mysql-4.00.12/0040755000175100001560000000000010021471571011642 5ustar takeshisamysql-4.00.12/index.html0120777000175100001560000000000010023620575017236 2manual.ja_toc.htmlustar takeshisamysql-4.00.12/manual.ja_Environment_variables.html0100644000175100001560000001237710021471264021020 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - F Environment Variables Go to the first, previous, next, last section, table of contents.

F Environment Variables

MySQLで直接又は間接的に使用されている全ての環境変数リストを示します。これらのほとんどはこのマニュアルのどこかで使用されています。

コマンドラインオプションで指定される環境変数はコンフィギュレーションファイルで指定されるものよりも優先されます。また、コンフィギュレーションファイルで指定される環境変数はシェルで設定された環境変数よりも優先されます。

MySQLの振る舞いを指定する場合、環境変数はシェルで設定するよりもにコンフィギュレーションファイルで設定される方が望ましいことが多いです。 「4.1.2 `my.cnf' オプションファイル」節参照.

Variable Description
CCX Set this to your C++ compiler when running configure.
CC Set this to your C compiler when running configure.
CFLAGS Flags for your C compiler when running configure.
CXXFLAGS Flags for your C++ compiler when running configure.
DBI_USER The default user name for Perl DBI.
DBI_TRACE Used when tracing Perl DBI.
HOME The default path for the mysql history file is `$HOME/.mysql_history'.
LD_RUN_PATH Used to specify where your `libmysqlclient.so' is.
MYSQL_DEBUG Debug-trace options when debugging.
MYSQL_HISTFILE The path to the mysql history file.
MYSQL_HOST Default host name used by the mysql command-line client.
MYSQL_PS1 Command prompt to use in the mysql command-line client. 「4.8.2 mysql, コマンドラインツール」節参照.
MYSQL_PWD The default password when connecting to mysqld. Note that use of this is insecure!
MYSQL_TCP_PORT The default TCP/IP port.
MYSQL_UNIX_PORT The default socket; used for connections to localhost.
PATH Used by the shell to finds the MySQL programs.
TMPDIR The directory where temporary tables/files are created.
TZ This should be set to your local time zone. 「A.4.6 Time Zone Problems」節参照.
UMASK_DIR The user-directory creation mask when creating directories. Note that this is ANDed with UMASK!
UMASK The user-file creation mask when creating files.
USER The default user on Windows to use when connecting to mysqld.

Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja.ps.gz0100644000175100001560001325630010021471313014474 0ustar takeshisarF@manual.ja.ps踴mu~_'N8B9ldeeeU1D8_*eH缶ezAh|1\Wn46-XH趺拵*sZ講償魴|驢/? 某W迯枚_y/~蟀wv_<|~頡娟~C a{(7~_w菅W_頗~酖Wx黜/閤苡^~髏翹_;?y笛_?x顆_~紫o_>x拵>聽^r捫x醸>胱<z肭}~囎疆}Kゼ{髓/x譲翹/^}脉?|g崇"衰o^|_~=|5hSF瀟#燧耨?k陌f~筵?趨S漿7_Z聽譲翼?y拵餾=?閊彈烈2?/xWGx b`g_~騅|a?Pc逑濕[^r.黎7o_p嘱拊o飾9]薐}v舶絲^}o濕縋?| ^|孵7某_g]硅-/|_w~尢x~?~{k~撥>+鐃+O^?%~銛_>鈬櫟鴪a]o^麥;g;o-ofxz融+7菅_c|鑼<<|`}X/`<睛/{~O^{齲_i膀~;酬|wN彙o遙~|7讌~取><?貧<蹕?授肭[ 鉐屁P涅h}膺x> 燠顏譌|肭黐?x殍c杵|鵆禊}f9&/x深恠紗Z=傷Y賚Ox黎閘?=韶3龕sY`齬Z{瘴賈/畴~t?硅兼/~z渤V~羚<%_|戀/q~縋o甅Ky猖w鯔_=嚶=赱朷<+V睿o^償棊|-cs冗岨襦7o_房+膩|昼7録W聘苹9骼貊?x卉O据綮揀g~>6<&;G釶鋏_徐o, '秉}芝}穹^頗W_a鵯W裾溜匏Z沛潘|朷雛_?陷y5# 磆燎傀蛆z孥悶廓YG鮟#鰡qiX祟^}1白迴y1W&_dB濘{[ }智<pr/?eW&孤=0庇'{NCC|"_n$1/据/^O\>[e>鋳>Y{h1w>社9<ﾏx滸|窰y-?型笵椙7D<D K鬲淇;~0毀z>耆 諾z8"8//~死鳰哲G璢稘嗷椙[`諠穗ya~[.%~臙囁|+M胚_r|\vM%膵 !錏君~kP濕86眀h~鯨纛_}f?y禎fG丞搭睡q>L#Q跖顳/_~nZkl鰮3XG短9 XW?cL~| 銅4竰/o埴遊|圏X}鹵BA?~萩#~髿蒸窰G瞻/∂^x埣a/u};_~| 艷o沫Y8w烈 6o=Y}ｗ/^|xy7_聟坊3役~黽疔7菅鵆鴉k踈=LgG4]o滯縋o歟?\+ebャ淆g%x陞敷}"f@":巡Fnyx/{/銷痞燧+4髢譌貿??巽7聳x?L?{e 美年qQb馭乏/^*_^頤觀o|驛>-o|騅x\{9G黶稻?力lgo?站z;聰'D餝昊'`麩f締似榕O釋o燬力輜 %~P/鍾寶~鴉K2劑⊃z寞某駛/皴Yo築Wx5?縷限晶Y~沫~?~y@杖??~`LOfiuO樟#鼈!|8h_}a^蜻U桓Wpw_dM}-|(杉/O?>z寸0E^H'戒 ~;胙F;!篆鴣從]L^>趣3g龠]1燼鞨筒髄依^A?R快7舵___膺?~?xx濬糴~?脯W /}7燔:dzO陂蜻o~/颶濘~[03:蓴?8k7xq鬼q[W濡W鐓緕eoD韶?Bj唆gGi}釋鰌聽{I諢?淶體W`J械#."o檣躬焉襟c枡o號G∫蛙yy骼bЩ%9cKW/~7!юY枅y W| 渫鯨>Y|如|w!採|a糺#=pyセ9^y|Bojb臟陂経{mG7a状w旬黝-N趺0Y渊2攴x齊M,q嶂x-|%釼覧_a~'/膽e}>c纏薫顰qb>"囍舶/o~龕?湯'~c}g諠/屶YLc^悁P譲Cjnw霽楢_歓CCK 蝎祚髞_廊嶇濕x|Px\F_|喬' qG_ 4qQ隧濔|u樞_o驢没霍g?~鶺/施奎/>y背=d>憂顋7b3z纓?^>湍v逞~|+gx|誥資襄/据W_3)M0li陜逑W:ぇ要誡竍n=B?障９}）踟靠ILK嵶'|征g~侭溂鉾WO/7^飾ro0s直};g/x~zgx?|_>}B?u<<{9辜;臙鴪77_嘱z肋殲wn_}'|7濕}zgxO>総ct?丈f濬'H>{G楾/_}r#ys(暼7RyzU衽+^Oy|u竕OWOx齡决+{z貼O~z貼羊+鈬O騁表輦+鈬=盾^~鶯{鰉W榾z貼殲+鈬?<盾^~{_]~芳<{2途+1C}馼K聽'/5O^<椙%O^D,性O^rO霽Kn褫'/巷<\巷/?y]徐%w'/5O^rWo?y%字榠7寂~K鉅w鉅寂霽K鉅|斬}k'9H}?~Q>Sa 痃麋Vu|壊PJc k]V{舫k][S=X]~RU-wq慘R柝虚q悩\:>s佼Uz\&^%禳#8sk丘樮Hwvl,=師r]i苴m椙-澣{gJ{p1甼銛5虚啓$3}?s12q泗uk肯sK舊qNbH酬qnyK5m_#Ok淨薗$XV:mweM{V(d-騎C>18s un彌n孟効Q1XGX毃'C敦V暉3Ｇ}{w|{uMe濛G5WY毎}似魚m跌xw -a蓍膓/[:R徭BY3暁祖l+6;q釁 5錏旦禎qUV躓rG}棔G約B7颯Zrl鏥xb萋H [(Ghv給\/V Z蠧 I省2Juf枠}嶐v4W蒄vs8以B8啜1 鱶|s怖Y蟶Bi5ulXBV0Sr嵬y|駢1<_泱XY郡++r`竡u?.轗4鰒T紙嫋_w竄qrT虜,8 _遣能&V,(}x蹶c'L尻miq}Ep \sa+8ZY,鰛rn[flY,|6_-弃澳m0fy 宇%a)pxGq8&qWq+:ﾊc惑8罩qyn訴-MoFBGOs碓hYM IUB%kk{\"I湛tc0踵窺点 kM77Y9芎v贏V楠Z蛩Kg1mu#崑咾麥#5v若Q#te胛ZX_"z<#5Lk緒 O9cM飄%告m c=u_0|i gqP鑽a:鍮uf＜cs*8n2峠k絽 粁za赱7BK_9_H"Kt随嫁K]}WK鍋qGd揩O3qA >岶] WDv k寺敵芝wMV#芹b徇BxRr濡ZH獨NhOlG\80XQ5崟保Y|Q婉QB(閾H衡%3靨G0Wmo7$0+香1k_)b-xF"OI (xWBuHvuV嚔G _臉+維5 遅a n;S惆C礪訣"K棚Gs表 稾q;8k^X'7-[羮X@-%~n-WVQ7\ual-@逝(txA`@糺>?ywX2X+收9桿alw乃x渝* KX";Tbb5謂描mAl z 7Ke窺=5"K%6hq;W椡l-8x糺割!>m読8 ;wQb=k烏\&牌聘枴 Jc ]veqM,YB rF慶p;x虫Z曾9木s'.怪茜q渊0s` Z8\P篋6\_O紗wnt4^xg)gX/bqw@ugp#k;迄LD <;wJL"z菜E^ax?C釈艘}1xYx疂&..XJ醪Fp2A@|mp!JY鰍0愿af9FPU*<}@g顕 w e zkIu l}nqP6FF%])m,竈*1惘跟N|qdz гp8`kw*9'b(.6t4 (5-x`棺b< D@]L]萵C険W i泥3\wMa)g!} Lz-3!`hXX招% _E ?[ocB'K`do懌q?;}/ /茎qp, ps{$眛堪@缸O%C&玻[X*a ;竍─p|*'b"q+JtJ Y e柁]p<,[2xse*\|JR禹W]`Js{ p3x< w#0k;;b'6J佯_xMhd+e_X=  h V霰 4蓿SMIg; B_/O吭vy~Bs{icM@征# p >普yP逸'VG31[g+71鳬B(,p 話{"Ig#O丙 7{pS(1[`pgゅy+7訌3+MaQjk88I9 ,3砺VFd;嵌8w 晴-k/kQ. cX(KA璋'no彫}N>m#悲質蒡{o抛 %H<該Pn]![:`2w ^ `v測~q$qm3H觝T Vv \\( &68|UQ^~l5tx*nLd\髞!jr:'c原P移k :穣 ]!&# qI癘u#像牒d(3cD/Xq9 Q 逞z鵐xx宅+δZV bN|X ｏ8筑wg]B^tJ次@{=al[ 果(.q%B n@fH瞥U飛4hn尅>!|)dNu9Q@l ]p5 uqX#o奈静d覬黔x2(n0[^{G儂f=!;b5x!k7l) w%=8F Rn"CH hsX,PxE`tDd0)47/=$瓊 7qp'$@s'V&cn0" )Ng@g4X[Ew,QX|漢e|篠N&w{別L橿蠧dZ _,0#チu10q3)匁敲:X+Yt'琢Rau;!洞w9z崔匱 LA#u'c$8$l 罹=@鷓5G唹Vx!杭7 T竇-慶壤Z| nG` ]x|域g-輒决'<霰W@>'4[Y )7頤韶f$ I伐mz I H5B=d@矇亥? 0 \症2z _p^0{B羔"tsChf AR声GqDl9曲#7HuD|禮Iqsj,s `2~5+呷Y%K1 8N稽+Q4貮a,商ufx莨019%V.'H#LiQ窮}' 憬M`黎V価X褌v)跚L*卓繪x2 (K 8兄E} g& `L死[6)R0=e`f|6籍2Tok 01QRl:Y9E_b獻:r.z1GrUv}ywhイ:X5D劭O@y笶榕-M9La 4Q?幟鴃Y蝋 )D漱`nKLyC&Plz觚|Xm+{゜縄,G"aw睹\鉾p歉 = MBJ4畧# R`IPb槿淤$y]\=&榕斈z Xe4韭|跏 芋彿*,oY+<'箭w^+&H l (S`,nGt閇\X*;F舸AY他 az7;{\*Q>*>7D`rt`'~V``箍B'U qg?\vT'7\w 嘯1V/L7J@m% uu懌nnZ~僕e;0f算*V|y5fs疔杏{x.3疹悍rwt \驃",cL`<.> 識M|{/携妝q鵬*糢})n浸tE6_噴N抜#/m秕瀧 諫.bMw6MADN@m朗3N韜зKhg`埓`y8%鞫Hsmn`^v|o抒MF44$;?栢6)n$`ztw+H2K.`=)8R`楜y=;=xe剔@既pu/p予K贄$<dc5 K/攅3h~t嘗0@&I0皺}^Oj彩捩 仭圏泝 &aC^3%7沛s1Ieの=C租rmb宇IpkA 窒*^)XW(&bﾐBe亂郡t\?%`=驟t#Gkq[]UP遜.X6s餅5r塾Xk騅@>1Y@yX% 3馬*eVG`@操N佝Q^]Kl$S}:J;B2lb".x;4&鰛8v从&_VyeSV+Nz$}6 PRt9 侅fxl8li耶)R8Q%曼B贊c> rw9{9li 0b展 隶hfr~O 7 榠xeV n@.8aT古K]-t`8/莵kF&{@ 0*qo[!XD[Ｔ |z戚ri0,),脊[砲赤Bix{.:f=cnDmM\ l2Cf3kA菌 Av&帳c#趁諺a%?n!6CXeda>a餔c'r JO | yp桁qC溢zbH,8aJ~]1@磽F嚏4].3?S綫 tk幀ar汳j壌qa,;M_k_b?12赭,*庵V<.&收>nUR棹V凱Lea0r},世N墜Cv `KIQz條討j+⇒ 識`p[KKQc楴xsi @`駅%gi`X丑;QF;k2/Nｃ6%3溂?禿$淤<2=b鵼Q|&ow煙;::詑2毀Qｳlj" tG#M&O府]]@9言sp) .o堺qh1*毎Pr  =b^f媚[ SqXHv,XrM!  ΗFKdDu\)gUS{u{i7帰Z:VR1+(r湲h LL~Y)=3\留zHOf8M}VGg,G棲c漉j`=紲刮壁}XIvVv祗fﾕG+xs`{W J&vf.j逃)/yc( 諾lmnvdaょ0ou(電mE皋Uq敬:C%梓,E&AC$4z [1怯jTZ'嶺睫墮@swW靠P>!h沢z 知p,Yu.Q3kU7Hpf#%MC +門rhEΜ求}似$cd8q硬'a釿]搜yh2A笏K,V6dY`no荊WS4r鞦8吭X:vA1<3P欒HK<La$GU原f'*訴 元稗>,V<::妁蘂vE Fc帯@3B}-Q7K=."N*]sXOB7Wc,y`f石}-3錺C=W舖b8+豺ijVｗS箱7/:Tm縻4K(柑=CtdkGMVUA,{ KNd,A-ebe7=l/K;Xqsy8W悳5n0z(楪ﾜ殊U]抬M2d,y5pV6dW3研φv'S0$i,驅}!Pk9f{p . y D4=,>7cT70[v['Y*iRN| 岩I_N嗄T庁n8慕緝/0H|B&侫)!^{+hu片N鄙S雉nR 茎I嫐YIi.n: Pe1 ;r"(^ 4q伊呈 2耜n2'MBVH%介%{Q;XW刑YRt,V5潮0 Q @IXRBi-w9pwFL>Y6,≦碧D/ZAV0=孑 剛樒`5#: */cb腔SpM:#4d.gu`p1yu\D1 :1q!呀I6VN歯＃h纂P睊\G]2d濯<粗<内#Ti ` *k>O4k棧JLR濟tmmY怙}w揖TRf04y8;s 敵 ISe`,嘯r 萇停]Y8釜1[絹ja95樽 *Fv` 鬱韻]ES (mib=\X7u]蕭z aT 鏐M"#,Wg5%(澳lbmI}+) (4(HQ>麑p鰾V繁桍;D槿徹Ky/(7章嘴<}h(6c$@e`< d6XU%=@ pz絹Wj4q磽t榲fiэ<兜" \鍖G`Pn7靆,D艟治zhAyL%粽]`Gw篁 7rR0英Xb[梅Qwp剖Y銭ygD^>+ &g{m%9C動TumN;zxtk5xU朖s窄d #IRnk0{i ^<7-{4 "苓|榠`e襴篋p}1e=霤詣"n愉&|z2}掾Nw{匂.&讌0Saw YzYR<,Ug..-濯.隍效A(-JF[u &Z .Y jVk]f孰 M舜辿PI曛`r_nz=iK)U壊$4,=觴C 緯CF +口p綬T`0[蛹封),8T鋪T=悦g:/８E^橈j<:,hA.?ar卿edXL=r.Vｹa*jX7  #h2BUn`$yyB2 phJfRk`:/'Y7I刮}JveOc衿遭A朷]@2}i想VZjhcxA.N!l邏琥#CB\徹q[ //隶9忰艪){{ 科隰K<艀RVn槎m漕AB彰膰~z xM/7<堕L[/Ll抄3'aa%,獄dQq 丹8/v,27A 4$|Ou+@h;,N(T.f\eciX冲Se+;l7@u'm _6咳 sj諦b棔bG( ,7 ]5 妬KJ[dｿ9MW3XP+q*MP bV,b31S eb朖!L|S6rCB飭!bMVsy["bZ鴛{Q凾HD8U%,v ﾛir+^s| 根r/k_%x弓\| aJ5聳& y r\詑:j@ Qh0 W<+k0:Y韲IvT 3:  悄u067Tow~允0`4nVTX:M:fl但37Que Drm0E割e B*厠"K9=O3z(eﾀ<珮諌櫃屆9甄 グ^:O7|zT蟷Hy;>M(v*>n碪& 0U&=YLM`$j獅_9vFS=Pe_+{o,+pDU巻\b1Xx0} fP )*BR^xXT!+5 ky黙=qhq*j `8zfLN肭5V饕'LRSc(@貘ZU0m轄枢H0) 踈\`Fjq$bc療瞻慷0xu2/d雌xy67HbaoV=e`傚 #G站$lEc]u岷:28G@r T_><7Y}r粁e皀D3`爍6~K\_|y{)_歹T\pvt#1黠gZ 皎%u33sTMB8E?.鴃Pq"j云uLn絮#r- qV[9y \o愃V.o\en]qa8i[1HCz`M鎌舳糟{到d鵝C!0籥_鵝KM%x規 Hvp縵?E#VがLd\M^c,j-荀a窘zs:ZbV[兄x;K鋲敗~N?P:8.zD+蠣-0 k7%I%D掫=4 \=ppn==~d\-譟b+02 b宛k,ｹ茵鰮 p3{S\默OK*梢r狛\,YA5衝j亀AIb1頃毫. pTS@}yt7)f=SJVmKZjBI舩$臓f%}y_;0Qs9[X鷙d2'λhCgM/v|(g☆ AB丁s?籾mibdE論XUAv翔7y X!@;lG 躊wuxR寔\m莖LP.QA]:瑪U[0{湊3$Xn6kiR粘b9BC6-I+d蝉7U&萍勠os3iU`SLe3!j`n罹&;!-KE功涼t~J^!k]莅dZF B~XgMyUqc 'Sp貶t,l皺(A3x精=B=^鰌X>p Q=`s P=瓠L?6fe坦 J) 7Yn謔n歉0a修Wp yucY鉈NS$@xEoeWl慟:-\Ц艶o[.3;;^蹼t N af?< S?+鈬象;04b5f柑p+6lQ埠Y[b\ｦ8悵O d &'FGj6 @坩} 散.6_医=納g;kF0073N隈o 杤m戳ベ4藜顰=e萼<y5Z^0姙DPfq1{xFa\?、色u 7c70Q*\2Q^"耀} Rmqdm`LBT)N@N.u<森Z2K尊+<斛f- LEU)S m@V景IJ~lQ石駄+>k,%崔+/9XNJi?姙4p{Y5漱3@r? 3O$?us?^靡z7梭薪|~臧|6朞搭Od券G据m1 睦{臙括吹w録|<.褥了i韲>穀;/骼nVzSs;{FBg瑪wO7y4S蝙嚴榾髞{奴/痳恠]型k"恂駻澣+i/^z驫o囘-鋳{酖O/;P;蓄5&浴}?戴^髓H?x?F旄ag冀z)n躔,n逾[n=;7壅 >dMP,耼肘1R悠~B"]N Lu}BsE9*二Id{ζA于U貲燕ew槎YQ甼$;'j)^lJN亥apJz鐸.g3朷30浤qWz*耜{*h^#6豢)p2[U"獨yeja經闔41$S砌,M%OO%*yb |4^Uu 拌 (Uny椌wD>>gG,fk 泓~) |YZuT際w)Pv^UU P +碗7L iya;L震-s^Y CG2vaZ)taA {V(]5{(t≠P躊?nFmb-f蟠1= 尠s郁E!^TK+禺2 E耡か甓,z=^Vy+ova.\B塩鏖塾^&Pv+譛`+3,n炸訐&8LIPwJ臠onR{a掎:]Y>";Hq ,畔=o`S9uMi8l#Zm雷.nG∴6廣8h V-1布求分*Kfa;s7;[祿譬]10稔\sfQ1D浹a 羌鑒~X茲Kr]糊鼹{桍XF畏S.]Cb騷9)ae'^ml偲.?\ J)+K)lnT)v[二Dq[a迸!軋+薜R[LHy;sW 1$輒 a%u<蒹 `ye%)Me{E:n洞nuNB>G{*]Ul2尹ad-LC叡遜角6)dBO{v4Ut/v[t!LiBu暴l泱Q8g_Q釦?M窺|ls9e-[KmIr*┰m米鰍C;棟讒MNe @~[Ze3nb|壱K5U3qﾄXCV椈*狢崑4nW To5nV8e 枦&3yvEG 鬚NmD醂R90 v_j|do{) \貿5g3圜 PQ豆V o/鼓-徹s@;fヌe4Oe)E軆孝L;uVsOZ'x6gl辰堀t:7m`fY7c)廾慯'泉D;& O'.~4霓捻qO途l]k[屐O J".[c懋  A o靜e盡Yisr勳w^X35no2. ka寒枩96(&f8ViU fk/Y.L綉^mA E寞購L3Ｔ蔦v(~規jY<洌D紡tLs賃<2-tI"存鼡R猝倶d! p[w{NxZs)*zlqfLh1a[8屁鞘CYZE誦n4;f也蒟Ep1 uJ鏃哽n xKpVb?'vMpe限滝鸚5q稔[ lm虜8s*詢l^Mo訴n[0/-;:}UA0KL@￣但經C井J駐w ┼jD痳Tj >>UUw[D踝悋x8*m０;$麟l5芥7w'~3$6A)i刷aO0K送鹸| _Y>T蠍B,@wPFRZ /08l&+,[j&<H崎p7c/6?MVBu*ru鶏峭1"J>6e.;3~ &衣jm@6Y<7Onn臆xxY)Uuu.TW]8用}s椨PN58&6閊  XﾛE\aRsT檪9突sS} T:o泡c% K浬l釛/d})\wnLHz, r c,RDMx?=(X*暼F!典-y#A086}曙s=,rt襴a℃ap$k狩N祈Gk 6x擧TeC盪Uo=|甫^ eD+搆02DmoY嗅歔u^U[\]jG?裄9TTQNc/?T葩.R[ h`9偵14W顧螳 I5 |6Ly5m]exGD渇黙#J覈W I`A楫`dqF`-u+)r檳J努:*v礇自枕~ .W]M*v@cfm<畧D(聾羔洌hN'=寳>疱5j桟ど{l牀6E*惷Y綏摯Glde%荏;=Y4bDοz%H$xE<\jlfdQ隲+w軽T3%o談~*1#-!PoH8rm>緇,iZsHu.9恚膾{Zp添ce MF窕>ox>7 \ Pc JICb脹}b1mv&靂m2tf楕0Gf興H胞ng扮y緘)餔},餔 ^駈fI緇Xo}l杏:ln杰癸8&釶_\Ky,S5借JYsJ←Jv孺hyz 凰Vdeu珮 KY}\&cwbD,rc@Dg~Q嬢jLo叩B#1[(i.D`靨鞴q6陀j9迯蛎殷TO-yQ z`匂b)7|V8l1fmn潜 N*N`}+4栩,*'doUgkX衾=ccqj;k)^^Q$征Mh拾;濬; MWARuk%: c捕q/cv筈klO _z幎P砧襍Xov I *$g1,曾 賎榻V&硝LD$oF~Urj3御隨t\GVFbI前H薜▲唱r跣有m mN|wU+q%NQmk9bJ）- W粍)R%愧pTu`oN Tav(dnjz nOuQc両9ini庁uxb!l藏{PBr%cK74蹌BjP$X疇[Wﾍ侑4[殳^]阜/靴。炭V斯1 銕樌ﾂD AJETG改礎績|bu(t語 賛gr-^Dc霧X;imaeg00]\p嬌 =妝6甕$N^H霞/l蛮n04I蛟T躄=%1kY5gO~e@(]>t煕PJKbgP- :<Lm_熏,u楸H}|屏lI芭[vv腆0e Wタ`嶷v*荷U閣&J6< 滷攷莢y _~yX枇H*覩,B罕tJ 禰vus涅86M蔽Bg]s婚脆Bu*"v鼈7fjsabQwh賻P|帳蚊:>jQ}Q:_淘輝UM 鬨weWr^O)V@勤hwga3Y> o`Wr_k]q)K+myO虞0_n漫FN舁HZ傘~b癲^e-y ┳勅hlq!Fl})r` 建}SU婿=-EK".C\vp者NxC}rZ6,rZe\ $7`{X酔曩\BvN};P+n橦yx3[}U k@蝦~ 弗~肱u岶cE;yd=:9W6w朦ι=i諄暁.姐c 凸A{wZ@kb縟vY;堵T鎔Hr渭蹊e髷Ya6瀬r<`*汢&mQ鬯)囂j$fWc=cF:~O&s[==6眇k襠畏bg"tg5(*似saB`$d~絮mE 參.PP兩(抄`yP綾PFn=P巳a訪gT=Lb宕.}戞vg*Y穰UG"M様3dYcαn伸浦w6%. 2MN罰P'MIQD-珥,苧FE- 8K档曾 7,[YA\& 廾蚓%:]橦hy) W%E'w]& \4pBqoPrLN`%SBjWX):.B=ULZ6鏥N惴i.忍佇jT'!.F -{ [U焔vSApR獪fl酵#?m螫5棄b'CAZ逧%A鯡'-dA{`h.N豢=8FuYnfA5寄mGw1>P-6e+櫟]p*a}tFma芦~噤ImsaB蛭~n?腸燿m/u5l1僵驃M]Ia:vRI膜ωl3Q]8cw脈蒲5B6]RrKws衾l錺2ny"lyS+v浜甫 @]s/戴銷juN吶[M^J^2-'g[7農幸k;oKカ殯(67L e7~n畍%6NL;Ag倦桀M.J禄柩 P7 桐×klh鼬EYd'卻[Cr地皖 漕"+ t詫鑑妙>lXGbZhx< \oaYI-c ?=歯L(⇔N8邑o2貊L梛oQoJ鑑T  肌'r5My誠w誓肚R2if2Sn)(6釖虐p<7T-l@-lV(Gt[聖i結\vg?CfSm 慧 &K$!N]睛d*a{a=@C@並P妥j贊.SgUuS凄鉈VGl(Eﾋ奨yapq蓿侈jS21沐8cY5wvcv們[jc<ЧP'A妣8v `y惶/X櫺N 鏘O~4chggC ]:S莇胙> 犇Wa27/猗Vv,W_ 偐h:橲`m/4叡{%cYX+e!杞v比 爵f`?7楾n樫^m o罠-\f[EUP洳Sy#~飼Qg9f,^}hfdGfw>f +#pZ 隣 C戴tS/b>l. :(i\鷁W-tya&K= 返7j瀲 Tfnsи蒋.j込冶f&;驫霊i}喋Mbxc=端1A0U疫姜E塗z篥醜}&.h6;<@B< RCZ害&.7c悗RH| P御YL溲~#&;@9D膣\Rg~P| K`[%盪xn嚥,姻 zJ瞻cv桑xvPa意7^l7l王0花of膈[=eF? `S慌m1Xs^$b 汳40雹Ps轎3|pD[<U ]K元@eZ+M9B~f臂万gsV=Y檜%=')>fo4XDWm"r~{邀}鮫nu23eI銅v8痞8w#4Q :'胼6eyh帚5簸W S樞&y{沍m4x I廻_瘻/y4鎔據u愾酬OjQ[6Esc詈f&WKメ A馭L C8 駢\W`f FlйrB``,番AF蛮=]%Z:@[0:NoiOuG第DyA<:築)V麸 岸UY落9*ms&nn楞wzfC=qd=葦l_&Ag^IG7Da1鷏SQu┤m‥+):/Fa7cX首@I +&T3e9d!(l:7CT#D察]N-OXs;Or pnC%d61SH攤v總(a s,娉諒#禽1樗4"A{mMq/NH,(vl{y+I瘟G#幀@l='勲6j6K Rz品 (:\#av#貨z+wSvK6?,娶埜徠i $bU bx`vw>L-0Dn2S夏'冠ZNw (y,Ly8|/pD|3lb● a[F罩楽mvlW01豆l{w 捜S9z_|[V7厘)4_鷯0_m_RJ Up1<葉籤=F袷覿pX 蓬kS#'K r募琿\yvPLp絏Z^DF%販qv=鎖p>8拒\?db \Y W: T:>垂蛄群v6X=z-(782)lw`e`原 gS`vm#qpl烙;TFn 体A{ 3 `5c9*?埀O=酥倪f7(Hw+@HTZM;ouS莠'9^談qMqmnK%0R#\&qb5cur9A!Q#鄒嶽(売B/I2g枳~hA斬3m祚,Y壊鮟MPP灯[ hwNUF唏tX c/{i`,,Uu心豢PHO茶"5C憊&xlww`+nDe偐dnN+l犹(5P皣8庶674ひc語g>0ij)茣f We,─X#ZA1)d|ik狆C1<踞\ly飽 6%W囁 f$B<9贓F(O6uX0┛vvz駅rj[玳潔酲難(cR0[k掠洟7]渺^2 餔:@))SD 町nTNq/n*RS,P"20L)M (,慷d恨=V ni2座.qb:m-u0A!CBFXnoOu3P"DK槹鷂屬T; x<|=牟駟N`寫iZYOj犖3n翳z這f~"s@~<ニ戟F)z[ef鎚>MSU皚(VS 螳xQl 造5wpf倪.)w軽vS善 la v榛+4Ne(`鼓g幣e芽{7}~0膣降:8[折@C~氏搦A鄰6,T\eZII 運2襭' eS樔畊軛M#F/lhLs7y%z&7\c61 DVW4帶:;@c3sZ<>y&kf}`4$DYux(b#Wg!Yg.Jkt箜 qs件{D禮{F&渊npn];w3-%堡[{9,胚*){\{疾葷H騙UPoU枠\霑>鉱aw`ZA Wc亦飲膊pij+~31`Y4！ro``欸И6 祚禿e0P q1*闢 xZ喩zvVfVbγh+N9nX&yP_f 3sJIOCIlYo`\\ T闍 \n.K2stX(鮠z7C |UwO羞|Y.+'XQ%k濃筴n<WR柢C {I^脣mw=羽yr鱒鱠b饂yE{t/@M双p*淵杰+qXA0`/*xqU6_0b;茣-8({eXs]*`]gJcg3zk4鷸/<森Ovw>sPCFU!c)\n浙*Bc咳%嚮}昆`.L* {VL7UwZ%Jq& oj;畦\ UVQA8[WAxk?l捷b王^櫁'y Q軟`EivMSaqネg+瞰臼cy'毘pew總#正Y,tdQ`'LbE^j[戳c柏GMf-躙斬A咒>=9,`1wK粍駈WP蠹嶐J1u F .u(Bt:g7w!!%r=-兄<[;0(b!V壥Se#輙8cj7mJo/FmL`i6$W`kY'yn蹠}A is惚/C#{Ibi宵+鷆勸:Cw旁|q;ydu$0%+wgΣ[>R}Q*;/青d)ッ fi噤尿;(rm鶉kJ,荀$BP眼v$tSaweRDcT觝 .2[x5y| g俎_.韃p^杵?]h塩V虚扇Y錆=ﾓF嘛g)o偶aF}継{M.J&6CX迪3怎O 畤_ヽx0;,悳桜鮟x* 塁M;aM%j]7竦A+GS_qモn+tМ|:EKJ釖<澪jXI$pN$完s9桍*牌; MI;]tNv!zQ糠D>_>蟾非t `f!AiQ4ci<0峻?f.5[掘NM@b'舘rC&-β46))堡慇0φ鵄耗dZTRoMh藉kx@, AZP,4eQボ#aqw26&n^3倫輌m6愴 儕剃%fH仕 Ж:(xha渊R[% 裃"V@璧` tLΚ_Ii{膊r朏)&刎泌槃u.x,>T]O2YEL0蒂r賈v5抵2*ucVK5G6[g少flV/沌嫣遊南0 (@ Bf2Ly2vMGROUmK誨皷rW9B?lmP%J巒x0}xk m Rrj {rXlgaNP薈8\)謙6'kxQCA;'<"YL驀1&w;$KKy~ji扶慳Tg%y8W6 ｎ 3}亨?淀й Μ歔Q&P|e5'橘雜QqP覆IsXk8;戲N雅C^Nk !鱚aTlｷ-wz;Hc 8蝣ZL|Q!扁-莠跪B<'Ti W戞Nc;xj;c0!w敝!OqN朴M昿Ti.戻pInu;0済:置0 襤鐘y7勸彌JYw殕^蹌4|1N√.uB[<%= 渋UTdA[&vup靄戝3銑u uLg嶺Z5[k鴻jUl9るF<昴9qS勁LUc s8D耄A5C'g+競weSl水e5Zi+嬲T芟jnFL||-鳳?!`zp#&*Ar金較^跌輜R'`kX霏琅E\8Y鋼綸*Lwml7>cX={Osq"姜花>lZ叺/Eq疳O-k轡1VaF槨`V0Jg(Q華f椹%塔4ef_818E]P鉋茲Xt^ 鉈x]+V~9c}8MQ`73ZE5bM*攤UA壷x冀V蚕q^Rzg脾們) dh_C`;羅庵y潦efEs理;%\6S覲V'金A邇Mb,ZMXwFU9U<5!\`sn+o )D+ijHε=p薛*k纓ffzRQL2'CLv喉E`56$(nu籐)BW軍}鏘i~翕JW腺]nD5x事I;P)穴插>櫚:lG8文4遨X :K';b旌 ~g】~Zz6M延^fvI`<1懿q:UYgs啅# tW俟z>TZ&城YAv -鼎TcdSてX瑚YhRL井s樣]Yt檮Uf^ 餒φ損剖8 eﾐ/v装$R8h澄{|.Kif漓需QH識=,1鶻X0IS 兮=O禍$scvT}駆卍R2GkW,劬=`S &GV])l=]Q眈\Yyd仕YkX0m?,po橸(z抛4V_\ 款尺8ъ+)5樶`nC鴎J灘ko!慴!tF』 牆qi髭2N-V-B/cMOq,氓梶c&~Sd+,3Y犒Zu璃X%$!鰄25*{K摶RTk&0Xg菱p}HT{ sl鏘.p9福鮒mS"%<恠Lul;dr? s)]ea Q濕C枚燵鷆(L7(結Cv7a}{oZ茉YyzuXO己騁>l!件>nql肝銕eWL$1JJM &怎\監z+v薗:租 )饑s燕_a 7-3`fuVj軈急止dOVm錦蹙e;]2憔lgCEKcV@恙u罰CumF靡koRo:e7R贐A_ 舶NK5rk頚p]r{g8#蠑Y*~牝*Z] m広y&H遁棍JNUB〇)\'V^N坩d l*};仏a%[#6陛(*":hP賀n禽+= ^櫨u7末熙0WyM投X2,+! $`棒K揖^U;qsk_p|U誤臨慴膕城b遨}wSJ,&鞁酘譽指套pn}m寺b4鵠[牛T^f諫 #G{Fl懶6Cem W9:P1EflemP"WY^W7-P?丹nbN楽'XTYMS z#f8 喰MA/{x7;鏖rRek3`3A2榿 jR/Llgo龜VBdt6;k*鐓&+pc詛XL}杞6@-c`n潘;b}{t擧順`=狽廴5n碾07M頼杙憫-{Kd1% 嫐{9=.壷0#w$nVJW,f*,0e8z I萃^p征5u+6>拘ojh囗5]x<[c_SHhmzz(暖.得Y{YZBf[{斂琢fj婿$不~ ->Pi点fLUORV-?惠TozU髮哀佚, v Y湯B貶←d>WCYK]Q)Pf T枌vlnw製c{y鏤T篳lc指径/lYz|Q/⊆1;pW敷Gfl湃,JkTc6fg6圭嶝e_僭[vODSj| 燗pO哮 p{悋C6gGMx.鮫DK1$O|I7W賍>e訣財戸絵-辷>RA莓X oOk ;Ga外u8 `2V?暼犹~荏激4'g.'0β6LBSYr.~mL誕2鏡8哺.m;愕敍>mBEP防$h^pge$滑最lfe]=_鈍v N枋Cts框l%携` tB_jf宦a;*/]c^$B 憶SS)VT昄=P枸蛋G朏Dv{N}i6'Ehz孱g辿[T $-wB攻,擡 |&t:B!岱男敕x#ZlE-fBS;;(`|SSCg= 虞|X_n:f%蓍`Dν|;瓷vBhYN誼 齊 jN Ez9巛鴬^{q<海b鯉A,/>截8@桶Fvp,1敬o^RMCb%pMe{d5BXSn4^,(BlcxTxb力jl苡d"X3!)晏册 fGXv(}愕架3u1cVhC拜BM1dTC惷W _/r恩*?; 昊`i恷68渝=)^o+3y;A遷Dt}CJ杁ZLLje靭鱸>UZ`;L冴@6F xX庠Y斬QU東(kY蟋~}Wq >U(8)Kィ U%變CtOucuV叉梔&9鴨MoeqlO訟 bw隈5縿篦@mP@ b藉蹴蟻c歟c 39=戚=B]/N暫? x*`&w!l恷9Li8~賑椏R丙P羞p]n鷄laWh/u,Mk_p z妬辻YX_l)m|^1jrnFG哺串J.\Nin>*~縣M~ ZkY 痔RJ*gis恫X]lzXLD爨NIOU[_wm?乞吾Kq拡R腑~Lj九>>_W&X邂4{華> 4隴:[Yニ^*wXu@o8儉悩jsdn/病pn5 ) Jf蕃7Sぇ滝%G秀$3`j;:氾}妖D ~v\*$;嗹剖嵯/^ xwWX[ h6%1&巉[洽ak>TL,|"5救笹7!宕瘰x 軒_2{A溺禊R\暸1NA@6_M&轌l] }AX 9n N 脹"a " JS1krYwew飯aBv@d-[餌6 K'タ g `@5J撞琿ヌsヵVz笈:/swhP;+G s海W42R矯b?M寔4}[D1WhJ俘厰!4L苴 ") K處V囑ju鎌7jVEYap最PQl >OjУ圖-豐X県\[R 9.Np駅B.q6遡'72W7汎(讒nzN=^ p,}/2з@癪Cf2靭 N;\iWB(/m啓HUセTXUpeu;;0xes薐 j寄Z[Bv]q|s_鵯d貭KQMiO拳V;0}mT期TkwJ.惷B卍E*n$02荻fh*q$[Fbe探{lA史LTヰVxOc∫}J%iPL-a$算2MZ z|qFvMNGd5謳1喪v辿楽楾P篥07\gXXmX`sSΜos莇闢設L'er=l14c1gO|R犢蝣/牲nO)傳c襟厮掛獻2贓-f/_ K華K}I)nlQZT1意種噐;恊PNy9MKXPV>*2(5哺~nLTyGy \缶W樢X 1rS:柞S&k胼聳<Inr收}W ┏S/q猴骭ア2&b1 ,W l着 vyz乾j TvＨ ;px@弾-U&醫6gth慧5n<'YB=暸>RえK?Gy鬆Z\j 盂;装Pc[腺侃拂 _ X omR`s?'BQ;fM&V>r5] !&_':WIpKT都鯲縦祟D"之O8娶l皮[wCsdXxd髟2^霆z(}P?%E;P?` 1C∃6唹J嬖nQq:rqCZR-)際L拳h蟯XUh o:Hq簿摎gd@d指*ew[*5,圃視吸 g^;堀X] 2]訟m(g *\jBl粂`Ai,p,卯uv 緋Ge Oj^ A(tq~E7oo4柩1D!躡lT0.8消S 渟搜ｸE;岡zu*乎斯森j`M@擠M跼v Q酷>l6i杣fcbGV 8``窺NfMa兆L!%痣t°C!( &i$- m輪rRW395誹仝K)*'?衛女*r*FnY吶X,v-2藪R崟5^6'xrq+PLe=gm ﾎf崢lr]wW杁9鈬"q憶*uT 'm 1j晤fe苺lL!G;湍Vf$U {T実(Kz07愍~妛={規瑚,`A熕qI校馗持vDv eYYGn qgs餮|銓"様1|ャXM(t慙EA.d藁YJ椡tv.NR便弭臈\F+*念U/(VM持Z?m16nEo'2=UEhdOvL9i!~"x珎vWMwc謦`C+Z- 旆鷆1懺bE繹F:膳摯a醐悖筱燔帖L哮麹JO.a8Q[d2 [-蔭4滝nW3]廩浤%爰怪a`; `ﾘ7NL e1q粁Iベ$f花OMUx獅膠`iJ y&棒kXY'm%爛Z妹6 9E撮\h`A)^樺;ov34b[iPx r'Ao,!*6[F<2V5橄v?prsYぺ-zf*bHb5/>UaNJKlJ┣f_NMn_z*g{ωb_Fk剣fQa,\0lgjV蛙踰!?F#h !<=N\%條w鱇Bw田!:\66zRYUJ,ar渭 ZPv4-])4t暎膨MuM76o2$657Q6'\p) h澑Uw1羽Ecg+d: "]閣1|q@狡vRN- {\ ZMFv歹0 質nK筝?試?iM髷 *6舩璃ku萱U70if!u梶耳?摧d_<:晟韭o_~/?yw韲>趣oB圉韭袗/JN腿t<<{薩 鰌o*b黶7<]'sc_{齟F{%|uS|AS綫|尨S伝|訖yz}蓍笨=盾^?UT冥(1>Tb冥輦+鈬=盾^~鶯{U|r/{O=盾^SI3<盾^~髢xwl繧~想k蜿斟>瞠涵罘r秦貨{驢aSEwH57蝉~d?鞘'/S諦a匸~d!gz惺F畳Rs棍qwQgq j>VZ 稟`s@;988禍YI桍覬o:>\潭43]m{(P_=< K睥bX&_vZ詞Oo4滴匿#廚BKRY|z篦`DUe鉄(K?' Ur焔j=t:\粡-?Q 6q5[D:nX=I狗I69~-匍毬<5鰥LPP;S[& Ab vf 8&9戯_恁“圜旌}穂/ lS況v2 3 羶彜"慢b荳jf[dAgi;婦~,[.a*gJ戻8巖"Wj詔t +>;檮%{s{7]擲-4,6[沍qX*!<6膚 GIt/歴ZM%襟\F2=b詞慓[&w+繦Y94n573McP5I似 wcseZ!醗}\痿r罷:v寞jSNW錦-gltk]霊s桟惓{y吸G0k 渝u\轗dZ乾n v*z^m#濔ttd筴gEs[GxSGN阻XXp$O}]Y帶F$o瓏|qzow<{癲 泳yzTa#W{序槎z>q完|だBx30jLn貌]婉zXl偲;苫O\[q7!万|[合B/ v3.z}G)%謇遯8Ln抃4U諍Lm肋0K拝zW巍PNw%bGa#;5[着膵YBZj6Qy"史c[贓ｐf>U呉翌F 詳U*3e\(?u仁XbX &@/b?hW,洽=敦 aps疉@\U>(C 1/強斃5!:綫Ma_aF~mMzM9悸z眷M;L才蕉DE仇GoKw槹fゾ$鑷馮)6形\ *Y0V括,屠3ktgR朏vX`oM"Lj6^賍eVZ誷87蚕抃 H 槎v降 ﾅ6￣-流凡,ky鷯 泄_UwU<喟HB2laG襠<:EQC!A!H窶;{w]Ukeeaa[S]M, /U-A 'f跌z5C"4慚L餃_x辛geaG,觜lO|Si+ 煽w zk.{SM便}聯k JX$NU1鬧-Ad*d,O5~Gg}|[uv?枝ZW]詛nH枴35'-M6{ciV]槽8譌胱\a揄綛R鋏D @嘲 ;a煮%i@|アＣr#F w HG/Fxz;yfiΤ發6o+E>B6拶久q4}鶴)yZ惘n税q裹7|D6 実Gq4梟pCF2N`Oh襦J7(^f sBBtRy?h9洽#8蚫"膤閏"8nWhｑ^Pa鰛~8iGG~O)M`XmLaXl利嵒IgRPw 喊cj{^U XP5KくIbqDk蛔 8V2'懷'g9h;V:續mP4滂GL衂p:X>f息7T$柘M^0 Gy船wN:!&軆ﾓ)/SR籬r蹂WfgST?@8I'GQ祝R湊^L1^B篠6/毒Ta ~,jGT g晉tg*狽 % 71 玩o確g;h-+4)C{職Il癢RtFN6掴販稾覧 P至M搆Z6廠R芸bx髮VR]~ l[ixdfj"~k=DO3#y K孱{絖蹌\ 析Az8Hk ｭ]X妝bf柯+-L票;欷x;RNvWNJ(B鼈v6|QSGo>z孜 氷+T#"蓼j賤3Y]Qx{L%z?G`dmU( ;47壜 庖4lUp/支9b.u,ﾁyka綬>=縣-,U<界Gy( J,"1h鷄M59JQ,閥!訌M@[U*苧~qXo;,RsURf)q{yv 3s喃@FS>旁:69WUj}&U 喃フ┠UH繝h300&{S shmp@LKrq~@`vf蔀切 箔9`-&,5P z#~Ｕ!;^}F@]zdJ@繹鵲 jW(!9 AN`#ÅgK$xq6T `\/a`rl7c/Y 9gF蕁O~<w餬諱9srxg 499癨NEJ[^>腺zaB6噐:0).]@~!,#m[黎AIKqu!紕qll$8/G4Cmlxe"c箟 膰 r* 戝棆v nS+OWなwbpn[Ehg廷#B-娃‰M[CO_(`PGv)ч峻kfqcv&俐紕_.#q5kBk<診@=x俐胆l慯堝6eS;Cga〆5$X$)d鹹S+x回g勅0讎縵Y Zw!!U5jr'SХr塒_.,e`F'z^[{-FT_{JGEz|k 廣 oX <|-~M戒o瘄y2+kVd aki>旗維j]SWm>%@7粘;l\1om66e9q峨,E縹ujwj将卦zh";Dtk凸<2P 2Ck滸"汨^jbvN'/DRk#D4庠?((` 8爵 z内h_V*s`1N'u'Sg{;RTp2D6薺wRs(ｮ 儖-<4Xl =8k馨韮;goC%7nPk*:!E&I詰3MK%欧[e芽Ю0.'[|8:iD唸[ 贐b<'#[q#嘉Jtf@pR^[TC:@附 \恊(XQZ9qBQz X百HO聘@輿&璋kTsU俐誄l>AH貞交][+qI|^ 喫--TE.-兢指[簗@he'2PX=駝$蝕6C P什:6諍.7 君澁巫b <a7 :9/l,弋>*GwN$K$e88韻?Eu咅%g~py/KP櫺f18CRt ~5"IK%`+g維Ng(gH糀rＧrq7Crg+ sU\鑞 6dq}-_UT撃Vb┠諫gJ 3W摸d3RFSo}^驂N鷦SJCE% '0* >-|鍜y]g~@ 郁M>FPvιzXJ#^v-oU鬮 ＦW[m6鮃H 袖%15c E1h,cE特鷙t&vlm新,帷s@oQG3[-洩DM祀W`V黻僂y防 +E/^&$藩&爐R帑亊rs蕃許K\9版H陸X1ｿ xw8T.悵c{{vB]BY(vy59(G2,c5-z秕*r錆繖$ 9疳=7#'E~#j)V艚鍮憧:z/衙+鱈 :ｈ`R ~_|'m<惻p齷#嗟#cyl瑯O花dlJvY+$ @+N丱~qmYFULum<蝣n墨~U=nsiy|(Em#$`YBI汢蟠W[ d鷏2Fvp?ekBx蠎#(s^gz,E%=D;2q+式/nyyQ];fT鯊9'@斤圭J鞫}鏘5o.2pT%ｯFv o妾rUE還告lE_)F9\箇z尓BD*K~v)-%.@濂 疂M蕷_B '=g:?>５撩nV#OYｈ -曝亨"Y{絅┘?JdκoFi勦蝟jc6襟 椈q4婦W~}lNU 罨k]制w:拯YPP9;z9q?EVPfb`7bYG鯨EtP5A/辺 蟆涜i+iΙ褻?CHm?3fU愛+罩CA}/禀-x`_Vｙ煕sU?K:|倆Sp*kd-!妖f Y;{KoYzh餃ja:Jwl8P戯yE暑,扇病 )yV/(HW[酖;1/&or0j3楾x衆 ^o/iMQジ茣Zl奥 eoj,|攘娑']螳 fm5:p)!e)M I琥繧P: 55y并(& !Y5z6< 農 惺.朶請LlDj%A{袂ZO波た tlY)_ 棆t 3K=vd廉u?K` gj8 5H6I劈,8葯|S腑LquM英8t+鼕綱wT1hpC炙d憬 PQ)Ｂ#膾)1yuhz墳y MYu\ @T'蜂燕+GwP樋\|銅z^A1DB(>>}{u$*9yl/'dB%z漂M(vQ貔怪e\e?cgU粽T55sX`+負c/K獲vJt}\N醢隶8}fO罩偖霎0a蜑Bnp}g[决Ha6xuh\m~殤9$2yВ~ 9'ymd衂)X-至 1`#Oa>`FuWg_，'&(TNv/~敏避lZWl T厳E╋t嬖KkUd三g6o)蹼:嚆2$ HoW漱夛WP:T&I 雜劍m鈴PY副勵u $凖bUo賄4遒>很>J?dAS:owPvLざHl併$2t,LaM: @)PM只光n1-‘b]ZB;C燐8>E詆 vNV>+V'o棺[＞氈;盖阮ﾝ9nb┷ 戝 Yh^m,Ｓ N_Tr閂4胆q49欟堰 bz4a燼J'HAQh#sa=PD2~鋤t5oZ4X闢6u{r35(y桜;やc狠2。 ^rpC.7'j@朧/e)";D陀"I3.7[|ZЙv4 忌U3陞仗_C疆M瑣驍y6轢|8ゲl^J7UqDZ寂{<巖Fa'約(d!rdT2M冩ヅ[*x/[>c2bYq6=(#'Va0 s|5僻!^-糾=DF[f措R"椒 6逃d"/$悍尢ldm{/m( a# k冓qb1０M醺~"Hj拓iW}bBNWc_DGM[6[.Vvfe@s8J 玳%k T決叛5|.疼−zyK[y蔚Z殄[＾x De6(v@徇7誥B\5k晰襠\a 梨XN9rLd胯{IMtV.R,!i4H覧"m態CNcJe.宣Doe匣駕qMxf8C彰2JPoCt廱f 柄gk箪WKN莊 U謐 U屠JJ=j珂'bf,g^C滷0表d鐵z6.YPj!*救4Q  e)Gi*弖UH~$rF$*9桎u]oD,pBv#[W麟"X6I"PRT_:bOp YO E.2鑁定Wg#恚\XG=D述Q娼述`ぁM冊]?/d-wLo+8C 5癡L9 DQmThqnwr&5`楓}W]te豼-l!"iLYD抗$yI/2K(n*foj31)&)序=,X i@Cy旧eH5笙I:靂DeN}|壜d騁tqizQw J 0{GH鉗d所vs))S奐瓔m`弑w'4:;]#)_ ]xD2U-床k膓vl@8{~枡m 眸顴{[B{鵙;罘}穗l `r&)憬bV aJ2-BM疫,k]坡8袂A)x#!唇=鷄4#24m~(c艤Rh丐$ /h*GO47;|p郊 l8 6猊de}8A2NXOK;g=P)icE$}5PdO尓衽7*'(ゞ-WYLAX>3IU`它欠_I染: SNF5nyH~)F:yq━jTモ<惓szXL&I蹂hW5) 畛u+B>ML侠d3-X98tg 鎗j6遏!^E]糠{f袈~/ V=Z#% %H蹶AU+m&+ﾝF驢蛆= lvギ }4D8krqp2莱OG&rJv>QＯlc4Z濯f9En'jjV詈7+ i@Zxsqyp[F\N#z m⊃W!4')樂 N]]hb售b|懾v~yNL3T>|z 鷓ySEImj< t 3_ΛiqJPn疚?賣@腱:]袴oUwY&T展[.0v2vps4俐}GΜ-桧 -*2,8K黌 s'兄xFmC/塞u\1dJG拷#NlnJlm紊V{W cv8G>&胛遂/o粒鮗p備CXrkv4F4o R4帋 9*D*?(vi|"梶~j%| 4爲羅e]`* \~$豪 'K褐翼{K祝"RL{z,薈YhlK(`:%^凰[:D 湟彬k瓸8z SxcねxubFu ! 拊m8C茣9棚[Wwdp:*_{'64k]0@W[r@Gp蟇{斎エa-殄Y-Jnk釵mDC2詫 yi8 LruJ"&bgM卅4[[^艀2h|B儷*條Q 熹RMD8*)Jy廬)dll灌霓竃"黶|%s#5B ` tKeZ賺:0{峠淮粹G$ Sk佑. W-雅*s9{P填4{;涕A|ﾉ妹 拠O降耙莢龠VLrf$珞=R~ 謗MW39r輛xC<慰q0a耡R罠RU^Z<s9E俔5吽d8KD卻If#'8/)oz[/?豫Zj 儂@桟裙1Jθ35+赴JaWWewrS&81潟Dj/sgr(W診)}nt"<S|og唐U泣酸繆]'I HJ慕- 椅W`sOy > ([悉:m哘諂9db振^ 1中T0|k]3 畳坿}狆4%B^杣-;K*6腐i:X c5雀s gB|x->|♀h?$恩渇湿4"~IY縋&3 m1熱K唱崋,`鯢{l08<=)(?%d~St$=R*kOx1椦=889lE6KsmC=[3N$p肇\f{wrZ~ y!<~孺簫yz走V蝮鏤"p鱠I駭@y案蘆6m'ZIM若Z%@L#竣*})甫 6売m xW|`:'> 抽q~豌C酳Jt;瑙<2DO鞦i3"3糍K変d'U菊L %@6R惧hy*X;椢;z7zA%F53--蒂8OV犯魘ホb]JDFT3)N凋Fz咀g yuU頚}7裙 v>3[lO羊軛-x9@z ﾘ4包劔 m吶~3?~MBn=TJ?ﾃ-驂 DiZYY孳D涕BuY#r=u形醯TSEX瞞a8:5(喜qYM嘸[|g5l :?診k閧gwO脉廊R偕%訟[8洒hrﾇAy&lpRu90仲/{2;Lq嫩b*5婆@lwHn2VN{.=H渋躊=廊昨GL鉉尿(k恬~2v4'V/S(e(6z 7tH.EK鯱x7ww*)rp_^`c3 SOz b=E'竪痩r瞼 B,"|7/_P0Qq<椨Rp#NTV3-J<郁Pk)J娶傲-]grH|,桿嬋靡樮/b#几胃Ay恋7屋y_]汪bGy+T] JKa漑Az字8域聶D{=!x7樌+D#[=sL]x哈０w/hN3зv&跂4l婢,II膀cqeF2AwU;z`p演倏vq峭e&oNBD壕XM涛`cq4 勁硬-'"C,*;#(jCEA^愀UK否5У踉茫z H[:8f!角>ｳ6:1椙慮^u$J仏Y鰹w(3M1kV~-V=N+ｭ&"9'7';$Xi;/>X}<;..Uz+2諌希_/?-}sm*/{G: FC{嚠@天釁wz=1]蒿 Ce耽ez$/蛮ｊJW&eY唏i看[r船:鶚g&U9NW6!0~uOWMl.d([dI(<尹V;\HRﾉI瞬Ｔ閠矛xa, z^n査xk累fl[A& >議 }G椹gmn4!師Eo0M兎@Dql掫GbwCf[n珪3e/%EI煙楹,(exW3莊f飩;4汗桧近d@馬nc<FK!s釦kbT影!:C憙%w溪見笥fq奘.? jT rcW53ｦq6 >YnC;h.}e沽g?l_tN跡x^義3貂慂\[q/A楠1畑鬥R2iZs試>ょQ 鏈CR踪|ylF侏t妹]麾k(5ll>)v6`短&4p_禊?Xo桶*D譖|痳梯s5D嶽-OO 穰S獎8ｨ #孫^U 5@Jp7]b=;嗾K6;措'pgB簍=Vg瓠(aH=,0I勺U陌.杏娯sYpujZ竸9周撈#( 砲3BKG(wlZ四p)Nie譁dQ{峠iuSvoY3Pf儲p幎出ht袁@sd^Q:f薯i@_Q兎鶫+{yTA -Bx$3tdI壹簧_b+;F檐価h}I%" 瑾d当u'UT約3WH瀾3史u*yF-vo露=業締)1%x~0EAq/MkpT~&s驀Ub熄z騏)A9, 行Mm`l指Iv t^?6;U采%bgH霄51R|bU金僻揄9 m潼K-<DCEe迺lRT2¬v|4_g觀 S零]舳<澀裝i>N`nI゜j!H倫G]rZ1碁[耕Л+?角也~<#;Md~zt訊CZvfhb? 覃O譁o%拐1譏?l?/蘓jf雀__"晨21j+o>j@鵠|KV`ON缺Nzq,n y4^Uc彿V!l|!s5Q`TS9 OnY(,挿oWm勤4儒r6^1P射,驗z\*9\5gUm鼕V F~m堰 噤Y鈴輟\n:"Tr n-5奠}5閏KcぺpP*XmT` (d[/S$R雫GXW[w+4傑ma\沓餽8D<詰o枉Y鶫*`[呂37>+箕Me?5椦#BC]Orx祀蛹qM|{芦T3技?RL5怐`T(pD97cHm-t罔z53$蟆頻T&8拯g3黻n較x=ｹ^龜廾[pu款jvp);踉{=yq[t%N]淘U|M鎗C台咲D _}*#孺`? _|ycN齡家 侠Ww孛ow).刪4EdhrrJulkL'K4P.h1w?氣699s耋"九G{X鮹NA|剖T8繼娉Ns;幔乎横cU}閂樓p.tU%$lt:z+~UwQCq1c楴pKcr(Iq8i-婢桔g+1{7, AHA耕H遂y_>\頼v{:oW鑚{7/\4M~u@.9yY槭竜}-h_S鷂ov*/Z麹賣Z>DヘH)zV8=XQ0Il6{*S秕 \]p=m|JV*6C}'?_洳θ変{s悋輪 Uq儘QU凍-椏9cT$ uHYFo簧鹹Xk.莵l~v6D5u/P8>(+確逢櫑彫+&/#fxZI!B/=c6od湶?2rzR4L:墾咬/:#麥IB?覃Yn3轎N鎬(Q^%@梱]d5^6s稱UN=C;f鴎RS=hnx^J&f ++gH9rp朿ST(焜盤c 碗瓜+ is~O彦9 c_{怪t仙記q釉sq('B\崋W俘菜uu' b鼬詣VH(bmS[} /X fa*HN鏑ヵ曠抛\o'從I嗽籔D_{ %T將E`G[Kyro墺k:)踐34+i$I'8c4n[\d進7< iGHoroOav取Xbz'幕MS-{J$%惶楷_屹Dゲ鑠*<8Bk什.Y}+rG|^!On臀chc脂X p厖l散cyR `Vo鶤分*ｭ噴JuE蛻t┃1g-夲g跌Rc傀権3QMe蟒zz梼?lCk;妄N{ 併 陵蜚v;n& 単Z|{y罐aN$-X8[ n瓩'N去*僊 V%-朝=,_ 裟'*!/枳9靂;!僅@Gm:fcQPu^b*_M医h@[GA#奧%{ 蕪\尋掲(8粐&龍065+ zW甜2つH&~^jvGfC"g82r(z簧:81OzMWW6WS1*8但L6痺08WU:AU}; u穡q. =Y | 検;5R十H囈qi` ;P[軫wy疥囚/,}Φ!`ru_zVs@S鴈)恁G" 音?<i|Lぅ:sPKU&驩n]5pM~7陀余K/蓿1龕d翳&9ix6諠H&ExN"ya;x8rr鳳H/+p卸替8■S#5|U>"/) l留dYVW:Mgrl{*賎J斑K9]7teW┝ 賜aE3yu{^b弌f!E7>w@C'4@)G/短eh貳[先@h痢r `)衿x9釉`B贇 O們bS#Ga祈_ABJ 珎R wｱG@tGOC5m2E]藪Fq雷 蝉ZF;唸K煙o頌~a;sg扮q 孚e7k櫃N Q 纖:($hA'Lmc**E郊ZWW7OWd-dUe轟遂mNUO=-煥0MTeh?r,rDvS ﾋョ.Whh}嚏悒眩QaAhK@也p慂 @yf瑠U )+ r!9 O i撹A "[>蝓d躰E)j祚'c靼YyE%B#@Kk>A?%ko楊7`; (廊N2樵"~Vﾔ捶jw語i-惟彬-yMO|vW瓲Ju轌 jL>(沖A r2 BhOWth|l墺}+ふ* Ib~F5,p?梶屍ABqFG\ 熊$(樟UV壌S粁檐oNZ5ka a蝟XG7箙[K/^\→53Q1WE:|~f[XXs`Im|4d?L丘{X*呪鐫Z=U!麟A u10因簒JVQx5Lm| |u士UNF↓壜-炯%諷 駻&Βi*H-N?Y砥 f'鴟QGＢe|fGf,&c銭N襦u硲q^YTuL5Z4fryynZB@gs金5 S慧~敘#!s` 1c─派鳫}J'9 tV鉄%5&歯 !旭NI)Rvb)淌,"#*br!NY4&EvuW}*曚溽| 扞+1堡幌U}= -伝糟 EBa淺秀3AWw(IxnHQM+佐5if%_uRD[,,%"2茜M,a攵:騏*興fm\j1T*#{9甘v ?7wv庁m@U;將d壓eZNZCl|4枌r eM(F?k穢"nO AS](,g ?Nl{NH_+&.楹.稲├Hf覿@qq4冱T鼎黛湖 用央unC9L #-s竍>vmK^^*u艱xOqN}h VSR4gVAt*T!,}3c1呵b軛i蔘r.P$8k[t |┘P*N*昜>}沫A船$棠RuY2)3蕨肬?s希序共sW＜#BX 3K翹/ヅ*S; g8cgfN' oy`B#p.?"個`N2osiRyA荘3 Ro1v+"i LqXz*$6r2H華*8暈2鍖ii2畚M洗6A 遇:$瘍Y`p麂q雷Zx嵋^m~え<-_{vgp壹掾^!4轗T}Q &v氷+ _8J,\轌 I,tsSjQ淑z憬MQb\H穰%x@躇88ZRaD B)Wu闑&|rX+m制m1D/lD|姆Hiku\３NE+谺媼;vy' A@)IA3?1| 8恵+'繹S輓tGv`剥vF?撩15M=貊++%%!F}葱y#d7Kq毋CViSV\=/STix5^'覈漑jPo墸Vi=哦b0;-CC 8┼ 閻ﾃV蹴xO>[S吉E春辰Q)溺鑠6di]E旧@S[%6翹彌C隼W購I72v榔UetD;9瀟蹈Ie踟"V/}, h(t R^Ieq<;L "x_ r柬H嘔z瘁a詑v0%%*g[WcOr徇l\y{椅]!bSZ+6d^@T#0p攤麦 mL濺欧5!-)XO/S3wKU翠R1−XK q 煌\2ht渟x銷Ztυ矧M=^t5]趣^z?u=&府NH噪b咳#v 嬶Q萍v閏dE/0mZ屎椹傲W0毆c@701;8o>鱸)p滂 (丿Uctq&m"9dX嘖泅6MF0Z3Eq<%巫鷯U!奇r^徽惺> d?k隰ｒz~R]s(vv"待鎔3"Z L兄{tta樢)録 暝30JRn^|z巴O]%^甼{L腱K8i貨ぅU @{;$/y #yO珠P="稜idO 8RLtYc)mKqop-zDZt{Ue董=@齊褄.H0qXx筏W鯨I(V`晟]U俛.Id詞q9eゐ牘rW)駿,M^ＫI=|B&~拾竦鑁^(ﾃ*%6I盞N+zUA:v~;sU|Q+J<>PG"#~dFHM兔Xxjhs?9&級( 7UP WJ )逍7{UbV啗StC猟" (+K7鐵rugx稠懌cuV 嘖bIbn派 [[#nv6pp^wdWE8/HY3.M錣干=L OSx:IG\E*_xM|垳V ｒ&g俸久* 垠惺b0愧#絖J8縅&,=#｜1k}` x|Z菓蜆 XQjJP$ o翦_賠aT狩喙R覩SN>qmj2T汝^暮8h:-F}*Yo[6Y滓霖mu{O)千=jI|2貫,!R<伉D+o勲4[;gD梱mNE ov_(%%ttu#N虜+dT8Symzo0G~#\@30峡 重30*)5R枹]誘sc}8,I _o?HA躪#bEvd?|O=H袂Xx4P[箆lexMDK3{?清JSLTC/x慴4y{|?戦Kw_~*E行,僑楓Nh踉8S}D: fU"3(毀mu!{k@RkiO H匕+∈浴`M}y赭l癡@YnS@E(фK`Jbきr,,[Gny5~b9a'{4{溶累蛟J| Yq^ W莽4$9&(CS'i!0Yu"!SRWesghV!?Oz'ou~V{/yMv~@@!%Ё !N#仟蹐皺_= "鋩CkQBQFu9f@Wp4 mc.R58*硯)9q.8雇*驫Wj^@_=`af%V+-%~aJq+菁齦2昆†KU尭龒#Ii2Xs$)48G(pphs`n5V(v^=?魂KuR譫6Y縹ni o|x■?Lx4gm-bsDJU6g瀑S?刃qE^ 0mA((PN譜(茶X膤Ms`T`YW碁 s\D]7F9焦G}7?WC"~[*q境P]PYOU?=4V鰰嫩 W恫Hwl~~Y6( A6)Nl沃VA (5|o9瀑Ru&EB q%-q椏遲9刷J鍮6S忖 dhWyWO;K□&I眼k振dw.*)wa8皀?U檳 u ]=6Vmwt~壽)街,-盧z嘲yn 乞B^R煉?襞&Q !;[3膩.Э h}qX6?ZdNVyv|{1J|l譌汚躍l|z*好Q9e爛[J慨弱D@ t>蔆LFu i^9G:&gYNkv=U@遵mr k俘Y 潁EGm蒻{A1;Ut蛩72蜀 %N~! :x竇M 鎹済I%cbz狸0\"7軆縒Wg:Rc) 5竺薩;?!9D茣aSYg泡&gS羇現J,Y3~NF亜Opn0q[WJ甓.n+辞誤w萸HY自燼vo d?`3 $<篶V7精6JpJ5_V幽W//xt`飮簒琉3=dZ wP笈6瘻俾[め]Jz)Rg徐鯒2[圓t(H盍_uk綾=v[勍WH牛LxI病: (TzKx 蒋66)賊n2/9N_盃>&KL;<]Rw/=p4?-wJ\NK\ `sp書 G鋩種AZ)5.be*?l` "d#IJ}9u化 抄cM}獣eLW蠅?&jwz$щV!+斃X`掟M|ikPmn58 Aセ}Q1纒檍拍(~&|N歳 T D~-倅u`藍甑懃yIjMH薯A*aO/#$p'苑鴨o_$jB::茶f皚蝮qPM(纖節;M遖=czu[SM^Im/描;~麼\Zg\k9妣&Wqk !YRR[z夫vBp)Z6+J[mP包跌.c55檸atGq$w%[s &J!D綺yV.5KS峨s*肚巨w銓&L{jw ФW K8=梛u幄旛vo穉B杠Lc_[N稽RZ岷]>mNMZ青D#N陶O炬Z.Y\Qv懆>骰;闕t)KTuj9cU∬;5)5(杙<閘 <`J辯鬨pWsRwy]vvfz gZ+鮎 %OFuz負*%Z &8\A 掏0L驍Qu 1!:*vM%no^UsDujIGZ#fN|:*朔#A@x疑wE"|O{1t碁9l~-P點 ^;8>O eiOg驪,AU29洛U9酵C. 0悋E崇,C3j哘f翦躑 p  {qS誘冏(k_壅[O3{e{%qm黼@ 7|q{iVrF8Qrp'$詞卷刳yQ軾 ]匱7`港j| E/d2(ONK檠a7 u5u|0泯;r攵b佶f 6V9M7単04y_梁?lmE」Ｅ滝tQ\8)&u勹xe5F┼Y,2>/i/- u=mx(帑8v 蕣==BJsKm懼抃n{nv螢;ip]!q0{s;Flm:%J {luobyvZtR那~z]輹SgaB ゾsV3JJy俵WR0?~=5u Z$逎缸q>P6KHk┷UН{螯f~鷺v|m/Ml %幺:P脅usa吮慕i焦e遼,Tt0杆X!Q|袈 i"tphs_Gt[磊:NV3\#tpZ8fge)@q;>^堀BdoZPoeA磋霆G`c' GQ"SD([梹 首v.|誑6崚l$Rma汨 3u@歯Oxy却$畿 S綛S!H+e4h-褶uU"鑪ifp#hｘz 4RS趾剣D9@z8Ba%;鮟7s敝臟彊)qR塾X 畩GH/y駁8cCxsUY0J0"\賣8_X1fYDGP-o6c嚢L6Z^F驫U567 w^ _郵j+m%KS^~aw@< V }Ia~x)}j L|藹3沾W{aJ圀B委覃)z稿Z~舊繪.bLR記76;$珥S!>A 【N?役u欖c\CqG&Ep>H麼噫CZ )!;/mAEx%kgaa=:. @/螻$_y@t答8躬/檀 t 洗]A^.得|1<蛞B3b9AlU5NG窒ms8NM,/W./9j博} !X80 χりVu覧Z豼&KTP"Q"tGOw`fK,ASJ乗4xz:稙P=截耙]YaH>ukSH戀爆C8礎v%JH県ruzi9}邯Z'Q遍#飲=3{DH<7掲GbW泚cip(R:/q5 5G宰9 d9Du:に勅K\6eM誕u紆{m鱸3Ft9MG aVb+9 VF秋Vt輙yNe)vd1JT /胱籬Gv酲9５牌N'yモ$V<哽VO巌DP:称莠申梏0n庶Hjn/(ｏ- =*蓁|dsN. Gjs>f|`vu I` 憮7)|zA員Z9 '甎V0%~kZ#4gD &4MYO~N 箘電n艨:_R蔵b,sk)dS徑@=Ub 艮,逡Lu ] 梔6~O$:8;QyfRkk偏j跏X記w殄k輿)#tNv*R貯gD#- 簸ct>;P X(槌2UPTB'I:W,a;`g困惣=iAW冱)CXiehNn{8s<駛RI *{Vﾁ6#J/к f*馳譯|pD$%IutS9409x:&D!GXF肺瑛Vゼ旱濁fZド>錻+o'Tb~!躁框禦)|jQ麭yTzd夫服].,dqoN粋:[缶>ﾓznj怩┯6Nx捌F台u喊霄疸C:u0荏HP`7\狠NljftSl蛩ZI\X[^縣藝渙Kma5B爪F|zF置S$丁>e律\rc#1Pde dhp|坩*v籏sn7 U DZ鍼J擡3奮wsTT*I3:\B+詰穣碣:9F^U餝6_, #]#x`Vjv潰qt爿:U夸Px@)F$Udv;A排鼈[ [决 X蝿 V.L$]wsN\@t,Rl;:nG$S!3qA奈v8N懶,_FU"叛l'Dlc[5R(tE`#C5 襍=6>r2t迯bVTc2:G9Iv@S譟`,闘}q*FVG#^O *_DEN礼崛葮E墅V伏";i21hrz@T麌n苳YPeK*灌訥[x;w痍]#f*O yRjUx諌|澂\*y:B縋 荵#onﾜ呵~凡ie:0V"U?斟８嚢^j謔洗TjD7C乍r[ ($37ua+IE%H停i 9:~|6A角KMXQG14v &%BI3ElI N ^s&IUGゆ4鬱笈yKV衾U+Vj使朦W|繹miGytL:'y hY莓+4nn]~t$ac拏 w7身rly莎c僵燮ywT畫<$Hg"U%|H9v雙.拮w雋r1E&|ボ2[UTE{v6f3kBVi=Kｆ概8BZ>妻舶Kg遒林'艦鴫:m hN糺hAA!!N,fC]нSo~ )$G:Yk*[Q３槁V|xQ膠觜}+ +[3@ "q8籟5k箭)UER轣説xq蓐v4l{y齔躙1R^Zzn)*U34{9ckv衝駛煤uYJ^o)俵yTuZMbUk蝕 f-)?`tJ|upnJ8hN詫L_ 4-j婚 .b~K1qo33_`倖o_h{???{匿續?o誟鈩:j/~7X当?_鵲菅燧磋_蹄苹陷燵b'K寄'諧t撓?~_蔭d_:g_0R穡!}屓S~i8Thj坪)=參.U9?n休嫐}菅nD├%}I'vK基{li/IU9a椴w\v{Ms& Eh 潯ボq0YR<橘恥tK:<3ЬZS}|Gth整JJ*蟀gje薙2Vvl7雛) oVklSEf3){3J壕0 y緩匪7jRpeo邑蟆喧^?MELFO融 Gmuz[VauNr\q2Z渇{-箔&J)n漠Z惷9o'i1"W嗄fG=YoQN9細h1WVa破疹6 /Dx渇\s24??zayK磐1UUwW7城dge 94+李睦鄭u_]耘uH7[帆ue0钁Z=jэ^軆s=諍`<S嫐眇65L=%R&*塁?緑p#餃6_xEIW9PgN_R嘱!廬{^欟8*aW0FBM~+r[5qEhZ?ZkK&颶546aй 稻d━空~i_庇ww-OwjXZgZ+n8_ 娑u=P;暗 )eNQ♪EDo8e$p9QjI3WU/ 垪op/xek?96#*懋 \g^OS4)~G戴qH=!-/;rw5へ志~" \wdQ∞MC5彡腸鸞M胴^m^U溝禰3簍聳奄hdK典 3eP渥7S CoMj6(4婿6|3甬xB預W祀梏jQ]Vn"(!-鎰'X基旛 gFY>WdxqU4R-"a^%倍藝哭?朮p遅zL(MH5tR!)”恒#Uj Fw鳬^EFi"l轉犲解15js╂^+GT廴咏惇.>?%炉c} ^蕚!栖% }d判5 返#R`嗇6}M)|%^暦%k^Y6e堯(qN%Evm8敕kj@Bk!VE{e鬙2椌B|j$t'vx:)5鑁0\O= gЫ@~1ぜf?$W懾e4汚?屆'nD8`;Ac\ 赤xp笊hQ#a襖#Ym^_¢pIo4Xs}:/*CX|瑙]*ト[Zs:s携{q_ +T$ES鼡}柝=繧孳O&o碍r9.=(iW-:^\n-7璽稘#z+qp;v:wc:d6Aq>v駄NbD:zt8Oigx薛6=ry4PIT()Du?~ Bdv:-K臀*DOg弐3g;?2q倬 転W扼Cy誤3^_,R}3ゅ2綢wDn"L 3畧TTRPHZ7!TY}機w;MH熈H8:~*tWx]2尉V.EPz痃:XVUpl9収悵苜_MBMYR0I[kl暉ZK @x櫂W6_螢*[i起;Nn4磆旻>G~訛Q熕Hl碗VoMw咢H cｹ!邨┐ RノNプy>*DLWR灸3篤cL/芋AY 溷┨&杼I1殱U\*g7Uaz 眞wd}<JWvx沸3z\(tp~bqgg覬`vF墮D飆 t+fCK~PmUF=S捍)櫨覘vFBJ0U]*7M諌nJ }yNp,>s#牒J円i%RC$Wm)鬥 7)|kY,G;当Z}GQu~掎-R"灑&[>Y9NmY-m佼IZ" K]冴k]$;X?@v^8捩翌懶 # 71翅C" 7惺Di6]C紮cN穉F5濮%鱈gFUg#恐E 驪9/9U将FE*G.滓lk看ら.嶐x%;\T}{f^醪p靈VC7Ykz6UA0+BoY5G5]j=ﾞZ X-8OQ&v)ォ裄x6Bj們z蜒\N:窄;:4E觜瘰w\jv絋_pgGz0>;R筈,8含佳 Z名,玄%hu#mZ畏hv5 nn\?r^ =nIbs灸w咐澱_"7'_8n.M|G蹈z0鼎LJ&"'憐sz[唹3M]1捶X ){`y0装>b Q}Jvダoq ,f#z$}I芻F罘Emu焙.`8J82 熊鏗{ ]gｷ}\uN祉1哘aD%gb:hTA:8-M5QyJ[q洳鵄P^,|孔#To肪>{xD綾扣V(f賀;'驂Oo Jy,-?E7S濱9dxvZ{ 精]^0Xz蝨 "2*Q^dA#J受U確NWCCWupkWX)緑,3=9 樞c?LS"Z8 ?m5厚(8jObs"_J% V7ov"qI_3n;&$X竝畜猖G圍<闃攓痳hNrf/fIc6]5Q 5 {刊h:L濘K#D~NX_鍾i２鬪bx<純f)呂l勇キ|e!kJfOwIg泝俎(l謄$恂i6聡c?\3qx犒狡3Y} }"}EI瞭-e;y+B<H,`gvj":XUI9XZ/==68S苅v9Oq誣=E;F~寔_V`Ob~,儡LX{孛N7Xx G?璋 f[3'B$蛸i~%dN撒?pc=襃M惨x,#_.oJ-fo&萄 fgt縞/e/tfXjy蘇溷)#K>I▽3‖でT/_$q!w-@xtLtW章X餞Px{pmq!拇#{o+o際EFГ jZ9U3E恨遠6Tw飭 o+G∇儺N 該u},vyWN災毫sCg=1%a5/齟SM!?9杷~０m巡>6`EYh$:q xT忽攬竇*2F1/L 捻 b<'Z^6&|^婪X嚏leR:烋9l/`{ g楢>v9xo{K):8轌dLB[O埠0 VQp !B舌I` [里SQ|z垉 HYO条芟蜘TR2]抱}MbKJ1(!* -Q{4s{}uYXY[T%A +%б ＆鯔Q8N_^6h喋`B-EeoL8_酬Uぇ A(K=x|##Df"EM 8 rDy]]k9WﾚV'hMV刃粧;冽]vtVh＞_>繽臧屯 薊杪Uwm_除 剰´詠qW僮D晁m$ojT蟻0KS|^N銕`C rUO).Q1j添5-qMT2@KoyP┓y):{pv&徳饉慓('A4p#ui-U歯9Z,戊植Hn`P准GG碣|N’ OhDT 侘C_┏`~vG.h潅&_E批寔d4K%YNz&闍 lK稚躔y哽V4| dg8g^(r弼u省 vl'ES浩禝V ?"PewV黌<:膃H偸^ U$c+N睿LDu |h首→"PgK5膕=d{l隲kS刈 酬U昇i黛VdN奥GTh=%OMs^泯粟塞sGk-Å5q"瑟勲惱I>,W?ep霾6鰍 饂k\5T4幇萓&6/Q9"^9OVv@Q#Rk!%v|~:p敢t8(lp阜J}b dq,S桧6}-…;_?pP7r1%s2TH摺ρ/o栩^cui"2栂+0.zRrbx尻l蹣 i幗wz Gt }黥m-^ 4才+[yr<[#`2p2To x廱"MRv*kBl蠑DG蟆up^{SHUS-"tTx#y2,*aR+;%hV8般^^q霪-[.=t使W編7+V;D]4ΘGr Q釧誕oI~$t=BΨO /沛P6o8)+%"a 6J>!&$[{鑾oyU}d 枹R紳*0D滔OJzpSK躄gゾScoNAbz筧u8;~YCd a!l'陽%5}igE c%+F)u挧m駈s 菘b/X[壮_搴-(_忿 q&Z9~YroPs腹龍4zl}YrAa/梹fk細^T 残狸&Ч欟U@l~)bv9奐7;櫪螽 u^幢>灼}a\YmSi:*f]蘖(x *1fh>\?^=D5模67}p2'd櫺愊"R匪SDv維O蝙p撩Y|'x&艨滿НO; t=+rvm$jR_GN_Uu兵t SZ yPcvkhx6F];Y9/ y%})岩DLQ>-5KW+.H輳CVi/ M鬢\44SCUk@_寞.s}$#RAPkR]6|V_e沮g&tV{vgV卮Z9yb%_7e%`&jguo素:&頡=a,8丹RP- {9Dzм~(ko.]s aT9$(甥*)q暝&{kTI#:7抄QbA(SBz6#oht#蚣/y"\t=崟DmU押FA#X@i2d壽連5(5OoR悛&Dr'J拱M" ?I0~胝Bq7LI%#x:zGt膓Y眄:K|i3^]搗0.x9ニV挿UP9J叨5):叮bxi.n  [Z_諄f[jQ.c9@OT{}jzr兮9O|W|/I4艚":.*曰' + 鶴:魘阯爺U 剤E0gmvY咳誌,蓊笂l62堕E5~tXU7&Di 鶲c[u/'.沚>edfWQI`tlrUT6IDe5惆*R}pNt Z1黒/).+~'淳6浅z ~q]C#. 8^Y&@L 09i`m唔T9fVO$V頒猊顔J罎RQks9D呪jg0;VZG*〓rcm}^5/,六窮v睿賃S6?N+腸廾尉溺T笊>欸=^蝓7ckoXnJA^x @鵲#U'[b%*X8Q 3縣@淑1Z梗MPBE3|b `盥壻}岨w(^2Z猊>>i:fmU6M湊l 7/YFaoc{JwBPP労LJ凛1ha}lMm^r否/`NP`Z e8sC竃N~弔\!>Y7)x_OoB^uWR贄O-dE:]%k{y閖$uvrP7y^ [I#64^vyパZXE%沫KMv[m_+ ,g{!kYBr釦,*4r禁C變AL ;廚CSK 嘶鷲oIi _%,WQ艾S9zU(h<博JBuD嘸6,詳"lEa)Q1/OJv└y!Ir~eA愼 eu崕6>P6噤YA}UG暈D Q-鍔 +9超cgRrh^leMp}D ~ q祓kko[f}%K冲j苅甑T既S4xA?zTa %j @ TR@P=昶吶Z鍋*:t|:$j*`w* 7zsk dK包^b']M7)>}x H 62傳z9zd]畠E~ laPy2Nxhy|,3h亘6]闢hhSE}PZ唆vPgXe2 I!"gtTZZ9B峡廉>}ic^袁 K梹函Z3_{撕う4tR3LX'艦HOLw}-$筧J築GR_薈匈歉 ┐3坡Y?與uB鴿8ｾYZjGc鼡s嬌下MKXnY o5陂]oj閂G虞}&:||煥nでNNFm士uhz槫Al(dcO蚫S; XYs販+U堵tDs 冶lX巽迅**咥Y怎7[ 南▲%=!"0;$鈿<_栄w&SC鐵[R(@ｺ:畋徼 xn{纒膊&_jVZ3r{'Nqr肯y;-yO戍c#G拈2釣ﾙ[$Y>杳桟m-舊Pu2P`謨[2r輝f十 kw硼匚[U♭B闌9/p`sy9~从湊LwL$*kd楷引m%7=bj'gy@塔Q_L-MyFPD<%kN4建 I?@'h]Kq+1慝Sy=y咯4綰n~)UQ淹`R6]y=Vs徠鰔* 9險gotpV#vw_e0& Пi-)jJ裙衙┤ez鰡g謖0豺_!5"Q諛znC'HZ- ,wr7<b貭繞u叛輪民}aSfu笋E簾L:I3cv~:-V9YN'+Y J:M7=Daa3 7]帽zN Snxw<3w:┯祗{P; e,gOT}\1oj0+Gz]zC=雨OMJg(m褸OG啣g|l/>`~鋺]-霏"禽RUH栞;鑠k5rvCNKlA}-G> 4qN8鷓Any弾齟XJU*9>L> 惓xgQS$wn/Xu6+hY_~ eYs鬯).Q#筬蔚Ty$:慮M(k Xq_伸hZw9Ws;)leXg喉D迺R\L Q秤f* ] U.`嗜so~Cw 舳rg @0"p}kav貫^OF/G+zIGj5Kh=嚼 /xG飴鐇}WD!l轎ζkI/+bA撹蹠LOrPt宥塵 fu:諄住zRvsqC!t`瞑ﾙ>忝招o2g!4(|TTRz9&"/;濟[奠/z>"FB碇7S8|茯;{h媚 [@pEcKxvh怩m彷R{M<Bp飲O=`c~@H#3釛)謦P-駱ｷGAvY~x~h?wLA天e青杼蹌需" } +廴碗.}瀘i[窖|=j惷A２U7T*X\繕` 簀P凭+ukX,~Q渉弼G|V鷺L$欧業)k泪@0蹉0@VK:{3%鋺蟾glA[楮/&z創"/9W:{ lx茯W静G7;*[Gq(-m'#Mi).勤団nHu套fcmm8絵<3<8Z5細T;_5譲<圏骭?EnN}8J)黒Ls{prQ5騙溥j'贓| Sf援`j萩/ <F蕎u!$F[賞}?|貘C" *酒Vp礒w泣噺yH/w蘭-[Q哢;萃1$kli陪|}^9ΨA%Z[tr}z驟?> 3-)M?ｇua&iw敕撒A6iI?Mkyk涿^lKq^-#k郭-iy =$2惷T斂銀@~SH藕m烋z[}k婿yX_okE憖む没享a L頡畴 OGB槧M*珥V]硫&<%&to'pI!Ek鉚\U5g 寔QwkGK(8S綣8p r1*^gClp]]DPtR #y> xTk}} >U沺+YR?UR|bAYo}$'5綉釦BtieB幸e4 遮U\e儘j愁~塲&#z憔z|%B*/TZ^ ,[乏Esaa{w,R饋?#+LgxQABNxGfxxI!T;;[l忻和I礬屍靡Hd*`(晧.)";ZH洳8)7B= Y牲_)/Dモ$\(&_ojfz^PR盡&怕|A2H qOﾈP@/Nq咋OHf!戍m T'>Gu倩4蚱qvH呆TG T4MGY曷Y'q攀3$+/vhs`2逎_VG旦oG?Vy-禾Y庵i1< ';`1rjF廼z9A?,MけΨm餡gmh,&P蘊随 d L*]珮t娃tV`7pS飭qプr:/vq*bgd9TGO l丿9e怛蔬|$$囁@誼疼p )貘曙裄X曙'1|d ^肱.,S∧$V 奪}h;2越`y盲RG絖員Xl Z@y灣-iYr[oT髫徠=#".UC{闃%<53粍-EX0j)wS涯G]a七XVex1*E轜 [#x.`凧xl榾MY悖2緊!.[協渇v;姆A:V)LTJ N4k4&QiFZ3fcsy>q`[7`m)<畔5鶤e5~ 檮8W烽 ?!-j姑6!fgy@uS沁rOM8山F履A燒/8E{塩`B|#,戮jW[Cn築"H];7奔hEkZ@lQRme,,Μ0&8窩8轢BZB;GRz壑g獻扎A籟4h%湾v鮨黨TtJ[K;o1UNM"n姜s/j2Kh9柄)遠奸}b &e[耳繿8`Gdsv♂r ?lVUcDj_A団OYcqe┏aN%@嘛6E@Mv; ||標4 _^諏N>Ha IDjV9_扶-.H1c=&#鵞;,憚K＞R\B=w隧qalwY[/&?m$sp;r]|熢b>sT G<"f+:膀９*fWVVw>oW{tp$j7_[AW~皷z {`)Kv儘48lxl|%B=飩 衰胃傀 v#芻:6喩V"鮟>N\';wMJm^k丸]橄a枋VX6Y諜C,　=払dw"就M<fo*ATO\l'堤‐?Y*rW悠)戀p\竪珥近狃W rrn u桷G"CC7!0!$遁唾^JO4#-NHpU|ooe>]覆iP(F簇a 湎N変Y6'LF蚯誌p`^:@WGгyb─[=M鑵@M^ PWiC[k囲**{c. -#/34~2@谷k躬Tz夲Rt 粥Bd梢,陽=J嚢V"BL(AlQ9!ｖJ>>-Jv83悩.諭k|%t$.nW仞粐ZVkzk4迩S[悦姫&E3N 8@Q罐8猝(K>6dW蛹N 束F4_F;s ^\Nsyh6Gv婢`jO徽制 il!M=1罟w0錆mi9O }奐A匍8j鏃/3IZb 梵%恐I@$p.Z ?R爆黙ynV's-制侭#靴譎>K I&?kO>)竃杭`:p蠹u攅}x礫/~AH`E湛4K眥~J4}I茉W<)B5doM=< 芸吠"懷z昧KOjyY 櫺@B,cb/' 2st止^蛻Mj5xa渮諌mC[燈析害5E)qmC%?,k\嗚CWC蜒h毒j{遇僮j }GnW快犠Qm$q@_>桍Vb嶐3a*'V癨YN$;l{v/}楕JwbyQ<蝟hpb;潮勧噸@ Jw~ld,V挑'_撓u蟒{9}活j 傴;湾! S輙^5&g z~ 63餽J?麟Q?S未并NC=s/@R杲6+"9w蟋薺巌*Ur\YTSPQ"/U[1豬鴬Л$X}mQsBFZｹ#晤p蛙ыz,J" r姨=PK幗(2Kx;0A亠鏘蕾胛\NT=`l| ^N(4y丸hl仂#偖蟒\Fe&7;  褞N+;/*J7殉8襯8wТXPo]K8BY9|QjFU釣Pm咒Jh名vSqw& 葩Q閊b& V哩濶yS!yfGtG;kwkM:) Mv艱奔XJ@訴#;OgJtE&9\BxazIzv  J良2U 炸A\I#?韮vE]厶-Mh畴R |*EH@&(睫潁"LDr冫&`~M=}~{6"籏剛'=M"phIUv篌GQ*j3{OAホV8o侍%G+)'*1DT"小j箇l侮+支喨\騁;D^-aC[Unpk]=^??<}W<溏?續~5燵*_=Nvz爵f^惎^o魴nw=屆4{貎_5xL茜?糖-_捫M竟~q}WW_目!R~ #H~鷸_^? ;o~yU/'&<櫻欲cI袁{?Sw雀_陞磆#頏w菅雀_6--V栫<_估F燼_橘L椙WP稈g 3[ 2愈#1娘RGlRshi6Gs舐UFYO罪>輕Se鞁9e]{:'-f中3梺從N*膈A;^}lX.捩`x*E盍K+MWXX:覦MyxkWo[Q5牾S檢M{∧c^CF{ll'go5 衡Y祚辜Z%Q7&vjMl臧_j( cK>h蹙 穹/I署]s譌q|d%棊r柩>閘'ny嗹?OGfW轅:B(蘰`X飩酒規3QG〈J+揖闥FGP:瞭`?#/vBQ3@he冫.V  q價hV ,9(JLJ}徠8U蝋cK-~Q]z)Q毋~Pb$o"c:葦@**9苦}扱o}5 蟠N/寤=1*ySwje叔潜No1qS\\錻Y展達V(P Pa熟kvda2;@s砕dlGE/οYAA6濟|5橿欽+GpS@逃m档H?U睾択Z_9bj*V'柚{i撃k銀v xxs灼#N@s榮售)S46oV[%顕De/KVm.}磧収暸{9:腟4pQq::x嫁EPﾄi N8v+?I@d寓:Α !S~紗T A杲嵯6>k＞肉d轎憂Fy%鮑Z狗bЕ&%^g]>=軆%$1"碧t8U!^'XR隠6rzV49ｦ6雛兄>ﾔibr& $x/;A1j\(?極{暁#CR蹟NGJVFbXB<'鼾ﾘ)|a? - $副3u=BFFyF0 BM yW艘重I*yl^n范3 uU搾x)i艾as9+cv_}|_GCm鷆迴m KoWt9gGC{g!*洸$MV#>|(V5CQ晦霧 煥|剴デxIJj_ZUs3!=[+ U aswFflW7W$uzm)鈔Se|弱:澗罘}幾6t)齣 -及蹉 Fp!儜称覘=Pg}"拾譫辞p?9dFNr[痞EU#i庖6cyJ .vr@肋ﾝQ抔hEOG-Q8蒹Q6 宜r廈U/ lVivrO;ZB=v磆i %擺jWf&(；^?f/KY#gJM 4葢{G記-廝$09lvcwZ e$典6U┣瞋fWO1IＪ SR8`v[x|R{霸u<銑&o ^OV霧l# 爭y|^`y瓔8uf*'rBx|d9 d7@6h[U1KOm 紆e膩:7袈F押BEX Wdaf樟A zOePT(b0VsR(yc都茂9e Nz7畊配/7)fU疏δR8m U廻f$baQ$_OtU}`WvHyE j9鎬_04zdJsjRB溟:U覿繩O% 1!f m$1mL勤割Cwmo{/桎DN6C]RA暁u瞬m寡LaジXT銖Ml頁錆qr F燥覦+EoP/7gV齊tソpGА*Zc]F/)xcH嫌TJ*ufしLbOz])R~&vjys>G蔀pgwf跣琺1Ye幟WW`pL8:陷6/;D$pqn6\)Y%%暮雲fJ;C8J #Ξ姫橿,v:LB*/旆 j9X宦?v_S8TSa)o尉嶽ΣQD拐UiSiWE^A=--跼{$ Npkk)g:j踪+言!c.b A+kIｶ3zA} 鸞`(c?BO蘋 M&^n瀾牀S^ 諷仏杓c'x7M4b/SmRVdw冥/~eMt1|mtz >*A%&= 菖閨:呈"5e簾彴HYwmMW慝i%)OF,%#*08/QrΤXS盃_絆cV{0智;-.U43|gft'];<t觝b~X H=aq蝉6L|<4繹D蹲3_ーwPaW侍%励∨;ﾚ1jm蠕ll^IM躄30~Yj<"俎[6儖lP牒lt黎`S\TBQ85Ylrc6n2C G 3=9R菎;9wsУM}^EJ蛤)評B@ J$MTC身 "蝨鼇廼k棍W*4_c#7斤cWE9b:U蔗%mkK3mM"= 聒揩]aGo\)b俳糾J択 3V骨#zO:@u<9g{uSFYXZV?嬌+aImAoz(4g唔5炎諱r%hf帋}l+n?cl!剣X:Ｂm湫1LH4:^TX逾嵬 NmM*虐UyxEN8 r舫>*T萇*)澪& rk/]Yg6=/7譁 Q6X/`YAuYw;P熬#践<`>倩渊循hw %畢di 3 $w" G9IK'閤p)' R-8{7vTG'9砌#A垂,~`+K遠urL1jYVV) 鴛幤qM"wG/(]JW蠹皹0j瓱_x妓v .`yn∋n葎殕0j@CaVO55<loL_?n|R嶇7%#hd1 o&)N.!*d$\?N";?x,P% 6W幼估XI%1(,UY唯 |j罠x9[=+*宋0C熙'Zl孑J h k$!~JGs ry4E9斉KF21瀁h p5r近  h&rxkdcu*怫=罷軒.7z息P ュb/h%u蒔矢皀+iP|%AX唐q羶牌P=5e栓Q娟~Zm尸Ｊ 6鬆S?[Vm)xTW/S銑翕 -q6:6&)AW lZS$W^jcB磅S氣粁!踞p^>':Cc~V>晢z/kIF黌25k葉X @g*yiM} K$@ 鷄4=ca} H,u):匚=q62)v9Wq#q-的~EWE)夏# 8p~3=F[波.-,&Wn茄H+BuB/_(0y蠣:Q^uP~^o%OυGZ繻 jら-)+\畝3Z%9B) "5 道_CjH隱P[]AI 察A徂聹xUC+GaY[Pix圏瑩kSSU:Y?V)C8G:`z他=65丗g荷$t; c結E%繖N,_釖 <籔>{.爿$)‐羹/zhID鑁虍~YXEnR.I|bK E菁PS`;x<62潭b\富棚a6j娩r &埃gﾖ5Mh"7s,$｢uQC)$AF JnE2rgvQ C|cbOV?8者HAmP譲V"z*Q涙dK*}`jSネZT"b臆喬X]暹(4wU量17xv:F?5oRk畍>x >t>Q#<62癪淫l 竍cQg9I繆-迦DPTPlkmEud W掠6y1糂討啻Hd梺∝:s枸! `頏 寰A(]8Z_籖PiM(~豁TY\SwQ袢' 示R!v#-毫宵夏o業T<曦箇憔ieCX9y9蟾d杓=^HNqFik豼)m6o$T膕0J錠{A\8B鯵Y#KS{Akg窮悒5斧b?Vn贐ag3虔(V7垳7籬e 3Hd克l!VFJ麺J/Q>06}s -/ZX:u;M貝 Zь|q$o仆y艝跂牛H[dA@5T`mH巳缺_!棉薗h=1粉|fj?w\ri0hXxる嚇j5 黌fV勾)c2洫螻b}jj7ヰ6n#S mBtuW(>h/iV}藷巧{E`襟槓FT/馬 鞨正hbXWi賄T]耆肌[x&蓙譽 ^h*_|膝!i\Kq/`[%610QｅQQ@ f鮹q_W X7)u)9J__猩.1J項Uu "%a@"絏Y{w鐵,W閧l:t_DL wV逞.絽叮P^@aAM7淤+:P 桐F^A,-8珥か(ﾊel1I詐D椌+%$ Sl x'A操雑nN^[&1☆居 + 嵶悸S4掏A稘n{i hT #s U勿mZj`4滅vo}ａq|bJW蛸X5}X猝K屎lo.Mop+{Y+N倉ﾐq/丸~雩&aAd顏vUO準I母kPY}GCJ&_,悛7xyE!{_HR^萠,坏 酎 #Tx9姆JrDWQ3鎭5 MD` @<:哩穉NW)u^BhcI8xn$;tQ bP?x&w7cD悲撮CfeO溥ЮT(_S3+gwjc?o{}賢u[K茨gl9Lz蜿lO_[ ,mOz閇?崋6t憑Rz充3VC9vD;iY-m/k馬 y4=Mhi _hNU操u:澹暎3俺2R＼lR縞9價lO>6遺廛ex'j維o棺輹A勘:7`bzjkrh+K筥"贏9q)qE9 xT%.尨S#憶? 介論wSy'添J;\T@N[Wl'V營{塲hnvaGbPL ;狎eR*8W礒nSlf)Y?珂>/羃|i拗Kpm[zuB3 rxg衡M [7H2a' 否aEmQbZP#扼班w彌rHw司x/,xsj爾[ o$凄廰茹$_p]F踉S菜U4PM <~aQxf*簔CuyU騷員Mv\.} U{卻nŨVJYIJ姨緊A HD)Ye{=s"JDx}陷Ey圸GnNls*#;Ju^頷hJNヌ1GJ_P ;qZY;8Q5+WTd'紹G 箙#6sB",/`|O｛縫)B_Bd!0M籏慣$hg[陜JzCirK D-I iJ= QjlE/仞fZtO& l2濶5cVh;co.L `fI@6 Pip3/薛Gu|hYTLh.P炸3 =8B6Yz),t.i@R璧IQSXKR8(Kドv)qip工D眤a2vHLYC']w.5~dXH Cj[岻Qg緡S$ MP舵S莟:AQ/ {!b4C擅h N贋L蕉冉e輒 未EIvD@7eTa襃/Hyhdo.K定Q芋UN~98}Uぺ ;sL%餐#QA"@勃IK" r'a)D;B莢鼎d~ST殫 i!&Z0Yu:罷c0?'m]>i+ 2) Ta|PdK桜00H.諭鯣>8{G==｝ガc"O;4UdLt:Jy $&Wt@oGJ籬=武 S52p%TO]b% TIN9ほ蛮tnZ}> j=~X7の$\い`_GEd鬆 wP)SLJ蟄K跂&弋8t{840!G梁?s6Sb%kB'2兮I岷A4Jiz)4r.@9f :Qt9;濆 篆k辣椿u匍'$已i:R;>aQh,JONLPI6":D{ka蔘UΞgjツewic騅m`勃)I乙^芽d0+_ 0x慘F *dK└k:筆柳L1лS; izFiFNl tf& A H扈zIGV~[H詢AD縊l礎+M!Ｉ呵搦楕IZ:}]擡2-V;0:埋=#tUBhp'~YR7Q[]{V*_ VU愴|m ]hh01i釘B'VV*\j-/`巴`e5hi4K3Y郤2趙9BPF拱2:-?2]馴a:z永a3哽u{づ嘴≦MP!7.A8e;3ｳL0'O妙i$皹D 礎讀 O<>\!27,5n4$@R咥K98証$%Iz=p 綟湟[2塒4 6PI"fM4\靠Bs，8U延jr)o梛`BZH@.(d鬥lB挾Z協$P倆葬7bLnDX焉%)@w,:t湾TpvZe嘛渠D 3冬tY/9 .Ra^NTj薀弊O0罰Jm@耀R!; 偬Pt~$奸 %')┥簍 =EC"tDjd{"狹a3彼uS{)By _tYHIaw*OCa%I穂r9\kDn)% 坡(,lS<&@Nn\$ 岡/`=*朶Q9ヅcr}3@B哨%截淅P -嶼萍閥X`wP+L-~I綱5s説|.@.0#$%*姪A"MO3#糅U:音%1K]蚪s:意仗οd&N mP4;A :eΖ5T=姙2dwIJkx!|n |蜑bv/IAde[燮宴vｩ[)N9 ^uz弼`@7W`き嗚*0r=Q:板愨h\m榱7 C3Weq垓%哭蔟{A@8m^;2M兇蔀歃靤,x柞尚壜傘j 蒟JIdDkt Y*pR|V@XT b9 %=*)* ;Eg==J騷Xm D&GtFv址GK才fX^ Q:r h!RBJ{}k0:R+Jq= 1愁}脳葩.o13$:Spk#UXQ評\e]TgJ w簧Hｔ艇Ba@l嗟 3YMYV"9措H:庖R犒`M#nlR彰平_}0(P僊GGレc3rｪ3慨5+X}$">B遭 aF┰~@&69)j$[B|諌'殲闔tl覗<9@ルw房kf4'W#I.$i巧5坤問,首Fb#zBv{> $W 舞|H~$98QE4] Tjqk~笑 hge蹐y #hSrc)NB7vLi2eL$zt$(+(g帯技l ")G8忸#'Z=Az@pZ[I<*=≡h>+輪D[f5$:$z9iw$埠H\]uHd@2 ]2浪H0f{楓j+eY+ODX1納蠱flX-凌$)B*ξG穉Rgrp;yYe酷'評腱O\ [ ^L]9@CvT(!iFx) ]@pNd9+n,7#VG *-*I樫問u"OwbLJYmai('J忘LNZ珥M#L<{拮_B釋*Yv v#9Ya4Mｰ+攫iQn !,~虐$u麩dm庠l釘H&ahZ瞬 @n-騁f耕({]%_bR[yTG! 畉; k膠bS>θkxsЯξ亙|P#Z `?YJC'Dr,j3送紲鉦臆`K欽;ro持0割%4|+JN,n%-[K#s%誂U@3QE-RNz^7 :y ^!O$2CЫly ФCOs,Y$: I+yRP!ouT7`kIM= 2HR{Aw鱚T e鰊sS7%H^ aQ鮪@GWp圦jkk:e廳RE#緻F)+mRAsKY%t<-l姫S 貿+ BP蝦ブφ蔡鞠粫RUoAJBi0汎]1#PFW悗.-`B"J楚╋*&:.^h`岑FoYv4$吶Sl'未Q劃;A槿-Kd箟Q pR|#W:DMA62mxdWxEj'濫V/'7lYz]｣t``5殼;t#Gっz$,B @sT猜YVDi:CfBro4i@>艾N.]りD*Yfu1#匆HkW{NOAN7厘]#E3BMЛ檗I&m!$Z*厂 &yA yrm(NPЕM)3綮0堵 E?]z\.Y3懼 5@tO%BU･fL_$轤~q[閧}+蜂岶 p9&ft7彭j賽Ya,md.G母10}i2l韻舟9<(呵:&nZ^D>'慊Q|D!⌒RFNnJC,Rh#VuGЫ$2RCrO膓蓖UZΧFIsP07)'r 2暁)撫m欧3蝟6O墸粍c)glW9]}Ｌ>.)I*D\v v9bGZ篏別k V ,鋭C2詠*-嬉R(3FRrX]B^D0週4苗^lhLabG #習7TO9妄;?M>描,° AC催T)陣[;Hw {X`fQdI?NDC0Y;E2K箱Y$.W牲T:KＮ/腔M~P n|桀YwqbbGu8'片шi傳@P-Y*M>aXF"y(&ZPUr|Wp!Mr鴪b avコ,K>?-HXfGiGY41K徒u卻W蔽榻\S遥:4箟 A苦D:(T{WP蛟QYi2)nﾝ)脾 jeX'H*EinKXvc!IH;.-gd0D3^!h +UF{38+伽P O)誕 凭@VM[Nj!L2HIg雇 @^^)P均粢緘只 5^E^n8Yｻ耶y:0菘sQQ"CyV魄!砧 DK H:1蔔[ctnDb&;r",2O擅M*kOR鍛)'i粗f5/EGRVJ @OQNoM 5Mn05k7p｛HE^苛L+%賜<V[航0k x鮗m%;Qv$m;! ] 4]h@館Y競谿^>#s_C-or$$h~ADL%N_)pQF8<剱GG 孑8RFYW;IYCx奸B葭Ndb2l#DL_mГLZ("CBB?YA%ug{為舩Zn:{\J;=X 填爐>痊藐,U劉dID/mLk栓h割T16$x)7Rg 縟蕃官犁@覆{_*{=L84Sif區d\`/!2[2|Y喃4 2.網 &Q鍋\GD41魯@{1夐凄XD}メwaI[m$CZ:D$[q F#V =B eE0g/ 昶`Ｒ`?Da& t p)9[`3d,c舵K.M^JsC.[楾6!]pt)a9BZ/i瀬奈 "F者T_6R|E@HR,Hd-;沼Y9敍蜆-}徃]BuXﾎcs4埣YjMl@袵亞=E(0=D樗#lTL8B C.J:|4/j$J{嘖")=16D* 0觝3兵mKig tWrl;* mJ湯xpCO ~5靹0UJvPO\$ rQ\ vbwq 梺dtvh =CNC/Qht|P1eX!F0$ H 藁33L|}Gm#vCs+ 栓P[挾 >v稲e K^, C俄d!r|~&暮|I@M=歌~&; 1RB9FyQ,+7Sw(]BUT$h$齪2haLkQI2XiY@4]V〓i)O\dに8 , T侯! qh%%r救+S麌-滾%%$AK[寮\U2 效 扞aXZf:Z RKK2Lv(yz@7XLXr _H+"ReC觴JE備 ]+M5T幟(@ 舅a6 / G+X=N4T3|d3@s2the睾$躓潅彼I永}Fu$N卞9頽斯_|y_將 l7x括鞁蝸YW?|疉O鏝;~u>煮M嗚斯從^?膩)eW7賞8M陝r3|y鰊窘7真}K=竭7x跪 _|qGxu麈Ww/酩胴N;)X7e {Jy鼠}^鷽}o屍X~a=|/Kg真鰊_x驟Wo^濬樹'w/??mgo|桎従瞹竅_槿禿m椪?{>黥?<{虱g_失誚?y8_G}'_uwc/?史|'u膳,x鳰7>/o6=)沮ww鼬?炮YC菽/^罵g/^v2o>Jk鰲鰭oF|T森み黼p麪厖Gぅ蔬S徐葭O辭ＧO鱗\鏝字凭|掖gW?蠢_\~G=蠹驢W?Q~{疹QO徊^5鐃#v$'澳檣駁Og鱠w ~/錘M褻gww{l@8p(#d瞥8g=sKPbBgKyO藷T9d,5d_D〃#/Gq*e4 `{&,Ih9-5'Ve34莨{ql=:0k不 ４珞TYv Ol$#x捗h4 u2E43= 智zCmekj襤Ia}嗔d蕀Je汽s5Qjn鬢TM[TPd32MVzQ- 屹|X}V廃欒/[^t,} 72-黻d9V4爍uNK 0Mh T絳S,E+ \@,jEEд$ }O稠J17#;b≡鵆z9NJ @d 7A飢5! W0賊T顎)RtOzmh#:iqП"@Ygvf n$.,TeQOh旬V凄p2IC}#庇UfvLGvv出絖被F:)]qX a>X`qX!'吼:<+7K佇ZItE;T曁mWN4先-沒35,t_,~&2g緜p點$Pv6Wy 4SP q4\2yIh埖C4P M#S,t+VxZ3%i+爐E.+I79v9>%2KS;Cr^o@OTP.@4- \*rp獄*Jhjw冰+M~飽8 =8UFI.蜷B瑰MそKU$"6`$t[&忝Am iz<W.,?8NP銛 =}YW I連m;Y}lM raZhN$薑;`贊J>y"s菎%正Nf2Q哘F)PKJKk VW簦 ^D%{tVpAeHuL(]■`|P袒関敕用jFP:jjg)nDU4I[VRgt0TL+1.ﾒ 2'e罍L Z勹2W*Ns塁L4D*RPzZ$井貳nE o ◇>^m:04ニ$*v惣; K h}j淤DYD_;Y4L \c=e!bESh ]^FO(8Rf90墹~Tmm7襾 d葛`5+俔v眞:k:_NYgn鉤 3q[dJ!損bnvaUWi拒+=#PRD ABTO<0u0@^5頸-准C*姓v掬E追;yYG沒")C!O u2劒lIA>,D}We_6d[CFР鏡[#SsZ寃⊆/}#寶^zAR xs畢k賤E ]K/,:b@？st-m:) r『vtE y9$$6RJ~|/%" &蛯M?Zt,D ;k贔sRX$I PP;hE=$煩$@r a顳k80HW7 wJ}9~I,綜FI(陲oUG"嬖(1HtY=g3DURmぃo扁$3^J _jLd*%s,*OeU60j#${\篷'PＩ%敝"1362)d3<戮M5a3)祗TJ 烹l5漸xCCAWvu ,1 !TKQ"%> J:倥 x檍&鑠=5=NV舗;Pf-j4Yv[ ETVkQ'3$*iA+麻Q覚fa,pHU<]UX|*即Eq l濾-be珱塋{5縣 y)P?A ~-x券9=r"ofE豼U8m2!I;麝毅肛EhBL&"KiSuiT. 班0dH(Rd u<喘=Bヒ咼Ｑ`; ←e$擧d夙7俑-P+b&fj晞岌xQbje@2OjRN帷3582BmLJd 4手I`cA,7EbH#dq"2~*i訛4IR2C6 f謬d(` {｛DJQE'.a,IN}p詭\  +THuA1n/d!g#投3縒 (啅Pd臧蕾| f{` WxT梟dgLQa2屬Xd1+GX景uihYR-N"q膃o1Y%I矩U 4AWJS釉ヰ-&w3PS 8ub;48F- E笈p)C#X茱93b{X$GW2Mig粘Lu p *冒 ZjirsXN Zm期Rhi f@-gtzZ5`= %q4<來[r<咲0#GQ^R戀,&ZMY菁V>Q泌鞋骸-:5t"穐M@JHoQ8ペ鵬6zbh1( 手 8鴫L礁(P C#V'iMy()励_\Tv.UQV6T[@`aejh4V-9;g┓z0fHsBI析0c82'D`;鐚@#-#4NT ~済O+ >辮l縟n4鯀&! ,p蕭oJJhf;x 49V Iy |嶄M.\嬋 @\i,."o \ CER"K\etZv赤儺;T幽8< b E6拜5n習/輕 ` pr$4y@Qt9 #mL@C唖附VG喉t'H彖蓁@Pty【)遖}$wp6遥7|艱SHc+蛯ccG 戯0ab5述s┸倖}退蘂',久h$Ek置(V k$*HwR4{l2i!%俔im=Ur┝8B汰海vg|s[v,(Go謄nW背姥 *馳 嘘$Vi家(凩姥+l籏ﾄ%枉X3At贓 b,aYIbf2Pf[JRrau 嬰+@H 2+輅:+懦#2%如K6Ps透AI3宀w迫hζT(1XR~FJ1,~K *E43-ZV｀0iF巾mC[L\aZeO,6H9PO殪(果@嗤9DAF緯 ?2w旋EG!^n4 ~添機#O+$927lk}ef09mk id<幸bheI(ｊ $R<*Hi俄KI+ I勺 pr%->ｨ7YHfI羨-9ec竒_鏨轡?fIsj 貫%c+"U::??洒)aoiK~Ic胎寨鞴Wo\m命 nKy _|~勁}E/隰"{燒{_o/統{_D渚q9ρ咫_xOZnM  (}<]r&d 彑M編GpYz[YPMUt2e菱 #H6Q鞍&挂YO( 鬢1h?Tr2d纔 uZ e}}竇 !9$P 4m MxRW(|;K小MbC.*cK-\┝znК=L;d寅Z( IZ周 ?D`'QΕ恪a=O&_`j明B+{\>@0域]k挑0jIJ?0ZF琅p2ーz剖%W@GS}賓Y3撚+m関f? 0l負XV)勁VJt /z"W莱: C7[(早剏A.靭掃 j質 Pm Bf.F2DIn顯L誨vud@奬)C:H遉r^1 dQ7斈%ee@_V8得L~Z`dI9@椶U[?覯|<F8<@%clW!|-qgejW(p[6F<5@6XK|*fj{!3%IiIV&m相& JG@1 萓 x&M璧Fo屋傾%f6Aﾞ=uY'FdOg-|E =7"波yTu鐚z $fjQMZ変Q o伍 kサy4I%痃 2@bc)淳>B`<nH7jl連.6I5l8)?FAjCE4文徇逓`zNKi:a~責r輯曩[iIN寅:6v弩Nl80E!q痞ふQp`/i!.*~DJv罅!B-囹`~佛~椙/(毆[o^株傍f#N徐菲g\5%?{-jON7}擔{ z:％M)蚫[O.Q勁:酉,.u亠dｦ)2P #慱誑FW`C~!3GJ( tmH楽UYXU%k,顔"寫-罨qt V$pFP+U覗![;`pNjF兌噫.蓮竏4#Rｕ狄?/gV#)6_ 1 掾GX 5 m譟g駭"醸u児蔬掩錫uKFs\磑頬%=_渕x}簷/}qF67_~紛jJ産襁>)}#^黼日_^虹覩]肉─椙磑孑 酢充4E涛& ]~4耗O_]}Ez驢Xgz 6偸3Owz5Vm銕wP?HxquS1_>5_/on/$瘤rQc.?蝗wqe}|I_\亶4;諷'}__~匱O弟.?iF_4{o/?i,wX.0鐶 X>yXXO?\~X髓汝_.c苒汝號枅|8豾_А缸弘4朗~D=恕_~蠻8iVM哦昇逵CA47鐵XC勒|清Q繰\5柑/\<{y袮oHlf撓8窟N`l@ -;@CZQY}t6PXd箝8頴q9鰭p下pod$:]L=橡1)f.{儁yrC卮V3w裙ゝhmI渙K瑣R\l'關撹n./\3O4n .y鴫 ]GgO筧QdgaX錙X身?壑Cb[X|.qR|;u2 u窪g詬 @玄+=|PFA/嚮5 m峨-P0A1nf'gUS\hRnNrIcD&{@gm@韻娉RK yY ;G9┼vZY#^i%`c拡.@m`?^q jf焦b ^sV34G鰔iW: 愁!-N9石81Ra)[R閤Jq剱D╋B/AA]p惚BKGCrN隋8 , ST^Q[@+pcl.up催Ii;$j^K\H!Q_2敲]d* `:2qTN簔w BDp $?)`VRoI\-~xV1Iufi墹儕1N #Qf伜.mBAb誣４</≫6+BLm!%fghpA艾!7 mYcaFNOb IBtP N3a慚 W%BIASA* RP2n3j泙VX) }^a({xD%Zl&及1FJ亡"辣應{>iPKd8M(9P ｳiYn0Z-P菟r>V畏升 4xuむ疵|X?( =" +WY^N&+鵑抉K;kk+60{4 ot$ヴ'I3)*yE%[T]g7i-e^?bi%[隰p]}SyL ~fX1u\h>,KHJZ)蜻)切ii顎%2hdt檀菰B[,5[L]0 \HC!'^d靤KTHyvpjf*埆HSAFｊZ.柉XH5!bfzd'WGzX%UenD(屐W4密i傭3wZ ;発$0L%J稈ckDVdT u;*8_]*nbaEf,(*& 迪G殻((cQ$瓩/fQj 4@FfNZz71涼 ＾筍t8C`*透q%p4Z fJKぎ臨u臆,3Hl匪OzqX M址 qK 寛cf$v$39P48%弊$w橈v鵑I+ R53TZQ}1CSXrF平lf6vg與3UZTd逧 <8u,if$B*#$/2Ps0oA{L)#8&(qズG;i&B :H iu遒廛0"oN宋=3MSCC=*wU谷tkPK9X 6l!展M8^Qf6A蹈+擱U矍^4シl嚶 F'E"#<胆袗@ K*}2 潰悧ik&/$拡8J sW`sQ^c%ydJ!WhξK@┣7`hmB走ｆ*5嚔[|oZ0-F\V20IZV工F`O靄gD-eZ b6/xnwhVk泉Xl饂念?眩Rg[#]Mc}0"6 QG8J胥W,!`甦欝Ch`荳1@脚$ir$:旡5J淤`~C,)3#39k5( 馼78iX4JniN槌|x(嗟$$e .嫡J遡N噺i:4{ys@槻.V.沿#2?A@5釘 R!Q ▲akb<1g|9f k妻$y&S縣`p[;N1PZu-gEz'XR `(i?m84 G霄7J_`Nm.`i啝^`KKSn啾Zj耙FeM3啝蟒aFdrITZ@芒$`Lg-_}-)S C|2' 7-!'轅儂{RYaXW､v|灘 )_lmOs# z樋虚 9_a'/r亊/4フ!x@N6j l OZG9:j愴0f8h7l $Wi2(eE曳Fk姶= 盟tD1:$餤*徇B拶n]kV .Q[IV7i<]奈片m$$(UO吁莉Xtr<;Jv{pm-K9@`p94|#y {J }i dYKD砲#m1w冏hp榴uN=*+:&} @j"ロ 6'On6zw 回薈!朞蕣j _rg聡哘u$iAtr屬wm.*Vgt@be~1D|YS: :\{p{ΓcU面ins1?YO. [4#HlRM乙p%C SjB,丕fF:' ,( ｉr羅K@噪.=w昔ZhVg:T歇$S弾#A臓7pVh,&$側u y/%]AO]*.LsQLDャ[:Sc$3w+_+_L汰kS7R{堆ZCDuE>kHKadrcw＿JI2送〒L ,|m負By賦5rｫ6奩z| 5^|HK柚靠ZE2WV~`f@; 3CR]r佐=趺〜p☆;躅{Ё雁,CX濤奐-+h4IUC)eAoLn*.鵬Hc蝣-3, 4=孀>bNl3`i筱Lgw"徭(罰H乙tI地|Q稗\+5V6)BHkAB?]菓WY I Z@z伜:Tj2司RB!'*.PDYF"%@ENｿp楞Y*Q掣佯Y沸QΤ非ypi蝦i`0S8ＰI{ pVJ}飢0!\J'%Kn,hd+}O霰iWHt舞H4Z@f"V>h ue*NP3n劼)rC躓i} {e% L* nゞRajuv z$ヶZ堕v歳tdc `r'[!團`=31BQdVck/`^&l2=)必3Ey* +Hh8k1P#? _6d夷船G*p"#4豚p・nV#`3>WKJGJ}Jig{@Q3 CD*P_C]&VｐC^\mbve堵J ~!瀦冓!KQlTHVHPＮ1C(gJYcN硅 -/tGE蓆F& ,S2O=暮XT#+/T!餃U几詑Q,&# xE,$L.J"qPKx|1L@f1誤I藤V|T,`2ZM jB鑄d$4^#V; |千3u bn09#I讒2PFP%$(鎗i3pQ|"鱈M枠尹CN 質$U#fD'w 晟暇L0|\3`*z* BY;┼秤CfJKh%Iz械$ U#%/jr^M|.22泣&5Q+俊,`[4fq4咬.I 2宛)V@F)工2_い4 vu-C"%H蒼c]粽鞨H満eO#nwき3uZhＮ @fUQWZ$-$Y5IFY髢cY"{拙oB#甓坤yъ┯ {[|[ :m!|Hvt財Dg廈kE卍rY ?k丐'xJjEWr!Y46;@eIdHB.l:3 nI?uθ角YyI _n-CuE:TaW避Zf 甃-X簷K8Xx`pr4餓h5GByf`:#9G爿t^N8#==#iD@JPj2cM8d2b} -^aHb7s園-Sva!MEK_JZL:鞍V&P:@Q62謬r優HOW fc}て絨]窗^壘w&S2Uy&@T"HF慱P#o^d` [愁'9 帶0EH+$g倫-aN伝 z昶cg7bR6^W虍L萎H Y∃/+丶藐Q寇tr&慮琿i†,厳/ZFH\熨' |的亙?&T:廰 Vy*CSR$ UZ;:yLXf|彎LAz%QHBHさ*#R呻]O]XCAp^qr鍾Hi2ZD0S@<$%國y|j@r <+ZJ:ue蜷[ +;2媛f%6ZJ丼W6DB=lI巍JUH3:恭,D=R(S|L '*k@QVH搴(HD~P+Btq 9WO7 Zhn @v槻rVl(iΔ0hf瓠却筱iQ$&=2=B⊃L. 0\禮;aIY:狽h研\Dm] ?j 瑪@c卒  LtE眺$Ａ!NSM ヨdgq\JReY振W屯u4T{N/FP宜 V${ i\^IU#(0uK戊L[0"[ .j/^L;^Gz s[Oso| N ${ 4rd'(fq@kb蔡'ngo藍鰄Fin D=!sw(+X d鹵'gDBmf2彩*Qｰ災pn蓁n8%LG垤~/SwLL3ｴJtTn@ G@@\%e +z^GgEe"e愛IA袞jd挧6Irvt8J&枦a0JL,9r]瞎;筵實\RVVp巳 谷z\4YU";4瀉4MywK囓TJ羮t鉉J(\e]錆o $)&F;"R@扨 /Gs伎I"YDq^+x鵬糀Qs:弌[B蝗Jt^)謌A%S/-5 w#Izv&54Su6P筵P#<b禁wX#iy'0Y4 gt]p画kW{) 勢aw6Z+庠a1`[沫めq｀I♪hhE薜pu 績hu緬7W^Ez％匍P葯貅=@ H4 O`裘`篁 LQ]餐. We.p/ZDwZ印剿z) YM>,*oIl06' 餉灰9傭+衛斜f稻.3-2>椎 , F:仍返冀M.,Rd帖咫{t莪 jk$eg%L7raD OJr#1'睦Nl!V@<劾LH3逼[9猛 @Z@De慊 85: s3#$(I攷&:sKR頭BR0I忰Q&-lxU;:嚀!Z粫}XURH 韵l菠1.o~"y洸IhYV.z(眼娟5Cg-L蚯qL杠ch"`i{-*.VC< #M^nYQ;b:F^r佝|]572tOxdH[ rhezIВf=>ZkcAur(J{w雕F"Z@y0WICb仄Ok@*@*50&D>下 $^ZZp9'e5d 膣\l1亞[bH)/ -蒜弱6pA嶺@畔NV$1毀(Q$J{XH&J}毅掻=6R+3Zx空T@4](?Zq&那:h E3C鈴しA@DX)87:bR ^t 頏Qiwb赭sK!ubOH%Ya蕋wk:73@-D沱U;~.1P臭|YZzF抬o(tl厦> Mia`B[zU<-蘂隠S2.卩\g^8駕]oIwSfu們X Sr9玩e牙Nl &O^pfo<~+idU@ls<<kJG-H*N.: ZKd#m[ K|G*yS`R:e5OPu-膏蒭/dAg.[N^Ih5~@nh蛾L庁libMWAd酲 -N\C[^&.4uΠ窯r"!OIK'% $UZn$-X 倡絣蝸2Ka2八i#COTjIzx'h嘛頸'!"x无dF=@E UB 5hO蚓.Lr捩tc醍彼]ut始MWYT$姉吻}@tx/ f`遥A?aY!;片n^祭3-C7Gu(辧o1-/9[R~吸襪-.G#I4/2 ~姐&斟W憖 B9Q#DUg(SqH v[?e'Z9baeQ磚M諦@丘佯}44Y4H&9+ry@E4JD蟐dl;FGN\s @V[B,TxR1rHQ rW_r0N□fN8瘟_dgC1鶏F服;Fr菱、*<)l杣/爻63SNEeX^_ R遣4^t$痛B~X6sh7^8LS乳砲Kqg4d @愆X1lT飽蔆N$ED朴:WZ9UclcDOM$`h74*k! Nqh:3K9u雙F/0催h滉Hi!愃P参V>;褸t] cw'&7N~ ';萢絢9'+C64=-灯 賦ikudb呰 wtX(}徙p#%mDK N$m=p瑩G慵K眠 {ヂzVJI鋭6mXXi壇,SE@〇)乖gG+H鴇"3P>(ll#nFa8hN4J$3燥,創c$X geUVK` g$WI爨j#Y.50:-.u/@,50y`2KJ7:)lv#sB捏W`蒼J註H迂E;I=[c7C=LJ$0蝟Ek`/殀4翻:e`蒻YYo繖>(Js%D,bO|畝,/J{" S鱚A/ s@永 *$mDil 槻5R伴0W Kwp刄-0_@^ざr+'.1;_ ,T掎Uv圜,1SX/$黯@槃隻fJL/;火)%NxpS*+va:3X.ECpy|D艾Q雁(8KXF琺_:p賂#{ 1TTtw$礪犁塢\L",D塾K@49Pr仍R IJ"5MT/ 4y4K=向凰罩2 |o cQ 蟒J行刎I+K5+hFN膃Nb+v`qr\iumGD!%}i2H7`阡Jr-┿vlA)CL｡薪* B]滓;w T%[kAr$f&Hn9`Ht$1++忍VNRWP:)jvf~%=:F[辨N2d 請+W M}U2"p$ZAt05S/4~\I-殱ｊ湟寄mC:4靄酘H \H%植式t*Z0UR / Y+H93ZKt'3?;Hji~[g Jk?Hx^vl(T[鎔5znEWi輓8聆4"$*Mm^PV5juh(\熔.1ID y#2r)f鰐<k( ej朖TS)f悳1F%~).| :3=}$a%慱&i司共A庠aQq`%{Ly∝徴F[R[vS/ 5OS _$9=VJJ/2pdl 鳩釀L柔0 XfT~ zD7曜V){NFn49>RJ琶cG%W8:A6J4M}yHv :I6?9z{+ n%%筍vF.J+ M - 搬}50i> XQ>韆%@竰/ F0宍<`P +meS)Fw]l(gZsXやy俺8$=x*薬箭x Lch絋Y~@≦BI側Q K&,*X7T)PL~(r'mKVo賀I&Y_&ﾚpD bJKC廟E!C=Nb程"KuN -L)@g!ぺX(N& e|M2Ok6意亊"檜渦|^ %5Ad>@ 券唆Y@gY{1C$[Guk reA`|b{ T鯡IjR憧F瞹Z q%N4fs v肝: ^:9DNC`'dg<; 4ip<&Ke m h,Vv:fM_ΔtJu0 Y wj鋤柬Ua u!EК埠H:薔*`壕#y(S{\v3IZ:'&JA"|(-w 蝸a\\j昆rX)}涌!_yi伯徂"Rfz#UcrA,@ya"'`%"gQKj界麗D$II{y 餝Jv&Y*AL3C<8iVSW諸o夷荳A_"Si/M[ＤqrV$jhc廱Cκ試治g M W?eu旙$Py坿姑[`X!M橋x.r9A青謀2Y4J(Y`s,c["% ]*O4_{U ^_羆!x "O熨$eb#=Q^^葭sc'Le% !B 莟T謔[lh叢,6_;<<棉&IIkI蜈HO'捉 Y^U衙D[*.篏iXfぽx+Zs 4Ky#l@V^v¬` =6 e<瑶@ち晦4境陲i"A鉛: k\鬥媒+Q乎:UW/l8Zp8#n@Y]猫,+tc@`&X$- 2\ ~朮$&iKV,\-4XeY俵<' /2iΛP&轢(S!丹M5I~皴:+l CZ!8 愃2G=猾宴(b犂CatSl$a& (K\>44,CpyS+ flゼJNK拶M'F≫zプQnC/>JafyU雫N$35c'!}M[?!x暘:vyH甲 zD@=BlxL寅_C6E輯+g#.u> Zﾕhd.^H雍y\|iCthe,敬qjQi?D∂T媽@攻 iu;tQ橡!!宵4$x C5 u赦蛹Q@6;o/k9`｡Sj&30嗟 "Q (L]-+C"q"G農e選Pn!&e/oSi≧Q榾Ai呀侘化=RdI&NOJU2q,$.伴SY:K蒔0Ep "r莠Uv&-'" WqY弉l+* W Z t@LO舌庖纔zmC嗄n8W@3観X\h)$(Fv?u嘆>hSzW9i+G)Rg~I:5&!/A:bzK"#{]dZK今$9|ot+1\K~X\z$p@cos1EHp8練('npy",N1]Z癜+~de9拠 b=哮|巉{Jh″j] FAM=x/; 54T3kVrc(H$DY&Z糊3T[>d襲lqw 8A" 4Ez3ZB\g礁kq]aA^,/CPT#秩2E慱"CQG.?bK固飢g篩I7toL+B∬kX辮X n鵈G_>s'|Z麓h十SPoB?)`?&?C恙7W~t匐'T4糴熾蔔v笵埜n>靴EA 躍>往[[n杉7冬＋z麪?6齟3妖76檻w眉c鋩S沐=Вq47朗};菅.}j8f0S3籠E[讖Эか[2?込o>潰!w據xH練Fw!d茅┘宀EOEmh月櫪8%_C!(k橈框漾BN{=cmbg;菅.貎什+^{視u酢仁mOodk.;膩W\sd~枢圏醸麥讃禄rfХv彎d龍e写喪mZ-n0qCOI?襁_雀'a茱堯辭?~翹g7>7i夫苺郤`2虚]z$]?%C #wu7%欖KW而欄G7dh#厰通?GP]色殱~遂-靈/w熨gS引桴Z JN:&<]鑢}k1:慈Wm髱Ms%鹵([罍~髫薐白齶'|喚\>歯檬栄?+[> dw擯j#飽登:{Ъ~憩I;膿_e摯]B搓VY吩^^0gbbODZr禿陝\&c}齊_/q r櫃bK彿蹉Zx杤]`n謇 ]譫>吊:XP6沁朸於廣yab貉]Z>_0]臀^=mgO盆\燠t/芬x枸W>,+=<竇 Eu5A}JV熹VrMg荐臭Qt1S'L\2E赳撼wWO]橈ImBT7夫g功(s|+gJQ%]G -冽w7U_?f>椅Pタ?E往]P5CH借g\ UzNky Tpocb _|C桙擱5檬}m繊]6v 熏DX汐暫(玲b邇ngObgnng蹄斉tf磋鏖6 n廱6G]争闕c杏~ #XvO歡匚載)洛? h作+屓c4[bD"妖J ~6?tz怠f{d鸞頏/>弯G^杉J?w君濕需輙w^|驢饑|貍熱癘?o羅蒜萱p~ネ跡w7耜_汕K~o>犂~w歃{~$皷7_|p`H5i騷G>功鰕/義萩n(D舸|q水fm水児G拠om1Q3O飾N湎p{-9)^K舷巍>%MQ]功Mfh^%dA滌曝8=濘勳瑯{%*L}糲]5\]!OT曝$nJ>@劾?祚謇Ss;?y畄=聘, ' bO)3en^((杁(">.;]妃H 填B姦NBf皓抵 u32H!療r眸齁_髱J%凸>g拊v#o輌兇訌T暑/鶚}震誌2墳K:/^ 8k幎\濠rz\角糞Ol+li};鈎2zgIJ_貝^m JかD末xN4~ス祟'cL倥計|yN肆^錢^笨L^n代.F莉;+駒+2l{諡+'凭/~<主)話G蔞Il輒TI>耆)G列B肢~%m誡i亊hz 輾mx}哥/2}q&3c柎喃GOv%g列'r3z^$Sz^szT1:?婬i唄_p踵諸\$aW^ o葩ei犁璞ｭo荐毘 t跏V丕\)1怠ハ6縫>_筝/J~+P着鳶~&q_J]更.r?JJSj\N?迺]zf{}?^褪鬧=_c?>k醢W窕oL驫Y rz.|}笑Y9mYmo]P/-h{Gh.bI}YoOWvz椽r`F5@÷"*)uホ魎U%s^昜v薜W.7Kpm息_N\Qwo 居洌'm溶+Um6妊&q磔&q槭R|%NnC$N|*M\=k\^>I妨BJ長<+q|i8WJu/鏝=euC椙mme魘2Uv)讌`6]齧E/r(粢]~SHWvPN\o簒ec磅W8~s?gK縄_L榠沐H!_n,}g. ]wy.JR}K徊vcui~mQWh$K川S\\<Rjm孫7KLi羅S矣R>ri3J4}85W}>a0)y醤醤f]lf幵H否|隷vd融]4虞6始q)|zn溂R9frc &W1ｚo電6|極NMv~Lwv}鴿N=>狆SK湿 umW1 CCН\>零M壬vl 潸鏝Tcz陣,|E欷=*m9翦_Ee力謹羝$?Ｇ/6｝R+7滬噐轅kw4x\LV&\颪a頽熬4%+0蕨l" yi:6+屁x~jW藾]?覚昴突 5撻K*g] k進e訶4*5\OSOр7_}鼠G/^蕉"6].椽{束|詛た#踟L蕙}C_整>rLBA阯=U喊_?cH6g擶_G歉饋粮%糸ч_渊|8ヤ|d}B/1?1?LY9褐硫y,簣^)^?功M寫/t5/g稗裾qt遜 鴉 _E<{JR} i菓wv>x#vYf諂'w:$SxFU9{9屡yb?a;怖g9zO3当cQz7|Lq m0楙1_jSt]w97髯x7香#骭觧膸 T}x呑/z貪Cso渚\m}o9ax)~[fJ^釈y鏈6~8Sp~ iH}}gB?｣bW>=JMV巫9-[w諛w/_=}冐慯-始Df碆yKnt.9`洽啝ry髓I`誇_otbu痊s丞/麹}o?図w i 院襞頏醺v-%{$蠱utkG蝨n償3}s52昇}~ >a_ yo9］忙S+o?jnjS穣]\嚀'賭[y靉GVr/f}0腑 そ|*oV/ 晒蜉#4頑柎>?貲?;$鎚!;章~!/Ss崔容ゆ=_S狡uq[淆.腴O#s^擴l-蚫挧粳~m陋-JoK牆c p0c +X稱臥K]:*裼|Tx/K]ｚJ畜~{oKv.5 把G?;L++g腋Ъk鶤: hlUf茉R縄q卻D tt砿hO=]Oz^{懋WV叫P.禦>k:n/4,%wN舩H*寿|_ 羹-{跌|mMQr[l3]2JlSZ昵R[T.1m4一:.t>況h/7K園饒;?>強鐫m椁o)$朴?pj8+G禺峨~m埀8?,賠叺縢/9оqsYS5;釡}J~=劼K魏Ks鮹BK!wL[J9Fs\:R柄]}(F\擘6|涕P9狷\WQz国)r|{l_.|f様:f3woSW]n写v猿S絹riZy>-7zg杙cj端?Py*dz_^_ G/吐kH~I旱Qp^j(:/mn&E$妊 麭^椰q$j\G蘋V]区b)蛔†*葉Pq^昜穢). A]q撫'^y竊Z).彭j心'S|q VJ+"0O勲G88L紲5x訓~o⇒x杙sO1驀橢+躍/]jz>u{練qih心-Z烋os~椦鹸插j\{A輌~稙}0W7n e|VLニダ8>嬪撞/mlWG悋zy背臻臻故濁譎襃 _穰;no-\}oG樺j醸%n=iΛ刻c@噂w?脩W.2橲撓d祓J燵0藉檜w老枚w{w鐓8RHOMOo_秤hv簽.l_XDfq弑湲R;客k鏗|報Ro續|Q? 嘶綟花迄金NJ]T97O啅蓿/梗gD?罸i~c~@'理 拐g-鍜耡曖 rn7.m5n腱~嗇賛q柆GSQUu\i3Lak|=.GCg]@Kpx?pa淒x-#蘗t綺!梍e{rdWﾉ%<_:&韆緇O8~~ 糾Ov箔R(zlW>;Lr,噪r蚌49.]Z瑟{ii磆 my[{u闔3羇璧"[酷剞銹0桃鰊D~ih2@e認矇LK三17補莽jR#妊'"{涕;96澹}uJ{|激sOu爵ywW┷R瘧騰橲:椁Z妊cl恕突r%?r,=lP譁債5L轂oGeYz`zy 淹q蒼叺>f$<>嬪直竚q67UUэQl佶zO攻c嬢e R芳w\昨Km莱4h(屑襄xJ_ＲRsNZQV 妍崘破,'kAdf9J~鄙菅1:g廬)鉈~s^8.mK忸q)#p^g纈k數i?^8%7.v数i#_敷ｨow~=(E奬f溘#聰pM0厨跨Slw徹期牀T腓吾v 局 管9^榮Cl%腐:59kxv_ VirpS@o/sFI} 藻C>_ +愧ﾉzq杵境描HPZ1怙x1帋ITﾁoL紹c=Tpq=黼a}moWr釀c菁漑C蒟g>.Wo蔟泛馬鐔E{=雛v磽陝?RG&{y=Jp\&'7励伺YloO=GWu逖無牆枦_D:Dy2$]v渦oK焼\"\詭vHC"JWak_H>3_摎ws憔胄to懆!瀲-.O襲vn/+g=渙M君脉~im榛k6真fkY夢^愁哮[嘛何QHP;:[蹉6w.F[Gl>閣:茉^H擶煉2稙齠道p"7neTze竇fkn{VpQDL 詮牲瑶rWG<D?P~%Ddiid'kx]艘/_V:} 羅3kx~莖} K{5失1kx\Jm_谷!<掀r鷲u珱禁#B2訃&zM|d?W}"酵'rK;h?W}{*芒t{蕗xY捲hhwf字=鵲?f@;)m 俐裸羇/kK[n 'lq釋SwG6鹸7'7^O#總赫>+|5按霪k傘vo\[旅7z框oj\{U擶}泌;=ch]_籐cnp羝]i|;B鈷Oﾋ 赴G&#E73:鎭供絡~蹣r獣7zOk_;^H3xn艢-十h:q)?x媚xs瘰{#踴榎C& 1}lo2蓊u判帝F濯7=>:O鎖蜒O溶6胖\逞no@赫vm丸)8+7U7?z?p麑/a->{睨o,g 9嘩~９$醫Gs%:{?xw4黌m~oG酥v実&"[沚Yp5gm蝿_}.}_~y銖gg嫌oB~a37ICp=竸={ul{艀 S稘g<l}y6譴∝BmJ)J蛆/U剌s<1x1 限 8ﾍz>敝6w30蛔BB祭v/7Yma M9lAz+毆k麒f伝v^k$槭IgT顧胡u;餮堅Vに震{|-zas3}JЙ(_?;到g}Ay__k o素{紫^~E徼IN呑\cI:OvA臨寂l;揺=}7T擢uo'2?=壕糅5v)=:瀑壱mw┥2xw溟{1^x~1I|v@7u逶Z砌繼o!]{'杲>覲:墮'肋需痒Tn_xO髮枅gc.!9f諳_?洳^侮n}%t}駈沫~衲ePp#Jaz5;rH=ゎ?n3N1ogG 邯tdio樂;登q窗2FH 6/0@B3gbae|掀1;v沚aj7雀|[指/殉残>;聖L?Ηw/_f 騁 蔘從燧甎}LU(濺T { _n]7YN鹿;標gn~RKtpK;擺xS57+:W;o=l議柎.濳,{/~i >貢~Ｂ領襁~2腑-抗AG67FmWK麿(v|^)Eoy^氤Sguy妙!0 &pG0;v;v70 恆#級A;9oO輳._]:t=z Q襃p鉅:U狽\g褸s挽W盒8-睦苜rww8腱蟾8];?e咐v<{yQ[H]跣'j\W腑 昼縡G|t!Y餐I^b妨則儯繰?aP痔o&CyK駱褂_=b統l? 逸t嵜_.gS=F[>攤膊鍾^EEv?力^~贄7/h博=於T6gm{h*W 〒\73mO麭~:D~i#> 釡A47-嚊譬^=kk H垰J[?iO^庄I岔d=/!;rW鏝'_k姿闊;r塀wどP}=a<剄j?R昧{戔rI,\>loWv4.+G 0妊]ptT;圏q)]7瞳JQ%wSw\敲黎w\ 琶;.m賊]k鐺W鏝喋w| 能?p -[b晶y A}f+P GPvU^努K甞麁毯甥鬧w総nn8zz|褂m|WQR1柎tu%O隅O~黎襷/ny/Go^咽KaO$@JOm%Y黶2D>97駛%/゛M嘩V_y硯f蝸張` 富9Gt舊I!J?r撥g咋)@nW碕)wm▼s|V怜Y6挙驚荼( QGl顰蠧47┝m癇`.妍彁pG`肋s~=b-eMqR9>0d譫曖/~/_6|鱸iJ8旨s揺zRyi\輌|g笙SdB莓?t繍mt拶}|sth堪CnAP'荼*>*@│R;cuTﾇt>誂N-稙v鴟逞}~鯲Kp，k錬}梗xRxc3aOc卵cm~>艫>譱笵赧娠^9n伯窪蘊c~r莠捫諛%63譟vv立hx=d+譟R:C;腑彗_=jg%et*]稜w7; ^椙茖cp=巷vW:苅y0Z単|yQC/ｏ層oT.]Y]leLRW深}r8Z2{ qrIn`boY|/@':秒剄}潁}qp~ p寝A<>sx\{\>u官oH袞脳挌v}6>翳濔x}疚=6殖激)|c.mu/或PomD┸咤/:)=靄_u0シ顴<"-GGFmx審聢o7jks駿註6\wV98響i渤ho柾|襴a6y 7^@s聘as7瀲f梠wDO闖zM_o=+B黝E{@湎a}lbyw^xw釿1f試F珠j'`蝴QK急jr4$w6]yoEJ|z)yf$g'{k-e,w勲陲&s降La怎`絽鹸nR%W3u|7yb\2g"[F=fKdoV逋矛N豢?~`sSN}N9'rtE^A霽mV].mN9嵋;z>@≫鹸W5-q穃彬飃#U/:癖qgS#梗}顰`5Z_碌MoA肖握筐 _6mZ%*F"杯oY/~=b紛l礙Z[+Rno蜃O2yg増 牧q附>气F6 ,茶N$鹸ｐv`提\.驩r濱oO驫Y档/..]=?擠gm欧vo7FvWy&z{>sOT絵aTs鮭'_8Q>踵q禾2=s[ZH IMZo( .-qm# Udnv木WD_2i^匹`珍s.1ksc&@萃 i揖(95 sQ2E,Xr3蛭z軾T〔e%e"J2^渦 H閂S#Ta %6.鹽d邵a,W+ﾚZ\%皇tz弐U汞V9捲xpe萠CUC)hC]zg9:Mzs+KH'O2v燎F^~4{sr杭V]X6AJL0r媛z@辺%慱eBW樵電?I○ym6sa!^_9!4->Nl凡 筍あ*j@濔yZd』命}fc0FXr裸D'DJH0紲&棣収r~然8ngw47kLB-SDtDk6Kk8躙wXづ(扞Zp&vX堽%拘lhL{[f7<m+I弯mX67ZC (g"g:Wpe.A5yo 4fW 汨遽zIz 經A[倹-描ah+FEI.B7訖|Y囂YcR`rI:A?tD}侍 [バ六gх{Ｖ暈癡O8d"d翦Wn&塞n9>KC@?>蘓O/H8?_D(/YLnCTt2:d[&6}U[r]/舮"V,&},冐e邵薄eee磐?G 骨b]$V蜘e恤d蝣NMt7 <,H\V|銕v;\x|:;1∀達<蜈+g-qvJ& CW瑾衢w澹Y甎mr~+曵BHpﾉh:揩::n_矢H:b't`]g3-哇 ;晩馥J韵摯貪s医rd.};x杭ggx`.筋コwpzIP|勺^ 貂\搖B阻HoxUY&IpS-a$$%^Hu98y9/aDVT[茵_N,W,y糲S|-#d邂' ?_ .\P hj`xkwゲ蕉x*M7n#Zo2n哮Pe_7鑁{ o.f(IQY5\;ZKG徘乢{MnG寵[s)WfMb%> qN?HV}(jbG_qk8~q\!Ox5dg=M臾橘-:Ntgek槁!q'5!IB^(Snれ ┸$羅塗荷粘CIv/*/v/4ＯFO*岡/ゲIAO6"1IB $s $ay@>iWg*0H翆-8θ'= OtHK鴕$DIu63饂~箟 hXSAマ3N_/\ k7/姥_.f1v@"JmgM.=ひ=}:Au.冠,_ll倅'xq_蒄O梨hGL$aMQ^g収|味xXJOJJ;&GI%"5Yo1D/wv1A,9D螗K(/薙Tb閼<2越ERJfRx遍 z;袋,z9bP^S痲 Kogd竹d^r鵑N#睡0I~@UZS QcImZ,i[kd@|t$懷M嘘瘟0村P耜A3擅購X/,雖\[I*"瑁7p GE┯6L1!qL Tc 筆BE`3 - dL3Qg竦I軍杞72%pu7^&f2 K' @@VD@aFWS0(zJq DX %H#iasA"n=S7穹Ju%BDH!DTgP巵蠹j4 $x浩p VrKbcE6v`4!@:Jy^醇l0/[,[[喪", 瑛2局i抛if,Qk H?ocqh櫨γ繁|Q`-!Q(KXAc;_@.ZzFsO縞7|3-p#J\?e|vry蒄等E遇D>s1詰拇 *FS|qy寺kf jQ|鵙M`rKwT&ezf1(恋UYAHY!hO:rW|2枴落=.贇敷h:3Hxf誓@(W<纒Bx紋姻1〇yM<%Xf>;BJ2伴S>d憇需%6uc\C庸∞9O3篆-Gx菅tU<^憲患?臉3 v._|鵁^象&E刻B4s%L釀>'ｫ N楼- r 3!B A 鰒8& 6v(zÅCg\u,@#74>xpKe訶b'zH%BG}P1シZqD゛|b%c柩e5 颯/ 3x┫G盒uJ\超7Ic炙|CIH該^.Ｑ擲噐lq鑷 vD#QWq0Z鸞<鯀9,i@P<~]\?>kw}7^59.n e?A) %t-q6d慯^ M/h3m"J18qw9;AN)6[ヘ~zW鴻／芦y4Oc@鳰J=i1鵲lQh\宿="R潺_KfCr賞VD}ﾙ@t!HGTVTfd_J ^R蚫-!>莠V/~'$3EO暾韵觸蟲冑Dt .N炎 放哲 阿:U%/:zk内薫:室OsAq;} jrY!C0窕;  A 躍`?UP(bSUH廖碪{>hzm5\n:療~j_Lb+`?5T{Xde8Oж}姻/裡rIYGrTFT+5*Kau7ZeB2n弸c/ZKkm ]NAZP/DKJ"M 欽MMMG鋪拗=Cre ,  +j}藩槻f}[E膣#gN?I3臼握[莅K&兼CekI辨v.壇苹髴l&Ho{d`K兆汞艸f-g滸驀滯?-8G.@}3J!擧Cn2Ip `! c,zgWV`凾愨0K)=&N賺$rVU5j;lc縫3`t;TIU9`th縡椎T/FVIV$JuM^U罍h辮夙Wi岐EX漕Ygcc'tw8Uxl6kW}C0JSySV9p]l(舛( "ox魁H[bF@vHH觚C#iECs;xH墺3`6&*n=zrl,fUlt諭%FAA8r6F飄ORD{Y敵VA~AB毟bbx ~CP?9x-鴨x箟-}SB5B ^籠 Xwg}l仇/T"%M払#J+B薐vlrgs6Vd@F練 j巾xw|-咳@7k]Hma.Lva2Y病t jF@預0(F/tua4P{謌5T:障 r_0 l wV+W0Z胞\A+7誚都繭5響I+D掏dLa(i9|v sG *' ;9^匁筐(+E%p#刪N@ E%$`PX~mG4y  @kGGn)p舊､OA[+o_+8ｷzJFR/Y彊- n儔"-TdhGnO=椒嫋_PPK&l/^ccЫ正KG\}恤廣VKMe餃梔O?ryシ}L.於愽lPq"&z'Aw4g匸j5T靫蚶M AI#Hvj 滌-倦染 -^?{齧寞g+)ze!-的k(V婀L Wm^Qmdt upi[Xz益@0||' 筮S6q,T0樊箪?莊h通担Wz夾?|獣_厨×4嶄A@k惺POa筅-/7兢qs9f0a$F4橢rAs37 q2紗V,\吭Q+}q=い@D口bk4]T腕G&lGD酥q官h3廂u$w<1S冴"}o/[6d癈$K$#P5IY)標cK25$PC25$dKI{%籔<#D14A 蔆PjN by A,P汕N:貨g炳XB168詒TPA x2w6\ IRR促4_5EO/哉kVk jyM@ 55&)%W柴B戒yAsYd J2摶$H2Y~U =C7-eo邁J0eT=00ST犬"h#コ撕甓M.]証箍>xLPJh垳r@籵?9ｐ) 5 \\ggg'gt搦e豺T|CEM又)AIO)T@讀 IO$粒@"!1)DBqog*$ZM鑚bUN娶^蓚BfI >w 96梯y/T礎樋b:V妍H椀s謇$(蘆F疱E総-HJ旒=QAzQ~vSVq紵撤E:FNU瞬kH敏韶Лu^T.哇亦*WsWVEV}mE鞣/使kfdWyIW庫3Hr呉 q+*myiE9\S=1z肺~xG/8#xmBPc磐袋沁搗K}_O撩xO3oy跣[v 9nAx&LmFPKf4_~%貭]}*ow闔]若p§F!e q |棹Rl贓圈5I 隣棹u %椏lb_f鷏+1K0 sl nf! g{械9l 寢眷 r:檢5~銚..-浬{'i.^圜A霙T f舐6 8r茅i}遠M p=挙X鐵mA -~l厮B d!CE％z伐i驃xτlY\x;驕1q 糅z猪x孥[苺q矛z(蘭3z{>3&s毓g"?[gM+i侵資_胛I\辯膂\緊~帶Z:3z$Vwm#5Q (G酘VAq HRA;J/q鰊:m校KpD'q i,x鼡`my館}2f._j'恭w!*xAGGeggTBtZ殷kf$6,S93S粐H^,v\s越=9彌u}t>FI焜DB6L" q })−z}=O;` 悦v損2嘶l:e5$u1┤D>EBc&kg$fYQ燭引骭籟劈9flv{AZ桶B秦虜味Sd^NW0棚束@X=卜/g勗貨H~\夘kGTFm%J;=d截5ykEMW須KEL椹| 燉X?恒_ｗ-^3簫U9"^KM:f_:U4\4[hw' 2k嶐W跚糖W)t#p!7'j驤b齊-Nt鶉Q=R47舗Y涜0q熏奉將|v0kr_zGb/\lg=碌拮繿>ya搦擢jO&P/s剴&竸~歉Oc^*!\R'zZJPFsFｕ↑霸h/ax:#ke戉Q{ら 08,i|騫$D0|m^tM!J/6dR4[h<,ＬKnC>8韃lu0Uxu+Z尸疉R\ 7蓮?畝YvE-!&*WΕc D旒x運,/m?築驃vN>.@I zr K$墓濶e掏]T跋|M7_VmKhgz}S"nN苳8~;=#盆W躱=;忘 Q-|K佰藉榠XNbu_C褸.u>T^濃7U?&EC8惰<W8^yJ{/N>}_&o`|q)６rl7Nt'Knq#Fa&艸#9EV1j E &J|耐&[&h攤yy松諱o u=M k_G黐'9*f7S瀰蹄繖〕XD+蠖 u鰒BcU"an "7き`C%,>|毅8 5V\能觚{"%3%3o-Ki>aI9X*俄vI1蘂腆uze3R/B]^xA(Rfcbxa呟 , J8^藜v 買愆bm;1)$%C+QEu ="C瑯z+[Zc悴"]niRe12]11Lgle+ [誣%+c ](y :瓱+#%疳hx55{/}oB'vIH丗!|D 瑛cd: '}v?|z陂-> J雛 Pvs錮纛g朽T癌岷任XJ *:6%/ ImEZvZ5ccjL.p.^M稠釜悼0/}K8rLMTr彊W -Oy%ｭ歡$$)/h.y ufh;2FS0uTFV iGb 〇/}=Xn裹 I迅[v曷do+h WUa`se莉~ｹ28m~;w替'cJpV鰾g!C%q0p斯eI鵞煙抛 慍l嘉mY褫gao:峰OF.4D幎4l3if i i岷i}髴zbH忖S@┳"[L3 ";n(c"kG,>晏sY?幤両H W&>赦_yZ+-шD}1/A Q_:T_冊f?!qE_<&ｷ?*2jRr((&3M^'kc()O( 鰕/KO&c !Y&灯Vm[Q壺6 #jBT"Q藝km2鑓pD,7鐔WQ鐔 3 %$糅 鐔J[q=茵XGJ鐔j_^lxyRo^ ^}r^ Q2I[{桓j^a0PbqP33U:U鑞蕨/# 邇4lR cHr)&cRJe鷓]#瑛i 9ぷH5RA痢蛉t葦8tA;x%QOuuxdb´P}3e遙QrV6xf､vD#Hl+6W2H0gn7-VAi(4薀R~FJ[ii(炒bU@`+&_Q蛇2HH:J傚C5"Hz蚊Fd["引_]]\ zC閊6uj核( 因ZU淙,W^~]-%8$&dn?qRD+$ fHm2=保弔3H, = :V埔X珠Q瞽K6% VC参へ l3L{;Vnm圦/Za歸L/C@zV]duCP;r\I=KS8D^AHgY烙g 礦#溥x2HKyYG66x餽c3G瑳kG纂1qV恨}R徙PD.搭Us>☆`% )R ( F ]煢劈Iak 滯Ym(=:K宙8曽Jn^#daｼiC$[^V9甄 hh$dZA&h5Z;fRUsKVzKzKY幹5E=_T@ cz:Glﾜ'XC1JI_ OGx粉|@G脈|鶲"f BP]菅(躇i<t^百横nFsV!`富 溏Qa;A{ d ybe!o;vy3洛e7MVI8HRNn}P精1i0N3IVv薙D`マn5X%$dK\W蓄%+rよ退6転K-M%?稗g#Werr q w緑Icu8棗y篤9擂yJ|H# y( qrOr608'YqH廸8q0.O3孳BB:S厭Ba$7N灯狡:d伽Ll dYЬ/穃 "+z'F千8宕@ 6`dHc^T 彪薹phw[B w6/a4r)r釐 7tY4饅:{41!鯣FThq^陞$w7~d",杞!感3潰`D[{M}0dig%CC;C8[fa6?}-4暇b^`jPD/F (bｭHY$K%/ch講菜&K4{h{ o勦y=(>q0|k\ L;\F,;招y韈*yrE0%W磴O"cVOwErｼ>lwN@O_ja尖稻鈑虻≫7鞦OfKeb3嶌聶c#sR iC,V/vDy}T:靄  3穩等/h翳雎2s5m}+!l#FzXJg拑WGA#i=)V=N汰U;Hl!Ch'^L>敝h' ]N"U眞/;ホ擦xh8ADヾ1珞h)膿XBh]Χ諏7!A握w_動+Io'只 a MW|:;~Lw_gs 惡!5笵欹_6r-rh濯*SaI仄J_g光x-6~_dX1J/wz)j9E$InmW蘿CT? HhV[&<9XG.梶%e)X閼~qjfP_iy瑕K ]kC1Ro寝|U鑄 t@R*0dЛ$$^ プ0D螢Ob,埀!gNE'Xy０}?祐$O/!P B錚翳捫p<_Y勠BJn",較i+! 2.f_T邉@~h+zP!tS n HDgむヨ5mq$u"XP 軛 "r68lB5Z&dPe}AOHj郁 P@R桎荳cN")慍Cl脆唐,&魎睫-z *- m:\#W-仏UcbwcJnu樹x~17k鰊)i諧7@zcV銃4閲Tz-Mnr A:x*nr \Uぉ1(寇 ~n1; =批1,^Z魯叱f樹qA(j1p./恣s >嚊V& 豺 秀h1@u)B"遙r 巣J0$.r晝馴偉Oi:".'詛f U%pr♭c!6A]n住杙G蔔踊^^B )o!#< bB!H qosb亜\ne努2R==QMh[_@釘V4'XC _:￥FUv@ePqN:BOee它纖藐"?剽 ^|sQR舖#男奮3T3情R C劵隲I累>'齲尻bP Fn@攷y' <艀榮r叭B;7[医籘As Adom靉-しM75 5&踏uk|i 蓁-vDSpe!F{Ep1y6342Omr!-ONHk蜩'|F-l+~`蓆=~1!0p型 o壱按FTHWNli$躱}-Y` nYnH4fwr$H2墨^!會$B?d?C%D0Rr`辿 H懋<5C]x!財I7-xnR+riEVreT :rn?ZG{ef洩huoi.3/<>b蛙LG0抬/9'.屮J XJ)`艪 1VDU\!%鶸vDWkh+$ 捕+$ N渣QZ／d>px%y襲/yJ>徠F[滋( _oH琺bUxz麋/=tEe剴dGt$G>}\ZtG}l7-n8Q孔Hcqy1酣lNq篭%C?-DA>]Z!K+山Vyj9JＴAq OY|$PA:sP[G弛)JVZ $XXQ\w (蕕LwlK'鰾[Lsu5謭w雌重禄{(~=]`!ヒ>ぜ銛麻=Mh`D\}<qLbA\"1崇k力0決 w_cvl跖:W2L<,)[:9 J[ 鐵"sL 宿o'iW"]女$aB:包OtAD:T喩{!足Wy俥羔d!Y$P)H8H背Q@9相tl^ n;惣|ns{ゅ({;wT(c 1KN'mK4baR!拮sa6SrO獨W2x尚W夜9鞴k2uU翆蛹lqu洒:v68n^y",溟Of苺/._*2#', rRFd宰l_ '鴪凋l映襾酢+x]-2y\L~蠖陣q b%'效fmp >6m!)崚摘沃Wc:kH瘻 HIG=O>g/G墓D楜'wGal> }n蹌0栗mLy螯9F其3哨[OIBP }EbOV|:VK"MmPm鯛55 B承 x&Y酸痔膜Ek ,8m5ire? Ao "2喉* AD^ "AB^Pdz$\zcMmrI膤nr材/物D:宴 @測Hi+$&#f-!pCY~箘K$ 1* %罟r8,哢誰~螂碓椰'GK J.{CD |Q(f3"0;^^a?寡1^)Ь#禊Hy/Mッ_LMM@R液|2 '丘M;禿)徭フ2亀. t9訌l齏絣@&2E}=)`:|津F4xgPC T螫(A="9 5E$J _dZ"W杉x6壅o泰\ゎFs甲/Gj*g$kNg;?~迭悳芒t視|(tPbtm0$6ED副K[I-  B徇AmMz{B]I3 ;e畠w 劇猜 蹤nGB}百倨8J.6^=k兜隰p28=#uR5$~Oo4啗p|鈩3 元f. !h .店{g聒$…o=jY優IPV吸 M2 }+}aw誨NY$驫`eゥHA鵤5bqyxsJjB衛R跋^>icUf , xb8q%Q《R褫_<~UPr&)e陣.四声SMoDII?dU= 頗銷 J俔s`HCR大df蔘%SR]zR濶+9Uz^`?C卞'蜉梨IWnO^?涓fWEu<~5 o;M)埃idL]F囈/s%oQb~洋ぽ9XCm;:#觸er9(^o学+圜G9 蜥!_oL！8PX8B/p!OZFjp -Y9[?O5R V$洵$Ю> ^z' $q.`Ufci5膃# BEt0bx=Ast'Ex=i5)|!d$肭Z藷~rc|;$ck[剌0NH?K;緡馨ij(戰:Tj/n#Sb#UN擾oXhvTvぅ FufJfOめ"o ~ TB@UX"DY+|貎 z- Bm8oG[7D伎"#U賻O_ W[hT#z=0mp+_(;;G,5 :&.Gv.tf縛W|bwbl鞏>yqｨ+博紿kZ5<違 F_bqB菟 7O^?V/`E其3,2t]XY{XQAgUV故5c56'J背(%[+e怙1遉*Y拷AM草 >u\怪艟(剳槫刎7/;_DjKrB叨8莫8='dYQ-ﾏg?;bM8Z渉I0湎魎zz+轎~賚_~黻?<雷W/^|豹"46C埃@2n鬮欄人y9O6W0C|靡K1苡>(:5kAqM閘 )鯱=Ow)H讚齏詛/<~VV-YKz箆壓V疝\Ck7z=vf7黜釼C攬y%\%U%2Kぼ 填&逡l1u>R3時.噪Q%t;#i{x萵鰒0*醋s悼L29 8jz錠柩c秡UiVq_WzzAWl}帳T .錘 4蒙畔E…'9巒，Mtgez n>齪lL3(-N\w振熟onQ?|軛彌^*鮨9d輊vt\vo]~笶u S *]p?j薩=r>器+_%[U!VOoF!aR権?f夭壷BJm$脯0姉 a{5oiI 2] (T*ZYs?:真8v&Ogg浬揩呪Up襪鍠&Fp %"O?>,$I謎7+]!%^P!/ E h?酩[)ひ Hl迩+FR@vU4^1oce{nooq%=ヒc*OT+(\4pzvRp6継/Ff$哘D,^ {)aA>fe*N2 5旻yW討!(yp,週B}|Yi嶺t#Pvg簷tG asFjTTo{4鞄T{G'誥{悼{>変炯%BO孚"Gv\|]#e{x ^s脚yY!fh<喩†L#GF6攝~0~0u2WMD寰敲,E j [好@+qx抔"dVab梏xP穴Q&$+g}跣=+lg/屍lwY@;cU攫譲O _!慱J"ms$數踈窿.学lr]f]f4耕T'Y醫^f4縮te溲2;rb,zd毆飛K' gO,B={ DwcPろg ぷ家P糲p^RQevJ題tエb HQ粱4リ庁\@@c1PCZヾ 7 d聊 F^s跏p,ZV 9并Q/}GLL_y襯c讒醫%Yrf;-:\ku(X闥x"~xo.B },q帖 wVAxT-c.MYQ: -J+Ε!H9>権 j X:T[Giu+0 q6手 K勹!+=AqAW?&4NR2>~l4~5椚d/TFgrl[H{6tj Wob`w 慫-s NQX7 >)楷Ntq}交i3Y 劣>_/>jG CGn%7l 坐l瑩~JIhM8R500bPc~擅竡2d畧LV蝎磊1[oeN'這g@vVNT(Nu鴇)`T; B~ロ 簔焙D#Pz腰,(J/i%瀕8J/iEIbQzi^v堀9v軟 LpvOg郡a;(労D)+>Ot3Io祓w檳ZdvY,l-:m姙(zR悩MQ"サh楢y-cb}H 非Z,u 冖Uj \0>F谷+Y4H_旡廾3-ノ柊fU良?LNDZC=f&飲SZ;ぼlzQ-%[勣K5|92B;_2NiK(IFgQ召!H t||冠|_;"陬u$-8f,}m|La1[cM!l7H0te謫.萪%仁MJGkfbl'vbPHS@]<領!YA` dYO o貲N} GGX模鈴[*oWY汕4=G怨|n#4ScC藉M; mn超?ﾖ*\MA棺bi蕩##0^>{ 9t34s埀褄{p"}i%RWtRO?t裳喩7g{gst;% T]Wro!8\{"W蕊a梏這鶻 M骰%iy (c'鶚=Q/2J!憇迹踉bAW碼撕泛$趣JｻbUlwI輦e `詼簔]L|m8y+* :5(?[腰+Q(+芒'哺藤_廉爰<@ Y*即鴣F*>琲芫r"鵞讙ヲr黼;烋E116醤AD祖/筮B瀲07J敏)s澎酷|魂精_Ul Wzhlc_Dv<7 z h.t萼淌~vow\螽_#7{O[縻拑u碯畭aＶu+ /_B菟憬gW7)1u^.烋uyy衙wSMR_#計邃U誚[;i)貽ド\k 浴VJv黼,['VU/7VhnJN"X掏桾aY鞠%OCB嚮Vs鬪縒5 W(J +U%tJPnP0jB_mL#T96_)嚔E>剰DGk.blE.√Lo*"VFhヲJHO贄雕e^yE硫+:fnq~Cr]vG穿r薤o唏橇D0w#尻N衙|柾4R+QzP洪2?6e]]?uE-/kd{gI檣K !!V讌6'識篏FU+A%A H磅bvt$MlLS偲埖7>znAk跡A時ib#C¨哢:燦;;;9>|{8暖 ]舟]_臠f?7R{a%liRbO%攻s#$+0攻(_AL[U|N鋺tEzU %:Ojm倅特犲:#H学wt:MUj?~#^+]訾sF5h)H'&o5Uxo%V觸麁'b泙瑜F"x"$霹Vk]O>|UΛI3g行ぼO}ZH:O}?~xGK\[.膊Q{y#eG; %S< 驪al煩高G&D9V"~C`q t;jsaP ckB檻*ptXu5kEi\6P_A:J0>羝4cqlM鱗灌P@\+ V溝NnｰaY-皷Od zShr" D<)1H<6!LIZ~e qxLN9Tg白k>]a?|dO隊P顱%B涵/<_9 uw槽F%/hG_o舌@22M JO H)EvWla+g:4xr7(EL3m腆c=Jyr/rKoxwShs3粛O$YF }ＳﾎK些AcF 癲c]AXj恆|O}嵋y=P鵞!煙V3*! JVzFJｸ,dg}P榁s9X/.箏?r辟\Kh照w帰cl汝j嘩/F:m慳r@>q|+^B辷N\vEfE5DpRiy:])h幹R楹R$u:HJH VW:AWJ@~OWfVJA{R:| Wj*8W])HVJ@SE>49按蛽zrR.](寡&/z蟄_>yg/瀛::#險T0{IZRE癌9ZG.al(1J>-GV鴫8pyUGﾍH+R幻ZB 鏑fxy0C φ△N><) Z各%f76M.e纛弦Jq祢) W\@?kN-6^#項鑪m袵wQ{7碩\= &!P ZZB 盻{Y[QJIa鴻療"}C7"夏 9:rvDNhiH0D 鮖"9潰D|>gp癶z=≦=墟@宇L)HO軼哨'B蓮фg佯F仁=諄逼?7E筺'jmfg罍a=5諷g++h瀲l@S ,W埣J夂y鬲苴徊力_45f衛]庵g(&vqvP妾%)6/d;*4'黜&V顏]3[.輓 QH6,Vf嶺_5SMD音yL勢百&>CLav1`剖SQkaX1史-Wmcf譎+7B6苑(?;9rc祢M6巳_虧"U度|8嗽p9 ]~8ュ謔爐r~鞄至3\Ω:?9h__酢SN1u淀|Wm/苳MhKJD 楕9Ltss墸囗覆b_IfRrh力f鷽W桝D費;x癩Z虧NWW`~w糖h腴Zg0$_7w僥I槝[糴O+骼'x憊]>_gd<.汪~ 6C*P軽+憔*X|6u8+m護Z[L 緑+Y麻8/{,}[T#`膸=$ +UBb~tPb┓8;嶺鷽溶/.V淫xE/RItU\gqg叟bi0K f+=専鞣* } g|zvrqr4E週! iwQ悴~$ 8涯0A6吾UVb|ymzｹ0iNY1ny u/a'h/Ml塗浩潅]匚掲FshEl_qz火s額>,wdN 幼ldbG*U澣廐 7M9鬼cI $M*p6誄*r-ナh5壜W: EmF2 VHz鉤溶Gc莓D7NfPk颯O-Z%kuw/鐘?嘱蔭*~2mF>渕G=`浄7vp吊X$ 銷,W罐/ sb+衒 %"};<制Y~'M{nW(y9?;1f~f.a+忸|玖pS{-ANЯ呉Fx憩z嚥vop孵MH喨R5yLZ,;[J京N麭WXG'Vw翼x"t1n\鸚W楮凉査-u短杁1!駘^\qZd誚岬:=篠J{}})Cy+隷鹵_k輯眄>]"R鷓貭lb'gW蹼_pSs鸞V\/!l E*/8/棟qT|q-|q)齟Xc苴蹴4暖sF膾zyc*ZFmq磊Xゝu;檗t8~壟\d⊂wb%e,W:K^4S".1褥笶V@-巒XN-郤4Y檮>;&FV,EpOKYo7}=厭模8|鬨 7484B%~+iZ滿Dc} 7] ;=-萌w髱-22碇(笙JG殉3p甓?m9椽<0w *d棚 設I例笆4蘚戸C蜂1却夾NA& 洲h7A~8vcY∇man!{1BjS扶壜<}莪2恭Oi'后Lv^!kLS Hd Q0.]StX/8?@(oL@cX:b@v▼+ど"第TAP[鈩nd曰NP-mP9 !抂5c5mS D>蛾D痍185#9r+em z;瘰c *b(g- uへ}ox1`E)>:Ｅ^'' XBRchi1 "hI 棘?Vgh8uEGiI]Wp |,穉:%Q$yI#7xyI d5Cqw\e始~%!FSyBIナ%羈 -90@葩2i_FZc6 痺*mU.cg 覆3xkE;'dKxE 璢友OfW展^募n┃$H94 b舖+ES{Q覗X,tzVQ~'@躋w 9^?噎豚P{寉!$荒s辣h2H>_<.恠>h Ax`5] 'X Q給,8P聡<俸s郁-) '逞/鑪fVPs佳隊縦dZjOI%}@H@rYEy+}/]h!+!Y夊w耜絲**NB.ge3Qa*jS%s学VL蘊/C康洩{B晰負+}%伸d\$%樫n{uJ羈+,ХR*坊*`Pr急UqR懐~PKI碕ｙ2 惓zjy蹕НIi鑁e] 8y&2賛Y|8=Zs'T[憲豬xlaIn3"Cv/{黹fS^9〇0yｸ4 cp腮)匚V93b森/JVf}k脉[g黙L駿 J&Jp{LGpQ89;B[4k憺Sow Z'赫朕9,`qG+39-掌|PR`~JO主^`2y~$C8瀚ih}!aS男=RRlvOr熬-羈針K^` 4_文L?.1綜g3]凅!!b84芬9(1+r<9RLX~L鰌o焜烱^(.D鍔JGFJ[ Y犖XJ/{l憤q)m"g&OE泊R@^l 鯀?wnYH/漫;.y鵁揀系x}嗚'oz羊廸~nSX~齣vvVVn2c雁FxR2敦G0_-2v gnxN680)d~L^1縻):yJb3\c'着b8xG18jv;<榎I穐匆d 9rYE%OO帥'RZr~磁孃>*k來8 t; v Raw撩 低vT歿(sr_(vUsRJ Be&3Y]'}*L 碾(Cuz/桓MU鼠Hu z<8%YCdI+JF形H@7G丑sQJ_#↑HazJ&社!;$*u;I&刈c@rN_ぃH]Iub~壞/JE/u Z'=l%'\ \gs|\v[ai簸Ev,m顴JC/⇒@BUN9壙A援h`^Z?' x0辻N!hD{RbgD5hZ 招HF;0DM=PT?A尻kTm秡f?.N#^yAP%1尓瑚d m$刋\n蹴 h* 籤KzBtb音l,.Nl vC)6%GcZ..Tw\%蕋ApIpS ieF".7#爨辧hEVqFN県G|a=Z6f]匐o(,7j>[w [ 2[?ゾul 5Jw尺]bTx潺tEE廖Xo摎+X p@a:I@ 8T呱患優v%取ZbW}6vBwbv仰9=FB9R/\9F7=i\螺t膤{7zm*ulp"3>^i:tJ0f@ぷ /tviVRk"/u$刪})f,RＵX攝HW\Jyq1fmE蟶げｴ冤 p n郊>Rk F=wa]=H篤bo細  HY觜C=VJIT%Y3J?9F+贏G c(nJ@ `+;$`竏3OO?|OngyG'{械)NCr 娜B@l16[ HO4UtB徐%'氷門飾苻zNx)|OＸ&b ;P[瘢$in莟1f“(I-E搗GZj20b kUC)b槧]薗(1 庠bhh鞴簔揀鬻囘搆|33w2O;<敘}rP宏S^奮#n寓笠爰3嬬)CVJz繻J篌o7&a^y糒(-s昇酌> 10p逮'Uw9s 1仍>G7弘ZjXYl.硴剏踴\.ax^.s[Ш`)`C宸z枋啗L泡M佗/{3tP7冒綜70溂wv;KBy`цK0創+~VvpAOP q0-#%T-G2BeZn9桷y BIFF味Rf燧z閼sTI#av ,H)aW攬5鑠┃賁 C`(1 抛TC)Or{忖,蓍qr w?鏥.榿蛭1波MX磴0熾}+P3 氣36$0腦%:鋭NA,萩0蚊 v凡K 鱗 9bUP亢G~ 5奬9)雌#5,C f髫s,~a2轤ui殷;挾疇巵避sJ!Aﾚ RU 7yおabi3?{5Z<過|$n;Ax脅F蟲<臟械${C隈'始蕨/艪6)~wua>听I,>b@活*气_佃%H=Z!~8 )0孅+孵t ]`5C"}碾G.LWX詠V澎侠 'LJP記RW}点"挽[ FkE6q鑓eN3:岨bcI|}屓g(3.Z@`枠 7DKa3P團R4C嘘FNVh#ｩ^A+yY兢8F鏨(^6E拝]]>俳栲g帙(武xC=は/DH纛鯛$9&鵆 W霙夾`Md2*慕3q=dx~~02富踰$N,vKM暸i沫c乱 LA$;QJ#d N@N@@7x炙MfミL&k蒸7帰 LAo2# /頤b熔+qGYi傘:An_n3]怜 .T@A_U$ m,b b'>ZGzO+3$狹痣5xqn)<7HRW)3`戝r89cY*恐ey$6高^.2錵b拘9=P@z1N!tuM~D""h PFhVWL@X]1H5xq:Bmy溂9kR(x%(|sN規喚K)%]h少襤 щ" 2To .▲u-〓H]旺俚I縹o.>~]>?素*wAnPT那loナ2&~-cBkG0,(q `X弍Ps外C?spcfx&@ 8プn垪4t "I;q立#8KGF%段2@嫖n7wxS.l9種轤!_|>呉W鴒吠p|8]WQfsB62O'候iuAlz~JM復 1A八Q貞(| R #(|jnUjO鑄7Z32橈K%膣)K狃,祖)y僉嚊消vvP晋H q m},蹣S\/ v勣4IGr/hK怯籠(7U莟9gh{H箇 hR9jP;拈 $竒RPAs^ 軾漢`滉]rz{7鼡e出u\3;Z猛e汀wb*;  H裙'z w;$*9R辣I宇鵤9 c19徂匝D1PHn竊TU奄蕕呶t$M[vDh螫yy凛=! Ju s驩ﾙ .$r根63止`Yh績*0竚lqIM$NwLX)6,|z)D>\Oqx7#ge[\wg1,.9芹Я剳:ku/x5餬/葢dmR\迯6QYK!FWR\R8 ^0!3g0Qq]m]$}Y 堤蘚G%h:N該@Z妲_{熹[`SWG1觀國NOx0 l衽^\uh觸*.J筈 WC被冥^did^鳰&p爭pD蒭}B,o鞦_l%#nl,4J]Mu剤Qk艦1A-)LOE袿]+]j鴨<x{qxw26.H7匡MCD坪6bYy岾PG慷煌CFmr桟{u|r!'P2p懐bY:^|W8/gWl!w鱶章hIﾒ緋|VeOb6!l]!架4lM赧DjD+T$ ad%孰|qA>%w薇-jm4@蒂齎 Jn VM$xVG'1 7$&]4zz 'L7襌OvlYA U`OP@Pt:W2宵_4it[va*]吟f$0M\J:-mB O{"藩靆g46BE70z勾T S*`!|jhY Z&[ "6窘YLQTek92閿s8}趺Vv|@nB 7 4k塚1| LfO53_晒;}|tz8劃ySUn苦gfnFX8eH捜O9[t~`s?長_葫f持YlLTfk榕55鼬j貴t7勦nI;褂FG 6\g 庖N|ｇ3>]lY[z$賑6\=t逸G驟帥>lwOk壷?!R ^ <~=Ocyv mTSS&_8勵b枠罵g棠dy41i柘cGHO` z/Wf真8A?/_}微G梢wG T#_6G?Ow*][e2l]=c7l!S{7ヮ5:$XAワqs岻x [蚰0Gp,[ 謔K祖Y=剽6L2瀘/V碧"33J`\? ^敗L-UX=q_G_D9*鞦(#y2$/;=庖秣翦-鵆#E,i艘}(M,穰rng 6n欖yK~W捩(礒Wx*F5*縺UrcR ;! ]Nvk刔懦`&UefjpC`Wq#*R志" lciBA"G嗤3+弐秤凭'Cwc2<1_0 W8 b#}u=箪`-#C啼mv-并x痊psr_掩bwG峭{ZJF人4Q_k騷=緕lpmXos6l戝}蒻騷!Mv^V :煕l qvj慣s#P ZV謐B!.!_y54W%K%F\q,2听+LX慟\iQ<倫^q.G{r穣韋l#壼lr8`粁Kj\H/%wu6 t^俺_牧\nrN~龜htrmPo~V^ =⇒mO?H恠myse^}紐顴艪Z^+B+!D_ds1l@X}0胴896БO 林7聖dV{ NN動冉)哇sJR^僣!~KH瀚Kv 5ls_湘載E!m盛^w6E錵X◆*帚 Xos暝^涅粡o=xZTc*2!7|肺奏yZS鎧 咾佗"b48>恚螫=?甌AWg;>ms繹/IJ"o['$onNO<=根f戸総&w*l褻化nw(d櫁裴&'tk瞽nJm.<粱0鶤#1nv%2棉{=X|`}|\y哇z+齢jd貢^4惴皋jlu巛pN76W瑜wM6/隋DWK4u3y悔4rnk2q僖 押/"^q~qO{nG=4 l07rLY(cQoctヘ聲SC38况L[@鬩=ぴn6毓6^|YCsI,qo罕6OTLQh"^H甦<<||%Y柘聾靺;E察m*塲(鑑/&芥@y|y8I<$msgdZ\咢%O4P{A\布.h鑵#應孅?痘{Ly.茆W嫺5"JqlN衣BZ溟z+[^S樛I截w~‘泣B{p4丹,,|A0g弦鏗之}fsJb7}胄亶f!g限Gz=5寃;*.庠-4SPrf7項柯防]:+C執3看WH]VkW&2=">&§羮,'|8変更滄&U蝎沫 }"iG(t唹;BZ{R~&dr>]Y塾糒4肇g参2] 寞A!Kf紕<w苞晟M颯ATrx 錠` 7.$WtWoa8;[^{|(5hq馬uqz戌)气hu/鄒-\=6~6檣J躓A裘FE鰾^/\n9n)也領~K殉 Vyr_;X\V9|bICE6dz薊p03睿Xl倹 2Xuj艀 *l幗р ?!己=|=廐譖駝RsPZost?"慧7袈{献?pk;rN/貢O`~#Thk 哲Op]OhA弟附?77NH_w,+%曳^apH__1?-慄%f wXbc5l <徼E^;図(雹YE濛K'y⇒汨3D瓰姙j畳譫甞=vG>A;H/珊c矍kot署拈F甜融C全zm鈑]>耡A|`閏iR茸 ypo2AsTT"Cx;[実:zS毛#MVq}`9*o^滴浬L8o褂¨k0鏃欅区郁‐qu=ezxD' I7v丸FnE&jun輜kdyk#獏t?Wf]Wl5 Ie簷c0e%n眥脣駟JQZYk 撹呰hj鱈2磨Vプ2+_犖酷(h38вz&鞏謙lA{0^)r7#+) (区0V0Z+浅NI鵤tiH~!XS畧{SzHq"@g熬C0邊316%籥Rv+~XZm@Ic%脉)QX痺}>?;>CpR P盡. IB9xH臧m倡8)@|似ﾑY)3鉐y挫4Z洶/i B+}8 a~挙h8輙氓'v:Xf>窕'4凧lg業箔竇撮)y駅啀|nUy+倔Rk`#偈{XE5j幡qz=hmw tr6" |涼]{~}zyX/暎簽芳> 跋*(>t晒^/?躍蜩7o_?'hX截 1tG9檢疸嚊=XVl6R';銜B欹 =|7O=e~w}D\K桑|}[1=l]g 9~骭糺 Z 0c#7|蠻Dnp]pQy1??cv^ *AK/B(" q`PP#vn;{衷97晏輜rwU9qULtD)j9隠rb*+傾(~e& 馬D~精N)1RTL8u{;*\懍烽K'Ad u9%lv` P3?~s剄hF麻=.膺影)/ 簑腥綏 宣 .u`:^v鷦撹祁Szn< j$1ＣL棧o第 Cn/0 Te{4 @owS^a2i9)篌* 6R汁!@F@k85{_~}ら \+A3O}cu 妥3 |鴦p,)j DX :H拈]}忸~(o凱xdOW淕渋H:情&}o9~8,M{l(gzJR&盖|樊Xhp楸=V.薹鐔R韵Y椎兢T浣oeX?]+迢繿[K `b尅cj9~+V'v&ya<簣侍7g{g}1Te_/ga枉真黼絎)T2{|xSl:夬DfK垠~. ?i撻\&刈B)$^!FZcpKyN?izAq| z<h縄7鶻帥/L椦⊇h苻@Dl帰}.Azy$>p}$B8B|4$e*(>費A`Nd%P贓?EJB$>h/"!ｽT9#F.YpYbQ ]szR;'燉6_ i 1M僮Wh+g0T i2 xUv]3(Y]PL歐89m減h&> y 愀Aht,-UX@G 6P CQr磬騾)JM0h]>tUz剿頤堆叔-k3漂29 , e恪PQm8@/7-b *_:C'rMkBrY闢BYK2(j)#Yu甃E$驫%箒zv`sh? *#物豸c#Q>JLhNot>IN姜1t鴟C7E=y|kN =9'舜1喇察J臧跌}%Kv+撕耘^{Jc= )V4'F8jiJC`j/`唆I+"Q椏DQB:懣bECuD耕L~屑愀L坑@| 壁*7ﾍ#渦 ^1g 偐[\ 碁ゎ^拍3:挫籀}6@/!戡m纈N.DP愼!)錮A5uigb?頒PO@ vuV=e]蝌. eA(書BH杯xEq 霹.w *\7qzpM/XGk#<rTuY<楙;@眈=+x,F`Oi 6U3A5a: v歹WhqH/M+3r`e }C(9 O*vE!P冑^At菘A彝 e3C( =9 糯PsU認=cq lV H6-)x|/燗h覃(@]棲4疔┿ !A9:軼nXyNfD>♂5&(淨．`Z鍼 >8_eE]襷>P1k("痕R-A4q樂蔗pd!w UZB剄w肌A" RXj纛7G艾潤%F`bCOST M+A} chn4;_&x峽s0虔愀ln5 m桍wN矗ZW ?2Ogw-{`f. qp[ b(pI"P嫺I{*嘘ｬ6{c6櫻r靤2瓣CvX絅U ">("Rq´洳s>(^,zs裙>4!(o!_u` vjx3Gl+Q枇-f彎AH_槃湊NoWXMB1 UQん黹挾2.厘EoPeX|%0f!p/9,卸5c8\8htxFskE]Up,j+Tc o蕩;@t&0ke~cn*jv科P1c_jcf{U*賭 K{b 6VBsY:_u凩内7畩J|iox緘&υ7恢17>( 汀P\@c遜_9菘D?俟Z2|cG壜K9fV佞b+Z佚悍N'Th_ &<+NWUAl2螽b易_U" GZWMi; vsrF6D{L+0頭H"絃JK輅I膠G駟}@i"A@,\zHA針{いf,u` R銃[G災 遭)攀xT{L[PeQ+.I$*R埠 4)^gP.%mC=45精16Gr賜/蒡8VnE腟/1tS暹‥狎nqw粛 z潤%=gAw厰relH"m槲7c[hs槹U靤?y蕣?鳬?^s疇B^t9Do$鉞ｴaz;oF3J|(o牴/ yrUI|eQ|^IP1畧a5XN!D9^ `3e桍fH3L % ALz}f22EW#!Cnq*]*：ud頴M!%b賎db=Ha檻淨e鼓ф搴'LAtN0ps考5Cht}3丙tz腸 僵%Gn勦7m+郷{カop2V2]C ]i敗79"v,槹9e.-!SVQ; !!D6(ttCVl5蹌Ap96Qp^關tL ´2 $醗)Vh係q/}葉CAF思UI #txe+{~!次HodylP72X)^cl;咬o;溌(A嶄Q}E'&.xl[Bf止^衝W0DZcVlzh%d[T里U+拈Z翻乘'+6QUW]GeU`ＵLYoFm英U篭P DZ:gdG賭Q喧} q_▼f窖" Czj壊偉 Q #o 村纎$8躡東T^験[`9nWav濔zJK擶|_q<-:JKS}9p8成*T^L+|a害"IoBDO('KjYk:2oxs9"m..^U[ONZ V-] d Jy_箋@qWB|@D Fut|S|A{的wn搾3k駿N9eP膚vWDZ;DjTyLZpC.K:6!6@=纃船9擡H{N;QQu'074wgg43+Bmy6_\恵P褄P權|0B牲cotS.Bo'}w Z$et"菫D. ~5ﾏC祗faA t'忱'yj夙筴"\/Mfqh6_N(z lW&o戻 !∂Kf厚R[D`o舗{A9E薨 劣  A.X?腺q m W2(渋]{X{貼L舗-方d(港 1wS\F1Say,井M'哨 念$名RGLbH0j {@莵艷鏑A};+yV:8CjFC0u [ng *A)@gk只[lnG+v{rh+}::2Q訣剽[RReY iN=VW ,v強mi*88WpVfF\u(D境 F (Rlb|D# 4p~]7abC 庚:辻P5劔*綢E$PxGBX6$.m6]3N ^琅sj插:uKc a`w$ @5&20>VB<惟+謎Sdz!}甕\! M}3yb濛^K[pl戈.g 坐曽пP-s.動nh^&!PDH悶Zx/td,w8eFT~啓|~[ t&Q行M坤y37x K祢俳M+魃l1H冠~>s 慵X1:+~}G揮U&hNPo !б<*JDq 62G_90z!歙遥x8@怙炭;;啀$I)葢 _じ龝 !v[餉["亰kp JX 忙2.F攸麈t;DK[＠K(]&$CnB[!5噬mz#加,*] [俸#6{08 R3F^U i処*叫^aｚe(ル7g4mb}墜∬K滸.cQ:RR\汲IA!ﾍAV奇{肛e)Uk顴酪f,:Ra4q>MQ仞 匙#壇Z!(6(王ACW虜Ip{VD ^`評@jUX6e,)x_hG}!srJG4vP鷄o:kYL齷溘揩矣ko:凩Sp絎?[k1PEq撲\4!玖Ecs3:) Z|Dd8JGV蔵3jR v剳 L`6mHK6``躔HM陋D$両二 m77n^{X9I5h稱c`c$mq效EG素%{&処識^\/e 詁idk豆擶A蒹d@OyC1q"髪!<`C&?保4i.+夥|er![Z硴v2-潼JtICC量v$ +螯3__;sLA3]L  X)蘚hH斂 PHG&8K1,i^|hz?°;AL敍 M/ｻ616Mあf(z- 8奴A*QX`(R FKZK=廷EY:\括9FC}3Go\.-0H粡駐j7]窕?-QPVW9欅 |謔t`bR4&0a|lK問y&nie/ {`&F[:m盡U惻j憎c仞q倏/猯< I!p^`輌OK lk\註 ?玄鯣tfl鞜-C@b藁63俐PR?掫-Vlr踝 +#&d@;解] JU払NQL\}讚c`#G3 陶}擱QBW)T)&vl崎鯰"dSr &$H,tｕ@冫LW:'hkP m}33NTaHrsCotょJ>蛻 txK)Zr蚤cd4柚bJol!潯凝'>K+_Zx煙$V}hZqMG擾GHEkEa^#SA書/a_< qpot!Ew0d[MI1Ir遡ai5I\r+Wc(Z 勣a!i]PL琳K2X ]RX\j-:6R〈z哥*aAr]JRFc%BRFC;r15(3ｕ  %1*]V9{g >u$tey杲gE5q豆#盈膤STul鰄2擺Y（RrZG糅~B@XG9iy0巍!T,Jo"jQ z哘Hyt `^&N0H/ Z(r3X9B薪z"G昃f|^b-M7鶚)eTl脅B#蚶翫)Rh酥#3宅t減 yl照 }#E LArN S!jQ 娚'.1O={宍+_q Q"e t献u 0]ｶｴm-f4n#S}Q_?授/r儷s#?(ss o！.mHUF葵nDUF-@`#琲Dv'{_u'XWdbv?9fXnuXb~?煽X偬kK猟дGI桃o wXV< 鴿抖歛92fWtrc麥Ra~o$1y1恃ejQ蠏淘>f坂r"Kq2c'g慫3%Kj n cYF惰P!8= LB o継v襴T諸Y2jZ\S* *j1G!MjJ粁: `3 dQx4`,=v 姆x<賻端 "婚xLq俶"PU攬*滾# tJR UPU]'tw軼r6$`;i/r条#>>2=v^C/;Y_Lm\YZX]洩_"?*u:82 ]Sq町)S>E%N瑯倉ヶ+*HD鴃 wS$6 3 ,620L,`勾G88#$X\:\W:庄YU[bYT ([ ) 砦g4義r!Sepa阻Ilgf7M6n?;7坏悼蛹lf9 i洽vV彊覽wW[N~i<.悃{q O"・'衞Q \6[_y4=r$'g-vOゅ)|<e岨w山>_r麈!譁]Aw[翰並V瑳沁GMS^bv<{謫&\W-Lo雑囚e髟4:&{3. in銅brhnm懶 DZ,J:4 7#[粂hYW^tF澳窓/K 2-0bi Uc2RC5coﾌ将;<10T踐賣<hyR:覺KZJG=暹q卉uj\ }#W"^Λ-:( fApdY Be%i/ oP@賓Ce~K5AH"u$~眩朔x8購L(uk内K瀘*李y}q剞WMM#=貮&5X1盟EQ!Qal`158L☆%Dv+ [尾ａSy蛾8aF!q,3葢t(3HG~ ^#a馥a牽:39K熔J.j+,5s煥Y) !6{'PtXB調6 T[;0D3dK埖`')柘c6醍,殱oZ陪c(弔 p杏/C8>XЁW剃7/o(Tth&J sp7Rad鶴}Ho$籀*15fr=C 勲9|収ro_繻qV<栩W5加ｿ_UP&+ hc4 ^E皆a2隻R1JIa&TDv>84`!)求}XQMY[Qyh0 ve懸 3D(uqU ~W!&h06%卮{|2Aゎ甸U 嵬b CHV猷D俾,の劬HcS3j~&nZ葢伎*LqCL?QA:$n A!ml dR" 驤1MNz殤?s |瓏';Pv蹂:Ewu麓0 p1X{.6I^@0耙KG晶\('T35z? 釣UvU籍I啀<~SF|SNf潴;S@ }p~tji;穡S`袈T掵HR6P`W(7% g#g/944\hIdPV詠z&pAJA(熾 %iJZMW2懍n81i`G黹R 8[呂u+Oz0d?H帛 u'狢 )Z!*nlX杪b此荀TH-AqD'T[* 78*2&H甞j:0fx津ud50;c/幃/R:t$7xUR'齟XP播涜/CP=蠕#a歳獪,?KzJWzv+`mHгE!钁,OJ FNfrB攘E塔S:d l畩6萵6D軼PaJqZt:ネq Bqv育d鵶^uV_Fe$aCJ8ho4ZG辟+X$rN:qNr~1WF"yBJzSI)jR#OXnz#鶤kb灌 w/9*&i2v螻婦f:个@Tfp{ "\痾茶p-;k^,\A (Y久; jX Y'H2L0 鑒^d|n8I槻  : >VdX\#JZz槐neI<< l防m>/X]9#穐dfRT J!7鵑8K oSa. ;胄by8e)\ BVO!d>-8x I[/筱mFxS1(Fg臑x bhc^導驗lTb'KVfx萎n/ 9" x扛Sni讖$ws^=F3O肅`b:簗]X^9f{&rmvd"iＲK!*l$L$? 攻.9原.91kkO  xwDs,頻H爍i1Q捐&d粍I+B=U|}{號J廴-N徨V_';Nダ \両@J`姥`|) j砌%g:M9coι5輪{"i%!.業网o陽sH{Z^!d* !s\陀Z !巡"6処b烈襾t[蕀>2,豆＆i4v狛$詛4s籥0+惻"WWB筵2 _昂/J`A# nk俳S(z=2ulr轟L\]-!va$f/bX１ ;Anh*z'詒[+K|%痔 %Xxx2LPゼ/L%Or <5dIn:~横, 鴈O<5'fP$很'欺GB{G={=[h`9T眥BWgo隔t <)悳dzkN@d.r螂#饗 2"曰ＮQ2b9飩]mEi0JHZ蕩懴-p| %(N3%!X/=?I0汰岩by楳 E<=Q,m漂pV1HZO tL虻B(岶D djE{#DE9"G9h/`d^擂fｮ_sウ]}h>秤化vQT嬋IhDCO686俥rxn7k:#8U-塗4i研kB5D_jN+c潦'kLfJr摯9娃轂`9 {0:D BgC',B┴r嚊|&9$殘vb飆M}T63A PO梵]JaGv¬Ky淆C RB!8貶$Nc票d"OZsｻ\ i停b-u]吉:圷 O漬1B6M>]j罘JMT:)1 T@N0T%a隋4O陷P祿.)|冑KJ)ts欒囎M!-Q P坤%.:j7*嫩3`0"$[ppL%5TSPゼT勝o*/R(,嬬jf Kl厥7鑑~6<培5_|qJ横!:霆!JAHBD0&HPd;8OllM!\ 5(嵯^P竪8≦団.E7(ｌH uQ#t kT#_>6 r]4|<\迦o0%R~ 鎰>*{恒o:RTci内EY;Jt*xLQ!;談QzH%u#5stpeｽ(/9@E%r1tS鐙z澹Y![GqYh歎jd堋o_m6酷u~撹.I麋3卞普7屬nG(5нRgUj&閧eIZ3BU煕f^'G宥cQ嚀f磽wc1F6X^Y篠+?4Slhq7qt=FQ蛭904gOLWk))jZJ'UP5i?槝撼X?@M)~ziD!?'jJ=!_`G[p譴ary艚鄂=~鴆刃.+;婿沒鷽|0;衍Vp2p xqz#6(Zm|]E^q _A2St~穎ur^楳g+#qjBp9Z魂4p"ｆ* JfNT逾*5:)JP.弥%"_/QWj'綸銷b~wx6箋凪U$}奐W_汾括z蓑0黯JIzzXv y`wH*] 8T@潼q&BR,V9Iと絲~35漾',9{*:%An)冫)]vJ(EZ C草!XB8z半紂LoB/_4p/淒琲+m(*xfq[u96L鱗pQg*OCo饂0Vp)N{FEoA8\oH篭U&赤mHzU(堙吏o:{p!u,O鋲@ z:磁]f[+  凖SPA5_"c觸`YK筆\;=*Ih/)&愽=[dK\{#>抃-)aC靄俔I115f蹉榴SM]蛮 + 眛0 姐9q%u'uL_Uu>oS<糯,]o#UB:猜 !dc襯z B``JAz返_0響 卦 兢&{OMq涅4Xe勳Futxj堪+Mjビ畸ABJ^<\go_?瘍o_傷?}鯱aW[=~BP肺貯度'3鳩;c*.D%oB[蠶{ I`qy2g軼)H鳩 _a|贔rh饒7 ^i -B2噁誨6剱W糅$O堝7緊s(9-j賀妓'*,RWVss~AD<%Q]x@ @V:/V2J Jz”3"dzk#yk閠勅 /lb^攫#lQ)5O&Y]r驕鵤})Lqm\}逖U2dP蜷 FQ^MEKbMH:C] K J3儷p擢j7'o鱈白q滕蟷健ua)V@^m輕"斌1B羞OA_@1[u `3@:XXl偲'X徂5ll@j鉅l-鱧M|猯`F&Iq&じ9 4QGW &._"' g-.;Lz辻0K党LAJmヤf)I0軋{ bQ1F[LHs)J Ppz飛|遐 @w\篆-v?T#z<遜円1埋mu\8 CH蛋得_D%贖rG&@!%x圉P厃G]+k,m;nal3{)34;a蛭dB拓M76Kfu,粉\ IB０TJ貔股alC@joOP)k+攅f槃H=3VtXt|罵I_B画V#\s`Dq#2z'.(#鰥映1HxUZKV"9ｈ cTYs.乏さ属:8< *}(+ciT^Dzdk8 g-SCty嵎E #'4.qc a"{K-"pF,A&5K=@[%gA012慮No\M\rZ|nGSblXSJ膽H粗7@FL鷯hZC夲Hr楴.y$I&zOBGwy:#&#IAT^)研縟堀瑁｛i)i1 沌ﾂ1 讃Z"0v$6 hB}8lm鱇sQ).Dy囘 a哨0Md#W'O0yJSU'|諱)´[Q髄^1)發H RxP"\'}BApz:hZ釀覡鱠M5{{<`]L9 SomDa獅52\x&y'>C耋z/佛QZ{循_a)v%賑9*@=Qe参4.rD0雑虞j)VafV艇れCl艚VfUXE憤saX,臈) 5.速q.`Вe[_6pM♭J:枌參g喧XPp#鐔wt4Q*惱D;T ひS^l粘> 9I0q6u P盧恪k-[]kA'i~y陏7U %xrX8|桿"lm`(!K _|6^&'堽BKFrJX `th3^巌羞VgR0va孰FnBl}$ 瞭8:.u去t[TNwkuv3EXyuV!鞴|}砌K$)j 4DSfJ~\I88皰9{Xz誤fE#aKr'g(admr寐oguXG>jBs距}鰓r必q88 L ZUI3噸YhFLK7J w氈n%kZ)dyヰ: y:娯C傚*ΟhZJ\K`r.u(Lv4'uく韲acA.K_Q]x5>Q^鶓c`P些+EU7r{2∈~8w.>9(*#)6k2!}?4)}?gu!b8偃iJ\qS準bu&+>iG$1M歸z 怏&jMC)Y1j謙y\檀w辮]|W歸/Y+1tw綣0h糾]<%Ыr\Av]/蹙jw錚懌3=罫j'XA唸T設P`Z,G卿蓚R>iP-%4P;P]-{ 2 hH}*cD塗Q^b朧>@NZ\5b0JFH 槍(s3GT嬲 v}eF漑UjWfDM_H-r鍋Bb瀦|"_^.Z-.Jy9l~H五Jkz&>T裸%托>弁 ia2WKHsH) \=uS =Z撒x鼕F Tn ^9J掌pR2}.B WX|.艇6y錠. r# 14鬥^6L%6賃H7CPｕ0F@/熊B0bDM 惇Cw55 liY)簍'革R=\2%%6'e胎つ Q^IC*9}=JAq:(E|7)Rx L\|k^:OJQ祖HJ;B^-db7酔4>#X靺a{奚wN/%3<⊂]RyU)Q J=DW.1d糞`3jVj6@GF裄I~^*9築鞦枅(||z癜7?>|#!霆uSbAue S擁賣Sb'捉t,mq2%T-vG`蔦丗8to^ q頼jヰDn-p逎oV快Xs r=bx]梓E1J]桍^=ixNY&]sz渡7'鬯L$ZE>k,\.E\W3egL.=/=晤M.醒[|!Hy緞(筰d$9<(e棗tSn}R|'^zs;qGgq;R@克7T Nl6礑\AG>C c=r凜+Hz;Dr凜m ']"A/CwOo斥縡0YZ H{i俊劉羨 N虞4VFi晁j$賄堡yjQ刺H吉;3&{).by?D{lI H|amF2Q?O邸8|宣瓣" -&=/{*景hS檍.#瞻nqmqR盻zlb ,FН|^D]'"蟶w\k d6K奧{\同鼬ギgN(Qo6裙9fucw:45Q$i8q\J #C#珞хツ壷C鴣ZDb'N|茅~B5$QVg柵NF\[濛ﾀ(W-+ r~C鎧Qw>WJjKbq%Scxc\o`Ry15 +0M9MH 颱閘ma! )F^UM照`4/vU DLf~Ji-憾-禀鵜淅4.QCPkH遲tDRICl:h)q|tD1Lc,#y)$:$鴨(WFRx低biP,1b綯JZ循砦2m[I66Wy|2>畴gIm]^=|qθ賛Fo^鯨;*掃w~N!'@C1t!C[ 峻oH?|o$殊 2jd4qxKE重5:=j gK)ご91V2r'\q_UjU,潜FE1THLJ 跚$) J越V f邁c.n恭|y^D|Qh%U L4(臧!"x~Bj-_[d藹典]Fc`Х`#tH8qis#-]`N+諧Gk 飼]Y 8M昜黌f79枸坦{Q3\ 茆b↓o&eC@#関?1]m1 c_W SCZ彌%M9%鰭3EI塞CI@?侏U{O3Н8uUY-f0[r\ddRn&\猛爛簽v>G_} Y醪RM瀉Hk5ya\8 s綫!;L;b駸#V#-((?Fw密/(kZ P0^U(.9.dSJ 橡3[~Y~aヤ嘸IS1iKGMglよD/USS\t準E1憶kЪp%FuddRr+ngKFGn貼0D膈峙y(oL$醐鄂&刋Lz遯 e(hy牾ę5TJ筈邁 ざMhtZ#O纐<G陰E績測Y;Jm&=>5HY#E衡.((皸RuvHE膽隸肯+&K)O!: cRu\?ERIrE紊4~p_=韶赱|煌'm痃fM#/'I贈3 kuFE I'':#父rSpt\UG巒7Bbx{+k寉XZ~d-Z#\9.rv bI9N'!ｄOb\H"Z町簟Gqh餞-顏篶UQ\(朽i(彰s3疳諱'僻3Kf兪粘"2だJh?QMk帥8ラ&9[v冑吩-6S`W麋 圷{J |s蝠OB[hA73/X覇_ZM秀Q 2翰#豢GD~N,3xr ′%$^%v/-送>: w d枡秩(#Ofj糶I.d`莇NhrR.紐R2I V繪r,圭bP MC項-I}蓍_G}派zn\軸鯤U }2p爰Кm%[9OoKp摘iD+d[={卿yV5ま室2kEks伍P@p 娘msCN都UJ貅笠:e萃:翰 v雍gfG')5o)%E2 R"bn\1--暖yび(粛\"8Qo#_弭bD T謳#m_/!g}廖E@総;c>ZU\K佐(6VJ犀fJ0q辮颯n 甘 ]鶺.M_m8O&>GQ uzh虐8wYa8泉4vNC'vwgs2/ 傳 ?gWd^4(h(]PRQ'-7yMXV)BH:\V貘Hぢ7Dw4#壹 H:T刋o^J"hOROsFywcZ9?Uk圖R鮔簑BNYR=BN脇韭*/(4]栫,QZVUJ`W8oUUJh*観i) <#1CbGm!栂=E気J)FR)錢`Le**RY"D^1:$^B]2n+?*+Q"kV ZE踟X #/2#2 p\ Zk%WwABe +)QV※ 4替u%覩)G 4z[戻棲\)瞞K掏Z@6P`Pkq^5o{'Я!羔掟`膸W俘PzY!J%)咏$<丞kwFI0xjxTC%G 粗擒JP>仄+y愕栞."B膈1)ъ6h師?z"p(o BTA+P5cSVIx"W!ck"3J誡;CjPVmeqX竄膾WR陸aJYw%X/{z=rHXgk ;竅H3r!nTJS GsF鋭SVX7WA78:.Gy22o)C彙<"J-T]X)Q-‐v0VU25苞UR9pH'k-e!"圭#謔vVB.Zy hAOb譟E3KDX瓩XhQ_SrtwiAc=n砠3又C.J h]KN嫉lkvu秣鳥x燃面D %y'4辷,N=.]BrIgP 狐nK~u! bPYWCB)sg改Cy*ip綢3E)W疳KY)i4糲諧FU{誌 )絧t「/~礑SRE*dIIｯ=j臻H3hy)-,9%hQxW(/gx^;('}紕Ljh&檄921I#脾T&ri劵1% 9r彬U+嶽 3脾jy bBOwFyjyZ=uby噎簔OQ"x~PZCd7PH7IV4GuZg J{)oLｅ)dc槌5豹=M /p?N菽)riY=q+絅8q{Vr疽{F eAD Eq(_b横)蘗4H k辭ヤb_VrPZ騙 0 C久.NR竦套.FKm佯Q偐潏6ph1lr&韋J '素}96y麭y兵y z*jBXd8.HQJ2椨63]Ta`SO(1 Ev 21'KベCu法x;XjF\yZ檐卍i饉p1 3T艪AL綣$HN吼u∧X篌 U^mx]o+鯒 nu,(Gr}D. 曷Ty*D<,簣NAAfC6M.>WQ苣>酘)_閥e勍JTr究\/$筥:#剛\b\Lf7r=智{+WS+(剣R\bu K.rr gf` Jj剌]y崟1E♭.9倚DNhmVQ3}eglj{N`l)b坂R#r:|Lc壷-a8^biLIYzy繩輪}*uS.勾$Z N里謄i k}O)#d広)ン=ed*掵MV^覆督裾"Y2AR A dBY#j~X\m"$>kIv)^lsFp,0r,當EB#eX:QVCN銭$uOq!,?^rFY3!惓 $C9*暾(X恂4JqYYP瑰"薩u8薜.Y,.R( .!;M dm蘂D)5呉勹^鮭SfHn^{k [J d擂7鷭qat蜥k\{P5a桾癜^~qn;E悒8喰e不l_QMd9虐oN'#+~FiiU渡eOwBm臘cV'3V#Rj 賦v=JR/v1?N工\F8g%iどe>NI#溲y膚[4r$楮-I#$嵒途望D右9O|2 差2oC距禅4\[92駿9.躬R清 倩* 'XABN,16丘袮~邁Pki87*GR ニk1e禳kF(I攻iQ() EFnﾈ(_#k簣]) `還)>z淞纓慕Q坿k"^箭tF,gkNb1原SPbП+Xy2+3%c| Sh-\w?偶d浴椌痞}gpfUJ=@YogTN89$<~zC]\ュZJ*zA *+wDo+鋏I粋[h租w"B' #z裾甌j跌# U鶩@側橋Jd|//3偸柏 TR^ Y8b(#[R(QnJ- ag作q5{4 ~妓C,1>"lﾒ芳4kB+腕IxQUzKo-hA甘3肇Ξ蠡}Z@?`*{5!g ^:BョlXB0GI-妄5-I85叉霈Rd禺L前VPQ[o尚]0FP%p4/?J{a$y目]繖LR皷5竿⇔EOiD婀椎蚯uv柵X9-B kS襠:M(gf#|AI粁3jQo '}p茆録挨7tp>f ~v^Y:g,;gWStふ8r>}9Gt-s]1soZ]廃,ok 灸dY''隨gz,m:I0p屏}K.統'?鞴?F@wD瑟沱7_.黛迸君 ntXC~幌=m #8I /0%U驗pe!! /u>':儀mvk<窩趾支4^驛3槓搴gI>oV=繿;嶐@EN&(@eu儼T?B~鍄依s3 MIb3lBJ鑛yrw_=瞰=/ 8h-H|YDoLJ7dUFpn礑-y#歉.\_Wb&{*I"LwRHM*,C'9舐Zh_RTY=收A貌4C． !炭"h#Yz枇れ<]{r砂.8 7)NｈJ2Uz3{R2vR廡M+*盃uiy(!w ~賤%U,j]>|Z]b_cUaGv竺橄X[(ID(G橋M9t}(_!w繖\IA%h.*d8WuHMUU亠:4H*:r*N& S4|箕.韋tb垪^鰺g5kQ 3頗1yんA咸Dq+n.9?B$q,#睨pxEA)b M%F#@釵[TsKm勿nU7^9Nxg'S 鼻K#g'GO陸 ]Kq] UU^TQq!-Ba<|$X+II .{坂\EqcQ敢_|築GL@頭┌\L癘)6,]q昂X狄UK"hi)p叭V\89ULずN！:gz4"孝Qlc<犲pYSIN# M%i)p[Q.@Pni*8I"B)V]M;A5bit且擴GJ9竪*QQ.rw(>u3[ ZJ舐#Pw[(@叩#\1D(言K"P:L'x5&*錠+c|Z~饂^}oo^搗`9*4 B6Kﾛ煽sT姜%.m賓栃(2(穉憑竊u点G{kiDnigQC(脣BYQj0)ph珀P?i>%;益hPzB3jE&#u耒C I拆>#=琺3!`Llzi_I2衙松丐9酔НnW=}}] 杠~ML擢I'@!M>rS%u 9些 k]<i$rF藁4)0J9k 9.0FT飭輪43*IvF?碪V^BI2@^bg-ATYE5Q$B|FcLcT簗Sr[k@恨C>wR泌mB> e7c3&\b2bos%I(H'}霾E2IW.@A漓R戔黜) 槲i`ZDHz.c~l#  J庖$ hA1|35I88哽6Q寥?)D=ry)!PeE$L'PWpId蛉EUPeNORp*]嗷us#,&e`RdWsＺXRP\蕊50#Hb. Q4Fahb9駝%?3duKs軣L%\%s甦zq+^gnv-Βr6g 鎬:骼)?L xt卿磯f慕e$1p %; P D9S^ Q^ n^`'9N誂{H斈畴君^d弉Y\@w|Qo=aH錠肭/m娩葵9!i)隹$]k`TKh 閭%[ZGpW;O醯]杳{clw憑鶲泓感,%(|#rKV 懦謾~ZJ5普z*6 AiL}+,/V/We耜 a j=j{[bm4桃(V^p咫\0:"y%dM痴hR58M@\-kZ/O栃'Sg鰉/床鷦iY3=誄Z"q*乢%Cp45piE|r''p<禧PFk={m岔u2jB\G廛YD4P狷z挧m0Lge*Uc磅DVL/{2.DnyXFBb<火yFP亢<V~%慂/]H EE+?3V~PQG/TU讚R)箸Q(^ 瀰2v 坑'@-l@- bL (莠 cQ>\cwｼ=8B\|yPc(;a口瑾庇VK雀-佞急?S;L嗄EMむ&L|R.筱ブ綻婬0re,$'!貊緤E髞ti棕\4REx上GYNr.吾!R]詆 {a'h$z?錠5u!U拍_~_~鰌恬/_}耽~\^y\歃n=oF"h?nh裾碵QM?h_}Wf>h窶[$/koWﾋ~O杉ZC/?}娟.2O泝{?gk 濳a,菅踞＋^0 几{dN9|*P+%SArw,例H顏縄_'3 ];[J枅BY2tH9卓(\N<6vmm] ~瞥P%U_鶫植關髷樫N p騙o愎 nDUjcU-%D7^Ja(%妨`k m]N$jA詢 JyXuCp"0_%P脊5LP(U<&USI紐#<Jk$`╋#HHl.|活h祁磨}塚p畑Szz 8 r曽HA6G`3πG趙aA7>~_.*楾.|驩~/010meyh$`Wy)Q6B{J-當X)儘|贇YVw{m#!0>@衄叡雎!7R~f%/G2\穩M(lx讓d+ W鑪風VΛIL=ye9.-'r釣6Z^B~V辯 達a9M= 張I`x,yV O畊DF:)ywFKax斃z)C6z]FF楔uV{%陌 ;$y朗 `LUz"媽().uQ瞠yU6pcrz-}u'養p aLNjボ&B`Q`G 鮹W?qLF烏*+(0{>(g外W$@9圓硬Okn_K酪Y圏|めbj>i ｦ@J溥葮嘱馬にp^l侖IjXU%Hb%6,Z4kツ=`2A苛PU g簑Kv2ga 1!$杁.BEegUv了Kh)抖^矩KMLf^KB>珂名#△\ RlE眥}Sr5"j/ぶP_w淵tY56nZI]MN/巴iu樽iaNRnyU夾N[ E++奠Oy~OYу5羣Jn。}K)K$C妊a \ａp5!o旛?V#!3f垓!f~ ] 舖e奘暮儖l%#JZl稿X=B) 梭頂;Ehz(點睫杳紘tぁ 莱Rj,脈.u/Xx_"/蠢懾;BF財)E6~JI 56'；cPxW跨liヤ醗JS&C 薄縡D| oI{Ψ廈E[`c絮Us:*1GSwｷユ$1#@V攜兇筌d、 瞞!D r`.fc落‥CuU*:+>E瑰p_宋C#ry杙oWi養^1o8@;M8u HQ喜LET\7.n\'LZMV5mryS侫 ]^@H鐚z窺伎6-V醜_20r j_kSbi夙EW]6].U*鯖U/O'"_PHqwk>=CY gR襠P}X,莉苫 L恬\.YsuR證\狐H:W/酳2wMc質鏈v`_}U)p'UP$ m謄No6sR猪U+a|/奠Q搬濟l{М%C_<{|Q,\肭wf.U範MR艸N%9!+0#帛ty仁6yh(gD(封OoaOlBw2;cW[x吋pю 9EFP5hJ黽Z(%瓩J%"l 5$C .)卞Z$ Yd;禀(司D1/r咤I/"LTqL"就yrl PZHT┬&Ο 鎧V鏃B種Z$MU'`z.HPlﾊT; Zc#i+x<胡Qq[[0>2VYN煎r#2Q )"^-) OGR竕%T] B{3#¶*U(7"3#)漾1F,M&D告RyT ?uqw [朝uK0V=CYIn/sQ票T(uG@g寿cs2甓hHv1\v XbJ=df|g6g箸abf5L^b#!J7p諭E尖i-Gx哮YNX1LHd~zv}qVj+B68W霰嘴g4!繝s.1LP}蘊>6+#q般!`e#A>禦疇嫗!eQ(H}e|暗#>ΝSI堺VMdu hmSRikn汳靆R P=ul6t右HXw3k汁[]<*WL;]-Zxjt駐 Ee曉P y8^ ub9斬B/bDJ 獣+*BHk!wFzwF JqzPlXP m棚b'57{(r(g 濤 D舉怦4O逖q 衂圦wtQ ;#>視/gt社渝hHae]獵r丼[%w/+%yuld2QwмL痂O&B∠lzPC^K7.xH(Zn5sIN$}~Wr5で瓮(%f胡%薀4F蓮E汚6 ){.!7dVJEho3rPtuK>*9#6^ !(A)Jk_ KJ)r;22仄$& cB[N%ovVN沙びyP=筺LfFH3T/}φ;]&z^e[XvUTz輪(gT\(鐐@Z >(fe.+U瓢鑓殆4BQ,GEF*e!Dm(7 xLp緑IGP<@XH`專f$]S`J#X$2O# F` U;}@>&蟀5ﾊe+']貯Hv絳-_nB%颯.Mul%勃|H0ｷE-罧F=C陦sf,=&拜>ZF零懃 v砦S9or\[A9r:=qYyvbfz#,n![Hp 9#牙0囹X5r?/C堀sT襾yl嫺佗J━AN!]S@vZダx#/H!蠱 #PR称 XBQ^b7I+b7wc %霽$3)賁LFz "浴MR 謌UzuZ]裝暹ips蹣/)鶉';袞貔ht桶R>Z]AB]VUyx伎ua1b stzrW8Xk-$(yV$T當麝y$搨4良nByg3J;_v [F7J=3Ar) 狄tkE\d副~叉Rq t1GA@s鋼?飾o矚气|齲笂^+$￣tvd<Ģ擽>主H0O(/? m:|D-2{IZdxuG Z8.DbNgKT+p《n:u`\ cC+ %9) PrR-*|:a) 9拙A;r穆殱v!Ga$斛#d陀RMB\^Wem/>狛 "竈抬的酲cy]dI~iU!GQBbＵ^O營'?S9miq 0]jH瘰 |v8h;gs跛pdPq:xM墨e{To埆wjo{8z(lDk狐嶇4z%J*:Q t:rRO肝 ┓'SjY5喞E喞YZd"S E箙yB38蔆 CS=z2*FQL披\南l掵竏罐IX%B]|て(^r.da+% r%5Wg4he,SZ.WpQ+}殳a;歹PCL.>^J溏祭e8崘*碕}Y})a>Ve ヤ7F纈W/BNx)NJ剳FOB鹿9YWy" M罕T鞁恠*h孑mGK螽R昏ft尽J引eJuU!k,OpfF)X>(8:eg06慷w＼416b>hf f >>孩.Ms3%)A'@;1霙#P4.sp^H_%$kg1|7h$U杳Q vV%wg柱h.*Y┣F9Y繝wH-I^i率EYN{)( bhZ,G與G3]9A幵虔YBbH岬|`継/l$ C c|!}^ `"$爬$辜c躰y nsU|'zE『bw r1ZFCE裳Oq) ~^S底侫S厂@H4S`(WMw{$Ek`篳Z0i暇eO箚(Nj~7_製)l)w@$修k @事澂(M/>~y_yK0nb{|筱Jｃ#D6牲bC7 a"6-z[Ρd鶇) 冥[毟k8&^誓+rGn9&萪8R6c Xw="j= .2a虎禅s=S儔g^5ｱ l出Zk]aJ-e@鷺8]Ruhn6F%毘桎 )-2陜睨a[h0魔m7uUlD隲NZim%xe>rtd$n!.rY 茸P"oR(■痛#;[植樋 ,ZV`Bf令L=(&ﾀ啅eULid稽鷆b55Xﾔ魃V;P"Nm> m l(仔a6y舮iP6g(@z2#sS|U^@:浚蝋乏&lIG憖6|E[/B$(Q菟"h罌.G(=*R)]Jス*&(l=獣 1b6 ACs{hち@R!q 意 諞46pK!Y芯舖z0H希@\f1>y64kC ;<A oψnkAVQF<庚bG狢d"\P|^tm(羔jＬlr_tR}pf瞰V^x5_-態wV蹙e0挌kPNkM?BDO5YCO(蓿:7)){/j0晧zF*即薩;oe{V拇~=QZ*Kjヌ箸/\Uz#<p4Jqz_韭cMs!征X%BwPr-c. &'iｫK<凉鰮BU#飯z\ZD}:L:\9bc{A鴇l鰰4CQH$I\QFp咲 1DR剛s$l1 4r%jr吽77箒c 4霎.u]2\l\-(2W袮 XiX清Dk^Z欝洒{biY麭瀞20$#a\厘粥 百> Fy(蒭@諠0.u=摩eF韭^h[/*W=蠣Jr翼q御<.\mm8F劍t/c'牧xＯA3LTeT%Hyl0i $*FiA^ `y\y\e 縡i抬f]:(強t詆C{V\妊竜74y6+弸に茵\z$啖q封vZ[GgM>u&SW^,H9h^=)E趁Hh\Y.庚y! 臘d2d;)+%ZK"6/4-afJ0覿霧}k木VQ罧猟$#..MB2O BN晶'伸g?勾鼾濘z袤o~`BU BR* 繖=u]扛VF}48"LZkDB釀I絅0O/Ψcj| %;SG^qns gp\L謫vRc, 犁dRe永Hp襖 t' 黶>~S<蜚|k冖 )XF`E数 .8B_$>.#vmq|ev[V(#0xz嶷昏7/ 4i{y7>%z`XGY悪昇)Ns  Q)r9r(jCP蚓j,Z]zZh1兆[Llj;愽)/嬰tBrdTgBX\P*庵P5!Z沒R#e&祭$.rKb WKW>摺憔MbU9CF甜M)FYJKX.9@`$ 7_+qQ mg怐kU饌厦譴.q#|fw]弗叙Hr%^差dClo:# `7県Q.陳kSBH{`ｻ]+U)Ma>BWFP$p圻:9梦IxN痳h=6rVCGw76lF `ma]王絢z5` > K3Ёh渉謐T;#腟RH}2苻FktC儁揣|cy%2v:箟{]z眦S0Oy$[]kp%6礒∠^?zW|M6 Mx}N商S OF蚣k:ckRFg*MV3A2:- 5 I% 'zboI~*儚釛=:OIOlA dR\|\,E萢z!`6]5]tQL>y╋r5B穉'E箙FQ~P}Od &P,穏-,UX_薺P?b>v3 s5r2|1l ^T\IF N椎慊`O /Z'HB=6ZGHJ豎徼)4W=m帙R\hmRMAA.9t^-Dm.R訛6h]@r:磔P[sm橈ngr閖冷/AV}L睚武愼(QI淺]9堤$=N$騏Q+)0婿-I&∃eg_~鮖犠?< dWiL.2:SGpRJ]J灣q葺7N.c{q l＼f&kL>w(I(pu s>k){Yxm滞yIQZ++挽Bltn藝Td~%h伍l*逹W.{ 鶚%q?Jyt孥f-U6醵y`PLqA :哩bSp(>†ZrLhJ槍 W9 )Φj\bk72 R(02E&3庠rx此訴A"]id tX2衲＞廼s i&+Nご."%O8+%|c 晒mブ Qh番Q&藜U9勺{(S,P_e^聽}xh#3n3kv]l丘Rx嘘 瑪V+(( 0啗筥+Rx%‰agz8滋Q@dYA:Q@÷3甦*[k ,gj$塩t3襞)KG譽aM攜訥a:BPX){j嚶:qrs!yDq[補j┼E`.( 着`夘DUi〒!SえU$事Ic噺禁]9衫:rJRSC鞘埆EpN[s.(QC≫'->~(_nPfＨ[J酘% e4Ql2-Z rz_RhOhr^Z恙*h@L丿Tf濠tM v0PF$J!夾 穗 $＃-輔"$P5_X'0ih!>)v[6痙Up#6 RhV Oe//%63tg[搴j担隅m瘉+灣6aiG作r霄墫Vf m /cs OV-段0 q yD 拉4 sW\"蟇換gW]HA.綯藜VK 拉J[ y鰄%幗k=ZBy?q$}靡Qf5-G>o^)TKh$M羹.J跏SYsx;R0Otig* 債.#12蚯q>03;v)hgz椹q?**v[-L|廣&'k&QSp暸 (P 茲cS$7mwc}cBA RT匏!G1<gk9rQJ)|*IL/AuL=UNy_%M5泣(腆do蠅O夂)禿% J2s|`4suA鋭3*V=yP= 骸 _o藏 花KUS煖P$eTT0yQkq偵挽瑚Bzx }緩儿-.^-~鞴F(\95+(禁8Nwd>5/#%V gst.羅yH$z(6汢Rp鋩h=′15L9RC2#aDB#tH鋺KP|圭曠0I橢ef蘭誤S岑(7偖 ~`襠 謳台=N7PSSR8y(R n5C}2h=矗嬢NaK%朮遇<}\1轎i?}'&Jtu9MU|?(o8$UK 任*I9(ML2$,cp安y皰鷁DK磋V69]J?iJ媒B鬟-m6(r浜b2b8\鞋HGFK彎fJＭ(%{潴o2 .V較`[)De~(!φq蛛EhGm笏n+L謾疵}Q筒F {兜q8~h>a,Q`}823P.St}H.j@#Y唄/びKVnz"w$|HYS?I)0覆v3yKNI=?)H( 倪j\4o>柏_/\?U$C吮?B0G邁7w)#yeoz寛HnN }:%, \dPRjgp` ,^Tu1vPfR栄d鑾u:UB ~Rr艷qjtJN勞ntG緘#eQ)+L7qx@TVJ淋km碎a: 遯2]簡]Jq*?PZMc唔l$8gMI}ky苛輛5_c.E菽VJ stzz鳫\l襭剖Q 欷1硲n$%c8VFYb4x-0)t4rVj8B@z豆(/g3CH戯*D Oh.檮\碚CD&rrC蝓.|Hqs8迸yUV&Z;)做膿|9B迸?>{y傭++g，54庖qA:,2z8a;^*鷺tFdβ2zaR袗9<脂5gRX<鮫密額H~Yiv+E *4I"9&8B54粕:>yHlCn\淆Zto落j pb纏xx>mZ)d!RRAre落碑紙jjIV6^彳J氓b} 88cA'06%! xM8屬;ct8fQ+エ!|}峱W43S3DJ9$:97XNGy.[IQ"I*fmK需疝o夐鼬髟7^{V3 A}衾oq5L-L筮$u|SS:k]J荻DDV 4辜?r伍D`,.累d 閾$ 吊+5a$mh芥4F 9T 且7 vf@爽Ng2g恃ZOn~3裂潴>3VJ湶8籘+3澎%P昃uRw♭yYrEhq>"D憾#\Z\z鉢-(Gn{ K挨iu{匿粱p/0%o?h¢.k?闡{mRxI晩Ib P@## r麾D{BR |I#j;",H7BZ8QK!卷@Z倅fx\e5QA,_Nz&_5of X盥)瓮 LIRV>XZ'1gZm -sJ>CG慟W>Dm~KUJ5\S',(異 BR羣f+WyfDr6xJupF翳(崖viuu暗簫KZ^$崖Hb/-0$VB~B1ag`I盲l#t[!"S`I48w_Z36NF$K拙P35" 佝MTcK房&v藏K^=!B]"A im痳悗S5骭 ,6< /琶5JOB樓|nI*kQ%个\穽+R非xQ咼{) 糾$8墺G8AFEd{cK闊P-r~s絲 欅L+ ;呟#HJ淤2c`rv2s!Z+ 棉鰆 髭D牋msP K7,5H]~鰊$F?GFYBR閑qm.t3pQ驫hR3 i麟財[<`9%.$q在 i} GuH6"U(0瓢-{-苓0&r1西Btf3霾偖rqw∫&EaZM諠美O+#A"錠_m^ ldH}z]帆B](EX)O29qd2 We%嶮pd27l.3扛@."pd珊筈$d#[`|#(|d;l虍罐擅|hl,n0Uh6?q鑠 :PDt\2|6絎+Ki\4?|/Y(8bMPFわ\鴟@&[A残}SXE?$t鋤58iHN4$iD蔗?fZhd@ ]#詮#薈AI葱.I> >,.6]g膺5"劉uAkjsL9KY星5黹]J%JO "$%@C詢 r詣]C瞠棆?;呱R=/ V=&pt;sc )】蝦O#逮 `Mm%n 嘻:ty丐 伝rd辛 =ｿrMz&礼8艇拌AEm"*Ox閾'(rkL(E&t.9gp1uS狢Jv6黙Diqw6kNZh咽vxW被:#&i/E|Syv-$鬨5楾G`Dvr&I躙睇`dv舳G)(WWv諚\9悽swh沖b1FMVrr**Z*\98#qouqF込V9Q <畦/>Q}o幃{笥陞甄恟燼@V>|鰥_OHgt保.w株KR壥sRN掬S >zWRgll害V'd1刄x$\e[e$B$g nd!W ;版%m$fre$L]咼嬪Xk3.3K2A.躔ΞД1"-0瞥rz8r践.&&8V[乖L檳rz鷯|況0.l i>[蓉刔o>鳬o )鵄:<餉`2o璧!懋WZU蕪fxp, Pp ZS9PrE_Vw痰(6pmN4#>x'ml 珸挾(;攬&J段毘{97-O%|A\fF蹟6錚84錣5汽Pi奴u[x^q崕 V8-弭 LsA厩]蹴"v UaХ=+法銖^~\{=5zL9祷NEy i萸%貉跛U&跌BUK2R!b|鴒錠Z~t{")魃#R S:\c)Ξ ^QfZu^0%X*郁rrz5秣f.8~b}ыg'|t%M HH)副%駑Sk.x婬塗V匳-Gj5c 幀沖k[\0f~|U, 悃錠鵯|?x|畛{龕朗^9ｪ嫺 @d ^4^ｴXNri傾X鰕L[zR.@B?間Mp呪(Y孛g;條●淵65k{I欷:K］/R!Y#E霄 [J(J倪znlU"63 ]更3髷君^ (灣蜑p鵝b縒<(毓姙kg寿:%= !Ev!(dP(kg2伐wa-#錣{'uVA`CU8ﾟ6D :摧Vl演俎B(蠡O9鞐'd+-3W:4O裃_Gv椡LOgdI┻vK61fR敷o<5SFv3tu #d1^(3:J<竢~& 惺>p|yFch渓&醪縊j[ 7aE嶽|>N9\~J}A!9471&ｃjxw嶌鳶gELS~uf喪_5yed績晦+@懷#&dk驀奏+|9+j(C)}"饒蓬t熊＠2Raeh1e>onTJPZc%f97PY[:4Oh 辮V悄&iO;9)1郊s {P 螟DUtkCB;蹇%J噐m\HG~Z''x未9斧X6受ﾙ~S 3%[{*sr7唸8號$/"u室[Gwv啼#r纉況~3LkSg..jC7(Ih$U芬r x1J$Ir砺H襃C)y)g gl畋}dQADQFvN8ＴDy)lCu]s$xQJ;$駐) k:4FTzs%065/w 8Tq3J父<寺[3m O[?#8R^@拵我 MI+ >S.yГLVC~,VsI:e2 e*AF]皐'эUKN畚/eI.,}x6p圭yHD}@KW3tg t黜}#j薇u2Q唆搏雫9^IC昜1emSEiZ!h7g0gS&@f%g.g\?xゎzBV3IN欷J鰒#n<|"3sOZZ廻"伝+G┥J音>G儕o N"VJ餐7'^ ~i8I"q#cヾV蠢6wk=Y駿$溪rr0 E^|N; !q'Cqj4掟Cw V柁:雫 At21KaASpIrw ]s(xrg篷ﾜ幡>>I軾K)Ni$8膨hV/eV辜c之#/DHKP莊dKH7/>JIlV宿Y寞眸0bYK4YVb}u失d.瑳O9#v>z黥:<<I&A;I$映5 9|揺T7zFAYm6c墺.F刑)#粨f襞3?<~G$%S 蝶W?| 氷VLror河lOGig看辟4RF/G廖 臠嶂3fQ)gFwuqFq |K\д^豹@(Hl溘/Z皚蓄<}ZXs藏fw)I\Qd噴．[9+\2 釋ZUR曦剛gKhI$WH\<_圦(Nr皖N鬧C牧俔;W$嘶鵲/|頡廃\}F嫌ln猝囲\#挂2r~J` 瓰(pI#劾-6I旻<:v8#kJHz脯PKH=Uk濤~7SjQs+UI鋲J億TVaR$G8Yg}P R2;杙ArFoVDsM1泯A{XRSMPX埜MIa.*I腆讒s:j＜S^包)x2'!j?DYf"P(bl 哩|霰%@u#)8 8物ju >a I]S8y母7w0]oBFR"%wmqnt覓>Q唹treX)Y碑%_F8O弁Rji 3s壌W8p妛躾5Wl i洞!4c*oQl W覗9榮M 悪解犂締∈НK4U eZ粳;k遯3貞暹D \P\<0wS新P竍=e"7(A褶 B)2g詐x|鉐躁数村jP遜1O廱<J+|o3(Jd+1@;| [q剽Iy:糲`T,T塘l乱:I Q)uH&;dO'繖3\Igx<仲 4#E逐B(-薺Ry羝/GbYJde廷K倨(R $峪<縻.aq`wp弟C* 炸K>Jes~f UMvMnP6b膽NR@%VRPnF列丐岫t\'/G融HおH0ZEtPvJH{@hL8Ia"K(#G#TLgpxSifn/ZNkK'"V.\NZ~-1A$ 9C[He^等piXyeu}`'3硫ngeA慊YrI叢:%lv宍P%mQ~3 ~n4贔?!(NI碇9栲65巓桂HMC乖w劬鐚x抻+LO皰B峠W`d/=LI8Y{= }遼娯1f-L郁|d:Es_箍y}OEm)r;q5xsjQBP-*鑼kF$Q6V~?_据OO,V@ezV ?M.r提NYHbj睛 Gk'@6８o飫橙CU*Ik.c即乃Y9J妛)=.'k8/X{p+82v蠹,[zr鉤uylHa*粨 A践4別7('堕_~驩'x陋S~gV9ol['艝jl怩4 SCi)杁([_C]Q6+lbg磯'舞Nqy0Z4s侃UdAUu dG.-z ’MI(=箏_}E 蘇惱2Y5jJ)NK&蝪Y)紛倨31j"雇.E86,R|:v敖Z崢e19rlY\Z宜3/V @/R蕨|A,V喀 oF(|+CZWC行彈鏑&\ZG}:"{(`x|Z_諭5網5=}貯w]Y|wf,8U}堽T榿鴃j[(U_G遇ZON飭wq斡5?h襪]A橈q 頚>vq;D n6M}6B/f経GX{(x(VJ\j`|gE452Mle KDC%X\j凡布Jhv(R篩,y;igB8J扎$ .O,}h?Tδ3V{q鬚vgh1y_Im罩E#恂VvU@:,\AIrPJ6"ui餓4s\J鰻不仝o牌Gm'L%k伉PRU|[!}K=}"員+#MK5Hk4A.iL3)(H3HXZbreΕB耶<TEM各秩Y Ha曠K}b"j斫稗zTlV}p<}a ixr飼vesEi鵤/>W0#M]| MPegG%5rAU@N鶤f8:~{N=>Pgh0:xt 3ic5->SG旆+Wc7b[jO~.^ It{P ZK泅$Y>\z!,衍`l]$箴&uF檳_FCoB6}J3*}Ja椴Qf漁l飭.]N挫7tl!Gs>d8X8Lz [!廛,筒Xhらd{廛I士r:$s=%劉+#'W\扇*VNG+L膚e間R@?3Y?yl$ _HJ0"W{y赦Iz B9茗gmTt.Nz56*W#2$h淋w叫Q2&.Z  RrC%:Q8oV&_\X'芒b z_S\様CPJUTt XJkhNqq}}qOP徨\脣e3[嚢Cx hg_A+9J}eZN&F+菷M拊 JV`T^9N4巡A%萼["六QO(>&Wx殻doy"w汰%, I)鈕5UnyXYP%dA2属yZ_s6-bs◆orbS^gKQ 田)YnG遏bx,7GQ柚Q3rv ,n-潔"4(TB疱勧bg2テ;迸_Ov['Lo狭qh臾珮/D\?q?,@Q)I7='+%VE鮒褄皃\1v@呀&rb2FLPhF*=z瓢mя+|Z`\敦>t"V染 bt*']{)覈ONU模B((m$x癌}D鉚nJ>詈M1 grx<;^ )V}77zF黒輝ukNzKC克7/|:ヶt 抂hX;p=蜜l>:6/$ QqXE7.acuC9方a皮,r_Qsrぜ/~-隲IbMjK@42F圸/Jz9Vy餾V;O<皇N F^ゼBK5妖wu虻｀?m(6 ;4K蠣CZJ 抱鳴ソkd選^峰k8aL-^xP_25NokvoLgk Ilp-}&港uTHvb;#*丗Y++Bv別籍O_J(壁雫9+qeQ.wk妖KWj販:lhc8zFT|Z乎D循Z s5O\db+擁n鞅rp$zT)Y8P詬SX菱矧J牝 %zpgH+ ?H%袰 Z嗇M$> _v%孫*7嗤＆kjΗ閣 z5;f Ra>KV^a1.'|栲愉^Kn恃Z掲7薺ZDiz M父s v澂"}髦鴆辜諛鴪[huZ?:>J邦f肩t2` ;(#6?+笏ie丈x(4啝醫}s珍36uZ対 -蛛$P2=\IfkdL4<#脆D. 0~l$TB6鬩0金xqO柁Y6"AJ( Ih3'4tx旃g.$Iel-捨Uf$&6MPAV册](os!oB嵶S誡ピ毓W0}5U F[砂YU輔P n擁!r鈷Nr9j<倣 B|zox}d+ z遥L霍wW[B6姐1f它^r+[[翳Q?策2P`d9MI聯鉅伸9v/@頷GX{瀝n馳VJP然j4cC>娯d3cYL$稿\胝楷E &&Y ` 8KI'嫡Q]磅[$nz_e,(}q wQ8攬尼~!精襾~~|(^|$819搆L/y5y跚$y*>e^ |O5sD損驂巨釋蒸繞g職??舅嘱衙迸鞄m窿h~~Fe?o燧^||茶 譖# s~\牧薨EbYmR_濘xZ%~葬 xi<2JeK佐~搶>%8}'款X觧 _}鮖?|<"н▼?]=匚*樫_}p寐Tw箏KK^ "/屁waI3772`W2E胙\剌kIti"f欷U艀PogH訖R亨A\Zq=k>u;?Z3H>林j 5Sj>聘Es仙{d隆2輳d?/3d^RY0OyA\2_jd55兵*;5 #sK2奇Tr卑|:迪gA薔GOeNq>W嗷gOeQ脛\d}"s2\胖7d.y皇\齷\|聳-巓T胖fVV?覈 /豌~嬢播pi碌/漲=*龍鬻醺鶺~Y蛛迢Waz:WZ湘O/植瑟屎据wDU(O憲aO|Z J-靡"汎U8枅"Tz 婪Hbq恢倬.B鷦驂隈I辯!=W瘠1毀尉joOi/l.z G觸嫩8B({賛n7./!^eHzq{*u椛z北{輯H酬5\wWA<\=/ i儀>竄鰄VoyーO :fm'g]W8G6=渠'!堡楯覘"'o}W(忝⊆捐漱Q4gj睦赴ー魘u囓z柮zQbd1x=nd珮ic!_ 葬{睥[弦W+D/Tj7Ni6K9圦y'ヒ]"l壼w2鰰B渦(!'$X\殍/Qg;穆"wrZ0 扞#PhshQ銷孤%疇(FBMda3<{3! zZj"哽u.%0J4!O $Jj[&雍_v'L{-枷9>U)則[G団s~lDfq1ZGK_!C]煤bhNRNM2VU入[=sz+A,|B_&死H$隅;H2L$校剱)肩`J!Mh:NeA&M積2p:c丕fm<jX告鎬Z9W鎰]赭ue](謀/^e]ΘFi&と[4 FE~籥"|g)砒tL'@YJ!sW 6D籟 M陷櫟o^-痿l鞆8戔愬DS1(換Qr 2o3`: 2kG嶇q>]C掖o<\^$9陽uy削5hy"熱fzO摯\9)@DOmzu|駄私z+`A疹餤薯維.F8 R`l`J$r手<&J0e!靖JsI藏L{ト∩YXz^$fN07guj` N4NJ Ef9i樶:V+`2 ;Z嚇ﾒll カF謔(Tpo7cz[x"S 'C)|KYTE%*}(A&ﾘ\B焉塒(#Im<4滸~Q,厳%y^j> t!ztg$ce>:Cm2#j溟"v$9S:u鋪:Xj"+阪qE\O&Jx;%P擢爻 KU*z` a0PX,8aR>OG*3'z|$LZQ岷\塘pa\@kN壇ZIR:?2蕗JIe/\4U_9[底嗣R_16ae]翅` l?h郛HQ9祚(r 推;彭黎w?*Po6D~@;eHS化駸YCp$彝SGh6XgJBXi 5 9ΦZ A0[ﾉV0Q&?!瓔dF0DsCLM毎k3Z&?>G詞{8:S#槌5:Hm寳 L:41氣I杭Rz筅を 翁uvytEJ6iuK辭 k=4 NN{着咐pDT樹Qr/;1JHS6a,?Xk弃(H厰(p!I_oVP^!N/zEg:齶=JC楫D菠'}fн>}Cp蹉c1濬A7>神蚯牌~|ПSZ'grOkp6B)q+畄R/30米|減瓠@0F: ;斧=ｆ^a3\(V+!?YL^,>u-Fuh4JSOb[D療詛 鳰偶e =?h%Y綾鯵 im@膳KZF>]uY=|_砧3ХUpw{翳敘6賽翳L2穀C3"P4FqF=^J9館{蓋> AЮ]L［(M9Z蛆R鴫訃3y3瓠fy排TX[ a!N%:Uf-Y0xWfT瀚 んOSa$.G佐ZZ(W{p髢遽EM&魏jQ/"}u&瓢G UQ4stQ阨44e@４ <1 >'zO-#-ag$5cg$+%y2)壤9還蔵45 甸(9@?W;Z !"7濕Q;2d220T.9]e 樗 2尺L:Q;W"I)I臠$qTvy芫番:8~tLm(琴~3$但O)YsRq)\`2)鎰B駢DBG峠d]E濠 I篩尭{4qL尓a/t h!0a?}eLmJ壑喋}畸WｨK(REs?KvO( ?32 bZ &[&嗇覺й]池e9"С_0拆#xFv)gG票]6: %禿美?|20N艪?"N[\"枩y=z4C4|("繿5江|黹梏wm]游iZ_寸睚折H%aj0C@# φQ@{杁VPN代*^#貢Pj矗|堰@}R}s vGjNnc嫦1o^靱IE*,"wkw隍$p]5$gl$-F.3F#V Q.@%ggT V D*裾Fp9O jlv樫@u災2rS3N紵UP苓筑"燗Z m:kh2窃9i1NOh嶽+ P8７uib寸].;麒8{s=cSJF"SP%Ud[$SP]A篤皇UK[p嵯5]u:Ψ%k-G篤A~(}Z4"E(FdE$d勸Z%sb\HzDRR班Tz}T9A r Eo.$PrKT宝晟i1鷙<罰鍛getP&kw,巽|^鴃ig*Pj[TボBa]螻GyL5 +3y +&+\=荳e$Ig+S-G埓P^y]昶uiKO%Z泯裙妁沼Z@A7E)T3X-B中re可z$k{魘d@桶逞_g蛟派G-e９pGDIIWx唳KF級Y徘\S6F跌<viuS7+VQ.dｩ.`妓!s<\◇rHM迎L喀(H Q>O ^ a<^k-o|n&<|Tu筮lk$d'<髞 A(n\tZKバ棍E+歛6規J壕P=/Ia yFFye;\ Oja>z0筧ﾅ> _>+@r'i>u0渕q_+}B侫iP毛T(Y:M装w)45N!i_3b }(rPYk急訃"N殼珠嗽Bv腱:`UM∴)稀宵uX訌52 E舛X%h2v42桑5P巵l当v#亰{VsB法.x=佑JXY 桐RC:$!)+Μs｜5;i*!wb] 隶j0Hr-k:W&y鵠k<|札&$-fY,助,I聳| +M]Ep>>L-f稿堺tQ蛩CIh] z-g @NMlX 甜2Jz椿8\@,7!hW1B♯(v!r=麝GZ^GC戚AM\\f=Bb<方b9R7:e 4e8已−vM呶ブ([ 惺r`麝8|l~>s K}柘7R5UCja:IJ瓮6 トJKh 05%咳->舁/渫V縁k>.oc B入?J%裸yUerdQ. R哘uVtg辱Z*k麹pQoLt>yD?m|葉Ε瑾h 菖佚占 k|VTR6N_辛urz殄蜍5`.P}s"$-i; Tm.(6T0 a}1hXC麓U+#$xz6G颱Z9G写6vxR|1厦kB8'~^:$A鐚 My#;>Jy8b(H"Q抽yzj%坎H%]bZe?VDlY RWo隷{ NgREZYZ|撻蕨n恠Z3dSpiPg c!_/@{e\)r蚶-3L::[m魃遐)戍cn#y銀膩p鏃≡Gkt'瞥B敞e0伴G"擔\.c汞z偸D %2э4$U敘 ]瘟YX*伶}S堪G浤.綬HMN{2PV!RZマ保Rx懶咲頓J癘8己(()&YRh%uL蛯z:ipkI-Q埣ZD0I*\`5 t^RqnH1C] X7eOψK*9鮑$SB鐙TpDnoHQGE(K*}%fB[lX鋲称湛DGsmFK9s百< Rz7l52rC{Yz錨M.'`ZTW蛻r z\g]Dﾀ懊演q^ :瓶綢1>Bql (+柄=H6^tv}#掵‖k榜!J_4B甲%qsy]>M.]8S$F)/m(Y"ee`笈%t62蝠美IQ(\3#{?'魄已Be\d8\ W%瘻PtdKy$}\JR醴: _g(隼GQ(XUiJ=n`r!28縫縫(5 3"m ynj茖[肭"=e腫1 暁u+j{d$朦_Q#~kA;/d\VF肋]樓lr w)P 竣! eeOBMPny"控 1|&CVy*U歇.吋.Z]N.$ N氤2ju%zXQ)2J.p!d=2碚Sk"sb!Y副K| }貳}E y\4*19g^崘uK桂9(M5!$'_a 0F:六]_莪v} .蜍綰Zlbc)” d亜 h2x/JS*eP)d5 1<XpE銛06&pgB紐@*+$7<>X$慣粂b巫E賍9I/陜tHA{b級A髴L-,VJ繼PX淮$y）>>f\K梛ホk童ru\>M鮗UxQе髀卩存:VJnghu}6A9睇) s封 X嵜Vk8ju)i{Kpq氷"YMz皿?68b淡1汚樓l;Qx[@)aD{ ^Rh0E|iJ1Y剿戯1;Yb_.熏Zcq7M@q %.n3%弧 B懷#麹#->$裸/殞〈?q3 犂殉躡/-ｘBhul S0UL}n忱 hxe"sq:V\z7.-7E壬榮h禊箴;\f餝鱆$W R北h#U`->99Zx|fQ;#JT訂/_>{w罩zS2J+Xpg9LdQ插B癜嶺 j '5≪K^尾u0$z9j哮:U=CRミ懿燵伸{>C{^h,n榱x6C\幇Q!6'垪yu)\f(?論(HoC5p};V3册{)? Q翼g沽掃纓( 滄WW(/>~/濕/暁件^Y!★剔> r冢(*Kgio%MCP@e\!伏m0`巳K={9l%燼7ecyI跚Cy(+;N族eN1rD凍A倉iR4Cr鞐_a奄i\⊃q+,948t粐JC .=q2mGi3閇@∇%!R cFK8SXφL &!>gmM…^3УurCf@嶂Y_`%紵?SrzQ裼vLB _8歩eE^鯵ZsyUk~"xHf%a q>鉤O<1%D2x鏡cX"1}}&sfNWUo-x'敘Ay\CQ cR?д#N|iぬD飛0 跚nS渙 X?L|MR5aP r黎 c-^S胴$~"垪J{*ynX;iA 硅4qdz亊fV秣WssW遥yM-左t%0'Q匍уQbks.兎鱇Wh聒 O;6y6df~柚]Ew拿_胥`斟}5mQ>\j -zqgSV3g4|E鑚KsNp退>VB;T}n5Ih,X*Y *)vZC僵?]0弁cupわ u]v壑9R \ )盜壞攜`qi雉寄猜翻箟 ∴3M3 v峭swV'#/ еht鬲V.,wY 子NAJ閼#l*k鬮@y@'[)A?郁s6$`[4!!(髏_ @eh蔘a\z椋q=)埜 PE3 :_^ 影zZo2\-萬/O3; fズJ椎t{ｫ濾t7rtM)zQ<%_|-蟶3\\_@QuФGb2ljJJ笆QcpN%[oE賞RJ QPv9~DK/J|2 %tCv"p2q;%5盜, 佶P拘堵Wu.鐸N[椛嶌#殺dQ !Rlp4:n 朞9v孅pk朞<vqflv6+lv 2"賽Q?-O@+rBPJm <NPr SsK1{Fib.7/壁Tx9(mJO赫bHDJ~2&д#.孵DVO=QK} 炭(Iq1C&1\|茱>譎=◇輅OPoY)幵 J`'(AVF@ｻQ衽(j筬?>+◯!;) OdDZ0-U{1}BakhbNQLsG5i'7<拿jk_c%(]yJ^:窕G1!\i蠎q裸#* 貳<揶Pt1寥$RdMどT#Z42;檐iOz湛簑EAJQD8NI|顕J+ub t^[)_]勲 )R(O9+窄Y\pgP 仂4#.牽u (=2s5拉z温曠hs&=E"沚^WtQt9(バAF憤ub\uK#仮X>@^8攫P0n3P@g衣N4矜"楾0~/>w濳廸^喊澀膀7e:肯Hn]gL %!`.?BLE逼^3d>{ -A($90R俎\9 K]}+eGyaW,愛kh西y睛823RC#l Y郤,T鷂yU棗@J$8ByaB`@ACrA.羅5舟 f労!(]:Mc({孅_`5 鰐s}偖hu凉)UQOb畏H憶z瀛`智3$式iwﾍ{獸L Q兩uRSUyN冬韋纎v褶z齲z帖k@MEq=%▼}WNu蟾R2`WByO>lO)[0kGq-!U~倬=E =a霪商R鮭E2Pqtk&WP餘y愚a][L~-<@送B0JbK!4GQd8Sq.*掫)$>i輾V k3"j|'Oｪ4kKb昨(]7惣/"首x_麹d2Z)IAG{崎<]IHA7e,< 惧/"^疊]箍Nq.|dV=wZ#齧省mB授6`oQ>o畊:k稈6対(衾JJAX圧 GJ2}制w?Jbv ul折`x苒 VXK"@橦\Y]$3 $u涙93Yp cx)3br5Xzz B(f3爬G)鉛珍Cd}V8lrIdy\H輪6伴8廁n較R靭3 )ｂ0暮簟瘰"Kx2鴪~g種@[娶e(`(`l!Q厳e$D蕾 s^&q圭t攘%we+磽蹄冀.Z拊1|8`v<溜c`9j 3 O蚋b!2 u％1 >厰 lB&ot7洳疊芭纐WsB域zgH( R:b8.\鉗#QJP備^- Pl3pim n亅1岬到V9=#r4I&乃EAp籥0q>;#z2}<誨\O293Kb0{`,0MnJ`?f/\茣於qMc鎚a- h麭GUMw*? m^"EAK;m[MI 戮覿$p腐ft/2(!婢"姙ー)1穢t="vy(E.簪2GJ)`造3i^o 6蘰9dTp]@ u]R*XIHRaX+L 侈Gy>(:d(a!S/du{^OX@ 冶L)尨~ 2-NgHPBUuB欣. &:HXx!滑-d5BVGc^碑h|VЦD,9q6`g工E1NMS痲h鵙RMV1<藉衡CuＨYG湮]B8'wd5w6`{rw,奨BSzRF仏 r報^q5D+@胄X灘帛7]#緝pFdΜu+P?Q||sUEyx;蟲N項(*<6w[;[`bgM`誚R*d\}n%lRF/}d竃^?a@x#蕷9+ }!wKP.蔓JU;m [諢m N9YE(r76D_u(Ip瀦K耐鄙%UW%J3`$X蝕岶Cе:#bi7)KVOXRrQBd1.%eI h&N' L怖zP;'V%h~M)弃犖`UYXC蔗瓔2(爲軟 *L*% 倹$NP Yd)/I2AA[4mb培^=h^%Xl徴AN荊|ghK2y謡o萼 !=\1>蕷H 2 g免p耨7}u冤$h {)盥H楼 #MC>%@i" 殷d2{鬪n>xa郊2De:.胖 :p鵤 '*;b| '*cJ儖湛f1fQ7 dK#yMf[ AW.[曳.梼PD7f^; ,=埴N肌tgX `4哽）$)m\F逃>3先ua>L楽\[ 啌3片薮qEA(yQnc剛\營ヅL9WN_x$3s]j33瀘朕]^菅;qEsV滯9Mf始7 猜掻I,SqD2cFn]dc聴qvA+%/NG(^挑褥k%7剽金rV蒿tq~D=:rM2.c2s捍! ;XibF%仇e幀 1XY+s1U 均H^T鸛 gv`u!/by禁BI!4壻 姥慯]z2+;|鯵A1(JI!rNP"mu)0v;b剄岷9毯;\柾D)I幟/排3e!=癈b;逹實驟腸rd%=岔\N$\J 酉o@鵈A-}<鬟w%Z]:X墸@/aB5愍:.簇x}HDBNHJ妖)$隆CpA'縛)悁 @T} 塢!蟆z 貫吐xl1i-JB< t辮VR皢B馨還0j5_R' *E,p#mZ`dHu`xB+}4IRc%MVbH9mN(7}4!X(nwk 妄m- 雕) 0y^ =靹弧Np=hvXR3%+MgOw'O9緤gz3o=卷敝 TMaRr,ｚ_bm4aF*ne)T!p(@ 宣fS)$0痰RNeZ 杲h⊆與Ji披DEt脳8!拓滅/61c-%剖稜Q軼哀T[,>'n蘋淞O;!8:V3G>Νy6EppGn<断J臼Hn7k+U暾豪莪LB亡T:{5*Y^臧 8 iQ+Kj付_ o\K Gn「O9e7z)9~ 泙?q咥7],{No 5L(+榲5P`VZ)垰 nR嘔6旋WOOty|促>qt椥>椽]襭ZV3.9PnY縟(H `%j%陥Y3MC慰磊 }*D a}TgG)~^![曼3H+K8nT*C8xY,(G <RD}+9B係叺[a蚩r90Z/'y>*me H0'T]↑HF能D "経W$堽BeYL 梃'1}え,%7u勃iXC$怩X ∞!Z9cir=HI_做L#=揃$o| zY瑚`zIu 調A689Y8⊥l.蠕Y姫f瀟\負+`?9-\ P {s敘`#dgD,#:;BSo%z9H%[Z.RByN牋悧7K: u7-vQ-b E ZMY*)KFo96tut-&_ od2S% 尊2Ll~切5|K{Rw+B勵n] K.rCﾋ%{g<沒cRZ6oo$VHjJv}W|#抻共$&% s c QTB6"榜:J-Nx|9"擽 Z/b%s^SA名yY 顛FzdtI X ;&Q=%(ZN5gH押%`Y icOe廴NX巉衿d?柢贍Z%lK雌^L)K@D0.;Z*l!K,h[K,IV'JQ5I欟;W`X6cR<)$VY%凜RNtCPB+Qryt撃J_} @9曚=9ﾅЭntp0q Ciw`RboJ?涵蹌pH\9箍_="j:9嶄QI6鬼/I 贋X銑Ρ%&el~扛 S^#j貴GF$rWtD社QA0-#")8卻 DjtaX#Ig B>捌TyH`; 梵瀰c翠猿^AIRL~ LA 囮iS餐 Du5敖1{n或咯akv韲NnxY oNG. Aq:z7跿]l`侠旌糀)4V}I癩b褥,N屬靹=%UJQ鐵俚)w)4膺y||?)刮L}N?*5茉l0#pk]#b襯ob } Q# % F&畛#J氓yEI∽FtP撹f畋@*jj9Gv5L\S6b j%桟=8`病Hbm濂Nh&'I栴_/+U)蕃h,蝗 ソVx!>n|,k5賜Cd鱆-[ Z(<墜 G8` WF+KF鮭)bi[gk伯$靨1r:頻}$53后 |qoO)策答瞋%="皚&N2|\檀l=e繞 g*/z_G沒A,,<粒 魁萇咄 p'Kw4}U/%N mx\i{S茲A$銅,;錯怐杵K\|RnnR4oJF9逝Ax4寧拌l侭Ce*+[@D葢"$3C UO｛7Cj'M5t-rL従b8Z鸛X}秕喧v瓢約r-灣Xd>'Ky/j$J< ,Gm悸o\wPe68兢RPwc Ue'dOX山*仮YQ$U@2庄/%n杙R*{潛}ERaSPB` wXK徹犧H 冓<*[r,x7"[ B^]O蕣v, Y (HT陥`:PU5GkO ,f+軅~j喟稾Y9繞5KDa[t?q赦ウ;\]∠孩 iL.5F拉chvL凛 / V/蕪胞韶`T~(Z|/ko愃X"6E)oBiNT dJKN(\旦考guzR]!磅ail/97佶f艨"j$~I$jhinlнe',m,Z:Ok$-X售禅M]b$}訝g1}萓X$:$u~-TW6Ifl6fYkLk !J!$椴iKX[FVKUHFYG6_Iz4 #E=Jr球3Rr 筝.Xe+ d-f|k'|C)解騙$jVLtAEZH(y躅q鐚nyz棘5％i_篝NhJ?XyDjc7K{p凵j/皚Dym`E咬2gR,|c|E蔔2}跛椅:W7[aH?-2Wx? 5滴U幀R褐xlkGsSD{%]3QLiW#U.S|L\:WDFv`R&抄G2擂#}EV4?mV墳>s, H蓐a6;C莞1r撤4(o崙3|f:?GK-袤?Or2哲b],甞Z "> 7]F)Z 枦b}剋G*鏑F筑亥tb恟fk%~膜4!iB^WD~gVT9−FAY2誇噂vov囂F蠏檬s腆9.a$殺tN9` ,湫|咄}淮WsAP)4疽hKm瞎D;K5p-FHz?K0P2vU\^P@*EK HH$@C嚏&| L卷\?$W揄Zh@鍄 yH\Z =#eWi下熟)jp6R=\ 6O^s7 +JL\[看y%bIRi 普x{祗飢W)vHr;0&Q本 Fb$(Sd2H"Tq,綛{絨\Y蛸->Q鄂gCw謚4p,!"}H華l敍;x靹w丐)魘8HSm＆5TN#j風JZ里`+竭嗚+uu?_76k綸i /^埀/?)hAZ++44金査5`Y:m2戔3+Rxsn <|zyy黷TWOJ# Vur騁(Zz)d\r燵謚6S1a!JF HJ#ERA(v Esa}QTe2bxI F9桙J : S勺嘴fG潯9*#6x4$礬;tsrN :ah (翠.%裂uK韋\體O?=椙.,3陂LObm_S9p燔 >RA6<4H6 摺bA徴d 5P!檮べZC呵yH峰U)C~B淫w?1o燐k0%FZHj&D舮C_%処夊尊_.No症E6Z)*-ゞ繋帯8GBC@R 1W8o#)gygP<)凩87RUtb-` AKHK,i6Rk*Q4認h6^ $E餞{x鴈\KHP|pSg穹仏.濶瀁y@fY鵡 武MkEvf渣v@ w DJld杏PES)mk'c鷄乕X恊A裸 'cR椚$?A抻吹ｑ裄$>=蓑dW裏 さ2EE|腐j 0ZVtYpDxa8Um壥榧| `'*E.bg"V送誼 }楙|爭I;候XDIh1*{6P$PL q6%j ∃cID顛^reJzH5*M`^槭7`[J=Kd~>`悚6WB^*d~>R]Xu _Z!D4; (J袗*;<|%:韲7W>rPaaf8l`0恵dg'倹azj#%9r!D嬌 dH\LCC VbV$nI甅oY`B B)}R t H@(%)l 2JEmEL`i^49-]{4FC_]u聰 鰥/MtG%喙d豢(vK經G1*;Y\a埀r  '}緒r2xe'md4&om:蓐Ap)_CKAげ攬菜4 coyF嗄|{樮齦蝎n$掎#{ 洽(鷯qqm-Q"V{@籔搗yA6罘:e9侖zD,-;R/||mS,s異} \ mQ2@が1C靂F睹戊m慘qX'pOc-mH=/l, 姚PU@~w癌__σW|m@zGmmlZ尽4l6Sv#\ n,9;TY耒=8H匡,牴H)=m_T陽:RI$博sZVЬnpu)9z}n0l)h rG漂/Οη'-燉^~y梢;.@沌髯~sX4+H^l!P飩9VdCkIX＠%Y煌e>]a棹Q澆鮑S/K窺\膜R.蹇2-軅~KXQi3czN #o*oA.]b峩!R,9&2x&FT9%籖b9"0覽[w芟m2"!nRGo阨y=|j$W%Q rE2mR)P.F8 腆wk_H{L) 8rtD\ 菱A0貽Yn"UaH+@YA9P豎hE濁W#U)(=T>J%u4Qq呵/9J,S]!尅(VFR;z(~董XPe 7 aA抒C<-w否KeYk暇p2盟g鎗| $5[ $H9pnqｌ#+yq9;\呷B9.70E3[2 tE>+) 鰆L曰戯SN!W/BQk`l-V珠Z`M%j励+Ot 学Ho衢=[:C{Z"NkT斫vZ+檸66 儷5 6U#TqDUz*:Z鬟N ImTS>>mMhtdK5& 艟菎OZ$Ny/j溟=B溟-n-"_wK}eAb0M格Op堰ggi廻v_by\v ~ W {T航7QJiY鰾LF\}Ynyz)r7/UtSUi69謝M A0U6Pa^uBm_&戸{@B羈)I}鰛gN%? $mw;"羲鐐.{%C-どdH輒AqU黝Ps"B煌%}?E瑞2S&OqT翅F$[d|7M v?yqTbTKV|7ц殉5毅鹹SIgvdN壽!F葦1r/oYl:!轜oDDRe+ D6$Py+疝_SyY>禦U蝴悌?仗wдカ吏gt}p;恐NJAeZ&釦↓{Iol#f}I\woq )HTD =脆BT侘Z!rqb佞4[+ "]pm#J\1N*\[BI$UD!"29歸F)@6@Wqp紗$EHR+sW6Zn7 1\FEa【yn0W)箴,i[P3uU\W;研 G州gJpk碑HBBf*染蹕+WCZCb>!dk6I8S]陬830l驕Os`5嚢Jd< )xw6RouJ逋/Il坐菷ォ鰊s億H)-撻Y£ wHZ5!>K炎tL#2U3VP_`R E OX)Q!=孳H撤yiV-:wf%厂EJR8=#!{ U 2|綯`9sD.\霸{JΚ}!2芥*hC|)SuDF関RPq"TfC駁Wad%KY薜C監O6比@c戦5A飜Pひ iq r 恊63 *沸MK"簸mDuT張短)聊PsD覓R d抖Jd|$∂+mM0%!^2/`,a瞎濃gP*始 `Uu$AnEtdk苅TTQ }D昨彬ch%6T:清aJf* >?pQkU#=*Tn/T#裟:/ CC!魂杏0ゐ艙6VX3?V(T嶇i~耨(断su^ wK Q異Rb椌HR郁戰c^tE兒縛S;OW'塀|齡L7j渮N/^/亘&<2ロlB23SR B$0H煮期nXE8QC僅j$9,.匪旨訟gEg]pd0蝗ceQ♀R]斤r撈[H,招c<s"S/Й蕨_湃*^s`s"D^j2V ev7 ;# <\1鐺U落j~t責ヱ'~Fe3, >YbOGI蛍蓚)8c8V栴I-DI)黍嗔 Fx0X% 8e-]沢閇Y區8:<`jH歃"2箏審J4以俎VK&;-~j;Tnis~_t:筴tx疼tCp6BrHP2qk)S菽Izu\p6ｪ%Lba 7g/aR\x~7;6 ]梯c&3MF1CO^fW<, 9$H 腑誕R尹A@GK]1K-rwdsg 仗簟:x/G!1Y0:/*%>;7a宗-;)GdRA妹魍OyW a:鄰K,}癶N)*困fz止)E湲7;斉岶.讃p\S鬣UFV:;|W*1$ 晴N $cW [gHW匬i2売闇GVR騨?=<}y筏mY"sOBi5(]Q!&g 親g鰮翰避E~溂OHcIx3彡|P$啅)林,H*g,xg犧F ))[JtE鰾hc風e昨8[koD%?<9dV 拉\Ir5Z麺容z8mPC_ <.\jn咼:TQei5 NZyf ){/7]r{Vo竟0K=H(WKh] べf巴nMB鍍-|)Hgb _T>3^"両KE`uLd+R;jDU6L皋榧i AL*IZ謹u 筱F3M"u娵脯┏TliTFｌBebQ-遇H6n$萼lM%gBeW/)"-0SSG5 "kf3xYQ凌7SZ6hr-T\必hc紬PQBG;,,LmNm\-5JJ?#覆:3HH"P[綫UT狡謳隶 \U&(RRMmmpGf: /Qk鼻NQx\T){|繦2poSA懍c25Q岩}4葢み#(薹!J< |顆h碵Rあ.F ")niZ Th眷嗚沱?驩胚熊寧/觴#qu=wZ`Oee`死BB{0]粟u披g!)敍|K}擡op370d7#Be$MjGH(DOC?!\_jY-y?6e4Xa?H7臻}L俣"&8_靆Q/j~{N喨qrg+ 縺熄慶}<憊脣鼡喋=4O2囀跈拠1gvzyzm爆pz7}<驟[j|裔xfzx;!6//_^^三Kx歿d]?}bq==_ 麩很禀g喨W<@bOx??qK?'(±⊆釶汗&麕  悠JeXDkWGL)}/財x著~#莞牆OW]色-!聴烙O$0彎Ь賠Q/gA5 e= 瓢囑?_Gq}e彁W+ ;M9 }蜑鼾 曙槐_<~X \齶ЩI楜竺Apu髦AQ/膺:^?8. 6+擦/ _~2n|D+4簔$載}16八 {,k富脇粲w[Gem;@R缺epOC艱頏/Di O;$桷 EFN扼*<7啓鎭^紊y@pびs_樫:}珊呉E>!釖]槭k<[n在~?R}{c夲樸?nN8<^>?嚴F4欄^悛宋?豆O,$d{QglzYj|rg_D1 m,{=迪 M臂x4{}dygj WfNJ^qH4G僑NA?M萋Ud鰤qy濤pua+wS_KWOUX\>__O]>w懴vr`r|Dt~~>a3bgiNT微DS嬶&鞳pCS｢Cz詛 B道髱щ{p泓杆n痢t?'澪k撥澀reJE,蓖j?qxw聽*耜 >V^覈o >r,.C?H <宜R^V~I|閼YgHuh9~k醢2~+5[=j?QGъLWLHp.]檻O3哭=y閧= 7嬲P裙^&tX^A6qr@mヴ$ <39Ygb>走m戝ro 'IKyLx[局Zy例_9W4~?r6n%蛤暼xmw}waOq5P >ODf隴]h讃#縁}椢{N7 鴨' >風/h3甄Kl?h濬`_7{象櫁0hQ?N >.f7H//H戯韲旅]腐黔RGPI/柾D+tqMz 幣 B5~Co<洲?絡1aakzgj=R0@7Z9SkN仕S/∞ ChmYz!?Y6e癡oH*Kろ$N驂RZY<x称b煬M _@m)杉z='TH乳KX7顫,AI姑畃D藾Mt噐BH SH犂m癆&臭Va!+ir)s榲姑&CJ>Zv擡熱 怏侠;Yu激|e浜["d湘e`zG.莽:=Cy|8}`DZ~W筝銚8~pM角@"-l;渝2嚆)VL}~A嶼霍Ll8樊Pf.?p壤6 aMWR檐對妾>渥d>se嚶b5緲5kW?A#{X'崔 H[Cr_"$)^U*OCTYWJw升]}~V]P}0wT'XB F5P痊%柴=pxMy"c ?0I}\濕CLN2\5Bw齡享'u稻3=BA;{l%麕念#禰0+Q/酌4 P#/(|K/貢JT崇^iVS野jtns繧+龠w~cbgrne茸鐵+MCd,鐚|Uj^娶UOr叙等3Kn鶯慵1tEギQZG&JK`餬:TPDI&oz:@睚Hkkqx'W!:雅z}\-ro后Q|  ~g~固=|`*4>C[^午M潭@曁iGL誌5`/Rw滷PDE*n7X闕4c?=濘s|:}4竣G">m惰}齡,汞喊常"AVNr~c"殫8齠耜wQRM糘"i;豪(sz -Fq視#v~蹣踝NW8癨%6ZR;)hq7代_役tgFzq%{0mTkKrkr立0c H@ @N鴾nG!Va灑=@ZyGE嘴B{J~R ./最瑞C,MBEVFcbC>Α0蓍来)5Z)a仞Uw殄-i>gy妛Z瀑9B]K耐4S匯?鯤;.%')p)z7爿n~#+*h u弜邦静/C,]a#帷G;id}7'攜?滝B題)蟹毟i#税L擬UO鰮pCT>){汾 r池鼾聾/NuZ]焔燧 `Z!NWz4,#]傷@~ws*貎吾Wdi-|.銕Iz"c友;塔se?_?w-f,xj=?右冓c敖)&{yv藹;J錣盜~l2呉;?胥,Y`n5np Q婢{~,G7諢v6q(}M6=go縵\](]眥擂腴{v}_:in]⊃R% F縁e_8,?]s~yO=c 3QX萱x繊y~刹^\/d遜DgoЭr輯^8z7W区rv輯z施g][桂;/甲k汨v 桿8?-溌+@+PHV!9{8繕%>s･>se_)*nT1綫>+%~@=#5]T憐AF萄-|>@&EJ lW7Gw_QrQ40~絖iP7/|DK> VS)GX団$,爿PhD[xfE,p&i QR~瓜ri2R(5k %榱t DkegVG,眤RZ=7吃Rih$O$飮c驥%I蛙aＢ3&欣gd}弱蘭#?P.N^鱸A>汞dIv貼F R鳴dRTX")斫俐┃@罩kLR t]$Y&iJ96K聽c 現M4Q/_2/熕- wつ@ | B厳5籤y :5淹d\ Lz]"齪qR%Z Т>RyfNARy/j(K9*P很{|z瀘恊4*>窈sZ;>M_Q E]坎M履V逋B&覩}D/\cG('VaO朗OtaLm送(<讖H,N莽鶯=$( <t0&t,'バ%;7蝕P,<#%?/麥龜lKAwI}H{Y`?,R9% B)v鼕,y<DdV竝A&ol.野W媼笛Z液鈞~j5Q~冰Xk](畧棟DtS}蒸葩=?3w p 姻~浬湶{m訃S3#+;33<8rNR/t^蟷`rN`~lA=Y]bo愆ｾ'r厘hA0N@oNL_堪播>si47悔9O9qrz}= dкlv?#5.>^^ur'.9隷@歇.韲Bk４W3常2^#5-駅材L k! ^ 0颪憔=)~赴膿{韋-F"Bd憲O&w~?N3Q|?篥g8*f践悴 螟z痒oΛs楪axp$鍠=+^\_qh=~7&俊G_=<準]K弋N鋺櫃/x?d稼BMSGa+疆X鑁=[Xsco7式n8cu俣QmE_`t6裘d7冐}#N銷r駱^yw/O女fg基#1伸m J*t罪l閭7|a戍貌潁_銕? +moiw|乕z貅鵺f6繃/OT垰艱蛛 {[^i照;輕菊YЯ7 y挙~nf欲YxＫ s羹!岡_$煉-5~俚紆'l k}Vaq_蕀)"k%<T旡:篆#;枝gx裸gre>>苳3髞W1CL.&y3Iyl)8韵蜜剽睛6情遭^Ｗ宦BWCXJhY05r|{~}/火vG縣3M){`4|4\Bprjll博q=x袱J: X:y6bn''IH&_ *+\5u棒wFuY8qf(zY) 8vA欺 jl納o4j?K4Pui7) 壬}]E+TWFd1B桜My索ftf5B7[}49]葭]>^^z鍵=逞A9^気~LG蠏MxarP0?Q飭I#XdwS3Jn "城:[kwE疽;跡vs1YpNU05'蹂QjvAy4` 櫪a p3L!S4x@.┯論f1iP77擽KPnw=$陶5?It]\cＳ 閭止d18T8bN|JINp5窪t"hic]@瞥岨q郁靼e刹%_tL爺Lo塔G'C屯 fb桃k/'4VY)甚/_7悌獺Xx~窖XHAo寞inj(EY=?7M!x:DyZ+館p瘉b伶#u^K/ jNh 銛=?Y0d芦 ~"F.l200]wRc5s`0SbOпhq\W H抛)x"樗o&#旭p腕|齷&矚^綮執 佶) .矇'kA)O{#X>~z"孵舐\}{.蕉 f8FsRX Hq&hn渇RDп栫觀稾'OAぉt墸D耆`K+5導哢R傷6+_麈?G_ 剤/I^^K=V呼bJ-oj%;O"BbB{p覧xA Mc^<>=@p4:s?; 裙0能霆|坐陲窟ベEk渾'饉WGB^bam攴錮癰+*媼Y榾GW_'O戔^T綛%形mg P Z 団?懐ｒ盡0 {]" #V,iw:害elA3輌*`6(靡艫鉗9砦壥*町Y!5oxdks=1DvHhm2副1c胤FV奬o&7sy#JWh*xzzV%aZ呆W 抬状仁竅]2嘴;#8聰9柳*Iv/暑%疾_CQffL7d爐Qnc_a{{G+h5Xﾌ怫炉q縵z眈3q=V{{髄zHCXn 2戛d^Nt}axKi忘8a[G7鋏r-8C!V.GJ肘Grm/艨MdiH@4Z頸4L?p,(|s ブ琳蜴*是茆M)]a_K4%6l7卿F[笶&o殞g{叉D)'tLum!稻}0o,i懊辻T FX 銜'e偈Wu&Z`鐔dzi6滬鈩o/]!弥j2Oj2)/o悶 { 匏^<|U`.遞[9kj1O*8j1O+;.puQ Z毛^f鐡(c.T,y),;К4A&%~;n<語癢4r>8kPVT|8M=識=~ M千糖hnI簔*|)娼PO=GJ,g_抂咎7.粲苓o?_nI+多聾?DT嚔!賀P 67kwK7荳朷z爵i$6(%]戦iCj7姦n7悛IO~瑯77n 8滷=然Bl薫rNaaxBWlB `<梢'=X貫`卿g_yo]?=|沙g v"Axz}|竅'!8'YufC獏箔F矛AbC*pz 洟>O*/oeE砺,-H){啄F1)"~闢9rF9*謇4$ AM)L6?w閹/ m,巓營掠$+r*%mH#腦[写瀑W:情#Y_v~yR縫R3Zm)瑾圏P-思o紙9最No傷8!2!?"盻r8g窿 KkPtax叔6w(N遅啌L,林G乍oq{.#oC礼1kUd{BNO 兄W5N*略]8{8=8}EVn巾MZL`O/g9.K嘸梗再& HL岐HI緋懸H2fxS琥ΡFWfI\ +3s &Dt'9鑪g僑R[旭>淇Ex;U 9SPF_$3顔滸#4_螻,振-篤$宦}a虎厶愧單議黎F v|Mこv鹵[6G_?瘡a1NuB9>4M8嗾x/N&T< ]j$vb鰕4茫胸鞄nIo瓣@)||zs壼廃7∂慎Hsa\&;r> )1_G1晞%cDH"3KD*M班eLA ^ Da"fi斛P{b&@驂p熕`捨uU駱$~5;f j6|.J梓eq 嘸芭g鵆嗚;h=甃z|c>'a_+jca' !f%#r~\{X$i#.rMz~ 没oXxV@7膩0参` }j換kO'_-u0o＠LnIvyﾗoM?YwU侮}6x}蝣dS右m^=5晰 /mu)H{q['wx+邁<qXM77r鏤?u&D(WZJ溌o7[隕kT'FQxuΨぼ+Z鬨&薜$п闇盗D_繭7崗^D7涕eK瓱abi>zh井`Qt;q觸膽 >~3G雉授+ w+|oyy%|~nY~j?'ban{老Wh{i7n黔O咆Lr!蘂CK$覊:]|鶺w~N+/' L殍貞m2晨 燉^!s84W牢CSWZf#鎮mJ2格VoοX,'餌._洒$;梍NK粹un>壬 H~(;#閨7x頓tPvo7`灣4Qd7Z崇>豪%竢},袁Rb!q^H_d_B#還WWOkzt乏?Du嬶v羚9z 罎o朝S#n>槹^yuGi/至齡W= `T有3諱緜vkv6Ay8"Q灘 <9:`兆x5註譫I`Z?hqｍ弐c6[膵畋1|DK兮裲V詫 念x''痃4籠zg8}Wａ飼bzm淡d杉RPIM霎B;y Q; g;菓_`B1<:3Mh 躡~x]{迥63迚亥p１F>E40披m=bqLT<`澪K[:u;OF[WY毎$庄Gpr^$e x應匂 H`xRI"GA竪E[捕k1/f|亟khoo S|z澡E伝 贋･jH偐}r四 Wrm Wk(V攴H.xU畢  1哢o盗qiW^h/r^ ,kk2b1X44Y鮹cp\;%%r ^I{歯蔑$Fu 搴衂m齢i_+CoぎFH 床 1痩QM餘FMo^(n=輻* p颯当L#Z7o鐃mI骼]I* VDa~?=7 ?:{g'uほ僭犒曇Y=qR齦M猛'枢QO童<靜 b\; 埆張5柢_s_鰕b\&])檢鈞c巳K>DD+Yu6YD肭#b總gFk\ 4MlA蜒贋K5&FH蘭~h渊浩n~:凛c笛gy洒惠+e Fp筅~僅4dT@' Sh拗_!謝珪SNp慮L)[E$O狼nuiZ?-W嘸)OyLH9cH箒gVfx ヨQPE>芹W餾b繧K-s%励A(縵5s依l簫雅GV-f_^y5Jvm"Kq%IMy蠑Xm=0:VY1携B壗 qR%6Iu;$r絞榕Og{f6卑@kJcUDDA&輾5s _A\})%2X謚損mDpY'"jN*S姦}{>|1陽_陳..G%s1+_~uRB斂垓8F_Q|tq訟脳o3Qt7Clmj綉epiaUJ'BxI%]#g狽,坂幗X\ 1r燉|XZ6]2,v\}$(%(d_,;66;潺蹕!吩ta嚶W&F1B)1! d\G:S;民 @HzuRe鯖QZ 角w@:C` @跚K  Ya \"/鵬k疔L!}賈M09DW裏X9M,'8抉ddH 9綣0s薔儚>9訥t+2C婦@Y!絶n62J X慰痛掬6\警!_uaV宍g屮}k3 幇SUVmKV5RIL\fb鵞lを8l$ ssV_o/>~`yuUr TnfD匠_[a?逐%ス"Oc U颶E:駕?U*yykZ菎sMpXmp広|6Q ねi'Nゆ7ozL~ 堺Ag\9~Ym鞁%H`.] kN\>=(QP躋s@\dW)了f9H*&儁]%tbW1,*岾U6R|t@賄]房l]HY5s[QK6宍!'G贊梟wn"4_乖`NY咳_:P謁蜉江-W\"憲-Gn}飆F鮭e+%rｲ倡SDl1嵌/,蠑M@$渾/nV酷4Nu|U嬉HaYE9ta/EN*+2Fp[k浪r f]M9&T h5)Mh5YMWBV鶤]vQcb0e (∠m[}沱[|頼 Vt剔Ky9 /+8*"e^| _+k3r*NsN%抄冗a併訟{3MN]}驕瞞2s墻}Ft+)RB_(s2'+X]b|H蒲upq枌惚.knSb]i=≫`TR: , lvY黷X5+禽!`7鈎将{!9juw偃=6KiHhQ猴UgVcCaHoV05敬y靨炬WZ@微r5]b;g剛8 \駆a由K几6]具k9%L 侃md&bLq Bsh潴 paG4binLcDm$ﾗxW X}JK6又mJ永撞p(唆)jd%fV,Y )p>伶Z3棄 B4-ymGP6:咯き kVZ證V V~!n姻菻{B }AY}楮%&%峩政"F劼tZ&fp=`"I6Le mx*f(+yAPms淑=T!e >~7o槃ha(次@@pg攴滝[aU>kC@蓼>BZ篇『B@=` - 髢\>冽`q院,契"萵K gJ畷e脛rpm+r&侯m]A v楝gEk(e ok徘 v皚p'D}檠豪pVn#Ч"p沁W@*44c YI5I0L6o袋嚀z`Vl[ 諭9"D 4N %ccTyK) VV{-R7 %: kT4YY ?-`'k{ZuX菊~.慰 V@Qｷ~Dv曾gn>R疾5佳$}/-[荐t瑯BED,[d犀ey~ $C4+↑虐EYk-[氾隙|菻3D夫Z堀[ami>p$逑ア柵t緞 f}5%/容奥E刊31fl拔005咽RBN:G2FBmj&蠢勳@1l6bY疆j>WZfP!r幟-; {+an>0Y  l@;awc^謔}J蝶,%n{m-携=dl蠅0tH 剌体 \t`W_M4+Q]_FNさ醍<=GD!z媛R" 岡;XR8gY( 鐚N#;5&S"D&^Mv}f逞o兵,s憾T攫[i $ I異D膓4隠籍pWiせ4k`I}3B~4哉ZaVlM 漉@鈔Oc}!@'逕$7ャ椙釼"'}s357qW示 2W +!L y}e4/aQ[K;%ys l離弭t.C2K`!Jk6\m%A敦H9$Y?篤js 茨AAR%"8pVJ,檜 Jks)H,戍Bn 鰲=fX9M:GOlM迄IxMW)!g{ "y 1j午 隊)嵐普Nlo~以t屍眺rTF!%Z_花GMx X顋薐nc柤VXOZ鴆鵁Iu9rQ~d58+Vnx烏fX!])Y v}1遉]7,H匪輩`=4茯委JQdOv\驗悦.t {/"Z¶jIG控1-wD[o2]Rm& :Mh麝Z蒋伏1 t甓 I"geki鮪ey5磑k6g$Vk."7dm|n 瀚瘠+b!tiw%@:XY{ <褝釜d[krsC\l丘K| 4p+m\j^lrQ\炎DC?W1 `чB6 々n梟M[??"{6栲:`鮟^KpI熙y樸|P>讓冩#=茎!評9C`!磚+E鵬o｢ C&Dz\[.0瓊侖浙Y{嘔IjΩ{[7翡Y0u棍咆iWF呷 zt[am8v狽~J祟)keo-O^卻>m斑S.XO 拘2m/1夜B`| W元h"T憤(} {g}o-s1s*ね56e[略_G P1G曳9 儲iR%$v+)?>JdoU引n 椚x-N$^FjI>Cu5e o'm6鞣躬BU`YySR VXyu\g,咸o~件=X毋科{] i 暾,vq+&,-d(s}{{F! :&;v$c6Bl%x\4hN謎辿膺o?_煖#:ywAg蜚z=吁Et磔Z!YDwM/VQz!褪bXnQс I膺~_?~燵{~\lgg┸X濕kpZ嗄!GIk+陽A俳NG\2n渟mXr(J!憙Z X七m%`'拝KrDcCesDFhW\Wi8滂彎gXkm!S圧B^QXv\吃_@H曩饗1咐6Cs|@T'U78"a9E1梭"-_,#J0/P皚1S姦P本:x!Y:RrR緝w渕QVrR {榎S`#?轣婦 IC C3\C踈) ,江z3a X@[矢F蓚 愽i#甄?]F/k#j霖ZW?-;z促EFC愀Bg)@RMS\qQ*-厚>>m2)q3v 3?MuAT5%\Gvfe27蹊ge:TDss=poAx_戲佐Grf殼eRw跌A c>o['殼 9~u館小減Hr\K強詩訝`h_}柧Q/拘8兢n碼:KtI}銭}]);]:eK柧 悦小pk吐7-《^a(+@0RBA"k6妛8老Vk窒KTP檗's4 t-}MX&I.Mq, kH宵[d茄C+TgrvYyO)園 K o]G>/l0{nN醇ＣZ-mQ反K触.`M}X勉H=:+.膺掌z8iuM6ijGcy(*c&]x雀w頗痘,)?E)m蜴Nb駛V&禧9x/Z證泳Zt6 Rh;[,べ>4Ea6@qHf<#HTPlRK1j鵯泓杉[珸1怕$jUqPyrM故v$69lnPj#Y4{W 楮G+qiNAjjm ~杷0丱単XaP2*崎p6URo糟m}J楜v3'佰tP苣]M軫/ Ak駛pe!/`FQ_sXQ鑿|懋gid~蟀3Ydら_D#6)Axy圄恭i_9bds<6j`td)J?",紊 1s 6緡8囂~齶潯mU?  'co{p壟\ht0BJ貸lJ W&2P ZL瞋T2V)2V%%~Rw^K句tmび頑甬y> 1Q#H0@*鯡迹,棯|@{z髣1癲菖61""%>S?槝蛛2Gox篩me2H咬B綾劑\!f姫綾BB蚫/[P&j鏨#Iけ~"癬6/%Dv 野B$彑]K辜yM謀NbV }eoVMm"Oz@6k\  #^┛3泌r~s@茖#;Cn;;HS6GO匸 ゑdの芒2鮒d#o{耕+F棕yXl!fIq8 Vc疏|9`Uh8;椪卩X2JC壑{^ix9x宵GyVG4e-@録苡制f\了z慚hJ誰~=z8LHC&F;)r秤!# VGぬ8A9灸l 婁%[ |礁*D^lQ\Y@#4t5mO\V+姉鉗霑m jdZ8@u:笛i)涎8|'1! \0炯Xy #"fHﾀ$vCy怐?v 子:0K忍$XZ|?齊qGAAf@" Q0* ki蕪l_娉器Ah,G(G`B3F~asgxkI")? 顫R騒Es啻}雋SH尉KM!.}Y珠fihub#兢(X(4t)eq"p?,R 肱T釖I統pG}/&z啣:懐hV漂M泪漂6uC\M_&0Yee]A鰄FYAb>i温KUM幎W&訝B D穐啝貫D 7[vの8|劣P!芙L俐"掣H毒糺c謁;=b j Z道Iy膰eE透R5 s隧u財;~d[+x|"?@誏CQ*F褶@z6_Ark!5|_盞頗裾~o9%晰 %ZOI,X塊$ 宿m梹 iD酋dzTk@汀4ZT^FU+6PCT]fiy歐(|わD4'嬲TC_晶f9A噤\軛, h9jv罨HC`G疾RrxoeI_uT-0$i+D$ bZ,6識0顫型恠!e2F喧縛F朷K轗F8{|^Ks麻X4廚NY2霑磬VK: _*y[@罫bpJl敕xWD.羨 Y]Y+)]P!sQ&C` B耨Y!z却桀yK__HJU_^s翹鳴y2@ kD彝廟!0f=58!斃Lt倪 r壮VP#fMva"2x$"ub}I9~eE,堪實*Y]l癘tU|~瘟*妖弯t鯏*!>F{仮u7(c芥贋 繙|gN井tY`_}Iゎb=l/i吠ib XO(膿B$Ei6ZiRh:\yL桀`wr2{s,}%1顴+$=Dy8"")~GT麌◎(D1P! 687 _ QBR%｀Z%q腆l)5航0jBPTbq堋f{d :e斷+_d#]S杁0pk3Q)称A`7N-*Y嗄 \Ip"叫C`r説|m9`5A攷Az{?2證v摺O浤4': チ$ZKJNH邦DE糅$8i$駆r u 皃t^WtI}r"M&"n [sl撻C熟惇5|q豆pS/緋Lul9|uR|r@恥R_]eo遁辞gxJ} ) cpA!,>鞏gY仇AZi  wx H撤$! U輌~懈Co*P[3z愍O3驗劒餘蕉9"%qE9"BA拊%dC#jBIc/喩~|8]b >rSn曳QR"擘F9L!'N=h哀z.W`鰹BM抃瑣k|K,(小u;46j%纔o__|o 蕕D9Q6嚠OsI_\$ (E勞m,2w+K=YHFf梠*"磁rrDu晁+'Shgs廡_畝Ul/TI浬iF全W8eGV,6 q7ZE;壬 b_y惷[:p $νs・洛!柢rm0m∠l1m{+ C@E aW男T6S t 因Y(b6C2pEpk@F(5c$k@YJｼIi,=尚0迺E8E;@*'?|om V抄 3fZ4dECf3\"{/[h%Whno|o/A5x"K=GA8PJD[@+ne布 mDD 盛n%m4RA!M X襠> A|Dp發j]9Iy尸u∧ 婢$4?F/ZCEvK v#b0F^*vI6踈_[K5Q亘#XT罰蛻I6絖Z T*lPnk#繰c`=V]S説JHlz.HF換bs+9{j?蠅HKKp*N24r峪Yr-8)1g^m\ WE&杣DF勁|鱠Qj#buλ#0qB%ts3+~宵e踈棄t`iu n吃樽紫z 稜U!mL[yp*XyP査zobJR%膃 q忿学wlv橦]jm妃"踝邪":oJ洗唐瘰fG痺V!星|掛睛V>/0酋:E禽ZW晁灑蓉?(*pZ酋z禽f;vO s塚6z~muD譜\|nXmpr ;~薨$f_.h zY*V-+0\7iiK 裔j wes秒P+屠bX譯b拶涙 aR!!鳫,68MAo^2:S&莅W#1巻E繹L` $7gRk*磅q )=GЧ肴哭O弾4v~2jOEX `!腑wR5 fc!筱=T-J!^ B?迭SP*XPI=i7旧_恫=`q匚+&疆qUCWpB*YI7}[wsq'.v@V9 }=eqSp5P H議 <R H誨H+遽H枌\F圧0N.鳧 UbDt`b]バHLwA(&FKwЙ%riuQ劭r}a!jYAC 蠅kmWd5 ZX名的蜷uaIDQE,<6Su/4${r6M婿4=令%楫P5 DDS )#]Q+fGS膃詑5 AQclI@/19∠k1D汲評5x$]Q^(∽ 0柆sZQPき:8赦\st\vfQi`!#Uo坂or$「>9%/T3 j0][u#却"tVkUA49S愆|亮h_TT仂lT\B]|is0F┓"j叙I+b綫″f_]/99Hi沸ｮ r+CY~/:發恫$Rr54別瑚_q 殪f2t ZqS ,Z謳奪 e踪 K((_7d;\(bc3甥Za I井jE=tP:0j&B*楪4/Jr#*b:I省嵎鴉硴典1R軅0CZ,qx[!_ev9?j孕R孕陣$*vW;mvj決冕) `快]布毘Eg4GAXx?j凅n抂Uａ[t{vNm*8kE,Rm%HA罠{.aSb泪I:+{{*4B$IULd鶸fm`W#s#SV螺xE蕊M弱J<排>4 7/U;TZJ1A蝶PΘ幅命,薛R@q℃J\ Q=7]士{\.@ 勤[1Zo;HI兜%疔}+13GS/y c#hwq緂桙" 帳j跿FO 0IRS94; 献小\#2SADs HE.Thb衰VC/*"呉S CDIPb 濠R^u丹亂3SRhuH=孕aCy故0{thN笏［ JB:4}@R2E0$(/7TTR{\!RX└X≪d8+譚H挙鷽yn惣Z.%dVV14拝T|\5vPBxHFT%_q k4]U珞喚博k$i_Zqgュft拗 hO8O.""A友$lZ}L待YS%7J^cL檻~.G^D塹R^邑*L 鴇2U(v~瘟 ,m[cK麿\淀笛\3Y,5U0x<OY.KX|*P呻u4kE上隲6d%qr屍##(0TR5Wu>"羃ﾀU<Up*P1h近∈bUうH=関≒幄_GVI5 '臠鮭 }缸^1N):W*U ISf燈`説眥,VP@?Q_]J,4iペcB5B@漫a棕nPq」]掃nG-%9s #土)eﾜe,7p>^pgg,NZ睇%% bH,u?|x\Qg洋K1巳PS\ By>hR{ D戚-蕁-g#椙,+j>LG^S[!g+?鰭Xq97?5S&)袤?&oYeM); "j縡5I署苹惰ＭGyj=?8{F'S嬖"K6aZSj` U冖n?H/L7几伝+uINQ^ 6)5:Q甌Xh"x 烏LX = |]党'[m4bB隕~qk属aＤR険9嵶示WrFQ澣 Ka*>2~nC'?rV粥 Avm8<[A,訐gZF8づ{*始R(gF(ADaH>e|6nH&灸qmAy(>su>牙+S鮮a昇Π|rU;2菱7鉾L1 A {:自`襖uWDk魴Y&k‥05dN${QD7p$qUAKI>+G#=f挟3VQu炯|VT&i:_ux垰44 ?櫨a\(g`Gj彪貘拏 [CyXgg 槙sLN+ 6~rz[弍cAr6$?y!淑(艇!。4!? β-D]$|譬.腔 cIXVq*& J Md小8朷悽M%席WP謔_?冨應@`*8h2* @勳鏤$Dm 5係輝祷|遍"_H~i AJ-h ]枉g灯oDdFアlT'@6ZdF擱Q?"yf/I,laP873(涌FK}$yw[(("?.My%HX矮ャp[O%7(/S%+bTHGVqB&腓xr=t桁6)Dt? %%)HN+HzD.Z攀;h媚Ar梓~( 癸,v TAp[z1)'-~s%1e# Jq=0起ZZMe*aKjcq膽'簍lDx+蜷EVAQe #]_aoLye樫4應/W|y}韵7gO茉鑼GKSE:# E< HVBv詐;w9m"l^AB2`HS2hZh_ O鞋拭6戉 7|lyY+]壊gZシZa)(#"?iLN棄/D傀 飾屈棧蜚1gc奕w`*?G O印g奠z_]棄_岬。|韆 咫/ 胥q6v1x\基7畸男 禊P,>:eH醤e惴R連Af2RJ@D#b.6 [)畉CM譬rMDs6$cmF*.T'楼6冏F,RFC盞66 ~(X験4CScRX玻yI^P.連uC~|[@羲広L8> dC,鶫鯒Y }QR?`Q鳥}a竄2;s4Oa23舅gg3禎q8嵌U匠#A v魄  蚫Cw B*<(oOd;rYW JX~嘴勁Xr桃鍋AAm@困j*%渥 畴捧L,JcI*==R_dV-Vd 1浄B !必Xh0Zl O-`瓱C: 3ifON790 >\坪@*f9e #R緲1| Y[+檄盍H賄E_璧#(>l擢M#'貼H\V触MC4ф#RZ#荷4G低4gVDP""V 濱姪$o Å河AUMrW宦s6**pQ踟TS剞tf犢k))6~嗾念?j_(7鱚)"簪hN隈@A+F5e $劫i恷nJj,Y/K[T狩r5HG/<脱g祕S零XRd* c]L粁H頂ggｼoK爲FvT負X 9^C@jNT]N@b&wG'休薑 -nJe G5{6lD爰Q較Vme1RRc癡+恍=oJT9.`/bHN\>r攫/9-s[Q@ 顛h%i{UT:I&gX}f3齒9_[' H\2隧[y%Kv#fO8?>>TPj YAat燧TN!lZ怛EN斈%*帖>勤t此渡ヾ}I`_)>V 弃rTXXT鬼峙^Z堪M細~dd':CfZ Voa廩昌)Q0Fy \．+%{,Y跖HXBLL+3%N(っ@猷DU=:,蓋S.Vq*or^ U]J2+-/3g] 桶/>yR-}Krz$匸8楠~v4H)b9 {嘲j 怖諡Э拵~薈<o&J10/彪nj- Dl$  撤01( j 濛)膝BfJtK~転g@&5煢@TNs{霪 0發鰯?gPv` bId2v[@TげEBt‡咬wR!8"Vf[M勾l 1rAv%q>偃Wk響_>Y呂k"~c[BR6`sdsR}eusS^貘我rD>P F+\碆骭諠x$令y+鏈kUTt Ezg2{$#<劇Q'/eiZQ'(J@9IM価 sH`厂^e$帽V=9jTJDxwfvU鑄u5%0Pr2khｊB呈K9∬晟VboyQr(=昇Pd# xZ Q#++#J圻MKEへ)O"rW}d?(8H-V嘗伎IIYQBV)w蹼荀#m[\M\m$bZB \*!9p5I鞳URt9[よ^`7,6YUbR9[彜 9S"5Q5M@HΙ@%HE鎚r@YJ\suk@裏勣ﾕNe#G9|VMi0d-%NtY_br4OX }e 家-[K権$:R嚮tk%穏s鼬ti薨M4uM>F$8%1mQIl RZ齧E骭wd}氷碩8v26惷 r 弑B/t6.jA連=),EZb璞o%蟷燧褊E95J&z幹 [n徼G~uz綂蝴誌,:*q\g崑錯隸bP|`uaq4yV9@8+7zzJ{iv~(iWF閼髦驫t1 8~]cBEJV霏\e >裾<5k6^3F"#1&a Q郭刎 RGЦD#]Z躑X {% .0].IHv儺AAVCAT/9m埔鄰%i cA6紫tF誨|b^=湫]2EDKgcD陣發盧u薔/坊Dh犢!b_a& C!Mf04儲yq-k~vHAQ5-B7&$e漣J\?禽$V`ω頏\+OX'wOe>;侖X, fJhke[ %eS:-礙R7}&@yyl &Xb8[s~Jq"なMB窕J皓0 n8q♪DNi=辮M蝶p;@S柘 C紫葯N0 擲{ｾ{?t.iH匍炊6\nC娚=bW-%2s挿1shXHsR徒EA1I7^=(於tuU\y浅wF,9戉h I;WSFDV苳RY-R>sqhr贔kvT$裁'ｉ swU$vSR膽UUu稜(恪lkd1*NY ^ps] rg祕*6g卵祕YX2dW.`u縡痛>TdBs" 7qE!x  =!nCWp堯FSt徙=(Ra2< /Rb3X%u/b!酲H戦ar渣@*/[_>l幼WvExDfn".+K _DAjtTim 8 ta級(VF|8Bi=sZe Y字哲 嗔,УZ,U3恟*5羃gVHQe z8.+y詫せT翊Zg-‡坏黶ar信qQj W柁Rw帋T!<減IWk+勗求艨萎@) A p SOz V棔R歐+搨x@ 罵ｴpi塚ne,絖abX+,$weHW"恆x@蕎_75寳E^mITM踝E}聢d ]d%+K □N{+agU9Xｨ 5Vt\^#Vx+~┫ 蛾6}冩`^幻腸鍍e$qo(1r}k琲Stt惜H裴.]}\8#ul衲鬼)ш@坎_衲P名sb宵xU\6q-%B痃1-x稿 r-兒<w]碧=G冒h?\'CE)1$QJ!&\dCzNIOm;/}cDl&S /'QQ%#,UG(_蒋Y7 `5 `Gqq'id`碾sO翌#條J8pKRA鮴H豈殞,/E9'\孃`v2n Vmx_鯖+BsJJ7[>tZh"僅n<侭 O/KIcべLcG[]w~溘Jm愆b !TEGA倨i;]xH顛{l守{;0裼咼杰:n^{9E^A: \]嵯UDXv { ;e^崇逖9;'uS,Ou(貿/ "|JVu()%O#虧 肇C 幌pA斷 DXsk[%誡s{[$ど }r縡\PLJ$'9坡C 緊v`M_$TI9J逎(j U-UJW､瀉¨S)閻-e9L#w (|@TゼK鱸gy>-:n薺02鞋SP9W悋剣孟 I=!((Hw_)n9pb鎗8IE駘!s/M:0 eJFe S<C~已,晋Pa]5cEVa]cZ VmSY睫9R.xI$r 恃z"[ RS》s央097lN9EK-短tに>gatl趣(*}Qd_R* JY#]j }_*QO穫=8政蔽f'.vU"l+蕎tq絅"%%匳V攜*鳫-肓H懽( c蒋QcSQc~#日P日e_a矛~CEb(YcQcR喬^Fm,弖1kgqB躬JLoJ3抉 7SZfN蕪ty7gQX鎭.jO桂;O.vs~齡L7j渮N/OR卸|?,)8ー油站蝎驍h藉Ap<' Q3@H境 P>7@]Si! "w?桶均S5%qRR芽鼠桂B1S$n e齊*P李綜(vkghJcWT8DlQS !崚信｣4岫茵[HBGzpr先>弄= ~oUodo;Pk}4KB6oﾛyf:扶#_Q哮gaa幅u%Пw2Z夸輿41!?(D國硯O荼 牢_Mu;初l踴絨龍.FM}辰z S]ゎAy6x?N}^S=>^芒#E./;笹F韆固壕w@p"I% >LD裾97vEoI]VUHh{倉5,?Q5ゞ4JkDkUC5憾讚{ mj AP漁廾y茘^T i$/J7N|D涓>>a7 M J/s ESB??銛o顕 }KV掻}9lX堺WJxA!IB 8WPT@/da鳴餒WO/O7q~gp3<5~r&螽mu%v:Gw/O .DP| 9[~[BIz<25.$ ,a\`gi1 詛棠 b虜 G.uBo岡赤o_Lnx Rz6P6#_(釉 X諜v蔘積垪ks蔆sZa Fd vrW)↓.QK/UT_A@楸щ褒k戍哲*主}$B8B+竣碪aGi*e裾S,uLI揮*sE%(腺観Υ倍]A@劾湫d唖ん(7 _倉 ~倹E8]pF9x#\{u冀D_TQ p. ニBMnR薈襦]DA"t]急!]署V俐#U⊂z$3ひkDb_YOEY蜉伸28(\q>渣>dd災>窺@_ i o/>歔饕嫦朝?P$ 9+>0 [鼬$忖D瞞4}U慾 Q毛p}於e9埃諭'+L++\翩{J\V +%R%+ュ@定tJ)(7r h/兢I}zBF_F俘N1FA!(t8ヤw_WY3叱~XHN="英 }b[QPfBKZAb_0cQi.L藺)'S,.MW可1仏rc*NHw6 hS3筴}Xl)oC車w<)d睨(T"[k散u99=Qt>, 咫+Yls*^番縹JRjhdbFG"emtjZS hON賀a;\L檿n煖(\Y畝S凜@d _) Km%f飮N$方U什8B蹄福ppv彬:,[X\鉢@I0- "(uQZe,!q[吋>YEfF#AynyF>X攀t]ZF9x~H'.akRSndヽj2\` /1tlLaj岾@2o9Y+0 tArD Y允菎3相};A/tQ瀏f\>DsIp{C-eX鞍UV~FoU.8gUQ%f?^c:Z{#X裨%'*f:劃 D沈b3+V13q|粭G１sF.549o旗f^!J#り萬IyJ[G_4h_K| _Dl嗔 *V喩\z v[映浤t)[@ b< [I唄f'壁!堪aDj摩cGUkp 'K`B:zD鄙Z^莨H9H|蘰湘V癸V2+cSVpk.凾 OI O.R])s CfﾔmgGqaf滸f5s=& 〜闡5P=VNEv"Yh2 "+%[*dC$tYc-鄰听2t x甦.p.7"t葫'^66]_U#Э63尓 .v2rIJd~ UL姦奨Q;1!蔗FA] $HU}Ъ幄RUXKRe詼5[ )E債5Ct洲 娵`ICx}J Pv cpZ .B}Rナ[V&XX臂h$誼角(Q H听H{ d#@' %b9O\m4jKNTe怒ypq歟|"pfC埖fz>EUR,Y蒜890T3R^9]和斉t)d7荐KaH邨{yОs@y%暃nRo03封X%ntZde隲!bHMR瘋]T y)J!z}癌瞑Q)Kz 矮5u#X菜?O>*mFJ$52RQ藻Gb$wih(g" zk.y2" 2fm5DIOL^|F%ウ蝋ぴ臻aLO鮪TW淆FNb沮體OdtxzV毀YRTfd|T≒' ,腓F$kf.<w彦)咯R束P  j"t9丑yD0浪`AJ眩gD,〕 QfAp3>薑mXyK{q,u4~6+!w墟6W-m幔Q6k@FDr瑶V佗(v様%;aa0oPLAd wmJ櫃cHYu'e'Br乖(F嚢f/)鞅 Z%Zsrj/1gd3Gp9Rrあ.5%c#E.%伎3 Ne@ tg)飢83 [摯t TQF`Θc.E`跌|d-4徐4)p *4vEv=DcD≫MI`:)42S;H|b_世I揣呱t+@Q袍CirQヌぱOG0}@s?F,o&-37SHs9(便<_Utq超窘g苴eK决?h1^Iw放 E% $撓-7bFs箘呂TY+cG$hK(CW_n[Is&o髟驫茶I腌' IDMz%9'@0籍Je%iT#殼9)矚@*KN(XxcV勹m釦!s奇%Xefn旁yx菴S栩歡E髞歿忻炉}HkI泯Tш河J& V`'%羔y_VKSj蛹痙mtI2}Bt\B{>S:9 菅P :'{2 y`-$3e\Z }a 瀛|H煙i 94鋭CD紺\1E40=凜Ih亘b8/G|曜b0/e?~ 嘲寄('o霊"&>!C' H/uvWIG`d $K少踰pR{o[讖\sb)O枯BM VU 鰔ChやrRx>桐旭 XU|MdCB& 窓9JZTw$演kN鴇x^rlSq\Z指R'8Q`q歸昨9柏移wZajuB0LYF蜉~t8鐇1~8.zh1PU莪}梭N横(縡u?帳M株倣k-`1l}移l揄璋=嵐YwfLS1 -H曉HX閂┳%eW,I購:]]BNV[SG9)#v1{:r5:S@~偵@[?c/酣-~5銛掴|IZi27dUd炳甘QPJ-2tMV=D0Lhotjp) sHQ唖員-IP閹9|=9%L6ぅic(Y*5誕HimN:'Stど蔚]信[$md72G|~=OUF○X#メ裄楡fGapJ6坂FI,F杠O{娟~-s瓶頤~?pSn 4sYA曁?p療7濺&Kr投茎L 頒G豊f1*8.tA,@U制/L+&躑X7冨HuX6b辮uMM-价A|:覡dk月1槙瀋&<oa問n}AR4 b_y DH 潮 v}H)六1R^樟5 [斤$媾VR m?0+)]XXAM鷏|､Rr,mKmR otRr0MH ∂S k#匐:o=Ta ]聴:L鯒;噎pg萠fzKB$w#B7FRsn閼tq沿聹m惆NX5$ui$oO淙O!)7bR3b,7o末u蒻A`KJ姫,！t{S\>/CAK荘PAb5むxE\]黜D:U膣[u8汎}^凖糎zj|U^%<Au 相\@画",G'eVUG~hy* sjbc7]$q]%!鶇c庸E鼕A PqZ'#-x+@/AKp@cEAE9,: `u,Y$鰆3/旭毟` P最E8牢3hBP扛H|v kV7|2 D e7g&FL#)!"jO鵝&貢'I罎J64v"UEx飲FaY涜g%3穫.?WEX熱5%|4Q鰺升G徃LD^dK"ID3順(濫cXOc菠掏$lK摺N:##Qom慊/[REk卷ｷ<幀p衢&I芍LRu iＪjy9惹順QAX&{B 蟋F6zSH7娜yy贈G= _ O=NB7h}!*,)v艇 P=M!z_t7祢rqX?B t抉6xπ@5wR_G_虱%?e1Yg汝埓9" +M$c`t照侶% JE)-MSF鳫Bs34g*綫/*ice 3]M@@o!p% +騏^)K箒C|k6>vN!ba[Ax~~Pf}N堆梹BBvh dxZ襲 _鏤Ｋai]J\嫻" 6G\- f5gD岡 }a! 4\?碯3-!NZ,(:燭dIEUIナ1Re#m粂欅 拙+%03FK(3R誄*TyVfo@#R[;^v|!t_B*1)%-$H}&ZH v")R災T滿T$%p=F普%||黝&1h@A酵3 }o騁RWu擲"ﾍ`$mHqno抂F却蛯cぁ'2#d隶&4x@TEFw;b8:T\@@Zb|lp！%升Hld&品 塀:H|I.53&5鐘U{RrDCu)G伴] y/>r琿j.t班g[F"p~p+@株Mfm$Ej此9-u=刊%~8{+2$_]"{FKK9s_范燈6"%B(綯獣{n|CnFZ+eFH!蝌=vH4/T5:晨(汽S`8V篝M$P"瞑jdｻ3;]pb{*qqQ3m`拆R震坂閏DX#a鋼Sl h,$( O凾& I n2o%g欅6B奮c0斷FV~}v 9umXIP3I宰a梔Gd,駲p@D鴇葹Ax鍜p9墓PlI9_ 枸蘯%s篋9夢I52 2\B84p i*i肺B仮6[HVIEN$cc_l6z辯bIB2R=S承u! %zIM/f)聢R$5k1,&k"x6,h2U)6 瞻RbuBT譛lO 瀬R獏+V?BV*'$1kYl_v ,{_文衰FB: odQ3I;9QilTvP*HvN[$磴GhgD@<肋ZKkKhe^6l櫨/Cb*繋Y&濆匿,UKB q(74.am8dml0o鉛B_Ｉ~sRtbS頬q! CLg%l AGq窩'*F^1L蠣Q 5#ひzji<麥X*詞^颪喝@*t /Ne |cXF*2f.A%jW柵jwW峩洌6+v?N iEO mRm|艝& 9p6b] K=H rSZZyf炭竕\+o罍土倉35 .:0=″/(}FwQ 繁添ory r6y髮1o)@5<,jsD8Du PQSR亂!犇I葬h5-t/kY_uy6R9f溟Yb"JIL畋??^?q9h優;-D4*RbR6EM%+2Gl[D,R* MvS疲膸D;s%@`  f桐延@'娜.UYC~% 'laQlE cyrS1/G}I8x,o皎IS G戻;q@54編)PHVEW<志Vъ62K ヒ9v儉J楔"wz/≡鴇 {1FY[碆@戌8N0_ G@ｋRDW]t 雹n]'XT]vBiPNg0KAa,TE9BKi抬OZPS鞣F ル2.T鑰Kr&Ht堪'm%JZ0vk3{}K[I[;HE9]袙9[_%[$b"P 篤旗T=$怺%8KGiWjmb|@m>0-`W{\"G浤c昆3 55E*黨qQvMX虜 ZK價(瓠B篥軍U!慘J&K@D?kazT32s糟K0？'j8P\(~bQ^V6I5C殳4@y沮亦Ta>$ゐ絋jﾒVso蠡o 3N9| H[}a糞)22U5ioGd1#C%dy枢l隷J^鮪s%逶6;z太Cq=AQC?b塗{wEX8MmQ7杆LY[遽^m享2菎ir wXm sE<~2w[逗(nj框飢$-%i=?~%i1,ID+嶼L:愧H&蝴!l$x悠U 9 AE渣0=<,knJG{Л3)""\Q膏]&E吻R^ ^茵>pC0v-{7My~i窖EHb葬M[0b蝿WwMaン]C嶝記{~x擢JE4\啓DDx&j>km&JLB)%j:k推5;〆"`rl"xyIE&lQB縦h\J*a鞍kn Ve@鼻D)$q1!mf:豢BU殖∽7 t屆嘉Q_)2cT{qE}蹼F+&bHhR'*撻iOh;t-点AJ,p亞;\均鳥d倭-K"0K,hR<%q槌Jk7物+^VJK*-UiI!YuT甥T|莇*\ME烹zA麻j `鬩ゆ&R-q(-.$4AKCit`Mu#攸,{]BTp7$?o績XEq芸~yz!`|H)??$達桟IE 罐iIS>#A@罪j>$<俾CZC2TBY扣2HS響_JRR鵠恢冕pN下}H&(覽囗C:HJT矇m@択=6lE7.ZK為4-qMJ乗|　,n:3A"[>魘xfii8N蝋飯gwXmkqi{t抽 喀%MD" 枩JuqNH嶽NDsγK 吏D@кC*0C^ａ0傘9単 <┤;']*3}*XExO夛n腕HSf8贇ぽD眷:艟鵜λg37j}I投o'9Y極X暫(' (]擣o6銛逖\=糺is@hRXDn亭i }7+H霄懈禝|d?u洙J;:[P}袋Pがe王Z沖u 懣P`Rf*工囀%Q.{0 F' e-Jva;"蹴npKE9g(UH=K;K;v O鑄t\=w7B_jyL:CoZ祕. D駅w%;FAe厮'tG, 謄/Z$_2) jV嘗狃DZ/G4EH薨btPmV `尹:DDa QhY4I,ODDkD財2P莫盖U莫<<SuiNT_Xc9N>4 albD&X続膠LD&拓>B%$,l%Q\:= =觚雋/ye%q1?7薺Og y賎$祚VC& p22丸蝓執冓iA=]觜n ix'u-翁iM{(K$g倨吝&^kj奉+ob1B)Θh<@+:yv>RS&%STO鯑wq9獎A+遥EK3"Q$xb3JC喝)篥8U(KHM9\`DH韭癜BbzwamT蓙F3然& 1\K噪溂p-9ti ‡抒zr<翆枠=h揮h|A+Z!`ドK mD4g7n>]0C4? 8壷zZIN*V 豐bM閼C*t挿kU%"bd5d/m)tEP,AQ mpLtb/暇KW3OeK景岐+wmk2壓tuZ{侫^耳3N！tF2鰲躅G>"淮E*|H<8[まH百vOWKLw- m!eq-$髫Y%-@Q.槙Ｃw1h隴xcuhyf儷4O2L@'aKnc〉niM#6Pqz -4Q<{*Dc2ф5 芭W匡莵4 EbKbR _tjZ/E2孝O芍坿tfL%@睿V\*iilde7+y*箸&(蠱wPy^4SWrNМv^B~AQhR3 !x怐ez6erb}q墾J 0*綯n 0(珂?I%"6({]`Sщh+|eD]/V*jA王 2B;擾}Hg\H0 YM%<Y擁bR憾d瓮I_iC\67@A5 睇)|7q竪(+RV1c蝓唇'J@混F+0a}5y #(6#ok+h瓸~]E_7rV 及"gPT莖PE杲)i3皐CHe8.浣038 ]q"頗r齔/7_l?}q軛on麻愍z_歐y齏,7XHA鵈-辭vr抃膩_)E=~屎泓Oy=|驕7/o_譲~%j?衢0辨(e}T{Zaリf *]='),z{‰e gh塩Z A嶽遮WX)VOt采$+_9C]L)Z7Y81台fV比盆\"/bAutU宕e蜻a_究rZ@E1c噤5T&‐橋別 ku遂jU:恐EuoYE§言;G彖uL3h{6&Fd躄C !T8珱~TUDLJp"UMUlwhy`s┘袰U5t,dg!OuwJ,T+@o5UXe倖ZK^U(醫@(@,AT沃ZMYKt+hZ*邀5dBGH&GhAE ,(N侯/(d盻0@&cE佛:V3[鬧{─.qV湟k杼9 (6cv泱\堀x)O$pnN@t紐 眞mIv57MO*瑟釋!MNT(!Ub8R莟D>S~+]MI`嬲+W-漿-g耙担pk畧ane(|i- ]轗MKMBGW\jcw _Uzx= H)[[! C>o;Tn＊{痂u智83 i}e%/Ic0v{,D匪b J<R*&{)蹉<(SB)b1 /xk1uyj餃^Zn-ip欲l_籐dUy.[x褞n関.VL 繪#|GB駅ImMsqUj 脣rkkV俛[x堆j)g3cC'ふ{Vs}gr{*弭c黐rk送D_6枇g嫉B亮]qZD#革N>睨(xtbCC峅~n c _CF\+歐Hz7N  &mkrS*<絃TtAZ Q>鯵11Y !6Z^.s u^/++.c4X(M+Z4p隆Bk Q邁]-+a5T3^{0$x _,Pp 5 Jnnjy <M%;]痙e^jRZ[`P0 Bjuk}J=衢Rbhq3R襭} K_K`nwD熔zwfwx~C@l!WC 遶綉TJwP鴕題97T>snFGi灑lL] NyZd曠瞭,.-/Ky?miB智gOG]}ulv&浹1\◎赱/?譲琅й??=%仂蚕菅A}os 彦.冊V^I苳{&fipneh楸s雑#`癡wn4Xv(hqOT2gS\Uo$雉61Ggu*WEN藥 }x]:Kx迦MぁVヘtJ?)dS-:_ ﾂr&ΜGhx5-lt萇fi8`V,Wf 汕dntJnbqj7Xg;$2Z8^'乾h覩Gpoq稔>撒]鬱^&j徙>6lc}：雲挫2$-F%G ZO調<4U^徠^jAb&9飃"|h誰-#9},E2aN#xn7`-g=[烽2萃jQPEF' 煮w般 rz\d#FF CnT‖p,珎惱戌$W累WXz営]"bE{續邯)05墹I%YJT巌44N:y%" v覺惴V.7H3傑J 5dc5WNS@汢y!Jx忖0徙FQ"\IYgur Qy\(Ujヲ!-K>$K嗣u49ST鵑y攀$6+#05mk#G邀蒜决悲桶易1Bp^py o!齡窰でZk,rZ0Hv榊 ' 0G%r$嘯N7 $Kk2T躬qc啌無ISk2mUS晉"uT%QSnrB7蝦1伎p-9('.%}3箒<`8xnョ u!UX~^,琉JVjH|eX3旻J9勠隍YxT ]NG4BL4)啓^|H+t觀渓p稈_莅耆o5P影Zf#e魑 #2M苺}Uu苫TM黄縊Ao#-frT櫪gjhq1*d\伐N% ddi,葮WIKDH+-7蟷<箙iei剤$j!郁鵜λDMマ;愡Dz{Xu=2;%b淨 筴b馮g 檠鼎 {鰕WvUiF(2~! 恣2 [j;+@U$兼D彝6EOhGB9j л+VK5\s蕈R溌'qeZ<by+昼5$u? w匳&ff攤M-2廷Jt2N[H)\=#tDws:zjv@~;_善aL腿@#a~hdM"lsj7V$懷XKM ` C@5b}V済.焼:< +5y*`*俐#^9椋6l擴*fVt;ｯ轗*n}s>K唯MY矢Qkh6xmKhsi0umy龕/g(哲S戦.D~ 悒h0罐sgTz4&QZ@L"k屡HBh7E&=tRt*9d鑿&Q |4EWub7z抔<娥額》j:皐7G4l蔑eΗ衰y矚7/翕_w?jQkM*V=W壇 =CxT; Z猫<}2EjΘOQgP嗇(=E5O%{G 歙D公 珥喩?F}) {=支'?m=;攣HF}>UeO"L壜.5&>(vKi*4OS{剩J夜olT,Hhn}ωy}zX呼絢S=YS?婢鏐f-l'hQy歃k鞜m*ZYc穴="[.め逑=0G =Kl|証MC裂F:5d*2}"(担$<肴v$ .蕩M" sΕ N亶P"= !!Id&[A1E寧l/t篠&se<[繽0]2B?`嚀r-Q F}3z徃}<]"O%彰"{炒fs菁Z{股^/%Ee摂~G~gD8_>收 CU羽9.#P!(`f =架9e@_I42QW-J7逅4|禮|n1!i槧ubHv\n9!簒f｀Nv h嫗WB* Q,q?8ZL|v.靖/y(aIy溘Vh4bmY[鱇Z5(]E蠹暸 TS %圏V爽&bU.y"97,E'棚@g閘‡6KIバ*l敬5V1+6/'P7Jn果pQJPq:.wpaEsEh9弌*m$8f9^粐t^G6彖$8NT 蓴K#1ob,椹i3xr6bcw&L巵喪Y*,U濡VO|MLGOK.腴洵v乞HZt2;J,DR& 觸csf}A棺ｴ競mm4洌TU%K(W+kl\:KkuL皎B身0n]V5h-O澪g城'MxO^>+靄逞o肬Fx'oズulX儁譱NHN.蝮4yex ;Z喙旛?漸SuNR^Np9翳KK5h8喨!gU"{嗷 w{ZrDo&QAεo9h瘢"]妣C4m+U0眼ma_-疱近2Ct属\%G(qk17~杢zAAN5G~;[村x9蜃鯀理~黶桟wl烟x\w`sJ(~BdxQt甦6HEhHo 44cH;m"xw&r3EY慙d_q&7tqD髪D奨& =(J `qJ奨藉頃RDKp珞K廸lx}検3硅"]榛Йw\振m!~T#j7~(咐7^{e6蕚P紊"|Sr胛d判Z4R#j3XZn4QQ$(拭i 4mら蚫,熹Px7r殕=@b冽憫A竊汝yZf§Qm&sL瀝B$EIHyk#v7EJ|P4(m=C9\'薺`;?h"6{p篷@H;M+*c齊hC @Cm2$8|mXJ苹x'X-7(0LtZ5]wj&K凡\ D ]]Fs@+噴(Q+lD(蜜.Q殷~` ~6朸`cF慵3#4-|P'V|t3f轟(肺.K]雷wf%|To戦*妓bg9攤!ZY*" >c賭u~U 6ZY,jZ源/ +iLM7u?/ [A,4)B({F Xs,+KPG}9授\T2PR0g]j_Fw(<,^ 綬邸~f恋嬾/G`k(QQ "E@m綴q3@s{ t#M>.\M 8J珮f(dy#m,.2DWeP0t4F] 9.0,91-}K= 艙 サV.ud9夕eS.a5jPZ (wュ3l趁IAa#I.A儖IA/UToq[訶/)):ヒ+冊 m{J^"剄^U騙'l趁"gO嘱$1?_,KK决肋竍_摩'W冽t-XyJ纐%KOHx)卅撃鯒Z N簔n"`;t/zEKH?:fw;iKBo坊~簾v=gZ#倒FXB,_鯤STxJk&E@i陦UeDos;ob?跌/U襃W_k5" 7=l:/l誰H4&齡渾/^xg^U`,仭k9h矇J8(%u L^i 堪{#mkloAL 'm縡{б@mjhZ#hq-[SU感t@%6纛/関Y5Mf s炒v\c%押DZ3 %┛Y{繩tW% 僮靆/d澗3o<狢覡8\.坡302|P費惆ls 4 Sjdx "覚憐BD)廂 壬蚋+9詒Z`\y蒙 違R/J^ s&KKQWXz}6暸NN*pH牀 q-袖PXtnZ筴_S*@*S-蜂\は]_1EOTvyO4T(c=┷2Z\黝6OXV櫛餃Mp-yi&wK5r"蓋5^牆-椪:% ?['耶 8KOx{-`gXv{- 5劑C預*IG^JV-山_(YZ"竏Zu阮B"o7曠椪邪1幻 廳@+r]贐IJWN7論G UPs鐃 )]?dC0?苧~z#>藤鎬朗S軌'`bI返.舖,0yyz跟v)QY舖b)MrbεgU仭K(7 J慨紂旒 hF2^N R0Y趁TIt陂!;& ∽mTNR*獎if)zY &J陸b←y撃6i娜Isn`火V孀TRLZzzR-)@輸8(Ε$}e H0(J&+ [l挿yR爾礫EoI5OON啾BMK&:~9^CNyd嚀eU=T鰆｜ _Hk 還7aKK&A-o1範y!r DW" c7ﾕB\S君R@幎n>/v袒磐p@撃@;Q!7淡 _皋*Q勝疫`.g]-2nUF4:圖Ouf!jUd銭耜`iRZLK=J櫺P岶8QCm牲N*Q也--k9相/`#6堀vXqx＾丱s粭牛4r蛄>G録 H U rL 譱M"~jr_<0Y i撰QD1'20gO'W<2^l殉k%21担d[_葹F$@YKi啾> S典wv9hcZへj9 ~N鰄ywG|℃i?aI鯨^w師"0oOg煙<7阿x|+)H>}-#TYX港h=VFMn&fq束1Ob顕h腮準5E}0R={]4K梗okr @1'5‖凡`陋~炎毫8采B*醴`<6rY8杷qiR6L感|it漏d/炸p丶L<"1厠A△櫪Zl &P 8QPo~~_滯/2~鼠杰~zJ蜃惧黶~~o緊型嵎2"翩2Q鴟Ha:@ ]j\a5 H!/qM%(T8Hqwc潁$H釘 Fdci五hY^黝゜ 彗萵Dy&諢vZz簽飲'5lcEpIjPNvMZ柩A*a QlEzu喘N`S^ 皴*zi斐slnPHZs) L~BV7i{6Er0YmKd"ZU頂MA蒹弼de6sq`L<1fケ叱3溶ep.]eq- qs?"kmz.&"PU旬8晉w2D稟BK舜}-b灘upd eVY鵺p=4隱!l9k I w搜`V Z]f&覓b営祇S -"8E2ZJZ8q|VXVr/鑾r/"WUr5kv7wWQza衫經0w;^ ^/bp{:q~;N艀曩H`z掣{F諸bd儀極h+簍志ox{ZMちgS獅@b7k$BSmK%rHJxf覺)k髓||-g馭$k.gg禍l'`U5瞹;j╋VEe)'ＵX^8rN3]yDf哀qic[CIEg!UH)R彰1罫JT~誤鐇;e0筍[ KrizTAQwJ髻(+b6q.瀘0V:H杆L;a0X2Lr^oB$zLQ_GpXtT 檄:Hg?め核抖ガ府T7q)菊Y9r71yHO-D∈[]Q_貅^;)E n `n S塢*5絵V茎k~fSQ"_|遍饂v癧&輌^D仆(3U9z浜r挈 &S|q*/y7aKobhTp&起y?どlw-質x`J.[ ZY"-啣WSg6)掫j H*h=RM瑁岼畭XJh|-XDtMf=鉱N Ja!鞋腟#2_|X=ηf bGM$7J+W<{gU[_Ψ概<z猶o)#{rQ!f4]TX*Y 垣C$\iGmCH{蠏I拔u籔ll+J13\+K^4霎>毘3)\2T $# qj*軌@斌,匏MQ鎬l轂MQzS`t|=荅縞A@mK勿DH1欣^Y学KX{evr erc!扎\$NQgZ黄`C茱Iv(4gg/鯀DE/6 z=(n V _I譟y荷`tDCa'QpBd:SУ&!8_沙|%D跣UzIP墮/C釖jzqF椏j{tV柮当獺+OVu-5J9(j#5vArnM*g=cn栞6qo3ie謬 G0(辰00r儲?eH{拜A/#4鶺x+e骨tvL hR&f用h升K馘9S;P 挿.ι)0m=/苅盥B^2輳F寫M6礙yOSL喚杵{8b=f|Gg jJ芙y竃PaBe:)武u V,}aw> z!FTJPmTkn蜘輸M3構H.nec<Ae{u5*ytiY^z\3&g醴 okS槝fJnMGIz堵]C*q+bR2XJ}il},QvPbc(QuF#uP黍|\c[zHfB杵K9D~^蟲プzmu戮_zb凉 V:卦xPW.!iWj4?HbΠ4玳隨% ){x-0i-k250s列縊Og@E]08撚V`".-N2既7_醸g#g軍ｑ各n{麌e8'`6y!*#v%x'C霄dO醫7`S<.椄*6投!5y察 訴友鮹@p"y#E隆 9>夢网Z@9h ,節8gljx$O(gA?t唖蔑YZ)珀6⊥)*5`f*{c  L:Du悟` Dy! :深eOb%$稟WE碁= 臘膃=dq!§紀"8(Ifb揣ﾗDY_Wb7wv`Ο|ptT s摧pC0JT/LW"颪Oz視sX 矜TE` 褒<鏝拿&ba酌Is┴,4c y噌hh岨漢D託|%e~~br但`cRVm{dwbX$z=緒講CH啾t d掎X@ 0K|2lmc)op寞k8Im振f}[3WqiO"盖A蛻y[[n%^[YD0H*t.{ ~[u}榁#{S$:峇剩担K弦VS{ek>Lt錵雋{7d杙-扶j}g{7K楴` &* d釡RELZ悠醒R昵tR{(鸛4F1皸)>圭qi#{ y*先{螢艟mtP-({轡Zm3|贔q7姓Up訊^n"RG裁鳰@5年KxD^p哂l<蛩M%\W% Z)tx.G4QU袖すLmeBz Rj^BpQ"V/PbI-ÅU庶JA浄=檪JG67<"M$L iX馬(OuG )dbHj(q <忝!埃$&駿7獄{DUy野8|腸.毋Z#$y*9,^GtIX*hgT簔q2LB;+* X %M1^A3*fXhT\KB^{, 2&%灌D買0En入tjq\dd%^YC}%`$p<'{^Oa"v7l5M[H"NkZr[\Rm申s5-vUC>]Z─豸hlH鐐9N幄T#-0W摂KN･vZs-Wb9(ZBlby框b@2k}\晒zaFSD-餤 Ｏ)將牙k藐d_E<6醴%y峻{#wK艾9ok1刎CBV{替.ASY.yd更U笥jxfF%湛DR%P-D 3@qsI齔flaY# EjAO炮%s瞰`TW活r惨E(T} 8lUr"zE%_ 2ws4>+jVkFGﾋ嫁*気?_Nw\kx妊"%鏝,{ 吠DD0譟$( G=:5l殕 'I槿 {:鏝;.#x妊iVAd//QZ/LXVE黛/P dM].SkwC!x6fq室Tq`O贖Fu!<]QwFTj*b|Qr[=(訟9vNnU>･KVR@h廬R旦v苦謙碯c >何,(;蚊Jи埆-+f程K/h '\TAL= w}=?U$V qj烟(yc釦-gi,\猷pvMx^ 3~x黻蟋U叶C3tm'卆yD[?鶉VmtiE7]蝗gZT砕D!j3m0-z'3+阻0,斡#垠s樣 V_ck┓\G<X8q'S.C鋭c\"nzO>:ad& Q/FD*Q&[彿FiA?Zl(&K|b菲R)琺l卉ｺ*{漠eAo〉喩R=_A BdE唹sC"憮e^猯licV W8沐> K-n/$Mk^v;nMKT2w*`?.&リUU拙*→棯 橡Lk2V. √o[kD彦[k%F洒U=碚制b7Qy 錻V_Q!m劔WSUsYUp Q奮仰謁^E羇鍬祈Pe蓿C噫w~燵0QGYo,邂KZh∩z=〜wrZzv 忝議tZ}%`#M$Qoxi5VNWQt39(/P+獣馮2S#万J"$ＬWZLKN6Qw福M方q4W<l苛E,4)f&官en}2%Xa=# %憤.総%("現jp{T*+jp{@Yt{Hvr孳V]/[K8Xl焜fEbo%mB+1Jk~`:{韈3 V甄殖$*wJBBｕr! =7B}Kh6x~Ψ両T'"~y(1Gy馨専`[W^詫j' fVIJb流&椛4源閥w怩oIU大5 sP _|吡g4z[Baxi~SM蒡TtS皎@hNc黴8\Q-9F=E綜絡 N冑獸y`e謎e[Gznne[7V"淒}\}|K?JK?vK?鷹召pF兩M[_@^執'xxM?烋愁渕沙?3釟泓;#咫uG26#p詢f"Y:哽HN>cvqE脆K(9HaVV/g!U~峻彼(叉凰(:yN襦D 齡zU@餓pT磑}q 怙 r>L BW]KF窖<5$x8^E}8JJO扣'寂l~xv|x2Y~^wYk^糊T坿g+E >3匫g`V "~K^tF~,VvR)UH Y!BU豚男,均秤攸4N)F {H#笏Y嗤y%O<" a:@oA3ゅ貰堂J(L:$xo'hlO$2:葎m[殃貝eu@愀Ltaj $vAm5P葎+D)tSB*c 桎}lk%2vY梶SvZEjU]型_,I2`^|@PK=^賛?)J]JK}[GI!n5t-3蚯c5!F1ktjw乗4))Fs!BW袴溝Xj595X｣唯-+#0h+`g猷[^%vUg%慙U!y tor"宍搏TYo3 S4W>r8v*倚N-f/L怩q  圜WY^節-H^J%d$^Jf皆CmJmmV*QB ^"*VK垰3P~*!z*z_K$mmL$-[Fh6lB代Z2Ci+ﾊB2W$q甅P#9xyW誨{x1かhH!j3IUjKg庁ykM軌QJd#V孀Z%┃苜2B^\ESY"T/^l" {kS彖n`j7TfWV fv{u狩Uｃ-閖`rGx侈`7:1竇楼^s欠p*NW恚jBoJQ罘:nx案H膀"墸~b恚j℃G]竝 fT6f!瘢b鱈C嗟=@H_5/G,蛟ほ 1Z啜u]運yl(#=[!C^yHA(+xg(IE K7#^Pめ脚莱z9%^RNVA${a}V3F8z]2x@pn"[:/}6矜AQ.N軟`yPUD_oXPJ_櫂蔑3類LVLUVEiZxG銓Hy竕O t q khaOHM?固be&G`練pZC/~繙疝_n^陣碆潴鄂嫦|襞輙o_&Y9o吹狠港ns辭獄F插L7呱戝=濬~u7ws:y~赱綯>yyv^滌%j1o襭Q鞭渋Z完遡tX1$XaSRdsS):f(7杏TS$'カ萠f*,+)*iy>`Ri_ne} -b)~客9.I{Rs 催瑟tf2e盍,i"蜷遁c箍0.kj濬o4L k(n1^Vtxp c \i*紳Z}銛5 v-K o 愃?91*▽81s \P心氛K@YU a[c贇[J!|L抻'6z ]u-T朖曲=c(粒~釼tn`xnI(疉G朦'|^VS~}>:%#`Dj#谷z扞6v#賊VX^0Uak` i8#O\ 8鉛G5喋&丗ZG$qgm5p蜜d弦臆m_7[B防o?{{\^>&ぅW?傷骼+Uf9俵/${椁 3A浤iCiitWvfyJc_Z .rGQugwC3q#Rw|Q2Qｰ+篌SPX @<>}KMEqX榿)/rZO^dd `5V%](凉7j|<[霓ZzoK1nZ { ,JKY <4g *^:Z--綉rkf,|浚df椣]P-dd1+c-害粫Wx士cOyl炎|x鶴b 餽m=嚢5&|uiFDD涯\脳嚇/^p捱o{靡[~充瘁o穀炮xl^x~,'[Yr貿_4JUb4~ji籟il2, ゃ=gz>`る(惴UﾌP:71OW亠>uzz霰&迫>rn|y9m叔稽l雪T(yf檗`充Zu Jt+XH辿涼漠HgM:"1∋+框UyD<^~[}s2,R(T:XひyT:毟oo%iT馥jS"gx%;d@W菌:F戳d寢%ZDgニyyY20揣]>]Egn}:9U梱蕈w艘W?} 系枕w?}褫椁z4 亢z址dGЕ)qsDitG}手YtIdLHPL!fO;\E裲J茜D3U-UBI%2`j!Rt塢]紙 介Cs:n釼}sMtPU鯲喟fuDiJ穉M-"Mjnn&q(Un崋2 y5)kUiL Ap5X語j{鮎\ -J"棘E 1, h晞tsH#飜[uX吉I$`rs-a-P<a&7z輟巷涙C NPE-A39(I"EE駭濬*DG8qJNzLstkq薈gd}%Gu WO{ *V俊ME9樹|●cy5,h7'！J ?,} >*其~?.e餤碕竏5oTYI哀 nf,h%1>jE釧EC綯:5{YR<,{3h8IT9.y3CsＰH擬薮Df(U右驀I褝+nrJ,kakCUh^InCR癈Xs4h 熹鷂tF遽:d5:z柆@+/ky7QR(QI~B^rc擦"JOmxcqt蛞ｋ k壕孩fPr♀pi`iq3It5z[kU<)葡施QTヂDなB>ES$q!5( 6c^"\j#y Q螫F=d/_18;i[穫im RiW/顯貰j=Y^f椀Fu屍B辣dL0iXr(81ToBV悒!弛瓷EO&hS2 BヘK>e税v/F1OQ|*/^ 7> C=9y^2qzeCf 'MK%GP/o=_ 0侑`.ei廼6Fj0|R^MyP"?^B=M0Cr尽m紗{BU|QOp? mTq♪式nO%S!~t50u暖$禍zn&nD-<$#dI喫G_RX!xs刑f娥#@抬z DJ'y|T講$Gv冗<遠{=泗f"Cboo据駘齒~0[鬯wEu;(邉G!8) 岡畢Ｔn~ltMf棄Qo> B耶\,.`3郡0M#被G3I[$啣||2)\F憐%U@!)\笳i蠢Y>V#N)an>X鍯d韲m-(w>,#_訪e5KKCRm*(v#jS扉yd偶yv"瘢c.憤贐5u+葯?iJ)$Q!<芙tA0横Yc靉櫻"豼金\GL航)2& nz*蹼譫s\Fw週cE7杢W.tn\"[ッ喩!t-9ZWB"j#舁蠱姫撚G浚袍Z,GUBNwE毫dOM 3k*戮墫 iGPL$AO州H8 8EH臈`bT僕jyR欸cZFA栫ESQ36$F蛆 8Aq(`)F?U?$KuD!>Q來c6A"i6A"+nU h!}羊YYl\"T!D>U惺C><-既fC跡zwQMYGMb"m肅篌飆i醢 忙梍?Jd[0鞳:DP%27柘.僅bU"嚢景h-g,,GHK甚sB+i{iDDK瘢(T:R"6:|LT.,E斂櫑wBTBUb先HF85VOB烈f(A/コ7rTo潛x3=c455MB *境(百N ~!eiT-検J^9 4{5窮BYHk;f鵬6v%"!9嫦k.KU+:"WKBRH!q s^8q踴0E]Zw4A-5^J Qz6EIE賉(q5wc\蜻杠!儂y刄窪U7&U>yw=~fQ Q;bwed羽c- D/HbE4迦-- E阜(Bt刳%hH ZH鄰J~5A+l哘(fkJ0朶w隕DY泱x[j!WAD閨%J=1 /az8L錙&sNV'V\曳3aB]J{`Mqﾎ;$蕩`U柘WM児3El艸n.(碆銓ar矛1B)'Dfu[RXL z$-.0-皺4RさH桀n彦\K.ｽ8>! 啾z8?"TW fP= [ "奏爰~k Z&1FIAJ\拓{JU7,cj!EEs\.幽=xC*k?"nWs=━BhNT.e< =♪6@6B奒|HK?P4/C"D;/"uO1>!橢XZ枳3jeXdZ21?j黨行G鍼弉Xt)E'Xn猷*/護VkO7=篠Ow/nmX.h(IE負 圸牘Z^[腔y8辯w5rA伸N馥潁ｚ0DEm dL*t狂(g +饒>E浬2F_*2&Sぃc檬@[w僥8M&O潁 }O-g 隕bgM1$吸M宇)%旄咸ωD:x4y4;I#b sy~K]?~#滌蝟嘛_?収琅斯g烝n^n}woT慨f4KAN'5n5<A<@p儚p|戝?B*騒Aby.PTs両oxZ`Yq L内%^\"bDZm [S%b<$2JO&呶8n<15D%5Sp龍_ 駮Z*9216D牴a暈3瑾;*,o+餃jb繹Z9齶_h~ J竍&;У*{F溥5:=蕃3Q0Fu 瑠蔆Mf?ZS t3 n祢If? ι蠎*ボ瓶ed!/>-]ﾈ訝nGZp^^XWV,誉=]$I共9K蚋^"ri兎畠mT:k0y]H2k){kb/WﾐF Htjv懸}pW蹤_S(v毫誚da9堕XN.8F-< D常鞳|p靡77冊蛛d%OAO^?0k勵8賜x殱屹}@7rT!pW貭Z%寝ｈB$8F<8A DL;AwZ?KnZ%IRpTK1XH蕎}uI怒*jx,E\:w[^FLH1 g+P(呱+甫e畷2@ ,9e.e2ﾊn" E(H Θ4-&pmajal5 瘤P"Ze~Kzz奪T琵艮9?`癩#R2s/CqIMZ~椁/ZZU%H~pAYzsxnO#q$$c`Z絃~晦暃QbdZ牙^ .塀VW99<1#_5 dk９di+fN[H=6禿$|bY:网D$飴R!8qX^, ._nF下2舸Xl\ R瘧I灸髯BEq紜zd 3宙､^r蔟蹌a.3A x~lh∨弘 Y`窮v!%8n紮  "R2tI40:hxV66 ア;(d_Wj 猾%P+YX醂EVw馗薈b叔,uP∠`e鍛慟z=0@|虔+盃1潁2. ,往汾;K摸 Wg" }s堂 @*馴倡L[J丞D"\V鏤Qt<V^PF(P輩 <Z鳧S#E<=0m'\HMA#p{aS=""b8L-2戞H 34[q電 Kg?K%尹P"J位3. /U-OTQy廬2,:&J wSRhc:.(踊?:=C c 罩|/)5 pseccrθ{(鑿狂aDRD扇#(r[TzＷ濾SI飛1p[)x %+Ff6?Fl+-TbKo1!m艇t}縱吶k-ρ!&P 0ZV.W={srEYC^鰕K_済 ^ﾞ%tSp.遂W7YvA#:勤U呉4@6&lFB8+ MTbdp瞰537`72fG賃F #j 撩;兇B0隅t?<[蕕_痂､X仍Kd簟< 27z鷯i2ρ駄VW]|鷙疂rw麻~ s鬚}xY?蚓] lvB6qc{Hb斜]%I 8qRg0_ O%我ev N}@(vNVCeqJ^狸[+>.啅s摩6肴輓k>uk]菽+誨oi^衒ovSGv=羨$瑩m_mOyk柱$屯<!oH=6K"Y2 \89裕bc(u籾xJ'A7f 颶e蛹i6f?iql;刊LX:rL=M"w t =簔Z５miE>>/爐N2p啀p臨Z#n_Xk蒜:W!:Z7彑VO4亢.vs[Qch"m+L|mIA 綾G.jrT$gY D^`<軫講un+r/嬬CI碵坿(hPUiN臆憚(A? 痔A輙続+="S腿N^皙jYX225FOfV|Z舩dT%mZ+痕]E$@^CPLxY8究┏巫wU5&勳<<:請'0本T:^D K-知W S樫qOW)09)!獗T牀CBl1zUWUmKa)p_扱g轆PeK#o[ k嘔AHun6y~婬$直'姥;(謬^Yh詆軒'9y)蹌nG^Q4"; jI5laZ2Smf顯o0(SOi%pStR:1opUs`n{>d皀?TdLa1E槎Cs遜,!M3鑰w驥m彗I栽gnV,P Rab浦xKsYY$PX iwJj>^_灼=鉄卦m笊\o聿#Y蝮片瓔"M|癜t|d箒a1N/]0-<\願eV忰 l2f柞Gr癢客个w_^9gOunYLE!D沾瘻 CZq8Mflp匍@yMsz.!-_>fZr+G峻8b/X4_[B/P&O<8凧u酖t倒K彷 7)c冫・*[ Qﾓ v出{蝓W6 U撥1 %AR奴Q.iTh_7.i&輧$ixUD3T僖 Rbn1s=1 sEV豚LM刀玩R`YG弸蓴~柧"(4 pu#閨蜚G'WwO#桿#`&u喩V8WkUk瞎噫-G[hb'Co滉諱X 珍 k藐侄k3kgVHY C/隔w燈Q縻_誚u喬寤C慕裝&"T~lAgo1螯 穿鄙N!霹f#ゾJh#w|"\1&9u j 詬\{pｵ@r4A(K>E>qMW-rp4-`fj呱赭hQ@戝k';~7+据B=%nsdol(vQ攀tx"${ 素gvEY8C枝kUo#.谷5 ナ腑c佼ca qk)$514-_j_l1N!~l>E稟錮 jpQぽ+沽2蒸kT鍾k/罸 I漂,jHＧ嚴|kYа+='fgW^6-P槽#G$My渣\ B0 i|t秤" oψ4\RDZ56ｬD<+ Q&+"#\c吟b鱶TX琵cZvD厭Ks?C>Du-1Ie J(RXj 椨鸚ゐ鶲a;MPcYX渙q)6k<3:-遥魯2JwF_慮S磨hcDS= 蘓1<麓+ [惡D<0 [J糴)G仟Z顫lAh髴, r) /(x;|J"RQ廼-5鰍優y彜`yb5on側{L稟咆sq>d1; 駛jNLc9P1[B%48N預R_aWwyL>|罔[ebhd*h倨W^彈FDx Ｈ＊S學E.#|j4LuSp-u民].B[J1{9`??nDU#[T&Ψ\ Be縉?%/y猯= 3→q\蛄)( w6d;k嘲壟b%W觝|LPc=F絎 %*wU(0 =稟S*R6k\Ff2pNS輯<`aB2b.6H6kjU `:+KeG0S牙!L3frulp娩L"Ypp0BeNSv邸S e樮PS刱Vo!f5T=Y%H!f私6M8 ,dz7Mb,#5Uyh∋揺1jLO>.W5媼庵:".pGTvl>ykB 往R/tE9!sK%餘=FマK,Aia\甅杆6\m惘GTZ倔# IdAmDJ]a \R4^^pNwB0錵$ 蚕r6濾*=!h nReBダ歃{*;lvj ~,芥P ^餓F*bZ疔c暁&c遶2d鳴-fttE=樸m$酌.描$`-\!jv0|gv1cy*q8wW^>樂山b] Ys6#-a綟$ 艾xq-.4ripW- n脆w"5莱蒼:{~靫rW使SWZo褫*] Hb&9SY*y鉞!/隰墫N^3淀LX磆K=sRf&QhaZ7[>f4蓊 Z貅H;願5D%縫K z <-[J民V)R m[}4/狸R2hAG蓮enw沢"Kmk%r>qd?nkbN3I/僅(fOqz弁8豈`W87g!={a黴:*嚏l\*'r_K鋼篠a_唸X0 才4rSz鷙y亟N~T朏O h*貸SP }権r&]M簀A唹Wk-k^4\D~蜴n$RE"+6O[)d'<僖蠣劉| @zan董g04,( 枇C>UZxu-s-U33P%讐G%8qAK[名&?;b%ET&Es;X拓&t3L)鉞幟?S,~#GO%惺\8?b~h;KP**,\蟲sPb鴦侯aq!q陝YU]QT%TB?E 3YnU4青 -冴y6o.fZC""T{#$2W卆|MmMDRbO%萌%+=-Z篁AZe]奢HIHy冱寤-+1wsKTE qj├8bn,V\p}~`免テJEG EG?Wj 癩{号EJ溥8#ｕ`9j#uU3cy* (疔>`莢後/箚zZY%"[Tp/U%P\π|[葵8q檳"瞽a"隣L^LRW$4Ｊ4zW{]T+ォ"Y}禎T-:44W皰SI?\t /[拳T +RP0湯I MVU}UT)T0 /M)瓸s鳳k韆M!0i 9仕SKC9aT+l6wT畠ガE9呆Xqdpx 獸wPxdy)Uu7rガhGbE2Dぁ+JpeJ+7諮2咤楷}0%a{w凧Esbh3}|KL(eF橲91Xh皆"搆3怕"[B*\!/d:>+蜴X|480 I邯DnOw喪w全 晞%x!(Rt挑>.V~賈"}cG蕪蘿w#菽c}墜 Q/m泪q汰{i*(<♯Q 嫩v苹5D11OdM?+P?97對B碯Ne洸4x$oy"耗)4@ N傭輛匸弦@yN -館D<活v/`T!np柱bF.vbHY-I!DjJze!メUw銛R&T慷6粉}z)jSK』agV'`几I箋U 復mGqea}[ tK&du$~' W  A籃+*3{eeVU=%采 ぴ\{wW%<坎2ls汪%=# 69Y縉~蓮3pR @E C~d`HaFP窖jLqs淑~醇<涎^%Uu81 か棺,Ko U5U*NH>{斯?蘓o^<6<lマ檣OO嘱fn艤>∂~c娟喰襷_I鮃 z|持?貮7_~髦'尋u麌$~~#Gu=粳>go0ip葫Tl{H*Fm.x!a,朠圈Z8SZr托-d+63^罪贖0gKT嗟AVKVg_cィV6釣ZCU$Lx4;歿穣NNkV2濁$侮 E1(B劃 j=|(n"wr邵もeP欣D碌忰E穂 jPX^淵|M筴vP,/p8D- 貍YS骭??`@R<旨 Y%!:.H@F#孀 涛?$BPMKYΑ^,v3金委杤o7烋>znLLGY杼^In^K8t&DrSp粭3%Aq侮uq`?: L*Ei+ [)4H叺)]^ 簡R`muk[@? .c韭縻彪O+5*1  <惓@臚I*n燗Zxdb$M%*hIi5-L^'}K#IAK%tG]!h;藜h!d+boBy耿P#&鰲=!t*]vK0n帑z0*AQ#M[L飩k3Akke,d^'mh(LJ煩灸Rd2@KNО}\zrN橦姫j~-/Cn4|oZY U)qk@S*$b4pyfyx>'XM駱Z%作虫*A&B桓URv鯵v7E|o%F0z^S-&J- j靫:~箜'傭f轉sYe昌鬩g??|齡嗜＆耋圏o胚t+紐蜊沒勵<詳nO=\x頡y0纐o戹sR!{倥X蛬$ [%Id!湛湖値蘰IY巡fclqd>DH定寂5<;paN賎s72E. 蒸 xd袴mi6稈∩Wo|^鮠k+p a^J鋳j掉q1mHO!8啝RHW瑯▽訶s幽 P"0/AHwOt-NFK;:_:GUsDP叶Tv5T苟_=耜'_f罸型s遇s纉?}徐_~?X!iw:b~ＭId学IkmrG5gO?3j L|埀3BT蟆zfQ唏%溌宣D9E qs+ 叢7A-)+ E"BA =$Kjm@鏖[pπ@C }c"パsgrBK稗X3)OΕ~^洵t蹴YkY]&)IS%胸zPB私%H5%7戈垈AKK#/pHhPr `贈{%lj Lir\%~ t専n)km6bXHu龍t4‥sU3Io3CA 邦%c撒lZ824$叺4 CwnKBRwS+?[理VS\'/(Ooj cr%vtS塚_6瀬`鉛fD渭 cO$ 2片灸e舖zenmn&gy (Sh制mkw3\Nre/播n3E y>k艨aで_~)~|SVfC%L+-f%U5^O=k6|!M:zY#亊\$徼sJt#C2"サ89Z'03= 9g 54I|Ct*=/>(^+路lm-i9G]"\a刄\Q&ZM|SeV6.芭4N¬uR ^{*丗Uux/M$RaZMゼ描DrA +LT*#oh OZuV油R娉|\知KUg纛オsWU.U_*!捜5(Re?0 , n%V徳u< |郥h7ZdAiF隆p@漓絳kgiKSVi喘RM.,N鵙!@:ityO"k=HEwY/L'BKSeDw6魏\>w} #閻歃6tgyVz^5:Q=bSi>稗o<*6TR无$N稾$/uVqfi84:D[Pg"-(3B\Wh^8骸3敏Qb6K:l５GCT廴圖體!簷%84AqmX&匝t|i$m|`u 侫P#班{P廷4ET"*SB@$/s聆\$ndT!H=OJ.Jz竕霖m`|ゎ^q5Ys@醋譱9框L締 ;VRvUaＩXK}t8釖;u,魅'暉D?S鯔桟c(%YF=汝J伊i逆娑ID察"揉0党{S譚TE!tG癜L鞦#oV 膏eeL]J民A蒿T蝶 o3;gy}n=~94H鵞K^B幾X kC W/毳呱檗i B0H4BDz%xc"5TF a RM:KHI椏椦+筵?z袿_愁!]智整麁!3J9iJD書qT4`\⌒iM鯔].$i5褄 v!<`nQoTb筈K. Q刳i&&xQ\U0y}U-飫>c}C0Sb3~cBpol/A瀬煎{St*RL]矯HO[q x駐bRywE槭/3r銕yk1;隲孵CU*qRqZw/苣ぁ"p1PE_"8[k DiFT篌(DD甜\耳pD|+痾Eei3h亅Nl^Z"0%T#02-h)刮`b篦g3累嘩-肱Jtx` α* w{Gy]uMCR/9W;覿Z>,wZ侏hVjz&c&Fw&Gdhix*頻$l#U`?'W%w`^VS 5=o絞^IB8VKYRh<`C#<xs~0槁腮hcg9*寉N/BbHX聞_sn6Z8徙;r貘單Q`KdF],濶R^D紙Ag"\捍樸KLLOz袞?詛 |+鯱>陷/塔3MO--.XM"3tKΕ3堯i0l`$@B:IRe@纒P P'i8]ν}e#d ~;xAFITphqJ`\}p@8_jJy/廓７尓Q粹 (X*0W冐y皚q6ＷqS/'2PwJBc搶]VPE餃_u矼F鸞r叉績UN"C_WUVUOV嬲昃_Vw栗rd`妣L9TnU椡7]紬KdmgU"+ -磐脯綯-飜wL5H&< Fw(&F16嚮阪!+筴3鰔!#Hkb"%=+J0"U&n簽綛叭皈慣2敵=2Z5*(a-"kHehtN'lЭ:eGl懍鬟vZY3r%JsF.悌:z+Z麿-?bH_飯DEx5募~@K箴9BT$覥 "譬Up8*..裘 ^)y膀~)P 曙VVE柵栗Pm牙1[菖~Jh8kOA$3[UfD<(V/|L<謳\N|{)$,w?}靄7GQt暾v7u体Ps滂A2>Kj>:饐/qT6韶H=Pk顰]噫]*b.夢4 陪x|yb稚uf-lSaDME!sOhAQ47s&諛d晩W:Ifc!NF$|rG~孑n逍蛆_})c派Bmv}%Qz\ ik<Aj%^Lv確(?%：lf}\ v尹F %駁y!/$悍鷙m&<2-nRln)IS蝮yi^榲h`)價裃 ow^_'8臀bM燮TM,冐枯Dvs鋸翹?>豎o=鳬 寛+KM^E#Q\v$Q]EI0fOK荊'a[*餘ヘal!/xa of"_H>rA~l.式舂８DHF Z1D9zV{Xξh& e $ O{Y{\E^6q:G.6ao-g3Pq鰻)包ET+`*鏑",a\Cz蒜O&k(决O4rP!履"名R*/Lwi.tD\:BJ 7@b^J{゛Zrk畫5+:1yV栽6P2リ'+^~nRR昌P盖7魘.躰/3b=Zr欣X斎`.l営kH齣ミi(gv ^8lp`!G~瑛%O?豹*薦qhy|#O[f滌'~^4Εれ萍C% 8i找Lz反?j淪險i擴(Cpu]DB_逋b蝋'JAOA)zM椏vep"Rhう簒o_蚯楫{v撼7Fm][m閂興P*lBp8U穩Oh~N(瀘y靦/椙RJka 輹]E[#受A漓闖i~zh#D暫SUp7TL~M`47}rI%sZ#息Km "ヴ[:r wj3/!:m0顴5畩K 驟[肆dTt範MB@ ,5?s,"XB廸nHg7Y5Ci@v}OKJo6鍼LNDp鈔蜃_>yU 鵯癧EyHkk~ v~Z喝U蟯j#矩Ot槙h:舳緇:儚hD几; c)pSD` 1'D諺Pzj鼬瘤W鬟=7Y^x椨DT8KPT^Yy)G|A0g`oa閔鮗]mXUjP檄*/r 8岡!)S]0d増P愍剳参m欖V貪I{佰}tu%G&m& SFCV>炮hf1Y t旦f6Go9Vn陞梏?htVBH比?<菴諜G烈Z[OE迚_疹o+f&Lh9鉐hbXF8飜Y|R~Tl竍mdV臍s2C枚霈s齎av(:%彜:家Y[Yi#^MY9S+ o;L帯OQwUP8我'l=fBhG% GK#+9H8UpQk賜"技y#d8絨Jk釁屮GwIR56G]iHb}彩2sZ^J{`yJQ`eyH!kK/M6 EhYjP'+釉Z蜿抂:1ku\aWu\ l!Q=HUe夢 %jafYa;B'螳i憂(r礁礇T:ｂ H^-PmP唆PU %3m'+$&0A,:A `<5OP梦Rv>9r+YR/'v常_ {M IF %R@$n0p覡%d啅@銷p0S z鬥居 GwxGmj鼬B%OJ{7箟蕣DaNDsV08'grK~}05(bA)-∴双鯑[C zaM%GqC筮(] WUpEytg椒N% H8'//QPwG\倦ジLMOt,, 0Fvw#ZggE1=4閑 9仇Q|9UI衫担hEOV5/ P馘X邁 +鋼!W#T 1GPenv`q\7; ur熀n嘔.'jX2木sO溘扉|齠_hK餬烋嘱Wo^/ 師帑sC<Dxヾウ2g雨oK辭Ex'$XI偬,簓|d~追2浩Poo 5K"5I1rd迫sdIO\m vq府旦./椎 獏B}死d鶤v9/sX[/~e{&四s&遑V膓.Sa< $髄IMT06 世Ol摂|賈. ?蛛A9RGzM 躯L! Ed)RmA1kbS捍ZET5,5R[梁LV亢(Z^^殍苔SQ-z脚k(1g@躬p~r*ktmT".垉p.~m,*X^鋲r^1L酋靡ut麝i"@EVV&jN6蹴仭仄慍gTTbs亥rs3R#m:塁$]Vp躁F\^~LKP贋Ch[匐\忙N/.37kYс;嫗WWI})nhY ?rq4BF鑠 .Tb]ijY侍P柢g紗Eg_Xzw洗'=lEqdn-苣M.y-"賎4zk蹌a2*N>|7QJH- 迢@]C7褪@/ 1ｺV猟WGgjVojwc[衚}HJH=LK託y}uh Dg"EaaV%e&U袞禅PCl魘oXu盃jrq悛QQk{6sda!:+Ue6R香0\Tda/U%J込" VIBAF跨iは校齒9W 郵`_m∵8哘@+b?UпgIbgI|F耻+XY 8:$y寓lZ0W+K KS>"2遲tk84g-9wZs]蝣v 0ktvpCLqS瑾7"(EZ悔;MsXC\0 毛蘋y*$<8 W硲罘5~hτB)Yh&%G唸#:jYe4)h沚"cj巣QCx 2g萌_0RK ?v-+@S> 繿1鰉$-c淡-U`~e,qi.i-F滝%D湶NG炮@\'b(援6h腆Bnz5js(:4汪cKn塚閂┬閧~鴿_傅J8\C制x2l&剄qn3g%cS軣D.*HR^2@9A倩DO~#?5Y取#儺{>:#Q6替-]鰕G'yIHG[/愿7ｯ;ヨ;>}w0$轜Am }`Bk遷i0 <分裼{0暾盈'&J厦{wG%+95n島椙6dc皹% lep撒% 2I(m7Fw擶qp兒m)R}r![)沮4%@H{vQ88 T\EF鉄 `[唾vhn衢Oo雀!整観/jv`拜盥D3XJ晦l&|W-4 豁ZwS`#h_粮jZ+6>W赧章S竟>'楚GZ 冊帶o nUタ 泝jK 酉6 草f][N"柆.j"d/ YHETSnqROM34 @q竇KmSvrn{} /8X淫9X粗d a~ZTROZ 1wj}-"}獺(h揆靱|d#8g$`瑶3@>默;JPrBH=E2刀MQI+Xr3Dqne矢LS?鰉w^屐鶴K薹w$反N慈櫚A]X3{}濟g捱q耜|nч=j硼"Up;[;GQ儉K((3N7/-.yy~鼕EX3h!C儒亠jAUVl罘,B$i =f9&3s].9宗刹Qn侯O }t斜〔7_C^氤x|"* n仰gT@ c>: :) n$ T$卻XP pl竅 \]nL"ｽ鷂ka禰g仟&1..1&'Q=A"/驛h%#5%2o漣Zw問%6v攬mkk 耙Ｌ2茶gb"3$l~(T躬芋sV.3.td霓U\hR J{  蛇% n/m6.-]菅R7T$縷% 0M#Y鷓海!@!,Z珠h{?>8迺今g\P#|-d%C zw-q^`0=g$E}d ?tb_$~2;%}ζ│_o俄fq19CWjfS% 2R9Я\&e<7q訥攅O閂Hkh齋YBtQ2t2DHfTu#嶺z]E&f!融f/KD.C.揚醪 嶋擺 gS D2tvAvI\x窪碣B/Mog+Yq5LUV Tv9L痊O攪lUPv8[嫦ZV蘇\ [wH|鰊_}I舎9/抹S1>h.}xo4m羞j@hT? sEEbpsB"豺h1滔C=]黶q"素No嵒蝓!#?THG>R NUDOLQjz_b7"|凖Gm6枚p~\f濔y{>?<-6楴狛[lw裾 {Lac竡濘@E晶}靦[@+町_滌築燼i反m燧屈j姻3gr崇gx-E砌 gR詢n(lBQA 'Kx j"LV醜(d外[*ks,>yqE蘂惔.*0W壤q "者!KY藁7斷燥6 t@:I$b!T][a Sw-y7MF8 jiwEF凹X0ygLpcl-Re@K+Qn8[h仂cdQ%49r5{T n1\mｐO^ @奸勢 ^\\% = hT}BT p $`/E喬fz@NE`NgS H>i岬"`o#;ArUu遐[┴譬k x〇hO%/S媛2 几頏WHpZGc;W<[-jLL&noLLcOj江%2Hx抱Cz!Gf誌j#yRtS:#]t郛鷏;FX]J崖6dah, 雍(koR%! t92傴ef.<:]3I^j&B4J寫ipi01"$2xkqp3(T厄izO瓢%!~[0:憔:B^K小^9體#$(屁&c cOke∨換Y14if轢(澣wvdr4Ey`2x %&2<夫D0/(t4+/Y9 _&^x衰YSh覧KQC6f270瘢xM{隙t脩xM{}wkN害~曇禺 j0p疽r#k~ 筺i3:u!拾9燗T悦(Y%:{x0$r~i祐0{jZGZB,<^,Xd准GPEJZ;d炒椴尠榜嵶婉潭M羶w句議>z┤鯉Ze`5|M^ZwS[1huEq供aTC&T`g5X{U xPb-[4ｬg4B{(Q嘱#sF<,m[廴緘痛H&袖keXCpK ZT"8%|a"2S5+qEm&q41%2{x00雖淘U蹇&}:mJ?K紫窺[ lQ&悩.M悩s[枸 ]4EqEq佚L 肴Z諦w$`LLR窕{[u_87,Zw<祿C E}ZqMQHm瞭~)qヌW様崋 So膓DL{PWz尓諢Fp\[tS插_-ゐ諾糀gN@e7f?l^bD詔X8U?2G糘bVVU5H\#]=-"8G7&襄6aH∃Pb擒XbQ+#4U.u^&KMs43XdyX虱官挌3Rb!|U|!F%觀~t婦(?魯;d/歔Ca~*B$Y Pjeウr!93P^~cJ*<\\KP cJ/[亙9s左1R {幻Hj隠mGV 也.T-(1X愧3:+;b>y %(а胚~K(劣K準`鯊g[n~+琺釆H<Y fM o:宸這y擁^暹Yp)t+>BtZ"H鰆J送訴= }"xJyj,Q8\dz3]$y:W夂{*p`Z3 \2C8/QC%D4hlG4勣X珱[%羣)aVS4v@`剿 "aof6濆<.U-t罘)a9puy税8 1情09$i:f8F蓁wd9X[]第|0%|?lgQ瘢wo燼7裾_GH蕈~驢恃顏_冢?}D?{cUh(a[ueeX>Rae勇h貮R巴E譯1GawEパ!專濮"DY逸Z U6蟋=gr4 ls[C 唸E%;D}p !D渉1B><%>p<(-TQi昿 X%hE61C^]5L9br榮L]/e}弉2q|8^{0vAYs}5 6v慨[幤2F/Co靺|B>yEgD鯀!:!曽@ L>+eP~6x,MMn:v`u#+列]eIi|爻9s_R徽.{m!8$;zq蔆棋-8jDv)BY0jn善[Q6Dx> 欖nv態0G Z棣oT平c3cFXDA I|_R[w-NeIHEg簫m5R5-;v生廃]5葬嚢^\k58E@jk%<$T1Rs 6~Mb$_r王gy<Eyk`\5pEz$弼^D3&E截苴0\en8"9vｏ".糅KE@C32//_E檪2./+fsQ)>60IXap8CapEYuo}=yO*(%N[%W*#$c%6WoMY>覊?4K母Ys対#_蕉k烋~>愍持沸yysF+x[)m愁O$z歸蓖a@Bf*Q?GIy櫟l4i冨(&:CI>韋%TW?g桷m闍S両pkGc+B銀%Y=s&d|于竅黶/2(匈wbfg#D$_K(~^Gm體侮\8:Vej3*sM'R副2Kj 歐E4 0vfQ+2_6We5P 斎<.B凾 7YmR|)EV|R2kbvk颱堀en5 虍QVg'a蹇梵 iQr9(GB8 VJikw,G9∝y羂Wrd g9$s]OJ遠q8[鏡)z~G祺)Z炯媒-獄 u(/=!xy霏KZJ'噤坏fCL'1F獄=hEZBz!QP臘y4&7e~0wkDG嶷桓Af{>32 Z1.>V侍@指l\ W+#粹<蚋U|鰭誦e.RUB{]zF$/ｘ簿50淙J裏mw _55 `B 將;vJGP( 腔X^魘e'p[`xwF玄駑ecq )bP'棘Mf摘aYF>1SSlE\gdc,鞐L7|K徊9}簣Qn*NedH5偸$a7*k`/]%=/O%疚~贖"隷{ ム3{_祗XoA.o投B梧s$] A>帑丐G涙CSC%$~-L⊂p@_M瓮鴨c>彎a@NAy溲,{u.q抔d 6h6逡尉X1.})Qﾏ}*pyH諍P.& ,kSfd>6cEh整a\=e@N匆O呷r&T‥In>艨Ti亀#^,輳L dm2c謨疽 ユ1!z筆稟6@YU E% :a61tF`鮓YqP5L 颯kt4T8%aE3!8誼'圀B ) 2$s刻1:J蔚2e;鯛cV綯貶!帰f/2K籏jUFD%BYp7 !#V=辺pCu品悳N∽rB忤Gg\>Lr?Ku:j7F=+廬@g滝2F9仇粮.IQ@Q12呼廾 /杰`%蒟尋s_w?O~IO@ B KyLL賤`%j~HOmD(9Au(Z1"L.$*%娜q*咀)I闡k`D第R]T$良K!a4a謹畠世GV-RL籔N 1g!透[ !$Z|QN{^'{B#川麥my*c7F _`N-ﾅt?X n3ﾗ%,%*確陲JB<夷?才酥MhL r緩iUq肴>V<r]覽帳eM)1f y箪菲O剥讖蓬h5jo[F填\z袱g+5!i嬰{砦Hp絃u瀦TN2O  eI]2BUL/;sgj`棹Q 吾 > 軾濠 5皋QJ~9b)Ly'朶*諫CaxogTo h驗0yL,Cue@&eI>ｾY纎oB埓lNA^2+RA9薫e-SA@jkQばMｐ@nPF)zw[K"魘XFC=駆}N蜷Rr^Q$Jp|I]KM$[]瞼淘5jk]硴A駸~ftYc'ｐqoy齧諧懺Bqau珞弯驂o[sqK7on_])"D27屑8)\萼:x]2 (3alR8C]\W\0uz刑4居Pxr0岨瑟c_/綟kv`+r1宙NB浸q7H活地]=\+ !;ez 5H; =DiI!< C厳J拯; 濳Eo!$T(7b演m.ub na$顛輦}U楜酵tU贋 螯m]|p瓣&@wy 瑙溥)=凸N'B]p>(樵偖幼z<α<>突:ek閘:楕%KMQR祇誡v礁鯛:f$ ? Hzv=\e0R~隨X<z\マQ$)Q0(\!ZJU^癶pATA +3vERyq B0c9:6(^_=}}\$0恠|ywC沫o%uC/ceM巷揉ils~頑\<mVo庸杳=凝[({a#箜 ri!鍠e丞($^6(t 'T N $d:ё>Z#俵歃袗垓PJ^6j 蜩&"{w4 P\hN){, 8弑=<v#招U>p (~ bq仕8B*]Bq殴貲IY \d=)z|#)(G1}#v.RKn顔 `C_化8H}5.c\z畄P脇e#%PvVQ]\-庇mv 4輻Bz<(鸛9震|&ZY7.Z倨КLs# $\藉^ 呪L逃W3 /=s昇^e;GLuz!Z4eA-4kJ流&`e +Q96c9ﾑ'pS{^蚕摘o@ T?弔Y|4u.93悠NOj5m?GqYC[勺G珥氣B慶{%4={xgab馨aO8N*{B?d 蕕奠~J%墺"Y:@pW- 村2堯IdaS羲纃4C磴xW,'篋\椦霸cL、&y麑Z'X7j磴O酎r8>uVNh宥 綴^R$h2:n穴N[u膕[uトJ^dm越H蔚犖eｻ&\!-~學]f0R7|$假樞fSШPzh)i祠幣u(Ms塹噸Y椅p)7 y}P=z5*肥\] 起^$n k 巖i2"Q[:K7R$眼' bD恷lA. ^8cu2a+z t5evNk uR濁;蠻J)~=tTj殤Ｓ1=准\p壥廐へRfJ繧#a*葯,膤c/aP$|JA[YBID )XV*UbWFP NMJ"eedplAぶ稟=Bu敦gBqytz4噐RO369\L4 .筱?wrU雅(H昏'PW吉Erf=kQ0|u>保`C(_V.樗T#醪 PK1tNJFAUsrw&贋\@fh\gv5.Lc7.砺\悵欠+'汢$蘋bズx斐a8dEy?Ｙmu1落a貶頑FATA^8]9z8(y$r迢i(4簓('姶1yi煉GQP28躁>g]Ot\8!A1G7Y充礪 BnE弃Ew/`1^顯鯨罠燼 & K駒M)z災鴬簫O'-ノ銘RA!(ID6文uAm&8u[吊.鷓X.r25 #og1r,\aXdHX-TI $摶Z:{瓮dI$x]O麹\==x#iw[#j-nZORSn; yB0$BY5#3皸Ly囘\)@丼Yb@&/罐忌rjK)<\lV'O"ヰ`);9 n)ps=UMy98'3@"`螢XX\UC),1肩m碧8!emIkdv3Q_!.0NJZ5Y蟇昼g朽遅\9tFI }蔦Vs;(eVx)疫:R滿!3 qOP生Eff\Z諱[j^)B[2i2mu<畋S痒tce 7ソ(cy$ k芭~HfY pEF_琵6F&QG ^]Ts劫Gv◇8B|A酷 2g祿RxA 脱^iU X;?┷(IQi籵D+VJ|鑾">1e46U磔xR獻r4S憧aS&y覯WR8Y.kiU^yB&3q|ε@x^匣sZl;D|vTRe糸38F4a桑崘r+i潘fm冤？kIlmn (qr`D!xPFat%7%a%7Krsi3!蟇)3UA嗤tG1eq,a估?6e&)r!!P,cnk奧儉h(Enov/]●^`S:\zy糴;h 粧Zk]:銀$y/tM$|%A&@蠡FN'ゎbL#= K&tPv=肇78*4]&]RJaヘ&Wma岩&KF([ d氤K孤P8ryxD皇(Y0"+zX\yxSVW|T7翳煦$粗9雑皋済R4rtyF豹A#^#呶(x _+\N澹RM 3**k7&D聹vGY隸;F鐺X|3+^]-:陌KIm9wz)tc慧?1{`勅'$!qv [tf) B鋏~" l;)MXQ gdf04B;p $#AdgNbC\vdPaSj聖(鮴LV s<戞9 賍5N%( lH\ 暫)muFDdksE孀q]M泱( l. /1} Vb]Mv童1ui/否w?N{]~H (K XP琶.sP.鎰Qc跖 pkWs|JSA H8勧Cr禁n*g8bG'~rK冉Rt?p+削穽k-叮 4*rhy讒皐+mR) R(U踐N仂s澗ZMq%nP珥J 1J j%-s蕘d%SXXU彬\z覈@Y&葱Uku_r/>>XMﾀX wae壷Hq匐kp_Y懷P巨ISrt&氈^`隷>9纎c_"9童垪\亘%V牘[(‖貮E\v#&p#染FF痕%Hpc亂tWgaF怦鐘 嚀PWdA*K教lA>\$静U萌}鎰# (p裨%1{2芽っka]M5?潭PvC濺筌K{l占B床 耕=&hf/_幃jpS.xFU2嫦7(3@]UzGu.^|Jzz A2vG_Zw..偐rxAo,WS7pk俛w[Q3鈕qJUmH害fLn0^汨驚;[X JJ`MI;4|[s_u3 vB旧鯖\徴2[;)rj弄tMi?Fa碯鯨:C8 !w4q╋ジ俸7xZ蝓;wt~Wm Q^ B@4< \2!q0吭[翳AFAGA{Q, t3 Wc牡 YuFL尨X詐3謳vykf`jaedm賦訴柧j\H苒yV@{_G阯幄+DN*8[<orxd稀~j=K\[q吻どS載Y誄竓sI父w-Z]le-3O.`]眛纎vG雕 Ou20追4]a,Mggf6y19通]RL[礬hL:m)箭F\nMI E)B9北c$N[w.郵毀p.,拗`fu崚03:tgyl?y[l/M/燐繙<fYiGOD wo h裸.j稠壥 2E暗iy r粗! T'ﾕ(]c嵌(r9r <&y頼~卆Q tX>$60K瑶仰'k]幟-h/(NFT睛rK貎\岡翰`)x*翼痘V,l1i{ _U/L875腟6 V +K固#>xNsZf\Ei6咤o~c6+Q!8_哭Z?~tFSX uVム&`PY2x碍遨WG9 乞#RssF&騏6w}aV>I9w:gV<1ahogRT^禺｣爾B訌D項z俎M|椶梯=鴿 踵n,MDlm邁]^t-_ N痣C>$#m!Y|Hu9u蹟C4,;mG2H=eGRDF､$\vR藏#)I礫s()関7肛禿-Z, cTV邸+G緘!縢cR?if2獵U8+F}[1K2舳a(A.h*+%k>/#z9 T1'"Ea >Y69RCJ%:i-V兪,$+搗Zcq堪A|Hdk]7圸Z-h3.:l 6BQ01矜&0}mK秤s,扁srF99〕味pa)景i{i[M8 %\頁s畳iJ盍Qt a*,]9ro(>hzXx*+}1昶,%M泌v9m惟|ﾁ{<)r敖 uS傑\)E,)¬k茆朔档H梢 靜M(j' Ppt甌Qh ≒T-∇4i_2|臣G@_R \86嗽飫C觀H}py\]G@P:"$ #43=w2Hrr_肛$|防纓o9~=0[nI-g跳LVU/濂褒 觴F3DV6gT b7SJ幡!ァ失JS^i頑禰Cmﾄ) &`衿)F`:{\麪OLeldse qaU↓Nt 4K1遜aXzkA-*b{hQo)綫rez拓R皓_sMy貮uVa&|VaA9U3 cMHBf\f絞lu C+!,y}[c廬$腐樅п瑰隈4家o3JL(Κ]):{=K9GhKnzJ癪}u.2Gokw.玳Vg探yaF =9|%[t菱K5~tba Q7ふma 9T{Ls\遥c袷zt皇 {`庭rbu z33VE z]OAi8Rlbp陬悸T 痼桿y8x.話bb6<C"4烟粘QBsQYU絞.撃$aJ+TvzXv/cJ13Wq&l_鼾W LtH鬨\朏o8$鯏u1l九;5扮2崖F5視瓜:瑛Sa^]Lce作QQ瞥泛;EC倣&*jV廖ffweh~玉B般棟&s警)Haf[}fO* 高\af7M3[ >[L⇔3[)拮侯s2y贈U |ｐiA6姑F6!f9}f-覚cJvVOVJ\<3-爽4kWXMs邸[.Q_M9遑 埔LqUVn9L.AC褄mмX K マ^-tqaa僥游3BI7S}2]h槁I"咢qz鞳R:勤)t URGr"8#前.q情剳q!)hw 6^I_ 黷o恠埴跖癩輜]驟#]醜\n蜃禹77閙\y銛憂W>産~~f豫絣抹sX_^迸%W髓B?^^^L?烋~z8x黶(僉v摯[j-o!e炙諂o~H駟*謫涵{辣緲w/他~?xXooYwo烟R廴rgX;RR唸iE偸 t$昶=+磊喋晉ui槻怫._D匯v1充{衲h癜2J欺~cxy驕@MlC+絲z傲fZ>O~yxx隊-7{e~r/祫鷏ony=A Z%=gw毀祉恬$鞁!m|陜稼OjOAYtgk/c蘯載<靜@HQy1_+疆~向%Y阨K此_{聽芬聲6抹詼Kd(0倚+叔wf}x84sx>|N楴m髓3#s艨!-QfeR彳3夾R竝衒迫7$ 鯣},o_睨驕饑閖萍蹕ﾛK|葬鴟譚W,&/]n莖eQ幅簔箒齲觸s平FS隗3潁襃| 趺4癡缸4 en/xi伉{与乞ZqC'J范]Ocn~屎sLBv _Lc6^粃zs厨_椙v曼]sj鋏鰺毯q祚鳧3{H#s裄閙.^:ey$K眷~諌蒜E茘 .{猩eAY^~4sゃ7o^a0諧蛻治E;頗罵_]>m;T7鏝裁経4dY0顰qo酥t○?sywd*>uth貊何RQ >n>mY芝軸l^]鈕闢T59-sIYk簑集次1P迺q/E鯔郊o_9:桑掛&亅危o0IG#~W{^ n椙80A親W飯;h}5Fvn#m/3S+_Jd后 !pmCnGL0-^惴剴b9}c/g5濾汎54甬k搭f/inK5 躱唐 7dng譏Zf+价K 6tx2俊?:顰詮育/ 嚔桓歍Vjx e|跋纖LjHv改yYi#%ai署 #0-Z帶E-{缸 _癸}p嬪;沍>Fkf湟/Qlu慇n暫?DrPnr憙>//O["!k在]ν*]゛w^頗vu剄褌師 U對=蝠奢[駭c~ェB_?s~; r襞 y<}'Jm£G77 y髷翆On悁箜計~Z?_H[鯀*k'銃>$8ёiq(F?F柚p(R;Uv史ｇ-撃O')杪T 庄Τj?/d鴪營]~zkAA?慌計?拾^Au>`k&}βO型丞5祀鐓f^;AKrk=9E^v^ ?a吁I7_=` 瓮攀枚2[ec WL5含錠訝ya合uv Z+m輦f6曾罹抜V'`JG]実8逑d"evn[E#}|0yk8'/].tsvVL M79c3Mt鈿N'm,濘貯Br:そy(駱=(L_袒E{6吶B~k'p5p2,x\ ![Y溷D柯n`DU墓W髮=邨?|齶o錠J)&//2 v u.AY雀?$.?=O4V/熬К1DmU縻Eu6竕Qqep.y%0_兜H稲s2Q漠柝*W蛍閂; 最[男瑤鳫l?倥'凄dl/閼鰲m43!w{;-m耘隼_}J'^Cv遍sl脩xOQ頽誰4 OkL駸72)>!篭婢${ e$qm!Zh徇PJ3fX覚$ejkhI.9幤推XN uR賤嵋u俎B=榱Jn嶬^'F%欷 Nztg:嶄zh邑 5^x$Q PI淹&G?虍嵎(1FK)jQGBGh]@c燠M:N黌xo&~{X`Z-R6 |H`s/%Y盍i村A,[c`T晴b/!M甕7鬨dy囂WFU贍"a (EvnM癈o;篝(IQS:8\漆CMKJI50K 8q Kq,HZ0Q ;`"Gn{Zf K鵑Z98芒}T7′#!KX?l覿GL襭逅:u;o[ 踝(~*朝5襭尹XwItS嶝`ｫy餓wiK#F>\殴Hp蛛O 5rNOw寵Th敝dL;d=Ss52@SD鉾CJ憎畋d \^HCy`ecB)1キQ 土-"3[z ‘>物gX)fF]90zZyS:V229o}&s(46鏘X延析T(&勉x~D1筅QO騷1 z4R!deH#^ZU\茖eV-l6B}HG&!u4x.^F冂&VOt葆oubsHs 9骭療<9FVFTYHx卮Z6訝 ヰp,5FMkl*F{2 X*KM\ TCT嵯%ys!囮zPfq舗紐Sj'1$sR0曇待 2旻ツ距0堂+6闔嵐0j) P"FB磨惱BcSPVqA軾UNくa(xq#WM絹墅er桑‥.g#$ }].(E O:3p =OcS恚R瓔r匁犀SM]c> 76'dS;厘)7J=,F+7pRSK60:3{vcs.\!wh餘5 )Xn:Xn90|H薬zD9ふ `H櫪Aak籵]CuEeY埀g;u`偲}f={lezc鶫 v=曷賠Khjぶ籀m>3}bに售i9!MW>i翳tK J@厭 E#)dB(H/(MkH哺e0G9M3W)報 {琴,ε慌K[3仮dOZ=Ji造硴a4Q#｀ﾘZDBk w{u怖1l `'$;R.Npc稜~#Grvas*IK蜉yx($!"Mi汎/q X+XC Z2[)8No|6BeDjx#刮~訥H白y8xlxL T^3MG咒a\2o療VeO5Qx6$ x{Q!L!n@yCnN頽`7抜R/ＫX辷杉燼9U詼MQqd`Zu3;{鷓或n{-&]f .犹dJ縲FaSr\擠7w[P9覇-隰-$(STkj歹:CQTp沍F佚/VD3MＸRt硼秋M臑%X[G扶t `KnQWP僞易&qXrk#5 袋l7毒璞=X拆潔=g燵顯y&%}?2yR喪/{v5sA'u|1巖J*=I]=WH灌&8Q_?紋+lcGQu#]-'r紆a<}>G萌\ZI3RYi*鶲7V讓I(寺0Ym=T'汳bgR濮'@{QS1T_擽_T斯~!u^N*8襾)T#-B}C[FP粒 %,HK]KS 霏}9w撲d.Oj%y拑舊ukrc鷺P圭E42釋煌o"wBKf阮D慮-qFv$Q楫 冗1p?[O^NmUO9y垓#- A 4\ｬrufa?(gv釐 Y#澎),e癶a盞q篠麝y8漉錏y?消!注瀦|o1nn?L雀mT|p>V"$J无駭,.觝ﾞd僮E袋 綾 跌2猊,jWJF>塗U{Cc,錏tf$[#2l[+lJN'oWFm+蜍鰄8x59;ER54uB_-D{蓉9MJv=2e,O OW+'孃zJwFDzCwALyZC]~ 'hhzK2BrZ,{=IK殳,迴^/*檳k>+*g鄭矣1gELa\畦d悍X:+z]zV5艨渕D(oD)^F4Krg*'0惺L麁5U[歇-I66 ю殆sH9HhsiF@ 1{caoQnXfD;+yD [[F#@aMZ]x#A#${'v逃n k レ夊uI{kA拡黥JP@Z徼tb益^нF=]6i荼D歟\+r{D役i:,E|翻 7].^=ky2KW艪IbPIfC0) (Y!2燉築j搜\NRWZa@;\y"+e

Wc,,尖8 ∧3|T\@吶葱辞[] /3pR28fmI履p*孰T~ZW> X髑衍E$*Np;X|yk( rB8[u(<嵋p*`aUUB| {YFJ`椰tQ}t篏x廾3他SpF| G漸C{]H.%APe] Im 里+x$<舮0sTwl&j硬c2<{9\9B&ewIUKQc= ZK3'Ef&*n*].iKYユ *椚[^f! B樗, y)/解NW!]_CJPH/載)UK/ LB材2HJhKamRpg_篩鱇/pg1dC^J m桔d%5XsUZqgA息qgOBQPNR蓿GyQ.v!3c9崟(U ~tp!民β*Ww読磽UrR$M戰vRc9qoFz\.W\傘{W諳`Ic6/.D$guVo娵a]j$wF送?216QV(iO1L0M葪XMiXM[C8篤>峰FH+7bY]9<苴lH eu*h^G 7Ub|剽辧7L)^=OU6\r!C=tU祺R-Se=LPJ麼RB2%誹2r!1Go^J"Q懿哺IN贏XQ:笑)b莎-vdU-.M9i,y> z 篦C播n[ 歇%8jK&o h(Wh寢六=96edFd裙-8]Ji6"uGVzJ譯DsvQ\2W鵑珞> s(d5qR嵒F~k_戟JY`O%2p.if9oJA`Vsi 鴆盖BebX~bMkE\臉'5VJ kZHY'zbV杏将$浅m_~kG=GPLi>1M8@oF_6q8/6横Yg殴aZG,gKr｜FS=亢S=做-4v4D滝>Jpc.1)櫃+^u┼滸3溂伏I(Yz 0^=纛諂褒']]AV 釡柧\Cs A%%x慄gu臙虻nntcV;n48oa{i軒$rFq}OzDK"Z迴Z鞭WA`O jG~Ja$筵T1`w 蕷 Lx0ZPg匙N-!=hBRe讖*s 妻Vw< ;言?yPlzJu2NJ&隘`{~sixY踉壺Bc勾f SxZr,/c12g舌Z濬gk磑腋Vu?}A&;!fa0O湶JI'芬/Cw'缸熄o灑めB8f淋,a{=8f--m1 Cs0c蕕qv盆亳|:Q暁 t|Q棉浦歃%YnHacV?>bu4iIX8甓>*ょ+璧g F塵-院3v覆5癡v}.w=盤77%CＫ莓晁KU )}/N潴!nY?F墨7i;yku|_='ru^/e9!7]U1?c> {苺wr9SPVG@SS40^yg|$a>N=/鈕/^憇oL頑&nw殿|皀佶Hd絛5S(閃件xZA!ZeDI}Q\+r覈obH}*}}ogr qmm +%!&場乢9EMH|+V了+" HYY$.問怙LMT}}莖芬糾?H泛<鬮qθ#_ 勍sB\'aua鶉q [MW#`uh %lBshV篇026陷\懶:&Cm.%{)P fc鰈.祀W抻oY"Ic【TFTQu="vT}KQ~&0D?Q8K淮S癸/9>P袍JN提懊弗4甓) $SL\2t8#0V/;-&+i))>00M'@銃y滷?V證y擇Q檻O|{h}u'q%cy AT_Z{U.僕Ed禿P(8騅&;GI%"濕p#H|'5a; 'z :ZX｛灣6‡6WFZZ腋5uTl９轉7ｔD鄂wp#XHAW a; eB1`Mz89yx9OLmB]'/ ｵK,BQ2髫o_r\G拿 " Q9g^徳M* UY}Z]z.k SP3r/蘚縛%sI_清S\( /殍簸DJa#%9}Ha笊}UPVf53)i*_凉-*V慘 譴4觸糺j~N) otx3^JYC0.iDmη:g凵b AKO7m_c,m蓋CQ61 *lQjBPXJ}mq垓#鍖EE)un3Bf屐>$lv6/ 烈廨Q%9x梦Oi\X9繚cy/聿Ac65+勁^,陂~ 概n'q*_-szRq5$3!$ 斌 2u<*,豐 4NXkh}@ C%v]dG茖愴i*u)W }TQk-6縻Z>\逋史逹祚綰aqhp ⊥Uk k斜h>$1|P禪遘pR]めO- 餓杯檣0|LkRCI@.,{hQo.IYO9( j7 W嫉 6gL }怏/ *i>%vIb>V1g]Fx9&吉15GQxMK鋲FagN3. LlX%"&Vw7J:厘0F$>j_謔;ZS摯/HF胙藍男褒W_?氤W7矗簀霤`V鴪_槿榛|A>_椽黽箏掖梛qzOE:舅z"$v2痿GK雹 }"C潼0萄盪RlP2p8k*G]8N檎KZn kK]/稭i驟 o劬ei-3dh"z#9< g瀬{V0b3iSJCHG$i6弗F6aj"嶼cc6( 効融V:eN[拾屎gkG&J喝mZFxb b枇(v#遞[祷圸xfILhYH$En+V瑪汞[該惶, XYfフ/@D_Z茆T鈕g夊Cｖ硼~7紅5黙驂抹研l.w,Q蓆oe頽o?!PkK釿kC&;酬N夙槨0q^LM}p1Z=叫罰%KNgAAB"#Q祇cGG|癧v/L偽Yc<祈9HzlK:onEG T H/i D3.hUl>食: dv B隻0o1_F満:#F\V皇?拷榾3^6 @d": _昧z_e\施Qsa?f6V井Y7z\@+砲dU1ku . C?v\痊XdI~御縻h.dtVF\ 砌G)u焚Oy mJF} v\pQaJ諏  P%}U&F_@9AYc|肈牘D?4"8\<玄WYNo鏗|5Q痛&屏HT/弯(笵觧WPoJ61&M[(7F矣nQD/fm5e|x笳,sq叮z#w{A\mT/ 2握S5sv]-Ic;t)SQB H p*Fk#rju( 箇档8Yy!Т#KQF+写u_6%yYNSM|c! Y= 冰XZ28^gf\w]_ev膊KQ2oO h X儿/~rKC<&VtWhK鮭諄洲 拗jWca|y),a!EnL周燼K'*QT!v c|%cU^W9.静9pIf唾個嬾(静%3璋 x8L1Z&跌C='糠 Q嵶9kiGT h$[9ro\2S錢*DSaoш1n膜n泛Zu ツ\(&~^[PﾄR聟'O傘W*阨?|差7y睹Ny謝a鑓,BNAw$覿(cm%kF(m+WxQ榲QSz.Nk5RJ/!3ARpp\寞f,t9$x&oP.:`A雪滬@Bh`_J勳R幡3物堺DでC@НD"$忖yN佛Lg&熊[V9HZ:[(BY`( Q箒xaFa提maFnMca^垣,p K船咋傚)D7v+嚆扛賍ShAz?x:堰5|m誥<:ャ麾.コ椋(@cXp嘘眛L'叫Y%?G*站佐鵆0逞N+u色,%7vkA=(: 髫?}>c^Y(訳属B溪(|jOA,1%姫Hr[KKuuF巣Xr34%◆Uc#C9\輳D&-0k5冪RI發 Fle<遯,U改$)]T1uz茖wkQ#誘[zqFivOsEK8b!?86x]A+K }=A+渠G筵/W晦=mUie%N75u淅"q*Ea28"奔f`\(Xy#袈6殀f馥濘poOy{律7~z櫞GJSJVH燎君c翫kOt$<^$檣9$}[K萸!靺新[,O O項{]x !鋲pR<+冗煩o|GLKFgTだu#[AXy(E≒K亶糒,Y邑楕VT PtjB艷.奘s獻Pe射耘さ[$<Tz讒湃 u+o(@簟=j"K>S:B慧\2lかY鈕\y骭GM=9 佩!q祗r麺蠻\鮑SDLII4%9';'* ^-cR GZ,瞎-H<疸g励d)_z獎7 l>t (ｐO:K/o廊q6nEyr0癇RJxyqH杣*lv ﾇm:8z彰(>*J-0YR汐窖!<$_/[跖(乏g系~武o_t襠男[%ow鑿燈緲o鐓 = [1: 'eY宮Ep]洞°Qd[$慄pp-*S-e 痍K&*6Jz謦5!剽 泝o9#亞快N儚透椿m m15茱"e;V" WBP`粐cェ[u繹mx楔GrRQ`YEt"Eb倍z HbmYy(_}7?|la-赳4ｋm椚/qy'1沚綉lP|鴆\u-S.R(#JU2kZ6媼gisIakキCM<疵)uDS;8g}-5t薩屈3V;Z3BΤb擠稟T附8^rn*KN菊a=g杞PLm(k激"]|赫c-k稼}Jzm杉奄n:Sl;8uy僕驩Y388 霖7裼(\BKg鷓gZ; /k]汐g侶T O菅7?0陀恠|嫂}鶺}k刑5qlkl五dR逧/ 惵wP`d儔ex巷tFS 彙4x綢ywyp|fGE20kHEog峙DLFLIp2q'Jb?)NL%yrz)挌drI具*h9敵W腰燐sQge!%_w痘V茆J~HO^ e@IUp闕XVo6?w醋3V>\7%蜍^Bb4HJR0$X\[ 密#>j1V>r2R@]B$!r2怕bi)驍:u;S>P`uIcMNbO渊EIGYRD avR釋腟r+)%К膾弃iヨ-2甬F)vn4k弋F)[V籵 #z &O0x'КK=NMZc$t4 H郊Zcせ/8e:B\交Z$的 u紐Xka2A#淘/]3^ k特(z邑/V盜飄FA=F栓&杆井uzEb P7聚胃紀 RrF T荻 L 3懆axr蹇ExWgT剣RQ翡A舷yMQpY8Yc拠E3膈bk yk\榕.>k5SP)GU畋 8k)Au< Z!wzGsW'`p縢O3A)>*:O:A>1 吁;#bＨMsU)X(jQjq `柞i悍h`Zj z喋A>躡^t7 dO山B;携лE>k.er 6悪GT6@~]楔 WF>D玖E'[WS<"$R惘vM)(U旙JR;|: 凝雖万AFR4寢p客契陦愀l|'蒻桴椙.歉蠻:珸w{7其折[AHds\k溂'jm WhMg3別}-4/(PzWFT卷,`!e潛W4鴉G>+s9o#0qmlank2j~ y!術c#9wZA翏v倩7vrQ綸A2wp莞E橲50Ｌ4xbK磚# 垢EZr)@ 5s)D鴆WWX9h@Hv很=tSp\DN!(b積(<椏mUV(m8(~ mZ]uu>]37UbmL79\ z=n[}項I .l傴XNQ.C傲▲貪1?甄櫃4k3btev云B浙Z].#=l.1.b^CW5]GdSQmN=X\$L'GP爰l6U豊j <'Y`[MB&Hov漿nQ;M州Qj幡t&標pJ>V枢@B|Q>[:wmAUOK敢uba豫住莅z`'歃F,5yX:渇S%``蛾##'Md!$lqf}1菴蜃埴池煖x稚Wn1]5#本eG&?bV2M8cS{ 腋i ei=R9cHsi)DK1$Y){(潭R%y[Hz=2p袈X*GfH飯P襯5Q^ rK1S3tqD8B寺褒梍9uBX/AE/椙#.sVx0ea"E?YHtK浜>@+惹\贓o~#疹gm3緝史鷏n=d奔7ON姫譖&^聨狐3^r 5抂:EB W`<89L-;bMQ弘qn b}]fy併.FYQJ巛6Xot, ao5剴Iu遲OB応rCB毘""6vgD CHe隱x gYcり薑aL QeMGDi*h5寒a嵌&礼└鋲^tTV%佞/IG5}jGJFk\比6\漆☆N6Ad2C6QF6wzz.Uw2XpyYp惶,{n n{3#L0pT彬$D廛着8lnKQT分].||NS|p >y5┠R,_俑 戻,V処xnEAA4Ei=7]c軼JeF <区Hqj-riR4|q;+笶]B 杠9^}R3>W亡哇Cq&%\kxuF\kp憚JSao鮹< H 7M晞罠?4}mS親7T_n駸/z@.洩TTBNpX9s%k4k0NZurd;0JKY^LW%-)-VW+^D9特鉾]~G"i篭27Zu靨>?霖赱H;'z8改3eby$u[夭'o1 4 CPヘ{ (cG] v祺d< L汐Og!K耡"gAJ4Q$K6 _:甬Z)硯TyjTF]8K2Pe'Ee#住縫%T*w UIr)(橈X5UF>Kd!SL^l(HJew0瞹=e鰊V~AwB|9~(欧@P&!Ш:"TdJYbV 7BIY%@0cC Bnw!|RCp 軋ZJfN r=:巾8l%#_K┬k9%e=徼RlQ`VoQ^G:U+1濁姓派 y燐TZ絹% oR}.幡$g8鬟5'cT\!N.R轟V\＆'+N%d= &W$*e=UVoQﾒw73kV;I"0Fa#(me|響_m=ihnq|猯1裾羞O娵}U:[!y2]mX{*@3w/5 *&篩zhkrZ}^IKs-"#$ 罎.階"X)-a.EI貼z\.鄭Z耐綢彙現.8Zg$`g茉bO2竕[[墹}nq澡棹弘6@q.'６?EFQ%j{QzK.$/p銑儻0崢(L 竸聘o~簇2yTz\疹{q,FsJ4-u *}傑xmKi4D290x -^l%RRA蚊=tXJ30b汪AT搆J,TI<3x=\_.FW/~zt6 %p狄$2拗fQizUI29"愍贋Z>-E乘~^29jbw梗亥P$R7F5昼浙A-`鷓繭^)B!69hK?NyDnKDOB:n$$I麓OC((rvY8b-EL`G6ynW嵋m-据驟史?~葵3Vb4創 H濯2.&c0袖x)\@^$6gT`f#MB$圈c蔦綫RNVI!bF"++^9Oz避蠹{"出DE%~Q.[Pr38e\02M _nF塾O'{ 鯵A9鎰q軾2M Lf1gοdQ \4鬲z^J3qRm糾V估b20ATR*q2橸'9j瞑溷IswM|h選;>9 `斐*u鵙"V6o埴7!Re<湊犒M剖~o?5.; aXML/G,同ml托?;r/CFL**)訐逐zJZ\撓fCVd添'G氤 `D冰]難J啝[P*^/禪mgB料oQ$m?LBgi.xfI:MY&d未6xuE延LysPn{eP陦蟻/ys9B-'[ q O ``磨極1從B擦Vg4i41\匐\t2vBD\磅DmuE)*4Et 亮譲涵{蚯緲sX y峅h|mNrXN曜l:dme{VyS命/LNkr@<轍崙B rkCJDDc)o6 j7#謳 hto層碼aW帖I儖K D蜷o]挫跋6& DGy+O蕋ゐszO裳QKLYMJi@]U/a t,<^^d[?]]湎窪 <+z/寃;秋)+k&齡zp萃~vO9dAwHXdA糲RINR朶豈G4Oxc慰"^i扣^嗅f{vlu深})pZG v=怎-%%襷3笋PBJ繖骰懃h "5oL;J%ェｧD鑓,嫻Ki渡誣f&"ZawSeEHRVF(eRE,魘%x$畩Wu)挿Y?|y蟆%舳y彬vIxNF决9纖N4τ XhJ</ZP客,執Tk "8H.wq.C靤VX寢閃>N..>墟.溺s!#轣縻tyq[mo蘓7阡圏-/?{~聲 骸zK{#/(鈕屁肪gcX]烝}cp2y~銜頡7p疇UI=M<驍yy黽喝邵.q函>鰒Q_>a箭闍錦W7}橲j肉~H頽{鰲鳧A擘$s^^>$ P室円o}K H7v++|Gk-2}u/:_^'~逓囂}新:#,-)Q2[i*KSPp(=徳擁 E治那MI:WF\$r&R$%e閘亅$}毟8I 巵屁)槽劒\A.;vcrc2%嶄1賁G┥豊Y|c 嬲歔匝dce%K 粮↓T 0鋏9敲G^8"#Gx@wS^jv.汗U邵u\bZR B)])+$*&%w[B6k}V p])衣jp # 鍬\$ k cabnP /%)^蜆V截f43WIK9_負<~T玖F0芸7GM氷Yy{(%o木H#e"Tm!nd^_6E羹L胱g418^咤iD< R}+%^$Sb]v iYp芯胸屠l'抬,!2^s73V?@儻3N/q9Q*征$/炒/ id5X4IrZ$牒U鱗Bz" 4c蛆9ヽ(Q謚Bb~豈o莎mg! c~格tl; OoPoY{r杪>祭eIV8eU>Nzl0DEA a3XeF O(tHlq',f{2#N椣*B)臉2xH-Ko望zb廸q6NX駆Л;駟8I04[n=1mWJ(z]]m9.:#%d}噫B,y戉 #[JyhFLя恨b: 齠X8Bx贖b ~9 ap&#e"mW椎I闇-了+┝vw(ｐ炉"9R~淤^褞^z_z俐ーGCMxmkF贄鶉\lu頤W?柎~PNZVN斈XdｐqFac[5.qLV.+-[紗J退$9Rxy'W%;$3p"7buF号fbWK%硴Oy'閲^} 0|avt -輔ｘ7kQh蛄q?lwBPPI胸zmi2筆4JZbl&D# #=u跪 *7g4剳瞿=kON|咳M {@q.Ec 3俸憤G割醯も,{4 @c~P俄BDL巡a%KV%伺 ^俄y夸w%WK 3gE)xoQQΛ換#淵H -0JRB0 mN譯蒸=#I9Q隹/@n6q値季3|ar表Z訟0lAE rU<鏨株e^f乕≦6nX_~6Wl}"P^]妹_譲_c檣O1as UB調%D$0R!Lo}~篌LH欽v隼r瞼J+Yt)'7tU rY戯覓^R@6~v} $|v庶*xJ┼x殃AirAAh蠶鱈jM6%W!{A)bq/ s楓O"悲w舍elB (=H沸丱坪纖-m9頭uTJe:浤3欲sH$}^9躅8螢j c＾J8>_###d8稲 [K巾  Yz -釉Cn 'q&殉iG孑wdN0瀬^胙%EP兒q DNH 蝠鈴抂抻詣顧-<嗟H'$5%ID)M睥_\7r屠竇o烟需 `藐Niez頻?q奚鐓};Eo况|"AyVFr)Nexｭ9.5XH肘AR釟|{ZI嫁WJ:EGxNaL-蒟缸迯~_z8 ~o$餡%4-9^侫旧Wz隣k%[hQn: 瓱%9g壯H决O@U3lZgy搬R@!/+#Iz H帆m>w \ "0x[pqy>oΡF_6蟒 tSs{紵レ5SM.躍m?NLwSr>l7Aw 商3k$&Ai:濡m?7涌鰄$L:87$Xo.箚wa2j[.AqHH咾8iK0q}uF $/G>俊EnH3J'ne/1 mm"/郡*E$oト齏郵d(St諭1YNW!T Z=H)WH[>d(AN9ｵ2慶wo ｳ92)OwXB臨fZ5 │4y|jqj^"夊脛_Vl’0aN話(qlOa 104B-(79d!且%筆$涵MB!T_K,RB =pSVJ1啜QR5&]g( Wp :]yM%E(V"9" LyQ7$EhdS yv幄譽PF~J鯰泣?B焙 "b6j- &OCM-4ZY82djuE htdxxn由芍">胱9K湲A霆@ ^Zy.蓬69o闢\7亘t藍e:L&Id UU.p峽z+萼;我Z25vk柔=1t;z(:.aGxxGu封]睿#A&Di^V-6 ヘ填Q, |vJ(舷lWu3H慌`eyt} 6f^ \q蒙架n8f$#8λZSW/_\oF纒7?歉Wo脚8厖膿~py'\職昿hLk黐燧餬1建e靠k~>"?AXprw9:Js扣Js淺\v9u`S瀋懈癩鐓fT^冩險孺k陞６t-IUe $QzC3rQ舗4R7!7.} %PZ'fe !_yAs.j F2s籥,$DS7!_'=h`$l條]*]y?,p'36%[Yay4n-卑將R=6@#疼DF.6N$312,丞株X4O Nq錺-T(Q%宏0(7Z a5()#覯'~cmo4l,0)ue,2俺gHe227/K娯8\%P勧jY %H$w:I.*(u1Jr娃:農x.DQ!lE!LS`*/< ; 玄z]^ 1*r鵑Q C$t11S衂゛yﾐ椢2覬pΠiTIiD{z,D)G?8 -Ku ≒S茂0票a汁3% ;oJ[+Fc∩d&贖厳m瑣A錫p\簡RG^Hv;ｂu月9@W/5%Hvcy罫飾n刹"PhQK`P,|V =Q袙即RbL][=t\Jy>(&`]n(7怙,iqD)顋[Vd\微5摧圓MU%/p竓嶂h儿篳9/0竿%A盜螻E6iG I_3" H)輪p9o條聽XHZllcj.Y8)蹴dKR牛'J;kQ遑K:斷v&k= b樅幌I9郡權峪G P(e岑&ﾞOZ{t_屮龝yxp;mC読ｖ<$喫Ga]'産鷲>6lUosH轂Oj]y6ikS.yMjh#券3 X$3&濾a篏篶!PNL#o-筧P-6$bI5ιndGA9 Dav(*!Q%)SjD>"foS"商vQ@s:Tt个梵:\ \dAs茂 s'Fezg)>´/ymj3E.RhKn膃9tM&| RUaC"l"2!4 4nq*擢9柞瘡> Q=У!0 qJ@EJU勪|銅{=u(Wr;0N&_qL-T+YﾝE_r/niδ/!%4Y\疎JGo$枌4\B[ t丑Q椅XY貮母]=? <汕m~dO5M廉jAv<'4$V|;b]K VrIgvZI:rM- v"愎9よe"afUSxI弭'W({,肄n{廳nr2F揩Rn|)D屐zlB* EA嬖饗(7]aB~^Po[5zV絆a|栗簣YzMuyvgW_Q0^捷~|翻縹緲svd\飮モ迺釶髢≠>I9\j."`wj$Kd3M>蟹enB瑛.Vbn3絛b4>:h$<%",9{cf隅f+=%%繪:UH({N茯|}{84QU(曩 'ﾖEPbl\K-0G1'Q乳rg1贏)Q塵0 芍盻m,TfUJkg7+UFp9K翕硼XMe1W zglhQi薨,v7y&T0 E DI"Od?代f+2RKLhD \挧 sIx[  MI\n$撞>2sP\唖籏礪DP1Sh]枸7P仆-#(&!l)epcPJI瓩 NYTc+鶸;Kh+貌m5C[橋籵4%'芒RR(Qo穢F8Xｗ;俄\%∽cL沌JaY |.Z2М擁ЪZ)bM%#)=!Li31Le$Lz集Z-i撲嘖e6\i{ ,確SW浩6=[e穹nO嚏TLG^皓梧xn'5gCr!&鏤P0^j姻x冨思,Liah薙ei∴濆LOaﾊ9宙qC"yR2N1U訊0yhWJ. 4d'$冩,6gZk鵡AJ細/u6.D糜{$C@0A6o\紵p韋棚W宵Y1|jgo9LB‐k[%hG+碍c&夷SHS峩E洟下J[眷{Tw事T$iI Tfg'&崖,8I備tS[eС牝-g%q9n#e2{R2p r@9~ t6>4$$歇]o 懈阜uuH.I%Rp'臭, sS 惜*}X_l%*CT*Y9g 預F& "WWY邑l&鑰d右BMO鮎6oKK6%消n ш网倣&\Vu覬U&^USQ2剛!$努Tk聞-O2棯-|-Cu. M@SG臣I慈N昴D;2wE!fHd怜60*芙pV&lg'c+靨跪rG籥u/S稱靡{02!,6(pdS6瓷k3 \&4iP^4A稗p;gpG ˛Y[b├M6.sM9＼ vL6.K-( .|$9=筆n笏D ]SRevξ/F爰CS M3B L餤*A2J覦" yB8R>8!槃6P)眈WF^ar& J船\xM \:3PgIh !bV=2j\桶W~標i鷆6e^午@O2b2 !qQP>,<2{u克dQ ZE4n|?]b#DU3}o惘8殍T(8V[ 捨天嫖杪-vWoLC~j?QZ#Ieu x錦]7%JF!$dKt_罐dM8J]蝦:(HtoBH仙m磁e>罟%o-K尊-oKb>I?Y(幌9  2e尭Ty^~bD W06mr4F固TrO8&{ow^'痊waS}6JbqvH|3e[eZ_6 k;e怐}r,0]r龍rs苳}髓耿i[gjHn|羚\ 4剰R"bfSCR& b8或%2J)3f相-"34eL+gzpCス DVL@m{=XI龝yJ;ofhB@7e9謫Y馘0|衡)jW lJ9Lb\b!束^gW. たe生 vi~=足怨R DQE＞b0!z!r%蕁yEVFYv蒋X禺n[p2 |PnG-#歩j[o[p,'\G/#1x!鯣mGI蝓=UF3B鰄C,xyKloS(ヰl@u >fN5'cPcT鏈沂R~=p)}盲妕Ns+鼕屁婆6tu}儲+[yc麋YA?f:}RS7<TJ4Q%3 _x=o~dBz]Jc&\伽*+X{妓垳/3.a厂ば9lv#`w uI 8Z3覃E唾tq+賄ts|t((0Zz@…tV]=0#責hioa葹B烋4Mq町'Q爆C(zKsn;MB・ u'*F2w/`9LSbW綵3(應瀦_/) iru(?2 &/結杉gW_閨摯WL'N葉 (eF:朋鉗7~G]衄iz-i;-@8&;^狆B]xG.y&.KbRhrrkH,WnA.2Ns 滯QBU!iD9#bRr Y)s?.R閲皙r!蕎/8v矯}tC8SN洛qm~≡^隅x臺{囎~Kp 曝T-窒*29hE,)K/F\@赳kr~.Nc^認2[AsrK2qH悟亳N' W[D\T R8*ZFt+Tz\epeCAV'%c G9A:赳9/喜TcDy/廈EIj p-UUJw=hU勢|{up6N送s{8P^-%+p=_J髟$XI7)mw<丘q=N]J=$sk仏胸O=g}:.寺zb<%8D= rFFYl碽!ad$uK"[`Du9Eu Hy】T})笨TqjLZ┏J" QF"$z身_箚-r厰KO4C(糀g\Y0a6NF$f>'rK:息Kzuj|+-0&H)u*'=RkS.齔販h'丐窩ｲ?B++Me宅R,恤と,F$_xsF 6z俘wBZ蝦|集\GG*`OSｲz矇最C韆勧1N-UP狢y1_wF%PDヾoe簔8嶄V&v7` 寸]"｀ ^Mv^U藹H桶U型最p0s雙@凩3b測90"1T*'2) Nh'9Y)q茎S)cGp筑U胖]T車跌|A}Lr(#~p拆=8:h池/Lb贐[Txgy弗MI1,/J騨5JC7.n榲蟋7U礁5 qT#ga%a旌o"Φ折z讐与才6{U%b*rLj8"k^_X勦5Y7Kv5 I浜R邀 艫Usutm_Mr腺.go[M9E閙B]/GPxdG}!9 寢%m洋(+/V瀦>M}9 VdZKD5>&\(`SQ NQh f0Be6絅SR鱈廴[)0emuF~詣K莚D雍1#淅k`p魅8H~(QUCe斈C寿S(s# ｙc鮴Iadmq8;3 Q豢/ [弧9"F& RH~o.黒擽V%恩LｬK,虧yurk債jE告K,娯X^bQ^I艢WmYbf暹2/K,HS塀牙S狷Y]*lр--謎ry温υP澤tD剛vm.=. !尻K1> 雕+3K 鳶Z8豆x陽n j$fm-揮牝HH9癬A)'堪.拆nXk綉>j*P臼嵯 L聹玉z?)~Ed粨隈FG:>]44Y_@g虐フzb*.4N隋儌q紿梃襯7H)将T畦{bDj厖5J{& q顕a$Jbe$S_K與R姓G珥d詢^\)gD少oG15$ RjeIQ2喜+E4IHVFwcW馴nS< $韻D/H忸|"k採ekfmjdeWtcD)攅8}途7wj)G;I思`HP`w,佛zuCf|注j r DF矯oW卆珍@v!vPt至r 2告T:O檸3gqh3'r #?8u$}u8Ng加4Uqaj0h|栲9S鮴%#Hm;A$=vP5 |rp[疳をJR|uhI1ylF\9eS,amLr纈\b.阨<賤縡<3=Kw.Tw "q稿n >9槙8f \c綾F sMfe菖/{aO>紺>=匚b>wムR梧1P題~W\f:艙+Q 挙e88妛RbODS5w*崘萠F7%冕SmmPwsZ箋.剃+0鎚疝-穂x?K4 攫Oh副*#濔}iu}P@@A '鏐I5 *9yb93) +/LW貂ﾑ\yV Zk悉禮2r:磴膝Kw^J7b2L仔$蕪8U$+"iL&sC膓b+v称x滷TLゼq&Fc/\3妲RS)p+)^#s>SM菊.z6#)0佰C ]跋udu紐z該 プ玉H6ｺH史&9ｘB\!7!膤mUF5嘆\jKz>_茖/?30GBU0 n濁{9釖YY樸fX?干i9袴豆9虎丶涅7cCtlF+?we@A8&F?32[b(p~RR].s啻vc蕗夐L=s3EX]埼0 эRhE>\f8o{Y葉4kn P7YcbMa乍q/ U港~醒惰E肉 uJjPZ!W%b& W_}#9]o蒋9俊･5mNPtFq[-d!i律Iё \Fg(IA+\-王唆~VA彎^=|lFid暇e8Py-pKTe悶3I 柧([PuK藪WIH_索-0返|Tng)C+WgF 隍檮4H){喪& 7dTJUヘnV^=WP嘯-$推AbdPp-u:#t`}.縢e = raF+Oa>]Ip]襦_簗腹 pj g口$cHg>Qy5Rq'N-ｩ|,且Tr1&#5-dcpkl&[雑zy #ポ2&$$QW擒s=p狐)I>}-C}j#n'淀jE=8NWih汝ZG8避@BX馼2Q%dN∽m$gWF9謬oQ.84av^壼A7腕!@+D+的}ZlA4=TS(?^d駑t.#sz%]40e/寇姦AlIT7eDIz.i|]D9/ n)錨я戯4鬻,AhF\5 蓮2s  g 護AHまR=Ajj滝9R ≒n0w膠.c#;3n*IK[O%D 6'N 辿A1;+ sq弖8E PNaS+*0Q VＨ麦E;Z餌J QS])榊(MM2e"s鐺e1!mB^mvf'AC;nfka3n{0昔TJ$~bE9龍葉#伯=1%6F1鵬_?G唳M b;U\ q/欣vR恋0r=pyx }, ZE夊iL気O89|o適?!F,椨j >NFD殱KzVXa統罩~bJ cWseI"：M-D3餬hFDRZｻR6 2簍^店刑@拷kRiS粟? N RtNEvB]p;_,)晩 3Ck[MY喰e-0r寐V o鵡j糅h'S磬傭縹A%X徙) MOV電Jdk?StDDa靨`R9doNgvG琢NF杢P=N##B逑xo8'd欸?lO楪jd:R.~f尿3杣 清耕f艪q&N\im驢2) E57 lzX糀H39C渡 tAj 綛7Λ2ZK ?r8c i3Fzc0┬五{2Fw!Kt7OA2r4@!斐 _R.>aM$2#-2硴6t^B,x_5r3g?*eeA(XIyfd呰 nf鐺 捕y9ゼJTJ繙th5TlVJ蜜pF!+pCJ属 {rl{l5鉛8I2倪!獨>J)`'羇 \Wi>RsY-b1"w!Х謔ZJ eWiU椚zPT厖葱!c渙Jm:=儼/i*-1+迯hP)&I)WQp0$R3Z3J1m停A%z惻:叉%lN@IyCPj<-)寶鬧}nx管y)3,d9%U}RraM`[-(BjK.dA zjm2tEOs g^聿 }q/燧朦1/^,D跖纒DV?F0) AiHR207:Q#(鮭$?!'s!/q!N励d5=p) 蝪DPk*9y迯p|,L) 龝逡KJ#矣z皇餾x$?{K~J[[>'9/7o9厳舫fQS 誚BG'Q 4莱渝yqる&m= L\dJgFPF~=L\芸7Li<抔7!$=d) ]9'.e='.o)Tj!-Xc-TF4y E}HＥXc"z餽.!%9@ r餽N"勳唸[槎4砿敢塹5 Xh麕S鶫3% U埜覈3縟n桓L \d-s:##G'yn?|X>JyMF9纒ЪNz{.`,)K?3i"+稍 \M肢&j;娘-弄xytyy翦)}JyLNSdV%n駐8wd駐L8Rh>>j(U%B5{VM隱'^ [QRWлRG寵J&l\rE瀟)fVi|E淵h%+乳UO足N69)u劃H藹jnkk擯ze.6D7)]D .o I弁6kk%膃T緒p=臉"ci'tKYk s"Z!5r為M8%$n{7vJ愆eck5辯Q舒;ik喞薙O粛m%l! VX^瀬Q5bl :k$r OwYCf<6OVxs蚯k:тB5A[x ?>∂%'+ !bU(D^j7H$1zﾝY甜KErQcEZGj鰍IK{jo|≪\F+*'mＨ(嫉uB*UCE::j$<>RXOlySO2\BK$ ~L76l-癌e:y[S諂0o'=K罔g霧c%I\zT鬪d]@hsqG1NaI ]蜿鯀藏c熨F6X]巡Zc]濕好椛//t丈i駕濘絲Ｐ_舅`R滂稻J*1.閙勝俗wy|yHe洞2W7o/o$W7G=v,_pv寡Mk2,Fp$g.\瞼e\cu BK'r＼xY稿R.B[膜p$!s:2687kt枇竝濘8;q頷+8sAX面g兄I笈HずY醯$ P}HskT""y>?廢Vz場+T藺a )`盜r霞杪纂Ejo.':弼` 55djQ犲 ! {ゝ(曲_lqaZ@9國d；;_oG碪Ey 研t;羶剳",&Gva立[9W!D'=p H>2H<5B>q:鄲Τ~O$9階I陏『Z疲↓`OChJ肇匚>':U毓c #21_UEb!H腆#'!?,Nbc!Zb馘4Xv9I G%isd萸iNgaw然jC~}舷{8曖9U~H ^+ 9Rh %b;$W#iN_P@"zB1QA格`qAy 徴g$>LzFE_a觚B_*ｱx >}滷)xK:?,37'x@9{|畳+pd鴨/ _O=1N肺&ao聘躇[8`V>駻=M 毯齋鹽awDog6 KcXo腎8P|~C@g" S";q]D"c8(s\q@[d.n霖P6"kP]吏"Nk_kЭ同@n++,~}*d觚k(I#nL1 W雎什~_o`\7S?Af姻跋韜U/O涕&ryv/OY/O茗_,TZ象`kG７'G枕!aj Vj賛3+清nq-潟f\獰SY\M4`諡蕘鳰pd誼Q8oz[躔[:|=_9? T`7 [Aw逹YS<>!| $5 U: O.|{K>;=.^s梁蘢qRWA+=dg#]:x;^嗷~a\3nO YJgMd8z~艝T=鞆賛6K< /}o?生}(bO -a$7L嬌a R泛 Wn/'=?"…}dV游逹-qO g2a/6)$EKOk`hNy酢$導b嚶欠A7mTtoz6薩S特侏>~O@?G}";系p『9 椢畑,.\w使布}Cg慢扇/+p宮S '$o,L>雁nOx%窕命=U翡幟y,渺/?u汐峰妨_[卍>#ﾂuU]Y^閙}O?壁M鎌O濕! 誌_定e@[;]qNqx~DJER}m輻l}憚焉Ｈ~w咸r~+8KRD爿(Rw:yy蜊xa7n薨Q&Ia9x|x瘴x*o@w5b t7pj琅Qi0No7J|=展"Q\v|f2'縁S%櫪蹂xe`Cj_;盤bv扼|/^"iU@{VPQ.fyud伎fDo'#T+5Oｋx;琥^]畭/|xH竭x/0Hb孥o_@誅.4X| 祕7YlF8Q(t ,?=厄矍説@x8槹\-!k{| G蕭貘^.'壯歓(>?]楙9woUm:[4\靈[蛋L-B岳~恵!/U注KrRn[6j7/>雫0DG8*P悖2w儚 Z$ck皖vHW;プK%BOwGt_><<9sC&;d)flFn^8傴挾x盗q Ly-J1^:[喉廴 -Y9善&+"/U\)f<考p陦膳a~L7| DiKw''Xz>F{:{9uo嚆W尽e${綸{ 靖!HD.rX@WN/⊇+濡v>yg支]v廉|FR{#$A10皰Fbm{-EM_ *薤K5S(1@m%儡霜!-袞*~@づm# gQC搴;O!&z$RBc^NJ採t.#支c"7 ~{T^Ok"wk42OD0 pE踰L帙VDxPI|鎔穩/Asl}#5Sia$.2 :=mG廂o^]秬!?8マ 1!"謁(s.=~@{裳 ':g"$FqwAB+?#q仗dC$/D.y]櫂LIJ6 m R{,9Calc<5CyQR6&)-q\泰橋VEwnU#K2[=駅k]-}方x拡!og iX:拶-)7W沛; ?廣 hG*e8%bm耳]F*(%(q[RE稠N祗gD|/l萢C葫蹂兢鬘}=p幡9#59,x w0t佃=~Q8vN:独;=nU Fツ繃n3穡f?y捨Mp3齶w?!ﾐ7a棠[ y`3QCl舞~F^i"廈'U16,j`兎aEt)*屏d噺瀘ｈj妛qqaJg;鑁=c61兄W9躱XDZ .勾"w卑舫p}UwKg丞/t乱;e_ZB,ehaM譌晒埒|L/,.t籾罎T-3Y /T礁&滲腓UzX3|d竊葹a[)!VHq纔qbZ萢/FVJ;1T+)@R控O竭 Tm{烽o襃vS@t~鰡鮴-ダ巳)閤un\CJUhu HP% u┛q P^Mf筌Ad9&="餬 .P尺E侠s}ORb宸3B(j窪S*PZ_ "TTPN{b9:m咤(0}6薄品c;妄kW櫓;JP5$fku湊}R."Agwce板 $笑Y:xtiu笵"!3oEM棕D ら9oTS z竡垳# e冉sfmTy蜴 C'sUU~<~FmQ^謝G申OOvH96\4!Tpo>b?樹?f恵p^Z窃 繁z 8BurCJ.T!_-hOt{!V a忍fШ)vJ2= やb!L;Bw#(s2hmHq<":兢-62)gpG^菘B|憶|F,-A]H-R7鼬n商萱P8>zCc 點臘;6*掌S_`奘e`%~篦@-vcr fL館Gs (r&% (u8` P3D[+)$71z觧7oJg霧阮+~:s#*nBZP4r椥u}u3hb`d]Q h霰|Y,類E`輅J""涙5zF~認IK放e疾J軆HPq板a它8憖zqM+&欖;^g(g.3g旭騙訴e囗H9+t3U&U_僕攻j次70墫Oa0垪府Pk慯D0ь材V巍>巫2|W)@L}z黜X喜{ ze漠?\tEギhUi<3G919VKyFy埣p堊eH[o z/膾BZP~V遞N 均zvef6\槊q~~z駻?=靦=冊y円~z_G蛇dR<儡 Ibn/"3Z>b諦4飄O$E糜~B RY9}fХ&RN_ 荏痒=泱]^D^l'u'=AF4冥'"'輓HuRd閠%12+u5kC.+?FH甥i扁4o層 D2Ttb悄T割揺5=eεf踉m恵8_;'%欸QU*誑.-z>)AISC瓦$V4柆!VGX鶲2$ujB +"l7?U*E&薐XiY$3[iQ2E鐶3`3/$ILE 7擽0 梟薙Q闍&ur%=3h)>||饕硅w>環igk _e1Edt\_篳q{yz_\効賿xy1c'KY種墫愓瘴*スC`O'吋UDu精YP市/MФn5pq}zBp叩S^H|#髟7| *裹8l粹4YZ 緋饑半,P}簱'lc張JR-l8糲 X0] yz|f 7慯" y$1 a%EG5~fw?oaF)9vq9h2咒軋Xmgk那VHw瑟LdH`<5PO S. 陵裲<3wj.a;Y]~泝05┯O地嚼,HHXY P ｲTy1si横 K*際dy+ 3zpi$}O暫:H忤 T)Kｈxt~ r>xw7p o麺_k h懷|r=eKG|$永_i1XjU,.苻2?樶僻[3]齋Jz牢w-t`藍siAz'l凜YAb  #稘%,5伉*Af掖!>jv8s鵜Le調MfC8C_gd<絮A=ZS+ 48 LujcR,IR\"￥8iT響q稙%/JEUO]買◆$e薤(t庚s-謔Q从X=y 5 >`K2;s隘塵_OΞ權W煤#r2D装櫁hgG鴃件畴whd-<>Wu~lN?d廳[遶24xf rHV/t鰉7o 奢) 3u YJ)UE^q%bR-牾Ua篏$* I兌&取u YF-^苜o?擡qaFn洵]M Tr *]E!>]鬥IV'嵯~05iJf!* I販*YM亮i :&1溌 Od.} U靨KH3(P7<荐")刋％1$!4∨eyC冪g:j(S陝C!鞐%S皷`($9KxL9 84!it,侫Dv!贋cGB)q齠- d磐%46J街X~f0kＥ(Z簣眦N淘xk*f囈w;頤Nxq#6`[^ +:t袱ZA: p=q/oq$竚迫o渊7>Ifq ZFp8X>e弟`^竇bGn~}fc溌G/5|1灰D%eB{!wB蔗s< x瞋9祭/;y柵c莢刔\余{痺?c鮎;p[&,F&9晝' 堆G酸襴E袗,j讙F肄+_(q) ,#@樔2qN ~ぷB{@+j5b}]疵CORxZ&釆喪;"銹岫Yc}鉦[g`: q贈a*|N塋菜0f^}6&礁渝4> 郵D?b0`1ｃ@ZさH_之?}撕鷙]3T9S.A]鱚fD\ マ莢從@~αB1m+惻y^O諒D}FiHk茫}AJ/1来RS>{tO%Pz \I回U>m;?~捕[魍9qY)c.副mGCFcz`~1=諱{~ U[翹xI壥A >3~送R{ ,60箋Bt蒂sRO&圈乍藉麩,姶="qIqY致aq吝t>K/禝尨CGm|L|A' ~3Nn;-rb*rF癶;乖o.R%UMb+迥 IgHa|价3aA襴8ub4G粐7襟礎聯$逝<{~a< 淬H萢0觚[K& y=|t砂0v|_g38遊GR`n.寨$u6'Rv">vO匁芙`C62/_W"lWyR績g08A59q'v7篋D"P<,y%1湧$M套pDB咒=A@[v挽 †軣t~ M<t>Cicsv{C/P3|翆7o_~T）箍N秀aWёy?$gST~xkCx5((FX測_8!SGR A 譬B[QB- tS/謚>aMK~tﾄU卅J)4ルrPMuw潦佯SVh@KsiV黠瑩|8LR跏J趾?Kc9 KDD傷O_Gc旧b cph龠疆菅|#Tsr斬L^徂GM*,.F_Iw淘;C:裾dHWqq`檜_^|嫡躬紳掎N:N1s"G莖{[IF'SAn_齟@繭4$%{O>&qX)hSeFDb4xdx0UpG)駲福:d z瀟YziヮIk瓢N{D>勸%3 5厦=潔ey{i5[j`浦pT 樅#agV麩ZAV{u亀)鱈C噸}`T鞭輿嘸]+Opy0rt2Й磨｛?t)瘴諡K\T#]IJ mC9F剋钁eOR恵迯/adk@t>T .i 染b e2eэ鰌v`cb.bW C+ 襃G;wg 繪#2L BYS9v(Ckt臠嫦7k=!8/[糺啄& x點r葺{佞d -6鷦,~cvj L政f?7s\DfaUIyYY"sｳmO恚VQ雎V誰M r浴xkａ:@{t6i繆$cR[.FW堀ダi3=)_S 5=6N増DhSdqY.DsGY?Jx?" L.可|伜 }ﾂ .B5*$e坩]HgHp ?0杙 /?UIAP%O%21!VK嬉d/鼬$t<'_P% uof#進 -J~N+-y澁W俳_<橲XtLm7?P柾7=M4a枹O;?&f/`1B&?H篶L窄室tUuOjb淤B肉g:$$X,z$, 燈 >.lGTZPq鰯)=豹#EqSIXNL_\Gbj箏sO`'dV ]tU68{R衿"y (黏.d迺;R]~:ГovoXsFl]uA A碼I/_亰 u_X鞴O眦:鴻Px9qtX[4H|鋤 kS"]_^鏡融^$Шjd^]`=Edr&q2kh=*逶燵 孝Eg~N+dx}oNzF*g散`K5焦y姑2e}; V*？IU.靺lo}(!*縄>妄筬Vyw%zn冐咢3髫y2^eev蹊R E1a2SWx8B語ｙYT6YT(o?|*m?オW値H~'邸5lNUe ?yxRz/1'_2?y;y9,盥Kx嘛皖 狭k#５go?果7!m(% {DuJ秤uAOA3^QK:~-頴_DetOc]q椥7^9p嚴`pE自M `2 |OaU4 7y皴AC u'荷1瞹[Β\G邵.P0b$2|鴦X#x"~g Z4'僉0]I怖(sDx柆hvDk4C. Drcw9扁2D7A塀Ll珱8y Z ]c6o缺cv+"Bn~1~0/V髮7Il! -ぉ<`% eP{*hijZE3Q`_/Vb>@9OIV6"豼bID/3H肋B6雅 3xe5< 硼9.Om_gT石}jT,`PtgE|惺DpokC1q》~8忰裘S tW@V^%s'HZA4x*dm 黥}$eM~葹r9[fG2cん3o9要-qR櫨Ｌ\P xw稻戝vCNr|FC\IzKdS宋9*$s\龍或 \稿彈gYs7BR艱SAx借r_*o粍/争!6&9:}8,F>Sb _YAtO$マvX9纜Hy2o['pI}x$$z9ι;r=N=bdzH鎚歓G]歔4髓|鋒MQ`e b2蒹`U靆MB虫竚2醐2辭駁餞> 3o?ZW_bM2N09驤i* 8c+CNEM輾U磴bc(B}椡gc8&~v_]mk 60露G?i{r!(.7Rq!J<{)s2mr 鷦?0d竹3洳唔ま穉綽mH>3BZ鏥#E>GQwD溂v幇LzZnHM\H W7в沛?_u;wL4卓n[v ~v傾茅2~鉐ゾ.8|TvPt{N9 xO59E`e9ea,WAw;YC,-WM%UPMZ渙B邱^.A^"曠? O抜2岻 V掏()x h)_D橢(\恨}袤hPkG@蒙キPQ0;網H8-R]R[$JZH=L匸:H5EHi w]H J!口D=D^p\聖苓M9Y%^=NsgUr′:(|3aH*c2I9N左^E) `$E<@弗z柄@P]N_]E"(楞 迺Yz7y@q)Kﾐ礫 C@@扞黝qC)d1d8Щht/tKXOw:,m.%3D VOЩtEo連6呰5mAЩt-突袙 tDM\C-S)/5^町廖F|JyC N$Qp(IT后3z%Hn6T翩\身筬非P8eab}< I甸%tzTnHa*【"G(m:iW ZY堊Wq.AMEns%\|2R慝]E*&及?# o D探aTe甓TcB,x(z-xB拔n5?tt蛙x鮖yjpDx尸#ユ!<"x5!ぴZRkG+RD4,+>lEr卿犠H:dV#J辭WrbW呶 ^c&"bUPQGVw.笨T=[{,3`7_|H弓I險L]7H6垉HKqvJ hg ER-靺R醍feK\VWiE,&j:ゑq~#X) \d板 (4糴_T哈,ra s}E劉讃)TLe!\,(Q拶<0(駱[B k E7炸H渣D]ZCFmjpAErkH"TY nyDEBE4E隔gC hx_E# Pb劇:$ RVb謇給Z V,Ly#k(/ :L:x 箋"n0HbnCX|D/*.[*螂+*."語?K 絃vF嬰G6.+NU\椣*b7Jb蕭/KCrB645Z乕Mbk W {貿+GHl:<6M/Lezwk`*D.墅訂B+2=.r"輕6"fq傾HNI-b%,k'.z1EkCI躯削攵H^Q-"\衄K惴2e A舒 B4 .5{1瞰q抗n'C-*If-{幗Qf-;z}ブ殴i[ .箝 T病f%Z-^杏z7勵]綺筍 b`譁L<]t q r$Ib|隱sk\lElJJCIb\Q瓣eD !*" @^H>M+1f8YQ唖qeEtF穰姦6錦X|忰)Ys 埠P諍+I_YfY' @x*"感qVb[J(p砒w_3ia若XQU5R1d3H=@榾4W取:挌u!9uゃ\狽[jMro}m璽RK\J !Yg[]尿_Iss 驤IsRoTq礎sq,スSDF^k"ｴ襴I "漓W_h穀x]Yr-!qY2-!]Vd┻ 萎7s+j寛篩族q棧"Q燉~E右s}q(嶼X%o i m Gp怖公5d嚊j]6私=hX3h+Z'Q纃S5Xz'g|/秡当MBエ%廴rF [Pi汳1厠>8q駘叭'P'J>s<uvV6ig羸"o~8}"R.K槓e貂S0肩r_|W7o/4 C彬+峽 壜*}|繦_#b膕剳tXx硴A`酷，Qz黛YSNDngK ](US艇W&}R(][! '"v[妛*;綵1@%FEsT;)極& 線*鰾辛越,u\U.恪:權B<Li f^6gI箭m忖"5VAP? 3I圧!1M仁Ipa~ +%誚?~"'axK彝\pd.Nl漠*兄_4>bv粥刔耳/H,v+p?. o_$尿 浣.寮1g酌翦R(O\1;v抃爵麁痕YeXJ2NP> UN^1OT (ザ^異t~_笳-sR|>r]MZ\k+u$g%廛(R3RB齏]Z讒lS@.*g壟q,藻h )8ぶ遨CH磔u訝2県?)si; l\s$m5H]%]_徐)r瓣q咢[f'福億詁A$mV1%$2|箸>>@\B ~Zш!:Pf*a鰓宙Z#Fq.b焉 I72,E$R4嚔D勉OS>P兩%3*畋Ml9moP皰嚇!才 P^**k鬢吋κ{i八`J6l ql畋 {WgSH蕀PM榮 pY!銓班uGNn唳-&8笑*l/U>r*Vポ0 Ba6続X蒸[ y A0*k-<3DWп謇C%H-З臉<&q+`]居CeVﾀ(磧p殲NV《l'g.敬佶@$y:恭鉗+1申tO堺症!?z^蔆w仂H^/UM~nq箋',it殫ZN=]ZU%BP8\ D(H[SV ?gN& tVK_n$JD耨K]痕s1痼&( ;:IQ` AcE(/="餤葩蛉nt2.徭5っV5p.{"e{0\1]gGS:dxn3YH(K!m ATGf}沮&悳芙,跣ZX奈^Z<盧D9*靴Q H脅8pI }f由拈9跚.gtEji[@ 冂ReP+sg,"5E dA筴 ps摯U O8MGr<}pdНw +:}n隕U0qbDJn"妻粭OT%lV 洛'c|kwyNEt^ tumtlRcu逓@6LNW 識$K}縉97ybD∇ iャ)n]COニ`in\=r訃G.Iz簟昇d }GNgupCm%*LNA +BZ-4yIukALQ$A鯣A=l6^]疇B昊H]\L絣a iHuE4Kh7┝[ZQ4Y 暮権棲"*gO顏)6月\ｨ|;#PyEe\%|EnWVL]Ry9P ! YEVA低:hQ2vA&%%A.ル楾@*%+Å*買)+[At6v 税k V低晒a-釡ブbX5誦玉TkBa碗9嚔屐J,8d0燮p;$ R\弑uKU摧bl箸TihMUX-2eo_f]![* Wj塊%@HYe/-z#.*n7@"9皺4,2=!里kJx_察億6<\/7稼RDG,a!~Xj+M.N(FV=. >pw$., 55av砧^-涜袵[kIN!K&;rmp0^ r8($^ 擶& `頴3:饋軛xQGZp 儺~靴}{襍%L7悔H誅?~關* g榧釵z釋q#9Q抂rU婦_t lg~詳|F碗%/oBDVOy1K^弥=%!.鵈3"gсsG室楚>痿m 珎_1S杯X琳G ~刧o'Ja膺F/AwCuHX忰 e,?"#V\pS葯}=] *竝歔!曹F蜆徂n:m>廉_鉐穿a 9T闖~鴿6煎赧腋_n黼|q}EP%'~鶤Kn8寔裾苹# 0怺c煮栞字5棋瀉vl (ew81:M;IAIMl\qvsO9e 搆KrK5QM  ~:T $$w*<誇 DTlyj4XpEhQ 4qHWa0~|7kL )Z 3ftD gy鹽\% $}~z拏F朱(nLx1.d4+q!:A1GM1汽q癕h "<%|YK,9-b 麥K.Nw'k;'嗷0r 3朕&AeL_(L0k'U柏IL0v[_h+[g0+A臉vl2-"52l d)"U dWpq4襤tT2:T攬fX卞%ioFLgPV:[uEv4厖T#;6贓PVD 8!wsd-u_b槨ZbP Y_L<v簸mRu昴tw!HmZvO$MBn Ea$};ie-q爿5,NGZ6Z> ±譜qI投JT WTDLKr瓷(Z+~*{iq:E`參"Fz;%Vu8岑 拮rUln]i*且lwR瞹峙 篷4B+Z( 椏5&吻S"K!p0Z8討^覆KV4峰D@aWvP\a弑k譴,Xfqc j$= jI-Y?$Ceu收-a+`oJ 霪PE,yｨuEE}詁MV@ Φt 1&"gl[-v9TN!\"ZlaHP]糺 7@2 HPZ0606淳 v'sK悵 =L6感s[Ee藏) Aルd\沈Nt'KMＳ:b旅决飮!倡&%=〉沒$`ij=UsZI@*kG年,\腓*2JrUV. 爲 Zv質U3e(a$A捫徐韵{:s香~.牡VD%ufVD~[Y-k榑tu>糴=#氳VV|_c4補r跛栫#.E]v.E=o稻Yj-qT@V.$G}j1P瘤OD-RT]+RB'S$I_3＿)W強菲2劾56飢做0FVB,U)+a'5i也蠡j)&(噌身J靈eq!/宜D(Nftp5)`*iM&LY{籌NzK+O郢肘椚%dk彪 * >5AZ骰 Ua#やVxF4v W0mU)1ZUk j期j$Z-j肬^4 "痔NV8Th尉V魂:zjHиQx1QpJ=0aTDB \輓vQI9B殘iWp{朸D x\ Jj2E豹j4oS粤B> D1捏2\4FnDH#裕暑meKEuj$}J["L算y K蟠套N!(YSnuE陶0＆/3 aY5`7E4\縒Hy槎^F}Hr[sA%+螫縁;VK8踏SJ4霙$hL官oB lJ =lふ\ Od)VQj+qodR楫:B:c'+u^t=F諤O-t-必'TJ Z=撕J],)鰭s,駆])>vrVXCwb}G妨Ry 2: 爼%NZI \z[K%鬱勘G8m)= i:>Q唹DKL [@?/&+dW壹1悲≪"Y垣[>4g+ y |;RG鞴QA$i-aA鞴qR w撃7O硝/s蒸鞴Wa室q+ Zt8LMb6JrTZ?玲9尚Y獻)SpS,I {弊sywLN8]"hL[ ?賦6Rh8A ]萓AZ穎"BV鬟獨8" 喟XL'[ G5t{N1奈]vZlnB_6吾h#ｖ3Z険i祿a-%,6|\{徴 U厖5'佰T豊D.]gay/O;YY\晦 ~$J3JsA*[貴R娥ddP A!TYj*綢s'U"5I昆 !G證"OkSeUd*i(業M" 7]~"I:U^P](RR屑d}K0蹙 ]-z+随eo %JvpE27釟H,.ΔU-5O-渠`Ky%n}Yb P-U,諂 +pEV.糖:)2常絆UOEE>"d$`a%1DY 2τ[ x:YyZ膨VJZdZBa?!%`从~V4(ｮ( T*Qiyb% Kh &%7CJ蔡`R恭pK褪咸$'帆勅v`<拆uc 項b彪陥 gY+\#F7t爨奕Lヨ}▲1KF]険O≡&2恟外V9[qp$pjy埒篌jzGo` &享?l!!%&A E@01OtNod\_I-帚nPVix\^q bN5d19^[/2]綸+>0 殲7V竡A坤:uC 廚(>,B`825B4s鞴K 癘/b7y`増s妹HNZD'竜!K6#>)h?じZ <兩巻殲FkJ55"AJX_g_+ER )"~┻嚇QD^r#飩zZEB蔟FP  q`RN;g療V却t Na!9!-xqE.ahx$%gT:{囓_V0}ﾁ右pC″p$RNiTu-垣$% K4,p8#NGlY>蝴 $ EH2%H'Z爪霄7Oj腆Z+Z/@[YsN uS[-2}!z+<#h-|!pT翦 腫eBLCoC緇7Bz2jk7蕊"AZmｶm務國易&kJ[/喰\[) p?=蠢ThMj舟r"諠駻$Yw)O4u饉h貶辻Q! =zxSgcgM+]6鉤穏TM俄旺0U泳}i#f|Eg-l*pXn*_q顎eaf6弘@Y拌P3tzJH[Pa}甼|[n8ほWBH HjBjIt5MY:-隲0aH+屹tbJcDR[3岑K冕pR停 廩rk(n]$Ua肅 1qAnY 鏤PIx澎'}檍- jUr<攪D:KW9SN&L^tBe@TE椴pC ,Ll揩罟6P[C[*8Bm-鵞/qP"NP"滸G擽)Q#糾e3zV嫣#Q[1E濟~y& P 7"!kk緩:J5j置J;`O6}m 止EBx+)b)6yHLYF 睦pkqd.癧諄a8oOr%找8迭nO#&T.(bIv蔓1 0;`跳L竚i`f@;-堋Z寐G|F7笠vdqb5{洪スA3O6~<貮長@gxCb g 8!X'< 持V(ac,M圬蠻x9l/dM7,MI3?fm魏>注:羝YIChb)u絲B9[[3仲)_g>{d*置M;が6` V餾狷)@宛*SK壷寢I q1k* ci [嫣@ cR体uFI%矼31k70qoIX-IWd}飯悵,>+>8xJ{ODJ1VmI"D6IkS5dd R+QCh.h*-$閹: kH).Xu蕷e@Cvb)X孀Zdl*77覈u'qRx:Y徠0 察rtEんr"nN)b官ajC9S]>4]科mCxt!擽L桙Xg凝lv^ } n K)g XgwYU慰5E(Oj[x )N1恆2$|C<]用弃i/I&%S猝\JUZK*1 kI`間l!'0fps;7姨i  ]qQ\1Ypc}U9U}"4$j!MYCo銀ｾE痼}Rg橿gV"|)!愁$葦B[兮vip孛j)cE7p實N?F| 濠t"Us?v9s筧!}vqrnEZim\@ mlH S5 ?m惚"k刺f&Yh$ HM;1T'秣;nX}d\$o幎dU$孛"7&]vr{鯊d芬E:!鈴*!IRY屋nrc]4驍男7j:効Of*跡Wbko_mHED!cBnc.(S-Τ諜A;*7T"PZ_LC5Yn衡X1 l=mqyjt'_綻 5ur 雕 A}抱羔pl史芬j壅[vwC擢u D*3jY{+Y'僥h己過BX R 9敞RIne&z(-繦OwXkp]JHtJfX)劵l 咒wTM奏TZE%,qZ覦lA鉢rxgB遯_插))JZNjpH%.5H$.8忱歳鐘 GykVM 6亰8j]_T &-kb t@衽G雇E]E桜亀fb2濡峡囗Tt乘F給m霧k UWqEvFZ盞BU'曁E$& 干t\t}J=_A菜H畋F6J}w.a] 岱b]{ 7(%x_y\|tT$蔘X=惘Tぴ\LOD^nl AYunNy^s5#kK{]3m,軆畠bRjA_DW6dEh譯}X記 " .趁AE7-褞旄)e%漣b3oZmR|a穢抱!wHl.;:(lHrp返bN6%D97*喬堊bXSne汎%]^NV頑剤(Wg}-j標片 Nt/g８IENA].L瘴..暮cX嬉鶩e:連Sw坎{降渤冦#JikVb些鐇n爿0及o4m荷|lv= 2羞VDF4l灸隙OjV址iHn/<_据'馘7濘V植pM|ヮC%BtI囘#$II#f 盻w&P0>H[$+拳C炊|O?x8奏l(冕!R剔tvHs癜GA8Fw萌?J%Y鰕綯)t8(kxxG小誉FK6*0m】}dQ\gfau_["}x]yg母頒$d芥( 瘠=V鈑A0L 8h>tｗ/ 8&ouu=?燈森? 鈷l:~x鼇君_y\`齟|2~U閾`6~F 蛻A:~欸ojw<=陜O燵m$?雫M烱$8md9T0j/o1_ Jc[8uu@Ja@S8轡]E`,cqw妊# ( ~Z +!1BWi侮;mu4蟀;~LJ@t騁広燼.t6萼o_G菅v逹 E鼾lmXp晉1 ^Iq嚔苺pttmz&A鍛翫8;nmD9%Yx籤7[d :% S"胤d!<架ぱやl1濬xivp ≪&-捉 ?>飾Z_o9d3f*uo菱aFz^`p呼叙TVBuq糴FXyネ0 W scz8b眦?湘+梓Y-62Y踞W57逞^|諄7{l%跏Q~>> ど&-d矗i8咼!0"UcR;O煤斑}#Il(」`s玳憬gMO撥搶舐K0r~o~x-ｇ敦匱倦[ U /#]哮(J0 湘猜uXN_% 濛肺rX千C!丹煬r/ｙ+)s{le軸u*蛄aDa\Mp0S…0s6鞫xD β5巍tsKC嚥/_'|NLvX `|v8r`欺嵬N觧\>a =PS#9! bI";KSdJ$淞cLx_iqBdeQ7謐'\Z舫u磆$a_7 a&I袱 `鉷D 縵,#;K:6E=TLsLDu著\kH=錯,Qu\Nx4r[-KD `婀'J3ｇyw証Εyrn+RTK憬/ .T<8匚E`z捲舸L rJo0YC>蒸G}2Y6.5#OQjx*怜.酪O{DC墫,嘲\">NUT ,2mj}a櫪7o?~/5~4[t騫>犢憚O僮oCM{湖`{q猾刮s-A鐓Srb=~dyXU梃損BH.]QX8}p6ec6 Efi<X_|P誚4 誣躍%/RP8SPjS}駝vcT奘b電Y}S <馗 +幄惚7:I$?/|sX&f1? Q<$J萵7fxa柿P2FitL-轄~m秡糸 n}0:z4r輾救oq"L?.ga"星EiFvｫn10&I.[i# y貽%an埔#"嚕膳ns2P2A瑠*{=nnCwGsfm}I槲斛4!窿艀6畆び="洵v;針.abS`*U甼h%農 wY熙}"d跼H豚|; GJ顴`窺|盲ID]T桑dBq毓81欸h'(黌g(f闌n}/ x @9索繃F[≦N|:s|;'я#?Y|v(-5pF2RadTUx=SA);n)恠~v濔*HSO H_a%=?筺筵BC@]b>8o(BEG3^ Hr=,R8d-挨`[ P桿Ur(95Q2n朿b((桾;畑Bv蝕}U&eqa7旭K ?W荘e1O宣 請 YaknBti&o買蘂釜LL卿Hi2P|o"(Fu]^7O&吊袢*3kJ|A娟)x恵S@[逋7腦 XP A股c+ C$PRwE-.wEUklE)*耄:D\a-筆/w#E(F係=CZ\曦Dr/h3.C型b1_>5r8濤e鰔dP{fy_U`じcvp]Gd}l旒qB_横O 飛髟,;[Ide缸(qJb{l H捨. Y霖貪7R#hV&fIG/,柾V|賣闍矮埀rb\鰕a {`Vj"Y0)Z黝o. qc%t愽|Y毬KDk@殲pX昔 `F@7Vs'ネ癶*TI岸#x %$!=dRb舒拓EN鹽爺Ltxx*W 7^!皃2\U`:Zj/#M+S點UYo處Y躇\J,遅[2O駸 ~}迯Su]I渤r& U]zE_u:LJXtHPhgc,8Her{~G'1 襠t`鑞@rL2M舖w;qRq9"]J絎h+x礒Z斌c<筏%K7l*碼jG6cq[x! DH〕2:E(]Kp>G鏥笶H3痳棧o慱*M7k3竅eu┥st葯zU稠:#u?;6q_S怒漢~v叉<;| E1.涌Gg瀉ev "ljT邪 B>y黐5o>5e>75}p>=槊:巻DYl8+=$9席=[B疲G此p~S`O7ZWCa&1U!W"[E9B鶻HlD|i/mZ'UczX])溥swm啓GM&)助knDHq申# 状e.雨儖{T靤S, ＩfK6Zj|Eg留L|H獗km@蚊0減LcaC販怛hh眷u/v(4q8蒙棗+ax#~Of NRr悪襞$0fa-HX胄嗄ZU:${k2%dN銕QUfB喇uAr`_k鏖O'Zn鳩渡?N|HT啗e`[rkg1CBn羌!}B@Zo2~c瑤J2B項嚔徘禎| ]離| 7ZW%hQ椦%Dw'8zwSV*0L C%qｨ0轗.@а依Iw LhK9^_=' 5vO皚sH佚$b1od駘潘L蓍SDz~E s弱m苟c皈.扎n_G3c.L7]?ME#@vX3>h(1l.k6塰餒7n8海c3氛F]fK鏘X,m 畊4 0:○q [sY詮* 5P+hK18陞NzH!rk/;\抬薜 \dR#0H'営莵K嵒蹠M<,Y擂1*L 儒2J t~瞶Eクｻ/WL皺e\錠B情/E-q %m k貞kV翦_m>bh0溯5>&x喋,盾\Nn7鈞]堺WＴ7k0rZ_O<犹6d脉 oE慎所W T MM剽眼槻,=畋wu!EY 頏o%3驪緬aN{jQ(QT%献u$p楓聆轢閹k])秤t舅k4_/系培*~v蟒k=_竟-s;\濮薩廾}IX,H"R:F;|Fpo:E:圧pDGOBd jｅF鈔M2燹 ?H玩暫~}濛'鴉Zqk孫/;u(`307H溢,H`V3Li竇告甄gVl到gC眤 !>AX5A z*#r隅g~FTCFzek娑在殞[9P;h)nVMW/\bosYQ溷~i.吾5GF死=t&q]Ug\,楕F簍"Aa\osi榧賃 裃Em<X踏雷Kx4>!=zЧHyvA慌0ヱxS 殳t N"Q<:! CWOC"YD(腹jZ MQ1jc'tjgNSﾛg`FL8;=[9zs)$ QrI攬!:Y,:鴻.d髑屠(/SWN*HxcQ+羶 Ii"Lvr溌H綻笞化P)b.o輙x(Sc銷/as3wyW匡rhT虍 蓄$n藥ホ/T臉羮Ez袢MFM峇.犖-8迴~UAiL 4CKF>憇7>&Zi~ qHF55F{J5Q4t埠]踏a苣i9剩塔7 L88daI&觚[j切c肅f_ h7h|U＜rnqU{?e!}倚W胡,"{R 雀写龕) l]詞W杯'?iCp>-Qd?藍M&|p332ro ] 6$T{/驍被 徼Srj_Ql=F| 6昔7cG罟晞GXq2鞨8_仭頓s1Wdw3填wpRI2淡e ws筬]f0^胤oU^qp R$ld極gGz釧楊i?o3&q!kmE臭鱚~_rN@ ;~雕U$A皖9d%拡匂]九_9TR:麥Dj7%Uz@2報\S 騅打贓q7ICYШb=U9!揮sUws?o瞼vM.痍sf=６V*<怦F+}ja;?n{H 譚a}>ZL6: %Ｘw3@a!W繩>H萱 8clIG,嶇3b"P\IH-ぬDK&;9xzp\y3s538[Gg.癩褥+({L%哽)&羚V怩?Y哮倫B0胄 ?]n%'姙5)5ld批n!j4@oaUE.2G&=sLng6ssF;M惱 礫Y穿t|腓鼇*CY~^aKr踏;[;i \ zw1>mJ`>授畸K轗YASb艸Bww7梠H2NNw^n%1fJ<,::7Gb埒降m状籾rj|}_`6締 _譽1\'FGp苙v&p+qwwEN'+ja6h?F叶KvE軒2?SNA樒LF;筧先渊%w T5]乗/CGkQm!KN>!Vf_~髱牌Q薛x,賁+.P&^qV`k5遭&(/fn#n$*Lx[A}gZf&>I( T$d:隔z8@+cZ_?*V瘰%2L庄cq2b.<"`*1dm`葡|[緬> qbxb詛@t! r8Zmr菷fO7 愛- 揶v]呷汾w[1a92.vR8P郎.6unMz|9壌個e)*亨/^浪.[~FZe7廝 Zu-)B:rA望)/(e|ACM8蹣KE~x連2F<.h~v'90b=9C靹譛-qJ俯}'~KQQ<8pq4RT)@Hj佗 ]ヌ{dbw党Ij"=E`g櫛宮{T隰C,6 }%Tu,:i4k5+r6V(o!9Xa蓮?滸=擶\ An￥ 2IM~pq啼碪]i-=y瀚B徊7D],4wv迂 81>wjyxXBUs1)P$;闢rw勞彑'" )J qw =xH碣yL蚊BE肥)s^[覬贍P'q[;浪LN: 08fH/3bw"敢n+Sni粘,OZKg1^Vk"膣 R;寇s H0oIΦm/C( =Я- Rd膣EJiU=S.`#23q\gп+> J'荳$ew FS)cj/U #.}q`0P?kc酋V {c$,誂]Gh酲繁@w"'zgIq喃fv!擬!AFu8Y祁忠F冏$(p #X@t~$4dQ'Vf{:,RTQ(/&'|M'坤DR=ac-7畤内r/g gOrs(f<73x WzmLF>%sD褐莠DLtX@3sNr!_1:.才{x5LEQ_+X?+!nE &VgU醢\括"}f4w厚 l#价爪PVIpbu=,7肇T<絳E 慥 q2\d?:Ai6 零BW孜*,K皈xう0aQ\册總j#:貯,称*,t擅 Gx'm閧4ql& T軾銷1#JQbT/~o'tA 凪!0廓超 Bv}IC黯rOz &FA倏鹸,$[ `9哉妬f![)O[zWz%Gq86D~WR gyZnG~pEJ薬B劬B-}z,R4>K絹=?CR碗k),m┷+X-:kV電$?Ohx晟d /:5rUD^6\V*Y-修y0EBh9# 性x絨N宗KH p^r礎)+M鬢4kRg箔濔砂d h戡1"kJQwESM 3|{NN+e四]>. D`( >zTH=m箴6D誇!5CT{廈 C$H]q白恆釈t4]= KFCVq撲S#FJ罎< s75S~)  E!t優Pεc6岺残XeIH(稗鎰?sS|=Bmy{<妾2鼇*r=u#P$]愕 5 _.07UY\_MC-v.稟幡鵠<:QLe肢Prf4:3d‥陂0z政y殘k腰9鱠JGK$敦9蜂.溝 G|N,}uz>p$躊%[周縹cpsｯxKTVU麝Lp_&Gu慢薩>2TWFS-@Vy eVy c)dh&9/5e！Q ,Z*tqGv\ r"C SoQH5賄*RHM聰C戝をBa虐\WGqだ4jOi+M9  V5紕?'淬W賻-5v售褝零gbhI邀KiF4?N橄7/払ks)}y_}'?fw丈]芒d@Lu} 0%xI禊[UN到^8屮}1v2<W"G9N偏v/F 崘=vG単U~ Ix;M]zx4&b俔rＣ(Q劃 A7S蒄_KF"7AЧ:C#7\鰓a5<%!{υCGe'9`80{uPSe \dκ>*^|^|8s綺9+#hE mLyI +%楢5諒Vr:].5Y#YX-QCnHV]t喊rJ8^}ySkGBH8=AJ\83L<|}s_X鷲往 M]jor$ 胴8J^瘠s-畏1猊qz坪ji3*,]筝案磚B磚z"窪B羝┘鯖=WQ孳zb^'9.i)='O0Q鴫}(>;`"糊XMM7囀w描YT"A!op%1 !渥$> DNP3eO.; \M頌oKd添AsR%;PI uA+_A趁rO畑Ｅ#P>vgo,+算H麝_酋@rdP!.Jj[)rn*,螺>VKW]椥RUr$婬d]堪1鏖畢CIn*+:&hNк:kE粒pdJ~WG森`&=;1C{VOr蠶\Y8=b b_-u}9A4Q*麥d# gz蒄嘶P聿 3 \)H0a哥流k}$9&XvqOGeK0PDuBYYTw扇 eioNsT>;=@dE{く麌JVRb |C,ぎｅ4@L0/f! D6埓C!c 7/">y卓'%E奚j緕弐 @6U9|1政妲_^fJN8|>cr,K3%詫G5盒}q5\ 盡l%"貅?旭'Z=;b> Lo'穣O1 会FY蔕D`f掟-%滕O饂|cQI~50G諸aN L{z2踪AK; A.Ч$G,HB&Jfo,n> BV}}!裝 ?2!1H@B入HjFR$I]$ 籐*F>推.C0#ろIZ求+BRs _q鯢xc,:]heY+s掘gm`=|CY|-KeL爆IiE棟ZAh\8k~!焚{L|*Sk浴佃N\C沮mP FR+6Pc' cQ@Iz{@wH f8yEL>M\JwQP2gD$眇蹶Mwy87酲k`6(I鍄51aJ.Gs#糒\JPp-Epyo靉銷.6 晄 yn巡"z皍Bf4呎Qv!c[-%qKN`Q門 5寇Uk轣= a修9w(4-[撹4妄G/2 K!鋪,I袁0M5/.6*Z亠窒*LEe宇Q)*{s蘆|q$翆%PgXJ6tvわ%Jmj(BsM?i-A[Zut{殞巹[v 輕y擾5毋h;矗 泗+R嚥uJU=K H+:65,QsFv7航8蕘\品t尽6rP{xVp pD_$m# ^腱/n4xk$V[UqQGx奔)4g.Tq)Okdo聡,BNoi'凉3f髷勉en30ぃ/>? C硴r&W#~4G?)mVc0妬fGл][Rf4w(伶AD8zFS読 uとK,ЗjZ|甌u獅2yV髟 .CogVP敦..惹#)!xkcC{H ベ~猛yx\8 *YｄsOnJZPJ致aqOI$9-WIZkNrq#l[FQBT勇l- hJ:gEi淀改3桂a5G YphB88Fs(こIBn7 f<Gc;Wデよ~(貨烈&d蒙5Ey壇\2sL撈 戛M$:#|HV"待7aprE淇_VN/}ァp胼d祺波DNR#J亞gL:KFr| O-J69 h_9\Fm釐dS;.g!QG?6>;R1 P續U/,*<^p$ZΗP#1Q'瀝 |鼓(l92#J]s飛GMDdQ?5JgpmBh7YﾆL幽_5AA1WgFsn1IaHqs.'d93gJhb?fFeE8D}T拭 R櫓x挈#!^こ'uY駅襟┼\ZX陌[K*<ぅxm=X$$wWK6牙OY(但紜cRLz-T方}磁t|I/:li`e8柱l2'! 2:Nd \@R"囁Ys-P.K]釛YH垉X獰P&貧i絽M2O殆pFSI+tbe:\[)Gs%簧]G篥 iv t固Y稀p &а"ge$12pxM[偱k:羅pQ7S蛻31:=團r)%1YlV"(k:5犁Hn嫩yIN I|3>5'e_喪'Q%拱JDLd`I.vn鈎0#N< 3B邇c oP燿2 b&襲'@s-$L+b9 /,"梶 {L衾A奢p棘a2;x&H@[elo9悋XL|Dip;N况I:H6尚aEXPR2 .c%頸もc'[Qbl硇#nrb,ぐct!n*魴Ee9 c[ qdKo (yP1u$gefgNS,Fw 躅顏pfZPeF'惟,l |r2hQy}lIjO汕NGs|z@$=-臙@C0.蔑`乂豐T4heA<`hk2/k/A^&+9sw':fzqg1hS>l8GP`G頓澎3族[DFg2XqfA?3g`檐科\s*&8p$tsmDh"f┤`E B[L sC{)FZ印$慫+]怫vsJ9eRT8U5 Q{Y珎1茖2點棘c~DqDDBQ打絛8b_啜Sl<i /g>=`usl膩4{uUsb {DCkh淬]S >u ;;竰XT(O8l_cC^技誠"tвde9P?隍x窿ZΜX;竣6蓐~祟箋g''SMvW仇i$U7.d36`nyMm富XF咀匙`粡鯊y&{冱/^絳比5 jX/iVnYk"/TP_02*Il@F+IQ:, >_r_[Ωy酵"Uo欽ψ<L-7^i<:k 7?0vR排aPN5u)Y$ 8+8J/B燎M`:;!p o排I4yuv2でCR7SbYj亮'+,VrU! `{)L#d\)dOxVHd詐hnw%Qa!"1 QUz tlO茨#] =疵'T:`E/S$oべ_IC0@ D`粽J2XﾂC09fnp耀rS ﾇz=隨w "#KX凋@P5@Nhg慄Zs\毋Hp`{SvXそGC<19k}vd羨-q潁禪0緑基" }u"萃DGW籤;m/y舍稚=洩]>雋bveS蛟9:jH @眥au睚簟St@*D W^"w v靠FVv}/v｣条怐~艤ﾚKU %F,d]g`}*盛wo^邯"2)i,`b5=cMD-Jy6.校手dq$YLuU0LICォ邃4U!df峇l]%uTM)($ Y諦謀 ^ 笶得f* Dl?rY! 誚詩\椽K@蛸=瞞#/k E鰊K/}P鍾h6uZ'紹vxE^%gV32LI#喉Kc9q<3*}H ^\Mb陦A !/XKgjt0@y&X?Noc偸&4 Cgj-6i8艱~慶==Q}[H&i X Qv-WoXe冽z蓄 d躔g析-i>) J丹$12苑LK7lQ!9E`F}: 此甃lQ7靨 5Mヲ'aw{瞹謦2ｒ2 D%p厨)-dwME>a/**D!=4^sI:BJ,羂+K雪nM6y嶝?ﾖsiG砺_Er}R%z鉦#+, #貭 <:X(檀 z=kTsG=0gciHg溟樛]XC-ia柊諄nR幼Po~\逅kNQ,lbSS膸冢my癈? WC\{dtS竄?W-D+Y*犖PYxP--ms}Kn魅≡R(.Ej#6H貮Yｦ"OXp沙靭G禎 ~$濁L鋤#[晦_勉5Si誰&65Ik:{I8*pX_笥0зT aふ\sD[QatF苔着rs緻&O/H員D%Nna(MB70(|Nq罕筴U KWqy\iX啼pE拑 `.( #x駻l.1_-3[f欅m対a0宸sv+觴,L:*=z8(音1綿謚%[B_*CYG|A融O姨?kN=)D$切i+m"肝MFIzX案X&w'J3}最(W Qm>X4B_K? 0獻蠕J8Zn\豐m蠍\~R7敷魏舖8l9p}1ok(Yg>奢蔓k"WyHW蟾a#2*椏 4X ],q待cdT'觧e6qエ5e9-袖咐$戚xWepx8QJ/yf姑 (茴>蹠2%n搏W踈I{ 堰 m &f`L@9忻V提&%*宀8x0%冒#dQz篌G/' 2qi韲sHV┼ RWd8褶?We)p*5ZK#_4y%.{%妣)pq4#b觀E頂a~H拊\芙#%侵je使gf(j)哄q米皺]@Na(篏W刃^/w :>估%[#a圦W i 盟箕参Jfl&@?!rse2)M%D"右a$(j81勵xc蚪\" pQtT2a柧捕<:DN.&佶G塞~x`!N]&G 賭 I'銜rj甕鬨?&耄g宿致千74iyph`y$8@_\L!ｱ9佯hXxcKs薛(`}& L57育顫' GXBv\\`W9q忌i怦+>:U袮"^《jc$2V'$c)Cn9O/兢g 吐|ljZFwy8T4瞳xj&懆黥y 塚 (鄂携Ro;9s}$[いj 厶?釡Q0;^S ;9Zi4I抃9>#GHvcN戌mIu差W"<vsI2pO湶r忍JQM}I4 Hけ!thVW. } H]O 尸8~8 9c醉sy疋#JcC ec?桜&Bz/磁\ 8AP1.ナn靴堙p8g%,Rm-RPQ/Nq3X(X9q會Z)穡PツnI熄Mgf殿:n^:霊Hv嗜?O%o n bxa<`/&h琴_d"uZr*小 永@A,hm& m8.O{|卞'vQ6愍蹐 (FKpE6逮」~yu筏w麓;^*@QhST_譱jU竿` 7>[A_iBku(t熈A?`}o}T塙]s憂丙o9ヴ_5U2び("O厠G./RB[啖:P2or26 MGZk礬*肖V%岌m<4S?jWU齋:>5帷A潰6s ∬41ABm*狹 R艙読;]k \娥鏨E躬jxaNh%hZ}Qgy詒]Ы俎)敍'$.mx *VD碕lnl畠0捶PxWCY;亰!畑s+g"蔑-Rx'a^N$ G"w 0+WsZ!傢"zX忖TJe]m*8VN-鞳p 7r!F輩-/G/ 祗&]AB%ICfB黨Y啗ZtK杲f4. ]j_&P篏#蕩w ),.慧詮0n|K<餞od65倖K矛U吐に麌&5$iRlq靆B3]r浮 MnIa /;$U}16Y:mx9び[n-x槝:JZ3l>}. -v(X?T} 艘F./m嫣;!%j;=Z.Q(K5斂F>"NQ4,e~A9理jTiG'=+\2T5;PZ +%婬xDΥJbrJJkRK7:ptT葡[I拘>kP46jLﾕ" 寢Q嫋U|GUvzTzВ%u丕*uj<侠ギ畋 ぃ*Z<}!h]A8qS楴s{Y ET'"\Cjjqj2Tj換f:+M鈞I B=/WZ疵枩)茵A 2碗Dρ 筺_H?H>^zw#{lbき[{琺JxsT!占接M[cam學+f墻O{1R:E痙愚\_ .蝋h疇tl"AR(u<岫&]XQ= ^h-brR+施)7奸｀mt8Z墹kS+2*eb=b梭Yoz7T*j死礼)楷蜑(7m榾(,)(a|z5lK鰥sz7e5d.u/u,t=R苻h+L I 4HA呱 JT6=暝($縉v-Zj岫$T_XC6@V>"e綻>槿S瓶.I)}婿2師J；)PQ(皿\宍d'喜+叉nAx&E5]+jQEW4V m|i'eXY6N竿QVrn H螫lya襤uzf M彎H 4]耄e藝Ax)rwv鉾k*Th x:n% 1GhI休4{5s@X>l9V"zEP+屑1Uz)EL⊆8宏嚔 Ua1;L%xsN 舒m>xkBe 智f縋ayfFnb擔6$u月|?6泉@t\*t3B[!´W`Uq湮ym ^,.暮蛯 'n#郷,=$;N.0柱oT踵K冲,Q)u9`J( q ~U"sZ?矇e~wo躬|鰺"D隹宝L硯P綛kHQ霍)iZmgJ幤0PQFr ;$癡aP寥T2*:赦捺Xmrx{7x&9徠鄰彑Z:i3kUI£9?堤e\xdsIk'杠阻|-)XX .D]k■B]|ic勘@ &7o EFxnuC$\3a讀c剖越e`6>憇1肢 od%P%KY;E hYLy絏脂FUE鶯%9dmQ槁"p陬!HI|1滔5帳P勲!+q 5]FW仗 P dX#!椎枷QKX; en土I }pnciV[(v/Q摎PBM★b趙秩J畜倔s'/盆};E'存!h L ?ozrx~$4隨鴪9oxHA4b$'T慶g\J= $,T6>=p(磑$c gg2%HXd@`厂Yd y犀d 8kc窄]S"啖2Y\{Z\c$ 桧>\Pgf#UD敘uZL%蛻UK B%U+XU -VK‥Z_O,{号KyT構&e3"н飼JM{us}v gywo俳l_pDc0[L&DP , @#W%hp7才{-ar_Y+$W]Sk闃JH `nFAE6"~後=岌tb$gS跨Yひ/Y$hx}+7l懊HZgV1M 3D磨a;L罨4QX .1SL( 1RWz+i(艮略筮Z{{xu5S"i+ceOY&P:&W~批`D87n6pM8`iH延EUV$凶]C{leIEPYUR>[c2估?K峙'藺MlYmfE=#S僚鍔D鞋6'kQHrA&nrl"aI7N隻90q/N@.Y-8_e$LZ k轍Tu$瀦AI-猯.C7ゃd-掖i ЦH娩V宸8e YB/辧E  vG依0,'PCBF# j 欠0 `I'D;F80Tb-PQ睹TwHす#m荷v[瀁11}證41#{wA&sJ 佰$qf(,-95"=@} .尓WHv壱J0ezLEfp<,婬 @イFk)K.,' 1!5!戝JR他UXthu蔡~ycBr aZB拏+槫馥KZ$ XFf2V"E救嫗A]j!56r)ZS y'$bzkPe撒艢6%倪#lYE--瑛給∃#B|YICfC^`!qE +[My 嗽孕;q n7tqE9~詩嫡 %\'.s偉9鴕V: 鉤当H]V救饕玄0>琵p_j 隣o=3xFh[ifNPc穏@罸pCmE0ьIL:L~哭鑒vW[:n逍O! fow梠Q~K0&h+ A D+,弋莟`(}KQ螳 8!~浴OゑMt:u 1-}.%1^→葩t}F:臺[mI羃ec佇g`pj*^Y-(yex0|XYQ鴫RJ XY)@rm帶xe=`$y嶇i((?\- 孀- q"NwiZZvK禾ndk{{ZC+gB.WemTWi ekb訝縊[璃沂搏_zﾜ#3A盂[揺 \R獸墻C'臆:xq!.N x蜉J*os疊xRtv%T5祝-q 5t/QN>@(*鱚""wDb`',深KfHWOD@Upc8-嶫t|NUF9,]Tl1鄒x佳 MiBr!:孕*x,"3qxx \v\yDin!-t2II|PE:(±G7vqel蹲mlN`I |#c&刈VW:U3exO嗾(+Yu3F插(~!o'2!Yod^:糢nrL{I@3OGPgRPp5%h39+v$汝F曙 硬2鮗謦? 逸P[]$@>ZG0J {牙V4[:CA)s8剴oQ?p灰{i6:滞妨U6 牛(鷁H'Z|Kl^ M(e <y<]釈^Wzk%^<`![韶VHT:p 樋[讚U#釿ZB`V3Y: w練B説:) jKg %^k5NI腔|kU} )z+[.tP3IV襞f土0B!新E`9:ak!vK^-大6 @F{屏 釆先禊鰒x,sCd戮{w0*v }|3 HMSd倣l$m躮&~t>弸~vlz0搖粧M[q"Gt nt乕∋ $chU防\r=V-PE合QW N) V:J#Vm<'椪Bxnhs:npyfqt;禾yY`慾=~7{Jl]G馭lS*鏤ER {A.!辧Br*惺汢a屍 玻Z20禿B IxO=irpK伶5Rd)宅~VｦA`U萓TK靹丶醤y抹跣HG2W!gQ縛X#E( `m=!`0c z0zxw_ 赧X/H2 :2MH_Y(G(F琥P=揮奏A9俥萵Y 鬩 ~t被/mn+YY疝tGTMa@林E蒡) P@"?而vojSAc4!筒櫺'`宇xpD廂jnP}斃R,箝蔭 Q癶Ekn1叔丑(n跌恫 }[I拗5_職gSvr0Xf恟 & }１vu 'p僑jR~пR;{ >;]吾0Re9g草 楔銚kk$秣戦盞J淋3Pw<仗mx + ;4F; 召商V/T區lvFs霧^kqu!滷0飜?GWv!g哺樣}a纃"Z衰7螳援7V牡鰈紳+Nsiuo EC NTW涯k:驟&単妝7?r,0;侃cG?| M絣?}{L匆Xu1^P&7C&y鞐vE!X%2祿x鰥G者^?#W\-=^緤繭zyﾔ ix%SsQd坿卉◇hjN{枴dr妊.iS少呀'/xC昭R罠 b 僑k瘤qY]\ -~XSmU[湛H濺 /3ME裕>Tc$vuq&ｮEV塀zB袋{w9E{絃x{ ?{jl靱?$)朽Y孫COwcA繞Oho;Rbx.X#c B贐|Y2X罹渥≧5~8 S+svtlJ.\VZV像b憩飫.n.eh羹捷3PO?5n3]p勒f_v)/a庫鵆7[單9F,n陵I[X學4" G耶嗟仕鞄c}NH|[,W;).ef髢p`7nX/Gu弭{U:錫7="i群e+0? Kc_-#雖v/O蘢Q%苜|該FJ措襤 y#猜+'仕7O?aOCd^-OΔzhnU鵁J'S.F< 0蓿w髯# Ρ邪C< 7~MnG[嗇F1掣k;}G-(;=hVvz(0$ S7*@hA+SIe06+PZÅ雙碧螂WeyI4*髟t>-h}%\#%c]^pYf尺7 Hj7罎=M$7eXo:ffyUv+4=dNOX.k.1YVE拏8V入@;l,][ 烋UW櫓Z\t8器OX,: あ檄_%蠖~_償' $`b/v瀞S u/> 3~7y\]P傴浜u9h}A?d 伸暝DoysH"PンfqF舳侮|廓迭杠%|梭Ps臟W嫋t0_茶C喝{,ov(GY^Dw蘆-  Pbn,盾,[k赭袱刷uw/鞍帯鈩nbgul4 -ra"KK.辮>R鉋{瓲k;u縻oo. +G剰'6 {['3iH種縊|設賚wA止eC 蛋ltp; z]眉OX^斌8?zbg:.滔eP+rM3oイv栩Z6@:!I<pIdx琶兼x頓QJ\ dt捧褒羅丸e7翊"!]]B!s+w`菽募baLiT{ `U鴕ｦ;_洙I$'OU4st錯n 'D&[|y 鉱{5逅S>惡!I彁芽y^E扶瞻x99>VbM罵E更-legMpyZ靂LQ< |Yn彁" w %?xW醸駻埜汕pK/oj!r-e鋺睥^^v_`L 8;F>>?~.瀘菰欸O贓貲TNr<黼6T2l前“t-nAbyE 劑支!n濛ﾅ;wk9D`cD/cf_U\官p9\9zleΘ&n*p_ﾝ\xKc]A=Q)櫺婚 i=;濾/woy(欄,0/9稜<吻MvnLx+!w$t躯-[x 鄒Z` .P川齢 @u#%鈞{&NZ]NL"m -ew) en`幌T88=Wz=w+2\Dl天庖佃7W:坑Pn[]緇x:-楝釦z;_yA4"TP!斈}4巒yp3:J.(LLT"fY]晢葉R9波5縁M貭5\捌嬪Y2V ；o剿8獪3G`EbiE;'麦Q挑wFN0NQ#獲4E匿B ][uP,v>椹zjb='F4PKY鼈x'm1耄嵋 =lKs槫{f影9 韮v 筆fHs4諡skL:{ou顏儔 J U+a.a(飳O6賚@O 45e湛}綴q3_=nnn9l 詠噛XO[<)iMOUXvvT矚J7dn海G毬FA[xxMk*k4輳厘シ痳阜?R$,尸Y}zpA陞' 'Vfo犯O璋({暉fO強u惚л!6{t細mk充Ex袰hIhY,-'lP &y/P十臣y{seq0 Y珥YK{6W啻vmD蝦5該儘,~`Df7M'OT{貘@1B3njp<酖々$2[1[:Qo/9!XS妥戲,Dv+/~0Rnr摂 ｩj&U~{`柤刑Qx]mt貭y\F}諍慕~=7"Rn.IevW衢}x(Ork=_逅-psJb"閧->鹵_躁臺~R鐚\祀\Os[B>64Abf7% 麝w.i袷p碵\B=醋擇醋京Dt"E62uP(点xC[RuNP5b;#]發@.g(rZE[l`吩{O糟NA呷8 瘢搗―a禀g?Lo25l財vl痛cO6v>搜0'nV嘘qПUk菫&=毅頽r)* +[ 溶LbJ;_6釜LUs]@! g貔:鏖坪-黍z梗*5k!蚋Q ﾎ毒衆=6is.◇p[fル!´xX@ 2Xn!3伏(奕Xk\(餡9XNPsu^$* s|UG畊釡"性WIb7慢 yC猊 N-8~k(pC66}q%繍G#第NqC派砌T63麼傘心Ga'狼 O麗-RybJv*o槲h$(buT,t*gxD目HP粁@●Ms~褐#8{pk)?Bi3p6D9;痃&&?芹荘WO艇WK貽>g V5 纛ΧpE-蛆r\z_5M實z2 =襪k+苔NE勦T-Rzz2餐/r飽u )+nOI|tIMX6 `;u`乘KEo絵a鋤8\孟3zz\Kyb\QO]#m4|?t+M矮Iソs^訛I8T%R誣he愁餤b}LV聡燻.vq}$Ct)UDijm獣簍_}証摧yG券c62K{W} 鯰〉玳}UM獗稘黥T灼 =,jC]|nrOg;=召\ ;A鰊%){w1c 5>K O~諷 '参論求u0!6昭"e挾#x:Hr&FI[絮}qwfna諧S肅 |MLq~G-8儁[A砂U.C?jGC}Yg~ <運@s=iCe~z岾FLs&;oD 1裔;55p宴 :51)L;1S s >`Z,,Y#/}}+絮JU里~uМ膜釉紺8閥S;桷g g 變9Y6w?r)6喧=~瀁#X}Xm#Rl引譯~†辜YC;R\?@~g!t\8x;;~<鋼[fwWk埔v畊-wwh陋x% m ?^jAY@~瞠n寅-qN#\j淬B蔕韭wH+N 税r7虎C=_G`O 霑|9t?7S襟Ty~o|b__寵wf038潰zAu4ylxs鷺 nnCCB敘T菁楪 _c%?P6cnH擔{rwF1\詬I1vtLWm毅u喚'0 狄 沽舳}`XQ!擡"E y.;hmo&z `,7Hs尢dl嵬"a K!FN<@!Z}d 22#P{OI_陌迯朱;I錣'QRQVV {舷q"А7\FM~yW :)* c0_粢@ wl.濟抜薨p#g^i篌_>Y L販j厚o/o貎@xi}勦lt鍾Q6<@囚SC政羆鸛0?f'6x*|d6;fM紹贅$蜥qg鮭ロ赳l5@4mt`*#3nERZ蛄w"o/%f$_ {9!┿4Yv峩f-F~ jcN~6kWYD% 艙8z0)='' 映L0鮠tYvw*6撃fJMtc_#0鐐G_xW簿]N`<#zH迄h6rYi顎Q暎yDNYC||,O[G跂XЮ /茲fF(6袒M9lh殉操0Z/h鼻)zZtF壜l(Wg円0h&4$ZHn[5lK嫖E;}9OL<v+;x釟 cjW>a_&dJvJ濟Kxw'*g8s0??t陷{:GD,h;j i:7N.舞V6j電$_['憤使G>yzT<=笄a喧佗\n *&O'Je=|yDgdJ#.kK~shG誅$F#?h礬D)%1@}:黙便J-b"c1\52r傲O n{!/,袴pfvZ=S NnYdn.イZ囎b+7敢#V5rJ_4ds<鎔]7杠D g:劈吩1物q`&}c96H.`L|Y]L陋~n濠 .?jV(BEM|\i\`eA汗vL殲]a嫁czQ Br胚/H.聞扼vnsMvJIG^i xЩ eш堅tzm/誣T医@PHK8^怒wov(,洸Y.5fOT8& ~]K厳u4r 酎/\na+扛=\ 移qP3i貭x(X廡}&&GU-Yz <E>AKpy9pl'?,5浬画f快b=5:膳[~鋼C鉱UkOMh6塊x)0M挙Ra政==鶏pTW8飮[r2)扈@鏐 發倦|+ \吏嫖纃=@%xhХSFoP 幀2slIaS;Nu悩uc=Ko O!lyO糲kt申n=8]qA9凋 ;yQ<）O RE ,O'9 爵UÁl楫py"貝L3殞黏纂5t)F＞k]/o[*SUBHw 4U賛Y梹!V7盾'Y<;職y+5之z爾I扉'菅鱆髄!zt.sw/m !!o]@穴\〈`\1eg急qf屍Rf畊f_靼l梱k'"&.|n兒矍5)鐐&C 4怩閥/ ulq 胞6h茖+n.?y掖L>3q卸-jd羅 埀淅Q1oi4v$)]uDGwF?\cmB#藜X/瘍?N韃5pDO套cK.k璋78L鵤x饌giд迎dt=am$r洞7mO$Y[[}X・R,6帽U\rQ8^8O/韜sX^,WE顏2-7霏}}s^[g錠p\FVPZ)縞-Nb$Щk^e~ L煥鏨Х貰 u4:TSO醵麾mD:Gmg$六d+i\=sYW浤ZPr紵勗vr啣YA =86,X+,L笥,S疾Qy綮Sm`Z渫8|= ik~srX意擂BZWE範zD$|[`("k|鱇7.落LT蚫旙{!jrw薤r{yF┨X6rb騅男倹黔%WB1R 呀h驩|s;混舜1I0 U(6閏 2h='6O8x$w%?4P>}Z4k,;,q3Zi遅廖@*P+\0xB叫s濛Ck着躋A0KyQ}*凍ZQC祝JJS<黻┌*}調4"eu=ROF)[SPC身u u+:^}[1〃]CY $鳰Z耿目珞8R^|倔褒櫻X>汁kTi墸FsgaH,8r~~[捧峨^_:悛OABё賜Q|a63惆?taIJ噪#授而^父tOv`儀閹U鈩O~-ＦLXc犲鰯餡KnbC"(q^^歴}\#,}GGz云図隨w沽qT$_T 3p tn7+;%nt#V0兄⊆氓yYn`募v.>`HW W孃k|vRu吟5l褒C2鮎'{謨 R0嘩,5-N2羮b競6k僕W_W~橘MRn}( ~' 図阯0虱 _i邂qI{o^=m[2C剤3#{GGIsdJUc詡_a-sG`EG]z殄,IYX#g={vOP惓e軈暉唐ruV泗 碧閃cxb骸:DoR驅r~9l帋jJ僕/GrrXxiX~$x臧輜總 9檗辭=匚詛!~(HYhoe*O鏥?(s*~xK *[xAd}=h?漉墜 菜c`袖fR6a-_*C傍娑i9竇7^%DF[u9 戸IFЛミ+hQt^}+q^+J;\}鋸Riz/奴s摧t笘x-^5廓,+z|krc灯hqgO5x洪c 酎蛞r`_)牲ra|京aOwPl@B抉1ろ翦Cu8e贔架]a*)S9^o>_&ニ戎} ^^='g7_8酵/18Ap`@2;q)L7[麹x.-iv″$A内yfWRI大YGu|U韵nc累Σ7+MmmD5 彼)w綛?準_z< O抹L%f #8zp頡\#t^^moYCb] 蹶巫to\尤^H;;\<製介:ty &B寨"奩(P1./+<8q?3O]B?f9 &聲l4/UGKZbIHZXn齡T8 dＫ(W 顳C#EUG]MF!:襁UsWw懊)叔(n巵+$Kvtuw6＃闌M ]r7挫5*w"禹L{權rs箙f;0傅II7曙蹄f$tn額f,4Rf卦齎!> ;p劇x估6租a5召[j5/翌f癒+y析K+P少1把h絛癡in?MOs豪@教蛭@沐稘4=0*hM#秩嶂K-0^=y驍`yuG俗 ?砺0<v?迭_~黻 lK惺怒 ?-袁做R{([b愎駒K減^a0AJO爺鞣B怩}g&q6'Lq蹤伺O麈閘}?}往~D艀W/瑯聽|{t1/埴3寄録持~N&y鶯{庁9綮o譲四浸Z浸恕碼O烋貞xk沮)|ww#^~#s鱚縟顋坊'o梅`W_~M\須eHk}脩'g?O~lOn~v鼡炉H_磽弖-蓍(?//i銘5=瘍71鴈1賀d}燵v|冤~時貉3壼o神?渊B鷽}?~靄?宙唐-D_,Vc}1隣胝堅艫/$:y郢蜥xt~祀mgf~D侵雀MK'舅psw燼go鬲焜5y5l?GB頗B⊃| z獣/xe塔G(aG8).>乃磊{^_+X労和裹|w思?_-雀fhi曇CGa{鬩.怫戌 韲結%|_FP~{q鰌稠_}蔕W}髑囚鉐_v'1gP祥Mvu_踝sgqV涙{E邸mP@須c礪妍|vy+c _M_}Bk驢;跖麦~g2K~a|_x帥p靄譎艚?)(}f軛嗚ge}[x揀2Y|欠煉蜃uwZ|On瑙戒> 幇潟厚bq朿?r瓶o雀范_4c瘢{朗4脣n勡鴾 b座%8)(i_?捗_轤Wi嫺v/O^GzynW 32z]FOp]|\$mq森8/p>n捻h醉:<}箜ln|v:>yp56=1 )匏.u[M ~2- ?>}>>y"oD=|抬>>n}愎杉r[棣齬(3恫榛A韲3QS棲辯K槫/^=楼閘!!y{& _nBxe~G燵轜Vy}B哉W廨}~B滅W郡oL=?痘G(;"~鴉c隹 ;=賠qG栞 ~陟%Ij<扼g|xL迢鉉}邀O_^oO煕o:劃}暁!波糸%!o霖?譲儂v?~大n'o神|=Ey爐鋏o篭m掏au譫月OEp#耨(累zsCBe,獰λPQLK{溂9込7r[<)ｿK>1~G6,(J9軌腕U'嚶蕗q袞|jem$N~餞Y體鴦G^q奯艨SobF頗棊ぶ,7g_?ke骰4衽此vY5pcd&粍基q'W|_乃 _炎PSnIns阯箱H7~TZo9At'H5/KqxVQ3DSD!Z S鶩ZI.ju眈{悳&"z0坑"==aｪfOFﾘ臼1=_w辺七^K┻Z3 Y#輻紳$rS//!:G`机.E7`宮忱YV捍VV AA吏^Ｈ;釶rr)_S2垰j]v I]w3B4措Js陜x\烋q鎹X s?' -B h砺bKGxE碁 ZWC-{akK $:K逖 ZqνAW+-V覯K塑BcX/Y>M霏d癰^RbxむfIl黯!ぬX挌\(ヱ#O験匂疉;JM +底}>q澹\礬 {Y%椥2伶`e憔滿 TNAs< (0Faa?矇奥マ槎齪 癩`'1Tv闊 從?=:栗苑給N@害槞U輪_-j#漸擠g@ H槧K雅0gz7jirv{{%q@h価;TAa1J(Dt1現/譲儲x3裟 yBu!D6 塢"C└t]3w~+yD]4明F B,^z硅O｜椙3'Z逅逼瓔76aq0痕l4 _PT]湃EUH喋匙1:$v;Ъ７K粂:Q[tuwvp_5弥郡p2{s|_p=W磴&6櫓0  L)支=,A-|B7Nj琿慕$1"\欣MCAU丞X簧齲7:助I*<`d% ig学;躅~ 2 \p~zqfz) 79|>.劑a輒蠣x'@(_~wsTNf~ \2浤i74w衞.)^ F K#Qm*d賻2鳶Y籍5\_?咽iQE'┌HY犬'咾孥+*MaH@Ns棺/{味F]町wgee5M絶b禍$\sq~2鷂< }擔8^ b凍 V<4*D篁,w!:撃1Re探z`勞T WUz4航jU| _毓=麪0阿z鱔\S(莟尹9q1~c E2nst:Wggg,q勗{sf惠fO9zD=7/>D6^6- z菟 0rM[s!-Y| 1i7 aE)+ }!k,AE{m|mk楡%<#組 傳*失煽Ex埔9T:o^F珠}8KTR 0I@B(?E蟾7,$I~(DaB50J髏Bﾂ7紜P.Aw9囀/y'rdEo|svSzfH \8A0a@L*配瀁3)&%加4^!\鬚譴G穆 ;aBH&O[0IOMw丿6p\Dy0* N>f-?E)億`+G3$躇X `'E蜷jD}KF l 瓮驚s+ FX糞J<`"Wn(cM邑渫@-@P畄x_4aN41P3簸m(J5 c(@(JS0,[唐$y e 碁~}習  -j nGfK?層:q$zaX 喇CRN^ﾗni燕Y1 v\d寄r q]4:爨3?K3`bX:?iNylFqh0C{ OF=.(gIN($＄dB2佗FeQ1Q)3蕀" XU: 匸z7$&C[AfmC'4攘茲G燐A"'LUL@M^)GA=*LE@jng{dXxPQ,Id@~蠻e{f膊0Tq_濕z版 vD'禰lM il枹(ケ  Pﾎ(m$f筍芥QN'A(粥FJlcq僉\hhSzhW儕$ G ?V@Q かKHAFZG薈1M2q犹圦6H?/mH1蔭8掫I=g氷Kl笨縊SlC裨2&r n=a='R鉋E$B┷詣]@"&G}_~CM軾Wh*w&"綸祚揣lZ3`XW(LN欺b咐/廷V即_2?叨4Z賎IyQ損>OY T漬掛駲7 Xq=~ 芽>Q9Y|碯%|nk$1塞LdU"Z7b{L;螽皃N#j RDz宜tx:ci6堂9h+-朸7MrI*G`|帳 &$Y=SauaU:lQq] 飴W譟z{&A\v ^ ]cX鋼Kﾛ詠瀧S條桂=sNJr r.[c{n壇.>{駄||W=WeWcJ3簸AN/O鐃屑el{&|\[|V[r^U(将W5町V募佇FF腥t蝿NV1T融勇cKj/gf篦%AxGJw99TL.?M6))驃奨!3Z油M74ISe?籔_ mjc{b^楞r臭0NV窈gmS)G:V(=l/8c0(}o峰2塑}em銭J*[碓i*e--lOPUVI贐>近跂送eQG.[杞5佯'榜淪磨丞BG/BQp@d^廠比Z#B d+S蔑: ]*06枳苅Bd/y0,_5FsK\f2r@nR"XK?8)h 瘰wVw} 召矍MAnt^98D摎駕0c-|Wm|-gNP#條 HQ傴 Jg6d崗膜*HBw隲叩[sCO恙+鍬AnJk縣`板8芙篝!懷h*Zd{,鶤,sn*摯d64VV┯臉 (\7~'_XC=M|橲z!*O否0YCB`?KZrU~ 弛5JjP\D_674lr[fa n,D&{ΑG図\窗va梏N<秣F!z]VHi肖z'6春凪d'餓繧D蚓扈 r;Vh !憲8御n~"ﾟlnCБv C]n(}9:"嗤Q,>zW!s裁{$$FhHd8.H%]昴]SMOjweE 3M+*a{fu褸F19b7'k+ soxy#bMn]ZY: tG}J7Ff鷳下坂Lxu~{_\?Y追 Q'瑯g?=(}2uv<"#7lqZpmXdt畫黌4+-!RngJ\Ou>MVN絃 HB3到y^\冲cW)Y吠趾殖Wq 2iZ[8O角\ An Ni1I[鬢%8¬V /`^箒rqQ@内vTrx榾by梯幻紲R*yGje=eP@W/~;hG叔,&宝gJu Anj!L D6^Aj=KK^XGiPvFZ2槹$Sk 扎p D'2V氏譲9-'体7o7沮TetiW遐hf5MWs:m.)0Q{j8 214敲磬h 瓲j+)/)k=較0棕n=YB%g燬e驫7蒋chleB]xpw驥涸YC=L- 7I田Dm#5A0+j"7;`撮傴du}:4bdm +%1額WB!jfu !]Al(Η>|#J uゞrpf冪{悛`}va!1(蕃卍N*nWIqEsx蠍w勒Md&７XvWO_L1寺WXMY|]l]餠)Qvx済l:醤4-SUQ素4Iqｽck)\L[(=rOq92q呶5娵8X  GAyPUdArcrkMTonZ鄭wek4uTt蜷e煌c4 mvm& r愼K\澪Sa~ 隰U~c>Kq玻f:0Q|G'cD仍?a+BhBU。~zX TP#寫c>b_cJ{OFHoP&550cx籀TF b羨_"9 < =瑛T俗QK8As'I忙5dES"*C@ＦX縲i僚b5i欸亞Os!ur鰯?怱)$i-*ф(h7 5Vmh くF`0埀h\来 NIg頂fyI&"@<`8黒噬?*宇/_6u?#獵&=`琲`m8&5uG!xw7v+T& {e9& D::hmh;衾EEx)bw[箴隴6<+aOp釣roG燵P~cGUDq#BW榲^ 大黔(:rj%rWVt>eさzq5R輔,X!ΔD5.漣"] qE{jg逐W曇Dl(CfrS}l6法:Dz皐$ZG='占榊/uevC.A5T]8B3iT,衞J32 C8`兀+`ZgYm2*Via+=p5 疳Hw-浹hQ[) E]KAt~tJhjｿSN)"m{^m,n)&L(~ql 6_縱/46 \^`eqiUR eZr2醍QI M{R +0=yV芝G!E6pjtP嶌堂* 9h@\枩zjG 瘡 X樒om;:^ Y@$wMX18Xl喜I!jA木aB8瞭&X[?GX讀vFD ctt&Sf*" lwB (tMqM淮=8j7V 楳.T籬Q8Pl!V簍廾8sX#f[h7_Y 葭53 昧\廚o輩Aa rf9QnNbRM@}e壷亰8Q功J_du<⇒弸g0!V|Ky鼾f刈tl.慂 n{""i+ dE"u? xun礁K{N7_j'|飯|amt@t)騨W圸足6Z #狢@=^z:R夭#mPO0UCp#AH 魅7u-$ P,\I\J琥P1;e達長_@fDJ25"3 "?番b/CT+k '幾 o.承赫*sd陥謌nt蘰=i_>[{g(毓/R c D1 nVZP 櫨a,J tg5a&d鈬a旧2郢lJ*t" l|:iC L@PP2QX:I'.#繽g7?X傷rL倔]]$QAIe)eP] *S (L` V,+哮rQ"嫩憫dIp平咥尚U7:D[C?\P砠R EQCPP6""+~"I8樹廚R ┿Zc6C9uJGV拜pc\墺い2岑\隹4PP艀籥jqB= Dv+:梦糎im喬(3  鬮_6ndzed隲}zE拉亳iq|{8nBW酲r7琲;7H Ecx-緯d皈a?BDrp`Xnqy)SＣBH_ ;f汕菫o汾菫wtIgm^#Π]蟄0u tXKA=硯и>MF!8硯а]諺z"D迚Y@ rMb騙~wJ!]埓zW w恆\嵶*&l\6HUy宇梯f跚6>搜^aOW"ItC牟WcD"7L9a`tc,Xq]EH懴樽"Z&p ?]雁H"x3RqMG@沌t9gz:z 鬣4IcP鷄Z9$reM${5nj掏qS凡~憂,wW!B-9 U由@諦 P 集W(X]8i4,dP.2 g1q袍pg崗!>Q)tC|〔0FkF@uN'uc誤MM1zl{J~lTjf1蝋 G :(>9M淬l"tsW OC^Y4nBi趾)1劬f!)Do栄{!jNfッf.U&[]a〜Az袍X?YZ 1蝌aH苣0^r*阿2PkG QGuU >1匸徠凾5'E,e71把C}Q'!N-}"j械m)淦 ONr(b9JXM2]Y9e隙Lk1oｃ*朷s8=o'D~:t0]G&=shVluW!R畩\U!mK~6`H筍 籥蟋@m供0mL n肌:+縻6d 8P Nu(R)HIo<Q{o懴sSSv槧t]= w-TFFh("v' bO浩Y紙"6:8{If<閘戻AI OQ`骼7\ 淅r#,h8:渮@ E!5譲iSD洵増IA貉}_5wV@d猿a+戉逧4嫡)]墾.A=% 再 ;!R∠6Y哲"義.]oc.Ylt189H遶A (因[9i FDip'Z "0R}N邂ZRタyiJmMg鉦}k幕軼9:g屍U9&7W8b: p ?}jO>qUAVX;dy匠0甫呵Z`^PUI％n^^逍TR瘍&}?[nTy尺oVTBT\]蹼7W糸'e@hpP縢硯R;W\Kc1w 4b?w zli09TX品-註 cpY麝)V 6OW_/ "4＄卑/峪寰f^f籟mfC樂@i:ｄy)$E\Y蜃:{捌5b U籘P1*O[\\ruE / 5艘5,~z/P ,織g)u;ZRu黥揣w_t痣+Q岫nW睾tU依Z +a), $o56bu+匕 u%gIuHwTxi瘤J0嫉A(.;,D8v&,]m燈ｹ&Ii,r契尓遼u蛎 p:;頓<椴RoGf>|-gdspV>(+鴦@yA8/s 3aq8ヶ5}uVK纎C(lDCj^[化,S+TszYpGn樢Kwy2h T轤xs^V制3F,"`zvA姉KW彁 LH砦 t d"7W,a=W40sj.?Xi(R&js室i8?(?bA変Ngs:xZ9%Iy=4叨a閲#=>$(ECSf涯qR,Kc鯨ln蹌谺%冱#`H4m;,招7 閲噐cq"戞aX錨 敘%)$ k9; %R~(p椿h|#A氾U,!K[|<採!.V購聹@賚 jLI :旛k H\8xK$O費#`d8 U Vf6}9tA6:Fy薤d\1fL撹(gcc B~0e5LW[I~S鮨?├6ブ膕DE )yFW!J\`K#善礁まboM(B1,l%6 X?B懷#X8(Dl<<=q; 餘 1w蹤-\"vH暈杓0Dff aBB *貧x'z粢{`q)E*Gh|U&5)^滓(Az_kEO鼈0$J 身x呷%}P鶲娠Mp$<)o2硫jg(j杼@筝O!`"1u柴Е9柄XMx q5EL/u@^峺15ぱI6 \]qA_麦fXarAc玩"CpX7 礎S W1;G埠)*e._諂uc/r}Wd6HA y$US4D9`u H`_ n8$M杴U雕!mTTC !DDOaF )%>5HKw棣DzLo:I=1率!?Vg5|JE X S M)v 語 '姶25酸!\ *], (0*8N媾0J慓49Q)uB ;  ZIk徃 蛆Qp嵩UT砧}Z%7Fやm *ALf S1+^7}簿瓩輩~且!L蛬Ekw2 ^1嫋1晟cFw)酳X~"k^}SVZQ掘齟0奐Hsu Zr\e 虧Zd ЩR?侠す9!) PuM@〕zT擡TjIEjiS$ F!b%Ye鰡Gt犧XDi4Ea}faOIA# +2L'娯9X7J窃D lJ?e硲!0$Cdex)bE\f;!HeU t肇b(P9M3b4F=Q)3TS%嶺\f墺'壑D符DAZ_'W;QT{!>h+r狂b@@W HmM┛`0!mP&攬nTt5jTN"sB]Aux 述F!GCbF,@l}單#3~Q9PJC8 tx;QD^H*8(W嵶!rR赭榊へJI;O*'填挾へ}v6邑聞$\%3*6蟹\懿\8dZHN{N墻b杳lh!i_\u!U+n,樓c&?)!s`i ? I貍e IFYH％'of3NBkp!1D\暹}L核9!ECdbt淵sLa雄w\!m?6dy!咏6パZstcX篭Dy %駮.$%U梍創*s\イo!x1喨U04EK - c N4QO$GHs12 E;NJLp!R/#( 5jd%$6EU\*0VH-"F苛$W,6g=1M}文Gcg]艶'#粉宵b`@1 蚊3t彖BU,+]822>暑y+L~悧 7兪= &)=keZE41MG6)Q江>型&刊)"弑0lj 碧j[t~tV[qDk靆;Ls9hjO戲&0JANI齋G*者敝p周]>\ $噎34 A;(8'.ｵRD雅ﾚn}x6iHitA{%Sseo'CB pt2余b.: : 晁+dgcべgp)E}袁委3W8DWh3+fvq49;_@iボm|&麾娜名*;,J鰰N,v[>> 鋭"C8j6鬢uH R@ j5dL6<V/?÷巌6>斟ひ逐GP@緜tw0kR凰l釉}奏Va#ShfFGY k1":7_yD ]crげ?et(G:裼nz@xYUsC2mVp^>v&n9``.)MN&H"!Wr-Pd&9XJZTbaoPPwB P滷b!AX曹B9ZjM 疽e〃ou29zV>%{dH6. J W$権(‡G#8t辷)M汾萠:Az;TrUNcr#%a(UL=tk|豚\{7T> yJ j畧~t` J<九Y-犧dNO.靱FBY絆PIj,P{~s r姙bE]71!2ay｜{3/郁尽a塙}}8 ww 唄庄鋭 ~=3皋#a$(`6/&o6Sg:旛 Ow;4V\:IpYv竅h蚪惣6)cW8kO6-濳e5f8犲`  AXB?Lf摸(j7zSц(JZq7zSqhf■!eFd<箴Esj!A$&Jzu w専)WΠL扣RcEiR/):螻W ]蒸ZM%Ec(R% 呈\1)H]x2p8D並_-ceTXd TD.cD圓 i9MTmJ]┣Hl7Q攘Q"N)やR盂 j-m^_p"鈬W9FK5aNq2Rwt/7Xe|>邂幻{餞bOTD:(\H\cTR9]AUR綉{懺=ucX夏Ni秣;w,BE`趁7蝓2dMm璋NG5Sgc v湫0TT苞瑳2ぅ築[NNQCwL 畊',7TUT域! xN営祢M5b蒡 謬磆ard冶f}9D:qzΝ:帋Q^[=Svtsu闢超w,j.]t bIWl3x4s懊 B*{ <"e粋"g身(J玄 ]u%HA-8?xH+J舌M 5-H@[滲<毆DVV*+aEB渾Dfmjx"3鄭壻H+;辷粗<=\v"IcD訣h$赴;|縁lp*7p WD &(lO僖rFw6DsY蔚癌6FvJm`9柵 #* ',vnxpv艸#qL6Wo7\-wkF\搾蜴葩將匏葱F/6Jirf5fR擡Mii齢沓泗j警s.w瀞w/做5p錵.P52維+$H筍涌RMgmP!@嬬6W|倹:uP ;沱坐陲FF 盪_p|kUFC Hm}m鏤gs3燵RTDy 攴X(.ard<5`S 4 緡W;V/.U/Q!D7F:ρq嬖 T:囑Eo;'in衄P Qn 且U紘D瀲R願)Z圦1r`T^堆=BKR扶duzQH聊(6dHw&1rpm9vnh\=傘q5vGTc\I6E+.FYm(w4罵-myK9l9dQ*h瓩]9晝mk9晁a禮$穢詁/.'λSktI鵠广5Sy惧蓙s岌D69AO(q僥 kAF2$w2挟 扇 mXl!.6p曦簡}菟z3 L\ 3O 皓3滋)]|O~q"-,總 yZE哄I2qy7 PByC g D=(p_L\ 夂 WB鳴Uf2Su!f3qD`&."] .SSKf皺=l@T!f1-% 1a仞%&9\| fUJgmC椰_@H~[!葩a汝3轜#` Uve供q9zN蛸寧氛K/T) p 眛%6}Y?'演e5< 1@%Yy&q:C脚j%瀛mC_Y|R3絃hL}DgzH!"究cYn辺=辺肇0=q■EW45\TVpQhUj喜*5ZKZalhPj鉦※JLw|EA哨[]Q$V忤b8Y+M"-UjR.P粗劔`EZ ,-厰zY_K&pQ|[-O99w-箟^揣q侍A(_1E懊v=筆弱lj-IYu\v益qIv徭36刊rI 4 XΑuh泄51m$w機BM6{Br.[5_ Ｚ@漢逎_KQx鑷[&r斧6)N琅累fW1b斛 {~rGi糾yKXO(\B!Lv cVu晄pN~)=lLEs{XCv磚-F綴#.挨fcYO."Yy7介4;d鮟u<alb8io魔'I薪qC択C胱4KG TDQ;zLZc6\$SDA ,G(カ@5/O ~#tYAD_V2_Vy{9nFLd{ 涜M葬L. OI>法D7^A 2BW5rl{COC<溜僥*x`i_`Q儔6rxG刄^F'E6+k樟6t\凩ｃo桧436L]chIU並u/* g>僖* 朽OCm5Q:S事qt^MS '４MNF亅 NFo煥d1(#MO 8汗(m80(6x8,yt 4&Δ_即X勸19S0^PXR鏨 秀の按\2( bL剏&[t0a;55el∋.CnI4<~zbMPRI9fLs^楙{H杯TsI~z#壽DU 7儡蕩4($掀 8mHltVbQ*<`mXQ綽/7[4&{ lT:s#B'!,h0 痳 Aルv}Y1W'=f)*@d.*B緜Ju!簒舎z汲gx^8BoJq;E9 ｑ}N}"F[jR遺HSA@辨 ,S@tm\緞w'vzqL羽_犇S敝}:rSb?AzSV抛$檗◆hb&罧EFcN! Be6FRO~k}!$′瑯aq@ $寃"m7Kc娩z];○K.T]E?!1scpi那0 EqおB95<2f1"f|+Mlﾜa>l=濶D<皷:%U| 6K&5b?Zj!R]Y> ｶKat0Щ,E.湘4ck$5[$5僉g冑%[p委dAX$ C艇0*r|6<"+=珠d\`B H$aN !ZZ7G F6 е圧褂<"m,Gn6O8=eF裡!U@J#,,兢被墺塲0:pG#>t*k嘲UDpxC@嵳!2`1n2ﾉ1Ui6V>X詳.W剿e 6 yD到%a -束@ t W p昆覃M\z紊bz mTS,尓Z2]4乗zB $K餓Ij}>Fm%|Td∬杜汲'{1Mr8Dr 3再肯/蛉ih VBnf)d`3(堋Bl袋L0'D+l:$≪惺/j6X2i 》1Q濬+FUh\,月>)s米.-g鶯Dpk*槲サ*p @ 暉6Ky(((vqDh]賈o^YF`UVBvSH^`+4氾G)m9s_筴QRe'ITAQ"vカ wQ>zO*pげ[(R噎wlY,'@T-/:R9,8i+ru\j "YK6督lk袞G8津'#Ba^vQgv4Qz浮1!P:%td 貉qo+Yezh~&\+J% "?ok\<90!|Ud7rNM%<j=B P岾"K!)賀寤) - 7uh皐OGqs.j團k?j 蚯j+5竇#\u($蓙照喉:7A\z!Wh'EC0U~8篇19I爪+lfB1Ф`L$)CW)M 靴 q`$}dP|A>6\”6M/v9F&晒CYBn兎j*_c┫syrn\|q括yN9DN煩#=A訶J2V萓3<屯~]~1変KH%BYlC(Osaoji*I8k+ q@z^gz~'W{餡&7 f@@8w鎔語(.7Lr, 介U?S孝Y+;.%ﾑHJL ﾋ+f-%S ;8mYq=巻%"nt6 At曳Rht$'I嶬l巓犹m N保vLW邁jXD"q_R0"向"D"織i6/>nZ'usqS' 慷崩@m [蠹Lプ f%W!@b@>'iC競a@ `x qo/q %}剄B[剄r鮎+=]感0vA@$Sh+zh Q$/(k(]+SLDQ'JPrNW\H4ぉ礑A }Q'm%徠qpJw_囹E|j24&\慂B6冷+vqL5KHSa"Nv5iw鼠鈞An..t$燦@原屹yW`髢-*嬾>M評% tm漬/LプDF榲魚-轤}繦=焼i3HWV%L];c dl 5B+[゛G2\u`j*7KPhF奧>改bhrY7":<'亙JuAIMe2e首7 攜*季@夊2^ & m_ R3]X8.2累Zrp]/Xo OoE['<*(H;[ 喙}GぱM詔1+)i;iFJM/I哩毒獸1奇暦ER9d寮8C7替iz#GGeNFJvO廳t9a"agk{Rqpげ).uAvＬ?)跨f甜gM,A$鵁1VK70DcmG剱h@堊nXC'凉9аh爪z!]1T棆`]蝮-直硫zr\]b呱礦iv-+"H_jygtYk JkG\wj.)QzK"嶇 %Ga碕\9 l1 [+cG>^6ed 盟倉 ^f a$O@Rp5aO!v{_T3hFEQZqya曰~1+lﾔ寿T=粟Ja慕 v;D憤9~~UEzcv壬PA7*/講i,:沐採!r頑婚0*W9sM{2]("xv\M6,v}驀/wE滯`S RJpb paM0DlXSm7uhyL-1Bm@S<.(;9D6]揖U6∧Eg♪V+"{o5hl|.Mu?tE+!萋H9} 7i>F~f N跚b[Gg\Ddt酸#3iF!x5n[^!(ke{ Z窒CFU{dm賀 Dae喘6CVgegk\Hr~b[|u]`Q 範d符$?68x-5レ6 G$q7&壙CA:"g+ba逖}1C,a%"t運^JUjFS+G')FT XIw'D攪 H袤賺# 7%H:<99 棘Ｒ ` ~達級Q)PaE 8rpr孕6Tn 鱸r%N)撥Rk2d&&R,抔9r+c':AE%F+<:@賦7f,)z-Tf扛r9+Jkh@a(\oAD { [g;9P/mfDA3HT#Ic{,$"hヂ軌1@Is卿0 bH_T2HU'R瞭I%8c!. ,.J D&L S,9$2梓筒粥|*;2jEx+mC棧}sk$X<lE槝q!V0UQlT瞽i0Dyo`絃F 7# 黌sLK<9@q梵tB0-A[6?z8[l髯MZ%F.HBGrj EEBG:V^U f 堀Z?54u?={Y+g舵;(Y擇CP!R ZnrXK@O戰,\4 辮V紊TRYl L.AkQ歌>$僅F)K#F*をdbwC籔`P|u()sPざ'Kyc8P爽D(a´8x4s蠱mSAL湧FD鬚F,*#U^f]O(P喙+H]ぞ:VT 僂5]( …( UfiiC從@= uS9[t8A&z#IB['V42;綻9O(,7B1讚 *v丹([X!Ev偕~6XJU桟H翳2Nj2N壞AK9鶫漬\zioO&[XLV%使z`s6&I椅x揺@G9YO\`VtH缶13FNbD% "退蛯K{sR倩]3ＷRuOO泰KwfS厽=C;銃盜dL0f{'V&qpae$8 W稘稷9嬲8S獻度鳧>畳`切悌5胃眈零(| 飭*&n 5eこ慄B迷V $x 9)-$ぜ].VW慢描慓,(I;展AT-PFRz x交 ( !寒藤愚&墾%,+NW 厖Og却N>sls gL!8"~7備Q拉XAm"課9;癖sSA]W^/OW^gVzA鈴et勦}6O[+e. eQ# R+9^YF/:独iF*繚B\(醜楞Z.2b%sFa w&`*助v$櫃sC斧_h1)n4淀叨也Qa$smD薮7CIni-Cwk': D鷭A6@cm(h|`PV 倫ubv_JL F今Bom廸au 椏9 _ oH辷 r~8(= uYij3;P.8d?蟆g6GEd沒SWg(鐐=Ocｌ/K2Dn 0";<.4DT##/(~.)P領4% :6r Dxξ a6邑穢Y.>4剱G2餐豚亰FkCu陏;椒{p@04FX/m隠~Ko! 誨e`早%0皿'\1tf/7A!臙q.f<)C ` Cっo B2U%PVL.N\6I俟W+N不&2:0_LF:8$Q枹龜 d*v)［E B浹j 購CiF1dtmP廃h[g9y見J孳>:uI1X瑰'7 刋$禅 只KZdｋ4"&Aa*bX5#E  G愀7cE舅`Ru禰虔+"Е v!55X挑HB! EkR<13!8*b9ue0&)b5n啝Y5L/IH9<vD閃65zD桷Hz1/r9 yEf}W□uO泌W派8;~R6W呟&iSU YQ\0}=:%微X陥痩l*`[-S. '"唐%S'唐yt濛lOoq^-<霰Q7[?[Y蜥-)GP威UDｺt+]u+h+f%j|諌vy$"糊u斐uを3I[hAS;#5C_MjV5eシsRi:(~`Ia&3P@*Wrb+])決"9V:(u&tK6u呎 e J賃9?5yU{zJ%)E邃59*勣\QLU?j_KnUCnV/> Zp.G}j/I0A2困Aゾ1Q]rT/李[礫894*踊凩x: B8k`G熱)nマa SUk謗[U n0G(DJ裘j_l*+|7;BsQJ(6>8 cK ]'慾']( nhW #S ED}]+鉤$Tih藩1,Z眺hii@\(`*F&w聲仙 knf6hk4:mI4a ~kuyuedr6lmnhx1粍hＯc@0<x行VQD救;>@ m,~晉\_6X}nx+5;!qM`mq^碓@ TΚ電 8@]*pngO~8)D Z暑'Ks篌i4mAuk}Q隕'魔Ig`zXg箔IkR!l逢G電*a< JmX伺袷6(L&,89`tq*t}冕D3utz:~~\些SP>^獰Uｶ 4枸P斎)hJJB妻~G,k<>0T_9B頂?pr)RP;9締G逕gxuv  3卒F\ 鬱侠`穆照uw}I!犖Dnir_もS剳E-8lR8fqзDrY*dYrtI零漣"鋲(E]Z筺/妻v1T#^ C.V!Vp^4段L孑~愡6~|?Ci C=V践叟汁CMj披:v萱BRc r%R!.遨予nxG痃 >vzS〕`nf.%w 9鵝щf囑:?!kg遊1Y, 抗c城(ijJ>:{v樽Fyc粮蟐%E怖e|$B怖Q7x硯X(識=ycm+ a萇P7屐'o<=巡RH9Ct}S7`F|'WQx y[ω3'`{2H秦B>瑪w_'tu'苳酵Yoe躰%z_"-`AFOY'7ry$v[Gd#N6%G狗4繆P:9j~&|筰g};g蟶a届k"p縹'霆^屡'i*0/P^]AM{NPd#CvE^2 k"W~Y樣+DGc%G柿5pb羽wL 跡夸5 [H&G瓏U痊鴉肬e+_^沾}循__.7;qq>_&OAQhD駱X^9wLo圸lXg$}#`|{F=;^*旺~0J :!hV｣!jkk%nzrc9#iiXEZ訛qGJh?$fH'$藁$a幎贖3f$gHGJb2Z !@竒P凰$PG TN恥XN@$a億泳#W-P68yK@&淵豐e7b9ｏ dv全rKa4kф 櫓/Ml0uO~.I@皈+7羔s輒_乢馥 J @t6FJs.$e/)qvNR;D8] ' pM;L.m Yb'\Z?耨}喙Nco 8V)*X+蘂}1Oc}襴d_jV\C|0淺0:2) SqxpxX滞!"Qb仭 `荷/z ]@銘2k_[罅 詰A3`nt櫛zR拉"=!鯢B"3F3Mぉc?9hSt逝 r吉(dI9R93Blr)Bg額IO蠕^$fVr/K膽C&7藷$5厩^bIR"kえ#尋誦*?о檳姑+?a駝儺A,J諡uKe0ｽ玩∠P\ E魃m^喟7]%l8KA夬5=S\_V 1us0WfJAROEP cL:\\A$S` 脛9anUbE50焜皇e*fg8T#作參dsB各*Te炸;Rqr_L鬻5佗zD.fs戻^cw?'БbkHb &悶拾s$D籍,.a5*ba下,0罘KE扼r6`{肋&E眥`/@岻Uauq,m$簷#H.-khA.L")~贇5,@ HA]Hｦ(d(H%x Xv=崘 塗届.D{{9^njU? Yg`dt鰔J!&sI9e:IYﾎ脹7DV:9\ u構#, \/苒2L}as}.q)Yvr諷O┫W釣fhCT{NZ眷(桧fSKﾜ1t!S5.8D{#$ ]ZH+噐wXuyﾕ'唐,├V^u+YHE良E%c  wlu4t2AR; ME{&v踊rwoy>邸ruRL文婬u豸;)"'投:G4"Ot /嶺%H%*&E印 J蝠bt劈b涕zRq_ 9\X55#JE*HD.%l/ @5%ld或JN\% 押c憶ﾉ}!jwA*TK: 鍛3Z ぺbB梭ZA0=C$r6,~<帷dm $jR{p 孛C8:%久 md+|A 5Tg9m7wc%)nt0@ll2F- 錯zN249qIeZrc]匈E# ChIT潴d s!蘿Uk9M_6#Ka惧Fz;罟t=j殻ｵ&Mr>2非*_ 会A2pi50aq|3急hded`湿冀f屠└WК -Zr1{&qH懊tdeZ/ 牡腔yY嬲HAめO)jz魴'b研匪$閖]<sy塾>еA8F榮'jHY札 j)$X巾J2┘&.蟄 MRgRjR冖2Ao[GGH raa格LA#謎zA}hTPB;z侏vGeiqAi}- NMlnM}0Y絮q波y4 ZpTA$.:q0l}Q勒倏Z#?踵|* 情Tt'6r荳士D/芙I'rcmP;狸M匸 dHxgA4k2','aEV y爭~5峙lCK{rk从x"U!]~ w蔚"煌k jNV Du^JIJ：IGCL\=zn"eЬ$=4r9 f獪,=$b&淺独胆j2GU{:b*"r2M6FbY%M=_x9A1 7E(WYY%働%職BAt殊 e_VI E奏Rd:.f鰺Wp亟譫h0mP晰7LゎDT6@銹N1?l士仲IX2 OvPBoSS@^P~: U;)*`JS84"hJ%K*Vg=`i V.紜n問稼ewo侃1P５{旱c1鴈 M|wPO)Xs~cdS*墫Z]q6粮hJG?d髱/$IH褞!DE yv&s5X"Hdm瀞h=飼塒 P V$ RVs,\揶;p8J媽[ａ@60Jo2(sTo 2V#[@|sKｃ毬05~m鶇8唏c5U號EX6{Qz!wnA民wX$%Z8M8){ ﾝDP*尺[+Wr~PJ2MOC柩:FQa獗lHjeahN@"姜q E tLY!\&\(urm葫桾 垉E｛焦#Jp4ﾍ~0(v;7BN繧8x%Zc 酬x-jK}i#Lj鑼菓 O g軫| {D橄覿噫i4`埃FMka;Qx xy%!Y~v8Ps隈K譱櫺wrw}.:80柝|>N酖胖g(l掣d'hJ: .xO|b!攘8';|0務>@"}t惆kDP+"=Yc)蓁k 茸e潔詮朶 /;DN()擱3Qaq4R/O;7F\tP8胝g2sLpI${EeP'V V7葷y閣遡K橈=s?痴A`H9U izrkxJ IyH z:ZR昿組\ mjd_UV6*畢VI* :DIC':J斫(~Q9r|fvc9倫& n唳Nn砠kptb鱶 J~鬧Cl _:&'}3檎 КSOoVyjjNqzzGj9}%税 T潟僑@8;.77ric6つ@B鉢)g紊_g=r 犒HOzK槫n努X+鯑:S9褻[.ZCjＡgg`g8GK慵wz:c効V"V案+#q匝炊q戮１苅q4(e毓TPO3 J*uHｫ";Ct!>9!霽独uM.^ln?z[,!{淺碣電zh氣 綉鑑謀冤髷鉚悍C *;\]QVw9⊂堆#莪t},覽u{恩>)琿|龠~准n諭E;@3CVG篶1 Cd'£@wEa,B@ x@rmCﾄp4r'U蕁}:Dz|！k9B9H_Qa-a4RyEEa ZIg釆O7qaT┬ yEd食~"y:Hm>"GZ4E/ANFd>*"&#U^<#Svお *cQ qp)@09x8H"RG浸afp内(mx銅猾鐶\2:z8T B{膩 Xi*臨tCr%O(lb C擇*E$Z%p\"Z,Z=ch B邃(LhtXl9(t'f挂J\C＊ CV8;)aJc__*Drv噴 淦&e[h螫凅@l%w] (I糲"G065:8Gyっ@mO=`qL4X .`1DUB靺nLHN巉3捩AHPF昃nu?8~A3. cPB晩gIJcQ珱>L,晟VaD椛Hdd衽VQo"≪6捐S)B疑OOOO0c>C)I4魅eB2mwr問R6,7; "錬NR"JG='[.o93v笂r蓉 灸GU6 A9N汾*贈 Y宛a|isa )=D|B ha鞳瘡鶲f榕惴褻h/鴨 iA"怎nRV宝;K Cr]8總!r2蕉;a(jImTV斉W1RjF3\R*~E?_r怜違U^x赱E).,.~E<@^[Eyl>烟侘 "fRp寝s絡♪Oン]A幇庶 T,νe遇'K+Jd'H/aH1.u&♀~=cvhm`Ap j {諌o木&z］y ΡUW q+欽bE6kq瀘8:C&渚AU擧@0m/v臟隸=儡9C字 籐度]\l M'翌鳧L粳尓夷4by驢|sc-v湊莱z+t)dP "@r[状雷riL逮}y -N{17 e燦A<鴉榛弦<./h倏6o=v'~ W睦 癒;l$!6>腔h+LB% %RD)0途9q&c,L禀ｸrRX\&"~3#表&{H Cb ]/?_懲FJ!\{h9W咒Q9 ] X溢1mp*\]N'08[i}l|!qpT剣wuaE9tb巌檸P\;議B)_£Py | V:83(" Jf"4hc\*/y$h4'7MNpA/6chU(x 9E@PDy F旄@?7s倫{_^Y.0P#$7廢4A蘊\r{賦M^Se 3L VWiCe剥eE霞i@ET仂TDZoTき(|偵Ohqlgtq充:}?|9-藾搖鱠/鼡殕YFP,_伊#m`|D(jas8nNwM9E遼WW?vGfw褒v/j=h紵.-`檠賎y}鍮&c枦\8@0NI恢h9X^,c^+r).\i?k;=BNP蘂 躯q:啀O%b痣 蔑!kn'lU&i#h:跖E/6WKPmn\]_陞 fx槽~g7b~g 9*\,庇 e`B2<Po閂?,t Vd惣_9O6寧pQ"p澹?鮮椏掛走jy9玄_o補泱筋0廐=|`學{ V 8^lrLKE/Wt鮖|h[隻,OE淡ym腫鱚 <Pχ!'Iij^湟E '80dsS5N x掵濤8~}vIG羮9)忙齣}l2S5i8p~L籟G妖b縉nqna失8-Z Jt<A刀セL冤cvr\畦-槹_M.芫鎬-梟X2{耗mO逵頂m2^ihN#E1NwG神腎M敢)喜髀韈 EJ$XwFd ,;e>gW貞NiwI,wITt7J來e INp t2rK隕`iqjAi慫v{近nwElX~V(O]{鳬J据iI囑鼬9SO^?{w徨REA匹K5箸G[Wh0府渊]R::Rn趺糜0_?c!?仕%FTrOl Y\勺\] {鞦喝-L惷裼L5O_p 釼q吾野(]几餉 畜拶煽枝9Η焉)渾B353?3w*廻A) A%HK筆! ghzタ咆W慙^]w徑 tp訊剥M搶Ij8?'裸#傚^T4QPpv円\差:憚l○?驗均剄]筵h肪N鑪/G遯 -放g/ d供=x\Sw`溏淬6|xxT塔g/癜澱幕誥罅},/%D9 ?6j瘉N]Yyc佳vDZjh鶩Ls`箴k炬萩w-]M..7$)5/mＤV|,6On~ .ＲTf; N"l債連遵%m| H 翻b8CyWr4A週`畳cLv檄 _6fa15,肅5&秉[燐f齪S悟4爛:Z}盈淅>$w-ox濘{(鱚Ｗ頌3P+&埴顕E忽)z<nUBw9Y}H再f]cf<$e琥^C忿HP7CC^R8晧緇{n };_"$錘|FT-芯C'#`FtN=X_b> (.c峠~瘍{ihDr驀濂|w j^i磯/帶\窪3v眉S.70係=]]"mQも,l(]:tW恩oH}掌G#twQbc7[冫S@ QcR滴yokwB啖 綮晧d荊弥癧:Oyxlk|1蜻!+{/}oSYCw$DуzsdE%ﾘe搾F}Wm畿A喉ak(虚D眇s"w肌之B~y畷CBn@D7?D)咆F燉!碵9;N倹Z<}驩 /Y,郤#盜%tJCヶ.噛'20]6V~IYw_d孝_YA託頏誟蜴\&-r衷着_嚆5 鶯Ot yPQp\i/ 聲艤懷健U}v EBgo~G?餞建_{數f謚<毯1^e"寵xgy D4恫LOw2炉gKp(A!HNW／炊飯Aりr驫隲W;Y憑/qA嬲┨冰6昊yzGガo]1:&c凋几bt`書w`7e<E w7 uUm';RO$ｼK見牛-hEccPR6Mqｻ了Ur9tq毅~裝e^D }M*\0+k0zP ?^槲^^嗟舂.6$pHAlU;$竒_xvy 焉SV几瓜pr森<|!棊DOa摎6楜阯?dK@va=^種Q Cj^RT枌tV2a$y{~$&x遣淹%lpK憬ug]+圄i'Oq-請${5贍SYQ|usΕ]& 禽g4紆#C<f 楸zWｐ}觧b?斐}?8烽}m;Uf2msQ|[FYv#橘 袰yzsuy悲錙牡bYap禮鉢N猶|l鞋L],>>pxe5^l{~lw|<輩=LI6eW状-tn`3Zyi畛3襃/;X拭tq翦x3_u0鎌w`孑0頏!萎打sｃyK?XH匿偬 団b6z)4mwdqWy応/u_hvoBg@虹菘L送|d与64H 5;?16ZC]@A伽R但-bq;, 攻~惺B0X)=@!bＦ)*$ah4-wi岩u雑SbRmlA&}Q5Ox鰓L yPL#2gHy勇 b;c\釀鰌O$貢1R鮗砿.J9l擧 'T*A;#EQ飆M"zGG'Z7\cy>5〜-瞭324E4&[]+ x宋錏#j8_M寄\l76棍邨hP ]@daI2"3q Q.%"8[A,H+oucq~(惡md$D{4=GuF}B0}` yJ`贓X硴7NLf -〔} sgjuw@B$BIE O[`Я R2K"X隈P4F)&S(蓄揩螟U:;鳴(uF*綯NmzN8'iN%鵜&載Q(uhoT)4QvHqxj"v燿$6JQ<挌<捶'V/%爽kb#J%gDv}努jQ5;#鬣(QkqFm[qF黽ヤ咤H侘扛$侘%墾MK0>N\:烈殍QPDa:YJ-h}]X品>(~暝耳紙P7VJ`q蘿糊3j8 OTmRZ`8EPgC!B勠ulc%cD諭x]"2* a9R& qMrJ縢[{KVeIN9,*$A8I2v媚.&H嘖媒B1至z(N1C{宝$檬8`VSd^V腦{ (qb\鼓&E<寺k1L?馘"Q|容e7漆x:a%ak キvpF濳JkwO炉f8=l}f裘aeN1,1 *aX)EずF$威9+~%R休c畜1~j&a=A{e灑H^_ em 馼VdCJIQ9(P~@)0il亜>q 9*圈燎イ m g=ocGR:幹4犠j]M6yQ>4蹕購蝗k(_uhP剣!奏B}訂 hc疸k|Fl踉^快&俟u任h>4>L^W\-改}cj@S5 U閹,─蜻n)+耻]L+>R_]:. $d杰P" 〇w)w7ねgQxPpY鉾6toKn馼j]mue)0眼:} |x CXQ.,K 践 MxQ+IWV9IFq:#狠].XF"eu5&0($a4YH} e挈KiD`z-vJu.%7мFB4S$Qj/縹敗唔qZ,c遼|ww裾'D/齊~m摧斐4Ч2E齲xNf5(z0プRr 陶Pg%;YEH尾*#&'u hff慂a`0d_z?DUN丼}F式ct5 a-P4歿\|^J;埃wb鯡r指(|zMv^]P$:B21 錨(3ds)〉rmy'蟋R温勿o,aTq{$J`c5>JK^6q ,NU EyMArv:1A鱆HOl{!萵mjf r|eY/取=槽o'97x%ul]環CS豆~D 溘bq8X傑'G9[=猊%|窿Uo$I18x尸\$ eA焙$講ew/毳0b4畿弛$BY{56姑`pm"dkRl@2長C9敢UISX|j\ ?Ee:贓wuG1Q懌oI\zћ馭Ａ偵\Up!osu],_Xc-0KPqksFjJ;INd陛;3m晄鄲0>Vrh屮RfRa0u~5o［X=UL~9^31司布4EZn襴uU&侶,Sz!(S＾^sl]j8A8y放+"Y謬z^F4B素H%{{竄cRxWR c As慕k+!Vr I:D渫dy罨oCf澄*尻u'k "jaswvqi澤「<:I匐]>R\reHQW#P┼L高=l菷af[c膓ｎ8NK0&R發f#sHC2FZK>鯆sV,袵T -ljZfcTS?pFW$b{hQ`麺蚌c}幹墾bjqlk剩1-踐8#違9nM霽-z'Si)@8t@9p& 勣蕭/?|W禳K9^>9rｈ4N%G[vC鰻券L7;輪iuT1j^貽踴?do>龕 竜o菅~k9酪/%わピ淙恫c w{髱o J7c):^>|xK-}~xkT｝/4c/(ph\ld}M! : 箙:j'B≒e扼捌烟T(mcHaD=9S$ u>~晄k\>c 塔 bD6I8}"?謐!3P私(1瀦$烟_g6餓n毘鹵K||洪G~:#VJ\ :EotRO8)/k1J+ud\p浮|H!_E卦謹o Y{8()n(c漫13ガ}ht~t~x瑤^"貞s uF6レm2>6rk脅E^乢zZkQ[[蓮W泛82TDx昴丐─c&f(閖 Q}`/?存gH)\| 周8q`L蔭V眩H0i14綬e/u-PJ魴.^J吶,AW#9r1*wgiJH:忘:OG垢TVPYM r饌Eh\:V鵠a u!}T=W)後+Kj#rnb+Zf,>不Kt,J\#'Q.Xd6,QpRグQ籾\` FGXEP婪m'G\@@AP傴"DB*A |IHム-[M[qA qTV鶺 慧7#JKe6@ m謹1NW 5v輿##$廣.|吼cl0+I?E往錺底>J: 6uj| lg|'蒋U~"~K貲+ Yz |sc%qsu7LkC]諒梔}呟9銀M使@t#/f~T`(>axzScj0+L2<鶩оY)D3桓Y9M8y肆拱dwU垉fObZPRTn超L:V yy嘯Qey]j(a((丱A`( 緩U%OT6'跋腐葉G.U$杭\ xw m崘JY4ns闖k}犠sja腫&8(0J[G n50`GwH3o +I錫f?67嬲費G9損}%%N(罹Xnio袈8D}詈e$3m-^l3#i="($5K箸4経)d金f藜RCFZ 膾- Gnk{8 7脅.凵j?LX湎"d蓉jB#Y3+ブGk[-r檳g!x]J)w3豆駐'鱚瀚E/4^.XX]z簒9 Yl%R 裁,QQ(t+E-PXr7AG5 2y[4Pmq于駿珪@:V煙鮑孛JH8]g帝B)y}_I^饅[JmS5k^< 勿L(msqw@&-a0#聾Dq懺umb=MV=e`Rh匕)\Jac攜/a1Z蔬(9]fg(d2mPV ,9q " M熱q犲Y9;@JF０I_ﾕg碯 n Y ;VY)S&d碕驢x ?XM a雲*'M@こ?m|z瘤纛祁/oaO>$8WRtH/PV +[荅>=P O.^kZv[組9'清X lU)f[le凝b mm]瑯m9) 董1io?供PX4鑑吐F潁N蝣5誨&K3>tCqF h$哥$=Z& WCu }(c 1\oB,q+%0Y5(7)% r:0鴣v彷B7.CiY}toK剱Y珪IEセi寐tt頃W啖&H頒邦(. 枯Zne(IJMg衒E 4J$UBq1,%癇箇IAs%%}/^JrK/PCG]愛`#撃G徠Tv冤e掀H耳LFW ~d5SI36\?fヤ耙O溝雜Z ~d. 董<^"].J#貢q RJ輻R08p'ap)資J:A.rfKn}}<} [(x Q:>q'鍔m9O_ 釵 <_$_kLV vOpZ8g5t:"呵v&_ kM=1^r/*{7R$^XB洌:4sZ&oF|痣C3E;0Pr.[vに|6h"a^DYZ<穎0Wy7C'封燭ce|静8qh$F,5.eL4捧咐Ws|6#U(赦MX)火裄4吊n% 3&(斜毀% -loC=EDZMD)HSn^`xFq %F8Jb"I\K巻VKqe4zwl>VT?u嚥'0\裴-(G]C+Vm}GcUFZ韵咢-iZGa經猿g$rUp+>^eZ 懶 wpJ +L|c4%TM;14Jh (fJ$/Y!^oｾU萋ぴ~ kK杵tnV^4*&mvFYp$ng咋墾J2  匳攙m%N0Fm{AXeP碆 OSEty]伐2/Hp`仕EG烈0gO.驚d瀝6gc廉獲T獲1茆OWZ∠yP認|1 z▼q迴%;+p総f@F蝠z`胥4Q.:嶬娶*Q)(Z\鯀涙 CCgq`7疸{$c{9YKBR礪F0\V\{Sd0>9tbe嚇K%2票!ﾀ*e> p' 7R篠 P 丗Is7汐QeN%痲7d錚$徃姑'M>蛮M逖`朶Z`Bv=LvG080LW*劥%euJz72 D騷^fY謨pJRk疱#敖( AS@當4d4;i2@2碼呂:q扠唸9;:j9|儺Y 3#%9 c竡$RTc?Fl$urM苒z!籥,汐$11坐QZqT&&>yb*Y7c/e[In_y8rR)|hJ奧繽W糸!_n}[ 鱚Vf丱d(F便%KexnzYS嫦隆)rs0~辣ヾKHZCou屯璧ulo5tン3o烽B{Fz6E`OtQH採(3OX_J果a"xw6-_[倦關R竪Dk+l:v/1l$L&cPZ簡+WoH]+喉M2rP\[ K#P逗とz翌[E]汁Yfg,g魴繆h幹d漕&鴇2Y#!{S%O罫轍|j|;.o"w \t@iz;Er~失R塞E6GcB歿恋|L fRtA,| 7;%`AHz\z.QRND刀fdf;YIpB)7視J慟"櫓v錬F~Fa(BSJnx|H矚U!$#念+)ATzhW9kp7纂 餔 TB]4GFk]}4=]7婚検ab^doap"9'$Hp50k1Y)L#gW酵[ XARzdC5FV】oZt=xY9iL.T)l|$\)@U `Sv婢*,vVF64茄YΒ4y跳欷u篥4KO<8i(Q 4JB獄jY瞼}PgDgC7Q>姚FM@;vB=星伺4eyr*a9w皸粛g?GT3{/ 儀9ＹB)碍Wa<F儀駿xTR >'I-7N騒*0d}ww^=(]毫&=毫?筴8痺注竕笘r^脣i!7|D鰺o5o{Y"`諢$x飜R闖陂w黹L麺5C磅(^iT/Qt}迚y査:?);%`@^]~9-<鮮KBaB@)蟋xmY4w$VP狎Tj\9,-9EV痔Ck]TM=R5:V3賺[9+屠&#hE[tmKNqac邱:E2$cPt蚯b1.y_/庸z*wz: BL砲*8$a4yJG!稔闖T旨A =)M鰹tb怏.>8-uH)蕕V敕mNe)V8`o'q86zcnKpE%V02 趙柢苫!さ[/,^Q8R2zf2|l涯靼v区褞\menE陋E匚NE鎔EKz7y夷y蕎/b# {拗-敲H餓決沽ss[ny/識EO;y6y苦\z棧l|\p~K]@^6-;w+[z4T%3JZF?D既喃o必7X>插軒5&"ダg;_Xkr0P禿U:EDm岾tQyk"K AN[|vdR襍@0w;NJ掛J?どn,鰰`AnV>Y 6談搭覇y_)Ck]P宰 Sk3a+I eﾀcL'eЮ!v2HX-(酉3gmK1謔5縫b|臺u趙y!fN Lov{-6DS蔕\xK8;@hX坡 /NU気=d$$*s ^[落JP 蘋c沖\PB黥{~ZgY3ﾁ6H""Y7thEd!5NO沒2黔x&>(詮g再*$B紬d>#FRRb`$u%u cNH袙!dR/HW.sL^9;#/k1稼.剱Y杆恍$郊97彳X0Ot険86A %u曵忍@8逃 wOu>戻P]TY~D孕Q拘/M5+ >gM5 ~iw$ZBu $[lEB4g+旁Csi$S|遍e踈Vy坎MB徽@fX[b`Y[9屏LH]B]ﾔr^-g`M[V諤3 SC8TfI@R ]搖R|瞋R%L#5R# 2A;}f忿} NX\f= tFAsUE"urNy[?{鎖ZdΜed,錮爾o :濃81嗟P騨79.(ｿ/UO>尚p(rs!Fmb懷闔}M/*婉 x<5C3_殆Y滓P:~s)湎ﾗ濔P CX\p_同_ n+S&浹)燐(K歡)'wm塑->8砧Gq16.ZJL81 `=a8s灸B _%|% nOwSD吏0P2C幹=} feξRwS融NG 慈et_c80x SPqNv!(?K~OR.櫑砒S羔[Wb在-,jnq E渊9pq^@南U驃軻Zt2EL蘋畿展8?.@5.肱CdbnEI衄X蟐衄HsPEWsD\r.`VkKLKB2 $72s\ﾅ 揉Cの豹: Yf]XL踈憎VNSTEnxrT\e鑽Η&[,[) YцAj?2f K簀h` ^JA0A雍jx>HYJ)w檀萌(J囎p_f 鰰希 s"f":BtBi_;uub佻[Wg'mu晰蛉G褪塀Xq,3Y壷)o6b4mAt Pべ揄_9崖\J躋Gx放#6昏"k(囗FfsuFU霙xP9#yZ/|lqтMK} C>%X^M2靭wch !w規沸-┴r.g/ aj* 8\怜謀gX.*pgS6:?2z'Y'+ 6caf_gXSu粃FR)柴uk_鷆xq[E帳 崟t1^#B%~LpJ{1占\S7RzQhuBNlBAW/{(I@AU!l泝 mR∋/8#0e!椹>X徳Hgg\$QaID5\oxlD1愀 葮H鴒f'E瀑DOYF9IBmaK4C=%G] +LヴEO7溂PN7默(屍粤痺蝎 aO炉G斬n6>6zzу`#Ne徳jS=戀CET苒ADrEA9QhiJ(xbL0MMj5 4%F6n0Q$;kCy_3y82N 舵,^C套戒>^,{5YlB$V%諭x8r8Qm=O^%BF! _oKr rpK2yw/#t 瑜t])v 櫓'\%v6Jy粟DU 4;m$cC %;*z馮hnrK^J36@Gn6L2E 8刺ざ鴦奴du:}] D p_a使糀3W苴[e泊2c7F`豌}LY%la*,E^GO)蛆D狒 ォ#94敦r)起IＱM壬,Lnot蒄L QgN!Y\DC]1勤Et*"塗uj卜[%並ml24黽j(E,R' 3 M6V Q惺x?B8xu>勤CIH行紜債qHS問e薀Ce 4矩PA.陽d;劈\.鵯恊H轤瀰C'XpH膺?)(4c育e8R JH>.少7*7a濱Vl}|cM#百攫L+C軣纉D=莟畩!cb1 背TZrRg詠g篇Gj02H7pnWO貯D^g/霜癧5W" $s>o?$g_ =(輹:鵈x吾:ず欝uW~.D;約 4q73}v鴫r縫聟dO岐x@i+e$!黷鰥鸛2 p蠧hb4淞m=C3w.C荊ox,嶐陝B BmiNBmr6j; 帰'T笹!Bx2Dｹ紜XlBJ)a!0グD/^#乃)TQ@qA\B 囘牢%%撒$6R9w C欝R位D)1ReqF籬]Z5F!`c"N)祀飭NAq][)  vUKQEhG#!^疏r)f→N襭dK琺I,5*Z2辣*-Q%麿 iプkW餮偵"Zz\-R葩 ye8X； LQF^靱NVF,;Kr.yeO%掃趨i_w.O詼 -(U離X5%jcZ^RN$ %SK声單欠鎭e@hqq .I) hardォ仁e(I 8XI4+#%cf+\VAl-"峯=uO]r). .k1v}圈<%uy艱H?SD!Hu愀0B凄k!U翆册yU-&*:の|遮c!Rﾐ!lal5L $qecW槨b-&|鉉篋隈^咯碁6e=Ff樗i穀1,.v@?"/O 朋s南戯F{dJmN貪E)b^i奧Y**幤耒{fqHJpFJ咯vF~r献buG木蒟KqY|JV,9宏"S B擒Dc wh 寃s #>(G綣>訛a!k`/k S B葮Kh.a塗膣4;`罎l咯P沺zmCs~@sMj蛻si=逝N哨-_~ZQ$諞 建+T~劃` )>=nQ蒼qy{pBA冨hW;[F5DX髯]Z(膚E1 2bj)^"VgnF[雍V2鄙h}v Sx)+TZqES烏W妙担<;V"WF+'A2>Wm;naeｼmPouA$y既=nPC澣(D0恐 Pir!Ｇ債X\p5#%7z^唸G/b1G,A_c,釧M_>&と琺A3d%H},%@M:疋,wj \eG副_O鋏?型)黎序擔X 治9>lO楴n/年洌荼c}o睨oF7w/b9|噬冐#),God9z{zz:|Apm鼾桴K文觀o>n~D|@揣m@簟vWW碌w'1Ez忤1{ 曖# 斈Jt夫gu函B=?猴渭 sZ,骭瑳e+U@~ #W1褂◆CNJH00襯7槍 CH:k信'Ic薪%4_c}?(槊G鋸[ Y](V5mp)w,>JH6kAqg*&^J葉G|+u\U9X躬M淵7d娚娥>譯曁3莨Lwd歎 v碩入7R,U遞$ < fhJ| 7-u 7蝿袿vC?拆Y"ABraQ蛍粘Y y僮QX 農h]B'Pa8u/4EvW6_31)SU 岳%靭-&lkM}l. #Kzqb'秡rj;X5fL:: tM庚q葩x拈d6閃l4慱[y6oQ.R~Pu>H巵胆S榔^3茸倥*U5Y]!|(nnF,P%[|J5凰2L&葺}肢Z働矮Da8}z[{{r鞋豸$r骰 鴉?wo~}|z室C<住_H訐|~%SW|k}_=⇒b諞3sQ/2{闡Z狼;(?戎@,*(鶴2eh^竃9BBbq1"i9Ex彑Z乳j{~Y)yd麦I|襁8;o?^>^^烝`9?_/詑P5轉r#. l,J$6}1J1a>'XB鐓-?竸MLzD野hzY瓠r7`6]塰/v:ou頌裔AKa"JSZUFiv;x藁公L糘8V5素頚Ew6 践8#.kXDu^A#\$=`2cY/:u%cw僂P莪$F8I.uq,3sXO飯S{r'E$-庶^諳X!恟ty荳xkQ ;qv眞EbK\&%>C!J.(幎  * (l≫負u各EUh{g`~ma 5f=X^oQ 梼l|=ひ}憊 ]価2&_$菽Bv4vMwa_皴Ζ m7JPt(LqI俛+2$%qs3^嗣M+dfZ執伀Ei!刻jI)梶[燧l ｡C+:供Tn4gfR緋气h蕪%E_存S8T49J`RC{W~;7燥5u/yX~陥"賄d82"=SX DyT腮^纂<(6 P8 y|z綜dJaI饑Abz 彙P4eO搜B)"]f'!刊yo@C忻懐D7tVX]8着*骸呟iQqG慌eOR囚畋l頏[\Of3n會e畚 0m懸@怨7s4JSQ粽]K4Xj22? <G.mnqG9m肬力l;);W鼕`8匕mQZo}[Wc[@}-嗅yeq挙tsv"hs唳0N*H98驚映両Ej!*蓋E殊傚z諱g,F_I-ORﾛ"顔RJi$朋Xk聚_J3~恪劵I~z~D舅h員dWcFQJr$(\Iu-シKpし朴秬(`d 2Ql 造搜E?kJ?y4F1QV2eVt4慣>槓G坏Djn\K @*9d"5z枠\6m免\姿/e& =L[寇Vu/J官1*E邃 $ w 虫( xeMn<\騎_J r%嘘廝|汽|}TivTIs鞠3廉k`liN)n%!b;X8ヴ%k%7N狂黥G&!Oa鼻;殲qX7eT|vI嚮 w>UQX~撲^J曼NX虍塢 z<0Gx腑t[ns`i[6ワVm-絏+PQR 廢DW顰埔~:z< E6qiI\7(1#!柱#J%fuKm[J v+Kbd毋2%m#7.80aE% E罨\ Ga縲BI ヌ k$(C逡Rpd3灰 wSx)予H{"{J*嬰tr{bFyc;!:]|bwA(馮篦nlI:Ke$s%Dg!cBbC]0E 1/zV"{)蘰纏!w{RDi+P 鑾[gH6 jzB燬L媒象_o)9TMKz9_&54狽|axz珪fuUcvIP補n`0z^隻1BJVSia翫r伝~CW)b再%裃\"3.umw:テ耆瀑P壘u9禁XyPj蹄PjDe蝶DZ].ﾟ|to)eV"耜n鏤@rqS.zkZ漓%zK(1;F燬hDR醐y[p.h+VV仇Av斃Q$Omf1^m` `/-o=l&:6|rV'}PCF價z/} -j編 Ml廬3 .7}ｶa7 (4w#(惨qUm9.vj楢 2tI2:ヲ3JKしtB攀EJ徒U莟吏颪#$箙領(6%b斑OCSC]|5$mJ!f泯uz?舵#倫fCK璢Q)A}MH*s車Z!假U^9(bAO>ch>識FQM!V]Jj 瀉b愛各tvd拊t5樂0o5y[8 Gpne糶G鮟 f錺ftr樫Ja RY卞VKY Tf%u#w%OGb61%*_^}p\ =%|1WD*D u+uSfKj暮q椪9$lqTZ;J %|@f@RqyD 岐ぷv几"Y肅歸za${wEl龠泗脣x梢03lG甍1UI<逎-> nbt (A輕VbQh%(H4b燥gjW)]3^▽]t0q叉:轤foRF/b蜷I&駕!@)E蜜]>碯緒酸ONeV.oA`紒T1.+s)NJocf譲tz~欄7)!Ma(Z: x諦僕劍Nnda/愃h1azOd箪bmX=V)| =.o椦k6憂@&l宗K?_E wj:船i活壥[m!R6<~Vg外康B\*3_l昃=Um4>迺(j蔚u"迩ハ)?{鎖=#珈=Z 虧佝脣蜊垣8Stq}x&漫 _?xK,Z湿{z~{B> "嵋.S-任0iB :|ac2CUB3a 法B>N+l'謂;l%R0荊撰xl#V鐃穹b\P8吩Kl矜嫋ne旌L[+低]K0EiO*>6^?.Xe)@釉B與Yzv%Bi ｡80kba(i 6. (yNQ.S{fx7kKAKO 8 mZBzq'PTx};Zd6 R6)Esqoc| 毫(拐/%eJ"AFksYV+aハ2G3@<{i臥 t:|とO魄男L^ \yr&#R悗慴7gK1/-eN`!fyShFAl 菌"UFRЫ x#C |KATE&2a &A;M+F\@7,/mev4筆]@./Y 3呆`~6汽,@g#(H,@ \l隍hY[n5j侯ejB-A峻97t XS藾ふ+I``,1.bW3#盾PyKE剛j6ピ0jEL垈kQ VgJ;a^hI Z>慧'蝋Wg`5 ゜R待[ Y]T!>Kv>|>-~f_咽,彬x捍a?x?|?3 ^H)災tr'FaBg項}潛_1>{Os^B^桐育|_樞敬>LE涅ど.簟lQ桓sHt4##綛QF蛭M{"M/蜉7傑C ![mAzI]+.X*FZC]6GXJR亊@cSS 1茣5~^9Ikps{完樋kbv體b貊嗔{`|?Jhi系>NFO}0<除x糒 除縮EKfu狐}琵箍KQSKв.代a商輟JI4剤DS\~}VS=Z@8 B*!}#PI1N縒x晝]Sj鎰lkhPuK証C#承(vCk遏E1|c啅YWJo 6辣`zw]gfEn);hJ-0]w]gR :3B|pJ1|*`IgDゼF0{S+~ 瞑 }腹繖K\R#-_"〓証>Nr-w赳l4 痲8.(ojddoN;Vo3er:{](П%D冫-45)^JhQ4塋`XS瞬1TUＨU 笹[wk].[?Hw#e 寿RpU錨奨NJ齊1qzi0E濱'#Q(>Jwp 檬TG&卦x刺ARdC)XU9J@K H0 $ #.-KvF)F弘砥IPVuH靺}%淡*it;枉6N威lfュ1赫咏1BE>Bq(H4E槍lu.@椨o$Hef3nFff3g'CU^@3C>.?^X韓p乱|Ybq5vYyw3@煤aX葮\k)I3DbM高u癧ut"d?n?R篠AP^u樞凾h單"z狢|,v冽Pvo4郤-2_vv獅_♭qCh1峩P▼EC1硫E#2臻4譎淹rA5[-)h>+e|T3ajY[sU}xYMViR@4>D-U;; f揣<LY苔 _17兎U6L>JRSSF!諂I屶ua}I帛~( %@m'W1PHS)% 1縡8鑄(]\V/松k湛"_跂aEP6po由a$ 5i^R{x)IwF3p遘D;5eoYH9T,\如"鐫G1FEcs!J|.L!衞gOU GdD.JZq郵ce+貭徭}@5I93p1筴=7oCf-|l_Hb$!&soi) <.XT蘰gH'D%'堤H>6Hd \{; <峇lZ|* VCT `u<偶星 > >0f7礁Gu磽:_9>SQx9Gu淇r|+X臑E7(!n*r*P_{:Z0轤:{'BH折 ,E|)o(圸JQ EV~(MvRU%d 5 A減V`R8b1."粶$ z儲K酪(3b $ EEs釿V 跨]l遥啗ex\&u_售ь 椋y:*khX^瀏≠夫B8沸 %6F顧BX$jrXVVJfM T)薨赴if葩葩 )dE/RvX#6yi9p948c)bK吠0+(@D鱒,Y=w`P v5<$zaVtcu[ rsb冶(D&BO rNb}依*zwsうX*蜈 #_.m跋v{貌( ^瑣Aq稔UJ>G00ｻ柔聹sqn!旬派ZK'Kiu68N- 鈕Usc3XI\@摘m(蹶u+#箜l0泡\LYQlJi洙5(6rr=堙gLVモ［H$z!VI焉LHh'IH牲FO B Q陥L^WIs迚3y?蠡f塲T枅|c2|忍5C諺類JoOJ魍洋% k珥!a@<R$%-+!J9b3|5 cKhKIx$勠,{x(%P$}kl!]酎,a与B'希0|蹲.8LED 8L 梛%PrΒ&x=#9Y?7n (#0BNKWr33>{n"禄pW~*ifx2 okve&D%JtFBVjCQB]%歙冓5┬,Z^%lnqF;C Tg6瓜Tx*L:WDjeTt0q7tDY鳴tZ鱚{i7 c)W 廚=旧?%]E｡v+o雲6'R_`N=AA\5F\5薙jbjbjrX#.y=%,6f^m 釡zθERh2Au <;)I玻篶B h允~残9*v夫寢B ,u$, oQal u5 蝿RS(E砺GC蔘_I8iv'喉5睦W4&161oo声*SE+\F輿U2hmc(fl Q0剏O鋨|}XG8U:N]>I$ckNX?II霎q=)mMT.莉ｧR椪ew相CI>豁O炉欲琥枚G葎?x郡巧H ^ P;S黛?%2p/F匝C娯+a -Go)頼\rchB%Iyc瞼e[ｱ $T獸 r侵ALA褒3"犒 ,鶏$朔jhQ嶽C)湟- |j筱-4@Lk-`,.- 8FKV}o>1}di$b(V箋蜈Qj)>-) xNRn荷p$ 8[嚏L9[0BM m/R>9ャ做j$cu +c ?C"_?ax翌鏤6{([!#a錙&z H-(微,{@%{邦QZaT/>}8?4Ы媒d犒R`b?eF羇1る:CTW噤b8>\(貳(幔鹽;瀾棗憶]CY:eI6|,Z佑 1D./e 培qy 73 綯J挌&-r餒2T&n囀|Az送)UCFmo +SxU*=KQ`(o"JED$eR犯濂R([p:qU\7Wxz6<2\网G晁"&8鈬RG自そ#@榾X2岾>2]kSw!C`M^J s,%z+ ,逹余梺f?t+Ni+e f[[ O*h5l)t 9:(欖+s;B誕!諧~P0kh=Ny7aOPz z|黥wy韲7恁Ip驕tZ7N^枩嚆{<,+p斯NL&")[)8K+掀$-o PeVy'RxΖm1;彩瓷9'FC蕩免`'u2E8革蓄 cL[SdIB+0D煽揣pf[B慶e遏1A坑(''L S/[{SM1>2k|AP駅2HP1;ＸW:m?F6O:-O埔C9m+/崘rB^設@%|襦yIATYR勃〓ksa}RnE/但Q畠麾nC>米w,＿R蝪E}'FXj碵px縫E鬱e9c疇T唳8lk \ANAF瀬b7*{?#0 鬻iR<4j%f(<[PW:ﾕ傾N'2z_,xm虱｀xIkJ)lkNkｅ[]|襦c 據t }惻z3[1P會mz&勲u)胡禁dZ簷Oc 荊1g92杖OC鬮>8p先率&0Cb0+6?C8Vqp1k_!袂+蚋\栲\;h5p:iu[ a4"E~+燻zC:t7~J~Q 吋寢jPjA7{%郤,uU壙12造C|摶~HD~}{HpM %紬hWЙR|B+Cz#裂~)h.9$t魍 兔d[kTb(楴riuP$栽6顱 ( BP2H參#Oa叱ed`8tMWI[H!I{A@H扼!IzenLal持 s/孚79j,S寸J^^VW;+UO甄JG"7g:/s*A過wja狹;]^d Y米0拗噛0偃u珞)iR詒@CH.a屬:[[恪柚 &rv絏Tmv.U+;-Z=M\Eo:*#脇\Ksc輩a籏[擁~lr m4:G{,項倹\@cH) >倔窘化n奚@:> k4j, h翌F6ve畫]ni%8/8Z@亟P%Kｏ -%j悉X8J$u欅>/>Nl?Ah=韃Hol哺tp g 5o%訃^:yHb%Vn:們}PKW2jfd?j[q 訃(#_1]=RL9\KHUBW/AA鰓$+o暮@4!ih29j,&!悲M粽布6Ｚ3(⌒a nV @G柊@pwqB6p_n( C(x$$j&!Z]|#e}$k+F|Wp亢%7=^hn蓙g冪I&t)c朋2)深m2@W/暗)蠎\4viPF)K.E笏T|溢R8].；O[,-. 伎nAJ麩t1薙pj.(N贅XZ嘔=,Bm:'\#m9sd@箭嫐t叉Zp8JKA FZ返⊂%oTh 黍cYCyFy8e>]∀Fij$E._8=+ENO2"z6z騾橘0k]B%v籠NG f"P亊`蠢s;R .I-j崟>{x!k茯`笄T,V=@pzgy[ ｧ\|`# W兄uu$:驩媼#_$z`#R_般h皚32@QBhv~51b->oGr1!4|\Qjhz鬻#A]Gv 17 U栽Bo,>襲沌oO滓8" !;TbGRI淬Ca sX,S ke%?Y抱(痙r刷HI`n!,Oi杁Z6龝 H 蹤張#匳DaM%)ITQ季" B1笳mfmk!@N+%)C冗`|澄c$鈎r#uI@)vi($K49 WJGX3g*I>嵬( A[ *zkC+G惹OQP9jL$t8PCT -敦|魎_z]nn a0N V$)MQ n4_s!h:I弘5]wx=v76vbsA帑jAz _痴Z3+#.dY C]洗J;優-*\;{} Wi;r~CB]e>r..xTZ窒}P8(f6#!*T略家;ee8@A~yI猾^升9orxY:Q陀.Itg悛RKTX5餽?"FｐnHヰ6n0Q瑰^Fr`jsV久)^宀瑙??k*akhEm~lS$&恫^aq:憾-曄B钁Dh蚌~ oB:t:S謎#Q;Lz柔#!-,FPG(rwM`R%Q崚)O]-[Sbc72ef=啗p涅@濶7轆jHcGcX"0J,馳|4蹙F$*蚩咳#ls`ETAB BC-咎d(hcIQi[ h卉[坎棺{)dj D〔^`tt90>0Fu踊Ehk?Dz/EgSF$r>3 *靹A韃P>"\n\劇`幇h[\x 3E*G&'E皇Dn@w'u58>S_.鞦IQy[1存VZHe|P(擲3a9良%2y)dBb bj3FzP輟&~eエ$#/坿_s.渭m{ N膸g濶Y\9糂薇7.Nww!8sr936yU■cbzS5裴:Jcw*E%# /qk[w+亮M#r.x>X'捗a:^0bB!XFo$$\8lど%[p -噴L(@F]悪E箘H"2H 2%,sF栄aぽ0gu]e<[0^瞹S譯x諭xRUI 蒸 Ce怕kE6}^寇Nf5 PS3`K.k R,卉標.GWYC>:O核O尹砦+ZdB傳媼'Bf鯒3n覬,$%=QM>!vH]^I啣$Q\ reKOap(fU QqDW錚.EG炒k_B9WHzF寢6k,烟=xy~k '0PO楠n細茯A63a+IP6$K!%_K扶CIJ0ZQi4H諜EE=MkY7(eVM'NC z_F_I丶冊 IzrN#6xu]QN酖腰[`XuQx7r7.vN;jMrSFZMdjeOa 贍o N|>渺}恙c 2咥綫C(DJ~AV場f≪}k[4検>庠0| 5iJXgS鷭艝喚o存尚穆8e5 *4謳,UF,'iB,fTl}^7|敝"DQBetCFP.[戒0p&uzw髢[x \j,>XcTOlygV Z ])(pK<8#m4LT-NsUX,SXlR胃q -爼'闘 U)4]VfGYY[[]v冐懲D=g:c\<=G粕pN爛.O[s z%X}^潸BH(UF_鎰'古dk儘棆 9ヴERM丿^sBP`:慶0e)a(錺Qe;#+0GA垢K #@rt,J})埀.裙+mUNIIz0>M<+lhS'1MfdI^F^ 蚶PJV;S粃痢fﾖclS.kUoN)7 嶄V緘7優Rr'爛$pm C半%2\wF\別牢蕊yv@ j*5t腆$}X2m Er窈H|%{`OL%0{C］J`V樋H沖FfIq)儲4,03 -j~&z*N35 疂}d笏-J'蹟`qてHHukn)z揄.G@`^].5o9團P)*zKF y }A稚lg)薗噬冐迹h n 扼脳_U騁?飩7+q癪瞻Ac掲0 N雑rb9 L=CF[1d 4J9L^YK10蟇C煉γぱ FQH12ZFQ)質5Pv \aH)b. {U"xc勝o4S爛Q* gDfDp^J`j XRfc-XonCh 必#M塙m3%呑鱶DsCK簍~箘F#F>k; -0禺-E .th(匕Y晁KH6|★{dBQDJ|+豺iH"多~0+JK"I -AQ8!sx\吶%R-E+Z由J*G素r+^a顕qLrugr…<麦dA^祈塁Fu士0v[&M月K嫗H眈"H44erPx:EeoZQ|h^#グ}PdLYr媽o柵EEn6XcHPub%Dm6rG$z %(i澑%ck7:5-n>:gEKlz10５xm$l'[ 仰td\彊<鍔lFUQ'v~*;s!幅* cu驍7霪0Sl] qBtl廉a--ys勇ttRX2廡iIu落&芭5dV6v宜.o^(哢/:VF6`NEb+`/4.KTo g/#1$拔j\8梔PI"xF$RY魘H(琥rRjKt _麓z[hQu[uF\聚;"a庭D+蟁K2ieVs&p-*o{V(osu&Z離_?~:]nq[9Y} \n^5Qro >倏応翼暴6c+fU%璽n{}ESXmK;E2lQ酌m5忙x$ -{A唱X1DHfpoOiZ{A1^{S@(K+銑k釛tVFuQ bu掖/逃W森9$Si[K■; 縫mk該4mG+\.捻3G&yQe桂}{姶Mr曦o蕨o? g"h(/).h3駻7_M!&桔')[(r4-薈4--#WPZJ4)KRzUh2屋x ezN猜貍Ix.Ζ)&.&〆牒-4&衽24&YW/%さc]trF&近 =.qtV*e}楮{舊`>l "KuYDykl,U"W艫卸<W@){v^s粮ZSvWg歉 E.廃OLI4應S欺鬆］pQ D*{ 2nkF\[^ d4觴-NR 駅l叺JA7a瀏E C登E$ :C]"VCL%S-&?脇hW\狹O.e3煥Yn/ZЁ$-T鞁wf)蹌[GhN単羂掻UJ7%F!＊4N黷Z7xBm+Y( jZ秬R$+:$n佳*2Q#x/黒~a*.P.哇KS脹+H<=wRv!.N隕[Ty["0`+$/'%犯n耆!|rX]pq^K侫ﾖhQFI59t侈>N$D,2倍MThd FBG`])9俶WYfD"!!悩"L`e#簑KVEOSI>hp*i+(_bh}h屠n#Lt巒 R}|p鞐殼挟定絏h色 zy_g qApN&geDK \*wWI@Q}mZ$dA_B!前kPs悁/~w飾%裙En竝35#7*眠Pb熱~ZT陶9橸h^y6同: EW\t12:K=~=r巻uimXnTe黍衾Q}葫uT)嘘y6?D@g^肯藺"3e} Vw3(＼>cX:3Qn:_LtL1hu淇@御)1<住& ｃ磊~胥n黹]nM ヘe捕6>v瘤|瀦嚶鐶_Js}e赳k蓐趙0%開UMvＺ-$cwS|G垪2靭蛔6"),wMYK+0y6鶚IT鬧宍T彳Xfi ?=__yu麁-宵ovWL掟3A()xwRV ebＣS柢d3Wwy猖株q2u2[揣1{L甍KAV蠶吸#筺,qT◎<緘W^]Q湮l借$鑢Bf黎5*N彎d~笹@A3亀.W?{ }CS}w饑OOxfM沙eLn蔆房v唱?v菅p LoSk~{s0狭激杪釦鹵穩嘗_2侶W執q)c鶤5鏃?蔟o_u(n/騰g z衍笂黥QTd←Z詳9Qm蹄BexK鐵O射x{皮暝 Y[緇O{:終Akt.WаG$;畷/KЪX`丙#3_fv.E\/醢濾達>;c7t秧8x4!7o>槿淇~x舅Q睾勗哮 g>PEEo敘![夜:圸iq$u 蛔B]釡狢]1r(FcqUkNGH圀(?RDi\ Eo^ 曼nPQﾙR與|[Lp J6&J(躑)44殴h$擡w]1{pD埋駈 e}lFR4|L.*&Ｙ崟([b@v /4H>HqK.`B拜U#09#P_D闡 GPhy.蹈=懆埠 B^I鏗2t(%AYF{H)そ K(tz蔓9Kfab<-40'lY'=F袢嗷囮;V 潁v@[&霓c蔽傚T@椣R, i2x ]+置<)T娯RLO6.Px9p1e杣-1NQ硫.~*ya齡##OOW =D+0hZ"鷹T顛妾d89梦〜HCH"GB 怨<~3曉瑳V?oC=v^Z弑agZ3%du7 %+DBKjm>H X=bFH好h蠅/]);RL舍O.BfI 冬 qG宰=拭;+EJwIuo?盾Zws刀o3YTTy烈弖~@l9~鳳XY`U欧& Y3#iR貮4 D=aJ黯痳象L邀‡HDMNB>$ ПETm笶齠|麝w}w 0跗A菴 筝-6Gl6) (2JFQ6F =nEDlkuF ,。m/v=}|m鮠^JnAdt萋s!}EY-({]bk屏釋 u F!( LaJPRTv ζ-V(JpJ^OSFD;y(蒿 P"u%)N掩SigXWJ＝]1B3HIZU業G6\8:ＤoA.茜dU9 2_;Pf04e狸OQ T_=="嫉y3K aV/h[6r辻u_′>~1(g/5P"sbP餃J<埠劾J(B)襤 ZF\G)Uz(8 彗7Mx.bDZIz_@SnZZjat-o6瀲壬BKCO廚uZM_I鵝!u睦a犯M喃lMs啀夙k@佰NEJH2gRNrU(_=@O2eOHf=:]n1.qDm^S)thO`x2BN=Z`r害k榱r(Q^l鈴}喞GAr1?ic9v+誤\>=\cQOdAk@ u1枩^TYRG蓐{燐)fΩYU戚vHw畭Bぜ&(櫨Q{ 紛-_t可f筮乘臭2~Mbo(e徹JmIu2mI H{戍fo魘U黙綬0u欄堪q) %F慙絽76gD0榁4R @;`L-p孕=)w?@醯l3{k|`摩UHR0喬]s/]CZ)H阻HR羸NI牡7Q靡 :^!鵠b瓣\Bb!.飴^-B62`6@JNH $1匱@2!vB?C>F/0h-S T9F#lもW[a1jYJVe#qw#6酥YQ_潁 Oe缺rdeSKS`/R8NO(%K吟静弉-辞@+ :KZQiQIIQ3ピ6@P='藁pwXc g蒜D 牧披cL>&Z 劫蒜$d[瓠齒#u}珂VCB9W7HZX謾buZp 雍}$靜G貴x柆(F_Y?楫匪$澣z#^t夫 r\Mf/aみ郵l#瀟_据!氈6 wQJ( Yh'bH^VJ寸倶r-3jce蕘鎚><@^r`堤BW6qUa"1$Wk[DaZb3 zB@鑵>M鞨w血=娑xDaHUBH\Y9W)G)x静F裸9#Y垈'~}劭W9_*惻醫](r(|~鵡牆O;!!dTcB幡&Kr1<(2 -5八= 盪\P泯唸>悉鼡?~?勒b(7_@0w Q^BEJY[s`Ｐ(X@qV8vqLNP巵[NN@P=YRB詣崖^d-肭唆mK/癆|w jT2+[,僭uFrC邁 dMf]""3!4jM餾=ゥR0幻FQ-?~N;L*B格Q}d3~p靺1 lﾙgLeN剽--銚$sIQzyl=Pd竰dhOOg 个r~"p 5XFddIFRWK-Ve壹2E-ニ%-(c$SA.YW謾w;mPg燵J?_Mnlc, 1 od鉚2 cB`;4ZRY?~魍?wt淅A1d鮃5ik囲7>w甥*1 .9jH9R e3 !`渊B声{^6祺>J.D~纃X\敖ｇ尖'2X処XQ y+3X+崟 `e共cOL5fc0l∨麦-PW>`? P$9/sr2!ZE愼M9aCIp*Z尉)E (l  L k/NaU((nDQYwK],>,隼$4鰛!@IbZC9桓F6B府>R怯QF簧d關 =aZ?~{:}z-kゃ<&Q^o禰豚)tH汳Bぐ{!?z :pq3KR<2(蠢]sA颪C!5HgQS/撤<砂A3@.即FMRJmg30wXKU?tsY_紗bM盜i%e62MzbHUBS.qV+c艀hUrHi'M與=樞 )2勹5帆mby6 `VyV;lad厩F槃s毬y[SF 勳=f0yy&:$o(e!vc巉u;3I煥c!i壞C%播`l}帖HQWo$逬F患S>)\游I朔 H瓷 L妨=H)3罟QNh5v0尚嵬el\角1\8跼\祿峙7|ZBi側}^д HJ卜u$o[_宙O*Q6X簟2>T\hn邀狆CrO*#w絅>jZ|掘Ux]座 TKrN鷄%m9*~>"k).-[SGKo)*>:k]>zZＡ:蒜R0"b0:L>3ムx"|!Z:弥Oj{?7襄vX () ai鷆簟nF泅mXd-/JjSgcDRUFhムE1QVZE%lJl2bK{1Tr108[la旁&闢nqm眞j鈩2i襃AN+YJJr,1k(^脛波:倔槙J.=娼~O B2+E4晨A{}OB授_` .k鵬(齪燮_W-SIa嘔”琳eMSPQ^).`#殼T" 彖4'!W]6F2RuH0&7p3VD,余.N栖粍!yC^ ;G ^Ti/>~p bN^Df祀|鴬5t_KaAP 5y4梟R祚QI皺_繊f炬C@鰈h0lT 4pYF`apI G r5ZdL)バ@*O>-K4v濁 疋V tJ%0>y]韈へZ1F7汾%F/Ν3%`j鐵Q.=H/8[#"pW0⇒ ;YrvZ検y-V昶DB|8ty涯#p孥澄盆di4"E~x"QooYf/UK5g#HX}:d雍Lo& mT4 ├鱶<製俥a6Y 9-P霍 _K誣~ T頷oM e丱JQf/轡[ 庫&ix V(礒/K裹0Q 3B(c3@s-&[%x}~rk"誨|Dq]kQU$(O& 顆翆P6弧u機Pk"O仙k.`H92ox嘱s(9AHWK蛛/f&0 +XF珞U*>N:&;tJdYY[8<[0vY箸j\[族MUVAnshK%Hh^#j1s0\VYp膃\XK^}KV/#o6c羨$2SPZq' 麝uv.1;)j6'f\飛t蟶_6 HH7^齎熀^vS琲,P}Gs_朷!妙o札Ooq飲Vl5ff-緩NA191\#]ﾖQ√"0*Pｸ1U9*謂X,H778雁鯉唇d9Z'膣圄nqO臟?+貲Nl宕@Rv.jC\}褪}L:徼6DN3c蒡O;3(夘x_yW@ eL!JDСo{Bo}Ur寨3F\&лLjws猶刺翹狆f5S`yLPhC4 ?^嫁WB龕|~t93>搆冬k+}Un黏 桑樋ne d\埠 d條Ab\2dT鉾j%fムZ楡C:"p#(襄E9V(噪S^6 &y|4LfzUD朮;Ydiv\=&ep:xMROT. !p戲9y狭{ &l洙鬥}j(、h=tW=-脇%{y*Ej徨o[K 簽f)Im*U8^l苓]BYeLn %揃恫輩 ^*,舍臭断a~飆呶7Hサ岷帶}j&ZBq 0BGcJ釆xu9d5n" /嵋ziE%y{ Uo傅 Z拙!吐/x(蕈a11R湍NF4`^F9写56Eｐ覇?k >eY(x要s g摶鹸jGw%~z>H綮j砂坦!1W 獣ｊu$m[Kb $8/c=霄l[6Qj*PQT/`$wc堅+曰A冏K\@a)\:＼AOo1Avip/喞Fz$afmzBHG~F卩?oNqRhO6FVl`簽3J *w扮c 2繰壥v,¶H&%BH&y+Wo oC分e$VZKn* lKcQo+h牢 礁钁-_8HOLs^cM(OQ玻^ 禽)Z I1嘘パ0qY道r}s)APcｂ\UJ渫7}dsxT}O{) 斤$姚$eT[RH4#NU:}番}TZy I>爻K@-_5}1=v346*[TCGT#6D2V集F亞~ 祝 r輊W'渚Le,_, /F髦INf\"cg`"wg/ヤm,薙耶洗考E行3cWP8#um)W ~D">5xSs"襤<.劉mcpg9h$魃nGG5s.dI愨8IlRdgIヅ 1}u9NZ[3y怎≡EU各x表fp^sX9r俾^h邯Y(&冨佻`J@kZ-E#MLFGZvVF"樰静AP!褒s怱~粛VR|,tmu /K懺(I_5cS4賃F>H:_E醗W sr{秤烟C^?|w@}yu@6R|}[X?昌#5GTNLhQUQ菲i 彎Yn8m碼嗾尸sS=~E鳫$5M #LD2EgxL部yrQ'/L粕S:' 梏g$巣3[ "驍鉐|%]資錻 XV=$SWk勝9睨f{?觚qc団qT度%dl>dZ最dO{[母( 北賓Q夫H7)ヮx&!.3Gyh A1寿6};>I跟釖餘<]杉H_譱xKK珀K>)On_*-) 嶐4Z,C:Aot^0#t2誠it%qL3dGlO&輅E:$y~y1毒v{tqDﾐ爵績X駝uc__.?W7琵1^>低i.~偉q71PIe4_+lN掃` A=yzFI;>C服d{%6_7wゲqRo[:nJ夐A^囓IWI旗6:sN?Hg*Xl刄lS鐺52{'YZA:}yZ渤}8恰q}FK搗/^$?;_7EKp {頬蠱toN,T)m韃T$k7P o/釁&竕椏`N/}官G,8}Sj!>椽{~x k:qR渝\X笨&x~@"惑^q@躇R|=驚uv8>^:岐>CMEt苡d tT愚史楕P`O感6$95C档o>\3M4緊*F +4r 5mz|r蓋-F<>>??!gKお>XY1饐3鑼0!G9%V(YC}y]?霸&Ot聟]},Y繩zz渺o認/_8y?3NPY百悒@|lW6Г葹na廡k莉o襃yN風閖WC[+&哢瘍20隣^7is+3用T強…X+UY9r%"鐏3+E3Dr4x\y4u\,逼繃2|zml靊U忻3V8:D1尢ke'm法碧^ 龠錏OWｫ{=v:Fs9DC蝠逡)tXKl/:/輛窰~EY"燗{X躁l>N廚鴪 7mHbz<=gnH鴿 笹靨潁c ~<畸磔Bv.5txh@K%E!h課J偽丼U綁?y\bl dHoo8!r1$crI.92I]u {TMuki 虜-l |沿>灘旻羃PF髏,qI[rY 鵺J-T^勳閘夙"恒;諚阨4禹鯨Ec萸zmeuR'O67Z[~偬+)v?d/T{申D_e?\87x鐺@cY$轎濃G聾}Z圻湎bi慯fa~垤_i7k綮℃NC枋Zlm<|"MwE戈d(|V/%pcJс[宋t禽*磽 九3B咄pToz ln-謾qunpw誦Y^$Nu O#teポ&i#l00{RC,g5鱸裴/[GlvwD醤*雇~-xf許焜鎧W襯6&沂O|zxy幵^toY?@B竕ｴ Cwc 躇-9錮4?~鏨104譖oO_袗y獄?q深>^w囓(夫g34簫-w蜍ht斫侍=DDC忻8 T;千Y泪ﾍ-汢nbXfxU)`鏗,漲s慷e慵tm濺$FpG#MR#隹wU#胱NxxV~yc__`U校(_航%/q":=}'q'O 臙欒欹kx%kA=9n=.yR~HI,ス凧'|蟶p'f8}W;]<侃4O%\ANv56索xw{+r.?iLXy>呻**Y|s%xm\]{鳧y'L%峡VN執#L#哩粐臙\><溟w鴈窩X ;a7勳eI>盗(i5vl*w茆qh髻臨wCQ胴O9軸1b*覇9=^}源K揶'廃3vCng,G?pV'k108齷NpY}'bl鯏鯱>{-汹?=<}f9e杭Y祺t樵c 講H'02a':?瑳1} 魅葩o'w(/Ьn~昭寫桃iN9tf3?]t,[功i蘊GTP02J@譌崩&ptz,[zu$yH+幽qwu86}J 'B2 fq)簗畝bDWo OT)-D 庇BucTx<衿--Qv+$#Z="7cT頴`皿碍(@N筬k|蚰Rb%r"檜$# 6#Ph2$Q1. xR%m} kA %;#5<]X@90 v 9rXkq捬築OeＡ兵};'R残}S("m覆iKQ*vc 3.善I疽材9Y(]q!]繦;0鐵)!y洽 B_薗z`R8l斌[wM1愼 nJヌ2v洩f剱 mQn穴+胙L辰,z)D3lq^$QKzdDZ043SJ_Llヤ禊j催慄#≪ty-f跂683D=A$O v(.VeS$ +qti GY{qE湘z{ ;潤n<2h∩N$cjdIqj Z, A)N\眥(,J[R糺jbF5/ 岼)犒Dz垰稗y{(g3?4&@_l=(甎k 蹴傷p折^Q現摎8S:%m O2j褄e~%*k 6dMh Ya$ %頤繁|#g倒Wonsd1v`~:i閖Λ\薈姶燧 ^ASHe'k(iz店{Z睡%z+#XDTWXDB5MA指 彰Q^`e$`#警*A嚮 S&$鬻 z:A3Iv7@@H拈:5va奠<芭 [9LQ!L7eD褥^)(vk黄^゜KV=飭$k k K0肇V凾%右[u6騒n'`@w0Z栖PdCN癬d!a繩拿 &稔y[罧♀V&c-lkRJbt'`架u 赤@::0m櫟賢 8 taRZ;%o%Y惣G=:h U(0]0 0/[ QAapCB 蒼r"X閖f_收Pm#@T睨煥匳摘~yV!H TQJ/#_I├衽 fJBDr5zD<渣忸|%L` $>蹶 W媼廱 t醺vK嬪BJBhR%:E9[i-k`D豚e6FSHよ9英g;v`|u暄 -4p./;A=戯挺嵐 RbrF栖fDKFR褌$敵.^v!篆 線篝906`X弑羸x/;2庖ZhQj`D跛cT;4T溢`ぅ/爽v卒9皴UU)cK<5yG tSs.桐RSヰl.Q%wg丗R+%笨+\隆i S&R#VSHl&:<&nc餝`-LK/XBz恋崕烽H#R,FiJYoBLi4-C8RK 憺濁 e7嬢妊^wB嫌娃|>aG_M鯏q^ k岶ぶυ(MS座eEJ?グ]c杜7@WHs$K9 }>?8cL'd+i9^k[04*睾T,トA{Rd&怱e)J+蔘筏p餠vk \Fl5w迪maCY2.r# GR溲N)cL2擠3j20 伎C鍠(>,>Y/ XK}'Osi4l $y-9 單;2配~遭3g0uz5a5nWR=< 9~2# vXbcVd 96dIt#z} t+hﾝ)H&^IQ⊆ n后^+64P`rN[甫G~6D6vび7P|Om`2BNyE4 ESzNy^zQ86delTy6純`T與r*%4e$VJb)髭 &g&}[)蹶uQ^)o篋9P13H MR-|2h@ 蹙E{yELd.QK鑄%Ie]"J闘y _"l鷆:耻 ,d絢 晏CWC剽%Y+~36\[ 砕ワcふ(I汎.C:X<}[RKtD;K茖`.=)+x_Qf厚ZM Un4%_-9WJ}"A[)dg2X(凜) 情#晄Rh萵仭+}`tR祐u u #36Z)摧6F1qu1#OS '餞7耆DGIY|L 娚59kJ*~sQL_8^I.3*bg?=;p@ｧZD峪P=mI 癨08WJHtOJKa鵐$JY,7Cju-L<疔p>vvOzu>}xa/[ &藩途沚xa'垳a揄sorK@黥笂<籥\臘8%脯巨&8gXbhf]｡vqV3TXSxDp坂13 eBF_|UjJ庇 TﾖV7ei,/B垤rYKK?pe蔑宴*DVCJ鰄, p{Es4蓼鯊R>k/tlQYVZzH,n濕W.йX悠{y?<}O航5a>W扼s"5w扣矢供|eot數4 HＨ1F个t `;y騫!^J{ !PtJolJjWo8 寅Z檣.孤Wa [=V-&a)6bVu^_N).T[Y&6!N=鍛woueFg3")Rpv踊fuy Js利n僣w2TWz 酩逶~F*/徨^F8`2Bk:Y 廟抓廷(s姆I耒xlYK`XMeQNyAムO-!栓e6[鰍B徃mnR(賤茯 lX屓BP奧BM篥Zd.Vyf8Yi追t8%W5鼇橡[x{s頡;狖%Qi,Jg_с^jr>:wWw踈[)/y[Hl=m標0L!y|\BX~KY~[n%=,/808'MhfZ%筅o `筋 )m9OX'訶R冰桎請wB9DY7+#y栴XcV纂殃 -j\x8}餃fNs粧%l7 N,Jv芬o+I3Q{Z梶 #lRsi#vKv{ `W%f]?~竹D気ui&UOxGdx?nI[VA}峩 d :+SZ-d={[^ KX9=n;%k翼&)u貝ghf傷oq&睡iW$漸0ヤ陽潯h6UU^K?w崎)5Ck$Q篋Z ] 8n.甞"ズ-e繊pB肭4kHQ7|dTU.9?,_4Ro&!Z6oK^橇b\jNE%T$О躁F,j川u[ %a'W J1袴94%5R0掩奨 j 0c(唔s豪iHnJ爪<6LＨ:VVSfZ"{s[S9 *wn^try冊k:I葩口:"n wZ堰舘汕界 m~|t9M3Y3c%9P&(*紲1 JPBPtl14 掌PR旧8Up_kY,eNv錨諠8Y鎬-怯IC8TI版轡I2{羚#.邃i$M4筧qs 艤Q!D90Hh(M'GXス窿9法[68dWup眼LH分濬ak'd$yc':S萋,<飫OA4(B)"1Cdb-NWH籾\uPq+ FK<髓CpVV}N'$泓 %nk;迴5'#T%)tvVJihzz狃cY)*Z捜a4Z$~詮楽h/鼕'e VLT{暮&Fmm Ze5^29iBQ:BX怏)\IX憺效p石n寃託#$9R胯bA/授ZKs)逋烈F6}2;+E*鞠+J"vg6`AR起町j#p晒iS蔭s> {<_ 寒@燮|VhQ/J1k3eHaf CJ"3颪[@扶>(鴈2 .['a"+2擽廬JI<=_<6柴lM$0lFo+ Wh I淨J[br竒B)M&xs鯲 慨l矜Td' P.g擡3%UmZ4IN6 R(寵K＆qj櫺s`磴[靆NG$籵O@CCI O 黷 G]~0n69敷.K巌SrcOm|>)t{釀eE >泰}y!}#[)-A往Q滄AEymKeNjTQIs,r^lM 洫n芙繕湿.惠E2 />&y9急%葺慂陲∵}￣嘖@t,1QDk%-4{g棆懿敕)|cwo]iv它@漿F,%$5o[梔`lB#<U饉xU冠Pq`#u V餠xIu#P,qHP}HDVF(V獎~賻WI`虜^0(=/(^凡1ヨK>(zе2.弉M]TE Q粍`,z調W潮CMbk%g](Keyueg]o廈&izym 1|'6WUm]溯}T(R盥 6kP}1鰕yE}TCou霜Ma[ vy :: 5;3襖lｧ" ЗW4OOF/?U9pﾍ}華1c2GA =Ｈr,f憖貅*^E羊L扠!探fgkacN策 A蜴旻nY8夘IIB泛而+舎@W柢c=p誦<NY "xDhS1M 5I3晧_永鑛_趨Q5.棠v面0S苺奸T爨Zyda7e6 {M&p? U+9/zｪ跪[Q'"3Y.c周Vt{{1!2 b:gЖh| oO_χy鬮t-學ht]%jl wD\h眦Z rq轗G翼x'n嬖qN%Gu瓮B幸E豬qR@9I>Uoe 酎F>t'q廠+\j丼>P|pas入WWpf粂何S偲`螽9=K:5^蝸P攪ljfP^`#2bd数j\b\vK劃髄琶`$w99 XSC3J敕莖{ K候俣Preo${冤I 錵SZqdO//%i迄 迥A@)a0r絏~.QNw{7mgs牧X顳筱zs>}S竣э8`Ae3\橇 oR蜒g+nN#{u渝Zs|禧EK(GZJ+桜笙o~mt鍋`.E"活}`|'觚;I綜|総Y><,K\;dZK-Sr&g,9/:I^unSI8pA+[:(B咫軟{"DCOP殀ImRＰDU3|7%GrQ! X 1 gy\竏R4闡Q YA促gB]61$HP &V'6>A6tZV費\I<襦. 3[t"y陣v緝(1+q晋g0Y}Z湶:#)iCt_ 童8A}e'!6瞭h9T.%k`Fr>(u習沸roVnk-捺m6學/7経ｬjX鉾ｬ$剖Y薪XF:0雨7.:O^$y爬%BIJ◯!DL禊~+T"A SepWw.6+BJ嫂3f EDm!dgzt) PO_m4uYx"d)+P Н縊P">%B$o"滝3*6薨1;#||7 ~pyQ]rt.>,選0u>27g{\Kz恙<承(餤.擇屹/L}}$}dNy0aBlqW/人a.藻濂yJ^,-V}樒t怡;掻~=Vp:/r}v嘉Fm\n籟v 3{乗lN|:A1wFNfO\ 標e凧s.D6Tz4f^ HK}Jq舉Mw~q<O*kVRN5+veu餬j築Z@*@E8#`u- \AB性&UU%匣@-*>Vc0a9a2dB>d]rRNL鎖;限{ wm>Pv g2(l2文uz候u242膃V/結e@ShM茖店L[丐"HzXG/uL5HjzTZ"V卓!R７R諦jQZ@ousy奧Y=zbSV o噐B"Y!TByPl 癡)I勤晴KL殺Cc.:=zs該s坂},"bWYU戉Y/T\p5 Dg8r i睥.IU簟b8麝算龜闔 W,PJO熊7GM棊_>Kj蓴L豐-sf7}A諜/_H0斃RVwJ! x幌+9Dq/赴0邵9EL>@繩`%LV^鷆)^ ○X竈C] Sh.A.u u5糶90m)E\W;.ha鹽,:{(# :V,勃YdaX釡UH藷I!蹂Hg蠎焼6|%CjM/\NeU<陵鱒jC候F=R"拯ZH{R鰆6Ys SLv蕁Hg%^J< 堀/m靆H*.= 惱E乕E泉錚沢丐"{Ηx 'h鶺h/B yfD%5N引癨;X{;糒g慕+8??=\pS|dwQ簔Pon+*A +$エ[%!Cq)VK]>$ P\j VJvRlKWq飭.&#庭jQw!F滑鍍w }T(?E皇1@晨B,9f_B _#鍍U0盆攜o鞣Ei,O服sI箔吏|E虹e 醫鵲b庄豢做?_錠6椙o鑪oo搜暼裔=滯歟杰9'匱住冊bVH稘"*.872@h餒.vF色yKb-b\'睿)p;zx店Hス/柎/_/H礑mq楫pHD/(E8Q5;皙吊腿dｗ拳 J6胄U=L峽j萱bH9EO篩遺 ! \Dj簔i躅t9bC;rf架b|7究恤UQN R4艝挾)4j_克暫 c.N UmlK狢+W筰蠍椁胆Kv#W頒:q^2E>掎`SW資j>Z@OV.Oヱ^{"A+ hV(x Z剪ep豼})-7x1_[,Ph4R_r*kxd避@%lR枇u&譲殼誚~o濘蜑dibV?#h]$ 嚠1+仰J3' $住)益b>H%cCjm皋4;)f\xYF:9+E S \_ PE{嵒Gll^ZPι)r#$TR綢郤/蓄E廷敲t0 釘o~齋R^瑾@Vqa\\c眄[R螫yf;勁_zAF父h j燗%DOB刧~峡壱)E^:4珥 纈FY~j/+ 冕W yn+c坩熕N)Qr廢臂l'lkY+C%%@kUZ%1+_8q`摎usfk=重u-VoK@?帑\\OI{q 頂\z:)i\湊褥!燭豫擲LFJV$+臠觧Y,淵`[=U各%3@浮h開& H:枇f,rX%簸ΡffX粽 99 鐫faH冢&By+/篇 |j|[W+4>P:7#Ey{X{乕'GH+R瞋CZgV [+ ?.BA6解MJc;1.c\菰qmV[?r機-Q-dJg\8:Rza楞#*-k}#燭.s梛t隻w:単2pOvWJ惡jElt.|$Q6A)8娯T伍閲<臉填5凝W;k$t(!a治雁0^盞RIB吩X%9N1+1e!4rGC#u戳G*-}O逃濾:FD 饉0t@[b矇\a<9?1a[D凄ke1F4n2x2 "1繰 [[Xj= A梺-c1銃mkki~@ $RIr :成qk逃].(Le v ]xizA, 並 Ze!03JU_Rc_ N稱t驂\'祗xe苴黥綮EwW[ 満U:EZ 蛸可7W^ ] K|&摘qI拶c鰭-ﾅ u$犬w-%H%{鰍Xj#^酥Ｄ$ }S,kt\KR科](rPa討丐t 頁u髓HH悩*a -Z4ND_E(s7F d1薩{}@|VO6g}~1>去:NPb[0硲臺+h[ wqdd:UJ,t-j ]P:?穏梱}Lk2崗:e蹕J譯 &ht$eqL娚M+Sf齊rN[p^gp<芦信Ft#(iA yRo[|器FBV .V2孅yJClF｣@-QEr /vI3#l!qFd4+定BcX#h=y._&4 笊庸景哺"kY糶u藜|Sdv.彝q狢V-^P8k2.M#y[y1oRT$ljieB)w :1抛3JA砠#<=)(R4警＋` G氛r00~HXle9NB&0鮃onmk1# Zi CGK`prF-`xyHN?ve鑓~(&S<\xP瞳]=EK粳x=2W批2n%PO6_-%I並C41v黄(ghy冒Vc}#A婚VB US43bT≪R;@tWi.KцX(UФ蚓6(Vcy#I:猪\0`~遡瞰LBe7r m Qf Z)YRF_&gdJL"X:A3OJiEsE'盲$I' +鶤'MNa飄[ xsM寤VOgwFM;W^:$瑩塒a/&齔箋Z魅[F産\寢vlq)r 版>5>舵o }FIU繆fI Mr歡RB]b>qj=┘E}rBT蔔OKJs=3?橸搾/1嚼ブ9Pm郭QD褝樛s 87)0Hz3襄N. c'd"筺17gC/￥xxi/(穫Qg燻匪@I{geg6>VeK=循 m>"ｘx疝&!0詁vF祖.[9LB X)Q諡RXlWX惓Ypc !u皧滴眛K忽2L娩|[[聿-応薦6亮隔丘/h今%:*Iw4B衒'q杼''折.Q罅. $C-JAvQ*Zw.~ oeUJ}lSz-.)m @*s q]3Bif@KL)l寧 |$u<[^あ0>"CAyD^tL|?~RH微>5> lMzky1a釧r討S"o64Uxe裹s嗚VjNa9(],D(dSFA"1 D% Xr -=J噂y潁&K0瀲ΕQ?*{n殃d$簪 jZL]fWFj鳧a福0L僣TI0Lqb(XgQ快x) pozTs`綸3ゑzTA]9Zこ貎d>_P8yGA 4 *_抱W6}do^駘縛}S/s^`/|Q沿wN訣XSxFmKs ^h+] $揖yl?'K'g驫a釵N_}sF[ZさbrZk王h鍋笄昶 .HA[･D#]朏8+q.±W4FWGLQ楚權,8N#惑h |_惓~nsyG簧QZ ud g Zg湘jpX@CeK芳o -`|e@NH|t鐙x虫譲W蜥}駈 f$漸;W櫨ZmcCy9蜴癰C &dxwO芝oGW_LO?P0n梟Y楙KZ@去=\2股欒x D侭H<>G/O系醸鯔1W鐃嫦_z8Q}窰t%yR>F苻ぱ^э蛬e/恟?q-v磔}UI漠v|牢^A9蝨臟褒g茴$G}VrU回4析 {ЗoD@唔o#0 {IX B7_qu,JORpI#uk(p^F^(ph!ofCUFp|_)8cGgsHX' J珥蹠.K牾べd!w"F~ \舎n遂Q '^@袮tq$,0/Ib\JU0-S(}AXz$」MHdJ霈PY@椴 占(io]1 E軫郡50禿2x),d楷%8r穎b`-j'P壟AqwVH H$y駭yrd+#!-o\nkD醗)y-h AE*縢NbW+A怨騅2@iu%^ ,G亙 0yVFE劵c;-y{)ｬeEi3v=,Vr?畭+C鱒N4'P9_ 条[1|J+2逃4西 i覗x2*iK)x7["S迅75,B2.>K([TDzdzp*N-_?|~;郎4g堙'kr.5@9鞴K$kP壺レ=I VW'!Glq誉s浤 Fa3r`7:$PfK茖$H?S!2yMU =[dgD MKaAU'hOP《WA2蔵q*X'~2 \/$勝@oQd&lk3.x=B+E>ん r% #疼 8?LZ 7&藾1}r)p 美#k,2#^rKdw会zd\激絶mH%邀L禮h喪?74cdhE. 2Glgr?"4G%羅飆j Z s/(|$G 霓:,'u3.M:錆cP8%彑?"dQ~業(T_※?#pkb1T yvFevi u $ bQLrK`IN$埜)<輟;&с^7y9RaJ“ l$QL盻XI@sY0?mf3e_列y')餓+)伶4qgI7kVv'lz 燐`zw2xx芟!d丙91 藝悄癇辣沱s折z|^i鑪跖zr寄w_[x?\b>FY8洸e6ve4儁*YR EfBe#6(具俥v?@篠F'b0/猾Is5D.M 142s醜賛9w廡徘 ;┥{twLn鯤8 B晁Aq$ Bdm泛p来辭 搆`9U警迭$傘#bH蹕6kU6(&H ]6Ｈ誣愃K-_-rD^e免=\I狡棹]Y奚WoU}Z(%g鷙4;t/梃R莅S鏐`w(2( y醵^&涓1lO fp庚l』MqCK~[X8i怒&+YOt7:o<:gykri*v召8 H[+ZX[gO:)('6ZOds"小lZFTVJNxjz髞|!;^T切南n$9廃$$炎a抃Y)u岳B]8猫u(jU貫7杉杉躔1w7C?xU\_z i雁Y'eizpG \K溯p計#erW #J閭Kd3?[-6槲0{q郊簽7Hm\u恕zmRd髣"ANR`1H p,2&oe溝cJl術}G+UEk)o.戯v;.-rWDV縁8Hyy=R\?i^IRa\+%ゥ擂7/?>=7WOiB9 I{!:{9dc}}%`拯'Ns' ?/8 蕘h銖裙∇窟獻牾*X5So~JIU年>竕JNd@瓶Oi?V>墾&.ﾀ撃A冲v[&ＨMj.6汗5aLXaE句y那mC謳y]fubGd Zx7&J(F; 0NMy&頤]z 槁3(筏[!y]釛xww嶋 c眺z $wc9坤x閘}w左伍gPyW甄澗^瓩П~8&T5<[uI樵n2j4^k<卜mH訴wM6{H))鞍)mGC+I^汪筌0f3f8D>^ VN=蒟戌:嘛W3=Y]NFbUs`7昆`!CR08mQT4I莫~]a8絛2N{A0ii?低@eS拑XavZ`Sa9L I.啅:Dヨ(8X9_ey迭z,歪 nec恚稿吉(r▲kgsyj装` 釖nv&Y瓷UgHwT%-{'F}ZLvrUOga}-tqAnyVGq<軒/]ne'-=C撲ey~x~瘻8OO@bCZ%嘶[ o> ?@馵LE/ +fHΜ柮褒GI据t~O擬'+塊9#'H舂_/閘闥/S册yf征悽}SJ99<wj.T肯Zf}rT9藁囮P排>I_>QU催~:5mwRK浚[釦%糲Guc敘x/鱶Sぺa,KmtYTH5-7?窪#7g>萱bN_臨@ :g劒D制L桷~w病巉鳧|[dRL]\nNk|%_BI'4kwн/holi栗pc1~zy喪)I^E,(vGt~浄突U潁Q0T菎熹B枕y樅組Jxz=搭體j(#v5斛9_}|&o'穎 w)E鬻fф+額/k~5_芳_蝿rn;6$凖 ,|(?Rry%C;譖!I]m棠H]綸u徭nO7l'鐓{swpmkB.緻I蒋I鴉叶oIK^m~G"Z哥箔>>;| pG廬v0!9{}1z骼w'%h診7n椅x榔謝n=y滌tgN3M;鵯x_9$>>>^Iq{g睇M!2:<磑0P'G 想jp{1v烟ify? 径潔"[.)5~xMusP侖I]霾=奢苜[>V膸 ')7CeMd 裘━|H9聯llAm&─&IfHN(Z慾!nE=1鵁哥W/鮓~2qﾎ }(潛輒鳩~g9珎M?o頞 44d^43 58>r,働_%yv邪2Ny濂U=ｻs頬1_槭q|$f3$aQ汝h ])siYt7OvQ猟yI/D5 |L 碼Ip3*%z%J)_$:Wm 3輯瀞が e jBN城倏:a巖DB7%:h従暎#-V1\(&,R8 擣Nw志徠e=fe%o 1eVg 曠翰9yX/}J 裹7]e#RAKL:KsjO E/2u1禊"%毘D l0zjs@G１B(H睨<=m,ugeAWFiC艪lP*男辭IE{wRf\ e旌S}jl@ 竭眺泣 oR蒙GGiU@亂珞dIY& K怠xSnx9佗fr(\ENJu遨{DVK揃kz?寥q#w└(N,V緋こ"XU"苞+\A0!y#"kHGEA]9XmV khc労d,2if:,9:蜊X\誂廖]cZi`5Wi旌Cn慟%<C[:8&] c.LC^K匚y?&d^:4%籥~8v部%廖^K^\=iд楫ux)s5q諄dKX(諺悃 }?跛e兩H.+A廓覓5Wi7:Q;F捫a:P兜ﾖ!-寡匳yxb,{{Z哽逆OWwd{苧g=~鹽Dl-*杆_[g泓r_g_#&僻>RoF稙縒緲{5^^裾8 嘶蘓|4v剖讐8E\2E22HsuL_k&8FP]畆L与B[]pg觝 SDLg?\6]夂g3xo岑u~甅#HA$A'Jo*1:K21;j奮 …a澡飽o+C@|#"R_ nF#Q[鷆Z3IYl秋OnG黷BwmRIl$F:O;S 壞&u#Yg Z裘痴1p dW4:;6.憖A!仟e衝HfnRmLhK負4誼Xm¬}>HO)UY蕣x`,a &科E$[(Rz? !}寂< 7<劇3F!VD9Qt'N-柘黜IT-*"?9c乘e&E[F$詒=拗I嶺Э壮酣宜h%刈 Vt7oY:{#g;#ntnR懐z!UI｀(N$粐淀ц 2) Q譛j?遒鰌"B)aJ0{<%p^0]S1, 3F淋o4rrl]E)H[4r*Ad0 0Q]P畋=iP>23YR#渓f5;gT / ?2$′J遜~[bM_鈍囎R?=><<[nvI/aL榔gC飢 z$S,$qu?f雨QYuJq楝[舵_0q_[^a.aD5'K/搆]Q}痼GV{黍w=狆0F < C0cL9肆R4b^e e豕┼=[=0賦L竄)D0w%_j@羔C 匙IQ%臈 鵠b襲%S^R.★[鯰,啓癖LjkeA[￣{q>4ISEK5=U'!V!9#EAwMj綺 .5%s諳娯VoQJ`:F輿\どl)13Ea^jWg}N^=D=P2o咫z(y]=GiMK吉_6g 綣_r1堂 {Z#I,Ypf3蘿AVlq繻Q^=)ｌs=9彎:AmU)駕S~Wダz vＸ庚.Z,張&2襯KMq.\j(-%m'C rMeGT藉iRt0h柔(/５RM8酬8B]Z!ft泅tH/o２-q?aR x藝_拆g}c75xeG05V'唖J昴us(Q鉤5@/RpkHmq僮v/S'Bi-6拔\|0 g{kBGNJヤVIbQ T];p['Tt陵崚qY=9S #ﾇ.n篋FM3$Y:x?URC楜wH>nsJ1p.s媾是鶴@Q-a8[#P\cJFn ^伉せZlpy]}J@l}戛芬Z辰kix$;(天QNe$接ShP-PP|`~17背 C@[b嶇^n?奴挺伸%$BRU(Jc磚Q{Tg滲%q$&Yﾖ4 TDq%hUf隊ra判X]!JB`f?#tir2伝sN2.^巡5辯輳+N輯x~ YYは.D漲 *)D湧NAr寔V肺嗚茜y^[=4|~5赴閹防f諳:榲gJ$" aJ<鏃8)Y0 合]L=.n率犢YG^$;YoQQH*紜K3 ^Wc暄i/9d副O,(/速Yt0ZM_:{R淬$C7,5f5豌-A$1-g i桙.:M頼nL;腺Rz?-KZT!Rn八P Cokuy聞=C)M!\rBzM佞憇B均z"'d>p TE4>d8>鱧GEM責[! K岨録;1`溘HszhynO 5制\8N駛,OCQw{w~K W[!P黹{z{[k#携оx骼,fk;{R[o蒻)s(l 綯9籀+!w頽~T1)V pBG:?3|azR}Q封|#X[&RN%qzHB}颶^%&`<宥\G$O3HpI g恵#齎JM豫Q SB肉t0fZ4@Tz9 4白AaT=N貿$暇QV蛩1VgT\場pS`D鞅-瓦u拒U鑁#_V,cVqUF[rTl2蟆協 9+{|Wxrr8g#c襤L}鷹2q5dRZ\)+(x1<鴫&!{l^^WD M)@6 BkiQK鰭C.啐W Ok=Tw g<+屍$'WFsr鵆GIN.E`s]cfpB邪 :絃q\/I策*_IG(xJ$9U巉x儒A辿*):4FQ樢J ~返~r)f0haE%&*廛x(o熠a&J{(迯()e Rdx顕t+)lr1NT@F驕P_eT3m|\YL95{*膕1*2宏B霾>jQ冰Q_渇馮#xQC2Q%nr[>hZe濡Ve邊畿@uPRV-Snd働 p謄慍2a<;E2d/nク~W3:]幀mkLZHV參pOEdokhaAP駛Z+[`q  ;#|%)鷦F9QH3W８WqZkQ.52@1F尉4!Prx]\ZM&*'M#i]Ni:oPl貞 -Xfcヰ粃p3")z洌銀Q+y段h ;ｐo'<5;,e|ぜ暄j枡DJ刪#＼g[O+,kM*Yf縱$夸: n境'gd゛VLH[lx詣_Fm$ssH>陌渡qИe\凱*U ○D{襄t=L獗短闖Gp ;羣BM0k竹cPVIaW]#TH塊Nc,j*RO o]"橋SbsyＨEchwBK i%i|YSH[)樛j%}( 瓠SHkek`H!俊6HR{_9FRH詒 zP鴎s ip1I!m6XA-%iBZ.A.蒲>f &凡&79L+7dq,jI),8宜V^W報缸8;$浦續T_{冢蔬pq齪vq22S/:瓦虎,^Frﾍ8C官a+E!myq>TQJtqOn$JlHjYI酖$?Hn薐-5v `l+q9v&3Bu; o2tVh柁W対Xt辧摂下h映疳擠F7g7丐 ,*V %(E討>e$ 5-u峙:)E)."B漫,Lu mTRWbb/(1vYNK5.u'(uR.MtjU+面｛臍 O猾;6%)嗚^-$]zMk[M6>@B3:(0t笈O撥@依ql`$(QQWcC田黛`"^%父`"5cS;$-JDkqS銖c;#x&邱u @]♯|r,rtr y匈Q<嫌GNk{湎g7t糺tkQLA>"T!(S4逆SE*+W養F鬱NA)%9ZLCEI%AVJ&h1仟q5jH懊.nAMu數NE馗o/q-,[少k7ZhQPm(F,_}3#ﾙ鋪;*IqLIp　垳*ZzZ3gSaOs~WOcQmQ洟0U&}碾 )\5M曙hbFW`RE_\>iMb-E_箜 `np}{y考7$h-汗I]”"bm+23@･L]/j逾OW[:机e =.7e@hEP糯) tr卦糧H瞠D&B%e:Vv9{%<萼U#yFA@C.PCi&pt()0> ho淵7溺y(1 K+k \tMDk追掬碓避T~供yey;.鼇fR@~詢s8g繭$}b+d_}苟椙uFsGY~2 窿罩蓁 =代P幼d%(x痺UPW]yS]u設>WP$Y /.6R+<,Q)}lN浄Wк5{靫KE"cZzn\r徃K2)hVn@砧狢ZVNド蠢EO氤騒艙./MqV摎rw.q■.;A;薈f抒8Q剛d碑R洲黝_)R`輌,^9z/~咸Ys0(lL X-##QhEFET鉾3mG'z:L盟2働i[r剥[Fr-|婉粮tk gzUUp楕-lu希W6g駝7-÷q浙yZe=i呻C=^q糞吼zZtP$k逼rzSC[`5k#I/癘!eG4J6折透]JC/ﾃ省N)AP$K@J-`kR$t豈"`頓B(堋 .}剃d soHczi<(x qY+eX[2韛衫6gT?S獺>0ダ辱t盛MOG l#ρf\WVsuAw覬X;廐t櫁wcP9G7[蕋箜目+面]z+AQ那tZ偃*7f,鑼+窶l~J"黷<ID%$7)vo杉5lL(^臆KZ+Ts|7P桙P?R$C#m壇U3x菱M権Rd[5 o慵GI_!拱崋\D<.搆遵|略+P 麟J 咬 哺Rg:8y"6 i碧,R" d-芦餓腰'/""芻@x8%@M0r7S>})^"qU馮] T H:cH几\&ym95N鋭5y]褥:{1z i%戔=N儷X@隍蝕hОgj#%Tz∃9切a*Ri榱A! r /隠Uz9z%kM4^-4zSB瀟x{bHb幽QZJA59&磊<`ヤl埜0+#n IRDM%2Y*lK葎 :cL{%砎Z E輻[篇^y Xu+:昇rp #-[kEDqF\|葦0r{9無2&GG斬r9Lzレ罐oq+A D&l*>#%"r巵(He%a&`Bg4g孅fUO特塒沃g- !F1 nﾎ GJb[弋lN浮*ySS`督hv%/T`%- S uL棹h's':}mu])[燔d\$!"@q.:y]蕭WP+';Q,KXw洽U溥 x&BXa GnbaiIUZA)n=GKl?:s C(椥単!cl6}ZB]摯NkwFoRKU澑c…徴\c-,齡SZy'ヘkN^溘 {zPxRA稠'OJV閧eY]班lkS.}謡} 5 pBI'c>J;3{ juA閘A垉F項=Tマ#スfc8逆#η9AW@yu/&RQyf`7]8nP9F0pA[tG(^B~昃瘧鰰pWR_C"H[{&讌m]GCJ&孃| i>_e*]苞!y(矚HFV{jS巣0弘q 4届=<"S[ix漱$67J_a#是RdsFY#+!d^=k病DE/^=ArW$(儖RdSXR|q6@R列C\Qk1襌UM B秤I餤F/鏡pj N>q3FЖdDj(%}nk45Q{H;3*節T擦b蘚(5Q4:劾q＿1側8nJ{y8# 6Sa高4{禪鞘`6弐{錙ィ^Y鰮6. R`Xo杆9w=毀k)_X鰮z$Y紿x澡R;HRe駐mE樫G俵bu)r鳳wbCdDey1呑i?e彎>46/&"j&,w@"潟}^抵霄費+B顰N l┼(vR)}>WI]磐d枳\]6hm0#m?VJ[`5x`P%_X6cY$I GIl輪ddJ5^L9g8椢c呷"Or:Vr+=渊}τwН 鞜yZ 燭J?侘Э浸楳o穗~GW諱s割拳 8wЁ`灑v X胎蒼酪埴?+桎}1/~躾^PR[:=<GQ譛9Z[對A<殖V燉w7蓖K {<_?>S6謇tL>_ $&=潦渺]hrFo鍋[ S67:^o> t稈鹵嫦1-.担9 !怡P)艘./t|効0鴣鍠$!^u:TO雀1r{zs鴒蘆黥{?$l!┣|'r5迯笙鵁+輕蓙x~~萬o=埴箔窩CE/S%Oн}8 迴}|E0+及Z蕭ZV-用hPo#0z匙黝s鉦( 爭?燗xL{ }:s气DF/扶ｐ 麟g0B>}n md%娶YIp !!~1&%]"^穏TV9T2箙Hё狽'!Tsf5` KIR$~M$nAe. "j?bL:0b 5FD渠P~eR&肇5%&9{}\.?V无辟3xl咯C^c|浜a椛 {w姪1i9d+獸%族^R醉>2寓}韋x;XJ_'v陜c}雀|#[5"Ap╋5^" hEIQs甸/丹[製y= ix/V毓゛%A*vKIrG'P#E'0"苒-z'Q^F@R rl$)s|TM鸞x+D7}W漑e~Yx,3U]p抓R[>K"5hqaK4雑rcK田汢z|渙y畤冨(穹/xK?u.C逮-)e ガqa補a覆$艀桃9-Hnc=>JNE+BKFB0VL倪$$IY.V$h-7V,5!$b^#PJ`r11i=E>r稼rnamM {%i鵁埖xJ<%濯硼1糅hE+eqRR " - 吊点g 襪Q|C= Q {胙蓚[MEI|r RAxeB5{$Ae淀dV等弍l舩6nA跿秕)計^)J4Vl茶x罧r砂落$X0 "y l N)ビkH2X･NKhH:恁t)>&8栽菖Rssm ZYg(J>4 I8七jx[ w@khKq QhQ arU_x/ab]\}滓= O#Dn藏%)澁_趨宮}:t\'嗟'阪9c薐^F廻罸^?h悉浸8WC\7r[莇3橘)D(zSr!Ft>叢'|=iア0勍+2v_M z賠Hけ啖飲UJ@/.*@VA",f.uQm檄Mx[w[KPb|3JB;lZ6cJ)56eh9瞶Dl"澂`X鋒tuo~裾[:?~silQ菅G冂_t``\4n2N｀ｨ-5 V{i衂U=}7UI_于/殉奠S赧o_鰉昼 gr!+~}　P沈OQJY}x~g@di店qfy6 |}(叉%0%H鶫u/;\vI pAO;(饑17q憾3:#.Nf8エg$ZLAuY~='o\EM3^P F>&S=W:=Ty再gXoCzIWJ =S藩-Lk tK;R^幾x畋[Ou*EP)t2['&菖8瓶1D滬B勠~8 {;N[ YZ`筍1劇%^IoELB!$}-Y)uBhcC G=2nkd疋莉X懦4!S畭qTa0gdo擒淤sI]>8ル旬(UAa_C殍"vvS†rк氾童JL、p浤bc$sTy芟裕[)製.,w Y協Km^=WK丶暘-8渺禿&Rb暮A9'(,pW8D"Wp 痃V帳z.uF1qs*:Q.s刎)[9[>.a[B-o-筌-危Qa+9#v{%V勹原漏*2Wo*E鑾侑wq@葺:9G凉 }pm%9圏aW!R碇~XI~?浬XI*あ;罰(１/C+hfg5e巴肉#L`U0‐u-(uzdq拑qi YRS?*s)Qa鳰;I&85R稼/Qo購GX{!8Ji0VT┝Io9h8絹^z(%Z $M5"Pb4ZWnaj!C_0捉:D*.BR HJ"BB艀x楳y弥稼t|Iw7v粁扛T2B)X徼`醉)@囓Y朏et跚K淨9ZGW.<p9`,擠f6d~録7杉o_ux@G|苺D|n @.dN0&g{Z癈qWsr6z83Cc[gP瑄сi^b甞de9prt5У婢< N$vxXShk苹oC[ aL<壁バI ９異P"@Q8z陦m菓P8楙.:Rx懍x襯p7ｷ咫Tri~aX饉j×磧h@2ヰj%<[pYb葺王PIKG{hK26J)a B!)k~Q=]C.EョPJ曲eB>抔;蚌E8vi5DR[v1め泅躓y痊>$ {e鸛aF\~|~錮襃||髴|X9耐7#ZR7: T術別HP+s瘢)|+Qfq.dqJAf?h1')iTK懦^o_Zrm 柮澎5K眈|e晰No犒!o>膺|P黎薫月侯op07uS), 9wg I%.v橙~ `n踟y|Vl4肚$? 'lOVJQK\I8紊G'8)）(j^9f( r&C%qoVJ:USHJplJkX痺I`h(Q! $MK[BBV称#HK/"Z票洛璢?u"Zど鑒纏|"k%F拔JZP|(8Z挟ゅWBb}弋{3"9Vﾕ珪1@TH1Q|qy 懾GI\q"b坤) Yt .'Z"散*"F蔓\$pD>d:A[[Fyf微*Xd.囎F[]0c彡}nWkF悳$k葺H'弃@儲jYOH?輯11)叡}Q 5ra殍孥0C~索G0閤!g SR\.Me]cLl青9'yw1V=/逵PK傘NゾS l<屠"9n渥|[ MeY$Ej%P4U@G\{ 'V fi=8簓)7)>*R長D$$#磴хyo汢02u鐇R 圀ac}f~T>JXerV罠blq&箚n贇_C"默(LHIRF(tur *p4" )9守lQpL=t{Y2gca1w^f.N12如iKt堙釜b9]!d煤"vCU-Qb%Y0%^Ln FYsSkcdco@促#ザ憫Q5o -Q嶋#z2* {}i"(逸笘"b1歩9f驕菖ZcFPJ9#sh-利Zy^m懇%lJB^'W[9x ZdjHV(6凅 飢 ,銷dz芝n!p鮟fJ駟$iXE`,n=槓v汎J*^iG6',.>醜!%iv q`J.~?}9#M)],蘂D_}.E桶r)Nyt_d>=瘻Yq5q*疫0Z釈 >=眤@蛋I:s}@8A8LjWUE淪UP0<#Od攜圜Y,QfH<~漆k<V9w(7 ^(yAbX@講C>86zRyGmRb"s醂U-R堙^a|M1n; g蹂{^{Q#;%<*HC-  M 虫謳S+蚰I-多$竜k糊%oQiIi^&9Z=翆 ..yz=:kNI撹@zh!fL\z=r[r仂i5Zj橙3bZ'花K舫]b9/陽"G#Mffx3套72据枚宸冲?_7v娵襃鏤%挙tz?- 吝Kｮ4OJf|J毿pK ~! cN"gX圻9.E寔"qIY0)?Rd>z>k2.骨m泝)2G'cMf+d鎔ZX[:g6I:鍖4VJo^眥\siJ旧i>V JrIG輦《& 裕P歃C覺y{襦T揩8"嚬.巣CXv專:oglURd賛41K:y=v2ム:S{!8j花 ut,HC]jo*a<Z鐙k$yVQT=VUE寫x*o.R譬Z\Tl" $8俺(DQ脹U8f k`,\ "Mv](wr秕斛#:PO__,w_頒於A植s/闔-ON円~/{}x|f_\_?=壥A-o?k$en+$\J TM8bWJ決2{1FS* 覚 H┴'R)q'U[+邊(u{(掌鍵A擇*W転IT)H剤JjヘS)邸糅筌 ∽c]Z)$ _$kQ_漬JZ* 桍謦Kj0hF櫃4,ZEr'y@Po_cT$[N鐡洩'8@毯"l!@U思$CA>;3zR0}MQX Y0%rRP[苗&0~a<+P{xn/“a)?>=鎧縟 ~cQAa.-[$L照 ~swh-(ARdcj^(jN錆i翼I1q9%#-pE旁4C' や懌_1ku|c鋲w"# iボ壟Jx'+Fu-}grqQ仗"fa[FX[=5:幢 LZj謔; kZ9i o I\)K`Bdgt`e.dLqつ[uH坊9ｌ<{LBFB)r en J=F(/Pp#/=a f9J$慧e(TWP6kug'☆~#3ZLUNAQL9%j8lN_杉=e菅歎禿}苞砠5,C胄<|たy Q菴JoIRmR!Nz；搴`)/(!g'eEE|x齊 gY議,嚔?EVyε5`pJ % >n%Rzｗ\:r絆ATa;С! @i+e-{υk(%Л4罎徼$0j宍$8 $vFd[U"鰒組EEKzm縢W"査髞oDxR?8r炊釼2愁KkB 森褪昭0壱L%B/%'vR1} 2gtg4跪0 v5TInわ &蝗'わ:м紀k!t翻<--ks齊磨.lM{8YIg鷓頤P|rJ恍ATzrWFKr> 8粁UTL8J糎還0瞶;'? N}撥{S r惠uQ|z需顫緞\$`mMo3QZvI"{讌x \=^:tK{|}w|~)x汗CD汪R-v堕臨艱恰:#/F3[b"縱T%6湮d e稀v1子l5"=粟0(MgDTd乗- 6%繿 Fs|r AA<6 嗤wwo墻 KKb1メ&$`aBMhe阮`sF9+u]~M6c`\% }]_Ba1剩素2BY5;O)|;`/H*b匚6TKW*協 DNFB~赳f_qCH歯PW_Crs"W2# -1|nEyJB己X5DP{(勺繧裼q7※B1j]vf監]Lk=Faz坦H!x《})#OK蛹+u&ch蕎暇吮\""#1(縵9J|1z拇H顕Xf紵靠s`"DL脇} H8 b９+X├梏_}綮薩腱 z顰K\^П\P_{z$N逅D7F7L>:勒F?TZ>y{甬N;>Q[1zuBM38摩y8)(|H#Q|檎X;uR/3zG[ml$GI)O5俗_?p5 ?~7WFcVJ+pO (V0C;2[rF9PpS J瓶攜XyrSCr5Q=8O{稿Vd[oEVJ}Uhklum沸慷UoE崘hne讓k:mE0Qc:y鴕.#%%lげ%hg拗筵j#WJf(u WG攴xfqG裙Uwh}>t=x(I6K8s餾d#l}T糟rzPWg濂fo刄+棉!|/|ﾎT>Zx豬|CGdH'iE?咤uK>=9Y@穐+Bd({#ne2 _峙j 雙bYG4H隲S=F9Tl&ヵ('yA&T/辮販(6DPLar5@曼dQb%疝Rb R-冨/RWW治UJIxGiWeE%!= %MRngn¨cgぅlF C,Q挾懽 o+^Vq_RGj瀕&PIr少\bQD[UOU蠡JO皆ツ7羲2)S8<CFhhFeR <ﾜr1.$0P CWJ{3察祚)斈雌[桎%~C+W苟!M.a5`粤$ ≦]I31gkJ!mb$$Pi0盪Д":sVD1rep'豫]q_Ng/J挧_戯#wPfojVJKukA:V TY @NqJ3JO(#VF2^_偲nj1 h拔臙U_)r. (鏈VuA納&4F9iV雨__]YZ#PO~_征森/a$o I典=N+y#m9J揮`雁R:.SheTS納X)5u)-#p2橡祀M6T宅}*qbp蔆∞/on#w下Ry y$%\Ρ\vh寢K(A='ZhJ|"寢v%麒趁(齟雨9|%sRA (&+J 校N1C}m炎LXB w9Y rp宙I!塚w 790 t^}Zu }ZA tVy #ぞV譏蕎旌U閘1褒.SOXB?^Z ciV> f'3kt羞ZV鋭|h x茸,eP疆6c*l^F 宊Z*EL$^d@)`DA狃'wgegZ)*a,i@K4c6葭bn瓩8vtH/(qiHa憶禽袞D琺\v】9,H4痍~U\&E"`c(1AdKK=c鑾z撕咀)xlm>0fF2R畷8陛\NVzyr 2%_豪Kq0):[(K22 '&B7k4儒B歿e巒meHP;ZNZ=呻$C6>諜U%H c費 <$滝hb)めIIмa!>!0"#FM@MA7G2,LQW{}e懃oZ I A _崙*腓%k 仄F2JQ9 旋磋?>苔 ^ h=LM+U.}v#L#-+>翕OALV6F皸簪 _||~x|w$Ms廢 H戸鞏気莽韻哈k}E[>~;xZc崛WEG殯e篁U)l22c酸jU鰥'[H B藏登D勵歉(o*Y腓ぺf)3@r"0,cТ GB0oJYK畩]8-;#P%fG3rUv"D菟l[対Xq"DD+%胖a $蒿m擠Pv(箘苛8\ 貫@V胛dD3Wx% 2*hFDcTXF*3f4H.Ο U胛1& f>`J=x>経5\z冑*乢DYYG4>]~[y<朏&^杲/ 耿N貢HtF+査涙6N宇A恩g'.hI筍,haD搪寺k4 雀KG叢B鑪w'猶fP廊DyIY)J$[E *@;備oIﾃ^@ {貮f奴T俊E+Aj)?h)9qj _~"#,G[=鍠;!.0 92 !怯,阻H+#nDt`R耆僻斜J$|>xe粫B髏^F $W uK=~()~數[a/x"ooQ<遨g古}zm#忠) 洵)}OZ)yU^{茖0P0e)^_k5b彬t▼鳧 2`莉B 蛋bs^Sj>i糯夷EHr銀;p e禪?2(GR2.畆YI.2z IH,LYldA<}噫zs銓Q9 鴈_6K男WQ蹈w O;8B?ktM[xb!w_B2n||繋R52tvFLP[I){府 旬[YN? gR6gg蚯w讀1KoA9y]CO輓(}!X!cl+ud319q$`8r^8ﾉ>DU惟0 'qv"&ウqpQRz*鰛&2z==tun* 縢 >5THmUV育Rn峙橙d岨%畆慴6Q=8g=q5;B{Zy 輾/j屆3}L*й捌w五|s~<_5N\7韵`S/鍛Yh8(F星~'聢R jg^O(oh&唐dD^ｹ 1Myl; H耆jYky煤A&8 |KIAFC殺Sk_2艙]Bc>j泪u%7%6wo1o/NzL涅薦櫓 -#wH針#9)d bc2h3Vqe按e鵆'-c/G = 6 Jj岡 ?|%HN榑Y2ヮAu飯()听=糶)UV喝4 g唸U,V\b]\B]!5NV,/腰h!e暎g絎fq ^3xk燎nUf觧御weZ/~3"8N+q敕a昊HC[х}xOQr霊^g`o鯨pm,&]齔潭uu錵 ERQR瞑M渭.摯,6{壙![盟m庫$_<杁 JOD ベ! 2[眩KE ,Ae<紅迥mp'G"1糴BB拷RC C分Yf8j槿d\^V#N虱: L6GPJ^ y滓V)u藪u\j2+j 撤%/k墟|｛Yd>pK>6X1y/NX~瘡- Xg8ft(!閣$v遉y%e1mo3@機0Nh\oVOv惟mSoX9邯98^2onS9V\E0拗T@炭嬉=A蹇"酲WD$ 楜Ud!8)Q^A庚%g秣E芥(褻IP"%~"淡堤-#2{籘A淑UVr 凵爨R竢復hk鏤 al祀蜉鯑磽蚪<,zt達侃Y 扼7$'笏E`/T*lMcwcZS導e蔚秣~縮{插儻$沖49[f>0巉;f'3h問j'3心dGu敝忸4~r6 ぼCnWy竭>5gP3',r┘-6V]vC赴RO5my憲 kAXKA狃z ^gI(K狃:/F`I譜k='x2' \憩d[5y愿z6qRXg背L=,43Ykhb Mc]\B嚏^zg媾/u盈"廰;f*廛j丐赭9梁.5Az^2 aK婬籵uKc")A痿]|@ fEdc&鎖^1dU# <)[)op \]PDI ^'[ZUPveD_k {P4 <F@k"7%~hupドB%^C)2oP笄C !os Q VrSL軾共丐 耘s[]Tf~|kwIsY) lN歎$x2;攘fliQo姥I愃&Wt$qoMI鯢b]8LR=y娘ij>‥Klhk礫篏Q :P(Lk1au {QV,il|5 |涓,%Aご+E@h*婉5甘3$^箴u*gR=7訖].k 阜jp4 $根; /旱I;GR oivQ皇.Jp虧GFBtF1-縢bＩb\Yr.nL^)*G_nk0r_s~fd頏殪仆%K&S,@=Jge>S+|;g zOd-+pGH箇)b研@ :W11迯()'///wi匪荳x)@VJ = v0廊処畍(lE'鵲{臻CqItufA-|N莱恂驫7wp朴bo薬@&v- 蹤葆hRuBC梢{\甫LCv払8Ｇq^.eN@架)Qd~齲Qt亰H僵'憑TC,z 摂d于2b啣YRC/蜆$=fN餘E_)苳囮y @!_吼屯pg翌怠C-2 W0Jd t0e&雪0_*m后9\靤CwPb\譲dE#忍he,B)h袢dJ隆Ji癜R市\鯑P3>~h}kp翩3a-諢グD6g%.%9.QovT%A:ｄ\QTr9r)]閑%.5$ * }IAX2[q壞B=蝗J+}B=USM8R>QXD-*a#$3穫+uI}; ?9M{購cHv0箜畠bvZ K舳勺呎Ac_X'!廡'S^(Q$失8y竦$y'Z6J}蠏re%算3b槝]*q$fKcK;0R3"C9HF*^<55H(V葭%v[O:Iiqjｵ-V%ダLB.uｱyTX.悴|`G- BnATY掲g&.zMB5oWID楢潜4G!d [)]EJ@i_ D嗽"D{Q]?8I从|v$sYPNB(qB5伺j\鑓,Nt.5{fZ7c詁zn .破》餤嶢繆+甌"J立\k'恒[R^9F淒0;|jO8鈑 瀟UsQS莫.a0:*P#. 聶Yj尸c<.冀R蓑|0GHsqm5稽;沂剴m*!x#4F;XY攜訴n[FU輯) |5蓼~z月!徳 T* )啣巳Z7\u(亮} *S遥dg慂($`KP接I-眛]b酪VOYQ鵲4廛:錵) ]?~i 41pq&癶f4$X葡.>涎5p髑A+中RyΔ@:,踐4Ny2nyJ8允s e0lz|3@.Xid@SsFu\.}繖\ VJ廉tXur5XjCQJBla)CW僑y(2'b18 $ ┓6^x)l+葬P>,1>I-8qNYp"^眸抑(C]0\BEdUkCLNJrv@IR忙R 疏Fo](鰭5川塋xVjctH%T_,Az姫^\T{癘n錚pswFNz${俺pC{ABTqc"^牧R2*$ 6o^\3[>:w>HJ臂im\&KvkkY.Jj_\f 擡Q+lK/a'Z獅d4LS5\sveY[/減嵜k仂e7洩Hu5hU\<逕轅7新拱+ ~:EFB6綾{=靂\ >&k3帶T;.h・`儲dREAV3燌Ol禹= hW忙kzCz,Dた多絃~d┃嚆伺黼'O愉嚔#;陶i)3R4奇鷄e巛♭w痣OW?/.4,尿&C`菓G). 匯Z}藹LV溘P""Q駸屍^zz9|譜李!P嚮J 菰2eeNc核uL 闔蕨pzs韵59"廣誡黎w^笵7vyt[:$VSlR%驪9K*}哲Lj$_ $!6)c!},士d^&4Pc鑓9[b%98-T_OC嘯|otQ0i34YBiW(S}IVｕ樶9l 鞨\bOnzg(#彿CG`&朸p/ B怒6|7хr鈿WJQ麓h_K!v87c帽ﾛ蔵薛`4蔵P{F髭ScT"])Qsl\ゼ-攻s撫u-{}KL楜&'bF+EN W可]i=u',1 ,1#繽=H)/s&X|,.`Pz;Ni濬рWa0d?Fbr&H怎\+Vh椁S醐fIe;t>$,籘R]w羌-ZP/s默篝ahpY'9p@zw8縡1'K CS‘芭$?@蟹址H%閃XPXK[穏4y2[&"9pT.cう(MDmHVr餾pJ99N綫qFYh e5!d孵ATlUサ!幹VA.5膵妾{a0 靆紗 v(X/K>R鉦5P98'璋sp鶚R淨d7?_>\&吋刳rz,Rk-%E[=4:?Fnb{|te 涓>1$G逋Ya蝗XNxp}FﾎT`%d鰺髢Nk9陌鵈I`髱2*qg黼=/EhPo8枚/q:思wl9^#04xhoOd}jSEb6XP黏\S拌H材彖肢偏c甃37"濃v更t集cвn4H5{4 排%廳d0s|3=rCXF頏9l:~O賺-sQIfNzMo嗽l`ーo;嗷WF隲wa滌X嗤 Ur~轡'3 x(殯PP`UblbeD JB#o=r1;皇fv9杭|G;sl韮M7>: Y跂 de"8!+aCz7h,PVFpkB逾\1衽,uU]/qu*W8Q超%醜i=XzUG\xaP8個WM >}C^5*qaM8支8y;jq2=t}h~},{9 'ZUUkXRE譎髓vmGD*xG_R搦8G3(5#K^85N芹' y8 Rx/S?[沱杯E閥G0&Hy$醒Oy$@Y塲J2$PFｱPy:+夭5kzkR鱸賊f暉W攫( 9淅fy-t.#]餬de [34L清;>>V:疳o(%6寡=ykV>D\冽GI )9=(A&^|XI?'w9ecv{/  ?它c 鬧&x1r春u EL("r!Xh=袙pguV!V亀U!aJo)0仆m\蟆bUjV.a-5)縄m掠qu[ MB=9&偉亮泛pG . Wu我表t3:\ a) -y)9旌9IWA(IzOa防Bwz]J 圍\竦^+6;\"#8w咢Y; CJ) ESxE);>裴.D砦CBc\9h穴D亞三>倣g\|7F,H. EhU凉 葛'聳%J(h 4JQ黷df:J+b7h砒D>^浙@;"A8jMRbfoHKv_:kg{轎_}Wx+[莪声芬X簟忖9%(QGジ\j"/胆聲nd((& 聾j }ENg仆E3jkPYVoPXARo&l儔5q5u]鉦vVhEhBES侃棄Mng3;mv脂3i~?}S()螻祀e\/{k#DqH m巽pc挑%y)mad{6FBhu1Fy $UnB>菓ｄvX1ZYfQ"<^>4遮I5tDz:Ma/u淨)KIN舖R"K](iy騫 ,怩:\m牌}ny&0i話K(aG6RD~=柎C~Ja(}>~`l鷹:r*fm=u＜o*-tC~rk%[{諳Dh^\!m r]]q+r)ХBUxwAl&4-Q(o\jfdwZ; eE)d.孵*I>{F敏CI"^&S'T'QI深1Zil砥S陰啼h$瑚W鍮:eo拷敦Ы3#Gi)Gb_%cN/W"袷E$痔[社K抛7Fgq=hN靡AeB迄gi-1徠尾b1&Za(a粕g祺H~e砒.vｑ{$^靴噸o纏Yi+ H妥vNg_+%/#Z2岫9}Z. # "ZFR5En★#`Aw(~憇 伏(g'1~c3}G薨UwU1Su忻**jtt3;L~蛸徘Dn>*I 淪%[普d桟LYi2袗J3])"7tRRq塒av)} h循2L0N\&u謌橘D#&:D魎ｼHtpDo3"SA'峺5(:E'"2汀0./rg鯤J; ;o决}myU緒WI"eB茱<冕W;R|%?3qvCK~耨sP\Y ;Nd\ )獪Ps 頌腰B<ii ├+C-%撮c9(%5I9zrhv8uf*[s9/msh溥[hf存\朋で1蓙哩u ヤ?UP(Kf+6@狩:滯\p:@pA.p/藥72EY移hI@OrP)vG 菠Ul萋nv挺a;鱸9 >/&Vね酖eZゥk\)D a+簑a1EPV6$Z;Hhp`i5T/En#n@5nVHCN|P jR%>H│?Hrテ$v_^剛 /{Zw9H┬吸駐 民終U:A!Z筒杷V)StjenvR凍`/_}梁![ w玖q磚`芹"篶單屎輿>2qY吭$A<ジu'IZ6?N(n];|e勲殀|jrFyy_髑&d55Yd nr ..Ww脾WめQ炉$收[墮x~|y*8n{@~K=%:幻A豸"~8}[7{暁W如w褫3#瓏皷蝎藥/B;邸砌HCw|辟顳~g畦w閼栫Vg.L3p梁v+S@f?'<">)08bb.'o釛r$kb^Vj次&9j♀昌xz鶏%"hLF/炮ty鵁c~:f(a/^職毯迚翠C c繖EoC8\6 ""O:鷹P蛾% 閂FJ楓@a$cPx/Nl[w 'YKX3/oi=y R噺 s(灣!O-h伉-拷x$低孰g>A盞o 9šsQ -[0"x %8g\W/\L(講{L6J{Ibl.%,[82I (XK1h5w\$1R; #孳j`伯jui医LH29\銹s+3U,%kOP%Zq(;^*^#KW|*8r}]Wdd=B)室%?|o _zav (葉S\=`Xw{!_Wq^梗tf豹^褥2-F{hOS$PKE";WG#.!Y"/%Q 莉th*\p騅 mHbEpC\z1c[KSKR-=Y%0蕃D褐e梁V8Ľ`D5thAQjCC; 掖]xmi竹k8-F`1)I9"n+Erfe靂@F|P靆Rdq綿-p]\陝[ 碓g|):ggl@v`怠D#mKlP=BwCW瞭9 @K!m|{z6苒d埃$r>t{0鏡(淌rP&G41霾[驚0F茖'+.U2D48X勃&(g閧蹠U=憾r垳r dh琲$Jp!Z<逢&%O帛睦7WwH6写>"=>>|2AX離諸1( nB_x FSJ~s[bMhj敍koL8X_m`俘K~A宑%J爾斐麝|713MGA聲|%++P+Ok耨Ojf:j&5*I :]*BK笛w0撞xX eZaV0I(紲Z2[I`X姜PJ>uKVej橿圷iL+*E§"}G`a鐐|1j[]命"E}99/=2f猝E|Id瞠2X耨 豎亙マjKfKq清rfY\H9qme少c/NΡ甌{oI;3t[ЫL鰥t胴y+Sfh\R +浜X詮FkH@5>w+聡m 1ozDT衒1}ykh7^AO 固ywuVFOq$xz柆6aXf鎬luq.y+pz茱z kKz 索K5zj#u-v0m^e狭d^?zMjSr 8y1. nl挧WJw般賈l\fY~$mt*n7#aJ゛L vwZ@J ィY 癪API牟Qp .SI稿06JkK畏:4vb]+PD冤XF>'E%pt O*c 爛校J獻3蕣k曷pM%Prjkt7.wO鎭nskFi|闥t~~}u{xy|~たz"Ya憚CjW|r礑7D^LNF怒 ，k\)ZQt^=2r捨l隶楴rPB3i銷^Z#lO5Q|KB)百$;>+u[{ ogX(+4瀏56餝H^@/( 蟀raf \ GBw<蟋 ZLB-#.yy齔會e/<U";/}2B}責+9Y崟%[畑r#螟\H1KNJ巧C[zmy:=x隙BX琶 :"j$碍G& 鵡)GM*a\zR2&禊-iy.<DfＸ4吝u7尹e>#aXe[壁Kna0A2 庭,[i]拵-(+Ё湊T#|&1"qXj~*A,Vs噸0л s戊堂, 錨B耜]D#-ec$肯S+g訂椄H貼m皸Ｅ6glUh3褄4GF1!ば"n耒?xq}琳Nｼ+級qZS v?z|b<蟋tQh縋2鴪h%keL p蒜\,K>絅Z=祕*謖j\KZOZ%黠?1 o%y怱z1YJ#!蛯bk秀 l[]Tr銛蕃^ K顱:2e徑]7[mJ賊StLB..釜la d=舁J 毛:琿(顰k xe u/9%弑緝uyG 鬧T#:戻嫁/4QQJQ,v興MЪPp竇僻tA86'G&彰dY T>BvRR8|*p7RfccF[ sDP5`iN@Z\JCqk%0:q皓J g.qdZm>N-}蚪zu痿 D}UDaA fUO!E5H|J7E悍U:)0O瘧鯛袈ToK^/E弘&t 疫Cw=紅2埋ЩS{ QI L ,2-Bz汞vo0 s駕"]ybb%YV-仏C 呵P寔G 泛{-ε嘛罍韵Y\d鎭bkRadぇ47f啖a_Y%F@ZT'ｘ}P)B1tD;kk7c爻5QOｐ嵶5:qy pSf%dD襦5 #9 v[5-RX架率Rd]Rj拿F}昌袮cq0om$~茶x[}#M$,>|UxPJV肅dS$N| k_?J 56rq\謝%[9X)q-# (  TwQ刔tyZ%y賈q\C]@3ua]2KFbCgkaSGDm^F@fT祿.::膤 S y*FXo&l數igQ^ &Q驚epF較バDIr{^8!B暈V悁t8-8蓴fl+]bW衷!Jqe\iv!tm{筈 =ろBz蠣.,CEN:D5wS=cHX"'Dk9Qr萸Y41$iV[2^\膚店\$)膕CjhC 淙%=恩<_OC{zU@&oh?cT4r必栲Iujbc聆E`_YCW{mTAKH,狃YrO螯]$W>mz.u嘔写Oθ: AA`吏Rh u pBK砺$F7c@〔9Jo;U杏Npy)P*HB)W8? F忠茀hvH沚倒黝R橇g闖7藁茆寧{b点|2g_踵h+湯m9魯:v`GD<綵йm ] 0^>Q%) {X )訶%hVubb廂(e- ｈVQ1UrX尢.杲@(]#BC5%痙#QO膕uY!E6`VHe-- )Lb末Bjを*FRs鯒#Iu蕈.垳蛞J>q-ﾍ稗(+iJz#6;rsxA|眛@ _蓙% O[垳f4造V+ Z^ jH1:WG|丗U漁$]庇%cw @~8v筵博0m筌0~錐u<梱饒E'uuq#\契z0dTo肋然諂GOW転>左C7篝3曦WwO&杠xjDf@"h凜3x' 近ma@`N[5 w E)０rSガ.OY戳rBv5| ki>iN 'AOoJ 9狡Hw(支奎]Ge沚嘱+;X謔跖 Z'7#+CKC蝓>(&ZE3a=,@彖_# AMY+$5s ^z豈瞰`<6zb0H=%|*D71 jI3R${紵杷9C陛BOSdu畔:愉P}諤?JfP"FoZpL痩|}r^LPY cY)Y]byC:dD霤Q列e5b0q梅:H9i鍮.~0<gpn埆hS&i檎pSG銷HDzP7;2rptWNp溪Cg褐|菎_ky;g駭蟆岼浸: 糺'G詆泓5zf1M 奔zu驫pqx8 gH%m}p ん殕g譚An鑪@K暃:1|+Gr峠寺忠窩A:鈕私]熱峠皴 并p`Gj@欽B戍]個秩裔xq<幎れAbKL,{GW`j<=5拊2u:iQ蟾W 鈍S逃1<_|6y^BzARbv;#z?Z4FO,4qIIyydU]).~J h菜M茆暫-%兼[ o航=^B秕q夕昊 nQ BF灼}6EV}7鼬覩}%嵎艤~o頗7紡暦u[X 秀[v;#QTD"yM瑁5;&C燐~d@}7 io邊_尽嶺/u柄'Ibwu弦x個%7k>peZ契l8@=mHP醗d序胖+&賁?抂 d@毎(`k得跖}~~wMq4聾 技<*hOQЮ9 乕f~H/gq~囓d+le{T]ju<++R曠$^zJu]慘[OUwX濃>T(rik7麁X6M-臻sC9`T$[* 』 #0hkf&a+)y!痔圓#ZsY)]]zYC}`作,? a)敏W朔=ι病#劇 d}-So7QYqJ甄 de-21y.dL Ziqv86ァL]+Z-Ko+\"/'q0迫J=Rb do宴^o戛7K結m;h(硯p~7-湎$sf司t妙d_e'W_宿tUfg.淑侑Uf~*酎d\*0k滌lLrt~W HG?理 fU7mj8B%僞0本v;988(6O|囗 .犲]定蜴dj毋！kw%艚 RW}oeg>tOp(}UiS棣 ii~\鼈6@W=T'$eJ>J`;y*AH`^肯;^†%F磑惇]\,w87_~uYj箏 粥$Z 播&z_)VF03| CRw6,寨zT-VKBcbwP/鯖s'A;蚊 鄒F|5v狸])t >8`k鋳床rK仍唾'櫂*Z{刔鞨7/色>覦\腔健+-R|燧W祖JX4Gvs_湃鵞f惨-no~維^m ;D}n儔)a^pY%辺驂沾(栞綬禾NfH;B?+@psHKTU胯H]X~n~P講癇=b水&蕕∫2g訐慢饑政:NW3 B 羨ssVc牘B幇M?凹苴饉9/|迩quY藤U>(Yqr&六w些洛拌5a籠#-a+僅n期 偈實萠[綺j(|-Q@D隰!HXfYYGKro(m Ktia狹u胯I6p8T 46X[xwIE R)ﾑe2t +3M)oF $boqu偲-emd裲m=s,WH]>9E3h)Q JX]>LB3 T槞&5F!A.ya  CS@'5\mu+h*}vY.We棠錺$GoX/d<僕rL儒榿bea)eh].#檪s槃dw'碚Npvn弊VjL=Re.廿M菜蝙\r_~$懊ZU嚀N/5v7'*-/w1OWW-肚K0E#裃V) Oj櫻遽ihz鈿hGt驪G:$Hza#E, 8xちbedK x =.2E[枚i導28P>DO%¨]:靨IKYI3[咫 q濆k$[Uo NuqQe?]楼 -Fx,[4F箜6 WY)賊Rb:畠, 杠JO嫺}#$C]r8鬥_\2 !%9Fラh6h,ヒN(P穣.粍N+*瀋zF雜K.抱]邪k=懸z'MY8r%蝶40/$7$BF;o洶+zY攅q父D FSf!h?A{]醇褫:霹+CAw}BoM6{4V{梯z0 un鎬r "D^ioG厨=Ow]ss恍<弋=袴Uc躋~t>r[>e{7<尽u窮淨苗]I+落D57v型><俥u]6轉譚/o觸n遏j悉?區vdH恆5摂)IyjUf;G椈gI\o\<"sT\,F:^泰#拵$"%m6&麪h`=F宥ew聚oAP:訃99@;qZ;+<攷殃Qb坐g4>vぇ凋oｦZ怠4z4nw Dt万L1O;P%HG;課3oY悪mC匂 o-wz85樶ｭ d$ d iМHfCg~鉐螂uy鳬處nw2g.-雲伺齠4怎瘤築圄e鑷亰湫B]菎斜vAowgp3v|B估rwr莱.j72労C] US茉943嫩oWQ樶h壮Y z灘I>({\IF m6忍{T5?I劫j涅橡馥H4&c函km豸U栢?z臼/8樹E5H,綣J++Ir寃ｿuz9哢,邵簷c澂p[k_l%⊆谷?春KU"wD3p+J-娵誌_}7}w篆KeoR塑_纃7o_椙?_晝JWf1髴?x_~驍?|KP({Ox/(J&[y@.aBl\:v<8IpLl#&=5戌U7?i 媚詼7P娵x&gVP涵W濬瞼y齟灑_Ev3?gJ徊襲Mi|柞KsVn3實R+紙71Yx寝鯒^n??鹵O|箪綵G9;:uq3V羸5EE~@鉤 簸!r}:q↓e#/^鹵|7/滯` >M83X 蛯Nt^@C;溲)eyU_4ZlOd淇U55Xn2\≪2ﾈ);篠qX=BU瞑2d8N6+.胆N}UfjosoFpZ纒<p冖XEDZ-S唸7穡7I^\g覩齎M?`n p棆t箍%!鼾[o_@?樹y馘W/偸$MK<残RC4@01qitMZ!"枉Fy(呟kXa_c助W5JP& hwyM/2#w鎔楓*桀>栫N\-llM愧cj砺/|gx=二^綬胚y輻74,朦^蒸F肓o|)$a]?ＣB0tf@g!:32K9 FOJ;5i)qIA猜C 1De@rLy籛W|O縉'娼cA&^|拍親`}0 S>s"wUP$L?陛('\\44ZwJ諢 )Sヾ{VjQgPuXO6u啓%Q侃Ea\{"r&NrsP"'eL功冰k$J>i繧2BI祷VJK 斧:E凪瓰v鮑lGX;B35Zr\Inj6dgJtNL"^N%蔘S'a牢2T^CP鬥YN@{R_o 鮴'X欝5cK?ZNPN.eU?^wh傲}(/N p$_ 訶J{0^ kOJ I%|Q4d_亭 ]∪4-Q狡91 臨靦聢IJ淨AOQWWQe晋装&j9D:-ｗO粒WI&y鏨W Gyrp =K$a8t6蛋Qz軛3+$銓ZA$諸= V%N5`錆鼡cq_|\h ANz >9+*Qa2_*熄U支v鎬550N}2黻!gvYC'w*m旧#牲NCQQ;{2y)"Guo\QYM=s\==t"(抗fr(|*r0楽D=8T僵e,7)薐hg棧%a>R 4c O!堊8I9絎躓DK#IBE稽}im)r.^5:q~f;pc19L)冨qmzTWF8B!VF=JhsL)@t発畳C榑5aD;饑!S^B34X0de2~z喨`韜Uムp*H襲乃T2'"剃,窒颱IXNy寐匚Hjqal毎r;#H;z+嶬8hu; 3q/0,O h綯宦~靄?T0彬z Pc{Rコど;M?~鰡?/】gd$⊃_@PHNMlCN2ki鯤*錮A<5C}$2;m(By悃J4P4o^@ {-E;PB^ /2更PiヮF不eNWV畉f餒Re@Q&漁E積V9t□祕:X1bQ瞭膊2{'殿卩!|6%b<添$圀 6J%W艮jZN:7UPP ~@[課f;NtXD-#褪蕈Kv;セ2n%酩]7nfｎW善4=-9K" V ()%ez睨tMNi WD|O-? RX5r^+{雷濘?o|KfKCs澣5%2l45S}咎聘_Ef ++Yz ;/ 9雀5X輅P VHkrF$-&FBarF =VKD;~聖)o6U5斃屁M<[?屶pA4+FJ:bp.豹S/ F瘤F硲:m$H(犯確薙zb可6@`J/葺G1P'#`nb..Iu#oﾕ \O%0J5H笑ｳ1E7H&R堯-f #)2n込h宕c )=>xHGo>zr'礒ヌ^ @ qB!v?Hn#nPh/齲b+套\c錐2.礒k %x匍>3[怺uk=$Fpdis,S5F沽褊BcZ TAo巖Pceo|_U1GSd&&.E43ГNebH6y#げgg{I /d@epS9|QUnP!♪dF?5A7p+0 OC2Sqz(7黝=祉G*\~@-BR7fYC&#}K(p +s$秣;-湯8E翅(殻lb丱VF9y1斡 VJF@籟υ4;#2佶D枩 ATQ騏贊k螫7 16冤E m罫CUNa&3L.9L(芍FF]^JhI"5GF66U胴DF<F,溷(6>%##i8WT;ｲch08!)1辰isY  4zガ榱3r *iJ!猊g2+#MB飆amJ 2gUSJP'jよg1喃b飾+Ev騁鋒彰U)Y/zs:$]|K`RlI嘲 V&HE& Z錐鍠蕣n,>hEdZQ隶< -y| 6:g7k]%&AZmIm=Ns8M>u僕91}9,jed潼牧$矜\H8ZsIKu鶚写g`i?w『袤9ZS %j`=括NI 騾 Q憩~r#ys u埠) u畢珠Spi#D]3n8m9a0l得(9iKヤ7{臾l常s.未54DICZ魎vm葛1m Chy.9=w$-s C労wNP苳鴈A蛭8uhE4QF7_)醜sR?ｐ ?4/2RfUMR>Mr_殪.jR$牴X `k.\駄~Sg,RE^5冓(I -Kv爰<彝 げj>j艱ZjVk$fP}8IMytQe,ZmM觧k[)S_梃LZG梃\uU貍X6;啝p梃傲守雋V挫\[q.Q&!Sh(El}H7&炙y@^、4報賽D)袖M 拗W艪sr5 l gH#q>aR)peqm w巵r"^ fh6Vy1鐙'Cw^.妾屐jw!Lt Doハ)ipｘy['蕩 Ir{{.eSU)9 oNuQ鴇`TdQ..%燒R|%RX.-e n玄(Qnt,越Yb鵞\bY劃~盂ffV,]+mVF2 OkorSMO{1騰ddo{!渚4AD k$/JMgw拾HL 廠o摩4~y)K^.G畝M%;?甅:芋3芽My=踄H.愾Gtx'扁音lAhUB[d (V9- -V`{>!Y逋7_#ｙ失(^x籟v擯&4 DRKTsJ]ur[逃B+2皋t o~Ζ{~z屆雀1.o殲$:ET ,zＨ毫)EvtR ^&G壽2淵査R5@y7席陟R蛩2遲6,e[tO~MO G>vyUv{櫨aΠ{o%6Y3%~>hS弾2速瘻5X%6.鐶/rk^巫b1lU// 險$h%gYhG*=y.|&⊃YQMJd]oI琉蒿噪c,]"膵"LJ9dQ:)絆l}&Z莢n衍唆充ERlkU>借g?bp蜷Vp 9LA:掾Nwxu0鉋08Y7_d1 kZ呀){彦G7).K橦`u&,zYA!<ヰ\&`(8kUq.牢U*p9w`O@6I|@( HhuhUR&5Z積b偵KF倉64芻胙%e&SV<?鰾tcTMd@ %PU+>4Oa)yM 閣]q {2{p[\,g0hPW郡soPFFHa陞位ο9闕U駑B}@# 各孱P!豐q2g3EY($iP;N氷壷+'5x#7,*!,KB $%bﾝ鮓!785.SGj}G%_齊2M'I蛮F嵳>З2N[o;鵠*G7kC}'N]) y!W捉39け&{ 3vy4刋 aG玻色4Dj&^(k EM)惹FF湲u>T長 %{&ゝ%"f&'sav)Rl2戻q主F榻AB.nPrK櫁劬o.|$4冷m$悗IDM9W乖 X=%,fu迫z:`m`D[H稠捶gP%0第3Somf輝H~.jCq6}!0b 陲jn1孫n48*r榎H<貴l恟^\S?2!W9&9*p革g陝wl!Vw(-*j繊淤W=#d^gKbn9 hM)嬬伍YAZB1 <+s!枯Q齡y&4款O樛PcN`;+紬z_eo謨(YQun塋@洵 Q#D n+/H雹'縹b/"a=KOPZj翠{論GXJ n6}!鬩^D楹;櫨Ch"BC-刪Pl~i<-Mp~1]h=rA迸PG8sqi Z舊薪2e/喋｡u5]Yn QS)ＦEφL狐aE 躔*rQ棣RA%.LJPz閧5}基絅TsK_G)kcS[兇揺dTGXf崖SF韻 %臉%1Qdiri@$=+ |,┐ svR,S`]]NucPw? PZw>B芟V8'vC J稘窩AF*Avrv_9儡 6杜Ytm2rd0kJ`T翌B甓Af_k(.ct衢f,f>,晤褪eJ.F6 ;湮{RdsswsL 6 ＼ZFyRt&嶌d&p半d倩Ld;3J &0 lzX悒JAze6.室席璢椨^^鎗`R/FlｼW漉hMa'a19KX|B s%htI/=.e廃Zo滓bjaaU<1)"De`.A (壱:鞦I柝XJ]柮ギ凶 i !j景*HJ_溯=v^@枹Qa!@JP駲) 稼r@1 tPk"5icPc55W{p}^PYm -c(丹i^\)# V&LvCb跟5)6壅Id咤h>#Q/%sI=x$Z= 醯K浚-]T- ]{趾==;十賞KgzVV>  [U蟹Qm膤 pX():Gp"Rc竝b\ied,"|顛Gw漂8o$D等= KAO=Z1ZM2|蕈dr>f!昨8P(Ic)3肖窗 Z鳥百}*Ｘ蜉o:墫x廨o鬯Q_FB趙=#'R2詁X)9基.y莠%rU.t!%L{P)t!oiZeZg]E6@袗)>1.ヴDQF`IggT#dムE1.*szgT茗 IjHYEkK1F兼5d沢 >8搨#陶P<MzB筌Q+x!+5:qZIOD1yQj"L!!釟-tB油j28MRv N=ks.MBsi71#爍L[H B瘉F3n$`~ G佩@@g痢`m[l禮BKMiE 靨P楞yqﾉ縡m+RMu6Q徊#YSj{M嚴樮kNtQミ闖 _醂*d:(jq'雀雀耆=NoN1K\孵S[!_飾3O<AQ<I6rＶ1Dh4j8]Sk^rdr\psQ週R(HSi*)~8sJ epIJ%#/HaXsFI$= u!Z%y楷/QfB P41▲;mF/騒連\0mJd抵`)'裨-"0 罷88FMnq9p撹3BJ扣从lD-Z07Q12^#)|m鉤%! CxR\#D ^)OJa7#5 GNa噐Fト-{&(dP`4cQ&8 yeTLBV1琴$g$良彼b1kqTZcWxZ卒IL9% 贊竦ユz+S狸巽Au"WK>p瑞Y=_-GX齔i] y矚z鴃Y繚6|(5H_齔★X"致.DIABW):9ｂ(x%qs&cv m6淵~P;v%c&unsm薬鰒楡(X1YcOHF{ei3hxC]韜駄)柿6$蟐/踊7濔}濘ァ%,5-`UQ2:g-edFU@N"qckgMaVhDqF ioヴb6QT)0M維!忸,xy胞kGhQmwqluV 唳L~tL詭,N褞 $s茵I}nu燹L /C8OW`iAIqT罰2-(I|CEP0.忰06HJ!B>靦~#,bLknV 龝wVGwB<Er=%/#"(Co謎鰐ひu黨FW^'潦)覇\&\妝弓rFdRP\}?m0_嘱蠹__~IZzBxO_}聽_|+譲動ZWG9LYA"7i)L|LS5rHa, p榕UKY28 Q4~^j*BjuRQ*釦┏vW濔x黹/D/3RV[?qV( 鑿t)僻"J\偲/VOU zK9-!鑵`5K駭kM表Mr \騅s,y{'播e{YB]9\$)\"'鎰q6"D剛^7p9椥N(wDJ+ as 楜=8p^B]r=}z\v-k稻_綬W?"E炉gS媒9|("慣 W9．.  z埜斉(弼O] 3A欸B,z< 'd#`FyJHM:MEu _8x eA=農h嗟(%4FQA灑尚/_~|B=A?_}_熏m_\垪T訖P_j●Z噬3:u#'=>_恕G灸72 t#bJ=[x]VF YvA:!邦什(sa+z%日脉n峰 Jlc%c)5.?X 磴/CqF9W累C 複匍]H)7-iY6-yvQAen帝1VJ.29瑙MlK)*&液E_.Ix*ΔVMO勳$;va29,*W9ア6[nAdsFO<暉U6淑隗煩, ;gU；]2(@喇鱒>)#}{__?\`葢ю$寮 !EK}6eAtAI'報8$NP%J(6n";_R┳6菰h*roC*xD1分5b噪W蛇)}V侑md遘 QQF9! fG)勺Q45=MK綾f.)kィ 穽|tDiFh褫Of=蔟F-R50)3"NXkLccP慾沸#0 #蚕gx&斐l釛_疽X:aIm`鯰乱e{v 樞N)榾嘉 B枇8%3陂 Df)ZyCgWl YA*渙rHnF俎HB:V2洟 ck5 諒vRb:MlC/|i]PWg|'J#Z&d2' 麿Hu2qM4鞠譌刷9宮,iS棲XCYc雲M( L6FA瘻Qz囎,V :r貎}f)dA樵2J娉{-[hYGW箇I盥牙Luk,茶/m@隊uHC楯*剖DC6#C3諤 n<=t巽d-S<乍喬李:['{FAC]2斐u_O2×m3/=<票還}j5o>9yT旻b/oｧ:宝Fn癧pw9e3=燵l茉蘗杏${h%v&%B$@NA齡o^埴齋M/A<橢FM$Re]+i5iq50lxK8MS|J∂ q!l'yp.zJ_号f=J縵UAI[骼jv8球GD占5tvK||k泉|. y&[Qrw|K誇,\価]b\rt5摺7紲:.wmp>F尊8r^吭Mc 汐NBA4A栄VngMSxb[z *0F鼾蜊稷ChlDvQ8Df眉信_P遶+*q抽bN_をN9M/#B#7急0 14[yK &5誕 GZ }K峡姥x簽Xe麼/kiC]cVo,ε[;fq./S $3早絹?NM].L疹Hy[Q旋f-勾蟷_酉皴茹& m[宅}棒衿&p茵F4Q抵-$no/9_0i巷c>2h1|[Pp首?Dtw7D r篇23b\s音!b将W寉窘@gkY* 炒輟6RBX+y)rky_b 訥au狒G2Ic無SJH罟eRz@pY7rYI♯qfS/o烝~:\(+])O}_自SDI@4^+E鶤W98\@'/;QヰcB"(k練Ip.K"M綉yA沱蝗鑚i$w(斥3^b#}0z"' j0st2衽$溶E B'<| 發C _D謄ie矗d贓eAqq嚮9+T/oOp0fA>LH># }aV5養讀養ゲ霽 蛉28(Z-mWF;]gS鋪[梍-'餠@惷\A/櫟o|#嚏S>2%O鮓\H[ $=9Re,CG81/袒O:;Oa%"PO冷`;z6餾靹4敕Ё{F>;|摶法y^5h衫('/g(.AT須毫R肚[O<07"V3U\豈罷?s7m汎蚰填M`i-v^BＵnUFu^G訃2$ FLPuW.Ed#` $疫嶂號^;Wﾍzl"勇蘂-菻bPcPsB1-:3ン2VLuK@J疥]LS'l承FyD`兎 699湟HH:x]6嚢煦^'Zn/{絲椈殿敬 瘡x(#%Ht*nL筝2]呵YeZP\0bV撼p$9X4I!i<@R'GSFqEOI*I1 9Sdq 8KhgFF娟杢婪nS`h_sqJ^bs^逃.^JK^巖(S6K cHrcC臠\y LN vFAh2PsОz4oJ)C打 `3j{廣e`I\zPSx..!]?6P&ｚ篩TV卯vO8YF棯F^kゥK 毋;宣潤8Ww|;<疽]鵁袋5lTF.; J88Uf(v[憊Ee=i-堅q蠣淤 2:課H`d-7ZAK#WgtFB畸X6q]T>s?匳eN2hQo徳BRiEZf'"+x 1LQX)ごXFn } 6J痳wz+#xc0) J况怡 !*zZ6-槎Z F64帳P 妬甬{u1$ M￥)Vy{(VQS ;膤l9茲c? 膤Ctk u4凹晒B_=m〓,mZD0z裂忽Q;b}do\z8k<5NΞ『7"e2蔽u`Q&臑t^b藺eh,5!_ zbC>k]X)件9SX爺# r$k_yO>=乘DGヤuI遡9r舛 (#2\.欟CI転uBr°<雷@A(0 Oo=4:I嫣IovkL)Is*z9=(~↑M3XII3F9 HRjQZX幵3rY0.sM4;mJy雕*IQ,iM\cM 礙l 剖WaR容g_k*O#^/栖*!Dv."02乖S&N<s%2.\vy]@)>ik(lZ< o3& i6|lv08想!e^.yj8G借奈&籥fj覓yE准~cXY>ziYjsyud贊F^m'l簽峙賊WVjso柏j3Y棠H耨UW惱攫衲$V y亀M%6gW粉yc泗('(x丕uh4Y2r{=eTVV<掴鵞;wQ!4U5zri*25手v.序 c^陬xjK檠`>剔@S嚮z]梃L瘠m葛g>^C諸.fA~S6 蹈U-]i%rD9M.#u&%#8<柯:bqhKk$粛罎G2vDEAEpU#BpAzpo#Bpm<2詆zD莊斐mCEze禊PwEd,w病E阯栗ﾕ孰蒲w熊 R R^Eォ&ь艾跟!m$!X蟶RCL4xm2jJR#L吮$/媒/\旺閥l[葛mEE洲LJ呱啣#軾笏(@hM]AZ]< s湟`+Eei窺;@H虜RЁ濤 1[?g釈$秣Nqq&l_Z瓦\瀬嶌N塹LO眥k0亡 *6L )6N寂zcT2!K( i^C抑-jL^ 賽1省q\賚FG3q料Nl:OdVQ¢澆 警竹殕mWoD k( wW9YDY3XgtF5iE團7eJp縮1AA\j+注(Q8婦>;{(xlUFJ(-rDi9M gQ )mw殀Kz躍c,f>;jb拉疫!0J^仆i ? 它B~3jBR 6FR Z]蠕m賺HD!nC$%LIbV柄稿RI)f繙lJdII~^&%c]O他+Et扈Y<4)judKV.9Y=鰔>ZEx%@'(y真,臧EBYn$h'茱`領(M&T投R<1a+3m嚀TJ60卦 O'K槫5 X3 頂$d6/~r行?y3j3喨f孰?n&U毬x4<5-x62QPV[T捉QjT?J:@)/DxiRysKnzcJ逃_oNAぅ&<% 率O .v.犒\5Y]zi赴(&K Hv擽QR) O%QlT濃懆r藥 fF/&FKs/KA垉r =h娯H*鮨 P携YlюG)6(pVOi+筑蔀${肆exv-9埣3iMs 塲*塲26Qa耙行<漉&!(教А11i)Il6/}箚紲Dns2QuHrJ(S+'T(i ON束'rQSW(OJf遊_O,A鰻溥>'m,shy }3$Nzr竰v tm1*~iF`@:vP頑&!P;團鶻(#f^&`0?)5籔w慌a`{ r拙┥茫Ga"2 驀涎S朋1sv z^ZQ遜A$PI{RPPO=B8U, Ж!a]eB~sNK{lH+vI4葡d0<_痘?醪X粤e[zru)HjpMH,~H`Z尓`$qiuF儚JxW0P\Tu]T伐継轍wQGU4?;lv襁聰-Fz媚宵$估┼/團蟆G9H串fg壞衵X}.P賞棡S &叔TB1]a9q Q粲Ja!8RXY糘Kn\wm鵄萢F巣IfCl.1鼬[l@0H0+Tzx73?XcZ,b$底jURFDi$OtZ?/"Ra mTG+&脈─兔'C u #蒟蹐e潴Z];m憇Nk7桓9Pp粐Zf 79wAx=lhxn5幼dQ忤1鬻baZ;'!_$|zVJ-$*Q4 q Mdv$kB"NR @秋!R}肴8y(.KYMQF説(?R帝hz別V ^P.8PpQr諳$=et^e/7pAAm(5Pf"^n$pR畆hUU軒qV6]N飛m 弋*D 潔z屶縡+F俣.l`核eM9W肖運i5#2Fisj13_U諸 寺bZ$鰺%yu>/話l}ixLTIJ,yV4pa, C2:!評`z熕W匱w5/Q厘iN}KYゆ!FA誓)侫8:扶2<駿L4^寇^ qKLK@Qi7iJ(aEYI珊'e瑛革XQ\]9/H)6g$GXQB 2a黽&R h%凖澑澳陰[dr 妊")ド(ORS-Qd( lyRF}5\HQE鵠E.VcT ij{陰  m陰{L Yd" q謨E hG接y(X$ k1.dIMH)pIJXI*I較D1拘#)YJ7БUy% +O%YY]>D笹um,XSb酘h莉ce垢8nDL頷Z6~+j&v2Шn Sw玩:BRf\ <-hA27 Y-Q禀繍)@6fsaD3VfH填 S.Sj_$E\艫k2圃ト^&括竓p>HEW.寇t(馳彗yG-c}哦_商as6~Ou 怫e/zb悗j^e孥3M u3p6Ju/Ъ孜0qR景iV厭^3bR撤E{M円x濶襟|cLT /CKp※xR[MOm6S];`竚0o:褂2N&\&P$n++jSE 很gB蠏v~+mV壐Lf話l_探6忱{'漸OQ^ 崟籏Ee^そ}b揀KIba^J煙M赱/qG1ylCsvB,I5S/1FN  >!n1v7 芯_@|>筐s<7{Jw輟 ,= Q<咥m4L6K咨 緕KI蓑'壥MCLi![dO+<0LIk楹4umVizOX游[`SX.}9#%)b邑SL,-!MСDbJ)?YI&葎"雀v丞4聰奎mk*_ylnNw#K;%{%矢距M\LP崘nc!絮y!=躁4Peoe眠讓X-/l桝YKy比-f95o Me=覩Dn瀛ゾcW.s[]96[_aa♂X%<棉鴫^ Osn忿nz\ Rmc yS篏〇\鳩c` N,zm zPo'nJ^弧e97名鳰Mkrk;視笶癆9搭>檢L5沁4e*砿竅7wk#/18灣A兜栖ｲ醴\>eG1q謳uJ>4"ud 尿灌濳,GxgDqxT諱(@mP}撹i5mh>鐔V臘oR剴fv3ip佐vM俣@:qELgg屮 |`/uB:y徭\ueL店@N-据$x餽'Gp0Zu鋪]I3eｦ161f.fK ,豎瞠BZuy冢Bw#; 豚6% 悩'Uc$3飢pげ 柎M頭Vﾚw蹝概;MT\)]w$fF*紜-廾h+ 勦6odV5. +a`k+楕U6訊7Ez~a韆`塰L嘔@UBM3lTq並hx]m?.oiNR+]縅w$`nsWe髄娼0E藩u|#治[/=[8閼 gPJdイ1I*¬Tiヮp詆%暈PF剴;zK/]|vYs<:<{L拱h退L2 C_-sd*&MP2跨<'z*>N(3jO2$T3Na)!ZJs牧`NK*)F3duZ!Gwg zUZJ{{ P4&M(`0E90+e8捉QBNa:PQIhJj%杏e19蓆晃窒外A搶P tI4珪!]00e`粲鯵iK+0g~IyJGﾖ, zGｘ]i&]'Q?aprKL斧H9 95 (HixQNv|Ii9G恰ENd&9aι臺Taf+5&>C],s‡d@ [S W>Ksxb,"T;a盥EarT]袢/^yN~何: !ZE爲((b"TpRQUsyJ職4c商Ee%Rt ＠;}2.ym#\p \\m 刪 qCB1x S<^o*Nb仏\F,.:}9Khyqy`zJ0啜G[KHQJ$S''亞嵎懌?";屁N}3Np螻/1czT{ #X'_j ;^ #為l 偐YQ獅7~in"Iv浪儒i;珞>G]dOQ濕; uW宅lZ//鵙k5  S  $v]C砌(鞜卻P臈臟可zx岫-&9%{ `u7B!)4/ﾂ_$=A/R[scXPdP=fB`/規ю圉eXM[h(Er鱶em扱哉^l 怪WZ=gb侞XI4O匁芍Ю 苳12雷{3(/5b?c栞y*淨/掏%P 23P8怖3Hps"&S`+X6#\Fmfs戯沒鷸詬RX#=斃Hj+p(瀉Qx＠"ik8{d^!iypT尠->8]Iz2kE！7>5Pb+6%U借t 雍眷@朕3Mt+黠oZF艨J \B#疏B煦 XAA()J:lo煩I9|QdJU,D&^ *E 0_) qh勦%(伴QD帛(@0%#擴lfFA<~*TJ0拯1*EmFQk+_k刹遽F1H|$(0mR ム?ME!I4沈`^74 j~.屆c4s #H ucED;~" Qh 3O0x/CK畤QyIg{'mq喋5踞R6cQ攷@-7]Z8VCz靄I倅9|dx3 者插r eM柧y蝎淤 Iy:RA>09Y謄)m;qb+!Ｗ7Ji~A}zP烹Vrby-3lyo(YChr2$Ke!3fM恆d!HD紕#伝zrH簑稻u]Q/矣{{-SY廷Z?R偏~QS #:pΓ oU祗J姙\6-ぎ黻31 !璞"Fw`gQ(Q吊%P^Bva| ZDJ:ATog!P劃g婬ЙOunbi iνD$K(%5K<膚Q<脱e,ｗ妍ralxΗ嵳猝x奈{[G岻gH)%dtF :C'L晝mG閘V衞vo%II銭PJ銭uV安RXK菫 \NS,!R4t(X亡{ 閘ZF椶Pw閘J)蝪`L[#kuy9NvoeSSo;eJV 囈~@岡嫖?'mo%rsDlP銷Ui#u1E4tm'肚rSR+ Xfv9肇安scWi6"#l\..沚r溘R _c]<俊(^hs__jE1y6鷄阜Dsc^'淕58/hIB2:p悦挂SKs;JRe惻I3V價tMB' 6 x)^&Z價@q]N(xV]=<\捶OCu 'w57%H |hli #^J |VotdwFVoi m9K@6d姨>Oa%$;M  ?劒+1j0妊s綿e壙4-ps9S猛煎Ka*%OnKbg^榑[$;b#Yq0 U?単w!}jY# 1c禧 K弼I<9 ロ `um4&~)少贊k惱dv}釈`+K.97two 孳k派"Mz6膂馭O+a阡3,妥E8J,gNx!&(p(E'QJ|T孤嵎sB壮 6甅羹Nxd靈d7"W呎^I唐絋湶W吮涵8o繧 o_< oroej^Mx+Ul[G枴当Z &)Q4)?y菽 b⊂必A.ahTI姜icpY]j+. 金槽2ou-a/(JkV拑7N7}t)_nv.7\_-"]營譌w 譛R7 1Y\fGdK"靱ON-'v似旨蝙8W券;E?^UI.uOR悋瘧)]1ns戳{R_懸\或8磧> BzajDpJ0rhVJ4O(Al 輜筱, HY哄&R9QL2CR7 7az1T葦CCE蠱NB&'{hョ7/m9 zta <`S墓R(鳰sd`XX\@u8JL疊寵EqQ-禳Z9鷦i))熟S0&7Hj>Y .x 眺q4neIkk 慫E932驪mP=c弋!縹}致}J"1 畠 OuY?q謂?3)ERU %N$衛!

掫pF>bz┠芬c_澹:m(謹UF(鋺芻51六 尽RY苧賃-m打X費_:(g uL梯x>'2.} 1NOcJわ暫)杵o`9W來B佝駐yT疏 trY9鏘0騎Ｔ漉蜘戞<:擡:洋B]2\z5DVp <KN捏l\H6按 画`j .xG_veG 4."\)x >%蝋 e0\|kbuV"'y@& T0m貭i7yT跪\狩j6#_淘>4墺j(婿[Xb;貔'H6稟O0+H=]￣赭3fねm贔r蝠δ\輟hr{w驫pq0h_NC酎g!F}MボbBcL/c,^Z(熱 'G gj刊抔!*#苧x]0@l&豼torPU糺酎Ċ??97zz$S|s摂)adyU咐+pyVG`幸+ %=DEQ7o _痺k6cyfJOg愎q[GjYq瓢wW祢壙N姆C'VG=M]@?,酷/? G>RX*IW疔疔iyo \_KYUJ!X〈佯BO旒{攤$; @E ^F8靭E$iS=`｀[Y`sU@8D o4 QUzk矯,t率;wIU3OUQ2fR"E重銚$,繆UAL '>H ^KB68P eS博d埆!A台誹~\X儁BFc^Q１4^%.&/j甌N中璽/frFfd驍*副4aIg*^ 卅@#?lp!霹FaF凹灣>Y轅9反#! 0誉82バr:h/Ｗ槌lfNS<% _;閾 '嵋\h.i4跡跪LH\V}mhFq$p)vK_秣淨(=ZU`R歡(停;hR-ai\mQF9ilD]fwh&"t " 僖把L)y s照+m s柏=s.esQaa9$躯z];！f1lf*S+胞W閥&\瞬@YjH3羹.`Q.xR稔50 拾]%!|J42U$+mb&`>@p^瀰崛JBC=lzTNMcYB齷FkV錆@ 苺^製't<^BPz@mp^Qzへ5 }5^p$.7[農(1j糴p浣kumk鉄0Oa俸'o%甥8j邯懾[H:hp$q帥d扇IQ塙A.sW,$!碩R槓(p錢`*H.>%8;Z{>sq=s.oLpnBF畍),K0c滋3i懆|r{o樗I>QP習{Y煌z STE*eby'掠`r ~]Ds)al耐#G,ヶVr2q_!^靼VeL.o c蚌Q7UeH[F>uW畔sB $u3ql;L9H/>L4V 1φMZ廷(uJ3r^縮 ;Ff9よ6捗z=~気Y弘U 伸e峭yS$$CcqH %0B"V;IzD9yN6bC+彈頂朝cZvPJfXr? qI簑fhrT1謡夐Q -r$IKF.^JC A8哘W9蕚K( x23b!ダ( Zc,$XXbE9Q1BjM靠1lkK bJ窓爼鮒\ Q z\\&G@麥. ?l$!XX6AUm{Oe1剤ZTPAR7 vF&1 SWH;栃hXH芽H VIs&d7L}vs耡,Mw狩<{u貂`R)eQ[qDqkA<7淙 UoX鉗儻粱suy圸"#2cB7Msanmr3t~轎d%; 9q托&b冷>%:K{kＺ雌d]4_uR俟(此/%刪m](I汪ナJ ^Ehuaua.qaﾜ[濠紺P]*\02LBV_xa-cki1On g<.-5 欸N9芸<|れ2O畳胙邂?28独隰]cR1OhA8美礇E獺@Ro1PN倣V QDSM)WJz屈|wd01BＲu丿%浙洸C] =兎__jd椄壱j颱jB@煉;3s/tI)彩Q弘 Ag)i-W!糅諚b廢鋒Q\$0t1b8^e4g 爬欟Qi銛寝8錯eVQG+jq啼擣m]0{)&o6 vmy4!d案.8絹 5%>)HuX函鵜Qv@ｈ摘B v2}恤彁^Fqwt!]>jC-|q3#\ Cbf|J^1 掬E 8UMA^J厖KN點I臼＜H)pNqR qw逍 髷Q機&8oh禳Cx醤dA琢kЧ~Jq w~(* 了懺賺{|\e悌1&w8/韆~2k)ym+jPm８Bo.舜J /z JOaJn#]|敖4館?;漆跣胯gvuy絣wd;>V斯Sgzk2 Ht:'J鈷E隻}o:i|耋濘|驟[苺朦_3k藁kCNf廡ydl!誉:螯頒X^et%5-跖D*Yow7{`-訛限)[m/IW~/骰WK[bK`"B>T炎lvDn0#Xw2*,@W/?@Ho8E$艸%\RC$~@陟&((vt#fH7襴s魏伜聆ぷ~z/沒U瀘鎖.立Sy槎2蕕\儺C?晉%jul^失$yXN@P:7影()F)捍2)NA2o B)g8e7店`[<<f匸tu芘x-$ h火(+ 楹" t4套闐X 080Z\TC)qC]Re(PLy9A.郵 Pk 畚nrJV%T勇N蝎&P@PV)i(S8-j`ヰs蛩筰л,H咢:rp|嚆VI@-^'c$EI0%jn$qgd( J筱こQvX∫GUg'mD^"K禅{S9{O,Oz1哘f胎曩`覿闢 nsa _B)y才SU N R/HU<6p+芫怖[! *戎=;g苺Wg悍_夷尓h 配+ 鞦%遒ょIΟ顱)D$8y\2)%k麗Sz&取 )wMj=Y)YtbFNL&,*瀧IMf!栖Sl鹵蕪l6/Q+BvNB2Qr)h裃M)1ud u!Al嫐  03@O],#癩帛Msn#0T洋h~I鱆銛kg彦循aq h隠ｦ猾 街y/"[xRkQeLQYi<R*-A@(5z,゜Q提 O憙がM y峒Gs~似w喘q碁&烟^T輾f,5|Ju{|@{@8j\殤寧OQ/箆Ix~?Ye&;p珱' 1 膿s娼?欝w狭/HZWR醤熏跏1專鞫夙g2鍔>W基臻8SWHr焦{勉wnu3_.,^o@u;;?fg5珍~瓜ぁdgg pw|"#家\on)gu.C:t糸y'p錮#b|O尿.*4waw~{uU[~殳jェN*寵■惺B^顔/v藩?t,:/e+;W[>L\Fxs !燗L賛3施VZ v范l?~OE1箕z炊R$?b?痍膾(KcTJ炬Z&x鬮ru癨Q汁-C :E2i3P_Q3P^q!Y/@IP&LX;abbrQX>薫DOa5e遂 V陏)R?4$M SOJp01fE 9 W V?k;<{%]( #滲h^須鈩o%膿|A}yF鰹n衝瀚鴾k隴 杲Bx #幌o蒙籵e%y"3巷*弍hHV貧J\9停X*F]C暦怖gLG慙B(`Q\R機fB)畔M^<)R$r(.魯2→^\6,z話^;QiX'S]簾6: j竜cV幀~厰膸^Otj6]u済gXOD:鰥揃WK\v2<3z祟⊆,Twd銚]"訶^sT冉; *Pc#ig#?1l愁(k(猩6W繙4hEgfQF AM" p.禄ir "7a@4 +w2%. 8z拆;7y%lAhF龠[FE鎬psfn%m?_'_呼u 瞰{M)$退]久S叺:yV<縷w?\g袞A渮i樢縛MP"!sTcj ^ogm\r)9N兄?濶鼓7N闔l\<&u!^=t^Ｌ兎202C)4藕m卜Ar}$/U5紆zT乃施]煌西晋壑GvGlB`~鳶J糊梼\k療-蒿(Mg,m 蓮'v4f`捶"2xDuN陌X*A/∪/<r[D`eE_涛se1#836;/ﾄ[炒#G^+$$op}` S蟷:S<釵 }0?=<%椏=q^_撮A梺{qffWfo|/w:uF0.wWx9 D_4*剪 nL洳ﾚxQbg;'uG迢/k}(4,H_lZ'k[}懶畫7k入c?守l忠bs>^vxiAｬ'CyP鰛^#)~槭]wキ賽#B勾煖z?Hj汢!D斜4 y~{^/0 /籐?慵褝Yq<;倩9zh[f克x糜V| 椙t淡t憊>uIw?J輾箔au_戎W鍄:K<'|JW {B8m9uI缸6.踵; {w悉;>愃m 3遞u芒h:h{和fn1w▽6滑q*n~vqi_父jM=*,T?s)Yur紵$;拆Grrs2囃JLXq=+Z鏘/6AV.=淮M培@*K\rB##;jIP8%\N:闖>y俥) q3脣vл9[守C>)'GbnNn5s羝[RRli}%?%t`g趣v.-}e:H=悍萸#+檠9Q|梛b襤?=e*t鍍P黥FEh:閃pQ.!!樋`i4gk|#{"疑衡願spu_L|v)%(xk6Q{mS∬f!l盆C?am7OqNuvq. q+D>:鯱'|槙溶$=!露]]邪THA_4CNn緤ZwtHW rs>T6pa9茱a1)7D1&{X#U"u]rx :*E9hk,Q5dxs+J箆s@{k>{緒Y菅赱g:^2P泄藉,]{Z區件  d"瀘-S4Xi來[{就o:魁脩yUX?恫舐霄鋲&,%YO{+q烱?> y<`r!]溪cyk怨CSj)剽?浚77稿櫟~婬恚\Q~"几&銘ソX 魁9$#D;8ZM\奪P願u SA!w$閲逆咐y'~YG1q<'Y濠k:椣/F>w山[ivn wwGQ掃bwT哲It<jmR0CS| ,z 竹e}2"<湶3呎KiDy{O x徽&刮(_隸VHuJE\|],u7孃L#^岱p 9G6T&z~:^t蓴f"_>z∞6 喧K3H&循+9落y@KeP5)>]蠢 E"峭2R\p桐薙sOXBIy僚} n湘~[)|kpd弩目殢拆巖K!閭<: n{Sor裡x+ VjXD&作T*Q#))BYiEhや剿+>"MV虹qm#9vP 創槙獣褪:hc8#訶筈W後!韲P%l,5%蜿紹%J`擂Pl6/rg+諸sRVd鰺EI Q5騰P壌q+Q^T盃U5枚對c,g s]$匁5Ф~R=NcTN拵>iSh_T怏a函鳥3[g#m,o兇哽%Ld^**;蒟u{B=G3ざM￥聨 S*9xb皮YLr+''ю DEJ迸m/U:?.UDz":>5tJx{3kHa.*(_ヂ梱k剪z6@]"$遡筒幀 xLFTn]\.d*j0I鯲\4=$~{~<)X漫B歟pU{_i =!,46J6F^`)汰8唔G參6iGk小Z%L0抔|kb  54,k珥技帙n}n8S(e+ h7AtC∃UAq 8塚e筋tT"E"q}f靖0z閇{]Z0壕"L283Xzb託9R$劬P<YI 鎹5$c0}js魏~Ji1-b4Q$htA, 縷UD 3Q士)H,發Q0e`^&rS0捉T9_0j }s灰e醜搭Mg､i笊7g#g97#ia!+-Y81FA_ebe$fq.eS醐=X}% pgN }Vs!s5w赱c$2稽KPrY $D漓C&Nqpm!ys5臺O"Lwo :'I 6 蓍 cRMwrbA滉d>rD9 7nC i締8cBt綣$z*'2FEaKRcbpK Xb 6Y+y@dp|2哄DШ  aS.蹊 FI-^u8eV嶷Qd-g楡(櫪)罨7 _]"x‘я厨^onm\w奔7U燻圷,)2G%$lv/H_#='2 I`u6 晁Gs踊利$0w: HW`C$HS:ESvFεeXazaE朧o逋禺VOD[LYyx&%BeL敍B D0U^WC=(th頓添VKGd{$W1f帝UM鈑W *P`=H所D唆 HF(限F%HN俄\2 bJwh:.+:8ャ2Uyd舮]r2\ H6> h 5A'3FQLu P#hw/fLa埋kHpk:K `ST1BDE泰E5J g]z^]"`>%澳XXy4FM嘩 o昼0V7Xw] d據NgNoI!} E[遮z.94eqrbp u蜜((P紋Ea k霄)w:[l]"|Bj!!Qm5g%Qm蔽2Cgq$`Tb竓mUwZb鍠76b因,磴 f#RSz77!-I}x0Y*a5I* D湫\Vφ\H蘚K蝮4‥蹊o{x' れ2<$[()I`5F｛RTqQ3J燎dF3Z m己%.鑵竚:毛K%\:DG/4MG9G21@\o9zh&QkgUCOu獪%D{pLF漂"4*(xmRA遠U_&膤D3 ~ 瀋a汨E汗@>UNcO>U2哨2 H凜┓~&}v4({wp_P!u 嬰Y&c\)dS=x)ZFeTﾕFP{Fqe悋Y7\淋|萵<;*nh宏E個z6.InR(ム`2.u'祢[@q[詠;#Kt齠pGd<儁!彝溏Be挌仇{G#MPt@48んz'M&z{By鰰tsGx>Ju;肺w}2%q'\痴pr}cy闖>9Wwi\ %]X*'C┼ #V"o{sk8.Y;mW_埴慾6Wr$g瑾~TFD^)6"&6aM牋央p/(挟alm#<黛zug";H_H4VE蠹e梱汐kr!+Ble GlE阯MG1-*W"J=dA>"l{Y);lKhg$cL1[ 9t(廃eZi豕JR9A曼 A朦D纉[IN%&s齋 @膜b&oV6z#FtFQ先曝贊NJ3CP/幾舳n t\]XX=)'q]uC=roб,5jB>(H1XEPNH"b握R5wQdp誄bz4謙s \bX]腱坩?z桍[麹mp炎Gj籌'Ｗ貂/I銘u~uh[Rgosq=]i簑uhV#Nr非0qJr9_( 4r- N緩璢廱:ov!viYe毒潭eN◆XI#F&iFN3Y幗:4(彊Y皆-y罅e笥j 瞎13)OH&+丁 y1>dCζq;9蟒=O各UQBr卷tvN)竜cLl 擢>vr]B.Xu0wI群>wmZM_=楮屆 R/d5? qc!豫 d_.p.y;習[jEiBqIH 撃>Y3AKRQ0y)K8Cｐﾌ)柩W_xW~~`<覯 7oZe4瀦癧V舗滔蒿蓚wwW瀰[SwL@]G_椙癪o鉦\用恠韲滯鞆w~7?|型}熊.>&Z２Ys49O;J*x?*輛浴沁7 ,`紗Fhw{咲?詢Z~m育F;仮nxﾂ7P R塑 e橘-}R椌oo譲蝗w~欸滕6閘o7O@8!XF鶉v|WI^01宇垠-K8Q鰕~w}arT E汨蒻踰j{q?夥OeX３=Wゑ4Vb'Tzupyo .]z 豌9ABG錠zp?y墺 "1W帛' d3TM(ら鏖x SxF2^.豁c写c|*Z專龍鉚8WF\0l4畝BBz夊衾擲椿.(,%兜wF:CqC]x@\#RR:g$S9b/和昷ln}fз=.0KoHhW施\8 nxG服*z ph盥(VcSGf&@`\(@;zedo嵌{inV涓MOnv~G叉$}hSM/k)剽j At桿刮c(灼}c6p:観Y賚$磽,槃捷女Q噫欹]}萋舅笞{PBw n棘pH*#T=GRA~'8瞬H1rC>GCj$yLd$TSgu樋w.cs杆冱]cg`-均Q0ZeA^ 擣Q>貼X鳩wA JhL<鳬登e%惰!無9CZ式k[X/匹 Jj=$hH~鮎!椀$S) dK^u 討%Q=枴¶ <$o !qtPL,r苺.?lPy^@q>凾m\/v66譱GCum錚!Ｈ,Z嚆!_ｳ監3]U)743nq奴%揮H-50tI^-}Ji tlcZ_I j竝u*V|=\[zI~P8參[7DZ!7%Pq~;oKd勹2篠"|布B茨m籬e準就C[9陝\>T^fCX XU慧_>h↓i蔑e6i黏0. x椋hTWw鬟7"h_ 菘^HE/:n%aO^"+Z稱mlVO圸U>hW予R雕Wx張w*|G勢vmU\ 嶋Y(eXБョ@PMN2r.oBﾜD S效,^睡Q后$RBh(Jイn^zuM+9: sYqMO;U} 井^[5d\蘯@Q6N5yGoKC4чK驕M_N{ 萱*ィ曠dO*vO(.^譖AH粽Q俤戮eV \4(!{'a#D IOu譴v~在=[F:Q哇)涕W6< X"K+#:rK.◯^3瞻|.uO[N _hgK(`zY &^w>'棲q創`^,踏^:g鴛F? 鰰*L*&!(気P敦 3A 孱 妬睨l烙鍋\c蝸@h5揚ﾝU椄Q@uCym.vn琴o}枩 FA5VD4n儿2P[5eダO拗Z3+0殯0nsv[sH]mv2冓`蒔膤R`殊A朽Vm0Cｫ>@ 6ls(}C].JQei6X7l1|]u]i=t0杙0杣-軒1+6N(rE"|0+#l室?Kwt.瘠iA 米('+澱GjstD.h匯ka3 X)A(tJ\S蝌0愃Sp3ndIVAEむs"56"m 38y雅`-沖縫閥]Kml;VBT}\w)1~"=ZJHk{G贐Eca郷{ [LMLp+yr%(9<+i{J=W=3q,({mi贐kc=hcz n $IQUl3 襌3,dRP!![.Vld u^HL持 0b (a e8a(KН-舉.鯢Q,68jJ AVu 'qJ疏O.33*j3衞-"~扈T/v)箟(c=Wjr!"oC]u\耨\!O蛭) ]<xJ0YcvF1殴(*Bt(敵1(v賍Rb[KvW s4AY循)kX]&.ZJhHRlO#\+A!拐R題-3g租6燼G纖eMQ>#KIP>\12A>-筧方┘:~w賦衫e}1"#8:I(靂>Yh5KNFf3符gmQQ]k}`a%29纖噌#l>`r6\xlE%IVJ#=F_欣z?lI廂籾消Geπl\x#fx%f\(fSb>KHZ茨XFｩKIR$8s`T3guork$0`PIm(%Gr;9 2魄嚏 N>%髪[ =v)d`s Rq塁jftK紹BGp垢p艢=-暉0)SH6(魃V削'Y0r餐)俔gz]7k"-D氓70W-*ZXdC賽9JMTFF& Z\ ?z>棧j E該5邊$ ｄ+ｌ&Mb(.Y| >8=7\>hy*a0Jq+址1V\ J&\] >e/匆ZxorH)ULB{<螯;zE=劉{掵\$5f鈴託倥Dnd兢".e||K猷l}s鮑斟W8蓮@.SreTl@z6QEUYCPI2c 3>>O3g塁2 t敬 \B# 4ベ鱒Qx\拗5:銘4 N(:Nr.x lr蚣Sjw6Fq\ hyKz嫦m壟7"5+\謄NK?b^軛j8拮l9聹e8C8範綸r姑l5補if剤gY｡kXB4Mu7sFjR1p BhJd)hI= K1g P t溪\P^喜OUm軸視枌泱nA7_憲+I #_騫1 ?Li%耄Du曾:g}輸觸xV 肘w( shqVGP澳q樂k>$ \|$Q$鄭v 8etp^`_dQ*yf ?#1搭?O-u8ZZFx$hTf$ 戞A4z}BHhMzH/q"$EfR ,DV\5893囘^K6済j魴KC>Etfet粧G9h-"h6E-C鷺(堂:0BN7F"09pW wle<--"J/VKy$Rm/fzL.sduw ]S10裁;ｇ \!e!R>G湟Ir蜍GcyEA:DPO.\rV南 o漂6|Q6負YACD)gZ^z.*U礫RBm陵 諌_<(瀉錮瘉ps;}X瘻%W0旺沌)￥"1;>r噂8E6x%臙fcw<硝10=I 3qi(z bQS"jZ N! L+甸#梗Rr5s[4P84ァh a+授8PVO)(E)pc!%軟!限dMJy<; prMs&%Y|廾扁cJUG 斯0溢Qj{9H56um$ 垂 ;>9B繹tZ5{NC(%X Ke啌1 皰籟 0JxeoBgj邃-fc臙+六}j}然c]^JT0u4J)4A瘰殿l!^.}EU燦\lvd紳7y+G蒙EoJ/>D-S& JAWJ qu_yQ嶽(I&帚`瓔jX,[tq拐j!5rKe>)I渠‥W{r"eFWS岷1 #t9&eRg@1\et~馼"f}Gx.W 嗣DPLTamJ仏/^#)僑dj/.&叫 <\^x8QL噫$DJ巫z牛|zp 羌Q借收&兩}o2Fa &NK胎NH:J蠶vHdRH:M禳y Q5'$t9h力i~J|恰YN-私x&7Pd i&滾AL= B0@vﾖ憖BM翆†ＩE9 柁` c７)2dB飯EСGR3$xsXer'_斐 Q"nR?\!HRV}dv/乎tL!55!C4uFw eb k[GBx=Y?$坡魔mtg8+.3H%Mw/屶3裾Y銖?P k9迢?;#待.簾dzxN侫A3 縫v;}BYs>;[%k震)筅>NQbG~C]"椿YK'j驗ru'7(e&亟MW|νM94o@?!M崑X8Y+榴{理fRfM2bu7 :l5k9熚k1q材v\SQ[hA業/Q:笋y 67(]@版f)09?軒0m!D C|穿>O>血Ai偖UO}nSFX>宇室7|^^!El4Y析c@Yc"3/qm粤4U2<'QUmpN/%$-!藪U$Z]=QD TrJ$EqRォ侯xwCK窓RW10B退拙C]|wu,}VrK NJ#2r9GgM%,^粁8a:m鵐H栓G9lAl@~JC<Y'_R'O.AF瓊杠zK"2>r4?zk| WnXb;EbiT碵O;`@MO鉢| 1P<\.,萬sj澗 AM臉框c#膨n OIA茹鐃Hsn蟻9~C}v功Z9c<蕘9\ys句G酋>EG?yH? N;訐 t?菟:t憲惑沁ｯ\8p&mz剩}9^1受\ M`O/6忿Q?[c5w艘+~@-$貸* g.t椨#b D$n6Hs麕3 _{c)贋離呶Pic{宣[7d>[,K@v?zH'e8;笈"池嫦ytsS艦呰E" 舖+W ;xA*旱殫^ <>蝗荷\闖t+艚屍澡nvT茯=m~毯=z闔v73緊u{S?be;凵^ K) P"N示l\@wmA畝県u.U-1lyDteO'PZB6Bw'I&}'n眞)z7髷'kqtN){)窮0鵆v*EQ.< .=RE-(撃C]/W!`68=店G|,脳~a zZ/a:NB巧>峻 eD/:]c 32'塢 xHS8FttY1I嬌 X/嘔橋凌/#}g歉.<癨8H\l螯Ra4FSQ)0 Jae(QZ3Gy.wzSA% 轂B!|UI`g}+鎧szw;幅'z 0l[c(9gyRSjXIayRSfマｮX=深n5+#腆oIvw| r郎xi臟?=:蔭{8W(r4Xy,X篤 顛纉龕驢Tｽ麝zQ◎璃%^殲来N>E5%\9{蘯渺j|獻鼠遐錘pu{OX庖?Z]yW碍堀Z9訖V鷸zA n震f;'bzw翁C_S>sS-襃慊呪A崔sdLl p*PfhSE鈔[Ht|科~何yx{}=t割櫟靈他fErJW;仏9 Q)8OQB^"寤5kp!gPWWFa=C{1##+,;董8差m^ PN i魂*E=@紫Tゾ吩ul6^l$軸卍X)q嗇t\V瑕s`i rbdA.輸)7Jg$朝6qN1l zy$RF甄rG5 ?旌S)l"(P茨0.Rx礬w5トO竣 TN3i宜_5a該^N`TJ`?q)lB uIJ~RF9%g%!|蔗ekqq~^蚩EjBoKh fH FHb蠡\"制A,mW"R$>(iN5R゜Z,}MVJ犖JuNQ想!_m.1B逝日W/:1%U?:| レ6@Q&Da+~ dL$JVRxgKC[ZZkYS簿hG"T抬S忝;+6EmUv.N,K凵a 慚m 貂>竿s介8$C>僻6V嫐:"T?Gq-庖C[磚[Bz#kYjツc81U96險 XE如n)菩[9IXT担1&+@ @LB !jsJ(}zcE｢dB\ [BEｶ`"Y)丿8zG4K (sVM!'" [G!k`j♯醂dXUW^3n怨v:Na\x韋-N6HMTu籵妍5M蘇]浪=E"Edr椥G療?祿C0|B>$a&%X.!1亙9X(Grp#M1矼8y5汐 黨U )'h吻的r.M^F#PRq*\$缶b8V~~愎毬>>~Y諫:L外貅wTRRfI7止往z5%w晶旻IWSJ8P!^e4S)?Fgm;夬QAD tJ%Q 2S(佇或*#(畧ihyQ H9{UI佗g路!0M夙樢~B膽v 峭~ｅ5mC(狂3Os疑C]清\由eW]mWp9~GKzN輙戒繼?}q__DxEz!S^黷LlQ,A6 fTD琢aC飽',《Q槓m鮴1XI:7%k5sl>S M])柁TxeJ(銓SW倏b$+%w禮nnEyQt+.ZYπb #n泣 ; %摎3"匏A.mgrf槌償薇z黎zk6oIl'_qSK 廠yQ鼬ILBeQ※Ns!`tцc5ElS4zP7!6D)釿FD18Wu&0&黙- 8HIjPRK V(S G aZ諺祕b儘)'c`..*65^ IId$F簔虻O.2鬥qaf]o挟W融譲裨雀蛞O46K啻r"zS)S}0XS8嫉)S;@0of}5 0*蔑8Vo9hj pH澱){N)2Nf)YU[#笞送x q=.p'栗5D}!q(A&"I禾倩8m岶Pdて>2~6;'@(鱧SyG{\Zy|F9H濃GKH+jer@揃h9C醐'W廰x4/WuD薀=9'6 思 將I&.娯SH8ph0'c^ETy夂>nbi苙r( A擠pzi& -!SIW g4ndT_Oku蕎Z堀8e+9ELK@U3.)WU)K絏uLd% :>eQf hRL"'B'KlW6H34VJxΞY Q[YQJ#8M9 7a%/>}^i_?m帝Fh鮭T蕪F($kL芝И 2,9%8 P `% /價Q.r|!x|1R`L燐k#DR$Do鬣咎p;怐n/Y@b!y{'-箏"Er8=Nn濛iK,Y>6Z柁W贈!|H璢造c#kHvD ,}|z差 K9hyoeNjB9氷e9SD0J4pXs!4Ku4#\*Ic]/eA.憑us:lfPWh8y ヱC6F,簑臓-FHQ}_p ΟYｽ泉-剤=c]|哢(hET"W_<@)a,hDl~ Zzxyntt-%$>悸mKxs帥 [嚥轎{膸9嚏kk飲)G~祁名純%懣s焉=Bis?..K?団/({xwd{鮓@<掴iqpQvDG琢 N踴_C>oF_lw俤~Ix 遇 %U8'竡蔘_D>TC簓輻癩vEZ_qqo7:脾壌IAlXXK8S /|VG9jA(-wA9|:s憬斐f98x滝Ad(.6燧訐y{wX紬NgI^C1iq*uMbx欄X?*]尓o飮?4骼 "}渙mq|に(ZGp呉+K)9kk| 8'2q>7曁l>m憐MB?喝^wR躯zt8gW繍諡z~綿X`7X奸}犬凅mo8aV# ]g/N-RB/w氏搴.~G趙稲齢鯊g醋瘋 Ou=p,0 }astE商G 麿税嗟n1!,)u!(鼬~F晨8,1.:X輊 *A縱Oc_BS_^S2&t+A大+ 綽_nvW詩w0!朿3q滬僮7:Z~I陣沍鉚q3Z申Mb惴仲T幇暴l鑄殉噴F#bl)o7,伺{=== 9FЯ靺恆47嫖v痺JZ嵯p^~舉倔贔痲jw}/ｋ=)v鼕@~働W~芋v:┸nwo5FBRlt Y6\f-T#/'(鰈Z 採F6 Sts礇62{]j!_e)2覘汐Aq虚:怐w幃_雀髟`{s児86VP`{~~3籖8{Q0GHG量V皿~7Cnctetqx6"麝xc.,Q 3"鋼I6F策RcBf瑶c$自|蒄s礪{=RW1 o"IW5#R垢P咎凝I QvPJ5RF P SHA6@汎?R蟆C希q!吁 )飫0:7?%Ve<檎Z8R判.頼;R4+ggf>BT)3墫&ehv緜Lhr寫ouuPDtM: @M隈n4織g.jgu禪寉wS堕($a｣K K坦&RPa].?漫.oIm槭ZZ:呻;434Tq*?)i^墮埔l-~踟g慇毘_waiv碾4U曹:3Y*.+,.` G子9 nvI榾柝%gIKDG琥6-}Wd則VT@t[D*\屮嶽sE`M6h%!?L訶%>oP82蛸僅3舵%uA.端89#:yk6;u階鑚>丼zv!提6y%)D蠣6#牡N;uX9z^N脆/V)達R4m'1棺R$oM,埋9[0Sx仍a4.Y}{[C8蕚 HA\81x1L讃馘v團fUu 艙4&mVWn歹lpr9E羃i4u2n+V n斥j\KQTzi4e(_ _操BW0F抑W襴}B屎&IgbRr|腹^8n#7,a[/査欷'&>理QTI白:V*<(C&{=Y"{qX(/{@q7HζrN&R政"d-メv R漕極台}t7b0L+啣i0b{gKn41n^嫖N翔( 珮D?O(a蠱 倏FY}`r?)KZTs裨#AAsh ,VONQ4A4Dr !:竰査N7岔Sbﾓe,ID]O_]C6}@e~偵?qL礫吃j葢F0}8Hj"s#Y/tKak彁i_J840ヵ`'札 EYdY鼕e彙:塗q濫め{@=ｲ&)Ш價@Y$抓'曼nS3LZDu SCy苔ヘ^ UKN|哈 1鶫i摸30嗄d苯Ox`dUヶ@OCI|iW'~6l|L白jexQ+96詰r2z.Kb／ 屶OU鉄Y冖u不/%~p";A啝喋]S汞 9R湟*RQ$d i査,Ts%!3e^u<B咆6疇蔬eS0")鑄7SX@z$H繿SFd?\DQ[IQ 瀝;&Om$^H_-'jA黹-娃d玻jJ繼]縻 %]1B0V9fCoﾉ亞"化b∩E3 O離Y鵬z=亊抜$津S7/+a⊥bOj(_潭fТf,鼬"諷\c PC F 泳G-医8jV=@徊PQ)rb!m _zB_!_ 鰛+tpzE31^斡(RR8IGI淘顏蓚^[べ豫\_+)譏+1\.о慱@v1P4Y] GM,;Z$w:=r鰰r]duu;!黌0P%撚啼>^\^}麒zd+'>果土 C)87L\eeP帶p)琵e銚z=&m梵%FQx4yb矯##,pCKlLzんbほN}pk.&d鳬y|B鉾UieJ-_+||\A)oEfqd8-誤摯/ G6 緕pw癪貿9P筬.y3睥LaP諳核W掬!EA&Rpx3籔v十 {僕Whn w $&}q";v彷x+$(A^浩稈投癈ｕp謳==V$_僧H3恣'x蛛b';qw'窰'vZ3q|'>w|PM-)69I棊8pt岾pkt+Wp }F86Zw-rO .: G@殘%n,Jh縮6\g8UQ=TK.3a*`ag(a0KbO>Oq!魑馨;F_hmq~61y涼3S/I\o&d1記L S禦X.==F抽.M@Hl%簓@ 犧iNu]KpF$Gc衰HT}雎%^KHZ鏈/inh層x帰氤zUQD颯ぱ* 宿jV譛/;!Y[> (D'{J 萼7&燦*?^)x~*04.^割gmdMik[@$ tf$3＼L%胞=m8Sce筧?w&zs饇z啅|泄P閘O?JUeF=m M`3^39麝|'G儉|Rz芹l~森殍A%{s9渺@梠4mHO鶻珸#\?nPz閣閙蒔YB7Cv#U_2aV"nn津N転bDXKD] z-ZEj}t傷擁na柩信AsC4\(]c%5並;>%ZShXゴ {x-@ 7Z 畊:C6麥0Ul暗/濃;p沸VK*% (Z=則RFB_習Eb冨r 斥1(7 B=z$,@= rQXIOz{v2 蒲T^艇丿)&~|@彬[%p晩CY$epB^Q氣J侈 oYk "NI*%勉幡#6.7Wa"p"!/儡Y1]yUE.>2hgwRJcZ 醴c郤f^_LO(&塸YL5?r,巫争XuSO]R@誂NQ%達壁 榑h^0(oO1:Ea埀.5zHMU6,-I犂Dz h{2d{zN[ud腦A.\Uu労f箱0@d几練j瞎坏FD址bC="%7拱CcO?}%鑞9\eS/2T鰍mIL淑x\^坎i9b1g(i<7 XGCnK/〓K]CP(顎 Ab+uOS|(!?:$p:w}%8!00#碼P/IhlOUGGB:5j47iJtP9$^Wb\u[竰. 2Re"+<飢溏r#3OW1火@含U",0I(F&Q;r=N 還寨 耀RI1%O駸啜謚g Y蔚)bQ}癆0*&U廚1b*zzgHtb.y!%}:BR5J)A )-Ю4Nx64 z∫f<;~#Gf／Jv唄x9續1BVS 5/締h6#6Hx 猷RM$痘姜詫皀Ds^IO>(eﾕ++`堕"4楽M祿D 甞)]{9J9伴}!znI5n毓бcKO P0Od厄9鬻FFe8H/UI1.斬e^oGDu,咏b櫁擒lY兮潁 w|7e乗ueT^経4 3:tS/n葷安!~*I=癖р6?;@ u須]歛)T鵁申5#,LX膂 BZc5p}lム腋|Zr77o>c =So?FQ肘撫GBOrH },U$S\8Q) {/# 詼E+[ $,V禰バ%;#liPL$6y鄲4,9JyRd<"J><Gx王H√{c鮓zw#h艙賊W也s}d1wwY駘SL<4賍LcZok+= 賎tPe藩 -鴿^?hVlM' 諂^戚}崟姻d N[r /fqG^zYJ'繰Qz'_利Fz雛:Zcou希徘U諌8擡_G］H磚狸1.呂z/Oi}<wMR鮒Q2!l{_`b/3鬱fbB\bN’w柵抽Bi 撫?w3z棘/葡鉗{燕bq'ZX┠[t~憬iB?QEf七璞\<:ZH穃i迂捩/XPE艤 F^n鉗i>X>鱔/{走isyuy;0_7i兔/aV> Bm!輩yィ貲-cByj>T甍ZE;_}_yJ擱s冰:.U FTD鈿e譎U静X~zu互捍\mL柝Ww$331Xr辯 o+裁]~歸s@[v:e牀IxF〓PX`L$/Yd},5姓.v懴jw=>'8S^BxiG`sJB]mΝヶv+1kqC鄭6失PjkB愿c{niCM7w %kBS痣N抛ﾀQRe;FpE絳yﾅ*s`淀~砿 6e{^q[f讚鴪罅P瀞 . '{q=~sxgV\c顯CG(z髣｢JC徼鎔L-沸[^qbK- 刑ajCY駒洟\@(9SY4bSOCH<#9E H[_8@"'z.3戈{N,"蒋8#俯'cTZk..DKh> ;Gb冢S藩v!C縒Woo]B.rH1"w暗nTJ:W9m(EbqAp!Dоpy_[鰛Q|2`3o F宛L粋]託BD %t`v%3$=3z#D}?./@5< sM0k!+C3s)*vQf _;_(酖Zu O|`zzbq#*S疾zrw―5PL;?#"J沽Te/bKh館胤|A灘psvo跨阜gdW]溌v2H$B@W8ロ猪徊*_l8 ^躁p,n1ﾄ2O/4V [,A:}]xb俑砿Hfs鴨軈4OR#?蚕}{ss:UQw@渺\hy i 二諛p nwnd+lKp39{}+[,-;\内aV^%#PW売:. 2A_1處w7K[RNu (u\Dvd"|壊dr全kmN}SJ^%4't=]nt儒oz<p夙;^{n_,w賈feH斈' X6麸E庶苞Q^=dI瘤钁`&5m;<)c"匚-1X4E啅$"O槎5喞-1dhA?生#?祷N痙1 忻Ir磅N鈔X"様w;烈亶BZiwA6)0l 睇}as齔P%}{兄=|L洋]HYョni見掬.-x< 悋w]/dk樺胛/up命;1[opeh(L%某|齒鐓疸W濬W鴉濕}_杉罸$縻君$S :p 1>QHhtPs┯l^雇*9n:蟠興mm z<,盡3邵k7^4円P~7yvゅ[UF&,j{J 叱"}JOh[?q吊靤t 3拌韭q講0~Dmj{Thdw;BlQ26pZ詈]SLut#]G f.脚D封ш瘟q威vJvM+Ze!~D&偃yIg^謡剽蠹n藁7K刷X綫KKc1umA}9gq%dSV-}v8寉^KY+ ("佞T蹴&gTIBL'%5}nc7鱶RSF8I_oH|YVZ鍖a貪_.ョ;Rz'!5遯>杤YCwV/虜!廠rgiqg$^za!sSnnp\#?w糅1珠塀乏p册 Qz藉J?M袮 LBχJAiLcB.p_EMJ喇輻&貽猖DW侯il飴-FI(Ydn[E72√t V都<$CE遑P)4毋16w銜 /B.<慶沮筵QT::l2紳eQ{翦QT笵菅⊇ヌ;2%vl\陸が胝-_ n_=攝Jc)9hzj5m)I頚命除d B0B矧b$2v堯~//ik冰L#8gCbsLdpi伏L姪4*@:Z筬alQW?t/淡u./藍Jeだ枹:)t! &蠅rg 聡｣1衷士HeUp畏]~i7好 *>i)努ぐAe/ 8$6筧_RY 6I|舛Z%y競~a,.[斗}鏗 鈞Y匪鰰逕 ;撫蘰( fj若濶"fπ"鉗j1=]瑙Yro((6鍠0ｸ$-噤R.4 %\PMa ew.QMh7. 粤e"lQrw%D廬n|8}{圧NVh7z\8dcqC 趾 p{緒p9ishA{"膓債&>Sd)ｵGRu"nX$,w\d賠$M^{s鷯S'EG@74Gftg警F}舅W落7Eu狡Z2:Uw摂w%3Ov! H SF尢|Lu(S占$懸J=o ]_?$+#eq.!oYfQ>aa立 m まVダ@GHF{oQn}k枇)o)tn 睿8崘z%b408g1)Iv>LY6> N鯵0鰒R7RT)槹IGIDr0v促KUA.:~UgァhG8NQeU惱碧聶uIPv p/耙'RO)?KJM" ~脹`{sA塵J.u(諤CuzAPYx]N屡;Hm飾1屆x齔F待K/賜2良N7qp~{D柬處錮p總d4峠G贔量D漉p Vu浄${"o餡騏=A鬥0(G晏jT`翊}R畚|>贐eg婢mGo弩]7$qNFpc{~w6.H贋GqJ杲]皇RR 碌NS 布熊O7'i>>SG$鷓o辻` &`= & ΕI崚<壱B44ЗzDEQ"y#n7o(jWO-%I{\b裝$iA8:X]e賣XKsi#B圭wQsfs%e%!@rIbSE%U/耜1厚MC!9$n=B0Hu3\V,T9%]e>JpW\毆v苓8.zУ-N縛;挿YY湎US Wlw還\ $y/.# IC `,3y(U蛆?Juu穰變a?3o2V処c^['cWCcexｴ嘴E%aK n拉G韻.X蔡伏)0Jz>wa)蒜(PH禪fm}5F=L5'hbмL u/<擁繧k3y(E) -oZf冠涅tlJ拗:t i`[) 郡cb,匁Yz bGwQ寶筌NA~襄lC^株xm#J/<呉/<vC=莨A|QR}=" \8晒3sPM<乢D娟C)濺b /AZ+k R剳悠墮盲uLr x:` EQsu蟹#(.衡S/A[)rqqc0マtP儡s,IH`Bg\KCkJYK0F瑣v]xa;kw KsSDyYY"ナ^案艪H:H;=|Ij蛸u\3Oj\淑湊XiTk'蒸鎚>j5Cj_?PN5%(S漫_)r#~ Qq戞_)`(EtX*栫E)g~qz 鞫! Zl,t7獎譯2w2doCI^)-EG律ecr辜 n"&О?Lq蒜O[振z<閘9cJfzL3u gz1塾BL%uJqn關C4b%9縺i;i]YZ&L7MIG顱nKQ>MuY雛X$隰!X]Dd]D&rN'饅 }簇WB4qCo}1):銖_ r ;#siW鸞愽GC]筏T<&疣結L+1$f#lg&穽k6GG)}!_2絛O|4,遇d諏)b&_釜GS狐s~)醜gQ.撮Ey,y兀據Fa}K酋ZIY+=v[_0[[RS[mSt[把?7s)<朮xh舮hwJ|:81S&{kR9r杳巫~5 ji罨9垉/罨9WEozZ~EJ$=$-M(1kbf磽un}> |o [cMqb劉M7M;xJK:u*OPW1YヲHh7崖舁8垢鰒5.亘`O暴Q`NK謄;L1槐掖\*_3*W汪%T\來坐(bKh#mn)`y杓n鑒=Uv[q糒7o∧an}楕BA<Qg\GhvSdlv3@$a {U|B'2OB[NIK払5榎5D莠Sx2嘗8+/烋KIW&k .U糒 vB4y:x6X=虹euy,淀稟Q茉P 6K9 布gH0渟鷹v悍hH@} }+桂薨敞梓鶫Uv5%,~E_bEQn"5Y "X1(zsW粮l'#zJ韆荳 4}凪f府+Lw{BY?}鶩?7j" 廂7q)q7jダcnQY;禪Dh2NEK/.刊[=bOuｸ帛 拗`sGPlf1Uw.CqZ暈u P鰾Nyh}/dH牘]$ m'盟E令襲vZI1汁)aPJHV賣詒NE&{7^/y-[A騅Tux&V雄Bh7FK擇J-^,^Zxpゥ掛N6  EU礇O-螽蠖淘w:&#i(c:g ; :9NJb;9芀X瞹cDg爿3NtK[臾qp袂S&cKa舛pZFsp qi鰊k聟h輛憐鏑河竚9r弖鎰IKZ^(==(zaUz+6BV匁l@帚'D Jyn%yR螫〕^F@}%.z`-,LCyP'P?:LC盍Z傑. [e*娼f$9 JmlZ7#洫lus;1'JpRn~含[譲uFdhF+PK莨舗dLV$鯰v墺6'來叟kZH欖僕r%Qb庖W萩eビR磅*bS;r/;T發?D∩#(!貽nSP$兏 鶩wW罘A4gB潼oS*o%\>qz!1t-丕8?D宅v@cA揖sqd載kb蘓祭pWaW)~$=9:諏!\H$Ld駁 3C>Jt`J4)[c堀lNv~z愁"j莞綯注/_~鞜恪踊圀 K,#pjX,e7R=桑fy扛 %7洳挾H%^ $fJS携TH H?W*$%p|OHW9v^r(`汀lsA鰺^Ba=PV"齔,}w卦 砦Y£羝奘^>fzyZ&灯li:oW5UjB‥goLIC所S圉勿&HA+)g~BBw.岷Z近QG0併-鎗lv 捲p)i頑^茸檠DT=J粨sM藥'rVｼD0邱[槹#;\n~y伺D 瀏"p栢~9熕Awv頤_R構准ZN扱G`o警|u*k-+蓉0w 靂|VyO|疑yQ斡Kh8m*掟>,亟T狩h~挟刎P o,S(鏗g(ot,懽nXd4}x[:+U筏xs0N?##哈環=gX3Ykus"丸? 3謬vJ"%-Wr;0pTt 'n堡=O惇HSB粥.yX(]a!VJ"HRB洋(g9cuZb%..1Q2U ヤEohVk仇mT)`> ^:ﾞfS宅<@G 3hGij@4Tb.2p3JL4h鞦h AD鰊O25Y+x,K4剏*u援)吉-<;$杼^Hб丐<衫Cysj;勲7飭FP3`@少:f3D醒蝕リR@ZF^h簷9;XQ(i蓚_齊o2 (蒜,H&MB<粁(KjQm2鐙 =/iBW!EM-"o[brDK@S)IDE慱s $)kb=T`69k 3X靜}D/v,栖*y蹤0pC>y^i@挿N%\*sI!pIqg\XCKfm aNA@fiX5 !cV十Zco#疹Q鎬p#闖B陀M住\1@mcX|mRduY( 疏k嶝bp(%]WO/J,矼葮Vb9=iよ! 耄塚7{=i%C 档Z)Y_\~痢|J5o{^y1払煩H霏B]pVWI＆R案(|UXBEh[#"sr!R88ZEj/.霽 疵7>m0π-[那G牧gV Zb０9C9QG (];生6y q!i^m[cDe("]oX蛩l.q_┠p乕eiE%&!M%yh4!TJ<L/#IP5C^-ZT!)mb;:I=}4@8舖x7Q.阜ku!p|曜庚aXO {-gS`豎A5SuYT%ntDh~3 疋e:ｹ8}儁x剿P3T8FIli0馥 8yeIBgV]Lbjm活bI},慾j rUo漢R柞V洙壥[嘴幻W猷6+;萎 [阿#h愀; RKs階@.弔瘰u./LZ1p bH<{1.U[/#NXFu+> u嗄單Tv19v}网鯔ziDz謠^H伽臧cZV(ΠZ: 8cg`4TeYG&eGMb'鏘Z! 9 2k軋a}OiX'/覡I幌j0Jv d \鴬惜HH壞Uf'W口H9Z= k IT悉zxy!/\~嶷 串=[6o` T[9<9U'5歳n4yiB+o|Fvx3<8~ o Y9y'頷抑s{釛k6蜩@i:N{wO18!/^w索DjQ輦 iGe赴[&y%cZ.cyseG# 1 屡雛欠>躑g2wk{f r%cV蟄zh"furDg{VyR洟M7xU凭{SJw淇eZ:,(3PUXJ,6m8 隻K"ゑGeB(D3瞽<wd検$<[e]0詼P鍠T6n!u6'gg梟U xg0'A竿!Az2絹@屠a\&HGmPR "蘋^&b祉fwv齊濔d鮠;m6?O?邃v?7Wg|襞獲醒 R-鎧9Ｖ~'r+u?棒\S`>|7`%!<{(*= Q)`UJ胆蹤UDPSTi継:,YRr%V輓M６Om@4iO垰pJK秕 東K笥H-坑&ssQidaPJ,F%SbXn`睚慈壅|jBfJeYQZK(A0W8`h决26u!X八/^SX'C1?9沌宅%歛0-Y萸5VuP襯Xt9<3l ^0tD.& k8酸d Oc親8a1'Φ.$9ヲbk!GS狹@M(Sb!然4 X鵁YB*T_3P(vu}6.Na顏繞8L9磅}奮fhYD{[t|8"2)nql'E1# G2~|nW％s个y快6v~ZDK) v截函OH~^E核艀T%4\ 保p)綮zI.Y(2)s6Sgc& ,M^+l免E&オKOLKR-@僞Yd\bIc?慚/Oo5Hz3{推f#N~v^BB羣效B?x觸|富$ #(>炸h詈j彁1L>} r蟐f町得棟oP<爨v孛0筋t-滾苫Qa'Q (G uM璋u頽JT|E+Q馼xOd'+vv9d{;Ic$JQC麾 ;qM蚋bIL\截(Y)p"ntP+E1 N巧j[顱QKmbM.i)#´KN魔h^q=\6<8B=m簓 2.O'Ka錯+迪隈D],2#?-%5B/jeﾙ榲BJU_扉P\峰眷_M6激Z'xlv'[Kj $1IR尤塗~P瀾sO0\瘡LW|ム sGcL4fj. $ foRE9與waC.!yq b暢uF:]tJ濘X|藝,年Pb#W70歩=yce叶#&[7%.櫓b)CR2C凹J;MHq0踊悵5H=10nwzす答冴すBPF%n~杰MpдXvr~E1j4慯`9閤DxNpHY7-fG闌G)8蠣 {Q茎m3 22KFXG)-X79,HHG63/u*詣BIymUN 茲kP粡nDV &x@ О@離"PlCU ﾋnF涅*4&w%q艫OK愎lgAyOO Z(i6 垠駆?J<|8J恰w 澄怡f=h鑒B憂"蛻膜ep恢轉M,v.%D/$&28I6瑳G!eGy Z1t(IgHDg)>"c^ }朴nGN0a$分W匈c,>9鋪F,+淒3Y b圍g0'yM/仕a>)pk*f;zJ沓UOz伎iaL%|ZgH b{97鎚(]欲北"_%=X"We輸)I'!;B$`臀2vYJQ+/H0V/a+@ Q$ ］p&櫨0dz呻^VL`<6|>Ni彩g3貫J\7}4JQVr殼憤zY_W`OwF9'kGOYcぎb5飭m ((惘比 6,展d｡V9~n#U^駅R UK#e痢.〕JA;O$堙0K%0Et9哉d@F濠Z鬥D0呟R;2:kX4zTn)5YQT\89斉ZN]3K&%x?XVT%vZN窪Y怎8鉢zlfRzがVUb!RIO\~"h0}|i /!I I;4娟[飽&E駻FO/ Ds$お劇Iゝc$](mτLN余J~Z偏#卸( )(>qbAT zOjf┣[M膰Q% >叢08L8^jH&CU3v氓pJKmAk^IXoY猷-J併J\塲 ` 堽(#+-Co,{2RzW_Gh"y_-I8BdC+r嬲尨gzR;`y率Y ~5;)NH^テAqZu説I@0;tH狸咫O/P["E^ blJjg$FO$芥5渇;%oTWBVYMgoo2{凖途i示K釶 燿2v`-}bN!鴛嬪:9#鉋s襤f#M斃&/蒜Kl耨獗K展z5lつ?PdsWdfs-啗Z`&p造fZJ濛貪蚤H&/#sI+:>WU+@,<O;pYo営k蠡+NJ7涸f|s 喬-*}C,歌)衄\I'H*Co/又&,CM4 sj#S&ZcW)QM)=9飯_U)U.W9+I2編*>et担f$Ao_姉b;vG|蒔竊69咯$ B1fc鮑0i官QK[x甘iMzH8 "N#Ji5m退r窶 卷|BRxGWS[7,WD!tEH:*XLZFKCb\q\ZX§脱M|恃B:R$9G咎;3&$=4_bﾀ`gJ肩k@ol0.^h04WgsnK}2j++E-填)ETe4命($AJ13 ;#EA"u2eH x$<<JMPR(@&K\熬4#N勣r#LFuMJ7.熊8@xA|&"ym@vH<簽8岌Qo^t剞q\ %Q6A7区l.E任i_D~5%-JR^ pAz[珊>萱reBm}tT緤k凱vc瓸 振J騾TAB/x!,kI,3冊=B(`H]% l$燻PU/cDV,ZR^h2;Ha鮑牛儔b\bKwZDLX %浦繆qDL鷺嶢s譯\\:I!%N}~Νf(Jj+剄:srqr |恒2lQ ?>QH|K3,2f@wx.^ 剪S 送 o)0J j瘻僂h租7r[ *l)s聴R 杆:(&+o!埣5\-稿跿.=Ai?yp p}辿UShPQSXfr. A.殃壞疸催優nNB\BRlnN] IUi@R)H9M~4y.]05N\錺d :I;蒭!($"デpU#zwrL'0z6~VZ聡Edj$N`PFG柱B) 3q!f)oF沁Eu/%c2D{懍 5v|.経LWIK8$充Q)Hzykq揆u1#Ez)w$>暘/K縊?k齎生}7 Jj(愆YEZ綟HiRf)'A)暇a電7F；gv_.2 nt1*WAv霪(&zh談S^~DQD5C+4浸xMS滓蕭 #J3q越jeG[qF^束I{i^ )qyVCi]染5sI4: pFe棋.B_[2廸IYERRX=C41x)(F8 >C H fSa:籟' J vh+絞fx Nj9kBqK@峨s x9ne/qmS #]D2=\F21R# y譟0\@DZV/丶IFS*M$.t71F銓NO>>.spf9nhb$@d]i┣榠[埃z &m^恋&}n%%8EaTe疳;曹( o}Wa FK/tOwO賛*r {)e-lE褶&mq63'JAug#]禝~l斈1>8LX4KW.簣;^Fg譟$6anExh1虔_1勦*T忘*果SZ(pFJ{d篏u^襌0+ W倬e7F<朷6A]wJfw8N播^^AB% JbC{>is浸降?+B5'BEM yf0VN"]Rw*lR廠20Wg}t于紊畠FX*ighd%jHx)yHE%-r\luy{=}環Δ嵎奠$R)bF $唱44~VFUd( K}舉`y3+ジ]rFQ蜑1dUDKJRz9捺OY5j<6y,舳.|Wk桂)抑K9z/!rqkZ^XZ!Xv{3Jdg;@蹉季R u ;7kJ法feE8aB&5>^dOBih啣;L"L繆G/瞽9#VY)(;Hg恟SG].$! TBG4.夐菟a]#a]T4*)2+y QTRRD┴躡"袙五@B]b,>2%/pe ea^>[?P&oo蘿祉@慍o|G*zl_SiY$') 鑪E鎌c-}B-薈J ~3l<0`j;2$畦hA*R&+cB\J1Jχ'[A8府3]&c]6(遷`3L/M{ un]MHe@帙*j問]wY.H"lD}冑$卻L麭(I犂@0逃oQv`z_Nf訶Hi\k>樗==5p +q禊檳ttMq#rsy?^?刹O雌毫鈕)F鉞膿R駟胸紫p飮笆8euI?>f犠KNw幺^gTu*|ョWJil>熈{Tw汲W[On榑 鋼燻x貼1鵯B? k旺瀛*RM肯HjR0瑰:"x%G遮?黔 &d-!|9{cINZ i@D謄枢 q婪oxa翳y8/68kn6Ι1fl 籤VZA牾 汀Nm呎弐U殃?_'@09V1of1#yさ0Z 窒握!KB(90K;O-°迎竸]L#w.Ly4VS夐淡`Iqy=L.hse弔8y=j"a|(:u撮}w椄s1;pﾏR?J冬%]>粘駮Xu騎l64};6J@Zg%: NqkC收+^ruE鷲z 5K Eix来Iu,q*K1.qmCF ト-T\%H覘u,/6耻墨m Jr[=rUfX衢\拝6Dv$X $ rFj%o``皰NI>bJwwnV nG4bQl, t`6$5'"X Xz#t賭 肱2:B&H[l|hH*2GGXFF閧T",7]Wm9eXg"kM8s/)U惴補ra}q7'e冰鯏奸*c/OP1E#ixZ(SQ0z4&"遵i坏ESG*贓m驢5BgR{-h-ｺSR.u Ck鮎毆庖bBt[ w>脇5Fd.旬@變& )?/8!0='[)YdS債g<EJ!検m"IL嘖L9[sW3LX( si'嫣DKJ儖P綣 2(#TR"{Y 熙eU@)ET5W8講\4監{PI%#瑯T宮4Cq,}ry]J虜>Aq娑引礇8 ],by`@p狩2\8駻F麝ぴ,7y]H杙NYwkV^3JY(J3F$a{+5禮%T崋I籠J_{j| %'柧v>梦S?T>bIpco!g7U)+WЁ寺{橈v7{/{4y1 m几警ck肩cE=@NMG`VJ \y(s{=h3'@塀5';g2jZ#薛K.x矕UC搭E暁.遍r弯X*Ad吐"%,l#& qA.qjCY{H'犁Vg諞M#)S/wGx龠胛瘋 K響P~諚m>癜of劉 6亶Ef4(^ s2恥RF\蜉6x)dO賃-"3臧[DNBX[vX8Nn敦穰3G\N~`_L U9w(KCHV!l$&il+韈{`4.|65 Wbぜ.!m%I壹KBZ簒剱q2`pt絞弃.%w!> H VJ\lx仗Q泛\夏!%8LqE徂.濯9卞K免{9r酋_蜘c亜0XAF 石e鵝2 惚R0_嗤:Lb熔'!_OsX絋 eT曜4*t鞫nS9P揺豌豌Q q棠@%Awft%LN 崛Eu{,[R釁tCUE@4Q|e<穫/&@ % >黴C竡|dF[h1CTO&i%蕷6I "YvJ ~nlVLT1[>彜#,Di慈%甲/芟QfVcnK@JCp)I42B\RF8Uа[津 寞地bd,E&-a]$1!2Tby%o躅}1∬T7i5ze 輕補uy?扮' z5 *檬oVτeQ lｶイ$3皹2覆6]=焚?unS Co曙券()mU={(|o~"涸筺ijB$T8D獵戯院R|f絣R堺D FRGq揚ICtzNK |i$-6xbP#<,;T尸Yv┴a$g'彪Ct確BljfE2#/na$p^B51牘0=漏Ifvy笛Y賠B|露2>J,.#S]J`eK -[eUl!瑇J3S整^RK."GLVVω啓Ze%iX-衷 c>/Y% チV:Yo!WA@N'枉鄙鶩豐R顫#keN洵兎\ E9鬣迭├|肉 $[-/t農(1$5LVJ壬'j嫦5XFB]EIQrJyZЮ穏n5U 'n)Q汐?lsQNAЪLYz8~6kQ!%嘗mo嗔鬢Vl:z_蟆H^ULAG'dU)EU+vY蛉稱疸=Ax^B3]襍俸s諛-蚊O5)p SL5)$ 貍#OLRx5G:RTtO.1'+w\蛋>? ^F垤眞蠧|"xHyy顧>l貞F陌o' q7-畿~靡U[e竪VssJ粃桎=.4O墺fw阪労T;5iU +-_l:1_w\oooao須n橇~oiB孜∀Lo俸倥ｫK胱?析R  WW<@e獄# 霊US'>-l陣u繙3 .Ng-鯲B^?_V5少:S恤\yP1Fh?}鼡神佻5t(4d十Dg.>oE廓釉|K2eMu斎Sｹ褻wK@氏K,瞽\(M魁捜K5四=c;[xZ汨=Z*霓~与）#v雀Wo~蛬庶.Wp;鳩欲X*SUfC>Kg7_徐_9齊y/nwpw%_幢.嶇wwr{|0;^vO腫ﾃ屓j6拮J&x病-蕈Qc~eoc<樓x >\炯K*u_R蹼ne/9耨;D褐竇nw吸溏朕蛛AaM貉om椁恪{昏y/覃.+y亊_菅 ｛Y鉾灼宦a_7Fu温<<^B\V]I&yu RXSK%>Tb}跟hrI0V)kgcA奮K+IfG638aTvC.(i(-例|zvqFyK}Y-~vqQ.<〓.IgN`筒撓Xp aRe;@b型2sbYMg鄭W逮リ蟻睦 ^)bNMP6P/q_b||I琢>QK 鬢 n7uwuPN(xbc錣%"W] 1├倪v便)Q}Tw.C q%qPEk彭w\ +/Fり(+ 煽(扮>r稷EK冨*#QplpLaχQ]Vq\=[1齦2M;2%|sxK< D)敦)淵珊wsm 娯鞳υ;|ltFYyv<馥1b偲(用qx巵D[`H,ZDee /9 iG1ap|j.$3蠎E0XC1Qa緘d炯'xxや[32Nm}彦EルxJ-で? _9oq" =E) 済裼饐蟒@e茱掬f案縺S %#Kjc$$KI^H憇)界: Rx4_GJ20 ?爛Xx kfvYw淌xjBSt1U^靴)nIJP)p.R8$R+E〕fF鼻-Vj&A $}J z衿伝揚V\&#P!h 52Ｙ.H#>F (QuJ嚊Aj2聞?屏x屏$9>0p x.'qCpB)AwQs潅郁h68鮠VBU地d];鑪lO房Ew> ﾍcLw)PT"#er.yC=炙O離^ 歹gk疲DBV9F5} f/-ED.L甞`iB]翳[1#b4d.,速o|っD2V8- VANwG QVR)[汞( u^絆q/',H C.*J \溯91:#r陰u曾 飭w&$KqZ .c ) %;<[7;Bum`移bOY!c#U坩c njI l櫃\PJ\s R噴3fSз殘$?w垣1$:ZB2 3q役割VjMer宮7^F妣件:dQP#Q&(?tl-|F9Kp惴縺kKe[9=r`__,46n2Ki$o髞o^}sz.p]F但廓諂`-gsE応o2ToA )fF/防退e9D>he$o阨戦KN]榮苛#{ yBVv*顋=34 Dt.5@wuFz茖TyT殳彪tzf[^"nv認+'*慥yrz?XK抔DY託0zt 申:4zx>盃NZs:碍G宋]N)G^ 1&c,?r8槎`E漿曄x)9)h)DehB"0l<^oh曲{g#eqhC$x0~l複嚥賈勁6竿gG;/3TTV-{3B,} DdHKfrZ_PD∝ LOzg\#!9U1%乎&E~K齲L+8Fl0Du}~纃QM)阜UJfNdM_m;$茘裁#(u6<ょ)H>4'(a*#09P>Is {X E茗2厭o牒{!|n徼誡 r瘰>\z漱`dBFs I;縡^iE$:/5 kk[ S8}x[E3"k+#vX 1 ]Ut]t叩2RC-#{-U渉Xxr2讙l.|SG> s "mHYz&G{c廾yzX]慵g;yW@I膀剃c3J/U \@ 3VG"^塋 BQ赴墻|4.URK{;SZuLFms*N鷹)J*牌8lc錺簟pJ;4VJS3'#@QHsjP繁:遐W>e+Z:1#鏤阜棚Y奔P= A: QX蚯鵝譲裨~z_= 愍+牢駝milXgR"ly N"c)oztEdF6# gc!鹽3|lD模2mp L)9\w Q~v{ほ> C]GX:726GdJDEl]U_磁@P3?惧訝尠"Y;7k覿ce\/@r miUi4V而恒2Z泣Es{ =\pc4Np枡q2bf#U2粭TqV3-諒&k 聾 `N6JP2勿/送}:d){u#BeCXqB))綾ci%b,畜xD<=40hH吐YgVNL]Z*_h裴l掎@Py =[{\C鍖yWD6з[uz%p_;ex"U0kB+\YLEYK俺翔Zu篩{炮9DM-]8>8kmi<鯡|z籔釐糎韲KMq j|4`LDf 憚&E麟|->"憮Nv'嗚?}皸掟?鵯7濔GO6M|GNNL融邯_O)<;3' 鶸捫隨}v}Tk%)}6口g龠d?wljCEw<媾3ro{{'W囓*c|<9x]9旬r茮8)yvGYl2,僑/KJ\R`駝l#6g h9Ep ^險Fh`3'Pl3'霹v@%20傚2R@{9F))貎状z3粗%揩h#&d\A%no雖L|(埜/崘鞍XxrX鼎g)ErE hQ*筒%捺Q{宥T"Q)a簑 xPEk].`\H 1繁AUlFw辭鱇癘/?|p碌蛛=>67W賣d8夬^mcS 帖U\_Cv碇T^?MU?5z3k":B&88 鬻l鉚@xV)]b?]"~'Q<"o\:酋c&L]P霞DHI U~$7)虹尠 誚* K5"Op]vFEr瘤bCW, 曠F滔tT"}wU濃] B孚修)jh模4 Q;^B撫9葵iW毛胖pq圭唱?\% せ_\lsB悁A/N蚶e[)'3Xм)S^QJEq{l J=sP$"Z #ツ.tvv(No!8:0PF],jＫ 碆4owtlxGO^舜' 4FB=t{z儺0 1Bf庖`QL`F $.OM 念PM/ $cI@¬HJ瘋Xa\眛.旻鈴|d0慓 絞@_)(& V唳Z礼 箚a{冬租呶a`$鰛q jx+5!:(墓0L岳;]KU(Nu\A?-[A V|5&N跨u\S'7O蒟;7qD a6)（S 'Q`n`;臉%菓 q齲G|J2x凪lzR|7DNlV$nBPwA?c9邊Q7学 ykKS11M]`4l/% ]/ Y蓿驅gL躯t9Zｲn^Oh埠u(KyA亂VJ"F5G,Cb`sP迯馘翼驕Bs=\ｨmEEQ授;Myv>$Mbべjr`DJYH^.N廾A5'+E:9 X{t隶]抹'O纔e蕚宕蓙nww/<5 :kj d::|8剤]ce%"簸~w}re暝臭s丸|{樟P施\2d朦盖et邏r5v}v*/v崕mrCTDY[d xggj[~T蓼_'*ob0Zgm{'I朽輻=PmA\$2k%c7 Yr=8]qzx IJ旃3燎肭FnvvG/T葵0EＣX鴬q囗 諫p噴 (g6,q6)2/霓myD老 ut}*K邨y3疳5A毟契禰| ^q7o取< oЙ}Zov齒:^ q wu蔕s ?n釧xfq[(S彷1k3>膣,戦6s7囚憂z*Z_/9n7x孱F隼w闖?P螺眄Ｅcmbs/pu山[浅~{詮昴]\?9''`i%鷏L8Fd粐?銓權I:'E[%阨W;"w;o/#W.vq姉(C伉xn ;P!0^'o遲帝k }[)剛>[V/;<鰡,'Xs!萼g;胚+&by班q訟\2N啝Vy憔\.wg& 梏敖'bc苓u;{y銛_{Gg芍/4鉦.3O3_竒'ごV墓5迅=_bhxD##Jmvjd<R,w!'/`X**E7PI) P(hA#Jv∨Heb!dO^i<茎ﾖ4 W榧(好2#脾#岨.}/A uDc膃 KK!;/i弌5f<_BK9H8$祈gBj罸cEN聢j "T狐4 nsE 9ﾂT.考TD/凝W憤gqvC<史,ウ /b'鱠t 扎RH;A贄;#r8tzf蚋Oe 嫦&:aa脉Qn^ ;$0J)9|% \V]os`'q|} u H 栴\Vc_娜{nz 吼RRJJIdnW+渠躇J?;$1V. E 篳{aP壁be h'aX5奴32n 革'h f魎2 2剔A采gt>Dd\歉族CXI$s+xxl 'XιPg m` T窓gcT遮( ]nE0:LRD"Fr汐^丙 ,鈴R!Q H皎f9yhCE>!wq詠or0B$l<|N$&0vdEz%敦s捨GUY鐘ywe:g_z8bNibttS豪q0)/幄=qZ| D*3@g媾X 婉!q6iDS3 矯3%\lE v%%vb]售W&w0瞋) %J!]ZEX娟wZOQ@磧Q壟GC8:4F傭mO倖f0[突_ 褪嚴|wQM^d{猖AGyrH靤<.何y憬l97W}ww止=+苳W｛uF|O=Auu呆g!%cL真Lo?,I幤Y比送}Xl<>室?隹N焔rSl~mIp闖7ah=V!ALdNw燼颶~w?~/jl|O{執)`Rd4-g#F+w 重Ia%r;]硼o麗vBrl|Fwm74X斡\[ 3ql$Ｑ;4q^$j`3處{5 歴:暘$y|_[,tz+/窘d_Pc% 6弄EYU跂m$8虹+#tz5Mj,s..hgV!xk醋<.)"墓Mi♪歌6彁Pй;9zFHXghQk\}GM;夲m黥孚x7NhdF膈瘉d}鷸O_魅6}t6\閻鏘禦k,;r籘Go齣);逧fsxs4.q真;t~9串随iy8堝灑蠖磨歸c=?弯笞?lKz8P}{wIbGHmge禧26Jb,) Bsr圄衷X4確n>A1;3流]T批U竅JT@@Wj戮/鯏6=S9Qv{%ndｿC )u冽we保鮑|/\j淙_l$ 傴;*^凛Orz 汳@:JGGnFa,r2U ~< ;RX_Zg LV\3"C 2JL;F甥)eWMAC繩微Ms]<ηca>涼l $M+I靼飛l J% k癆d$(S=R&/%*JMrieaKVgB91V{~_>9CUpd5wRN=1}貪;SIP[(f@<9:>O;娘訥N:狽r`旧S,K/^JAf$米a珪!4[枢M]nf.)H,)0"牾 靫J昇&Pe/讚X6d/崙<@"P]哥8bc#`+AT鵠 Jq妻%}-4搓ZU([I#tOeЭ8笵PqexiCrR]焔0(c/討蕊DWfヰ覚0xS寿}2zx!O}黄穫9oWs緝U兀:獅xo巧VM蜷HPAG3暃f4!Np熱Yv?OFR冥u_秡82)猊)t?h\H?.W勤 {}斧ck煙/Is.dｗxzaJ%8&n\鼓|#s (+熏?`R4 (&%K籥E(^燦(CRPE/HG齊瘉WdzO?wu公o匐K;崋旻ZU!1P0S 判la8峇42"u#;索IFVm XHY.油4(#KAr!t;dξec~,G◯E告H7 kFrsZA!Q S6?rP2慱` y\/*hz3Xnvй驃在談lM;u碾+91s挺`l(燥(cwX-dp3@qh]('塚瀦u婉$[W%Oマ冥7罨U|f錬%痺c霧岐K!|,ZWtf-)驛@咢&S> 闇2cpz廛!rзe梱@V嬲qY qE狽lz+R橡 UJ l8>く#yE敕Aqぁ]LIH8K衛R qaQ)2i-*e{\'W\~]9, mgQx2[倦$\]T9憲qn*bz l$6零MK m \t3& kLmBrTQ縵F緡1感LAH6^:}:y々#屆p>pOrY~(=A"=6H3qE憬 uej歐GVyWz櫓?4X'=|萱<:}ha+默O勅竣P'q1ir;]-劈衣茅L&'櫚u厶q鏥2 〈g盈白G(kH-疚奏♯k\oa5)7C|;0б$ｕsc31ri|*$桜lyVe糘@_DuHyiB%X0crxI1G({船A)xt&d2t B1Eｐ-F!ヽR$`(Y跖}鞣fV;IGw蛎M /緑攫桷 s *$B{mI `RUG s?ll隧慓)Yt6"=,:SM ?D/s9>m338w≠戔乏鐔瘡EI~2fa5En<5$~l+nfЩb7竅彿z=6\B'<{=bM/qDpPW*2~~z)`鐓T*A(册&7R9Ut UE)p8#urGofc鹽VBr冒3n)Kt%蹂i湯槲emug`O丼]^砥W柄wu}[wc-:深 i |Μ{<埆NM c 糀4吶忤`ZW'a6肢迢#{1姆贓蕕橇dN-+}AO Ou)~1 g2`y'&dvUE!:う [ 輟*鹿%弓<,Hm♀$Dy捻帋(z0舘imB!]]Z0hkpB d正8zE_V||+1zGP,A呼諒P`3閃[M=っ~Z懺禅越嘘U`%@v8Ro)$慳xE4nM9M鸚K&筮2j*mＵ"濔TBk_m,籏彜V,=眺候i;衲b溥s妲Lw*$-pI:. 閉|tp.9Y8鈔僥r8>NA枯O+F=胯9OhZS.p\*[lW更:'1寡F支nof射 $p | 梗Z沙午QMoW床eKoLkR8XN?Z鐃e$hOkEE1D+t顯刹N)zY署糂Q^' |6JS'''`Y2>斎^c!Kt}"C4WRUMD8|b*z!EY!Iid)FWTJ[庖\[lY"kg*Sg栂S*d2め+S3eZB D嘶5般 狎x(=hkH[Dn)e@/a\JE岫算U}[ 蹌 1C $西pL2cVq砿Z&削0xKyv/{∇/$vIs読g"髴vaVFb@俟a85=!熈V袤8-4>Mj木r0= C*06nF:I dz 稜Cю=e bQ酵jSBL\Nal] 鍋□X 6 >0 i(C鵞TKBD琴k;raRBaNBv Uz6v4FN:S]ol 培vuX|! ,パξlP甬(aﾁuo蓐Sb2vn3SAKz際 ,戉 ;6NlVl馘o欖rF(鎰V<-x畫+2)]'陶V Y来(_0首JB%`證%!廝0fL3otj.Q譱!(6T$ 爲PF囘禧~,aM;牀WWgYD5o朗純政洛=;0nf鵝aQ殲睾ph<8&4A_ヘ[Lo1S(5湘晟(o蔚^b÷≒C+P8G琲jmoe讙r s#K５》l.D!?Ij抓Z^厄c_$慰B?Da\專p;s`9!f夭軟臟簣=繚從_菅S&!?>h (Kq\m*r$_aJGitSQ0eOsY V$Rge:yJQ嶄H衛eK JZ52 3@ W!,^氾4wG熔嫡糴薮 :cl勅N\[Eo樞顴Zmu_*2@ DHP(鸚:,f!_u釶0E/xe!1 FK:輩XE6葦S 3xZD "vFI-Z-r~`b70fW我Cv} F3ZWIu&5~RG:aN/c3"v"甲vU #hA蟶8*v-Kk;LiVA 筝[D滬畢Qe頻#街[HUdA>chE盈($6XNJRj 懆為s(粭 26:lk8読SuA癨`y'F;;RRP:b←到.JD齬".縣症hkW,NF"爽Ud$韆z+"^R;a癶d'7K匁|?町^z q6*呷U8&MjyR6/| tJｩ;{Rc]-##a)l5*綣C"RhmqVwk{[/R`|eP1A8_`沛Q84RJm`;`VX[H穗罍~]~ 叺蕀#&l?Q揶@LL /{V~恷n X[仞1S6c 痍劭'u 運Ｃ}z瀬I)pv5f攬W織X(,I EkEHjYS凪b[DIF笟D*G?`F~ a菻 hd "巨M(X3C畧[`鎚k瑣kb@&J 偲アOGo:8{L fv>_l貳&`塞M杞x#羆ZEvjvmz#q-06J英/磊V$8sD71:dJWk玄u4n&劬1細gR`U8/庇12P映0ZN;晢ZgIB*e 犢[M=w?UkWH/EP途O┫忽C剏{6~%@-vogKP泗3瀞寰'6IH="%j{ THt HZ1A"@o&0偐xAN A2嫖| x5C~ 370(|#UtOlZt{N)RKUQQ6D"醸縺VTxｴ濶/腮$lZ9r]%蒭BUvuV@-GEz翡,\復 }ｕqR(w;Nz[嶮KH)'kd{d鮭r_+EMc`"5)6N],曲#啖X]被仂@~ l9P)"u“Xg)C&-悄%棔6 B9jD(SR"089L気&,kV清Y粃e@^},wVq]4a霽9g/FS+rF)jw 泪-羶ZTedgA.=)6x溢_0逵挑@$R5+店8H)@dy "nc$z歳U繹蜉f;0k90秡Qo6C5u])Rq耗gY`ucM鑰1pfS+"p莖EWm酲Mya/v彷覊_^`b[ZN|帛６jY飜mC=/:@襲G 1kAoP}J[方[u郷`VM-dW グ9\ l遲7 ,'.8O鄭両B澎)ZeX$bsh\.到=e!^;愆~.vDBbfP)剌VdI "鮫6cjAfHNBJU@FN j謎cwI0 慓J瓰eZ(1FB=R+天斎%.愀h給Q[λ 8｛5B?bpti鎗MI⇒61X/5:Xc兢HW樢(bУ * |xp]epU\陣c1N8`IR觝符牡/''$喇墜!*ﾟO(KmA羯Cn>#$ybtO19Aev|0*emQJ9掉,/Lpv`/^C:{Wb輩嵎[)Z`Z tR=sだ.oQ4ゼC>} 晃臼oY:1uYv#鸚 汕z! !a'dMK靺Jr[跌q2J籾0i+oj雙愡/2Zf膺iH} bb!ｩ琥0$攻ye慚M,VN B駮! 'Y4$膳%碵K7{#K4G"K圖!nJRY $V$&*8Gu a=窓0樶"2:qHwq66D~yIfwq5悸$qte{^R*ホSd( %!R -vZf令;=F(視軼~u砌積x(<\Ａf亙凵=奧GY'1 YB藝xw,Uqj LL`e 8(7(%[kr笙6W694;mZ覧;妙沈5K萓伺躊7gi=$qN硝:%4*:ic9|Q~@ヰ眇blpG.ns明u梛詼}r遜/夊G\痊媛78=MfG楯;0 g@k:`/Y}P +pl#il\ty?rSBx報2w撓 Y撻曠:Z:& z秡n/(G&3 fw*Tfik`〆_]\"桜jwIx9lu%C楕留_╂nV?yxg/?嗾 {釀nP;s57羽樔x果鴈k謀zTY't鮮m'.#脣4}C娯矗QA篤oU8`諫J7p;3S14ki/Y邪\o3yX}->9屐j9 Y拙C拒査G納R}2]砂/Kz織GM1qa箔~u該w[V.Y$汐鰕 ?烽=y 障26栞b^vo\^4猾En?_0聒m8>\K_dfqe: nIe螢l61}]酷% w8qA|fT(iB). QLoe纈d\題q+"関R4付e|NC冂$r ((MRt zRmugyeA#^k%I.? t gB^_ZoLMvhH ;q3栗uG{t /wKjJ/^\M\+\:pqmH?I蜀|拜WWkN`b!oG{%e!雌vI 7撤婆TvdW$=e.gaWY斎#K$2琢樺|瑠餔Uq\7販k /OiN橿z:凧'!n |/Z@n U邂AtjQE:晋lw能kh昃uaL壺R縁Gpvefmif_8FJYm瀲J5uJea9G3ъz適_0袙)#jB樅4秦蝦Hr.1夏+^翅,,湃D畳tqth[z浜z油kLG2%l+[冫"v('収~":=6c>7DCwF8^D-Hjp命VHAJB#o\ >`$XpφRD鰛^nG庶 m`Z>r僭鯣議#MSο0bXelu9^\=<'|+q{-iQ,<_x-覐!Z%.雇")qQ箆*&(\~~鱆 {JiK擲 *'Ba預{>{眇顳^s6^哄k~r5里E(",慚1<C U|pプ $3:[ !]*櫑`<7yAVHH{菷娟f腱|9mX^: p,!+wWT`薹卵蕨x糒s┘ C5дY'B0j浸溽.H- E.鵯υ贈J-陸&Bx[}q5o9y婢 |(ue8W;%ブ[Zz説j`徭q肌NQ&伺V:}j+p z}5N`WG[KR嘲"嶇爿Y#稗OiQo{ ,TnIUh謝(櫞K%将L'ny,x哭/cA3z@/RCg JHDx Ip>QMw)猟瑯T6粢s 袰rNW%pODCZ|gIUH]f] ^}( ,=+i"JH'黙勝/松=[QO/X梗恋卯M]1}茗sJ跋E9―游 u<|w`OC県抂 {LKQ涵=vl:梢,v鮎朿幕 b';矗] $/Ck< ]瘰兄,~Q,餬  O_BQ焦sM鍬j v菽}啝#m{7(gJ_1?ws5H&SΤbr8７\_fu端a旅閠feCfK~JJ諦\JqH 殪b啼瀕[6U汲$ 8v3K(?Z朗洙qd錵3_潴^nRN9tT氈VXEロ2{l3(娭謐滓y白h祥湾P_Oo~ W1鷓}9 Q霍>o;{C喬[簫{X__a5y?b;k榁幢ｐ!%t4nAV3窩混k亙癬u YoC,2葆g}p^-"g#;椣總蔭|"哲a#恩貪~Ye/mV.肥 吼cp8a 幗 N_guAOi0bャｦh]N2 j}^}8C'~46.R瞋l]煮oIlS>^dX0D刹f#┰1bLsm~O$f%鐡tm5弟BTwh!~ba^ Q!lD A陥淨眥6G-5腟@ 勘BheB斌]-蝉P{-Z!Z逃dgNV|'#磋膤_.7W黼OゆF7浹颪"k&C=q薑p;r~Nl寥|d8a\)7rd+-萼{wUg1pL[k|磆柮c`衍?DN1B 舒w{逵o靼/@!_X&QvwW臨kO霖7Yvf襠εN自 i.Q+帑%q6鈍U0秩 Ngel/KUQ[０;fq2gm倥V?Tbbo鴒f緜}k蛆QM6+◇館<[黶f蠧f鎰j艀z`仇o(|+qd情 潸N徐Ta/R0+t大%斡+jj廚c刄培%Y鰲鏖w}R葉@ふ/璃UdpG淇0鰯wHU9y_rWpN 旆2hq5]邑健.鉄W乍2wwL)H=]覧d孱sw蟷@z-^蹼 ]爻緲蜉 xYdw `A|MUX-BxO[d>p"⊇朕.QDPmm)+Dai?zY!Ndd6碧TVd8Ya+怜秦YADD:}O5s?zAuAV[`LM3L伎D寥 e36.9h-h 襪坡u趾鮪ju物'P濯BC= 函IL^~!>IF9mM>-rq|Q&'r%;蠻LbsCUHZ[yP.jd抗- 6[6Qw]滅w{5"/n|] ||9 q蔬狆f>y{踴Jl棠鶻K籠=|y;mNw> m6 掫VX /M<_e鸚鉦EV\\-/悔BM猗t~r@I0v >$m速|莇誦}r澤革v廈蹤fAi[$q.y/- 藉$XD傾 BeH+aF踴Vz#rsq7u ~ェ_隹(B椈縟陛}轤[惰 s qB`&E " Q\dH#AVm#^徽!兩FA-珞$k`z以杳:fX@胖ZCv7L2_L*jU*`s%仂%鍠掠K n(蓁趺逵rr瑩sYk Kk凝: 荏N `dz%旱i迅+brVU溜';g鯀W腴繩冢sP}~tbv化>c#聖N,鶴3 ﾏn&qe)w1]cs%C17U!L1 bQ`.K 釜c4uk)嗹gJQ櫟&=ul7蜉齦屆晧W悍o舒YS4秉b,c1F&gHDZ 貘骼|wD鴇VX3twax懸ぐ:?6%ivsdf虹G3/垉cX逞rBQ*u!mu(I NUU 排慳8"w)x;{0]WsGq塚劉k  ]aw[B'yg:Z!潛zoA棠ヮ"R B月傑SoT牟cV'v斗址y":N6bU:.Q遒\筌O _6 !_鯒N亂崛|鳶H+v/L0厩wkX__wK65Nxc eS褻X;庖濶|謗 _8n0sD紜T廣(N$W#鏨?"伺ジw覧0L!0z@02v云VVSMBEl/z4HH 0螆Znyq7y;P萄 ?X=のO9PcX-Gh 9\T筆EcPer腓kIb 叛':^P yG 雕 I'bA2m,@Bk'５掟Kn旺] _rdl!MzV\Fi{綫i{Z`毫JuG*NQOL|\Ｃ観⇒m.ooC3BxGf場_9o[_機n G坡E98V右T5B皖aP38kK奘克^u暇$ア&w襠犬ho數>盲kA信hoiG8Z@HQ  `T&m;{&v 1-貰下ua`栞駛ｰ贋,YG% <戎%'櫃W8Q籤椨暴K詬f+o63W=7E賤F褻^謀p*3zx/w n泱e>o生{G椒Ui!cfW%J&,X<)l!濡].P鋤-[吹執B]睇]KY,n%ISh[ m|Wxs昏K<懲莓_^g欖s捌;毬各;Rlxt;{Iハ1~7:a+ *}凭TJ(B湘條>>S-Kuk[vR鶩答4_K烙$f;RRu>vq需泳[i}]従w:Jk&]|c姶wVF世抉 .@W|w.(;&F,E憾]w$: %|Wp;_溜G:Op.^eqvP殉Xsqy及K塗ej*6<) b鮹TC$郢了t7g7`聯u1傾OA驗WO(鯤 忖3 劔+NyHd&0猖E//痊w?|_D G絍弖3:-'肋恠y hm瀛H;,]uz杯R牴Qd# 珂a篋*K&<俎+@s!Th G7驢TU粐=礼B9:Eb油.駁L叫J`麑/O逎}H嘶~Ty鉈V^BJ鏐4 鏖希+BU +!'塔f粫欟G滋syNh僕 佶$斂jq:K4M A`:99Yr 塾操8'瓏-]W淵{+j5w8反x 彌60kiG c$g1PM=yY齬u z[k.[k慓B?鉋莫侭亨HMgsq\駅NT瘢[\y]N癬 ]*v{>Te慎~*N梃P嫌椨U7T栲-m(]顱 A6I怺E/GEiq"4 DHFMORW^oq藤~]M p~(蕘!續9*旋醜k_Q_ABWo匪Yh弍Hi d^ 8謾#>Vy+2>秘ou&滝P8/鵁Q*6)Y}acXsぁ兄9Ri4"ーh'[G+MW;iA-^/Yuy装gS N狄#KAGH家聾朮xX閇0t血eHN=a 玄=5ZlW rG赱vF!: ~zXO廝/懆俔Yo=|67G-壜T攜"m$P奥bm閭M:>>魑qB^&m2k龠瀘/9dg庠孟蕣f~z]jtpx]Ts?6<_Fb3)evS悦W涕&枚QOq#9H{b鍛k+q}2e苜RJ惟7q@2孰鶚b]Vu0翊b,蛔~<~鰲|;:a6@pе駑\( M)_V\幽v{粧0>>fhN3`] )qz愎.1綏篩瓶俘廻Y[ＲCL^Z冴鮗9唇+z/$Fsc|`<罠炉waﾁd娃~3;d;#醸|v6|:fhタbM1H O瀾w'V/l/|倉Y 鈬g]梦ZI&Ow錺 {j }GS3/mYi糞椥@fqE髣`Dz,狎4|BmZ4&M=(\{ﾗDN#嬌漸JdU芹mnSi&*6I寧雁W!yW@賚a^7Vu祿qai蒼Y抬鉋p 1gKo n{ j鼡蒿|_磯$莵-p#黐塗嗷?2[0|P{3BT\梠D剄$?B鑠,r/揣]] B6цf(4 }VdvEOSw3那w=0=ol$2!e0$ｄ\7^} {睾3Pf8@)Zm{a$6t腰%b険X'蕈^HF嚊%R1;段BFe措1皿e#<~/~RMV[f\x0u =Pt!肋 k@2 m,UUVオ2輪8g嚠M|7w!OdR{n]xeDSra7黎"o$=#yFZ3B+@3KJyp.ROj; | 橸v=}F hX2ne>4i鎖 泣翻%7\^|Z1雌談~UhQ@'楡l`u_,;贖& r?;0~Kr'悖hFC73W瘉 ^TzJ [;d}p$(glk犒 XePtQR\2涜妓舊愚淺R善O>u , $i3ｒ\(o% +潅mr g7Rﾉ&! w糞@b^;v H 雷K$'a榛K`癰Sq2U7袂d]3+xJ憩BhiPUb$EA+n+mb冷e*o'z:.t|摧Y詮~賚R麹i5∇舗{U簦*v$We:H聖Om{'懸j蔵4m0DHx?Ls^_Кh4  yK瀉`|oQ閃梏wｮ営"[}権0;q])qB8hW$*Nx./3xZ?[7h{=疑菓38菰P7 7Yk"1'%eLS(y 徂混&e瓮r558糧2q蘗}|;;C庖1Buzi!\^`A/,`y*>'ﾝnVP(*KUJ `8"e]競W鵯囮4#z然 褓[ZhG塢\zl='scれ]/o釛S該:A殿34鞴X L{zJj`]Tw深Fa|nI丐B4"}8[w痿J_} H.ini;g>,_i9as参*E私8羮2hK慮9ビ錢]k肯詈[蹄(必an支~9N{k*%穢SlM)>A*6\ d dB穿k}}DRhvxT呰VM處颱焼@me#[鋒遼V窰qu#z$OPe(0L８$仁g/zwo鷸'?^~鴦,m,\}~隙qun+o槿)p萸p|乘#落=真QY tW)rL諭0!]$%, 縣髦坂e)K2碯6HS`>J.+KY.三r謐椌ju携Wd樞dYI聊}c@R驂T%fh^(7K4 騷/(磧GF}u!7谺 {CLW 竍kQ1F4 涅Hk~Mu|k{呆(%3OSo{1Mm疔K 蹊z() ISDI- 弍B %a_i85p%~Z8鶴^i/!ZV#!賊Ｋ瑳P@o0`bXJx8@{忸;WiyE9摺:碍Wf_ gnxx5"d瘠^皈7CCT6xle@ oI 1v霍'W犢2&]碯!K<M726`#d,\\O2`|[X}ywRj$`$y^mf_=48背4&3_WgpUZ2gY澂7f&HQ4-F) |JZm`!）追*&H)盪K**m 酩-K,鮎 yse= w8p9般;蕃F侗熬鞐Ih4z2NH仲旭韭wOz齠<[龍 弃 YBA#巌磋 妲ur松3hT|-b\)Y ]K"1 ;D猥L])KUG椡)Sw眤癜 +5E+cO旆寫U][U(鮴<烋Q掴xLWr.94l鵲埜義~;濬Sm7zy,vxwｗ~1qFXny$6戞栓X漓序,!鍋h9*$@4總Jf FZ捐[{q愚!m寺CUFTo榎O C駮4W性 a甄C?5!@旡桎in'棘餝O 斫昔>)Y磬nTy{.lヒ7夭4. iZ6kGd{XQxW-lッt魄CC$RfyT*焉朴vX jAn1{v'ぢy0x怐G鬟 V\\'5CW1o@m`瓣f◎b%4DSX馭~滕寃啌bj嗾腆餬F}@@5X醢V鐫BZd>$*溥U8|誇m>Yd2& 8s灣y}z窿;:ll> 敕I|u%!:畊(s刺汚5慶L躾"WtJ 6;M[hFWTy,$ZoW.0鎗t淋{MA h v｜箙s髞良9隋擔>0/刀Qt =s*閙o}番5w1M{\mD=o亙5[粲w[鞘IY\ (}\jb濾Q5h服E2t珀 maTi spX喟vTph7GG卵<損侵(鈬x短搗N峰0甦箔Fm/ykLhlz!-l?柿fCb1癧V@`/B滞<%#2GB k]8Vs@4lQ3&将 }  |匍|sKZ&CT嵐鴕#V|訪8c鸚oo\jDT6hFg|, '[UDqQFz"^WTl辣丸lu:vmWQiLxE zO婁zm迄5I~)K技麻AKaz｛=&%3腿A$迴\C0碌;H'殊u0Q)%}* 理jwy洲0w\瞻鵆v }挧恠?jxE[~{-zq蔵V踏K9逼萌沈0 ykJSf蓑&KS,'EMB呑PPp S0ΦT淅K^篁SG8ミoy8Cu-&憫 怱wefG閹3o_1XmDA`濠巧c 7gD?囗] ;"oymc1EJ!oGa躇iu}#xG咐濟"#&RZ:eN!L_i$jｂ 怩z%*^薀/qxF[jWH:B$99g偈緝l益jy9I:aG茫OntL"\Aj0&%*淪Ng*氾8`飾tu岡K|T1Kl羞W54DW樮z壮p1碾J h尨巛炎-HP\JVT桴d6x]hw(:$孺爺(uqY#澂>鐵 kvYSy `j%Z!rho≫A\G=PBbh.|Nt%4EMpV<をd0C晝4 ]BZ^OcQCY毎V女A啝阯vCM菱 _尉稱/六A74uc1_\{Td縹Kc>&9威t4- U) l‐*/m0WAp?BbHo;De@m笊慯DpOG;z-z昨BX謫艸c%H}*XP鯊)>戎q8啣]*)湖-AQbﾔ`v}CH瀉3~穰暸株L甌般萄}eA竪 ?;'v(>O<(=b.N技s肌rpsyS)j~Nx+蹙Hf劔顆Cy!斷商@kIj[Z矇*)9& $<3r9麪$阡巓YS*I批Rr/n^ -謡D興房Kp1hC篶雍e"d柩鑛>雅n姉Nf会醺?3 xO尨G_Ut|D 0圄{GN;vSq侘"sywR)bvO摸4d=1;嘲)fGuww底T 訐V疉賂8綴'5 ,j燉篤Tsｩ&1釵Jc@1Ud{c;c~OpLcR&OpL5任晋 (褫V猴/\ k遮算Opz'dEs\jc)/N9OcC噛_ "E妙-]6y<`:OCu6FW$泯>+8;m@G 請agH87胞G抉e叩7蒻糒"n !坩tH 二滲Jl滑p:g"霎jJG<p5)%`g{1 J9簪淮C WHv,?do~q75s\ayTA濘 EO7r &]i`PCQ]k!ZIUprOX楮北HZ?憔93J3$VmDQ麝|w^(喚f5>$D/yqUd5俔bDNJ(歇-a^WxｻRlffi\'誨_錫M~h>v,_[ygO髏龝兔JZhGq 咼FZｳ%w"#g[w鍖WPe760醸]%渫wa:Hx`j舎'鋤?B爿枦Ub = P/f>RiS wNn*k軌tco糺0q 奨rj握>Q態9Pc%$Dtj3n` 蟋 ]A5zX jR~l 通q`2&t~OH蔡2\zS-~ow蝨瑰>vXU'需嘛DVpxf)Qphe%ryQ}1蔘zJ$g/~?'SZ>V}])Gap酖P~USHqIX Q\礼Rf_rvW詧0?,個宍煬青#7W訖# 鶫 ?xVQ 購b騁麈  \\QX cE4>ai$+q茉#乏P紅u/Vk ]W+寧$\>4SEMGyeO`(Q;d65&{),X$6xC4 Y遮3qf^焼0"v}1P~vJ Xt4]]租徇dk椴玄憮恋|r錦 I8b=uJL{@7K,朖."]{a"nBJD'朦2SKw sf&e Go ,支麋,}蒋ii2yque-rUC鰒BCiwO 6晩Q朞6浬29e<|QlyYP]椽xleFo#瞑2{v=/ P硼到~Ty傅-dS濂'栢僑h鴛{ПY8松8n裔漆疾~EwwffoeOS[)2巷Lm薤&xx&箭鉚m(鼻aU(T {vFE("EN]VY/=Kv H"=>@07逋!CF XjV),!~pwj鏨dp顱緋陟1飾d拡L<{X2v! = bknв5CMG_4價X未翠期痔|躰AjHMR&祿%tF RdZriH 鷽,Ht=%9IK_陵w~O1Yn;ja亦JvN ?"投郵喞?E^`"<黼両y*小_&NpUl蔕2Mb{偖釧_zdヮ<~p;Ym硴ofJV 維x潛裴竓tu{ 垉yV4&s輜序t5心峭]0ﾃ4<朧n鞏a r}>i寥=c)q Y9t&s7vK唾褂"dbLf=R訛f&|質}5~qO俗I}沼hD82.rH~鵬援?G[F兮Z7jt鴎:S$|%債的蓐L'HUG-膀 UMK~$6]|* S,oS Wp}6+)h P黌|Ok=AP\r讀8GTZl栴Oh洗H'!JnB~ri.LzkXW~$_9(互瞞 md9NtTjfP累9/|uUY''=~彑A>V ]W%絃嘱座^Wkz放CbJ2zt運j-WJ 傲#;恪94(伐9@P-:v鯆胄G E? }9墜ztqy&] :,|斟g縮 (傷5欲Ma$sU\ +R曇f\N'` #myS斡!.>a兇 慓#X3/dP=?u1[n~u bw]^*u kl7w$6F1彰想R醂套Rw]b帶~笛H6R~z筋0 |v/1逹z9^x岔腹xc桐!)6Z 宦開r0捗%J攤埼k毓>鯡 mO&HC1q2 黌"!;dF札OX@E'W蹐雑桔u^ ,~c}b_H 棆得+P対nF鱶1XA[9p泪厩nvt I`d絹72RCSj膀=05 i謫fkNq4*xQ~#pwiW舊Cu\流Rl,:慎5辜=w1pA錦Rq$痘%oI蚶+5?hｻ@釿A18qik|> v罌FT2,d.紮*?B,A:E ws]J Y&K' TH純g奨R>+_zFkxsg├9Ь?rl0$垣o6$dж万$d掲r賭 +仰KZm_/,sm_下Tf肆軌F(櫂rM澆b$ ;/き4J ФC嫉誠:~遲/_=蛞__m S|</3e1jl!M}蓙 CW5CHn%?j06bFqa"X寃 \';^B妍pv#縦B*endz怪麻Qr8&2噪>扨T径i'Iyn卸!o+ _{d;EU扈J j漓=\mu-K!]脉e$щ顏")[奇臂|u雕[?M'L?k&~"p4kk拇擢)=BK噤m麼v$Cｋ0x虫Vq:Ws啀s*浜 勝u 肅\ptC=x+p葯hC 沙 Dv'>憤宦L1a sq0L浜爺MXoqv8VIVB齊 lT猿;6v'鮎DSx \Vi.NW誌r佝ej;魑,l00娠iA1ﾀ;Nt侫o^9謄B_黼IwcR右s贅Y愉Y=n)"U4盞v\$^6\Q椅[8H7wTiK}.\5!`_'瞋>z"|~z/h}q諞8, S噪8$6E--Zj#r荀on読 lE#1`u>kf}@z酉痕)y;qBj2/:彷初載.>I勳幡y(K9n05槭ElM=^4,蔽Q4QG必＠$c{H;高q佗a]C4秬 0t!!阯7g-V&幃w/xz/ bQG骰tv:^?l菽dOT{XA,W/侖胯/傭竢_""詼'(QNmSQefN]k]逃鍔s3h墺W~<巷wP告坦n'z|祀鴛邇(acW'pz~u>蟻D+>檢悶v=O炭J瘉7Α x杤|翕/^?Yx H' ~tz_6=l[*k舒W潟% v闌陞a戚?{jx}{~GM汢b歳/oy'|〆w ,@m wI竸Mc厄+B)z|R01{S&|H\x髑N&"-- $IAp8=:O4G黌i9&'#+制~赳蝪C泝slz獻/3JJdd瘻&境=Y.i}VFeu7aFcC}N渕!V|xA)0p卍3云Q該^C4XQ"j?~黻N目VV溌擱RUr氓B咼{l徴som<謫u賣:疵揀6/]Ko3l:[zn,h'蜈諤",pU岱鶫bz l0G_GaEF+\E悛假-NA/XF 1a[塀=Y-蹕 >6Lx塾Y,_1[9u0w-JH02$tt恒Tv VNv$1(P S恍徒r^sx_\ 淨帑II(pikls/ '7OC* (l碯+x@J儺rJ;%:1g;濮>晃^鰕9賞咄UcQlP \軫mI;C)譏-3#,O1_6xO 8Ftf税oy~yow'F腱JA先梛iyuNP}繻W_*區sM帰A潟v聆 Jw/fl濡*聹n_}juY鱆:GH田 g冰D癲_Y`;痼#tB撓軅W.単+%VHb:'?0 魚2笹焚KON O訖|郵迹!C~澆6mv=写V("pSe9舜峩*郊q蒟z 酋*鏥/恐Knm劑)Ll%Ww慢\u-.|zwqLq8h喧疸Gd@D$)@觸燗5z榊f@窩E=skIqep@郭#[ @'/2儺 卷C`HW6伜殻來S匆堋旁j┻R;爛k&i 陟hOJjc F惷K AS!嚀EKa?|】~目X7={<鰹驅:C啗ot#徳4ゝ} Z yV&jV*W~ UらX[1}觝 誦M-I@刺!螳.N椿h努1寫d3az)50懼[H5士U`@TH0 4DΥ+#%vjH?浅f粐擧覓.%彎61ho+魚zTYf蹇.Qb1V^K苴j7}s{ 篳粨W;耨&W&.:#w,|[[z$ E渝tNrPbV"磁氓,isF% ]茣5執b\u-mnW7d2bZ嚀y`6R8姐b徨vK$hA;I甜4j| 換]E黽Noi雛nSnN;X3桀7w"換Q+!TuV 9｛D%vp4j-.vV g ÷$e~濔%/謡H&|SシCv枅#霧敗堙wx楔Hk晄t!YE6t?JyP`tJ{LvLu#emvfl`Uｴ透t!E\f妙HI*:CD網Nk~X ;H145[G&剴@ %6 倶8XW){*HMg]% 篋*h]#s[拑Jo`41vt格韎f裳旁4M<\|4wL^w2 1/v2児nb仍pm<BK')ッ朸n0Z圍渾jt7X-8&,杼}W 抒ゞZ揮 YEK灣V;63Z鑿 貞E7#t6M 蘖A"_nR};欒}承-|s8惆1e) L"⇔~~pah榑穰;暄X斫-p濶u#プo"5 nMXM鏘H0Y骨ι鯊#Z*>#fGuu[Q7督U|/h_ #也TJ\(IdL(|痲 k纒ue=ZI 冓$e權vuZ~P={WcI遍$7||f醒MOJ;]a2|P読斑X愬|]m褂z<DrS茘E樵c墫Gf$!3x|P敝樔 r>替 U$>I"読5qK<粂mn褐(E[] ` l8L瘍Hz討hEO Se5U ｶKe<(Z`)j:sn=勲3cwv/)Z閻}FH>(e~]El~pi鴇N4,_6 ! "z8C@NQF_C?麿獨ﾟds+CL!聢棟[| 8EY(#ゥ嵎Hj.5ukN1FPGFJtkI,+BA豕.}茗ｭXAE{vh#{X齋H+h:`PV hezo@LDr髟>Ao-グVS# @x S彁Om]L M_YWWoCR(CCO}鋒G- HpFl[z=LCGS鋒<%3UtbfY濂HoYg$Q9RG$YIxEvpmY9oA_ __6Gk碆@ FUf>nn[(靖b2Zx{pZ者kXI!ut^`7 奎gU:i邇yH.I侑1Gz1uG店;,簔}T消繪ｮ鵺 R*.A'_+励zk"j"B{消R;L($D |y/¬姙PzRVJ詮eHl默_o(32t翡JS[5>Mc7；御泌{El{Z5D'-W09B=56許(vT XaQ鞫`!=_]>拠S :6G禅云^H帖TDoN憐?簟stNQ0Iz86LF舛iLtUq5Y{|;zIM%Rq濁f甫V^液2棕!;┻h<僖禅渫Z 7}$廏=UG6t=>Ty牷6/J~uxq'-幕~|BK1幕E睦撤O@GsJk|R託u-]`I[m]O9U超 瓧Q私*}6$~!)崛>Y體鮮)D 十窖]N潘軣3tnu?R*]o天UjV WZFo W7怩角.o\;x-ﾜJh{3NEdfup粱婪Rrv6Mr`:8iRL燬 G厥vl SJ!3攪柊Ji8ZaBX^Gム?r8買hr$X俺(P 92貽噎4｣t碾俳U{cS^V芭ChQn7,噫欧Bw$/P倅豕Rl o0w ラ[ZR+巷5P1刷佚KJV臉j54G<糎B Y@^dﾑMzvXI!混O覚b#CnыFcm鐸vX~N.$~匆M;P追hZF錚 S+x|擺EW%F;(/YN2幻3采0Z第`#Y串@a価?Cp.蕾\mヰ;燎tQ'*/iZpx Ag|p麌>冰 ARV.XOtq=MW=rm郡$MdO;7dwi80惚 Y$r "qi&[[瓜!J)B 措k@Ph8%屏梁-W{~榜壻\e lX/G%驛{Zc&X'+~T芭I[j+>GO[*Jb|_/涅/ >/ 槐zU0rZWY+Ez捻q&f&cMgU@dY\閔%,-o追F]%U 践+rＡ "?GD#!e@況2o百2AW峰Jp+%.c蔭dkGd{m筋wu;72V`~hd}b@pm售Vpw亅9$ZQx>LVg(}逮z^)-Co]R' Z}鷹敲^b_'"猝>:涅Z*99)`cD<\FfP'g 8疊:I猫n帶"m.='m福福傴CY-8贈u訥oZCKy檪5?9>H6}7bk0^^ls>BJコ23バ9嫗&Sh@Q ~>i倭%=S4V6 ２CUnGKxB#Li(i6L拝tM*":YE2滸cpB鼠秀cgjap?8bp_mC=c>i辰争r@Yp由3縒>$rBa5p+jzrO鳬I丘'| qc瘁ky"3Zk;|咋12t腫1J1 3；Z)1+Y9wcZ=CH髪IJ 數 i'1c船,m`Gn&yOI("N垉TSZF86d\>5鰄#$rn楫蒹+pへ4 eg齦唳o\Q王?_U9cr2驟h}f昭U醯u/*7x[v"扁Dgr溟X[HWLVX都j推煎WjEUHEVВ`$僥d儔`N=jR*D5IWH}"jQ]'悛wRb9M%dvu析]gEh`^N\-欝YvH]\a価fe]aV 蕀EkWyCK|YE曉w$:)FWX5憙&葩D驂7席^=6%lmJbrHE酸],]w#珊D皓G莟幻8&_$岸囑;fSlﾙEn8`RD~R0Wv LP~X( C旬X蟻0ks0CI1Z):RI.g(Y_Z1j}CbV|ZQ8d]褓!m-g wn 濯>)Eeヰ. b K"0燈/^_#稱#S~沍/雌"&)[o1$L<h]]R褞粲凸I-:6yz\TCk$蠡G1罫HX[oD)5~R}o_gT:通I">斟黹c\~Y0}oI /y粟,$A XEZ芯(Bbz_WH/qh-%guV$bkE妻j 8L2ICW91K?V.8fLblWL曇H蓮$立;. 7H,p点rk庚u熹:(錆]黻窗1#>軒y~e@f潔瀧2_W&R{f羂H=,佗GYX3s蓋灘舊>74 V8x8k2jogk輛蒔v@塋 f;*'p "糧g^丈巉|k]0Lik p-CWr輟漬U`箴坪%pbB\[Zh[筥B耻8差i蛩vmq?rgTUFC%丑tRFe \7RMRZIv2z8Y2`a-t};WE繿虱W0>V@e}03'|+S湶2bR(wvu沒U`RK`]WF -0境d}k#' 治Z um窘BYW'WP\hG_〔~獨!疑#d貯H0P_*針額`竹♀@返海E;Vo[識z"煢c$XVIxTJ竭PiV$:\& "wTj椣ps軽后斫FTgﾎB# }O}q頡逶y亘KNEN3 GyeDq K''瞬Y&MF)v)慝%IFV弼pQE)6wxc=8}Zuj#Yg後.SZA;‡R9fa#PXr燹nt\‰q）悦泯q遠0o^融｜y嫂-r址j0"3OI範Zv.m_ I@$BkQ昃[apH&UK快B,zei I力#SZｕEty N%.QkKQ陏C `Cq6,zk3R摩SD4巨L6g jr擅'釦浜揺褸lz衂Oq1誄R?a`脾/発x g!S"罫7|瞳;p佶%?tCwP_ZtUx@Am:m1@\AatFI蹄s^!Y筏% d驗>#{BCF駻[%{8HPm澳V.}[$+g騙*F] $執伽f9託cx:"j#嗹佞0〇J l" j2d.)靦{B歉EI:蒐MLA{┻ p#h 諜aG^tヘ`VyJ3O鰊wO5M_gCj 愧1Vuf}笊L6苛vm填/2gr8b' 雇&N陣n@ 0どJpt2|t聿(VwKI Rl%9バg猜懆F[J愕y峨k HEZg ;3c!"Dme禅'`8?t/(9檜決VC卒6kxH2|oW{N) 1]WfP@N纛7[MU1矣!鶩多_ >@_ e阯Pr顛\__1PjT_遒_`1j珮(lD鍖粭肱tcrE5)}fDq5{極_渊dJt0Rj1Pc=@筴P! )j}V渾k*CC 5sS?橡N}戈wo5磴F鐘l| 2bDVkHmu_G0Wut3,sE+榴4i1 Gebp麕RGml@Lxy冊.(N+展_j浚%湊P1I, 8(岫Vそ%P)挽B"儂u$CB" T_碇"と*{0ZKjLF諢]l@I8X萇@H5BDx1 +gm'縁h滑矼 zn靡9施泱byD塢RWWZ粡c A祕S洫)-擱 ,滬i0 Lh6UJ]CD+S8"v販疆[@Q[Jj*^臚fl05V 5[=H0b}4^oNぺ5Kg[Ho員sO. Sm$孱8.Slh澗i*4}mc*8/B"X9T|DUU[)彰５砺q[<{蔚摯F~_U,sU"犧Px諭vU}$.~t*0峙C i囲夫,HS w/~rNrMl沓5u!)Vd lg_#+`hY嗹 ｮ"]蒂'gD/mR0 `r jED赭#^6B{*}站深)穗CwL+4CYR-V韮kl :ag猩ec葭`[12 NS!v作BNE(朱T7滄pT^[B(e`?|"OJn /\曁>g膿}眄eE"QoEPぜu*Ec|;春竪thh;ne恚kCX?> Y栴XH-XB4E雉cSY┠ZmQ nBj躑Po m!ぎ忝BH腸党(nJPIrL,9昇xy6die鑽鍖K{霧Wl/CQR監*KFIf釐DRZ- ZNYk珱TlFs\L椀蜴K \d739K4P!擂Y6T!4kSJ>"9bxY靡"NHT mm;][Mwb幸umE衍n粗%尚p *"吸vWI\(町56RqCim(O l(5 %8c蔭do];IZ?,)Zb埣>8Ipb善d.歔閲~a#掛!9 AL//b,b^h*6ux /`8P誌Ou稟}W4/},g萓cf[)Fd%i-KV顴+E>G@(cY]qG)芫j2:U#)4Sc胙 wCD*拾w堪cVd.凍歳感X｝媾Udo?/髢\[跋Z駅油xKWgFx S蘋 0I/D.5`D<銑+ヘn]! 垤業颯w柾A!"uy~)欅c`tI♯I57F 'IPuOZsZ)*d添JP9睇U~\!m冀_@悠l/ k 牀TNC hx;SK4b3FP!) S,淡1摧nW鯲跿!~Z純MV遊U>M` 溪DIRlp`N#umqFH^其P[E \x6SU,\$KOf<稙H;w来=~KN4vmP#JV桎lnZrn{Y,{.j\M m p2@讒V^甎^X]/.鹽yt[@6i: !げ8][R %f{(%5+I 1C禰$?hq=IMA#E9HrSE-r啼_霆次騏9T nA_ZA燭 拈Y)fuオfp`6:-J:XJ_#A|アeE音儺%n_,Q5:4聴-臓~y$丈"@ 99Bb背+-$x渊x~a2?<{/?{簍鋲]達俊鵙\營伐h#&Q9  s澂_LczW1裼Tc[/2"{-菁Bb漕1lと"Jhmp泪 x:%J}Sk//@1EM!劇'[P珥?U无4Ha1da(Q$嘗kAA%fFlV ?DO3I\ |Z>悩~Ri`UfRMN p"_ nulFLd剽T_琵D%7Bb@F?hz斃 殕>VR6lbVdd 5q簒!2 I/w-kb竏H]鱈L;jX雹k>:糘'B杼{lG仄=XFqrB<Ｔv醯CKR8"qQ),#lE2@aRFuF:*BS碾C9Eq=I@'m<叨icc:%)蛛Xj)gK掖`|ut6d=aぁ!裘0Y罔蜜散g& [7濘n94５z/qzP![｢圀泗#P<:7j?@屓碪W槹戎 G閘],侍)S鞁V殖緕WjGAY鳰 覓9^j))j(PO`dj憺^JA9RLa8WQ舸j;#|牾(M駻 錢X4Bb`&**zZ# "錚|耽'''_PMDH|[9f掎HMy桜$ivJWT櫟sC>6{Z!2CL鳶$7?)$p"j罌w|-Tr1*N.l{C1@TP(-6aJ6vJ%$6V)uFち*.%L+=潺U[u N$|"Ns兢H1sDfj9cj"竊b-6'w_よzk3KMq!)dcNs`1\P芭w@~I=EM* r鬻c d撮,u2sヮm働 (EグEZ暮糴 c;d.P40t邀糲〈g:wYJIp+E#]+E首"g*U$OX`(駑Y5 cБ掬≦M液0*$>jGN(妥峙UJl幹Z$輔+Wj 1m'o._ub -24H(@I２GcH[id@4MyM{@n_=蠑K广,D j誤Df5D}qap9o[珸=gUb證E^嫖)Z塩Jq\Ds論8棡~勅ュtCz府Tc}yWQ.%?胴^JZ1!xv!p gvX)o^Hﾔd8ZR~氛}H5廃Q8*j儷}:QXMT浙k:rMH&qqr$ DrR臂+)|;+び荀^蒟蕕羈&Wb">rKN逧^DI rHW9但_!*馥9M猥MnQ!6~pBrKrnB]:U _@| *#,Bi)a`oeX;y婁9Y#-,,X R+pB"4sWn88 苞E0pBbsn[kEG,-q鄙 'ツ咐榾pqE老}6zw┏瀟?oG焙嗷wq誼_WW `H8E[wЙc[=%a8uYD;東奴GAz_-7}Hy1{tvY /Gr#o(騙稠(3貿盈睡;_W懺"改x 7臻zwXv 6X\]f=a p Q{RmZ G鑽泗 N竍Gp苴83z_\l罌6~З酘鞜!M`+G甫" $~&G^殀鰯@4G;z.!蚰=Q9wFR`4E*L-:綜,ioPNI j|: yqz,'[jy塹rvB ∠W馘]R+~e狗x76GNB認WV鯵i9K(#抹J>HN^kUK?5O] 具}Yb餌hSOS聶b%輟誑tQZ翡 c}v溢- BYf.{Y8R:-](pp120屋Wy+H届y ?dZo摶)ﾁ_[-p~cZ$ 5HA'鋸t\續$５LB稙E滬c*＋?a^[ 1宵?E`;d*e始s'裔趙~B迥驩W[ @J-k\MH=廸tGt-x仮\Z~灼鉚A驍y>洋g A昔僥掖吏G堀鎌G,IZOЙ6碵P+281 ~X霍柑@5嫖W?熈 黥翊E@N(@R "xVrC4QQ=^旨匝,H麕弃|Xt~萄梛9E逆sJ$K|Ov-SoCR助KWB0 ZI|r\芯5i斡傳VQ楙詆蒟#\W9R!湎].Q濡9傳L75|ieK} e' 甸n7D扮狆Ks',#a)(wut訥1儂=wtc(IqpLRtSD(,ZN禁X3$猪屏~KV @Z$noW°I疂ytBR顕J \5^pY n諺'兪 ;H=勅B"戀v班v L]R#iP+R"jSz!uz%7bq)乍邁\由[qC*6%冕 F鰹 ~怪'HDH,D?_T*$樮封KD~4 t#;6%|]F; ?<{~~鴦E陪o@囹〈jP{z@蔓S1 繻 V_a+{N @1zp;39V搨FI#r.f>Utj擂bO展s3xAA[梁#6ue_|W17s :fd鈔w粍`Dr'=!荊審１蛤'跏~qi倜鎌9M.>f◯V&@履}A~.CRd暾倍)黛Y疱xuP#+cQ(擅6 ekＵ 輕 SwF詁Zkq*pj[`RJOG鐙l'埋 C^#Qo@%=Ai #7b8 K~IT 環e亰TIP#Wだzt"?槹Bb._権粨"eU 8pW#Ш!-|傘q{畆T(r@q&k屯oi狹2?y猝-莇'v哺C 濺rcj7VDjj<xW%NiZZ頻O%J"0Xw(締#檪8g[j佐蟆uC隣h9K?j%(fﾓnQ[X+B|qE2c栩X=zD[S*' BLW)%(免V'」2L $d$JU&酉ges[8p羇VxO紗萇wo這oqf-? 薙) _m&@d& :D 漸N珱ぎR剳 檢氤`yDT$qHIVHＭ3qS\ZS:堪"c _$Ph' <+q<\5!P Z@1AT4Gl$蛎ulj)凧|-A\-Ｕ"謝S"RmCも由(me;m^W#v准JIFI准*jj7 K脹%W琉V黷怡kSp_$&RZ祐aW惴sk刈"DbS韃hU*Jg,#蟠陂;(8L8@u' RJ')nL篁F)乞p(EYW膸栃,Q鯵;+熔Yz.Z;\{G齢"C腥瞰=O41W差掌A-%tv z彝緲P功I9`7~OP!:8}`^Vk囘6O 猯]{x|,DPXK(尖陥fiZisQ&&-斯Mo1,(hw`6Q\i-esGs&%9Sm(, 縊K 4sRK|mcO振Lf荻Q鞅 MgCa貪[Nz29R懈NJ#E譯|=亢o[e%2@砧逕83{O>|D與b+/5("*g#d> 漢<碣*z%.$`<Rjt躋Xe7+xm< *$グO-拠責m_>C4 At=[uN~鴦s"#觀A~Z7}|0.{d鴿e(2桜Aa( 崔楕0ZG>:ct(h"?眛3至彪猜*jaz -0b~2侭;HU:J P*)N`燥Q&#AKnUH妲_ン噐 |K/I(Nd,g60qL!8x|R徽懈a?WU) n2q-Cl飄S(7^ |qOk胎発 J !+ぶ"/OBy粐Ggd纂7u c'5勢XD ~z> U;H怨p2T-ae KB址AP BG bFb 'c Gp{ RBD)>`襲.qS潟cp1凍2k変繞l捕e`,`S9声 ?p 2|g労/!l眉窟 嚆T詆ecy賂a昆帳jA4aJ&$B-KI=焼鋤b國H:6BL a:sM/!NI-竚bxrHMx$ [ (@lC栞9le'L04I6U箘稿 uu0雑CJe*親$*AuK賓DLa[[[9d濾I苑]U/剋敖m*|渣|0懍A 'h咤aA3X8J-剔Ｘ狗Zf%} 隋AxjE劉beXT]Cx;@vQz@) _xZ):5}3弦$Vn]E '][Tjj"dOn}[篌矮y}\H7F sjＬDuS10kuZ]t MA-PtV\s\R"-;lv詆fq儕:倣 $欧q身&C !:& }畊 先}"0質1v0這蓊'/Q&;Wc:m* x譛P睾x.n,kプdu旛_Bv%['_A2@QjR*ep;: u逐J,;n功盥g\m\!壇f¢c筱Z吸VZ#5U'ｕ"1k_^f =( ?Bn漬By舵 pO腺兮6|LeGq枦`=o0!茸"R*.4欧 ceA从貧Kd]GQ-&}r :-/b鰊 U9{y部B蕕"Urpvt捶1mtv@Ml#q h[DHWRや握e+Ve[GMm$MfU`}T拍Qr{zº*|)U糢(藷"&龜IfT雰 LbZSd(L?nXFL!0`M5向H4C[ ))+。謝#]ar因k 麪Q招/鬧)催鼠 ま安鎌唱|~o,k佇]DIX[i2擦坊`/ｩTI,"▽仂HnG{I郊 !喧m賎G=]皹髱bＭ\Xv3VK"F=$_担b陏z(&? '`s児b癢柁WH2?&FA6~*ペΞ yi移@;{ qa-XB&貴l]=咐Dk*V 0K7^ h%+Bf^Q5※/#睫C[u]>=O_a痴Cнd'箥N\J簽V* 6**$替VQ0Sem;W成7r okW11G辭隴 h^&C孜^司cf$鯡3^O*bF'Pff加棗d#yB|S&押廏)怙匏Ez蟯bK phU!8*>あ*蛯I6yW>刈*I父'Ha窕Lﾂ姦~2p鼻]mr吉\RNjQOZ}j拊RV !!Xh&m@*砺7ocs"RM* 磴 %DK蜀E 71%薑粥 T1C唳WRZW蚯cm]%/Z$/|娉'PУH題巵 鏃BbP濆 襦 .(vQXAvS#1T*5d峅o0懇}苞轍H杳篆Hzh8Se;).tw燮8N}"'[72:("朦賀Vj 袈 ";nh[E骰0屯_$7饅HE CQD)&g防A扠z刈"]=遷"A%,g_2 ZyFE4q 創.E,颯酬避 ~1m噸龝: %K qE2u-`C撹Rf[|R羝r擘}VRD7tG!M4夏-至 R熔N&:?WA司A]W皃s$Bﾑ-2[}v{H5=WZ ]\Ea2_周D/E槓B昧繊L*J>@!附]64sUC:MZQTaOZ(r)サ(乎A姆V4qt`IEY;=Jn!~{A"o ff o q巷栞sL]廉OWi3W炯RXF$,裃/z$7JHg\R1T)sVvP@Y旁"尋^覆lG*y`%OzD沃焦o**L!o7`@tVk″i$3欖静jEl莅oo_; R1麋B4 c7lS;*[\+賦x\nUL tdd$z% DBiQ-LW|5>.""I\DGA>15掴0蔕 nLH咾￣ Ka E(#xh]#J(廱甍;I KdXZF ;jCb4e5[ B;mo套CPQ同5D#q峡yR][4牋f#/&H8?DmD~[ t\深?D)T?r蕩wxu NP(n;槙tqqy!姉RlD梳憬F xzqv6?_9au銜lf酸N} {]I鷙+熹lqq~bl0 ]fGY箝<_ OB8 ]R簾7葡#(\v|eJu[)栂Rq^!%h^!『]B( 3Lj繊T n:o1aKSE愿-8\o 憶$3IUrk 0|"}_&釜RJ犖Tk@現Wb錵u$2h"UB{m+_%$xv"憶_!|餌+シ/C悁~1侶/IE4悴] 駘 .J!'塑se'E槧 ba跏^z発R~SX! HuUa緯rH Y"hdq殊C&6(咏党82鯵/?F_&i&兢lhEvvo表NNrr$+{7NDu耻C-l5N≦^BPH-vd8G劫 6"f2C;遊t94CgUげ-$s貝 AU_Ja)hCuR u y%B.VJJUD,4'AF1+C荻E齢DKD]c@6>^>)幃A食8"~VLdﾈ*F 6D抂5雫壬1PD冩VFWNus0OLpU$G'楼Tr旦&GlSN'_8]0昶0lftrDY簿@vB1d9~Ud,G6冽|L0Ke[l8 a%A1塾bC8BY-6椁VEmOgygII(險rNz$ k楹c憶1IN7BV?:&辞W゜U~tb5せJJ xE\bZTEzVX52/0dopU,5.Sn7iE``"受3a馮f//Xf煦r艾6d/J"n 酳龕5詰'=隻At`鑑Ｇ/Gxtdahm8v研fd`tVd位[Er5O6姿貯 *0B.r;bG{5RoM(鞭吸}^fJ謚v沚喨w@g葡P鎬.N%T釿碗G(<9 J 柔GkEr z23F!}藝冀朶%`薺簷踵D*褒J2熕¬# A峻"[H%uZ 欅neHu戯^Q(e+F-悩*JA X-WS;YLb5/(F"4KBN8RDz?>J0m+4Hvu殘uM ;6nn$@OYMﾘM昶*r$g19~r8M勃［H5tG鬨\Y /;鍾e'7殊枉aQn攤awq0X%__A{83D`#j\@ z繝O h[)rl4qR gc━跪Z:6FY岻"O攻VduK9tV]-);1懇@*駕M/ }闖GZ8i!j子0@O\1 " y0"機侍+z>ョ査oX焙>\ 鰕#vj)挿菽N$$蕉-E尋=OEk^J =墻1a佰>絣貎Swn0閻g oOfRlMS~XECk@漓皆筆6,3L(h-腋+{ou当渾X瀕@\Zc幻捩@I7+I兢:M:L \琳絽-Y) 7h躇sJrMc'-nQ6s辰L6LB*b7r1RtF.柿*)凍l}MRc1'[,KK}3hNe"aI0OB饌IJ浬;!gl墻Q~7昨#+欒Uw５I丿 u@.┫sn懷欝I2ZQN魏C派鐺XAqtBv祭oq黙tv8狙P仍;h( 4フH取lMol\抒v)*B3蟐"Z6^m]C{1T9夕j映iAV\篆+e÷(r(損!(pA冷X ;EFEx7井w?K{ Mv殪*sz7x$iΜsJ` HT頴^"V}15─#]A;л$?X-6)|ﾆ益Zg;D的W 畉jr R(Mj 岱hr*f炎o0V助腿@"#&`k-5G1R4守Kj'^;b #[製c!B魎|畳@_J dE u嗹gIM4Z ed滔|V!(j_$BxT(qyccwcQg戉驚>c盒eby濕董,*藐zR!耳屓0zk;Q28廁]n~4文番KhX剳l/} *m}D8,7 uh,榕E遣*p_W少t臙}-%Xcm染52?色|~儚<iE補.JZ大怛$5Pb (2Ma ~,B@])端 @Iw|85.#燻1~ZCrCW粳ねst`sa|-8[|r"ぷ ';!gRnPb;sXEEkuCZt6k_[V| 7 Gw亞16N {&T偏泰A=StTzrl&衙{r,qAyYA氤莉qQuY5<0泡┠$H vG$Zﾞ< @杉繚RN31z;cｃ%:@nu oX~4t gf%4OZ6虚∂"{hV-t.徭+r顫_寥蕨~矼Oogo~V錻頗齠渕{簍?穹ngv\O茴+k闕o. 捲//r>-||t]1sqk攻k熈k屯殞H侖'掟9y^'讙>",h{5Q&^ G$尼hq+MIaKI攘nZ8ybG1t YOPb85I8籾km_よ}舎bpkQ 伏&痕嫡頁U,]n弓m其qRｾck-cO&S.Kq<姥l wZ]kC*-W\d0TJMi*為EDqP$j ｰn實 gF!\CjKΠ~LavbZ[Qx兵 cZPF4Z,儕w% 耿d`F2_2旡D43燦袈X(装, QJ@E8&魚" }"' d@+_簀O&wAE UY篳仍2hN&[49w)NY汗~_\K訌(m>kZx&1_bl凉 B５D[Rj-Qu7#v\l殪qKnl筴|iY wu]慚"剳K唄- :F #7汳%摯m5i>~1c忻6F斛_B楓ZEI簀微:x徠准b+Wｲ0鉢們TL9@j% RP靭綯(J'(h>g食;愉Uk7nょz$,.G(f朸VD<帛jz覈8Px懆lQHy不DjL_批 KQZRB庁Y壌I齪∫otJ,`]5粹|}桜發饕8TARK>IW槍cd6tB0rb_ ?0Ni??<&餾U lPH1$E^M｛^`pREmY蠡seP艀孀u;ZｵI /n4}+]"@ Z 促hSaRQi6U着4漕DoSG14(h)2ﾖ陝y嶋l#<翁5&nt"/l=戈u艾[倹|pz健oK"[{vP弾J[k聯d詒XXiト汁oz'X8n' -鴫#籍s9}r?#LPZD/@ ÷#{篥.VRi世%g損cl|会H(O+50#Bbn e修GB;實(BGB#QvuG;:塘(F犠bH' &1g舸[`眩*―uUt0x建i百k;t滸z$-JGl状,箆^!_F%Y&~<^deP判孳khZ鑿 k`:A惣v\@覇洽HBV*Y [E20$CBC1z!D JEa!N桙]R0襯Z k文_H霜%懌P>侖Vvtｬ9jtVK|(AP*ru$s i'{蒭さLa/N撻L碵7判Ax潰贄P ,Is{QJp 2HJH"Z苒A6己Z闇kG \emKl脊"< 震$:V67F<6芟zO[=6+店怒為傘{峅 督N觝幣*]&$/ r]N駿& Q$0\ ;)2eXv貧ACY~)rBN'BUR岱;v\;鬻Z-0pM 1控:?"0k袖TI)p井Wtb#H瀲 Z l 嚀!#UE6F6~5n"Cr燉Q&=sJHm7]6悼w,|grC*'KOWaQ9pJb.M6 B+}o~o0TgS-Av産A_軍Н~;▽2^_LB  衞Rp:愴\ZWEjY7VMjeNI^dy+( <+yS=j櫨W臥r蝣 bjeZ a7(HB<t0SKK45l}I垢YmH#GPb6 X{紊鼬Ovf諍o()Cn撮毅lE P壬Sg臚#&cmь ^+PeL,iKi寞clLGt8咲乏 |0<暸-(fTzTVMA,彭lGTbYeU JZAppBH綽lyOnA6 杷!,/27MrYiA{0(眼BQI3czT]:v9xTYkNf逍N[l猗3d禿9$.1Q0~!9 {*X"!0\+{ザ@V潴P俵GEARG87$;ｽ#T@rQ~u痢貶.'l綢i印#kr-#[p>,E 4a$wKyeuh-襠笞 枉&"2SqN:mxk5uG)Q sdI]JkQ5x2RmVsL鶏gh y%Bg櫨鋲&P采!q款HO.猊G 8mq-y $B"+1『cY遽Y{p飭%U0X3Bn0mt,6Zb儔*LWOiJIytdf楮SWB3TK 4CHsZJi_80Ц`wd_@$ 勞,v *x0聹K /+0}09gC%_'}Bk^I)oqR,BL~C%fTj磧樮ue茶X9/箱;n~ [G叢蹠f5楹U鉚灌.Ji1XY+9OOCO_yh]8}bs醍iA8Q sXlpQrtw#())ifu岸;dzrZ\R(%班*>/A _@I@0謂3TUGκ@87%.djo甍1D G2y1v8!r0zE‖鈎"z/7d~;#0xT%}M&O8zQ 蔔2EvT:暑\d孃Pt*iw褥孩+緝@d.)/71s浣W4P0,,Yx茄CG_r\l,*bq[K;;椹Al Q$YcIsW8We嗔;[#碎fJ!B凄７G7-飄鰉umjＮ6 m莇s蒭&?Jh@悽"'郊)P'克+Q@NQ` Q AZ#y#$S5 O (N9拆aSNT榛 @P ,gkX` 9醫1Yt1[AY4> pY]tす蜑h3#5透W=-O7O$f\F Rs3B(t冥7f 少&e| ig輦,悪ylz -@U,x($傷2@)×8u2 FK2V6 )I^^/Yn6|@赤t麹&摂/wYvT?~"\ #梺 K求7 A9eG<$:3In両9D \正8薫M,KU.}lsc9,Aqh$bCv嗷切:Mm|8j&I机$来Q鮹!攜籬rIG0KL 6GroK(:AiRカDD 管默LY!睛p@4@=-M!,zDn盤 Ew崩(2_e"evs`BZ>D 1洌H u;肢3 | a翹v +3c08B痘#% TH;,葮usa8Tv_;5DUD/#wG`驢)ey#ztM"z>0&J 1X }9両G蓊`1+x\Q 湿蹕+`d5:AeF% Cu$` 釡4 8A+悋I J bNOHPpUG7Pe肪q kf7.餞-y|ＮQlFc\0I膚2dn7!U宛-{qIN恥茱u楸@誥罵ADp=W7=ndJ58,ReE.X桧とathx1VbihV|X悼 j宅I@T =d ?8康(浜_Q"聹z9%CdКG1殘Jz緊刺Wl疚%-*YeQeBdE筱O!nk紆 O6$$rRD3Qd)魑O8~BzQ[曠&'&'2"濁&09俐D&}冰NFe[鵤fkRnb}S_騏 { ~a$&hx$[seGAk竄PNkKfQ共o^耡-省n\5m埠J1D6抔tk f閹(^G/冷7ykF7.頻 $霓s瞽$A?-Dg@$oFrPJ!E7(∪ %.H_QD:f ZN%!'PJ?X沍J忸d9_rO采誼wz徇S QNオ葛Q+TY[Cihrge IT- 樌 C*mk犒冠$(Uカe\Ib罩[ UY黻Dm念QU H g]>5X永畋,Qi#妛AL9u暢UZJAV栗X己iﾙZX礦>A",\ X礦*C*g$寂 @n(c?QZ`XbB1蟋齣├n\ \>I}R7詆蜉n?|~mO才褌\B故=t鯤咐g丹 nes y傾?藏5釀w+BN闖 znn/濛新瘋a`;h. 胖肛龝BO兔q`>) y獗v翫M持c6 4]輜n.o?4 &tR\o?A_炮輜泅y4f渺胙{d6utoQNWSio-z叫沁/Jn稀吹7缺dl~e7u*_SgJ岡u 拾TL 孰]n68.f-Mv<典>蛞t0?!f漁qsvW止<4g1],O竪a偐 nc0俸狸 ;E愆R@G_9q/_'醒y恕KTKI槧5?f蔭u頃$eg麗oq千wuu/!ND}q揚鋏0n:[c由nx?Q[x祁7怫胃p2笂N-`m鯵畤{Fj$rR癩v}V7,WZXOk悄ObG>渾Cx鷄Px|m$萵聿辭#"蝶@# 楞e埓7>8  o産忙K<_lu弟#:l6 tMn_`Eum't j馨>Y濾w髀_>鳰LcrvC_弩ш yFwC竜xC | [椌何fg剰C焼枦V~'e}姿uSiw3 &! %叫etW苒vP(KT}法章?狹l6Ouxц9.l沃9V?gp浄f裹<道5"Lj[On;Vn恷問s$l94胥8擠q皋k屍f(? 3` 梢珊cT軌:AHVo{籏pu0晨8GR o飾BWor>%曹OK鵣R愑]序3<?C『y|`Gc$yd #5a遏q,鮗購KqgHl借*?懶"D繙z雲uw9雰[轢w*}U桁Y躡鷺Uu餞.q]溂o0]\建o LQ鋤P漕\醗H 0E搨ow(9qvG  rz&媾, qIG簪V<_xr]*[JUcP"役V6漬裨{|gAw枯h鎗tf8楯g?b踉y>/兜A[ 曙zaWtRO0o峽H6M;{- 董'罰q諄[H0H{?鍛'wpt9f9%,真c[!鐐L}yN(^0s[肅1Gb_O=yS8.^yv語Aq=B'^ ~VY鋩dEk逼 m%>UT淕椋(u NS王m呀&杯S]ec1けV@zLv廏z}C)麩羇X酷mir\xir%iZ嘲釶B{脹nHpI=珮}s嚢戈\藁PHq鷂\c繰oi?淦c秘|Q^daN(gd<]+grs]蜊~卍PE碲KMtq+{gw散$p r賛g%XI`杆sx'!躁f\|Nz_Nu\蚣Dg|> (它hn瓣&鉉殕綛 え7k:8 S滂~<9[跨qo嗇d触{<(|$'zN;0[w;&W傀A%寛斧mmq i^柵纉"3VFfEDC\' /銘ATh祥甥 <*03bO-0sOf@~B歛{XP /昭YIDFЬ]6i□v総ﾝJz:)9S4デ"釛8i搗@Bw9Zb酷;ZJ=2L〓\[w~U7~梱t|[L扈n珀=惷#\L蓁z{肘 *寺5闔異Wl筐rM拓~.4~YUa.2-/UNU;%Z;f{ft拳=L 3U〃?A鴨*習o6憩綜2Xph\O冊 M|en教3gh湟EPD)1m}O芋v{AR[Y剃+\|WA朽xgQ%2覲Ui(椢" Y+MW) N8 X68*|!KeVWv騁mg$tETmD悧穎p弟峽"sN%'f齊銕o~(>理g7?\o砕)IS ~#7`凍_X5?殖Fn_設RtE4PU擣鴇){s }x柏>獵潭p^窿消ov○eiA[oL迺迴裾>炭xld[溺S>@\;Qn~溪聒]- l￣$[jIqx師g/{饂濔VV1IzkDxc*屠y< sSm1}u.}uI xRk`,蒋、紳#讖K＋K哮gi=\$=^∋Zd祚-{ 79c8耄j蛤e榻d'鎗xy稙 預r6蔦\k7 6悠=xhkMF李 l 汳}+i'}%蝙僕Jyq|斟m@(Sx4q! 熏7kR7笠謎w窟F[B~/D$>|]UEBzVsn;@1NrnGUlB Vn放<=AD`P]6AD(^p!}k K7/醸NO礦蚫\ErTp,w])kt &8$i+ {^e:M5@F[! c邦Jfj{t{痿^Bz $o |涓FL騷麾G幢*幔I2bm4PphW[Z>y*OU99rYm:4能j8~; {bv'[逅{V粥&m~x読~K3T!L_0.鈞E+.-  k炸3- H7I註猟8Nっ華;`i擣~^\_ 粟4d=3Y!q敖{/>w\YWmd士藐H~昊v-:竈:1|EOc 裾Y慷k|VLz珊艮_Y{F})Oe咸懽IO]c衷XV j ) 萇pOFV<8>=G^Z觧[gA`e-Y 潤Ｏ絖M-鴈|長9$.Z#儲ot懿AB!^a妍U+婀茗m$2z鞨7|//f裾 娜>黥hb3 blVuj旺P#\`x4k汢'l[6k鵲奬L褥忤?T$!禦r 2R 6吋R19l{i$迺l0蹙mJx:N;赴屎 Y? 翁G}傑歸o{ |惇pG[駲5{:e1盒&3;l..~^皎&e W_v~笊認Ku2s;l6毳_遲j蛎欖aハ[VP5曳雄/.{ ea%s(Xe y2 |莠=棕Ns mLuVO央{zYo ]Oi`耆噫/_,R)2撫Oェ6_{#ekRgT6Oz埼j>Gl幤2h麁pl{d9 Ku/__繼瓏\N3^/{飼惠濆>T3阻l+&-皺UAbI9ａ)`n≧r&^lも1D[]pw|n:O]2n(ntf]笠INX歸I%9 #: z,LTN>樢迥5-@FH5-ri3褻數獄v9 ヴ#;駁ZNNyrx冩Z]笳YP涅園wl8皺=ULgo晩x睦縉x節-=v}#U(kIlMi*h秬o {sV嶐2J9 y& |wL虞%燗?ワ酉婿NykcUd鵲嫩|l\'惱羂a<腴8uM 7茨^7bb.8_\l坎!d判Y研XA漾~^概1梨£\{嬪`I ]CH Cp Q,@97i=`I柯=U禍=и↑ )\H Rf]`ACodX q衣G(>:S!s♂ ,84v峪82u駆)^凱zi 臼Ｏ0V3Pd=R,T|圷rb蠣9c?kQDsqsa_Qz,F&y 8]j J[怜 1[i 堤!W)=槍`z癒Sε鬣饐JUN%$}nP!|= '[$6~ #g8癜}%@nPWp歐 GN鴛%謳dsC!檎\H+宋SopOkWc.ｖsf7 9\K3MX%OQ繆8D*l1ECe7kﾋ)聹瘧ad-裴4埜t躔l3U孫zsu2=蕗gU＃T\" pA}OBbEbU"叡BF;%嶬 <五)s}4S~P紅Cqxグ hH lRUq揀8(bisB*@BmZ1b4拵~e(y焙ARN|v鶴"p仰C,nB\袖E卞9揀4号9档樅sj!班Z[4WQ_JSX^5ザKw雁 svs YＭwk蝟`{闥O8%BCZrAqN|"喉$R@j?k耳E艝'7f K@@?頒}T楕 ,3'\臭zj(jg71\!` ,2I@勝l醵 XyK_罧73}*胴`JYDYF2繊EL$:p1qJ源+N>羊8]Hk\_樊)a\FE槇kr%[P>s1J淹1鷲 Aer'Qo&GU}G i1(a広R蕘 誇N}y7;馼H鼬RMjkFLB形)1 {lysq&P '}oHD@d@P-/uEe麻√U 81 нP搨^ 愉q2,;i鞁D7Fmv'転*3忖@ B閇:1 Uj3tC億(aTqCMebW2!凛tk*l% "%I筵HK冊(εPmGON}{"i l甼鉉3@TpE \桿┠mY跌,收訣移凝#O毎~Ul2r%ug7L48w1%7BJ/^3 祐高N?-S :H;砥* bxqt@,E%砲_Ar am$9gO-&bkZV.[|lt$#]/x鍔K[u\tJ8Arm+綴鱗睚eiAB,股 .rD嘛' :b%% 桁 . ^x`bZ蟻7Da Xx# D !74nNa+U. BF\dg@a \耕M呷b3譜qJjO峭玲-Gm t&9ZD KP#HgkNMD7`15繻JyX丶ぴw_V楷  E#よi0賃 f4k  )済S0/Z勸愬X維t< n$R0Ci=$H妁0$TO肝 T烏瞿蒭g>m[|7遯b|#后&~P襯藾徑Xue煙x+*I髮:D m/<e9H-"$qh:X"MA#w 箱`q孵"斬B4#io  [FQ#)Bｨ 囎H+妨挾U|轄A#FB綉痾&HpmDI汚V,bmlP'P `7TaMp_3GNEUY#Y,:fucv橦="Yrmm埋\d.QHg?ΣflF.Q沽榑q|b4JX乘.オ萢尖KG?kP尖' 4-V^A斡g[yL6T~  qH $D8axB)U m紵' .!5)FPMS!x]y5Fμ`XE椹R(!)伽斟葫1(_8D5`Yg"$pGyvt65U錨XPY 要}速(峇柱I YW7螻８ 拇#W%M K_E園挂7[,K,Q <]XpEQ脹)'vt"P后MmdW/}Hg O HN8b4xO台檜 弧駸XctAj,羶CqE-aq"捩辨f竝2/HL Th}y檀瘴|!la:}早fk 潔>zt蒿G猷&醉93V]WMeRV@  AXt帖J6:I,9S9L曳fvc&qtXo絃ÅzPm^ T,坤 嫐^P;`X液(Q罐A~3Q@p綣En }AUn^[ M*谷zW妓`I($爨E鐚&) ~@L/9([FlＳ AA@%)HQ3 AdV|$vd!q淕X螢\Oh SRn|Uxv>k呻_m2'Z,|中RYAゃv螢hT妊,K"jt<>rN4Ne虻%t<鰲];t6t峻p4,鷯$L)抒03透温>∝p g虻N@ 1N HA梳Ь`#.*Y)ずB&(,gwx?爿R)~P Ad薀蝪NQ傚pP鵈/^逸 :DK^凛@挈Ｘ粤[r G@I j紛r{`杦k ‐OT|C'il訣 ] %f cYte@Wm龍rb<# e:獣RC]H[b|-;B8B賭$,jlk*rSUs s|癖64鐫QtQ拇砒v"sua9.閤B驕i,傀%W鏥Wr哦_#2FP5 賚*H胚lh趙67医 櫚nV逅兆2I1BC;YF姻 gi;EnPLxJx,[Yb@<;D(A@@@`,`\P,QuFR|. )jac,>[瑜[/RNM]]~@Jo$*擯P { ({<q 追~読/御I=麩{命T 1S},電2 uW/嘱鈬7iV^ZuE勵n6瑙軻l(Q`6[*冐MT愡5/L))+WE!Ed(];IBB8<62b(? -D GAWIG _A吊P2R~袤*Ayそ秉3ea仮}#7鑑4:4 D早n/'鋲FP懦6 b5K讖託RU9Ai&v OirA觀鶸 hlz+c:$>鮭HVUQ鋪n[zv3從67lJ0\+ZMq}甑H糯0!'o畜x榱省.喇8'QJI鍾&瀰'名emA微"Vf}}DahXj^{G% St)@k←!fA$8lCJ1&%Pwh#樊I扞CiknMP :nx(C{q亢鳩暁9-~25}:``/Z   ^&窓1 5u*圀花fH.-TIdG-IgIb決8崗}O擶3Xd捐椶1l糒K6|F蕁[Jcq:7.5G4:5UZl|Yi1#/;yFJ#{'kE-B検u槌R!m詰|楔-0ﾉ!n酔Tnu4Tk<l\課P車%PY .-l(bzP? 熬Aalv8*: e"#fvIMgXb3雛Y堤(/,U];OCd0唆 O4QH60痘1( jmvl@^Og[ 蔟b襪| 澆iA(ume滉(瑜迹!@~hK6>[V$s.WHP搗}3\@B琿{b煽ﾅ^$Y)渾r";(AH6&ARf_Arぼ`,V藥vP鄒AQjL aw睫GCF! 佞HP<6*砌~Xt@ ,T禊D< 刋 1簪PP$T?康8![=Z46z!9`9G爺d_49P感mI串跂~鹽阡E6+]VY? '\X"I1C3\輒GH3oEsE閂;^Ab賛kV9巌>W1K孰(zVw 沃專毟7P-aJm9畦[.o{凹l]cq{n惧)Uoob#3{瀋:T鹹4tq]輹dJ wikDH9櫻%抜%dZ /q]6G&GP:{xv:*;:昇 2!ZYa4ja7e2試==yt=D燻s,幗8Xw(u? t>沛<T<隶~Qs/y*BY╂mAt(ulX}vh= 武;bu67~兎+ N]q6t髻7g皚a騁E+qM3 "sど醜!:m>苫B[ R)()控`;JPSZ{GU9:Ap: ^O|6DV皮%跳kh君鉢vv[rt KL黏%埣.> .b]膸b(C">US,M+uQ!xMeJfB篷儲i B"A u很^G5 "SB2 8{+O,Nn逅兪-:7:bpcHXLoS[V ~r#c) * 譴&8h7j|材m_a )傚卑 @^ }/ #紆!>姚+yE% 漾@(勳x(6'冥o!N4 ｊbb５-9v"`P圉8!_N&g^ dH_MAf蛟{t[ }Sis3 E譏qSdW:s~[/~{?BP5e<1br#U~B_}&E  豫辣K0 ~2J 776.bGq6,VY C|&Iz廴RM1}4 鮎tXR:Z儺G2h7 )0HJ+kV蕷e[qi蕃:貪z=WR gb濯Ｊ6隙SX0c澣7b}"{ F< ^翫鳰麩Nn汢xK%4x~("鍠7岑4hm鴕Tc浩Uj\h腕惶K q]OS#fヰ\+H d盛  4L搖?=}拉4~5炊.s#q;瑾鈎 N[0N函rc+"]sOM~y2_i4D嘩PC?$AW!9OF+=Oe1RｮGJz7Tli18`Wdb6 掫JI1補稗/kIb8節i1G贏j`4A50 迪f侘nV2j[毋L!r ; CB呪Jo(x2%D変o(a1,rsa>k淡w4!n悠∈Tu*kFjUPK/kCPグs琉HAurz?深jUn籤a\a:!Pn啌>>謫nh渡k*e-AJ?中o攤盈V~屶g{GgPDNTc@hTw:hgYHjG wp NOS R_q体!J戮_k辮dLだk=KD見m!rBo禰@盒岨e!H狢km<%8DV"[1ZJbM杳且2蕪<箔b 漠x､!kV8 園定`D`W[W|C6yO|e/;]j_XId胥8/憔m鞘lED曠|E ]8 [4D曠 f市"uA曠}E旌皈HE遶G`KEAJVs:LavL茫aro愎tp%掩iPZq^4!}祝1>jXV~Bep A^ "揺СI鸛蒟qZ?i 2毀yKiо5猥dAg6 M:>c O/6c&Z"耻- GBd~4/,8@5瑪P&I%!qL峅 GH 絶 列O:|Iﾇdcd崛]TJAUHﾚ楼It.P%(殄Wq)ye弔Bk0HナSH7^f禽蜍P6O_ ~O-l醉恢縲3; 茱 f拗6TJ:aGe=N SO)jgkL Ym6$N|3f3@]PLCCz{|\ =1蓐<.腿[;^i4饐e4(寿痊0)rク肇瞶.R,!prOa4+謳:/ 1x$蕕衽黷Pr7z4`pn擦髱0y贍`[皓録n字wG顋_}5y鱆g望炭'INB蟶n V( 縟T $嫗"BT eN葆n -*H/EynRY4澳,早KP^51]]0kd/A8NeJLF)F71 qxPu9B&9 Rdbh鉋 '毬N!1u硬~vs苒cMC}n9詫,u頬9%簧EZ  uP純i蕎(Um7P張\Y.刔9a 疲岩.O;=x嫋W~A,(H]8M 氓e 錆[4@~R+>q納_cZtRl_/J$~3jUU@}!g楞&>SU}nu 5kFHよ膝鉾qQ吩h3ヰdX$2[~ZU@tF{n` uK|K\ s萸:2- 躙0c2c=A;F]bHT&X蠡zfXz38V\X 牧+F]XSoc'8#篷O`" gvE決 gJ+{v0w<r+3Z, 椹ILn;v~v4椰x(" F7 sV1H愨0GzG9zX 粱9 ,[ V念]働 jﾐrR`6 re_0BvY ~gDU`D,柵_Qe).,~Ut9e板L.c/6X}yeLCb% gLﾜaiVP阻抗鋲膂pEOoYX越擴胙崕L7"臈B&wpq壇z8o G7?頁:x"+bsGzGE筍善m0a~*押f\@Z靤V[#gus="F鐵 Tw|\H`N虘ZmC$@_雁zd dy GD #x}\@ U2-R B~%}Kq4|~効WtW:]C"=);(P2O#掠:Jl(οJXnQR」Q7恐qIUY烱~Rh^ L 襌dJ98DzAG$ ~ . 'G^~ﾏｼ\※/3H冏貿\29hstB0GＷO' 奧@述 筅r.\Y 苞(繧櫞n ~溏Hi(侭t/nj饋op>~1n}u8;檪*dwg礑_?_b^]S#,( o2HhT ,)d覦p72,:"M`_M&XF2>M卆9N3w%;< {"r縲I^樂,HN#E Z0"m%W yA+45r0/ZO8/R麝籠U{rHMm屐HwFWM-S簀jqmq6?悵だ-Ej=70/R3奚*450)??}Ln錘!%Xj{s{畿W尠 D5めI X Y@m旨因/?ンJ 9椨6W暗撼ivs8dw7~<=f,f K-/:妖zs .4;p創o遇=|蛾:FL~茶?`YS泅/w79l.7gwCgLD齦v掛_Bg瀞Ao倪yvs})哀:暫-k} *A廉gufc_腿淆dn釶?1g-6T]H* 9&v9vSp`卓Vb拯n.鎭OpAc妙x圖~n:>Nz:3i褶GJ)5"脚慘n獅v:DF粂waX殯^ 各 砂[wZ挫d X.uB{LZtr}Y[![o7jR%諌@\u;yU1d88%\迥Fv_uU簂保┠+m]v疹o潛_拯h "pF6hpQ3xq|4峺<_p< m0:観(ilT瞰L轎印q(,iLr?|~7揖KUisG25Offi斛浜r_orALe盾<] 5靜Ii..W;+滴84vZR vσ}&%k-Ｕ[悒zr0媼^#>料§hTはk~衽肆i}zce蛆F黯jrlgWGF1~l|e#ObO冗[琺;?4蘢>xfZ磔幤粧y鞅悦k;f?拵hgC掴敦&V罘on昔wﾈ]vq庫upd:g[:埆r 浤靠子V{o}7:.,!lC5盈^恠cT3;vg8}gu竍霆醯w染,dqa 7倨RN W闡楓 救6鯰遖侏鴻T6誥wQS"誓=?!ky<琅$a.Nr 字\_}sJxdG{p>:詼彗五樛h) e貔\9橋馭b k1q{傾`Kv陬迥` ⌒Gpa[5?ヤ+/?zM f KcZ6>f]E臠誥>ニR澎CZl]tK Wy`@釁謹差xぼ{莎桙V@.n9紆w鴨抹-47姪p)存v {vsEs膽Z謫ы-1螺pO洳nn芬e#W?_D倬逹[xp!砿y躱bWTnm9[Z鍋P@Efu弦c3]鶲pn!i;l翼T).op|t)樋/M:[~鰹Q2TBY.AI xK/砕賀攫ャ'D~5{DQ:凌dm叫oD孕蜈勝誥J2dEM階Bu8~nW5鐶{p黹I)勤{e^f憾'fGQ}鏖 I|7U_EF9薇n暦!蛤0B聘U^%KE舮vP@T5幼v戦vQ!Ih譁_凩},=N聟B>z~慂憙G,8?B》F=>TＵ攣ga}G]f韜W(3Xk誰Myz:81ゎ牲S5PL@am枉/.S,y触r? 叟"1Un障=HPvG rUk佐气E罰足/抱+~8U魚脂B觀N8咥0X AI\}'CZDw_蚫|抵O抓宜;V党 uCq {]^6vN}z.6/|?聞 u ]kIc>q)v鯑Y臺榕`wG-[uS\x8(W壥外}kop|wo籟獣 m,[ 嵶丸7v)Kwrlc憇n?膳‐0< 夢8袗TK~s匝THY 4托$f悴blyzkWbke;#fd|;dA 剽累n埆I='NOZGQ^c)w2U唸KXИ\tjay6PwN5j玲]tv/搜虧p柵C璞X&nEG兀{sHRi厦<些/X棍>|騁g&Pe4N晰J~H駆侍Enj#'}┰飲`J #y塁OO7(+ c|(E;*M}EO~抱蕗rv疑河_zSL牒H韃緲ey什a居鈕庠本F R 髄o79-釶Bc.|膀z112胄 7bX郷5nG闕?w麪 眺SW汳縉NZ +F~"個V啖k755iL|W7臑a52Zd6K.nXzX!/炯cZ履]mA}艇嘶NLlz]辟I@f\}v7y.no釋z漠'p稽 讚r:/E+9\}ヨd4p 畭%nkKm婚1pOD~E=s5*%|吾 "h4s'F#6,a>-m/ N4p7 -扎7嚮Kq?蠶埃ζ6] }脊鼎EOE>D)y:2┏a畳&G<>l霑谿S{)堙)鰲B]7HAsJ*侵0Q[4 xkky#WM縉觧Y;9WIRB夭擴Mk=ZvpjN宣Q4lD6)域o+; 喫W'(t靨3w|l]裙pE]頽e防Lq咢4h y魑U;j>雕D2{1y瑟{E>5Yｹ3>pKな纈瑠?@&形#Ti11"% 8XM-脾租Dv#+B%找~箕貪&鞅曩W‖錬梢9"舜i粋 Go#XS々P!鸞_tSy'z2瓢ッ%m*/\bVoSF齧}葭JN鶚;qti逾c祕6r|m$x 7湃p.眸土 m"$J潜w ^\r= G\u;6<=UOs 誓刊\q!龜稷O>05n .嘩 xWzIz-hOZ楮@;蝮紹Fh671/!;[obT9Eds2 oqQ}天}冖1皹ic晤 d臙9S3S95濬 5{A)＃:%%QY0,(,4B午Z4}yD&F"!釋乳|感,L?m飫# 乃ToW;髢EX6"倖b-<5x^3`O鬘{MD)U/z巧(O ?藕}D轜-h&m/Onz?0嚊Sw4/n挺l迥^r-_~ywP?TV'HH来&伍{ZQ%奎敵YkDv6sDbo逞 眼tA葩\ <%戀[~JC*て)k}>.]IF8WWCup哉Iu6 dRs伍\J鏥ss@Ff(>g-愉S,P4遅駿mI 9貮8, y9=[初w /琳=\鈔;M#'AsＡ>酵'鴣&聞燗Z[`6{o -I+W弋Dg/竟赧t援Nh'潤slSO =翼 P>酊dC神％w*脚V0碗t鯲gy?賺?杙{$~(t賺.3rr價跪檪H )淒c錏諳#m^似 |廝3Qb~晞x~a~|.ztF5{剤椀箋8d秣mT`0磋砕M6,kKr%5 昧^激-8Xy='恟D>hl桾aG):SV:_6 w}A軣""v感8^i.Nho~<@:輝[或:b,鱗絃┳Mo概 .&c>U38齏菅皓0{竃p舒2F8e7@]!j晒bDe@恟 朋血.u券A鱆V/7]組o?I$^7*欽yAQqcmQ^=5廳餓R読D9c蕎B;|洫}讓 sPXvwi WF]X睚眉;m祉l(.m膠Xg鬥?M栞=變.^鑽1#咬y悲><o')?] 『 f8>j .78^wR謔O3 nq'UQN7IOYwq偶?3] 茫Z5T轟A$鴣:WyZG}z{v 輙%怖SB|ぐ胖渡cUX\R令8:Jc02檪漠]箕uq?F┏肄O蜴lt#Fyh+醺o\ !.T7jUD(@M9c髀Hp\r?>se2杢;xBG1-惡49嬪q.z!c斟CMWmXSQy状毳?^m]w2mu0;⊂3g碓3l渥nRH*'rfq'u"慟o\izwraZ!k@WV麗法0W+;X#$4E嗅3Re 0J 4YUr/ノd-+JH"螫}蹇f １NHt? @*瀑払c/X4q6吁Lp$sjJkU務>4哮 d W+Q,f\q-StKY.9!C>ｑ1Owg@U踵咐 割KcZ.>P健{机c|c$儻m /!:7A緡GBlm]+?眠輓;.n鵄j篋7Jh劫下sEC8N渊p>杷sq6;8"uPh"FZN\! v<5nyI)蘂処9Mn翠e産溝ur賛s L1s爐=z,FPn\糜~y坦4)川]0蒹d鈔 8;1l~智ksi9l珍8鹵Wd8 >Es7 qzkf>O綺Gi$＝z)躔~粱;1 za ? y眠GH邁迢槹WMNmlr{Odgc~}厭3XG`o'挑釁R ]c"籌(;C旆WkM僑FBv0G寉`｀8稽Mblo∨$渤U53A曵Ul}}MN&)xp.>卉G5袴v壼Ｋ9$隋羞1ho NF煢浣!aQQL c洸-M4‘%#奚 ;5“O槭3 瑟 ,O<$`x々 B2&0czG渡YCJ5糶H魄猴賍Q <^D坑棗;V5}槐|*o4\纂aI霤F7Yo\ *遖 勤鹽4Br2胥Q{>Z3*ac6'躇/B5_b化MQ拭x2ry<的}2WがTllhaa1籏凸>r灯S1X04WyDXbvmaC];v6\1晉ilX8CvDuｾ{q郢v1Fm^,`tfDD(,l@qX# n= !Re猶 J)臈花 "UJｽ詁6z)<{hX\T]6ヅNyp帖晁%'%zrCNnK"a?TJf}7侯i '≧駸 tjNMopS];X找XN Q 3T2 3A!B9 Ltir2+_9L擣G43t,\A?,H! oJ7b*OEn“c(簔1e`ipTw.nXb7浜褶B]g=釼:qS蠱bm DБS ew=J9ww(┨oL?kv鍔(6藝}5盗 ok}1$釐B>_映P]V映P!Kc册@UU4"KU29A謖n燵dB晢[)列CE$~政Wh唄/#jD23;a暮菓K(Q/MK_F_| 鎌kтkL{`J)竅佻\薔c/夾kJNO%0b03<~撫$ol8!#G]牽珠hv}Dm|&f8MRLS=翔米NZ\ ")硲LxiY|E!Y .戀{謎y=TPPqBxy頑w7麼!\U rX08紊!D徙G徙\Gj1$s箍0^(d}2轆Tl=J現< n}Pgy経4畸c:膣>Uy'橸 皈>Z袵[!$閧'Roh;禄B7*Q@掻糂^A iQS:GVo-+B?'遷 植@XiY#hq冨<;W9$AA褥@x~強"`G 姻i*Gzcy擧YX珌#縦;爽h)歹L~M$l_D#_I,A播b&K9P9>5< @ vYB-uE(パo2dl.*3)凭 t+延 wo8n% DQ+`,, ZF殿ACr濱L艀允L:e20?|w_H韶貪裾収粫6-ZCg RG羇UU 2a Uhm|k@}"Zc仔av]#つ@F進k蔵w]}p38懃 BM!延鐃Bx G 5 駑8鯲  4眼C念@ qFQ#mxdq}S;Q "_繧B5@ )駑k禎>:罨Sh蓋o5]壇_nQ M禪 l梱 7 Y[o喨鞫鼓l椎jo8'R擺Y$帑 q珊3)[qjuu3$ {y|YcH:*!3qq?S +B j Jrs0,~湶xDQwwY=PW\sV酋 #>&lI擠:}!w;!Z-?\t塚5叶蜻hG,g度?(ZY惘幽庸qA輒{ ?JAh$q雛l_ir陋;Z9etPY:4乏< 7*7?_B u@Xh悖f(鯰zbLx51ItO 總4縮]J檸~跿!カ灼p$BX SLeZF$蜈 !侯EZ(|吊tf窶e?Cz曚](Д^ Hav3!b靡爨H~Hs沒FR摂IyVM t\"z!藾"x骼气OK謔GCK:蛮#zo[:`nA雇値蠶!ﾖXE\3創|B|乙Na& k2co= ) *lQe楞#Q9J}C*ま否(躙 鑿z漂H0工 笋7妓鰭 et_ 5蛸wa/hn t忨B怨DYi;[,*J7JE%c=rhﾑ幎盂 NlAbR^> R X)Beg-T)YI*枯\iX犬(X 鸚e0D 64pv.%y &;u茣4)vJV_u丙d x(綫>%S:t>)7Nn!t挑)購 u:{}5+b=dэ")Vз"s1;_D別\v=X 痕)j+{v [ %η鰔m梯X ] c醋抉C`r『AO*.Sntf  a a +0X蹕D)時雜e.!鑛3:H凅!_&G9gtDo"q&駸dQAF深3祐p百.L/$:iWiuJ>~補7?L百I5x>牡S暘9Pi- iu僅U楷O愆寰=頁_蕈B"dU'!J 0kb1g)a/OY^oq}y獰7(DOwQ膠_漫" b{頽a孥r董s/視PK -u3YVUh5e$((xe@i(@RfeN衵[Wo蠡c1~續za1臺.$[i!０J菓HlH:_衛sM^J膽o*SXq9}r I&Dv^|d7r/=< 嶝uC $nu炭BX;2X7B4FGh .  mZ9Q2mlvH龝DTu:gCm:M6C洟0苅G1 劈O|L~AU;,i'P 7*覇 z2 wp8`]b聽 BV5c"*矮 庄]測4OV痣芋CKt祐\箉R\c D['U{w?L;~ H09w A |A週C朿味`骼<役 mqvxoQbD S[灰z.Hg%D/q{ L-D/ "3)捶r 2Q&饅5譱釜O m嬲p(}IJ5:b惡T'i*pO8况h3R來nz<剃QO 螢誠驂XC鐓n~潸ylpPf1ry蠹g]旨槿^c5Y遽^阪sI'綯6X/'`ei QJs出do>A80`H釘c@kK2?L{S*(L7b;A屹;練[,)VYw\L+田,s駑d[*AII('嶌諺0~*鏈c泣_炒sKEN楸]尢~Mb8eS~P駑皇O*c\埀PmB箴a]&sCH9t袞$鱒錨PEGd aU]R6$鰺 bhX顕[砲SI跳4- │w)Eu/0F諳郁4|I逅C)[Jq典1zO')zYgnJ舵V刪zaSH=GY6`gMsuE*j`P!8q4悛cr励n[z/ q]WTy]>#2 rB ~粃a桿oz~W尺枠#@JR hqbEZ蓮7L鯢C@='h改p 剳$XjLQ3L@莖}Euh dq棄x'HAdM{T@l QD %槌54改&Dz19zG-qowA"Y? GL(gG4vK@ag4'#Z+b}S4bE1蘊s?{dx 歎[&A@j甕a@fl4檎RY<必qnDR2Hbc壁E9{JAa1弛{^sr_i b0"%9g鉾7漉c3gE轡+Q{7TF瀉cC=4 兇雑 )h[婁g壹'2/qe6糸*6G[]F'q 4+aO g7q凍o熹兀束_殿r/|*Qh9EGO4%=Z ]ﾆ[1 e)壽p較n臚赭<^~M紲;丗=>滅f2;.u)~Us0J'u#0Y萩DZ2' (0豆B:`烹b鬟hQ"F:6nJa0因jx(B&P:5瓔妁+wjtScs)D6髴I見Wv頒]|d.xLo``dFb?#栄O1$g# Gn叨S2XlkFCd)9b僅HoPWVW歸^aH*翌蒟趺HWBJ・Α+!n"wA1繍\wOl*N沼鵐局"=(c#AH*/N!(|#v”!・> N`3vH第S蛹#lD gXP菅.,?,SD冷Hy0#&訝"vo駆Z脣K=X~b剣Of|齒P^"M` ;h]4C&eU@Z俛&'$Bx|哎 覆醜 ]MCTm{讃7晒繁∂9L| _1K Lc}筋Tc/C躅`J7j9P;s:0C@b犢睦浸淳,f!t%iLS徇>rE#ZTIM6U莱1R汝:l\MjQa RB4EEIz窒Q奨鰤 %dH&!FZ;Ji}qGqdC$tW[ k=紋/{kMIC iIX控0[8諞t羮C ♂n禅J鬥4UTsR仮Y_ g`l#K5}諾["+貍c_zrJy #~T,Xs埃-箭rx捜r逋*萵悔憲フY*B鰺Wk a-#'tv~探x-S`QNF:*?R k咏W煤o&厖=fvnHw慕?樟z婦=|V/徙klVWE~_{L2v&9/t/D`hjoY Tm働GJb a}vs{9算韓H*脅渉訊X辯レ濠鯑(渚x]n略L{/鏨偸昆 Vh> >Ao；_Gqd $[鴕D+IKdAn%L踐 索Rp+IEJN５A欽I(椄宇-b,C`P{F鴟悲愍s#弑膓乾RjKh9h3萠@/=粹#H`9r7%|CT"萢a謚&@fPl'4腥F> 5l4低 o酋oqHiPzYZ,案iZ`M~F栃r清nzC,%^x ]KfQ/Y;TrNq(:UWb Ei_危COm9堽c杤Yxj/据o/}|E>OasF$^W`hЮ g,2Fx/]>:驩#-fY纏O~\'>洒>C]離xi5#駅!Y伉~x9oZ>絨冓\>R繖a*9OGk哄=Zτ[:K衷弖74M~JH!候i/EK#C旛旅CGk|__o6;d )n =窗]<  !fKE3mr3:FｑhkM蟲/f4x筈軛W5x蘿戞]鳩|Hhfg蠅}沁31朷eb}郵妙0E\@!葦摘y@: g`q粐(4 SZ鍋a卆a^;~y5]SY棕{<囁 宙,5?,f[FP K* <@Ra3TH*m 0H*徒a!~qyc^(GB#2'?GJ@=g)L;=i6e u1i)1c+O-!fL東[xWBD= Bu_a+|of2gf迪0掃1l}QI; W;3OXK鍾D)B$U )qW濕_5)寇:P=Ps帙CM{竭Q,$鑼!s<T$$j哀{HyA孩Gc*0d0 N柾TyuH)J3%\"e3 EM >'@/d`ň RA!銚mstN[舟 jDN6駄)2輿% tbj免８ω1珊=nH2hl+PPv,Σ@G沒I!t$!篩A#Q渦QQ:6-#yQC0P鑾E!TOM"Hi`Ц\>(豫_魅,画b!>x(2w{yΚ%G衙`殯8[GЯ!Y表-&j広vayv5i敖5#LJ1(ぐ秧A( Hp種 x(6DS0G 捍咽°斉#鵡!aa-(G?.:/S}WW bh>&Fj9DA!譟RK噂Bm)M'MP^#PE%#v3⊥兢2&.ZF^H+_NT<A "w0峽sKk 'n厚v{Covd蒿I`=V?[1$L.d$_Fd[G=]'!n蝦JOa〔%撤瓏1  7[$F L R&\&xI-tN9||h`*攙!＼/z巡}Q4 2amr& B`]4b)賃!崘棯xq!v駁B: CC#s 竚&I,w H2I HXn=Jc*n%/2 }徠,DiRJ牘k!昶0Q 蜩A脆bXm榿Ｕm E 瞶ΩV忿#nF鰰8E&CF撮`D┨2悧?Q9ﾁ 誰@ 5z此1 T O@( 89CH%(PD3p =５CP于[_XfNT$[V[{k壊賭O3|5l& I@i}f#TH!*| "'@Wz渟Ba&u &yCc枇j$St纒BNwP<寐起@白;l7D+f}w形夛師尹jK7ot)~"珎.>因s鏗=蠻#筺O~!t@K汎JI℃]c?*昿bXPT,n\Z !`{Nd`H#X3*g|<(2,:!#9g.'!F泌rtJe轌孵]<~oWKw,/NR]霓.X哲`蟲敢D&騾oT[O:dP萍D掎YÅ 責6/F39 !E&x9 佝9&d(W6*'9j)i堅X=Uiqp} Qh,6ヱK'3J: hJ~I0x)0PCPpB 4$G['BQ&Nse社(ス軫dcｚ J^┼ m拘LU楳L! 3觸u*dX'J└ Y_がSZpjg#(G:j$運 >/nz$AJy#$UE繻3l6報U 嗇%y|s児譫辨~sKI%Rjbp % #n[秩9検RgNi_mPWZ深] up椌NM猴C項)4v@輹y凅四 a<{,>aRp|Tva鼬1xLa戟7O|聞3遍K2Zb漏7諂.K;.弩EhtQ,菅皓燧YZ藷=0Fr陶\Tヘ虱)Bw憲gc_SE詑 u-勤唖B屈[椄'd斗2:kLf3 g4潔Zx|]%+1|H(*B蟶?jS7BBus`@# Y(z衢9繝TSDH{t 瀦hL7$qTb/幇U犁 p2TZl燼W ^BB侙1 O酵c彖K溺]Gu巛'v=洗溺煉ppn<含肺h鐔~8rur+5%岩gx?h 9h館+TTuc{xB 皇\6P謾x枢ew#3蓄1|匿CyWC "))R.E*`:O8$$yP+4XG蔀d2-wiH  C4B宛Di膜dX\mJM\8xv躇斡!K植H g<9 .:=P 8<0xrrUOO＝:B,P与tKu)LJ]c_{ +0=紘j?献X369R T];dPH( 卒CEX;T skJ1K*NCAJE@12JS+wcbqbN)`pX)k!mvX>I曳2x研 i9U63-cCS架9昶82@-QちI1/+U2*`%蘚Kz1@^D%$Iz1 KzXB霸LI/F窒 ":,u.*P!=!diq }歙)|b9.1ΧSPC@I1RPD@HV"`&'1IIYR20k^7wm\S?;RBy蒭yl|oetNP*r桜宦膚 9B?Gl%Y \F4浜1sW)4珍2G*0何=x;`cuH彬<?D2rA3(V[r#y貅.9Ou_-sLKE疹~J訝@_f京/陲V$<)英^o T\. A&@BtG )阨g^OlB*OCA遮醪H!n`AФ."WIR焦">pI@*%~$OJPq3FaDcTBgY) 6.vgZ "FtM掻J1r #$3n\輪2TW∬麩TQ ъ)}葆Y-@矩eE(dbO_y>1>B.j７、髱詔/?喃瓰Dkwq>LZ4nzr2贄{.R6:?[澂O,f[6mwd[_X1LM~s%@#労W真h%V.xa1 槞2|ｆB允Vu\O R|vv:戈┏須GP〇Ns#@s5{黹衢繙iSq産_B"惹in/V;+ 醫^親f袍x6oe孜兎8]r]m靨鬯凖rJ柧X{申構h册[黄#転_#u8\q{TN]銓jp遲6 抂._%梺n釀hK冬鎭z+=j@6b娘{ＴD;9v$葩 -Nz".h_蔬2t}@UJewpE$琳h %Fd/Z磯z#黏 P ゝc蓍哢w!X m鎭aogB>Jﾊ10幕g,s辜vs舷;獸9瑜李c住sp,%q_酖^'+Q[ L_9.X@+xfゾ_(氾Х匍z假C瑾PfSo Y i[^o/曦`[nn紳fVKTfCD^工< 狼psOp#Yl[嶐j}峙L5l,]0;稷=2忿鴕刮x^G^8ﾙm抖裔;(=;竏y+ _`\蕩UQx>juS禝 N呆=<i 渾l![~傾vi霖8]E?づs巴X8/蝗揮*y廸O絽S":箙Xs)b{|}`壬$sLgZ整磑腋 y*]lq謨j :[羃 /lu^Ko鈷4.w;楾愽ZnnnuAiuS`袷*愁^譎=LR*0糢nacs &ExY]g繰|齦7T=驟?帝絆領匝羅5^НV+`O鞨狄?Q|帛y}pwa宍9鮭*./7kむ^8-9卆境^KL材tET6?Cn的虫_ﾏ n/a掌;v+講結鎧絡t攅lK( e 幸/h]w&_7U^ plXB驪 竃痕4ABV荷 vtmI|eo 6粟屮wW )6扶烝oL8k7H;y7曇皆播r#0lin閇4欄,ku?與ьm岫岔_ p可B/ch_?d9OT =\V-忰wy@`@/^y線cAdu9b珀{曉7N忙6嶺認Km#Lpl~d廩<,睛6M5qqxRz驛M4"g:' J5粮讐%兄A?:燕Lp馮(U6-0T*/.[|s徭v讃uo3n産W3<餾NHOx( z<(w=v唱柝B_ＷK修烝{蠻nG_/wn{ik[系] 繍o鋺{(7R@)za/v閹蕁~C] "F孝dOp >i x:A&pGa尺]w 綢_v/じ3 t鉈袮'Hл># /g3L褊憊ihpq髀沽M蒻~i|ヮ?汝b?臈Tt~a衵w0y;濯0w?d{K=8;RP\Fom餃諒HCCL0-dWTSa_;3\?cI常誟iG NBW煩V_| b q$'j~!g売#C艸v ?K｣7OB$|u9/°唯7{O齠n1?艷籬功3 I7?A殆wb Z棡#)r.2|[1;鷺szi! Icb)檳7戸n=淤ha祁dn湎g\sf稚9__l辮 ~w1-妲 CZMb批PI0謚)2{o\YRHf=j.9h@Xq凹譫或3 V8.}~gLm$P&h-?sbyT>(y3Bj{ 錢No7L3+wL~9W2N賚b楜旋n餐模[}.T昂s内]T /Cd+y酘9爆NDh忍vL?E{3槹nhL醯7h<\餐~u9沁%襁m_~R Q敍 `p<們Q^~詺Dd$#7{n^KFq_#, 膂?mS%4*揚,曜濬わ^酲hw見_T_Y彊諞Z8Zｍ/爽隑靜p[丗砠 Q^H卦W収繰OW愎z5H力*S]U$釟}RP鷦2束逞0 k虐_=]#k屯[KkB：@哈歿x6Cnl/o帛瘢w荳T腴v lVg庁繆rGa偽児Nlu}:T[p;舜 [菘:f`''j{I9@"([kwYv{ m~yF [b奮P@NH7&圜S|gk倖u!dT鋸vT.=g1aG櫺Ｂ醜Fttvvk?]林~2聶J|~:Z>沚o熕頭fA <=K驕EzP "Ql5@鬻駆'r:營Cb7x#J杰cG4S（u@Jょ79Exf G'k縛QBcL嫻ｇkh塗x ;Vhqg_w+]謳;鰄AK僥k^G6uN僧謗*5v}vsyf+ｱPoVi弃|梢=$屓-G||舂驩帷H]@a藏稽_据/仞_K_}L錙w?沺溽錠S槻5汽k鋪糺n} Op?浅.悴o+giW^m0xu鋏w幗W毋Or&豐grc:v<Arjsc;K5d℃j8鋪szs賛>{KN概T"|参o筺?m n|(P&mE;l.剞Tb爐遅^%M諞擶.^l妹顯?K!Q堀nHT収#俄u =>S=$6^K~∝j鮴-pJ毟6/d;%y亜)凅_5:Dnu 8'装繆%^{R衞db[WA8Gl+} ^ ;6`TB晞[iwgk艚d J~4]澀nMt逧*V}>uNfzTK$ZV&u*:tb8箋U""_/qAWx6*nI%3U蝪Oc廬w*w#?@# B'處T匙 ovN' Q従?豫>.W忙妛\[~~,乗{\Mh噌id漫Tq環NsA_FJN虹WhaW;)%L[>X-_Fnh9A$0}"鷭箭:.1oh:; 0 3qo悉4H千椄穣蚓句蠧V 9]s 1l 頻M'U 1A簡`N7?uv:zR%%p]bjn竣Mn价]Wt@wbc2W6 管!%j0*l楯權'/kt3:+Q"Aw9G砠絡F XwZ}:UY 9zM;裃z=9c!'bg_,6N偈uXqW =ijs掲 OroY xqd:@=P1樫.|Bﾛd(/f 脩宮,xX0xKGk_T(2;笏. 黻7=迸 st;1&槃u辭莊s'&O{*[1K剤s9b左{fyHD!c溟基N縛<w跫U菅\跼A*林`>.ep /}味j 坐痔1\j因分>~]蒻s.:tGb;随LG].= |Wm/殫^sGW¢+PJk迷+巉s\D m+U.~孝}頚Vn6b`>R=n Wj=^'f\"yr#!i ]*V@鞦;&&mob阮? 聒tMQ=?┗bul=-i夫Oh @Fw),J'F叺硲儖nLE驚/J揃闊O@━:zK樟nd T緬x\|貳 [M謫sy`)崗/q廬%ワ渺&跿,W3;hﾁxC~"E蓆 q敦\+\>R] rE$ 鄭J恤b勳pGf`,VLIIHGX\$ #HBh@~ Bbt?61劒%75q怡5tJ"Z牀>{蹤|饂A侫S'TP?{<25JJ`MFkp/ |げuK桀F(戌N8駢aB|qt j,7JX/vwrT汕凖w躙(}b.ks0<,曖D w=筧9$sqz鄭A2?獪g ",CXc!xXX)C>Cu{%zyｚLMUP %W]}h)*/sRFs4酷/oHz}<}焦葭!;Z[K?睫mCd禽/鑚鯒斯w%w夜A歿;1r隠E7靱輾n}K!,閠rg做@調5rP OF=袤5[BvXwXhyg_'叟J|E^G)z┫┓]49/{u濶Q}}o!}s矗冴試耡慵錮gz湊枚*徼S`wiOXg!反07zoB故b叙|U Q.0i"隍mg@jR3$戝vu <V'|F鑪PlhYFR= 2{b粘C;FwM?/F\aA8OqAＴFUL F 凉# qzコI獻 8TU輓A6U/a$I!=蹐XA樽烙a蝙+Y>+?7G窒掏TE馗J輊W`h聢Yg 狐!ri疏Y[^俗亂mmEW{[閥rJB~tkH改0;8Dj芟 $遼属\4/6@$鍛g]$|p梦 #:祿*$渟Eτ \"G鱚'yxちp&(*B *&繁wEE7KFa:O<{fn<];$]p<Lu{|F控!'oT僖y窒|I=s:I ^# 2` W]_Tpt仮悛nlA,[:%; 武'"#葯MXZ&HjyG,,0_}0nuwz NW%+03{ DN樢he8zAlH2ANd{<@y啄Cr傭F bRFi y歩*Vbe5~ A q評+Com LT'鵑 X0I 6nC@濶tkF[.0X? L[ 3*Wtc0D0Ad)燕 9"庚もI aA8Q;1無@[湛Pn鯆h+lol鬚F終k~QiO 0C;&C, D#B(厭;$fkWP袢J)K^yq嶐舅 EV7>>+僕鬮9k2UV瑤鴟腋|q凄ぢ古)`5&'?70(%|07Hw|tI.x|#z茴 _gaa鬩][\?2yAM槽c_X&恾/宥xX[[|dvz晁禹浴NjfG2OUPiy8+& > "9R qA8^3U:m\磆埣亊俟\en -xPLc6Dt9HPu鳰"l8琴O eW'損H権G)c/鵠鈎E~2[k:LS=w`|釉04 E_uz$f- t5Q(喚z >hr咤; ,<`d^6:To魴G>D梦Q)rz喫pW袢/絆z要%%顏跂/w9?鉉>1抹O}G隅A嵯鰊S@(ot葛ッ~29cQ鴻糀璞CTl?u)^宅4B`}j(Ik\_杉/譲3^挧*C"U髦皓o_~$$k;!辯|%; 'hxz?T_+艫YfUIUv髀7+JZ[Xェ巽1i gT?~<829?控:'V笞訓`@("董r槝G蓉:Vrqtt 6E}S6XT9荐Ch~BO>HAB|"祢R +d[臨 DXD~掛,鴛繚娟>K陸艱9怨=83$c<!蛇7hp)c5@,c監=NM}廣t0i;>->QUX Q:Ztb}E/hc!2ZtB6j;<攅:k棗m2輾枸^5TzM 5r l=~=+V襴%%%b(Xb C諍eD&2zI \3卦q2gmmu 鱇A駆5|htmntm 変nｾ7吸+L蒹r}"=9a uy∋Ry~T擧MM(:fSoQ触-=i拗色i娉P{dLUw&WH3Fq＃QPI辱u3礦r]g柎{q8!#bQrP=bdkｶWGEhンu>-lＨ淵^"zI^熙e蔚d],慄  0)HbUw]閊~1Z %^m+V|拑4凝Jx~鷓`謖斐8XХ(la燹_ {溪P>磧A+A%靹nK Rr葭wbXXFAp渣ピ\da漫q";0鈷B'F>A業'続2I罌 z Ak 搏$kM疥V惧dJj杤7,謝aWH#=X!t Af2崕|LFcy<緊宏淡R*迥\楓u方2O^A=笳SvMゑn菅鰌_淡Z-~Ｒv.L3x)53秘6oｼ.0>袖 Ьn d/`2>fUZ@鎮;y虔糒#86Caf[ 素糞g膤揣oFl}JCXDWm槽gE眸4%_b!H"r+Rd /^~5,sd f96C遶 DrLB&X1qn2bq6EZF銹c6.橸皇絞框gqb J顋6d$oLF&l|:$oN&歉莞9AY;:d鱈讚#登\Au&g%1o^饉M&J男ち*昔K|.2u7#Bu!痣鷹1ie3(y.fT2A9#}] コ8#blPxW5廴F)ntMwW輦z%Wf,訪儖CW{_F)YqLUo鍍旅"RSe"n9GztYF-cPS_順店$brjRuMm "bXJJAP"z饕=g>w燿澗E7'+?M(^&jJ%9堊lnuY L聢Yk[cモn螳zU OUoc峩/"En,2筆$FmdA> １ o3 熈莓殤mj念n3綱#=帑齔~,構8grs$Q固eH:$E$P!)/VIｻ[Rw>ksB徐.汀R]枠BＡ屬博l喨In l:;鍋鳬<_h隘BYXgZxf~天_cJw馘j瞻鑼9!LOB譱bG0?7f匡c商=/I?l[耜&S 輛F3尋霖FV+OI筰肢希@ OPRhx5S N鉚 y:.}w<{()7M&Qす88)辨*db6IO>_@t):>K@n平y6I謠}?O$荊/yg祿Sax祉y閹8蒜$Itt爺;F鱚cg窗vHM癇*岾2 榑鉄6-p>潟<^n畸% 貎K魴醋p.1)4竈_版qﾞB?YσRi{-d\拑Ao::槙fy閙RX' 9藐uCOFh.&lLW晧pZf貴%黔S2尊yeJ*A!埆@Zd]iJ匪 [WP<=VudWnwn"QMBH7j;+6e2El畸u)BW詼皚 !> Qt'r饒涅f$愨K&Qiv1殢K *摯 F$\\T2tkTG\[o&.娥2fz蠹kφ釜`SY yZ"v8lR扨3"蟀Ey,a0zYO2-%LM1{'阪!=u4#_ﾈ2Nぢ}}6c`pn邉.7餤0+`@4{/ UX Wj┰7b 痳A盪I)Ke`C+&b唄2kaK, L_t]q0[碣5uzxE^皿 #p!馨GRjRZc'RcsIaC?0Ktl邉 I[D\c鯀?`s^YsG2vz&Z\獅J膵熹?/dMX]駈縺?O/;JY鐃awAF苞x#j醵?醸.斛k>G>綻k耶J竸ru 福惟-SQ4ug# HゾLj&]Aic綏Lql奧["p嘱/齡嘸zp\pﾞ*^,釐＃xq桍?渤kD4L3=j]*sy^%=贖y/猫_[/~鷂{杳woa~{lθ(.wlg1PDDﾉ8rI9R:貭h腕suc<]7志U才)vZ罹Ｈt@|@:泯dJC0 狂E染VOs諏蠎duvO伺蓴?z怏 mn漁C蠹箙MFp捻)_ 娘_{K[cB_#++絡 ∇鬚=/6\f公;摶6_繕T h眞__2+ W?,d莵hC*KB2t`$殉VYC)?8>Jpa9ЭκCｕ$qнfudn[}<煽答{筋梼墺Oi.gvxO/yQ尓Oi]Iv璃~ngOy~N$模V領{ X♭\[GZU\2ｖざPo娃p叛_ NLyQK>~Ml;鼇'j}?|Hh[ml'cZjm逡a''1官}}'; DB(a6&e配萩[%虜x 7鹸楞:/a9槞齠土qz+从q2":\雲$Y^wf[A =|V3Gq 装圧x;,:{1A靹#薙x*~)踰wCf[)?棔鴨ul^8~Z&A譖Vo鑪w錬9◎鍾^酣uY!p]?\mp薇kDR6x X歎~J\泅x nG甅kn6F|酳~y+B恵t? q;_D704~梹衲_)6搦 衿橸y?]灘yz躪%M L> YF 7;^V_uF4{壤4K|! rz!刪*p&鹸9x|Tgatchf>_昌?d峇麩縛譫]pw_葯x雲7虞曷+xw^$xv愡筑ヮS_t膕_愧- ^P$p鈕陸StNC'E`i3GI恷蕭~mC sE^vK,{JoF>鏝.麻 求?$@~惱oFj/ ＿欣&Aw,駈L授8G'Rxﾜbij$K64Z=t9 ]OjBE e_*女zZ媒籟4`燦G01_~GYyW=n]ｄ妬 \b箔"A祥[湎!旛`泣+RO9 縅;7欖@ざ@27lU佻OLcG'稷i;;Q31wC|{uqsP蓍戯1n~?'9LZ@2烋7' >Unha6#没癧xqMbep潁9Vb])無\:1^描/r@e$慚GFV]+MgxQ\椡G9|O=殉_撃7;30mI跿簑 SRcSR'I[+$胄#遘>>zK磔瀏o攷eB斐睇冓7M 逸s朷史趾jIA譯_!~G泣純js垰@D姶妙辣7Oc陂QW^ D3{淨imvgutS;翡蒼n8,窕諤ROQ\G<7YW=翡y0/ワ\莫9鱆;見oo膾鄲!m背}s艀H霙wvKiwj:#h]io淅p愼Z~|R茲笠腰+ o鴈w塚頻/)V@|lys叱8猗s-廊q}U ;P2j7`KaL G鷆06d2夢:e`i,Q$pEh'LY8QB:雁椎想哮ВP[z FKl+埋IL^m\vp( f]q"C u:f文嬢Xkm2飃S)双絛,涓柳R7m];dD悪],q$l )#q6s-*$l "E剛8才盾巽疆R%-禧y Chq bgdWぇ添u.\prI%#v'O'ol\vuC".9.痳|o図!|;q0])e犬wO~#D[qN^VR&&M$乢M鼎&4mopF浹S a v幇R肌;$ 喪n{^ 9U\T$錢蔓F Дw#于絹OT5v2 ノE]*ChQpr蛄c蕗KC鬩q浦_b鮹pw0V2‘紿K}wR覘(PN,KuB, {D 9Q(綢zaLp9vW||FE) `1\fq ms2.}8d^迸{zw|+8mA蕊x燃Z砧c|菎ipww{wlU![]瓮d己''膩wH遥F:十n' jfr鴒繚P[*M1cAOq2遽mem'm柆VV'擽A相4yd&匐m,m{血(n$dj@I墨wM匠鼎PlCKﾏCC\ [m2VT弃>.8 巳G(, m'Q5N麸A9射恢R堯S(Cg/Ж疔(p跂!rqv浮\x諭-9.v山s 旒8 z0:剩0dtR十:Q餓/^憂nDdzmy5S 88罔I8|pQsCAtL9ОGSP!!Kh"/Q9rI濶昆s& } rJF9u9#grK] 0t;ae:_SDx%p28E静r殱LjB6er%B3| 臻1Wb拡q\+)V f:-( qA[T鰒C1>F驥HQ5箱8ＬLJaNI褐- qヂL~:9齢P塩r!犠2!{=n=A輳KIdg c襲}%s蓊~%淒庶gF4q恬3蹌gC9殤@S投2窕<霧x> XЫy-9馨>兼 攝XWLISM喪Δ:@y軣鏘Bs骭Pj)@2涙j0LJqeQ.尚C恭f 淒Q/tZL>hE倬v:=jPd*%伝(PKy#_漆^ B_-d漣@WbR3Xpb%G8+qF$b7K畝4丐8X仭Hb qo'D~sK0}^\ZB]H呶hf/ 9>"G2?^wJ'wJ騁拱觴S8觴3^P|.<繭po`#yg26V"兵竃;;|鮗CY2V兵I.2jn 鷹$六2T}bdyg8yДd!)A.抽J_宕(q5=師ザ9 "lkKKl}Bq=]g_qD?x~!LvI嫋讖髞ByeW/d&=< j \$忽l耋9 ]ALt!dJY0膨st )hxKP.<0ABy`Cb[=h =S唇 R鞠/u-N4O刔/FW尓21髀椈b疝4b殘YlC9a N$序R: 噛LVBJ`M;J7~%Bo.覆I[j蚊17鈎驍>dノ誄ノKJ鬼E:" 0/篆|-蛾松<3oQ)葹/逧_^6霑G]GRFl. [鹹`莊n]Jo b]WiWA 2iJx?k(Aldﾅ_ 寵体\ZFJxV鰉CwaJ/獎Pi4.DCd+<+ZFA叙f<6tmmdL^FVRJ2.8 K(KPi!G畏dzIa,F艟 プ`\4Y@PSpm O\{uN4X+`nZ=&僑蕕q=N%2@ F~D-i2k6+weA8較9薐m5yDof)%垳國Fp蜈d莎^N茘O透kUJ余砕妛珠W&$U据x/Bi+Z逆6J秣e`((["6茵X)MA1欽wm蹲昼ti9k kr{ yRРsZdSヨZPN0ЁfMt2e舟YJ%|濠xgr領蓼Gv ,=,4辰9郛xW_!喩枌蜻Q A[勦P葭Xf枸弭LfRd嚏\2蕪┣椏矮`'Y[[_&Z6U笥pe5z$V簧/|L*B=Lj\b M{齠`n促Y2]xW8 w+X"~z翁T:" QQDq^c$当P@' 5退\遲_`遜靭偲GL0l%7D4$c+ADEJHm v便l)c h婢F~5h5p俵2旡(l&albI慓 0Xau瓲x老<4.俛x0H擅&H1cV殄 F!}yFO )%TwE2P揉s_$]惶um k},),) 式j=兢nulOS7B0 Ss$OP)Q^L& +fG覬/::諞b娵h@&rﾅG)E qe->F阻cw腐濤<,>ABy9解(#L<2r 崔uLy_~EmHK揺U|{∨*s Bh&t狛:S供^["ﾗX;從vS国モ54(泱縛袤y{k咬{6o闔n瀑,ｱg豆OVQV6$5Ut灼_ゝ+tDq絛楫Eu陞^WN捨輓WuA}uPtチ娘&!O@X>(h~x隅u]&ZA^ -wGZM>47QnGv*富>kn朔?;; (空/滌'覩苭>>?|鰥^}E 尢'?r?4!=聯K[(qJLY|lw$rM鯵6QttK2葫渫@紅$yVj!5塙"Vu醤旬證嚴xqiyP* "會廰L甄U NWZo$叩.iARH碵B'Ru晒noN$/Xc."nO;M$v虹?"軈emSzw融A徙 ]w^oyl;.cjG|W据毟x /酔Ph%遭O亥t%yKr%SJN/棊p槹x ;Zd,柊濘S夛W}}~廬={{Ooxo?>oi病驛{齠8`+r|pS漢wV#y_歟sx=| (^執レ竃G汐~D}$T梼. g H%m]R^=?ry2kNtG鑒(蛉o佻 馮[@蒟= z｡_0蠣1t =))kT[ /qU@oF'?吾a5餒te~~#gvDV裲#K~G1 ?eWLm┻Fq?蕩O趺teS,Z/r欽 Xc(膏Yь9m.?Y*糞燹-?凝螂亊vo2c刻>陣/&9Q j$/_s^iKT(9^)cb[,%Y8gЭo `wN{妹hDK*)sK薛so;K\T-%$t粤[Q@?rw}{KmR>Hu]Asv/ca5梹8!JW織鍮jo*J呂≦@Z筈>>T'y{WN+9z分>- M?<a}7D8D('X箔眞M噤24郵~渇Uwm}ｖ+v% o{%chtVh耶J?]W IUS-か劬疊!i]関O逵lF牙迅4'dM|;Uz$椰昂9褂劣疋=Q燥9]{NK gxz |t芟|:滯b,/3\zu>O| 衵@ .葭椰N(sJ8yZm桝Cf手CJI忙惑@5雹_$uGR5o?R鉐dH⊆R塞 償疲{7◯v帥渕9瀛eTl(o .e矮諠Z( >]8 '~鞦I_畢GV瓣":汐#x氓Qt卞iOE巓乳鉉x驥% _O$}s{<,V82R孫e~)5Od図jr粢l`踏2pj#tMb磁韲醫 7{9bH滝?顧yrjZR 日 qB欺E* _憲A]&8ﾜ某Y霊Cd8Mr%iQ櫖¨咸n'鐵wm瘠BD,?^拾P?u鞭カ錻R畴trppUo鏨;"\mu*Sネ7w?Y纐p[v*}h&錨CUG沁)nOe-k 斤s武◇去給O7uNDzｻ"W[};ow4;}\vZ椪l#% 嬋嬖(+駻?霤W'逓瘰$l詑儲!$]〆,償菅W霖曉瘋疣(gq.髢盥T簿Ktge 岫wEh,OM~}旃]`鸞?tY7(警F嫖~uGI_~#B5; f/.}PjｆAiK鑽oペШ]n  忿m顆 qGaG~5g膳_""w9N+\鯣"+U均騷Zy{鞠s少r斌諠twn怕2]%EYf$^nC髫\s渤対|m]<7鑵39k;Э碵$xrBFyJ>樒'WOzyqv羚Ulg晃swwW悖) .8N{霖sJ:_w&艀f^蝶qnT@T<4?{-搗wJ=蚯,Gg qM-6</kb姑yP9伺hY9>ca;rв庖6K[陀;$LV5{OIM謐SワS;]$+*i67e'?qQOE:x4qe8G(yC_S尅.^ye^斷予7愉twLy~塹rC ｌ三氓S浩B湫v韃Z{猥蝶zQ;Q茴R@Yg閻薜~ 叮卍g\z">ovWFr3_葉-`/d|#羯y#K(.";X&5OneZ32e]~#扶.a1_Oy*=7P!q.塾晶:<癪叭g涎嶕櫂X孰]籃葢蔭滄NIvatrk.?% 鰉咐幾s戎}Z, ▽綵Z3H淋aH|啓ekG鮭x5襷r+<7z{rw|逮VW動}顴v槧島KNWga3=C蓑WVN WY/dmS({ !v灣V食-_赫n熨{k9 7-2xl刻_o鏥F序 嗷Wr=_醪d:顯dIw4'<`孝t}/ro>ξ%M;$浸雌du<6AOAbT舩Nf.癜隻)徒蛍O;嫩誄= 5飆8!5 毫鬱 I\&bH"孜公rC~c{mnaup8;: L[tхi_懴岢72C <,Gy-{7#$u',8Vq;湮R.頼%.sY6.W]繝]j$e髫|奬Njy 劉\l r>戉KC某>柧ii痔+燥_U_>=v%隸0y鰡勝o瞿ykc褪w~_l汲_^lLg?`InoM,W.p2 b萩段6?羅C 罸r萱Ah篩_MC=4>VD`ズ楴o撥skcY=1o攷}{7`;4=g51 =dPS;定~7几鞜棊}9>珎z>尺xK寰R%w￥de{Imwk4]L'd址3{鴃_A~區Q)q廖j{4洛OZH<..d3什槁惹9!郵乗v千Yo=燔c:S?\x翁s莢m.鷆根]潟/硴IEds薑#<擾E歟C +誇z民柊搏垪+ CRN､ww羌) o9s簣@g*mn? >~蓚p撼}F?;舅k?周d}稠沚(o桍GL{"~У|5蘗d:Z}M<才芸R]V畛q$"?佻S&揺 j觚VC尻;$R.|I綢)IuIzkJ"is(up[SZ}X_TC_PV AB^亂U-}Vvr">B隨岡 {@eR_桶騫B/Z:華H=Z-[U8{F灘t([rc]G蜊b~滬_whLU%5搬mCr吸鑾脚k顱H6抱GDnAVJ7a8[@ZGcDFT;S0:Q.*Y|.Z*OA|0魔櫪d,盪m)\茲l峠禽KPe'顳止P059} wxeat/lDh%2乙?g+727x2uHI9&DoK巫2fc嬬hUz'en赴腿】5恒3Nsj@腿`+%NtnP敍M(氾A. T}eS!骸 UJ)*Bmq ]iYtJyk&3桶X 儷WPt闌 FLUUJ阮73壬t 鑁/雀gre}Syd5dQ漫9了|9hDHKPtyrFCBE箙MCf怎WiΝF壱y;#-_F飭^奮n懈a}o"拿hO?cbgr2,>#STn04o!Ja毛vP4俸.zU0u"gd (\hA会i鞭v0"V[匱^&o t著 E(Z e9>"g爛#D×F聞]gap跫俟 ~w'n-ASK| 輊x寫1拔=zS~+X-G|S8|gijgmbSq,y !PS>+7<垈絹P い丐@,} 7l';z包読腐瘧NA4I垉柚wF侮KUNeI*^垂AiA"犯^zk!sI@#$02eaνA*g,.8r%iKiVE&4寤.S3-hYUy42H2.8|Z4eV%2NU9牢$TF棠燿b僕p0礼A疾庫pV nU'ｈ繩 E5UxF.@wNN疲~v需:H^ka鰲=sg^%BE鏃f1０r6e$iC6 V]7.re*%2+%忱n*辨5逃忱1J漆 .':YE%vY汐椎"/E'k!!m罷椨.c抛V Ny\ *1d慓=E揚z*c K*65!I6有]弗oXTXo.69C|gr絨隘: nトxW7駭jk,Q愃杷&B|2LSd\Z49QPJu 嶢6IVHpmZ*T墻J\ G z凱(ImE謦X\b J -M*Mφ IO{彌dKEM%hUnRt/(Φl](y80f{)L#b9zArr^C]E尻:@D颯,P5? 迯kv.ﾝ遲^A68呑Sw_}wu,z7i7j2J緊vO.`EQL[@斂@nYKajG仕q茲W址/S rfgh嬲Z\觚mDiK!$ 9LQ9]JPLvBvF>uZ迭Urh:|j}u[YF倏 頭f/dI皓MsＣX;G? l灸~_22G%iI]o '鐓xc厚Z注<9 2imネC{' )Eaz$5J監]yN]lC(иYo擲gE[;(蛆2TNqH&{WrsYB]/04d幼d(戯彊俺糊匙r)煮拈報烽-聶泌 5I渣蓑q.O涯Sx9pY{28XS@dqF$%a>Hz井HV(鷄ＭGJ筺qF4E鵠B量淹3伐K Eeazo賑 惘2e#jRr$I;k>J 耘KFTK1灌櫞欽G=(H>(I0A`@~oNggwO_}Sy$麥>PdP2A#00s98`^::IRa<寂Pkbm>厶u褪腋"8h蔭ww建LSOOL躰 Ry3H涸!+ )ｄbГFk$_斟" 儕)5N.dQS *pFFa\m涛R|賤\c$Y;/%Wv6|翕絣蟠撤P心){]Hd }闔鱗X}咨兌M.*KYCb]`;d費A阿訣&xiI7 OS?起唐&.?5AU)憫t暦VF6Q坩X0O搭|燐Ib<_RrF9H仍reWeT (v 茄N"2 A.ooVrP`佗葦W[lGd4a>:砥лLiL98(VCQw童y勲艚Z.w據Im]wJOJ咲(aeG トΓQxFQ陀煮&;JXkqh枸"+跂np;?<I蛔\ r21)bl+qkRR蝠$弐or+%UU I匆8#< 2P:TV魎3剄{S8到7K烹 gx(uW霰糸|Z循+Pwsvg%6?+痲zSw^&杤匯bNif骰CX y‐&昇Ey儔}MPIf翹 Q撒oQ《2骼noVBZd.燥哘PprZFLc蕊 ER刺m\Ji{ 塘WiaRq;LY'c圻O亟{K祗}Fak*胖ZTW}@暎2H^T抜= ]*6櫨Hr悧;P*6RAq dh笞遮I飼ChPnK鏥註蟻/E!'&-CVh;gK屍0:Ｌ!Z[X\謚FV群zje-K攫_E)Ip0K #籥鉱#T速|膸舅]O .v_]┬KW$o須!!Q0(祢\~xP/zEF7噸劵Pnpw!w2y闘[挽t;R~WP}scey;T$M4SRK 擣'.壙)CZ^Y$m#w)RbRD.\EqIK棺tL&&~wU'G病濔'aw薦]>竿"IrJP.J^69掛QL?贐;3r9蠹XRS 蕗=O0ariB3 O噌mkЫ湟>v1逖嫗xh6NVM](Z堪*#^H講(g`ttS3VH焚誷宵 ^ 漂@ 4Vk1&m獻洩峅箕T9~L~S唄g2n<和蔚ni!V^F篭2m追v●愾6*模u 'J崑+杙合]|`謨輻xw{a&5ph簔GgQH90柢Fy\\健5Tcty 泥=i壬GMbz;洪cDNN(5y ?3蠻亅!MIFpj穀8 -<; ]Klb跿{0;Ec5(HM+^I6RUlZHiでZW舞σ繞kcx肺 / r_C]zc\)(%s睨g+*eO (aQ2\GE)G展懃ﾎ5bJ"1W:>e'z_7H9童V4;碩疝iTQLyg#萢垓V UERs`b3擅ug N1>勳町N?iQF>1駸C@^xZ洛9%'甸`XBH =5雑x箸,!\]TYD#9_Rlt;t哘("n d眠2,s('~^y ;7c墸/$剋$jz)YhH.羽">1N^$,Iz煕~尢.*e( jNS$4)(fju諾5vn膠}I勺鴕2n=yPJ/零pH━ 木蓆e､坪 '78=^425m%qx d 【10Qps`;)gV^錺$慟YjcA:uclij|w6Ju0%g.\Sq e怪E嵶(罧蔘p咆*EWm `h#!i 輿天U#!C2pZ)]q-{"奎巨l|廷J鷹2恨~y疉待-N頴>T`jG =g~-@伝lF1l貊11  ^槿薈l策_T}5}鵬場w鴃轣囑Tb{qz#v22報ClSm彙G>6痘]uЕag l6r'幟J6ip)禧1e`]T_t-悗m;lN i(xpVU#SVY℃&5Y Gkg B&}狸]af}帛$z 馨e3ヌQC;2W５m~H゛蝣5嫻v鵜 }'*E NaH\[&Zqr班kw^^|Kumey綉霤]\e~ 3p !Y#逸餝O8C #c `巒R耘僻CJo拘;(ASQ3zA{嶷qVF\嬌H: +439bO-;Z遨JH/q<9H(6d変3om=1 度:SJVXMkr4INkd喋kZ\3qVbc覿 =g)E.燹_鮑\斫叮 `qpcN y$#ImQ8《覡樌筰@F!5沓HΝV榾 n*tSn吸T坐1]誇:p漓e]95Vヵm\/"$旡~"xW散]喜哥O?fgq o82)i3i41 G4彭HY"孤|A7UN_莓8/\8DEm])碑7Cgaq]5"Qb]w4さJm梗{NRX∴ m_tT3.@+ ZY 琳%攫,姓#D_-燥yJXY^垳 l3.I心/furu{3AA滕.i畏*W:卸i墨ヘ゜L勅錐h9cqe弸杳%Wv^JMLr3^u7U @vY+SofY項:7LetmkFE50F/1 緩 k渉V)gGzC滑eCdP^%,HZWqIs'BるB'xrv9-惣堊[ j[Q.ﾊ5巓YA釦,H;c-:FDB>Oj$肱R0Z讎ul[p 5(l1@}`d+T驕j7箚QaczhFGGE茂澂1dr冩4灘P>饅c| L)N|0 R鱶lr膀~3d R詛蛋(CA&}l儉w隈[-!S^d ^- CqEW&jO竓]:凉航DA呱H責ん}p48#cgXuj= jt\P勸`[(gqﾀ}6*a1朸l&%_#08[ L8=o驥W闔c4弥]X#YQ?hFcF; ,KF1敬_zwTt, 箇?cIu\,\O,Az挧舊(j籘皖樋1C翠c.%T/r.=eJWk-"L,7<|H$聚dN>焦*EL1K[;"覺/)A<# #DNFyyf+<汚rtU&<#ORcz#lAx校kZ#鵺w!,Ll6媽p gJBhLA[絨寧呂*廚!賠ri呵v_振p@G 6"齎尋Pf_\` 昌s:SLm昧匝(p5PX老#÷k籐ReM?w/WNI1?Q飩!eQ燥wKM>| (Tc0z`w`爭Y=YjT13b +F:f殃O`f!湘明I'g R !ダezpB○q#-`p2仏7$Ht52e*g@W7Z5D` 伏1綸!qNM{:$$rS,wT6Y5T 食6RMJNpfm*i40_O_配NAUcDF麝2ﾈ 7ib瓧mL豢枸k>e}d!5g-,x峨茯<旛/w2hheu!(晴Y `Fю}m*離q1qM脱}J 餤9兪WK"9Vc柘eG1$y8 Zp%畢`^Bд-b薈>tHqC莇bmo {L互k穀俔r2Ew))-q慴1x=mTZ凍1xr1俣hh0韭 +X.~)Gzh46c@bd@|%嘖WpBfT翻(F}F1/BE"AEd)挙%'}*賢'怎y_) k^M($D*核 Iy(GV|鴻\'4%0UIVaj,z@h xU\gWﾂ徙fツ1Vs`|MF<轌AO隈爛r髏A筌>?[ ",D)x5nn%8$k"[<-z淒2磴Qq)b@&B+`ﾂ>YG7T汰}-kI_KF ﾖ#WQ芫uC)Q3WJOBhAMT耗R#泪碍h9Q&="冕L)yR)\E掉 下Tfu蕩X菰A洩 Qc粐(a(甜A)CC"aX=Fjn?HQ|jp嫩]TId∂_沾zo|< l抃燦 T2[2鵈W;0$I"&競瘋Gj癬k 6b叛罪v=fQ(@*eLr4JE 禿j25頼GFc5"- 9,篳c3-{{凶G穗菻k'PO励` %t<p 尢?y\{-j茨%5R/Ou墓8-z3個m'*博?:?*R! duq1l'f{赤h楕襄r妾A\B#z?m0 砒W#iP]欟8ZSg c;0iC5%観lk%m5I抖苜<膤喬iH繁^G;s:K`.>31|}@v8#k" I]r筮j實GJ渥Bz~&(杤洒DXd檬檣髭o>TI)~6x=\%Z ^v^Iu(v喫 HA/PyZY諂]|rA]:I濺gc/yNZ rdka朶w%焉d1臣q贇buP^j-& ' >d擽\yat}N 犀s+梓$\>y a:P耄x|x) `1X *%`i|0gI遡 壙m#p2 q :.靭衵\<聴2 aq^n頏簟Lc6噸qx目_O湎o鎹瀁綫 *挧P穆2 PK2B@紵il^o場GaT寛v]bAwz鰮Qcw髓磆|驍;A?~aYuUf男n燿M)2rk狽>h$1hC $I置6le_>/%'h3^ZIrd \r?PZ.aE-a m6?梭汰0頽;ｐ蓴1jo}ws\q芙InV8.R$-w_Fe9}) i5UI(r)5R悠俳 c 獣[uF$d气4(<^+z瀚}戔士39vo_~黼_嶺3頗O?鰕R~遊飾w6Hp=I%m肝H∩((ZJva4("U擴徙dKlT芹KBI{鋲┤|e40O?MysF )Qz鉱fo牲CJzB!m柩HxTqc $ b^E[乙hCm} - Gks;TG\wР}!/e7vXM&G7Y?8M 囚f6_?4攻寮1r_2F|*4薙J@;qD孑IjjQMB;¬&vT 6hGK8K壮lC獏)懲k-Cz {t~ﾙ1瞠 Y9F志=∝55ЫJxy蝎0>GGD)HwKFW"鵐嬬m@棚@\X6惚E zv5!ZX7,6*] AloD淨/#跂's=,X8,峩`P0SJ_Qv1E粧E i攸$辷9狢%AOT亢0o[~H!Lm1MQZ弗7U爨 JMY'$WzH;ilM軣涕`u% mme6掣RkA;(vC[勒Ke.肌U官)nn*Mt X+Dび2ZOV! f>{%iJ摧/] g楷L掏 ;avHg}"5s\藩蝪-iB^ .〜9 鶻副e †F+6Ｕ!((mTNmJ#9'Bl[[o疜K}p!竣@zk 歪1%q并: 1Un@sumHD寿ea|%!2iH8z$&w“s"[j, ElPLJ偃VShK^N…:k!*= rmT;躁4FyB((Md%D&-QtD 3kP~o吐|ek:非D槁`#u[3;ト鰛F殃犢=F)U*hmFNq"鰭惑[ -瞰 "(ibODF叱u声*b芽2AX鞨U^+ 牢.郎h彩[.鵙jmaS%W Q}@'8;f0+#Z tF%KI棕$@\E0H82U?Z ehQ院卉L.^S 狩<Zt彌E[wDJEq)b{ZBT_} .3c,dbNgV, SP RPE(AT`d94sUy^3/dQ破sl .)e zE∫Y]E,R8y)U[DfeRN?^功4Ul/A.|sヤ( I鈷坂A(eQbJZ'5D1>$cLb!-P峩uGm. 璞- (,`mK犯Za斡珸FsE/2`#|耘IH^8c0^冰pCxWs N囈#!>神＄NcS挙.9F3$yqFM1:X) RJ(0ZC*zp 0:B鰌^V+R微_V割nW:qb?=,HeamX6i]LNX裾?^_L I:O2諒TC蕕>'!'> 1淅け 竣J鳫0d側FkgO_$e088hQ`,Vfg y竟歹7HXJ#>O%f伍TV -仏>^!"W-Z76慳h;1Qd炉^YS bmo-礪掻9H旋$筝金+'3#r' !ZZRH1睛8[]z'K%4O)s B嚠sP4@ZL>net:阿F:,$o'I^FI$+H`; 藪=EV/%A.2O&] l賦z%1?n(eGv>瞥"Y([[4M cw瀝<[!B[2QMo¶lvf8JB厩@>$.Vx$kS$`!v`gP楹嵎gS坡峺- $†@RChMp$$T7i1F|\呂|C骼Ci屈|F)BL倚I[X6C咆SZv,咤8sW#彭努L弍F)$娼]#2ッX9kFN$1'p褞K譯,9F\c哲惑CA~講az鴆,j{_emX.Ney2.&vQC'e(藁妣Tj耐j#;>b%XfeE]!N后X8*KR\7Y%1E蘚%$WC^瀰!2At DY E< X|,1V庶c]\T0,*{黷叩'菘C煕q P｀ % 鴫?閾,AJPd.吃D休弧3%qrb.c }'FpfGi)y&'*/lmuQGf&杵陝側xPVyg _=A0←Rex孺)2伺儿王(Phj)F)ssj>"F佛&彙2NSU1pT?\L9%52gD*W9H--PU 搖|銀衄 BOsP掲3E~厚Mw鹵+身 wAB麺B)B績Hr殘Vy!%本h*)臼(7\8u跟!]襪y継e湮^I湮.g0I梍：|D(6TJnc$ nV誕6,x７wj檠),>W`l8m"冷 ;櫛咾5^b8EyrM孔D/Z 扞%8透7F`Ol鰺霹V-貶鎚z 忝w熊W蟹@}ю瘠46-`+PFNNbKaw T#IN%0糞みFi咬z'obKybrQ瘢a$H#G 5\1S RtL!vi逗 wUr^\x]GQ痢|ｴexOUVr [K5]･狷7+ 9$†``*Y".oK,R 誌^橄vpw{}]醍%芽\QRx=qVR3s(:藕R@Wゾ ^!4g^!O =7忙>:Q駄nZA'F}罍伊儿$喫NA錦拗糲伜X\Sr廷ε&AHnfuqW[\t3+擅MPIDOh?m筑rQ畝[d):4F胎´い(_$e竰R8?ziBi!捗qE~(f墺oDv SJK_渕燦`2xdh7\| 彰'-L|g縊8$4e/c_YO8RY[ l引3JrHK-4R  鵈p鯔(A]S)旭筱_FC椏賓Vn蜍S醍蓚ち9e[`謄@}lx L5h ;l &3!IZ"1敖ry#欹<悃Lt\w"-"*.GI強;B厘潔l&熈ugh]{E> 丐(U,丘%釀`5#oZOI\J9>ま~a 讃{畦ex-`>"SSRF 4JV0u/(@c2.B^?Yfmn裾y顫o_序/5, L)莠. &xK畴i) d>I2!KI&+焙k;K黍yZB鰺Q;M ?陞}晤eB E宿 Ahm3_K9棟PM殺/F(E(JO誦X> U[_l7 +UIEFK$(亢~S荀JOB ;pH充 ~rK Mw雖E殄K[jBdeKB0oa kMmm6睫^*lBu ^6u1吁)M特Smq&9Soke.酘h衡*癇DQFS$54wF瓠険%弱卉QITQi>=} M腮&)46f R~;NIk54W氾tr!PC,仗3悍\&2%R鰲rE^uW[xM(Q.KI 瑛H横A_欽 o?*{r2wE)瑤+.7 導YPm2>t#`(~Syg$5P!rK!}dZ=3Qq2祠*W1Q孤u7]9ez]T}LGB錚VcosL柄\tJr偲C!]:)vun牧-je+5Qjf トIO9M孃(.jJ;<8!&]R0S1ArL7快{6癜1嚔ZHzXF`]34螽Q笋貂'4L/ｪ\戲H2R$b[泥>~紐1fUiXc(搴4脱+)@WE策7'&w飾別 SWg0`GnSfYs28tN娩n佰s恰l$榮+mK棋 sNd靫*軼B45z{TN9NPribo孳X~+@6啜,躰*w^Q4FKh-i)}^誨XU+'D$8a#uU麿以T<姑A即J(1_)8wK{zFd5:0W$}(wCxKExD-+Oi席(X")E42apaLe&$_怠韻P0K8fY9(&lxjNA"MQ{UC<Ｆ8Zn/,. {xQ.EK3z(K(猩f錚擲cD坂DQpz+[jG F却Pjc盛/壹S>1ゥS)C舮.a背QuJ) z soe4a9 k` h2PHh2P0(芝H]Ij5K`1\ND峺XZ=O)%姫Rz摘 魑K默Jn }塙敍蝙鴟W杰捫 MS+Q抒僭賺)噴1{De/N僭贐n{ )}vF^BWIO泛奴g掛/{髮!.?E6WX蓄(z錦f(6Hc釜-Vk\ddYj7嘉MC `礇N)h2{2,:V\@& 2M鰻髭$J簓KUN 督mの8d磬-mZ8G HlN.+EG{ [H<>'?f嫖覆Ku hbQHWG官JoeV#y_%TaXQC蟯XLﾉ,Y偉喝LIbgqc簷_b2縱 l,m岩J$.ZeLVFv迎)'垣[7FGZC>fK}鐚uι a6 5P孰adm7 ,2Y丐$V[ G'tvPK狂!0J:泛應hEk誹- [;D-GMpGf(y(3/毓F鐃兎れeXE{m聰6Si^zKpTF0"gOy4`qCh"A8.uv.品bFD@9%'Bi'(hv!s}'柊詬 uQ曉 攬藪僨婁34HzG5z&鏥B> N:Qc偈D9獎^ 3B_aF;02緲t柯鹵氈胄@')u9{6胤瘤^^^VR$: 烟NNN+o$G這IkqC@Og佇WSt>xp顴| 躪SR+n RnA4g2p4悒腓sX\] 叭畩3濡+道`E9:\~k5v<pA}LkF~>-i殄狭. r:腟即HxI5桙V(3eEi/贐慫5v1m. sZd"aLgoZL徊w秩 2恭`~圭4$0e<=1 m*C#藷0:TT軣a}n{瑚拗;w2y`褊 ^-m:w+L餠:匱lS4+v'\_壅42{2.r(hB4$堕妊[榑[Nm展rY9w乢AB+OGTw\+]Yu 纓<;$J磐革HGQBh<|&fe僭U$B)rY R 頽Go肴奨K71' 7:f菅新GIh%bs遶/# ctxe!倡GvT}! P坩j\鞨(9AV.iH-髀Y:f$wHB∩h2y="g oD2OHne}f雍7T浚!м)M羚7mh</E5酌/組\ u)hKCQ>|QJN鴒ger早;o&緇PF c{茫&=L9`<Q\)`G 1(|&toe`k8f^KO7jBﾐO)M不! -F:i畊[\|,衰 z/q N1冊Wn錘V[j#'Gq- EY(Fg Wデm$:B疉*瞥輅嫡#^ OQlC)冂､ＸW彌e38C清 z@20h笘p凉G_澆*淕(u-ca|S%>egD炎Ia)S#Q7zh){FDq'z2<桓(edb\2^飽x富$LFV %b$]=聹R皎l願-GY癆 ;ピXB ozv%}}m鼗瀞]z=*稿|>g@驥* ^?赧do3u(Kg CN【Y}C|2:4SPPER@8J裼靖3 撓j)|D2ekB30Z;n1cXe"<&Iヨ誦el珈Hc$''P9!n=|DaM@励<\xaph鰮濕x腔t耋靂m齲_~O6斐PKON^l)兢贔C ehue|AUB9 iO\ $Mr搦jEYR@IfC$#i JhBD@W9A蛯JG(K則ｄ32┌Q @+漢'燔9e旱癰h)E地X(t暖菊Gu%Nｗ8柄 0K;[*6糎]iH8遠R解)看KvMN革"(kC篩jE )けQf]T餬Le }PHF*08a Pwx{AN竄 %J*}Q餔髭6D{p.g盻劼蹉 h系抱 m柏O@夭 ~徇K闢轄*d乾#戊nK6臭assx粒w通> 3篭is0Q`RfＧ 地Zn 3OZ\#k扇B.er綿shcUZ玲ue莱ZJ Z)丐8;d 3; 岫碵vk]`Ug蠹z呻#7罔@劵z+mJ&i $8Us愡4I>(蓑`○rhQn#/叩.箟jPn#yX`()$ba=?bj4ju|6gh!穉rn#%!\頤+黜;?)鰮d:独o!吼5雑DRd3u(.謎 :H\6Pn#Wﾜ矩$MhTM嚊H痼F>Q!?: O.*r.骭n:脂n3gQA)rYd Belu禿 LQFnVe[堰#J躔3_枌H4KS渓NL]m-)黴-{Rぺ攜eRP8-3噤%eW倫Z/e[&WA}ej夭9Mj;n}G狼誰!2p膝Х7O9r[!F_K圏G蛇zwK[軼銕歟驢p+輳o苙尅F-Y< N)!F 2nh}b2^冲捏!:>;雖*$_B-eぃ)疳< 媒[鎚CpQDUm_R2.房i13奪| `++%/ g$.ri8 9.MH緲'>鼓Lbn#2-#F!舉.儲 E1( #)v8尤qΛzVuUE=搆Vx7iTY Ve_I>-ai輜悍v/巷[Z:d9惠pyrF$>=wueqF}台T釵<十O瞻歔=S",圻f斌jR(姦uRF@NQ B K5ZD+I [8FWg錚z- !;9/q  Μs7 b\g+#'Nma暁T臑*gcｘ^6gu覯iU:)F&~#s顧E$7b%^53G{IL/%"Ra儲[xL[b E.啼*y rdox =Fnr果#N>K @?Zl'DMMa ljb"'E/%oy|\eH[K_%(G-Fz袂呶JJ~M(b9mkQd^舐If揩\写,Cl cc}M踏` yKwg'%1(9pJQ箴螢[7XYW 康* r_>7@ 蛯JJ隊Z kmGjh3９{Y掠Qo_!\oU D季/qM箴Gp_柧檎#濔sR黎D/+F]o{u0S`仲＼地噪98x^&ykPA[掠ZB)钁qS >6`mROh-T畷2Hb YZ┻tV v5]3o:#v))?FNy[+@v7Fl}uF#0FU/Vk9 7ABcV爺v42mzR'臉#DQ ``W(QZsJcv?!|q|;LpeeM5C) g得?W(A'*IMI@M*MFnR(W 馗 6孃mMaV=m顔*?椚Ei6W-F2_読Z3,j~m$bnK>示U淞]_rqQkYlUUM< -28Inu5蹼*9V嫻ν瓷送破5鵈HHnJ;Qd.腹リ痕蛤4Fq $|探e0#]M ~p1.yk0.k1Eyu"#:*"免)攝Ca!$,ぷhzNO4 岬|哘 $jfrK褌NW<π 羊H,} I$ %t0Yd共Tm5L6Ｃ惜2材eI佚Qiqu附{ )濬h覿z6 QF(]Y/= .V壙InCH8 D =]5綸Hb9[7-UFw Cg萢9MN4Y8Me:3Hｲ:Ms4薯d Z;o b l o閭o摺.F搴0蘇誄関^9uH鞦 Ew#cy)Y3KHE k.△Vt}}W*糯fwm1j峪\UD$HNO蛞Z.$盻Q]_f.b0踈 Vす,9A_/3q=m勢 具X1jU(\rl T彝OO(gき貭<'hm)e鞏8 ,3';m甚?7旨b E+)噤$Hl-!Γ搴 z1$qPN% #X/疸0s@njQ.H垤b}hsr-ol0.T)rE肘2@9Kv勃u7OO~}鯏?x嘱仮叩盧m甅7yJ|Ws.[_~Ｄ=C麿謠`.陰m蟯甄}站o^|rZ昊_頗/_}裾衙?鐃鯒謠杉髣vMe偵厳&;.%2Qpea購釼7Gw=!igQoG検トcU.)?IA賜56hzv.'臑s聒dZG聊:@n孑w苺jqhPE乾O%Dd)uy夏堊$%\SФG y荵e ^沸u隻穎(rOFye@VP蚊Q,/CM2rW J7'R賤儻?bH7r蚪Xf仰nx[RO Y&r/\U]z>yzじ/bQ 淌>n|O溲gA] a'擶磔%|t}NO自獨e縋庫w#lIA\翠H)r`諱p粱迯UpLd\晨梢g鈎六麻==j>n|.v{h0嫻.w似D //8. kTZ(k髏H井#0fy遞o評滉乎x銕I:r淨p-際哽寵腱$橦癩F4v}額КU;捏xuEQ觜dNx膈CwQ`1桀~CzEA崟驢甍?Sm]zE?LE蛟憇%憤]'4OW{Sm序wv矮>|w/ !{@:#:田召形/_P 偸朸NTd瘧ガ逗de`lNag8搜ae塚cvD３櫟h索% 4I c諢 |b%6kQb,$%4鷓pJy喚fk}~vQq2Q匐UMTM\ *P迂Wv#膚D)w' 傘mOWOo&~烏7TUon&H杓az溪Afj楜(q戯)<汎iy*2*+噪YI!乙餌VI#;=<}祭ob V打#農78)ER0F鐸R 焙蜷I<;EX}%k繧収芝-値退s`%+Lj甞\P9眄Jv[QLJkQ 96d崩 G.(V< 葬粫X,XL吐霞惷| nn4tUMUT+Qm齊j# P>u? ;BH.Ca(兪zHTF4餌fd驍^k型冓 x|+F1渫47E鰆dS扈9寂yrF[lCIC鐵;墅=?8 Jo=ddQf膜}Td} E#I鄲講(%uks7S´,T姥U~簣kYK0x 勢嶢ykS q%v秒悋^7馳n統fXn/深Q2: \luiS!s0M詔N7g郡増zo駸ClシH& ib挽J》f垈6#Z4sniahdu i憩[{Iz杤5酬蝠f'.6.孝e~8}wghu史+9zy;MP匱_領D郷ォ俛$鎧栩 5W粂悔rw{}Pg2y,癨虱9^W~fj_L@佐 m(b旬毳\酬,G竡ALX惣9善>靄歸Q`tw]-x視bDfC穰酎(^Z%#TZo榛}`0苙]挙普癆SQHZ) 6:;=*x沙ctj$1omr釐"]No号黥尅證9a(uHwG6ga麹cw>_躬1}r0'飛Ppivp$25myml})5F1,諒奴5hrJJ9Lv,S)@+u|p.R*v3FjZ]r嚥*\枹5E< ^~@J読pR杭8U:杣X鋳Rp(lG00=KQEnx+ lIB ?酖;6_R轎?只  ]MH"'/%xgDEBj;+NZ,<97F ?meo播 \$裳X抽MF@F<23Ch s0 gBS893N穏B5ax/\[規9@ZP#)T顆躓{TH}R史dKML>XMQD 捏uNT)$櫓6P性WSD物Aljt{\jrFh7v V;y%72.嫣告_ 澑uE22P-QB数皙亀ADY }l]S?\]鼻=#萄9%xt埆7Y勝a髷14宏 3M蒄= MXL慄*=NBZ}y褥j郛&<2;詳S+語蘊Ee-B|>H!L$&dV*紮N\X'gp$g]8Dg鎹q5Z筏(q+mFg HCWg昵@F瞼0%似蠹E7- ]~e\ @V>JQ4駕⇒vP%0CB冉n-\峅Ju):稗PQ礫EO.^J FYLst4凩a$$'##FCGsR皹3恨p.5*猴QL|y3J姚( (P越Qcy}D胙vn C sE蓆PBx-2挫J邂_<3)fLKIZ?)O":&#侭'拗`?^F l脾KD睦r'HVO;1t_.K8H砦y2{H u)e姓tj - Hb窄 >sJaB5EDYWY)KN管(茱SJzd"SI嶮\\X 5^~k?ｆ!p#%品2漫.Ь1E慌-.8#V(Gy YB B\ QG1[.fp罍'){qBdUFB8;Y&2%'可(L_  靉@:Z咐F1 J-W q@壅{` %?(*樣s`忖u)p*GY#s┼upF簟5薜D+霏埴$愼艦0XW!吝掾'榱`1d香>:Z5\y!}^uP 2 :拮繻pwpO)鉚'臟`[笹M~,*sU\ 榠枅2k)ur(TY7H析}(%U矯F歩簟]z餾pKP8Z蕪Lqa.1NYK僞V,aV縄S[IabfKIaanOh7'苅ヾn6槻{Y$5^fｈPI lg吐h#uX/Odヤ: P散eqHK&迸灑 JjXhV,8xhQbS6rZC箘PvU'=FYU_hsQi LR0普K`Z:FW{4囗Xfo~w gK(OOoR>CcJXv7"對ぇK/%Jkt#g #w-# _晩 糾i+鉞54 hZ1#AG&HF4鱗@<3馬 F 牒';m%k@/@6V'E6d_T5幗$A=欧6)`濤.塚ql掬xdT7":J20粧8) ! s6IQ98+嶽コ2}P簫 apN]F偶=wi O滓})决Bn=S)| 鴃oまm;y任 u缸|)aPuylwB ;享隠0UIUＷfR22鍔硴d& yIQ隍:(譱L追l:#S2Zr群寇<~)礼汽/,Al,L股8<05,u_\舌Q;8芭A=~c匝U5/F0c#tk FPB9cw尋4紆\ 篏|,\??r6&a5R檄XbV仰i7>f82nlpJY84鷽mN啣Q`Puz\nMY蘇izdnLMlij }珸俑bXp韲zU"3茂d畸D┯F'=HE?97TAAi 善_F2|'wk残J紛 p=UO9+i7.踰U$/(g磁&o <{k概Uuz荻5x>]FozlR dn_!'促X5^V\ mC @ML 6b{`47K！6m听!7D[}DzAM兔x %5ijr1j煥P;#/妛E畚T5z狠&J"火9 iq:%zF逎垣QJj`JK-駟dCWn9)m韓>yＵ! fr [k渠淡jjkZL!i)|5}`D鴎%3D#o5a莎<  'eZr教,0,w<擁ブq2jJ珥K&昶`揺蠢4[ 瞚%#G~tg $G 咋!e\tgR耄$郵=[OHs^pJu`脱Sg|?jv/o跪聒P E髱B ;釼000[燗LRo}clzZ懿l"lEul.4 Wq1_&e恬tER# o;lZDerXl\HI擺2kR駟杳i甬桁U誡RC[Dd`5- aCaG塊{Hh_M*犧End`,:+獏EByh$2鵠XcaNプ卻譖jj$迸0W胴ll?)博Qf;w逵pz%UK匋xakz辛{zy鑓阯廡?vo/|{k糴3R`店dg Z背T~t.ISc ?Og(PpAgDヰ3I雖a'^Pl/AI看X睹4だ(f竓 衲#G-弼d -3莱馘傀Ｕ#盈ZD0tIurF\K丿%7> (yZ9y}5l榑E截]z+\'Ｊ瓜瞑鰒R"?nC g)58槝Km蒿,踴uv {h=Q\1/\hD SD{ w'`&P D叫(9vｐh=1 Tv鉗1F涛$乱,Mw$徙dgＪgQDA~FB%I蔦t1u4Q^ 躊6 =| C#pZζ82BIv2P媛Z 2F骭 C▼Z}p.Wou難A=犯2e%dlZw@Q櫺A7燐"/q曲Zaki繃纏]蛉S^Dy=6~)綱÷@臨RK4[y昶崔hKmu@氛y,掌<y)Ef13!nSg5吠 X93hG)v鮓E{vyE.OE淡K\ -HＷ穣qL狐$;RIШ? pD}K\PG0,b aX(謀沚桟宇?Z8N)^`)k8徇 wJ[*>SXI(Dc斌4R珠qwknSVaCgn＜oO嵒DVYWLdu蜀8-屏 Wk%j;;k1さKz@0K09%#e)s'謔Im把[/[ぷE ;go優#脹_u:[]靱swN/n-+B措５}$@@-#/0z"Q KO)N* |26Hx^大u *A綱徂墜俳79q覈+P+-K2m+CkgdM^唾息V_6m)W/,BK簑砲@頸8^評 X"V闍0餤憩O7UiJC粧H5,,O_; A探 zz-7JP=蟲)ATLD*Z\T衰- 領V@ 01`g}.黙(?%1mc04`hSdh(!(冕`hhP M瀕　04tV"hbj経d辧DTB+=vV@8 t(9Hh影('6m]eW\+2l^ 紹:ybR2wp噺=3K昌a$橈]-w遐\,売\VЮAm"NBp{\E8{ DOZ6z a@Ij Y8貔JZ讀$/1G@m 許\uKlmc輯6撒FhRK恕=Rg .)^.)90硫v%!< ~U(<Л聾^化覩Q4I[u]篭>%o H/Rz^6)個5迅myU []騷2Kq?^V+篩罘FPp%!馘榻4系ozU g ｚB<6圖Rmeq&~?"F欒宍LI,EI&2V5]m7#ndd1w椁/檢,j%1zp獘\K4"gt琿zYLfS滔@AAq.5#`9(EZ<O析Y<泪 ok)>gJ* q梓C]籍&K棚白5vPPD讚QeeGx]酒e鐸6秋h7TXJk隹YN6,8u.lVΣMK抄┯U舍8/nq鵡m&:\rW&/dX9*@=hI]cFﾕ袖>nu=leX从!翦(W1謠2丘*F x丘[=rf2燥b[MT七"pjvL-*GZwU郢7tS}油郢貫K蕣}v~ }#LVp|x8U?:"Aﾋ洙贍+轣F疸 w K摩僥篷νs琺'2wMP[舗8伸V2K[Qm5肇=%%=抻=鼕ムJ[v@ F}時冪=Rb~^>万>~^3> imI(cNi殖a|A挑~炉 S*j:=?^蜥s3x>(3J冐.任>r雫/昆JO;Z'嚔OO濘x{{y}yZ~ 将/GkfN鑪Rp甑|\{ |0 M>-:}:枅{個>竺臓K`FG%+R 偏2buc(跿0趣Qx.AKahm送嚢夏?:|y|t;?燵u南 fsw+5判)E@g●渋QJ_ERwnAAHfCyX!舛89+& SCAT`(:綢2Qe}柿y|.:jBe8g -狸)gmIhfW端瘉qq!Sb{OOml>鷁a^戟POBv8kp*0y調 P6弸N9渋W,s -}琲癲運i嚥花 0sRd$gHD識埴縡|r薺冫 廸yモmU`-是棉$9CeVF琴褫K珥9S裝{M{軆>K8Y硬 伊畢切a＼w裃LkFxB+Ni.(xI%/g課j鰰d^CE7gvmdC/5 Q]Lp`蛙*:巣=;%&Fh^)鍠\梧BS cu.{z2儀~7.q0斉( 4偉B!鰺贋]]#撚:d停-TI.:n1篳\T隍Sn_ j仆{r粃0好m止-5w& H0趨eE渣戮iiC.泛b'N!闖談))M.a[=M礙s荻越fg)册a}Jt0'I∪7&|*9}uy~W?K*Ha||ラ^t拭!葛c;TE;TP#sK. 癲嫻Zfu!Z簑nC)@R砧逃.2QF Wg# 釆W,刄h恆{繕qU=ro J巌~aR<$#yC;iJ.Cv:#sC)n$聲-邀8)J扉-鱠GVNU/刺r筒(r^覿h P[c娘2岬riq3捺0iB桁i+x{J%$S冊韶蠱緕}!q3脈!$`X懌$DgS 3c0X!$h_R;e^/RdW=5＜9/m*trF旺鑪p;$C>D絃長huF +&Yu澣/[&IJB^gb13hH宝G\ﾌ#%yihiw尾謎Uy<穏0\:4晏Z{殴殲8:礫竏rZ僑\+投rzr痃5[W'薺n=%gIT:#~JHs旁｀68:&但　CFE8雷湛U~uf^9 麒I聰宛f$じ_C]Hq4gMcK1e撥kw`qq>+ W捺B8 D: 凭欽嬖 |歐*E@x 蟐1dQKb∴1,cGB[p 伉TΡδ19JGH: ri称L m9HZBC鶫}oDS]]K拔黍E;_]{9＊ E(迥-山 aC,((2-TjYM5qyD碆ｏ批g S鰌+:姻,羶^ョr0ビ=/肅8q(LI84dY&#苗`k浦jE+[ YZh0FI簑 抖"k[KD"W!#然p蛾+,UI "'&nZk qAP69QVDtwe.+iSj>Knk R碧-FA =Kz0$3Z廣fU待j|割射xNuI P\b4 m芥2 VRx9 T-4*+Sx凄-FuQ"iO^奉n-皺 F功榔E&樣窺m nQ  b}nQUGM0*6qPDoI逃1ArMQ):K眠季9H+KFRC4zR>Hs!eI)|]g*m,展bY6&釡8X[gＭ`t$[\jRjO\k I&G滝#PUr|→dツ,lQ(B|p3j"趙|逃Kq扶"Ug<`3g3|&U浙Gw>#gXBURG8A9l厥m 袮PUl*FX街\%D痲PDV/R~HJI(ADhdM+WkP9rdmm!建!q襴<^F伴T~Hk悒t8I_/凅%4Uv$亦K8%pY凄)&3"Dq$-lG2斉lzYj cLa叉IGg舜dmGB)EZ`3~裂!8VPV}Hc)殍d険cJ逍!iiP!Hkc園?哥jB▽8Y6J兒翩("； 緑Z^dNX譛捐Y=@z(g u= 妍0P垪~G-1襾Υ琳F)1嶷"=J*do=拱Cr'>9TR!% v[坡0=.FlH!6%MJ&,>$KZ)CIj:cPZ]%C_弄垠`r&屠惱QpQ99~{SB=(縺OyK^魏:ag簪75TT硼= 扁@;(i%"X539>)INk _"炒Y]G(m|G?I廰2B!oQ0&%p#UR9ｐRQx (}yEK%VNtJ17aA┥2槲蚋笵疝3z /Aj\^瀋k:*I&sJA;pfsY叔p世c塰汗{=BkQ射QTz役A!>|xdLu?0MF$烱&hD7a8UN,U隷on 5&)S)YQ写繁`=2 茄z 1q<qHＬ釀w/粋]徐y８)u'唆愍!_#P穉W>邂`=dｐ)+C M5~t+p/愿逝X S wTD愕X0pKMIzI斐4eTcRDrXV(faB\!U綢[憫uv吠?\@mp韜唸d}環=A.甜 ? 篠>喘n}^{Z{L肩J2"厘&ト!J9E感抔4`掏0MC[懐{ l?盃$鼬aJ揉R虜[]/9婚)E}(Xd3(R8┫筒肇Vc}$f%` 0)E7+cTKS*f\Y$嫺eh彿e-QJVJF班;n,3N4eR倖亘4vsY操JON51o岨2睚&駢s薙吶"z計N~E,4P3~Pf?#4kb)uxВ(帆囓-紵o&x \ TeZQ.tR3. 挧I9J96H@EVdztk,敬%B_ニ#gO:%6柱歟'hB/%'(=襯tyd$退a+\2;$\拾Q跖umN A吁G.F}/i6zy)黒義F!JriCu2|p褊NoO雀ov鳬o軅鍍礬/逼萬^~+%凋Y]燼k8$\H熟g@WG^喋I"6n癪/o@4 N7F迅r`~,%K02]\~,閹#Y7畸W諞/j錦%6寞{h(X ^↑xEBihY#y降Z酔屏,ガE)[R矯-宣VcwWe貉+ 椽aS`9%a 正9ＴtPalJ舵U2薯圈(萼h"dX避Z-I^(sm,k"&nj}?孑)輓ZR2呪lWU-Uou3yDM( [Z^D`y27f刻?逸蚫|Bwc3聿wOD陷Be_皆U梧gR瘢蝟Ql./閙v癩櫛&u"燐t癰g凜C?QC猜笵gbD=~nIuz.dr'}w~洪pOB]醜 KhU織ux=醴qWIZ{瀰!>~}K&]秣JX.葹鉐居蛞=f/j觝3o柴圭oy遑t9\h灑kh兀=]<x7癪us _Zbz$粮;N浚Q註NR i[6rJpV愃eltЛ繖S[勤wＴh*ez/B]6jF4w嵜S纐L"x線恫訊@O<^O/l<シ:Sg} 遞&:鈩55A$8粍]%鱠@~v暄沸&~pzvmjh係e0xjA]{#}3g/淵v4GsU跏Gp賠3>C sh]壗}5"+{Z瑾柬嚆=K刑"W*湶kW}=N濫H<j ukK SR0@?G~防9窕pbdX私s<3]). {gxYｶ8 (&Χ`?9Y 印dW|HF;;鬮(9)"埋馨FZD貧t\?(t轤離щ{3 yg{昭)%傳'>t樮蜴p#Php~:撹Txi闊L<_>}x昭思2&珎Y#oh3 YNL@r<山.!麁x嚔蜻c7[T/4n蕨w}xdI藏>扮s+鋪0険箔k|.笑qKjjPN<[沈x'_G愛} I 屬 NY鐵 O黄 qx海IiJF/9姐N)剏wё}湍 ] 8溟困4鰒p垪6I徑1l沖+覬$N|K y^Ei-i^豎kT駛mk齲繧|T iMz7辭dI.s辻dv∴;2^娶.Q$)"1frhkC[[.桁E[0 [鞋x&>蛎墫<]jg]]榎Ao$kGr5q資 l3,NHf>9[)P%if∴寞zs蝠I]ス(M:U斜s檻xZU虫杞濔館鹸8 EHjrnrHkDjk#p!0j3U9b B4a,%謚;kyiqb%M\M8;46bH4!僻]9}ZFj \l矢臥ω:)6-J~<.A+y]\髞L稘H見8/+%t{:" .N| cKF旁+1;#D1+38ihd砦mD8P]9h^=2y% PoO_$廛`i%9c澱aL9%攻$M\j/帛4! 鍼}U輊Jd49iT@6@-/{;9FQt_lIb鈑!nT浦pY^備W(y}9檣-% 嫩yd]*g/K|&qXB挺;-L1-e奩IF|q憎YC弑逓I5蔽6批.{WU7羈-h-#r.dApX(/E#營懸(^橢m鯲_:x%8周Yhx腕哽W8裙|;&xz|籐Dyx7J?'梍I>梢 @鋤膩梯p=zVy)寳&pO椦頗2 >鳬]u#Hワw{I}o 弟E8kzd 箇X_/徒5H$knwc6k邁PV;#聊FU/5[緩殪"隣掩羇∵>鰌%knm)xle - >Q.ul>(r#m 6MA_4LAcI辜 ($_I蒙[0Cr^j(f&93汐9.9a6RL双脛d" ej f>爭懇vy'~鹿8帛鉐巖pSvs'皷__8v?F8cU涓IIR|ゆ乱o磅 椊&99.W? ] >a;Q\'姥 瀁gxX=踪w?'工m9+ ;鰻?9C湍# 岻'併S4[Y/exw:?<=l笂E<淘2t掫ou?維+萍?"鷸__}K/HN!N__Q j躁~止7墹QQh5耀糀yOW%!)0彑7X匠])X蜈宣徊徊y)stZ$BsV)vMc\育N濁.:f2~U {C+罌C)=Fu1~jGG 7dюA?6*( 7 L=樞n`"G5>r"-.y1鑼'5; (YMm hｖ #saey皴a癰[<4虫墾@U<"吴aJu (d(|刈借Na=# [5.8叱yBs2 5=q6(f妍z^{ 8 j-O訃Xi_蒿げxe5A8nPV#! skxkUZ喧蘿UCc"(4#ET5m[Ujn揀H儒0(N~Jv2! a~B12リRZ=Hg\r供 i, EKbmo.鯱%H@N}0bF)j▲\/qW;J)QZJ=Z罵R韆1D1肇CAU8P{Zr弘I%>q4u#> q$n>q0Fw?{y'G w?j FWF況7 ,眄Yj_z^鋳屍j吽9`7?傷夭e>&E}!TJ@芹qfC=枉t0[CA\)娯|O術'Emp供'c@錢QE}部熟dZQ粳邑]O +ce帚\bvnsb-B6Jf pe 彪渕g@Qs Ir3G9%l~[nqK$H煤HC8丶E9召>2""Qe4_g;Jod-V+(IL6童mq8箍`房辮膝Nc;*嗹ﾊ4僑rJ G臣民遙&.e4=?O=|!Q dGh82eu.Y++e峙epL]J*`v:≧}H-[?$O\参k8亙${ :┝~5Å2\=LXe;逃)睡d8ｰ1*iT"aSF5v{o8 ECxC ZzP}&C]覿"篠PPiX什黍 EWwiS[卓v章H楠^/4i∞^枅睦#X1~虜HI__JI逃.cu葎 総禰d$癈x=0g"# [F牝bBg"oE潘Rr鷯x}kt+ xT8^ ;5娑>RJМr躡m&gkgm7m*胙`Rs描}YLH厮TKUUBP#qdq瘡埼g v>K,r*n/iYL摘A?1鐡痰LYM-yOCΗJHy1 x\z[翊R[世G譬#*搭G*6Q71l^OPr}Y蒿T w>浅y@PLz& s弧T4閹TdP窺O氏o(q据pyH己\vr=___1xoybTpj慷"溯m+a?~辣=o'.e輝壇3澡渤\玲*%OoH亰\烟d盾`¢6V蝴遒i)]yv2鐔|T壘G@O歛?]wc鎖;9L#W$Ha牘戯I_]冕嚶Iaｯ蔔$nXI65c故'Oc9Qz8数y7魅樂S 覧銓ty`$OI〃lM菊GW馼酢萩?汕瑤黼#&|H_};Zvyx ;7} >D1wv糂笂=rzE雫O獗hsyS壅u,x5L(霙UG] z{瘁 bfqZ=2w}I{o7sID皰欄'(`eF`鼇肪-ko/ /6oy頼M7N稘8躅.髢y重Z!c齋z巴3痺据 s=50~>;譖}m=X旬nD*$C8lN熊_~gn_9JdiBX M(2X[wB)xk&FpEBダNY[Cq' Bu本巻'c\~]F(S(>g>b}C'{t<{E-X(&F0VjC罍hQ剴rc^8jT$ aJ劼-jsJ=>x奴6-KK摎V w側%托B*r乖玻 * sdУ"XE\p釉y-^\XUQ=i:iBy歳Uq)P貢\48麟ru,b,+),+,#∬ Qug-ji!-\旧h譟績* .5+y\zx"JvMj T%!B=JdY `"l|Q稠.` a砦輯ts6鑾 &J*5Yof馗rPFM槐MeyU嫣yZu&じ恃rwUm :E8v rEJ漑UfM)|' 鎧徼x.徘.(v鍼７?DG{Hgソa9!7(I\(qIF#$@lB邉^瘰Q>6[O\z季9\X望 '>↓ 冉|[ﾘﾊk)GK\[Q粹59L E#!簗〒Z實k延塲會f#;U$vvfgLNYQ6飢>-"冑衵MqQ72/捏V噎盖摯z °t( `m9S5gW[冫仞pkLTSr秒閥萄8价ff(囗ku!cD36Q sKR嶮李fY)狽R7X~ *$邉S15b+>,?Pv=BeO脣;J忠o$ぺA70o- -0V厩Ut価 絎磯$3e=d6ZpZ(.wM3}c劭 征Nto fK1,*=y3%ぅ,殯>O})i%Sn3%Y\f腟n\搓?|切黨%>wY|QJ崢 }塀類jrH只.$dI 喜+含zO@1圦Iw ZE: [7l0們bU^蚪癲$[HN僻Q sJo$<褄f-VW5Fg1WDL慇l|x)rSt,Y鵝-Xym(#餠o療眈UoK=eB7詣"|t3" 馘:W \けq-\４HcA^2r 栖 rk籌ょM{7pW^8a(y1Y震a齢Mu裙盲:yD>採>.*<矧DQ容%LS}n櫑~Cw/BQmQ.e "P]毓f--I&:郵Ｂj(廣=M欖PO烋診 Olw.釦(6噐,rtz沚ncF8q&_澱U|v2%5]繻慯鷆+ 遞=賎T]渮lpY歩-"\ 孜秉9Q覧_u;蟷湊(AI妁5%a,擢 E搶- +P0Bｺ慱9_J1%`.rbJ寂 k./yE5gqA6#p)療AT裃=l<釉晤#j$ 菲]烱:dBN $q)舒eK)# | Fqa1#0DWL;.1Q_Xh c]=.田IP(9薈kg」"~s込Dots{齠破e桂RN營嘛O酣圭@√{T昊Y鮖Y'd;$ 毆>蜒羅A\,邊AqR ~_$+W#\!l ヰдu噸A駒eXC)甓艪Ok]代\*M;畆b5tC^A師b$8b{s沽J忰D亠鬥T魔:A仆}.tn1\藹bWog={P蚯F%j *:Z66旁fZZn!次e.\|mC餉c y鰭7(3tN&偏Gd(hd"mUqLxk `\朽J9BPT7Tp&Cf\Br2;eK葱Jdy[0`z |dE ?,aH0`$孃7 UIG淹K8 I\檀a{l$粐00蠏W{Phc\刊U Bg YO(汪4e`Le標4>P3")條1$ymk:rUysyQGD^fer)Ыh杰 ,|/G浅cA-碌Y3j併o廷o~G*85_C7Q}/Oね^Ju-Qk癖}{ge4４袋更aLCuл(蕾os!+櫁UM0-A 験bf2"郊堕LR|P9Im-RXusx` 狼NO@g0ZX-倹K>偵pd貶點\93弄狆婿+G狸["X溝Adi鷯$Gywe\qunA笏蒸蜘枯o^R滓e$2}ATR(I\<~ C= -JW薺}戟_胱oq恚紕8=贔7/篭挨|旺rb陸}9H率.(V作u)蟶18D7nja#巳P;A+"of^竰|lj蕎H6崩9NjV呵(q0 R !C"嵋fez5肌5O^4D +v嫗VLLJXF0A"彷x@7鍮吶.1槃S^vu4}籤G9UuMvThZOJ@Fe ［VWf ~-90EC|EY025ie6p9pF@ru i? e 3e S殍!>Pf/[0Jん8BT約J!m K!8'v3S{[3K樅%p$禺8|軈郊R>1(72q Wu O}KX$#m9J =D嶇jh6/4QUMpDЩ逑m構樊{建2,=4冒U午z]0(eS s Y才WN滞vd\R9<w C"rPP&Wh/Da,} L;6 70"/t9Lv,X%蜃c拶%G8'M轟( n篶/Ck)3讙NXf|U-%P@侫蔗}v#嫻k^σ SBKR>鏥!5D熬PDL}#)*$7C爆WCc白競C爆uU.59%e0,戲1>hB 眞T6oO`*禝Nq%駈@g@NpFf\=g"A(|R|g臑夕*w{fK`|}Aq1V;WtR 0mQn/虱|/QL╋~穂B {ZpFEDA噪D茜-史%`y9@T\ BxR<%*+=#^h r` 纛s`0:KI蟲喉+%gLvQ簟唆卵E1S淅g(rnn>銀A杞dSQY=rC yu6,dc 衢vPJhqど{f-6z鷄E 9憾婪6lk.Ld 3眤4th1 '憾{4閏@帑3賣/6MgJA9AfaEWc_q竿w-T/iJ>茂両 tkG} 裝7,Erfo\pｖ)j 愿l / l ┸l Pl@a\`緒.0S從qq莊 %Y闖9`%|kr:櫨gS舸)H0M" Kq竡O騏dC#|CxeV^fF`f; /vK+ Or梟HsY砲9麺d颪`f)抔S;YM DZ6н_U[pi.F`uAн蠖鄂J~$40_>r0ld[qUWXm|pH/@２q戻Om@]TFIeoEＩ`U淦(悪W]0Im#*雛Z\:\ O Z 4%6;{-{r@7籀A r%臥"{paBSVoI:-淡n4se@ Yc杣.Xh3p%n+%hCe4/Kp'甦P営FJ(、9質&QZ!爆櫨r|AK=&sxA N!]$\K%B -析Hq叱 d1専ILQ`-#Sh=E5Xp-*-L5N&L袈dAPG ygs.Fx$-ge蒲 絶&讁WO 7$鰡p>_踝M罷J;y=z７)])vХ 壟桜Ro@{秣-mN^3T2x蜆w&紵恊]cx{"戯6霹9}DCR$l^ r`TByfo9RwQ2lOn-k CC辧P返a0:(肢k uB醇x鏥k沖9 凶E+ r15$,V1,瞑櫑q附Z5it&箋E澁F#輅プt.叮Gnc緒鶯]蕊Ъ@j*ExwKn魘袒p&/U4Wi+{tA‥z務pl[vIL^瀬n麑Tt q*X O~e(jZu]C9 ,kY 襠t影I寓ｫ囑升$l\侭vK椰d(寿 b}ぷu{fbx]V.~}MG_gY囓kΙn:. WkD(\隘 衿I施2ll}遥:蟄gy庇m愕A儘k|BtAsCL`{`ﾒ丐!u鑽@oHDo団aヵ秩8h o^_SFAmMM)z單Do"7懌~l+O5)#m7i"浪票)W稿O林 oqΟ&r[Z)I灸哭shQp蹴IN"Ax9mzA噂!buQ3%r!粤zI^fdEJC&\_\9xqP39 `]9#h&ａoo#d$gA壙$iem"7Q,助o":au (村j&?(q票 j44ＮBe%dH XL/-)tg$ "[#y1s40vL 醉)_p琴櫓[ sq~釡仏>,v;緲曼~]q4e67y厶c-$)s X>i?-休.合z|T(-舎aV墮擬ir@:AA(,=)EvFC汗gxMoGoW'淪U7<-SU "Dee c5 q!w-離謨vgЙ%]t-3篇;IU(等T);N#-{DiC$4鑷shQb^5 (0~ER)F GvT韻*G%73iq`?q%e }DqT稗Bj轄w 1LK:託T& 5uFI8q丙}幀分f;ig{硯D臾A5o|L^b5etU 棣0i$ATRBRbqFx隱R瀚R\ y劭7預x拡e;ジ"F&2"U u}.御愈EsZC]pO祚L7翳lJIEYtS>iCIs 浮iAxoQ,- Uu)&@xep灼鏡舌0{%牌q~q-<鬆bトeP4]a2lp(P,]q!@ Jz箜)P0.{ )]zc(3蹕しC((獵果{r新hBcw]Hs7Vn欸QW1籟@.RQs iG剴a Jj箸C椴g堅B{MA.JAn(bsど)C.h^Frh#a+YE\qKFZ%)_3\@]兆駑M2QR繁liN/&n&rC畄O;K:je gW;]鱇瘻螟OcJs^e.鯢z矼3c6q銑rQ]o$庫uF6$X|廛z+7%ktlヤ 93-A*8?wsJ-` F4唐b貝 筺l-t;呱cD mnS)P\├~C>鈔2kVOm"廊$IvB UR_i5>~5Et,4(!h齲u屯<7綴i>x±春kA=g.jeP9睨5)ai朮q d^u);Dr★J:#u2 +K％7腦r \w劵[?箭2)5;4Z蝮雌h.Te]砿業(>HY/匱Ea1-漉o風凄IsrKnWB#9V=勺#贐= 丐(i WgT4甼t藁^癲4Y線 '9呪,Khq3Q風m碓bsD`d/#刳u/e7桑兎砒愼[m疝b掏FB7F@[b6mxERE}19#dN{63D3n4GS哦>K'匯OＶRQ5mRsE'U甌6,u!yd> $rn3j 8#Y:>g: 摎緬R丶>Pdq.}p.:+%K.家#ZL悄-Do1BfXt蜈K衽Xt rbJl#n忤A@^bj彑鶉vD嬌{Rt#vPﾞB^VuLX74＋rZ t>」Wx靱0,脊N肴+n噸cca畋x観0,bY抂H9'|晢V (+YdB菱b1嶢"[v.-+I{B[CXv 2:1j4!5X4h79S寨eKvH.%y←%j7CJ`_lj' q-艙4Q}D牽裁>N_吼`Fu蘗r[臺%}q!!#4A臠Q9F5CｘT:xrV[M>.C/藥 昭aLBA{!/(5C~變jg}t%;mCte6R8ZkZ9T靦黼蚣э%;\I8SbDIm$gCe!$X$宇BgHu(RFfh7.C3y]d鑾m@5%s&-&r.Z,弱 #O&P五]I觧肪H闢ryxKanh恥 #<r"1'%2(煩\狃Kr ë5p#j#IEGQ%( J蕋Gx=Q槞]Ut言'5Z-"iAＣ)TSIS:)1ro5qNqY$k %業rd拾q蔔夏[D~奬0e^F$ZQ+c=[FZ0b畔Uk贍mz=.J~d6[祖/噸%" Vnw. 隹(e+(l$L箍DF=mzX.;RcwF6g v睡mA@ -J.Qb遭 D/@堀せ}J4Ul-A.JUm)噌3 掎[+纂-&gA裏<麥孰壷*%rkc%M48葉I2詈kAW&xHk%)[卯轂"aZS`OR霙nc?|`J~)&5u!!G/Vd$ｬs>?x)pZ1EwZpQou%浜oBA!94R2vIY8+F[掬n\竅-碧慘f<v~I"x\ e鮠d)馥7iH鞦 xO*` 3DEc,7BvZ弑 tふ疥UcS|4pj揉|PQ衢^AQ*(*H;4GCN52bd\談U握=I購U#}研B『畊LFA~2rE( C_)E#fM'8<}d+M帚2桎J9J槇:JB T嗣.QL'鐚k ~OI!N^N|%%續 r蝠BDi@紵耨zZ1jjHmu4G蕊.W蝴DW8鶺gXB?L%菟.%,>IK(d5Gv(v 箜AeJh0xE領O茶e=lzdvJ:5K M BmJ鴟$!(s槭$罵河ApqDXw 3環 PuhﾕoqwQgqlC$e*6FqTTR揣f<)装 #xE亮 惰#3 6涅 "#o&VC鴟OY z;&2橈裴~BHcz鐫 e7F僧烈0eMa8瓜r哥P估 x( .u[%F-亮JiC eem a\i棯l|f]SJ漾r妨C閹p Si$~<嚏%8Z &xNA/M技b穏{gY]U,ToQ\x版0C廃m?O^(0>獸.yq^r盧$^x7鵠緘[AT&罍rw9 !\ cQ駟Ιos`oiMx&Rvl&}, 秬7SFX~T|敲cs腹qFG掣題H陌J撤A[廰q $Fやh#eS酬([l.lE摎6Z+EC鵑U襃娚d]TZe:C)C{ y&I,.D揃|┥O旱a9WcFqm"igskG"糾=*&-E5M(ve7[jzN(s)羯R爐Kd~権M;巡B:d'IOX))團 3`PJZY2喉diъc][-erne*4zs+G湍|p杏堂2bs鬥/>'{]Z橿ET砕w8j吝;0Rl6GH18沺r(I\)N`x&縢Q!OZJ7N幹V\.:'L-c矧阻B&q99[NoZzpg$肱'qI鬩几井々9eVFEAldVC'@A\f _B&X良JI:Ii4,U5ё%*MOI譲o~o)`Io纜F堆_R5Bu(3=\,^Ge{能)燈2戸妾h鰥|*熹K}恁HO3|yW69筱2&`7:I,f+BSg#孃\%廣8]]'p*9@(6bWc徴Ge(_u．-J]X)m.b$B冓7 晶Q士4uU苛'鏈. 2MXC=N 鮓O瘤 /@U-3(/百慴}kK-濤&X-H%)cVTA}MT@-t VvTi%怦 uKe,,^;_チYy2 Qe唔 犂lRYw2,4羌0DI ^P p?8#3Gs@kl\)匝鱒GB 萓'Y罎1j雛J7稗{$ RI42rZB晏會*W _n}'j/ea4･rC9v?]uH|j-】rC./)JUup檪鬢稗縻FMQ2}mNCy薛梺7REC]r/kh7K= Giaq杙篝誇 A2@&f★攫93始u`m.融6 NS}査<~減漆謫柬 A晶__\醜悉v?Wmz嫂約jfMo;"2 糖M .[猊B#雕吩] 5k艶iE\(K9@'dtgx!Д}n.2儂(E 狢l1Oキp辣;ァYBgM清穡k==`%.Fk苫.封0gji')-&B7lfD雉-}$忸u!1遥FG`h&tAY匐K筋:奚CS %~aMk7a頑Xo\pW嶽梳GZ剛CGzSy殆q%ｲ舊 0J2H9s￥4K{#灌0f] l-5,>Kb73插罰t`Jto\士RpaMY q'Q(W5G汽#)RG耒 廩}啅5<^g>*03rt @ 7kez=番U 漂-DfW !ﾂb § g@/fh5ウ ┌;E<wD叶,g)斷4g蚩R横m揀L}}PB,EK Nx<0 a釘{c-j3"3rk蟆{.@,498xW[n, #\5CJuOgSPm66I謫鍛kMG2*牃ofG学^>}dQ<場烝`6鯱OLxH07=ゼ=>>本}P蓬r~q牽e^zG阡"i/O?:差caq<鰥繞N:Oy}x8__nhX58曉cqKX$N疝~9 R"草~tp~載|r~梗纂n頽+(x~・I諏z)W狂GLI bX5E)W2F W$'苗 888_(([卦L(^託\L行)}I4D尸4JP29嫖RS悆g2Vm}昜#!fgUnBh $:9麸枝=k 0p(潟H糞f$dl校BhBjsW[B)`$o{d0慴a]`來|LDJ^JE lp>]]'蔔Scm 哺4qpv5 PCPVF竭Ｈ>4眈Jp>林*z'ZA}wy$'82H』RR膢"鉱sN C鍋-j蠱-瞠zM90"Z,giq朏,,裨$$,屏<$ [W\\C$ eamt甃ZNl8*買y桁y cŭf仏E7 Qn塔>#ぇﾝ[ 揩ゑx6唆*:Mie[W)Q2 XK\)q*e 6q癢橡(r|磴緤,e;TxYd経x-墫7烱vC#斉B#"4 lN5Wc廷"^I化D)A59(舮主 0r皃U.8T/ly)轟1襠7(IT*}i貝.Wr x%0眞Y妻q2r5楔<:螟臆MJ湘;5"杏弧\櫨:uG( F)0R胙j殄VH))ylV們.自雖TZ茫 iT$i>(rB妄5ta田JIAu>Н沸( E e]C?ZC@q氓麭juYO(%闍。醺ZR o--L[,&ZHG鷲0銜}傍"k{7$P ,M (2y1Y4Lj^ |Q.X(L(,gQ ".ax]xD!k; Hlk{m!Kk PgPV7z\^Fe y鐃P=Rc]Dh BK溯杣藤O側@~Rh>I(Y0&yr,G@娉Q歉\X尚)J$$TLB#臆|8=c抹4灣fu狎w[[.寞^ 穏-9p*Z 兇%!PF x蔵卑#EEuw4tm^ 麻u>9 H|兜鉛J?)Z襭V傅寉茱!佚甬K|Jk$4鵜mrAfn1"4\N0dA^:)仁_e`z,{烈,ET膣ZO c8.逃5'kz9Ic1庇J!}C[l`-屏p.‥)征zy&Bx&\.d)/^$9蠧&k9|~YWb;(xCmde碁secX)X U(見[9P筧[KCrhYm`棹$_NC8絖wFYZKr顰棚窺h蚋eqZ-QSLT=衛AOB[>("'NCT"Oc3T覿X:y=嶮 v5HΓ&2a[{ 潟L_0E]iiQaoa価lr9蜈JuF脈{6趺/ +%適C淒]鍮綜塙R0孫?5KC" >rK7A@v " Jv\fYty*V&|v "柊I_R5{,lR緯吭j捺_J俸r!29: wQ$9#e`_ vYG}.ss;L&苗]拉LdT"\冢k]&H2E P3om@癲RY韓孩裟:FpV7`槇>p;6戲Qk6藹橿#tzz~OoE阯C/貳={C3c?b4S %5 R81l蒋Ue#qTхRlIrAgcK sd&QR后觹NQg辜香 DQS 艫08>]Nu0+E9xfGeE! M$好畦弧炸H続L&f ]BSEd6y豆%Z癸@K Z塗g])!t拴eBo繦`[)辞嚴+$'#^w,b 3R3QdM.8<|q5Rr<#RqZWC? 癸V ,'U 椎刎iK7VG<.a F>へ!I甃N亰 HdzPJ$；)職V滑sFR Er!cGdO r{%79JZwQb09抔緜9?汎(NP9?Qr＜s~(I,999?0棉 Y6fnsl}oQ\l%#~KX鵝 ,h2S鈷"eNKr4bs%iPLr8E吃]?=XV(hrA(f-X@gDU=2ndp@+畆00楝!\串隲-a,j繩'8 C( -D0壘 F"9_N&*X"+8E剰R卩6腱T磐]RZ}寨隶B踏褞d童gGu酳i頷8<'w蕷NJ]!v]XPP<*r;"x畦$]gk]vJ q>Kpi0-%2S成fC|JiMB率ko%sэ0%=j(ml6XCn &_ !籵;L6Σ{閤7+5∴&1.瑾@O孫mPMO朗-~gO蕨wKech娼RX%]a餘甘I 3#qkF%忙@yR度ru0:*D齟*譬68h@$vDE]K{p2MeTaE8y9Yhp隱`9G鰹Q>4幅б殃$睛`g{鴈繞蓄g?霖詛]嶐OozIYh&rPl浣; =QJME磆DQ譽8AWTZ9XJB衂}識lK`K況Nd剥t{懷sM燵L3PQKgWH^zEL,g怺1T/8<)22<8付0wW+c販%蔘La%阻e-X=?I ?KX3M!YSKQ/賭濘p:)kYD?8@a~j^i9\JvNO)uu宅inH剪p.bhZ9L慵BGqto.S&栩 ~佇HR^~T"\pMIQ3`zq! l5裝$3>@W8PJ i 盻舛卸杓*Y2lSrJ黍⊆rPLM._I)г9{RrT⊂ｬeDEp;hEU3,奎B9]}8" [裘剛裄#l(-+寒歃L|R2xpJ--F驕YZhP懃`%0"^j霾O逃ｊnguv 5K }3q 堙rfv齡rwy/O1~P^浙0 |8┝焦>{割鮑5弦櫁i?qsKe彑?0',ekw4M"7l(C送J労J#()(,殱S.D9,/FdW(e覺S&& zt胄#cpa9歇^`YdI%b G_AReOGcDR梗 鯔C~2F@^L#c}`F4O*|GQ4!K+~d7┳3蠢p+崔H*3L#u<[m宵4R jy/6y2Y^W]22b[J娯N %)! 3e班H．-1zqJAp~wqX]$93*FJVXs1!KD9&tZJ.9% tR|`HN i-魴堤-0mPVR】関I'`k階U,6oD(侫u+{8妣=嘗疚慴LDT `шツ屮*ZポD 壁08菎(VJ`}\ 団HZ程牝(as)債`|f!!C3C.I#VL(g%%梠遣故竿A.険t行H錨a>u釣8CZ1v[6褌1.J,4釜I(_R?|/埴.=8_}K?>??頽t齠駘7止汢'/?|鍍tHPw?P珮8菊V菠Uh耡Lo敷8舍q7 滯__哢譲;a#\等柏 n△憚#筰QPFO 売hUK$2_Y?漆}ksDC 喝\s)Ｆ a?搓<>L M>旄%4([4R詈OqAbagK肭b Н#{rI杁%i)咫\~尺iMcz{JQ&/羇;8~ぅ eHew>I`dc)c亘/>s'v2bP6PdsZ8VN{3/weVFL 8RdN I-i棄畠;8B#'C蹲Ns@2.<4W偕|5K蒿wI)@?LN'W收喧m.*ﾏ$Yu>L"C壼UG穎.+KG *bi^壼9;)AE:AFDRP8B)《輝R,纈:兌y~れE歩j恠1鬚C&派y3.鉉I病O n*Y峩M噬jMyJ法 M羔%/:m)(r康m*!.}8Sy汪Hf悗*P$ 鯤@<}Uf@VY]}7d:填;鷲ZklZWk窓孟同蘿Gk}P徘がa旗\ :U荊>WJ)&]^醵諡係U涓纒槙軅擇"Bg# 卻xPI"kjA減W#pT`\ 柁P+Pt81mqykzz+煮=拙5o&!B]]^歯fma>pQY;\?r唄瞿栓z#Lz~dO岶Mqts{zo8刧恚ayW物l+吮a価'G姿dCO/ 酵.BM7X髟鏖z3,z58気>潸]L}(讀 .wR罵;'%YZ涯隱Q誼j 5+赦4bLi鯤'怦gIX4 `&t_U=S晧ALY!雕jBd$<[(^h敏YQPf蔦糢c暄^E痲X!漆倚B 琥 EXV7dj@S,, jLys榜6(QO魎ﾈrDg=避MScF桜Qt.Em^@ku%%9@s獎ukf{ 痃CEs2b_覃1G)5hS帋d8fN艘沫njj籔溷4嵬隠&iSz毀嬢gs問1彬諍7H4頴嗤[:p2用H$ 笙P_ uqぁ)Rck鷁n[s@"度)<)9Y8Or.uq.厚D*Ps`'R G梹晄 a包3cG儉VQ N舐/鑪閙rj瀑%PPL珠AQ亶\)c2DDxjsRDR(4sQfD7)_清zk7 ?宅3W 5{f賀sWBZ .O髯啝~/黶}wz校苜y3D弦b7 喋}帳孵|褶O^MzG<~8醵駘[nBk>q2Li.s}~xD0Tpハ<蓆}%,波xi)7RT"oOw\碪池 +|}}!{巓|肺6 w>n/gr箙\<>?>@}Y 5pdyK#Z, 幣諠ryNWW{充Nkx粫+RH?o>2} Jy$om;!^_瓣! 'x+3|L f?7g8愬0j e/ZzZUep魑2隣9(?=x綛Pb嵎sxE俣lv{+テ聚9-T^r2埼Eu1鴪PV+$/%9 dJ v艸Rr 5飼x!|ΡLLG*Uy+vdm0 '丐 ZA0fZX%廬g廬}LV% -(U纉;晨%;W_>><=搗pw q凍Yk 礎+o(Q箟21$]蜉ZIX nCnDF r裙n鬩)IЭ1F9擺XH^wQ9oHI壱M nX 6Ph媛KNhdPQLﾊ@/>S.}wFxoC<倡[QMESefVY苻E9喀杠研羞=?$向髞c*y廊JIJRZ^?%2 W$d,Z4La'だ(hO4cy変.李A荊A+zzQy^詳% l;4<- 398Φly滷$c却&H5JB.瑠|@U-|jolD ~*WQゾNk)(Dw(0"-At5c舁) y);'gTg倒 ^嫩[幀$j吩ir荏歳b端G_S&'-\C$y50{ V8r /nKBF#CT|#都_竦^"(GN30篠浄r厶7\{e圸%(AX|峡|OTn+yu 臺[Ch2#劒hy蔚/{=QDx.4q  ?暮2A)Rt∪,艚dA2/榿lQzA_{+<唳敗~湧~蟄_職廛_坊殖7燵痙1HAﾌ葯yIP92K=2Z~et!4'9FY>@og穽@Ry記竜hOY}l\}懲%3q癪7o 'B|R杣|bYo鎒1;E9eu`z拵師1p[2 Rux,S墳鎧RT*gOB 3I\ g .姫Hxu稍j邀&$0 b )8o)dCOsZ.|yqYUnP|Q.Y4A啝 y- zO[/|At Hr_6FWnCK 争QC:恵<`h 砲Cypa?拙R`VV-q5槊j[綫兎)>u!lＨW= `><]p愀PJ_Nd棕XbQVGpXJPl<70};\$l励FFM"#ﾜ率k`J扨C^UI,79# (wq_#ｘch fzA吻0 _Fwс>Eg広))]住Z PJφj轢T/ 厭筈績&滯p}h鶸 _iZI58'(`MU擁2kzsY,k訪,-,察y倔dヂp  鑼=l6QW？凩, |/G`VrUqPs {N)n凹.)w9\\* BM5\l1*怪N虎ZijjrYfK檀;HyV)エVAS xoz|詰I驛j_u箱破z般_ 9[)d玳@Y-(=9r2)A鯡糒0+w[cu *w哩&dpn發x 礦鵡l%y%[)I妍gd/\0<8js| 2W*If缶UbC把J, K滑<тi+s6*su∧_]T勾l"f!]Zx^EMv4kQzfr0Ta5W應1R 穀h0Q倒$G跖r;E6曁N艶2鴃0Q+o/aVf巷n朷#)7StGrKnV(d=pt鷄F= ヨｴL^o8n窪苙罐;+I"9陋 T7R]!81e3F|[:Y箏vJ0f卷 l[莇|%t 了)緯"dms!:訂(娵;F2紂4kHB!EwZ8Ukiu!num.*vPJ糸90C剛遅覬u=,~n0Uq2e>勞琅p洳9`T5#vN%筈L＼c"#}洳rG6pDJd{潭9X2櫃)`.W_)A9蟶hUkQ-5.WA=@1G"2 [U<Ck召9;(攁F1z8_M H8Jb3.(P!s(xZLU_>R2.QzPx[塊抬`pc+1{k} Ix/8'k;p媒Bjf 1CI4&翅!-ZaJ0>{&o):)%^ 靈 -Jqy.M{<賤)5et4J9J`MAp}飆福E手36Q(荀沂硼Ν=}u壕徂┘cjLWKs"痢H5qr<4釼烋?\録;+}a愬瑤蛛$!=f ~lB*z}(XsAN仕um_/髞:bt晶z{w9?_[潤_9@6SD埔EO晋N縦ow鍍X7椙FVI咎w鑪oP搜繞m3C 龝k{w*GmZ{ B帝勒'HwGる黹;h圄{P}璽t膊薹~ysG>=升zQR輪GAw蕘' O抹"Eb]見}iys罪@殍3Pk饂#/^/Q=o)!7椏 "@濶ﾝ*?R緕L)p_ t.F嵬b6t[/婉+2,爿f'PD yn"N舐?y^Z(檣_TﾁXcw赳MYp.,}`R__? Cr)VI;絖8cj'iMWOK=gRP胛! 笵Sp燧t*N/?,".wq\cSr懐彷槹Z6&b銓I 囎"h[盥驪WVgg UW&e4CC l0ZH]PI[yj'M;懽圏>熟t O^h(?~|冐f(Q余 U),Jh蹠G?熊w騅O)掌勤g9/OXd/∝oyh~%偵 `Gヨ;[ 厘描{ w\7%熊燵 這r"職O蒟OtuPr]矮sCp 圀onTX_@1李萩[3褸驕禹@p{0褪Oi{o>2^vR~UO^,)|/WE+ #r7[Viyq\Bg栽p:ﾋ]5N~srmE"ьn3繽 \^[$[v/pJ@? 7Ｈ}a t%塾yR`VKRVt ^^E8,[攫)r.xWep] fXl吻92逡罌庵^SQI^Iy弌%L9pvff諞魄瓢s.&z\郢Sqi"; +Q.y襾J己Kbzw黥tcm%N2*q!0j5mDy=BR ╂aD<咋jAF羜:!I 9)X%(A6\&6ヶfdAHA称.>||{-nA譌C-D裼昴瘻lガr瀉xeM~x 腑$HP艘2%E5iJ蝴7G*&Gq@0yV槲b5!p ]i騁T周E^$羆4>$"d+aZM}>\3x軽g.wFl銹)G書c6Mu5 Zk)BIag眷P_"LvS嶐3Va4QK#巴x!p<-1盜 悵齋w&2o^=]o4 i9K ePXg!次PJ摂皺P怪輯4螻]q" -{71$慣xMBw穢~  e&℃:讎H6倅 +SGB2,9牝0EB27v5Wo救鳬kK P叢KVy&_l)椙D姫VQ1sqチcQbfW妥09 *-F9D%Eo1朔F擂坦yy;H5(|q-(K9H egdd贇AqQqギ%0 萵= Bq肆F鞳"秭Q8^nY5L:K1BdkV>+邑4B=6D'H]蝪!Ro_}x{o酪猿AH鑓<;SD2}]5#SfPM&Q7s" 福孟0@KR uI^射与60"~=(?95sdY`Tt系8"n-Z  *0梶戲1 ^e替us箒+GGn<凵=Q"8婿pZ猟ip壜GAi\蝗}-榁]2惘W9乢>UzWNf暮_~n躬Ll伉[Чyv17ZC77 q 1 d{K漁xd cs}Qx0x{C=x易E行?&(hC~91 HBK祥zgX.>s)P出{ynmA.X捌包vO^_W故L葫柮YZZ 給鱆O&~~w;扶wR闕_y%NN0S jx*纔V潦鍄t轗^郢I\f梢繁Cy>"遥竦".LZ`K罷蝴癰鰤ュ}ke?>=i瘟&Io辜f鰭S?繽E4旄Z;枅 ~~{寶Ct踉髴Q{xCR濘Hｧ ry隅彁 62收HL2檄x謠 w|0},?|戴C顫h=i|[a5BcX{e;退蕉身J驂蛔}7>d倨0糢.畚0lD2H:+拓綯 椶瑞-鮃'~!SNyEk-?夢nsM瑶/UGv/^蓍sW7omn=Gt嫁}NlwaY4.I密喘С&5+=磁@5OZWU鰈稲H_tU蕕O" ?~G^h@ w8隼Mq Z+T女-離 4rc性踟 S[Om!*;殴}"y|l|Рg毋}}K9?D&亦c]汽轢(.;Z_5儉冂 NIwwqd1;十p%*v&晏/OOT;uus,+Rw_-vｾQd_q憊1*妄DL棊/.7前W[隼`g克84AgwRc2z歪^詛沸gSnfq- {v-@no- 痃`巫@h^]n+恪U扶摘bJ.Qy2凖T"]$QA"h玖&k5y$(-B皙97HzR8/jEw9 順9 I棚封p}]sjAW6絹 v5 %cH1&o\鮠\P<0艪∧泡d!U&PM^0y穴 1q&}弘Qru3 *%E蜈)b^村鞁0hvuF4兵.er6mR !z"}CoJM:p\sIG^)$(u&+#搴A貽i+ZU xR]顴)\F8|kVQsB&ﾅI8tBr6"k崗Q5[3酲Whv河O濁ZdSsF_\|P/_Y+x戴S坏敘DcdRA悠'uQ#RK|(^剛$8p)Sn^h^;kK\$欷$\鰄<押 4 Rg點'T~漢vΨoG7B5k緤3R&:GNBvF8}1 iBtLZAp肇1uu]薀)P(篝`<]ynn%.}r ^渇R&I告繿re茶J)M黎E} P4PN sj 9J0@ S2SF1sJ)鴉9])']2匆9e 鞅Xfus,割P 9%o0[LywkQ(8O)me:F恠y:QD}>Etm ouダ"FG08PJ>t$%'xrT濂.臈[P沸r葬#/ X~t$瀕.*匕R23:J81=H vn5M|kg衿U`敢袰i$ pvQOsVJ屶戳Q=較@IDU`5\兀!sR_A3C?N{k(OD"}^Ρ y)E[=0)PW)bOSY秣艪淺kx?^w}N.s惴讙CKka莠nT>y)Yよi珪)2h?^ZHfr'Jfla xEqR'=+]rb]Z?Q口r. ]&qlss/鈞Ugu9o\什梼%tk^)WBxRyG4 09keGN^Jc腿30yq/vB暴B葛Q偉5諏^-|}r.J*拱 h0zvZKv$JdGぷ$黻 xz ZQBk\ X8ef\?=J&$|L7|gO 釘Oj#u oZL;}&K8J玖U泊捕, zv洩l@y6 A)擺odr隋O媼]樞N筌$4*; G抒P疸ヂyE蓑8Y(og漕騷⊥柩o瘉樵9d;n}PXdYm ti -^F巖n[:EBal\;6Y!,^7J{`DKi汎D+g[=uMwe)EhNJ:lp鞆>3AI`H盧MRowH蝦8I嶢Fk/h‥Jq -填os表\-逆-_3VVJJ^hR N廢EyY%G9g摂(Eu畿|H^3o=)2茬 -坦nq2岳 g daI LK板肢`Z`bp$KV N3")R菓$C5Kk xgkC)> LAk!cq>QBK$wm88Hnc pyb´縊G30-0WJ\PdO\與x信)X]( 炉配椦詼k鮟z=荅A睿)n$1WZumS廷Z鵬G竿ι)駱$ +T9cwD N舐縺卓I莢\F噐2康o曄喀[u{9}vnvwn{ Heбz[%橇(X2] o|$9" s$}K瞞5N qLE)j*y@Q5)^]5yY%KR) 醸%!tR 6l嶝莞tf`=SAQV83cZwづ党赳RI酋裟0∵釀B穉鍄fwZA腿S #暾C袰ZFj\o4UE鴣dW款AGI[P循源┯^OCｂ}7e?cw嬪>a縒07i ZOc乖|*q,JgXDMcQ?|!耨野H濛竕"洟鑄~1真橈~@PPh~2Cx樫yZ&%1h超,寮lYwg9-|J9少Z［霍@伏yz-@/^m'.r壺Ue|n雋DB7mz[u\x=G95*`*俳搴k]BFwq6L.F=-}9ZMzBUmzk鳧b*邵晦?荳;\."ZqLEQJ測惠aa(^)t@Ns@Fp袢總鼕'慰T宅b\rq歙H伏パA祷J葬F隼!珈%%EJF$SX&C%_i%8&S-AJ [!gDWy`7uG]鬆3JX]-鑪eL@紆^F |獵V]\#%.粐*kJ僭mt~5音@Eq鵑e$ReJ?8/!+r(R<7獪m腕X6w掵Y f\温oFz*bd蛸}z拔:釐裲e筧-;罰袙9Y[g杣Цf[Mz勃\c蝟蛾桟+凝購% INWll鳬 3еYV3pMbx+@扱簍sfRH岡r<+AT'% 麕<6Kﾌ涜q} fjD!:凱\3d沂g(-#W廛$桓_-U/#Ps:p-f\~uw1.|感+&/#乏+X#fk ;寢咄辛G~6rrD6 y^gOZ疚t3h5噐mчP_7kC&z瞿Wum42蠣偐Gk~僣?Coa沐WW% 柩9!(Α]旺5KVC@+B齪F讚}Y ,r幅Y?o窩j< y !ЩQX鉱K皙\J6;v&禽%?s9(B*W銃ROP^S]L 伜:Nvm`M%頒'L憧*)什0!譖殆.O8賦1k)V爵A8)^ 3Oq銀>龝C+R巾搆e銷{it =>GY婦t冐稻翼ctF3鱸`G纛嚔 孺哉*Jh褫:9n^F滓v(耳os jzz=P vS(萓U@.2pF<[} T 厘編9'4E^%鑷_*r磚 Qq[.夙)^J8F@9;K勃aql葛M伯}1A堺yMQ}zq過藝$R:|(尠(*nQTUhsQ塘]&7{滝 LAA}葱..}s>[j`ZqrQ]囘Wn!x)=w`AAoEpIRsぐ{OfArkS`-:r砦23O v@ANN/%H贋綺5援'=;6等HN鞘cn椅;┛3%0v$\yu5Qp♯xB5骸3蛸mpd=SZ─9T@>GFe 3\紲hNbF 穹 i_=ZFY`"?D_uXz!SU鱗E1E)2Y~l1 ^X{W麌f.*p?H!VJ凌臉"Tgzt濕{p_(v r=E沒D4xGpWｚwFrP １m社ZxE:'8U\i経maT,sPR帛zQ\_a Ys'!; b5<囀!Z!+S3 /牆i&; }X2`q>ｾ横d並楠|e"tOoI倆E~r#E韓/Y鎰_I'clu?N7h詭'nR止IB(Vgj"{銜r~A@Wl羮揖lF}bX\ /#_-+wq薐R2m82y=W憬娯ケ-C[;當爺oy4'j娚淨W絆^|柵&d tn6"|6\剱2騏{fokFqr ÅPQr#_\J &=}SN閥M6O^}D6缺#澁z8nj]ekQKZa8J荊q1x8$3｜]脯jK,iu~`謌lB標W>/@il 4.Eq.6>黐Tc^YPhg^6PR'Sm! "3A\長Bz4S碼懐`勿`歃-1馮;!KQ7=цvZ)M<-O;フMHoK糾-`;JrF9li = 9V/;剖z%0kvjG2FLn扮^jHLTH<\ 巵最`法>:;#e4!GV6襭ゥ{y a^笏Y-|七5<.[[lm]A 憊gz?vZ*5MKsg喙秚KB<\xn=D=].J貴畸裕\.鯉 n= QC絋0]bYZ0?\f]Z@*okR^3P8I WA1JUONbHk-緻-~4[tBj 9x徙甫!1碩&弸n1(>|m$ .@_Q()~SЁ怺@~z訛:o Q*黙IX &8虱幕Bna-b [Z--(MN#Jh[vA携 禰SpWTT8=% "{)T弧HrIq+ \d = .2*s 3T/$HdE亙I*斧霆遭4FK(ajmAWx[y 1奮nJ疔鏃J務&~舁j贈dq}?u 巖G#f抬艚ц}8jﾏC>$*]28)>$z>M9!,t8Jz}H&=v\;NoHmtTH1dhβ A^ 舅got鴫鯣>K`UW6y癬m/(\h鑓蓙iQ炸a木N(vBZJ<KZJo^Q|I~ 6疉qvB%[6J%氓3! q)F=^A} |(IGh~暸!cXK4]liiH)xrQuf梔10a$Tp；^T=2\i郭]tSR`s9(J#p甥鞦Dn>*"vKp%nM1CV%qL[aW4J3蜈q}C02dy~柧Z"g埠p_)p 4ﾍB皿1他Ld]B訣鐸`燗Zv桔@r \gMB [zl#VimI辞〔 .u畝; I>d5w_tuhK艷X3&L9酣D/p!@}^薊Q弥8搨!J釧髯膀=坊m黽6SPN 0D怠?帖嘸_<~"痳C鍋^x髑 壻2*泝oQ2菴|C\?Roo?hO$7S柔柝徭,&*>生赱/,H'&m交Gm圀俐0朸&gxR#4=X棺 y9Ir岨n%B=l]7AkKl3X湲Q():QbIy,.нwML`" Z4 4F&X7A`3lL/u&茴rvM>JZH :J)w]_RpH男p 墫(rI寝q!1< Pgnmd/&摎i5R箏妻obN?磚ケ]2瀲t行oJV尼2jLyya-O券}dr> :K]v>>d陏Zぅ纂I60X%q漱FmqXうhZniKﾏ-#力tAn }T;嵜},!Dnト[2B抔`AxouNa2縢'.9志PZ閻iT 誄paN諱'?B;tQd=J9'Cd41味彭薤L7''}%r"|{ 杖,Q9声k薛bm鯱cべM$郊z)\訶YMDva8[L7 MJ}$NPx'伊EKa閹JP|Ex[7BA1{ >X隙C 'μuMvF凹董YEyQS\^gP%v0xw2章 |揃$爬r|7ER"\kWH @?Z1R覿ef)zx01nE5i`pQd$GR蟯HtS6#復-9Hhq杜[(yHDl$給<"耐Pｕ-sn党2栓JI誣EH+(d述H籘%際!{> e綏Zf^\xK圻痃|尸似vol渤9飴R{J藍Z亡翔仭IY!$覲y%[/}FWxvJg樓苓$ J4駆H?4C]斑粁,泯p笄r.s7"#4壕pF9箝;P6C]%雙)L(賚zlnUy賓u>経B簫昆 虐n:*rD蕪:($d殱滸暈Z3Y#S∴HQ唸&S講H*oId0Jn性-Bp.6K*g築l函糘訳#u湟R悲F1-eﾗ~GW 窕A呼C羅:UW守5鎮cy呂c\Z坪matnu}8#.`prk>:DYr%lPNd⊂遑R鴾hnc}侘!嗟foFr I}[h1 F刋 Rl'X-Y[k\`oR7苛J Ii(繭擘z狗j -"YT嫦; t行AJR[D栖M.廐:* nV身0znE2黌х}S!\.}鮗>?BM#MZn賂i?#eT}- `:h+2b%R9PXM奪e$}{ U橋屯:HpD U甼HI0《<5MD閏狸G2頂f訂)vf#2G}?詼6Z-k鮟印覚YG(W[(07:*dfP R3P_%h}E hK-{0l05H充rH輓G ZG4G3va+%A.辭u jW` A.菊 9g#b%2My壊\.現翌-jriDjK)j蓊Pkm蓴纎2st h}>0>!J&麸6#hE混Xs4L\vt2muT{鶸ЛR@` %6xYQQ}9{Q挺N/G8DNz(IgヤBLP !蕁 CG=1yg粫R)3鱠Ti列Uv =p\m*DT.q5pc-鴪@c縉蘆斫`9B啌,ZND=bEelrex}/Wf卅G安{94ug?%'TZr }!+G藉dU*-枠6儡Ly卍t%杏%叢"貳c|]>NＤ&|fB]2肥穰歿H飲Pa亅c3.tHv[e)R58/?轄 tnTv@dsdsc~m!l\5n螺alf 韓u7KYI+6:^K駆跼*fe *f續R8L;6 佐8#L+.aV^Wc佐 Q y)9僖e#cVz)狸t<能2 m1Q祐$^#inF"。WgJSZr_)遮QX{5(E岱hn0憎佐o4}P2pz=HBIKR隲,} |Lgf~衡E斐^ 怡; Ej$Iw -Hhf]{E$rP>oRfU9K峡廂E>猿專蚣DO"椀""7\p+7Eh:袗 f衍Zv}i捍VrOO籍S>ZpsH_ 3% V2ヵ稗秘&21匝aT補!Dc_膺GQ戻oo狂?KZ砧L濘躄vhs秀.問zYt oJ_m+;^FOJ頃$x;U $^1S齔Do],IEFA['#a倶Hb9/g$#&*!XakhQ [7}蝟昨pjg考;弘n}q`eMG)1RHg0Ac腦Q4`?^h)チCU{\s=xlq拂Y!/溘\yM膕gi求 &<&覡"騎)"怨g塙m葆 ]iA S:h8Ms舉閲]5K]}f#}抬怡WOD@3j8i>8m@S禺AkF┫&Z~fi@n%迂e}H&^K|0.NqIG[P K!ci,#edqLh(NX涵xoN %;LE4uF選\火|)J .4c *]FBu{'8@{dWzFF洸衲退.4EO`:xj偖5H鯛&[GsFfdD tife4聢!xj`Ra r4.Q饂*an JY^W裾3 HXB糟,PB糎q(3R 紅蛋項9Vgb(&YL C縢J腐Z$rf鄭J煎F+IZiD|fF)N .*画I魏@Y}n敍n=*Vue3)轂詰7miz靨>D7m# 江u咯MuMELurin!*C(I5C[桁0V零# gNVtzjDs}羝R,[姨9"F(U儿;%gRJWtnYNe袍kn(QH0J;i 9X2WDg]n9r\7tn徂\建7.%Q賂(|豼C 黏L' -JfccIQ\鞄T C :~S[-肇K.n%hy7!7瞎wP<\W*> |s8C6e<{潔QVW-.@荘J襞ki祀77H"u8 (yPn-Ha/嗜a\]{8(E>1u淀T乍T.<_H定`扶PHjI>c]A恒+j遊召岶a16bi_嚏gQB+茴冩R s&W$B]R*e4a Xzi[-製wM危m籏m窕 cWt9]$/工\mIcS!{)龝7d ~粉緲Hxs村.L.#%Q]-#"R;QiBW v|暃游J3>3F$Rm`(JL$6g}faJh^g 1R窄=e$ 3Eu8A4J`O巵*$K_TZ$顕pY d寤榊7J騁P)B9"#p]!"[WｔB9乾\ZR 5額i8_&!\蛭\rQDA<峽jJYiIDX;;#vv,R嗜餞 o=笘u粲]kfsI5s+k罔洌q5sXR/uZ[w渇扞:`听$1"f8X:9}%zt椿＊t('6W$+y櫟{_3F兀{\u*8+標 %Z7OAAPZf[朗釡 x>,HsB3D_#I0L[T汧D繃'5Oo沍tH*怒e/<#hEtu)J%歐@e$'%zyy─-髞:@r{|e. !; 3J`廠8Opk1學X鈴N?_<砠晒yn`O河h%|拑MrF.劃l徘粭L驪%gBT 最.]La蒜>BSIU飫[UPGZ-x7:i弼7Rjё+pg_>}*X-芳B趾6瑣rl$9%蘭噬m凾&+I蚩剰Dy7皺苛.W瑰Gt受Q{]l凡(~襭dL1`2! Gsf$AE4(gv癨!&AL'訟ml"'¢b叟~媚^"娼qfZ2r氛 J2忻2l#吝zVF食!R09ol 9Y(1!фW4 4鍵* Lj)HQ(v撮Me R郷 教澪R/NW"\磴槇蛸 zl`Jl薈折+rdS$ +皀/Bd>*j袞hzArt 嗔#Y((2^57(*'6B/z 5 W\GDKP9{h]炒V}-g菊jx鑰 ;既訥Y襁R6]4z'gJ膕募版北y>[覯n-卮Z{+嬾黔P圷@92瞹!_;Lv:B a 滌 1oP絹f@UfTAr蓿c Y39{[(X*j+qaI]n@[UyW%鮑X5:r>Mi9Q}lNZx覚 R8K17p滑a4F{=u謁Q萩c:I:G俣6SG9潮K@U^bj#\%%歹({_> <]TD睥nBP2H句U襾c∬W n| %Ej)y"y欺妝 !O^EKqBc9TJ[78Tmij'E@B@B:Pp -p@N#\S'T'!ms}#lQ匸%=6P=7頗v9}_._艇>+Y!v _^B扽8 eg竢~s褄z帯瓏3噫碵論(Y>>f\=z顫o0&N!)9'紅齢墨 (犹F5dY%s"DM蜻?}黯GeU塙G6iyTi/{z蛙踈~~ｃd@B3琅JRW6g;\L*Y燵δ◯5DF_I/_S怱 謇要鐓y癪丞膁７戳馬蕨~GfJ^騙<裾癘僵[樣*<5羇,瘴滔睚DaIr~H}欝2靦祚矚4E_O35AQj{tDY鴬5逑潼I{V%顆=M膿RU謹g)qmk獸屁7/充0q昊W据~桎}c悠_3鈷|媚苺y蓋諞]')髣裾 QI費甄~1!*32S乙傲o'恍竍診G'T_?y舶/|X2$鱶U濘yo僅v54芋?;$屁歎C0 gdv mαBOwhK業粋N;C 粘25Iz < JBVxJb(L5@|2U+d$-覃 9k]8 U *NnrF6UZ`r争U\T Hb,Q域Z`,恨Bc0仇Z`$&芒}srJUIA]d-8vr8所-槙j醐筰WbSF3箜oSnd)7%2.mxp`が樶[V箭e`чje捗) *貼!I\良cU7O:粱岡oK堰2XT|].稗BKaSd憲3I'G>誦脚hUヾ1X[g)|;,e(F\C)IB]/8腕-"'Dg~2,W)Ur嗽BSxK !^E $^夜6tq鵠9%季闖e捉A@Z梢[tj&Z先颯煌J%ZAl&k堀u\t<2=iR$`Yo, TZ$Ec箟(Z$簗B?#i鯣Tク3(DL 3&隆Y$釉婬Y`o +|3;:ez歸Pnt厰滓HB'*/'!lONIHuK_6R河螟]=QY_攝T/%x観TWeU P |zV|Jvu1qSU潔濘rukr_B菅矍/W v6yu (髏"ト.:Q6TzR 9PE~0.Y夘})uc=DgJ吶處V筒|役DJf-5*爲sW8 hbD洙s5M gn嘆aT>mskn)kJ俳▲ "e茶筝R6<\卸h9OxF鶚y}0yJy 爐s[}<2hg`D鮑i疑tDpCRFY\P@*# j蹠46Y塙)ta6p),X..+gw RZuDg{罫M@萼kB3^!8{0 gQ-(V畊.nJy咐%e]&61 fu $ GE yKXLcC PW券佇%g*{KC+[6寛m祈珀ﾕZ嫌b人[樔suT?s=S|U峨DjMbb|渥 2壙猿iu'S82雰Hcm39I>pT帰PKHA$B"8$Mq- Tn颶88-Sd\3dr禳m抔C;I1ZV>甜]ゥr% Y#i*`3^J1(~tQ;I8IuT8uJeｽ滲 ~Xs%pワNB^ 葭*縡8>虫'2鍼秩U:裄.g9h螻qgoj[ LMURgtSGZ霈(ﾎy&Mf<(r'TqJ憑唸xf z(UBq謬 L毋:屍鸛/dI士79任sKe{WL%圀ЕL%雷F~rc\ 磯*'WN|Z.gzbP緘}>B)肇85; 脉0)?lgj; 9fｈaVKR糂X段函bgKGbs\aw刄=>jwa.z| 瘴B)3G窰1opdoKAP$D XVRbI!8ER`Pd-F兢dJF/ePI_Q75 奠 ュ uf'H R5u\Yfdw(A)E"M.~Qv/j^A1Hx?喘.W> rF9痲,VP} z>虜0△ 蔀2ф0夸F烈FRB ≒K*ATMvr4! riw3(j1竇.`f B|E: NiS辟4|.fJ#") 兎`; \XOl臟B?3・@7跋i ?績uk3*XARF∧膓YeYA3opr迩l,k,#>径ZJ -*K黶Vgg[H6jW }f3)鐘逸mZE槫M癖pr_&@m@p Ve p6 4k[Sk/#浅嗚顫Wｐe^_/!sBー-Dy1癇z爺~穽hm h+C") Ljp:"v B3.68Q (blz騏[盜`W-蜍e 醇8uU+{xBq`'l"蹂XE\み)t姓!?i;L韶 -N悲縢U筆&`葛@. v]S "9 ａ@緩}I蠍Eｮ)1"oYW\yx泛燬樞鵐vdgFS#鰮a@X^8"ヰ 0frkZ@ (跟1qiﾜ師k+dHU6rkomnVC*:aNg霙auYxbZxbKK諞f舵=>;j 1a.ud"tlqFXK ツ/eIGr疱_?}黽>}髏瘻晒}=2~鑠/胱-fa8q=供>y鴟紫_"(竝W?|g巓;{2鋳^EzE`.買Wdl {&0|釶'~bXnshV"zG1汞8oO鐓 務_MQzZ(<鰾jnA%J唸d磧E/療A-勲渉3|o+q矢?J=cHr3~c.(a7iT<瓮z)#J8H?}k ん"x/#I J +Z14XB7OXF~ X\T #cPo沍臙m:y?eU悳6$ Q7@7khXJxSRo截=淦s ND7}X詣y剣公h)肝\q郊;J~"壗q孀!O鵄&hE4 z舞\3a｡6$B}?涎u; A懲D8^剖knn 黶濱 $b/R8lmw"=梗Zmr]丿/oRケhv蹙6Lu7.y)*Sl 付sK.α蝠噐ﾐnCvJn'w扛=MrQn P隕z^\u"冱1(P巒娩BjcP. PY3捧%)吻Дg_xuC゜喨 n交aIf_P夙OOJMB樛F猩p-B@HZ委(zVyw';!7b噺-spv謬 ]RU+圜Y舒PrI|Yc"澎zj4^Y)2{3.FXhC4J9文~tn⊆ (E"圧V%y8 X{!>贍k現-)C6琺粐\M柢蟹LVM麓k%4w?儿i3監SS6Y(=姦*V+"-[r( _Knd?Jj蔔%:w" N\決NC <=,I泯)K笑Sd%Hn2靡=*N_綰iu +尋罵IErz濛! 2 腰.|hO]{KB9dkiWDNEwPsr瓏廰m|(縒~a?祿of(肴}憔F2%鹽~O鈷Jjm瀚0z( ｛(95Fn94B@;苦5KC^ib殯 d柔k[r RカW臓!>f9[ ⇒uO咫 咫Z&_B燗uV5|/Vbxm,>:K渮5X0dqｗm^尖)kcta|屋l1  hBVR抽+抽 歟P% .kX,J|)fB!- pVjo\8 瞥Z}示桶番U助EoMU>\PreU瞿 >綵dSsa準IVB覃:2&廊搓/  |S.Gles十0.7o悋rX坦Cx6us櫓n~裁塒6l 謠ゥ|)_KJp硬Rn葛@dK i顴o麸敖j伐5P$6]I^竃_*7LPfZ+2唳NbiS3z'g;坑5cVPr珂GDFkm鮗}2=n祕蚫@6e&(k扈)gC慍I詼臥jO-非('x>~>=_A嶺5f謹 q]Q kr)Bro>0MIWW胚H9$$Hcs0|P 緝@刄%Bj9T 61kD丿a鏖aZ}\k JE鈞嚏+G5iK仰齎W9杯 A妬Hd1k|M甞c 萃=如黙f,rYaQ (vl0J}Z_,kA栗Yi[;( 宰lEOM4I:(9J7槨2.P%5+4娼%弗4R罘覊\-P( uNr8|c\鰾]>%rUIs6h1Х%Wu掟%$Lm< K酷1>y4駆廴yXisI\}pm注懿}wq69m x-Q~~$(,Z霄<酩emL9GkHS27r vydJ;Y糀{總 ", 泗aDWC]ry)o檗9B]k^wzoQ0\r#g/S_-撥DC| R/甥FGH旌e2.F:}Bn8Dzx!A!-ゑc4: Qb]E眷- `グ(kQ`篶bOE嬬s折5E]^*e>D"&>KGm(2hV 剗LBC( eQ,V循|]p[1.b_&蟶鰰溲S Zv}q>|(OD{6o;`R%.S -svI4C @o ">AVトyni@y,o{w易掀^hu盻dmyL|e^!'勤QA脾G9P\獪w/._聘xp /Myx)uhS>-dL?Th2I1_*ST&エ " m*E^giF噌mB'P#疽肯! i5fd*8^:ＬRbB跂vば⊆Zs- ghQ_苣>j大n孑D屏-%{Z0;o璢Z=e1z前5LL\T1H4oQ6蛎V 克Mk5楹"^&ZD -q%h符|侈1KOi]}'嘔nKRdqI"怱e-'w'GYrｊD)2:"_)BQ/k碾0.衫\頽√p+(!6,P(!昂/ucgx迥}LQ跣定LMvugwFU_t+uugLW鼕, 耻<-ＯA-$焼jC(8ba8霹0}8]B x9J +h黶L右3]z}vZ4 zfj蟾Kz烏G權uQ~@Qf駱^Q-VJM゜J驪 +琴r+)妁GM走:]15s穣Q噂zi}m^&疂]&4豎qt$偐J('4oiD!3[KsX音PQ|視D椨c}`rF5SPwpT@*T醵嬉 EQ%(O# 鵈2Y E 蒜EZD:#o_kc濬8t条Z銘p\s瞶s S VqCKE怨]率a|kqE#&$蝙->屁8n默yv]M=(t逍J},fB=(0丼嵯E蚕#k u閉no館[p3yH8逍V @8ｏF鰥;貉=}勺GdM Abz^矧C)5zI岼kFi⊇詁E療 ]z4L弗雌I+Z捐糄9#/2覯x8 w裼${6l919?k o^n(z~飼lT域s4犹P|9V=Y酳稗^7繖Y駟&Wー,\yC[(/邦)L^&/zR @en F涙"伽30GV;:dBH梵;h:s`[M*子 r綴2Wv5u害ej$\鬥J|"#GH]Ds彦Bj^&徇 &kGWO 穴{;*")A崚S.71(I L B\_ghQﾎZJ # u艟la詩{繼q}i4萸 *>飜ZV修J9Ld>C]x潔&6e?6擠d0mP朱S>民'9x済囚0S祚躇V浸DF}s>,孝$n8簽鵺ngsV屠{}穴~踴tnA -嚠B/阮:傭肌x#0#`$wD>bB mxK"xtaq浦tStM葎\鉦0W版((I>C"H$O =:s ]H @(xCjpAkeb6&mX展+HX抵 wf嘘5!vTゆR"VO=&SO葩+;hwt SOU<^pQPJ卦O栂P矢}4\LcAz~hy##A/謙舫6Rl2礦苧+%頻恣４N駄!|>洸DE.6L0Us琉弁mBc.|*j8C^*r0JWk^L!Nkq覧+Hnzd&ヨ 槽#SG2>Ir ]C`I!J {{{Q,江鬧&癈 {AUjŠ$T話]N<紫l!'. qC擦/磨M=)Cvz0c!aP9E:Sr$`(併LH'cAu 筬[g( qz姓z>^QW7襦.l瞠(さ5+八擒yO^;G(鳰WtK;F儻トWqR晞\0!vダq蜚x}hA剽Q膩V yv!恙1庠  \I g簡蓁Va虫}&Wct>s ムBL$KxGN黝z~ 2ZE1 (3kめZ請le+K-.>DO掫Ru}DTq:aI 0O鏘bWMvmHd^o%ΟW愿仏癇j%4Z P0)%K+e_I7.|%-%F就鼠(o/k:#$疋+p)(tu;矛謦RrUs)酳\;5泅XR 4cN鴆 m奇 ;nF\Cq W}h9k s]2*E >`EaQｽ aP8j\稼#S悋\N 蟲u6?韵嫡CBr 幢&a"P+T]BkPNIYK =JwZEJx 30rcbOxHJ%xMo? AP.1c'HF) 'H響慶睚+!wxRwI&GI1JVW Y讒CY~/sN<∧%)*3G=6c\b9擡 >?滌 |0>DOZ~vG*;5)TLC(響J瘁t$H槃)^Hb柚3S!).bMT3tL45!aAU|穩碌癪肅諛エE疆短Gzo|w輦契VB 髑gw__*;薪Us3AT呀曳Qb t0/ 艱5@XR=Rc 4$IkgMY^ ポ1Fy;JA4{Q3S册VcR疣hhMvuａ齶閘Gk[TNYO壓(m Hx爾H#a`e]NA8逃齟RQ1zhQ@H[d?U/%)HBC6穀jr:.Z1G剛yEfoG ru=V穏w/ !0_VU*wtHJ|rJR_J&2j`R$-jN僧2性Fg紛椒VJa5 鑑Ca;Jqif];lfZ\} )Pn\恤44Z *gDy3e膣'P私r`2#.vzNJLY$"律$$,UXU)卻T 邵Un単fd{dUH8NJ飴u≦J5!!\蹈\絮MIvm#$YPD a儘n^哥蛮\rb`FQo罫p5VY8b]o!縅V"I\Gj| 怖3]|-(0cKF唾:@T冑Wpv0#帷蔕exzH竅vi]煙Cgi呶 7S)襭O煉!p鶚?>r喫總 Yn穣QZ助r泅F#0svN縉u5'&采 韲q近xU~岩|X_&(uA GZEhG5!>桴濬齧OkkJq~j)´蔭Z'e{k馼1 P飢u┫7嚏T z ) 込I"yR(&6I葯ed\Jp1.DR∇fM春鵡(x\qnj%5#E歃*E;7\$75Hr'榑(MmuIB (2ZI5C. 8+8qnMzMm杷 *8~Y\6諠dX M r甄=7}悦+M4y尺yL<6H%粤/刻~彙y朶2─&]店!}N岷Kt哉p~?蛬W_?}E7cSe?:{ 05h)(エB=q >}(\}辞O{[NSX|P聟hkV,f~=|Av^#)RwZ-SX%!RkO禺ゼwsskJyI*}LBN0.~Jd=F?F:(El[[ZB=訓v%t=9 滉ぷdk%<.&囓n3-#?T\=uPo33%+&A.ud.H粭}Th$%沫JIYj?勉LS0 RB61<1モ\~&/_b^hp\% DB[V yM洗u{Jn+L霑9Y柬Z-+/1a 2  sG`艙 L0轟h|MQIP!剱-b殲*氤RWrHG髓擠i d,管VD B5}U I89thB0x>sH%M艾TK,f4BFTZrLlE.MI|^Y睦iri楯茘楹(R"+VT贋e麩:@莽|xb/1ZS}&FV=2 ＾vO[7-Ja]4Un杢r.^/r)藹"回Tb%"e.uK菰\*=k+VZ}丐D $S噂|HRpKvM@qR.冖)QX>凜巌o`ia笑W靡罐z辜k2U例寃^<j>~髏濕[椦N締黝苡yL件殖+_l};Ub恙2K{)}L( 7*pK%a平幸姪TK韆12+4<(хdCdl^l鋳l!0?都op4C/裾驟o游MCC7@g/廾j_ b\'U`O\I kI6zv#G"=#予 週R冓w|+D}. %Xz 磬T0}lXヮ#h.[JA埃Dn鷄BW((#6魍:BR/>Do畊*OA2Y淘2(岐k G-2p爼7.竣MB*7.y5nU項tV躪zqRlk>;;緒{3bL9.昼8矩':3烹:l鐓T俐|;/t\髑dALl8 ネc胛P弃e脯9.Z捉 oS梍)怯)!告SO5複Wr,2@BK^##冬^x_下磁\?e縦鬧K ?9+Xi菖*擠F@n!逮pKV澎b熕|VB(皋/i吶9U釛(3eZ慥)}\p{ ax)P]r1 "S2 b魘;[r予Fwu"%GyrU |khKL抔mD揶m\d9話.雹. MQXIbu踟膿迴 fe1T GnC痘p鮮p,Q7$蛉E9[猛2袤KGHr.$$7 Ozb4奢7M0{{Fz邊J^Rt%%季{磊髣逓AR妍箟ｦ9C6縒U+u>X;E杙o渕В5i禳]妓M[妊y,e;7r+xY筰瀲;聴9cP●^ 7L^(3DclexpQ嬖碩 $e2+I毒qPtt,緬個鯲)NJ1Misj~i3I*6S4衾^+@%gkS{zM+  WW0:JB8t輊sqQuUyuQx\u奢(E"3泥7}|{6Rh壼tCAA[hJ"根 2FH香2tT M5_差x5沐譬*Jb2 c|嶽<湛w *vH.f|^ [蝸lV`~gJ{ImD獲[]?S鮟TI彌Pq陥o6m&x=К'$UJAkUePD.嵒)販= 找)oXQ<徃展屮y揖sHH船\i1u群A蛾C蠻{1m&vm佝w賻M凅>]v!C&H3AHh1&世AA {-pi$#k土Dfj-?枴猛]BuX5蜊汗 z`2 x蜆(Xt-拑晩$MQ;f6d/oQ?Nm頓*N|rkPgvu罌K F*6+)P9 Z衡論.Pa/s^)tt!O緜T佇pv;*E`l翅+dS>贍TPT倪{ 0窶@%IAR!]#kPuobRべI.> 89 *E>qz：z:2,x[Y]\溯aGA/HD-T鳧}`)I癈.bA剽>咲S)Oジ> f擧UmYHdoru/ ΤRCPrj喫J蓄実 U#@BXu* AQL投e&CS JZgR蘇IA\ f43(li$ l*Iw煌{M9i! w_?住k(R0>)_^*2FT軾(I>M(PMF拒千P^+%s2`Or;s I q 嶢 Ba僣/,w0,:?MIXtz房覘.uznWKMW ?rY,SuI|o>j4BUP}r )`D} 5 7堺a \" 5DCj\qc# h$G@Px|ko-*廰禅(~=蓼躰3ZTOSB*%\6{t$ _w廝H茹N4E竹駑Y ЖbPな &廢2%+%,Z}蘆s7/P蝗涵xx#=順?菅%g|^巖GA踴y.y3气 -}勍^O;*ao錠~x|齡哽\!H 鞜_{#拒{.A档!嗽盪o菁鐃| }K蜩p:X??~O濕y奕hK)OQ諾 M玲k 柞FLoc2昆P`=gtWp稗,(N#9簪M穩Gиr.%%' ＋_匍纃N]hz&;6剛b]tV.W)0^^N錚ZJY4BQ()G◇2(X@VdrEQl怱詭'罅d\ 6 t其S _.z1'bK&0委i Vhx)1qQゐ+IK/73>a残r;/g2!#8 駻E椙ぷzx%_oh=EYl崘*:xKu us]\.I}G9F固┘え{3Nu o\ Ｎ/g5cWC3aWg73,(rd侖擇 Y(ｵNssX{r:gh]q%jcg体.r1J=z5_月o鷄ko籟$x]k&Dz1\we^=99;#滑I+藩y.s&l縉!tv!x9NmV;W3 ||-C加nqcwZJe編U) OZ戰斐 2sl4bNx'C;xаZ#靤X>倨U唳悦ULGp析w的Ik:逝]濂睴U懺d=-啀)嶝cY躡ｕ$lI}鴛墺i a=m7 R珠uu胡h6*g杵@:'SQ4Q$vJ蝴e%\址\/0岾Pp]搴右譬Fn爐l皇仞!k~竝eIk R9$@ デ<vSkm&*篳/c$]z卑Kz6FP洽WYc7#p)WG_zZD湎E^G瓢4movD,t&+t纎汞椙椙g薐灑豬拭KW/ ,~O織齡閘>Yk遼6_k<` cyO}F盈A44JFwJ媼J動zp/K穀kP罩gy湧2~Y&蕡科熨& 硬vcwLul$8\R81/n材 ]7吃綢瓮X]xZ\fR KY `豪^f昜淌&z-毯5ﾇo蘆??^郢o_FPSR?頬9ム'\3fa&vP齏PDJHS欷l?(Zq易FWl5.<\FvD+%Y9AD(彑鵠rDeWs+G'(%1メH^Ｚ^@j)箍WP*V#$怦>JFwCE粹&jPc農WL妝1トIj2CtJEF静O?- ikM0s&6L)>9!个7 V 'M"YVt-q泅誹燦R"1f仄]{"W:藜 c2 4oWIXz蓊URA^#`Yk薦MOm懃!i7My&)瀝m堀6[R7M何K,/翠rH0] -'8cDX才1#Ps YaS5yC殿#p,勝Ak72k 3.MPelcd{A@^0ZS_;vQ_腐Ku蘖cgDLl童02>CE[(V昆産咲t嚴(V3%S9*lsF兄蕉甌ADV=>≧H:{+;;凜CpJU|BJ*CPMs貰8O+A&nN^ (楜v8寯fH9E\X凄d}=%&wOhXdK JWR\|^-Nu-0啄G8ΛWI F狛ο!w+UNW,dJF9+Ut弸)Gd>$d3 7)F.F>D繩bp附z;Tv=5yOv}透JF3Lqi蛄,S*2~亦-%j]z嘉拂萓-Nf溟クM5房 3 s|襾[包kMpn"E厦錺\ BaT9Q雷U%司X杼H@A"rn%u*(>桴符mm[扉U 嬲R vTKE吋1 U/F踈>%涵 ?'湎o燠Ho捕WKv癶螫2}/EXc:BtQ於  6Qc莇 }蟋6\TAQtU缶PF v U耕扶(N|Y嬖yq-=}W7?|/莢"<溜{}68$鵤l(i/y: 9搗P UG取14"餃|*g_Rb陝晦|菽KIz%~(有?5R1$`p9%嶝3Qv:;I@g#oS>v{兜L嚏+G>Mo Hm4$e豆hIaB3I社|u/)3> !酷 V-7盈dO>>0,\0Qn~V窿hd Un0X zIGE 異WREm"G刎MH~cIm$聊;qGjBRJaイnGQ 宍^mu磋惻"聨謔7'' 8^.8i ｧt醗!T 罹:>0 哩eヾ|b慴青+\q,8Y核$Tg/!%kRjT-"A妥父_C3R [ M 禳B鰓{ @B(瘟-歩匕-QHb>"u7*槿j捩}"muE:O"ぎ蘆I判:"}`凜幡P+[ 4m%願}%4Q67hj7 '?Gl6Tfe`V#o《'JFaA*>Qh-%/+V*6罩rI\!+E各B 事旃篠c粮佶k wHO悛hGhj:PJp)#因枢:訥皀K-^ゃ-ghQ嶇埖K8o&DgJQZ|b隈彰6fTQ70s>掉zew?o?槭\L>K7ad#鮮^u9!|;,Y)O)4R~:照a{8Wr3@3. 9-Lgy x[.hF鷹j.徼t敕0u[w9怡_瞭wsj]惷eHpU(Kul8#W 蜥Mu(0Z艮怺M3&QRo寵?N竰HBd鏃>a桾%O5Ll1U>lZ綯Ubn-k[甘v[L75)!柧dTc0"永ZI8K2C7a_Lc.Er+|HABUVL O 徒=pk 5y>`" MJ頭**Z鞳銷o麑I 錏/霆y雷~7TO9; 'Zw<>6^j鯒迫#R7<&S[.G+d "W&HZ'T[X'Wkx瞑%p8 X}愆Cs /2DｦJ2D6mKC. _I委緞KNj6mUsy_.*Lu8,|3 X{3.益Sx5^F Z0G∃疂Z如d羸iRqh! !'2eL偉紛\(6TR >CQ使CSw準l郵L1DqFdlM俘fki+<%65W:r謬輩勘6U P勗U X*幤0zINzjt5g+期vY%5ewFe庇E跚a{!Q\M%P h阻%9膚蟇L8/h乗 ZFR^ Z/V(#!< Vh 舒幟p> -)%Q)JIV簔P]F陀^Ol穴gPLy*ajr閘p@^説e2c_|齪_驀;濕 eM$|;j?dj竕7tb襠偖繝x鱸w団*筝驕q"-{wｼWCR?q?=>椏oD@>;k}=<)翻[箱髫蚫oQ1Q{KB≡) KAR/@eE!2[=dG 7)dX1!&W'AB<|]IA"|Mu枚Rj2*{(q&Fv3\6rj oD7w#N[9厦q #F<e' cw L~繆r01&pF(![>g:|3r八蝴r燔( Q9d繋`_E5S(砂GpLFb[%霪B\驟DAnJI!7稷pD8鵝IpXX#q椙虧)"#y/PTp左{P胥湧 g^^B陞簓 廂漂0}痳W_頗磊?鰲e鰌'o彿鯢 -\7&ig60:r漏E)4G_N#/,|訖嵶:,7R]G"I==fJ +xO%rZE娃8NluY匐弔}UmK|*岌<跿嶌Qz亞5h&0qlcd焼Nxr< ^[=|g^ ]2m_F7Α\j桀6l6亢a使TMrq慚>[9p_"1 (1QiZFs1 唏\X拾,k嚏A悩批k葎<衢7#VK9|k涯淙j鍄S顏粧cvy0r=wx猜Vs選. _影0B橈AS╂JJK?Q"庚dR盛vD÷PcdF9eYK稙Unm5y.l[/4ra僂O\)非燦NgS&S!/頬_w蔭Bポy~U#o~-"/U閃(PSD+BrD騎r嵒0苅$(P ~<賻 '旻Ld{))c}#Pナ j<2*J 'dRp頭VW}盂F9!'_(P乘亘n-I}鯉M.PZa蛔蝪N7IW巉u肯zOs匸心敞縡耆w< )fy凩9枚@翁蹕)$|w)'<吟<短籐,-qx?H?uI8緜3% _V并)v3$雷8W/w9hnvJ村|爆>.箇藉fZ;w :LVC)5;C5PFYbvR!y拓VO/湛{8G^Rh炒杳%.+#FqJ臙:雍^佯棟q>xmg$vS]"噬;IdH& Wd.GD碑4Qa0zQ^CpZRポ知+嶢ahF零ITc綟X乙d鯤w%玻B_=斡(縛H}JIAH粐I+F@ #`航+[#'煎V*.IB萋%E=-.UgR!hs!儘r\l鬧w欝Ok%1縮/濔ow懾X%B2jz@Aj1]%0"y#y) AhX儀UQ#G}榴Jq巍81圸!~c" UR+Y<(c餬a"*#!M=]9j斂Tq了Rg墅G旒[uVh6py掴{pN舸0h彁ｲQ86[箝}ぁ\Xyu磆]N揀俺^8FQ+^bjr!wjR仮s 9~S霧jeFvhRPl>c$6モ^籀u雕 %&R羅ER;^OdWp{o{x= &;{E趁N^>鋺@qTx 何 :黎iFN倉"J)HV>+箋P AZDi[BfD~Q~L溥槙0 )駿Y汎%<:E絶攤\_U党`肋y|堊B五CHmE3G>sblG P)^I@洪~Wm% 劾tベQ]hCTZ舍0Q6 zvH~"粒37 t~7q$+%n;占}p票循Tq(oCVR[@胡恨r#a(320':%B纓)Ql}FWf粲L b-HI却.e寒zF! zRH)ipb#e8耜H7癶5Cc<帷]E土wHL~{iE9q+%囎w椴Q $ηn>f閖S(zWI r近侏Qu3(&WfEhV穉e滬\]z側5@^x用2K:L5>_Y[+r'└K(MJdb暗f:NHJ訴I冗&gz&\需8|(ふ%3>t|H娑啝1a蜴J`U^) :籀嚥封h怭k'TA}kgP~5抓Z80_ 霎cA2 Qp9持>m99>.bCx']J5#椹('Z5F?%P'J "喨,z)F善j$穢氷童=e:ェ匐oq寛vr2蘂9lhVB[裝+JW/詳$KY竄#j]+n滿K)' !E*I陛4/1鬼BO_|僻P┬*^七VBp馮泛Taﾆ_ 授}K1Q1癨K avhd_ HOCo輓[NrF|WUMa仟kPy> WlE&^ 0盜UV-S_黼社JgcA'1I厶gKzдU^Q吼B粲riYiωj g`IA!L丵) \.5I澰rWM過絃4!與G糴r!熄'!Ct篳AIbK{.|)~)W =H+O7`S)oXKN7ZU:孳*,3Q.AY堀Eje0 e5roiKRΦ鴦C.3 ]籟YRCB:z(ﾈ?OFE?m0-tLn5rF贔.P翳&MJP!na>榎 !PA$CH毯暇N_CP[螟.Np jQ)2 Z送0,3旬[N快:3([庭Q7R螂浜69[/臙L衝ZYJ!C4gO3F業ZGdrVF|[誘Mul?\4`l6&B6]zlv@F頚7.[W"%~%j/[U鵠zX徘h6^'C躾房Hm第]淌瓜| "._wy"Tｻ| K8_4B苣=鶤葺Q) rianjYs2hS9PJ0R ukZ 蹈$"AJA Q #)Ei混|懽N%鵙B鄙讃aW!71/%F }2C'來求Lx\H纔_(s埔祚&2/ﾜQstAs+s篳黶~;_?嶋/Qzp紕焜qRL=oWP傚飩$姑 4'jJ%6юFpw3J \挨訳$eM$9|恨xH+gRj^IgQ罌ECuCr諳"K)|Eun檸3k素?錏/潘3&0t\B.'瘁:n卯R;x5Gj \賽L渦9r/減E漏6l;]哽 [逃6.l束$\wG]甬裙)( G]柵左簑Q..} }JKS0+,~0BF症@.M S"脾儲>C)K r>rbW:'>k6[r舮h杤殫dCK.R-壅吻s~:<峇i壞i{K ckjAWuG7}U<率>``k*mツXK>-R8#E簷快}Z>qF湧BbAT}>ｸ茎{`瀰*依G STB?0F1R`J/gL[")C+|Hv./d筺!lV-L2泡AK&7c\le斛A壮ΔKiDC晧%!麺>$斬C*NB,?XsS}H巒W!m}i/En{oM;j屮F鷽|H8ze4Fuh]d:vM葦k#9%sNrQcguHWQe濫N9MZp8 s;o::I)a;g 膂8}HrC芽炸しjy|sFﾔEvりL(K^桔)E)sI~VLB叮x祓q?迯(# r<2vvkQKpl?vv!imqVP[w9;It2]D3S:弄註0>nz7F "鱇D鴃u蛮叛^ME璃zh砧y{+@NAou[4hr寄j2!hJE21UMLceYﾋ)冉{Y=n(1雪,|電 9=杲恍=9VjBMXJHV hX塲hPf$ 5Na $軒[BV^bQ:(@i`@fZ鍬.q^;o!經 Uh鏥2ｌ齎:`:u{7y顴 m[w:iC騏(p;1d險D& UV歩BSCK7{RZXl=獏(,療Sg 6J閣Sd\?“!聒籬P庫ix伯%E(P慟)<{j %u\蛞#) FuS畋P卮Y) V溪紵dO梳eRPピ孵tQ<$繝O,f蝟捥竍? |uz竢?OI懊*o靚_龕gn膀2m}oT互=~V=褐Wx|袤7ORMK 瘟~FK1ΞyIK逹ey_f氛 GQ蒸T1a,びL+"浤A獏LOiGnz-K\y/3 8XM@te>j-W.|5i襷\Ja釦Md穀$F固1ok3扮9Xt(1悸 3&iP]+4!5u菠w:q樞W史u伊E.栩\_J&[] 2碾碇興Cl<孟f倨i?iGwyGJM;w*標3,FGI ed鰒d~K謄徙_u>@墹TA#;/%9 po"О]MRzzZ'Θ逃Tz%4l`垰l?J:蝴R(rM\\ FI5dBH甃a貪冩X箭&Hm{槫?J]愬n;|G昜H  +翹x.oE`P LpV>he.KJyhe3靫ｐ孚44oJLt藁ゲ[W鶏dl 吟?恕褶? 0=5z俶譌_頤7tHjL薐V46mZi>N5UIPUI,憧 v9n78禊GlcS亢 {)ｩ 棲_)~崩侃k -VFBh5J*pFg5*"椎T鱧恠舅yzSH2T.¶0 壅粐 ГHUёpFXrZc$|xa MTg!t蟶@'e0r&s@/乘FJJ.^彿sYs(j)D&6?{oh)垠>2}0吃y-{66i零8鯨?e(/Jc)貅Kw_胥泓d胱鴒o燼/美骼;鴈?;J-朱\ z\演w]T?]塲&,Mdz)9SKj0MZJ7%gr@}kR>#wbN~鄰,)諛7L紫[ 馭挾I碌X=9,/,D}荏匍*Es( 旌 }妬 {!? I建/yI緘(|#'p!?9>xFM<朷R"!:2Wnふ按#p*H鶯斡|#3uPLwNw墫`.G茎n 怜Ft/E>散r6kCちz)原V 9#},rOa03xp-". 廣B) wEUL `L|fT列Цy)9Mn1气`閧>5^MhaL 朶^}C%%03&S#畿8 |LXFpAS 訪K`eN"裁\K3芋s艀o*AJ8Φa+CJrid,埆w辜k蠏x)y.]5Mo/匹 o(Bopmk^-}n蟆gz97drg襦x巵擁^哩碪DwQk~娟s甍|9惧i\p'<漸AUF鋳79N-S妣Q幗lC7~徑 苔rv沫)HuaPJv＝J>)(兜z9eaK怖$ Jz9x.(&薄鏑Whc'-[t圜^棯#>yfO;6}鑿::? 踊TvA彪&臓-J楸w}$*&D廸eQ.9罵滕_-t&.ZR3T,&Qq%s\梗.u状,jr鵠婀!TW }lx r7{E}a竪{伯a豬z罅c()80a鈞訛E^nr2=|_" $L宿uQ8om&yr9MV 'K料L-9+[dJf&%GR**80d鯑(品(+J/ ,"藕&h倪Y@U@A*9<&`麋$ hr滕拊Ｘ贔導櫂_7疂B)b`|M7r]=r@`^9YS:f 02PR曙w: {=n.卑彬楾^z\ヱp-o?(o.齢g'"4[鷙ZUPF淫SXuだ'AZ@槽(E濠Mg>\k<Gl京/kiws$6N@@λ往0x$遲d$10}e{袂'CcW` MwqeR5n$=49-何y7眺NEiY9EI睡 cvvF禺位l&荳 cCQr}夾gF=44 /7c2oac I& 蝿F~f@';Ee,I(R兌藉1黏$坑5r齣IY@z篭`*覦酖e勸%ul存Krk7m;* 猪;#yE;]{m吟傳* n Tx鱶見頽f5")e貳m>C?5\J?E?:H{KCPD=F腺\Jr尨a@c]4 $~K^ 絳=*Pxz"$3/(J応(/肇XёXW>veQ Х'}|_b^臙^p0@AZyr;i繪隘e^ jnmaK尹?L; Jz*1莎I.K驟S#癆66f痴Fv髫]6F銖7m\N2O:sKe/tVJAE2.\d[濤抜l\UyX&盜S>e八l#Sh.W勳秘05\ wnS5XT$]HlK￣>?Q&P訃?n#BALj br9cjAN儒YC|U゜^g,rN>Q]Ts,&.FM柘>n te$a:4F3.1桙.>,Vck惻"y;(Gh黨陽(<Wz8\h黨諞陽y[]p┐#!猴H 円#|XNoQ瀟(hhMW ASm7)UPX]Cj+vYt[衰{該4└#=O AGbC=#LR0Y?.Å>Pk穣0A|Ze-伏}> 削％縢%TZJ8-(ムEU5fJ寸,a9yT.Dw艪 _;/gbvBAPJ;gH@mXk2eeI姧zSM率6尉禮Q?D*閡3oB\NK,[h>瞥雰>Gd權HByi5P&Kb,>_模LA\fI恊V篋蕗l 8L5bUM笶O 撫>irFK|錣\.5h)カQ))魑S÷c@ky曙Qc嘴s.評Q繁OW:u迱@縲V>gB瀛"#~kfwI#iW7FM姜D_寢ROＺ8}Q嚢A_雑嚢薀E/Q嘗3[O轗"棹W┼"》-{r6万.gT94u=&*838(i*I#y飽辺勬*_Y/4Xl烈V麼bBL)e謇Z棗sam鏤屯NZwu&a刮檠UIZ;%!ｗ@znz胱B)l5汗g9# "uD8|!4xΤ*aHB )位~+&杉 Y)嘛尻8.P章E靭漲Qw*j{P{E3ybHTiJ辷幼(s-!#:=`v《lZ|*V)頴MB )p 鎚#uq?M驫yy寝&1.G感脈nzL`3辮'梟Nlk;k;q p俗}xq'[捐貭Bnu%ME: 蜷%Q僵]咐 [e瞼vJ慘m5;JG;A配4(新*C副*万u:n糸4V  0忙'odT,6廳q,uKoC?:(|W?w+l a%q49矚ouL09.guy2q5-f*NF s K/ YaPj@F1Oqw"’yN4k寸J IF``Gs$i0)\D墺 Х雉 V鎬,vgZH窺榮d5"o~|wl*腓)gｨj\C0[1.mz6甚q=Nr'Yu\qR{F6?k _'o=%pQBTqQ$U6伸鐚藜披\%}AqY_-652w濯gS滕Y瞿X壟o,l靉^yY害^%(戊q#涕RQk0JN辺|苳2zy=Eg1.唐MjL( ^ fwi\痩淵.=} }糒演Rx[倩A_//\%3#私*j_B.:Kyl+KD+kMR}YB{M@u 2接dN+( 0${j `X,G+6H耄P?雀o杉梍?6W硇~_`~x(`∫bNV拗gm[@Ix凉:(弃E鉾C.q2亶掬0)A51_9^hu淪輹B鬯策エBhOS庁"ξnma}\C(UHi!cG卸pVFv],_q#Lu1~H Q \^.+# '@H> :1笙#畆CgJY2匡 n~瞥兎bRa2D析8$錺2z悳%@]W鰕_-─]|t^憊P"3荳 @=jxJtn気0f pZU}Y=}A竜+-3[恢嶄R;\榿%LXjq]屏'EEE`q%伏zhmru}4鞨~qN,^[|ウ2氾Qo\S eI&P 家%:k68e5E'&gf曚'qB?4 Tj@^g+G昇#RW/u努r]}祀7_W嘱癪7~+= @4PkhA 繦z&% 8d t>fy] 6"8r℃蕋WXyj]. 谿" >淋`j{l1q?C_Qc%WV丈h蠹T/dFf2$$?VOLrFSMJ顱As"oc衂J$E8;+r **kUvO, LATY埼紜bo3*溷m2UWX迂褻HW16茶3涼+TL#裡+E/q 狸4遊9(K6 人B奄[@q}pR;P"I'.[wP>uF4q!l^8$'zK2vV`}階YeN69+聲yy耳鸛V4SWzhiヰ*Pb,PfpOWhQ >6kﾏ頓Af/%丸簗.T芹9+{]旭%Gk)h.Z)>,sx@vZ.9肇N-團0%,ej娃QB$'a :H蘇t*#r鰻Mw.っ離p E/7IY_脉}QA/>菅縅_烋nG宜\"% pri$YAsd倪u5!7:w兌p@Q感~S*{*V6R輦K畝Ye`vo儔5顧m > E加J+檸筰5二S蘯E掬汪皎楡'LKN嗽t* qZzWE~nqSR"Ei-7l柬5旬蟾畋;娶b1Zk }_杣u鶸>mg=\Gpf?隣》絋F彜r@妻tFq聊∇{t/E`Fl0謗]MQ| 窶V}7度Re)I/99m`%(r YScv`x=C97 [} -EfQ@'i+^疽bR V!g,zfufemj6.p侃pl3i裘zQ`U3v}](w}t牀4#:X隙(裼\$-邑溥gnm遥)膈椀4|E;$'r7)SS 狠2^Q6|A)q 煤Mww3hP尤.[sr~W'姨#}i>wg:nF /坑9ta環w.Qr譯IG44%}D盪 kbn N_wl-R愈椡R4&r+モ聞t●#B0vw|сF膳c|^#l v6J1縮ykU>ｭY8v繝C?噎eT'8}u rVG|%a rVN>#EeN驩1 BOF1?段Bg圻 )E/W%vFv 7RLL蝌UF'A瑟\^CGV_Tx$s{JOM敖o.鼬^#{.K"h9I2g#世` &%m7Q n旗羯Sm#%} 05S=悈河  g囿60r uoSnxx∵ ト{R$z#;\?)H(oy恵[lNx@\B\?)nDPFge漿匣VLmL(牒e0AtsA 挧Ib!Lu.&5(F"甜k>oC9r綛齟5z0*Q6 ^RX0 dC z/礇5C) UuY\然;vチD> B xmx|y(aSir鋼@烹7P:零zq#=cr鮑籥Y#獸冪A$_z5笑`b輪↑A{ 巒}&LBH"J ^|wEY/TE6豎hqf俐c}BPg皚gP『iz j旛p7})WmrSQaW<{sQ- ^o|拶'梼 噸ρrYNR&6*E6="&d蹈dk1L6SQnR}S$Az8@lxNBE(^~P童劣&:%Pd^(疸lHUXパjd^=NOc頃5蘢cxi7M03D}伎v%(b#"y錚MxY1rvMrm!Q(!3?x9d何*ERW驪#;(Z\f8Lg嶌i 9d11眼Kj}%'遵l@&ikQF&IBHQ g}J守:].囘y莠(滅M仏Eq店u3溌!}zrI滅G",遐!Cr!KF{嗤眷2 !9 恤)<>x3 9n"22唐ZL9%FaFI.(I4(2 5SsC^f珥N}讃#V/eUc綢gF{zu床R0P*f%層S ;)0"*tF8にAuDQF 1Feevep]"VL= `{Ai @i)躋RWｅ儻D9AQla鯣x叮e`穫%8唳ウw03REmq>峽G' Ov%避q9:-d$8hT5BA椛VON:{ 輹靼A罩L3c6T太埠嶝plm祠a LY 替~\>0FFFP~  Es6Q^J!P閾0q 棲兩DyXk}'={匏QL桐jefp Pp.綢兌elVF6r.G }涯H#D=P`鴿T>}0mKG7S un^瀰]3[丁 qw%,Abv'X3 0撲廂樽EB>v5淙恕}6(G}==衣7>7})8璋c#Wr填pa+N遑b拌<}^鱸B 5%r\Fr述/ラ撮峩"瞭^->V稍a5iJ休"宸m/jn請仰5OF,;%DODDZJ利r 矣X1"fz-T/友A1jZ~e旬f;/A1O#)BV0>*)Mn@GHF骰苴舫G:淒順+DJA.|H/3鵲1ｈ頷m縢GH便m9;窕r| -(\arP g>;#H^a返^K`j峨8,+/Qz8WX25悩qq悶q豌z4%$ZsVJ炒Y~4~4Qrd晰洲~ 4S*xMeJCZiTxzk:4v%!精X7豆 替e J*jpF e*lH BQ0Qo4 3pQbh張 &cmUR|3+YA 辞KE d1m*! LyKIxKDJKK9*V_:gLp%.G0-T謄迯Vp6vZ "=7 6Dzn2.F\u⊆* p歳u | 裹R囘43Ｋi瓮.└AR.n3j`佯護m燗}d+\7湶J]zG _y-廚f^擅n*扮$tc>}У(:%^RwqS*#y3C@3 o&=#`)k{^r*]1"Z1.}Xy匳淇z蠹Z#^=B遨/?x2i|辯/|噬У <}x~髏|lexo~矚._U掘Tl&Q 峰q/vyF僞D[as )O|jAVZRYG909甘K |S凡:GvFYcKB品馨'T刧璞d#}$<]/瓜W讀k3\5誤0wRW)# ][5LW稱p紵Y久舒憔)WMYI埠/幼)W31sY: +俘KoB瓣*}状QmzT+y){a$)6э楕w》'lFiOezSEFi励21lM'(gFTS"HQi押" 槐謔[k )p]h ~,*{]h);況z@駆B}LlylD:ZyB餞g菰a:}0J3KqU +0K [="ay8:跼壗K珥<9{p襲1K$R^9,5 xt$#Q&WOp$F,犧qx] HS枹+ BMm^\吾 3J9#^嶽-JG@_|Ig閙誅~l佰鉦P"[員yCn7堙;P6} ,G6uhVYS-4!p荘煌盜D]C{ 魯+A{#:'W.O$oB} S 7-U/!h 隧U盻8% -絅1泗j熱giviD纏f>Ng祗>y}L>~bs~股M} W f|.蠎+i┠3V?n[]OPRcdR/咀`~MK &P2莪\|4m+>品@\CrTBxWK2kDR mU椀zT& d昴稚Un[+qMSx鑪#wwz/+颱y里昆3邵_+q=vg~鬱Oqv^]9xfoQyK\fi2緘)磁U -#^2S`DjBPrpFnQ_S;kBz4AF(HJ儉7sqNよT僮奄m:AF3pUI$筬謄XtS][s>g'i鰜J)7c_a9v5}ZMMfy廻c坏飜I鰌W藪鍋RqW_逸吐4*GM9S滝箭`EС:#iF碼閃B >塔mGゴ-J儷OmdA9I?$ IRt8)m!!ヨR %`5J;Wmq4E'@Ar.ziPJE;p無{=9椀!wLs{z/ Y|x\m]f /p#/孩CU(E 8fh6w H罔v扮vi/攣&K`*{ Ze/UK@I@^\d/WnS|b踊iM'y,6! F掛簡R滯,'\髻掌8Evt贊p2K8V嗔Y[FKrtvt9%(G]- i+2e;# U\.ul/ul4抛l 勺Q3@^]晢 (WD0IN.+豌~P燠pJWZ帙"V[|H*CuJ灌7~{n事hV5\r)釦l頒Rhn脉C4Edc{F%.f9&ぜn濘?]~査湿=麕o&c[N]絣W._,g J=g苡>醸d#呑^_湿!Gq2zvrwysy}Nwo?D昴翼k8'5j7_=(想?JY vy<=cFUwsy^髣輊%#D%<)3 L[>=QP,莞F1Vrc m7j  pn^-L別yj+LR @ bO{' -m9Xr-{ゅ>f%ltTﾎ|D'g/K.j俄\,竺,giph~法50SLkZm雲f籀zQKE6B醜<>1:*UHr黽RE嚀V$L%; 格51*Up6袿J抔a`c%P惰MeY$xu鬩D覯谺+t覺 乘1:4S湟ｱSOGeQ$阡*&ゴ-(舅.w恟^\1r\ kZ8]v~-M)QS楕ナFWDo挺oYxC爾Y♀A"Dgm宮4ny'CHU!/T"!_UzE;I5^D,華l襞Iy*#梹yUk6 耳割+氓Gh/*[ C|OEp閘郡h4W9鈴Y25 蹈V綣d7^陜簽乍gKv髞b輹 2bu'#F!/ 籍D@F =_偃b<hz|qy魴/E.M>yG$o渙ド PHrxq_ ]<^滯;;稈t逕R.[湲o#濃囮聲詼[H頻7o{K蜉仮{sy|A(ti}t稈$ d齊q|6槲鋤)9~^箒慢舘愿OT針WtmN]1HT/c枌@!11H. }d _1桂nB%%BSTt~疚#?2fM-QtlAHV傴YSec*eg桁;i,/aE#擘贄y|7耳YMQ@vhaU>/zF}^}掠鎹qDd>m2u*|^W.y;}^.9邁 "]酲%剏RSk:MeTe 4+B} 30b稱&1FF\Kv[G佗_Y螂95HhIзlak!{kbS%5HNX6oL%潺:18DUq"s(,^P呷yuAcaIyP,{hmq筴{v\m,$閧羲xjZi隊ro7Ab!ni:bt-[\WH>u"_]蹼J;gFHl4e(}H 閇未iz^Q儡j)蹙)51/*2@d\鑄Ez=JI謝x戰^K[鮗 酊8aZ]=&thQ]鱶kKN鼕FHW緩+0> ((H{ `E┰$怦粉F頬y*iv#→maa潛K)恍r0uMIr# 7 g@)\Q葵yE{i--/3mxs,WzYQvFD靼I々@鴣v]?s ?w瘍^О畤募!U' |EAr蓿F+0!阻J(^ >P$.FKdS FH_^|=&=厦栴i6,NMo茨sK虍屠-70睾M"sk7K.[E'[Y-元zT*V劭5[K○k"UQ;|Z^xf1東1Af幔X亦hkytP3Nz 7aEK! M8]K>rU飢脹@Ld!0= EA1Ebb叫|瘤4mV &?zC閏Qjt_\QR+"9!^P"磆`*閏晁展tW)n$lΘai*|_~v驪奔_狼倦| Z2!纏HN${ z怨{-z亶9_'Z-~瘍弖??帙*e'DedYM$+5H'`ni$"&褒\僕{%[y#GhS鯊`*Xr{TvC]K_ #t25 Z4琴jjBo 艷y9)V5嗄|鴕>y脛O膅q`姚j" =4?Vw逗13%}Fu l&A/(よixaf) 3Sh歴JLj駄VBC梁Lq^3欷6x^x7J^\,,%UR+%5扞$Tk从崙Dt1ISJzt微F,-!Q[A蟀 HL必S芹e;p頂}up陌蝨O:wЙ=繪e/n_厂0\S1?]?>鞴7[智L"龠R%鎖tI1 tH起L+@群tC"臺UMKN椿萇 (/M餃L]-/%*93笛@q' 簧p+j{%$/悒mEb0F薀Dh&S%n-r鯔hG'ze eI_}8's^M}'f懈O♯糺ﾋ~萪LQ>&U霄家４<y $GV}0─*陣|EjHe! a8漾7惑Hz]F Z`H奮, d{2CK/?T&VHf"4(;1)NG儀~5枅愾U VqZC;JlG澳|@宕6so巓q|8 vv鳰n臺騏q:> }'OS 嘖{W3u"z9%e(E)`♀]〃N9+P\7EブHa鱒^":/"{唳rg[う暴i`j曼~V<me{-Y狐 Q|iX]鏑強*RU亘H*j紐)-"*tT3.hE雰Is6C<ώeO=ｭ&G?袞\例zQeXY袁x%x-&枡磨'7M蓄_AnZ哄S揖$Y{D噪98[1ck使NDZ撕xs]d pKmp)J+へU癇腹sh圻臾r[M`蟇(tq6d罧法Qu盥j2Z*甦{Uibp<e9i鯣柬\９ 杰tB槿Gsxv裡zWDd"髢聟d跋/U穽z疥霽lH2+4&U$I g9ひ1rNE\.cVT eKh<岨;.rb鮃D9Zg!N%(b-.竝s*>N=/chz星]U%"/8|z=2I噬J"|9y>r狩!g0!0Hq^];AiTAP`;3締鑢 膺[j0薈搆5g %4 kjh`F慱%<1也2S 饒i√Sh^手-L%πJ)mMK>L○.Yxrf/Fh岌勾肌VU塰肉N簍WaTKf%堋8?b痿皷v]$ \c'&gО>n}ju2e鍔F2y 纐`簟5臙#wO_T%軛=読$暁0\0-hai4hdZ挂JQ餡q炮BpWh$vZWExz#P3嚠c],X怪F英uE+;政oZJns pN)S,`月At[P6c7E$:yx*GWKl<5u黔^游R}P羮"O0QhRJj付q1Rzh/JqDOw|%-L`Q橿lnz .4WyY5G@遥%[п/禾$#F8崗M吊p+C呷I崢P{蓊5sDPw;迭?HQ6科*'eku=/xIl]b%lNV恊&K翦k=}< 1X奕k'北khB]7!ME W黙`U督ヒ-m;?苙K{捧cp. 偶aCK4v6H7lO It農iH/!yハBmV 卮jr1B愚iG瓜\06看P x DySl抖x黐D6d($fwU" 9H!'$vO僭Yl5u屡[旻5z綿J夫I?5垪僣娩FE見=0:X zo式O?O{/W?}`飾oo>嚼鮗QF謬QJU{:Tp襦繝6 F1PUcvtY;O牴|Di霰7A剖R,y霧p0ＣAUs近陪[" 莅勃&TL匝撃`jA{ -;Z/NBR鯊Q~-KlC lS/GD}hc-XMC~h'@dA(q蔦NW斑拐Fl5CODM H]!  qE0]RBE]@jal=J亂tIU p_9箜_~?序歐@=鑞徴蝮OjB噫K@y驕9: f衲vVkDEKwMh-o溽lS絅!瞹d ｳq"&,47yqW}]峻 /dmG5Z/Qt-鑒唆;+Lzw8U}B%HA'n< RX^`c{PA;P$]>*UF4{%oe` 8xC邦 ^2著 BaβM麋lN>"G,Oc【e+A2OZ#H(!|1p;.d>&UU"-lJ~_V啾睛(Dd:巌2<聚uKe孀'O#閊\K,妍%(>t)+ #K%\CY━sd朽*笆Imis$鮹皷B飫慣.楢mX\ 釜怱逗PVNy恂z扛絮V2罍0V&8/A oR!.T%h94皮k}N9;6!M望$\DjZ癖[,5it妛z))Z}H.U条嘛%決fo逍┿u慇TNskG迩逶Oo_執\炸1|Y lv-HV t8s鰻聹LvVS,]BK[TJNR戌? 9 F可f臟25;J懋i]W*x 2{1>勁蔕判*藏_ W遞;s藉}#皇h去皓@.0ZO>iR]=g湃膽どk不5]踏ByZ 8s柞 ~GU3H"~"~螺*I<: N仙)MA,\H'TBS;{T =/貸TAcovm6禍+5MAKFZniXL壯侑Zw賤オZ,K{YhniB跣j*湎=彗]ww-uqL$良|'-堪 {0VYy/s vo勺<弭=!泡Z6C鉉r:{kUrぶF)92I余aＨR袷@g隋!淀腸w菅qyGRNM%=& uW-欅d-lrw-Yt挂R|l",o1匂nV豚#4r~NC椚V(\TtUP臻j4罪XAa,DWe遨DjGhFf竣@:九y 0RQ}j~-'u`秕n傳 tcCa/a“E瓦Dl 黛|6b5<(.^t-'eH‰旙亢@K r *mzz+!娃,%Y04WKd覡%W@x9I隙-!Euq-q0鼻UM"s1|k!梟!%YY(C9n)jtwU}k6P席*^驀+j=T茵rU痩i面^9xﾊyY型枡丐y擯8NS`7抵_,Q6Qf┥%*J)|1HW\%-E謀5a\mUVt讓g4V e耘&R*携竡emn\ﾍ'1kYNn嘴\窈妓D>[口.A-MDhK^@y枝又9xm共,☆94鋒贈1!+@hR縡~VMMEg^.Ew|mRf,}csK!3o_fWB2R-e絳Z: oyi畧#Q=y#t群d7M按j3滬rz 坿 肝UYRt侏BUu 疼*4蒿ey.t鞁u<鴉娜)0^pi(霤熊鼾3[ E憶]我豬 蛾J?QET-E)mjCJ_SmvWr 杲EpSu_WTW7Uw5;1U(`:SqcpY8洙b"ADM6 R転{-@$eK裃%/hu-nNl&a44 75QLo冤y%/{LBZ-n曄>k^E8h帑u.q\y褪Vサ澑j*&h$准 NVMkgn糠2aHv.qJ戈*息0Q(4wo_濔;Mh<}YUE= ]!&+{=h-pZ5Mpm|4.u頼豈"籐*Vl藾r#"{-@ V冀(m冀@Ert!&>O%=Ue.Akh =チ@;g Gn}途澑把_Q'PatY誣ORKm!&a￥<羔|宋IH#;,Jl.5%刳e4潼/オ験\<+uヘ)Vy臠(>yU_"桂rlw漲S煮\GZ2 q+|3*&Pe9G~┯qbk'^嚥2J津*@X yed'S提徒k i 挫5r酣悦YAv^bN %%+-) *_n' ku" C%ML+14w岩%可/<様侃殳m捌_&坑uNNE24)+G$NJG+^=xUTr')yw-/XW/QzL猷b 粂[褐:u樛xxSoJ粹0_'zn3zhdk,焙%b-^>.蹇B雋Ｏb羅l蚩8<}h!3S({& a/Q染#H9.!MZ^Eq↑+%TFn0*L%FJ&,錵&lu-YA(=P0)]氓5垣P5YurPl纎A ]撚雖rC耒RQA$zT鬨SeIDsxCW)^G兎f2＜Jh-*b~R#碩姿}1LdJzD#D.FU(hX獄Aょ瑁y畔5 q@珂Q籾sO*D4|LdZ<'W=T, mWs &魔#g"l;衡 h"y@鷂0n}Lh wE珂`8A<`=S8Z癸`l忖B昼oZ\G{o"UE4qJ.ヲD2S6輙y疋[RBOw加k ^kAQj AWB睛G&b幾2B{^ia_D_竢闊b*站 wR\0'徭8 'Y 概舟{1+eA瑕] =00唆>慰m;;01\6巖銀|{4e]5b儺ZG%鯣 >&E)%eb鷁 c5C]W K}62{^UC Cdm4|[隙ろ訌v05-^鍬9Q省央p賻鶇e%+碧 Sh催JOrU9G鈩|鱚地dB+@Nic&翅.CD跼~娼楹奨mI噂{C%KA 9LN>X ?7&pR餬H)TQF^K@yLv]|SE}洟^kQ-IDYSDCC^兀1k|&鮓!T曦4:QO8柵szk?tDzUMQ^uE)pЮS財聆.h9(k口'eDZ蘿r>%x|鴬94sA"'舉hh>)0$8ag+ '-iｙE饗模鷹aV渕R欣M~bG*0bセ gV]F妓ヶPDk"磅9w/=蒸簇b-!.VgP 蔽{-`日yT=J#0K-4O=怱Y^yTy3^hAfW壑J4!up悲O%-LbO|eU痊vP6Y|(pY~*. +m;9 }5&flTiLA0K褝C*H│mWzE枋e ゛KW~瀰#r c>yu鵐u睚巡 A8&Op66v()畆. M =蜘V/m!:\>嫺?~0{sd控x#莨EZh3jO^><係ni&<,'&{Y=∪0T{7Eur$7~jl(ZKRE_ =M贄T{{^6C →蒼h@73(6cせgo[ 1lm;務A[tft-t^F$J@rneEk0A z紅P袂EwQI|sq[據# W n*Nk`梳卩@CC▽辺,!hK U?'("`fX$0,i猖3]曝I)Hc *a<8[R75沛傀m"鞨Y)胸Dh< .UeP8E$)PAf(萼#4bm`30S T癬 歳xu~gES9笈l!w H0=IF+e槊sn俎+iu-J4髻]吏飴DxbwC*rP碍 b▲oXAQv孥 FX?yGnT$w]{1Sq7JTV!e*Kh*ｷ`髣7xfn蚩8梹"6鉢qD獲TD*s_凱=?yn xM0Ws/3Bナ襭3^q薬X6b+V窟"6pq  央d愿J篁Ki4獰4n3 s+(y2n;K碪\\蛉祇Ighb3/!8bizD丞mn!u Iょo飾`nEBY゛.\ ^c高YLY甜R敞vlu 1LYq堯DﾊaMHrEuw{梢F^:uS8禅(h;関"_A \j戮H俵IQ類`尤+5#G&\ i0wr候 3y@抖(#$KG蓙)Q挨П)Y[JN^=M1 {p[?柚["g鈑隅b0n(MＸt@X7i^д儡1E1u,'P$57I珍"tY W6;璋,/xt0蟶庁cm.m!奕tj L :8yu坩`cUi>Y/%瑜K.[歃U繞三9rｴ'#0魏.W兜 :L淙sKP{河Y^ Pb?FB^煽^乖+^GC]Ag9+DLqGi祐yDxpjR&]up+c FAL%vc鰡69IＵB<p2q6UmTeX~BWG*顫LIzufP!,VO(鷦E Y67Q&2O%士寂[%ｱR5VA[米ZF:崑0vm~l$'fX殍8U@眄鈔monY:Rq7&n!薫h qj"Eqg6,,CnUuGq_ O Ci症．$Dﾏ瓮慴<咼慴H>DU"$D-".矜'J.,nP嬢92&^3西/&K7W]7EJgIJ<7x @"磴eE8-9=e} %^lD$~{ |Be "aI^G軒kiQ|dO疸希E*D*9X@冷-T~k5 坂+|鴕>'o./歙ZTt`矜&元1q觚誕(夾l;JtGh視by&_bh浜 J!穰44W1|!j$圻Z1鍠"B|R !> \荏ﾕ樗 'k7l,$攜i ._b TI[M噫,pRp3=YP蒸Ue%Gh4`*GD. 嫦鳧D 諜LKW ^C遑YRMY O息zq賻'e .ＢBV+4k\2=EA横](uwUi)s_Nf~ =%緝鳬奔_諄7 AC>↓`濂K-萇s[ YS9gW,q爰*B^Y蝶6桂亘P7U矛]`]慍.i7Q犬=婪QB滕悽黝J燿m+vHgPkΒPyu1紮%蒲$Z8慓 xG植pex:F<最&絡H1Ayu!~cVi[椀!r李r4[\K RRB抬Y虐gjnW.[衞T1篥l*yv{w{畊危VKr膾w7BU-e´K1^*3w}=VkH&鑑PN`f*v灼 纂CNs9d@螳)SじLnSiK(T~}du0AOIATJLFJ0R~$Z9 臹Κ轅C(単:"盒y戰測:Sy"j鄒S[-r=4IK@V凛?d栗 W#mn瓔 \98嶢l zO@kbV6(v"y椄af挧6桁@>#**SocOzKu ]訂Ri"S;妙q:s1燕E'父g/o<^,Tpcv/b>る堯y5zf\_哩撕;@+]周8}s校執湿腔fN1j'5<3C2eji>紵栓uJ腹曹C&I"8%-W`QIlw傭A献3M>GF%K)(%9 y%D% 蒙;;cbキB:y*.7“:[j{b-k4](寨4;lhgp`H1噤s?/+@hiЗ?g~OGVk8#XQqS]-@ - gﾔP%6pPnDaD儒EASM迭XYtj)t42hV7R$蜀Z6jR,$!4f)J|粨b h$"nM皚ztd0>|C"@S迄∴pOgE@5NP絳e７{0zU狭e1vTu!暉G佑 52楞綴J+vc")j7k3褪)-鏑LV{F;un(yW89Z5PR82.}.濕$"謖sH堕i_jmDeD|."-于PTvGGb歇^]w)}A;)j/}せ-疂O侵Z`~b抻Bi#荅ONk7 壗p8qHЯp仠`6mz`pwNlZQ+cd@覽叡x冏 姚善Np(ｽl靴9KR8-K犢5MciMRAｶBYa8*?寨8GD"q"滝站p*#tG"JGyiIZ[錻C拌F5 T0鹵/"!|+`d & w\e伸9+ unS4Z嶬氣#i'1&7槧}{UO夏yVS`冥*i%.)誣xUV%4[#J汲86-,1/ 命¶LZ]= ]<$賈l@s{p腔#銑[z7p7{o+桷狡5+裏-N纏黯牾38]%L;"[橙)Q5肬0Wthcvi 4aZuBT 7芳摧岩Xy`"LQ.{9dpnxX"O果 疚I&JVH P‡PW~05@!wDcy院立Rvw:$oyI7!X榛楳c{^抻h !迚$|gA W@ _6K{晞sP_泡yX倦I-[/諳冕槍陥1K~/!{Z囘$!{Jl*-^x?=@qJLwhUZv莊L]|hS1%^!Jv%W%aVL體a 皖HTi関YYy冬!'q!徭TU>DC\UEW涯1=@4Vvl竏; *" C^盍F很#緡.e翳{!{PDmf<岱Z 9:)kup朧釡!g伸tANPzNＱJ,V(飜0/Lqlb=\)2WjD O?iWt'翼%{URUsv H鷂I?#M鷂棡Lq膚c蹇f`!+0[ЁZ5m嫦mU6rBf`QE イ5雫K9SluM伎R鯰\D)Tn]S{K|Lbbw4@f q尚V 曄 覗z?"勘J"rZvq/CE<'lN,<Э釿Q+f>?w_椙止S )d^t3@X_}}wJ>N(CE榑wI夢lf焼mv硼"6edkzc*S7薄?閧%2YY煮DZ(Q,OEMrL1Y笋M%x4i $F-]yba|袤&FeT@x`<="}\n+/芭勦(3寰y)Y]Q20K^*U豌mJ0{im湎%kK*U 道HEM帝%O8諦e)┠[xkw飼j;帽dOH_B^覲tF槁Hy)繖%^Fpn}禰 [柎M i3Eh亞M/Q5TlxlA:?m膈Mpc砦TwOR`饂7苫zpWE8KQ/]S>=$禀毛/9h駢*祐6VM8KJ,g|%^ldP@WbiJ_IP+8S$喉<-箚l;f"%\\~筬遘THW[ 価sP%E冫EmqdA7S%EW舂g$W憖n庠eD0j1%P0&旅嗹`ILc}:舊.=Ek( ~X{ !%*儺$JT Cad伴@9`Zh抖dV){Y(bZ8miQ4XKZP2+!S藺R!/"Px-_I FwE賺zCc_TEjQO^r齲鉞B)Xe2 7UsUrXn賻nJ覯垓qRc>(盡c辣湖B_Im-A((I-yW%ykI_嫺S[F"ks1OFc^u2 :f7v+瓷霾`Uur-v*里D{債U bIv~XfV>:h7VPr彰=(Y4Z^ L^b Q ^]Q#W勅.顔,REM_)-(bCTbdCpP Zj+Q KP=絏EE蟷=KB部a S}Bw`MX|[*BPG%8:TTa鉛D^%I <"筑a$F%zj\OaW<&-h調uP螂 pG鴪t銕If1h*J鰄h珠 %7q4i2hj*I&箏v&UN;NrtVWdv\&l]B; `Qn粐韲7oUn粮=榿5t:.縊L8}綻LUB采l;.散<\X9 CE⇔uD!5TbD&`Ns昨!@k鍛P^^#J 塗-ヌc>v詁x*SF w箒u{sN: S9彼d},$rGJ,m)M2K[XnNfiS`@3X;,o~ ! (TX克&o7慢?;{暸L;j\OTY RfW圦+}H.sKVTQKjll_卒u56$沍-,L搴WRM12豊K-{Eq趺/E 毀.溺=*OiPQ`8睿d^s/y Mi9!^"巛 Fj=丹.i#$\mOF.ZHTe{(].Bmq59亊f`@ H[]QBQ=Ed&促]櫚zOJ> TZ閣h*県2隙"\帚uT惓JL"g% t!aHyC*A肘XZ/rM6<i'勸9;MDrjFYCo 撹Y*Y縒vhL菘iS絹銷_|xH呼_齷?}途PyLRZ"8jg玖-亰N:皈LU汐.LU稉f=R&2U nz覽h*% *[很JcYY薑':湃頬麕９百P;2u+:|絆z3縟'd+q猛\=>:(fm\sT荊5j{FLed'[UIHf甸奮)ha Z`newj<@e$W塢寓(/r纖'x75U%邱/-)#珎]OY=?森"捌w5z~?森"L1瀏)!JJIALI Q|WTu&+1_RpdB兎Kul幖n(AV、>克WBV{ [追XURtu&疇正= ?woGe珺鴿IdJ(,$uU _碆U}4elE ",J欲ReCk絅塙Z{+rq賜&~d|6Q9Y*uKw識x6/cq_C `uy\e1a f6撻#;W=x^6菓H#[$ N#[$%l z2I -Y~xdCrk,g珸9 温K#Jd/A貨躅f>葵虧&欟ぅ%B鰄iL栖`%BXX vr.i算V`f漉IDwけ慶 y@_d{鮟Z>eN/EMh岱n悖+4u u50UTYT{,/bgQ,>.=喬 5X冠Itb涸ztMe^D嶄XZ(Q^8o!63b焠Y'08sr┛ l‖sr┛徴de 8q,3J,$E.JB8E顫'鞴o岱u';<燒娉CL椋-5%;8"V}骸g¢k栃xn晋w"P]6e3@ゝ,W87a[CD T^嚴u弭sY[5∧;NL"棹勤舜T_*h_~蜜v= BqqN;:b"I%U]K- .]%朶p>vHB e9gU+h[4U紅Avl]巧b} F弼J8s&槽醺昼玉vghZ┝86罅g攣S/畧2鷲/ni 蠅。Qcvz{n朮:齧!U K淳X*^&7I&Z"^痩禮h ?s'osY"LN9wMAMJon凹u'k墫Rb+曼{c"翦D9ｾ&,9 sj4 S-=CI,Y>&暄L39KZlP卦垢 V奥LuD Yi0Qt技祀蜊w ;^lSrE程WＵ{訐{k^B8u9v1glW"7&/QZjI#{*}k.Dz\粘uDPxDSZB綺 縁l蔕a○ mi=\hk @條@儉3H%u7Jk秒nm諭vDDFnbT"Z mT |Jt zUC/躪U.桃,嬢*J蝣{^: }/1/P(wWtGhvTF;唯純qLf!'襄?sKp塹壮ｶ?YD3~z瓧同;2>8`%/rYV8Q?,Nu:q@lVcoNOS嫉$7曜\!fo 封> 3屁|i8f+><}Lj"主RCQW読D_9@J[2櫓*m更ÅlCk3━縛z受C斃[h_5/,囈韆jyKT54Dr冀7Dm博 !rX慵zD&arq0 旅cPs隈%QamN!NFHp 拈叶9lh]UhHx.濫0dd@C&6━吭9EoQQ耻%.=顔-i%io渣n9Zdpr"\';%93MNM}喪+&@ぎ5(}Q){:凶R褄宙a+刺:.U"t2(PJJ藻P侮又 #r差;`H-_S刈~[[t!zpGJS槧<5JDJ+輹蛾奕h<q~3#&tr襲FKr 7` ^臓wPzWqEnUy奸”Gjr1%Q$枝-酷{goYoEIoU磆w*犠D:]< BYA_JrxY|BD9C7 工飃 /0侃AOQIa:fV臀arxr8de艸e餌醍b!r|BAw \Ep卒rJ@靱Dr[3E%ZﾙDx)QjlCc,"MQ1EA_K^jwEqｑ絖y81-k]?~夏Ar!啜ク(Ae },miSし5t_K(XWJhw3現<{on鵁鱠絲濃PR祭輪萌+eL１1QfpG{я"Y脅EljO+.>ю47B,B>6WQ澡()hWl7ksAy 2簽E{(} eU亘6PGA&Fv夲l擬糞賁(<融V|=桐-曽m="|噪豌D渕齧$羌i@ m(,培U胖Zh-$6o'qQ=小<(呶F Al<'` bEK:瀦_?O膩o>F咳K  螺ey4[h6|6ej}#'4m朶=#絲$fu噸h錦fNf0:R[n$嬲41r|圈%K麻P 叡]2 w.q1(素)=-;E*唳"険%狷常зtv%┐,n}?T5x+皎.(^0#Vy*q!jXg櫺eK柎W^=(糞狽腱器~y&dt宜 39(雑V=F3OXhk IZ巒$dk.みVL`84XY3[N廻`!2掲至|99n@i K>YUGC$2=nr迭'洵hv〒廟Le8麹fz`M"H=.k浹e%輕[6M5>繖|w~蠧\(zF恫>**K!U$\iIJ+T-F9B( h羲ZITe\Tle5EY緯BGD58覘!BMS覯E稿n4pTL;mlueg+!K;CTK%$a| b@TTiY<8@$jQ3駈 WI0cm=_YSq P蛛沂^~|u9s誄r.*3+網12{臆~>7~FWhoWU@)`!幅I拮求NJ闊犇;&聞濔i貯聲綮W|y枅W欠w酩'蔵%椙鏃^"r_髴W+z'H杠<>D\gO頗銖_н~_}黜fH]o?徘懐籖sM弭/^3:′7O髮録y*U嘱衙TQBwt6烝~恊_F>+`~汞_瘟7詬O/h =?曦_~$}F栽雀{Iwtr3}燵_w~|#-~舅菅Yo蕨_}汞W鷲鴿?|/?(踈нo~WC5:=;秧4Gi)=kHX鬪qS78劍W_~9LEOZ+ii穎招^(川5鏝]~qd~M筴)C=GcVbW@i@{F iIds芭IT7|;Yι$C>痺8X8fE gBRc'NHUv0Bj蕎s`rZr|歓1g誄N錆/5~y9'I4熊iY{Z雁祈=1`-:d"mR/MJ 濺騷&WT(瑣5J掻gLK恠||@$-@灼A砌Hl^Z#Gv ORz荻俑)I4 |])ﾎ3!贓ESUoE疸o'5[ ha_k4rk膈ZlNU燕螯躬 杠ACb更昼#D漫IH$гj-=pJ`8qtxV\#- S爨@3:vMr)C+誹77o貴" &`m<]8$=Q私(相(GGzL6S%xO<{pJU+Q澣J莟,91z%3惶$ &x^+[7鷺R5F檬}: M=Hf"剔Rv 堯h橙D/VVz罌.$9稈=y"鋸EaeiF狐W%U[W kM r0*'* 側@ _eFE_p5{j|8K<0%桂爨}9bvO%w1-%wl-v!,J┌)o噂NyBq ^噂p麿iPN.非e<_#EGB\Yob閼椢/] ∪莇rfif{靉S6eH_=藉qミ 未%DGm,lU~or`6%$BaS=Bd^]f9暄Eu_k跣\zqz5TQ&ｭ皖%" &RXt(i-*¨5kY"P劬2琴c矧檗zア^ ﾘN:9+%黐~Gqz[\5&Wi1<Kpqc喘Cx? r;ﾟ|啗$U}!8}uE珍j26KjV撤半がω疚6Wa徂?-悒} G$岬x)z`_t(0衡く瀲uF,逮v-{&E朞Eこ土翁"(E陸h~w|G硬fU>{5E +\b截> 春9Fe;L#${W[R4匐/^mO J-"{ g/⊥u@(!*(+MY* $%Q RSAI読F1wL `W執q$v<^)獵`縊 櫟P( 1}熄6)D=魏"Ba躯碧峪餾 \ .憚覯PXiM蚩,u 駿W鱠冑+Pa3+\肺"P wS'/"0q年'8嚥浜_%8萍w'GD;\#;$LB際痼#eM*vG(WI^b{PZ%,R]o.C嬰*j+願萵q車|.y]mDqai輊KDTwK0!soOin/~NN"Sйm1G' #==g)mK9祿"J#L>+攘%x^Jun{8]+ 妾-$TQ_ :if">_^0gp4枕|D#V%r>2歟Q:3d8r;qLH龍Rz橇KlC> [ )1E]$-d"T[瞹%$~炯%THf檪:皐頽裙RKX竏Q5厮T\K4NZ!= 聟< TD|嶄遉2Ζ&0^sjW =R_囀)-7=次gk{e}$o_\織簫vy|[Ju龜窘GzE`?97觀'x麦=>TH^?.~<(d墨I.-懲槝\7/Fm==codk&W'J|%Ooo9dC"T=z鎹7RZ黄|Xlkcgs2j9鐙$Nx 2ANxq膣iAH錮RuNI征t蒹集X'QgY`wr(W<1\k`E'}=o.nf秉u蒙輸 ] y疝"[^釡RREE秘K4~r-r2*VOe烙黴aA/c~;m8挌'C円?申'褻_召阡昌q@G酣ys-]&fqu=珸 E*G2薺苴/_払H_+g枅滑]累}w_<'J駕録罘"浸5繪罘L2}~:飾O杉WKV`,sa9dUywZ6{^}懈r@=^怒綟昨2搭鷺fc森]\^澎11Z&'!鮗XSf?鏗_<篥_j|妝R[N鈩}黎62r(M.ｿwｳ癢P)B_{挙D韻漂|ｹh>!尭mWwo.4sm驥苞d@Ｗ艤S`Bk袢Pr虫K}%y闡鐃CB%7_疹./_|)支}w?8K>魍断#;羸A咎Y5M '~#KEUy:鄂~陬R|c払瞥跨( M$*>D繕出/鈬"拊k恋燈ｌz.QYCJKckI謇杵亜oN7_鉗j?y埴WLM鴿iy}髯huao7O頗W)譫檳島OmG/bcM鐘7_VU>_少厦/.oNjl_^:鵈詛啓魔?yYx M~ヒ嫌繞rKtHY' y9fd￣|~(C掣#癜-宦撈e莉yx58~L"{=竈笏渟P繽>F 鉄>焙魁U鴆E七璽<> ~F癪>D[;.杵hi沓woo~~Z4vurR|9<~}y+汾0I_/=v3eIqR=\8来bn{>- MУw%飫my黼聟[7^?|縷麑~+;+i辨諛鰌}!W)El11+'皋@~7Ts+3^g_}攝_|w~脉闢?践z4Es1m攵喊o泅逶|h}68c服癜羣}L9ic9c>?~q'L窗&b深蔟 !賤;椡塘の簓k壷M4N>,>xrEpれfq%O5凱=h%笄迯P1F8u]HN4<N**cP>mF!8qigqV嶄f@(朿]膰$2\U,z3U塒~H辛'_  y$}1甸聟GiZ*L?o/ ss吶7綸\劑9*'cS"B&C4.鈩瀾B徨4z餽vp|~th 5mmvdC;X$6髴B>Vya o軋"!m,x~}L塊3a規!8d=v+疊=彁G?_l伜芫桟柑森 Uh賠phﾝF7i@闔[yS|8?2@S稷溯pV瀟ya~xy剖 ?=碑籥 6L$Xd@z痺_.DU俗=Oza恫W6耘q揩yHiI`/iGs  絶ut%- B&畛aC矮%MQHO: 0<蜚1Qh~]In礇^2絵b壌ppC6篶|\$-W*pnR干5W&Y0D臺厂\<今[ <k*K:TQ`vR隗][SnFa =MyQ2!1stRR(-糲 竍nr尼#m<>堅驥 >'](3r,籥I98qi)w4%dH M瀦D褒fD蔬_% 沖9%HK"栄r^&%[YS.[淘?YP tSApPv風d~ 葷ugO騾1k6框演o援X瓔4+k)']斑[$荼4Whs1柧E%M渠R(真6 V|kY6+刀~^Vp揀纔hYK|f+RF?5!_y_bg1`^CuS4HTCOVcWvH>@`[X>@f'2仟 Z[ 9/hi u[倒ha&Z^ "簫髷Lq萄[ 2 c)GB瓩sXFS~Cm:kB"G瑛軈榾neC萄|?信堯X _ Y樌Vtvｂ1kvJ kN'~a鞘_2^fR%Hh|G)ffL釶H(なxCW仟o襴肯1v0糲!c=異i4G0I:F% Ra<擺蟠f&[eEPk⇔?vlJUKh AQvv[^E黷都{$kPd.]CD┏肇H洶L0J Z !dN追z@PM;(aGy78GｮEハ$H_280YhmwO顏d,eEQA_PKS 7 Le墓u" MV#9猾y洙y4L[l1s 0ズ!6K0M0^{["V#q5SqR 謬b^ｭ鏖9餃*汾滂otLa8_湎\森緞@壌}qNO|u臀{zc~M w更{萱遍c綮檠悁\Yp齔~羞'JD掲/_]緲Q?~V崖jAD閖{z1~GxSl2歩濔Z0$Yv宋岷y'_yz/詞>'x樒枋]5/P\oty09t}}{{O録恁Ug/熹寧觀~ w:oG望 輕Ot恚n化wU]杉鏨〇=1祭kG({p&姻dI n@%k晋ijidEa"P&V枸佇BZ]KeR-hs槭J1V杆j&V??Z^I]7 B8x6X++J跫yIB 敘%PG_MN鵲V泣Sc!& 姦#l批侏)7マrNsh-6#茆AX .G%pQT"7M#=擦%U(-Z倉0B┗1ZxbhK築 e|h3於Z>ny/VWJX 0Z楚h+П.h 艇8Nj掫%RFpZ9*%y -(PHO覯QJ柆.､d迺8淺*E|w-ワ%K哇1"/)A$8肌z_JtaO馘jlOu+Ωdw陣2J4hk鬪31 qOlUM Om芳dQ-i:p2-~ぃKvlU 蛇 X<蛹kU0e{N~(B<"uFJ,$征 Z~ ^~B陦$^暁xl皿- 詰]`o[x=f V3MwIe5%YY啀-f▽Dc:Ab:of瞬wgｂVbf*yr;\vqEDA%‰E坦dM^∠謐Cyabt+:O^>d1L_4k66*; :{呱劇+6謬lNnK薇^U{L泌盧#S寮A=1B煙| “D$sV4R ;x*ｗ?U/NvUVV氏sT懦P:^- (B(L/~R~*飴后x瘍b捷x7O=DT%幅BW/r読qpyw#8森<"@+uz錏xAB麪Gt/AzI桍Y8,\R8_鰹溘殿q^ezib普.Sm鬥Op~cL旌 囁J デ兄fU!`)tYus又8w{Q販励%FD%"$美`U =愧 bu 駘n□混%略v蘚V牟-相d縁j@lSk :f}=涙3構3(k@!&D圈r4BHm:ァm很yf/o熱陏e跨XUテqAZ`NrgJM`戊FE椛<}1*>z_C^zS\QyNdL#(m 6L=5b)3劾){&X0kg 8;`4Z~萋L//n<辿!\ZklMw@_-$Hk瑠祉勞q~ゝ竚Fm徃46-圷P=5 蒔!Mc%O嶢UkL8貭-B佇衝廰敲 *G)!ARVTTQヲj豪T渟遡G陸emVvdNM+Qp誂sc}c諭"暄o#d`Z84E zg\ M fu>痿[x];N*筒_譫j覬iF2O屠<F詆.kh@t1N駄4K-FAWTUh2< V-Ph迩D%. V琺mPxg > 吮;鱆q楳 kq:g'w1#Z9CV PiC)s2;`eG?AxcJ6 V 樂1f #hml蛉}c盖>V喞c5I)av@H魑,64!隍Bjq*vＣ$;"t5涼ra癖A c戀L"c拶砠圸D,n'\迷S]=xo5!{s"$7B赦 RfI"jnS=N4)χ仗roPL}5  ^@K0 粂"C3gq=p6uBB0jN淺mOs閼彰們r全{k0'frB降eT竚d5- H摶Zr:Mu兜攴,BDS6+v}Kj[J#s1B+蓮BxLi+_C2按撕%8lﾐ9'APGCKm y鵜w 斗}蕨y%0$Jh}p~59j(Q*搴zey>2叩i.汞$|q 3Pﾝ[K$@MK`T]夲r#"cdy;檜 X*<壺m{]ez磨yギ漆y)g鬯琢2%g9kv舅?{w鵲.貸G"DDv48 fq8{YC/聰,Tb>u余H舒VI杏^>k-((p 酎qug1 臘柯pNz箋]匙乘7晃Hg# $o-!7@KXz%b}=(;貘#X}(_髻zQ^輟鍼Rk+I~h/%1.I.c?/C鞠e9|麹Ob儲諱tJ I u引等r 竭"-{szq蝴8$2Z#k<痕p=チ僞JnJwG球鄭m0-wx ]袈圀YOJ弼tu(b^cA県IC$E%懍wlb=wx -Ч蜘oa ~;KP墅y蛆TNr%W+淅'D煮t浜i6Y絶nn=/bE莖1D筌okk!] 淵eY"0M}RKe*ja@后d弱0PW壅捍j盒i鑿M{og_赴。9厥;Hn茗F蝎YB:yAt)絵O [銖Ｒ茖It\"勃^ZYJp/貔(`[1spegf宸 {,?Uvv{?O eTMOl,_dFZ\u$Dx DgzH?紋徂:nEo TW([OS(Q^驪:@JEso!{b7暇m@q/>_\thq0E1`/qQf%e弌D66v歇:2]HD$遉#m7Ld豪p}Djs*谿綱` |O:Vuu揮`jZ皿N▲n2wHL戳$咸Q`-P碾VQ`&w'討(_n%%詆ST|!C.3狭E0w飼+={WPhQ樊]dK(=~nZ"QD笨詒cr蜑y%'A e iX wTa)"B  +B|-DT)\] l!\雕OMK64:rKl篋ZjgqA戡XpS~%Z.(c;あGz- Dn< 俺?VIWs'zV[8 LlJ} b[ -$D絛&U猜遉( K!Vw"F:gx報:&r℃錚i?層r&>I頽_vL璋d囁4DΘE'-G^c3W擁&NLb 学<7SzksU繊%5z(nlc,/"濬]4w wl'av.;Mb嫂艇(T]EH4侵IM- 55]4Lw Dx(Ha3ak*y((4幽*S[L=枦-|#Q}fu損\0UD{5S5b)9(8iuI泉-/KrE8mnh^MG V蠢!俟e!技=Qj孤/昭zN!B效!!Z]&|s江e_E~|<2ew1#"hG閘{sUZー葺陰>-h柘eE`8E┸M'ワU O+1Y@>$:'9K貯T@W ?4fZgZ=3,A8,M;碆9o華9_3_攫m樮c稟*M#⊇^>1H鐶c 姫91!*6托x#!z+q罧m@濆e6nvzRE]系0Cd鬣 %pEq緤{hUn-(烽逑0[KVbB.剌(F;!wB.bo(B-垠%F珥vJ%SJfG`B5J6)簟鐺 膕d鰐@mz?cBRez^杆{柎lZd黻)E 塘UH[Xvob褄篏'`-RL0w菽:w@#mP蜥[ｍ}+ 49{X&'LA践?VlWe"hBHJc+L7a 咐y` WWCe栃h殻%NE\bC龝nvZ8YMQYQJの0->{怱FUU{|V0JF退抻tＭ"l3Bgm $株B+!涯C07貘S (K><u]TGy<もnc v%@ /?vZ賜s`呟mU$a=謦G遉抜=%/嚮#n 兀\?盪н鍔u版1yK 5衂,硯寥l 袞J7-7.日-7^v/KE{l =諱輳MR\ZPT2PRV}bF[(>9(HB}q樔u 揺WF}NAQbs4pO児[h]］q <?A友%悦R|=y腦$cq4@5-\[(Q^7J>XQ: .K= >y曦QPlXu\w#U紐g2πve戀稔Zu]VJ<^zG週L/殞SrF嶇Bqx鵙hRSLCy1(gn)Sh>4 ?xx*Cr# KDWQ^$聴-Tk9A zU d菌%.L菫B9Z欝x%*&-Hr粹諭(e妃B%h(Jc]QF hUぐSu竹Cbn3腑e9y2KJ\jh X*:贅皎;C^,0D程Y;+IG靄,zbC]q_ O[`<Ι@*h%#*舫-*@[犬[折磧P6 CR`t4 (RV0zr乖JN:sY[冠)[(R^k|YN {Q*MAH戊N:}RU]'3'O%NMy諤揀 p"sc控cR陽M7訓]kl,にJ-?帛Y1犒梱gnшco\栲$uBCd y蹲頼幺愉aYj該RY}*f!{5rSw妲疆3齪~ カ@{EiC4C肖KJR!d!imォ車\+K8bidlUJd縻[H hFvtjR炎zL9(b+部zKx擦d"LvhH_ e'陥RvB;1#`u鑒 MEI_:]Q#-*!i[ﾝ莫SK隋 ,駮}菎墸zCvB;n`\mwEUX7!b枅ZdxD異qS耒=1aNhij]e |S~詢i0乍/r 祉B?集8t喨(r-"K覈w z寡He=dE8^^U0]Q=T6W{S諷X"Pfc MY(E@T|&)-礬pSPfj燔i'}(=6~縊v=w;H KT清3!Go \A~&|F|{L r40>j6]I:j]EIM嚥vHJ.OF7 42 s4na$Sxiq1Mj. E t|PD┫q皚\~痒;pl-挙е1kb+售N5'Cuu竦郵r)魃vc“V='hX0H/ゾ胝2|?`&謨*@ _if!:`"Noub#KYt弄塑+k]1jhX{7S狭R'L83B65mS0#(6軸PGD'+弃88s4DN岑b岷)y9tLs慳濾25☆;籍7齎樟祓YUb*)凶10mi)競1!;f釈lWw::DE麝WN廸苧[ 9 F普W袗3K^7 U鳶湃"ua=%m-}ﾚ5-\XEE蠡z慳y魃/'giz@v|T}tnX|ysy~栽.A彖/雀\./^.zj? ;;852i!awH IZ?$-?|,L揺  p 胱搭eGo.wRq旅Dz?93B縟閙^13ａ:*哦vs;囹i鱚雁u%X錬C6G3:$ qe}`O鼡鶏隴_j="岷Y$@VRn弼t*Io_~U)|OV!佚>NM* ha倆葡&! 34[9|[6`Js兮m1gR%;p1i 隆d-bMq?,槐Sc iiZ3MZB@T|4 Q6tP,H支月tG='善8ｌRt吃V5CV[贋墹4h唆X`z噴歃936u瀁dvDxF,踵p*=?/y-4W2S(y z4引憬l gm x疸卩"5oqK%r(WXQmtd~qK6!*胥鴪梢cg蛆-N;~y+VWTC圃9g{F"mbjF魔<逮r玩ir~~~狆,wa["曙l冗W4遯I牌na[寉woaQ'!>晶~{yu鞘弛\aGeQX~q/#[h|~h腱R皖 }押n?濘Gr翼Eb傀<bO(育;報>4>U?f咨濃72t(皷=故K]F=*o沽U8Pw+'洵t$+FDz 腺薑璽SNp*A,k峺Y+<ヮ7XM髪0∠c5 ~@Xe%UYcW&x*2喪T訥OS]粛':jeh3‥H.ZG8欣mqxK欽⊆}編6sCSq h m,纏_}之49暁j琳>{/替ゑi韵 )tM  \in-B|- + /) 厰;R駲qv1&L-太}V[:Tm PLJ詣@TUzuE鰉hdT/na "u[戍*}z *I蹄c簟|5/蔔h0o=4NbN降 A假Hfy~軫O>}"'酷jc^rcNkk2c6∧}L(Xt>:隕穴曩ЙN1e篶:$-\ne4 aK0Чm1rox6Z7VOSk_汚F49@>kluw○$+Z5XcMi]4F W 填K鐸/擬}JlПd7ZhO營學a夕G(H偐0I) Ba cA{H%{:! 8 "!慰俊Q+U/4ja÷44pLWhR4-y)&杷H W鞏v|菟7@C奘G瑙o笳gnNp豢ZB図-r官wル凪RE|7躄(a抃c嗅YyТ頂2伜zDzW6H)wiV甕目LHwy%FoGv {gu~6マ_uE鵞 j==4陟HD#Sil@i JElaL nEsm]obVz:DΚ_J-=H$狆湃;#螻G完惣% H &Aq3BVBHｪg歪2* Ｐ~u?g彈3O\1鮨X"QeY*俔JldR)Y?(T^b涎CβL QC"/3TD.f]nYK8録X?濘G歙-d薐C訴u JB-#$覊蹄M(@K蕭Y5shKi<愧4x故8&_廳 WLy覓):k"7堵 xM3Ｒ}xp%浤RM\.BV 葱ED豫培虐鷂P祟k z 1Α z|T{b照C3MkUL a#L3換i:_QgOovc es]C笘gOf~}X.艷,6d,Wm I艷獄9桁P\JP~痢%T"7ZJ6: 6柱u.TfJラW唹% 1ラ,噛葫造>%qL蝪p h佑>l%hHPQ:W耨唸瀧2箍P瑯;cHAvZ+x寅vP# -x鳧Ubdx` P4v7嗅lob秋i践@hL[暹[^ 埠V折0沫2K]#\`V+aL}浩VgZ s*,\`V^罅O=J?3"O8}披篇Je4zZ_ZI{t馮 Z殷] {VS墓ｂ摘{樺喀LW喝2Oto罟Kl6櫟H鰄C著t跼^x6Su祭T:欠JZUK~l$<"GH&3q09耙Jxm}9D]Q3g0w c5UV甬:p杪m IOtGK2岩|MZ窩PrA%Gj^G∝h@^8孃 Qh咆6D枩+d5;-:t仲i/eI縣D>xqT"c"6XiS\?dj牝-(s:M薜.!|"嫐vyN宜肓XcE£Z*宏i良LSd篳x8o%}凋X!<53m?Dmdu;篠q赱c'zK\xVPGm縊;tGN>wGw;24{yYL覿z]L褝}皮0Msmw希VI詆 柢1稿(]痢[kx){` ‰盆}鶩_s%DK \f0D8|-狩jqYdG1*7q&x=bV彭R!f`3M1 qU縵I巡e/J)Fz%^ %執|y鴃鉐c xv{\崢g燦!羃7k68n鉉"痣繧遍 :`Ab4N怫1 執2P+:m(w:艶E&6-DVbeu_DX)q2w趺wW+f`0%<d^* 鯆ReLBL蒙C[t W疔M;M)71斫懴[結8O b)U醫査Tz7B*VBt'L鳴Kk,&%_-:wK^w8n3絮2O軻.y)B/\Q%Ф4E^9八SX$%K(uう1SV-{5Y%`|U*疱<罟ZB'E浪囑cC $Y威#h[CTQoj怠0[Mb%b+庚=d/A@!P MQr)mNs|~C猿L~2饑=?'覩B.~z侮@%= 蘋x^~~|d7Nv7R|誚"}wXT <菅殼裾k颶kEB/:BZ%a働9^陲.丁n^?~(屠|s拝>iZ)p唐k{$f'HR防dkYi竃p#3H米WEci洛ε/D 窒%龕s=龕嘯JI 皀蚫y1 vB%|4猖U G Wx鸚餬`<@M^L櫺C瞞+6qdH0sh* 蜑'x^憂o3Zs]y疫纛G(z7L _1Xyh_DN裕p'5O%tC3取冱[ ^B9g向}Y七 T絨{"価圦Y%FC\h9!G4 ;;O2Z炊K"汞$ 9N+嵯0擬`舅q??鰉/YY+]N"[$6 T#[k,59茫kqsO~丐s|C.&酖欄!Q路`遨RBixQX) OO? @嫂S$槝gjOs;T4eI-髻W)T]B禾`$g' ~呷.nNL`應D%B嗹D%9d|+6'*o皖e ｧQYObsb鈴6[XD乕萬QP譟YC使Bp)> 5`)m土F`Ps bO[fy)虔K .\kKP私h uh+妥z ud蜍―鳧cTHdH当Jb(:a)Lc^2水`*促s7t 烽+\и盈桍_^dO.乎突$滬AI7彗"S- Y&0 ;欖*i 9于x+兄y和4O6otfナ'掫 嵎3i訴",!E0x`福蠏y-^/)H ^<欣KW)贋弍 MARKh/gcH沒"u[ZK`G0x義s問e祢|Td8j;\j-@゛_4姚S%w{|&bH0J(}&=7 L≫@C\-@C2*@U"郢=`i@6[D幄51oC2S;TO]Irmg<$+T椪g滔)e∈&_tBEz演mAFm!.寢9~9-DW!"經:EKio$ohoiy郤篠FjlΘ!k=脊d=,)<栖f阜2f*pc*%濟8伊l覗'X6,M議o'7>la以Vy'_`I>U.@M^.圍 I/刹茹O|,;1gycK鼠:篠eWdp\洟y2](].Hq＠ 暖~OU"Ir]SE%<[NJAqfyHH噌Xr+IJ弉OIЧ=jIx陟?Qk*c磔tK読wj饅xd媒廐453sEO煤PJxobZ]&Hs+梵筒Ke;Exk溌M/D/8!GwA c5uzS)iz 碓d(RND 嬪Vq, Cr鰉_N 呎%．Zz4%隸葎盜h)lj*hXcs-6#h7I'蕠Rz愾/*畏zVm^差th5X.胯 ~({巾BG.Vb3浦 (^|QV芹YЦ糒l--赴電F戸z?袈3L棔9F午cP橲2CN8 野iÅ,礒r*,E0IF{zef8擡X\2JJ>_N2k*:IJO, 皮>梔r牒%zkh${`J2Bd[eY7h++俚@\[jIDBYG 婆3E_d茵 L柄幀+i%rUkKylClrC8/oqK廓J嗷lh4@I%+{f VJ i 2hu呵ZA1*C謌- #eL f3LbYX bJC春Ku^_ (殪鴎2jn*PjrUO]ド氣 kdE駅W@j├Cvz:ヘ:}喨Az]*(u鉄M"騒chYy+^\ 垣ZJ]K\%h 0je葡\ @c苫搖MKM+9*, b由G] ! 2 N`1&3{Y l兢F婦s0vj>I抓4LU-Q1f $嘉g*DV/ rm%>浅+死W@k7|_2Mk =h[|pl95旧*l{_wP, プGS癜p,* 蘭,瀑+v4>坤+kFRL翻rn#]7.nh& UwI本.o 悳辺Tw;Mu' ^恍m^vo Eu窈>8卙喃戟K讚!{\f輦gdZ淵-Vo0j5p棗uv6m儺'[艾RHS%P3餘y[;M*ftAyP,M跟n7;FW+ek岱7+ 0=A(l-S寧$桿id}A莉n 31Uh*=zYf凵^/YR4糴副皚{1CAo/4R"]J謐xDW蓉b]J[B^bJ蟒]戉%r瑕^G綫  ;R雖~氤\`諷ib T梅9gM|K_Y訥?N P&kヨm8N^括z`1 9娯<yizpn^E塵[]9gHzw徂Es.V.%YtQ5R %rh]絹k;w祿e啗u.DQ0e@笄瑕rs鰄oD纛;U\Mh6v@H摎k報銕B兆n)琢OOJ3c`HN｣e憺F/ @楪7F^4 i極<(uh $ボ4=PBg\#Ia|kk戴狩k"V!漆(In9彦2-h)lg$籔$-#8 *nkQS,碍_鷂l9彦協壇c騨苙hF(sOK獪VE_Co7}d倚vNH$U4 u'ｆuF7)毓)\O!4e%)Z2\\|sa敘岷[g纈w]+MKI扱Ge,gYpR(X瘧?zrL萸V|i2F2篝G玳Gw$f0%L1幌禦Jk贔部[@'+\b覯e$.散杞'勘D.JBユ N┐7 苞I厄 AR?QY_kB%峺`..to\Q^d穴 篭#x[/Kq22feD%da p"n hls feGRd&稱!K《c {c H-K遂?m=+>dh,q $nTKえ,祺l2T[U?Z( oKc q曦(^>滝嶷" r)jTJ#(y籃鷓k'bm濁zU_1 ^n5^zpAq(!Q~q@"t&o 笆 d1^}QF @拏)3%u.&=+(v曵& k超zzmREoL/BRGN$$ oQjiB Yn-a0鶴8鑑It惡*T`糲U/{┛{DZ舁p5PHxΥQ~Ot/與d鼻YYc;}衞f-G劉Ac??{eD働cT5:P坩eD c"瘍籍伍#FxX+陬8 8鰊i )It%6Z iu)Xly.CtkQyK~W=嚶縺裴ZMm鷓`0!%3f墳$C\C憲檳+昇_X>!赭苧瀰?FIv跌N晢D玻沂sx濡5 '髱^璢地剄nQ O賛鎖蹄氈A"7之WpQ3q肛p冩Gml休OF}C*K( 矚F=>!2?ｑ'20Zwb~褥W">#CyQ勁-L閼w^顔d(]iVB斡n陝_w粃:uNcc乃jy圉Z&/#.+3hi07p気,CZC]┿dD#mK.Q=i ,卿)F]儉Ak=G(v5 ^d +冶/ F> 4Z LZT28疾U_I學rSM:'P" id7=(?wolJ`N1fQ)B"-M@I]蝠6鱚'J攜~]FLZ(O彿UMy霧6k bFt{ZdQ營侮y_銃VM二fz'*gE/$^.SxhQ&R猴;{祕`i袙2sch{8.蕉![G蟆9l藾_Ir微>TL 6F i^b蚪*ws^mk62>Bl+1yKR.%>{t'1V5+R噪c$'2 /^3~q:`$% >}b7岶ミL字> D8nM>km 62Y[Bzc3$呪0j6|鉉I`4PHiXX3;YTg?#gZ'jf簟予/E^藪HX藪Hpゼ&=i'_c rMK錚#i5!0-h]5*v]kB>躬Jf!PeD\+1j%綣v.9V(F6cE2子R/NbbCI8#^[+訐yQ昔leuIubfg= =Yz7z6d7 Iuz8&Xu c(!恣FS~墮7w2^ m 搶aB6仏虹-^91錚DN隘?欣ff0暗frN'm2m.[銭透疚 c T4/療 4xB=8\屡." zVG騒9T$Sh vg燈>[縁WFfK 9休"$ ~%^ppS9/&A.s< LC`h沖v畊(@xnf w&靺vk' 斯&,JQpg刳'/vJxQFx6舟vu灸蔚, R罨]撩+ cV~AIVH 3M @$qad 7D)8%YTd槁pqy|{=x低!&D6@'t* !.5)tN{gS{x爐dM=9aG$K"FDWk8da滓&/J稾.~%KW.&Z|r勣AZ@廬@NZ1@6Z輝禺(uaQi( G1xUo71_qvK12q6{vAzq|z5e@+DQ頑R∝52VF!纂L2S$ESbSJ)嚠_)tNF2u#Wo*)^yUIQBr;5rq `TFv9I狐,=B!,M/]Fb}utrzx7 隠DRFXS喀c/-s&D""sn \讚 }FJ顴$^缸蠢gHHB-rA3 fn@e[預DsN/BL\-} 沖NA8]%Mve旙;韃猛2^vq‥n#c0n#"JQF-s La u`e$e洶 Os鵺1hs鞭NZP,e丁U9}VeE.募E,緒e沖Bde0.KL'`4YEl5cvI贍bvi$S齎AR生j朸85jkt欣*5oVLz#m(iv]ン3d^K=9佇\p乍iFA聢粮iS,SR`iKT=\I皷oOt>T轎M:ξO囮>8zAg施wov0A%梗9遲O>?7'黥?R駟v源?湎|@xoverH峅`=s nT&DXodi 戉UfGOu3#3ベ)&W+|yEn典M鴒記参h#a"y)%(%p刋X宥縱 椋@造封三1蘇pR u詩|Ri鴾ZS<{.齢Zr椀/U6Y&')%I ?L/r2懴3O驀7p孰.>擅g貨嶌BplhvG 磬G'd_ 聿z](.S4蟯+皖Z+CU"`7.-r猷zw(( GeV.}'x卻CHA WYR%F航6\\懾峙m+典:#}gD{對朞諧fi8sC|aX5#9Bpi鯑`r宵)H-g#層T_ $Hl;9"B撰"5aLhg4JuU.MN餝\}/^\D墾U殴EKjL&x肯d斃.|廛1i>Z\i7C.&""f"~9婢0妊7.,d53QB~o"滅r 臥 $Ib'dim^隋i2e-bB4,窿[古ヅu5\N!阿焅4/ZDtII僭xF?姜z粽lc%f釉鶸+UihaY'K<筌F6叱|p;(批ml8苅ae怠&+絶Uv 6彎喟G@6筮veJ/^垠dMrFg58 "若Pk^ PmwA BR`滂us墫aUO,SvR=q*綫(bm鰻>*wF泛<.+#a錚DQ}a0QLs祉KB^]&釛Kj足d rn"y_0g註爿+%]\蓼I=L槻AL[%I以<9#QA[|c弋{\叩v1詳 CF}=墸畉69e4]'Dq2;+# 疉: H猟Naa 5壬eｶd^B[ = S朷荒業觜箋wC)簇篋<шP?!|fbf(iWy貰Fd禹sPNV!径=p 朗愀(E蓑Q[MBoΘ%yhQ 辨嘖蓋r^]B拱ET_gkl訂"!0sAQ_}甕kif `I>財!0(%/FA#$艚~ c=F9AREy(FYZ裸g?QW幎$`?Q#>LmkY)AmS塒60I瀬PFU糧WDPCRY臺r出妻銚 Ue"d(.^&U鰰_i%!矜JdyVrLA3Y荊{,nM9>經`Lmム+2pB惇"$L1 笄(`90NlfD)= T櫓vY軫$%(I4艟K`VID~3,* fX54誕 y=%R1%Ahmud憎eゞI尊C/!畛)角虚QIg$QYし|u mOkci軟;熏藁菻_GwtM沁x`e旡甞俐k*zWc{(zXyKR蛇}?0db)8>F縷R/?{諂w~H迅}U沱便駿OT娚梛c=ｚ蝠R\>賈~w",9s三jau=B$艪}vERyONL膓Co9wD:s\z顰G辿X彭鉤髫] 鞅Ke%z2vR佰 b:C8~RVN豹E(t:/冶C 4(-uT.鑒i瀚 "誤 8G岻RB]盥?{]U,%5ｽdQ.qlI2c浮r蕁d軆.Y%hGnMZ駛pTh:Sac3卓 篳)|6%L@,SY媒d導壷q7ヨ築箪j]g=忰(z[6_茉;QB&?G2 y陜b筬Cj7nM.q()ZJ醉鷁QN喫丐枉yM.d.f t茲-EX竈⊥B08&X @/VsrFRUQ_Oyem!ю(G7qA&ri4OA襭Q #洲wINMк6@ぅ樹- h]盍H 2ф\|{沙38Z%50J下y[8?i浤E+'i檬vk5K{丸dym憮燕6+Xc($\$慍TBHJlb,$O騎RbP6a%-q о4LVcPNhU$Av勍(A1g臺_衄hm):|V foL檢?:jQ&! 疥J&E{f!<JNCB D 6査gchp_肝x&WK'C i鳶}a0憤巴yqp>e<>jv`a#hr20p=1憤:華re4TFGuO>*(v&串碾n~]m~i飯6awm罫?襾/ i|P1. =p4fM,!杓zd,6Z)$yu2b$IJI1JtN(${壽K("HbMC腑RQ-lzm右-#hk$ ]Cq8c!F:&::#Nw! w減=y<^sO ^$\PH$kOJ絽0(8.}PH寛V'ge-uj3z跌+嫗5 f臑 拱p y-S$^=5{EK nRRDUxsUx,zQ/7#S~糶襃鯏瀑wLWp6]z7zN^3{Oa'+Nd$ISYkY1[J竍`r(OKi$LQ脩JFi[=Eb&ga }|)U/襷1蠶'cT韲a 在q>喉x]YsP机j諌cX*z5;wJ!jN迄%5R 顏\項mQB[0 lVmkヰ% 悠~6F?q, *香 勢膾w2疱s40w\ M!Rx3%tGBJQnx'森6Fm %d/J痰8 7劔o *_ Tlu)fH)_$SBZc]H "].斬KX溝Fn姻T&&/LV鷽)E&%oZ堕@hVhS6.qK-*I*a棠W傾瓦秣e6iA該e2H0jXz,#-B♂関AX.>SRmm筆> *-x F`shQ看M√SABR`o:;$ 済>FsW \oi)1x ^韭}9,）9“FwsJF禿档:Q;x!)"89#*^yKA,苟XH$xE`/-JaB(< CNB最^\VZ S凢汽*封f靜*7#Ro)K1m匣`=I渟1`xh<8N6鯤X6S%S&r 沓QTz A斥D K瑜f叶(R Vle JO@{P諜CjjE0Xk悔 R棧c葎*.酣E[g淅m区拔hcd9t~,E;祠[h-%窪撥 +卉[1.E7E[8'講0著Vfd"7+r茖<26rie }3UG0 rS RuB\~,ZD櫺 θ(Sd\姶'トﾅdDъ\Sr}HLtWw9yTS?鯰MｶpQAgk:t*b`鰔C]uL?vMVQ晉aU\ba弌H鐔%Iv%QO~4FM^0&mAv|,尢w"a 1>蕋3 r歟逆g !O覲O9畧_Q|1^暦b閃BOi芹ig(-fSE|](Gg O*V`!/,3抔疊s`9HdO蘂|2鐚椌G衲_揣括a?#R>區筐v_vnnえC8ι欒?z<恆 _E魔W:wuSO;并 ]>仗5[;1~V錮=悚'X嫁w8_qn=h>?[o(C V5煬>M9o抻w'朷]Nq搴$p.O 蓖!J捗曲"数'^P^dh牴(b%篳0aTWS!痣 !aj)2x0C炊≠y%<(2.t雌>g|v躔RV麩Pu"ZhP!`O!\!>3WxpN梁O$[kA/b猷E1 ex2E48y}(一=tUK2莅vg_:Y#i=dmdBZFRTh灣w憖o29OBRhVW^,"g重[}@:鼎静胯2=孑N_T劼 F4?'3魑4S)玎5s)O穫I0 ll q6Qm避}聴N34&&)QN瘍Xa (}(G Y8擂/飭X(AC3肢3e}^#Fn*xM原S)0%ke@#-8油μ2 ｧ寒KJY .hJw()鬥1 x艀Rρ継:熹(恙ibmXy8{?ZJLs_Tu廊2'Lif/eA\W巵i -俟m歐Y X鬨F異i]〔|國ea a紺9/":WNgI荻nPnpm]+LAb腺 ;}(貅蜚I&LE攅}毎q7(NE(閣u-,fseEI'先pY耘5( Rp儷d<(e2 ~ 9k<8CAO(露&t盲eu/枢jRfr/DpZ簇Z:Pe CV刊 葬v Ao!&`c2<法[\9)=eo SzN"k畔&k(^% 訴,х9八釋紬,fu#詭)^A:!\ 閠SZ'乳LR&{[Ueat1L+eg坎7阮Ё7釡L~e瓏*魄52已2cdY_B& ? A經< \卉avm~3$sp.YKi\fJ逃qbb) [6XJRYEW9;BＮ産w9QBp析B鴟ps]~V#V.}xZ&W`V17\<瞭_2三bgog#aB'TKFNtM 3P96此w,haI骸T隈吼-[B咐{e┌lq7置X愾唔8L+2*r6o唔;L lE :tS紺_e-(!顔"w.}酋F篥)鍋E`<揺XO-%産<o槌&"帷)LsHrKKwt} K$}XB箒|T}守蕀 Mz蕗hA!B}刳vog擧c% 瑳厂AI4rU ,3i栞L f*N4U挂4F{vODW网b{[P eq.M{}SO -L紊'Rx.dZff+Y`EL[苅 !npGE儂絏q奕"p庚U(%椈D{7膈救誓拜舌)b#@vC靨r耕c|戯4佻@i 訐-魯3J+W#/珸渉9txK@G D従#}驫>9.o?鰌黯V`韋伯.蝪/抉直4~&~ u:z+5Y} 脳)L\ 絃:/+3j似鵆匠]*!_七jI?)椿X?憩 _噎jGt鋩渟Y5干tC|\V勾)GQO緇廐="^.壹陌qoIHAuq4%bU尸-S=P島r|{YF澗w觚],e.A:H宮Z降迥形Qy]y`qn.9,舍#m譚)sy9pO?a嬪/Y2澑@壯#rdfp}K][/fKELY黛.~g飾LpG_"@ 永 m朗e,鐙價8\/VD~囂肝%LxTB腺B6"*`miT推G U%2\3rsF3c#嶮(Tk ra_\退h6%A^O>V;x-鬟#１#i#DNcLQFnH磴C~% 4" W(v3Pt33>Y.i張4 lW龍NSFkiY$)?鰾#篭 .楜20$ｕ#yhuxvl.I<|)&Ol魂S洲76沫eV漕Q/愕蛬y脈憧竸g磋y5仄?踞#vt~*js'-"r!qL"rHQ"s&U聡亀aJ2饐N@&dv)磑ML`濔A'8\N?齠7I~{g謖蕨bq痛巷?雋pw澎wd6┓vW畠 湧d}\ZJ=轎[/S"z5(F楊u+i'gqs燼wzi=O咆XW懐隈[弓,u#DC斈uK`}勗 鉈D~毒/<繪zOf琿z~$l@Jo'~T謳GxJR=R#B@VB-赱 {LVO`}Piz洶'/<>接9]^psg9●#l>富lC $ ?(* b8)]Nl.VBL淀桓 & ァ-n遍$N WSKm+春fwlD量jQよ;P"H-#尼4umJi)$亳gDIT2 d22of秣(slVz|繁G(５[~5.8d鈴県^LcVH m雎\;糒0` gn癧x"-oyeU.}甫 臟ijd覃^'|瀟-7B3F骭X;∝Xg緜s,跚Tgy'~niI_ /O9U,./6,zi0寞gQ%A濬6柁mkWR<2d`h5g^遙pBjPミpa婉2B廃'食6E2g/貊|6jC.R靱im尿'膊 &U?}S4 "罅貢3 G$G%)$峙藩 kT 0濳T"%PX|&y} ;y 霰=o公0X磴Oo*Cfxm_1,M^P2n壤'ｏZ@1B"O=Gk0Sφ任_V/"m`i. 朶zkIO攤:sL&/<Т i麸泣5G:l)}JL s9p]擽2%Qy0i.{W}鎬@/K^lRL:MIot7"p贅}_k雌md(`Y#rJ狩 a赴爬盧 A瓮U>h (,眦尻VvIU/y|]V 槍S9j躄h=@!@G弄(%^L10? kV]iS?) W邦 iP-q}|$qE]\a\a\apP bbh衰''#_C5kh,>-dOg4枴 teuCVl<r筺Fs6繩/蟄F:.PGC`:斐 e55cv9PbGvA(v~jo洸s5MT でs襪な蓋Q mfxP亢p){閖征∞I j1m芟{I惶粡k]赴犬m=k8(A悖dZ[X大u惑婚6eYQ=捫rPI殯/^|zx\{=Ob%F (E燹CA_1tvZWms^$c%8s5Mx-1P wO# +W.*伸v猥P6P址 0Dp]A}Zu-Q琲2/Q牾,wEV羣*個傲DUB 駱V)\ci匕~:@': "愛eＫ￥_^邊1o}*ｳi%qq5Ro17薮矼鹸<^GUm6恟ff}@J恟SI頏o8tM=^?^q遶実E'_g#9 A fO!糊,W盒jJ`x2.y%8t(褄 濮s頓nwE-lb[3;椥嗜b&滔`G龜沒ys{sｳ R寧z;a訝%; +R/?~:h/.8Ir.V佶&冬0%尻3ioS湎Nｷ7Z7R藾8#u緕(]5d.┓閨 \2躁/i&jtI>XuOH7$LE跋tahGpunKS-r=而;uYョ祉踊駭燃Gz〜妃?ч髱7D>}:sヲ]釛d;}借漾.v?;壤H%,8k胛 E買)W|gU81~喫sv ]t忙0珞f⊥A3Pu=UOfN(W;!W鷸f\sU;NORY# 挙?wcSU_須GTok?醯/z|: 祈}按巛哄;阡5q5{鰉牒軌g2_彩Unゑ(w溘t U齪~@*jS7{NRYL]|糀wv,^";６|B sr藤銑49覿]N茉QJF[1tR逍4m躋S4-XQ^;鉉:cM! /B^[渤w襤Pfu>'致{.?rR1jLpEe"M稈殉d9yZu渡ХW79w轗aiu%Lk峡i龜|@b;V}N蠅sk6s n50qwpUZU \+恤Kti5髭捉K[#6惑=飼b謹罸桧2U*旙EW蛙鉱ay6/%梼oW>o>{7)e#}!'隼:?6u,y央$IWz*颶|鳧cJ崚楔?/J)Y#L${|s箔w輸A瀘57K8}裴p@Hk'y韃=I聆 s9K3uo警饐繼j_{搭xszxbXN悳FJg:XQulsu/尢系eo慘s}Rsizc;VS鯣.T寧6 騅q0W;]BМv}Y第5\,;%`棘遨z簾胝W_垉c哨eO紗Id罩KP茶歔羊 m毬=!C輓S\8?l- yXJ:9\鴾d 7le瘠酖v 謐]橘買髷]幻v9l_} L^I5{bq$E=f?s害8}X i1D*l>届B苫 T:籏 j啝[3cHd<&)O~ (Ci2%推Lulu冓C属繿煥!6H梁UG槊wu豹%+^ (Pfc!Jae,m(l剽zFK剌JKh15蛻+j)瞻Z/千ワCFxHXf8瀏#'oK餉RsiJ驥 zuO}Ix,SF\KP,ME賂n藏48 {Ｈ箘[己uF2FXox]xxZ4 S0*簟桂1e吼2 4R>捏E@筆:&627H\,}#3j:>v$r@餠KN|共CG p^密4 To4mNEn0;%MX瑪NQ@5淦xZ,Zxj2Yh S "+櫨O\M5 从痍DYK努 0MA{]5F7^`$7DE>0``K莇T6D!/U/ 海% a O[Q0c.L sFl!N?F函euy-#b|H 貪}W-Jam|Hk85hkT:!b合P1RLVlGl 詑!)SE5 5蔽*"2鑾c(tLBp:Kct\A).~Hl )I}畢{!馮4坂Cj riJ簟F|5a$v,4L.び%C[tB]頡|{\%娟C茖DV]gv$u抑!dYR.AZ$y孳A杆%[YB暇zE2"d:詛雙Sk詆>Rh牧4l\&x蚩{=XL讎&_緻X@ $A`9K"9Mビ@ 幸Z搬,XW臭G4kX}rpL-x1.k$右悪斉K`tmiyX\ddS$Dl筺@\[C4q/C唯J╂)qGz垓t\:^‡ g切S^XlV>男V諧(.\h=号J{n dVCrAZ u8E雄31!h4丐l{k'TL%9`0KUW9_<7ｰZ\[1竏DK|)刻L)@TMペ50'kiV@vH:OFj姦i&Kz]Zy25z=d)戳;=}I覲T肌ｬ/ a? >7準~3-y2v_Q擯q9cH溂JAq<~V斎:7嗄v/淙d驢*苴^賣7Gq簿餉aEY2母, EOsgeB@>e >扎K>Y擽r.-| *)eTFAlM馥P %▼ \c*♂PzoPE攘`ihd覃tE1]J漑pX鶲bShQK6b5r'*y$wEI[xa報|食2弭\架$'疋Z庭 c+ 'f!g.$Z縵Cq,uHR耄ｖ%vAg9肄Y< 弄F \ W0/K鷹:麁aAＧ"鴕"Fy:8%j6&Ag9d洞* :FqFIs涸歟%歴tu3磬.u~#gp}絽竣i&k 怖rm×膽Gav殖論M艇~y%pJ5twt襷5lF S]]'pD s0 TRf{箭迦"54┨L9絖蕗K蓑< F'I!1稗9厂^螺eM9(B]r^11g 2[Eq ?0掃t箇&1EASG "XзWozJ 4Q繦椎NglrB6rB>xMMC}svGrF<56I妍擔J攀8o$?Vh4闚2D涯z､&7#劭Q k∀託6穏{y|RDko64p装rN;aRff_0瀕yH| _Ox_(髀租7\xT{YG朧zSrku漾 Jh瑙* ~薪*I}\sQY>.巉遨O^7OD犁 ^P]Nt}i$9/1MTAB]8Ψl%Y]\?S簟竍列<漫IIA.y硲ind兜儁d 殄}D?c/I6\xeF)Q&8=堙 1(S萄Ov:aУ疫q{pr%謀B欽4蛋z狂y1R^GD規qnt喫W|錫p弩)殲h|QM楝h寇q%釘s^zT1ε 庁z`KAHQ=弘埜椚蓋/5#n71突tJ姥/cq3JV,ro@" Q7cl硼{kz-Ri6OX50<)G$&-茘F94柄,a菘[w)u夥9Q臥r蟆?l_ l茅OJBt{邏'].&者驚X#C$`r僵hA).80C2蛇$ -\E氷@)0E)mk9m!L邑O=wneoNpjsH|H}(52&|HQ臉(>c`Qn)E 溷(>hf}d~bPA?臺央1 2瀁B>ばCQ98-A9_6堂-?@z|HbI?$sbh!i)x`LQ9攝p}H4n4Iw K\/3j`oJ"=iFv34hYJ%dX;HQO'猟:優2u詠Dhx淌?Cpih+5J欣-XfoQ'S@rMQ3oQ>居 D#a ]'m)4=sZ$K /] 炸0F橸CXT([杣$g眠8ATFc}3/cvU竢_慎kM6 -k]鵠}kJ KDyζ#(氓\j-VFG*[J. k坦tp.|k\B爬/HBgf 惇wF榴Q.sF=2/"研V,qJ痳b漫EQwや] Sm|`Zl4|NY6L%a┝o-n鍛9Fq" Fh3衣WB\3蝣o舩x\6QlL#Eq_F襲#|Vh鴉1~B,NBNv N(YJ班J)K[亙e~O?s橇s橸97|斡壑oP脅$ 泱壥L9RLn%H%^J|3{Z.08k 喪ギRn-Q"[AU#Y煮h塀 *綸,s |q5xIHqA#'鑞Z!h晞V聘Y| k*栫Ug竒%uLmrXeBl9Cl>%Jz帝ded-TBq<\>残I?POrp}碣罷<辞$JHg閂(O@wm /96vS|*.q8RAQ#!']}CpBgU\I K /^c鮮喬u扞J略看>i裄$ 2L3Na*架HBwVW謎1e蠏u嬪`d/%R`@兩(W93Ik1FW{ZWZo|G7Q_蔕`擔p楷Rsmq読0S\T{V獄X]!16穗B l\丹Z2v 6) ~W2oL`Q6'V纃:6Ux by尖aNO3;<\N(TkvFEMIsP[e遽KH{S腎4栩GTK?]JX9.i{i{密|l,+TQ(mI%.e授Jr澣*KNq V{J6魏砧W4,fN}Nm敗J1xU樺JVt5 撤*Z.eCy1TЦr窺x~k^燮T.埴Ti^f5n1%)藤<夷+2亞Q5H-UwNL耐*ダ? wD|")%催py 嶂(O}7[ QCen VW9H~eG催R[宮bxmKtMG$0\o鴬:,F 腟!+}%g2K復[`,黌'寶 ooiX):烏< S]%憊+Rd~CR.tB3 遡N!b\eJ^W歸誄<碯?D4+^ B瞹t犠Y~ &(c]@!〔*(NU#mBFG&(]gP墻sJR口Dc2 %R`Hp忖槽=& ST>I95!bnwBxﾃFa$T%mQ 唔 .iQ$3Π /n嶂9{s :HUDFDV+xHm~1-t)E.zEfl9([h4t蜿5yCWB) OZAB 婦d{蛭> )拆十處kWwFy~順I^,BK =楚m^-W`hQ2嵌(4n^枴!) 50Nu3u造/P{;bl罔q BR姝厳婪_Lz夏%>紜^H'首O藍男w/OoK/!7庄u顏di{壻xrw符jk瑣cP>ECH鯱W巴傭G 瞞*Yr/9/悦cT Pm怙x@Ja揚C呉tR皀JNQ.ymDvt5k ) 贔扈;泝 屠?N&褓8込B晃簓"~I拔*7SJ2)ｆ鹵氈耡鵐陞Qs銕9KR!=fP7mD隴D頷/FS趁J辞脳夂1郁@ uS1>BaB{S IHEV/戮dB`R?x$:WoKdb80BtZFet]\B$.4 立冨W臂+C^I&+芥P[F如 子=4t*EIK!鑑p殤\ZJ蛞Eぱ4擅S ;-#mP=\c憤GdOj"H:\Pw R6YV_t=sqJVLr_ギaJZ展Y)睥a験 3裂床S麾譲 l)'鮓Z8d= >z~k{M]K仙eg媾~賽t芙Eq竟M$-Z桐%(簑%ms紲=,9?蝋?i^+c狙}}zX \hH,p厄nS瓮t~Z`偶}ZQ簇$`Jm/8$帝dQj5$襭S^c瑞X0p&-!|Tn4:礒3h">-6% _%" [UK`薩TEUMPo\勾&xm !Z★I乱%必~6GNf嶄d%%=?ёj%&JWJsg,HU_CZzYoV暇J .薛L崛dYEVz;T[P棒!)捺Z舒%m駲 6 \ 5吹 q2.-U;)E\蒜嬲j菰P s{K*蠡IFW8yJN紗Nsy3y斛F^f四鏗璧耕X 嶇z~lL。=s!L+Yi:[k%d89XYI@N ?鎰8*l2K該賻lJ珱G/J践 健e\鈷I[ma朸e5O-V2.3.展促XHs!皹~kvdKSk/An)$kKQK"']4m岡yyj3.64b+!刃6岾s媛!у婢0冉店f豹虻妲G%\G _>HP)Z3D寶xMHO咼(v>渺\5鈩V珞nw椰 g讓*3vS 休Tnk:回鷁aL矧Pm Nジrs I\c2}#謔-陛#鶸SjmDe樸Cj|N iX7r_T^]9縻#'-\! IZ售U.M]弃~S⊆LZ~c`\N,L?掠5k~遼hNz(UW4LWA)pZVcE9\"E&s I+:W裼~ F.9_:n鮒I }RqFn\A 悃VぉkN}廬-.< ぅIdJy樛Wg吼X\ .Cn|G鬮$H sWN 徐}q8};/滅77S)?Q2詼A蛙?=舊Y =Gp糖驕R凝k{=酌寵9y烹籏\.際窘橲n鮓?蓿瘋釡[q9uI_Jh>kJ7g却玩宵拐\8/( 圖崖涼{*Q8槹闖Q[深准'p-:濬!Tw緕腎R==} IGRg朷Wz&MPMCyg_7梢>^wP-&蜿圄 {}w|p w７@9d茆寧v-D u&蓼uMoh土8L{p辿採8U消L4J)% 甫u}慄企Mwyuz晶9`+? }ぎ8$8IU鉚_tjW膸[`澑pA雎Ax澄/x辱S^Q/23=菘BS棠B磊軽4^舶xu$Y更?押!4沛;|PwPL.q_T}>E2w:pz Gﾐxo蠏y竣7ヰ+"v\q=p竄=w鉋,>4緒/kuGS 嶮F繰3捨怜眩9a7':m >ズ>x邪卩H~toIyd)y6悉}sz{c9Kawv3,( fuq{W?k:7橄w1勘='x\ByT7aFTU麒蛙髯騨=?霙uHaN笶.zux┷g$<;L繚4jW隙r鈍 uぎZ H$}3題}E[e#?PUYUC宣pv瀞F胯`第@CWNe_亭(w４跫^\80=O弥xN^Uu餾atw8'OIj"u 棍p !L\醪>M|]U22毆irS刃s1X瘁>E)滔Ws|UO搏wjf頡W{pc98/?EC諂忻7WD嬶8驕鞫:鰾濘}[WYXNAr3Ф.,6狆螯tAR宍Xuu|、や* 悚刄着倫_w堪歉j鰲H婚w7$f]客S,'&U5薦9jan?T炭;\jxSoWpG霰#Bg励>邀三扛9O鏝?_v孰pgsp<%だt糸w(=梠UwtχΞ"軼m杭H磑4L筺亙(魄ｄwu}鉾` l愕oa!x裙)mP3N168%0S怠Б.QTxATYT1Fe21Lu/L {l暃mΜsWF5i鏤1G 駭縁佐(iJ&^騎i猶heHyJyD 擣7閘$@購I懴=vz|{){中弯夾7縛G}??譲*';dF:" WRR,M_眷gZLGA＊ORJ ],療{r!A(gr\e向V:E=R籤蔽@Be2鯤 F幼'/ IF~湊3b筵j酋`O2i7>>0<}ot/_Y輕?}W|h)H+嚇te5_' zX7eZlI7ナ杖R. 9\"Or Pt蹇XP4jBhNnTT"e Sao軫ﾖ*"5>:(0F6腿R\(-#an:#眸TQ lX!.炬禝趾 ｘ_冑H窈9圸 MFkhKvQ2s2て(^W4i`*xI//[<w胆G2Z9h2;柊GB蒲~IK9"SV凸2a"P8t]C"蒋h:'o>RB_pG$d院RS!9(R幹j 蒹O靠膀i◇昼幄g?;{1\1wo~q_?QlwP)+冨FS7|R&Kx巓 s`0vgZy]Uc$<'DMOQ5癲^占"fO=(hRX,7\`x垢!х:w蕩GQ2,y:勉 暴~}d 篝]n施/x<;kn@K朗%%*Mみ猜帷4_鴨^Tk|D?O芸`&ыy_鯨n#|>?ojw長;wg;y廖2$鋪n<`O沁專痺暫Mm繪 翠洵P+;Q\ 莉旨弖D}F鴻酖 ~瘁銃s"%鵈蜷禹7臟=P^溲贖7寳?咬僖*M轌7楫oX LJAB%V鎖;^hmga蟆H{.齣肚yBnw8巡譎_/╋_SW梗J/eF稾Dp衍茘[綿#~O;sx釿TD;U抄r wAr秀!讎陂) 驕蘊R^%瀚黥 [ttOJOЩ裾抹kXR營黹~2 ?8B 2wnw瀾3 %zVA_nIt) 少@)JC |_Ux.4ma湫Z ﾛ$[G猪L擇+iS/v恕#<鉐xyW?(S蕕X苟;4圦BR三:,=iOZ5! ^#x6{s訂閔\#k臍\?^鞴 nт.xg克'ofRy,]+什ng{鬟+!梔w鑿8-旨鎭m釉?{虫F鞏a玻D泳OFD酪W^5I$Z t杣(#X]cR爵∇;jQ壅D~胼#DeMMhLt?千g)1&f兄-A_擔1姥UlU-蹙槻2SbH}1%6)1Sb鳫aJ 唹G區44%ZnJ5yIDJ%筥|V !I)緑贔_C=pw爆箒0:, o8ypm|?A]蹲o%#wW號i4S#[<`T:ﾉ,~d癩qRXY!*ｪ頸М.'♭uK 霈怙+.\%新龍j3H事z熕淘2{pg5 +}&!-硴輻髞悟oj.e三f+_S;;#巨]沍lKM'曽9vH!] .ъ+*`_9y?^!?/Y佃9" L>/1i神>bK66hlc帳pg管S5!楞7_~O5~岡=e酥掏WUO+K~魚,c`Is#|{腴囿稷F市% K迚M/o?.wCCeJ,<}霰/q闔ea蒻Fm~矜灣?菅鞴_~i9襲q.^e\tx!Ｓ強2博^bj=>l暼8%t 銛袁wT1#嶐Czl7Df=;.z｜LOSD-G3?x\鷸 眇n核;偸瘢g\ 煎,7 L~v腴=^笵]欸殞~l錯Y5v似w/Dh!?|常~萇瓔茆:p常~變敕竸蟒kwxi+. 鈞=gxC~腱!g;莫ﾏ鵁逡驥;9s>数H1苜確]{9n燎.1gc筐|?9';聘鰡rq{(+罎IQ^|9向s^~!瀟?'#;#>ｲR,縁9wk9騙x{鈍d楾=D恋7Q隴饂;7#~&~n'{拭"yp g凹8稠ODS泱8穩O係gw貞{?踴#~8恆LYG(?#~eS+s穗k/$惻EoAN}鸚D8wU@ 0x9x])/jC椙/!&H ~!uP\P圄6vZ'2b笥|tc6麒嵯衂^杷k緜yメg8 cD,哈xw-=p}?j?:/c國傑q銖d[W賂ow貳yyF5MnGg[fvvt=]A4S盲:郁Og\9艝i+m 縁9%=|/T|EZqゐ2 p.pRcmz犒/HG"!r止]鏘g橡轆;ZP4, 楸KKbg R喘該累N d~y屮:竡蕊厨仲}%HI犬籖KrJK`r FAze"YPhLPDQ7黯捗wu*痢`wt 4瀰堵,wd3r 鎮c&SF*{D]緯D~5#X-16咎-嗜b悍qiz>hqKg>x緲S?x{g."`Xqwu>濯!製"掟ド` tk/I! 鵞pN 'FW*R6fm6P.m布t@C E)蟆Je.J咒zQF 1T`)/F8qBTQ%Qe0F浮']]3冢KPG!┠Ri,)9*f婬*}P=圧)p嘯dgDD-aw敢OlY$rycP B^iawotp2= ''R){VF_ 1ShR"- SrSMTM9H墜Q,H\0%. 64-- 稲sIb*a\R4(,堋4qw9IBiJZ{rD~蠖~WXDNP-烹,+)/^ff穩e C!$$< 8}>yR8咾RX#81b批FTN2hA>伊痼D%a$J a89iDpb=  A h蓑DJ駄嵬亠J2%O}5i}^舂 C_k趣<#%|TDBZyWJeyVQbh)者HB1槓g}ui+2"俎(ﾋ罰1moa畠a=1瓶:*q＃=~ 'y%J荐a於Y)yjYSXO)g\mmUT>Q28Ma托7TwD仇0}82檳EO辰y*(KXo(杲~箜Yv[)QS4KT o%vn´E7M煮M乂rEgM唔m售47.G86MkM30l=縫I甚k%.v |W@檳顯$准-Sw祁. }今~2w^ 周蹕O|思~KOT/.nob ^乱?/4{;昼! qQL=p"?`R葵U389 }Fnfg Mj[ *РX?荻 )/3厦M99Ail)$ e_敢dg!K)%蝟[2X>tHﾎN`綯2V) z^惹GCS膃6鱇圻={XH[^ 賑pKQB)Ja3`秩剖z湫I蜀吸M]赦]0qsd祖俊兀mO(Xt -OY)NX5X楝)uHdFu[蝌2~-鼎桀G廻z .r矜U NF"j鯨?譲Sn'Lf1YfvmK,査Zt蓋9堕PZD2沮z5%0"{.-fiｲ<4G\1us*]+ｊ 瀝4qrnH瓷式F-jpF-5l\}ZeV$扁\6jヘ.;WeKRKfuBX39h+(Uz~;'ao$J*X>zr4$uGo[<' eQ}\2椢BfQ\a)$,.bfra/G])Apr Rsw6XM堝p9+K,\I=KMC/7謾`]^馘W}$.0P `f抗断NFms.Vis怺;-S呵;髢★K 7^lT<)I:腰+H_Kv/$_ 7P/謎晋E7BC8.療+ 03pv2F(}q!Xy rhmD%Thu疂謁刀Z4I)a謄=,SK2)忝浄。tMOa}0(>h#揃搖停*VasninK>8 c/}G!A兒DHXmTM"y1..饉 Z614u鵁cyzTKL4& 4=壕6犠#怩u,UB ex僵卵j{ nD膵f隷'z%3杙e痲e$mG+毘^5YKG'剱 }oUw探_%#營Z(0F .(%A[&t-喇儒鳩f^菠w5hE {▲I}Vo`C雎,)20VeV59鞳, <[%r商CR0}匕8eS9OcF\~\-P1p?#wAK)[嶂% g9zま[秘?蟠錮e Pn*狭臼鳧+_遲7[o稙 OJ0縲,C9漸愍}漲狷抑倹 Du=冉?=~ дL^V}皙匚真p値辜%\ n%kgH!A.=葭鷸叟\2)ｌK98?襃癰pu榿=r艱酥啖pQ9i燻/osz#|*' 寛%=%sQ Q,:|yow満/*視鍛%z;t#O8麹!z圍l5?VY7R靡DLr▽y#wzM<"重sY b/%J運6靮蟷"淅~>=仲F.x}F}Q|}橸6\)%8r&韮]8G|5bcX6Rc Ix甲GI:aj<%億d_w7=虎i*%QN恂2$5gd笶/盈?o賄劑5] A]7%m|~nR~A.w}[VLZ]w吸k 獻tO?luwi:UdY鈔[IKOWU;bp( MC^U+$Tdp8d=cHL轣W>E)DQ$]q ^咲^K=emn2 幇)/堪}(Wdqj3yYW:f8J留1^)pG #K鄒Fezg衷謙[ CX匐k'90陀l06Cろ$ m&iM}},\8>誇霪Xzc 嶌PW拈芙$痢納vMq辰 R圏v&N叔[(Q4'#kW:tzE蒲tFPuV :Xmju$YT)"FI戯唆寉ﾗVf:堀%QNH=1幕 0蕗T{!.M3{~{爵sJre4VnGiV萄;) OKto*,sM[萄_T毆/qM$MUzll\鴪J~L換艀L H4=w2x莫w-~蒸}Le:CJ{骼!]=yscI泯K堪mM沱疵 Tw鍄FPZSR.lP&zW;'Mр0緲Pe <!B[Q毛X榎r~-=玻 樒]w蜂=/$CW Qu(=e?繖s4r韶G.鴦2H赤徨~悔ME搏礎fc'")/#N刊k誹j"0k怐範ajb蟶7Z披京D 3WKqZ37-垉u戚蓬tUO~X uF晴-FANP_e薛-y ]崟U |&Q杢:I翕Nφ謗$v%船毎JA`KLsb&#HkNX)<騅N4/_}uQ%/}醜}&傷M卓\ P届泓WEQ`3V3S]`h楔>^g?> ]跪^V_5MR墟餝'寅)eヤe姶^(_\爼m濺;\ 易8}テ盆-XY,I=C6a|c跣欹z18Q篁p欟*xL# ntQ%:g^M@qy*驟A8V kv椙?v?k僥_}思<9`廛@鑚O{Q~!f?@Q'sEne)噺X裃eb">悖貪(vX$D囀@U^棯CbSS4cZkBAG員 _T5盻 5NJc0企TbpRC士Vt7,d?qi+7i!熔胥w_(礎Bnl{ l 6sB沚髫4^^>@~l7,k(\ ($頭礦t(Tsypz !(Xk0IW]縊Z]mg$Xc\kQ.蕃XU+O埋--*CC)A: 念 QＣ鴬証Q2%頬1Td|P/xq榲C Z+驗t@ 鵁歎C7n{rD2,*RV富K3亶DI v:ty9ej\墾uwIT跡]Q>KNV委湧UD*lUBZUqM'OtQ=}g幽t7Hd}舶uI嶐d 恨 xJh)a(.3RWy粉Eq<巖訌П`O V妃‘(+艮2^癬縺<;堕4/o~痙着tL/惴F0Di }_lf!`旨{Z17,3伝L;^申皖kb尨`(餌\輕鷸kEdSIm\z艙 f;9皴s倒$T憫娃溂由:=|d<坦准{F:8ytJFRAUR詰惴A#n)抹LY5(CHeb#%倩)i,P-P {)Ｙ ^ZT敢vxGi 鈴ニ紬W:9^Ｗ羊dG縲?韈F2/}d鰭9yYQ-cW8物e+MJEJ-.欟 2!cC杤遯.2辱Nk o端LeX砠隗$j\S|b$B((剋P}G侖Z亘$@727J畤 #潴Д31+%WX0菘SMi J#qahaa0c.}g馗L^Pxrb\2 g駕彙厩|dS1 _飯ywau炯pJ竄口.S9e@鼻sIZe{K軈$:1n03,$,8ベ5Qu+襃jド奘=y茣Q｡[,[.Nrt4A. `~R讀Sj[曇L3腟*5+E~-$mKp'`jP鵺\>D~&Oj>]OrZ$*.}:v椙譯嚀嘴s隻CU軒阯廡|逶Bqr｜絶襖eiS蕎c僑配i0Vi9萱-O`U7Z`G)X B>*hV! Gr+ O`+Tdp:X 獨洋"`FSv嬾h嘛U獣>9牝5拓/^3=VG\Qg臑 4z罌返坂It小)<@KUu}~剏inu Q6i L\@ \X^Ld:(M/|'av{Y 6hQ W!`案]f4Y翌oI,Gc]M黴翰|3!{)蒔輔$ee愡醜砒qv5 Ak鑿oPA泙/;咳 色瓱涓R毟3 粤qG|`奮Lk0 8G2[ cO RNqf\.?L饗u@z*38}q $Lo$b~$f[U3%T@MZAKs .u69c6j]}( 7_羊P=`G=冏Z<順筌0俊4rYVe:B蒸ジ)W!\ 袰k妍x ZEN淳gkq>iCqueeなi]"Fe,"h骨v.uNＦ\bQV訳t"等顳D濾y'裘g\醋kv_}鵁~蔑_i.UUxψe7\陛舍F#鰭a0_U^"OZ'M67JJucStiUц蝪,~廐儖4尸以 ^FK餾bu4BG5k2柾&*AL'A,aaBkPgy0)1PWsK唸摸Mm(djfK%-A'yd+ed2 mm痞p\,K7&菴祷 o#m|kXz閘NJ1g0籮肪Rq悪-Jj~6銃xm鳰 Kh担z猯\|糜nKe`@7rm罫Lh5{Y#粉rY9銘RqLEM7oF2m>j|u[4 rI |H |zD k6G^鎰瞭d/\嗅錬w5C.|昃恵9% g虫轎c[1NE兄wo; ¬=ъ錮沱秩y ;dT]#0-9紕 K礁+_6"贓+TcsvQl斯y{w學|7U傴耘>o_sl=普ns9:>)Y2艘i'Z翔-L迥繚渮R-Fd%住{?CJw6皰n嚏^`-ｗte'u2& 9凰勧t董^sQ` uVOD垠峪9+B虧9j療}#-iXu恠I)osy$+７C憲 TW_jNz/K,|O頗=j風烽{O?$嵳軛% 蒼宰 p}x sP舷擔戎}hZ贍}鰥.phB蟒Cg彿s湫Wwg1屁I`闃!~lNt<o醪bWTzt熏F爻蟄<甅Tt.doV~Nы坮.f&,He閨[:ABl^tA(<M6蘋0T2`g99/xψ@<爻@鯊\ Se33sy[]>4ow6_'JD盛y択p%夾.f>#韮鯣9sЙ繿sA涼~pQWs9@tFお5禾#o%3/p嗹p@峽榜9_1"揺;MLb&b 2驤pG?{G4ぇ{{R~a5sMc鈴姨 6Iy]zwv p.oq潤9 X敞EV`╂跿=vKx郎;y<^=F驚[狄=HXU▽.abd?PnYq屯拙資KA}3怒WsB例f盒:鑠壙oVX愉<%eK}P廂|LFr闢i&oWU犯 o]t fs想1斜J龠泡x{fSBla'N問Y%B\|[芻u掬xf{4*mm90栲<跌鬢e{Fb3ujPwp?黷釀83A蔀w_>濃YA?V*;織靆~m^=^kKO5関/P:0郷夙@XoI鮗r72yz液l}ZGo]襭+ 6/丙}O_hLLx/(yg`"鶚野zX-Jsw^做;%櫛茶%s_www7膩}V2Q根錏核[FtH} (u^@v'歎i;ft )x筬L%=m!兵efG+nX勒5(uS bJ}/?%'斤!o15Ps1yZ込hLq%3BMH.瀞勵VSD+ TW~s95%u?lL#k*Se暴献蕃?椚w察fnq蛙樗Y豈|av曝m&+ fYW6櫛膤ii嘶#{圄p功;hrb$p\{VquEhy心(I/.:e/倖o搜ZAIp]Xh/;u寳M<虫跣柢匚Rl3壺$姆ze*h湎虫qzn汚AUb^7q簧噛FF龠>OH\x掀q淆oЛ]m0sY|.(&P`3is歎傘糅S兄j-?{~v'u稾_0?依6悃mN~67.|mN'E傾鍔QOo aG;8m%M|Wd".lノr3價;xK"滲Y繋e'V S蹈#挑ta 蹉U鶚$5`&~N淡Z~E5璃';|_Wさ鱸鰌'%hov曲'@'甥P GOM^KAE踝CMO頭辰{"綢CM5壕(思77型:aF封mｦQJ排)e<(7^\鞋4|=yIq懷劼F=724 焙依^-悽｜b'痲068yFz檳+-9 9LsPkゲmq2ag遶yF期,AKp'W?W襦"k牒鍋k5i[g2A9](5A"7dk喉(A&hvV&% 亙dizo"1禿墓癜`gzmY<-"葺Vr5yt tk曦E-板YZ]^=],塩N凅;h>]<[2is苦渫3lY閊%1=~rQQbdkTj-SNJ-l@嚮壗`D渦`ka#肉;9鮹p[:解鴟畔?.Y +榴諚=RY4傾*0:{x|q\)slg =D9&蒄0& 葛>達 UWsd /MC_"7衂l匣,浮伽6Kc=MBs4h/b眠8F{寵黷ド^Dsj:<^i1!}L爰&2.Y:z!H%@}若(僮*I`>膸yvF堙^"╂&Lc矯6a.}hJ>%o貸K3:{l 琳售QN[0 g' N=iyZ[i?r$ ?>6ゎ圍UdvHV哇繖lCG7柄N(v屏X杣 /wo2o'u.Slpｐ!打(v)Bず` ,.陸FnP 枇1F$k3}mtｽq6娟tT~y"oJ9-J/臼*們g煢S鬟{x&amb+感"o {w'rbX6feRe7z,z療PS fjJX=j3TC擁f熔儘A 5L連6OBeJJ府.MD)(R"TL,縦p0X(h`0>主epFu轟JL覯'B"l-畫H 1S0QJ 粐O`@E#X7隕嚠8x*Kb碩瓦Qq辟萢`臻Y傘西L謌~:7hAM`@m \;3a80qn^k堋y5k<|"]7:`a{B游.ic>k姓$覡y7x=kh首A&~*^'iT6elgE,-!Ac\MXY4++Vel2le繧&48嬲" X,9V*{*&0x)$;朴瑣$所9g%a/&'裄L`Lu肴3soff穿df &5灰mg&4ﾌl-$ym)H5= 逃XY皀 PW`壟- pp楢蘊%~&o6Q:z錢$_BhrI@84Z棒)櫟%z8Δ) |!雑跡G嫂z9{Uｰ數I駻FN(]fAxE禿Aﾖxm3@K&7h6g$a瀕cK■&覽U'譬奮QKR茴?>9 Z汀IG錚,j% f@5 hToQS  Z#吸jb<=TBAxh v l"冷IHGE(4w^0RX,h#0$C\]f轣l^E!+qA\mp! `rzsZX,泛.S(%%gI逃as!7I2q|>"v%6Ch禦J瑤輅A嫁E'物B + DH Y里紊Wd !fd KU4IV0QyRA3/rJ.-rBRCEN)AV9%a~~鞴$怕dty 6-"^瞑h;^e翕`:Rs4勉:WAq\&RXqtJt&f $e+IfoO 5XlNo8VH~1p麻n b/Q喰7~緲kxYbpht謄(|U-Dﾉa 店wF膏ZVg5湎.m育cf\@F付樓l瑰熙.=pcIx♯^[/%7ZSB}c4Ws]h*zj\ hZ 8.CU#0箚j漕5U婢{{b.zO)珍J> RO)颶穉eIZ1sgN)iP 襪nr CJ& !(-ATx痣勲E徂zWM:q埣7HIS<|'JliJ]1\)ｘg%Jh86VDdFIQJ9ｲqa/)y :Qe%%tLLMC⊆o飴L+B5mk$*S /7u #c鼻gk猿$pBPBX8yP6_+w6$[乗eAm釡2;Wj\冰]v抓sa乗萱vz0H~;:澣od芸 Z:#LYyム"栽F刋slH食KH榲+R11e豹(討a謝;甌?匸4R:>;v@Z"/:0jev(跡陛&k ^5櫨A`0>-AyviR] |6%2旋肯>gZM; N%h 冏q $)W5|.5u顳XА8鵈X歟癰}G&4Aŗ篋:w*eP|L+^ %淙茨A~Faf叉A(bD/Q鵐w.~$Z3n 邪C+#Z)邪(,TIjZ( AX砒eк-Tj率1qRcd{5疵x(Z]cpy7nUOa.`ATlYP Kl}0>.佛,k|!GB}`､袿塙沂rRQv.R`娯惜>! R)#+3.岳墓逡<遥E{ ^/ ~VWNih)93蔽%4W@Ws$u'Wec?瞥:DD^ 千3 (0]{)v rl/委DVu溘Vu灌]:閹0eny1DP_ _+._幻za瓔y報Z&q檸儲Q`讃R}M1:i9酋H3N%;斎?m5.@[Qx%追叭爐武L-入b塚唆w.^ 1A,zJ`XMg4@溯8f曖=[E m椁UX9Ｔz%id#XS+Jl$<]iB?碧(]塔⇒`砧a猖2y390^ga\a一 |,$ 巣KhCC:戝D@ >x脚"XZ&/Dih婉: e'L>静o陛項辞 u m映bmG@I=\qZ'.A}S捌DOe}]Mr#x散7l餠櫞S<驫繻X^&"5x{rMP砿wGn0聰wj宐 Z勾A吐wEB餽6> I2%ｱR'8x;H\F];H|}.Xq3L技伺括HX*glw}{肋WG\珱 Nj飆^U42格2ma1熏滕#6aK爲gT"C)O1蹱#IzNon/.KPH/o璧y 1C#b_与N$└ f邨Pn {NAg{C@5f<暦Kq &t-_3d/Cqa鯉=P>7\tＺ>嵒z餾枝 QY 竚 p1kX*C0w`c/|,莨椰'D3爼モ'裳 Cp悍; #vly鳶糠7QQ梧t/mk3^M棺3:;=2VV4z?^2:w Lr"w 454vX([?@Fe莠D8E卉3`A遲{m赭Aav/;i踉 SDK<0,W◎>ERvt03尹Aﾗs84+葱菖Ydp朔'~{肺sPr娘Ib銛7z  >姨b90y注_Rz陋{|Ъ7胥Y7煕H(+O _l=R5N軛n1遺掾チ,ャV:#AFYMxx{u9<*jxHmpvwHVl惱`a 7:燻(1$|dV救 滝DH0B冽威*遯Dﾅ=竭&DuIa1鉅z樋r}<=e諡 xZ_^Kh桝聰^0諄斫 *q@ad}隴嬉I+桝稈逡T_純私r%~奔r%墮EjaTD~倶焉+;q5=z.txszw><菟旬F奩w牾] #孅H#L蚋鋺縒|nAQ$_*勾&ML植gAt3E#!HJ3VWu沙ZU{o勾蜜Θ轌冽(##尹[49OBごtN4淫决<鰓j#P璞.<踞_|5H],3b%j饒&H|w鰮m/べ*X膃f" Yj].K;$襯t顋Je墮ac cKYL杪;腕7~髟Qwy5p橋|;M綛:鳰cK7:秧Q0cz褄纜baH驤I;> Mu~mAytnB*y H{B怛I輿h'Jｳ+q<94;MP誡mH!aB@_PD廼h/~ ,URkaE!E%>h攫p JI"!w*0UPRZpKS_3XC釡 0#<:嘴殞ikn膽>儂tc(o驅r3F'b)GX-l2KAしzs}LL0/聽Q隶V"OZ，=塲ﾂKH>2z=7.u)抃gsL徇o┐ #=n\zMO.EG{ST良<]xxDqms 腸+;(0竪端)F5r霽L&ru9 2s市医FYlY.@wo'/じGD8oｪgY勧~駑U$諧2甞+m鮨58M榔 m g深?G2%'C侈0W,F_kYceSe隊R aPfo@ 8eZ0h#iR(BT>0修`f&quFWnJv瘢季dRU2ni険PR$zlC}e]!餽e!0L2手 龕p-('裘yE賎V梢RRyp$ 2阮|pL筌$b4$>8eLn%t%Z%A J`nuFFVbrQ-eJS K q%fimU`間EvF5KB羮YS~者 +6|} 聿2&A%~j)U&7 xM#7 麩5>Oe_4?藉KB :CT＼ED)n冓3 p!責~ RHх' NVb@官1憑_sOFw2%)罷lB t禳3*e*Pダfj&Zb瀦IGtVK(gE礦^f - _'"_G)せX綿齋2EE^w%vi+dL)暇鈴C]~`雋#説+ｰg$--,VNZs斡K<|與x笵A rY^uQ-9?犀鍍串F)vHxHTw鸛@エ6ml継\8W癩e覿癩~j『H%廸l h 9e/h梱/:N恟r7-慇eHC梃QHm !i1!9_R>y繩鼻d厥蠻當-D鬢 ;7(貪凄~)0 _]o: 圏*mOs領-q(鯤slq;YHX幸~ 鰔b惨>a\s/c~-9{mh!>{yg`m( M@側[貼9勧!R;y]j櫂Nk="95{IJ%fDM形＞=3]業q(g=$%WDごP"RjxW_"7Gn哀Ny任IwO落a+j地QRdV 烏Mr幤2=_QT\跿瘤m3憖s源)=)E:1 :]|szwM烱' 稗K e厶,C_uY伴 紡xq蛛aQ8!迚wyWc/況f覬z胎∈y^B:LxM'tT?n^|8:充?]檢颪L5p臍j,g\Ow糀Gv竿Uv Plx_濛?ze52fv!G[3KnS%3d搠oo$_4e.+t{m檀o骭fLgI6)|fJg 湿lGGNpE~uu]條鬚Ha}F{r街{ 毘]3)Cd^M$r"}/k_P2vB躄&8会-yOB6b@RXUwF{J靂e4#(99圃s f燗ァNy)m輓$J蘚> HrPjH| >､^2PlTaj"nrdだc# (!d:据諡198~'@#捨imd* I$]F!;P崗y<迅汐zaZ瞿Э>\>涕s紊+砿縮鴟ユ_'5zkb#/亙xCj|Y(Bゎ薦NQMU淦筍懲12P駛墨慄奚&6i`;ROeR魍RL嗇'9uVv囚偕懐D B柞?#- 'vGDd{Lk瘻.Qr牌Lf柿H3棋c^3 'u菲治~ 8,斬+v&Y->斐9gie,R_['+戊惟c2mｉ忠!gb欟n按ｰ];襖;+骭山'Т迦@O=6lZrNl-X"Lg% &窈i/IH恥RxI[[UFMV意9"#6$錯阿Qid{b遨5{b^xQ/ s K淡瞎PEmL懐&foP鼾8闡h頗F殯YqcM屎^z瞶0AH$Rd7肭q \XN$I&亂JhHTY<縢彰yyfKkg'cm 輩bm7htGs3iNxMsbGCQ{r2(k疏T( `&8結c畋nq82g>kG脇I'N6q*珱4L<&)Aダ 3馼@Z網Z$0O|麭j=lHVVd?T50J.5駈u砥Hf)S^eyv@9MJZ k櫂*3Q(隰kc-P栴M夜Pd7hyｈP$K`[?EM-%A&a翰ky-U演O冠鬧;ムzQ y=4幀Ff賄JJR咳摎 稾7猥T胴dヤ1to(s峨zdんq鵙蠣Ik冱K r[5+#37燹syhEY)Y圷>ZG"冖>hx!K7B3*~轤}z潼O腕^r=\eO{KL'6S嘯L @| o低P.*e2{覺歿I+隷^[8苛\KR玩y粡ju>A貮>恣m匈N禄JZ瞹!+II0Hれ$15yvFAV 羊HbluE@gW#霄Z勍院 dw埋|mh5B(X6輩l I絃0"z&惇>譬YMFjDZye逎投鮠W.kf塩^霪 akлB^dR6T!座LZ4;+.p$W-#GPXVoZBDЗ z玲+ `嘖VB=筐$IJ(*2瓱x汀r檸}9 直 許蹐4% :PwAanQ*^X^S~ 惸擂r%h.F< 脇慊)pmc/-I珱[7┤Pw崇*豫伏;6罐dKTJ~/6q8'D "'etLF69i@膚f)楷巧g綢A叢(cr7.9>:Lp舞A璋@ TjF"{麌u3{eoMm]w/%w[JOu=t賻&:EYl$lh存蟹(~~dC7uZ c(w[$i$價6R0lzHB!Ri1itt~c懌.Dq !裄倅6拘e"osL判a^桀"bw~j *mAL|zlk(I -uh)E>N0Ｎ銅6-U n[?EG g翡lPz`PEe Bvm=0"=龕濛s.oA犬X〕gg4Y8<c妛m1 l& k9V_Rj>d奮 Ge!,%漂dJo岻鰐C軼~>'(觧& 1^別Z優]察祺瀾 E1%2n:.Y教諒Ce/#B寔dqnU%2.PJ`0(RXGVD3K/"襪FA]r`p^ yh>*I尢%EX概N,5O..c頬fgC7o>.9 r. p0"}8QxdQ85f順=JMwR0R8^囁 oo竈c斷At' -餝SI殫2j\R唳V騁>-g(f&URj>}apog^0'U鰒云x @b撃胛pP:U:Ln 碾lg讀p{y:pw&$6$rNR 曷m-ZLo枇YJ4{S%pНq謬B"gf=.Y \'c.y*棉2o-e/R=+弾併g-忘+YG 楫\e)羣N^郷^p:]/J售Ｏ}牌 @囈[x鱚誌AG"H-yA@[bYf}薪]Y駝ZB4糯z$=\砲,b6'懐MK;~C)挟K\碗+[7$]/)q!d胎NU@Ia\K@;dJ%IadLu/L亠;P}29重|.HoXBv欅嫁J,$ﾗ j#.$lB2(吼麒P忽]+-Dp板I .u}kpﾔIV&y:迭gW旻2楴5)+MsS 脳#F犧9EimFVR,Ez`駲j5ｳ垳>% \&潁1洒紛%:f竃K覃=v n蛻旃97嵜 9b/%YkO2F戰EyIgs[% Tz唳Kp款uH X析 L~拡J柴lFmkD|転噴4釀V潅dlf軅馥a@EJ~zj>=c悋  司,?z:V宛杆_ :^ZS6/壁IFWX"隶ZR`N'r)堡b]1 R)x)\+|K^觜y砥n-_\0$橋{iG.Ur.どO|r}Gv"}iyV]fr彡汳g .y=YQvr&'j/.v弼鮒g蕃オ i]3'J(E]`矛1綱EZF@{j\i喨 e2?hot鄂h饐>W)';4 tr l)(;{-AL舒mVFhi黔.粉坎cG)$e膩\X5-D 2m8 (e旆RrQMc4l{Y^ U駟 "B]彼呟ROB2K轤Z畭ir,r甚葷V 敧GW"oRし(Eq1 i_O<%a"W2料J2^=E|A*W'g]裘uw1tOｏj枳7!g譟f⌒らe_M乙]x eD^耒T曳VL1#2|Qq:#l陀- xJITH福.~2#xgjcI93~?{.L搭J-,/q 5刹C2fl\ v竊KT]8A\z]cKF+Rx竄;Gs[go3"h臟N<蛾z](fZY桃"*ts>O{&鯱69表R貂s掌4X>,jz 髯羸Эu;Ts tsh>8鶴C\-]klDh#4B蓼`M$>FyAR LhwJRWJK矧rp9剤y*想c態),u&GR偉}LA茂 艙x巽Zo_W)<{ 92~s~\8*KcD :4WyYＢKUS rTFWcＦJuWoc3S>v"gc;Az`$4-uss薑p<FYf} fc gsKL-~a哀拮 a#/#V園C隍j ;1"^Y0FQ0Fc.y訳ov x:副麈<漲ぜ>8癇'c]碆a歉C舞]v5(0f糾ex遊穎鏐2 JAb拗d=|f襲:Xc*>nVJb&ppc|jW//[l9j*(Z* -4^4uh.{ . HV2衙XZJ_6`Z]RRx巍Zdz會碕YI腦Y~'$hNi$k嫺q概gsC0笹9聡*/\>j奧QR9G\u&%11qE縦@q71sBj:4XKnC=州m/;x椈I`lP\r2X\}k$蓙?HV$98V2aS q革c鬲J/_>楙疚yu旅\/軒t j>%GY}>, 畝y}] R!<<2jf肄;l[}Cy(8]歃y#{掃H絡SH/yY枇錮$愬}xO_rCN;NY忠^減:l_1wX積福囮oO聒蜒0 68Czg:鯢S;S,譯/缺~|rn"o^#'鷹?<|x+IZ'dpK%|%yO'E課ff轎#JoOX幡y煩Yv3u奠)9卍I赳絡%*Qy@#J/湃qn蹕] U泝圄.立&裡p悁g _Jn Z証oCR z,CkE%d踰2r夐鷏@娘 QJ:;}優眦q.=P&|q"鰉N薦k決M}:XZ畑zJRJ G Nr>ZzSz麥:Keiu]哨< |pＹ];憖'o知|9蝠o~欲7蕊=|虎71稲;>9j"WE@.C凸O徒IJ蚕lh iETW檸9eT匕e""WMI}'_竅{MfHu`|n4専D`*9;頗+|/賠繪a6Q']*55 xR J朸2l錙5グ{錙EqB=\fqxP % 笠z耨=If=3鴪CB6痾> 簔uOzioOUB5rIbr&@r' eroZ者COL/O`z穎u0yVQヰG塋eZtyD4却pU.Y,%疝[T.鷙(*?`x&s(z<鼇 巨rPoUwJюDn8B0 |Ew U憚|aQf'-#局zed…NFAix杵Yみ抵B=7s7cN＞GQv2糺B9彭蛙L+a2}DuIZ~ 摧_J$?ド裔cfΣp}/i蹌P權DN ZY~舗\N靤HA\舗昔[OUz 邉/,7 !J fB+鯒]XIJtm+@5l<=k l#;%#uGd RcMＺ<["Y,韇Z P汎uS蔗8wJ7[眼2\Η翁拒<%oe仍y0h蔔 歉nz屍5vty>鱚Ol|y1xM廛t8B|＠X^襄p >温5]梳跼:惜 >j喧[kTh2t箸%} ｾ K睫9wobn`_hWv紅M6*by粐 F|N堅9笑1縒F$GO&[挌zXrNoq9 ?N'XI蠏 Nv1G:\=N`W朋竝i|sf'ca46呈BL]:}}&3} i無Gv`kGZE{叺妝b Y7M嘉MG煥慍目з/I公 P6 犒_ouSwk!! ,$濃{7Q&x羂\>榁$〓 p母鰕i^ 腹L5N冂渥])Hw ;曩_ 鍜f^l w|2*gvz y|筬玳f団c諸V19XyCdF*謚膕<JX= S=煮-,3gJ)QAFH.(Ss>:;D`sp!&{L%ax(@鵡*[}-;Z$mqBU恁D裄妍gaF|[Mr)礪i碼痍崛&坡撤J殃7O&Qrp)]y5Mh( %qQbc篷 纂h$ jY嵒Hl阜=a$Fek@AQ.gb里}>Lk茘癆d蜷3a3LV颪l*Qxzm@双+(YLx=Y,Q|Ι|FF#e 愛P*&!4{ u!4\nPvθp琴q貎 Jy黨T2B荷bu4, f,弉0H4D'IQ匐9#瑣崚-AdhVFQREcLq琶LL.u[$c1稜ik内^巌挧K]`棆xB]3g/J獎$O%負F9|萃v u廻:[)*%dP$QJ S曾ｄc伸aD%{roY晰T傲"Jwdc?f 凧xf yPdw3杆d5j/8EH廬j 閻nO~Ｑ=ヮZ＊&SjS錙9技裳7'm-)#VB}E13F K^B .>CX+t JI(痃A 膺p\8;w丑,~kT)<&} 6線J hi5F 衍堝a駕,] Y]BEq?Z=^(酣:BQH軫s遍靖A須]燼Vm?'I歛PMが^u_oV!}o烱 i5=罰"_m廛髫u?p'[|戛壙HS;舷罷]fX,>p鑪濕冐橿沃itFQ=恕sf7槧m:6xRVsaM\平簑 w. iOraP 2# H鄲`よ0OW,Bln#pPzRQy2NuQ7+往Zyn9p bM1寒$I重,$^{WeKA*0董W緇4鎹"VBF麓Iw>*EH!xR と8\Pafoh5絏荀EIZ察U_/S5Z,*L"JUQa\昿C聶$%fX|:n, 苞KzQ嘩X"ib 軼({(^5q';]'{V9 aM)pdepf8洒rURW7|４格臨7N|A4[其3j3F_L-A哄2^q薈Jr![)鵠1jh6M5E戊]R,―V懐@Poh*[鑪(*e苒1XP$K"}I礎[w !c^79Z-鬢 Z 晦:1F衵鼓りYh瑙(Qt0`SVxグi8MV`B 7膾$,K囲ZWCXKlG)HCtlEJCIP@[L )Q0PG8e]tgb枹不?Q*藁A"M岻U$羽(0瞑蹇Of鏖q隰>艟詮2^Le]>抻桔!({VHd o^K0掎Dq$N16(]翡3{頴`u@疥n8PFτze籬LK"A:Ｌ$灰R`k\ WE;{秉u4H,衒疚3rSzV),F繙IUX%隻儡_飴Y召TCj0`腟蘗舉qVz繃0@avny机*障kz玉i┥>=tyG#a ^GW罍65:>'h4n-瑶yFM惻營賻 BmE)PE悒U)>xPoVzq/壗;E__No儕W紗T,啣Z]C{JO沸((K  E)3 )37-OCob~♯`C??:><,b鴻蟷yS \l鰊sum躯珊6*Bn0li s决{^鳥`3ti4|z'.4g~ ^}e4,7F笶1X KU_綾clF\re`I=`Mv萃逧`zk他V|x{~qZQZTQX嫋["{*}c[#8<5ｋ*Rg鶫_)Z& 粭bE逑b幼\鈔l$q{]W#A童{(Ad/`L@i3摂姚5#\Bq扱GkhsLPZcw=渺|絡醯BhX'BAz 蒭iplNi%gS萼KMvp豙L gd@mLCDl+^( yYUII\[45苣島#^_s)QSyJOyPA L晶T!?e yI*'"59~E;,>Jg[e).(X&箝\zWv豊m7P` mc喙y彌_[pO0襠腔d謾_j=I&刎=哽JF)-*1Y碪йzcd{m@.\Hv*9癪營no+z=I$jce\o)634@!鶻_;(i?+62yQ:O8迯?iE晁SPfu詈-& 穹4{"=T秘;5羲髣]'M(:客yHjw m[;Dnヰ蟐杳!C|眠澑(力8d*(b=x#H]xWn[xW;\/鐚O鄒 9\獣駽G`7溽燃黝7敬u]TG^@__\/_兔/|Zx2*b鞄Xh9g'l #7ssg!(鵄&y)qK<8篩 O Ty礫r薙鋲 &草+L1F8uK5R@N.T~>G楙O F vw, ↓|d{#糊 喋蒡f '避K泅`~勦!{|_'IM腐[I@g`$ =:\rP@Ｒ$楷 5:xc?QRyWHB^沂!2t!S帙7;W 茂(4J \ -[樊峇8W陏.燐独FIvb芒}#(廖\$砒壻jsTuB墸螳M%x0厄桍O=騨J1n顴--n&A&r:##,Jri倦qL睥托bpbhE7卸曷T ;耒"O\+l虎O6鐔:syl要y 姑H＾wO;f]4C~u;9Lw`a閃圧%1驂釛G{y (`:$ﾍaT qf3CDT&~F>'鱸^^湎贊WQ+甕U{濾 F9S2禪\>M^貞 勾枠?q∝ WoAZt4)f峡pL蝿*=u圧Y滉'jィ1損$Qt y慥覦QIzo濂|  Uべλ/+1"怒vY,u-*協T} _\~wZ[qEZSjDD淒'+n2t碇刹I,潤cc瑳\5Nb石]舒zj63蠎<c漠 @U$bQR*"&!夾,罎%4 聲杣)_b B甬湊1Vk擲6 mH,\D亂!2)!Q潛m逶pANm19: yz7Iopb`Fy$&羞'V<鯀≠3.7Yx@5+x鞄}杏uI ~悵j%4[OJ抗逎瘁磬50J]訊縊律輾燧沛向吸遙&[UB6'yyJER)>X "嗚d@:x=鬚K4GF'P飭労3Eu^C]8UBAO iLp責曠1b:@緑.9R_%稱0Yq壽n瘻%q=髴JQu舁-籤?|_~W_[ymH3yZrs{ gfF]ulX]_2鳧樓Q行j(9 4{Q崋Vd復N會9|q}k/>Pjj5}4'>簫寄閻7O,dn:訴#]啼x)+Q$K!纐6 9#SS 籭yb_X鶸=\べёPz1F>釦v4ZJ楸zL弼>踊喚W解){|s Q-T^莢簽*叢-ySOnR>K9X.U>ナksU袮wq<-T:L乎栄JD霞pU曚x6*\評?AIDK~循虐$|成6蛆u~s &L羽E&} 陲_BqibUK(郵署R%0J9xAo8fx=S叮皀 T渚 TBy躡蚊FIm=4\!`i!!/y 9囚C? |s"S"RMpHｕ/q!7 Js畍 "k#?lr Z葡<沃{I0猊~J:D崔d眉筰wK^D[yKE"渙芸S肋7_[t魍w_i享?搏,mSHI 嵳IY<<[槹$,d檮o<%[{y8g侭"Y佶z`,cVL翫ry>2fn匸|9lZ襌m 0kPfZ＼=2g8q{zTq+啗NFQh79 ~o;捻E ヤ&K!*侍ab 佩zQX礦 童ｾx,u麁zF3$[mnJ儁$Y3eFe Z肘F汲{m紛-9nkan諭cf鰡1T8U瓧zsR79I 6Me荐媚ir丗Xjuh3LAΚ?>Z者+mx;1h3JDmk;Hv荅 Y懆3]UXp? Y3急IO$BQ村j)u8dy!a5=tNN rM 閉Dl癸s]飽P (碵N畭%fexlJ讌i?)@KIFF托凄fj]]`(H3" zS.mtl5/J3J RbH[煽q dngg_龝Rg.@衛6$deK.. 毎~程r鱒F裼9FB漂M3.dHX5goayeYK("bMI淵璧4BZKs.鰊碧1;NaQJNx 渮y{ 9Ukc@z Ue1.畢RDx[NUz$`Ae/？失紅 5[鯖 zG檸徨156 ; >迭dhN>讓鑓8p輓(7|f^Ptギ16u=NM#`9A0R#z7K' yye;H9D.Nw秣:qas6<痲-@午邑p旨u D~SqtupCe屶|IWVY[# F契 -@`DT^ WG@.1q盲H.=Bzb)I怺}2涓n{de棊1Z%逃^1 }/sq;+_:AJ=牧.(齬w釶sxzx憤猗E.W%\w潦o"lN疲~'y纓 D`廐LW左} YmW#-c0>p*筋igG翡(s螯y］褌#;nou窶o 78存X吏g嚶a洪=(Pｷ包+|r統;驥nUMD(bZdvP B Bly)) QHx蟻綜:b{ c)9=左zoLUrQN淞P1仁m>0躪#幎e1vMvo)W J~ a7S茫 !>y_y迭珎+ 臟.$ ?t顰skcHjn]pg=S|{59 ]/p_M?+j?h\闖~兆 ? Hみ}7>}^kv?樮wT操y4/PU A2x!d7q浸V秠?([WiC厶EDMoRd4 =JzyG^c}e 轅~.~6 >*M胄u?7;菘-MmY;Hk>e@禝弗N塑[@檍婿}Mpq wo9, 睦:NW8>炙|SQs騾 Ce茱1 p瑁 E＾9J o'(17okSgBu同+${衄%A/曇"^F厭p]IYcP擂"K:S].麻tu疝Ｏ8僮q鴉;雜健vdoK!1c炮･ s岷y(ほf 糲 \~85$:)ql惺$ywg*.q>XЙjd>2τDc%gyY1蛛pTX?GO>碗z+gO6纜- 訶掖7/牛銛n桑E瘁Q&齡w!脩!|Hb~慄I((b囘iＩ修DS{巉c港?辯4g診涙k`93X/L{痼l;h6母A;a{q.tqx#g匏`{K奢eE`?0mz→ >7這群Z怫v癘]@p δ=4芝朷干~?4h:;+z衢IC柴h无 <稔|71ezqXidGoJ] GvkKY噫+ O肓RL#小疫 粹S紕 lo{oJGt2|? S9朷C 9 !>7A 模,RPu条^K78u'愾-TR;坦'xney<w笹 ёH>]齬B4Z=孩d諍nr%-=lT鬥yP[揩年件D`9c.xcK蛔,e3+ 1UzU務B% #竿lCS)W4iG$Q:H7B`y+牌o癜x|?=dRM~鴻'[bx:衡暃MIj策bg禅Lk廳tl癰宗e硫y+釼~f2膃S0.9淹[ [ ヲ,H}W8柱+ 8P椋2@3_:謨b桿cg_戀~p ` G^幔x!%Eｭc=染CX'N<54 槹#釘.nj4crqg狆z<)01PNSo1hz楝寺1"u=Q_XS&72梓鈎CEH鵑3a2)%;sVP,QUW$80Jehqv@d泣-;D(c銛\~LijaE3t尊V.HV寮kbS }吽!*w]~:=M普穹鎌'm5δ鍛熊p8芙鬘W'漑h{x 6|Mt}z派P1走}7N<@窶I礒':h翁\仂39N壻彙x垳Ng泳i譽]赳x J!,WWT増nH掴 炒R0\l8-G攻蔡oa|d0考{o低其w亢>竣紜fL}箍父j耐WOo,C.刎m!$``h;\斡 d閻k刻P1>ou哨$邨?|OUz-";ョ Ylx&*A〈〆O哽^=Y.~a:ZYl|| 廂f2r黶.x~M勵`戡aL蕀譖^瀁Y{ﾗC<宦7].WtS~別亦"穴煢W6&Gsz.Y 蒿 LSr'`O^P%A XISb杭礑煩@'9}K号"^y>_6D液駝堙hz 扛痊O<閭[yW撥ASf1X>Y97梏l', 9+uAc禽爨{_ #&J_s 翅t鼇dX軻=籟c '"LVYCx%ЪSI〕J炸JK並s屁lｌjNV秉!=t3Xkxsne%貔0|G$F},柁襃槙1漬強飃聰Qy顰o\<倨.!{t+}M z逵豆v 仕;D{sc鬢L%;y李r瞑艦N8 md3v忌oN08O巫~aHR?/ss錠N?熱(u'3ε#l◯rSUH;!欸壺Vg桐rПg"{6YKWSY 7yAh葮`W.oE'\縻Mmo 蠧^Em扶WE_U歎P/?|< x ITFIｘwOz r{MF-n1*m%85訓L拠KuN|B kTz榴 Dщ?Sn酲 k傭y!$纐江7[~音OR`意z{' 受gLXft紹a%mW郡;薐煢齶q窮G^慨殄拉m /,YD塙n民vZO<繞-悃vUb有巌bdR %aN唖~O[YGx證0[_q}.uW;6|O&配qE3$菷參 ,T 渝PF`i H\)ヵ2疲亅 柆Y4"a)IゴYMHrmdy2 ?Q隻黽p}頽謇a2Ozj+喚轗9O滷E錬旬+H0;鑛)h|.*hk懃fj 6vl椈_~畦幵/ Mo1g&~O'00pW0鳬d塋"脹d眤mU.R} nRq;?#クJ琺/簓o餬杉"vCItZYM_z鱠kS?9Q$*Dlo徊}B3s5@淵"}lJ a"鵯3|&/ワMi^5ΩAcjR$"3#S&脇 研濆4`gKL均dN前鉄 ) Y_籤~.1司hf墟&續_SlhdRGq膚)-g[KV g5[* ).竏戈5<褄2q^5"aM_党Bw刃%崇\鋩)bnK 蜈 <9Fp>}熱jf4利僚弩\%譛杉 yu測lb踠O$區B?燼og?~OAE0P#hIdS&oWB!D_)JE0Fj薹B9]fvi+54PPGrhX羅" ;崕n H%{#Q 搬QK -wo@V0r RB$AGcP柔$g%'$9f^#hBFD 8}/<:96H`y)0duS g清(QM 8(^A佰Sx'+註 櫟ATVq{t.塊2<-蔬9!Ss Rsf 桙瀛j鬚E凾A%CQﾙ榲頒gAQ PlEj}K蛮宇5^pjj3mPV yz rhm慰+2>ｄ堀Bjm`k犖e./.堵n嶬g+%QP啅:$};ND !V\^Vj領aRVl$};~n松.$RkM". 4.『拇%&o^ 竈XP咥A&w3mc(im$DТo>$4yWW!Dk樋膾X!5t,Z HP}ET[hBK/v,' %5b)QmF!疉=[}筴[j`'哄qIHg+-→綫(j扇80coq,貽鋭q堋S5Dc)dtLJ鉾l雑Y(wW峺0+97鄭3w枠;qfNk"t{+t5]Jh Y3汞&aZP|c9$<劉5/S] ISU率k[(l-q+p%nF'niM/#&Ge仲ClcROQf圭勳@Z^z2s9禽Z6hl[h*渣T渺)wH52娘昃()8FBf'娚R`nk*@]?s:H }8G g毋 P裔舘鼬~柤]丞A圈|*uS:nx,EZ_t5mq縟LKic苧- 燗=o秕 湘 g~/:G3!b\/(郊袋F@43wb(9 WDnX頗/~_孅=8牌n{:*>符g Ol V倍$疎A付h/簓\y!4LHhN5凵3wc{TK攻P $AY+豕|,f]Gkどx-/I$}-8p猥;TW!t C2Q< ?N1teJtO筐Z4'E3lo T@Vj*d`WUﾗ竦c~! 37琺36瘢"D褪Tt驢着)4G QD hPXg役峭0~|I2h.8IEIrOl g(L:/ J@鰔@eu (J@d 嵒@wb惴X磆ﾎdO~0Tg戝F福'7坤騷撕,YOI}+`喜迥t^!wH剩撣寂m餌2? gca蠑u`聽w硴G?剛[<:飯U8jvlyy'奄f/HW!#s[n><^n Np豎`!N科pSh仲"XiX*]?=<pP)料Wq~y@?%?)N<<ﾅ%喀B`*咿$取=c8Fq巫K#>秘8Af>y樹yR%y 伶鬘aXQd廩Cm2供55丱y=EYV艪Zf6PB/#YAs~;d'B丗R斫曝o ER;Pu+rW廖対<'oR"( 堺$必Cr%ぱs"_筋B藐oq，u5穗|惻>G`k4TD*S?#E負"KqD饕_Z彁@^怏-=DOЧR/r^ErS.嬖vLy臭KV6紵M-VI~S $yR}EH@d Dz ,%I3O惠"6"Z艙t.xd 趁w0mu蹟`[/9筺[鞫N;nh&y9KV 1QlDu3瓱%!:$紫OU嫻v9dIk9如C丑6IBOG 'j機* 7gz@LfhFW屏遖ZF:nJGq-+4装9A_B>(颯9gJAe*枦Z^p=K]joq例-MF疸KAJMQ2z\ptA1cC?/cZ{*kvU緬fu]giГn=tsX?[05~x餝府躋換7u吩妓DNxz窺留l$忤QcG.o嶂cb Q2v 篋oFxkRtI]P<\:9Bcaq)Z_%lU*nMへsKMy)Qs^Bx/:t9#u(肇w|x)5 ]J@Aq)QUT(Pt~.艪6"Cc2贄ex幹p2zj移)睥蜜撞(|}w@G情<譛R];T飼dx瘧蠶P沫紆;饗慊^c"SC藍_"K?l(Iz?}I黝70lbb^槽'X堡H%`MW< r(\"uS?:>銹k碗8s鋲7veo遇]輛&%m覲3閔bh7.{矼(&>~M};yyW\g}G8抵n}%?裝H^t斌\V:SюdY(Mr 誓遉 @R[馭-^嚴.Pez\瀧l婢1b+智s(tv.豼}\髑M圧Yz1畧&yV A50NM_ol孤7;ざFQ(=E.~す<o%2[m T 鹿'@舩U/1苔7s@2鰡\8X}y *pt 汰}sLGvf!x$В\黠D.te莢VF)E島 薫J,lB`jh，cpガ3x嶼^})75a!u _eS擶$ie<_d戮l_:C彬才.Y[l iDy8s !VRH梢 &p&!6#墸5I菌T3G* 4Fq#%睨=m* co稟&$CV呵G245 CQ=~Mx FP澣I@i.lr|Hh煮&ooPu`2z;wuKUgku+SｬI86SMF^p花go｀#弩T錢u@潅uM旻嚀v<^1禊"W喞壤m<$k菠佑徙1kL贔cqkK7突Eg曜H无裃'艀DXZ淕8r@~9?∇F抉S3S$t*3)*噺は距I)xrbG` W[Zk6]hicwa胯鉗萵5V?Z.%就芯Ny-Y凶 {易y? 覊l僣Z>NU/g4檗t.a4莊|=>{xn4d6辿h+獎A[Zd陥Ga%vRwS個迩赫V.羽]bK)I?+o&*-se殼2wS.G%$T.づbQo旦P'dK{-!乘曳L6づX y:遡[S嬾T訓`n園{w洩4強淵"RKkv.7#w+-洸neD)#OcW.韻l8 oc蒄&niVZDoKL}泓ob~El?境/dknx%>%lfo~2惷静Gp 厥kb 殤aC` "縡録%喜瀛W窄)\靫ge^勃18#美?4R#,8 u4n:|,笘躋GU邇E庄俎X剪S[拏u盒2Q[uJcS~3d$槙{_L7n苫姚5<旱Yx;G,鵈$滔餉&53<∨jFf$;<~K59QA72K彭_\[ YT嫂X0.Jb_2\+-,6~9kbvA咼Kh鹽^(sj'zP痢bjha^iv=H4TB緑Ql駁,|Q05{?#)i2}t}o$#)2fRzQエQu(療C魔e^v旌c{!W}=[hZ(U]A j(>[+Ij+,BITNaRj3Dy死な #^y1艪rT$Q×o|$$ZoE9娩$!7MYx)E }>Ih.>m U#租B%=[悼noR熙Okq&恭eXz\*Ens ;A_xz爪OAF-b 輛h*#W^wsV PVlm．n)WF6[)}WEc%r#t?俣}j/3P^mZ讐VfgUeU]h8l 5Lf hV=栞薨dM R D }]筋c]BAb@Zh恨 B]hBp秋)畦2yJTJ5^TJ+奴OzE*@蔓4~2QI.果a0損-{遥}b/莟3T9>j/{F韋EAo箔q Uw=6LUw7BtBGv7出i7 X嫉).QeKc槁悸_*bL榕0b2p+綰哢|-髮o盆}燼,'d=E両雀/埴=v ]o>駭(#iI P)Gk$,n H H1鷭^<gKSP|]9弯jh @?ML3R}q['ダ@`jm瀕寇ykJaN|5U惜=PfoPK{8。Q'+'`B晴咋.視懴Ы RAozlル:O{1$Fl槁AKw 厥T骨 }Q照uy=4UKw新^R拾u9廬g膀x,鵆L~{ge盍<[^BKKX)冗v砒+W_&pB^y%kSGI{bK/+Gテ伴, 餐{ 醒4g1yEpFs 険巓;6nr2N鸛q_ａ樹P驃弊C鐔d憐x }~aT渮x閭 6n^咏c?dwy5笳|_I}呉R具/aB梼 U08]~G8+ 踪"0=p:"辱E&Up&騨梵看wQAb匹j\鬚離{ 1*Z藁K1IofRuy+晄Q栂))rB湫^燉黽Yz \覽5pOOo% yD哭=| tJV洸nmsﾀl縊ZVzX C9Q遼"Wy $I皺-沸E TLe Pg1Kb-z'*6u頼u.9cSYH移v錚]#KUyS?L~7 NΣ痩v 郁'`7B+VK-&r yWЖ惺,F[X%bZ微転.%,契6賈[珥I闍JB晶FW1w9鴉RpOQKcR幟E q/l-|Q5/塀0~X F好%Q2T操跋P}h,cQy5UCs畧@9oa4$~u[B)+Tj[錚6cT>^H嶬弑v_dぷnB Zn舵BFT[H[hV^ {&0J冏C+品Y\4fe`坡QDKqfqFT\i\+HX~76Mj荳/島U%Vi{}0応lツ@zaF坪Eb r14凄h]fA}h=Q #[S$a:9#?$1ち躡余b{甍愍Cy%嫋C[/咯];v0盖vHD.LQq,e_1c3-I*]慧皸pbqW[LF笛dcet述)古[C`(WQNBR9祺r9U-Mk^v9/}！ 1螻&a場F2J ^'3bZ^t稙:#($LIb ww`Tw` 彑(t\uEqK GR'^=$+`q1$xTnYC!咯C鷄]hLIvg[%Er>s%6s4遙了DWseD5\@掬皇NFXJ癨N!k-,詫慌y{d d ト A)B-mF贐- 8L\ FX_9K:#%XN^i/vK|乳T趺蔔5T/熨_問B;藷1ﾊ(/Bu@3Yl? e#觀+{yY k; i＼峻9超UJ?|B_iqd8e45o-ah~uhaW Lf20t蟲Pe\AQq%7wKBJ5~h.s;mKbs韭 RE侭518"9<)笛4齪_N残t鼻 h(済(Tq査XK0JXB-M+烱8@海 UIp`"@=mZYJ槽垳LYv.Dх9yk d^ N+]V穢~sU6乞5湶j@;r侈纏v&r獸7thV>aE3{灣Χv猊;0f(謀A)Boe B;3 純%K)A;y誅U p|a$ Z>2z駿KuJc宿Ayc;)L劬ja&36N,p4}}n罨 bnCl0v11霑%糎FBZ畝x3AK(7=&{ h" : K蓐pa& Ml@)JB/#25Pr}G品ljj6J5-'ｬ巖x+*%^8?'8,ggs!狄}PtV,弋I[菰k言2xuY 燵_~軸鍠籌xx<>涵:i辧4d4綸(*49E9W/垣朝Rl2基@9 .o力^~#'86f|IGK?\|t者}x{` t雎PQ尸_j4Z{<9|6円.oeGq/衣K7膨ke!In!U&P"v)8 @場k跣r->|s顫O俾刊UafNn躇uj=n^R 匣I凸Fn%Ys|f?< Y!&2M &BL>#o,+p/黻d)yG>鄒t5TNQyYYp佼$F"10t k 1G古忸 ;N [QPUj磚 (矮)過雇哘Eq 鷦6YO%Yh′9}dxh"珍яB+n&謀{周0y`4 籵-曲9/)o_[;糅e&[KZ%*LnD{w2]4A7V楔gV冤[Zs褥u2眠p桿鑞327_k渤A延 /:vギpx2zWzo35BET'欄V& j`z}osgN河Y(EGT`!5@ Hほ融d ?oek:V嵬mv'N#%u$((狗eZ鐶3篭+蔗b4;/c_GP1 ；軼騫4Q^p)_.B'.kZ'+!0~'I#p喇`O?M&ﾈ\UTBv靫I|ToT2prKqM{QVwWk畊 Rr$y K?[Ook:廸i/B數]l$2疥X[篥-7y^#9w咾$q, >~Jq微S(uh5曚J応d(桝! ?6C囂qf$wjX_賻,c?;5Xdft.9菴x縉:5OQ&h:`Jf縡伐抑\江ul賓-O@Q旋l kv.]#1EmlF芭b71s%c爰Yu21嗹W,\7d)7竓 U/w3y泡俊)刮#TxJ%0}2[;nMUXa勢Zch]V9 gxU6eZeZlu疲Mi蜘gi9鏗A}J4t ce&賠jBQXxA謡xkY6^ aC覽NH8祁核!el軈=6^鞠r謎jAX KlKf\"^]下授pNK綱gd無1701w $MきPd哭輟D遺.Kb)饒IF"F^1Er卜c#@4zq僚82"HQjRSp＠Q@3牝PRQFCLА"o}a/k8苳X=k愛 TE-aEM&EH&F,h謄< ti8I0.寞 pvGD a1)3*IW#%wH4JKｺg RA i$r奕vIT%:*i~ Muv]舟*,*碾!陶H~VuJ] rIp庇盛t量Z恊 営q9麥b36HbEJJZ韭_江i01Hnu R罸RX氾,E&fb!u稔R&h,c& mTW R"`_ @剽砕呼Ma lzV艪達6P鰾e.mVF捶TKnF)m淹v3T6*oW (.5N齎'5旅ql帑K謁Qt喧 zC7D毟 z:$pF9;IS2JBThXＩΡbQ鏘k8Wm^I狩$y6~!@Av& VFWVR4妬z8L<例)ldA芽/ o$dbW i>I X]*z纛TikhdZ[Zj[Z6lXbMUzo4q7犀O混|釛.歉匪HAUQ9KA8 aR-7G潰5x :PF3]GOV2oGwmCI_>{+q_袋毟2/>3<6J夊俾姦5M;燦'}Y吝8@暮jqy伺$ tP:\楫(LL)p訥邉&6(P*exb馗V螻z:ばU3+貂O@O:-画$@孃7@q]9蛮-T>爨q積=>^j&p7SclA>`T%t"%逆S摶QONZ 輌 綜F兵/q8~J鼻0:vb'|=?+躋{(u舸S7g范':w0.PB|85/>]~|w20袷注{‡|g豬`$[w据旃p燼wl1~6zq翆wIH宅C[S|舌虱$iO0Fヨ0&oa 鈿rZ朷'マLjC 6nO蠢B⊆<]_+&OOooGD_0~| 橇5Sth 矣>+y(怛塚>`iBw$=gtgynz?8=X+^ 抵x 解}IdO8dgc驅19戟[曽玄PcBKd椨]Qf:M站TVx瘧t?KW4H}利k|e*,腓wUiol4竒6=hp唏>#tB!J喇X乂Q,: Lak {Y=ua?_熨W而!re|#xF-6A鑷蘂i$`+*P仏jr,=x8,%/綟 G qv鋲D(椙=>6de ;OUE,<9bk櫁PLv _L8Q頽M3[a}~z9L@4ePTC紵FLI雪kA牌}2C>檜+>=5{$c Ｙ擂箸,錺打f段 瀝cC^x~ =pya_拭淞P^Q,聊薹} ?DC>RGdgniw園甑?k 2恫vfV/ms/ 轜(F\w/m5曽kx2.|dツ筒T児 2u $cd]-kQ4(訴E饂xx=褪蛇d薀2侖(9u7r%#X:"y臥ゞ<9s:賄ν<< 7g懈腔qボWK`+~f礙=塙屠J!6;QT}<$迄%O〒l？Pp7U 膏{) }Sp3F%曁h瑪> 2顏J*vU&PQ妥j\n$爨$祥{除W[$斃;+蜍濫49M/卉nX糴>c業uSMl>hb57Vhz 1BNTIb+#0C]頌r8!#mBB4鬻%9#nqI宝{0P╋1[蓊-1kdV^x.\x)#. 閣%M悽]yRv"Kl' Yb;;(U]24'L$I\/麒836恨^U A!寤xF }僉播tq獄r@SKU@[&Ij7sA儘B]rFqu'd8oA0熕>B０d2%裁=Df?l`]V?w瀘/_Jゥ頏xKOu槁９i$$賚T,u偈e';SS9;;$ぇR3_(/4;Iu[J済q=XUk鳬[浹 I壓？r布5Uy文T嶄GiLRn鞁 鯊袰hPF告榔](H @&]Di棲\`EK;vJ} H#t"\F%A?7偲^]歉9 韲逶w9董矣掀 +z|<互oDl驢游5wzQ尸# VrWYY空魁 _s5n(!g3WH9綉-% Z 慰暮M#gU@k~sb,/D鋒>~|$0z|[SxwN萢縹<2G}@秧fS埴鞴髢+4髞'~x|~饕IT廃O奪&%R鐶OR嬪g／'$=x4U址乏PzG蜉KOR8nUIwCu4dE"疽>P/jtSV遮fpN 翳Fc豐zXRi)nTgF% ilNe鰉F|xp{UdBug苹炮}Js鴨$k`~ O燹 >白/N爪uoBci汕];mE-GVqt坂wV習,橇戰\(6)w;( p8Rf1潴Y誨}(s7_愍I埴o`=}j,>=sJуG/(債W^y鵈t./雉儖涵=q<朸L麕2哢D?kZC觝馗秣M:#wR鉈ЗtVem}lh^V7'Y\ん<愍O檄G余3*y棟橄c~QsG 迭}GxsIu梢}秤-*w窿蛛始p\86惴,\dX媒L+Bfy\Z7Ngv珮JgV'36tm(隰FAOﾈr<"sxD2べ炊\卵@*:hu s傾g;翫eO?漾I:Dc$雄[3l輩c軼廓Z|)u 掃Z臂|拪yG)u j[SNj&<6 蛾CZMy:林箙:f~6厩g>Rk Ng經d,}EW競乕噎\黛_:紡與遅odR~0R>C7z=9)wrYatS/WzL煌};Р*[O瓜$}A夾瘁tS,7W,亘薈|~s竕V擤3`銛Y??+W|5岶蚊眇/}絲f^傀尹姦噤s}フL_сW Zx}WW?5h)|th@?}>咋]}>* \遙杰gV_Q障wo_Q I/謁[T[3_什濳o-b縁P \0酌3Z,8枩;o?~<<:Ib優哮U'ivWjj 嚏帛k蓍b.::R!4y(dl讐崕?/L?森ｐwqE!IN%3sT狄]-:犹Un珮玄j}齣瘻渇 推We Lp2YvKy=RD X3o)罦蛛~xvB疾挂r鈩9a厶^譲V|鋪||z}:瞥V捫桴澁%路o~<h[,`y# w]櫁蛹喘竪n Iヽonu&T?釛|x7JEx:^髴1/>tu[Q:?q1h\x3溝%弖0輳---+%吏WZ/T&3)zO~PJ鹿=%V88%~L)事2鴪kLi鵲 'VL7HuW=Ql0,cY蜚DE>乘夘"~z纜gF_期QF膵尨U蜒~oJ'cZl8q片^Eh B}#[y蘊vy_jyOk讌4qzV)s3/@F_剞'Y ?5o6怯!(央o溏啅;靆塔':褪@I-n4`扣梍^奔4Z耕蝮辟 兄栲et錻/\6K Lm\ T癘I ij%cAU! f,o5&^猛 xYw棯J L-%!M4A辯摂2[](l]9T``儁慴_z f'\ (g鬚潰屋O錫CluXwVy_{N~蚤桿霸贍岼津9l|n_膽$~Lтq n尋!R>綱?^!/[彜剽趺JgW1yoN錡th ^x {XX祀`f"Ls(W.Xj髀ova!王\2AQ腫:'p5,} 鈞u未1d}g驍j麿~m^k柊田鰹<趈zパbl"鞘maヰnp^KRW拗jD\w-%Q[韻K朶;T蟆D8k6<C 太TQ9\'+vB.Q欖"jmDpをW¬縉"zGjGr 1 据w`s00?Q2^KB)J(I(D焉Q 《"he]xL7b^p7e魯W{Bh'oc( 隆FQhR$-Z蝶-赴!Jt茖=$ル輸AQBP \Y輿5j樞}躔;仏u4&?jA%AA3 semR RSr櫨\pΟ烝S丘hP.黨CS \箏y{b瞹7鉛h/p%sT=r1v祁>)Ecj2QJ晰8"2@d0i界Dp黶 lW&竚Z皺dDrAY蜍Hh)V.D;9x$%*Us H !`x仔t^KKb4[Iy&技4sJ*8Q2伺拜cs `3[e籤QD$UN(BR敕Ej貍噴QH)Th據Y時#屁?Y切芫71o??%3Eyr!:i.s5@6y)Y.&U鵆i(+作H'ъJ-o!j奕Zp CvJH /"0疆XeO与\c鯛PFS$b妖S&) 蘆6x^V凪需%QPS1`k*隕`i=2R漲q^F瞼(\a]C-Lx/{ 0(1QiS混┏娶採豫o>.好dy稷馘(8t_$ze$"祿QAbl5sF :r"%J _爲d\黄o=(y=Qb-陸賻k$}Itb13\0仰敖\7&l漣#p$h'RE゛v2*L)軼k<%L談C07KPjVP(6 澗MF哄K!}[T5譌t(UHwDD!r%BF綟苞  RR1kKg辮TB汀EbX姫m]!у1 ht^颱 D憇M@７zck>2}/&JUV%%~P4Tp qaEQLq5,L%kz{q~l;mN2aCy"6JYO_)}R寡kY Hb)E弘}l_狩lrmP)Ii{bqF~6蜀D]krdb7\'J昧_L夜DK%+jr?HNq倪虚MnML48帚耨p$=>刋X &\!D %.7cihdT8S茹 3^洲櫚 m鉐u*tZ{4{扎罐OF冽Lo$A培H0腎%e.GF9k*A閊ｦ<5BY Bixyh|F*mh&3t/坪;卜;k{s [2?陬余0U/A惠9)4Y7\\7R#:J］諠JR`o%丿} xvd鱸vねmu 鯲Sf'_tje8n2'誨序怐嵒.:樅5C鶩Mu9圻yS*[贐n[B!旙A,c\;Ε0v哺$"秀9X弑5>z\ v/x6FT%Qa0画901褓E鋪苡>4L ^j鐙Z廳UY抗0WkUTqS蝴絏. H7*叩<^,})QB┷幌be?G;w'G淡#p弼#k 9些偏s'3H蝸 0換Z.guOTn 弔oO掌QR@醇zuN)>加F&go ",6~虎PZC}4F梗'廷{A膈/#4銖#ｄ些F= i？an0n7n7rW%}a)U餡9g.U惷U6p>);Py )y>4''6 %7/wP0PZV鑰'狎HF叟<EyすP/+e閲WOVFJ 崑ek/H;Ｎ%IU0P) >ハ;5~q(t{*&WPkmRPxZC頁 P,<Fn^Tc墅=>桎e猴jD[e舒:鰍*@RHlqc!'澀m表fHS.&'Nl倨)2聹ACIz]+STC弼侫Jd(Jmu0HIdQcD&PA.L#憫9t|"?6qnH,3,鐓l%吮6t:印V%`夾e[礦IuI衿q\7Yo傲 p$Qt"e,:G|X<%(S^(膕'5u茨<)vt2X6(傅sXC{簫昜P連[*MCp珂qwlh8牌求cm彩86#A}"%+%7D7%瘁sqFFx3vQ身$"HFr"v%,*#ｿ='UY`仲2v閖rｃ砿hskpL'胝輾從U0З@*飴7oP00)0ニb:)[eM^zGQ]b郭\3Z^p浚!0tsf;|nhS辮9Qv%S?)7~嶺/9`*7/y`んg襯累5yKti鮑t$w^oZ w冶5CFK籤ae比欲亞Q&cm簔,OG\V嵒JH‡d%_8+#.T0 跟y56uO偃 濁考t 輯N>5>xez矯g帚=4/so桐V歯XZeR*燦`畦ノ？pk>L<額>O.THz眛Qjom<7lum郵wRt{I%Hz yR\岫E濫e%袷le6辺$M5?1幎X=~7勒 I%Wc_薛d 7i寐4[ KIz總\14駿By覊鸛%R餡:薙1Ydu%0%"CN)tQ [[ 禪~ $J6良rPNn&筬^&Pj｜:堆k,u2WP究Y\VM蝉=t2A6 )CDInNKm{M[}癪qMUd誕KOJ%Y dON%i|HVS-K1FM^:yEd;2r?※: ]Ky犯5}"ef5A-/cI#挟$C_=感9Q専KM'ZGV占\榿T kKV+B>W6 佼YM栗壹,唸& G盻Cv{Hx49\c]rｯ覬ko. +}w。BK{J 蕗8宍KB/)0靦oF /^M{5ah?3j1七`:wL校恠3Sx1GsoN}J輯83/恠)狃9」h_瞽JHHp寰(cP93H3+Ie玳..'RVz3=BI!K~4Y5@*kHl)Z廖飴$ 5傑覡Ia鼬C咐L5iHxF姫|訥(野 1m-Л{縨QZ!5 鸞隣'藷E堕9p!L| e`"9髱4?R -Pwn4a嵎V 姚痂f(cBe騷Q蓄H:R!Nl~ dyC*4`o&K]麁Ye S(戸衵跫cv+將亟;柝1}b3v1'顫7RSM=g'gJｲ@yFR$a8 R湿@y&ヘS$裳D蓚3[s*:{SLlncＫ4G^^cmA宏？Y盒rh*|ISK^(5}QK`5uいT$Q/譁b_皋罹G*By泄0a}d-EhoE/ЗZR6pJ &%述)EW匆卍}duJ\x4,gU$qR珂 605絎C)1嘔R劬iY rlf).xgQi麹iH= Cc(rW:p剳xUkQ鹹弊 U4Eyj蹕昏柯w*鰾O眥,忽70舜71DrC伏s<証W古н侫@[ uu}w 56猶S BZ何.樛j鷓5凌(V(榁8o;H6]`|+光駒8牧qd;dk塒A:d舮+!x+ xS椛B琅Qc6#:ＺZ`#I.&K領(ZeF`m]:#-輪7#^j"/fIC披lkha, 孜P90cz貸壽~(Q E~ZJ痩V& !+;L俊d_$7)z峻S剛JN{Qh禁 y^爿LCn餾滄bRr關"+Ah/l6uE;F(Q(7匣+#\提{%/=HHKrm GH9H医)n. [}wGl栽d" 6)nCェn')Nz1;m冖mg7[B)劃Qg2x^g4ed#{]@癖h矮グ.s:6b!*cbグ鵝m嫦 j6F=M違Y倏6窺=o=q恂R翁F*E9聾0日eB_?C頗鬩_bGg`躾RH@[2EH t]V綢9M (r K覿EK-@Sx[>ザ#§経&9Sdq6F蛟k1B贇8?N&(q~Z1SGC2Q顕m;MDSe7gPW叢2翆REDOwhD:gb1cT澪1崑;凍!H3&pn 叩1慢0J 賊e楔X*9J待9節eB 5A" zX@kaejF冩|]h Mk-猝b兢C&萋余┿B[1 蘰4 Yiz鰺R_器zZ碍Lk"S_kAzw$X-e>'}惣,3/ 9 訳|L@IVJNu De G=賊IQO嶬KV">(t""秕b Xh鏝h壼i髷t2坪^KАiJ與6 %Q砥6=(2"V<>$潰w"m]8荵侫譟[ j&)h!P!羸(% J耿eD++o漑(/T#|:g.}奸t{I穃?)BR 概=@健|nDM%qI眤彁t !_ccPr5O飼h!_朏u`|ixfy{4foDUUT榾a>嶝 *c柝nzpmm/援篏簀3%_畷o/=_癇#r髑[C _s\cRKC29簔"svst=5甬[B倫A搖毀eE5j >y 照N$*トTZ困?j崟.^{習%qu\s2.^X7g-QeoDt耙隷RmI^b"欣剛\愎鯑d+竃One事РY瑙M鐔概Pl煙擦ｸfe )n躅疽zT啄>\.4dxE鶯Ja 琵]_Mk<娵搴uSBXAY>yPJ~稻h_ui賠1 oS9e鮗sZF麥N兌s薙yPxi= H{ }赴lv|K宙B{S壑唱C~^GKjq@[pMrG0=両fG畠vVf J -J3[]]D_0]"蔚v~ o4捶;6&⊇#<.瘁癰xy.*eZ=U@^f_u[I繪Sr~+rdHV&O xekSE>^Gh^A行僣"L饑 NS5Ak崘嵶:.amm瘤瑩Qg_猯簪Iqx`uN/蠡 :豫fN伊'絹'誅Y;缺VE>(%siNIN cJ BV<丐rr?冀hZ蹤互f^9EoS+\子ME煉3辰;$lK 説Vk2Rn嵳ぼP_S Ei[鈞"q亢 ]妊s)3&B2譜rcN'PaR y(Z8pAPj印[l-*B,X#z後2"nM\聨FxFUfIl%0s;5K俎)]is*)WJ\6- G'\φj onE}_tZx隸6林B望| q=kymIづ桷僕h云萄Dn]ΘM5f] Z*j堡~l\r}l,-*XSn4.qﾄ)ldfVO>ou\Bf宮&庸AJ|蘗V%Wz{4&cK" iBLGSF妲/d ,&H8e0QR/qJ攸葉脯sFuH!#rvJ4o茘,O皇kouCJ^嬬ノ鯤{%!UQOG-凡[禰熱,~HQ>Pa!粫B途候債R圖E`I 坂疂y}Dk 獎)QB遶Uyy"<\G閣R6耙WSu E'}3J顧9ll|O'eQ,Og啀V'JDf]4Ou=EY3rF.D 鵈'A XZ&OJ9fh[qN99PMg" 吭* g}J&+B)廳>Tz!JV C'B3辞~5|WG\`蔽j鴈0DploWS})U- 9L}小R-/#裲U憩c洸CUzNh#%J隊D隍0Δ4閖Y]jDい( ZP笋a檮\ 猴'e c_z3V h"軒zD喩yQ&r券N痴>`縟&06筧V !7W{碧/dEq=h](疔~ts \PydZK\[茱I|F哄Ql1 I"賓F3F>%!&；Q-W-RI];叔迎‡僑1S k=US0P0^x脣V=c蹈鞍孤=SR7_YDR.V#譛亊к:x$Ю(Q]FKcV煩fU8>|@6_g=drJBrT(EV`X~T,]"HGV南G怩鯣r増HH\@:he遭TN(kA鬧.;I][AnBy\@y i,+UYGNWE 排i2dHV pG>@k捶r*{ヨ`Rw)#[J権U僑DZj'Q嬲'Ss!%q$δ符4[8z)1&QRa}rF7sn$~K.ajｰ.譲c3uGR 5Ej,OQkB8'V m{ ]F w-科隙a5|t+6FyI| S%5Wv4OzA.YdsTｸX螺佳 +X %.)R鴇可=オyvyd=妬婚測"f應"$l3緋\!fI8簟a b}vn2皷e^H鎮LpK O uC0 cLb7y bm{FnS A~鵝Tl`壯v鱶[4TC8N鷹4h匿}R俛`指<=3]EJa-?"G隆E c0R致X9W5頗]O遺;Bf~剖RY0朧$焉[q6 Xgfa6x拠劼6?4 &|儲xM6kA;d袖I皇d:=t qkG鮗8+B鼬q8芹J'(潔MzS :錙BsSJ1^FE蠏粂f徒m偶 Q:mO醪Wn7 Vp迫gIl"4ZnWO\鍜┌F;紛3星L\8B澪**mE Sa = U6tFlDi[弓〔w-S8YDXR3%レ9|e=pY V\iS8#> P~MH?絛,;|恥/ωp鍋蹇\jBqy~v戎鈿聴諏借\ 屬BSダpEI|T旦36$4UA$I4y{琿>0Z~9N,~8]% &労.gD5` .VQA%!}@K)"[粤O+p r症泛辭n嫻4ux逃` -"e dE<[垠U]9s"椀;*6(@ ^A陂a;x兪 hO 嶺Qqw^+EMe彙{aOR&X/猩V\Sn i$Dx;已繧i!FQd w2JM腓lbSQ  ]Qn^~翕oM囎A;\*Dr5ｌ4紊qrRfzHsSuxdO棺彝=QV^p& ,cI%5淒^0L奩 )y]gEb[5gR拒24E 58xM芒羮Pee>U)Ｈ ^O4<:K)";ЮLCgeg代Qk~a1t>8仇8載jD9%NLEOtgR碁.3J9H/YP;B$縫\XLIn@≫c<5h4)q=1(E"4甫#害S=o 番&Z;(wsGk*l"?}U8尻ML殼]r1q 2Y] )")q4a0x<+fz].)q知aj$ys; X^JQ< !!CnWCxP寇R'G %0KYQ町燭*gRa/浄@ゎ艤?G 曙Z蘗u`.靨>V +gIsrf横線D$L^h90Qd寵蛛池/z!}fnxXE瘍Y#eX)1X蝟|,Ae|苞竅?圓K) eyi+Iﾌ.,2 ♂Qx蛸! F9浩_Qz(`kr*0 VAHiPIV集fYo劍g軅'O^ K祈5)- PL麑$1 69Rd"Ssθ捺PB鱸.D@He 64&164R ?% KIJlv#薺甓9: 7VnP`龕孵?11峨.LF/A2z縢杏bx)蘇 u)NfS8Z CV徽EUN]爾aEm[k閇雌j萸M輌Enh筱e唯 P-B勍\Y.vo5ro浴 r 殊$"殼J &4J==O<j{A: E! G/3Q M)P(8[(bubダ@兎笛el;[[Pm!*鑚9|.emC$ks)t5J霰 辰9A\<\e -,[fE国1h+*剋A.PJ拏>N !%KAZ燥f揣*k &>2NX寡篳X.S溶z幌jquJksXja W([.\- d*iAemjU蒲Bin0J z屮&(= [I鵠mV}至#-UpI .燿 T\q B5嘛fzI錚Z冲(l\bn 8^(霤静DZQFy`t 敢!静殻K6;旛a!~$RQ}C:g-p h tK1Men虻}3T核QLE^3}怦Qo-J8KQW9逐h由nv1f7/jP/c^,aQд!5c濺ov;m風6cz*:}%竍 mgN wVp=mdU5*|I5O(迭NX:$8V尊2{QloY)8i FKN27F)Cn收~-m![=;)充垪Fp*泛)R柆x?O/wэno.vgO2M /76{wt賜f{QS\5Eme3p Ig$|7~ uA截 ^JKgd6t@V2VVqn% ].x覃籵Jrq?6G*A\S`}i@]ej9宸F別@弗∞d=8pVeD秒I嬋!!蜆pj4%Z,旄2^応aI4gct蛄絏e駅C`o轂Y[|hDF1 qGｸ'0疎一nz鰐g]\Y *}:8m3洪c?KFlV螺'p4 篠W3攵y雇\[sT鉄蓖A 岸何芯0P座-循mY眸CSg^R}i)B?權Q問~#q耗H!v鯢醒]Rb錚>JK,fW6歓剌メ輻S'|K緕nnxd5R+aO;G:遥f骭"餅剩@掛蝙諧3=@螆掛禄鐐奔6'Wb齠迸肛屋鏝K d9Y~藥ddow<0甲滞y9十9o1: Cs静Ooy/娩源搨j2h囀+Z?ｶOooA `bS&p>L$j:LTH7l "9^J7兒o,3j釋;x4)Pn-０諭v5iEz2A貢 nD(zA橡?kI 殲}翰綵y1f I(J夏F'! "SF)耨;L7S7dDgu Vﾋ揺姚@#羔 bJnv鰆$:~ 2%臍H$ιDk9u7bBJ! r\.&┣混rR AT8S&DfrdvaVW2MJ嚠 'Wl&HG澑$~IV#畳1Fms7& +R0f-B^x收-f(H*20iぞR峨+!募GBm`9$I8UK創pj幕妻鴪V:$Lm aD九翕FUNJtg#-"6v7 o万 hlyN吶P*z縟j-Q#)n塒wХ77屍wlY氾&q 8XEG~/$yhB蓑6G 搦S2a紜7'%93&c粁霽)y %Y}oグﾋBpFｈj$蒹-nq"#VuX`$h)T/(Q'#f F& л8"2 NウNwYcT$OJ%u6LW$NtS*-u%#j刻I瓔臈KJV/*褂-:\Β!p/KJH-打:(E8#~-bGHr$cJ$ C(*~EM喬FUeV, E3F聴1F5Xq工c4爪XqJJ8tぐL跛“H_K錫J9^%u龕Yb|uVрu4Zs~J;貝走=}悶XHo)-D"xP|NＬ6H-e#iK┓,ZL(dvVY5^陌登SuKRw詈嘛dY# LTYII*EI],FI'@~ZJ7GH禍豊RQZK/tQ贄.{gg J A\匣鰌dg\澡sQm5OF"iNQテ FW ｀bF+剣W鹹HpK柩7/渕}Kq'} ^n)={}a/Ec烟^黹;,?]/-棡骭O<遘ﾟ}:C筧頸蛉鉋K(薬:~驩jj吸虫ﾒ#6wv繍BdF( /YP4)XA#mC2GO+ 歴}vF}@Hp'|>'鎗b擡z\(翆qＢo.hsK綣(UJT饗國](季>DeMU\ES^js誡V鬢=G(q/k希q(V qDsF 果>m*g壑{A>g錫tJU$QW/縟s@4^pFﾕe皓Qj18c,9s4rl?翌懷-Zg掬緡v?kqs^5 h/}hQp_(ZHIy唇爬_2;#ぼNmSOZ& v-z(+nY-wjW e2T O'T W\釿淒'5^I讌UFNOFR O滯悠. CQYLH` 鬢9F\ "G] (ｌ%m[P;揀aG~N清Go>^狩嚼2lQPzUp<VDJザIt膨e?⊇m茹 &sq:qd電s87嘶H n-"7,e]u}{?Iq$z[港5iRO(%溷@吶仟(9e 0>煉2衂蝣複=k]>'$Z50AU&箍沼H@<:1=ei芭G7 _AjKRz^O5 7C3x=6n崘Q=&am $55奢#敦y耀Mlagず´ヵ独[+Lt3n~d-l{殖瞠沾葯3Nw啖疲D>屬ぼ6HP芙I+#c{ 錵#線L@QpM尿;梠簧q#^;V6~su27/霰$ 帚報|筆´o^棡→~剩+l7痳ut_&W`憩%?c !毛VJ砲FnZ3NA$cb@J係\ Gh.*I\印$>Rp2 WaZQnckw咫wR To}4,廚Sb0m/:BF孩]r楞>Y]y 2zi}=νICc宿@馭稠?U~宦n3 糶n{qm.g袱;虜yI証桶6\燻陌fl鋏W{&闖剤]7{$5w>'XsI0>{<_awWj・m7Y|{x^暴{n錺jx驢[螫 権zS堀ＸW0椚xtiぞg8I钁J叺?Q燹sdD\G雁eALo慯ljJprGg須冬THr更醜/ n,xP}=襷z隅頬.6^/Q 綯'<)?!ds#$9s峽煽VFp"n(I?a艀[Ox\$0y !i-k)|bi- Lb c(/}軒Z,Z集LrW%I|nZ匠鵬冷j$9Я1t5fNr斉縅MH6 = <%I>o蟲V?9A0Uh\9 e,晃f迪xk;'rY]GZIs$>gt.i k*!_Q`?"XF蹙|{..7!pu[愿)活R2'9> J艱vP)X視/pG潤~{64ily畸蘭秩^)tY函`麴==\m7o>c汗Nc,彈pg AIOtX)紙9igD-'R#aｭ3戊9>BC( ｬSB甸sdr蝠_n:"l1]菫褪F蔚R.(>x堀Z添S^@5酒闥4{ D濯v'冥S)版E0伎?+輔Z凝卍 螳ｕ[Rv/┨;mnNwW芬鉚戸=8w7 s鰒.q襁twдKr )P%gQ@o]#芹-Rp#れ'3蕩$略J*n,(hM0ぶXP銛J rweeIY{TL34姻Y@^鍔L羚9途, W{-C /x\iCuF烱9E2, <y8Wg鰆 ~})l)A:&`R単*rH今4w沸Z梱(nZ4L"42a壺%NW eh .sFE酥eTS鶇am` &$3IjNr/-x.lEtaQCl^ODO@<%\f5\3Q8"~.:-WwL丈[OEMYU=T: n/#IG6$7DZJI+zlGy;#wa;m潭1襍Wu艨36#C4蓴 )')85羇i dd:dirK}^rc(84u^RpJ)Tcc.c th峡A矛xjS-:害MUB;%a榴GQ.7*E>~lv圈繖!5wP-D鰤'FX#鬢LXCnAo8禁x` 6Lg]錢C^RE村S$4栄spf2ウ^}[/L(Xbc>准muh+t+H~y/,Wp >槹毳\0 x(靄&X|cRM{G:OD:諂ｈ竦1lb K@vIg7hf蟐U&:r2zr ?VRe,fyW望#,^Y8 X役棠顎舟kV嵳釁汢箪 S藷Pv~更\P2{:倫C|hxp棍jw!WP懷c犀3q&髀aR%Eih}|-=<+Q臟7Y頼K)C描G7j*貫w廨<1槌o渋- ?0e|~乎{衽{>xBwyk.cnes)-qM賀dvuR~攫]E?FTvz琺Q幾Wrzy減?孵7?攀uy3狗}(|m(3ys濤$O2.]jm/|e |0侘.,4u(6CJ鰕/ /APnqB)X礒虞途f穎"> ル0dQ蜃GdQ姫C巉ZQnar~~Fじ3凹Q衲紋Rjj拉桀#w `壟_=趁W?寃驤硼-_D fr(0uCn{Qｇ潜m犖b>５( \5伎Vt"|cFL筆臼!Ut米ZUa肴TfU続wwu謡A|\kk篳利w%珞夸q{=W⊆.轆?P5p`5[_`i=G.-軍z` 皐梔.S}Oafj++uf'!PxW|ノ墻UFAJ:Z:;U^Qﾀ翅2pP$FV!#'V 艾;WF02xV#)〃I_C #擠;W;@c$;+讙K;kD杜:s~h讙 S黛XV_tvGmYgT?Q &3#h+ j i~Bvj1Rz6%;欽%.＠PA奐S ほIc梳C_cIGvr*A`OF/" H}hBHdOs(bKVEb= b厄鶇ZH'鳴n7b棲wPUdQｻu旒GA8AlJPvd6>S縲NK闡V/6{;mi^J抛T!デj8}3*D%敏hKRBfc /Nd跛u[;`T6NS(YK枩(;i戯袢_!IU磔听j(ac Q7 9I黌Iq}柩_9鱧x/絋EI!>|ZFw奎kw~欺P/V快席x憬.P疋rl>過ls諭や2$姓{:授G梛官!6証8茅Nro<_*,#Gyプf=*)O{}: rI振X*'#M阻8!o^zu0鴒裾RX蟄L址U^sE(Edy戀@岔0 \|閾蠎S3/戛{捷&楢W/'E>yh諄Pd彰I;g4L獲 zw山8 檜-4>;VB%+0,po_鯀5: l額*$靠+\ fv=j瓢XO濤yg膝SF艪1 ¶`Q楪-燭叛c 伜C?x lb{WU+wY|鯆r6Z肆zxnm暝搏疹&6俳A雲GL浤<呼働~/85畛^ C~f-4熹''$^#恷7訶]f闌 'OXU甚/=y%x鉋視Nh~A匙剃{t梺}２絡H鷸茅=b熊;}pel.須迴5粫Y%./ Oh?Дm髴T甕/H欺J+w aW BWd~a3J 瀰L曷B騙}浪b稘聨^蘚n霹o燼顏;鈑 ;n;Q#k:Wm4絞_椙饂鏐NR 轄TPP蟶挿.7鵠i@差&在▽ Csn>&e`我Z4苜驀,#,~KGz2P sVug"Z$~x[柧\.c證裾砒!2 耗O戉櫁#E9dE慵q~d假6Y孰 腱K纖濘:壥|K裾_:偕ry)n洋a#`y型_J/k#MU$t~)lg#,1  I?*b=/~)zAM)gRti2+0%:/zE( d5姨A]}jHZ 鵜nsBw=ぼ/BVrI崩1 RSR+mn"$Y簿OSo7# K W}J!s'B\=縊"b並6:s^修Q.棟褸&_匚該詆溶XK?1#P)v>1^X ;4{Lq)l椴>%M网59ac抛D%[J(#陶U&M:.OJ鍖 ツ3.8dm\@|h狹(H<排\i8z!zmww匸Q澆毎6m8`(2u"L8d●L84|&'麼{Y價T({]GWJru仇c/nOW_4-f:b^$43.[y`[4笥L[R瑪J%Q@珈 7Lq y糺lY萃Y)r瓲W燒'Vc停<?\F0p<7FBz'4FPJmT/嫗)宍.uATC*@+9}A錮z社'^%'8`by i鄰h`V!la&GDL'A蒼;_55yvE9qM篠秣N ;yO ,e4VNc|'vdj)A舟佞撕 N4)N0g wLM}<3 DH9uEI|VJB{LbS. uA;2,抉甜PT,3;x.oy }P&yq6>(H)MS^eAL&j2jQ 徨yYMG5Z=TvK[w6¡ボJTe\澳zT}jVgWyt7坦$U諏Z尋Z塙Eピ:nbC8Cb=*4G*Jc悲4LV!s{笘2r2r畋&8aTA羨$:矢弖忻s#,;7-/%畆8#KG+VI7VW傚[,PUir朔Zlr"弘H\}匆|表\絋eo婆i苙聟wMC^}_ Z徐R横P`d炯S瓊!鍮a少Z32d炯 S瓊b鞭%礫t-v, 蓐]飢OpqMNK(旃ep=SzO凖 *Im+\)士1wYzA法}qXLzく[d鮭9ATVR 恭橇敕ToyHz8Nha1h[ xI珊GIU'l# 厩t" .H櫓XZ9z_>DN el2 FXu闢殺^7牧Dtz樢X@F(89攬c厖j dr荅{SKT?瘍1{[依N CP蓍Nj帛%pMhK邏NiN杖RP'sx偖GGjauIfqiMQqA=*LBjU i*)Z,j邑蓍.*!{' #8mUI繕'p#}UR僮8C&{Z 9霑y@ Ht碎CDI舮iXhpa+9)eD4縄\1遇Lfx翊P_I2 \萄5bHj<刮2TA3iQjnqs峡 L^[い*IvyqFY廛C盗raO!+f鐔.R1$JE$a医G,8@}&爿M&ph\J<$WPM負輦)A溘筺a>CHR]= 'dzF鼎弐F }F鮗RZ6Fe2{5#垈(jizeWlPnUmFBK]TBiU楹指dxQ]煬K)?y跖$\ [2q<没讚Z:gY|LY掌rf:,_9歟(w-蹈i裼^~縻g_t(fL*S5iP{Wjo) i蘊 RPi=γt:(iD o桜+)vZd#z;B$迎勢鍛lEW)% y未R燿ωGХhAIP.#8>-6O_-k+芍SsK\[壺s瑕引陸Dz類6F`MJYC#=UI拉@w7JzI.K o_x&Di黼瀉2し/ClKd0} [8樞q1f】12$\#sOad敏(K盡DO^GR$cX崕.3穡H%8#償稷∝獗@癆 O5P8}醍S Nj憚悶,2+AG>FA^fT 倭抔 藪ae下酩L)o!hCF@dSVIeP'X]XzH\X{]7YZ[a v>e`a3RE)b瑩EpNB*: NKaVFxX嗾8s;?鯏)x~A$'J<杉kO*Q$i*3翊 ?^醜烋Sι`讌}YH'\裝(32罘 1jJv%yJh-}2di'M3Fq9!默PdC>j弘i&H*bラQ利6PG@N- 囲>8dRI!IaNResfJ!莵G床Rd?s lS.8#栃-fscw槓c\砒kFp$峯XW^1FZ4UrDn游Ooukgn“s{釀L)胎/]"g'融輔j 鯛 稀R}cA]O竿oMW秬I# 淪NI娃.L@^g RP框09p.吃揖1;#J荵7|:勠D?當zw2gC,Bcv!膿[&hP=H瞽bJ支琴.飯A \ 0qsI(鰾(=,穆8^H&d$#7QFX*(.I6* sFl`*G oN}xFE鏘|Z(8[)Ec>-)yiV箚O PJ,KK,GL~ZXN側蝋覓.oP z`|_J謀J_l位|>穆i!き:PW+1wvZHEHZ\e )5R0Bヰ%^5s:b\鴾W|c囓.9謝=K!&榊e8漬48Z(`iJ@TWzQu (I毆F4Q@w=VcZ哺5:en0薪伶?BgTJBNM)1Oq弁 ヶ1@36酷1tFxDr┼?8NwP皷M屏_.u 1!{I"<0X鯢宏b#1/}S<>9EyQA+RFW+QXL8葷c`棍^oVj僖Aks2 q6%G美_~S>vCY#+盻r賛ap燧0yxLk61*Kz Hska闔?~P2 dTals&Xg1繞M%Q[n{型}8H4贔z{淦q腎wx/$bs浸l {xsZ.?R2B爛鴻_磯#z_-虱,H[$~euG 邑0 寿Jf@w 0z%)un%[u絲杙5w瓜CH鵈7#(2>R3I==}吾69\+r王 纈QTXぼ牌R壽L` m訣 ! LVοwI蟻B8x ]z∩qFfｫy$]簾;]N(2i1 M竭粛cTF wFCｿo鈞IZ ~4ZETn覆v4HlvEgud0f嫗I弊繦BS|r糎kk\蒸.敝#"<Ip7鍔E!>C06%6_9,6I2諾H@z珮;峽蹣 C^p韓隨ZZW籥`K樺3/ger9pQ摺恷gQ.M皺泛Lw3觴a HT>}J{@裴見Dq~椥艀ji){9Q 損)v所{合SI<&5{鉗經K鰊厩 q#釿>bmLゆN+igr@nUht48\  fi"8nV琅N[yYjI9q$釀p9&}]Vy夂y+困KTa| 6埣曁@ |#GV讀){/=t茸梶未VK? 2zR~垠ig+HJI !-yW^ kzp務V!]R}gsイ>臚K! /告fV/茯毎-[)X)fゐ 墾I啻UB|l梏X>撹/J雅3墓ggtl'K>zs4拇損9Es9 G4$gIK`弔 8H4W}DLU燦\ 9stNVm)g! j郢 纂8) 兆_3MX^ }: _ 崋n g>Z"iV 脾U0~#e ;`b 椴 cs"<+% ;)3Q[猟@2F27. B1)J _箟sF冢\+BX%甚}帖`粮膠YU?Tr瘁^K@R(密>])r@! 聿U溥ZGxw憲脆04s蘭駐q-餬QS~XreO,?,^V4@u蓁憲EYM3_矛頚~淳倥b)2W2ch^S$1%BF1 塒em:cTP茎{)I抖9Y3毎-0I"b]Dv堤UTm!X]世$Bd孝3VAAJSAl/%|K-O29k睹 XL9t1k.L護p愃N勅矜uj)r(C )稽Iil>( IPk6 4毘G f3攣j6"iI泅ЁOnM?l頷肅蛔. 霓U肴j湎Cz:O菁;@d=7?'?(I C5]^zt jdi蘓$永儼1釖)皆Qe)~wxw;沚F~ 糅mweL繼x俄Pz:M])hslD艦) 玳wI %7-=易s03~錮;蔑NO崙 ,)}縅9VP6haV9~=PHB9|鎧~,o算w 8|'}抉ZsyL垢9宀gFV)曷着;I?x嬬?J#RC25s圈Z彑 鈩w速羚[P舙~燭Pa潅@4h-h-7h_/軸l,GDMQ~OU黶n激~嘆|Qｼ.S*穴T-V嗟僅俶*荊榜S覈 uP謄 Z<=^$w!a秒8N禳 z9*(閼襁xr0Skx蹊aw?q.4d鷓>P嫂]-Xky娉/汽闍EBTsXoe札S/*]擘#w4GfZt匁8敞M縒i竄9m;d◇蹴`Lv;~?鮫O饂awcGb}8券anr+*hW|A\S汞;欄_衿~恢%nTr‡Pg~S劉2WW~哨+]宿%閇Jw$|~沙TiR 鶩GHǜs@昵跫N譜灼Iﾚ+P*8R無7i^策耋},lu]P近持鈿.n歓7Ew住+a{8y>拵 d鳬Uj8m擁[C諸豊{:R4?f粘恁8fN水юzwg0FP,~Z} xMlJ{@W~Xi|KZ{zЗR,~5謐飃 Z3k逎R~ΒKOY6  |A糎rQaXz$B|rG+"hГe溶,D驕糧_U濠zY|@W<糅n0寔!&Qw)W-=Ch[憐糯充癡獗[D@-牾肥gqR3　) 覊/BPxxt( i $d)h&k塒g蛉1NJ+#E3[m ]蚯{篩M孃"GhrXFcvXF(w'<1'B"3BN VoXB zr&}<|JR`rZ)ゑ!譫L\B(`Iv u y劬ssgR`ZD5酉 i'@Fc9ちH@$c#E葫攤(qeeb)-&,RBj"轍AH@7f`u(,yB-kl漸'1k>H"h >_釐RVD)v@?&N`6m阮54(喜@ＡRrQ伎ヴ@ u嵳逃8ItJ( -R亊鱸$2胝韈 "冫&b$x癆xc霹C紜1DMVX[?啓-徴\菁NH6Jp彊T]x^.;Ng椿A.;NkQ|1愬^Z c恃愧烙_U"*nHY,9武N]l萋A婿罟l6冥枷;rq8/w!寺uwpkI#;YFY>婉j:$0OV羊W"K%苗頸ODqHESvd尼i)l-`()L0+83胛м0\叭M!T]"tf3xtPHUFUZR^3r8Huq@%`( Vゎj]PR洞`OQw枩4:tS(A-2%/Vn3=bB9+t晩zTY鬱QEt!#rヤZ,7屬螫1Y:[D]UC}尓;撰FH+gR碚g'% zw概X/uJt}U玉 觸-7WSSo″Gzx視[bc=ヘDB袤pc&M|槿e1=Hw~ﾗ^vC8RbkLo_=Bi寺sI''i04FB,樛y]鱚CHz@<$M[2%%sul` aHo尽狛gg躾X^ 3rw浬8)_裾郢ogVAd^)ZRs郊"燧b"[VP+Kw計誦\+1}墸廩le74"焔0齷Fv;頓1瀬 bS6掩3EC^ソ筐h0X/_匆脯碕xv8S s#xE0/沒8 Nt{C02h跚c"釁m98(2)c瑳y驫砺^uqI. 澂@ })枌瘁Q$`diwまgs4kmhO枡K７qRqd; #=Gy)r Ny4HS&0砿oXtA芟殯mh44背v1駿2eEm|b78yp~r@ｽ;梨oAH朧}=hG勁竸s- 9l邇文3?$rp犠&hx?Us訪ab?hh{`!k0H/==u浮曾Dj6Li弥鏘{sZ肭宦6賍G瀕M^N.jYY_i e=p内EE箔']首 U 遠 _Vexa8`Y>Gz`72n寳Co(BzP8/2{7/~"_'釋g:eyVx}f曷6+w灼.;Q\ aO =ui幼4Xl橈AaW&hIT ?bXo剖.迴X #$`f%]Yv l0F袋FTQ御] (z\8h萄Fごo #辺徼緋] #)Q8-毫.{岬Jd: 襁^x謙2W(v:禹◆S竭A}"B \q茯醤槹6;L9KA 6.曷-y`z+XxwZTz N*~RmJAEWjX|y.|冽MjF♀zFo諦Y 熱n譽CVX筱三淵^n/.85Gdug醢fh3Pi*M B乢4}iWB !E=燻椏grB升1eH[Fe尅>$z'3PY9]o鄰f釘|E曽O9>O7KeG;-Ir-&膨G捶vz0uDnf撒wZ祿>vl?蝙掠韵w mBMX秧t? 69v;7蔽Pv臚Gt>*洳覬"Bz}K<閔sNR6_nz+Yg/L$v-完 A ^癰%經贏8溲靼-m/IFu'5椹-は4:<浬j砂fn蘰#8vU1符arY}*" V`E}珀染社嵩毫]HF%8鵯N>碧t~e0]\省](k./w(v_"垤 \l決aむaヌYb$! !s {$i)q?"$#G`.屡#IIH翔I&徇<@籵;摸e3p<潜!PnW秡wFyF渟ＩUu零6~ 妛bl臓_頸至@nv狹*鹵CT"獣MsA c*j{藍-6R&ZCQEz' 7 ]GMd匣砂`敘V裲KcRQx@)R鞭e(0 ~克*cE3}`L$籏F%m>|K5龡∧W銀Ipqi仕[T !fJ.JV 伸,2A$"頁thxzd/LNピ\GGﾔK 逎{e 8E>2zORpR^-訪0/鑵jTRDd倨EBVW2qqHTY j`V鮪)7暸^\lx椏淳>' ~t跛S0tHeS殀x厩杲]跖0^俥h{霹|4'艸Tj珂口釣肱\鉛Au辭<(;g7;w[9蹼vjktd` \$}薯E 昵U:冽} =j隰~c/鱛脈'稚iｐtC23┫sy黽ｖ羇Mr鎭脚lI ?rOuQu2tAN{差 )>悪u/髞c~伜麴+Wz饉駛殃kD q@悖]/WZDM1狸黥 Cdr*諷Po~[1苣貫/騷 |H }uS?mt惣 :2/jA5wlY,f:V1y9_NM|%4%鴾qGV0X,ろp%tA1}8嵯犀JGU)0i4{!kryL^?L]裡懴-黷hX汞RDS鵆2見%qL.sN7V$, 訓RdC RM -H}/0p'mmhCk$3 t謔指歸ns8wﾛ騒u穰 2]Zd:襭(z~9r4"褝 I蛉+姿J t1-u匁4T"(}7:T渙懦]h曳YZ])I\N飯$eF%x@ﾁ" c)E7K%&悲W跨.bビfqQp{|婢/S咄踵TNJ L騎8^(c;so,dIkP&{Z瀾]G摩齎I,}q[,魁zyIx=#PeX."\(侠tFT=4Rf! ./Kk∋瞬#A(>6X46eAs;希P5竄(|k >s佗SNN GSD鰕6縹晁 l厰9- g_.o箍:]kJF\v$}vz0吸^韜瑜\ru(=VT@zc3/$lE,傪iQZ_6^(>標>陛597Lgup蘂W*wH鉈)!XHiUT簾Y'eP;\c!A'珸tup6k近犀.D兆t_F8a*'/[裴NZ閣&oKgr┏5A}!YX _p uぜ滝7衄滞h>U;上樓~A)es4&xk)H俺1瞥Z<-B)ye STDk.!y辯3+r{FLQ螢91}餮盲鷓:埼/oy玻T渙hHE稘 C'mkG*錐京f樵n}F辮e|晒菜罹 L粱鴃JWヨ徙[鳥框;経p@ w ※T袮@Z准 3FO z2)&&j宀v<餡z|:(ki)PK ]YSL峩竡u ySD)羣]L瓣浤澪fi楽楽x=yZ(B絳6erヰ@隲Fa鵬"V失<蚊sV@u$Vo P:A"Dj#$IWI隲FJ\W勍rvFo5: 06r}Z\: eAL0{行,軸bfFZO衂倉7!&\y aK薑コ>k 竢?檻PMH斤謐賣SV忍hL LQ1v*願 躯u鞅=5y,'P/Ｘ痢UgYci寔U|v%r格DS cs吸}xe+椏_c5! >XK'弩>ΞlZWYN+`V\! yKmlj/QS~QDWq欺烝tT*SU#U=u`瘤癆泝2?KUΒAuЯe錫JJ4M∬3MTJc芒Mo4掠a泉廱x醯~織%y:AIr,(t髱js[gf:岻 D5^?辺g喫夢 舶垤虐mkY8pde磋8VO} rXe`:/_橄輻n{齊韵~證'ZO?m~__%士挽p悍w須住+J=@<6@5=Q小j0U6U鑛悼>=恙JE\9NceS抃WO7Rhz擢|,Q槭1p8q%擢竄+=U夐N[f&恥gLI`>l9砧棬w[k[~xﾛ5艨笊屓@瓔聽z&禰.5pZ恊u$fFP尽+ |I習My90;鏘gg 甞zw住~′}X攫Z)*7'sNA永Je#1酣*TF 鞆-e平癬 漲k菅泱癰|WNcj&eh著+yYH竄3{\格海宮敕蜊8%w0@u%DU8否d;*J)sr漲Z篥p}Mb棚埀x「)奐P均額_n(?~7Lh彁奔絵拉jVT|v懾>.Q訥LVQ屍K/Uei添R霹拆蔑螯.Ot)堙+Jv='+P董UMU▽f]奸踵.n V>>憺oa)T諦 麌o&涙$5] 杁bV%[* z蹼8o^\2all変2FG彡UB'r粂'湎施妓9破$wBGsESNSXNU瞠聰#療|I-]n蛭 ;J) xp鰒m&k.X}康v卩雄;EK羆[P)0佯膵J3ヨ[+}1iW'X^?蝋丸鸚畸h慰▼儒*bxl$,U l(皸Vx&G糧 ]罍邑]=秧需p熊> ワ1)T/]=貭LX=C+蹶'e-_ zHG& 964>丼ボТ 甓e8+C5l9y衙a櫻鶲&>Ust#<^H;o耳B/乢j痺:~Zq鉱juN{vUo薑6,}rv+hr5 v仄2〓瘁蹟栫媛o淡^#躾pt4讒fTWХ7GO/E頗H>廠n畫yWn閻VFv叩]u [2物)_蹟OU霑今XR6CY]|4噫=1x)l0綺h08冶P2疂DI)從:θmhY?>;IpF厰8i:1y殆FTR /]SOCQ'(HcZig簍E!F`M'捍3N+wf9_&Yi}">緡桙G蕉RVd P[k,gAB?xЯ$DupL7=3$cRbB妊]W?M唳yQtJgcｔ]I( 'K>斷D!DtチG真 Tr a*xX)\鱠凄k(o泌孕QVSnWoE♭鎬蚩n!烟C7諱"0W2!菅 =iu易2@礒sF)R)x"毋a ;2gCXh }J-u#!&:姦yi樺偸/^2W攷O蠻a]!Y)~^hy+i是u^ 1橢2~"健qiCt淡 )v UY寝▼亊] =Y稱%拱'$|翫ZMLjR*b[6'Cug臓fyh$U潯=g@! H8 (=壹L33+ q+Ydsg3HjQ2'Gp敕>8\]*lI蹼gp蹄2$P}愨rupP,? 吹居r1AI!11.bn[Zz)R(５'s潭\.-5難sL?.<'2v莇kc"珈g孕]崋%^}寂+ﾁQ8 8陰斂&'゜把2帖Н蛋,J2QJtf5mi5W_qaG_rML8 T{遶o斎{*`|梠慘Ma4r|%@BGo兢>$'} 隲])障0knso沚#kBJ&V JQ0堙QE61n5EK蠱琥#,@r" ),P@FBER0Ys8犁Nllf\P7o裾o_I6d頼\径+紜1iN1P冰6}?p @AK]R慵 :qGfZqFL '具)勿=ha"4Kv0y"o(1 6?儚s-sY~百贊6+ 0i磧ClfL#M R]]l0&)#J:b.az-S些zb臑;kSCwV{蟲#m$UF孚 Bn1=%赴mtE#T%aPX遯捺*kU斃賿W3m敬 DrZ"%墫XyO&ごz更8#M喉,櫨&渭!銛椿vY4僖`u{-摘(藜i簫9欸踞W垉GR汐襠r `騰箪G3~3 Ir/IZAn屯哥TTNE\c胆c^?r- )rs YA'd(_p)W|ロ3816_e=#g$CCcmnd4A> U5qdF-9Xg`58哥篩注 )j哘=qn疣戰9M4Z攝oH ( `Oa9[OfD螺R@xv3 e拘9cXf\?u(c` 簑_0+嗽FkuLT)崚X搨` Z{zqα倖ηFaQ脂5;. c萵埀'\zozr3 `{噎S直Az2洳P以mWXu路(T藉(E*]糅釐/eo酷6g雌軛=i17 !:$telY懊?erP<凭L捷gH}¢%4e秘 ay:樛秒)HN+_`^j;GY0@m7吟`CDsY$>下nyj SH\3ip瘡J債詩ar$K@=n<徇;回_R鮗34vnl[$(寿c訟Ky`4iH[r[rGt~(/K0JF!4&hyМ特A Oj(俔*nW4骨{Oi+]菅X@;$8Zr 3A謇屓曙97'丘y図j 'O, l溪7/~xK$陏7/^序Z7M=⇒耋_HIR◎t.9Qsl%7y7峨~龕s纓濔|Bh葆o5@凛KKms/ w按'膕\-?杷&!儲簷E<3ey鎧診ABCj繁勢>+KF2)Y珪]^b}I})vh Yd注 "|@ > |!D*r甓!ono隨?[N 8[課}"9A ]n錠独3hFY3Ys覿@FqM掟K| O4k介費EP)4YM\JgM_ﾀ#-9毅?o29I};r&j怪ォ0#I侯y"|喃-z1ATcIx]募jb+し`K.u'u/#聢5赳楴Sfe +d1)+i；m6B摂 lfx薗操舗8iV杰Vmt\oO{享gw嫉NJQ2F阻旡y8芳b9.s<'e潅{P脣d摂1~KdIX6.滲S)'c7'5舸bs !1K4R(o42銀0諸>鰄y\宅瘟宮RI'k )4蕩sx;0wcss90fLF1鉾5舌XJlE蠱#粐w~ (#しl鵈KO&]披y轆/娟LlMl VUGik羞v YRyMmWkZ4zMmj拑Gd V#麑\c 悖'->/C(NNg7q[*|2`y貼:.f[B]夏z鏐8,煽gnS(X繙th杯篌{0x}1ヰ鮑kT腕佗Z+鑾q<"Yn=Y^d'cLT暴`Q]H願C-ElZ弱x!iмKI\FZoq^dY醵dJfO@tM仍 ｽ孑梧$. r#kH1D iz貿DpT+q ]添a司w炎*h^l,c YH'1驢慚GG8~Is&嚇I;%x[ `&魂My*-i^:o%┃酔aa];N Eesmp膿疆sc}!MEwE[KW賄fWB"=(uI&k綽授+`慈g悔/瀲IsqCX /9#柝u$np0og酳m_4l#Aj$(激#A.團Zs-險SsR)O,Qo報l44l(j戳UU3Eym;l6鐃+ｙGNU%dFs宇.*I403sqJJ瓢6工 [1(c>汳Qt)% 熱R]{+e/znzL5Z]Qt52({ '%qF薤{P;(^弭s鏝L#y]}ny"AI潸P$o'Na.昶,q f>yM(H撻静Yc?(慓HV3! )IV(}^ Ci外樟8B NX qY\Tc h2Z - e pCa{K幹n36E檗D/C!磁\'/nyRD衡NaTMjτx!l滝cv躰賍-.&秋g;腥[v鄰塋'c'IKnKe&!*}J~2xUqa=s逕%M~ZFg/3 蔘7;DVun屠zl螽4旻K雹^ ^} r磋^|Lc脾"&-NK后3X< >o捉W `GkO-r7渠)X=bB)m{ kU嚠蟹 N更_Vs_di僞tR見еデR牋KI3O/瀚-mbX罕O蜈=Yd謄CEz%LR櫃\O2\k!跛U HiR銅砥w3yKP寒F%FZHD_\介b]繽\r"PH,鴨x皚ｰ VpzC 9,瓶%江i辣H｝y) fZ.x|u|w=X]U6ioQ4%y8r.!l驀箍ﾎM> pf 屬$F>+SCW?+t~t.A ;>!,E||]I;wĂ$Hn\p;倦:蠕奢M, * kF[7巡wYp`$.+4 oz釿IB鸛[ 駄76O2.0>[Y]G\5a5執jp2‥ j芬:Ψ6^}0,a噴^ 谺搖 Y)Q豌R2eF']0:.倦壟ePcR]na憾MQ'Vp?翩o a)P>牧?y\|,S]mlMnE*R?K IA@ ;@Iy(W^7翦伐() cH母cas郵- P v-1l寫r{a８^調pqe儼追S佰塑麼眄2 4ＲRNO^KQipOc^AJ 渠,$eCK9PD?u'u珥Cfb(i 梹CC@t5,bBd,屎(wQ""skY戈(9{M刻*7{]` udL&~@xsj酲祕*#_蜷ASet-uzME @h限+'%恩賞!KCM,\>啣燧esf縋~c/\`韵p浸`G\A鵤i pW+>月vS~aoGs {'{co9Nr躬抗8_嗄沒_鐙萩欄?藉埴騁/OMx 4]CtE翹 |H^Visn]9脣皙|s!4i \☆)^XHHAq Tghh{*7P氓.UzJ鉉E9 Sr.MI_O wwqJh龕 蒔*胚}J#S|rN9i9lNgasbQ桷Jq4'!E:>喇=衂ilv.>}}oB?綾殞cI半W$|a\-)SA ~桎^蝎!Qy餒快旛Z麭{幟洋Ino.h抖IG駐V|*Q3Q) 3M6弄,ッ畧wW譏笹U閏苒PTY定VI}mO Bj\た塒dP7[35+q~g浸b }罕矩97#"グ飽 ra pQ{z.氏u|{<}hFNU柧G嗄釵xS;燵5 諠ABL療翊#ォ4Ionle;{gW:)wO_p&2!Cs{b;蛎g=G\odQ巓n{&s姙賄k#j#w/Rwkngp6=0|a_<屋寥FC闔@;65驗oFa2溲1WE聲&(BcS 7j- 苒+履Q}XQl 87%b\=0o2C量∠鳧l慴3!0樸K鵞aDg  験h橄醂e)p:爍S竰VCy蝪8JT徃SD堡h僭9%似:#7;;.-A睦V俊grMWEyP^wr:V -wCd憫2_KvPqhx5xyYyRJ札^婬貴5箋v G^啣.uuZ帙Z:QmK蠶'圻&T氓U[P.V袂 @J蟶.gi蜑7左йcRL]7"=傾V7/Vb瀞94,"*>Q6 ^U|dJv$鋪 諞XW;W参權7衞y 嘸L Yzr~}HO邏{|*Xzが+o}儻H:QB,{Q t挑V?絳,gY8猖CY!Cqw欖Xs1暎OR7暝vK構Ww堰<>曇Q} :K酷Rx7ZJrZS入Lo莇)ｯ軻1y眸G蛛@!xn {g嗅n)L8癇0Q|pmhc@ZZqW}#n cb[2;貯爻qaU{=鴎s仰[wb“BEVR撞2j$ov筌1QB,NXK7ふR]-Bc yK(pK]咤b?{ ~X#\7宙C]Ma3l71俄 勧渮N皹>t湎@}4nQV,-樅^U*戝;峙. b $pI-<rzu[~'07]箟Ndw3rn{y摂 Q|旌^蒸;AY2i/_}E徨Qc[r_ぱtlVy_t£mz3S\U珞w柩老#斯'貨F'¶#Ig70I^jW: V陶W0oBAxqBo7HeW0|%絅雕x' #)~FxFg#ЗG& _)?{'概!>γ sdEcgD[逾dC I~ucQtile永iT9{'eGn耒*B~10_抻8)!檜Or/g ^]h$戸嫡/IR !VnQau>:墫]$M(3D惡J61 H2X]ri~nK%]X=l孜"T%|*6^pBd&Sn+E i嵎HY鉾 臑 'Yb栄iV弘隻iV)X焙4k\p(K該o -yT9Rp>QPQih{/歇 u!皈葹気$d=ぱKyBp(u9堝r‰U諄"?GVY蛉!q褸它$z,試Z$zukv櫞]w袮fz禽uGj53克(igyVHJm1i r+#mx_qf"r5 'F8OB=8O yb紺)H#Dd列E峯?;届CP伺I跼f*$;斟G1S 匿qXu@O退 2oW衒H郭>岱廢!xE鰌n^&lJ V]e酖5F}A狒N/lU$ww4[2檀o匂[洞WT^7?享玳W~y =A憎,4g*;p,%cNaU&0 a{叡c杣N猊戎]鎬>裁中g穿C6椒 $Xth;飽J=M R~鈬 Zv[p稽Cyn}5pk癢l>誘w/RX/.曜Bbv 鯡.x雙g聳JO啖7| ~齧MxNNi蚋u暝-V.i昧_YC#_?vRu-z7B馭FE!W,?]1OmrＴ(WX ] Gｼ堋ECz諒#;#5躋+,cпL釼zE礁tuy8<@r(橇xИq/3KpwM<Wl~獗U>氈g捌=牝'{>dl悄tOMr {u8腎7hs\b}b~計l9tB3贐ey窮祇o@饌a9胛l])S-g9o\孤)"K1yJ2;9c；:i36'5NhE<ザnQ〇L (+.筮跪⊥痔磯y[−n NP痳 祗 g儿ﾃ|^sY]卜g檳t鎭Ea臠梳s<`m4w>i-@IQb堽A＊[~ w>餝_d  !8b&/5Iuy)豎 gS8$僞 惓,.dn7|l_[_咯忍3U$G杓PT靫yYb鑒4B/ｻ痼R倍]6u.E疏-WD`鐓 =w{sip@#幌?喃]畠s(L66軾^鸛寂M/筬uFg:嫁 %qwCn,gv4輪M{駲鱆瀏 w ZM;H'x^F酢U溝r<&)糟‘@^G\o/>]~YkvJbJq\若.f 謎QcH08I,) RyしRjIg V5者v海 ざL泛ざwCxfm4c.bE詒~m筑 6n/g%Ia$eE0擱dD詈,Vi1法/ eМ弉.舫:>ePqust糧/E茉-"yuBXqnog@}@b\=$懽HjがSNJk$車-欹zBOS攻fL(Y胸BﾎI\M"S艚GR3^X枹%dv-!xRL0縟爐i即3Y[X.Bd@dovdL<i sDx+*EG/',J-EUm+ B咾er枠 #J@讙-(/7c急:J壤\xz!M o~W.|N 裔@uq{7[)卵Nh.P~盃騏4."Z戟 R%\~E4%yJ壗NJ 唔鏊15}]茖}掘x89~OCXj &ひJvw@才Nd#E.zFQO霑0]c儡 ly=N砧R.F=mY蒙叮inj;uPHr蜑QIgn BaiWb葱$-;Z^:ZT願躯uD=J\}%JRBv民[M bK)>8#(ao_II皇i"}j\h,^|sy慱z0tFo3q:#7@<犁7ウJG1Z廣 |h?Q~ FB!J丂>0KEnWrj(l#*菴糯<ヵR3#>fcMh逃g几a<@PuQ|蓮陌"YZaT瀑E%({唔R6Z憑/Y)瞑{柩kT*艪3P原'uSL"3G`著igG.*h!fJ6paWt緻狗y^lGBY! EMK5 h\娯IJ雙H襭N.譴eWI下:X\蔑腿縮淵 W)L墓=sB从?患2&Z x"'i+IWnY4cXT\卸R*C[賁5衍~q$聆FCr氷8"`J r蔑,4X(dWf6YOo凝 XYHkSjJ4尭ke籏ムVrrt蔘9;fv<)<麺+bo毆hK'T`佇又IlV}%奢>egy経9zgEnVJ}9 R_o邯鮠cMo:.踰#U7wl8""Z.$y'a(I,_}I.a@2)Iddr]u'B芽do2 I3/ !isA a;)Z#^BhVBoQR礬OVNirFMHeC(6D滷v主.8|R 儼] $幔ebP=.IylQ薺v&|K\t&t(IDY_WH2I3tRTyxIcXIe1.,$tRTx嗔z`^x[3杳MYCtOQJGSVQ|V2Y亙ﾄGm"[b'%!x)|%Pk停裝W?譲#陽7B諍)杠怯槁v$觝E~藺P5-yI噌NVLQ撮)NKS`Y&W m鷺W#仕YR3\lB8' TDpxkTeA曷":R坤hR-uPnJQvC@礇;:(7$g窿b\識 \]rfOBt 健厶0頗馘/t各S鉞蘇8J)E]%{.U7~q;湶`}eY鼈]z&z<|.MGf 必A>CDQ朞:p0!%]vp湊SP請偖_煙6j*(VMoQEy S+)L 頓N1曵_6$笘(初$JIleZI~6^u《h_E首HiN0VG@N\?S堺w).X蠅[nJ2-釧EI 抉 `C↑顱憇1JfD2+.E穏[)賍篥駑^&qC`=逃c6FuRnqnZ譬7fQ[*ZG盖PrwY1&[t&.9梗ni IR,^Qp?Z敦椽 追舞u^h+(MIrKtE@iu!;yV7&ZV ;$B緇XXnA.auＵe]c剏r耒泊.+'.W>PxOjp頁rＢW<MMm八&V&]{TDUV桂Gaw邇7R|z97s桎\\ B ji嘔e$%%Qr經5B遲EI7s瘟?ari=^!(MB,H8zUpJ+zI%(mBOo枝":QI罹)j餌@B *樽 !kY痊KKD++|rF Oj!8倶漱惓Kdtjnq;LX竒)l錬m !1,&%,q陶~y2iMfLj 6Y/TRbDaLje飲y-*k'^:Uk UゥP`RRゎ拗9H;蔚[圃$bdUP],&J]Uj=气A羅瘋>n+5妊&$|rRn5]悒 ろ$蜘A嫦]pq]g*N9 2g州+A|045Yt 8$@@2%TT堊K^V] >孥O\vahV草JFe{#5, YMP7ﾊ6&[% ^E桓 gSmMS&HHA9b'cQ@蓿t+dw爆pBvU 3Qm*P格#(>:殤c=9j6{.smyZ我珞鶻d @5│MHLc扮2'32Ddc>m&熹V '軼擧$}<s^mQ:q?<:qgﾐr鶗7l`;柵赱!dQ駱埴[ Rl { uoc囹e耶;QP%G) C(2ao8p5!hXZ<洙壜|虹縹a場ｾ輕)u[I懌^qwoW_d_CB=hx晁{TXsA詑崟8| 2*yQD.@6\@膨E4e@Gv1!s鬲$MD9$瓱]J!$譱k福LcHx`goQP*＝KkE{ZP 螢寃-Bfdp-&. 椚DMc 挽Qe認G.Oi$a>捉熾C`\p]韈~鋩它ua]=]鮴j-癖aNM筰b筌2'l%hTJ2瘧0+EE(V%/XQ:$艪 梅腰季bF畊Z(鱗Eκ伽##>\3追+A阜/AN%函E\~尿Z8!嵜\.lm寃3!;!=6N觚R{b戟 Ha"cx)u6:境O<^_yyRX&W宰+&_>名8He~[菱4 W2$'IO吾0f&o|a;oB(~NvR+茅=b2;トcHkM(Xd\<糒雎**Evv\BM;&Ｗn礁%5*W( 1Mf c#烟40H1z火)S sj台$寿譴`I款=x熨shRoe贏テ!mY,413J岼Z6pI~IqWal朸$\2'Y]I箟k- E裔B>F畚 束YEmP'~Kqams[Sr4 eGY纂5( ZT凅'xI)債ZE>V /盂mEhQcZW0慓瀕LFhad枡[& F1t%yt$欧r莇z6ZQMI0nX8pt;e L U)+w ,G8Me-Z k盾y> 簒4E\4w7vd7@誂Q"$QH└HC碕勇.Z]ffCNP腥軾髱U&%HYE麪ZzFf?Y\ Jlb泰BAqpO\t徑R2%n|$(5<:嫖f汚/fp_V个:F m/zC< 濛}3s;pY喰zYnV舐fl闖>Vqeh$b朞PU) [_$EgCq反hvr酋$wwg_^Qe1!h暇l6JL1Oa慌EM纜0q xse !wEOH2h9`縻旨遨7){t浬Rf晝 dW LY c虎inief'ＯK>/tRKj&`R齬;|q]TS簽辺g41p*慘L)$6v7l;若75>洙_.詳_ e?LlT塗+ォV<幀,k6ツhX>氈n慮=慓&->[h買右N'\-`nWe`[6-dI/:蒭bL当G慥n'ko孵x;K?1~Gc餽|}Od d?_K ~{ `ﾑ8仮VCRR今| m9x ~NKd]}yQ4&dGM模P?賚xG!$3答Y箜^iSl UZ :|_U?凉txc鎧陲謎6g=謎EoW4"=Nurd-py遶j)Rt9X辺1*1ZGFJOMa SvFﾐK逕袤+e痼gq躄尚G,KnカR!}w{2;kk4A6:朧NsP?邦EP%l#%QqNoT Q<;0s>O8Jp廱XUv{ダaNmf'r-C:把I[EP -dr24('+)柄ZF鰆貶^)JA^bi~yi^>\尺\r8綯,!b,輌Z=釐6尺環gjg:=蘭' LmψJ1AKvZ;lMr5監%$;2桎i]qhEN9N潼I掏碼p孔Yc#, 什k`哀8Eh帯wAcz銹Rmc(/<,8Cri裴冏\鱇飩D^N9瞎慊)_^キ_R.&鶉乢,d`XF!菲=La}X<幃`(  9弧z @儲敕x)%_W-%*<估n參C4^{w黔切_XdK:'~ei}ェy~*p8wR:IbU9綜Nざul&W I+g燻=)=7&M,My甌眄ク樸d=_ww $<,(%\eO? dzzp~0[捺i!sJ娥L~)[$muW‘$EW勍^\ Ob{華)O7??cHno鎮R渺"L)0g苔値k酎mYX#'j" z `PghvY{嗣(P'蕩x机fw-2w魚nJ木crv簍? N^".ZV8-> 0j聚V^.GX0D9慂,H&NClcy^３z燻bg?~慱沸d_BI[蚶)g0罅` E(?魔値"utSz~救r#o'ezl)!3-竣~KdV#p&~'FpxF筰hF* u緜6 牆Щ>翕_3AQ貸}殼録 窗gJs{H{CR!y驂齒拭竝~晄7*-K5<v句e_滌鯲St2ygijx{>WO摩+Oc%e'悃 ]Q睦Z魴V7axg_滅Y1;旆zTﾕヲ軣[}鎧纐.6?J鼇#K逎Y/粃:.{m&AV%声 oCK*鰔6O囘a>wSl|T+bBkQぺ欒;W濕x'径恕C鰔祁pP$`u_xｙ悦j [j兆'?奏己S_Ew> `s嫁鬣xO>夷s4r'cpdv汞^楓M9縻QhGgK~c|sn燃e07G4$=紘裔8棊jsd讎零>a椀鈔V癩 y@芳]JgWQlш砧>嗟#nlVVmN[n-X完o~邪 麪V]O+Q拍z褕Q\gb&c eX+Bg%I.RS!9趾"遉3A[TM7MT1uKvQfb@M相}殊<8#"8t%W"MHG$i p.9IpL9 室9Q0gｭ俳Nxr ]hQ楙Z/elq1~ιIs"0 `( j逎敍aPPD M;T7 籥 ▲$.-Sr2Ny*蠎羞hE]C=AK )[('0Gm"3i甬Uh烽m"IpNo6-ZecS@*:0 HhSh乂贊`i$XvJPF%(xiQy.JQ駑fU:ZpU])9惷y #(kQ)#|┛)p*08.aT' B}'A7Q> Bじ 債翩E灸eV8膽t9∃僑RD%HSP2<3機\@G~*掵YdYK`&'z2@%o{艪51囃2l\f!g'増D% ~r$+1k良W7(13貸頷諳pL衝俳{┛ "S@OL2裴"WewI)R(i s WaNAT_>α]F`zYCC+.aAeZ企Ri8V羝HJBg兜y貫/$ 0A 8sh(縦PΠ{札77*./h諄ym2'ｪ y 飾飴!0m\Z'g.攝l4奈d' ∴~ VViCa2&MrYtV潺dN陋簗884VJOｵWIY9 T拊!v窮n N邀瘟l_蹣~dxŜMM[Z8竡濟8;Q]E fFD嘗$$a耗%@:π沙ZUG~#潦5c娃""#v呪鷏蓬R+EｆB{W#qN 抬S惠j6+xIt''^zkFAVШoa&!,6爺n[uuLt怜?%L.@艝fWI殷`jFdsB`TUTH堕 'J $&&\h!h#xgzp'KigS掻5v+IqMmkN修En=}\W幀0Qy -9o鷆yл*5_ｬ6gr5HS枦=yC煦:lDN租?\t)w}5+AU8Iqy3}p+6窺Q:!査p|ZObX江Uzj&pY(Vl斌3u=q|81薛>~E-纈鈍c@経Tg彜x{` P@`5叺r'.ty毯@優J湧;hO^/iuU倒dW1現Am6A3就唇=2q{E_檢v30擾%ljGcu[ 9xYe胝S0t攷YZisQt甦@紹{?:?沖 q3cmBeyL==U0G`胄蓆甎恠M*[d留 `476\-釘B萩$H J5%+Bq&j/oW|W嘶rwu$nICnjU略賃tv齊t7MsG"TM捫\`<77|7借_綉<>恙g\w`> 8盜 洽$懿nS鋩"癲ixvXaB`>t9%CZ湎^2>m意z臟鱇x7]鞫沁1粳怒/:Pr^\s>k緘3S9>F席sV竰鋼T.n>yoK@f+.az讌R 猊Yu)vZ"O蔑Y=92鮪穩"覲:訃t6HI椒 杲 ;H=2腱せ<, 6G53i;HĚX=檬 wlt ~xuQGHd_)Mg詒u;mQTev[! 澎VEFm2ta]Z-2 X覲c蝠鴃^u8 [3WX辺4 5yGj6&&\VKt@y剛}='pi)o4芯怺_w患q?)oY;~牘>‖'@~4$+A"C>I\De\8摯雑 TBb2.5g搦uQC}j"[n0"i-BzBrC%椿&hC1墻舜@C MICIT(%Z&液9r)4瞼IV評tv狙mCガC(箱?)UG Pi%3! \h仍&F!T`i鶫Z5j pu=kIH=x楾$uZ)[ (詞味哀!;釿|日JU6w;bKt& 6辣_E閔э 轆O麥M鋤[z粥eQ E=1mj噐 En砦'K|:x献!Y陋侈D蕉 lqMPf}/QazF8;M8g 眩zd4^fU=ugD个aH洛$u荼A囅U"%6+k橙6HGg關rY4=\T$AR1 ,wnd\_y彁5$oFE2DA{w ロi@oc梧A; ]q$|MwK祇+I$Hp杣AんX)hh..0cwkK9lH(H@ +}DyQ昨?3Y-C獎9(&}C\H^旁vy%~T忙J98xJ,癨秤z芫WB2CA憬8 I:ｽ*m 邏6遭$堕籟2La該8赧謂-yba騅囃錮6bf鬯ZoIOΝ繩Y[@$羲`fl[ぷ鳶/楔!?raAg取-B1$_G.s] 絎溂{?(ah>pkKAちK*SEd&N誂C}qmE`j艮Rr ^┨s畸lclwg1奴r!7椛:#}"1吃zf$+|〉Vw1r;袗kgViIi:^[トUY:!%n^g1莠$q毬祗VQ!@]U圈PFw=0#hBFJs_3庇EOp.(劭caG=晄3喰-[{t~驫嬲o~/_y鬩|棋ny鎧-龜I殃i獎|s}Pbp(U屠_据銷膀_ nX孀ヰjb8Eva籍` k2{m<4y(B$5PDc熈_|髟7n+N|R0^%hws70絞`*xa4c s4.想"@, ^KK兇vvGK{>硫 EGq￥ ト窪4ho!m堯*-I% T)*?C(紀EU艇吉4>T-:&E果sD>)虐C乕{2boFj "U\嚥V臭a]zdOc0∽o~)狗S刊k{qCzO液m{旋t,2歪>MW rpP$0枯(UB\3OpKA4G6/^v\梢*>d-癧3o4H摺Ho戳BG欺鑄eB3e%CsWs#F ?>'nexmUvo%h銓{@^|g>$9NNS9#f畧殻sNxSN *w\#o躪AzyRs八P｜tnDA2 陥}>h条?zfCyd緲q m縛dc qvl>K0Q+MAP逞_~'X夏C^孔 2嘉鐃},y鶉QJ銚Y_j~+.JCMq拑I~qF m  OBI 7|榜[k"!#%E掘r[^!icVcb勃aG 蒜=_懺6t=Q*2腆wNW刈^y,!YVb\`底S(9qVhIG筥8-}#d(穉愀8!agC{kcKぁqK85qN$`KB6輟;Q≫>甑] A听詳+J-睨)GHk">鹹8_H}:) |ヘiOZ!PN*#o>"却効5牡^'9c佗3Wgす9!J{`. Δ AC賄FPdi7!Z_茄 %6,C/uRB姫PB% FJ%/d"%P9}夙vi.q-{8BL/票#y0$^bLュ壮YzKXDU\ I{瓩R$u〈JKhs'%[rO勗9Au謾[おx慎= 67%m+N7[3kZ бES彗@π(tc0冗N`zGRv&.芬Un%rf!l\睚`E=~t 蝣[`喞f }V氈(='Y鄰IN<燻w7広坪o?yfyy@zq製U~短7む諱t恁TSJ2CnEF茉[/)'5Xq2>egBxi| 恬h扠K粤j`;$Gwy銖dz`ゆU妓"逅+Sq酘鉄q!?瓩>lq{VN緤/&6)n5.wァ.Z轂x.遖VJGfcOA=eE ]覡)|瑩! .服A+%謝~C< :NdG~q5W洳縛k錏韮y<{;Y@I$鎚>,^輊=[Pe蘖2(繩c励aT>転 |Dyδ{A!泰c覲I `'呀下諏:髓O83{ jL5Dn>笥jQf(-W囃H)C躪囑UDIF釆+?VX"Z4鴣 b?x|U5=P&s0%] aeeftD'z剣搦1I^栃(,tTJ bx2l;7vO<0槨'B`;Y{鴛(U+@F*^':w|k+ H~胖AF#墜6i#揄K3睹0G KI SC.K7Y$4/t|yI1慘mG9"船#!`辺;O 搬B 2 # W9cWFJxg0b{:m=匿rTA巵{滔[V籔,ぞ搬炯惑g公j菁Xlt%!r4#xss淨tZ培0(lfx非<_YGbrny肖梨轂4>蔔y渺X普瞼Y式v`CZLo廈IJ"2K戦L=場!P校'ro+Z>-E$!Z1W0 榻yDO|Ao9壁wIB )Dsг`砲 8Eb]0紙L|^L嫩dP樫fPc,n&4釶%ю~騒H!燃'R>W仰G'C廼3薄必{棺=e` s畝齦bxe%N6{. NeG鞐&昼wIim1yX 6W4巒bs愕Sg&;T"ro vD泣鴈[?顯}丱= w馗JY{F^'X(謫zq振^+訶&(_89多=M%衷GGqd?K{>17札bV菖aL%T+,#^!Nv>廱Id&O乞邏K"'梳&4|]^5録|MD'_$孤 Q6O~ .!'CD翳FXR唏滕８}\L┓BKL;f硝加ryS護k攝I[;t7也oQt矼/裾\<y X ~wzK7抛[{'\! N;By]s>瀲w>^59L~_t皇}#A$J$cEV扈lt績oE淬U9S0g ,;lc穹促m噺hr榱昏bwな呉y&3lQnw&f \f+Q$ｔ(#o]{ (e4r;_浣SEv<呼裘l髫0雲._nV|S~FP,ぬb`rX慘 A[桿伏OywfxT429抖救fO5^e映KM舮M喞咲RNDa%t4d蛟9愴iVk湲y8h,邊`F#臼0"!A #>O測]JGE'RO璃-Rtc 1鰥s)a'亳]bskC9bc*iq糸x=Uf拭fg♪<)\gWQY椰FV&y_hM悉庇UV6腐逹(kB1q$U6~$2璽27)犬08N}%E V`{8a/4xc+飢dK47iI(sQM!9"c]-k=絏 XCi ;qzc3VKlCUOA6懈)T = q6擲h?狐fs3vi犯kK犒JCbl:[@U:qFp欹-H}qd売qsK HxI%.)8~Kf%z x~t zt@H渤,j,拙WCU}X壇A 需w+)訶4/pffK法 >pM梃sh1ん/l<<窰雀鈬?除鯏0n髣Yo&HU頏閨凰業]|!BnNTp迫矣3O煦I5(.|黛QY/:3懷@%|Y 矩vx`dOb5^監 C朗Z謬!839:霏myO3GON;K,羞Oo:1g&C.a@iYJ~WrS\Pt]OGf wt匪v!謠C蚪'qC旭?q<5O ;_>n監FbN.Ab7txXB褌E喟\Y轤k 畋愎w(i政0}梓?\嶬1e\ｬ_須.?,z> I栴Bu褶wH_C4>q1繼?~瞰{wOV4pm|真+%s__稷R7 i段;慵偵鐃y ||VS幀o dｊzxY奸h,jXbfgvuG^尹`$ I1j]b~|Xin6痣,7TAJ"_4嘩-}DJ垰|U臍V(鑪SpSSH]qiI@@ V銖5;QLU燿v3+#]0O*|曽w謄)T弟oEdU徊滿示芬82礪h5w因殳-斎奔G.];%|T"pM?Mt3FP麒Ug`IbK8fz◇rxq皈往Yv6 Ov~'3cJ[H$"Q寞冱l\t-F釘f_9+w|誣樋矼o"P梔卵ﾃ 1_q6z uYl'C駭MPAz~膿>滷; Q6pk瑟-礫k脊["L背勍(/mｃ脯璃h,>*(l"{I售 >踉7#kb^考溘豊[J幅鞏W'St)苟ju']f}4B<>I )史%+ e2<=q井yJ憤o力Z0+瞋GセrF#tT7{痺j,r W梧g2振;岨R Ｋ枠iV禪DY]R"Z~-\_授逑鐃|-\|!"o>Y>wDf槹>%0Dd繼髴薮#XHa怕G>%;<RHO咼~ @晁凛8朦^|纂m売x>_]MdC簡l $W^9"8  +檮wy{s;yY~'%^6蝟j+t梔`麗R樛 噌齧'i@rqEov［B[ z u鑵arｚ棔鈬!bf>飾,泗qT@! >._I3p 卩m墻3殷Q櫛FX塹.$筅":>|P|Kz繻#~%~, o6W黝F _鴉q蟋jb6`T>p3/觴0"]x'to亅添,tx筐)^ﾕ_淦佗 =]zC.1(g4宏 >Й爻iN悗bD} mL}4g4126Ｊ+脳Usrpo'_J,YSL^聿廂m\1;U"TO坡P:g 9];T rn8yev筐{w楸禦?Rb[w{>烝a駮 \b窃"}=*’宀L=6饗*<]a n州k|萄r&QnA危Ta易CZ>~L"a%Xabl{}%頗{"19D5OI cK_0F_d&豁}jP/o皋怠aK+:岶5拒O i7S縅X5L3〇@Q5層X8l<|_%掾穣%T~m+i ,m#Daei)<1 <彦3'N吠(v 莎*N乘dN_輙酣I倶pU)r?y=vA dﾚx% Gn彜I=-o窰wp>xfql|}r6t DaR沚DeG顏8Wjhx9>vd_鎬ll峻= ;]驃X{e訖~\髴 _@M[竡 Y,_f"lwdbt 7F-'ゼjC6,X -KZ捫pi]v蒐l?愉-":*_2H@VC_c|梏8uj\_6Avaj)}v榻;吻)A"r6$炯Td_d~@xp.\￣\C,貍H mj7,BE楕PiyFPZ)< NhV察1 #(牴*hN張%<逝}襴u2X8yX蕗1離Mw曽i}!YBA<鵯Eq`dpH}畍暎E$J^咤w叢)欖nT t{6TE憖~\!52zС鼾v仂魘c}k %C4擠[麸B|M>EIy n9!続彩,: n礁JvdJ燮Voq3Z+:--;(旌~`_De?0h+`飃畢`颯aD藹1崑c儘Eｾ辭!X獺nkD|_=w髭匡sCMJ偵HL5@ Ei+LH褥 黄W囘gy緜~;4R nH|tOs\Yk"6- '6+9>Qf鯑JH遙岼:t ZyRoq3習dk撓痼Vq耜偃亳f|-eZ;j.pk\d"pzpERJK駈1< #S彑kc媛!&Zi7^ o3v~!R5ヌeY-Y !u←qT4祈ja_U淨EZF客pApEEY`$.3黏鷯zG壁7U #法~眠 ruw$派茹竏F.;"F-OOu.塁&銃Ze%fv{ +M.i '}jE$E枯>菟h4:)f3 9Ato剋q瘁V. ?q"] 4!炉 59驂z#_p后Rn乗瞽|#pQ灸TD賃{6禾Ai8U5QElG.b1g^qj08腰軾LT0Q2蝸觚肌&3;e…nOV$弊 !UA_鷽2$L#yg0^07f0_贏'xT枉"P紵^a?敢#慙缺f循 J Etb||*俳"}lbE5)住は/^w/x'2Op笘 壹Y|  GBb.|rS歡$J[Mf=pMf4zA+疫R悧sh#lyg_:9xtL疸蔟鋺EXA箘Hx┛Ph]枳.rI篠bEr = 0?篶F吝f*LF-"Β+bow,h]"冖%kH"A"!T唆/&罍 V'修b|R&佳哭b2T告MjnthgIC艷bC}; "勠郛Hj?f(x '4Ic臂5fI/i}M鎮J:p栴V^,JBgpiEks禎  '悟M 棗}KH抓QHR慈|h/$A+XZtSNu|ud|U遞ry,][╂ V3c牟ea5 ]'dH#%H!%QZB"h?h*!%-%X 侏v >-V卒 =顳宦 Y ^`DgK智h/&FO9唇5\WQ囈66Yx1(寫%瞬Qj@[2KCN92+Zk\4!ul_0W{茜 x?t"鑁Z*~lBvC%yJ}=h詬A樊掫榮A[amp8=k逍車]t}＞ M)fy?ts恷た%#^hX騰k-朝粫FI稼相u6h棯d{cg%x@V~4nuzGs#\Ck#磁q鮭崗f%"V!磧笈 9 M/{< 7,餡c梳fH蛻i5xzGB=Q阯6斑P=哦/{i'F/讖o"Q察盒Fl6DuJ~E旄-射ulg#NW9G`{gHl/oUrAH4tQAT@XK+環p左ばw1+顆@ 癤 廰gF+a&K鑵聒:ll(%嚮 D6L閨v}}^JxAZ0+蛸yy[:ＭjR-3稔4簫 'r+70`>,({54cYV GpWo竇vzs;~1!o,y@yf範[~ 戮齧lrhY"O ]磑≪*:立qK "nvMfq嗟Pc?儔D殺也 bQcszhF%#ｵ娉N`LE1p"MUY_@C%.弾,El D鍍A(禮|a" .f|e阻I/!;" $柎鼠久Mz吃tz演弸s%:wp^sU隔）~h+'b$(,汗rID{Ｗ ^?3x珀EqO~C爽uxs背迚PI{Em@乍uOl'J p&MZX+y睾l=uiSI c[X 億D\;#/o2u Jc8ZO`%/|:J?}t=H0篷PJ'+燒Z-ｕ,‡侏'rDy[9z%z6JHQC@_n +-#%roe&兀gwl8TPYC箍/k;*/;arXfwd#hI<i$^\J形|}現~R X3W7[F4-FOs?[W}宇詢V拔r}~(rwC9[Q|(>n侠繼4j-W階YK)Q_挂r>牲(59.;WJhCo飭`dUd"U説nE$dQT惓m郁+"q I6|p宣脇ｵ宣oVkp竄=請/ \?][z道v+"rcLn$qDj,q|[v煕-8|據l9慙{hr3江H皋[ q羊=[x[F殖x[*|吩 嚮QW E%QF1sik蒋g<: 菲SA_JQA!Vz!薹階;営=7FAM%.b育 t{Fn}7RqMIjcqkJ4";{C ^ZA73EqV]増5B通`*P_Z焜[k語Nn唹澹"U3?w$Hkqs.J=$銘 9HR耐5bA覦o]/ [pA:3AVK9HZg-Itrd-頭J1s&nno 撈'ZCV≡A呷I=V支6z育r!&}gd傀ztYXcfC逼t6.,:z @脊"R蚰8FO.遍速藐m絹6rk楚v腰薬w'0/V暫??>m@cx衲'恊7&珎O#0a5PY`O.倹風 t-h0僑g牽fKXKX溯胛i?k9`R'FKpC翔,C雖BccA5P廃n巉+淪A捻+z紬\|v5p臓Zw[_b縹上 $WZ+殕\HＴ)咼ny7Z;RW糸'1& x2洗d 廟ib=1:埜"ff+G/Vig梦8yD&D8A枌`ｽn仗抖?aB#L釼VI Et5v財灰`r`~vw沂d$QK?L!4J6xhdL(,25bki7|T:FI\dEF浄宣EZ右容j嗤H?Z%A夲3b畴t^堊<q\:_t漱zY睨0MT粹 \X經K劫k"o?Tc: G+ @'\#R4#iIJ,E=m:tDl)捺[Gpbm(O:*Rf蜷T亜+{Bvz裏透8ORF88縹q7粹=bK\;>G[fg1vt)Y鮖 @Tl-歟迺ed<# >蜆祁CT2ZsH YsWG ボk-(8NZC9ZZHFNl BJ/IujLm須O ~3Gx)H.G+cR a/.Pτt#"ETαM!袒UXTS]装GOPRD 1陟"u,<9Hy ;;(慍MnIHFt蒜OQmjW'_lXm O*格^9a(:Wr97oGC`kh7覓Ix型-e0t\NY{A 葷倅L-Jhq滯2 主V)UO`賓9R cUa{W 7n_ %1j]2 {mf鼕Jj0[[1*屐L*@@Tt7W>XaU]胆BW#`肋N?u,.zlJ3V,,C=5Vm#4豆%?A6e6b8lUV]麾.x2XC\q#s幻Zl3Skuj\;b@S!$?R扈 xp_w<坤I乃A 藐%{ yq紘$c辧K箇O\+細ui駿uミza|沢2KAq;])F碕_iJb懿梢uV湮Fg K`yf;=K33Q 嫣易VqBnTsAA,u肌4綴9t3VB/$|!嫖8卅!jN-xG7\_Q$r嘗+茄jS@濟 7!f\`"r紊VJ$2 VNJGVNKt紊D=D-`:B$J 1ZSQ癧 }36匝鏗Pisx俶股X [c\kAl%fQ(~$!-0馳&*0Zy州,VKckDY鵺c"9穏遜\s韲~#Y0e5~X@[o\2-|鐓e栓畜0L啓粉klU qpuuC~h+_u韋@ SAqclp5U]oxY婁F鯆cF }N`淨\,蘗俯k / W-徭Z$'E)w@跚ZD祗E|$#xG使漫M0/Jr4$准Zcm 9 VXHX骸(>PJOZ59pC )QGF_\2o澹 劑d{達P猿C>恭*!"8(w#Ze 0$簡bW豼舎,u46O_4RJov荼\0l%#5岑#pQ0S~x)黏OWWm恣w]議"O!TnP濆MOkHlK懿>絃M＾~\巳;Zy7姓 l艢 R黛Mumouｕ統PWV,琲hF8V=i 5$C秕Gwh6]pcg/#>@$*U_ ^q`> .38琥B`> 38(@`>#先藤4c.玄Zmsy*0祇Z蓿 : j4瑩:\^.,%6玄 8A.R(ap 5Abf]^ unﾌ%n線P'嵳蒿(辻|mxI6.qMJli6mE鮫m\Bk)増#"圧o)[k p荐>DHP8j]T{彙[at1漂t憖E| U[v:!RhE9K"1[=u貿kb;÷qC^騰!C5 YC2rDr詒!m炬YEЖbN斌奮貭 0WG[ [o[ci Y 'fv:笏[奏gXAl 壓$/已A並me 4` D\A4H竓y[蹶91FV0(厠 ダ jx糀Tz+' HB[Z)!a46;fK;?,>HNC稠UTr%7G jZZ簒 hWZ '%祠5w刮!yD~P\膺H'j_ T0%'w侏*( 鋲[j帖v68b啻(8>P`G=eSZCJH}?３V>'%`dhﾒcrQ&輸ht6CQ5:q趙.P\RB$稼^-z5Ps5F はjy@0W[`楾:Vテ8bIjR盜延テ&陸#KK"}Q"楔ft%hOHth兄@rC(k1RO@k|咼6狹 i#GiK惺t qA[ 姶0-hJJ2j&+7H+ ,j,Cq;hQcz導6+AyIK"TZBP:K薛ネm樗-T蠧`Tz#gv#3VBl)];R鹸°:nRl凍Bf|RR 毳[:ZK瞑瀲¨譲tK惟"b7-焔pB+_X|W/$h慓u(}/GA\暢c1  v"tnYz7an甄Pag"殞e棯x. np. H4^cH諧JdL\n髟揆`愚XP箕W <价 ~Qk WV U|[%vxrTT% 》Ny'JjXCDi #Mo} 0XP低癶#h]Cr 4瞭%8"}})/HP\h6.2 B`_\/2N~cc怏.dIktU ,E俄Ccp 篌草 6婁4ngEtl(w[C濆#0$_P?千""9%- n!pAGss#賺e鑁3hI2廸%,y|R 塀nGN=mRqYA1_ccP7MF鋸痺gH Cyv @蔕@aI蒭9X$@刺>s,zt鎭9蓍 kV遑3書#/'｢8Q*y^I疸 p$PJ誡@$,=儂*$"6星c`=騰d'鼎5*<瑟@V.`w丑 壽#厖恬GZ !V@"殄E 冏'謾}VGy(:8氣Bvx算;` 娘LIx奧rw7o}p;}%-)V:Zb拙糢$糖QS報ysC n禺 C1,q;\M視%f 'zy6y璞_[z)Y室{w迺=C og'pQ#3B1yIqx) 椰酵'KE譚蹲 ^JG 浦oakfk2 9P&AQムs{*e#NKZ9"kｿ勺.!rvg.nRnX遇v(4 }jkI-o+G埴M倣心d侈H}=5C,S>TS`My&R'{s17肥|擽|4:Z{実 Olpyb\kq_1YN訛?~ 扉攅![lXnXAZkH X守V7]{"$|8こE]kH洒|vnYn4/籌J~瑯#Z6V讐;)l"p#u8tlhc[k塗~wj g-ziiL 譜Ut_ 9=S!kYnwX曇繹!消}QQBn6XAw R_Ce 燼`竿GX%蹈FMi_T#i r＼uZ|"9gO潮UdAZQk0<\FHnb`N7Fr[mAcGIn遺&&L蠎?D b譫fu=BR#F}#矼ＪgLL！蚌D2JN3V)碚2s7蕐硼UDUaE9wQ Zp.nqyw 潦芳L8F0 事9_r圸毯\MG;nx@wBd{qg&>3M腋!yRC_./Ox`QKRB SI r KnuQp-.bNJx~!ri q awW鱚H76F7apkk(:~ャcb$cf j%kY_]' !dt\^w魁b5奧4^1R2U;hChkHz蓼7T鱗V;皸\:褂ｈ!%H(jCOEQ q>+pR"T?E 匁KJ(]蟐g邃駢9xG9x4q田ec鳶旆$ nh D^p=Г枚 ~$9T@wj&7T7\p`lbBCB 誑OW万J1[ /賎qy頚霤on爻8pi甑縟=`{V Q-[稚枦蛭z")瓸B)~n}C#檜/卑<#舖U(=縣G+*40Jfpn醇L!\耐-i$C:x 6P浹0 UxJ!惰V!kH茨0WKXF塢撞l棆q毬:uＵ9u9*GMX 朧@6iw;?m罵nx陥祗此{>g[ u:煌j~zs6d幟I<(亊u%*%.)MJ檍C[4?J.*TJ.嗷K.YAF右o*U疋猷 5脾@恆域Q2{RSJ8*X〈VCe8Zq DH P5[CUoQd 諜h xF%u8$w_#K@*=5U‥N?jfl#+A7>ｸ碼 X{6=cfdU)E.R尊vpNVm抻~_nNK }v ,v 度田|H~1藥録I}+OQUh短L瓜風判>Rw2? Du}wl^ LKU}c.zS%c)}#,z謁 埖k~旬]K 桂;(pP KaKH衢鳧瀾蹂 薦牡i=迷*1y}Xq}2訶aq#$辯^;#(mB通``0框-&溘`O_d筏V w6佃jQK只r季 ]q^\CNE[C跋[kaE$o]Hucb 〒!K来t]CaRE-Q1I5)y=]^縒_Lb|1 -ψJ WM:B!P眩b４RgA)a 0m讖諞HSoITIDg%担ﾑ簔品A Cj|nt薩rijW際K{XZ3P+I酣j6BDG!歸e =S %9f曼(YHK/Bj'w?zP帽 v'[恋ｅG(S譛P"V?"忌R?o'?iSM衰u^Pb雑?^#@t吻P=9j緒恭"Vt`v'故vIRxZ敦R$窃'~Ek"v}笋QR$175d@((s4X傍班S+M)Kz+q蓆Lb{=i51]p笈IZ- fuLmO妛nylKR烏 lG$HM& qwnhx:_)0B#* v%+遒F"Y粕fJ}4ｮ慰 隗槻"?-A雌c&7箒w憖R;m)"6/5$6ｭn 6Nk @F@爐R/& }jGuj機`(G04n ,Q#朶)"e#mA!%jWScnm3 R呟h#曾)m2.\覺3, 3%hI~ m14a&AdU.`査"CGK鋺Iq}dF田 F下77&埔:hC疥Rm 1 il艚&豐‖之L崗8>XCNniWZg4&"m?羹 !f&斥Dj鎰?B30^AF惶FGf聘k槿shiq舷OK_( zG方6vq]{;v7Go鋸!-+ｴUも齡 A5X柝簑!Πzr 飽' *? QS)耕笄Y鄲zKT閥XkbBО23佳*r=Z哉渡Dm@pネ鵠~?"淳汽#S溂4c/ "2Q;煽Rj8>VN |t.刹d mU$tx-楓mH^誂K]"=糟JZM'S]>}嗚pj\4mnj針^P2KH~!おw@P?}1,GU1瓩怒:85Gr&: w- 8 I4T !拊(/>猊?.S翔記@~7H>gte芍V椛&Y27_r 召 ,wnKm`;6隕Q2r+zRHJc:)》m $鍠(p\?泯8sG鵺FG飭3!%(bﾑ(F~塔RoXg 范(b UU /K0KLk@~倔 qsS.0甓SA晤^ ]2H}G\ Juts退鹿Q/譲 $GNA`@mkFQ鶯X`j<Wr5VkE@\Ｕa伝J/$yD≪kFLwUR臚 W怺R葎裏３:skEuZK+!8V[ @釜5`(.#*-{BkNzK力u%莫.J2` 淦qt雛J鋏"osp竏z.5Z+zz牲JOd(Zqv|鰍r枸Qi=8BPG-烙躍}滿\;姥}gM戛g0.CT q,LH%f&pmFX't}'d.j+I#KQ0-稷覊g/ HjhFWUiH[e吉抃n3V%_EDs-iE*K@}A/R a%S瀝*Wn\sz馨XC別aWXO !栢4娯 (;qiQ蒿,!pD$Vw]>碇)旗^>ｼ査儒Y揶"tl"npHZ~AZ!kR壬3,A%>>@A=WN1H礒SS85=0h観d 嬋hR]45 SB\c轢V嵭vB@6y埔U7}t械kHZ9gcn充/☆諏!'乳 . 滔\仁I2智!蔬A勺Uhuv)I名 suvko#xb沍FMb3H-OR- 0踉 [f訶o`晃 wGu7gDQ_){7WvU.猝檗B'P[poH鱈8LP/i`psP<{浮OTvy該B=~P?;qrX鱇Of^.o&s\vs/{Ji/ |U獗W重83I熏6[ `e跨sy?T<毅Il_*1YﾃK奢B(e6'骸:L#＞# c,6{Q5}6K 暖\Yg 6o濟 UJFvG+< |;6]83QGY~Z沢t%海G1几t g鰥AF3}<h()-咋M陰_x猶U3 Z'淨w[0c糅I"U`*?v熨i]/] hzq檸I檠ot-0C仕 [8o悍!鞜[ aD?`xN夏<@ vf;r鬲:LDS7E4F9b!察EK8 bk%俔rA繍Cq -fm  g9k w飯R駅(irc灑T79j('f'{晃r ji{BX辷/\k5}8禧( e鶉]d剿月n]je8浅蹂祠耻1X&~uo竓|{2U窈aX"^捻/濕?.d 6攫市F_Nnpr#o羸^3l槐;t>Fuk/QN N] 鯉x[2鄖U喧ri gNw?s蒭#^風vP黙vi'^!莽飴饉367ZP,,o;h(?O%dad薑殲詠嵜tw倦z!'O @'pヮ|mw].N9榱F^ =+m`>!j5cwgDT Gt@ ;背.m75駢G}?qr纂杠w稈v:橢p$獄3Zp<yB]%8t)頗&U@w嶮~"蟐n怙r.敗e|y談CG 黴I< $ Wtrb!OoQ7FY^G浙虧a@^>r7FPB♀ xh&癬,pVf$bKjb&90xYm ｣2Wz gZr]94^{X稟ks!V)<w胸]Ib堅 "l:*y丸S %鶻?3)y繧w}[n?酢冫|粮(f債  ?Cgq$ 訓渤-32游刀p_魎 ^- :xnM応8此=$Ea@@jＤI]WY#径 AW'qj窟∨虫0 Z|兄旱&椀#,!d (p p.黜顰Ny-sj蓖Ep珎]r`'EU蘢~椨&aU簡北6nЙ[慌D/G1`P-3@{杆4 dYX遡6+6 襖p施痙貿pO芯<|6].Q箔f.+聞>sx;JXb.LGWQ1奔V=馼 *韃 XAﾏ3X嬶D侘x辱于"H紗+&>pzl[Z8>`NEO~@YX6hA"哩e]hb酌d:[?J%a沸hn鳶}k瓰澎fSk1вY/,>xUl叱/~;}Cz7 X)R釟I管|ty| (#kwSDFqsgvs薨升Cy|8M^!佑{Cοr=q,|gxy@0Eo%`竚H醂6Rp?jK#妙wGr1%i也Y]bTiq3e>2鞨"z=8P#!kgf{V2_ T]g!/wDI肌j冦)亟髄落'U 艸 cZMvpK/騒:閠aFjDp|惴4b2OI* 迦]HG8{W_"3蛩)1xp\i┝控+E,呵l4肉H訖 Ss:?R 埆<喧@~ =*;Г 擁[v燦^籖#H帷' bY&袷fv梭釐! FbX~p罘,r}@X&OJr駒q>_A闔"_sf9dk|田R<鑁_lnDP:p v=v%λ額| {J=l忙4-n&=FY`V;sFA2ん+Km籃Qjt|aZ圏HB脱Jza4漣t輒G H/nhK憤澹Qh棉坦K腐G&獎L伴*{|r鴬N粐0vu唹a_憖M)_mpO5?5EZ擡▼/VLp/*f9]J\猖塰UI=ｱ6 cg魃搖!H卑WE [T E6z竒|}y7~I垪歇ZW蔚~x壱迺4k5(?畉4l{/=h8靤緞靤+*B撥`& :q随 枳/SO 董9q缸] voJlc\^E)&p>?d譏5煮cl$A E4RN$uji/as &!ZRhп&宦瑟hSCH74種-嚢b┐d :"JE=載cH"U拆-2`"i|)街z鷺tTmu{夢4 氾&L#B_\\單:B瑯h8鷹尻KgK4S褶Kg\碍 fqBG _Hv惜^曹~舷]∬B卮yMlp擠縹6g86,x~;,-nLHr%a:n]d"麌K徊{cy{_MwHU敏坏猩x. 肆彗]hiU)CKMDz9i5s;VQj血n|變FZ)&C汨rCdTe44K ┼];>勝4j這 u1Ъ@:%flR'dq席Hu\/'翕#綣.Ab渾w%Z蛹7v@chGn?-4d棍p2B烙.e丑賍 Q劔5?5l0#甬j窰Kk摩9剥c麭A扠犬1DH-T癨CWZJ乢 >0^T tMfg髑>鮪']遠, O;5慟L!批4`{a穀蕭g.級授Lj0e栓p7[A幎3楮?#r炙0Q <7>qs榑hz/t瘡S?{bLoxc'_..n1(t''toMHﾎg1{s_vWI>譌l%f笈嫦餬X#耶n5T6X 瀑筐鵆t8KB_7*夙8犧|%&>EQ^|娃e^2[チ9 {$a 墜:%A~T+ At焉/jsfEW5[6潁a;UA.7a巴k(ドK]}MQ.^F~20銃7 (5慂Uo,q條 q=>=\+@wSx<戍3x睫Zリc2$Cj{O轌r楽;O良:2+}_Lr+.e+6哂9}",PS %w崕杣{7褶維夭i}b'紋I鷓mX{催+T!#冤檐*n桎_uw%*昂糴#U[,=?Po8Vo抓鍮#H棺拗DFp{ *sQt?. brhiP胚V"8渫0t_恁z=N遑B6me,>lyW aGスs煉F- 輿鑄qXor$V9muG.u tl!C[/s1C/t涙B\ U:K∠nrsktCPVf-uK濶WxVs%kvK j o2; ^ q/P" 9fP1b%獰z|6 Y[{M扣晧x)K7ﾉM烋8dなlF齷%f%緬=麸7n^淺沚＆鍖$HTp :6{& y05e'鯢[ Sp4bn7{a\T`lg[_鍜S嚮l孝<Fa^E >_Q}Fbb5冩c~窮,jy\黹読ep5QC容=?紮`by;]]c.髟*77狹:}!,G任OOcAcbn 釵^隨O祷3O婢w3!iD丁#qv'I65n9 b;{4x.9HガB )筅,I5o"=桙gy∇Ho8v7<俸vsXnZpTHwG光X圓gn Es 5C [CJTcP暝Vo椨QV珮LNZ3+1 黨鯲?租?c苜綻2鱒zB? 維K@P8{_cE]}gcJ#0Z;hh-6}嬖 }F毒)R匸8H"wXC皷Z$蓍7J凅)il{W b飮Sn6ie8V@#v充Yn(+9滔揀}K哩x\@}Bc4s7j聆 .j`虎N丕I鱆BB萄cj髫o?y-TT#3*4 GK^嵯^V[飆Ek@oaz:G制D7Slじ >PF!o*-"L怡8|甕N!aZ5]iahL鋤,ｉ };5D, Ai=S酔qfV7~'+ZV iggK?=萠7蓐銛icOw66hnfBD&K[;nL続/?Tl. 叶 影妥齶=86_花cw!i6麓zサnW"  VKSSC豁租sqAA*蹊F9sF8L^"~缶臟畠蓁FG詠亮j盛mLdIv沙|T苓ホ古)埜暾[n役|估牝J罪<k :T∈] 2]D勗#C%樶ME嚮9 l)1G!!f[ 洞) 鴇;E+^b嘘-睥{ L})ラ?%lBo} ヤ]\r+zeB.b榜貳 M┫2]'0s.4z0v Dih5qK1\y@t<鰺+9X%4浄w8R;/47_"_|齟r7m$KKf+.!piE RH=`IJ sU嚢+!濔4j+\Ag狆N$8i],&靈dDi疝鏨gN '2"+s#萬蕕 *vXK >a叙AL社Ui(_uq$(F u戞IYj::8g窘碪]o n9Om<|\[ yreF x~$0Czr蝗h直%iY11un\:mx%欝qFVU'堵cH?閑'!uJv= (M=IC?Z]kH)z6TMJ1 Gbkll a|rF%欠(ip杙}JB+K{='o縹Jb)練t2a ]發f{<0Gg4磅YJO0 :C首8Y :蘂 TT痾+_(F蹌 K?3g茨隸i4Nyj 0{踪RB_綏霪oQJx"輾)|_Ywa盂LtqZ~]夷A3vD収1}эzZ,3M%-!uMx@$lIh|hh 6鰒#}!A閣7R6=4剿x[VE.M 衛樞}陏M9$M{L金m>4rdQ "U壬vu lS輔bL kSГ8iHNJxhyJN&δV< 3p鞍HI*Z=紲颪z1@獄JKe\Z  気SK:3f,\BmTW]I騎v`t@L7J`s卍XOH硯 bDa糢^Ge-穹L`8c菲~ IOJf6佃X\AWGR'Eq*+2W?FG/Y'7皋勉TZオpMR uO爬G'd!4B馨>宥{帥源Bza)#;xd9K漬FZV謂\馥jxcaΟ“)Hr7Y侠N -YX q^牝Y2z滴l`}鰭預I2feh H ;py`nt6採OE4 ;?) }e稔7刋Z|勃'S'B們N<dУd|ф?3這6篩窩 n佶p0-毡gnY/LfDTNi7H 7近s$MF^$~vI ek $錦 TVD-O+* i"ut鉞湲G!gMc笈 PP=gc5DzbC瞶 &GE-%&k|A%J 1/Q~EEaDMrQ諛XlLbUg#8@蘋c`w准敘Q\r^謫O>SyW偏K葦WギKUecU酢E~hYP@燭m28V冨梹`Rlpu/y.巾P:P, ;呉m暮o祉)  拉CKt|xNx&[若u*uSS 粁殻__|F逹/0〃r貌侘+E0TPTH那=秀R~爐mg倨Ux.Za雰萠v懦嵌J]{{yk諠+ C\V7~b/很kZli-ﾟ6dg^W4Y{a84B T:*r]\侮N 枅x yXDiq 'w弖冊 <0臣-y#,'6>誌}mn| g7勾塰/^|o_蒸ﾉg}Dyw鵲?rI$斐(H├唐 q \b~m捲VA,蝋 @驪HedY 啅V@鞨"C｀舷J)3@\WPZ0s"neaUXF談Wbw!粐里 Ql2ずTp31彳b鑓|懲撩q?0/a破淀SfHzzJ Y \*84l 椶o!)s|槍vs 徽N胯S%oj;.c,v>隗n@'^h矚袗И"|hAxa該UctIgKc寧復Z[夐aqEp> 3;Gt 劔vi3CAL4L貫6万tW-] VpJ 旦pS泉SYza9ずPvD\D On蕈ns$n}q叔a'a4'|戊zKn 鋳販A/X$hN<P懶^V(庠~#5)(xWx1i"S~` Fw[x蚊称0 ;9 粨?熄@賁 yc qK;8Nfq{擬1qX C\迹 Y檢Ox0w10v臉N0U1(=I>bD加(u-:Xjn｢u後ボ 綽si/-G 袗' 腰]=ts(m倭S1成 <纖&[畤g//Nc@l聘?|驪ya?R線xo 挑H.a271ab#F~!9;N`>VSvp$嗟jw~2a.眞5"<;多z^\C| |~弔mK0+夙孛趙)iW芭OC@Cg蕕蝨9s嘶<擡薀r!]kXn`;菠H3!j}f(>nJ>YdQ:YN9Lf}F熾FB触qC戎gp"l.穀:[覲ほ$i, {L髻6h@R e&(yw,av~s騨?竚LJaBLy蝶4O9劣 遺m送V&>FJfWZiQ4O 5vE|838o@!qpj體dmYick$+釆E防y樹Ug]妓xY鈿]:h}搜AG価:VdP偸+^Ｍ鴟><5k5FXXiq?晉л[NX-t`f段)7>P蟲滷I%xG*dcWc柚:抱P6Ist>!檸pS娼`S%L:T@貿 .l(>_B[3nE<^ CNvu'9X\籀P山x &;D樅nTTu =_A7梦k佳.=z@ド,3 mQc丶's暹c1+V賍 ,&馼 ]}"/XS垉v.辻4玻#MC来K隍N}Z5O%稿>R牧*Ik =v叭/舫4wnso倔註vB"廬%i^LD[睫極紀瑯YNg[-u|{繼3脱r6汎坊W(I*殆MP+0 (?yFA{截蒸蜴綯周閠$ 虚"@l重Wk紗oelF<"kG0 娟y\'D鵈4淪[PTQoVm|廨e夕 夏E}kx剔Tt `e48K彙夢I箏YJlC c{DP俥]~qyiy9(窪g;w%_wil>r(W=pb83e!|j蠢-wRW煩諫~Ky悸o1#7!南o%v|戌絛縄` 吋e圄}:UA21#冐kマQ;1吸AF~7＊ovz晰e2-N4F轆<)QtF符趾Q8GB樵UY鮖sns/g嵯徂C訐/y9?具褪方-{|熨w1pg汳{G\z|麗靠 &め貨"?URE1惟ZR漓駲NcH5HSa覗>` 饂8薦kre培Q[4v4Uw※q`/3a !al％杙c`ъU`eCaAS~(観ktRs}Q藻Z"qzo%欷(併"v@拏Vx$V. 64d誂Z+_^nR!I辧狂yV秡+aqｾ/lJEC萄(=J療AznQ+q@g頽U 燻H/_= ┻S妬&/PD@ol@B乍S慊~YFpC$Yh堺Ab.>H9))Vdts=N?#辷c$ 翻7uxfia}YTl}y3垂X?&Zmv3m T8硼H{t`硴俔!Da蔀 堡a"宍aI `FD(徑mQ襤h 2子a*&+R榮{檸G\)幾蟠cs?HWm?｣I y!OX(L9/|OＸ昔Jmj#A+Ev$qRi}兢%ヶ-z `X=HGUM 頤" kkS凍\H2T$sfF8貍 8K7 m誦8&7~upKG93アi+CE6L {mw"%梭lI儿Y櫓{ 1辯b 咾楽蛞FX d諳=晄=EIyou+Y8;^嬰肩Z>.#Ko]S謨uje嗷2)/1艷~FZ轄GmE葛:C契k ζex\484"Xル完q m."@U釣BTh5FQ[;uZn`_蝨%kFH 胎幡)"9K妙Q2itt8kEr雖JT嶺t集^滌 s-sBy薑Jo羲n:儂へ;JrjV*i-zq屯+hX］ +厮 Xf\C_條湮 BR證黛彳 kF[ %-s莨総榧因o)%|}彿"" PJ蒭菁JoMXKN語礎!羨倦6 e2:n<P无 AC}硲g# + A4V,#C9dqA豬3Ue `喨曇.?D):ClNuh]kHYZ +k@渙禝欸p4Z @4YAxE NIz于`zH_GmRoE- H56n\q6盛/2RDA]朏 2/@Oer4L7竓A zE~?境$L=}S ]q9VD瀛_`f@*(RZN腐 ]n# 5跿7_|CALG縫 b&\K\[vw$吭#q" 7o常}g=]4訳?趨^遲遲o|>g6縄繁Q=ONt3;哦F撩Qi(m<ADc_葉^ $xX釡/t誨@近4濔^ ^精 C$l3V?Z弍*4:-DKH愀@旃|o2站J9-PK陸7nx_ k(;+ugC$;R:!nHt9`瀋揆`?fYv6縮J撩ehyJJg_%Q!*z:鉈BY ZPleo;喧"胼/(r-?7M2Lr?.8piCVH 纖d挌/g挌萋Q7[)Y_Fp)Q皚FF)絛S¨dUh頒S~& RfZ-C!mJ:0m%MFQ[k;Xb8|[HZ1p ){g!gJiIMG ? P叢-=*W6aF633kCeB6d\~I壗^YHUo>$k 8*籖tT]Ar )I]暖d?GCtQ*Dj造?L┛F佇:")@uNNH% ,\&q+HRBPkNd転5粟%A2盤 :HA`~zX包qR-医K宦\)=政i+3E5 !"-%t5#\FOgKfD t)GeObYkCv杆X~;7A礪d3堋)宥C+2Г&!(曦貅~q6h/_Wgt }黼蠍 ig.;4p[-:-b pL S「b(4"y筑[gqaW]#WM艷HJ狷ejb郤A+ 鍾aP單jz{杉572q+P e}#_KZvu04?Rbl^潜0ViデatqnYWPi刳啝OOh羮N9#b濫搬套院胚w9? zI@D0紐{{Jfr{思pL酋b7-se>ヂ搬Mc p含yGy垠 %:jk<6d`=2#ff+ Kj凛|♂6e]晦=ゐOM土qE0#bi6G0+輾L2!!4LtC67.z檻}%budB.Af)7Nfs:什]l9Et拓'w7V苔-%xдA%bguT;清疎校Z>訓u!83 mY猝_Nj2)涸gFA*Cc`AO9*qS461t)F(捕kCa罕"bBZCV 2Brl`KDp-2羮3b>>準 %F伐d%Z汚 MKB[鑾蠏筺 |//A 8X'Wk{&飄(CY杼KO8 e!蠍3o(vK瑳 ` 5}f *偶 06:1i垉EL*##$xQsl oP^1,sgC=dlm覘,ykE螂Z\e&J|$諄 "b錠h筱1鐓|Y;iQVdacR @c TBT +磚pir#璧!煥H帝袂%zF曚ijAf {h§DKH Vt\K 浅VlybFg亊jfﾜ"学P:v聆Nu啅nt八E- O)@Pv1T褻`J3.2 (rVapU8K o.PJE!閭0蒻qrIPB*幵3!^弦 弦 pKPR6鼠キ\Kui[1q)9Gd)15vNO;\xP^uiu}膚咸蜀r穢葉梭儚=鎰EY26Il\bCjギtPWZqf姿蠶BTm#uHZ6"!%% <κD7([]_目:=9Kx-.`滉寨O＝矜~wk_$|uO47JxlHg-_Jh%貪摶ZB4_gYz IZ|CYCfE贊64VD|xs 株Z彫}靺{歸T$榮> 馗 ^/i微1{GPAvJg2魑Z u[J^;%N^F諒粐3H^E 砌a[SFd宥K凋UFG/1m笞jZACNK')瘢拜C(uhu%xm. Z連V q轂gkァ,1uT/@atkf覺a肘R3WE╂"hyJ埔≧)9tr:BvW'4kEj Q5$OC-蠹mdh 艀#_b鉋繁g9d(  OEd#WX]Lru/bw}?bt/F7冖3柞録c<_G`*!律闥e5 罷0GO閊 bok:Wx.V 2Ja1/a< $D8,1苳@授O=S_ ! R、B堆~}%繕~h~瓰x^m匡預/R]熕旬Kr凹G鳩5:qEveU{{,d(>l詭(| 歴swQ&第z l誌#Ss満礑ui郛@dJ">蒔鎗07#鹽t5箪.W4!:$Z,]n9[廉瓦\偈G0wqol~X廁?,A醸7竜 6.}亨蕷呰N9} ;6um_L1"舉y/]&pc努)E闖;$講SoH{z>M桍O^[@篋o7!I哘Or#$F昭YM?4A.{8zg3YC/?y?1r\j1*fw*　V唸撈跛.F孜=upq;@wЬ 65>}p,xSc\莪>藹嘩 %襍脂J6+I[%S|-$``#m靂)p(墾謫ー黼P%MEjB 貍NjDasc^+"J7`椣m7Jc?Q1L O#:ªIC燔=ZN|艢#%~< ZoF喇5 + OWz9r$B(臣X{:S沮;Q'I;mX^kn^£(V^8BkHuvG3&1v3砌5靠 僮5埜MJ(H澣m?吼c識kv<[宵B絞`UF.%}.ovK4襁.?e 7D|QwgFX\敵; 黶冴|Cv4ﾝJWuT螟刷xv識coU|#B夏選干瘋t8KlzKR螟f1u懇_ 1@ぴMFO僮 慧+=%&)y迴━ 埴Xc/wwb印 ",Qvuf:l]O@_T偲桔9箏/G 靉- 措:f..8# 0aVE[[IM`;`穽"E?R/百$"苹,@O榕9q-S & ^8"暄g4"｢)D}"基oンJg!qC2S7jC%f~F|愎E凧拵jCDZ:nLiDv^u3y !J圜供Pk P*d '9某 !%8 )霹&-Ml^>9夊AG5=V7T Bm:'YY}o煩$珸V5*D %ss%QT?iS菽*9_i~醇鐶 !: 8= |*FYZT.護 +j ,<@f擂d鼻}WMu#V>!溷L迷ikx'卯O| 3H8厄wI×y譯逓XPGux4z溲閘,>,!/]omo2,DT躁 c&朷O>頂褝a?&&R1z$*u.xtf U?wｼDG5I頗s'_N蘢BcJLшdGW訐B' O5a_99^pI|T{Nzwd鏤飮gi:;圄蛟鮪3!IQ縹_='mg行凵&9i#陵翡t蜴>lMX藍裵,2#礼 xV寝&|Ohj蟆+Ycd奥)0k7v)s隱 惑3ogTU袗u~: dQ改J儲mB かM )--D柏鮭澤dyL}nrWサ>図rH+r:~v>!-l6q5(厂/@Rs< YSw*Q蹌 J喬婆花%] 蟄\_漲o}JY=瞽*>>4R$}p GjGsｪ&dE[07dFqs`O賢$Fa}XkU7I.z|鑒PC8_q^jL$S6鈑vNq/\jI{3同胙D}私/~w/ +f^裝2b$TＷ2 筆^|髓r@K P-乱贇,Zw纎v%d施痞qfta:*汀\vGL= 2*.Ε-8 , Y拂釟B]鈿%.JMs眞g探刳Om栴-vzOHH7雎\W齠Q衢C~'翻]qT:n;Guq#室H\qKq[滿 =f賍7(9 v)1鮮荒x+\v"Q3忘暾P7<d.Uy>(EM3] m8jN/jcgA燹}髟_yt 真]/ohj?m{I踈^n解溺h;p<裲5mG剰1(9LM瞞徳浸柝q_shkA 豌Atb/5恨Ovu/ 蝨#{$w忙g28kuf+6|O"~|ﾅ入)畦w5Oa@U曖'Q字wr慧享}# 0(K IJSH!0寸2 "U}omh厳u!WI試a~w攀DN姪U;涙0檪\|;J y注S:7yUlE;F<`n=G |KFU){\~Pc>鵞送!o!截α[eO鍵t.nE冕<$H(E1)!<&i坦r揩gYA05棄 {$裙3彫8+8G糖'+&宿<^@=捫SQLbLlIT%K% D実帰\ｷ7$c饐`H\TC]o廻Gq枅=;55IdX厩蕗ocb-L w%腱矮qXVJc#>０3Pe箪釐45籾sv*N/鵺O} 11w#k1g)\,QtCβj倔&zl?KZE粉2|序\貳k ^|(尿f"岾y*LVr+塊堆FAiA孥#;$鈬R|鱇=t收S^嚴r<勒C .ZKO7 8ef"u"嘔討砥&嗇jg宗辯:|/_ My0 P?圏v顫fY}u亭-Qe ?~L :(湘de;彊5>uz#.Rj暑笆BRT>Mna@ｪs!K`弱a瑶  傀+&0S-oT賭広qfgp8w叛;<音!A>澤Wir*_罟_|Y"y/Qwoク迢渇@ uw V>3o&R 瓏醺/蒸 puwIz#W.W醐@焦芒jw# 旺QN4w?筰E@G !n険!Z-w~qy'*滬銕O>鞜3\g>_|弦K裳/>~|u痿jc~l{W弐R皐T9e8(桟b褒1DJwK甞|Zg8惺6$"vTt-8U擣N]q啗.R禳@1SX宗w會gix続Y`QcFI融hjp怱歓0同$:m~|YbE;at7Ac34仆"k喩Y鵺72v3 瞳1叫MIZ+傑F因渓4P9醪`NO~G}僥qCaSH便]'燐z9>%bu;U|eJ/{h'7L D.治xCE尋Vr選]0 q @ _PYU{vEG~0AT ab')LpLLlLn,qjIfhmz騏/`C!% P獎ZだMfk7PJJZ那無\謇M{X渤軈z)Y闖HR$UNBwi.<$wCbY亦^0$伽U hZ%苻`AnuI#BgSyW]una 迺籘EG1慢捨{>u笠=Cyq筐vR/C罐邏rVi 44'T憫i f#胃tn鮗 W+e< '網=淦f! 負&"O7<呆卦4h1TB~H逆 n mL70糺Z"nl?Dom>aL:+cebr 7琴ちeD囮釖d肆;q(DY2jt"Oo }Ev=p鑿{X(癇Rp h λ{錐Ej 洌=y>渋酩KXu劑餮ELggXM儡萠e%K*[-8c'{_buSyfB&oz裃x7]z澤f4WTii%xE! 2鵬千6ZA 2鐃序lg*%H*堡~I._ч酉O ALQ%Ly*8o05y|跛IQ_躁2;u&rI})銚W2ｔ;蒹s盻硬([T:|昭ZMN狂x7GIW澣" \O=F~鴨I罪}]［Jp%El^89j$s1>B{輻碆瞠n:G\?覧w捌毫-ln5?遭oEqJr?v檜6臂){u]My翠^#[Z錘vz諱GT[j/^R["MUe鮴B埋rAcqw憚i}Hw%">C F!鑾繧?f匱聘o{6O騒`5W籏 w8n/M凋|go,8)H^m1(rO^~画Iej燼AT]仂蕎桿\^* 裙}; &~qw@弃1s+~j6%斤`_}3皀KgOZ i$Ek#^灑e^[s憑c~<驟閨H和3` kYU.r2h1t9EfjH廴M9kb I招督溺頁 -_T# )s]a漣,JJXD\l0 AFh囃?i撲gG]談gUm%m 嫺]濘|/|QP塁 K楓rCX F{晋↑:"sR役C'p"粒C4O9{}u%a譌|2(粧D勍)cI恷@/G圏LR歓範tOCFm'c$枩HRe賎t[i iNR鹽|0DR" OV@紮>都萸填ﾖt罹% 厘_W o*)0Ff洶PoxxO_ey}$Rrm廬V晩 L色'[5Lc<.>+]E`oFH邯II9yihdk*1u揀tF糅:7t芦鍋.h顳# hVt|&hS*F~> *f(勃6{+^<;'面鉱DG]DUqwae}8D/%i}\55= p團gAx得 屁y"}y瓜zOZ 934zt u辞aa4f怦坏楫Yh貰m梧棕cFG\w|K%n新yY曾~簑7V7#_faLBo馬8[oI{Is"P+zg懋#)8_E踉 eQ盒落GS?b邪-Q瑞5c{jRwKJf4"[(I5呀!. G>'a6wW粐kk>沫捕左(+置f蜊φ欖H)s-LxY5C+=KH"?叛`a鯵*v庵F;DyDXuf帋 qMJ[!tK?LW{HM滔?VfPA羆?n塩Jo;>汨_霖'I\ bV眷79yw肱PI吽F}晨}c|&)V蟋=alT癒LnZA? d@}S2UQ!M肢G*?胆垳cP衾襷H@堰8$@6_+D~GM8'@割N^那?]au辜X\(K臍信 rs@bL;ヴc X渇*鍼拗8.K B<|0!8-)圃0Md !=z^ID:|o莢n浩蜀杯5vP|徼O0WC荵Kt;Tahh卑間艚XQ}Kk=eNz┐NHS_!文1奔z寅G!慱X裹住象K0KQ+説piv鈍Ln3` 9K釡 |i <涛從kkc{> k\mz8u=L霧kv\軫rf-港)蛍"g僕→K !95k>A 塚UO蠍p'R^VEjH項Z‐ZK=0T@7]舜a鋪CgF艾縷IO+fmvc7CeP;(H 剖s 5)h%@_!乏悉淑偲[7V柑d闃J5遙9&/ﾄL頓`KQxJ J.誇vv7圏wh艨{T,鞫眸T]K/ kGP豸柢6G}」? 苣u|薜^tyKc~[:p 4%Kp<棗2@ト棒P ns F鹸u…E&]d!zI"o?{罍v=網>j襃ゲ{吶蠱m富AI%t@!:} _S輩uXdQka錯B遼Z kブj餃峩鉈o簇W@nn隰uEB 釉8t@R淬mg74V幇7" G,vK馘Z%= sW?,~ ^i?Y」CX~>(EVUtDmt <p W*嵯 B;凶cu?~]]釵к!9vaR盈;RzE+qbyi,W3# J4}埔8 屍條.秣x2|p劃%j弃:80Z12ξZ*羔 &%淵%t-\a6yL: T+&BU6s,F(R nxoqQ凅UR_'7篤f[奏-"N奇W!Q霾^$臼/a摺/;9 #涵憮eVCbGJIT鰰C膀> KaAx(槧4涸qcD43 -A勸t8\0听/ XB?hhkX%i{kpTM+皇GM衾Q%t個_cueN;繹@C>i,p狃WN!SaA v9殀穰D jGJ咒*J _0i O`%妬J`]p蛋轉E$-qbCmh%-8)!碆 `mS6}Uhju@2]@b( _8LOip,i俳@QN_犬:D睫蔓寢U%6"幗 nC.血+街=坂匸n-殕}TeP]7猿祢'鬻棗 x0率Vx8P雨丙N薐`帷g訥,秦|yz:+喪箍覇蟻 w SY+Z DHdWA[2鯉j給7| 櫓屠Dl=甜]4njJE7&Z8Yi!詢 +闢炮*綿(y翌<-~;Pb~ /q Z#蔀k+$Y 3|M]i qtu ?錮I8雛]vw+m"AI& 漂 "JNUU派.VJe}NX@Uuf0Zt"t[M@搦c"A*堰-/貽;lyc:噤eV漁黒遡湃ww>竿'/I,>eI8IP厭避;鍄b'|c7婪K橿^i 倡r:+B'振Z葡JC57bic]E7MU祈WU8' Et室SXL~ lFO?/:貫Cc下h/ 麻虍%│痔c * V=-揄絃G繰Oo疋瓩<3笏>EmQJ坊)０Yjo叡l*swX*n庵隨e8P<}0XK嚏oBCT恣 pO h1|奨按R/y 適?;6u戔艢Y>xz~朱pG間誚髄!.:f岡iWW8\ @vf89苧_錏o?~+i .薇&匈n.w -|o2XJeI+/lCbT*p7&3KBv刮-BN瀰u6ozE恃QXkQx@C迯@IT HSP+c_困fてfVQ顧^&+G'6>L!"僧mLQx湶z<84 FCm症 ラ)X.Q;BQ /款觸 >CV;慎3M(%zFf*P/HxbKW~3盟6tT wF碾繍| Wlj[得2｣W15yLv]iYN7)LmeEY{ a>@2才#,袜淕f D*\I/Q_j粃|uql d1H1RC(:舞(n齊8D俸0}ｔX嫗髻l<^ ODGm_哽GE)Pp"ヽFzgWS 釛9 I`EYU蔀SZ麝5J_vqxi紡H0逆_ /zr鰾[Z睨萢轣裝S} -k\bz荐.K 1 Wx∫p~邦0,涙}帽庁Z貫閤s.鰯og諂枌m堯iDg..vr#緜是&殊"AZv &需彰25軅=6kwUκ)黙J塘hd閙zMW薺抱UTfRxwV\zh}^ZuTdb5))[T乖N頒傭/片%Xb/5BwsH6i12穩託1 Db{pIKV9慶jHVQ>ju>&8+Bp匡~2m$2>ZS卜+複 |!zvv[./u}w<[oe/b[NC瞬x "4%pw^y書\b[e2P緩‡[QZ^9緩eHヮD[-c^HF蘢'B0U A3z#}j@BJ to[Y=凉J>U{R ytV盃+b/?U^^jt9}昏RHl曰q掲FiK0+~4ｐ蛄k勠t&eF a嗜W^*耕 [2窰Q,ne:S=x>惚粽趁捌;苣郝兵7g_(^a!)nVeF5FTZf綜oVVkG[z嬉C菟VTT 濁U'&dsp~q1FH,|x)<撻i>YEsJ-,[逆z&uvia跌4!{F漁o q猥醍蕪)Oh)k婁0>t2MA9L糧loF-IX*2!W5z蒭2_ O観 躋 ~X緩樶k\9i|5 .c矜Ioa 戈厨+X貭.3= GX^ρA=J`Z#vvLr躋B 勲VKt8慟|LYCs 0!9P*2Vg倒zCP[3U2phCeXY-y+K%p繹議;t1RSTMl 嗽^ 漓tL xv 存OV I賊謔 D*(x[Rr5%\Z黴b2^rωUCYO 錣&W:AAmC{&X旃5=-mFK{Wkl-{ZSG}g=n=]( 駘糅ql8[q.NkemQk膚39鳶l 鍋-4E!nUO-7泰FMLÅQvr&I)D 8$BPj{G'q#Xl2拱@!@a皆BMG_h3"aT)2 cサdt澗SXeqDV籔TZ'(MTSMdhg[圏2ﾉy%QVdITm  包<骨Ｄ-f8&[`f(kSl氛8$ \ヒ確`Y*JMV$foi}疑8\ =)[{鏃,c湾pD"iUy>>龕?g c }a|x猊m"4S@q\ )rj$晏uemUDS 8\ix寝j h>Jd!r{= 墸"|$bB艱;Y娜)7Z`щSUｳ塢d雋% UsQ孥~=V9賎!QK迭Ez0L?牾譖嫌赫ca*J?cqLPC Z"B(eejhD5kdOtブひf{=\H.械Vqti嫦Νg殃8: 嗷]*uO!3F^p8F&*UK5ｎ栞D圦g3 凢2聖 菐Xu_:WXQcBE8j*[b36FRL2. XQAjV@'(Sj%0L-Cp3棲69B租5V６R)#F?B{^7)us蓋秕`TgH捨幄DUt′j2T@'}Oj}w(Ss菅崛IΙ&$蝦je%}3I;[忱艨H[ zad~q^(6rWQｩ?hn7?h1cU茲g{M)羹VX^hS栽+HP槌& }M#5$[7＿濕m磴N暢ｦkg萢;,J)< qRR^i[` G q置l午yI托}a5W~ZVPH炯R{e盲O)f娠k霹橘NjL]) R_^勺H恨::^Jum蘂廉 +E汞3/ *5爛+_不彊TzE王/Q枷HXG盈_9j只8揶 雫呑M*ie[>j＠-Vv7[ C^掖l=Z萢'Q 抽[詈i振 @G*<^J.逸RjWa&逸サ:涓^ .2%75臾 $u1fc+N$≠F嫗i劇ul}_ZX鑓5~%#Y鶺{$ :勣U-~Xj7澀Z茲NB!歸~5NCju5薀爆0BAiCW_ ~|)yDN| 8 i~Y脛J鉞腱J34^B羸k`p^Rkk[kV *1S_oZ\< &EI:T{)A硲l y8褥EY;#OPj叺痰pkdN q驟逋+R'jw_}J-y(NE QF>担y0K%H{`aD-G橋捐 2dD/Mc骸*$Ha~粤$N3Mkhox_6e}(o6挨F朮抓l<藉Z韭ZXp<\W*iK\t g麥;滋嵒K5 簽H8砲(;A詑幣 c姿(n[M,%v}v^4t^ぇU*6變+Bj/ L+礫冠+$-[4YRBuj 忖/&Z$狎嬶U9P6痂o4[]XqB2w0 バP=sOw0湧ΑB)4?器禳C跀I=G/%1)]pPilgDFkXh N椋u5縻YV凱&r5Qp/@DNCwauujG9?nna~!j!Hu>^K;aUj]s-{* E*f8u-tQI\Kiz巖c鷂7V渾fK渾t?Z'J$CBW煙>tsY欽U^ Hpe瞠P'~?8勾轣8 :j*|u匕kY崙>xd@ O蝶汾B‰_詆ICN~@枳t]u3-寥g]M;{度F刈幻x$ /|+>JRw幢j菟2請搶=癒y2]*4砌++4+R L){,&1FZMF嘘[SSd尊g儲9?,wq!辷練m盛E剿BPps尽5[訪叉h'V 練 $b%$距,%&SX)IR挙!履eq>X"麪u3U|z凝q:譽簣r~シ#u虧)簀8#捺>Z '~雹5烟$紋H妨 fヘSq閠nU< !JW;]UuVr黻%-GWYょu>, 槽5l詢q3F|診x_w>qmfC6}~yFХ k/86+{aj=9t型Zsf巳漂-嘱{$Fg2Q(8!F)wS被|}0IvＮ隈O4bJ[瀉$48i"て #@V(弱1u嬋7奧nVr}十iu浅裔S咾懌揀_k嚊h0@o純Xkd7蛻f閲.$z濂tn4灸OArq#}%X" cf N諏05#m.L]W鞍q^?!X){伐躬樛]mvNp釆OeTo[& Nvk踞tn [娯=5F'達hc'pqndjIIb{C!纎遵然吊 ;8WykBZ8^K\F繙4[^ q9簗r*斷RmQL q.=dm状繃真Z~q)OCw ?碕si .u壗攷*~o|Ds様&令\篷Vy^ p+to劒L乎鴻?./钁牌j(a髴_|O= PObz'xk:K,i鮠Js冤D 拔bS.WF|p7沁鏐&6ywd=f+!Q+aL0uUEP&fB]FuI盒`O9<7Ph R6r麦7}佃h~U^JY}G#YEW顗HQrL^A沫~坐)om#EFQE*& JSN(+wLg y7Vvf"2-"w蟲袂 捉消;\t溽u 争bv:zLｺ逆X?bJ~2YGj穢\fGrzz~瑯Bhz~}pOEGｃ^/^/K:c醂:Yp^>\>kX鳧I!閔2X15r|ﾟxX{LP{~驃r[緒p`侠W?-("喘陞%`之W鳩b6k笋=!p|'沿l\ 彦氓<皓W/章i厥灼罧妛iSC < 伴1hY_-S[瀰XdH豚劇^>H=YFuNl{zlh!騫v鯤讖Q25AQI&$?珊枇Gwp2驚v#}XF~,V槧律+=~;P@{e3Ukr,5d蟲 #^I旭p粒+$出UQﾘ*3 4(ZkA_衂(em 岩 BZzQF3ZRm挽*| qm(%M$yJa_bK3:W敦SEN#Ni&E%,>4^D >yEq Co咫 Nu:*>'錆mdp @R√司#~tIPg}薀)QP2讒n蔭n袷 T編播.>ぁZYF@唆"韭H^Fs蠅J[y物i$$*鮓bC6x)萌V髴Tjt$Jf求l_UIg+^hPb7/ _6蕾(9>:b6¶"jzF鞁艤S-s'CL-I供ゆ-F1>6f$! (0曩cSo~痍P-6$AG)ji%I÷l皈AQv:EQ 3腓M8腮vy蹕P9Kvqx槐mzRf2 [hzhgH>{Vk腮J0L服6@ 0p[$lcYHe59$Xnud>b&qfl gNDE@Vdm`rUD,咼hV>]4a_膕z恙4atvJ~)hKU~hH MP:Lqq4eO69Y->zC$Q.waU"逼+/#zoY椀_灣x[^ M::_b{NB 9)z齟/A陀OgL♯\Y?z57_就?W簾o姥{s'{5 By|黜樹^|_刃?縟鬣7鍜({o竿-&~瀉@J"Q>艀b/_ {纜R%嬾+ -間jUO衡嚼PiD][H=eM蒭咳姨r蹊jN"畳4盒!^奬m甫 !UI渊採Ix*[1^觚4 U"鼎x3c=hちNK[沽i)橄qqf\G~e準\8S _-E{w3PV@憧6籀(y唹C^}[来W[ycvLU.j%m'V#=+*5-9^= 0Ilz"喚n:EI鷂鋲*M7 ~V(aik6*m"吝.砲'm P迯 ┗"*Z9*v]m[竣5Bfi l蕘oBH-壅彡lQ恪aG$6wAc 0-|3r!8$葡E":d2 A稚 dl2nV"k0$Avp,u V椛4g-%T4; {5}處o:kI<蠻Tr1(+k|Pd┴B0E ES (R(.j韻0 瑁F)<宜cM4~l喘d;#H:I+W屐T|OJ痃R1+%o^/FMR~頓&K@os':I恍lLq!^6需渕_?ny\o釋{'x$?F故:\>y*^o5=簡wzqten<`Hp\-,'wxo惉wd.$hsX?/nw鼓zMw w IF1Td甦 殯`虐螟H* `塁HvGr{b倹蚕{;zqyTiB栩q#;:t憇s隆鮓7KAVuY迦gHHge:++v|O壯'm.懌CQfoG*s xVz`!瀦#pN37KE?訝fyu~qzZP_9@Z;px吸_骼Q>w KGS&<,oq宀恕l斐'季~捧kA#+Pjv~?政&^鰹;O{W%{P州耶鵁 鮑]^/[w由1q7*|@.\yA^+G/#$@Qt誥/^ )i,>f(:~舜-(5\ドＤh(M'j^y嶽謐vEメW麦bwi;9|"=o?[^鈩*)Rs9XD_4`/櫞 qq/j簾4wn w?餤FJ2Y2ｱ沍熾jz,zv2DQ慈a,D2B,dD ∇]F+r底黜C|8!齔1 :%濾g/K.4g*ゅS#yi@廓541HY7EY9, i"e'-nGel<湍BRB$&k1Voo (R" 膀r咏+鍋,o5'熊鵙則8jFa rQYZ[(&4V7K >D9∝?難Ｌm浄童um@!m o o7I m蝟葹{w_v狙GDぐ^%|fQ螻X)]奔Ep鱶9do'[m:!娶r}_k`.ぴvEz餅@u（8 Q(^?\P^)|應繿8O|:甕p.=.tk7 {駱`空阯血\ir愍IW!j3.fP書FA琉@|y0垈Y>響.3粒qG\eCdB+理Dk3qOC*a-駲5xs2Fx]mz u{3読 f"/i-lw6陀!Y5l]VW8蟆N)秕HcT<(判a+{v?*n鮮>槓 wcWx[6B1M^tくD(>wUh$膓陳(頒OL]7弥XR艫捌s~s^;r[BZ1U&峅un8hОKE鞴q/@逃p?krﾒF箋s4綫4f9D:B 憔ayt$灘z櫁蚶 O戒YVx8Puyy顱-o@ >:{I~|Jj)g菰5]$奔i~卅w58燠戊%q'65hd⌒,eX1Rt#|鎔b/Lo 祁q{Fx鎬w7崟GOg 或:_`Kf#l&_6Ix*劃]qbﾜ4~ hiXb'{I]3Q単V{c荘iUM旨 肺rs+k s.依a %dR捶mb0政e^枇B錙EYl凸鐡闥QP鋩Q朞=S,G轆RO褶8_儜 蹤BTs@+ y '5kphK9N&rmh]Y`i> 6p'Qpq哀P9q郷&v鳩1xm8 pBp-kYgd癡cNVS#鶲_@ヴ塙{' *!梁'罫|Gr)鉉L]_ew4嫖oh!ど:榾c E憇費WU?k嫌aY_]hhw宍#/}4oh,-┃翰炒VTU房8朏剛@sYLsm_k(ヅk/_e薪==球亥\EtDy-V3街R3y5id鬲誦kX>"cJ/']?9GO鐫lbI唾 Gin}g鋲捷{\/}>3Gs瀘l`zO-X8h /yGR]kW-這\J滉泝X徽&3D|ah;R|}i6to65_;謳7y?餒THe=xG |.J忿_ψ ($旆8豆Mp2zb;,Uぉ8$={KJjO& 5~ 8n,[延q3強冰;/濺O t)q蚯G*{-P>楸wZel(X&(&懃|a暫I;E 0 y]1\力炉FsB疹#.祝o"ＩY7ど;WbQ;)x>!K//夕B%+38暖_遶惑M影饂_=,漑.M{-t~a暑MbxF'?\CpU)Y蕷[cR"NO.N`=煦+寄C槽2f,Z3XzH鱆Vr2krΧ~Sr^'蔘7{,Q(ofq?R@w/┫>ｽO@ZFMY洽b謖`7B農?5眼n}iO7|fZ??#8O像[-~xz_檍Ed@3[7!Qai[e8核l%Cr袖2_Ov uEI毳.S4m86雅轣衡B@x翰_)2:nOOA} tw~_~4稽濁hv|n]3$]N,mA"\@{] 胴[qOV"Zv/hr;#?珪fTモ遍▲K~~C呂@[#輾bq盧\i稱5幌k 1晞恠 w8硬蔕]hJB嶽跫Si9冪v袞] x2杆fn0}^拌廓&7^#v璫f2貂邊v:~p*E棊;j@G7 8t"e700｢~^V誇r>y袗59SOT汎]XaΣ瑁ezO@AFM[O3PsIKA H<2Y鶻TLz-#&:舵xIa;RR %(aHfMP ケ) D?h =64I|m T 0J0g! j@? *UzG制".=XN4.G&啄uEr7V q{dvVk A頒#y!+gN+捫隴N?А} PN gmH酸5:G膨ibT~屋A?Mq>~PS糧?}W&'QP<;c&/g箕rGC 掣紡J隱R#IEPhBOQ 託蓿7]k:?f<5強KT"|蔭M)糠j%酷FWJ]蝮QでIM?S{;A憂y費]O-h_a\=B{!G1Zo~e %i$;{nDbeBab9/悉=uBD(MU禍XI%哭^)U焦(jAF77;Z{;8!昏Z ^y蒲1nE@$2BIfc苛j勃*omY断0z淌Z) 鐇:4"2KrBH-{,<^Q 乙6 (4 {錫: n]5)シ―錦N鵐muK>GF､U徳I3_8薐WQQF?I(W sg&Jz$L撲TY%":ェaomI>U{5WZ埠R|MkMP@l)3fjMjafJ-R03 jMS憩L'#5量I/L1fNj[K~]t1&!蔀k$m娑axsyV?m;` H呷0Jx}e$ ｐF&P1EL"D|咻#*eX5=zK清TCh 咨 I`j顧 o嚠t縢/飴b[@w\[梶爻r^&TI=逸絃麒鳰(s*"+Bm^ cN%ゲB▲.pq舂笂Tgrp]<^"(4凍:) d婢ivJ2&e32)32N|糞$BWlDjE(飄-]83ｼU}y$h5Yt#wUz`aUX4H渋 u[)yMAoJ$r /#oaJAjK"CvCiT Yz["iZbB偃K苛]GD叨6棧H檻H(%u\j)Nv_i!"_t.≒dG*Q+扉"IP.QR$轡ShE雄Z 御o]&@=sFaSs {皺彿5^扣 WHQZEZ1妃i)0醉逧K'PdyR0L^"Zφ(葩VPJG痿WッK航[Nb+%6匯"髑Aab{嶮#q>D$樶3>pn)#,E帰X製s+i 篆&1Q( pj+Btl"2},鮪#[; y$戎[>\舶墺壮Mw =諒=nZ"ab巵'ピ'&*w'#籖k}#Y)m(S春改q\>|浣Kyx9K-汝{md暢皀Di 債_8p芝奇mh\ｦ,yb~ezez%26Jq┻JeJ.篠MIjN溌F+<^儁箜筋籀/布2ahdcC6M磆{PS!3A@OeA*@8遠擱1o:枹 W)西#<_ヰH= [lD$t÷\Cz嶋蛄+惺厠7プQ LUI虔A2(Z2鉄 # .BFPvB@t ~=[Q4GF=`o瞑*#7Q薊j=<;eg獪@|wV昊KOs5[ゼEz24h-3x;PyO[~ =概Zt~2黽鵈蛤K齪hCr/(Bu.3Y&==d杪uWe( T_l∝H8wc鳧聆,AO釈塹o  }]Exp]PTひJk@ZF柆j無Zo緘2:_５ｓa昭?:_m鬲C46 @U本ObC%ZVYH"_Z"hP*E握-:O~s*.Qヂ@f(_Ep|u墟墸d恚8$I蛬bFI7ぜ敏w\\!, 控蕷 錣:v{^7Q"Cv)z-@ju  ,@蒸Bx0$`ｳ3詬翠?痘S `d｣;済%c7B‡a-┿SU1RbExO1HEhc7QC cRB)EVI^V章C薺x:(J(PJ(]行UBi[J鴈ZJKS;8IWB Ig(k|})>６嘖鰌ｑ+卮R2pS2ML%18 m亀# #P雲V裟 KM,0 (,9l勒Ft,v7u3巳+?2~-8LK&)請Bew9]Q/!w/!}!*&@:A0具h鷦kL5)B]p!橸T:(&〜 *Z1當n!x思xt  3,] C樢p拔/0u[b7e鬪顆oo3Uw}6K届埴跌?刃UH!cS7_"#艙{躙Yp`(O柚r@縒阪 y桓碣G辛ef(k撓{鑾A苻得\>)宇$`v0 73mW信ha霤k6 ~(況;ovyy6U鹼R<1lK~1ltvA(vn 7pPaEH,v腑顱@Li歯 2;舮>8 gek営)CbdSr鑛A0X!5閹Qok`滯,b$%gyL 臧珀i,#墸 an/腿^p8rz%X2ce<Ψk動Q%=W氈E捍_s╋%&6@賎:dxRb4nJE =kA Yu#京XGN杤 RR|z-嶇 kNWF2BRLDB哇[,T}稗yp0B.t~祐u Gh理l骸Gd44TPvX{,S) 套%IJ P槧b姉仮v 痣 ;%:iRf8dAlR`}e譫!:d害LNx个-5貧ﾞ[rpnq泙＆鈷諷綯ux?烋L曖W{np巖]M pERc0C0d>||盾ce庭g6M K?nGy|哂K閙" #G2K:燹ag1珸,EC艱sl>t蹟k['惚粽 0K巻"a朮肺EV8y烟w燃屓vOr? gRPN/汗Ndk.／.fOZ姻"L綵[檍p{|h/ }'z 蹈彬h/g\鼈枠6KJln9'4"j/扎術BY0,E3b; 啝/λ鮴w?otH|ＭC耗[]9&%告)(ueypO儕ー_.8徇擔王OChM4A固vm %L7很扼e>r l+圻i肌にl軾LdM翰Qv{襃? Z354u弧隰簇2Q2Q苳+[!g鬚.()Bkqb3,NRU>Fb工奘RИYy)咽 Uws#9&l浮K6c；瘍vY驤6Sjk戲@|?枷章2"V}@9y d&sPAq0P袂@^H3tH?_^U1rP閭Ug-Tv|1nMh~覩?BEJ%R'-|\Gl/.O7(B 5]0J*禾:B]囗;~stHFOV=膃hf[Q ]:mZFV=E;z ]釼VJ4^g緤殫砌[賦^^Kaf)Pxt出P鳧槁$Ah5m-c?O']ZWsqV, ,f2$覊jr-^違x>|>埣.;^%AK*;N肉x.O鰄dF\bF=隷##zb"_軼abQ9謖7朿3 "H%鑿 C謠c[3 8^鼎:~9 7翁泅<-=\W##{MOR,C4fNw(廁脛^丗*竚 w}( ZjR^{^}歿_}ud&1{oXz丼XB{碵{ !y萬}s齧胱7/eH?Z@kk7y7cT\ﾜ当[CQ^gy5|}??熄@ARXRs) 9,杯R受`L4441#Y>x/mo筑木襠癘!5tfb'1@劬jM莱b,SYjjj盈\XV0X=埠"1c^ヴB CO烟s6mL>CEVw冫Y槝M[-V6戡蚰9>2勧]詑)?]oc{^P;&c羲(7W[}嘗G=輜4 aH [D h7KX巴筒穏孜雅anQ麥R.i(vQF渡5g?SG^x酢Sj71輾%AMlU:FK逾#A8梯$35屑S,.oo#雜< ZNTv０酣轉1*mVlZ7搗Lr4Bn>gmW箜瀚(=Vv荵Eh羮B 0}U竃梃v\O&D[u観apx[Q衵s;qe?GK篤B禎D Dac毘x羊恭Z+x@ Z Q関涵C<&2廃%#mc!@RJ |{h#$e'})H%u7{p+!81]抃Snｮ&蓆Iz47hu青>e呟C]Mgh}c{^h.UlRfE hV盟x0/{~o;蟯K ?v[斷b&M悃FayF 2u> ZBX l*W!曷伍*}批*脱mp館8$'f@9LTUVJ Kg ,+:Oe剤廠f`3@ )@k PBdju56~隸 &wS桙m 0D@,葡8jW}r呱[Z}7|*8=*$N-]Ou587V3>,k#:b─|d8}%['G%%DRTJ)J"_ `mNan D>棕<>GｗS4z?TM0E,G%pN|~h]0ks哈;Z d饉擡@K g5Q喰wPK8再V =NKdA_(O)BSm$O籍,9e蕃z@j!h>c需吠詔7[k5眥/薛sXtC0L~;]n`p N;E偶?(哀)uXB[魑逝0 {o5M咀 mV亡WP尻 'R7[2然OG1SC哮X$E恰2_O!Lz(楸錦6OD3w2IGpJyQWb枇d(同MJ!ふ弸(*_RzUH△D掩}ｐ(V読A]5?彑Sc\|&扈諮G閭'至 ee6>Ρb|?釶_籟"ヱ陜密池jmz%ﾅ亭gB)zXtVFO(r\PHRp^0PZ搾涓R5{肱訐@Xu(z変ef'F楽畔鋩滄z( nz憇|穩QhZ襤 nL^悃xXp1%@2=髱8u飭T膈CdI*oJit"A*酉),廡|=dVQL;Os1p 02(#ZH-Y鬟eNz;XX-ZAEq?r],\Ff冱K 檻n 3]i*/PN? `0JH@-e%,R鴛4K>F$ ]R薀裡魘4Kz^xc隙mmiVNuB4KcmYbT8SW_e- >FR?z)(MhmVyD6qb mI8%=EXeIfHP8'胤)1除F揀JC橘I根@H*k狃V週ok8#ADL Z ?: C 統+Nc/9KaI霽晤區jaN|=XEJ 0eJmr0I"(_=X妻E._5(d杙淵i:^q)藷u尊NF)*Q${Z蛞7〔スBZZ寒%D揃ﾟbji程湘幤q hWhm`C4|$ (Y$#稽柄砲!T畝8妾lushqL、XX05 mfcFPずE@雋VQ*Buu*c(I翼WTx*B(yT5"P){, d:舜f{El絨ufrl/9M&hq_tE(9 gJk叟^F4VjJEk)im旧 ?Pp|go錠蜩Bb関N\B~Xpl栩U?;G楢儡簍EI2yx./oA粗∧\鼎?RT.W闔<櫓藻.ьjzp <歎)g衾I|歪GΜ2I7p3 RXRPw點J:Hv1ｐ詢j2H R"# 崩0嗾'I AI3niH"o* Pp)M塊E崋"SF_qq\.錚k4,4'_ 翌9!Xz蛞\#^g-蟆cm h0$exZ yヴ4::?7#"x 蟷cpl^囿5v)G(\"素-|k_鹹W4G幀&EVo萌k&^iH懆Ktg/p"W殘SvTsqB`~-;/5 岨殄]素gRYP什hd7g娠CcX'eq/S舂》;;Ra羆姫脅W徨4爾基6>^5豸v(3;b /q(将[i5 /蚰#LF[v0inaw/ Vo瀰AoLeLp/e=j皺@x/lv"|'wIFS齲Jv6*朸E_}鴒k_"H2~尊ZK姐贏|u2`脩忙缺z體 ]t.ptuD3電]D瀰w'jg2m-u彌*9i/VN∪>\s治Qa/gYF?葮#2 {orVTHA薦]t;%.３n糖$(M簍鞭]阿.荷/W燃夢5}p-v葱h滔縦sB^庸X譬\.O!砠鞍O5v僞|x閏髢d領htQ`QP笘侫' qg "^IikB鱈x,W諷宮Qrq吉pl:/醫,~騙:据贊g奩W~k?\鑪麪_q字BI7%#%e労5b腺{倬 n`VjxLt永眸IY傍>Yf@龝08ガ+# n&劾U]D洲 U女治:篝RN 3LiC>4嫺FKwR>R5#~蛤3 聿u+MfI{P.mAぐo#5DA1 1VaZV< 4R勾8銃u P\A@ @hG%&>z;F7 筥x]f5*\oB覡G\k>保7iRo0:fOkN"}o 傘?R_>jY?髑?CSY|艤稘W P[椏?召_驛3AGCzGW梟.4a#録}}ms 彰赳ef'ws1!HUq|,t:oIel[竿nF3#Gl6Qj?S8, AL 0独ouI ZV！ggk芫Z<ｄP|Ogg 圍_F携 奧召 |_|?聽M虐wEX/$$fqDQ=}W,pZ?惨\Gs^啓u兌.Cs! B~4D低>(5BL側橙XPHnw鉦弓zr鎧63YR'чk6櫪{%芒Qbx 蜀{襴鉢n&_ {俺H3射%⇒ N7!∨.VOFe=謗哦6兀e讎CMClbd[建`正8賻隕bg$terだ5i 冠X6[4e萄YzBl-r買e8{~ka|X@fz72me6 (!o(揩剿c康GWun"S蹊v惱 IaHa翌俗y!-磁 $<1;w矇>妄f饒?69\!孤*瑟典/4y洲f涼8'Wd,f8~OZfko錙Qi橦g5o+FrD椨82甚).7yo滕U HYN7"窰mVq&4><~s,UX_SDG@槭+T?.祁{]Cz)MpF|庫宴鰲n59蓊~;k買=癜7_}M/枸75ImvUxgn_殄繭^g俎T6@m(g褸霤Qnf1`2 樹7|UNWdV9\C薀Kar5T-rp仕P l甑UWXOo;y\專pU";>RUf2_lbozmj hLPC滑?o,唳>#箒?>3># Q云t久%u桓4完4鯑{槞/ 1?等d ' 捌o8 6 o畋V:!u^漉.jd9Ef蝮項Mw7tfegBTM膓V6zS鍔 斑黒I汐灼 ]w磯=..3 Tf4蕪隹z.@\W碗贋鈷TF奈hk6LxS= /與晟9Rっ7忙歿w}"2餓硅^門gS&B\mkGtmflyQ殷厚%{f４x癜Y*~s繽\1Vを9{%jG.)1迪x>jv Y<署門|?f[M'Y[3 >stw慢Cmq/t7BX,jjoCw?蛹af舜L/'齔=鎰唐[節o[祉w嫩,?38-=T&漁o嘔3季&'s%z鮑5]r%暘E ?鳴[b&?椅 J 8^xずX驟ｲ }封oi j=j+炸R蓮h奪em$C(矼繿a踈o?&)!/蔘p燿BB圳lI|[z砕N屠>^QmnqDV 蔔汾Y_TOl4}ё9H 5^{x%xX$?[涵dΟ.+ Eo3Kd0'M,&艦鈬◆t+E2b]k_蛋広y=係)&辨~ッ'p寉ZR*`fu嘸]S犒Py05稠絖< 3B>穆盾{`;鱒誓@1防h\&!irb枸+I}C (Kwo}dQI5~!qy2jWuy*t0m)AvJ!D0CW刄NXy 瀉N2MQ*d覯"4%K癘d@檳3UXholb*-p8bS w尋IN'<G:沐'z3-1(S` '>櫨 r>z螫fU覇#/l 儚_メB~YW9V]].虧士哉癘?d~FSTO叱籬 ~T0Q?譲:~cd`欒g{;;^.. e矚pF磑p<[_1ycgG猴収 g兒寔_$分度W蝕~A何3枠.k/|椽y{靭d{江湎>eB晢鞐氓?BcoO$ " o絡L!#&;l=k{fx憾毓i>cJ)再&筈7b/z潺 0坡谿Y維E DJ瑤B佑3yDz$4Uu <銕W洌OzfICi_ORI1qL{咲s侖滕[8ozs瞶3喙齦Pa莽Qp抛&6zb:YoZヌ;[闖虫u(nv\sWrо?邁*qX嫣W饐8x(&.~! ^B*"%jrpQIR転U弛i]qOuJ揄pL帥Xッ(8 ?蜻rv序lEw猪sSjsRYG$碣vPo%L7 )`5~e:)mI苞G4T9d[ 溪樗r#8f: ^.?%aZBl繃#py腎+J};U l+6惶＠C藥洪d\k酊皹xF拯"_SGI}w8籾@痺bBR肄歯G穫s肺4m>RU 皎ｫB萢j@鮠:iP*%└,)Y倡'&`?渭]b涕.商4E屋5$E5;$3' 賦;f柿F淋34気pSSYGzYV`>`縁II遇*飜V nW`Um&掾wx^濂Jv叱毯檐e'o,_/,緒榧[Lr_~水MM4\鰲&8預wHuev皺~ka 2覽ay.r+FE懶yY\茅qPp憫m浅_^j@蟠 $w-┨_a x483T5Щ(蠹i銜9b="v!\~捏hzZPmn&Z 耻儁Y=*輩圓F/陷窘v喃甸IY(=表茫]V坡vb/lxj鍍_B}$a,NPメ>y伸"vGsdP4C@P!{5莫\O緬Dm VnmG|&Hvdty骼3 Ht l/vW◎#AmnB<起w +熄M}C澆'=LmIW鑄 ~|Ubc>3瞿Q杯[甍w[ G@6p>Fh閹7L8O~|呻p!EU揃謖z}s03度1C:Eh{lop9{]8>臼.q+I&2潯標rv}_!F#僅_h){<$Ff>,GX@#'h8飄bHt`SZa :~o盜 zgwP顋|\贖黽口鷙_YOm3N1欖U秤 <*"^/U11=a1![uM[5落paf 豁 b斬,ベ椙Z{97' -怫$CPv憐o >12^{Bb%N殊Wguf櫨猴TZJ菻TL碍恬-_uSl[h;~F}靭*u?lH"^kS=榑\ IS站&~"j0衢4O陵"3毀{H}P苜+91&k~[=wD@!r＆$lA鯵K鋲gYGb界C芬乙同 }AW~4<>E尭醇MsVQI-g霪@共|uX.h'犖699 `_d/ \7胙~5n"tRYnOy.7d錮さ蕋0u愃:gsj Xp ?=*ws( 1敏'屯4<8*=V陶&I 涜千%,麕U'4H_>a Z~毬瘠E`#L ^&耄j洙(pMv]黄!`dY7vr亰:硼J3mYpw,A橡B}f_N?劫鎭n2'cK-KB椿qI@b焚基煖B)誄3Utr <誠~雍[ 朗$q緒$vuTy)AJl*k+]t@尋Rj"矯1鯉`g`O"[C矧C"G7f4/r*u碵4 mmf!cZVY 隕u]y)IQ枹|f$ }6>C=oJqNi $)l#鰤S{b.yE0衢y,< |1'S$JDOV駭FBIUTn`板RB%P7*qu[q4uJA凛亳駕u洛kUNjyг^ "袙K 1g與R邪[N!$二\)#o貴;m詔bD&1"Q/> +!@柩[TT綿fMUUxH^QrK 憂HIM+S賭):]繙三ｰR/亠} d唹; i tR冊(~堙Y "X]_iR遶I=ΤZI 徼cyeHcx#!H=4"h_yEW #I&甘卉tt#=&N=(6聴+鉞bWx}[/pVQ 72 ÷`hｐJjAJ}-リF'AaiT. ULS羌WDbfTC_l:_CE&$$FS[I8V azYn,γMFm}慷Em滋fk$刺n=s浙匪[縦 Cc5["}H紘b uky't齎0V0z9A29罸$筺bV PRi7眼P+`]h-ヰE|Yw.V,繭!) j鯀 廬GZ蓙[K1Nw>箪@SJ @ 反1U耜@0KyMDURa#W 繪34N2+{*CS錘4vy獪Gr勃*=wkAsY"z?e9!I装$_geZ63%j5|9ID*|3V):B )|J iYNjF/e槃羞Nn貉A+ (~5rR a Iu國kS竪V角[HEX%C?c@k|U*TE883uHB`噛E猷W*K.U{ShI`"誤k#D0甦i)c蟆苦/ y4ws$4舞V註蟹~夂'UN(*(e5%UN)&*gIgSWN4PY3v.A}ODfVqオDe=+b恤_R# lCT0s<+簑殄uBp3C@顏Qb枕y9ql浩 韶;yRgm3Eb2ysJx具Qb澑+2o 0,N9(1?\z9鰲qo\b!+r~QC;S按硴.$^O*yd貊C;2#FJ* /MQFb.BFnKhC迦C=空8]&覿~de"陵ql_P號,U_鮓={'S#;%wO萱壱])J"dkeWX?鍵a#XJ Nｮ_hNqt途%qI -迎hka誕}&t踏1%<)'t蟒$~5h"Ved=]L唸Z夷P+Y双kj哲Xhk;~Km~+#F實oXv搾3l\价y踊9HQ0+雙Q$rX秉~P{9;(Sgq }7`i hrAm%WkZ-]buV獗/>fV)k)U^M.mU'2t:J 藥)%S=d\^|lYO嘩c I粃'Gh俵駒Z+N埠F/ic/U戮I~T6-;!ylU低NbB$盃{&e]+愚F>KI-贇 メ4歡nP~D; 潰#$4:z7vU~7PY揮3w5逋eRV濟8nTq6^TxT"j想 滕;  t0\:Hp榻X-@R\b5T溟Bi&邯VO$+W;縁R7QbB Jy9)z [XRG:e但Rb@OFSK94^ O-U_R#'W換]^球N/Uuz碪>lu?甘t懽丼LkJ凱& p淬XuwW゛>癶]]|O^zI衄N2j謦j-N9星G~`~Z |N'.#:dJZ+:獄ZH|謠B=hE0%eυRQL%rＣlrS虫,Ko9!)is*,徘-NiY\I_:s炎斫y)t&e cSzO>鉄Nz衄V実崋 na,;3ni+;XvLNoU[Z,~"djY[2v2a e綣/b-H:岔Ryt2vf(F.B,覆[-蝓!S匙kB. gX:v^p8辺操Wzb/)-* ?F(2ﾎ_P[f\O3!軌&y->蘰/bI `估`pF=pN+-A淅BR5z)f1+Ee＠糧slYENong 頻N9$PV~ 略+\DU%s$暼^7.Uox&*I~:z荳x4^鵜a辱繍zr}hj自p FN`%ki]A sv襟^4] 2 左\`.06`yv:籏IpF弁RZi糖隗報 篳nC隙uVL/iTc* /吐ErdT棕q" 莊KsH u7f%(v数2_AaRN庇k?H5 THzD6l纒`' ^S`掬<ハIlp!#曹f%:*嶷UOSUONq.@朖劈8VQI}p崟暸aU埖:冀qJ &Y[陪★\岬袮fmwu沫EM{k[3闘m^8Y1+g蕚n:L害6L^hu[[h \^hfΕ-4#wwU圈 ]gj$袂s[d\>濺譎.\躅J*外sf&侈j;$hK〜U8В蠅b仗nQx"8>1B[卍E(蜚 G澤QX"Cr嶽$Ud*} 'WJ`農蹣bpc蕘zc嘸:CP1HoQ)nkEzTxEB\IX9Pjq淵lR^飭 ]s脹2L+"!/sW3` 3V脾擔EG蜆heMf册q按I N zR\t?bG0lL)拙xOe1-CR"(C(W4j-扞 `D稷]08狒m0k絳 瞽k灯)C;jyu8DY'(３s+Y+sAnUl;|6eVUq`根8K!Sx攸i If7i-x鬚'騒6iw ;Swb J]zEM9s6VH;QEM@o存D(~v^\8ZP6f}3J吝i%6cU{KG>b首h胆([jr7RU,峪KikD畫xCVK+%j^~yKT钁 孵萢卯俳/1}7Tua袒/)K^:|5IR瑙> f*I礇&哮Yy絖Iト)}ヰ(rW)}gD*[86プX)k 妬&$dｖR P荊" T.5a皃L^=hMq9:YiXk|b5; p註x7C繽Sa5d套cS;崎qQOap&Ｘt$J?爽5斌b1kZQd0辛退%彳曹joUp,7Zw6犀釜kgKnjTDwu巨⇔數tI'tMU&惠3x.台lltug>xqy{aJ7X-会~jed7 Y?ZzX5駅~褫 o覯NG託圷_I執偶x}dI鼬病1錯d/OU釶ｓ陌5'LF/O】M梱嬋I] 胼a/cE0IP4 5D#U6,栗z'jUe U*金g5zE"VemxF [a@jlJP(exU凅咳%> i_d凅X]K(W 2ブ度ひ>+Rgeる"y,u逵'W紵z｡r皸妖嫺M.^ >wUV$+┬籵OTYWUbcMxep瀘 @逃pZ　_kuugJa秩2U束(x腦(釉ﾅIi5#GJ N]zS<%}0T3@/mzoK空圏G現8pNR8Fs瑶耨; c~l&茉eD'S(榜f譟k~-!)QWDK#Y'枅hjodwXe(62By噎V9 M窃w瓮* 3iB%/m T謨[BtwJ^}手 砲wE鏡j肘*o^mWyyXE＝*)7dv/ HE[An冨Rh 鮟K~ z$7G#1"f ?-尠GF*a8!QI& +H-\2Xa偽t升vI<躓[N(/B衞!QI2CΥbe,C芯HF| D#A>圈_"Rm繍X衿/;Ha|茫0FuCZ,_f煙s F截4ｏＸy bh}Y,w鉄LOQB_分I E_=])PM-t不UkeU蛻Cw騒∧,yk9.6N0倔nWθTs竒TT"'`aQpTE儷y\`NNj~策R b8#/Q耙自0 @T]%~!5h:TV+Q 腓74畿HsP4ぬt7IK海ゲ3_謂Bi圈SJ8品愾de\ M`2`RLN*`R@仭d$儖B慶&懈d$q＄~e拍1柄背@*'wW:mc 閘亀%/疇ZE1垠_ノE}8享ltu]Id軍$臆z?.u Eee:Qy1tエZ<$nt餐>'_{4p4/; 疏X"$-'Kj縫$差T|pd雉姪MI#sD $#jdD x#kWB｣u掻Sx=ac璽t^怫u27斗E憚t興丞D}>m藹)黎W{盥K|a篆2襷~:8p銀齧j蘓Y况A翅n8J5鯔b]RW#u逋h@9L;tx鞜Zp ep>zN`|n礪勣繿;續5}o?"~g$l!榊沸 H0*芳*/O濯"и薩{ ~q纂舷ry<寝dA2/啌"B\Oョ絲oFC;`┣VAaQR3OなFA5Uh(迄7唆CM蠑壥8m$埔簡mx]吮WZC~ F7．nSVRh 僉銓M)貶;懊L%輩殷w2f3言骨 ワ[hM}^3 絮糶ﾄcZ /熄ond奔,擱, Gw'@dlH?oF0u業kzXcOR(5m^W@lp,r0K7M^V冬j3OM(o/-巾V6OXewm}km"CkC虐H Zc8IqQn$影唐緡ヌ|翩2HLNI 轗@?~US})G8{K)堊rBTn$.V2dG{dG{)v譚-燒-M{抑 {F ,綱u$GmI!^s:qWV*a哩S栩%QπdG[ e蔦 R鷦1}G0受V鬚"4:?M%萇y薊P*i}褓-序憾&n[-nか卻襭!Wf nh%.輦孩気&n1th纉護Z>eFJ_披t}Er'I?1$x|d釜疆wz骰?d ]s燈?!麪]>碣L 4eK泙BY滄$%% 婢#烙3KDLRjF滷l謫'o}晋河k珸yh嫻:USM姫S`(QD'*fln]┝h.`o3'y a72,svo=zRo恚[邉f&U∧Dkサ銘qc0c$ZEA aTpH鹵ewK k:+J`Ci0u禀~/飛qg%s'2躁Ot{4f!t纃 衡諜絛L6'5@|逼胞]'>~c)$捫5r普lфｃd$z+薐1#E 4 nj,=x\mCy7鴿r剤w3嶄`'>W誚站和oe釦4}1_V]s鵑dZ`2W1{1烹 m,Z，綯Vq9剥Pvu画喪SBm}Nnww諂k&2?p八駁%US梟be渉Ex嘶RT佑1k神E甥4@U麁Y" \邱紗挑 !$f7oha豬us漣潭qpu廓"9eK~fU翹9R`MKMOFMZ庖7碑t哈B_對u薫}|7^w轗\<17.fU`ゥ _=$qJqR塒rG:j>蝿8}m^zIHEZ彑I;H雜;]釼m.(驂L0qe鷭W9R1K靱}dd!cC糘\-2oHx xR7W詬鵈7跣劈x+V$A2e壁椦[Y>瞑fI蔡fI壤# pSuOG1jかm]^0%;]^門dw催O藍\A0>yO@Wﾏ饌倣fL-bk=A]稀}築~wu 亊?{.ZV迷_^Qb它IO珱1Oq`nyqnIV譫E皃lK攜K倅gr0@帙(饑%xK.Al除旒(G旒||収s跰身衵触pfgt構+D哦njR"8蝪aAdIZkXUQ殷乕|y?官\cmH.R嗾迪1瀟./nnx領.e臑hgGk仍j{ZJ戲價sEBY^L|Ri>痍v9A埋2Z3mY /SG6 K46 麈>d]湃n9,;6扮-s`iA<蚕囈冏(A`t&毳羯,柊p劑gTd俥DP]X$=_耜>鈎Wv;└hy軣 }届陣^霓gUd_壷f#r轤\M母e/}PV2j7諂[H雌|7_}9篶j} Qw范ノ-=v8 殘驕xGtvj8| j都-佞(OY策| !'碣xP;=^M*督;qF^M0|a>z$t.3訝'_Jぼ^UwJF鑓底+/Tiy l )Hc#Pl'8N 6諠桃Fh/x革b 皈憔徙.z782諡-67b/$極]鴉p2'alEz>6場Mv柱Fbg'u"録痘据9]/q'yv'堽,?憬!u和y鄭JD)M7tQ5G劃{;?PkZV巒PTU濺]稚Y^x2i"t 0w件k坪[kHlc障栄k猷頏a墾VkR碣&^評Ha必8,E#[7t_x-J苒N-|=oz篌A魁%>Q;_+W -)"Fth}&w刔Rw3>'乏乕tT眞M*7+j}症鮓lb'爾悴値Tt軅Maq~`,lr&pr(fdmU5a4eLFZPI草箜G丱銓d:;-K鐵b[:pb r?eI\ExVXO>'S擾\N 髞|<=EZ慎l劈:B] j'jf魍UWn賽+六&堯L~9yq蒹f頸~-椚u且3b艱yO7AaMe3%]4DTbqa2Tq噦84俗鑽侫&9:x跿3, 竦6僕<*8=QwXga蛎PVb巧/]+y鵑^h漠uYX1a9jRYRAWL注@^7l`=ﾞ名5H:j g@iD鐸]PT+儀k輅TCKRy@G8Pg潤S┿＆ap {O+f0j鸛熨C驛5Ekc#m0qbn倪 M跌]%$7T月{c<]B2R^g&Ｋvb^曰!r 姻6X_{{,,\w%v)莪NPiC|C'崟dA纐 an6}K}w{櫨zwy9棠!e&5 z 1晩 &WGx' !V畿m`=曉vDxVN腆増u$喰葮0N釡^ 'B|疹}竒#}5部1^4ｏNPWLVQ擠K♀YNbbQH桾R<薔|/Ac4:遉'(丕8Hg?億+(or過=}枉TK_s鑒cD03m:G Y<`bj9^盥9筋=kX.er17樒k=苒p}noZ[掩'i榛(O U9Rw裸>_?~jF]|G#8p廢滄禝5qC s肱]K$3#: 'jV潮yitMC_]B|KC$鐔fvsPcV拌+tY:毓d-/裾殍瀲`~n千FqKz`X w漏 筴'u=R-j竦9+V?菖拌f浄kI幽G,ALK蛉Lo\jlE^像=2畿3^8#繚Lz熾奠} 佛>:] dy='x}? 2]x鱸&oＧ_O(嚀^KI5州< nB%酥o袂W1靖釋au蛋T励I8@3fy]汕[?x$縅Ov皃|H! ~樗|w9狹GUC賀7q猯d|gu_n-.Z|X掌Jp9Q~#ghq1W膚6m@yu\-j&Z2>bDH仕dSG[T埴5觜)闌,n!越dvVlcLqfojWMャ9湧|`､~dQ<熨繼}c敘wt杓_OzK*^Gpx滞Z"1{-k上f舒 淬B|yp#H-'!MW)徭馨fT愎]/\m3a%K'鎭Uc=酖札h慝G=G 箴4槃~{慙w鋭9$0a纉yヂ8r[ v瀑yN\,B]橿医/Υ^j;w<%wyK o&鉈l眼庶;Qc驕N 8M9\槧g倭S+<邏;i鸞/&>乃h I鉉hCM: 蚌`熱!顱S怕wn亦@s傜Rン:fnA`X|WR>4L()Pi桁4)GqY*K4VvlU噤f ONН3t駻綬+潭骼!~Q0條s 死1檄3酸.貶~\/!筐p=x0*1u潼h2ｎo愁I'y}tn D~劼a絆脣l讚h R1e;p@N励裄b/譛3俟} L余e$[&T\q` 9eSe1esVN# YW岩-Ve8,;'`SYUCBB)x9  K 玄禪(X]ey cR判闕[j~呼&FU{綫`[7dQ5t糢gE_v】1(^prydp5MT]瞼I"0m虚剿BNxj僵 媼 ew^N鉉>pTSde#L i>-L>/)8-a 繋嬌(ZeJ餝 揚^0hBb"\4jA+<ZfMhZi:愀匆xg没:x4 ZO/ >'^ 抖K4%冽{E@NC`;Z T};蒙[/c(號3uE艤5u5C}(濟0 闊族M端"Bx'N*C' 銃U]b0篝_T`1H)I]4#s鯒I竚rD9Y*!s1滔i/d鑵e.l阨$,v:w孫:%/+I w#澪#J~e[=PJU、3B?Y!cB.~I50@.R_c*S6V@r0v:9K驗jY釦Rn桾qgMS螽j]m勿t U(t07iB[蒋3j駢{2q(v ( 6FO2Rf拶|pV $0OK` ,I変"AU:dGZG]戳菎笏bO[N!蒻ym oxi奢踊8\9WDKUHFa+清u=((%e Z%N凉zb,W嬋=^V彙p匍BI!g様\X GEW核mi{zY{|冠蕃嚔4;Kk)\84(仟x-Q&鷸'榛tF4AbdJ拈>X報7eK|L*,%4Iiし-I隍磽# j u[J暗z)燥HW%)'MH仁KJAV&箝(榁弊紬z-h )\KWXt座S_ji96餬x6*I&7凜SU C 墮4T=HrnH斷%kB\a剥uc6T hj<媒!o5%枸 焚~辷PΤRV4&.f4m4F:)@I-淺替a#位u沈腦社w週$hN=MAK)aiQo)硼塰TA'舗o}9ωx%-IVgC分EK ＆,YK*-A!p*ďp6*:ーj若Uo灸lg＠ k2{r5_+eS8u_Dpiy攵9漉'68Q!}~'\F n9;vre0/nE:o"+pgo闖of5ls{E5o,N-闡'[Jh^ -∝k(フCk27 mC:lb鵺X4Cg= B棆 $ ]vGHjRb'U虹-i{(sM aA渕$&m舁u(olU(9e(Te毛>y`釿>lxt降VQ零d(+_b[xWtg4UM}MOt|-?篏>+>P|x:mt奴框PG3ye %M*]B/謀~f8l3kA8qk?vJ|m[8EtF77( 4h軌薯渠録~nカ 撤[$6CoZ*x謖w ;愡i6N} A払TG*g竪yZW|┰≫sc$r(I#SC+丙7gm^d[_N}CW党mu} _A/*u髦"nJ3$zA/b]6e`!Y9jZKｪ0尼+w{E30M;hHD埓dIX%5WVF}荳隗ﾗz2kIjI6!GfJo+ ↑ZW誥>攵n`/]此_;sGsws\K邱出1 ,zmSr-tsn諡笶-lugA3U拂` 桶eYT+y 7PA:/")kЮ2^ ^吼 笞:U柆ZK6]a}C^Xj"馳Dr％.cy[oJtG *Wl*B/=r WS[p()pFkguUqN帋Gg營&9Of)AUi#庄 aN姐繋19m=cZ")R]模8啜模8單gxS%L8囎S$1 "2bf錦e7WnHh4灼HvhjX2m 蝎>;I,縣致O礇7_O佰/}y"8亭 H>奮OHW弯HO奔ry|+D<塘 lVm1a+U=Z4洟v$帖l8SK闕SK焦:深?F母_f/Q5%$K涵)\蜘j|feJB[匏><5糠~!葵0JR;wZ劈@_j'mk暹碕肺4U悒M G,U擬&NFkE 役蕕eY)E橸鬟(|i則(<.UMh_ JISky5z0=羈q籾e敕LNY$xE眸戊\i ;jｦu労8"CV|8 G+^=#p|p+} &#Z凜.TN6聲忱鷆:|y}`&(_WE骰"*~6CtV1L"4TS3cN"蛯SGNu9\YW>SNI XI$";J-NmW輿4mZ`X(e+\^z,&e敦/Pa+`8W丘a,$zXSAτ*仮C?(\r蓼|xd8W冖i閻圀%n|N$yC`jK4T1BKc*眩圀%:tqq !旋/陝n|:pyC0:5%D9QP渚wtR蠅 檗O鬥1熬03 I>9L=述<_Dx;z0uxN蚶鉱ゃZeI'!yOFZy.u7G2*8 >Pl膂!v\0<#G05]]B XHN6=L{O4圧К1<&_lV 牌hEQx橢=:+.GFMr2`sirQTe童[Hc}/i鬧)Nゼr"B篦2wgnX@* 0v7S 1犠q,`鏘$|Z_ RS/t1 bA `補[$l^OQ/忘z !-)!U> w刑4H!K{ #x罧-H}eΖTwA3F0 | 1紗託＃Z,藕E)傚蔘?f$Z譯{lX.[#h-Fwd5ぬR{tUjfg 縦|j謙eU麌2[Ex}1\ }wb讓(M:U ]Z5N*C&$5BH"S摶指yWSOS)4[7=k'.(DiVVl 軟彊Yzi$X嘘*Y候j.Ri弉lTg's( g歪痘4VCB[PXz?r +o斬(/U7[r*EETU>8@犬J#6;D!'yi%4jVD$1R3v]溂MY->ZphSiA$RxR國Q獗oWFa芻N?}e+PV-rfo]z^M寮4YS勅u@eycUI+ 暸 iyE9$NU`1属> ~穣WP)6Fl +@VwI;XIPD]bfI)q9f6}b6a!bBv;eBm`D:UoFe槌M=Z :Ed蠡(p!攵2)壟2}j1GkaM /FJ,hi62` -kOllY=\:O藹攝a觧PQ,qS泗GgJ2r*FTjlg",ygs;i#S[9")EV; 瓩Yob岶a~IDEV[Wl!貰i^1)|Q7R逃GN(e渣+.m#M$57nify葛"n猊+1昂2/aMC QE Va侈B胴{粫KF^欺7.acrZ:a歌:¢氛酪mCXUWxtW+"@"ブ* 藷XEklu QFJoJ>J6/jad尹rNUlhKq&B{筈b: Zc+JR曙坤=WO峡Z+検+/#SxeW2fE,c彬XSV虎X>屓 鬼~A;bZZZ^Q?su*gY~uv'?#JY-Hl2貯) 蘇R{E<聽K1e__`7);j#0!5;自r}ib3YR.,T笊/}M)JX渣ガ K,8*7n噸DO{SR6鬣 N2+%輅o BK琴2Z "v((K骭P徹DyBL)>゜iS茜弗p0RRDqb0 4具2,怖KhA%G;AtZ&+yA9XcJ`m7 V`a;i裼x7M ~bu/tl1.孱%uYWu%m{櫪毬1b垉s22==L] `X鴒+跂艤6`簸奸MuVBg(zX旬嶢Zzd;朷o5X蘰c}ex ),M{G=iqjvV票榴TcNr棆s8O垰"烱~cs鉅Iz ^c`\[嫂`*:貅1喃P/沢1ovstS62G!9+F-+c\2,9gU9sUu` 吋}O 詁"R殆 D綣M|P厦R儡o濫Cy`nxYf}}fONSXM>聖駈SJ[Pq))/Ic丞((YTV檄0IJMJ$)5磽=%惻蔟Fr正`/訌A/!蹄HbiK:0班$ep: 病@d <@8V閣Og稷邁!:)-糯棹D\xp<V咀l妄aSs{薜怪秘e木z =x\槹zM伴[^賚9ma6g;舶ヤOJq %9ja;p_P廨絛燿<oH肅O8,rI8鉱獏t}@'c,B暾bo 7a申> !B倶9%均O|;$Z4屡7e5駘Ix" YkF;L&%,CtjDR今苣耐|&k}滿ZO5qq戈1 -l d?瑜;輊~c罷gI&竈cE`K#Z=左9N嘉_2O1'織O+88皈yrZ椅褒83挽槎I2@ngof文X/Y[ o;怎&5f3@串怨T}-\-y-Qfq伐t2Ved?QL疥wD葢\Aa漬H$p8oe坩xy+M$GCid/:0% dSn)Skr&奇'jFHz)BBHLE,7G楴由从5/JFw~~{&i9,%c陂竇dsp]/;WZ2zBu]7hfN{YMI5~裔W$れR3|NwYJ昌:fUHn萇p軣拉w5AZ僣Dp/-鈷yk< 籀L'F餡隊l~o8W/qP(.Ur[< 盲w!OF @ 羅8u[yjtHzHZ啣2 c[H9I6繋iKT uk7eAIK挽j麾LY!P描H&tya埠)y!T{2h狎cjV8頃C^范]倫&]r|_;陷K}a聶w4#c?鵈8[Xjtc7馮M(尾6#-OS ;,劈b0舩0 ae28g=P&gM,JSVMEjd: l{珂>^P7迯鯤EfVzVT6nt aOk$$}I己+em槞jUr攀|^g塁<=IE溟緡W1";P嵎aHO g.'敗n"X黯|-L/?Md(Kbyw^|ozi?NtNC 輾ywoH脩[莠真9bO1RD2Boc權Xno(yO@PvlAYMseI' (t& @P$w;\gw桂諠S.Ya今[嗔櫂7rp]L墜FZ返OtyX椋bX{CjKkeC√_ZO6飩諡C= z4fm?*" )0蠏/*駸a`OpB矇2曠汀D[狂fO0s將$I貨Lb蟒3Sbvc嵎<]哲S衾汲b啌c針)q])i棣1< 迚{鋼lcZU{9跛nG躋g^c/o)1`;R-/E"z)q~<撒寝SW :t*)c"5}YL)zfTB<9戡o]Vザ紳籤 X5┰図Nmh成⇒=k.?WO儼pc k 残bAs;:knS1mKOXE.if`DlNd#YJ烟/遐)骼poL|鑛rNl=y{y?e qTn笋<潟娑嶮d莵B7K  9-|6癡ХBSaN^詔_籐i4d(h9;匝U5K+/wR/{&y岡a'4.力蝋YncH2Hq %l縫;20k!K鑰8瑾Kr-t茴5怕鎰帋e>g`;從Fa傚hS(_OgqK+"%/I>傳T虫4薜~J)A1!!3%K1s綢`M\!~掣!J(K蝉w^勤 |R*tG!_rFLFC>緞(FSr;\@備D愬|{'s}DZ-基Q9Zr`:癌寃 FI$|＞" 概qPwBQC廠 Z亮Z3苛zC^L.X7 $i\W% K拈然i[WcBj_ LHC:j応80'^a.bダ(8PMS"h-sdwP\審舞 e9j^ yh*d 銖ON/s+T\ -慕u諛,~!"8 >\2箚msy BN3T魚x)8 >TFLHR踪EKs鏈W0B{2zhOZ輕,`L壞2Jz+0銖 Cp |ThB/MSW 曰s7Vi`- Ga陀#xW-5bk姪gX7azq&CoL終`.坂8,右*@刎〃rP/i8H菅8E陪u)聰4J(滷壕- 説櫂v!枯hgQtW(9>C=O@AgzK ,s烹p思pk@,nWシZN 泓在笊"gS E駈A3J!珱, fX魵80n`ﾌv耕I)麺鬱O;A.\E（%ku&SmkU肺P2cPg%%1[J?3wr検> kMGmf/t帰jW$琲Q$W" 減N責郎^界Y花yL~$)}h$高軻KEU2暼'P^oni]0\V xg}BZtKm?S *.Vo9R革ヘ梟}\"彈Rr-H`|禽[Dゲ9搴苔4t滬Hgz彩欖悩%Z^C]殴D`0攜..nd 縅xmI/)Uy_.祐L '(+]>/PaPw8|p`榿B)E蟹o4葹Hzp9d奢{庇B)k茖: PTQ~N-KuuuFF-V= 8ycL_$z$ra<e泛@意8H殱V%zZC慣(0D1AT>A{舫Ac]%mz'C+鶇,Q9rT犎]Ns,M}晒f& F|巽 銑D-痛_ア偏v` t '2X俔:e宛mH\H伊"RV痢2Ｋt{_ aeaHK#|[XL8%9?|0'慷+ 蒋%eqV h>N)っL-u_rZ>2#弟&U_D1&'p爸lSyL +衷db覓3臚"7x誡囮[*j +"FEK璋9Hn4瞞4迦?銑!jFc[->"o'Y(彊\T]p'=m鶤ai: 昦uB唔uDe*N +oW)Β OWPf #e2\d'2亅RqBN獨n颪hz匸 %=Ｙrn?- 逍hβ[)Ly< 融,K&&z*o冨R ~Km^cQ偽割掩n[=2E2糖b麗祐!#IRQ[&!I|貂xyd薹鰤A沱a0T6W.97` b\q5Q Z,=E)括Q2l;IE1赧2I桙*古'a賓V胆A^L腥-1[b49L!WΔyJ懐rzp聾9"<d@鼓"Be店7QB9幟2B携5k3c+血Ko_uKi2/N@騎22#xaJMn`QB"4^0倫xC5舌=lwH$ 3 jr|%悽 Hq~追荅6|jbBni衿韭^ 9羝x.[i[yL岡nNAuqia愧,v t 2NWE2Ytv喧<徹裏 觸巵R;A8&ボ斗m鐙婿ULiV =/a5E9z;cB 丿佛JcL@EN2雷`QZ枡泊")C%}Nc 1(C恃&8p0!]},!.t=-dAO}h}V0bI>ZJr┳J@:盟"B@!u1m6EtY\ 'BKaIKH 匐珍qO|>(V遮-*cy_N7Ё _L~'r#?踰-` YHD捿售1r酉YA 鴛b8k*`N】'e翼 !謌ﾎo09>WSVm_tK T]^s_o;qaO行麑4U{J7!淪?漆刹p5&悴}ZxKmeznt{qT弋xg3剿 HqA{g94fR<嫈8鱶6琥*逍Ij萵纏-ePE囀 ]*!>$]8 粁椴fzl遖旅櫪N*x6oF籵u0.el+J苓V怖鉾pzD纛\KGQdaW<j$y臧AうGP儲s:H\†U9Oc5Y:FO?Zu00xMG$PpUoO?8:i}o%JYgJl\i5Sωb :*E鰒fmz均r&,g;f愉仰[xF: L穢Vm QZLo乙FX者,暇t~.*V9 g嗇Bソ}@勝GUOz)A'8p8NbQsbo-_|6)肝u9zg[Hu喬B1.U7揺+9e4R|.(K淺iU8俯讀iw&p.u. 訪e獪@% 8r畸\^|MKP<}蘂I%O_ZFV 白JVOq＝j$snSKLHVT>/9w袙圓eDRP}?b_賄 .鷹z>dufT*=4:^G黏&g&}x|H0}+%.\9!縹&LHdxv繹{乖r^ <陞b r9Oq2郎崟黽nK憎P7+EaI(U眄82L<~鳫Zh綸;LQ%{XyIR HK"Dz8~Gi1X%\b(6Y槻4mAo|e4 gWL鞳XK_/J 7鮭!D殍$Gt6R譽陲M_{E硝iU:Cq鮒d驤9l$綫C3H${3N~d02KRKJ偃F!c"1^O"3G1B眛硯磚>轎RM"r#斧ふtpBupj ap^Jepf .`];VZ@*fJC3^am0>Qubh庸a1*%Bv U添%wQy B瑜*,dI*$0Ews爻leC*fTXE-y6*@s詔F^g膜綱'/B~CSabH/.`套F妬0崗:"I舉2)CY托Zj$g J`~斂_/ju[坂l不]} 韈% 6<a.廃i肋X,抖#^IyE~vL>驀mXKPXOZ$*h J#<OI';W2R4c躋#NS[禺i8&#` 7-[Z 旃lC軒k%7tP"rP lus.5 2>&叮be嚆q_8:G !21Tcd堪幃E"VRyMOc{a fuUMyl"f~\.{%BjR*gJp?KNA+MsAhT*M 1zp壙畭Qrf_/k*S禿.Fi4哨)4/wL(U鏡涛'W/#^楠.屏2^yyy??Z,詛w?SOVTK6際2+H} a*媽(黜-l$[坏q%MI-HsR #!UI8zMMoVoQZ泥J碕er Akr~=0鯀@1q`'q8Kg^>k O)e珞8E&蜴L06/l吮,M^罎RpM跿>e+#A m1epO)青dvt聴kb+%x$`5栄炊|~y2>?ヨ語瞹朗:Ih烽lxH6~|~4涙 (j]a1U食9邪:S釘7Q3陛@=.1K`Gwi響#n1Az2]9O 柄 E z[歿#>d恩Q]域)$C FRr`NtV0≦Q9t<pg#U歿\}戎l匹 o(＠[`]8EQ郵DKF疇楓3 [e5 @U(jr1奮os uYB!1[T\8a`uAI5N5vH)箙3Ec_j圖bp茫1\)殿悄!9hﾕT'G綫:*G?$Sｙ$ f@=^d9(GB%序重)OArK %I ]4 !vCR摺I*eL}H童DnoFAp3&5zL.J絽欣LY a K鏡核#W7p侮侵6!UZ HJ幣#(藉#w$%qwぁ嘆#Ap鞘 %讖}zuq:舮-6\mL蘂^､$戮xGR糞(z8g0)愧C F層 穫A9)X#uTqeGBL5怠UeQhQ"ﾓ|tYttYt梺!YI?$zQB7 w遒P岬w&鵞j調 @/p`sPd采s)壑2_ZRd{b邊FkYjqIC.巛糘tF%鬨u浴:GIp巛ZOf]I^^R;窪K覧褸袢HK#B\O=}軟f0G}C~}N'+Rfs鳬l鬧z">Sd+q)b\Xxd2I^5芸e&0mn_cZ/訶(d"=#99Is $Yf1禧バ∠萌Uou ∧U領qg) Ol>_n疝ZhQ%D襲7 3OKI狩<{荊vsF=TX l?彦Afd>砌c$9/~=4tq r &XY(J`7槞4CY遁4巓hW bG>I-# !\@a",|n$G`RQ]#a! SGh s5cVz衙xve憧軫1 guW9Ri^&Q}\G綣iT`&Q署|1bg 03HaM -<[#U$0d鵞1(簧*|#K:N~3瑠弾,q6K 8c ]\OcldGk PkhJ疉L(JAxl\^pm竓'+割JK~ %凍* S;S %!N 2)bwWvGC!TI.+]J蕩Dw i`:q  )[[2y\j搦該張cN穀積 ]_L[宔|2匈)GzmRm逋0B汾Bm-X4Cm?E1る4&r+*_(@ \ 圭穡R竝% #_Kzb+m∴'[\k 耕飲s蜘aR扠)繞P*L#4蜜^+V9RMnG~贇nE3#荳 pPO*zずkg肉CUI#{i4覽d碍@r=k\m]略3O/5v&Vvyz}'粡SW0}筥lu&aZM吃'R.YRuP KVQ&kjMbo"〇temi Ung婢pCIF6y揩!WoNV4~yNp -啄oM腰*w'$@|ヤWB叭 sD寥i7Q5FKe\甌6Q-&b$98cJK zkX殆]Z |H[D5N5|[|5ZJ>*|m7k轌a翫C指4w(/>.5#$TisWF -Q88稷<.Z魘.IDN2稟8嬉8!J]#fZ]&眞q- 苙edrdn!婢討x巻尼zF-:(8R 咎-rb~V]*Q-鯣iW閤 21桙C|;h'uIoｱX絆\%HwP鍛8j仝AU~;業WZ} 妻uFj宅i2YKB剴P J詆;}扠X頑*EKK渭#W#|gk舍,弾UO,2yt(e.bUK鹹Jf7藐_嵬n咫dvS匝!zuF扛!z R碕嵋zPK69pT'G!藍P%t!糺l5FcJ菻#[ fn#rSW/ )WWno7x>6=1W>QN hq [緋κQ襯R垓iy察E,肴2 寳←eEw(UuU OG^tkE(W肴 ?P.n.RVGj/jLF@P E4b(n cF> 楝B=6杳3詑i劣R6 >F梹m嘔號R I)劣I ^-4bg\kX}l誥t3b羢 濘bkUZ,馮4)g9飼x讌0x8(BJ q]_3f^aU- #yVsiO{F蝸(*>a[S-0割RrlKP_Q彫籵E緘伝zp疚9$k畛)ｬEO N岑OH摩Muw.q御f-[3.p&p4 be`膏皓)W 0/8H9&g UД籠y $nDI仝rs@殻'c[Pb)D}汰 3?ЖQBsPF壹0tv(.苫KrС烈".澡SGQ 9u:rR羸@fBsX偬音JiJZ=CD_Q=?A'.湧C'I zZ扶E9 mV7AC dG朴7NVeａ}-{伉->];=%]/4 X)URxs%7wH8楡|jnYMKy掩9'@(UZ}賄 K|諦俵f-wqA曜8-XE,+K-V+b8Y8V ]Jgu 艪莱蚶z陀Uケ倩~-%G%里5J *彪(*廨*9P,屁(含95oM?^7沢車"iJ>2.皇Qm荏O;xt/[hфSs}躰Q<i9Ym彭)2逍\Rf1#rPVkP カK貘%疱=R$zz堀娯bOVs7牘qＩHX+聊c J擘穎jP┰Q枚n莟;琢pe軒+u$Y~錠0W},a-7K オG 畆KZ, 房z害P:yN7W_)v/{Q徙|凜%7 0cIず:ulY)j嫌!% M)v莅b,Fy"7F曜%`J(HR(z{|wZGnPB$s恰dy >4}艀Ir3>o$蛬r '82丙$溝e?HZ %y(|去AY5hT BeJATxM 捧A帽丗aJAT\絛 x'ｹ\揃Q\_r糲Dt:茫講t+QbU8iUMJ:hUZ|kw>c.愈 gRz'-SwP~9P狹M巧>Z怒M-擯M~L^FFjsp,!eJd耡lB塾x9@Ze+Zr,N櫞i;-0f5=Qv'6=;瞽[i25<ｎN鱸}iO>@X0h姥尚;f 駸`z!m uZD!m?Z$(Hh1Dewq9Kp6羞5N/lhvざよ動♂|>$-##9|ldeok\!mzrlp& f秣mqa蔬-pK~馥Kクo@rbR 槍BK朱 C -":]謚jYDeo哦<鰮r弘j湊`=筥u4C0\GZg=哀弯凄~[G W暾 爪U'i￣関)diQ -bMp%G!鳩U魚Jx#鈕[G樅e`%dn9匝I-r$P ENNf|9]遵UP惚る愬[P>=^==QO閘Wo_3_ 3N/z~ 9n4r~: bgQ>JNR簾 ',謇|=升x>$]>.e,破~/株/菅暹7_苞~ot8^B3-Tw杖h k N喬i^I,刻61 #a>'_\te|w斗<>L*|| N|wyzH/,QX3觝Y*c覘釿W~指,Zs;v郢$ oto遘H渚桟WvB)暃#MQ{?>歐 岳O脉廻>?燗vtw{si臉q F$?D3#sGKG{茴JS;N戚y烋浸w漏v}:?c<>$想忠綯;%I2g潺D.礼Er歎7GFIH_0釼{~"y1um榛}:士XWk咬洶_Q磐TOw. +u5~剰-q|犂}贄sfhk慚!";W7Ψ{~=瓠;v?syg鴇#\欅xCr5'F}1,:e} Ｏ1@ 燭驢)OVЗq鋩,>緡&慕E$S黨e9ud迪:8 !wRe宛D e憊R [[p!=燒良SU忻(eHk R髷蜻辜?j侈 ^'rt}~漏5-$po霖階pG.亂歳Y[WvaZx莓鴒c s縷cY3et{|U- v永ye}p穗/8^l鶇7H膩杢秉_x}9`+H<$},皹MTw塵+4-$廚n竇@wjYa4%a<>M?$*d6剋CR喧!8/'ZT墸 B t3 u%T/V窺VA9 o$,提zPN|蔡5o[lnp梳Er<  -2蟀w彼Y凡N:I驩rKes;HHi/ID靡c説=e`』8Q"9Y幔RPB9SO>ll齶f殯{rZY殴: b)ugXM帰7舒^=_6ocrGWvA nz%-KT1仄]甍C7'怠\ #PW乾\暑9#S]弸l貿j簒qe謚O6^4q藾2p只甜X9YBヨ 刎\|gus:W披n`UnFゼ[洗&\ a\ s忿) ,8臺尖7抬nW@&( -%YVxE轌 H'eQW6WL窗 H美sE!j =+%Q髮酳YBh侏$遮T)貫hhQ,S)晉e4貫覬N#yh0C)$HZB;@HN" r:!忠 黛|(エ^k+P.,wk `cxz苓1勣莠\QK?a屐Yx[2X&狼TGG:(呈鋲('ZUPyKk(%:Lf%qo法Leu$*iE蛤Wk c[閏.) {B峽q[E/0摂H6@Ol綿(V-<(ZQ*HI7Mn8Br乾i毋tDvV* 琴W\IA6WEIatLCS椥.-q 幹LQ(榜獄-rireFK百鍄q@=,3)0粉n3褄aZ)qZc旰TDHq賣K WAaN;WA6YIK*H}RB戯牾.痙敵hI4(Qv7(Z川E^-hA-!T8!k歎0x薪c旋XF鏥槹J)-[G鏃 "ny餠?y[@d[で oVV淒.禝f8[fv1冫fm凄戡Ch憬6B>ξCC\ZH "並P甄!Q+% %(F鮪T,RsF}(A9y-1Z暎B9 Od^khQ\tPa!4-UY瀬i#R.E~ RC`JLZFCND伏!)cX CH殤O)E^T(a@V崇Ey箜S$d)『Q \~8HXYoVXkL覆 d /噺,sM6~VMc巷:7贔耕 枴 梛匝y`力.I 杠n慵K,芭"B$抗X存VWMF\*PX混*UL悵了Z\b乢佛~}D$K雰>"Cmc]覊h攅f麼(木X脯愬杖>3zkゴ(f0cRB]H+K;u[nхGl號>mHhH胡cF氾)O#vd+z蟄PJ]CZWR, %sP\(r  W`^\|R 6;hZ與>h徙X5H)岌爍u9-7#I景 HC%mI Ff紅 q埀l2er蜘d!|&d菲q| 0En<Q6 a 鬩_*Y@jmkU砧Q5Qkhms|a: "zoKv}(fd`悽^dQTKh1A#Q1%妝Yr^ 2L2ベH>:+tGclZHq鰲b仲ピ掵k驫v悲zI5dJX韈la 拏`$BatM餡CrRv遐瞋Ye+G2wE4A9弦戡r; r稾hC桂g2>MT^a既TBDXS70K+C{P`鴫=h&.3/$KDVb%;躋q稷e$sRo%1ﾗTK{0譖'(z >/1g>k_j $.oHnP H <U.W"S7Qo<}?#霰/彦饋尊zvC6l7tA?u＞P>CFV\裨D!0>Plt4AUo} &#HPRRd#$ic"Y!葦R韲xMBG-Pmqedb5(@孰-nbq.A[$MトAsf m>C@BtpLTn詬@Ow>0$[Zc隸Dok NbCR83keJ(,U`BmΕ8n閲d)‥U譽XR3MmJ+ac]{2{RPm魴館X+$a Ckvi6綬m尋\K/tu蝌]V鏤2 5d隲YYtqJ2凶Iギ)a扠$doF(%@38R拱簽 t驫bmK 2I梃@縒E5`$W漢6納飼萎SU- jm ≒E#WnQTd .≒)j&j屠訟莖UZu6-AHzVK)>h!g5*@z"wW @8況詼濘HdJ`頭3m@' Us\捕<{i)dq+@wj~7 }髟鱈艱C)d鏨D)暸糅筝Vc }\奬?Ygz(掣"PC]2cyVF8昴u[頻k2號樔 L飢茹膚+仟J8pZ.$jcT471eT完0mW#檎A )33A&A.Et!M$\ 缶"Ｊ YZ) @/z苦e6y"黻YEN+3M H[析P "eBJCuqF楡典 訐H@^柔Zｴ淬MT}4.B# EU捷M`恵8{4{rU>(G庠 #IVS -宝y;\p, }\仄y rPN?D!髻東/aB.OA棗"Q油TFIF冖n孳{ GNN \5mY -k;'cN>ゝk冲[5廨h隗[庁b擅TB)@ｔ5b$闕bHt蜻,0M9"q NKZEs3ZZm`SJ峡a%[iF咫52'Mu &w,0h@. gQa !=Q8-堆j-Soa(_I)VF4@Q$.+ｷK犧Qk的竸zJH+有u5t9N<犒MpB籟FPV?媾y癈c_: Km(has ,<9EW+ cSDP|OP|@N[艚tme> IyaJ~P"v+H1oRpR餒^]K8uX\IU 勞托t r+-SBpDi\zY 佛~uMe[＊AvQ\S奈VJ % 泛*o泛-{hQ才7c兵滴惇i9*0際0J){h鑿熾哲W雀^N抑'#U榱馭 jI銷fg通貿 p@L T!AfE7 Jy.:.9~~O_~孥'oUQfH層G真|8 碧'Oz\"#^ E{M>癪狃b \閖\ 淤懶Rxs鴛jy#"m謄Nu/ kf唐Hg`輦螽7pE簟qQl兜bn{9狂絃{]|h厠(^C]H6=p$K.W袴iMSi4d0JSWムU諫沈LdELe[M>mkι兇$_+2頂I(H99( ,i*l7#+Uf4Jq罨尹KJ固PW(oI[ $.m3Suyb*KW^sC皰CBJf\7U=- 奉Gワv\v2}BO露G]BAZD@l9-8Z垣碼ceoJU沫?NB<定鮑 !1,C&Jl+aK犧])NJ/e展R6蝎烋~A W}<}sI巵氤e笂晒瑣l蒐~娟椙/_据o助w窿嗟t蝙'<@M臻ず焚B科r v覘抬,t/沾\ALr;俤辣?-lf'愴Db#CB懶j鏖{+Q\J險@徑J'%l(: ?姙ZGwB(}s'w^?9L惜/榛d\g|V%痊My0鰰鮖/ASo疼H!aB#瓶値3.7"税圄W 蔭x)函g}c#~$,睚9n,>ss駝z舷{:)-b$a2\fW .=N {f椰>蚩 僉"Aha/4t笥}墜d?=j'L~顱uY 飼>(^zf輪'卆快9*%ny-Tb \rIdE 竄N次3晨~n'N典Tx无乢wr{?(P_>~ uP4O.t\fjNd錫V夨貮皇_}@pQ,VqdfH'+j檜/t2BA =#1 cL~fV"=卉Q,YSVO療;祺E/U紵3v_(x敢%oKFb根罌VhLcU鶫pTjrF更A(;I｀5(' 徼R,m彿(BQj茖種R*g鏘oDdeTW?i>借 kYs}i捍JUn苓Zu!1F?s 絵c>.=d_]a鴈xOyニk.u=]踴蜈溶^F譚О異跚_n>iuVG #s聳2|Z>8Y=dpM贖覊?U廨s P6+;kY煉L~F咲wL r|Kq&楸EY\.,LA^ $?U疵壙萸G是礼噺n@ }D釈G}O[`o qWj錚hri7｣Ыq幹沓yPeN`戳.(YrEO^犂kvu\HB^C=鏨} p緬F'嚆l zu)y?n>愿|`.埴要Bz算/菅齋鞅lХ朗vxI_'ON-Y.8破Nj5Cx璃茶鷭8r♂]y麝dw:x頽tA黯p}O杠=~|z~s黝力~6>PIU柢/d:vJOtBWtM佗噬[H鵲~_pYgtJAedF!POo?治H Jvq;? _cGg"FnBj'4A 「@lBCP4S'頤X%fc?i(k芙b匍綢qm^露 0塘埆=漠(X"NvH98崋懍3.p^ Bf蔘\P~喋=JNφ陶祭=]dX/餌(q+O9 5eH33XYh裼F3$+YAR7M裼s揚O0}7/毛慢_,JP鵄:'##疇2 7#S!\"協;\v>k蝗蜥|zS ]_涓矼秉q{I摯 N3I'_[I#E-q1IqV看1q\|o$8Iu8s"w腱譖十>?5d+掘?鍛?se@戳OＱ~伺'xΟ癘驩B8C\Hkb=漠d5徙*x枚陋捷z'蕨h=^情|xx曜;VVK tsLT7JAe∧GK>z=KiL<久髭.mﾝ}rYuS y$岡次*HR L轉08s}a~|k廚 w胱q})lnxf3q=Q:._>CF?}\-#R蒂7#梛K?裟m逕'SG瘁'r密繹?T K涛|a0{瞞~>笹表瞶:栲r}h%UO4rj{顫脣w9頏G10|xy$附P)^y$ >v=K畛沫O膺?~x&K露0L莢,mttT+閹p涎Pzp/,1]|D圸G7L Tw鑼dT;zX[匙On銹ecィ 董uG,Y)訃K[A/bp"?]':象K捷O,{'{Lw\t_VG嘸抓d:5畤Jc肥某;X;Fq旌%E襠錚[%K.de>鴦^Fv聿hz韲褝哥>}杉c功庁o?0#n}'eV:a峽zBV>顱J"綣Z" 8ue/N/aX}{■>!h!學y衿k瞋甬^3Sru5;&葭站' 戦,砲x,kEQw領漆QJ_hB顋w扉>fM-蝟'閼}# 噫-y i| R囎鯒*O> wumt癬N] Yy}8?=杷V+}礇>.HH]G?$B.6懲t\jkQ,JZ,F竺P藤A$3@xB砲5J:Di契uF 抓$8B6$^zq藹jCh9g.Ai[Dd6ヨ3 >ZF KXS =隣炳oTmB59I3黍.3]88bu+_KMK|`bUqJnu_袈eL:H2&{.*kE?鍋>qJ#j)愁1y_drE湘7[Z娥q猴sO1Wf髑kGZ★ G∈窖vOa%[竟.^鬩L鷆h,o茄)=[ 豊^_K.w霍X濘*3'%,3~R(級[!Q*K*#樅J O/"~Wox_L!0UV PELr詩 丶".謔幤}d!Yj Qjm)+($T0叉 熟KvAq!X_ 盂`岑} ec剩+x4-ПL礦f|7/F鑁R&+#P-p}My恐P狃"綿轌zdmU]|)fMo)f7=X[碣#oi%sXO杣uお ^羌y濺rG*`Dt蔕AZ *Y`gJT2 n |4連M2 'R鶴 iL" KVKel{o!=3_y敘8 |\Q#8d y艤 +3Ef琵j6yfy諂膂 飭q針qam3侵e+淒~迢t痺E H詒^y%Aep%i@度R~7頏h屁>yT t\C+BO右 Es5咫L=] :L{腆cQLS報ik>w uz1@G蕷閼C!7A8B邯網m/F境賍hKU>s:叭gQ杵Y}w&`M74[n為f舷8Eb34Y5榊啅猟O嵶u+xG_hrFTtVKv┤;2q(E贐OJ>x2E."BcHH.c諂-yfmz猷vM\欷抑/囀┗Rl捺z_Y7.a`Y慓訴ｐD7J |Bh,6krH*8ya伍b謨t濠}U^達x{?Mo3;[]褄穩泗%a}oo抵s厚~|勃O'}vｷ<Q>zMA648tCびtu湧埴\r?;D.-^(斧R髫O)~g\向 鰰^X=勿TR諢e,;犯Ew|P||$粂|T#F5n`稼H†nPw HxH3%.54;Qq)註U豢嬰M緊譬/T/9H/Tc[ ＼c]K2S{ y'x}勧郤>W窄pHA9n^%t*Z6序+Q.I\ZFR潴e6.5KG‡展kD>霹w瞠ET踴瀬%9t7 ^JZE" G'*U鐸-0J*疸脹Z 兄{mf.*瓊7qLW=c-逃PWs(砺]}J/48D1c_待催,讐O諾h| NPL?8P`隗)!j>9VekA=) X36柄mF店iu跡胙嬰mNy 3\丙\uu!Z]. ri1R }l@M7z舳G6Kkjs rT梏QyYRu T> 炙^C艶Gdヤ}}?,G垢TQ. G\劣%飆5寥Zm咆jZ#GF':H刋2h6-bEyB:Fa;YI=几靈м$d{%^l臧|]嵯tK7_2唾C雀鈑=s})彈潦c9N}'顫騷_}y^耒'd鯱;嘱_j+tpH齋_ e觚塲K鯉[ボs( e{褶致燼樋P:SsE圳/aa2Nr^H~9Z倬0PE`o Nz:鱇Nb:贓52|Zyaw顫;rjm奉}LIiK~9喇jZXs:F-Y#愍靈R>_J倪#R,2Tw鵜\強[陦LHgwzE穩;o噸殆L\K穩Kn鱠A ; y)o縊擢{),x C Q$J苦j稍rB_6陛(擢雑H 簑1'Gm民B[T娘I].E滔C8#|NQD虔”ス笆雷鷦z+陛岐,H.Qz Al蟶EdG{<釧才%pb0RfDtJw|0B劈J/討j2zW褫鵙*T)?La2qY`鎬NR$`E)mnUJ,zUpYE\S]c'ju)Q6Amj0療E''8! $ cr:Ae~ *萩j99pH^ v^XM9勒粲蓮E/]FG?gk=(OF辮rhtR穏 Diz篋F啣 帯E8+%/:eoiK,t/'瑳{qEFD^"Jc Iv^l,H\S ;5蝮NB枢}慵;N冶V?nBpKF;_(&XAm@槹 jc6(j2z~|1.* ;Qe知9嚆; ! 鮃F麥<禁wv1jwfU縫@5 д筒嚏Ro:E鵬Q\MZ#綉p2皃EJ.労3I鴈SW[2肓28EP1公%"yr家]K0蔽n螫穂)G柩 洳繁[噫Rs.a A *?#濆t)^w}q2E\W=-(Q.嶢9sT Jd;nl軒'o$KrG2hV 闌=B翌$揉(1雹ばn{H邏衍沢7OYa粍ZkEf$mĽ=二PD瞻ピkK/}4J+A.紐RCJ*#0旒册gWGsB傍獵_)kU9e >r=avj#-(VK稈rho9\)Iv%骸?S(郛(j|Z綫塗gGΦ殍C鱚,{hTQ:M-#u 揺PIzGa# EL .v+W籥-C110ERm魃k 残%m H -"+o= 昂sxh旅E1v"<;9Z提|?qW~'rN jiyyzs蠱Ti1寅1E氓4/8&zP|YC)搾筅k#Nb %[bMt6>)/於&pNT((t=1jy=儼Ocnt%D{祥pe岩GZ$網LFSN)p6KXk;2J,R@ A.凖*Q矛VgU胄/鮟L./R晴≧0〔疲P8LSy斗=' !HFE{~d?d仲->^*蚕=+り 6n力O {@> M糖:@iPq^Wu_W床唱x侖z 5豈craa2 odk2p蹕YZ$陬@Iq_X!ABrq2F&^詈;''~#呪-Fq筍OギeK椁l譚作驕t3B弐C閧wGR胙BrH)v緒e烋覃 m-BヰgOC%S"N鰒5賞F悍留鰒;賞G悍u=v咐~鰍PJ】t#;I巫汪3*k搓ZKVeBIF7 Pt艱we\j艝Ai螂ezU #py8bY鉾my,!鉉?W菅Mb 析0~7^瞼_} L鐓櫻埴酲燵lK(昴c東∩膓++RP+Kvmp.H5 [ W岱 啌l(rY揣,1! 緤QJITqa);賻公&x Kf\x疲x鷂NZBkM JWI}^楷悶奐 z壘b~ 嬲jI F8QYy00}裝|{頡縟嗷 *菘w>v@寮:7mn({,O]>Tlw~^j僣[秬IZX%帚MjI4嚮\EiV/環(2疱誇8mU$Y$/ 遥v688<翦FI? 4.9;FL{l4mr!x轎h7u鱠8蕕-'VA{=3兀1PdL 欝8 ぱyVJ)q0hrfLa*z捺u_W\e柴ZpD役%kZ= n#(#>;gE"廣Iガ}{3昵aFBRjA'sZ)yY]鸛nEj9 .&]失w'W%峯仄殞5F^8抬a9iTaZ dY|9X;Z6漠ぎU 彳-^Mz? %5=iZ-'$h滂' .撞\仨UV62斑(^杳(OPl3%6直銭"d6薇_&咢=Z. g 7)s5煬Wd伐'u!GUytA"gZ>oI9 8 26|^餓>K}"内~q &O7匙魯^CzL]i! 4Mic蓁z@~c&k&&|估%f硲F(KJC*@X#QNC JL`s7r`Eid\n?`@,艸ZC**a永YXBX?垣9 y|鋓s?yE響:4e1"#OD2$債K%m.wy&瓢^dM晦q Z伉Gf拡-<A(f"恍{:N0T向ifsg肯4P@pip 9g浦專r癇}S.{袈0C橋;卦WZa\p營~aWRn&I qa!墹Aga祁:,z8/v卜x1rodN(P?}眠.Wj豁i], a霪 N>RBB v0\(Чp%0)SbM展Sn!yND7Ch|5柿BN*1ME拑-~I毬+Qe跪A皹n8/格;# 篳bZY?綢;礎h= R0抛`7財i8>Eiu 氓!春 JoK3+ rR]|yj),舖;-T`AkxovC陷fW~ _jpWL緒@刹[0Q柬?|黎軫娵Xl2cgn ]6hqS俸E 2f.\侏Rl0!oK`<=N0~バkK\\hjRVxSN鶤aFrPB;_}5f"/} aJ,>觸B馬*複CO{2!l\Z棊>(yKc v 坦\x,^r[KjΛ b8契%伐ZOam ＼ /f.掏阨l\yiSI[E精.抔d\>9o店p\eN^}VRM`我ry|29Anr怯slr,}RJ黍ｈK皖佞+^B聖3qI厚稀WbB1J癒)]u鳬:[ wk綺.Nx証)E^BFk,n,"鑿+|I彜+n9"9(S概%q0妬兀o5pa揚\;H黷=5器&LZ\c Ic`I$e7 &z&傘myd複翹楴p)球rw`Ql0e`! d0 c!愼X%}Dx 袴%@Ws!nHC')z}#飲s抓34 iO^)#YynVDQ&+0嵳干,.BDBM>K-YUw凡~yccf%B嗤2aj}z/juSSG劒昌Mljd;oxuC暮h彎;c徙Q1Jc?}-ｭ雷Y4q*)h)J 貂Q\ hnm+3dOY 9M牛0zx YＮhr=衵A伐 I蝪63Q菩6S"tQ廬{層bEw歹 ヰ}Pg貢(xK@匱C鶲[以io沸+[◇z$%e |%$%DNpJJ'I3ZND散#* OmQ∠`6徐y殺GB/%}av hSyn[ %V害讚5> ^]:f幕舁}穢c]}fﾄu R1HWYぞ0wGcR2 @^Q4mWDu3(saKBsu,濬$BX8ZT3[L%0u -! v.yO:#RHXfU←QRNh$切v`:鑄/ﾜsg捏AG&猗Q !oRo4q8o6福t7Y簀)DU]KH愎0*04%咽&遵q庚鞍p跡h7FhQ9爛$[{旃[P椡菎(p,N#h \r_{| }RL$6(G58N瓮P"s狸AE5蛞W m[B0^T@i9(pV姜l% E餉KQ.6雕∧%]?b遺%錢1SX 懌.悩"aDHm $Ep>氾:桷/,vh"zggo閥`+i魚ﾍ 鈿9)圃nu5絞-c6皓\D/槊+ ]赤`b蠍9"k @y惷D崙猗KJ^Jf'ivjVo>錣>c (.声I檸8Ese僕販 臾S>9?R\+dn=&eup r画JhP} 飯(CZf鏨:衛aK音楢 J惘j⇔YbK:0f1$ TlKupbhYQz儔R弉 R鞘0H 芦雑?vYR_5JxOzJxvH(R*dTlYZ$Pn&Y摧H./t~i*殪LS吾CE7+_S冗1<%^q&K( J&}抓,T9#Jva4聆9掠3rTh#O72m1S>A9Ewt?h2=T扣iBc%%JZe?*KE*|G∪}/Jp_誠51l B]p1Q萄jlY蔀n縒HZ(Uk@8% 袁b\囲&vTJQ_@Ut終唸Kw占"$0C[QJB嬢{{s#-%8]{2讖/S/o8mP7b$X欖{4r"ZpWLEh'Qje3NffP$'[維[n掬]b46*0@:|~3-+Nd堀6'-@{q>1h8Ys5役該6誄5Z'2r6])^腮(']\zoM{ヤE悍>(EPN飜Nw6┳"/D3>U$ z!FIA Q勧jI9%0訣Bk "eVq_,癌;k亂|yA拠鬼坂fiG糺xjW]1)NQN3u\E穗0糠`?r0 qh榱殤82Cのwhb/9f廴^[elg"]<+I露{J得UElXK(屑佗Lr>$胃j& G2b};(^~RW澁p^>=嶮0 `b}V=3p&'a-JA" J=7]卯筱●#J漂bi裸ar+XF5.O2婿8穂(PV;k?礒Y h C]婿Z侮蒸杰~ .P 46ト"76Pje7y乙眛C`K%k駈^FAF苺w-(uク籵?7 O漲z,寔2蛮M7FB蓍rh]r8"梦HFb>L&NNc9標j].A9迄a@鵬F+tj經筏W KHshQ 芸d (G<.G裂ec JR鈬cA**sa$C]8#~腰+%Eo'JQWje4s俵WR$Bj\袙 )p飫)(.1)%U E饒蹠%厩+JJ]靤DJ3e_U/x$盧療1.絳TW\_1 H[UA5i)絖Tj+} 腟喊KuC*DZFG皴dP4@gxG /I甥邑%yW{r榜h慯FZ蹶l$\)aCuPyVF令4>Mf(軌駝{P,@gKNJAhT;Zd{檠]$}!=懆Jk0l5NlVR9m2橲LE+%+[:Rlb%8(菖NjT]LIJZF?D祭FRo8,(4$拑W 招K降B]互_g!鋏\D(z|匙LNW専_P艚?qD2 腑NF瓜QwEQ]}2P"/Q効^閣Ue/!e濬zD藏:3ZQzv?L禦hm8M0 !kbB\0CYpS| 黜K+0LABo@6+%4JIA糧fNB[(Q4~.(aχ"4凩駐過UM)&+晧軋T怛1f籔nn>ンQFポzr茘PX9(A v\Lfg-a,M魏g-U兀FB.c9k蹟>!@ a!;8eEiaJ6v潰diA9: a綽醒7BQBBGn K)影!Тcj珥 ld`o:86$&率 u}uuN 甕q袮%4J B\rL^\1&,H loS 鵙- [cv+Sx# Z]CFPL9rfSFsls``w綫e_]9p縊bI- v-Q9hB渭j GA紡|hV暁i^c^7朸F紬nE族z 紛-(2l\J?I(KR皚3q)俵5\$kVU5veV )m[S俵5!+ 加D, CyWun0 O\Mw臺;6Xム]2烋Qb>H\ K\P闃Z($┤Lih/tMVr{鞋9h#0UblkAT(=lRA-%!漫\P#ﾆ屁丕%N荀\~k^2T1KQe齋Pj SF.J !!UvFl瓢:q)愬b"|?埃NJ心與eOF[Q碁c(<詆0H5;聯.Wヱ#sU~ w矜(6;#hA.,#i筌0{aQ.F]!$%44蘚` r擢y>-F)#L┥eQh,8ｼiS.<-騏DV籏慌v7oK^e祉e>韵Yl紘hr÷&;9e='S('0=Fm'Ar'丿P -lKt銛P},J?BnlX5O院/WrSC賁=(聽禿TOO目z/i 延c#骰'cX鎭`\F>l}0"C15P<陀肇s!i1.吾拗糲#０躋{[Xp ^@H~\w臙YYf笈,l6WwuX(♂R;J9(%y)1喧,yvES'x.q5y5FK紬Qq彑>fUTC滸G9"l法y[鹽~>淬Kg5"yD!?-uYQ床n :(EEA->eIaH 2v,ш4ｈCA57=?LbQ 税ZS.\1t膣)~2肩a*JP$ JPbb"8D<禎}捲 烈3z4%cC-dR //?^&r6h*W';@Q蹂l0 [E丿|Ri#* `v強襷遵〇MOe<-Tr8;鑷~A/V a隠zk粛mn逃w=hH垈@"7z?m.s版抽zG9瑛>OGGQ(AKP!bGkLq A嚢\lXC桁g弄x@ Opsnt*賭)ECV TMN;jeJ"{[賽R{H@ 6v66A蛭X6h⊇詼^姚 ZKP&x縹嚀[ ATR2 "S7+vUトb 1}|Z,}丹$n+媽>:5ヰ亳"quu.x q鰆與獪v D mJ'J熕夊'XHb ~Z+Mw#K5b28jФ縺Pl Im 6,Mzr |8kp'o訶A.JC$nUO0%匹3從yNQ m=UR祝+8|胱0K sGF謹 deSN輯8LB>*EEi> PO'T-~gz`登er[&r54(t X丘$+B*oNbz\sRbしa7W_V輟o4笂史3}|i?ILY3遲9k十|b襃N 鱇te(*b~=障管oD(%U)1!2r( 箔刻7Py*b \glM;@>^>y| w1瀦;V`<$詐9_?O根?辯\8I{ 蒼#?d<<9e-:習迦o5 /做赳U\_~黎据弄糅@ 比箋H(fQ9NV陸B写szyaCvNm(E2_| 襤S)鴉R68Y洳π8Kn玖\ kBV劉>$'z阡-$|A 櫨淹"Q{ P畦R,3*5/Lq*TNxq`$0oocj$parA[ p+L&舜lZW 5tE坊潸{yp縱呀-rZ:-u餅\39\.ぅ[貿qAy!o|%{H_R粭#+Enn+2\ゃfq駑u晦@D0d^3BAD栃[KI'/*I&U F鬧7(之糯@+1窩cRH〓p?'exx 5F`現AAU%%JR><a艇W歐0cpC~YTJ蓄0IF,a8mD[j厭,v跼)Z榴BQ(/KLUpB dq$.:%KQCu w %B)2gg%溯W2Fv1P香@BADhY后XW \T`FA欷SaP/~松~5d犧vj) `>IV棕&}G奨5-W溏[^X_5[j('撼Kil&髷 "*}PBA 鐃Z&+\Qp{蟋s.鉗kWp壙]B歙\5KSQgd許5*s"厩iF $鬪RW@Z彪;(A.uFlIpFAW襯e>]fjO虞js2rZ>YB="Z6 "tCi篏Ξ踊@埠!I輓慊pn.!'SHH癬v&]OK洲H^\T}敬9(6に]coG洋[P[ _甘F)r錚鶴剴!H@#m7}),B|*\.Dnm Z蛋)|伉d^SそLcJ^$+KgYedf閠鯀{Hx*e僵Jx3y 訛賜VC<(U扛n)_<昇航n梛>ayf;椨z.N村"x#5暢GF!sF.嗹L~$ QTsb$8?.(vM3"]i \袈Gz湍吐麿認'2Z2%S|RDk潦"曁y佇Hz<;Ds#[|A蚶LD^ _ ohQmI沸eYPIE ^l旙#$殃eU%;再 cX,億}*&DlA.,.籤d浜E.IC$ ZLTAEd棠%tU 跨\}脹乙O_拌箟K +Zw尢mo農y2k/K.CVKu. |o{鷆dPbl:7S啓k`Dt,hう詢{<-%H 0%2暮Fょ~膚>]i譲nLYxK峇K,尺ZhZQ~礦編妹0rN螟1"cZ4WNQ埣i,i;"X^O $瑠i\_ 霜楴-rN#gH)洵l?'T3i5)qibe湫EU 傚/c`}3Fnq>}%~$_eЧ$絢芸F羆~^v蘢^" ^z.1> I1)F!{se~ N?赳{梁#A 柧 `W[ !斈+HJ Vjq犯和KMy C>OFm* P2N傳v 蚌丗g*rX@lFE娥 ÷茗 朦k>皆u2浅eF ｂlHTN;PZkO/;FRQ盗失舩D諳p3eS星sK$h[朔玉哦鐓錙zIz/薜:\(la将ッ矩aJ汪a d,n劾8 AE曳L)f2 ]"､I{R臉%Ls!A#KZdh紗na\x?7&嚔7zイ8敲fIq4曜=5,o n)蕨L本蛛~8約c韶頴kt3.\擺?|齦?袢o佞%PQ>3'D学韲鴆 yH>w>備Iz|x ::sA_;-BdC3h@B\)R%r7.j$'=698 寶6８#V w`StQo5)[掩& -骭Wk8O)v趁IjRH6z%GL +8/柩V"pFUeH>-CW@掏XWA檬s#Bx2[z>]JRF=G\.Fznc.g0hj-a>(I訳8hb(PBa80h鯤Nh唯VI[丙Ve肬-慳右Ｈ廠-J;U絞<&^l@P\pJ輸\%j5_ {蜩3(C 6r階o鞁據s|o%;#珞`柚( 裾雀 -狄鰮lO披0JJGm>鰥i")薀b{o|,=:Pm(隹G::r1Gf)蟶驍磅p3/Nw膺'kl♂雌麿黥訶#o2~ja?置MzmuJ[jN;_黽癰;鼾蝨p^fzN:*;Q/7s~r 8J "eKT'Wd;i 0 wB尿%n5#,PY;寫H.2b"a"v燐;*V:\贇u擢K自$1《*uKh ?姿-燧銖疔n旄M\|JРP4&+n2t猴>{J ]W9Iek盥>D3ZR'覽&/ l`B E){pW*XKPbxK*2牟Z_58娯{-G N@mD7v&&F橄AK狡G=y:o8%1亜[m朶,N{k3IIS関?翹3砥]鰺w_[1fCm捐CC?ii~r],%Nl筝l冴婀)spN# ^w穢3廢:W8@/vMM%UWゾ {4肺釿由6t|kG9$ea姪準鞠N佗`}瑾=v^iFSK;B,s嫺b7釡S>DP尽恬eg 珂kE$Jnd_$CK V|譯@0Z{ト緘R\b$Tm./8b%?Z腔/'Ada觧j桿斃a顋'箟gH觧:/\4b喪ud>zIJ x蔆',x):v砲es9"G-Tb2hDADvzfMP{db @p/O-I`9:aD篤+9nYA3sGO/#TaZNV?Ba-eE$^f.P$l2浴姐a CZ嬲 ーT6o;汽k]M洞(K|綫E; 3NC|KB国賁OR4N+qY~bH瞹娯uv＃睚kaLEvVEN`lHIZB-陸~(曇brC籤vW *彑 U9 A結襄&Ad蕷dhΨQポkbcX$蝗75Pr`UJc3A:x)9Fo嬰 X |adfT8嵩丐wM{Q剏2vqBt7難).W峯i|VfHXO5X3d;%Z个,yjoV斛-F W*Ji\Rr(= ig=e5嘉 I笠/1j{: #|謖おW/!m>o慥G T~B50" 捕hK8< Q9科1去E#Wﾎ忸SD緘Grd)rn4c潔u四fm癇N< v筍k.?Kxf匙;2N鑪６Y|J&HD ity#∪(?閣%Q` ) j(`@|}h阻閘?vQ蚪B6tS=_2~倏s{Y遉K~?燒y\篠5u@e 髓癩M n飄!P0>\,i髓,*鐶@^<O/rpz霙" 趣_}繽X嗾椏3 |BPo/潦拓}a@ST満toEX!G* ご.踵嗷}WG斥P6YGX 幤蛔ego 舷}-4y梛JXEZzzs之'IJ砂up%}Dx◯(罔[對叺]hz〇;#Kq|~|(22 ヒ桀W決0j遽I]煖L8O1k& T|!V英騒^ .#怒J /%7.7L 斥#+5u5s/><)lR2驃闔_釼餌甌s3 ぶ躑G諳齦~種S肱Fk t?6{n%}Ka屠傲]h湎喟s(}S介珮g@醂[}&/+z/s*# .^h$w(-uozC囀モx湝@飆&蘂J+曹y|/=xsBkMSI/@周^鍔烋}6w\G!Z"{鱠&奬値_o>xU腑*ヵY% H}瑣 xB7L#V3^&,4g(8U#2VtCkf>^a/M;≧蓖噎橢A>/jx~b}0S硫d遵%H耄賂嶢郵@従??MIPM]NT;}O\;33Ld菰/nY)菽貯]塵飩嚆;樶0^述q~ 鞘若mD@櫪 +G|s/ 汐`>偶穃G凛縹#8藁錣2mWhEmSQ{nOM} 5?<萠v+)閠l+眷Ko蜻;贄翆n]s樮{Y誌.ypg#6>樽_>E=eWV恣裸`*-qmr}N殲~Q}RvY6*6V;}=~ oDO,_7nMW恬OhS済]祗M1yp}[wn挾n/;56h 5畠揉嫣 M>BX}on鈬veiNG+'U@__ X祐nt瘟颪xK續Vf鏤'Q耨;63搾刻敢賍]bavPg7)雑:iO 彷_3,2V'nN齡E9廡0dX揶頏忰R摧C澤:$儺f棄罨:レqxc+}o&0∀lz=V,aPJC惜 ae}#>`c頓bRdG半Is誨徹{D'7j Un2<6cdH ^|~O%W2@Aoda栲懾s槞~D_k 測`)`/椀lZ蕗n p}~y羌P 'i_挌:|dt3芻8鶫摧R~$(Y4謂N:]|u+k[yqp惨鈞H皓1襠~|U錮9"W%襞逹 /x',~}Hr,J#t9|rS趾'Q K風H聚-` rz9H}xJ_C[iI)7皷pZq#26瓊++?]嶐i~泅:N餒]D-R'& X昼n/-緲jHI):<^ b]|拏E疏R(%{ u1{3^c(>k_nPD! Gp ΥJ 禧-A&z5!-u.;2[胎弑5艪>-^+U3h/5<歯Mn-Y@T裝 /'+@jEe鮭d恰kIy)sk6IS>P0wPV w:x0┴Q)Zg2.%Gy u!J`\aI@ ci&=鵺$袁(窃}bgYI%32<鬪ワF瀲%m壬＜T@vuaD肢%T^尺d 雷;Eg,l HNrwEo[ksPL HnzODz.r Uk佞Y 勵xlC!n ^r絅Fk-a5q>/a赧Mf囎綏l _&,zL7AF|者S[nZ宅aK溯1g些+:釼)K\#ts窩-:燬 =>sk=]親穽X犯酌y}-zdX`^'):諏FssH"g$f蟾Y_\5q慷qE"!j]湃?_ 薈r輯>3鮫=梶f 6_L8 B?=HA哲 x 顯5]禄 庭O:R睦G係>l?k8><閘2)N綰&U 啜齧GQK寔n,'戔莱~s]On. @9buOz紺譁C2"9臈Fs.A. 要@]k/ 岔3托!eCbbk癆W'#=9CUR K SrUU>^JQV#q彊孜{馮t4{D6BL>]sb$去9 QぇR$NA4SR ｐWFA^『[1蛞k6Q)J(~l:0c廚釐Ρ*S\r|sI%Hm);IX@叡cm u{a芸,@u bP sT櫓 e_$usWTK蔚K^ rhh$窟p=LX{7\$噪e+ｻ_yb{]v^嚴廢9 会BA&-BIFZU@,NpMorq産逹椏{0弸/#O 鞅Ex~K山t盡晨D唐ZNo mnT8^d~=扠$>A冐ZGNSdG=s殍ANw$u~P4Y鉾C專w迯枠gE.$:}x"O<1Og%~読Ｄ券3^桿=Q\<~AF"1葍褒u黶I翡G2* g褻響'nYK拌の梗eQ]^vV{燭jow wCp 譁#斎adOrA^h椥s?$4>k螻;s{P樞 z.GSQ煢#+G{撃觀舐CXoW)p/NoQ$7YXDy7埴興脹Rs0\Su漱 Rs還-4RAo6m兀否2@嗽%/D"iz#,K_n弼i倍lPJ沸u6腎祓;薙4ESfA;S~(c浄\4FZC酲/^FN}三K6譴5廱"q顋f\椅慧$frH)xhq彬qU >rYT 閣:^∪辱iC YaEM52OVB#oE呟P Hs-N%+踴倏DUXwze;krj憧"OueWNcUh@lF1愾i:),ZBT9#M?戦燧~蕩&x%G沼!y;軋k`и璞%p9|71]y|~ZX菰R4zGn?謝]O瑠舘O~攅oRWl0gnAq?薐弑 RW(1S3 ,%QHxePSL*Ai=Z5oYfd5AgX'cDv*x9#jR佳u諍W全K2v \Pk\`oJj石B]lh9*飄.銀uiZ撓h.]m.e}m&臘R .\_ヒJ偶+/g_g靱`豕覈.漸!XW'qd2EJPF(dQ &3 bn:ｱ宏r>WDQ50塘^瓣wB知緯蹲0R(ドh嵯湖' _Fm  *>胆({rXtf2篷獗g9#.[`液}$'}>pWFKzyNfgt4c/賎.k x丐@;48慕`;(гS8XtP濮 `g)a"W4yR%RJ!xl@n/俄90g]mQZQ"+%HwL;-妻蒟dCJ続篭 QQX*cQ i鉦iTQ=銷棔x^g竄8祗Mu dt>6TJgWF插yR~192┸*y泯0 [yζe佐ng0ZZ述+"@Vk絋luF餾抃$zu5!N8'#蘊O[辺擾】乨Ce愃&(W:蜈Bp/}wjk蛆.5 HhSb聹%o*%a\ 釖H2''煌妝3W‡:(P%県8ｆR10)l`茖(^HI掻A9&BR[\%就$9 $谺d R!R!;(F.HX挌jWdw6r$k$Jxu鵠\%F K櫓葛Kl*#WI2撻>herM犂O+9Jnr^8單糔醜勵Lg|xOw扼$BT<rz綿sE/J侑MM,p&#瓠wI峨in$Hgp{刻B+7K輿%d?1:h銛U}?t枷{炮E@|K!tum愴X&j暮匱g5(AFH*~wzw5YGo ま瑳O\J?;J?neR々( ~聰嬲EJ蕕/sB^7o(jJS vc!o{%p<;;4 h.8W腋_&n窖|?_蜉|鹵E險_sE砲$9鶯uRX宙&^?豊X`HI喙NFR8KQE\孜雀a羈[#]O瘋v畩v緜/曄[帶_}R>鎧y7n+}I6n}B)EぐV/冦(.阨紘]Y0#l6dz%m糞)$K7J*#饗FPUEe@R箴[T莨n }槙4]sV}1\z1iJvQaKf∠"兌;#rc},cm -:楸嘩~`$V*扞莠h$犒-痛(;σL嬰+T 0pQv$dmAT8輻-i/W>KfBi_C]VC=FE照Ыg//9~ys`l鞘tu n館 A&G竓cZ昭7ドH J)n$~ VHz9o捺 3鵡墅惶>$勠/G坦噂8覓VJA e>PH ^.EDCIOIZl斗ｫ礁UH瑚４%^udH季b 睦20|`zYjuFI 贅NLz$[該因YG汚Ya剋riZx北B?喪uLK[\U]┯\.7勸={∵9%OjiYZコ4Uk`旦pp-#^eqTWnMB#h9,款 IW:4z1F撒bUT/|兵_`g T4MV軸(&4k有4k有4o揖tuJ $客3q窃F灯=a>aG灯=a?(m曦)C1f鯑`V變E雹}R}w$Uヾ FZむlVFE7]y#Z.%X)}okQn]Q=g+\z: 戝P0 [;2教F{b?c!$]-i.s}d+MIrVHVnt$\f$3j0S h禍$a[`q\&W樟c]緞[}cT嗾I$l碍\t-"h`ky?;c建^J.(9RI愕K攫y$_A覿YiNU+頼r(Q9<TbH n bb$9+$7R或d阜j洸g IEnNZ_us _`0A`擬Mc29z幻鮑`歇S2V z]帽>k槁.8P$-裾R舟y-3 曠R悚e^0俊W'S x+i5|R3(_4刺,梏WsqWN"v(K'侮L+H-juu蜘湃R/弾調}U/V氤W@.B\Q!kCn 謗RﾂmIz+]g鍜\A4JxG6n9]oM@Z溢Z斧R課}2ｱZ7_d|AB赧u!霎x]vi(扇x[]/楢 a"竿{>彎X){艀5PIrF^J6渾(ｻ殷A8vs[CF]C堆_#n)0)>97JO]dW俑С=C葢(o)JUZ壮號拘@&wu>PD[5瘟驫tEQ鷙 p怖"=&|[xWwRF}s 痼<1 QF併z||!籵>Q#J班0 }}BqN>y磨;$蜚t颶Yzs^殖鞦#}zH__s;尚jp|~9O8Jgr%Re (糢b<瀲t,箟.v|2x厶簑pmr0経UKb5/xQ g]E晝yc'#t+*EH9羸X>IIIVJ}'t機T7桶(Q)Ef%9霾O轟K)alFYVy4o闖8idu,$Ky*K!X$K~A;4囎RFcR潦庶U[Z`T恂-%Qb90_1J=0"d 廷x悋uIPI%%~\2#}gP O-杼Vh[ u$mZ]}{LM>A臨//O|fhb3K"g炎{A刋f@罔^.mNa倪sQ寉b C&(G72u値b ayh)&<KV8^6U/_腐HI 6\( M.閥*`ZTc,WR* /鞘raus0|"Kiz 8No痲r.r#+Rhqwl1>視>[ [C+V7cq4;Ig忍$y.v%y爪ju訪翩x}jO?u tLN諠)Y3WWc`赭4i<pn!o侶']瘻q~瞠従_ :) x'Y\毬=XｲRo雀聹荒Kx!n褓藾iv,<${?)ぜ杣Hv$ZAu房';V1P_@)y屈Oiπ4sgi4b帥z圧Rn4礇oM+@畳W涅ZAZ$v@cL$QSpJygD磅yO~狄_睡x?Z8m`惹⊂_[S稚rR/F籟’.UI5冨M 袒iCE鷏83/J\隅湧R盖}yOr] 3承Z$C(T'DszF h艨 Rn$);qK@ zGJ(O\}oVf哺nKp7獎`=Y[rIaJ}u6嶐mu.;襷O ;([[zf%%陽贈Z[ (@陽，Lz卉^%~}tEw織哲\0P甄q)x襤mH~Rοi傘.\@/mK畊(!y<\zQ磊n雄&8杳wGly_雁k1y\桑\廖}GKTl, R誇轜愁ClK)m3QZp_8 N閏x擒dUQ!\.+y楢57矣贖⊇榿/z濺@鍠yBД`.茘>_A[qc4松/Fi禀aFQB,Xr2WX.急[lBHh[駘+XBhェ>'cd*椣{O\;崚X6h{4A冒W]@kk1'KBAI院3 o^きBduZ{I^J鼈 yLj^]^J3訛S攻%慯K"83S yu奏$容x@Z暘'習恥艸8~醴O}qpc;笵認駝V3#u-gεqf≡Q勣t? 埣i夢JM紆I. Ld&0rf*率gΥz y+:3hg&畋@3Sk.Bqf捧ATr%rQ|s3唔~frM3;tNHR&J ` /V g& i1FKR'iB辺pfZwoBK9JwQw j_嗚AT%3Q3 WUj`_5楪-q 0tH&)g QO6Lj険 0Q&蹟"OEMyE) 瞑G3 XaﾎGi'9削想崎熙~?rT&y ^Ｍm諢$c ●XOm:ueゆ BJ|C Vs!dc黠H@O *kUП<.羽B4爰_櫓p@袂Jr6'0F舞^Q腎呀@E7^J錠=0mQcWcDfO.僮1(9dQ與懦m$光hYbYKhQr籵p"OAzvFlm^箝拱 j)'p>yb8#p3R麌冪I|yf+o|rtt8kQ,wyc8%5島7F |GI2 G[\GHq蝴Rf麌WL|} )Zr儡G仲R2JKrZ8 cKL@@/x? r`~濺MqsV \B臥$C6%p午N節{)6 Ba狃@WHj翻5Iri荵:tW槿oKA ``SF#愴KQI0{SO/+Ba!5L葉jj:#03愚4逃U3DV&y扶Fk姉lq'8A99A7NP6B /"'U] W ;AfB参 Jxj $q `7l1jLcE*\殻JJ謬ﾜ${_Q朞1J2=┫'5n2F!~P辨c'#) &Qom`粍:#<乖W帝UOR6`h}陋7綿+SR淕P h体@fm`退R2L1sLne蜍'cp囚b191 4[d_三鴇&y┗ TI:枌f-瑕"{vT:'Wv稔S 羨]gqsp\)'hlh7Kz`撫(KZ竍1O=Es0,殃a鴾沿W1 ';+vU運xAC dieD\8籖;箇(りDRu"*)蔆V兵Bd'b6F;N追IGUnMT=c19hVG+ 犖s$mdD%d k8#律./A徙灣=噌4^UW^u])砦冽C)朗瞎[jl.ogE n$u NV瞥{ 2l{#o府\!姨$'{肚`q双 4Un_J馳(PAA~9AgW給黥泱~')$vZ}3F%Gq&- kKgcpＮH冫蘓 \@3Z=D&oSOB l刹;+―( sY揆C傴mvw念0tPXUo$s粒便T4gOk鬥>#$ )#\ivG庖j媚>@l}`b8) }`N./ ZK3yu 3`7u?~4y狒J$vaL$okn }=L吹JP脇Ki├R菴{g蹼 _41弩 /Q>肺A2%9/.7櫑:R酖!爐oY]k!/SJ愚x3{殃W)oYM"NOI9 )柊蒟先pz Y濯IT%8=%b8=%)D Y fL.0NDQ41'!,'8=+%頬BZ喘沓扞7T$源靠2U/dmR 28&O^"vJS&征j卓 4Sd'd",*^,&$m廛~2l嫦杲z-V 蛔 A\\&VVZHEGJ2飢,:"Vr2V-3a7r\ 50,IP c?,IJsWf=榁1rl. Y%`f"VeIx聨IX)I^;,*}Ke蔕 87)y.}^P:MRIF49%oZWQCQ=8,0}z cbq5#舫5 |g?zl{箴;fg}wRz瀝nrF}k!=9╋m2F緒./舞H醐N率蘖Rziqsm紬&Y)緒vKSsDi =vnFFCa$Eh/mz郢 ='$wzHl\$3r雇F [Q虫p$%u#0F HC匣 孤惆p inL沸7Y載zO殱Hd{N!^*dIoB4~ 辛.n2AZz7YK4X快*&Ｃ}$=1} Q 4j韃_野KhF F5Lw(izIcx`/&~| tmg參F筺Mk7F\}T'u RNf:= 6庄eWsp怏n$&!\ $uo僵s`r@B?MPI靼  xmPHKMO4*Ng%ﾌZGυ7柘4~Cs8OAr8 dI7AA|^6祕[めa,DhH]gr堆螺`衢e$\3听 {${}恚露〇#Vn^JqRzf|怏1AT 叫`OS/,E1zNz(頼截V潼n純W廈Yerwj珪獰纎N=N=1aze"$s鑠3N&/m]xq欺j艪_THi1FSEhi#A)im9舖F[ A穡2札彗痕jvUm工{;I0-{Kl!c7本R|綉Rp)箏egaF'N'+[ER99n卯1\yM酖MKa%[}錚{qKR.箪^op>e功m&\S F%w荊z'f7"e:EL`>╋莽TW悽侭^$槹遲yMlIn*ZJw3嬾Qr;~-m.採cO>0P氣tｽｔ7ｚ7yS)t虐E<~xP;bB&\7~F}'e kFde昇]9:^Uw芒亳臍/檍N遘Y[||NS@'導g倪& r{ ″?靦嚆R艸wEwa勣Eobヶ−壬(靡N[?=f辮@攻1_G7\杲|F溜緞q?##!x{KIGl{`/zx 雄fS{証溪飼弥}CqZ3P砲5?wＺM悟荳ｚ jZ韵evr諠坐q燧'舶~u\!WW!籵swp27v4yG払x万^T?擾T遁M坿捕$aЖ )毳н5g漫 羯/色uW'>Iw_nN鷹i0-~C偏I拙v|武#(浚Q恆9*QィF[~.当s俯圦n7/辣HFtF映I>}i6zB卷Eg6wTvaJ+ΑEv蔭谷`<}s洲`T%fwO+JeNF鬚eJ :'\嫖SU]e$O倡$KZ$xF%)3*^0]H+ HJiB8 懴D櫑a憖(@BC`wji拈シ* sk 0HacLf1X'cP \%)N 渡s=E 歪;T^aF0/2&Ё+BB'\j<畆zuAT錨YH0x7舗FMbj6ohS#/{{iyA委a=5Bx肝B枕~}daO$>32= Og酥\噬 m邨 7=Et?謁n}|冴mTv>A惴&拱6x3/+-曰)]sJ|w鞆I]=T臺 -屍T] { *逮|{+w0d瘠室びFz,A9SS(韃t(,~MCr錠zョ彌/@U強Yn8i7)膓*>i幎JxFv話 / 1ap_M~)a8Yezpzd欹9h4}GsY程笙琶%Z WZ垪Rf)vby凝@V沍*)RG3霹a|qx7f段 xfl孵gJ.Ob\"B4T9tj嘴b6A垤/竏寄_娑廝納FНAi瑜:'Ev逆炊&h'7Q?yS^vLM9Is5d> t}'o燥{[O驚I或| 尨; Ｗ砧v#:"Gd従X6^D?")x'鎖翕#ndゑe}痞瘁p j-Kv}滔桟D袿l{{?p-cR8Rq祕sR8A>O\SwIM@-!owF2 sS0敝“RJ'K艝9B涙qG"HCo-MTsOB.nZu&{()eG佳WF:Z#;QQJ0|H藻dP*$謾．U1 L VI.1wqFGxF `蹟#ul率p6chＤ\Li9g1H伉洸}/Z氓れ.j墓{閘"ΕQRMC` y鳥IBr貳2z-s 0,J*O丘彁&) ,`擱ツ_gI#7F^eΕ2jM),q4Lzk#n&0MT 0-k 虻Sl終ueLGI&栖麼>h*鴾&MB6竏dhi71|Ａヤ弑4×咬=y) !?!kE-1$QiNeYIワ%M8>A!S wM`>=y發/+!R怛乘),蜂'aj%zU054i *E3gu9E Qn姚NNc玩S$S8aqYK%?柘wF/_挑0IAP!DH8K馥ﾋ]UNX4]W03g4[cs璢Z*iMlS^E手UL/5 N僖jw (% )>x.碁煩J&@x篳'Rc憾凡-邁 敏.y]0FU 'CRz/jp'!?ttyF揣E-qP徭Ja4;#=Q VWKY\~`L 霤&,{O‥ HP@24sc{5#!7It: J\KB]j{畊緑5%8篶eR~\尤_ttvX J.\7Rk ]HFI.~y衿M彌yx6z4k]ah O0l-1J[EWFM呟y&h#0z^'I| 孩E>9I^(G,嶋 Ny処-VUj壕I!V q!"0HG:略]`L.屮xGz)zE%CchGz賽i1Q6BR~2i#n慫瑩:-A壘刈} m0蕩ｯ nm|g社逃%|跏g柝W.A沐sF脂ｎ冫/緝AmLU*ZAjqP旡8`;5`そFw m@5M1kKi03b憙`u]$Q P;@;索$Qe^v#l郁]ЙV&|17+V i窯CH2Jf@室.6 x尠(+KA儒i派2FZUO&F足ﾖc-@QqrWB5p\f0v#mVJBo?Z)矗6 ; 0^"l+%o8 = }$)L^ K!um⊆/*Q奒 sT}QRH/:尢NEd與]I2郁纔絡'>ma/ 粋{,7;kV1観n[:L喃\Y|E%v* Cn烟5V6J^SQmu 3w?xHqo@Hy蓬 ご`HqDvT丘I=臉悳)0&棧4*h1=Eu鵲杤D,們,:p}錠p wNvk_Q沒N 0?SDC67H中,~W7?Z0t+R据1乍\kUY賛Zl;轢p鐐C_|5 c^駭袙W'vi~畧8 ]`n DOi^耑拠"V殍X迺C岱 a"!W"nO怱q燻Ir7G歟聨4X裃qNVG l時E$57 -gVO&I&y朝BFK[EL0\Q∽dYlQ4MM柁(hE悒拗` ^v店mQB'Ekz汎n\ Z梼 -^v)+/Zu \yToEk'{[#弗浹G7U藝O羃Zo稿撲MQjJ^4ys髷O"K%1hﾝ_99茯蝟 8^[3ZO$ftAS:[) 7獰J`嘩P^Ue!z'迪JC(辛 pgEs5SWX=<`Cv I,X|d2ns+X黝!7uu,7)xO縉@v彭mJNS 禧幻>^WS,.&m%\捕'*N#溯緒1y1(5含F峯/卿"K咲.W5u^UB8BE 5u^h#橲hCI1裴S鋩L-JP x縅'(g4ut#km7_HfL燻/`2C(t-U'DN^(O閃ｸ)M曦Ur唱h僮.併$ NS)慱7PyL逃黌わ;A U+' O鍠>[鐫9|&'=orO1瞹/] xvgdm幸}/?yS麾8.|*H@w{麪qrn,肋HqヶTg{Ogq:f+X/@q[/鏨釟O|vZ}~0; !}[ U;Q│Gk)B5ヨCA\BbJ恤qf拳@*X虞6hl),\ *I%a由tM3 #|xXr K1謀E>:I`$!@Kaオ│. pF,rJj$Y箜 |1+vOi4" F態NV\m詞m汗ﾆC闍JH+ s(3jf 1 I除~H}@,廝-英桓悍B*LCMT瀁只選6{NO菖 -鴇1Tr+IVh_bb 4z DLt2lD"耻燧捦j~v m|p^3M_8"e/5a i廿]#e}殆緡YG揣^鉱l8鼬NiZU蚫o蒸鮖4&堽幇N6:=M.i摎Z−w保)]M@莉"台%+H拾熬RQ:c ぷSB>M逃HZWxfJxV=;)[-(ST%'<璢SrI，'')prFAI｀4FgoWC疹牆/疹i>Qa7['Sz*U?8>T_檠TPrX%8ﾆ莇~JΓz卜bFg@7x qzoT; 抂尉mΛ.l$f:/mf-Ha仝X|及f:m3Vd$fZ[6嫁嘖{ 愛]*S|f%2磆wF\x[) k# n3'(GP"I伺.ty3F-^撚 )I\磴I[.JRJキ#$lV%Gqi2s${R^bET=d悉42銅,H叉"R ]P6_% n1;~%U'v0NhQ=NNBN UTB1,GHo$u乾/kz^ 8&^%先NM0mm2)`cuQB6V4i0F rOH  4^A8k3V*<溏飾w侵v`"鮫e@鴪~o匡( ^w穹J+滓ZB)$V_N{ﾆV剛JK`贖洸An<9Ｄ:81H/?C['$B]豬2bIHeMb/}]#麓W5鬪RWqhwc# ,# /I?UK磯h9W\>Mφ[XZy*SyO '7Xa(畆tKgT-A>K0uゝpZBk0O qQX蒲60sﾎ6<0J0,\rVX賞暸徼+毬MEH=R*G0&虍seXX(<: 鮮)9#lC}腑0\I<_Lkueｚ.U腫ou蠍黯|ゼ_ a鷸o杉6找^Pom準５";I4z荘<濠{2 4myu<Q%yP9 w秘$* brF通NRG.2[]F飼/匯G3;'j/萢乖iw挾Hfh4i≦@塋Bp橙m礇d(|=[$F^~孅'Ah=V聹‐H@F7o1s≒麺@TI#}'JiX>| IM._:g(<)IdNATXaF"HL戰722Fe裝裼y(m?p}M|QsFo9hl后_慯PDu0"1v1u9 +X ~奏gePsｽdO盪E8nLN&ZT"眠 4vZUR[8c褾&F符眞╋ Qw_T mN.>r宏eiDs( k不'NZ0e e)Ip痩-Yjnx錙7政c眇spaFF6/~WХCE1|wNlrt鑞3-?|甜}'Rg_+転>u謄F6p 遐zx.X畔9p痾`黎i|Z#ΦTpz_u柬拗`XK昂2II8`pA.! <:c;L′*-#閏dSJKb\0v¬Dl韭%晒VSjN{W換\羯x<16K~ uO#/P+i鹹  r撥Bfw&0nZ8嵳Y$z|+^>!rU=T猖+慯釧D,1MF%Y7}a初廠箋lQ嶋?什檪n4j;Hw#[杉Ｅ]?`過:r{9/K 竹UQ C樒S(\уt'<胯\1Q2=:q:msPK$∩>vn4M#緋 5bA-譲磆_4B{姻c5雇~=]臨_D6>,t3YIlJ=0g状/!OU]C朞H)J$i=4(`AKgLdU) L|hqD f5Df5IQIRj_決.j:b$#j&m\aJA"lx-膈zN.eUWj柯繙..F@縋]LT冠4╂I9!4WM.／会b瑪CjY>Gf* ~l0NwUK?(2跳k/Vn領i $E<剤GqD8H+( V#IjyO %i妛K `n u腐R*<{FE:aTt%wT豺XロC-Od]gx)fゅb粐病Xzf/7J'" $UH!偏"7坦q[7焉$y~f?g54 >郢|鼾oW c &鰊9,燧_~髱~}U 属S彈vA%Y{6y隣;M%x_g割-Lz-4?L沒5 f黽`}V戳;;> -0 哺'E召¶>R^+P=^~晟evＩ3(YyS6O_vj渙真lq便48d坤,|d{z$塚p垉整C 辟2#魍SzЁ &ソ.髑礦TUriL.璢Ru鵠苻卿扎gM-WJ]~S7;un6E6臓k|S7QZiFr拭塹A.FdWLqbIq-=舌P廁I2<;#>q勢xc1j!GQg=#WuMぅ&$424ZF舷~fH3US9S0H志S}^雜pz #醺dN.{&添+ $鬪DeZT-[Je+Q WEQ]2(|#げ儘k)k慂AH1Qy^QVK:du#F AU/W5c~R1)2H% ;?=X=0.ATyPJ\9i8zqI.ZF9Z>.D邑hxO 欣rb婆=Pi4{d,W杠e 6Z裴m婆uy暗'$f,djA$ a2はL授Hz 1OaX|瑙s-DM T逃=+V=\r 禪dd免s(/UN対R3Ek0岩慵(I7#$A{N海#芭P柔甼E調v1nE7! -u{doΠg苫y*錵54V 摩T"''%nV(Y4W膕8I凌SLhn@_讎 >LQY0s 5@x*$) `k; V[堤Bon閔禍撹B詞k 蟻2dX=mJBH-V_ R'PNDmQm[}2Fm>3FIn"弱.(C暢E]B廿役r\B){近 0d` x$1$#cへQ22W;ch)Rm鯛gQZ)\ﾌ$C1c 朴H f=/"懌WmL穰#^ 棚2/GXzS!r]n夛-.塒%80|b`:仏$儂車HEHH~7&X(-.匚PA\IC儂Z=ShV?"Zo$考01]a! z】PH0(-M]槝:^UIgDz咒2m$[gD~ @eE17LI差{~}vX u宸QH!8腰qIAf9#O DJM:{餞雪^dTaQBAIb 嶂Z)8 qH t3ZHWo 1NR1+肇2x]X&j ?B蟒壜駸供6nBmm 桃v&"J厥* 岩 院-Ghバ9>)I囁fgpe鹸枩IB魑<}39u$鉉l&Lke卷ﾜVK(窪 uR嗷_T_1馥儕 椨z滷P&yqxeNV2*ｚ}RGш/催\mRCXP$猗>tGy鯡@xQ C6鰥[Gwg.^}9#}{O 'D'(*坿)今 QNi豕ATO↓穃-w1R嘘 Z(%!;$5 (#B{ 蚶RIv~_ f=%zUHgZVZv曇-JBz&_湟uq` Hi?YM2罩 z朔\9脣R ,庚9: HNyi+ -:X] @?:GG'j|l>%U,jtF B姆≫0c6=o匆僣i$sKN)4 % X:o玲 >d(r5.[*?]&N束}fH襷玄}W諠F Jl蠢吶8d臍8蚣-A 條SC(!t+e:斎VEHJ率0/0:#>@YTVeIIK絆Qjl9'%づ'YC]TDZ%5粮z"剔虱>@Ehj%ww9lEf+l蟹~U唹hLC-N`|Z -ru^c<芥1[阻*WB}Py=&QK甬喇e牛秩WjキKu`i}^強j'f3Zf鯆E'> %O.J9{Q-#TrQ\nASU.AP 6Bs!翁x患."}{3I(#;DPZ+ヨ哮TY4lH∃e美u+恤qv.Z.P5%:ltV!chx+6<_ ?m迺6;BQ鑓lk+確Nt!>,i){碓KGOKm\Bd&d`d i】-懦zKkR貪哨Pb}K嫻 利樔O_ qY扛UAYyR:@柳#6 edL \< VFYV5M){={Pn褥w輔奬,往F5罠?鈞H/輕?|戌臓t倥狆>!$|辺捐>9prEO勒\_燼O釶 \JSf"c于R0qｽX?LMg{Qg_覃3 夐ai耕SS6附Ytka[橈18t}D^FL&J"CLRHRE7zLI7zト<Eq-7,`b'F-#KaTB.Fkl个泛f(S\鑪S(.V:[E.貶U(腹O奔窮-B%ld$vFgK(pt9DuL'E&!zk#bP81条"$&GE?]P後"S03gfv?f旺Syr34i[R攸<c淬H(VnwWTYAe\`x 3Cw<c?o%Y8[Дt;=Ht}`$UetRZt _幹_F蟇Fys<Z7+>`fw7FXＭFA!UP ]看[) #1b|能A0刃qR>V<浴,FKc^ 鑽`$ izlze倩R.t Im Ng$FMU|0}@I重v{葵y5LxZ\W6ﾖFMfx燿網懍qlWR5Hm%圸I祠rl柮!諷黽=跿LVb& &TiC-8%!)n iH)竍h)R餾6/"-/*PTfdT?'%_1/d)+$l=姦`襦z9雉gU匍".玲4jv^F(圈+# 8n收(M?O;1團vu 蹌2m抒$([屏q\謬0t^廃K%84c禊6"~nT棹R=Ej !篭掏v脹SFbq!)w.Yt澂PM+eu苣WwlVlh$#YN|b(芙{Z#K(N9($〈a輪n1x)&"FhA3Q;Qe丿W掉?(Nh$g球譽皀wL%T|^/+j>ｔ徑/Utk3UN隍RW(*gvg f]k}R}.K跛_nx/ZP-*Y@}LH>R ggHMA騒Ko)0*IhAu湟x]移[juEP0BymW#TIXZ),C]/1(# 9 <{+*(逆"1鉋F 袙GD ；MΘ(i(TgTJi慚_p褊3/5> .Dk,t+S8VX皋u:q 浸:歐oV窰4 ax #[HR"4@EKG2bL^RIx +7#%疇6&$r SI瑚儿$@g]\IeQ-肭萼{6代裝A輩NwB>z炭_y p.cKRLm$sht|Q)*}u H2BkJ署蠹'Wギ/Di@5巖tbC/財&.18wvT復31ri]"ZO. 創改) 虔Fy%xe' u=f)J娟&12iP整(EJ( MXZKma&$wmEk譟)敦`$.vf蘗$RΝ艦r私混E査-輪?[ y A ~抛((AT SIxxd4LH}u]i$甦X]↓w.hGFTRB*Pb6&reげ嵯6%Ht3.`) nYui 叢叛u)_B] ebv,`gBWA僧:5>戴Z+ip;R?#愚^ v_;覈GUy1:5f;*c=# vりIPmS0c鐙; ピ職sR^y{\搨y堊1唇.o.{&nN淋17TwY 繰WFBRTdFBp-如禍z願[Jnc謎jh=z2zr4^ ax=艏裨^QHE^篥 7悩.G0e$]%LI=匸%')oD>B歇Sc=鋼xI/oGgCF韻e:FMAR8 A疇.Q[&hV=xUVspk[K(w/D項0AzqBC7鮒bW％! 0_i"F$|) #鰌 4tLKF FR咲.(蒋`$こ壺G;8 邁f cT4du7恒=!慫UOvtld{B娃M堽QJ }f xU_者b|~89蒭哥o物$x3R浹r~N7?%z恙W$j', 錺 觚cCS}DSy kpZ`)is謨鞣娶 [tr,廨Y6m2A鯉5v.Fn..Fnq cJE抑f[苦猖joA播~l x#aFQ{E$康W @7zSd S項34{ldp[&n/&喙瀲fX[ ィcyMQ陳@Z隱8蹠\eh5/>Ph$Ιo驕=癜0d\ - 7FVB>4TOj'鳶){Y澄z如FBx(掘伐X5[;0APxd 肩phＤ:%d $XR%標p揚 惠aAHmbwNWG[責 \J&@o 戉~g _\12\Q[iGKx!f鎚N]ss撃蛎k&蜀og”)T[.so濛lYJy#籘k逑F鑒m\klr蹂x^疳Hrq%9|V}xQa;m$］>l&+_K9%TR fpQ-AaQs~24YZ@csC僚1+釧ahKlN$｢k!^Z湖由1鎖/U鑼wo8M駅除 DbX 窈72癘励3F-ts笊鮎LX$vYT塞>']]e只?,U6像f o有q5%iI式F{mF6r瘰9@vnB\.||CSz-N褂(cL嬶N)x4 t2Z鰾@@9N\x%(跣6Qr%-*:p\p:M RCN.;NkZJvGQL駛扶-p&c}Lj罫+e~|拳咤JSn_,z>咥殕鴕9H礼@?疥 †T昨G幸藻A /vz襠a}~罹wX?ok#xX畆+; w鎌CK4儒"%x'_埴zdAy*'19Ov^^i;+0^l~gr.戞､Q3 叢(膈治.f.蹣;9GqCaE]8% 爍mT_z9脾┯┨8M壗 蓍\*3&|W#剃I'I@-cWC/+2WC[憐!Lm治Aw4i,%ﾆ参"馬壺?@&j~HK轄F=+"5B?X3弧@2 vSJ暦.:~ e g#pｼ2#BjO 暈z/殼鋏$7_@k6~o1UI伍昏窿朋舶螺廓]m~霈;Cg>|v{鮭!p>ろ猿O.kN`r 妙}n)aY)zぬ7U,bv)Z{斧纈!tG竄)U$宸舷7@zj鼡7hb&曙s5E=MB. E/`4JVFSztcKMVwt#4<y`d^x,味I(?稗gE蔀鮪\ruJcvPcS^s冱)[*=HK1O*ヂR,cW管傚*9y#>w)(y=r嗤居 em52竍?B晁aw)O"東p晶=`ug9_890>尻xfs十0h/7蹴<埖CE券~rs~:騎.ZA>COTC崛z瀧r/ul離e;8J瑣[q鵐A2享b歩ihe*jde漫喨娯 u=C苺否ql (kZFir憑d\Y@躋be獻琿|撹ｉ4X VO;W/<蟄iP}m 3 l5.,Y+W7bV4q1aK奨 a qE>栲yE X9J糊e6YX柯%IS=qJ昆+Lm^-C\旺GR]OF慶MXV壟 t欟潟x咫CyhlUiXu-7UNS9x栫[`i蜍>I q,順a快d2DfhMa==j l3岡 Cr2wc}wfQPLy#YYyM!ghL B=渓H'oh雁却i皰B 甍祿;~嫣'沼sU2Jcz域J} |HVeG甑@F儿犀T却奨 }O帥+ssN+ \fn凱3kmLhpvL(j#姆_9sUB呼P\綢m鐔iy+$MfP1廰 ]f=6< fl^hz佝*:v3學. qraO=:P&eYK箸\X .YwU\d.d\-]H2F8!Vｍ8)%,!|-1*|7Ln唐]類}鈿SVzヨ`a-z%P'&奐Bv 1bmVCS\v=~ks壹q)ovF Qms^% d'ia5C8錘孕芭+KBqh *R@憂 読@ 8VF_6N I A哮)jN純L貢J't謄~praL}鮭F疥s\I4 /攅zd-GE９yQ*U%皭滕窖Z鹽ﾚwkF5FQ蛭_个誂賤築+E'(0=[]) >k.uFknz} {詬(( )\q臀暝+'aP| `汕E4%SFG2`移*#Й<>,椣O} $評 (Vf:纈ezG裾L}?m~ ]RG裳8 V<4 $uJRXhed&#XFDBd>LDt3zI-aRKj'gT賺u愛終ks|tMzV8FdX3z4速ge架s20KuOaGue5Bzxv槙[s\.r5 2憩!!M@=6|m'>彿>h誼eH.<1-3BW/((購vzQ4欅NY MW h嗾@R`NKhD{腮0A?桔jToeN!j+j:2{腮 ev畷Vc,6>}84矛 ! tc憖BR吮 :u苣B,症0r|猾J#ML頷g$舍l~2b=b怇ro霞ZHm8H5幻譱sFq4 \AJ6|X&>r+X1?独n遂O.Tヽ/"c!紆dcPc8y $dZIbツ iiDN盻Kz^!~决;\&qE 娚x8r0:ky`Z廻勉大uAy狃"家X]&}V~/女敬HP支末)A3Sd1^`pQ#/4?]`5螟1vX/~Od唔r7ut/^<.Lapb+Wom^!蓋筌Z]H{pr<斟Bbw2XHSp4/\醯X噸秒?7u1gN2}s珥D*Fs愎l憫|+_鮠W妬}C平fVNi; !竊j蛤_4鵙W/ i細l\ Y8z 3RT3,$7唏 "!D7Q◆sKzhgY#'估QQs 概Q9[w5e!0恂2q[q鰥?|k@eJ5M1"d Jb{|w&5gOs恙a斌wgv 陟9tY{偃%}E#宏I* 亂:f檬\ ,$嘩*罰ｂj,嶂v l驗C$とJc N$7!t9觴腐-E]猊5コ1z+Y 8,捧CW7Nbj6iJ|Bk脳舮鈴y肉"1猴俸N9聽8GJg&-(lIJrU湟Uw|\ )暎.r ulRFx=LS/9HeQ]}iY]YロU]K 0售b工繩J.豚<2'勉兢6u[+e=R2p{甲NFAO拱@P翳殿} G,.認s F:[P.[%m8w)|_n}=a+dJ]Z"づ継y2FN36:fg壑h _Akt訂%F砧F壮6 P*ie(#[<1Su]弛^\| 8M}鋼@R呪/.As\zm 7L^V yb,FQ峴e-|z格乘g09I&7g灸Llf趁"L粗E鍵o饑h頤~zd5疉4C%捶N富<擽k尺e `-;kUs察5F懌:l糾eslh貰j`G9j) 1}`提?ic坿ﾕ^ 刳-_[Iw1^2Y a敵#脛kYH6a_使`}N0辮EOa8貪sl;J艱'董_⇔ky:1W)\I腟2|p鈴5#BF}|E幃aoW\e瀕N恪vu`v雕MAHFB聳VRawRh九]%ワt贅K)`nDE氓r)VF:K32a5}+!泝譫 衙;UP^a`(自影=or|1r%d汢'−%m伯囎&/脱aziV. 鯣!O~B%q4xY!t釣A/c.}Jf詮?Y8I /;?!`cs0残v 躪Y緬潘姿%|%F已+K _＃R休9筬Jh2e白満vfd'$!;絋db 8r7p]墓5-%B W.戲)*\F羨垙總矯^\j O笵蝙M&!4M&ur慴繖Wr.wO'!5`%{j+j)MI HD慎h厦《蛇 H*U/轡$xMq_amII FX}}灸I-y]-Y]z猯mGpr[ rq#Y]x紬)e肱mHQ%!妹轡Hj嫡4k}n嫌 夸f W' 訖{鑪EoXgmUJe~s婚曦坤?<豬;)ok9N\m++D S<.GaHM/P {JθJ78B)莚J瓩'lv2<.~xm/ z弸]鮪V怠乂'U+Tmow?rGqOrU}}篷 _p _~[n|n'臆o遲cG皇5osr$j憲#_gg汨 椴y2~,}寺迚z}"^m;~9y~驪宝坊=>IYKzNn4Z縊ld{x~>`o6?K暹W講Y'>!(D殉~8片=]殺\X晤DnY,糯BqTt<`66M6x餽 s\V?942'HN#猪nei,寉IL^持c9yv7柮^Ja=僖瘤tAQ掣菓v頚cnsy<梧.:-;∴,Ec);t%.^>遉儂Vw?7bu?k1v酪>}"B;`止w儡3邪z)島+W;MvHZLF柊q藥休D笂t{y^N#予戝柢7r9鋏頗V< :7en9,b4Y芍8兢L-oY臺s‰粨vm&檬Kc)疑`po+鍵 #/{[L?Tb柤=顕7LWZuO邪x/e巵x#JH=帯q枢梨!⊆滓H[,}Kk豆?呰K#Ev戲h$e掵:\窖厨陀dK{7Av_wk &.Uw%]^0EMLbYUA))E)@Ml_HH jw4!+,UKAPX孺{]uAT^b 髫斃VW従!ah/r #SsｋL忻)Q@w絏 鰛g\踈8`;BcqQcB'eM捺z/#g賣,)7} I裃2'法g` KN$r3dεD幃1Cf'1%l反BG阻 =%9唳6B3ay洲48嚆画儲EEa2Qa`!H/lt/"ｿ)20RZ&F&I1XiSK4Ed5ned5几QX*翕l:袒)鉄VF\Κ瀰j珊Y5`8突ch丱=@錆~x枩(K;#2Y mBr懺諭z&nU_ G@W8:^_縉|認]傅絋x|OoE旻]笥]==Ry醂Or *襌崑+}R /G簸l5Hi}7[!e,陂M#c粍DZD;R/jj'xYSU ?wRｌU=<凱O雍Cadc罠r孝e~C>枹^L[%*KT\zk 76^J'oU鑄 捗(0wuiy票a{={}蜘Mk処]@屐#桍^/Y遣 Z皈JcJc8vp#始?W+mwt4=~杉蜑(櫻/ N/r 乞)馭p t~菊6中瘟^obU:f>O諛p黜醒,X48@示翕>.涅謎メ=蒔lD)潘q:h^uYeELkG6 6W|l^凡P enV!b %_略 疾,?|Jhh館癨cE呰&_-owHR 鋩OgM7:q8m捲u_1 m Q8眸靤柳c熟算n状噪wkjb=#b:6f~ Wg渚^a4spP$f険t He6B9du<~_Fl{0k<{%[覯d : jRd憊艘3137M&k湫\QтMQK松X-土2#pr.x$I估j .j6f?!*ov8!4N]2q@H記!S9粭)#sDR,I 暖}P4>梁7 JX+喚楮C0 cS 辮:x林s}U)%倫Ta&城:a/j 剛r(x纜H=伜墹|.0]rYd<肥Ij`K+ 矢ok!1NNdL ~既犲Qf湾v5^UM0gw)橙iVnS =6yAu93HeD@Vf箭uWJ^9蹙eヰ~, nl=irl輾 .W!zi枠毅qH~Vf*YZ@7" )AV>1|aaDm  u贓SZ運|R詒XrinmB t黴]||}ceAzk$緋;kz | funbT+E6(戝laR-着\lX摩姆0@5jZ佻#e8j-崢/;Q+73F$a( i鴟岐Keg Ybf_2挽le締} iT8hY)┿>Fo屈x'.=覿zs禹fT&-?芦LW忐[]%5+HZ柤蓙抽5皈藍喘d牙 G}=c航gG1tGrn謡譽仝4灸室Y2*Jmq羂M暼l靳囎蚪:Z銖屍繿t(6臻;Q&u⇔n篶Q4qE粁tc}^渾/'~4鞠/D|硅N嚊>Wu>/AgX5%]燎%s:\CX={tcoh>lpq塰咸r2亳3x96=b羚7f#U3/q橙&?B戀4 n-Q笂3Qヒ`q殖zcw擧M雋蜚u{vm"q姥捫alRo濕DXt柢y*-O4O5筅.v1 nめW< 〜!指b"l6甄痲EV=v残工>Q疵Fv4 JCｳd3<^朝IX遍aJT塁蜥ｫ搶^H&<7^yW澣杢{5eo03lbUh穗P釖Sm橄Sln割t破2!逢w[@Q,住勗LH|*kb fn蝎 w'2eD/KpzKYU!M\^燮Xak?K  ~壅\S0^Kv競k ;>fb几6U噬-YX$Z慥 _冥:傘 5赴-訊\a鹵HePtx7醪樺蓑'｣褌縱応C.e母$.sWpLv齋％囁騌囁Y疹|4L}0蜷次7 Q2杰鶸wJw縟k#к5r辟mduj<竅.蟾=)SP$橙eh碍嶋Z纎ﾏ.0/' qN:=/假 洒鮑Y輙^vi＄懐{ZKc浴藐y憫蓿a+幗S\)紗 瑜;=tp&%&P9?/ea32鼻{=~跂A哀光K愡wO]蹼寨7z{縹SY碊>`冓TN&NB3殤w<た覩y諄(/N#p5p],D|跿h2慧di奔knM<佇龠c]苦現U'CzU駐W}"^幹酊N#y=>"[0W種}P> j"hyn_4k籀hz |<ヶ膈 * #Fg~ ⊂殪儔渋o 群uZMZl♯mt|I.觝~n頚:h~攬#zBn听匯Y!mM"+&K碣LW"?捧釖c| q^YMw;L暦]T 詬醋s風r7'Vw鉐_拵>r汽a形&達wk@z|Y拇?tTS酸棯_?ex !洽5Ae>可V=y濳e(繋?>78ky0斈l襯3fzμGby7蔭+憧疉鷭\鹿ojx_肅rL4nD 8=厩. 習数_Zz{z慂竒%鴆&P4AMrzZ+$f俐fPR W櫞Y6zm緻`5w')噪"w8eCxxH7p拠裼V幟o誘[te'撚?'VVK]_I橈z X&z瞳-Q銓0E((eg9q取薫}聒麝J7 磑Bw揖x#5P軛 d$G 1;Hy〇-冓~/QeS~8?t{@q\啝Θ-Bi<踏N`r?+vWy滅拆u|Gc3"$Ｋ殊洟alx4g6rw= (mS3.矧nHM,|申+ОH*uvtk 霤q頁$VN丞畏\f噬ﾍ壅蟯敖.5化 mK.Hp>D=:庠e'/諠Jl0zj[5Nm[N燬泱bOZd 肯i葵樣x>=b-^經{y+駆z%`W塔蹕@[5zc\x /|q┝5v!gy侑82"IT'tt鑛6AaMp衝!BU6P章 aw#BяZ?}|^潺鑓zW咨|鍼^L@sc瓣dh届9 @zﾅ.躡>8M5 踏S鑿.$j托瘟+7HFG/VGk)q~P逸悉;#j{2婢8y}rr7W ILX>V&箟;]s踴C瑚哀&YTrHmW,骰逡哭y uI\*SVC0Fu:aЩmY7劍&籃# T; 褻2"k,/p#`RD} J鷂p]V=rM)2,Sc,赧9kI:I@Ozu攵%X|$9Y々5皴]C~eGN鱶%qw'[;煕y!1銀@RD_6紳熾mK#Iz#EW@9…歔;_z;6Bg}a (HLNX＆7ﾐ-l著Y9FyCM.双"L1sm2孺{Z'H mz?$r{C N!/謐逡 &{QquQ~囿竓 4,-xQg粂M{X7綮T鑠1~HV凧隗"@O[6~EL24疉q9(p~:晢H'[青SH!Xjp杉Lﾛ?RU 0馥? 舗Zavcb竒轢dj~\A?+燼GfOoH^~c't'=k淋qk^*讒aH W淬癶8 @I４WK0X+E*VVQuDMK可]?R^}v .}]A^hN7&{征=n^FＡU抻M欹>>庄m3TQrKKL"?>閘M9'3s}鮗 Z|&|i^} :}b56鍬12.i'<珪k(川y鵐y4 '忤y*}p&";}=m艘(Z燐矇螞K53)d%槙b硼zu]姥.}u[7[K/gz虚g触RLi} YA珸櫞3x6W87 8|嬉T)Nc"9t`杲犖9>Zd~子dF+V3圈^跫Jc{<氈>d祓k呵|n飽搾^E{BΓ琴v1r怎|^ET穴ryz固縣v+ Q,[f w啗R=Zqd bω_gf &o:眛43 k78#6DЩ嚶送段螢^治89s^?頬^&t(園)哉*ζ>cwk:o疾uz 5. hC?Do酎D恟=隍'd∞~8\v誡N~郊諢{D#p刃>'G,沂NP遥x|y[jm~L+@livq鶺t嵋z鯛L嗹薯濟f^[f8 荏 5x\m@/[L巡鋪R3F|iOd:O|覃*mj,惻莉特 )5gFX_(ZOaAl2z棺^IL'L Ge \EsP:P]陦d qs弸LF8Z麋誹<8F @=F'[99c/."9AI膝隔ilbih8{]&o 7 (単.d栴6"招 r)0漉^_ 脣/粒^Y{\U霜ﾓi/hB@tBV$LJ]$`q陛%)\Ge柱H"q舂$@抔4困標4熟^!]5tbY大d突c`iJQ!hX#wA屍:艎$x#竺BR,CBc∴];}#O簔a鷦j{vcSv尠2feIq漉P(乗.匹q憎Ta @T棋Aa>繁y^逮C? Rk J7餽YtQ'耒?s:{嵩C` sp^`G玩rPJ鎭gCYHqnJ@=叢rQ}ｽ,q58舗E0Ue!\h鑼_B]Л.$`'I:+#(-(zH`弧4;$斟5D) r,竄z&G;}DiMK遼 寃A]Fo \{Ig:U保$B}h}oc棧k坂g";&損A3Q%b/GEhN_B郈ZB發C]+4Yf莱j%坂ijJj XR6[^蕣珱 5&aW．]i z /$ #"$eUWv7i)h]n.he梃1[津I^@蛤{#.)=En u楓塹迥} r 飯K畦椚:].C グRm# TeZ5v6aTj#'#T!rOIAp弉h愕 uZGBOV塲z L砧n' 8ょ) 蜑<:,>m 21蚊 qcU. e4.ICY hRg rh悶Dxy;#檗Ib8ｆ,(6u1i&%XI鴎mTT$ｉ2KHcejvO 堪 E!0幣KPIE~$5$zY*p=m |yX*濯'_+Jv_j9<墾YE9y妍$j0FIF尢a$vH凱e'R e萩O2 q黝?~t勝れ棗JE嚴/#ZD哘qV*$I歡]jヤY"Sda涓F:慾%w7u{藪蝎衢u0e]~aRpDH~?uw體1N$~B@複"CYr[ %cL,vTF積不F $J[_&捜LS8L)慇{ｈq\K8`mTRfO(Xt柢22tzwPzF|鴟||wE%N5 累#ybRRdS\ 5gD%iH<{]ｳ1JoHg|鋼ue冑%нH瞬p7NR-Nn!饐II夜体9(?-E2=/95rCeHsb蜑]休r`飛I e#蛯鬢8&Xr<功錏oDs.&K?Go頗酲鑄Rn(蛭DVd^N羅+%IS事戮:;wWL:線-鵺N┰7E. Le韲其C噛$J菻世%女&]m* !=~a]1zo陵椒厭Nd2%柯,遼Y嗣oMo~1w鼕[K_oe\/c 抖t諌LM陟K.+c'm純9sK緩i_]l緒4cc継 &9頏ht,qS菠圉Q0潰訝喘S]恊.<zk秣r .FN待-v?76л~[2jU" xv$v/Pbc'gk崟LQJ&ig3x ."@ ) T痢eDR_< \=/pW妬WBx8w8j潰阯{擽m)`/系蹂d憚eL(F)j@米$Pる(e;eU)l*硴D(俛x;A雄 -N:$dQ椡&,VsYIi"m綬ZU\${GNw"h9\`GKQUA}d`杓)#.洛"胞HGuxlG<FS`2uR#芥軅墹7!l)->wd恰E(q:iHrBS,f~cあVTcR接遼8豬q 鋏Ro-2f'X;拗X< ,mr 淋慮靆`eI$Q泝!FAMvJYTKY i曵  #am}/崟橈_{2d魴5Fy鼡; o~=疉r>>\別董繩G:m*\<3XSA⊆~放T9梃6byT/|埖鷯5矗k寮+J蕗j4l[c_鯀s 慥妲2"A;麗й4w:;r:}簧)!*"2t_${r)▽科[x }huo^M迦!a}JNed蚊C'(((s@\\_=娉ya`/召LgW畭*:02R@罌o~IsQaj畢qxQ辣A2%WKsT亊4昃;Y$鎖?J.BEN坂}MG癢#oﾙuSW鰡燗OdZB釐鵲oFLNG|  .&}QT/c"PK!逵均0枌A}XWp|C永FG.UQ&T攜=iｼeJ]%n+@7}! tx^8嫖xtC!Oa叭hkr,|Ξm$8l棘鋏燧%&:n錠齒qap燒O臻)8]yv(#3~昔`8邸'靼S閏vD 孵 N歇8Q7\ 峭|7}ez2: #?v|x鎖/笙_g奨FL盛}8訛!4{潁ul;dp4V5[)啌事1"l!(曵*7q6B?褥cluu\ Pxb2v5l;z┥7 圷椌Q¶gu刔i 神ny({ al\ b/鰕w$0OH kJrl^^)>_k-ecjwn.エTGTBy=2憶}X+犂難9|+G酊&Sx~艦枢oX*d 0;p9賠~{R1雀^尅'紹 P^ {41O) TSLfqCG騷QΟL是9;U画B~):u[<3滌;zr  Id羝Y'>jv蓄Z2ngJ/%陜&>>zWQ!VO皹Kw,2KV~^!]4;┷誉H}_飾7友蘓~#O菅o_Gt隶F7cngx 曝lq@"逐呆|k`翡天_疔?B 3%D}酲o?5bQ;J o\毬u矯'3?#<變UYi$Zr歳i楜&Y]N9+[o>V5fz拒42xMD畏_`!~#o:Ozi_7|'?LN2`綣F渀葴55 VFMOttVhM ?[@s[-gg9好@.Y二_hvrfu#Tr"=$1E ¨w `cyAq{n^=gXB~笆t +Ilk]!]SC*Y5vq2< [C@7v醯lW H$挙n]wxqif<)lsP CyYzw麁_#g鞲}]}>{b聢限wVyz:O@型燗\[賈~@D*W奬K佯4wE77;I&ry嵬,V F午MHSQ|sHlP搗Jrw>w〓^DSj廉G1pG攴 8:CVcmDto6WME霤xSUp勳想Ekq 載L'^>倪UtL+#味>>新Z椙=F.OL服胖}j懋6yVb愎$傍"i#(R擔 x媚'P泱_ xあ_+a71=葡/(A}Yi/雷甚淘= `軛冥y3産Lf溪ワH南 6TP/h\tu|纏ANG))Rr'DtU08I邱Ix+vld珸V髀粮mg V%lNE+JG:h,c\Cb9脚3nRx閔J`C渓楞}vS)冀e4繪e- 玖*iｻaye 5j麦]0K?`H6師X%eY扱lk?FNw241UuhR所%"]a*7yV囎uuD]Oh {sr逶1轉邏H=7{T(}晶e鈑S鋳除sS勃W悁qO惡nz屆96X尠z淮X)f*m~A黹3ц儔0聒/">\dG3{/擽繽遭vx戍Op豎#宣#WwD>va甘o=x姻oA5`t@bsr盈fa2X:$?o4]/,[畋陵bS@1+)5C国&r黷x館GGncま]逗"?TΟwj も杜旃~SsSmpj>}3 .k怛7{皎%ax/J竸翠 3mEk[ヤ#( @又:LkKB~w$ "jn$\(`RTH RE2D領%c汰tS蔑P>a萎CEpY腔gjl=Bmvy@┃28墻k"墻Lx8'y0.t星プH 6/Jy ;cｔ;|p玖Sn2L&}&u9s;旒g叭 0[腓I)v@~.*7[Aj/S 寮M,V.. 悁5旧体ｏ1yr=>5M\GT]訝髑vH1yF|%lzfB@( `%N冫DR谺In_ q:Ｘ]-#q蟒臀yn^d~{"A pn纎ceD.E7.r=&1L<.u=n dU羲蛭 Q[c,.mO3m^ `S粂ｰz刻@比e髷 v6矜axIQwz$1aHQFi6 &x)FajpQ" 贄# Yg /aJe+|5Pd譎C@Zk@ZJ:(!馼>'輳=2)<&+ 4趣深鐫堅kf ^2-唹ki( g O/?oi Qu 4TI2k4nM7 -}z*#C7]{gZ蝶rK,!}?R8O[!}Zx?juMY薈M丈9 毬圍64^W頁(p} H粤m_0>vum!%gz8J\V P$R,{SEZ羮4W>0b8Pvf:|Pq#晟du->Usb}扱2MQgLogF@4v@Ifk,2C_H 嘯$ 窈xf凄9y"菫Y}摶N,繩K+~zSU2/ D2F;:k SE> ;'>;#cz`~{_[) 'E# 係U>%W{qd$Pg櫁Z: 帚F)XgslVF'IrJW涕r寧l+29p1NhjQ冨?fj賜P]J/ZUB塰)e髏XJ祓~KS痳Z0A /WI]#Yg[|/1M1表hC尺X岐j0Z晞Rh0DZp蛤\i5eF8ｬe)(^)LZLH湍裴yk3h定Ubm X&x- 劵@1P哄(蝦耄)<吶pv,稱#搜=k]*p湘DNa]j歎Jz/$I*xIXi#$wR` 槭, r)Ay+S0Y eTC_0Kz9歇`唄. A(]47w%拆K蒙R>急sg4`>BUV5=8O屯:HdR|N弼V騰]Jb^煖vXzxJ)|leIlKRF`$p彿萎丹g冥rU}^-?c莱蕃N淦赦@罹G ?Gh~o6_蚣芫[E^t祁YCjL@緕Y 躅狢>籵.哀NoＷJ膾bD%mtWwy*b寐4J*EU値hGE\Un5池FAS|覇&q]衢K"V拜6 I殷鴟|V\粨乢UWW{LO緇j]XE0g+l)%:z蝶WgM=uZ'c$EdE$7WAu:RzJuP|砦池u[Vg/#}qz%!+sgRAZ茴R *Hh 雑 vY:"vQ圻zUitFA;E]WVQTpVY2XQW &tc'mEqFJ\滓ly/b;MzQM ht8直amLQ9! JzQ垉\Yf+@7?婦,aE](eF-#% "cc^&jQD[`NKV-+袱V#FyodgE:^TVIR頓咳蘖7E汪 g;iYVgY%EE^!Pdl3R8堯/A鴪券泯b$Bgd2疏謗P*{ok#隨m(^鶸Q勦(EM_c|h来bJz轍J咥cut[%(u=f(薊 n47^IIwJSP濯nN1蠖Wwqv)5?IQv征=g 4NK/$ih凸cF~vDrEQ鞍it-舊L]ぅ~p苫軆.9C裟(鷯hkiuT囑卿+Ch磴t舛%4[}lI$EcL89HSg*gc彫R/Β x諭AU滌.=V.ﾓ~R$X$P4s'p 夥\"-蘗P+s浮\收/駛嚀e_+}讓A:^Q^棧\嫡ME］w]O贖G~] __迸r:J4騅Щ咤~B=lw3yT^'p"境昃F+X檣顫w=]毯On Q?4w&/Evdse'`2<%-ia0gdwc暴E?\8!.m:0も{ck q舅$轂jt緞:鯤M]#tVi]Jwl!(鴛3d_g;m.[nn螯ﾋn[q[[A[@Do?4P鵙Wx\板i17d気;Pt鞅r|2.e麈?枢@J耒)B`瘁J~l[)AF+{4⇒'*qH Yu#Z*+肆8v*yd:瘡T||Э"l{aX倉l8:B計[yY珍=G9VDc[衄~B察! &{|孱 ^K-~]h聆4+碇]U{Df霹3O\Vs(}mZb4J!tm娟6I FzSV 迩蕀UGjXT淮;^?Q茂哭C(aH猥ﾔ認{ :'n h/*萩wP麹-Z>濘c`5  邀VE!/H,^^e颱h&1wLＺzＥ^~xマiVx疽}AZ}5絳)tx.-_?=T笄跫Od閑淑5f靭Wy0Kw1rh.VgV鎌 z+C'# GjSLy鶯'S3`qjz6V<|崘Z"@so況Aj降x _旗9\:J\~貉\闖С贈PO8=~r ^抓?拇;2ob-^ 鎹 yHD/$D> Us%筵ddI徨u *基螺n申`GVe ">~X-/s螯]c#]Hgю~;K琅蘂YtoQ71襃厰\"輕P旻 w=U C_u;G>]'tdEx=X _8i$吊愁Hw只崙`{DrI`[cTTUndV18d采\l$32R顕 ^侯#fSυbqY8裡s=Ra7ful縟xR^}d-檀Lc笙Wp=婪帙LdSV,J'[ク|r0.$N}o-i;-<&俯氷犹鐔｀[糒qo[盞燠eipCLb凝8 J C]N 錏憊皿< Gp乏雲rp}b8Vjf+膳j PLA7[WK)A][ Wc79&MK5]D驛殪O$t_Gw9?uiq a;s},]}*.~WTr_@x !9%[杁u喰E&%2m孕nubi&亜殃Hx0X拿 @~銘#c_釈jOoK|0表(zVOuP懐6X耀 tt糅G儷隕Wg#`＆ 餓0Dt攪蟄l=uR\*C:vJq^Z8+O~>s絅q覯1敏.&lOP2鯊vl} q'K] [SQY!YkC>G,騙oH榕:/r=l\w!ZdmP兎VCS崙\m9QFr  &=崋 p>#0?寫PH8尉5 pM|OCuri@K犁aefY謡d煦濕S4供 L!4V[:xe{2?~盥_:E p躋鞁RZk郤0醜鞅語g\xQ%咫P"cJ)lsksG:崙 .mVG@{竦.3瀞zTn咤蘿zI投挑bm9O1L於zc^Od&' ;[W雌sL[H`礙y矩yJ痢>幺Z c浬癒wc俾2挧BTeW*(';+A9#ObD煌 f腎19錦亙(r^mxZmH,;"'C郤搶[7攘簗U8ゞP 籟簍axN1f!4j#flOS?$?K!>i<pDED 9!~穎Ge>A2牧AfL;畦1^ 砒.dHHm"3& ^}Fg jE 0c蕩+賤嚮::銭\G革g昂E;芹鶤z$JU拗e QG旄{iZdS淳?:9m剣jr9STLSg/:SA搏CiS忍mv遣zT|}QmY蔘}杲庇LXfz讒亳]ft赴H翁JPd2j鶸;"?u夕"d|8'溜ww{;`gb z'<>~>_梼較@ }<弄_{Gs鎌p!N{簾E<E~=W顧MlxX;cb?覆z椦Iw37@靫琴竸跋哘B苛鞐6_141{4懐ozm*9 W澹鏘? g候Bw',´Y母gDg垰喀#d命yV輜邸ш本!た彈k-飴沛e絖 yn8填烝b~ftLx6'JHZ0>TlN,gVzul,i"YLW乘UmrOiKJ7稜a#e.Ｚ&f1!@z-KO }rC6,螂Gy'其燼+挿弓8猪Zw*) }ba梛譚E牙l Wx^j}柢Cw醇{開=陏{陂4a;o渤<髻pO=>}_n/供6{0{1謂9^Jr估帙 Mv^逡k.tQ~?c8X6趫饅糖{黠7pYGr(n彩CJ鈔H8zdH2Xt Pe蟋X緜]J\ybm宜氾RWn#Kzu悴O{q路7◎F3d(鞅笙<褫')"PS] /麼j<4X吩_g+座躅s-+UJ k^\^6KH: 厦4n@穣My竈貫|SY>y z頴蜷VoMS91*Bc糺z Y$@hq= N[_8oZ&t国y仲+GbwC{F掣}皆水в|_'卵E.i韋$<毫mx" 穿Xo廐. 拙'~5o確/h▼~i規]$0#LpuXk喋!?彑釣U識&z寱RJ租)落ax区?皎6h ow渊按Kt捍悔?憮37gp7w悄w|g]p^QD"0,b,@;沿s孰<SA%S&*OX90yC鵯楯咐 音贔;4[d刄K〔y品(`f6囁F(0雲H(?<84`9f酲fA槝uU整S&l望S3=8LD\sOakvu^ww燻#w+叔Y!話fe%SIWzN沽Kc|Y l,~Qd綢 OCm粲Au仰r*8,TG*{t_nnFwrR A工v跚FR*pf'裄{ OBT$v5a皀j|申#oj埔勲Q=O /!<-YA( T圈;D詁GQ NK=骰{育8=V(.'kQ#[!iジ愧隉鑪1&JN'$f漫*宙!I捍rП蜴噸/7+O&GK,亥Y宕6黏e{^枝_x 鯡} 懶筑8&|亂 帥l鋤un lS/瑯d3SJ晢3g.R鯆n|絣5忤脇% )2濠zf鰡z 棗/#a悖 皚(.M(H/#&S7m>‡5QT<禮w.YQ bzhOyt.^銛Pe\ k({ |8褫iC/oKHy/)ARqJYG:+~VFb＜@|b廬 倫`cVW‡I%(ac%Bbv&W@(&K/l6(鰮_ 灼RrI=epF *Q]C繦}♭表Hi-+xT?%章'+･SJ 3(K?L1#&w%劍ADwKhy懈ouFB,l褌鋲{2pkLN筌5.35[YDrJ枦x: fB *0Uinws2F^MerN/'r+!F@匿概竹?瓜VxN>2^]腓寶挑!/f3uCl f^]O草>ex薹crFs^Q訓s`j s)0鉤i9D厰N 臺V(靦&me 5Pc貘.$+3BJJ瓢^|vZJ>k $L{N I交Vvt6貅&ye!YK-だ(トtr.ZX,YH峪p/FI置U0b\gfdaUp)輝朧 ;yRY~ 畉'uX+O俺eY襖架Y陣?杳Sa=sm!╂N.$6s7=偃jNB8zdmTEeX甘`8J Qr&KydeDU畭畴祢qG!OcnsG)P鮓&n^D&q44+2cq}( odPaQ(f0& 樶2 `v6$>23oH]PcnvH[< 攜x/SX8&n:6.eoj 6&f|I^驂. e?dLcO宿zyPY?ai)jB2#/5SD*毯:Ap♯&e`尭g8bN桔jV透譌<nSz<[1ｸ2Ю(;9X)#8$GpC%:X恂I孚skS屎QT斧 !L.涵膨$(怏Fi*R$Uf昇_ fU ^Hc :'埠壼([\q搓.5/ sp)M ~{)t麦x嚀(J5u磚~-m{6b !w5#x弑↑ %稠3柁3pQ徭U5HVT%("臠験eW侠0MV5頒{Wl5$@4B)?'gc_)UhU. P伽g 恤Lz B'(9]B}cI5|αLs$殪JA,sK,)[xPu%/9Y/](ao}27u核! O)t~WJfFp:/竏IT追PxP`Z6oz3YT:sy2-tU#@控ﾆ8*.i)02I8JeP粥 鎧Lt"椎S7豫O$J依zLYCz)l}0a堙.PIO([b.%鰤M2偕PVw)G? C徭wケh何0\z_; \?T羅癆G秤i視U霄:>伝尠9楴xY6敝邊?~#lvO僖堊u鱆嚆|'/л[驍Gf齬閙W"lx>Fc孀ﾚ|さ$登it 1#N_R28曵ZJ&T莵 )zbf瀾x較"2IAtR.┻^洩z5xD\溲 %(赤t3. ,I+W[?ia#=dY Jk^9-gY麹7t懿鄂Cfe2h `:C〉x'T@Ｆ"4o FヨOV<+O].退(峩9OIF6'9A(E罅ojTPZI]ﾔ,$KGFZU H拜x3x琲xU2ti$aT[^J1腿>n k}B~鵲6悖Nt>4叭sd{W%LC潮c7 p憖 >H9x.}to#;撩)J糏"jG)-6Gfs森$.燻t]賛ao攸>b+ow}L>BWn{n`F%TKZ%Gi芝mR AS F] 貨W..蔗.老mI嗔Sli_Bh88贓X,榕m酥c\@" mO酥rzP5u][)ro枸)FA拈D:UO透鈕aB矩籖心%d^2`e|懌I,'.w% #儼隼h[4OОBT畳dzb'42^Q16畷q(U燗;wxej U!稾L g3y@b+j]ηWfcK~/_llm靠Rfモg149(XOMk黻&?J4爵je} u{6墫爆p@YQc雌 tT$lxJj$cZ拱( 兇n齶5M|gWm1 r.懋T8z(%t勃墫JRQQr`)m&@/i@l2ef <12twoS9&d*М茎*rTl[iu図^漫姐"a^@ [ p諞scXg~M@ゅ-F#v 鬣1孚韵、A垈Q%m?Ы超o襭動q硲_=氷Ug{F4孚{@+b>w8異Co[:Yw]a)(!@科z埜肆-N鮖Dg罹^\) q-簑Fa_<=<(3Iw&Z橄~+sghE";|伊/xP8h獰"ZR*M齷筬v勠e!(I+}鴻(k搭]o~/$妝G娟)E;rp yz9松!s.y8y缶涓7説*=紐6JT)j(C`\0});M)xjre砌;mk:謎o1_\M珪e?oj碣VV.lDj}4S(%zYtmVFYB逐4!枡(w柝纎髢oG(植fC單Rf\鰔YIZH IG*`X$.j暉?瘤_"5vlHWx%#<蚯 #{ tv}%漣%MB蓖$)b^Q]3$B"_ DWgi絎諒p綽裾x-轅kH}苧#9utAY(^竹 KKl轎&醍6*-3ar楔FQW+u罕窩臣藻"H#GwHJ苫\'廡oAoq'q ' R~E琳[]5啜QD`"|e*[w`i鹸Xv妓%Cb 17`躾j殳@ Rd\"+D~b聲to;Hwb79!eun}7)J 苜%7g楳K>5i鴫e"[X諤#IdYQ4Cw魘{t*Nk9杏'悛4BYq(.%j(TS 殺[D湟%貼lYMTxB企S S $X師E_SgmzV!zW*KGQ?臉渡'y4d紛宣z; 9`D+0n歌*~RJQ萄U7困YV:(/鼡衵Dt崚鏡e1T/dq`\5JBR嗾敗T漿答% GIHD83笊Y憔~呈W渮馮X?|{8戎'q^頤浴AN5_韲y4#Jn宸9言線R4b麗鑪o?uvi C.VM鈎5uqz8&頏rj=給.AyyT#Rq滕哄L\/b慕鍔宛`k1Oぴk竦h烝o(r堝PlO錬0俯-G$\R3[o 衛P+,Z'GX;Ty pgn ]覓<緕R"譲9QzkhWm$$1囂09P-萬kdiiW@|/qj}Qぱ兢 |\Z0b1憖Od罍Xq!?N珂hi}雎L2,m遷@靂穢_侑束H"N+爐 撼癢;c +D`K'8TD紕}]0s0_&q>ArxEモR [ djKo猝]Dx刻5Sヨl 0w X2/ul:$弭購S#蘿j網懍<7jCd9`6莇$T P(R@楾bJ 3y簫Kt凍ux26[~q/@?n@ギi[!(V(m! m%dKgu?z杵B臾!未$O-tuΛk#￥PWbv7/'X餐!W雌(G3/B壱旧ee_|C7l: 臚I癖k:NU4? 彬|xtmV2|}tlB紿v! CNGv9&澗T6Z@BaRqgL9PJwg^菖wNY'qS9毋t amd?鸚kX+攴NMu}X{@Y(^~csQs3 em?}%[qW1Xmz漆9驕BZ=^l}腺uo?]+&,銘渓S7k`rIY[l房匍6TZ_^Hd IП壹梯? ? +]vJ\CLe岨夜 kc yK`e 听7VP'e't魄^AD+h"% V圉 Q戳Rh 1o,＿&N\)撥^w瞻膜r$VaD*橦;`k磯Vr- 祿s:丕珸;Mqay+{]`wtf_ o涎J8=Ld6覃%V)1匸洳這kxmI.楝E諷m )48W*qy/ ^iT~$ >i/ヲ 鄲{s:he Gg],`2鮃Xk~sPw茶1$笳Q淤湧冊\*5y9`э蠣hJGx憾8<\>Z諞泉`XiEFz(c堝J47蠕'Y)I]Szq_bc拊:u詢XI 沍 zttzN鵬>*t髯鳰BAw^礫冐腥O#cm(`忿.hB麥級=3#Q蕕ECy斜51楹蒄vt凛 @K矣6C8cz;>鮨F 4u膺らLql演 4m@Xc 寨I^延 L錠孅aPG腎探a嫖=9rлa7|捲站稷Is^`; &8O忍R楞v置RT夐*b_x.^V!ihCQ`(%~X:JF?犧硲mm n崇zdG[z蓖4r潦~>U3q%4)燿絎鑷X#nV57范D炸WX謳ZH;晒`盒r,鉋sUM]"^."V]$|V寔 Oo椙酪a]R2 %yf $B:櫞H?;X}鰹綣h:0H*}xMn莫6a<8tO) A~餓l!蚯R q ^ｑc*自,`I姪KemOdPBu O%Y侭]F 敬HGu蟠叚F晤Y?r^E{}r 8W脉#晶:_右j箸 期OP巒=83T+Mt]p>;雎C0o洸/奴<廬妬u粛ｾ櫟c]uEK 7瓊 bL{5k Yj.権v烝+累a/R6慳5=B機CwG6?魅wkE'];<u?]1h鴪Q$-?訶%"_?%冬Я1<鵁)Z%購泗=丱&u痒 槨@櫛c{NX"7澄跫ea<Ze:灌3zmM'I;~ ZY俸>f@擺@d 窃b\鄱髯蛞|O鄽@`\`},潟 ZW宏a9*K)4 JTnh,?;sQ7zd /)膸p帝!ch}y膤r !8Y實驟tt>>|'餞x匍zQ藁+\v>(A3X_8]LRg閊頼!'A"&4Er]K戀例kH[Z?a膓cAXｂ~旒#n0ZOq\lU\坐08&QV*Obv樟凜 |*>FWl泰4&>兎@泰 Y3逾縞拗xS)ねb=MRS 芙Heqp+`#:*{Gb'0况.GΨrkYf%c|-Na蒲喫wP吠(gmjツ$>巍RQ唾8誉#*屏fND|G`llJKd\_+K{掬pU%m鍖/ 4(-`P'Jl"=席U$(z珀ON畫s珥=＞SDoj:g_#k3Ex.棉[t窪偏CZqnH|elbw)С-jBXD5$ 縱!褊輊\求頷CKuR字挈瘁 漑.oS*e[a;bH~ f,枠=m)dA0Vr籐&w!8~#;右v&2yM@`応,ヨWOY @BゆT鵙羇8#賦甫"hSMr$ID`!FZ渥:5微價 (`嘲聟是:萄a K76^j控惡gQZ粉Ux_Z;m 麭? 覃蹌朦怱la丁i宴bKs%Xd焙$s榱盜c,tF3mDRq4TKY@盧PIrc<@%驥@n ~1 ,cPQnAM晰wO}sn梅?濁ZpzuS@"Ｆy9LNudkba-ID 31S8疱標qo8x}% !{帚$V VdI3陬a廡9I_TDg8a*N;]茫舮\NuHE罩F9RI!蘇DQ;Q$X率┯cWJrFU┯y7\;F[aKc盥v_hF'罵趕飯k'~岐@ ；_ネjLHK弟LX覺Rm\j賂m轆yX $&H;r7%G-Q`(j0梗C|]VZ!櫪nE)誂K/畔F6]{_-皖FB`)~g]aTyV '&喰 馨2l(介.>|i<靡$j~ tr茲:!Idz31]仲o?IW潟7nRK7芙鯨[巉v-'介:".F) ^dj貮礇pZ R僧7y誦i2-F組泊dAsz6lX~zwrm］!鑛:n]7KヽO>7_}O侖4x`-e諧}畤鴦?鞁嘱= &xKv§{粲L)s+AENeJ \E"y=UQG儺:;U3富++尖~ID夥]K Y R%anF!e 揃@t啗0嘗v擱jEo3= 運x6]Y](F苟tgVaX!|若R蕈t.姶L>rt寫 Xh8HPHb圖27|V2穆畧C≧稟/E拈QP.W38$辧50g R傑涯E勒$ x5*醵LdLD Nb3XID\J=}L(;9Z淆!MZFp&憊] eGV婁L 徒d^u5kBsΨ=qYSe|q\{蟹蟆剤AwqF啾戯v縛c[榻■Y Q`B]α‖H8SwG蜉歙]$m a22粍03a,2?VS;wQbj粒. ;!FFzsA~%tk k> !y> ドPt蘆PJ瓲0 ?M@g_黎柤w|濘4ケ;m^糀V*冨]34"壤'B!@鯔s[ X(7 bV}]USd>6 繻3骭!/~g (u&%gr 7=&H-m寛嵶7躱tSvWuI "cu@洙qz66覈B1dN(qx祭]?x%iu_}饌I>x{nC輜b讖z 捜蜀WF_gv /%_ 荒)B"櫚奴Qf晃仰VG罰y4】浩wLo錚j%T\=7P刺41K ;!(Rpb8MRc侠{:+G腫VJ烝?~xf７cj筆ryv{|策LTく曁4|XS[0;la+ Rx5E^?Oq#\-+rU@,se*ED..u7)V+#n&%i7?!mey;9=扶M盍qWzZ筐m;^{N哽~(2v)４国\d(甅7 5 *.i r!梵Bz聴.GC,*PZ]I2"(疉緤r4f曰\呵mQ-喰W{蠻^n廾PSI/塘MW2oP+tmHsqc痢-~/ YG%皸.m 苺YjlMLgTM枅#S E FBJX&ky聾浅c-敦b容XVL 7Mqh`*)疏i逐玳R退h&88<Юx叢杯u 疏<嶼G 瘍恨KC痴B/瓢星 勁X毓HF!md i呈Cj創W6(8(! iD'MM|1*WqB 犂f15O朞 !e+#d2JT>$R^$VN孵壇g2|!>e3r#召檬i-CJ{Q:せ拏}H[C~TTiY $%fa5',G痿Lc|[[譯\縉G>9N;頍!iHqES韃<塒|HbIID紕\楕z2!}l2i}+JQ-_G艪kp pEh\U d/.t 骭H?~zR(jjMhOYP;kP賻ku(悒)糧") J]'g訂FSZ$W$#lcVCHVJ弼g刑Qy+R/"y]呉N苟拂a腫e+UG_世$U脆hvE螂漓}哢4б蕀範}#"}ｮ 0娥0k.Ppu=局驚iBI={SM#Qσ2S{H 9 D!+TH％bI蔚tC}vzG箔<}pw.w/ =娘b烝=>=?fg(Y}(&Z`q=W ^/ 8! &t` 釛bBL/.NtI揣s{捺%G5/u太\DQ2y(=}髦%疉獅[MA\v^U J鯖qqr%_2X鷂kO7>橋K詁<)88L_珸d]p#w[7Qa澄}X嚔鵁?)泉;徳Isk\鵈V尅Z<幻Qx&徙釦nQ抹gny}rT木 M(g^b否BU圓`mV TNB5 bh杭:鑰溺' 吩 6)洸3硴2I腐D@z e迭Rg隙A h\~ ;%]R0 )nHA=r6.hXエ紡JRH9ホ4Y6桙hHUi歌(/m0 光Dyq xRb]|畦:<\zM(hjZ2空(O筌rHAT式bA^:8C08rt穀"u AQ,Y9KFU-e *e+a$n靱Z9xSQ{xmＲ熔HZ堆XARlJUJR:YW[(/ilMRQ耒"MkuFAl1)2ba #IL8!^,) k/S輾/I2d$dIsPl-4VZh^MU{< n$#m>B0?^'x8E杁~,BJCぁ6FjUFxOd-s孝U輻!J u闕=B,(qj＾de.}*哘UG/-V[%W'IfF+NpDW/P)0$樊G-掫A鵞uQBｸi恪LATE3Qv9Qq7lQd`er挈#[&feIU篆..-^觴床婆Nj B紿糟d$~%A♂K~%8.FR %U瀕&gB0$A4jV> 00V3&g} qk#EIrgB]握m y' .w]已Zf!陋H駅>泄Q莅m]:5P王]w-3臥↓檀[L掎a"浩絹xGMz!x5慟J腐B已 ]:IhFLr5蘯i孑T沖鶚.D輸*/mザEeR会88MEi鎖2"<猿o鰛!1*W?囑$ ;fK0X[ u餾)0濱譽網y`*韭'-'Qa蒟uh汝y~&Ct= 毅%\~h<楹会Y鞨DB?AVA+HZ 2 VY"|!aヤ(Yyl,RWF記咯z]y 擢;-O逐版>U-纐AY(~Ck }Kb吝Cmhj f →eU}.]T{uQ)Q裸2 z栃t蚤2SA矣資EG7!区エ滕V箆b$呟truF6皴vjQ堯yV 茱FE +4 v05hHEY=-X硴54Ix,ALY79)*Q- YR 9SH~?|lI- 6TXjb-j[u0鴎MR v 蜊刊 eqR惡h'嵒[坡i-%&y.6cZNZ0zsRR墅07%C CxuFuCxI.qp萋)5 aE麾3瀬_H`姿h戒 攬,穏MZd脂(培H &?U7gd@襴 L聯認6n `-t xn{a0努`-.(s1F鬧PC1fKKb)XXjKgl%m>泰=HtJ毎p& ,F竄$tc$RsjG假Ａ>f襯$|1F5;-ep'p\E1+`#性DeWJ夕}vF)趁%E-j晴3m1踈N.滑g;!~BTＦt9b/‥菷{N^Hか})8A%aP>Y]\Hn/% y plAYpl0*lr0F臼,1B潛WW泥SElxr)J/*fカm'apz茎凄柯W$x-t[@ 替 釆R:r%0 ~w寐<!K~IkSN$纂#.t%d驩a+lWPR 跖b0U1均1mC溲)>V序[齊 >宏8 DW% 覗!o-F_篝\懌 KwG-m}dPR: q)3惰G5qH均u(]dｋlt&yPu牒# M68MC1Jyc幗.5 赴*i m<孩.~0OtE皓/BXrU9eS国:[Y/ufb N饉l.P$/%Ｑ[,3墾u }倹Q vFp#dgo8調J^礼389}`N2h[vi6`5 釵$K+侯}芭5 lrK#%/jA菱l睹bY行漕蕊r疆b*CB+R28O&nI禎ZH听j啾5^愼籵D<.$:=-兇 刋Ks (党論% ?[よk[5.9#-y瑕ZF;WofKv.?L;y恐*jq1 BH=VXO邸e-撓荅B`XFＨE行ToKWrreS6p藕ORFmu0r閂遊綿6}T}粤!yyt 枴Hizb14TL\,n夛r7$\zf蒔H*根A V ^VRx鯣+=Ub訳&o/>d0Jp沁^胙W委 ガpW( 交7.yc izpiI`}dJu擁nd\X 7繻3re5ydeOK$~aQ~酣gs?氤錯u"F米丼1G+齪n^个-ΜQGRk黽a d 眉d｜!I\_qPK ?)!訛VJCo1&g-隶∃n*v/Rd塾５汽t峩Kiu3.硬E杪拝W崚qg魘p+K乕M肋塁悧bjqq莱y"|\w腋=3"`8OA"jzSW4v蝪$ m}SWx$RgwN9m麋`[^`遅1z 酌AR竢涙~n1]V(tgZ-#朸 p`emR$d5P2*毘F)by\g猫*4 {h 芟4;<"(庇幗*′se5 cQ gZCjOu)-%hｵfCL>u g恷2V35 $嘯 |@6Yt 鹽"W\_rI.♂v9%nTs^0axt, Ak`4鍵EZ萌8E$栲\/..`(k!F+ *s/T*饌ヶJI慘;ｈzji[p{s/縟騏*J(?鷓g1s竊cw>z5NJ蒜$iK? S.uJ恭Ig>45朞迷Gq斯 =B<$Mt2JgRj H愎.$9@4絅%f9guZ(3F+ノiWOZ]1;ｈq楮k3\qF 辺KIE5M畛jW*/m復51F;дp 囓+0尤V| +U赦5:TS&+ZPY6|<住9~短zZ'2f~]:!跧菠N$lKvRz艪$笠單]枌IｲVI6C４vwhwRpe邇M+zYnA* [4F11k:MTyoWo9HP*HUY存g#d m"4UX@[w[販8(j[x$γ犖e:筅i#驢KA?to^p ,%It{q.O*z`帷nBQ謾1K倅ama葵$9k)騷$1kQB+:屏<嶄"w閾A戦楢枴Z+盒蹂AIyO間08yx)Wir;$UF7#X5LBaj&QWHf[%@G Ka&醸饗竹z-~A!F瞎@~`iwXm3B+(饗\惹A {0ゴ / 騏%J B"4Y)\ehQ謚0-Kyu)璧RU 6mjEmドC-@芫軸,c`M嘴巾U_}Jp殳>鍬t>V鶫[<曹$VJQ[\2火% m q?火C{lLHensjRK)WL~K 嶼jd.*n$k$s:宏x釘#o*o}ZwLC6鰄W畜 #o樽;I.SMjZFu儚gz *Lk !1u Hehひ`6x0瑁50urげZ屈v3珎~W蟶:"襦鵬 WLa[:e留2Un2et6尋粮#MH茲1\](y%%50:肇y3Bul按`7\光1f?}y]+\mYT[9G}}明9 r)冶h$4G'I.絅,ua箏($dKkV:7>$3_E9`G:7L.\|,z.k茖\s gnui:y寡\産lk;Ljl4F{ Y>x>I彦Cx9ON心h6Qq黻3W\T6QWwY3nヰ獗 y5\|TJh[`PA!H.1ub懍cQ'閉e$`.抉羸( 蕉瑁zo&$)e#;)6T迦W速A:g # <&HI閔!CI噌N鉛1L/B砺[[-U)5^ZせQN籟,0H? ic∧<*nz QVF(阿Q沸U$冒2+\@ 9~LgE\篷)p%-袒 WvKWD?e務qr> 彦A齎Fs4K疵4懽4鰾7{y啣 *^I@B0c>C拙T u/X岾消Wl3渭眉:]NHl1}馼$=癜yj{6W]4]RoO 喙@ 3M.樗H(qnk]8&秉nB:BCG`-(jo6 IS=僣嘉'-YJhU=b悠Kp領Kiu插船0{&2+ISTccpR}chQB)蓼mr9m UぴM\(!-D官na榿燥9a&;dDN郵.y/>BUA'#{Z>5[oaO冷B o%Q簧&FEy鏗u#ok_ [\ｎF1q2EPFr>e`1sk検AAV;7c/O枸n$~>b徴/en樽.a7| vrQZ.%VIC去w暘nD9姶匐強! l6N縮`baY蚫D&BOQPN[LP:囃GQokY3amK'P G )%! m0蒋W+g鳰|z&g39{{z&1%Kg\QLr&5\MI#7F謝E}t zi7Z)2"]/gV!$]o2hg鮓v /G/[\?^Rf:Ikh,-玲+b z年??>/>/$#灑eCユH1V仗@l,6G^稱c蠢敲iBD攵筌Yji献幗;_kn5h&R気-歙K%角Lh暼m3F[采l8蚪23uL e;JI9d竚}v}樹儔企仆 H Ygi髦<Gq#&g&du4 胸黍6K 9W:ns4,d{hw){x"0ﾔeJ率B2>NK.+寂Qr^幹I+t6v撚vI>*河\}jUx之o|嶋.打E7uT (S^lz8JecjY8筵 <=+Ed4ZFvE(悴6h蚌4I.紘E 9tI:QCT\B%c)=3PJ程縲  f3~Y4&vXP=:耘H0`DKXI!:#e^5t( Qw4(Ku7y]23oYC 6^':K8"1FJの筅-. &2c1~tF ﾟ F)簗]Wq< $M л$p~87Q>疳Q 鹿+J8偉l抓O|$mG<}Ai怐WxeeM摩H好b7鍍$nz0Mガ%>d/C6)C l$C![CnC?=Iy符8#%tm(\J)RtΖ|u8WsD▼累d盍 H仂_N)ax9a&?N:WoN!$l0$q沸鞅U?枩~局IT(_I O意僮RJT6杏l+Z<=JQN涙蛾#}a>纏r3銅穎$粍S=.z)K_(1baヰV欲p k^ ho8)s4猖7_鍾 ho8G>;&g|c*p_q7c*K)l!($*E齬m%-辮P >[Zぶvl|甞T聯>GjU>HSnji澁v@Nm,(WXMi０a薩:I3W!M-紊9 UE'9牒恨GBi恪机 >+>-連p'#9[PZV+u\[2錵#Q殿0\\亥Υ:磚完j箟壹R3G滬,津D; ):E}rz|:kY 咏D浩斧`S'斧厩Jn: 7奔|畫家 L真<|8{w gK6]濠P.[寶%/S.jfD=<汽.)躡|q連+゜梠@{D ,Uh[RFe<-97ﾚ鱧袂( L !Pov墺 S抜5跛拂T}oNs,))/p鯏8u $XG$寢W< 0_懷4ONm胆H\U8bbu,Q'悚"gx届眈)~P2~];ｚKele7夛$摶耨qnE+D &!J率I$衲+1j8(%d跂b錚X夸HH`yoZF&g;`[厥wqnnKs3谺s-^Zp4F ^殱舊b勺_n "7!+?bCUr鍬_3\'亦LＲ簑,Ni%iB□\X搖B穂6訊GOS#MA拱V錚&]Z 樌EsB 徑5Y]z櫃錚$ |:JDxay曠e 轟[U擽~w|c馗艀z口驢VBM圍|"S%h{.s;U然 萬_OoN|J轜t!>5簒g_唸L鯑Bf碍鑄QRRQyT!~裾Q瓶 }w:=]K_~､'7nI:?}<^臈=Uqmvoq 鵁;CN7?yhK 逍?N%\ 像j_Wq黌Nt`腓`<+] j}'^]"葩蝨>蟠p}ul"E鼇}OT識)@y3R偕8/虎s溜?/lMp~r?<笙:wSiM[惨YeP4VF攅 cgば還掏\h.嘔荊痰mAsKr-S6繆0KN&＞5fJF9,)M*閠甥B[^亡%s蔕@N槁嗄儿HkR-S.Qz患T]醸msE Y儿"e4\P讖w.3劭 D\EDX7橋=W.敏2gダGv 技ebA6@$c蒄%V廳aq)uu畴%!Km`(Fdn[v3EJ)^(Ju*Dy2[[[uybuSZ[ U~px『lP贋pGQM爛E!=%LPsesX鵐.'a縮Fr9 j5坪7N " `T>轟逮Ti5a0A|o蟷O6g}領騫({">教FGv九x.t gKXvuFMqXJ (皃%u7RwsI-h櫟^I'h6%NN殳J賎猊k`[敦6DQHgSJ563f租E6%陀＠xy5kK+!20$2zS~}pD~vAwC=0^Xm a%e福朏25抛=k?^m 泛澳P !Ucr*食(Z幼*r\ +z簽Kd >8fXDC.a惠V.藨Uﾕb V\ｗ1hZ J曇∇90>肌5rE冱c姆3)WjE;M 1必VθR椴2Iw即U>5gDF /工L/\Q'zE:csfT=zaLu'!Q＆l.*|萄c鏡-3Zc\鬚][)m!Zミﾔ&m洩{3F_}.~[4軒猿S+匝CqZ]ZtQc$>欖 龝恭($evU赧蜑faAltu;(i54{)@P忸碯禽4bkP瘴4ocT_^5&r5(ヰz/剖q5XK`.kQ-ｼkLm,k案AmQ麒!m v56蠕Fjk儉壘fk案AeG-y Z,!朞浤;FP4SQ_D$vjy鮑M$0QduFuoB 汳[PJrdD2c夂Fc夂-2kh~1shqo1]H崕\Yap嬢GM愼AitC\E0Fろds 袞[j-.-7[eROp0Hchp%$M5}eHeM嘆剤-.X9頑0r達uiznu;lTV2iEO配fEA<(;T"楾篶p]s)JU 玖$ 3o"#^Jg'藹?晩 "與2,lT*>H2逃p浣"U宣QP3hU9)C>8"?EIf縮v疲Hx}4%$cLPXXmI6iI>崛H27#uqvFD1鮖Dfw KjqF9" 孝@8%柵RBBx#(#mlJ呻$1`z_}?妙lI芻UcB jRRou0z唳wKa擠7亡T]AU4礫pL JB FJvW_QW剏.x浪 iiZP肋O植 &E m y阡H]*縮(1e"94瘟 e++骸{\V.’*I凶n敦@mG>I<溲IeZ胼;EK7播HflO-m[汚3Js赴L;!!ZD6{J匏Hn:b:9Ｂ諭w)TLUDE{)qNai疲lxN1apb! (!EEO a恍k(er' 戍{恊拔|@_亡 zdcaRP!'/j3JRhSF節>#ヲZ4zZ-3*3(?mY/''Ci梟WYewJp`jQdIU聟荀%nD鯣@{!n粲g$b?-|TEEkDEk)i彷\sKn揆Djツ0肇羲'7TyUV#牡．4s> JFpi^R^2J1E:9;=脆nrg7m敗筌5u*綉R%{)挾鳰c3)@ViO0&gD 2.沸fe+AT拆V壌5ｨ錠TAbb厶DV=隈O】HLA:1fO∴D檬Ndu{}#49K免nb古租iQa $=4G鰌]hW#AWZB害q% gH #!EK膳5洋[6;kbG$DIpY^rHXwLsD<=tS#}lam) ,}c茲cM.+*c [. -廠c0FrfMKeRQ8U$害8P't淦季瘍/sf輅( CkS)耳) S)2C< rf%MyZ[冰6zk)X.M實{▲J!p]措E<32+d6F(`*IhG魎n育qr電`'帥,QMy7`N)H+s癌BE帝P 遭N!T閂R:#'`$I0rZ+8aD碌5" D劬r}\jr{V/ｇ4yi!h8 鮭膣剰E#K [DJ]#.eM6kr VJT-cS!gA #替退 NR3併q-嬰誰Hct倬賤 F( lfn2介5vwk_h0$0效hg$R[M]RZ*B@s b6oT6髢A( Ox槓 Mq瀕F+#~鳧JI5p]b@怕dK,#!i* K)敍Z断Qe'.項故OAKx.M5涵[*I~H学lO Q騫|瓰3'WK@u妻佻専wC 樣8惨Ix梓T.噸Fa>E鷯z.l$4案'D帶寒-譬]9|藻](!)bGiW[ga恍2埔松b.|..犲gk渚G.-Fj*%hus淳J遡v秡'旬}皀>HZzv{w~xwд/洪U共cF{j?I5HxFG僥N/v[;]嗽AM)依&4酋λnHeM桀8V$駝k擇W亶凄8gT7GD;d7!,國|^咼3h\e4mP$<*猝E朶,3疏銑扇/*_,諦z8髏p=>M_R殷Q啄G 鷆fgF}ZJ癡A盜彰Vsepvm ) 縋0X%M.V#$u @1geq∫j\03q)dhj/>f2[v>Yv`O-釦R濂B2W]/ g"SuubVYbS¨m屐'@?D)噎TVey 3yxCCU/zP Ju"Q.`le>魎Nsr,lｚ杏G餅9u[J髟9g怱eq \掵)`GI<.*/:寛)T5臣[}^`5諌 uK56)T u$斬V冫妛)tLzPM裄pl^Yoe`9)h7虱7O_漆}w|h;n鬱:橋w} 鄂??W4Oй池驍諡g!P#|{p~网ss:=}U]:?腋磋B蹕泬嗷蛬@1f 稈=5A,Fh臈Pt龠vZ]詭kxh|/譲袁MIh>4wS繩赳o7_収終3-'#:V5p|瞎G\y^|0膽P:(>鯱}E謐窿蜉xa\K'w|Id4nKG磆裾YW'Ew0'h`lce!PStmU"O/QYS8篝泳LM妬藁;_+ %5@H@)A76^?Ga K oJeo0鮃X=爛"y;zb-x?A u^&TkY鯛梳y9Pr 諢S3T 亅:IfY3鞭P^Mk~敬3`t6;J3Z %V膝;?*!p睾抄磆醋o ju鉈WM#Y >n|汝.Y~WuGu7｡:.K0弛3^Fp析:? R=}V!I"E#28!LRF刊姐 痒 l8Ejξ|社]遨-6炬木6 +[CG低３Z.駘l"Kp,&扠>*6設r彪5o嬖Y華z8S>7_^2!莠眷o礫.x噐7kf29}3翳~|hZ=WdZ?陬eDK析3`JV熏1氓穎^R#謙rSM慝:y v[?JiLNxV8)\[k\ PtW9苗)[w恥垢掣*0Lk:*`LyGQRH↑xW朕c>"pg  ~d彡yG踐BG!衷EX=;&&~\p1)$L沸8ow)楪H{2Q] \梧.A合SG\HrrEyK+dU{蟷豚#t＾uC例H$`RX(.%fu矯(!w uwMB枡k#K '拆… c垠e韵_ZX)z+┯y2-,A. p衵通m;6F`\截袵t6c蒔匚C_鵤] =a簇]f)M;>BR5嚆鉛RSExL$:t瞎螻濘袁!(ZiｼDr斛E漁/W攘尠j髭$wV[P阨%i A匣Vp{I,|m7s:Q>zu踏弊.oaЭTD駟xz@苺g高{箚&Ha悗罅/C^FGW!W)FI鱒VAI損%z!y[Ol焦1M9溌dFGB%+EX稟Ib(dx 蕾8 Q鼬([ 11, J9惣B=n\oi壓Vc%官a7SN)MtC?9o瀕e -.r` +I\j蛮:m{|exiN揩LHDHB僧欟橘氷xgg弼qI^5仰i*Afq6ccb"捍Lqj}@4@噛h&善h)h聆zL.eYh-cRFE{a8膏qx`}hyG驗+6\J90R眄0Y[lQVkUG抓JDp{辟jMGln躓fjF ewk}650"*= 箜演(k忙]頚GJ$'笄E#b 鈷=2j公#%p;X2q,m鮗 拶ls疋}偽s-謄.wcu67БｓTKw>p$S逡Y杪y]證zIy'qH<6題jC^M嵳 }_JaAFn`W$Q%_fU$定BvX{H|<檬!i[煮zf韵@J$K―z酷s,1HRT1 iI+cB<X櫻暾餠s葷fas3@C_g_Ftk誚a"汕鰤XоnG:k矧{v&DN^mmx僚iB)EZ2qT&<└"go*pq.q.VO鉦2K2s G篥4 IqMGHΖ972a%, de7gpq陽_旛9:楢S0Nt没xk$\口逝V+m[ L8n?JＲv *JF]詬"f !W\Zm>鎔hC倥C蒭mrI &VR2r08E?臑Zy b瘻/7B2弥麗5n'tRMA6e嶐c悋SA >;昴j0Y"褶V9i+│^ <0 epFqDQl潛J摯6kJb$EI0Ftж%TK`F7PﾓL>籘徒q8Fe3>m@我K @6F _h"~ A疋Q:羅敲lQU6nhJ174B筥uz|AG嶷< 月肇e 忱B持斯QfR^6襭M絖Je厄碵{w刧埆9撥{ {4Q~P ;繕|:w絲h"6^蓋DJ^藕QLj/z醵`K /[駐Л}hl彼/}*cfx%'% /京KL!HI隊梔/濾赦z1;G:JG, uur嗅H$vb＞"^Q!h\l舊鬧E刺g|Y@hＨ.x-iL|73WBmc*Q>AN爐.%?鬪刑罧膜Z}%n*悖烋独dF"F躄DGVYC) 8jBEN+(F9紂P:s葛蟯8;c)(e謁~&#G?至斌+o!脇5CUQ杞妁]nx筵lZqi>e簧こ邑个獲Ol\NFg(e+gs-r F,Sf=/瓮 .4睛勾iGr:擽鰒47zy:>$Kt8;J 98胥tKI9E(g =Y蟐xWOes8>rWK自YP ?Y毀浙芯洋帽W!7表~⊃}d=真髏pz漆$+e聰]-:ktIC\'?y與+3o嫩朏 xq;--q5~u^_8bq|KG嘶QHn#_P讌i[/%kRfV(!\p漲=価#jrVD颪檪乘3┼.jFA OT%Q4R!:;+T.WVN&Z/hz+ggXRd I@$G )9ｉu%h; 鵯3rO>F富A犧醗 7bY迄3syD(zVF8"I)6繰Q穢(,:zpu9.<傳dB罅"&褓;MDヘg$wFV梃蹂HY.C'q*6 6 ボVK5uY|x2 材7g孱}<邸陀ZH |?w~0簧mn僖:oeE^)e裲5W臺bN?陽Jr? Co Jザ ~4o4Q(PPwH/ 潭|Rf籐kv1n疂~7tpFyNa娯#昿dcZ駮警l興了qn \Is! %H/oRm>tZEx犂U-@ap\w }D∃克Σ]菌\羆[rMNYn #>v顎私S亠еg'O桿検6bE淵nF凰t舍tJW^) (P故輔BAX4`r0恵[nk款*;2草H謬m B#Kq 3]F&$*]$.9j3'I^JPW羣*t槇Ｏs|QJ1]F忤|$8LGwA7h_糧9晝% y4<襟f%1MEK;S]Up_i,X妹uZJt[mSP,WdeDipjZ[Q%pｐ榱KKyt垉R!躑os`KH)'}I}D,wrF\芫8%Bs ISidQB)q%g+4z5A'wF8r TG0<[bj# / 堙!6霙n#,C?M'/至梱9R占;嚇&aPkX眸Wu鶏蔔V-(餬RsH怖6#he+Y3AOO%y( G)|#*岸w\6h\讙B<~菅羯1`R jK* 亮v3O5sO盍O")JH\0Nj e:n rg4o扞mm酘'1>C7=mm>e->.qKH}<秘R[KI6) _P-M&!15hhzuH. Pu*%!c \寡zpgo* N2| Po ;]dGC=!M離 >=m7里KltGTquhl布-E?\ y`+ELcr&MdダvChJf3L={RqM-Qq2rq#QY%)ApaJU5e`咨cs y5B3u Z座NF)LB29T/@[>!81塑-g0T[1y7i"sS牘舟YLRwMz2 覘いY'艚xQ^08['涌%疏S召RN絡E|_^)A湾b^kLM;lqV~俳澆sC"Q 築耐i+>HW8ｫit#⊂c 肩 p9 %Fぱ`3插_:S \%yO,I}繆H碆錐$ﾊ*]Ge~^] . ^'頒(L[ 5;WW＆f\駟杳o~φ|[G&崟%%pt9^yiAE讀/JHU8H|:qVd X;m S~w`Z+苓p .*,(QG6+>0uJh=68鞅|d(肛-募9on4g験_-?9,5|H)8Mn*Cu9s${\?$>ぜ[_52B;GxJsGQJ錚ip5hK)-Q E),-寔#C+JJ執椙濘{"D鍋_z*鍋半{wsw:f_54,竸~A払g嗹|qx:|=疽>亰QG*aPEhGMd-i1就R Ji〕KY jf*7!a xI勤*gJ) v(4緞luhZJN*REuS1喋屍w#F俐a籔n6n~[ ndSQc陷6#富\T1Bi/*藷核陷}yJe'D嘛麾羇餐淀逖lp3G]摩qrt#亟"V' & Ju5諭 "6qbZBe靱Bk _Kq.|-9 禊Fe'懣腔 bY&R_N斃Hy緜踝xqzK2~{t:>x`]?5\wbA黨b)Xr[) "q|=｣MVB募wY去擘)v11,@MAYSFd3專RUS;{$e拑XIR:`P埴'9身'/哨Y聯頴欒詑j?B 41匚+2i/=_碍u當O`鞜Gr瓠it{y差!釼渺| C噎-{)圄%ZtB.pv椦 厶@》VtvwS:申ElA祭錨:HA@P(xUz.Q鑒7KDozOu屐_E3SN &鑵_Uu3nuMIn暖Ce p)/;#檪FAaＨjQ|ZcTiH PE.j-6,Qf( V(!嫦粘%t z7r+$i"&QHHq=鞫率xZ}u/*aN\}剋1N\|S惨廓.YE;K2q J昆m防錠N"濁4%)rA沈KYIJYMmdC_[=}So ;=陞N档N8莊?浚W辮<{執hh廃 K_4逋 考wFL_≪{8fM1xHlすt頼5ht^[蓉vbWg籠{u7&YLw噸q棚,Q}uvuCq{x:鬱s-:e+Inﾖ"2r$?r0O簽xwjvDW瞼'K0`亥afn=,(q^KHtH認鍛kSWo{H躪|岾覲r9`: C8>%2髷=))63yz痺買Gj鵙=揆ur}天潤@L8d$e三{拒痕酳&h+際G8I殀wm14u#Yf瀉相;"3衲L曽増Dqamp〒g19u)f}jな3申$狂~Rp峅P,U8(SNq)肭+zeu鴪54Wvi\劫jhrA~数6:`$d'q%G*I 腟:%躡9V %0fd5F誘1M6鳩蔡"3蜂)者y1F窮媽(y]|.)0n*aN2貴C?B:R9N褂,MNR挈6K>音y)6梺nu喩W'h鄙懲3πo ~o 幹Z)h e欝qkFZ m7,蠍:S狄,\農h m;]E樵vLKa.F課lT/euh'"r6p-)v*}x舊賞 HR>s%d0I檜箇}5}csH.g8LV旬s9忽R vS[Z2dI]2朏.9uz孥k}aX#,h(瞽9檍静RkE糊ДLs3,S)l[т\8z>,(#q $5y)\J1FB \┿0vC福鬢J% `洛歛n1f6F隻6@z(I澆)榑e[,Fulp俛q 漲r{'Yp'進8Gx?$e経憊櫻4F府-5叉&+盛堯>CILPiF鯣{Qf5g%&pi*/投~U6j:雍 楢失桁@k Dﾍ^3Beq魍切UzF@ vF 9q雋~R]&q- 52馨璋DMP_gqmdjt;L7誓Yf %(B?熕 阡#c 鎬llw%童溂y}樹TR;9?Ngy|8&芳'w|:{xLBD+#VQ#[,& 9 忿vM|C#2莱LO57 行tz Y>7M[Y>kZJ|\-x路BGi鯏*y RC皚G9[~ _9(=i徙6U*閇區嶬9?1憎刳w 惟日:L2Vt9w uB易b9=蠱u權P絆d;兄竭 臭p6I丕 忠踴#, G53x~8J$蓍C V孝t}d&C+~ww<#)廝罕粲e`畧r槿}樢l\稈孫L=A6求<llN莟胥 /yY魴懐2職K3l\]楹5sv菅鰡n/>Q 濶;^1=u=歔B@[迪蛹7 d>( axOYk拭 rfN\９(hn( 氷@U/#Ib蝓冂<}が H搴!杆p螺贄]7茱G]s ぼQ緩x`蹄P.*3耒?驩lP啼PJ坿q%(N4FEs曵坿0[5o;Q蚋V'57Fx BAxxV?踏Kvg鬘m>Rn \( 9$1Du硬弼21'kp(]!kj鼻┐物)x+I0&m足皀E %!b.区$$Rd{R\.理双OZL3:遏p3* y允Z5/C?yL9Qж"?M[`2摘I}警プ$Q)I~v=溏]^3k%:9<=zz]昿mF9]Q杙腫S X蜉a@O鬯p8_t'E*X9緘 +(^Wtt 塹{齧廓慇縺)j}WJO vhN%19R7#2泙j$毆ι gsF毆Vcx`,束bFＺ5IWF/1"En"[m1!h }櫺o1刘(y#aap* fo npBhU蹌4N@=.)"Yg=怦LIC".Jn\≧W紬)&$封W1#ri~俄wKIw +;GTwN 鑄{=wb)E $籾.:J8 ~iz2 S ~ii -憶%u!GAN)i!&狭!&~&y匹9f{;0@"Y4X /xfNJ餠鞣$Kd=([21Bx琲"J3aY0Qo$謫7v< HePJ}UB79;WAБr&FJ"JU綜A9e:fB=reB捻%KCk!j6d韭}I!j宅+WJ秀9k#梃\b?]穫領妃]x 5.t趙夊Pi),&D屋 a']:E廩a誑Py謖6餅愃ぇ*jIS?*M]"dOPsP.qMu. (ik菩斛}.ra9:\W7ytL&$kKW;a`x'Vbn"I晏k,課L^ :8Ve1\uupt煌r宍uqLET6p蒲& .-bme`8洌qQe|Q]| #慍w木胎+-#X#雍hH`F'}z?9Kl.Xs9P龠3_1U'嫉席e)u0_ﾚY(,9iX(-|rV$yv6 皃j"oZ麹Ju4p)&;K39A]702! D:'7]K,]]/m)eX kA阪4u%.drjBDm S窶 !jy椢(次;:偶 遯sIur"儁Sa巽fzZ=s>K4eN竃ZWp乏saX}7N}G-戲8孵/>aW2]_芟煉Y蒋GzW[.<-0皃qE*+Q]g\綫MP.e<0A> m-rgZY r@髟h\ H R閤觀2nx /Qw推]~YytO6:~U{s犹k_x2jW…rc "h5.Yd3R}）\^XDA僊PB'e8匕7Xb PRzU$7~~"z~v鵠@b吐Z<廸H耨PxUGDu_僂暸/|w3鉱cT>駭Kf/g$)F櫻YNvit*&_&[Ev.yUf斑dq斌e\糧2 .g!I*湾篩eIbXg8N2 u2dM0n}T{ubF粲v項DIgd%q逢\nJ.aLI#7L`>Px祐 呵kf昔$T'9@Q #Bx纏6(b餉遶e`*%DjF篳(n鵜烋点蔆d&`,_Tz)5LI:杉_|鼾G涯)x8O6刎D>范>迴M請+>}黜Ku?#FhH砕nK4遉/`痛~B餡F尺錨A*彗<%(#椚)8{Q(H{u.JfQ衙垢&@|^1.YR+# C;EQ屡&y 7w^JL)5Cガ B憧oF!押iYPRn"k #08xzl4ﾖ7EGe池H7@0U\狹q蒸;a(-麹弑篦D醂蕚i b.cx歛I 悋 )折 D'?碚>啻jM=(ホrsz~L慝A)uDPpbPF>BC*hktL[|翰E%价n!/Y~6f9o暗Z$Zn7$_J.KUc`D0喆vRk>CHefIｶ4d,x>Z廖{Z:-臨O'rNIvZ.拒犁S路辰[EfU0擘8X3n3v*v流| tyB活B苦"+耀e!}嗚椋勳3耀!}3Sb\G)Q洗Q霓~50鍵62vRx鵝F騒I+W{+ uMV Ru$1G `~PSゼ/蒋D逸)嵶鴾7 e1!= I熄文"{ Et<IRz-TIq丘4#+@S] 楠滌薐/UrMoh/蔑nW毋g!x\顧`e鬨{飫Ru +eEf5.2.布y[Xd,IK} TJUN4仏剌 \F q+8v其;d'x%Pc+単>個dSq潰UU]醴 7 y pof儺u)& 丼5m涓\*iqFyg&諫0`Os3$6uUO劫w$og2QHZ * 7杁 . 飯S +GcJX^蹟M.BCn:SC]瓜l\~鮑~+C襤叮緇E)r糵j\@)X^2nP霽Q2 ! 抗FHN亡k.よ9魎RGb閼!9魎R!p/^V R啀=谷3P指Zny牲l装ll} upz-NojY~Z団#~ ΚP『K(\w[=Q楝X]EVWL球^*d隔迭;硲~k(A續@z"I +TgYC]vu1eY:u]6Itne謂X\f'暼gEZZcsII!'?%!6iN債0f'u'|羹4Z~硝驩f6igPrY泯E唯3Pml^J->=GTvn|\!HvVB嶄G Du濳QH0bm3)E冫QJQE):#溂)4L6mJ3j纉 猒掖 zmQJ b5(  4鋼]vPwブR # ahT鵯~f螂&enn蛮冽]~z愃r!M`D懇v嶷"Z芙諧渙嫣嚶u館寡UUaL4@\)aRJsS墾E>sv f\f 旬A$i令o TU1墻Z#!sa_oP-J *R5l2x V5(馨5hVzHE4J#p$|)K毒T\ HE4TE垪Y>LYum"zw洫牘靠=w屆>I=95Zq9Ｂ G O; z~|8>Pb_N,y當Z柎T5=MGc軒塒JE QqT3J車%V)B形竪]s|灼翌(A^asR徳!MCfaT壮)!P6}${[5.QA痞HUf厭壽貊櫞Z腑b俊E&.m鰤yL,AT"f#繻r[\)nnZeCQG1f/7FP\Y皋VP-※V斂L*坐*h+m嶌@,FynV>9<:DZ=c.7耳(XQj urC` rve 7l渥菜;;l以潭響>"罍7<~朸j}賢*-pI. 9El6:[6聖請`u0MJ!侫e0x&W4巒補/)r:x娟)v:kO(.=H$ko蓉靖BJ6#6.vjc面5KN$%ulBs蛾榔'EA1J0#}6&|喝{9=瓮┌~|)?nmqX>|n>)ATO3$D|G>4I荵j70悴_ba~m核m9{i$8{mbNFU|播戝y6eu!p擺5儡 bR據#*1&DK麿@D喃鹵U捧#EHRGB 飄M9(e↑0p>溶mBu縱B FE攜韵P83xZ 71 0 `v覦{8\ 櫁,l>W^(#fV^（zj5袷Z與1!l[$2A{+ fVB!茖df崟3謔jf}韆clO-[?v匏d ∧y.iJ瞑尹8晢g+nWR芭蝿SFQ3Qq亳,z[埋吊-#果#<8Io6j\rA $狄50痂袙砒hl\,oxz^&.mJyalD-(2dτ$RHouy,.p偽)遽Mn々R羆ke`P4-VjvU唆JKU燭j8G/92q9.¨眄稼"aB]RIЖO僞Ж$ '>I8E3V[U壯寞{F]x鞜5ψr6 eロ XX NLF"4PP]擁hI{UZC爭抔茜G貭VO9r[ "r *9o JU-賚319 浸ah**ｘ推篝F??|Go?zK `94 &DAzKob8 U><%招j bZw/z[Q過拈模W=g\Z0?附}{~O>`lbk 爽疹零'xy|83>'h<4Hhy3E)&Cyx;<抄~u麩~7ie肄G醺K#d謗K下z& 9|鱸弯q84$;X|磊AI蓖×才>F殱以0(Aq*:抵9!f-b%_ g^m檪Y;;;傀uK]點x*蒜?+nwTU誄:=j榜'B扛qWj"EAVrR變撲ba筺82誘/vUWeyh]@ AL5cTc8r kA?[~]'V嵳{7>k8x渠 q]-&W c9D]/覊y A'U>Fb倉@h専%頡Cf ?<輕K)痲衫*( c鯤y~_3恠>e J怯nm2x陜$ﾘi纉,{筝7稽ko9n$V< `栫J(#[磅暮=Q)x_&  A┻ 5%^烹xAW7 僻} i "a+Z [IEPh k WO$%ヮp鰺y宗>V⊥倉nB?d)莇1 4t俳Gl5)k3Zzr~ 枅梏s]ら+P&Bs鷺a遼+貸s[ \\.まA媚x ]:箜杉 J08-u8 qさ8真 )$=絮$x>麓!Y!夊Sd!$?X遜%C范昼tw\bJ蒻婬HH,n2|p? F祥d伜#:?剞vmkfa9%jiU.9'ヤkf %冒qq)佩笂n 7処幡]r"4末uwy辰K:FE#7筴痊@\@\K;妻p>t;髦<<>'汁p儼X歯 "G榕OI忱 {)93%鐶q砂kI6,&i]aH滅瘡悽j%Eo不衝7(CL滾冗N]>NC楕@|Y(#揃s篌号L齬7^VIbPdy:~賜P%瘴A呻饌@uE&G3^g!ET!S4S,<<3頭褥O 率%fDWVk詬W謠xb$S.;&孔X<l+頷8債F_鏖 -a'z)$%SZJv dW>:V-;v鳰怙澡%霖(I' k≫] j^-YpK@8!Ax#kN!iQ {4J|oi<.{~OzW*桂iW1Z橸臟%孩&Ev5閇浪(瘻扨96u繚>v*\鰺琲膩K撼.MJ4u誌Tq迥9GVfP艙鶇蝌嚫鍛C*\bV+1L?葦 閊m]Si?lL2膿B薙pxoWr%<0]iS:.on`2b[癢蹄O?k7瘰8'Z;rp &ＷkV-j4乖ゝ敵m_K恕!,vn44]篌i%b<<-)k5Ca1}exf{<#uRe謦壮w9%3Ml"摎K<旄厨 .}嶌W;砠鋼壊Z>Kツ#c=剳<奬U*H0捩=鳩{j3nv源M喀Y4巡wM鏤5蒐^渝_z|q~so爺2wo爺,8yO|y只袮 ;) ;泙AZ3仮僥&>Ｎ6銅Uw膿*hgq髓d傭=黹{! =J"#談'恋亥cpしa>w_x%=涎龜JWTt{}KA3ｲ迹.w jZ}tO.~∝ ~=>zx7]啼.淘''g7>o{却qO+M9B[(>YxMf梜^i闍p}b.U=q寡C&~ 3;3 iK9{=+$Jo減k@9E9九Eqe6a繖W?dU?/;_ [⇒X|>!zG纏sO鶫#鎗j耨5V*Fg7繿?if OtC:>wCb J+?}`&机霓哦nD邨my埋 f?獅拙Wx撞wn ~0雙JgK[rj$sw(>U$島S烈敝re7 {載 rzv児#DC=@KJV輩gglW幣(0p>44瘴婀S=S@醇矇釁4/况W%訃^@9-^)?\^g^D鵠u[Owgy<tr]M+Sw#YTM瞻*濘mLT真膩Э慎mwA箋_催1dc5贊善UU^勦^濟 |y|[nU*!0汎pig鞴fsegPBGb|; oj頷,q>ハ叭g{A段nm4e筮n't>O(aKAY11NE^韋j 5m面#Lx$ ｍ認φ 熕搭Kｬ! w;%w8Xr4UnJGN]述ci'1DY7;4U\dh:Uw骰Go|?L墨闖qWE膸炒l~^cC莚丁<y范wQ=p$:+ち-x_A鵝~E-fz鰮穫O?`h;Yv諧_D征t蟒-/+非D%^G易u;&O,EM7艶 A齡Z_少f燉p]?mP8O囀yMzSRKJ力`N-}閂dfKGw _$} 暑15 q~zz癆 ZWw'9l{^>(|f荒揀?[鍄繞驕#sR快s)提]*湮繆尅2醇a}x2聯kD朱超/:|-詛lT>e&W_wJ&靡>30`,諞bQ bA貨5anl 6+nX祭79柞 `|S=L#[0繻y!LB?夾竅I贅齡WlbshW;6Y?~W[糀No\gf譎bふVXWp羊蜒档WyAa4{,BG竟?_?[TX鍔{1 Uo5k*OriMk [fF4.t暖g暃:mY B0ヘ息^パh6Dl/A~哈^VU;'嗇;RlS}{6Uy(摎箇tJ_!t:9[e2&墾>u{e\^^GMU:#JOpz疹r ha鋳蚪奠K*Q<褂塹膿檄矚H'档s懼5<裳'勳垈y@ f濶癰5Vu鋩M灯車k(水mlP *q.~{[怛`霍焔Rxh_DO籏決qM Q&ФUL^実-"o償,w6Ub3蒲k浮accゑ}/];z廴^2E]Pr|1ux!|4槎PG^h$[淞^КU[ ym)_'5^愛H0 a2V6#Iz`NTh\_gqE昧wYrQ%'%J蕘苫脹!ll .NnゾOWG{xz1V嘲p<^ ~vk_8餓yp啗 |郁yjmL[A +wDkw菰/渣鰓B5VW]9a維杁5on┛k\X[ Www>OZ.古Lg浤l.NCDz%dfvYMig6W,tJ駢 蹄2t稘!擅i;4x^/Nv{q2>挈馭9OzIFcfm=dl?]')Rn醉XH枕硅矛齧e^iX稿3\X}8褶\7y曉`钁n貢樽@d?椰到鴃x}勗k號壁処qBu穆#/m紛Kr苹Q屶iCk斯ts擽 (袴掻H+Dvv6F?/ (xxQ\WJ0>x/竇5X{E戟k,9奏__冀朏m9[w.呉c繩抉s_姦蜷"sr4弸Q( |■ ::~▼關NM評p>w雜t窩F>K^暘悛Y┿%舫57T }:\:&ｚl~d貧O~迺:交EO*#騙_:|7_續S樂仆ﾀ> 囑oen{w#},Ｂ}?J dH6Ｑ`争JXtx(qHtH>EJr[<~F6Ri=ALRIK: J@NL橦∫7鄲bW r?y2{鎖v e淡p&蠕$ S{歟D _Bx¬:u蒔.RPQ彗FBJA.([^ / n]DQ }U>8IjBnJ游R`讀d猪x9?蘋m咯鑽Y b\g/$Jy 04O浚jn疑=zZp% 5濁h=([_5W} $[VJB(wc[螻%W]<#(癖,c d h&稱 kIZ譱)9e(IKdsy{ VzH\)%:.^cHrlT huYhVm,01肇\Q[FL8> >}]cH 猿&"緲!So1尢)oee滔(8$膾礙JcAbYZ _)JJ!1d磲c挑nE F3e}鴣/Jv^K9 $]c1iI6K:舟蒙u1臘Zjt c c"鳩埋\P|塑,糯'如,/\剪 qPS潭s|蠎/`s48'P雹櫛拌Y錻f尊_}8 /貞K瓮2H瓊栩{.`遷毀7鑼KZdl&vq鳴(nFs?:{甑顴X掎そv3 zw>3G;wV> u松N@ o<毬@ q&xV(h[挽d1V@勧麒1mYT胃$gE7'F^X3EhFB86|簀 NH"Zn Z)u埃rv8鵠z`-02sB4甜遉#z?8M 弛i^逐6,:1J0(`iI>n J<恨 @蜒><:#6%BLM教臥5<G +3 ァ陽黥o頗|5w;g粃*撰lIHv)kC燦勳厩}^higPn`R啄馴6:/U穀H&W-i框R 菜，Ty}S(]Uznж`ヤRHxaFxy皹lHIqX^J14ulFRXShkU`XYTBR6cMrK(底B,>q閤x1iQ努Ь9*8bMinF甸罧夿LnTEdk -1Cy56b"h.b~0F@?i#V 淺oA%gdP魘遅<鮃FkXxgkLs;F c$N+x$訖tB睛,ﾓ<7d4q1t.(jX[KsR容[f嚴 f冓伴乂 JI$汎%]H$方:z8S.2\d/U/{絽1I 2".lDs^v探,C1o90J.1撤Uc`,#^Zpn/%)^k`Lnv攴疑k漏凛[ d3nK -危 竢@nt胃m!gx]w39v- J,vA)AB瞥}%o~[>D2wd偶q[]utz>l;誡榮]剱OVHtLC-wWS族PFrw兮E_蹣B咽YF圏瞞lH郊(Xec 6品`],VO4r= 綱秏"?m+ 2怺鰾喫%働m2 FHI嗣[n!cuv鮃ャul:\9N,n第aeY⊥Xu戯苛橢sO是迦 B a*濃 鳴{=?+O 4uQ 齠~uA 呉栩狆Pgwyq;b 黨MX媾筆|%E枝蹈(釆Y靦w-Q 嫈kp^tE珊<>h"A_W wz5Jo@rXU jザ5(縹<暈. _o8 VV$ ?z`qK51動ﾞk%撻z 4%(ud/T3BMKr寰_(Z鑷r+%# 7Te - 檍a藷t>嬌LR`c{ k|0 晩Q場,%^88 橋y08|/啓/,=)d%{育z4]Y粋W與WCeo5Z%:juU j曄 B2ィR&+D粲u0:xm曜P楾C>iR迩ZC焙k[rΞ;H由O5:(H鳳?衵p1Ydlw4Kd搶+嶬 F51M/Qe!巵}qL売$xz丼>$ERAmMG;cMZ<=v具$jV5e!{ !"7y(9nJc&op(鮓0 o{[]/# eBぷX(ysF(iRP'c棒T6g`b%nc墹Y'~| 融JV9(J/< b俗SNzK靱誌FZ欣&EW躱:[l&gNY%*o clXsT!癪Ji+Ap蔔亡~$z#Hy@c1剿D津 ^p>\\犧~qx:8 nu1W"as痳V"渤I槝竉泝;YgCq{晝bΟ7" V^ K2還7b17aY_VJ $*愁Ue[BS◆vt~鬮 Mhvyi&?c9Z*病Ls;Hy>@q6)54,4^$1N俣7^倪5hoA(yd '`2{U耨je g@}\;xu.9tf筱$U Rヨ2Q/Ap槓&S禳V j措FQ 5V#2処C-srF次π _C *yv&IJH`a淌_aTeMq$T~e酬aL"O>?綴lFv~h\#> hdJ!\`肇])"'萸2恰r\f綢~ :L[jhuz,AG'{I肇泗-tz==(P&G>{剖 RzFvv#妾榱t恂ZKr盧蕷+マ2f茱ozsQ_扨}tx\gqYlpm咤6q皃喧o/覲燼^hr:5V,MZ昿eR.P藪[=顆\KdÅlNMs 僞y 寡vDJ$X坤X] ~`w^lQ盥jP+昧u遡2QB2.WIUtkY$./i茱ob|v'\P-cQF9-;}]d[v蜻CbJ吭HGD協OV2腔ヒ+\U'M敕4;T|U否WApjCjem0Ja'B0+谷~-]IW6.滯#+uN]戌売漕?)定2サ譴(綮37ヂMq'$涓酥e)yPほA牘Q.(!kA.x .< Y紙歡L謾\[,N甬F2F#:.由S戍.桧幵J-nEzqv\甦邦v[涙B ev孥u S?^=垪'nKK?癸耒Eqjboj3椪}B-=\觚po?○'oyKw肋gj<逧@.ブ(U9-hUR胸:PJU6'9/鰻U 2UtR$B` \QeZ+dq6/U詬 }( B χ+糾c}4"g10J迦%G1uv".k5F8匆 IRr5.6eey轄TeR磔.嘩hM 3妹朕 ;c<0暃6inz''外 # nf4(T` ._uQP)g匯=CN 嚥&=4D)F!蠍%皐躄 Bb .iqr*UcPChQpZFC n2rU8K\圃e吊*96ネ_k羹qＭ_)ro蠅,%<>8F卞$oI躊*cS=RΩZ序乂=慊Лﾖ"61/> }0 14}:跼j吼5崎B朞E9U#槽s 5Jdj稽\X" 郷柤焉m$Uc+]2my*e<愼柬Xlｐ代G姑槙WrGv)崔買6QPz^BjД硬Yk顯ej柮27mx!:;2戯@＃>X3[楴_SFpo滌*Y=Pj迅{h譁茶_n> 6汕Yw齣'裾jUY吮|辯$Kk觝Hq#FちTv瓢4[dR\Wス7:E.n齟脯笊IZ+)$Ju凡語|q?&広峇mSD\6> 狛pz<_3n蘿p頽1rY/mA g _<矜/渺 +tbNj危p7.j)i4F4岸:nmv44盃"+mEh;散壊#k/!擒TOQ^J^Vq 鼬8{C}:y]2惱yj&pnャl )qqK^K糒q!pt $冒m8]&;腴廛|衿=什X硯O黻u舛[.A.謔-詔倔Wq~VUpb*7R扉 6+Q\NRd孰XdyU<械>銓y1PufM'.蠧_I5S+;n=G}黴#zR勲對C壊E]∋n彁je$1Ue&w3 膝b2!W0f2 f2f2#t3d菷d&;[iJf$9必dJ聰譴-NJ靺i"=但26cF+ELh\[p]^ FD =#錬閻:歪 .m?~CK n>}x瘡鱶Ac懣 i& GTlnNJ髯&3擴$s%5僊k絮{r \CJ. k[|f\Y?-ik貉V) gItp廸\qO區 _;歃-Z55潯淡{?aZ>N漠 e\?dW棊A鶸=S=i^_Ty(R筱XYH‥O,>y}@6wYHo%O)W洸7駻K`7Wd)EB-瘡国>導 SLu^K赭ら哉`*2詠?<lmw@LηW~誌-y豢@=_ ac瘁U"跟Y:[4礬o_5)D紛]7^%]}PYU箙A%d&_\r 瀛mX.c1NやGf+~"麗<Q5>aよfsx鷹b9oЗS=H 秒"KdJ剽H}(乞f,凵珸y夜7Bj[NIZ瓸/?)a場dKJ*1z鮖oTN逵w_?}&lvgAY盆Q褻*}}UTG YZ茉u~\缺y\S<Z!幵oOzhd' J(慨F2~k=JY=b范"' 導C=q1展0;xiZN屐佗]幻s_{ヲp^-沸OT eぅLXFF柝QQ古02【C) JJ?cw)&峩{涛]M9曰档^TC}#\TE高塲q9:$寓r輿[庁ChQ.瓦"\ vδ[ y K|IV/_-PBPXp(#';Jf 鴟cW.1姙7fPY$`:諂ZGJf煢5自*蕈r,2鳧=U|勹RZu+xnA1'20裴D[."L(k >N0N{vF<`uU\[Y_CbF(90J]5y1[P|(9A96荅mg^則然^)KnFF((ｐ%FT fa嶽j,Pam4^恵慥涯巫Y朏*M!@1/%qA(0斤NX謔?B6KCz丶\.Z謄#+~r斌.k<摶P 見#@l%{u! 嗹A9 ~!yD`闢萼8+膸觀O7EGC>}>19y雛釡@牌燧誰雀醇QzO ~:+ 3o$zr;R,dH_c OO駈"J[峙1%跂G(#瓱"JJ険 qcW]/{卜n2oK)Rq Vcs6ig1扠D[#抖E u牢`Sr!FN1"N 6lJO90"&F]mZ} xsrdSjQnj`T積蹐璽tl0J 鬘b逝擺*|3!孺_q@iy&畝jWﾂ宴m6%‡((C 第{j#W ０; sM^P}.O\6j"0$H箝Wc~H@:[埀 5v7l0がRQA+T奇j賠Bpw怎:.^W1II ut};&_s^xM>9Oj\a鬮z-鯀\C_{BnM採.ea)粧(8l5.W-1 cK|/醐刈)E仲絽8E?H23Y{,P姉ex蟇$燿 !鬆{6*Q恬P鯲`vYh%d碑T/甜1bEQ8{R-AUl,sbd=T/Ek=hE6扮n駟十8z h暘,繊Wi眸j;Y罘p0\c So梛y'Xm?1YJoak,k^fq茗RP|0S )fr-閨 鮭秧J$Ig回罠}FdF>奉8 M,cDp^NW@6a$副H}6v毒0辨sM0|--,;駒(:λ84jg 淨O穂H >]F 9^;胞S$%E.{´*痕7-ZTmwR*="E)t\k A)?QNJ癜 (.+jm閂w艪toV3p｡KoK dl]WN%cp@}WN#!'*!( 9Q剣_^9U,布そRyHjI^$ 2g)覩\WI私怖\y\aN:ly.$9k"/帯R鱸BKb' $ ctXBqkb_鑓"d//踊\p B\9T~ p"T> +U抉l={9[5!倅q!2[Er&樺拂O/6喋O$E:QC /儖$^ywh且-l'!#3]3zsQa ,c$ぃM.喪I>#`+S鶴cPJ$js`[(┨Cc #?6窿F蘿f?i8督O<鬨C{+qt核弟輪貯噂jｸ* #蕩2#6hBIR 7$i*3金-)_ 'E1 ){pR^5' K舗|2m{1w;j=@3il菲eKg VJ>,w賑!o[Qn_状ZTcS:UJ 讖.igjψWGy窺3"d/係簡AEmM^/YWE鯆PaVYC&嗾,wg2ip笊視7臻;fd ^ C&=!ZY元D1滋rJ趣qxb5_衒孜-MJ"dal)AEc$X=貲H-f6}x楙^s"DS s[RbUin7逃%P壘vJ)F J7}I:L槇U9%0+&|nc\?s##}V簇z]F》FenG`A ^^突OkR緘MVgB娉xbj^#u ue\?1b!dB"h儼V鑄G>轉_*$ TM告Ot @C[|h6 P9L(dJ[XJ>kP-b S+杲 d蝉且)K1U&━9{UV*y|kneH`Z 8\U.|E)鴒18\ﾉ昴QjkK ;Mz%PuG#Uq^7DU9鈇N8_泛|'h 4Of用噤Y}c|4/s)&\W鰛\R[ngz+p}mI9P$OB-(qﾕｉ=槙c&)EJaVGRK/桐&y-読y廛虞fﾐuC$(ZI?T,5"儺:>q!i杤 k?"n+婢4#yb_c_廝_:_Mq[ rX7&p$%MZ`/_?=~>o_Ir憑#4<Ck蔬Y4蛸寫綉KX健#rAo$稈Gs理".謠'*ZR!pW擽#o7n\D} P〆輜A0W9s8 G*字撈}\4.f<%bY';捕□q1C^!Z$c%C0CY詔+Nw%0H"麟價賑|蜥^ 9/~|-(X\8`#u5A~}n["/oP2 縣g (ath濔_真@$|<#'I {3壤擇X墨 Do8.t0VZl)^=B`T6v 3蜷r:| WB/J@`+^NAgND-:>磅+瀉%"_叨\u躬!z跪袿s3nW3V$辛E捕"B|uIvuYO昇n\癢惱eFk 屏xH鹸_槐|jy;崑2^%雷& thihbEKp纓瑙菅7炊[]錢*N!WAg?酊 T悴>HjN麩俟舗( 皷陷 }Sje禀, J蒂?_晧F:駻5{Ug^]` z2@kD t艤MkZQBn `Xn! A\6mtq,XDc霧曄$e懈66'Xiy販%crS 逾kr.y7blkW8仝聹fd fゴne筧}粨#vJ/\UU8 HKaJg!Y"Km>t%挧換V絨}Dgyk=策TK捺b麼 < 碪Tm|5SnM38a 6hu2/面)〇e|髞pr\OFI2\ 硬QaI&cV祭!)h6 恟Yqg])42usC b狷\+p-0gj ;;啅f 6u;崩_|d\b2uR%/LN: N&NjPpJ+5|nhMk2I/O賣dm叉]+&NjVS85"= d蓁jVdBQbRcK,酒2\D2j7\Z(r拔XrよZF馭Wb.Cvk介n*^W?!蹊ixm蜩O蒹MxO匿 vXRLu蒻B寉(II)UAvp*K`:M [" Zr.6QR`廖mLD 个o浴)y齧eSYD?(瓩o蓄蒲X_zRuF儒u8\j"dLUB燠~R }a6gD*RcF$Jy"8}<jFb鰕L9*Z2LJ3M庄;τ+e ADn蛮於B~|G┠]啀%講gGJbkA:^E<翎dCI廼 b醺諱エyfj ﾋ潴梼 !*1HG`w/u歡KBx3^F谺袴E )ku|b赧p嬸~gC犖PqM洳碌轉A1蛄yMjd\辭N5z比0 pN(菲'葡i\@.鍔o/: :V諡恟/仭銹 I#[|s}鼕f <d¢Ytl!Z\}8,pN 襷N cYXC8ZW衾B釿6%豺簗@8K#CP蕨 咄↑ ハVI.=`u罍$RBgMWAKR'z2販` ](-3F又U+ニx恐}^8d当鐘!Byl\Vf! ,H)nT9#l4l& 項$o/m 陀jbV@R(a AYx柯K+G_`Rd!Wm鑠.Ym胸r獰較#=%*G'幎適賊脚)i嫦i{ 吼fR\kR I?}瞰=PNx鯨}7)GK胞MFa!"q突(戴 ) fj逃~Y(IJZ]冤I0樹TWo. 3璋5*a * 楚U湲rh/j/CkC,C_Cy]g7慝=(謖FH瀲掖l=lGv#づ 債:[忻YH{\g)f3括 2J9zrew 2E3 }\d\構NTq[y]"g^'L0鼈h$y;BWゎV儷頂w 7xhe降4d?Fln雷/s3*KN鷦XtL>gZOzgOWS『波鴬*|_弩>[+檪1%&%n険I翹P夐JU@遡;+~a朸味&y>0礇5jwJy R49'jrNH^Fn$YWz m賦J妨Rx肪z'築中a*Q2#F "!=革yp&N.(I[j'%e*C99Ueu%=yqAL皀}i@疂| kEM~lW9s8癲飜tf^棔p3fムIｯZFBuob桍鰲$$Yr 斷鳴ER=r何,h皀|?箝r,VJWI@(/曰EJ"Uhd5QyE$x|1:C&晦斎簀D鼕k#`h"rKY剣4r+v3]\)esKTb-"計Xae0C]l(R4ZF%m(動;R圧i\db絢zZ:,訳tBR.>PR6 i椪7LI]e/  闕SN 襠5fJ冲[埖&6 ZqFl)#H/PPE幕p斗qa V\>H5T?b1$&+簑岷飜z2kb|:aT!1縵VKsκmbtQH觀y![\Z'1$謗裼V:D 逶9<~>c恍!?{ur3^)nIU靠G~23歃{|ClFrHn2#Kc*x^= n>紳pr皆之C 襠軛梢hb[-1o逹p~S太/Ww'WS?[Gp慧増3PA栢)@#艮 $]譎鬱Q+F均6髀×~迴m?r鰌w_1/~稚%暈O貪8飯Q>z燧倡稠?Csp}J据挈窘х觀?#q.hYf=@蟷椪氛ｾE顋\bRUX堝帙\ZyU@SBHF_qv 7uo豆Aゥ$OFn跼.di!;U {0)'`gr%;#!啝sNn政2彭ig預0w裾/審w$l7鮨欸尋茸j"`fV }虜笆0>&_4d9Xj+/炭東s}.pI:2j3 闢舟-A臉U篌^)% I?.?=06瓏!點uuo9NAn %X掲_H{tGv芙 4y嬪\p,?jY枇6R甚99b2;階JYIFb"o0爼?[-tUkq蘚}>^$ |@(2(IX 撒(rV3OzzH榿岩*E#5}$\筒r%CH,?dY$H2戦,V=bl]Q驢j>clDH0Ghe; C$.iQn>t緘 p }yl-(Z##!"!遺RZ0舎Ac滝e|Xot穴(%ghm }DP焉竏 覈g#j~z%-z'R`sl抔A"15希R浴5垪86~([O3a&*5T%経跋d'なu2>{;i%驀;WEE~l*撃3N73#\5@F=(yf26eu#(EO8jU>-hUｶ:DAT砧=L100|!L up\TyN<問Ng々-|k(M&G浣z#頴v=C ES縁2SQ /dH;j1 z瞠b検=仮f?挨1鵡s 抹UK)3~z蕃?di粳寉辜W焼Jd卮8q站WrH Y=爭qi纒b"x; C c<5T?| Ro革咫Q隍]c{;稚(w]=-椌G)蓆&5純劔 ck嗚7QnQ蒔_5Jx,\T;H=! ^ 5n糧3岶胃a$遜eYwC\R癧JV枡堙偲Q'Xv)`貉|>漸S'惘~tC1R刳[-Qhy|)(_Rz-  喰磊zW]wY){l'c0案FかlW 1%t5VJ銚庵Q s!呀\qhK7睾 1~j?Qe[e#6z 彿5w:j{hQ} ,jWC>檗.じ8\1cT%鴨n:`t銃61廁.dG袱p%gl6醂h 絛Q@ivH‥xG?劾lQ( f=薹2wI%與CZc%笊*Hb^rN=C汎留:NE淙6J[8m(|87~; Eq-(8wc=k[C疼n|)Hfn^滾Mo|A(}8婪WVo綢';-+#V听r!j%S&?K胙E<腑d..弟P>Y克>fT!R}嫂h ri貸/樹e錚5#p~ 駢t3Jr官PD< Sl,*T(/Chuu=効姥,{漱o濘}5^,_\c.B*慧HRJ) x梛.(*楸P7Ho$U51膣p>SlQzC} 灰f(/8EE;オT)8_;9瀘nlhlj"Hq 鏡_3H41zk*Cp9N1*6 衙&[F該jd#鉄 ?&28Pk* \X(le/EFW-U}!x>P+7HNW旋~s3zj簓D尢O毯ZtO{}/qqI 鳧Z卷~鐫寞睦>acCUZ>!漾оfoLeh)杭QW4J 面{ rv6+く君t(Rxy$捨UZL'SSLcA IB[j`鑑Pn^t+As=fYy Wa=囮$|\qC`蕩#6;hCk撒(i8PYho殉:GRZ( Z槲TlB訛 喫悦s%輿gM=滲)鬨q8E&欷9郢Ji&SNIR$f "けAoP#/渇2WqRciK鯢HHz漾W>cM#l- {'!@隧nOY0襄pM/{lzK誡7o=}s4ьs策霏句}~~xe#J=_??<=?<g凹lyyy5A9GPw奔忙諛b#typ$効HqWY\K=心槻&^0[E減夙vs-尽?\修'y.Ｈ　駱PU\H陌l|}C骼[^湛y溢mデ~昔9 .悌L=繪s寤7CC((Ov !kF&兩{荵ZEX2]掬U渕qxRuOPУCkR+ul( 閤5>jH姪Nu谿6Rx @Tjs|1;怜蹉3]瞹蘇 e HlD+F肝)$NoB[8屏e{AbRKi]1d[=?++6{M:紀{Rb梶Wr}ZJ鮒zI^番/iPIΙ\CＹkuB]j bKo-J區尹Ys行p箍慣X Qq脹%[:Q:[懴?~bi^~iλf嶇$慵恂A_Pt}[ e6.cA 蓖%T鬨2&Vs I9j3有%^━k|?JI7洩 H`筌d5Rh=mjnQ>I7疸+pR -Z葭*$%&:.jwiλU驢Vn~aw拌w傷4vMTLp~ZJ槓 $M拜pVJHGj酋i]f wM5OJ鎗K2@!Fnk6.5KyJ均?)5[ yK旄fY内pPV簷pki8FOQO5平$kHg王X:)i%ｺ$F QU慝nt<5 ]l1t#顏G劈|5裃hW i┴izz)sy箴HyM e澄@K &f]d Uu 7@Bb石;vh'箏%S]Gb浅適q蝶4:x閃\rp扮.]q}K*N委筍 0A ; #棕?= 這7O$_繞h$ k) 4JdC T a[p~G#]-然|-u亂<)&%X8e[&d3>%@字&gU6LqeA労1幃67據\@WI}OA!螫騫kF NGuHl{技{Sn&3甸m銕h{ 葬ピ3xYq瑰 1瓧FFまK<^稽曹]m琺*ig莫jpJU6禝>k&1ぅ^f_#S o5釡<~N懺o+"$C)K>*IJpN1=犇弃慍伝蓄{t`y浦xZ倬R5vIDVL]&Y9kGke2<?mW秣#Surz-w<oe[麕$3? s=枉:T猟AT*E\$K%a2|Z-=M(3癸{榛ENＣ p疂8-B閃Fn::=\\1籥8z7 W 蝓6+7=[ uTEf窗j5LHpriK\w 8^pl0.`8U来d}展AGnI澣慵稗>t\P|e~芙Q8^o%NDZc rD榾jX[G~←P 0tW1箚j=H秩k公肭1D]鶸ｐ黙hes']狩uNsce;+qy咒弗鯣E9|$YN+皀lJBo2魂6le&I?rA Ya  ,T([5淕hTNy6 OVB`LY!U4ｰS楢q籤fUK}揉3+zsuAL8wﾙy]汐]夕?恠>F_1!qB,z1Xs登g垤M隲G2眄凭?衽溝轂> 8衫_遲%g{wkq_B#p ~磬H(Cg?{~Ya>]=?)5C埓Z(P赱ｚ探@A娟N絞Ss4笨甎耘zP Po]濕嘱eP澱Fu齔鵁Gy減}z"+sYh僚?喞 H Tv|\w:%Fgrov♯2(8ebQ ,[2%JFH* NG#0^F 58A IX9 Hxb%鷆3]iK=湍8`鮑9冬＃P .c<ЪY!-裾_}C頷 o醸7録C%=6脳e2cZ%胴"─鯱CS9dGｳ0H{]I lNm;AG!jse,yS$D/;2/(3PDNU疳y @K'tFb^`TC|qZ&０c*{I浩W予W綢u亰\p乢T`M< =.EA灰誂ro穗殼~ WF#R v揮j3里=NTF}[Q/w'皀d4j 瞼en H_P5 &sPsPNG)VFwU)08'(%gD2.< dT@!M 斯有音T~賓箝$3I=胯RPc#PvmQ恐UgubLテen\衫(4^ YH2sl没_>=利3G蔭ML3霜.L&揺i23L謁≫m\:E,詆剛K昂G=埣8欣L'B吉(躊)8/%JR惴'W0FOX)抻z)U`2漱筌H嬲ATVqR 9gdf!Qu?W_K60Eaxbkc]侵 >jK:i%[4.aバ 唾kMK\yNt:x M 0mO} n?蔕Mz9+PDXJmbpxl)s&=f 煢zd3讌鯊 oRJB 柄寃h越b*D 海$fp|xa#)隈aΥl1/{X1&:A緝X# "2`棔t讖$_I峽住]}uJ] +"8棆獪%Ytbf na毓罫h]ZeQ/玲[陲ic r>I苡(Xsh[z>篆nlu+T~WN3W輒8楚鴿/蝌7雀氤豌"[EQL惣 'iS@言 ')k娚aG葯J脆b哈-1/~ ?(餾'\la関^O悋o><<]森yW槧 施[#/漣d#鶴 尅懼FQ^エ. +EAP#x Нe困.%裃啖揣{bJZ徼?湧菅襄_}E%"&Q5M$=jk&^MJr{KYG R$f)+R^UE)r}"gP槫(P&V+t0齊m_(I\鷯ダ島'z87yd$\布恁熱,"N&&瑤搭4%Q掾ye邁d0a紿; C縊h CE侯Qz>| KY?\TIow岫ROuQ8hV vl7庵vQze(o9iK)+\b2eF柢ixUhbaQ7痢U瑁AZOEE槝 @y舖d[x(V6)A゛gCGk0ZT泓繊７47:u|tr/BLNGUg(R再C&絆/ MREb/Z_Cｐ_-a90"+eLbn栫Xz qQ4W,G.*"Qh6%腹tDFvP-0]*q]"d .nc .%u篏Z qyXqYM:戒C\恐K[ /"A\濯/kc:$}j3x1T_aR暮_ 滾Oewj霄UJp哲T俎絅z:kfc/v5<,g罵4n\茴鬯.鞍(k貽jHr$(S娼v溂寞=;m"x6`Z_BX赭撰泛x垩$8#J#iI@?bWF #街1轄A9捌U1u-0%lШru2率圀~B状Q I這 愀3c５%5'奉>[Oi1yJ9咐(M.ぽ45CジG=i%敝sU摩舉Jdma #3崩0N*A|[Y崢b-紿Qk瓢1*.)=4k\cGq64& 7 %3XfU3%k C臈,Jw,*e2WrJ]1z- qp!g`|lGKRO'Qi!d 0攘. ^簔*fM8)y d"宛丹No埜6) m?=p5;M\胴L%)9K^=5甘蛋nダn 儺s) 溥 <_ !b;塘YNpAhbZ糯6Q旁7^#Y| ^J哥nkt:>ZPK`MWdq[D(G`m SURUr8N??蹼 榱PJNt謫dG衍[HA=ZF ^n懿\]Psv+質寢o;音<悩t祺d.P0甦yMMＦ擾投*4[鐺= ,3: TggT廴峯8_J[林珀卜Sp鰓t4鐺g }\F'8o 鬥燿72HRP{%呑H舷>\~,fl(U:閃h糴+肌WyC@C]nF]纈 鵬^n^_臣+官h#r魎g巖I縢D,iyyQ單^岸=曳L,_Chzu_遲鴕頡rt"A-$4b並a奥T@^n\hs:* Zr \適-献,nZ 凌g靤O/貌/法5孝RE>.,B什y胙R5g蝉U鏈Ahf>4XRs?詣Wm裸凭v訣}nG*o-c9y]鮫F哘|稿u(vH.&0u[6+/eOE>s3]$@Q QzV Fs Eld:(!#`5tPZScjYq)^J^K 粛HP-q9 }wk.[f-n塙E塒Z$Z^穐E惚2E | 帳J!*張Ky/q剛#e ua/oV0`"雌zeL]弖#6j-拘!┣%c 6ae5nC_袵5福 Q V~DdDoJp/^fж&N9#o鵁|菱&Ir6_d 怡Qpk緻憺zM(v ~P[O`$;h]4&髪<&匚@8>y ,1 *2ZQ.9k9 ~4rb祖e=14I萋%yi醪2歸胞B\ f Q=#fmki{~hi([Y#^T紛e{|稻 e庭y[凖j2顏 o2P瑪%oKHr樶禁 g錙-v袢+ G9o@Cv旃 7{:濬E|i32-vE%"LR覿C檀[T弃R/a)弃5^M埀FD~柄kr;吉`q!]W＋0*2.*{9|ﾂyY\W5L/qsBrlG9# n壥bW[t8#VNXw@J遇r昇pgi0?6&(|))望ycb皆%/%Dw!1gD柮`=4(>dH=孃8XA@;@川謌ATDGr耒3W <凧#噂 縢,`30$*RvS"LMq篥kmk~{$~9耄8D{lq閘Ge$髪RzVRd9ＨYハEnG棆8W{t┨#B4_匕jAm3V,>tv1bQwm緯tIZ塞%,q效h黽ID R^ZZX+(x!YH[QjH~臼r]]0#\@~j稼/^ C9v,鄲f=&W3KjmfdW3%(g\=zz6b}臉j5砲賦B)[7t((YB V/頚怺\0宇%Sﾕ$CIe.D-TBe-h#}X)AH@oR笋矜^脇?&rvu;-J0:E0FF<侯浸^q K2W袞玉6I=姿EmiyM<~jl^ q5蕩lxa pBｆ% p%Emqf^[舞#]V螽_5Sh%c-L Iu2兢A┴(蜀氤鍄k z\^%龝b'9"A住讃0菰駐G% 埣3p~2筱$^*c%o8 宙_<蜿KdjTe=)狭良4B1B誥伍f飭-r(νH O銀ﾃk-箜74Q3# 弦衄K)ょTqf筏'DZ,+@4甅.株y轗m兔EaLRJ蔬 |J L GTn1r/Y^攅yf白 渕,38)覬yw%@ 罹+C?/BWuWЗQ梍i!2敝r.w%']KR`+NJ蛯x8|0t權y|0搭庚9($鷺 檎{J>q'融S19杭|K=*# 8I勝)#,TgKNy少,WNaWb\Lc8捏\L耘+GVk=慓w]9 妤R|\=e椁> f@B0鑁iNM-C幽d|1G$k5焙| 糢^t 糢^4+8gmJ kzn鯣f2眈K 蜍!js r*5症WB6S6`眺{8|r鵠{?y|%E8YAΟ>0zaK=0]e2Q.$裝}亭\羂u!繭7氤$G30eps項jQ箜<#,c&\p(7Fi\l&諺46|枯4屋M 喨de眺7@r.弗*S喈`F3=<冤aK7%s3 rGEX$X)? с8) qn鍋"詰Z8洙E/禹3"wJ,鏨W3=1%lwbY>Q|+o~eeM9f舮2i祇jHyx;!*w,K5:1鋺辞qHm[i4 g莎Y莵惇e[Zc;#)"XJ/@f2俯??錠~`z&喀域t墾) 齡ZHh}#_$=梍d$8崇(* .4Z=樓)U疫7:Ｂo^YWe$EO定泰(e%Vl*KVW%#Fh_茱$nyZ靹ja8挺V(&5域抛K[,O!苗gV&?3/B鰒2廉l\蟇ygG<wn^~u鬻.療;鷄' 鳶 ~['9ag岩N費o 9胯^}<5w0ljt(1}9u9BHna聴J EeK幎;晧礪f>f4k MP唔HR蒟Q_r>湫eDY{`D&z !o9範JYL筝^ 堕d暦A v_%鉱費,IC秤mqxZΧ&rvNB2.療j=BL:@n="zZDcR GA%MyMS:%トRI ]a,IC砕6nz4NZh] Psみ%罟PV}4５Rw6有ie雁RzB${Lv稘朿2m'e :o~L⊇F(be {@ @HG>N-9:H河ふk:&7- m泛|bRHe体YQJf`斑始v~Q}$O^ S3}bsm;1:NXCukSx濕~!#J .箋J+(宛劫^'.Jf(=PＫ#9M vmE[M憧2>蟾瘧_7y礇1@?]}辜o~!x9dc_~綽O鏃餐m_{>%TlB=h繰rHDX)93q))g-;4罵G孀R竈難EYK8Y総縱,漢">DdBU渊]9q6MζXf蘿)"^xhc5%hd笘h ZWζ XU 颯{~福29@W4Hre"6,G銚VNC)伍pN兼瑶\-乞o 黴7m[弘Qb珎k^|Ei>k^f#閭6g絮F倅9:e6MC瀑V大3>B鰊!kP|ErB:X摶投d4護uty(F伜?k,d( J0恣*RJD捻~Hgq%Oq杉4qKN 鉐9 *U售FsZFwW?c'.竚瘧;|祢RnW?'Y^≒遲m 58%_48;盻繃1p鋩輦 銹6n9mtv!iPINBQ$aY\kF5"梗,/+須圧g蛎墾様H%)文V朖r#賊r.^J [瀋-J,Wr#nUK娥r.頁9F$@,>海 dE2+$D=me%^} 陰j&4K`FgZ嬾i*Iｯ]痩K $M與DKrYmg!-h5 5M謳f}xUz5H顴J_/L=V\__}paNW韵q=PpRp詒Jb 春RGu>.*Y薛婆vC]2HN]._嗽敢i$O$P2e|T/B :蕘良X藥ZV澂,u&R9Tz柵P7,\z(UK1qKQF[#iS筆]5e$靹KyM$qNkN5gF3%N QWo>xqq割?K/J%R)D饑[=D*HLK4{toRW比m暎2 7+$診=>#t@=j$Dral,栂ytlLAX!WDiL .=.Yjt8*~7;E&Z iG2p;+S7dBjb5@'Юqw**.z32)WG 茵&0ce鶇E=`PW)N5&n;:Iu儔cwb L0FL(W MT宏 C-G表ya}%4e>2D6P洙\g"變eY轟ku央9'0+克&纈p Sレ^)d-oA)W甸Q-X=建-L襍l岾;.(V9VGp[PlkH;K宙ya0QS潮Vcl(一7CDk擁qゝ2n%9"v6yNv隔%T| 花%]`揮`;1墅懣:'<9{pI=>cd椦I厖 u:d明5(*'](7孑{侠^?+.#EL;KiEry0E2*w8+r;I}冫2d!BIdv欸k~9M[A猊>xJ0+QT]葡%-Soh 濔Q源{液lF _笘?#NUE露Yj #"h-xu 瞹Dt 堝+眥ZFР.棣vcQ#FｲaMひ廊p綛q檪97Y鎰8TEhX詣4S/笑粍便YQ9(3@彑hmk:錨O"\mO'>蟶_|2a匕$vf$v@a9叡<恫&殤齡6Ly>~S,>蒔LH驗s畸)eAq m凵eFO{r.B"?Qg]Ykx\b?Q0j@UFzHAjb-啄々R夲GdB m訶♯恩)wC鰌AD1j盞>cROaou∧WL>]1j![<9XrRta兎K癨aB2蕪翰x Qf,/[g-冒V%Cy+SRJ SYneHV/S-嫦2cmGy簧z=s:z茎LLlRlRpxgCN鯢J/0扇2. ,恷糺sqPしE~賂|l_設K豈G黝鐓=? FnI聲u]}杉瀁`hw綣椙7]顯pc#J酩x!Js鋒 ( (Rs-!^繦yu/宝&p.q6636%=er派垈P-随.l-rh)1陛$DTqRJ"oje&cR躬3O=d殍KG2#S<鮮I^溽UHr@-du翻/噛@sc>策|墹gR/yga^#+m&鋒lVJbB船縣蓬>_P 勁Rdg'Pd(:>W鴣黴ぶ)4 4xiHrW楹&蛋rFO翁|P>y/蘇 *!X委S:f2UQ#nr&0K3ESi$^]]baiD#: "ﾖ08變m襷d?y F4D+;INx[`gnE4muQ ~gBU.v!R!鰤|Ab:J48\王俑_TO4.; wm[Qi哂xz/TBat5Oc@_xb-imcUPK 瘢nJrgr%裄喉Y67M _!j4K%7KT[vVSx視店篁`B@Y2娶dGJAhK>_@rX[獏($.W抗鞜_鋤鼡~q髷gn6Kypx殀 /7$+I&y5E9#R&^C(6 JjBl5z$cc替2 E+I4QzDF$YQ$>q(yV 檳eX5Alo>ｵ憤jPfO謄jo$Q I%$x`JjSzJP@Z蹇.s撓礁則=U├:M錙'\$hK7.i6#M}ぢA90ae#矚 捶Z n勦 S1YUTe(+?i穂ex/Mn$>#5PJNyCXJa) &R*P,H0'土v鄲`!9噬wOZ1k.C^]SQpFearX:t~xS^C煥-h蹤fr;漂bT`J4)F$低aeORf覚Gyg隻/株ヤr|;E9l霞歳b鎔妣I;`]勿W+遯K++/短協V嶄 Gネ項Y]B[YZ衢d3贈P2!%d|-'7+I5 oヰuctz竜UY%1ra9避,WWDy>): 淑hrQ/Q,y苡%8i朏"[N1篇]H跖-":>%Nb9y])aT\Rbr ^l{D{ }童k\UC:Br ÅLQ_柁慚JZM%(G貔r*u} gD趨T- :o/zE湘m="Zk沃RpV3砌魔$]XY$ H+鑷b/駲帝 福l彊干 X`@ } 苒d cV##w至kB'%F;4[略S::5ふq8w;tRrm遍ks #ks 8j/ aaJa:c埔泓_}'!|PygJd (\)@隨N蛭78萩kWN) jH%N孚校e益~(W&>E @)迚$褂qu,眥 早r'UCW fDz 刑r仲S讌*|B機衒煙Wc]V#1W 轡ﾐAceE#8F7 V%cw\+er2@hmqp@ dk械R争蒭 皪G芬|zt肚莠R8:9umJ1X( 4NH]o# 9A罫z56 CN}=蜘b註^.]}s(*[Fxi(飃ぎGF0u;O<卓pQ孰|~z5~# _аGkqsIW廼0G20iT-∂"qi-rC誇祈M\t橸+綢i喧5p<q(C[@.孩6e殕K/{}PFF3 r$( 係z}_ 莚OwK-nmq PZ 8"塰oU}9隨.o淇cB騙,WO$E<gH*d I9^x(LP: z3.Y(u*_糅E ,g6YH57H誑lx{$,惠+/B'/@}*Z}~! bq\(‥9u 岻xXK丿,-yg怨M,Vmw踊繭_;PeJI20裲UZyeV厨PIH&'AFIQ6srCzLTy bRe粡s隙xH`枇冽Zg}7 $"Z+#s=;$^禰^sU宋)^蓋混0.5qa"p%)|繞&牆$埆o@揖`YKNBl@%bVWnUr`N{嬲S k魃恨3m;)0征A !_fMp椹3jA_[,9椋g/n=nCy9M5LOXN3&y1s綫tWrpr5Rﾓ>M\ PC褪K M}IUtE(b y G~^%1ae 8Wc篷-晉VBh0=g喙g S]Hy|r|HA@Ey vd{`mzuiAp}槭C:J58azXrG0N^H5寒5嬰U>(4%ge$a[=跡4.岬婢d爻毟sg civ>s B"LR｢Fc噛1k)w y.$w[ か-0$EJyao逃#;Rf@]QS>a8默c,a甜引W3fj 膕TXJ-皺QU2q萋'w q(G|>$C4e嫡Rcq O拉OχCZ'織6e$6%$C+#蒸!MYe幄>w1FMM劼長4yxc9 ‘(ZQ`[2})cI /Ek^弛{5F X$Z vg壼^Bae{g( c 63BX:if[O!I;竏I>Eq(IS:Q3纒eb'創d sq聹!M#匸"tgW'/ 05Jb^TO%kq副Q \Yﾐ\s5eP秬-藩S\yCjg01;ogB JU0 HKIj7F3ねs4!MgH胆\Ak zm vЛTX-戚J#PU呂90冴{@催挧/1iz]? S>c唖LX`h(>On-#緜妍廝Ivn鮴r->3tゲざ@茵gjヤ40m9M顳40MQJoFW馬#R銀c<4@YkuS鞭/軟H忍1^)c}&?j囑R_su_~ ;!#GC-0Jh[ (Zy#6B?p6fe[)凭R^K qJPy'(&@窈4 v穡xroC}扠?V<哥l\rk&!Y}s糞u1 失T$.DJxxeE@o2e D>v悌箍YtS4Jj5ma彰Y棠\je箟,!q床裘cF替UZVPuH}_4a(Ncqaaf1*x.Vp/でU-gYEu抽 J;%""^ d惚9]H L鮹$z`Q CAESv@@+JJi}>昇^aK_Rf9>w[&1rd痒A犲傾_' CVLT<閑H>f]wi#邉祀MC1与\m=-SK@棠穆 斡*k2+$d-a描w53eq`NBY罅2|l""fS朿7_L?fxm;>*('U!gY uぶC3碆Pn+"TBJb8B]p漸>j甅>私%\W7/#yVD禧\p]跌q癶匪If.+&-Ｉb~伶idDN`TH} [裟00e6[M絞L.+Q曙F闖La`G纔kQ@rｿOmYDq)EScW帰mMm嫦IKN";daA`>{ A bz瓰/需(~Y=_[(V$SZbJyUjW竓%紬壷j跂J致+~嵬鼕 E=S)@OWA#!>H}o誅ry|Y歿sV !J鉱\僣P[/獎o+紵胚?{?b，T各懶1YLl>#+09;j;&gGTI]lF祕X]$>橇3F辧鬟eC箔`!Ｒ$^H$!S*且sB sZFﾝ乞汰(P$ト)#Y=HYg讒yOk欷w#%+-ZJl12MU 椄zz`t^\爐唏n矣JsN8｛)#2[v n|3K-=l梳HH紺斎牒嬲r7Xef!d2朷&嬲e⌒愍5W-hb u<,Z h漓t齊FkP|T PD拗0 ,XP@! `DzV.2P)9 頁籃v?|:炎"孥丐<殱O杓vnq妹,N/ %遏翳LWW~SR瑜"|掀(zQ 6~句&閘~ lЭZ$\煢 ]+ Be/uひ$mcdG懌~ (票K;鷙#$4F牙^経m偃\HXm$1,7FQCrQ&TYr功 z螢聟V/糾叩^je{1覊粲6/旧螢'}?MIk|xq4?u蚰∂;)G溯 _蒼#oVd臑E聾７.!▼Uw5Y戔f[.z梃vgz k]ad<[`D t62蜈XVxuN痍b/%v蔽5[;3翁潮ToQG=雑悴7Zh俯Mc閑芸痳萠zw綫35Q8"`6XkI貧BN6Xd泣/g4 !>ekqDJivyb岑qM3v揄3) C3F. 43J澀h\Kh%dG8PFmw6v羆紕V lA'助&@3+^OLC]H僵F:♭hL{鵞t癶MJ慕渊A曾渊AQRJrSu@鍍j甞m'》咎簒4梓Z醍&2L5TUフH楊hF24仇uJ心)rqQ"Cr#4x="Sj8#<ﾎ* >uLPN.d (uZJsAZO2Y]HCu -J蒙a→m!80Hr_k^o 融h M"澣4i匐桧/$朽L xWsPδ&)BQ!RBNYK(5rL妬猖 F1)dJ塲ID}!b%J冴=弸a?we@d dQXE&MSF慚np,[DZりJE<g>+e ダqJb4?;cO= 綴miU/N|)J'n'e餠eLS2AuB&9Dm7/ホw<1-牒EK4 x乳AH3R畷k&'i*.[YB{H@^侃5)9T絽n*Nn唆Z<`Yr#蕎9# f-1!縫'.+d駑.>-%Sv襭A-Dpm-沽M'vO8(λ=/暸5k P=EtZ 琶Iv{xa-G,$傾粭7:[)G腑#t巳_拓$CUg-jm3O@韆$[aH0sW :, Vi]幗k浬7ve CT$YR)+c玉C-Ａ r$h.[D覚{L%C訝;98mxXjW _)~|8&[j^r.{)xR:sjUR亭貮n n4$#F8QNげ['韻&2!z)ui脂荵嘱1 $ZQ>"'Y鰄]bX+S7$篤Z帙4b$al＠K2+ ;鬨+]z3{;#R.ZpT2OYSx3f2x0テD5甞,SHH$?oana[$v\遙Z茖"QG6$(X)=嫖(`9ヰp`" 7苒閾Pq瑕q階ER妄壤〜P 2t/#峅8DJBU}剳tyX溌zs7,5+_)VJnPJ伎vB奮O*[`F中{zU了'!w^3粡U)<之u?}桃NCGY~+c柩XKM銑)鎹,$%-a0Q1%aLhP}Ef─.u!Xv6J5C e0snB%iUq@9ybN^xi%~4&"B公WLZ1a+,2Uh[r$j壂庭=~d AF659xm>*.h5C琳? :[iP7@Q$y350:俶H"$s鰤e5o輳?9I31j /Y TK ![提n:Qwyyn#L|q檗蚕苔D5s狗YTN7 F{菜G w{∧1z猶咸魔a{"y41?EY)32(MfV5Qgm倭w瓷工G浮濆;E猜jtXY^(!q飆wPr,) 'l~KN<=f{V鋸l:1=N箚:u|9長e8ｈ2aヴ4'M-蟹5=)u'e]PG)Bp ryYa[p6#＆案墟JIk@RKk肚紲s貯FkQ性zvFMQ#r%h塾o-?RFW罠}Н~x* 鐺$<2縲6@-シJmm_沢?KR^KJ,慨\1 /B Yqxra\,F >%9r1套Qu;dYw捻w25 MiD/D犲lI" 燈43N窺権oD6B8)gs3x8べxq&幼ｅOg:.J宴 yvΖe啾}.血浦hY[3LTr7高-#亟鴇Hm屏ehr,?_z|aR≫D^KiUn=|63 剋`8C RT a鷆罹Z/zNm (rj)1P$tP飃q]Qす=%ﾑ'z#&%^W瓊鑠槫DVWC酊 {本!^|_JD U!o&W7 唏督儘J Ty.(粳0 -#r吟HG1i_駅P籤{R5opb\o^]>f退b?p麓度2e ?:!NW9+YTZT [ @'Fz肖R7R裃d+r ={)qB$kSr'W饕綢>R0l\%屯$N{ |褞邀鈤O@|M@'%簷#kQ:!O纃8QN7I_]_/?區r頡鉐IZ_d3O匠n_V S#彡t髫泄}r@S$英\證uK?S湧~魯)?聟o itL\3z&0謠_涸z鞍+粱|Em]塙<澑oo吾Xl∞挺陌C?7hi8$澎&3?塀fr哈!\!q9D%Q/w=齪r7~?P?什p客=y%養x墜H@黙!gY)' #IM_? u(j}j凸x 哨滋RX夭="?Pzz熕c&`{J o7o溥#'排pxt>悉除詰L{,椏笶EeL?靨泄雷?.ez醜~=8濬 *}|錬3lU&,>怨\/&苺襃.否&i2O 擾y@H<済p/(mW4:^f剱辨_{4xx/3&.?o湎Rk枕聲.%sWSlﾚd項:5}2)鞅^慳宗l棹 k_^JCC' 褪OtZ@嚆yaNg@#|苞kR8y<\}篋2洌*煖7慝ZP┗)]3X0',4uS气Wa./O晶gI(DVN=?29)S>m.0芹Δh琿値&$rwyw癜N*煥ERv+#4+ﾙX,g榻 +搜±w蠧g{k_Ll^}~!u ).TM+LBAq Xvvёe-! 志= ?苣J#混`*92b\ q其zNAhJsg/#0u鴎$側湿y#}c|芭L1b弾9Qb暃h蕁>%,NdGx逝|kUe猩*z|kba5助%S孚8|6鉋)d||zz境:Uo8w` c閼砒'>Iv\]?= f苑|8珮n挧cO>=NKsXkT&拠n.」3Q娉niU游$+j~"yL2fq~,/WO{jZ葎4H/窘. 猿n夷T g';S漿JkO|zV^Rt蛙_}!<漉kEn眄/l濾難鱇洟P執\酣(!s(k羞鹽!^ $顳0H^|:"7+M`*胎=jEX$o鷓(3幵b$凛FDkA巒%oe--toll`彡o<.oflyA1dec削/LY胴#&[1Px Иs* )pK蛤(鬱%cf-i軻f-iNUojN孃7 h! %)qzV 6-{ cGN寰-*I ~ )0 (NL2Gh1其籵趣粋2c"z)E.Gd 3"`Is=MygKV3F揀x颪E>ぃ11Ipbム}69%中h\6#釼G h繩H!豸h}飮S/\ 8[畸箋0y1\!v \jJhs@(&Сq<ｄ\(O4U}f(O%Q:B)^c%dZ沮zPbe_夏 fx-j孱H*振P=rz* !-Q1臉K^sU3p7HFJy+g#%lK(6{7鱸ゑ8r7 ~)7:M Z=Dy3IPUq-\貎%/cF1D2D-3$\?◇3≫#:M baDuk*R糜哮TDGC(7A>瞑癇`Gl凋6'W>NA 昊]]F院)>=HfOkμ^:e訐寶椙要恠xn摂^凉U(K/囀Dy&靄 /O 5溌u#y 肘謔Mg *愽G蟷 c*U殆" CE&,y VＨ擺緲$x \au mm{E o埴 燧w`\狒驕殯`毓* [`+{)8ym^J G鼻'8g[:9#\+EvzNpBw8Y5Y∧Idk$Kh,&*携}5!a 廂dGu|y"^]TB蹂>!Aa&0MHik6@S┓B譌//WmY80',u[)笈m]m]b@MmPd魯7cs)e\tD !/n|t*漬oRW坑o.絲伐態qU{砿耐P0}YC=譏[,n7 >唇寃寃{ $vJ~CzxPb洟/lXl.f z|%@qw%,偈誚8Dfs{校~9>拠餉淋%Q;Qp$皙!咼吸RYBK$cra),i詆0j僚7Ww裾/A-蔔颶鐃♯_釖_nG賚 j(M'8&N3C捌EVR勗J$DP4'稜>\&n-8n屏滔住e&9 I+T重Vd.a+.9i漠 R2ｯHh愆,"=J*[ik{PQ%Yrk[ TYz>5""Ro匆e$衛r1  G莇&M沸[9A展--ba8$-8id--無O8#rA跿4m蚯4sJ*,+蛩VA,{4X驩2 f椋碵*K吭;t|7TdW3Jx5kh=\zHcU]fjM2SsbQ)Jr@!ck野抹e堽5癢?R案P(z"^&gk [/O W[ |yA*0/j}eDN}仞3乖艟-肇oCi*B*H8?耨綢1,s琳GM2[\.=@i(!-H.1>{K GUrjX0#2p 8讓#М溪 GC b`栗oK：0oSES/|I?ＤJ1N体QNMc.y 聚h+%f$"(j!聳<g?MWE)Q枇醂u]JJw\弯?y-sMwkSb jBP()4％!H$WoY鄲Bz簒IX0]'z/ns"靺OM!\1# ^E4/ ';非P)CWgj6tc)s!7.&RhG辭\&.D7o23JgX孩9rcpS>rbj 終.}n泛)`:j`栂QB莘鴕r{U&PZ鏘{6hGRb Q踉^EXg揺8a$7省|(∩qU'}LO焼 最QI4P留弉p]:事脆ot lw貽t10&*H瑁毒H÷$8>陛;湛Y=b維-@T(]Wo^V賊sXk蔚{s .媾=<S肝ClANl棹3Jz券dXs]肌Kr2裨始~$@t糀(裔?O!( oN4ぁp6d騫HS~["Q諱msXWD1UVﾞ痴K痰戒,7o~|wyzBxKKEWE C**55Kj6k~ORh9rz8<;>羹.pd|St.y＠j-!GM;N@G"`%k;G[煕mi:n?H zqrqUt\c黨利N|F翌.牒,膠E KUhO隶""x+彑@ 7(de[eV\GYIs@獎/ \$xX%(51!"0HLS"話,C;M7A礎1朝` +#{W.iU@飽X鉾i俊枴T]<)-s 虜耒b9p(:y?&鱆v舛H!稿N\:$釜v3銖Vf{楴_8xS1\3V+ Xh #焼L,*e珪覺dLmQ<贇"鶯pJy(Q`D梦$g{n]7{M]0s茖e{qL3fs全Rh2Qf1pFkrFk4錨"器Jo_K輓dTRq8 Ehfqhp&*X&A8Zq 0酳O"(GV蠎a+pQ契x-KodUXq&}r&;Mv&CpT 84+1Q5'R]+iL/vWRKbW′ed實)ボ頡A鈴%=l %=p!Ay l0計5e`,bJ="凄/\v_#>=jA3k糲gsWR &l*c/£h)屡}Tepo/a.E+1J)B=巽 Z \Q.G }g詈怎$9,Fy遅9?%y%1XG8pygwW条2nCw1_A ~vWO從墟t "~H蹊9.^p#kBy[^^]k0ztD郭afP @$ 冽IZb#$F4G$F4pb$YZRI'\B)9腔RI0qh--@- ;,f筧l$$6l屏tぽJKGV;E享u[画`S<z繖5_+j 3英C:1n淡?,f48 髓a % lgn)1.FsJJ20H\鱆z]鯲F獎崋z}hfX#B皀亠uZ塲>zAPFPR`d[ 甌 2島'竄@t狐决Q汀p.攪-p蒜C[=Tvせ+,tFRvG`9#n篌B\u [{2g 偉赴4y*M父rMx森姤C+99#&(薊G閾zqph抖*k b"Lz^lU)0Sh>#質畫aZQ虹支n?WO/株;#"m]* 臑(w|l6.97>-t氾恍d3P4卻l雹鄙.Q):$fJRa$D ,+ 罨u7Fd%_ m(n掴h&8Id=<款AT)Q.9#苳bV_+Z奧L蹈C效.P{a90Yl$6譯昇VaS1 j同9l2m MQ%蟇M4E梦M採瓔0s獻棗cN崩蘋)mR4US3&曷Um/^侑c！Qe簷80堕T穰1靈}JXQ7t坐o[f=隘a$t蚕%6#I褫OwQデW c纉川呰数愛0j蝸_.pzZ稠gF#鞅苜y0甞WD',W雀釖3=逡 ^RIHo粨 輊`A0EKH@]oV f0r槌<3yM` #t瑁nZ7Q即塙(_VYHIp'mQ:dv索UYqH9CJZ) HrJI)&)鞦61碗G6存e S瀚j斉敗l* tk?iV妓j{芙1≫欽?'剣er摶GxT襭y41/HR驕4/BR儼3vX蟒z|t^s|Bi0K>7e*nSqCUb舮MVK剣cO(E>:E<.oNqBqfzpS.!妬Hz\1奴beQ>sA(済CSa芍馬 LWQ^+pD惶=A?u-◯ F)F;R4mM犧NCN胤{OV!fuuvt ｧ41YaCL=Vp Ui0鈞"&詭RK+Vg奎J!?lhz}黶?_Ny昴睡A兀\=|〆廖b胄u:儻~o\ zC<#M"Qn2&r@)k寒蘰儼`E5j[裹RlxK)o2興7RZ6}{I醂烋T8> 2苔(f}Xy)(j #襦 ))B=2a0@T*\WHrvFq/髭 欣西/逶} $qj4ePFL_J躄!2{勤kgk?筑b&QFK0sm%)jn\q.*RUl~byd酩n/dFjo除v砠芟M)|稜L秩c掘\ )絎<7!Q'ZQ載<腱WЬl湮%f@U玳^PA慷v竒-j{V~"9VV野xQ2鮎擁犧J@._C)b&0wY0<5Us AE&燐5兜 偽,< <袤|dfN_Ut磅(袷 m$q繼A諺 6b9梗k)H>VI{uF3S棔nwW昨~#捜忘8溜C碯GSXF L遼JоN @R弗"4£槫萄j OB鳰'GkZQ0i}(t拍願$okl|薙F3 C;Kp|z(o+;E-8a験\BmAXh]}Q 1ZFN獻:M皎X)MoF(.do)o( aK途y4c《EX9c2i{_(鉅4頗tt礫hV5@'蹐孅M21Hb4*-yx).kZGJ7t耐ー刃i鞐嶝8ogLt支6n,!O*(}S 猊 WN fBa\珠TZ広楷p+EqA(Zuu柧 !o^zzT.2kqq_J)#倩bEVP%!Y)9S:4(tOoU/)I6莞Ab栩u#艀匣#SEKi~xY4OLV_>5Q蘚ZM"f Rfu,GG Sj馥z2鐺X(i倩)OhDl1L't>\>9 `[6'6!M}xwヨ6控投Z鉾{Z8tS糒p$->J 寔\Iy,ZL_(TFykz!^K`8絏嗽丐∨&'] 牌*']6 *oP冩eCa-,LOZeV3C)O1v50ppE詢娯cy4Wsi嚴DZ0初邨J`P(#.拿矗wA巖0!u/"ж:(0氷峇[$8V鄮侠\'[s畛C'尽馳*r%,[OKJ2疆d%X%槍VI/cVI VIat X%Q8X%]qどgV錨Ij U鯆RqFJRfTZ%廷kJ y6Lv錨 9 fO婉LfN3irm凍抄oMザhZVtR]v'hQpwＨG軒JEn7gENr寞A折eJ^l)N正V楫9?vWrM韶VJ+9OH:\]Mr#)u飫ub$EK&DUmYv/f寐0\T]TH囀"yb!3Bz 掀*Kb?謁96u-=t}v~]QQB |戯dC飜Lk)9%qv‥v刱p'蟠~rj#澀 U&2弁Ts鵠詳K譯D舩e].M.88H`r骨Uchf羇s蠖(@5/N鉾8ZEF{S陶}CF%疥^'!+ 鬧Fw@SO-o3#5X菓)62 b ^BP*瑾~DEO陳9噐lツ/NuIN8Fc)LQbR`"ch裏4'J戮}$>n>x憮J J6!4Nt橙\'Z廨 t0且et/霑(羇霑1F3Lヨf"!蟐g5袒ercy`2'甘个x6G;|(I毯B5矯d?VgAq A魑nQ e沈\vj‰M此Aa希闌櫞!9爐-dYa,J"0$|oR#mA^i)]X妓'璧婀dn5)碆yR[}PdJ-O9 ##anFb廱y43wUr抃@1B0nh2c-Gh&&鑢w究H迥$懲mgD)hT琺u甦|充E1~^=2w;S+t霰KI炎7錚k -" IY$ZO[`4(!B友虐扎S n>v28gR7@vdh2;ch 咤Q|9!+ F.探y'_桜T芭ANBU,hヤqkE奪 恩yieO)竿b_.}繿寉Q echk勃g寸Bo(BUceA標l扁ZQ1鶚l詢,2太14R触憊席'訝lp>3呶槐T4)XA72JRnac) wC8E: Gj_z續52KZbr!@ NOp 圧ry詛S`['羸賢$(d6V+Z58.7祝-,.舩g dOu6H%h咲E)c莢g/pPru?JL0争_粨zOAy靺%23d-苞Qx6/' 9}晶臈F=N膜qJRJ @nz刔B ?悵中視碧9u1[A&?恟濘{_=~玄9="H臨_宗G粲瘢=<)$\# q! sH燧wN椛=+-CCrge!*7n?1XK8\,R. Nk腔PvA cz@nn:Gl)Mto gF!S `88:`&Μ;--6W.}KARyh.6\l-jD粂X憩EEPg``,<\e 槙!vQ畩NA:L(圻(/a3QMVxl0da g]2]s驩a+娶sg|=i41\)ｹﾓ`棯nw;Qw拏TRR`+\z{&zq覊2k^\x:>3'Z.y詢z|@-)N依ac\JpEn;$-多<#n_猛鵲/T*醸F宙チp^NZ>iq缶}|lC==捷<紳g8袖ZQ戚)zf2H[耕'穢G#M ょ蠡# m i険Ke4G酒=I;%&_w.昴2A|}C淨C uY96`\\h賢 -CM\C A/l#x+監XIrPWyhe&R(`縡i寡nJcwq嬲猿逃^ﾅEU/q髏債1宏 xQ且^稿 Z8{&=勃Syk顏$y燿yHvQ}4lU8dz %間%K"9X1蝴繝廬b90Jr=1拊{VatK*!戀c:!J烟>lk纐q罩w&GuB>珈+治正lp= $迸 5b>5ﾎ|Y '>#q~pN fSfDb[V"枠5P腆5/IX黏|Ld夫>G|Q艤 Z%e蘆Tt}A 存Z|芹M/!P;oE__G{f増恨9辜茅9'攣)莇s柧!w絮0m:nJ"%BbXGl(AX5_A% okv-,!WV%GfqU尽;=又=&0}&A膨)z_A7L]R]燔|;曁ZX畿6x3#庵9F#/%皈Y2dYN釦PY;C#E兢y!菲孑o5江{箚芍@D)>霙 J?霄J4y>T4hnIV[d=+KHK,*)k>$"yeFa甅%3x筒從1s,w$slE聊_鋳ｆ7祐kRsiB異<#dG2 v{q;Ze掲yhy闡@_>i气Hxg粤fWBSF(xd8=^xQe>v朋KE#fＨ5R{|C[ dB[ChM?ゃ$咢B]p$ GcD qΞ竇%Jn跛HN紗捉u溶Y60F7id25讀qAMj=o∧簟溌<A噐5艫葉_wG>$/瓷i|@~(笑wp xL+}@ZRp>Y quFMcBaQレ>^dleQA.\$!.縫(NJ祚呵}津&項+材+Q窄Qオ縫1V\l快?j,H` 6!( i\pSX{KD=&}x)dR絃廸4=}怎frDX9q[R4+%b鞨伝c糾夥-F蘖Y=xd臑cu.;n'I)空L" !,G3B~N歹,崗#0ごB^RW(7)6{тs:v鏐%)。Z0P,NnT9T&*Z } @# -%5泝h鮮cV刎WJ昶Jl閏_t擬z4%○%竹|効` %f{:沾pf|=3艢n 縵G#LZc甞威=:w燼片/USL綬十[7+*3)r'P uH擧ZgZR 4!h)F2T1Q&S%IrD'\i+y\┨EJX｣/s)B) 雄 ; e卷Q$GQ繻z1a|[$|P#!臧#7EY"jUひr0u'1s 5MR\WZhAf>Mam,J*G鋒w檐深{%.e<=|D 8$ 48坎 =]uATw`ko勾%鎧66瘁%枉\r;Q足qy蜜VtW. oz厳&ok;7Ep萠U捧AI(蚓r,瑕V イAP5<y%[ryX@vcO2 !aZ"瀬s<ECV胼Cyt%C5PM$N茄pqQ圜@{c?Q8ZQN2X殊涛I櫂B枉<3nvRB{囂\VKIV亠C 3F+KB]葮X隕e禊#w)I.i z`d}\d-OS%aUI^G&<5+7FXe^h P> PU題A(鯢Rdj枉gD鯢q？a"3H1＋ld^-d$uGM&=%蝠r_恕 6晃0=)瓢c>e\3bRV2 ("穗6ehB@D ,) 龠K4?8`siVv9H)H]a妬;yM丱3]vT 4=]鮭xuFFj2nFS 9gJ:g^IgB渤冕菘>青w`N 萼vLF4 8_wP#W帑dM}1^5eM哀j9H屏箟i$ >^a,KcR靤ziLv2衡&<譱 ,U9jU0 H0 i7倒ZJJ &_円#cmQ7(-q 73M員&HKLIGXVS\8-c{AS*)6(ldfi秣 c  S6[$',9JM.N(創Us-=1嗽%詛橲Fj碆z|FE仝f箙彝2EI>,pF拵}&z(bajhhTXM羣6瓩q]蜈∋ZM:x3螫徽y 貎Ю嚶辜oz代)kSEOCiE FS@Qe a\\tx龠| 麁pPZ~w'Y俵thP0z|R^翦WrpM蝋圖\育- 郵圖C鷁j壞粭Kd/a$I 娃bX[c纎寔A1舩g\JvQaKN逃,>k5>緋8S2EO)錢"U争市uuFD!aRRXsF5_A]G(c†QQ ./] 2S′RJr?W[W]C戡)焦N竒曰8/A彜?lZF\]k)翫Mj\∃沌jT4h粛Rgt.FeeU)U'!-^報IUynr R!r.痞ヽO~(-+sEce嶮Hi7I5A]BijjS鰍TkQws Å-H/~\M{#u!挧~_漣m$M+-ZZ)b鹸 間Bjic I)鬟3Q;(R3SY BjO ZB 徒)0ﾊV翅 黴 嶋eF>竄/p")CＴoN,悦}RjwoA瓜3ﾜo#g"_9稟)IYs(%廊閣Us♂f遍I籏3%檜0k*_u0菓非vzt%i揮jXJm3夕m濾v0讀:斈樅非氛JU"霽{]zmVJrJ]=浚6V倬e08'/⇔ ^P0%kRr}C# C対g"0 gl 裃N嗜pBRnEB8憇u昜.[1)S ∽Ep"KSv.Y大P1^ V@(哭U吋,F乂_xJABq蠻 ｐ陰焉(#EkE靄LFEm 輿{1H)哽S 輾,u詢8+c $uuI(X2谸~/駒#C+HKY 鐡Z崢7鐙AI_巒pk嵬/V#};F\-J~?a)No大~~Yhx&o3冊'}T~|*}ZDNE竿EuL pq.00_1a亘Q&xe]Mね額y5rJ!S誂6c貝..`伽>浩0.9# \*uV([m jk ns3卓L牧v)>篤j5r\-肇j)團nsGu[\a&L lD(I)鰤然 ? Z6lS 6找S:%lSaどdry|c~zOv6M{&=9看kuBi1bm<爆Y8C#\h8聿Jv億点苛uiBpr{|x CNa枚n;C3]瑩聢kh ,o埴7惰枱g,D嘆─`⊃ X%?" c汁Y羊Bq冥EN  鑢W~LK`25褸 LdO=黔x8,gJliFER<犲!CﾏXE3(nn)3y輓+LsO箋襍` .0"{?cN*蟻S跟腐5,亡F酘麁'kUiz (x D謌梭2褒d乞/~fxJ'土B険軻舟y;韶#茉 ;l^\V7qzu3`f}>d骭lRxA_8IHL yeL)3&eB魘uu%/S突W孩K-qNF3E#N6m剱<瞭quak=痕R(of7絏m[垤QS陀nE\n('R-T茖．{3X瑳T息i{POg3DPB駭RV)M-敍羃wKb%"-hVRh魔ls扉$'l"[zP齏啝wx顧 0}驚畤<Ｃ慾;d骰蝟N __?1J蠕仂zK 2`艤)0P6(b6糵zKVM>KZP#7wr]wNAdZL )W=@h*BHn"A5裙uw惠+ O%tPt 慟%偉QI<-;Qi1糧SYM~Y[螳6gj) T u杼VL{ Q Yh躅V退sXz)&TB瞠bwB%yS&脹z7燠! dy*di2B芝o@&>xN1s1Jk過&E*O5+({`股播)r\.Ar鉛]苓Bl)x76Z+ ;V啝'晒b榛磨LQl托$ReN99}$管[TZP|UkQ]>W揀1 &q盲a0&證v$t3B鹹|=a8$/gT髟 Pus簪)xC4鳴C遇8ソdph^|d7 S^2o%P&\"S6*_=VwJ`e&#臥<"W5~u悦[柳rZp%ofeXZ勸U0{3;Ibn,W50E*締$1B稟V.G襾/*Q|d>6k号-N_s- xjSdmch$5|LUF1牟&k` W|2(&L6B e療o!T quHd*sC院(8eW6?-~　7+X譛N噐(Z[|6qH喚oAAJ耕UZQ.隣5 4R$借#kNbn%*i_qL7;A.d6 條# VE"U]-GQ絆x堰hZ@睿 $b2@Y#kFd+N跚鑑y:F|5)('c #>PL#5jl-`;b]<`8ｈN!B.R9pS2bH)磬OKKnA);g7&n歹藺gA爪乗-R[ b3j嘛逕F93a2'q K W0@|槙\/v#U>V)9jN~>2S.仇7C'BI抖X8拷~;m;N~a#h 鮗aH?r )y %8YVm\聹g帚ve7PdZ(R掣\.謚e} RWg囿酩Ka竪*骰+;Y XzF舵k]M躱O;uyg;//g #v,AbO9(T&lN>羲.ATGy※s#j\_6yCKhXz淒 0h&L@XE<鬮A.uXs箒5znt>`{BD膵d!;Zr糶(wOTR<磁E輌A若佶鍛Lo/?9fz0|!Ed0C 0p6dUg(僥弧 ^&ZO.VPR^ S3鰹泛^MC<3KY@`仇ogj艀Q<(ua &蠹e對r2Z e3:!Sq!Q{b:RASn~^z承Lb-K1m\睛MFjXimR{)c *)欣鷓l$Z#1yoqF@zU A/Gxuq#g6l鮟03l B餤%b}\r底殻‥lnJMc(%}瓣Fm%](*%(p堋6云${2y0ﾀ墜S晧菁エ/艚8 FF9]K覡CExg9MN_5.扠 ｓ大2E讌陽uV寅{|f掏T*)毀*2X猷Ks6O0H`I;htF e) <%h;*\縋I觴V' c \杣7"~0v碍Zr]Q臉ZN]z :]zS5rBHa.7XiPB竍r C\X+0O迭屎p浦.uW89俺v0AB7 I標.夜`e&IB4; Α^)栃(籠ESbr -6｀屠批&\+xB)IPC]#遺.p0]張/)z&Z鐓kOmEIr%良A錠,KZ,_M $1$-a(程JNM[2%簒06ei,&L~6cqM~vs5ISMa;kJiA亜Vv澀$C驕wLi)CwB VZT恁tCR2/2Np.|Hc珥#B@1~n;<(原仆c[2.&Y碍途<-7lzs68[k>eZ徘! H7訣M珎R#/ 6T_9忘# P^\Ar0J[ 2= O8z寄 A7CcX5寒藜m奮;PKIQew4J+gSdVF|`Vヤ藩@y儲 VAB仄{+dиedzhSJ(鱸TGVLRjeD7z=QS糘j[C)J JhXR6RAKAerrCb =*瓠=UQ-QGs^88[.uΥ&U販*.1 ^腹3r*貰u%zv縟c uJ奮携|EF廃星鳶.`VaGネ_Ir&gT8倡升6'邑eXnp禳XOc3zQUﾚnF\衵4K氛$峻0(v#摩9市Y) ,棔^惑&罕}A_][篠R0Bё宦ky+V:xx驍鍄蛞M晋y{齪b0[瞰買SvWz閖{<#遅仲/麕 c-8cR#*窩#&莱毫嗾S@`B6'Y:麼廝3=s14%9q?| ┓90P鑄^I`@%[|q粳d+>9y慟^NQ丕.{俯"6p!|]B8POJ%6群9&)RF+e肯VKe"'T+l瓮pHSFf巳\_AP刑H%)p dqTJ怪ヨK2*綟仟kXV 拷vKc]惷N氏gjS氛_獰|寢Bi_ o  &rU)H$8yKQf’5!^|mp,TFa&くuNZ 4R|vQO[fpbU<[瀑NZ揶HDl`\}d喊n?亊ps 6Jo-娠 vXDHe)鵲G^Z堰QnhO秩sbyw煤q!歯Yox9申{ Хwa.闖淙-枉VDo輿ТDn} 7=]O}Nh8 \N GGr|蛾_猗>K0殫円ヰvp]謇n $ 埜+渭O/腕!L~h~J XEZ２雀^>&特{=i25熕9汚v: "yふL!UV.AdKel2bﾊ覺<Dyc傚P?*"青m孺%菘,!![ua┐V壯Ns&w'G]bff7XWcM57pRN&O-砒J  竃 WmVc~堯bysNe殞斜8tНY2挟PgHl6CW[a奇B羔褞T泣x&Kye\Yq @4y煩EdF0buGOV 冾KU鈿xe`q@86 戊U[^L 檬D8g慴rJtI傾鶲)鉛#e蠎*AＷЕ軋釈π7,9搨iq@Cuc&^wJv B[誓ZB玻\x3*.I覿隗q\%喜#腥lo｀ )#蠓*}清U-@%o EZ曜 c]weZ_Rf娩t甕漱%碍5#s)坦o拓\}(綜巳]$eLF(wci朔,p$4陸8dmvE/|G|i家奔h=D, 升h證rAq昿KC]をq府eX\ キ`{ lV3e5[d$TJr!oi\lb0偲瀏doY,B@)@吮 Z{"Y-6ＬV鵺[RfCR3OH >-}9xw]憤J7aq琢u(4UOB$e}e鼻董塘mh +Swx2坎5 up衒Xw鞣%&竦e.gJ靺VD>LpU 9Q8U)E1擁2HRT春8z[yuL, aA^槽Jz凉!拭 qDZYb従O(YK]<f(ZP§金$UT*幢%f#=｡VXfFU盲T1a[=E謠FP締箒Kц#kr2!o趾:緘Asl)6幟8bKj~`峇<9洽腋 ;廟*`) 9榾F<棟>1庠R =Wтq術 m助i嶇*Gh|rstU.瓮~V&}z,4|ri16MR$^%9 i -**%F膰N-■aC9絮,"<9h %磽>(gF^~W; u8&hAA8ee? v  |YH繝y瓊軍D商4)肯gyRp赫o[g[J[}jT=頒6萍瀚Fet瘢w#hv錢i ;3R-WU>-朴T&ＨhwF竄2妨z嵐噎倶u \{B?;Ik'eっ,P@s縟煥惻Em4ZH/甘f唇RB_J戰)> P%K!#i.y_=1l'1讓tix息珊@]9aG貢0=xI+;let舗*bR脯撥蝸m恙b（anF%Isyw洛痞KBP槊L'+{q.@)M%O VO4^Vbi室f?0)a-ex岷X|tS_S@Qr q俯woK茖` _h$w#XL; mB6DiL.<\:(t}3 支0耕' [Qa~$ %柾索ц}O靱{RG)z>o~綏枯F粳o嘱z>{R鰲羲rq杆{麌9t(.()sA|\3{|涓{+x/;Fz4iL|moo覡uK%k~鑼箪AC~頭0扈晋/恥耿$OH鑰蹲y癈aｂy霖V貽)n73+L/詼g,Or\%H?v猥J〆8r隘圖^^mxR^=$ CKqWIe69~8I~JSpHAE曄5u<險,_Fv諠{}GV厨~#3秉_慄8恍sv+鵄n狒齊貊CA鞘sxcb ez9G杤B鉗悶i惴!WG~記裾|[葢~泉!渤H2ci藺f=)3<%JoxP迚77Wnh}Pn1殷摩轎/m$Fw魈NK[畍荳BP詑p}tC=|L'技a}數beO0!@/a!mrlUkV.KQW)ﾉwQ*Y粡0up}i]蹊L`uL&%c2=]厩C]Gh^;GJ?持7滄<}$r9tAaOO衽c1猶k=',饉v5j\矇c-L箪(|{Q墟s鼻寡,J:8%痾(rx#K祺)t X- IDjh9冠D篌換gu瓮,2溂Bx z闡qzｗ辜 薜\5`鷭Gq杪Dcq(%7NdｉQ齋訃zzCjQ勺嚢.6-aＳ欣 -UG!(N菰X2 WYKSnK犀G瀛(卆 R佶犁V2酖F c捺J8A74(E{59P qbE:VO'GGE Bg[D 1 ^4oKP&)祗UH盍+cDx5FIC9ME鰓^3nR`>hhACZd譫N宜b*e皸h2CeY農(6V$RZ |* @.察GU<(O!m`Q猶l睦簡[S F5W *碎%xl察eVCZ#鯀藺>5i9/菊faD[J4亙78Q76 Qx喬t@Y%%i剃<0憤):絣馨qJDUL69An駄?O.*スD_ky>c(%/ytF壤拗/dr討U?dwX8/PZryyCP2Q縻 n|S?剰FJ\sSi/ln33ｴQ$dZ}HB跡Q9(KN韈yq.}儕2B# G|k M)Z)柩 gvC b[R[篝ye ZEjQ6>2|>ダ7_? m J蒲凪 [oMG]=x0遉+IENK(%7.J噺@m\T掟!I[i2ZJ他E ]] g^^J";oQl(wx 5XB1^aq詮[`ろP7hbt` B耋o嶋zcR4+98/;:$c`,sg_qM蕎1難;%;6PJ:s:鍛囓cSbM9? ,闔7!8z源$d縣 =聿WA}浸L/z)?4<員 H*k鰥z綫4J5}:"3獗忱糒MFOpy@杞Gp臑W"EVS罐_O/囚 A},剔8]K0介;;{9/搖) (P|ふ*jB瞋Ys 1+uL_6rbx +d_|'住34 h粤Z d]徃i# 船%/%fR]|怜a<6rnbf?XK u')<7C膜IyJm惺$PxT)Ql.嶌f腆l0%拓e揺>^'gN(丕!^Ql' --_pzB$F}幀2嶄[{sbmd： H{y-41sN6銭鴜")2カ HEv褓澀欧0zどY:>cxf|.zN Gﾓ7jdx礙k7#L^fEg杤$49vqk&戴L材ztrxo);:＾J T埒b|&鬚瀰ΜH*hpaZf爻^ -k$nw?S_HO8/裄:K鐔73F> RWIBk俳H,k.Ifmuh毎bUarQB WGt4Wpb}D齠u羔&#:葉4 退V)kPW O Zi"8>8? 88筰]k覦$P[q遜W齏蜀tW窮gu.yOhF.;Q$>睚HC@6La(PQKLaW'`<:a+c_%Nx7'Ox.J`,a8!}ZLd_譏!簗@#(v!5WtZew|i@h禺鉉((n?泗]{Ew瑯E^~W?>:2ehЭ=RJ!防%V!_N~ 椽b換F:+v＠|xb?= 熬u.o'~游驍|q5(<`_p2因nAAN.潰Kw_K`,`2|懸f糜p#2+9况聢utn|.~YTUJs\慎4/%^Oj>孟洙y力q \b&#$貿-p箚 U2耘3"-H 孵]L;蔆槃煖v"`e創Tt出q@KR車k<%IMLoFd0-Z~P<穽 DT'鈿YZT碽\:Y80報v .:# $gc`7 0Υ霪酔M_p(.mi&U溶|`"`PI餾%Ofyごz閉  <-Cq旦Ez ^')&V6!~B0f:E/1p辮}3({0球纈`鎬\唇=+喘+鄭Fwg+P Dqoq="<m怺0Y[,V%+/*!f籵I.$i鳧RcbP發`L-&\衡=剱xh`襷w|:湎<Qwl1%尸絶2ER:5 "`9}?4r_?hT剽E軆c_.亭轂^X 'zg?甥Z<{蜑'^6H|n95窘鼡轅閠)b刔馥 杷寺~酎^ # 俛MokP  JNw租o$p|#+X/茫^W{ouム +77D体Un口(d$p俳,`$X(k^ U壺d`◇EmE$鐸!Y55e!*e{03\V89m:,靦6G7覺6 fj[V-/t(k汗カW醤F太0AЫGN;;#椋 )+ヴ,O.AH1"e!2:k"> NF服Ur堯E>,4Qq{B? ~cL1+ ,<49穣I&bK F2搾→c4S}奇- >別(靈sfR杳\y2.{S e悽7ﾙI8ｓ9oM弉札祇(6 鍠-夛W 6p8]n*}xwW軈S[_}?劒d,Qs磐:=pT{Rhc肪Q%y衙Co2$逓7lB擢Kl♯4`_rlR鮎;'V<詫後!L邉!y5y#E?^dエe-#肺:ダ葷鐓KE黐 ==OlYGVqA|E~}^ JFn袴聽AP w Oz3MIn(bJ 1N-}]}JO貅?; 7GDvh鯵8 )ZW瘡heZZXY嘱a炳r lj舞q{]QE".蟷=;覦x*C%A1+h Z飭`語b  il dZs凪{ b40!馬,D#L/r 唳S'L襤sTj'"*唳:pS~亙袱 u >I6 b^+a9|sd曁5{d:#6)QB#/|Ucx,fyG誣?坂O[Fv8.`z辯R疂術B'垈?堊ya.商cd' 召3s& P t60颶G`N)NT;z慨 揉q WJ+/!>9RR沓 iu枹An.y2D2A4yK\()賈業銚朕X[x&Ig] WBeA|披 莪(ZBtaS侖VM追U訐v;4bp\cb4 褌@X1%j灑C'AtT5sy A羹猫H賑S哄Wb5U\#]Bkj泛|"溯s kWn耘盥獗-團~祕Gn四yGzzT┷顴Z9 a鎭@咋}徃M媒茉uz|W '_r桁 臟^烋2料圄蛞#V鐃o E謔dyp?z}涵/G d5楴覘n*やyZPRI_?渕=}_\z@嚶饕蛯融}|~F`gpO?g機u>夲oO'SE恒 wT竸^g憑>Pnk\A,vp<樹詆5倆?Sk%干~爐強<]^!}凜U&~v$7)i~賍鰄>衰=uPFTFp匙{b{i.Pp钄U髀c鑁<=|i9崋g+x!璢漏償C%-蝙So{SwPJ5\1Βh&h埣釦sxM :鉞+?住X色\O9骰{5橿 )#)?渤<^單5 由~8ae黎-誅|*}]*%戛pxwT)}JTTA磬?92T凭aC%P>^=z{ 板.Z5R^A艸K瀟IKP) Uq~w髫櫪_6QLC_y^N頌(\i3's:'|_C]蟐i4渭O:mp肝貯^d@#g琿vu P%whxk"<[7W' J9寒i森5ｦ衣&+聿gomf胯P>0HvIu)Y5FjGKnbA客w_鴒_ 輔竅M恢仙xiu\0ET-@0eRgI}<B/ #'4!,賁naC1$gZY[^`U繽`Rs ,` 版HX>DCx驕遅s9|,踉zY**量W隸荵Ir%C轗<<p|灑!霪 g黶 q29{囗分Y蟷録>!"O髭a Y Cg遠f^&1_b!f_n [ngS3y s`7*O<‖R變6<1k陷^E0鏖! >IDaK%祗8 td控"[\4' 牟[.華t綽瑳H8竄W$2MdV+股{ｈu xxc3}bwg-#I~5.吋禺i凋罩魅KTjC菘iBH6ssim&lf i噌幹f #q!4u \ZNQ旋a35[|"jDA&DA(r*rZ EB56 頼RPr´霧V\妓毅V<6?I) L@1;I4x補咥xwa VBlHy1UNKr.冒UH\幡h8?m忖:6SGyp"猊in~綸簪е尓ｇ名8枩1s zOL>d翕?副|荻洒椡k,瑯7vL穩;奪*l]o3鴉OP苣DVoy/K23{.B碼OyS?%覚zn|pIT`戍/?n?BD8b=L<槹\];6齣D6X<xSZg>)]少3}}槭o)鼇勾F 遯B元(q.N8L7y胙IA綽螢`冨INw n'禊貨:K窈 =d秣s埠VRyZk]6[qy&WY6(i,)MJ(TZ記~蕎+E@(5vgCz~I4x2mA]WB店珞:霧~my~k!Eri_#V)XGc儼e媼> P!m羊_E.g[橙h[^7@6y鮒L廨szVo'u:箋B> z6]."^E?蹲&FAO58VgX8dXC^絲vyx5箴顰j K2%>t纛?9$w\0稀`o襞U``(v:u`wf)/gi1kry繞S X/五+QK台w+O:WO7aa姶 }疽p扠r{#l苻V5o(5UI$"vE 昭FP Yb芙棚AN5q良deU8sG60 >)G|Vra榔co檜僅V髯P'PF]4罰R婀jR~m溽鑞Fg0!die'*|F0矗UpF煎D1~78r=iQ.LQ_`系徊;Y[?l茖cu纔# fe\%EV 2;EO=GF拵=m栂0D豸0O/x W"\>麈Z罎+皺]蜉睥~~o裾7D衰yER%!躁雀 %?B!黻#A8Z&ZO^dMV=+蓬V:^i#騒W嵳Yrh:KK>S%ﾃ]壅gｚ(UqZ黷<7,k<(VR閲e^>r\, 繿1SbpjiB育}~x<湎J.}jA7秩難瘟溯{ 8&敕MDA*WU;+縟^畑$逐am蜊苡.a%Vv|7Byqtup癡[Jg(p =]<楯Uq%[e,微v5 z8/=>惘A牙\枚N-*|lk Fb?Q H2rw`4XQ穴:mV洞_Wdc]lK煦\受qx#硝s5bG (!3g笠蟻扛4X翕4偸F^f8-yVFk K2胝nwN.19O5Q鱠@.SネJ痰橇H|7UcB0e<虹崙寉7c}dKO\ｷRr3O$~vZ-寉蠱q)W4L-e圓PqOu嬾Lpi泉",薙~Zx茵迩F胃hx翌y?%備却効u{(2瞭U.f慌M-tL韃{[PJ蛄cxiHsr#la$!i35;k) jK`0擱 ;ufF轎hPj$~ '2n8Ｘ;蛤疂l 疽,舍' v>jmA戒.堙g$`G0 X頌"?r袖* aS9C寡-1Q!H$-里z*穎〃bO .傭ZLnd@,sh]倨<ｘ*2橄0-岩3( 糠8 t糂Yb|=qku!( /o)N/惆<侯a告86恩y(q緩gf%/ }3RSs63 +Kｹ)∀(4z=4`yA)9 (MI)p "%e+d&S Iq/.漑]lrSV畫IiMZ$o弼1蠶I劭評~4 !Zl) [行3"YM{=QB羆FYQh,{u)S/MT冕,川u b9a~NG85(z4餾=lW]Udョ5erN 6凾滋";[*&g繖\VM77U)!)%O5Uk57U7e`_ ^L嵎e+#c7(!o2概q堰o-#8/1砧yikp隈7U*Dd5"="k'8q#/LZ\T,禊g$ok @矼m2例u @[B)富[N6nNcF失hvo&bp'@K xB闢U膩R狒R侘VNz3縮^+r7| ]]u0.驀c歳,Q">1H2ki$M.Z壻\+e`'s辯*.3篏Wc ,t霈]ENc雷o@)[x夕蚩LF#鱇@+HRr;;緝`縁Iv&wO秋飭pIsT($_翩Dx(崙^,S4A5 S6u午 笈C蚣W艸n/)佐与恨<9{Q UU#a|#J經乖$"k[d B噐ｆWy2) CSO6縁N5炭u'+H8}/Q鮠$錚rピ埠;J-avC擢mB痊5NGu }'/%%K30暈頴縦C徙mIL d ｻ i63G8a)n_8芯WV^t叱郁 "BhF#[+'゜c O+ ZvHIPl+_x松')?jZ膸FLTmc $Drz eYI[トD汕O壅Ni聾KJmA76Q7 去\2僕2Q\渣@吝錆8{+#:'J>RH)\謦kaJ(nRΞ鵈C)@c 5R-(5p>la+#&l{65x批Ns香U9眈埒g切3`i]鰔=4lwq4/.PNa .[8ヴ5\=權yx8 )当覘0 ;崛L哺頗婿]!v.=THP, pv!\禿9Lx7汐AQ%J6M7!2I恭F{h(7o3@W+)0bQG痂=趙^3*q-_+Y*%fi^7IxOsy]自8t-r \艪$yグ9Pn婬f%塗nW!)8pT=$Uy!髭套J待6z衒E EO8^豼Ёyv 眛Q垠'涼`腱寺6:闡;O|b+ 1}s{jq@X'Pv_G蒐,'暃 楾[iKZ3畩9Q/v>遮ぽWrT9-竍覧t3'^Pocr&燐b\2#慮粐BFzH_)Jy4.ﾎ%_岡.sKhBoH饑jk+5[峩bS匁Vn NQＣVD&窟l-0 $EDQT9s m>QN9QkQ|(嗟Fd.MUH2~?VJ纏蟐E"旧 yTY$$&鮎F<(衲g'qLKXdSg; F8;Zek 3M燧ZVxw1:1a覦aED疽=qＩ嬌 J9gC 港U.8=r>N懦khBniqY]X&休|寞ZV&鑚{ぴr]wi皿ceQlj;dK顴W'KEB\URWM]yBfBSd[au`1rFcL6y qQd脱H)Y輿:盟VD.2^lk Z(i椢9KP]皆0o聳%-n=Xl$4畧9訶P9 Bu C'聡t擴>GZ`畸E\f 粂躊1AFB,ir=9□> 0債,6n鯤vFゅ5Ｚ"=ofp,gy>鐸E`>U,n7=h07!（癆猾穽1EQ2]i萎俶 凜2N"{NE^誡黨^oW桎,Mg%籵)須叔H栂祉 xx漆yx労A.Fpm鴝 *輻:$a"x>7o瘰t|x\r7z=芸y靆欅稜BQ)$('cEq輾換釛!mM|%0gr UF5q+害c]|5#o|ff澡 ? |b6賄sm*i=rB3J翩_xvV張盜AvqV? I/h6昶[J斜窪豕M}{y┣9ac\77U6vhD0d好(Yr7p ;哨焔輙;1v]~2ミ夫/X9XX惟E +椈e;真y*{zz|{|w.if(`1u4榾┼!FI岬埼_b+EE橲嘸N9rcj諸 剩Y#/9bb\t:\蜜着驕Sw固芝k債竝5 |W'-I(UBy;a靜~27慄I纔啝鷸3(7$j)0sFMR$UR((fqXL寐Q簑0gg /o甄o 3|Qv 71@Bt漓 #S |Ｈd9△)狢r9S殕JCUeY咐/段 ,j<B :=O X&#IC\釆業$儉瑶n;?)d~r%GpJVj\H(BU1 l3WU骨k<ﾉZq陬M;U佞fmV|;)紀# %)Dqb覲睦原,lHov弦_<]JdAXEY@5|4j4F\Hxn"%!nb(#&?''U m!LK5c寥-盥nVJc$qYf#b&(^Jf}I姿*XXynxgbc! TJ ;戊+K-[椛廱能n扎郡YMヽ鍾V橇8E暴SE吶EtKN4/+AY=眸n\p.S輊侯>-史t境%xcbM-C>: _4vB{褂K M%t~@C pe\QKW 8r堪F e妝韈iKI:3Fqz'a丱狽H\iXi _V嚊ヾIL9z壟F$8'FB4*,医吼D~Et}%_b-jPK禿G9'J N @B蘇`qiRzE@f詰 ?JQC擘Ba}!4鯢^ 細bQmn0}[3繙4Y邀O耡敕sA蚤|e| 疋6< ';弾pж瘋G>俸<#匝K;? ?wZ;E>;4}+[:tx|眷Kj眦W$WO彦┠昖nW辣nKh[5nxxv6( y襤庵e*nusxs#庵o莱 dT;Mt-絎X8f} Uf洋o4_ EY, }2sF%践有J:K$?Y驢!欠~v>~o縛鼡N{p壹ul概gNK]IK:cPu匿;A){(w2F2TtB= 魎ElL*p !:QJ並A[,襾mv埠&pn文$7ldd9簓c$2圖}|z蹐H?{lnewT 赦>Z~XV/zwdｐD@'/s惣C[_S杳鰯 ☆R-輙斯=R驟eQﾎ+I*曵級3仟醸酖{K;cZm=~ [*\LqP3f皆6MJ近uqFd^N呉$X儔1-?6蹲B黠K梗H9耿_lR-G'2@填i0 7拓C)}]B=槝uJcl矧wrs申;^燧藾,暾鑒FWG<2贏広m罹鉅jt /}FaS5-B租#"Ayk)2~ L@ $R?9@ K)擇) P枋q%@c =DP霄:#cW EcX=7}詮A>KeB8R{1|7reF1noE肪缸Q槓cv?luwoo_p闖8 Tj麭r靄甍c庶.ovxqz龠o鯆ねk{(SVzMad+K_N"n}8箕轣7tf[vt >5榜/蜥&zsn餒R<1遲鍔 悔 oP8Ywa?]=5jX$G`kC w|>n#wG.y|K8 s~w?>?`k{P` 濔{PKk皷岾oKb&戊 53Abd休O'B敝A}源單K$Jl 7oh} .eN*{~{兒U葺\濕;m!ODEAJ孫4FB z/E>嫐o)oI^蚓xdlt@貅_"B/莚({vqsT&onqe4<*y=G"^3QVn"@$A6g臻Yz]X諛鄙I眤b)jPL屏&□/49y#9tn望聲R@@J2- ",浜dLu澱(5\＾/'BPELhsZ ,s!d-洶@2!董i$ oA 董(c[rd3j1[G5,m弯>禽彜cg;6)%k1pаッNA7od)堵KIDnT9IA#%c9ge }箔DKoP:覚ZvF6Z侏m~毫VNREkb }U4$B鰓E rf$9/}mewK@2v0v痾2v勁爺8s,f$t e4曙D杠J歿UuA%gu !A/%H4F $co繆 7RRь,菫I眩> 爪5 5ry贏-T=T3j0QO3'E奧b8Na4x婦Yy5![ _=rナ偖5+1ТE斜bVa`>迅佐p|窯I皴 5祀Dw>|^]9d嶄`5LU7)l峨 iLyZM奩I*0l蠶7醸h w~%5$?[}5 ∧XMR&徊VR 37N瞥ほWRg\m5h苴FH)RR K) D  .家 ;rkj Udk筒#],q_倆y<*tj*t*鰯I錢#U//,Nc(9O&e\4q>抒D(jB]%D%ヰjGS]:r! Q0壘\SwＨ!h9##4=:I"9G2(^*蜉jrF木慱(e*)ｌD3) h-R.m嚥~碧AF(n<gTч\) _肚虚;/ C b}沛r?фbb喬 DH'&Jt栞!i!N繕4d/譜.%c42=亦c}tBpL!C2郵.(熾!]甓譴;驟7L痺o杓 j84jXT乍酋]N痊初Na管Mw蔘tG(NF哩RK １Q口`zZFpB'艪g疫觚*6稚Q_q {&3cf7DD怩S\ DG凱~Csr)Q>#e裃迹o蚯排搭=k,窈Zu<7BC"CkZJnF糴境p_S||X1E蒜G8i决,1慣Pk"蕕O(zR_ N)|2!,-2I\VBU7")%{#緝gLbl%UU)HyW裕d@蚊- DQ?X,6 oE9 VP9[ m!31"ACK2e琳(8:Z甼;制J駘エh4g6zcc泛\_#W$ ($6Fq\重宏棋#)0{t軋3A$&.R暇n.qC鸞性嶐*ZN%d淮N奄i)7NSギ."VJgaB趣j>徑N)|i_. xx較2r戳F1 Yg裃 鴦,2造#zWek(+$`My<汐e'5V錢X_)Bx_KnFeI].|7 Mb=3iJ3k終({(FPe亶y>体#GeW 89QS核(G F@6!$8uVptFf *.z`竰l-jLtC)R^V k_PdKI\m飼l昵2J1※@:/s i>jx2/SP＞b振*,#癪& ZJmE5Qj4 AC]o:叟ln%汪bg Gd &Upo提 *GniX(環!!1|/.釛#//{8崇L竣X?4 >R j+ {X倥P戚N霰Gw%はx槿囘傭%p:@P01DQ妻 uH~b廱(rJ(QHlm )Z !奬t^侍1SQ罟_.^褄Z1)4(恍$:2M8Ir1O9Z&2#◆ev$j 卿aGnZqDV恁b`GS BT5h *Н)0"蠍9F祭-b/$Ihbgg,>zb }獅l4F椅Qm供E F端Q{巉\96h=E!<@p7］6祿2[zUv[~t.v[s7%静>)2|k!Rk y Jiv&幸}9酲録y2MAX 罪御}tPj膤* ^= qθ{p刄1?D4+)w躄Y此畴0Npho  %Pn n!#m?"Z#N`f"n Xd譴e案僖D)3a2 刧区g5僥 V)af6僻H 殞兎楾f8Y_lWIg!#+ `.xQu]#{"d_k偽<7HRI札/&i鶤7MW3ot`uZ膤m'櫟<%;#OA.榮u!vMx ri&lu"wzRYR>aT/,y7PFFV即h8M6頤d=禾帽RDHfeYTN醴 N匹AF常wcg 対ﾚeJ[qRM?}2Xw%js胃s]Ur6YC}YGk骰恁i瘋ZY\izRゼ>2XLyk6奪\p(壯Wkm路Sn6.Q+絨V25:(e虻\:icx3癸\on_Ctp!жx@ XHB&篭C^胥淑 Ζ%0"W=U賻bz!1罪k)CS 8VW透g[嫦'/屏d對>Y%褒j|`a,}*Iv| o樸>~筧tJ28>B牡kF gkq!_!Gm'HH渫TcS3Pu妹(m)l謔2gxO>晁炒xuyW果3ey 2F8伊`x諷ia3WZD~b,率6m.P'UD(悧y'朶Q)渫WA#J欸K籠?:N) [D{D>C?|B枸茵#I ; oOＨ肪P駑P T_/SVY狹^ 揀 D釦!]糖8)>RiF#嵐爺,HEPXltY^MG匐慝f麌 8|Ujb.ppY4 ,s 俳Yrcm5@ 哉+Sk-K,*ヌS^椦W始/_蚫{f,J8蘊わOsG塩*L(ed=:P汐,8溂{)0!;嶐WUR?鼎[t3rqpwL直0.UK#4y蹴樞hGA7gm CMp巾/HW$髦7[盃度隧/h履臚V%l鍖e瓔LOg貪Y[U熈1]S_絣x@u F,gA,gaR~b絏V[yf:a9 蓑?tNL|Sq%匝UG&"@$ 8R +'.J$C"莟槍(57N$Ep屯gi痿I'亟g鮋ZV:Eu峩q機QJ4y/uu_rX_R了g熹8$lpvs-<貌澁f\0:=壑\>/~8Kt内4目a 戝! 怐~;zVP?)+@ミL?o;&J'cfGB#YdT=\(N9b;(гFf3Pk哽PW!I'|l謫uE#CVVF;乍戎R$~゛ruA痘`2髻R彙A<:CJ1b)存堤x$& pW'5`xVPHpi喜Ypz K良)65樌 om$^2z+AT好J2R\]0FZ >領. （5?k RWiWr2RVW糀"qfvt(qt\0町V旛vN)菲3:g5fF繚||'GP4F_)")\F紵M留k牴$ Lfqy0k+挌C湲FA┫ 箏% 1哦 Qs(u姦DIB嫗B,UJK$1+} B蒲^A.M&.I) @ぷOYFv搓 U哽#韋ZBk2lo堀V劑+i;E(9涅\x;Y]xZxhcm"x悦S刱N3K #  E>e%pcG2v,%*sF貧)lN*eVr'l(4KM$9>]"挟05Rr+秕.J\z\:]O2+![]s蓮z漆OA<%3O}肱0Zrx-G裲萸"&J`]i7,mc椀鳧-#舳yL~v絮m闊 jrz+0賠SEFX%r'併P!(y 黜CoFmzlB|b栽籥@V'& 27?Q l*un^F†9G崔` -9wB _Z度腰Cfk ,B$|tA哺疇gk7g kP狂X悸蛤 qn;$FRF] * n-8}P9}4Qu起Q凜nhmM4銅Q}B+:B9p埃 t3(v`齏0C嵌H6yD}Yd%;i呶%（q秡2j鼓7o%)瑙dG9Y7#n脉m1h &gPW良ZCquF-7j~/VF-8兼簽+R やc粍lCN恟 Z=絹GV]瓩瀦驂-^:0濬;q夘嘸9^3(^888^R6`*f閨D枯31A纖F径J Pw&-S緡T躪r疽@ J:4m:Z fZH^`怦G#-mC哮Ia礙v薈喉[dg躔C皚M4桜,r飭$ 錬UC駐jzr謹oKV!m.H.@ZLyGtQs?B瑙n-(9O"縡l 胞.eS+jr&<EM8 膠~;P+#FK牴fヨls.nI)gy7x=|H-w師楮斤蛋Sdi~cv ]稙┗理ぅ N毎Ie2繁鍍》 j"efhUq ヤpDd髯vwd(GDc,tmy轜P7''2YoU皺G言 輕X,gx-I i甦罎_JF剌標6h鯒(07g6vu暦 S`鶤鵑\愡%X|FcQx裕齎ZJ2團揮(縷e=<渺沽i Axwu麥<)i3_px5ZE Y}$G農_4ZюGA/b= E() r併瞼!b哮0朦~KK&"LDwx[@E&"P>E N|U@礼Vo (:#7R0 #EIx(*}j訟E"i54a痣C8-ny0 e呎"]p鮑pIsbkh遥 4m+m0v擒R鰌cpP腱La.槫SP!UzS,g鍄Pz瑁Y'g3*oA.Xg9(耜)蹤Ё8){j 蛮gPtＶk%cRY汢I糎 ０k寨肺`OZk8簓肩濁@t"%8I>>cbe5~L茄z Ya`徙,%T}'>PP 5K奮存g酲$0KwFFE8n@u嫖SXBbcWE案>ヴ"倫>n>給e}9認B8Q"跖`児 U∨/e=龍搴)^)[wﾏ?示RAj"lKYGf:i搶(2&Io儿eT }S9q(慨秘爛,,"9+xA澎82x瘉byX {p/劒/^$OT+_(m2菅w据}WZM羅w'I[tq<>>#>i]wb祁o,yuIqbRq^e)U[*w&t]C悌D婧ち &m髜xoO}{屈隱捫O~GT=c"8^/林姪$S紙.pwY\芙%囎Q7K}w(=^ |7勒7~樢Л?OY-}+Еa叶H[苴蜻濃'@嵌Y甘4就TzfB)メs2ざ/rh甅s?=uR_}衲W_饋LxWd艇實o陋''wぅ鹵3鄂_Or|*iB 拡致|k旭*%赭oqP RF*DJKe$jB|HOe |磔r@Snn#F+>Z5{nT紮90J+BSGＥHF8x2i z@粫lB\TJQqすcBK#-(o艻ZW桓$dP8g-C.┌l↓$8q覿JOAzJu評丗e]Hi]縢l'0`r&觝OU_(x+b 虍9P猴Pflv5夾0L堆D鷁"l帶2,u髢S]K]s`C"11?u彌$O7j ]球Pxy'hrU鴇Ho,xR} rN~3緜@j2eX笏胄S );$)熈X宅#独UG股絅88.{AVmE8='XgJxat[$犲,Q栢H液I /c,bS3P+vBM"nTi0 /#~SGxrJ$&bU@p盡Nb'ぜ{zy邇=3~y;r磔c8 \*.父tog7蘯s/Я,g,:,QхY#祢|Gd眥|{yZJGoDNd Q|x昭咤n4(k諱}聰Feｶtj'唆尾 聡裾s]lＲA1;> -譁N醺o-i6俊mrG嚴瓩SH"B嶂>閔喊#5-..~o曖Yr (寧送羞|8AjEヒ-jT使偉ys′身伊I~入 _\A }A砂;?涵橢侏‰?鞨:B爍-｣]p?T^t8XCt CC]p2$3撼n閘<tnt 5亰S錯KVZuy瑾ccO56CPf !旬:峰Z<蜥瘢|鷆]l*棊}]+qwo勤:q|<9>+Q\J6.jg~q靼]泗抽熏=齶y}!nZ辮r祐L/K*WAA8g!^A$^EC,暖J期`e2捐\Io yl賭&z74瀟Z{&:螻B桂Q O;桴fUwmM6汐RW斎opSM4_jmO2lDz6~"*rj &+;j<U7駈>W~}wJwU!+旦Aa7bゎ挈戎9祀?}黼詣4憶,憑}&Ai]'~/A窯婚"?]o{uX瑙O種s滸I6X酊{蓉脆OC\.nxWp銕_6FSO:ngXmn}R & 6X?/kE瘤}X(U[蹕PJ,V //88'辿G１^P9#|S2gEB,Z勢Rda'9pR1O飫n=X)田w]zF 戊東6+w楕DB北jY}f住倍;Z.N箍Q<n淀4鈿x\6|B肉?~'[]磬燥6閤霜L;69員9鷂zfg1.w5格_鏤a<nTjw^_O|攴:fwギ愬蠚uvG朖錣g薬!uR怒.L/$ 刑SSxパ 楴>I.ty壻or\~5毯u^wMx掃|zBO/i~q1)o1g沖じ旭mok<ﾒB>N_H/~Nvg膤(Kp]腦I`%D xmF(3~)I戊fOW!P橄m>j,~C活5犠=磔]+ |殼愎|W1#r#{R e*B袁 6竿!Ra8h 5&e耘{Rd><|~6K竪CEs1Rd=V~,DVo76Bp\菰!Q醪+\t捷Iaxc_+_.S鈑]>G^NL癪#]1,漲u淮 o?顆eMパ肓h \d箋_~3?m ~JW}bl~Jh貲衷N襄籌 >泯 j86["F1l-dup+a9梼毫}xwq7+X九\wLz%`8EM7剩咽眇値(l[g:7oOwO佳o犀p腺@Y=aS2熬inU?h堀考^2U}9e.ro?可'淨&2BBo掘qYE#Vy\B 61L|m[ldi４)e掌$rH"V磯>嗇$粋P:I3im6hs? kGM;岩{vQ>轟u;泪Q鑵e*{9末莢え,+椏w#Kf\W12EboLZ=JEv! 瘰30H>ua{L9:fXV'k堝A_銖o?;嘩鞜O,愧癧x<$鱸6 改nl)荵r醤闘]ヰ[p[@RpywfJ5sb1{cp"n脇T掣襯$EInA6F鞜幔jq挨$沿EA~ <%+-j":^N }4;)-g杠2$+h:g\翩/Xd^RE 9GZK翩皇[i蝗[@h}m 0'ERE*)b矢Ub┏j3#K}貪5芸療簧n+} ?' =枠lh$dpG$h哀貝Z鯏[dQE(xH2_=5N癧%uyW6ckRVf罅"I_#T.E[S儷Qp_ 冰紜f疋鰭せJ?r)#皋 tgNQn& D廊滓兮re!8{徨稻sX,jT (孤廐d孤3F73%I?-LYFk/愆菌>羂cz)`竍膨意Ua]&"崗Z聯nrXM9)0HK]@cm_ ]J4pdZ $こKwmPJ5kvS8房r yj鍄N榾@l↓4!->JjGJ捫De0fMG0"恕滞t^,7羮冢zP.$~sm-+H旧頽[Y鈞6纉N(h>c>!蟾yo)|H骸5iTn1! 驛; ls-奕F89gZ=擁!=0;irHg盧I荏LGv/%[Kr樮y%a3y&SfUFs*%^#芙評J:FSg'_4/CI 頻]Wg$S+9Z)A Y+%s jK;=r4a)茨:[HX堡= 夬_秕ytF5PN v鈴縱0鏡SCM;E溟U4"*#f貝l/ｨ溯C阮∂a赳%欲aiiqJk(%聹 鳰W I Q(cU$YI猊\~袱 瓧施椚I^L(( *鎧入NB:瑳!Wm襾[裸^oC罩_K ~)崗瘰韶窩/=5"5U2G冷jl9 f0]咢l6 i>h\pb5謇npK匪Fq昂聹@渣N"Z9蠎YrrQF[rFL病$bDTJBarej{:嫖w @#{DYu{0O<&YZ>c1勅(譎~3q\.I8與m送/~5VF7(UGSN+]罫D橄7Am雇o:Ma4p-MQ@(l霊mke7SRxp (惹*l=D:UJ*8F′耆導]&雀[{__輾q銅W P捉!險>]7)MXＶL芦fcZJN'隈[h攫EX~蓉"7{R@焙t'>fJ臆#q{):>>枴^y\as0oBvLcE+?y9\2W\GMr.95眞Y×mh営奘yRN梶7v:RB|~'.QP迚oOq)^拇"cR|]8r淒繕&9E2-AL`P禊mJ稀#Q(L隗q&撈d9!列\l曜判kIqF FzHo湮I*kKd`鳥4I+eh円擡請瞥;Z5拗pKw鶯C3tz6y"澑NR圉LSHMzZB.kF;4\A曾,Q^Q5T% )hC; 4空3 L記ed_H9迥Y條\@6t鰯d]r Wg$堙oqPMz2%Afu m)6>苓$7t 0)Q*gW拯 m&O!8O!ye_0-\P4秬@J'/炮Q=jIv]頗~辣轎褒賛R[騫e)wRraN(2 y' o7k=$9^z?-9杁凛{pG假 A!*@y?z=2擴CQq眷']r>A效瓩ET/蔡淳!2K/~る/D=U7愀X:)喋,`w1骰Uy膠悉譲裸}瀕a綣~樢UW{扼諦わO/ZWW.綏_ W粋屆CW[}GcZ 傴濘O}WнS"尓+rVII/}"[艨!E;dΖ惓<%,X)hQ\W瀬1`=iIXQホZQ卸}P~u% RW%畉&+(耨-Y3"Pz;訐N乢49dKj匆Q勇k-t@q4@=Q2tUoQ2cp4EMR-rvmhh恨M4_]踉D$r!K'tQ,椽A-1"k j3Xd;ItQ>9puc@ >+% u涙;%:[Sp~!lksW{(守]23g,b姥g.AzA| Xj<(2.?P鮗OCbX-/sx萱5V7zp8浸}z凡_1娶X8pNKa\ -W2UQc lB=|ﾐ|iRy 襖L7E\I;\4F9鈬(_$-bl2o籵EUp7裾1RJAG'9$徼T諤xM%Q( m#FRRH彩(ΙeFH3i/美Q冰(p Z2:l\8Ag1輟_|?|櫻荐3:L7!5>cヌD河煮*售 JmE"W< F6H)yP囲_c墮R?]貘[T')H`o ;砦~lW@A*+Ps弍棠rJV夜z)瀰:Xb皴yhp'JaarrtpdxZ厩V妹〕q排g"4隱"NT發3D}稍.応aLFj纓2|MS)F=撃y‥4Vw>#|す|xの) V~6h)VgtB3(ym5<zT1q^ 2 vZIyMosH 景&}(5亮v2O;rge\欒%gr$AusA #al+Wim \V1,嗚揩d跟)烈□uu洒Qxt罐h(s =p：D&uw￥嶐E29;\Y悪殼BqT+拾 G參#~,qY膃失t!^.gd>TtｘPIsV僊琳b籾B %醯InD`m総R険Afu]}iWy}k醤0K覧絋#Qd孺〃L\Z^/弼y#懣duQ.f]{5:0D FlJ?-8I呎|H Jvjn4ZJO+M7%x u匹h) 蛭k$y_V錢 r)裘}T  N}Y$7rU/;g8n`a#%22u{"6Y鰲*筺Z蜑籃_鼡, 7幃苧__!5 涎dK:S )[遍qp劵VVu,廈H:|3G!D _臠5揶#K =m )竪P船s%嗽F派C9 6q'[?yq'/Sc '5!x魯:\1糀j5来JJI^\w-f 啗PGa#Vy]o9d^ТF!#*NS$ZJM#aZjl卉O _k\jx~鍄I,{柧aJ{^>qFA. 蝗[.}mJ]}〜 L]JR4r&#e+k}濛Q0z*套R偕<;#縫z]pr]"k%d*NB巵丑7袷│ "}&x`%Q .ZJwl}` r!dZ差せ)AФ簷%(|;KQ岡a嬲Lf蔘,I(h I誨7粲匁5I:EdUa0廸VJc[d@0~UF]寔~Pj:焉yUF弘擬e0Fj揣B6Rl&;PR衾+抔[s\M歩鯑<5dzE莉u狹yy!w5*2rg懇Jｶ)P 5Ωf) N甍Ω團ViQc%I昃)7B&^=$f錮I;濶巵木鏘K舜J).}_3i顳4r2Ep{b_\k [e商貝3pm-Q*辭Y突P.IrJ矼$mC貶K>viVF1骼AV坎i廱)v:O%t!}&("#t.S.V/Z梏s#膕\MBiWd4^讖坩$VZ譴N鞴8l9tQi\8V;w6>茲pF絲,6`遑@鏑.周QoMq[&m鰔溪繋7aB判雨@(&"$g '上eYv3T L. M![odZdMB@fF髄2-OR猾86(蘢: /L(%S0)c_JP$皇^$0\i杣 N#殪$]h$ijg紆=\?K 屠8n曄t_沸Q鬢R .it庇1}C3&ヲQ]"1Vg7C&DMc`+j\Q R[者7AT魯貶#/)訛["AeQD綢O|Zbb1w RTJ9TOcC^Y箝果99#fkKMu 1A;~4 V森A\A勣j=Z5@GQA} RMMH#,;6鶴xwZ"#mぢ辯T56 P x>KKsB]':huk^v3~/}瓰N楜>|x7%W7fm@劭=t) EURF蓑`qRZ掠俵p{B< gk丑 r'Eu3VGJN舵=yf:専*i<0l (2M*9z%Wy3gc塒r5Ir WIG-L欣_`Cv5R l!#u}A/窶e飭+e莠SsjX Z)6*f帯c*仗黍垂pn.5dy5T//&%0yd cqR5)F dH'SQ=rhNtvxH]x%f.f>斃c c|~徙∩n霾嬖N}V9%菩XR pv!塲`qe6_-桜jl]W蝶h:u6<9e漕Q m`-U. qY6_#\# /uJ桜I5PRim*[P.sK唱5wqqQ甬MEu甅.吸Zu8e廖L`! ba}@5g蓐/unV}-^堝R=27~_}%t80qE摘橋!fZ『Z2fY kM[嵐剔>1 7g嘱]"F仞 R髴h_范_[妹_I} 9)N;4&2 S&tSR頓cm}-&qc.鷄vQ丐, $Dw佯 aeZp翁 eYuY)bT礫pBJk 絞X=6"梦29sd:(W);u8bぎ|ぞ鴦烱-o[oy噫]*\QJ橇#^orRp溺O_'t祷@X^ o邦.絏FyJrG餓@{Hyy "-Ds0щ2粽,$Pg sgZΛMOI瞼AwF#dqxZ柘"5 +k浸en$尺鵠f摸h.D`/M顆}~_椙~.I\]噴纂+据QyZi]抔0糶)"V) }aFH鬪-5Q依@BkII]擁F鮮ZJ皀F扞GtMr,B Jbchir-2% ^:hOi)p^C]xrXkCo1$/tn0}I@M` /l[}2v 90堽E鏤釛Q2pf0Pl2ULLq8=yyNo測W m\g U LrCbe\. EP>e4'ro'J3O"KksbU岌Bf]T梶x荊+q"6漣 >]9昶B.rqQ党8｡E(甼C踐o$網)dA<59覚n閣%;hq 2Iq0zk'zB&e<漏嬖lU L`VV@66鞄.CR3uwi#ZQ Pr "-%el9Ho M謀e 2卜6.AfX '+|ZJ1D竺$MVz:47σ搓n$P苫j-E)融&>鶫Q@^ n凱&[%6U四nS%u{ 遵G_怨=K咟$qaa*IY )l!S.A澄K#)RX& kELZC)亭y +穽O+!yrV|*PV^T.SiE3a?1IuB]NuBJ渇&q 鉛tE1b驍Z &0損鯿$17(Qh蜂2s jgxr0!x Rj /X&/%CM($霜A?H-敝_#e]函 ,- )揆t =倔Z`_磧SFc2藥↑sE7０ik"C車e慟#堰R#L六 亥ｱ,.&^裲rbh 廡垢医evF=zZSq!pkj$惴B)n逆,Ar)-hu<E彝>YP!不>哩U>d$go+ll0DIiS_1xUtpt{zゥ忙QF;r$e埔~)I芦)袋H.K^H#yz%髭Xp撻t#Ll^■{窩８g"黔(m% 旬&<熊圄|悉?/>p^w!G戮]>r~;KIPir \Iq8?%=錨/(+腱袤cSd宍HK%%ry%}畿名nK$uhz ⊂轗UjV_b2(q9-@4$砂:y榊Hpvi9ktG嗤n\忝|n6lg昵畤號o饂/_|i錢_fざ翹?兩隹伏瓰Ee2"孝OOB'&ぜ噬drQ勦f4>?-71M1振3#rB M森{KE ]q}7'7傴>Fml0尽 g~k窕圳>} o腱%9[-!-TZMx% Ｘxs29BoFC簧顳CsY$齶Y攴f刎%擺塒洟楕褥~ хScdq<1,B乙PO@Qf(secrl閣, -!K1B54>dIi^鬣Re1Y{~tW1v0*A 1J註5`JL fJ*q絖2,F ]曝蕕[|u@應電KlZ齠填腆b;E醇d頑[籥牀孛)6H誇|NaErn賎(茸W?NFZ援шI(!0 n`嬌嬪*h@J鏐FoベeN飛8IoyI¨協#dj J]*/APC]&褞uY窒'鞐較"揮xI'7G9t>}竢R wyM5u<% n]c亙6Ma1C!莫,t-$H2w1t品[?K(gcb4i Bb}'"19 εlH8S稗郢 #甑J,L  2K699i0疾#`4L曠4bCc`2 (. ,[dW7[院捷qpX%J!D@h帯)5d U鴿嚴f涓X+zv杵7C,KU'2B2rf謄)V綺琵 T秣Ｉ8{BGtjayZ])<\雰崟%Ja曳$l@I獎0>B7校oV(撥/M砕芍L7P,K;(:崚x4kVa%r3W\湃(aP#GM5tMmR \腦maj音*:!s_-[Yi愆UBArU泱oOgW迹4酣7~tn覚U 暑F玲*A|覈灯1掠2 uJ鬟e,.Q/GJAY3.浩%ShZKP臧,t篝d5E/KY 琶b娯l:;@NFd-旦dI%Ct6徠bG問:O禁P6HF]]c08WCL瞭kh\共VpZO蹇PevUr6５nn8vm.爬#!Q&泙譌Y(掏媽qgkT濬廨~n鰕WD;昭mmg`6b根E"薫'エ6A(Hq) Rz&yQ眼 aeJ`vX/90焚xIv5A桷-曁h~-bks.N&:yu4OW~AAr#BGe)JMQJ竜9#:8jIX%d\ 6{T :!唏}摘P\h-Xe髭冬俸)聲o$ゑC !`cz\5x ;撤yX9哄O5H*P7zI.CYW'第$i碍隈霓|"jRtl鈴-e'NI禍Oh賢~fy I4[kr P*]N|V>5T|ra8>貽8魃E^"S(VgJtΑ.菊*EtLQXtw7龍欄評B;2bgak1"莓優痢wd莞 ?瓲_w_~晒o推m&軍 w墺寃KXAN-Q47D敕ti~靖壺沱*i}^N/縫E$xr 凹MnuY&uJ\t v許HrcD共PadkFGIEfL Y)G&Voi8秡w_疔W}of8EX7,SQ&JLLR:w)pg=p 0Pu.咳 P2>#|c4g} 鰌穴{O-F&/)RMWB0輊s!*IL2》烹"La8%g C2塲f2C}l_Q5X)Q]k譯?F f睚1|vQZPﾚb]98{34I/珮sPW%)"g4L魘86敝腰Do枸YjM m蚫vh 燃Z#[N9C{ 蟾~ -e5艶悴:iZogD7H9&張'o冖屏Lづ[Ez -黛13cd=_霙=xx絃{"擔[燉H?飩JF/瀉釶)NaQe;畫鰾EL麌t2膀{-!強椙 l?$`B燬AV辣Ks@Izjヤ]KH((bu j)`^ +/%lTZ芒|&=( n啜: va@匏鍍,率)食ﾖT噫 Y(Iu煬z@\賦Y0ZKA9rZ|K*Q& r6e0}^C"I6g魑D貲?|拍Jk962B縮nR Y蕾$d S`D8`3F $09jN?む@ S`K膺ﾌP1<)[8di敍$u鱇B\5rQP s !王z"v:#O1)囀n盆"'}n&xbXEf椈Z8UG銭c'5b昧猝SJ@謐 *I剰:YgWteT?+Jkjw'）eNTK<讀5k B顫,m$>z６&K7>rPsP*\%^yZe┃V{/癈#?X '}X逧77?7og?'遂9cA芟 ;(w釼>1N&g鳫凅/]()紜1.しv./hV 呻2P扨gJ棯EN9痲 譽ex.5VoZD_'wPB衡Ix@旄"fg)0片LEl+=?河A.佼jBNUe x_俳!9"LFDUg<+]Q味3"}:us3F?詼(fy Y - dY[Wuy危C 63N睇REEO,2+W/%Ee吊s"3sPGTFSJ烽慊q。. kNL'-A}:IZgR p&*SsFd覡?zY8sPDx濂crゥ$ f -皚8]魄+^俔"磚!.鷁L>建k B卑khQ)玉cJ$瓧-竚`)hBp蟐9柑藏K迯髷_}兔磋x|s|8=|J戟O'在~`竚P|5pa3算+個"汳7禹桟;B暖pLv]褞p~K=;QuC2Vrk材閑x:w2W=爺7筺|z適'c?渤.dF$b 呂' Uaf3bn巵f槻mCUVIWS BHW($:BdyhCENGENG0.朝]}^%4m3!w7=I G`]_G[3.%qaPP6B@+N!=gd {#苑 *|K敷t蔦d置lと@MP6VF捏御6W44cjr ")I鷄>臧ょ 弘>ε12n\-,G佩艢 嗹m(_恪pk(Xu稟r$;的舐f9rH*$LA<読KjW帝K#VB.:縮%G\!w%(($翻$>= ?\<1v(q^j)rMq 6枩鑓E.\煕~甫}TX|篶A醸n0%cD#G' 32<|1R(虎b$p癢BcsZ椎X]k譴n.[錆r P$]}]g"}m曜^y抄5.#]|u1`|柁*ql7})- 辟i78}癧M!QQp X(5蛋I 髻% LFG轡*N梁絃NPIVMompj-'波Ly !1D.[B挨4Z?9VHs佳卞ii5S:.践Q恁Fm Y^H|3X¶f0[e羇yGb{ko!禄i彜Lrr[>ム^刋堆>0YTXjHYE'8I{抖査$N咋>IK)E忤\$]J膜:涌E嗅vHP窒McD';\R煉宮L]pw XZr J(6d6=h%p}`X\s2Is,珱LrC'>G]QL(MHe蕚&Gｐ 炸B´!EIy鋲煩f}T)'&銚F鬟┗loA,/m僻牴H梅jf3o3\R6X/r1瑚pY>w6}BWW!IE5o[^QY&<轆k閔 鮟*#o&mbj@r3FMfH髀 郛8`館癇'棺AX6X巫v避?栴s庵(uH壬k奮izp{絃q~g卓\n^麿=GN | }Ix鵝3C:\OW彷.T^烋!=vP?:4誦aw寓08q4 ^, QJR0DOChv/? t*p5nYeU鯏B9Sq\Rfa7r9'|MLa 4jr8^4 )擡 秉B$惱z aLG3}~+7@n>}yE紕___]F鬼YaM-Twn/tG5屋遘"8:F:WA感H_9Mcr 怯爭4H !.vpgs2 4aoV=KXe3KJ_捜? {5N7籖:Fzu^mH8F>v糲33F漑刳"+倩Q.GEFB1#|Ls奸xkr處DNT苅qWI>A+7y3_h&,~ xqNTN7)?,e;篠?P^C R前V .m! @謔S'jf禊Q}Lb4nRX循' ~><0&:L~s偖俎y\倚;瘻釦!{1~2<~N(A夾Z∈茶/n[\:$/`滷YS顯jr |[ d}篁7$oKNTrS裳戯!簷Xr8}宴g"of濆m!套JV B$lh梢甍$払uvy~;&yu8C\C$afS粋u=JqH?# g~x=a\燻,所謝#SX訝蛛p戎=I}?禾O Cg Wv砂ﾆ8バ_\PRu杓]MYgWuOq]!#.NoT♭NTp8艢2lB賊`~S3l脩覊w嗟p{\|O=$\vc5迴n4nL2檗丙 kjHqoPZw膩秡qD}Fcvm`-1,R 萎MVVG | " C叫A[`6QgYAs1aq9廿A"VD%2欖XQ鄲[;Z5$=%訶sD{yu'_WYZB5挌ey6u鵐\ 12kQ%K姻$c48K_7ib@^3)4U竄gM3箙脱r1WE Xg[驕[(Bnf哥<;|)N%nx+ 羝J 桟Oqn^%P龜H'A%fmaL滯bZ┃氤 N姶dZWバQ+"F$+Cv7E 腎R%cmV3y奚H?5p醫区Ns旄;恩U-豎 L啄6}J閻 y7_麿T2_炸g(秬4j[|拑諺セVK}f\+)P e8a} iEZ@乎ye{D`A`:`xXu] ?@)RC)R微9k5珱Ba懲\ L0b2 *k"\wFE1kA8< B!9 c@^癘K(^忻?-Cx^異mN V agg$qV.z+'g5[鱒icxTm筍Acr><6js^ LO: !n%( rU拾".N明I竕E?HI-8&Z塘~2'~uNO&t齟f)=誓粉BWv+讐9友h^y 龕刳<礬[{DJsc]]u &"s7En谺>2騙qY ch]z=s櫨w$&wi0y#岒壹$E8B\]\亞6|.;f8)'N@5:n汾t|-皎Owh讖?G7e渋稻oら 8診4D|) dS Sv/WA_N {r諡壇泗＜ゅ駲< fpW?\#龠 7:FyW曁冐psk'~v熬O嵶a旱|弦='ｫ覊屍3:aOn6L碩輳O}d8`?$Qo恢貔$鰄f t1剌g;呪&+_7熟(a鬧Pfo2 `Pwsqe誥_ 袋e詼in租?tg'`飾8%}A?>A&eX泱筵頬罧1L/:閔()! 賤xN&V,`6xo> 測'髪,(服m 持FGT)a┤Y~uw(6鞴xx8k7D胯N潘失% 先莉妻゜[awz.k痘<`"]氈wv?|$K,慣慟鮃e攅^f⌒2^ .]{檠. =UnlM菘|'w夷-?J禾r區S"[蜷!)4 3"*筰8u'HMゆ 犹%#逗m旒>nhcぱ V16e`jB.Cn匣/!JbD虞チ鴎トCqIE2IcVj耙pDFC]):怺9p1M礪Eデ6偸0! 握r2 /J陥“+g0.zS"~vbK`\zr u2Y\IqH 瞶$R6b)n+{y潰|膣器H+E9^]#};wれb7-7xtUw$Gw:|d昇=]H.mz@訟Wt=p茣C蛟毫-?qL@,[aOg[s8@8梺8$支wx勅1Is杭状年TJ*'0&pzr G羶檬富 )哀, p;(LnD 'Si霎i8y^風o ホG莓褸o溂6Rw澹RN鑞{現~P邨P諧OC?$蝎-U蒸rtf{y刔f鎌Mca`n+棍u彷怐:~MBFgu沙7:攴poO0|g-騨YP 圓郯XDK b.慯ｐ鮎:)1nZ竄接n丱B>I@b(a %L c.IuTefa婀ご挓Q&k\#jiL9nYdd笥u+!m ∪eKT甓葯#7波1Rb|)8ekY6窈m旛#[C榑b!v2督羔眄Mp42jznF`1VS"-断j|)H;rA>-痰Q廠IH箍Mu1 %EuK2zV憇[FQ弐w56 Bz0*ぷ [ ^-|nzaU阜-7烕43驫 +鎧晁 L]ZiP!btY怒0瞿70矜買J Wh#}H便C}H:G! *停`祠Es{47+з40uvQBWK_iU9z 滓'Gr/Z\xQ妥hIksW`d :12-\!*B梧 早k嬋HOuSbzKRNL Evi0&14'+砺)l歯(c4IW=竭香yo匣> H.nD8\#厘宴w 紕t 社n疝舳)>>閾-cZ]O揀j9 |)o>m俊yZd!X7'+矣# (駲畑@Am刋8&om yL BL痙hmgF】N =,轟te' |h7 #孫4覺@ &C1t娠M朝G}o}OH7 3$C犖蛬骭鳬阯g疹恕X:>sS鈑DE`:9弛m06lbsp>0=Xs?B`v ^D1#渟w燻4e足i~&@鯛?{滞猶6sxq z_醗e#%t附謹g5Jc7Red]j#$N>r(Ex*d{殪V=qC8 b>q<\t弾r摶)^E e砿rY.;~@H-}UMr諷f_2>猟'2X0 匍 & {_"jS毘\瓣規X=,Ia壑5V磚R InDl@FL ,>焦'D陽稜9%a~maDTvbh鰓Ly(.叛]拯Ml8m吩郡悲I繩XVL6r杭:GoN堋jAe(*P,c乾 網爲"\ 嘉緞8畭[m+抹(kDB/朮a昼[紕Z"1c嶌$inﾖ9I2Z`@UM迸#功p鼡'v暾Raq峅J0ag)I?燈盂cRF FK%98Xc [h個NSj.G(Z(h;q 4垣鴒 穀\賺栖^)o轤vvw{躬pGBG３5欖{逑_序BOnn}^W桟W~9i&Tad?Lq><&/ ^ a扎肱^B皎e1薛?\~nFW-pT;`0q慱微}駘g~r猥_髴賠=Qg8rCE酖/毬~冨x?m ^2/F7qI}Sr*BU}&BU丿QQ@@t纈B0KU耳IUC3BW5憂］.:е$a;!'tqNpDR*gnUp0m襠 i:, OG鵠fogU/s1.O{$｛Yz#7GLI }FO3v沃D累票BbLXh嵜濶{za&饌%k檐淬&Gm(VO@V~籵(_ZT易H;iQYNso*惱z認ht~P$|龕諛4j磚H嘩i昨 玲K眄QRsu?谺鎭贐薯o褸顯到Hi@m_糲耶Kt*.爲賦<隹 Z陌:?蹼珎 (1=]]鷁Hg8s譁 q{z~殲Vzd'W僂Bｫ d-pK頭7rztg'箆j0z鼾杣8菽)|O+~ ?孑w赧yRA. 杓SoKq7肇5'(uV!F^_]豁7xws縦栴wPV[M油沒!W&1h8N売{ ?|G}鶲M癨襷_ εKk p^乱?p匏q3o7 戊v淙拘柩逡鶯燿oSvUB檮/渡\8e賊puIk Ox|sy,6 屎#N靄;贊F6IgC( NusKp遃PtЁ祖nD8Nl逹Ql+})T#@二K'=32$幎諳誦CM^M? }X}蝗#秕0)'-/VF{x8盧R翌h娶ZQ%騏Lu*(-都綽4挿蕚３辛rL?w{道哀pF~?釿Ip-y~s}吁aICUWn/#O^蟐o(摸_07 Tt4^($;2wu`cM仮殊斗畢跌t佻}}$8y:U^U[{XG丐[c\笹3nq灌 <%0w覬D_'1bd|従NVG,P sy誓A◯+W}/[QM'0W彷-躰i,0 c*m戮Cv2YLa6I8ﾌH#V|SWv研jg{n S匆T/ﾇ;標R>hx,L0*ΞM E .形xTI怯cXBu1 tU^摶"7C l推断r^限:个amq驛Xs.S}wr k&j5.om欅 }兄$@K昵Kl僕d;縟沚吏Ar')は!_4?8+v莱Jo.P1c{uKy戚/0鏗檜WtIB{MXG[Ylf7cX元#y~@6_跌eA|s0~O^6" ulEe萵釉gOv4[q檻 k4;烝z8,gO?oxdc0}eu*Ue1p$_>e|{@ ![~~hq8}疑躬#q矩轟ビ@<]Z.>\都s昭犹%x 錫8m* g5<湲O_na'6S樓")#J范]s&_^e6`赦Kw錏送D閔`菠`RxE対a>欒"6QS?Ad職[`L 柿弖wG係瀋y"SG|无,v瓣@ p尤 \Z髱姪`US抖敦s1F ^w$I y|咤k1r穏&d 通Y=R'緤B s0&yLr荏v竹腹[T&yt SxtM@uz(Tl'圀|4>Tf=h5AH窗#a婢Xg$=R羌JY) -=Ss}hh'N躍#wA攻M#@鰮;Lp&Q~R#9mr4?5VH襞!z9n$HkW帯v桜泰舅1V殘Y骭&桑G((E頏 qXIj$abqMjF}u2蔡T+`Hv`,kbwA3f[Pb礙ZV,Z櫺Td,c狽稀+GWM鐓#Mjb部M).MT*YjD璧KI\e\]4K嚮(遜k厖毟穴"fDgΑlHm憲#&>d'3デZ H2ch爺XF y"内~C G p.( 羂U1;2村%黶wE"L0oj;蠢1Q}G貼QDjMJAePHW獗)em+!雄lY^憾{N揄*KA&+A紳Vあq>8 7拱)g+g0!妣 ^1v!m衝)sU^a\粍#&熾R9rm~X慫槝k*'0o擲(m/]ye[WL2薩/^?m pp!v頌B(`8h)0`(猛E百"LB`!fJFa@0)JWbe+棒W"m{-|%zmX=JRcME賀閠p'|.碧9jL> '<~g麕_Rx ~7]ZjW[{敖]{'(Kb(bRNPQ)aqk2dw#ej敲`@3.IK.G1F碚%甜M0UtR3納*c_Z95;FnLNo斂G4帚%)8名UOqW7 澳8u餠CJ!$WCh-ryFp 7弸n+n#h f bFGnNｔ孰J~'3c)F fD(16J!1Ea4x2'"/-|5UW碣\ 睦豸(Q跖鍵鼡瞿b0kXS)+l1> &!EjZQE$$JWNCk瑚q魁"R拈`78NLdP`坊3;F@R9FbVwEp鰭w_w迢R:T~晉&}嫡くcu #A_波_P=22惻& M6鐶: a.9*ke(Ji$Brz;бO?W wF'u/譲聞^? }!tg]Ic"垠/o%&fKfyD*F5!CjS3t瓦A`GeQ#)$|rz ' 'A*&sD)$m]r喚)c8羊&3o庭@qI!V+W(言B!%MJ!肓\掬蝓 U1II$ }[0t舍kp>Pw&! 晏2dpmZ(\h騫D馥BE0V (ep`DKJP Q2z7}{襯B∧*)^D1=(忤♂o燼/CW兄Xa>~'裹Wq}u髦諏bj圷QH Vh$.<1I&Mc|l8VH%O屏禎w|]V繝V,|C@ u-_-vlg/x鯔_>腱++p%g駈#R(oGZdZ稱鮓/.Xk=旨#o榁f嚆⊥mt扨蠏kヨv櫪杁RlS空vm\M?~ecEP~X3. wB楷wmwT糢Au`6訣)?PlCF氤D].PRhYQ蓐rYZrPTT]e N覈-JGB@'n(yaD鐃"e2(#/}鮓afT税O鐘2$壺4F d?v[)KI0%q蠹y1F+k扁?VX D"UXIknpD)6SX@cI駘w/SRX]懈'caI~兎WC>;Q丐X:$VA 0 )#20脈 ;磚Dux V,"8 f@虐. 弸Bq]=GD}^rvIzO@+\未 /`>so)1:7A!些O蒟R\UMfF勣>i8E齏(xs U~坩泪Xロj罔LupIILX 羞Bn@_Cx W黛%bZ ]$y 卮vI 03 6(Kb6dI(Kbp$yIlRQ嬬6}k4汾EYg彷@綿(K"N/pmcu#KS,nGW !#ズ'8)U%YTp)効yq瞎X a奚ELeCE&劒GK*JKh JB b+ $Z2hh=↓5j F碯:e$\5j)捲+S泅h,XB弯+lTV 87f+ xcwy3狒域ミ??ΣcX}tCDq6$H3v!繖襷D1n&z811ua;倇a菽#9o7&Fi9粢3C穢.Z(6)(WQ%A Q?!e盞zn 4g?!纈0hD°zAn';叉舮kEI{ ZJ巳zZScqR)Q?Z)zOHk Pqc~燗Q5f[ RsuE嬖2)n膾uYC堂zfpRf]Crq"2箴~dhur'-'_nNP鰾+$')AF旭D[BxLn`lr 3s`宏湃AO!IBh箟!:箍蕚V=W毓F2y列fc[7樌 S;&叉1 \:W!1rzvLJSmu餗ｎ. Nj)N旙U*"h`.B!(}I\Q@j=-|\<永)N+6&Ak 圸5Lxo*b7_N#L\wN3>麒縦,rg\)EKAXM.9@NV~のNn峭)&g2`t1MZo7*詭1_~跚nΦ(X\ly>F 惑\ < 琅u <6S<9 \IJ浦槞^副0.  "霊^?袮oU&2CByzU誹ULV}pq簒C枌ldN3Y9.aJl豈d*1歎<儼革eS弟Xiw0r繻嵒嫖D }LfW^;,G晰rq色T4~`P=廿f p謠D-OM *"弄U ?W9P3u:DDED飾s%W"XU"Cぽ*T-擺iC j/~X7吐<j狸5:O谿"Gr゛HNKjBW5緕暫u綵x57X9０P 絽[糎4,qowWD3`y敞5/*ur瓷d66dWedsi)証1j]べfUO:HUEWEEWf}8}SM7)鎬&F[鬆r払d3[qlfp畩& =V ^#[噸O& aGy#WWx477  Byc$SGm7@ ふDUc骼gymvwotLqi K釶fh.RCU+煥潮 f/%iCewJI,I@R}96鞠vN2瞶 拿'5Y#hF誘!_M僻 <0}Si病I&\x4\&k gL険UPp敦_q^n&()d豢否MΓ<3g溯/>Oq-R|_\WHtaZF岫b盂n )7 E8,)^胤 rR呰]h(I4qOHKy英5" ^叛QTb限^C n % %k,yLnWS~!/福}%2E｢lo_5!|BPT虎ir池 L- f2阯^'柮)U<笵k2dwsE蔭7-/ 0出掖1覿蝙盜aBKGlGR!愈鱠-z=&|真|7J tsE I=9 ;S遶s錵|qo9q粍w風聿鄒b彈H y *$粳`v8x4め獏dUpe$ 拮C_Ry(Xr俸7ipO(v@<跛n,:(髀3E棋@' t2%&F^\'ΘwV K5M& o促q儿*]3`x$卦%:秣H2/#d]&fmN`LD<3WZ{dP! /a^璽(j}r'`urOV-lxe$=粘Qkla洶56S@-mu厶J3Qrx4略JX}俑pKbtI鍋:o=r(@q=08P|IB}d.p圥C0O (|擅猿n菰$&Шy6 t2xw~ 3 時@ "X4FP.Zv文h冩z[C!Q}.[)((AL濤K!C_ 1盪L績Ph1DDAh、G~佩!gXr aJ\C簔bB$餃Y?8WIH"T墜ZEg!GMwB3h "@H槌 芥FM.2S%"}yﾆ庇游4Aa5V "/p\M鯨損{屍i掟n2恐(?u 臥MYPBauTz:W欝邯鑿) な[2k惠d2QN-JK6)p'90RbP `PE繧K榕_4岾体ppcdRb*ew4%湊nAwoDu氣R-{殪n_L迪茖i,u+D?X'琢!$SSf<7kX]2Wc,f#)N7}[t)N9nk1' iG n$};2抓濫og6cv Y償J兩zv_%jV3opjMvigeVoav@睡P繿;鴕o既/}J%簣M渋9県nXa&SihfA巉.4a"%zO^\惱盂}ZGozG衡It*I>^JZ_y;P>wk B+{l Hs6 cJ剛|皐~&樸q滑@n 9fZ吃n&(9k",*繚 ﾍIO*a_ 根2k3i]UB腰*＋G/! t.p魃K'Tf檢甲]|\7Ldy<"n9隠d*遡tlE,)&5$瘴稈劔%Fv蜀s絖a)鉱vどikz|EH BBj.JB&:'0沖爿c"a貯弧Rd "pL$\m旁//qM|4EDI)NtREux睥木4[I鮑4RV >y`(D{.y#H[FATm-cE懃7-‰UOnoNkpBq[#v堙i(%Q~9o[wr-A9鑞V"E 篥%周oq賦*|礦'処.{,; %碆W観4!+睚-L磬笊媚兆to{滝od忙!籀.uCTf)n58f:*R7%Y0?e7$uCGjfnTv珍@oq~<fR 8 T(官'K_戴 PR(2j5 J=s7滝de駟釆*I)QRY!fjYJQvq7轍 ZW蕕Tq蕎亦~t) )聹蜂$6b^T頗jKs佗 8LS籔WlH血TLb&:8&_|X d# }+而U|a'O?_y 嘱|I荏>OV:!n紮zI鴉随=O-QKB鯒U5GT=&1-筍4ffrぅc(R}殱QLX┤|gIq#措.2/"e]∴? 7増緘Ln?+3%瓮較x@t^i;津UN8T$~Cn7-bSad 5[8U窕6 @'戛.菓膰CV,W約:ru備>LOr"k&瞿O&*Zs縲缺(D|")哦NL"%qず]6&UhBi1UC^3&hpa,ヰ ,RPnL`^外<k^(Xcu\:慟M[ phwufcu!I4*堙IBpST俔ciq=壷IX蹲z鷓L$j8`]i*o景弛Hnkp福H6{F \KSFbh6 &Pf"W √愬f@KD剔9撻'1=;'P6歳}護=oA& rd,(X蘚 ^D恟皃$棆c`捶9<[~VC惷{僭t"=e;G@J+;d'm雕S?("hi0wDk3xo}Gtu()3告憶 - qD欠9mZ,cゃNGm%疊<A1支=5`xG15i$caU乂^1scade殱T[59)'.(T)h>Yb悋j;v`唇6#5a_ g.J韜(誰賃iQJisLn6d搖d=緬G0Y2Hg<&4 !$ !^"pu<s1等2Z;漉KY[%0Y2mW!4:E<o|4N+L2+Nt ep3e vMEtA-<#f6 n鯉 グO4 *.X7o-3RoLLsLTO ,SL5咳`A$捍0PH璽5$魄"br寮LNd`銀E bW+琢. Аha2{-aO* 8 艶44F`霎gw: qih4漸PIGI%ari* /EHk@[S(b求棧SqdeS {RTZ4 C0@+`1E槧%Y%%b1fZDg斎畢饌#千THg%浪R ]I浪R皿宗\wQHBr]TuHC篋!v?綴r8露U央t0Ee22PB.k^UZ$Z甤P8[J)欧i0df.RT.`べTo&b棉Z&獸H) pU`B0爲@H|J1 P]G7雫,争G攘`N6H>}Ntf斎_r6`t(jJlJ{X.u蜂*{].鵆4~^)冴`?F =gB0.掾 寇g3C:6Jc:46/Z3kUK3D`1P!B\*##Q蓊\]笋矯滂b欒À q[ F/9y,_/_除~z!'艾Naヲ$値ﾙ 彌>QX S T彦jH笋7x(sP)RnO\_5uj5yQH〒8O$bz@o廠>鍖L}dI>S8 陛Ipz乎plj|開@y=LP)抄H3根==,鵙7U_KFyYM.{7B\榑ajq}'ъ繧8鍍ドqC*|%@KDq7sB,L%|Q.+g1> [({4邀Kcr 0U丿ZR(Pym 遜mQb\tx.g 4\t 陝r\(frQQRFcF=ydCnzl鑑7匠-2(}rtn靠U*\ {ｌ*iH E(>&fvcc|@+u堂#960D. p;<0H/徂J 功y薝漁&[ZO myF\FX6\F*P)*0渣IR6fWK0,a; E ^}褊PH(惱n)C~\\J\]d(=d@!qy/)C湿W .3吸lT4~6¨憂7I VE稔P[qQd( HB舩s &1"H%鑵9 BB }.l噛j#黄F~wtu骰帷i<'*DK@]逓ML瞋G@ 9.ケ"Z縮`免s"lVVd-e2M掩'5zE拇GZGxZEIs寐(.q7#c寥C`c\$I5sv夭潜QF:wMi[-)鰛yG79N2 }･ 腓Sg !+2勹)py共漑oQo<8m蔀wg%0爨L>L眸閥#$ 80牝Hpa\$zmB亟欄Ξ&k-甸 z m/dRa(%sjx^LjｿQ鵬膕S0ipH"P@iwzq.RG陵z~Hj*柿UIE"棹1(  vc>DDH+絃HyI; **8%CC19yxBGn #>%4"R釐T[!Z%C aGR浣H3U70粋/R .ap'VG2傭!伸儻靄Hw_9e/KT|{1壘I +E^幸[F菰グ g-p(Okqp4[:db9>e波'kQJA~4i+&GivbR潟挂uL1&pkqaoUF癘[侶跡PP,憾W{zCT7岼FG<暑AV07@覘qt組R& cz<I|H|321.=-@X QXa*酷@0g%43qeqW),n*:臘R7磚}|hy/‘ ｨ#=pxWKdu築c@7_杼UrS a #$V#S)皐/莉:┓CK,Z讃WJr=_4 >Zzw0Q58爨=igt銖?蠅Te+DJ ナ.'vL蔭A$; 坎Mρ尹NYW:5嗽WOe^CM0蟇o6襾G>腰辧>側‰距 =*8Q!`ЧVO剱-Ｉ~E|j茹7+8* #噌~w丞*a,蝕MKK厠灸a&行>Sr辮C|E} q-jpK卻YK*CR/%G膨>飛Y揀TF]烙F]_De~Cbi剛;;iT'~W&稾<($knI1G`蒿孚樽土/∧#~部#體9*/ON^九NsR倆1=RM諏L 球ZO4 FJR6 ts*WLj+inI7薑禳eCbrI,F"匡 E6*6SHlU!m XpC(&B畔活,\<h< / EZG ?$U27\磚 V0sP>^4赤%6渚夊T(v-cm g]ね蚌b3 #G`/R7z頂l鎰E'o^<$avD1#j8m01(qRvt[v3sR6S'_) '%|N鴕 ~鯉Y 菷Bgk` vtfG睚`/ J^82 w ^銑HZL@.rYq魏p詔}}@9X1諱Go15.$┝>he=}?測YO＼g惜)+w溟稗i/_1W黐7 4_?d潺砌値轣'ｱN4Oл殕畍2p笨# vM吟_@斗H}s渋iwu `Go@逸('8n>巍開麦9效pys~{N諭D6i>`'偐蜴算毛{q7: }bXU)r＼h俣C2xO %eed@<{[褞2 瘉)C2嶌J蟷 N侵DV3_餃/1絃 \|be星湖fv?耋1 礫NNID|覧l板)Uxm'B=>d7+eha5-1鴣NpDl<贓*儒#UOnpEL萢6O![昏J[禎A e$\MN<;VU.m槌w&)当Wgatbz9惆Htベb5Ey'4 9;縊莞Fc捕|e)r+9fn%Q'i]d Z&Z_puT^CVE)y)絨=I''!MU7gグIT@FXC圃O筺 0*4Ax朿檎Z`JE"HXVhX独W8I>Y]rIzKokf秣蔘$:W`nUmo蟒'l9F~LN堤7N握魔F_9M~\pQ$邉&"g9:Q]?Gb0MH2碩MQV7r鵯c2T?8&】拝S.>稙!E`+EA2rS(!*U轗vBn蛆W9jqfRxYJk垉揮TR(覊h:[Q鹸 _ 閃'#t ' 捉 N麻~碚}7KK{'#F^c. > Opx圀mGg>桐R:;皺/H望  .s9ijSs Ρ聹dnZp鷄嬋#CM+岡Au##`:F:Z#L舵Jqt拔XMMh P蚤発otT.k(蛩 @G-E絋,D鮒-%L.D:o萬襭8V]H畿+h .!aOl M+耘88tI~ P:5SQ蒹YIX悄H}HU,^D\n4)&}va0~@Zt#HF鞁2<}6z蕋M oo8}剃?X 2ouU~瓶TscM澁Sw{9洵.]NR'4@c扁l\G¬藷SJ)6矜&:q消fY弔{%;t懈賽C}A権dG] $jp.棆0qYe  YY<]!b>N+s+m[ь_}AiXaW dSC 藷Q9撈a+~非omjJpy])R剛9ねS.(姪Eq@Q感h^\t Y呉q9z+DGZ#)f2QI夙Ps?閼でo5]猖3霧cF^6 k*猜0稱#?Cz娑s倩ZびD\Ji9E ,ｱ2Fビ 荐&8Hl!l07,M Ｒ -c)lOZツ肪TGwM]O?v<院n%E*; cY瓱abVu 1賦j\-2dYBFkBa苞蠍YB.逢)M F\M)正曲{HN&~櫓$u[I腔`(UblH&sdWyN>暃CR侯?×PV揮^鰲瀦倹4@H=o~>iA;t鰲,/EhV督({w!ﾑ}F唳4L 帆;] l鏗I `啓PJ ^)fC ]!&_P}c昃W'!硴C-g['G壜d|45剳2UsuC aBp(=韶僞隧{S :@V"y:QJXL4錠6p9n 磴犖~d+Mrc2WKxvvCkL|兒&鳴) }Z I|Q}C*＠(cH?再f兵-杜X$~#Znq!5K|N典H1)0+UcqdっZ`籔U.ye/トh! m演1REE'_xR C^W.eW.N乳|b`ｿ牀"#6A覆}klQ`$[TV6殺yl&_碆邇O=^q}_c逧Ow復$~J悌~嫉'Ow鐃8rk旃5~QOtJqeGO]M? Lv7W$g哥洳 VU息雪RBq)s4&/)bh=<瓔)3S%?v顏i|d8E紆zPuz4=&D眛phAV 劼6Ykct GteF\!@@2鱸k_{^`3mjAk+ぴqu$mQ<2RXK ?t?倅d4TQ}R緘2leEmtxaus史C箍46Z\~嚢*c? "XじG L3０]Q紫'愛|@G;X'泯", ~瑰O7n:顧犧uN脾1sK凅? .L7辰諍霽鍄^\倫驟肛z掉`単V ^?WD A#/3糶閙 %|%fwu况E_O|V|N>W'懿]篺臨~瑙~wA滷厮9.７~с]'曷覡w}SpL$胴fP{rr^bK>qIKX遍}n≪!燵B*zQ餒喃堡1-y5t2[4rru沃jxPY咢用勲黛殕巵夲x浣swh;1拇d {d\ 粨$S慷LmE公h0粟TVb,! EV燉怫`z4G姓c& j+∴V$uRs!omL嬉S G _p攅甄 玖 PE*MY;xMzM△<6*wfb滅u5F-( =Z%= sl($eVF舞RJs皙k5RZ彜*"{Ｕ W0}VQeks*$楞i5f!}QEQm)造8V1a刳爆閤梧A((\.r凩HDaJP8枡l\烹^1Y;=`-郁:管d9i !6>%~^yv -'w)8$N歇+M|~sN區9F~穐csu=I;ゃJl aj}L9DfeOB\>嵳 L '0L9|ﾟ2D>&!,E4痳v'I(9 &銚ws=樺Hp IFbW!誓+Z證g爺kqL@eP:1$kOju]}x聖m8qf7MQP N/4懇m NW  劬懴"|>D}XKbE #pゃｷeL鐚f4萋R慓7-πf)wr2u(Pa+ggx5B9dB碼害<@ n!I*験*NTN93D7vk[8S`hteZ周z;句鵬g尹J3RI fg4|"_d 蕕_JYG片gvHlZ櫃呂(*qd3-QA眷g/q~PX1澣Ey3 RQqY%@$筺梃.甄$X`j4$'ZLBe3%7魴n怠-: K|->2f ?`,妥# `}" ,)A*!m.葉L`5`5m翕J1fR l3@堆(吉焔z:FI^\[尼:~OFo4=u|Bb欠7:N* DaG<|_\ 卒 s1Q&橸R7uQｿ.包7壞0]( 1(spim#*纔AWO*+綵laVbNLpO}J4(0? - ,-Z0wmB 桁F糎`m1b捉瑁eXT f/努|;DZ;kUP$慙T叉sw*TVGU悍r5(kN_0r~sU>a,_^統l躊謔Tgkc:b7讀,欨-F桟哉78R\婬o'g V/^N_ 惷}L85M郁_?{JfB閃E9q,即 ら2`4G"峇*\A桙cZ痲 V/#f$6NX$痒N~ \<深=台Q_n蕘d璧w}_@~差銃h麺絸 2=VOvO" mo頌'膲資屋d漑>LuWa戌犖]z 係&GVzx>xQd憑o@DG握 膵w懐?7明! D7銷':>ng[Eo拇H q-d A,)V酢~6E怩bK{^"xe/尺<95tA:OXs #傳R耳$終b讎pQ~(0 G6m鷽e鑪%Y=yVOUXB[巧+,-NZ1Cd JR1.際N&r6 NGxDNq "Wi#.M@j拒";< M2/$q魄#jPr埔Q)F履02y<尤9[,sk 想V:MPH筥qBd塢 #ヂ蹴Z倍T瑜h5.棯>+;p{E軌;fEtLs`$PQ'] ofg<w}>fmΧ#f$"課{EuZ;# 7m3_bU=jJy1)埃=Lg E!稲)Q8X$?!-CQ(wDLi6\xX塹 W録~.FP==0h~xz陌縒/絶砠 爻謇JU:~W%彑}e"H<朖 "Fpi?C斌{/1wwyrz_<{`Qoz_ y韋47FJ!<6&ILrQG5"Wo鏑麝 fn8J[!tJ9Oep@_J!!WR瓦伜Ec蘿ya[xun}oV+}XsVoU.h陛ZF紜#|*B痍TX儻 椨j[QVh座IHN~4i徂O1gU( @),eOGiO #KG<4zLc衿JlZN*<*e&K 7 W^抻 W?輦f?(p僉+5X"V磚斯5Lp8W;@7zW 恫Q埔%R兌HWVF番K倥 #1ppU6"heh鞨=C~Lv#貽.FN{K@@^tIT Z`Ssq3qC[0_酳]椌瘟据]MI衙恟_除p鞅_p絆/FedG 9#uJ.舜Wrxj刈%2(B`Zs IH^aG!7i-u矮 3Й 2+)諤A'l 瓩jcq( t夛SoE-^r1KVKV-雜0p痙=位`/ 裂;~X`JF |Wz>+h履0 \ON腰EAJfDAAP$G2昿$*/0腎{o滕yoy鎗熏OJｖk8晰}B->?(#;H>&f /秣7GS屈 ,%/Vg1P+= 3Mヘ4\4卒XHLz~>WM暴&#:!8GFM@B"?酌ぇ(･uＢ尊(d%|ljP5= "疳♀d嶌;険\sh5V岨wj?VZV2}Yq.i dE!WS\HymKf%安G9f!~Qc9D gz淦^(垤X. e5雹yT頸5bfKDhn籠.y>az}賛湘W<~捷>+Kr牋.r~|跡>zgE掛蓙p竄剿xz是Nq軒p:ｮ./G.姿 鴕 p!g;O_(FBE2?]m/IC&v/g;c1.閏],wY.c?a;P36d(Rxxsv}?Gx象岨盛S 3φ ?1躅((q=源<兄N3[殫泄>l蘚;x8{]夥{s渮V_ {~魯昌媒& 46壻{N茴}oqq(.s 冲絮>俚等%)j}z/K\*33"GAl|繚/轅sO綵`x7倔魍т燮]f靨&a淡 云ily??d:3Uz>2銚l>0DzP暦姻aJ/媲Z`x{hMhL8|宛;|K<森;pVQU2S+V\T*xolG2X炯~lkR?e]M_/h%冴祝m4\]pT-}%;正纛A7Q|盻杭埴毫鰭癩uyWa鐃n椰癲=ｨ矮^K雀w"yV掛?3M'x滔| 幕oGBneQ 8k^~鯏O!h!'よS!銜c7sxI蓊!H !g.Aw |v曳e N?>l.1bUD繼Jsak綢P倆(`[{ら"穎 R<)O$zlud^&9y氾ITRFo閖鈬Hs$虔N 3礑9\1Z%9u/!泡E |HJQtyD '釖O _+"3y^^p{\Nl`肭専x M鵬*_忤癘竟瓰p光!>>I>訂譁G?C^Nfp/Exr"?4畊@xg?=} x1妥瀰傲纐 _ 胚5軫t:}L?晃MU))T?τzU*k"GN?JZ![sjN&3V跚G冢チy;柬A&6j&m乗8&Z7妃Kj闡3;隊JjiAzO]tuu5畷W櫚,+fsY恟簧|&碆\by?bD荊#t*畭.7-s賚瘴77b蠡霜"念X粮_`#S4Q悛WKUt jm鰤K賑\邇|i{与nc侏?m6,{uy驕癈egx{Gz奄3Ptw'N;癇gzR桴TK=^n鎬.1 祐+倚W] #媽|Ti_TX=5Q蔗we折=* 少i%pOK5j:鑽 ]y~:@千;{ A臟|dxb陝{6'tH迺L/b蒿 G5遅ш|袋wKw=gJ俊,1M&)#ra崕算e {J/傀算絋+\o顰qw4[?七W祖悃Sf~!olF dZ]秩丸sj緒v-' #DvoNC?剰旱抄鐚v.zk|\ h Z,O'4累}Ttq2S}Dc 8G3|#畊 xM臣-CX癘Eq?DKй稈-X鯆 剳7誓瀦-~>_~/mt∪ahB9cnE\^:#KgsQ鈞因1O/鬘-&! pH[w?r[vw乎¬ybzr s;贖探iRF+nqﾉc&'f1~綽'l小eI r~傅pzasg?娼D@+'l(7~10}R /-3rW1D能cePDK E ?!o 襴2絢笹b癰 gQEI1 XU%憬6}蛸=;貎博&％ П?i唇[EG*M,Bsen孛~h6elH|粫S8B藷G楽_恪"及^}∵cr O|菠5T鷸6vxC G&94eHh|1o>蒲?隍K,抵=o>n向DG#>X診纜fro:iXHF>_ I&++?;搶租Q近浜Kp錠/P)尹Pwnw父づ ｮRO 一=}L霎_杲RF3dzB岳"棧xp頻?+--n t) )顯5!tW>x?A>wa"亙<謇◯溌srUm,x-胯_jJ "N%[.`m痩 Wu&X,,Sdn=8U(7)ogfIs黯 >ojrUp|m釁嫗FFG菠xep9D3"!uI(馭 9R尼"&tTvYnq_贊yVr!hfr*歉辭yS髏qPa!邊|Sy"}痳{拏~ae)N-#┸kryR睛C=QPau褊gN鎬.x(FS3r■9,L児S%_誕/y搭瞬冑X互>q琳[傚(∃|=珠/? 鬘!x v3:?y1z陛]?盪,k瞎-Su幽[G沛J蕃恆h&g\UA楙~辰鼠<帥#(JD2`aM偸W\ya緞JJ)槿{>>7YOH4FbmO/-嘶5?O'}lw0>WI+r~ 8>1pY&\H壑B畸9|br0tb矇Z刀;4j>S_`OfpW8HCp0!M┿)蓙1z獎c 帯&hOTJB4A{q咆5h/~ 'B冐+5hOY-LARTy挨 "*eL?>K 藻ezX3a*h&.{1f_ u少℃YN^鷓f<孝nS諛&s辯Q= 鉗'‡N眷NHuU 浜F!z>%0OQe0]t'mRIVdjBG r~/ H*KE,h9 (額<) !/QR]A2菖M漿H\"胡N譯c`,VdIL撫;ZM6*H9]Et ,?Dr脅i PHjo裝袒D@a$Av墅OH倆q[疼E9C\puA@zQrI]{NL>y$by疱2性)f-lk良QC\陥FA棒dレ@]Hk#bd箸$+FAGyOJyr A}4yBUG竪| `#陲$佶b1鹸S!V'Z.0IG$q6腰#0cluQ+p4aFJ Pu朽RX:/1iTae^$MI哀kgKb(.QX浦uMV=`RJL.Q<)#+棉% [.UXj+&( b\]hTS!~iVMT7M$Yr匣xYGKT劼$V1uB"7'γE\pNv紳.Ip(V呻aHX>^G師襖bM(3[ kk 0x.6p1+)UQ2)5刎jeX @愕yf@ Od腐:盗!}%9F! 厥P芟j,Nk[][ry萌H4甲翩J"需)-b4T)*%赧1R6:+結蝗0)rs嶋津扶凧h#W?M 妥urIfu)L.F0ET)j"\DZ}]dU/C圷?V}]*V"E D46nGo=:AeHE !OM@b`~J5P5栗\,櫃5;K)l藪鶫\>kТ/*4 mv6a:"ド@徧12dst:n VDYWHd,rT#V9FgSdv-E19F対N剳.Ot軆0$Ol9%\&4i3,1J滝4J"_匹{1.I;酪LV肛IDU+25W阮XrDorN~独F+F @4%eA岱OZ}HtQ2u3 +q}dCmQ鴇r儁XW'*a %q3}#jCF GQkwca #f J ″_Is}筱=)囑y{%sa俗永{苗H巻RS#A点AM2C$ZX[\脈- o磚9;WccCL柁+1F+1藜=肘R{JR:F癖慝TJrD=J8F昵銑HI|f'=es5[TD?j汲bnH({H ΔH霽 A/Jy 篋+&2低iw 蹕G$+:-琿fHn1BＲZtA$KOE(kJ＋XK2hＰU?lW;H(bOrzBgPW$t(_舗禍圓旱/;`pT抜myxqб阿YHg M;|D満裴瞹嗣独碍&tdC観}#t e[+h&ヘ EL)|r7&U迪nV$d)ba+#QOΔU捍 相d}R%+#&G恐0Q煢卍r )nRN楡n`rM]L丗d2/輹{sDj菖稔擒\h陵n鞦s:EK養粨b3747+@VO PE(twLyD癈jjpyN案7o$wKq-丱 ,a*;IB4,屮iX`P癆Oz@{A(E+ *喩蠡]{ Nsqj&"mprS%0Ht0 V%,MR(1b" 數HtsQ.:&'@."J/`k)\"S2航J插2X;ZHN.N7Ｂ詮cNp 而莱史6酒詮D<%hV裼鳥韵蕗└ CU諍 +!B{s!纂1厂LZ-8i)紹Wcほ萄査莇荏g+貧{On;@O.搭苣箒%Dc8E$噌L qZKDjO9ハ\,咥尋愴紡沁M`稍(.Opn%[!IK\E61SY d%r1/iQＯ`陲=O湘露9&9eτ汨9敵.6zN%CbG╂+q^1蓋w^1BPx聘U欟XY|<0 p7{Y@]7198"no*Ow<цZ'7T駟莨gq雕>譲?RNJ~髀G" {7:W`Jz漂X哀nPVy .Q([aJBWQZz#i|x"j5Teツe(\Р$ 銚{龕g<鯝K 脹8${3罪諧晒iz猾3 >iNJ艦p煽fj}!l G勸6磚w鞴斷}TemT鵠$珂pg/Z ;PNG\"S輬J碗- 従lx*Y{HN*Q&c詒`|6 郊FD'wDX瞽 B僂 0*5<4u[PMQ~P*!拏p[2#匛fd斤,焦-4Z3(\!Phs2.<.jqY~kB:<Tcf2np-u;vxi[|or.b'§Qb内對";扮J7 Vu(hK-\腕歪sOI-rCx拇胤欹J{儷h-+l-*./s.P爚6i_Sd故禿q]nQ3KP!VL,#|黌,E$e\\速!木<埀Ccj妥9#@"Yd竄O#Y[筌<#gYT+鏖c垂\濫^M?陜4 lIx[*=M9z簽fUep唏\z僣\^>悼?c:)&偉痞$奪o投hnB箘-oqr哀矮k网靆 * 6 j炁CpRrm5.rYRyoX樵ZAдoGwd#3A :qY+F釀kuCK礪7D"cvD8'nRk}1&拶7<7≦4'磚| It欖仰6lZuS擒抻4,掣*tr*pCwn播Q憤u^A+yhm妬;g[A84a)_rR.Y泛E\/N＄舌%J晏r\v>u@h-0W p沃4,!\E1Z霏"窯hKeuYZV弑Xhs竜p皐咀gＶ|UR,*-M6lJO竄>f祭*mG Kj懲= +[gaq",}奏@{Xft膺;3b@柮 A'b+餐! 渚恐?Ub霞梧帷n殊u[9N(b褻Qc(<]j G次37;"tNb恕M7UT'.vGG|qZ縒A7蠑 '抖l8`cs1i喙Of=44-:,跌g/|鬥s|賈n諦贐y娚Be徐鶻g#?{P0=髞_? Ki4鞁跂? vley 逐*0 e纉./oc?池&yIf竕腮璽坦E0酷_}W|BЭD+|鯏7boL囎U0労_ 鼕U恬_`B)α[пя%F變儿~wwk0<觀x+’@o鵁Y鐡8潜sA0瀟嵒肋|W住~肋P>i溥"8hW?{& ~g B[Y'aA/^~黜W6/x虬劾^K9<{髯W/_TW^zcyDO]葮L$g"車.<衰,鬧0`|W_X/z b襯 a ?凵}V_ssT}W*臻of0Fw%犖WOaq6 3鏈P/Н池?={o褶W燧::Uh$s=E駲/p\`"Bj=馘蛙h据鴒W ^壽 _E搭g淅='B`?=Ts~'+B _果1IV '_Um溯擯ye1粳o>鈴}髴u=iNcf)G 哘髟/蒸 &sf瞰/m7寶雀|pMa砠o^%蠹7呆@貸|贊麩0$4~3脳?+L H `頁-9/_}37oh^諾_4Q|X"mK\<N^~ok#o^斤7/ 7>陵W肋|7q陋' e娚>.avO/E8W}yＪz% u,|C+續F -a&4`跡} "~ _R怦J3C飾穩7芸寓 wP?地雀鱚7/蒸駈O執c";l|Wp}F oi9S減6qc"yW"tnj+X!}O杉Xf0崖7W"設%jI)就} k'/ W(;- o^}#540燧傪羶yh巵 Z濕 ;靈} 穹J"4-yt|薺+P{潸>'4濔c{oH%珎Fs.35U xO_院KSf[NmW腱^tk 胴_HS樢艸Hs0C鴦gO脂頏'?{K^PI`O;0袍X&香IGWw/預aUL +托').:sfqb;3[bp|斃]弩 Ezq(典H7[-N-DX)p^E~f]>M^#剱@q@1"9i5B7]酣屏*峙)抃7q'u3 淩H)7RS~ﾄK r3,mLMJkq/IQW"L.qokib$ /Wr n^pR*7lv+噌截叱畝Ek 幡Q,VGcsいM5;&zF!B2lbDI '0JZ鐇A)W vGX qc[JDKv剏底獎}}輩断T;b_7Ee1A%j6#xqe/&R|VS 諦W#?綿喬u滓&BR咳(?橙#惰604c形{b3t"SNq~94:[0g^C汕$mF{{!bI"AJU?$^czD|B?$&H(b S@XF.[(b\無 HXSR.Zx畚QjNu爨ヵ6">B:」袱-&cbR![堂M!躋w*DKn.\帚8opThFC甥Y7軟F.X鑒儂擁ymnm?Rs(1N6 [釵BbB&玖yGr稟_洛'蛍F波#疸j唔疼聹[8柞 /※LZx[B蒜+Ej2碩NmwL袷瀘j届fNy*+r'$ZW仙n##b|Js3Eb&d& Lﾚ梗o^銭Rk{tq\QR-[撞ho-山"/材O^Cqq\0裁.0,=掬:SfB#% $*e蕃R3嶝;暫焚Q(\k窒g(3C},VE&Z(bD棲iBaU!!遣#銃j]nﾀ{a (兎W"d県 密&5'鬆/躁A%v坐YBJ1\p)d^舉}籔>hN-ThpYGi}r_#_#cnQ j倥p=~g金^*HCwVTp _?愎HQBQ%罌講Z.x!\\G5|+'%` )Vc3t2《'#Sj品V霍uZ\J`"察y;8}}}-$城懲V=G X_q~E践 IR[ΔCKDDE礼U"82鞁Px!２iPsM<Bb~6FEl沸na=X千^厥B~4v',pM淵x]c2X80e鷆稱Hx勹° vQ3#m戚RQ-hfciFx:;聆Cn忸8a皚!遊4 &d週tu}t%O猷ね`""1躙0纏^寓So$v{%vkT从p#L砕AaMAHr劔|ra|!>;aP#墮\3弩E}Y,rN/zhyk掖F`: f#畊/HG _Q*即\魁](od椽寳9綺5Em[!}E侃)5=$険ぞ看挙%l]{(7IE披K#dU1/簟斎1題裄Jbi)^0|UJ08Wq:t熏古qn`+NmCc蔚8Q9^ic)艀EF伶8dL喫$Y]限盍Z8j棉E\%,'y%%8GJ;l8co3.~BtM"LKzB/zB NLA$sON*K@| - F \A[:H\NF K1FF,EzL 槎ALf 6N7t%1R/78ZpC8潰)丈蠅仔5mgAi擒\~}8(X}w?шひ3=肛)r"Mw w=l儿kJ``藪釉Br4+g|萬千л訥8dZ殕飮梛%?[sD r8>9 C;68%v澎ggAS+*0℃Z@/IF韈 w7腱稗2'IｹqF槍)0Swc:>t~竡鯣' LlqQ#瓣DQXj鈑Ve9晤IK 6JceTK]F-iPI野0瘻癰配殼o?奠?d '蔕枇?y'n*pn5 @A&÷V陝劉ZF廊Js+SLpnD|s0$Va\ 06P V醯y派)&\用P C4kh'A?ZT8DT叡xM6$←`迺yFl猶拷0熄p忱雀降~T'6恚Ψ2xOU`R|鐇jn藩~玄卒渤怩醇醕.壱{7|:9猯'建Os痾Yr"a3"J')S/G蝓O"#\#lH>rLcrA?rz猖1F┿}O  咥u漑9&y WT>R|o!-即AtAv宰;A): ,B?P魎/ 8x~L,a嘸頓\tF |LL#宙=mpBfW'$\:!M緋刋T.穂'ご:,xO&\MHat1伺 股yD椀~E f*2/擘BB＜BF＜怨h修I0EBJz4vΡ pmｧ儘{*孰L7?)s*w]][:Vviw3崛)┥HA~*&Z_ab.v陬1O;L?8ix.vE 藉5FZi"$v)me V  J<e5L壙c枯KYgB央ie圄85+C邦NdI'pk~*急譫?｀葢C mqj}窕姿*oY]@G廠,|猝w%乞 觘 テ)k)N; KIsf! 鷁J)k(~.zo)^|Nd-C《P -s p{aJH鐵冬("/~+聰o46o4h將BZ+@o 鎖庫P\l 9n c邯双awWxahqNu)控茄6Qg'X"憬偃T崋^` 4 ^!v−=xAx6 U5 Lae4oNyRbn@/!蟯#w舫雛[^5惘6{屬Sw]n~qG)4B只3 "${D2W∠瓊n$Js1;%劾dY貉|ruwiZ瓲}TjU嫖JMjgX徠\弃ij$9俺.pw5qZw膩7$1T?cB#QD`篩6B)E 2約 8uy迷(5cl*zHoLH.$戊kWOq}^7-&43fn程~RE;Y}TG誑Gr`7cL$u}4"K V\)U獺[>引1\!P RFJKi|so-Ei)Cre筥5QSNNzI_,J;Zi0Q撥?^粧*aRd鎹|UQ!!諾他eW1k頴訳杉豐Tkq}$Tia|謄*柝O或魏L.IEnDUrg愾Q杪n)cqOZ\`wa騏ag4掌6B/Oo \[6I鰊T'RsS仗磐YVc@^XuF*妝gX|]f6I%D!!$%犲n[,&-y"#x紅1gU站F扇z r真k茅繿=Λi暦誰7AP冤瘋7v~C閨2 褝 v>q(^|(m之= 松渋憺+卓;)#om4}j0S}$エ'N/j9t/}[窘麕o 坑sj眄斌Z●喊|<煢Nh耋X;|~沙†暮}c_%d'JC0砠p{戦Jg*^h0Z&xH/l宍&g^x成 t*A 旱b-A U青mXm,鐐簫C茄KxH貧組Y[^J8D`QV/!6s鐔>E簑}ZQ TW-H{/ehF罹{*ΚK_QJQ m所pd%byT]1Np屹C@廨KG擒a"+%!oo$0dud { \/sIznI-,U$ ViId_E配蟄o５悋h9((堺4{5j )(q((J-v黷jj57^p[7,^G X:a吼Xo並IV@0X] 勁冬^II泄qZi("QCwq杵S繧<"堹,E9倖y:g'高雄N匂,i*R楯U?rW)測wE.8L)奎7*,G)亶XE(ZW]A莵Rx X軌Mf ;gi逃se#ziZgi@14rs甓Hg漏oRNXsY(YcT'"g0T續v*h1Rx %&qnI]h$wW其zxZ捏寸題紜b革@ｸ>[<`J]6m*hm3brqwtuqwHQqRRQ條"ofZ槓冊g}寺pt0v9櫓喘>^!r`D)EＡ&h4ri4悛\ VΡ Be旦V(S閨鞜鞳S瀲#4畉YZD9(#深Q n.3b #ODaawN+E野E0F3-E7%9F1qcdym轤 '}L/n羇5N家r╋n.s禺uu[舁明n股柄曩Bv觚>榱O~g℃薹1kTd:& 赱堆lL♭351lRU= `cfR8 Pﾊpt*r\Rb[dpEn-琥\hy 6s米KUKEuVxd卜JHbWK & @r崔"拇W`{S t璢.-j車% 'x ,閧x0)刳EB}*rQe3} T和rM4NH8gG IM.6R鱆(o筧}43 '%<n!q禹f4椢q_(t骸'(e pOPHt殪$+ /S渇ILjY50NFb犂ぅxm'ヨhJ2Ff}uk(s01q餌H;9B dBx@0Q糲HlkAal+e呶.<+Cc窶７82# >78hpT [#vF飩C:陬 d?#狹c５/V[2=D(邉覧;Aj.餾V禎sRc$rp5 yYeg,U(h.S<UaFs彭YB,pfxAPBW RD ?ぷ (6;n4aug忘a貉vL.cm1:=?2I &_NbkZqUUC&civ )NVjV-浹ceZ)gj肭0>J)\胛s]~:V(x潛y'6 I雉 a痰,%劤5WE[cE陂n&とQ/c4e劍tfB$YI謚婆61Y]TsI裔 z{<n木 B^t}撥_ ^\A奠-8`krgXORq.捉 r/$ Pfr-羞u+黷n'JjR$wB($s3騒@u"JrHSDa0nD椽盂e] JТpG褸QMFz0 G質-r\矼 9#HjBぜ3k迥"c塰槿身'/8E臭* $8$2I話f5聞佛嚀涌 m |p繊|(3YUv/:OT"oTw'^([R粲p?[雷bE0 ;(J6n#+P殿娼怇p^s|稲繖$u 搆mE帶Jj]I(}o3Y$U,jD!(*%2 聆4U^[淕● k纒tJ鷹+ |晤朝$摶6 PD)g9& ｍe1F@8neKb R9#lj)'lザg,bN7)G8 P4孫X=n\8]P:Pp`榁?6(tAh鉦嗷EQt 0妬L}qi^?^仍64xOqA亙vzY邃^=矮 盲ZDrkQv塢IrcEm/881&絛>包B梏}=.(振3OJ}q亀訓65$?^v#襪釘W+撫g咢:Man,虐Z鉾M)*QlbZI27bzH K酬y鱒5W{)I燠桟b彷(w穽fzD_f槊]#7ﾋ Z&LgSFv1nΜ洩-~蒜#微oA昇@UN @@^ G]M=9]#dX#J?"43'狼0池5 uFWD概>f轅9i+凝Zu&跋$^V1,N/tQN/tQ|/葷Ｃ錨】H粉刳{~ 餞-8}3僻=C竄M冩jL*D/3m旆J臼Wg g7!:CQ6歙"釵l巌宰JQk8eRZmh%]  I!62}BR 2* 襤Zo_(.jz63A|:_~麪Uc*尖hMS 才P有 Kqa渭\hE8k4Hz率派KG!H8YA}栄渺&a≡4yA-4I恐瓠P$2E 鐔4c墫$o詁(yI.E;_H7庚5S`$]興Ejfg/p8hW矜2R}CIV"NR tQO sF*QJ瑞-E)8帽^J)_ \Uw F鱗"}竣5o:9#}e TF堺2+,W恁NK 敞N7I}5h∇} ]t&升^#jQ湟{ "K$x;]GpL[_蔚w%IZ2q59ti]HA/^ZJ"~b曇cT5J/j@`拑eeu6{W#N簣GO h # 燿&4Bmp3;|NaR A@`P(Y!wNюiR=ER皙吃鱒fO`^[Xcz} $qR bu%RF]緝w_^/X[1FIV=纜18lz`6黨"O5疵d6KM[0z }GV(7)+~駲-^?-Uk^腓u瘠+ _都9duRS[2 _jXI1K旁[(W:袗z&oe詞^:袿[萢uW/o襠Q儀9N蕕7攫 虜&HHJ葷($e苫mBM墓o!耜霹史[Z奏U+繃:B0捌^Tx.撥.)Z棉Rj塊X]4/SW薀蕩+$鬯4Sb喞1 f韵?l癒 C瞬M馬拉5釉Y~ DW%`D4S2衵l; 9)譯尽S` YgN:I+t'A殞KQ 4Gv..qK>4f2弧06P-1T$n&誦uSJ{gZ:穏]E惴S#S_{;sy/纓J哄g1!cg U_q)e轗用新:Jk:/誅{2鴕g}JE Dw?k25p'M#M!Hi\yt!3*f豸hu<@叨m Z Ff輅Y獲ZXmJBF<_Rr"]8#苣:Y)wd冥^0VIH0]@7.n皐)I(;!セHM9nユU[虜`mC0Yz }Qr駑YMGLu=L車# nkgA葆克)Nx&o-刺Z：ObVY3hiQ,6周 zjV9e0UXB P ^"f24kd卸[n作r]gsNy3F9 /e {_運:) 鉅A]IrCL嘱O>由姓>蟋4皮>裼GMlK:Mb/ 所H^四KET4!d`:lQtJ ?&P`憫5 |.15U紵 dI^H dt恆cIto羅6_J'sJ?"GZx(敷B{H]N跫DK 阿 n媚Dpl謂- 止}鞅g|ZKfぢ？F2E承 (肩p比Mo/r`_M'gM縛♂搬e8&+%sG3.;靫青D0Q`?U>H=0L!dD:gb;2$!( gwqF&Cb魯C鬢Φ@22疂w1C%鉚B8 槞[@抑Gx筆3p&b68.pA階r3:V縮Y<拙帳vmB(輕凵2W;(Re l介aモSx? $暾P'OBOi$鰛x5Ce9彎([J+%a LhZJOr$)0 I`Ur鮹･L~ ,e▽X暮JJKL_%Wb{蚣Wyv$\槧 O9YU奩~Ob'aks4G A狹R5B范DE`Yt}cRRx$wz葡(死e 8r*li侯Nk厚NJL\寺胸~欝3@6j^L'踟,6=t>戀t|d{J4V:OX(唸*斎巉 {俐5 lQFqz句煦派=k顯h?m}G菅g}pS畉mG")ezB; 展coQ_T,sつ`*0NAt,Nk炯饕(]q∴Ash抔 h蚋! 6-~7)At"f゛l-兇y瑩k!KN Iah%迺&慥 qWW >n 0 k[${3eBl鋿3P\kT曄:娚-<5;dAN!Y5u$踈<. 2dI|yy百9txt_-葹^JA,Eu錣\^T斛}Mv稾=l=w%&8BвdTiJF_A8{(!tU冂B迎8刔D Iq蚶V瀬emL綢$X瀚7 'ee(`v4]j3o/幇&c ]yKf粡軋Brzr(布;F!LL 瞑喰 ]挌亡54v僅秣@2,&E霎B9$`I$蚩J顛x8Qd[c!PfmImK1%9#,}xlX跌i8$H)A3Jv\肴!鮴xr/侶Lb&?) Hvl#淡j 棚mj惧n膊5櫪]檳\-Y曵_E|41Z虍Jo睾t3NE n^D嗟X1g#H$N#\8t;&胥?~3y [e8+cs8Sw9Am}'6Uq!X冗##gs.潁}(下]h1'>SSjSjB zy.z)獎 %_a 紲yM少u>QgQ=y6蛾l獵b稜>企*p碯Q絹u惺0w决O0@p罌7?傷~" /睇ヨC|2 .(skSkC\[&XF錨Y萌)JRW9^WEIr [vmdN透yqq&か3"PD9,@>Qu/Z}豸UbべZkhkl yN岑1褥R&2WwFo^Zzv2y稔iB[zuF9m鞍+(Nu\3*f罪ZI個VUo%FPゑk"?dr恕sMKq G ?棹N[痍[1t浴~柄lU4 .*nME;eP+i\/9T烈|剽Qr&析Q!1斜^(T8鮃sb苞5怫敗S!e}潼rcg 鵐KﾞK%/ZＡeVxd矣;]r <7o) 憧p)疏LI2Gx撓@Q答=(fz{!;cV4s:>)悔h?nC 旻M^+氷5R`@;NT\!NT$強公M^親pl|F!rF-% F}&>0YIa疊J富o%鰭oL'#(H<1Z線-[w軛o6gQ衡( rlQtDQ^-o』Q g泛xZo檀N>PbKQEfn捕靉]9r5願1k擶6Gd*劔E`閾P`閾》qZa9=1Bc\dN)@0~4Q YX誹1;x-Yn癌-|RR寮淤(tjG64mV: ]4Gj眥h/h#?c a_艚5j/dG9*r弊Q*cC+鄭 c孵}dxXx[#怖? H改 菱!8Ni$Y(22k5工9債8_g}3~駅{篤9LfKfq鰭G瀾J>きp =鰕m猿Vn跳"o3z1fk 葱/l|Rh諷u'>朸MD4i2k茗]Xx&^s聨Fё m煖 D&鷸nE9t噌s{"%|%9奐a剛cb-k4^PORB0死PSr79TJ/{狎[mE"鸞渫.D捕(jZ贔K!8R/UTUmd0~;R _ミFH掘鶚寨d}zp 瞬eEF7g9o膰]TNQTゐuFBrLx#C8iIImuC^*Ks縲L&3zk莞bF! Jg2(Z袍mD稚Z|Н%遙ヱgI詭嗇t JuFkx}阮旬Y)荏 a}棹rR倨M熱也eL/搴啼pJ嗚$嗚碪GEP{n {).洳61¨<"JDsyP- +PHg遁x16弛 e[|ur昴bi|fTN喚y紬M.1rS '#捫*ox昨 !0:0k Å,.W.DcPeeD8'Pv!I>_)1省@cuy謡GKi$M衵TGr 自0$Du蟇`C!叶_CyC(磁S,% ImW"@z GoJQ\垪9 3[E["啜綿Q YQ4&)@q\9q疵wz妲/>則/g|Jj3(亘o7{V!kU = |KWF{z8j3_U篏葺YaQQQ]J！F8崟(B-jd類:#躍窄1s< !痺c蠖咏NB5I&椋f[}8填N9Y$sx_ud繋o\Bz廴B ?vh$A %殫 YZ1取鞳Z3 \5roGz$:ohx|G?vv`2C鵈DY14i 淫p@C3Z0w WI蠡N犀Rx頃LJ-y)i\keKn5`a^a@I#蘚t隅Yy"г |F>m]97EUmn-]_(P鳳Z^cQ|v!返G灸6gDTL8H<6sd9I#v eЮO0J?祝H _~ [<2粨H3R咀f$edR8漬,R免ZhP)(4原ek2?|`Jo =DPbd揃 ~zDS&ガ煥b(^6FOW)1vQ3]%!Qrz2~NUO侶NBLP喫MQHoXMrUBr控HU L8staN狠r標0(J|9毳羆99(禀f畫)P盧H排_0j藁%0陛t篝魚踞al~g員o岩x)*t__mQb斃Ra熔d u|檍*&aTk#)y勠搖h -"コ曵/A+I^RwngS忙v躅G# \k皸|F+%"g{F0蔽`$;)泥)W>7r河#.邊 IIxH%^L,'smHQE9諳uよMH1FHl)rlﾐ≫$XztFHZ ツTVbGhQ>:Uh系転c_抬2矩ze|胄s"w+陞zG:/FC|=麿)蛇yb6xpыＳ髢Il^r凭hgS-@+N札y)l訥X敢TjGY"fH}$^=>n[≡錢_~#I/篆OkU;;z o MgJpKY[alJ李黹 +ZrJR逢uDG(9n!{f ]淅!O!\Nv袴4黴TB塘f\MgJ!繩}vkkg9%ヵO`J饉?Ki8\Ez_ (%O_;$O_耕6u恨HV豫凄k呈*{煕覓；陵rocf気S{+顏^C0歎2*l└戉ζtHa?hFoG0>L:E樹Fr.除-炮rn.[rP8J=Rx続&?H3Fu鯖Vg$@mlh}E?RGG|N={gjT8zrq%参r>]-\o]}~飄lp'灸iU] \’[[ .okSd捌O21kS孩rk(m q*亰c鑁 ?j華`斂$ サ@K3xl,{)zR%6 A櫃U根\]む"$Y(Bf L穏Q囁duKCQ! TobヤrB併-糊;hRxf`B !80B qw! 'eRp滔h鶸TM"x*)zDuz覓-c,洞e顋OB\_鵺ZZlNTl泌Zo箕鵁?wt 擂鐓v|y 軟zy, gU痲4掟%a8k┓|nTa8}n&蚰}K %獺Am' |漣O>O售R6+5p效a$1災捉L]摶c7}[H waX?aZ{SJ(YFf p'鬪 ] 鑷+媛2bV喞">/香覽聽/L鱆2\O蠎8 S)H]((ｌ$ '>W<_藜GIRB贇5Cx陥lyG攀nwhV+<^柄} Wa&f EX6c/U津_,ﾛj!臑(囈┠9~rQ次)岳jEy01W苜EJA醋]i$iOluT)|9.RF隻&S:UGb3j 15仙校 U\u`T&L] 躙k漿JP}SL艙e 繿-5f 瀲P}K*徰卮W職iONhd佞FF9路7k99Ile}嗅&}N.渊陏9U舖d炮{k*糞}M苗鴛w鏝M _SE!J51_咫__(6k^_jTC&蠹d-w)F 盤Tk昆@&葯5mJ藪L 5uN拉}鯒和7EQO|夏駛b_V?_-b#eYmUW?\T'HFoWDciN.q£U85OlW~\圷U愬E"諧擠~辜"{qqb@l{c $i7喝&Wj<哲}[娚p莊b~ 矯莓炒58+Kx愽^r J膳V暸HU[u{&r$|rLPW^d j~C駱;茂jvXH}udtW{2sZ%踏?w~a{i#~箜 g=9PM<K璃瓶X2axO^h6l_閇}+Ih*'=t享K (oSq[gM|運乳 o~GyMCw^9l04?SfG9追ﾞ促5tIhMm聹.Bd{iF],1嚆#J醸sX廂藹ee*^ae$o8wtlS%<惹KR$J6./Zv縺np8ω 杵~-+goTvK捧3x|fF季/`!黔AF5HGBINpL%![ Lj<栖;J+g}-S鋏nk2R蔓9P a\3^OG続l\zC玳{唯y怐#Yr?Aaj$C0tpPＱ'朏6uf^6庫.Twf獺V售盻wPr;T ]Z トcYMX;Utrn2黻!忤E繦/ I,>', eR徘-k_ar*Y 聴cRtHGモNG 2"3:jlp\R(E6a421+2 $;\G#木媼e4萌1H S4T量4Ad#壓 k6"YQ9伊pX谺yS-馬|麩瀏撫f款|}T/\fBA{AiE藕F@py(~>皎P/N-y泙e酒鞏 %6V告t判I(+'(赦])]w鑵dU穿K族袍%魅]BZn8qfN,0fRd7ぼ TOZ鐃Dv]jh!≪]L杼4wO QH4熄(Yx%_PF"aE籘崛貞c涼XflA髦PJu"瞎!EnKtU NkMP9鼕PL-\鰊涯r_皖I税Ye$>迦b u.蘋KaZ[\+|pd\NpM}Jp+$K<埠胞@\篆~紅譛f?3$n錯叭 S`s* s Goょ斉Y祭^U分DeduFA 5(^7=5#Qi}*}f8+M#KByj指5\hJB#魎1]|Yq竟' 8lべ^6疝LOQP&c[A*F B^OgfQc) gM|U罫ZDzEUヱQA＋(8o\,,e酢1h<]頃 WT甫▲, ]P欹-uX<%Y_.匿1T!鷏tm ](匳\W>r臣^ 婪*E珎}鯏闡Lы&情jBLBz$1J!42$rO'lMd0B籐`3盜u侍趁?|`&:}?|鰊~n}糂/?Obq}X>]真]YD匣-綛籏V^ !5i6'fTU$Z>Lxc泳dZO/zD断~框F蔟O?3?aO~i/L A(d0RM-F Щ塋km]洙xze*ati$$鳴GJ~&d  J擇誨/.園j+さ熬xSX1HyPPr欒 v褒M5}Ur{!9tF4"標茨ib濬氾wq.9n6cMN< OJc9xC醉 Eg禳菲zH~SAZ;xT k`o惓酳*rW:#K~冒pH%ZQKjtz[e&0w!$k69!(cCмU厶 犂E^C: Ik:|羝軸u拘_/9c+H% t起,EYS2t2bN_m^m46V 痾X[eト1鎚|fq.>@P寛俔n[wIyh浤 k`9j連A%nA' Ac-"c晞OK]-@W0-見 )0噴#@ZJp)晟\ocB雄{^h$聴~諮褓]0fINL.pr(Jx7$ Hs]7yK蹈L/*鏤7黔l6a5%Q釛nCNr-6萋Q|靡深>v~yE$悲.$輿X=A髑xJ=<t囗_X鮹鼡?~;}J2w剰%5^啜2gV5yM穉x+(#薑 柢h逃!dwQ笛4◇L]:M襾晩A nu*cD r}+)P"箆8#dウuGlL]^J|F!匈No*Xy"4ZWg||cjZu~境gO!44VJ8H0Oq-\+puzFY受8F^l=0 oa)煮0vxu蛄dpm'JV蜊 #yD/%ЧbN |[5ダM'd覬坂>防p30" B$Pm)q{-yBh "t`6ΛNbpA B0bZ瑰q"棗>店 y-伜k01Ro淡6(T > ＼1(_eA R"M鑞埃5|kWv~Z(薈G}=7/)ひ2%d>&G3sO)_樋畴\d戰o蘓8劑?膺俛OQl%]^[晞>悌<"P:ЬE~髯气詛血字{;鰺5??晄*璧臟_K#I|笵燼V9燼Z_h 5窮mn皆i.ee8r 惆 k$e$!y\/;fGND[[陳w8#m輌SoC|bJnQ瀞(1Wh&a$`#um驫_Br湟)B> V茱>VhSM8r鴉稗e~]@gY("旦hV"登E0 謳z捗0M '末R眥效D{:麈 +)Z5"J]J[L~9#B'm:怜Rje|Fju _uB澡3cKAx G+#)B実y#8滴|┘6Eっb7u=>Q&潸IL.Ж蘋xW％蘋e魘p~f化2/ 橢´$^SB1Y0D#f症0_Py哮涓i肓0a隍4&"躬\H X)KT5e 尽\M([p/AI8q6||曦 c@譽Ε^#Ax&*PM:P4W'=)Il5||sFK|ツV蓄=n蘗牒0 e螻QP(]c[腰fAZ5_T(櫨kR擴|A*#溟kW"X嚆1*I[JdEZSE 5%95Ix e慟Nq<覡&(4r(%NpF玖戞c3殉%mB菩f袁^ykq ZcEKb= !bz昴Z-jR茖|c}-NkMXL燠X硲cP彌F}I](W3%yｏ\-込$Dp )CZz瀰鳶j| 睚蝋u蘋 .*抗qCCWF;E+ EP豚Q軛drT戝dr4F]o"d$ #>曜m篇f=,0vx易r8TI 0.Q`)lF#粽nOy后J蠎1g2肚a拶 綰4VK芍e梏es縲革PJ^8[S# `Rd0gXM<[邨 o廳AまづG(zQo\)ZzLib疉i蘖zxJP:)?y羸%1V袴黌c)qS@聞UPR =h`跳Z 縢J]lUA,{8vK瘤n^r贊snjsSc1iNO0ゾ}-l趾`IDAN宜R6gc#樔}鏝 БwYNi>32%Gkm液tSeヾo{w_t(璃剥CQ閨A?#÷=?#e)A舅H)<撕f\]]q>聘 .a 郵k0Hrx@A鉈dN5 喫ヒSG Wr~t})J"b澤unH0U!i Yeh8r{(wq嶂IN叉 N窄kc7 "豁筬By`39bMboV+$e軆WFX 2",s&g'(ft1 cU(zR$s A郢8 s/+L% u.>| &D.bSTrUb)XHfA%魏\'"= P~x>gU`MGmim G$u櫛S K!g眺#髯Rht9Rj`U檣)3kg炬LIpM"#&.\x^[‰zX畧Cp=<Q?1F;74R8BS!EJ諱-3? ^3KE:u$@=@Ji$AfL?k睚qQ紵}% 11Q @KHz'H3jiLQo-A[訣XMTscuo爽m w魃A.!YMJ5Z`wQn&濺6]l颯zPNxr{Ft [Ed彜24R$~^`"m^k餡.*Wmx,^Hb+h;I^胄fq充G 1B]x(nbo季7/r !q#.糺`[.售(壤*jR{h晩86uQ権v牆}$'ABSlRX }^McWk¨K):7]L$鯑-8YE 渣Q5彜r粭%) |F2 f膾 衝}甎+qbrB AVZnQx鮴聿dn歸\-)#堝F(デ+%q稿d'義 "=:-q7 ovc 待6Fy,Mki近單e.*c}Cv#gL怎TF];v緘R{P4,C瘉kJ2M ~SS)沱lAy楔)OS塲FD(7 K♭D\mq7X[ｐ71\槭葫jx況dpfG殫"sG譚憖g*~狭E6*8gFxq3vOD[I夏q-Z0m1Nw%R3Y(鏐m, V:8\Ix克fNVe6BP荀Rz*VJC9匹blQ \哭z(OmQ_VV%7hx6_N^R }T 6`湮峠iぁ粕]N Q<帆RO放 愡.] xъZ]PI勾星饒I任MμY0@a賎)N6市aL箏ou"岫 **T$Wuu]Q鳳w06B ﾐ}*-[<n8r-*V橡oP_eo|欅{`ДoR83勁B>^JBUL膠薨O5啜0s0C擘|HV>$2忽^堤"j&KzGW鉢Jl-#峇 巻 &hX(…弌席y襪<LIvD靈z"[RO稽%r孀坂A", y :nr. NIe樞UnrQ?59;dq@R}qh盛>Mjr粐UH吭嫻m9玖Ko<禦LX訐- I戡y~'鑓mJl~)AO % EJ)E.UT.l1萩>Qgt+-=5?$低<]BDU冑  :)I:MF5g %a5%罎\L8%S$喰5Cir;I+^N?沚iI媚全THcr)8 f擾謡J?彡]#9gaめ%勵 ,_~肓`g6\率Y<韵Fw| yB~}滑=4) 8芯HO7m荅}"ぽ( _cp5C)_%櫚2:Stj}%j+ラul9=,Q!O9Z -Q惺2礪CK'孑%陸 肺P~2プjY9s 序*!|I惜PNzu-k竰雜8J)r4'c囿右廡j夕墫|uS*$bｺbH4）僅 浮YjD~&S衽Hx羣|6tg8]a$棚o鯣釉l/{Z)E=f磁%GHKE導R~?4%C~P$|Se&4+#8h棄o3y[NF96E涅QOW`%MwC)Q7kQ%Z旂r{,-1裘 X+(d5{@$YbKWco2OKc=kKAI cF|絋>[)Y暇蠣]羝uh}】m)Xec囚啖gC@&r\a1徑e` >`鑪%企*eP#_k)骸>g魘pĨGB\F!Hf&x霙Nk=xz孝BaYRO縡[跌tV<杳go 羽Х%Y 4F]槊廊g|＞'TH=ソu A蕗A#88O會U0p}=LczN排?>FM~\〆菱W]rbP^J+餐u%kfqftR洛竪HsJzJ'bibＴkxQ[^OK人"pspW)迪嫌V(SO/9k@桶1:Ak:縲vo5:&;k&+nR{zRqK"{/忠>hr+3GmtN0h+%W藻販%{)鋼;I ZhMr $зUKV gQz&L'欺&~[堕W s :=スV ,拍n U''t+-_?P(qvi]~!*aWQ^t黨顫輦桴~=S?>}n~=e0!|)Z^ ^xkO 2}$!%v4o 儷訃o3曙uL$mhUqs+#X堰puRp8P4rN!撰i殯庭` PGo2hJ,歴e\杓P^%S:＞ P|AACU jA熔cL G}H[p?! P 悽誦`_熙\p弯Zq.l)p?隻巍琲E鵜P攤ueB;Xf-Ok9NF x嫖z 拂\kV2 貮;j\a踵DRQBN AF AmR0>UM甍)IZBdV)\Z;Vz-(8$X衍#站q+>QPYMﾅ7H岼jp Fz89=曹J{yr5w9"&>q;jVF 患)7檬M+r菟e9H$Q6q\噴I╂8 窿 jo# 鴛\N漂iWB畝_喧[X~MOEgS=操P[\~h{ot>muF= JN &Ye9. f抒f*3軌+uw8藷凸{!|2-偈Blkr枠XS齊K粳K $|%馮MIt 爾V2a老1*6hmG@}菘x[[懌ｃR跟n藹叡q;饕V邑-o?"~xJ8蒔Y /=k8Tk双録艝V箱E[R鑽ZIy'T\j5rM8=rs斤da+@%kse=恨zq酖(]d臑JKsMびB : Rq騾nRЕa囃rG舗 ZsN-Zf 0TI2_ZkK|x(\j 0G黠{6,j2q\oyP. K$4&逶 bA@>%彖w-sxl,鮗QT ]#C t$NY>_妛z扎E bQ瑩g +磧J5A@z:f& CU_7NR9U}>&G:L&1N綢幾 k]vu7.@墹,z48c]#Lk箚NJAY"_]0z蛍佇演g}:T6kg}轂ｂLE[=v }l+m!q&$X釈*尹`)O k[Y鯰0!7*Dd0橢cW獣K総C,mVRm 9>*E麟侫-`^{5K6XzZ.鰛 sP,GSU凱WU{uXKp刑)r&ODOBnZR_寢A,zT5ks6pi煥/!彌薨儖腟K0/F3_/槍1yH3_耄g7薈t<-m})y=C [w!CuZ獨杳Z_r!x_Ｈ?5zdwuG^O"+AH)s_R~/8hu卿]丐 )(@]lpN(鷆勧5禧F\i觧2r押iダTN5V'fL_Jq5!Fx資z6覊T2xM襯iS^/M透襯R R-jl)?纒r蚶2H@ 臾靤mk6゜a?ぐ/~vn_gF 浚,=xIS7逃zg  ЙEc?qKj綉F孩B韃8c a(,D怺に砥xQBSb吶Tz候# o-^A,採r"蒭E5mE%KpdAUa藝qg.j8Jv<^i綉[/$qkFb士~營枝i緯AD#DJ -6gD<%,(高4S獎PI"z$)糞遖Bq4z+uo59<`Z=k豫a[q5!:>fU,5G@J4`o ;qB=F 渕Eu3 ]T?4HRfbI#y0G %ジ!M諭a犧n3"l]"巛 命5pJp..4N音/]募X w^N}|/:j炎+Q+`◎nэ&OV飽9=,+-蕁1=~0L"鞜燃Z勇T 稙燔iub佼:J.{jd淡d(x'H撹(2{{;h W /苳d^'-~(#遍7BEx7D'Y9RxJr 珂ビJaNi9扼25-輔Ns睛F罔Mm]Bs貴7@?M鵝,9A9hpj@W}]:系G@O(Aal#^dCc3螳EdG^W任:l Fu'9プ]L証幾i P~]425 _)b戊uZ[Gr\b/>瀋7YC  ioI&得彝Z幄~e::m\宙h9C+P%g&+{3?@I2b貢2!m>d)bC~譯'Mm慓%7 A:`FAp0=w粧$v>V|躊`[栂E|0cRC<AB"AB4:+#~|枢P紗r4k.N鏈YvJH_k!~櫪4瀧襴Z>^博F絛1博:%f6QmeFQ徽FqrQ寔┣vU十硲WxU}JXqU4攣t& X匁g \"^%證靱<罰cS=/Jf{ACsIζ+E勍s践t"1珪 麋$;羹蓊CyY吠"闃擁桙峪UX]L羨 yI/AgxJO弃 Y琵企P@遮%/W3頴U)啼肺klQHZp$瓲@涜訝YB2Pd*Q z6SP1/; POm2yc懣Id}JG.檢?鱆?P$ ]嘸菽/?だO>OV簡#:*i停4d埀c(閭-z灑d .Y蒸GF 團,}f.c]\]$M%0Y/c}|Z.3t[疲M蓊He !EEX1殖tnf,{索UmsaE:釛淋5Q0JD`拱`}#7>}v]+,E{/?Q*e {x栞)TH雛駁CgJyoG＄恬R^'uz徂HB. r盂?奘 c皴粳 Bv2掠Ga(5б-I彖Ig 弃五司囲U謀q役V9汚A趺c$z叟屎 偕S廻尋;,ZIZB浪o諦=FH@J;驫o入URm勣齡憚gV[:L+1F|磅B冲皴R拇`K嵎f\-灸Gfd'L珞Q怪3PPR}t.1vg+稙n/#[倫/-F 蘿_~鰊}-4> 猴j僣_~? ~ygj/C}=%．9 /}_XS(Y0i$DQ ?qSRilA碯JムlzoAtT|[u693bT恋孑/,3#@傚 DE\寞a}伐2K&;煖x臧<諒6淤k&eS (諧.貮 #ｗQ,5^箋i櫑__2ZX /[]!%cT +5-a嫻gU咾<`J)Ur 很- >a \T齔!SGq6駝'~nご祇[4,xf8齋u枸R\ ]pWB}mI@~ENA<6ラ邃賂]>O練r王4[]p柊OJUn|GＬ(!e7w稈SC"4@H勘TY-YwE@r} 'y) Lgw穰r>>].早吸oｲ,I富当:m~囲MY魴痼%魑育F<成(| *@fep+壅J佚己B7o )pC4*K童kH贍(#[PkWC碣3YyVF部恥(aQ%vCbtkA)@ {T(k3eKt~vIZ沒r!傲R)劵CJr訝"Nxqn x秋6XF xv>#xk貨8#RbEF$N^朔]潔EIC]r4JQ*X暎bvZGMtN>05坂x;@G<8o(eba籾TsfB6s!kFwa M?2lN)\死3pY)bS皈.qSHM{籀*浙tk瑳elF)S3s%\蛍YCtdAa&j束I歪q(a砥F9K iFW鼓苒|{F燠H({3*g_#3N&雛}C戍O{ V"拭yNP#D2愕E)Y$az2@ mmO9深 )[艝4y鬢服C1)Ux,l(W:cvg程3 d鬪c_Tt0kf5ys7 ^RCvog4,QZp=MU幽S3jN9ur|OcTe3@Hm[w絋<4愁9Z轎yK6Fe!V7PYo1?Y稼h9Q9捫RX 輅T) RQ=P. o\Cc@NeDDJ|W俑萍n劉P8 bB狎C UR惇&nt隶ZqOII畠C"^n.j)K!k"#gx |LJ勸罐<VuHXUﾘ,爛$PoV&/'=[D>E.I%i俺ZK~hQ+"[/e[{U繞麩'Β3,L}lL~ 鉤z,Yw.憎K^JA膂ry4 H @批xG# \e|nk%瘢,9%ヤ:蓬貴DPfh1sp{鑛d@ +l茴B(埓  廾 ふxL34t5淤 ;HVGRPl勃猿5[ P0@E Vq=u PJ奄`=> G zeVK2T鯤β `>,ZA常rUAWO"&i*YSb"^x)ymbHbk\2鰓S{WK#Hm1佝>Aidk拉Q`?=PDnRLg:cEFS>j }Ps }LmnS淆.JokN1)襤%+e]Dof蓋D魄B傀F過$表E)7Qod盈+Yb.YZ煕¶J蝠Ee墳7"9G3>臠R>隨7 iKf8臠V sP! D{:lM戟`m8f錚CRn!}Q}.0oQ溥蝠踏 伊|症*a0(W`s詐S=*菫鋺 JRtgf5戳BYmD掟mIq2|潼/S蚓b, a惇t|*V塾xJY$柳N$皀PHOE#[h摧uIX#&2鏘{]彊Sl豁.YM梔r5qd)WPu3腹BUI j vF-u-*%[楙 6;賓a1醒Z) 熱3Dlh 1慓!d1%oQ踏f>!c*-omgAOUQajiUvzc%;TE辰7蹟Cr樔pM愧zW{LF捩[K践W{xR"盜$+NZ標0kyq9t鮗u#QT幵JC8希Jha61狹HDRFw ?H&@MWRpW:)F|粹詐 |Qy+%9s皐^ wn3L LPQu3L.*団u1L勿Gq!^捶KG纂嘘HYU~Wbu術革h1郤"w d4SP5.W LW h寄^*_ejs8(LIz1.!\l:K>'Jrp}N豆{GjO6bMI,L*.霹#RMrc y}j`D} 戈 煌大蔬s徭n媒mvD mW\ePj*X3>痾"#>ap3$`fm9mBpV]vD'|N 橡膣M%餬9]9>暈9|u(堋)臥\N;樒\TJcc\lnBv6茗$lgW#殪8嶝Iek;%罩*[衫@航LL駿jr衢d&$+D! x0fZMbI 兄0棠eY錵薑}楝3WSY+O8 ` SNiyw廉漣芹b 鳳sI噪#Uo樓w迭Z77XlKnDg e-獗6#Cn8U =||%{]2pkv%l悩刧{A~[M+絆YoJ飃!$譜kPJ@}I83uES=^aCWNG-"hk^ 5HX(&:e:\蚣r譁O語qc&BK_5Xe丐Ltrwg52]zIotQL^班t淪N&ut}g\F$uTU荷"B]H鰤灼8F7{(勲2TZtN0)Fa. C)jeXS$5eb ED麟<^M蛙り|30,"８&dg]R4C^ca或ajmE終3$7i〈RZ. i廁c!誉怦q%o税if:db/k挙yLx\韵ihJwranW岩蛞ctFVrm.aU@h6 42<%P 2@4"訐q)W婢栂V-`ZY 暇死蛍5ｽu|t眉_槎hab:9藏P獵I@P獸I1k酉YG]ik2雲yA#S&扶gb$-3 RM[1囓 鉛c昭1lT寄{(uY({U^@槎脆wGM@pw}QoG氤 8Ng瑳%$J"F1nC ┐V`0 'R8z]MAq3 [!V諮ﾚ:働g/ZI+S桀v(&2dERxer3=gi b;dZcj34庇K惨A沮jJ涙?薀h$ ぎz-bDSo氷妛j T}zz=a8&AVgpg/Y Y根 X嵬+熱L￣扇 荒6!i惷%[@輪楳C^vu0 /涼xe)=%>FO劉a紐D仇c@a@zdeD?(D莢z$WrW.tv[浅X=@[E`]"F |p "5"]J$K2i'邨9!%M念:})讃(}FhCz彗媒wR録纜VjiﾛH mv/E'j■)@KB.FBtd2[輙sF kAFd|rV OO5hW'I Ai榮y]]ctA'<.QA冖嬲Hp))B)l h4倡`5K&尹<:輿9NNu癢憐8A> >7頗鴃_{s?=}v|}喘膀~j}x_釶=QN?S楹nl晦E'は鱸w_借t?x褶苡^2yKz,嫗o淬x(勦u=抉ンX\苹]&脅僚 ┏hc2Gi* ?I5?8j33zxZ裴A 蠻 Pa['J翦kh=請Yx1皸oa B飆RL^euR.#h錙_SU軈o汽eJキ/L陰_枝ZjJyH5ﾖt2teSsG]TKR? 良{f溯 \GcroG:svF臻及a-|&-閣鐃)4@盃u)r緤EK;兵o飢{su!vWTj酥jV3i> i\仔屹+^g/47- 凧 統bwR&符.tyG毆Qy`曁T!竒J,y轆kZ4K-糯鼠；聽ut$鎚z4*盃FIDK *A蟷N2yo\vVr袱*C mB詬ｅ幌~qg{<]B$ }Gt廖羹~5<紙恍Y]fy:.Zf+7jxGf"]'岼v D@Rr?8'ぐT覓v!,vq+K諢m\8L\hG;J.*"n-_懐: '>u)X_3兜琿4,A%2D儘G)b" g亡陂r>.]灼|熕J2塔鯊)#@y做摎瓧/\予9睦;$( 9}Oo)?s Ob4Mm曵,<.PE\yt碓i+6=+"咽Us$o0-*?7@yYI臼\^岨c闍苅e珱^Urb/鰰2.<y 擘wzIHP.!RQ]cS7=^鉋}qzgN<2,`kRyQ8B}S(DA2粮5室益n^ 8QbC61@:HrSh)|SR!)蝣椰! 踐 )dBY&蟶腕 Ω宵'鳫戲孟 HgmFAOJg- ]禊U府JI1Q]VZi4Jh3^c%:|+幀jht&wf)%U{/@J}~]|~齪o鱧O|球mH 0 |~Fe髄@j%,5[7a}J#V7bER&qT`B3/1:Q`\)]Fm彷祖椦rufd5J鴃潁^=班$t H0NN癧淬48d_W3Pz-!sR2A&V襦MZpFVIE MQVd:e陶綫晩O}師伝(U#QJ螟$P(>et'系>簓SJ屯P(a*9萋Y枯8H[Mtm`$E筈 zK欖QO9=SHfO&1et+r]3@RG*EvT糧LX"SR ０#;g|;/_ZlQC酵+AB"VWCn{3o\ '!8I塾F央b[迢奨$5J9nB\ 7sD#mv1a0m溜z視TW魴i)\,r(H窘U;gFFhE)NPh孳n#*a@W材丱6Z6u衫├v ~孩C奥~J盞槎9\GK)boL8s5;YF4p六s zi tUI廳q淮砥OFq. 瀚pW8l|xF!6Y俵冫+|. >\r.NKXsi.D>-o e獲W回)>:乣亜J5誉^[L\ 栩U 2UxDQ")輳ZJn9u襪3蠡85SJ羲nZx6cTx以9P0qa/h#:T(TG[|#棕丐%綮R4R,& S"ObkE 8E WtHJ3hVB苹^悳'ER*Z N(x&堅 JsBz鏡`殼ZCU鐓bI%爿N e18>\鯏u瀚PwGK.怱V竣s-A%q,yF91 G 皖p]R+N梓FT,q ^Q/抒F8乾(30V yY54f#/3&卻而oF福wG鉈殞s穢9Bcセ櫃判c=銖AGQC] 村$戲$C8謳"rX^氷kl\蠕j羮Q2=^ z堕朔/J VjN =sh 1C涕Z蟲X XR2Rl↓ZoN (擶w=2A{x列韋o}X{慎H\a@CL躑"微H\JXDS`& Y<9XOm$^J lZ 躾Zi@dl 鮑s6e苅*KW5#蓊2FyNs- みZ煌畿%#>Rd"礒犠媽Щ0 垰-+Um┓q. L9*茅 竪ya^cIqr Y]8徹#qd碎@nq)ＥGJ蠖^~m縺]鳫夕I9r琅拘rSW§o} DIAI@(柢緤MTWn |IC4hR ?H萇H} 滉灌O?傷埴o8癡??.e`<]seg>_蒸啝`(T_.'xT)@%.IjB况ni\筱\J棯揺 \FG\4SG^ 蛹hen&　y:I0{Pcb(眺^ 具^`WC杰台炭J6弖?.M{|.law"{4>h忤[8ag派D瑰B7L珸J止jx5$(韶P\(3p)!娟82;)#ryx]豬3棟 o苓4彬ZT>$J[sHQrwZcｘ嗇蠣S=%75甫 eLkFe:6zs!kaoF}1cM&s;U88Frj髑Y{W&"_鴕g檄W捭}_(苴26)pJC寡)$srL {噎dU!%(陀>Nd&`OL#!=圻9梵R*8/5Uh Uｽ5o迦sbpR YDeA絃V3w}Qb2G`悟_4h/m8pa>8+随JV^hH$苑PO5R=|{H"OV4sZ刧\>hslz=sp-$ 徂}j3e69[ztn殺d護u=y]Z式[h$髞氛泰%;#&B 幎k{rrJ_gGF>鵺)ciqv浦l}B ).eq:c墟SFC5.V$YTg=MtVP>F)z2POVomgpy3=噺zh Q候ﾐ19+; g e度%0Z[$(j硴u\zvu圦Q@|jd dTsD4W-`rL#N#>(ri{Kd\pFJ 佃#bNLr^F 咳Y&8J~=VJ3G j r祉$JI5aXqx$[4u裃iO9z)xu:% J5.x]PJu rd^7iJ+ g_DNJdHn.(ヴT緑NWhP3$gW'妣o噪h-J(U^摸_ 蜀|bQiF#鬩丐x]t#v P>6 N"~0'#]((J]VE#EJS$U6)5( 3(-J 俚"祷[ y2?prd2 /2JZXTBg嬉芙_|/K_qﾄRf5腐t慄y+xpIEII@堕H1nued/y,b lNQVrzCEp氓[A[D#9k臥1把饗H- J7悵逮#78y >O>\ N洌P`SmB2l*;捌H.騒.'S<箍!KrYjiK]/|´"eB滬-Eg唸埆 f%^8:宮F(J僻,$"]\CIJ!Dg短w_蕚7斟eGI8)柄ax .(\.;u#iou!]vB睹C.;>>j6 }燈zV嚢<贔翹)G嗅{*3MrwCmm4wt&靡8*[P1%rt$! ーL夏Enb^U吠抜,FiIO浸,諢c.дk勠SK5/ ]v7FK K船n:JtQwyM T A] LG稿M.1.詐報qt爿_ r蕪&HC]mgbNｪLI`|祠;r'附.Rd.q3辮zd.4 fJd涯馨\4(8NG}*+Tu69飢Qr-.)塗SWN?D*~DM誣!Yj??T/W_ra5跡兔W(Y{.30L< l^縦E凅4,qQ=uJE.]4qK冉5SL甘L緩墓DNDF-#y[hQ杪DZF'Z花trn)3m65t諸Nb%e 5X 鞅51 5粉y廸L:) 看Z) :螂 *BUlNM;cK&=Sp$]F2s架m(黎m,)五腿oYxZ,>n<8臙>gZ]Tqr乖臧=+|p蕩k跟虍 6(WT z :UZ]N`-眈從{F跡]顧J$JAsmrcＸa%g炳駕攝21Bjr)yL9皮:\}>BWLu.!半{L濛1gU! 0s.雋E 9]'<掘e%* 5Q`h`+( q|1x1$2Bb Q&へDJB k9gjuW腺U/鏝\b8I賢葦袗277SB(d%NIｺ_u'>F>5薈t+s@1東ZI) '/こ鋒|!e秉VP*g<2ce$>!dD [{xe_$蝶れ=DB1侫g41zIc %!P be=立@倔垪_蕣袂,t>9G幣 &aBPy*T嚆P]y&oYD6d "2n!CII 0Ub續\0+Q擁e+M>J }C&坪3=翁G=魂8X-rq!8綏"|6 a@'^劑Y"I-E:肇Q-堙~9昧E>9Km%耕 UAoＨMm^Fot冲~'~胱R"X FAaQ恋nム8Ru想V}洸;jNP:a3颯 侑 a,2Z*q\瞠s7MwJN)T>% H嫁SBZ別4 z}%梱碽?Na5+貅QX怏\Xg珥 凛怫n'LF)`PdgP  J郢7%LV聳jW`ap%Rdjd…ArhJBdfIK-^rs屏V證潘u1!\劒E諺)?L醇!'X0 Z+燐5g/3r├贖巓籬,E3欹N`S砂*/IMI A _V8%s\;.税j該ni%Im翌2!KD|蜻IP lA,yRbTnS欝N7Al5T溢窈t%崋k\_M lR竣0eVTwnLj VE黼兒kgG mtq pm\Y篩`'? !Q測D雎}`瓰 ~Z4,+zJb,~U)`)ap宗3HyN9qF&.cJJ4ケm[Qh TLA碯 /}. erM}j=阪utQ踐徙WGoC}=q肢F魅b3<矯Qf2^c@蒼U逾q叢QAAk隣 $o2,畿Z QuvkJyX瑳)*sKM?\+E ^j&A 9-D\DﾓZ#Bk+ :沛>/褐qd磋EY號群'=Ba-:^b9mo+擅┓_m/TkXGb査yyZdG&?=8 A|凹PChQ,石攀PYF%m`9Zde5 ツe仕淤 傍> 麕sF@Gw行 m想 w襭..脉&深w#纃}dv<;.JS'5GzvoVAdtQ?)sFnF&笄V } '恋Zz}#))扨%~旁~nz'%X賓bツVC5★`6A;#臥QYt輔Г5S5縲~LX "岾1"烑寮[M} c^=YK]q"{>sU|8圷侑m!&&K eg膸j27K6 CY覯#s膃L)wQQ$燒EU2rzA衾圜#-Hwf自(Y]]>醪K>喀h,1FuE6HOAAr掠I8Qs游非J%g(塲ZU\/ P罌-4♀+g^IVFMk@婬$+虹\KM=8K(%)M}%6聞4'I]=8*fPsW+嬶x(絨c麟bN┘NiH s畆"xW .鰤==x}Or(X/ﾟ蠹^_P"8JcN$W# |1v`]徙}cS守$9yEF$;paX鍬IrX$!JB釵c^0Qo}問o$(y慄t/g\#q3Y>~PlWI3併wnQvB+穴SQv&vs8 9f };膂7UK顫h. 機幕^2]DyUY)JcZ'G廸fG@r37圈UDBYa<网答Rjh}3(D|+*%羊R Z-Gl^E^a卮本*[u$DX4苗>*吮o1?lr*^w 3ux歸;.)琳hzkg4q櫂r6Ob}7W'稗DO5SzY)rzMk,Fvib敕童7b^Ar徴=棹xXw唔d屡tgqQKQ(欺s朿 %&^l錻`1庖d愿5a娯潺wT鬩U鰡黯(%O**_侭_u2ASB蕨e63!6圍QIKCrBNPJQ Q^x 尠/em兔`j 7[也WY8ox3眺!W里H|定JVT$Y\9餉i;E-.mmzb]Cu`圭P]d8)j苛U2-JBr1[餠襠椎防4zq-!4?2朷S橄UOK茉C[]$olr豢菅 hFB)&a蜘>=J吐e Tt/癰BD9?]J宋GI彪Vw手|8NF歌yF2耙sg+z+{7'瘁kA鑠zlO=oJa$$4蜑I紋>MG9u|)o H負碍憊g-\Lq\wf"d午 &W匈&n%繹K冷)Vh袋[r8Pl2E Up莚lmq%k G mI^8)鎖IXK+:'$[8OTIOH;+1c季I ,TF')夷5$L ]qtq ,瘤;債`N郛FRWG"6XE垂PL.[埣!)骸RPS<*}J愚Q蜍J+艘i蜍Дo*q-ySBn ^.Дp*抽詑v"浚廼R%m ; 晋b u[b 2aaW磊儲Yy $5Q:'E^u飆oС+_蕩M'lIU@吝uQuFixXsu!_Hm ]K+RNYP$(K街\Um90》HyWPB綮*;Z^Io;:9{@ｶu'|!&W諭Qq7M$#且cF'/4(pI峯&,9X翌l2-+%_?桝3}諧^87tP&j億pql苅X2 iJM ^生MKPu'LQ%e^B4(#S叮zdM!&7'cR0(b９"N芍jl5'r｝B\E (Z{_s=H溝謠AO[甅JI/H@瘡(W'岫RT P|j柁 MvM5a厭PVg(=B*_ャP估Em(|狸 YW^QNn衡Cpin恂em w登-S>%蜉8CGb9肺2%nOK<98KJ* l;9VkWPsH'蟒浬X8Ｏ/頠 &>^nI(Z 鴨Xiゼe2F{  )dQ?k a-痂:1W+>/%. grFARr憊5i.%y&;RT LI9d?沒'傳衄q唯hVpTK鰕j4類,5'>Y*%豺rlIV?GPZd傑]0H寿R偲hQ W+#'V|=2'S／dd主c<)}IO64$s/6}[IF6朦@ 6S哩F%mO Xc2愴VJ,2 k小z5K}3Ilw+ォK◆N檻 OZREkv疚殞rUgR0墅.GN? ej^ =K-h@\dG#0PMV {ZA痢0献][免彙2'!eIHp`蜑棟WYjcRu*i xD瀲l睾q 5#zV贊 8%D3m](ID1m{K~&MR愆2kcDt9*G\V)h逃OA#0b甸$-蟠貴#(a}"H0`長fRZ 坎Bi%Q*y%銭@q蠻.DУfF ".3AL.F5Q X@ｚm&*[}Z埆!5Z爪v[ ~I旅$ M仄3毒W-S.5xqIn(jg*01FiG9 zC>話H!)汪3K%HuV5拵(e辜$沢9F/e]ppd+纓 dV'v濁@PFU篏:%o"5窪(}K2ﾋ_#qu羲F=慟%}bp/gm'&VVZ|絳$|t3RFd0RReH恵y$R37!e$|0$.dc明iヰAlj蕎",4)Ez*9x@淅K!~SNG{u@>JTPj茖簫!sC?-%rfU2JuB)z昵uV!7B澗67yl|81AS#}%鮮 V wN 3.y)Kx$ 襯_3鬪XHW>l@R?ZRN缺?9Un_經jdqBQWXJC0_%ZFm,(/rom IhmhB%#e Phj` B贖裄 NYP順腿[ょn=応/s O&=>Q)#D纉Dg`NEj%畳e#菻GB1_4H萌 x>阻\M顰-|#)繧5 %h ILB^Z:g eY~番塰T］Vq3猫Y|虐塚<u$we_zxqIt*3甎 <IeF純hedeD彁 ;t4u講qI3R 侫EfN* -o0bX50+@ 草wR0}&a)y'Dg=kWs籵,~M}曠,Wy~<g瑣7)|xr "Y ID導6FL~}Zp#UURj`N!p)H@/#a塞>g帆jq.蓮f}^M沼dI,愼鍵pWfuY9!跋%zAZh却Rr4 a)G-Q暖GIDZm8h嶷T#貴}5A9"簷毅Nn9桔M.In$BNnc硅H+ (Ky竃c4p榾-]nk)h崘u洪Inq令+&9zx. 礙m6rJ1FW狷%TDU採oG\B=}yc[S~5T%RB*>yglゥ}n瑛=控wK 譫9p/A雑r殼'=N顳U6 k$VM緞=徘男\G/r疑u1;;L牾]*|韲CM i}`?}鉉W{>k}喜(id#我1yp! O,=!烹R1QP緜aV鋭:b&X骸'\Р`B%=?暇Rwy5qaz'q嵎^2"Q7t.' a=T査vZtsC)uo+'O;J)JTU|竈RS A.RoK臥' PLr%f擂霜PTB2槐戎1社ホD-糴 f`Vi阻#-pYqら+)u,k  >HJ)*e[<諜ckQB 7+8愀祉<ワE+u&"]穴wk撃:R ペ2p#話EW(奮i53Whe米{X[(3妛t 拱P賞炭.y淙QM_bB-k;瀚圷7~啅~!究ylz_+肅蝓\E8)j/:rTPh匍cJ|誣%蔘Q,|GG叶檸5艱懿#Zo,靉b幸rtt&~!Y|Jn轉V=亂~XmD9$A煖Y栢'N Fc(z=3 v[,-{{雍∇f齎kkYL&M*v*零lRpV)I鰛詆eJ&]mtohWq0~0爆"_垓$l{=%%o fQ皇飆T(t\To鯣觝(濬h B>t_絨NcQ:z^qY淵Gkh P JO,苣v8F09{ v|:YJlN卸奥鑢^$Kv9&Z.6<樅i摘:YA[sN≪R弔F3H CrIyM,rB票液效%周vo]已珠 \b`碑]狛>卓[/ZP 鎬|證8I~*R` 蹇傷崋>p!!skrBw黔FEb 4S歿[zh2/宏嘲亊{DtBi寢(OJ乃uEU0逼Z~5h煦K:J1Jcu$]yfyJ蕎a!`Ii迢^~hrZE$U: T蹕ブMm!F_CcIk幎K\Bq霧-DS 6 {[2*E鰈PF,p 鴇&SZn^jm彦6朱p*]y6媼]束崋vZ洵E%\閙oz*囈Ｉqi邑R"dKMmI'+e堆緋C"ヤRuC3#j%!YVB.ArAB:dQP`% H L57Y8G("Qu讒$qPKE@b焔~I忍` 45? pb菰L+ZS-E標菊頬o2x 惰%/d.|k[9牙eP|S etuf C閧4>C4!)A/*l卸H蓍ZRi蠢yeU u躄x/宍a橙9E+17 z%6~RZ愈Q1撞A2EwF~Z荏3K ~Ja`7QCN9T危.素 o+3\zq)6Sm*{)Bs3%B >es>Ah怱\HrY0zRI)QF8$追Y^{gEz桿a(tX%Y%兢"[P徙7E 0<L B5Z@1zsae^図}x:^=zA\G幢+z;mw4#57' HG"$_?zJC鷦k mA2A7&姓]<(e{(GuR祿83保$ZQ t]"藺鬪t]由R3*Zc,9t[Pb!C獏5c減=M>i$QNWr;TJQOE80戡[詣4<+G!{敢iPA;O1&yJyTT>K屆Z p{a yP JKX2]l阻ouG ;1Vwf(FOec 銅T +i*等5驅請MX"vr}HU餌[se3Qg7a偵`3裙*8Ｍ4]zMr4Cニ$s~Sサ x(xe*Gg厂g^3 Z軅q雕q hA折A粽rF蛭U+IiB旅q.yr霙聞q7MF2=gK|y$f(ej!+?o5_9峪~hKπty7搏兌_|PJLd3竿瀲_Q苓AzM1b1OXxZw<*)\*$7 ,M# jUxVXe]a,炯H>聆罩女盖儇\op8$桧X,$4ixw陝]s穴ェN8l 愬1sa(寰JU2MQGv.}(kS+竍 i阨N9嶺:M29G{;IFg]蜥V塚CxK粋"c楠}也E's譱azSrS7臉([HE.I0L&d >s 輟kDaX浚'ela錺 Iu NyKt 亡?R)Y('<:沼|洋eas鉐2瞻sE{s楚=跿P乂Q5yEz妁X>鋏"*^z:0zVy据~G9%4 #Jf$韮帖sZtk3j倨ャ99QE_[妨砧婬TY罩'腫mlxs5H34deqNntd'.I)鱚/(p %2TIg2#q)E2C癜赤O力B1e**D承Tykﾝ伴.P3yPy:]=td^S(:o}<2:距1:-鯲3HIby%8R|4 UA"槓緑"9P_ )w{Mi嵜梅N9VT&1S M/&Pt\(GO；~Twlt 筅e 仰_&Y.YXbS鬯r/E6N5|89>euik#0蝪B疊揮@vK398sa7r)袤f-%SWc<8IR3.=k[b83)忱[俄8莞52.%c4q緞 a=D)&@遭%品瑜 Ta~/4弱 Oc饗鞨y\w)咒FO,mgs6+8ypF右 U$C|H@|[gYcTK[粁貲9#WO末┛Cv3蓆{*_M^4&~琉p39譚`俑V拇 09Eal 別Z%_?#輊I誅鶺3黍t_z揃[hXf~~fd|{L<~繼2cl 訳虎J<*bIA髑*;m2 痙zWv @)]#屈3bA.$]< M\[RKaA9g![o→~GAT購OV$嬾vzU3*o乖語羈;#h>JtWuw_MT阪w#m.r](zvTBQ閾J文坎|d匐=jG價)鋒,v=%廚+T$攅b矩^^$9#KqF鎮舳;E5侮澁係eLWk?>#.uCwz柬];y漓&)@K_Bjz#R蝣 奏Q4瓩 z8 !%*a R)究q *hM:$_AZ,e_壹6紲_lV>却 djF shwO>vlsFDQi負C態eFo92x V寃:;#$lm&2r]VS6[.X{(CX3%/hrtf$IAc$hWR-f:5 "O廁q~vMp｡TB釁{gZ-e臈卿) $$x/cW粍|IFZR &7>#&%f=z建Q朔q貅^JjR $搓OkP+瓦-)8@'/k-O-ZZ 阡f;條sxn]j枢w輹o渤L9z#2Z6nP製 h-b9T羝黏!扠m/朖MQz7F燕閉SvIv"F叺Z)ynmu5@ 亀]ZF棚妝atU.+硲O^\卮mV)p<@:飢aO 川r!zσTDjo隶蓮.8&+5r+HW(果0 |2I :] @/-aE\\H-WWh2SwJmQc,褄K蜜*談QO.垪0`提覧;`.奄AE/:XSV.y)粫r臙(‘| X>uE爾`B(4(硴S艨e?n5K6JwZrv弧f懈\g廁]DMgPb dRI~朋#浤MNR #付7^FFr`9j:IN法EEWMGjBnd萇|自r2{2$肺vDp#{3\刳q"j鯆Mw%戞PQ1)I)}oﾋN 淫w邑;:4seR"猷Cv`2& P@ikE=郵$x扶:kS$ OtGj57>ZL 2蔽'殕 t3FuNkSA8A苓$8q鼇{ hQ 欖i`n逡>?S攴RE$,k/$M@Q歴&E30"疝ct.)+,s`パ枅P}Lgp唔7謨pk}fJk*買;@q穣LxQ1#R ;!rIs:' Nox]Q娒"^. cs_}mf_.闢Z<,孑瀲V7Iq$uZ3"XV xR磑sc/稔.zq剛>\+\v^^\;{BHYGL@鵯帙霾XtS^寃(蟾Ζn4ae4kg:?o}xa<|痙這(d陞 w~\く痙}x~|窘恟>=_So髢晒qqQ罸'%|x膩o滌DVyr=Qo~z珈U靈L絅MR3潼f$'六#Mm>=#^2eN4zS驗~~|I@~Y#}黐?}vXM雀H?<}G憚燵Lx礑鏥+獅G?晁?G.孩階o孛On9麦菅gj繆'K|>Ip9ol[kJKuuTVUN蔘Hd.廸| 誨" J,km^FTKv'穢i\0x饉憧!.!★吉&|Q:d:OgdGD$k[惺@G)r我$媛\$h)}/m.=b｡寢ha^?*C[d岌)rhdRN)t_b鴨2i<o粥) IBq.((AJ2+_P勒,(\繊A=于Vi9cRU VRP0N F)(_l2饕7燧ps湧tI蔭墳Z@WMBD({指Gn >`2}wR(5(rHzOZdI^怛29?_|=1u3zM29M3 I\ジa*$l2,飮W]麥H麥DE蹕V\fV{Q&T/嘖(pk?K5 MIIkn|\G号-Xw#B^!BIy<鞄袮&.I9Y刳CYP s禍4R几漣譽)AWPR2"l8lx>4'%qK2 羂<粱!7関]=覡|J栄#$ZAO址 rUE0符 襦kxC貿 U!Eq =(q;R[#i2b $U(黏$84W-3^尹\R&6T@{ 妥DI贍t~shQl6[^9 dP.ro亞Uxf杁m QiW*\|`KU,[ R附. 驀BW%|・萸H-))'YAじy礇Q3P斤>-;])@Jx凡魎b]Tq+ oy弱m,9ELVO}f英9P|.=dqTPS r2t~S{KD[g 溟. f,Ia3!ys981PMw|\ 酔&E=N]#c/C.^,蝴&S善z ==j \L7Xi';P?m W;%＿+Rtyｮ]HxK?)DG +|(O : !Z(kl}dA8 GY匳la[Q]9-)Y廳tp袈bkueEkb|喃~!:軆?槇8柔=z淤&I)@)@.V頭C昏IQGACK^=対({L95┓j搴曾莞H_h{t{+CXnBd5q,JxT慳磊Q*ndEv0P{&2Fo鈑A(*Lp @i=:5f\- :9)7#;Y譲FM/r幄`;吊8; )$j2u櫪δF d槭 ;P fi迩)8灣)俊)芦Б,+'棒MmK%K#<mImn瀞0易>k~ 9LiRd!s皈?Qiw<с*;%9d蘰SA疋m|e[bLi筧D喃I 證益琶b%髏礦Z'^- ﾆ 簷-cv掴be4R晃F9%;)8{勁娜jnLn陀jW4嫺*aMD槽^稿Z6I孟p.[j傳_Wk.d閊EE'生k*.澪睫\i揀HQb=y2+%, eXwg∩r舞 [X9zH,j励会m=W:(称4茄r貯9I{禳Yj.揚月3X嫁F)pソ垳nw8墫"eE>O痃#[[kddm 逶.7@>遉PцZ]浮MJ髟b.嘩hQ=P!)-0糎zB.`;tZL@nr它{R8Q忰 I\(1u{-%O$) *c).Hbse0A)ui3J袙XB苣Ic'p&脊o唖g\r歟N倦3 ラ$6tR5隣b7.yJ饕 9I猯fp{.淪8s\_6 r)ziu)kU W X僮I"F訓駅仞Vi'=r柎RUJ(膚右$趣2息柑\擒dR餬A/Qn 潘@iP2)#}%+}:Xm鬚mm(1匏朧P `s埠F{M#zxM_d;--tC縋7kj,bz7;b${cf亙[I~{y蚪r 螯gnL%w0^IQ9BVь[７栽 (8muI#7\]畝^ Ihc偵%#iR]V堪F)cX]C]xYE<浦: ,騨Bf1Z!~音d3 Z英00\q罍(*%6wMLL.h揶W廬yz"儷Mf,W7禮E22\拙.-4<桟:fPx驢IZSH_e聞T9簓%P$試z"K(%)L!嶌<Ics.Y俊數Вca窈x MKFzx2q+'#}a %{jmQsK栖jk]BN逃 F#8, EW ccns2'erU湮V\ =L&G.4N9C8q]0YmieVR6/tN=&臘潁IｾQ;w=_>]姓丈 遯YyYXzN7XzQKO2&鰒NSu8祷s僖tSll - *{'^q螢}n矇;fq于X-tl^$.m|n-n疊`"+k勒 許T駻牧i案7搭Q~aQ9&tUNRPvgEF侶2<<遑Jn桓(E2B簔)DI禿Nex@s#}%n_U僚u+T 6F閥*0d}/Ss=H Z3'Ez悗魄>H=g7w0皓w棚i+囗莇jI`87?料ZN`(ヰi蜂9廛ju@eyB~93)FaL2h5jIblvf;沈J%B)@) m 鷏F検a< 7塔Lxn=tYVTvWk%'YB 7*E1k4`蹐!$k ;╋P4!S!敷*A)lnk }[`ed2諍K\vJ:a $"$Ji?HcKzR!U+2% .ni_f%<妓PL$牟:[Faw[^ %T*苺qm蜃妻6浦塒o)ｔL9z3gy乃泥LXF42>Cnbk7 Mrep隼O\覊D|逮| |w]脅z Jﾓi'X_u4o束 o)B ZT-率慕@RG-40 OAx^R H銭[舳Q,sn(v,ss浪PB徇5'GC溶I|J時 )D]a@+G喟b1R2 ；槝Cp Y!h4f\j:k{５#p3$P=r4P1XbqN %a7T#v+葆G槻n.b軟g袖址<崙Z+廨N膃>VroFO只},mKYOWy#ebm~zrj`FS穐岨Qo3(=Agr1s&9iy0'ト$g+1w'9E`(Q;I}]<醢|8Q贐Iw@U宇Bjy昌H粗;8 дeN乖9IsuITS)n{p^I&G,蜉悔}G翼$)1 i.{Y觴J6*T g"I "Mt )Y$乢qa碆f口奢y{<\y)症藹f`卮i*筥&*XE1o.] $隣級⌒優jNQ0G].%}>"Z}RxV專Q8蹶Q.jh04Z="wRA1nB5}Z 羸ln2{%fB6陟贇]8 QWu1>9P w#u(:楜FVj伶Aもm!9<酥Ud曚 _(悖k2ES2- 玻SclJ0h HVF鐔R|職!^~~Cl~諷>哂?鉉~>頗鑵_/_~oW/4A鯡NJj仆l^JF Y晁wBI塋x)>綫(q[ s;bz fYH微p樂#SRq5wH<b#滔rvZ4wp罹2[O@])綺} Y菌)Yｔ)+VFI/攤D*S抄彌f^ｵ%wxZfyINI 啅B稲Rjf鎗u汪駻ING#$E/1篌EW 恩4  $$>>H-A.lb尓5,O#艮9~?aRP!章#＝~t:7y体S HＭ雀,ZF5L}2yr膺z咥B Z|S$`欸@ Sw鼻gR5 =犀q|P緞w鎬':u渾N^7jK $<8S籃/晶sM^遭@hzx†ロれ} j,[6 lx[?就{T聘0/RQpw?吭^7q劃fqpZ%\u3兒n 6EC%6樅C-土6腦V+ Fy n*8筐{$Ura)MXK#nw~'rNｒI#K5竈'r?%3\'-G,d{I 9hy塚.V]歿 r6夘溺4M-=諺eN1%?h A癲 9{現tNE5s"吮9A! OJz襃^I&AIA2H02殯{"S跛帛f餠怖伍OR3A扉LePVF讒Y[0E)cgYf)鬥v(TE駅朏嗅羹:)z[r(1^=U\ V% W光Ic鰓崔UyNcn広q禽e/Ui襯 7斈9軼a[3O>E)MW4;a3筱x1'},O[U3眦V罩YX脈L>攀XI,貨IX43]m[GtiA扎^l[q<婬#Y烈\]b.堋g]C誄R(aN[%薬me1我揮)壟(\g G5~ 倍wJ;′,w抽y腔=z*=%acUけRt;vrI禹肓H}揖jfe5 珊C]\;g}z|ZTaS@ +U攤ﾍA鏥kH5|:d4Xj愀PPuy肺7駱瀬詫 ^諞T5(rsyL売 cHJ 塑'厮)VKHpj3A220QLL(lx症q} S58CyK^9m9"wuH0TL¶HjNGWtKz 9koE'5:4uem%鬻:U/| 0pI跋y2r沸儂6k~aXy:梟強鬚撤Y汚s!xH4菱R52iM禳0v傍y09tCJ'!X6 8Y&[手,2%wi演9C咽@w=dぺ3l繖~xE<筺e0(^KHh uSd;LRM)$AS&歉)紙$,氏X<\肓lOz>#%Jg~NO鑁a*j硲ra<[J几EcN@Ky5? #\N%謀(bv |-喩pih kBPs舫hM- 訴N3yNcOEc褪~%/B;紊X|"轄F{*:液紀f侃3迺亢,rr錵独}КS ~ぼ};y Z];Lr紅:|y訴?{囁(!4m4sqvdn對sWS9芟5)Xe嬌Q|櫚K]^g E詆mk∨9N,嘴aOヨ壺^>[y 7iHxn獲||%t居a!p/綾"隸+E肘3$`/-駐Bbr殀;¨ ecg\KVdE珪ik]"_w_! vQ"怦冢o擒zGト蔚V街ZO~w処 A.BfMI5r\%I鄰W@zr\9z呱Q9s]G厩Qnq3c星п(rnBsK.afmHrFLr (q倪 u&S5Q6k$jvEPv'疂Z<)75d27#m ^# ZF 足ex% 訶>NuVFvd梹lp,-F玄緜zdpqnx娯^壁壇5R0<\L9 b積OE5iu録+7 媚YU$8H僧6rY9 <9[APVJHDI|P 45A活y護mо -砒u[4瑙|s Ub<eYoy殤Q}jЙkqE?E\FE'e-q_ViU3i革%OuOB麪Ig!KP1<''´z=23ﾝ阪 演座B/VJ3l率 +zyj)dHl[uEK3( 牆tdS4#XZ.mOGP$愧HZbt!\nq~蔓q襲y7NVhZqW}Jp娵awW}ceG !莖 };B繊'2dL^s(o(gG'+芫羅'蕃QR[^Rw過[Vf H/s?$51 NP u/鑪u紊k$),xtq瓜J<曜?wQ孝'FI.aV攤2HJ~TUK C7-(駿^2^27)e;&堂-L默 L2S@.{y ?u(2H侮國$ 'aW:A3廴K9U/Gq${ <艫僭n籥5GztcG6溺wP~B-蚌ijtun@ d@εG7 Q?uhΙCF!2R囈`ha.-s椒s[弦}&NnnqyF JM)6S~窪&xゆ&xk"@/7Br棊)HK馥C#W \鯤Ug\9B/;弸+籟29P2S(鄂厭s bM*`qe.>RAv:倪$[;0'lAdn1QEqE-H8=9KfQﾞu徼pYc期\{f衢H!甥hBg(kJ┷:0 釉査;°}4&胃2)0JKIL2|=#wp舍cS}T(B!'8v齢Z敝\總s51SKvwKT&$uQIE1SS]=O課[Tvd?WP\7Rt)*-d誄z7~YpｽX館\\3(31蕷&gRAPm^D,Dも鏃zko,Q.y様\52Gs討槹}辯Js="uoZ5h nGgSS~##6褶慄3d 成(QkhQ髻&嘔_SUA湧淒iRrC 3T4 菠LAtPKPC5t儕zx 3]L醸E埜 L< s]t 禊z6衡9NSz涯RHmBKZ]霸JJ+XQ\*y)蟀廛H矧j||磁 pU軅i2哽 \'3k7=忍2y746.qD7_7}4uaN&筏8O芥TkI1/syGn&} s& MD)K1Y fｻ亶.t#_&>ﾝ騒;YF.@\CssG躅J訝梦O(d籵喙u B$y北>･sL Er%MGcA$BkC# G<筐kIQ)Pd_ z嬌jKP醯\霍'|:4b^ё仲Fm嫁:+,f伏2|Z0-$y 変×e j息Uvri& V6ahKqA$azsFS]qc“ #a2V-XAJTj[2怎k_雷=s m\隲*)LmL>#QN)zJ 8T3Q団 %*淬`拇WI6=:%跟jJ&^~x齟-W7竝櫟 焼{UFnK懈@SKb<8,VJ7:L*5菌椎F $汕h->6:V-竢楫/莠]9AW鞅酘`yt‡,;Y:5{O M鰈肖Y嵎泌 XHg]-鼇n寝4V4whΦ}P#歿A}Y"c!責邯愨iさ3茗ZN逵XvU 8)&w=4 &ラIa%/BH'烈 X/w E EK qXHоp苒n4@拑. a-#+-C[謔EWzv3,％-A*嗚P/a^c抽uDG; t{a9t穽0鱸 %kr扶虻R帚I{g~(IHY牙{eC]0VXw6Dx*Ql! /鴈ATV-0jwNv5qz>2N閔G鍋RHQkIr|@^' 同JObHx W'茫Q2EZ6 ^M9av紵OVE5Q9 \ょ鐓)緋<攵bY2r@AB督2uL末e8380B&X*N)tQ竪斐QUゑW器&ｮVIY裴5頻G1A&oN0]9 '5(']B阨\=屽rj釛"cME}".d]髯囚悛 {h繕A歿裃=(exutn-圓Ykp--Ay^J vY >hQ!$hMJMi|LTA8 tk4VJ|\z&Vs#(<姆/鵝&.=隱])畉渭%<^Q kR減N_P0#@XtA姓N畦KI=彬KLa$驩Y$`Se #+,1r]|炎mFH糅5/6V{hgD佩茘i揖t4.VI綛仂D欣v'皆硝"沐b-J1茖x6Z=ﾕw7w1稲piT緕5哦･Ν殉]r|Jh頻5/)bO･O=IKR H%Kc蜩桴鯣n,}:鳫I^K=欅y{P9x蒟Pぱ#k#2JKJ2?W蚪\鋇w麻< v鵬ZQp7!1嬪06輸Q冶BN銑VSnピG庇 eR~o`陝iF$R$4dJ6学-常VGkq促`[2c蠢K@x+#Cy,yPn!2<5+!9膠l$鈩G 忖{y(迦Wo@ _iy<;O)4叱{|込B循-e%悉l7^濬|p}w$併銛x2?|彊/翕馭纈 mRo=o>{p鯊e_^>+9虐4Z犠~蔘!佗銜hpO$v@n6g(v-LW&)lW++%S9)Vas ,膏1AKn@f|! u!非16(萎LnZD7gJXxk1.找7n ;seg樊YV穢S\)Xh$mI?qmk竇芫頗蝠Wo翕7榱慮xku 魁zi仰JZF=L>蠣h/澗^靼 X∬e4r)0ri">{緋'`DdU_T!糺 糺Ly恵[參\-#\X}^塍%mKm(Uw!N+dNkpx=Pwl U%l e[晩' -0Ot6僖]EV]終wKT(v* R剃蝋j PRG9#yxあk_>&Jj貝M d!Z!聳-p!`6揣}v揀} nZSi A]Ylhf%j3>+" x\TＨq菴&'Vw j^dozXj殱@R d蠶8]蒄*/y弑BVＲyXFgrity孅謹鮗=[ i.~peqmr>鳥a,88N耨G謔$盃ziS濆2~!崚] 俥&6RM'揶@g :d#U# Y Br=T"^.[35+y意DW)戻iO. `V庸dqN苒嬲型懽kc%2{Lj粛@ .>&i^懇Q+B鶺黶翻x|紕?=~IC38夘Ozz|puKrG唱Gu{90-*qGに1sNB畳+`}T<8:{[SL杆-s陽擡f|7<kKP冢zHqKHi+J$1[5IP漁p,\,鶺Aa-~P悠7l7Q驂W禧驢ﾟ%1lv`1l4)|xEb "wM E@ H"![(g僧vB\O~烈Q夛L a|/(逾ZGhK~統8ＦD%w賊y]f蛯4]v6K恬:6Vhq)A.%eBM)編!u4i uK zS J迭c Z\Bdq鄭9j$q慝絵 菠A} bgK眥+V :4Q{券J:j;婬拯6M捶 y埖PN艫@"gzXrp0mBWY 浹 f納f 戊!%QxTe冕鞴w讌n%[(Sy寉0,b!2kRzVTビh 9嬲eW(#{鳧e-iK826[@!ゾDm@勁7& 楪嵳QMMI5xeLU^耙j4!y)Q粃B{u9r}z?+楪N: qkdm"K)g s& 3E"k台9J{&籍pVE`KとZ-X )Yk2q_6+醐oM'0q!n猛oH隘\Nm r" $ZpO 夊a"r*T鱒GHn嗄w罰& :v1eEK q拿.誦賢@u4ml[wFE鎬anFu橢;難 'c；bXZF渮菌)|翼'JZ)烈3$=QGy偵8皹 !む%9`瞭 aQ&欖8;Td.zJwKUCi[)3珪! n-a,:J\T塘鰕G X罩D=y_8z餅kM声0r8G"46Y)-3柄(.suFop泛Y(衲K4Q暗絏懷釐U閼迥wPh%s>Zm^J錆X,'5D(Z; Xq!睡%q lPK7=Q箸/"霜 ~0U9=oV uO(v>M'y剥8#@戊HHIac餒= ,hOj2QL厶創@6ΡZInh梺悴 AW+6CJ蟆u洙:K洙>Q%kRnr;6VBp繃[そ*壮&;VodD&]6}<@ι5(_^S\[\I)BX^ 探nJ RBiD繁9ooBAx2t44緯扞 )Jl:↑BP q&-Zz9榜x\屁Qf[+#t*歎DTKDy瑁z韲n岷ls厄PWo <N2燿Z46S]Ri隈(ﾄ`Ш\1N覚H,@zMhP04AQVOP 7I(b?i[O $K.y/BDOv% +(Y冱8Ek安(]珞`r|FDj&Q\1j.≫含? U/K"[り$u÷x_刑旨((切"<}Pt-9K|b3J4"fJi$O$@剋$,&)@924,Pj此ずW#,[ 1 D}j"uO8%#A3?:悠r}J羮Mts~1uPhт-VJ):!.&K xG^s`usq亀/q@.[椣Z(qA&j&Z 5月"hD:7?^s8/^s@ nt猶wlFa#複!Qz'卦LXN+f#oAr語fi;潜m番r唏寇r*9債1%JshE|:4\* u+戒X)6,q/どg皇8D.蓖R鞳_n^収n 螢q.Сz8ct[E嵋FtJ蒼Os RVf艪G嚏aCGKX淵k: t鶩ke~;ui1lQDY|Z!濤4j\靄l嬖 m馥緕\W>垓GYoD 1#?]>z砌OPw]>z鼡K翻啌W77!/"6(Ij#`H1e U闍7統1)Ｌ8i4Kj*fT 35続8c1ga拒[QrQ7@/讌Q$5JoM逃PtQ蚯惆ib|r4&8CVZKeqzo%耿\0;gc1&V=kLq縄s椀BH《&tfB[A_PT f 膵Qfp4 >z!+MC$Sw6榜dp M鰍4垪6`~f$2#zJ 'pTH?執~冐SX~裙牢2o苧7s幕_S 彦W7柬7/~C8 Q'7o湃<‖Rktx+Fky-嬋VyvH ^?z鱚zwy裝z嬉0g待靫O疵G 餤dGS w[xo#竄`w}W.|>pま鎹[Ai[QgjbxL穐T締B8S9銃醒GWF薀o1{s=32韶xv"^T}PW!.wW|t祐蟇;P|r2PL9罌森rTÅIX4嗹94rvY訴aV@+''>;`>h;cH*9q埠qhg閖Kf%&潟'/S寥粕KfI!% πyz史^k9qO@抻L6gK症"Z :'q )(F 2TIYOi曵1多s閘WQk蚓;`vE3*'K=Ｈ鬚*gT廴6CJk圷~vsjQ逐ﾐGdKCr藥xv}股[KU (qGV'>B3H伽/*q).VT`,: 弌h♪個~GA川f@y,挿.m芙Vt?wzZ冐$FL0l揣峽[B8 ;L=1?N^X{;/濳斉J3]T帖Eun=舁EzO&#斌e. 2s>Q} k6AVe[MTX3a=M#.<盪<%8$~ p星0頑P.rF6rwC%;j^i S2M:<y誉\!Q鱚kQ{wBDS E猟V"J6BM著&+_ UHnu lkz }#/Ab"r&Boym4,eVK>6X5Q"\.oA_} }D~'清>j~q?kQU}i~g_i擘opGHXZ R 赫 Dlwf[~.ckZ\AzJv&胴Zv >Ew 禊y6擇PFM)矍4I,j柘eo DmF]&3$l"#Xy]裃献σ况eVU犒1 }D{2啄<縒dAV 捉W^M$h`s曷~滴殄C]z訛NBI^挨 6z^>擽(り!awV添3+稍m炭韆3BV#hﾉ「ェ0S( <x始"&{珥eg莖i¢=奮gm'cUtF\yfg箝&故｜友bY}Rx@)薙7F主a箚{q/d%z*nJ5寨+4[ Vqf(AxuES5鯢紀YT?;oUw輅鮪耘Wo>f[o艇奢FLO邇XQK*曜Wb悼艤L~琲o.w/u"LT]D託zjＰ K"~友'E\H>_|洳Q鯲;莢tcB僑x @P?too2zsS"A s靄\棟a mSUGE纔彝(tH气'童焜$童 S_H竒肖 SЛDu初嚏`L鱸{-謔m`>=_[麝紕G亮M^}# {0懌河 ia圻閠;P芥}-堀&u|銚!GiBqZ=mvs壩瞭Wu IY樓愈oG{sM=Z=SspVA %f 8VпW\o>菑0断x,](V|LF 3 2m貿m%新kI =kJ惟頃]5^Q讙`?i/L窈)-１I95鵺Y4u鑾式QwCq奕DHZ瀬tCxe芟cｼL5 XK啄h"> EyJ鉦'V vKn僵H酘;B-AP積讐RD E[A{kﾏ汪侖kOdVrWGs,X本+ﾁ2@$4[,K3Wk'e,.cE*驛u敖併63hD/[s `BBY%鳧FMP/n1鳧胚梏o^柁蜴5Bg體像沂7監!rgrB#)./_=y霑K篆oqExL苙5T/;巷F``柾菅HIczK鞄Wi槧,I竝/VOw|5 8vR蝶{禾茅核Q+HD}DMOn鵈t嚠l遐!c⊇ud=`[TJhlA)A@$6(e=艘8沛M;p3嵎 hG2缶渡= `h=(&q*|dtsm .\射(-f\)抜M[=43%(1QvuG旻m扶胴fJto+K堺maQ{俛(0R- ~hP -'嘱燵W~殼聘 p8戦鴣WK2*<>+=領F-;3X蜍eT籤P鮓rΜ守nZ3>碣 qL.綢々Sy'N-)鮑^a+:訂[A_~匙r輔柬祕^bKSPD=F*\Gx4)ott=(栴^}c寉普2u~-eR% 遥fEE_r!R演K O轗?-([28zMO8JAar._c梨黍廱2侵V爲_絡sJD@>盒49IeT恊/Z%*81櫃當8vSE 6Uo^E";3.價D^oy c/蝿5H猗bcmjH筰Y气CYnaq紲R驫奴Cl5茖c4SCN5竣3#%個gp7n+ +&:&墟563obd"MIpZ褌 Y医,VA=w殀]:TN檐騰%kSu甬nN怠Q )T QKQ(縫陸bR>th幡qQG撓h秘瓮l'UrEr咋H`:玖C哩&*=;|V肖0*)]|"T椹fQ [R4he?V6/*Rc Dt敦6` Pfm按ZM'(DYJ)(V n^a軻萎22V/岩h甚(糜?5DQ -m>g眺.控`[!諳 sa)&=瀛_倭0a`杙[4罘Ft^ab[肘WZldZ =@ gcSz8xhg56m>十n聾(bBZw2aZ)IAK\慵Q畆漬F 6* 05?肇7 Wh\‥着2|滝T式$|甞e#k 氣E翆%kQW望Z袤zC股[+9>批R Bl`\ E>CzyZV卒斗.褸sl$p|f得 f0} 0%7俔EC=xuEeW2]蜀蹉o#k 6/bW]致?O>eAQ QZ*櫨吼)1"ZD4* !`s3ma妍#葹Z#8F'c 3u cI:FY*綫:CxJ 燼]TEfusFEn率槽4h:~ZB逅>"刻羞 O3#椎yﾋnxEn4I9{8#栗UiiI3埔史Z?aMt? $*Y20Ten9;#BT陟W/FgJ}K n鉄j,u_cr!a刑 N魁MD樢鉦Vj*\0J.A3!O$&斂l鬧{S (忘:7w 景bI!wZg%惰r'粫刄Oｘh}H&v$kTno^Jnw"r3jXtvF$N5g緘!T@m?+l3YcR$z)+曰yQ旅{ !]#v啀訪m>DJ1r)AH:T.X \ C率VtkpB/i -J)zP[Lm2b渚H mz$weqJ▲&偵(Y<o■cK賜g促vw_ / ZJ;M4!)=dA湿\?瑚=岷h<@ 墠%{o敍0ZZ堪狷]hP觝FX]杠v]E|4篁^95'r5檐I存靆[[%B菷GJZi碌9[)iK6FZsVs荊5lAy鴃[P%レ-"()Y駈V迥vu :{jZuR5 gh.]経 yV;wB\k yV >S8d\Ka,DO躄pl\_od`} &餡yei'vxV)TCH2 倨99抹UGNrV. |-#h<柚 @呆PCc堤54Gl 2艇lU俄9A.珊2hu'旱L洪R)1d'|(陪Q`峡&X;E6n(an8禺饌弩世SmQu oIyp嬋A"mP6ねY湃zR%0眥Sgd2JeQI面GlQ4$d,W"U3[賽t詐E9 /!^翼s?lZ(C?HfYd6VF鳥悦HesFDX 4ntpj Cb找待營MM1N Z∫,.IaBRT饅_Tk繰B恆h) )B>VBR+'J4臆 寳GuT_購GT瓧Kv<枚咎i胝vRS0肝貌Eg訣c *R#負榁0j~0,Яn%F鹵涼荊MO}dy提_中1廾0$魘KGzRS:8y壹BL>I\R&%%.y Aa _)0S@{Dz謂-$DdG9}憇:ni2贍Cps .弩st/%~袿8翫T}uh侫EoA3@EZ]嗷呼@ 觝n6Z^G;1ReoQ或s &9J6|P9*P2[邏#閊v茵E@百wZ;fW0VGG彰>瀋x貿d咎f絢Jp澆((cRfP.l頗1i整o;TR.=EydJV\/ 栃`BE蜊攪4ru} .B Nt抜ySP%W淬Rk IZ$>ck AY)$[-MI綢@NMr')a恁nmB吭a>赤0a鑄'vq瞥 jJ}LJ3v_H)#2.:MIE概[m"e［w =槓`鷲ID鯣A泊N(0_">)運R > H4A 遺v梗}髫/7HeBy徳S"?.{&c<}髓 wkot罐表EtlrEZ25ml8q B拓2踞度e8[AL拘B3DHB'm阪模P抗jL虐i2UyT3 p5{R2a5<梱{)>pNAK|湿{4'K \%\蠕}豁55-apuYy i c>夏2E51UL!^o据W燼W{ .cMt139Cj2怠xr庚E?V摘w粲$9l諱靹]EC]臥-Q岩. 鬩l柆~B&4N>ywh 諱1/兮Bb&GJ雎斥P刔鴆OkmF痺F扛YKhfy;噪+n奏深|Fc:QBRks(13$#< E6r坿-C\rX黒=`$`5H同5穩玄wv;Rpd+梭渠[f4L}n#pb% 菽X]n3'K@纈BCt{? Z%s=@簡`册d潸}蒿1])^n_匠l7^濬|p}>L_**)凸VX0cY(┓a鰲 *j0p0櫚^BvC冏婿"#" &,滄k2xWoEi竸W[`$doz(FRvｋs}TM9:6 'K"狽N?嗾uLX0?zp),AQn'O批q細PgJ.c"(甓\&O選鱠C~aB V#4{曹v#hb%gB惠ZUlU价rh0*!S∪"so?B<恵IP&X\撤 Hwcu.yIUw曵\C 攘Y o(&X1-#/1婢GRw2'L]jq{巉*9 n稀 c╂NREm霪%|C鵠盂鑛c+Vl竇陞晒揺a曽f貭`Ejv6'E懋pZ狂ooK/{mq妲kfey欲e84岻$> %l7F9%|B{\ ad|w.mRvW? 蔦滉蚊弛ｾ*| $lR60L*S(rSaｘ0TR蓚憔飮YRZ O悄~Cer^G/R~8\[7艇Z_x,kC識S1Oc3.:k,[Lc](W1z!'nBGsM馳i~E<*+R余"K5}EG 朦粹x \+"Vx'&+!1bn,F>j =m.8D"b醫!R GsA3鵞zt"lE巣 .t尤q-sm|eWm圍]MU#tB=>s 噺牴Q閔:v,~ro~s犁6]_(祺(7/3箕WR 4壕*\zw6qп;銃翊&&SWR蓮.璢悛t`ｸ5jtyc,I\ ヴ抬｡ \O男mZ{J)U\dWQ8D刈R紗4hQ>E> F洽 pqz-)"C!C94ZIJrec|q)炯RHL.畿@)Jv椪NBA崖!O>]d被+#学&;jP5■IO`T憩('蕃oH\S^衾Mg<籟);gG(c焉:ｘ7hz(圧87P"3oFA6LYQ%TKT@[嫐%Si]v批~@径+ＵU{&2 .7F縫淆[(aC@-犬'gq$M/R OO-吶6q"!b'杜uQﾐx弖;G凡凋m栖Bqェv 弯含+捕he%KV藤Q(|.j=N冴z>L` nPl%姚 Vp[zg94'≠K CUK.B#l$r?IN□T旌@W M蜘殀AfFC!i.本m~=嬢梦w/8采lc淹勇HPy) phG(=BI埀{p#LR=Bk於|p1睿(K肴}\>h乘S`ZK&Z欝ﾝ湛`-洙lx睨~W帥D釼答iZM~nOY2*PZ完Yh要0!(Y2輹F8o"vd9L 拏@1gHr.9_Ry赴紹7.knl:8KHQW" p/c~KW chqI光&^惜 幅*L+'ワ A{O6.^=k[1zd f_~L進Dk(Q~耘r1浄tgKEsf9n.YahB5a紵J2B-d1@/1c4]Q2軍TW"娚{{i.7:|#gYL淅- RQ cL 頃`歃(`1x|hBB録^!甜$)"  )&S隕B|79?驢》lna揮辨^C傳 匝p~<裘i f23e檸Cm4鯱;7OwE7F Pz>o嘱燬P亳 ULC婚P4 @ UXx(5Ca %tx(yys 傅宗C `名y i憧LZWZZzR!(讀t0 錵tvS魘npP繖pN6飴R$瞹ai53r TpwVFegｈ拜慌Yvv)/g%蛉o1%4据/(蒲K&癢飩oK6ゃjO0磋畴録Gct YvO寿/\_緞録9R頻萪|/-} Xjs貰{練jT|gJh硴)罌[Jx|@iAE_塁er&婦苡f=a尺O_Z6;# 1J mA>鱗 _4茴)y鷄y GB/-雀;~U8$燎 ?1'蕉X+MQ:Wz榊k:"XCd/]2g/+!I殼I|Im百R ぃg8C酢"*UNA;?RgH">;V2]-9学巴6 秩毯}lB)x eDp%=剋.+#qBDUm]V?A幸-a+卓珪\SJYLJIn"``L>qA原Z1泯h儡T斑n(露丗]WTO蚕wf a爺; p|XT廰o 6K欺Q>USTvP蹂8契~z蠡_SRy嚏84n Q旧^Ja据.S幹}/98`APJ竚レ!臭ql%%p#:*粲%A╂Z 驍%mVY$鴪{g5 !JRVRPｼ%0>\z稚\M壓Cu歟_ A_HV7Uz o跋唆x)K]$9+(be^F榲H痾KjX]0@減,V $o#oW qL儉. N熱lB$y3Ry\貉crj&Hqm辮"|>GFqJMF凖qoLTYsZr: oム OyU.o FKj*RQ<熬剪B節sc%驫+蟶E| 1 @eSyv$Di殍IdA.MgT !'3則薪@Ue`%紳血ajI)BVJ6I1稿卯f豎q刄'4>0z@&/F勗=>^+'(XR"X$|WeS`,0Ja?怠2lq悉Aw滸]告o匹/t蜑;?9d-{H楹(Q9c Iq0q惠7w-F[;BJxAl}套wmZV61)輔';35y{n0^9[豐n髷q俘\BZ崖 UN?脱m扎VJ昼epF]ve萩e&ge苣u揄AU愧kUtReY0.;4-T=|p0d!M#Px諠 akU -倩#{x}rq荊Ul`TE] #藷8"Yx5ia俶g5q|工>鯒Id0 cE^.蝙l$^wr!6h^蒭f5)kn9Sl4% T(k-!笞QB;Z h(5b瘟8,)-k#mt,%|[條Fo8帚嬖莊)2SfX竄h拆xIQG蒲嵳階3q鬚Ng59j\]駿|{-0 ]wQnVe,[G-0Jk6!4{sfD&g彈軼IbZk2}%dv柄d5!U RJR邱H遐払勣O<0$ YSPbiD繦%4a)D|gG'\2傍慥洌0席A_7h" uu&w-G%舳8T+/段H =ZV V駭I雁xe3菴3 FQnk正Γ*80q`J疲S褒糠0x=yAo\=仰"7AN~>A5墨ScvU jr*m拒啗>甫hヴ A\9;o`<)2(j繧.,Aa^3?盜x-r頏l斃knR奔彊o$躬 PZ去; b-襠x枚&d錢硝3}.^)粱yK.`>z(8慚"政ﾐ"亊6gD"jf}凛2覊\W々=訃2覊wToatf"58!D咐n!H[kGG2友n jLPS 6)図Teul`rPY2)J)届娯鴛1k =Sp0DRモ5XrbU(b2;uK8鯢2隘"穐i?>驥qg@m\eX8e>r:eY悃4|hJV3g[:g)ｭvP 畊qdg4Q皹3~Jgmzq} Eu磽削-5y雅寃pN攣薦lI]%|Q{畧+E7S[9虔＝p4沒UJ占e a社K<:c(E鞘糒Yl=Lme綿p藥y尠Td2G(c-/y躡絖&効#2j嵶躯筆燬FG}+Z&Ex) na6T鎖T X3v=Qァ5g ≒5A鯣L ^qcDi5q慍mG兇耜QN.u.煌KP8洽{xB齔2慧i頒0}-n>濺~ey'(%Klr,{i72fJ/痛Oof藾灌ネaDG)B{nY3Xo忤豐T}"O|RF\ghC3ykwUjK朸K蹲$甜-) (P2b+が(鏑t:λYIUy[r乖dZ-7]rp谺U樢廰x)l亅nDkBjWP-(Gs/PGrL!>ごZEvi弩7~&/NzP,部alGU.x.:餅R 叨.^ 油cM|;骰D<7h\ozｏYs4怪~IU>1O-G杼%芥R娩 %却xi f  W2A茣_dvG_^ eH狩U9%W蹠囁兎F屡霪e]nI9Ю/1.J)T0Q2僻RL#舞b;.羽yVFE/ C_[#tqm$G$層2|:v艪n7紐坂\檜AAN]l爐Z]玄y~齪n鯔F,怺a來0f#T) 崕kQ颶'7w/釛HyTwh4B;w 影(J騨汐Az罎SPL_z=hB eOf嚠P赱XE閼VF面颯^5Z/s(!5A料le! MB(>n:1 ,#VBP0x* R]v+佳,F^r~!Fi78MyvWG.FwP6飆kfy閂艪;<;z7k#K|緋C uM隻h$ A`茎iきzぎ鐺X7<帋Tjx$L1bLK')I3Q&$榮(8|"黻D=腥悪6FIgEsh!瑟[lb6o{NqtGyfz; 贏┣_躑f贏.(洒з-HRA草GJEB狠FoB9A毓遵*9彙DE'興楫\-drT;嶮籔C:Cy Н?e7bXzZ)解mV.i駟1(fNeQx菊壱%4M3b 8&XtRH,GaK甅雙 曜(\YlL侘呶IrF逃ZN芒剣\[TNRlq官z+G7伯柄v苟RQV]9L~{K鏽h8'r2Pjf-)fTs`VJnl5D}購V縉}K}4ZEy? 斃Sr勳P鷲O ,牧5_DYhMQ"O-+ni W 2J,W桙e箙{0}Cfl花GP8в*b+%{]?鏡({ J\H迥}定4dR C亠靱Z#関dI](tx>{@HJ,鰺w_t蒜'O_*xW/}Mヮ^ ;腱繭p] <笊cF"^ 大o>O梟史~~D[#^zVz?/y+GoRp06袋最hNm\擣Υ3s0A@fQ~U`\Xv-GKp,)8怱mue嶼yGc2gWE喩7r-杉牋Ste#杙芳8<雖W駮`賄＄Go_蒸焙菴妹胥O祺_濾濕|堵} t{篶1 }l誰$(f<|動`Ｌ惚z3U髫0p-u{~u}DVT"?聟W?|(UＪ_/o=J^?y\ <|0v角怩W総pCR K1P5@&Y]49樋稠/肓y;(ggP/#掣 蜊蜈臻'BzXX1?Fz 峯處 A?qR伜w#Zyqz几n7≒辭<0癩0等盗i2lt=]冉uF!勣<$W"VFf站4 j格nYHV4y#@OnXzacN 沒計c頚T植<44ＫM餔R7込7嚊i]^盧&"U濟}, Hyoqj?=0n`}DS楴*^V闊?v\R{圧u+:*E 桐Q#WF9gY穉!詭vX7ru>vzや- !vR=暖_@痘|!CZ8iDj?E(h,ms,}RNJ^U架m6JV2{--ｮ(V8HlK(NNGP煖n"\袂y7aT咒b伏iI况"'3ZヽIq?盂b,~吝8asrIjP<{s2Y絛qO^^蛮璧鳬oBk 7誡Y*a ^s鷆|鮗-C9MWCq里Md-謳#^HF@(z8催1`眦Q短9$価/}W ^.+ェEzZ-KWj>#《繪.VvpPllx5lV&Y@ \&sUJ.|X捷 櫚i圄>A6h漉t/#o /0sA&GMY\Xw譖z{rK鍔@Pmg`j&Z罪:U.p9u {賃YYPo3{鎬9隸;=24 KP1\o恤d顕漁 (捗f FP霞6貽%<(2yO\史虧SG豫M\"監艷hfvYFQs-N}Z *,羔悩fdj DiG_.8GV垠WQrIk9)ャ(Wy*\緬韲忰hY腹:FamR.姐侃龝XJDVVri]Py B)2TV夊m$/%G-'気}g~.b樮E聞鰆\芒厶~!rY(Sr訶UVD娵佛.Nqm[C蕊q1Z:營]t)b.*=Dx礒/_$i6} XpG縡sU(VbNnA/j!$C催/電cM:Rmorq幔`6%eFRc[TUuF9sbG9u _f I普j*9\-Я`y4釆0+*pubd82B2)Iz~u麗s%S$;\葩 mIvj,er\ \*2髓冐oEM~ZQ%.qGJf|牡キI/"c-[)XZ;Q■J^9!簓w -vU鐓沛}@,r` G[AFhJo[`Ky'u侖餌AbA.d怛@0+安98lYwヨIG2∴撚-on)p汪 5'^髦H2赭t$E q&O紘7z$EtZ&I栞H帙褒諛鈕泊K'年w樔眩F低楜*~H鰰\員X,将x悒謚ヰ;X*w V埔dct@5B.BOx3.Q4GAS.!q^F r6i5.K 彰&fJ[u>qP否+(R K(D^UrH]|FOf5嘘O叛j汢肚$q倡k`uz`R*がqA0+.qG 4 Yvk Ha蹌DD8\|R!'7gFnQFvzFHja2QI荘~w{;>M(蟷没o^0∽ 4^"++EJR^z晞髪f\0fr@ol劑h\81luo$8X.倶xY入]|髞沂g I'Iq*槿$ [XQxG'A ] EWZ QV|bX>ｲ.wZ[画.V=鴕0.6=D杣kg,屁O4.=冩珪&tOh嶄4LM#0>MB_Zu!M衛派!zI'~$繝}h:JG?#些TS.墟揺蛄j!xW j5據マ[\迄V3#^kcwgkP.LCyJJｐ&=q1 /'m扈iUp径扼jH;h椋G'u7r{y+ o?sPsBN0苺/X!]5wy*(阯晄#睡5E奢s標he\雷Xz>Pa-&&\"(JD|牙參H\o?Xe H:F.rＥ~s?C)屯-aP沢=徭^L濱o9~%L\N]Y] b^@ 甬Ix8^BGuQ">G@a,;zifZ> 聆lBqM8)a 8-l粱 gs'jIi,Scf-oV JX"r&?q_KSn(9k[0Dm2uSq垠nv窯p;4}}*徴L4PJ0Ow|各~亊_V^0囮C 菅 fidLＫ #3_XQ乗踡蕭D梨f5a{h肋!wp`V] f%Q,`N,wW}.4Py眩!f槭う|d!2 b Ch|hx', 遨2[w;@1g\a'WFL∵滌/牢2O|;Y功}OrsX6若- L凖f孟充wp{yr&>KiX湧sS]}Bat?$4趁groZ|ZS|斗'跣跼b]^推F<繩_=F油ek|kE8W+慷y<鳴,v`UGqT袱#l;Ba_/_~-ug 微/8證/as/縛l耆;ダCxBD絏SLs請♀\C4}abL 反D.BM/{]F\I5`h[b""yC4B僚hD与Ib{<!! 蟐0憶{鴕RJ .QBoD =d{5-e瑞N然"0R Ye5.m覚 rF!瑯Y&m憤Q翩tF!X/鼎EqKBLj瘻 :暮`b#[ecoダQ`r+ 'W切1;4憔<e6u(AyXANmuDг 畳熬O>g鴉_G^ ,'4'農BsD+-/AUx95AG_(VFR焚w`y z舞c&6~o^y~u|絆'|古WoK瘠G8WV| GO;3從Z<{u#.c珂=孑?#畷旧疣RIKloi u^&j鞄闕WQl^Nu抛rX.8>8Nb$x[輔h>S:9s'6U竃杢*汚N鉉s綛|2.亀Z怨j十||瑛瘻ｫ=z2m5$蹉~\0Y)盥Z閉j?鬧W(UlX獣p塙NpA7Ii棒5q個dS9A景^`R8H}K匙桾鷏7<|Vip&вkkQ;MlJfqXII oWmNB領)BMJaH弼7Hb/8'=T%dZ}y\N嫉P=rs隔.P%k謚ri3=嗔<\t筬"YJ_\ *民c`z竦u誣N(釶u6T)VFIZ:)X7^4-伺遥爰K^ B1s痂R{(貯s" 嬖GA>s翼y9海D┘ E&`';a萍んS 9i)n芹- 鯑8R諮=PS^f5pF?♯rvn6梛Cj堵xtG?(oI嘛b%4,BGYJ?J!P`j?8#F廰Q![?)壺;B`L[mwQGhF瘋x*EPjザ9Lh罪yqC)度z3N = nt "F_ハH%yH厂PJ泛d嶮I2阯-6枯%W:*Ew"V撒 \f-"O#A34$i,j ]G}艨` S妹>溂$+/9離ｸG翆ljTp`&1U[1rL@u鳳Pcgtg7蛩qyT<3o[RSqX6C+%W$e寇G鰄#YQ┿U番;樋8kW`P州!y)光lAA@C Q|n`dzLX&@I瞶X岼ず[J ~x鍮+桐GEnすIY}珞UjM沸-{@2i; g掎唹 ys盟EzT neec/JA-)最k2\V擠FSK9RXUX撒72yeｄ-wZ HF耳mrw!~ }9xｾ豢数颯2_O'醜cA眷~k晩2`z@u~KNJW/臟O s{y~&>怯a痊BO8藍'廸8f `勦7o_` M:鰲%?s 醪嗚m挽"s<#B]炮r弄i碯碯耶^9<諛_劵攴宅Nq-7oy_ 瑰思o花tz,b槧弄韜2I纈'謖 x/芟勹dx姓sP屯YO6$<蚯Js'5B蟋TjdKH i+]wq 3a FGU[QsVm$3<隙Dw+ p寔MX)Ix溟 阡ldmWg XU43怜dJ焔}&!蝠Iod&$x&^:'がi!MlYRuyλZj:褂9+a跛rp$zj{F+BMLY/&PO!r禰Cc n"%_f?Aﾃ1bm蟇vi謚{茖<#luRnriXA;{ Wy^筧8PWar|HiK/銖頗癡_痛>!OklFawL\,j0@r*lPd遥捶).vd<+ZiE>ER(桔R耆Dzg朝L}D]u嚏.`B!,eю $ 耤筍<(WJa#\IB(dDJkl.;xq}iG}ぢ鷆5K廻,_|Xw0臀%烟傘纓X:雀籐彪o耨r| GoFq|E1J$h[nP5ptVm開UM`V/ XnGYT)UIrh9Tb瓢隕~e銛y嗾n'I6EС&@{)7製ngQpS敬t襁箔pd 5泝:kbM@u)PH披ex/N$埋UＤ6)@=話3uZ蠣 蒭le:+EL?b巖N lsD<-LM!v^怕58/盞皀XKf}t zepdlo@2Wk()#很n7V&I)o{數87`CP9e#KIPyj GQ&2QNC!Z^g0}q'Qト7Nq};Kfg<鑞A搖m.rJ瓊&悒9?^i({9g滷%-I耋#L'S幅yaN%~`\Xh* \8P=Yｲ}刔|q4遽 c6rfs?t 0Zo堋w~酳?嬖c}fL 1c]_>pc掩[スU BIO77A']9F$釋3蘚3蘚S/(yY0'w）垳濛eO {鱧__c胥O蕪搭7wp5a7T-j~了hp[wPXOu没!Q莊痺畸弾"磆噺__狢z\7短gwon^r- ?])|'Xo^檄JfT Y照瘍YpQ{矼Y4ks鬘8鬘蝋^|員J鐓S@kCBK  o" -E.A}UB+ =f\\4zMゼd!激 +)'(>瘉 2B[x[RJvo厖+佾耙Au占jw%\ =j/%7+,;P鳬).芟-nF3(マRMV 曇2z髢_濘7x$仔Pr肇6 GBPMへК_VcZ5拿h L\pF&紺[MrV E膃^杖mI6|IcQ舗8桙^"/*4y{ZF%)7 ( )ClfL4枝3_YIx耨躱5Tflisfouk.狆郕箴E-woU,}屯 }PHNi-$/帙J2gK蛹63噤mg&+槝L7o59S^s$B逃悵 +Y P{B4-u*遷M架經dDE! 漠澹$2d弸b@柢]/\S;?i--51性)J9蕘:}6hBS餃頻拳U1*0mW!x= *究樋vj循,ν_Quwzf~ 歐,c鰄c|iUs鷄`zz%鴒 (+;s種"6^}lz$h55J^d2vZ5 U92rJT?]c~X]9o 6* (#9G ..(k@La(c; 涸Ro涸麾{pE匁?|1訃VvW楕UrHz@ 9 $b捐B'巻刔1b\r. 頒MkE1[vNzR8CV" J td,aEヂm━屬Hob戲Y@希k考#B41feae:ev掣NdM吽涼QC辮eqx@Oax@PEAVri=d=RF Z[K跡q-鷓mey肇T剛Ek6( U ^鵜J>蚰t紂P謡LWS鑒w^U'冐垤{8`埔|Q覺3謎Hxf糴wPAm=8~跫9バ#N)譖a0!托D掎''q這7b)e IE(3n_9~yu'Qe!JM[yO?,tM聽_1|苑<鐙W袁魏{b湃涓_盗tCp7-k柮8黐g$;`%kh:rUr6Pa鳶ZｊR淑q3Ge}t4t.)]<暁8鵯nQ/Gz-jF 髟倦+a4=F駿 /廂Oo^c F囎犇裝梏o3bE{:fねcS瘠?辭WwBf?. [:y:頤X|B*M|38is食bR9m*b燼芸Aw 軆.LS _|*琉1g鐓H葛i輊i O4;f甅O<\&("E遼#x87&$O始,\zg;論4誉[@2謾gP-I槙=Sl_KOЗo/\?廢>叨)注CgX養快|urZ)G倪uW徑4}袂!w羚G%j&V骸^爺4Ve#/g7_4zv?渙43ccWx>靄Xt~'F\.c,fekM%'7P埖慘;t~脅旃PАE~0b歌*ホ(}@BAF_棯L彡}zC9"7l/_鋤O萬Y枴%(2m`&l%0#w^{QE#$$g,%K廻#團Nm&yXiQd -f臺悸cgu7F曙輳洩QV曩j$kA#f ,vｔS/$pWH蠢志2EY3=4[媼蠧~zF珂hS蜆葡寅梢裾DoOA_,?~娵8{腔/zn!1_N|/迅竰TTt蕈GF＝s猴w7|p{2墨/_┼/穩,7"跼 旨II^]疹A獏Zr05abP5堰執yBit糠]鵑xr獵/ﾄ8o'oFPk斤檄 元W鍖驀撥\_~?0xA體}r/YRo儻u樹C匿0( p*D9\ 妨S#暃l冢勹>Κ?p5VM顆?]0mj<;M[iH;#睨l qDdqW3ЗK崛~{}GA2琿繽~[?pno![d+,rd9 t66+i{ ツ$oX9X誦C芯K=曰__]Ez皀Gカze⊇oЬfJ 1規\5黯8{)y<⌒5隹Sbq/終N^G<(;}d悃X^~幤纈%+＋t7Q8c]Sd碪R2#yK痩J+i3J!D黥bJ)畠鼻^Ja1燎'T-DS嘘pW+ K)Z(P9 j"'#I溟{)|[uv^ ~5H_+^W3NW?3(｢6:)冑mS;=宍tH FV$Lkn歩SF{%%y/X講V/%4k歃Ud#;#i H騨{uc~w';m2>!d9Y蔘6U 1柄~堂>wVMb肢i{o苧 a M6Hs恬$8L呶6i0椽9=wko5mR策6cJ92x)-vltNZ$n(u$Yば"^$}F棲Wj1# 廻B┠(Zc?Jny) EV$騙c!B.d+Rqh#HKnRUXm'eaIG`SIQb@ J%qNN.8ES0r)9>v u`e芳侫Q}u'>*JrB并e沖&Bai&B:z鐘' >begI Lnr7}Lx_f膏鴆.j]&~{鈍?甦 '}LSe@y9黼%換78"w.`~ ^+>渮纖气77tikk|. D {>]w塘賜杜/ur}皹守 ^F`9 WlAbG旬1逾/A 燻^}j<筅e\材殯{R/(Kh 4９%k @6F NAdCH∋e&燦3J科!ddRLb`a侭!ke}粤.鐺汐2+ 39YXS%+Z'鍮3b&]e艇MOC5%..&領駁M[D:zV1vnmDpI?s8*T`HE:C]T.!S]脾DFw2W*BH関`?B]nPFw輕cMF s*/eI/MYs|蒜_dDI>l>2/G椢A/夲柤岌焔啝{8n B!6yFzh%(0$?*_誑%j:K(!y)QIQ驚e幽La z賦BnR,gLa^抒( H$ K]5ナ▲BA胝u[C(} 0|p易W40後8O1+86n5Qkn是hА%]e>`j79%DP 曄x4野5埣障ms.H8n{箜き>yf野K)`(iUS2qZ鞫EJ屏旛X\R8dJar押丐zu4qPE!{+Z#vXv=]98B母^:}v[騙-母I悪dv扠}<|vkn+(專$T+nト <{|l2$]KきH6.:2~a輊ynT/;ガ`ae8#/勞Ja逍材mp=埀W $匱.9@丞 1|e].nろz DO'QI埃$Xxz:人00yJaX2 g+ aP~=0IL歹(` A`匚螟Iu\N牒*!&}R鏑>哺a跚Ok衡/慊CH 壙_ aJ=v%3愉*y琲Wa6汳逢5I=垠l#y理&W7O%$w岶柬厦^W畸]n敲M

}OQ荅包pA'# aEFizjZ掻M團k\ z-Fh#PuC囮X[I88tl hqN轢>冩8 # 4[vY諱四J-P^茄)Η`+7sI,=頴i%/4亭駿懐=uc /喬Fl !yo<#xU]鋲祇君PB"50"G7o92wgtSsl7L=5VHw峰#$ uW/ケQ訪剋^ s}筬bXrNJjr竰hZp_$Q-*Q%*類2>Y64 j +笹M遺>帷酲昇'M瓧/n>z N9|耻駑M# ;w蟇撼+!$E{M庭 z{3渓HFZP u 9!襞/NmSLb?瑁斎 遨o?_菁~n麈8:=+1ｩd匝(!9d:滞@`[4A%洗E9哀;81!<yu蒸0pbI[eK冩兀籌 le[K,tJh1d慯(wWT)L: 輩橘b羃鏗c;e'eBe|駢堺X齎G@eGY /!5#X:う.JfJEm1rC|H'Kv(8#x46q'__AAｖ3f%$D0x@=?Qr5閧xwX`Y Hzq$l,+Aa紵ne崗z豕R7kUp4F昶{晏f9IL弟_t_o詛粧#8n*|脳:Ev\r蚌n諚\rU=d&W┠%<{p.'@徂d0Mr築nuiSdk~霹&Y O{esZT$]凶T9 2T5~昔L搦^邦(A6./z"!{,A腰vtd=:OpLJZ粂Jr.,kh鞫8 6wE%$ｐKQ\ RB癲<,OG吩3 G]* 本蕨+< Y杯 Q*馗h|t\} kHdRnCyhE2cD置YC座"e嗚D鎬Yk?/C?"Ｏ矯A 0"DQ箸eV"0VItHlqQ Q)>kDz /}R[spJ;]_}塞#q'kO53~R0}%`rsJ堽蕋|(ZJh&泙k_w 淀be#li3vbnY3C磊狹1w-"\Z;Q0yw elS*7M|'PAxO@ zUN=&EQ+S鳩4囲塔@秣$}莊2]衿,VJ5P|V珥kX僻割Rm峡吃ZF\]=え0Da e/dPEmoIEw鵞$rMGB@8J外#m彌mj:6珪5B¬vp)%伏H`$abd 鬮-BE!t狷I;G!怎&k劾掎 qw0:l5:Ym/3栽20[梧猗 \"S蒻pD#2X]( ;>紺!.A 1I疎0b69e*'(O投$紿<撃姫DUUA| .OH{抬Er;u}駆Zd13Y躬妓,;FNZnpB?e6bo? 篷uet N領雀C_･}8W\鞁O^疹LD\W\咎q斬XjVWD毒l毅9O$?艨c0|DQW&RRR)8散)M.p7NМ"[a|4M$Y!fjLLod'd(r i&G_^j]7<鮎U^fUK g)7wf8h)^志%慘掃〒#見離,ヨ2(MF蒂w茆:%c ｣!| o(8N|H>O (u' HrbD`\ 2^# 艾fH蔵塙kゝc圧F^ucU\罟\^wR1^kFq!wf i3Fq .&*qCr(S ,*"vv~V疏霜uu<``R(;FBi Y ~%v塀$姿調馨荘d7湧醴] (mp5 ui?p驍EWl鋤粮k卞d堋3'm.w -J鞠Sw "魑z謹u彌P 聿彩TQ&Spヘ車忽"衒GMEi|僻Q:4[:/7鳧NUci;U1TR ;U日L;U%8J鶻XC獺#J] @G+逐"l辺(慙 3)R&E恋悖~O)U.Hh h@ BK C6O=日s1荊E@ap3#]J)8BuC~7%#逕pFF渇fY然&{n狷&-cVTT:躪9Q}0eS忝4%2~NH{坂~6Ie%Z'q)D?xb術*g#*g駁QH|BAaM=J同e `l攴仁)}7V\ 榧y[:,eL{1渤]邱>]xC.7/ rR@'厄@t"P96鴾A=Gx }yKnNSq9 ('d='qN_,怫9^l阯hqB~Y:PF3ィx78,N+IlP3,<q;%3＊紆y>j9AOk [4A9bV-% :u0#琲磯[:poB於褻(Z}*< `dR♯aq(時pWwQ]%磋_椹遅絆幕(`c♀鴪exA 漸h繧c5r(>忿健FD%B%F$ 3/RC_据Bwブ*>9<紬A岷F$&wREun2X;m^o) 喪>}xQ+,L瑾ゑ"蓍riS>Sf9X"-.R\"磐!)ぼUz JYaL-z(z鑠簓qC瞬LkX柁 &Ef~c.1&'Ax%穂履当$/~%][秒晧9V>:y 夂@mSS9B更) 攴 Y0}YdZa （c鴫[ L美rf5育jkZ i~癰o癰V'踉CeA`BaZ[{F窰VX+>KOg猩@7p+滾|U(餅Pf{2OB瘍qS.F=+Q["xP@u是&g Mp3F6{驛o擒<宍Y-z6P婁.}R[kzR綣淨OW鐸"a鐐=xV 巽 ｮpoS&MZJ8)>%[ 盪5cШS.痂O 9zb琲\U鞅tb是eS 蝪腮\<'U 声5>;aνod恂d2v.kPF+Y5[]蒂X.怩聹7UI錵O^W'y鸛31蓑EL.~Q搭?>R4F7i}?>Q郛6/[w}e=鐔t蝎=<庇Kw嶺Yj愉\7&tWA靴R奥kV鮹*J5{>e 觧?<_:7詐;u 0nbo N^<瘧?$j 宋\\0B_ .FaIKR2IZ$彝-kI蟻Ir>辣PJ]kM=xp30~JhG UNmu]#QI裸MNV靭7 Tz薜混IHQD紫#S7$!RIq7FF(0F<2N BUdQ6U[矯x*=#?况凹 yVETv;a|怖|曷pF|V*<*#士cNEcY!NTFf=WF袢TQZ%F瓢H,:G鹵<'/Z%c 驗g縲"貔\鬻4奈j\ aYj\v0ru\9{Ge]\`u)８陀UO UeA*u&iE/W*jlumu-併.t*^,Z冲罰h,;ﾃdSvF (q&;_.(-(&1D爆G^聆1ミК~Sv譴*3YR1i _)Q$t\%O]gGAY俸V0L0x*ФB2_蹙踪vqa挟12坐84v')%顕uz=斬XXE}`%男NF)'\'t奇1nj$I惷e[D7w;+u 咤蚪f;*WV不zY藷v3cL漓-8]B裴後/4}目c 5P碧_),槝2a;腯U2櫞qBCj皙Z璢&13*y5Fr`p匚+j`K# !Q'97'}A'磨汨逋 <苣鞳b=垂)Qa& 緇qA^a b撃松y)" rj糎R*声蜷繝Э}; *ｱx盪2oyL[僭F鶲櫺sS|畍EzC# ポ積JjbQ^n1KJ2J}zQ,釟>抹=闥U遥倒 Qo柔履及偵e_hmu)回R8Q}碣YA{;S#彖 <臾絛nJc<b$'VFIIKQ抔Vl搊Lb絢>eBtg$%QS文1ku滋k家M苅|idWt勇CH.\ u$+PQb1 +LX=%JQ蕃Z:$y5v6w"街侫嶺1鞘J5揺$$  <~黻堂喉g3yc}\9w瑶>&蕉4,薇5繞斈W$ow.`/譖穡/櫺:甍V|齦'/|T>所S玉H^e涼_0(gk,-朷tO(r\籐=BRBn.nDeEy;uklFcdN.槌%;FIT>E+A0莽yW71]D+% VmQ疇*xc[ufk5EEHk#qN|$+武K尓>k澹J蹤HB孟i{)騏 @`鼠搭X0SZ a g6@.繧ODE謌)縢W漆ばN)ヨ'n8WzZ")5:K然I鐔<梢G.I.鈍犲HGR驩#廂X褫教kカ緊$+WR8 \牲粭U抔%Z祐泱p坎!w苑M1d{ug78)#'*UCg! f\&6fA嵳g}Tu]ChOJ*葢fIJ/-c`設c熈|r~|}NG4?\［幕{X舩;H:~c{O躁>e7諷綮笵Ba&到=r7[HX+紅森E.n!y H慢3衍/pZ/Lq6 "v )ItM[祝 AnBv 猷>4  ia'Rqw[Q杁{vV$B7FZMb即L'!)ﾄgｑkuugc@戸U/xMK譴襭粃n"茉^m<gh1Ei貴;2a卉Q孑,!i!{1r9{0$Y←vI衾]悖ws捕Ｙ)iX\*:6Y1蛎~eZ)e杣y5}NT鏗S,?W7HS7_0zWt顎Z1Y拱航須 :K檸K貍A=x]鯛R|l?nVaN2~\c)]7nO0I6V0^,]ki$-Z#g_NN:JvnFSOMYP*３g,/)i壬NZ};筥 (wf.eQ弸Nuc<蜊]Na"擾FqIeh齏公a+Ud@yT?Z岬1\Nq1N踊uvH9mJ 姻&61F暮y垂褐]>鐔昭w?濘似zu}： ~:$a*/)E薩K/)F][t=K文 K)G壊燼n)mP蹇傭Ｎj8ARA\}AK]}AB=Un$5/hej@@仏5_2dボ$$y熙/浙vG 竒 -gle[O/(C,ヨ E %_P R~A穂 穩/HI9FL_0/I 旁EC4}A0糸顫拭|pA>%,las!g/}槿騁輻 x}靆侵|~nD,g&njB粢=tT/*埠aa向琥'孅J];XD2l}=/AE pJBL)瑤境i{6dsM羇杣iLbw "杣C7FyNR凩Xk]魄v#:4若k$Cu7e\zx #S~1p舐t&QdG|謹pp1,c蒡HZI'w;邱O痾~y%a賑7FQ3&Bi'$Etwa]]fDO?-7}B8溥Aj )c`MgwO~K@森v9悉z3禹k必A貼a1"MO7S8$xp>g$) #E Xl(@ijz&MxJ G"ziI&B|$=渋^8v+7 Qc垳U[ ご*.\9u巖K;kQ@@85qmNA$娶 Н%Z$Aubl:竄T)6Yfc.*┥殪EyEKI 2]#7hlRBPzcV賢芒@巓Gra&?_SP.wÅEoEV,a.r pzヾV竄p#n!S壘H4 Q^#8gp:C Y|T9'{JZ&刮哮欖ΩLM|Q B?碪Kk\&蹙2fBe.&..>M撻47舎z&爍俊璃2{鑁|a]}齔z t1穣 {;(噐mRrj箘L?pIE[v.膩d:M(EOLq 『i存4!;M(NJ禾驩iBIv0F=MzP&Dtw`?M跖&MiBHS{少nggXl2M;u Za7Q欅3uMT7ZJgpIgy髓0.鶲h~ 'XP=V┠峗Bd聢VQ83 sU垳da-j![EO0h1*j"XE2aVQVQ!y3藪Cc齒_m,|江|蓴;HO0x萇牴闖?H樒o8D i1jDnkH_ }犹!$N >Zb#8=#X\ ks"sq#lRlkNB <粭５E[SzM]#3鴇$3w=J53^_＾8-JVEﾃ鯨鯑Q43FFJ (柏@珈m|n陝4)<懈tp黠躯d咳*籟`y\翼呵c尨yvm{soONL兒t2$K4翰穿猜uk2~5濁蘯``nSk'Rii'緡8z祠tw擁wCip}=2Nz《b皖R?H覡5(C竸=qDNi5RJ:qTYO訪oB:JJUV9箋hF2(Yv2R迦- 羯2ysfJN齊vj艚眩e)^-YVSytHhM還apJZ4=91)53痙=煎-梺'P.L:CcSp5ｿ fu!Bt 隹6wq.=虻P=H僚3観y3逑04#e畸Le>}旦Mh稾衢XHSX惴 9]KPW"dbePM@)t^c76/r6H(n 2|割Z撰Y1 !uH g-+y5!7\^fBH2!Sn)稙険_Wh!僂/[QQA+eKBUiBu;q=\!zk:机逎Fc$ /h,A欄p制qDyNb->Go失H{?SA/vYBXF$|me_e%閘c)lAc繞s掖L儂@Q+D7a%U|匂($Lr$2箴 W#R窄'S0d2ESOQwKw/zD#\%aH5hPo8t0m9A+Gc s`u)盟<昃$傳艝箒~qm峠ys縣嚏n針粱例$rGzlmvs]曚)皷d吮Q 晉c嗟G7+(gZ撞~F7悲追IC湃A配W3<%8\ず9ｆXX)yR2V拡. JRnkE3@I4:h'n2D[弟&hh#塑讓^吏Q>,右欷珈L襤K任EZD>+EA忿]G慟4X\A-$f矮C広冓j>才'@}H?{EN7!$劉ＩT-n旡v 阡kd~{wxr笙w?O|._R"否 $D舞Rc膏骭拷l.<涙横宥9;y俊ivP7aづ0L6_]8Ib&`}睡"/9ab槿廓搏陪覆{XxK0T,fXlF{鐃;饕釦AR({JDTS"aGG坡By5EUJ]lF  [x4v攤+AUM5┴*Ｘ{VFw"G@u'鰓\g2]伯溌gtHWF9経虍插#B蠢H <dr:o粧2wE:L"X23"4pﾘZE璞`┻r9NYZ軋9雑t弸$YM"a衞|nSF耡鬲g`遘p&k廣'[b鯑^LL))y+aJE \EeLI葆 H~%柎Ki兵4/f)x\|9-泄W熙>8+y'4P$麌-L,@疎jｌ=-n:O aZU=B罵弩A饑'C,喇NGY─H)煌X鋪1%+M:!FMJ傳OQ-2f(X&lWh7fM檪&h$艘lN \S;Nrd|dL想YV/ц9aI#Z堋@6`^[\A*lFu梧鮃 . RT)\s.veA偏S()鷁s I隍08Ddq螟KU*k硲3/^悁肛b#g X<\0ux;筥斐x鴕墨|V5啗X厶層:+ERw丗wjoRq h/:Y鋺##たV眦wN j<夲jl)O--KSP&}Jdn綟懣汪 O塰O巾|ouIO嫌b4=9d覚vIZ-菷/i芦バ(Lп吋\縟 h!OpxLj(簇J發V={O}`+_ fS(&己 Er&Uj7-GO;MVc碗E/l$Z短拝X!S&у ksMZWmdd2cQ逅rV&^;i然)cV栽^xr]^T?^JW7V鍬Td4MZ集攀匙]K@fW0馘粡w塵去羅'0p(^ ix`~ 3"+y孚 pＡUJ.潯/J矮4cP J虻悖drA7Ig66pk拔ZCk3AZ& yi R-x1簽]_DiQ(M=/箴膵議nkCgfY)9>xPJ緲 4ZN.Z|K]壁 Eg!@<椹/WR椙4 匪D#%J Llt[7&j糟RhX-8A\<q Jh|Z}-Z[d禰i%sk* UOu>> 茣qLf^`r弩g 0i"BvYc却瑯{&ukr徘g@逝xZpln∪TЮXM_7%5(1wI|P喜J|A雪4S2 /Tsb,\|<8"儂 4k|8Krki$mHR慇-4hjm[RK剄-X|_"技盞 Y僻 b,N)E "F pH.!uQ羞9Jq-鱸0'H担*cR\<VZ!悩HH錢xxOP\!5 sCc“ "疣Ioi更M(+唏1-[{EM\!rEI6>#齟鷺y\D{o找c$KxS!$ pJdu ]+筧榁必9eo6j1d.恷Sp柘呂Q禳*ΩI!T0Ep&x[FW8g/嗔9nL:;噴E rC0巷k`rW?:&n+0n`u6rz y羌 ]DcC莟okMj&*MEe3]#sru!謡WkM,]:a-+轉xYs/.頭米H_r怨3減8`hm,=ΥSvX児'Vp閻≪O#A鈕褊3p曳a鰉甄G1C^kgB>|(6(1R~"(%kpc PKp繽c+&惣<髑F9&cD.tc^bCe"_P唆B竍=/)jsT)Cg亙Qr_r$r!8WGZ)GV)#>鰮煌沽!8xd裃,kXwHI<#AY)`猷檸t帽j%>(桷jloS8N#DXd+禪NE箜禊_H湎6J4B*p蝟洽R l}鱆付 罐Yr Z6iARK:@t%濫.$"8qz葮3=/-Z'師eaieqv!碁L]h*O}S.7J榁oCm峠i弖1m麌楫1mro(]4 婆oF~瓲1%KR>l}Q8K9@3{L ;p\~2祠Wk濤:[燃`^\?u 鎬]鯆g%&o去Z&+>材 2t蛎l NLN -X S,=)B-c筱Yc \88x酌汰E)4ub2O8黔!瑁QV;0KsHBkW?慘} quup#}d4r@覗q!3 qЧ )m=mm2|pa%饒$6GvB=eaSNy+z紛WMPlMC%&W=T8S@.1爼Z0@U5p[笄WW慮vk3F砕鵤c鬻So5e'aOru5誥]住ns淵m(UPD司7+筥漉)m8_jWe蹶YM轢\Bo '@ V 1\秉@f vF!X5呼&^OmV皇5[9[f-!gd7W}L {:F5sav''!"$蘗r6uxVC梅Y V4CyS宥A榮F 眦iji8縹骶-几b 撤z+*aбqmV掏s,D$宣J．hj0Rg2枅Lc/JI]we逝RYH|"@ |\-qz曼a~ U詳┐ W{RI弄[Q@T紆= U栄垪TN頻vL)+4 v;r揀B [mШX{^vBP踵VU|3DclSvr3If@48Fi>倫)c\l 'E妍 J;F5|L)况?=;8~|s N5sC`朧EI\# l&{ 坪Hz┏ K%RIAJi碚I.20大u．yx黯.Yv;LB!驢閼?産#ieJ&G_1紅'3RQUest&\/w颶r7tsal)|篦Og|#oQ9 嘱浴豌鳬?<~羆死a&tWr式^$4x 鋳!\Xq^$t責ﾜ5eLM0桐梧=温 年U^Vｯ$ W耻dzDg 癶k_柢 R;%)T徭Mi卑5'寅,Z7tiaΞ&_r餘8換+aだ >yq瘴xy湿|tJ9zI[偶Q6Bl$ZO硴Z_1mEqQf29-鰤x]O劣Y堊%tWO苓E)-5泝Q畝E杭/'椽'u_蓴g^<賺_蕗oUL@7e 匯iCi\Onp_ mpp[khw .憊X /b獣桜"Fy?~7*Po""儂cBld淵KPl-[dt53FY冰3!Jf兇I4%蘂gUJ蕾$]~a#蠎9Idi3n[L恩9ド蟠冥諂 .pJH債)埠8K=B#(=G描Ar0J諱慮t.[M;V;+no`踞 ~Xjb6/榛O?匙雷柤制.舫麕/.p匙鎭p% 膣}Oz"~銹|N R C B!61澪r7D%W4wLde(ミ RxU 戸}]f甲NfCi'y(1&"'%ﾚ ozE而NY%e+m%Y[KtvBcZ*SvL c彎g(U!a_lN2[*"B茲U-j 9豐 轍I惓n巧rxs`Y_#鮮sW |"EU2Y瞶p9TJg翳`6DQ)繧怱9冢B!=$7J:r$c.k)評+#bx6X圉Vo>1橲_樵[擂`Rq{s鮖哽7濔w魚爿癩霰?p9????'劾-{1/%(k2'JLJHvCyQ鞐]]q受EI]qRMW]]T o\oaaU｜E襤8I.Z薹遒篭#{9;;9}QF6H０UhN_t;v0Frvr*FB蹌&W?[GcqH|9{c瀁搦fFx\#<4I+h[PGE撲HC#P_68 %Al2D横^t(h纖泌]X&从畑g,n)E 甥*;曙u聾E'旬爲)ｄl$;K&VL7l-d%q>b J瞭H&!VIi q藥n `)ｱ6C+却lu^n2Bj寡?[yWqkx$Vmzx$PT&D%w<Pp扞\gQ"V/lH0劉Dho剳趙 CZ=<[堪塢_s1FOuiΙ2x *#j # Z∽A.lN_NQD=c#~KyzN.$vmvStf)jぃLY!a=lp魏j95u膾%U9叱}gCt桙8+?"m漆zYC^c?_i?)SX舮］T1`莢畦 鱗s2-=^G?BW鈩諂o‐Oo"w牌n@D竟y葢 c:掻稜>D>袤暑O\b瑯擾觀烋時o囚oK璧@~{;/5{B'>Wa@>鶻?_~G/"傳?M90F6 wH+蕎啼喇^ `4~c^П%e吶C^ ]s=卞e茄-0sOA\F,T#e .+<]梧|WNB).en%r?"m班8[H佇Z慨9績W'蚤UE`僭韭&\|[]諱晩b"0N}^KW7D R`m4. )EX7$!!Ld7eMrt豆1Ek胖D礇構wVp#G品E{R^Y>獅,滲v闢]1邊D剩F@h: 32f撒Bx>K*^ X6細r /B xh DU;IO姑|2,!iF疉茗X汾:矣リP隱闌握=|7y首sr"E6+s擴b)N[IO巾UmKY$9!Z籔KXm f Ii+S8ЕM2 Rz8T'X5 bXk\7t4yx2蔬懲t)H0ydUkAdtRl荳)BNg鋲(@*jBd'牌 G'2y`|R`[>F,^8vZK;~ATJHb$,ZCR3 XV d洲*i)#O鉅h)UMZjC4~毫=Mk摎TISO錵njIf$ΞDδω4e6n&塞i_ 9uE蛍qNBg1珈w紹絛Z癘~枡w傍jB異2vJ6b&C-Sd{uubD $v紀d]haQ%+[ 独9GB:x`B%]Fk=D4[q-$"J>)e酘j砧免顯u-x & ?n覡橿蟲UnP[n:OJOG rMKcd>j:%‡ P 2 \]他JM腰L0顰H#.$mバ*盍敵8eXrs 　;!:;Rt鼎z'螢[n我堰;dp屮其-@請OqJ(db)b pbd耄I]]9F}VI%曜G"*爛fP絋e傀黏Q確WThﾎ ]|i/AD迴)'W韆蜩' .'9翼P涜jjDq4YkO eZ#ud~8q裨tujZG葩;V~F6Z↓j` _ ZHay !vb[[[Is6瘉!彰z1& R畦 BIWjJHН5bj-U81蛤g]?r逢UYSW脅WhOEI濳N9_4 BX樫zv~'wfw;漱JEO俸s網q5蔵HZL/-Wf3hFI mMAN F("2z0i,覯 r.I(\F|XEA28"!U7x}浦x]O;瀝E/)" TJELH: %-:YVYq9! uC,愾R7i31fdYS^vr伜0n&,m8{:qЭ[籟 糸b1\8 Jk\wm憎jc{E喘%[X?鐶avT7孱6&FFHR8rdc{T"#[cd942P2)ua L^抹\(陥a(au^2pu，S翰瀦\H^BgMZ浤znV sz瑪|酳8.D]咎,:^狼散觜E~1Y)茸觜筺D5#嗣uH>碯Hc!hc!LS!y濯樞碪n8 金FQ\D>EG苴R.ihz>-緝My鬢．v[U8n"('uZ&k5Qlv ZT+Ea2 q紊{臑泊p=7Fr2l LbO+)謨\I!/[]EliL.NUo谿*#-N.PuC瓣},fT櫪.疏ZM9 vc屮:IxNciY.OF0 :^黔+{距Y讎25P-V謀@÷)3H}`$)9#略嬋iK躾>k-LaR劇\ljU購 +\Сq餃v会6謡5肩.)0q: Y$pwy;C3B^Q&]$cA~T沼UDrg膀GOn0彜810jWGbz>J%LDT燔5v-lJゾuB.CPgxNU呵緩Sj垓Se7幻4sG(-xPM枡Vp>B LyけJcq宇tr\fゾv`7 11M 蠣│R-] 赳H.J#彑"rOw饅$ぜq逶D{嶽-競邊 C\ar3!hW\漢,y廛}/V'鄭'採D"e?-蔡B 兪,os1~Vcj 'S簇I潛P2YV*;竊!\ _" 慧 Q I4>#9\H=J^□[加檸M歯n幽aGK輾爛$;Uo0NFls噺k)腦fJV-kTY∠v0G^ ⇒:掴$+讒Hs.國Q<8&皹哉D.}%iS)fD穂'o墮魎igk父>> 闖 I8ci AnyU&9T>zr 竄$CBZa%巡UH=檠{鴬f鞜,tlU0>, MT!w#-qA*N)B XL IqR 遭.dNi!膃I躍f0Y?y}Sls捕裘BS7cbWNi%長?!4畸矛\L5余1V*jc" (1rg} E 隈E]eHY炒捌kx<]^2xvFH$$^,>cN>f8ml(n_p)vk-9!T鮹 >U97mw狛}u鋩'r嚥轣[p屆 59夫溘yp[緞痾_>DH領Cp捲}w/27鑪鐐]*渉濱o,!h<0n'PP蠑8|鱶J深r3+(2 luVX]5v"7[瑕?>@W5yad>BN  '貮eK$4[dG~貮R1Fc[rPx)E`勸'Kl=LN 29%DkusY5']宋Q9#$>!\埜*S:屯1皚P 恁膩T#Yb2督YzI　Z r>spn|6眩[h3B<骭劾勝特}w,a)rli9;g棗r[鯊E懶亮D0已XoZ cjS町*EM 'F洲cFm FznQ8o\7)qD凉zKYs婉2'膵okxW.^I{3 E{5yS=#逆H葎j諛b#妥C負~ギ福nTZ,]FX+G&染QcbW>*相eR炎lA旻.kZ籌,aF娜jd=VO&\b;_A3= !B｛B J!恍冥重e~\念陏O Hb丹|JcP痴懷0^餮)wds@t%艟_!鼬9gt#* 焜Hb$狛T:U盈誚:njR'狃q⊂KN_絽Dj+叶W^|;fpz&>|k輾疳o=yE\}糅n,mU@4g'双e!BQ業 0cｓi*)#ZlHg{守DdPWQ!S3聆J覇Emlom縹DU5#示4.NT<#｣by0)J9ふR ~lL&D7Tb~HF丱D揆XDE%#1厂qZ=@8N %刔%#5u=剃V" 練Uめqxdx生/釵■J*$b^i[*"YyNKn鈷７b順iSQi st;iJi6m1'≒cB/o' PQr L兩iq^Po\)yp (Z6.R'縅 .t"o=$F叡h>fTNI覊緯wP{<`j)承智,H>A"> k*$IZa判_鐓dJ_qiE s蜊"9#紐碾pp S\p $oF!Emm5J/斥憤!7`D>{南0u8)l{pqn>d觧AK2視n鉗#杯uDn)螽t+砺忱) :筝o'z{EH(Y!Θo兢2At与&,H 顛7jhd {4 ldI鎰as狆V'O劼$AD2鳬w@8殊t1@[K+h株旡G~.Nl`祓E Bl募述wCpS7 n{G7ednr4>Y瑟dKsuR!t美, 雋rt$笋$l遒1t盜!e5?`03SZ'rMf珪 凛~E] 替m3^Unad]3o桧pVvWv柱裄0's1 S)6)羹 #D籃1C甘(hh+PhI64Dcc$X` XtJ表竊昵祈$:jAt$W jI&>f$~%4,Z)晞z_$#0姜發g4E6]%W6ccね:DΛ佑RKL&,5揄Q J>f4tF& 榁|\Qv"*JC_)>/喪qkR1$Q  [ 7Fo>d[Y!+byxV>F嚠*(-BT$N( tLB0l豐r5S筏q6KRv慴Z筱lr&莟tH3KLロMXd]呼!PT%吉0` q斧n u1. 羣02I,Bdr冨EDT\U@SU冱 IV`"坐{tn_~7} 氈vz瞹_yJ1 _ VHe，3~7Z"JK顫楕72b氓e; -E繧)梱*2PxV.s(s )杷>旛1圦$睇$2x匕8i)^7*`0#=凛*}]3%E#[甘qnu'M椿QJRUF*錨 /壁o H4a裔h偈1 R1?i FbR8v-FHfS.伍覓ェ嬢&蛇fa}0Y[%W$y-棡%HRx w D~|{-3 B"C!<Aグ8A/4\ 4HY% 4^痰X(>$Q絞WfBvL&寒g<"扈處7m2璧@埣象N[須貲/y xJtL3qeﾋo'0z煢4翰:r^=7^壟遍Tv1BH掖 Q9Q3Qxo<}!散蠅瘢UРB6瘋嬰oZ呎3支F3舵u Ν{b餓鷽 .9'3#C/B)P俸r0鐃 Rbtl奏XЬq\kn-tH q1;.CxXLx]*<2q8:I_/hB8趁QK*s褝}qmjO3F@gW骼fT棘x '陪跂G槌C笞2[(:Pk娶mBRk26TV冨狩9_q|(qbJOujL皰jL盧貉e+%FVTr}ｅ`*XxtA/K&胴9 %S|Qd齪HT*qo:Er_>Z-h鼾%9O$薨y!eDe+jUj]@M.U dLMr疫,/(6guZne5ぽTVьGw愿/TuJsWa[8f蒋w 琴eV\2+B筴_pF!?\μE7択j{RD霙 jUU]B\.'吶q8聖ｿlLuC/::8 +覩摶5闥Qpa|t侅]b凅,&X關ajb `2zuMB君痛!E=f~KB$i_想(,3槊 ]@WBYa[<@Mm!l"]zNｩTUJ#Qp*R).(SJE奴R搨]:=oApe g'?升r8{..LiU [\pu2|y'DyO蘢w@W6^l)NQA冑F售i]2cd?5Jq"$洞AWvb)i掃J5#zwoaGc^歹v罎!爆'v!*'6Y]dI5腰{Yw ]x 朽Ｒ8誚1|{3?wH|V竟+3Y;`J"je2R s詭擢f|PY /J!e品“旡6b)$8醋\5;y(R]^_r驛局#+xC惺h蠱tH5XwKX>)x6QB~IG瑰c4g_H`M)\)\2ti D疽EaQ~q~2e凋 Ho8).M&Efgq|若2.嗔eX'y櫺A{j@ ER -B《;pUJ!FTZ峪rYbH-Cy4 &SW5MFyETA*.'Siﾔ\;b}G7@)EtH&5LS僻嶽乙┤\)~B H($|(僣\0U qs7ZTA&*%2TAG+諷V]R -7R/D: R搨VvnＫ1i\7xb G,GK 3u F槽iKHYQ偏"z(0%Q玉Z  xfr甅y45雰<[p}Sk4c"y-%]ZN/ nI2c;F DN詞跏;V=+帑в FhH6wh5l気U V@B&淘 G 孀i' 羊_D 鰛uvxk\!\E"utR. 瑾[Q8(9<6i-JKQLb1o}?欄o`鼡鐐#4^/?\徐x}!n聶9U休Xo,*T6 n)m&θΑ蒹vK?H4 觴caw#黷uu釡!,bp /Qご|s蒲guOBH=+.掖か#o ４<孚%kgr2-hF独KK鞍悼 o?SCy)#I 乗9e“A "f-閣S+WH 0h5 DD[UFqD0…W+`$F,J鮪↓Hu星_<1獗幼Z{+uYOKfRSCr -エAｷn3 jG鐵*V 辿`k]w54%uwT硅録=<LW$懴O\,忰3BV||YIA爪 6^[#0 鍄!CyjC/提:#P+@b r荳Zf1豆c寝5*-,+sVZu<該^%HNNc>e5LYh 3師伝 Y膝i8xBN滑bM"y五榎4s38F考>L(黒>ｱ`BApM抛`,Q并н阮f亥村}+E/L燕[文轉公7w7P愍拘濔頑 庭[襪z(Smof愍M掠u朷0ﾞM.wWW<[E縱uj豐}F2縋_?mWO`2(]x1waΠfC痛>臼 溥`V !"洽郤 /ReV x三0^T贋跌]惶FbO[从`諍EVC[鬱0絵_'MF.KM e$漸p}-\x>L躪 +0&[f =z團wzuW#}恩HhA v b\@EB;EBH#i\$颯.Z=GcWIO("!(v'$魴_R-xiGM~O3尺#召_壟nM3,iq<X僂ypeC彝__veE2rK+Y/dcVF姥_-bu廾_f :X説~R u2nKt躄2~B-tNiY 蚓0潟Kヶu挫8>/\濤-[mUo.ZZV,mP,‡KlRt述uV淵妛k孱K$3T[Xy"%7剔 rxYf2XDf ,x"gOgNyq<穗^JPlbeK~+/XoX277x# SNx>f*e.vz填e于 kZ1^cT`v~ko槲!俺pj倦(懍PZ穂$8皰ok*YBq_?兼gJS-a俛9k4o5=hmK比<7>aBx`kSUY袙63(mM斡鉅l] ,Z#L:BtB4-E嵌UKSf aFy(-FbK\:浪抜哲髦Α$^EAbq槞#1paJnzf |蠣J&阨1RR華sW&涙vcgf5 WKJ看8R/ 緲<@2zf@1檬q%QcN 搖lJa;I%xdtc)MFw厦ATW"p0~rE騫> L$ .蕃+)WR縁粐^s]vr5/d >J燈12f&裲 邨fe1>d d;竇(蒿O7*>E_[`zo長G=A/t8U6[iU= XD啝<上{ONyuy縫STmqo8M88役a籌E-,y葮L"}４違xS O4}^%牘wCZx<1VsKj嗽W_Z a褄ky0y7fB*)HM_>輝胡.熱wA繭刀葉笵幕o}[\妻~:n@/ru囎a辜p弩芻N T2u|s鑽賈pPx髑{疏PX_ 9Ge渉@0筅_> z{0_炊Q嘱~刻Ж\Q慍斃`9:Vr-s$腋A/~W`fb V&^公qb~ q辮rz|v=PWo朗1笹W\nux/3C豹iw蒸yGY具!g艤B>!mG}E閇豺p'hrk巵f ~jNN8B秤)肛0Ec@W繧搭IH<0`aIU9y\!9| ZA 卑l嘉l1'1fYVRhU+L+1r謄査3i]菲SkZC摯(T&Y7Uf]nn|9r Nu9~S&囲清VH!I`jbUzW~_閂AqU実^垂t3尚}働X\}鉛~%<笵彷?q笑迄._?7l8%qj~p% VW簣|~XW鏥P]砌s N焦^鐘 +nGA囘n?沓弸癩l1%0X mP駲6T封;誤 *:~8om{秤:o+[κ.x奪? *!*4O4awc'pM4hKCBT3 @/>Q 鞁 b>^従u疸瘢|yo痿_7-&A沛a?w}絃z?既&!淫居o?s5\`銃/c卯 i48=Cx濘</ \b傅D霞K|7hZ[4癩xSs譫逎& z-j&9- 淹Zk"Fwq-U{%2鮮Dm Zj .rL!xC(c>綸o紫渾y4w埖H{;}yM&O裃Of' |}啖>wpU嚊G_齬E@肓?£O|xP臠?pФs9B.54&i"]LyD見桴(f種ﾇq-鵑jC\? Wu UD=j_集勹UxEAng'P`\{%Z4I(4惣膽ポU/艢&KR2$ ]梓TJ6}3qw+$;sW;"v%3#Ｋ!UGoG :=+.%qI姉 rq黙 t*蹲i咨Y!剤@1&&kS奐$6`u))r!kp@h)=nac@qgZWsreJ*=j係:E函%FUA疥$QM~;E8+(L!烹b榮]&,nfI韻]O L絳Mw91^(37付` 1)RlZ} $` _QNhSrPZD6Df%)f%v-AEgKC僑;5_VWC擣1TiM3^?}蹉G9~+"J+,W %GIUAbSaま\sOKAq.Dni=mnR"H?mQJjupcGPnju2Bd+AqrF蓴'Ow波1}aJa}. 7V7WTC=Io^f\6V'jXEYdj^rw^P-{u輳^9a~nh9 \F %乢``Dy;`P 4ｹ擇*7W Z;8篏u-秒旆V8f;qa:y))'嬪]貼o縡 a*<,ュ3蛇txd+|, e)眺(VKBzh)00:Dul!Y)豸*cl0Rh)~JEr^$査?HW:筏m^2w;杢Fg鉱嬲SxD9 -9A(QVt$m[ v癶F3搨黄7嶺V:+g{F/$艷1 鰌 瘡府倥5|O#鷦島Fx[崚uB>恩4B85s瑛*#uYQ篋MJBf:QSr< Mq$}wRmI午)H鞠|r7&混@>+:79KW0 F[7k鹸:g眈uNt+X[o壞z)h(v)]j鷁疂我z f>盈R罎稔姪,cn3$&Fo宀0R(r2aH6Sh $08DqZ 抔Mm厮J&7i謝漓t^Z_f衷}萍l 0岷5髢g@Xo<{`b")?&鬲=,橢{WW塩c砿fAZV!b k8H |:Y#V恩; 張冷w\dleh qe;zl7軋複{C .津*L'-CQt[T ?WkBi20Y1>k#牛J漏6"< 7Q#蛍d:A2$Sq}.xgv2C '1s8)9y~:SwMl荒9√;#X7C gj0`嫡O#L 傳&q銘R1B0L)劼 GbQKh_"螯d該69g}神劉VHjpJb屡 EZ>dVU i1rFl=弸8克(敏筴簇 "4Wk"Gfk(I吮 e#32H#0. 遣ZQ屐ｈ蜘K&SQ #aΥ細C PfK麿0k46 3MIUS(ΥPg, SZ((%"kJ4.ﾖ'! 0偽&114a υ敝戴z\f(R9{wB[n;m "Y#<決Z筍2Jk]o ZJ#"88b (";!q~9{巒'MUn(婉訝7w7(v鋤po随癲]掲TpB!SrG8]5wWfCR"d*0侫7X)1hS/,(w#j0gy0袴A')s{$^xk"t[ 鞍>{$騙 KB04p1` ELe'D0身{Z$\qs# -!VsS&xuTFY;UO JHcсAI礦阿u!Z .,Do}KE xRl)3己l毬 DT'-,志G>Rt#>R 2eg墮U＄|on也Y\Nhbs1槙OfU3@E6 喀:l8Xu9CD  dH J"e2 +衷Jb+Qp7E^-cZHr$ト!%Lr@yfBkx(^,:i 昭\X⇒ 從:d刔卅eG,交ku踐|kV瘍?鉐廓//A! z_n@'_=y!n~N情 T=,P(ヾu#W#RBX]]MD1%I;9 0c$3)6{V&pU瀑昆$G&wX]|`+8 #8m"RX6tFQe[u粱璢b`6axGL|~剴oq畸龠iPv2冂)clXB!政屏磚Tq5殆Iq|A敢O+Red28鑢 "\闘R0e=pW 犲F蹇d4i馥}YZJ^J#$m5btYc>Gucf("tn m雅=蠣q檗69F~vt}$I^iJi8R縒F1su"[U C)磚\鯏ho`~倪^CH5H擽0党{5 /NF豺QZ鈎 壽^M=c$,滋)h\!収1p13R巵9mq6F廠4CU#x{MB呈D@w寐R吸T槐)u7-(|曵kst肬M*&週@u裡>>7  a7J^vXe'!o-k慱 S]B篝(!*S; 宋3VnWDwTGwt-擢p潜"R軛?!=~凜<獰B Z)r蜍i3I籐殳填(I e_=Y>WH尢HDUMU&ha"ぜs$:gU&P必nHQ|Ν}3桐k->>vH4嘛w}I杁府"n$hF2vC銭HDkF"孑li 'g\AtBz$D\/-HS`@RP;+'NZF<$$:vdBIHh碓#謚Z$+=dRg站典1J摎Iわ%-s#LtcJD(1#.);緜汐;`Xku枲r"<椴[ ;D染R橘H`5)刋磆ykQTa0Z)^2G.Tpd%Krp\HY逗o鮗.4o簀D%SG9IW<崚3zI4o?a≦炙摘V(蘋縫>k螟+U L]1銜7 3R?:d}L{|;u4譚4)V枌Ｊ`)∈Jｲ枝講O~麌O>Ep,DGg$#QL`c>/RBJL?ﾛ域HY3e|発!jlCL宕7 檎jY彩Q)*VvI m(荳`_舍bykc篥]F6 #"G篏fxzA妾W_q5hB!壼L?H回蒼穴op8x|=ZK@ uyp .%!qie沌[X愆E-KAy悵6a子Z M(A贅FHm(&KK J2\l誨Ukゞ_1iKmI%冴8ufy婉w;y槨@i|7S#`=l6CrYy襭]ed/ZOBcgL3Tv@`t8h=]傴(釈￥**X)(ト[q_S.vL0|MlUt^V{6;vf&貨LB.i Grc5pj5囁woPl[2鹿D竄(Ha 蒭m-Y朧.~sIZн]Vm/ `wヵ盈H質d|GG麪}>箚癘XX#v Im'tDgg"N3了QUJ[MZ嗟Esu剰j庠狩t1升b-S~iia5m9hs{80.磧馬b# &bK1!g 音G:jzL/mm陛AHm&6c清SN0+b QrK2&vp$龝1#{行!tnu枴#ysc稙柝嚥'畴g(iu:_聞g  ~p2bnFbgQ}軟+MB攝Tnn煌听刑tgF~%攝)i ?ku~^F{.0 樌T !硫p = @$|AsBa怱%◎c2S菫 0JSCp9["Up` WK ゃi^m-t J5CvGn營A^kk-`eZ額 2ar }浦遂'O[ HI肬Jk.NN 藹fb}d穃uU%gq掲B巌xf-~ k4>#曩驛eU2([m<3\uX虹'}MU!u盧GeS$ {ASJ!{[2\ES鏥:/鰰 莉v+~a籍`)N0 LDa}e女"e1~緤J)w闍>孚!>A⊇袞jzkI||r H圦7塹鎭j禀/W鐺%(蔡 壘D責迫鵈裔;M木桂骨苡*>O&戻"we凩笊%c凡#恤kpQ9o__!1V_[@qs5J4蝋x=程3n"m孫#'%嶮 9 舮iF;O3;\斥qP*BR3 :yn_|p!XElS荊Ml[SFHOD &8≫ Ｚ$L,息cj6茜"zqェNX<1aH5N.o,V/b}$管ヶi/ONX&購@uj\掏淀uw榿C=#x士遅Gt"茜馳hY; Y{F.uu '1Q,馳涌] 啞殃擂疳) qN儘xD0G!辨)8栗XSZ 織dGbG`E阻En[;丈b0(r}Nuォ\tH掖9j' T廖i[畷c 笶 V櫂h慾z那L)%馼) 神袴s\R!=烹9UHrγ/uM n?b?y3@. !UrK.)/}{1dEM畋$hSL^1J6O/*yyMR_駟<+'kE(0OZ9騁 AAΘ[!薤\|仂Bb}f彬HTAdxuJM8W-棚EΠ限"S:擯 P^(3rz簟E}ﾍf]N椽e":侍gtS#崩Oo蘰AR碵c U[鶤 漱 !P海p1BB;+糟轟J Hdx)dZf堋d怠i<篩!uUtV i(千H|^qFj<' Y瓱!5s 68h(gWsWyR摘舌l(屍7鱶i:佛繧星貎[1;双aI8ゝ紗 W 7es杢IB^q75 菖ou+c鑠,\i匹Bj6T哺8(3Twc訓\樮1G*Il8 .J†珞2XAm(vp5溪/8:銜1m-o贊@tqx髟w?囀oO!W!x橢'BBe_瑾男2 pxj /c8IxPrK6A*vY.%,耋g齲p鉤/<8芍3\8^0Q%8!Q*弩.Lo#.山vetX7侫_eRc%8艶C~&P/(N&B}3@萓TZ&j畩o(鉢Ｊ9hjZA檮%側><|(I}2dj鑷K{B干scC^c[XiU.,嫺.: 飽飾7gv{R"VkR8T']^S靂=i毫\w#BIwn婁)[AE广`MZKz@Ytip78!.?欲HWbtSmrJuo靈1ぴ):S蠅dD*8:>ui8-淒(o爿袒5幃_隰頂噬GnQ%f C$kLq2J-ｙ_R萌*→監&U*E44O9~V韻桾 p ψ` 畩鰄n( :=RwuN.u資YQy騨},ctZ仲]幟yW(XzXkC#e4u厩MZJ卸Ej~零N結鬮z8竭=mI RG^<~6rVSP=5!09G)xqU>弭u+"MTzI貴%2!b2用]K9WK{蹼趺唳1HuuP/2桶錨惘d[D;Q}jU體#XMXI8CI謹NIj_^Ta&`{K亶s&_~撃縟m錫縊l捷RrN/.五SrE0sIb 蟠9jehZIPR\店|T4窕.J)怦W,$~X(`糞伝gN] hlR=6Hu3y$A<g}N\'R]５┳iAsPH@xWg}澆燹$>JFHN黙殿Z保)(2t蘿oeW=P梭影Si}7.Ut\4樊rqe? 0(x [k^%|全=$孅2OR8獏~ = 4TM2嫁8rWihT\VWJ{讀椥gLMy0尼脇謁%e0w;>bqUuUA6U#A蟠諠X較Vg/*!撚孟'L3奏L NzI &F4/:仏榎+57G楡:P t2)R→X5+(`b?&U栄TN\放MH6@竺0r]]U羣 x嗚B楜*#rc(彌┫&B^Ey畄ヨns2m^hs蝗R%>吝PD[>h({鴇je^Tﾍ3Q痘'xQeHK %檬1j?A5(ald 震d((8\XO~嘉o 9Wo袷&{刀貯蚯;z裔s瀧B*Jvt{zM埒顳托G( ~<|u~|'4_Bｴ、嘴肪A磅'Q+LS;}X莉齦=%戦5m=6t w?.濮蕀;<] x桂n腴+g＠ 艪NyH`P(甫RWsv;0xEf)雕nx,E9鑛!q}{x鴾kpN*$虞砕; にagg$4S O臣侍fUv僕GR7aQ裙g壑_R織凡?SQoΚ紛w16#L^]C#O4庇>ZF璃W)霹E88wOs~ S?)|{痔WR] 7c濶ヒ9C#鮠^:_娯Q}DT陀 鬥+)~BqKo草5;vc t~E%^~x_WQ{t樔p逃/椅^rs Sb]住w ?`襟&\Q>獨蔦C剞f|9mvw/_w7k派wWsyrΘU逓|2AU0V-嘛WSふmy s濮F N>粧驅A餓^SW金,衆 . `UT,?Z~~序銓VW -. M;現yL恙sz髦 aa$Q.u?ra車茯撕%"砌N掬9Ebj@臂kBYh Y_檬淮oNC89[韜室EW湛7:XIk|竝駭e~5> \\SD+z衵-鵁識4;xs)?bXN (d|//BG._cSr z/恟埜~%Gm7> 惴牋WtR"0"ri+^zd鐻<癆襠{mT>偈>OW)V^rNN]o`8{Sm<}m z5Aw:搨RO`蛉Rs4g)h4/d rR(Hwl_=;jL/_1UPT'罧CNp^ Ъ公5ヅ島)+.NIqqkJ*[vVﾛ擔o_xx瓷Pn{湍巫Gs嫁!i无| 眽7榎W(m z W(bR貍Vfc/SW-$'*洙9GB"Z[) J e(肘<=)Q9 =:>Pe<puju耀] ;nE且b睥,^&L鈔d|逅2菲,S簗滑禧n;}鏑G7djn8qBBqc$rG2 x)v^Z;1j噌C8}L k^8F2_W5h|Tsu%磴 沺心A2v]RHgdEHAb43=(Fy`杁XRTFj莅輯(蛤{P m濺乘+竹Iu&突]uBP 6+w該d#2-n!陏薇l <沢4B/d添 &Z$~b`職$CX^f?d`I悦Y懋MCD, ^- (蝎b]0B/K 9`(].,u憾JI9眦稀I拉-Z被+7_we?C{ i @}у3( \D`.WK 選Sd|S*O"Qqqf+EzeBk%~/慨-b“^Y Irjr昼G-}/i廓締teW*B4$W跖∨8 \K\]觝堕R(醐 I&陜Ba 7O譚F#罌D{q]Th K瘰d ;@h檗,*<礑&UJS*NGVNGl竣N"v+搬 B侑 代 "[A.[A[Az!/(a "Q+ 1q8XF&j魚韓願bo U[mzV#BK661@@愎.v+E `*IW* 恪\P杪?&|"7ﾔZ翕m,}>狸瓢#x2{,x竸xLK*!亞&^鮹{~遜1A.+謫肬b-8QFv躍gqj-/i+v-6"BuM`wTr1&E霾$zG1@r傘啖處惘GkISZS)Gp擒}_jp罟c$慳禺LJ$7 rR8hQ顫\\ r|yA ;>T,l:m降*ki4|Lkh繩@/|Xﾉ}5k%{u 2雉m I碧DKxBV揆簇%綺鉢6躓胡同##u'qQ` +Ez@W=6Dj)JN{>zriT凹kqu誦D&T優[z1rb琥M9_Mt#s.!)Y~1∬lnムhn( l\Oao獻樞`=nF廼 )Fauf秤~嗄yq薔R派廬&唖zqJi;`3#P8a-R ` 9Rnss"a$盻R啗'l|{孫RCl6yLc9rB 昇zY旌Z<5腓郁5i<4kh ^YDq6d,( wbi)芳ム2fn≒=' H,{*3εd#,簒EDP(冨8X岬Kd7腰FV1QIq,rN址k/,縫Fe,則:}I匕粨"K}蹴|;.q鴆_<{oyNh鳫 Jr#O廷$}nMmEf渋' Kh4軅=#;觀]b56~勁`a廼%X2FFjJq$墳cd┬簫AK4>T幅'%P,]r濃 ~ZF1]DRq{kPi錨YPzRe~l擶|!hHu颶4D7%\8>減8~-u弦.旻怱C9 T xIё6i7*?BuxF件i+`_O1嗣KsESG1~]"襷頤yc`穫>=/?(0$是xxI 5 wrO襟跂WO限繊訂NzSd +fG繍 b? I餾V;~@]%Eoe鄙!$6B}YQQyF弉軻gL2$Wc3Y)QLR"#}!#C*wW*黐-穉番添%冰sr$~l貽1J鈿(q 櫓航8E*Cxc紬ztB)g8G"Ef尽岾V_mc粱2]))q>2H8F:Q"峙`o!%IY|2DxP-n )nT翦pqFQH世\4姑?N`糞fb慇K曦0V韈bF{禀,玉RzI'\~Ce'lﾋN e7清:yW冦tB=QY標]j%y^1M K>?試g ろoPS /劒"?^Ox竣inD甞XAHbEL)贇(}`% T牝}狎!| b彿嘛wm%[sqS`t1匳I=vehi濳JMt: ZX0dｽ酵wL2'1 =g^MGl`螫 hV=^|WXC見+7SH矗vM)rZ&mO'dD8F 蘚T~zDqV姪 A?処QO/`1 N苡需 cU蜒?詮_Bd愁A髣|48U0j#WT [路j裴^;)W估k_C ''$6瞠,D`傾}be?_%羌/姻T]腦O吐1湎租揆'毒9! 爲`e8S!p@遲 B.2.xr取s]製k.:凵'W0u挑&9j36{?+->|皓8i=wyiA!鬲h娩y;'雌p"絳燔鴬~K桎8巨? Ood+群樢Pl-w7Nr7 ,n2b鵯年(MK"LbepO~P> U.:&WQ%5icmkN1御p{WtあC:7>".手S凝C?Z):tt囃rRrl1 ;b}qr--+(u@O0j碩ycE2be'聊`2jJcg/mK澪D舫%- X)m1號2J邃n&-召D`黠N袰/!才Erh.jv|vdevk幟P? *すE氓清(Hb[@３蝌BUTd8DdCR m}n/ZM5MF籐LVA~洟淅Lns =r x"]孃:b-(誥K$Q(*!Z9*!司粍V3BI1兇\4Ru* "鳬'2 [畦愽$;fUy剪2BVe,gb)Cy{!璢;匣OW挫遥b[i6ypRZJ>7E\黨 _VF粟{qB雅DM鍍d0k麕mzＢ[%O7椀Rz}n集!^'\5s bV^~EH4I8>'劒EO-cE~35VU,sZ惜f}H/(>庚 9w<2 !y更Xc垓QIGsv靨=]LBOfMP}z_` 寺W]%UkOT[;WE^Q Aqa]v}sz6i6S>k(S"@nmJ.旱`羔L:jylVbscQsax7Hm識&70L"攫fd-肄祺伶9卿ke7Q1札aXSez寵 c>r_L6`+F@57#sDLV7qAedwHn2\Fw瞿8#M楴QN)y &_Im*H蔔H3/Dy) _7.^ Y }gv|Rtel8(``!M猥>}B-;LNy篝?すxx攜3ξ6n\1m:B+欺憖 DI~A[a.=P8FiRo.KqxBTKv狆j8咬せ釐6m&蚰p;(rTesr堤?s-_h".O署M懃H? 胱_G奇.>0'u藪s!:%SEI\sz黯s$' 8o~E糸Ex-q3|情uI'i賽:茖Dz5.I&2^zmw?容疥O(?]fsdmo斡葡O'傅k津瀰淺蘭EH|E嘩.+FH淪MエW(AL S2t逢 rWaZT.恁 ソ I存=I9 @MJ= CiJ(@ 待綱&氾/=br^^K Ju痾X%蒜:m7r,&s!P]";z貮1Xzfa篳V朱8qsFHq霙貮Xd"瓔:[U0>@__HbRr]<`礫$鯆s炎9jBNZ$泛m3F狃\uY覡ｫ5'!2&晟r\?i?p2[(o聽5'k"Yoc% |)]p禹湑?q戝dm}y~肉& 丙&BdI AB》K$7<'@臟XJX# 霍Sy3%打$&蕃H篋B0FS^KUdzgQQm%tEg-Um/遼uF#‰>D+Rc〜4>\F OlHzf1蜆t7tq4!BC G8(/ z)!v [臍BG_Z訃4a+I字3uA(緘w)R!$-@KR跫啅U柎!hKcSbp1qVt贔Jq2&!1R>蔽&; cYkYC米@2pR截E@m細*R`蔭丸_Q"O蹼=N]儀JqUlh 賓QUヨb- k>+ ?x/ 'ytU-%06eWmH)y\ 7uKi{ BeOAVkO鶫@+ч) fLty%h蛬塞Tb 7)ywbSs)n Zm=X祉ur?g=IhTR金LE[杆Si!p cHT,DpK +Pt!Y#R1"pv)舊卓B鰹裸0oN:朔6<唄4V榧ncu]XmZdP$楠HSuH腆崙 E-/-抖 M!u覡 D v lZ& llW箝|F-某??昇u~疆F{;cj'映/Nlb'6KpS[ね靉輯RRl4.､N客e応A5B PbO骼鴃+1淹 W56Hi |?z幗AL/v/Qo.\%t巵Svj25a々{夬VLdSu口@憙_u`鬧`gLRk|釐B" tHe\oDg.$Z]0 R9IT(菱\Hr#僣hu9S !*w$Q獄價Ir9\onyV}w{o字$1e<.FbVJT$*脇(*'産 #d痔})債F萎[km4toth狗#bK其7 };f沁4G鏗`2-kビBLW\x7626xl6d稻2=vN縷暼_E木?L.cX3B 樽6(vt邸mK&諸鬲$N\-/\鰯N鯛>浣|<*16#} 呑胚骰>v砒eD{#@}[首oH恰Po>WNnq驃犖 樵{i-灣猟4|&31∞FGm :6c甘糒 &^?Eo8馮h尨{6樣Bg蠣廴k?//恍w_ gr將鰹@k 盆K} #Ip9Wcn続usw哇k_9?Kj箍Ш蛤9-慶v9=$>H wyV Ц)#9釐"' !Y殺qn VX鰛庇 E .CUiqQTXpI{i[；榜丕]H|_p E(#/6xN}6Tt3D 6D鎮NTBJ:FF個 V.m相H)@I痲爰億U捩xT eTa9旃")Z(Qu0$2B] v-C蕈;坂蒸TFxk)r"髓Gp!g輹$G圦O[E^'_*貼EJ]qV 淞b脈-序R4 @ou]%v糾j,O$9鯏/T\y 挺a桾n{oOv十<桍+ ?|"TOQn 愉功湮床<; っ愨;znP@蓉y莫tl輩Hj/'I重8tss{u獣m1OE3bEQqd鋼鞋島>彼2冤FQ'聰L萠eBq辷~;? n=滂TF-7K扠5|[=T1r[d縉 (勲田 鏑/FoM\S6$孔爨0 ~L"Ry@ q茹7P/s!`}HvN'pE縢?b{6 # t擁 7g^(=s齣4pz/a)iK4mpW亊們独Y46(6%XV4典HN3概煩 $菩1WkpGa^D;1p}$\促JhG+#J& S刎5Q' Sa"+&,l S兀*2Ju?}sE<: jT擴DD都ju裸P鑽o}:zbC7hNHKX怖0at菁-e%&FqrL]DR矣`卍#繼b蛯PLP@!泓xuFkMu @2_@Auhw吭6U屐R07P"hBi  T舸耕堵(Z演%P0UD|鯨上p反4n艢$9綉鄰T蜃_o雀轉jmuw 厶Fc t民{5!ﾕ*8!唔+輓+E uXRw,12a'H ftO&碪Ip:糠rqﾙR О)%!\6L愧茸8槓 HAJ災'p &ox+7"R';R銑\mCr譽dgVF[\drI碇_$痰#b}d慷"M.k{墻{SvKR7Q2橦灌KR歌t#汳 冫X[|慫 {ｮ@iY 敬[蜒{}XШ+粍荀Sc-9aW菱co;躔}舐j~釋鯨n牟O$6 ]zl匈x ,さ我vbj朖)13怨ER}u*:巡2sk眼缶NP>Em鷆!p(B '1ShBIHi 身NI(9iu4#,&wxX,B heY(悉艦20. n%♭0*DO=嶐 (+H] TJSd完{>隨Jvt俚 hV8y<.~q& Fs-E:]ﾆ,解xr.暗谺K'%-o妓5< M"L72Z鉗i$7川1d35w?m%線噸氣褞s9侶觜xF)裾翻Z<$rawF^2妁Alss蚕sN8[c酔RDxHBk8DCw &異^淦r.n/v8trz根{ &f6n7型{賾,a廿e"Uif?-|S ;4"Tp qz"Yg}O\逝株^Y{y*稔-6<'ｷ隗麕 ~V4収{{}vaGo<茵叔Ozw{w _) <!T@0' t5甫J6vW愍峰+d\_~ !歯瑛gs晁J;T*sRkhiQKCkIsI啄5:gj&?*+3[tjZs}> xd Oe殯皖%3gr哽w~剋Y _ﾀ PH|Y.6:4=@z弛IΟ4ETJW)eJZ1-C5c i4}[潤Z\f5儷<(ECR{W.H迺+悃A}RU枡k9*臟Wk((z嵬m-躑;~践枴x`4uf<6慟 qr0])3UzF$vCXl(塵Bbhl@?D"封!.(ivのfLV> :O|爛zv,Gw\&q仮9#'典H&UO&qJZWh(#\rcUFRZ仇6棹c&QK繝Bl (４姻wH+7Kb&t4L(E2NAA爭\0!~8lVe9t.`P卍b４姻LW2糶 @oN!塀g,9蕩G8o*6H7&WR`$YntzjvK@蕉7a堡8R:Q1 ." 9炎于$"+JiET0滲hWw|sC>+鞏[DH濁,O刧1B6ь1?r  [匆fqmDYD>抓+蘭//n=_嗄6G1KYlxA{G3\円詩5'.OU膺 簿&姓p/IpHl<7Zw舗47wGLU霏9昇勾py鵑tA}US舳YSlo }哺,3<rM<9g視峪 .0X式"G*/爿-]c+#u%_q?K [GMcyqV/殤9YC);#其dj8s%aO嗣iGa7[檢] 3I愡慢/闡?歡6e6]tJr8~%稼 n蜜q倹N八'ZD/廛MzEQ?nTTwP*簀\!?鈕Tl%Wx+`3:$+sAonwZxRjkｮqzk\e卅b慟V葎o4B"gFwc:":昨k`@Rri0m虜\]d5-C1u{tB]U喜%&_K元.T枢例Bf4v![3>?除 tvqm/J6!#zXG>a黻 Mt+C8c疚(h]B鎰GFm"R&姪(Iq 鎰2r簣Tz6AUGJ醂De寳[牡+X%K/ 9.HO%X)!0Zu鵜{qヨ2"+I嬾 ~^筴C=襠AQ!/ "qq艘N{裡38p.mu[fP`FT8 $Q麋(!閣%吠B4<%p縣裄u2\ef'4i<;狽H&WS&&_JQ(p揆故l穰JR='k9\IpR].~uMs}$W3>W{JgW]G{*Z閙_Mi疝mE ;xB#,G%[1)6\驪KI|ｺT8*SR韆橋l棘切住fw揖↓5J@鑰琥gH鴎%o囃4shn曠sT#鐚Y>翁qO柘iQ`裏@咬)`嫌sSxW|-Cc29xz4u0b3直-]`直-nglY|Im 譜S>躱栴h看 閨揶誑Y|Q Q偽!藾E X`髦?歠#?[*XbtV Z9]*n>Ej9g絣件|De;梃o簔 3Q 懋~x住>dx~4+非+A┫ s#_蘚h'踴?形嶼N.拑s坑~$mS牀F1LrN痳goX)縋w汚ajd7/pM條! 誣/悚;k8=7/r齶檮yV)De湾P_O股plAb弦Fk?Oe7敖<6uFh茨C;T鈬S鉱sJ [途/0T誌奇跪E;|報' 4揺t6S~駢S\竃t{#PtgoM2碑Ｅ獵% 禳笹飴 箏>n/:\]~｢\9J_,/O8鮨y骼|nv艮U4\~qAg=~Q".N,埼嗤:E茹n]|>o2|4-h&鷺>U?Dg埀A_)`~%?Yn>lo瘡iQD蝪F=菅lh/ 竹"5$;tCqW廸g;Km>X功Io2IW)u}↓.~胚剃壜wT >眛uf\X||cW.+;s {杲wMНMO`5-6}挈p支^浸"s_T"桑#b.t/LQNI_h@<5dGB~f]=|撥Bk爨,MF觴}VR縺臨eS:樂楮枝h9@SyC$yrj(扮;q6W7慯設 ,x!肖{*ng邉Tv>練SZ>~omB@Y 乞 O;Jg梛|ef惜J&'勳 螟-3楪椢l}x=^q[w姦{yUo[%:暝綯霸 fK[?寓觧_9_:^*(W i<qq@}3i8"c{擧ZMb虚娩1引.Cs暼;6G' .v釣挟_gM=Xt" d[l膈Q8L+?tDw1:p甞yyF_wzjw8vM宮$Te`歔-_`B'l+Q3s氤禝L,l'8F>ャ/FzsW囁p<製f喋i..mnqf 88A>E朷m瑟:Sg駁Z陬C到q>on Nk2}t}+洫(擢w.昶@:hsMR$g汢lw+G洌N,4 h'唱g (EvG{8y充 1午u'7竅O謗筺JP|阡竅H闢sO紿),5匚n,1;w<< r;什y=溝喪!徹 2盃2|bu_8cx4p\>&掀構妣\面責iL*YmixtZ:<|國]I?:8K+X7j,^cZ艚eb7l>mG腕W'xt磊桴a.韲3麕w/芀8`#積~ UR箱暴F猾&d nけ悟W昏w<4]と丱 'q)匸I)u S)黄~慂mlk+]7n8餘t}vn患赤ao :t2-?栖kL>&漬>)*(k架AF磚I鱒4k=簀陝#舌={8P彙寸a&`\Y.e>j%鞅8%財Krt 萱6/veg-87 D晨T徽`"0;J@6ＩG-U衄3ц.M#C fb$佞| IAjC6ayUSW愶()├c?l)" 鮴_ h*07%0>諱O碣e$'UrO瀞~笨O髮} :G5T>>= m5ZYO愴5繝$" 迪^笘麵kC,VJku>SJ袤B魏沮濟Lvz?,~o+*%右d!G{+VkZ6J*茘($迷B"箟E.v'%魯8u\xsxoECg賎kC@]q塚+ :84Ok3[(Г]W&t&y坏D少ー4-uGKP涸//垪 銚-G{>琳D\md)D3e5憊S 螺/I蛍X7:O#ZG f鰭EN7+E>&Wk2d7Bt R#t8乗 W橇9九A蜃バ6i屍roZへ+.7若{-sMw}X0q<導?<{:`#gld買eJe(q "3tl|(DR措A]Now7,/ g<2BA0phL^B,epL!ORpL處鴻QVGY2;H952ｲ1r&杏XGYH{繩Zぽ防E騾iU R J"５H?XsD]/~騨RDHaE%K hb*bWruB辷R#~d+[UJbgJerLh"軻苞Hv獅R1[8 LO@&rp ]}[g*弄Xl#鐸IH4[!PJ)XU4[!瞭肇 | 1+c^("In:F54L+sLA1R癌X巣"Dlc.kucyuZ&^.ｱ:e^&E$?佞y%=D 圖;pI`7FZ歔6 L詔 r&c簽 J潘 [}$'Zg'f蛉m]zh *'5g&pB積$Y\sQ&J挿'殼:侫:81時UvRE{R顕$(0|4Np濔遏鳫C)鞴NE阯'_~#g?{}@'一燕闍%C[SKT-驫:.uz r庖`f3>R粭O0犒ouN: 楞Abc楠@JB錣zH"笳睛Pn/@yv|嫉A 侮r}h搾9O7wO G[桿h0玻椹沖& hＳ禳胛瓣m銑楠}O<農QOCJ`vz欄~徊T)v官 _MZ:A2&LS2.ｪ`6Q 侫姫@敢B睹aUW]沓灸ヾ+吉iuFGL絃 齎蹂=怙kQXI>]0j0t寢5肴i0t!b 禦v4劔&+Q菟Ub3是0xJY)z隲YDG+E)鈷裱n 6 ~gl.梺…PD疸PL8hBd\h[rV`/$桜n{s齠尓現[kEgp誅=@y嫖 lH.vJRJMR^0v嚠fe9Zzs頼"3aRB夢uW 0!W5gaxJ听 d33hj$qI僻Tm OH乙H彡E_:@st}`FG司dB0e*唔AkcDQR!Yc匪!"erG"PuZ>"RG@T)御雍gZe8 墜+@QD東V A/Pe箒g< 告x'b*ｋnD楴x?-:!m0赧 sRi#:;GK  }|7BZ%[";#票 q)M,w)宣IBtH*/$n"磐tゾ/桔F已0PX行虱}幄a"о笄;@aU~"KIl$僂/ *}" イIMzTteD)茨3_cc7王78e菁 a YcWHsk稗 W#爻 g[汎N絆Ip0h%8RK+ MV6370js}XHd壇$^~AK劔uzl@kw披!vZ2s-,z=nh3H&ﾛ<BDW:!)k休(q.:組<]pQろTKXFM←.8j餞at(7肚裄T7+grE=x"&5LU)t2da&n}^&`裟糅g聡窃; N!浮C'$}H+P%D+x[)鎖D+マ玲嵬=zvqsmnvqho醸il[係7WM#奔+H_"nn)Zq]pNS偈 y"^pL;Y D`pw; BS:o煙z炮^緝蘭磑3apzd9!`X喃梹Dxc.$2,$* E巡蛄DK c[+贅*朝Td_( フ 磐$h祠5F爍ck陥uKc@a美逼&(R{拙 EI^z矧H E/d# qH酪i9NtXfUG2N,)じ聹< |L,3;\%殯 u t')堵n3鞆RB;WOT~vE= 捌r[ 僕遷&"RYUsFs'━賊*豁2&QI_N\YG'KY1b@r8dk熨 /B⊇/BJa,娵&.$1L蒜x>EtgnY%).Q飯%GRO"щP締素[$nE奠J'Pot T束^D:)#6 1rBZ 31H7^lCyJV絏墜re"evuG*襭x8購e nb2'*#ntk=x1x58F鑑$/_G1Aa}y覆[0m[Yf替Tm+x^_正蝮yHut [({ム9R畸g 辛柚 Z順(-/娶鰊nк 1nD`9!C蒿 拮$G6wjKq址43 施n醒\H|刺H|)w:zDG柩 yLd g隣q軌Z}XZXJzL,KrZETH\kY栴6mMYH亥/hZR_&O8,jX 僻羪1/t7櫻癧+J7|忠x穃O)m_&'2簑 J巣 wU瓷跼U$u]梏.見&uY'sOJb<ej[;譖(質 /)}]q xt4CMCV2端8i隧honh6J埋|*bt~Vs螟r皃\*yGcW,y猯6/鮴]kr-"えz俟@ c$(D &7胚HL抛稀"4jN"SJG4Ev瞑~0"m釵R.ヘYSF沛\貧奏Ez房L**u%+'C~i醫`h【蹤黷`蕚s306f [ZMe]}Y便o 騫ﾏ~Cu@I ◇柄^_ 3$@"環~m+di7+} OH.滬繻JQ\nF⊇侃y!半1')З+J}YM|D }1Ga窺61^:ha 1u)葯HBQ癶啗I凩 純аqZ徽'pnINM!,}j9ｳn敍ほG[>招!YΥ1粲4RP彭)%cQfQ.2=`研P*))$V6)Kv#ive!>KL葛_7(l#%驥$~/尺`) k"OS苳+fyM>x朸8<鍼Q~G癆x[BY魏+'mbhX乘R s*]樌式7.＾9b\@$"`詔yCoo f Gp監頬C遉 燻nng薩g;韭碎 \C晰 厥K鷺::BB薄j7KVw[3台fq/弦oSZB@-G*_蠎 *d)Lopv_p._ooDT C"hG};r障3NL #j+B&檣w<-Aj&1x柮I9D8$?!/?z蔘掟dXJdMa3t5w\罪3鞘様囈F'}/( Dq& 傅侈p$[ + !M7cWg忝誠炮lOw}姶7W y?1=C轄儕4VQ60R.曖m敕2~zc-襃H'禀 .'1PP(t>+L9 S0xd3W 3Bz亰I牋H韵寉璃dw;%9dL.! 蹊no+4` XN嬉+{鉞3$n ,icvp^?>Q喞EU> Lj^p暼*^'g/涵>2茜既鰛^嫡^mdm/H~<璞(q Sn >%浅瓔戊~d5~+JuGK太An:8g'4XpI zqi#夐栩X計'a13陞uuwC~H?]fc竈]勣'iJW"HrηcB.~-m!Qi#n姉<"0;_嶼f枕F^uQ隷7m蟯bc!n藜9N77Ww彷 LK悽nvv;&n }e 襠夬}U[怠泅H$|m\勳5!D8;9N(瘻?lYO9齷w.m,hEkQhqKS爻樌lO楝4_c S_||qK_oE悁ｼ \y T.V "*wxX\mDA _YAWp}霾2-1>棒1>尿昔凝豐◇micg9>a\z隴[ >hjV|)者寓n較ﾃ沚嶮^柳pi" %t,vncIxa.舸<紂0M(群0NW犀9d8z>S@&jjK RM\>ek |8g梛vRAK? F12e若qo:\KB8MMz zh&y价Q j6.3ky(冷bdXp2}z税痩'^翔変^_v悍]>柩Wo_y疔W^\會}=<OC3{鰊>nXI4b|F!/xZA澁Fx鷆j冗n醤j∫7% dB`jJ竇Kyp偵fCe#)襞\2彝-＜祀/7芫)NR%堪_:6K]{twg>F |蟶Cb >D|c衽":G?|g殖xwH/#諷刔_q n柔膏:^U礦s7暼#(7 oWpi閖,v顆^AHi]W78^6Dha4蔦~牋.UNg線A?IQ閠Rs薺襠hjP[]y8?l@臂治'r# 菓xM= x$Gl嵬.3*Yu拯-g%%X塰促柬e!nx 胖咯k s4識bq{yK f;[)"w$ 稲MsM[詢蝠n迚蝙bg'=vO竅JUnqY`7$Z麹玖驩濂H寄y貔 v _:JPr/m[ E~3}8V~v`s /C FIPwXYk8W4a|?\u]K?7?mM涜 9% 塩Yzss"G漲/mw{'x v:d|厠y罩o0/|E3ys誅=噴瞠6@轌$IFa尼I粳覊'.M簧mU1p+@"団2,呑游瘡p田l褸貊Ye~蒲f~Cb<%`ﾀ\ ZoB/un枉O7|Nw^叫m況Mq ?Chho 寿_2M3h仂贐 Z_│m.文a_ZH峪JgVeI芙l;欷s!gif;K7Z囀L臟HO抜hP>q2M{neZ$b(&)g庠`M茱LK1w嗄r`uP段Cｴ3Q鰛箇tN=_o.v]7[4 Qｬ7e=毳K貘y45:^k`P2;屓Tn倨g蕣lls-譏??t癡S3錵vZ|#5l[< N .蘭 徼蝮創 \S4_}覧oz鞏^=W姦^Bv{h7mQw7^kxI閤Yt{9y鎧鈷x -{w曵t盈弦吠Ie@QY6募2Rn噺F~Y%頃nu_〓兮朔jロ+/~xHP"楡w酔on tS━;f%uY?OxDa速aI[wa "ew7z册L７dx烝]G@G|aw奨w}? -bO67mDx{Ax樌W棊配k\tg] 莢飴Lm L_}*r}.uoN.l#MO }W伜iYMv濬筆.加E=v倏咐=VDk|f+}{ Xcqxe銕+%=Vxぽ=V[c責遽速芝2赦B(F寿> 夭xi?^J(h$IR掠vndLr{~砥+!r盖}&寥~~ =vv弥係儷<=*J轟i-U逵AJZx$@rGW+1\ \ 菌 /默ﾌ犬冒k梹$3l}>さ'~89芸[s;N牆坪律O(@靺zdpGgJs琢$G鐃{F3,P新52研ji鬟6K)Vo[EzU @梯!z:Ab'n鎧AU|CoW8{雑o/忱`k/枋N[e`譱^hX[`P{HH$譖5I云W?r~蓍7涵{Oo _>a/%` 瑾A%eFP8@u擴 砌摎^&|黷 3AI Rl往*,sR拶鑿yYs8Odg Pkz 2O遜j艝-wM)\;/6y$yI8FJ4Ny%*X)B-6.Rvf慙d%  F78％(0)V蔔T$)+&s&漄嘘 c$2e7o熄O||莨qm( 霑p%AIb4>部qNTZ=}WBu/[諺赱HJ ｐ翩1rCq-rCt#EXSW-A_WgW-@*=nK"&>%$壁)8F檍J徼Cy?g5>W*5喃8:t/&64:(%V 暗QD紡A漾艾DeTGR~7ab N0*B @4 FIIAKq8ot1JH,槞iR@^Q"qgUK*R鑓|鋼很躑_+Z*b壞登瓶*胡Jb1ElPぎynG無E[o4-S裏| 晃)t@/?O? XDn総(,;b^h(^q5.+!Q, C潤籬潜6&z`?p 泙填[陝.(>荊PAc"冪DР?3\d)0椄]=杓Svpp蹉cJlL確H疫霹seV!囈z#]p 鍠2rDe0!g`Xg ADjjZ湛JPP%llx:A桀游89@*t'7<5$3 uz( ]F36斡GT ]H(&c粤2F\1 NRF cXyt 朶v+ESz,~h(H;}'6BJ>R~嚇 Ew鷓o6j#]R<"dB匕T*o7l1Nq+I <稾'>]U35D3'3% t^22\}u&B原L(TVxけVqv$u梧=0VWITSaU}r浦Vp(bV/^.^季箚~d裔o`Z{K3q槹渊權総lc63鐡D<珂o +8Lu8購+ﾟY]砿ra撓=|*2X)捕]1NJ1j嶮TkH即^泡rmy \n-NQ8;Do8>k  Jaet7 蝿Cgp>FgU@ PI$Fs"W.vJ,kMU0UW$Gh")\摩.z=ЖHT'柁F2c%|贔 =7/(_鉞ヱl鹵fBG}_^whXy]"?94jjiD>替#膈,FQ+60Q6uk:`+裏%r H8冕\2l IR98bJAE4腰伺CL:郵┐&Z$2D]9=2揉麭+肭wx>Oa}O~(wH {#'7BLMI44*tハVS\}9NN\宍cTFQ$嫖Z反gヰ\4b追'u\YG綜戯xyq}$"'恁O!#0晢b}$B*j v;鼏~"P?ru蟀%褂E%^!4Q8$ ej:現u>PJ"|俔dHcT6 囜8#弛@ah騁D 8MN:-J6A9'vM(w#gO嶌伐 cD3T檜UF;7D)H1h極-KZFDO8e粢vMn&藹s6F~;SHohj〒 sRKDcわ,A9T U腆q2d憂%B眠a爺|J@5 ERj+[%[z辻v＞$Y mNL_LHFv2:駟K|2917@rv)/≪0+,s藝?VW #V&! N~+f|実8]8h]I]#zwO"?茲Irl&~(ga興QKL;]8Z%;3%.1A .÷@.H器x!ia栫9}lRR|fG@nU1;IF=`j+ONcnvW-4惴$6: ##Φ套ZD抜狂5%kQ鮎dJo =F鴕虹門PQu胃dＫ妁BF L兩h仕CJ>0H)EO=＊g3置C6M.L蹕o 無H|4kQ'i勤諄w/E箪卒V?體培DHAjQeb7 特c7ViGU亟#V\КRA7!4ad"もQF姫蜀D嵌Idp ?A(COΓ洽[x6tnws h 6柮[D榔wFWp悼c圈9QCDV<3C`愡Ho9 E_拆%WeW&"計|{)Pr受L17/<V`w|wWk哺|w9盟" )1｛樗; |TW 8柩W|贔~%Wo欲o$bc@DQG#%z炉h唳蘢bX5sS佞iaip/ &7QGBM.楪1q∇bL<狎eヘi賤哺脇H鑿)UhVc+両NW%績 h\sI脣Du+Pd4Xal'是p栲l MS8:8i)X*(葵%*&/lRx}]fM. WA :"+N.#)C2e"mG1[Qota =承[h釶Q雙718.PkN)|4NkZ&AL_t)# |"H>vv+%u@a?_G\S*促ZhlM; }G}r畝T魏醗g:Er \曇F&! 4=j5!~滂%w)so}引~!jNX}B(鴃+`6eF業[ (,佗*eA"Q品于j22MS9'BsZ/[#彈kdmWIH,!`奈NM妥  鞆`@SSZ&!巷i摯og矢t\Y]字屶E%dqLB>(!.P^B Qct I]- 5 奸K%aI4*fY|Al]念l痳@?|XTc(` Z斥K餮Lh B[撈}\q-[DV鍖2@$.QdG@\)C$鶴*垰< *we舵輩E/桾 - =eB2@f(館65@(dkE -Rx,~甌]EEmA^B畏<[Z6鬚N)=eM ,v<瀝邏R菫\徑;.n滂uv筱`!oB 4ONe9(R]P\c4E襴 ;" F'LO〓!'c>o&眷鑼1!8dm\^aC/dp7h.PP%B^Q兀李鞨DeA'QT塙*櫪tmjwl鳫m#1mdHｶj:XkCE/BKI#'H 'Qd0*;xDJ洵=B　@G体f疵&%Hwu服D&8盧G0HicpB{企 ?"{ Xh況. = CdI嚮mvX!<(鴉渕x+nt城}\ED0W{縊殃酲XXW碣HO-FX'RRQ"@P(zq`J>F 9@FZv+a,vRUdme, _肺+X虔 oVl(F4FL()`d5!(O|嚏悼浣見!o6乞%:0IBS6e(4%,R更N8k-:u[F独[`_`u刹LaJ.|Go醵蹂HWj}qpr騁8`X#q寡~lq}ふS;壕ヾ"鉄ep鋩gxs{-O苟im{FX膓弊$69%&QD9(XZ`R嶬.)hOfMm3|,p=#e'oq%p 磯 qoヨAL=j麸w+KT.6BJ/}M.s\侯Zd嗣8孚 "K寔 賺)+&X64lM驂W"n6*8J&h[張JG6{JY~聾La P*訴$坏<\c]t e葮&+砺炬G4Uk-5[,,$zpO6])\DReFkQ9`A*s 1 =w'e k!h/C,|-yq4sz#d陋_[Zh7kcn g~m)9)8F4&Hu9y)争k% c LI[YGposRpufZe*H攪TYZ贅/*軼o觀晋夛( PN禎N;h空燦(F済)(V'X2]6&靂:dFh9:6ZLr [OT嬲` 絮@<;桙昜2摂擘?D+%AO訣n ((0)&0h41_曵QDY鰒!aa0W7鶻yb\衰 )\Oq/gx[Z.LA艾{H ~禳_驟}1昭65$J/Q 璢∬襤u&k#"qr#/ZXc.yLGZq]W鮫X3 &[K /n8vTwex-`憮:I#h9|鎖;w9絨T2szz7r 77E&%Ki岻趙s8工"U RQ0+H/i+爐T 3K2H.$i諞vd^~ _ve0+F砲6 7撰A續6pDGdrG0n'PAs璃pw<cV落3lXXwQJA94`"S,Y~$ gw|胃+`` ?:腦 C ]嶬a喊,U AXTRvi) 村w豹q m)vn7x驫鋒}Ν祀史'if ASJKWF^.`&S N8:RLkL' =羂錠]8S0 胤I~WW藁1蛉電fJ{鰊fc:9滝v拘肅餓Oa冊7\3b(蔔緇 v竚 >9MC"梭瑩痿@u;\O2|CgZ2$精觧nhq %居C>P #pFObxf桙ﾆｰhkj(ZJ拾pQ>怺/d#M跟]р趙P伶Hk`huh傾eqH d\|yY ) }継毬|泓MTV=UO践dSeL2h[u\_F8 JJI me=垳筌oR!盻{%]5dFtL脹坦cょZUH饌J)Nsv#eih%Sq!;/2Wx9i)k@'R-TGGHl禀%9Frr}dR蛇+#n*:8'YポH潦t?sKV/'bGkp允^NX}Wハ g A\{727N5lJ矼deHp6.椶@WP #g%(Z/';+v*>7{W/渊銛3'P`RQ*"迦L臑E憑8Dbf:竜LZtTeD)tn$u2VWG{隋YTuO謬亂V=OFW~7T85o D KO3)6=淮(F! 廨y葬Rm母聚% -geR |iz'ZvY1膜d&{爺*aru 7謫lwT)'<矗]蹈?1胥3OT娚w操8}-76PR@'÷Z0燕C'J5.\i >(UMHf禅楼c1FZJ&8PQ1 西 ｛.pvq]蹊*2膝B靂/#cH)是EP醸&wa 沿.\U`%釐2?|j:丐OXtVZ'VらD楯^\Bt癶BR,N:rSP0ty-y2`_4迷,架 ESXEy')應弃貫装dZF執{装@MeZ3-滝浸v!若u`a 警.xM9P葫/[Ln ;0 23wK9[ksリ.vR!宣Q)Ir`.j!倫絹fX嵬擢4{酖濬~|中礪=珠∫ 0韵螟+&髭IwE 40l霈$%ub(PaA梱%J b亮Y8rB#;5 ;5i褞BB＄myNL柵$}lOT,mI4Y@)蓼!+猖'5(ZseY]+'vQ兜l2燈r冪(TXHtUw嬾u2Vm 1=gB|<|=孀e-I7l]ｯ屯@K[5sU#GB_lXF0,2i 7%,*鬟1T~Axt9gTJe圷\3Wa37 G姜/爾 \ei@(t/:@k貂埜 Ph~$R1YG鶉m1 l%BNV. 0"aMdP圈eS2U即F罌8輟~#}s7~ j珂犁罅[ -u}2[Z容9淬qjfy(V鸞-啻碼 KUl f~x_.組1蹉Fi照埀Dw&$v逎m `/<願2i鍛瞰Ow訶+_? Z擇7e繧7-#桴榾榜ja.IMg痰F口妁"hR8(圈/38/c?#m済 ?崎W[%NI8PB蓮挈X%唔-0Jv#OQ~)</N@ _叉Z0'^T &l /痩#S%燥TO燥TOp眈ZM\6槽A(佑jy!崔)EB仙eA(`8t凝Pd#-宛ip. r方疾y&&["極j|4~#8`t#拝|Sl_ek咬Nz7乕C掏k@oH失s突3Vｭx悉A`l ?'iXO5Y罘us个酥s窩 檣s父L~ww( 藁!7m<醜~s皷Lr中r喝駅mpioh%輜 HA関溶悍栩Kp=_豼_>碁歿2(6兄a隸甄恠z雷z档^*SG霆庁yno\lc揣H@は李/}黼{ jB'2麩YX|5 霽1Sr+?waxnn%c/,o^~i45m.l6_y-挾SJ*嘛/渕@s8By抑M甥e0d 閣d陵vLF l&J:靦}[GVぽ }$稔]5y\訛Iy- WwV退咀倪JsM}(K6mxS血;8探wPN化Q 漉K裾]` 'Gb9mAq悉8昌-オ九-6擂枯歸-{aA Z雋9皰瀬tR||fV_I{C饌V8T6_v][VfLZ澃 "-713@_4tEV紜_l.$様逍}@P"S^B*HHQ#n咐0件襌O="GE吁n唱yF衵濕;F$l%^D~py 篩,* ^bK)Y.:eR支N瑪/T_旙*,q),hq0[sSa廻(Lp.擒l-jNmQ棠!,Xgyt=d RCq8>厶MXp#Jrl}hh-rk y58ﾉ蜻.E座ME2Fy5hE鰹A?i`Ik鍵 ,ぅ憾9粲Gk$さu(選B^9!z 習%06C0.6xV? 顆4.|ruLC+顯wGhτ~iI需z践s軾室|ijgx@`羯Vt繊盆j6惷w 碩m *例9+ *EC"DmI3飴B0g挽1F0\1s\2&FN\W=5b杆212Bs2I Gd玖)4s螽XaCbci9\x平Ew,栫嚀}糎R鯱I$甦2yD~剳{mOA6@h^m03d甥$范湍$ y3G$枷煌 n)s ; >S懌b /uJL葢,W懼q4Fr駛d咎0 Zz/YJ,VQ8甸 H@gD$礼 IZ])%GHc綸y b*?!ぁmkQlHK!BD#9vr顳gr$~I┫乖2鰔wO!1f<|^1>rxukEv5敘憲糲仆*3SeY%*~B!d,fx耙舂Y墓{НΔl澀T}Y*z0FgnRP*5YiX\d<ゴuﾚC[\| 8(独s2Q?)e'*ydkSH8販F\相h:BZaJ甘O5JjpR6"4査5yhi=XK~憺{63Y;V4-驥/濔{ `冒神倭;1払sBA)LW$z5`AE鰔3]!NW_儒GY9m 讌]轢`uYTL磅WEZ貴4."#k)Q}]業t'WS婬wQzE6O9tEO#嬲%@膂檎/絶e苑b摸4鱗L )x8/Q瓏QM啜Z纏 |P互^_}菴]%pF J]<  )A34+$MdJ簗qW0Z+Dk2 8a@Lヾ1bB|JgkE詔%J躊tVY Q冫1%!梺&o s> t]M常*l開B逝jFbYJ:w31I蹊 ^uB奴>3/*9D5/DN幡.C熏 朏0n&q3"踰thP"m}kT)7BN0#崢eh]/(%J]T饗.^%$v '#m/mO N0:Rx`R$+EyL:从s\N:+Ep聴RdJ[F静 WX愍zPI蜈j誚 曽/ｪ,:/68tL*jsu8狷J1 pI2D5o)#FJv+ g涵T]a騰 VlwbZBI播R'Hｶ>E$/kAL1BZ,`ア斧Wu緝TR|豌T嶮t-K 4r^c介 x)@;68ZE辯1J pPH串Aa亀jh\O44i.揀(qYlT\'L[qq W偏E+[E4講8GR[>d*熟$jpj嫐付%ZKO1t1TS{mdsD '|<渤_]鑚X&Lc@g'|,< ^xPZ釁=ZRP攘/]P+aC帝系[C*蝙〓P .e>'e痳Y@`nAA振Ck3ICb)c sE隷%E1\翦\RDe,21Q妙2HS'浅^ BJN‘Bk 考h\q 钁 \La?x;zI_xQN I杪(Ew\K^JR.KScaぅ尊-s2(rY&m+r2廣m凾k!\|N5WJvHJ済公mＡ2e A//t!%m9縮ikRFUvp^待itry{H銚)P c|Jmq大313零VPo剱/=y;IYSS@oC0N筝R(忸9 揀@p塑0i驥%≠. Q`+-O綰躓:;W] 撲n /70ｆ倒>I燎-`MZ5竊9/;装`cG9z].愽z O` u. 簪^p:Uz Kｘ'h8r`vC>oW杠覧u :" Lb VSLT賎ZH5磋x7\爐+IKI@ t`ｮ藝嬲N作4;Q掖iGBX*{FR6RX&\SCzcb^ JJ a$+Q2\lor=G~Tpf力T+#k'1zb-押 t USL惴O鐐y ~*Sx]浅Me`遍7DoJ▲哺o毒&vn z聽W_乗lxgJ=\pmb梛怠z薪F )Igt岨Fp-p~鋼]CDI劫t短[y菓}>m.a?NMyna(kC陞8P濔{昇tDi/_b\s 鈞> EEe2|1E;4掌Waovy!%3NdQ洞 Rq-4Ig伸?#oYhcdKy溌氤md筺Nry56hW[寝!g7姜8\UC亠MぴU趺_SK樅GR|tBQFt汨`#FPY6c[T<瓷e@@^G)sD )9扉A|I 春@r^F続u(斂If^e]f! oG矜甅3TS]=:gZ 禿P"]h^Q#)E輛倥1f/o'$gY"FYu6F^zo%Ц刋M]FXf4p瑠.q58dYJQ\1,65ocOqao-\->eト_掌戳xZ0F"HzcCG13G3~鮗b@)M!む4O$($ZS>a9 F抔$a0[x觀z假#;.iTVLA*#qj*吊(#fRFe竍鼬8Su][T銅~F OV2恭涓聹p甄Q|Q;:T内4F7X1*c UT瀦Q燃:賺O鄲H^s1F砕唐C8Isc ?n登張BG-t9ys]M?扁3$c?ご) >$賂c!繩"H/!弩YY{A$麟l\M寸^{琿0\$:TWs Wo琥N'南XHT}p設筏 F瘍+ip5bUdLrX冱u`慎局?9F 愬w0!H 6H3hluBp埜８滞褶8\edy2Q9逸QDF6RxF&'荷S (H(&V 'V+大v[Q|'溂!pe"qE 0h=8E 韭旙pΔ9M2'4I晢|qpR R;／8F气EU+gF({c]dCEi !噂M蹣1WA&7}桐崩─~t〕j伝q!,(yG茴<9{OFDo27Б\dqYb2$!会,毒Of第'zRu rts貢"L箋1教M~o宙''*A/適5}q1r*:1kE\)Y\c@WC僉H霍C];%霏u`(#醒TH挟[=[$儺HWyx0Q1u招H剄t4逶H{槌1g!J]QE &&b"qM5?.lqW.rcA個蕉稗拶PlW.T/7i]E鶻R;tせ0f屆/G+*磴b?奧>Z徠/yQFZQ8s澱B直H_`v 0HDA(＼秣 :裲標hAp珠<:.B9Z*EO3d("rQT=77&&棉7 {E^D纓%I evCCYX##盟= MN>>k苹U骨fn" 'VL@4#6TcD仟iu&d0Z┳[9AEl?襃餡R=1d` ](\8.妥)TW!?[ylxR.BbJi K7瓮R0w=鞣)氛8i1@E)鯔n5FcqAVHcS机`h恪埜c務[Xg6UWm.30I3 Wg;`屶V~WD&(,*&5K:閲ej''?={a9冶yP3&"p$`!q~~x{逍t秕|zv}u驩 3媼 %槿F 4hZMi?c4eRk筴擶y1%扱Q9b;K 慾c-DE鰻Llex 磚~R#D籃M 0WyB拌fH愴?|Z,伯Hlf繝;9箭KI師n蟻(忽Ri|EY+EWJVOJVHK.J~XlX拱:+l8g0eluＥQ5U)フLCμ ?/鷦4N.N#\\粐Y MJQF\s杏?e hv"槿' 塚7_P〜aB/f'H5 :aKfジ}幀怨H琳+ 在B1p@ Z;g篶v0 ?烋n著v{`OLn|迚A涵xCH髱w{掩_軽蛛-Vr|怺Q".O-H掻28膓]6除穽閘__醸靤ADO李鯨>o^収w?囚ＱW_xcdhT絣/~;某IWWe_q?没M寿濬y曜wLCu襠Qa^;`7 [^Xz;}滿X O0W簽V駛W^X笊鐓z 蒹a逑鐃(~t叡閠s(jl彝W1\%*ZB扶_ Ma ~=dJ彁'屍%読 r+~?.og奔gPqM腎SD$>?go推鉈桙{_1Y4piM~O/_ w!<"樶pl m@5吉(R:=駿>+Sd寄讖0 屐h[()+鰥_x=esx}u;校9a浬>寺p烝楝xa犢fGs疹yV_沼/_?y+)O=Zz+X伸p413`MC侯U 跡['韓E4'Sp盡@_'MyU=鴻~Va0N'PUQFJ曲注c氛t#8$際6Dwiv巡;iu$瓮L養 ;#uB3wq*9R=楞拊iN~ !9 ]gB%"LP髢6獲%焜RWci$rAt:D%NEP,gZ朝1#Zj僖i\屏决兤}]! r塲La+R害k)s 8"Z{:/ZJ^E&cWjr琳↑氛百８刷唳H %29XH@沸聳~,)M.~DoO(.@1&|ru Fa拇qU|J/pz_>吶sve=;Tｐf6租C{ > IzgLq)隔_">+ツmFi^ 鎖hh盗7QJ/"軾rYx舷X)N+Q甅PHT]:K膝1=斯a~ |x`優譫&:廳W[YF!,z mfK砂ρ俸埜22_be怪銓mM#;宏94'K\8箝}ca&V/lL\[)C;R[AL%\![Hd][|Q 攝ヒD+qkB1J|w"P`#$2Q)>RHOL棟%)E!賺Z$菫{JE 藾b& V\MGDO+Vnk_^RビS髮+F+L&Q$mZFO ,堋Y)Dj蔚EHiuc嶽C! uW7:Xcd:) bcょ鉦裄1#H漏"e6M衒,宦)yKru?1NI酣0"0lZ*0Q9`b MQ- B竺p$$讚^準"Ъk折($擧=H\戦W9x.R閑醇I,TXaE)V"a2JJ=R闌C術uf~g} {I[と12\\A佗圀Nw 2 VBf[=蟻,袮;F B?d鞆xV,!"@]Z0.q$z2A鐘S罪R _vΧ *矧`E(K 伎?`t佐Y##２R1b$鵺+Q1PIbhト)wr}ぇdr.{'WS色f^藤rZ')V + 蟇8@iBr:t40.竊Bl沈搖>Y}tK[g,883Fzm9E柘mn鰆!S泰SH磯R1総)eIf)i/j2DQ4Jw頡 ipD溌哨Z+~KCz[RDaX>Qv^{'沚鋩S&aRQ)悒J;昌E V9!hAab\轂y `b裝視6y -LF\Jもx *HTx Q57GB錐&n8右1qdLDQ! $D^BnVW;>n'BD(>1/煽 %v@gBiv#"lp 9Ctd阜K7Wm _綺$pI%jH讌>"Mv9mc云 @1Z cq#@1麵fDn$奩 `"qSd@UG稗G 羈f@(dZO(|TRi1JU)q@f 嶂 H}f%%椰1T 夘簽WW躡1_願 罔;晁浚兌N掬rd秀N'>XEE 桜翕Wx眈iTv竃]P M4s1R6*B,Gt1@4苅a3C?q睿+瓸頌y4七Zr桧f換DnQ"%_#_2L<A t =創Q婦\w>蠉椌驂1qYf?;E捻L止廁~sネnb寃台.~d瑚  暁} O憎Y3）陷9沙@郁'痲]鈔AvJVd77w@ T飲3憲廐 C!BN挨尓楙諞'DS俘>Ux>qﾟN澎)9G[Wrn絅.O>{蕃a0oaﾖ熨8沮醪8\竍}2W|p>$FZu 環Ngt7; ]_,苴dHk9&t屡f;B8恐0墨'淬mas }J 2O境鷺 纔 xO效uT8<鷹到x2器N罐=QH0{$ `PeN >D嫋賃xyr城-m^]!茶#8都n歹%?Jawj&DY紅=講 PH`\x\&燠矧D筝｢2荷LH恨E'eb(艀u｡p驤7厩掏|G]y%2r8圃}fClH疥eY$妛NmM.a"@`ujky堰グH}$@裨W4jaZ1ud+C]eI^ ~^R館d瓮MZYV YW=^&F\#QK處 rF L杭R dWLT^存D.rYeGご+悩-.;輟.;.#Dq伎t]v:G碕De$NN8ecui[Yvl4楸bXvB/S$^}6.{u`h匐1amM^3#qBX1]mq襯 原%訶 IzN&#貰bLJ\3lr[oLPZuT$-u9StＩ逼mY店d\zq. '&R2w嚊礪[T`R顫-.引佛h慧6M:/F:0Bv%R凪 ;{伯$_na8Мm($k$y辭P⌒&慱"SS孫擔歩8enF +.tAy潰 部OBbWMa粽UZaI鮪| v2+h>倶LAEQj pqUE%[[b8N%zf); #g)<圄zw},椴s餓英z,ｬ{(!@$vCI@"}xd^O@閧`t6購 &\;(]`:罎9%C '#&7LX鱠:p0<襄歇歎3(Bbxx浬^^'Wv8:n祭R"XQ#'~u[87&$/IwJ9{ｕ+^Xx Y9-l蒸:z鯰L効Q9=natp))n#XG-*A衆ywU衣J葱\\貞A掃eY=9 E｜茹5{#'T(\v/0 -3鞋gvbX&2型(.g@tqckF<(`\6i=PLpE4縵'n@S г G1k)o塑蘢8[|{ril,fxC&Tex?OEK雎rewp4i fL>H9 !21Wt qg紜]寅BE檍妄i啾\i!T┤Vb育rRF _% yr9$b墹s.甞W1s1lm %")C!禿 C匚#oKG>E|@u# wV70#荻HTlI:h[" k$#薛 Yn oDho[sO@i分83KgRp|uq;ＳWO俑[]亥] 瘰)Vゝ`et7}昇saIf|sP=%芳HP繪壤!3z{C G秕 kJs呑6uc,BA Q2Ev($J-F+20晢m4K(::wh ThpU%swCIu]smWr蘇zHc"陪h0FHΦykVA?`M1旁Cm?q 装q&-@膀轜鈎7C?88Or築(()貨NYL尿 h)TR^D' wD/mK(jS8B#-S 態sr2!竺殕q*/,^o/f+E鏝dRdfcVRF432%>猜b-Y ifbB_TIV%qxe1F吝ΖY]dx :緤3今l{,$旻埔法P:誂,U$c'x 裙r96+a2D*[(b密V改 E_&O腫-7*\漢)l2<4p2 ^qP3'h殃寮-#2朶 aARI6BHhx0黜h&757CA!jN本ΩSUEL(d }St4:沿NA%QeP/EZQ{2F,ab0JH て0hu紲r５`APmp$T}mp QGzFa升戻凱>n 慙)&.ul(VJ杲2bdIQ g]2;.HtmJE2}R\( ZP掌K0Vel$$F:{Fz僻犂 #毎P^,7QG&s `嵐j4榑AY{xZ卮"uP Qi]dぅ \RO9f MD苛疲"澪狷IFi-_lMp4Q 5>R$Wk[j:y坏d8S  E2b|Qob;TNP%=n\'[iA+t襾a;>%0苑)fW!弼u2F>]9葺X徼#CzI喇D12LF拷V=%>Cl\a5aN)RV /MEV寃ZE錫ZR譴3ぇ嚴Y}Z2 xK`} o ~jP畭tJ@/dq 戡\^Ka^Q+;9Jy寉>` loC芒7た醜c=肅vp_Z鏨 患DJa!讐⊆m鬟?G6<僻@1Y笄x4qX_0Fu$*@p3@H蘯_m獗 $保N碓]?Z玩#勝(覇RW&x?1e檬V_?K=}8=AC a7p聲Rr<(f+鮮qQRI犯)0u6.n7DL傔Bhe粲絣19lH(輒1Ogr`>'! 唄 J'\LTI*9^Ee_HD>0!zN*Y$甼5荐J-d )e.nM[wWKaB密x7'm=nHO[e7贔fh"<%7鞅E~愡-qQV釡"myR./ J[' Dgo謂2y@||bpT>U'哘bぢ)iB犠莖p#S惨双 坐'\怎 %:b'挌.Y杏MIeEi)VY3声0)H錦|`sU\IA'厄爭嗜58F駻VsλM/sZ畑z\RY5y'B"Ux-D補h!B台iB Zп頴(r d%x陛焜*衢z偖 %逸 >]素B%A:X1U哮T\d\慷燦8R.屏dtrIN淹f0U=鏑z 画1TLbF"囀4uZJrm艨$Z<\Q2柿狙$Ie58[8h"y.jmFd#[]v2B1Y){3!=pv*O~尹叛1c =礬1F4>#髷PΩp偬~i毎#f'X( p2E4,\lIZFI腰 xβ("q疱3/-跛2+樣禅\\]Zj|B篩斌H5>fM緩5露4皸 !oE 尾W]Q娼c?n999FhﾊYeXe]3[&(} 9Q3j覓;>Emp;e+'c<垉'WO-m群UDVHq瘰畚)E}^<H+/[%_DT梵Mk憇}GS鎮q w悉榾[四蹈!棠廩@*2Dt#u%D: y"っ服zw興>!<局鮫 $.8TVt?噐准1-'Jiuo6ZI Qt庄a na:Q`F D痍V跡o7m魘捌;髭pjgaS从-dI!Yqg+%q Z_W,.+p繙 挾! 53w-A_^沁hmo 縉8.{匁=0)}'+TEBbK|@loF{<~ 1 Aw+~曦gkZ7郡^湖O-塙~\,v' < 租03X7v99 {RTh梟/婆僅qv*\d@|QKZ>ck5 8Q(Naz$lI}>u1:18WJ梳胖zU[Yr#H杁:ca妄bs<~邑| 枯7~}逸燵y買Ux瞼gSj9=fQ_賽F js裳S桜GI/3teHyEDzW;iI*/[?絃4 B{.jQkU1D/iy薬-e~eH冠5尉508yG Re3[>_ ugF@ 00v僞鰰TBJ*竇7$^h9Nc^虔*=4pu6l\VpJ 卓TG1攸{ }^6.wOt?T鑾!p8Vpi!\_ !YRX哂L#eP?X6RuD <$P: Ja恟<+%@2h\b(?./U{KsN鰔p怨h.s4.5Ir4WG)f16r I @x)=KGG(單FUF^邂゜V擦}Q9‥l wR 閤Q$o(b $K-侮`y,Rl>碓PDTY1E代%2dmSぜO罩:-2P)X{bISBbg/r鷺失gw 竃3x援b).n@)G.縺nE縺'rr羔篠I紅4Ej@aGVz?O):|輯.Ge萠v二Da( %(V藏磴,u瞋]p;|π@ |+J Xx;:i19戈l$A\A7Q9RC娯塾uぽLA\漑b{gC 癖'OD瑪V:< `35i8Rｿ C攬A>Kw' ,痺4妄FS9d s*-9rk ]J&R@ES y$B^=)著Ub@v&河S>euH蘰]8i ~ご&JdX!H&W+OB.朶變qbM%Nhf)jヤY-Rn2P"Ｉ!Nx;3 △$uIrf(Ir> (TZz陛>c斡8f圄/d\3j[ЕxR雀>N? \a@dL%Zm7R^灼}K*>HQY粱4餌s- vY& ,阮B,*03aWJ}/尿rG"<研#5[娶禁-b].*+佰9zQ cR. E.jF1y篷恠z中n象毬丞@枝g鳫蓐窘x幃>"6R)YM` 6M連孤鰰2>娯mZziB qWRHsQ.P沓P+ud.褥e#:艘擁%sqT ;":O*!,OH[$44n3 ~K;9grl*g]|提OZG誑箙}荏VF4yqJ/店0?8EXOZBr5 l\aH0XB梵D竄貮7+$zD蘂K1F{!<h_ 2JR['旄投y洞MyH沮髫 (P旅釁O旃Ds%O 9鶯*e{2Bv2e解P]Ij夏G澱A薬U%f).贈店W js竜抃A"AE$9諤v銑AItM儺H 6擒莵nДGVhG4&=4Q4W#MdHeGM+%o `r搾哮}jtTeXj2F/襾_府厮YDg#AJbTOInW?8FLF!*濯NnH )@JDa麓p%xf:%8r1盞N"$髴=G波u蕀2矜 7SNNP6Ln,IB{^均dC$nzBb麾FFed0QОvst"Κ3!N.:鱇8F2Fc糒?c糒?-11[VB@ !UGU,!+托友_}鰡=.<会騨6^Mnm#8X[\X+b釶d毒Xq\c++IfJ`7 X 44}")96y5;XgRQ WP7&E|檬吮?(#T KVFNG鑚8EY付YI>斎B 堙&V$ Qh咳1為D~鶉 sq 2N6b8/M麕s 5Jn_Sb惱Sfpn5M畝SdYr餡`L越:楸, bJg÷& !駸l9&U炙a/>2:蕚EBIA!刳K6i6FF境E;D猯S[  OgsQG想:独為u卩l"!Dｽ6-X4B89C &!e%j[牾[$勍~e-$硲BpRY:q@0キqfV&KQ8Kx溥VHqR8eD貽9 )5侠]3┘$f'ﾈ圻II宅i_ Dav`0嫡{'^4u$減Nc+~!ΗP~4Hy2GmT2>OpsT豆 q[p-s 麾SKe倖in@p-.yZGu-F7]樹{?(襭(Y)F7賁0""k/J3DFK"烽cdwnot>鰯蜀;t仮=枝Sl^SGDj杭Eo傷珎qvqeж6鹿椙褄wP桎XH憎+祕k9v~ ;OMyBt儀cHF9Pj!IaF5f'燿 & 祟 pKm98j]業z8翡波8p?)tz}|燹濃諂Cn"!J湶冐#xL+滕 L|ベP 1n蒂O)_O]5S>匠?nv兄 `f 噤?>[RヅM'呵甦倩YsEyb棣盒`og])冽E: 2bQ/f膠4?#經HV1莖LkN(N7Z>  ;z%"dQn Y4*ErE紜@R2jhZi$返y^l[!s子XOx?混0耗W#l["mfl桙9x8X5狸raV'm饉W21J惷\J|恢8詈Bp_2941魃左aUs崛ieDH"xN>〜<昃飲F =T68貍f?81% U[ RO{証x!咯/辭a&<#)(<(IL]#IU1Fｼ VJ,ctgU癸^n楢D[ 韈C毬鴆褸OfoWv"$'ォ ydG#' 5飽h犢xXNa9`*vQ p0dK_)a椶gKQ4F-%qi兀BoI蚯]1#ec*凶xWF椡擺+P7_|駘鷏b游<=&β|蠹[}鷓 #`h9D曙H%q$Qrヨ~,襲jY@ 1)莅*@^Y"zM=nOZ=J "l鉦/k0 粒6n P忠jRrm,3ガ ZOd＆4I鯉OZ`朞gBaU!M$ 戍 'JRtjr!G"kU椀牽3i- 'EQKmo屐＃瘰yDD尾a?bQm{6l柮>淮遵"(#9}dTp黷肋{|W5z$х@斟gKFZJ(B蹂県fHCO@R$"≦JyGL 聰H ~szx<驚/^l贍]v間")`9hxxF臙A+L)4F [P)p,2HТp噫C|i97^樹絆g@xA踈|ta"_E-}+1津迂z%!桎Wd擂ML$a挺lX屮fE坪v攤u,5精JJ；.A/_B?ciTm@KJMa:遲+Fg=HRSMP]XOnBRw暗HdL~HIYN'畳e C7H)w7V~L.滸\葡 0 u襴>JQp,瓔v6.ZO0e 落p艢肩)2;.ql6=Z`%FD'E苫H殆Hv%HH\q8ё疆gH(oX_icmUu儚2|Jo*櫑E9f#qDJ\rl独?tq?,M\r%8l俶"粋1bM|\?VA+IC4Amb$蔑~恃Yh a&(÷AQ]宙婉脈<&W&cS&Db~w2僖 cI mqbm$%@符Js簗l-|ｒcEiCrcC+~/jy+Ei\W\]TYbF9B-xv9Bjn"/荅8 赭繧冬-DG柵W榛h股*FoDw[I)q1Ek*PhRphPrj\\ fN2jcC J3ItFk)vQ{(/\y\d芳G`-滴]]T D]\lVi-]E'矼j8%)愴価?e-VXSvIfh3)x1T摺s)嚠V.U qrBxI*n'繃<瞞[m<姓[Nh`BQ4E痰限+hg'+s\檎G]~Tee5V諏)8>"m矯('\X7' <0mv):*89皇9 囲E漑臥沓瀑47X2 E= q喃惺$MId糧6vqr1@BL#a竏2bi A}R鞦IQGuW)IfV{AqM6h-vpUVfGO郷9zl|w>&滕~狛 uMi杉芙X赴閘|袮7燧./^}雷PN籍>s5/神廸2w:p霖HQ1!拐N5Yt(屶丶茨;R-鯊 L畴pQ. cT WY$閾2鱈@9 >坤u]R:(#LIN^.:(%$6*D/|,(!@H3YT>yo[Ix%餾q5nDTj cTa6+\\5Uk КE1!脆_4誤 Ce)寵p2x>.j来F06綜'-S"&{"-禿脯Z| 創_朦Q Fc!Yw R1t勣*ea軾1V:!vF&r074~Qj穃JN~9袱jt4F"O15lG"y}G@cdw7l5J 克el剔睫2}%j纜収Yeq& 常_U]0kQZI, XR\'03u{}6%^]3豸桍樓3誂.:y?9d怪_"<}r肭lh4#蘿* cC\l*"(!0 }"X蘚rvr YOE~1oVWT90}JL1竇w圀)=被b/Q圏SzhやBO$PoHGi?s電泄栲C\薛l"@~氷 kJz+W嵜遜xW%}k浜8k爼韶)e*~}路nOH?=>5Rc"9箘n; 彈グ儚[.;/9Z攻t\參@梔壅;~q' HX刮嘶┼7;u t:~ZB趙[ 絋%-Mv 掘RSPV_(`靦9h-J_G6{eG"Z{e#6 2~$A[isqX{Q岶XONsIpZﾅ枇曲々)孥4菅巽V=h7c4EB\)r[`P 細q|否u髟垓6挺SzuQ沚3N"Y偽胡4d鞦g\4褸e|'j;>繖X;Y詆JQg蔽F'Xi .`]J/_|殼/уZDcHh}w`xJH9qtb+P)i竄孚[sV臨4lVF髴A寐~悔雜jY IQMP_v補 pqG服,d熟匝 宗P眦3O苟限蛭n+"躬鱸R麈?z髫菅3{送_麗D答~孥髱E?X拷HE.'t/]pC#ャp傚4|踴I<^L^\t亡|裸_Wzu;Gjtq'跚BHC~觜> U締MB 涛;$1Qs*莅A_}ひ稘dn< (A>n_q!恍5'y膩】7cfUM妬hA:迅W*微__5tAi;/[Q簣^<\v濟3ﾙ唸;XF-zG辺|,)'m{獄_EInq&]}&lHノ'9.T# E)DeヌB杤r:V冑q太*M%~[9Y十8塾%z{z埀=Uc鱈+BB佷V= :If4燔0@hjrO愉.`5a西qO柿^ +xq8zgI圀D；J`同裙lC_6(着PtZNs:zXm%Vl5匚紮盗5訊u$"-$-e擣箟崎"IU+>l沸!u5豈L!8旱Jqix(Y写 歸(x壑灌8bz寃,EB?|力/^_pu:6o~|}醋艚>O[U_|#In~~"K8rhk放7^ 栗跿C江sh背#1PT鷄~W K,[暸-wlМ(uNO3ﾕ!kww/jxE壤yQT!V漢FEk物yaペ丐M90複'QFDZへQ序La!-*FI戯$` cD46&)=T0c,A ) GAa沖[4 STCd %NLA+9"*W,uH6\6GiSL-e)u=奎?諢8"買yDz壺7S$3Y)禅$$ #! :Erh{B!h $k3.psI握\B0'(9){1sksX $q36剛BPkN176~P\b7r)ber"V6聾{Wv:iW3F3トd#?.P,嚇\2[h戡iUsXGiNkiY8χU!4擅a).@z'-本B)k錙.6~nK峽vX漓 &A鮑g#srf痼况;Q:z83"09kC`NFQ]+[寢6.!<柔',6$ !#9ZT4 ^ M%弼oFBV90J*d-Li1そzE|8TU甼 _;z2 J=tR#R瑛EbsM`XP\W ]T堵ATx02kh5Q凾T7-B%t[#KS!瑚渥SRRP∽R+J5ON#y5.8CBQ掴.UoK0聹eX諏sYtw嘱/l9sU/4_ph+I淦wbΕ覆`>>玻瞶w特nhRk囿在?鰯〃?}.<;QGxxGxxQ[Qs; KΥ>rL如G *溯0U靈D睛擒/K朏@AX ),6鋭ｆqLaQKYl]終P(繞DZ耳皇仕0^鑷0eXfHN.%#%臑zKP^{Hj-tF5*3GFAJ\ダC!,7TMcwV曄?p%*eJeBH5=幕箸UyiK;=3吉2瑣e{h1{T /.ZU c LPKP:f藁Qu繹縲{QZ宗FE]i旆+7fPｔGd$r,l)XE8Ec@(X(wq.A撃$q~HgkR 譖Aw+ Y戌 杪%&fJy_Ld愈X'臉+)N%[の柬_/_\T7>}K`別6@辺aX 1 tTQG9YWoii7フ藍"恟D舁V<@>~ 摶94+o BCP  休&堽]l暾ha_40-M/尋1BK$sn-V gp,vV. `njA3G_#菱9Ｘ;)-aK ~TP=kz( /hfmq|輊筌[P偉:伶s$mhp|<招dhI|_]捷}|XM輕[Ha}怖AK"/遡sQzＯ2L4L<5¨o暮}7娵罕Bor-"}%[mB2A]3簪;Hu杣 tP=x0M+5g6oN'膳咋-敲f`l#H+鰈g&蔕Z>四(噴/壕i5B}_|8紹E晒ToQ+*喃shkUz:E{bS丐卓5BS餃F謀窃LL鯛\1rネR(6Xi2uD J,ky@0FVM(所悼n [zB?R>~9=;Kb党Qエ\ヰ2*QHpFe0.Y ≒e着~ZU{;庖 {B^((E?7釵j^{jrFFcD>閻渉廃Air)6C=Z9JJ|@-."!\;D燻修huA/~棍T/嘱]$:11V二蟾|釋=)l龜璃Gob,5Y|#n_]珠?N Wxu*湶eg曁|~鯱j#7漕9泱(p珱To3dL@袋Yq擁g YC@q*]仰[np'死Χ8(@宵#AC6WlxHn%!jcLH~)NL!d靈梁,p将?Lm"重@羣|6ru栽[m吉i摩}^Jb)x 7r兀xsy)'}D菘^}誇2p\莨jJ1 蹕q痾机明i-V_`qU`超bx5``C'J,>%x8(j[%7J璞&;F鱠uHfl:{0;ガ軋灣Vw啣邪侯?.X/+=k tTIv%PIz|^Jk`轟=+\6Wmm 属厩:#< R申B比jJ@>oT#MT\S/4O\l籟襯ny潸q2=l@加@加め@2o栄$L -Qv{M9zqF;8c< 8AQ QU)靉dex7ν(t苅`ｐ85;VLlf 遞sQQFq#幅T△T&._Ps&斐X:躊 聹J ;O| qZe腑Kb%[ldO轜>gl~h警 OqcD4Jf0P備H顆Xx0PB努~務_★.`r;M3rPbJF#>$ q8瓰>EI}3( H鰯S'ga:Ew査晴$gPzS浦IV_韲嚶Mx晃T+G7~CBH黄t髦率('v66f 麿Y拭A3p窯矧Q|>筬+@Uf囹~r黏U(>=bn~1r>?榴l-4Gu[^~э+Lv謚q=(*VY #AgHHql7蜒L HEAU隠麺Dl47D(.BS饅廓HYTB-E>cD*~2VX.@6XzI<巧9js池l%?KVI腦 xkK6e`!粨y*k$O6e(VyN,l眸F$惺鬪*x 靺鐓+ YN濕 ;TYbH,nV4 :|5]/D.鐶bL92gvX#HR9 I脛9'4!{f}黹謫T/Spgk>3模s5`Ｖ,岌3埔C5深;e }WT碾4dE&NOO&-S槓随巽p{zCwqnfq蝌/蓊~?#vJ*_8)烽叔;CG+Gc髴~PGF "AapWx8Oh炬vR韶~OBDLJvp急L'@卒+o頗$G e6''Хwh=jA,Tq5twStV"/!岨|び'oUW_AI!衫塔嘶W|;誄蝠]G9賻QJr?4L|N"eT蕀墓KF=]s$gM繽棹bx@`>e9R如Ba>;kZF椴3son奢X籔;9!#Ml/yU_呻G頬韈艤|>eI[t{p{Ak B9} -t\2BQWpox^@@[?/酩'Xj`2狛(f哂2T**tn d]".鈞裨O:yL様 9(qvf=`~ &}X7臟鵤:'D止 p>;囓1u鉱|>VJCnう/>芟Cf:v- $+>1&#Q9#G椿8J_k_v!;{NDe)癢$浙tzN炙 Nn疵S!!DIc53ｷ##'鋪z琺^|*~Gt&[!粤o~Ml_8水/燒%_F愼Dwx狽#'筮OhQ *}o B銖杉v|或N?x!缺鶏3(g亙9篭屑r?, I%4Dn?+S壑MDEFz4[+懐癒Q構<謦,侖^ G:|6"=黷qvK孑/囮Wz=?\]:笨NＱ~C冕 ]下R.Q@# ]}moo.皷GOxbv\頷輕sk?元浪n;`hW>d]找&7蓚tO統kA!婿>o$s:p=/`|o;^従S鉗?歉k\"^wa渫"1 ?{6q 丶8A_o}o纛o<r溽't_xkPCN{0'\歐}'  yV6Oa蓐+6Rv-z;yo~@qW笞陽a2完+ｻ!_A{JQ%]\}SJw@hrIG-^|H疔aqe"*QZ 〔憂~>cR臑6.Iz?槲s=\E?eg匏+赦遙@?\皎IB9Z/綯w;F{d紹rc o-mcm-9g閥<]<|:Tzzs R6鯔忤^黏4|ihC=Cu 2/磑IsT<鰉 悠{>RoP-DL~鏈hq5FUL,nd3O唱)ｳW>]懦bSt+_~呵_s^ ~}t]]7jKEW労'Y<{KK=Exrz|{嘱8^焚5m+Eo$+l9炳ΓSnNk\;qo6浜島撥p窘|#縻tQ崔}+G[宍酬`fGK%Ksl椶濁+J/ef2"jH1#t5正3免j崋: C}粢Nwkn{fU_族6Dy齡~ /x陏fa)主稍+-g齶炳ogS #j忠-4#vyW-桿P3疵j( p霜I`:?Exp啝<4Hv>#(el5G塩~0+/D誠O!4V"c縣.b昌|M十w/j2 It鬧齦q貸zq3o諜|0CW ]m~F労OS%_藕桴~"瑞p］;N臨赳nm 嬶/馼HQ腋y'劵#}9Y2L臂P:b6[|q遶&kW係-煖^x笙_lG承o寚^宴旡+5FQ棄授巛x祇fkf |K銕lW|] V崑;-D! →7g%a斥T~戞K厖崔Q3?=cs>q敝fR[涎'蟒r=[7D&笄[8佗kn蔵9痼_z窄'KI}9舊rO>tD#{%$1h&o>ZNQR奐[4(禅lWdv_頤_}D鋤_4>~贄?1xc迎z%泊w綏_1E+餘O塩*咯^|驂g瀏~x*f盪/壌[sI就 霞C霤pj+饉艮\W&湧襲;Q`0m h{礬植W2TPK嗜EW1鑽Hn瞰 R#7}k凰8`l_PY孫"y#U鶻5曖5?L?T硼=5}節y{lJ$> `0%`8u%?攤gL涯fYFV'F@BogvR(rNn LE3v*(@wTv|ﾖ峠POR7或鵈 #]~^q廷-魔Q-yW故'単1u紲=/鷁IB: <`8+giyKSwe排Y'$6 2>D$HI< 促pE: }Z瓶闢 B艾0 n婆CpL K J$(NkS:J . 搏 *~vHbsxr#Z9&)[%rG2yL4aMI縺=D$Y屏8CEP ;ｸ._@9M稾I0Lw8s魘Y _T眥! 98m8mY發eqls!@v+!Sff＄D蛩KTx蒋(}{鍖6bO*%3> 底j! ━6l1S$yC!`yacф2{ v.端Ю1Bmx<:yVaG 殷~=f/0p]M;婿5bAI鴦^B2K$%. \-QsuWmRc柆I vJgＭ ^癨 Ｏ/cj:深^;%&uu.鐸％_J匣p虍!Ω[q)%[:{{鐚Pvn/w&nU7諂匡Z]6ｈxjmOJ鑿CNX5 PbEd)x3筐J<身M5 )PTfM:dB黌fl靈1p閊%l刊{  |nk,1,1cGT爛Vzh 憩:^ }怫廠:i\dTc,eI$v器 RX綸;塲xVk AjF脹陳 {xlmJN v)/?- *&vI 尊K A鞅痳獣い]jE6L|;<b E/屠奚VA]W.g8 @擒瓮岐尵F>7碍ﾃw?:7T剩@亂-]p+}S$A(! 洙Z'-aXfo椦fd離弯EL槌~rpLmV彬d堂AT1ZF\e2]ZfI3;8vuM:F23C:P\5 "\Ef舍!P~}Q甅__a$ ]_l /-%'奸筌XC|gQ煕iF 7N棡Eq?"$HV lE%痰WECxJ,S.IH(#)NヴRjA> R|uFj)A RI~Z聊=漉M粛裼嗜譲粳揶".[_#@A樛 Zp50 <:M85棒魯F/]塾(%B#u;F3B{Eu(-&TG 滞[餽TFGgxPT7聒W9獄9{[Bmsy`^XA萃)%tVMqF*j`AuJHuQzd鑪n^}>j:t*I@%ALHR\^\.>冲狭╂棚 j^J`帳sT\w/踪8h鉤J1Zu鍮sUlpsT讙r[ 螢遶&B皀p45 ダIPiC63P*CR5閾檀衂rm%cJ7.B凶;vb(!m6 l?R.od ;W6=lO$ UbH鰥$nZ *RS/A${U'u犂I\憐>xE%{S[f9Vs若預we銚輿ef:pdF[c暄"^ L`5計Hs萬-\v蜃.,b痼 ;D俘[Ou.{1q3_8kw'-&6 .彼ﾁ!/C>%^ _Q1@竟B}n>戸iW嚶#映lU蛬}ugi三隠&upg~y聢LC%鯢 ap/k'ID;OqL^a+i}sF}j5n鮮/1一禅k_禎攫燈\追^/MUy@*`4琲^鰈眈|伺 躾x雫~.΅)Iz_ni滴v}OqD2P惓{xI謔}∃.痲v{nSt弉0)A4nnp} }P嚊n%#H9>LV戊zQsMaPpdgIvг6e０`L踏<)c齧fT$5aH.h+彡瞑NKRm^C]H`]-/4#淇鬢,X築t#胛5!韭R宍Jh~慌 M?F.切B 會V&$DQH{dd{H^cbFYb%SP0)胼R\% 7NT^!UI)l" C)=pi1"控瀬,潦4#+1鷙[y^$催%gA荻{嘸d3#奢"q"IRPlQJj`X}b\2 d魘Uq R\[.Ftﾙdr>dHH(#鼠x啣EaQB2ErhM6\Dqj2\宰Sc$T擅w)EBQ*:ej?tZ涓(δ嚠)顫F\)5?Hj 墜(J$G.s浦坪(ZR[W,9eV篩 vk'6ＷJ_U鈑3k!=2K hZ^/桙#t/k;儷x5K卜lzqjJ筒ve嗇M鱧JPjAb-jbU笑HYxX麭(oS$ 唐ex儉(U匈q嚀gN七lNw{ \z(9; ng$<]{`DUI祇俚3" y.)I2B2縛Z\50脂}=x)y_ <7覿0zTFaR^DZ著[J 彌G歇a8R;O0Qz供>R泗I-0| =~O$O蛋旛ZG,Gz7Fy腱7qr韜ah暄Ch簸Dc)8L(W'瞥,尽(0鞣%妬 -:Pd鵝_g-{/瑰xk塙A]枦]dc U31jFp[并.患9qLonOAY0nZo^ 崚Ff~ふ%+罵A9 依0l#F袖0LPJg},JpXF0,6y!l `70IJRr靄S÷-D￣hmrU驍h撞J"ZむR+連_]"Y4vrR鴃bv`KU渠K%RRD<Y+硴z(}YLXD｡ 跏(aU}規e^慝表qCa q耡mDx =%xUjr'#X沐&w\4O蝗1* 轌B<*Z偵wqP q}n`-s；GJ鰤!9p鯲C8o画}$鐇#~圷Q驤{JJV簽櫟I{d屏〉=D H/麦}呈iN}砺d~5%w,a霑麩苣郵dwт^#|4AAG5\霤mKK耳與'nuY5豆!M5u!絏N搴v$ xfcu[|t1H "ザ9 QT.RMj tn-" /`P}?gc;{ 身~JM%P蘢3 GM喪xj?滸S A聶b6\滸r!WΧ+y6Qc｢G [/7 ?(袷`ロ\鱒郢呱j(角Hj共~/&G橢)i "V-ZuYKUe,zＺ 冱L@5tLF遣Az_IKd神ZJvLwLm/mC6Q1Xe▲q{{[S肛~B%6几j(qmc&ja峇3!]W椌M-(OLFj冐f:=kU0凱}Z<"鰲@N9U;驤頗qts0:嚔娟__WP4wuP淤kts (噪鰛'.@a$ W^&憾w:wO^/Y S飴W杼 0 m6作Q"FあVSR 茲=5r:+, v4r\k$ `Q}E疉O>\軛Bs\ED(Y何KＰ>&Sg'x) :,歔0刀_醗*a炮_舳A>>Kf3@?vL巉"`p榛浸砂~`戛m闟ic13)8L+bfYm2H}A.皚2y1U良*j}o/冢mQc-8]dh WG2sV喚}??g_~keS雛卩UI{O^忽熟5r輜kKD^D5鮑梼E$o凹3%;=8礫X6颪gwTVE(女 %+o帥yK]yHe胴l-_)f#T6!6}^>lS燭8V#閃eH婿Tp6嶇塰dm"\i^ --HE狐QfYct`R__怯/Vz f扮UHC;'霖蝸蔘ー遥T=a wZA逕鮠9@M揣f3N RwC永JY"題:Q(wC\拑 a_goZ4I zqxWfX%Ds輕$?W#"e[\z5ャ>】珂9.MqHaLLci Zi!bUM-襤(8S4E]寥鬢Y|4Jo{z5L剴*J]j(j壕=巓?zミn+#ほ /C@~B3_ =貉り[壮hg iG&EY07YOL2is!,C+L@牟~dV/c+coV0NＷa嫂m率靈繝 N餘/￥4 ,j\!悲掠=傭oTM@煙&s蠅f鴫Ρ)(%8z^茗D殻勗VP取.Al [2 +fz獰4BU$ ,磴|襞2釜Sg2|r|CwwD$ 1逎0']hC奢g 斐G 'T+ca賢eN＊命i陋魂 _S$<64BL秬鄲舞K|26.~ Rd/.h粨TFr h鰹 o_6UA*〆?C-&!t頬┗爾Z{mQ簓0X若Y=v遼-y5.饂iEQOJ9/4 [@複{*:/Z臭U膩q!*/4hV蔆縊:}`~os麌拵魴-D霍IL-Xdx EG+q}/4乗VG,]L_tmV床EWb_tトW6(M/:*>恥Oaqg*擒/:d$鬪EJdЁ/:(b/濤,~>(X粋L(裲祐XB7]\幻zTQr飼- )悁VxRH3!dF+9D叙-LC~[TfTL'J]Mk申*3n竣)*吠bpwl^T:CGx3.xYe}\\B%> M}e2"8_y朏_zwyp 別o %yP'tL9:r!蟻>芍f峯b4j;C=2答S dz督2鞆\/B+#tJ`<}WBZxIA" "&H7}) DLHG9tON潔VdjA0%e[d6kJvｕ扁_Q}3V ygPF<V0 \q9ﾕ%!答X/e鎬NRK&鮗q楫(7餠T(-;Jg,J厩L- 敏C):w臑\^ sY*\1/{*肄ゲ/}<XS抄z)Rぅ3碧]Пi柾U色 -8y)j&L+e^%Hh/0%A)eorI愼E0xx]宙記ATA溂扶;壺Z>寇8Jo}\-氤B50&Z(UO唖堂乍$Xj3.RpR.gj瞭G竚\p4N店h3亟2cHg!>黝[頃l .z+銕Woj7水)`BP D慱rtI.п;~{~c|寧J7Au(_zE2aP>g\#f_2Y=覃J豌ktqlgCM92X\<(猶B兌Ch銘 吐迎/h22*!Gc廠Fw黝e 8}?C*頃_^r据Y私:&8"`i#) My% 癩嗟皙yM者官P彭NYg}(哇:<驕WK映%h=yx鴣似k[E%亊G~訛~熊坊 .#!z9=悉{T)pcz鰻|B伊Mo^=)8}>x失;/xx}譽\去k(檀鷆( 憾s+^4J`rTr^維鮎AR マ']`IsI-F]-0R=.2P_W3Mx7J燐U pP浮 \b慧瓣fc$i黶X!wa%拂同%B姥泛>(栓0% *+t亡KpRi{|' AaS@儻+$Q&#lN邉qLXWnR亀U 1Zほ;s盾~VJ,U;> gB^{Z牆j%ぽaD-O隹V叮B {K`xZ埜9 )曜a8TxH怱襠H$T)售|=0"pu JV 鷦FVF~t>-仲(禪pd2J~#2L^fQ個第zxfoFqt3x8,5韜YceD #[My齠dボwcLг忖m2\t(釜莇$8c埔邊 /9緒哦DRB jR慳M濶"{◆cz娯&0,鈷?Ss#Q{D4D膜蟶77 胸,NQ}e鰊蒼l朸p9Q憤2d/(t |K|Ez眇D~nGi甓|殳飭4挺Nu!bC紫H鯰僣什冦LI D#jq昌i/_3.+徒f6xs{y)6`8惹 jdUbp楮|ocl34^mq鞿dN泗|)裘V(狒B#8G r碕瀝6y6yHJnM3qQ#SPGnBB b6<@繻Z鞆{ p身iRh渝寺);DfQFt`W:B:剿Ka 3雄o(8pr#A2OVofレ  1<6 O)R$陣gDZx{]xc煌n⇔u-cvt 5^!@ЧVb ; xb州@K@48QR@SmXsU<6KKc'j纒b\TDOa HGh0(0蜘inbRY4燿凵/[ SAS)MHW([dOKﾟqI臠&`赤Z=Jne]47楢QZlE{4jsi##E;lI60b@2 9k昂!7;-% 爵QzL派i?k:`S@鱆CS uG) k0箘O*煽aEr z'ql&"8LmY JXrZ=)錚`B螳)t> 2咼M Is@$l)zG)<@m違 R,先Tv[抉殀)o 膩=A街KJ&xhv椎%JyK輔廨:PaZji記舉N+TjJU[1r際)w咬誄fu\錙塙R勃F}臀iPx?Q0hd魎/t4NcOc#C \f指@MH:g[[(|g教&e$|Ln&) wvxp杪*#DksoZ7甜8WUj0c~ M)絃麺2候}Is瀕TC猷32>,露@ $c操e\A]S^K :oh~6;瑰lQr ^xq1j^^Ys訂.0;,b_a寂%= 0^!SA2`0,,x7AJy＠jZ"rE[褐krv@驟KD頏%"S隗r\D茗&Lo|J k_[3<H`ZO.V$[[. 魍A^Vt{S&坿.c靺MZ9L桑\Zfz曄 q/V,oUr稾VHlW/VU,@k9Y>CMlnAV \8a.NR`]b愀G^,|卷b/cwXmmJfmzkX~1槝L;穽)33J瞠~^U!w %HI?i綣u&#LhZ&vUj> R'6. e4 剰嶌8-s$n嬖 S偽B$<{^#眈P Er0辿x"Wq@e嫉=u！o~pYOh1雅靈5;D5.a蔭Fxbt_s},A2Y拮W艪L啀 %zZ勤gK6s5`m瞭%YM.4 iL[hN|5;_T纎b粉li>班(UY8序瞼8I箏/~gXDx咄][J6_dDC{菅盪o薮權7S窕p篏d&k`@-乏qf&aj88(K@0sxg4"P,週;3A.)E18Z:(5]da.A\r%~黽\赴Q@W/XZrS (gDh $xZzjAkG!岫8ｌ希{):-vQ2jQxR96<)#璃_a/8=P溺掾7K圭欸=s6C>勒((9"#rdl3j騨u(#H) Q)hSE~s`lG(-褊錚e9(n$1+鼻y~))悩9関_絋Bs[olMn麈*~5I.受3km填9嶄+杠9A 3_8 h伍肩:d5SF )E,k)9諄5p-JR8+ 9:U>$-54'Ne$M粡3茲*Ilv_zQ}-H?1$g門 xs6oGg >T_3.0lQMWN彝=h5=0=v 拑yx-2*$?5$.F&sh_Ub変U葛 |4hU*c尊A髴E礑)ed桷e~戒 B JR*=硲5x嶄$槲S=n尢]{\( ZBx麓lWAQr､3J蓿\r鍔rNv7(=gB$WSV溷m5絗袋I娯!Q査&G+靦jc禿%!l@yv科:U (j飜ZΜ6|H@U婿r痙ONq^衤7kr5.!!SYJB^.8J驕0蒲NqKqb蟹百s〕;(sЫz受Z穏>露`wCr!$p菖. 版÷/97橘K=(H盪曜 fsJx-/宙9p盈C[該. 陸撩T[w參x折9C)TUVC $孕Bゲ4嗣~6x卯率9X先zq$i%I0,A紐 _X饑6Oｔ 08{`:糠{oIQｻ礇%8#tso裁'+遶Y?f窰:{ ^･Z馨9hBYK%,)nd%s彙.5HX41a p譫T< 禊S毅網M8 .=V丙k紙as%6F負HAE9a丁房h?TLw紮#)<Т#)@3Z-5 duYrCBe0K=(@DeqU4;"湃ALC栞gk怛樟+G>0 /CN ku \)]ﾕ#羂Pss8ns鯑2ﾋVn\$s{躇P儕曽( -A@^C稗誄B f{^4:+%4)3[Nc8言尚ctK *76t普鐺h瘴脇i節.貸C7j\JZ6jX5F`\`)LEh9槊1總IGyk qmr畍Mn*~欧\_LD 竡B濛PS3C%&)切()`mdgPFhL{*:'o襭薹>5DAF5DaJNk麌F#k!i『x) m越d梍~又GiK,^L.捍|Pj梟iOΗl^喰-習>fru}!|荐2-(撚-*G扁BQ.%*0W+ hE罪O蕕" QJ[0pA) 4 qI兌$%冐9pY'p[B@$考彑兄bvd90-迯D ~cR1 RПばlq`2#2}mq| B八o兜1^B荵0N\dHFn低PxuQ#~i= yC沸h8淒97b-OFlg4%鰯nJ駛d6J"^ Dk戔膝鰤Pm vhZ吏*BXOo aBx-Ga3荵7'e暎C悪99@Q;g^N 膩膩??滌漏:~VW.-rPY.{癖畭 ;I=[z耐1qPa!*o1婉zW*博B.(g{ SFc9+莞G ,s轟$x$;R*'/#療g,游聞&(J屠靺gQvGo !9e;H奠1E)旙)J_O*^|'zY箴@ # ~sR \枉_M3@'}kQ\C毆lC-斥RP%#R切oajiZJ觚2魍Ac=Q 孕j) 轉囮2|匁k来 lR `dVGadv(b\p 諧P顰Eyp#`t.´$GH裲2mjW4^Ke^QMppG(7欣2Pu昶S坂6/7bWL寇赳rI.鑄E.Ea臼(WUgc]圦zスFrA9V@sF8U竣F(${G h挿fACxzw2l[7凜y[2o巵makkwj!;Ks新市鱧C瑳ZOE>0o梍賻I pe@~oKeZ"鵺謨O¶va紆EogEr EiT[2p?h礎bjy E+0籏∋P拓*Q|Ox装=wxS"施\ F+W鱒D]慮x$k 晴 S)eY~餞kIq=FR]({桙uoo.^-jqF Es2系7>4ラ９;жf菫UJk$-A%ag,  鵤E:In旛R(偈=:uJ d@6 _TH梧d紗G.qCYgyz(慯皇E*J鷁M^|.Rb*AHxP覃,#@ 戞~;QF.啣Z4;遥2SP蛒9eU^6]di>R愕`^]]M6ggDA5t";(& Q. =:2 #3-w?UR 鉍GUfツZrh@5Z4 Z%]М`S7^a;e?>&O]:-q`鉈\k叨Q[鬨%Lr<侖げ,aOLK[d2Kh袤%buFog代cwП 癘}挨 ^d5@#N28冪(:瞭eA G単z^靄銛XDk Y`2x{r!0/ i痛i$p4\%'hEN8框HaI^6斛^JN89j8v,鵬npy ri~戯螢棹9 !bQ.封Hx拿Dw#SFl口S~%(/n鎬m妝'-)\0.k$料]JZb否2芟P_薊束_法転1Zl寡y}跂}蛛河1-h.l戒ぎdRZpB莇8N\GGI雨憺KF鵠\.觴I移e蝮黎觀7]zp8MP_4H旭撲Ｔ\0(z!Cツu'$襴O年l<ﾅ2<ｺ9#8J3Q椀 ,8L NxkS.Sd/AK ;篋. 譲sS瞼闌{2]^ 5e?該MO2Y]& >m$ E\2t跛Kqq#_t昌<_鴆蛯蜊Xs菰~5/疣Ia{5o現a籃db@IE4`悄WT碕z∂QC@沐d}/嶽奸k~ョL,<洌HY|/女=jDm!RЭE%&> } `FRpP )bM-0撚; УM紋詮5tV＠m鵈K3-B^fI,Em5JuYi哦LW*B.楴.H1go儔1.t＝兩7p58 XEM3H_"HHD紡_zNd\RjW= ?bI稀{J;ptD)目6F:J&瑠:7g通ワ俺榛5!gVB)~兜Pz= T].M獎+6婉>Q8iSF籏|B税S沼Qp=SqQ瘠]8W4暦 ~6煤Xr+UEc\u2(峡購 I8 %Bl?jN臍D觀w P"WЮ楾dRQ$ .1S~KP<錙8L/u8z[貨/離=痿 I]8+He 殼 ) z潸QTpRY/3l敦71D% VIuhQL>1j‰yO3erＺN=2^LJ#Ny\ov/Q|Z R_ｘM棧f?(Lr ry=急w?GP !Wxq\b1e2& e夲Z)b7p苺y穗濯灰CwPoQ5)├浹(8#$j愴b踴K鶯/醸?瘠録oO=;鬩?NO/_鈞MsJ離.譲鍒蚯除~}G^qR梔oZzc?j♯N膿跌.n~刑砂}砂菅GW/孥I璧Ts9V穣r犠o剩7鰻,E &O_/.隨燒H/SмN 氷/>艤Bty=HVz)3`k"w6D}|宅椣 ^卿w喟QJ貎>nP(l]僂8aQ蕗9s埃L ydRL%E∇c卑-%狠兜q扱U篩SA9距~e+uH写] h6YJJ|J剏&≧匝MB6蝌5uZ"''\r)D良!f :j]]C芯ef~)mH蒙,Q vyG'[g.cF囃VmByD^s.yWcT昜/v魔2()(黯!_+Yf箇4&XAZ1{+rE菁g%4 eo't 0,Q !p聡]k)>s酬% xO OzSj1ro擘3-B-#Bu /逹也.S觴蜜S Pp;^u嘩帆viVS尭=,IZRy%IZGIH沐 ;'-愧{瓩qleM:%w["#o>oN3M^Fb6/'@拗F. Z3}r-VN!繆f/sv彭項賞\ )f|ｯAHkkhOf覡: LWc-2HksF} /康[)Gx勿])XC餘XA闌O9*ｧQt=u.w|旺'.此{e腿L$貉~:LRZh a!捷&1cK2bL[8yS8FB+o瓣Vd~ 4B儻瘋HoT)瞰s|)i吩\w3;$3Oc } ~my kR-QL)Y +Bポ飽=rt d?愧p廝o#*$dRUつU)M6#{!@.5屯瀉d# 埀\ VQT2)f]kvs U険t} J磆A}cj簑nz):?=x( b恠積Hg">%3k S笄3k茖堙FB6佛!L9 %`4鑠\蘊0$])歇 ,*:展2iy_m p{Gth&'5pF(}租IzP槃7}f*P7 B$替e拗2d頑i凱E0PT1MO0Q%8.lwNs{38難we|l[麥b >V<9 澂 1^m鰺z^g騫aVrk`G -艪y>U7{淆跨*糶*>煽glB"J9 :雀x)``zt^Zy消+y駟 騨x \羞gFoe^衒WZtxzM票鰕戴怖nyk蛍 [Znk.Q$* 孩7Gy4;贔T' 1G厨5* !H r<鎧\Y *OCoR┏倖0驚P\Y?-qqe塢]\.棚d8k]WIN 掬X!f1mQ.D78m^?Yu唱9:K鮗Z悠R萌/ @qS斑b =%I}nb拭廣ex髴xj>?~_驛 女0'Yah9NBv y瑩A*IqiねH>%#@BBm駮 6wEv)"AyS$u:K<\*l|SR@ BG7e!n UMIWzt垪pp].寝皷Q$y 揚RRzlZ莨苙擯崖wp Jcj;_SG膜rA].E棗禹n‥R茖|)K B(恭X: 'n1eMbFmH3!(tA[k瑠ﾜ餓N v[雎КJQ| O続膝nB鍛jR"aN*KSV筋Bq寇ゾSbM& S9t,} 77瓸GH担X螽99k I kHfQY]7C< 22ViW%∬7E冬N$SSu>櫪;|li簽sLEI`#5M^W?E滾 e洙 dvS0Iz療f蠢k'$)E`冖^,0e奨?:譚fuow~qt俗AQ}Q3"-.k'TLrf3!9(Pj{Y舮5T{熔"q羔薊pEY福24 `1*&z5H+}噪C砺dF5Q.q畛O苞Z丹IE _Bf:A跟惆肌l. 篠GFX(兆*E`J始V60禊QsIVG=~懐;c /瘟で,煩u02([8cQ+c~&8t0吶匳S%i)X,% b孫7Qr壱L=F7摯ekf~x}_yxx B[OO7t\敗散佩~|申殖R|~^?&GKW付鑄SWo犂Kxr7u<\<&/y@7老n0_2Hm六>鐙?) ^招O7森殖^5貧|}u5(_*~鑚汪 o/Q鴟W棣hg<-~ 9Nw楾g[( gux+dr_ 梛+' XP/$Q a?K隧^_}Y`隧訌l境l悔燻銖O`鷸椙=0風T({^隼4e?MTV]ｯ⊃qh3s8g%nz襤使|7#/#rrqFy5KQ5Bd剴_},0es[?NA&>52[C}CA臭こ鐓jJyCn冉k知吮Yw/ AS)K1嬢憾V)SE鮫U9#`:g_V調l29lwz^Q1S(Ktq|~n$榲A*g琉AZhピ[a.tHZ J6G濛eb4/錠O醸h粳*'hB;〉ZV E+E[.,鉾JF$^cTWSQh2b.}-Z'!cqY\R$窗ツ3 逑N[D"@t-頑YG縻菅8G維:yi$w&_%I倣L盎6y],'t^r l&LK .TBIvy/K断褫py/8oc齲Qり賺w硅蒋栞+:炮歉x_`自27\e.辮眤az阪3"&C靜賎¬qGL #=;/m8}0裟JN*4G]鎧.d鵙LR絢,^/@(g}K麓)/,>e'%Qj JyaY殼g#;UA V蹼G~T.T~(VrLmrKel＄=-抵m(教:r明AY{{ y 6e#殀6Iy QO|S$鴻5|+閼X!UYI*3"WY瀬y[$篁#故塰瘁楔8桎xfY8+*疎6頼qd%pd張R創F{ CFg pM1纔t*B;A,&e佝? ,r G_-P,遲X3?FzR_#EcV!|&P5A7%ト此`dc{カ淀uY9R牒5+#O痲l@畆m%d,}v+=e(Q誂/FR創eqAmPo弉'B!ZB ";i)`[naBp5{邨摸党Y6I輟Ip嵳g9tQul1O2W注善.B剴p_3Fh e$Rz7^w秣}楜Aqg卿x;f~Jn;y+En(3II$∪~@4Ll梢*iU-mH3F撤廨~E_| $r3躪/ 搯1P&lEW惻ZこnPA拳<&ae0*,l>89d5[)r/ 2.-V橡u軈訛sNr& Ib`Yい}x鼕/j]9q\ 迪}*E`r籵}<.~捍g稈a<QJybu):/ソ?C{魄-I_6茵`ziC+~~W=s@9=櫟曷wb飜U\珀R]刳N'NhDesyzMOus:]烋IEgj矩鹵5p{wyW~}pwGr.|西 tXP9尽屍O7健Eto]菷*%哽鹵A敷rK巷W垪T!K婿啖Lﾟ路>廱q{=鉛V`J9藝呈陽Wl套%{｝[U亟癖歇&RYW∋箔 f^b蜩Q羊_WO1nN'r嘆"I 頡艸=!3^o~xUo笛WGI%鴟=y3G尋>TO蜒<韵Sv樮)ьS~~kbfja*@9|6k Wc#(S:4{k 卒_關qj#曦#+'P,t5Jk:gDV_2ﾌS逃arXP 粕316(V 淋8>#}fV['P(J苫wYbb蒐+y y妣3%v3 卅OJ鰻N)i<" 楓X goQ cvkリ$瀟xxキ2i廐Pけ{F`E(~彩=7J*%~m[洩e `<粐=sTbcｆ戛m.93}i)5薄8X7有`嶷ZL諦 w0枸ff淤[Z><咲W墹qM[Vl3W_N,HAiUo0萍nQX|容%/l%lE*f8QENb#RW%g,x'P~犇xK薗3Q(gLQ| *7aM奩}C '3!TZ-鮃 Q^8=励佛失#d?+%%tH?XLr/9秒Q『1c謖F'_#$xm動>)wYPx;摧[RA[(z觀v^%\L(遷^XG )7m.Ob!遷sv )5$4krﾚ6a%iJy(KmR ^I2,jJ)\欣(歿)}R?se)ps.Pf !PD cap)d EI Kf表6#y龠kV;`謦ZS9ヅ5+Q僣e@LArftMj&!i[ 卻b @\xI*EH称9t@|=GP}P殉^D脂L苴.ku~省 \L}良y(R}|VAL>J縄\X考kU)z*309WYt*E廬SC94衲幄P7UR卿RoPAO-涸V8{0u K|7n員 =悧94FEv 搭}`wy ﾝQ,AD%戲~ia3遑 cE瘤HE嬲7+雲zm闖 jv.vz0P懃mK´,;E{齡4E_1kZ RuSy2j)$緘(hMt.@6(\K>A3LVVu-弗c]k bCm.}Cl玉Q諢繝d縊"8 PfEjP5}_;Lux小;-5bJI睇ICe椎xz`殃d]kt艸溺 8-v-*|C]税1[*@W9)孥/蓆F3Q2 /bHPkdWk>%k< j-P毛麒^?,LL% uPVo\>n\姿b筵FlavS^&q\MJ欅8\RQ^g袈I_-om1k6w/責GB_50;:M陛@S>}Im \fMR[ふw酲wφy50I }h3$[;blin%gc71UfEys頷/飾'03KHL-C嚮炬臙邸:u O{3MfS7廠俣r|}~鸚祿mktG-'g膣>vN%龠.冉^A^.珥grTu9&w營喘蜊+dRyy};Bl颯Y)SVs;g%:gZ舩9}鰌|}fR授OQ/nO据 ',暾 o蠑,B=qB睡'7FJN嚥汞}驩7b(}咯跌o?Tr痘?V Br俗|馘持褪|騁7u\?~鬮,壗g|鰲^-屁CB闌V)掛据K貨\lW^培/0`斌漬WЩo^rXtZ巌包可SreTyL!$E鴫i$+浙q'L+cR#IH'k $)qd$ts%ib藏{r#\Q~^N 檀党eur#_o s^醪%w苦坐m]T煖Az吻uP*舫r皇AcKqH惹T(癘蒜$5t`:氾.=qE`gk円貪~^.錢嘱 ? 麸G蓊^祠Uh^w/奎|'(Q,R耶##x盻Loqu2 Qny鬚@-#XA席% &疾A$gMCgZC s 悁-Irf重.$sd.jC招A&I'UL斑{fD癇(9Mc=0 2\釋W,!兮"yqQa+橢l)hU\!Qs^aX1Kq>KJYX gK剽{l=|owv9Nsve=i " 3sI"災"r"]療褰9pRQx釖le随JD%Ny-%H:}似z8A Ik&.7(~bMS$vd[J往H pVJlGs+% 銀zh/~v'輾垓vThWN6S-Q sht"y縫孤kヰ`M國yg|W}臙p繊 3縢GB<ByZ< <60CKQF煮 稟 莞 m4J%I)@nN嗄^7s&(蛆)紵w9N <'怩'H(_B2Lyvu%軼Z ux范L% yλ年 *|94H禿D-顯\T8%mu<)哦LuTT|F39HAz|FMP}j嬲gt莢/8>:]眞,G峠>"fA+|Ti4.酎僚CR''1c0}/ uY眥5P舒譌 O哩NFgXPTP該RXQ5\!V'5,CVJ%I}x y)^VoQr<2nFDuJU)n2#CC*忿IY融*6^U拮5)(競A P cs7"C2枠Pg,iQ@[PHEB1K;8 V艸C9f憮c謦 #榿F?N?_n/tX^ '_*亰美_~*MAJ狹1%'#[d"墸:ZcULKBI箙U幼#F%y,{]q糂Mx虞mz\!G7+yl|菰 c/_.>Ig!t_鴣弯悉#gO憲A\胚 j.{=兩OB剿斎亟%hU k=^!+G?E Z%Kn仏b 纜司(zBR爻uUV8\[K|Hrm wgdN嘛 P(P4} Kn謗e鮓:/β:ﾏ-v5 Tp夫bc楸W:祗!MEre 輊?J@ K~fWJUl{`.A-r秀傾b奢[B]蔭耨X富 w]9蔭6\zniK e!U布iﾑmjXp mX,径HU\ R+=i趨X ﾎqimadL2X!稾sI{ﾑ{湫*苺c探居rb千p$2`|46Q%k3+王>u8e娟}/號跏Wa汞殖_頻速|>.E=Rg<1"諺W=6H@愕F k#9w](杙y#地ws ?sq^H黙伺."H?Hvwd褸阻"E閥7?y_:KS+'NP骭A烏S覦A俯\梱xK豕b':?PTM m島5╋`6`:ll$彈F勦 lbMZA@;,"'QoF粲 N}N峩\6w57^5)ePКFт般)A9ersz 舩v7 q とY)鍖&!)Uc桶Vk y倔袙PY5fF斥OKト+;敍2gk脈x> .)禪K戊S|6;鍼淡鼡0^L'W[=l蒹*d^tZBa2偽N滯Pe"Ad8 4:X:F蛔僵才 >D{`a-/\蚩z%b趁->\6K%艪j蔘<塁T )但~B~喬K儺W噐斡簓6輻U)`R~B_Rl*x晄k湛4'|B桐伍.AD 0 輩c )E"O蛔Af R.餘雲J` N8B"ti|]U`氷Pwx曽l'ZpQN融rl%iNrd6怒y//6dZ僮蓋wK_T N8漂男銜瑁駕^禽k(輻O[ Of*X# o2 cXR翕 h`爺h%tN告{CzYbH?=YS y:庵=A鋺b#%]["<'\["聽s9< C=oCN$H[&] f8!eK姑Z､XC%JK>Y+30zU0~!&j瞳zO娶G畤Va$TOb+&vnYJgs\1roU輻%Ru6.\t'SxPr?)[g?Af拳+iA^`綢採籏oe筮Q戉$⊥Q弘5I弘K &cif鏤$V 3>i@(8┤=TL[6X}UV;創ek Vm mJkl妛MeO弌 [6E.Y髀-?={x勃mM54qp 愧粃-[Zm2 {v嶽JZq棧1EPFO&jXHdN駐'吩e"sI8WVsvJ5弧覘躰凪KZ獏mm $9(u0Hm楸~PF|o5h PGK |yKK捷3 2 arq_循0%0}7EFwP<(=巴xH3i:0kdk/xZ踞葫t#Ah)fCB土:#盡蝟裂<rkLr57b|虧49tJ劣JNFP2/ )S瞭ァQ字l,男裃H鐘6.^[J曜!紮:翊#6h@o2ad瑪Jc菅緘mSkCHc蛋nN(乳u/m}6PfJ茘|篋UDy9 R_)典 zH!@軅X耿KqV"GP~"L0iB/p*Th樗姐`胆e1F蝉bt妖AH1bUm8*:A(?r賊2E . i71⇒汞exk桟S笛東CO銀Jx UFぜhz -vZl9J糟e9hF+ //JDfR顎教A詣%v淑VUH鏘gc貫闌$g|b|9231tZd光転=S[飭DL4 (UNs槓/^"B= 2qMx?XcLq{h.?^r VC'&猾&Ko蹴>m[ A兆)809'%>保娯0孔GI=艫th5 Sy)zC! !Ais近s + 讖WGz6*miT$Gx>(R<訪:6=],8lＭdES[;》#) a4=(%Km \'d愀%蝴裘Rn蠻秘5F訊##迴c~f-K鋲姥 %%Q>2{qd_鵝Ry訓qQ淌mG~Bg-瞼慕z$更J N2r]'tFU/\e[j.p馗b鵝Ve{V栲,mlZj[OhE,\/Ui;c塔z鷦{r1h90caSi+'衰@恬"+j襭~qv _6. 棧o<,F!= A7lgGxa雑孛Dj箋ar旒b$1VDp1%uW$X<8K^n`lU@5事案\f羸%7赳 2g[$> 90q\{"-S|QZ rJ NMl袂媼zu5鏨r8oAz8`,A\[圜栗;CtMdr"RvZ[UF:/穫?幎0y毘M>,5|Qr禎E緘qk/Orj;*W雄巣C6'疲氣剩I)u)癇E`;x=20<儡C.fz=r&sZ2"{4r VKr!v`初 を棣&{r浜K]膰 ,6d]A`> _*2瘢b(廚P\X[Y楽Q|滸lA$~JR瓲 -鞋 FM悩Zb Q良碍{o[|h縁jA}rY-# [済5e汕9n-Jl OQm5鮃泣!X4爰Y51G!vK6Kvk塩m@v掬&､躬Zlq]M&j孜)A'% y5P@e{Q) E"y痩-ul^uL^y m#Av.^D.W8(P)8 夢\n肘)rd緡V3*卓 FF&g-(O G酖1W|~l元g錚X=?I0rP配H?$HS 4}Y 斧b@ ^iG#轂Y~u- zFI者@咋膾稠"門S鬚X杰6: #薺 (_k@.8奄OT;h8{薙8{{w坊wL劫.%'X辭褪裃|扱Wdl竡篏p盖/8MOBz}Kh舗)咎序k8/PglP^ r$~8兢ДHR*ru馮9FU62;X姦 wPyR5=/ゥdW屯$_\N%@U=l 釁q閥}s蟷o\Y{將6%ж4p鏡RP2~WPQ9y~pj,))d9=S'q`%C`t=M![R偶狭-[I礎狷 ++狭Rk$cUR溌yQB兩!q牧7 W iy?6 jQ;VＨ!宿(XP蓋:z[rb燒C[j尼l拏5=[cg9相泰2嵎*7y &!I'4`ce]\嵐C$/TTCF)Sm:^aa6B) 南@t*FS O痴,6篇fツ_b振84缶CeI$s(xL紬股2Es|《?e$4sS.爾6+B唾e`C`$2C%S'XqBk>h4s ] 筮Bb生2峇 *vGKn兜Oc*(kd\$R罎 P|$G с梱@@E"2.:DT-O僑V盗)偽{Wk++lhk,YkK垣'oK垣)(WmヤDiB0J<d>.NrR吭ra Yw^'o[<..K舒汲rQ&+%\9n#:|sR1U-+#&G^庠8;du繊(即74cDv aG┐註M~屆GY%!?嫦.d;貞s跡笋"送 b-QvA}3аLJ彎S:Pm%~z#azv礼=jZY@鮴$ze_I鑼/嗹>C鐵峽AE{%e烝捧逸q読険Sj?P1P.屆\循B=EEmYe+I僅^Z=ｳpgN痔i&th襖",瓊oiQ薮*$s状j K=夫MDQ8d9!c~ 弁08"]γ3]狎\U 顱+K)店A(&pyt寫~W,d揣堺2敦A6;#佇鳳E}Rb_UHS*Ｅj`Q釦e|"!o0|t2n(l針bY砦G{⊂|.\/^H枡(_]脳Qa;$QQ_HP;-,Aac9m黹$7豆鬣6#閃 #gKaRsSHZJb n[句XEh齔uHA":ぽ袋@ZR}《# UI5J_J*2営{昴R<5y]#QL勺B`q9S2sU狹U.,ｼNsutB7oSr婉2~G峠.tnKRTB54Q)便ti?<0}+Jぽ~髱Oξ囈忠逗恫儿!鐃>]聟p$稙aR@9km k$鑪%k$zdRxＵ0# Z=4o輩:般 廚KI)]".-搖%Rr"遠j殲%恩tpcc+H茵曇Ua50qtpVPC嶽}Nnw YreBt樌L.["i>bAke5eqF8G|Tn\"#0y~ny!Pbl=PP&/瓏FjDGOX薙j^脱^j戻 a喙+碍M[嶼易h居麭2L害NV=SU]:=%辺:7;*P.*VJjxy\0x*6+MQ 0縫~:┛_徙" 痛_藝[WKe遨Is=箕~b }9^\6 sa蠧yBBUxh>6%髀krJ+f\b\8憤g-^tｌh}瓠<5JxQ%v~4D8dDU wXwzO- 9E\eI-BUH~=9覘=惇Z鹵C+PU急T-J思V;H靈RTj}諂 \w\処{{o@I)x|OZF6怠I@腓OM3Gs>助}ｭsb,-OhW}Zk<勍4#o樵SP瓦約zlRkP:F"nE'.錚*yTE2E [$q2jedW4J]i-yk(P>[覦*m5x#+僵S鐃D {ガ%b8 反$U0V艾@W>井7床; 統jb B=H嵜)%m !1RB 測Pk`TPRT&輓古muF^摑*Lz`iGlμｿ@簒-/+RUv.V^ ;P4*B翕.^TK獵tGT yG2h]l %VC#d$S#dRw奈dr$PyW /9&( ou轟Pd #asrI}該`鞴Ya鞴ACa9E?圻:[7-忍笈ehM;C/i)"Z"蟋 g 蝦n企OX鵆|wA|wupy0Bj草 ZK$H現Zv|D-=WURE)E)U_8X{P瓏@j2碯迺H-B處=複%j兀 5O",鷹LxVj{d&VIa(i 1薇`- `(_c0殉毋(idID;Ndl9堪\yLQFZ[zVA7添+doN+[R>接Dn;髱N-找zJ釦(嵳C]洽 c8k8K弭\0su}9庶G=7K澡G7襭j縹D&j>J_L2 Xs^{ uq$J撥i J茶0K9i IL$-yUcjJ)禁SljZF,思#3W_JW5-#j弐HW5p(鬨 矚(0j(W5;;U$YyUR?y~0Odb7sHi0O桧凭W若烟 LSI壺i$b鯔O1:f%}R+pk<a蠶D )2蹼q >J徭<sH3L,U4zIRP6IqAW10 轌提a眄洵r竿cXz8委娯゛x=A欄hR%JDPH(o}C廼X乳J:Z3l&Oi/!-F3j[81KYC:嫦[qF棒_tQ7a)>r/R籏dgDft祢fC#A,´p7氤挿Eﾅ8D蠱佚8r栄&!.姑-. Dk}K"5S\)fj+SLvm`M覓e<>DW|v竣;y瀛I罍4?,E歌/9逑*tO7}袰iERY]6q鰓2N A覘q宛5%$亀 u篋J I駅,e`gEeJ倭C堅oz}V3IY鶚u餃-h軛 3Ii4'8Ij}/├;=G\Y \ULNvQ箪QC~+/mE7亭3黯d,(?s秘I3F, x'-!JQnG喝颱Q#Rbll鬨`T,搭晴ne凛'^T8 '2Sk.kI撞 j縒'm輔殫L3pn0'LYcE髪X/%j5悶\2m=5kLm)[瑚鑞}mI佇Cp'%4g覃_%L.蛆ON*1q"c #viw鴕mN66% `qc)噫N{J倩(!慘]n]峩h妓Gn÷=-YV\8d嫖Cn整有 {|"sqtzxFR.,f5=kH;~fP杣6V] .荵a錙g]a@i9+qI y乾S燎Ix"<~臨 Z換Lz3?G;V9:6DQu7†URm驕D抜Bcd=}fp蟐j}嬬T`椶嗽+Hn |\hqH堋啗deE5〇nJ)O2灌傍,D奬 1PD?*:3c簷YK:f|董<>}1U !sA儿O舌洵 {[韲e])n\2w批鑪fV A隰 "D3E Y}Akq5VQQ火篝E/\ r閇evFCxC剤Pr鴾X\GKS.& 7T}pIZ0Z"?hw惷消С1蚫5Cd,vokLY>x0O !J=J2R9fsq\]WO#:iRg病娯AiC~8?Zq{$Yj邁1Kv5$I;F 綮,J軆}生0(bpN-Tx礎]]srC遣@l逃O9#琳`E4-N魅zRh0=0"閇4ep*3M63Z令d勵HES最BnAg8-->zMLuq浹ip5z熙)WLVOef1P療S`貢,~芫 ]涯lkbR#屐- JfUc:N5}b亂(x} *94H鯲(!‥チR+ij悵J彪Y饅E映7YA噫$渾[庭%GvQ%("aQ喟R豺k}p蜀-b6q:,s#T)剩罎6"mNrLq&Cｱ2@ b8'X_胙7LZ桎0娠aR`4R3as賄XP @\)9d膜uz刳aS濡:Y}AD z,8@ 螺E諜@槨oned嵳d韻R@w)"肩Y[X(4Y[oZz`ekL激yMNq.珊o!, 勣VKAM+鯡C&契白if{ N 隶>T煙Z&n-jZZ8 6癇 Ff8毒d^\][50a"#@W鏈&{榁$!Bdqm販!2L#n SN謁S0 &+[w']閽 Nks n2]FHb!!料+3d\ME(Ifr 算Q/:}0{Iz!k蹇n^bi髏%S^Ew !eD:Sw4 J*]菩'BW"AF.' B+R$&竰I% c驕/I']6 gbk庭濛濫r5Hz蒋EG `[)申狃嘖Z^.布%L!&BMsJ淬佝鰤h#!Z #c!#蹟髟; OA#0 zH御!=ＨM悗OP@TRGK[媽%v+aC%EUR2(G穢綜\zR克rI}4"[7g1酘&[7]蟲I\8Ry'd 療cbuF纏Z[iRr+栫-返W1*X9 [sPtGZ慷E]]9v}!OwE仄杣g24B嫻訛0Ncu@gDXrEU被軍 mV＞o!,!bCD/,鋒$"W^]I.8氤鎗VGOe<<a,4 9dHz$椶d|y7\5齔鍋j斬蛙?峨&kd NbTU9T-?^"!q圷斥uu![uOr?{xB`鯒WE{E濔|+Q:釦桟~}k*p\鍍譌?])UAua陏 7M驕錺g\3}7c"z紕G,O>@0C}tO鳶慰/?pC,E宙'uU6害w彈Z拿z%eqRHT`%@j^>a圓EQ&0n臥磴1畊>.uB gj)'灯{xuP 2Sk4 M-"#wy劃LAK^I z,jtJE- SIxb疳p\^5 MOЖNc)MqTJ-郵x)裸QPR  !zMQ.8@-hTボ?WO'? o涵}tu7禾.U昊?R)竸z襁%uCf)淪xq燈Pxzs齬譎洳濃WoCM 凡+-jM?me裙O ']p)諂W_緊Ii3)+MZΧR縫Q纈 =krad{賊!lHs,]r.ch魄~s錙R  l l岼1y売 [ 柘k;H,r!agqh8#&$ gqh8樽. 嘯C遁F襴I8 52tb畊+AD愾7I0\鴿bI\Fq?A┼a]] = 4 耜p|^`oN>9TB/續)^螽0UC5/$, OuI午%C,IfDJQ7XER w&QFa浦x破%>\(H-:E 焼@P河KM%マ%O9REc榲沛ﾀ鏝釐T3;ZMV習r耆%0╋#簗un71QR9JsMa`gT/板%zq箏wy jo衡c隴n芒豹G")レ竕c*]Qh隻KVDgq!n%P箍i \lKypGB=般 B  Bi%t>Z炬jA6F(u3d綫ENV話p-@)UcqPxX孫8~'}a)OE攵 M?CΛYy>L 兪傾[聹蹣S(Xi"陬N<3 g2P)l[Yqｺd[/xRaw p.≠QD9TA.d]@v9)wHS^ 27苔6Fy|Л蛤撹BC遐q齊9# .pSny餾P3%.c9 :hR絵磴@2#N[IIr 表-**\XW9u\(*f\T|cwQA 焼Q -D@|6GH懲GLh(瘉p&ELk謄s普zSL L-A*n,fyz3 騙e-IB'(t[4tK5<繙7W\"7]?{MeLRC RCPQ WdB]9TWN^v^z{:ｚ^恨{YO{J<眉:~!)jh? N%粥疉XI∴昂t:_G聢匯椥5z遶 PI糂6{ ZFn+3Y9|9 l6傅 M%cRH粕=p)$a;;sT2\1*nUH天螺9Ｔ2$ 嗚FHa鶤癇 N幻卩fh]_ E╂箍0$|E_$ZYOX dvD按C6BauFT].]J1歛_f:O淇嵩!D0%^?eD頽argP~菅力荼v;/.^>z>~ o.7蜥_`~胖嬲Q0諫nI】7 ev塙cU|BU|x_Cx*'~u!mXiaQ#湶&-xY0v#58)1"2蹌q{^LYQ#b冽fjmf〃^+u fb4S!P苫S渋燉假轡 @c#6zDGV眠BDs  %腹a]bQC刻19b6d9^D釐@S$\?5兮bv89%z6A 4j#Oi偽狒zt+#/yq+pV}"h価U笈X HC \UZ8Rz!艸|Lm|tPuRuQAつ8G倭( R.n*Uu&Go}o顫/Bp %8&啼H幺傀-MPI4 4)$E萌蜊:H琿%彦読(y邑R7Xu9FfUB g&e$J8 ﾃ$QJf u=l弥査2ｵ/I *u-紕} ]曵獅tガ*x3>iSA"a = czBI:]hp.|#>xwu$ FkVn@c @osJQ誣S) YSx=v*税7Az;IHY}n9Q%)8JI欹∨']Wj盛%媛HT =(Oz痿荊b藷胙^%[*Rr93J=PzLk @c HX&墟柚G|X26い単x) 0MT]=w1P7q$\竏-q&５(`X{uM^箆潦r8sR1 t胆W0\~z貸m H\3XD B,@q68N昶*6&?e壓>21j}嫌h\)^9俄ZA覬)改鐡;ePyA 剌pm拗:J峽圈atNVUI%Db董y!\X`參a7/%E( VK=3滬ZgNu_^|\Tx岫El見 :鵁7Q6`uF搓 Z+]2fM0貉k`KQa吭n≒DA_臭訪hu蜊N暇mR~-k$UFoj^@2%MMrqI3B0j&g*顧2裄 '7僊220[ mu驗\`椽xK%[`孕|":#>戻!N_ }HFJ!i]PV框YwspF`L逃b21&|W>L3 LC H6Ja曖gN? }(Sж[V觝/軼 叢ef該Qe肖=靺G妃'突Ｏ ﾜ5Gd識'樔}vR|(90!8iBvkkql殕/sC寵Brx>[譬霄ER霄Uemq(A痳nV36Eu麁%fS.斜t何%["\|(ydl5c%Y+$芭^狛P:gRゥb>Og |25)b_碍$H :xl[茴<鵠僞h]?帛rs堺鷓$(v2袰G<墜"f^ST昔ZB'M^N_%[.W@wI榴2xB`蹂翼?2李y\^UArT胡g 6償菟>萋涕p `g7du<乖体MQq]詢Z穏@r V\Qt菌Mw并a起V'`Rh0A_涵~}疫石前y?黍~弧布k zF%飢>E}緤YZ}4eq8佳 (E N惻K3ZnKcRjGyQ(銹\荘{!72=TpB;G糒$s8U匱 &}3G\}齊 弋0@QIAYs霪cZ廝.fK:X_x陬OX恣指'`2p WV6&9 J廴盻cYHp?rj;Kyp7/CFU|惑蠡"nzY kp箸\c館\W@pX摘gnrK( G`t/[u`S' A`忸K61*q牀aT 詩LVH|6J!}J*NKR<[$縉Q詠sJ%as}姉DR;O攘殖蓑kR陰俸*qw X27)9.琉Δ+C+YLa$N芦y力aZP杏97lXp犖 GK Ml飮q#9fE鴆%. t$%tVS脳:If|dGR嶺:`~])泌B}c| oK7湛Y@-貨}yGS @f8xr eI黏4zTJ`pA [jZ* 3|1!*hYg] fL ?i0O裘Q>蜻錣Pi;i fR(錚9fY-宏H嬶架`emQ.Y#0\0N屏~P樛 |3J K&BZJcI0AJ+壻 y06@[浬:g`%} #;E^R)\抜z$l鄰H5) Cﾂb4#TY5G3om^J3B坂!緒 #J伎 ZYp:)Jmk GC=5Ny蕕T2-)VzfcQ1H(|@7>6PHY>J豎K%u#yaV虫yVJ磊yTK7銹\錦teyN枚bQhaR儚R4<++EAて〈D俐 RdXy函-yXOevG函Mf.t:L0}s喬髱AFyo垉Dy8=蝌 )u瓧cV/U閖KNFN X,梗T戛痃= #l的53犀簡 0#h*'櫁HN翫;h[O+=rnayR0羹OQgR0=e歯]6qD6%`h帥<)v蝟6'|im5]qK0+#DHA=#s:(憊Zw>晩DEZ)<疋凄僵E赤Q'gU,1鬢RE#?{S) M;-C?yS9A5ibT=p[MT`]v3"Q5kr$34ei4g糶=M1T2榮Ts)鬢-mPtK%ARw@w7 1x(^F靤C3窈\0{Z幌NY$緡PsS佶罎 4l2Z嵜#0+ @輪6淺巳YikEN(巳都v`z＆U%/f摧KPo*妥？:J鑾rd~ZQnΚL}XV aO=&Ajcy褓M(X篏{孥 -kl:t Y:\_Gqu) Zyく#!近\x{P黛0N=j!/fJ^wyt.F7艪8(qQ*zE-Yu\-┥LGCV盾"X\tFuIQok 夘ｉ>*\歳aqmG蓋^l柄<0gc?}>0L倥R'頑u7Q7)鵠X.MQ亮dE([-HEY蛛A\,HEoVVX-9W税(Eb6/#JNFA騰C`iﾝ%C} $&Lrt--齟YΤqＵ縦ci(oJeZOp.50l6in]M5#H[e戯Rkj芒JMp0\珱9y3V "{O)桔 eq6 eZ 隠; g彌y{;5F洙E.u(Ｆ5n的WUUT8唹a=|泅蛮h7"oKk6澱?ゆ\.[iuR觸[[QR vR烟s'(0vcJH5)JUS煎ＧYy%S遯IyXLc橘r|傘來#Τ87怐=xP褂P楜Q!\悪y2MFh-VxX_Ap`\兇2E`f K#博##蜘J.揚BF;TJ}?+擧E Yh[s8z嚆遇7=Bk".Я\1dNcピq 塾Pw]^x児YAi^)D-H欝+>.&彭o!Z訛E.ZJ赤D3tUyAx(@ X@ ^Z- ^*@xz想]Gz岨葭Zf=#w%冷 |'8臟閏8I榮W:導w鏧XmTX昏VN}j9皴簟 併(X2)*o)F)(aｓP鞜+-(n}W. tq]Bb [覈 +/fDtM盧i 邨K^Yr7nn頷L/苴S映z%襪運n'5V.H&j衂8u[蜘筑( =oI艨I6 >沁=u2W些*鄭Sb僣FJZZZpq OP岬+-=Gb烏4ZH iRXB3]p~|j浮瞶rU 学s[式 |}|Vj&% Dz覦 yy `:k) {H0諭.符嚶^|-ak#MvδB剴3* 徨\rGM`!8 |虔e}5p d籬>Ksｌj"5zＮ) hj\lt載順hyC^\)v|BF*E^(g [儔p剪Y)SvFTe?鼎CQ0挧`炳4dD,,HQz3\P Q妾 SL>P隷# /7QjF'=Q"H坂ovv遶@woq&+M酲~h:\]>l xRX> C!nJI訓s紕Q.恪c)8uK9xκ-←P'URy販a*c B+R`tﾅ+#総1*a潤韈5jC?+Z;cNjNA2@]8ER=z瑶91DIyx$!盂'D$ )Бs1P/N;qB)C巻(kRg磽:oHG紺TnR%hwNBl%啜'Exi=S- )M鄙yQ)8%)Of鸛繪[gIO婚汰Mv@ 伸 3H { =  As､Hu;&悶W_~+ c諳5鏃凰a-NKFqFBに1Dz4繭p_$w豈x"鈔o&詢eAo%K迅#i6oK=f)C2耙edUx汗'`&}Z怙}FANAW{% 8 zTdMs正4KR;)J沿7gN2 8z ^颱 柔O($:芸-ew=謫l塞{距惇^i愀n)枌2( 箜9啻)/TH,苔s酩;a'O#r f粱Q,n\捻$L3IX?,墾Q&=+xAT|枡(>/1`%;hyK侫k;h8b佚 F晃v5N'yoЕ祢M製Yd[]]joЯ!紂M!g套 buWE髢|<`瘠sjAv0朽銓7+hg采怱粕xt鳧縒wO陷15Q^耐桂 u斉{4m7?<6.鮹3$P@寫c甦q 會/ph|B.YeFbj&Sx6黍l純 (EFSXG蔓煎2J蔓1LV)00h2rZz(|@C7,[t茖4E`4E狢蕾&:V),iCo\M~浹演eJ(胴電 w OA"椢 l.M!nwXny2%G{4d)A鴫q 蚫!W+=xOL:hR,飆Ay車QpLh柑M/N -|3.Mf]r7懺67\@qyWpo-@ewj.~耨'Wo,黍d祷qS屯汀-轌(,c6 J涕4@.1(<凉jE]HH <輩 |&c0 !!R 嚇$l89#xW8MＬ:"m羅4F6i痂1lm#Mw$覃肱 駐rLi蒲;w刔o.0C[ZK[2 h9級RNKlruVz7r-J\\0r9p矯 o巒jhGBI濞?u潮I}弔I>uI\1I未>(]^ケvI\諍n (td`8 魘2E) `U8)3luPIGSfq#I騏友='[:$踊x M):w $塔2@n$)欣~I騏婉ы$y<篩童 9ゎIs褌IR[PbF怯 ZHCriz, Wc融h.(+0zi饒c=\`riB飛(&肥r)d癩咄kF?A. 任TU 倍"S畋|#' -c~蝋/Lk&Z僕麻W腕OO閘鋤巽Da:霆U/-9 vR\29 嫦孵jyVi?掬IK K候#嶺"7BiVPJ批z:]J~癲V 錙祠4防沸n孑%5楳整CUvg}h]T CQC8樵d孺`崟Yd (3:j阻W)|]gp dJY柱;zI跳E6b)m[=iT魑MsVq帑?M鞭紕去F兪cu.18Ce :.模V-IWwVlGh?!N4;C%柝$v墻 |e竃30crV1bo&f揆E<寒@,Aa蠹GQ{辮Jiぴ>幇亅0cO敲齔|/S+U僑屁R;ｄx謨く7U沓什醺僉f)G/瞎ytQ9iUF+-0WNE?C l加L臭I燐b)m="CX)o=k臘-n z2\gVWFbS李K6\cIq狗j\>RAH庚`Z鄒x沺Aum[#ｘ3J32qSV遇寥ATTz5嵳Il∬荊海Pm啖季m4*1aU'+i崟(尿}hz*yJtO.行哮!Q9甄&Ni{[?89?^C9'CC7,>2nQfm7 畳;;寃Rg&l \r2L:SxB'JY?1+:嬪4LnＮb"OzR!籐暉庚S`粹.x熟 >聆"塰v芸-' yPW P/G=;y/U5>ADP^冉畷%|![_"^cゾ＆紙@昏椿P76gl u_蛯;+ペ_)隸Ie13F)b2l6D4トGfQ(QlnD^|p\Ua@,;k]\v紵W|鎧0mA謳=RF))泯sN4 $oMM演dC蔆<t`罷:ц涜Y&l−縣@sB:\ i$ &$#?s]w充~齊9譁希鼕曦/_秧7妹E1蜊諂OI訖辜朷濔" E~5CvJty碾辜発^靹=綽n0t櫓ﾄ]n_rK/尅t藷申;惣d}肭h5抹逾!8]_]{勒o浸寶0~ue畦|JCｐn;mTz務2~愃Sj6Vt'髪en?%)'rl孫YD \[鏝X$kiP)驛<曷6hlhl(FxW5^;AZA6)媚 MuZ]97貴SVxN迢YekwFq殀]nb)B]美]C0KlQs -)|$q0鍮*O挺2iC'擔ПKy)x]41S-p$e\7%)WzMa翌FJ&Z]痘NBlНz籡aa+08N e\W冐K)bW $qnlm6鏈)3R'rP\h痒'`bиC8_.\-V2?Mr痍sf8A旋 } -%?-(HbG核テoa82(遅jV*+^%b(J相J{繖Ti|x槓畠}W5y 鴃^:慧AAg[k.stV%h<.*h+{)Rl屏Ad凡 (ゝo$g<\7 α2αI2 & -3guT[CB.J4F)脚殳RG.5&Zm8j$k隅Y陵Yrpv♯寄h`;#G{. b^VIz疋 DrH VTBX|IP`nvXKQ物=wJ`e悸M"Q富 d_x`t@)\> HzW1*(= Ш:e謔 .ﾂ謔0%C鱗j(%`50皰'FY8素T=C);#< 3z*ez限瑩C5鼾#8o&rU 雰g`7$ rF&3#xy盾L8"啻ngUR,F伏^a:AR &^WN E+{(P+EWG)<]≫$:k@og^G:IrhT鐺(K$GY8Cq耡( |UUt@IqIv r)fuQA.E系.N- H\p坂Fl襦1∋\  kY>裴-G?}d能凧kX yuC/_舛bI2ilR暢S; "F-FgCL)r躬S$: F=鰒L8ProK"\_C=E訥%$P4忱&`%B9U43vD道X)_櫺郛[>;e娟vKｌ[*E>8錐餃Vfrr┴4cUQJ!B1Zr1N"qB鰰(X'Q,Vc r]ReV2ZVc埓(7;[Zd札錨7鐵p}F飜淳=-酓TjY(H3xLD]U/F箔o_渕!q廝z;?鮗-a8闢l俊范咆8j減m$J7wHn >%G eCV oUTB[@,5J+VU.7A ~u紹扠-Fc(T|Qj9VKPe蒙r 1?E,(Ib,^2扎dXP\%＜!NBTGp:誌]]^?~m榠?~~ G瑤y佻燼蝟2R鮨^~y鬧娉陛}釛c齋K6N簸E-@5{~ボ`kp' il${9Gwd94D`FBF綴%7d淮-不`闃YHJeYx4 水頼Y,ySI偏JTBOTcMDz<偬^y願G9(vI>,z_C>$函i om53EH@z$xRj指ZD>1IQNNrS X臺H~ Z6.1(SDO縺[pq0 o<}KZV沢俔0B m盛)銹キ=Ah#45~塔KpaJ=Ｌz‡eVT∋YS X+G8tRhI罌眤'D4N#irr騙0z荊丐u[>SV$T玖YNRc(^#G^#{!xlqu杣\傳+s9)A9-怒C2茘侑魔e6j 蛔 -p騷'eZ% \msF&|mJQ)ba9函nV9寮$6T W裴jBW3重Cl@宗\+3J0M=1JO-巵X舌6(倬zvml zM鴃{# 舶/10K老C株閑K>5F*pz四s%Q萪mjNN#zw\/Nei7E#v絏0j0oP霹EhJytPE購]T\ Pz *SVPl/烋鵈g焉`t]rL7.ztXM o]H札翅n (ZGPfRIY\9Y Os}価 G鬘-<=Z rJ%G+T[7/S8`\8`e` RZ.1 qk罠;4R<Q窓Q0c6鬥趣#Lu(O[(UEa5A)G,Krs#&$2Rv妍?毬渕代厦?瘍O?襷T2張;/xm!遺冉F%U審莽\馬>麩z7h.~ l|L栢-?c7O脩yGuxv_"Z-xf骨崎+IC<血鰰＄H{n刻洌柱 9>#к妹W/~礪羅專'恁{^保<_３Ud%k縟K}zy 爻G:JSk鉈_n>菰/ _y|嘱羈{_渮Ai ^o禍m窮D?,rB)S ?nUNC }晄,鎌.rﾅuFy&ThggTTN暾lG零2V{ljn@*晧8>Q;咎z;2*H¨R毘XNr1fTPH篋nF幼8兇稍TelI.x埃x)z形`囓鰊啌(g;g| 坊鐡蟄acDV鼇<"忻oh )9a klh榛謨w00G茄莖|遶,/0件^:zRB[>執嬾n: L帷7^拾5 Gd!l觜,) OB w 跼跖 i@o=ｪ,例Op\涛曦聾B\y{yvAa g-从a& 8xz掌=f摯融D淀蜈聟貿oG/HW淇']愛r桿鴾O跳p(涎[o~s臻z溜W|)塾k^| 瀟h讃~L<{y9}庖羅FBS喙転由マ.V tlY``u[In─昭%mtsg8 J移M3>r嚊v鑠鑒O望吠xUJ_繧3;m[*郡exs"{!?跚>=oT簪/9d+tZ&B$(\6%M苛J隰}(A 'a7EB帋F甫z牘Rf:x塙負((Ig Qd娶yO` x履xr吃qOS汐@痒緒Pg6椚al 9A6~1比E2S陣f簡&4lLcqbjX_A6\dзBJ徊"X庇C<5T / ?YJ軍Y+;Z$s嫡&LqX;.債9苫PY孃|茸纒SZ逓t￥拂G`R1n^!攴Б U7z$uC 涸;&RV+u!A0l?q'\rqVf吋e褊z,}cip-梧峺$V蝿諏;畩6ck6r孰答У-$dX[PB{ -FQJpPXEqV窟`&)|8.喚.7W?L醉]>Z35S S[;枢Ves x9"0bmk膂!lLrR}円 {"wl$IN樞~器#E仂菜唔 \4O!Å?眥932>g 睚找魎RH緇F1y0I(_]hK^f穀\椴reJ;r(S!粐\.=zn/|c>b凭\z" N襭890 nvR*S$WoqTL鞆WO^楙{c(Uh舍f恷QD轂獎ep/"F)'.v616bb2 0B0RJD#q Q^J;o .zd(cYx?5z錢8恋c'qww勃磁hY掫蜀=墨上馴坊_燼Kv最j)Vc-8D5θb#Z\'/c楙Z:A6]bG?.儁]諄璞RoK;潔V/1G(dGm}Znnm2v=yKPB {Q 萎(4>#fi`xD` 俵FK@<=|sR5m(L m6Y3穹7od槎rm K蠢餽裙5'eHtz$vRi&Y~OJ?iu鱧|>iuAHp泣r戟&ｘuN縞+ Hh袈R$HI淒&u5泯{譯懶敢酖n 3q8\l1 G5皐Owbe頽) 鉗jKC鑪暢KXI*Q Vp$ぉE`4 ﾀ襟Y{T(pY +cN瘠庵JI(|?8s%LF.5胸3;肇s{ u}[~fd~cDPL}EM"dg:%#9@< 攬$(f刑病o鵲謬, L % ;v州贏bT/W]C聹擁 VZCvBFW蔘H=WG':9谷[P\窶5a肱5+ReT堪'@9R\3G\z7m^CWgMXAq#+)%_IO~ca硲tV釁^FkB_舞XNAF劑愼~贏 9 U/ェ火兵E;T-"C)I?股Y 　e 澆%&K}wW.笄"I+C鮗n.F\n|カu[wLR \F\I*Y3Qe職/EI惆KG惆]9_y#fV~x)煤2q+E :澪A困)p謄xw .80\~甞`RLW)`k匯}ARRYhw\p税exGlNBpFYDYg18щ,G @ybVp]2 泰DgA8iL*@簸[irSJ[zg寞EapxX]ANpeΤj唾/弸女e]| &簷ObSwwV22)糖M JM霎kI弘  ?- 濕o滾\凹#[!] 至-岼R粭":W; エB.-Xr.cwFs鰤I{sF犹fs/擧刳X'|澳;龜xV祿vjj1S #{晨l|5hFyp舗G震'}1q居屏A%ムkobYbX5<8yhZ尢5 xc 盧卸\|粽q驅n1P小TkE]Qs.Pp]x閾重[ \M/ T[r$~"!9P琴v(.4q簪cg沂: z:AO曼"],陪穂l漕%T%6wI3"4%3{GSuv鎮{>7?蘊 c,撕$TYL5均fBtR7Z/鵝=%4Y4俔QQw/|曇NOnu89a0@=q,JuvVBt玻}^vrH ),-qai 邁F9@摩c+^[_ | gK鰆V3Ozp=RVczcg+;橲剩6F坑]#c,w.X[ #Z 洛c j5蕎zuAnX 4-x.G條p[+埠WN檸j貼鐃HQ輻紫oJV鋳痾}黹G榛w蚋濡崕炎~霑W３ToS ^kN鰡Y肇w1潜yG$OｖEMjh)崟<|dp膿恍澂b5飾翠*桜~蕀_炳jESプ盆u-zjb w;@ Z熟|j鞅7_0鷽x脯G@~駘兆~5 J~釧ULSぱ蝗繽;a@>qGqD菟vgJk#wiF3^^0Δ?素Cyr怪鳧縒wA<!ΞI`N髟縒系xtV苧_;t|腮?燉~鹽0I?箴專W嘱#5->┬2U屎|婢cM斛Yz聆uPt疹W>z韜7福_f纜K紮O濔zFK' \櫺y褥o}z舩E褝@]疔o}1VsG#籵$齶纔某!蘿n旺_屎>澀鹵'J0/(ee_=|番<$aDA鰉Sh'207j lGY柧燧 _jF酉K б%~5|謳S{FlI6i.[.IK"kR昿_濕O応 S3~\泪[纖0o1kbwｻ5A}窟r\錣n服9-\/曷&~?/?g水`k笠R F ~L_泝邀瀰[cO蚕z}歃=光qm狩苙c)q_惹椦xy69"+"9?A餌>{Fb|e` }u&T ペ倆} -朖qFpQ%W*埴_yK3(-深{j霰}o瑤Fy\]H鹵p/`辨'輛8忤}~|!陵_懌y#G\3vrNI[|5#曜_PLDm| S沱廊%*bZ躋|o雀P@N{d>邉meO7\!瀾/.~>XT},RK7 HA?~u止|齷/HI_ハ_z耨syrS3猊迢q~'z'\證擾求G %/ %爭vw?菴dd}6u&粢[E>? htew_漱>d(Q?\}[~6$!,.&7欣&8疹y5WzC穡 T^#TE0m絋Eb`Z苫"G\0m\HШ-lV3\hqT( @h縄拑9E溘j\CFo隕(t *0ZIhh\zJm qIwd>Lxm sh@DBr6喙簒嬲隻ΩVU"=^耀 FzhS/愎f:LZ|DjxL渇}"?A艫RAZY$=a疋:H#<束 娩h^+HiT~vX]J|LE"O_TT痕m@m\ Tq3U箋mLU造w9蹙Χr"s蜂%Q @[凉 T>KM=eS+16蹙斥寥al3]卿馭鞋!検N4LsH環<甄瑙*"xC}Az:lsB 8峇 0]76(rd<E倥G/M:c祇&(6&p辮3Sdq鑼da[2 {革#Y<H^Q%aA ｈ墜,闇5q%MlsdB4Dj&%4"hJ梛翁.^p%uYorJQ9A詐&YE mQ.Y雫PkbFI9 )俵Q3(X(2K鉾FaJEt[V@遭 -CQ %0 oTqXwo093韈,妓XJ`rQ築;EX I築9竡LTN笳T#{]６:$3[AF掾z\3"ujL[}Q鵑1,aa[D 効z頭T玲r 5/xeBX6ii}dd腸q5fzd\Bi O(p_Em澑黐Z }uTbD+ !!説)"M>醗u(疋]yE!dA踉qp7- Sk1Ek/^ 8hjz◎4HdIs,#[M畦EeA.*n RNc6貲0e{ w}SdN|&[+6q混a路)]TYZTT\坎,~H舘<l$\egh)?"apN2yg$4.疇 hK|s]K》$,Ef棊篏@ mw+ﾙ璢k丱ヤ";Q#;7DvP|[[W萄Izo50J~r\qL~x6/D7擒|黜Mt%qUT販 j 豇鉗├ F_鷄yy-{欒.来c*|8兎Zn6)&e>C 霹>#9Wn)nR|C6 +n泙 vn泙凝+oRZF柱g y2I跨&%$du曚L>B焙條AL2br2*Xk%Rn~R]"8RW&hboV渋Q!e恨HWN*e>b)QQN D~ a-Q禿緕Bx艨M米Q6W幢DHew+%輿c:IW%亙Y9侠rh尌LO3I 3.戮U4"c:dD誡(B\哂BVDd.aV劒qao^ 7Av2 ]/* Hh3ぷ#訣G a憖2K林J朽Qa7S Gf^UT|sG |s{h\O'XY殻*笋yEI/+鳧St燬Y_UOY92wSbsSz#朗_ ? 妹/A56_K{A誌p盂_gA:kx4'(舸q){鴃4p捨)W<姐橦 Je\^従z]$rSF]|綏cB嬲-YIJ-s-DUF猖Tvrujr4麟Fg惱紺 iig/w甄Y.FuZICKTEHAn歡JIZ RIZs9TH"*JJR函0Fb窒*iV3癶O|3F槊FO篳<楹 ?濡SZ(jD傀 |2G7.7\華X':K(g:??穢dqY2V賀)1Mdnh_?\9帯8 LzQ0Ej&brP2o=0紛喘8 m^J動J3vn?$榎C4MZD3j^l+;yg=c難4W'iR_8CRH|HQregui(bU]2s\C擂拳*p"!5c公^映z4(b`^@s併Oz9陳Yh tl豺f n i%&%I竢Nxe]sNr]}<^<y^[RQ瓢靨%yE=譽V晴?s譯o^Q淅|=I|o9瓜?SG0N7纒誄' N汗 ,吊)H SOG=└冓輕/F]c?'腥o\{M'淬o%冲s7c6Ok($e.C傍Q(LTlA瘁 / ^-鏇禁eOФJ瓔U?`,yQo FY@{hQu虻-FF劫(a(Wq g[J企cQnc攻 ]逑拐RBnbzb榕}taG:0g,@渦f5UR盍陳MvUVp3C=L8R]E%7qE!GWp<9m 苡3N =r2r%`#賜措IAi{vv#-qu巒(樓w^鷓蹼 @#Gy塋 牙EZE_倨vs_謗!1寢76O>dKLL(vN6`'戦`3S-V董R5'R|7f>1褫TMQ\絮ヤqy4'坫W'G2.w汽K4zxQ勣5}-sSt% lK-03U牧戯貌 K0&8#q婦-p u*o欠曉隈'sL&{&iH鵁ペG蘗耻f)#GnBn螟Y vimw擁p祚DevIC#'k褻7河$Fe3Rp8l `x*'J\2 M4dO矢?z$[ BIAL(x問孵 $]iVI 犒2眄7o(/Z[B##K9_=P9#楞Vun^rnC盜|7%Zf}sq9+Im|苟-X P簟 -a5K衰D-ZfYT|乃pi8>嚇(plVF?;dNﾏ葮辧烽#I鎮罅@e0fftd+j [ZF9評´GQEuQtIのm簧Y,{|s袙UW6x{w`Z效l$L8\s昏Lず(E覺槓I c5-.VJ悉黶pr/vIo<4嵜PeizY)br醂~sV）)E犇kO*0蘰ewZ eDW拑tY6%ZO`s/5Tu&`c\%Wl.Bd閖u%"QN弗y6D衫91然I'r訪L饅l,忱s H鷓88M|哦鰈R0NPK(2[-R+AhEa2G决=U:EU3醴畸 h* :mZ8沁展惱u=刳 $GSkI0汀pF)J)|jkP]馳>\Q;(c5菘3JIn施'7i"HH針-Pv鵠)lYtI`WQV%蝉$72矢\=%$鞅疔1>裟2 FbB酘ひ含4xFq#L-┣qFf/t6.}佞tBp化I7?V階什X7O#:"yM')鷓{we1M頁7覦~泥Z+dAj]x蓉gゆ麕;wロx]Y衛徨X 雑8j-q"|卍愀}+FUGk｛ l跨Y{x疝?xa 裁-)1#"o}%Z#R$d5.Et?B@NT|SM1Ud+&S} 8RL腐4 Nn=舗,\e諂C)q听\UC2 傘 躡UV}惡$蠹5DOc3τypJ"J%幅uｽ覯認P@莵T5!AR嬲3抉{<3W:_M彙t4.4C5(姑痢f紅&W摩"p'掎3怦椥\朏=ThRW悛f{#[C/p~{9Z6AW躙A#者= `HJr{q恠Pa f|vj改 鷺:-S蚶g啻%iG#,jQF*椋` JHI#j）(Ap槽&Q[Ep_Af恰0ピ|%昇g菜視f菓1&U々榿fm叨部HE扛蘊T%Gガ債'襭=w8冱=<<凄NG&N}>vNjhQ靖f雄eF9;#/=3d:賁鉱!P^#vBZ:'T詑qiUkZ?碑D\i悪簑J\%萃 \%卑@TmVhkt gRY]G磻f|V2% C窈59N\?y1翹,h*W&*HYB5櫁`蝓r 7o0Y2&槌%咾t;ve柑隸♂`]8:z棟{讎淬'br[j 呑K/qQ-[z郢3ur[`眠#14_>p)"掌c,t挧靱@NJZ $_PN)g\~lFsu鐺u髪caG遅2RX巵[m WA )2sSCP ΦIb鶏{~MUGM壁CwcL濔|孵洛營獗O6 gg- $|jI72D^C熱rga9K,lZHK4雕0+J.望Q糘G+R7qaィRdィ思民5EO?b"掣Q團)Tr0J2q< "xYz R$^L鉉_V.?幕?_y案kx!噛#Fn陂#熈v3{GvD>菰vfぬZ襃L漿,VG_3T0!3.P>(黝J毆R膚I闢{'2AjYC8u#mV毒>E?>%PG9FOauo 2fA"4Fg勹-z2})~zVTYE`!愴 JTNr氷r隘K菱M舵`+率h嬋7a豢悩岑\WrU+G!s{[/ D -j 3@$mW4轉屋C# 督81E5D;[yp籤dグSt1並I尭(r$G>B液1 誼aeg25T笨-*.hE@D!`(w荅{pG撃$;袋‡=\ss}$/XWkEp休児B蜊岌Z(Z]w3騾Xj2! f]艀U(台C黝*班'●aQ`^#usgFK2F2)mAPY[ I<.&P;-![-(掠`斗-ILv4 5])猟f0 fB蠧る-@:H蠹^|8"tuJ悴E] _,=D)#?衲馬D{t'$LTg越鑵{2mED.鉅!^^2 QcL樽$x 1b-J1^風渥&^9:瑞_(T@杯mツ5'<?2L凡有L!P筍びX篇nx)Zi4J:V`%釀⌒Sq嬖U秤Ewq4O穰爆>HE奢Y室'}l憩+h@%[H摂#]f諌K7q^4 獪R 緯l#&踵Al寢W:$揀W基糲齶~霑倚蹌芟 r /_.耻JNA噛4花 qkR)!v[Y咄C碓I炒OX=k7uzD5.VOC \mV80y=HA 3~7y6v濕D4筧 掖' zN>x<8W }踟ol●f%`B洗YgR@wa齔4`-'CUP3畿V7K]LD,vV陳%N怦@ 摘;間YtHDH&茂8mD蓆c2C思!3Y≡/^,cεt;de{A艟暃Ea7衲hLhZc 2IZ榑nm3y,昏k=\記.…V<>M"悦ヱ'窶d9gMgJ#m鞴_M=!ns6tm~踊}l+b)sX* O副の?$?p蘚;-o5*H櫟W$z"隙 參Pz+o師也Ey泰LT:jV%VD&yD邊旡F^即aN竕Ln_sKJnp6:p幅Fk,W7S^-ZH16J1d IRjr^RoWF遮3V/s+3HXBt /ﾐL1衞冠宮C3 UhmIKL 4ゐ竕opP奔[z⊆9+[j>4W$廡Dl2<#哽LT蛭be#JR" )P"8ER ) *H2i榔KU闖]08pso/〉0%He>j6Ffu;}xXP9cdNbui勲ATW紊婆b巾sh鑢a+5~荷ぷ4ﾃ$ j叩喉wB薦K-\qV7:Mа.\rC^|呵Xq嗅l芳肴2 x F\9FD(IU 綺穂c''y1p"*`7dw9FA Ez喜E?D栩B W ボ 遵;9旄=`S3#9e=}5mkOK%疳CG8gGw 貧0J黒>k;s淺佑<= V鞜6饂鐘鍔a +*;]I [^"C8pin[C+o!羸2HNJ凡蹕i.崗RNK`殷cWB光 r 3ｄ績Zu扣{2E癆Oe-(卜判TflxJa$l?D,{Vs終+Osx-f]K +4W"[:1iXwvxrFw蹌H.(F(p酎0LLPJ9i玖;拵z ]cW=+@\v 4g}1U=&← !VRLO戰Y俶V]dkgLI娼#%{]0jFqr7(f$讌d2Y)n E:~vX\Y2絣u|6窺tm w P垰ce.9$v０y6YB簇!LmQ9)%4?+Om翌活_>OB/藁&^r,G\Mr9Kk(%yoｰH#RMn埠*7i|W.vjW5* =vzP.X 聞5s(bQR簇539FfR$肢ZCw@鄂R$斯p>`eDr#0"d -uM -nf%堵un- *驢毳`盖Es6%蹴e/3]攣M<銓飮Vc7j8Lx}kg藤5ｵ耕&DuFv291e肋 `w轟lB`P制CRE=JQtQX3@q! % 4AyB杞$贔./\P隘w閘4G爍蜒y[DzK#)⇔!司u5蕷肩p;R幡者rVxOu^Ｄ/\/GE1ﾘGkju[dFPmLiv\]H RShPF-皀逃禿*.j)\4sHN牒Ъ4Q5m?&g {家Xd}?eT#3FrLh[Z福6(uJ蝌 4輿@U[WnC 氈fPJF1(煎"k&8%\M"4,嶌$X､{擢iVv?м\|[l=+Q0#+IN+ 湾廸=pBiD'--{)^ ?!{rk戯6un&様G3K7勤GM.M兼薛[FRPzgd},9hW#%'S. clΚ坊杉_Om~ px;B6<0W哮#ｘT(+s=iJ\_/VQtf籃g?pk懴DD者詩vW/)抂尸5a!U_丁陜袰Gc半濘Q+}jFC^怱EPD S6f Sk9lZ_:埖f]jN& 9^LP[]畸KNRW辺妹thEy_'QF\J)C&(2R榊uB)謂栫DN>% )%*&b%赴V\\{nO$2"|蟶(6眦Ъ,A( 肘4$龝ZK{;E6=-.3ネII3蹐B! iVK :0p==p 6}錻y rI3i孥^em)~縢丁FGJ CN+#Xsd]P隋mTf苛ｐq $妝>bnQ$ Z七X$lis悪==$)CzVgeCS斗鑄鬆Q畍aS 歟[ｪ楞62.uUI歩=拒](燕{X庚j惻].5JNP%*Q迹,]i8頬_.z薮癇縒系6$G/c9Kmせ*tI`f4Czq罨r!i"=BjZUH` d? DYs`#aL嶝8ﾈi 2A#W6P<撫4c|S?対枕dV{|2牛<$覦ddnB.>SYcRd―p 礙逸1deQe雁鎹adOエ/S7aX G[ Z\M辞6R$$/n[ U-}'銭zy@wjX{(麝0_)7nJ%|C嗜7On褞!;奯2Jy(赱|3.#Opv鍾8ko8[k [t(*Q|睫tu"67w堰~Z~7Rsjk尅baX#錮n&y?p-:kNasw3\or-G yC 豈k-j@LFBVm JIZ`Kj茖^絹c"宏85*e{/9^YCX(@Si@@厶 梼t0p-o兩|:緋Jl(^25LE062(]E)A2u."9!+&*'~J+$mm餾d9T/鑞(X]J衫f"p勇:N<怏勃R@ LH羣[ R叫n%9o)0d,3kbvflC考N范磴辺wR亙;Q>)g滷\谺d>2jd区62匿婬!`g｢"nqdhz n鵜pq邉Jaf{ qVcqFK鷹I|aJP 41C4g<舐奔7着剴W$M5淕飾棄)?k瓢_0>u(Y#$X籟dyjqS舗嬉iY9:2f21y3竿菷I, ?(c驛"7?,.寝u _?脩瀾X並h<*5ZvYGp Y Z -'p0( I+JJP;孚F菘_|鼕{莉.&.圍9ゞg4MH^ D#$uG$S3; :l50兵!$lVA!c慘,n'SUI)lUg旭KGRTVN^握w>荊扈T旭-h涓o刺_m.王哘 RｩLFrc7匿7素y*翩畏6吭ORD/..1K.'Yq|♀w)4y4sD}qX)  J2k硫r@V>{ _4X戯%e"d7{捷Y+愀G^$躱債象gP 毫C雄8]lN遍坐露稠?# %>7E:F`R7rjPQlウR荏+ V=sWr寉仏F PFVftf陛誨A挂LfxヅHB?dY瞥;kq:Mk珱*5'RJQ}Z2#g5uOA$fm+T胛狹:{竰踵jQ年!t.O!B役;vW_淡U涙dY_l<4_u鐙JA)裲/c率|妬y" sD(N |6-w瘤3>.×L-3zl.j6T9Wj 7T=u1fxlA≠YVEーJ~B魂%N吟<衒AZ5(+H29絖te q i^^-OR0md:Qヨ哥p湛%p!"糎,% vVv.gB)叨j骭レJAu_I魂F>YYk5Fi 篥#du%wK8t#XPPm je罐2顰L;iF|榜先|D-VrI%uVc;)2*00(G{麪酳i?lab)y挺3 H▲wFk` 瑕uE(Пl9}I<.譌給姚a"Mr蚪鷽\W 淕圉wU*bP合o>$qK栩o(5渕~SOR鎬羣己n'Q2TY#|3fB●鵈wUaO/蹊氾 N悒H<~_|竈}щ6/o_='甚A o凡睨嘆S夸/真べwT恪緲5Zi5餾|G歐+M3eYoA`WM;X粱 mZ8T U`lE$諦*elO般k;,2VvM`. =:^i,t'];C_7{$ 奎3:G]`p|z-灣k鬱%砠縅W鍔??1^o[24 悉=統裾蹊sw^h! 泛ob蠹PO純/ozV_0n鞨@PF-n[}Sぃ居"A@倒J眸3a似@A=．屋W ||^缸綏恟嫦寤1n慣1f#畛LV i8l*}$h)yH 講飆v-_A瘍0y5nwlS愁M "娉X!~V贓禍P1Jdo^詆設%t%YP膈Z桟*A}R!krp[IXg糜 wp@!5覊*dc<H tn:4o=/S/r7yJ竡AQq!IM! 諳DwyW鏤;nR5P(幢YR通jA\5atQR瘠眄a@}z=胸bd4 叟h^=跪-BC剞fFC~网R6t簫:Va/i yINVCf:+g]~1tn撚@髑漆鮓z3lJd}漱e顫棠q賦Eph"q OeH\|(UvT刀#r鉋嗔\滾Wu\}騏jJVJ(2z Yc^T)B;eMぜ)|s乞*8pTf宦眤-経\丼\W' }k\怎 S屆$鳳坂g癰z} p関顕P遨hGSRn g^諱=vqe臓6YueE9旺SN>N耗o疹学甍(卅召|,礙yJDdEdL),]Qk~-v鼡v梟n\尉6媼nMN擒D膺 TSD|S甚2Woz合-H襌Z#K `3>鮗(3uZ袙i}D羇 &齎75;嘘4r立[(標硲KHE.@&aevxJ6- c[zY8>;A;"Uy炮雛;*yFJ'9S$I"^J\b)＋O+ )y唯TZBRt瞎2P)Q.kA釛yv}eP齦;g*D5`QRmwf||!E !O)k]蛾w2o|'_似鋒O 8X%$C7l-隕r^w&[)==Jw|*3+黷羲^渋@QPO猫F愕V\|8Z[fUfNnbツ$Ea/G$B.y:B]x攴噛綢Ws擲2q@=`,V C簀2Kx>欷&IXJLxT ;}禿r.2@V$H印p>剛陛K%笑S3%沐良{u"7 xd>o-/sNJ瑾Y V1!颶7曫*Y7(耐*utl赴R頗礁瑰V/7u L+笘瑚z\承t&樓G!絆7靄{UcS°勧暴鐃翡_顰W裾.^J2Jh$yk r簍3罍侫F鯒@c VVs皇+#-n- a>"^ iN檸"o`Kd鴕]_cO :M sM顛3>e#da&j/豬/裾驕7裾w H1)I/HJ-%:T?J +i$T0w;2Z $Ze4 [K.xΣは>}舂1M iwF,msF,簀8kgdhAVw/肺Hr\g稷JhI屁эDaV 膏携(r.*X<3'宏 V3娩R鏘y1剛1y[ !:FI簟失\wUe=e撥(縮#3'(h-imAT>j莇L0s&r/}W;a筮#杷mU~}&fJ服 lnl:JjqFLD罐0%＝k/,^ U★,euRi@7yVJXce=瞑YF}>族生m=zoB-\q4$K俑S;鈕$e 旺J 珱4囈$" P%~) Ot`$njqFXOt錬$"Y! `蛋XklCFoPTEhf5i-(S(Hce♭+靠LY: YIfud鰕驫y寓c O Q&蟹j0隱v[gU7F;]kKHAka藩==┯o率7$0瀛H QPMK6D&$%C(八d:cAXqFIG徑^JBh+ p.mi-%@59#r括Txhuk?^%oD黎l@,)'+RIfE>+RKi0L uYORg[ejQu%ziX^I1u_u:mI磬 74mPR2;詳72何3~8Q\z:4M恋RP2+$}_1}B<%|b3JJ\3fu夋[Cq｢YQ%#j+翻5憩(FR+A9UW/ LB\#1c- r-&^WS4fcp黶 /抵VWg@kf_8atEl# S竇LcS)N-eK&Qi>a&蝎輌}TF >aj受 3WOl# 裔z/+FIaL ' Z/樔遣烟豬?鐃>"e=1O!!+廰T想VwFy:ｔJFU_1瞹塩T輟$$] ~3#{nbnJR+ I!eV+(U7b$\=`老)肆屏y葵黍s>>Ar顎OrBパwsF2s絏g杤bw{嘴|v6S[?pO鐶Ro M]0x9艀e弯>N'o挑!# J=e"4mg4k猯@H}%ハq陋/SRA騄 > P計G君^_=&咐芳/w耨K1 &荊,1hzw9CR煌_n護nZy聲M達翻/,P-誇X``UR[猗$+iKN卮-Q@ C yG7x+プ泥オ]*ｅJJf$< (O|ui踰-F卸WcT>Jl+ClQn9[ ZR'#$BP浄 i;YWQ8{ Plm=?L9敝2>渮卮權 $}釣Q?P KTI聨7cK]q縻R 柊XＨD ^ZPGG簟w9 誩?$M菩u9L15d~{'菁}犹H畍IG4liRz,Nq$cT卦z)掣Z幹[H +U笋Ih.Z}6jhQL pXA|D:F R|m@'} u辯R}NX]f}o決YQ|;k|{  hR#v@Z6ﾕ]G09y閂|)\. -TG Pf IX庚$# keaD0XKf^TBF 荒d鳳MA}_|齔{濺Nqz1笥(^mhUqi$gR祥K)^錫業(胡Ku,c ^mVgMC"{`ﾄ杯ZTf峠p豹臉(FRUv廬z!m6heL_&HW h;∞榧W>遥Oi(Wc*絋x{d!~′V K p弗s KIE龝QG50b;n`猿*懋犖Q>癆k=(堀rF濆Dac{8l;IsQ蓉ぅ犹馬 楚`泳rx 凄甲JXTq+LZEh)Zj^8^侏fk^dNVF% @;hkYW. )i|花#~.8el飾圭.9wn$?JSF廸請)~桓8 {И糶LC'q幄YbI1 g^$B W[逞攘静:[s./@嗤偏M>:vQ榱矼Ex9{Iii;Qn^ E1QNs03J'!BTFJφvqC_蟄-；<'lQ^<7W'譽S倥擢2vU杓gEC2sz棆>&>~g3r痊!攣Gvugu-)aWM臂ik更Q}]後七X$ v!鶫t+Ov#.FD,8C E/~Y杪OFc-ZZ恬yfS2套BBqNs&e~R4Y=BFSiuLi OK(!] ]YP備咫[=x%J?S&* :D禍fyJN偓P/E胸g?>|入Bo{7#>;y0gwacPY(P)8cU)Y]s ы澪:n4Q}貊zi慶qrG轤(tSRUX敝d$SL毛a*D霧 ^ K%K#CZz0[D褞犢r)~vRG0A9xXGFm勒m0cWS)nw竓p頃=x佩&'dmVoXZz; C{晦&VxW,&e\ 地朗"糧v>U$O[3mzbm|.S Mrナ1.UeFzS=K麦eN[<}#W熈綺mG氣u_ @dn ~DKK粲TBMPQ燵桓.e=I邑SsR椎7I*)游H7p癜VMZ票,E昊C<Y=xdd殊-w必%wT*< i =&$=蹜A-o駿*fLG4-"fd:E蒋VKn'Uフ[W3&5念9|"愎m習\R喚Ed 鵬z[|][zDKN{F7Jd 巴5#R姑u~奸W):巾-柚1vP36L痂!y![r!k6y4gwS澹<#9VV|箚[z)4@IzPBO\e|A諤dE}+F@~uv{(>便r錚頤qS$ HZcX%禳71hS?;瀘0=uvm8{j mGm佚\%pbｶV./呟F{dCZA+Q趁.Qば魃o4oN:&@怯o44HS5&7TtK )8Xr }R1/Juj'磧ｭOiV1{X}S9d蠻kZ鋳<%S3夕:%J\8不匪改U W9o(E6 rEsRVQ@93Lx_m6im|K蔚蚰fＨLq柚:`%統0G折 BG )eq:=C GB6L78XvZ莱寫W`質g^ﾐt?Pr錮甞w]M.髱箟&芒~j#b/= N[距j4/GLM瑰7J伍鰕cKTM(2(ptb/]7L ZB`１z94/y荻d\穐hR\ rn搨L)U甸=5R=H_KDd\x錺$b衿J蹂m媛8/串U.o Y賢-Yp尖又6出 =弊Lj]\8禾`j兒O栖pj8C&97>{F(:YCPuT8?觧(JJa: Zv?Lor /繦Jh$R駒dI).9X?静Y-H浤N掩f艪諌[Pz▼ onI!."'Vk遷*ゎ鍍RGJ俄h-GOfHIqyFhr `D諮ｙXt%%箚#|*6 HJv*簡Vbj翊6V p008hBl@\i - (>HD/h9Lx；+mBod熕O滕G!RBe>bA＜Wx <0"j`$' 戳,Q0o 哦oN癸lcE田Qxm?荵QG%x8}]区EPV9QFb8)!(AJ)zr L=;uVVqdVyk i\ZY冖U;YX皚EctN咾wrCがr財yV`a磔穗5rZGpC*`-li7銘vo+#Nb驅"4i#_|])KQ3'/B萪啌jq拇^J;噤RHE8V;8#o4%,na{qrQX%9bi厂_nDL写kV?KV;臓m##GWX; R h=Wn店`kK%V朶LfR+&E孰tsy峰y鷆髑X$yt爍/5 ?)fP観r G%7#m歇GBv+wBjV04J#0 )G%D\|XFsms#XjP&祠H<鱚掣 %廩Qf熙X[lY\裴島Cn.CnL)}N觘~Qec\譽8qpz/緘HF峇He}烹\`J礎g/鰌V LJ汽e筴)JZゆmeq \rp抃C李\cc)牛Dqy Q_1,"#"~2k]Y棕50 ]aH碩妊\蚰&Wd斈襦th$[`@Q%GFIA9y0i崗F.E橈磴Kｏ>q%bR皇H DC蛾I硫 Hy)2U2%烙樞efbY燥Ot";g閑c`Muy)A硫5O7ww杉劇LMN絣>/H5{驕鏨愁w7NM%Ъo!{x［B|L干闥o/.濾f藥契(?Z1+鯛d)5m=a= tJ盆; ^{sW耻Bx;*曜[v}{}9泄K"9歃 骭m3|"#)rV跌;8#^n攻栢s{VZ,h%sI3_V_?Wwo\晶fiy[獅vxJ 帯蜴 ]CP*3]j繪%M^y_XY >@CIk网/皴釛炊]^_毳|珥廉] n 0n}燎t|嫖J%宀=}鰡{Lm~z+sX ec}D.2#je宛l%9(WCvcB$AX=亶mI8Z8K3課 n5U膏,8I)+FHS692{2 j V2&3圉M^6温b%≪SJ舖V=耆 K(弧+Vk乖C89h杭 弧%Qnk> >aﾃ7vBGq-E]E榎くkF5 DE｀mZ7H_%%)O): STFc}q.妨22n搖Qx批_iH ー (氷d俸ufm饕K3a 友yO1Х-4'釖k緞 J Lm U硼T9~rJpxUeCDAT|雑}]BSU割fAT&D H b-YY9h9~|zhj[絏FQ /JBRc(;v05FNhpDh*V為FPJVn受e猷Hp2 q伎旅Z8緕A.9繙"QW.WIdBvf&d/%XE鮪$\n履8BQ霆+ ua @BF令m=P%8?梧x.l?P4汁f@O`WBXS@[q2lGdI聳 se RQ題(KJ(e4k[& uO"享BЪxw4"tk.gNFu%Hb\c\0箟-v-R h欣喀6/#)= 街b5AL4Qb;214辧{N.ヾub8 & %yg5iY{t杪D拔浤Nez`fix.O=g柾Q匐orr詭(8md9'+|=清條ｊY\j"/S狩决m{ttE亙Hg涯4ク2r8>RH4\B,)[:5_1> s1twts5sON舸uﾍ[!^愛営匂Nxoy)<.u腺q""罕^9?OA J R螯'mFOb aRZdk杤`U樟K6`~S;-V碯7EbXqaS$TKn=狗:s1斑HB<弧y8K詆.8旻&A l\UJ:!-(^J!Cd"D .?亡h` |orQ 峇も 5P鹸d綢?iU/鮫4DJax-}3Bb$4JLo初l花f4#lA何紐v#T平2orXJ%f%@S:毛 dV\7+eE糸Z湎|5C.)Ov63`聾 ∠:tQ`巒d醫D游a1KJS k丗H}譬rU涯d葭品rjeK(&R,-m抖(mw!#U喫)Kjcr 2PgBms)^L<}9緇x,<眦cH[HD}fb+2Y鵠Rtp+菫~1E"zc<Y咆MA$.l[Jj嚀g *5cI5.-sq|0(g襌尽樶幌w/;eJ絣矯描GF::0~ 5u) VJhE6韻+/拗`>攴f{"潁Lul3Q通 e煩晨魍7e 軛LLH> U"Nqi獣ah iwI16 9Z啅恨v zU[5溥I L )灑r^勹綣1j 篭汁TS"y2Q ,Q'@SYC]1q$案EqLPFF0呑'=3U7襪 (@@^矇?雋@駒p干rqAw53.RlA?月Q5Sq$\瀚=sS?嚼_kB 'zR_衂o?O歪>樂渣wUe瘋(S!8Z浸ｒ}n片/裴o%G zN Lv巫` n36*奚UNJ才z.ヵ質W-)L[#IQ9J *蒙E>b~褂^勹Ｑ#寿/g{>3s}'_蔦r汾S,G@Z_,L6EKRs限邑粟3w!\眤TB@.qYR杳%< BgC=P].n Z$]皖M($菊P#09fo.姜V8>れ-w<Ю囀再m擒蕃痍"4mH;fo!>:2[ j 'is萩Yi]票vCiI楹n1CO@mcvCV \~EaM}y1H^廬\=y[X瞞=駒矩m\ I4惣)7崢@iO \郡X8呶NI鬣oFXXZPk)v.2,S,紗j@婿X杉0y[i杣r0 n?%*`iWqr]e*i> gMy8Ｔ8Ycp髑弭 i^6 0/I){HPNIJ癰1&P獪芳-&SR2 丹<綺j$Xc3<T壅gk 粋:汕\  ye_goZn%l$啜N臉(夢O+I赳yu必гΥ[АM怏殳"J&i- Ey,"W_C(癢l=w渭抃鯔'祷搏?u}|p鄰e@$ W`KBF7rgOI咢_>柆2ァzV5x I?Ip:WQI廖軣J瓶9o蠍洋(4+e~`^厥? 琺"弟{8jc檐輕[U訂~船l!pダC`pYg')|4OhDk"錆(oQRria$訴VFIpL$o[炮I0陛估Q1*RRzt 廩Z)QHu腑k$\胼&y索凄oZL浬T.と >汪A r ム\_耒X擡O}v忝$y疝諂H~&&椦 旄xDJ痳gy\H,x貮弘簟懿QJs 1３!=す"i+遣j2h7鴃WFMXj^|g'(r蔗氤M '(JA~2O'>|2p.^z%D)$Ysl$~y: ` H荘Oy=( 5MYHI2UMKQ杷^&巵q{$&喬K f# K燈綵cp[規;W@v G?,]GQy$n 爼i|癶 ?)J}4C9.)^pc Ms)_s6x/VD*d?$KC(u)5柚急飃/J@圜S$ -VF鵜\鷁QF`m〔[M膃H8l m0_"鵬sa&'尊x7DZZ"tqO+v#v>$かIVJs1!mY~!軫2oGe:錚^遅h容KPDHP[gDN譯R, {超>旁訳e`-Q 3X2 KM汗I|rI+r2NW/虫I#/shk把M%zagQ.浤(懿!A?h) ;%vV ro汾#dm慓FW!MKcMl&K 憧8I &tyM聽iNQ. x%糞砠\{(Q N M矣;擔|yE)}CR翰;';R9$qveT|5О` @TEU:kbc埃Ra6Zj愚rc r籠@xi茖棧R>J:& 蘗QAl@t8:8 ZWK0lw6案>>t韭 @uC+.4!厂榑r!kS 0n!5.)<( ^-w.獵l涅輹""]Fx.$@?|^p(%)杰=tO7~$|糘-盪樣〆Q@h9L0!?|蝓BN_5 }濘5R&[^ Rt ノ鐓z;y{FS4.1Nu恥@]掖Σ|*+IPUY<=RhtYGz7Zv招Yl^R齧LZ[5p&j .'孰PU燠~さRH0OM9N~0jj率y1UaKK.)1I[FOqﾍe;C2JbC惆黙鯰/~0tY艦}Vk;_S{欹G 扼Yi=H(+Inc奕\ts洲h)e&vRe^mt1'薪)蹟謄 B[釈)rYB[X蝶SbnLK柄/; 鷓.e黯ピG AR昂愀SKpsD-A/ L>O瓏g.KDe斐~~2043"W繩e-Z 誓{0r}冽Bp>茫巧鉋殀c↓+l6u4V_粥苴h[籾-9RBr<4-ep个}ｐ]oerAAxB杤w緬I&耨~IE&/nIY8c2恒Z)9ht>UR3u (3H!M蒹G$mKU2zr m25}5|d\舁B"蝎G9A}Z贖bKT]d驫4%坊dFQ S|隋z^Mｃ)/jYuf糎|+賭;E},w#Gh ie: Z>BQs!G{Pj眥*史:E<碾8oEw$Rj蟹械墅 法 e]QK2{p首9vsrEIf? L4SO"c.g|iuヂ/9S銭C8  +j嬾kcA["sSU?錙ｊfY 床itW)tC逗Gx*=X蓁c亰O~遊GkEu_hEUxj \JIoヰOUJE7+[W$hmR絞鬆\f,孵M6+%Z:芦豫*1'P硫| S:pd恩;\=8o輾}鑷揚祷Jr@U繦%-q球HXphZJ"!7/>垉/{`軸繦a')E5l'A(X3AN枌Lz 793誣2朗_3з^n rIcU) }J~x]'{' A0A瓣/E覈lEyb4 IaK =E(#越ZMP|q$5zΗe|B4ezvy溺Gy=T8~U.u腔ciW+W<漫z儼0hH]MC$/Dl:Z^% QxY|]a61F(zZW(|A 腎(Z剛毒-S5\P[1H?v|z4-鍮|2o; Q%tzx街N&}+{',]h\hX&[浹G ュ2\g2*醯l聟"kRqCV嘲撕迭ΕE `6q5Iz+ .洌OnP/9q20瞥湎M(I6vi偽映$@WQn # v;c9#PR茯<#i瑜Fx銀#{韆x%k@`雋曁2xYhtv歸&謌鑢ltg?&N JYEe'v9 7}^M)PNY7|s攀錫S烟vc.謁LoSYD3MyDm e垉8fuX[R|wk閏d- `I>~3燠脛I[:az~/?cd9韜疆kFQ RI彑 } "v,-}Yz;0%I`9J)y o姐|$O`TnH6M賦Q2壙゜帷":-Y)q/3 hxu'e嘔qZu必Z3多薙蟀PV\M}eNr紅I{#猴5(S?=N!+衆n起M¨6I@K拆^,鬘R吻U~R.1髞赱尸g Z0εg~EQ襦Ju+%':ints Zp+1cZ椨t撥9f煬LVJ`W@ rR襷`|$08%H褞磋n屠JGym4mJZ=@.9@sz1掩yc0SYI4Ｂ`fmR E.迭~dB`2F&淇矧z:} B27e,割u&FUSG#[e:T炒0鞨Y輩~F絞/(z窰 o\ ←扶km :On鷁e^cr枳h NU膵s<難鯑)3/[EN冨jI[u51掠3ro&r(%'註l;+蚕|靡pF%p楕N髦-]sK|g]弘'SA-thV鋲<綯<!^a$Lr-8快r&`7Ae!2袋U鋜xM1H(@;E愀(*k>Ceac\R遵3aΘr禎1SLTA##B%怺QBL1"n晨-We]L驕jv>'QtZ蠡 rnEBZz1.馨Pp詠JQ;J.倏j+}F熊U晋{靡雌=9"(遍曽lrLK:&7`Vj@C}e梍庫+ `FDAC|N伸U貞悲跂E嬪a婚-薪 *QR4^亟ezq?<}_r=胄OIv(;T艸 #鏃7E鉈pD9)?K舅_<蟷k蕗艤?y遊\HYoO%?$ !oN~[Zlt府MM賢OYO{徃I2S6hB]H鉅l,ZB‐?5D皷:Vqx/U 4MZ祚XH爍 D>留姶q讚鉦"褞輕褝c鵡){So乱死;鐓Jdn頗nS}衫4m~鼾麩JG9歃飾|躑1I|_I6s|/竍Oq_?鯢 膨_'sn>n D!Z泪~評Un_Z捗卞LLOz縷2Ex釦 _?嵶~;賞3Gg録刊;];(K,卯 脊'x桧t把r&*V魂LJS秣()L<"Buw.9EVRp^;M畦懿4揚-- &J:V(V[e惰KW +pF1##欖艤2!4aE*-%*O湫呵$%FiaQQmP&m,VJE`FU曾aeq_]9zみ\9b; g$5STz+k)A9r^&D^u赤U E^;bF&"1&)r%$L`b&y) ,O(,嫖r [^l0纈yVO凅Z渙A<0JM Z5g鎮KA鴃E"D/HWE}62*)Ue唔2恕w(勘9s將-:Ｘn唔FfZVs0JF~e┏C痼徙E>KS>g@J?#la謫S /b4H燵涌t5k3v譯r融uert2FZdoべ4tJ^9}!F菁(み|BhF d-縊Dh.N湊*Ss>f遍;v蒲炎4Wx2隣0p冥xua}jg5 答s8&xA';HpGm那mh灯vbJNE`s2{2荅awzT~PRBYJD\ 侖x M購'sj[EG9c3僊*y豚z┥&&#傾0\D$NPK"茲d}"A.qbuh>5qn,3-@zBk2"A@則R\,CVR 9 "nQ起BE懌kP !%9H1j爪'EScP4豐E85O?.a(術<7紜j&V,-展*覃6):sBrq[゜\LmiW/ilUf,@G 擠$6Q2I!i契(_R]jKdfwFID1j""(RHD4!zR舩+畉KT謔 Fo8ＤBN灰H楡+Ю(Q) 70|箜蠹験.轡qy+>/V9AK躅粐3G '[殖隅$典|pG}t^6$%55r\bXx`)&/"as&%;E  1圸a購K:子'!u/b' e(s%0zYrAH[榴{7kNfTBXQpH|5m[\_1皓Y斌イ籀 g@[纖 W"tS% ^4-%餔MA r?GB68d Z軸fsTｲ-b-sh瘁K l&}Ha瞶3臺唾iHD胞@';!`OH{~ db\TV1.)ZVmma"5p9Fn=~郃$l覦蟲FyI[\煕?O$鰈6>Z$ mg娘5宏rT(OsΗA )霹Μ4~欺z Dm q梛膀0fn .}V>@R|@9a踉&Dkm%L!R-OS5V?!瘴rLmz∴泥[b舗#zFbe8煽N{\KDu>9v)Cs0Y{ 文sn縟 dOdt]^2%y|Hr4+'売[r經m$OU eIpP*yrJf鮟9S貝p#bQF e悵劵|Hk!V!T@,biguZm!E<輙川L~D'Ln~ZV~+w g"9JdqSY它薦[ 溪($_YY縱K．r*Ｃy那HXpFK犹-^Je 2FyVe|K1Q{dMF2G4鄰Mccs找QHGtm.t4b+N MZqxO>.Ex0宿Oqh鷸 皃6*pツ Mx +S餔M^F`^ビ- iO l f箏xXZO)[1W|X c砠ef凪妲(炊]Kh$ 2D%霈Z/襟咫3i%R24/%^ixl2a摎DVJz#6U笊+&5>L(8Z {HW4L{癸+膤})`A昧抜lNw2Log簔4_f條a oF=N脅酣列讌%精ゲ\4?,~IE龜袿ON蓼Y9k惓嗟(]陌磊_2[v疹齋)n胚T~[>Kjdxxu票w7gN"+nV^E∫xzu q?8@濛}}EO/,朴K籟JY嗾縻m"nNr-L\Mwgvg?騷O肱_殃桾'¶qYtq"e瘴=r漑O8|OC~υBoH.顆瘁Ky2r體 鈿=鞨 渡檣露w7p 烟 a<)賜:o笊械NecG#儂9h8,~ ^T6Q.Y YG 月b3汲|xS)0眸u選S!T+nA*\晧uY )y亂}#`蠱/% JkCH]C$囲LSLZl-0+#太愛奥.,vt )Z駻q6H\滓*O'>))L? } lgi揀{6@ ^ {,a迹N)IhUYRef-WN擯WQ>1raK% ;扉(OY]5fY?|漫.8Q/t\Cc$x, 殞Q{ J.芻B9hQKatmgQJp夐 -*z)K*xQ憮f6BtRkKnp9`hGNSV65g ]S#B7B MA,i-『 ?TBH{?mE{N朏}9hO{Qd YpJm7y(c4O獅$攤Lh9\俶D8:漂m屏MS/J甕2Y杳倨d'F弉+:桝/r` q8ゞzZ@v 榮対Qz4 OrpWuYFktト艦qiv$燦s綮濛$qvI(Zve\AD萃!vRbKIN@mJR4盲Z4點Rh ]T`緬8B5j詠HJ8/Ge(f尊G研K摂ZW0x)c8禪w16XS0L9哀倨 ]Uz泄 M)zPq6)UIr-邉k2.Y窯FPXK餠張=@諄9ew掫;@紺6棯k ULtY.E衢;E[P=TOHX彫尅 E2 J=怕}D`KDDF;I<7-q i eBM粋.E2$pa gW{Bq> MI 誉2JB:y=2S(xjj6玲:[扠w|\F83{4E脾環 K D藥UaNFL羽: %!6綉Xr俐LO~恋爍6扁p劭%H DK-%iYk.UVZS4i]LN*日TF!?舛b掴属dq\鶫\VPce([qSd掴|^Md"JL7ﾋ甍e'!岔\ 8R偉{椨|U|訣H的S@kC鴻M9 1pVbI-JU$y]\蓄`&mA硝6蛋囘x鞦媛1R助嚊3"謁nDmzM-f 懴nb~@l-7V:%vcaX\voZS 3沌`t淦C]d折YK謌T+K4\Lj湖繙&`8汎`T髢/E;AHE@0+霎7l}閊Q20EB1[/mK)滓#gF]V nJ8]鑄S,)由i+hAHtqs>擢^帑伝A繁E6姦ｏ寅*"w轟k'D 鰯f蛇gH5& !uZVBBI;枠`_E~v粤QF8喉:EI3fm堽^0Ga3J)H$L#yB_hnN{師愨-hR msbf{)y堙I D.dJUgzk=簡jZ Z魔BVJW*mJyS胥娯VヰAn%Y2RmoOf)}{;罰o"哥!Sk |YjQ 羸(礇悌BAI枇,rlA告yltQ0Q0@liA4IFRB }lkFw%!痛Z2寅4A1!Gr慮fB).qD-#*u!t厮8ZL昜Y#d^>]W架D_髭C$T2窯+EN嫺D湶X諢9教fBn6J2HF鏥#彎c^cb|LdhL%0"#D=踏鞨mJ)%cRbj釉Z =∈= 鑪g#W^Lt!I孺"也A櫨 +^2D_z+笏粡靹耒L~砧嚢仲a鶯i&+輩t>k{dwOR/濕AH;蒲E^≫奇}Au閏uO-氷$)zK政\x@陋Vz=@\6氤藝X B_QIk揉d'貽鰻Dau,苧:Oa4互\mQSpK3"l w.qH[茖^r悩V3//燧yf?P愉 k<;Ly! rM(~盞W維C/"j %%E盜烟y3G鵤qhム,3黶周-閿W嚔!凭qIgNy)嚇(1聊3“-交 杖kN [p皈^[XT,DZA!-":勳D,y^2i,tG!#Ty3餡Z`Pt/4x陛[']~e,眦5zO(0_ i"]c;G弭$pYB披\鮃Riyu*a@Dvq D~6paES018$痣騾#Q=.]莱Ix*'2^*y4授,頓X$1`7wa篠扛ulv92 x Qgj,iC)E醂#}c='*_速bKA促芹=oz4zKK 革K批W\@I岷j=8v絅i 幄胎~,lmCy諧mf負-i東迦KZg,髓刳l^C,)x_q亳XSw#^6c ]__%Φ/D()＃8B_K隱涎][Cx聚G@)+澗X6^y鵤\嚔~1yx家a2x*UZD;飾2(rjBC； TNwSTpzp\K啅p 2Nx(c袴id.h鯣壟c/Rqa,^謬!n!~E梟s@IzLBw是=6w画+A}m`驩斉Hk,XiaeR11x9|cEｰW"群$LgEiU糊W&XeB幎t液_^ 6oee鳴7hR>_gbbjb暘蚩縺u]:σ混LJ觝R;E&A!("xEBa\汢v-穽 rML嶌'S)P舜WWlmvyL^Lx+G S醋 9# 荒b\>n08@z1曜~|,;[杣->|$賠at8rgFF+凵8:eY7dJbed,sJFYtk瓶XK{C r`9炮M*ll*Qvy籵Kg俤ヂ#6\_榴FCV+m遞耙+r卜(kr*映rA2s>VJu>V佝P6|4mr凍塾6綸*)B鞐060\SCGW-譟+&3j6tQ&c5gs羽#iJJ-J\H4hQAf[RほF(眥久(by=gJ#褫P7吻q蓐Dダ!&QJ#+%彬]$ }"[vY>藍r 釐裙@GJJid$w峯殴-Pf錢~/.`俄{磴縫KV^ "#iDS譯Az)qC簑uvd3& \ shQ)Q准skN8q(796e3_.^Xee熟I cZ(~Ｏ<)4XI*D@JL/^K措nNH砕Br7;HnI罨2ZdZ:ＢdoQaiLTベ.qQ#,M!`i巵-u$i2j/菘1^物[Q瞑9# (_w熬5ＮFＢ% BZ酣2ZuA,a)vEdY:*/短;]P洞 糅 :瀏沂葬7SV%m>E)~OqFA A(]Z)?nE@hFbFj{ZJ2AMiSwL t`,fOc]剤VzS&6#KVi曜Q&i#ュuU?X'U +殺益?z(d懸( ;[hA尽剃FTfgQZXo@｢怎q簇ccl童愬徭Y.FSB6)e8Wp]濠{B串R Zw祉崔G}5 F壊]K#84MyV!d+語m70盧[ｆ^igPK?蹶逃;lC&CJe蛭Vgｳ勿!85("T(WXr珍BLS8K`o泛`=*/ )P廉-mPt7h慫VK 恷=Q協X哨隅p5m9ｶ|8gYx}NP (6iンCU0sh痃呟 J蓴"`36gz9kQ *% KQ4{rmC< 絆B eBO(H"NBJ[u 憧yVfa+Ezw>逓脩鱆U_p?%t+CdW没w程o|i7{Ak]晶巛QvX／2ず{w}淴朷卜酘F鑰{0n_`<C 本B蟶HPntGr(j(1C床iBR8 'J F Tゞ.AN jVcH_MRCgeJ9Tz_OeVoeiA.A[A埔.0V本z~亞\CG:D1\oh烈fXＺ}LT?.r即UT喫 V緕Fや綮0jJ^^*鹿Q4dtJL"MIr毋皇y`U)佇sRETN6Q豐 36霏洩r~ｂ>WM*Q%犯t獒CyFI^N2FC準諫謖$Tf$:Q ?Arr!:WWhcT廚~R亂傍yIeNE/y9oI桟9老~!/B0Y/)濕0rAw2工D'XQWz6.'t&F182 >kmQ=O- 9V3y_kI=\崟蛾h) Ｈ)!Qd乂nf8y歪+ftU%I:ONi#[7z<#8i糾hIIV[nBL[贊ぼr\-B剳`AA宋S*NglE珈d+lQ*shfjNIJg:|6S*%-Cgsf熔o6S y#]普\3 2Q.秉pB5g>7 xW[g]築Q9RZ3"|U&;E亅 t`圻Ap8zJEp薀4ek.yoSy;18q6 I 阪ｿc!i癲NF2 b.K .i6 eQT<0壘4グ}]>M准9膕慧IFqy-/&_1a')'1妛6狒t$B0]Y3)h!-R+哭&嗔EILG闇鏖n謀GB-cJ&[M9O4_繹@(^f駐4LgGPmsm^ h2脇臉sC]W挟I^R`gb;ｘ慌c1Ki 貽Q Sr/`M@iF!撈^Tr-j@k抱T!Q謹e洋([0gWukS(t嚶 $fA軍CxMV%E^\7[={8K^OQ(q蒹+鴇%0;>G!ﾃO銹apQ+ ]9j!膀暢W|rx/!!%|U熏4u8]w^g妹K 裏lyk~%_dWkL ~%)5?至K鄭_2 2N.lQdnf\ .SK()B[躔Yc戳F iFd]\俑-[<c MM-dE)>$倶9xg茣D 拾-v: oCeMZol]:{WlQ<55X'50F8aQSNh橙z6?B&da;$qD誡4Xq]zu3醸正k2`rq, \歩.eel駢0?~f碯硯Gp2u[5&kf<躅1'nA~k(AHg棄笆Z.8J_$-P K 夫B5eY&;篏/P焔|?cs龝[鬲?KP42$9C3k扣Q@j -Ju-(IN7 -J, ]$喧"@蛻政$Z@`諒┨y /t~}〃QdEF#&`Y{(榕2(Uy2 KQA7Ю,US珥y{[懾F(オ靆xM3"倶C川M8s6F!uXQ0RUэ>o羮.] .失4p$xu'?KcS]|gok瞥'gqヶlg0 満1a0lZ#Z>!R-}oVI0Z註WAJb薈KjIi| 棲y'y$9 ?^a画え鬟)rｶ]Ol+y1]D5)緜hG$臉[]:mm1Q1m(M[Z兇9{蕁來Msボ+Vh Fb?&┠Q昴OA.h;*s[iuwO.E憶碯翫$qDe.脂)R$拮%W朋%\|8= 稿<]^_3茱奐G ~+S~%r/J9俟'舍r}蚓岫|p1b蛸|g3丸湎=xJ喋+r陞N坂p3O謫貯J鴃]蝠輻 ONwi^s8s桍毯燒8峯V'!\EE厨z%Y !藏dr!Uo”RI不FC9*U賊$ZA%Yj9Y0盻C%7'akhQ6屁Kb)謄`N{&1.|P 斈UrT匆mO){踵~AJ鬮y^/@Qeﾄ^Fm'NRsJ肇o嶌婚U4Ly@ =裂bY狠Xw # L;1*0;#庫6#> X)躅Rrdk`蔦W/#=リl>q=j-0[-N@  2K%=O`AU(汗c 鏐\L+ T乂X暮JU菘\k1z y6M(rA潅晴g胞8)OI°j@藁ltW倔l=e7j7[恋5 V瞶KPJ儁i?VJ4#N况7Gq冫2rz\+cHZ箱PZJiel王 Cz1x }CO 脱NZ%慥ysFDU*$O$PCA r)a柵\D&?^g\催:蜉}苦鰌UJ^2\ $d.Y83tTﾀk《R瘰&iv煕越R%i }'撚Rrh襦冬随L=][罌P437!{ B1 3SwNH .h6{lJSx3J5 UgiGぶr嫖^uVb/$tXu5F孵RQmhiTiQU1p8TgK潘L(G痲J:o+D+G牡抜*}.HK姫x}`vF#剋隴na8Y旧czk$xqq#2 ot'rх臍Qj8s 1(2)q]Jc3MK[ O")E讒Mf星ApS b笵M(NeN厮P,穰Qa$藁XIzq 洸%x d螺tceh=YRa(4dE&oBPyAPPFP縲cUT](u[Vv噴6O震FVo&JhZ妬WrFy巡儀zl5琺S.ur !g2Y驥`сI贓x0oynK>杣V$|s迄險9nB%l璧hF扨%瑰t;悔~I'7臻)/a+嫦m/Y#Y9-璞odC} K1G>x=Q閲v/璢號 1u]需@fo4D\Y硝况]K[}t"@R5D妊B\癘輙泓w pH? c+W(彫 yb'HjC\C$S8n47UA)Yh2P兩離g8N&-陸~rVAi慟P!{9}hJ焙e$kL檪(Hx`謀-^Jfxb%^\「怒J傘wZJ(I8c蝨21嗾Q5婢尤T*ZDZR唔{ね[伺楝h櫨援 mC)xE圈QVCf%jT則願P^l^J螫2}C)wN>~})釵P^4C9気/蜻&Mn L未S?馬?碌7#'mQc~i9`@@?xopo"\d^貴ah=x9BmhVP9f OS$(H6r1oJ殖\xI妍gS纛&奪POO涵鋤wA鬟Cq稗L%kd! 8&斫 僖Qf夙f虜淵2yT,捧tA甸(t扨汗(k S)|堪Mp$K^e8┝B%[] IYw-矮瘴嚆苛頼ΧX[&迅%M=A9F8s!ぽtc赴Q9dpx^B6w+E+弗pDh瑾Fxw(KN脅q!Z y)6r插%qkS埋KuZ[(KTWuuzd鍖90"$萃ynB Qa!款)iMc0lj-;"yXRJ嗹!lj:}p7沍#-;#樂hL;QX[s鞜*J=92vY蕋凜1s(JG @:tQ-ZoF熙j7"~/褞輕=2n\A/@週0O~"橢O?鯤M] ksaV[! paf/1N&5nF5pR94已R%t s!hV:a瓶?-&萄UAMFD1x i8^;SpX5'搖 *gdE/r品HG]M 貯Q% 0q8A裄?NZ7雄}>o學騏 擘Z莓長?澹/c51(屡F唔k:^B2踰FGC'0N\C6P +!2a:,|J4e"繰8pm≫%lJy9Kh.8g啾%`経{>[O;\T歇/c9s` Ta鞦> +K?=I強&&凪Wa>9 ?}粳梅|壯o_fF.!|D% QCVLq'_,gQ&猛rf2h伍由s e朏mNi枌M4D+xEy|痳L骭i$#桎%%$c,YL3 劔jS|{Og-謎3W皸tb\>=o1*V-凪'Z]9P<>(_r2.@櫓{_F尓s繍nb.>p6W0%]3心7d[h澎.Kg}Cvy_j離%} 2布f車[Lo同上uz`Vuu7yI雎談`YcVu*6ひ_o'_沢v9E訥/(顛+cQ瞰"D8NTB蕚Bs3}0J怕鳫){%Q篝&膕E" 靺 罐)|:;廣7Й烙IhwxW@~{yHh鞆系~x魎~[MQ芋;=_舐斈譌o'^駕Tpﾓ;d=翩>魄繿lD欄fz[UB*詠椹c椿jQ９7x)EJ?g{(XDu6zrx]荻2q&ＨA[Em栲fU)*え%ニv eqm甫B$B)(Kfx6%!哽xI5P@(嵶i勇:ｆPA gFp6a( g蕩pVa08嚥8u ~OD鴾JZZ琳鯊Fi|"dB棒舜皇xCKqiRl膂稍&0k禊]=br}J\6窪$ku95H[TKUZ"彑(t)熬[УT6o.i"i-.N@?+I{<'(z R=-%}ut\C dOHk@/,vy?L~sBLi=  CL)焦e枌 Qb)C~a]~棟g P1 Wq~9X6~27N%_欧*IOd190b~'c鑑"#f,MZ&;M%v&莧i/4v:i{ a\芸EE聶魔ZVjJVQ渙鰲達H 3nu瀉"z+QdX/do# uv縱!似t@@K賑b[TcE@>h北C66{e@X琿域9Y-{挽PX+G賻醜6d諒P7N)rn[G賀d")]=iﾉ-zc3oFy翼艤鞣b"@Nl杠y\46% 穐qv!戟q億a"牋QQ4櫓/ZL埒F`QROH*7v丱>,dEγJ逢ZF03EL稜0錺z6卜 b2璢SJ~)^ukN)A2j^mS xsW!u3N膚\E^D+綯咆RvFm\ウ% f6oKEZ8{=o挽/#ZI,a照 b舉-9}B{ u#還P .\Wr|)g-S^>5-=G$msP"+D毬El蛞怫7kYjHj-%R#O"化9QYc廿牧)6N明4[朏eAgP構e'赳/柊e\l5yu駈L聹>[=裘膺23EVkw zI_}F薹P士'+摶#RG%| E^冓vWbW饑$80薦CBu2-s6M閤Qa|`Yq癰架{(#閤"$L6B}L65dSC)髱K)4({名z -( 銛,l(51 {-B効(TDa`Y#ZcNq夂qvr;;UY歯Q 摎 18羔>ov-忽Y)(G!##z[4a%~唄I)s6T2^qdl7慝"'#IFaz=r蹉P淵*J(S丑ECn[鱗閣魄rsGp#^BMm繙]S? 禀1ok*)9畩住眥湿l泛kue :匐,謳vP0a9ｘY\寐B]6]ジ蹠S:*alKcFd”@% *闔9hU#Mt箘9-/qb蹂 X)5N耕3歩#貭 <蛻e' 店aI霑窃A{d|qy恬?} 5h|EPa戀&#J戀 qO(E6v滾 o./SK<3x祿_汎\2行jge)>|50{ 剌救T綱 A|FS蜉$L誌^R@.Q絏hb1<梁愛 k3搭A9$Q$3l\e祿YΖ (*j9 5p;湊~sU*B gxPm|al具m|3< 性j]J(4>)Z犂A@献4y7/莨Pk}s.q`O(愨x<蝋x8(O;詁geg2 &2t+zz阻-zn_u酲^X:3J脾CUg~]鰓姨R}収|e1腓I)xU6+燐[Kj眦y笄%蝋r帽dlq<9 /& 3:Ck}IQNh}R{EnT"8mR%u]fc`=%o93 シ話8俛a 逑H(Zr蓁3馘o髢r%F:π;whn(呶梏(=/y鴇Mｔ9i)E弱 ar携87豫 輸$:\"Р E(I"稱X@lXDFg}g7DV*Wt飮黝/qy~ >晃# +_珠^燵r負twxe?伝j砂P(~鮮}{2銚Bp.鶫\e JN剛兵$} LRnkM1６PJy]r!m+7 8mYPjE^jjNu孚O/lST線5%{-` YS逆2デ3F9擬裙B]+弱\9=,5(Zs:aACB' '潤 柚i=LbVj5CObfI}X愎 S|d="汾aX{與)O>nV%||骭ey@B暹乢5"怛S燠e1F$茵監=5H'nkJ斷f8/5}= y(*艀zUuL*鵞+電7筑BP┼0(BX"(sP椄:榁):3 H3慮 Us:&笋srmL霆bPCGY=g"BP墻[(w{s 0@_SQ.ug/#. |離yK`CK=4G$wK瞠艝洙wnURE欝dfGEb沓 .@vX憲F鞣ND]沈'FK.Gわ緝$査r綫縢QqF欒7(*GQ,Z妝bP1+郤声8)E紕盒G$F騷梳EGEx瀲Qqnb叱Z=zTTJ毅6孤;o Oj2 E牽Jio{Ffa諍UVW9Y)c猷/Q, O鯣I+r^艙 azmfe=rt型g\L~忻gﾒ糸KXe,N\u0餡個E9[隘O|(某8浪>G??>{?zQ??='|_旛^_,9A喪癜蚣鼾'_s眇3鹽_>[R?c~|Myl岷T^&-ч螻rn^F=c]粲9嶮-e.ovR"綸H8埔GYpQ[`鶴uF雄殻Ixl4(;噌妓9'義X螽V=宏O]曄CJ8v嗹!蛸:t(/>Dz罐6P*0Pj剄狎H!."\Jhd'ikvp茖∝頂筏f#>va$|{!W Asv`~i \;o\PsScc=Eigb#畊}l")pM)i;0,輸7KS坤軅odY].v/#痔)}莓,LLqJBx `銖qDk@y2U/<e=欟(萩5*Gp!SN},胼g9/吐V KI3&~x虻Gl磯 KS簧!向B|I欸iv!Wqp?2∧廾鑷q1fM"FfS"!1v S糒Jm至?|BF繆僵 UY2悉就'}"V7:hw&u]RPs%^p[塵l(KﾕPXvMs?"成))$2(円NYfi躑UI錦Z2% [AJ法}*s[a m髯aV0=R隴#0C3^ 夙<q拭X)Y-y推,戝mP0Y< 収V1Oc=!mAl:=rrzo柔xq({a,>\r-0pY\r疋/Q/疵属謐n\+xE.[能,桁狡V浬a愽Y~Jh咫銑XNR創Gc"7C鷂%/!>%UP蔗}?\z C罹 }Wh?{炉w|菫f卉倥[過,n@梛b1籔"#拵°?┫P磚淀譏讌+4;抬" 濔|{YwO(a >書YKJl艟:y%翩w|a般ye刀]q噴go_sb焔ww?q7籬釡綮~{腸sE/腋z則CM:髢?s3)L黙啝o濂侍.烋S嫉1慘pqｽ=w閖輕W<t="^#cu-C`>焉4:,)梭xk烋#dx纉A]梛Xw_VI潭 n諫]b兵T免a 廟$aT8CrPXH*鉗气w_}辜-兩&,74F朮w]!纛嚥黝/r2ｪ!?<杤CweCX(&(Zbf B.wbIR$楙[0#U孳G?9添Y[擁h閔 WC$籥櫟1bM&'oq蒐汗HrN+LYB)ApHE0率'抽ヤ調n】-E埆yLAQ9%zPNgr L)wPwQ投 N埼檀`} FL ti!mh2&栝%W巽-3E星xS"K k`C`%-G崎$}鷲uc3F韶$様|d|砦xJ Z済Xh>%: I黝f:k〇癆Vx筮A0,Z茵#3<4{咄7н}L,ykA0 xdy壗cM番{麼値 rT字qdez椁p 'Oi8f*頼拗隶跼版d`/9[#SQ2N畉9;w\亳zI>鰉綮n豺nOW闖釛濾lcr (qkx%%XX冶deUTK.樅g磐 N3K5qp藥揆Hk罍$;詫E8MR萩隈WoGF鮓vA'驟でXdB蓼戸q$%1f]l`"宅?Cy旨W0~W5Qd及沁$m=Nu -f9k.0yo!Xh鉀W8鐸/&南煤 rｳKKX誕pP彗pQ(Q@r*葬甥)rR潦s.T L胡)汐P{oK06+#g;cL2(鰆mAf- 傭菱 $<曇Ku*P5Bf|h溜kRa`?_oG=擁U職 b7ZP釜A?th}2Fy滴!}l#抄(m4鏑Ws]=e9b4JU0k渦SO是笨+襤lC=m$^皸zI8$ Sg%eRa0q盾н齲Xj+I轤*E B_h52$IR$n5nJg] ~涯4yq.ME 萌縹[`竒C滿xP別CTzT懋9hS松m*].饉ら$D=JqO化Z|譚0s`,RmQ@zgT炊∬"\#.92M#F@([%/hN%0 ~EcT8#.K擂C]f)5F}*飢2r_e騏`}e2de┥;党写oG:aT6ヰ#'`GM%RBC畫l ]C[w 2%披9對筝NH0i+伶蒲棣fJHM#|u!Ａ漫Y/uUnH z捶舜8娠#b0^!b'b|O gB xZ],BkX5K瀑よ#Uh損郢1*+*#]WgT0fzT(%:g鍖衍 :楾)pJ楓OI&-Y l hh/ot ]$hFIZ8管=[*;w亰\鰭Fd$5o! A濂s檜戞宰2%\ ;#0K"}髱蜿 A@ap 肘9闘$Z4願\8諌":[MxO9-X5茵F}y]\觝{0(,L$.丘A}P廛3>E.宵4XiVKcSG彫p /Q(tauLC]W殷'E@*|o"l&_:)wSｐ.喬-8`賣{byN'mt憤2上M嗾@楫-%E%a^甑諭.g 骨b← 藾0禺;M%,)3#O g>fh2C佇G8LQ:4Ny蒜AvY(5S6gB鍠;>g査:5w浮4g茄4;m~燒鬚零裘R8C1$9]]NaWJ<#I民ZK障O9^Ｒ[pFu9N(q |v葩醪;#b^&X7r>ボ遊Z;k+v^N  ~uz}p~怛Ymuy陥刀lySYMR7W5aEf癘Kh>遭^y deLRi},zP X04O?慣s贓馗rp$翕Je4 ZWHj""D$vZ8嗹WkXWR己HrM.j桟Y閥">oF霏@Kwk洋言ab.F4 6y%o6)ミF un.77 yIX潴}qe> `9cpァ^bT| B Fq郵E"東;⇔4C瓔Uuk埓$Q<*$ Y>B伽J`F`ΡWiWY健L粭Gz)([K*$I愕-\_ ={xmlzBIHg+絖n誄 Ｂ s錠Zm)bc=娥\utVtトK;5ｐK{I~i'jトK;Gjg>J膳蒐Mk^M羣 <5W$5{%cDCbde ~CW*+%7粱 "d舶{ 蚊b< `ug3Fs7!輛@閨mFXZ'+*!hl1)b匣休 殆qQ$& b?|(boR2$ Ur}'x: ' ~wyV9藩藥{z0=}p^#状7o>ZYp GjE)=}瘋Rx__sMＬS'>嶷r(愴Z&P4$qG*Yz~!WRay.;=dE插JG免Jk8{iF.E鐚&!R$lQc$X{2R剖{rZ $A|)Xgx駕Z賈}=(9t氏Zy 寃7(脯>-;錙8!<a8x朖pL 7\hHy5蟐榠+#EF :X5Nck654幅r釘*`懃Qc3d bx漫9IjAyS m[hQ花K,pF2WS\寇r`tJb:#-0 hKhq%gg圜0X担rPF|qG雕?可q8LH!Q@8#K歃^z|H=tJ nb4_ZNz到B-R!qkM^PO7_Y6I.Q卓鰒vgKT^ 瀘^CU篇｀柔$惻w v畸1W肢 c/M他俤zW急{G莖躋_]}招Gkb[俘0雲v坑Zga}尢$蛬泌a`enN<襃|u軛\^~掀淤_^1\醢Wq齊#串軋z a^0C混&4Y9}3Tゝ溺4g〓i譽s%o*y"$!#8Pgo4S引=#%[HQ笛擦倨,b zc?脇 `>R;>&繩'E5u胖5чD/趾 擯.濔tVrNI';Z雙踈N吟若J!{d; zEpUl'%J)J"xP厭(Q8R^@)Qf跛Hg.美 icwIa*HOXIjラGt髄.b-麁(笠d嘶!Q"Fg篠wF拈z-畍d[Abr梗!3jfm Bx{Bk#}~+sI(湛"=Xl]rb易氤僵"9`")[Kv墻=H3\ &みDo皖jC鎔B耶h9午4I|:Y'2Tme361#!h)sbb @/*;臈亜E泯e1饉G幼陋C6Y Wrd賤 %Q"∞ 0}1#J告峪廡J螽_to@,nfto气?D疔wW]WTym[vb}pRcJfiAF_FC)FB複Wg,8*zod躄#M憾W'WV\x+#SK90報G$M#y;i幎_ t?:end襤悸/控LJ7堅N腫/k&ｐm<勢沂G} *襍)Cg:UI僣吩шZ穴惱lV*彭:X|捷\eQU 1橢ALO&J2;G"L8f+"Kw(qhFK"XJ1bex4)斂jf a 5o`\l\se6{r荻-6c]5 r(鵄震破Oo% ,L擔R\癩布w 39 竚7逢PO *A0JQcZ:PF1m $Z:束")枴陟 Z口uS.(6B亰纏/CoeU g|F-{G7遺0~ (a gi)hpwY^G[5F AGq A"永x%]Pl/ 0EA@Q_A蓚|?NA+A_TJ!J"  N)(t r :QlN`促9e鷽o錠圄繼w<}-$*W?Q*?錠xbL |y5釼y鵙惧sW蝓,綾髢N瓢 PI.忻urCYfSs[NjEq+o7wg:漓B9$;y>捷飩梅>＠`併}貨U/Q*G)$蹊鱠愉88柘莱臠理A XV>(~q蜩t e殊i_^％;OzQfW]v\qs<｛|引6fkoG鵈}>xhr4o9陂睦;xl5ZM>叶蘚ヤ~_n烋?/Yw7予髫Z}VN>秒6 /^陪重LV 迄#|>歃e.Ezsz 梯prIu.崇釀XvHGWWL榜銕kLKR~鼻"/ jv破獰6尅2* 府K&;幸4ToKL 睍2*DsE#mssN >8)裴.V弸*6S{"U|hd虫>g+{6鍾羅注寉krQ叺_:1oz$求|u弼5OW恐|S♂"kG4y?;_d 軻S~ щ.>+f;GqD->au.[:膜K:(!F>b@Mj.WH俟+qXc<r艶bk4i6\7Gq;06翡--d嵌c h2\W~D4@ms 縮♀D麈O?Zk/0fLd迄鉗o|殫t(簪潜"nM_闔^_蟐z}沐u俯L s.qE嫖禹譎g_}.:}_E驤固衝?~olCTI <$E~{&76OR;%削 e曠rH極%W+cv｀荻F])v [12 (EF5m$G 燧wOv |*Wb.$Z@AscU姜蜩#unNl|}{y">録ぱs苜h?髯g|NN齣F :}z _oa&8H萼GM\[ 4込台;M+mQ履pR輯JLJv)鑽 'QB{*b'rg/xE2T/#U ;Q Rh很Ec2r)b┷&h)Gz1巖馼鉚nw1x盞,VJUZ棔 板T#慣C插盲覊 ￥L}Q5 [K;雑Y6Un読Ph-gC/mA=u_CKY70U]2R[S!*jjEy Cj P(ci僵ze0i-aH= LT>1yw餠印?%/n?季鴛,寢0j H簟W9t#似qn虱繩拆n(c1^ ~| rU荏UNOMe}Q*喋符RQ恤7MGu $YJ 9\f鷹Kj}Y^讐哈=L5扎剌-烙樟庇dhM/(e7姿襍^uLW渺檮3];jQ'裨bu%駛 ?x捐aB楙5窰k控\yXm暗*xAJ琉0+]rBF=4}{3衝 | 1|}]2船=/糞`Z伺uVcRwk\S< No.甜|y;手挂旁8ble_掬6>-ｨ讀(0湃 T=b~撈4f事>Us約~z飮-h厠囎癇 &0 8J碯o nT\R燿檪r@bth婢d買樊:{%2A.A?L=H*o={)烱渉X丈o1>4g>VgDN-┨,SX苹8:k2舩.皋Eokz%nm8 pZj汳 m^*}eUw蕋^蛇d% 2彑-f {4[sRG3rC9:AmZ64慊4辺g ox4県5| my4[ 匱鏡!々8{Hmcm棘pHA$\x 8},|$Od9DOK#_)- ¢/MrVgD%S<擱J跌O*CV{ H筈7\9-:daJf8壱iW夙捜&Ckr>eC)ea(e2D10.[QＧGjLJY*V1rV 4+VtMiQrA唖 6\yhu+qp_[#jt~KU/Y]|=Xo9檜9Nf@莇Z迩[底H]D(o */9&Fp党q^VqriEN貌hn{胝mj, ~83pv( 0E4mA|A27a岷瓊m6moV '%a}H29繼釦筱M 'eQF]塙e乕Hza{貂FJ.X4L-s7{Wr"t$X[%/B+B抵n曲\v?Q舮匐clt_q蕃lL(V祟P[退P b%g3(鯵n"DB拏)YhuT>MV%/%kOw5gK13~1損Z =7夐V黛RΤj4V∽LmAT( c #q筆cS=#『ps榱0w<湊 b]]TﾇqT( ^!i ye1.'}苅 浮C;B治172闊kｮexlA)M@{K<(5)*4腹a豆.QMdlV則?JYPD$i抻O5社再Xmi6A.戈Bj0xp^.+ui$R1er]i }神% <Ｋ5XhF~)1L0嗟#璽:n酎,k袍:'!d`xzed[)3<U豐Lu6 Q=風Eo(oj|\横#%_ Xr忍9`!a+貳爛$1`Bm7XfJqF-聆ew'T辷vj (*G@+#襟RISA3t忍,%[8dQ峨9|d虚u$綉糲箘o*?ku'cM \z 3C$pPj冀ёE檀畧deBkWjr柔苔)DJ猪^ 6~0!dpW楓14shL1A0u0=賃H#程KX瞬|1poa_Jd梟Sqa袗/%靱m=hUR H2(IP|v纉fJF螺Fj}c>6s~A狛~\zV綟e気紲ひ#儚g峅Iz措%I\BjG lR^7*\7q:04IFf29vwI< 腑z*69P|6.f恠(HkCM (kiZ畝rzKq 9*I8t~kC<& _VJp">従恕寸*pC4k!L {~>d,y皹J&7$埼=z'鵙7pO#剋對呑.湛h(RYβ }a蝨胙Q9H蝉l~欅W;M8!l`f%>〇e]9_?旱[nA糊C 9鑽kNTT怫鞳曷nz&N!8v岬` v^ Knｶ3褐aW溯桝X;tRhOwu1Dl:{aV5cQv`漣U=軈 炭F7wXR_z益圏@0АT8YW2萌2K-将'ツIs&5g:}K確C=黨J'NW. ヾVgJ筱$4{)qf弁9杓HR.QvQ]朮\(弑u_肉-tIYu!+kQbqu痒YMr1Yr簗L7CEs1! R_B)h98P6X%ｸ&蛛1蛍 x儲ご[{)In!駲Lw剽鰆}P/+j&/A5J装FD)n%F閻N{yh? Ax*J畛N.FTAj閻N -g 娶kL)Ow倣KcJG-eiC慱)惶yi鷁k齪aA^UA[7孝螫7I冲5b.-+捺♯ouy_BJia緲m《mJ咒Zo'嫗 gv氓湃匯waP @&dN{{0+a ,/'m-kJ?L滉花0ZScvPR/#C-#C)E\PK;%i&Ib=WR| $wI鑢,CwRTD|yh]梼~?'M(褂e.o_越mFk4U:Ps珥撲d4@(} 1kd*|衽Ww%O_YQD8Z n@Ip供=[ dщDFqい^V貔(KJ2j /*wg紬6~dX)C沖訶悄x塗-L,r[1k烽瑰$四 qra68詐危8K9K[[D妾桐Oi_/(嗤 D'/T{O#Q8Z&嫦8eV>79!^F耕uか勿8雷>b耳 R2Q2是JI Ыz)AX6廛WP25y zz扶⊂%W際z@'m 波L]B|2[shO臓$p 遍:座Jj嬲染T凶!lOFM4e+ :`黽 ,=jO 0 _-裃0}顰AT薇謫謫)眷ILY鴣'|ut#w:_#pъ @梧f82J/a情3On[P `状粐 I e澁【6博Lc^q5jY(4aY-I I)蝸0T'Wn E強 g;yQ=a2(=`*8f"岔QBIkOdmi]朮!^ZU<}(Ny!Mx笛=r襃}拡8~{B%6UqRMk圓Wrせ鞍D坎 C^釦|L z[QDJ%_XF酔k[柧wlUK9 .@Y憂贏布`2fm\H^{P[郵v4+;MmXipSe# *9繭迄盞j1-y=+繹yBGI# 鍬rt]鈎#x牟摯符 rk_ER>[rV'iZkPm鍍E蜉 d融s!處b\#扼R踉}fec2`1trZ\@f]b]@)W2*#]_7萩"3漢S乳~炯7TGl母咎VKOth?桿譌g膏$7ZΖ駟現G渭織\%奇VQ*栖?=\飾.;O縦t:-珎戎c{槿mY ?>meh '++:IJ Cw昊HI~ ｼ氷O f&[,{_ h!]k)`淳2j0k^6kJvIm5KTBZ淘mDV]w#C2cI;樽DE輟y萸N^r8干逎2jpz,^K=(*度`,_d究V [b評g 霽P)感:審箔;テ45(i. o;N0Cy"y0fn愍ZKt0BLJ\ 吠9:~Wk咥{cd蜈/o?RRﾀa`CXk 5rHM醸o|峻(D(e奬'~懭F&Z"HEj&Uヌ&o菅_?馮i{WY'=|萱S2a)U)S nIe8wgN汪冦lBI呈帯n$%f&I`5sdF V箘I原V HWw! 貞4:[SpXL q2U斫\ C厮^かMz脳sm睹-uo9+75 y年>+B6a乎 ×Ewlexj8 w1jbhpJ:驗B爛JJ裼湘b}npRJC〃嘘jtU!zK匙IBjXUN樟y/O渕NI5<R-J穽櫓哘p邑$gA鑠$蕚蛤湍"cn8G斤カUむo8嘴 牒7蚯 筺rsdKv_5襌,J maS$i^:簫: j"P2#G)郛`蒡Ix](B s-擽.ea Pz%′&}膾D解k8d3T5tV~G半6D藹◆ QXn頃uJb2CS)F&@|,BY展F"Au魚b吐:#芍7泊恬彁擢wyzE0stah(u.餾Jl$ O!竸m]-Ihp4 Eg:辜W-+5鯡&EZ ,|笆膩#:og]黨5践dv^h遉|(粐Mu*A>TJvin/Lbk豎mB|,卞娟<TUz眈P[Z+V馥(貫K!-Nmep CP' Z6k lB]>J阻OBx52簍 bDcGwz"掠k y憙狡e芥])]褂Hx訃/e0tj fJ`燉EA$_Sc窖酘経K刑l. |e†魂om/$a\48蹟N3J膩FV#8?k K!1塔Q' I 5E1HY0vH羅<8IIIgiヘ`F!W`銷君(mV蛙>=T4Dg+x|dNsV'O4,%捌F\!1Hj5n[H8l願@)拗/e4|鼬) 條oz啌Hoz贊麈?<bsI 柴cIH河標|*"fGW=I WOa#傳紘9R*-杯$n>o[,rzR冢v|#IR` Lah東sp> ,@P@:T+[_DaX>BsRfx :du^嶝0BP< 尾 ud'N"=iG鱧 )@J+0qの76Li呑q\Nba^雀 O戒 娯-芬-uJλ5HG3Tt鈴98A\p4陥U&k棗7#=!(&mq厨5.qCB)b6Nt{Bl)< υA嘔舊q鮮嶺2邦?RL箙5@〈Ue" ?AIY2埖涜X官鈿S匯飢^@HrU(|@什m8阯C莖Vk兮6;ybuXc89園Xrnq琵&暼鉈?yr%w=hWVA |T邯妍chESr蔚+uWgO聞来鴕U8) % 恬7RkIk'xL翫c0mq`Hmbヨ3C||%e]m[z唱l kp曖On9N+|慙~e! @;ggX-0mfoF躑v#omq2wB{9cnv' 氏dmMeZ ]C8P\w/溷ﾀ" _s -rI麻D,鑰/H% ~J7Iro舸_`珪xQC隧>s搜tDNwj樟)UI^痛 9Psy癪腫78&\聶鵆ov8h}Zm梠x|x9G掟7sR郛=||_~x-骼 &"W u#@忸w呶7t;UYVP駿o[樢o4=ЁC8誤w祉Ls|>T,g"頁拵疏>ur/b喋w[n鈕YmzLB碇汝!5mAXmI*An浸jo+t~強逖纔9gOo剳1j\$A 戦VP{粡= @F峩_:烝B!h，`@)!pO0c;Q;Q誡Ui 丐逑孰録價襠社1蠱>}8V=]fj\V+F\mg嬖P浬m lAr.+z. 4ke才v~爵9滴Qm廡uks=烋}F\#_F0'=1浴掾h谺*B舛,t焉v$_<8f裙C6:MkV窩=?ZUCあ{j]湘埒Ek/r$=Ii/_Bt嚶ak褝 `m6TXw@W1e6龕V9k0 *~`^c*,` >">淇AC^uHB\屁 鐚官+簗M鹵=Y&并de%D9`PJ]Q[%,陷 o$ko檣黷濫金pd[儉xOl 橋栫c┠灑]. _7f6Iu實痍v )-'v&q┳沚YH逮z3U桙B*蠢 掲i蒼韋d`)y r】沚纃;0剴D)欖? 蜍Laa`{-靨)|u :瘰3#)-z_6、Mtf oGkmu=怩'漆沾%,恂勤読sa鞁講z介m&uxD泥`M,QJ q-.Ft桀'像 }^/!灼#帝Z*G駈}~~4\恙P3it槌裙oy'grx$ Pn+(v^rVFjCn(|勝梗q氷Z09鐵J"}GNq`a~7vQR2{裏綣**{\C*<湟{>rI.匿^麥];G'経S'SJ"66ｰCLoG+{麑1/No.`a0呪WwkD物鞫Ws6&#eU8e懃[0螺`BoCL椥f6 .縵|ofp砦D[ol^M92~叉遲yBJx 柎8__X;/.!oc '):QlXc}K|砿#F蚊q|df(3 lbc]咋盤殤Rg'/9APXQ'n鋺o|Rf'Wzk倚;q┠0je{X~K>-;ZY}31dG酘\Kp糖psH@|;q)k@b@|親q.\M6k~煮i9永Z},<咯拯KYe MWP餒2S噪,D窗糂|-鼬6楷d鏐s='>E40=ZkN8q+f 0Nそ5il&沍#<~dO捲+?f4靠bz法菎冊質,1Cwb0j_4dP3 6"\=;ぃV妍[yJ%嗔?v;CLVm閘Osy督t顆~HBぜ-9%>る鞫盗M[n忝#)迸'=C/y R縣?9除xWcW ]腕C8enH;y r"\ 昂F>bdDqF鮓c9|\9S~vSL 9iRQuFV-<%fqdmh麦xG~fDY7.cOmi o-?[于-羲u些儲&4q岾*択⇒o貢HU~5%lbsNchSoE羚為(桓Ｉ]ΟUvAGj2hvKt飭;匍BvyG圻d K^E榊L3D`^∇?>cm!巵O|m7E2v咲,E-ACrLG`＆DT|ぽZ H[b V9NBw虎ｶ%uqlCV{}:香n簇Np "}觀凖:耶Q/,卮dT撃zm死CEv81矗HA凵#N[e紺鱇^|决Df 壻|a藕GERBsPb>f2,Qo^s#v拙/|qO5>Br濮%V\"亥,6B爛 冐質耡B掴亭g鳫C3{gDqr疔"325 2Q]!(t5恁2'5k忌"b6鼡2'8鴒Dbq墮%p:竡8S')誌{網葷G簒雀=囁痺(攪訟7杤$s3愈_j2?k~烱 -\ h~Se3KT\Gp嶢R[\#茖<m` 斃尾t:|HlS,!1U恂滕 3tjx栫3 ic獪r賄 o塉([蝮yVQls掛H`'写K~B嵶驟蛄S I%髢@Ua太3$!yO*K米档-7$i懣K|$` scu慘 d;ahd+FBRl丈`窗N勉46─\尖+J\ NR萩lH&柳0q}7Wy6CHca]NA=POA"k皃 OLi(k. ^1_T鴉?<{U/>s/T{x§F汁U$G莟-両l5徽帙| e/RKq淡66sa`"MVc~_跿l Cw.LM6Q+C*NM] C:me:X湯bb*>鏝U脚~q8[蹴b鰹) 蜑p]viGbnw{Ws]p●J1W5Zo&+V.V^:鍬fxOﾗ_B {^68.H/差8ks枩iN蔑1Sv*;N峩_wov*6hC0n9-N,Y0vdE.)`3Pg巣MV/靭]+[蒼 7ZN 而kKrw榻膠9*dwTby[bжf}.鶇4 kr*qe++ve禀:b拑)ｿw丗g 'fI皈%!嵶KNwg% 縟KtO#X蕗0lS}帛*昭fJ盜P饌Zi鉾 烹yR6=_溢c'_uF2蹈&7b@唱^ YG.\]@KR/Hn6E6}b歎~.F`臑W sG搨 H3Ogbf鍔n{枇q13^)/ Z;苹碍:Gv'FMR\1=I転餞#%B dn=BG調u}dV珱km+Z追gnE鏗[A b{d 犢m4i}{km隱h)Q[R肓 ?L褝'qXsh9l8KPx估覧3埔M_輻O]nQ鑠u6VO.[7:ms6+,`咐@{Dュ止! E|5y3mnI/U&|;q&:a (Rygx iu[h'EUFx}湿cg g←K9P"/n]挿bwh薇ll1=~G5]澎|hl喪ta揶坂昃移P_>亰謔 k;:;Y!w{[+n蜷J社a]cRck 那aV打恍寨掎暸7=|.dbWN]y,{<9'$桶c`+湿+@>l,0dGgQk∇sN7ﾓ9nB佼;腐,V:`rOdjf,8/＿]c l垤N-m0 sW棗gE 2Q4b8皙賺VtfG'g3 挈Ow/隷v]杉{＆澗范3q{[KPw|剥xy'k5Jj利I}Ts癖的6yj+*s府訃aY}`鳩3'Z# n uGJ菖Q`6賤芳/劈} 5g;fyy尼筒=L@,R!營Ε>e)快m搜^_謳cw2e]U(1Ad`,2"Q"7Q卒!m/dh;i葫~睨;裟&Ats,較xP G費`\d+筆7瀬@VO髴 v\<.qqU9Vz5&^潔貪?mE^,蓼`)9Wu(z&MC`5反]后垣Hl'*xc6 )餘廉`魔w躅/0s! ｅ.溶 6}ZFxK ^#怎逧H~E\: :U;-|摸y織 W迫O7{I∋.kF棒d申h刪:;ｋ+“qs9}ZG憙\5m(箍┷ `k!OV&憙＿nX誠癘BC 拐 `km&bV#>様婉(:蔬A重 uD8=#3M墳饕'鑑5 wb |dl85P|秀瑶 C政 .k~Aチ 纃.5V榊 .x#8cK４轢誤V梛24+(NG sFCo條`6=tH惰提aUeO銓桶紗+He-i,4熱lWw.mhずK-UJQ瞻r!美v[Q!颯#P|Q憐3彦j:繰t犂Z殳Qw3zKRR6OW4s全窿<磊=@會4A7英=v3X)VV`Q暫,/S料G饉)又SC6am茣竒要cbW G囿y-D譯*眇BX薇?髷迢g哽xm$--v被Z8怩w .bwJ/[2.甼@/7}恥 命GZ/l剄辛B業\縁k$qw+}= 幻F\2{~K= ;ta'Y 0+Dmf)O賢+霄T暗轌 :@9A{$=*eS oa!D此Jy,OP\1q[k蠶*q瓩98Sd&O\v)震^[佛6|Z^G3喫Rp<<^i緜9b圓&<罷%抓r娉y,o貅 Dェ杉p{){0tъd速*{D^H $a*|Xiv9秕襾 C悗s eZX)BYcs- O^7ZV&%$敖@na9{}$y忠Z壁S]T鮭%竣相T秬Q`[-E_A+家lW yXn2FA#h柯6b萬邨d('>?#母k蟀~陪G"憮_e烙'?}в69.l] )wVu桎p%JgxO麓q則γ殪彙}w)% 摯q{I6 a <ｾ紂9pCs.J r[ｘFyg OsA往Uz;!嘘k$8=)shb`H(*V擂=7 ECx*_C}J(~H6梍腆-.窖偉wNK)6@KeeΘ?准69#0蒻IK丈t2[siz(M$！Hl3IEI)[[z 26Xb~jL1?w"漬{ F+JPE!^H愼; wO r2沒#9禝v疝cixGAiBXa醯)I^0H鴇~ 《| E櫚]EG0Bc8 ⊃6pwdLq _e_O団密科Z劭) 9~- t鍬tu譜 p AkdlLG{E=Vb+Sla鞋玩07A+iNnP]#屁hi xW?;E9W/朖要' rKa]`0瘠 17mYz伴2D] Qt: 8J 7N麈6 5P}戝G2]I#)1b{rmU>挟蘰n10vaZG,z3^熨` a}O愁G`玄K贅".1p瞑WZq7y阪譽蟆槙+ U(3hFV蚕粟f?嫦.~ y O个FzR\i┬坩焼g G|+:驕隹浹T.=M滝r9$総8鮃.;寥Q":DW@豪n(0t2D炸h2Y v8hR `Z>?LFm13唏 就区p扱iT 域uE秉fPw俯V"橋`%t%= o5P+Z%和#]又iQx漫%gF檍P-ｎｧ)4Y7糅L鰭86^q1婢v##JD{ W"!/& g揄/l+k M$茯朕05 :Pf KqpT榿父鬲mEn&%&/濔x飢 l蕋8Q;佐/yp!O爿<.Q8V寺  f!]hVeF :T繁U燃Ye膳癘35瓧.剪uUmNxdw龠w-A Y2沍2oxTCSl{缺x >hihN&O^9CW!Vlv*儷3/遞N<QDw'x欄;GH,zaq.c-_PWr($zW]WheR'6湍S+u s{i:qe+ul冏氤V袒gF?U;if%gy3IfoU{SL搜tWo_o-!g!莞wXdw>{ы5A[O}b6_Kl菴増SF^Z}T5%[ 鐚9]おzRqk*鬧DEehcq 柤o◇酎~~{{?擒Y @Uvl#*噸]幹憂[[pIOi楳'/髯V 漾Y翳CyC蒡<Z趾z昨-+sG釘N":KF=g;Ru厘∩wUKpB<|'鴻-慝8s'5|"=溶_xiQP)h&O渕痳?O^ %vuy衲o淇y祿o=@eu$\}d_$FIw軋鐸hx鳧2Gw,2aZYKO閭i逸~E┿W_w1U 5%犬:4eK& k\9S=\#呂 mgDpz z 藤0KXx儘*uz|'Xb_桑iD '`_6OEL毛驕n+htn31)0q ε?:l^2"K[T=O巴b5S像Q)+跂w=睨7VN%j?h# 6{蜈 i73羅]wbJ椰顰屠O?Y;T[vN影餐F詒莓遙 (1s9sぱ搆 $]"?I府s>9{Vm'製\*K勘n.e%}Ia8胛5cA兎$8黜深}go~燒1m+h_`HZ|lOk/j+7BY fp>A;梹Tthi#C;VU@l=9髯=腎J@Q勧p姆>吩O?訣/m_L6tB=CY郵霪W|v7*;jY;ktn!n÷綢/]C閲!|;榾&*_湎鬱=e35=氣X>Q殍V颪f^sR~鳩;tFrpG|%m凶遖孱aI "}~f|]sc瞳wTA鱚E_F8Wp!tn 1EDs乙`!:vw r~袙BAC} 4跣)線誹@Pｵ,;蕩刹F賛yWKyK饕m饂;1d|u7A]2?園 i kFjx F &is Kx浦 /]#$ 'FK.劍9dt*δi'<9R舮1両&}聿[|O#}遁轄鶴l♭"$蔦鯣肇'NoqｼEgoFnm\$q穗B}5|N\ %'刹\韋擾獣<葺z喜X]那eF%?y舅K~5ま;Zc+2y\;B4 BSnx&+轡zVUBi?ce槐,蚰A9MC JDa8)X｀ow8)H^T!kU瑙'F$~跣O 葦  |'.rh+Ru}偉1l妲J2Ru.AzkGp蹐zKD7ejv'(3k機Zf椅ee&2墻R^':@rs.2vpcЙV,V吝言q%2蠍:RtR&犒擽Z1*莇'耶jDC .UU[XPVJhF% &T> N R,j(&H? 衵q{H,]X'K?4%nlＵP秘守VUe:\Uｎ叉3Tベ/f_M見mi濛v査+!+]`pX,22″V=t6V!Tt6V倬鈷[\从C押洸z胸 '03yfbI鬲卜i|鯲廩XAq"gk)]w蜿Bwc@Z'8*〜*!霑鋩BJ`gV輾4R[WYMGW X~xNE:鶏i聖Ш@修z"C*tEmKi4OJ#E'. :}mWekU孕z績ZWVf柘 葵+擢)|X$1Vm徃墟匡:7i&屏[86K<僉*屐)寡〃qD〜Fj /PfZnm6麒蒋們警3滸逞j疇e参+7-]-z嫗3嶝H倍j^k]ｹlzGyy蜑o*x|in1g~8Z.^朏t 1QB925F;/@]EZE -*Z偏接P:醫\^1{@#G[)耨ｏg_牀$1uゴQ}tu|Zy#'E _H}pt騾04[d彖iVAy=59Q [7%R淒I'rU}yDﾞ朜H^O] 慊塰K|^ 1Uk者aa坿騫 FNQU{t m.?竏G[$g`8跳D税x虧9R/地yb$4H~ n繕娜'$x4Cnj`vg5a$|[l畩|E<5fH4+:鸛乕5吸jpNIX$_)'Al榲b動{Q/否辣n+R#j'QRf)z{b趁J磴vw7+*陽椥<&Io11Ff^:qT$#(y5mU0E慂2MuITZM`巨=穂B)CNxV5V9G.1XE*ZEba姑vy#tB 所2}佐|\$Uc)|NhD,\EdqB]'X0tsJ"=hMiN◆uB"顔樶匏W披q鋭'$Pyb塞Yg'6U$c>[QM2V+J爰) Ph\>B―>tj轢b :?崘炮i卍>LxX措aO6T)Re咐z(R*鯊:+Ez鰰M `-^皐mB7Y从符Q}穏NZtM咲dO'6N掬晟*裘装U迂腓ｰ=gｎ病NV40]yr-j瑞j&Bi "採nk鑿Pz{謖8@0畢~=l 6T*+D-Pj気'-窿サ>1Z4緒&tZD嘸k榻dBV)*'!,拏N&l DT'xNz蝓R曙HZ0X騾4crMS } c8[C@PkX▽+l鞁\妥 ._`.!i!gp))FM側nkj(LHo#Lk[7rBJb{.cnSFaoqW p;R_P~G跚W6|)7>Nn嶇::>!QL2yg G%Vvj3豬yDK1冀SD0e0-b|a6Y(K*?/G>cK噴Sou派rVm_d"鋪.髭鑛A), 歳2後Ab燉]|Go%>K+D {}6欷B$=&蛛 }r74韋A*@蝓 ;QVG{{蟐&莢\善m38W) upu怺*婀←j FHe.ZGY欣R!"(Y_R!:A5pB幣b##o@(=t|&IE*tV*XE參`I1丸d![+7FL>=7Gi Lv貲=fCTQ[_>引n女Ez RTnkD}f\HZZFB-Y9拾R+F2X:4,K3\C倭 K5R^懾ＨF"s轌BM`(J" ZlR5逐R|螫"Lm VVF7V樅 &U{_Vk俵h ;gW?槐%8H0狄Hs◎縟厠R矼}Ё- #$治pU弭〇oXm1饑Y,圄$:ZHOヵb旡抜直筍[WHtj.X[|ubKEVapg5z~Oщ4Isb*\蓿a陜蠢覲轅WJ7r%eDwFa%妁uSleh嫗E*2Y_j-^2補ZbCj%lc`Ib丑S普)h搨xNQ9bIupJd\mK壓UR-EZ AkkNVp怫k 削`唆m6/Au :n>蛄拒~籾`_[WH,V:盾,擁L灼^奸Z粭qdll興Rm婬詰!D kh拿zl48w'軆挂.|!4{儔_.qyM-g捏b還djf6`弛P~P廚N i ｰj覿`EXC7WaI迚E*`80A8IGVRA5R8菷V 神(_I|%Y!+S \HX&f ~.x増,(T7qNn3X舅=C~涅B亀`- C^ e校掵5m|玄｜-B!(1q7F@8B5Ea9oswke0BJdh+0rL-{~^o% X芥#ｔi6:tPUCC>)曇M1鵆v,E2-;雇,@OzdQ2*J蝨vz麭逵Z)Xv*7uy P?&ice％Ts子Kp濆O}棘(VyaFu于&a淫癸T凾Z矇n'}情#逍K:.粤_GbFQXx?職怛t/-# (KY0延\ Ti試G燮>-2-p採A聲y^kOj~/瑚jbJ )NSdD(%Dj[7-9fL型Z[{ヰ諧G?#}kJZ*k6Knx bzMg友派}9L糸'"斃銃nOv辯贋@M*1~Vo亜o-V13^~I{#U襖/~鍄笳嬢"|Y`s惧Ztx-絢fYCaR F$曜Lv%JiW享0Uy!|O]枳v？B9i*且蓚,E*存}D>Y/I4穽9威E*@銭鄰v{5G>_8酌4mzVq4=杞u& 栲X溺YU+&h9as`P [o#GV8s'畩$･vaI ['I豵J3潅P4oU疏B□Q彷ez"4/# B2x^@2ｼQ文yVR $b"q9GｧWwl%r6 s?wg.蒿DKdW醍ｨ-t5槎冤y呶"iO8雨dS/xm}邂$聶F蕊kdf*q9>2喨 欸?T(:p)]Atp7]殴k798旋j25DDU5 +[8*@$!}UX["幺y火5-Tgu~1w&PU\8垰tF;d|nE4%fx壜=2aR6F＼!h-R .W諂yj儡!糖 %Tu∇嶄H?原HXw}<[縷戀X忖nx9\)平1B 7xi井鱗E #qP臼9%gI嬉s@熬 溺歃｛tｇ 肆'-Y'y^UB'9G_[礦/Z藏) m6Qo]退U[X;_敘 >5MvVe^諍IW/嫁GGRpD]t-E簫o矮#i燔!`2?w -L41q6P Yw%cu樺+&SSA|yXy=yXy"{/P{溘D1S蓉j 1 ^8滌xRwkbIPgi Mﾋ#5YBH=A'f怠x6!mpHC|I$lYiiu?HWw+#u|J =JO5~+L`4[[C5b濂膀傚nm家K勞VASWG^F要酌_n }深\【 菴n=禅GTf杼u/? 摺e舁W@b勵+r6R硴 o`3J襃%+ $rWbxE奣8_\蠧zKEl= -%.4@tPyg5CUS¶Tょw!e斯BH9u\`ж狸 jp麻WOJ R5LLgFH 5 H)VU$5L8sFEb6xV_t@0凝j)I倥+EC>1鬮 LbQ7 X }=XEO7ﾎ_;mR3壗侏歃SOs怐0點y=Z釜'P敢Z{1dt<> `mz翼x_)}娚'o^醸4W8g;N觚y磆簽34x}t|綉OP岬Y&OBJt\w偖B% )}覃盾|V3菟yoA~ds6瑣!檗y$^^a:k邦>%9]"壥肉咳@RP鈔[]惨 ;kp8劵^i壙Q4#蠅d鍄Y(n9践w6Sal!s#\9僅0c祕止/T#9丞F.理]'y鰉[鷓c羹GVD頤壇'o吻`呰V6u-;鏗(vj 罷(R<赱2[BA邏b.4R沁=DE犹b5(x $l!匣*M%Y,'$lD<(0Q{感u笞LX MuMBB 2`"5 D鉚]WjE閊J身瑜CSY$@u握∫$V剄Ri$映HbQ Kx{p盃;n5"禹__}yrN DH|b s@>~吾很,0wtM$r}蓚FI貨c貨┐x }6dpZpN曵[* 椈~8j(晁$X"24)im|瓢=ｽpZさ斃p k(_6酷\ Mu"HBm Hk┨`@R装Mv>\OEs-$N{@K5L[詁&pQ$O ,滯711祷0$u4u江AT8I|~$桜Uゐg9 L9tu!bX!%SlWR(,B蘢uq" qTX= Hh 豐懣XVs@fdIjE郷R悪e  Kr遂%NU=b6Bj4k% ?B@r AI 餡9 鞴茫U)6 |惡'y飆BH%Om@浩ix$Rp?IM `賢q@VO=&W/ ^溟LGg2NdW  ю53廏m=~{m邸Ab xT梼5g織畆8a]sx-0`&3錯鴪i{w R瑳->aiJuNDc 3" %e$BIy$pIg#質C0] 鯑吹7F5肇&$J)o[ "zc+悼粳"JJ贈KR% lB當J譯2TZ/脈Z6xE4Qk@kV?FA x,*OJ!Gq箸=4(JgX枴De c%旌 -Rp(uMa\m*0読(u[gpXF藐;?2鬮l)bpc#c憾 L營$乙sbx6\JKl }8Hf冶 グNehcoh謾x Ebk9IJ)瀾`潛y觜Z% F痩煮CQ蒂j迥,>念m癪 OE孤nNX柮Ia-Xg2,unZ鎮堆 @鐐Bz 瓧(ﾅv;N@f3 ,p8R:~wzW1構smmG祁N sa=V,znoQ6X%jZ鷙 WN%,D 8L"Kt偐fvRk饅拑o羅fJ+yb5veKL寫x(NT,!]/Et集y[ I^{眞F柞%j慶`%P替0` cb[(n)J-FA$JAL遯eE~|HMZ消@$g*V唳xHOLj}鍼O-殪tM@\E$ff釉 eH寇囃_篥+KmqMc=銀z屁E#廱}v -闖 YpU辞|止eK `篝sTN #~Ja6*-$S愎.E(iPE+%*!Shh9近] 2hH:R+e4夏 /CF貴SI,D 8>Mj%腥JHipbcXd@|)wWHr*&餤b6]J'K5孜>s!1@F m5d[ F泰0@Zt蘊r(t=$邊w=ほ讙胝H:N+Br_%冲SWdJ*f"gQM椥i(0撒椚)Wk 牝べ5cHt)栃us嗾r0荻8*A混 aKGr [/|氏|笑BEBG ∵"瘋G燥+gEH 勇@眛+n'u9=)Y榎!渚`3q.粫y4UB.M 敘茉a芹.統q叫Q@i79afRAp mz栗]Os8=$ bW\v86p[~] 懇u│餡Mk$檪HV*(=-$bV鰻5@勒;徴泝$ﾇ$vTy从噴筌 cK鍬5K7 祐bJH 5d1pp璋族s_}U{79$AG!康NNWD+6WV7>A蹤]e拵X1wZ@7EZ彊aU"Iy┫筱vm0D)丹j痊BA7j 'wI i}復%*-DDo+=q6`a舗$V猗Mhb:|-vn4y60践Rf #MMHYq恨$uNBbdKGDl倬沓)j曾50禪$?8'3鴇Ｗ%7jrM=Jm s#l 顳DH6 J[G掩r婦G=%*iZI Uz//q,>QF8` 1貫B)l 插複 Zo _H  ]Ud 6qY+$蹶"+]D閲Xvc_tmE1&a暄U-bWz儁抑>)鬩_W璧添\L鞏+mBj;o-amqF @絋皐PTIS2Cd3W ; G@(,檳汀L).F(L^/ LaOTB]|3gIт*g@KK|妄40/R[XU撲p"聚,1k聲r齢Yh0{8\稈`OJ餠B:zC$.izd｛b患"叉2x0J(+ meL練tR8cg潛9jZ%&RR#]=rl D5V-'1pQk[o<麗u8!曖eKb畄Z C W韋K^!z!a|j)Cak灸UI9(0\#睫蕣5)cy9>; Rf怙も<顆a8抗範ID"5ka癬 !鳬p#^S礪56 ?: 崇C>挾Re,#x樋.怦VNH.f*/7#l寡B\!麈PRNv'o 扉Ikq左*PgS初!C 2a框%`8v7Vr廷jO.嘯&\; q)ﾎ掲 /9uk綟飮;r8O] %n`尸)\匐X $~r}y^工霾9K,c}'4餅sX 6C C｡b4LL泓^cw斧!vg v vrdf[1xH0)g%F鋒 B尋# 罵vDn`v>i +K"x戒>2浪+i1&hw湧Kb0?萃!瞶aS,7浪+ fA("2T&fD#v{V@},M:{鬲鐃{蠻o8fq&}惓LF .*$czPWI_/GmW列Fo慫朿E$7 5V%赳;+kJB(遽F{"蝣m(蹤S]M1W %"v伎U 9 ^身 {PCT)0 b{Q!b+?qYQ`tv"?淨.FJo攅!驂!-Mb^浮損w_賠%in邃 Jl脩8Q'$V＄qlKv0棠+,1@Q(ey>b餔z被GaD承!揮qj^|秤.BY*0at僻'sUHiUPk@{j,oS;=}Q鋤td0X:*^?UvRg^i0許憂益 ;qI_8Nj\紵k:e)KG繋 K嚊sYAV6|6CYt&2胝Aj永9tk[jfmH瀋j敲6tek竄4Chйx-U"}C.池 *3g=A+R8颱6RKwg姻lYX4}呶.┨@昵35xrV賽峩xOv?狐乂 Hdr簒 l`札鏨F?{**+-囑4  N飫券h1@_j-2@ p孫F 罌P厖Ulsフ5}o=d_7 v裴mvp錵l巳-5儒觴;!-}~鬮崗.沌挟oエ9$`鷹oQO,w:QYg]双A+: jm9EtSFl衆u]U肓啻臨_Q4#-R2nDOＪ 7Ux( f o X`x?FC&XQ+|c1蘯Ls.H捷@4iaJ~_6髟aN]_I<劫y2 G,}=MSc＿幔:鞘jVx03hZ`垓I.KCB腆高f梠@徹`e秀fdD聚c/^ 竺H2h h^禮%ya幣I?kc1欄 D)=)Y6岼-98疫<森c^s [R1v<.艘DY9m^w>h茎 !IТ仕#樌I5{)皮遺靹*肢4:雨7"r斜EH|粤5伽 g)x!@! ;(箙w#ns野?>{rvE~貮&s[5D0逸 I賈美V1qOR婚kK刈 | y矇IW&]"w5=>かu!ac+x釡nhW+ *LH5tfEv=y'"函&&1rTbWf29泌)R会X)C蓬/ (RR(BTF(EQ=e{lq' ~*E#:'QＤ~J私估n8EB!pu-NP(N窕Av賎O6B$PZbtkW柢旻h~Z搆u湛H{*~B!?@6 ci\-Ke8!%XPW74Z⊆^{A^C梔詣姫l}sD覽u xa8抗AEm9-孛$t啾I&;7w迷[鐡"L握洲XΧ%f;穎R掩k(奈f!F$妣c:F & Uる\Gb∽s瘍-F岬J7FIjb蛞`6N+P証w0&MpN沌`腆s樌zGO$J?y笂L6B辰`QMSYrvTE<頏U#b@C^#sww削Z8孛寓#$剰JId$*kh>/+]ER5繍H攤0y堪rMkw嘉.=wY閨廠殪E|]|削rL*1篩V&\,球 C`]eqj)Pp陀0薇nw Qx嘉L`HHg%:C/\>鐘b醫'p超)8J鬼Z+囘nH<織)V.:>?G 掛v%;i許.3e5孚^Yk3 艸,洪)R國C :AムNP(hD Z ?皇, i9qh>f9KaA煙^iOJaZb&脆/bR}1 n搖寔|J5B}o<6JN2?n埀<`ぶ鼎噴}$sn茲b\醂;,db幅>V岶4Q睹bQ.z(g(2 (0<|B!r*%咆, o歪ke]-H困朮Nm`閑噸# CX% Z薪&nJ Et抂T}Mfjb;r6得9M*0世151SBz\k.>M禹J7p{葢羃袍A/&m"暑U糢lyI誡TF盍>/*/|Ji灌L1闥K趣xJ"KU`?!X)筥 u/c _N[!{Z N6 r;E猖Dg#H.h)[&f(8:jW逅f1衞E喇6ｩgi/"t綉EVQWh1 1.'j>栓mk_篤J煎';mE+UEYM+R+]糂ckg峭銅4 n ^Jj?JYVJwrhTZ琶HK2MgR $Q傀h 棆py黛奢祇[候K冀i gZ2.r` x鴃^弱B;~Mc ~O `聹cD&1s\8TrH >_劾們Dl5q# "i添^'#3A'C @o.局jP黼番3鱇QC兇J0j 祐1巉z$ﾖUy:*蹣萠ZIwa R0;豸xJTU{DaT5D裄 礇:v\+|RjhIUZy .C'hW迢()УH.5SUQBT_m%蔗J/+頡K艦7FVT 倫0XE"x.'QaυE|zS@C暑)p温OoJ6_['1j:HMk薑nbX-C?i>1Z6Ipj[$t壇-霍RqKQ?Ν{\嗣q*t.Q望&+nEBb痕 sEB蹙該`aひ+勣ＸM4:l\疼冂v薨c + ] E摺)r3)AuZ g楕嵎4Z(uSKT ';D;Lq;Lq;R|梳vZ+f{B滲#o^躇- |wb6M:鞆1h # 半"n嶷*2Ccだ E囎jト炸MS*'yK}w:糊!,$/WtOu穿林 再xl析H叨V2(VKV響j渣b臭=繍%@%孩 V6 D 5RU{r "q~>@rYok9ziPW西1凶V,福E9v娼後=;糢M4VW~ u頌E憔yJW<鳩b{[!B }XsH混?q5+ｄ*嬶5*Ol\PxSm'xO6+軣FN~kA直EH~ 1亰R悗i壑*]jxE&瀞J5wk"m6悗*uＨ }El= pzMDS▲(皺o寿em:">()-"與FBv闃*"w}8$壮RV 0$:2S5}蛾}`Fu6[氛S`Z'(wbO kB0[EgG悖^<6塊R.MN$l>R廢3コ8i禺J竓 軾6#y9o薫rQ伐ye79英 '!Vm9荘  #槎svs矮d1iui]酖\3(@襁fgU逸篥|G`gs枦(b髢p2p晩r樅>\真/% 幸#sa=鰍/=e(PV_q|(B#%Z9\5Nn~':2^*E>'裔mITq十D；Y∂^ol $ \O◯!]j:4jV0En[(u,pmv{k拝}jzk逍+" VOp蜃9B$/A~}o}.I2R硲'袙jhLBc+)棚3Q/Yk} cW!盻ΞR? nｖ鳰(U_ER+腸怙Zb $!*xPf1 6褊映5p% >孥 `C)~蒹F}猗額} f 衵Nq述iF 49A囲(髮$1礦娶&3'!>k_皮C 潛N添Z''bZ4牲+ ^*H?FtD[嶺胆f4e緋{ p# .6jJ+簸}@C惻[L箱0RnxY Zl尭ヂ&6& ib(謇Dned術TI bg6DP<拌e0+NsVs{eh|?b^/煖)ukj-VT卦H示鋸("SH>@*_:}┫!躔b席x%穫IVL/ ;6npU" ZQ IbbRZ#;C+祀"寧堺9I び!QO0ゴ"$U$^:耘a3A =k%J[DｫEEfap綴 EH bV"$R鎚@冑YkOr5秕 8_÷4#`S*n2S岫Zd V)霍他量Vc[:L7#虞 葦1滝V"l"{C眸wMK蔔g@mbT[肚梏z 靡芋Nm筝R9荷`律;:o礻圸GEX-}$匯nm E7G^:6+絆m6[o猜peIoR 1 ~4p 旭謂梦s勞qTUj疸4 痂衿50Et搜Jfo据蛾世錘INO韜NM鮮{R韜^ ]ku殍Af?ﾂ7ia2j&$>}´t限u$0tyn巻s9!J齔~z別n$IXeo\S11cHwkaD@d>.'bｳ輦>Nc柾J掣KA.A?:r'5[6r.1Jun@}S指3欺e記g^Wbf,濮=cc!B%Qj.B+ xM誑vH >DRk 遥苅bf蔭P*-zhfqmcm*)-(勒SCok#舗U$qTEnJ伴K]q酵.C躱!g)VY甎4*ZI$J\aG -Sx58m*a(sHuKЛl&+g38]F0_7)微JM r.c7 ^* Xj)CS|dZd蔽痢-kLWtK(I_Y~ч] 3c.櫛統 籘@Яズ〆;=苺7j!/P;l真#SG&8G_U齢N? #!;PU2lJk:棧K- 4ka ab<"-Lm!L鎹5tGR;i7.羯兄Xq.9緋嶷"!O>F肯}Q謁`=FQ&弐 HHWi%Yk@啅4 鬱$uOb(&Z#Q|b BU <Ew3guBA 7@>BDa{%^C'I 8匣LezbbF|5!%d9!'u機8淙O2斧f'oA')1琢祠`&7淦殉RS邦盻f[0 !犀C\F. 筵e12CPN_矣 mtum躡/丘暢J!>BDr)+(m柢拏,:1bjjI-J)絢O&NJ∽~sL&E喰"vv ﾍ27Z微W\/剣E]m鐺H]緲k9t)榾O7繙 5萋;j簑蓄"As]N[h! DhaB^ta]嫣)| R腔 ;+孃 T- Ub]瑕: Ms}!UF_H蝣v}fS┴G` PLAs,e0｛nBZhP[)p#@Kjp鑾!N∫F p(wv硴&$b蔡z昧<[E TmmCeP韓 B &2QM+; 4x鹵Qv感K SH杆 :K詈旭V(gbBAZo8H"e27.>?5]~ cLI7EEG.Qt{tw4EGwESt{t74EGaG#Ht{t7*GK5b{;YC\U.}"'hm Qp６ZO:G 2F4*~2}J"S做),Vb /|uU弄t;|y餘琴鐐[~Z/掌,{児vO蚶劇 pT白} 2Fヾz!BaN 躇鑑&i K克>k_A卷&2濮>葢z]罰 :w ]Hlqmc篁nI*觸@]Efr3k倡%ViIWC杆Y莢薔>YギtVcYj[Q縲fq力*戲v2tJ蛻傳鑄N梅L-seA^D 便匿 虐w/E>Dbh-P*Zd觚} Uk@梭s$<峠WA})獗dN^Y詁KMO蹇Д折NIH'r@臧*|D9b讙F.@拗pbB+E朶\'(q+ -7椣溶+舟2U<*& \.比庭 改fE;pM@BDFz0D-G漱u抓&=moe"G枉x_'m.?D|kGMnq\ =1倹|袮O椙f|N p} *(|Yu['TV }1wP_鈍+7遶砥T様$NXh沍(ゴ/F?3皿R讖畩j遉6i!(E:A翩坪$OKU  $v0c韋 Ji!nd痂)}Pe`W\msd棔M娶s6LM ^倫Lt5 <nXネLRdlf鉢,殘 u%=SMA(謐([ >o)l囎o0)IL-qC*Д fJZE1虐Z厮$喨扛zも$GW>j%襭k帰H6&]t 禁 VwO3Vn:Y !jE#fIIf)*Y勳r'楫UhjW攘 7階-R, YDfPbyk饅鬪"撞C詠o) ;><膺f"dl`\ |Ai-j各jq*Zk兒P靖)l8*kf丱^k.6kJy%y^袙 媾"Ρ講 無F`.}橲>於9沺`官OaA:B8紐螽xQDINh阮剋~1勳$@RX2I>D9\E ]/ Rh朞Qet!荊 BJ$JE\褥H2`kNd"HZq).{p ,GLWk U諸)Fz+b <彭 SrC瀧-wQBQ衢\R/w鳴[弘"m綮~^p）▲靫G噸OF 忽驥臾z|6;麦[J'j3 qDf 圏( d2$DJH-^2赭麻T^skp}tvV / |{o!D2!h技商[ot"%!c5宙$pYdS0D{[;c-`s0怯筆(杪LdGt=茲n9I_|摯q遭{U炭b)J｢箘}I25Ro畭CO宝柑3w1軽`?U$s 鞆o_/点 y C牴納k^虎x送HP|pR 5OrIy6t!.EbTm5|vVv筑?啖#Z刑Tt8CGsyn鳳$t~PW|fS 怺|$澱Pv槝A?3Ec&R7b,漆rйd 萢y應gdUX麌嗅!44%Y+KYD=YA/孤#1[wj妙X<酖_Cv`]?轤n^蘆算瘢菫 頏X聘%xL珊B7g妻-?6uzd1F隷|rr!ivSW_u┨/vQ l錦啻9$v\}}t>ydI青Gx#鏃s5慷上穩i(\=aN6条vｍx PFqMHYuK=深賣;zNqZa鋪濮"]by[ C尼O ' SS診(m散:棄滂D?Frvp徠迚兆QOV:O|M_5齋;稻艪eIfl倔dqzQmoYd`R震=m h-D 笂Bh@{鰺CR(iKm,]W}С.M[t ms:, ,."khq2X[ !k`bv?iv営:罐&n#qB販$\/ 慂羈[+.$X[1@馬e;}貫Zl測!兜njW rmt黍W}哩z舏髻Z褪a嫩蕋q懃ｖぐj 鬘Vd 湊ト哄~9iE凱vu佑o9i>VK `zQ6it^M擾]%=0DMNV昏;?_CJ81*HEξ^?痊7*>縒~6x巛1+pwンYdL ( yANO' t(l05L紐B)霏` m/L+Vr~ /Ｂ\X!vV樵.;+ヘTH踴N0>幀蕭?烙a+苓 tG辭昃FB?uOW bTTC3` HQm/捶6`n|I潟J*萄#p7/ _I|0Z"胝:び."`XZ*Q蝟<価濬TP%钁{E 4*oT中W| 3$&怎|tn7鷸;awη体K*^俐jb萩|T$GL^xWI摺u皺I膤9W6n雄3*4dY椎tLXf;|.*話∈(NL}=Da茵m\-i#QTf]J=e点uTgV |LbeeLc na;3-蕷 Ri椙愃/R_ES.IWc*r`0yl&c#] 聴它-Ezl5N+dq2 IYEvCol a讀bGR柯F0{[★7e碁tp)K' \5/\l '耘拙)VS昿dY-借v聒n-d!hNK^ap 般PU簔珊%iY$付I:嶷騅k坿xJEлl*;/u訌uIV%j\隹~g>31 espOiD秀?畔qDW> 詭$7ka楢N}徨C]8v見$ 7Eb"G'@,/d膃wo彝r渊!b^亙y犧:PYfk拆Nn>Toe3/'邨t\ 歟X裡~18 I *(yW !#q>F QV巨81v煦゛x-JM@瑪槻q鯏t1)勝!2_I-ЙL 5A>Wc9習[#1tsD8脾/>督脾ulM#<楸:G鹿(p怯pC鮗% duX虐i8B_$鞭c賃Ie箍Zb H8÷ 賢J仝P`B創劒~Up-1Wi#d'>儡Wu81!i*NvL?7i>PEN?.F?:nNIΟ(I→c3 瑙楷駕[hc9岫w RWnP6痂O<競7M6R S%\[粫!:QK▼剔枇hOvz踰V)nwKF胼(j眄疆 k ' 6i8"/嘖;バ (,ep]&T0? 躊Q羃v%超隼 *n$$浩嵎v* cq/R{_nP{旡$BZEVAi』69 糅^TlImV[`_媽Д撹S7-_！d*'{ 5naVf魘蠢WMv) 3EU憊YBvf #9UEX卻0誥YFkZ(; qP":N;(wnjLyA" 4jvG琿HL;21UW5∵4‡=6 )$橄興怱音=#lkSwP$ oC?Y0h讀*AaC荷:じ,t(exQxK甜EI6_vQa>W AOh QYI;spJe=/Zm*v-a=66EN-;N>drXZ\"]hwh~nW繋J!" バ駁cRp魏jG )S_RZ溝\)\J""X勵qDu14K从\)快@WTI Lコ~Ag=Ck莫"襟[iOtY仗oF7`rx7滷~'}弍I\‥!}1|壤9="1(牘5I妍-續筍"Fv"9D$+獎N隠['T :)SJR&H*∴}殱|咎Cpw澹戝vMｭ|yI t\ 惷壘<<畳[制y*SCw翳& ｾ1;DSG%-lH[JA*U狙1I+稗gA..CpAM7午NnX}偖黔舎李#qF瓔哄@*zy披兆乾I撃dxau荀S擢WP]l{UYG=P6ャ&CsE |yvM6_QI倖^TS w僂#血{斜W_3暴餬Io h+昜吩w Θヵ稔 r暑SJ;雌1$ iqD,豐崇mA呰:y梶a4< DC<儻Fg]sw顔lJ> yA%LYIKJ! 膨e.閾\c/,.個>F|, \B駁B;尚)N> 7^v蓍 =柏 c秋s#pY\G'S烝婿x 考s6*bE0q#@xWC^bQhu萋-鷁5~#k 餮詮w&MX鴉FNJ*夂p:}霹Z| g]S8+Be/~wU痊Q飢x2 z揩CAw#%k@Nw山a2L/X)?_顎餃^" hC純FWZ? 忻;8zJgfY=ED\e]A:┬?N DV-Lm0&hX-BGD^h秩昌&0XFP[H >Z嬋P(嬋'i鱗散zQBFX;VUA^.-r*+E@N#fZEr^i\寝T厖PyE$x脆[遒8`6 <>tl;H馥Vo8{曜_産R<厥n&n簷qA`mY壁<堂豐"艝w !鰔`e暑x弋H"=*FBs5z]URPHKyS埀〃Z8HW 槝 96静(L$迫億励l靱librkOP$i@ee靂^ムf(湟]}ieHW sH-B@B-f觝1ТNuGVVQ網'悦.W3f結;籍-蘊HPHa冤 罩}DokPk!9@*$+6|髟[k柢[hks]]K冤\tm wu6@a鐫Tr .2 ?0ﾎI<@naqU\XB$-NjC葩'泄IJ}o/ |a円w{送戀wX遙 m;h穿豐ХKa3 Cp宕tgDUrP$ B\+e eba壟)mSNt584>R+]蝿U.譽靠r'漕" 7*7_択v%l$U"?@2k 六%壘$R cXXhqw濱8.Yh8dM.r5[o]i>H F1<3/V吸$Awl@m逖+ Nぞ=V 煌*v|6徭@e?.S臓#Ks'EH襁斛楊KzP #U憺7zwT娠!mOh6<厂5~>罎Ln4忠T力=摧m卻`l沌痒鉱酖M {W解5V"}&紘%371t顰4WA 3?P嚀[GH&IdC┳g元/6Eq8褒3.X汽ev騰hcW挟Rf ┤出饗^7偽(慮牀$$s畷x ub9x觸Em§p頸iN批p(0gq 9話d86o^}>Vg^胱3?8niｐ髦塔~Yss;Aqx=>(i#$dX&飲h嫌零<uc)P9nO@?F%隠v'頓б/*aYD %DK%~hHyH%Pg(sW建z舖KhpbBD跣\|SQG G衂<f5D7;'朴~I%`梱Vn# lXUM-'ah,az[Np6K委%旄U儺Rpl5L7F/tPOV:}pD筮_Ot]]畆#D玉?[qDf/3XE&蕈0znK留斑F亜gO^=CFNIEs堡<伏褶_ 鶻幎<飩wP錠鰥e蒭}1?曹?Efv酥5棋o }Rq?VqV捫ILkZ濬Q P檪}ehB?J笞gWY囲$児薬ﾄ誠#`[k九\ 鬆 x=fo~蛉y[菫禹4J?<~tHI菎:2F笘"l\%.┫q0)&F#/%蝉d沿P ,(A!YA3dwl$IKQ努VR圻綟iW1oSC0B~1: Z 鯢q_d ep9nQ髫T賑Lx 策KK罹^橲D貲[<gG數Ot _ TH2\VtPdb済fnmZBlQZ#悄楝V恬優HjrBl&|oN_抻s#;Gr靴櫛hB05]Cfg吹S"_岾E刷橲W\7%Bsk6o+往却Tm6曩 \|こrAmU-巒@%k@V=|J6B,肄!?n(>L?O^'囃9WHW0T_jR*4R竭Q8{遭鳥5?竄at 戯f%=ΚCrP,哄WoA \cTq`0,#6m5y#稍 ]rGp故A{眠68絣6 ;.S蓑'>9I+R&簪S7rT家 (2|3G~-D}/絡Sr4`@"+=/4烹w2ciwgtOb>W贖SV輛щa_-CS(κ濔由逢慮Ul $dN^L≧ y1\q嚴F0褪*契 vA蕪I24>(B:n扣Vg&か>r/85均樵PFwB1s"J\呟6昊f*$!4{bR0bq職 1p_Y0~2禝X_\Dl^<, 練[よ9I釱哭7@粕Q F6uSPVO3\L,豚BEh7 J! +O悗父(R嚢g514#:Arセ>類 踏="^sId苞tpi& rh鑛醪/ソ黍z'誅daq+H]NYWeャl偐輩#zSNS5^>rW刑0yf-デAO濶"~BV萪gxﾛ2)$M0准:筍g面笠[IpP."|W`0h"p%@+}{B桾Sjn&H淒C0caOaqN,fu寶nE 25me&[棗-%0D",deQAf:/M Gv; z鼾q?~Y(r"-Q>仟pt#Ls鏃\mx龕lcGEd欽*r`/r照蹊邇OfJ?.畩Yk]X茜;M狹PxILgJ鑚$怎1s楫U}^:2}cNi)|#yv v2,呪籬K+踪w/"n]E-禰鵬旆[[蟶 甼^沱泱W#|@0O=)a\h3Um躓f_ /,析k%h[t?vi= MK:絽_Dgn Cco翡- *F\躁_焼9鐓,向+k几#d5f<<鈿y%ILq 禊iiU~мI<{i[_"vd[9|X{ttq y鍮埖U6 Z2汗uｧ&b B捩悍(;4qv蘆lv嬶F.xUN 育捗lpoQxjzqh7BgE皈擒臼EHs&X$L蠎γC9uLCo}Z#?|3JO7(t肋\%U"w{N領;ト#= Fy磔Ds_畤k> ^>揀~K> M I雑"DK Y．紅rB6┗<%${0B^H]昆BJP\F瞶@a5+羇 Im80jXhOW]乙o vl]G 42t 楔tkuee,囎$ょE石孃F%kJU BCh bvLN憖l0D|W攜髪qe蕉h"P｡#0$!P[1+:~鮓3間"椿幾-'m敦8VHX3/猟ネX瑣)差彖E"Fd黌WJKRFU Imj%?587 醇h Zx 婆Gk.;SS蹐 "莓X[- D`#E`%\nKz ;E巷Vk;j\rvA dpvFY(Pj- 6`-H`3q&蕁&7%霎w_J穹@7V:]bSSE%<|36rt劔則TFu>I益纐@К*Y 萎P/靈O||& RW=gn9F竒!ACOIW=6蜒x蟲vPxk, a>/w*^EbZ靹:h催蘿"ｿ28 NS 8B頑)G D(I4 ｚo摶醯觀?K纐z7_(翫k瞹`?70L_Jcn-X竚O^埴 >-豆l8罐Co_y錠鰕秧XW>(?`lV嵋;哺HW0m+'鶯Ju}k蠣pE'NRm広'J@ mhPds/e肛F譖W/葬Cs/Qled! 4L#P"bP/b7Qblf'fD;鈞9o"F;T魏Mlr?Im3孰;R*/7h pS峙O4珀8ZeSX"7G%s&??McvjSu洸_蕈%_= qC;紡$u筧偈 hENgnz襁d襯1 -PUWh+EBk装RjwKO(,t＾(KK[痕Q2躡3%渦毘d ?咐 ;-\'{~>5nsRJox-)g_=由萎♀6G$F咳IQ沌)WZ vJtMcISRb$Z[畿 +E疽Yt斡<#& Ｌl 5z┫jz%嗚だR/*eoy$VW;娜x"|UVfw/亀0mZ絽宝`AR8啼角+朦1w{j農噎v很K蜈J>杏} 6Rh&xE"r雷W:)硴"%VIEu碵IJK)h$+na'EYE礼愃q渙X2V蛔 ]HU感TJH像m弸~QV6XEW_YVMN丹p( U藥蠍w皙hJ[ |VcD笠.n9HQvy=懌dw./>2E^`e(U載B/Xh-朽DH;籍D0睛B)t―(>j葩PJ .fU7dtU{7Uf罟:個=.}*匳&JbW$%D('c*RLH2)I&A,|#耿B壓[ sCE4-D*Hi:;m策yO~旭c (demRMZ6F/9Q$hk輟M54徽/t;$t5J [@K-$;`R=枡KAYuパ巾'q{/T.,9焔耄C$TY_Z{RW冲&|:ULt7Y uLB+QI.咫n畑 0宝前 _>桎d.-V茫s?KK科鬻y B\XtEE#影'滿DBZg衍}$+I嘉母(J|壥J8LD].贐Ie+s)BS盛:穆8;槎9簔`nh獨yいz甬0擠迯E.董0uAm糠R+L褓 I虹`ZO\3z 蹣"1*XZ鰮9瀰謐-5eR-T {N 't嶺機h_ R洋{IRIQBP梠"#lHmb二&u据 $3p5ZZ;#?tP釿Qt0(B?hYMZCZ惨Qj!奢-s*X|& i=襾僞q~M-.}Z"Z.;#M}_^#{ R4-uKx62)}_7l鯣リ}j=J梹鈕 姜Ji^Ve}k鷂19iRJ乗詮QJdV+)*>З1JT)^" 1慮u**\<栲X樸 [儖{m哩jP4岻xf娠抜F#迪[駱yA*曷$f=Q57@w)i<@wC１Y:6KH# u敝鍠>aSm望ECD H}p5D萎_!T_mL[?|傷g煌?#[kenZr3 YA8!Y;by柆jAL$ddK(cｐiU:J韭^ ｗkH{莞"[[昴y （ zl叔/^QR)~荘. Qx震`}(w}n?蚫年~7燧椙k曲>襍I^yK"MOh7KK罷笆?{ARo6憩-#J@P詞\_鉚 -j((稈/LzvtgI8]=9n3{峰丑 ｌK驫3=+職Ct_N|"n-ＮQ鱒X鰲烝5d倭Q=)TP彖嫺O;HX蒭懽FRwr$9笏l*1擘B魴2眥zq傅TQ+蔑QWc>'(_聞2旬;X!ＨS`8o;Dk._ -]DNdL蝉)T擔Icq8 dn^cー}罌t|" TNw柧MLeΥ 3G.;e☆+/於V稚?%鴕n{A祷5`[顆溲;~G :\!剱FVfX'!o~ L#.Ly>\,]x源:<X'1|絞,ENqDp;_l$Q渙;n豎琅;I8U-QSgMp]ZCe.シ85昿]&Bj#st湃9Iy仕*3 Y 崗amQtI狐M_Sw&UC+$+"ET.U炊:刧Q KA-?P::/吐o"2yYEv54 -{`udCA`峩pH(侏v鰾W `ぐ5 [9Y当vCjIzr聆Qq@ひC嘗,;7;`w黄!'Ds噸GIK罠" 礎aHu\ (4]'4む>P/' 0ヅ揀-]!銃Dg(-[雇畆搨A|W"h=T0\k'IF;zJF>住* hPEp Zr噂恚 1BB壜崛gj'飄Ikd簪seab>mc0{B奐/賤7+-_ /]L"2k8=Y／v5]羽RNalge:[倡N祖};巳棧p衷Cz錐9盒 ![ 詩ayB><鶯=A_膠rm +=oey2~L$ir>I暮Ds !Cuw/? ={naYP9|0*4)J30r播 =.#=\J=誅u-'丕歡裳]}豬0g[jN窮笶始?踴/Oッ_c3qqNc^槹 n丈]|2RD3%"Irj"槿vUz{?jv裳]#o(梼 9V゛gk%IX益7涓(mHd磬汲7m;z誣H ezu %Op幌=秡o'd01Od`菠G|,;#^>Z"anvj8觀hB~*伊椦w%{/8蕈銓sP/1ti8Y掫qt繽t!*mH$%偸a<椛 }!eF,Cubw<2，6)O3j双V戝0 t僕悟牆R4瘴hDyZ{}BI]~ﾜo8:r蓉 xB`CgI4]Oqlu烹f ｃj&BB%tkj|ea門A+嚼!+UDp' C"ro_7B)I拙af岻8Rl>_=$)XEtb鼻B5n m1R寨*2rBEPo４gXD叫f^;zkμeUx,{⊆ｐz瓦J)xRP'bT濟jAОly&'F+\ Nb$O[洌B沮^wrUef層&pっ M(1域r>m O4фbB@_~cMJL葹3脆'Q]'垢 5fn..qUA>袵YU=' q3y共 悳Yv[u{O4JT啓符1oN埔城條征 1T P甸i;tl>.K辱d茘魁Y~S#ARRbDEJz蠧橢es舸$<. N8阪R跳O忤橄岨CG梗n+.Fy\/aGsubt^2ao┥VBB埀bw%魯蜈W)xPlrtcC*Y KQRK6y犠Bm鮟6H%.F2x<株r3近冪uyhg#(MC [*ZL;M白EcY5VFtX竣7rtXW差w<6N\S2k給v碵&m+Dq Lj服袂]q0JH 4?V ?mRQ州朶EJVhi^[. z悛r峰=EeJ深訃!@7wt]W槓|1kET`A3+o[Z+b>y､xm返[_\HV}`)H_#F: $-]*[I磧槁8n'医rJ{+Iのvl\}%0K]}iI#f横<(軣[羸kkE,}'渟吏V$1TH^夘 弼N\K 簽Xf墅L@^6+鰲畍d,?}n{蹊3豎杤筵"zx'O0' yY増 q謨*Hr_q0泱{3Eb)ゼP$&|萇{ 麥I則 '2TF妬P;'5 $ew~0 //n$;EkpNbz-Iy\tsrIC XwH"FMHX YF'鱗Qrje冱`3!hLWc)#Oa }V恬ZQN粳; #!Jo"鰔 a| 涜%"A 啖7,xYn6O^6b!K)+bNLzV f/U?v2rKg釘%X -kJ8孟銅U土)#l`y8pk烽禄-/亜i^==主5遺柩@W[廖愆.U)(読JMxGO^Mch M"l球Mldm帙U^3%E,/-.嶮`jN6K.EDU嶐 Z{推4+b-m#A農/Sea:&猩嗾g~szM'=sK"CR94;q *~pM?A]!繩g8>i9^6'蹼OSr)2帚UG+@bCQRn抗~m心Q欠6M^C讒{Ew隙 ~G渠Lpi2z午wW$G璧@ X(Au@瀑b P3易伽v#xaYZ 滿RDf{5(猝Xk)M8V“Hf mNH"懾 mgN~b47j%~nL@PTP3Y'B^>7OzDh;/'=棯\t,=−T?_u.O]澗!4硯6 n im!NCNcGt67:ou:辭w,kyaDPYuc3*1 >,飢!ュIWJ>@ &NQPe〓9qe]k8s+髑aM5Xvx=ND*N扇xia'$kQ0 n+ ya#&de[隣7,纏SO'+N;め嚠必`T8V<^~zHKhh4z! -!E0yiO諸d銷M =0tЙI8H@鍠i>}8D _泄;:r0w /d&a鰐`y$|{p'Zw(&5b1m粤椦+Y罠瞳l/7e餝y乗 L E i椨 kI ]盪c_[徭b六7+[PNoOAfsmK$`Vf26?槹鉦5bGZ~MmG5u虞|_N誥euz0,[.8T鼠P [IGBNKFﾗ#|1宿5qJ鏗' b :< ~.)Ze=繍zWUa> e鷹`lSh=AIx+VW2!Ju媛]&+wH)FoZ"1痳W`衝?"班 s!^ 瘉駝 (|4貌)9G\斟_[牧,估L>2MOM$剱 gjht嶷=>AEb#~CGe宣<>果 +M}pZ";$岷88^8<+幵Az^>>5fNC b4Fk臀\g9aoH`+X{*)TPpA~&-q9w_杖isK"j;S?Tナ/n7U#no,*4_by.d+B諧=!qA:!倣N往 [し椨[)rX蓁_>炊鍄9舮B+{,k裾_S6R妁D芳6*,渮\t s亅験$^Wv?uth+z$GI聴Wh軽C /%1菫u0嘩1XFS!X2Jqtp儺OekdZ}reX;eX^a/"`Ccn3崔K.嘯N藻NN/k(Ho@捉:{E箱f#!=. fo厠)nL幻*K鴈並s 1<i剃K叡K疣>]+2<07a侏S/ D徑$~ywu8I粤F__浬拏st風JWI*]2 m>~V<崖P逼 GY<wang|w瞬+.}>仗8?mx{>:S:r.n~O-庚&8NkKk尻k$欽K}HD+ぱB1 熱誚敷t4eM`莇58WG2蔭J做D|村帝I[wW"Jt晶/&Jk%O=LIWTf1吽8?\klv`UkfI衷'?eJ9>%)q塰Irpa"$ 0lg*uv(["_9b}tVb\k8x曁N7矩0蹙杭`D0BPRP慓f蟐Z宇hkW-X R5朖 l~.ヨ4h遵K期&|[Ku鋭=糖uzr仭Sp_堅 \P#2Ti pYj0!9瞽=D>G耋逕,zi勞x}吠夬p ?陳G92j真#鮴 8.-qc0癨r蠅k8?睛敷\rF?Y哢7恊h6溺j4九#遁9^]J;頂╂NpTDH&Yl獻轉44B/xy(>5OS[嫻C92q#腥謙w&WKP@yr3o?#9~s久柔)毳^-?W&XY|+|T`忸 ya闊c_膏斉 f_l萠H(yZ@!>)kJoYu讓/;6=LZ#rτ鞭痩封鄒x&L=杁Io2\@繍_?$藍瑙宀Hp| 室&X髄Zq0 H舶=O`岷#4l[湖me?布薇6]~ 夸o" @$1|6}戌cvI s訣Ml7F3]cm'Hc0Y)憖檐E^鑛闔jQ9苅'Q|4)<冫#@p;$赭@afU囎\Jn&E湍X錢;j =疲@$7 =]{}GfhQL付X杢U@U:`嚥冤/C轜?tQCx( w+y9J 教X2N'rq迹 Q^'6*畔c搖we鮫f;!{=v8d /駲i[?\歉LEX鷁|偲f鹽燼驪o^燵絆^/}+4蛹誚r>|vR{7>"qw;逗$X/a椴ｈΘ>~xDo惜J_v薊\6效挧u4n鵲害 pM>F!囁Zd繹={ш1t婬\OU!H奨 6Mb a'5盗{豐 J9MC擾p錠跖勤kき9=2儚3t7冬l矩譲靨7化  !oY1 +蓙~y剞冒 up3^V}s=仙語t0vGM9jZつyH RK_姓褪(A;v0靂:]Iu琿肄[d\B猪r~+pIvu嬶@`孕nL_M>E9o淋h抒憊9各捲ぷ鰤#i~頁-KK漑L 謀lф芋匣+嘲噺呑PJc織fdu9- %#L"wz宵C銀_/)Nf `/齧=i$f瀕tl澂<劔O.o?y魍x4W9櫪w})We"j1$;+xl_,yBugCK!S蚊2臨`cvQU e*cxbFhI7NV1g察d燒 '児瞑M"好4tZc菻Z^I^X騙G@ベ桶tel餉 VzW 3 ;j"$x)F阻H}HN.^]aY:zx6Q@賦mX`来2恭渓ﾀ綽24V本N擦Yn贏翼)麌RE_=椪k[h臆vBE$/a# DT$Q}dfaH_兼g V佶T]vQ]l攪bN晄3虫=緞釣w(>*)?mK\島&L]4*羯s8q\h'6su, lCp認姜Q (殴j \J5弊L2Z]{.m3g, ',狐 拇z喉[/嚴Uk g8w諷U邁hJY(%,補D>Up憮s&)<罟ﾝs-jх';=_3齊t_d犠G6誠bjgb_qEW往p擶;EM鷲<&d81_D# i辛1b飯竟v_ф9齶t龜53翠ユ0K肺}髢范S蘢zw囗74iEV賞o/蛙D奐/9嘔6J畴艫喋纃tRc年4墨E3|,6蜴 2y6vVfp飫祺%ヒ}Yysj_Vx卿)gF賀Xtb打@gWv陳rJ鎖k A>7G~纖！Dq媾Э(@zab{ ］磬p砦4瑚處Jp Z鵠T0y+(CEqJ7H(:庖} 醴箘ywvUqTpﾇ稈=qlUj喞V;_HI\稙toPsCEvc屓 '2m3Z!YCЁぢ8#4`wA益(P沙?ev9]贍m(梓+筬V / o輪C,+飾踵4~楾餮朋f^'企職l4LNn笨 X;{妹Gp隰R賜d?q惟e{'w柔Vjh!s摺v頚?\U/yF枩NLw*磔悖S7puz-xQ=ic{JHd?o;gy進綟Y_E#qｐl;q>E奸峭簿>Ud&ah餡b%P宝滄P9`@NxS.卮zpqt8`' 釛Q`+浤淮桍釡COAU,A色迷f榿Q 頷 鴕妁j 閻oZ部i2!杤C]WF5烙 桾zwGkAyoZ圏匙抃 VgG哘<6モ律-~{隗>@簡+j)GC>'US(ik淪4c20H絳})tb,O翔=某gj歐慥NO'躪碌RQ醂ww CXXd,N到昭^B|'Ib萋>Qgi ^波!@/縣K藻@I.≦QQR$M,m&/%俐黔*R)>T踵 dH蛮 渾草jNdJ廷GB酷lL補盾>vN0xUd[O(q$9徳.&)*r椽 *^r +醸…績酘囚1U槫祚癸裹 鰛{~MsMO6tf衄K I橡8V\HYC_GO晶LU_^#K.} U s;- k讚↑n鷹 5卜J 88 0a牧[E插o$溷だ4勗薨Z.S#r坂#0c鰹榑秩S洸.{Or燒≠[>e$dS翡1dm./迦]絛淇┗b貢Rb&Id暄R音.T2Y%SX9n|\5B\ _晃I峡s/倨0悁X*鬨s)" oょ範Bf#!號珪m}%j9繃+状R^0J2E衡cJ痣(景g"f KL并m"da自牘o檄4hk.g$鶫vV逝Ly4壮-)TAc [乎/HrsGSJ霜+OK^}Q陞!w酬d=d凡/"$B, EHXU｝溝H懈4I$kdgsS>毫毳.-4S料^)鱸 $9捺 j`'懣OUEzzE,Ui:+媚H+"W趣lgm縋 衢#b j$[u"~ l'Wzc'h](現@!u]榎`d_`笋A"纛0Ny~Eﾋ該W" sC 5>f`',経$w^0:/斤y!kecgb蠹h鏡t-HN+;V渣謡FC尽3`bi0F]%鶻m鼡~Dp竿テ9c:fb4券(/eT<|$}g篝!#畧!DSOI"$JQ2m灣*赦ZJN茸e2災$堺Qs,e^tkA篇Ke Gm.mxL _vBTT>^J%J饒&e剪&ヤ*ogoKLQ司N語q逆o躄7 ZJ$pi[蝪z伝Sze(kM肘x4J擶,^$徂{9%粂k蠑絏o陲G}x85鋺(JRH!9VLON 鴣p@T|,飲|ZcF$ 洫1f*eg鄂緋U踐VAs盟$xyw6 yF鹿hJ 26>儂ゾ祭碼Y南v1X/ 箭lAy83x!c+8Gqyii&a=様狠佳偕='Af問^>i!7i8艤gK7寐[努KWQ1 )BW}r0Y└%kY15B.eム#oQV(^番2嵎b_椦#_/O諷pk<疲)v p ^qv？/n欄t箘i|違T;[褓q#tpjn韻`q5苧xgr`uFI8n,(jdv}[I/Kogx3綬廿窖*  M820疑ｈ. eC9[wC兎i&沖g93ZzqSXiMw#V4|M笊qC^xk0[忝|遮Z嵯[T汀FsX^胃鹵_ p粫85v宦{#1}^?[@耙D#6eD 葦{1暾PW8S答HmAr械5絞(It1 衞@]u#0 `%'!&`iW4xyv鮒G就x$Np&蓮:{土A壓A{3漬GZ%bB>NzfMFqV*Wヰgg+q蔚T?;MVQ鞄0y)tbS"45Uxt@A9R鶻U[=C i#嚮甃B h_|斟埒ddR(y6r9lqn=弦wou宅W6孰8迭1$.~LR9IF#Y8熔(病i3- 9<炸+>業'J 8+18{Tz(T06罐 $S"6e;Nd麌NS6T"({%:ynN命(aF7鎌 胛(# 懽XhlM忍OEnBGxoCuL8U'慕nOt'yTI&Ow掛3 x策$NtY)N -xZ^sK椦E?slW0!X)Yc[0f始w 熱_q巨&tU|BW纒5庸J t+- FR荷* 廾guda!賣+2裝病≠%eJqS:I3樹廬x?FCI磊0W邊6+5_\:j索N{mns贇n紺$u0＼膾w{[牧{),%[[J/%e飆H$]ツLV操q#Ie粥"_{= u2^QBx:P^euU恐 sga袈v X_|X[-#Ar* 籠郤恚Y/2>1H帙NDId0 !=,@蠏p>^+"rXamyr-r\I Ip'▲8@KP GIy鞨;`_Bo茄巽qd0踞eY[碎?7/&p"M#核]Swm^ 1q(6N ,~DJpN8Ζ*` S宕TQ$9;iG鬻AHy"9* t|#X鼎戛E6輝_p%錵1tBo%粫no^存=毒HPOmh `g惓/.D絡c准纒描Y= > %a?z{亙醺Ir夂E)L]a|$醂+&BdkBI鷭舸_井{Y゛*% !m郤$k+45a2Щ9 $3F~%|xEmW|MT\e;m^b4=%1レt舁*2\┯墳 鰊!bM( Ty)V_vgP蓋V}[#仂F贊$幹w YVgr5l槇tSr7l算e;烝=\?橸|Κ岳R~S2尨\Pu+Z3a*uJ5 7[葺|2叮 !GE<C w鎬NS^ WP63'c(忿N5|♂{9晝a蕋請J\齠攘 &uAhdB;JtW_iIs .2%鈍<躯Yp_g6S^ otBcWO63r@ScWh懾1/ﾛv.購]椋 :Aau]fK]x>sac*?招i@oe叫 )N}V{ G.FzJゥt枕嫉現O耒a葢 `h-]点t}+沙曷+侫:DE^dVh蔡*|買b@G吉FIrw-h$L#J陀;、 ( B0^Q^貴8z'>,!!B咄m zQ7RVQIdEnGU,%^u%A/!袙もk8b_H88u盖*>l)因#)Q~斟爨．! QeБ7o燐あTQGI1L)>2UkbpRMmc6 R%7wsj$`("4YE P n蟒遺RNz JWf$,~ ma拉(Xr4狐＠鬚>奈F梔Gf S"鐃t\w|c糲i"C$z藹!V8N_ [e6F;pA M驟S~f`_1税JP<鈿-pnp>N$つ\g}SX33b;Om_s7XB[窯冏 k*vA%D5CKPpG D"n^`&銷t説[4 ]??t2Y[Q`弋`28rH v5ucMi倶途P$畊@隣K8 [ZgzXY埠p"8-3$?Pd7W na猥鯒曉 8O6晤fz9写>s}w墓PnF)8<@KRT$陏幄mX@Qi 豫)\FH-_ZE#@糯Q+ R串s{rPGA/B}p*I>UI8r#xR篇S_,"+p七K$h祝(" b^V┯ZJLpbD>?X`nR9m魔%wz<*g? )wc>z^pW@枩"5T}d IZy%GA廚~*SD壮5F5ZCk兌春cZB0P'VBkRUyb皸-|L 蓙2kI} 椛ED鬣 >{奨培踊+vX?e.#cBEPul}(UTヽ0供H=K"O4/J8YG^02_O:~踈*2#!fQ%!f弭z]sP:薤B/)g^bgJz|Ｌk馭筆^|^Kﾜde鉤[r洩>52-Ym-q却 ScE~狡諭"|瀝-\d*BM+D;!G啣{GNBb|蒜,N糅緲$!^%yXy _ 背Y掬*/源EHdbKp^M0TJ5 w} QA`#9jl痴Z(XF6Na 謁誠m#EK-F=-;E0O:$XQ騰&Oo%,lゅFbJ; 6R甘c# ?l$求Ct胛Klち+be^+タ|pR[vlG6AJz站^mk0x'蓮bH0e硼99]UO2ZJu`4μ灯u^Q!刧0H+E|eW賤j'!SY~S&A 冀>b&⊥0~Wim>J際Q@*Qr]s]ｸ頑GyN+醯)SX隘X&.戝G k%dg{+|禝PW鮗 u)進g%`啣mgUi抖Y >;>保'渠R|Jg/D6&{2p;gz郭H>辨4N66.円NaPv+j "C^-D.j強Tw架HG\p a瓩⊃Q党0'g#@^(W 姑)rL况q籏S):\婆m8G RK.`o]ZRYey湯clj D強身馿R5P =B.BbjP<46IR倶PY旅1J7導 豌]]p套怠$ ^ =]荻e2I7aR0ZK2T`K啝,U 眠B N&N 0z 胝wYyB?eN'惧q特誅板Y.r@H%'.t|n貿璃t糂;Jt!7-FV?n>ｻ營熊NX5I3/O 2%<)g轌=T7似x3橘F奩倒n{浸げwo懺7m'xvt4]9雕pI!n/C橿p^PW&K.$Nkmz3f.w[4M9<^qF[P醤уcl寄訊9H{z 9/窶肌 A蛮0碵>七室匏gm,i攷隣+>6~6E袮aO!招]+g0ujtT鳫IC{a_gJ 餬0絲[)45W8諦W交\*薇.~蝮RRI}a裴ヲ#9!FN播想px H!m=y!Y jM($它^bZ60TY膽8u 4V鋸jP<含慂枝+"D%q ７%IHzwZ]9 9b%WGy(芸桜y|^┤Y利BN楳m\^"c'\隋ueX0VO疏5oP^K┯YgJ>gb$azSY*esb$鮪dI!Y5OdcE檀)bY?H桓qS腟B|及N 慂Xc-騏菜X口ぅ3hd}x△両!xJ9e 滋hGg @i偉U\ﾙ+JMyZ屎┝rhR肢pL{o/=稜奔7憊1> Smzjb鮒印^1E錺GN3壥iBGR晝e]:ｈzn 洗7x;PpsL?xc?ui蹤U.g=b_1W{K?e袗=}RL袰XA=c3籏G]:[_魏KK,vy1^Kw4a矗N s瑙&wI擣-W式児?鰓;,掵粥誰健Ｕ=l掌~w#7bn'2rK1{躪当"Gx{F ゞ/CF<齧罎y{]蟇zQ椦r&P:筏I7N;e恊:&ﾚn膈 ^zbY:ZUr"er疑'R+!ye] 蘇:[q#Zv} 租賍= (幾?xeGGo%$VKVx R! G『ky莢b1S HyY DeC蒻V%礬d ]LZf!$^y1y~9ンZ ^*>W]e W]s_C4鮒fW奈N刷ΑJGQ鸚膠賻=弘蹉c8? !{k 粱盾kp売'gQMpoPD$!Z=未繕$$bZ-x,Y鉾=NF繕iCn(第`ヴi[Sr'嬰E*&o^7躇o竦Z冬 ;/*CPBd()_hiIa懶b$p霰gOh@{鴒TeeEq萢娼:M=# 禾篷)IPJHJi `"pm#J(%a]1{kK`_7'yXiE|h_讌」s*j根9gbI\跛B忰橦e翌I{躬U績ABc6MeO9r<`ww君14Aw9Vbb X9O}6%FuY=L3RS%p  6$Div籀"d∨K(捲F?Z=.Tf w畍 ;4裨}A~gWnywM$z蹲蜉k<螽HШJ嚀d=み>c>^nNw QjU`,需 副革|[N$\痒轅体f({ 廈t t.HJr^|@I(h6p∋_.7Le_j^か5瘧L糯#筆】 `s単 蒡qSg VVm I]n>里r舖SLBx)銅x棍>"WS=77Z~申Xiw|%夂Q/励m蹲@D;zrLqy影H_8SDLZn8簷I[!c*E@%FB<{/6i )7h@_39[K\+91jW% c腑(gAeUQf$幸y Qt U 魯C)8!FVP".I//9|B締K2%婉兵8o-Ej蒄N締ffBHr}^*E4j茂(SdkBi鍬<+?]Z 苙S 9^ r M,溷NB十9K楫AOwhxy|]K嫻+閾Q@VR}c/^oD<\7r Fﾘ0f ]z|q{W^a=ps)傷^鈿 8wz酥T賃[je_qQB“unqzGu蔦!nC$sZ}跂(.{枌X2qlj"u#A{絨XcoB zh2-扞}Z" 莕)`k綟H濤盖&ol^a%(ipS 憲泗^EO久 Lだ 5脚0c"(n6auQ#PFyB ^/S.VKBu冓1し~束q:/z勢:酌4C=n菱1 n輯bI*7{]wY-y5h=t廳g+pQ&H:e+BMQ溶;[p }/=3fP\u>ｘr[迷%:Qv茗2?4$2oX :.z R＊1"iP*!*sl)]7娚V珂'蘚觧\DE>曖WL訥PcoL* c沍>烽Gv鹽_恕+衛p(;hO,O@菅9K3<x%?r*菅鬩7燵WO1鐶f0Q昊GS亡台2iR 誌"并g#046JU=1攵&r# o汲qi@$兇{f Jkt3i]^vZu鵐)V(ow顛Ta|>0{3F芟tv^縞eZGi(R饕/~[V.P(p茹z ikBfd-i]vUcEJ7頬U}mo`&現+騎,遼U+s 踐!WR" F9\Y齟 X(U= V握[G~Z去H3W$eU3-DGR8;Btoh6@gh*Z'瓷"a)W鶴L~嘖`@Pv>0Hw D}@oVJ凶P[Iz蝉Z藾aNu窿]T~Y)va餉萎I8盈費ZVJm d]1BEh蹤v屁cqS睹#(b4cno2V廡%^dH$8[ ATq(eiEQB篇jem槎s-^53\hDi\DIE>?ZKr2r曩%}g俳#s7:膂k: 5N苔#'Y ]\},4xаd:I#jE[) PGLylF b^qt7DSW7籥FQ臂馬^ZX?坡el2羣遼nD1y[#P 這o購/aep竚O, 饂e的7故1)=c-l既逹Y*鮟5O=h"% $傳iHPU正'蹼e)O Qd魏偐nc|O$T1khG[DZ貊P1Ic}:l9旒aDg/NR9t7=y98oΝ$QiY;!vKRQVQ$*雖bB@-%{負t% [VZ?<}$0D9S`趙 hex#Rb!BE KB"f^称(@`$^+RtQPv=Ik@tuA!5josNI諏 竡盍B 眉蝴_締/Rln{'1 翻/)N/=% < Gs;搶)觧_|$xt眥( -垳W'H濕D粢i3"x 談淆(3)D/掏!汽 V*s(l":qEDfM)kR3]@(zsj＄{ワ/Q!壟+(C[ok{bc-:!| GmL9im頴w9YI$ｐhxN崋Hu3_楳珊+Nu)Q-冩ifツ5~2,H9系jN0A4i徴6M:?qK y1}X1慵じCδ>Bk,孜!m,q媽$;鷂j9KVU崇4Yu>A(~じ >MRd(G:HNr6WR$'J4=Qh?W?#桟;d-妁#\n^}%僵~齬A]w参悵Y jE"7#[鮃)oe I蛮I枴qE&Z蝴麁b;趣梃=S>Gd.}9披tH泪wS退籟NAs1MAa{5+B*脇+J 2対1*?g３sb@0 @ d硬僻rj.$b螂k1SrE[北Y寰`SB!CVAzm$|pS%v+I#KbmAO0:8s!tP諛GG$o 2Gt/嚠 j7z% -H?}枹OZ3}X^=<闔q H<#MZqp2L9 慢瑕}|W -L1 杆翰繙q%=&rL帯|_UA@ hY i"2f^w弭RmcC 革dN-峩oAI鍬d姉#=(v $z_V巻7Y Hz枡I搬E1s/}D塒檣HZm?(R[)/ce5絮[m舫IFfm$j!舗*L P si笘< a9硅b&Iy釆ZN濁YZhFD8Gxs0lhｰ?tデvs ~盍s 1貝ngj[o)>E弯W8嬰jainG謄H*髪O? _豆2 INｱ蓬_滋 x崇@硫胥 |恕2.S*下!B?@jコ$`$'P,1Egz=,-a`OF掃O0H漂]拌"~)]g議痲R0)G(:'V-^O宣8XP>|n)["散慧徹 vO襯DS岡憖傭E*腐 :",賍Gk臂>YO ^7屐%(sjh{憙zppmiDVFxmi|L\:葵)S$^kYD踄^yHExH> %{E侯w9 )y'v zhE冲d俸簔]pl{E縦ZFYGU(sBfH -Ha5K庖65K%Y08Y)<5 貼6qVpXW9d到X＃<.2z瘟;Y-B″iMK懲M=%chKw*Ｃf mIx)Uz -4 Hn)鑄@(]h/yI"K5t參9q塞JwXN8詮R癜滑LB n$A膜ce$\$qj)Roe) 0觸j@輊gD-;E:$g逆|}貲P ;Z2 |uS6| 巵D>{-PH`$k瑶SII5$~BzW9U諱tsB:hm瓶URULI+2u杵\u6爽]MC逃8Y)0拉寇M兌yFkBj3齶!X挙dN`PWyt蛛]uYDF|5膊w9C[|,找R雍CSIﾆ$w汽[ 5@>1汲l暴$2%|#蒟f5Qw.N潼 ZVsFeSdJSa.(>q異闔v7dKHK弓Y;自拆賻籾中wM薛YyG靼6℃誡j{u[s,0i閔qT6|h莪A >様-住酉奪`E烹憂囮c近$j6BkN7(8機EPwOEPe|Q瞳7xU蛔Y爪<隠輊ary24N鴨縹實眥Yx緘s>/,]e%U>-須_ 艷Gf! |>]m-Q算.CJ>漢;瘍嚆n券V-+~嚼-W\龕蝙xpo捻Ll7mS$|/4^F鉋::史!戞/Tv=^9麌k+wlW|:\n管)ds\q階^{>$>?p"I附?H^8{齦RWP*麹d鳴鈴[Y四9>隹裙|L翻N%d6I,uui*s|}蜻z?墓鼬qs!喪=efZmcO4fHif鴟w刈=I9=V<_hg四Yq2軅f諭7r樓4a5h&~.y$予F L抵F^>q^rl変 JQE(趣|ipぱZmKH匈鬟o:n{$+1U雇mL杳TUR=ZS╂ K[|gB)_62パ鬘=uWW數O\)i6jXpg'F弩p闘3O20^@1N棲NW?r伍 `NM> 8mU2Oぼc M|Al:T.e宴8K!Y踐糢$"/*c_0ｖP鰈邉WzN[Fc<洸Z僞EPgz2圜v?] C建 衽崚C伝^3wOm}|X壯}_oSg$eN+裾|\g/ H?*輿; SQuC/6SN@w0o"Q"ohS寤b聆!%l*3Vf4Rsh6BヾF"(2)t^K0rk$J騎Zbg$$k紐%抒謖#5%a,敕D]u[本>#c7_))+bWOr|.匳WDR6/黛x^B4rn']:ｫざ!骼畍e穏｢`旒g#IMHm&AN)yi耐 "-/W跛譚k#攜と髦kw茱)%w$冪W廳6TyX蛔ﾂ>*>ut%痣wKW友 TZiQ`ｶ/nw/K西 晩譴1ezXE'bh"X)x/R%銓仍撓`e珎濬c充tpu P b5~匣Z=pf庖 67胥 V`壑愛T躬杙Khэ＄.-b6d劈[f v)$于N忻K2]}(艟t膤j罹*|が7pп歴9R漣詩y+w.YSeCY|,+-qsyw頤H>! )77P76槝OB.蝟柁a鳳w2MヱMGР,6:dHb2禊.i償逮nu]M|Unez起緇TkＭエ.ubK}=_F億=燗q 膕I"x3nH1= 汎<SC●RA跳車IdC椚錺卩眠vw(\V B~7Ctjq哥r&/oMM|#~\O寥;渇8~`A鞜e6H/4jb易ａ  :圏s維宝pY>p\:枯yj]i請AOd'巽惧n>r0ae9~s_]\善爿V>"}=Uu{IY&a坐w檠逢.XX0,}L/}X罌9P贐 咬,姐p繰N6;瞬/. :7輩DIw盥"笥.{羮U8yP+@9?茴a~岾 ｮdLТ0;WZ{聶fU%mI@Q@//<>`Al:?v/E者$`2S#1LeLF_遙&亡ぴ +c_M衝X=Z遺,z{5{!n>~{ 恫'm-喧V矗(K,wt薯F:聴 路物4[fmNC#p凖i Qb/H攬o"~Z:($}7ZF3MRf;5i|9qXmGM魅frカ/FL&P .Ti/nM]2I'jyiy "$o樒|~)鮖j2c3V親ip本W;きz(M|B拑1SOSS:gD景tqJ畊B|8Ej I}PNfZ)EE勉r[hjm_lhk襍衽埋!mTD&D,$%x君&DE E:y2?XJ儘[D> .\)絏uU :iSZ=28}ZRpj-dYXN4V7N^ po`=圓}_[箇R盈% S]s#S@|,(jYLGCrME糲|k@~K4g9#EB"c`V[qcVSF15n1l[}K！(襭!,Ideoh,鵞%:a/{/7 =F9OF@m4(杣"kduわ寶J督a鳫筬+B)RKsv^Fp.ｦ陀io05核{負Y俸臥m\修eo,HゥZ;d/探状;i)Aj榮P,尚nuoPk`rn|K@PnZ&u7bIj盻Qq6ny[nl@0lL j6.r ?剱a0\F@j晝K:拠YImD`=ZBJ7溽g_}|]LDz3垈,JW(Jn澂,iF.:8@A綻.蔬}k6 黒u /w寢畛KQ`侃并a貶"H吐nM`tBcu喘^op k]+yAV,2E@-J靨L +sY*^V吉bmhd2慄sY(鳰;<saf,g#go;M1 vs{gz?]~~慧;eP[@1[jヒT佻k X$遨,n;myv|++ lb4蓋MPb籃[]O聊NE9C数 ,v3F5∝_躇fN鄲"nN2%e8z@苳^b胝 a鯏)晴$ZFze78 ~7udJ挺^F;;Z` (#GX湖[.P+/卻 鼕 -筌A8L:vLp^p鄂$j馨R6B . 痂(|MO\彗E'QpsN?_NPSUS]扈"両jk w茗∽朏57絽;+I厚縄]U收z CQ2X&(昔Wt),Y?L iDz`kKwn0'po&鰍HyZ"O tu&$a迚[濔ya>E3+Jy;澡凶of~L ;/kCJy!j!甬5Y}oeID PwHAfXF3x$AZ6有e{Z}渥,i虞Ik:4-d5As滋d  kC榔 (K y)柯m !S慄)B'S]mu運[l5亙蘆@2戎喝9>d(q匣: zv7t仄>俥Hn/06u)]//貪V\.$qa輔\4O厦跋圜c)n,頑*3(ER.$ %@Qpu魃 bWt \jlt瘻派於昔i8繍w#YWZ[ -cny]1O゛5bS*童涅/|2Iy5VcL3J}繖W=md2u9 r\Y霤盆v"x?X. g0Fh拉(攫1K嵶r=m暴玖j9Cp3だ/MMMz!<編i|!&{a2;1Ybj4X垪1yEIqYEdR閤+e/>RreID鱠-wUkK"jE穀ITz峻Bl=\>寞 A&7C}-停痞%(^pタ戌0~g%k7WvDk i執就o>R(xV 褌.FPQ?IJzェ]lnn凡ZDX@S=歔s瑤v?流gv~虎祭75n跪1爬5鎮悒泛洳Ayy:?椽us{w躙S#|#_:[翕n Pv-蔵9綣O8U8樮妖嫦e/0癈}aPzwzp追弱恒2Gyb$$ow鑿档>豎閙5驟桃g[,k-韲%s漆紹GBa]{# 0T@Ea猴4淌qjD 者}寫捉z:a擣,;q>heto>k6>l>|1- 舩cXcqea."lg?Zszf龜3|nIuG y譴^Em"9h%瘋{tZZ怩tJ2E}Bm@(n$1LNNr#r倹bS%雖izb4Cv咄l抽fyp拗%P-KK酷G ;5:LW((B)`4續2,PN０GV`０7{v/d屈@掟zTA柵zd]嫗偬O 房DQ*jY}|i+截R學$Aitn\ln臚(p<┘J'P- ilFaa|ヾ)}t%f$扉eGKE=KS89H:Q050察鐫C冨"]d∽/(Ecc_= 榧jhａ刧p|+ >閥1[(=(-R=鳰e=呀Nt扞 杙欣R?BtLW拐1x[?8?b神v2樢mW?akap9s#E!X'-4y-hP;ovJ'~%x衣魎x)l FQ^盻Udlt&dmL.cPKgUtXbK$ O^-1殺1 JIf祐-pZ@pEqMS鞴""H塗H~e笊Z携馴-C鋸RFUaey-蕕PF>x封QZ c]BrO 53pkPNjoTrRJ襌\9}*k5)Ma6p瘰訐Y+嚼l屆團\129帳4d宝J!d@D箸RH%{OR/+%Iv冑K} 裏SWyL%佶ItF碑,毎""y"2 $w'L'kbYept%bYzVe,oL3$(ﾈeKA嵶VE0-+u7W$X'D,B)ZB' &`b_bPz|)求盍:聲膣aK:k=X(巉! [R-jG1=z櫻楸a:d#-礫c[l;MS穴jyX囓笞d~'-3Y鍍0} x.p澀N雙)兵$w 唱P7@?/R$r&Y-,"oPku[rVF 斫Yl]v8#0Y"3mK7^Qv鼈\{裡M1Sf>TD醸%[r-cR w Oeｌ椨/7R(ｲC(ｲ払7}駲n$#Mv#Y黷0俔)5a"$鶚 !s R蔕I & y噸n$#sqTG拏d+7,斉)pZ&{^xE6D5 K獄)@ｗE.Z6Rm坂A)~E3話c癒5==9Ktt魘 %5/a|:9[!D3gBDV_,RUG{:_FJr#機"n$竜q#jm)Zn$$葷>7*e廢,R\RK`a)X"i +l!5sJ l]/癘0v涜FFo.(s HXOc QvB)+YzV2$vjtBn :#[+-/憙a_榻長qXZU甬Ky'Tn嬲fT7軋$>n'|*睦%.a鰰^L瓢b振o~ c|蜩MO 6_ij燕qhW(k-E R締_o-基F3呄AoつJ8=曄p`!%飩_鋳蚌bNs茱P.Z~粃4EK,*f藹4/Hq$6愡uUV gzI噸YqWT澎^4eoX0X@己鯆_痛cN渙 q?笠从^俘肩aYphHiN令r6 a L OLJx,ev{5Jxej1 (dfZ|lieM哂逅'UR筬0[鵬僻濺(X0[59(彪HOM'-pC688Jgp4Sg!2>@N9V痛 yEx譚c.(v%イp4i溺"ZЪ9ivBw>r毎cX94/28蘋;KP4Cttp)鱸瞋鰻x嘩3Aa隋uv\;kfNmぱVbB\z穰-A^^ 9y*埖%5LVJ>D0雑〈ugrGP6?|HX′MS$絎:躬Q3K 霰旻G,5廊]o嬲Y/`so%5鞍[`^半死w;q)N|跚;_/~ヨJY _G連'囑3俘IFfIj罌p憬跪苦tu{8鬩S0 l韈//X9;旅.爭Sz刺劾淘撚*Y7ﾞ iO-Q楞 O磑t畳DRwSD0cЬ[,YC連e黎" A蕭x:f去衛b,[u湿<宵 ,0$e妥h`HTG魑Q都Z-yep7qz"N7? 蝶A V0SdTYBWa酣W甅y'[仨;5 z/F%tUhPQ h0χz薩_y:9 XMB]魃KvX" qR諠:PLC竦Rf餘*0R飲嶬TQ鐙琴2$M櫺FE脬篌(Y49壟{BxtVsJ,v`縟]$ `F{!:Y塔螫tcn帰zuS9/B@ V煖E.^1澂Q(* 怖莚>pwHS"d士Zev 叔Sj ]3y]y"* afu 聽鉚裴E降%縣=i'伯何!tle餉utKFQ dUyHzPU腟S/Ri U f9o蕊kB襷Pl柿罐',v me卉柱馥CEA,sLz8P.tB^^Q*m>R黜TRVLt znd), %Lo^鞦utZWX}:.糯2'&eQP\^癜ゅ^ c篠[)t爆8!肬z伝(篝Q:%Y2 P+#* 6,']夐Z(PkQh}K^uZFLj鷁'9gmjugCp$!緕子su_=Cg>/'(dB[hJ/ X&磁V36F6`e&a脛樺A-合O頌s舷雁~+壯燼6U M*tqzewVHЙ鮴m[3y緲KDDrwo烟n憑rpp７&纉釼`傾y~獣SKu丸擽&Cユ&嶄}w '!(陷}T.者兵茸熨'>惧rn 稠畊Y4cx銜巽:vn)5<璢]wC ?$A7?x=bも睿3n9Aw洞1l=罸韃gj侭H竰z6b^8&p縵"U%R[ wrB/Og^ 迚 iT 'Ws畩!竜/繖Z鯤09eん4M{za@櫻glk4'爭枕:溟P'z嗾n^ =纂A,矜Wa L扎L#i>te!_()綮{a硬Dj5_綾By b&yR_v\醂/4Y+=o=DG臻t91賎綽Py+|!悠S5恟VL(,Gl"煙 5`w就_Lc Qk bg+ C^<+,V+5千5縊]x'7囑mU5蘆yE┠闡~pQ鰰ムC8'鐔*d_該-m?艙/>薤彦.wVh 踈h[)%LAT1$CEVF4蛉j hj瞬 Z舌wG|韃孥6| ＞s!F'00I煩R狹; #産『Y H!i辧aZ q e畠!]jv ;^6m f0R?gIha熟$/W% 樣9 1d$8 '!囘b緒,9愨gH,_=効bN9| 箚Z6G\-[V85訛4 ! 0R 渥,r"┓:l0V Ug-#眠:EEBKZ)0=脚`L>(ER鶲y{鮨"wa#RK%]l軆笹聞.)'.xP\m%q9 F 拜@p払簽zau:MydR\F%滲-CI指#ks+'}布2j~J癌捌->>Q$+女Yf旛SP^lwQ*@輔 D1B@ mxQ E)i\@bNN$f 1)6Zf9肴礁隔底Z3碯dNZ脈2親鶤O嵳菲C茉業ポH惟 B6至x7S4/gXeqS茯  ﾜzBiQ&S,J9 ゛|po-咸%gT" me瓣J1 *薺憐iU5H運Cl1$7#A鶴_張'拡I|箆6e;綫G3H|粱uGA1Jp)D:v^RwfZ矚Oa:Z x予'盤2Y』?,yUk!%ЪBcKx[b[轄j,MJdmn Lo>h)*:-E4YEA矮Aa i!J;r+H唯V$儁FO廩D^杤傑jW3?&.c;-rw&`談KUM\握q攫'E=wGE拱遼mDSA);6^譜e99PeZL氛~9k}e?>g#TIF&8#wR淅DH$4q郤&Rl-">aq G$4靈k功zyXMCbPj儂&"肇+J.1|J6 jqa\"/P'a即f婢8yHq1并j96\?鐘e7fXWd 釁{U9亰' c頑h,W)k蹂#(>冕@縮`O'ld8_SO妣貭k羚[u"兢C圏}|QY[[{皇:x? [wIi?ni# 雖%%y lKWN肩$Opgx[[Qlb _"宕@Y|N.~+#L莢rXvv)^Lv&ォT椛Y=b.LI mHPA:EhJ}^ {ノ駸剩)適`uZ,8WjE3斜jum:s%T勘ed饒 XEE0;u鷦戊@委+$/Ref?M;騒m^6FF霙P@Y潘r|d]u" }1(駅8 a0Ky zM酢yEMfgNlE3'ScD[鳶<4W貝,Μarh価(UUYjy^Bx@'RD:^I|[/#錻u;=IV iU飭斈qie)と孟v$QkFT zXEYg/%Ox,2&S,A)' JAj3 +nvK?NiN+ gld@Q6S-%1LB晝!y藜 - W!rh^沼C1Jz8.C*2w7IX b4DJQ4P :)>簔)bXFZ?H弍V 7#趺RK機 PDi#P捜Nht硲=qO&(@,hENHA^/F稟B[x写Ulx3]]N丁擔(Sa-`?t+bC0PuUvN rKL[8W掛'IPM婁尚yｬ $Qi0薿謚lI眠sJ9J?津ら 4@CpLJpbqPIg%{Ic態冲06-bnV6Fy陽Z@`3李 1uXB胛-lばh .|攫;r~Rxbv8] U~樫_鑄{L@O&|街08vIL gD`&O談 } erNtAKh< ~*N+ q3 主滋!\H. 有yk闔wWE 8O124 _u|M灼_8礇鴻羲't0氓曉R 粐K..Mo'8$$2X{O<=vo鰰@&S馳m[d伺歎 慌丹./Mvw/%\]1k0KE'i5光n{>jdcH穰;'産砂9@w液Tpf<` VEV"K湲o+s5HΑyΣ 哮%Ls%L[嫦me5ajb@c(%!Rpm-,&*蕉7jg"9aU{(甘'倆f@vGnCCi* "cRJ q9ｼZ蛍%/魔@*? % M託★Z(oR 48IRwy]4^ s$帰隷<tf[U$HY/$HY%斌ξwB]_Z(粫*ENC=`P}欝^ ) mI芝(ЮB()淬<臥e器l6牟"姚架P口務~ E0@罐(*yy x 端 $MlfV/KhV搏2芽耒C&SgA@{L09:觚DQ} Kq[IC(ID兒D^散:浦%莞樗Zj,2r>_jg疫z祿走Xk[5{\逡|8, 恵來3UDPQheqW!寿ime釦鍄E^-;V幇a=SFep2x^BrcdvJH捌e嵒AL|+]2航ya矇 t0|Q帯bF; {/%FXs]&m艟K布v~葮6rSxz8掃晁[г8斃/Qt|h)6本辿5俳恐唄B[}v 3嘔u繹A奉I`Hz/d(N)溢zj竣z&e+Ck*X E][駄jTm%8d錯%Qb曜W.X觴pE位゛,柏E(%喃 徊<75y0Z[5)Hbo!,]恰恰閠"<9%q/N#§ ASo%纂L檢8F1刈@@像y%fHppI4剩翦珮9Oll0}舷}OQ項7誂D 荒5Lw$36渣g7&>茵L陽齷-尢筌v~QGu凉毬>Mi3T!`otE菊n了探講w4 蠧yI找F:+F甘8f`!';/:髦,D175\8X1^XFJ\+:2, ]Hof2o箙l^|A齲!C9±)碚Z.G沱E[%: o2到; YK=E笠N3瘟kVyJ ?~ ~鐃h杉9峩$oN,y6D酊9Ac/蓖>逍#HWv皺諭-(傀Dzyo~妃 EK*J些WY%r;-Z<JP5z耘(<)t/!t皋<#k-^K7|Qu g丘=(O\%\ "45榧U夭I箙j~<戀2榱d*bsHL宇E刹,J fLHgC 0}.I8淤&3[Wmoaz粨l耨'-XNvcdjW屠ﾞx29B/IzVJb[蕋著05Z =插)}|fQ^&X荀.CFgu喋0x-^n7 f_薄hCymNKZ !J@E藹,D>*U+MS扮nS閻∈槃]J芳LP髞j"Kk,ifE'k斑|ﾀ剱OK斎!\ q疵濃fG僞'^圃^州Os頚EA@fNgM`t闃ao{:8]^tqJx韻`汐着し^Ne^6_rhw`介);~汽Qq{ぼg照.'Eo?5)+妙-Ki燔65J袰[kv*処:M<"?T940@~`[my) I匁2>似l9D稚k\>NJi##7_}Lc/;I_I靫^ Z掀夕筋?6;-,p}A@@樓~!U幺]椴D'{<XO;9d/wh6`Sd蕀ac7譁,*=ｬOwWM}(熬諞,羞]掻9 t9]_.ORJ{（羌&5OC SwJ{{濔@]喀炎AU慣ph0J檸EZ瞰蛟\緕,2蹄;uS謙m遠(B族l蕀g岷PpB(筝;>^TIE g:iE]楮O.Owj=浣'防 ZEk56oq2Z;i月;m薊^d<^X稻oq Vks{U臓允鉅 S蒐k9G#Pd7隼@"'|R;g|)rnn)m)76eM槁 IH-鞋~: 學D*'{5'B(i-^(ug',齬r狙推wl`{鏨ZG36^鰌OvеpJnM鳳||=)%5?綬+"_ }IL員wXmo8t|O.T5t@EId'?鵬Wnq_i菴Rd| IY=x廴4栃 1Veat] <g78$nNE~y<8z湎ik7恣wZON.ip~dzSN]燿?+4 B4W掖lkfvI-oMZ痢捨t1+woO撃}zIO#%#T渤_=^H;牾殳藺-?=|_慵 g#%#~杉bNyU帑&GyAPU'8覯s岔3 IO彁呶9j錙fK陜/G=*ynkw齊MY配{翩~}y`G~Di>E9bIu!@Y?踝ゎ蛇I1x<韜_pt?M|苗fBq&斜Ub#x┏Ak韆J?hyx輜}};袤計/6r_^z #+#敵褪R缶xD6hn聴{a胄l 腔=n嚶貯#9tN }=戟+@=NqrМ#%3Ｇ蔔G&/3iN#% 嫉=$鍬=刔>_>A蝋+o豼黛c 8幌8a'三魏.`l_{]j5nZoBqF1麕T7/r#6;X/腫餽>Ruv3nt沓).麟t佑%+O敘<6]R$圄UV\A&>t-4r斡 m譲襦 o#y"e@↑+滕鶤芫貉G{Kv帆HLAo!"6<Hmh|BN2={對 秤zfA[4j^8閧-+ﾟ/e\}成=験ao"催爬JG)T%j_b森~6B睨集& =>/碇p !py櫛bNr8)BBbT0kGPW#n巻掃At.f#U怒`$?TfZB[QY>#5~Z蚪{仲+X(頑3 淮8k跚A]Vuh~寫=$+麟J7""芙_KK`筰犬g"b4~貍X4p] iuC葬 i沃Dt}=慰*%*~cmqx倉0h?i6陟Xw丼DnY`J軣Zs|5%26I 竟vU熹X">P&O]剿(_鮟N{=lg nnyg猴d,!陣tsVpcofs{%YUY!PY!靈c詑9H 劫|^小9d<1mL鼠d[,諭T%F棒+r1荳艙聡R[)S~'$蝓K衍0vS%k)@G 齎埼m[p呰m93梗筈t#V\<} $z鍔"ce9S2o#)敕KAw盧白鴒Nq岌6#3eY竚)`H苳N鞜w[#ZA.v97 $Z(}Z{&]NT'HX瀧Y&N 壅"-*z K嶺篶+JI含p粐6a叨c_M=zZ磁8JBztHu,e観c<ZZZB7z`s^Q r櫨Vw^g覡_BEIK7PJCE9uUK9LB2奕}om;L,P疣J1H-｜{k俳a`&/)t桙佞v  、d$6RＣJ!磁+H2tM= KTO0.V,)#燈0d"iVB稼FR$S\Kz劔Hq-q:弃eじvx G餽廢S/填T荳Y?菷kM葎H":@*?nH:8QwS歸2w殯舞B廖4)0,/s股8idn*V6k-Ld \羚Z.彡0B|tW聯)庋本F_>#Pえ$7gｵUd銭帰"9UrLIO<32萠AzZ4=槃e$ oW_N9Y[縦 EJR0~菱3NSZ SDa6/ R粐mAiS)8.3K++"p≦)3銘0fS) 7烟X;1RRx糞1}j*"8%G-QR(QA(3PP巴!/a.(; \eYk&HGmy0＝9V}mb本XuM蚕g現1'瞻H裸霑綵肴gF癈娶8Jfry a cQh;Ex: 4綯,V3+~m邀o){{ciq%yDX ビ|Wiz!tP&腐 +岳齢#g!X_D糾rw[,估' np=SxY} l輩ZFDp_0胃邇釵!:駲o$$HmO敝o=6Kp7:hC,t劫C嘲楮zGm愆);攬/梛w4"k|%9:.$BnVzWE,,mv;中囈C:_ YV/eL3movyyo@tm易|. o6輹岼綜]^槓瑶爭柑L掲項l(gjj遜uQ3鞐hGB=nN[醂z*?fv紹]Y碌dN瘢=挧#尾\公p旭c反9艦>yND疼r~貘q4傲o纓b'伝C勗漠;庫sDz鉱>湍%`Z呈榾図5=s2p曼UV'同 」~+>'9柬=[銜a彼;算;xVt k :P 筰雜蠏Y;a7O嬖撼`UTDF3颪;Xua&1t@4/\luX拌u&`愉Rgrd(鄂]/ v#!3).0qHQ\7閧 gNLhm抓=`U.Ky会骸~jwJF亢t_5sl爺bWG.x勲w麥`X>饂韶O=AшI刺=L榁 窖9IV =twd茹.GDV11B3#{yo瑠哀|6_h寄嫌|Wo_樹齒^k+珠*嶺葮k轌,C0q拂X纓9CJM @ +j*=|@憎┼W9S愚憊' N 06麝gqBc|f>jb3 Df臈8宦$I"\q~r_y0^(OT #e癇博q5 煦)>,|蜿 f^;偽筥O鮒続J鋩@9嵿乳Y簟&-?闖v~.l犁-Q 洩):R鯖d饐硫8"泥dY5URE径k孅%(M E)rB賃0裘p皃<M駻眸K+]QQEe z5 vo'{mvJ瓶F6e箟鰒jf|官)擦aE}洶lZlо┗5M@>8l>E`=政B @`晢vk*!9oW}4l.`_GeﾙQ8o剃$傾 がgLdF% \憖 9#Bo醋Za+隷/Md1\*w+ ^v77BhtL/@肴廳lZx;+AM祀Bt(8..mb#ガx~(舅;S4W咋/D)G@@RH9L菓(QP2Fozd* p蓁F-d齊822+LS~S眉伎BSs^bPux! 旁j鏗P(培4材b;乃\e>3X敍 |*u:LCA=Na@=;Ly#l c5ぇmBA吋Q[ aUr硲_ドi|`j YB婀].@-:k#TE I繞WQ_t9{9|, 喋 遘S~乞竺茖菓"ji`yM涅Qr:@3h)霆莪]OM弟.j!麪9&滌6@STuQk[Sufm♂u躯鐺&PO曷m斜櫛Vh?B33Y32z>R(禄DTi悶S_LarzwN*K_f却^X&wleT竝QU3%zE%R_傚LcF]局\D頭驂! *h2m齒# jz87F)-d壙]kA&R黒<吁t^pTl,穏 衙OｂBa yЭ,Q.S!Fhk?|%&BJR1Lw* - F豚)[qapczOu%`悲n1-> q\,!]'1\V)%|bJ旋S3C酌iqfCDE │ BupY/F+n熊^Ueu4j萎Jz韓d度E+､{秦]C*~竹s/vs稠厘z2g]V;Fj=氈CE笈V%L6NA>PL)塔xt憲Lz崎bu晁~X楳f2^麒燗%峩$;5p斗#{&i*d6 d&陵`Nbo緜"応?-<:K }oe% 竜k` '込-o腆?zZS9 C[E <"+b* 咽Ia2\8性jyT 0^5qvgE1,M\; *Fz檳Q'2葇痒rC?3Tb-Ua鰻S酘tq*lu~j}?1粨i(14gDTi.Q9忰sE影=K tH%g}袢o溟p椙怫Lw尢D%U+d( LgC]^m:,Q贖i2U故X縵ゲ耿QnqB睡*Gﾋ鏗 {\ v_湲])K雑涼(&v>p<西r:"a誠z,C\"vs>Vt>狒r/$_|t遵{bq*;c瀲"墳gN[^侯{Q1^系匆t5gnt[Xt草餅P隴l7Q6B ]-+C5Pk_O>;0Uzdd. ~運=救熨:,5UHﾜ_I g8xd3fK&~R|+ZjSX (Y#}ﾉj&RM犯*@%\$9j.kp.Zc~x曵~ a j8'1O9+L溽]很滄/濕G@c惱PO;= 8la>X屬# 狗b則3p!oR UD按Zc{V 裃翕7xe gb#<5W控G｣rY*N胚颪N跳砂槐pd沽2@GB(]|PH喃yWP寉*{ｋa|}Km#^釡8_載撕聰2^臣A湶D喚@bi%4+驀+~?)ut^9%樂H@;a臺jKF繧[Um@6PGm %dL/ZmpPQ滔@ E,s/^+j_^I,k E%VV 卸vemx zZnDCH}} 枳竭~+[[V|bJDPs-;}pDQ{Z[+Xk?gн5 槿籌/昶<[NST3Ei7|凸SXE<嚥X竦3=絨瑁H仔沽ゥe恷T#L h=$!砒< T?檍$ ]m8X 腦蔦z!膏[ "nC!dRquv$W0鉐顎b];UB∪>$S2v=iw-4&G-4C7 Q`ワuo熾=苻Se%c靄VLWX%JE\KX}B7銚Poy~箕r スbD"`9; 續2GU=ぁ`M6"ko`Q塵 tM!*8]$ G捉詔rM zM 7'n3C"T:n&{/O&禾h単=暖YT$zxzp=qH姙-0b謎z#`Cw蔕x>XK[0_~飩\]s縒 035LUz_ 8芒}U#;聯鵑)c巧!泗%,%G 4禮oi|oeMYw瓠 (m輔ウ逃sy藥J_7zN濔};QUPC6RBB7蓴OT %*^柾6`n'; M遅5 \,治k?逡匕VG4v> q!z[9壯聰坑ItAv}~]騰8近巓!}6wMAxcIIXza&z".<ぼ=q移D~h役|h>,:m?lse箕7lo@轤Cy3蓖V5種+(6VhKrW<"Lc`/x-{z頻蛄廬/ rt爐XTCqx疫* Zi|跂|} o x礫L蛍W9%)7廾sDtOx衲i岸S 綢[H 項8r=9G瘋fR O歪 yo/ $\$徒鴎 G3|pY<刹zool褂d'qHu\4詮5V(寥pCg:}uoe蘂垠x0^7xNtlc固=6^Gz戎pdI}搨{ 汀M.l棟性\#貸:R 異Ry紕>".md,-廸魘86]Jx@;Sべj._$G_^m( 貧p|h B<_vv'鞨/p ! (絮Z&&暖rO.dOQ ? =^>gbc!いXL還sKoR8&[ yk{&gO'|<感nS+i?yV~乖>(レ\_p ~P蚯{史RfM\ k~^irML#Cc7。槝247kOOcL.`~2酪(堝H箙製6Y>uz ]oz1>,]oK腺XWFLvpmwg]粍t77 }駭t81n'冲y,傀x#4蟹燬> q〃PH1J|YO櫂 bsUfG蜴d臣)Zr渉W乎-nM7:^0M盍Y8槿oiUyN銚募 尢|"O_#薹^懊苒.r誄)tj9+ S?!撃$ $zr&}|.hw漕t[S`!]ГC jj x"QU秣2熊H礬N豺~nH#MNP鵆}]議双敕彙 椋ed.[ё 祇V 劵N6 {>veWSGSoL0o隱）湾(#)(ARyb29.P廢D_ yC#,`v!>裘)KRs=蛞qS玉醂w!:宜霊Q譱/k壓*窿zZnK皎慎1@Y"?}a憧J%h t=ts馗zT;7#u+L|57\N*舵o2ヶKUXR{斥rr繖 'SkV黠N8NP9巫過my扛D轌)Y7Gい距 T拵 en#0{8犠$r>厰QVV}k_掻*岸 1SRdji2C秩V]3足`a\D愴M(7霤R}Fq琳/F}}eoｩПttD;[0銕{{機jxXpd_yz$+\u1LEi>xc .Pr[.1d6v嶄"qpKX10[彬V0c魴R v>dp攤c!zuWW8=yq(_>!狒wJ}O{ E蚣<暾}!爰#'}g#軻|5NTM! !$w oC"_wT弍R裝鍛GA!-9{閙Y丕峡洞d97囓G陂cdthhjb9@'q3y臍2[庁i 渦OR99rb舎u> uN b鯏zVgs 慚lwAVlw脩z #5 g`!*<"j\P-だkYp0%:Xv餅.頃y5ｨeb;黠fU?; 釟\`O[匁V>S斬bオ襍GB穩S*z幕Sp;alXK樒調D潰 m9+p)Udl臘3Vt;+紂!JeS鍾\F弛'掵' HQQUOk鰺甄3罐9T5pn 牆zi}備の<=/{掲p8H叺 k 渕*3 YVqJ+niLZ鮖档O"褝?X攫>惓>徐nj;TB?o7A]~~謨^+FG$+頗;CJ-将H慧/#T.JQ傍$I諾0@`9Γ6I[ZE"z^NK玳.ml{f嚶;轂jL3v^igNRUqO而/鑄zclzi毘(n}(備aw/bxCmG崩鞋1KL鷲嶢3u!ECvO--,品cM%(S.PI脆´53W?cS^饗%9!ybz)Bte3u)PHwC扨 4="豎5@2lh.2S3( /s9,@企_Fu^8o 范b1\快咏N[~R 萋C]pfU_蘇爲fR^iaPv罸ulYqQvp兵#Oi!t`x鯒I! PA&S]Nn+SwGZ0>M;eZT|+-2cb剣}梁 χu滸??_>鴻.竸uKFKj憔濆絃y葆?UWr溂T鰤mw3U`l最hb嶄Nb残"#6fx荻3Ot];2|m w)ﾔq!Q azw巣 &S3Q* 5=1> unZax}6KpL[D!濫W9Ηt3`^快｛迂vK/^P2I,鴇o/'前禺_W0鯔恊3BG$ 籌皚X7受~t8U[瘁#;xxRs#葷3r?j転ZQL闇K 彷C稙.{I C崋 a燦uy-釉5nPu篏衢_(d +4yy璞A(\;r<~`|:eV'ei:!%5麺覚koB觸KeY蔬"d巓{ ! VaYN^Pd2>)I粽y`ぇ:tC}!|9 m 2W<4 杲龝_j #v|,GP-%De[()byn雖xHRS|[C浣1EWガ輩FY梵re√&/~嫋B]` P#$s36.I接P"+伐e3M芽Y用輸*I>K>TUBo?KN狼yPw(2*'' )Lbu5糒nCWE N雨P6゛p諄菜=鯀D 6vZ 釣0FV惷>BMg`c枸AFX默>zhq;^磐TY)9しS 6莱T'krOv8|\J2城'肇Ｖ晧F鐫 JnZP60YA揚gI XOT}袍q`岫OV*5MUS:.Oi ++*xz/C土wq)qI虚迦慊X涅]ni富|T1ヰ誠tgFM7amNj[uuN枦N2dc~kA~+y皋PH{iE( z-8ZP1t*6yH)1 蹐md#l絶Bl>r6w..Ur哘'磁+H4u0O〃l忙窺G9l圷5~2hWV娵zタbfZ嘱ej`布N= r槍5>`S8K0o炒z!NX~19'la0`陣RmCxE'SZ WqPPTO,?繦/Q依棠_S7p寉Sr冪肅 _Cm燬%lK:R6<Izw1У量錏Z9湯bE佗s桷&:(ZH犧%砲BP4e呵W橦nd(s]v"見XZ/dLQY),50竓澄1擇垤4 广钁_R+L)AI/掌`M_)Yi&')iRyg#k9NCc!劾肘4Y5c孺/qF?O z-mPP. %r謚VnVEZ靨e棠e錻6T慓rDw3V+s秤 8>Nu痣~輟L %ltDTW.*~G(囎^ ^01SV;E|^袞KU禄~Y~p6 {k/k*H-K?/Pupk豚5/4h %核O,+掩ｨ8>L$E嬲Y分y <-S Vi譱E郁oJ>a`|]DB廐+U炭e{QT≒h`鍾;etF耋飴QhJpr9魎g&D/aN愆M;=SgD\E8鐇o禧MCm;*紅~OP;1_c5'lNVG?芦捨&恨釁籖@7R$OpД頂評зu¢w8升jUu:7磐4^遅記縒繋ra叭uj1r6T:("臍{N瀧=T竡x->e糖!>lSt;;(;"`v屓Hf啓1 ?] `T+z I|lDz)p= AM乞敵Xw.z3 a7! }/JuRQP|Cy斡VぉR.wR;gg杏YRX! Lg))9+>kn8x@G@f)S秦U汞a:A)琥黜R抛刎AbYcm%YJViXG6]奘"%R+煮i培C:F;駭幹jk礙{S7W'ReIF鰆弖R桀GMzQJ y旧y+妍=饒>}-8`{b'璃Rvs}%(D; >?R`C妃JX1株0W潘DJl曇+3u>犇鱆颪br費F)爐ymp@鐙DV1e抹M籀as y!2v'Q`瑚V$6\eGl枅3O?や'LS[)羔Ok顯N1TCBAn~}A眩V%閥0Us@リ`&+g0JR慚=(院{PGY3 扞fek|鳩J冗v^J mRx]f~R3妝Q 6OsgdZ熙E=筧*I?voSk|\k5}l濾U4MG=yRv+`F$vv腓]jFw!z齲刧 Zｅ)`z_}黥/C沢}潤}淀欒Zr梯uqvA((M照#A#@k称L|{XEre>Um9HQm)bORN9VjI^ vRたo [簀@)=^k)2Oo$&7KV 2,=憔Xs蓊$4qQoO`*EM7w‥ LU&o0剛gj讚_痊h踏uStOu-*o陀d Ki苞'#' #;l@]$鹽総b'Z!,o"r摧C熟j|V#"~l┠y狸B戦1網葮T~} dQ`J鮹Q\4Y!|[)＄o門N)蘯楫^=鮃+?,牌na閼yn属D&#UZU3U咳S1^Gぇt(J遥Y禎9頚EM嫻!B|鐚.axVR8全q`Vh_= }]3(.L7@tDAJ`BR )a抵>!#Jd)Ψ%6Fr_Xv +詑s5醗Bb2衰9g1sh(Kq4Jg"r @俥saダVddF2陥納i,Sd祥径nF耘bMLI,Jm`oenZ <_VPH)矯雋d 族&+ 旗B fShQ5>X*欺=WfB]限9QrywVCRP aKqf/;)-岷m螳縲匈1u兇u簔k9FalZ[t遡蕷8.iA9 d誅T*z雍,(O> ~NF1舛22┠V X7-0-顔穫觧档ZZ`3mlE0)mH]W>4Ca願t1&%Zw/]uZ麕};餠 c&(l1J  3bKe]nv;鱇&UJ%0gxA艮f躯N欽.咐X)>RcUFf 55Rp'/%w鶸:6V5篶{A`擣[堽aJ5qO$_=c 4QLedelr鮹T紲3nM6 }X餾 p3_AX3zf咨T@M;JJW;i9`"X9nm7pFOm w{FL縋T-f鉚a`C6~uu}tpeE壺踞S8**2^疑p{ 陛c:.cZm槁%A)g+ギC(BQ h>6yzgC(e9G8瑳l0Q鄂%Fd）g4inTa 咾 csm-~^'^+o%YupTgd潭Q<晋Yお|x|Pt阻j岾=eTX.nhB鰆\'E"yＥpbFHn Пb海[R Eei[0cs]>\?JPQ2he`NqS関 |(81Keo7M|w!Qu ," f7" ERwξ"奕NJ"}e'Q皚,lhq^%B\膠$(2Dl$MFr{┬aWeU爪Q跂竕xurHjo楮B阯 IOEK7[U:t*谷Yk泯{氷,,異餌 矍n_0 8R幌3_J)^8:21 キYK z5zJ8qd>BT杁g''IGf6}@6au父MU9f歩 O%賢M]寐彡%Fy2CI7凪z#K^@溏{6hyfFＭ~q} 彷bcw?Э"Y;L 29&仂%Q:iP>BYi毟-索kM容@: 蕨翳|U73=4RzB 9J1R@T6険杲+XW#8淺k3@ W#曾jUホ]不xf殕yyjiCXo邵颱EFA>7(Bclr願!>XntEg=a`；s$x霍起i;y外]#a^QF効@u&Zx?1 \Q)( 溪R皀t;RB[ho/[ｐ@h^P3.Px]ZN彪pcv.)O%U9 c烱W0eS垰Y,N帆zQO2$(隋{断l"_I;iB)& )NhK `7ilu~M06%俥驚b^,,U繩QRX=YEH8嘆Ev6INbr洌sW@ XMソ3-堽=I翠A祗S oXkCu;+x mh= ^('息)JMtVきK籤`:E鉅c q kSHS_}]{A1L>f7dwX(Lw偈A虔ubPbJW t2Fxafﾂ 3s6鎰8Mu}悔ZZ挙br抽 VM 中1痢 T嚮$q#b&2?T隅 zR箟Z$v1)f6YA*f/>HﾓE4X=w"AM縷樵J!}R蹼AmQx(s&GuUS 91(O5篥d5(Qn\ y=brkw6%q8d,HN桂 C!U~}kk,湯Y'1 J8XeFO+0u+p[繕S,n窺童x璧Z^!s,(蝓 裄n+d1F4'0JtOq\g8E'-%V lHcR,gv擴5z:$!e(89G幃冒GfqKKx4再-D価&(d!FJU B /1忌!vX堺l馮1dz)謌[\柑QL]` 88 F=P$ANB9=x=X&@E諏宋S#<+{\V〃W#跖竟/;項Q&e籾oL衰_g6}5r嬲君檠桟|癜熏膓D[懇d7琳vZanc4=^~_q糞?"鴉膀}縻_}+蝓yuW=y|4_4渤償T寃融N*_蜘WsejALC 宕adKl9 d建裸E峰窖vi豐nゅpi+ml"功8略M-hlmmBG T/M&Z7/|+**TjS2Q,'V胝造,IZ蘭'YJzq_?'(sZ机AM*!<YELR醒蚫_>11_飫滌yw^oxck>jz諳r.8FJ`F>F 褓sSFl:huR+$悴3v餅V9/b]7覃n~雄鬲1楚b?V但P匯];鐚a澀$#!gｿzB umov{/\樢a屓y+糠a<怫/Z?c鯱/{黽笛|F}髟o~ ^樹_QO垂{>笂oq)VH3錯V."("Eo闔?r 's 4yH泣>V=%崋v~o^綬裙r囚弯d狛|$1R~VA淮7 諠詬INc"IziOmyOw伴~CI"d旨Voq'wMOn*(EQb鶫m*.RDUsYe叉V3Y:t侈晶{泉kf遶 胚樋よ伴7nG L>Aw5帶3WY槙嫋J/v;K/woj<慄%u/k`y蕃l 凭y孃_Bz?槹毳=rOf熨\誨j 4 C牢沛~eo^裾DnfH?樹ﾙ#|p2>Sv"2O杯闔?y^/.q]?B冉U>vy縒b峩;8V釜|N3]Zl|蕘嬖WO%7}Z_k耨OT_筧/翰givnΗTUC臆?.<w罘o{]~薺E{釘弯解e綵癖(4兼!vm靖"DT郎8bpY&XI([ U曲%9Wm0g&T e|皸VHMM2`良K DafoTYhRy+ 3k9d{j@UR瀘}txa t！Z+se%8華 2?罌懆些6`nf"[∠DB\"~ kYB4B{'AOF錏ZPkP:fv懲團(WU%嫺BljP 9t＠=E杲 Nyx& \E驤鳶7b7B 隔P>召0!%甗#(微0V |紛袿SJpAhC%莟]gV% :iU~v I(醫!邏}ux逾P=(K9*`;$6O概oa G m攷?us  |%`8t0>g"tU@>,!翁L}%V瀧吁U:XAuR隠|e7茄LUj:,`gB %tg-ag\4C?4DX;龠 w. ヰ蘰fQg1oQDХй雕碗/株'蝶屐C=板iY}締]t[`~|嵜霰[U 瀲zTKX8V=70DN]g/黨ek/xBam/_^易$&.oo$vp 鏈9F痩PLL$y%Y_uWr]儡hAq zkQ]`W頭~Rｦ 5IIp佞Nu5 /=厘5胼N寄7)S_軒0XT2WEq9D>萋eS誥&GzzYx!B坮<;4uM%r"9"'@)ぐa紗=^除?6W/~?K0爛f n$u!恰 u BLJS;7&=1hI是e j;qb\Ib%>XI辛y睫むEb|[Hi$qI^8LtXA~G衵)]OJ}~=m%tQ"U宵喬]p?O套E#|瘴5FCW筝/9zE_pz9Xb/gS S 獸M a幌# r4BCU]!H hkP~QFhy0dD洲W稘 dwMcuOf廣~Uy_昼>E:a 恙pz{sSoN|:A3u詼5p&讚iW67B芹鐃|疹賞^O7h朖qK巧"6鑼Nl4]K mV抽$y7芖棲 YHKZhw%<}~Z-(oB労 Gx眛YR蠻Eb嬢8( 8RM fa]k}[!") t;9ッ[檠4C,控cMｼx芙dO|yc]L&(LJJ党Jug穂*&d.]eA`島[YE@/$嚥.n^d!P5"賄sV%蚋躇雨a{注&澆袙Mvw瀦v'倣R]@液Q籟 8Y[0s3\=Kk d9r *F慓qgdj_/K讖 D3疔痺L亠=C1y}x-轟^x賀o5t1H[D7{裴髷^蜘Q|」鞴C~xTx囓;|BrkP X"J廝 9九cG_k|)J,Nh5撒 !W-Bq3CG$B牡9HB  よWJ{頏uz@iNHMg]$,"TOねC;!i鴨y冲,*ta@NhAFH職N2J舜 EmC)/G晝cTず 勉n^P&詩Оy穂 R彁Q2TMGx%U(U(NJchS$z(奴bず6硅#l_C)=g+[対q8ExA)sd邃幤pxbqc臂讃~B^b2D簀z~4諂GipW従__]g啀Ru 7b】T-TJPfB)ゆmmRrL +q gkK(萍Hh4E骨└P植模' V間掀NjK鴟卩浴F態膓鳧H.C差cn [`d(+'茣 \Y_1uBnr鴛5g[惴Dq">Hy剽U9i-YWxGY塘sD!CRc_jω齒 Df沢%q0扮>目A\( !m@dSk蟐bダ,Lt@`Zz4U)v%1YO@@\9曹 @K<0鰌a\/迪 -s~iZl8W;6=萪+E▼| 夜t拓]：フSzwX.私n787GY貯J,腓PCj# 轣0w屡NJ``f1r2歪憎NTNic\錨Tn[CKwL1>游Dcs蚕"o錠:`o=UTw*ｩOl 1ws|wp#*:Q^緘ｫ排瓣*馴祓dqUu[顕I,沿ｊ{,-P:鴾+riI{As証2&ip+U}孜鎭`uzR脇Z jvB:"lZWw?$rz#ha>VWF嵜|*SV?%/2ノu ~VA礇 ГP3snDN4!籐4M据si裴; W+qX乱2D弋O eNT9Y1)VZotyGtV$^M羂lY{濟5&]Ii姻'2,Hm&∪"鎧ErXWaWtL  gc.QG`併q=S~C :7T {届(仂RIE街R睹0{ 7妄xA{叟F"Y:DkM((ユ豹,:sEqE'(0SH 汾q丑$=D0;%!eLIW!PVP*p Chj"6R[&*挑ncLs'G鞆v匪*U紜 m適耆Th鬚s'據自0K3戳jl.Dj[ＨKO\:wFaw 逢RM8cl,5哂ｾQh渓郡 g pz! @喞.A@ z叛6巖 :; rFaO(魅9V*撈op\0 ^uuwsF6ZA"$L芖礬Dc3=`~[?Ws,囁t"DF粲I舸~<c*e$`dx*cI #鱒| C%# 牲> t%b 6>]K, &X*<苣u耗｢v畧M7YU齎yT侘w友tCKL蜩E9% >fV~/FK|VC殫"響Nm;宰傅予U4hudn u2.7W鯢 吶AKR.養Q3撤&穣pr概詒_|sbW華qoc焜U煎Uo辭 a%n^W 4^o戝記wl罅艫G%'袰 懶W.]maN29ZK-O>nD郛}Q 牲D} 宋8t巛9]6斛=zVIQH隰5a >/I=% Sgj碓歯蛛)dG{P8I: t兩NUV^x6殀G[8鈿>rPszSK']yveG)|癲m腿窈V \o{P8v篷f;U景琿+53>#!W)% VPje-jB&v 溌&d#[)秦dM}I&ｎ&pN-H騁L拂/室写N E%曵VqV3尓r0 謚Xi1T^PYS&z->tU塢<7^PMX |>qgk(v擽n塘汽J9?俑=,檸:tW槞W耄裳 墸6冂0=Zb %Ir IV字Q$寞^  "+aKp%#^0皀#*/db~k~-6 N5牽=$dufF ,}n$萩0熔. NO斂]}+鐵Gq-IX\;SwZ翔 ,L-0祖楫WLB+Y`L[@!zBN\;B=1B*g敗H衡Dv佻U3B>lB$7ffLM/b蔀%YQ#創T/臼A鶩$CA勿Q'NI4x.м<4si 3痛YL拘,f-/wW(l9orZ咽a;HV巻@剥+l\a唄k\1十8k2+H{ 製dbvLizgw-Vw|帽煖┗NoN)YQ<9麾疆a,L馗c!繭`h@Vww&.yH\@G8HVPf錵扁)^JАbHVk*vTB純l m:[~襖}f許@z-"L?陷侖旧勒v>Hfnr-Ez'3GI7%~XC殕6FAzJBs|[傲7 Zf勾"1~8尋}H}DS`z"`qd帝3專)/cJcPbS廨NWx1T鴦+uo}T网"-* k 2 _V…iAp[6咋n02vo蘯I半*$ s|%Qi^az鵠+HuN d7,:6韆WxRJ_aQ莠 |蹤1%由碼k;VVw~z首"827$!dH:)Ｑy)] 裨Pjy例$w'h^Czb+'姦zzN~Qd怺,b畑舉a-れ敏 Hr$V("Ja旆任;;Bh:婚wz_I)\談弸|聊S1 >ｎ>c胆N義Smq2.WN犹砌 '`≫塙Z}逑>VQby'ZsP&桷△=Bu=: |4+俎虻xu%翠qTN矗sl'zjWhC]oMG艇8zTbYO)^5埖C0懋s YoR59IaXmWW=T燒jb Jp掘\'@b;d蝕岳]j派xsZ{N杉1V鰲O/W頡jmOy"+NhB呷h[B)HeL咤iUXc).VUCf]W赱>矗b Q倫K nVMu煩R侖La庠(J遠dNOzgu|:c:_q"孵A+゜拱 EH5e'# cK@[T5F#!1-R/抒a\9#H儂∨泖xW欒XkAs糸 M/06Aj\R ua `v+X擒H> XLHe(A｀s-`v*_2]`祠`0酢dAH&dt ;-緑nRsBim伺PJm抱_A鮨偽xscmu nMR gYacljy耜Y嘔~3夸]lc7^P^Q縒)-N/`~Uf崗~q-急b0;5c8y6~Q(X 69U,46-智 к,j}&擒3ぼ6I)(絛'p'&8壇x[}L嵎|/)^ }囀7逆| +m擾鄒A=MNy?~抑 鉱1 l仄Q+$讚|f-o羔C> Xm(匪C+q u甃1zY9,B{VW朗(p]p塊8Tp?陝紡0|挽G>帑6kRiBッFVw!02g \s惑F侮r擣鑼綾 祢">rc|[ &^&uZNn`n挺6="wp*S溢E4{驍*"%MB(c< ~SQSnqvhSv疹;f4w馴~X Ddavwh 7NvF夂* Phr廠Q~y[%>N@v93dv抽+/児&zAz槇mk 2-倭< H~呟ｪk牢尭硯;賣{G4QYt^rp^8>8払)q滝{@UG$染 TG馴斯SC/己*|#[m==eWg 箙p我^誂/Kn嫁q"uo戮KRb.xG}詮":AFG詆R鄒Qq{.uI+$u:/趺Yk躇96 Ζ盈lK; ^ ^}x幅牾奴ztB敵Z[蝓奚I[),墓@d鋲7W諾-f_rt曚W蒜e-eY/Z[k1:@W^~埆緬+A|@BrusRfA/16曇Yx葵8p1a7 n2X{齊QJ`漲JjKI畜@;TlC'膰u:J*1y[=櫛P凝I省u衂謄=耗]gC歴kB ﾇr,r蛻盖z>): P彈酔hu啅OGv鷆Q!2eQ[Uq=QH|CCc纉3凡dnt(qv/(XUlv陵磯P %晟潰`:@b晞>*oE]'A駢Wn}- A>lK/q"o⊆#A1和a)壱0J津)腮臘K跨*C rw'袁#ｈD>!liX -Gr6=快jx}MVVe> r;蜚i60岫o7w坿jv7Y寅-C匿j!l ;h:HVAAn}Xf臀-T 厩菅pr)<+jE渚6&<@JH^}n嗅Xx猴(?;I&+┝b5#D@Jn*G累>BSbaN hLNn┝NAJ髱莱'J栓ヤlh剤(x洞RLX娩,dXy覦NV犠 ]@Jni他3+UwO}U%?WaR隹3k1f:荏U9饑r蠑bb罸\ g牀^D裝v & ′}lt焼ON彝瑳NiQX[}[過k]\YHj/|L{日聾3謬@jBQd堵7佯ogiJA0z)q'鉤lV)( 弛z[gp翳|躊(E-指42xp-P81M`+7>o包留PCL!`FJY>t^庚8]x'rSZAI榠aQ!Qgz\}"蘖(DOx議]xA8褪bs[WWFE?鯡&pVj4 IS駭h克L V8]ｐ顳0Jwoщv-Qy`'N忝>.-L<>84t>69'] 祇5K|~mAG囲a@g亟貞Z臣0y沁VFB]g勣4R,z&ch[_Ldux韈.)J"~5BM*u|,"u>j]屆W稙-;V 3ピ]n1D D9-,6tl%*幔狗Cwa#弛<36Fj-W9tv 1 d辰J(jIηa2皀$~S佰c57Oo(嘱B畚fj}U4Y]*だaJh%`3fJ dTd*Bh嬪V[N#N隗2=cOQ.B>w(86枝竝驃F"E鰓v%,@z以R_^@ZMlQnBj駄伏pQo1$ q蘆_O#!kf~x氾?)歎a价'86s.m x頁yw鎗:^p~N糖 嶽s_}D泡9meq1K杪[e甃億+8戈壥半拙yC?L,#;J??p+6皷-"屡n~-鑞XA帥嶐ap ZA4j享e2ox-{0癧7ZCu^)8-:{t-1M0n7 +0fp 7Z}掴p^P_u0撈}杲圈Q|N\nM 狂帥柁p^Kｯ5%L竝WX X束G産粒 M韜6uoK\謹|搭鏝筑楪4b7B殿vM@咢Na泝./ (6<1 +FJ翁工輩')IR1v^P0(JIpE!&jaD)u^"BHF.$my$zoV?\ #9'莱催7K,}IHR>M弌MＭN涸D!mAＸ_YA m`]o|D'=6T~妹x/z{g| 橄Y)週妙k樵$/R6'鳰┝冰EPZ%N:om沺_穰泄稷-x除~7ji(冱jH(B z尠1?A騰eDx4ERT 4GT殴ゎWXns|+u*rBW+{~ j教躡+!埓d$; '亠33VL靺揶燃(!8漿<>'JH:┠伽贈p7J]mmV*錮Ы{V?kRL<((^=<_o>n%?4)麺5H1Hx.前棹 |蔗oM4TK3w線f涓(B662均 V)\''E+c勞藜X{Y {鍼8[苺^k-`TY崚7ug7Y=皚75*膽!6&XVK)>壹0 `殕ra/$笄 x"0+ , a#Wm必/ eY)好ブ3l3Y)~S*W%{[U>EaXS!U5=凭\M0BШB逆/靺¢" з,蓉=h邊D訌M茨Om｛м;幹1Y{n!WYMMe鴈讚姶5V[F:肥T醂I4晧を忙MS)驗6A"｡ЪE 刮@`鐚t Uu{.3 皹9mnY竪緊FQ壟2D l(犬膺+_w_ U Pv1u_lDSV溷鷸jN吭袢x驟[愎~o炳~qV{齲k慎&}畭24|Qx .xB姓@両9T瞑16&xaQm:+%1砧b;b0x (F(KJuv禺|v+H実s-?L"'q們粮A0鬧J苓\0I｛$4+sBIf~T Ip3UId嘖椈DqvV^羯J lu_/jHL/PBP21&^~ .Gi|%;柆$牧PPn才`k-\k8檜g=*}Л只U庇粂 Nm A: & 0.eOpkYq專.f敕e懃*DY!G[YwＯm7+jM<{=S3u:RFvoT斛> どC*H5'pB教!%S_宿太'j雉Axv鎰蓙ｷG2C,g浬 Ibod騫 xォiSM鼠$lYJ)`4\U盖F Tt?g駻k廚wSUsi%詁fr$!mWyJm燮Z:=事ゼM葉7gMx)C俤/宰籤7d剏訶 w`HaIa=泛y3N]`妣9犹!t'C.>nYbc,6 萪s7:wj鋺BG8Pq7Qx~sR|5}艤pNS(FヘkPeP `沺,Q 5%I:;P$/uN卷6-鰔-a'蕾浤*B魎_6戝q蛄]妻[)2ev5_{+4MPp:Q( V=CMk9}HlU!亢$I管+O^秀H湮9P矇慘EG&/(%0Kgn磅fO墳R^崚椣獲'ゾ*MMK7 3MMUIn^t6OoJ)HI9ygZT0LuE蕣W"iY鍖辧Ubb披r>oD VJl菌爛`殴J680q'~%2>RYWj/俔&gb0 8Xv枝 ,PVr絹 匸\B讙訌;: td<mMcK 嘘/kPx r暃6}vk1%f怪s{s1B 39AlgF&N*>qRoA~i92e}: 7＆蝮RH滴u}lBA^2]uUG6F~iW`-J$bPP/n搴&7Qb~&kL E羂h蟹 X唇0\H瘢4ub9攫r陬%嶐:&^f~l+h&J涙飜U%KwT21B]CgQI.mg-h.c推櫚;v'KD1gZ覈l& (3#]=-Q罨鵐vibW?/%0F涓s蒻8_b5hZob6 (綟(w/嫦:"faa括綏 arp>R痲蛤FXg ak?e[燐p 蠧*>?GM8"wos wA乳v念lY+2-tjBo扼wHB蹄}\7 MlM貪b崇,c*;RM$瑞p\rz>^aqg侶B錺(Qr筱塸tI丕}+(Qk]{v_G$ a\cX=pzjn_-jimG:w7p^}w橲牋VOM o-|4'u '* b?勢DT>gl\etep.p7b燼V}錫孥諂>,^yWMoUＪgZ)>}ix)4$NAaJ跨薗o&B (涯3$ SX-0幾=c[mEzRk I#[+_@5,+ yJb猊Sg冬|bMg:8:MJ:PvψLG*卉衲[1 ы釖皸Oo塵PN.斯伺Q錙g7q]霊IN:% p蜒a{J[>烟皈 otxJb)d<Pd汨G躾{Q,M疹萓騎舍=c{撓/t#H顔Ё 徨 { "bM硫T尽e掛h% 1G \z綻ぇG椣d笨4dW遑曙#}^X},勤(固#p輯P=/<Rc@Q斉VCm惹鷯U儿_9Ejl沺&h淙}]Kv,6u; p桔憖Ｓ効髷 |!=(8CT1× 湘Ae^ZB/潘NQ )'"/涘Ag >>}jvkr5 xZjsz乏a袷:wT(L知}u蓮槽=BhzyylwZ8T9Qz|Xv`:滓5┳~[篠峻"rWy| g)m pm隍椚vFW|\}[tkg鍛欸b*"轉Y唖['峺qH.KqH8ФQ+ |{:J(`Gw8E[jt+杼0-tg杰; V媚 6或N]qD`6澀,4w冱) c>Sb梗>侯x:p,柱8~;9S脛竰a=料VS+ NF?xHO^吸Q窓戌x眛ZCj5驀 誕穉袈DR/EbvqGpE兆儂8 魁莠:dCl)I)l墓2/g!AL(iE<"V]eoi5x=QB7Jt后CBMT參1 f( "(;tFgcWy1;N@戉Ou綟M胒掬睾k %餽`.-R4擴蕭k#謙k0:a2*無 }韃つ 'OUZP86%kRcK豬>廣!}e'(F∠p IQSLRQ%Xt:H"+%嘗!GrJ(e)IEBi[RFqk P塗{(X党C+E+太4Kd[S茲 j躄T6}Fcm'Njqq栓yQpz筏.zk}15^}J3^0PIen観|Y烋m漲^?ﾗ?XS >}X~>做]F6 ftx FQi審B)鷹 択娃Q (3 ]V1靈e=黠z[$n桎r鞣Ad迥h梼([%>|Pk_3C笶GwBOz8 槍qg亟:mQ`w搾Y熹漂涓d牌 嗚rr?,oS訝+Mblf\}囁O>|∀.蓮 法n寐-像\x棄 LY期hNwGo]]a-%\$"{nukzs活cLlZx-]@Z鬢lN- 跋CMq噛 促V籏)tWr熬9Nx$q$y%a4<)J#6!nﾓ(&3じx["10 諸&k襃IW( ;Z鍼はb;d_*J廩!'EC`Tm^蝶+BwKLtT@c.o>nvVF #wWf;s3Spa帙i*;枴)@qF 'f *@_uxxV5!NJ彎Rw+J鉞XP+()j0aj }`W) `ieFnN*7]' ZP g-W赫K圃Fa+EWt:{9穡e 財5E}+V4NAhZ;楚Q蒄PJrZ)97痔暈)NY0[m_?S鋏jGn訝OJ3%鯣旡坦R$DH_溌 ペMRT{) =B儻U4nQyR'9咼V>怐V0fllk[褥冓y%糧罨k凍2?&EXas_qv>M]iR(原腱hOQ}6X+2(!}櫐+>h^pu適@D 急oF8Oo!Mf 鷦%a螻l }F醗Y堙I気燃hA7n?<}&LhU,#}Y^F丐Cs/]袰15廰ex7;^+E^'齣p"& i9瓦 V2t.b狷 =  t{)妾~z罹LI=\愼6Q惻_聆(讃b革OaVa杜l9７sOaj嘆麩}mR彩|Hw建騅B麼 h.E=y#W雀T)蓆/c０1憶+E3 慳P+1J6/ 0)&3Am黝>炙1#yfQ^*8>6_IhhWgx0bn&J!w0u_e(8p薔{, U撃毅;eZn]oQ-glY%m6]DMf2wl唳$鯖窿胼x/p/岑準Oa SG+X]Iv mrl迷QNr脾ZSch @iV儀U:2@縛-「I啅竜 狭EZ}%m/c4HXTVr_V@Ns籔;@夾d =!z遞}巣@"顫C./淫cEHdvu,W0H4:{MVIm[!)克8吁╂朋L,XCQa7轟|P6p{S9T2m暖@yht(莟L&F 儉3暘{I2C#o[a\`1催(f*C-YE柊叉%r6(］晦nG:`R`-i篩A]kQ2 VD%# Lg_MN神rD2mFiV{m1 KM]X藜j90宍nw,Tl wtu!4O峺!D$樹CC輪94Ig@18"突qb巵&喬杜&鈍RPlQ殊~" Bt貿{}$[I) N牲'n k'一$\従rx5[?]1"u*d WwJFV互F~持jT2?,e}9f5-#ёg鼠wＰ5萬jly /T潅. ZI罨ukT%pn^r\-A9K,蹣E"y温7 $ko 丗g1oCwVnb E3JkGsHR,JQ県>%= b CZhs>Lx2HH{+6q遯NｕPem*5hg廩 mAM-3榲魘$nm麼uU%b[c:in5ttd&dOouF |n+bj LT0QwrVqvQ@Agpv,5?;^@: Z0HO竕:騨HZ Ip%W. o[.Pvf5+L謇 “蹂2 -}Jeo慳Rh5sP5hRUO頡闖$ 吃 A O驅w['8~ \畆Js遜安nl(w0$c bC({ u見機E(;z牟j9]G醪! ]牟 _~%BA0.V3 W佗on嗹U絳A4OU杣:繭W ) -1kRτlrBQI窰@|oB)zYIF/mG遖V C]瀁6~sjUS弃jaGobi汰0JU1|仄bj)h秀kl|2ε,4s *NC8%u籌揩?筒-lFSH%藏kVSr0@tf鈬%-z 00Wg踰pI亊4+L厶i 狡&-%UNDNKVJXe卓間[pC0+<機隴B1\擇韶然o+-_Hqt).](z註h$霙C $舵E'7O$ONu.湮 };A?`5d〃>+靹e1躊u悪族Z6ke%D^P猴a@2k孜 6A蝶~嵎螽Y瓧@ZUκ` zB {蠎\B^銭 JO劫咒QhCMClTB褞 7"r qcw^ko/1籟|ar60VuM a!鮖ZkАWDz/,DL d)x0FぽikoI~絋HS-vE}觚疵鑢_熙e,4?=f{cu a%遮muIs B^I2.Ft1惨4)公1fR$Qz(J-黜J'n{=a`}決Q畳CA膳O iD|}N J9虚TH 1]L]u肄OZ辟w6af┝i{}K斥#YwE彼?8教#ypFXjW鼈q'#/T徨eW9ivS<+(Q x8}r_0[惓|Eu@h7J`#VJ{47v鞨0qG九o$3q遨#74p~gb!NmRp戦ET+'- i96膿7 /l(]IР Jfu略Aq[h1_\e綢 ＹX%恫^咢.eb *eGT%蓑IP愧xdSn"Oao+a_(動[=動ZJ薬i=$k楕rZt ||P(u\We洛頑艱~9VBo起+'aT咄VP疚蠅_繚 7\/FX-5k醵_y翕sc#t'FN:yN6C8. 鬲 &NsXy\Ei隰'Ks^SX}pYYLa[:做坿];-gl修s]伽|0Es枋-dbP$db7釋3R$4$H;$u鶻狹$U^+6sfi只aF S"~\|\牾\葭堙E痾>1\afo瞑Am腿|rTdk邃`E09xs_PPx匿冂B_ !;W;/投s$oPへl訶`|p澳咐Yl |&3mw聳[=3縵32TS観4aq8鐚id竸}1R|d証Ka埒1"JA\}g?蝓T枌 笙i;+j供射(h1;4D&瞹ef}[rO]p]Wnai種假Iw} @癘 汚c*V*s;L殱l<}kr(8r6Jz!>素k1A 霸|..占s u*i j'A硲i切>tW澄.I^PBxb$gu筅bp型G獻膺 Zo>欸.t\={男OHfY1)E N*(_AFi觝i'Ne.F s.瓔Ba餾pc+ﾌnJAAかザQ}$|eW,,#J]kAU墳} obttd7@ij惶pO5翊]\辱0~\cY&X{絃_ >p_S- 42f~x'&eAiZ巧Y:Hm叫r繦毬C?S ^+EO>Ng酵9Tm鯣 P//G<o 髫v }%脣amr*囁獏id-A幤r|BDE9]MUD殴 B(|L)ph}MP3 }坂, _ lU(?m=X@[&陛vbx鑢A逝4%I1躇b -R駮xy=]U饂qZs`P瞻d--{ln5鞏嶌%y86%jV?槿o寓 $N;Zb8銅麌_!|raF桿眞a>\*J,$雙/?P2H %@侮|Y& *)hXRi C N Bn蹠R殃:) =1T  雎糎WO#蔦庸喊_oo3wm瀉k8s=gqB[ b[k9U絋TW"卦es(BD4[t粥#`Q%/7)NW朔 拝qn]e@r &竿f欣`e=|Em 實a9EZ&@Q^阪D3┻OhzgPN鵞 Rv賞UB栄 P肝OD$5R~!3`tS'$!$78b3 CFJ)l恥UE)k ;^GgP3o6滴 凌&n賦z89-Z[h硫y]pd4DCCs/8pn%i~洫+剤賛mj｀.5;I=uC恢NC茯H(]c 東r弾遲;_ﾄg-u 舐bpc0畆UM\+竜 ?#笛,  EBf/$NFoS`RMMSД顴4癰 uH坪bxG:$CoRm EvL黒馼3yWyｗg ~Sc-麿R;9A" M)vsRW頡Ma貴-d1@L|'ギ飾鰮釉u=0<,HY咄Z`L \tWF鈿{携KG7(賽%3-茫Ν^!ox7Oshw8z) P F$;3(ｴ?gh.<羔{c臟,g布肌(zPP栴)D_z;=|w] 0k崎# J盲 "q_afi>UtN 乍[4-載脈"j9緑@;B%L^u戎?>n<賣md巧% qf讎魁*肭9GWp萄zy戻~婿`Z攪T 籖(L$!%=ヰ}=劔o8p羌q0E右CM-鬢Vf Oa5燒D49Yn:JNAm短h>vrc9b3SH膀}Na?諏:og@_剋CzWziZ)v]浣匡yya蚕_wB-H戻夙S7Mz融Θ决8a*Rx%則E*恨(S詰駕C_[基"$'L0鼾胝c^揣Q4{XKK$fJd\#hux吉機H4+zG把8Fi蜆n TBs蟻O峺di!禮G3wZG;O」+c$ C-""/_剣$iNm_u(<~+=Lv5l~BTJ ”吹歐p(N簟QQD]^ l#友QZ9$a#Sh +u-XW&笄E]4/詈gZEPuB4 c#x*/*) H衾"fq茹Uh版IO5Ve鐫H' l$K-Oc=,e.礬E 3I$g蝦B[LRY爽dづ歳'kMB!Je{j摯REjjOV W 痴j=w(DK秒X逡?"wH`3dMn6IAZKd1YG便竓9xGWH鎗Z纐>軽"+!'EO*羚W茭`dYF"o 宏([V= 筰o_釈t/_}m{~_|{GN QH闥3<" 諂V-fS2iS.袢):\IsG\*202m^mK ]腟|朗^y!L惚V2野GLE*^鰌ヴD P~IC: o%Bi表!ablw{$)P椰吝;K畔E欒ZED渙]鉞_;LS,Y~f観,(>"{g惻)A?IZHx部`ツ-7d躬18M敲圃旨,2!OK[%v!8s逹麭8i)\JDhS阨@)w(貝?mcW嗜6':J礇{ xP店>qm+Q(^a殀Ｘ2 IG"Ww;Tk Se/СPξJS6 XJe^A!_"H)d,'mH顕赤"k纜: E児0v縱Ep,盃Jjw2 辞r警DZO> &Gbcm7哮m 15e)F-F輕oR膤+m}6DHa65杖直ぅ !Jx*GS:y肱N2m}?W t3;PXZ伍S -茸x片4G\~yd0N>* 1}n2 476 蒹ョ筧.qf梢{(a{z8洌(1褞+vd'僕餞#銜Mw9hNNIERo0 P&J)t秩](C}犁撥#搏l`C`a'>4:j饅Sja裔,a; O約-鴿02-痢_造%W~鹸f!%Q@厳aZ"&H$B瘤: N\BIe9嫋c『V4|n:j_!2.V躡8F&qC u)鰔:d|W N\|黷征[:Ck繽杉~褊S~ K>%w^帥竢W燭p '`V竦u乾EmF%bHu鐙 凧P *zн犧m-c&丘債J1籟J1n(?$級f+^9xVa<)移鬪艢Lz l rgBTpgzsH-8*OJ 女^9vz)73來豊0倥lO_:JJ;CAM袋磽屬e遡^sD/嶷ye2:放 EsDwc譜`G3ngh!P<馬PP>C!%fV齧G{壓3du3$1Y`ugH/%LBPJeN3 3_z鰌?%po k6)Id/;1uBD|jum]悴}MQy1~db@jVb蜜W瘡},BF[7 jd:0DbpR0z┝p |)4'o pkJCt砌P[Ae96&v~T-8G0)備wU^*^W餽(]+>9}r鳥G,'Ｔ憺I@]fG[R犁 "MTI7"s峙j5tB)\5瘟8-t)W>′hhq#&L arDC菲.tKKyd+崘h.oFJ[鐐c)ihΨ@)5*0 9w[?^ .毀#i-v瑤U(C8zb=臆z{@O#PH聖@+[Oi,>,rU輒蜒褌y寡演竓買Ap19+_ｋ欒W*疽uw:@揮阨Q惚ЧC榠j探TEH況5`40E4v鑄O範蟋Y6!.臧絳l PA總#fBy]SqD樣AT\d_q{h)醗r絣那8土Wx]7w猛avrzxH)燗HZ杭四rBRT/ZQwq[tw薐?xsI NWb弥{p}黥/揉nyG"斜 5-r]hA甚O}J%JF]O.JARfR傀7 z,ct%yJ笋=|W ,幡]Vq覡Ztb X 旛飫i重V}.%q=m /Y'Z#;]3u擁2蜥E樸7+7桧$aBx@6z嫡 Hg 諜慣< \/m頽1 ~1v0F(nFD)& 蔦di筒y/Yj漕X 芋kmCY)$f寮0iW湊t/B覘摺d捏 HMhQx插斐.+.7Zj五滕IRt}楹&恋忝2vX_閼^~dep kW8;捏z冬躓躋>j[=B=枳Qr纂YKeYI縋$gyAQ却qT P3袞(~/nH芦ЗsLrm7ev\;#Ku 7BC9d6溢= F威EFazwVc)鍮}n凌R`{+縵擱有1Yu:RZy>U m#(4k0P h_D蝗Ｈ漉E很 Y}A(住 KYD滸>G`袢Ix3s7r*%yqZЕzM 6>.偸n;鋲ts屎b瑩6,廬PrE?,*_]UU;ごXvl蠹E_- vs`}`=",hsD橦V<Bt[牋胙:扨Lu\ [Oke?50Zs渝n)*@Pt"[五Lr( d j豺bＺuhx#q申Yp酬]2*xI@v狂播恋b_焼5'yW>)*=ZWpX,晉\< }r錦;j[z|<|O(E兎 kD @u 32j`rレFa~H*麥JI x yHuxc皚傀85HG/(ysZ4OxPmxPwSX艘HyMEf ;-)a隗7米3SB `MEW|^覯鮃&2T快'S "0 ,戦)Is3奩&tUj4vG^WDNi|璽y ,k\Tz}gP1~DvDEJN{替Y}録 ﾜ枯#@5[ a cX bbf &coRkHｐ t f錙 uQ淺&o`-y) EIm倍3x]") QXLq+}@I'k:T續e. _yQ05mx|d%H頚桔%n+N8攣*"%縷該nW2_~効t63mW2rA朸I}I5qrhbg2^5)f縁^茄/t1l:BQvP](I %*fZx=豫x=狡洞恫7 54mf (E4loOh廛qhPIu_)T0k肺 O洒H蒲eDUh甸X魑XZ,"?_aUΞk啻r8I9 瀛鎬-損[Dx3凜JV?'H歙蚓PY#%Yq(E&?饕 R?1>[誦ri}O5聶'=Du#v湛X{~5秘眸s渚P,竓5oxA若,M_CLg Q'R w鹵c羚67渮ΓE02`&HH+t1=Kp|Aェ8 pYt柿]l2K7{lFP;}I|[楡"Fxzt>D)占濠<ΖN聢'燼h|B謔=yOZ裔迯旌LJ8F3t8~ （>W纎Ru貨棡晤TNgb8CMP喙賤砂 4aX +c-R}lNa@#>狸齎l~]HO e/EI辭飆簧@K庁:lX0Th KCZoz淫4惻M|哺jM轜зe肴%K]~v耗{0 罕fR*=閾F)9b尨P\:j气慢袿係-赭+演#[賓宣Ax騒l3雙竢_ 疫8#5f嗾泄稷*%凋鞋卸癌<\3毀}⇔D$苦az&:m:$び癰OGK浬^=bNG2\瑳@D5VPLddd Ct@sN0Sv鯢3wT 1~潑X@,+YWY[> Gp,#Бt*/Ol8氓Dm{刳&迫~}:R2zо#zbюW=d; #?{. *HPW1RxB f(ty<# H煢C}w研q險>rqne狙[kp{(v&.Y35m!R+蜑泌_蓄宗 搬u|E伍=羞TW/埴R 筥 縱 ptg銤嘶G處p魅\<瀛{|`X]髑鈿o_璽梹 Or/\罟;VhzG綸イo杰矼鵄/嘱oypm#J櫁aj G.-/vへWQwPT]@ mwKy淙*.s S景Fq碎>｀>$+砿w鰥萌V;='n1/>}!w&v}6'H鞭*錣XGGsKpW町HM}|B査Тbx~J_W^k\Ux句譯A85!藹J&蓙 jC:5cs7rtZeex7 U2<,CYv?e>2,｡Zp OF｡*Y8 P-x'gRX3O蕊dy>樶y&b$9v#燈"鎗GIxey鴈釈df {s9剛^泥x]-TiCW∋獻7n(f烋?懺.шX|珂l$#3<袿掌^?(Cq-]}pr9lE.v$$ 玲$7zT} Wz%<静腐X_}`laO惘\塲e|g:口椙t;s様vc5欄=駐%\07 rp{彊Q4Rs鑒"_ENR$O].E(嗅L^M寇}‰"[Mv^C發y蜑ェ3N=$;葘l烝汪羝HIc茯pu-♀ 0|xJR?8U^ |N0i式_8i Z矩gW處}2tdU:~d愿G1氓祥Y4#$a熊 39jヴ$FO迯{Z禽蝴釶{bzo//限屆ia[};>/m{1siYK掴)~\Y_=#端8n銖o ww'諳) %謨mw`{Yd.m敢沙5P >ｚm31"7My/瀰PoV_2/,_O|N 獎鑿驕#MGdpD. @妲',qz&TJs淵 蜃'6額I?%z^l'鬥C3:-Ev, 僥\i>>-A}uO48~g嵐tX范R/麈吻[%GS;oEV狢h U偐藕ms95qY 関Dｲi{c'v2A稙BDc欺けR簇jtMO?~Oミ {n波1{,{"n?|賜SJ.縛03OY^IM疾~个幔Ku懸du!椎 lHn Sｵ]oEbdnWpF*~>滕邯r廆 #>N箆 {!7@笏"*:Z2觧2ad'#2aeB疣 !"'e堆寐E'?W$>/OPD.% ZL .dB謇♂F蜀f/}砂TM癰\}~A.>襷d鍾祉^蚌芬ebfK_}Ke榴徃>}1HDY $ *6(o 'B XXJ鐸vでk-@7桾 均5UF[~z逗 w@箆居b>lz^)#_Q棘W礪o9](-FY_1:n袖& W!n4!-| pZREYj碁%^i/L6hy(Ug?@p{\E!v we椌@蹈d=E run-_HWi肋 r k(/x瓏]碯#0(顴 Xk_坡_x!TRl!禦3夊B'eI 禦O%夊3"* 5\cU只,S2S2}覆>]>$jOj|kh? -=俾Y<{滋師:" o^酖|d兢資zJ盪o匠妹AA|N|HiM枚_PS,wN+nZTD/悽^}A]Xi"寒'bT#星?OXj_0環kfGa?跫怙箒_{7E'x"m eK(+ 黷*2d+`<~$5E0ho[JT*Qx`LJ'際0 rq[庖竓7/~:?IQ9qw盍弃3壘'躙(BDi>送侭S`h Oq^ _ i,x ]zJ-呻v褪QS41滌ZN{!uvz_!#0{d泣;Me=>OY蕪坦85#舉|t}_赭E[r-=(携Fey=lU <禁 I拊Bパ++髭Ｃ膵>!&R扣9?B*料!|>:laD[&T-f犲fY≒恟l1糟[驥Xa{桾C"pz滋則K爆Trxk#V[ a5UA亰5l:IwV njS]沁E`疣芒d鴈%Rb狃. 男W{~Y~鉈/_坊牀o:5ﾀyp\ eGyGyp)o彑<%[:DP医;滉鼇奇;cpWA扎.mY BW;yFkyﾌmTsV0蹴j樟T 90M藥o燃/}聲/濾椽 obA彜帯gfu'|I]SPSCk[2'Rr8_醸鰺_p\C忌狸##R喘PфOL(依Owm 3ty 翳%]< q`/o`R_oo '艀gj７l!歓|v邨/飾胚Bげ{c.界ﾛk?q&s仙c 4=:6W∃ b1c醋k瑟Sr=uC}x数_xEy(ATT4媚K";.$Y y歡劈:FB{t*Ho(-G]繼 悍5釜dsr eo捉6/C;>&c0[6^ yO\lQr7)伐Qu>=fN?O魚-Ｚ]]<|Xij?燎YQk\|G =Q鐸薨L廕HEg,使'\<# t/r?>鮴6{(c雰[奴8(瘻溏雪#遒(:"/~JT}V]!O鯢YLc~MT"O.OnL!S2繰"囚o-U猥詈岐)Ml FnL愆n 鏐$伎鑚_-#6wdlWPC愁;\*N57 mRE-bVWw-倍8I従__A躁!9-;8?妙sVU鷓h緒)I}2pd'/齧Wg#yy&婪%1<_Fx>MV簔_z017 uW#-hPx刺^"W雑実x;癶U験mZ谷-F矍r!g棯"@P嵐u[@a\@!QU| {LWrT梠>^} KTA7+I唱?<>丗暄c}VCり_3/:O栩+ゃ状' 藩汢＄gd$迂<??k 聾言ssIuR=ByK[敗()`醢o清GW_QW`Bk m襦撥確B+hN鐘i繦h80L$k尽珊$WJf'0"e+駐L琴N;$V#Wx E瑤x悍5D楾z&Y1悵pI篭K$尉Io燧zW 償.P:GｊD 尨ja瘠C@7|Z?錺_I w_I*_W旛m6暑Wbk]T krTM鰤=5縹A-kl.:罍梃[藉蝣鬟Lw(奢;bdOor) &e枳o1 O v<蠏V贊Ax6G IA:所xY'r-&藻P/_}iw省l~+参qos{柚5T鬣:e慨臑c468S=u6涌8肉 Ijw$度U[恍.,w狒%(P繆LkeZf T1j潘vso{_*c{d購gз5o`oL^mP`掌b靡S4q9苔蒿5b7翩圧m鷦6O|尾7UQKW{_ y吠6EKB gEpdF浸=鴉Dg}村瞶 4(J` 蔘hZc,Km?~%}y譌t0{杠d =+B I瓱!K/}u踟0V輜T_笵F$~y犠-[癧dh 腟lV ^1*昼2押-[3x3段]肭x簿EKQnz6u[IK↓搭l麁6 贏 U壯!嘱z1]L讒%a,監,$rNZxf '-抃o=.ZQYGy!gE&径BKJ常b7}@o &i驀}l|T4>?-o-e$1MK殆雖: 疹z [_zD CPT"sN澂莠1y#5Gso({a戊EK q疋Y>m7'澁醪癲@g)se2萋@`粢,2螳*JT 濡oTQb凧)Dk!Kｎ}a|gB饌"]z_js賃='葹崙P\ま 7RKベ67遐6K}=T易tｓV]nPaMVDoK潭GyeB@!O<遯|牒?8v貌h洛9`3.|B6VEL共*5OfuM5iu:~舖5)下39疑R0W\筝VECyTv?Ag :f鑠8I9*Tl胸笊EFIw髫(蝉v*奉$7{AP＄31V4_餃坪40}d=+ JV椡~_f膂Q坏|+奕;^拆Cr.nq!D6hi均彪Htwrm褻蹤>オ|WU嬾U5UeWUQS9'U3:sXEU&寸:額,UpS頃x懆 }0隲|n- 競撲Sm鵯:)ﾋziN譟3%榕=}蹟= 茜鴒Jc&E~vQ穂譲wU)osZ'\iys?SK*隸 _夲倣T"4f建[t璽建W|c.x*溯o囁xM萩> sA.:洟s s_NwPB憖& I闇儷刎I})讒K0s?H耙ZvHw4C8i{.姫$r "8@,蚓D妻E冊BkQE II 52抖+u_UM=ＴU"7uD2=囁za}旙jYw7rPPMedeBEjN '9Y円螢 F脛>_az.韶b B>}t巉+使楕p-f[~_z%RY|鑪XiKbh\勅[)[dPQy56|AOoy誕cJG67$ 麸.e>%W杞b時?_lO洗LlO}燵柮0|0mx葷g;I匕Q QlNdX嫌砠T/APt6Yb1D:噴z?XpG$ V# ≧[_.;q昿o7q4rwxfQmwh俣uジ=C厰S9 9呷 檪 %碾_<伊`k栓=gb `ヶ6広桷r={q苒圦5QЗ?&髣 閥\vQJXF簫m(<[rm|S{9[畍? 27t'Bs!統G8=5\滓 !nずN\"x燵 鴟!^-13r鷹C;+o禁>; ,Qyvw化サd卍6衾薔復S銜P┌3Va愬娵w恚iI蝶M\z 馬mr"6(y喋T窄U(>寓3a_m4隼Q~Q Bbd矧{築盻〆>|xB詫zc:B,! <舸qG猖o錠賠狽tＦ8H]d9td[En將W[HG. 25YH畚hx}9絡{ 8J /宵o\5%e吼VNp=_~iG殱7j磅|'z 篭"?!3W鋳yV/;<薮i:}^Pxxq溲!Z?r稟鯆掻祚T2ш衣*Fお婚9 般D6毯攷}殤gm{乢悠St{'Ia1K埣A(Jt=邱(d渓 P?'篁9. 2籬SioKF蒸嗚彡!J/)-bV≫ [G4u}\je槃V 5 xOb,i]ＶwbRGVgQ@b着]熏W]=,圈も束JMS /&E0_)=rO42{KniJ`痔-鑿z%L\|# 9s]<1Mw W- UzC9!UTF 蜂m p3鋒|繦2KVe zVu變wgm;Q`a堯\s$FFxp6#+_邃Q7"YaF ;5MYBiｨZ{l3稈r落$ts別ml'P}d竹dV}戴蘆I4"ｄ@d"yYb\,M 8O剖h[q0J"IU O鰄SR4k<}\程阨j拆3F e;{d$pan$MMD.aA}+yw聞b肺!}e(G&D{Z1 Z)杖 xS橢iEY3ML4聒{1波!]嬬~靤竇 )g%s"-d^j糞窟{H慕L%4.=~$0l由#箇傴j卓C;8\8&U'90!>三Y# *夢p施6r3D[VB7y56mE句}0Xp2(xs*寵hMdZ A嵌秣J皓grrL揆GW~CcwO綉E |#會jK|)Dэ[M*h=N攬 OPHd "ztH:g篌連;sxp<  Kr雇'畧}う 櫃l~s{希9塊*=lズ0W# v^`# ?銭!R&M1B死@>h*$Gw(g|蕗1i磋sb;4奨ow沱稿Ut1 }@"N8I.GCq>N,:q>lx6橇 RG;N薬d\g\H 袰8w躍YH}T5rTG `5驢doP%2癩l:]Td粒<傑sxP Ji{(.;遅听chPWIUrcpHII% 'c≒2隨PSuM_%$T坩u^^pPfakC i揉Kez.LQ: @z碾醒vb;Nl|qV!s#覦羣q洪Hh 0KYPH雉2,毫fua O'k??W"£ofdf退_x=OcL >抬Z郤+ NaG^薈 dd"噪cE?.};崟cs=m玉@踵qrKpz~羶9聾'~K 濾W& k`奨凰4Go-U燹0k%Yg|秒7~'獸<臍呷 I(Opr謠FO9臍J桍 Z\[ C"|!)% qC'IT6l_7f跚wo())wDeEY0{f桐Xsч懴憔b3I- x@""9V^0P n=bWG,c5B*,7{YQ0'喬.T:h,qRt壙]鱈7IM+#(~FD"A" w 鈕^.HL煕落(ly{.黜0'座&6Ed>_T{s }cW萢d璣 lUN0=;S.YL,5菅粢XWKE,* _]Fx$N hs)nBbG.y嘱屆6s{箭d禺XPs0媛Gc2iP)躄VQjYz鴆k^z^>uN^~nl 8嗾t佃Nf岡耆33M)k Y]3`痼A{yu傚wЭ荅iy屯V|)Y{掛 B-pX硯}宵DxU"迭HMH TWotG蜊p)dA FUw6%fq5J ;\g7D稽o臨sa;e`羨Kc719W=j}n7{:HtY@b>p@o瓧"zkQ5@Ip犖-le＼喉= q мML 痔S恫Pz 徠]黴MvL5x法 Ne ]Pt愿PgQ,95厂O6Q鰤1ld>k髯p(g俤y:[aY L螳h陛D#}b3W/.m}@蕷*y`"' (XU溌咳|(网n"]|攝C3C("?'{胚w?2d[Dx饅P`莟@Z,煤鏐c$x;v這phK6>n-*9xP5淙[]dI{g痴Nm V G遨&K訃@W=鉉[寵燔&VMXu臑k塹.m}M倩D甅'JI爪e8稔>g@y"%$)) H爨 1@愀:醵IT/w壕Z3湮[{W;Y鍠=gP.<3苴c羶mE@!G飼ZV陛in4W~^oG1睇pV75_+j児sTU{uC藁a[霹oGpUl憫Y0g劼^]溺RRs!7jAs砧w=Gx-1Kv{罧,mzz^{覺廬b 僥笑Pd;!5X{8ruC碎h+XAU0譚{綫帚'f拌宰ZO7l2U j8:BUu1'DND5S:/莖&P苔穩DwsL;懷=+R~莅;_Pu> D倅本/:t.C20%糎OU欹佳瑰^R)(h#9}9uaHnzP,3\桜6賃i)Q NLo~K4JP728 Э`宮S#y@2v98年isM.e$游X 勍pdk.C6瓱瓱′$玖NJ-反#xc*ly{BB畏~Zl蘭出8oB搾"＝oc- Lm*B8>O蜜Z7Iq$関a$[uW竰QDizI鵬=jN艱遊漓(銜F穏A>md tH励lfP朽悃W+;8f3e><}t除 4 q倖?3jY恟C$SU拘&[r%+賀]纔(+y ymMP1r o\;M柄甍$L3%H茫)F#(F#.Kc`鍜v"xF龜p" ^佇~dsC#"K@. i+z<襦B9Q誉屑nsGj(は冦IeIv R艶j:VH笈*aM譎)焔.vtBC4_xt,FH-豎@(>,< O!#t&Wmキ X]臠Oef.LXE:/>yeXEKlo 淀,z帽<6燒maD)憾闊Yt9`M汗UOAA6zt勃s  sJl1 jJ"6*YD&#~d,P穽椥R h潭~'?)@zXzti8K8M聢A=固部OkA=Y#8LWNX(Pl6Ry;筐S隧Q甞xNR]Jh0f9睫拌跪x|+2黏]Y_'~f等朮MP Rs1t4oVUn{w?IL(s,謳hm)Θ2fy僥)Y◎{J|ywチr8賁C詢 os幄fDbq綸醂W8, dE31I."GJdBP遇焚(C際/D$vdv"舂Ofw4ZlVOo~`Asy3p關p鑰|9椹n鈞f!稷z係s0Q 1B6AL肚ud公L#%矯U楯?{Oz}8e5箭^Mv^4懺M!囗t`i2B[a$l-Hでw% m!CA0#n~4"Z騒0殘除隙ixUzv倡嵐 j$HZ1F&.PX0!N/#%蛩*仏`%;i~`NeBi}f)=Ur?x刃qEgse<[*c8nck2悚at"傭j<1@U无'q\%W;懾: F(<5梗- 風3G ! ~N贄0G^蜃:k`] 亮rv#'8 E曵2Sp埋Da隲蛤wZ=;dU戛/.:Z隕Yz#[罟9GBILa=v2' ;芫O&,( x捷9A^sZ0狹汀z{曹 4融>j,R3p7\叫役zK蝴pv_`査r}iB=U瓮 lo *h ^.Rs*蘿?f#bN &G狂C!V.6-m轍%*%S'KDA.8?ycL z vI/氷倬%^MG53$ClK EZ;EGpCG澎=r%sm 2?墨 YTCar#砒方<WNAげf$u{N3|6 I>/饒a{x.u)@Z'F;{N蝉撹<:t鵺8oDYx弭6Eb4KG它匙6B pDcoUl?0_{H}+Ft}uE輾# p} 團kσzg>)Qwpwyq%@8厘dD6癸線k#@gvbi浸d~%?gr[p[ 芳5($dhv,&qIf @@_` NEx^7:L隨o9錚H'i誼l3,R037'e9憬Z煕GU5%{j_p0hw1N#酪翠Q1齶RNc>:SUlOf^TGr3c,慙繝Rl'`3)r戮苴Z4w~q#/;眸2fM.暖Z燈A飜IX]y{Lw:云CiWzz_ W_"b{H'13趨}〉)&釁PS.A^ge壼ZAm釵i[-H&+fYぼ靆an36瑾£4r./E黝ys渮-xS~PDK啻3S憫.七YwL1?,OsB.A諏zl裏 I9g6MxツI-Y七941oh<"羮lu~据褄n:PP4*0 Sjt3^EU}_zXy="轎/風f9;$+T2,Ihrx聚6J^Ud∪G4恍潤M8v v\覬pIぇ湲F+{a初f_4|N飼OeB蛤Tl乱捏[飜.磚9xbFY $8 !撻´莇#aU:+=A草缸b@CガmI"<撞?x qJ #略噤98rzg h~hF#PI }m}.姫慷#y< kW1帛Vm(%$閼"w dt麗M*Pu偉 fC峯luQu{J霎.)鑛4孜沽 ^HHK缸N>MVb_CGexMq?w!u/|Zsgqd琿BRbmF0} aP{cV2#)詆;^Rzs乍t}&Q)C5)6~I恷b蹟K;qd tB<,N淨@8tFC3 算}.渺沚j-啗p旨歙71"+6!宴.)R[8誑紕Ν斎v+>zNL="`悛mq>@献u熊Tz阮＃l釈靉穰a桜4qtJ\K~Z鑒e沮o.~阨大*5ND幻種$ypts+-懼d >SKS  %銗S沁NuJ>L2]sa鰮釆嫗co7υdC*.馨h}40 /G(滔g(獣8湎'aH|)8肚7~HHlg移a 区hC路轡ニd取(繖m楔rK$曉zG`3wwhB "> U&lB|4歳9pD凛さzZMzH)i牀､~慙e垂hu@勺I 8LYE]}X )8.柊1cH丱$n陦&ojc梱8#!bt=菴攅m牙l迺堰5]#9eI韲{A澎D(:%O[DC{_s洋gu塘陝`<倬V3苳(%ЦXaZ滂E ZgｆQ"V宸E <Uu 韓cnG*s8;0mWW-<胡E}QM"b/$}]欣oae;. !晶+b]6T梓EFx樋 dXj`KUT=,衝4.~!UK枦掩vMz{讃dI!阿>sH/惧y&3 `.t玲d担M 別6咸_ ~"|[t$KyU6% v潟R鶫s\鈔V _1p噤"\惨歯g+ ]-Ez糊l;p酒u9ik熨LGK崖VAv:悗@O[UqＢE[朔軅I囿qSXz<{ ?CSh1< tqpb爾USYU2J-/@孚| dP@D"績=幣曜 |w"tM0穏0[d#] /;u}>茲J5W;Sri; qA\rh ]%>z=煽Gdv%I`Bpecy]轤坩TdT9T. d>f^.N┐W=81$&Gj卅4訥i-98OJ[M赭q<(5DdRrq { 揉wiw詛xO ?杏愃+a轤1drh+/ ｡j},L01繚ｴ6#zq3QdT&B,離kxT悠-@/^hB挈v緑=*Tr5&dv%W}R筬?MX[K1hFfc|[3QOt6W腔baEFB=A畠@"Pym7%BH} HeQ6板RUmU胃r朔N;;.'+[n,=]0恷虹=K實足nmzU矮擲A 浚苟q5w's医Zs gS@6"L[1]謫pM=引h算@0%;] *C7沛k`V牢廨uA]&Pqaq8>@ﾈ板Of*K3r{L椥g36 C喀]~z?R; ~F軅YI伯wKPd竿/}鱆w|bYN"J}奴/iV)?-3 MowF}常mov潓W稿90O斬iV罧@齡vsty樣%B:彝YmDzdq藷 蓙ui綯6++

Mj {u蒻扎cR韵K[8竜"?@T 疵t at@O6[u#A*,r?;GuRAb旗靦0BVabIi螯tj`9譎-y朗xgk+ aZu%\Mrn((弸$iK梶H.}T2T|QOeYcdB9Zd婚P 0!+z砕98K嚠p;垰`H波 gw~:`B+&z$!)淤s?^ 00!∝_甦d惘餝[i萩冖^@父泝&p?k事LweuBmg8８Kγ!筍G{褐 d9<0筺x0:いM―nU\>O %2.(撹.榲(U`9Xxo';鶉 Ll/pqf3朖┬uS"jb仟Pu0/;z{lZ>笛8EOho廊配*"V燦)6 +昃^FV,bB~絹/DV=羂勳D'*' >-匳.Xc!{eeN\u5&ushtxN0餤N 3W餤-2餤FU!(O蓼)!t?I'M=霏,_{豕@x (2*3踵v桀笑s#0g i@'D&LG8萩["Q聽踰X呵Wb _8櫓蝿65\^u5_~:踝^'eT：]2宰Ch{ 攅斫3h~s {O^治境n /C8蘰<混v2b倦PM RfP "=+=Y濺ﾄ_tNXt梗?序Oap珪XS7U惧劉 +盃KL b ;*+}iW濠楢uXZxV/D)|JcaBk9VOMgb軒z47SI\'卵\wxD除謎k3 12荼L $EB*kJyS桐dl`  刲s粢瘡遊(l G)△.\m瀛,e T縫d 剥^叡brb XqJb hKRFt3VSOeo%{p#_Me積Y ,.糎4,mY-楹粍 瀏5d1X:Y9* I1G媽7禪盍┷-.'7 6|8C< ,f諦桴~|g}Ooe宅 ]w-Yk 埴5q]=pt┌V=CM&Gnd'ｷB 昌%O;磅`}uSlKr)a;@etuOtmIKGs/sY+"]O 嗜t70WQtb\д 9r.tiV~Dx< NFN!k ~:tOhHPぃj跂;2^h2OOzl} 7_Z5gz_@<^a!6i瞥Nd殲賍.N4rH6Y烑募#q f7x_r^@u^広_dIhS j-\7*SD^F牝u"0\iv鰄韓覗f;E2m"u$*pI:殿e^c[6Y鬮!/i揶wK @CGびBX黹:1ｇ&qg^Kbac _8:edFXR;lFIKx@\ 歌 1hA'喞j[%3.F身Z43KuITT%w9@p:a*ST?Ι *Lw10餝#Y矚3挑*sUG頭g.Em=y.眄6o-9g oEc/"P!(絈p7~卵[sv察M>^8|r\ε2$筥純!a|INan_!sB2xbD^箒 孔 T~廉籤\鳰餃]憇X|;柿HnQJ'"(砺C:vs/yz&>V0.徐髟似LP燼>2(ﾙ3& 9<'~ /#>O^流i3 }" 4s>{愾"nS{Mh經]xR:飽'!p^__^輩閼pf:YE]ei3>HRP>}^$sN8胙F@9螂I腫忍鈩gゑ6$ &R軋gP5OVs&IWE eM溽Qw(*yP)jj瓸8_#z(/{@y(4#沺2XvX> #yky{@_]M2派署k艨z多QZBTが5P眸o%ST+2Z&噤]\*77"h}臧z艀ce斂[~j~.W!&^ 杞[c谺<.竊|n<*7Jeki[鬼RIc7TA &\d"e;$*軍岷檍rg 売J]#哇%z獺z}y建9族K:餮SO!5e&W 0\(j@b碼awXWvauL賻j. Uw(聒)3iN　涙\Y[7t10粳XAl8g慱@b16c沌A罕D4殍&l4籠r&}@阿嗅RildsqY>P '頷>kd<$犂0^E+7(碆fE瘰GGi2 (鐚i嵋#1,( Flr摸j|呆}Y7R?_ 袁}"R}fSo;$ C_O錠~YE蚯i閙|n2/B]"8i\VbS7^S櫃=j8籔-PmB$&_DrC3sPe雫uNFgi33)g÷Y4\苑 Y#Y~c/p囎與椰cZ |&\ .`\,w懍|K竝測`詑g_價,vu}Uヱ4S"QY{>嗚UZY$晨o!N>[7o熟鰍s/&瀟7/脯0:児#RKf4巽v#矇-9#禮3_?"9"OnKk戉|'O議&o淆nXEr矢}Yg"B;A xow占付[戊B15lT6:g屶CH蕀T  jdVs;茉rHdT?j(I讖(g@ぃ;tY(= >`.鍾7!0 蛭1~洪NwдjyI.,-聟1稗p間 jp fCf雉$nf7R-PIDz)uoO栗淇m0aE欠Hce+]\h W_?鞅%_冫msi域-扞FJUHy8x 女懽._,A咎暢#hWsc詠9\瘴L:2儚,Lp}5|}pN{.`n祖坐dfo:>$+機.NYя`冤 2~'fNkC硬"f.du"MVx8wN)閖g'L茖4v\謳4Mg:IFU沸裲逑芦 X7:W' I4Z~oG_2/B$%3GN!#ks"q:色籟pH61籖b4q（舁徇^4IA薜E{_梁}庠rG|';G預槫!葆DsλxbJz靈pCWs4 bQ^ 膀¢G%怫c%亮!%欠rIdC官LTv;橋暫@\}Q抵,~^]TuIO在通q*P[囘映復H倒 Y6`|\bJ^( +p=  :QA!3W麑$\Bl|;tg 9X !杷W8盍bvo9;亠蕩m ^c'd'8%{*%i黔|索sgr%驀xcsVEΗI ]L~}=hXY酵N-|mhG斯#>]C酒捌尸 I^C^繧tU慍 遠OB9x楝g|!ΖV$@`CPEw鮠+hO|蝦靜PRn竦,L+Nソt6]C-c&tA4"Y @=焚食7M 西S!9t4[靄lZCq誣ij慕n 鞫僕OHLw夂 EGE.{IbL7s超産F鱠艱婀r.A{面l籟A梛墹]'{&d笨=.}W $;~%苣!PHyS瑶.j:g[QW9'搴iyED_]痛BJS\羸'O強蹐^+] "M靆挨-lZ!間QvYt+O繋=`?"g;: %%蟻 2 x!*pxLc,$况鞣"eb潰H9溘`苴8恐O製$s肄k^mor.譴SbyS9jXm卷I=χmQ鴕煖6d濮朝x&(^?{#x困UX hfW'jQa礫7nbj &9(凍nsj%bK$7?lCV%%C3)>`f/[聢般fDVF盗-K粉u5L~,!-梭vB k'T[fVl9>巫 q-qrk枅 fB2 這\際^杷偏yQfz< 雖f嫣3;ir仰`&YF9W>b穰^7-;E~駛%7Lw$7.督fQR溲濆u^k*^L7蚣V*,染ﾀ鶻y6 &慓abCP1Nlu鑰N1q鉾9演me公 蛇 u(蝪!,6召地q4;>廳 F臍"(>I乱H^起~MGv&枌zxjY\ a> A#Wn9|!鼠./ 櫑o(q陏a>Q,a ;@T仟I曼彑iZ-..fg7IToZqq%=10`通\,X@o9M@_E5yaw皀弖}Mh /I8厠#'V'4jGLh#托m*裸愚BlJ%爨荀?>;{i*玄r28?;aL|NVt蹟]+&3zJ=%+9"3o`Cc 榮3寛+D箋[JS"0Gk堕KG厖鎬.X韻eAtX剳妍8QxJ^iN_3/2cBGy4M-YL@ x涜9>迢W#SfaP<ゎ眛+i墾O*毒鵲柊Dk遲 5層訟7 BJ罹j4跏n0X偶>@QJ7X$F_j^却7l1F 礫A4t b?PkI#us eV,k|7.Xbﾘ検PCra玉"_與v-t"-t"媼痼-tL7 uG巉*nVNx末;m隗vJ'兀絳arx醇=t-/hzD){9$@i[KQ[w篩Q杞:>j .g\Jp|バr8Ry\C:y0!恷馮pe蓐[55#孛徽E':S+<5.=8K兀奴1 lq np_鎮TZ壟I "呈鍾p{樅`~np_/鴣 nELg76DbJvDfj儺bV+n;r邸u^浙C?zwy=xm敍^ *}FZ7rE杪:^笵ｧKjcW簔B躱 l岐 7[p~]T )>膽nWW Mb▽kC|a&絃D[kwz,譫A罨Nu翆 pxZn睛 髓ENr:萢lg椌 娉!9廝(HO=豈性 佇ndMK  ,pW`~zk*LVH悋u hrA屹 R't4]?CI+祺R売9/nJVjJyzR怺!EB-)b>#$"Ju\7(f2=A楔]I}+#{la9-H#持1xaE謀_?GtD阻}Ok屶_y鷭# C} z.X片j櫂K莪許g%DWKkHw\椎bBuhN妃扇y陝m]ZW馳jv'動1tH9Q%0:楜n靆Vnm"1[T杪莇[ 雁`&-O7k{6tW,vwX>Wnqv韃b{迅BGig@1閥h"C穃然H燈R\G0u^I7*QyJ b;_a鈴崚_3W7Jen∈I"&)Uk^#= 鄒X&画bXZCTOVm眤g 杼"f郁Vh礫K~ [蹕詰QDB7.zU5皇kN膰∂u"NR豊u:iC['-u~\n姑NTKG訥Et?!D:f7(mt@Q 惧}$>L\$|bL7\$}xM9姶nIOW蛍/總Xf;y%}7Rgp9蚰au/ YY-M+6 W篁]]iR a+.kbV許eY[C:鞳Gp淪1.u{砌ネ晃筐D橸挙\逖 SuCD% qw個 i当$[.%P6!5KF翻.;XjF>丸(GJ8RBB:Y ｝:-!"$R-H SDcQA巴;KnFZ!鯉4#,Bl^b MCZ<醉Sa愃$j b讐買v菅r_淹z抽KI =磐mfOopW_JAVKxI罧 %#YZsX})3 uZY}*嬾ｫcz"煮9yUd{%.袗[檠-u-:限+劒3M7$1嬋f軫吸~AIWIK#t心qE%n晋潘:K并 公"鷏j-鬮愽~蛆[yｩi假_B/+[ /iE{擽貫馮~夫iO 黷=拍!tOT-秩G原渙RKL5)i斷Z甬K 4"V[mF~V@佰KO%祢陰k%U3m{t^狩|箭雍G[ 滬些匐'VE栲M>DmΜhlJi%NR=怐m椁p琅賀;嶄WKz礎G%jM*K+zx[}~iU+*\e*_u@FO妾b遯'uK顛/ｒ\2r4t* J甍*~Vp\,%RJ斑RZ)auYJV K)% s舉ヌ船vqiKjUV"U坏+&:BI=x{,;'W0\雙E}苳滾pI -60ZGO倅鍛%D 迅~IF#覡K褂iVietn(st憬/QY)YR-+ZA)-V:xZ j´44漏b抻VD,擴lM幹c]"TR:z[i%蓮LVV$Z葉Z%gJOBkX`&4V== F8"i塘5 ZuふKiE[O夲[^Qg桍輦 r4&*sEJn:'/號ZDロx&E5{胄VOrhi:JCpろ)V汨a/Q6rbzk_q宦'iA5%俊]\7z>竒xP/xuｫnE{纎騨M!^0=}?醸虱?}':?2Zd.鯤n)VKY蜍卮|9xkAJ}B蜚xAW324便 3+VpSCYO菅NAy"t, "H\TaDX斟?\ )/C`_dKnr+@Hgy謎r}aZDd-kHE}У.Dpy,(郁0kV四Fp+喬OBs&L.}b杏催8N+の潴u' j tUkuj?1接{謌瀁iエNo┐'?{靡没~x驫搭wC)rH孥p丼Ov  鄭bvB?R'T*宮 "=＊ErJcv:2brQ~坤)恕報;E6c.3"w'紅XjK鯏~^8且?xVg聯,z8=geqq m N樌N殳?v cop1;vRV8xW@Za]~j澗{ qCX疂!t?CXX(>#-│J#~* m?延勠s_堺ERhrUp好[> 仟裕:盒1"q!B)}-EO顧\dLkH壅 jE0p {Bh衄Z膰dz8<俳vz({3儺~ A?.0&"\TTJ30\`*q言斟8Pu0Vj4KD]o}f<.G\俺hh! *6Xh鰍[C,P背毘旄K6 2P6qft錫U6aif;"3HY e-2%et忍m}盪o3_ 攪 N@"j舒Zk6粡茨,6E&斉[ZLgr'@R丐lXJ峅rQcjJ-mZ夐L/攜j3"oZ楷VC0舷KUgN#M"UJ2E) bZZ慨_E蕗;Y暇C oOaryjS=#E{Fk蓑!邊6T)b6N8dv2挽a雁F惹#恋囀6+琅h竜ZU]W[C+8UKG@ O}nvl趺E槨"伉G苗2Z銜OOFﾋ& _Ps?狼壺#M+`%xA#h%@c B3$[ uj|l醸騙Q冑YamRn.N"L\r q|4%Oh116p"q~e:痺q9\4p2oz0f1已祁肪癈n尋He[W6`%WZ =m?Vy壌\+4y4bbo(况哉;bgcji'E獨C5o懿lX&DE磑5:A櫚flmYZW 瀚Pi -sE,9ny8⌒?脱fUb#φc簔xp@\,AE,椌j?< y"|Hu凱晦(&Bo7,涕v嶷u F}*H\崎Z許j=箚"r;柄>枠3薺A天L?#鋼q- mpN0ヱTsC;1NU蚰1K婦"/P+ k痩n@bz(跪蜻鰕T7g窃)円}VTsG Hi楓福:=r_GpUc岐轌ww斐aG@斯 kl la醜9bS+HXB忿'iPIヌ毆?pt爨%}藹dH=史}vL ＝S(>L僚M/w怎a6~?c=e.'GL4?Tn,xJ7礽7u楽ty[房 指r/2稘{id{Bq蜒EF)9qs!!$史O竭!矣竡1V 霧惹m+Tr9fBCz]R炭8+Pw鮎熔q8u齬+)"HMkS]T郵伝u+飯xKP潦'hIV 溂w4hy続RJ卷M,C[馴rw pcoYC苟%籬ゼyi#D棊+VsV 9F*G&>[劑xM+f%Mt奸P托)>x魄[196W2碾碣fm//s迴崋X|O<3hlYJw>4]jS \owET;Ag@)w]w7;c?}3} 郡XaC;5W竣鍖臺a0櫂jp籏M8P&E7GAL-$Z@sdNhaNfpg/H啗aI ;4&矮B濤B e|b?3x癒[陵kI1Y &0-I\jN=c頴"削ｲQXqr>d糖3&.皴 OJ>l?TQJ%rhテsL▲[栗4a┏62-KG 5Uc'XD;.l\j^b}!4d(*=C攬愡 a閔9Prj6#R抵`U7ol\鱶H8鐔;7A{+"餝l6l 92" EQTAIC殼}阮1洞%kGi 宏4PBJRh 4hAIu8oｭ[懲HXUz⊆┐@jcdFz`EIｃ$&VJ+"M|┰Kn$."5幹qY仆Hh樒~[7{n qJm(6.6 ビm}yP#樊兩 h堤wQczP協 2A Od者[ ^Tnh6[y.振帯klZa@jp]"~""qm^ 戉機1滑 砥 (}俐:Q 浴(戊 惨9YkU!k65$%wレ M*-容洵X5[x>!6t(競60雄lg{" SC餌境v/ Hx+t暉]lwAO;)[w槓Vz'%H鏝4wY3wZVz7 wA hlKKxE血n潅\@\%+9yt党}\汁p%;D}鯔-`豆.8綣Q纃^<{'hO3'伉- 叶ふ8誡K ]/~W釿S仰x?髢/  戮wO^丈n斐H賢%竈) 0Yv JI^her鰈S3V&kP梅/HYM叛聆| 翔鞠,市互o~;(VI苒"}6$Mh$kざ'bzpG麑支xB[lTE,蓴ﾔq=埠nIU 嬉真讎:券Nol欲$?BдDnxmP活PQ蘗JGobt教< 勠*" A烏^*\ !/皴>j;E ~J=籟慰U d對C|W0岨匸K^ X6yfuk`8a|1';E&亥爨/"+lXig t ;A璢*dlサfjmE@+Akh夫衙C=X+c,蒄$6T99,{r邸r嫡TU 寡tk('兢H_?^e省G @鵠 .檄!EZ巒|sw's胎)b Vnq8苒b畍|}蛛泣o&dlNA桀 顛j*胱wz@怺kwiJplJ Nhi+淺__i選 }q I,LLiO掌遉unkCn%YZX6KUp岫X;R側 ]兇謖Uy 患\滔舛jb g 3蒭"fr\X[DP,p}`E1j+br I5 ZK T=Pb=YBd($@h E =8dm千済'龠+嶌kH B扎'[N^JJ$!3寓:Z姜 鞋HN皿P .均{L真.\兇PK|#Yh=[邦/~Eom+>ki勸n薊A`銅VT$ 槨X-i.!uWdmぁ X堀9rF藐G\Jw澳rTQTW羲Q2f&<##篌 7,孰b`qO u 梶 疾nB)箜LR NJ(#Q'`%Z`Y壯i-UKJ}/_U=]/)Hhp裔eM% E {E gZHgE#K(3─tμ < l*感|@gi豕!,m蝮#NW6T舞厖$∀5$QFO|j4児擅LwB贔PI*喧箸6e/;Dl楔X恭cGﾀ3庠%s&&BdXJEw]βa2dt)2legh^wd[怜-q晦>jCA:鏨8℃][d* F'l貭 O`C辮憖Pn凉P{sz丐H y>ktA*窄`牴rs$cV?%NG%}蛍}d顧y炭.壷&}L\j疝Z照5$;備< d淌{2qL1池性uEU:Gq 當j桎 P.PQ揺5$ g覇 /装E e_KCT6)ガM(:,7n倅d仇4_h9)l朖->Y杭く肖9&-6N艸8m-蚕9W鴛5:G p供uQDT ($qRPS列5XTk':iTZ*1^IL 鯵\G u4@m4AHH]s fEr{#拏9cdn<椢xo欷YP宝"H% ^m<|YV mm"UQ/%UiDD`G-mb櫻Do;9NL# BGJ "磽K&A)LA0b赱XC迪|\RdNtbcx"8v"5?,"_づ;1 N8hPt:P\w t9U'v6c]l粥!^Oz|mrC^mv:m修櫺 i=E.的"廢溶pg YCaR E}mEEn妾晩Z|_A+E|a!I6}慌8cY孅GZ.!n\蝠排{_Ow9[傑Vt!R^Z剳[e3"蕘k6碗;`2`t@h瓰=促2t}FIxKAWzSR pm }<徹|CJ0:{岨BK`ZGFi%D0?%V@gx苛Zm斧nD +sb{ 3f;1)@刀6RP6 525夛oZ1!/inhxx棟ofdn9=|嬶b"m$ [C$<_X5~;奕l竚圍uポGBMY詩 閹tC%cP范\k9 d叶H?j@K`SJ匪$咬wm:Hy撞 <%= LA$V5hC` YjCw xQk*oE/dX!ｖnd CN嗄n8SQ礒MJ蜉杆吊AW-5$2P斯 Wu`fg!\B$）vahf|gJ*癖Q_bR敷>1n;A>f0峯彙]%8t}a%H紛q荐58uP]ZCMF+++曖4GRz46,VUm苞B用"}E>vSdk俶:T抔JK崋 幤挫囗k;?'{坊]{[ObFal&Z肆BK 掖(/с尨7'9正Lr_mg }YyF :D+aF`V"9V,9奐-*mfUz │pFaj^q+‰u3io"8古!M薔H1Wb0^[ 茘! mｭ+諍5dsf_椋|iC XAW6Gl%r9淳d- u幵攬g[/zc,鴣鶩黍T"1ゥ"uOjbll,7nLz昃*^,o雀wzx逕?罰Y輝5e,\GG> +d%Br]q5:[Va57|UKGd] JBWjg%>HqH 8g輟XI拵BI%緕qУ2 l跫fR%e 蘚 .P摘wC掏母X m)|Pg( m\巾PC|GiE4s{/崑5$CS=x|ct'賓 {Viv0|:?om-!yf'Ow% +9Ri`+]k劃◎URvRZDTZ$閠{[ R釣劒皙}6竪*x"n貶ZCS[_PZ_ 0名*x#1Ab }PKz扎 滉閥1W邦,MRk-rjv/u/丘"&Av懈tg+A[W旛Yn^ 排8%HtS _|<歔g ^Z9謝0悼E秒剳兎WE矣楹,8V(佞I8V.Y孥Js;%ZX+T@"JZ Zob孛VDzx&EG,n%P|(dm\`he-MC1陀盖E天狸a_oU[6[ tm 楷 6=L記*算1/PIL-K*hl$E"雰# KtM?Vx]{r^東>瑜c6m}舸+nnCo4D^-Qc1G['Z6胄9}K"蝕R<僮4,b冲礦A @WtY~V0P?q+" m]X E5_kkWD4-vI;mqSU"+a@蚩5/<(4U梟R%此硴Nt[B?=$隊〉♀°*gLhQoLQ".Pu Y戳A]h<`漱<zhQ讎犬rV2!v^ 峻尾7+K~>o買v(殳5 ^栄3(@~.4leYo. {Ag"瘤p>@|-'R樗椈mU笘 /nX"媚=蝣  jBd弌ffAM3/Pび1z?~H[d%r┛FWY[H 縣A6 源tCS悗fp;狩[]Dj>x;誠氷5e1Ofh^`%uBJ 8jG;oDza8痒1oPZm召从m@T,A#"昧!巻鄣坐H^ m[X-R%vc絨SAk2*h1hZl}El(-b}_k};^6JXM 彭接3 去/P+鈕8]鹽AV\cY襯 viE价Cff[3A豫鄰Ce$v,hmCM晝匍c|A,Z#栲Q4Z嗹H甜R)kHJGF5酸l\}o  村R箱W.Ck%rA 汝d{FO 醂50o!n7c{16,C_2Y荳a"W木7X=+7%MJ卍n|-"_j}Y"k]$u1 aXx湶鹵篁J%avsCD}$.~Z?bW't8[i N87$F u勍3n螫ll&蝠;H6kv ocFl PlJb[wz鯡僚=in?輹?яju亥=恷]矣|B=@i- 兎股腔O'xR8l/@\S]I?u&Ib|L8">L *iズl鞋=靄.F`cs'v？uj;t8R 靜C!*aW蕀VK8$V#>2NOq>c(t0#L|! 岑at?k婪]e AcgEA1* Cik R僧xR3Jz`L u紛ciQ,.R @LK)Ε !' 0 i&畝V寧1燥]}8`\W7Mn堅omwO7ﾋ鍼.g鬟@y|*p,>_Za霍@o斟孕鞭%g J 敖MI uu:m \Zu2V翡K=種;s>M◎@} BZgkb(J0k 覺J]義NSo5u#)感枚IG筈`kH)l5"x!e#Dv排:EJ7@8iR@:i声槧R psIv3)Wv反栢≠k|T/8V|gkhS*-G+<. Dk}.0fNH=Q那敦d友{脯S$*s`f!G0†k8褒縺g3f`7o宵xI<C_/^+uu ch r$6蚣*&pUN捐1_ 0R (瘁<亶aG@w{LK*j)ﾋ同^\ |};)饉}9;Vl1呻AV#兆蘢@碧%項軈夫B森u曁 鈿IIFP毫髢:4^7q1=  O9操;w^ yz}[鉗帙n?鋤疉Ga"?OEIR 汐FSL冪汗h]蜥正iテG@槹3Al }[扛rja畭K?}閖/繙鋩 mn唸v頚+票1ﾒ羝=窓/?灯%&A^q+}LWz馮^IT,筐&=蟯p|/=& きO鵝 墾i纏Fy 澗y%uK$hHIGt>&疫ZTx鱆7?|^Dr茲H4Q器p妻蹟?Tjk 截$j5dx薤C~sK!LD叩却w$Cb- _婪Μ9Bw@")v洌EY$YCR6+滝Hp+bqQ臑%!Jv.a+h 瓦寥ZX"\B*^D!yJG/XzJt3~ >M@eVwF.Jay絣椈!潴F籖"ltｚ蒡=-"L/3:9G:2 KFq槍rsQE%iEp}I"aHy2I@)f君 `c戚"M槁劼DHfu下瞥C(gtAJ.p \礦2 %F R頻etA]"GetA乗B>? ]盤64tA朴)rtA]/:`t排*=KlJ竿]育*]茨(]Wm-2|q┳U_S 3M%筌p0@ /-!曁arA^&+"5H魏菖ＣTk9sNa2倹1r0iA*VR來H=^)G *颪[9R%h?F 'R.鬚<)ZH-G d#R- l]HCG 仮byREHCG 萵)佚H':D#RH9R5R1R,#RHAD 拐#R EF 晄X$T.hH w0怏4S;!sR %аE5ZO)bG脊!H=kihY{\::<を食Sqy雕v,KHHd$BJVDH+%Zb$[y!D慝DHCG"-r$B:!_41|YD粳$9*ZDh#斟H|H[%8DPEO"育 (竿H)pa D筰 $mmHD"*DXC%M9個3t}9BKI;T俺DVK&Rg ｛毅bV+!2, 7',斟kQprm~%弾%+撤琿,C% D@qﾙ劉iH樊)MOjVDudsP"Hv8Mdk+DJきi+D)%r_JTjCDpH(\'3747wN(( 鎌U`リ0[]CD@v仮ih(Pg茹LMVB3IV樛gFHL禅SVMtv:I旌庖脾vjjn抵電5p\Bj/h籵]\\噎y1DOsZ,2.a'藏iu lRGqbckHeKf OYD(o9_{W0=4;Dn絣(Ip3*BZCY eH?}QXf9 I]lD~!fkEgFcH$:*QltNv4BF帋y2@1cxd+Pe稼刮bbSG qm +織,<~f茉盞v|T2樫Dm6弼鉐&c!4 a!J豼!dRpH Kd2u!FahC2xUiERC2x=T'_耆花卿Z: $ ,Gdnu[`eC*杣W)Ewbq )u粨Zl癌m}:~X6sq?擣QqH"d3`{!@疸%9uhC\;RFWo D0/E霎0''Rю髷6鹹=(Rb7E誣>,I浮P +iOJ'T$;{Er`OajY_'E9.U'g M''_熔tr0咫NZY6０qo=>吁uhG/E塚+%:m"`┬_czM癶z)A童.> e瑛%<膨H[G[ \M"{vJh}6O档規vEn1Y)貌%L!H-兀5暑朸<4{榊up )2墾 Q攜*扞 uqき$;0gL奸菰瓩番HW*劒Q|9\5RJXXF({{EL~Hvh^k-V實8(7ヤu,掫L 悗B,sa,:箸E@饒P竪@IxlZ援萎vDE}O爨X_旄3A'>w雎p鯏n圧U^!:当x収1`綮罹7-:!U灑Ty,$V″MY淬Oa)**-1"s)]艢t(.軸e#.v/[\W.|+M;&%x7 p盜ea+≪F"Cq0(UN P餘q…4劵煎)P_-JP21 VP 籔Ia:W{0虐,鰲E$燈鴟8"靖 l3菟擽^l- nG0~梵e j2QX. bB[<鄙#o浴x[>2s5$ !鎬wy止m幕]r z5@8$_>O=V1 ]St. O9b8@k苻Ro{繹?,g DA#{達b7a閤Da(1憾H/ .)06G#1%N$k剋0I屏-`I`0GK^k |Z湎^M2$!^V%Cf怏fEq瓔o0熾靄W窿恟Dqx;狒f孚! GiNe顴9l7創C64/Yz跡"u g破壊z鄒-rM載Qま_"3扨^C ^戞! ?6T~s 竄-pY:-$FE∨ .ZSGp]nψ剰%etBG6Jo嚴Y.ヨ* y/b-mlH-j i!]AT^ZV6禾究拳鼇(\そ}借惣-vK:<匿罫#b在0着nv<重pX/|%4鎭F^c!'z$神Yr!Xg痛@後t90HQI@^wB>蛤p]]IK)OK荼$$"?#K\G2nRiM鷏Aa>K\NEI 冑栗ndN[!DgEkta) q IX薉泅d3\衍這矣-撕SG蝨枢,EN/+ ='gxoSn\@z貢轤w/?}#嵌vww駁W=~S+萋^-d通*竓> L %{3ﾔ?3区t@麓Kbq,tP+h髏糊5 ,?柵x| 犁 塞7m %基t>ovWo抉:#Wows暖Pc\'[lcCi2t0dｘ44+@$8QvB Q*.篩2V緯jvn整LU3腦Cm踊,'Z剃a E杜`茲оB';Im`6昿\Bu4.nU-%+KmKz)@PN8 椚v6/XkH|RD uM ? l=yXUq pnX2b1棺p禅83S哩〜 -LZ&g貞辺d盟8hU如uJ+Y@\!9 會 #uj YS,P;oB]愴<^( U茫rPQ\; :}1h`_$wdS-"LYU勸sK壅暑孰#j"anXrob[ VP$w<f1z底u)O年貌.I/D┠7k$frl%w憲iyT^l.灑dq餒-_湘w7L? :N+s ;uF?^~XO;谺髑9L徨rD*n,冷劍o_需髮F2 &DK/-ch~ AJH《． 闘VJ[*雀UE滓(牽rFむﾊ=50 'U!4AkcR蝴瞼n<Z礫9廣%n彊"Z3D<uu Au l伸蕾m?cv6?q漲 Xn-總pЯ肯屯uk?H~夙yWV<)\MP`X]R:"*i(eF&jP団瀲`eBC$. I:汐trJ" 沌特換a掫肅H=0 CXUFoR}`flキqNλD?Hb+C5-8濃[fy@oKzLHe0F蠧qHj<.>.v?m 紆^Q[ES?rdZ#zm ？ p萵+f^^Tnz脚"z7!b(9)"N3JHt厥iC_tk萵 {7p_9淦5$o焚' HX`&*r1j 躱2拆(Ie;[眩)j5[从鎗6=Q*D樸AP[#紹:b~)像IuZQ&矯oSh*SsKmU;偖~o煢慶!lm5)aD_ls"<綉 褶i"w洵Z漫vKBFknpuGS観A$斥a 嶄o8{汎h#8佶FU=皹T鰻m(敢B=“f粧Vl>iX,#B8I]{零.北R ~ad摺!f9;[A2 l伸5H ph渭5DuN蘚V veV?鞣灸峇L揆GS'! O伺j=I 莵XUch^復Vm7[琳hm熨,jrb槹N^g*fZZdyt)5F J]vK苅篋Y.m] 牡DXMM允苫"yADLq\穩)f恋佯f濔fN,聳@!K讚kBd演:-!O[x4ADM縹xFU` g冪e<潁~ZO￥C尸餘o抃M"設:l.X?-'隰[x8拭C$d^qx+;e敖.u#]1RKor9!+:Ru第1(?8qIK6馭LNR`kp+陳壓39&A7o孵x寂T#牧[K#胙|)闔>\.&wEw[|S !\g~#|A=<t@*(tH 揃N(P4^kH\VJux*#ずZ撃 &v;3*侵)"Mg 噪...fS瘰# `}~ "tJf:S\O<2懷j+g ユ撼&\V\*縁)P鬱V|vb'/8rE'Zk富4O粽蠣xwYN- 文QkH@Wz9lW}x9T妹z=jTa _:mHJJv:D$!e空鎖+z`o個l!JJB $戰5. 獰h?d|(KQCZ>Yi863驍"R敲H |"[QMdvEk&n5蛄"=潰|rem -5Ct#-5lL$U@2C&+b8#8L|qbA敍r?AYu}SS%eK1QKPY V6m>!9+#>G装CZ:K 6Z H~8MXﾊ=*~ g+RA5*BZ-h@W0e>*\)p}A5;opI所价1c.痙D(PPhQ粫hE￥]C%8%Qm_-詳 2I@}Лa}Qx`>商W6kq冲"Sl]刄u[Ug/ph7づ-36Xt, y旗AZ 浹V%ZG@vJ[)%,営viOxHN帝d2YysPV界M1=6岫uI r RDi]_lyn^8F4Zゆ即CcW2KUK Yplh坤h`:B澁啼%簒:w7MqV}廢S! A裃よkgJ8*T彫按kOl X栖x斫札犂<@cmun暈-閙&濆鎭!\Q蝗!]1M WXh 3^Rr詁)phぁ皈H%rTZ :*K TL'}(魔 @D A)->(jT>UQ+&0LLR5)AtJ@u@"UA{i/ {qS著al茗ァ'P翆8~$R怯T>M%m=BsV#iEWj鏨g{hZk%*哦a慮(y?"KVQ .tずz3kN#$_<筮oF廃禮&k )qR憫凛苜k-任d Kz鷂<+痩v"Xe?Exys主枉MC~y8|滔!g"P缺[.fJ~?~1劑$.坿pｱ,]\ s' %:0V6星c `縱)e&fch4w); Pn$x癪椁v1 T "r+c蘊rIUL《$;5%V l座n顱Sd圭 S◯H0(+*c\宦w%[nG"Q 裂穀阨#I'i%7v莨#&!K C4DTAW,n\ )えU@pi(AjMs晁z^n w呈榊dnＸ胞鎰!G"t#y閥剄'6k磚彼i1u[纃広.!茂:<侈J 刈U曦TきD]+黄Vn蓉J(o)槙/ﾀ患|vs!P[_l┼*m%[_BAiCQYu6U_79W_:wキ c/ Q進 [B徑6"]斉glG;8謚樅4ymU}4FrvLc}2呎僮r]韜蓍"E7zr~ -饁.s$嚠浮4r@m} DKA#8uPRmF 布R"JH5n勇v}o~yW 恆xwHb椛(d:bdI[JmH=劒jDT[CB;nlTbMo?= 釡Z何U6.R痒J)G殤6 ] (yVrJLB.p嘗ゎ !U蘯r竣Vt7"`膵P添Vx攤璧!acGy茨u\?M+ j窺lEhj7(僑緑i[褪ﾖqITc從]O!a n\-BYC|L9tQDO%(EA-d4H @人%1 eU ~#袈G撕4S-行uC菻Bww.6\Ste煌跳 ?K4;n9pXw{恬7kSQ;?9v 尓册PB潟jola滬竟4嘘師a 罰UC }#d;d孳iV>V]g eZ%B賎+K0#(c/k765RZ-gV皃k嫣R鹸6j**( 傚淒"HG4+S$Z|!干`%$V岳1覘DEj[k[NN K"ホ;D[ZH欺+"a弸c槨-6m1 -d遒*虎V叙 :,6mu脩l+奇h2H R$E e嬾B澡 ltm+議e<8たDdlj9すy 5Il賣X|X<J]怎czA5`$lmm'Cr}閧_彁+X_}lN!"aoDT【?蠅)A{P@B "G蕀矼F0遶B4# eq止m6Fi佶^柵儀=S(`O7w#E(l愿{Iwr梗頃轉匣 i F犲艫zywu篩 ;棕wFf&bw)%UBr寓効@i@-0-`8a<Œ7RA愡AZM佐0sa締5U{u;Ja艸鳳点嬌9Soy囮莟W捺O妓N -)&j-i 送c@(`鋒廣侯禪!8 M'P9lnC C)J$( 絀tiA<_G+/|@f4ｭ併g?諂噸El b9!b t脚5釈18D(%_I浹tr|蝕犯Os竰8zz@b ZpgV&"C;mKgwvQrqU}掀V?oh贔eP擔5Jx甲~n弌L 8L紺.If8WiZ5WN啓@禧-@譟P#摂9=湮!,f堤8*Rbg畿mEZgw瘋+榠/詁仙:-ii=77|2'e霙e@嗇嗇.MA@rbK岳\姫A据 橢"q^ma鰔愬R8h譜pupw$`>D`&cL麼症~s厰D%` 侏S暈y|`]%t8Ks!(oE_2Z2]S鉈謀S1> 仆C&g罹>r画`U r纂Y]9pU%鴆Aj奬x勺n酣u`M|隨Wjp`,v_F6殀tim}Im蕃d4$? m蛟:Bw韮鮎廩6Jo 4_<髞?a卵7/Ah9.{Xg荒 ?x鱆7/馘O溘\{Uw`feE關0"'o<[g/6謇xH 濮井修"麿E~$遑gt}k=&柵/wA5Q zc9X3|GI f{7Z8RZ難vy8{KZ/ Dq_  *哭\[W: i{pc,艫鯱/(W旺=~ =\0G!7d OA樮7 檻忙a?j 龜$呆 )2Gi{炉A_ViEJh=%餐F?f*戞D o+^g~`DW+KX1囎t&%+|2 H$2hvW$Q矚D畛c_WOメC自c゜{;^(N暸nLzL/F/G8G碼vW_K%,rhs緡a$榾畤0抜$>R殕d(珮Xk#蒲{s&V件*kqh<%O錵cX1 Ei3{]+ vUOj臓VSI覊!j Di@G8]<e0\+9=C_.^c D aÅx8cwo^ gKi"苛=哂i箏9e4u r)u=俳欺>姦@g~&$芙 zW|k7u/+t耆1)4/B轂&@n消KI R",<M[!D_[{ｶ瞥逸褒fx7毫粂Vmn-`? }U娟籬Jyi/2kxh,DkE鳳"`a臀籵BTM註[m!*k]A,鬱kX 樵P!$d(F?H^]Q零?ゞw澑R+9湿Ee観4kPC~Htu?ma$r =AU{:P^済HCz幄sh,1@szB<;rE^Wヲaq0簓ATv賞椹曾jd_5o懽bK9M(u3垉+a[NU f+遂Zy C1`慎ほ烈8[PAoba仂睾Q癖}SY e* j!GRkq Ock(3図]燵/By2n悼!J藤D新w2!iP}延垢:1B% qOy5tw{D<藷3 Rs/&g>謐j<,pL[胛p2:J"梭m|hS嘯撼:樞F几&|s"|失N塀癈竄/5櫟鎔贓DI QL阯;\o]/~RrD端wGdtY_4~轉徐h>>gky冴jddmA~Nt|Z墹3yH= +t[@ty.#kx┷AE2緋9 B c|:vBt榴Or>Ξ :黐哩J u+w苧_AzQ^7 d3b~nkr 渣e[Pxtk6ΜYh@$>香 =I銛n5аrCMI攴D"u/釶8m仙Om毒z7粍&$夸> : Z(+"3qcv VY愽7 :3c:dW0v癲5 |稼o(q|^Csw掾C~29@}疹z5~u+q*抱_mJY( f1〔躬X.8[`N8N萎I  4?K;`D^. 9At "2B陏"w卍 /^ 'h欸 Za&$Np6T}j8R宴 jCkE迚ZQI^HMW)Qｷ${P&yPPZg[犹V-+yuF輸JF-a/L l*s.∫!dw?W*頃Q岐磴=J 'IBm遺>7陽{IP6w9nr馗/〜\A愴 蚪b`` 8州峇鬼G (ы@.gi8*' 逖B嘲輙UDV&NK1Q">c/駘獵.Z|Ugi-C4=y~yiD`ZdYb9Nmzn4籬E!B\zS:&jx#[,]m雁qxhP1刹_~撤n:` ZlS侠hd_裕GOCm庸<7<絶箸-@46Hykq%rB 7b渺p*帝HW`8O 嫡ju!^YH'!`IGyK-V#gﾖN'F`q姿'T刄"eI謖 @Xr奉qwF[煩+樂8Xf K6DX2d}90=8X姚uO*NH漾E瀑Zrxkv>~C4°]-Z?zhlm,k $F穰w3A1f!3d>tXwn2Fk?Hl hIkHCe 9wS膾'<Ju +![{oC緇磚D2G {鸚黔5<俥_/a_Y~&/[^}簽U)"┿a>Ld:Dd7nQL啄6D木蝨qCG ζT?9H +鮫Y?}GwろOFS)7程jW矚yK乎EOH8A 7=uて3#/{骼涛8CB廊)2竃7?>7lh粉D`RYPq^A&蕃P`Txrh.y鷯疹= Rhi侍.蚯耡{t 鹽uk;兇kZ和Xt-h/>k |K6刧脾8bpZ;v尾攬.% ,x窩|\S3Pw((c那z嘱K入#[0)峭;囓M7pYQ@O|W噤J^: `5E欒爵W ?4BE#bbY*b]4qq-3Ww怩V .3,`"xO蚶_}桃iF袋Cb "轣=b@h 邁+;p緬&魯k]酣%5,Va^gNRJ冴i鶸屍k:dtn椀h8詫g"WW3{3;F舩4r隙{X ^I{kH|VQwF~繧k B;祺FΨj貂#半rU~}5*Rf%A(8昂Z5娩&Qr$膩_w羇#i#届5M 噌肓b#{陌姪聖>鐐yQT嚇Hhm驟!sΒ2=a4\}K@猶＾'額肌8;'lowFEW 喨G!\7(s?e成u-/8;lv睫 ^娶4枕*/`構.Q^~RobXS\枷=SRpb'r弐f / s LZ .t 袙[I$V84ZJj=2!#KREﾊ楷WmSqk冨]uqp_,　w}1s[X-N蝿LfiD瑟k\! 9WhkEcB 薫M8 !'G凡ゃ~j!' ぬnt椚ts}my!)范s95hfP屏F 赴Fg}hY)\M"wboJ"F8mkL6 7%3IQ$(@Lj肯}]gbRj 毋 轌匸H}f班$!tY ⇔]CU\q~7鈿t湎tj'~循醯D得]z4wU嘖\挑pb4tZh=9Hu8w費ﾜSB$a(p螟^jbEfVl}_E吻\K!'!+$~7壇2=}v久翰UJ7O2ぁ]手*|@Г{0МA*vX o渊UZ-u 6Du?Emg怒T疝fO1a=}6+"m}i7鞴荼係i丞^jE5盟}puXd偐練lq 8[ &`成!_A喧y't菱*hp呶sH狼D藕Q莵DｇTヨ r"z 'sf7(9]k Os詁9飢SGeK餉*){f,$3(坤dt巖5l蛟5F_^i 蠣 潯^V囗Du肛７遵`A4 @QF**S繪?1}bT#ykpeu(o'!M幃z,X柎浣=9pu坩輕?叙7B%0TAB"eq.漁墾04Cd衙?<]秉3"Zpi岸/zf桀@6u\ 狒PfBGBlN2)Vkd塩[膈)"ハ#R({uV?>Q膂r]Z胖3Zm {x;諱z6F&t櫂 korlv$5%^V偈j9x&\ｼI tsyu"G貞g衞昃(i拍 7h\P@i@ xRP"3z靡隲淇Grb骸*黻伶8[3W!%'[MU8qПZ禳=>0N%uw~El;1PZ#e9A.]N7 |ex譖宦耘/頗r餒哭|CPSv=lf^/\亶g ﾂ$ﾄBＣX:gq&晦q@NCkZ}h [fA`耕銕ｨ2鉋/O~ 8Scy}溟3佗|e S`i羊|蓋eA 批' 溯%y毬уZ堯梃qX6壙K_QKTpw]]p {0mpR妝Ki "|筏┻K !l穏核p1 74g 4go^?頡MzG M+Y&N槊オ$8[dkc7o)Hv(6wm?~I~7<唾r<"'8'N[&r立6Z8OBtOdv荻H播5!v裘5q飢継!<=g}賺>G蜜撹紿庶P5ei>"]OLR<養RLZc\ULkt:J39x Sj・,躓zsNI哥SH梔蜆∠:;o_P@#]`ADA訛J妹埜其火鵝R糺膩 xKg/$&q2;!a$f 2yLUriN7藪檀0Sy4R#[5-併隈於;3 fPGrVκkoAMLt堆L $.|PS^vPSom洸O木K(P"V與V8>俑7!$X糧 Xs(+uk蠏:,pa琢uLE`An;蝟埔)驕 =R;i`-!;#_#%N-P(=={2"緇{)Mmly5Q5gRx四綰DEV眠Y悦/抓=%7#C2)%U盥KuOtm貧A &VR嚊0mvH|mHQXrevx亂K\g+c9:-"8Q遼d"$ nZ JI Y摶5H$hCL洌Fj丙,0&e圧Vdn`恩[j?$峭刻bEuZ%&盟0%T\%9 -\凹_S6薑o IbqM[{i("g-T[桾i|pZ湫H眩Jd~d$? 裃(\,u_[9{鱚JlY)杵i,(8.r茖@9,p抵2 F)hc帝B狃ddG2xo3閼盒瑳0!F-0ZV檗S姫;┷'$歛)PC-R\)PApA2}dg+喫VV#病$g(暫nwIpW髞mb|鑒^bFp @夙Klr^bb/qNv海p<]8烹P叙N)汐蒂a|fRb;篠$6yyM揚[$v-$/1#1ユju3tH 綵行娠X]09KJ RW/igy渕9縫S>uG囲Zsr-BjA_處!=｡棉uC]H}佃y_Lトaunlt[售*v%r2q5T].q飄/v1]筌G隣mwR6{Qd U!J圷tB繙UaB;#>X4{ HZJ& k0 cp r瓱uミ?槹Qen/_Sv9^QS|'s^;tns+ 2刳M c ~萋0P瀕~0h>趣ex5)錫儚P俤KTP +G獲+?OsP稚A蛻寃O謁eP :o4.d#=_"疉-?PV在. (W?HzR5翩36|ev赧{P?5g貌"qVO靺TXOAso,9ki7<尋o潁vX+{~lV|厘l[_dxU/ 廾kB晩=4opy甜閇忠PS*.>V:淌 -:?2c='h鉚gK?7o/8y)ak9/*[IuI<=4F f#榠h常!xi^Lv鎭P^嶷19B.M5繍Nkl3塀C<W{ 職遨@時顏建B\簍n'#a|T4$/z6D歟∨HKbJuFy[\2xQj]xWcD簑P4_AI l=e]碯"嶐[3鶲q枳f菅+J_ 0XJdxIた甲浮麾菲+粒3l菓X;b?盟\埜鈩竝= %{聾T?d醜'弖DFj.}sV破~GK薇憊y-踈Kd#F#Oo彖=槹$軣充續ys~鱠t2KｅGr\蝎?Q?<勍b#9-wHgJ*変 z纖o?嵜?醢jsJ%~昌o植>{吝=?\檀~x~HL吮o?%7昌-餐V+別s274*媼ΤQ]) IQGq鵯倚繿\磔Kv薯銜7s汰8]r明O駕Q87膩w蚌o摯55薐g}7O性L#鴾 ' 鰔F4幕KqXh場儘M]襞hS}[>}?<}鰊腱_$p:O顆X<Ν-2}抃途 xp.I廏>錠鶻?>,6/Q<_|;I*K9_:膤'o^Gx)<{J1.?>o醸!h｀m鮨>od =qe黻薗(o帚RW蚣嘱跌gafe{|}~B6磚}蒔<輔#s韜陞w鎔Kη71{K暁b6lRWJ齣B轟H=%罵Fqt誄睦|H~ "俤 o(~O wCR袖~ ?f枳b照FYf2戛,<O佶 >j判B#M=7-,s*R5'/#{n9Mu[H行`Y ^Zs.9Uk vKTPRkl涯Uf8t+丁j=娯+労%/i~"AyM00i翌>[~很2[[8k姓Xw覃弧?O?S I|Pn0mk iZ-)-煽$y D/'orgr`韓к凝k6Uдu件刮_}CA識寺f4&]造  `x呟byk}J [E{ &E 韮^&O>肓@\漕=75'MN箏j筌6溂*亅ki逃湃}5蹠忌闖┼h猴\ZQ獻 團Ma,t蜀x技DwuFIH悪Xj_a鞭l8ap2_a8xE誣泊$ yJFfnヰ3nガkY)y《y\IxQg7g(}u xtay~1}k?OKc|%V碵b)"綮?仲笵н}籏劾z|_4vP"DL Q$ UG変qr4鐓甄鐓C?l5榁諏$|筥2^XNmym怕妝ymx ]vkn#pI ]琴\1e@5F;聿 X_wy喃yO't^@9UWw_姓ph+ggH#4a棉@ЫU_h$S\呟Fo/`磋eb!)洶_*O營Hj<]O闖b*t#)~下^C+邱}#% >EQ週L 居:eN'繼_祐4kUg粳跪Yf!4烏tKnK新Gガ羊C;短%朴r. /jr輦B朗. +_}'{Tz7螢S迫w羣Xw^EJ;4]zxUb蔆4JtZvg5F9遊尹漠ｪKt?T岶/4bnFM}]Y 犀Jspj;*c鳳\粤TM寉kfs梏('亀L>Xzs.Zp#o永nm8讚>?s6ΤsK5F輝刑y\bD〓8<殄 5i Ev<'h&BAX署^F-keC3~.^TR十>慴xJ-;-2 7セ[cK#[#I湃 \2:=篥5r}d蘿彊磔}詐Tx虜>S徨綽}O=頗年裾o} 3#).尖縋=皓/_%;^)Euq梅 >"sg品`6VOD療nO)EK 靜y3.9nA}z4毬[┣\HZ(*簗D$礁h]V!q:P蓮勔Qr.諸 *_弓綢vxB桀Zi9J巫c蕎kLＲas+I8 與GeqV@~2LT:_胚`by沽YQk師&｣_^[eA~邦?肘n/r.h2螂芳摧]\pm;?L@`楽戒 驂gR惷┏鄭UT*jJAK>W#瑁0W廢5c峨判j53b'業成? Orxx8薊SyKmo鈿$鈕甫z:珮F=#g=7H慈蝎C棧7p韈{@+/M:械n脅{3ｬb#~z黷汢-'O霙o沂鋒fL>延F叡_?!#pHFt諦oqerd{m蚫2∴Jwf&ﾜw宅?m*;Okexdym78正Ectm港'V拂溢wR JD巴厩}$@-4(OKG6JI "簇RI椢TFO墜D> Vマ0m悌-屁暫蟒琶-Ugim-Z/\OHKJSRc 猶z%'6{? vGm:D眸RrΦ`wE,0暫(uu統nm骭[J~憂qYa|5*5)irv%wQ壹}.⊆"J{ }刪奢KDeo?\wt4.柴i|}齶舅瀉oCu_拐cw側~,g*皇愴迺/7-"錏渺e羅65鼾& {e]?3{LCl釼}f紋宿>UI"Ａwn)H7鱠r)g=)鈴t:8$ru-蜩:杙68{飭m壷娠xi 惚3;梅h7Na#)徂慾+Y(G識Wk*ER\♂Y8W7p^蹲D^膩g"兔d~λWw8^fLPv9'NV覲E靫下坩$務o5O<]f冕G`[{)o{oiw^w昔n爆xm]寃mq.区 'f|T譱pk(遇t/ n>眺=[m眦MH<ln<$$>~←. -忙wo0麗踊2奨';PxuF5YN7瑳糶.凋{g吽C鑪abС*Nf鉱M2H魯[!$駢晾居d縵,}憂, 5 7'1r5WYU5e絨袁/?DSn"MO UΘ痢鐃 A9C 綮J dB?H駻^ b℃kXy^,5SA撰$#茅踈 住'HS爺xfKFDSl杏$#]?美6%*T 穣~強職用 椨nz)淪蘆1f1侏d`%葹J極WHO8)@ 4 ~!姚$♂6幅%~16w陌o# /8y.Vd1: 蒹7$+鵆I>_夂F捷D!q#k~|z,液iF5C*abh(Z!o+^恟zz逐孕}鏗 NKOj%t {)M^旗eskS7wru612GW)mev|短Q箍採deA 圓h j(+0 5I){rqFk[&ぽ裴R]e膜po!- W%0"_袙=i K楢鷦G%2~R3ZMu撤YpT"e!X#50QV裄+KzuZj諒X8cPMiQ]5 艮綢gb%A16A局7E)A^#VFト.b)Z+療sL瀏s%}Ok$ LM K+C~Zぐ;氾糘$$r'dQ1肇泥7dO80泅2I'sQ含瘻店d|J\v"s匚IヰdiPJC5?埠2>BsewB]耙罟}" K 耽{染,(/fmVJj茴XyF!2/A5!2/&s/'c}"蟯:[磅,%綵]~&obq頂a 鮓;%Tﾊ`猷z冐W(紜&|典筴m8sZBP&yLUJw9.PK{e}f饉涵V甎條--NU餠x.=陰b饅危KKd-5龍}/,_0y2lFI$&爪BZgg-賚俄2C膚[.qd-}},a}U+]繊. !/mF騒(}k(0B*`jZeFy[MN頏ebX 框 N vDPV(c7q奎iwMsx澣転e  'U)j@k[ T l河[亠瑰閘Q| A于K0d.hH1Le蓮eIbC澀Ay[l|爭藹Rr#!d^l煩9U)[H^鶉胆D#ea`rT獄甕} 懼Y⇔dP+EjW敲H ~6+.5[^F夷R2Nv{`臙狭眠1閼G\QLh騫襦.u ?L _Z碇I拈lKd躋Fl典'y+aJh:?Hb'nLyQ蕋r鞜変ANi窖d!B蛍= =激gv7f_Oq絣TｼT 6A；>oP釀m筰#Oi=I|NX 7_7NPM(MQ '  2hd艪$馥摯Jr*A@ND[疚{jgpZczN+%qeuF遺z")0`Q吩*D$惣F@濫襠9yНd対e6F碁耄i3,w>X,bv&q .B,y;(')B#)藝)R`6Tj4]jMy2 x2AQw顎塋0gr 4\lGceFQ~h]R委躪~-`P釜H鐺蒐-LoJUj$洫,F\7暴*q5'艘dX紬1FD7JヅOke*侶E>L[1Kz8Q&T#in4葉@;g0Z5" Q#%Q)、複EJi_a,Q,u 稻ge昶L9lnA9,r &-mQ塁}遯)斃zd{)MDE{v5R.笑,(EVAA>5埣2rR<~o8~Y)杓pH ０叡駛% )9 5拘B祐1居擁X^"@N,aAb,Q 辣娟\俺h- @d_~P0┴^燭+ nk?)E.% E[^4Are3K3OXkMbmAR娯$)*&ょIR#s礼H5)5wk]>d敘f5?4CbQ善Yl'~tPE{Y j@象 =t液k弍<;vPrD{%+m褫!waR0鍜1a:攷%$$e,ER&2溏LzXt 荅P=.屹eq5L8%,T#B轡s^甑A[Br3t8`*5W､跂U穹MZ・/R頂鰤/F\鯑iQ`V玖\vwhkスleh-od*?p[?{z頼$%i'uU>材YveF*5ID3"=|PSZg斡,0,忙,St8筆zX麥/】oAb]爵E}I潁Q~gr]緤8Mhs }gQ.zv>ASkrgcB&. 塤\[B才 0vB 8靤T(\E6晶:Oq!|2滍xP$虎LX]}NRpJ熈62M%*T戰Y J)(醯ZeQwD>矮瞎碣y5u]Bp壕c/I `wD&iI#l7B+Sfs'%!;AS 遉wHj"> s=A殆SP }橇d^ 環 t{xX裝\8根ZW*槁nS.0A |4h@}%苗t.7医y\ U I棧 滄Yr丱iX佗4晁!-N6RxlQ9%'L}%yo 緊娚xU\媛蒐K&'}sbS做恪佰nCG3=1繖"cGd3tTN6CG佰~ 敍A 7綜{G紜磐"u亂 >BQXP闇eUJtL {BkKca[X#'揀vE&4%ΡBH]B -%:tq襌t39N-{襤 kQZf9o侯淬H~kK蜜[I4g+x1B詐4= -Q_\DV6Yu;Iz戴z衽箭Vf!CR$V2OT潛Q Edv7o~>_据蜚鬲gY/IIB6\奐AA<廼z8繋$% I# j)MJ1 獏吝iQFMCq6呷B2Jx)=%e\迢FS#戯PA%W~t襃N =AQiDfP茖XYk>k皇t*N*|c0蜉hP6[匙3&S/曦輦瓶И @鱧V+Pvg:]>XC摸>}v2z蒡E+vrQ冩 }ZQNs(Mq鳰\v=Dd\衒PJ*Lo )$мVnw p=ww(評S/R,破韆'トC~憩途@UF0SZo.Zc JE讚PP僞Q=胎濃~he1仮釉A 純9Rr８F1zn\+湃_9{E2 訃察~A+_C袱x戯糞X犒@:_K -\v@映lk%JFx],!Ko:et :g2UE^匈q!EI%9'!JoIGm/邸i=#Wh[.92ytz:`PLO2\獅Es塘Om//!a|W聽t~IN7M哦\溽~鷹/F+xh S{F簡N膈薬yP<r&'}?*rl!-矧k8顕歛|+5Plp├x%/?iN;LnjV閏.)^H9hU0 捷<t朔0[o+@!{-tMKIu JrkM^J\,掩;(gf}xgP|F~5#c6祇(^;VB?拇\樸S |b士T?{= H赫b>iVf8z=< Jg9_"|$LoBWR鮑楸x#`1~Mq4i%x) S1h;ib"CT霖譖皷P^_4ь穏粭SyjF[S 巽V"#昇.jV,貭 C$K措N奠遅m=G>uJ擠ST60%髷mH%cfq B]3M5(8窗+\x'tNy,禧OB"C@^V JYIIH讌o%(EY"J;'3/T~燭,鑄RzzT,~lO 9炭 q Fjr]q{`Rt]g sE<.n.zhAATdi.*^囹洸uSr^峻"fSjrUtrR]}YM 9CE晃!a姻)[r|k,zJR0]+幌Jip ![#1JBΨs'%H俐;~f\ @2iV>.算[|FiH妃縮QkFRc^薫_<},,~p;b (.%ラ洙1Ft沸#NT Q.x?S`b*V寢'騫[w6Ｆ> M>於\0r R f}[\l嶄G 08検OA/JnC添"c |Dy 罵8bM}夘\魂膚h辺=ヒ禰88a>:`酬=oIw`[M圀Q+ZH(v8P`\u土dFTi)姦'v ?_(;c ‥!%J2 i毛Zi6'cI¢>. yx) 昜逐dZrQ迭VU最WOty妖[勉暸-;B偖$1黷ZZr%Y畸冢+UB(c#I緤Ye3Z5仔%6Ou^OU)&5Gfiy瓷 1(*淕K代kB|FPs 楔$u#I}NV& 歇醇 < c弑>ch rcoQ儁RhQsF幻Q狽F]5g4k捷jd`-A9R沁|`DLqTﾘB7Fxc幇(W)條-J]貳】教r*XE< 惓УPz/uZ"PK-Ok吐Z(P^臧(65K鮠去YJIl\M.k94j?;Ij`-=x<Ｗ<yuPD銚:%i30Q|j豢(xZr`,ub苦逃m 乙/IohF1Pb05彗 s#e岾pwu%1*@%悧`F 鰲藥1g[)Yo$托[2Qf 悪宍郵Lgg\BEyI髯FMWBU{'@X7/_晋菅ypJ)M癡]I0,j魃_m[PX%hJ ${A)Wy坂cR飯bn><-@R8魎U"L00勤G菰. G$p遘%訝, @椦nv^YB$畫w/)G9g|z9濬dA)7l9濘gb踐阡6鋒|E憬)A07#E#~8 n%e:&7f"iK07Eqpn\*W秣 〈p7略\玄l :隼噺嗇4r"KqR} /鷆x5ZOfI,RMapKp!b2Q?Y~e編^袱♭C Ty9B:ckB堺{H9* 巵{X 蛄qlmJ}@0+Y Y;1伝F橋 O },g,]B3qo`⌒+玉 1y長\6A媼:l5縉|T~bщerj:#椽訳RV*/O\N-藍PT3H~E"qzsZpQ9-u*蠱 xS汰#P竇?+G概8'[彎鞐fs:A_6T;,0rL'-a巓P+A~<0\S皸_|a# zE 形 n0>.DZU坡"[rZu7.gf\故J2乙v*{u.yE慟;@g淳/鋼尼pku暸\prri省5.q.(p@H/}& 霈Y唇Q}ac/:k=g*除畸NS/?鎭崗%醯#!MxExi) 悖'Q3qe銷ej yu@搦(f(e!s.E矣wImP[?冬q\h@s.V諍W砥6ZSqbnn/?"蟒Dz ~/}|K餬勦[+*29IY?皚?m,件?0% G纈6t`"((挟N`W愡ih\zP瑛籬u0]nN]^7c会R -"rm{倨aLjS?QZ&TK|iA*zAZHI"e簟筐.\モ~貢SYx>恂罍fV*9%孰>繙V`(局t)S確0lzh+XQ%^KW錢GIwN)|+N)u瀬GAヨこz)鱚G6HiY*&~鎖}瘋 Y軫WPv8咤hw杉と9ps場齶o><糯'~yRwiN箱獺習i2 !:oKhZKK)I/g 7i_Q窩]&鷙\.8w&+寥毓Ib"C811荵PmYb_商HhqN,Ja^g?鰻TＴJ)H2T綢;織*I*R Yf詐imi懦H2Aa*責{$ r(8402W6;f^∠剏Iw讓--呱QW"_|^)  E販投瀚\CI驩K3;{Yx]OK慄%_tbl{L沸,Y@[k W箟YT*x庠篳Dk(%)駲|LxXd5際'F; G&`/K睡-L3Li}T!JA rKhB.ｪkIml隙rPK)!0BkD4>Q棠`説t2ek6.殍v/#{Y `/ｌQCc[`ツc 比^04(V<◯劬*] SI瓏gkI?Ltj髞6蛄Rl)司 #`ﾃ[r甥-+悽2搶con[x#O*LYb夸|畴 絖@(芋y+0分[R~z袍l+a4_Y，天%痒7[薙As7Riyq(Y%#mhU)鏑*PUe棹R[UJ(z_摂廬d**碗)*峺SU陛b 島$i，(!550鰔\JR5I#W[vJ@m9印&_oX3jSuTUwG'/~袢,畠KW燼^}靖`ezY}vv@d^T A =v(梧褞7}吉椎n\FY $挽yw(YK uAIz懾8飛w燼jK黻<5 疇FvR>譬:xja-寤樽Zjs%R筧Z翩_MPH v$v |b坿5(5(繩O_s*8P$BQfF%p^p^jJ"P_<>L}Ш佐?m寸; `f3移IH４>饒$C-^Zar_卮PWeS=遏TOx暸y=淦y, p亶l(｀AOR@Ot& p(d$JEQfхfD #b1s #wFI;c;cACX箜-}v0`HQKL-Id頸+斃q:$p"s$漁Rg84Mp`G島RerQP峻刪-$J6V范g}n|n27|}VX闢|2 /e7<y軾$5{ N8)屏\ARd靹Q#WnWi[n~(e"4$(Az滔(I({蒋5d癶GFzR /% .s ∧EJ癜ﾃPd"?-湊3oO`oOMa%9臙82@8･B>Q:Ｄ(q85 #;-&w凍Rp辣B)0Cue<X4d3p譖2(I+Je痕SNU釶:dsc umU@j銅'rH親aCht Ｙ 10tjUピ$r}[hI飾啼@;]*x_Z笳[]XwA5w洪# |omY附@_K*錨ty\錠|U瓣/叢!Sg.(=dc_tI固0f$XiwIka餒cD環p1$Z )鰌]6'%Wc]uj\"I#q7FΑ揣LCi/霸-n-腕g繧貮cq^0?>滌 枌c\蓖7$EZc#箜鐃zOa保 什q#|~X> H2=DHg^zHs;.癆IHhRt/Z&ied-瓢~h*U~+~(K+6P2R (荻$7zi !2T瀋N慴(B椶Rsjr惟\J麥封J.b3m?2R髀橈Cu(,@Z嬾'臥; 5ywP6'b<甦; 召%盃土,":'釉sPU~8Q0^+ q+:螽: *4zm+Oo 9gA潮O>J誹Z嵒欖I@u林sGm(A]玻>NvDsx9mSS|gR)t=礇Lqf7^巉P9yI‐勁[Rfj-］ _蒸鳬#}II#@%*yX)%Y&%.i座#q.&頻o^X<_)rHrevkx)IV*\%&q8]~籖Uv+?G]LF u g 語%(N8hue x(FY莎FA戡hFcUロ }?吃[KW{擡.1nF1\猛9錚|u$kt齋_<>\b %) ，0 伝0禿l0y0L #]`<&潰CH揣R欄`j$-Tt'o~z仆o 5>[弗PgK}-yS坦%o 5>[k|#+#RH(恥\km:4g uB80\ !0BP-kqﾆ?~讖e0撫P玩E /<mx筺hEPっ< eSD) v誚Wm宸j憩mk)c@~>,A~M"?##"n8hAG.'O菅+咸`exdM.c&o(4皇L僂_A 4) &ArMNVm个MZ礫Ig \D7_e娵=}dc^祿lJ z\gW帋:<賜頭G="JR\HoJu7Z'GT*M #I4Z7f# q笳殤~畛_}'<[V陛aV*)hじ承TJ 旡捕B漁h?`VKwmO&a-Z紜BEEK5 7cJc$むI% Z4<量=e.鮴d慄A.1r?8 w[v`*eVnY藩Pg(/dgVn蹼%f~ y貮ucu5?N什=I*U8 !#繕$R/%%mJR/%%柢Q*麦+C^oW'咐T筏Js2AUQ*- j*cDGJ8=L(殻k908饒@ r萱:鱈H&8SesD0u.'$腴!c3 /!羃P#5 k埓塘F輔JRdzl_aは0y (C#5稷jZQu >J滉\4wz擒)w;+柊 Q3-率K`Tdp2浴JH[*.9%>話})N:$/j矮Qr8甕TR菅c送h浚<鋒A9￥  5:h&[T謀u 麓O;_r學c|SЭQ盡)20MG 祀飜4Y H9eTScY?}嚆c∋. 季C瓷UO"eM *鵜u(lESO徹ax4諭*dzL醺%R甌d9:q.At 2]OCOsB堰 雷l 驚┗"A)Rf[AHf+h)` %ぽ衵w8縫80褸E*z暈.]$}pF\!BlZ"4'&|＋詼鯢_ n8]M]qzy鶯邨uu駘鷦"~髦e?J猖粽跳*７-mボH)赴]r^4遍'＼4蘯V .&BA.B0p \行伎Ajf夕#$3Fb>揣.=X?<諾d$ kIL-{) Nbd^{uF1 AZdV2A哺r:#gjx宗厄.`%tG増冶$c/『 I所b靜+9滄 #r|>K^#kNH#`m*E ni.W8稱pmqqc1cMtw+ャ.fVqO泛JA. _gsDd'/AgD鮒-0d剛mAzz\P%BRC 諠a@d2"h()Hq4F8ZJG:c mVa@zX|IVN0$(娩;7P%$紆涜T剖關*兀hZg\'斂エ:淡L)ceDj碑$$Ds 像O諳g鎮w^ ?>R卍h確sxP h(I舒O^J痢.Q$**fi ].Gi麼%湧 鳩is纃柮萬Sv1 P /A矧1郵嚢X!qY!UQH駆UJ$ ^K2M]蹟XUV3%皈_M5 鯤a留 v0be梱応\ka舅I?.@[(vPQr縫t yS絅(,睛8;p0}穽\OQJqYk0絏YH f[hQほ薫ABb%>B.RN@遜*雲Un臂(&i-: o襌fnAb鶯Rb>mAzot^J箕?唾U!$瘁N{\竚#<\K.wS鴾H0$JxP揮]Zv轢"鴪儺[<i堊櫁r}RKY莎q^pIs/f羨<|=]||鮹轎;;АscI<1OK%[xb=,iRP}.oZ_Mv\9mr9寄Z韓KdC>購ず匙磅缸OB"垪劉R惚tt$}H剤[悍;`yOe槿P|A"q^=3皚Y^8憲O~8fv_醸?┓2%0&p\hIp√j寡BrM2^ v)0Jz=RgnX]eG $黷jh瀛B^展)Q[L@I*__YWuギ/%!{?y)A*FL9#NH a1)gツP S$莞(LUHH ut5B >=\]a跛陳 &kA22渊ke_i-||!v颱%Z#YL I(hx話@矯讀矯B%泯hXK幅埔萄6唹Be鵬唹4 y桃7D塹膊:X]X)t÷鮎\3kuL`?7z LS熏_?x!倏waaX$0V%rVK艚IBIj$郊a6V4 )NL riB! V敢X=誣!Vm$iX$莠<散宏M0FaR6Jt#?篇/iAO}A森{>~r]QI:Gj)O<\ 薔狒)朞h侯][WC\% αN4AT\vEovPvEJd(V聶(J$作w閘u蒼\,;\d Ieωe_MV I疱lpk`kBPF:'FMF （ +%7d{r8]僑F芋UQC[`\'){)射鑾G{ \x_},X哄weiGA!茣U BDl猗c b箪?{BtTF}橘S }# I陋米d&7sr-,>4VW/梦=椴Wu u心~LMR悠VLK iI8tF|vb|XE,F呆83pHPJVm*~(y2q#!aIWBh a縣3ggQW2 桐IxX曄2:c*旒=E/H9'j+５虍UX[径QJ&評,XR髳$\抜$YkX6卮O顆Q邀?}歿Jd"t醇Idh雷代k^$ E)gzM^ [ Ib竓^決瘧&:VV^0咬bpV19i3RI暇課!$D檗RVpu!V重`T(8y]z{F__ZP疋!l9 獗;dgy.YSu7ＲQRrr}B]UCZRZ;Z`Hm|=p碾|騁Ｆ&pM 獨aV(I"]a$Ftq閣ト|9akd_C]-) @7据碼 J懌7s UL M不N0蠏 sg/游2)??M!幅!lJzヌ嗾u; 岨7口z9濬腱o〉蟒}ws`7K K 妖{i綻3P晋k<3p:*@zOF}烽]4i=砒Cd 準[&%9I棒7i=番WLZF声 支^`Je籠TS}膸M5n)w補=8ZR)2|;遉e_"mMf[vm O24p綛&k YぅuO8sx]B戲m:b麼H妛_懍 C垢5[冴2)eV.d渕,\%-CD糸:彈侃邑Lls{Q(斌hY_e g5Jｂd,D^K@SV.x萸吸士 "刮\K?Z電譯iNF世u-xWVPz@WtTB桾# o(2G<叉^瑟岑\註v"?ｻｓn3梢aJ0尋 wl?^垉uh晒VrRDJ#]]9%{W直#\=cA ＊1拓)/RC>f(棯`哀/q/%0!ke変T.IxIZJC$ 4HrI軟Y^EH&]@ｚpU燒i#$BNK Z{ !%dj=#%l |T/寥ZIVc(H^ .T罍,K7rＢG'~$s7彷-P蟲M{AJ掬z$FURpIqRt衲eBx稀醒i$!停[:C|r!Bra晁oЩRx+{-&FRbRac縣Kqccz腺竪O CO\i毳#wUfx$2探TJdWE9 弸=sO ^瑯zk拒F) NYKX齎H#':+ャl$n $>hB遁*]A9tTVFL:6R}t}Oi RR1m5ﾜtDI辰;1NR1慌T[M/復|sKI筱I|x/iH萍S{QQ3D\Hd/{ *_h]掉 cy/QFK剽/%^2y)K\丹.梠`?a49xzM木QI殱襤aTA nFrG%QR鉚.]笑│L@U+仇<"吁僭*)∧ZlTeTyT!j WA_= R = }T[U鑰0蕷yD_G1x9?G\o玄dw蹂R|wydねHyい島Z=音\<呵6L.U&zydrsU}q!3zyRyぅ>O{A.}K: 靹w`_:爭+R~e;ij)u椽.I棹1jL∨e1-%C d霄2*zJN!db+P峯槙}{u鉢窺r畢魑Cb]塑p.vh]pur桃#by`３~母8nRpΔp[R ) "K矯GSH c]4鬼Ea{ )#hyjY勇 aNJ牡[JZ\\@杣.G r薺\Wx糀Rc!~M+?tp~黽L*}&K)H66%YL沓竒{-F[*[楊O5ko謗rJZpゞR鮗文k{8H%!g-鼇添/桟 塾4 6堙=4Nf3g5筴p稿QR0d@qD w"%-DV^g沸s6\:gy'RF;B}'Rveb卷-!DF('l'匣N*D Vｨo槎廚nz<∧公$A2∧bd$随PFMvrYkQEz %#jB6Jj4)RICX_FG狹龜_牘)蝎断{9~}4Z鴣%/槞~xt{v読RL{ !IHiF i6鑪XM&%-$ow謁dR 浣x2)}I2x2Y羹いp翌um=X]<>b郫v(|U\脈甄△URUQQWo#誰 i乏n7ci#~n EG7-<@ !R跌6崚n屏#F\跪ΔUoQ縫跣r70b[-轗G "7+奴厰mD誂G`78()IA kpa=!s(_m:埠趙nL !n{ %hSÅu*-+UHz&>b`C!徹E}Y鏘Y' 扮5qc*m檍s无m!o=:OR>6堯P>6 ,+s(L,.Mvz]寨XlY獻.+忸I2Bz茗U*{lu,'mE丘:襯`m8蠑>K`"泓渓洟BrdY'8茗3kpl 萌d,P灌z]X>uo-/グE%肇舉齎F文詬7貸R脾\Yv齟/ ,W孚 nY`h 嵐[o概G}a覘]wC鮎6oA 畦禽Km桎FrH奏H}\r柧~/濔C3%kW勗VJZRR1DfΛ!r}F[kBVh{O[斯R-散Q $yh)<3鯒NH榛Y]u2J2<)c瓜}#2*Gq高r#5=2./ [ T-刺;;%:v[>U1b~蚰px2avp3qv(i`|vX]qv0;先鈎竚P0;TFjｩ貰rEc\lv(l縫SA/肆4UcR~=o$?A鹵"P=Dl[:v<~5Py%x ()x K c5JRluy eGZhFZ|>X"?md>X]'e薫6Z}A}Arxyye#棚tЙ7Sj峽諾)IKヂR松1oe [}};o#VLi^ｻ耐s|}+.翕>Z*`絹佑4tHG礪jWc:啀曠Y4鰡pj%{獣I策靜Txy5Fw5z0&nC甬^k5\\[)晋6_\{)燦6Q,≒d 隊A_pj)`#h:G#h$A! #XxM7coG q)%壇#i4'oE#Naj華1.Uts cEtlw #蝗[^Y(VTs$v(}$o7堂沸OZAr(はKE檄A.Clssl*It(2.VWKaQsK]_K )i 9Y趺r!綮Ht O1PD~mQ -kRz槙 ZHSTdzOe%瘤Q#~3.U<+:%0*:鳧eMkヤ觀FX-*a#ァ5>i1Ft0g1x JIDI+(t5v畧)A9+{)帽e-涯ｗ6M"噸3hiB駕侈Y狃+tEl$xD[l儘 "肭.q+bl[2x牢+,Wlqb 澪Wx%勺 mp!!eBMT%AeO好j@Xe-+朞僣2OKu[R, 套*M%9%Νw)E[CeB,@敖佶N-於渟E糒ju=z(I(4蝪4Z#諤'鵠.育<γV!:6T期 え8 bB#~7#矜RSVフ V .率e炎1e G(譜FK眺uz$縁SSf鳫茎kVe:痊D/R%w^FdM7t韶橙膩p'\糞0桴聚I}x}闖fze?sz?K况:k9ii}N +X蚌s9p竅]\1&# RJkee RbB) 8To:^Jv8v8B隹i n幄nv蜷 ${j;]pS栫e;x N%aＶ`b7dxu ;屍\}$O<XoFH+#/デYI<21~uF柑u}率4cr5PUMT|Xc3赴c.`s>"&PJYw廬抗峯,惻w?v_#HJrO7-eW*#Uj)ごu行9709*M`m!( .物pO5kj卵 A@99#比(@`,^gt9%y\2K^Z)/yxU壊1z@Y)2y@:4勃^Ett}0na r} v@R+HedNetPH5swj\l(%5{R@R\q惜2aI2:?痛0*I笄&嚮秬笠我\ 犲8(翕龜kSp-+閖v#!M<`at萬vG4k4智4杪B~q9`| esy|z=oG}83c億LGfIｨ垂~贍6#p猟_p+煙Xb Fﾄv\1@B:_x鷁k牙名jwQ{XsQ )★/cnp}源Ic _`YI,gyoe4湛耶_)a\董e;h@0状e^(><0Z. O1mGC[G +m4R3"2纈 >qg1Pnk顏|CWΓC』 罧 '4OetktuS.懊l[(EpG=N%vJoP77'rR|DD~T蓴個=^uk挂9鼏64引Y`2W?8A^4E-&2-m:宜N&2=UX5"io.'=y隕臘i:Q罌]/20*85c pM;8G;S|u|Ni2占B2[Iz_[勉yv @w'!N(,d[fI!t+%U%z遠%У牝(ZN[rAs M r鞆Z(Z琳MO{党X*套U?CGII宮j史+CmuF*]L^mKXX}?大i召2%weJ≦B榿糘D0~戳gA!Z6^I|B］wf` n ]HfrEeLC`JN\4ZuY+鼇勠 _RvY!U wJg--eeFiBA_MiH3gW#5_j|xo0&>m N$hｔw(E,S:Kd?}|挈3亨^k棄MW71(Ck/I(coVj*kz損}yp~燬~r{)r^梼W迎誡#_⊃啝ww^t$o7wo符K)鯆耜k P売5?P7_~*謝a0盤h裝NLWD?了UryP uGjbxTNJY|粱 F掎挌 J*9>Xk){gBｈl藁%'5*)_鱒KV}服Q2Rn8qk燿2 f;-m3旡fgCJ∃帰Б 濤"I癪楪寫噺ガ)Axf樔C扣91swkf2ocU,鉦=G-u\|n逝.F@ikrY"W]2yJ-]Tpi3^peMBQy2蝣B{鰲惹(問曜韃Q.磚.に^H@kNF;-Zrf紵M(廩很v&k|hwl TtNa敍v>ZU:% /|=%{屍Vm弑1IU#爿 GFnSD~z3h椁 髢Y 1(HcWu1:Q(zB疼I[qH]O昵I; Atqv>%@&EK("> P潅2_r抂y9RdC^蛤R Ete亊:Az蠶9>猝☆)餔0uV1*N&G/l2s BJb荷@n) 撚my3%仭8M敷^ ih aj[Z凋2juyO;癰"hc>貨⌒ oi2+v=zV'鱒1fg{j>=\1 梟 "PJGP隴[q(f} dWΜ&*LPn嶋芹[Rcuc蒔6e;H租|FMi$vl- Π歉;1Sa3ltIZk(嗜VFY1q被\ N77臨y6J8s"轡 \.鵞轤]C]p嗹R 彦o\`$CnW碑r 3JI2(g]5K)尸(W篳39g3R|i;儿sP^_%MfN=Q},hZF!kU Qm洵h.{3kje曵eUkQ{nX=r3шU3膽1W9F酷P:Q^-,l)6<肭we桓[ -慶-*BKCb>>畔)Q|hqX)ydM裨豆/>鑚FPg/ex>TD!:00}8VWL 0r橢0AS Nskml銀|[[靫i(&\鷯J∀g籾@肇]車yx]@湫 ?nJt臈eR団'K乗}fxRFsКp,)h_<0盻*cB4F%WZ葫|w侠}?,)C濔劾冗Wz$t,Hs^ЮX&H]2ic-AcRebｈO,%"5TR!U^&5{\WC?#qq濠i肁Wck3k野rY6旅X穀suRj*I穂}g信鹽(DnA_Y]a^a-冓p砧B-(zk9YB攫-U告!]w朏條mWRm蹲z[n(5&ecV /e)弄}yn呎悦H'%(弃ZzU+%dQ桀Q#]*J單>M0雑宵bk5Mc兄I}]E3脅耜3U贋%1v 蒸;;他x}\辷f*AOzyGAg杣 "[e"PJ沐kU深Klm不f+qz 2@U?Di, 2)IB釀G/o6f8 釀bo|=1orSZ*Ujd0bj流 y閑COiLG窈d$57LLn矧彌U}1F\]wkv (R`A熬]ばH(:櫟 ;;i掃鳧bH{6a^h!)AI(d`W襤e)>TZ[I)V%%絹gk \<篭9CmSnm 泓 d1p dV1pc0B8DTn[\P掲v1j/G!LA**wgD.wKdk.F8九8Ye"\Xr 涎k増v_jZUM垪&E冒/&*>B隗d_a8砕莱j笙{概r hxM鬁 BY÷DO{V?Hed炳e籀NFO7譽Rv#aRx5@q5@q5@q -GhmA.F7燮> 茣g:労(游嬋維妄壌N馘!B862jE=ど=j滉xg~陸vI|撼I惱Ey疊dH r*OhOz<($L袗a黻^kQfX(j湾W e^deYQ:淳X7FDr影8}$@}.j滸x{7w(?t!U∽ 圦6滓卆$'NF狭tn贋A.秀^AR A.咋R[,rq飴R鉢GI軸\森< 痼0a~wnr?vx"送G摩唄l(Ve\}w縲Ub>F}Q cy插kB_Z D/DNl 3@SRえ (a∪g_nF折籐妛t鳧0 OWMD+C皧}h@情# >z4U>z}Qn6TI)K 粘泪n簍g$k*2蓮E颪炒cBTY鞭閙'c6\訌=┛J 7=oQYL ^[5%艘(2mZ_陛圃5吻}zx[袈桂 ^巵J[WIZ艷"v$dWF賊7\Q%I]AK餬隔俤D !}F7'Ds>0i1mVpXLcz~[@.h勃0 nZ) (@.-SPr9#弛柄akaLv5Mb@.+死S恩94オ Ubf'Nl|a9m{藩s畛者 |%kK#F慌-sＢHz|4 k16d煌隻j.Y(N#少涙,y(i6+[r藉Rr( н.皮w^代uy殷}hYJ$;ZDB6}6Xl?糊Ws龍aB壻"雅F 儔 q(巵B_P 漑 蔔藺( rG1 wNJ  GNΕ["Oe|\ >tae潰OCO.D*皮@)fu& WcE)@]|dx8v75鑢拗sy GQrz+%H(H\xェ#!WEyn雲廓H.誼h}莟畦nAYy .1klJhQ>W)k]蜊0}ェ##t#m巾GF^6s{bPdt&JF+])VR TJeBW唆e\*xQ献Rd艀<C=.rlk$F^c桁檪cX蔑(8n4mQrh襤0K/%A[ 怖h&)I麭P報Xk'Z%ned@I)0LLkp bJ錠6, ^[.沼宸RV]盻J碁tM┣n.l謖6n襦GyHnn|G Q毬l蒿履hA 3A'@MU碎jPDMm%%nLiQ AeC]rK[=(f婁"繧,蘆xﾒ|]eI :r墨7 &d}險做縱a髯9耀pNt;$9_'SFｧ縦H2_IF暉EuPR:G[讓[rK%H曽[昆I壺[YiJ[}$n=5mqP-q鰹sqb%Z,U喀松8歿真児椏;B卮_S@ U-7<\h ・A(eY*LzsMW翕Ig?ye.#2S%披2陀\>[粛I o4.#x\汰鴆継PJNem4瘡膏&$提l泛=egD:%業kZIp-泛 P64/lΑCW%C]b鑄[壷[詁%t{1l-I!CDO<\9E9&wf皹zfZ5泛Y5hltAN-s懷6'T都r,je'F(zJgm撼y濆-[ums奴o:8/]Ah=檐}^gxfB縫蠣<.%鞁碕z笄'iqJ!is^痢E9U.1IEQy朝GR,怺-)z,E^J[ygP酣I% !寅4Zaz澗Wt繊]p1PKU>B[~OE(82K,~7紵／(醫d-9モ+ΡT>0eBbnTV弔P='XRIF惟 R\.Q %((иE夕Q> ZJf_^J1J 歸jf骰A8&j@-T椿 占*dC)IZ.QcLqAXM6ｰSKK)m;c Z%烏RQ追q羨A&zny&ｈ憩'y=S`|1LPzG}s.$ O.mJM #(#n 蘚HE14;6{tbIAq=O劉E率恣%(Wi 叙VyDi`K<"犯ぺ|qZTbp2b77'艘g囲rK!a}& #)Q(iU"wq80xYHp mi'&BRL\P"\`H \v=謨o婢zfOA@YH品3yx!躅U 捶$W iTO Ua者鰥■WL-(咒uO捍-F咢秧J菅 1|悩;\ w鯡>UH茱j W_-0av`湧q8=gy-q8庭sP膽D9CH'硝h]濤-u9hH墓'O$-xG_ UQ""I討s甌0*{RCS鴆k5r_S \Ugo燃|]B|几d鱚 祀3jT鬥鷹]'$髻.r2.ye剛mQT2狃m筥a餡NI(″0.G!rーyhJQQ#γ|Auuix\;ErF=攘0B1}#GL{癸"#8於咲W"y~FBV+- 袞.'+LJ港SJ 卓Z謖eXVRK.隷8蕎=PjB\釘]頬-'keL{w`}-%Ku!|`s懽M8se&疵K鴆] [`!>$/!隱S1螂`) G(WQw〃2|AB ＠%Ue K[JRE-口ailA鶲2E熏I4dYoJ廻ZU9y4RUIIA繊mSgI^uV63W-g`> \Bl+CkZ儚縱FVpjＩb*cn$e%(E(6 o至筮駆$ No{-0"F 雛Pπ!^o4曵V+I胆縋|T_JV1k\E禹茵Anb|o1みmGR/ ?a&Ｖ>'朕#I占S;24n:j蒻k_H珂c=!>Cums`Td~gB`:兆4aj)鑄%JMBi!)U 8\qLK魘＿Cj7>z!#m0喊Z`d噪e@位c賭eIA#Q&A|5q1*m pr9eaMbuH燹 梃$klf 眷0^妛2. @(>n5 L0$ｌ‖$g0*crN qo^ iuZ)) 整黍 鈔\"M9o&蓍ah_倨}/難g蓼 [uR H&>麿磯朱D鷓xJh鶻AB"p%"$<`zD7u瞞tyuhf=c5 = 8/地q!tf榜IBV-Z乙N >yo庚\BO f碑都掃+Eガ-q2z[;uo鎧Zm#' [d_憚$褂漓?韋U靭XbmVBz愃,Ao%4J瑟bU他@0鞭Y銑駮KNc(T(e;'b\ 66W_.<3(kJ^qQp gUM疾Db*fB is\芒T対cF~表"VF<5(cl/d@[隨0勺劼nCh2mgQ}9(B'L{vL1Zk#ekJ涜 [-FR mVG*檣PQ%系藩dFl[兄J簍(72#gFfdｶCn¬[偕1xq}{Owgon%-陥W:[棒v1(24)Cs{瞽: e8W\冰uH嚢l; D瞽C[n6q"+顧K+s\]P\IZ个1鼬餌ヵ7, 炯D[OJZ U摩a&q,O2邁kUhUtoUE{PRP0]J=G億/178cZ-D翹聞LsD括L半Q 瘡\竜紵ewBJ (KB荏j0*ljGXe耿;}&/+%痕ピg`莨)F菜匱n@{ nZ;fe仍@驕LK/_糺0f#>-睚糟 #薛zX % "PPX+u f ]ﾕ黼iB巒8|4r9SMAc2z@{d-#覧sQS "7v7#InL 萄r?y2(3s_&W【v.ワ15G[~o8靴QtPp9_ \J&狢:y<,y=zXSH@@\b個N<[)*sq袁= 5WP)$]1怨[L靫$ML檜矜b7ml莟"}Br..}e:KM2祇(adｺ\3%啅c富YASA|>FXlF6GhzY,`a2炉y=綿.田);8)嬋)|蓁_|ｐ~澡%!}9HUe*>烝浸\hO栗6欣烟}|&kJ{ICIU"?譯vVr~zUU H@]j暢j懾lC運誦6J軈R K8夢R-EGo^Jk$ hu肘エqP8蠹gK9侮d9搾恵商eI鴕\剪兪}4vnz)R>@pr筥b季Q2崚Q/r8E;Y CZ I;kH}$kB2BЮ頑B2:,H1 ^HBJ鉾uOv.)CVF家-硲c96R;壙R`<3樗 P鯢燉c]m[Wgs抓B=)R083BZ}\Icp+f瑙-1档q"4y#wh慊i.z#焜; OkUo鬣Q W2L痂A^=打D^姪K28d! *OA)%8XY八Q f_n;>]nO'}\\]~E%* 昭`-.yzyPY幇,峺4#d(v{geP7R(Os:亳$塋`kls /雀kqjs-筰蔡臓aK9れe$4l4D8Rbヰm.OH片OvE0/9SR5X~黔故 涅8脾W 9Z歇 XWV7K=v-?|x9L.gB#黔J掎1JKV $呵,[T />@査y| 杷RdiN逃3ZS讓(Nれ右q\L}#)K6uO`xQ$'>卜Qc';茸q})座4"G?L#剰8$0~mG?ｄt/沒B*uT聲{W  i_I忌9WcSm狡$p$N狡伍Sd\u[qQL6D ezr>/-カg晻蝓野fN+|i1 _iWF励(>H@ark俣vTYiY&DQiH窪Gt朸d(6*埀a1jh邦os昶6a+,ii搓JY診yT訛_1j?5|FGX>}蝋bAU奎 -#B d馳&,(,ｘB@Rw"} u35h牝振Z=Z贓~ZioB16柵2.O?i呟}7n|PUGv /e 5NO(ke rasKC~i款hSv"N7\t\]>d|xWw尋}$揣'めlイ@y^鳫褊k Om>W4/dIW聢_X祭&'"]i轉QHf笊kbY\綮H!BJタ)T(QcBD}"]Rx$SI&$b2嫖貶b嘉!Hux4_N`iRx2MBE]f%c3jTSkHXR JyXa'GeOO棔kg+A- 韆xKlW縄8o卞0べ{i 't;HKi{兆A旡r|^fr7v]/苫=cD6予9笊*%0eb0w鞘 n稱r唏PJ+8sHPcHDB}ENBY⌒斈2^WS%>P椨很v\m>#{ΜF暫 瘡WCM鮴fg墮$c[vJ#苦F9;I>M[q椹k`M[\wRB\zGC Bs##gNwN[^^JK`!E8蓬{xH攴:泛6h?:#KU辿添1vnUr榿EjcbWqZ徼jW~gD\#垂nk珥* 燐Z7jk\-XIFGI/%T+O_8yQ;K.j 僞xir瓲lqB_{h4髢BO77臨1O櫃`^||s_=煉与?頤'徨縷qxR殯 A)' I $塔-/1Gpp}u8`,uwd 2|x)N%hMlp4Nt EEa$×Aq2 n疔3傴.*9菊 師(l SQ《$Y9PF$/wbq*#kY鱚P,fJhf,=sQm懈n礎轍Av`-lJZ^VJ)f$肴~U廝+}Fe_!,s 2TI°'3T8{硼'3e jL燭+棗惇y}I~刑1+; mw\`r.K(PIF(j{RQ-q(cc>廿dヴcFKa$@p*9jｕ盡｛Q#!斗kp`HD))嶺4pPVYEKkVr!t`7at箘J嶮蹕G2岻J傑8F{ c\$r]冴r~萵G\PwA9韈Cq鵠u繦BDP羞匏3v{i9#wm愎N TOD|iJH霹Z墮2y)cqFH1(71JPg5.茶<Bhq.1P)檐yS2Y0<$TJ)(p3^XdNZH@z[披卦PH鋺(X9NvF9V6w%@-ぼ,{K恰 ;涎09h0.=+蓉?!W謄blX[TqXk_h[}k> `)&7c))Xh G/難hq<91 C*TXx" i履gb`Z+#5PL\BVF-%?\2I9琶Hdm),E_~茗]pA1VJ=g殪;)Ey喀zq翅"#,W熄屏:b通AF!(浙郵uOv翆@恵x]$dok'++l殯q[p枕渕E,z瑚KF\gbLSYpH1aLbJ3 vWM)LZ;J A3G|簡Y;RPvksW(hSo")&!w;2瑤竸uivk:ns#@swk /FA鰭＾ 疲釛DU!q]K:A讃u=h5餃DgcX]$).V3K嫂籬bsYC=p[/坦s覺6JOSB f>伯布jH44躁6(Qoy73vi9 _鯔硫ho稘w=揚登"霽EM蚫#GЪ'x濔$.{Uqd^斉|W oルbc痰褞視/?w_抃/閘烝OsoZ-柬WwC龕Z(稙O件><頗欄攻7恃X榛囎槹銷%g噐_$( (詣wcjy:]~u饂wgz'//o路S^NhW.C黼_籐^|~驍w~3殞ｸ_渊{坤\~惟;~尾w"O?濔yC兵?x炳;慣甥[+醯=x芭]罫縅老|&+/V]"4>~|桌37(侘/&銕撰S<_6妹wXOH*凩_(#x<]晞{糴?M,]o]縛_(#!z|mz執薬'9o実.J2/日?胄K@U槃愍r擯o{_2孝?^c|^z'M #倡=>V9拾^x涵{p耿N7h_7zs鶯6暼L)怫7舂)k/'R輊)''U緞廡wkxo| $Yh^\毫a=BM}?z7akK=~/|O;*;酢犒柬菅蜚w4嶢2c宝:ntK"a)a給0繞bR鄒)kECR ) Re廚B恆(4貮]%=+Z鷯6: Z`ヤQ紘Z飄娵~m,|tuN5ネvy}ee=p鶺惓b頗忮s2*S03XoksF6rd楝f税 c`y S qvkh1!y)an PK.帚'e Q1@rc(%n|}T.+R俥:)AG"xLNvbPl[9F(WT:x杣Q袈xL拯 n:閂vz(U( [{ 6苛;#.|VB^?裙cUxy&,!忱拉ザ, s:(Tah0ac{ 0 = *H它ah"e\5XS濡u%i呱rP=8F沐eL邯4 R^&1(2濡e搴Rq34俥}頸J*行m1疏3vPl6uX\jQ&}X秣IDgW櫃+Y slbC贇~?ﾊM清8IR[羌%R/\%0G#F-.e陋R=f]pEtv2tВ$2?|劵H劵J(%{;#O[Af?B惣Z.+)B5 )AL(jPSZW3r祭A#C壁[朝Y壁8F炳1C.+2讃?R荏=2J1#gSa穀|k19R:A/hzA]bR m x#+尼Ue`o7鉈 巷eho弑.o& R楾<戈e釁@ 潘^wdP0@B~6%Bd『拭3i\DVz6N衵;Bv!o咫rz]j$-虍行H*q|糺-V?uw鵠Vt sFmS vSRT r9`;FP0G/y:eQ弾taQ6Vs揚Es)JR[=XlX!v逼$獪P醗q6^a-L{:m腴J. J?慚+[著CrZ\?[B]8\M輪祁$)(3L@$) "雪l %F9=P檎q 扱04r3jx 4苫tEt$OB_怪{!程{P$';R!d紀>}JY BR鷹 c!7@!VH吽\魄餓S懲_+N$LN 2Flr5Y`9{W%teA 古+sL6L8LJCOI'#莓乳|x奴r1+s嫌:僻st(EnN@K占H\#l拏i\x?Oe2! *x?u癬y袤[捉Hg?}髯w|黜_<{驂?授酲柤?xV )瞼+@i+9)>━c拑BAn2讙悴8uG>JeV3-e0u線),G+G]RnV:KP EcA bad1K1XJm2迭'O輊欸O^RP+矧1(D9童rT(Q(d|ZC彈{/\W6Ey w2EE珸E) 楴 LA.l9K7SJ7jd3-XM_q4>8靡鐓gZ~0Ux+c(*F.x舍U%BRZ.t飫o$V閖Xs\sA(9jC寓~貸陏|sb|W'@.J^~漆7=qb?纏wp味佇_.}8黷辣理[sj]忰春澑 市什<3v,|y"晒錘W!{ 涸3vibwO,{^*/炮畜據Q骨p~>w_tL<骨醉*+9弟鷲{徇J]K燵iu賻H# +蚶楳醇oI7CJ US*_s^u２KY奇*X彈為恟o筒{K韭9Ap銓#5 [i蟄;QB拇J5!NJhU:qRb+pCG繼m&],Ae0搶:霤(/1Mv&0`JY鉤dwm埔d)iZ6 i]r3Yw'浜拌xc%剴JA$ﾏuy&t&/Lf@})KU'-Q鄂i+I{籃o$善…採(u6"I+P椨ｖaJVAJ績c:r4SX_e杵嫺rM9j9QaL|*!髦ku>_TIK|B弔}/炮}荀稷 莞-VT概LTF{Dm 悌焦dC][=JL+X[`uWq$K直lc&a%a潼{f福ゥ粡(/30>ゝ@W1E瞑U5/HIｓ`Kk譽'ExaVjP4) }@,o諞MFQ爆亳:_e,Z_螂 襴c'微)>UV5,NrK/N{珂!T%vJ呰;(蟠棣@DD箚 ,冠':&m~6_ OGHHN>%5t敵dUi*jQ5 z脂轢AT濮q~1vvpg J-bSO耳s>hqFM0δ 拜M泰 [-$ L6 v%e.wiv箋El6+(9,鞦-Y概婬R(5戯4Q彩1g-"ｙ$s]$9s)aUK]dyo5r旺,鑛Xc-∵\IEq -屏l[;O FQ/M毘03耆Z夂h!RB)0:[qＣ@s*0e[茖8pR)〕廴 鯡,u扠`ylh{t葷I(#i&C-O損棕<*i1:#!mVA瀧Ej[格$EVJ蔓X$*:$;~P受r2#5骰/YE挧+=Kk)vUclW犇^蚊oQT9}5 M-a88Mp[Z 7m) w_|率p[&%折]TM'Y qG@i]E:H壊ks.4処qx/VFM\血\U犇f/旦\竍XBXKVF犇f*#%損l 5葢mpXWgT歳pZqh硫駄J 湯R83C"AK慝c5t(liT 捜)`iGT!腰{Hc}]qi{P]lPB椨孟U 緑5F軒d\jlZ恙rJ焉}mwen\v&1XlS液蟇\uLS$ZJ喇$平(T舟;2M-_$8uU吟罐Vl肺IpOgcljL%#edvF}%3fkGJ59o9t_8CBm>"ec迫]EOlo=懌[/0^k\@J-k kI(J萸X1dqB 羲zmmWn>Y4E2&Ez樣躯 Q,5}血W\ }"Ww仟Asi`%k資5flhC"z ,*MNA= UPuF%ばi5 柤\杠JaYy}Ｒ:痛UkV@逶X yvA @OS`2朖H免U]5SZtvDp納{fPf°e)19&]@"銖C^椡& f瘟4? n=樓叺Р}S洟E亂泪,c{##\hnX3skM$茫sＭ! a凜 _ "池5OJzEZ@S#ceE.\\KП野鰰R\ W騨Dz歪X. \Ln|e!D_w z.15 w4KU９k~sD躙L<藍%wi^Ρ9項tz.)叛3Z2XL~i薑 機,`MF0L)ClZ鴟7:=,!t*:胄NPB@Nx@QZ>gG?3z柏煎&(U獄ASxI竄E遘5%披土'憐>ug6K_)Ty&k?`hD&爵kd惷 %2-zYvB嶼5auЬzZz(%徭5詫絋 犂5H/O3oB0鉢X1絶L9E芻0贖NRxI1x 4NRъ}A6j I霪 b4aQ劈x鄰dq~)dJ>$:JC"> IW板kX画$\S`B[0.n HBW>$p#a穏}HJ0o.RNV[)薄tP д,,c5-a 殿規Yヨf瓔@r ~G屎NfBVD"*A)鰲LR^XL)J(pQeG S N)DB閘F_%~L伺y1:(w爽部,2(E$ ]\DP U!XK<&Jw 9Z`jF)6~J1DA(R?kQ.X8x:tJ/?rlY頻L)|b,D 2O=7O"k\穩:9QH孛伎!箙eツNG招CG7H(u--%N招JB,D.pG p}Bp3咾E3SmiX#&迯G|=%fR 祁 [GG#D歌BG：苡^i=駢q?B~蕈分eM)yR>N"O)RxsI5A幵I[7.$Md=Zmrs勘凌ogw]=+Y唔毅ZC2J OJ然&芽>+"'櫛T{_&~肥tat殕K\f#僧Yr从1 ;XA苫x稘;g%狐髱@ ]-|T7(埼曜 6 cwtJa/qA甦*EM^-f)p6A $糶cG(瓠'P鴇+咄L籀d$9O如VQAg悒g$AIL痺KQ粒M/&Kup=T{zCr4!^q:宣oA9_5%X}}o;(g`>Ｎ^\q蝌瓮_FWrHoLc-`.1`y Jrd"'H(b7.呆 reR*儷(<+-oG&oKPGV椨y8P1縒kHn照抑I碪7;}R0G衛ZVg<V]Sx(h9Nζ/i |X qwz+o$LjpW`)rX汳f_灼∋y┏X:=o[剩|U"7Bi岼&G飮,μ麩F66d1卓KdmSJ@) VJG絡:aW'@UQ巍U）M斡XDX6L,m歙Q姆"藩BIK }<戝`-#mfO?eKgdCJc2 qy<簡焉 pDnK/IBj |榲o-u5kK}0KK囚Vc2箍{残wL  /"o'5p!x影4z.侫C蘇`秣R^)Pdzuhq%+$D|r( 瓔o?q9Sh;TocR>)!饌鴇N皎g垠cJE5t:譱憺^M\OJf04M![?困OhKEY:g!/oorgC{ O rGG0~gE%├!@{  )NJ1gC- QCЖ叩l\K}C[p:芹PIvh$;4奈xh$<<2r~c4CT詞=[姐柵$s@ }4D<曙PjVpuCw,2pDFQO剃\'G貮%9[2pG4 D4>巫R eIl(a廷|LH3j芯u 1g斉Z/_~D9cHI9ｴ59窟t堽櫨:AjK惓V'蒿1)EcQ?.@7C耕}(D >N療 oFOEJ崚醜 0!}Pq礼XW. f&8M%)d蒻u\寤BI0慎Bk8C>zeY%邀)&}NabB丗`Zc騨VJyR途K#K茖=mOR?$!hE) 尊_,"Rz2}I8AQJ鋭^FNP_錠荀QL0耀RqR椏忌Tk=odA/duSJ8 p 弊,|hL6v尚痳K絹M閹K40觜@e08囘(F"2v+P Q,p)/沿`}OZA靄.v M家A)o睚qaa擴_盞p4bM %^叢VT.+棟烙U4 {$勉p%\秦_瞰o X~+)\傳M&~[;yJb注4=ndRGgoo_}J[X8]i\槲_rxB=T wrjx -#P蛤R #p蜻拱R d盜,H(nY\ MeYWc)+J"+S爭稀x壷K9N" 7HdQ{%N稱.x} >氾TZ dF紿-(fsl$C9讃#^{陶x]dal0lPu6l0{fS+賦 s4 /3z［qsBp.N/JO0&P彗;|P@砠xM2符H2QR \J聿Z}莎JuB]rN軆;,k 巒柵j*EQ<4YTpY[A《[Pl]/_RaLEV%k4sNbT/X9JlP壊 6(:y0ej禿 !edj,Zg.N,Rx64BFa杷B[(袂$D珮6H席h= bR"唄RHRN箘NNbSuRaUT[x亅B箙γ0c1Ew殴t md7$VJb_xPGI.$q$R灰5( 咼W 猊0r5(KrXBm)jwGY6/)d{O'鱧梹#w愎瑶=,咬鱚圈/鷏H]yu~H"e秣1QhB処p妬 $h%!K5.`B"商y ,1E=仮vR蜉m{[@dяT >Jo\*(lBc]"k神 'om [R|=/獺U6x22F 癜芬!L晃 CqV!e?%~t6k)v-4lL> 膣R |0m>j%塢I~R=\懆蔔z[U%q&U!逞I9U=~oG剃叭~ＡR柁崙(w.*,8 j&"%!"諭CMH踈[b$X$Cz *R@u筺r髭 S陪u涙"惇5tHs7"Ee瀟0Art蕷.1yp畔羸跨599'3: 有e^-_庚Ap=St<_#酸  ho|贄YЧQ,X鮟4W@4b\2k%u眸km)溺mK>uW(E>m`!Ba謬怨h[M隨S*$住9(o篩|-bc跚0," 愕$3ZDj韵&y^\Ut|j"s5|3XAT+,V趁X5 '3F ajE:5~n[)]8r\ zn1冱恂楕IIDS}_&F (l9#3RQb3墓e E4+|2dF8B|tI$ 4艨b- XW,*"9z[F*5,ヰh]鏑Yxd湿t@]HC鍾c朶=q妝66觜*-`R| kLC2a蔓Et\ 鼠`,^fX)r*ゝ\8*feZｒ)k)!;ХuZ,iK<iYDU睚/彭/瑶3v[Nh@\[Z9]/3筋B\q f'?%84yh!&` ＼L#L!t4F以K|t`齋Oj蠡j# J7-{2>Waq-w=nHk)ガl槨鮠(rd*'H硼} 鍛>}r=M$>$GZ契('zIf'C% cL畔妛Eu/[uz桴6:Y]rKAT竺也 }N3b*fZ羃UNbwJ磔]zeRF||tV幵抄^lkS漉蛻a8Z透Vs埆┣y蹠Qr! :0棡U)4{hQ粍X膿j堙Wp*∨RTD謄.S堙糢$_!脚(Q羆&aV!B!F*XWg2y'c菫]簟K;haLz{Q|B}廉qtyx鑾"}w{%%vP.y>hp衵C):jPQ3lhnk&Εcux!@0iiSD=+A,NJ槍q~[4i ?-B基οjV8/Sszs n烹磅9XEJ[Vn餽且粽BE8J1G邂檪^橡MNk{ ]Bju蚯x+\9!3臻lujL幺i<'罍乕`嬌 qF5罐7^孱fs_Ae韜h比n犲mAv'促S)c{I&9V%NP税依 XK仂D!il. [V9SbqaWdMXEu.[Rx6ZkFづDpZ$~鰥0NSｳ艸陣!輦S@諫迢啌膀5nP4傴`jD+旡(7(齧栩 87黹^==H#I BH既izq祁*踴K1 $&c"'5qｱ<1^ GdU#KQjmk Gr, 黽m摺A鳥c$遽eqqq&1)]4,i坎套-з%貝SUYK 嫁(Y9 D8r-. 砒%Q.E}椣7MGぺ鹿蜍1@塋6GVmia顴k廴w`*癰\距p涅E9Km搖9簧0燎Rerz|zu\(沓Y朸?d轜v隼@nA%d3{sw黷 JfdC 獺[%釐K@0ML}!Ｄqk宿Q escz蜘#){@oP6灸m瓢9oM項9f忙C祀e$ `f誼l?#BZQC`T?Z)!l+寳jQ'x:j惆A3維tP薯筧Q讀aVVZv瓦q6 i3EUP)生-6(jOp#=^L3+'+ト\cオ蟶+UT\ZE#績V#>{5,sN飩/% 0&q M 郛錵j東BG6`)蠶MF|Y]&洩芬_hyn&zl5tW0k\$q犖J3DD0;2~: 届63dX1唱芬fB芬Q蠑TD39#r鶆lQ|W鏘B踝H惟H膈Ce｢修PBt鼕縒o[; Bf9鋏{9始p =+%{夐/庵Wj*掻rPSA8- 9B(n蘚)HqZYgYx5彦RIfN-U.Q爻3ψ ,.'N,<$.3)Al封斎J劵fxN@&\I2b貊>b\ZKG+9/= #!炉.4}N崔T廸a.誚0.快#**)m稿Sw!2_2^*`鉈%Nn銕烋<ww謫t埜}`rdaN`-裾蚯鈑W7慈L='=楙<}沙o@wrY椙|B怫о沂甚O鉞B7|h/j 著纃縹cyo Y嬖lpQ;0Qh亅Og禿`~[GK1@Z[I+Dzij惆B + N蓮 c<渣篩昭Y=/w酲%([ X Bi'ZL武4[+#修Z{u)伊唆In挿母糂Ｐ5\e鯵;\Q堽 B鯵*eH.V=礒UNy,淤凋+偵jz APiZ)AV|=a97m妝7ト飫\鏡W+rsZ ](z帰%[dm飫漫-'*匯=w+z*z",曹;< O5*B/dN觴KP,Vdy&)d{w4/Sh即声尸l edM`h妊yNVjY著KLI>&l;撼WuF"8NzrNNMNv*2-s6 )!h/byUBk{=pK}26謦Gk_^7gSLJ描z+A#r>V循WS F楮饅/GQWjCy r.A339n y矯<6(!.WY困;[鹸b史4d`hUp.@|c;&Iqt W~?* ps O[lQ舐BO鞐儡td<a ,O1[wyH:(xA'lCgzx態鱧袞，綛L耳 _N\韆p_\Mzg&Ft/ru|Aぴ9ib+Xw;//濬JQj礒艤~4rG竭震dWzн6*L濘5L(g彊湮*4^C\"r%ZEou. ^h>.qHZm)X鉾鰊Ku.dl\53N歳ymsu砕!i1於sYZ50YX3z=闢nNm 檀嘔s c 奸p8r_zdq FR夕mU乳 陶\Cduy場G8oQ"jJJQ r 貯}H\鉅x`D銚Rd)A QjL 飮(>oA唳$YL5%YJ鷆x%9*臉%2s=ｪ<2gzS9霽UOri5<;b2%1nVNe逃I.\.M閥AA7B7V/WD麟‥L0p6|rプ+/糘QWI iKm悩K:!Cl仏I5KIY謫脇*5輪ka0閣R5逞T-x^?[ X0q!d凧9T!罸91o^L?y衙擬lpz8冂oT衒uE5%(蕪^4 悖扞1B弟-dl-(#%J)nR\9U嬲,袍k|ua(Pp&g^#9MDC'(x菘~n$"j蟹盂MJ\|j+]F穹2[lEJ]QPj%phAC\. 巷.Am鸛Ov鵠S\]z!Q麿精\GGL fS`S_L~末1訖rpK!x神*z琲 57o'oKd異a楫5幡`R]ft\~yB}p擁9`+mXKFB`<1uO! $%.1燕[冽Od挨ゼNN0{ e\x* 鵲Pj  S\t/>jTDB"3'2(2微(YOVf轉巧]雍4諭S\,型l;Js卜A X8'1H VJsLVp6-嗹謹9InQOrIun9ﾁ罟D疫G]K愬][@喉c曄er蜆Q_j|hCa 絆yHc%+K,擲&GIA. -T6q碼鷂石.6>◆$^臧(h(E匱$勁uX)Q }虻肚裔& s>H榔NkP8j)x瓱鉤bA慵5m2 gVYsI.v2X" "S├leZy=キ(lXJ羣9 VR]F9vc*ShP?J> 親lIt孱d 8隼o:-TpIC.=グ#h Y/└LOs挽(.K{7\C潯弩_MO#秩! A薦Ze#2z$}kf |>叨粫>BY*b梶T苛-h39P B4s q03%S 突毎5S q\;lr T W@'9Z!yNグV#)y/wQ楷m&5)x蹣|!=`?O+9isR ecrP,g!*E0J埃N,彜1;抹寫sllP\ヰDND?泉戦Ow!5JmJQ犹J'0v7鰥V, s'/bdn?)]z5{ g0$Rci洌Y'H@ 琺棗QeN8)肇d*D g+S _椰## ,L!g膃ZF_テ2WkT2Vrh\=f綢悳 ^鉾#z:岾踊Xf鰥2@蜍&％f^FQ$ENi6f^JHr1LK!!9I棯ZQs$/堵vm.Y渥黠m:,[k:廂(亀弌肓空 譁a4k= G&q8R0uXf&US~OAe5e:48l*栖州\2aST0m 街0UWR,鏗3w楔|'!W疹gNo^ m痃于=~  竭Cx)穡薩v: Ota5Fm東費EE$`zK"%JE9壮B3N0P瓣08X#蜥凾*豪L略[\},BC糠n嚮e< ou鷙$g\)88\4癜[{ q慨: !:Y&追\?8(DRR加w倍 |犀2HV T杳槧Z#:3A`yIx.$朱$8$1麒E<ヾ佝 K|z qZ"4脹o8vwH2fs張5Q囈r蹈箘C]REcrN虻40>?BxR !]4#2c讖: & A]SgA d-vo穿餘+Cjυ嬢H2&+'鴾妖誡z叺~u$B0!/*=0+zw祢t?hc?>n?bX3m>!C!;e-pk[s|'e搴3w"\|縞Kr14{z.O愃哭[wJV[作,386RMr艀O8kC杆CeD'/V+bH/d奔4)S%i檣fBGk<6-l6%:t.#Vgz0-(z哇3Ｐaq9; "]^炉5)$avddd$」Qf4acXPQ)bel5遲e襦)_廼( `ty]A&O3g1.K.\ψpce:BW d=峙 Q)2g>aJFfQ97$(Ub fXr装mei4ruy6C[]z4y籵塒Yzl9+fb,G$`S輟f,G|Q0u禪.4nJ^pv霏<+0^3?霏問3q9G謌$^59Eh2撤廟.Iph禮O 欠`くo|s>#+%勝W7綽hVs$:OV臣qm#;:[欅e:NZC;惡6; NxgZYHNy$mSF}aQdcK[DZ鬋CRK庵D#l氏f6wujtDn鷓fk>業9bu8ピ眞Е>c`獲;gg泛\KZ 濛:;I(3J:zq!qN|4>P搾-?/"ﾄaK2%$]!Ghz0 a)NeZh z遇i痊r:(yGh6)raзlJJzlrHlDR肪=75 驫壁Vw9bvA}ｸ+=n>0"iT餾v7#+]Ii6L*(%&vLBh~~TBo_-J閏c^ \N >疥cらfjT=Fn g.q訝睿?皰2綺妁某 6"GU汰9楙5)e4P`d_&UI6^cr=f=H驛1 r顳7d框M o#|>rdq;o枝9濶C'v_QE$鞣Jo87臈hB 陵 -妝!z枝2$頬K鯑ρー[ O{9nO褊從e4鍄R+j`VV=嫩{"{@sFqcSCW重厚泛m彬% S陋捫QKn;挌Q&麈FQ^;;Qx謡zUzgD考$Yk C彡J舊+Nq笹2qG努2*v.jp:椎QBU換+OR哇2t篌窒DgDW'\盞 <痂从|麕?=亳WBH9z菖0["y荊敵m#.F|xZ塹F參d F-!FLR黙惓o竓>RV/Yde46lv.I2W\@XJyI6yd>o\MF$&BK1FS螻惡"[(yAD z<耒A'Ai蘗$$才,6 u_3p`?%cR|$0kNfL.f?%tS#C軍 kp2r%r佛燵81h7?SもFM(論}]ZW3!$k俄PGR6Ds{布Sf@蕾Fqリdm造;(♭r梟FUP4ChGeね{GZgT-蓑f椹KJ猛'-隨%*W碆咯F`恤慙煮иE~n率/jum-a,)哲紜)}\u{.|卒G&蹟#IR!鱸2U5ΤCcCV:夭t邱>4輛LX$q*唹D俣&D耙 x?H卮YWKd}羈7cgk;CB8~PWr} M>p(lw*C沖Dr!&惚Z梅斤f#`ロSrxpj.軛Krq1歌*_鱠p ;唖+e"< 3隨/Yc窪"g,瘰 :EKS=PR T評j_q'$]'b}'坡s瘡2[op[7R蟯` 1s^N AJ\r寃五M嘆0V`Q.gjD鎚jO|ey d啼K[Q"h\cJBh6詞f7浄(=bb*?#h>g!琅G^ 4郵胴'$\ .Vpx% 諛諧$弔車|XyG3m額>\f-E E9Dh-.xS8R4Vu ~局n嶋("KT(Mkh砌mqu偽]X6鏤D-布zP _L8"yjedL?D＼v僅"m 9P揶igk^履5<OF上JDk he擺[刪bCc鰹昭 &)$}'x.[*e 珥OFG6N杯逓I0臆^MR:(\)~娩MVopZ瞽[G魃2AuZvP3緇B~L4 4m {_biLs 齎@塋d|1)0FFH~P.慳 @)E0O毎 C 6uOs0]&(ｭQ,Msi, ko暎w^h54UEo\MLs~*f:a-紺#鏃認)uvS/E鯀G俄jb?o 珞Nx沛d黶X~_椙9:隨oN*鏈NyT廛>03`澪1W^壬艤wts'yj{~xN央NzLdl術漲僕蝕t\'KihN?靂ぉB @~1~@|憺TD2P~^{硅靂崘怐U憺ps ^埋爽LVF5gkJ感Ncqz錨杳Un抑rデ杷4漏7蛍{A:w }'遑-Au5符J;J虧}N否2N\5{BM魅椰).UlT[ 个\kQ\\R]嶌辟 敲RSVu> ズ6欖&HEH哦>~/_w\C酒b櫃I/鷽受t2激慫|>DJ1ri樶?凵殆帯Fd卑 ,q4#{MFevFx =yB!G%RlQ,)H!MkQ蝣鷆 !!mqFMS-*IIZ 鐓596L}W^c~D<幀jX温.m =67o/W2$q6H7糂8bWP'#h4/b蚋Уp+}T 当Qg}祷^''C李≫\VL' JZ燒 pVHgQjR3]lB 39,qq%kl[%穢%I\s~玩ZW5}YY\xB r :束QSjn5愧MMJP/v+⇔&g,;#R&J9@s%VZv+g屬/T,J-Ae(9;'oB)I_;摸(簾e 裄Ow%_{:h+m..RMWgTZ墅})]FZ;^|櫚塞6TwQt.UF&茱{ 5!d3X6Ol]7]徑iTc9(95wf譽4褒R煢^|WJEg]2)n├.=4%驢e@8OP 3Gy-HOE]G5qW/_%3*I(Hp?z勦璋 u8e%lz'q%|[忘NK/e餉RCW颯U|)QP駿h墜*w濬w1蜊1QJ]sTF2bK戎j廝j療(L(LH)L畔X2!X2!kH)P9m碧賄6eCr袂G#G3O yQd┿:鍠嬖@#昧\pljX3緡[V9p窯#$uBJa#i岶M=∪札&Bd$7`e-\5后S0黒寇t&d-?Ay81BnQ8徐XliI56.A澤b-螯a慵3;1]TxY_kB 4-塾6怱-kxN濛Dr}S 2圃c壽聰o}籐|鴉劾~98浙/uvム2kI)b3蛞Agz, _$2(Y6v36EdR?' H 9V !/T|m.V(zTR|,%t 倒R-糴颶]5o~@>,7JZX逧\_B+'.y[M-諤B&TTHSPH鴾&\涵{sU蓬M06O Xb_逮j#) CVqX6 [(!@+&E嗄m^l%'拌A5慾+,i浸NF贈%2)I;d2I隱6e庁4芬 m.彰gJ d.G0|kO袮f gmGhEL嚢p`:\9 "S(eZ'e决hv-QJjx蓬E糢91{+闢噺fE倥h慟廢\ヌ#B"tl")p ﾒl\/# #QPDざ3_瞭SuJIbれh^JN扱50 F7(x~qUde=EIci." <叟x鴕I奧誡x#w"ﾃ論殀l6漱x悉9Ds!了b//^roOvW*%{遷|sfFP妣#a^赧剥}聯殍w癬b鴪綸O廡 G]#~sc嫌yMN鶏"#7k&"{}-l_dbRB死 Oqb鐸砿 .mJ握_<r\\_.OWz吾壼!  蛤 %:QGD_MUI勵%齊j_I8j'瓦采y淘Xg)y%>RF葭-R6綿_'+O湶7KE砿!GB||撥N*;jgemzK)F卍9`mg怦維濃'sB?Jc允5G[%о3L彁嚔G,測L/Br?=Z尸逡ia浮懋8,J (篤魚zKv?iP4a沃qX筺l貨K隨Xh*7(尺ABy?櫁f懐y覯+H]D.([hN 362<麁哉硼}殤嫩=xuplｆV]l{d69DnG fR/K:cYP隸訃燗9pEM@08/&Y坿Rt(K<2EY"r諄foU艪蘿Ф亞娚煬5X獄E-j.DzW忻l~iyU|vJL9t*杞&" +%拶HcH2 gK|脈P()F0'8兌/F冤wU.< EH觜閼w鑿:拘L艨b\Fy4Lq=4NN砦餤聹*v.z聴6R気l v悴g(PDU在?sK)vN9j[ψP豼デ淺樗.&花B]/潭足E/唖NZd刈-*!L,9Eb1hY=2DΡ簪LTV\Wy e6G'XP0.V?苑3f*e0f厥 !32jT8*O^J楪?*xG鯨VV)j<)aVV|E&JM( ~poa忤s nG^=`69IB%g ;%3J牝Q%%4BH0%鹽;/f?;８1&P~席5f2&f迂甘{A^ZuFYDF_D辺1YB0/%qUkw Ql>H侵6*WZZ(ATq|Jｼxpyy(A;稜B f^Qμ A[)=贇5房Ib@|<獏9]$`ByXvfv(z祕鰈 1=1C<>k+Ka+tgJH1Aq(c+Qt7._謄+s拱e|  z 鰰>惘 =:Zk&Aょ8:=:"X鐺@\)k'L弾EΝ acAXp/$OCX RG>5`7〕簓w蜻'h8咢怨?牲0jK謔lDyH$B.PQ\0kR)=⊂@I忖\-hsP燿=Q`u.v啅D$\,jzJ'盻 BC]癆@ `e0=%H7/d[VoKlA@zYp"載q79Ztf`f瑠m星CFc %Vpb\HB9yj2di;zL禾 )7Ih至6：氣d赱F=< '4"BhN)q桃^^_]昇9醜v黽pC/_^弱眼璞-m7W狹~"wm q則三u2^KFH\皚KF4ピ_Xs7X3[參obkQSqGFXjbWplXA曼UJ学擱R{}8#r!uW&Cbk#JI6BQB晁0xjri晁Pr1`3B0@i|rG#%'豼 燦5++ jk淤鵤QX;d1 M旛XJC梨h後-m瀾[Q磯H成/^[Ms犯9H% 4夊GK7k)o[.jA -'W聘昌[1h{mX='#懆~BX=2VD+痞蜊OoYnT|=azh1ルH蔭ひ富翹嘶縻銷jb@iT-児閂~3]wss^zvw~E~#4LnN//#j=;o8sYnX?K?|YL盈=-\!nT|+x<\pSc^濘`坊嘴IaG|oBz1I/^ﾝ需阨統;w粳 蹤6D?}C-3/<>viﾜ執eW狭|Piy闘ki-wsk:勹6nQ襄膺着裼.^褪Kg3#槃;{LuL揣鴿TO約|^>券?z.tW營暑'*v<訶0^`P.<斤Ooo_悉x迯~wn君OP.^^t髴蟒>O>柩] u.隣粕.LoNCM|?eEX|￥纃p28ij禰栓/_Z9|Qpj-e8p鍋 v_困N凅*KstBOz8r (|QJ>kbmmn2Y†`鑿rakJh5J w 6R -v=Z 1Fys/蓚-";EEX)5}J蚓?fJC) 巍0v2L2i/8,0%tE/寇irU:Pfk=M 楊擾a;dE,uS4翡13R賣`ykI'競UKw.ub"OlkZ'R<咀"{D8馗Rrmn7` 輊jv O貎"!.=$fY~^[5K^UR%{揩OXz_笳}鎖}:衆U<5貎g~m巳藐HyS喊舫"T:9轗2L(>C涓KCfu\雅c\EC襖彈1~1|>#-c啖` ^05困zKy3+グu-[纈[un6 ~螻[輅鵜ED尅|>=z>C~e$ 6&Ps(q"b)p &l"9N3ｘD1^苒T-S'髯DRa")&R`Tａ.3x]>d瓢蒿l2柧HA&3.d該>厳b}壹]. C()sGeZ].6WD標釁h<C.}]m@嶬=t吃3'n定>醸6避嘯渙~郷b捫?:J~N2JF陦傳劼f6a鼕P-~FY4<(慥寉捜b鶫cOC!憂_#Qs岨L ZGLW溺 Q J:笏y !唈MqAE|A >X5et %P<>葯+) :8(];Ep包 g*<瘡u|0I)臆W8轣‰JSq\i<雙 _sRhYD <-J u屯/>|}AvPA,8儒啌6\VnAWVs69m砧0z攘24;VJ5誣1e1fF)j1裝d$ 麌迭G"}'zP7徂YuSJ柔5l)|RR1遵d`]9 !祺o臾9tL轟KIL_>"錮9楸K鼻\~{弸#o瓔].~哥x "皰UY梁VKY妄|U舒f ,9LS)Srrx6@鯡)RpKPH@A*1I皮/,'`哩53qR- ,Po*jEKw(Q@m`|K1kfJ;;tG攸+S]j*])c8IFrhe仔04/*癶歩"|$9 茘 頂H'Rr-Az [.QTd)摯u4V <(G2y C`T_K~7@#~X)_+8-MF宋2#axNi|&j $ G>/AJzI2荻)a?e{ ~n&IDkS3ff&hmfjE) (赦I\Dc$披z Jc- XZ訣DDN殳{Z r痰IDG3(K つF,C窯a薇池.1醸羯'~OoU_}龜SzI豎 ~1 E m赳{Ty蜿K/m.o^沱^ヮf:鰥On./OD匠8?單7{-RpZk<6o裾#9ιN疵_=隼p聊ZB凝G3耗O%屎o-I7菅裨'&5?0+o(9:0[w?滯P隕h謠|KM}F",@Z7黐cd=鈩]%*{l < C~\阡榁謫*o^囎^{G#6enﾏB<容x!膂9eWCP飲P kN2C{{XF3 }NNaKX_W#A\枉\8専JNC泝y囘4fQ]Фu-Ar摎wW_蟋IP 盃hj.@魯(2fI[g薩c†{s8湲W臑=帙行語\硯o5PQe\vO_"2屹^Cs硯臠(%|uR尋Vc,Y\ HI戸wW滉廨xcv >Q＼pF\+G?Ｗ5唳^4j>w襄[L:uO孑{F及吠rL`dA*d俐Q%q5蝣書:|倨-"3b.yC`S\!h{I∇o1槿;Ps;}裝 >=|itv暁?OG3■[仔i疔E腋`=O9腋竊-.[#擦3ヘ熊W.o濕9]F4@醇5&峻2I_0夢握6J#T瀾４4B'０ 7醺lj@Qn~9; srT4o=tLQ岑拱g/%+G1i爽b寇.KN03 i[@(2!x)vd|M,v@B穴%((U<7fX5k息5 ~qQ1ERha%X` y鬟59C hC^zM+yO6$Nj?9綸[DXtQ u k*eP.9Mn毓B6+ R蹇5Aヤ)fiT5(F2m運rhZsP<-Q}xoQk`pX0RLでAVJ>  I?  wM鳩托B Z=>`"| _9“]]^HR%H2雛VC滸餬^JLEQ90E8'.隲%*`x"H&T<&%h(w" )S`Y\r`(^'C]fKu.dQ."#E列JDVOCD息EL2:Ho2 kn段憚CZΡ兆i.EZkdZE:F}PyVtR簣.: O蒸43C,5h鋸dZ糺dra-M! jMgVN痍g|i}-纔zdu*A`{N凰Va#)iXc c"\nN騁]B65E%c捐ｎ粫UF/深F#[懊-廛Z}3dl.n3%D#_#ｄ#<}&`5= N*蕋伎UB9 I^an泛}F s鯏DHN 1J:% 執IBi73RZY'u:TVJLb丼Vf M!hR;Z'Ane2D#:01yBQ9SQx.Qｐw@F[w9Kz#忰^)c%T睇司xr lrA% f5荒 粽%]@捏-pi601r(劬SPHn碎(%915rv_e蓉)容醉屍椦g7Wo7A ~"M%WLn yh霹kC0oU@鶉[Cwzl鷦猝o]麓',SグC#(S+CJcd,祟U?}7_|糢O粧r夘X敖拙*祁!Unos[渮KN甥*ahe櫟s>蜉l9+RVJ!&Nc劉普R>U89+ TC7諧99a寴Ee0鵡 0L)[ 8{kp矧煙MC宿DVOQy9/絳u扣:L57$uNrZ3b傳,QC/SM&V)=e5m雷Rx穢ElS腐&秕L縊39nB瀕JD$;Y-0"0範叱\ 佶$>"ust#az*E剛G^Jr霧F告@V:Y.絋{&_8尺+tＥ0pm>冕=0kZv.}w.匳ENe 'P@XEp黝8Kc鵐m⇔(K>E~f豹孃_MQ /ug0l垠,=r_91Ei谿t)yz8>蠍#荳m:EWR4d w8:FrN+┃12縉bnpNg^ @P"wHKRSclアt"3恭[o"g@T踏Q,( 85<箆A uo逃oJP$^N+KE砧-; nsrF毳tPDNk?J6G8$字P J;]#|：B 穎B員2Az D冢@9 Q\Y)5n4j;纖@F@\@ T$g mハme毳J>T$[等:xT卜M魃剽}円QOruqZ恬HGII疊?_執譫艢V;ﾜ鑼vl\89楯$@涼枅 ?外cK)O~[)Yd.~莱肝/o_{"m捶Df)o菅tW_p~Zg5Y誑YV貎D)b52B咄鑒1u%swyz裄莱沙p視wo. G#f)z~矣耒I.)4乕SH4['(rO+ｙ3)袙':牛{DmF延 宣 JtPhE!'z盥CD}SX,R^[CJmZXPx粘|d$o17Y1-#CRJ`橸HoくiW2~埜x涕拓苒 (唸>憫eA V[ ##1qh;R7(U]+s永蠢V mV8搴i@奨%膕羅几隧S媚O&tFn * *優臓-o1*M 8/悩崚zX康%/%sf酲4vh?厂VI:5[Y:87zwaM_碧zp /9/ zdyiKE18N訃A繁~y緬噂湲C'G玳C9~鞏 m?{S 叙~骰/雀翹=笳釋wz艚IeD m P!` /っ0L]i.斉/ZM^R"1")I)HZ擴<撹∀=Ni%畳K>御矗 P-#\5L百^喋>O}Oy鳰彪>6Db.儼)閹E,1U誘煢|體5R:o雍*鮗6/#h沂2u寝E^\MUa頤囂sgxA@H枉j $GsG ※qIiH Hy(%庫>mYNk4w"KYa&Q:wｶ篩“5nvk_i&B呰杉o76T'iA恋<"謠 '(P畭 妝.謄 XckVM+ F BexCA<<r萃槫p\~rFフ苒K _涵校g{+C8渡7枴汰hR退9^ o' {j"fE/Ti3Az贍Q$n252k競憇Cu(eU6M Lo眛~ U荘BFE7yO泌-8D&_-p{(ir痃1ZiOU襭Rp^GQ]H,H\_泉=?A|5l5PM^{8xr[(*Ny蒜QB9肇a;蚰Rg襭羞⊆@JB({P& I4芯.S2y!NQ#9E |饕[[9[!S `,瑠x9_ 皺L^羚醺F m嵶'ｵPWJYs`,泅@)洶hョ(陌顫6寿g57-QgzJ<葬 W JxhYo葢s眉bb8aヘ(啜曠@LV贐S(IZ;Rr\2SqlP8[8md簧Qa鼇BKoA<鄱B~6 :勝q7糂LWﾕ醤X%VF]R0~E!t*?9e<94RJuZo'籠-!8 蕃b4<"=^是l>柑彎左m 9D*I!,4b_\区r|$?f{H鶩sb"箔ZyN{Nl)O6`袈8EwUt|-{(V蛾is鍵f佳s~Bl逃=,）lp勠zX歯蒜qD#1 [;G =ZD@QM[k5(n桃\(双e墟3uMFq[蒙$vc0wn2-^F2紋eQ +匙?(1剴NRm%6b 三65記} Hqek庵M庵 9b8/cΩII$59必q冖qRxk$59[LaxVF!}`芥NxaP*e,7)桃rF1(nSh36畦Ykfd9#yNw哩:J->d6:#T_亦q+]gY諌MJq+(J赫MF1+RJg V:%+1nrY薔早慌勘~ 1 toN:Szt宝R^n?rrj圭/堰Uz6<%折4b]x 妝Y4Q籠互7維{YQ篌]静[[<6r^H^<-xJY霄 1fH< *迦"晏萎b 洶.謹i# 邃Zb3d P bRHR\r3& 2.迦)#l}m<錚xlu6\.ol[|2悦絃H<紺E 1-W~#;御mA/&EVぬ(T a"k2&^U缶{ _RlTLf箭3pQU5?漫$Q%0N媾E}_#c屏[箸漻('-zc{WR ]_詣#崟i\J剖z)54)@FL5)V`$ΚC<譽>~ 0af>G乳8 =c鑓争5ZBg9A<#Q7p5&k薺 Ю俸$CQx&孵bs}B惣q)h個Wr"毟3 E1 ^4u;艦(wD_sPD'A<[NE彑v^ [K ukq圧8I?:衄 遞aR慣<qEqT:T諚Hb#Xr盈u雄u/~梅釖Э:;}:x~zgfM ItUt5F^_C]L咸H2$VudWFXrrtDwj[Ｚ壅rAJ7b>:褝d蕚>2瓔&^k-KF&hW\帖;9砌42@h zHCr^|C%V?T{H徳I-CT{H `9.$xH陵;s!!9 <$s;xHrCrnQQ"頻CrxH=C<$vTiC)ご=$弭fp kS~AR$3灌A2jP$vt!qA曼 9GT 8H/k幅遉恂湎^銕NwT(h%nW5cXs%Q c褄^d# crJ决hbt私 XfCl艪 Oe \]QZwLI)8z,eod66眸'BK畆1頒~RZTB髟IbYeJﾝk0'錨｀([ ya吝戰p}- }dR``鼓T% 0*3肯 U聹鍍7ESM!(~7Y壜7Y{o~驗誌飾攻E~希9皆^郎KZ$ZSm'9舁蠧H8壼: z5d霽bJRjuz1慘(憾V2N箙[}2G剛]C]]ВgVK8P%NI|g$芯9.q_皙z芯/q捺8#%N%NIg~s]蘯z残/q\|S呎bD wIzFD割w!KRKw/qZCpJt!F C 1TtCJtvA!FC2F嬌Abu_*b@床$BQ_^/k&/容(v1p1_nr旨(c灼()o.8.pS4:e1LnO9Jq+筐'J 7'KeP..?1wL卅d>h竏b$IfPRD(FEDIG方O| 'ipZ\$'T%Qo%p R.AJK寃'X))\劑Od kp $V.AO}竏Rru'bb鴻vtIu`{槓K2罠4 NHRv!nA/?N"i莇5畧(霓z袈5/C素k)lerA)l皀VEjsoN!ChBZd楷r訶Jp[ynORF Dd'!K課Ug)bh6Dl患%2?bR漫-A. Cp$p8II8/ 船(グ鶴 E-hUI+GIIIa8vo3~酲| eOb'q(統I@ $V日Ib$^FI2?q?襞$Fr/e$G'qF'1蛔篝H$ 'Q$蒄_'入$8'機$Ｉ$*o'ROR?Ka$Fr/e$^放I~?8ad1Or`$QaOO#苙$UIH OEpG-.74輯,P嫗UbQ[B倉Tk+s/盜{"#嬉Eksq6i6OlzX:Hzd7帛f {opZi3@I$>-GBI>=bｖ喪xH:]。u[3{q坑|E^Wdj<(gB掃>)WV殯;j 5nV*河摸UKT嶮 $刷0晢AN~etoGa]Q Jb))u)_2[da]uYn)uu畢X尊尊儉XN屋.淆VQ.覈c( )Yyb QdD(|IBR%GXZ洵XD炭P&XV,E+ V,m.X雲XXN2+ XZ}bXＤ82３eb)exo覩yW0W[閲OL舩}_臀Za]Fz#He詮厳\ rw6{w:by)5No國Jkb勍隲^煩2\`r=_貊Yヨ抑Iho$bqeomi{計\fV,+cO^X薙V,Y鎭Jq+街Z|'Ko.Z1Z卯?;IX.[LU凋覈顳望U|ジ bMJ颶|K)f2+$bYlN=隍"褸*deJMj_w冶6E.廟KJylZ (Muz~ ♯ %Gz疑NG1|e綰 Eby\4y甓hE s- ^ v:縹3Ρ`蒭t^r夕eEPvZe"m紡b齏m3.di$禰!<"'VI)E性#u蹤羂d,b 敢`Dw >U教h 晝-(T \"IKE9oo仰{枢8.w W\nリHJ3G+襪┏H停鶯Q\D.isQa|vFX, }P^0xG~y'T}^@;IRxa%3d都,a\KY3/u3d9"況Mq槿濔}潰*Q輝WR*I志:6鴈K> B?SpＱ蓮%Zst(椁rzf+ ZG Q$$!D!9 vAcATRA4 &: 杳C狸\/"aJA"抔0h 先+9YQ R$V bBiR.>m4th X9PK 1后g ^J"jhR曼唹vM ':隍B爐Co("oA 鞴-Av.s >掛TC: x%(9蔦[1<)$L 炎`GHVaZ8l剃SPlu層lNx勃c"史8ym(ｂ)&'~ {I69h[%0Jn嬰腺~註n黝&e8G G;gC圏 1Y績)GMH7:#IJJ8od澆H半Nf+Hb%7,J(YTt墨.>RVe肘<鶴鷭Qf^PqEy[AB@3-h%胴綯Lq*G湮!d鯨i,6@辟`-Vj>0"&X*Y)X'`7/坦.9p瓜L\rrp.8{2!J qu橋n\J8UC范l班県<He$KK!'nFFi 2!舜2T$樂]g儒N=-b厂9 !鳩竚葮|Hk`D %0[`@Q.a8C*A2)掫Gi sBnZ団麝XHF2審QzDP玉Q3!wU3t14E5z cX=鵬p鑪~79q9~,JZ勃0,%Yk6-_nX/?^yZSj4QwD&_)ivfq<條j$釦g呪jS,乙冫去沌締,D!fq,:i1･籥|@9rKQ i5N!AP妨亳mP)n2jt.3j/7#oDR}f閔業i;5kq臘鍍'цp2獄["v~k淌1xarY8,_)Cz6>+\l dO櫓*k'>$B>xp{鑓O&$QRt*{(zE烋|u屑Sx~s踊税;}貯:E枠a {旨?z豺%gSNP>鈩oI帯朷鏡m癬_枉k??什;Q9)Ξ閘]^NW+cXOx!pFj|{x?毬K霎M(% :筑-fcOx欠nrv-Va"k?{~~鶯{s!QA)]i'Z}6<絹mN哦r凌9D贅/%8>深x*qp1p :/F嵙-a)v{r"濬}J*G;室皷BCk[NL棗[L8BCJ&欟(eO娘裾癧錮j艘q5&牆ir:錠7恢o瀑5DJHFY$8XR"72Q~~@{3減7H('s.8浣_|曽'煥 儀>1h渟B'聰ty財澹?e菎褶 ;=@抖=#\^鶸By遡}>磴Q~冬m}%節9l o<^vJ i5 al,奎zY劫fq芙壗滂W+ZrTiC先舞C1V#4秣qF抒#NVノ公 Rg鯣>湫Q7YKQQ4mg(4s[0ma盧s禽逞%Y9t亀t迹ULbR/ _)6>lH"慱j頒.７c錬CtfwBeMg緜拑5 "瀘vy秣`.UA瓧 P欧Z-3%疫2R%#XW趣<<<λmK樣[o_-橦銀6-_諛x)2{aA,ヽ黙Xs) 5su-T專~EG5I~O9q PWf6q,DpcK2Pw鏃%eR;eu叛J`%"翌~掟L(昃 'vdu<[w%[3!]ENWaXc:I厶V咎y"Gl:S%%踉rtDe+D(o鷲9筵\xt荷)EnLAVgL#梟$ c2&{J命dD3"f-Q }"(汪銭c癨oVs痩N)2k;(寉儚樓)[%(q@QC9吶E1H痔H檗p潘a黝鍛O7ogL/F褪nFK+`+b9?s=J,凪 Zrs/F}" p- R'c'%\h隰qyc8zhWJVq規Fi鯰MFas0HbNN/dMB 媒jmMKc^Vg87〃C恂#t;-J|3r]xob[^Qn鼓G隧1$GcY`Ｈ黜\5)ma]9{P=G∽%誡[ [zτ3呆字惓kV_\/fr5MdC*銜nqF笛O"Ul`!饑h]1Jv節79Y tb愛x珸 >6n"`サ卿^xkL匝pu!>1di卿r狡`pU熹孚[/p3!$ax]ZUZ",j ha"&FFzL躯臨瀝iX_a乢げJ<\#咯T%)ナ―}xs瑳')B;科67俺G侶#;蛯1J,d!c}8V ^y甑9!}8C(j"{MTグ(#Q2崔q畸 \'Q-p"愃!2N@今ヮr@V|> #鋪~*~嬉*0帑症vk (kL'J|4ry2g%y)W #甄oxnZ>8z k蓚~>瀟9]T'醪凝ycs褶佛珿Ph>frH涕ExwZ57rC)3G-A_bA.+k蔬Wi6c;flП4v>.i鮒鬩$MC+=t-<MeKL,‥┰~RsI.Tljク eD轉裃#超nG芙MR楷s ~p`鏖?z]yXU,BY;N#(v/ZF勸Rdf倅FYn:ャ衍\z7}'&"VG簍5H@n 4甜湛DK.K$,K┐c0達 疉5秕so%進<苧肋x7O蒸摎_瓶?径袢Q`2D_/$|!hRI!/JQ潮A+@n%`"+uEqI易$'H>A碪u[6揉1!Q晨齏>4賓9<釆 秒%y7a).KvX哦" U遘GE~\%B'/UuvkZIl2.LV**y[)IA芟$_{9CpF!Z,俔慮E aS NHz/拐1_4N|i|~讖o~孥OxwF-r孰蓊蚌鎧[娩顏D<T毯聯MCO1I┻_]?舁-y2=蠹 ;集N良辣晃嵋,R輯>W D>xNОl I鰲?!LP腑_Sj/zy+T~>o"25YM] Ywb"埃V~C髦羞鱚?|'z\c=yi6c_ *|cA:dsfK$/諞楴s7=k7*漉[齪r|z `Д韈An:Zf@{A2Z0L┠塙 @愚5$.'4Y帳鼕#戴$]瞬Ku[O 提OX.dA![i7s _}黎 蛉*<Y柢O8餾*判I d洙AHKIDx[`@呻t KJF戊P)#7^x$`!0"Xし (HYVkB4[埋 9aj)y'EsH({2嵳Ra} \veTM鮎jFh J]*6I)Z蔦{kU 4¶#")40A咎5fS`}箏_>鯢~年&+蘯>y=拏V\疱?|s}/^)97IJ)$依J 76 PnK2〈X 懋z萠(ft%eのc1sZI輸*[-v8h兼3aVs&Tf$9KU%U]綬zvS殀洋H胞g7Bn.D彝檜!>⊥b;$][[HNg蛍, げMt-i梺)鞏]os/a!X)<劇/!%\I #9Q具听意(O茸齣s;&[F,+n IzUI:徂b謫u題rGq%dTRN6F6k 17葎d''BHBBJ.$ gpCeD9O^@3&)r冨0ZJVJ.]KTof繙qmE9d3#AI6Ｆ哂.$xmR)=$|J|2R)饅NILccz@奘 0Q汚<葱B]u*~Z數鬻_罨j縟wRCU^FdOk%師{f/vkL^_k3.9 mr籵I}DI` 瑠hY很y笙絆=O| 衡h^; z9!局7!羲eE3vQU->S9j3q丶F,nh!h)\o5MJ0+z#![n7neq5P ~5Z)S[c~~6+&rLS[g4KW'~a5%"5(貼＼Y,ZB皇Ekr?^@V俗N a鯣簫Rfo~4EE[kCn.柧/r 8P娵%$7簷bm瘟dUz& ^/u齲tN?m[Z 悃\?┤Vq$'m帑eiト7]G`iM覓Z唳n%v}"r縡Fl_蛞苙%朏s喩KX.^毫~物DK鈩烟滴PX現8晃合N'6QcoIt~驢窓纖栩徠2;傷栢I糴CｕХkk団?┨cDc巉} \u盾 SzqW縞3-;+H<畛<8徼)鮟土m8y攘)o 濳K82 *k]bl.fl~[訴y),收恟M懾橘%/瞋 q)wQ.$S.ぐ\喰Q-7 娯\莞廢 Y鵠tM\ 3悍淡PU-＊脯峭T縡w^KIlIxpmhtX 9!RT!}J釼盍S>e烽g苻船EP0Y[T.g-貶氤t(3>EO煢#1uF6i7F+ aXLF:dれpnVWGc>I3z@臾{n酥W~u黽耨 w讚G/wZf烟q`躓g茅8魴7駭Bn全蛯顛=x襁舐娚..<檻唄儚弟/7HM廉r敢K^O饉B賍t;<-豬wq8ty[魁Ry唏h$=猫0x\g0R:2..&6wv 捷?io数L岌.3RrF%+Zu$d寞耐螯[[ $|l 暾DN^sY%A%P2"v Vo】T劃>永絏 |n★+E.7闘Ep5Q8hpO6舶kf9Xe9Xee番XA料b-O*-DdpFz%f祠q燧p>巽W歐w坊/渊]B_ryM//'疾#\弉r_j+kY芍=?}x +=tqw鼾曷乞/竓，z(VHa虻|虻-J um>N喨濛征靦O策g{RRNS椚qFEbz]n陸b$H倖K2患]hmFCs-yf鬧KN逃/l@2F]_O4J''% 魘絹r茱 % 4P 唖 Q@舩4O c3H =/曁營椦柬Ww1GChF=|OくM^潘Q` F脉O~;P?充l涕-H憖站抬}+>7?qS愃 嗜F>印4/&L裄轉元 5~4oF笏混tmU^R:2..Mゝ$iP<鵯諂wo~%@7M綻p4pI]$(扨"むM!'@]湧o#9.0E+熕Lr sz輓(w裡$\Gvhギe7琳C (ZJ!vr5!4 x弸;qn躙TVTれ3J1JBlu掎K3FKo薙Xy1V廢傘$Ds7lLq霪 d}w3d攫.a4yo苴坑抜爐Q_芟羸a9 U細,X-;]p 夘hK馨mS^baCfD(%4O9k;!]D椥ti"\B"\PAA&(s*iYRNQuzdHm$D7W D僻m$ば$X.;n= &[B]顛AiUgh4<+巵暎!G575}鰛npm|JS 癢@扛qbP瞠v?V詑=LW蛉tN鉐9$4 )$~堀+J弗~hT綏yKN-?~Ir{除dl K4Ou:dT仗|=+NlN!堆W/?杭珥濟_~C驪講拜z觝緯mQ贅俣O~w縁Wz|秘 }t5m旗b@Z](G*&L\=ky *<'"_ ezKU跿YOuYK0蕗捜ygd:粤$o班WH`j =MB<琊>^>箚耆5<|~rTT>経"%09g6FV3jｨR忖.}$1<鮭(s瀘AuDEl%RhO1}sY枚foy訌-");pC{T"補緤|l8BE~Jmg,cth螺[uJ7~淀5瑳鯡=^{p弋x耐g瑟J７k,#" S奎]w|~歙&づ舎m鬘0{9IQM] 冪 rOsE7A/苴o需鴆7X憐4Z⊥J0ZISV.K\BG> gm)介'鏃uJA柎 YZBbX7搶q芙G#緇S 過mr \/goVe4n\J}CMy'6褒t]!9G$UO桙q柧Yo !&謄%Z芫BΗy戻8J兔D%泡7oP抓fm x戲堝汰l]p汐qF"jI紀@|=.耳 |Nx蓍霞闥|世:A塩 eH;'&Pdx Ne;F整XeR莟r 篤遒0-w)群~o9>@k9>@JPUKb\x塾優t綢GA*DCQF&;中LN=e{=@J-]瀝dP.剃繆$CZOcQ[b蹣B}Jla:he脱6F!Ph犲 0:e^S豎kC"B{ξ>R{鴉?>捫?翩'~[<%FMwe`Wv士?(M? RI赭W'幖(7NHJ% w鱗C]vm肅?}c0x_(b商 >}nMJ)O犇Ff裴b\佯>桑U4D蝦几rFE}-滿J蝎nB"J$顧ra剣%b_釁^)i愈q嚥p|hYrR'ヮ刧慄'\畏(r=gxF~(sRIH %+bc^3W39nX業X`ZQ]K旄裝AE}Lgb2R ,%Zhi 9zRk Q粽]"8>kPl$ RYfv&bC aY[|L氷藹佯jBM淤[$Br *tmVo`kF蝓"%\t瓊\Q沮ML=bN鋳鋳L;r51sNsVXIQTI#ZKoD@-aa$YeTZka% .v扼6XbEv$cRx.20劃n8T倏(葆sF%U弃EF躯*I#Q引9iB}ry澤}祉臙畸Shb2aJ ZV塘QVq0l鹵034Ｈεbtb*C>`iJ,檜lZ 叫)Y跛盜`pPl!)zA@`p+#F乘<詛@s8姐OIJ.BFeR2k6@Kzr,:j ZX/f%[週|P霈2E沃R#粐uel%s怒"VWVK袷ax$j]Gm{縉P 0 逆g{4FOv'6O5!xTaj鷹q O穹 WZf綢"轡婢`cE鰄o w(RETK河莞9o嚊gvZ]($){v|臍$@?R榧k%{ F/=DX噫wKKL礁胖~幺$A茋N]3wNf A$x0~7C8IVz(\# "n醤vsジ`7W柩bvsジ毬q珊6趾J vsct珊nn Fyk-慷C児ic=鎗\@"c9LL衞 X_"~(裼|o癸6悃 /8L8踞墳M} "{so$Lwnr(蹂嫖#n=虻<#j (親 Or= p fSvqSk<}.r棊EOLlI^g/貝|F2S}P`(K5NS碾,z%1,w[nV惨8e砲棔u$.カ3fQジgz"!(_岔Um8舁g/2з%xk&W僧蹼C]v9抒/NrΥ)M0NS(3J萋玉 Wa^^(5[IXk_＄pPsd振NZ6葷擒(pHdQR長k]'AHJ昿\|<抛:封5L~!淡nL,<"5LC47晦g朝C3:gJ懋CAhMJ(rZb8,粡q}mH1irwf殖;i.2H[耆  EG羇 B凄晒mn9Vm!g冨lJLea*~N&唱{1!,9ネ}>!|几>概}]JE偸>=&% * 4NC#7埠4,ij<晩X)/C曚1qaJ{)z<%)E)Szx4卑I'-噪f_釆 訟It&rI76@zY嵯%g吩\ Yje|Zz;0g+{ =穩>鮪3]A7}t"5+e姦y摸HdTS{'sю堕go]躑Rc霪%N/F$Hxo/^&QD哦齲0&H /%(SIK肋iu11;{74&o5萃(QQAiAuΔ\也gK&x訂U'o疚D,}(i m淘繹0*8 E--d~ Z酖剽P樋Zベ;j)9u63n';If,r蛉[指@@eD. xOR4E`:%4$-0be3HFIP<愾DP(exk5盖(>4k扼低.挽)0zpN昜茱 0O3y_鏥B9梃U9b3pゝ.寰Д跼q?8ｆ#'>{[>t>_kaKAi2WvIKS. Jr磔罠'柢{NEN畊M>`Y娯xM 栞糯醵toUL蜀j$菟2>x["ﾖX'T\na}駟MG繧s7楳X=天*85;%sm.-k鼕fl餠+#G拙}Rv 考1(|KQV9uU n(Y=2_ b$"ysQ滂まc&Ke箙EIK<]%Bz*@gLnA螢HOGS9Z$x疝Q>fO)Eu9HXtp)9 JR7什YM M$K立V18 q炉5\x fosTWg縅l| 2|)p3^F>5r3.⊥迪L&8?{~-dx8va念X%緩 /e唳D9w^魔Cd$:('iT}\}3F<}f U!$*AK5 苓.YQ gt0sKg8c駄=2b`{ J騒浮e@Re JE7Pl2瑛|7dB`P俛{B|2I|$|湎$拉^KXc 岫;#0乢ヴKEkR-脱jR^y&憙胚0皇!BM1zaFd鴬/矯Al0 台 mj3弖uUIrdx嶮u8嶮 k5斗o1$瓜Rd彿 [貢>QXdcg鯣又蟋)c1.up報.F試52N7做7"o咬g-Ny噐,R^K-i_QnS)%W= \>Ka ]#gq%1F喞R.=`圓q庚-+X瀏[Km夜YE$s]p }D9鵯rx>1*zfu/!舫u橿`'@<蝿9疚\T.|pb p6.籌郵玻芥S3>%3U^`Db[o->$jN垰%)-hFFj雛mX瘢J!>F|&}nE屠蒐{1SZ"0;90* 3軻XVv#概3:19楢b1*gJiTtgQ瑁9風>L]7Q_籤Rm萇M7 P[Y%{:R助毋Tぱ 6uX=刺HeYhﾒ煩z)'C@瞹$/^%CI8o沂Ru & Ks$y=(SNu/%zPmvFXEA26銀)-1PboA.06 5 Q.A0Y鞘 CM15rpH霹G;盲XwL5zPT8zpURu 蛆e29H#D佝!鬥RZM境n+#||菽&uY щ珮VPSa3+q亞&鷓:ILeJiZ $,d昨将Faa菜<叢驤e+k層ZP巵豌QZL牲-A|汾>[N }DF1VzvkEK乃y@dr5$臾c]^5p檬ED錚a汽U 経G駅n】O[E隅$.>:L~悌9q+1yaK+Rx*a0狂,gBGapトﾄ0}m!lA'uRrJN耿Q  I--Q%R忖Q8^S@`FsG5ｵxp[R ]瑰s朗YnNs`慫-g5 J椢t;D}gc&D !!W~r зI0l21W煉◎褊yg燵畄_<B|WOw?]\R衿謫譖\{s)|O jGN\~wA 瓩h;+)]竈T;%昇 SrXG缺脩'燼鐃GMqв 6 37ov/v|zv=謗ty肛準沱r系r{梓4>?_樛?^wJ>t?z杤Gめ松}{"u\昇住y!t\Qp井B剪xU5/A<}撫視%4舅H?%柤1+0椌河Oe鷁R5; '桀'/%慫)裙%猥@%r :恬6^ KIbP1(=頡TPJ<抄k$ \$rrFlB ,[F%y#Z 姉cA6螫 I5-k"試L.&t(*Cq<.C4v=)YB槐Mw0F `"![Dc?@F滴wahCdS@避C延FdYaku-R翕絣 } !}JYD}衫uR XQe鷲-寒:Sy&-,7.0y5o臙z垢(恍d)h-報GkX斯[G芽-帯2痂Gk4荒 EICI@I淞'gL88If~Bl}uKNg8JI M,$Y哀|N+ rRH6d岱3>粂b}I沸 Ora瘁5[IeR0R恐Z_cF>B箄r+ ZIK工H茜葉#牢A悉)4,Ci_2eF+5lkF髦uhoB女p憇`c:go{(J3Tr/侃zq題A*Nx!$T巛l曚,=笛叮7'vF+}Q5f- 8 揣 \,NsHq)戸髀錠GOW箪7r:癧胙逶 1湮~Tn採Gaf>9>IdNl"/9N=63,@#3"%Y/DBf)Kh-\算爲jR=so樸ぽ竃3}+"2q3o%煌"8It憊@$$Aq縣G咆B7BR i PINXdV*rN6sI. AJ%(@*jDy@/k*FW|Eｋ*)誂ZEk皙_q%)u\+uxеwBhU $黌@杭w荅! H1筥%耜q!k;"y襯掏坐>Em'議嶐D!7Q`3宥h]17#oq!jIAiyZ甑0HO,M b欧 TR_i+4M#.X]頃h槃> ,O&IE }Cdr蓑￥ebt啣'郷碇CZzgDt3bF啝簷\eLb7ve劒%!иUrO&矇 /ｻ)^匯Z%FZktybJiQ屏ABzπ FE杼c7切Q!*UjH8a)Qe$JRJ G16A~ f7nn-lezH0$NkJbhC7tk" 6,6Em7MG5b`]hKB~楳wocdM7iTY暸!("_B`A星禝lP=S偏nZ0.Zak竚桙}j¢q/%{oaqb/pXL!%議dRXn2ф)z_Fx B唖/牛 YS,CPt\Nkkb#i典_wGf!涅JB蛻尅yu';Z20靂 )1Ri3_N靠育_嘩AI頂mEa錬垳5 R SBｮCm笞%朖k:囘-BH牧%fMH7a嵳7iP3Ｎ鬟R k-A_jc*F!Fk冦赳 xcゝZB9$H Qb4@蛋0@h6[NZ汕E4．F>F8fq勹庭d2%o 緻Cb掖來壇lQFR游資giE%>l {O鎚1fI. "hl "hD8C繖, z0Y溟LvH麗9迎牢bD鋳Kt$k"芝qn#6p7im`A巵P4槊-:授i;$VtROhU覇(d q=TH.瀞+&)GnHT雨mx5E g&8ｕ0R|I1f_l.dz~mq`gp2CFy毒9Os╋$MZyr X(W懼nwSe箸t隨'維)e擔A\m:ニ .{{p阜2}" `ro}^\=grgfT=匝J0Spz8KamTR徂:zNWxoV醇ZVφH+茂SだR應)S 8O冕渕qR.魘G|u3倉H I VaE%/"mHuNw}|E)!Wy3ga茖?c|蘂1A=oＵ∵j瓪~|eI-vAramYdn叫障寿Wn牒羸F! ,}量Fm愼)熱|pw06)IsIＴ邉掬#!`8TH:/1W J頃-wl^47E參d"Fm+9e蒿_朝巻yl4^EMJukJ_O!_x2/IJ_n6!7hr(L"nqp,n6p~PlL!n=QJ+ ` Bv ^A^~_~o1|O睥AQHB (N`B h=Ha!p!d豈Z[vm a* z/u'iufZ Ud6qcd6Z\rヴK麈<^霆菻櫖/ Qa_gK#$4LK#$4Z:KsLXN衲jW`械FYQ燭KRくア.IkrIZ芙K鵁oX}r丑0?6c6DkO\!qnkX-Z]%1:FrmkF]!V;/蔓c轂pEl権?6R%抉aRF/p&膓!賊z%kHEU糢j%WCF籵湯C`' (7 泥0&#JkP旙J'6@y_02c覚0 闡; 鸚朮@X軅o釜e算掻ЭN恬'PB~i0Hewzv戎重Q柁P"參o痂PqSW]働佻m4fxDJ@魴y/*47 i濕概xk艚/蒸7崇副髮юg{韲樫)%l燻海]]9 埖峭v>{{@珎_V舐VK,昭襷濛?~ Z}鴟 4]鶲?Ow椅毫ivq<篷^|e^DG6O^w↑鞆笏+ /W一o誑濔鋤,罫eV!TPLPI' [@3S-}h{ $5*X Cペ捍輓GhwuX秧 tk8`(曩2 EZ2~y糒u d5D.瘰qHb硼釟)wj*鵁ngstｭtH動貯x)蟯]%er_0*陬珪>mO|{ 2}5p極#q矮 f<,?wx8沚OyrLN/i zFKnM褝椌i矼!H; {\j>Y']wBrZJv@|\P麕Y.3V+P3QqAPr]I ARF@!/6討寅1f◆i8纓WZH=*" c$2jぺaT u鮃?RJrl.#BhmsY,5Co$鰕犇!Uy都n暸 ZQLa貧V琶*y 自cY)2Q掬PzNk9PX\: N~|讖快\$鬲j誄}"oFUFjfETK%WS^坡E*@lj△.,]!e@r[敦ud径WU"r脱覬2y2DC衫q)BpiLdgMd|sP4N其p_0'bn(&, KpmK"pm` G!nEnV瓱枉ZQZ#Bh"SVlO B(Vla, 0@u傍擇,ov魍AA莎}+q.B-秩 璞Gt6 &E^)d(e 舳spS統$amVbV+Y+nF!7kVk{XsE旛w(]AaZF38@TLwS)A#M魑+Ｐ皀z)AkG∴X> QK6zar< D自eA, (」M鴣灌A妻;糜 c鉄u@rJQM,8Z!3|\K遏+'7,/鯣N&vZ7U筴俘3Hi h吮=v0t S O'=OY"B1$ #"e/U}j1(錫麌:2祗1v0GR黽 rG-l`bgSk{E@!XGs怛踊清g 縫u-唄F殿O囓6 Ll?6:I)Z9/H+sf&Q?fY體#(NY iX/◎D +掩Owx] 幤禪旱Q'監 = 渣ot:i鶉OuψO貫3|`桝[_\ru@{tlj`C昜X 敕O韶淫? P壻t]CV>r]痕|ua拝闔8s甍8皰-2dv疵 崚[a+G?i嚼蜑Ql.R^ $"w(E 流J0pEy3秘 HfI`讚 5=8W租0uN+F鏑L簿[Ef再}]Er厖OW5+┝DW3跌%M('帋h$Ai}= ﾑvC?薛K"Z!晄*k9郢付w4:~!哉kL0<8<)cx$B1<pi$ -Caz*kq量痔)仟@ CAN%iN(FC $u]fL'A$董R給D峡 sTiD`#F厥" ちQ]^qI:aegJy[>X:J)xE)ZSv妁e(eB?jfaOh; Sh)Uぅc*s%I:HeygLj攤厭0 \鷁u}'所肢umEb;XE覲~蓉9psr<*w6Zｆ)Iu =/|}f穎L損躅 ?7A,^cMeQ｀羹絃l藍?F;}^恢}^扛c9:*f< α%MZK 銖.S唳dl[)twパ 儿Z神N@Hf帰$u"$h珂"穴6*!i8'紋zlRL4ljVt阿BN% mc Q+慟 VQ} u帙Pg_$;aKE|bBL) 番W唄?zo 0p4:!渦X)n/ -3nZ BIWjA7p痴9 :IV P(&LPp綰qv瑰dz$~ﾄ慟F"rlmJhKO$yTF]M_'7>=_5[syb\V ,泙4ttjhe族X#_)Y|雁 %fUA3 毀多}+B7E`?垂∨KNA|7土-Mj[vｶn盜b,yd " 夥愨諏m%i車桷pkt(r官Zt 幎辻vp[Rz2 茨q咲９ uS∪92(nJd 啣!a┳さhO Q揄~20僖цaS&4JTE1.$).2;眤6>w?UL2XDS"&ZIeJ√ z嶽KZ襭H"b杆/^)/拇"愨16qmbffa`~avw\hg毆 楔綣K9w曉qD)翊(#N.Yp24猖I}_閔\/ 2s%G"味[〉呼 0=u!~a)X$甜U#+ヨi刊VpcA+r7墹UU6l&穀! 03JZQR=3uDa"( G弃獵zv-忠攣QUIＶb@∴薪J款@Sw(`[ f5Y)v qfZ?R嬋q!t5[$髣N ) xьｷq w駻$‡v"?Mv晦 圄｣SxsB# 斯 [J$藍nY住渤燎P^ 翦~駄[zy !6國 c#q Xdq慄o1AU4Mf矜|S`P(SD>\珎7fp#t善>U95jo拜.%涅\B7KmR陣Q[d';z戞Pek拌T )R=FtegkN驩\RSS禄aIjAj1emI忰]i% ?喉らD囀無n支h&%7Dd)6l%]莚(khfnNgF／_<8w3篤*2Cl別)夐dH駁@UL=+j{rwJLL8o~-@x$D)厥`" 95Wih+bp@R&7:F-s饗装財楝EUL#&J:罩絖uuB]1 ]Z%e戀釖?3tL0O)aL瘁爭R3%0聳'ev ~* Cs@ !m"4cWxVR L` `m0UmX;TB06aH(<+rRbＮuw7Ww"]G!o0;R/0浣akp'r:r鑿凜`TC[0*`WaTc蟯 Q?6%.9m~}kk嚼W\T賤~*魚UCfYb犠WW [:屆p$@# H3_$ehvm+｛rLj５2 PP(uhQ)]Y \' 恤M禀uZ 2F- A晋粫FG:再:ijC引aV*@HjMH/-#u含s,!箜+W"(帚,好跿uゞH貽yWV'G$DD_繙1 [Y]q_$膤scd]7lq?KxE扉U6Am蚓R暑j0N^~ He都VJg9綵溝l?]=TZ- 'ePtZ =uj$`XIo]お*@凜ho26'＾[KnB*I∵ap(>鑑ZkTC[Pf北Y- .P :H`f起懈jq%A]g 桷Fjjs?6ltpE鱧w燧`~W魑Dt?4当韲Q:S>{SI疲a甘Sz^1~臼稠1X LK皮"q靺kF_u?Yxs$澡羽返想I沸D >n纓除gx9O * 栴粹"zYO(&1I{LqyO(*UJ1OI&)Ie>>dbU4OI&Y)痾bO~!x.諸'BrTTVJeY)8QFR)PI&jOy6*>%69羝el#,)２PTZ& 2B1y乖@_3H"jE'JN(^T(X┘L.4U u#geC=}v b!SL6b押RT6Z防1' dCh押T6lH.%u[l 深;NO3 c閖燵1_{ z\Z|A \{Z贏諠t*薯YD (YaGc$Tz]s *ΑZ=E-班５0/h-S頭TxZ鞴朷B攪A躰N VG=RO:請愃DJKb忤@Л6Z'Z3 R1/E5:u)侖:梦l ({塘*24黻ZI"I欽US]|hb}*rZUm峩籠:c僭\G,1同#uDT y5y c( 1艘0:へ6E/)N5:#h!A_V"'^俸APh 屏HApS銖 E5Nh"*mF!}up7~, P散X3RQ族蜘WC艙 }L}!bJ僣 E淬℃\WQ8[薈-<[h$撞m恫蛇#鐡1? y,AD;z,f.:{A;DAz`+s%{D)旧8峠T!8hy4=(n'Y\`jHs<碼ld┃l!l ]弭B葭 [V90AT痼$Nr:t甥~央_弭O!#|LdQ"cY%cF)篁muA&=M77>+yl{,_8 dゑf Jso1Y7 qnH\%JX?Z[EOC$V~*A3遥Z[N0A/Cq塲I+J^鬨lM KJ`Z*+B 追{“Pd8/y2x巌F, '浅i-tx/ 3wPHH敗s1s;!<@3罫 M.r$砠お[GIW^I u.q雖ZCS`<)R$螺S$)r60 LTH餓chkC:H$mU~llp磴9唆x@. 3luny婦Z7F舖退廝楾狷YJn適院Uy+fm&oX只P5VwG2:TF｜Y蓬N必 \"AkG]G_専oZc8Tix!※!a衄TJ lDz/判%-UUU陏/@ n(yi)5‡~lg! 晃U艶"賄EJ廊VIoS%1a伝($RtQ 8e登_VKd e8%Xe2竪$O橘*Y5I2f_eqn C gVp伊筋A+6#`y7&鵜Τc^53=3畫6wdNM[uNld[{H8g(vtJA橙諄寔8p+w]I.J%hLP$Σi5rk\實z踉Z#7vU`CE'EV髟U|_+]灌WjU0J<[tx8}ag$vRA4卍x:]o[9/{$PL鰈2V$孔} _]躇G_q)愕[CWb罘皙dmr[JD?bBB]EFUktVYm6 Za穆0(Gwn~8,K\b瀉璧致I汰/m=:v2 函゛∀0蔦h熬:倣動 I鴕.E冒'WQ%呷臚潜C3;2c乖NiJ鏨檎R_T陸]蛍%Wぬlw8-C~~第RKB aN d#"`ciI[朷R}ZW&<^u#筴@%◎F R(瞋Bx(7VB]8{?壕泰CN＄s.7*U W嗜i)給&kMd`"kjgFImo]h\黻{EJ7かplV殘&42^筒.擯*/[>M=nU^*1m}壙Oa僅h+KCz&度bC27_q格鴛[&╋英尸nV歉 T?d#b||E>I0do7彑)s3茴 eBl}E介男_(l2l;x挧HE掛*CCFn^ ZJ"xnu7|?QK鋺Ja8=!^#雍a {xBJ4Π8h- n\;Rn9l=3 ,E"x,E.RH11-hLpNB)N蕁s/3'u2{xZ|O罅K書V+uJ?H水?Rs?Jtu'w}Butessss<;3;KE/$ヌ ~<=巛tOMOd/s2/$o$uW9[)u'x# ^{狒:)'|008 犁: NLqNBqNZ瑪ko$uW9K麥 zNLNZNJ2'xb!} >LoNB1'x8'xR ^(|9 9kEs7:窓 '4A→[ﾛj翻NS}E擬EGF*Su:姶侏和#苓飾w 嬬{pf K&n殖[i [却A\0nP=cR0g a粮( ヱ鐇 xGAbWS o D 嬰nP$ +I * nP 7H泰 7┛1n 8i篩7#!nGB +2 4R堽pRav J7(y}6%ﾔ9nP唆v 堽qnP42nP燼-v騎P[, v*D v*7+zv,q虚遇< DH.Y_. .c<bn}萪w杭調4~4Z}Rbx*$FS7Qb('V`ah嵋H9^V1qH膾@ |H:6j$I6lo挙q)|5呉gVj:{I6徭Tls謡k)N7yx齎Y'nV: 照S Q4N~糒o^~Tsu診陝墅*s$[r# {燦裕pW0{4NCb ,O按y$脂K^咫wS+HSb.>+F0込V +:+晢bすb*|+q s`鷙b想}亥B`+FJZb*-U癘(W甓.WT瘧i>]|4,安` r45BE0Z+i*}傚H Y[ aB"76ｮ"i^欣1H7 ok~}_ 5皈Hr=1h]Ez\X}Jutc箚/VZ\VH螻,y),えYMY:PwR/鷯hlz|)|3pk噌"h Z7`92g j4&9m埣0W飽V  .$i5{.v2qkbs芭\_浪Z2Xhｋh!KP(蜜io#2O!:4EGZ#d}2sZC勍Cyp W~/3CkB迢〉樒2pq+E處洋5s :puB sF6*(F@ 3B%,iGc ._[uI ]2`(>Sh-q 婪# :8 !x)0")B>@}f 寄V1X-q/ohje4熔P1銕o怫n06!:誅7C8(壟 篤jE:S ar7彜Af$敬_a耄咨4盆 D遞譯狆K'':*=~m譴霓w|@ゝ連9lj徂片肚46 vX ∂fiA^參ZvU=VwU3慊:{"k|殤j!|郭" 唾v0b I~Y4cm' A;HYH@6 羊G(幤U*#o忸ホcx~閨[+n 鰥Z[/}eE湎y閼:p-NVNO`'6彪|^写 !薹"gO+＄58C`儕鼕|麪濛7R pj69R鋩  z/!`臉P%*LK斉eKY~z|#=kf_盥M&cJ J陝)& 8qｄc# 7R?yS9Zi&XkZ縊d2atXE枳j0,]H 扨J($l ?$l}痔2&l=籔DXwby\AE瓜f2qeEQflOA YS( #R゛F)ΧR$?l";J:Sj蘿洛)\b~E津yNw:ITD)寤m}眼0泣 d那jo 3EmJ,>*?!dc*i斡o[1]FO}-u6BquI*"w7wl OX赤>!(X&bNLqNLqNVF"bNJ1H%S)R7Hss$sR)ぢ)#\痳錠O淌T走MM).L R6濛K=5#^{i8C貊4R#;+cQlBr^Ryij) d螢K*j,KS{ZF貶xY85V:`靤dG腑)hZ罐)eKS!5ky/Mf^5kN2/M m~&^ n罐ヌKS頁f!f菷hn@ /M.禺4bn\yiJ麭v,M>羲4GKS+Z|yi 厮?玩i 瞳w師EA煉祉ns7dtG]御9 E靜PxhfAL+2T1ELu#e6`Y傚vV 鰰chRcD%F[?\C-^qZj豐 "耨mb hサ/i Z嚈%BHJ$靦Rt%VJ:據O~F彗X黻殫干 u 詰示r)7U99Zd¨Ыig知Ud8土Mtio旛%*轌vh6鶉_Ic=6 %Ttv*效*B[に+P FbF)ｉWK禍(a?}?庠簓 姻)A璧 qkpWv員!A蛄ADkepO(j8,D飴xNHk!}cQC綫嶌-Cka-)VB惟楴pM8F`C聶6嶂*鴆U#S+Ft0惡 tIoj/穽~6原戉[%MJrR(:+h>tIC=z9itIｃ747hF?gp7!Io.(VF+6^(|NSh+-B $T ^T-ZFYoeRA ΠReX埋~E←鮓ト-Txtj[$kn犬J}FG~4NKIz+EL8, 吶孅UpgK2Q麕咏U茴N6^'-!fwNｨA'GtKUdwO}2=z串?藝J鮭&G氛P7XnpLゅj+b酵?8<]rXF2践uR FApP RI/#Y-Fk8WD[-t筆弌HBY D)UH <|41%(J6盻婆| oq&x7《,_pfp=朦 〆Df%+YR帳I-9coe(2 QzgmZ薪Xz[iB訴Y+2HdV齣八4~"2+A:0+1Y}f- /idV∠_V,#xRGf2#Y^ 冏ぃE朕u-2I>2zYREfY42I>2KH.2K+Zd42KIUFf脆,!攸| !DTJvDOE``h杼覬9&+Teem$z&甼息I}qUJ-^季_Q XBamD|Zd權M.0'QNt>Φ 蚪M*kE:Wxe t\E4刈z<k1(S慂[滬3O&\Щ簫e優v笈[Qz2A&6比8G{sKeS-ZF侏YacVl|nl>戀[[嶼軌Gn"9`cnH  R+ p7M晁*s雙Ι樔lR nIB~8H噸愃nuSM.K[hx:羨w爻8 A.4]c?,v迪u留A>Pin0FIﾕ\js,My _/G}jE Zu-XuJ$Q鯨,M#だ篇tx Ln-q1@`浹\&訊"hpP(0%葉wk歎A{.hUF7:グM  粕6 盤俺#BmZGdFa'他廁據Z.r`y復58 R斯3J \∩e晩v`hv^F_BHt廈|%宅 z;Jl |4\WZmV5/S8+:yyR{a彖j驂;Z-温2噺"&種にiE;$%i杭rH|u/ I曄/BJE 滂pt-;9 Ra<P~60:\qz#54念6D @彿f站8k鍵}@-E (xi┗]ZN歙p+B"(*:bn8G8!D倬VeE0 QK~D F n4&<8m!ru:bAyA匸h]p1蘊XI(4 :屶p' y>O8I.Ox I棠Hwy=珮\,'`+VP鴕rmte&愀Hm箴zW 懇t懲m灸菩竟f: .C&h-Am江I輒8!虔伶7b%載/,2w鍮m0燹}ni*亭羹4K9hah FuhSgA)XL+ rXu4R+5袮`o飃V徑腎'楡 鉄+@F}nhX0h-RCg漓+5l DbvX"taDv UNj.>G靜y匠M￣Zt2SR漏/冥&+8鰲W-S[:P C(zy$\蔟祁忙"R!珥w弯eRo飽jqM-,/娩 oiW後R<!$ﾊ - 紐O<p W (f@&:(I住黶Rゆ "IVUf OH uVQ|:‡瑪Z舗A_-OK[9d0b|z)u${kU畛.恚蝴4;iW揉I`AE恒 {TI#ふ緯o X+炒祠<♪殊*>|eW)DUEip{ibB!S$cZ);9p[x窃*i r}d~9X89EB朋daV熱m`sR-l$#X%d/v鵆$ !$1S妝Uh迥!;uV潅C<5H Q?h Lpp R悌 R!.(E!"xBQmPR](`exA(/ D(@/h{  ZJ既`5b`P!0a*H ` ′0qU  ph 陷h@4hg&h(%1x/h@Hh+zh@:.h@Kt K9@9^寅w^ })@7平+R漸/1e_"`肋e4S\%仝KBr箍/I.g_b肋$]%!轟KZ腹Tf_o 遙3l*EI44正偏1 4龠 %tPM_ hRg@ZK}:(@J鱸ЧtP s 46g0J3縒AS*A9~>T 哥Js hE*t<@嘱tP!(PJ.b@\Hyx俄1X黜BmM9^*uI1k@茱z-"P`針r+5渤])aﾗ]*2L錵 o0' fXszsG喜_R|欲=壟 錠H諚DYR2翌f`O@j喟UwxzY"p,KKn臾 ,~8k|qOtC$#x'亠&m鱗x %恒wn=JYxj0Ie}!{dc0循沚罅g)托茉Z Ynx疋:=>冐^.FaemWO#d0騒^楾助甍覓9 V,$F腑NbzXwq堅様 |8 vVD_j!Ox獲 Lt%x?;.S硬（落螳調pr瀁}' oCM) fY8眺=宴俄髻'z耽.O桿 oTu 繃}9灸q:<f漕5輳n策srC'汎or .o釋>$燻錵>8齣j餠w救p3x麦I京2鑞I#g舷mx遖Wz/uN4-畢冊Wv驛迹へa%Ju HPz~^/9GW鰻6鯏\F~9揉89揉貂斎范&rxkfBKc< 弁i14hn6盛t0 .{e 枅悚|+讓^_觸lw-t]仗@縻vxm址\K BsW,=燻OWmn惺/[JgGZ0棍'L躑束施vYz7J伶_jBNFS%Q煉F=薇nv彁 膓ii3KAeKLLzq3-債[ |y@陸,掣 掣蕋.4KiCV腰 pP夾 +rを9憬喙Y銕$@PVya1'x罷礦f8躱ag堡zD $ AO0Lf5J宋!圍墟 :!O[!萎擒 /\i綺 瘋:O謐}E&Kgねa(畊#/2cOG[掠y 河溂鰍/殞&=鬮xIз-UE '2`r^L'[ｒt"yg(_漲wlx/UゴK貲C>i堅X)K^9l銕_Wl:]_*Q蠧fD 1<^rOy磁]-zE舅擲l[^L 柚!;ay鑪[Y制瓣 5簇?+K(KrfXc2VtipZ%Q酊_織{恆瘉痾K救Lw[<寶 ,祇kts騷@7窈循 r離=濶y4N,$h洶_甞|[~t/允I^,H五,O[富&）馨糴控汢sAk;HV囁tZi誰LZ5舫?憹 w菜_r孵.|K$/g俊!限 y_p~搦D2i '/eAt8 \襯fO2,H優PS揖P[|GU~0G2C:: U~@U┿hU桧 \v Zw僂V~Y4mR毆僞蜘'zvvdqP酥V眶8_A耗v[ZM6Sa6~プ^hLt廐3型Wa1o?Z勇)暁<GT]s]&PsX蘓谷9_R^f"源讃_,蘓爛u狛 4xf/排* YR∬=d唇J[f6/淤7卵!7韶xS昏G猴~Ogk録{=.挺 sl;={>畠氈7(pz囈韲~'黥q色瀋h >,黐'敞2JF{w y`y>npq'*霪:UA|.愼!?C~ [緒w yI]$} u ;D銭贏'>l|佼B貸y1E&%.M=g荒M `am<K'闕_s"r弘?蛔=| 6ヮ xIV'oEg8/廱7^W/_職Y@援I "Z;UOW-*|蝟峰%{.|FakiI{}8`jN@*o福;v*Q~#[労M 杞& B-示(lY@樅? k_-tG@w*zt 浴詣 bWl与!O貅tPiw)]:壞cpVN$z婆~.鉢┷Eね<)W7(Qn撥@5"[J#b$V}屹b` x);r臉J5 IRP$8m90&!-CH(@Z\C犧y堂k皸TS; .寶伽 h)舊Pb[W-$@U]$ q鏡JJz+CU}k楫8~1 i璋耘>0.t卻M或h婆gas *瞻 )} :B0J724i $+ V/gp8o+n曠i禊!'*?M9r XtrAェ`ytqB啝~sこ)L%NU v6x YN $幌'%伊/泰嵶QJa_(#C$J$TE@R)p @厂寒D:MU罍/S裸61匕d\3Z韭D)e*hr" RNO  PeqQx:5*vT膕!)/仔K0`^(!獪(j&pSUZqR*x笛i|`Tt范Q士~Z13 rR6!w_LmY8]痲Vb /x耆い]Ox{ly6?yE9^9B羸P%吻R Tm Vl c!A@cεbTfoR[bDB@鈔T!Le`09n0R(0ZF Lu DjRY&曾2Hy黝)鋸 S'2$lAj Sjj-滾Nb2hM^綏SSxFM 僅x5sT!D3S(I[,痙-M2o;1'飼\P蝗 o ZL阮KXU0意6O@B體y玄@@f <占+[循Ib$b∪Mm&); \Fw fP折蛆BY; ;zEyP!NvRS[-Vu,tA(P0遂`EFve8Ba7n~h/譱[ j劒XpM SWs曚sXkｨ)"v蓿r\ (2tVk@3. Q蹈 Ie9`JKZ|,qW -徠; 0HwZУH痾5b};r}$蕉,,,15l*1M$%k{;?鎰d"Z祿eCI2VG :-+d謁uHrwund"雇$w'IbX尤間OF n 6$/k^(J疚ズ嶷T滴Gh勗bZ2 [<_Bm餠[sfn溽(.f1"嗔'BEdLQxX9n4H憲)亟\ Rc`M=%A8JP'kcR"` NV$Y隲!>L))3荘B D` 4!6J1欝O3Up'UfhEM^H`mCR,?A! U;+X貢Hx+t宥YW=kr~qNM|倅0sDH2 Q嶢樛+yxsk-bj委Z=tB~h\-@}9M叩堙xp麕w9}t戦(臂H>B(沿3N@gなcнAxIE@}(9a[q9I2$&MK衛oD榔n]EmR (B1O4*弑?Z崟k u雇*2鴨"a"n[央@+溪#Pu\(f遣VD[榕Z亶j%訴俐MkC0@+=de霾6q G琵Z` !dI(5"y(__s yv=i 湮擒5u!肉*4来&+m^[yU砕vq餤FM剪vl&!Ju刺 " Q 蚯s`i#~qZ8R襴RW8 +bSJ= U]ls"x7We竜uUds低,;k C 彈跖<粟^MVFb欧ボ睫 l:UyPBX儿7Ly{hvT譲酖K7/ ,疸型{曜頬ED3党| Xpx_gj6s?.c槹G.NT"35h*V'IPzC.\C(C甦lm(<|老訊A\vkgZa!+3-甕箸諫ww訛|YbMW温а* :s 濆rpK角ti^15)"ibp妝6找^峩釟 ~tJ洋V&^(V4X粋)o欷a7砂(vL0{唱O/9>lft台~FLa3VRK H- 啜P&Dユ抱u麺弩駑Z.X-~:4c%$'D蚯GA装s檜16鰰H%O啖Z->`LR&危w'k屋 :\泯=(K槨訣94jJ42-?]G[am rzb膩烹~<:[靖 =D5G 6 舘B!.迺' FPG2E0 VTj桝eKZ#i0S抑Jq@H(叭6x`:+vヰ壺i i~/2gE#媚齏s[rHLk謹oXLk Ｍ"Y4jmQ ,b_X1/`/AiaL ∈}%y ウx xm3/SXlfZ7竓s￣C藏蜊k怱0k8f^<5sZ]!;dC奢E~/L !m嘘/喬Zo%妬v_M-曾Ega究_D奈,9Jo_d8唱<_|#mps篭=砧G|餤5V*!}'諢tn($.濾Z&Rpc{gZ:M丗tRlAlG<;浸/z城`()5V+1 !g〇s#\兔mvtm┠/K隸匐zu;QR"K2[/SLF荘B?cFLbFY:R d@HY m臆io蓿醺^&odc{CsG.\vSRV;+9CW浙M3_6JM彙D>c}舫\mW暸猛HGVt<挫幅熬┏ 1>閹 5艸*% l槲s冷l磴eVtB^墳#cIew!pN槐e瞬Zt慨,{O%b%aZ槭(`D!em}FO}.両t旆:?/^F楢lBXx?{7%廴"?GW[bS g &w7f5M1=u秕x%M 9kn%(oY甜j7hPd6霙揆tC.W毋5BIa支k1鍛諳＄d*%m"8#[ }96ENG怖NJ宍z萋7bT(封喟X唸^3F觸胖@Xq耋6Um:6"oa!me甜M%鬪pFv"閔}w.nSWT;m n8q瘤屠t\] "+}'?W轡誠>sdo僂古|z{r2'FJ&'脂ko68<L)帳>#a?YoyoV[7丈)汕K堡[L歓?}固靄aw:Mw;K_0|J  {Kfomi0)[PJ! B@SW3g蚓kJ/0. ziA'm姜~pJK 0ib初:x!$D"竃?愴萢嘱^k0\K8(墮I 弧/4 ']Cf13EBMK裏j!-搜+~疊H:j登iOd抄0!mp! 追 筒Φ /輒D U+6p,ec RoY攸QY捶a4@q獎霜A哀ｋE{ P<.E孥9烋nVxB+:pZ|O}Ce> e#NtD杙Jsq杵%冦nx8N7O2PNhYv(+蕈 {wX=<$U8a懐T>NsqJUL趾?q$J'R0,9}b#9v k>bl)d辿91,r泣 nr<[緋X:九iR_(d,.w+н=PR5Km≫ no!jPy8I圉o$s?Q4`9_c7_沫M抗罵I xP u1D+8U?[=R癪3QzH)$H8?弦話!{Y4(秬4鱆Y$誨&2q』?is`6!9x2jPA泉,(ob5Qj袙H($犇B\:5笄薺'.S@#8V' W!n>S[遥目l|Ej2{dd(kK<{fH |唯W~楚z馨a70;ぜk萼g(? k|??=^,7DXq|=没梠?{b7a歇m &}<慙4砿hir/6喇≪Jn-5酘 (V笙In蜚Qt4痢!4EIδE兩 Zr !ipI\.E u6Pap)>~C7貽渫Ra *Ql1X't$ 恰Sr訌J益H弩=&u泣rU攀到 黥Vp!V痔44n941*ｫL^l K1柘T#仕力?dbv1DI隠4L,`吉`uF掃楜BjZW #b2 j貌襴q]svZG M54: $N剿ErjSJ＆n|AAnT|T捩廃逃冱U篝斉(^yW"U$8^o8Fv u支p})擢SK'I%建|攤 曄Ud侈0橋'4歓n] ^F)+QLE,L喋d桂UQj嗹箝R~濘%謐<擬({<(7$剛T遡牆AK, 6p ~F,線+R鎮"孀b邱b%qwXu師Eq%y1)睨触裕DPr!狙誄\a^v^掻劔絆秦}D皐$6XR]mI#~傳G'BE.A7q^{l 糜慳F"程]C|g*&0BWD絳凪>HKt撥1R\ GkW淘)dBE 醐@p Q"Z^焼+LIj!ZLe_wrYQAN忍vc価F&Gcの''義Ih yJAm烱 E f5槿Xw搦nyQ*tz伸T覲Y鵈翊 zP9\]ш鐫'+沼橢o\?逕hQF沍j9蠣敘ZFRV喬巛-鉚[0t)k蜈皰X54E,%'&clK >SjK欸P眇ｻFAg i019Rxl7 攣)Ro吏c_KB*FsJX2Asu昴cb\S: i$>\W退"&YWo址$fh):4[A 嚇}┃"/wm訥6R蛤Q.oWn[-86m(W8瀲l籌r瘋c0c貂~6F2c Ne倅剴/Z9qHd8@m5Dc ｣k$@ wu"nc"' Z)=Uk:娥--G8 RKv-N園e[C魍@Y瘉Y*X)ch！麺Hs.-\Chmwh 2X%確uｋ !r!皮棣和_%4G翦N]{v呑乳VIy篳 <^,?;-Ry=^ 瘧-j&「ceDa洽H(笈Yn:$rzI残瓸橋sq漢NF L役Ns4A$y$D66Z CtgW膾RC寄NOI*R:X刊tX迴>G~D1桃CJ 旱N斬Km:YG距XU` 1`ZzXA2;qTT`]\>鯊gw/`瀛/<]血*v 4DUW7ei#b(-IVT!*-%v熔WZ鵬a3V7f!G.N x@d写阿イ鴻dcw発zFL'汁 6桃s蕚> 6鄒^}h伯>o.}ltp 考h63b?Z+CY垠v(自E_M)(]t"i|熹[5Y[-'Z|?@FzθnZM2/$#qTz T5凪噛nyH: Bx給;兎*Ql_G匯8"黹eb|[$H*'0e)|t*a[Gm鼾 }Hv%P顬DYo$軟弗(bsx$懍'死B)II9JR7嬶H皃 .7Um湃Thna!q濱;R[%|X樓汲(PB寒毫n0L 恊0DK(陬QlS蓼((u~醍z+鬼e檄C譽V(Xpe n)D0} 8}NRY|76R柱R*f"IQS$0wY:KC4.y{pS椀冤=K園/El2MxD星7号.混h(B}欄摧ｋ}`烙Hj五7O&M m&更ae:K?厨 7倚)@d@ 2]檬f_wc d&,Kp;O'孳a8`3 IvH濠1\( CI>+Csi*+Fd(:997n)粗}O=佼a#*2R< B%9>L6(;-O艙MSTSaC9<,@ *p2親UF=!2my憚/{EiKu皀?KA<d%J&U恩' fh)CLy!Am因H;;e\=0 L\` MDaG逮M舷黒xzDt)2C`s[*U!雕pw Rd序思f(BkUa琥}硼naG嫉_筅iuAhg歟磬nV= yya#VKYW7;Pks{sSMG80 ,aK~O5U^HWbR)=sV&U | 7-挟3舶5迫e搦C /轣SU扁|tSejpQb橘芟W謾眼sE鈕vp /{~r均G微;7Bi*T?P5?/kn`yP08zoy>0υG |oq~by薩Vw孑6b*B" 5$wo謀t `j1繃O邂[澤fL3紆bT 侫}d18闇Hh]%a淨鴒N#N幗c6A=n&Vn]D窺fG册7皃<-E?lK~{昇雀U(zyG."焙}wv!笄-/鷄{O発樌9莅<[讐}く~嶬U咫⊂n鯉紹Hrs'|C6|幇=y聖fvsD{.5rr;(趣N賄A{[i笞LM?C 愛pf槃`~7f{>~s識г祗+cJ]7(]D憲^pd?禺y穃钁4披_也~cf3fZ&{'紡 JnpXAo *'|*;放,巾該俔%d!Lb珮i贏K`档| ~w| 賻翡 @q釧6/#Q|- 7翡mmx#?9@喀 こ娼ldV&?悄斐3柏勁vZe]z:o&C馬\6陝)障? fXK>v髦c屆k*#兆9 'Gygk]+#膜p_6;*筮?槹#FPon3r(>}gww椨 3B 伸x:諷7kU0景-Ｕ呎鉋8\9l[荘ゃB!U涎SI眦]|o]k`譎hJ+<rcZNG求'@蒻~渡L牙>nk>-勲L]燥綣j蔀g)%nzyan|粹簫k?h默鍜,*#CfOqE窰{G>bp.W+y8J訂:V多?e,fVQ7t^1 僖ヱr也酌[3l8O,鄙凅鮫位壬p簽汞x!>'A瞥>\|ieTCゥ4H92E蝪=" 縊"4H9c/實 隆决X得,W班ZV#1}9猫XR - 抂NNCT撰n_.A4 ?_MW鼓gC$g贔1+jUW KtTvS土m]=!_u@R 6v)算 dたm]S歎鋪%.x葯OW-I訟U-7J`zNO&礫袴M"Z61f;Fv5城qC^rC_袙NVfI極偶\-5=*鞅rG壓=bnd[7S*m{較塔*&3Y58vLp@meu;:uE9梱"K?L"cN紅副往;dm!XU7,"~肅,b.b館iTSDE浮xdfua#遨/GTT>8魴xsl !私 :7_3 M[占年WGgi| EFw:9A匈xmk鑁呦@U銜v^@VbcZ*\瓸xaB+ 4{:恠vMfTl穗Vx尚\6%#⇔8q<7K8r{tA*2v7%∇5W=諛Z借>|xi Gj @貼8sk&f酣V^|AEA r.G弾四a癢膺@yR%Ka0紘A3Yl讓g0鋸o鍾~#L礫V-Z暾WE;O\`O>=掾Cts#嚔"~a淬d龕ゾ?YNF3_職"V碍N-袁q?\y9l;怖s^S~T d霏cGl∠示蛉[NyP.5nIL>鞨D7|ぉ 盧vлf湧音BUF~M6vW;7bB"(y符v 戦篷p`嶹宸~^>深}玄Cex>h {dkywN~蓖O垂=FK!NO7_nNs霈Z<k!竓"_靜Gラj 怩}'"潸償w9y黷鯨Do~|>宸ZT濺DRZ|"7鞨K_T=葺&X~,樫s数b瀧M@N,vZZ{#Z岷J[p岶Mam_Wo渊飩^~-OZL6b#E=_&絨嵬ac犠%n鴪)1>Oi^#>8Po>籟鑽椄ｨ -蒟Cf8oYK#紲7V>敖饋-骰\]|轎O) 6l[t1; `G }uEJ*ｶG.-啄^綬翡^9 KO> 惺0g碓VY瀬芽vy舮狽>6d 1(w胞魴E9E^"[#碎p閧ﾍнAK~ wY1搬nY尖瞼}>+=, xMS>嗅察#O5.f?#柊lj?pp劬 Wf_勍鳥~渮&畢'索Can'>s犬~x硅w_頗y齊_酣iYf,W濕z]MXb6* M猷_\Oe鶴蘰I誠?>◇到-|諮nFD昵g([qALW 慟t? 膽財Ks5奠b躯屡|M2W%fU Qr9*'遨I祁$|m桀r列i棔-B扮=Y nZ y榴TK嚥UfNr%(lWX+I比} T0E:t錫"[4/OI慈T &|跫os^蟶缺Ｅ?射私,嚴lD=,戉8,W'>慊;GY` [h逗wq`ExNU\coaz!4Mt剤X攻&IvJu~?K>Ca9芯{bJI纏Ic釜g儒^Ov]宸{;qA0я莊oO!M瓷澀異3_>3;qQ~HLFE樮2A樮Go*__Qb`4iCsUb塾 )Oxz−棯鯒`峅K. y,7zcS｜W鰓恚va%kuC*Jgr4迭濬=[_%3S~x^|Jx| 5_|陛gzGRR7_s1Dm<.Wuh^SD巌lR$aWH~_a= y5sa]( Q襌肓o^:煎.;7yrqxV?理9弦><|81;S[MA瞋 BC挈aBwb,泓疸裾 武纉對齠寺z%瀉KajU!e^31D>TU股h/在跪`h14YffC辭v(J;b Qe敏q 2 時AE>iε {g52諷彗Q筰KMk|XWG鰰晃~ 伺%W1sZ6哮Z!iqjB|4@"g韃fZ漲I}@[ 梗~o`岬7V8倶縀[7YD;Z8{>般^瓮x箋kA晁(聲妒o點4 !X曇轤_圜佯'N 跡z轟 狎｀V謀鐡Ez*蝨!)g  深/c?ZM=!m.$$+/t'd雙'ﾁB伽霞菜{B&Tvi#'HW0鮠P]VqF4.mLce,P{化P_3]ugｂA 3{V]FE CM| #{$c98j,0Sf)贐^]w励C^^R s{;w2.]jQd#1>WAJz騷K|$d$>0X{?&_b 孫Vfi[m艘J6P:HAB措.夜 BI Q繼kw狡3:讃+,闘 K( 6@G*癨W -牋 |娠A}坪[赧M'A#b+[+! W扱wwk0杏FP|MUk3\S9oOz_~$?Wｗl翡鎭囁ywj!|?s1厘`A伽M(ouM馳R%廁Ce儖lu駁竡nEq筏#諭.}~hJ)E{Yp9ibmGXKTvaa逸1 1O獪av=][03bl挙枅0gz*逐X 6駻舐c\F?5Z\0(>x 酌7 穐OvR%eIB'6 凸槞 #Xf4蹄x:_8拮f傾P0恒;菌个V鈎CCAE凡fhEl){9W筰)煩?L62(u^b筴氤y$l-\1袂@Kわ蟐Gd?G PLc畤4&q泥w(榕qT3g@.M=駐4_X|減x々 !5cNえf^}鏖ugG|巾.:S=7c+ `!/Ik)7r+EKg!qlz驅PSu7g&rgn痲@概d0 J!q竝~朦LL庫:Hv陟\CCh;$螯8o1!8\R'nC鹵th掀| 6瓣/h袂bjm1麿AC痴肴Z-Fph"S&ARpSTE~iq=起弩5g鑵7L)DsP:xuR{H:s充図}oO3?WW膤[q/竊9ZL頷_/沮 Cpi椀7-r茜[X IWBQfZ藍GP鷆*m>'{?UG碣6%楾?[M; x@us袿?d! ;o4wnI\徘)gh躙颶 沍p*季td0沿3畦"粢Od#JN5粒犧談旬Lw嚔治p_ﾒ M0~Cg着pFzsJZ`BL JL>0'BWb\$Ak D繼V-症厳^B0>&2杯賠信W釦fR8LjHPQ'%q7}Xv;a漾ol<&.-N+ !)W Mv6レ 偲翻z榕rﾗ:Ov 仏2占% -jVΙ頡4 UqyO銕|Ki寺歪鹵gG@癖穴s=萪|-@K%Cpv/j^哢岶xr>LO,塔i<(5/尉膃}慇憮j3視pq宗7*X(遲聚6] !RjN(秀PZJ 36Z託QP .H.B9`Ku7 u飭#霹A.s鞳+TeF% eMi{V$QBUzX(<<征瞶&<% Mろ Ｍ 'sD&y}DLhc}諞Pd9mvB驩2 [ kQZ>F噌B0k3i IfD氷JxEpr∴喞 |H米cQ湯,:xIR6|KH*kXNF頭 些y坤 {遒DA矯y$K~,K3痛bq鈞1 慥luY VS oEahPE% F'奕ayp靭}RH9G?C!f?鞜暦[9-wN``;濘`0pO哨cG4t蘇iWΙY:QZ A~u粕lZB闔qhH}v]甅 O党.  ug [l1通$1$P @rt7嵶f亢`$鵺"-oGtOS`z牙4dh90B>R H&e;晁zA9槍2 疽& Q洛t<儁&H誰aﾙ"潴@雲)0_3WkY0侮8 d@#@g-Zd(巻& j\X}iグ%ufK騨J絖皖b⊂抂0FlO;=h{.$養pM 4%考Ufh8iS轢*侮V呱hRZE!UZE訥 l6 \L8Yz死兼&T{ AU丈  / N仕vA036S*Ng'o黠)円ub陳=2gGlN舁 j%o軍pY涙}>i L梼OOv短^h%F,h&>,jb!*a":7雲畍緋 ,3e{XOTTlaU"HSF|w經5TP< /p1咾71 4$oeewT$p遇"_a~~q"ヌOM^衝戒MT溌m{q*.-錵暎rЦ>5舷肪Q7Z | >!6p>=麿;k寥lyo0G音BQ&S彿鯀\-vQN:s丹T 2e3.N(jM+【劾|鰥o^5竰 v{%+<] _衝僖OJZD'$D=kNH[09:|6QP,6暫E猿5嗜$6 光腋};7Y rfzUk;M2<頷 +&KTmNtG3h軻_9Pr^iuh9蟹 c]9U識k{、!;lou{}70M_頗翕^~-7惴非=y笞|λ=3% "Qλv掾 g[-B憬xp[Xwiw+娩F少'F謄og8tc"c7, v/8&S屮 e{*|u=g>于83WKN╋](蝴x77Дry預TEV7%費r?払23偖Wy>wJTv7p.YAC^拿Z\U黝nTM捺0踐8ET握H趨Vl:Opq^剥額I2 偃SpY褶弯&ｮ%tL$;A面UM;X R甓兄笊ts骸北>}速sYf3嶬\Tg佚5$oT %撒鵆s;'uG!r+Orr/遽n銕R-ov'w c- 紂B:}=^0LЩ#芻d奕序選Ez]d{9褸３$衵Fy3N?槹= 鰍場18奈h癸奈1hx$闌 冩9;sIベKyE.GVn7尉/7 `K-?3,F踏L-k:u[硬v9e5-覡鯤il\f.熹WNq釣a :醪J"B鐔犇l樋棚"OVh穉b!.zAGAtJ&制|1bR:'K畝{HrIeA?QU!4趨\,5阜U澱Tx$T<$u9AH .擽&Li#BNq鷺\c釛#h.NmKviBFv和D88U0gcZXy){. 8Lぢf&0<-'悵茫dm,Gk) n 慝JK1削K`f錯A%>hU(@+_K:T 尓I!W傷 c賢4)ibF,U I曄 _J<bGZ %Y匈ApjzΖ効;N"b2e E8S勹S&党/"j_#s9軈{f/YTfh9墫N曲1h 7.~g xiD$4F|O遏^-y宦W Ps"蘓1BD J稈!!恍{dIeC9P樛c||尖DN$!淋_G%&>&;"p張猗.措w^[b魚yBA- 萄N,i績,,F12 rQU#囚禅S s=@ち(棠Hi仮|(^膜9vb;Yw|%ue}c V憐[ 鼕ALmuｩs4bw/猝z簓+G9Cd辞@ц鏐+v/$dy决汳4沽浹 a\8f4IlA3 覽&dTV N矮%6iVD{pq%TqY3/Q[?.90 A^@r妙:M耒 岬M+_]_|-S噪|uc_BNu喝WMHlof;  K] х_\N$v 嵩BXH6" w鶩 tB栓vd苻 膈飴遊AE烟}W}Ie5lA}nnX4S"準悛[E尊b8EU2u3!vk:-<辺9I闖nPr%桀僊> n"#d`,*,7%(5]w.[!J ^3n*!Z(嚆% 7/zcvs`xF麓稻7/^}k?熟徙5旗H>[<檸k>)p:仗でK僣].f※Q閲CDKАf7 |磅{低銹t7&*@^'t箇IС8穐A,_f8僅)4%"i3vr總,餮搴d[r3K-j4|8'SfW\Vq季t-0W+.g4Z憺LU80!Og6M鍛z,ｓMry鍮t37董椀qyw1鶩e0u>#ysQW`e+孵s睫K:c\ MHgUtp >欽 V%5XQ拂 DP` e窺N+So?k\Y,zrY:砿 51p@vK矧w 闇<儁fMH@,V<+捻tQ4 f%@6{ [45?扱&4q^蜜`*bv量so.^顔q"J/作"R壺IuN財滋,Y+溘w蟄Iz,q抉>{N|~淡60疔|髄5mcf9/> 5lW>N3擶y蕚pjaV４:6 `3/9!0!;vか^m(^頁}帛KUGO迸0y "Ro茱縛A憺>a}ZH)u%*)FF鎗 \Q匐TWj勿1[LVVャ hp狆逆(4牾g狆?毫^I):@偐GンC腺y忙W]>v螟MW,G}>$DJGr->麹89";& q%$- .f\四7齬8i)wn tTU|I跳LS9cv4|&p 8ghQ濆)l洞醵q2iL l8*B4Pd !u&7@9 % T&/_PJp /4k=Q81蹤x >] o]?WB $_!l汀18pT6N楊T迦o 書這穩9a'lv ∠~Uqt/afl.gC 賞'E ; xO3~;uE>PX5O9e27楕RR麑r憚m.6―(親8烹#Ob Ew*徳;scz[1b< lgZ.p8稼llMfl!{p|CJ雲皙儡‐-YbL櫪膤甘/B3晝 +~]2B 2M[i) 鄒k".?e0粃)$u僻(弓淳vpq&S轄蜑$ 觜.fMs:腟^?[n}2佛p訊p3fE{q齬 ^z"&[G睚 nJ&y[ta'yv)TSzhGq<和y'<:>rj/iO#狡,W地xs2恬懇享y46$yI"鑓SuEXT>嫻E"kP&q赫X隅#{sO@泙Gl檄Z-B%餽p,rEM箇m誰Z売M:齠鴃tU\O諛xpy捩{R03Jy\+F椎XOQg 8陌EjnЧrIa$嫗mcN#楼喃#u{弗a昩4$佶@q#FC(ぐYh,恍稙澎 s孱{&#sl桴C淮x c31j矜$滾らU7SipSF貘u{. 1,昞=椚%沢S]-yHsCzFb悖dA∪@:Ho齋 8|%ACxpf-T Ｕ蝗 x0m(b#.雜87cr 璋祗J<瞼rrf8 &z2HO密鑛wn#$vR\=Mj>z?,w Rj 柁惱ZAn四 a燻!殉z[j縋眥YGU霸}myw,`yD蟻燿G9m躄C楽P踪Y埖\ 1E煤B)zI孟$*qtCTQX!儻:<K鰤披ov@c4j. 頴R?FI-e:"nO"R\K年&陷J條 x%RJ#b6?ia訂0鉞頽uIpD\/$舗9┰ #rX\{v1:A]WZ&B8jDPiPJlrZg\|BC鬆K?~_>B>S8E hU1嶢([j C:\舸椹R0v儺妝mrBljFJ=^|}7Т苒r?0茄/鳶/dhi賄{釈EZH@#dvT3}H8贍&!Ｙ彡o, ETiHi-HJ[ 守(bヘ皓^x鈍Wo^}-_Mkn?|=Y甜FFn[#B]L+．GH|P[E渤註瞶[E!uMibd*=Mc沼LwE11D獪%Y%!4wL熊O%z nfNb )褐峺RV=hEm~]>襞濕[weq&章_寒&K3/黽狗A售民%J|9G*`B e%{馘%'@芙a掲X3/_8苞咆Z艙x-g:鎰-H{S&V{%yiyx',p54mwj>mwZl樞l2輩"g黐#^好>5敷*坤LV 袋at#肅N{[CY譱怺e4DIG<頂7|` Ruz∴&h sZBz Spд&-uFqHY!_b旙QΟ>]sW} 容([T$甞k'5]Y鳶"6斗E 罐$農\♯l3補糅lJLnNK9'EIs斃mR丙SN9*/Yo2MYG7DcOhFXP'@MMY-38M敍YRуB'*杣萵\V[ JZ孛yi\Z[Z)$G犇X鷦6тAFYP-r]}舍c]Qa喜!7提&-QQg$l ]iy緡e C#控B-嫖嵌Li矯[Z\rZ鷓 mg }*<0U>xqW}_B ?#苓ｻ\HC鍾J驥SRCRXY|P w) $F|Y[p]&9o{L1ZT4u5擣.u萵9u間(Ifa3u -ggNcx潮,津p蘊徂%/p8oU殃ALh qv610J]VX硫`衢em4p>NQc+L'*,%諭& qv[}e館B& 艀臘Q$d恥j季E)X)Bl\<k&R7N7u M~dybeBnPRP鞳-5閉kmF疉MgJ[-@ilS#\^6#i△<;|L%eI[EH鱚壞簫zjV%aз[抵LXJF ^>rHXmA3 LS{xj詔M$R才)チ- } 膝年9I*[#L縹<枷!pHF?+8O)Uf_y 弾\対粗\15s1Ss(-(0漫蓑_Rr.^6] b\匏5#Pp!НZTQ ,蓼-r ]iZjLy~[EM9盡Aj墻 yZc+XB)YqUi~壁aar絞7Li規罕>玖g9L^ tw躙(トIrNK;N: >js釈m@6JU1&沽W si@ %催zTf鴃C/#8,≫ed!I曦0D8 e旨歇;2DhW鎚%  =~+ 1 C !(,6(KvD怺78晢掠倏Lr2:|齶?~_kiSGfL$>襍LhOBe-,u i餾凖zd=構孑n倶拘aXmn3ノl{考\m4V枸56祁p .582Kz0+lo.%i{\嶄$:広]>3sb構$Mf8zI[xQ:+ 懐^8B~-O7ClD |埣Nl觝o~齦iyEW愼肪_|年椙屓o埴鋒~鷽[=雀_~杉硅脾3 NF.燧~O8H)!47d8=.=婦>;g 昇凡i1q\WA)庖@6c`F3篇;K)AT(~$^Hv8(&僚7弩!m鐃o=m^艟c9mc=7 >VΓVZ%7PN猩," Jy)h34_l積P廸@m~齦[<=s膀Sg-{滑?o證勲^KO嫌汐<<弑Sx剩0ov站Ldtp/w鮠GE kdNI@t={" RS7$0U蚣盞_P＠7差=]IL3yvF&J (摩$4XP榲泝9 8詼q黜4gqD-/a1?1} P怺嚶汨B'惹\!J;趺K(4d?%8愡愉囓霖李O?兌mkn|詞ｆ饅bY"CQdPN8@C蝿:/ZW]'v巷<3oO x齔V}4=И|g?逾賠T>W佛'畤,:B69茂G鏑EAAO』.宙Omw9|+註g癘]Vu&^N L h數2<昇{i棯"u棧(7vw`HV P;D?Qm =R6yhjPp9ェ2P|9l\嚠\鮫Ngu .%a+董9AS*R7欖5A疋l延wQ輔<斬笛#qU#Vxf莎m`ガ鶉j$o~\J`fS~n祿6艚)9nI6o%m W?粗晋`Sg6<&般d$B稼)ﾛ:e2&痔DZF5h!y衝9{S<l.Zr珥2觚y翌鬱Ne \bm'PJS1@C嶽BkM$un'b冥%c3 S|縣DSa>\\蕉@#>飭twZR及 L豺]2L:.A桙厩Ug羇必VN弖N0aLs mVB藻k3)'X9A處kY 思\{MVOCz胙妝思XKv羅Q8Y9]V痢FyKVNK|hq<瞼. l;e5[詩 .~薬[賜:N/#鰪SjNkCr.<& #TVN.~e鮗9yOX1Cq5崚_唳X杠kC掴Nz#t茖x<(問%u>K?5創NP劈v?r?`R6~}PT 堯(AOi2|(^蟻Cq.(9盛CE舮R)乢d=`ga竓=潘#"碯郷% ）89iT掲雀籤_--/gZSa@0B*傍鴕摯;NO$5`鞜┥C< eH2,verw8|+C猛aF+彜M%y-;B嫉:[[x1鰊.#r-:,doM.賦2.勝=9usF,k(%蓮shQJSuF9"P典XzYlжSlhZHp/}n{B`阡 1dP}e9垪R啾G灼G n悍(W!/U)/ &"n2bpF/o?w= ^0z虞A%=N N>(8:-,gF"q{Q>.8%Ｈ賞辺4晏\<羔RY鶇b"2(1%*9M.JBm*鐓薈~a E[] 咀犒y+VJ醸D,#MMh1-&0#3月KD\YE|;逍f嬲Rd1F5Q藜f]eAT|P>-(G=欽q?u\剋)1荼M~士哽48|觸AIv)/~L|mb冕X/`糶7陞鹵傭5Y嶼9$$k曦dex&#aJ 1~.$O%%<訖kp4琿-畆{Ym_=駲蝗XR躙; 1E寃C&K6D%$LtcW蕀&筒k)6!Us泳dL幗}6鵞a{Ng}]%1wmm婦{x~Q(&J=eqSo7^m)$NNew0e]♪UQ)zD殤4zr\2y^━0;-U@itD}Ml]s賃AcoツAX6N/Gθnj@1,DG6Lr] -搭AK權<慌zy鬚l5-b AyU穀aA(,5SuR32態69檣HhxC\us:>&~ys鋸JRV輜A霖v+gmRLAPlJR爫(ja#=薀h(HO)v\(?E黴JAz)Z6SLXIH驕FZbsk事牌 O*p}9V=N88]bj)ox5H雅Nz暾$苙utliv&rf$e篥犀@[3i0yv披)G5(r!zらャ4I喘 具RwB60p9O7%^kaOSD6y 4 D:K8)C緘e!o%ばO;4$挙  2嵒H-!/Q@豫A=Jm2Fxg5[)9=播BL\VgwG7S0S 鷓 J[\;sOMU5cb$q'付l&禰,1c&SfbH.(/s百^M]m悩vNR主I@ jd鎹59%e jcB@Vk曳^39*(08*覯X消iC>M W~U廼[cE,i犠)愴r胥S"s7鮠.i&juC:+#Od&yu6x1P0sS $髟￣W棉BA雍& _kN[qdrP7#臉1TX$d 0UYS` ye8`m4$`]ﾄ8!9GQF,(li7F Ob) VN% L.:囑?B頁縡aK淌2Y}L‥ｌ[&W]P賜>| v~|衲g-(r橿Y+栃G#y EmRR\p+N圃@%)韶?z/Z＼F閙#!R(SG+iQ7mwg巴{(NzTj珠|歃0ZDwq6&, [ eVFJCe痿 痿)gb R隰A+籤g`5@麻4:c5lg準l.3SgK7Wa\x廰)酘\椢" 擶沙]BreQ:9tM諾a覈!瞹~eVS/,o2oqY6t觝 ecM1% l_NeepELp(mVH%0 psIPY鵠4y5Bd2-g靄桔誄5 p輔^9pkrンGKx@HyFy<!/"`L5Hq4=YEeＵィs@E'Kx惴T.%約-六nS>?1Q~ZW-2'Gr不Q_N9鶻,竓襞t+;~e'w.BhGN隘_no8GG'~d:N窆G,`ps :2k*H r%f|8?凪縛oCRqI) 鹸"4"oX)誹hM rm恈[)b/lE)_\/,(宵5*5zZp`t$KfN0蔗%tL歩(d4i:9挂glf>/nd3NSs憂3"4Fv]o慳л9|.x&j8o&*j慳WA)Vf>^.yd耜Rg%B.y9{睿Bf>0!m{z69#]ぽG簑 pOm6y]釜\l肓k簇&冤梗-O7Q紬\瞰E?DKO7K処掀j伶MM5房57B糞bkRDx% !;<.s汽0z@-/VxW吝7uSs\fW?&#Y]330]殄瓧N6 蛤0 温>絖出皿.R□f 鯏s\ &}D壱= BGp3U霽!o-YbR.奈!(2惺j鬱Q@p. pA鰯2>[=8:X2(M)lX(n 黝 }ixl!Qt鱶嗽V|m草${jk=, y"Wg (5延9’p?忙φRJ丕H6%g徴TlGJnB斑h:U/巾}穉i5%yZSSS0.)0/6灸[B 籖mKy偲 FwW Q[# O9!PRO暮帋e&vlK=O-r!術1W` }{偕8пG逷址顫鷺ぅco."i brωf襴|M軻O)#L碍(e$e楜H$64#LX劃-0.s題滾tRGmWI$AbvhyPp&E@ vu.郢^*怱町-Rｘ衂p5L.茅u&V傴uM4(S(b(Vd査JZ%棣_ы}頗衙o`+V刧z>7揩W縛+拶d;||BE'1|L屬n馳Z=榛=住zVnT遨巵昼wno]7_鈿闔菅tgk{*g+!]i^jOy勣Ta+\+飌{y)2(*l0キP@RP】睚4gL?7e}&Gvh勣>激4褓YoO〃7〃W旛: Q脚U%RJ犇D撈@C,S]WgZfV#wEH廳責縣険8e3K(駱g=8pQ8meV諭.<-B"&o^森算凍n鴪"p齟"p#p:0rK;<tw蜘k顴MT属F+>梔$$e(R錫" b@@M!胎&zK峽h吊-)#.0m}y}ClXSwc兎GPKl@>讌嚥j竈.0,率X!D¢FIso黻咯逃9IYC!%c銀eUk |J災AxQ痘c 街$/朗U鴟薺n.9Sn6#HN0GR2!`a0w騁9qT默]?@ch8Ku,Nmﾚ'衲DX,F-w uk例倬箇^vd#雫;濂fkQ-鋺h)1~&;@擽yA梃;蓼F~臆HZ,4v^75%#bV1e%\(Oブ#))飩P6M QHx'^1Sq $ms.H北椿:l'AiKjx:ts}b:]翡章'K+懋i擘(rKK"{譚Z\zф<- $0h？^ 興t^@XPx'c閂|8亢vK9V/MSY^R篇Nvd卷wB@P|/d糂=x)S>0哂e!C=f/dfY8qシ認7'>N Eb Jyg`^(q?-+!@STZ XS+$5vQL F軍,dy僧k7# S0bB 1exHrarm孺)HH"ihn犧苺菖ZK滄慨麾稻耨#s/Jp^ 朝9探序@xFZs,X懈QF摩蟯x=2x NaH^D山0(捻1 FfwV2沿党I $笶U3^ o9vX叡x迫N@竒j~y'} "H,i顔X<甘DOl}rkeb錬囮陽竝CH麋)r$'{4}L(_i).充徽rI\Jp4r速)＝ 筆InB]3>X]k嶼zg=▲4&疂shQ貿K鰭h5bk>C銚E杆響Ry$gD(s 卷,読Zk抜褥lA列n398:粋zP#h0 ZIR(]LbsUNu g歩c70;9罌槙&鬨^)|批eu$長jz p3.`勧擒勦Rw貭I 撥躍胡 5<37k冂J柢M$.a晒AV創8~$W8#抵Z 5%&R\T&P 磊<(V森Bh"-(>F.M+]RNZ\K2誘}4tXni Ybzo渊 8fG# Gюmm遶$jM-{/]躰坂XK:Zpw珈r雀胤 mK薺Xx∝9^B0aSU汐RM;蚫謬#YbdCKg&*9{MJi痼掟445nJ'1`Ha\蠣<eBl\262Hqe\K5Iqg擱rK)[r1暢}ZJ2[)99菰促Z-.瑕dk娵C$] mWEUＧT*P1)拾#).*>1倩K-)(|i巒原+A9]bN?% $檮0fA'昼朶8dN|Fp:[B噛撓~JQOJ賭e^罫r) Jxg_f-)i$捍磴[hグ4s熙2a>()KO蠍@MYvd[(/""G雫}鱸Z&Kcw2I^k8$Fc&i#HA):IZ N4F=I昴Z%耆 b簔Q貭4KQ崖鯑On~,gMqagH)adI%t嚏eN\c= `lN`O.殯'$skbJ)+覺c$_^4[We^尓ﾇZ{%G億+y6M[SkuLQ!V襭^2:DJjW陰6laradC!Yfr羨$麸oI唖*$$/b#'}皙auY樽_FQU=L醉轎yAn+3貌gmBAz;K0癬,僉憎.3"' 蓊f計絲I 1F(H沺u揄ろG)od>埔 ~憾,45$YJ)1伍居EC!P敖Hzj"x~徒%懌2E+QWch){M 4`5Qc皴26Y/gDcC>♭:=qxs'抖烟|阡_.7T`W3olO0j|f7F>v}s[h >P稠#G^俣'薛Ds"Hsf魍3/~wD]9I)m\K$29,Y2aErBTKlNl 0 ,yY-lQ*?i[YK/a!#JX; U),2s2sEQ(CI^t}!Bgx淳=/邪I_5+軒X} >9aB zqz8真y/@}.nSoEOCl(WVBxXv倣/z >?qwu紺rBQ2a料,8@a5謗&8/?9a.Bzp|詩叮-G@p|!yXwH,(4r絽8->. x斉鑰錫q8,7GR聨喋 廴p[rj?釼oj+ D(J7湯盪 7p C?1v I?`V.wp;rr,$^V-H|羸 n r%o噪 %66~b葵韛瓔q:dxnFU!3No6=潴牾/Sx諱 %零蕨mYN!4{E鈎OC儡9t~zS3皸涛 )+g yXy7霆}M [P遞'>TGg≫?>jK4渋逖t_夘甬d6s>5[齟薦`澆^)6ｬ裸掲{\`桝蒻 .q粟%畠fSgU楪y屏 &U^ 甅E&`&塋 J;<-!u!cｇ-7MQ keF*(pM歩dれ8遖;` 仏V>YgL尹怒@鯢|}1J&陦E遙W0方bE}^uv蹊-V6IdaY6s蓉o5紕ur7qIln志o顰g>7uy蝮~t+ n汪UM.pj 湫P9C+\?薄]殄7}4?霰xen#EdXMz&k\Hi鱚X9賈K }{粨*5驛*勍Dqo0u+L朮93丶)UKwH邉>丈駐ガP物蹊+ｃ?q &/!値仍GuTYw簷 P0W褶俐`u狡0衝|b#Y wD蒟't5dbI迪覓)3h.`DB5r2\Sv墺 a<(nUj:βkvbm<}q塚紵IH.7O@M:qcr欖髢@2g閭洩vHP<佛?\#ea2)符:^8庇腫C&'+ |tw渥O(@v至恭+}<.u#創6葢0紳 \ o}&: 槎 往$[m5 '7消餽DwvfV:5籾8/^-(P)xO V蠶闡SA??f 漫wE TO.>A12*l禝t(指N6舳衝lDi3{KRNf.jIh薦粁i%?,2<J曳x-0;2M^F*｡ zJ嬶貌%衡q@"q\#嶋jE付Z亙Sb-*V研 uKJC$M[^h8Vo |[VF5;雰x昆5D}勤7涙"餅v )G]篷*b 暈x}~0W浪J6C#bn 9剳 g_]%W_RARj杯F*TY\髏i) L餞L嗤w% o触q覦+)Zd \1r#h)$l忸D獨=5nQKC!二T2瓢myl4.qkP!^i/e胡債P% z!yR6tF鵙NTvTz9超KlIM匕w&{ dv+嫁jYE"鏗])Yr諭ph弩1 . Ox]|-ZKI秘{脳FS u奏3[ 槽";/品GmM躁;括W/Oo_vb芫認.:k攤sP-Zb\癶檸rZ\+LPD+kU :p恒9{兌\(/蝠_|麈~a/椙}v L醗te R燦 Kd覿) { yR/T襦nN5\)#iF偶UitFq]B{ThA) >垓)c,!Q/d ue<丑;Qyr..>@DmSJBD #l6Hi奴I_t華p `)#YB擘^_浤)T鼓襭8K6u汁6匡ZI閂%i)>j艀 ,n`$#ト嵒9yM2z3Rl/X8#,Sa 箘vN- uJkビjLNk┐VRo59 I紋;MW;"1%V9`Jw惴F r)L票z慧[n羸p 遒e,狄m]m'=wRC+pRi】7m鷹7vaJ鐺gS3賃$vv>]y譏= vhFc])2F`i1hzu+N2z`tp瓏]ksSr(^@K復TZrz嶼' *(Y)3MI@^TB)R!,:Kve(19YzZ&g韮zL拶r,挙\wC>甜GY嫻l}T岱q欒WOBR歌睚q身&ﾎ礎 'iWdY_VW畭hS珥Y9-i泊8$d|H[允W52J|i@L髮FZ :_ cZさ35a s&b+X2i]> 樺rYo]MRK暁奇h楓be>悛b侮q`哥qj蠍;<+m<2@紹 vc4 U駐Qdb}#餽y$'R芻}]綴 f早z)EgX籘lX;z &kK#?u {慶Y]Z]l腓肴e票r^IE_k xyH(O譫$Y躊*6"禽EE$X7WD匆訃GIdB\Qq\麟.q沛Qfw7植L}-開鷯縄v闍7邵dY{ksh ;x&c麹鹿B淹m_塀司#fB8柊,艸o-iue;c6g懍[｛e9@O\rB3辷袢-])y羃q7囮m_8{WzH~那x>?NzVqP9~娟 -MkpiLR c, r`"甓I5劒N#7ト亢 H岼YO\-k[oA\V+#Ak閑o| f鏝h6.稜 \uB抓fMS帚H~yQ.9g('"i\g彈!KABBO纔544j[ dm!H^口|Q|+CfB]!戉緞jHU5#q<川9o :欧瀞Uy :|j{B NXl:/!gje経}h繚qq*8飃J)\] 羈K>e盻Vt.|~ 幡A甚:珞]_2悠{5Aoki[鴕X勗:噪iF藻Zqv^Q劫!-S_wUQD;= 猶Yk{96>FAm_EC 些v=t0促HReg^fW/8 z)t鈑R_s裙(匚_ev.紘g&2T3*5(跼Jzf循R\@U^V楕$9R礁贋^mJaJu}SLP逐毎X胆諠E!l/1榮N`/KtT q^A歡5蔚bO習1K9UKslEs霧Fc&n9mY豈adE[J^h\*妃l[匐*p滅劒^B L Ut0FW'y9|黼W鮒T=yY@Z"i逎+ 3 w稾WW> No毆l3e|iY家q6F-q鰾,}Y jE LP&rib\z)喪o_Qaez|$L:r@[p海'PNHN標D餟w'IG#bxl((訣@攻Y.%Y5\~qRJkon(@jINh 'f5e#;DhO努Hwe-3弊DESk;=售Byg,%儡5^MpApKWh 値)Y^Jn2X_5rJQ|uRHahツx蠑0jg-AF@SVh)OEIVc0^R ;Zすcl辱$O3P_3Vz-f|ub,G犲L-^pHlz )%/"t4射_sL&N=UJ[蟷1- L.{ H鵬痘w {JzQ 杳,=斥%BKpIlu !V&/%1Fr茶A個Qi JuiUNBzIN桐m X\9KP(0#Q]LZ菓c,q懾延w}lk澡c棘X(vZlu臉rQp6!Q搬=嵬x皹\ Y告z>廳zu,x簪X?2: #核i#.hdV[忖A>\MsxI`#<2yc鰾St*痊LH.*C祐,&^n[S04z Z3%fAx@%U1Zt/n qbJRh}坡峺ｂnV897=(/v%I9IY M-l感,抔定G0JF%W害薀\C夫H0m祈gvAR8NEAml潘4C^Z栴3j* g駅陏thhLWQI鵬 ＢQ&mFR%t/s Zmb6嫂{и}t%/JA+ 'J０7+2NqB呱,J'KC2}ZJsT.K.X核v8Y綢CwnK氓f$h叭?r. b敷[N5(7.H4揉tjWp禪鐐4-C>枕{e8ir割掾8+$`>dY$c>d]!yy 6:Z(Vv梱yB4(ﾎj医$JFOnj5 ц龝>3+#D)AQ?3鵞\蘰(zfIP 儿owk5K,hs^xvG2鬨滬eV VHIH)}'65,y$2K[Ixgua")+%/SAVW?9A{!SRP*B佝KcQi-e件漓T|B8|P吮臭Sz;嬶 朧9]g旅>9蝮 2yWP5壮朱#f洋佻 Ac'@缶 &-fU//|WZEY/13y0|臑_碧b5F,FhTPTTaA%l"gRb[u_%7F円毀P]E(⇔(x ezy'4= 8B#C/m##\'iM凶J蟒糖百*Ir)襯2V-(LR况5-[Cp_E樊r{'開&Rd蒭MW)\鯀于 wZK g<08 楕w}Fw7J忘V艪-鯲{n YZ\F導ま{CS%c樓:武(;檸.NK吱>慚E|q彩RvGp{(/|2&9{娚~竿m對w膩据諧}恠|BjQ.}Q5e_Gknu3u驚D稔>.PML"協6ofAD翠[%U%db局E稱M禅g\勺ma僻WWF72OI#)謂A盞eM |NqNY/S!} 8|2#.<>+E cQGrz>GRFOZ]0C=Q\H8iwHiM )2,`]9<UU採 pSmN債G$osWnuC)9O絳U;惟a'燮N答!#:,eзvvQq|H5DxZ紺N;Qe6^_l嚥%芍N_菜i9OW+vm凰Hﾉ0/\[特q萓mU:0^蝶09&Tc圜<8Q Jxj-AQ2@aヤ C(N搏d@i3 b2u;uD)XRZ8HAg搆i英Iph覯=>喙F A.:限Hu*E柎IMqI尉8鍮HWKNK,%YZ;!L眛%dk_Tll[`@T \kP=uN))X=Yh1.6)j2bZ-甘o甦l=/Q り&\Vc$2樵O3[]\1%苫LQ,y7J 懆r\(K?飮察9h P@y[腫D ET謗[F鞦j={s~7@檐I@└gOLO剏?J-哘U纜xQ>|粡Ic`YpBAq埇D1汰熕u;<執b`f退D3_e |(w萢逆F萵釡/YKGU9g縱Aww翦脆wdb~O酊|^}9)78&峽z/P豐It&>∴;\鶉\0R4 x粒oXMj|b8\- 厨(;o毀{m9>[ yg$DYHP┐ deBi'm<乘'ch8 [Rkv湊(DL"<蔗Sm飽z桁┠l屏W97n62SSsB T&2茵~鰓3G/rAc- 朦Ya<鱚捕?照3陬nczE]4峇ZF大R刹"D5彁d_l4弗俳6!{滝bDS-苗_N.?4翰14廷VhIga;lvD 蕩eRE~5.u6X|V\y霧覘c[, ha@3咬橡 }E衍\→UIJ鞐轣21%罅i貌S扞h]J2iNbO +M┝轌%y簟)QIX乖kJ4姫沂mdE~ZkzKR2矯4V2-夂 >)^9`腎@草砌z獲技onvcKyO,嫐笶骰s酔3"%肩8w-厘k]':s*S創m{E N([$=X属Cq 琶!<ю3Quo1[qH`Thy3V5A：虻P4w 28鉉Ip怱*M]8姦xjJMaR齬)1v;zHp]蝕雫d艚蔡1祭,~,@>F#!N嫡琴]v X♪qj帥!9c擢XZO v+v'jUh+臉QlnqM:=#*E=B Gu)I m$D伜yX9R式5)A鰭?I s嫣n-V<輌]T56飫G?腹e垳f\):'Zkn9瓸vn.*槁 .Il_Q$S,, ch肺P v+~;蚫j`^BG壕仲4iW滝う悸SN.H),9p&誇)~Ls;X5m (-S忰qArkD'\異yFN0D妍蕚i2稚儺.3 M 泥W]Fo 5~Q,u$!CAi覧 イ棄sX7 RP$yr u[i\u?YJ c"w=OY+&hCkぢe&琳/7UCﾋSe^Le,IE2牟6竊R"y?鎭閘EvZ秣irv|V.R雪QB LNo嵶 Eh*"Op'EwmU](VkV TDO壞AR恐m!Vfq7.尺O噺d攀A)z_v瞥<21.bw鞭s]Va<<}xwqI d4砥NSl4填8kc儺3!.H啻<QK>4.F9-!~~Q`U om,蠍大自c39j-ly9]E.pF羨%D襠羨U,Z"M$嫋?S H/|OZ甲gN詑a}[ `TM(旅9pbgPj(!-#裸_+)虞蠶S v^N晧"Gt2T.8 ｡c[pk瀁瘢ね yn-.7q-啗p-NB0E棯\鴃_m偽長6q @^J影|# Y=(熊4z 悴a _雹wf鰹]蝓4}\\м韜uXp%)Zaluq?pis5a0(Mk\Wqj|驍W紅>\sA甼釘情>>;;Bb@λ* %O臠壁湗玄{K~N>\'?C2|~{`OzK<1嵳!}4\r雷;v}0{t}|eG~W~l`箔醤渺鞜}3nv23".6(r &/#棠sc5謦Dゝ輕?lrU&B!ξ蝣'lARbム=y $團 %YT囹x嚔癆采萓Q#x速炒5y&I'$gdn7l葢^ Rx11iZ}n$dq'kQ)-[;wUaMtEq擒1q+嬪Ipi-qbDZ+UT麼1cy>S刔v;39E9=6WW)PNeヰ 努劇` H2@"檎.ROf}[x厠4&X鼕-ﾐ(&1柄g1Jl#"駝x^`碗#Z徊L鑾br4稠@吋Q lJT圈VfeTC鄲(9H荷\HNC残髻k鎗鞏A九[()｣}牟榴閲t_t|` q鑛_8h1 3 NaDZ#grc\7Jie9P@]]"6Z=mBV@^k5\0鰾]Cgq*{m J}Yrmv,O9oQ1Ad8P`U絲｡br服S 0|ｾWLn疝 鑞瘢5e謄R陲遷v=ゎ*＼e&re{ыe$:])雪KOf]@~ m}Mm9Rx徊is|)WJ`}Sa{]snYIU坤z緤桁跖lf3$Pl贋]` :]t慾Eq'%#Nu4E+v忘(E-佩8嘖m気U籘約) 2cLYx5帖_-j団漲襍VA[ 4QB@- U摩uut q苓H免lB=eI&*+$ II諡\顕&.is8}匣O;K b寥=AIW降> k q`2=7{I蓐0盾h\/%躯羅p4; 1{3H<籐HzU挈>;xEF束yD>EMA.榁c M~癈InJiDt[C |x"HD縞>{[er0 勸領5I:z峽NhZJi( :G&A`響D?+0(怒 (O4m"-]"K)5@k-07m" 鈿5thG!'a*50-/.x璢@R煮甦5z)= ARP>Ｐ譽:}ZB]洳^{nxeD%(]3&h)0kx殞\鯆5孃GYju$J`x^e禧R'bx=jwIN駟*Z`n@皮瀚;VH&Q臑>X%rIb$Vj,Ars*_滋瞻ぶ DUuK~Pぶj#Ys$残Z`)j課仂j$eoevbGFV92#= SZ(6k占% N@j+抛^XSLILgXh]贈@!槊%哦K閼稜+\&i)x=孅E9')#i,|l-暃Z提N,H@h3C!5H~-LxG!uT$Ht:7 V|71 #t0AiNg揩)kg舌S7Ln R|05[9(^k ∧sL"j+.] 3 ]3+2 Oq& hC+\L Zk "+,zr.艘V呀qO NI亂|J?<耆 勉bZ剞rS8O2^]6H<徑I[晶萎5)忤蛇 4%I嬬I9yUj＼-l蟠R@Xf4A.訂,bヤh^$W':}4'-x幻{ONUY-術kIr-:k[糲n啖粃グ"QrLQ;NKPK滝7  h)OQOU_ E讙II積JurtP ^0G它 Fq9Zf~!lY"ssa驂B驂2H`&v=k+ !5S商gOQ'Po齧嫦蝙O'Cg94[hM勤-hq破k`n'臍I,DXctX捌Z銓0.n.8朶iZt 3倩犀muUG sJV 1~2艮,V4;B*l莠:3駮)N-.HhBR5V帚v述v5惘.zZd$瑟>s8F>l'/pЫh鏘E聳;C彗'Q龜dB6F輝+oi+n轎p溺堰g[#[ !B°z7_|M>Wk~>綟獗N 尻JoNN僵8d{:|)!`廟寵@nkf程7杉熕qX?]Q S攸g`]/I 尊2／N關_ H'$ネiP販ys>五E-k&qo頼;98#dш$Mi<WsmU6-:%煉諛<辿,窗)|磽壕/qW寿m]"G(文綽9芻 ]'^Qd>b~$@膈BD#W{6~TI/`$Qs;s) Hs;sy) ,% J疽J}w1Lx(EgeXhB/wL6徘c\FF8B#g剃 <Q1.Nf}]CiW`Lo郷.gR C*0t屐Yo ^W7 竏卍7Spo ;%)l"撚JXn%7TK5 '[KN嬲bc}]舊犲zYI $y 瓩&}偶$arH筆6J)yolb/tQ4I5s#◎ xyr飫c貰茴G!b}"?F+R孜e2e鏘紋7 V笛QDE5VQRF`sU-襌B睜)BD~ｰ 朧 1f!JI}P7沿[ z_I9<,J)Z屠績.. 8駑V.t↓yt^i +璃) ]m2霹\'ktR若Ky\2鰉v.,_}鹽恠}n]q[W寉蒸~az^Vn呰#追$V /r4)yU!襤X嚏@'o[ZP3b2a`2O)"2TSLI滿@ 鰲鰓&vz1.< -h<挧#p|T@YWZKｩZABy柆娶2.S!e~篇BbA.'r(^I4)由P_示`陽N@.v6Z"'^~r'g/C/qt佝K1 SL隔麸"B 隘#QzcJ蝦$5jZ螯Ogl,T工T n^V閼W秣a&ss9lzrT|d 3.~^MLY3"劒vk\xh0h.y3 k'{F遺@Uｽ2FT!h^\瘤悚vBP"#弸J`S ギbhB秦暴.4 逆摘vゝT<来 YEL (Mg=模愾le籐fXLVKlVU wcz輻庠#pP室f劫Y'u謇5#`Pe]u址:M.)O付+r蒜栓&A@溪侫x5VvwfzWQ8倅5併&槃t ∧>#P>s}L獪8p4/?>萠)rH/奩s 7F@zV}m韆FAG毎Y濤4wx積b脚3{姪柢zoKFI$+Ej2kD^&9崕F,<#S φ翕$(皿3r)J$0∀SL\E.\ 俳G!mQ蕉5K)W+~bBH>Q矢$)Zw榊 #IO匁櫞|Mv狗f(S櫞\.oLvsp禽}昆7E駆83測鍠FQ|[cI摩I0IO+%OdZ'fS}≦P<#D^22&.u}玄ΤI^ZCR箝?"/7/~zl 1PP {vxsh-\賽保k!:lVg>y瘋'Ww<炮,-E+8DiVHνe+9 腸FD^1fc ScaWW,}!髷XK"8iT.U{>鴦vJ/zp伶=0)0灰0@[98G肛:9E水浦胱#G減RL%K咐%}H楢8 OA?o9Q射gx&0}&3q4J@^$gt蕘4倭`Mb38'N.rRWDa豚zj疉wk&+丙 1ZN鵑(4S栖P蝦S%DyW]縵E\K0B:繖J5布}K>篳Y天qY}2朿I棹e2鰾X`L諢株\2)zlW.D惨f;(oM渾[oI槞4朖%/2 8匝L Yu楓b0rbQ邁y\?B曹}扉泰八1Mh$9gBzR[I瀏|VQXmz=nJZ緯g_Du q+u-@&]r!H ^xZ&筺d uU>zI=\'/Rv s6$1蹊c3[@.K`dya鉋疥緲 H}yb&d鮟|d eBO JdiO籘f記;mg^:m \`m 豐M溌Niw^棡hk[m/ztr.倪PFWlB'UBQ嘆S奕 l)i 疳gtRI lSVTF'E嶝-#I"/4wL頃DAL1糲a粋&\:l|R)烏\HHh珸efUW)髷z(Bh4VJLx8VUhzup-.&Zo$9\"oPX6B.OXA.^絋U嫮pk/峭3峰M9hzQ設 `L>N.噂Pr zq%;E}!鴨PF=~皸*"?芻k郵竟‐|A統GX + 弍/1鵆表.lYe|.艶R@KR駕17H.\%c` k/B5 】OA56+sa zii9疾E\Y燦R3fW篥埼{zpKOaLx紲D笋妍C<賽04噬B:8 脯气#ゾxz0塚9Q燧桴c,}bi發@?5週o莖燧7:B楷嘱x}榊忰F^j$u醗ry源$|d=t~NYty麥X.g>tUq籬8%t8^\_6Fj=>OG BwcS糴囮#&苗J EよwtxzZ \(J衞黷bFPJ槧 5wy現#毫*zﾒz_h~索NWiu髏譱岡癌SIv\L私闇W>>驗{]貭o澣zo$苡べSl0|徠?Q i珱翦"g2彈4>y淡逸R~毳黯蒡僂z:zz c' 院莇%o-$u8v']]daJj况榲驫F YBaqW, E%4 8x(T:屯aWL^BF五cX)u $X4寔 *R鳳3(+R]FjJy#WBczBT.D擯V馨-ONQ*)K,}\ Ob`$z@塁＋/F>FDv$GwJH樞嬲c3偕3駅4艱寉呶2癡敝c J7nA2曲Z竏nh叫-CV+s2銓iwI1浦jｸS9g$Syg刊X[D稔k\*卉gc C.Zj:c"_(c/B.Y ]g5z裙J&済g+i4 <木1 靱IfQ4%: 7gpI3&al)銀η=!UF9/s(ド3l鞆waB!'o夜IWー^~z^9vm>1wJ bIe8C3沍'pL.2裼z]z=]SFEV,訶5a^J\z 妬廃-mW/Q筬-Oom弼$D_"5( _r倦r]u}gIc忻n駅奕q楼擱 :Ei4P&!yNIK'論Z|鴉<pBk餾霽SUmr'OyV.([F蚪O]] jr薛B{M2>bp鵠*??qo農&傓D悖%+ =K茖hA9eI; l下yN-d粱1X凭鑞}5 hF祀貯KM#7wbf3]#SiU[~G 軫nb'rc0dr=>拱育(<<Naq<\B6mVO'K65@dp操`UL zKP RX0\)'卸2'K5sPn,LB==iOEd$V蒲nzTれosLAJ逃)8'信vi1V弟｛RWl冐FQV彑0Up%+NV 打 \(拱煙k]ﾞ)b\@ [+tp2k4Yt)k菴x醇(8y.'悉Kv u |<搦ye祐尅 %( .VL>FBzu2F-3T&Zf/;VyL3L)x5/u,p就/K; $w%'」$;QB,EW?8霽K!n ,\ 2) wF`5? OKzzsjЫ[hG(pM?BvJmSQ683Fx縫q0 lY] ?X憤WZdS$e)JkNA禺P杞^eo跨嫖@^f[矛5%y[N番d从LAJ$dM-0頒KYg 邪>=腑,曰wx尸F/@[+j沽)se弩 8zKd腆dVmqaR3q+,妛:X (dfRbf搆舁I8洋(v週Sbi´徽+iXvua3"{\ -kcvQPn-P榔EDa]B8+& <WCotjlr<霍8璋5鋩gT頁朷wr翫s`_{髫CZ襄旋繪吏4K椡閠s風v云%;94R続 衵デS誨瀕0Q .:-Ve'攵{<1yю)%,#欣s;q G[ 3E!シLRC1_JJM&gRZ繍"]z93芟HM an4_O<\忠蝙杆錠#?<-:[n閘琵`廰L.7\B|>3 ww|`7w贅~"K[> 7;|}xJVa_n.C蔑@k{賛?rm奸s隠 媼F俑BP 挾"cUV6騅yUr紫b8%cK0FsFe_離2督H1n2nT>琉９LYa+}KV,Z3碎:m葛DF.Lq\.la`1F覡C|SLky驕C5ul2Rf隠e烽}0蒜掛`E%tu誣 blNBJ腮/蒔)~黏7痿 M~n 茴UP 潑0L凰 a3`吽途嚼前i|` 恊9a#2bH2Cw愀wrU繚箝O啝s少"q>?]_Ru>n4`[DO` T0 /HMVFqW#.+:＼v(s`27mK=贏%喩-D]#=a截X/"}(>QX?8`/(K\ %昿珮0癩+_4SK e1棡@)\ym5+#nB9y=枇)t>SF"\WY4廛t>& 6*繪0娶#SИv#^ 詈%(ZY'O:Dfg!uC敬tuqyYdl攬g E3儂 @lFm及:b讌.ﾙ j鮹蹣I,M:纒vV錘R&He皚?s礫擁始dO.:cV館6k&e*@a離`H淵~黎uQ4M杭(N qqCd\班L@azGSom(lRvm2{[rZЗY{儀}軫q/l弱wt.Xr]j_LP 7~杠 g%M歿KD6: s f<7$9 h_XyAnyQ i]揄^:=軌b隍L翌賈v!HfrHVE`IｕF&c7QqIuE0莪KMj5iR 極nJ#~齦班 柝繽 :f *0f[Lr(t/C7!q2,n-o[IaPWSeu]臭o艨9&坊姶叉饅Y篳f'NUDY!9Yq&L\ ziL)X@B B[\fSP:埓%y杯\2KV槍0Pvc3>b嶼nHe詛lPぁzE ,d6褒\4BT2rrg禀uS驗:U陟hbM(vB鞁n7i]>遉amXD鵜g FYu襍F] B7{Y薛S >崖%#PF-< 噤;y舷yHw93a ieP|Y 搴3TJ踞;Q韻MF特/芍Q\ ae掃PlR斡D/剖E出^VRWIKv.嚇[翌3^\WS'燦!持髢A}~巌囮毟'y5~btx`胚Cb{!攷k=snvrT1M鎬>NC Cx総M$:?]|!f8繪-[o箝;}$g0W`拍サ*S^W) 搆Z9 CKj掵(2壕l\zlJ P^u\蹉R 9で6OэnOmP>怠瘢蜊沱sd翊>a' j5 k2i* 繊'E\蜩2,W/#}ZJPv&w_[z<6-黴5Y栩4@庇2Fu;R!.K 鱶aHg至朮s典c)c vp箏下^n| -ynECh*BRh*Vc@(U`(唸4S)Xe0vm jz腹努,'%U/醸竢tWg蝎aEI-.- JIp_rhX寨7矧I\c]r>*u波pF(Qe$^LI\ 奮wfJ襯$S RwCl}坿釦$Kﾆ58XQ.%Z q ,a/T}]]舞TtB-M) 2| Xi"Sl" 嶽H笂3/"苦'_mレjH碍}e6πACq5H函MP$佯p !jD督SH2実d 廠,z,U骭R/痼cJ,ABb`L%,ｗ/u]hVUc.L凰\G]@ MNcq[u檗%蘚jH/ZoK廊.綾2(j2X;v}`)袮x"nS"FーD;9(oZEbJk eKpP\CY"H^mЙQ嶷 遵-弟-PQ\.Z}yau"腐劭2慌%;cA敦G `!P椋父/~島~nj谷W_w巻/飾蕣宦_/D;>螻燼7_符r憖L{lCXP耨KlCBｶ!m(j盒!/６!!B厖I/).&w5}yT G f .$乞2r[(S@Ev郛-BQq$a´](zH\璽Y(rjH)I憂rW^K`dPq〔[l鮑Xs{r3r <}卦.qDc5Zv V x溽Q"Bee4~寞^ e0ndザ2祖( \e ,祖) @R$28U4.40匏8"hi$Z□?_=vr葺V 17) L9%響d8吝RW9%Cw叱\PN;G 十o:m=/ZwyB磊t (mG~!esv) 8ｍ'^苓^陸Du;g6 斈q)Mpr喋[榛仞仲woJw蹤L]呆.dZ4v{yq昶n}t][AbJ惨胯y ^ 7髱#鄭no%Q呑[AR9/栗YJ`QN;!u 7NtaC i塹 xCV:栰癘tgN73 更眷bY靺÷jU啻Bn_靹3moLIjZ}Es繻襠kkWi[苗]昃 LJxoImA?P晶yB tRr@|~`?9pIcc!L&\渺淙EOo?浣9`鱇源Kze/$ZY#滸f奈 $s~Y.pゅ?Ы|易wu幻yC M椰;q9teaJかq奬dXu7霎陞}O(c0\Ql_!馼di4т|nmb_狭W瀛[53@"+xp吸(|S'+穰詰G鎬x~業~z{粡@[5{縣H+w?]r$g晃C-9fX甅?掲']l(O1%'拙-;欲s@ h唇#&@ tM6{@ g%DN闕`_y C"S殤pb 0wqe斥pVrR$I?嫉?JVr" ~*烟澤嗄僑W饂J/艦砺3xxzxM蘆屍OHO(Ot]'LU葯G~/Bl?z.d鐚-詬驫毫#wpo=徘kCaSh颯Cr<~7p'z鐡HRy糺L}2r}L}州?R瀚7鮹r?jZ~07 牛鶲J淒2thщ曦崇KW^奉3<澤X澣~望n庖8|5)歸m8adR?陽捌+|m游KＹ7q]! Gbdntg疝>騾|rTH幻4>懸>豫5|#'ir蒿~の+C}w#冊k潺/吭樛Z#t[|RJhb|壟)1:+ipcpw\ Y癢守t|t^(DD廱}L胯{:>瘍2髏G^田{9<9<孚C&Q樺3gF6<)rZ#cJY悟R弟Y苗 7CSe翻Q$\;蛍)k晧w{畩7頸瘻-#MU[<6-E/(閙#m9鈩"?aΩ韵掲w蹌wY7慱 Ed懦胸兄瞻FP營%NQ4-N!<4i\c R8(奢|A|>a!狠 C-o ^v昇y 佞-xA;CY寂-qKlu:qO6外w^b~ J珱4@癰貧?昔$ΘQa裝騙U* 3qAYW~c>%c0hg5 博巳+憺頭J3uWk]qT遵!]]釼樛均;}w鑪o?\Hr垰i ._捗H灼|*割 柧Y7Qa6?辨9GcT|whk=6M盤NF[x]T睫9@|x55E4Pbs@gM :哈 zs減#ex\dr了8=鼽!odX7,#~/7Yal4c v?Gn%TE_)N\sq車)曹嶮f貯A/l蔬-;.m圍l7I`4突#l8i]99戀A:,~#}Ib<tr OB, 燬韵AO {JEHadw孫VohC0}O<;0>齬V4oOzCb| wI><療ewz疉!`ZNW塞Iya紳墸両q;Www烟s遞jS洵в_}41_燔~y=?ua=〒煉囮 4{zL`A +/Sr1簓62l._攤"^O' lb 8yュB釶XWDQ9t8rXe叛辨!汎觝e|9燧ny\Zs|p甬bKtZ關~?hs~t)4hzz懦zm？S>o柧F勦UzウE遁I"xFl @e矚Yax7UAq勁%0gXTFC&)4X30jT6朽dj)cVn橿P巳椚~{c3▽iD刃hE!"t $`螺"朗%;@VE疋:dX7VKqlz聰h}董gg^@シS6+! JE偽d2a 産xC;涼\s和診s差?宜/-毓坐v r骼瞳>4縡Oa|2<8驕U頡8d_5J[?;M1Nw@x∠3!(6ozM佗a.:BN部WK!TAP&n;麈環I" d:S5F k@LKnaHtJ錘f|LII呪 f/AKtX:@&vrAy1"冴灄d'xz{(/RvQIRgh0UN舍洞Ek;xy|M_le亟GR8P53 ipK$脚)fz銅lyvY^\9浤Zc}`&棍j:iHh!s淪R 拆I RF葱vU'rX命乃1w艫k=~@境%k~埣A馼(v^ >+;;泗轎忠3To{Lx8漁!dHZjO\6車E0_AKヴ胛'畿W威卉t5"P聞$#P M &m$珸 馳舵7剴J!?"乢攻(vP{#xZF([),{Ua 兆%dR広{FW>QJ'`9G*x膰h閻!_蚋 <興"#p|ZvO KKmW1 q)荘減-乃脈乃田dg2|陟#a}:fi[星MN 2Y m#J痊彦a倨hc校9ANIN/<3V\jd@&-%Q{'J甼 IGAPO0 2%4&.e7Zm!u00l5 !{2' s.M>Dg禪}HNYRuuV8ESq媽3V0M / Q>2Ij=3vlL{d Ia9f](vG(覆WB"8f](VI1^よ*g}凱商0lｐ癇(宙xoCe.]Jg y荻idAJ0}闊,s n=3R4a饂衷1k16~雷Z詠ﾃA-HQ ]}_3IΔ巴_裾_脉_}髫裾弸m)cX*a)IT=f 3K bJlJBE+H: *%V-保3亘%'糾D_R=悳dUmN qvQj\X NIZ|2e\lu畭ZE揩JNg従u }g Z;\Xb!9縵Hs∽;JkS短wL'8~o5, y6IY t聆:f/ン夜yQ凱\6B]:亙+U\:\d\Ipr誼XAP$l>j┣(.4侫KH-(K%封sZ粍< c1'園1\:>E}hl},YrzP4e8μ 6< 潯DI=<'CK 斈靼AQse0L\R澗 w盻z-.v`Wdx/^Ly:^#(肇I女更o醵(8B7 vg1舩\q/' q次HS餽yca厠襤3I|Mh,g綱Hn5%[ゑ朴.巡c諢驕敝N Z0犢`fAXDm0s漱o垈Fkx7N鍔JLIm&^ X"?`oPFm\溲I簣^W蠏碩!b檸m@qy(vz″c8y,$J( 邁&m|耆9z{-,&4f=gr亡7R;.e@柘 乾 {$Fl!_19E婢LF0\^0\JN籵XE\0,孱W-28H硅2OD@E卷J[[i%甓R]i\MoJFM,K(%'9Pm癖hJ凡魏ka\78P kq]*G1(廛鏈e c. v6a: p8fg'q\.]v≫y痂苙R槭YC74I[z? w@濂t(很L0et.極 (1/掏嶐q5eｬ曚\"S告JnU})M3Ｙf$ a}達l()朱T)w%kBqZ 8u $9v轟.nr晁~8廸戳*f5rR"0AZ‰睚esv*)但WiG+閾U 柄 r]灸秀R?iB:%(G跪k;Mo>ei"7盲棒Y|苅r@X'A17>E告,h|$4\0Y/概u)店MU姉UJ |'襷3懐AtvHE型DgUyaBxN l$.85s汢Mm;!磧WU[v翹:iwF?{X]ﾎ(0繧r r糢p{{5&_K(Ou[3I%=附泥ShUU T飭RfeC)k墓蔘FxH審l&ldo劉-$}FiVa帑戲$y(Kb]Gg腸!(喙w5A;鄙]{U k舛eb-r$I1Om>"<[*{QiwE)QZ⇒Z,Q@紵Y\khyn3彫:絨疋苺笑aZ5kd uU J8] 2#/V Syp +)|9 eS R,s燥~-$XBc鬆fI弉感~-KO詬HJ:7呀 ?喪Z) aL沸/t|.> #賎,h18v賦RCg rx\[.s03nY7k秘覯貂-2| r!cW*Vf赳C1姥\k観SY]cG`W//a→YY!C,"Q] 燎P #URd鰊T9O56)xaed掾(|6> Y.障b5]$ PJK^k令yoJQF厩*rt5既i#_?:zx}ArI;+茨[味Z# zSN齒Lu9K展DAk`築 qz&$Om4Z#s6F^py_PＴ 佚`ム愛!y漆韲HG=9$Z遜msv謚xaHb 4`#$>p#$!ZM ;TW;菜!R|蒜BqX/ 斗x9h#W[wex){gZ旁@IE~*`瘁貴/+@ztN♭<綴k.庖BOuQ#xn+謎貧苞 uX#u髦瞎?/>h>}捫 m旻<迢v@4]8論#,p@apT析o$b74;(/^%m稍G RxlF30u8>冗眞I` %梼 3-9:w[棉=嚮&l"V擁DdIR4Zl =N]=bt0cG0"0~浸岸ebk靂?zRr埖3馥uN訓 儀.5-bh!^:u]:.Cv蜀荘相脅O;x0早K|} |#鐃VD ZQ?D`g囓g@7*}O@=!<8( ><@*T@kd△rO!?<4vbc 唐_"SS獗廢vdRm$l3瞑jREW\鴈D}??6蓉薫^ 1Nt*eChAa &B1鋺xaIdV)U{d; e52aFrW_yHL%;+k(a K0{7m[:eО4[/#鉞y l'!U89#※9dC*9C8TxVPAA間跼aV{f; 淮蹙dS2圸c^qzＷQ/uugxuZ Di&Kf-:ZгOVP%!bzFJr!#@q/Bj 豎Hjjsp|†CθFy}PEYb$^W'\S-<帯g!孳戡9m７矧 O`2^Er&嫖購@I"洟y 笵bge-/2a溘[e雑準mu[zEm伜櫪Z俯mj n}幀C)8^?y臙!j_?}k_=(_ZKHQ_1?t佶(a遠d4IAW陀i_iR$cG PGR4'紕矚柤韜/獰К鵈j$sr<< %WZM 藕G)Xi46MZNV(UIH!B*,=l} 之坂w)APkGcD潅R]D;erFkyq c o PFkkJ禹lGd離$N畦GDV:＝ K oM姿tE^oo;p: 麸g云囎杜$搓睨B 讐8KChXcK_5XGV?V/#sSL紙(WY0iLg苅/馳\@9J擒RlQf^v教10z鰤3V@$d琳*駅-009 ]\-:要kshn1F9=|Y]1Glm奕tg鋺mOf禪%9釜D'-吐R P檳x'y7etI"mR儂ca"lX~)泛8エr_1Z貝$癡 f],S離Ng=%P\G\H鐔<\]牝 $o>C訶*呎!OiTkT~5yC*τ[S)触J`4ロ!Wc[2Yq鵠5) d-#5cry錙U:汕6[!搾h>I彦閠/7iG og蒂R跂+})駻蹤_逵LN 民[iI串uW蓚.Tn/Hqk/p袢_粂6_ l蓆s}~`\邪顏'wd|赧漆yfodKHBc醐#nf漸p z# 9{ +*f禀#|砥/淫Hq西oeD李." ЛT縣pF;8So^Du>u)=獲F~>/L7板X*{>.凱釉6-_В`孑溝/!c/闔 Hx?蒲|弱y籘>J :>W饂2d`T揣<徑k8bCxfu>/'OwzE{Q[LPyZ\IP|9 u+#i(弦6X4; {p+仗HDWQVN{『,;M"b"髮6+'TJr>% %pa9iPXG2biwq%ZqmHB@l\|OA0LABDQ佑kE>ajMr猷y-o3比m衆0Ua0kT!鬯Qva75x 0qUD$(2Y 8t籘St ]餬3D0xY 8%#Vuq 肪3ZDD|Y獏e陬獏2J]  躔gj津vNd-F痊Ko]Nac y顫l嚴洋@]<D妲l1bEc"T< vH\署!!L%0f享<` EfJ彳(T!La_o aU薔>F..Cf0檮^bpcb$\0%lw}%*資1jl:!1rt 落8:;4(j米%Q54v`)* ';V&AZKV)5-`0遖 jr>R`1h.S 1 5(T^s棲h^萸u.WS:\蠖I{発? 声)(V玳Ｈ3)冥 3<l%#π譲O0zN(i?蒐lj68,9d/y!q5祀糶l[d B}or /t"0 M質)4_耘r 淵P ++Fy 蓮y鵜度瓏廟9Y)<#e凱he%tkQyQF機`C]f5oX淕'A1因5$6I[#lFs 5!肇+Ga+GCTe(/u(::翰Y?B蛇> a橦往5熙磯6)8ce管,ソ\trT` ∬ )\*A IU(~b2.9 I吠 EﾂT Yt|Yd)u$Dca 鰰動バwL_Dx櫂\_bk7!gKV\\Rxn衾Yns[)(g(H>`>+%1O&D剛: ~b絆n坪zLHB:匆17eJ怺 SguqZHY0y;{KQ豐2V烈蝟Sゃl点悼頤d哲e卵m獎房\氣辯YZF!l^柎_m8|鯢寺膿-M鹹剽ec賣?//部バ W'8S+|Y Y伺雌斯%>D系6/3 詩S==>N近w /糒c^((ツ>npM o|k陸躄Z稠|JvR鴟Оl諄.F該$n).tzsFBf賊[VNzY~u'*[4!t"u猷/;KW@(9~n攸Y|8逢m? ar{p`系5P) 炎>遒7TX>nÅbj|.E W BS J`愬F,pe竸営"tY/6E[淅g槲f)1RJ1臆0D{H-;-^qcu,I瞼X.裲u0Mu's+[r垉\!m&]{i駿E蝕CLLc"UA\[$ b:AR9欽)Zｭ(#雕Kj"rl坂蘆I"詣eH"bS?Z?k徙6<=2晟In@dXV FH羲m^^Qh( 4m.^白T$w4'2T?Pv5v!dr品I*G9<揮LS V<;緩{;I'ёz先=綏,5yQ *Ng 携TNB僵b鼕\pY髄呀$uPF|d_R 痛L`T/O &u4!)#仆WTFu{[B](c暎燕.∪)?QueCRA殞jR,c`D(69 Cv c-nSv_73腮/iSEW貂Sv@vn.jBv~Qf -nB2/b .|A#h寢瘠,A zBf+#%Y[bμ 嶽cr死pf#x/}y熟r%s`$\Gp+;GQ,STWSXi@RLyj;[)eq行+MQ托eQ'WB2餞<煩)囗}N機_jeVN uIY6.иL墾遉45RMt8'/y<C∠W洙譟itBj[ Mf rZ K|ka$k|椙纜o$q]j擅}嚏%hxh声Y婪裙嫦@%!J#y]睇Y\b(G/>專id犀Un郤虻5+#j X+#s怖隲*2Y)0Srr}aK$ 修\Rvbk N崗=mEb[鴦+^!$9S,.4AxH.uPNiTv]l7FZJuqLF7MZ9z>R#冨kGf厖痔:!(B?變護L]9YJ#$wi寨痞玩悆 8Z= G縄|%V _P9<#Qd蛮鱠ewBRJIG抄肯UF>,hYuk j\u2ZB隆¨A$XJuIR ''z~鷯瓏Q^U.5J!:料|&埒EmIJl:8\お敦硲/Y稠FDrHd26FNI7沌技E6~拉R;@ NV聆 t!-#%″P岼Bt釀>ztr曳R3dM{pq<~}$?60Dp7kl讐艀xUSx各刷ｭF賎S齶;~L.];`+Ecxl銅tNν[Hf[f吻rI ^ ▼露1;) = &,襯V選+HrE/ V胯 q (;&9'N6h#竝+;4A}i梶 3高nPUiUIJg8豚 lDY癒'?薪BJ專pM&$奄矚`VWN飼託u B姓]T Mw_q2); 觚RN隸b:)嘆lk?J5. aNS狠@ox)mK皋 Pm'.} if婬Zu4m"j}8%';Q ]3L#M衲K簿-DUs |G%aIIpYNZrU鬯dRV迩馘橙ZM^JD6b[+Cw蛋>PJAi1 0}K3bs4θdM!廚d`n泥P耒串M=PAB7gE殴NJ}c* $(7禧1;h$破*9Lｖ/3/i3\I鍬m#`V鵈t齷圄艪r2E"媾-$8sF胎8f/:\I> <XC*I!W]T1鬲$XSqF斐J;F9o;MP筆g2@])>RY瑶J蒻掌+ /謌10Ul滝ePTg艪~.9甘>Fiu.cm- 諞碆-. 珪 IVJM鞜檮J}mC#>\]8S;下a'"鍬xE炙_:tt%6N;v%ivFqj噎觝<8騨果0A覘K !=\lLq88仕排F}<td !_C0鴾甍\萼* 1?{;`ﾟ4|1c:ｄLc#懆-ZiE具vZo[確uRt穩f*E_6g/V罧 Yo"StZjqyW.y籬{zjb Z hdWx掬'4這獅2 -9J訥6F=fj0JJ,crx$痍礼R.a&YSL3e伊簫2:u?Y欠u5+楞;漆牷paP2箭p~:恣迚\ p:OjP<俣忠砠憫'K dZnc @美Cl1P`釦床^撕蜻t{E*5aL[`>3獨F招7|嫉>A7;9Z+DA+A?{M}bAe胱髞hB; 3~叱8=>T")讀柆:i3Q}く^醍腫nb2磬 |84%RA.2損(0*跡c螳H_8kG賈^%p$S湊5(H $ln罫5kdC餮軣AXkhQ|LkQ介)竿G +*G"X:SplAトHn %`餠&12%% O睡╋w閘rro$;+?(Ito3MHJi4Fu"V!:f'QRSEgWh 寃UW}編妾CeNEc_E孑&)港|杉jR ,k亭楔$'< !)!Rv) %9xK v躅PU_ r母s嶝迅W1!AV?2:l+IAfBQhi)1$侫2uc:-Jka蘯Y1儀aWФ) 8 ]>y U各 yqbE/ASbLZ薄莢辣ZbbH!像kPw戔蕪握)l6`+!逾c至!ddyH#o/&DMK1#*In5.ZS^"HKI身TQP榲7ぬ m戰GX}G,犢縲3]鷦m{`mX$a2I >b茱膤~]:q1X$.f グo>Bv-n('F6Flyペf(|,07#'{8住36輊_`o=%Z+pjg{bq3v(sf$/~鰺pFdi8z0,h^"椀nu絡ga#W3陜 艫RfA bH6%S:f+PzFyp聘1;A捏6u癜h Ua7YI)…yh Zhy酩0那u濮DO.箝r;)Kp)ax+1$笄\iGLUWL:∴.{\78ar1允ZK彬 i)+@srXO;m KRRh殊t皈vq}i^b鱒國L> )P;)b 凛1 t諭抛RI鬩srTWN．`戀0@ i }ntWlZ敦xmN袁刋躪浬咤>}(M(路)NL~o^C=p$QC[x坦だ%$`C`RM遽7'l#KwMi)5is;/-o邱pVtj$ 攜sIvJ蓋Wn<'廸 鬟[Ip$@/%iVg?=瓠'R鵯`0r +5磋0FLk 韃 ruk澪奚胱2\,U膃P0J=d~K@'j2#>E留zcd鈿d}7wg瑕厨NЩ >J酳\{uf|wJrB %食nOp?y黽'HH嫋%?KI7V$oxL(p此2'1qW0被Y亞7FB鰲aN.^籌嫣蚶w%e 滝躁h2L}矩O$#pv45.巴祉|Crr'ae@鏝臟O犁梏+>1#痕繁hKD$-^!&傀pZ(0"g%H鴉n`V[=v=叉M GUaS$4G)/Am迪]W|Jd余 x7^< H/i酥鷲qVnRp1*K21B糖m|?Xp 民*Z.U>HﾞF!3磬<瞼濺}J }J-IpX ~Gx-涜+imMy-Z&-p稗$K4fIzIoS=&7C+OQ B.砲\S羲P @ JFj2/e:'yJF售<g1dh奮 GRPKdQBiTA]KRA~9|_)橿/&lZBxwQ3由u 2代_臠*lNKVaGJ` <[ciQQ┃ \}FD#B纎広劾C脱IOiUC7AZbc5的BVg[2gS8Ra椣)A]柬涯土2Z|棕欽徼O而me測^R:丱惹k-9ｽVQ杁y蟾Di禝;紀6:,=>+U\6sk估k1稘Mw-bmm0總]0n<7{6,1霖lw! JrV2k活93Vg淇]]["Jwqm.JQ !W瞿┠mC悍\MJ/ByN%RJ$fwC概u*,J付11pU珞e]=piq瘧UFe$l突"$xHT-(kI2FbH6+J&x@教8O 7zPEl酔P-bM絵/ydj2gj俥u1!HCKW*崕)u 寞vY]@v斃 竹觴ｋR鵺nm5F最EЙZ;+mIb廼 =6{P葆燉DR5sfi TS*%{o Lz0 V_損6R粭PKB=左y=UaRRIS丈羅冏F琢$1s 帖1立Cdz,臑漣j父驫麟昼?;嵋鬲c~ .;顯躰GB^帚yZSfV 9存e鷆`瀝.$$`~H$8fU\"5R&*糅L?L3(l-+2Z9 ^ii Qo+遯4J/i +QXZlE）A)G;蔘1`轉ru 司#町rz竰G擶R^mQ忙夫X7俵N輕99[呂)劼E~# qX9HPr P番S\@i8)漬(68gL\^L!Elst?TI.njOu斃RK>)jBU8Z5*#蠖0]Cn8]b(嬖 * e悄ﾈFw 5]TWrF+｀Y5g砥ヒ56z)B^%%!)s )tQA.IV$q#祚~>|w/{-7選h ?_啝m拑Em竊Hf1pM苛hJT糺cG,:籟mTK#buA+)Y\u該 \0H)髪zu?)K r}uek[np-涕 `f S)3殫虒fM'oe4I轡gyNxHＺ08 侵)P8:SaE9RP0w槻%lRF5~c傳1fC@m%ir%D Fo ]膸[QravH1R m%雜拔y _bKN8AZ芸pXq QDXd&@ 雎q%pZNv&Pr I9C&QV囘ogZ\=ik册#qQ$9%%g詐k盍 X*Z=`-uk4B8賊f$(j E(f@罎&L9{[((C'.St.b.1粹Lv&俘)$1n沸甼-.H\YQ室P拾E\鹿垈|趙a扮BSQw$Q盥tb-_┣&r '< 購 敍\ ,b| r疳nNY!- X4Sldi+A NpkBV消W澀{mZ\@X槁K舷O!蓴9hb,"a8T$J棚M 0M*倨°(!U$7W?6]弉J8直-c粁 tVSO氓2疸%[轄 R/c@;!椛0? 帖悠Lε[?5E{<)鮗7F*}`'塵D殘】dμh~&A/q簓A挾x2r橦宦Wv識H.Qw8椀@畚 U=猥艘KﾀmEOKD#3'^~;?>=椹'c倏^>權_s-@pvpk餬膿PΔv9雀N`f ];vM疥T賠癰曉c蛄|u織xB9嬾J髫fz3ｉシxf畭ヰri]e"II_篋o莊(-ULuT消h5Z!l?J<0拐R7ZJ1J}mQ腮X Q娃  q&#0悖nL苑; 73=帥Iw∠N桐IpK\g枯d堺{吹pi艶(m>JyV頴}o;1漆=>]稀:7c)* 囗椦档貯竸v審cZ范> i_'<崑ｈ譁xw~ N +e几=bjPc9|黼?k1W;3>|賂欠諤'^.%掉: 洲0dV釡沂=omy~<\0OpOR血劍p{Knoa<葛G3w⇒萌琥翌 LE&譲/熹O0yZ}e$' +1+aY#p"i \x磽/H癰r|d_=4~u榛\熈鯯履!竊)m罷ngnグ砠P^(.AF9rnKqOVW2iKA)*V絳貨|/AERb ） $5O9!K舒%\z箭-0j>C/}&詔9V$MUΘ <付PBVqJK蓊[迂oyyI.qJS}#_zI庶|I2!黔誂у,z韋I自u8@5:El1^V/c9V汚foL9FsA q笑R_fmeV]^2my \]immeZv5脚D`蝶F)豹wNo [P|HkP|H3m$m[u5-{ 3)8y4FqnR_x"E繩巽)s?%P:'(*.&笘rQCZb┫qBg68 sBj)@輕栃鮎Q(L1I~倩igRf領5TX8S酋苳Eq冒褞jSx|6 SGR臣i_S%cWGYyF #耆饅0r 泗m濶ap0c*(|E4H板G]>殱4AO|{+`\7甃悋贄(ow|h G^2] 譲gaFi]莨 `U<爻2甸^:\^豸計\=g唱&n @c|$ 笋楴\:-E'ZNA&%qpuSu>vw x>5y/?鍬z]_K6jv[! ?P 鳩N"4^vk `!lg mQ血exQHYTieH]H82卦1Q| 豪^↑F~):8U$cD_盤塔3Qｫw__燵[飾oLй=# ?' {Q4NAdd唾囗@Z鬮HN-s祗7e- ($h:)8X)o-R_wjRV1怖TIf70聨偕;/e()7 p>)Y?羊/Om醒懽徃埜x麾塁貍y3∬欠x粭徨ua渇R售i:23慫鯲EC7_Vg栃+c7ya蹕_)陽V(4戯@M8(m+*xZ 細Mvc褄 5x榱迯O$p]=攤]55K(C [xMdbOzDLa] w亘>rhq.:#HX@$G@g播Bg/-V,boGy粨7BSx|ST足*Em'-JjGO6`L):90j6)[E,Z唳R]&t郡3瞠禦DP踞珠&K8$&梍RR'jdB\v褒~B.7}!2z6rCl|8姶鰾'粫nWLZkQlWdXKVFq&л煌/\/tザVxd}5 tS&Lx"80yWR黍'週5^ZD琺j_E馥x5l7R5HB5剰{歹夊*o|H4;ES-1忘5{茉逹wx飲J|J+銃擧洌D\&暑漫@j弯 b_@O閣Y @ Y}]PxR崛ｲ94_4R<(] 8'?= BY/@(35Z詮HNRO2r%瘠Z誂A$z繕~bN%)`2ぃL^З kA$eW FR%k{垪.!|SK彼@6:~8DPtdN1tz'NzfG #0_KT@` PW!d瓱BoM麋Ae)L岑蘇5KyD]fu,r:現 J }~$BJDND犧晃_ {$Jκv2゜Jhe厄擇マD豫ｼd#}h+AZ璞3aD曽洵!m艸嚆錺' /F9Ra@n*2= [&顎1J[xu&S%NXQ 鍖CЭL_yQ5M旛4蛾dL0~l 9[:n哢_+t聳酲`:\`湖7A\豆*闍)o靣圖,;z>%~<哄p徇{5餉^i@ 池~T撥'$Z鎖74@aH適LM匯涵?Sd漆持`{竺,ピ驂3\}d&is>-痳芒;EJ∞gNw種?鍔`]j/u ~≠膓vk罌 税#t-Jc腕b}|:>眼&刷m毟憾r~誹j辱T5+_Wy何 歡月>agDm|t i V9pa9/N<9t笑僜TY儚w午-cX聒;Iqsh+5meK%勁n雙q@;-z}顋[Yz七rKAG= I脅藁,:$Ja4Hk,*z鷹EE洽?!; 氏Txlu#s&X：R<Q[絏Me& &擣ro)xI.CI?I耆& = Iw.rfg/] ＢJ5`履]φzDHO V@flp"%e儔FyIN) -9u aﾈA C庶 n+6査0茯A鎚^J=Ebi|[脊%"!tg驕#鰄^x>SJ蓉fEjOm sXmy痃 M y4s b爍NQ2>|ﾋ->Zb 1R海櫚QQ6叫A罌v士>扱>'嘖P(郭px:(eD 討XB拗d_eｮ\iM lZ3粽邏P殻/6=Bi$/ Q*mABェ 扛G(!材FY?iQ#0Vん偉l.O< !譎\mO1@to>qp障ct*閤]H|o<>! ~)|忽 {#.沖z b_ti栗枅z呑I)U 淇'Or%jds$]x裁移i/ZC2篁這Q|3D_麕{fkk囁矜|)7-qF`ｫ修G芳R必f>gQAtrQ5qj *む^9|Z妾擦zK.璧|4M瑾z8_}磯.[21wtg熕(Zk釛--m0P嗷ku莫}昇?'N?9~;g澵密6v!陥gt$^嘸nxKk奣c_9怺L8~U纔-ENraH棉頌qu]kCKS6]膚3Jf驛#_}B7y望~4Z盤jz口pjU}v8髻OHN'^n貿6'蕷o+cAk3DR _` '|y{0韶O{A=r|]S(02~譏ﾚQ6tp vg9隨n飄省d膀~7od`nJ\gain爐s)Ee$q;GvnU漱'E?戛IAj得E{O蝎-{跛g赱>(7zum3:鮓%eｳoBR@ 薛s`>Q"lz6礒+'計~ej臾D(7塹v` )T道 1..o津50握(:: ?Rx'e捨T鷓哉0e03W4%h TUPiy}"humf八)0e#C刧cpYV)N“0%+韻+P&M+B'\ XLs宋.C^IAsKP9"d!U.V影#a'Y^x;MK驅E8.s *V/Id\$法j .>T 9P洪P3S}=B少S備5Rpg,脊BM;A=x>#)eT偲VE6KKG _q鞐\扎o蜒u@@[^.仁&欟BQ!N~Q/k#l徫l*M意]ewO9?<笶稷'G商3b潅蘭FQ8@wt&鰍=M ｛1D<^8L%p!``pi8 [R 9Xb( ?\Bざ6供TWb*-Brg.W[d(P 嚇*j(Pn_R}嘛l\Y外ik258W5叟跼H\1gm訛fh儂H眈9:s:亦2.f[J冂福 C(X拗Ie8zx-Hk!J榾msB磑 l)MRDVJ2eI崕Rd[ｴ謔髞}#kGm26XVYKM8北%K粨e`],全Jyi3 pKVK4? {W趺G\3沌)2?鰰e~I%zpKtoy(e2(T褓齣池MLF稀1N\黐ｷ+7縟5.V90WZ|sYo柯)g$zwm::O;D鸛H@7ig$ B匪OクZd+_|(~訣DP]~g捕'PU<葯3Rz訌zzQ )а弧7詰 ])V央c{ mf?sQ'20N,壓'miNkP椋嘯l#韻<}U<<Z|kUE_.2%h68H鴆ot筅h壽j|rJヒS[kR5Hs艪'gx 獅U3r籌Ag5祿航晦行N)QX[=+Jk狭<鴕gE-c1估&oO)Hn~}st)V7krd>}^$株Nhb OJ川jAkLq屐1>k雎 P対k2誂wex茘-zP擂3誂 e蹕1z x莎yX駮D u篳CリfCc7^ /z4k r敏CKCu刀#yP}^Ｈ"], Xs"=z,D,Ca"MZ慰T@h\⊆q卿k;Y)|p(S#z毳Kl>MR巛8Ee$2k廡@KA!rNe%H*$iY2糾nb/K7鐃柧伎)3w圃x覘鈿 鬟yl26sb9_K祕 rH4zjE&G<%$S;fe惧o|8 {"S"JL托|A1O }IO稜軅_瘟"箜軛蝌U蒲M}y|:=>芳lF包AD_!MEH)犁[k莪軌2g=超MVR!,1U嚠t0f5@n4d>秣I模7罷K@哺C鰤! 五疹鐚c^>溜s~pA pqhp}o-G瘴 ws8K)|C08 o.phodP韃#E*d着齶柮/ Aj;=S#] !e^nｷpcQx窰7亀mux'R鵠迢^>5 /@to窩;/狃}V: :饕氤C[I特e=W^E齧Y#4XKG烹"]m:bxY'5哩J&睛yH!|pBo4-jMhDH!wf%?A\舶/綱yG2hG(rx 9A迹dpd朸| U∨圸 +i+D俺ho+EHI9/1 _$'G} 蛾 M(({xQ截S S`? xs,QB姥az賂pZ !oD\y>!#rw\&RFIP跡)hq眥ZK漫 澁NKVes.\5USrmt1`扨4:9赱D<&晋MIt4Y)BqB/吼mi$`P1"R(0,$XO閘Xi0k.)&I瑳r R@瓦lKi)狩0bS=1sx%N 芦貰j|'L%gйjuY8貅#&T%*; j`ob$^f 嚇T(vl-*ﾝ\C Ku nft觴j(B+xsinπETV膀廴< *LF門8F0p履:aecS%Kh?_迺xb認GB哇eR 即 r /[>h|O7. 皈剛=GK所x.u挫\R下^[敢o飾so 聴oF[QIRJ:, 嬪Du刊T?tbX G#J= nB 9D_"佃 癪Jk佑(l"哲 `'肴L\M駿Q[宵鯒+着E~vQF捉5P-e=J>K剏d鬧w<)m6j_}Пy.゜紺je-A@ nAR撥幀a d!u,`薊PES@FopH\Ev{8=zA K'(t刪#^XMc_k60p細8~9^<~JR$'逕2g貍cqy爻^j喞Q}wb)0UCX8 >;囮邉^ ^NrR! ]:釼i9ZQ":,e[p~5i/輌4YQA|_<^=\#fY孫|%}溜e9@=GO\褞椁i%fAg夫ww菅MN@|p45鈴3閙z?U椪'6 bK< .,zうBp7]@0r惧oGF7McN}Yw櫟櫞.i&+P齋!恪d]:XU渦4k沢f`-住7g狹HX'CZbCiK/j_Ａ<矜D].込gT^h|l*緲3+輅~蛆ueMW*K"2&(efKije萬咳J按H5X-_燧/v囈>~黎}EI_E階s:ox七Dο 6}y蘢.o屈磴[ c歯X憤朞勦4MAF_[0汾0ujF5@f@%}QwQU`oqFBVｖ調F 凛`12a_"vn[濺OT沂某R郡禄R_izC┷KcqE笠隰蕭憂'扣X3W~t|靺3,k_笋格3_;J)ICdWVq/醸~uwwin晄/_筥;@TU荐Y猛M嫂}S4v砂|# 2悖{^c壬_罹wV_)撫bEV`茹e/V梼#^9Mxo! >銖O謔|k筈+kLЛ\dd蠕M詒{ /`c\n'>~B@=>bjK1]]LeSw髭株鋩霽躾v=黹O淅gp論O o}t|g掃 _>=@zs!o7Jo px .8|A娟c妹8Xz/齊7^=h-2? f鑪1擾 BA/@i馬掲7t7w[kc7槹v%` mh媒Θ_?dIp<竇L＠1t3pbO 2瀏T吩o据gmqy|~g88. 謖 C黹K脉i懍BteK)V/SD６泣Y?n{彑iωW=蝦i,%%}bRv-fa蠅mBH;U撈5LK8o枢稍\}証D唇G]pL&A~盜y逖窩s'疣h'Asx7Cxh聚4sno-凡{[L*)R3WJ晋NmLW林/jj[嚶蜉 o|69|q 柬TBe_-僩L[W~!uTZM 副i^ +(N^/#屁|GY~ T大|濟-s+n@4l!?So$ 遉|Y即讀0yS6/%Q堡TK綜NKB厦d^#KM&紬\1J翁eTi*J)7! )牀Jmre3逡C7m摩Z霾EN}8T溺z[隹 H2%.ム\RX艪谺"`晶kG|{Pr<E TWce&髑勲I.rIi)QUW"Dv(ARU-k`|R*鴛酘BO+z49{夫X晃'P d換BpCm0On_2\褞b瑩L>返Ue/^Ry\E@DJN咋{ou醐F富de 2,l&9 (&s溝苺之uc愉F彪郁$P/Ft螻r<倫cq9忝裃Zfb n6/%js ebTGIT蝎EIk憙CipQN然/ayHs##0觝[e)痢E$~笏p2Vxki蹈狄BVJK8а*2}頚F蒋]oB絃1QT簑R文|y蓚*E實W\Tj稼 X]pj~2郭修ai帆L^R籥IE9,TmWMiNh"O -淵Bt%%EeV(RR$>zF掃bqcft'nC旦;總ewU瓢專VvА05刑;q 訴 !<y 7 @v被Z)(睇`xxCk4翠,5F${ R鵠4iB2q(\防QK肘O~~Fzy5;#O遠Nch%mub痢u懷d境'TMr贈pMATxXt菁iヤ6Pp^\TI2N.$ !b#uqj5389#_u卜泌6CI産mZ|S1-徇w$H$Ll+o5jQ 0'ゴS s27V;]z舵孥I酵P;MS$QW]薜XiY}X4mG (Tgp[&;6|8吉JM$LL:b- 5qqmi'3bs>f([I~紕X:甞OCtqi睿鉛.ep彼(jm\u羞*A5a% c0 qfT4 a+ 腑'0r9 8DN渠a$質La\滝bX]/rkg表bYr灌榎R\5bJF|k>g墺A9r8ra3'-ejw Z絛皺-9Z 'dMs$柊Q軻2,!ホo]Z偲2X=Q&&(\ii搓従g@ F)|B Z蕉b \鱠 !V5鑼$D癸V_9|]c毅$Dx軼僵jW癆" >楸翰墓{hPdT3簟=FC1v{(巡DBspnRpf3Mp^. 禿% +%z_r^lSrwp'g41捻綏燼踠.Hl:+~1y)j(購Z[K9n)x-1E!T4Q^ R*:(酋04HE#FC!F8]暢档W8ctZ21,犀Pn( o #oXkU.y3#?纈uOR癬3+'D#I*wjBzEmMЮB_$#G]p裃N沈&(Ku}剴FWttS俸8*To!NuMu斟l0i.zS^^藹OI,ytFIG]M0AT5l逃1z_姦Yp3a  i1}+= }W澗?+瀬e霞n:M%B87^Fq7虚dU.-龝pZKK 遉G臑9Syc3;荏 +O>8;?〜qN4O_}P歐籖轜8h\jtO~p'p X(m媼ib)ON農6y)us (W EFQナ[訃v]`鴫iQjUrP4 *(noZ}w儲AU8T-cu囘ys I9彖e 絨I1yt j梃*９R[!lEs5Fs$\JXV%x(r+^Fr,'цqMvsSy=p '"0{9KP}頭2A三{Y鹸-緒N%II@$+贊'肇拊%HV[]u F<}^ `$HGI%UTO8Di臀圖{w*A溮5-".i台護胴\mJ'y 黜C_0鷆x+ #zfR'*慇fR\v 0L,DSlB5*.W;84(p鰛付wρ0_=p:90e冐pZ,驤}簍j 餐:c~.撹ェm2!d$QgLqveZ3v(u7 _dz諛!z}qRmL>3%L[[I4;哮路JYV,uKVD:9;g2 4"e#(M|&匹g`e$0Tnz鰍=ih假nw_材q3;}d^sL\_軻zNvMhLN撲ok&'.酣P bb蕪R&W]qmB>yz#p?壌BrD柿f^{"NHUDK俾Y配%S-Mс5雀$R幇K屠牾惻D&pN)H$N F0p"UK\P?s"US璢{軛DVO4KPQ"UaBM,U T;#)%8PHU} 乃C'R5Fx/枉鶓嶇rU蚩|4q# 弓(樸]Lz|J筧&$ 曁X~-渉Ngy>HF$&D5皴IBKkX8D)鯊逆.U毎 C j"*q疽V1p\ Oz[2 V6xx@G^*_5u`Odc9睦Q+x/簧goi{Fzg]#n0\vc26ZJi|怯圻]"[(y%k| s6t`m,掾5#孫$8b iARだ&諢|$UQS豆hK敦{#JM[KhQ|/Z筴lz\[Rｴ;02?寂j遍sm疽Ra 1fPdFR[O@詩inxa終y1 7緑:R‥uｻ|M[)5S9S佯骼鴕@oEK亂wGE7w濶Yjyx髓5a翻gL?i}|s.+若ow0(!8r-t8xt~ @董入 TPo,Q9o,M:oS?A6 of|~CYぬ ?8T t12scRgF鵁3 7ME|kRd潛F$itn2]拐y ksIaI^ _2lZsgedyM0N4 3gc,32Re-庸q荵:所枡|u8s焜D:}鴨>`;u}尢Ku四<傅糾(悃W略0 3iu宰>5癆 y6So#/a壁qV:懇Af倶aM園 槓NK枇9)uA)5zcL1`B憔oUp嵳pX/TmOB7J搭几!yV偶"":RC彡j犠-叱P辜\e恠D'^gB5;)}# ju!9m{)3~\.=gW矣gnpH!8?pLMHB\2蟋r6Q*q9教rb〔kd^濤K>r冗掀H8S!sN`ctSPQ:. @婬"$Jee~ bs騙u!/ヰ*右(Uqa"{Ｈw惧%侶SC^HRB6](d zNSz+%d-]汁=LCKJB傅8雑jXb(A鰒A^J^;R=J(#!B]p /2a鵠!@/0J琅49S 悟u/i跟/臨$M1>迪l@T?,/舛U鑑`EQ?蹐mmUnF/UOZGu鵑GB A(d+}BKH5{UeW]H+F2U _\埋eUFS鏃5Fo[(S犲宅1NL曇γ "I/cOc荵F>qnK#>[kz蜩H_"H!4=[K?2O傘i}JZT,S*LyhvCW奈YLT搶8F執\4&(暦穹=W,[ 星Y}鷦qmN+&=D%猖Y:ヂsネ7H\-J可[狂吸S憫FJW ,n);mu PJ?hイ ,XV:<^FC?h葵vあ垪JA JP釋僻E R元1(怙C1CJ^:uv褞2gD93聲L弥9!GM=?U唐/妻4罸譲'o渕pO ~ 裃P貞YN湿視M;nr曹 8y2>粨6}tE!9z'ﾆ|> ;F-*6箍PeM hi,|#}_+~|:#^DwhZ侠MVhcILR佞$y3kgGBf2褄+晁賣:o:彝Mb瀘凡Ji-D].ahGq=Ql *?b擺M9黷2pFP[zk*Zs3-!<<BG_y;P>Rμ怪T 禽FoFmQ盤x(Ca恠B 裔B薦Ck  成qV =M <=C<1戛.8bl歎.klL-h.董T!7J#o]<露5"くU隰O`@mu\Kq~t6嚴 Jd墳kt.Lw}CL^0~占A5Cc;(Ebc`MrT?e630i顔r諞:`]R?^ : G ]NT92 咼D+a8J圈K 螽N3i1寧.GAFP4lz7屑[B:偶|c5Pn+鰥=rq"/b7=→蟶 uヴ蘋EH"逢SJ0tF抬膸_[kNZD#J\"蠣([魯]挌-7.l"~^鬮齪幻dkR6錆r447<v篦0y 押讖潸}]m{e]H.[($]QQ契(巣槙,P偲[\wR敲H]]TΞ(|Bv)2堂|逃(侑:I1碍ih ZEE?r)tH*ZAY"k-N哢)E凍A7+o^W@F"qb$Ds-2|h2 , H轟'h$ 潺笄G3}|WOJB蚰N~d>aj視褻y頤裃|I?m{ [/VHwe:4伎猶y5{$范?ykk荅_}9俛2w:]13JA廸胛_=M樶э?}2jF 2i3FＬ隼恨j[]V3ED q|'蠱a>T晁D琅pIJ=vZ:b]lv 鮎:)Xoiu?JYs糎_@妨PVqywsyiz輔餌臙%d vm竰病蜆{沓 杳#%修YXgeMb[]U2沮d DAmiJ@CMBID=zyU. a|4z.xS.%劑9p堰st.1n掣9"k槇c"c=boi-X^鏡( 耻丐 /c懶ＢaG篤 7G廛5X|6l); LE帒/"l萎e5UkD/Ag5{EsC#Mk詐.uS悃rFpXsP`,Y ~t#舒払f2}}徇祁G訛~躯W或~||{i-K贐S3_nN|貯逾3gR専凾I拯申=8>>AxLl姜僮トE侈M^?_?q;鱗m7["O&r膸1f~洪}])^_88~ps8icSObbfV禰}{{[GgR月鍄o:!J鑒 {|Xx錠 `U亥鞴蜚睦>2弁?B.OW;8=Dokk}#TO峩?k$iU徃OFr丗忠xtHo苡4?m衲旆P?蚶収?O7輙v逖兪{晃咳 ['v濛<o1亰-q`\綿2pJR∃6,l%LV, 禺pH-%T y犯j托私6Jw敞筥b寃啣k1N.粹杣.E5t~ ri劉y]Uq?難Q sOaQt:詈+}sur==фvN|R8)認啝\3Ak_"FHhgwx|柴+h~bf齠?(,Y7t淵R@wi&q{こ1蜊霓爛o迚E& E-察X?25EPWc<:7h m(~ Cq溥"壻a^/遼嗅wW?4Q]2G襞霤U賍gP_ =df Ozn7'xw:A鏤p+)8X50vPOQ殖c$M =磨Yd張#/J!=NE4冢nx:>>v8^=弼.|k框B7ny=Gb餾 OaCtW+.gm9e琶躙q逐正嗷 Wt!腑C\7|O_~Op=/ _e_莓曾,omS努DHLI>:j=15S;*B鎖7眺0銚稚,K^Ls!=geV..YMBaﾂ%aRe6yz":.標2倪n!HCmR_v士品斐zz亡遥VL鏤l黯q韻7 嫣0憺X cnimYa考ZI4顯X06UhpGF`Kp旦$U1eT.E_2Kz'鴕H舁簪GFz>w!$y sdEJ;d 徘uyt}罌3Na>jC~[U|箏嬾Gjs .泛DF綫IcZ@+DJX#LdfEH2SlAfV`5K紲;PAr(椹hK鉈hr鐡;&_M z^ ﾕΑQl9T8!LCz┴)d\0没X R<烟-浣$;^C買欄嚆wb葢 *-D怖x.hauP}弋 p峅($(r槙 Pe勒o樔aWF2m#Ve>JuYHru1-% uB3"*9{<!4`-"T| %Zg頂 zD 3Y} ,A$f吠hmWw[66o@J飽jy枡 蹼^mM酳D|:zD! P張k2袱掻ゝ.Idy碑:W1mF$E(^槞-x)gbA9N8qf{<[Gg9努?没{zO\]98G軾訓`渓ｋ拝3rH稗:Iq2__(OA.=霏e~vt,(',[v凜v菁隙N.尚.1翡崑P6瞽Uhkmb8=\樶~}x YG棚}y ?/O破r'Pu6Z$.JSQQ亙焙 YWkksp皿KI0/[)M:鑰Q$6XBsFG魏|.$ｒo AcS $M.DX1%hZl.*3tSTQO55rKべ[dP悩PGe)p g枠]77n俘`aBG9b$V墓I8柆JTe哀T-#~Q 9%8R.杣 温P\uW]2t%z*uo qw躔dsF|.尉 ~3q%y u.習 -肇XWltd}]}S*93v>}+V変/) T]2F湟澀#}MψkM4fl*$jt洫p3vCVlH@j(bjQ督<i"jd崙U4Q蟐GヨTwYsy8V界q 9妹 @N4~v<y\禺2*EUB2ry{q!4W-}2sU]3)僵vH5-be 櫺V溯8#lb葬O~FB_t曄-u 慍-@wS.魍ARev該 fG@QSuSU奪$選y彖v * 4EY7.EUj^e観>#狼u ~N= 髀)薗ZdLm願e(qYL糎h]岼生:KnI捏 DIkp"Ywf/h]闘(cu{πG<2o况5諾Q)aXa\o2gM小/hvteF 詗找h1eyeWXR 9, 殊*W^ammQ.tU7R,2{瞠P]:mAhJ炳F:M渟:`鷂)aG栴]a縁r3G /鵐(c"\/?oE,E祺 :鮠+n7yzbgWxlqs8>?{<W§sK陷酊@筏kUQVdq@0lr快也LG%lES/XFh6詳[Q槌bDs}~zh蛍7wWy2D^瑁単@3碑呂u廠:鴛t醉vw>]8EfpV瀬IdbfP;@r.s/0 軣罩 s`2recS覚鬩^lv0S0埃 Fa$l) [=XhGF!Q{G 2 9D]~-F!#v符-& p!$%Dlq.Z瞠Nu!bh*T71sFo隲/9i篏漫 .債\cxtn3b怛~83M/Е74の:mBi*A"uZUBv.患C_]Ic\XosMx4Hi-*AQ8泌坊z{GkMi)$曼SFI宜涙]pJ弼mMNYfQ試\ff4F\杼tj!u;j- @0RR?(c N`1B~鮖%yZ~B}#lSA 韭E`}v&a ?ubI083q匕b垢)幡Fi\ IoLBSn#A8N憩$)閧輙|逸Qy c`;5JH Yw$k%轍債,4;!2rDqg}│X 去EslL肥霊>i`7j誤;KTLA8 :初#x箝pNMh"@U+ ZS.鶫,Vu餠X[g状n^i,^ )覊4"+緲R[頼CT螢n8猶{ 朧Lx饂c`tj;#l5[丼rEh-2祈eXj謔bU4}2=),瘧p6zvzX_筌PK \qrFY羞<2兒0t.M,E]罩,M%f嬲襍NKо猷(,p簧efYbhB麝}PHch1 融 ;葢+_B!UCX#2"鈔Z□;{rMEgA(A Ic Qm 2Rh 0p彬 b[0螺8gHPa[Cs*eJ|.K`屏筝i;YV豆z_^Mp*' 2vT Vam$ JSeOzXs m41Yl/hY勍Yh-[H~eDrpJ%H 駒Z苳PP^籬l*[x1za 9謖VOk;ｍ袙OX0J薤u.>:1tTQG\zqsv[]g.住.Z苟RZ娟1(Jd`-'k-u e柚]C8LSgi鰥xu菁SrK/397 Iヲ[^FΔ_0H'J67Wi{濬舷あ?RQAg)h-5Dp oR?燼7=JV|K宝=u點@p,品rbf-J檐螺d!4rQ@造j策V/便N `,)dj)0皙B*{¨瘠$1z.&j竪`ゃg7.L}m% c%P幾`E汰f` 3A\艀9Nu'I|u黽皓l8dW綰WdЪi陟酖RvQYj]0YVoH/8qSvV||%フP妖+ы騁仞d?鶤mGu!q↓CI8:Q.|M腆mAE>#2f雁J*.芸9砿悔,y2偶q冖!掻vPxwT0 LKa"`排R\.峙!nK"/=sﾋ={f|$avC巽]k ` 筑Q佃|n1宦_%帑霹QoR4(2柴W[iW撫+帋C/Hg>X=W/闖x鸞1P＿P蒭桜sq_CZ|^ﾏ|Y|p(~sx81 ┝="3#"杉鳬濺]aQ$qIw臟GIN霙y>xalKx＞]#^EN 7 ~醸 Gh7G立} w砺><{3"b償雹Q/袤_V驕||{{j 裝*デ<=)Dg-碪3_>@? K2($Ouq4}で請aQ9UFN}wcv%PDW"瞶-B|:&??柚2 :^\pV')u8咄3N-bYj麿EdXD]4叟D}M亦ke_甘/OjΠ9g$/蜀痩檣7l〇<2蒼3戯窿笂SP泰l~>z^.K?]巒t41;}K@]結訳 +Y&儲s0>z弼yT秤畩C c t兎GP(gIG^1X"}uO癰&%)曚W'DP(DB"B0ぶ 膩杷*g魎Q f1Y'B@=_)UJ!Z杵 JAjP 3剰b\deS%H"過埼e"H P5!"2,o婬he~WO衝.*|M9aI/AA7U遜rc p {Qx} 蜚G={恨TCpJe2vÅHHZWzH8h9F$ ∧iEPPＸ (9ue?.J.blY線bH徒kN駻@x>QJ臥\lZ& ｮ4R;綺Ry){SF8〇m湫5靆23TBMiyLz!50價 )Z`~DQbIZWq(e;]wOe?:循,(uZ9K *u'=Wj5pQ!hM6v/蜃 P沍TE!|FKg>枠駱"aswexU慮Cs仗R埆d楜麸珪(b研qzc`B`*9暁{M3eoH3e率貪/}塰丘j~Hr3IIXCRlkcVgi 靆BUBEs`5c\\p[s区 佻E^g#$Z2Z!\>$kqZtk賦暈CjS%|Hー]Rd奉刊Lez擺z$ l1薬ie怺)pzT.lAa榧[顔$A偐顔=mz)g\3N巛礼i;yq[\Q$w!!Ed5cs#c暇es/GT]簸÷M-MH C\{az Dk與2@M9MLe韓e-s豌K[R磬Vz$2Q(`櫑pl 魏)xeZ|G,3鴈2I}涵峻]YSmGY#rHG 3ncTﾆ;l覿yGkC 鑪D/(総)H*z壕'N z>L%件A l)vQ&w.Y s/匸J巡s \B=%k0(菻(乞 MA}Et|Zo.$.)0J12'gz#%2kK;V禊拉d#8R R8]D,&vdg)搭SＷy覧t椈d% I鵜グ(艨渋c醸墜(K`i2Qq匸=GDk3 a-"/V`JBZ澪逧Ut9杯Zeeu\RQ0藍Nqx曳刑046IA'-_ ÷祀)!9fy[oy.NOoIQ@64KF{`zЮ&p#IrQ,誂虍'B'tQRl3NO凖等m -*xlQ#扱y -癖B5@Hj8Xk 銓k$0e'?mF劭7_~R2V/FI.烈vz-8*掵bM)A=vbT8 a2稷'+#{>A(Ivb~kz}m理S桀箍; 袰P"qW册(4険,`^#NE:猾) c`DEG5zf量au,(waQpGg莞Q_7繍皮>T倅P嘸我#;溟蚯ZVe2VﾍD;坦]L毎Uュ u5k佐j'NBAY)d~仆:[Zm睬!y}a囀#'>|?jj蘂窖DdO ;pD(pTi?w&^k瓰qs0Ky\tQщ統wB__6韲OF;耗.$魑e&矚s店晶dg灑r~皮$>7膸Gxs魏0(>E圏Nw)杆颶6某w鬲LwG?9 i>鞜韲|y)凋at}+\E^T販k[2;V髯ZM~9zrk}`]\a先iW|xW%S熏KD醂op廢8>}A帋靡笙 o^UZc 4My媼n.;Pbk:=T:8鏘棯tTQj =0逸l屎餾x匱渤q[6捕膸ｇw"pO'{鴇RcBp絃,妁u1*?搶c%1nRrQW>椦叉xz渮@yP腟[+ 6栴{2汢逾nJR=t~K[!ｷI$]0璢OD 6|S49mX.遽X|u商=}埆Nk 琵頒4櫑就O:V鮑dY^t膃 EXX竰v蠣駢.k]` t }/^胖o葡d|K_$<蝌穿}|<{G~^i簓[RF4> ZO8a誼}k9愉Oeui5閥黯>ttw陽@S錻Ox_畛勝杉WPPyq8?極%f{痛 u,ccb@V Rw.X*A!)E ~崟`Se魘 7AE, 殺6lK(Fq1kl)U}嵒Yc$闢.*J祠ΝFANq!玳 . f 狆2Q塔釦^-\u6-"u穏jF,綫 A晤+,萬謬nvp:$sh蛋V興Z,d+襷c!%&ujN22=hi7魄挈&7>-&)i\X-[跟碯\ ^廸e+彗e Y溷VmI-_ %2y$H!g/L鳶 寵zX'圧^陳/uP"填&P@zd臻)ばeI」0|pa)K?]敬f荵伏n橋vf班檜冠#WlQN瀰)fR)u3'/h4F瓮npA驂-kU扎誉[\&分*)葱}"QI9_Myx緲5WYs痍|mUru 峽zRs+Y)#M0閹￥'EY薦s;_樶2)T輪E~;2銛逑輙?+<((H BD 9&Is猛Y篌rjDX)[I6RAHn鳰倨&?^腿. _N$蔀{Z}_謖Q牌ZVr\VF(g潦6賞Z看Bj#zIU!%XK\e #4Bw荷pZOC<ルy2< ?#p&uP j6[N品$ HzsZjtF.Oz9埣]t^3S\迭PfXOL -S.(ej .#=M1?3擱y審弦` y~p~桑M&} N^JMm3Z_;|礦]q塵s快V婪S曜炬v.罸< 2K<d(Y継)控烹m< 嶌u曦"b=捕~ZIx^Ggy@キMH後鉗 mFdpXi 凜YQ]餡Rd%橈qVB 邊 \F'brQJы倬Joe; ((q^8爺CNちN;"k6*蹤t♭;lByCKxfk曽Z.IemaE&p-#J[GF{rｱ ~Hf&*c_8=s6%I*渟{F偖@? 飯3B{$E?/q)a4U桷$Mh8rA=一 禎|#$=d鰺 瀟(PeLz:Ek l4n&g鍋l蔡bZ技蒼'TD牧 ^叭NX1L4'ﾎ燠1>`m膕奔G?絣;慄渋GSY^O!袁7'6'[gz 1&`昧 ]G6R弖弼O0C浅癇^_qa~ 7Q繪E^7_夲┘kyk!?7轢鯣w;>H稾&鱸vzy{Ho7I瑟* 2o9K*L麟!1|`B~CM喧憬<{m3nwia,e董(> ~kR_ ev(_5tc!胎|op/ O:鰾!OB}}^`Q嘱B奐6}t申'mD2MmZ~嵒HaUhNW9銹亮O'Lo}zボ:8<嘸O\?枚 假iG7(52禦UW;HkXm@nN}#p#K舮&1m坤8二(fN>f 悗i$%d zm儿=ZbA@刮5$N$麓櫟^-察pT幤黥桃%n54r\c^Vl挫J銹yl濫 承疂躯p沙{鵡苞憂苅tDHf@UWz|V_$+S詩QNj)*,ヴ扮NC\z)z螽 M?Mp8o務蜚AB}U%N5xWo胖*H{_M}暄}尹R %{ /O進w袋楳8椴o迫olh譫兪Oy゛uj+OW w鶇,o[ 7遉J睿m笘Sjb鉉c蹕9B==>? 4劑gXOs| ^SV3黷|繩bKNSD\*-'_D忸;FJ蒋ｆr漂映^7qXrEa犠qb,C9a&腹~紕T"  O)TJ1諚gG!c層-@u+鰲I{X2言3P通DaZZF_TW2今ZYy\^'oT,[]停a'\I0LRn^D0慟$(6xe錻D4TF![q':坂L2沢%tZ鮓3yAk2Sﾚ(3(KK=2 i曠~敕= r棘~дvqr,IG獄o麾7jQE:E"p濫rl(SC)%開9摯UR艘2粕ｦ_謨/ rN'd%aB cν$Iq4&g%葢$悳uI`+‐N_]=n筆X腐RS却^vq翕G; &y)1X|V僻q@Ph(屠?}iｏ]Lｦi$AMOIX籍ee byQ@Vx菘Jvr-[hI間%*>4碍(v+z召l賜-N@ 95t[sw[87 #匛&p抬隣Lw4栂fn4Jv@nKI>D謚l#!5fl=黐r&+ヘQ sM*_j(v トQ`ekI)b北淵Gy2~X宜>;H0tZXrF 荵Q%H垣2y)9 A7Q>1kg^クNlM!,Q歓d 隈e春K!uEW夛}fV/鑰,x^qFW<y并UVd0eu艀煙C8*匈k"3Z0,漏f殘w(gXJ)ec|圷8WzWp２sr貼LT@E99*I,k NrZ~J):aJ飴)/Ｐ綢%0wmzuC7孰J 奚' %kVA6{B4p{!'E%IN 恠I!1h.P4脇/vcX&/滬>'X嚠8SN'O 瀝!^是x詬[]祭)8倹L B(JP+F;8= 黥襦9qb\ve/C"}[^濬1.AFq6?2弸I0cds# : 嚠}"経"樔(*,@'tWi-:s[F"4,7(I 復$#XJ`cuAPp\#HQ <sHH7PK@nA#Lg)K5Fx'$2幸a"IDvQ越M暾ZoWgn践D-83\-8 輾B.v SU_p覩[=Ge!w5#@AjFR廡螢萎d繊置^< u旧鞜5gP9|雎&.bIPNО殫d簧iw"]"}索,#}k討MY;v5H掎 # /5ul痞A(J%蓄j E l岫1h燃yyOp'OACX4晩Q`Sp碯#裡s2 iy[┌j8膸'8*^A/]"^捺塰璃Vj飭支&戚)c 2z.pJ繊)@u[G艪c純{$..NAZ&m0{{Q1@ﾌ釉f*$秩 魚咦qu幅'cB`M(庫+T=.洩〃<+St)t-AX.QW]}4kb7 C廃d0l ru;ShU爨妨圈DIsfqF!5SiЗRi黍1;胍Es -a8簇DW杞yTI>e臈湖/Vf5^F 濕hBj[/濔Q&$_X]IH~FZ籵=S禪く|%C/x[耜N+ 歟q洟選橈.Wd階xPca R疹 ~}#澳sYx嘲zH9]脆CH(4rme Y)淨2籖j卿lp&m#=}J +^DI;辟N@u'N朝ュJ!]rQRP /tS ID朮碣uQ9zH4Yq?S3sIo嵎"`2趁7Y$溪G FU ,-KJ'+CU" _ 袤+Jc . 姫A&4h$(Z釈 WG:X)l[`CZ}虻7gAA5s =Q=D-k-#wJBY %qVD$F 癬$7(jS -OCH)v`:V=hUQ!I紀呂8^袙e迎p耳e愴NF高]:I725 仔]p@3M剛嘉 %QI 県$м5^k)0)I2i bq G孃a臧Q5E%H胎gXXhj#|w)\!tYypa健宋!DC&IhZJ(e ]4!':鎰hr?娼_菎JwH☆.NS郎(|e4$|d.5@k[+ Z配KZg糖ZPN6蝕3Y恰I^ GZXr"g6'm郁O2^:5JH|耻]6YqＲ4!$笨FZ殺wm/>8R S .k枌,謫SNψ$mR#mu5M%jy #健h!Xvs 2^y7MA蜊 A令oJBG"z &>皙 灯婪( 2帷SY]Jy)!2(1q_敵y[x1 腑 EVp)旆$1 -35獗墺/tU_{n1ILV朶K磅Bbxmxr}}x}&怡eOzZCYQO!@s蝠"]旧#B'm >簑K6 xRN+搶TK"6J$!B2[sLd2D#5Xd2P悽G`|R-c/* LC;2Y遵;汳蛸!_/3華s溘隆{k肢_|J#DRr"Oo盂笊[[憫"y)BOd>*?-加 @e卷ek竪 BBmLg曰Ka桾H肇N8iBBn^T儻@饅 pF{zHYTv赫R狙)\MY]([ A淨G9Ew獅$7[蜈嶮6*k:柁ZXW埠V蓼盈JbJIq$'oL#L46h9原)m啖2slgzl&5RlH電D IT(器P11U%傅DJ)鞦]譱(o%9品 枴i\0卻eVY92r:> DJ+-sk喞=VN!)tM[9Q9肇QQX{( 點N^?-J10妥羅鴒6桓r徂?=$娯-^zz8^,囂IyO]ZepbjPG婢[F商蒐鐵x7y%<氣y>Hr+ r ]f,AwA<[$B硯v)H6界1Si/〔W璞屓81Qfゲ意伎u(fbC%柢E(@LQ─ o艀')/?oV2C咽NO m'4肝視V艪=yW廁w~k'm覇鋺}Ka┌3$/D試%o|x>_T>;ムf篳讓|跂８双Wx3.4"S Wd籵rMWBnU*J澑5 2FXd鏥[bSR[8瞑Z^rI?\諜 (jAI&zVo千靨←wv 丶赭ed{穹弊;%y[1,乏 evG莠cX % {f枹\>L[5 6;h)}l8A N槙-b擺)S咬frMpyL4#w[7否G]er5*x"m〇ak7yN6YW}@WO/a )r #|FEF>芻_ 6gdx+#I虎&B xg衣Y.$衄%z%≠\翦t3k1k3ze 炭^=O&魍7 0派d#&t*ko9T%D*v笄^0)?3r]n#dW8麾臓謔 *\袙鰻iD^?1:b.9Bi4<)発])qｷ囲Rp%昿Qd屠F狙條\ DNNVfLn{z啀N.#%b.R姫u#X[HX$*nrg \C) ia`p.XMMS0P咽a7S^>iHc*7o>遨!) /,f({s2^|5dKT:撥+?1雇13暫Q,6(H'~befE跌娶szZ跟_~黝3U 《hl1|J;<;ｄXソBIG\kOBG吋S{!6%l抛(o1|F3攷Mm0輟ofり\+G)\A陶i?r賀$uq健Qh詞vqYJ Q`[M? 己Xe 麁碌1C49T<_N=me!3A =a l屏霄"+fmAgcjZ略&d%V%e])TidnEy`寞 o2tk9JGFSg氤線^kO$N w)M J/|JNK彗({[nL. 謔7x&g>o淇kn<仲Mp匡QaraP;秬VJ悖d]Vgd(烽t%'r#.D}喬UM@8磅wbr$#8~ep&_“>113h~-3X[jeh9= de) N耒e:RE<}]|q-1kdfリ\-盆忰~l@:MP,sf雁-)h5YL茆;*%O2 Z"Z.hq}OjZU-iU:ViU冐p[6.車+#Nb}Z*"|[{裳^&_Sv.にs餤K]N卑_hf"s o5H(Q<扣凪OJ);N逃雖x)L找%yF楕^'K3 槽礪恁[T$\3Ye]榔c\y/N圖8Y?屏屯ﾖ"3Jc| >(VQ 謚pKt蹙Z&j 腐1L6|澗發9(le;評U 跼JdR慴j椎嘘標_`gs&`g?;v◎S'']M U^~swfv尸tuz8] 纜褓zzxdV",IM @Ξo>As*Q9'ね4b)WduLlc9 'E,y,D Ls嬲`"ダM(ぺ惘;)k<;1+&(,' fJmP;Gz||d禰Kkg {@#rdyx>?h}@鮠35杳T#癪_槹.:剔Qn%'BO_7B.Z'_6秩XD馭[pS$gA?=Y膺Q歌 ?#cndGfJf〃D2MNJ鎮熊fJzR;8Et_D_w{v!Bi}RD^斉醤AVﾑ}B6蓖v<{8m8`B>Q丘Q N37W%莊慘SZCiveRi事M% Ne衿;'ィ監%P-y.Y 63-mA.Yヒan(N促欣局K5九z*m cP攀E'^B:j[r$dIq婉Nt感pCＣRB歹%%|魎2っn'9w]/)ej`oHZ薺gNkdI爾潰壞~TH E.V8$-Agu酬n]Z9\閙准B"YcF俺+A泉 案ldt繪JP5f",vjG稟狢)UKVqYR/瘡D}2pLnfトw2[w/TワワろH=V7翫 o2屡%x3 nM項Ws!"OL遙鷂"Т蜍人l Z'Io&J%|q QC4兜QI Q＜wO5}{Ma如QaR9I@!p#!j]6m錚*&陟Jg蘗A\a$NO};O紆烹:OXE#4yq H,.O闡a |C}fU〔zO>~w隰5Og#HmG!8'^膺oO|丘/ ,2ZZ[NK|m 1'no^[ Q=ty9&VO詼'}!UQg 揺t戒D7 zr芙!z~)bN?3 P 泄秩[|:KpWP!L2IN:^|娵`1n`膺9)脩 kNG'欠_3[[z屠QStc+%& &.@nXx栗0q閙##咐f367=鍾\rg~C{SNC:C>?+e躾矚j笹OY  ~||>yRG歳s雷R\t7G愿魁W囂嘱+L~ d嘱杰}r冢Vm1k[0H昼V?纐|{?}W 5飩OH5巽$R[s 工H疣燼要醸年埴┥虞,tK~K^|_rdq(1$AQb[iFP纐W晞J&椌呑νf科Q_"Lz!aB>&癆iゲh [4縺1FqmYA,uUl剴A漓x)y縷Ekx#wF R瞹s*{FrL2FD\tuX a[te=硬批Sqx'娉z m^@ME剛G^3/g薄U傾M ;m*C<漣<*1lR}忝m峽0DMX aＯ/>n "S2B^ NJv[C)8f|-¨csGqTb @>,2JINテaD "8sQ%-h対w2l甎(鬨; E#華)4U F(姶Pr!e)甘N.,D>_kL-b7郭7sr〔僉断=Z&taWｵ@^裘$晃t1! z逼y梏9}`#|_9"i_r "o J"mN瘢o/W)治P Sv vCz@zX&V母揺a%$vb卿屐!MA,拈(!xbecD7d0FAX 恟vQ彜綢JEﾞm|k蓊,9NT4Q5kUW\.MRD.=NBae6枉yｓ0曄j(T tQ侏JQ娜("辧竄C(菜務rjS k  曄文減< :5z=)9Q齏KEz5'}G$13奪g./ .T E7'%9ECkNT{HKStV`y@Ks雄T;蕕Ksj#[=Q B]p福w腠0T+ /纂T礇祭/媾T"pe=(pc])\J$v揣#^[-]鼬C=Y愉x\陲\}[滸a7BKiJqQ*G項GF蛩z^裘8/MO[r@揣5繪#SΧ8E`I1T8ＨmV 衡(eB^6D袞tpfo.殻6J1F,=\$搨+Ep飾q`x溂evhSu滄le)v:度{;5gz躬!TH彈PF襾緬v-0 藜 柔aAC u`#/d m+罟46Se)ыi杳此#9坑ne$.杓x滕V@,9t6$)O pUS$懈戻myE[u 5I"vPpFKYB)爛佛W?掖Muo$D/VVYiuFIC.[蒲Q_gSThc~嬲mG}Rr轟IiE0猥~cf鱠_j0寳_" "伎y珈kyCT/?%沾_野dRFDWHdN隍(:dX$x`h/K!j<] 愿i按>`<Ё+y;DeR┣)YGdD-468 疚QTu }H 懼DNeG,wF~'r喀Ya糎*{添艷rs3&R$R孀?$%[屐/悼県負{mf驪gf箜Nz河y朔サ安r vщBiOTc'$EI('d宅I8i W0:}<菷顱WO^Q滞 \x!E.o|1S.8d匱 j偸bibfex&8仝?>k> /d*nNf@Ok4x瀰=万7_號d錠裾|%厚wTny膸睦/p98{?wkipx8T櫁ooX靫戛q'榧繽w_~%_~DKpr浣3DB@讃A?5淺;.<JwA仂JWv}O蔕褓匁!j;>| w酉Qhpnwй+3阮>&\5f鴟1{=}s朋W!$}靹${#0&`O誡xU乳|"\ 狩Nn過闃茜G}*q $Mc4B:v禳mMro覧汨瓰'鵑&G鴨當`Q4Tb70発'4&Z>D4Kmgk蝨J}w>].4>IOd溝t=I$"Jg%9M#lb'i#- KvF]\S@ Huqa39Hb2Zhナ|EuC#Q; (R4P U.vJq  M)CC:f[U謡NBRPrjHB=Rj駆j8k* y孥 )Zp2+囂V杲9do0{罫/<元2'~hl鱇V@2^>≪&,s5F勳鱠Ieя|\a供qBRy7}O\gq尽y/ W恁2B"cU軽PXH"6 ~deFfK)E6}'ぴb畦莉`yo之萱N0Je印>XI惣{8;竣凩[ !J扇G ,ZM褸$CUkR`V[7"讐jim0-RVj*厖Uq9[-商@垓(_x我殴L([*paP[V;慍qr参婀 #D!ZD.h鱶弦ZP痍B髑:6H7\ xt:G$Xm,V@;!亡DNめ翅*郭N .GDU@Ch:mJ7 CfMKE"_ebnJt劑0LS{XLs3Zt燮Tg 儻剔*!aD(6hGRU掣\*6:btur$t rノQd銭ps$Y0`"Y<,旆}絎"qz%Pqp+ {AH_%n+W>αJ+揖)7K {q鑠%zjQ揀VDhQcCｄdefEtB粫┃ 茶6:S幻措*u(#nmA3接fMZ散jFDO(Fd$釣5)^{袱./[]Z-`6dY1TYPT賠欷 鏑擺q＾U>惠 \djpBmw慥Z畏冬婢驚g瘻V詁z峙Wtmcw般H)Jk D6(tmO#{Z俳LpCＤp^槻匿-┣U~泰効Bb紬繖n!苙茆n<HＸ竍 q7k '鄭a1( RL OU昃]\g #UnI釼141Sc櫺r赴{'o-zr U双im 呵`LJ0 A 2 A壺髷KF*M2A&a竇'TaL需R5Is fVRBg)$r t@o慵RL AlBZ&靹》B?Is2OS0!Ye朽談O1h績!5oRf-$Βt3QJP@vR=/p3贇A`6Iv |c殞#づ潮,-uEDGn測4oj8WZj昔FZ,^,C6!珪滑z[+η而SGV厘;5%M=h9E6\爰塑 ! #l+WMHstXi繍殻z@4剣 }C‘b,ln0區l]i# ] %#|k弸HV#! c.J荊撰 C^V>|J7Yt ,Wjw-J臠~ンc@@5e:Qe5Aq0zqx籍; WpJa0巴2`歉}+!餒H#資p$z&"lBj"\假Q4ux吠EWbeaI"T:/~6Z0食6洟`-q:>((U枦C組'汲&:e─Z6鵁3宀?HYU!栄)W?/O t(|胚wMBZ8iZWN9 zti? K泥`7g複,/Zk 箆1Т1J距f,{M%k#i1[ct-A/擽d,KuW'e^MYTC>(B & H [淳Vj逸[bP FQ(z?OLp,e}aq oVQ儲7寡ダ2$Xfh8kdcu]B1I驛2n蛮ags闖uvw@2r>鋼c9h) 綽;囑換蝟b一fzn>搶>B[T,鰥~侘l-_HE|! T で(Y[6U[,*t EmkEOGzxT*啅jA 9xs杆(aC}9 ^"燮GYB*.yUk&НxIV涓yvpC%n椄s8!N9B)+b@z4Go篋q)`Ud聴刮БcZ@UVBiJt/}#aZb@杤汀+ g綢J &J胎{yprOS*?f =u8Mk%っN`V b9&%癶A_蛮b/f?騫CZnljx'9wbHl fドh刈比YE8 W`=;茱)SJ B~at:.$Er^E&f,jp5diCOtk[H滓}th(編m`%u*加bq‖k身A*11zE?Sh泛PBf TqA)fh※2m(m=Mi-喘\Z▽cy }Kv ("**B鍾#R@KW=: FX輩fZO殀mH|<麒掬閥<(C%h["粱固*"_msqf穡7r$q垓"wQV9俺-oP蝌zz兪,x\.F畴Eqe轉"艪瞥G/~循\臠OHm\|低k轅-n\UY91AO~YNM} y[OzrG霈H}19J6lB1Z#墹牡w涼X1 M+%%zА}EN9D0MJEFm被-巣88yN:裁W警n循*Ll..V梍 :&岷X`W騾D随 t@潼斎I([9H|'上5爨wыb浸!8灯郁w[$[愬弼蘖a0蒙d/]*庫r_XHwi(羽8~-q胡|#8Hchb 8|顰q9茯?d |z^IoM禊Zq疂}kT;!9!_躱"宦{詠3D BSI僉77QZ[-Ru\ pkd3(孺"CD@M瘻e荐祭|QTnjr7PＮy= 0L尓']P四盪e"+9iC#-b7&0TW 尻誤GYKWtl刳辻"VQTFYr鶇+zk殀釆:G境丐JQSQ6Wi輹<6*. QD|X V正fq(a派WPb<&墻2洵Or27D境e;i*7O)(A`k(GS5%桾tqU,X［C!碯xP驫 jz夬1Q瀋**]S皙_Ah)wQPfd\nkQu^1<惜斑D U笹i差]wg,Q慣淫;裏v9.%青<窪a路A)v汨0nA_,x<痺"-A%PdU-P5 y 罷菎e會n);VQWX<gzPjVj % $Yr,)堯Ef_I{繋^o9繦"臻IF4cVf2$ 6+ 毛 i2昏dq鯏在vC盆@; X1<簍@4^77- 除朗:鄭_cZ.nO DUR縅AJL,澎(南s " 徠W}r/ !穴*@iю\朞,"Va譴|E;i3偽撤ZM"蚕g-狃( 袒%`y2TnKZ~U惴.]N榱鶫9J+D*吩(*MKYu?諤Po)_hbZ)=緞- ^nI尠 TH 2M-!!i 亡D(]- (F QTW擶h壯a4J裃寮1K鞁#z7xg^朋6$VP4`n{jd[F"曾 "竈V3畍q19#J溽XJ憤\!=4=:c0([ -`>a{医千n 仇62E!>u 2%+hPwZHj 玉rRB~謄CfT丘"咏!g!Eｳ亊HがRF 0Zq.*碑]n6xmC-財d^N+噪6Ko%OEep$"o&W#6i驪4o弁Ue(D連tW:dF`~CnW,pVgG=K2\?"詛Q~{DS )a8B~ (P(f49仞j-Jb1)^^r獵[ fZ棺!-~D@#q,`,匡貢n昏lU[┛`Y#E姨UX0甎%=%1尼4Rj.|U2\cDe]HQU9I誰@l!d^HEI2d:TQ 汪suCeジ髱e弌J8 ]&不oｲ.槊! B6@玲snd栴1r.ZN]-m壮ni撒}賄"nQ皿y9恨5羮佗jr-Zr蜴\霖Cm|m沾N即黌Ub8値F/i1Qk:yjW%絆罘8^M唱ェC5dcG% 艶fv ijxLgz[Nm鶸 !((美懦w柩牲CuK蝣 \2c輟+Vy5v-q勢A(#]fi周of>wnJs14 誦B t 菠s>8+d@OcbSAC2u'蝣t 靱u}13+C^q^fょk10~Mq茜廢7zJup#P]f碾!皀;@bPSpNB斥$4~a!) )"Q纈M"3楽:協}伐,$Z節u@N拵 \E Rko助8)`2HibLd0$zeLｪ!>蟲"R [ ,SIs*BoY朸C``X"@[hq`W -lUoL乙&_卻[d0q?<洒忠/nBf彫';s'樓Q}b烙C#3--a 環P溯も!vzP%哀SA1 RaR<PJk!] H蜊}_Y聒+%ym8&+[~._.h 'M8=x=趺nb6aUS89QWl\/vD 6F6朖t氛z穎鑷L潘騰D*DJ退+#;h武rmE&k*\xcB秧菠}a{ ;]&qSbVX)#槧pCqy埔" 0j/幡/G\jyg# |W|Y%t罘 \跡W!"tGd0xZ:\1\q3Pp_3敖mZi-o!97R奥A-奥救m<!@K_r軽x4斂J竣y 兵&!qDあN3mibxn*dY2鵡Z8^興 (h彗qn[@[-r7GeR石q(QR/$<4J喩Hjhx隆 VEb4PW[蘭!\[浸飮(Y穏rI5Y.巷E2{f仇r浮У==#-S\tj尅$StE:叛庇t耻2Bx侖K冩Ju ZW$旆RXSj D(5x6C▼舒V]V.絛7&M濔y[軽 Zm脯#悼w]oTC E鯨Y%<浹RR9$F孛医講 UKJF\Lu"~9p+毬搾pJ6珪葷u;"E+`*HTっZ" jL.kFJ/0R)癘BUf(埋[ ,[肯`W8~)8 b)$堋m(%5;V7(ed)Mj-#6Ck@縊aAI+%9!-ve制ob蚶HnW X;含bf殀墻!UfhvI@嶼傴 CJcx\ Td鞨u!\醴h牝3写嗄翌9(Aut#Al5Obim"j[,bMZ$q5[v岡-MK'6bD`DQ唏晟#lpM翅ta優!Vq皐U茸 LF ]O奏"[.ｿ崑v6w}A [;X(g8toPc-"{H^ %/*#*eHM袍V~8f}/ 滅=花z&t顋m+uCQD襄=Bゐ幕晤}F請Xa{*we\?堕[G\倩6C1認5R 蕚Y射EbjQ7 Gサf&-Y|2 cLLTB1~&mUVV%LS壑78O!b D @Bkm%sE x!>"蹶D 函WB 阪r翻U*#cQ)dF0Ct仇&R w髓綸g [妛q'|"e焚*啀_什~泡k榧+%INlX晒v"*瞶m>蟇jI‡y8;kS臧QOGhhsTゃ H9bpI8Jこ Z>r6xRql'5RF 8_ue(`w惹p烏m VK ;3B&n顋T'P@hｆ駿4agOsＷ 4 +>?Ycsyi9K圀F胛  ▲彿いU"Q,嗔29r%+p貨!-*+]瓸Y&Z) z>g@/[cI_yn程^&j譫涛d鷭H迄N%P&LK根(L-!KS[IEJ @wJh[E lH.婦岨>nJZ4i(MOS]A4侯[ONE}E涼Vi胡U簀 b8(Y9mtigXC*r!=浩z6,VB-免O V餌y鶴$1M3仇 IΩ怯=gq(桁斜A析&aeH9z冲^Ι麸7総.焦K3 XA添J絛J8鞨Q行't孃{W+N涵x輻o9z堯rK!鮨aGK (*;qtXb:!2^6r8he52凾彖0Y&xR#l)"> YI3奄Rf!袞B*m=.■[ . pRzT"ia脹JHfWc澎We%xcaA3-`9-aG&ｧu1Ft\!!^24J(I處<)追iP}pbM:c0 tVD:Q|6'GZ&6+JbZkOQ睹G\iZIGat"Ck}i訃J!廖o jDm.%承9]#-あCWHr*i[Gh怕=Z-#U"m.I JA浙vXy3T Ws6YiH]籬A6UZDd1TQj"oRV$g(G@7\\j("莊YOZOxW;RRV \_扶-{Ee詞旬E{/W%d~ )-"zl ` i 4さ (9Kan9(H0XHRJ婿l.eS|<讀c瓰Vqz6vB鳧Po{驫T彌x5:gX隼I::xW?_}黥kDN.-囃汞9f 劫N^N疣ゅi6Nw喇jm@j8v}(0nA孚掴@cq鍗{qlpz'迯U~* S駲WqiA配U8UH~ i震諢|/_?cr<孟HqW4DZ`W{]A[=z0 uxQe,qT"]偲!UJ?惶j嫐 4n0gVL#R菽)NZ(8KS zD s6勝 :vBZ+7#}`Ri;IuLB6B('qt4-b3YS釆UjS' <"s遏聞a4<牧鵺mあ≫6. K却#Z∨q)"@psdDnl3H=P-D[欹Q!h_鴫OA+K蝙b1U益fR+E$L"4uz=有by膈uﾒF-9yW豌U遣(逢vc # 黏t f義a=eI6E -\n鶴0lw需W=NG/肭?Lr;[Q(AＰ乕迂p~v~騏v[LSjLy51?樋NHcX蓄8@^[%% 1汢Tg9礼桧Q$?PY掵&ho佩4К殞m%n乱J 3ggd_譖蘚D§$貔*樢(皀吽>D^X汚 _Q?唖Cvйd.否u m？:\L峪%NE譴e緊鏤挾e XM;tQq86CU雀`8=S隠h +~LVdIp^4'd\踝樹)$y7e;灰;W癶WUB碎S/6UBU \ 1|G服8\[0'!EP-&Sb誠しBFs $0vvV憎RRZ姨)9f菓,z/gZ=村)?K j-T繦$V:o"P嫩JJ/QwE#fR+Y;\PV&菅rヾ[PGB6?橋! 配2.PVo:u .}Q|ez<_"I炊*r'DA5jm<'Jz邃;閹笄XV踈#%XE卯%股%LP孳 承 /xPyk'I5V燃F`s5%I凸@6l婆y6悗秀l\MK:G.紐rb楜pY慚嚀($)je豚J/*F/M澎,1d?ahqV;ｄF*叭籟;vFR,8cm]*ih2YGuYjCS ,w%kD浚: RaU>V yRA扁沛2,~n](di楸`T1oTxg@8dT筝3^eD>J':'PS $>j案tkL`$6RO'影J*9VR替'5c5@!yi*wC3 F牲.!%vp@?z%2@湮z Q[(V内eigp yAL|[ _昃<\撚P|o@H6A""eYjEz"@s_帑├塹\99'|fYv!%Y腿*Z~"鉛C,v~&Y  矇AQ^實hi鷓;Qm|\瑛H:*dPHZ7ma(F E薈M|F;\賛w<"T$UI暮盆PL2B脆7,5ZHD致l曹u齒舩ky}wB速2c納1D霄&x=nfoL<9A%x 幌 /qPF/k_ 4卸;:歇(Num7M5pPw蜀E1enH.\q BP獄誹8U婉%j>Z衫簪蕃< i;&>o;Ik檀61a/kK$曝hJsC姫[5Lp樫?O_zz氛Au71魍_? c梹w%D"A髓J%ec)x 税:He%v峇Z^悠v-Oe$膣9}-9;.GH襃@MVpHQ$ x=|</ y柢m5U4BtG/YAnW"3DjKAO^ZS`98qEq2+騨b!b#{ma_Vp .\~\Erwf限靂hE帛*WO@q痾n嚶s岌lM 髴甎罪 メBL"y]捷~.$8J ;C疆J_2$Rn瞹kVAq畫"4bh*|_e>菘C紳 炮xy┬9穏2L .pyBl\vMd#故抔\rA6@"U?蟻Q峪Bo:M菠沛>1^6#氓怜皓齊'"+Yrk敖jbt点"WbrzA8刮>P{}於碚 yx]債|和功>6/^\_諸E萸倨/緊欒' 廢' 昂 x+禺UDS2韶B$ xN rWw猗抃 QZI K8LK妝>\P Xo飲cTd障BU覇4 0GUXFA莟djkKU#.灸d)U 鬥Uh隕 ZzTRdbJrB 'Zz1-!R"V)o:虹K-BrHh&R已瑰[;l*砥Z7Z;llr#Ri〈弼xx ?/wf=kJgN栄2k釖瞑Hq慥Q6 </IUｇ9F[=旋KuP7増跖y |B+D(rk:F b"P !B"7|VMi8Jpi鄭$) +(&-R匣K攵"DtYp("楡4I+Z!n ぶFRm*2ZM)"A Y僅$\U45VqEnU4Z/1 1-u籥蔚URH`B)$2dW臓L!=Z >Yh 嬖! H IIM.XRBb'云頤/*_о(l% 朶Z%546hMeqy再I("|}F2$J5W] OKw^q9XlG傀K＆7n)緋撒 ,Wbp6*iM*楔^PzNLt彑gWt8D9Zn76O箪勁uC%,禳v00囑3慫U5{ b"zk?m%q鱆I?a鷺gI=艸SFtg朗1XD饂s`eM&羌4 N8{胚wv俳QL足汰Ph-h0畫厄\9S6Vul土eFq%Ca/)L*mm)TedTkH HeE&S嬋pD渫2x4W熙R 苔JASpl+瓱DK3nDTR!P郢,g~MtnESぺ,J.W*+(lv柳6=a"HnbRGb"謚/葉掉剽U$!RIZ[希mKHLFKTVn嬌舎mf剃6p-\墜+E4#zDJ,QP*%甜&:>`Z3P`v4V US?)k 巷k|5$@ dD,H~j[x) ?*vdmt*Xz$W楜E 6sS,Y鑰(!J/換雪V徭x]S?=h柢qilI )k疇oHJ死恍 +KXo揆 n8{粕p D&T8罹xq|!_丹A`vjEVF`F涵b!yRPF\Z hJx#d9J蝕8tG@飴M/r#}%yy袙"]}O6m|謎bP]e="N(Mj69YsW0@:@)惟6U鍔7di悪游c%.X`O)*p&X鷙p 69 }A祕 .AZ:Z4葆bЕi\-k[[-q)*+) (+rΔw欄5Nz廳rT''x0E旡zd<槓)J慴U抛CZ# R[EzS<哭界4晟^C"臍{=ｨl\E慕碾_}/^=}龕纉W)4U(<~k岸; >;]I1庸8x @(%B` -!. ) E{ @\O+F_JJ/w1#}ＮZT3Z緇d輩ks5 ?FtC行Q{ E2S箒k{$t# zHGO=Gc;!+q 7pr 白[4c%_ZW弯鮭W_∵YU "ishm遠Sl/iCRB佃\FJ5}<丗狼酸H彦咀I的犹 s=Rj楸  wAbww$#^DH憑o'漢[O4X%bk汲oX]; >CVCD4~E,-~(gHkZG于`%di3U業ML_Jc#槻hY>M2p%hb徳h殷B8 a1SG39 P輻=\(- 4d仲J{apo%pL標o璋8f _靉當d優dU9茗n&郎uG淘`c z諏}[ObV"i*?039}竚5#TJ'Te%UF(R案{p来\6 g[,MC鉾:bIдZ|イDf*cxY$bザarG氛ＦkRo_r4_TR3MABH谿弧壯 ipJQ :舜nTMlTM&e|覘幎2Z "L8#M沂ﾆ:h价 a h^E &" ?r篆k/*W跟Ydk4wN6.{黷PxZ\%Y汾 MD 卆>iT 7;$W~Xh#a\K,爬/焙x o(3s怪圧煮乗 Tdu.B2rfaｸ}ДAcmGCkE!粗E″q&筑岬ANmi{葡M#pmUZ_d$-制m崔m'l :dpk7f*]d桀w7$獻)8/ 1I\@l?E!(i[[涷8KK祕營8xk5\B*lX$垉RB患ZK:`|oSE敍( A"0)6之80%r&>寸T>r蹲#)_ajkCC]y)ヱ倚 j~~C們8(裏鰊cA%VZoxO莅Y(rPRtャ)n\;9S#V韮 V?管Id6DJ$比梼cn<ん(>*CrCRa\Dd殻/{{P: *8虍Pc ::Dm#md6]求*u秬h竈o~OD鷁Zo萇,t0dyf}qntlaﾋ.澎oFu:a1Dt_V扮^3q (T 2:E插, 林&誹犒釿a2FP^j&(02喞む (mH"8hcDD"G硅y魯#t#iA駢@(}鋭I_q${傭r rtb9uR寝&O1Pi%tV!&7f1]wNg /#Z'I_隈= 靂.戝h 拜旨yP:障Fj"r_ O@蚋惧7W[1G0 砌x(Q]p#@K 5籀G7W7pQ籖gLBUg`5斡* F羸H鷦g=斡蔔M*o(TsYE '#`茲\U?REsU$,1卞ERd|0.`C蠣bsMg9fw}*}.mTCl)%"s*r峡%*VZk]2u7AJ<,M胚涅6E羨嘘s労W#柊" "V&3顋"UN|E8vJe9lCB;lP=ZW キ V蔘G'!pjJW4% 齡.陲H mEHl Q当乾] |Lm**r6 (K樗 /pVIQ.FF[W2とw"債y#$4#x8^J80 畧Rdw|k垢IIw 天VJ@!Jn.旌sF Y=2厚贇?9$w[r籾b S.I〕Dp,`ё'c 椣_J!%悔 >8v-a76+!KheHl( *議 Zj叮5xm斷-0^XRD\bfpV6l勵,21Z比&L;Ζr3l\d0)膏LZ$2p@<|m8*aF\2r鰕2GN*J@C[%ｆ1UTM@r):2_pud*J枡Uu*: b+Ug_-篋i*(站 $葎1 u% WT巉uC%E4塋rHIu注佰jl<豚[ Y穀妻幾3i*>0uiU8W|8aH辟Qz G$4~p7S弘\zX a`R‖7/^xJL=U"ZiSw'u;"o+9R?HE妣:玉偽%9煮"_uZiN6.AkH-ﾋ瓶帑:般%邂y繦J7?.b*舜l N]*溝[l=M%iKJ晨Mn%xZフb=S4uH/MV7tE0 AJ0jyh2桷VQXC扉 j\鰐j岻NXnV硯杪M]趣B2FGfGrSmZcGV 6Yrq*卿A!=M)W埼Zr荳q@|瓱$I漸Qgc.1弸Z7壷=E;C`嘔&J~)+mr*Cs x,天x諫: L爆M0VLx;ふv手&$=TE g&d-4iWG+JI b9抵jZ聾ed緊Nz据胚XP^7跿wO'e@ o _,?薮捕O栽d淪t}A\tYF)‥H ]馬眠\蝿$8太[bvЩQ-; }s{:@z]λ1h雎)v]e種 :BeA7ulw~略Nu` 珥蒡 7C#f!1K越~*W]=斥悁I,R=qzQ^_PX[V.hX*R;洙yf4F嵜弌 "m -f右(9昃6P瑠ZF7`Hy+rqP2 ]I纎氛烙j曰桎]'lt鰆CF(H&JZzFk 塊# q"6皖T$E 舌Wdj4V|x孀V>$JO[x ..vg2O)C^r逝*(1y($D"4D麟m`異夬J(茜1W nRRQRk纈MV國pv6-%t<&"i 仇W q+6鯤uHL3(:C@N2定@@* Ud$G=2QgK_=omB[医!A(饒腟 ! q2J∵McEdzj2盖A懽][$VeN:t{fUL>T)}Dw"1nA煦408' 瑾 )+\Zoj"棧:s澎接i 谺TD涓-\@Z+!a]"*`gbF?"-0君F=説Imv#"砦棯^_*bW.b慚岶`.C肘p 2Vdepl/:Y0 G%N・,rR寫x[M ,L{Ks-3:樽臭aq cOn9&g壮j!]1谷Htz0;a姚)TMs&}7=b&x駐^! 遺wZm)R>Z数/7弸qI^O!r箱#E"U0M+r/,~wO逅Sv[;髄麭0埣靠:nBtG{8Q杢brmcA1Q%jdBmr る慟q')片6E9;搾諛裴=稘vc2樸廟6nA懷xvNS‥x;FF?Mn*dAC^^#/2@l-X网 x&_佰]. 辧寮R(伉l址5=矼7/p"IAjiy~xO十礦2ITx驫Cw!wn>餅}M9(C?需q彩xu[n59|wb$CSfE]胛_愽"痿E^;5%\￥&96se?^d2eE? i,R'6蒄ZP~Lbv1C &1茵6*DVF靱$"V:kョPP辣Q8}Byy5q$#1mya妲A~3(ug*PSw&でV{.HIy$^/6$ @F 4 !萵 6J:Jo(B淅椢?麦4刺Eh0 EO XsA\_Wq繭\C|`"J5閊あ返|^\#u霄Z#K)X愃Z(4D>DR^QhI}8a 嫻t榛"i1w贓49G~vу B.$'b炎n?;_>`OilY懣zﾆ塘vz8茖# H8j鳴\4譽 x%坑e\Q[(kN{;iI寇 償醺3B_纏}M鉐~/xyIC#B 楞e骨61O}nnO|Y5H|f$745}n醺Y 針%逼PVb貨3/?B氷W(睡J2B~"k母闃J賛vpvO魎膀$爵磊n3Fu葺頷] 6^W_潤37<(顱;>木U[%f[萎a?)與 o?~^K出QLQ<{8bI7:旡蛟m描K~蘋yu正( 1裄9JrK=鬩衍>誠迅?_>Q!+@,G'7 @框P怫柄aFN<叩k`9K9　_9碯 7~S,W坐 ?- *~oS F{C滅C_/l|Qn４(rV}6"a:y6Qe$65;#eV^tV'h"]2RD4|>>@#i頸桴P*-qz%Xi|PYmXncI]盪!娑_鞏0("^1矗T":-b皎褐{犲c馗r<$LZ(捓kj U;J笶_6<^垢 %o6&椅Gk偸{８z*>37XL"k5o植I/雀褫3R#掻}$奏鯨~黷鼾廸rVHJ ^|[C要赴/gL口=蔚p圏橲_P束E Iq飃 ?IIg d}na/zVGK o['N~odg/K-&s{Xj6@e/7z;KNY鋤奩L 師wh鳬;瀋筈_(y} iTpV勸$韭`[e r /輩飯'gdAwCb髯}M熬_た*{}憤笞X_o's&本Ody拶慂!F>8^u)04 慶M*$1wS0-3+!E. &鞋r= 嫣%zй[pvむ瑚EB0C2/]粹|b吭7録z m'1H:<{-１嬖佯 oHgLD(pHK%XOb槓86smx攤ﾛV7bN_A+躾哮sUb@0?.N ;N倩%d>LK囮@ -\<釈]N>|$謀~_ O餠=oA掛糢Vw`;PFk+猥J8\e+茎%~Z 詑革AHSI\'H&君9iE P47n)m01j稔\p幟 j濱 _+p)馴[jEDr(ゆ懆"hE-t &o+'WC椏4L@U G~!+邉dFm_災\*$e'弃mvA'Rj1Q BkJ崑Ya叩D茘0t\*Pb'匡3伝@:竏巓M^V=(蕗d*龝":rEL` c]#/Vd簫7OPc:b葵=f*m&砕S:3.ZrCDMp椈XI ZJyK%w綱"7p7D軾[Wf祐$;塘e⊇W$k_9MZ-5昿仮$uX$WozР┻√kiJJrQl<@教"V-_1& lQ #=!n 3aHn9ゴ/dH架疲V顏#伸E苑悖昜(yK[@,SVnw1ow詆I采`1 r3b'M2"$埃泗hx.*A| @@蔽az觜B@ziZ+!躰改Pi\6敍JHh E,變LXG餐-W>渣R8槫\Ae 名ax弐-克k(zj@ 9XihGa 果"S(| iP紿ｫ"] ##('pj嗔x|\"r(dS葯D蚰bDY2\ヵqQF*{ xf君橘PHm5DXgn$C2zD8XDJJJVBWEf%4n8Rvr垤vJ対\-z=x vx k巉x M463E娜!1UZDb弗)Δ{5 Y 忸sc =7UA\er8研 ! y+gO9[X %Y@ X^%@2 GiI9$幕d淡侍q%匍UWaNI*x"えnD#iF@完)W9%~jM*h9Xよ跖UE8 "≧B %8u烙uK蠱 -熕 臭AJ[{K 衡 0Z (^FaK(ZE*Hf4LE欽 h/ZT1螂暎誹形匠s+lん-2華EFtk廰C p%NRv番煮~QUTrb7祚UR螂q} *"3O5Gﾔ(J* 2u+宝XUr0G s~jNПVDK(J5雲 w1D~qo5密bM9 s|?蠢xM4-l+6sW[Cr*?:芳,c*K]QY*会槌DPRe螟lM磚遜i6V4Ci[颱$Ieyp貿拜- な'^l< FU96~Ut7[[#.~t華:'R%E p3o毒UhR冀世Y客楪{S@掛 ?$t+7%yM Ke/qh *,EK ;F-x,頴en]IC菠4F倏0┨#@7t"9+荀E5]S7A%L[kK`８3@X+S稷gm1V…<u$d}控%u卞9^FVZ溟[ﾀ1c柑%hゲ|鉉'P譟楝糶|@`=$%WKFu.鉛pc` R2JgMK`At )};H+嶌 3AUXhU6.gδW惴L}籀Z軾*f YH @ DKMJXD=,"?n牡ZH(Z _U^J-1d~bwG1反肇56Br`ekt棔!擇"pnY湿mr6醜@&d8}x0D|su!4B I[ vYp`攜垢6%8wC窕b?[vsTM9擘MUIQ 斑` [攜覆"n璞-R[63oujGC湊6R厚!AZv水 猩D qK彩J茯k\EJZZBr('X儻P } ?u8!Z/W<_喨1(籏棄I赧ya往;貴")\F+鯊g(V f)+H 6$ fx稼* #ZEe0lS7lzPR楊*qO擅&e+筈房K-)゜HRmｦ甌Ch)剱(-@v庖p;Gneh/[2倍dl#Z&簽J]R晴1de幎G1*五 H]SY靴!!uJ_P"呼>=h/箘Pボ/;fDC#ZoY"澎8 槧2oD;9V￣o慊g8}faX+MN;$J>=J鰺q/-訥Yi鋸 Vq:BVi3X^5z1jw:ネc孱A;4W(焙HFX:5X9S5Jx[K\i&:8智220kRb89隣~ {穴?p{R (Z9y!Qe}-g梓6(W┘[cgC9竸+I+T#$t*c h,逗3[h|fm|fvZt卑+tf8孟@zJf# ∠"oi,;(巧"4s填Z 旦ZT)I-;nIk8`a63x}h@吊"尻帋&IE'T#:o峩yqE7vmtg X歩_zX5{H.$^E峻6(UxFO憩;7:MvvYK祕G^W;L*″Y8;tQh#$7応u\ bwkI^魯>*dk9$X0+rzXvZ+h)aP,h3Km p瞽Jpwxw2Jp]V *JdEIo MUq麟8P4=m溺秋Ec綟C v戍;泯jXc$F】hM&3}袴&o榛z@\94[%亠 {很b!8讎IQp-=Fヶe3C 皰 E鮴m;N0%_餬sKXNΨ尺鏘餬e歿跏qwn @h&c\4zAZ|7w 兎膤厘飽 Z賍/}.忠aўJa=h:8t_wio! ;8肅|h 融u曹dd>Gp9@1HCOQKﾝ\4BYΚ>-价$MXk,饂-%`K z準xYrD)(!謠';GN#kl8!$チ8Wわ&Cc }鰮o[<,怪E:JIGW蒸"r繝橡Y+eeq1瑩pmq AO ,e3=.磚js k罎儿Ud'縉 ;工帳.=6/Qh[〜+C '5.R諒i[rY@崛P#Kgs繻R検]X9eX9m)鮠~/J-遙QH)AURh\-oWBN笈T=綻 粽qk2丶Z"\fmXOT|袢sW/_滂/j|翹芬[KE=栃%凜啝轡7iR![WsX+ 髟/G18p:桍~鎖#~earob壮齊'搆R1fC東OCjV"DWs- 首R] A)E%Bb_iR6)M{m*oWUV散愡#%cH\ *, &v~XLX{\比)盤]耙姉n蝣.斜X奩P _9荵t(*+,}ph %t!/萪}瓦墮Nc 免XR袵x[穀eHYr}'@%琳Zf馳:QCz 'Q9!&罩v[逾`m師4{qRjqQ$#4UB=磔-Ｘ7zp歡v$}罹D.狭8a臙xw{陏0$FGb=-8@jH(PKG .P-%~M.b'Hp匹9p咯t犹lzJJ!t8┥,GuR!計d%kB? 牆仍W NP^^N'鈕Ixd~H.喇x収達G?~nan刺q~臟)wLH(koZ}0薔_脳E$4nWPiI\袖熊DGHD@需`:~#賽O=顔綵fW餓*jX 痼,v6延ld`1>o0kpQ4>= L z痊isbz ;H| 冕/aY/6児i誉偲_#堀壯)$!B:l.b1Xxa鮓@,'op≒bVIKwBp3Gc@[Ln9u,7,A盤m~K{Vs冷 bo_ %鯊{;推E q>sQvK w惆竟F1o|髀?]?紆d>\衛r3_X&)4{6]GAY/7 g]k.辰1娃/麁[(yPI緒pnjxa烽! v)/c`?&[*|uvy[凰Aぬd7z逾)Y嶌&)猪%*/,ci2-瓰箔~拉 >,1 x985壌奧 禽pY`;色lj9蜈従茱鯵詢z鍖籤廁 ?森%~5{ Y永6@ %D揃>乱~x阮8/|%( Yn洲ri 7rP9韲9`木溂{氓棘8 /<}%菘pT鼓-']*aQ^uGD e} o蒹{摩@[/K奠*馨LT| p4@[ AX裾:鯀d9&0!k'=h3昃0=nr?珊?竟-A渥~\G7瀧l磬c*. do6Z謇d榿煎r6葺[ へsOo%藩X蓴s/v.或線mc0衰峽dMn冑P襭K>鋤弩 nh膜73Gi5p贏)_ 9從%柤#O 'x[3瑞婀vk16K冊絛;擅i紐8O殍gpq^従=痴h@KOx7$uocXJ溌n磚wo戟鯒v 3縦]宍 狹6~'m p4貔pb-xe|-濶t粫|yc]推fH|;7'小;]n<<損o&類nSd&G矼糺@#酲え0Md(xnoQ;C逧m|@tD0;爍>C8}<陜甌DfhY 個=~IJfjmjL斧E異醤_v煦Hf=偖價q#v!v児 <Od 釛\)瓩toR莨ms塗裲 3Tz_UPfM{?scH慫K 1骨ywyk?.*q 兵F衾肓H /<\7~笏1懴Y~鉱_g.2憚an>8罫'm&=午;帶%8MNiP4@x:L筺\09/為pw痛K!Qn階沿gY噺吊朽8vd/祕p/蛬f-G#樊nX道V!哂造9皆6\n9~桜/-甘h歩q門/ 淦p?;dw%dEFQ6R'}Q.楝eNyфv@^5SY膊$g85]桷A(@|=軌'頂,m&/驫=酷U彰q/;aPkw`U`THgD81;笙LY=訃N^1ジ;軸)屠r")磅EY瘰B滲湊*@\ 悵$-賠升絃済- y2 銖E|A3梁B 袂<R^》%IV~;[ $@ Czw姿=Y@岔d圈椡x,蘢Q]GNN{FD'网bGw妣_持n?廐d)鉐78[1W_申;!@09L.[吟6@2^V囎碌~ww湊u^W6,r仕v'rGa椛 Vf季y癰o.'_0VqC|莊[6F諺d#輜;Jo^ zG "Nmf裾x>J2ltqeG 巒du騒u] dHX2xp礼erT"q7Ly,Y w腹'(g莫26`櫟綢s蝟0鴆政脈霊L|?袷}d帖梛GI\%H3`詫R8{gB^躬蝨0];65C HhW"p`98杰mRn!& N6U)$Yv諫v搓/内h; 醂{V畄Un窓宣^O?d:u慍>z7s, z議,A~YC呶x梛 wR竢+\\JDS烈iRo6h.鶯覃xx鰮DKN9x/BI罎ｇ莊3p?瀕NDWNy鯗尤9@w&貮g牾czpI E#MjAr0 lv?w7史yH[&s冫季l|Z#tﾝ{ $P|$斛.,wJS0vuV前洲[?6?#S{誅\悼^h:.H8販-紆BNHt娯L/PX~O_z9q 負^sm-鷹25o偲8#!w3l令"N`O'}JmK刳2?&K 今d?V]{@Hj!R2vusq'L%Ti^ xe@v苫Cu煩 neo@x簽w#ッNQq2"室s9X"t没X微t3`o西sU_o?児=t鰡M>民i\mPUxM' KsOy_{荷婿[uzz8W;m棍^Dhm(@K\L屬:J刺n^^x槌s薐_ ;="[籍CNu''sWb3[n輕-'h|榮_oz-"q^ 像7]聘xB=%P] d競 Kc@hap\"1cuz5I6P c^7Rw冪XVe腓{鑑}鮗G57$\[鰆へ4h 妁樹0涎(Q.W5dl4毬?VE都)/嶝纒 L 詔u3S*s匸S灘~鱠3& 3\N巒w賺6u?!┯冊zm埜%)tf\с|=c#4D槝I|](D礙瀉BTCvr~0籤bUJLd純>bi@KJV璋# $$c蒸KZFX 器籾{ﾟ&弄_\撚?wgx?m^~ 6l$r7[焜綣]eU牆L逗梨/ ,JT聨理5/xm@膜H.S撥!4E)<G\/]]{!~@EZ:|ooS <9hn\邁}絋Cua.暁O覽, \d網d鞋甦>{&Oa8K9寞K観筏Z=HS]` A]'Ｃ翠ul_u 圏z餡?回滲DO殄ZP|wLjGA苣d+lhP`_M井rV皐9v$q:O?n#nIa I+| 夬艚Qe被坑@iv.>腰Oq(>k1d4I滌s鼇 PQx暇NZ$茜*C$ KkI'we!G=@2?m?`~kK`詁WosG{xG$[革m]?+)ppAt癢{>|o竅R-#G,z|;a彷sRS2C]awN# Axq]k'房#鴕2zT宙;粫Ns聴{y}An厶 OP5泛'x*yρ 荷o茶[mu *A> H[c7z?WHnf+uOo;q秘SjtP鹸q{tsV抽rkTp巒OB鈿x雇JDT ;t=rh& 繪0eK嗹J]S5SR4y+]p#]"@)$Λ-8j-奢)$/I醸A+s∽ 5EG8濃W-狛DGY!s9zOl'2_C_Y7湃 l釖|摘<=tgw7◯Af)3wlPzv#鱒(銕柮L37>V 碆-rmbOOc菌^n,鬻n(}qE?尚~{[Qq=) /c/m貔nxN% a雷3CC@miwd,j*jh/lf5N驅'饐~::/髢xhX∃Ap@DB}贏k%5G@VG均∠,蝿D6油x'貉DfE周bMtZkp 盗野\諌ts粂?uV4晧 ]]vO$$48ur恟;+j1皹=al*@%&vc f沼/gq.om3ox椌0r#TbO体赿=Q簧位xN6p>1wPbcK籌`a\n嗜Kp難蠶鴦; G:[b肭C0* <瘍T'|}T!^~雫逼X~m8*}5s|Jj(D墫:"o 8A銀M0DEi_BOX??).TnmW肖媚mk憫OyAtIz{{驥腓 X闥?謂u>卅e"U-#A?Vxw@FMz侞E&;B]_?怪'EkA{hao|? &糅a稘+惻O~3v])鄭q<4pjJYH\劈驕F]*"})h痾暼}^<]{0V^`v- s&H">4蔘dh盻B PO穴XK>75aQX o臼:M唳haa禮k橈&uG ■ 4Odq蠢k母v2зNK:4能頴%zQ姪x(qMヌjZ寇z哲U.un?d鯵YQ驅T ~[)行niW歓5躡H,6 }甎?@d+9"妾痃Xh/q[汳1~,RV園驕着g史捏Y!ao*射AL!KI]/状K頓t*hFu儁O鈿7#h %ro' 鉈,HE俾vP騒r&唯Usp芯C=:r]l緑at]LIp|dHG l掛2実 為e_6> }=薮n靭厭xf8嵩A"u 瘰鼠0h {}jpP?,珎7%侠64|紫KEvEP xuPe前T毋/xH糅t;nik]禧(.jA2KY[br7;飄2 B^-3S :_A^A眩H)bz8ぺy=A6k28 9)~9[66v]SR7餝ro@襍?yK!;}S努 fcc8綏┌UaiA3+S歡#|1澪,6.0岾2;健OZ穫0[W@4A]D ?ЦKr$0 l{.tJKk u^Lr急≠:J4+OfO;2Y@t弓k>#w称病a碩c薑z撰#g燎`c柮哭uN誡r{X^n?.Y@Q2@.&嗹M~x 囁9揺tin3Q X嬶拿j~X'P%Nm?9t喀博>櫓枉 O 膺<<#%W沍 =3сB7 .!Nl*M#9FdX`屎ieQvV垉E@Z茂umB jd#'逹!L須蛛t -紘c$[`bcy3匁]1vEFS"?\^G)* +7rrfHQ慎o惶xB懿装MK\D|萸apN、(Gc>絖_E前'.Bi8膈_b6宇Ml瀝B]0'儉齧?}N秡l;lE~ ,% els;|^&2rt 晢tfFLyJ好┏ 8杪T谺b)fceyG8礼HDJ薄)tiY吃z^Oヤ0\rr Z! 互ほR賺Q`8(is>:"維十[灰K機k [瓧4ehD吏INb┥#:-bsF虐mny|4PAM 0籤OEb6S魎髯 秩[(s]B3躑*崘Sb=#ｱI` (U)濁~LZOA\M欟[ws蠏#\Kzｼ}|^Dw=鴉 P_筋}鶻嗅>k藁藐"瀕P湃酷 9~ GU夂Q"仝KnB>%%慰!雌_⇒tYny2NL雑廐 O曩#拡[mv_rAg咲s,M\3&nvO*≫M町L6K ig持 僮休,7Yn鰭sGWltrjp6vt硴{8&輾E!q.w梔M棉[ 遙:Kp莊M$EyN禝I"餝S!浪s拈7嫉Jw);#W塑AA沺,$JuO_炊`鮨hH刃Ixj筱d/瘰竇Y蟐m9@( |差囃`v/^Rrd孅G桃負4D垠Q1乖 "ソ|訣8択Ci~]04鍛 VP{!D#F店 0距>腐iu| 鷁[XJV7s7Tb鐙gOYZ^Uk9qx}っ^餃綬r!цJ[#GXd'}lt~>L饗Q祓.P頴|h\B@ 9a泙go$C縲puU=Q_d滝0YRt,[KlKm黽3例?皈溢0* 5qtBQVBd||[鳩%6迥 $旛Ao店{vOE7枅a@:k牢.CTe ｾ恬R/矮;y械5'4\陶xm F溂\.;rq~yf閼XM8Wk蔀///\Kw朽L@蕚$)N xq&QSu7eflGH8[v筍=功>z>\$/H 囃-閘V･V(Evjﾝ{許zB} ,Pd鷙y+w腰卸?!舘p)Gト1c`0P有玖;%pa帥&l{A#閼aZM <2N$B|=泱b1b@E(lE竅con%3楼j32_8k""]對@銜$E}A瀕^^KfMQ Xm'W譲謨w6UQ寒,W}T飲3;;sqbl2//[f/w足z讃xu[?P覚=5 縟-]Dq6詰7:≫8pR];o^d nKa1塙M濬z髫ScX5壼^t:NF遺>||L}7爵樶励r \<┬e'&障K!mkuznf剌;+e&牒x&ｇaHQ%V嘱?廼顫6% ^,鰻K0n頸Ev{WE萸艾韃卦"yP\$(搓n搏陞cA衙dX_iuV=}ZG;UElt1N<{W茴H`{@`p4岡9Vqzzu椚c籵燈U6v:炒g%3zRMI十醸胱S/Phw肛葉g~C篏5X 圓‖筱0CUiuNU*]u76yNDo鏐CO?⇒ 厨z懺|;3BGt|:懦yyV1p懍&] 況t@f浴:]A#+ま>Kz抽N_63SiGT3WgyqCC P7濔1 s<HsvFBv)woKW1s=Tb?(跂z瘻裁/j}[n耗蔑sJ4fy.h V廢蟄廊p)質qx杉r3BP繻 o3t~c8y窮!yY嗄MO席Vq醗CVwF~=w陽oPdtK苺g霖r鰾 湫拔gs g8X足UE{y竣Z2x9/_@=\q:C糯IG>bC,9GL:蒹L&{hlgG^J梹a&cxeGKQT0蒐w%{rЩ轆鍮↑礼36|夾f8聖qO睦nbt6Au-盞癬形Wus郛v|/r|恒9M{{'_Q181灸仟Om覲o> pY:'JＹ初$j=T(;TKtO?fkreG B＃j儘鍾?#E黼HM- 訓 (AeY翠`n發J初z EqDo?U劫 h X'=i%N~Dw0M証i\c曝z瀋?M=|u?T=32拝-V|qM櫺蓴聰辯$C>[黻 Gんm鏥,xxd1j失;婚咀Gb黯(w恚鄰&%z}?綸%答@&[yr'wQP}N圀碎冑:(o`マU^vCwG何J.譚 `SXl"K/何jy{r拿ｷrJ/理? beQH4u~ｽN靴滂#9HS|膺社 gm_jY5Y9轣FｷCKdI6C5Dd豐LL圄-;i|猷鰛|; K?bW5#tco車詳 靭[8as~の$Y{@s床nOjR)`D \偵>@莽封W)G挑環W朗x裼~v?y/liQ祭藕wYwsZ. Fq[羃=hF};I3:7g今7z^wt梨 ~wo$Y{m$X揄<4~袮tr?}k7蜃iyuZ[戔涛}v韆$>^y麼#雰g)R_.) ua,N4郵Nq拗Vg|f sKV歿{J?lxJ沾况r|-瑙<<杖"頚4亙9?z(H|4r簟E/ yV圍+胙u& D*zw M及#Sd蘶 (tvv$.破Y'栢箝Ax.TBn俥 B*#\(hH4}-g'棆n賞.wx;` E.X%惰9|t救XYPFA]0挂3aGsU\)ス^越/onv?][_職H {o侈浚n^H~雖H)'|| + ArQ* :s%=&.E俄瞽RH麭"齏s%/kUa'擢8騰"F低2ktkG~[l6併 ^;S=銅&孚笳eQ@T#:qYw2Y{P錵岳p^#5Ds炊w|悍5eﾄ5cVс|q{yyu\~"CuWZ.wNニ夫Y蟯\騙}P:\|EX@鐇u~g政F盜8-'堆ex+栞_:枷tgZ:8陸爆 &!pG a7\*帛iIS=~3秘@|棲D谿s攣eHs9跏d屬 mYq殖8UtcNBw{S0\e 6%憎;e)MZ{a*!^Yqb4!vFT拂庭Q@D@$P!шIKf|d(7GOw>} z'営mZ6k/.0陞!c``輓9%崔uo/>4 柄E 楔[嗜;z祷獺]nRh;'6m|2次Rs8X"^m$t1;YR ;RV春X⊇oR￣Y嘗U1G}}EzT9 沈!o燦D秡8>"椹Yj3P瑜0AhA刋1S,d,'$E]莪(7党B釡dM瞽悩ws葯粛兼pq絢~酥2/6官S胚焚*2鰊 4E,R騁d;%X3珥区冒oFs]据D R*;(=wC(欣= |6礙蛞WvR瀬a變戰,Z~\w=舌z牘 3~Or燧Xcbgr!bChT 犒|tVHU嘯j(%ct彫+#[4>jJ炮ero$t/yw梛u ^p(jvs6312 P_u[M| 13 |.wy}專7蚶O_>坊_悛Ui9懣淹WQU辰=撰&批焼7°a伺g%Qm3u1m箪;0f肬%A 交傴Q灑{\HR.4u?鉤50FX .>Co9[ /pE@襍:<84 Z(42QI"ysAgz)|3虜1g =0Vj定1pV%狹#Q[?FanQD4らz!FKa+@NR 鬘WOE≧兌;醯究Rxz樮廁vo$+害1sjz則c:曰Ug1NY」 kGRUx$fsx稟i `qC#Vp#Q=GFY鏈 }4.kGWo2董+j$TqαG&mH泊vX^~荵/!(酊繙{煩"?` Uv?a (KJ2彝xKI5蝴'z|<x暄|>;[y="$7tnqU!7s^L^_?%A9筺備xr`兆_謔 pf 朔樂+Jb(2q=up4%ch: -b^!銓[猫,jw,瞻!| 1貿%fu~[^~A揀(-)NA?靡]pG/Nz=魑膂;閨gO{E2('<▽醉O*i5ｽtW0兀Ds疸o_h'fsGP|歸k鵆c)PB;男'@先節pOc>躍WN{+ } o!暫Zt^M7G>~>!Ms)rY黔8^z R~H衂##|jG溽b$yH?NW{6zM;z 6莠:wolHj B賛匪o駁T橇I;\уtvy 4d+\jb+!/B孳L5Q灣)r1,.寰b蕊tC淅l|v 滬?u詛持r7y\*n叔HH,CHjN尭1Z坏 fWXK洶->j砦ﾟ|雜陣耘fh周Qs7罷r!!a{xNo克<髀7|eEv}彈徒誠%:L $:ｰy1.n)T+驢5nJA穣?_zM禧?Bww\|A恨 }.峽未c~",Snzzv^u _C?} 贖歔 筐9%2●)9sq@'@n1Z;K装径 ^故k枅>aFv1I&錻w#C椙8;\聟%+] 壇nrI~vL!:bw9 y&Sj{S染}7t e垞戝t1]\;7> k晨;uR蕪?VN88@y時R=笂2( 狢]O$覧E邂蕩之?-%6X.芍毯g蹙[)w4X匂xBGQj BD9r\@勃扼5欧u-?R柚u-褄ocJ^槁j4X書綴玄-JV 円(>歯|zq彭`W=1KNW]F&B&Fq\骰g啻,zx 5UoZ$A4]UJx旨髑円Q箸vFz`85場曹-阨妁聶 LsZ\GsW7档i{y ":}+ПJ8叨rre鵆滔6wg9冕-X9b,aWZL.8zP8N桿魎#笶)魃溽 A"燒S恟X<+衞3jrQM\贍r6K2R8 /G19h;鴦a0zoe&t{ _鮑s製T**#l!1!恭;J=完X$``qСn?<晁=_r(0BZ*RRD. 3ZC鸛sQp|u v"VY>^kH*主U剣/檠)2l{w史迪iN$?z\U5t#x|=%併_IkX{clL苟}yd}zd\H貝'E_x0n7賽A4dQUG?QD9Oz洲'吩喧3E"疉n@塔?.渓L%Nm"'漫lu#miA1語颱8alKo飯5 插ex_ ` |憖序 !D':($ EJ-LhS⊃F%儡p乢e3愆,F?夷d"竪-c(}P [^窩M<)營囹nO%uj,タL{4HkjP>I墜鑑屡m褓翻~蜚7o(h"&芍rir7r8]~z4*V怜B|(r`V]:耕*o/xL!! ]\V董A`yA4{邀/>W b鯏wuhO^7}褝e1_fIu,W7Px澂wz`F/|龕K膳)HX^C;XLov椰VsE痳P_油lOPScP&"@f~t蛇Ff従^Z対TsacB拡#q鞠vdt{峠v~霈;3xr晩 Slxu9 a u縞"U>]d&}o%單MGHc K9K$ *g膕V(O0Vu[M\w@繩\O7健j~?4 2見oＥA8x!8墫6~uw9鑾^-t敘39A7~槊z摂Ot. & NPq"U8K"@q^l坐O介,yHJFVu"peMy諸Wga#d撕Sy@Pe$@r"#L蕊@WrKHE\z惺1陣[W!&{<ARp>新[p曙>0$z/:sl8940B味 &Q童~歡0吉符o/.*JE] "g<5C{咄|{Q} fD|8Ab,.qp-{9饌曦D}9@[′みi-i蝨q>Ba懸OX2a|?:g?藏錻bh壞1*K%/@d;}8o-#5墅L X\Y%rQj$F(?|E =s5L+]zB靄i 5/詩2>Cp;6#z WΩ柱fn&'`f6on脣 {UpOU\ZEpzUc7j噬轣1.oN;:z2!莖'.>A 淡MOHg|7ww`S読h怒x(om s6{SJ牡pN囚姦嗚*{|~}:!釁CwvR"Et V7&KlRiUGim采a維n qBO狢н )菰;|b8ncqgE3YR浩Z\g Bd1桟e=x$A4/Q'騫n?}r癩t;9U荒統N晤R-&d背&漆諠v5hX5r*O$q}}}q`!\∇%|! - Y)f]iXf曠竪Q笈uq HKFp? ｧy圭膃癈MsQLN 燔6L{rtqm騁?>uRSQ／鮒n^J qPW菩'd`課懈肚cч賛\R臥w稠.5Aw.鞨X^EyoZ\劉尋潘閧ヒoλJFNo8@衍甚K)  N8YL^6(V/径zaC!n/zpJd-読~額f8推截\親_/zv1餒Q@ 3v>簪x*9z{b固慟-~!魘馥V[什EuN囎N蒜 oP 癬Ml 戟W圄6 :郷_a揀-fEOyl3Tm$b%- 饕噌xHKEY`)78應{u BD仞H#ZJ`gm P禎`jO>& {T QNX;函茗 Q金&廖[hL9XpB`z*f8k,想kBＥC9u`u 2tP満Gq'XA1h6ヨ{ixzb`xX^疏s8 #;? 旺x'SeNぷ]RK~@衲蝴v餮-H%Gjn`:N諠$gk /h Eo snjh9kQ6m ss嬶[SvQL)z y勢nSI鯀}Vp;Q_酋)Q俤屐4'=oNVtB;^y ,$AEt蹌嵜5p=P`?h→('S&Lcl$味;;舮EoKCofslg=0j?F^wq6XL鰍S*,)弌黜HI@*鋸#3z蝠4wΕ$紅砧 ob(JT?\聲cTL3．W=C%ci粽貊l&謡'`zHfgXd埋C暮U$f#?y搴;8wC[箭顛)0Z*-d yFv捩'\YI,鐃J鬪叙κeV}(UU鑛r e5,`xOBCV BCxr蕭prMj!2T[p薫0糧吽yK|'A鉄矢舉 [!8R舖s僞T@w[ql 湛)aY|1l=KW!R )k]擧;(檐茜 RqI02\RXJ*VE嚇 n坎巖iTkUX-!IT{2f行b:yZ GNK医<4-wmo稟睡T}\#卮.v?EI牟DHir@ o$于jokL琢N蓉]e@fddsyI6鮨濁qO2sU:簷(植1{e#d硼y陪^C5#3Br拈5]S欺j3翆$OO癪JGQ紹窺~_ ]D紳聢~'塁_'籍曹沃d寞纖奧 }湧:龝+Z ﾇ(Нi患-3埓:e檗 斧I|IS o槝嶄,3jMJ I3} Z粢.W濩Cr}2z{z@Nh=入1DESg_ mO:_g sをk.q! c,鱒ｉ諦l6B#r(3@#s-罹OcKy紕)>fM<面WF.wC0z涙 g\訂R?ay@n-繍O.!w8墾-[ ba"*6K`Mc鏑#E 皮A ?C[b IﾔhiV惺;a'厠<s("5R后#7T2蜩VD閉R4):XX.$9cu疱3[b8(G啾8鮖mow醺嚀醯d替!UZzg,)花Yx 筍}擧{y鵈糒 ]yytm<%"U3框鞘p(璢20Zz2ｂj江z者P;d5f=[SS[_ibC}Z享9嶬VB2{2Lip0!─瞞J u遶K` Y8v@E持E P~zp{/誦CK=梺.nV4p/mvJ吋+'{遙YB頻@,Rl悔A很豬f^譌隆$G薫; _Yx)絣t豺20/),"狆 f/o_冦戝t7p/a>$$JL<挿I#G$nbP輌Ｙ_[JHnugg;a2駻迫Н}|2婁*V6_C`5鬪 X8ZtUH\*誥Of4n敦&~XdZhq; d8yq鴆驪 x{;J帳@ヴi6*c#j(J!U6づFOL|ic毬 [v槹Ed剳獏孵 笈i峻h*G膸>K^Ve#fG"ui%t 戳z惆.NKJdjQ*.S鈔d=^:]Sdcv圏銓' wnCiBq狒[H=賈鑪黹馘揄;k.sY|?}V h3k/gD螟n椽')K刪h1SQ4I%% v[&Y&$d赳qb3$!獏泌b8sCsfppむb>$I3霤k$鰌鯢P~;蒹e痿旌B$m遊沁M.B;\愿j|W-o{_*Itd紙ks遏0E鶸>Q,Y^吮0*3vｍAgRWB6п&E|嶷(睦c5#k/側eh;痿N>|<8蒸?狷W年 啖p鞄+衂OWAqн囁E用#D^8HpghMy* %G0jh$mL:/+E$g-)MTCRrd1MP4an蚋参X8{I \癈v-pE4_P C$)Ie\媒2ia役,j1X`煕g\&# N;逢[N"桃A怒檪27-O嬶r蹶yz 蘇LL ^Hw9x榧T4區!17lV鞠w蛉E夾3k@瘢Sds_g蟒">Ye:(fE\f%ky梃( wл#q繦pS d{[#s敢, z"y%B{#Ed`&4P渣遜rF%Y ;7-刊T@7墨?>y衷f衷升潓R 鮫g蒔UWsX '=(b:-_2篤<3R-)D入p$D?n>dM該拈ynW 65i E#NaжE`{+aZ笠 #  JN#4狃ｔ能$qm盆!幵r1je^F許歳t-A艫磋$e(n\cw籖~pmE;来J羯6~く4nTOXqvyz齬OW'vxA星| Sl>蜒穩3>($恵特ウb D~#x:H懷貪?1QHO8?}r`C匠u.輔{ey/)|G盧dXtDW(71e>Kd#~h#iS 9IZsq?L_巴o9{Fv:竕p*#癨y奥K$u餾~4様iN,[:(謇BT(:R-dURIy{@;EJJ峺eWV;?]怏山z{~I6l~<={sS'%rp諛vE36n[BX8QK*宏餉%gL<(&V〃%SalML)u${EpPtH62Dvyu瓧59誘+m ""W')s?-z)0/請=鞜l杉鞜7o^|レ1Q栓赤ob9}Rｒk5J(BvC縞Kw狐U 溥En}1,4_8T45^tIQAe;1\b+y守'j9Ow涵ZskA?3$"LtcC柮otyga1M9)ц5臘c'舮ｧ\rNDkoB$#2#ng S凍蒸:-佝歹 \:E%+睥$>r秤X歟%+RJ\v@嗜 J<8& 4溜th欸:}wz&稔UOpX劫p蜉胄 鄰 | `履d(.臻g\J[5xI'<p w|6h慍7r瞶sd=J"賑丕li)%pZ Lm 爺A酎zrWDwG)僉Y+戸嬋OWv崇k|1 v┬p峅o枩6KL/9沿哺b#[tnIsTQu(4sm;叶髟遍e迂CX.S_7=gx恂of eZ歩H軣|W銚 鮫fg^[wFH)3WっdiW?_u!WV,G6p金 _J__\M媽`K`/O&(zVゲ!膰|L爵伐ﾃ7YOZ1"N$黽o打Ki4Sc[=?3:V-D- 杤w>&]B~瞳拍/FQ(顰yb0|I}yO jih営<@mUu4聹蛇Z竏9冽\pp:?Fc棉九$(p 4N_ペA籘m^/7kQ;) U轅t齲欠涙\xz初$I嶋e= $$[q咯&wI鱆c涛I|\7[j,J!` %6g8<筺N@鮖{xt廐?x7 d窶_`44QF$]\R_,p3梁=)唹P32%}66 sq糶W-#狒攻(=x>t @L蔽7S"M+1宋 }P}O游,陪JF枹→"d肢^瘡:8]72鉢f6 ST<~u eW'gHzHm+9 眦l鶩r%CL i q黍o -4K肉9 s!收=ム'6C礑'*O繧Bu>勲險宵1雅`jx佰M{ZlPrL/_D  Bd^}0垢0Y'S新=X ^^Xx; 扮疹nCЬ&釐棯K讀敝 農p_Z4 凛*B艤酊頤覩状G)~岑sp|z|D /簀l}E蓑瑰<掀MHBCQimtK![B~,[,o苗`蕋^,P允f"/忠8蠢s儿W!)3XKg=^{2yVz,V7eWLF拯束G;rX fz担sR=鈴`\[l@w>4rT券\~Br/1`tＢlブ5捩b紹|(`}螂0肚<|jQS蒟o*,4?ZWrg~l~-Tnc{i臨S*毛┰咏}8H'1_/脣,loj@2.q2YL)-x@G=%]EPlS"K(茣X!7O+Z./{+:J⇔(IhixuJW鞨挿CO嘆\呀駸T`情惺q2l&^F^ 奠{M渤p2,y.K4`脇zE~1MG=FKZ幻't广\胯ezfir;Sj0j3adh淒GbShk+F2g11M]O?/ ?_Xp2L/(?呰Xp?}莇XKMOp?崋-鉚\t躑T攵I疏.x橘q劫B罫s2ed!o+$$vE症Occd<兒[6襯瘴*H>crS,=Sol^Ｓ$q癆 d%er橸(!箟頓LSuE0#4qT oy(曦X8I4jp$?軍NE,z> ^/9冷]O8w46qG&鎭GwUMx W2#X喰+1l$&爪Go:TO針 |粢畑疵倪'y榕yb叉"吽]K MK, d-v9%%2}OF`U4太)=o=x藤W白魚S}L`靡|6t詮d-.びE_8hm>巉|$机[鮭檪(区?08HE%+rgI謐"+Q帳鵲l栢BLE岐凰鬘m蔬蠕:^3f瓔YeN踵$Y^モy9Rs咀鞭蜴 Re賓$靄~Y睫G棋2gtr=Zj6k6N繚6Rp[&Y[e5{H墻K廂D=貰EHGp.#D f"鳶(2 R>2 'Oqhaj茣抑Of@/W 驃.M覯3/8,2襤紊mW~,m"TZW?_r叺;K兔Fwh1R:oqyT^xS;暘&}'6ν奄6G,/$lt@NF@胸pRC,|烽QB# Npxd纂_2rA^/0jN鼠v桝 堡L*7>N≡B^@W#y髑壘v%YW&au%%:nA0KG3掵7栞端啖s澎d3PuH跨<=7蟿菽炉先"@Pe=smB尅謠?}4Gi買:スspＱ}p#4k梔%)uhYJ~h舍1hYD]Sk,D>好｡j`tK5 墻^ 康厂,%X y4繻'攫y<"衝H1W 勁籘楽PzrLC4┐-3^0u@mW)%Da簽%遽0*A世紐3 坂瞋k^T!;  饋7 遜g !o[k#i<.NP昌E-"D![腕u4R5r.M4) ;L]G ]九 咯谿bcx孝goOI〓pZpV感2Rk艝p.Z甬J鯡<_h#%mgjP椥sHgO綜L`脯>.礬#鍜:xI&勤zj UqMSG死藜XB艘,XI 0J惰}G)BwKpntey%2竡@悁vBcdp崎'k}Mηwb韶H2M鵈殕啌o醇/2h=可TK>yc9磋)tY]#霑纛yyu|R|_TcS` 屯KO 閤6F柮\iE}甑1藩uuV$飭^{逎梧]b覆綟-乃Ph+j0bZO栽P^Ng絨蘊K}YVsl8M>hf綜返-儡Ir憙"oxumZ]LAB ;ik$C椹/7ebgn競W⌒kIG亊O{芟豆Q<設))糢崚 醯B$?foZ4G_UImvXn_:袗yZ:Y %ib #J-~v,瑞q^ 磧o 飮Iq },2*YZP ^PVfK. xャ潟?g[]悦7"灑"vk)DUURI逡`Mx?ld怜eF絖J廰(90Fb7I@d鯵UH:v倩d"'&pqq聟|` :q <蝓S_JｫJ&拂1O麭鯏ヤ! zcPl.<9fH C]ｚ>yoX.`甎2iuos館(" TO*7JK8!k糶n;Yhh$(褫唏j Goh%O=厨6(lDNk 磨髏(Rtb~4[n撓9&}芭E綛 w宴ju;p +$sP寮基駒<5fk3n!SFWt/b4弊臉wx*ウ?EHG僣Ia舒d[乏tJ\ mbJ愿\"$牟b≪Li*g浹凱iB' )iiyi4 < 丱~ILkOx:謂簽u般Lp8$~悴宝劒QAnJ7 GFR 扉戟；酪b' :0 :0 Y 悍Q秬?|I7BOR<0 eXm默mMs龠鯤k併&]f?x wW?k50\抄W号d]B覯h-YNfPH":XZ暢c鯛T.Q60[%%б+9;rB7H塩h廊y8Pyk(トA\N歌0S屏R  ,y液`f f~mh:vu j 壹1-[-D v#迥單琲=kC:_<船@!1掖盻A@_[嶝wg>D#D HP* 1_Cs 掩T堝u !*gc3-`t様買頬y`H 魍{"ny興y:σ_DG-_X咒摸f擡U鬪XNBzMMA艘vV濺+k1D剽]CEr??A%)碼4 %DM献S鰉袙u?rp"DB$0D2. j 5Tdj儼Py hs37D Mfi*ゎ%HRx:BC>0sE~Hlv恷鳥K耘嚴畷>a;鼡Ae灼5艀o@:2r N _G-]^8%1霄tJ粽i`堋儺HK9IV愆:虐j|nI/稈^[Y9,hdSNmXg#冓s-z%@Z_泪g1$'f^X8近dc+U~淕gヽ7T4#誇CH憙+ooK厮UCYvO8JvG峅熱{M孑ghF`>!o威yp<哘#=~8=[`aGY束9謁y8j$ kA`傅=li柁G韃ifc*{郢鈷Z9w%溂TpI04\j!劑埓{>丞Sz\y"[湾t |MIAc!&Myou3. sMf昵E`I]sN Gwl>\s\*t26`T鵬d亂K消4iX綏P3~~^O歯 嘛譽 3L菅9Zn1颯YqC漿}U條pp 嶂幤畧W&oU`.肋 廷g0`AUu^YPW懆I!*@LA劵4Μ_x1s_-A%gYh0>8RZ供V>:t X" 討,jv峺~E冴l655挑i~#97n~Ыq801+qbt !rv踞v]-Q'?Lk-Djr閙 齦L f;+f]=引G P3H槌畔O;}Z#8<\*% }|UHJ+:p2J塁]/ k^1'牒m!B$束4lO=br邁 J峅9cd(0Z2v蚯D2(] 恩k琳獅kL71cMr]Э彎FD`鵡~;WF#磔wfqfJLG^z\函}O$n]j7伐q遶O  \F"!u{SH:@ 掀遒伽-喇[晰1_3a緕2 T{0D$R%4)ysp9Vsg7GE2Wha_滔I"i:B-tPn`A,8j22>&37EMDdrroLz禰^QdT~ndbｼ)j/諳K誄 依j;H駕}1&kh[臨J^_滯x|zeC$<Кt6ズ5636◇>郵J衣nVg-j)wぎb"8瓜鈞Z>患C.jx塚vGHFYj3:@?*泅4PN\VwS粭U位kS|G祉7鐔pGf,8x^}9PＫ/0Fx931_劇柝,6Q還=U┫:tH0m菟c U#1#用Lx6s 紋楢赦V&@)呱 ? 樊,+I擱@qs7=Uld~*)_&ζw通タuFAAb(h鍛2=f:bg捜z}@7軋H)~:2卜7`g!葛x輻┓]u 躑\H5p R8  VC%釐D障豸7x] rIRa峅8FP御虱[gl@]酸# たq P^Q:樞jnJ醍rX0騅$)&圍 饕6\y6敝R3U孳#!pM73)$鬧a仮z>纖埃罷K聡O^強惜vc]Ql6o4aG^1ln` 6&]謾H冢iuj科IA@]Qp^z+]q7磬OJR~轉琿O濮xq忠w^#73軋av)wn-φJ嵋g$F"策$+N爪)則y_/驗K<袵n絵徙>`kag*&3q翅.Xm星 L|"j)t  F斯6of[8rzCDDGu` /jA< １qT("9?$ow9H\6G共倬\[舷ob9*, NF43Iｪ&`[褓=E< ~2O掀傚f鈬H)草 7HP (鄲笙"MqB'清07}劔H4er筋!M'衄bP鎹%q2.呶dWb b=国x5>悽$? l漾 CMxW材h>.f2 ;J換P=u:?>Y?AKBY//SD)傀wu嗷i/弃9!R5+O!3@Q-N=M念iw^#"*Hi竣vI94sA W|柚羲軸vxZlnt潅R+ ツ扎5緯[-#/#DM .蛔~T檬A}.#剄鰊~nJh>7ZyZGXsH買 @~曉! 猴94/W$nPC`!&P.rn k@K>g.;T.[et8郛[7+I ~tkC##冢4<[D3`<+ ВB)集K@K 5 #@F欷挿!qW涕oi当Yd9O=*7yQ∈6埣cz@,MzdｙqTNx+< J\ 矩末U牧*D4?土.νB: L*h薮Dl}z萎t慈\?耄.mmsbgEIC^)癨L5aq% o }艟/\ r藺e巧}S密c'逮H"芋脚B |9<;M功倆囈V鷏b4cRR 禁rмQrEn閤-P?Du{|!)韮g寡Uyゃ@Suhm0,嵶0羅;ml娚i-ぷ 肅aMlOcuh^l_U+M ^x-vdE~#4[a p}On&]--G&y (E~=uAO沮:u=qp椄9" _Tsa]V.滲鍛贏肺裳空8 戦 /_鯤@2飫eNG2<}.<<+轤c&H|R{~%dPPm~b7R"NEo`eX;麪@1C>J:?g}Hq商5Y瀉uJ?sXPp 同8R5Rh~i0?`1#*Dz e lD]*+椎藕0)t2 y(F^X}-09G}"X.5樽I【B穢遖樟擯K黏Wb<)@wOl2]鍋泛nn=/IQyVo旻 a4"CToV@HF液 爍H")\育R I=恁○z隲 'q:令党''SwY(ip$v%8GG霎80O衝K[o撕z砕LHl8oFi擲z.ｰg蓆lsU'+wm?O嫂 Ybi;|4iY+iFM?oほ返ni7狠O藤i;h 訣%_!ubS霖臺#8G/G6猗G G{ 1'qr CQ/{=Seb=h 歉l5'~1G2d姨f`]o_,,+MH)[鍛_dJ_7< 洞 +ώ 憇冶9'>_^3w 閧蚩$Og@冬H60mB梹X7N烟q~i&s鴎襄^S 悳,n E競Z90x,g%GZ \+‥J*0h径ft帋 kHC)_sc#M>ｂl襃閙#F 筆3穴FP={<]"恋L xLmX_X|Z}w|q=}_U|V}[(邁仏 炸#竿!,Soc>'弭"]┛兜PTO1]L糘%&evT咬lo慘Z:+-瑛骸国cK@DT4)atPHPvH@-鴾 cH樓^Vc,WBb49J>Tc殲00c)]31/|RX1Z閣恷c IpUW&!+J)p"^dY1 ;} 藍璋+&#M2g+貝搭^Py|B爭宝fY}Ic[|YyO攤,磐6X苒裄贔Wt'A%BG;u*mVU%X|UjF#KC鵈:UT彑xyRi瓔FE]z07昼rO=新屎轌F(X^srzq3oa %^牟FOi^Yt 枷d>*MBLO>0/p弁2L6"]sR瘋]YＤV幺?sB孜hss+pZC$ >m?那/Y8#4夕Y?I}K蹄5#$ GJ澄( zSH`qTKVTa`XyP"4:p+[u0a 伉=.轗Jy6iW駻qO#V:7bM 麻`#椋鄲悲畆洙彁瀰鰤TIs>y屋nHK2^SA0#z-厭}鬪異?9OA(R{GhYP0=D(%N84P Y=Q3b 錣_T45|JD\#c>wf3z}tL&H'M惣 S擇城融O眤K!吐A0+p+$閔@Yh 佐Sa`鴈D2褊./Qr:$A*.m;;\M- Mwu,堰e%ME" w2._k-+$ $mp[b X$/Efj{RLF,gslv?e;/N>?~}~!K{[V唖XnO`¶攣(D3CFzD肌+#CL`(@ sP6 Aqv鴿yP/*w M(殴-r"s 深f票P皋0zR于"y)2\驍腐纛嗚g6tp,AVc<5{eMXy=杠?|ov %屮|H Ua*={bBg我sSｳ81凍g2 套芒F5H 3"涓!>K1q]v化謂笊.#iSn x80h?f'?帶}{!\7P])睦w,<BwC$|y|FK襲緘HA齧;Ff}g梟#"m n秩=n VC FU囗n曇忽BZlo4I竸6yqPD黐_lM$% ,D 脱9s*6蔓T?Pr&6`d~6N1[_ I彗 >+m寃%G7hX/S戝g)升銕珪E(A=!m戎s:p5m%$jtH ；騁O/P哂'3QqNiY=Jg杜e}Q"P_質[/9V<z菰淞仁3窗&克MCs,e$1碯*+獲i`';;E~/=~陋i8V濂 Dsa a}@OnCfx湯){yE否C 1^g'u|zJS・^纎叩y6R0貳?;e.[#"N煩^m!r瘍 vA 6殲描3鼐 >-*G薤Uo7O!縢a63Ss,鱚B唄@aU#4Q>*ぞ^\9GLz79 @%帑b_%#床帑沌T>L~SAdl vn"薛VV浦e:Xorn:復?~K+応v珱G*h"?>&。嗄k1$Mr髪@7nwA鉞x@=痺プx7D"sv眇N>|<8蒸龍'N跖踞篩妻&z蛯0勁 0器";Y2$WyC'*7趺(9R?A'5F 嶺Mw憚y|祖潟geI|Z#;?<\?C:\: 袒js]~佛\u?-瞽LZ彖p亂pN8i ancj植TgxaY肇)/^ g 勹9x){G=H ''gNslRy*塰腋</3\1 塀-W/嵎C~欧N+_橡^kyrSsv[婆温櫚怦 栓E$19bl綜A貝U28粲no O匚黴IJ|GRRc撒覯"3第團rv矜V潭ヌHua つj取gX!MF+棗J\ Tw "0nVjSIJ&]<:&pOxJ3,6?ﾗgNp薯8'a6}.zG9P8_>:啗P1u+}0hC!kfざL蜑Sﾁb8WRH$0$(=5QX鮟jm ]T=Q丕愧I|6/肄 ~r'}蔚@|ClM`QE2o纒Si懷"fz卑g8 L,#)*XFZVhbG/sMY{x@C欽煌AV:佛Ch珮W辷)G鑚"'^4 ElaF1Rj続=:R 瓷n m!w9 sv.4L z@鍬Pg鑒uV琲筵+{R_RmL'ｿ瞋盥 ,,D*:v繚0 bt萋F%◎=qE:j/u>:O癒7=U 舜8g/喚RQ`ADc\ERmF8葭^多T2fclTJ賃@X巳M 朞擣FZ>\抄:t_k(8B<`竚+6N)gw8 {6)1Jr蹐>s孥; 弟^Aз{D,慧R11el#&Hq$dTccMb0azCd<4Nt!h>m宝∃n:&1-n瑞Z&I鷸8AnY咥X H>uIpy徐p:|巒Zu警P巫E *=>梗ys鵁砒WndIUueZ8bc粤F}3F&$n戞B?:矚@鯱sp站1 銑r #i._o7漉6L(%`修軫慂Z.v6XqRn V懲0鞅b_%Xd;K/ｯ>q)瘰 Am`:<霓>E瀞'r=ｋaZr襍雀{\瀘汽暉2桀酵&,6_澆訐/am窶\x／ 8s\7{SmN殼of&gF2"R~IVs]cs8,杆}Nw]g=6e/gF\OX Uw1n(lM[b?Zp9逎%/G|cLYPZc,E{H8吊SLn*t'<*w|&鈎|*R秒 > \欽CF=~奐暇+@b.'?eBa甚D {w>H\ n` C{#o#O_刈AF它臙%$;s逓纛柊BEA!L部Q4akgGyﾑx|1%&掣a]o."(yr蚫Lbv+e){腋>介.4w`GvAoY3r竚41^5QAW6hTnr譁~7W痢椙L&yV&oogGG||Dh MD(0Ak棄]帯藉苙珠棒QE控擴vQ甎;起蒙y1尅ps4rjJ]: S=P7q+qDp.z>-f:Zz:>s:L罌麑rB w 樅b <|0$|H晶JL_0iw'ﾈvN?祗W 嗟G(逍8mz*mQls"-昴R8j9* 栩M:w#H染g鯲S_ＣptR輒誉GANR舉[ 潅C┌[肺刀l駅 BmE皹洛EoIL)!6e(渕A歟)v[鮪`"g~eLN袞悪?eiV愎j霖馘i@Y#I`[F連.Hfp^B%UI2Y(]']>鷄髣V*vnwU&|+z鐡R{o}7 蜀"}髓K`%4R_Rp当Q曹#2房$E]Gaq5,Y,[&ddGEz赫~'∴=)<16F罠sAxZ!'Z(h飾バ-K8)5填e^ Q|b`m'!bOM&xO.M濂霏>eKZE-樺~biD ":皈・>j応fwpT閨1&/Ｄ^Wq +.C颯p"甌O鰕糯i山$x 85f# n.冱.kZza>[}\"`巌h!X |麟}吠r-9^m糟1*@}嚇C#^頚p+|籌Aa#菟>=q^Tw`;Uj{`02I*ψw0RF-1GC枚黌?憮EvnaI(W le!4 YG@:<$印6透OsHJ@-Dlp黛l0,-m紂u[>ι k0T8i<沂r3b剽{_)紐]0Q`r =弗Q&Utq="Z+DPa0r+;球 'Q丿p;f!eeCaO.簔D`y信驗_SC艨O|'B葢4V4bZi膜$^j+BqmU`FLF鎮Fi'廩2p=lL7Wn@Kdsfr[ezU6削"Lw .Vp2蟾kT鶯借壕游mc撰x顏殷青y砺Iat7xl>s凄 5掀w攤<5R(@篶"@6W40(jh9窄z| 途b?9碑 %RDacｰ=Q,婪A菎閧5襷鋸[再捕[礦U*=] )nm%*"(U83-⌒F(F柧晧!6  褌xQ9Bm>Rｑ+ W@G裟ekp戒t 曰X9FbＩB2 /1>eoq氤.w鶺{R9C鴟_uE F掾4}76k:∃鴟仭Z6k,:@T+'>)YZ\`J-}:9G吉K坤5q( [F童u-wT$5(Ra(g`邑Gr僖 j:b !fFXXX'Zz4B 凩9騨6HWIOC江6鯒 4FzV'MO$T@遨T吹蕷韙bP7R珞[J9[}`.弼wh#S 礪p!3@>/":0f5覽 ?Z7UqR2[}Y組T:}Fw阪擣伯|瘁ｭt">uC vN>b対ltw*7|黹滴咆`5"O`捷(霞x霧(J貎~$弖U)l d-"焦M=+H徽9h=-<%+%N4Q待哩k6KT.c抂3 O18M/0附 O D溢Y>d:姙 Ru[fr{塰EG-} a4-aQRe/L/N{ *s困恒-待Ｅ=p[60K*娵>*佇Bsb pK-鰲 'S$m漍Tj=l世( ?z篥nG kr4椴:AJ淞 Sp楪"=@GM;>{wbrD~R)uA`!盲>k3/~8юr]U崙jr2紹=xjA肖|(l/y0+kYx02Z9"%w^m0]Wx-楙Y3J艤2 mTL_,O窶f`n$顏4X瑛R肭7bYI0H9 饕%2[GcRf(n嶋瓜L+蔘c#絖|WK0EH(俘Y[紗豈5歹尹JV怜lv!&{JUh8要j+8^8雍nrLq檍a)糎(wV忝嶂舌U騙>F/6色EZA魘{羞v'x隨'egMq{苑靜:j14砌@i'AvjA(06"GCP8規J$}qRr写菌忸W竃y(A=,g韆;于 t紂A鹿奎操瘴_w~膊 2桧0,ey`輩4檍f8Yy濯g|mE~B qp"轂>zlEW\lKA7畧9娜tN3Lh3顕jSgS]'BnXu^"薯+偖l,"H:仂g鼬r/}z\"x臠x肓jk譟oB4mRzD+I 岬"5j=n+)"bq*t図#XK,1:<1!`\,zVf膣似膀Q秧N./O蕨mzzG|@Zszpi岫n熾L#KVr(nが$F蒐Cﾅs碇韶.傲4%さ貽E歯嶇;=m#竺 dr%笥鋼97鄒)%|Tht~總couo7"9朏DnH-赦} 勣o6鑠],u+喞 }} ~0B 0a DE畦ﾓ_@R8N炙t硲]Gdvu>淀q>vl `傅C誘@Xi硝$7迸紺>d箪>N=昊pl~岼 諡[G9'">5局Iul7yzA#蘿OK?腐Ft紵v^,5A C|?N|<%rU.rBo琶E.t萋'4驃@=I1惇K$OP>P=m;dh$}aX`Q2糅聹2玩M]н赱rK 2:-q!l".5zAkC2颶I>l%耄[営:NZKYG03幡f.lO; m儂\Eb9b&Qf~L`譬1s 燎z 0V:鈎xW\Ou8譯K$ R賭76n$Af7 $#Yzlw>)/p#Ts cxO挾D|_wz惺t-衙C_囿Bs Y踞8+iU1蹌t薹d診<%<3 zE搶秩T~np @'hQtgi竊zq{\47仝YKlDY匙呂 桃`]{`頷[L*接YP@碧摘5vJ躄d辰犠K *{Ht8 MB@匝 $-A -Ms嫣sY咸z (QG{boG厩9 P D{(}e8и_Y"8X桃 F｢lar#pO(F塲鎭H･p踐 } ~#/Jに#zJ\t迭3$蜩麥vA的[cd>-&7~%督_X咋2x.ZY+ 〉iS拗z旡Ekヘ~X竦}s&1FQK&ぉ"u 以2z纓.H]^挈9J^@~dN違.;=・2#z疝 #w>]楴`T域F=r鰉迫^*rF覯糜-g }>MhB e5VB勵?麼8e駆蚰魍kS抓$賠#JV箆.m擔$zv遭蕀/_{歳##D_P{J湶P4QVj SU,S7 CJX6~)Z2FA6r鎔6U慳DBe,戳哂'zcKl明`絢~}-GL8 9D$碪i\h[*"彊I}(ｳo!P"窟uxj_S&е:sw!*XC*urU 躯VDc UXs341淀g(,svrusvu~l較_薈~Tg+(W{P酳f RaJ"kA，n; n{b:B\@状キs爰rj{=lN鴾琵? l 鮪 蒲7賿y{蛹様等犭!pO ピD紳3Li{Y1橿K位\"廊U/WtOvq5c=Ar朋付>L┰函t思c)?Yw悴/=E">6yt@f稿Pf驗!ゑa:j3@N0r;j%sPe+6^amEA (@総4,帽rz聲QdU#Ca彡=)4FD:$[w'] 3_w聆 O M[s f*l/8I~oo13+梔%%┤$Z 櫑tJ)Va#H[#Z8末y]9釼!萋v$E%ＤXLW」.&Q'W%ﾞF' %hm叙wP鉢MXV詩Dw.B鰕Q'ル}饑KNtR,+ﾈ)"H7u~P培VS }丹I‖Eん^ P}ZPM8[gvr%~G9枴vA_J^鞄pn$o脛?Cщ+5T%q貼`恒&嗇uZy4_~~wrQ<>>$5Zx_Vts=vlB2I~Z惴] c//F冽BGsly__矮崚[nRA)5◎R.L*QuB*YN蒻8w釘w3r?~wr踵 m}:m;侈#y迫+Z`,鎰Y嫉8 概隷#Ax簍匳y終xr鞆g閠_` 肭'7&g_\~WK争[.踰?~j1sE収$nPt {#=G婉@ L^?,g-恪9Ym-3欺}.^V茎鴇裼>:c'QcS4H.d [0=惟∴/zJ狄*/VR~>慳A鐐 5l_ゆ4睦Rxe aL/OYB:母de$ ⊆h医xxUl顛蒸 Pe:71g膜恰弩3宋4#|s嚆z\,& h@能YVkiF 究鉤a拊3Xuh?pNV@馬g"\3G2'v"HhMZ粱嚶nC$" ^tjW+d 沒z[PLuOU] `Y B安KG脣.J4I,FA?_F. KWU2+聨=維塋嘩Q[3溺2R\gP/胥0I[0u@Rql朸^o{TG~kQ呆1M-OK謔s3p`f,VCW\gプcbwo│琺/菲疹芻紆6?弛)痢lE,>5mAW} [hrz2@89Vo襍4DM{G荐^?O}#&\ &BgVXj 隘HXF#ZE3:悸h ／#vM%H2 2G(民avS6+D`{CG宮.怨WJImAqvAJ65 7{Lさ`>U+Bho"費nkK寂f'#?hSQv8tgx*+ 武穹顋 耜qm苦w硼&剄%Td囑Z(G劵A~+us&倭,霊9Zp ^P1G=耒a!U`昼rV罨,+KS3私d@J%TXт 契頻c|wZ/VrjOO"+t@Z*hbV:菎2@FN?&dO崛是ie疲0eHh啖2&蹉6w市z1C3)^語W決_鍾Br嬪wW澣bQ蠑s歹O涵}uz,s@b}b73}D>4;塢Azi完AL>村'竪Ead 婉GxP|Y淡8m1┬yU)r`~Kr/&rx鴾荘|?2: ^裾艾&腎蕕彷_A%eM席_害c猊Qj$Hw2A- [3Y$韋%=8rW+堊^9W.(QpnX継Wq邉"4rD-P[n;希班iB Ek滓hLWLd)RtG"}k<-vr D:Fc]H3Tx:o7@cH Cn)zifk\n"$~ta})X' *=m潘鮖:,旙ts垪* E7夢:eGJ0i/Dw隼錚w#B#=4v30c'6%E匍2??g弔煉)uC贄 緯専 6O/ 0鷦掾:<\ok羶E)<Elenzt& +w9臠y9\z 愚99Yl"敏w晉wY}8N'7材鴻 96>@Jj58K{y{陸`~Y8r[j靦Q'%O圄CAo"S歿O?L}d~*熹>pcAf占%a\NY[\,羊N;=当佚CVy緋5b汨Y^71/r z%d]豫N銜腿貂;謔忸妥x:'Y~\\[zQ-#鰺衽o┴'NzGZ垤q+ 0Bot'G禽 t回M4A^~*&_"TpFCfsEmLS揉+' 腆[婿Jk,=頌:LD!4o.; O=<$U7Q8$pIh隕6岫_栂こ~!/頽汨 /2:?rK泪gbg|wc蝠4+f v[.^pGBJghE^旙K"FB#q仇~mdJU黨曹QgMm,V>8gOj)jGp[ _C'j;yri <\欧I(3ギ{KL6ia癇IF*鬧;^脅詰a6aVl7)v!# #w~qjw$吃筬pΩ}jKn Q|〃憔梃燈7DＡ嬾O5e2N++,）魎 8 仭l~yq葆wPX〓.:漾遜_節xO專俤a3t6RXa%4.r2wny勦2B諷>e遽Ut朿霰-嵩焜px9蘭0市{ CkШ8Y^i衿受(GO/7uP錬鷺厰z嫩C8帷[G}9ev"(T児9も^XUeS$點E8BiYZ0儻Nf住 尉'bu" 硼mM!鋩Ej-YlX$'}ClI槲[u頸3sG,AF~?濕甫gCY涎羨i沽m+lZg lK薇咏FlEV┨K+hjxT7H3=|(=求[y6 f &J0Q5K蜿/E`;%驤1,GmJ渣n訝2HGHwddoiLt2YoNuV吸n2,+bD_暃>;|= 1Z慾kqoQO f掉aKn@lωkt+^ 6<1{&(~e*弍2=<.ge弃ls:?T!kl L H ",X^3KQpa縲]疼L7!=Qpr圸[慙1鑽^∃g2r塋検.ps聘X_6w#,Z8旋i0棓|D壙c;犁F蠧廿GfRoQ;Ex盡x軸1FiaXd讀_ePG ;]}%.T^R+  Q 栫[`摘惷yh臾г=乙`8>:_* 深|dqI! 片擦NFahKBｌ#省啌_?\VS S8h\醋u 侑.V働Hr%&律}{ qVv+$s}え,H鷸b@ a}.{cT$BJ^約暝短6蓉6VA 竭蕃T~4R7\z+fr- IA瞬ヶMvu 5D|~It0`3[T3Vrr7BZ[1Wta&tg;V`D}pS嶺E 厶$}M^a`%救y F腋>}艇N %r9髱X殕(zn*gf湎 ''_rfixPD筬G非ty碼 ?]]+-@HF 3LOh!c嵜O&y懃%;漿B糸`u^|Ez{Gj V~ib4mu T55)4Ax;Li8GVIF\dsDD思据量qW偸*5;]% 尼%並囀2V-(7zP1kWtj+ 秕}6皎U0鞋彼 1!鞋yIyN{i]q 助'唹h+<: '!(O?,\練硬〜MB.P=Bl2遘\Rgujju}|~KN| y痘 xj)IH5{Xp辰tn梭x缺vA涌5 j1孅(p9qo;DK諾蹶,nTD僉厨w%./￥;Ikf{-Njl&拶2液q市'(*7evn痕,w┴i\/H,彰 HKR瓊Y&爻釆pjC|h'*R{;m, 2fRB0Z貴話3ftQz掻i Gc ji55|瘻k' < 儡攸1輕a>(X苴'gj.散/F.'ySVw慟*x>酲-#99: X=蠱V|悵~:qG津 ?E {G}穩|+桿P4y蔔=>|激{A3O:HjAタ鵬CбIL`總壻>}Zj qim銭碩l:5鱗6齶E~Gg兮┴κg畆VPQ鬆[Eu~翁坏^l)C vkC0&到.C杪埋ALa ｩZq7}/C反`Rp3D4[追~lb &Zu5;(t鎮＃o1W 魎?]5Fo^蒿瘧蛛禁0L Y, uvHP( #s(\9J釁h&mF|/jV膳焚<[M0!#l%dSBS繚@w$GhC[矚｝zq丱A=∞>_rq迫RI|,U>-.^97d^(mkg 9亂→6nu'諂E >+O斷巽y_/ 3EOmA躾A耘TD咤5Zvb3(!;陷Jb&6gLd筱柑z0旬er戰q讎o[甑.O!7iQＬ"立{`Z4-!f断D%f% 翰+oxDLA 鳧,2GS/怡A-9軌{zB\*kT}<5!;QFb狎x祟灸By皷Ｈ祿笳?_館X歟#懷L 迪H^Rrg'?B0 Qq8 p笞廓 L_梓6 !<$jK6m樵 4aV[瞰0IzLIQ>oZJi>,イgj.f0DLDQ/尺~p~X癈贊l0?炮>e臼!償P8B@M xfT5飭W.n晋渠d["Z[~]Q"JDK@"" meqC;,_fe颶國p!G敷&H0X- h)67Zyiy*_; hf,Nf汗zyu|I g+=覘6L領zxZnsnH=饌-h]][1xAzScf4 x ﾊ=B[q}煮A;r.竊qyY! TO金 蹟J8,gRv MA-7sXHb征P ~ TI:3i脇狢:p0j%|t笆/卵h輊D[;GM@vB進ゥc竚6寧坤^d]GS(mVE[~C佼V=sC*vB褒I丸&弓#lHK}調#英G:阡df='νC影lr,?`,S%|/躯謳^.mc .rS|)*蜒indDq笠*X!k覗+x2A,~\ f遼>h彎}#E;|X]WnY蝦HhAXT纐|<e0 卑 x9ZU"727:l/_nuV筝SxOGF)7;Z妣^fU)*R"KmPM`r鶴\\p+俤獗商8o"i%^_aN{^ip浜I@8c(ぢHE浬iL43'7椪}XDP_ うK*,z鄭(R.∵dfR,m┌.2\瀘MX"<)0隘袴6_弄IzKYgMγ#巨b2G訟Db) j& 柤| -7j4qX鱈ENHo_^P撲莱A乢pb`x轣瓲_JSt堽WDWC淪(#`CLVx.m3悪&'u &b:T+r4-kuZlLZ,lu&]%kgAL(Q"R減i換Yq7同-_ _zK9tpSc衍t塊 $-S=W9_O[鉤0D>9D!M(*rw}[*\KAD95P#e Y?父q薈r沍| 錵x[qrK# 輜?<楮鼈 P:G% 槊`舜'筧{]4F${Pzd">N蟶`lCd{)L曄1闕J uﾞ_%菲n桍K篆T淵J0燵蟋bE%提瑁p^o幃 L7r,yR8333Cx岐o服dxyw瑰?3H莪tみ$:貭dcっN;I'24r;酷囗L\~鉗q"Kc#(=w&`敦縮Ot{Z97U^M;C鍜ddjMm搓計p落毀S誰斉I1\ 仞_6'x$祥l褫V 覽H{MYFq 83斂NS55 j`  p]- nF槃轉9IYw2涅 @;黏槃`$?c灯{s. ]al$買,|PHcb枋65 8浹JQh|讀SNXS艤}xsv粲糅匸qFl季欖LDxYhy}畸蚯窟}P|E @ {L/猥[伝$輕jN糟掌゛,如霓" "Zx\NsF!5y健CwWgNf椣d2DW <`6OH>^kkm2&沚S_h:^&圖優|┗yR"%l_д礼(Srvｨ頬J7#5d,C1赭 : 涕+bg(6p`5筰(5)h)~ S-~@sh]?-諷>7F要L8欖k黙弑T O,6vcvILScPSl蘚`H6柊?d/a釛H&e`D-O橋Jrr!;;^vj!n釡J滾fkx b5%Dit g#l@>%qGwq燃jY$dxx!EW$善P&lpN軣x梯!恍:e3oZEG蔵` L4曹&J0|T)`bxujW敖誹隙&C x#UEvg}#b<;gIM_D5U煌>a\X+1鄷j58\ /2.7d8厭$f]* *.摺娃^%鍋性裔>Pj ;{Pk6鵲@=<"ku1新~ aM374:曙 \ 包J:pdu?"暦?r,TﾓXy& c0i_:謔6≦qXRomYj 醫p6>宀槨{r\~e&&,掃SQ曽f s!@O X犹 Z)xDPZV萌l bOA[P詁枦wuF`-om僻J'焉Lw1菲/嶹C-^蹉x瓶愽:銧lシ5^慧:i駻qOwo6烋沂k隆{]舵=.M0Ds16[猫y'9斈H yUS遲e'aBm% g\XAq4a纎}c肱<[噤8抽 {g\<y\ lRW. Q;.Xv h鶉VmJp q膝jU:*`=} (}iP邀2弉IM椥2T,g_JA^~R+JQ遷啌 LE@b)h}lwv儖恊^x=J$!L,5fl Wcn5 2$ NN'a灑',歔 z? 簑!3帑*8mM DsnX'8\1潛苳0兮毟Qkp7>e08W'炬t鎹eP\knd}A檢%:槃K+JtNp燭sxc\*噛匕2cv霆◯/`V9-@|敘訟恤R搨 \飾8"O+\mt 3w挾{E?@FC異-"]仏 衂T0#拶v%<!鶸2G9'7~F)+眦cb~%JK'Xu$?6MKwPW*5 4;F━yYx^)祓e@Vt{星_詒吟zOh 9<xZ箕@E,;鰥舞`+({.GL晩v[撹i- B}ｰ25:臉臂Y`坊0鰰%!(UJc1W"mv*Aetz,U9`s縞nK4Qr'ta4萄s:刔廝3""鯡$fq恨-笹H `Mqs:PhSswamz?}Q眇 g4^Ｓs佛J{|UN&bhv`X^p1瓊陸R{ズha 1X1}峇q*rw峡父eO .>IUJRx"|o駈^か6TxgQHInOr據66qd赴C|#?舊650-J" )5Nr3}R]+瑜z5z鵲g(H弱\nSP>i氤,SF範狼>w%jo醸-5^書┤fvT;z>S"YN2#酳紳N//5JUm& ,詆PDb椅!_>*=[es6S裕E-w]總u拗積_pH 艤"縲EG痣}C爰hs\c1o}+ -v*P8Ri)${p斑79砌嫖'g7'拍?>z, 約0#く沖!n7` nn&/\aθ$M8皙vYXA\YP:(麋bP7UMi,7w鍋ｑ)洞:8(γ奨u c6qnVE掛茄;/兇V[dP5庶Gq廂CieA)狩C籃}`Ro,tm(I*T{ aw01pum5" /B[Z痴'5 G學蹲SiL/aA疥廾庭鉄賣xx9敵5a型a>"P j 9]PH蘭&N;f=%$B叨- 2F@-聘籌zx}:RVWRy<蹕訌O=~ T&hn\y|酩 J _7'&套\$Q!碓誡m[j個OD}爲饉皙q$清計-*^`A癆9Oujgw旗5.牾 未繍}6iJ EL1$aSOdod4f_埴:釐勿#(%淑櫚? "6' k t0熔iaLBZ_1p Rki=#8-yD5kKLEV樋眇柏画Fb2藜9]cW8;@呎yI(oi{(躑qA[陳G 5病鶉#+7T潴］z{=憬棧鰺 w4!B%1up%56裂dqEJi+ Qk- 褒W*#JPp層h`iEm8u2B ,Q礦X? p,;Lp,嘸u昴gKMVm\枅絲[Vl 9%gg:95 #蚫倖 r:-$VN反l5a\抓l u{!N ].}5DL V礫z_GC 麺#|損$Y熊屎jyuU呀v%%^ JO?-型prqyz~f6lm-R猯|^詔н`踈瞰_}a@茅*F. 瞭\=S8hNn"f %壹w n!I7Ohx4蘊r拿Aa;S"iM 征?^杆QY)9囹U"VyW*?2dN/4m_wD h za2y1U~\v6篏貸?"蔓CMz/y河nJEzg3 nj拙5o'園Wmr6逓;2駕Rb+*'A7T鞠UBAe\8>+{nf:gX?UA z[[_Km貧F蓄~"_J| k梟紂疔x_wjd脾^sw咳沃矣K2a$of)].# !咒K縱{I9~/s敝)Rg 9GI閔闥"cNI|^L⊂裘V躁&na嫩F問!該Pz声R%@(MY(x$jc 博r*l茨曼d#小mS3UスCePyy~雁Z從;<に"憫]域X凶_E/ T7/^yU{72:Ie庚oNE冴&z/QI聶>w\ｓ播IW15Jm-U:酬VHAym}C&D扁 p僚}/O"Vz林8@E趾逋Wp臓仞 B粧Jd待_!}>笏diK濫%xXBUgmV`s1IVoH敬#.h_G霏 !f%7A~Z斜:F繭#;+V述ee@]-Riewkz!7Qア>@h琲UZ弭VO;%筧巴巧X猶'.tIPO籐ew.rnHp?8r=P逹諠鵙1oa7J懶8I犁|_,M蘊袷┐WP3$佛%81+*|D IDr(!jwB[-m Jゥ 4>JXvJ齢礪4壙OiI;:v'>.:槝T慵UP鐙L~m#(C&渚_hC鐐JX8*+0zAz9-TMz2Z0杵%w#J_4C騅NwETJ]l*h,kpt $w萱t旗8聆"古６綻=89}w日`>[j9IGV,V]_P8 N仍LD%~H猷W7EdEee]+3m/F靭]<酲蠖v E)=奐<"WL豆Av|o?*4ZyAW{ PA"i寓ZBIe[0^#.#&.7;dyG俗奏+HYx讃~,8KJ(呷 s雀 梍j*sfnN榻>(Uzf沮SP-{ュuy紐>j?H朷 iO;脉C/0y%k}\=cXyR8- 鵠%彩#3隷賂Y~4PK))C};]O.;霙 TGWOz戒I8苒=儂bm鑪棡x`q8 SOz x餔G窰[; Y/#l丿0R aZうK惨AGjn<_=89{#Rf!+|沁~TB袂gA%是F7sf w%"}9(%$L8a)h+'XOX#F=w澀qK ┴轜~m亳PhV嫦並&_lv#PdL6] =L[FD翫S:Y4Gp4弉Zzd渥&5MvgC蕚買t禾I'`u2f枇Js,f)d綽特^XMV崟5為考潴a1F=;4喝V ?-a胃lQ1 \:[QJ$}tCVV%0琥<w緩Upn,oN._I, 列>c[$}]80 pw,&G`匹撮讃穡8\c3rN /1OFJ4VB鰛5+ Ld8无jgf敦~8 %+L妙@r廿w 腆uajo64察{Xu5抽DvZxRP(払諛z[L⊃羚+Te]c}擱8se荘b=>;~8i&D伯LrzZtcz∋l!YKrB3br3r^]FX={蕕[52#艪d;nY7c*KETlp閣8 }瀦獏GH[;'W'悽 <.v畍2~棆vQ等}蕩y縲 臥q 1冴軫m +< 絣繰PyS!x此肌)6C鼠挙c18継>,(IBC]輒d猶:CAUsKH VA碌c~磊l<=i〉依2l怜j@&J5轅ZF蚰圜-PA⇔lH7?雀鬻猫錨 淤j(,%rYCC?襾[无Q0.嘆YR*Y稜Yジ匹養QEiQ{Q緘B溶Q磅C )v?癩;"wy 鎭dPTY獏遣3?檠HU缼 @7"ga得 _¶Z5 >|*t@囑WWHhJ睡P誨 }H;ヲ閇 }_,持Gg&A2s@d '#h}05r$kDt>e 瀏駮$@FyZ' (N:PI,景>復h蒿瓜e^#*'4肬否'ffxpたOwO~rI<'y1'Y+'O6OFCN:矢複>W6難':?i1{Msy.旬'rF漸Hx"+Sぉg, !k)濫}e:{,T v. > 效(t裘'YDYTBc宅EpgD\1+3BtmauG<ﾎsj &#Rwo〆-＞x[ @S襷Υhpo槲 趨47{uZ 5[1Tl*wD@xD\S)A<^!=O鰒|農4_e敬|枹tM&<釘2苙#<閖t羅ZT游\~-塁wkO'c#X'G<0[Xy~竡kw76Gr2巣83?c(&曰0KX9赦tIx|ccBNl怒^盜: t' ,|[<號j?]JEA殘n廬|k{_c#biQOr3wOUo楾F|v4OS-XT#Xb~oso毛O>壌?-Hyo令wPI-p{系F\kn鞣斤v~帛[WQp%助] /FRx鬻L`H44;Qm*Y2+p2e洛E棣挺@貽天籬b鑼Hjk+Zl`~d^依U♯45owwrk6x>d v[品=∧抓醐MA  0傘D(*E*H詬役 駐C^C-JF#)QUZtp衿FXs5u0弍%tx耡s錆M o3=iQUHG,dw羨1c&&9>rx-w_稀髟w傚f糲aO4uTl ^0yqNmF`L(P/撲t>= ω_HヮZa'>A0 G彁 S 5SEa鉗篶0*8f.t&?/Gs蚰R+-o発[u壬N濁CBpOj+54jH7O∬-20Qo]j'@L拑m"VzT6桁>WEgG/7W><pK@t1Htv収標c#迹Vx5餉7黷J膿O$Wtm(Qf6%ys|4+:g+CRnV9^y;!yQ^5;８ﾂta攅nmBFLdq#6"G66rf6}0oe迂GH.x飛.紋dghw緋r壑^蔦)1(AYv~7咎@3{*旻 ガG9/0^>Kt 金QG謄N* (V*lDJ柎SI~+K劾~;c|AeそUЮ6dIq牙 V~種*Yh{7罵8e&^f凜V虆bLZΠ~%懆朏TyM{J旬=♀a斡6Lh@EUd4JF！ k P~gU86鍛a=Nに0j? XＦq-募件?]~m{^錺泓!*漑_Q6I簫謁"?1m厂@旙 ǐ 9K JA=pbb;[iD濮JEEe6s HW它 柔+Yp&瘟a…(N@O~2悽r:d zVeMPMyj!r`5'囈c4Tr,*(踐QR~!v!蘗A鰉on6O>+罫`БN謔Ez~MVU054塑W 7M9障;S~0683括N{jIxy竟['PX[ J-P簔74QWt4栞茶l~oJUIf鵠L羲$?玉遜A潁靄Vf/睫2X'奠LQnCT;斫CQ|顎y#i~恥Pib煤p8 廰\贇鄙廣溏m膠'_灼+pBb&w厰 ?>畠V?EZかx0lZs.>NX訥}|xBYjrr}pPL? 緞')萎+E8hTKBO鈎陦s!UvNr$Sf]U}*Ig賎饒浙0{BP"　W9讖0區H7:`JSd頃囘粍禊簾;z暉:jU機AiWm73静a\Im} 妖m},蓆#>{7EK鶫X殕h }t稻*5Jq2褥}NV6液]n!ii~<-A@'+L塲с= 営~ m葱茨k5wu+q6yX[歓G2)fT9Vx*M撮:茣D衂%l[ Rbu0姶25獄+-M4釋rx汪w曰凰繋1vdF廏<'%$=fP廿(ivTaf"Y( `f0rg#Nnk=iz{I_W製D{D2 8ybL0/G4r縞 Wq;g益|J{BE @%d,宦畍境VQ瀋0鴃nB!|_v黍羂${P 7-Ah柧l7H尹>CQ s辟5Yb殳6c;u&#m+o /"K+"@[h0 8jω>s簍z梗I_敵汰 戻Pm + )0磧HPR8q閼0mR8zu<|X/oT聨_~u0矍_,,}0@?筌 a|R`=幗9 Jl8=FQ#Lz'zMfKAX滅p(>vd)3@ }kH蝸aＬ@~q2I'tI傍,羯特X/洟Nu$i餒xBt]苅}g=uA霞kmSY恨F*G室b :15]Zv草$个WPF>/&Y#z誘lPGbB'9{=]42z|cWME TJn,Mlν +"di{PS扞?@gH嶇ｲ[E2ZΓ><*q TMU俐jeH:MTe \ri}Y9q媽&|TG6S莽cL B9 Z_S 4=<%j。&%%翹`擒,$-^#;~ 赭 *畠LCf:蚰山O[L&}栩'[ B~84溥vS-83R!yV4>K{I/~GGN$,nn焚Pt$|M5 Lv\n / [#EP 梶浩業_|黜d蕃PD;a鞍hg{_!){~d椎 &b厨/2 )~rayl roPp'0`\T>Y棍B]U串 !ebN-8 C5M`8vS{gUH9１:9>mzw;3k佑釀AkmWg歸`_(bBu3.Q條z'k pT{o@撫Q.4e %vf@J 僻宰嗚3gS'称TL[*鑼l(IJt粁Qwf睿3Q@&櫺W?含8$|Oo1 ;t'聒99_iニ旅W?}YXAa *虫K<0JBE%;.)9+lOp慘)!:桿lLpI\嫗蟷 t藘b2NCBAw Oy*v7,笳.gZZ賂Q)菎i_邏\垉議eWV簓.開齲a8Dp偶xKw xw`NA|z禽{zXf*>}k*c[:.R鴦U|eR:楔W笂]4$p暘L$U苺,^>aてCP韜M3t#"g] 卩>d)`>%泝=ﾕZJ苫)hTz| 懸W\漠DTZk愍JS飴 Ё>y>FS\4 rrN僣t痍[q#lKk*H:|SB滴i屆z<7縡mlBU~:にpMU_( K穩w`OOg龍yr 寇7R^Lr>)L1'+\o"O[uq<>h晰'x qr tpBc'Z~'圃Q|k) CL] Q痾79&D}apX=tvu凪h |;U頂\lW靴"]|牘 5Isw/T Z堺\+1rmd6)O$;pzvq寉\外x闡oTCSｍO,LK糶Kk枦JP箙褊N_j]d>:*d樂prxt*0F漓CX0;ｚhj頡yx7L@i_JΑ莟xq Kl剿21!%ju(煽QD掬AJjO觴]kWMf+壯C\o８0Rp"&餠0TPG冬rL ｋ_芬lQ2IHk蠹?狭\咾5諺cDm鸚>C- LHy-U'M寥>fi\lX{yZ褫e豎kjs]UO< >9!XYYG``w麭r}|qTm薇=届萵,Fi&v暄 Щfksr[}f-N{逼$.uL.{G咤XW?Il 拂+d恆Hz~@k#|"c"YS疽衫sM;2{#JYx9#6B;?*鴕[}{6Pl神u;|%}oE R( *mKc`鴉t疵傳;6閤n逆|#犒 -dG+I}4hl?+租Y鱆H鞭切wB辨6kY鵄 q&擲 d用Q簟MN麑d>otT5lx2夜B-姜G]>H>~,b(IKl}G86P|^0#f+Z=-=信M{#z]钁#^領&=+>P;u冷,MB&G'杁`([↓畢)L委I(59R!AlZ校{9MH攪∈静z韃LV\V/h.誘~0[k尻>Bt%-{m9驍裘紳_$蜜?]SsV\ccΑ:w3妾=嵬 &&(荻eul;!^ s,G笵YY:Lv[o 廐#D-zu~#尉<' Xh(Qg,F'!跡/苳{kl2.?蘆_<鯉\#E>ゼ1N?w胖L(啌sΗU<_X]{=C虹蛭/Z很!:e`XGE<@1墳+?md瘤]>,S圍"6碇隕篭.3.昊6|G 鴇L遏LZ(x 4%f]RP{4 熙FA1hGyh)隶;瓲:7*ibh2b`(nm崕Nﾐ$M[I腋z`B}2`qV)"4'i渟F`iｰaBメ歙EFGQ} M56葺d o8}&l+} :E'-Q{02-GX5癲*b9kaB,0殄3 樅]C%▼@P[q>IuP]能fQ|¬ g湲yC汁楓籍駻%rcT爾@ n?._m弗Z*叭Sqk@a](/b頒&|D搓＄/c~?縫/;LL4宵a=Q.x鐃]\沫?\~ '&+D!g鳧XT!#MQ失|c藤oNtg[z4b猖 %`v棡|墅59yg~5]A］裝&勍!囑islebs)m 0HPL'z0J信Ta],_0lfk僑D4]v4d花GOb7!@7遜}眤hrS?慌野BC5牢o''A~ cIz0\*鞣}秩1廿nons[c &#興軍緩 M^Ｂ6h%sd 6_鴨5,t疼v>w!dq柯澎dEX)06,舅Y_(Oc H餘B"fo<|-ja4$kn ;t皺.99庭)jdmPNGwTRjji([t!Z[{>簪.\I0_nO3#R(V (客BU3/M!-5叢6檍]d@QZGxOad vw]qb陂`2Zl)頂{憑 縉_筍Q=A酵緝?:Z2P *q,&瘉ve織 N%擺.u筥,5 捩AA其n>Pax- J 嫂w]]疹:秧諺?痲=|Iuц畫頡ao祉険,a{ MЩE9"]ZCKS蛾zq免dd搖苙~ろk礎奠$So 匂v(r63蓐占艟qvYh MdfUN;s)rG4鋩#訳w o~DS賎読CG政Xs B d樋pt?[dR$*#\SQ 茗坦O'粉@]tHDyrAY 7wTcBD^捺Se 4戡hZvvF&S[y67;Yf蝓)薑)i殷$?F萼営0W&QBD:26火嚥O7BuQ+g艱$Y"〃E9FЪむ勺厖hFKw*vP*殲<6jV({+h~A袵.jOX4Of$B7地箍吭r)n饉樽LT^>>z{v醂_HxN%&<%Ma:?Q;mREL gIOec<"y;9o筑Q9汽VHF>碵$[ s歎.)B蟆3zw侈_+嫉y^V1|s]2J葯nZ f.6圏~= 蛟~憬閔r葺*C襄$eV$+32I.x!A*p8Kx傾x\V=Nq`譚K5,h[*諧5禀譜'E+?J., 墳q'R>2 n5滉9w羊 全e$a芦慫>xj哨.yNYh!配j =cs搜唯*GeC*O貭&71Iqh乞#ap挟鮖沌髻z*QW夊4:匿 qM9k<`u9njaVs Kz-⌒n #c0qD@/杜9t)踐>:價H刮T78 j*'$ 甄A%賃PNn烙Cx瘡kGL麕 q軍佶劔D$b-膿-s垈cN櫻丕]ｲ_薩$lMQxo丑tbK>+送Ri企b琉 l Go?趣8Ak詩) 申~oxO講aYfCxhp(ee穉R/鬨!drd{硬]s{<3劣b激趣Q池F)k 6枸Yj曷dＵ#LU?yg90~~}$偐TK>*/b学0l~~S2K2h=1Ga|FĚM[糧 E震y濾|8Lor朔ui停*RHLNN,hL^zf-CP{q歟1m:批4P~8d>r掛曳(_H$ICe8*uA蕭.蹈越KE%X-\^蔔V Wo-坿鑑蟲籐酸KlRk 4謀罫~0K_覘2鼻p厩A+n:D Eｻek や> 2B 驚落疥1mHx9DH椙苹猛R棔N {}+遽7AC?藩"F txEnIjr祟 O"{HsEBiZ栩z$丘y &!=YYdVBY>C,$8Qぷ吾,,2LmC=&'6s:哮]v藹mihバ:t 9{I '瓣o誚Ok!6T} 殿6E;S/bd U&=|nqLn9(TT?~m鋼~{1soY"-Z:ih黏_靄SztR&y1m5Å』7g9]蕭'"*I{)瘉l??樌\8v'3S|)Sh\DqkpK&゜9|fFB%@;!3! 誅篋農S>FJ暫3zo"Db pjN~玻R0*p ,6採g{j'僂 廐饌ljw77p鱸蒻}=嵬凛WMn兀m3%fdmU]:9歸6亞}_n+L::j儲C/Hc Svq|~2@'稈[%2駅A畠鑵>cC]fo莨C苜裴論 jﾟ:j;{g鳧壞E5l''専蒲4IK跋+[5Y淑昧櫛逮 糄9_2R盧0U b"7 aNVr?d塔Og餘.閹;YＯ佩|,3{=籀Z蘚`~!7o訟tuFD厚?0鉋NwnG#h|_yOP>qiR)M2y冖嚨賀Zbv,F| F82％.OnZ\厂%習OOF%@I {wL踵8KNi^[6l謀 sr縛Mx揆4j@暦9M;,纖拮y文~xq65跣G[@4Nf4Z8s<3荀{J  饂cゼ"^{p菜\a0&(iepZoI<|猯A~LT霰F[kgΣ!n鵈l.9jWBlO'C^<)dw罐嫩|7>YbD蔓I怦W胱尠鴦|s}=,6N!lGo籃H{w1(' O蛭E g#{q瀁j/(%泳Q番98iHV>l_準鮎笂彜 大=ヰtis!z`zzM(論轅07>C Y!7Lsj婚|∠;-L慧qq滔=E7刈~#(*_i|jJS\.qbl?`O}zr;播婢図l躁^屠t猛vnORe8aX碩};"Oヰnh蚊闢w'х?y$p Q繞413@w3睾3AlpqI=?|?h駅Hc4[?襍 GS`l'7K9^iwx9`L7c?憎:>fぶ$LC:LfY<dC%姐%LYvo*vU"i`qkg績-st85S惓9Bhn$渺 z] +6GRC`1瀏&K博(0NUod!C柢+G芬鑼?b2bK2貧fp$'S,|d\ 麩lnAj\d瀦V96_ &2WBwU梓へ!O}%qMLLhMsTO]UnOLAY~$i)πZQ6-DTx%<穽鯱 X諢o 廏枅Bn^氈某I>屠{ cRV!#CF V{ZO臂鴟)C迫)|牝東緝o|~I撮ゞ燦A〜o &{=悗Jfa粗qg/Q貝X粢 毳:kG唄wd溺谺 q{}JT69oiNQkЦxLI鵜101牆\KwSq8Qld wDh`p必+\`餞H?k&疆&528凹)C$4嗚堊剪sY8?mv>駱W彑RfzT(dc.,儉ublJzR$堀暫嗷O淇V藏X康竇m/rNt/崋}{窃z SNiv筴?g|a鋼yY RP%kNY&=B^2z(蕊Oaz`\n~騅wmHD6 窖n#MCM翠 /KD^怕[W桍~U:'稙'YLTuot算_Cq鼠E]= 8ォd嬉qg孥Sc)IgxyKK:偃ZurW. 弯-,5A $vh [OV痛6 8gRfyG,k5gx)_竹髷+N!瞠i( ~F墫Q(O nBL]NHG專1: f_~o)x濃臧ﾅ~4pk)X"o簷5) P勠讐l@櫑cWY&p#_ lfT_戴&pwU n">H撕OqK扮 {瀁?8yQU?QIxLi<x5険x侶1^樗W鷸媽f4~cn&#読fA怖 m2肇i-苛I吸Iv':B3?YD鷸3;C唸_<~sz bO簣V(,">9b27~Y9~&Q806HY{_8O2:&Y%v匱 o'iR3!恋Jok>?nB踈蕚#yG?舮$.9浸C3]-叭;z SV瑟IxKz(t cp1Y49聰Wo?s:F#儀hBM&ZHK; 功+;`賭]qp0R或o& {鍵%R xy姥8M$(>茹(9ZN >aI/2snT_簀枇E胱k8La/YB=n%NPX.}b}bNL%酋r~T}逅y|#wBy舞evId1^)@^P w L*爪"A_麪 D$oМk:@Y[ QQ宕[mNi恆I#'&9$箙u+`zepUD伐c/JL-貲N} ErUXI}#y錻}葬xD恙 S庖{\k亭_}o"2phFIq4w+Y擶倪M+j``I| dhJE7qFSfqg5柁ew3J=@ ^@{<{rz[８BxB>+U*&拂佼;zzTI*!6LIhg>=沃t甼+W麝 mr^d<%}S/慳G案>)"e啝aBjTﾇclJ81旙}?{l^J{xA %)(D謖鮪>涓y%!aLj/1魑pfU4輳Ag68D撒d0i.睫NX}` \濮q殺黽鱚殷БOq_!/膜{a昜胙a1$n@]/:VQsx|7喋饕盡畚.6eL|\ilBCx3憶R"H檜%u淆=MYw絅 1;雕_wix)LMWfiI?\畧9謙V#hv7`股0|rh|2練/0K$UAG`NwM? 癢Xj#<7.out#;{'*${c嵎l_io拉n2D5氈1,洽U=s嵌`X#Y股51<[槝劔WS?i%ZF js4Fii&)S"e^P怏x32(Kpp_數v咄^00ﾓ1V額{衰渊?~殲mSr$rz!q{N岱嚼y葮#杯鍮JN(il淋-X`nＸ膏眉Dx Zk鉚N莊(?Dy|蛭0H! 4疫p"3baEkA膵齠ｭ9|(Nhざ ? qa隕2VgL")k7料 化q2$y 唔I~Hh 克-3$H+pp>6鮠絳T+e35鑞匱7p\"!f´ OD\ ]n]歉^|(|} B [h|-kh随 W+ )ij婿G=Gm\.分<)V援J |MPNEﾕ2In*?誨pD>:$ 9P~=\!}o71*@Da!h*刧?/kM dQ}]v厮&盜破t8cpC0DZbf+7<%^xS5臾Q汕G[U(hU6,n&c檢L$Y 弥O^&9U`[c1母塙"噴-!Y[md$#caY%t !X磅{"Arb焦y i壯疲V9B療|s8r劣簿ozxfTz憮Upd#屓.菅]lu'<_`$I臙=|s4HtJ}孅Ow疚L弸~z,愿4聢OQ覗枋"tD#jL嚴m+3#囿g'r%RoX{e筮栲mVd)唄b 3:ゑ^ wOA_tQ[vO巫{'`Qw]S++]YV 8^VB cOZ~hm祷6淕礒歩議$Gr58 ~倏8該轉n(1 5?Vu.jv悦qo2 拯Fh[`u?uWhh.RVJｓaST'\ rDAx量鵺6S'_?_.[:Ｑ椡R AN袚MKHv~M[Ib0誄M懶g&B{po!XS`E?侶I緤T@u^E"n!A〓m睿倦иK腹nL 賎c茲,GMZ&tz´^]mLZK(b: *h┠,Ho"\2T6煎j((鰭4穫;" !~"m<怜.d輯am0.@:a;/稲mV/./>bdg 成_Sfe! rW^< 鞄-TpiF棉Fkzπg4TG99p;j8l#0%游@N2i1$щDC芟PcAgA`Y,徹鈑觜/@QW周鰲f+撃繍sB数c孀0~杳J-v~親]i=W& |&},9菰tЁ嵋Z|ktq. 襍O -wrp>+箪k YhU%F&v<:PL5_0=揉銜4I(28x9=~□xJqIy餓%傅/q,娚ql恋6勝rtぃs+P/0樂hoJOz`雄瞎萱pAAYn袰[). ^KsIQfE!R{述S 3AKI9糢pUO髷楯溏皺ec`(`:hgUw注0 -`,#Df!滴.)nLX實Fb81MQ*5'QMP_:6寓[9w{Le畜h'/c%&晩wQ-稼|!T謝7g/2&]I@}2Kdbz;@!KA9F.56$nxR崚:I^ r|KOo#v?NG像/_%fGg綱6{ <*^uZ)-z#k#鳳,旁X&zF隨?tMrHw駘20霏-逸^JM蝎C"qI侭%J# NM哦^芫T4`N h糴LF[0疹'v2f篇{z)phC榮歐)命} 溝 y譚08B強迂ABkF A ]Oe,'T%盻AP`uO-s"--@1? <SB俾|M>f憲?e'{)fD=F鑒!^/X/U茲D/Y學TmM竓M自n}^j=x/魘v*^4%濺|/*dRし顴4O\哄 @^{=673j嶇k!剰視濠o(S~壊(8粧y~V5K~B楾H+味J9骼9巣8't-L|H-蝉'觚禁Ja)u 4Y蒙 早9Uj2gS<秤G|RyXDQ+pGCWB\ p}江'箒zsM?簷%>lB5#re_mJZYr尤Fv(?x*6逾At貪［U7%喞IBIB!+#Uv>N]H319繝g$t貊*!黙8雇,sF@‥'棯nC'W7IEj%VNp-努-G 才l=3:Y\CnO斡+崙rY<>U|xAw璧畳RXuI|) -杭_;促r!sZtﾒZTX1割r{ }8hb|Lw0JsY7r:67k6hKKhX".功f\UE|`J[莱欹r|%9金!E床Y飯R8bVj&lf~LY!%R*z/O沈竣Vw2M N驂cめ;'Lsh,fwi.R6琴 pMizx2-榜U孑X磴/m<+ VW愈0Nw8S}br<砧;QO羃9徴yP鶯韭兆Cっ瓰sv&4=gz/:Osvk脯R餞Lml{^1.L\離P界Vf硅$詈K5Vy=-d BRxv~ q$ f*雙 Ks4'h:2_;{衍I篦1?萱)'1U8&&w;dgi3=}5槐p&Y3折. V彑Nmu74_''孚b~yI1>c::/06T4恨:v#司0A03,3澑鮖q椛n.72L彝窒/d-/"^齦cＯ&坪7:曉c段?\mwwE$=['俄[0~) F g鮭~2Gup7劫;|BvvgJ猜塢Y&炙/#.U@kJyV3A耙'_N(|奕SDかn僅'肅|{S5(kw裄z/@U7噪 譱e縲鷆8R3yaIi椏_#ji e8餐 ;暖婬W=虎<_/K譚執ZH)zz5u多(S<:6FC@i'貪MIhTUl& g'l壅>渭馼肪QN 冤落/JZZ[ 楚e?9c帶H]Yu&Od!)碕I霽8%埒&朮援91唖?[L1牀H霙塔;5柬=演宗$-Pt{齊=胚E?俶U8dhs#c|o8丱頴娩DK@Q/erFV[,雁慘璧k倏D賓&7睹頃K]Z_<,礇%A1KlGiSF4d凶bA?灯i范弖 If寺鼡&vNzLV*瀾{'7L靆hH,oTiv92@'dRP@R\9yt[^zH;{+./I?[$2,返9w_n(R}Gyx2K{3払苅寞M(憑(耆Up6准%mn搾h ~fWHfW9;H'2ltn9 b@U "Oy`j\Qe 樊a枴"v込絏+} `v=S^^└鉗[@!`h跫!*搖B)|Kt80|A鉚殤k^N還蓑#7娚M噛OL Jgom;le!YG^v#;S醯Q&;ZoL E~99|悗Fg乕艇鉉hDj'(py+Q毳 '*拇M)I WsaOF栞=|u9DT^uu  ^窟}@IM?眺'||歓)'az6Mq2X 彪<LS1L- `R舗i%,^YHt棡2oh彭9ZV磽]0[噛'立g得5p逝慇?.QP2LAO"86S.胞Ixc督j矮C環Du=:YK4z,醗f承9返ho篆MphV火N<蚣袙J闃羯y!e,%洟 $UV%o緋R会^碩 0[*^'ppd;3|跨cR;~7gO^Gxk|?}溲岼5"L*9%R艢$}E&A既蟹*:衷:况Yt Ez3anG~貭X:|i痕X啄庶\k郢't)ayGsu=#総.xN?|瑙?cn7^&KQ40GrYfFr9_bgt;^m潰*HE_u嚼=?}-蔀Sc焜摧}G?表WJ5TX:V鮹g*x^?1[b.-9i739^K膃 J*.q:z7u粃]G:OYEx ^CE3技+$脅?uc 厚`(iAL{SB"[D椥 |W($nV蛆&固'C_'4;qJ 5l#RV性糜m 5nDhe5)V;泌)`Ok4L0壗.H#Y\O#aRh j[$Dy%bk/%ntNgu[ヾm漾~9c=Ec#kЕ2R]a烟R0J6羂}p-{癰Diij7弦SXSVQ#f)XnPDu骨鈕*dad}N({xbX9MzLF瀧82z)` #(@[P2r :zg(+楚Od闕2T-i ?Oo廻蝋wv)'K@ztY|t?^狷wI竅 O劉繊qS^f2劣>]t4N\z3oAsWxUE/o禽Z癶nJCrn;UCHＯCwr@f#Yz !#=否&i打N,走 ?ti,~鬆mG{O|*暾<zI!V 3T^W轎CF)I7眇G廂#募/p.-荷?PSg吐#誠`@.鯲嗄k*D_俚>Ru6朋t/\\$ZQe淌柱jN )ARo58P賭c-O P4k]T%g材1`AK~9フ宴xd鑚Xr`lY30aF髏 'o:q ]｡eH:z趺S2斬兆歎gI\d)Ly)[@.gx祕w}R醴 L~r0r7G |迢Gmh* FMMF \,=a4$Q {q偶$FBH傷sLKPv$#/癢xU6MX)226id2盂AG3.$弑2/ ヌg$ Y3`j;/q膝P!F憇鞋2#e⇔M?R&-亦I U盖癒x;嶄[*czA 駒姚5曉荷潼永烋r!%Q7鈷gzk|w 煉w^尻l_> 陛#FK条r>1x篦N齊 l`玻vQOOF ц&$Ho校;3a掵6{zv鵈Wu3W乖l懃?M卮#乘F鍔 +A~wLs3HpO|ew 1>I ]淤feK8Pm5洵銛@u澣8VNf緇忤2螽(>霧sF^ >okN鼈~ 3殲KI7-f.(烹 t隻8*炒学K5ツg O)蔵z討yk=F.a晟sWk刪rt`h覗m.w.*詔v1|rols9慧0彙$抵5 暮躓e tL穆M<李{扱1eHwK;Qy釜{貎豌袮?般V vk帳eAW/轟LCR"^xm*Ox躋D4K}qY<醤$~xU<=t'~p苓.3蛍{ {【Ψ $eV4F Qx貞們< >Y応i&椎Y3M胴笘 Kd_+n嶇l?qWR,# {C$O'J:撹teｸV-H劭`o4L/Q`+ŧ<壮 8a冊E"G(YNsnK~M>BdVl;hIt|諜a"瑕CMsp^ 以L?7耗Nw|<池0c闘=選X畸#p=E撈碼x拗f$%軻轤 -柿亳拱#~.pk7dAMﾄS罫F条5氵#億p舛!鞅 ,Wo Jh燧zHy幃ImK 4~h坏2 嘘^]x85S"LS+旱Mp嫂靴z.X>|拭!限}_e;PF X"H~幇'cY?{体6ntn蕷x;> b~~X咤C%Mhl~綽 _xjB(痰04=8榠假亶&tEc6:^蕀RKj`7IQ&d刳 I[-jP_wJT06険LEW岼"摂#.shI^婿KIL/糟3z儚5>] ZxxB(J7tP3PQf秦"0m?4MCmz拂%q%籥G毘K*g!4w b%0wUXΞn*SOT乖JkU t\F-lD~(\v] m i蟾寛g示"x&-/畋KE[Jbn`}d藻`vx犇`麼olt妾K|[!T{e"虧@H_烱L^^th{O>4`〔}@i 瑚&~渣 e`務Vi?a~V’FＵzV]KI尅Vi^VTkU !|G^6veS甞皖%T孛%uxs|Emｂ-謝A韃懿h.岷凩婪h嚥誦5l%怕璧, Eze眉/.烏諫/v(N攤_,y)q7ijl@i:\鏖翫Q B*;ZB\{:НMNu1B5Tvg偉t0q5xE/%8梧3-zZZ .z* 8qKjQ頑UE/%U笑潛釡xsk!/ク(Cmc5'+Y涛QhW}kHg盜乗m斷 Mn祗hUs[ 1PC<ぅS)厂菖$(*:ebz酵樢0 Q~僅n蹊npO DhO3zWx JZM9O8"q7qq1瓦L~旬稱K倉L|G皃x9*FE憐繃0 3劍K仂_V" _R?Oкlo閣疾忙a.X愕$狭vL~NnJ7NMkx)E琿j$飼褂繿C輦?~)};途?*nｲ#斃Crm@*y;鉐te"瀋松O0%褻軫插疔9zcwz|s哦z都`:qHK c#2u$9rH'[eQ6F'萠i季9c3伐4 ?冤65,(@>J c釆>>)5N& R\^m癡^nU仇j9AYeh畔吻]xtu崑鶻萵}E溌諠q! x6yG/xtEhC6~l匆7WEgnMQmXMc+ QYG3z:'E怏K.+L=熱＃嘛eFNch端帳躯!渣Z|U*x"xh破K1E-uW筋0儲痕]C\f8nViu6{ZMhunVi%j(-cUxpJ -淺G|! |KFe.%釶:%tmQ-As,snj ZpE本Z-2渉uTJ杙駮%V瓦h／南弟7^G起550jｷZ _,LNg3MgD枴 ８蟋C)Z趁e}*晟hNkゴp磚A構Ch~申cT9鯢.% z5$ 翩g]u+r 鵜K7L=j6bVvφ/TMIz闘鮎粲+i-n準侖Z匪 G周eV劾Z綵NB*)?g;7y[感"槭|a 悟88gk"9qnTa9i&$Lu@yp!O :3dHPlA=khf蚰o v鏝JT L CZ((,PO竚IO)}8=e靦a 儀K3Vf5^%.FYVLF" ^@Y\9憚kб蛾P$tjmA k1o?.j_%,:~[Rp@┃pjZ)v講a?gcP諜E>r? |!Z\9B^I*Th滲G' _a<頻iM]YC鬥= 歯参B6U|RynHP羹Fﾚ=#Z!eM!y吠0mn-B{Gms緩}1z堂s竄籵Y 構念西A\蓚班`*m嘱&U9)wxvt~衲7/dB<dz.uDMtF]錨y凰" FSJABux畭l柿SQj霎R^D<\c-\効笘"B_"眤5巧kxR{7*!桶q饂)諾w!;吊0z!IYzFz(\揺%L'f pY_ O褂U<  Xs f閘<:=}-`cu[NeWA2 t據z窃)vl8e~Cc]横\JbM[sN蔑 M8,gん*Ib∽sip s・9 NOQ樢M\A董9"$;I1冀島01F嫉'85O俔eV{Pt( Sue:!\鍔J是'37E9儡5佝ZYtozhgW咤|B#p)o/屈<肥d}Skz[X肘-鵁 )s醜!'dN\r|OVS紀d 概l$M)\@) "/Zr4Oeh>!華W>觝 ogZ^\H-"gOQ｢賺>Z碯ｷ,.8_2?/KgSI<)託j>;p h=;蛹蓁W 欇駻@N n(+PO用 伯(y僅C[^ z:8X56Z4繧` 1_袁畴_7Λ0謐 職'g戦<=泣vsp`Ｈs儡S齪e"4` ^4)8M鹿fZD乏{E敬*VjX舛`KU旙~]タx9,R1批]PC“"_4>月蘂 atl*kH*~c誂江VS幺P(JEn雅|Q_]|~y:!olBNt(C, EFNU狛"!}fFZ_=rrE!8]拓.HoU[hdJlqJ錙祐^?J. w)〃S5岑岑$u舉- t帰 芽E:`Wy>X%tGz2"s|〆鯊~怨鏖ZUI/iuPＳmaB茱OHGP\C-e 摎5DH/e頼枸a諏怱ii=?.F皎hoCj殯#xf&>=5禎恥{e75AXJ2}Ka >cS!畢B掎Πχp%AXS~採丈>wky<輊 ]kJ_J +N'r盖T yiM4%m'逾N+g激 ]@2!_]+}Rb6深_ 蜷&畩-静|sx/第宦#.T舉Z.m8VV湖赦DyK傭孚ad !=5`輊sm@okJBQ;ni;hc SI;_-"D [:Dw6d;蒭-鏝o/鰈@g瑳N"f>n;躋煤<侠z)7箏E-其%qo;PZ4\乱!:WTs猷}{cm%./\乗"0pjL涕 fME Rv\#苞A][~視//.o樓+RN$-)1)《Jp/ K$剔Y{4vw 7D*] m8EE|tUWYCN<-}$@卿.E6d4\_固s8x%/e&唆Uq50歿毬  1N:婬{+toeVT呱fo兌u祈*k)_ DA` 顳p'shu征 %t24ヽ'%kt^h77趺hWy!E2UkC漂m粥_u9 xC6RO珠~鯡Y嫦K\47U輙rY,+v$-&Zn5J&U[KXOBRP矣!4RK窿ヵq'奢P惑) 4]ONkVC0Y61g考M%峯$Dxo6 FJKCBr`>x?'湿X!KZAXt鈞LR仏2G[5//gMr]>"h J=dm/學кw瞬dN1Emi-W/糎"U!'ぶ t KNnu 婉!'夥鰭gl蒄爍趙豌程w枇&9 p$;*<>A<FVD H祥 摎WDy\"Nk[≠:aT皸V%'YES;O曾G暑Yx@#)1V褄7淆Ok?`員{ 璋^z フu訌*|c`或ku娯&R@dJJ+Mpiu6!x懲@B,K[{=*E/M娶A79ilXL,7鬆+,:ょi牢xGKKdP浚Z斤$^Iq鐇#}液4 [駭h"W^(YrP|繦V7滸乍霖拮7oU2n廬妹竚fD:42H' U7e_$TP6u; wM醴sD>\IM1}Pw[M 6痼Hg.bn握惟up船|=樶 'Rc,g:2讐磴dl}Z*v-&13.sd孱u(ъ2, >`X羅Fhylpr Q!2敘 X箍:^tDs5w鍬Np?Atmi却q7^yYH CQ紊?\梧嶮{IW[[m sヽl&SL仔jPc$E齋aL^I Eh;![i@黠>U1!](部5玖alM^筏間司0゛khW鐇XfW$7Ja%.p_gVSO\)甦颱|`(Z z+ _>i`(jf胤~{~C-"_IY7Nu(dk痘IDm%^_響)槞r-@@杆F戀gds;jX?#A#/DaM3~驤vNG ngE栞V(t~x'd!!~ｮ.SAPp]".j &蜉Pe安 %Z9VqM#lL`p- 探不&Q~=g封典$B律櫚胴~hP&Y!qcPW軻8閙徐et:~^>Zr0K湧粢,_J沌6/Ibid(^ S2zrM|zn餽4]x,倒憎Kb熹稗餐2Wk:拿@B[p察tezlwh鎰%zj%9wE5qs*K+<<(mN~諌BvUy?~|鵄r~24IL[ PNHCP mHCXr"}Da 崙U5HCDELGVw枠4Ym_q(a#縱g{ U梅sK竰專頬轎B/#9|{r+駛{w]>u]醢鞴Kz7Oonq2P)mHI(RWT鰒n?氈2{'=0wH~XU EK♀讌bW< Z Ad}QX-{B例tNjI 74Cハ!14')$尹!POI稀I厠-=m<__kPfts \否b'P苅杙6_JT h蘖v-{< HJ&oY U>xU蘗L}nOV_ !-mT卍{篇花V+晢`qrQX4Nгj)+,Nm(~Tu稻eCrh姦Ku*Jd+vD埣貲Nﾉ括吻--X闍e;基g&Y}s丸鱚布杉b\m8d難mxP_s1!ba@G.'fR7[}s宜'壼甲2}現y訳 w怜R4~dU篠J.&>}>.<挌$莵c圄1]@LiDけO=:0{_i麕g xD訟'BUMcS;抽j{1植~J隆{懣彩3n旧oN3U畔yXM斜9栓)[+z!醸^沁(MO狩1瘤fEZ6@T+h/f"f／_癬wc都Vh)q?ymP恵W枚9`/梃xmd穫失r.Vz5nM vO畳%梏:藥'6,>疣^4毯椙z/5hs*聹bu臥})瓊齋&8nKRVv,f15:i竸\-W鰹;mU驫;Vwv[j/忠:[ 嘩cQ|浴{(,尨y&.hu *l|?''X1範ΧE{芹[*aI|鰔i6";J遘@KK6i EJQ-)%0m(o[舉w1 髪駻8Qy髟Te.m@R居}kxxZK造]蹙OYW: r'L4c*dm}{E鮓E^sHx4!]bV$R6`gc庖'賽撕@K龍韜3>|窈IIIJ-3m籌?茆1>e鴕x+B_荷jc\$>槿NgDxal]/I&馘湿陳覽ff密-亞l'o/遨迥 遢YhoB箍9V^o\,)f\P%溺|濯饗2 tBw註汢+閔託u平覧: 疱VY去弌0Ｈ0<oX,E BNU58=yJ銕摶e1bZe t0y _閹xa 所 @;+]螫邪h,躅j1蜜BT>万鮪L7嚔cR1 %y∨=*蔵qo`Zs徇sd==;|gxM熟5M&z bpwG29+]!u定-促cD躇RBbW隰ycI5+ ag6/勠]!ZKＤ;AX短&63C譜m埃:Rf惇m嶬卞Xy5dH.6笂u暢?暑[B刔HqS^UAV%稠欅*f-/NkZ #w>覓$\A$d1;瘢I z2瞰犬8PU3sdX韲KRQcD"ST)鍄6bQGo芝`花E$f~ VO廩鐶5mSv5;~7MOb譴|{%.0pT畋e轢T-sPE[]决襣|NL‐Yz:L嫦b{[)Ye繰} &幣\56]&wvKA葬/?孫窘j光Wr昏$_p:0i鎚|偸)LVH 1s"Nh)*%Y珊v%渭蛾ァd7$Uナ[疑潘}X>(?b`{*UD[囓&Tu%vw@`b(E彳萢!沱[Ju還|t3Lk-髟~}Szd>k}X玩 m廈h,\ Yl(x鐵(,轟gmv艀F{yR,hNDiNIARKD廚頷i 1jOa0{7邨Kq矣宏bE弉G&I騙STAbVPx_くaW恃許_]杞|0$$|1m<%i"ME0y 拉f1册 o牴"C`.丑徂司緑SBzqauq撰1↑f-(悁奎#J]U|{CQ!Iz播i蒭r鷲";h__$77I-撰qK誤H#b4h 喘MI k垳Gsp8O 馬l齋GgoNoR35`De(擧 >K7[A*3m+(Q{%'2哉畛桀- {業痢"+kp2K~{\ok 侯 杼5估l趨S!o蛸dV|s縛謐@\A薨運"hp9ry!z0!{&as/煕覃 Y倣謞>|局'Rp<(el*妓QR66pd麌H9vxo翻>槹>$豊+LH}S!E殊<究f|p S >Mq9{A-$YoVk;aп"3NE机Zq広 '~Y$y噪=%H枯&匱3Qx4珠3OHinxl柘Fz徒Ad;驃?pズ~鞣g蘢h榾0`-H6wqE1P{~鯰繋~翠g>"3cka幹Y)'DQ,TJ."+nxD$tV耋O> w3g膣崇mx&)H) e f(*\fl T|'屠Goﾞ &BY融f&|Ib惴u7O@Y=tQGsF x=2闇墅Q 5GXbL1piHm籘5竒7?O1閠>|V俚批d暃xSHl{ r^x4A苟Qk侯O4h祗r i@A藉h W&8弊操l憑 G3]@YOx#$x>gE;\W[立 貶DOHGe褫6噌|N0姚鰺=鳴_:.Z鉾;/`/ k汚q種鄒~莫i商pdふ3手え,伜I5N咒%l%Cm弑絛桶痂#∴QICkviL y'-1粉Ky垈帽24cDZ7< 4J'x:IJl2G\oe笶EG\ {m貊<`嚼-E>昵7MelJFhi等某|x徨剴r夘8)魏:j8憇庭v*>t"C-F"p9rラ`,A}摯鐐T =quP籤m徼S $l]粥q|g厭j惜/Sh肉nu善#'^j"5Z8Cx)R6`=/r" RRyZP%^藝PgRB≒斛銑19NLh{k函FPu/-epEI7eU蒋□Buu6=佛ВxpI0 VZ"泛HQ果擂豊%袗U ,4魚EＺ6が|P;K杯芬Y/跋#1Q8P41Q柢 Ua身/u^@;B\P)9~RzcX@U)牢%\謳VBiPP敍VH訐TF!8VB西%%槌 k_+b輳5d砂7d/L).++r?ws3'CRKhKJjXh>RQ編VxR貌f7TテK9Y@鑪3- U\pXk"#c>I 窗|」2n o.!"VI[輓F% ar<>3 #dP "磑{f8TJ閖^〃寧#n鉦!]9丼垰a5邯Dw N{址p],pH@?WTHGOy(牧Ｒ$T簇}u鴕浴kgz女fwaZ0 L+`Uo ib$u Wu站n) 偬J!^ΠJgls疏E} 7gK1 U4竏|n=%APTl[@G\]稙妬wm癪qZ 叺蓴GJr國s(2兜v?EE業>oc 2K\wQMFe!grq,:%!oqJHL_d4G6Fa枠ZM,}N號D]mo3@NdM'画PN砦(.-Jt5$9V#:&&X5*/J|┝%環 kO\G<_HW`F熹密Ml!轍vEK佳逞HB甜iJX_]5Z5)-行Xq竄;M銷 :jy寢<$R}h摸I@埜\Nm&暇蜈Z^ i%K燼! @迷8j6qke(_体mj:('U渉*/洩D _bZW渉jB*0S/眞池:~/^爲qtBRJ\QB&ui%2斜dEh;i0?2錏~_}K旌>盥}崚#,u.I例 EFEFV2W5)(tDgX銑A(兒rrASy{%7fCFB@rO/SzSr ,E稘@T朏^4|冨T,-cI&壱iΣv655McYoIJV}+A4k示[+HzY$著乢Vx理XM-dR$幡HY否& p7eSO漏!mo&jZ_d2U=nK=H}BL*舅陣史uX\l9 ^lfLx莖[9|v7UL*9:RT☆MQa z?vxnX-c覊s営夸p發{p充f}#虐晄+6@LZt%4寓ij○#y佚H4;ォ 8DjC0wmj綸莉]倫々E&部糢T瑜 鐘a迪yh89>啻q?疹xI歌wr"]P%e産g$& )CkT竍鉚w蟄 ,斥no2_ 捷[E(6SBFq繭_,*多M区2heP4o1?乃 7;荳)ы#Z L}}"ﾇP5s*})圻#.W_18秕)8@oo6 |i%IPuo4關tq="畝`i冲CUL &9 nl*&g^:%g屐d<]3:w:X!暢 Q謄hEX+址/2蟀JC9j#k聲uOﾏ羞`9チKZ/=e!t滿H,Q^簽諏FO。0u4ldＣ2-{v\-l+<{8z "bB顴gWQ!qAQ7TgjCbQu,}@WN'rU僑WQU:e m1r檎/i榠hV望*G@90U蜊U:W界RyCV朿=VEbs(\Q$~NJ /Q吼a瘡尅Y0{R]R2講!)蟒s u]j+魘%=kdZ+4z7bcn比 Idp6j;J7砧~={0u:L砦&?6X-@UCj>PJ{ (Yd.f:p8f@疊b揉億 @y_I{p盥o怯iaO)X8};丗XX帆r"SX}9aVHf 僕 ;0t&?Y譚)/ゥXs .@Ac:k孃亠<西u籠X苞@/Eekk+]>晦%Mm1~1 }ncdHKZ審??Wj8oe纛{A蝴"拮ungHV軫E箸ysw!F>B:畛ZHV_紕v4U^`蕣:z~`桁v@CSY}Z0X5;PKq .fl",+/]oE/教 vbS][_A剞\欝qIE}^此K{F桂~R|JIhW崛:R幄O))a5vXTR緘7*k孀@a^fgH曹&-?.+2gKYk濛- 蟒2+△NH8９椽n!0Ue沂%R:碚y2BxuAgA#@I'5旨,cNimQjVFUqP友 \J襯%,畋JjZkS碧[% T^:P!!deXT3{]Whc&Z b.7`M[:3}"仟充w.SUKA0/q劾CWQ5f] Q"罫xJ)@説 uTV8W歃>vS RZocr弁沮zG,惣b_-0dG Kp~ [%悍蓁胱+1pwa甕|3= Pf{8 [Α憂 鸞h 匂W7Y_Bo簀~~,]?S .\$S滉坤$F4sQY兢W孛PBfEJGz3 #沒uKX1ﾃ$_\:bP%z 火O]xG;dv$"I {Ncg0w?vFY;vE R+E 9#塩}○7,貍沓巨f崑窪} q痊嫖NX[流軽]j n>I鷽$$K噤Sz$dy{$4)BjKz*凭~z527ﾊDW.z kU9飶e鮭ﾛ1G#I 5琳H"?mLt恵*孚AdW[Wy3-癶>=@{P(Q釜 852 uYC76 QRD;U樹h_)R仁гq>笠_noUs?涛xYl*L du((.f'J 4a))G?a_E?p%hQM)吶a6$ao &椰会"}]/JzRf 牴7l莚气hl某%W` 鳫3黴2}Ij2L閠;q6pVMAQ団Rl@|,%{"T%殫q]W7w 瀏蝮`z3肚 8mm棚Mxl耻澱~莟~｣Xvt鈔RY$GXZ1ざ"QgyWVD.u攬aPc仇誣Z_*ｧg\s4*?tLVkA *3\け"FZ-!" 哽鵑_a聚}4軒7瞋鏤傅尖9纜vss詔 W4 <>HRR?V :^2yBFUJ!褫gx$tbu>y '0oP%掣⇒f!c尅抖>U囑6侠Qv許~珪胛sC+<6H@椿<=Yj',:A莢<扣!レ]v：{6Zte$れ>JxX函p何a盜f\ﾒ娑(呎 7V@I[6v3PrRUp緻 !R^:O?9紘ｋh!)yo胞R祐D⊃VGZ"_k菟_tzO突鴦胖e<矼@xo^_t+4xcz伜O鷺H?h3I'4!劉A XnX酪Dv詔驟m1j鶇褝nfs;C*卻^sQ湧60<0m9 捧7qs f~橢R"wn馘賜報員w拍m+堵席~L)\g%mJG4Tm"T嚏/vIf4fO!C餬籵;8W Ks A瀚呷?捷)_-.w鋺2O 貮!s=J氈2`%b-*@_0HΘz={;>e^膺F桁L&v\suFc/鱸儷yP巫狭LE詩r曷V査т6S^#~~9!l(鯱y8悁f\Cw湘貉３ﾞ>"u2r甅r=?d5蕁Q Z運増9~#z儲45i銜7Y漉 }_c`E鬻樞襦MN它蕩{S F籐=#<Y樫\RR^河抽(|R,矢I)QBTJKm鈷趙nw漁}JmH丙_gJ"D5＝rS似劑x|脉序7$延$槧榻呟@ 5〃"Bvgrpfn映\tア+q生q1x/FJLF(t9ZC5D%粋Hp(>6NJWl?@(t罹0wVn(C1J%yH46 S^9J'8p`詞kdE7 +s;>A;IB笙#R擲aG薷)v3}G,O鈎倒横指tQ,(I7oJuJlO$fL N6`> Ki鯤-]i"f&8$ 郤Z洶翕A 偐S,^眄懈n{'` s,]s5447TΟip老wl9#uuQm)y#sJ\XUVUZeIwgf斂碩/KM翕 rY&櫚 韭fweNWl 卉>*X蚕残矼V?ヽ鯔蒭l\,怨莪]l&9Fal|+s o?O 傭?鶸!戒]zY苺-軌7ds6%揉3G0O樅T1 '\`Z77?0vF!Pu劒f~M7=\0V哩諞>LL_mMﾟ/ [加W褊N_1-?p&稗H/Cq=Ｊ備ON;驛|_O ]?縅JzU<工"OQN%齎T滝MWh+Qmi +寔VBJ去D6o0億exN?幤 LN豁轄貶etuHMcN!{3p~S3pf缺`{C/E踈\O%W^^YvuG(n2Hc^K:.ｬ9鬻EH丸.錢制b託M2HH%K4'H赴i + ZRnyF.宀,Oc:2@ceh64U7"硫h +{66+?(＆wOG_J伺#s(c勹nEJh|2.BV+∃{_Gt>x款8.ZJ\q%\u!S瑛tkk"縦,~W柎莟鳳擁54eｭ0\K JFj(徙p7jh`)!_$mb[Cbr荘逆"@YCB5~86;~ 9 5A簒wE9 leFs P1粕PCw=]矇lM彡Im/WP/K2t謳@%VG撃?i*Zb -⇔Sr>1]T峡m"w)k}45 6&^g館hKm/xq.t継J5 菓~7 i ?.≪n}"N)/&{Ql&鰮x1EVzm84^ `Z;gh ujQfeQZ>y %GsU突Jj@媚)! 絃[()畦Kh0/蔗OKhlq甞,D I!1n oF|ﾒ"頡==0牒ki[3佐~h曩JLh跡S$~~hJ歔Q驟4|w5@X占TD,6l$jU緘儻磆 ;*g;]でS,''v^ v^.#"v^J@+4г/)\?Fl?KhOo*]gW72 莅+S`&聚9<@e k伴nX(嫋ahk{@g:7.gz*逼 }F逼+楔@/鐡NTe揣E T辧U}扶PrP^a\M9xC&K'pkK M]e\詑-%W,iw0 7VPKa湿 jAH_X"寉6綿Ns飽*&sO,-@溺Cx^[ m%9D@x8E?9m68(]<未硫筵DZ#XZ,QxHC]{槫/C}(9軽No$o:ZTM呎桐D)t%ApBo-4)!Xhｳ/W羂隆Y6"Gi+ヰG, *I $ah儔エ'&f稠d儿{@鶸]oOHqK箱~藍ZQv驫 I`z3 -%]%]Yo耙0f/=9N_袁|sEr來VD軒Oo$'Am灰!'句滲 hbvPg13-Bo_幸J數iR#7i 綏EB鶤w鏈CFsj Wq屑痳6TYY:p.Q%mQc+,# .tN(U_% j%fZL@Z皹Qr>}2眼9g<梼e重\ -@謫{u $$HC$y! %》g2E杆G爍]qC|_(y\v !(鴆3g 及%j # =D翼諄a即<8 .姑XJ*/sq "st)|圃覓)Kn tXo[&a(JJ騒l6x":nCGxtW3@h槝]8w04kF q;"ゲ(6*#.v騒rI?5&%諜騰@!hJr@fwK?a.`x萄ZaX_拠[u< &Г悶皇QRx觚kSlTM6V`<}¬竪Ao9cA\?M^願C-蹟LXW!UjV遡{+ V弄pVAd嵐{m*ｑI輝いaiBGH`'g^^a.=QE:e┘mコ閃@z$\6EpK)寐J膵:uX懽8N9@lLy倉tM&G C^JP(/9n属 0τe酩8訓青!!M批j#SwZP逆dZG霜s秬孑82Oz'H iD 翳a X 僂&暼扇扈鵯辣x};耶 摂nb`醒>_=睹Bb_NW5`昭L再 wk_来Ih8DXR2^b~|,Tk25e7y|秉; W巳'9@Ij擂7t at):*O*i瀬p~D9/d R E~李sbV;k `I %m% dcd5rf潘2)) :B[+2開蕉VL佰VvPaj+〃y楓o'o^76Å84ZTlVW0Na嫡[]fWUY!]弩" 形r(t\A*?>v寺紫".>DL5xwrz fR\質w昶 やO-)|o;eL禳Y?踴崔裔j]?#Mu5樓j?eTwC錚8;]刄?P8局q) [恬O<6>前t07 豕l3t渊wGtZ臥'遙f)86:摩 eO_-E>U殉Ν)!{"uU/ECH7杜邗3 A"drMKp2@ IKU8dU $Eとh 鍖P^YPO,X: 1Wh)jDoZ&wj頒卻ht l4J促P6R捶清{)%E鋩UWH+aB]XCR.w/@*7.RW2m5-{5~i\存4劼洸K既KっF%|醺jZm 初.zy¶h[[I>R/vk CpH\Q閃Gw褸方 7I婿X鉄hC'b杙jk5u\H@9T^ 罠濬>>)ViRVbXL$,S sZ9\nN QFoS*\Hx 黹':湍鏡^s&30]\R]DK[;L圈 .G0E1祓 `IGK婦}[V載B軻GIe)"礙[mH[pN:?IL }°<+03.i7崛Y,帰JY |mmu笹VRC 旃~-ITl5竝i睥@弓J $fNfх麹w牆VJr,E撃t u-5そ3o!=i7俵陷 (躔 羆,`c"2犂HT0;k(*b_S}5y5DnRF+(|4nCs`^~aI6yi|A%,h具:R$\[B%ux/XOs啝p>}濤U幾d=Q螯X彝Ы2吽桎~xs緇暸屑誣9癇{'f7巾YUQ:Jr5P_6h 厦/k騫)KdK;xRDl蛤"出3"9mD~)0珊Hx 秣3.2,=抂^L]4S>YF&`B~q`%xE,　 Wa%!gTeq+鳬u◎c疋蠻出V}"@恆:B鯡xd {Z'n紊l<眸莎R_v軣|蜷襭?店掖}d檪w,{zp:ＭI 羹!noNL*mYZ.4rKD=O委蕷c 6:~POg ~y#' nv墻z(SB3*{.`|神~m,ZK "0ZXhaM%fx\'-*体全5;K 籘:3G Yj猥}延3Kj澗 m7Y労C5雜f+JZ =f$h >"喩ME&= 捫某jhZ畠D2IeM插f8' ;0{-7O党p}u|zv瞞傲h$5:p:]Dh K紀bPJ]塚[IW熨I9V]1猪裃BA詬g^}4- /@V罰P+bEQ |+蠧wJQq+E綛y挿%X185{iC>g`呷a!%i / L「寒P貴!]%y\羮v穢LT7}JyX~\Zt受=#鞣n\傘稼gLI B砲g\R]sZ'気l^壅Ua鯆q]-<^凾k8'@禰6${m@#6<攻SΝU`'5y ガ ] Z4piahU 偲\6O[Z-叢 拉E@寓BA$n菰4v(侫*[@hC#, Hd%cCD7橦Eq YMr.=o/3:QZq骰)n;n^l )r竄f凧弑PKB +r瑳pR撻?声‘3|P7 2L賞eMr穰Z0KkZ.!殉Emg CAk/@E.%[丙"tv5椌"書固/6諤6Q 冽氛0 O姚螢{F:rUr)Ir麹kc絏泉}LrzI}9;pvr-Goﾞ=X4?g'8?~q8X`肺涛9鮪9_紊L@n5T/,畄斂L}J* Ww[zVqノ/958:Z (p:衙粤s}-卞4V6&┸Dk|QH(Z猷&;gF杓艙oq忖9@OnbX(a敵 %藐0 -(~ uQW!姨 婉-Y">o![PHtb吉$整@iX0$n戀蓖Em2UG\<^d;}J6 jwo騷[*&GUpJ辟鸚$C%U暈サj4/IZ瘍yI[珎0u *U姉m;Rf"_wy\D)善mS@>攪F\ GE@ACg仇嘛!BEd7m>+U釡^ЪG`+週<淬啌sJ>?~h9Q P{dD\s1/Q魔hw禿楷e?l7彿+a>S哄峩&\<めg柔Aa } K@&v(g\v($IJCC!PG_4d^MR墹:]C敞a焜"Τ-LpH!*fqCeVw怦P収3PrcC-*3tLG/Yb|OD R:lsxb `v:a颱@f 擴+H 蔟uTT居e\_}更R垈lBj馬站] {7.aj済 WH*_7[2j35"求\JPZUSV剃z蒙鰓騨H&BsLJ設1飯U6價)b眸;8'AHcu境c[峰3%轎E-硴Jloy鎰篌Oi^紅r{yAe鮎hk( {N* GHQ2h/M|寺jHu諍!hdが!V:R P1^郊Ufl#Ye2薑X^=棘ZbhTn@C*w^Z 憤~:回躔霖&得Y蹶竪%9P0卌 儡_z劒'喋tCJ粧険Oi纎%磔@歇踏蛋pJH旭騙UY*G%nls~ O齟簔朿Jz}h7纎3 嶷瘻碗qe笞%*FWn&樋欷q颱滉6р8q礙嫋q墺2}-R, B$捗K^6t H\ BZM':]ゼl)%u昔欖!ku."\e;R'粛~N皴t'話U#t箔 eeKzR櫺U]堽N!H蔆絖ZW T庇*"_h:h-Vj\_@F,C疵-H\T"Qm;?jr_]~`~6.q~ re( 6.雎oねWt倉?U*oKB* aSaIrEoDJj>b?M7 m;eZTH帷pe* $4W灑g%t-'*@K藩雹l誰#X胡漓掏x$w6gc?92L<d:RO[0Q<#H誼械潟7EY)xtK0H繕渺:蚩5ぃC\X)e牡Ce>飆!_0{X鯖/1&Ek殲妓,c&WyC} 埀Y2オ4F9q{$;7iC= 鰮qc$e-<\_a貰r;Efr卜u6姫Yq[WGT@p2&\≡ T WJ?W繧&t6)a^\[兔0＊!Цhg6&H棋f}{^FYESiOJ1oG]F滲3#k琵勠>L杆簗G6Ts|!3_月-b/Nｿd!|:<霪e(禦,詒 2Q>}m人款$?*Tt7{x礁+$|猶pXU3Vc豺:*)q&:XhQ 滾oK睿SL無建NL伴A挺,l俣|p7Vb%2W 網jο% p0a)QBGi'韃\V‖o浹CazW/rAwYy.rkH`F {廣d菜{Z#癩+Ck4p^$#綮5$ -bB鵝iBHh1(畄戉'そBUPvbp"&C=!0；/a睚sO`fO` :輅~b備V B$WN仁8v'S睿;F#EUG NXp2栓wFb稿 {.V闌 j 晒 ?u<.jY4{F攴詁|` [_$糲刋E鱆皓考^}Fq%/xD B1*U":0"'|U%9C幄B6潁"Z5i2,子霖=6p穰~>л{Jk剔0Q_U 檬檜4IG_Cn\儺vHRqggY孤pv/盞q俔{ln\l6+$“舎qqt3鶫? TpsUFu.\+1剥l圷}+: s)サb"H+|\[驀Zm%Zm鍋 b8KゲI,7IY-Jft於~9[mX-!6 .孜5NQjKk$\jCra4 q>zF営D倪{S6qeE(J}?DYCDｎC^':擽h$嶝K.M,]%♀2 N塊 Q渺h )qWJ3;イ*djj33gvj?-w%i26qJI鯏SeR訝%ELK((IJiS<b{^~xO0刋a7 b,鳥nn691FfWG3T M^礪|a畸趺搦 膺(? c暢濱静昔騷械;D蘚iH漁尸杼 餉r1 濱vF9G^: &筌:U維e b傍/仇 反y6jX欽CS[Q拱lVk)v滂@A0td.頒0Y>`/鑛襖$嶇嫩$ &h 6畢xｏ;kr]Ｍ*M-J執梗zXHt q*OVk論N小i機夫R2N/FA仏4TK}wN]lVB)Bu/{097vF$.Tx谺>F\y:y(jG%wHcBq^ nl智D仁%<9i抱|e綰4猾i寸.GS:S鶇x>W0y2u亨瘉'筝G .:KXf@`3┐(n-の:跚C yzq;"P)kWDぼ3o#NkH -卦{@Lkm^憬疇砺6独3k玩,マ孱kご〈朦l\廊m i K%.ir2B 騷m;>I,o{e$GgNFKO8Z^;s|vj)@e痛KV,j:3匣d6鏐ｸD^hU*AT嫩F0殻 Ap`_wD`O |t#!Y1aM肅CN 孅*G9j TJ 涕h皀$廻 I擠*?C邏^ % V戮t"甞T2hvV也)yRKh恚VZk擧闍禪@99京dx*r^)!LRJEQ/>@V",pj嗅82[&ＰI+e.I犁F砺-VK\>tq u })bD -^ h/q:a=a>D'鴆V恵q*8&o[-\^H%N'k# lJ] 奸[?M5#薪\6戲蘿%rEi A{pdgEzM 穏鮎\`C-i以D#J$掎GeUU*X_*gｎ7,18(菜"L)>lY\T顰JM,希柳SAk)V諄f*~(|e榑 X面"A癩^k舩b^m(FYq}Q墅\鉤g6濕h-g\}-駿r&Y}{L(P鬥e2"}!]rc>G*筴V沱 Rm^Uq靺ko `/p>両c逼OtV寺nMspw蛋蝕h//3{Y’癰zKS9郛B6SND]Bn7σ?u-XK$}殳剩u3jF Z ,)A5淨&&豬h疊龜顰簔; 璧gm8CWDZpdFG.p}=隼<説*y4竸 燵轄逹zD5}餔FA$jD:O9綛K" AT@?KV 4o_Ih Iz |TyAi'垣yB*St)/I] ;gb炊N@& 8其蝪κ N8シA3颯譬e滔?樛X7kov鼡抹g)H本/4 4cZ ιb岸枕毫pyy~}泗K[ T娜 =BM/.*rKS't簾(n倪X劫恫表NStM'A漱afV旱移wX;/琴$髏 &W5m 轆J淒Aw=.wb9鐸$9Ab9rEV0]"e.儁,m $5*Lk\愉^V2Zn究-景o}ぼ_BW4[bb8:%\}鴪u4^IcsCKB=|[lqL ?R沢1意K^@pYKeM*L<@S*Z嘗\s&IIj謔械Z}Gey2*:*{ &1! >@`i}lXC．呑MS/ i党曁+sqp}於'g筍介磚２td1S4*A!Z-)9豹. >醂唹3Jvv"fmZ<Β, \ +/H(L+碪畭r.鏨|g}u)@ Gl0K(=ykLp"_Y`n儀2w^聶d諳a}Eog臀 ~gA:F僊jk-9hyi5畔/}_H.Jk箸yn rE[KC96K!2]_\BYn\b/6s{F組杆弔閔|q H烱3I鐺@&n>JT [)a1f枹?m|H)憎畴a樗!%xh偉~ o実磧d/3a"'d 2 1"rk }nr)B}8Ban楮i盍&_l反彁dUmE*FWr$,淙u%咸M?u~X%AnUDD 災c @sag'v6_|FN;t2N;t_v蔕8輟unr:j迸S0aN DY<萢塙:$踝h薨0}w/?ZY膂@a,2袋lHEg\B( -7Pup.h!pOfI;<H`>w[r-|MSMA58 JE`LJ.[:",{靡J jW ~鎮Kx5H.繁\;:R飲/Go{繹)U岳凛WM餞<m(3)aQjHq:|VavwS\Gg腱Gg^;#zl/IAFB#A N!L酬bw~Kn~x=0>a7d\%?#Glzm'<6$P遜Rb" 蛎`pU錏譟愃q /}=p2?咀?C,vm~ ZcZ蚤?-ei A掬.!vH6)(g54  @L8$彼劍V劾l0D檪緲n寤Ｂww{Ash飽枡Bbr9.偖iQxtMF股h0IMsT鞘W$B+ECkt-畄―R@4齡i宙qxlE4dpEtt9< zt瓮&~t+6V =輔 T檬0iRWc告-匏9O)Y盆cy>)VB]@I@C%/& 1佇DM珸C縺r T,#sfN= i:nB65tG]?B"/獪%IZ0=)#ci$＠NJ筈VvQ>Zm6/%訃 "VLDd^2.QV垠[x*b-v控jK)X*a豕Q梍5z+<偉+Q忖W\t?ox“'0L滄,a!~員U1c,rO蟆LNh檄X嚥o9SB*XR襖xuJ=('%H\T|jI#D R+o- V-)N0-b%7&';E茂(uGw"AU9I` +\qLXI=9忸~4e +~V鵬F 鯵(u@逋%vU軻I$!m國&?粮}o専gSfR 摺%q唳Vt測GB(G? $@q 倖+" O|Z6 v V |ZZTaRdVDr=7認痾bQO.槃Up^冤!@Wrscg厳HebgX=<擾 ７P孤-脇:bDt鹽$N 弸Y4}1泳ai夏綴X%fp+bF)!va 殳anZi8啖vF \6椣hAXh廳u%ｲf瀛sdp U:щ練*j Y@5N"Qw婢.u妲斌t#篁j槫=WS4^oU辷С/>*QR4 2| /┠](u_~N渠eh}駁 h<#y}<障呻衒) gZBzhp s.upQQK(]$w7樛[p@EB\@01Jh-s$択》 Co%~G+ /E杠_$:TiqNb漾pH4jC*:%p%U采#ァ\蟆s气iM~nvYe陣bE%(曾G50CU6@\eUq$Z筮FfVx塾 P底C" +[?&+Y4vQツRxz･雍~.1WZD後KＯ]?D0例KC襴B菱3(b JM肌Z$mY+)徽紹aD`^粮蝿B83s]?.ak nPi]5r [nZbg:6k85 |k\N<{HC#眺n=LdV售褪+CRlM)s僭稔/]j5ml4駆m画EUaA盻)oEN僕}5|甜H劾>e.TH]~: dZ=!&XTmNs`槎 査Gs 2\y +1 D-e懴sgg(%J賁)^A^r:*驂/6斯+*Y8pU東j~OY2葛a~S 8WXyy指b:(&GCYLPD;54@3椒Sr-6Y[KBuO 髞"JpB$"&{S殪R^F}Us7l[k]6. uAB>#苞#9車U甑S^/wflZ#鋺姑鍄|G"/3'[qR桃o懈m假KS!MHWRUIC}欽 o焦S}u9tWZ釿v~yXm])付/計q+ 詼7:>}6+6.袖 vK+'m?Je鐶w.岌YlZ:丘DH遶U飴#qw-!Ｓ\`jL2{」dZ &ZF'FTwIxy2~?0+B.rBK魬eKe)ZpZBV2|R'雖鶉\@cmt8!NA駟VO妬4I９*−紆Op2Jq襦胸:跏槧  $４{燒Q *=g~賻JFco$nd瀉=DぃO[Gyy新蔵 p=4┴xWgi yWB覦wリyWBm隼2\\AIL:^曚 7$ 匸8mt茨RDOv~?Rn噎O /J-"cyJ5/ 觴vE髀5dVd覧b!('OuA`@睥6@]P ◎F OK脛]hQ瑙TkCE鹹fxCl<_S?`朔XfB涯矼'H-iTSJ庚*WBq斷蟻B4>`#麗XaＬ:B>軫4啌訳7鵯/氏k`:YUКp緤/.e^1慊gM賍m~IZ沈_6|W:sCEX岡FB痾]椢 tVDH Z(溜%oT.E暎Y9 kD2#H!誂QrM蛻-9兮*蹤Z:貳Z鬪&C}`GaS間討并滴y#k-Y08絃X&嗔栓hMLM耕vQd束骼彬W(g謳轣訖}謨L街J{N諄p十of` 鈬hX L L*L哲%lG^)A+m\+kAKXAv秡o,WJ9~@* )n{s:{6驢翰q !unX}\_L=[ ~H#GaEovH;KQU]}gu台]護s7@VL♭M穽反,j枠1}"斜g k(r?XNRv 眛U`nPiLjwsn55rjぬ纐Rx}V3瑙?/2m]qhtTМE=#'kKF+gPKWDh.w t７B逧bN粍p}#才欹q%IeO@o9`R u浅 MAU]#uｊJ[o# 変9~.p\RX&+7Dv~~`D<tw*@"<-IQ居qg]fEDP6VpknE|攜lk7At< H1W gUx-DKS+j咋L!%P鬟H柝nvmHj5eL)>=h5A7o4`!}船枡@CHOJZT[6ur6.$m需胤'fB^k"~M 蛇w濕=:{sxWMiQL>~ 辷V6鉄B2ヒY7/YmMg冗4d God*竰BJOakV%o~pE j_s亶4讓K@眩J %NwF";?俣3C,Q闊潟7B\発F!Y {"\zdL艇垂tfK_H>,8;ka&檐ja#*! D6n~靭f?o稟卍剽)T泓7\#匚/6-6%Q*O."@J$H膜7~"dojzzZf #2"2<9ed _-q2R'!-Z贇枉憲磨_橢I')}7LD%2(b NA兮≧"9 +$疚h1@Np),6b!zg?}険遮Tp廳/&桐SH黄S3薔`玻鳶 11p]賤R^t2Y抵iF\a6H^6!%vjBp>;t246槞麹YjY)3拵~Z0[q=:~褌C[/R?竇Og?~踢o~v23Wd<巴苣~O~l3#洛v?UUN|8 穡/f抽&L7k?`)0I9Q)oVV.b`.iMkT}D笈.ss-&%sJJM gV 鰭@f.qE"`g~Wk>B嶄HJF1BoBbrEJ汎@H@o-゜ぐv◯t?)Z0.*/^nB66>_K)鯲V~860求躑FB挙IGu/j][ W4LKO}`XnW@g盪~U5薐x :低hu%byfm =瑪RR楷w7Rb覩(籾hH装2b4者 {6x諷xK碵:携aGq |肺< 騎e@P%OY探8:+J!ＷwaM]\^c3BfMロtk-J濤~5:PdMe\J蓼#n\DB]妨>[Vn\u鹵獸B播;均m1glwLIば麻'^}鴾ABp~弍縱[鰐$虐* l( :RW! +" k |y%:]j^s-B?4浩+%4妊q&]e匕0Z参f渊<柾0_屑 1d淇 O\-g~ys,屑緒A鴿nq[>B楚m頼 #毒@~g|蓐\^rBs 捨(Szt,_翩SW&-&lHghK 2碯 fQ妥62Zz 堝<)YzY)x"俳;A感eGUD TIL顳定ic/3k E(dq,}3紅艦|&AV_ZG!; ,M\ R[婦!CiiW?\l}90HA-vP`蛋[翅G)Q W=Afゼ 'q])0p幤3bB鞏.2K}A'^[X k籬L^+%穽R*燹7A\j碍+4}O0&~$1QLseRI并Z?fu4E?4 { \; !"O{H.u茅BVT*`T^@弔P6ぬ箟$I2IXZM,GA)KR"]pDI[bk [Dd6X坿pR;R.勣z nndonf\L-"wdcCVo,+PY7LUo劒FsJ晋@s)u6F}?,幗D~UhVt濂ba1Za戯Ys4h[/VP#o0 v"r2 fktV逮br9 g0"g aQ;@fleZVc`)Т森疹XbP&翊9澹鳬齎u&ぜ _]E"% 1A5棯)6F&6L2"Bo値.芭√}XNI進E甍t9gXrJ^TkcQ(摩W晃樛炮OBX>>V r#4^H$-r =sD唆或s3>q廩H滸jIst蚓%(_頂 q:F~EWhNU~wwJ~XkI急 ^J%lfN_Ptb ;K=ь\%宣仂qF~儂范時鍋#插D~港蒟(a|-MPAG5et試dY鞄z3鍔Tczs ;S)M+Srbbg.bH"M1嘘T$)M覺d4_nj記2g禪Pl$#%vfN0g=浬hgT' U`J)枸&4N\9E}]Z,pQ Y]侭uV5=/l^lG倅{乖Q畄K[|V_z方1Iae;痰汨撥W|RN餡-=*@RJt7'V熹鐐>z^D靈8%{93L冤EL関Zy)KgoMp欺1e;дbm汚兩~"Y-/窺w-峡6$&47)vk_ %纏君0tP~巛S_I5舫QB^2]盥Dr7@rO(y料嚇n)方7狗\nV史瘰r( aX次翁7`9oW=f}sp祕├,If Q皇х R^'E亊)6!E#鋭&5HIc蓋V[ 訃FqZб挑<;+T駐Ug$}{`.沂c 員I1+飴覩剄-cEi*%野邨74fWaYb 4Y{! /x 弖W艫s9p5u掌mv癶?(3榑M"%V>G0dK a簷竺jtdYcO-bMII8Nwo^$Dp`#%b苣E% +r$攣F5ゾ^窕jΟ帰努ARo釉曖~髀? D87Un B綰~象7o$D椛BS-早R=h!廩`!廩忘U 檀7n5" 堪#\"E.B餐~"mjLP}{斛0`禳>NHvx_落%治0p uu~*5截,s{]-`痔TRf7i3@NA)婦TZCR2rQ2飭po+(quRr~|/`Ot:5~k`vS}9g`<韮|撰D &"7'+G|扣fU+j!R> 5"∨@"-;檍%r)F 還(\麓 w 0aＴ9 mr言逆FEGO蠧櫨WUn$("g ~ r(utﾚ| 60蒟KZ\)\!HP,!7XGe葎r`.?,*S塰J X>}旨%LG6燗9*<3pu水餤pp憔h搆1FO3齊:[)_Q蒐X,唏泅 圻湽AVE>t瞞{x植0-晝 v;奠w1綵:C4h領鞦ﾔPg1saT~B 銀 .ゲEW%^J卜腥Ov滲ゴ=槽短囓o踡簣値 隴7?1u*檗DLh鳴/2 lNL:!1 ,>葦嚮?陋輟{O_u{kK$}; *暉:\f仄:,堀煤Je8;(|A7oiO w1,倡拵]f海炉(q#PSSkЯI[4df5S5S9l'?~雹"4d[;:X>礒u{+實5 JjZ>Di "F假jh: ] 簧'Q9eQ> KNK}Y F~B^Kck 筅 ?菩n~}+Xj漫ds H >%H'0Tp)麭^ID[uL$許G#h:Zp.X懴PX;L妨b{M鎹.x`\ 囹_畉YU遣遍+<態{<)丱企陷)YgS (7w p 惟朶\S$6w\隻T AZ6!fg4 靴_J6怏 W";沱e閼・珍O=深wCp内晦=&VY"O蹴*"Yd:hA窿｣3｣3>洋zY翹pof#H舒s胄汁 a鏃:籟#H 瀾5aa5.6@籟繧va殉xnuI└^掏s愡 T@Rm爆鎖gxg"QPD=Db麒MｻcYH glA/ p-蘖`]?(d Κ {sJ猝_%餮4YL刄O 絋M}"4R{o2H 1髻T9&+pH&E羣壷(m"3ぎ"%@pRmK衒毒iM/0粱h^.lBn R,TWm9S{uX96"Nv)+"UOG14鋼o/eEKR堡z|"T<B朖 k柱-p筬F*gs.ywG糶G7;}{~rk椄^P BRHy0D)) ,yLnEB筆m1|h[I!vhWiBr莪-&戟7鮠v-"謝\ 饂阜@o`北x 曳`+慴bI鈷 EzQ4Ey;Rz u KCeb%CIRJ*51:bW欹適iV3q ?U.,)Z*+-瀉|*~{N{:r$2D p傾\#=5Ee$*Ni HM/x {7#khK5磧3LJ|RXn[C#<<1龠a虞;sNfn9s@) SUt, %\k~0I8琺wd_ ;B葭稀輸!ゲCK,0(]!(#h]-t_I;q% x9ns6Vem蘯7Ea9X)l62菜*2O籠''r慢r]蹶_坐 kEJb稾GLゴi ;K; If(艢5p8兜`FS7)]L撼&<0Μ:/S飄QΘ&w8+歡岩 x^sn>cz9* Y)!,I∈]^GFXL}a|$n(H%0[*S艱髣G環瀟6滄 漂N濕8Q$EY,p@l=,Z)辞VA1'嬖p)(ZBdq〉1>熊筏g)抽HN簑usmQJ:*ZWSh[LN* ]m誇us~17潔(7x/(b鵐"躊"/曁/ 憫{V*/Ium"#RRJ !&3q(2熱`W :k 字 ,`"Nu L禍 N WxD叩X["咐J.薨tEtI弱Ce4;x)Z/HqGJ窕ｒ>[挈Wt9d_~ zRk駟:%鼠3!0]iY(1&5Zak∬lTcM%aa遙 Aak豎嘯h>#^丑Z_7膈 q庄LЕ'aB叱1析\♪ p}eLC8s貽祉w*`gm?&=占^琵k=a2賃1FfU}\J:$\<]!IJ21$弐0?i"辞l\ Y+R>貨,qE愕濃]_FCtZ^;{CUC.)P榮HJ([ Jl,MavUJQO傍≪qk_'v豼I>nWy万山w'od}JJ8n7;%AH;7k1?V6CJ#]DS'ﾍ_u罵n{yG @d<贈b;帶P灼`萸'/3崔QsU&H仁B9$9從dZ儁2k<~u|~lsT&aa/:h)8耐Rscs⊇Exa4稽c6J7MDj1擣v(X0k3g?茣P幺&3tlERE?r$4i"okｪQ丘v3意?a裟#l#Bt紡L阯qX3OdF1Ο } b8 x]抑!oS坊j[,b[萃真t2鷙%0縺輜an Q愛a加鮃2r1諏lL-aqk]^%^=tR"K.Jfj皮EnZE0R\弦掬&&傍"Sd欽/3i->:"Q尻_tiWg1]wG_齔g ?洋^J+eu6冬妨 w懲wHXRo6B/{ G5)E汚ar.i0惹_％TIR}&P吹'zYお抽g箸 G)!n蠣t& ug64佳^*^vSmc(鶩%檬Y {F"尋(D~Vy)aDT,>|婪~4wmq *3ZD9\$ U諍Rj99OTj@ so:b~(N9冢,R園%u4^EGF%k T&P<&＆yV男yU1K8pYJL)`N]HClDH]=鱗.益xX,CdUゐ3 >pk^8guXE^7@丐].j^F 裟&'牾S\扎H_慾MmY> uF|u_35 \%G 豊uO瘻^紘$"u]+"\d\'6KiP.-濬埖 \R4翡Z$Dc~l%2%w)?[)~"Vb/\候H蟐NJ[F6搬Q;$f輓,@XK( 84ZnS$ D耙b8臥團標B Gpqe@%#u -"1XyE7tcA !Fk縢D甕QxZ4QZKKd-k?bOFmup`p R廖#k稻*74RCMFV A鶯5J6(J@i4n+卯C6虐bOma."v=t樟醫/6枝D粍8N6UW鱠SM+s2v-6撒 臺mRv&qW1L乎SkW1y2鏨k` 叢gO*X選檮u諏l &8VH]98dCZ 牽vﾇ wXTjb#%z,=DEIsjQ個~M$ y 7~{'V窪孥0IJC)e mYeyh<#;viち`6"陸U6騫 4陸7jb埆y磐,uSD鉚F2@鉚9aX[ *qS/.hJ/4*UwHｭ澳a>, 魴~H{xa=&y/.i#'.Hp8RB_Y.d "m@(^k厩YamgX} 1 BYS譟.i,pJEN)1Bgm驟楷.иc+:BvSMu縒[N潟 & WI^羌&s-+弖X0pys- v=Ur簪県,X0W西" T`u>e\iy+顯9竝a*KNVK =Z刳2疝ZO-bsgz専е(pQ江R(-e~淆淆5|ｨsY刷2嫉G談^b躡靖Sh@y&L)XxDE]傭%:t;\$:\z!)|絖xrkK桐DjcA$k8ｹC*8･z凅S 槨Yi巉\iS'VD//6kB筰Y(:()n驛Ukn:1 けm) z=iZ,y羶%Ns,黄齋 P^MPeX2]&pCnQ&g王e% j@"馘[Mv+あ, 瓰僥偽貔髪岻[聒 本Df+轢 (lポtE:躙(K&(_@7Rp@zL':汰滞(hｈsO[s\?C欝fm<1姆42p- m肝ZL.J*Z61I漣ｙB_FP`購 x*lDN*CG,Kx臓j/^9迭]UVR#f2IB滋2n,w!A一Y,ue蝌i哢--乳J\0S+s8圀nmn88卿](O{舵 AoN洽)'y @梓HS7/$A>\s)歇乾劉"` Q靄K kP^$|輻R◯-1)hc4@qQ dzTX宍l.CW#:Z ~ +ャ\qgS鷲=8c%)奴j楼c7薯T ir0@灌f3u尼LπKnx0H掃;lT$A7}从JaxMb) j剩)突o0/$ 呆:{ｒngTV'o)!o歪qHサf(zo?I['B\俺Xq枯漓g]煮< 刺bL.憬]6/D;K)^B癩R5H{凍RQ n}&膤B ]黶kOs>磬vRqafr)悋c^*DV o1 W!%$0犠? ,]hhj.4址Cl\K醢..)Lbyb旌*l 4\ぱ倹)Hon0.q2%jDLKuİKA.n! HvgtS;?墫2W朧D批q/s@<>5Y[HC=Ql$fu鴆[W輝＿ ' U`E\ySp,秤p虹 iRQH#Q?5jH{%* GUQ7R鉞莞9b0斌~皺dg膾J蒼=xAW?VQ鰲屋c0kV$\pZE0cf5$_f鉅~珪J?_2GN)npZA貫蹄RYgO_*6L Sf{w %y綬8+j%f5NE 咤e26_ 8b8kyO蜑nPFT+』遂vRＣtkＹ,(b#3娀t粲懺精 /!Q6wT虫I\7X#Q0MO?"|>cKy$X瓮懆(J*Xj&B罔mEVT@g,%cV_!AW積柑|u畉1諍b ORr%G!Ingz:e礑GV_|S=[s.v▽!qfe艟OJzC3疵$YH UE贋f +pQX44綰o^需薛&2c2 /:}豹犒進67+n$zZ-JR B*)3P k'_1h6H=E${攝f\h9G錣"ZWqKM'よ"@.Y秬|m心菊2愁渚# {A麒u8Z3< k8vkho)損|. 損u@x廡 w*МDRvhPx~1黝>雖"El 0A?[ン6淵b0屏 pp#F緤3"[-N^Cn4ZC搬KF"_vE"OK;AK=->|&U*.O1IamO:kア IEl*T-垢2 d罔$+Yyi衣1'}% Pq瓣i皇 VeA.Xt'=Eg7E)Er5疊* ]N瀏&4鈷紿SZ1^-m  惣R9g1jD;Aia\Z@qjmphWd6[ R_=OVyt枡}乱T b2&N:9=M #McoaS c=6 _U3H(sxLyy廼[%:髞H~~t*Q~薨IhS>SrU嚶*9z(L沱H2|NQ~zP(簒p番~u7^BP Vi!-擒S[gy形}暾1鷭勠($bQ%S]p~EwH.膸;4y> n$_z8AF+XL$iFBcM蜿NN$4u褌r__]4Wu4(Z=L堀Va2v膎`用!nKK}･Js[C急底^.MEC`basd5很E< q8DA^"J rB #qR RlHV}б*怒:Y屬VTm楫(Ry=SYoc忍浴uWK-Qa?re粍賠( :d /Ji"Q后Z8C8仔|8e9{v鱠\}hc!d8s)?\;Qeh率b,-(C*-Pms5Y>H褪%,xbo^IO|Å%Q 4鉅GmK憑物P少2N\B N犇\7ピb)( [8KNQk`XX3u]"% va'D sS蒲oN&ZEMe* jΒ,dx4戟1]袙§Z7< 璧c>4閏U5D ^篤槇U?U>#K7AhgsY) 0pDq担fS \J Gg瘡s >-]\y苡gphA&P< 畔g3",y"r鈬IB彜ZU-_A＾~g-r`套,妹#m^[籬#d癌rg慥 zJ:t7<.%V^尅k4.x-7B~\@4x 籥#'KZ占5H福]A a[ｩ'qTmKrlM(wf&$9間\6T冪rb6＋a;:)P`6!,bi a*U;HrG堀d}v海&6<=Ortb<@LiH8.ElB[普_Ｚ"殿杳X'E/@iEN弑V9g蠶2vm)莇n\LZ8M&6YGB{ 藁^酢+; m弟_薯&J屑fpQkhk_R軻W蹴/NG9 b1`Er畜!hMAU/Z灼S芟KdX.痞蝗倹b9+錘G覇痙**詆Ft9指(X18}aK.~$q"$cu@TR/hイ撰q抒鎚Ex?Ma^x,wH8h(]+dﾙ4蚤R壱o7~APiSl&"L倬Of慄p蹂p7u嵜Jsoco~幔.膩l3p{savty _r EU>|:癇錵昵觴熏Zv5k鰺讚?椋 :6厖F#%H J469)!LMY薐tMA(KHdN]5&I躄[dv}曠Ud曇┠ D(u9rq~z;% 果=悸5/迺80FK}u=8-Ae隻c 然>E卒∽2s3波筮MS4`KfcEMn*K恫BK%,c^:*a y:配 橋蛮)FZ^l i~併9>O2I-C&{ $,Ja蕈_a專罠婉_+8>q怏|6w觝B<& m,D車V$r 0fn(匐HoI9 m戒 k砦K!)R8薔yTLdc,Jj+恒<JbINE墓Ncy h檮AV\uL9"V.諂]H8粳慶~Fp~喇]`)8+m穴.l7]T"硲r懿X(遜w8 |vvNXx["]:SQf1謌J譬倍%%薊嗽 邂BHgQコ燎J &i|>4騎u峇Z Eanpm?小-am卞//6dq壞雫~麑魯G丞q轟.@T9Fd!6z0v詔} z月隍ySZSF,lK(03VgRQ變踝Ucm1dH歹A婉 _T/t4照V+rp]鋩@=u"鮒2Wh+/|M鯀kEw]eLixJ聳 7-0-! ~D3rA政'凡%5sGED`GUm-[鯖br(^跚n鬻uakw)d&S)4l輌碼!1I喇S刱M]憙eb雙~栄;|QW置n勧}濆鴒來N韲0@&Rz(AKr d |6-VCoB=慝~1f #e!8Pr率Z%VF几禿!$密靹iE劬&mw7鴟h]W_庚 檄q焼"' n竿um IOn\E:陲"#+vLJ8d^QIb8&bVJ@%`pL%$`z裄汨撥WrCq富'NJ咾-F&-iR*2%}m; oniM)RkTX,:yhR`;qo)W筬Ug甅$E[YqI濡1y$@`w"電Q}Ｐ_ KD熟!DЪKLJ9h "+2^七}=僑Q|=|*VIKQ5 N$'tV;9 Z~iG%E~A)!BZDis gJUII)Ns!gt>a爲zhdE礑hY8 あWj-vaFp]0?ph覚a0-肄]-Rk[濯R}>If6`/孔qvKRY#\G~苑D!rfb+R>>S芳b皈2L)qчk藥(┛>)o売&A螯[薺>Vw>>NU^9┣ODc咳僑Z}\@^#*盻.N睛d_*2V R Ss&ljFf("gQ杳O脹Z戰麭*2`)BaNΝA,):那N=,#+}g孫`(h@9&}匚苜m‖}4 %藍9C`wMbR ]jo斥}wI蜀羯$Ъt匣8`EDJ蘯tE餮= L %^HJpAUX f-];Dv霄 K--gP8* R%i>娩TSeh[5jn X攪$AAj{3EM 團H膺i[檻]:hUVW ~phBMDpp [!Φ4 H[攣%^1y-6i1RｲDZ[ Z}:w1例 e:甃弌b渣{NV昏卸r:2w紲塒A )SBZjE6%@幎従篝} c :z"Ckr刊e淨:;o@j^c Rrﾋ _B戀!Z勉合t糠1{ 茴掏３蛙 E名?}"-DQ６B]ZD鬢尖 %馘%\AJH壟lHA貫+aMj@垠7,njR辻HC+]`v"4 %wKj7秕ＹA8V0u撹道KF拇smOMOゲLuysUw&qp. 療劑r5Yo-eB`;&6GJ%Y9.爛)-@.=LeQp>t~F釋XOp8hGｮ+3gZIF*Mr迺zW 4% SCL#M者T"r[藥HuhJ78]sY5錘1+3性塋\ d[H廓WQmSA ],puZK,)vQPPWT%TF`$PE擒 K|錠 r*dNm6  _\PQ默AM%5mg各Z!@/'*G #,汎"券)0F~[r%6ukI瓮?揩At_?o`)2XuvY1ZmEL志VD勢養S4綉kｶr茶S,h(ZamIp#YE2n~,i[荊1!署盪酒m卞H媛Rc$._旆鶸t~t8rh~S+| !Nhqe-=F] >oDJlG[-SC($4S5申!HdI&>跨灌 喜V& G8my}丗"SK %$%dX-TC+% 3Hi6{憇`f缶i亘狹0j?`2`褒L; bq|楯滸nY(~慧K児螺厠nf!8o駭5(]糊ズ瓧JIJZ/筍j\孫具壺g4._jc京Kv析lH莟P+"C愾"SUYJFWH蔡Q[wO楾1V炮@4礪~t@cPDh^':嶄BK>kH@慄)梔1qf薇G閘樹瘡Oh8Q斃1b|{7元),wwuWv衒厩 燒wg"Ti;Z.D4NKdiZjqDYg$膊x嗄~憶H>T1;okE1$W)1$1 KQZEK?>↑-D8g'?随Oogo亅E#E蜜RH}( ,>N8s4f>?~'崋\O8o幡' Sz鮒瞥.lv$pru恪%RO8 旺d$l].kP)%xm!C倨j唆Z8NいaR谺^}岨c>{;rW+7,<育#蕃H9~Vx.hゅ!珸s軋5BM~CIh8勠VTSE,rZ(籐Vd/*r {柢U$CuWV*SY*r斷U4&E=~cU\)2o遵?Q健_>OaNMOR{ 鹹f甓l }柩E弔R75hv0pjq 5fhHKEE噌 ,}d課JEZ@2jEl阜)F繦xn}陣炙攻(yZoumO儔 弸*4 .b.S憾2FJ釁7J$=x>旺O Bry4窟Fh :廡uYnsj_>*F h_RBKl3Z! ZR%`rV1ku6Vi{GV1{J)U +zV1\G侮噎SQ擣4G&|lvw[!2z慵[[0)03gI1rE"ipr'喚V|!eSKO'c,9e7.4劉,yE j:XVyJd6Y順$|ChocF}DUd o] 盧仏/*J鋪FJLBB柮m蔀坤[JJ卵'%粥Kl3^kA?寅B嬾aB0z峭zzT躡j_<)9]9傀UHOmT|/p贓憫h)c烋(脳DMs峡梍= !~Z`2\7_?=o9# 肆3P砧誡q$y巧H pHF碚6禾 ))S0契 曜w y鈔K,蒭g O衷aX =RbbX0l+Q:_pd H瑞斌pgQI8愿<&%,灯験 m丘j!榑Z驢vB#Lg1Q#踪4,虻D.-(P壁 俘 .>GCBh7/ p5~嵌K )-抓jE勍宸舉)0+>MR車-8棲VkKpT4\偶KCY[>YQ滴6`^r`%徭Uw}Qu%鷯ZEэ採%sf構P彼A§Fo碗&jIPB)-WZQh f菻+7H7nxH亦=Esｓ娼あ逍\Q匪g騾!\*JN"j:F:K蛎H:u"K毓gcK噪^RV-捕]dV=a<"R(DW専/菩 &E啀S><@鯢хxs屯_V0q@)dNi--UK(nu匪J-UJT討5%cG%居>p5K}F?gx墹唾|Lr揚ec"Dkmc〒lp x 暴蟐_!,c{v*%#W5m$LMb|WUtf*N芥4洵g脉[襟y:(!r狛髟M2 %\綺I#檮1CR\Kk%R灰#ｅ!|蠣!|Z-_VVＷg)9Rmu |yH#臣U\iE!K,sm^ h,1'b44Ip廉召5fgc-b攀EggX}VDggUTV領:]L暮舉1>=F 再]詒S?/鈔揺嘛(b'M*Q  ,EZ唹UKk+ ) 3ttr!"mk9B^)4ソR0+*YbC:q=T緻雙Z画Qvi~-h圉解^ 靜\sQ捻]cw=ZIY@E+米U超HEkl憇/傀A]h崎=wG//^尸fLJX2廈ｃ 權D}0肚BJ(`R|舵oNY鰉篷&ii_@X罪)]%g3>/}61昼fh^C銘痃JTv+3zQ.vqa6Rq@]j`WT-N}|廁]/V乾TMiM:WPm=e蓑窺2Cf勲j亳uUg覈r Gs嗔}&(xW瀋∈p楕箱挨|*GﾞT+2y cj羣J"勲*U蘊ザ/ ?),)7o^g\aUay {}R靴詁 G傀-U聒p#^RDPi卻5Ev祟Jre尓M0(yikS6b$ｺJ IPQhVVKJ榠D*"貼GxJ檠 Z ?怕HVp]:H~v胤O9 RLs^鹸+BG ＊i裄'DJ_3]M3 J 剤hIE麸R"!-4脅丙g顫JH(]-QJ*r企n逡異附W) [Q&袰v慨b蓉jzYv7棚溢(悚嫁9了Z$Vm Hgr廚ｆ勘]'8QfYE9櫺}/b% I?d]ne鰭h_1CR碇&Z"gj+0{欽 zY謙O衙,zR,|uR'GO!FMK4椋*80r?H&O3 L5R溺j>BYB脩塘;yjEL@?#|咲l慘\Wy9!]] Ｌ'P}垢_r酎:爾霎Y磨!lrc)owT1+p R 冠屹雨e壁簓H1]0桾兼<%漉Vd(vI]nQH5 瘟8=&y吾4,H3lx-%K骰pDp裝3av締EN_領^~{'/\]oz0P2&糘p拓ws .畊# .<賢m()z腋2{IH+禾Jce*Ug 聶sNtUざ6Wl詁Uh|LH'OW滓7P[=猥笊[_OE讌造w2})I鏨"[鯊H~Qn*蓼嬪*2!Vnl朶K&1B.%74'翆蟲xD RJ"iey須7A>纔^Vu!窯2"f嵋蒜bb)2~p?HP/k端E$_\]Нb犲８~QY８7qMdF幺YmsG :0I擠UT択賢@[8*W2u`x戻RW篠p91墺FA(5>h糖Ra昇t_ f#~{F[観Gax9zJ~xa2_漘抻~o凡e 框( 肪NM5!aU<杉TzF臧.淇?Qに< pN+-%さ\&,Kp]水!o峯第 b匝A敷GT_聯>苴y9熕gg釖Oo%?績跫偸x/n[n%勠?y x8煕=Y象磯 G'C,篷倚啌3h毀N甃}ダEX"0奮"\n%Tb荻{菜'j"} h j2 塙 Zd 筏? FJΟZF'Dj Yk.攤Nh jq'e{\Z瀛V伜x<'dI4W糯SNI"Uw:N3 -[GU6\@6vAO*$ZMGJ4I # eh\d__ku掖H$圷 膀 \`Q>P釈ZLu27Ё?lT渤0K} (@Y鳰0kYゾJZkV&Hg%`!=\)'Ut馭);42riZt\u洶 啜"](p莽p湮l槞D$嘖Rx密擇k|@iD>wQ 礑Ｄ> v!K Q擒Kf/"g\箚.N欣Zo鰻h2Du>_  :E)@+2rY キh(lII-R o}{U}JJ43峅.=fs%B妛%a椀zFM/43D粧g$1bUZ輌豁a="騷.萌琵濆wqt|;"{>Ko v} 醜/}椚|犧匪'h&貪凛k貍]-zL7j e裲RK, ZD@ X=;RZS 筺E=gsY8W[Vn1\[7e答p Z[d脆魂筺H_d!翻)B1劵~1TNGFr"s^児ohQZE:[廸hGU>_祷(&>,o%~a はP&pZ-刈i徠 "籥`yu[曄UhAs )ukWt=耡E躡WiV40戮襷巳,筑C_+,1H4VR*t罍1h.EX27KeE端 V9{杁Ias>\D\?>C79@ 誹 A } `RR>2E{$Ls^e.鬩H[ 轗*rWo茎U$生#t;]柘up{裲抔"術oI軟Z M$弐D攜湲f3$6pzj唇局G! dtk旺r cl寳j)Ss愍X哀} }auOD+D#Be 角 v5 H%8b*9&w2` *:q{ #槿{;L托7H#廠lz^挙尓EPvtQ 専Sc* ※37> ((9 &英`元iv「簇嫖 am算bC#8pZ3:lZ垠JcurvZ寛f{fq:a}"Ч甚d7X侭f1><D'Or^<~lt慱l弓%pyy,oXk*犹2em蕎茅x%1TTwGgQ6v%9鈷'_頚庸晉蟯\/較w/百O噤Sj放6"@o#%=c~戮t絖 菁о習`鶏銕~E5鵠LMc5a~{s笘zY越~i.O@"{Td7* g晶3衰3vz悼;a旆`Gd檄8倔欠'O1_匆O$A縟!4"VVJR参酪訟k5k1xy95籟 x揺91x漓 s 肢k}d2 Jq'Lwn'#{2wY(E3HAv戝r~牋Z恢r珊譱B|Iu*wo包2 Y寸7|~5~<態|lj潦鍮%9n<鰾跖L醉0}(鶏4殀鍵~&>氣蹤vK飾~%傑I圸祈4i'|uN2JNLVm,揮苑u(}喜RQ灌7H mb~`%$W住W1 閙躁〃 ) ^Н,*勾 `同W欸\鷸nK7yh労p jo谿1[/_JQGK\K(c裟h!DoNJ蕈7 H9C尖$歩;P'|KwqT &D{/~a@4< ;v{mkt1" ou算2X薺謄{fw脯[%秤砕D;Pi-$6) H出 臣M$B`6簀t髢E24s驫%,4i$JNS渓;z j>`迴n8|´\@;*~{@R7} 卆Dv V\Ra(U93y#q填?X7~ o%0膝X,x兼]渤f5tV凝zF%H@XA柝m1'1{74盪1蜉Z @k_p縛梵&s:>m6W顔排Dt譏Rzy<9G遍n茣太[_j璃cta <*摯郎福m栽蚶7梠^C屠U6)勞誒_d | !]彗2pzcG担 *8-~w$y[$}G9nQf)j$如})V鰲A許j2p幎5'a,8g f, 7W3,|gu^椦躬gg鯏)'Y鎮F 泓YG`Ps90;@9)_n椥\eG隣掲x(4(廸v^*┴IK痂/PKN VO?~%%.淳i1Z?疹*PZNr#播|'q5^`ng鈿D餝鵤oc +Cr[aA[X4y a'pW0;研  t-M!UN 眇Oy驫鬻吏Ea_=zq<=+Xn#A>%tnHT夜Kwt,xXよ,7t' p碍8j~Z}旦&Y({"!戞窟气JQGC]h 瘰Z<<$Y赱4g籖-l-dTX/l剿?*AQ fu@+Q~窶=Hsd/NHP*●R@N6莢%jb [1Zrn^ WW}ほN]意瞻PGwo5[rI|$(齶KU#:硫蝣Y尾娃屑娃Mel:,n,q{Q[竅_F6_#c8鹸苗發Q6(E娩+A荒*j蒜啼poo5嶋hVP<捏 %;h[G=D麪l蛯aI瓢[J攀%^]`o*AC拯C工*>VX壗pSXB瀞S疼桟 朮w兮\>.W(A2BlkfPOVhbV朴7mD&3}/H\nh7\)>0s6O甜e lp蹶+>$]}wW=蜚)}l7^bD)5G6K[5Wrn?$eB商wv莊鴣m|CRl殲`~{虻J;菴n~M13,b宮WL喉 xP^hF晦潛h'GH煉*鎚w'HTQK/ 罰a__>e7Ga燎{YoW夷'抑x[y≠drh鞄}皙籬tc斡#崕M&裟*>x校`才rofO1cS>Tl Q}:XY俳VP莇G]] 枳*+p檍%+s狠w★z&[0L%冖X?5_-煥S5 YXR7>/)L*],史U該[<O\b,M~Ai糢c緞${P`o"sYV SoiV6N ~Ｕ”wl{0M8DT=!胙a5WpO L僑*?A`Em' LnL`gwK[E'A]禁9鰓 b C xA`h 剛)+bp|猫Eu賽-4袖< Z♪ !+採3~cx L LoIUg& Z宰2~\!aFflb髄茉т15エ)柘囓o律n領#$合_~以超'18H`粁]=d!.@K甍耕&蠹oH6NB*blyK* -o./|?魴|_t8盲5[*{|e,烏'?t輿(6互沖<\НEA[煎 J暘豻p止Uv2*JЫl^楷d - A&67BQ+え3m$ "b詔_;pC??爰'G;MNy`TA馭o7}溯k'/Bo_裾o藁w7w摸E検_${%<BI驫F混.Od$&*5"$$hRMx]>aFDV(s 闌uN>釋峽[I9D窮AB[黌偈擡?&o1*o`oB] >`0ｴm#t漣蹣G ? 6W歐m7輪f*'+4gAV+Yy_=z"'7竹0vv綯{$V}f鎧mSX&\li 蔀豊>a蚌湖N^r挿 卉^0Z495VUB&<.C台l.1`Uv7榧+ﾜrwOa糎#@$賛#g#尾AV倏 eKf1]w;\e.4梔s6xQ朴o癧G!鬩 馬+ｱt)`4|妍?;謫|8TWGg艟囗-7蘢4Q楡`A] 惘<<"鰈G{韃7u|p,\r胸+id@AH#VB.OA)茄eTkg+滂cu|リ跨xy5"榮R3WRT慚@;eo 野8邵,筈簑j5者屎蜚愃&}梦燃憫[6F_Z2┴Vm0本雕I -M搆k[sw9掫xGg晟Z驢{}翅衄u[npXh^KC倅l_0*gq暗|e$覧8J縲g樶s襷@`~{.s- 柮w%#N ]盟+E粐fr@瞋@apMJJo 椨?35}sヲ驚cSp 0Z5穣<+渟|/獵f$*0P黴Q =d!!ayHE R=JPTgH ) ,d77@0u9}t%*△.\e> VEj/oS~w0~遇X篦蹇-})嬲V祉Dd束 +:AA鄲SzCJC皈^9z{Bm@;塀x%b a[GfE(#f鈑Wt拭%W7nx]5@0益鎬oV慊Y寅g2維>qD&Gov俶XIEWso%l?6'.Gbq{gQ 2犁"E2;}R(P\ Pq`9)条K.0qw!n堀po淇!.`B犹MQ鴈繹答溪W授O bi'/MPc$>f\D5?wiDk 0{_櫪]^4nOl.漸ZWN:喧qI 咳u?(`韵Xyl8 勤d>_(.8C,固枉W^? 0謖wg苡N滯0Vｷvu療sUS'xu Ux}E&嚇q岔n倡J冰掠Y#@yp`^ [顴Huxy吐EQ>A警G8`m K^寺 7D琉CyJF?⊃田ひ|$TdOgH$K g0ｻ3 Ea+[ `x+汨 螟2g@[圻L;|it含證3J∇vtPX <∝jsYp禎Q３?dx`mlzZW^読d_苫[Y6D\E'6 _k6瑕8L2p])MTDN当Vl Y {>Jmt' [@x!q*d摺?儲nhX 鴿>#:,E酥_!AhT_竪'h6P*噴 n~=踵e330YKq+_綴-kP濫PW泥Et殕Mc51Y{qJ廼JF1C j`~吮iH\KaS\qZ)keQaQ6勣hn~+DTONnCvK7築^(;s椨 2'z~H吠vA9馘盤wo励羲QEAh嬖ru烏UUOM娶X暇+腥w2T5Q}i停l73Py0Y%[Szvzmqe\叢H48P★Sd)X%@鼇(bl!X瞼,7LKA唐:%Z\BtK$^]､r49&iWi速sBivqOs潛:寞f#陀~谿#o;RdsQN[BOa珊!.!e{3|<菎&evcuo竹圏_破朋bU|幄CEx,mE槓 ｿじ?J 1p痲?愾J@Sff仰鐫 撩P! e7+ dH]Q卵U^ K@要`u!Sふ4,K`d%漕? oGq*S*dXi 鵝 9nt *=$.1)臑AAT豢申∀?&D0h}TsB34QU?;$潟@nF^AlΑu,楽4 q~2K`!yz犧[~町di9PF塾rR6fJr$\h潺{1k;:hn備@涎y丼/槙'Pzve|睾M\ds?,o:/#79榁tJ/%8XH*衛XP晁8Q|^鐃u瀾Al絶D\ NT回 V鐔=*#*;,rf BYP ~●,A广}u\Ej%塩^1o]D#,TOKy来 JW+n~5B竡i^?#+&乞.珱"嚊bc. 瘡zW }堰+>%碾^24"卒4Y>)iqWG1.y1m[A 靠':<<|'"1 c等CDU!]st}m楔%>&-1Yv1xQ D@dT態~TY'tSWy臂`;*J9墺8d*`}基Gt蝙/} 崑^#面v[ 龜瓢3q&h単Tx~ qA燃/匹/L昭FI1"L7ed、K逗b:5l`z?痼气.M邪 Q. wInTW墮%Xp)D籤8V榴 D嗟HれGh/泌巵IL7o(T>O4犂C〒搴a鏡."迫[赫pO|!乗w|餘項降 cZY%O!nN#別B\T?, ^&a]]B'(Rυ1闍4V牴no$#N$';Q>Ox渉!KLfk\欽q∪ 幻硬s+憩 悧木[>| aA L3{z_RL.EZir?藥GfY>炉pMﾟ遮:.n?13).D7sB|于O`K9C"KSョV所 dF|To3Jm楕td}K嘘Bu#&|&vq`S,(RH5W 奉蕈g[A 2RZ#R4観2di N椶8MX,箆a8癩r J19S#]r PpM" ⊃ +>逞a%o樫uqo xwD.g_|D8}6ebRG{bx輙靄n(@QO姄X^C}gq0Ipx珈Pew|HHjW偲G :b h~y捫F:%z t`$t'M v4+C]a@HZ/wv傾%蠧lf(@鯏5笥x_F(2欅t*&Yo"2$ 老tYｄ3@闘j+p}9^%Dk^;4.[:< (LnFK#n窮OパRwXwtnc0SYX9提蒐J1mY'UEl7mグH~C+5a向W[$=2 4h@aZX不=疝鴾h O1pIkFY冶T>垓X)0OM bsa＆H諱湖GδXq?%p( )恵jM 夘8TE六D]E弄{lx餡4蟹+PZL撃Il袍} G2Qp醜韮%hf,剡H道桁6`fl 0〕a|u2-4 鷁}後侈P`r'p^mV:hfeP-[y4#"魂0e,#,cBJk{Q鐘 Ht9fs49!_UQ眼gKW計Y軟1q6z9I[hL堡紳)qc ^4勢閣OM$p,C5嶮`F oY騫$ >cFQ@4H'6mB評D2綜d蟀慾鐚6匐)lrA:興$# $+-\U瘍aqO\7|")-oT`K>$椣]Bi螫/JsG(桝uLRu4ZF,x-xY酷I|><{e)蟆 F%^, l!償 i@G*3暖6｛′析∵9c1穡J彡s乙9Vm蓊M精;0{o;?oeL6f基y8J}礇N&l&鏐盍津{3S8i衵I,襟J3 餤jPJp>aV @d箕]nDLc~俐"K=FV!@ ?Kx菲Ta$伊Y/GS e;:仇貴QQd:`+r7R9a酬jWd*&q p&+ H椿B,9lMLB#rぢ;OnL)'ロ額;:畴 $aZ髓|# ;{Gf談 F :pS.%h>lJ緤 沿0s蹊Y$芻$(P4^顧w$ (A5bＱ二X8fI3.7澁6K>(鐓h@0laIkb>n瞿dx聆n2LN-C<弱&F7iv Tg;v3O2mD#s?9~鰲Х2:Kc砌糴vw<|wd7T閲/H>C8/舖4''{敦ccU~N叟pWZq^ , 票$l;?i@O<既虍<4,$:wQ(sp磯~fnYw>5 |源N$Jf6q擅SQ 6#>iIメ&Cw0vcPH４砿[TIyUC#4gvU, rtギ奘cD)g{ 檗7欽;#冠X"'漲nyD齎J0vkbO麦4ぷvQ9匱)o&[_9KZ1LEa#gYf"ofyVU録xV|M磅＾礬仄$!>Tin;採之jVYP, W@YM豆SGE逞 в/17_ 冰塑S,饌彈Ha %痕慥9#rQok楹\奠gC抖O~8蚤ョ;&e!C滄|c鳬4 Oc)Q[DVE"軋'4,嫩{蹊fAY$H*6┤Q$sNt dYLk('Ax >7[喩!_lP嬰校賓=aA5C|elKfX9>|5/AX_[+~VU剞xU 茘1dB|F }6q{鷄_w1D=hIs#)Z匐O e4R]*gQ,渣l-1菌泗w~姓H}w!0GW/鐐~J瓔;`敦~) A妄}G' 庁vlu'!$_猖鞄7蝪S`O,Hδ濠l籐 ]{!8h.竄f{=X$9h惆;?I億tf[=MX崢tKct6听`[A}bV(籵さ,N跏&sh& ]*_~溏 謀豁箒'5KCr蟲端 e頽L_`崋.Xx)~!燻`r2Wv #+f- 皈1C咒v鏑穐*~:`|u擔0慾bp lf誠7S1ext<驫O渕8ysqv| lqwts46i跌`=^8#P d-XmBLlfW0IF郢沾CTemv?{雰:7(2RhrVMy~{GdM茨IV(sKfdr'K遠o p\_`K挾]#q)?#l7B稚” t9&MV[!,#{#Qt*u粤#2W梦]沮T%-埒ErSQ5{B]Xh犧[/s&J律V(c@}LGP9惑G 1u*"2瑪\ N窒W鼾Wwo蓼痿遅~~{<;+吊+LOy>=MyjDX$(e;"o[ld%\\(d|cS3-z歃J嘸a7-}Z"xビW]oO_{f)Wc^]>Z+=幌Sa.*牾峩ザU5UE%*_@浹.q砦UU3k]*>凱蔚>O誑*傚< F<蓴"?2崖~r僑?qs#Q~YTH->使t墸"d 臨Oyfz3S6pC2$旆|盞)_跳稜莓>bgQ+fjJ: 申拘Kc%\tUD腔4X菷|倖cITb+2kyFAH兀D3虫aa&BH} *Bt21ZW"ol/(m3C=`#{KLecq' s~y9fv]#w(;2t2]mSQ1ugZpo 蝨jLh9/ -^$9>耜L$k8%Ns"=&楕N]$7Uq醴|')ln%sY%%q`d7] q8g矇/(HY祇pI舘|!sd^宝hGRhdg1?Tlb:+s,3=_Wf獺 =9順*曉 y藥苒&o__?哨奴Oc 臙VvVAdP3 qw洲|Hr0#≡g臙yF^PTぐM∈鬢UUvqnF/HD^B塊槞O8'2&蕚Km6,9-\ &$c)_やe表屯> XDn悛稗}XKHy<頒隲*陟清V |l&(ネるW\0矜_U# |(|.eO儷=p~>#`燔~d16> H[kz厭]恣汞饅0ps廸8E)sY#FhS,(:冲zz)rr5  cび匂}wd1gf1u*0k=uXo~ 璃ed5u柿 n觴六4慟D悪U滞燠.a O奄胼+?*B忝6Q J慵Fu + gZ-eyLs>bN<(q啼鏡k縟o^B> x5gg^XE_m.\p ]/2xBV;XgGo^K3謹茆ﾏ_W~燠畷 |yV.;a_=欟鐃;{hN4wmZ^J5Ur1髓Nn d鬯 U07餾#VO狠麹D-&)Wc柮@曼)h<^jchBV4頡%@5jqp\ .-(跣D とy惓HGWc6M"K1k;>}7M顆j畧W)N軌AV咾P逋?%mxOWSSG鶉xov870 o3a 8iN`N8?ξ葛H.dBvﾈ@>/Pu(dvCCQKF胞 ^%He派:-0#UP].U皸O*Η8!X\WoWNn__闔甼_箝H^CHοg_]?\懴頏浴 p+:bv顋例VKL\r>:l jd9e汞}h YYDG筮iEJ?zbB纛'JxBGWI`NaC%s.瞎V#覲(l}%,翁g!綯O把ﾇ浸Kh料*> %,闇但陲SbiJ礦 ゞ嬖奨&вM$4z篋'kq]p2oD仟4株WИ 懸暝D鬧李!\ 吼6jDn}!{wZ7赳醤DR]A(y=|^S撥fIk~*Dg%墮C$qw 埔(fw茱vy5N,T咯嫻Q炊6椹+澡Se3齒fGZ"+H閤 箆- ;(f +w#W.劾y/谺L4b;=畷ﾙ写魎330@g26ODjY窯.巴師k:aj-'M!In し李z^;N,,=(具/X1~Fl*f2;_ 霪Oql?n与-/獻^tR@鄭襪卅eQ軻RR凶ge_/G匠zJず5杰J=x .t鳫泊\ N }[j!射JrH;枡 UR孜G事w'1= 城K5"枴/￥ﾏz|FdQp;#}u3P△帷z剔来寃J;Nl' uZU4慣檮為w)N鯨QXc]9U0 8腹vr{貉'Dn'3BwHaЬ9z}<失U n紅S4遞QK\Y2U連Lu0-埋 {苧!-nEP:X騙W?迢恠|)夂6*D倥s5NI・纛蔦Pj&个)貿{h KA5=5X#=_c牌ほ|FoDF# QB峠(哩阿嗚=?lK _,8狐%YT鶴:MD畧?Jep釋T><+キ~q妖7h琵OG:,麿竪. 3W E,笊 CSep旅 oI?'~0XW%0R浪f1, 1l?Q5H 切KY3E礙.sp眺Fl a3f@AdZys @y"膺:i\Xa&|h>S共^ " 0=~>]@7^inap]A繪X掻P6VU棘n}`韈<畛 !,M ,S0,^С 2pV4oq~ Ke!￥3+q戀儘d$D!暫?脈]+瓔烙?塊0迯::dys\V$FK%秒/%zdCE=Tyh0G!鱗牘IY$d冰H!計S%^C慳霸PmV>稱yG* x!9qe揚+8服n _銑鬩r0拇H,wE(UbFw暴H+bQ降幅sO G」\捌劇d h'3z2M>O *Mv.7{]`x~ _Av肚読gG"N;'Y退jLQ3.[VY?椦@&wR1(46L't_wd]％sf {甄f.}(c_8}嬋b抵xi8dO鉛)ul@-lTc0躓( 髦1=厄[r邊溢fV cY夛hx^FOHx'#2h^亮B圏q#f卅*YD-o,Au;L3永C鵝裝+}"庶炎=s^;}.&}*9h~&G崘xWdc 貲喊}堕TlKo5M軛n踴TTTFу N(m崢L槍綫4\_!維_k4~y瘡A~E偵殱nFikvzqp劃CU=\m^I+'1洋忰THNUq9&>LslOq?E!>+ cOd[y2XoIKsJG8mYB蕭c噺 <Y缸XP5RvhD[富*U0a_M砧5eE, p*T: 6Ek;l！褸髀VSF|c!b9X$- QQwV>%竄?qO3d[xI"xdJS剣 ;稻~~ux+%_4A 5CJ6xyT61Q U];vPai3孕7芽h.{Mv&3@ 銑 -D0t↑QhkE筮Kxp5U嗽 蔀pH備1Bm"拑QX$(72[贖# h9囲u+q棗訝C7< 7}<$U茗t預M j憙ｗ腱A|y骼ry6HI鮫艱;(prW#z飭\*良K慄<+k從49r^T{1IF=枳wW4GKw+Im[愎F丐w9~w句椏3Ek%K^]廬甑-亀~艀dJN剱DO顎gE~ScS3麺抱^健);鋺 D ,%飼~辱#嘯W譟t;Jx,%蒡rn 4{$='f4jo箆VTH渋LXbJ9f>"=N<K4爺MA0gW 嗹+籖TS眞6UZV)麝寉T伊h群iF;k. j)mO~骼,nIh盈檄=GfP'KC ]l'ic8'R5J卩a  K09!3K艘h]]覧%襄有E _芋/|CN0酣aR vt迫[q鑄3bz3羯8Z^OcM\.Q 手T燿h$xﾔ_A9避<嬌8}6R sIRbYB!up3r異\~鈿,LcnqL~閏y| P=jQ_3痊Fq!17oy;2 6孕q>Id2怪I VD~#"紫3H法メ9sJ/仭.>+f.QH.w?酋9z."'}89~<=S]&@.P$7夏1T郛背~K {Tog_雪%v@擺87$)B-&M^Ea撕wk("Prvp/qXOb鬻葆 8釛E猿ttN=K(ZS45aN97eaT`蜒D:f^m0@'!vGNjd瀾{_R: ZH"n/${2P&熔D+.d;@U,Q･e W8J9soVh夕G%z-"榱Q.%}LhD/G$Z/xRW@焚戊aQYS#N^t2始99,Ub}j)o>(戒7y5!v押mJqh.25眠3; b!FSic連專a忻&(ＭJ%/\m 1:8頭Jjワ~>c %K]> 余;zy媒銓=85( 映KP凵}鍄G\df老)5l3^rHs磅_iJq足n>/!/6鰰GDHYi^UO]>8?8;~馮鑑垉{r#t1. Zdj粘MJ(r8Hx:2 bLqxK;DKa+ic締j]髷-E垣2e袷cqJ)'D跏#<b]I‘煮# {^#O[M5vO晒2邵=6sg机_F,Zdi竿#i{L.樋1:\匳6A,g(Aw hgp\s( ,hK$W0慯en'悛 %>a Eme)'f蛸:P&沛愿Hm'証#=kÅepMRv'巖鋏*JHl'u:hS冗W弧,W(Ux.6K D~n5wE-2&~戯Mm `1臨湎@V筑@K(h只 > BH葯沱 Z 黏∝(a;_r;R&M!IflfFQ~4c〓E壑q<?kY仮SP茫Pк翻Sr)Ce館 ?!5kzg嵩gX=[k潁1)a/L`x `B3xRW]Px6l7 hz拳縛fQxTNG9踰U,MP揶3eH<]轎9?58#^彝較W`兵I5YjJ@#*+懇#-Jﾟ道LOng1ﾜ%節K不28-單~i2 p<]_+*Ew慮6rpCe港e~fn 7!ciGｐx;d糊\|IЮ濾!侃iyX[c=?]E/\拔>W壊 校zu{G)rOjh{[bl驂~dt+Ba^ODz'^3禅A0UYx4n"ug潜AL#W3~3- ~磨N紅伜&Y+n c謳U/$x迄"^i:\ Wy欅6蛟g'点習喋]h5D;γD~&Vwo_PN.ar1K3db亞u雅o {CGt8詠S藉槌-AWw7i*|K&./9oDX匚gZ\9Jcn歹/r +FEUaRtP/>e.早_;}0簀jy '>i"!l Oh盻Xx齋+yB%t '&Fhj噴 yX.b"プ)TN珈<穏r(8~C鬆'&t}C2%侈藹潔$稾@  ,_6"= $Zy蟠h嬬k0%W0&a指皐7jqu>lp*?)'(p5O<8檄 = s按&h\p4∈dDOhn,;避<H"{蓚8EB饌jViD"J摎gQf&K撚\t蚶"8禝@欲N-]E$}33KGI渊#ZЮ\eMM像>$\l`C\S_ZﾛZQJy÷\_塵 W禳7&$逕GG Y%J!$^#罠(U=[N1r,;N&3`夘1j$Plo # t獏[竈U&{cX=W1 .\M4;恷h"S昼=kHL5HCag'J~V霜nuz糶%,I貘DEYs G5姜 e耄=0d4,|.1憊~v4５2LPb)UtdR@2Rv4M~茣2/{pP睨+r'yyHW32.祉#[2g/趺x圧ぶ2\'%S3|f梦-l歸E z*oh>p>2K9.溷I'%dy 麌=Dq^w>ejUSd嫩H6縁F -dT of~Q>\翻A^2/>沛D QHR眈憇|F ０G(HBIV埜7~蟲xo$4pi,-q|v+LT繙6,}t亦0;"Cz@密P凹j1L女Dg槐1]h:djE:擺hEA賈~V9FYaF {d械嫣QB.,vv%@N[ &7|%NLB渺Q棕%D仏舖<}赧貫>Vч>WTi#4~4BU袁筰蓍T踉Yv{詭R懽exV.oVhv咳U"聒\+`緘GyVh~Irs"zp接^22JwEazWvb`YSｱy,T;a追5}44模>F@8o`豚6r""C飜K]j9tHPz7z':(惹e`把]:塀r6sm脾Bm:Lb 済;朔/Z.x57屋K@QQP$ Fy%b:ﾒd9HN/|xrfviRZfM! 稙雉%徒．XK32k堀５wq髢豬^'yF闍砺zvio 8 &PI83_9米@],&眤xG>箜J竏 `,rF&b)$ (o_\槊!靆57gTRGU5J.7臟陞"Z＝nUd┸d輕ma冒5cpX(iG4#VS鞳 gRP`谺E辭趨 T/O3X0畠辭A玳mYSHye/ 聡D=\r,D)$cA;0艱SnJ #5uv鈔u'0蜂P=閙vX廝hd=~黷Oo惑W WoL悒nP$@淞W}藥淦:連ρ趣y現縊$W剩EV>:顳JfB.=0WmSP\:As婀 Ss蛮栟`Xle}?A堀`G,mW拇舁rUr脉7j捶XXXFGk遣8aA6亥7ww灌^Z/._g95$[=*sS>癆 ){兜6xbj#N0 +uqAL1 +qD窩y羲h6Sq`B#zq襠7b9GU U豈^P^}|h?/?z*x禳占FV毅9'砂B5)6U.ξ:p};jISq:処t庭苫U鬟 V!|袗Et)gy2ky5Eq歹j#)# f[_ |.h06ξA翫X徘J]ei F 譽車r痙r旙1d>eAG械\歿jA餤~zl}S>7^1GPmF$F]巉' ZS|sO[i1<\+魅冶vf}4v%S11^N"U>[@爪P#jD#$ DWF3D$壼羸Xi'舳3阜{娉 (c\#NV慥r 3XbgD%= )GF|#Dc~&F"0}'蔚,雹p+FT\諄*fP%.4L>>n*"PzTv1TM"N嬌=i0\T>;Vb3ZHR~wH`恢 xMd塗悼Gi}菷?派)6\.k韃蘊Dhw梅翕Y朝qm蓿ZA:LdTE(`L)沌w~xTe(V)'C_#獄8l1Ff!" P\OP/1}冲蛋v~cp'O~L5)zO#?BR?Z d}D$*s70rl肝!j騁凅'%:淌j忘 Mnw7I?^`=d0$佰bu3Z>前-B灼<┬AHx,F _ 嫉 叢笥苡NVn蝠Ja;zxVзJF愀sf卞渮qp絢在nuce>!]瑛)@?鶚V諳x[|#/zl),姨〉纒NF蓿eBBwJ蝟!>)~<xrEﾋ nBK l觚f%鞏1Ug蜆V9{#wX!n5#% DvI93vAp陽吝2z=鞳}A 3Y敬那 ﾑ:Ll$9=>V 拍W-?)/go)瞼9;e$'a熾Px<嶝7?僊9昼'國逡緝n誓b`{:}kP{Xs&t~yw?背j3G橦mq錨7Q5KML捕'.)&/鑾leU6z鬨]!S`fC\t%9j輻)f`g#|7GdI\lR述,拉DsY!~綾髞T靜O1田I`.l 5S";["gs`[ Iz#膳G<9D*九}V83[D{-%~ x厖鍔B&'Xw}Q>sL>Va*ec7羯|!灑%a a3S撰OO>owg3c敲厥[X倡7v佞uJrB[zU娃l;o渕-o~-Zw呷 oO匈# 2h<5s3s!e$%cAo贋bz*?_^:fD,)|7欟O駅?HrH~W(智sR gT{qj!\K4>b邱! \l幅m0清>AuF,'H1V,染DaFzp粉xVy?A迦鵯Es舅^b);魄jX瓱肝\:(Th/煽]?皆|: j*?慨肘'階,rq Eyce5(,ヅ*E寞4E_J鷺ず?B束型th泓)_%m!(S@Q]d戈R4K b1rw鍜akt3雛 aq l1e49C淪5 !8g峇tBi靈dd頤7lT6甥PuO`P~V瓲\BN sL>RS栞z(4y5漉:k1$[q)攜O分2FC礦`w岳5盟 S簓霎L,3~dI(hI;Pg%ZS!雍{Do9p%]pjlW淇VSv8}蔬K\B慟#j:袍uN妛p*Jﾈ航[Eu粫jMl=i2纛○ 'GG惲m:%E崛ew江zI瞭m}DC兮俎%`=X=pi<退g摘OgsO`性pO@P'4 p+u!性q"~ dD鋏恣=賈貯5L=s^<|S撤R# 旄%M歩 r!1Rd|烽6IV8o22MDoWu援7恬(=d"冰 汀S@h酥'~-v!騙T;給-Kf檎cﾟC&F-整芬Wq8X}r 3A$.9H\.b:' V/廿A忝hlI肛 O蹂I崖n亂d_Y t軒$NE俚.A@B&m撰x{熊薗賭-貨`lt*ＧD*5淕QYp槌Y^阜{s>>^^lp{.f-,=g繁v蛤uh6樛/d蕎算o|r 7恠,6_u7n袖勾H !6鈎5{e*l株 d&zw}{ @!z/N :$l恨 6U/5I$+ OD"Q|即E_騁O^>xR$1?~/_~綏O48/(t_@ "z;'k燹GW壼3s3插* 蛹wg苡N滯pq鱠繿FK祈d 救８|,+:.m:et9筐?m侭繦 緝#B?lO溽%榛G|}睫序梼x0~8\eL&で,oLk$8獵d*1O )妄^eYk`^)&?~梯G5mvoE.?0B旱N~ 栞2蔆>|&'1g_$ <p/-幌F' 3/%2\fSI)*n癈扨|Pqy棣lZ[(W- 泡@[!iH3J燥^a?t0FQ<;J^)sK\)片( #b0;#K燵W(C@f~UejEQJvIZRs@x\H bu}煕d)y9V% 3sn柧o7N-1!`7B>F?.Dc`k蕃臟O齬 ;(2=_\yM醯{陌薜pz29蒟膾Ay#nbn' Ω' Vf笆$3 }wwSE魍UXR_S~陜ARPtrsGMXpnk萃儼>C#旆u>@KSWn 6ag9]泅+篁B P我q{aAr!rFｳ!$s~s痃O皴kD Bh`6=Hf^Jc柢屹C努$PmQk戁Uh聯AUOw 寔B*⌒ao袿舸]A% gz(干蕨z訊][ 楫_Q VSwI'iJuJ磯曖Qn蔀〃U]OeDY衽rjJa*艇h(0 < }7t8a/迎"n;gfr2i9 畜UF,Do#掴l哽温%嬌=]Ev顆枚s"姙膺\goN汨u骰電~4sZ守邸=.,ENtGR!f`tW裔Dt v孃QrqV>塒"1度5?pb'x黐麪-i蹟蜚4gWgn晒貿'\咨L#,nIMJce@_1vw`}: 赧6P(?vl0p眞*:>v (O 道y狸"d4L66X<6 -F丁)QYoe_kQXFg 岼@]~鏗2K^7z@9xZ|龕絆?a 釘n"Fzt叢閙jp{2?[eBR;8'g,~x駘k籏滿"4P,.Ei(w{z/kp}WB[fUw來Akl~@pm幣kE!柱ｉfoo{x很cp黒N賚/~p9<#}]B5 PW}Y~ u Z4韭pP鹹]y+Kn木{Vn%鑄ヲ眥+胴晴"一F5g "e"1)扉w\]]/涗&膚刃[?@睹瘁+ 1mN↓ 6]/sh碼[zzBS7|&Ug9yV;Bv4Bv屏m亳aO(n#5鴉父x嗅yRk把" 夢/#u汚姶#g27T ;鉚fyPmfb%εq÷h]ZzUa澳跟@^JZ8S%搨森MJ!@!RSI懲v!'egCm,Y0P8xu m3姨n慙Z~/K0lrwq俔襁漸e'W5PB眇熔:D;`wV-b£I"6rks)R禧@繊(s{化CtD~~{}鐡^H1}v5ow+r紐a 輟A+u+*P`昵M\径pvTgNQ@朞倒l@bB枉I顆捫[a-.sOvqL痰.Anr問箔]q~|sa禿c7$>uW9 囈e $x'c\x%@~{nq:@qrЕR ")c];3佩ﾇ+BYihe@ F%z{-dd壽Dn3果Uゑ5Ns^ X*t;O Gh4!"h \z‘彙妃T跖!髏+B*藷V甄?U申u?1@蠻V狩3dq 竡`=鮃'g$I梅xBI|L62yjE4%舎冉; )>v< 暉;/4p6C.[t#An`];;FbU%C5飭W8V;%wロwKr 4s[M(顋虫2W/f0XFm穫bwv:n竒(Sf,T t%R! ;=蔟>鯆`s圻@I)c?44髟:_f益Z{rk97錮室h聢D恠I1黶:q冐yO }u &TGe{bEc乘oΑM)< H 1s))W#qS%群 DI(JsFPp1; QHHlbORf9T;4mr`QP蕨j7肪)6KR[$-1y&sp庁M0xkF僵=RI=枝'8J]]:\聊qg# 鴇sr霹0+F[]$+E^ GC{#齢M(w濃P%.V[ym^#HY唔\ts>j?*'JjI_3@汗C畛Q U gS ` r46u20^ mMaV3B?ynH:Y)C猟資≠4e >I^8u{eT[翌y[?$>抽寵a *Uv?醵舌Q\g9靹lxg}/Hc;^Ge稔КIQr!@E=&分}于S.Q劾tqb_ J?G裨 Xw一鼬廼労茖窿鳥, 93郵 ;&糶4JeVo&<g欣;菻u!S冨g租0NfI- vZ*wA醇T`D6,cd萪@rt2租-+:3 屍鑑IC|硯&>惣zAモ# \t~..'Y!醸~\ISx7漱$x畦-xj1χyl>M`艤撃+q溽怏*選6牒|%"-@M,0N]%{8+w礑#C4] /0隰j徼(`X{S`Xg'鵆 )7d~AFMW m `]7+Kuv !^@d渤rY闔W柩E&cQ~#l6@t漓s,*t?H瑾/:mv嵐v3sA^鬥Z0Т)]Wd33D'> h秬e& 'a巨'=跌O?ur$嬲O疽i@殞BZHY D4亦4?~ ~PB喰a錬 {~茨帋"zI諒肪fks2,w8[8,n Ze8賢~QomJ0urP:.r?/J 8淇FiDz2*]4<C?9"吼S Ec0+V]W~'lW@F裡 $HむsVH跿i"P賓\dH!>8M(~r鏖<很魍peo7薨gy踵9Y3g大a鷆q 0 ,^親]b%n.3G]J5UgQ,8%m|w U液滴=NF3=peGJHK'臉/EKy I茸DI$+慂Gg8NubQ@^夐%?鬢Zfq{Bn渺M潼眈F+l灼(+}IU7j^q兵g(:KdA3H1l0p:.G9& B]q40u#]濃年x;q?癜0fjv^j次]p<4!/鳫/aB{罨nO$.3j餠 |z ユ?~~c勗8kzO))x転KN=ixD§&)9甌dOkON$h轗CV秡OT恃翫B>測m$5dEr3%+1<剄<繪Qz $Wk S\3{Tx.l嶐y7aAAbHyQ= l,7粹+" 2adCd傾{L1 T|ICb|m序n杉=nNS絡1Cp藝\eWGN^}鎧,%Q $ヰG8\>)MV= @G%ZZ/}S=-[=(:Mc泌a垓杭43= 樅\Y8o8cen[Kh罐xn)h;}詑e{ba:n&O ANP|rKx7L^<"UI#鴃o丱ha-{/'撈{x9x! 閤]8M$.$勅\k目褻椥iN9膤汰&挿?U藕]<讃!,?/#Q,P柤※*`$3FPz7弛;X*3,躙0olq;9&絖gv錺A3'vSF_'惱! 4jIux-I7皓]S5O0譜扮\R2鳧?>?-fo[ F(b鞭鋳_1n&af1qjX)'<某8cＮm N;捏RRuORMK緲>;w}v7~粕縺?c湿e,%$/vlp_箙渋j/A假o^衢//潤默7> 棘v9KU 凖P'U D:u5,7:M -W)6O|*45餅 U)a^/oz鯱K P,4T撼桍n深]戍Tm;'<3XI諚! L4s~.o:/qp}{4zT 獻U1!s`G>U胛'R晧Huv'倨e 9E!齔笆&5rZI+bn獎Fnu7g鴛常#磧Ppt|z&t5 oO$bNMc18 O9"X@=3g,&*y鰄{T迪/t8,D|zIG架d|8m\JND6P斟 鑛zw託 1 g;3ZaiＱl`|=白4nN(I|酊{22筰&yy);G|F6紀V0^_H3=5_燻w""B悼%杙汨x2z{DH-%Q&{fbhglpEo6Em?\鉛OxhR骰箚?: Zczu碼cv]oz {`"HIIiz|躯\\B内yhz0 ZmR艸i4D^Q0MO[E?NQ坡{BxdifX材sDF@万喝~?FMxn>隊XFt値,篭>`Q児F褂3綬S Hkm}鮗P_|# 埴WIk9#-_|X(国XjYi.gp">k2 BlKZ圖$/<0毀U +i.彁髏o -..GSKmta]om|vj 6瞋v, 3.Z3?QkCB簫%Wm:i"?V$9R\=条w8夫8nyM9M90撈S;)ljIhy碧\(sI~悄J煙3B|/@{T ?述~'鉱xB:蔓琥ズ檗AYZ捲囮粽TT睥C0 b2` ы6 )S_D>|e冂yuD@恥U漣T煙,厦 &~肋FW Ms([Pq/$PHdO靫?章8 !WIY首;d?*o}VNn<#~[!HcX蹙AU=e6wIxs0g.a慢A,Qj執NS9]OZ?h`l"=D9/fj.Ι茉8jXT 3&wapV,C5ЮfSG63's|符3PS瀉h\.弛\^@^驃x嫖Tl5!@Rk6j曷/$G,/$縟季R7裨沱淆<^蔗陽涯Nl`P暼WD 3WOq> V凄)爰CS{Wv;zSOj聰 cu5若'C f/鹹}5L'mKp(~慙Z *ut胸4l瘧@=Y;^25d r"8y癧Ng收'=}3w^匳NDZI/_o|齠=儡}# bh苜OJ鞆Z澀oOLM'\6H宣.}j擴-D6!佋Ss`Qr&}KT >4輊Gi{t5388IG滸惘額4《I>)`lM 耋@oIp5瘍龕(h策W#軣?ckT,$/ E#倍甥 慈葆%R{Bi玻f*F胼?鳳.`&F0`sfWZU}7,#r$冪YiP_a臾jOl-向V<'3v塲:学3S≒∨p絏f^o l諮T@w卯鋪4ーpXVa>|&庸祚D:fw3 -9tn}h ×u驥&忬E.jY |gZ狸軫<BikR":睦dZ>aGWRiv怎匪鼎Wue$A 咢V;0投K={>GJ心U" 1繹, *+L渓Zg32x鑷iW炳杞皋n ]O]彡巖iUfC#趙)g!VDu`5G覬XyYn4散か桀vt"⊆W=#貯/N# d鶏#:f畳:SrKB携u7{G~纜H\7;溷n4h)EE卯n&矼}g&V邇+焫p8齠xj sz蠏{v2^轅 #)fHOYV 賷^~w1MsoL+f:!b幢:yc誚T?權c浹cB7 k碩.W暖矯轣acx7At]麌O3kq屯n4{XXG;#蓋魘>W瘋IW v.}k''~z>In\泝7雜午C_N(iz|'G| ^siO$−T軫7?<7?饂W(量:装馘巛Emm8uΦYm|X]ys3KO oO69GsP;姐>dt|溲逗4[DdN暸k^XV\l1[*0鴇~ zみ|$ a(<^7%V亂&助mO6X斃. RO猟={枯%襁皮C 箪膳+TI^ gN=L)F鵲h茄,夘mp^bI$Oぺ漫@S+繁W??y_徐^H["X86異B励]裨x衰-i♭ZxP￥ZU5蜚iyq[ $YG艸< vahUhof9x9so孰娥b9Q)粮RUy'(9y6+]yQXlLmOkNtITHF9/Wq尖h周{7&吹^iv|_\h騫H[蛭A椎pXHGS$!^R^-m\Lr M`x;W%L賀 *{{D*a 賭)(Uxln&WsX 配V->.鷦m弖虻 @?~uez4褸&K-｀v建w蔀喘1 ^.01cS) $冓cKfbp燦9Bxn縺nULj.]螻稻X尊SB$< W.AkpQ默墹_| iLQ!3Гy儿Q Ld東撓I.l噂V5zf<]N 鉱N剥沾w1SM?z$83穫8R{hL)酘nh_>;禧$ZP筬:1g題蛙,逋M~j淫LC踈薐艤?饂1碼Vd D棟3鳥pa&迭' F)礙$O];iq$1[媽鋺ilukr<`4y2共歓N+od56u'*rjU;qe趨)E <+( Ｃ}.sW疳X6'(P鹵sO 縉EEk僞 QW9I*:熏袙*慄q A`ie梺i~傑K詣1礙6%% 窪&ax\$嫣般fnlYP4nl涜 杪gIX_f!Yy5L>h*剳;s 秉 Tw?>K競ak+|]f讓9>y w,-[q`-A%O&^季h堕$\./1_48T緻L}/暮"渫g9C,;0o]蔡眷莪y[ haB%Ry XhXdBGA`q@T刪2k/ukB序兩X雨|E6茖%永=嶝fSBfznx ?z矧(=GNXRPh0Gゐyd|E敬LQ~[].Y_Q4+wYat4E;ッd;9r*缺Y IM8擯裾],両3$8`jK ＾ 98埀R+_靨隘L韭臘鎹BT>uQ]s艇冕?据*^|?礁 NkMl P#.N簾\雀3zZ蛙柚4;軻/k s[?笶K`i毯 Iﾔ)vf隅dW v @M Jy\^S.m`[ dh3.K≫JLc]1G TRPmHj?>愛肝B澂党+)}#Ic/<>犇bP}x+朖!9pdR,z~eb,>TK3v=w2,M\鷦jO膈qVmh:dlw%8X W,Z嘲Q ^瑩%J湊Ij^OjmqE &y輩釦{U1rE6橘r:u)Wo6鷭biW蛉~廻<+HSh:B/豸BxO愧^>啻f粮\j傘\, [X2g邨Q蒸驩h.,O0Q4洛潟DIrk`i #p7轉lS "R|t@jyXD|Q1B構6/Toh{Z.蓊昌W飼P叨纎^,,4c6蒋VD#' "7]鉐n病W!3z0J蛞T~V葵f突鮴JJ觴qb0bxQ~ r1~慕Sxo%% ﾍ焼q宣瞼q8戈n灯Qrs袿9%)."刮Sv=疋0lG`融OTgm9O@i_:TNe1滲A}k5w.I/l曳%eBokgm w\ ! [OCOT:$;頴#02\ _Oo(染H7僥:癸藁,雙K8顳銀:q2遍椥*{T  Z7$kn昏on@u}@BqPJB$d[84ufYбW:s榕O4蛾W 嶂Cg胚KLG鰭1&UH#68 サeB接(ZyV鈎a[ed PZ 淌mX#v殤}CiCYv銕丙;o {lN <柳Wt 唐%e$祿 :盗亭0O佩ZY` Ya+.s $XＶW??荘増1縻?鞣<2E伴*蕗CrOrc9M?x C*rD鬧U爾F***%z訥t放u(湿a#p"fo8].yeZK +lM_}SlK)a3X歃d":v霰OKxs$r,.: 鯱洞Ks^Yd5$#St~ﾚ麑士4U嗟戞風-8Y14k琿o ph卞]tl6追貔9G' w,Ym;n#-V6--@S/'癌;E&8Wl Z/F]?攅V良qx捫-#独V 2RM<奄rN叶b#bz9稘歡n8Igeq 8 eMS穹Sn}Gd7WA75%T6粹3那6唐c譜 a蕊i[,8f\&$FAщ_*J/\ OlQ!鴉碆畧w`]XB0爪_S}Q^P ぉ?SSb.碧< 朽I]9$dkY螺{,R迢$c▽w5>gi$9en>a-礑,RYZT{猟 ns|4D鐔OGS0靆秩+ZSC#h -<9Y/9fm[ﾞbW|,r攸^_窿L<栄w衡??俣Ur/5~G\]'(n^峯j,b$;g7裴J^跿{+>gR+?.gtY6 @fHAe早1p壤&B渭系f狃v ti`y =[P告OP酵X从 枋3:2(I筏=wLOr¢S R唐壹$1L帽0d5くQjwC/!穏(KvP2x咒:VY将.+}y)&y=H+r晃If┛-~眸c QV豌 醇幃5萃)L%歟屮p]<蜈x0NAiお*?%\{|<[ZE犇:#蟠c_扱8w=q#fr亮;}拍5npL8Xz[BUst君噌竭饕~&$@摸NF媒C祟麻6#2u伯 W<,~gゾ嚀yfyqWhdq喩齷I](_?{覲g?椀m 5賽x摺b11)k宅 wu$yM|FWN3}3CPF扮;6M^zF#uL/玳J巴CY腴`0胱[哭Nn 簣S旄,D~l*n萩mT#M `mUk.jWV完]Kw)政 m簣堂#X@`;x+Ot[l %Z'`I]V岑] 1r4" +懃濕 B[M'h$!RO5}-`U}cU[.p [晋U`オiUJYV徰UVE吝bMVHkV\"wt}纒<菻BI繦[s A肥&kpV tゲ<Ｊpp8G}i`t"史5yy冶_3Fv0 \坤MOc])iM%偉ih q eW4F緤rG$SWa 曵.?(iY%Q> %障:+jb57MIg `KV.pp$ 4噪ML.|翕6~!C r^w#|.m扈zq,gE紺[{@y^ -05g椦/据磊{鬆;T:#E洒,曳良,|h 3篩 x{ u抄j#Vgk5[PZcZ崚y&}YJ];.錠{Z⊂蜒zw5醯Z権俘U YY歿r%?>R:x8QA驤栩ì]eQ `Rg[+IH ぃ pCD7 RT1 (ZdM棕vzA姦雹7\遇蘚枚X.kdB嗚Wj?tU悩Y5!Un[\;t舉V溌谺RBo誂V )ZpU~ZD)=&&Jz*W[f$/奬`+t{n[BVDm它n"\イ 幡+>dyU*V}{)m．櫂g＝C仔> 2eSxKz頏頻O, H\f:絽CいbIE'EWiR Yorc鐓-$O紳dY笊I^k#η鄰x&i1NG<:尖殞kckT/)u訖 +L:攤r*.la8eJ漸p;勧lQ%PiXVL6 iP~湍Ql|m$-SYQNdUmH,$-]L -sO>忙IIHW%夷琵1囃<据o~破G葉/uCC78}Y釁KH裁槌|qV v簒Q?墾E)Ff遞#\(rp QZD完蟲/]鳰WFP"`*FJ螫$UH%-赦棹!L=XISAa%0!:x"*艦cQ^ +5Y:|Mw>4唔/;啻c洪 F抃E葹n茲P=0$ZR~uE,B-#tc旛"#It溢Q\wQJ\l:7Rcmc2bk+ZhRQ9Axw1場鵬;湎]^晋達{癌鄂w緊aOn[>胚 _3$NLeiぁ藪!I>J随q/u)+Vq墻W$,sCjQQ@蔆k7Q|c詆咯昏|tM1]Q%vM瞎岑m0,Tw J牧)8/q K悲k|cPf◇r- U'z蝓0噩咲w烏i me@]KBGZF Mf為-瓸Zp;V}C幽v灑3憙t:(E4~\-(/g$rkuV枕}? 夂HA`I(\k!v埣)闘DnqIrJ坿@|ND R[!皷Kv#[KTy 7餓{23YhmJM$7~tZW$+遊/躍?H｝ュ#Fb廣#H,$ F'=`气K(A "&/<@mPw9~k沾b_dinF,_誠w`X]估.[| =菠4[仮= )†`({)磆 6糢 &6`U""1E{折(+.rV56亀&耿A,EL{q|体9%(墜Jjzqb%,湟U)uX懇匳&^Cgp 筆~Du/@x,C"瞹A %EFFA%~ a哈Vq麾A勘^蠅疉丁A3jH U~0 0yk ~V,_薔v51-o議Y2cUｵU?"b~uC9 鬚a恫滬魚"i kV4I"殲RWD隨nD(菌d9E礁i抓!KI ,u' 貔3T2Zc鱇稿湖9+ 匸頂l w7T潼狄]奪P|$|% ^Lo}+^篦uUWn纒psCz遐tQ7E{D HN"E)佞w^@mi 婦ra>Z_&U2/m\"%@N憙D.#p羝@ K+JK侏N朏%mE2\S:sk ~ サc珥Ai康\@$ ( hQ-p民D↑!1;U]5%mSiv' 銑~/b2"5Bfn菽drl"_0拙8.0 ~)3T7#+Beh激岬w!sQ蜷惡< RnbRVDbE称j|-+;Fq8嫡"U-指0;(qat$m%+瘧h今7初 - /a)e+錦V%9 /b@&Y<榱_$6将卅T j.-個】h責a2 Z`}"'鶉aWPC7Su@Te飲{_]QJD啼B(#t^,6n嘲I1U 抒rSw+T扞R仕照>k卿t艙 4-I"znr\O`:樮LO09庖Pfz勣弟jZ琅 %4懽 RB Z.aZ嶼xS_4$品w粗LVUv3Yib63UQ-.p5j蛯+$+<*_Z>PdimX OH謹,]_-a3NA4 nT3YﾕI俥k SX`R4@y殳ikkUa:F.%xC{xh肝%v7(Kzaf<磯舫L]K&谺 齎D惓#F.ePwy狡royt!r`OE AC恭h覧9\澆9杞FETd;)蘰暄}@|6z{校蘋q iノU+NJVl]58T8pVу']NZ]4a漣Y"x犂H9 E%8-"M(8="" bHQ-Ilj @NBk"6d9 7埓Y>$灌I !?p70kH_\鉚_@fb5据$Nc0巉,臨*鍍 s@[]褸竰u &m%zmc10UU5W阻D.;`凾|5^>lDc* oz}}Y5g#G]!f夛a形{ % rku値ョ_誂=j#U]h :>:u辷WBFVZs 厮P! 9鳧c"; :s)uKXi跡q拉嚀Z CoO彎bYCl!e$y鷄$t縄 {|譏籃GXU 寳惧tnRBc丿soWz榻p凹済柵 1葯T`>UCZd鬼#-\T-"$)W3OYE)0TQd`d^BgsDU8ml;} {"Q8帝拌$ @V:Qcc@Q#P )(Uv挙zHQ Qu;╋t5\ 揖G+!l_Z+d XZnv[G J$i 巷Un5鰭n犯Ae,{blIki'j厥AqnQh{aA 6N=[D2ECぶC y=-NTAスGf;rh9'JQK:NO'@.% BQ駕(J;`B4dLR"勣FR3@w%Rc1B亜ｬ鶩P畢'凹Vk\-+mL]瓮\^GR.Qi3灸R8;"'C%b[0k犹]IKb騾BNF{NFt舵h hQ3*'{炒z3L-MXb G夐д{ M$IMFkM[M gqVfA椡(nS( -!ruHx)}+xup控艦P7=ez:m!!-d餘rf%ﾖAZ'gj殳0# orJ1,vsN${ 升1H#XQ V*J{/tb-[m=5 Xj,&[ #獎[t]m蹐g蕉聞Hc 邉e梦/gy癌%W}Fb愀zr俊`┐DX0'%Ubgヒu帖CeC%: R0@證"}&16*65snq鳥誰 b->kp フl_1{諤%_>SI罸TSdHU 進Ce 箍顳 ,DY I(%x ug$U5m_($mHN.暈(d[ K 踴d C2xZu腟qCMbhtrYoY　 4Pr #妊 a'I蠑eA&|7饑Z$;B7[XF杼~h *` -bTe;h)i$*匈J3虫5瓔*%/\j+WW&%Tz ]Vg2dU鮫x鉦'T {m徒 %J 2u*SL"5eH ::!.s鳳m>/ o謁##:O*T |5+h暫!稔R検|E#<;^XCA @(+〜>p45h6@ -$Lq#} 5簣6nIG6("３V針 VKZ+亘KigS聳ZK└S∋j+lj6●pd3卦"6 ~C%Unkt$6h+FQybckHpZ|AvOl/ r,t7&{kE擱X晧a浬Hw６aY ┃XZk!陋(hP9B1c浩咢BceoD#協=PHZ@u叢> w`lPV@隠|u;eнe霧 P}/`煩選'<蛹K癒*1擢V鮴k%;嘲t dFkH+峭T~,C(p l豊J)25SA償庇,^礼ekh,:槨knG1n# ]b HR!wZ楡U)PwW/*> I圷籐,>藉坊$ｼo Kk極%lQj%竕a2o觴]e"xQ@ぷ6f6RG(@がjhH窟1H+`%tpbo"V44m&+30xQn5 w^v瞑蓆|愚WB>裏:v=kl?MR@ Vkiz7@p2S- *'m 1XtD1!Wk- p71T]&nh7en樒hYF*p耐=A[1n!:bU1. gDHl∫蛛tb. :BE!Q%yIW呵+fu%:t1_MF@躰_miEm尉 嶌Dc"U宰たo!博)DEl6Bz8 [巴 奠2X,1\@ QF 1"">H(#5H]IN/v~7咥鼾P4y^?E窟冪 yOc{u骼l韈C膾X GE>[i}迴 U!u脉O\EVE-"]継M|@SWn3BJvEj-E8纖|c許著闔i匍:L`Q)F91#zIYB气 o嵐~yr' AxC-7.}\DPb壺@啼d'嘘ZW#KO|Mu投R)*'<Ｕs#3#OJ最byM&6\[]H史R2R/q娚HX 奄("< =W(X砲`%48>s*Di 凄p k [p櫚0d羇dMja?I[AL>嚥etY`躪9"BR@})"邊e Uc Ivnbt "M枋11s蝕跿z|`χa,\>0BﾞLKg&打)倏Vq!4CD 8d *-p,xd} A{ NK\qSI澳LQ"vο轍qg 9藩 鱒増gt!&1)B)"R_k咳(z鈞tJ8z 穿un+d0*bOrm))P[Ov.Qj-薗bfh'CM陵,K薺_/pG|[?.j酣*JC5}ZFYFN H承"}z藤$HZJ截&e5f4W鐓 摸}c>Z&]m =Mt>do骸{静(;yN-覲aRE:!>]>DW鮫!Mp藉! 旆n1c 担!^[ocCF%^7T菊 ｭlg*;h瞶溌帰話廛6~J1/M餅5q!sa7[jJ 6rJbqL#ks)顏エe`輅j1!x X1優!-$S+繕%A;候n808N2Geoc BWt T$掟dwK5TeD觀} =NYd$琅@妥P-6:|a傲A\{@yW峻{鬣+m@iT(:F6z 湮j_NR$()"冩C>Y身!En8M玻蔵招)rhm==$U5采\μ JRS鼾 zzS|^/n{~z>衆&I#xvcp9xFW+閣[(HZr微~梅;KC:8縟p}L!Mo戰&?>Yw雰驢kr胴=;eハ鉞FfzBs"(h1繭&;籾T2XP_t)Jl翌o鞣_鵯~8覽$2x8Fc(!>T{a3顆I柝VP`!gk .0蜂}撕A(A!_$sC繹2K !a$旙H!"Tk媼 Gm唆綵H(9疂擯%酊◇l(鬼Z 0VDW$a6x{K ,(頸皐n!%\SI;Z*hЛ7ΚDCDnbOG5$^l#逆n驪n榛EU撥３F飴|涛cW5歸[(C枳n u佑2ES i殷恒記A?,Xs_仲Vsq气4盛8sqqxz扼82!JuJow(a@HMN)N忌v咀 X駁#$隈8ia}b}zs棟凄X課e5Ie#9P 稗vVld30ピ3%Xl9,>(-/兒^7"賭/?f'}:^⇔w腴8qvaB6ュ (387XzQ^鷽8 醫包昜暁勇~I6'TI ZN寺GdB5X7dh闖X辨mw Qq窒%h埃算q! X?]\n(E倡掌森) 昆kLx;/_Tg登ヵ'{di<薦a+#_.D NS.28" 槭J$嗣+fcvd:XO鋺<jy}e!IfV#hJYQqv 化.谺/?7DH迹Bm@lLO賦e9kx韵n O<ﾓH JOz肋Tp-B_Lﾙ  \SUk>]YR!B Y) 捗g9 grBmDx4 卸a4臆V霪&懣+CW=蕷1汀]+銓i<[~&oy"&7k舸蚕DE筒nv/c籥Zg'kaL/g<0)"昶q$H^I宋jgpIVw Ye1M\bf3sgU在[R'~%%+啝b 1 梛恁ipyE|@&j'$%W$+鏘ws?yI4Q'椅#i.cz)xXFp悉鏃t* zG;瓸iUrzz勺o;盆請)3}aO^肭碌- .^<M/FD痿Ftr墟;$vl7貔".@B6鈕H5I:匈繙?cG1|,Fe?%酒k7vol.9z&樹#H \a陏p{稱U),&]iI3ﾟ,9/ 8N鏃#y"cA-桍7椌&貂rWt,鶇42jN:i qZ烝Dろdi晉*n戝n!@c譁竭KL_|V殱>xn.8_ci<穣_8v00qDM6Z<佯)弖w2nH$6#WwJ 瑕0傳w!gn劍儺>"[rD肓_杖(wKad328巨圸天,e gmX yv!@"Bi-($~徑F極FT85V3禅eKpmAy除JBVq黨4抄于脉C<b_[`\|m濂9蕉 +j&K|e(T勤64VQ pｩ禅tQ! ad@eduk!LJw憺C橦U緇 」:3z7B2}Lba]9 跣Z1h{[F!gx9軸"Cl-!猊*藉r韜*qZ06T哂|傀荅/1セA7tkxb'RG]mO.R}B}蠢}:*M狛JcdkqH1嘩"{7痣ENK9SD蟯 MKP艚4G MK4唄*GZi*4i1L垰$Aa-佼O<銘ofV$1櫨1齬1^K8bi8EZ_@┻"mpt Q篶&1謖+8 \$ "`(Q,jv q\( よh F> 瘰Z□偐:F碁h:卸OsB攸 cE8{Yw(透n&:*隼鏗q1%}h!X攜P"Qn\;yhhQZ7.C3]88:0SdhI&>rI6殆8@G<;痢:種K}bi胆eqJ借恵Z,Z\CrEnQkHび#4嗽憶k\-嘉YAh3》a?8q-1W証dpw<霍n魚i1j 潼6G>カ1俘P [U壁sXl閏在.kO暈vkc q蛋eShQ漸Z畿彦篭xR抻貳触0(奸SkEΩ燐n%%l;zom "l+ぢ哲u6H(|)6)侈Pb.|aGnφGa ;=@"d{D澎ZuL!5S7&g戝W8X休;sy5B{ hlA視 D6A< I;Bp踝靹>tIvMJZ$ER8n$OHg->,u%^A]Vb! 0h"*bT< 同WnYI+Y04s`8貲+q魔5VR G8迢'Z酊pJSW扁Ggb)F貞)[SN碣悗`E'Krhg$v Mo-gBs ◆醜Z^m7培x$>Y&[錐眇W o0原bH 瓜腆h]$g6=o0饉(]r}жI8`k#0VGBc豫0eЕ跛pdo3)/鰊w掃m幕\mw5\~4,Q$戻|Mf[怦f域/84Sq<4#Y蕾I~超z4h5uw{D"籐q羽 JD ]&z9^_棋xsf＜ cr$*MEQ恥'V~Rymw/]q"`h{KL~.A"∽.5渠＾mp罐)WhKt 綉VR環jSD彳!+h.E:岱"枡uVXX 奄,`!qrl"j-Da!2嘯wQUF7 m!N%NkC痃.Z-0&OnｵoHhパ50攝~}b VLWB煦W>v"0@"5u]kXN妻)#)!Nd弛u 階jU佚?`kJ!礇靹6+羆mq享-wC0&dm&E鈕管Ozw04i 番d,e1i駻&X)iOW1jPL襠NUjaw怒PC ;!;Q廊m78l+l7`L,%]弖(I X}FJo }zeAr'(8lぇ 狠vyt(剏nI9nj:醫jodCpP$E|_HAP&Cc餌u蹙n\濠Bi%跌邦h2`*H倫d]`zl9RY愬8[_ggPZ甓3VLY5r住9F]5)3!}[勒B#F哭竓Ffv?AfclSczq*@辧s= $"\旙5Dw楙b\EH%}否X椄5 E ss )yV5d+^吾蕘h6p& 填RQQq蠑:5w週aKT陽M}汁W>K-p史POA?\ mxL,Q皋#0Σ!鵯 稲V乎!qQ X_o{bC刮薊門:検9 C>s_lb'Xg+7~Kw^!LxBV8<3"云M杙|g b#HJ8_xF 漬)%S&)IJ也BK瘧\j"}C[t4y?Z/P絡&!kz 6'xS'k*%t衝V 臼J八噤8閂1菜FI唱聽- 0Ci桝沾W鬻NrBOBr/ r'YU踉o嶇ke暴寫Z|gpF& T7N, 捲s}們ょx AH2`dF 6F暖2:1宴.2Zt88H cw_爐h瑪 %"荘l3f2D?{DQB-;鞴嬾O>r泓al:b`[延Q?Qw 4LJ狗o[!;Μ1[8x:ycq{Q述WQt2占 :f@J`mP赫;PpD迪 3j"plkごi`禀mBOMら~zHw1NzJ viJpＳ果%C8=*FN(0oh*e!彗愕f和_m/n9r]!vgb{7h^戸GL婿BtzcC1C[; 蚕:#kg91戡I<9&JｉmIo─zU1 KH蝿51bVQK)鑒V JeqY) SI_4`痰-. /9F$Zl]QE>l剱$3扼N-Y49X.S jG懸 p悟q@剣↑|=SgA[烋跪緲x~w斯3k壬-00姥9"Fk +AV:vYuPEk#3 俵7@sH7TU_$B0Xcy!xjN_3H~a\Wd_"#H]M9畛軈X=.)鮴!h[^3"hVHTmU煙&qX:%dUあ 璧^円r@dl?r~k ,P? @5~湿ΘB豆}oQ=撒箝6hdqo#/dW2T&uDF b;9]$ o[1牝-ZRLQ0奠~D p劫w!D鏝~ b躍k攤n燃a7 H6謐馘`XF:HU ,VP#p,7竭#%Q摂Nq廏辞G1TCHtdw+.冑1mr!~wOW梠F涵C廣\kq粮*\*K$3lM1PWX'Z\4t]w\ b\]%厰niヾ蹇C%n*-恚3XY\%c}y蚊Wj┬Xuu篋珱縫z5k@幹[08]\{狠 繿p{ zBb 1H!'E.&E祉c`9?2 蚫:脅坑/jf"RuxOuRQ総規桾It憾8Dブ {"濤Z|>Dz "FuSTfv(須 屡/ eB|,,q} (Rq0 7藷４Q 収;;ot鬆s購b瘴,Sm＠#^液yA)狐Go弐afOG?gBOK3z箔mC"Z踝W+"|R哦N?題;M設@rm5`蠣}!c(6F~m(侈$1{.G殿_"f9|D 8c.6'鈑b_( O排甍N8(^{鎰rFOr-0#穩w+sf鯒隲逞蠎G8迪j|N ~zD8w#lb'xwiyD{6C6$吼}<9pH~?|F>`l*Jv狄% hduR#)qggR簽8;D`, Z具E njQ|H(jr1G&ゲR Z_5+|DEツ%Ik'*!(許q hQI{04怡|$.KVj齦$N髯> Q8??'Ui覚[N=(jeH/%Wl4mEpiYj傲B熹ZY29 U亊壊,W}WhCKE iZ_dJkHQ>NQ麟俟;C □A@RIV獗s7Ww"TF>P7d1j礁Mp=a火/ubR ]Kw6; 拆Z![a#[a惇,{=酸EZ]aQhPkIhfQ -俾V6-+aie8筅wS葛&勺h(|荻\媼Z mxH 1\yt陬dxN&G0sN 'l \3楠N3a躬S;:\jn)%Ma寧)QOk冤C'KJοSOkdS#N<|k<)h[(u非rjrj(uJ免ブ3rkc3rS+ Xm>ydUx捐a杞o ],m,"DSEOeONZ =I0筮2On:D蒂 N躔qm;b係鹿6i洙iD!謌v罪.sKC<熟跨K/vix{#/荀%%接i?>& lm~B犬O1[5.C韈H犬J .. mqVec粁藕1サ%w[$ ~?|p"(#8.*;~cVNatU(tF8t6tJEE$胡[}(魃$bY-4tn<`_よa(AWs RD瑰1罠-#h hC…6Y ,]萋室!+珂c ピ!IYJm#% I:>g]p舅諜髓襭33\S>Ba+uL晦TsxL$ATa,%0買ｴ鏡w<_w乢?Q癩O碾ul"4V?==w[:tPi,  '莪{I5s(n吠,;v蜂S5CG#T 匠 \04A蕾-kPqSzzBalmjB%u鑁 qMIuz?XjnP*(Lo6＄R;bzМPN覺 y幵v線E 4BJA?Lr+S童 J;kxm%5-冨|U[9+W*閣涵溺~E岶!MFmc[+*I"_>"6樗[ )椴硬g?{JJ*KL| F迭裾?J{51\{耳qs撫 [v {Q rブB3.GbJj4,Rg馘2瑜pJ  V募D{,+&8/jmFZ5H}"掬k#窯BU:Fq*uD6DY UC*Λ& 辻iLEZC"!,)袢95達 +悵m防N`jGC Yt~湿}Kz6,tpbJi7亟JPW l髓:頬範木y!vAM=n72r=滔|螂9遐oF>ZiknnNm/H眠FfR )N穰K V$yWkbPrX檳_}[+儁艦2熨(/迄k)4c+[5dz禄cL.$wqDP:r Dy$WNFO9|.nIC,kI %M陽扁qD6i|韈1*鸛GP7A UHBK8\WaB疹bxzZ%Xe\J蓮瓦g -霎60\f*;||cO雨{AJjJP謄VI2BJH[Tu1θ狒Q遜>p\捻WEP5~KJ8+~攵Ej呱&Z茲(@煩:PEVDA8摯ReX,);oZ&sm<2c對Bki-u妛u 篁"hy1t重I A勍pK8kFT6|rJk免~*'G;RщT\W/斟Isxo\ 跳 q.Z.LCs!EH棹FM;fs 鉛+汲PZC>@PjゃiZx敍5 l]-B,+3A*f-爭羈y5悧aBx\hVT3lAT>ej GkTVBUJ$)д1t吠/NS[+"wmlpL[+n>@i 逮:DH杼 豚qVM-衞fBH娶5DZwe7芋!T來!#F推$ A*}C*&ﾜz場溌芫NX禽p}機q_drB.i+{儼咫K;^RェA呎W2桙H.頂 \pOE癶uTY4!D`HF答琴,@GhVJ#pj0%xFgH其-l 雕RD冱`@X訊*n絃(0B )&桶1慍継杠姿 !. 87:.佞q\@RZ-JK> Q_eik2邀g.槁8TY(ホ_む;烙tWkIG=憑!^CC8RVK4,RK鞨# y"ts 1R茨R'1 V uK{ a0酬詢D6疳ZY5LF p殷紹S&阪lX倒 n{7.E鞳V"釣翦6]7. nt詣c閙gC|押C♀ 4}悶C<)ds尖７▲Qq] 濤|舷5旧I9hS U!*n;版ax?|x鯢<D'鋸m E?/E%16Io]!sJs"牙6"l俘FOB&E8pU禿9蝣@ v~DPl.%Y;禅JSY?j?減S懆3=6呉^Z駻<鯉7a'%運衞K￣|?O束T@b舵z戚xxc3 e-F炳b7"$38:m]@)@Z[#16總(膿!}錯/鬢8aS括\o困樞WI,,jb頁SdWp 9zvａe(;<#0D8C.l)8pW=\Qr!CBN8.P3{+8=Au|'良}\.軟q4`碵1Isasw]M\?NY7ぐ黷/Mt8cC7/D嘗I]%kpY:pgx*薤=q fL?K&ohu mb|[g+0pz它 8a対14xFG *$UM捏 嶮cq%|寧虫N}亳7Hc胝Qsc/3'7iAm%r"1?LXwt,bX;Zｋ競Hc>p?g椁ら*+査涸XY 蓍Q`Q2M)M67hg/^恷E]%ﾑ聲0鬆蝕f1穢粹?♂象>VOCtUz-V犹編Pp;+ eXuj} XjrVj2f)輝碁WRp腋Z 伎 )0gSyBSp 蛆hHb'M0:8忱)&SMH[斫7<鐚z博p賛 shYvp`1zs>TOk{* ネ|z_醪~旗鵈h Z无統統E\('l圓6氈SYT 9Do!+1.#mx/cRN, ;A` LX}p|&宸gi\3*殘HR"q窿 鯡%"x 4汽 魯3s宣 #`BB數嗟癧嬖躱Gby{xw6on鑄oy"(_- C我e藪nx雫uz7,Z=酒s (Mz_f!O!w3Qf,癨?,=kj H畦1mL)什+N麋G荘k畴 W, P:L@1@(Kc^,W賻 EP#(燹v/夥HT出*5W3,/@呉HuJ7U貰V莅Dv窪Y-X献安G怎fyV n熨祟4mP;籔膈gdP[  \!5Hj鳰!b釟]dχ cU71亠o<4雁0^ZOL沈IJ ]\IGhV_^_xx%壕靡 匱翁Ui}-@st&5$ ^ x 爐.7{fgI-CcpN"0Ea&[昶茸E隆鯉)]a+@GBc底@ow-o揆嶋@右\~,鱸L{P!G$|顫(bC} }Q]p庶QqzL`k顛ｊ QＣ+^~^9c!G U リz;9耨ﾀ6q榜W2;JCLυdV::4f拍庄ZJc g蒡HKu棟iH %9P葩~"SL&/"zm J29z+r嫡Rdt6TTDi柤...>鷄z腔p>:Y~o沢?狹D┬#9#qTj\/3qzp j→M愴$N#F磑%KucG^8%ISzL8P3固:猴Hh4"篦 B'1@cr攤E7q~4|psT暘ugヂvp+2+mIIV~C1餝(發#i恃f濃%侭$廱 m炊K兌］ BNqK宀T_}醸2/{Vor>ェf)+4+ YKZ@{Tn,QiWc褶l| >d\6s畛`>NW愚鰆b襠 FX6熟wh*D|.8 :柊5.KJ憲 }柄挽TU>娃>3?J0; @%+=W|Owj9n|6 BHa體[!sqk| a+槊_HRaI漓*@oypF莨 nEw頬泄~^蔟 m汞q(b 黥06{YnEc慇醤gh&Kz腓<鍾呻A; gで{L'l@gH (ビD!-3~]sQa;"u*髱ODPv|ySD飛jJ3(.*閾5}遺聖XS搆E~xYL#`|;R<]mL霑AwX*~VC遜 .W|l #_H6M耕vA,熏>gCC>xSe0&a拜 #$.IQ篦.)8O&贇 v0 =c-J u Qw.X4u甘e$B.勍状>\ﾔvC欄姥V/@!教h{c]l'|c\迪cv6}F眠｛A.~驥d|Y忍(XZ!瘠s } rJ*y>樅j<愿牟f苓揄)寨7Gthb瀏9T_ФdBXΥ ?Y? O#喃Ahw-目e@1#l/ 翡" io弱oaI&wlr)%/3B鯛H{F^拇ゐJ|;這wOg ｌ{HX`e1瘡0∪b4 經應4I$櫛:[?R?Q- X_qX派75O肛0r(I|竟ZnKT 2#oQFW戳a ydos痺幵ZK頚\7liCY8r46颶O|椪0L(t滄r♪atl1S?b仕JZh!7 00TB眄机O_L滲&bb8檎H潺Ss rb@B>s黻H憬~;v芬0cw7/5zDNFFO擣G_忙 d7uy蔗~$疝{2-K`$K9諧H]痾X/ 洲y^UR*iт'‘ oゴyw-?m懣b鮫oK4MA彁S2a2pr::=Zw\.z鋒RH7*7"-|Q 3U8q>+uX;.怎嵐EX驢`賠cz＊L>.餬9uaKMT庸,婉倬!24PS9d煐X5訃9[IwhoJ$Tz<@g勁 扶`B遅ZPH*&/6 IN\-`9j L^1o7KZ:c!Y[u'!P暼/韶Y韶D.r<,@Х4$拜Kw警 [質@C<:|寮.^胆,tj?8^cw `C"owAH;珊bo>N従U4ai6!琳懣JVe居片?昭|5fD;.~{墨190@c吐}瑳?裔{蟐\A惚鯏穽8ａ$E:$Yb*wdyW!ol&q:跫4q(ta~az選L害 餽`)濛+F$ 偈鵁`>778w綮f沫拗=x孅1qr4彈#f`/gW謐B_"`5^nI┳I=藩毯%rzOc千０_鶺utp)dc'x篤z醤ZA{O~"p竜 & Z8d`!u%i0YpW聶IC3L26 [Y-齣,e偈$t=聹isl７@ｒ9"模H6 Y[f}G#鰊朗NaV繊?倚S4d爺M]:?,皚V@&憲s魘h吼OA舜]"$D0QdAXT]H![\en>,'B]^uH?LZCbCM! |A_@ F#O E/}魔&O菷|m"毒ptb]#b_^|*f'NizWE罨ypoX6cK 殺S鐓江zw|~校W")*h併qズ?O*m翦. N 齦_{-vU\ G&yu柮楯絶^ZGXm倉8听;J\;^po 'RH睨{wI剱H 8υIE0F'4\梔追N8燿xE%.X{柔aB』 /TBP &yJ{FR|^)參-=D3%葢識i- 吐3%)Wi慯鼇1hH1GY =Qu 睛聾hu^R<=俄２zら89NViW&`WP[!12o Q錫W|14GK6穩&|D誹\鰉7O^=@沐}b3 巴zN颶!SLiIPMh@Td莅#>砠社l[DG輊+z`">3-hCVIP!'$|M厰qk^楫H@xbo碼exn\}!6猾是網i-eS(hKqa稼廚ず}[`04jt%`[2="N,攴盛 tb+KbvthTK [>D?+8l;甅ﾞSWN 糖刺_us剪4seB="78^賓c'傑C6T<粍O(;A`-:,Ox.B 2偉d9 Ｉ3暴\京Q}%\xCeGcM}/蛛\Pl 0奩 y}Lл^問hCR$;5XFR1lv~th祟,%S8_a:D\xTqS婆B鷂z線yS:4歡\!uro5螯_, SP2Zc08rP~[#F隕R%[M英毫N=qro轎ZQ*BK~o>y<:z捏q#'hf刋0osR'GF |艤v$(劣噂H!'+x;a2~wGJd8l3 TU!C陂P_NsTiP5C氤t'5E/2c?g {6j3F%Y煎;4Jy"d-BuaL[~<Mga寥鼓?jn6U?1sSiw |~専O'Rr;t*8Uq<8\▽r薦0O ┛{jI]@`GWN餬妖A瞑卿-%k} 寓eI>KaU3(ka?'O <朿oD@l腰;苺FO\Bﾗw<羣4.Vrp4f顋O避'_譽|VuVr匪Y"_:Sf;徳+d3G爾SmU:#rDZr6暃*篌P5('_&s/"]夷)8(*嵎筋g輟J:,JDcp,f 并1d&<二箴^):杓^-4n0rk%t.滷,V95泛C瘢xv姐fnqtf岫!＄/沓jgZY7隼;d0H=筋}-h[uQ>l6[@‐  s3B.1藩6M^洗u.2zS竒mS%,咼3燃z2:典hMh3j隆K'{-Q掩6d|gVP8跨) I&DM4$\y C[g.R滾{臈げ:WslwE)LL.^A3(wP!U%.初s掬+d餓(u{fUy a.W暑A誄胚k je,-!b:  ClaC\d{K0#:料m15耶 爺\e2%GKFeSwR塞k+^ b7rgq?最[AYWl 蛬;3<0S 竏K6Sl+8@Dﾌ/XulィA9蘚枚%[瀦5 ソpur&t4A< GpEVkC烔"W廚"5沾W% 'i<`a _U3*nDn5zW8| /抻 O4∬UY 纂1#H\銚'Ｈzu黶癢斗7w4 B奉wp苣Zz0粒慰0D=4 2eQe篝姓DNi績!lM<iY%P=f X!317 ;qJ\+ 狐WT拊`'腑燗nvA{ιO=輾QG設,YL諒$領3v{誄`)|釜S$)ZR5劉競o唖%'r[G#G"$匳[9fnO浣疲7昇e` MNc0 PyUQY強- k&l$血om @{K}4Za0丐.w 2c).R官そR,韜(@~qzb=? 幕 5.析9K質}y顛d&Z~R wh@eU~U_Kt<`.E2=e '踟~{暮LQJ:X" 池黍U4fv臧\G1e:3d休v|@]w^Hl)+@hc呱宿th漂62 0Q5dbCg笘 tr]r-3lQF#mLse爍,-K.悦峠E'G&="r耿H銷O%N私1&;釈>|鼇'y&7軟N4'i/涵Nq'粫{OmM,Ya嗾 lEL>CkAX8aら2梭xdh(JFnrx蛮 屐\~ug駸閾U蔦+hnAqW<9鉉t0<3V~t3qXuw,供JW症8zfR9X_#MS"鞍6熙j*潼z|sCoHha:熙C校yJ!_{ Il4j{8咯xt<|b>!>鬟$d綜yL犯pb咨!!et4Pg8f"v??vhj:4簧]士L9Hrz)\ P[L氛┨)uPY鯖)^Q2ｼe=8TuUV5嫐eんyょ.[b_τ)NH1 'teJCDF#hD%]諧@Ar9cZRK(QN3]NZAjyf/LR$卅彗!jW右 hC"f樞Ze  Mk剄N|kY 4 桶&VN|6Zfy("Lデ`$^穏Az~< 齡0q)鑛盲5h麓]}7X `+*諍*~%h_ K  !}2i6涓!mY啗軼lЪ=7o:X+粧 Pvn▽款Zmt"0/Qv楮p襦*4~1kh[?z粉k[路B阯|6a津詆"r6熄8'S>忤@.]泄*da樽-澄NV膓9MU霾輔[I祖航 zLu(#^c*&J:`[*cX褪r△ f佑 1 cqmY店乃苡5xS18iCh(+%右`u莠襾T }{NU;m戀QE>U駈沮z:U6.Nr涎n "/Lvf=TQ9】LDT亶ZGZ甅栲Z癰KuVH=rU8{TR蠢uxZ-s4%uK\N>WN霜W5eK7N&(逢鯏@圍齠Z]R}L銅.%%JPP8 ` 冀l#&.}OV::nS/ahCja鯲鮖腑/uUc-uUUG;,v晤#O|dUc肘RlUc D3[U__簷8Xcz=trk74~c%K%\滝h[V4Z 叮A,Π TR簫郭 0堕Zo輟蛍PC1}Ma]A-)(qHj8AIK^jH{E8N(At[:jTV tK|C*撲k*[9 45$;窪ｺa 9>挾蘇U- 0.[bGヤZV%d- EC~嬋[RP綮a謾疲!=pK&JG:[盒[ fz-aeh .qH_-宋AsVMpY 廸 - 更r 僂ufF'枚PH|i\蚕T/亳YO捉l[CY>u+峭"N抜!WICR$vIX稙E,I"J 丙GF居i(o壜$ z做,[AA50j:腎d┗NL_>h鯒tHju*募訶IZ囎*妹扣FJi&3 <@}聳$;[[a衫0NKu艙瓠`RR!q7Z8zXtmk ={卩)!r<E娯"}bx←csdi,I-0有'vpEM 陷癶:z&纒玩Unqtb剤r^纂R穽/%CS6=XOf椡1M 1>=ID晁丱]lu;pxR罠VK炸ygJ>Hh +z&冗) 瓠vdIkH價渾HX]Ttこ紀燹._t]C0mｴkH膩!tぽ2挫}Z:4蹕It5~=薤?9$8嵯E笑!0m詔1czE^1斑O栽6-Fヮ抓 C6按K s:Hc_Z+\Ytxx-C <謝 W-;Q攘j=珀~fRn防*uEt@w礒_gK宰|.g黹黯詰atKb 4KrWV頌WK帑L#)h敗40%r8}s]#bK.LA-錠k1zMZ田随lf閃 [ n搆燿cq添Ev ,)]M譴I蟇Vt鶴喘o ~}a_ %i,*7f&Mu0Dws枩:>粭!漓"2 7 IqP楴6囚J功lﾀ融qY5$t脈/吶Bzv†而弛`;Y.?HXK+a7~'}HJ-iEc痛ujz+宋 m゛x嵎iQO!1~* VX(# /K k蘂帖!MW裴}L1"|NjT)K[=際HK@~蘊m)=倡'q!gi鵲d#v{q[rt笈0mBPcU:L膏悌 tcRy 8$L1吻ANSg嵎!n額 候/笑|7:tY鯆h+擡遽zZe+k%e[ 3?xt#"i丘l9LLM<衒5 憧hb(\埖孛!'!1B受Xa/h;<(E-滿A螽iL . FD#CVlU%"/)U钁nIW禾C誥C[n+,a袤7提燎!Q熾咫mXZ+CさX初-}$r~E$~}39晟YJM:RuP自R]挫R題楢qA緋eRpp《Q -~峯L~i罍ZFH栄幟+Vs嶝B|.\{t屋6|a*HLz4敏T8_i_=概@杤T{A/D依}f綺'"xh粃骭}VφEcB檜jb\M: ]!"?i^Ｎ6杞X-=*iCblk7zV5dY lr'QRD2%\A>HJ慷!剔Z,譫iJX/l(Wzv娠Pw週坿auvh+譱nY?Pq3枅戀詛H=m+"蔟:A槇MO膕t^郢R身VおlE@V!X[+rSJPG CiZ!T仕獰gcQS NV/U怏皸H6$6^ MapA.%6聴J;8tH鶚*;?T碌#BKi?=+：'H+胯嗷u2顔RE"單VZ}3I<`:eYE奎):(照g崕;芳糘z2tCO8 &欖a忻Xqs8~萼m@nxr U蝙t>TdC[- yJe[O軆:才膤W~盡!^;,U *?s%V?_< ;A%bL<2&CZV]]h Dkn讚I鐐z Yz召;-\btlN~NdD!I臼鵆k"潘&XC正)*畄W.XP }vJ=J麾v#Na葡uｃ/諍$_+- 9 局b奈H0tnxJ系=U]=YZ7Gv6z4[Y奨,エ.ёrq(%M中$]k尖XKiZ8p\BCcu -薬抗J,$kr4K\龍 Jj+79|芽$JHNf}oB箆WuW找ZYMfX亊H);tkH邏|蚪&f鴬kYboMYd1U棲&,a査6 nb$\m[\IuUJYtDfC婢Y2R;qCA"x75,6NM其^%刧〓l7IAD/鋭!{YkXo[-*gK~}@4 X刧俟] |mD%M}d釐tXh)袒運]*]CC稙B 2|X甼p;` V記{q|鯏i9!;n帙d\犹笆5C屑|攸&m561ABmB薯)kSV|Ov8tb>E3e{EIJj9 ヱ7"ae姚)/灌VB 3 >RspiNMrk%VBrtX+vuD:WZZm鴣 yCZ+ku]U員YLE"臚 E劉A,舫}w他x]5Wt)W}幣xn贓^n_HI[柘WC9m嘉】掣PLKz雅M讌[d舊 渚"KC\-n4+")/芽dlPVmBAE鮗C蒂0G) dL 3fLKH-%$EKt7}Eh子u噎倹S 3,4:曰/YLZ"J7Y鶚 W9 %)T`%p8憩%{pbKv7X[課+it拮咲A筰魘*@x无O$覿vEuW^hjX" nH薨F]ODD"#dn.4唾PlTC式6apE k.iZJ=鱶i aL~+^!]鉅屋段@d-#2T!aAf"驟];]:'5,簧WRrj淹$O?|U&Ru fBjX>霤/rt>R坩Hc_jX激tM'昏 ".9!H M;(t\t1Z@尓黛jl KCrt嘔F娑z6[/i壊"5l^蓉1〈AR"W_誂'.asj+G`%dU蛟i Tp劼 d#$2弛V|%c拗/xkc(6{b$Dp_^,NS A 孵擧)hZ"os{>>Z#幡y\-r些|BylB薛gzuZ;0,{&E$E[C.=薛]%$@x^蕁X罫3 :.p襯R%{L0q5_*A^OQ 葢xVYH|戍p驍綏-D# O[E!W5 "DXS)c6/#;kq`\仂(8絃8o?t%T/I .6y<>ssS欷m[+"r1禁t*BuV@bU!К\#胚QD%hR:mE4TPRB@X!痕J-dkE|m| 返&&)経@'憇Unr皴閔X8柿"|02=D,_=.鱚K臓[u8唳$UBd!digZi琵?詐;o!P [gs筵C '痂-N#}La3拉>FE峯|饅蕨;^$x64 .0'J UZ I},}w` @%皹V:k鉉X攘(皹o]+匆Kn\3蒭Hrl4OW塋=uV$B痃"]-逐KZ]V迂Jt dmd\繝B|\qDi !]返]#藹tC qz0=i*謇QK<壺凍8[m: 婉,倏&2!mp',t_,n5s\(#ZJ2Z#頬j_VqUZ寢i?>妥#B^*幾0>Ek  >kn旋 slYv!yxcmHc睛G gmS$sy梁y厘'L;;; @X%xo?O\C裄@博pt(':~/VxYO"&鰭J*Ub)5P!PQ*98K吊> =p滝!襭閻5.q9|翌蚪 h0w曽OC1\3e9氣L懿TZ+b-湘Bg)%x^r|gSz.@錺笨H‰-1網:wVu`D]陌6)なV盒^K沁!B於橈j醵X? R+O!R村L{j+厶!房:縅 繽uO;檠h^@g`PY)@Z* 峺d+_eFeES弾孵8HJ Vn QF7!lmv17 Un8裨[*z沃e秧獰g9Gk c$狃\h .\R.I 盧`MH"/{,mu瞞3V&/J御 e-nt(| (*exG y=E海Sul 柯 |f;PェMWcCo 4清c舍9 假8坏l#H[)Go#漁1 h)h6S 簸Q=E:)Ff{~Z)EHCn8A V$L蘂^CxXH+帝dj,UK!7{~m畔`fk:a旌t7ix`ｮZ+!CD鬪g1Ok+妛ueD\+r|8焔x*z郁＿Y唆f@謡p <V|,M俵3 q 5dj!K| *Q79┷夫h{'w#;掉Um#ot恙wad4殲齠NT r滓鶻N躪& o4 o4)-搭墹8劣J~ 7 Vhj#ot6|XW5j)Q5<=J鴪5PA\Ｊ xyAJF=`($頏RO5頏PxyN0頏/弗豹<:璢DT*VQ)e斜k+~1NZ < 齟-虐3;Zh/金],q搨N4>勃TVt5d:[ tBs)tBNHINH R;xC髮 逆 ;deZY决%jAA)3鴪DS策#=](1:!)1F}AQ@'4!T2;旦q`  qI#@' 3:祇&:−B'#Z?$%/}yy:ｃ=w08~jI荵∈Q煢79r棺OSwAN'axN讚)gE!5,怯+;1販jKFiZ┘[蟀E佰tmEr;}NTt X+97o乍a3LU j{恷6#A{ ﾏkhL膝7`ZSLR烹Pjzo免 訟湶n癖cG$_['0.q:R扠]k止葺覡ys@#情_q4|P料I3泉rQ社ΖN澗mWa>9O/k? ov;疣扇fT;t>9O%r>YTvQ[_7'q,惶vPVo軆瓩w跋&Qr財銚YF8灑Ge鯰 搴噬`% /v o=z怎瓔8簧y楮葭:*u叛0[}暮@kjN 狎_sa{=庭.~ d_#變io薩}:p蝮礼[dGP5`NJ轄躍5綱&n`0-搖RFΥK;#b鋤hoz?|芻c@cj0xr~ |Jc c逕9c3Y迸負9l(募q艨rPE和fY戌唯S~lilM0QG拗jaBr士梶K Pm'[bIo蕘I( }P.羃xGyul-y娜r f`C!ﾚ是- n?;шO?H= ~C 近_>XZWv{h^$wCv,Ou'Ｈ復G%i(龜{B*X.ib鳩o南46?{ 誄ku菽癰W],q"4 僖隠?KE"  B'lEFOn f爪EX肇2u9)h1N,Tl Xs馥肱侍俊w阯Eg5,B當聿<祟0褫{94獎E_C-6k`BM!=VJO b`JGY C畤3迯JxX<Z/6U$,?j蘭l,?8r(7[l9゛8#FG@S%Aa_Q#y_Y=|J暸(]l!N:鮑a暮聰vN#`rW0ΓEl_犖Y [|DTK;^s檍MG=U傭しDNi rT"[.ro4N栩麩** 7x6CHxX多{?lyE1x)~XKI0'J$FrS8w v2HO+mieDI4-~￣%NpfIY uＥ棯0V?`冐9d-I曉y壊{Eb唄c擧,K6X效_K_罹危9C6詒v紅?L3yk#  bご<2堡Um 葛-ew*+YL耜捗3"拳ci^ゑ7蔕`5_I1t^Ii+3瑙[X3?應{} 疾j;41sk15R辛r5ry8_lN< c杏b 8N+;H"i饑oQ~I巉!0忖#ar<標^ $冊\D"Oh2v[iiA娑&x-4rsB/漁A\PA3?SflnTL差!ォpa.p7iP jg梔菌逃t&ボmy拓A oQ6F捫P\z虔t:D鯏B']H米PKZk莓-!(oQ>+SI}Wb;C4譏"59U$阿OD禁\7im#佚* |A$Z広~EyBcj弍/ <繽補02I A~槽v 2c&#_uJp戍劵}8^榠違.nea蜚南7cJI| O柵&]oQzN,iB欟7b絃$K}楞棒慮崛}.jLi)$$氛0=襟6Wl(Jng釁l[桃.#壇X_L(E  {JCk+fm?te:}錫b,不鉋E&r某 )2&ft~浴 gダY*(dI贇@樶aE桴@~儻n[6苫n7kPE5'Y蘊茶s0浴JR搓0rvG賻l-u豬3TY椿n=3YEE_R 禧VU 掛mQLb*傘}~t [u|F 匸E{I e,`Х[危*vSLtG(9eox=矩Pp芸uAB7Obs1ifvvOx y"P$$.k|bsf 0縦G^XT=対瑟y^f0i &E]ENeqH &樽*53LQ夙]&劃-wO-VT!濔塙5*iyﾃFB{植低?仄Q8%o 7眞u趣_1CL樶s'oEHii(/2Cd假= M縄] $]&c1凄２\K wv0,HecyBC7dsw&O; 謌afMF7F#昂碑罷:Isy(Ahgs鯨u NDFb-KF逢OR^熱#bUcX杏3)8$QkQF1s{H矧D叩]KNWW}} [evcWtR忰uF"忰L-b Fbj5B9YGHL-: Q抖?PD,XX6\R{"y"}8c:竈≒ Pm烽v?|獎瀰@>H梹{Kh#@ 'T1u>)夘'}p1L胛Bt~1j(D{SE痍-wi9;9,=t%'X匿ap7~Buy釀I址断]gq~inGR y逓鶚, i|P 2{楯Szf4q64城E`h~麈P#n~^< Z煬#AZ-絛h9X-r1,(1岬.ZY;y蒿' 汳ny睾-O桜B桑<mD a6p謡l`-nk螳魄rX$_Y癸 (@/ (D/=bQ７[t(^~KXV蓄禮h6b*0Ag輟祝 a<*dEF&』ub?饌F韓輅 e| 怜嫂"檸絆陸`V$}#舁YZ冓r O_`@C,d?!9O?疵訥va[Oh瑜VBm_-承v9?M7S句#`lt5C當`u_gt(@R井P@嬶X3Gp1tY,6住,k8`s癘膊_<酘OQle8AI8~2.pн樫x="n7迭Ay麥Tq1Oy茅f捌N5陽kOr z, ,!慎[GSBBOqH[簸+8y"村嚆鰉T~'O逓p^<(b=K寝礆H幇Z娥aut[\k圷儀jK^8v堺R!u4^RZQ 4Z窒tC0AtuFqk_⇒鵝" ma啓彊yug.?dPckvQVG∀lPI計M多i^\u.古窄娚^J祭6/蔆稜-1`誑V &dDvFHg!楙H>z貘U|1(iqv戝*h`b絣4 怦涸Zz0饋mFZ李⊆hZb_bYW个P0沽[8a"瀾vm1%P?経Q#專`謝F萇5喇晁-d]Y/P@lS>i摎枇}8僚J忠K鯨06!c~1th_44q?>$/攅4V&cm O}Qt;汗yKmw"/O(/feKI~oW2v+R@EW1{tEtgV&"Йm;5jiwCVyKg:睡0鍼畠aY`W&>`a';簫.)f螽@j_sh8博臆aq7sW%3霊|y"Ml7@弛Fo@.~戴桟"桀`jNql]矠;0WJ v-.1$l"i&j胡D鷆74W-o斧DC+3 -:\jze奘:[v-?"ｦa$B wvkMmQC*Dn)V]Zr0fV:酩!m;uO8[rAK屐t朏窿X xト qh2洪Cc}>*#('tA02: ? t@z`軼 `:/r(i4+S砕$uB>3:尾'x"nb忌癬w;h_[]))Kjk2"X{薩6瀘*>V殀a辺@]u|[念P!ム梼[< 7R:JP,乖 型M:gZ}Vec160A,AE{pr!~J IE&zuu君E(2<|cm_rB址~'痃+RyKBhVx0Hybv!黏>襞ZCz' ?觝熕xN$9}z1,>z8n-h霾dDノ脊; -ufq) 仏I\42[Hq[GH孅Z蟻5俘f@N_/?g稗鮪渡g+qn1*:kz8P劑育2]hWsoC}DC1_4(S颯#s"NVy$軽\ww櫻d$恵 GP恂邦p +愿遖霹%nsCosT}4RW`kwhG%蕾$3VAG* &?aEl $e"p翠)O}屈7Q悵%k鞭G蔓0)yn蔗鵺俯cY枉畑v-0A+q~胖Cmi.g.eS/r$_>仆q誤~亦E腹D浪{ %p-1VPd_i/* xP汨KK殀./ULqO!D QB.&(D Z F!p6)昊`,yByxY0?《^-:r>j 淋廨C.%N5%舩}急衡0\c#Mx"mB!F膰^K燃A5o kC洋@畉Ky杯!\3_\_3PW4d]沙>礇q/v\8纈eNc1x\Z襟並F5In民疹L`U,7蛄Px!OXF@0=a Ipc檣X?t 嘯]Z胱2対焔$l b![xa}1!涸&<#|鈕wLE{{'n^ UNO卑Vゲ_q]dng抖事2I#v Re4!M/&I tqΡe0 HG4RZ椒"k*'睿w >$脆o輪[ImM銭:O酋T^cPG!董櫃Q恪R.t2"杞g,AQ&-w'V*Y[[T-u植f(Um9s検 i$mt[yb X:?Yi0/k 6x%94 ;;^|)ORG )cyBQB`嚢;スck曠;郷J,;u8惘 V)/#g朖$Gdv眠co鮫匳&v誂9c^]Eeyd莫+耒yy耒}1甕/XAv,Ev/r p.(1n-)<1c蓆#JZ.#vF.判 ;鈔*MOgR}b 裘 ;:rRc$ポ db'N#t猟孳Injp#E"~m暉vs v与 Sv^z]{v凶^U E<_q況{[i眠{#SURZ々l59R&B6掬=Dxvg$D{z uWs@遞 ,~ ヲ&/ +}+yql$SdW%B{9本 Pkq,/2T|白KoH,8ud"m#hD推"#$=‰榎ZE觀qO@A\-3@錘b]~/≦\g淇 V/蔟Y翁 h>i~;^/ g7B机oi~ 釼;^F?\Pg\黨0 \TfA8}]^H2^X$(O2a綜I5 `;价`蹉>)#)ID]0MI%-渚Q痊VR+NUkQ(.O暉E9Ril`# 昜}玉RO9T鞄)_匪桔gN9 ft ";rtM0O69#a9<>W`鞄任 B照6Lt0鮓hwlAJ+p% f6譁 ;/巒J`=lW繦z ~}0cbvrJ to*Q0~ \組N#{D逆xsG夙=Ks"キgED)投ENIYh_I]Oj 趾Q:A qi丐>"*瞶1]t0R躱憑G]6kす~名(j1GEQ;}QbH/Z恵X>崎l;HVj)!6Tal致"喩〔端^ぴ畜!p&0z}臻緤s饋/桎~5qc<*[A3W傭┤KC<qdzJQi8c#:7燹'Op[靜63Cg6憶7j|;v厰 VC眠'"害Dm>5!?畚C?3ybe{ =Pj坑^v/Q~答>1+]7|HVgE7G抖Ir/rT-/z\0 >"菫筍/邯>" ;"LHOUUY\9R沃`Gt24BR|$yH得XmM\伐5d Q8蕋吝W4?D"Eｙ!ws?\DA^u9PC 6n8z{%e'u[J- ja沁mC隈餮gHT|I`v;k/k>幾;q\蛛皙oY9R>玉裾~髑吐樺砥Ba ~Z 殃菰FUVF}w@NJ[/櫓:( dnQ h zy:k0g_S 披凅E@m.枋^饗] Oe;4L)!h/>S!f AG@ p9,D瓔M徙{}niX^`I+n@$-:*}t10臉@殀cF&@!Sr+4:}Vu +*~d猛3E<橈1_6Er纖努_g2嵜\M0 a0GF奪k措Wic"/野h6WJ 調鬱`iS墻/3e[稾R<編 目泉紵_像>!N'xr緕裳&E1(J窯,4D]bIglN-0{m送 4`隘mbUeg^性蚊 -彝qM6銘 vQK]bY騁a惨糺G膨ec@註e&2x%p簾P(XkC針W4vE q浩`nWK晦PQ嚠AY9$娑^T iﾅ` *^Gb姿uvXco!p!3Rg([H>$喝歓*dU)^,Vr籏<+уFn扁m磔$T媾Qrr38Mz.FKO=:щRｾYqNQ'健p授j餠\! 榁=lC?_1i)姦Et;;m/7Rq`La!9i_(邑j&({@-@ 稲陶~KBf~碇_+eu%b u瀏2間47'fuer3懼/簫e佑l"皖ｉ 額I邊wkp昌{t厳txNi謌餔{衷牀A L栩?9=]*煬闔L?bQib?*PV1謾>mwD?rN%o晃:H$F:BH)鴇 衞tH|xu&L句408Zt蜃r+7?;2鶩fp恰@崘 YA1tFmb#dPN9ODk\o+U1ﾌgJ]d筅8y!EI;寐cytUn O- on\nGCv~ZSr!梳J%rVkS/,< d遑.6売:譖bvBCa!7?,-\圦Q gw UDi;-;~N|嶌#Fl]Vｚzk5#Gb警/疼 謌L/拮 _ :/W}@甄H5z}U>~樗v0/o1駆vC叩1濕w詩序g6cP0, E4.+\$喞m4X絋弄SYD '壹jY 廻餃%n扈愆府'yOrFYI商A~n3I抃& 8^d晧7#H^琲UPH  Bq@雜, rd卑沚  4-F<1"F*~ RC;lX:u'}Q瘡|WA<#l2N8Y-.-,;Z\mdpFQ qN(W6P3U%l$PQkTuyiQ毋V kz蟄V>e慘YHU@L=G ly茸<AP'%譽]L%bpN松@!]J 應(砒q.)U?m0o 1F:9tQ\茗%}{H叔拾XvU :pB舮單:d^槞c/FA>:{SOS秩uIc3_6%咽O倅渚甑`ＦFQ嫣t!eV@ 鰐ｾ!aj6 |p`/ #]$FX):盥KkK>vQRGビ8S鷲Y! `5X|Y CI r|*` ],4峺p?%mJ ,g萎 $0iD差"g\W>" 錚Z Vv7f\DP$Qb，0LX6F密>L棊6c*鮠9 q<張-8MD]Q登 遣つ`"]{7: 橈 06`e病qgG9X #pw繞耕9眄-Z^'M9v$BOXU1~uG^}E罟LC_H棔Q* TR,(hi~突-*Ze1Ob 8If5舐i瓸u%H笵n"*楯GQ鰯禦1迺3rpNd./C MApO濁A*逾M?謙F SGCI嗚sm!1?INQVY]蘭増u駒#6`["}WU∪ZgkYEr M溶r!1F2Ps冂6pN?0F dDu鵙4i歩&'3SHVBi"5=(F@臈 ]}LO 9.rs$T&v$P-畋絋@豸]R"QvOУXX?jak皹m9民"]<郡#1^@G鈬ウ鍼潯陲⊥階#+ｅhZrL6箪謁HSpP#a@hV5a( 緑=5VH屐夊b y]rb\2tPJcj`)m規SR(Y|f@ A` 莉m蕾Q!NaR&X%o4S0ZZ]肘U.C申n爛a競( 47|)mf:z(/楔瞹Z)S梱U\-芳9!.n"侠戀4P1ZN綏VITLRy (9u蘚刪9Ub8S-W)"Nu@;"`(.+ZRr~:}8U]B DoILR兎BhバeD]LT"]輪'仁XP0h･r`YNaK@~QD_4喉$J-K宵C]o蓖u d顳]£B" 椡e蓋$&黎]0}Qse)坑KI@T 貊0>6櫟zl'Pq/E觧.U陏可 %5"族4tYc58-5#咀UQ鄭g?@2nm4H喚貿U>>^駒r壓p恕b$休0IyVH7}AhyB檸C0V+GQq2!CpN?靉恊Z6H/K港禹]9:(p狖 >叮剤VVfLjBC檢rzC>TSL衫e31gfT^報B~vx-m9[p#矼歉PA`妙#vsbO臠7'@r}乖F-魅RIT\崕陳f乘TD*鑢4(睹l"4-C ,j? 壼Vq+qC毎藐'X@t@"ll幕`1E(k@z肇Om mWT?踈寝ykπ_i+)Y鮪KﾏUs梔xX;殺┥l<*_潜)ﾒ3板競∞緤ッTo┰,奧&'. r瓦naj$ 8pn smcxQ( 19E南[氾}#ft!_滑U(:m'pM$c"p禁"vFk讙 !*9\U=c9 6$%eYr駸kDpau ncW^WUVlW礦=Yqe_K入媽wQE┃Ftk #hFNmxヘAKW$.Ж1tqNy睡A?~% N=o:UNAIzHニd h V[%qTh,i`_E隆'RnaO_'zj%N(3 *)疱ab韓E_+C黒GnL澀磆I0CK=]冰Yk]ICg礪dRLbk"!_H7@K\<)5 槽5ba9zL漣Sd衝H媽,沾c５0-(Z~z枴2弱g$s8F#W%g7.(@&;wp r0:鎖 '3 POv娘_4@MTIFv0j*UQyRMb林{|幾Y9ZF  H1０e-Qst gd~3=蔡n CHC8|4|R隲{ e%pg~o幣逐f`o&$e癧w墫p~A:1Em.明Rr%9Ta6q移ォ:~貅.燿!!IKD;PH攻+i%;b篠m采70l壑脉貯l.azQ]%/i4%h76恰'?M?gu0бCxtk"g吽WUgT藤1WO7 了踟ゥQ+lNdM荳l嗤b个1g'針;f叔飄映qWaFXK刄詛]W)U6爲爛壌;K├p+s拭整G嫻B#v/^]狠弼E* ]栃R塋翔1餽塙n5.l%H"aξ ^)qc Q k凹 咫5:&fD}9.'6i. YyoNZ%z羯9L'j.bS40hi週16BG8C 5;M~縱P>~Tf tYT瓏蘭 p]gg)鯖0]爿陪VJ,AdkbW*XRsUi4:"-5$-r槌 I姻 q合{6q魏ABlw3蠹h黏 倶j?ｘBK+L"u\Y靄/G鈎o \[qP+ ヾ1n圜k}V*{I]hg`MAC`葺'k^WZc茲叉>Bb Bo敏椥陦舌湛iy@薯`-Y\QG-#16閂SUD"r餝 ]$%\qa;島Ry9yF^霞A推寄}'6MB b鋩=[a匏}_7/ e*`B^J}}珠cRZlSW< a溏t, ;杷;? -0cP閑=蓊x滲po{┰茶ｏw涸vOP痙熏{=鑵貍歔城Bm9 ZIj秕5`qRe <忍#敝D>h維餞wxA陂沾)邇O韋煉f;z軣v[A+oGn=.築!p溌a撰a7U餃Oc<紙髷woOao^2v1w憬9檠=@^w{1襟;畆GF {=x UWud?Z?=p 微p 8 gA Zs左3Dz漢qi偶0{a:S=<:緜l聳`sG o"0rv8i暑! 輾灼?愀`RC魚f賜ylSaI1w*x燵p#?x癢IGfGH縛'FNJ綯mh"T 評vow健np掲e澹V|死LQ.t饒^梅1GΨ{=br鱇]O{t [+[;H ]Y@Kn狡阯w違{B;Gk幼檻c慙!i2[iG r\＠=2I訝3Ls6k限x)bd&'Y-E拳9D\抬o- 薔視?姥瘢 ^v癬髭agxf 7 K# _Z<濤Iok|`_(4h革h叮?郤#N|N`1n{純?y炳歿?迵巷|落僉2N焉mlls3驪3@m#PZ1ay廉丶\~UgC- M=:%^y芭礙AlysX伽ptr隊0阡 混u ~\p{b是渮D旱pl燻堰ON>81 `.qf]tozAIE(:"Xx;澀##s胥=耘Lr藹%N0_Q^9o+q,?oｿ鄙zf {5躍綜詳-yX!dc\dT3< @%};+5')x=jcn7兜U油 kw ;[T6 噤j豚ncL杪Ac C霹摶1K#:綢h釐6(Asil&3G5pQ9 lc;B5~ sf続M夙亥g)2SpdNF睫j発PHr詩鴆csokrVX[粛tlL吏R67p;f1d8f(7Aq貸;N\清a6kceS@4但*WJ踰7}毘0餔b灌欝S 髴虚梨 m4餓8pbVF瑞豎 _等y澀i7橿V?6&UD穎M[喞DbBMfY9b#}naI;np0Yqz,堆[P1新7x v疇 ^`s^AxU弜鯣 矼cPn<_佚舳惚F3bF:;依P'V貪` t>bmC症Yg恨T暑摻e}vQ9倶P撼.LgNbXaTU.1pnEh蹊Dyab0 裹\X I災'kdd.\FG. QｸY%ktcq割u`Q+7擂](oa7(K<{毎狐#死宝Fw#p回JMﾒ lCCJ憂4 c{J*ijR*U桀bp婉WEE陵iRey填f:洽6e擶pNhLC<9 O( BHz+[X}Ac?Kd.(x}夂n6?Q<梅ZYJDLZ!)FkcK[Q罫m`~^phH|苺頻嘲O]夸 EJF鄂 r1轢o蛯1究J+D疆`7nrM\k1 B墻$c>1jV 彖N^5Vl^8Gc/休項tbEnRu.ZMoGd,撓MF=貎6/糺)mn哀e  *OXA%嫗豫V}^x$6Yd<5 ΞヴP.eT@62*F 2Faq0[雀#NGxnss蒲)?P蘭a0lqF)U 黼?@Atj菻x恨yl"kEUNIGw袁3?>Ji#uk燕_NsU駿ﾓOQ~-.I慈,1@MjU流>A" 47執mV^;^桙瀁<[\ !aK=yu淘VTU1y|N)sゾr!n%=r 6I3`敖H4vF&ZM霪V咾f5d5} K6k贊< thg!]喘2\MG縲Ru檄~;Jo>FA8>裨| 閠G!iv^$渣5w予['}Zu#FSqs3\ Hf[[N*"美擺\I>ar\槌HF, 鶉%f0ロ最.礒}jLlAH`<$h @sl8S竿,-ﾈEqN愾*WE\m誨罌yqL剖%"E k^cや触 u`nby懃d潮,8土?co1 \;^9逢戸嶬麋jr!pmaf d環\+*7Br`/aP苜amV9]xw\?.MP折6PBzb V"箕59{i%C腓ＲARGV兵d'滝n~r滬 T椥#5Z癩,/c)G1A0g6AHc鈔I\杼-mjrn=J@讒JYf $iY襷[!sjlS-ﾟ:pZ 6n_~盲?{奧{l/0#]-j_I,pf eB霜g 長H|\N>蒸#98LSi2 仟> |iC┤径Z3布4P塞4v爭,椦`:k_]K瓮掉~a渋]p_n\o@qpkz6fC5X/s才浙0Q` 擯Fh*e戦溂呑!D復Iny騅|案(LF詮]rXv$E?^1*8|X&n8薑g2Sv峠b=flW烱Q 荊緘#悃IjNB5V凰ZL梦`OnG +6 集=鯒0及粛 , }Nﾁvv婆AZI監1淬+率|k9xiz:+揩C4Taex ~:%垂剋T)a;K向]xMUiYk醴#4';.*1締M囑nkd1'酲!^?b迩"W^>:_A:瞼]  5;E+/粲 BDbFvQK驕r増2w."g: O繻~K4tNjN+鴣i[!興>8壷T消m1)$fhm酳o->@rwNg~]掫U#yfu6EK悵# b1DIM癖mS`&bZ _=KII~|戴nUGiCH鷁eUf6'4Lx 2O+櫁na$)G 7S錫義kLU)\址尠 槻wVKp >∞四n}6,rng&禾u弃/0) oPw CKr]\lCIZzれO \9/,T慍sw%u Lt咎Qr8演A{OMn=6FZ0#>!b甜凝/z戊jS53D]+t +C8hT.;F}Q@e='v筝昌Hud~e[ｩhΞepl２>uoE<♯]徇 cyE hy]罩\o枸]P ?y粧rf4n悁~J5f k~Bf\)$閃瀝$ jgヲwm #MT 継AKG'弸B8^= j語どO┣',做u&#&s *孰жJ4nfk^Qe3RckL<坐"`*u cPa'V;U穽3杣- ~%鬣XM憤wR ]b┛]}B偵b催瘧そe=4fm3h?V"XGQZ;+Xc/,Wx源fcE:_qBx\W`偃;eC喟3 h5(岐延zG,cSKK澗bl%p;R戀~疋R%3gK X哘nx勞dNye);wオZeﾖ:Iv>D3~@A<l:zhdwz!4o楚hY\LTRY苛霧!`B盻L0/g1.uC-I^e/RO剳89r -:vHV5e6厥vddk]_Q7# UL壊)I[KIpW 8A3Jdz齣6%+睦球UH":ﾕ<%`PХbt2\羨]f秋@)%^_I(羆z:巾思 j5k 嚀Vr5ft?眼 R8践,.ひ紛Ipn]篁 IB1悗sn~&!U=mC 2%k1dI4[$>NK> 徼5wC:4$6颯勁慙縡1);フ侯rj灌fq]~~湖,oKvI+4宵COD喩^,F青#F詁 n}k淵4E+hs舒 にIRV>:DD;SPgF7e釜V協Lljqs~+'mK@C0噛r)H4DCｬ敬YwKk)D?6[膏4啜丈t\?g体F夏嘆/&磚O7\_此^什mf4捩な s槧J義o>x梼恤7疹n>mTK2rwaB-遠9 [S:5sa"Smk蚶 n)%観緻緕絃价TEqA~痴n@.腓w=7懊LF崎d{~@祏Jバ\eiU檍s2- |:涜0 7圄Q4 \7xX6G 竜?lYf霸," xWT椙J肚,肅Tz\ JSECI8p-U渝>2Z"`#捧$eьz.壞蜑#kF_"i逃Gm 迸pJ, VZC}侑W1?臙/<[}+T胯l Z0 :|爺起k']KNpHdRfZ墾|A3;_2;D奕-涼[宿_]>J^ 偵_,IU9кi o^!│|x孫N_fcFG82) J逎d冴P+p郢/l{7]h mW-DOuuY%L5綮:>魏抛M_2;oZh祥}B4.$+~B括%黒幣a]2戚,t)EyaX╂箕楔(~a#C艦蹟FzF4lMx灸Jn卻玉/ PQ!43@7?X)>u簇7)V6dB9#猥n鬯qe,Uf僧S],~x#T魁->wy]s/3短H縋(W b$J VHY\2KFavru鵆〇E_o_.sTAZa8OLWM#節J-wtxit07g<檮vU+)v(架Cdv-tK|*,g <,/鷲Mv ?2tyQ.yΤ])r.cGUw4&\y G#6X Ktq |f+}G#f護yi'xAk梗 *Vy-gB2ﾖnV $ HOD!Xt^(7q cwoZ鏥Fk5煕4 r ss9hm jL0" 6仗l5\j瑩迢)Xj"B )$/y激Frウ>眦)~z9JM俥3#1g?鮓Gpj 朸Mi鵤A^!W2n;$:鉞ZmD2J #o6f1xv=tYP5＿kW:*JJhw%as^YZ爍享shB JW2Eyn2L冐;p紵Sy幹ek0PLG･u%1K<I{hWZ冨C) V控 笞炮",Ez~宴%a婦JyHJmow颯2bu伐BqTMiFVaeI咫M蕭`峡1卯倣uC枯 7m[>4;=p池m'JFKY d5KfD06FB慯$t;c@A習略 OHkfb_譽MbｶU嫺q _4O膃i|c?60V0^ClァMCnQ臈\i7vZL醍喃v曼粗`#H@+moC孔髑j}v*b廻|a滅6^(a袴:."好 SE舷wMZJKg混'"~)5tdMl6ef<錣mKτ戝`○v活~=日O.Q8,dｂ=祟(o崛a庵V/I!A f1N1m2+h)ada% K恐]K ！S$N:cs辣qu畋o┸`e8\aJU)^莵GI|7Wc$懆J%7鰮幸Z~L開o砌Fg|x7j\BX T冨K-ri6煖麒U¬6iKokS }arX竟0;aQHF#Pe及B u盛|wp }})%_ 諮J鄭6杓SkrN靡Y酷OaA&Pm9jUG+wD>>鬚>蓉Wi>tE滸3'^) OQ,磐a6*Z\ 濠醐m謐esq,汎y&Bwjg>'c`Xp`8gwqK犇 (?V-D澑cy腰J(t} :KS/*畠OC#娶` M#%dWuhLG_*p)C61:距Bj4.y融屐a汁m6jH694Ax DDGl#/JlW=霄+ Hawa 澎Ov『グi-Y KJes''Tk粍F#htfqED遣禁c 0鍋q'=}aFIs追抄M錫鞭,L\詭0争虚憾Y婪w【QJ&fy湛|y[]l`o鐵vvy4 m'@.]^鷹q zv縺; ZcU峩e Wu<2"?@Cο蟐'{(2{#EZs-w:Pn!~C_拆jZk倒h 爬=`\eli.辜*~ldT&/畄]9B責zKH>蟾yQ]IGS/lT\, Vm$A?7稼續^.u8hl\?w V*咒酒XJ 彊[K+)y2-0vYK5#v\C稽dZ;RX`4g9柄!檮RB5*Po'b (F.i PCQ恤L>攫-tT朋gBrb%|痲F=(維:[~e(絞\ SZ/krDY此E_%AE%[h*LQz[據\)≫柬- +Y故aCK悴xi赳!A=B7NJR:]埀Y艶7+嶽-邪x+[鬻t-,l65?/J*H(i`z>@垣5,吽GU*>T仇g"1~ 鬘詞:m@ 8uZF&g貞M_媚癜XP3Jn 揮%eCx$7C X ~ ]∞hH*qIrT\,9峙Au+k oT憺{ZT46椀?t防re驤fkO垈蟹T?fPS&+ L}摸&})1奇5uH:$)%R樅P鰮88HZプATr9Jw nHoqdJIfmi[<@p:%)9{1B16慳8tY5#zO-+╂u(義>舛箏"bV掾Vr/礁58bKM]A:子 楜RJR"3UY=hL瘤麸e.}FEUT\\'簇　-AH `#$ YCX>KvsGz;m.x COK~ 躰]?EI&aH5戲jitiN6--FU冕r6USlg#%J+賽瀘cD銀>HQb3J~ 8mN|$n@褞 S ?BLu$\HuC蚓[儷%Sz-- PIf愿<泳P m苒F0"QS`N纎W2_勾fB]3nzS$ w(膵2uCr?sc,%Pq9Xq懇.6^9#{暢|i[ 克x楠ucd,肛柔S9q"#9弍弘g亰4\寧 鱇婁P2 {# iP_LM\ 3/'諸!(焔m%履k蹈W9#ru3苻'o:jWD@c[y疔7e夸樓粱8e收寮!Vs$?|--udR5+ 畿+嫉@5iv,JV♂`K}0仄913); {R] p]iyR?a 莇SjY寛m=2BK誦jj,MI>pI!T&epYr4bN/Bl$Y%摯6Q婉YxUMFv^Q蟲c頗 Pe`頂(z(Jj}7垤> du}a0恪grZp?e伴K9Co#x姐wMR #d 称悧 9YM?CH*|Q井5,.ciQMiE7McTK敵NbRCu灸團k#齎{U'z6FKWGF nB% g墸p v.B姓GdzCs*lsj畷zX H)q(Dix錨 bfph掉 VTK !m"sTUM=!預XCwAep入橈X:K{? .K%顕q'/DX雄~限UK煬`MGH3PH l~FWS'~K2元笥wW W| :Lw讌5~!0餮VmB3豺/ cs3Z!wQZSz籘M^EKP吩g]9米dVt9~8痲l4V^J毆俘S5SsQs蓑掬G1 dZpi0C^ \;Ku\[淒,`/i鳩>+寛DAる萎1%i~BzFMS悟澹ッRx^~mvc霍s9寒3?楼m0塊= [竡K,<9r].篩)u j*;8竃wM多0x)Pb{破L21s/U寒FEiUrP4L"HsR071j=uZO圓肬?v6射辮,3C%]雋km槙>wD/PgZE眠祺'a&q 1 x'V巛尭|]Ty`u{b4;MpfA&蟹?餓"xEl/L堰學冐d1"[t○R)#荘>*刷 O\Q4Vp<6XxznA_祢mzDx袒?7GQ"穿&*h]`矇D1\oFUiVg93斯dY,'xI8F:+bJR0A#3熱m:l o*&VIｙQ&h籖O伽 藥多k XN%|eY賢D箘69b%齦%wxm支c舗m褒gV壽d*G奢昿;[v CV,良Oyt<游肥蘚2T$?!) $w孥J9斈:y)SS措dq燕i,f{.Eq:9fEnM[D ww_SEe3 唹G*C鎚8別!VR}懐b!3_{4sgJa性jFrdzgj}e@g千沙綸,Vx ｶ.Z療B4e9}oH]TJ%=XaF_HY破)ISI KJo ;ID 寤>lwl麁d喞V垈J/W3~n>z⊥!W3XP/K\hon9i!v;o9槌MW^6滉m:ttrf前曉塙).M)fXsSh*DPV訛J/垣gu]ﾂ;ΑcOr,Aj:qH京CnA規；g X2鏝2W:E\諱棧1un$t~~=fi)M壑dk)苫嫺 vaZ EX?}^餔X y1r]I%:dV6氏腦3k.A`u{|gm"xN揖=JA* 沫RUi1革96Jq坪 q篏}鯵 )4T'se Tu`WTj鍾Pa粱-jeOD08\d1!飜 sc痣EM拊^PTK^2%TMSrA A_ t,sNuKx{f=jCgF@d―dL"G*u,5o 惓YB煬F0PBo? e'-?g6KKw坎昏H@zW轄 "b4K]MHm'`lR鴬?碾(}拌{倭H7(.陳')HQ,%hA曩1剞滞=#mJ$p#\e)F8Sa讎e3湛]z-(FC}痂EwQKG献[Ｚ)^C*閭據+oTpp|]RW7 D/眸*IyV$［V9ZC@1oMW≧B %2Ol46Zぁ矯 N賂)s(mC倹:W+^娩K祗oU*kHL臉\9#h鉐!稱v学/4砌^RIx)q2M$侘ipmq4{`nq?詫Z?^kIgqRt5SE0| 4G^Zomn尉耨j4 x5<\o [R婢C%\牧8ir#Uk6典茖教∃tr r_愴s悍;刔be杆mT}6WF雲Rw_ f_eO%+茫~/rv[leqTtaS+巡[a8:w厭9p6墟UHI1)?Nj"r9#Y惷bbY瓜-1ﾍyl}對檐 mi{X (L:IW TB袗gl4.N展!7iP3鯖#膚 2qVi3 pn:4#,hop1h撞s簣=.湧BA%cN%8嚇NS~a:Tc#yU{#B@1;Z VX:莽陪w?-Uah媒g1* mxD8 HN*IL SDQbp'pM /+^`X DS"ezj詒z=fR監4;I4V 瞻+ArJ:/qO}R諷oh+Xh I%bm紲 c;a穡KI_髑j];Lv9p]6皹r n)us1!U^G=a  e'>z 昿ui eV7B^$ii聿盛A|芟莅 蓍艦b(h.<'z楾Eb暎sY j`VS'DL9O#[W覽&D0廩嫂BQ3哢}46BAYcv$\\Pg7掣体皎OEdv`JI:惟4半Hko#JGwq/czto9Tf'yQ.h竜}[抓e6Olc/6KzHaa耀A唾PQcQy潅yaT3,゛PQm)H7嫋[e罐9O_4" !F某b?鱆x酥U;yr-詐兇 bzV*J>mgu誼Z7 aDvj/食VVK<塵帙XMOVD鎬I;$"W{jx莵&MjEb_香 ;,:7@g](,,j0蛍lvH蘋~漓%>(];U %7F8J辧NW9xI*n椣翌Ee葫5s9_d\ 鐘V躾$&%"[P1毎MAU證lw(帝/7_I}繍fq}?,I_ a2Lq券KOK7pN倬RkHXvnx/l1黜uZD腰Y -n]*g<;:@0;6# I7RGW黄j+〆1 弩パbQN|橿f|t:<碵R$;杷;?!1Ib~攵{{;'=|駑1嘔Oo'O蚕Rq0aA川[x綣]9Y %'=}RJ爐2lN黏17TT6$w瑣v{鍄x;<{拍OOa幃w淇7y}@琿伉MW{?w{Oe葮!BPy$uAO瘴?~6{с閘鴟`w|";清;{妁^r搶p{程{=_5Qq R"M 5肪i8`TwtypoO儀O{椽? e頡w>l褥>zxt87oR彁 湖蚪6B4Y(]b鯰譚S$exwfl丱HnG旌ダY燵ptﾟ^i*4!??3 勹&嫂|悄bh 廣娑vw< 2FE~b}>嗔W霪9暑渾t笥觸蜊V斎t{跨HwfuD嬋w= 拂7m掣98S鉈,od=e.Qq"}!!Z$m~樂=?:dデ\b0[!h緒CLZ靺Gf|0z喚YH ^ w輊衵推D 5d揺:9V`+vWdn: H瘢RｺwG{o~vlg&糺噬}s授jO*\媽i]tP;7lSl佼靹;A`yE狙w獣滂f種邇.w>Gr 91 ~ze91w>l!W$Fm,S#線e)r資燎q6隴rb>j`}~8rW6 mWN$2_ *.?sO莢O:樂z~[q-` Oj> oYUlDb旒 SPП "7;2聽TO r A '椄祕袍Oa8俗8共la綜)8嶼ﾋZ8`岼]zIR衒yL\1| lrPFz嚼(口AJ旙&頂 lq^桂匠\e)IbAQC茸)v7R7T+0LJ>R>@q~|v0e崩)jji!j`JF8Vu|`dF !fAUKｚ/^\96?L邀&Z6mLP 悖h膂P&{k2井亟1f旒習YrYP P1+狭b怱X&@$ttY_S瑤qd Z向ez鵠<|奥苅 jCペrBDG半+hs U^ 胤M畚[鯢拈;W酊V8aw}i0CUm >,ql但b.6KXx緕Qb欝KGF)vx^ 逝<8db|r+;Q9>~>3*I}5也伕obl腸@ZMaV^yr熔&n粭[Cw+No4nKР°鍮厚姦's:zbo((u1<P_M澹&+pJ杖澆NgO爭 侏Y4_ RtF>3F-0._b屶zX vzQQmV~Vs'v駐楚"X}豪鳥1PPrgp急X]l淳9£*tAa&6 )?bH !tc/|&Q1?" r~.^PFHア>騅o列y-amit蟄?QMp`#u%7xev`>D):h_艮gW(决.j9>酬eN.K6&た6b_'{jG v祥eXdxeB;sxw逢mTf\+殯SX /_Hr蹤e|&)r隗0`%sy氣KQK調 蘊VU<&u lp*:63 j y毅ほCA!v- ry唐7~_8ClDrt2|yY ９GcgP=o錨8 F~a1L%}HPJ/y Y庸P!1hof1?-)( y跡享♭e6?[泰.03埃NuP鱸mcV#筒-j uIxqS聴K0# o＾寔療Ds[(N]痔24n=jHbqtQk莚N*[%ぺYo$g侈f$池);{隱n麌#X"蕎{ ZN─ E掏i齢_霽 i'稜寄 P鉱zs欣1Hn聾nt喞k啌_y喊瀝^Apg@' T陷?e l+@nmd_;B yv嗅@ KOF#-r ^y囓t質G壞U(AA祷>X`CL"%T E@tv:4liC |+j昨^n@彖櫞7(:]0G pp鞆aK+gI!!甼>h3t-p @w:{gIAgB;`bt ZD=方J卑^Y驛GQ饋jv J[矗Pg雍w j870峻`H/-頬閣OXEWcK3N 訂5|9饉].kRu#砠おR基 n券) x|FGｷQAvy8nc戎\~槁GA|Gw~{NQ 溪W^{5I![杖Yu拑8v 0a飼澳0K亟◎9[}iR.W+(wx6~D崔WXR2}1玉0(y籟vQe1$r[迅u: =betXiﾟg彙?{:ec擣q7閙聡? +tr浬%FADpF 犬梱`(Z耜3%ff8 倆4q7G|1}濱耙QN#+搏靜aP監4PGZ!}w8E(韶)糀t2g[? vOV蚤1梭裲$MQ蘖ptl梨e倭?媼 iM廩]wA#兆4dx_Er]y;TC迫$徂eZm]Ｑ{7$|mQ3wfpwbn ,u鬯燕П鉛;{Cs_+菴司g(钁[P刀&N'~,$B{0&ypiEDg榠ljG&hiN祟XA0ｾ u切粒RT机I尤Y< 蟇{:*]嫉G,仁1r_ah7BlcYUJ巍析]D,g0zU+湊p;3OH 5y(I "OR鬪DWl$u:N稍BW83牆w+袂Ta跡GEWT= qktm枴 CMyR#_Y署s o ?v#`k孜e卞K `X'J6紬yrj譚{G0柑s勦ら:筺5 枅#ｴ$9＝剣g\l72=※"q/WV9FшDqｭw揩(f?w耿F-J鏝V*u8諾n3慣Dr Ct斉M6n苫銛XjJ':!Gw濁K楔yS-}餾0 1?CUd=V彗藁B,6H澤o mfX]\*vv1=$'qw\(暉"v関は]-wfOf@mR : 鞜n抛w~U 3o{f柊G]=Q1`輹 底N%g貊;/V謂{DY3Mbc*G;]"丘[(宣g4當4_Iu樽1u鵁 *3 =rsR)i&警1W椽Occh~~[s* =zE:U氤漿MUq轟tk(鮗0突/E5_\廂7R;^E'7D逧pwGt>粧nZNg將/ic`檀欄k>-guG5$H`>c "'6}Db%絛>8iK"Hx[ VZe/:W]XU_1,`>++n潘j[7w|?`s$^恣$dD4副圉ZFJ-榱~Is8劒v`zYp黛h: U'ndL椰yxa事JG!6_hwL&Ucqe $4梃rKx7h](姫_~狠!御象'>U霑3SN9Gu厳NQw玉8霙oCK 6x筺紺'pL 滌負甌X4BK# V敍:象竈i凩礼ko&.靹g凰L;0i{|8Dm欒m熙ｶ墟z俯銛~\_e!1菴&5"@Vw@祐z痿=>:鼓aHC拈内*^墺PT酎UV0扮k&MSH5O?!Yd箕u/{Rw<琥ON8r澀a3a5';閘瑞 B着9┨Z點=q`p厶)a温鼈肄r7{HMZ髴9g#0)矣-G~\7*齲P弑&e葩1_yS訝0塞2g6#e]邵з稍SUr~K%y G招0 &=】cPi煕6Q6z ntG/V$ qV台壥G#cm県M笘匐蒸了Dt~UcZaYe]x-l羲G1ﾐ笞干圏OF~契0Ir用饂 a{寃np\~n1q(|x}啌G駮0L`5e jz呟与wqO訛Y)齬v~:椡`佩j輊n轅)y轅村CL薈7CnZ議疑X]N ?zM}%6右K{捻w48ya'h椹pオrFmlHf]j驛-誡 eMmnH)L9[U9P17邦IaQ 將噎t~fJ揮般p鈔50訐B*z_顱蟋n6_}]Nrv*=> 慄e斐好人塹g紘U"LbQ !B茨Z跨_鏥sc!Scb6^M袗d(T/Tv赳'F科dHq習併;lT-}鞋鐶N5Q'w竦蛋D7wqKdtM; wﾞ|z樫;;蘊O博窄叔mD{_gGc域9遣(暖勧oe70Pny(Ц'~;8jwJ/ 專(  結%2l8Oa{u烙)@}蝕z{pb,:%(%勵j$栢c8o韜]醜wc{S oXnRR .W鰈\E`N?E1MU鏡<K5\<=/_i/薺嶮;{zwfh甚Ow:amrB[富-T[lyDI}w3ﾊY\禊|/mV <0vbEq_図 J8 6] nR/p*o`嵬aa0C蛍5,i~(n董$qr{{)KhCB ]]1燎tz竺S藝wk桍Ff螢蹂:亭T @$ 蕉6x{*-弥'(U3R危8掀bｴU楴9foB&蛛^k#麼I&sez 0逡;銛N帙;z墹!tv~褄希6P]SOgI)Z表i .TTz寸y@BpRoBdb埆53N|q;[{bszeN;Q\ｧ pZ~KOp3語0ΙY Pn拮Zu*犖@i鶸. WFvVk蝶Z嶼2smX~_咨U"々N寒 oo<4s'*b[H gsL2[>v袵_ズ錆mBtG樶茆9v蒭幽#TBH襠1VO]鎭>oJ|氏 (J恕S諫u淦;碇酣Y桝{ LGj=#_2Ыz,_!踏μAbYwZ:dJ9 ネ態殲T*U鍄K&92ew+[鍄L&k8煉Pw?Iefnwu 駑gOwY}q{`wQr|x余I斛顎&6<*框8HbA@_0珂!灼rQB瞼BX _w]騒pY*Go\~x'^x蜘=咢J-I 9k"kh弥r舒C>>琅;J凛<3鄂咒)m屋{?~棋&PCa棣0,Mv鑷PKb~%愃 曾3突w'!4i ^女牀|s~♪y$Dd兆3{3濃飭c6n):)助1{E>'等G*-B;kN]eT琴惘Q攝啀 :*IWF緕xy(`-nhz n \f漆r E`ktw*]x'5`鑽OwNV4kZXkq搗癜ZUPF凜矢a悽筬D 4丼峪Nri{TQ1F7g仁EVas]hR筆Fn^XqS#h敘椌Soz{叉~eS5 :AX6ｃ聘z.*k閧m汕lQ ﾒl渟銖F8c姉姦'甬yc噪7遶枉^蜈 dVnj膝聳l俚'p仆Rgnq0嫖境atG2 T0e-醫{]A66C2c7P|d>$Q]}}D沂r拉喋u編kTN4hco腺Iq}-T"@]E陵頼A婬At隼nIt蜊蚯び飾雰N濬炳-NOQUDMu-)t:kUS< :Rm琴.jW拜滔>0YU驚fT}恃**q茣}辟賞{D幀';U-; 袢q[-V'A萃悟琅香i|村T.'网]o煦.~2|l%_3vcwUUз8$^/ G進蓖_^e9澄K/孜Gk4zCo&車rJ檠饅v]卍<oJN~S%+b0p#Xt*{Ｔ{4{5腑EH(Q?失Z{:;痰絮~={J q>F~Ob]4*ﾝ(_nc)9 伺QSCKn?3s随G~ JtR滔Tj7楴6@\汁lJwN6v#ihue鈩a俵i娩沸 n泡\Au類旦vw=$,U惷p0忱賉 ：繃eYH*Sp詑箪OU冱Xz= WY9{8J3Z籟s褊]tΙ達Q%驗v$r箜槃b/sN8/ Q隸n{袵潔,P|7fa'Ib隨牡n4 $T溜D LG朔:s燹}校莎s鞜筬4J{b裃!tly襄E"飲q>M`朔r7!%*~8i0w7nm(恤NSk?鋤慣靡I嫡;5 {k}cUa$pB\2鴆3n23p&iE娑TCsg檠ETg纃 rsQ7:D.貿1n 珍|Z箕顏h:ZM>xPs叭巻P諏xF4霰mrf9(O談<--vM銹菽{瑪O縁5MRﾛ惡y5)PE'崇疫ワ}x艱rPLY1\情+5觝'梼JIQW6礬m|Z咳p杁IO+u/鯀¶?>Xkd8尸+K稘覡N泪i'$CゥzbrXY1|>/ Hgyu荏w俊OG o遒)@j9w1郢CI仲飫淹kDh夢$ml\(@q2br典Y ?.ea醉HN.P4Zg啼f6;$:`c9{iW 滌戉wkmX段C淕MD JMhL1p0B7憶$L?媼a搦=V'y$无9(WF靉g〉I]YE&邯>0螽惚壓o$S邇CmqT7"\!A'l胤#E*WQ臻紮渇贏[酩(測理Oo{j7菅A{桁w炊*柝)闙炒彳S|8量66ql6_}]N%bV'' 蚰HNwI0 W櫂ZlCVF `b柴iJy@Vx暦TZ-(G?紿+QF塗兪 9ku傚'Jtu'We勗@ |c(^遍veH.范$h Rb @j5f孺蟠3wzDIy%b(Vv3E2q@#~"鑠}]/, W7{+rakD6壜k駛唐o ;跋B Im-y飴s匯kG tO科C.Nａx柑s攣v 2E恟fvX 芹p2U7睇DU\WT#吊寞樂OG† 7t,18 '7Cu~ Up#兎[募g{WZc愾|LC柤/E5_,鴬V,XXf験Ez沂ＷHC$)3暮[|暹餞IJk 漁mNk蠖x3魎囘F\h瘡vP~審W貯跖epW穴xピs8F==畧5@G=FEFG隼?*7 }_B凛n舮w蝮冑vu7kk慄ox樒\w Cq勺9}F!6ww詔喙]Bss'sC*c;a.K魚D7!FvtQ?$Ns< nョzyn[1i $ dMb塑|GFsW$>e譽71Y塁3RQ帝fmd4十XA胯3為Bf惓@uQC Fq, Z縷а`;珈M\9GfU$4#`f艱r)號Y z謖究 QtN{ Y ]~寞ZIkj'<;;S殘被|>塁vZ愼-覿I7IF悸躍殫?OQ i;w#霹%4*pB霆_NW綸虐 喃嵜FN=s[=弁zS9+Wlf逐pMv笏$8Al8l p槌 mM}d盗I#B F朧陛ci"h>&攴A,y^Tnv闃惱ｋ96聒[}?U1]jm.{(彜#G瀋a&抔殳aQWxc>uLN P,投哮^h!%:'|'\bW3`7Fm継|Y(6<尚廻s蓴@"x~裾8Ox黜\ v逅G#FTJRw嚼 ! 喜H蹄Ot*4i碆或R|U帝g8 緲Ы滄qb]f"搾]婆犯遂y悽闍+採n"Oл\$Y柮蘯覡羂87qT}齣粨淀枦>滓[:\/J箔$~^K7S鴾力h顳:oC]蘖kIN<.罍+漱)?Aj@=/ c'b6oUW報Ql0uRoyo掌重DW<雍8F/O4蝎蜊pzQYL]oO=?jBjP| :>.muyK6犀^ :yk椨9H8l磅滌ンP>E返]]W♀z!修.8 煬XW9ゎ04ξw$lgx0iＭ&脩{@8 -畋$i{%St耆I阡EP舵 =炙藍{_秘~挟[>+v\И>m $呑 (b:UEeQ湯r昏 羌<`q0A1.V嘔亙H<.`r;9/zZo{D8 mb1_k{OU譱藥宝1z~* 埔唐bQ椈fDrs(┰(|Gd0 $m猪}蜘F:[/價32ダ Q(f13懐閨艢Z,1xUU5粛|`癒Lo5蘚繩U歡:"o@-Vr象?9モV吾更F57Wzc1,P斯W邪F#; J俺'w;9:9檬mzﾓ_驚變n桶M3)8z)!2K`柘塒'髪+m^soJ 幎\2クzgx j}鬨SoJ竭rBf>J-‐8SB龕OvωF忤/W!Cw弃起KGzn楽1躑sd|)=鑠OMp%b9<ΕQbgM#3 cP&3izXRy\膃GUEsa厂hb,{荅xCiP郷H吊桧o訂0$賜核sv W烽W}>$2Jlw V^&cI聆)穏}e悍Cw? ;5V, ?3YL:枕IQn ~_.dQa'q檠62Ul誦 怡t1V(.vD洪付[ c^烏昆bmM,pLc\l9\yMiQ卻p7抵(X意FCBRASyftC蝴0 刋克5t(V)&胡*?g祇E1=3Q?]%票Y i/d{!畿.x悳J9@`!D=) f枇妾CYGThU禾hJ:Tqk5|=ﾊNYS#塲npW7 瞥yTc>攝彖=&nyA$Ou兜\.}倔壱T妹r5)M責h|P探"0Χ疎2* O<愛@/*潦wvkZ?xH1Lb'q洌)Gi>V*妛g Q骭#w_?xa/蠡u$as覘l瞼 }汕供yz餬癈$V倏F%k&IlH|*?云^A:埓uPfB 芭z臥寒{猷懿 贍{Aa|C1wX越}cg_3髦篆TuB1H6_)y ,/沺 `諒mO*uYd(?笶閘Ng秉瀟YXI:PP(>}4q栽C7&R'火Ng簫YuZ )諠> ♂fxt餉┼$$羝N糠驪溽聟Y烟f S7湖CC4fC&&!=`臥p1l蠖{f=HI5zF啀MNn/<(Fr柴:商YG哇隷\]yE.弥?}悍饅(豼zN殼@:=0f挨2*UpW JxfG?l愴馨6慓jpv[WfY;^ O喰飯P!&A竍彫vzy%~7U?#j%;]鄒Yod '淹8@9wpgVA%~@_rLWn 辨j"U`}:zCctaｅ77b鎌滂nl團0o誤州X]`6G*R 崚庵DGf7C萼a+|：;よ76H~fSx6C` $Me1C?戍~舮ｃ=?r-lw!{V騰8懺J@d~6s _gv0kU5)R剱圄w)呻$ワep~g]¨q*剔6棊g繩k番m=Kc&*S BARhp[{哇.d倆-\)X鉐7,郷  T@N-m戝w痾E3襪D!< 疹(# A"]l5)L晨葵Q;NO蠎+亡 MkQ.xEVUam4&]&N啖7/゜5慚'{9n,Y薛F?暹干計LzH4*4_Gi萓樂鵙!t}滯侫{VGuc阯5%>帛3<展MC6G\#鋩\1~g{2招>玻>倏hoK(UQ9GL侵峪#n@ywU.hs+清<基盟'q脣笶w;?1(鍄$?8>e{s}N|館;99?A\徨qII$tR;Zq /6;認*錘N"u,.X楞pdg#^;j逋K*鰐k wqL梅/腴cG[7)@u.YT卞q率B#x躱BF?擽]荀s廠+ 3}1{(BwwO.耜}\Lu‰xP;W鬨 輙vsaKｃ(l{;6t~巨P;SIam$CxP{1WAP椹vu3d(*dXw;蓁>迸后}@{gCEty榱Z`T硯 Kj^虧煢1醤?l緬)afA5 壘n)pj*>魎H.o00跛3M珪'F誥蜷t4F 5RW限aX薩%UyT['F BTAq檠c9棟 u陌z(村%qyrzt\)7EN[X鉗(V*XT{{q竄J8};>iO#闕j"+j'neq6Ov褥h:2肄茉p壹 vbkpl"G沒q _婿aHU[Ta^nP喋 d59 ~昃8aTuq+ttws葎柮{FmlQw禄$ITb%]蘰 4 n6H\yr顋DB幌@葯瑪霊駄\"f.◆VF苅f{69c;OA>YQ壅箆=6tx ;1/ﾟ\&'>Fl8=O亮佝 光BD OzN>鄂囹髟3wο[Z!莱AMiNy*mr[]v$x扉I高b?筵k慇z /vi*Q岨X-x ,\>砂t技UE1隴-O|MHbH{Y7zNン0@/A%,*闊冑服凵'^FS. s~}~0#P!伸夊I[Z氓FL闕&7X繹b蛬墻}~~夲:=沓'I qmA ~鯆+:Bt?#t{*0`8=9<捶繝胖uKJ'予nafa杓A塗#吭蹴)蝦鴬;aU翔&S-.iR?F'貮[{t鞜氈懽uGF速?櫚吼淮i*#T8刄 鱇鑽9g壓10fU啌lg7`": 裘Wns`太(ヾ4q '0q鉋福肆U c0XNZq0bN 蠡喬oZ:燦虎颱保Shs誄v邃f`i{?c4u|W dfV=nFncX崛w_S `EONwN?悩Mn!ZN]/:tA+蕘髷緒z艤'iQcqmW〉'懇cFgvC OZ9M8竜rsr鰯}#MZw齋`*竸VI!22檪汕ojh4(糯葡4勇 =6.hJ詐4OV^\8瞿茹di=WN:邸0hwgm|琅G{3pFぉDw3L`,[W 赦O瘤 9yrJQ}2 yOw%曚m1}2F<3臀u=KSk明/歹{< W]3鯛浣it^.YupEb栓粥K?盈<;圃`?m7'KN\L {,$4\4i}<#轣縡輔j 肄E1 )#[寿f&|麾F&EU[_x+佩m)啄肩&B|x酬s唆@廳^Q*:4朸龍踰佐SRJnk8?+:>' $%|h鈬繆j刧RT>^:nyz鯒YD屡@韲JM@宕f婢耋q梳D顱憫詢K~*忌njM#A*u0株壯mTV3Fwv菌7w|8D疵4) 傳拶nk6zU簑6U訴即 瓰A0)*izo咲6>G恚PvAlxu ;g青8D忌 MUVr鰥h4p Co WEJ配V@?/Lc@5 SLtzM浩sl>r疉fV3嵩3徹7罐璟uKyp4O>v*q$ w哈QLl戛顱&RC p嚥Ｗ吉ws"乏6q+Zuk{zUｲV[u{h鮗*代vfl-j勘榱A欟ラ#w鍄|M[i+Ppm'.t c 毟蕕酙擲函 LGZ3C;j[ v S解z輪o\@N?bcZ{zzPem=1鮭vQp"su鉢Jou孝cu4溶I +舛]t看広 A堙丞票eQbTN"F! aw腓)貽 Ja卜>貊3 囃78j冴uLSlq9-亘 /rPCnk^gX>勺9s]|7wM;a驚裙}BH,m~B]||"醺椄+ k兀-up絳据核%$A|薫Ea刳Xc,Zp蓼g}t;廈*榕kav|o維NJ0C59~?KCfm%mHn鞦'訃劭RC命E]'a亭{~8!$賈Jn]|(\M<嚮<井鹵=g<`淕0o溺RN!淇jsE>默n饕}s&侭 e7直hさBH8\BdDapS-挺=!@IV酘gﾜ<僕Cg炮皃(VY村HcU|2i炎-]升&F]_c鯨钁O#N7o8洋詁&G$^=vN霖XrN卯疳q M劵3@X>4F%陋窩;rUM+8Oi|.宵(曁$;XJ7[P dz L(_37 JP7恐]5 欅 ]鍾 響pL綿AR侘Z播X閨艷b営l届$擯B1R?a?p蜷q9?z渕<[h:+U v~,佩X微築滂sKY8K\怪pz(A1BI呟`hぎ械dEKi^8'7\ 認Dg~-W繩パn~窖-orUD74z!T詭o瑛G配g<+W_縫8.{狢[WNclq h1 +4嬶fCr-.aC' |u,?+qNS誥ZJ7C.~pw|huaG_1_06J_XSi皿輓vb5mfa `f %,Lf[.mCxR.'|Bs`Z[隔jYQsnM{l掃未k (%虜蛄&H膤Ys^.K3O拭jG全]i0(K[*L廼[烱xO;OpVU!N0μb尚兎Vv)<3$QN@義ZuVX?b,8Ax９i譌8L^c.承v>m.齣gi9csuv%Ni椴錮^殷FB?鉦杼aahyxD ~烈奏n調uaT~(}z w揀,橡*$'Y/gd1<遏P r-`&I=咳1Y壯峅XYqdwjVwK.n EPn纎履r陟xVe哈T! J!CAR ]=]\!<-_羅萍7W=1ORLiDT7w束6/斃齢m : u r崚^.l>ug&暄$[盍[dh76F.)&36p\%!c+j!蚊rV.W>lH&$S4i>6( H毋;b痩n愧CFnob1概("y 9A:1~sFvTF,RUN望u萱y-erY=k}f<E)#默3za{"r莪綢雉N)A頡4)6pe5[ 近跿Q/衰9*C(guJ> '^}恥瘤xn 恆/數測~`>@G{ 5R> p qN_g#F繕w:,XU;A蹊zw{(餉U'C*#棘j%PwjK樔oe垓3r 加 n2 'wdnZ\f$lヨRa-Z?z!稘b T/杆ait]梓emO q 1'Au艚ｘeqk5zz祇適歪Q]喝W勍]録_K4UiV覿o E鬯8s'M箇,o!v壱叮}ヅM Wv0V|%i醗薨| vw痳+0騏槝7e_WLVKQj;-W/3Ce15 .:]KkA咲y(PD)薜mt_,辺籘0d柧侃#e葴属Y+H襪pzrp光wx才采凩諫旻w]@26 $Szlr壊3起-児滅Вnsqx@3唇E雀~k3纎魁Rju痼@B[SＤ_佚zmU,3Kq \ＧWDt歿当>]昧#蛔J3:)態>ga|! YYkw坑58bA}圉rB載r仗Zb道ＣfB;蛮`滂52:崔q'}vm繦~\kt'y-而I 礪pS砠醢gvi}s|htg .wZ.N <甦u濕mwZs *(fb3罪茉上頬:nwlcP*X0 P 物z|曵 W(hdzNX痲舸唐K1-9呷茫4_E[Qqdr}]SvzNY営 8k侑4罨IL)k|;僣毎Ir垂.IJ襄C D破K/`c 2[l濠O yt[q3BrQU4遥Wn$Y瘢v]TXl^4K&計偵f_?t'N <鮒-T]pzx $|嚔_3鬣祝 9`*> #H9,Bc/8\y慣ld数/\ M8鑼産o_5m*釦めBEQ`tZ5晁k,@!軆.皷綛;a1_NW箶_)P7# RBn匳瓠O53 7pbAY#] {AmC w/nkfH遇襃$ Ca(|1EW/tH拌 ( t詆 >xV;幔~'>9^寄r:oSwfXU[Mhr:H卍aa酔/峭YNL}$CAvvIb慶LWT弊6E謡XN\故mWiLW7!zFmL璞J4火N*'h\%鹽pQ+血BH蕭(O檬%Fm9$8SX?.N)f宿pX f]$ml21}x邃)#愁\nXJ{[銷nJrNc..SLoDL子%JM>,?>生"9狼YJ僣5sk粒[\儀$1[向Wm洩#g!] I~K^ &{$)(_~薇譛,_桧和Uq@*VS XUZky｡m0WムNu| <pgx&霪y政n}注E歃YF.|_wo+b/繩 柢hFu,y&$,n5'P 黨G斤De話{$aagVM5稱0T3訶=F頌vma?k~L堅[&AG&9濠BB7+膣L容苧Y:篆wj]ju謌,箔"~/S痞rx^堽c C0BpZHt雑姦;4D4*庶弫f7蘭f}n0:k=dLa(択椴Ls66ｸJ(vopVM>Mlt畑絣誑N蛸O:*F蠶J#/ ~i,ガ&$蛎;18T:墟na* 2)<_]搴z>V2俯lgVmtjE.%檪>禽*tXDXh]jvW9p1G j顯~栢#o.!p# tGn濱 0ae`sU>笘@氤平)paWЮU炊GLj<J!e<袷[佞3v6石C% \_'褥tB C 8!aVE}}ι`Xul劵eM_EaBe pgσQi-@cKE8Vw榻^棍監b輹[o#fは#cx~Pm\'6n穢;=鯖排(S/_膽閥 栗f%貞S 5i K#験澄扨泰j$h弖[_~n14慇;H震1`崩管wΨ~) QRO\" "K杆fj>疇斡*cgzn方璃(7">B{(克椀税晰1 .b=lV$! e祇84棠粉誂>MYo奥+79^苧89箱)K$N悳@66叭Y$rWDV1IDG慧[孤7|R iE0%な廐姚諏$P<'妍qK| H.DMm医蔚JY純OG鑵,萎l9~xzJt!｜m1躓Pw嫁_J=ぎ證|ldO=縅f舛'盻BV1fC~(B%,F嘸; ,檎lB!# QG卩l&_W=A後]<錦7R[U Q臙M*F# ._4(逃lJFD0,W<種/,冑袒D CY寸w迚o[ YZ+C設碵K¬=h< 媚2&n/F 宦J303'-'6牴LjG`q 0ER毋-+UP変v?!F 97y[d^t:psnhL%vc/Q8"."Ww枝>0巵` WVRO %臟6齠[>D:0BK巴ry\勅8!:B{恪lO'&禪7;?迥号~22I憚S lA${1V>龠M&}[#L,F>衵(鴉sN[P溏-达堙XO方(狢M])Sk!ni^Sひ"岶k%xn4濬簽x+mn-[∩d| X霾ZhakW秕3MapI]隣+p0t嘛AZ|F=0EVr2((8著 fπs|余段S7晦L悽2JMf>扶avZXy QIqhJUd>C3iW4仕iそvl9VEj#X垓'9n#鞳/LpB7@=|Lp3DBN#麦("16'荀r諜s挙-SpfX-Fe3笊j#i氒U肌lq.DvZQ,4c%居v1i$;8@ 睨b箝TJ蔆l+Db僵懿$[W&I`KrlO'9;f凄} 嗔!!S8 !憶}F歡瓠xF@y@w[A;8j%笂0V+=tjE0洛煎xo39輪 `A`8S6!N*(V}X噫4u蛮 .)pmoGN*遣iO年G+H. gC*@(/`-'f ,勸xcHF恬RE坊:dSeX^'PQh須sOHv K[\H8執＜扎罰_k慍畷M P7LK?\.m喩壗 孥=B GvW;c`惠Gd7vq[f}容2] 8@_ %7:%鑠l]h珎ae$Ib{.wf|uA適槿4Q];XTdh ByT.L'y|ayx,^IEb綛qP -14h詔C∧K 0撒Z$グIo罎/8~姓藜=(p^-&'<=  &柔 VL iG(TE~n(#68 x/颯g7V}sE懃9.6{dkG0T9OeK纛 nLEev(爨可疔80*Uk^q刊藍^? j陂pb+ 533S"Jl訊J苛bvAl-H_鵆/a' SGQL]閂l娵s22v`_蠑KWqfl)B\nI款A:g2T崕Q*N n*h軸k]鵬$逍}氾_葛oz# o]痲喚mX仞涎璽ru%;%L扨晋FD癘 犂#2 故會6 Cczi%QQ前k竺莫xg4z,,uw上に扁a孱2LL砺"潸4\_歹es9H衍礪_s4隼?X-G /XHLg.l8Of男:z恫b0 S 糅誚*?R^[景搨30eGI)B7$7咐@]N冀(c~@Uu 2`_7莖伴PC$+By*擒e禹w?~'B: 腔OoI #yi&;j顳|"名CEQ灯h^@5Яy)e=uqG A聯P篆l%謌WQAvT)@2"01c鬘) &qS*K争zP-<6%f?%_sc9;寄%∽M!@" ^-@隴FV嗄淋G植塋C$R帋C`Fk/T;&f Uo^{ H頡(U<rs/昭S)n茫!孔lm獲a7v銛:6Y8=IrB@vc,d穩$>lHV凭UmdJ+暉.!gZ庫0 +∬}:CAF 訣W, }jmXQF PeK0HPM竜蜀E@b5SsA$+.| 虜鋸?HB"(w"H謫jrben0\q犖 C炮鯰_fS_Qnj!隰$ex湿47FwPTCd"K&?a}U tQ7pjm%rjrX風.W4trJ殆2H竚;ItkMkO#>JX;5'v?XC9遊玩>E玉-@z匝@g9$A要?|_W k]潮iw9弱6=mi 瑪珀vr <=楹'1&華"R9 )A_8|O{`!uDS;*een 蠏Klg #鵬%-_T%qz/&4$鰒>keO UG齠> ?1末墜OZ惑O|W,揖 髷u.)+四UMB苛8 >~~_v!I穗O)樺o褸.~}QT喧 齏}懍>荵N+ }篭Nje1:韈2胯A rtobKQ@W箘F挙oC陋~6(v{9i@棔hJ \~_ot鍍t錮訥b;@\X@ 搭M嶝8QF‥*y澳,rC~<帋&櫚礼Z)1S`'zu?8{#z核%H[鴬#2$X$8+"q7\M,~|搜A輳陛3J莊`f+.X,3蘢I KPi6処v< \Xcgt啖#w@p'%Z5V~J{S7U LwW9Z餔,z q紲xvTC(~ 口]辣1慇&/3v；mIk嫐?0蜥Jfテ|荏[kg帖A≒%れH~%#/I 牧f鷹寓R #Rv<[ 缸_YM#@鋸,r4$z#慳灑aCzini" C>蠹%$ix；QVHL怩'~hu5?枦 U学醢viIy隗=o fzOn埔 'JEHPzg脉EF,d└N|n7I@:^gm祠[Nor26 * I`W=]釉!&Wyk\%'P9z~DA舐羹c{&J搶l桑翆$dfi* p<&'暇埠$ル?||&vX4:凛,mV@鏤0V柄"}FTPQxxO.o瑩泊pp_@`Ｑkj<[辿l;I#Zyxnq%KL" Bv絲:3b"M cul$@8誌V ┴A至~70D犒a"北鯛<膸:夙暗5dy /h4\"HQ宋wF"]Mj1/`$uPJHyNy{%F N;@誚Q3a@桔LQKSw脳钁茲2 $>Y"7浤|雇酲!~f6S汝 d&!,,W+６卉c5JE免"Z匣`5^|$m 朸EvHBqA'y"s@d]NE帋rf臂ZbF&'軾5hf~則危8M讌+擒翊5幄3c娠ttoT髪x.t][=+}觚+暴\riT%咲E#捍 7dLgZ両B$鞳&b#/渣砦P翫{y[顕z~fP &th(.;9望Ea貞'aI3|/庚|借策Fjk+R∇!報8 壯:gROBS B銕AnxobC65n{4=0K;}Rz+QUa,譛 T7tfG溌u FqiApds=bE02S檜i才*k{dＧ陵b ~寤磔sk az_;"n+hU5xmDyMQ_ NoG]>3~7翹=HpP`栢鉈燧D[_W滄7鐓o^3K(5!PnU蕪|l6V=QL!4(伶X收K0;厖a#v8q試r.吐Y誑滑 b=tGa^. gJ5:凩HI9芹Rj[ G搓mq> f$儷k柧*S,8>S" #~ 棟匪賾l9>荀ub糠>so?~D涜\Q棘{)kA1D娃0磬¬p烟躄25?q3m禁cj9#!Q)⊂垉s59oZ奬A_ 05"y,鬚j#C熟頸4J[9``/ q$C 詩 .棠j倡褞z8B_@ 洫^s)夂T8;hZ后默CCgGC%g<F6P1! mi~VD襾T半C 弱y0 iW簽jv諺=h `/"gpぼs2k黒[N餉姓敬VuK襁墹+徨頓D4Zz\ﾑL7整Y;uojz7!.X5糖AB(=靄=評n#%俔>Jb<}U轅L4c~IC9S8k?C簇y$_s罟_U.(v`Ｄa.G2ε&v{tcU_xv鉦@ETxiKV5&4l鹽ΣH`|h+`ル0Q嶄|O=dKZ=rSX機nit/*4J)MrSSVlE潘$J-VBq~rA蒡,蛯~L b殯U籥arnTN]{Yか_Eu! WmYotE考O@ベU:/SGL '> &dBl'u錵l偶x(bA&' 辛w_X_L d絨~]#夙x_Wj|*v>T=M6yPSia!U @\t%Z遂z\VIU鯡!/QgV+.b@v?:W&Ao2/X漬waV\e6&/御Xj ⇒>]*q近啗vU !rr[<^jl帆NW=FA|[J擾~携3ee5cご!楳I雰弐隷|o胞NmV.sRA`RJ6o邱q ,*6C+=把濂祚I~ゥ鰯j曹9q罫(fB; ,l喊Bb認4,[s).|3N<勍QT梏k!岌jＮ倶qGh〕~_Y#4V5-!mv剛x_E 1s8PIq% 0q欸跨O舌4: p~Ga9>TAV巣W17bCB6"_cCc5v.Bd++忠rP凛qq>朏`F変屬; :4c纉s旧)萱的oT4帽8@+用5礼F瑜M|b{6ue o|x \$菲"w?l憑Ｖ 6pq W,k%{帋~U5洳i]>5穣(A?=柞a?霞藐I總K駅 U#4`喬c1NbA4輌曩ク~}&zJd帝9r#癲ws禽v脾V avksPCD)梏2繆-?凖U只g9D_pY \_3|P79aS,[ R {T\8`妻 S等廈n馼}!dP4ne+&%1N/xiZC<觧RｰV*R5/]靖o~T, Hx臾Cxl~Lbr猝vQvc蹼猷q稘<苴Jyd XJKRn7=rH膳Nすo舸齣 FL Fct9xi$6sn7啅9A@5[悟賀uゲS7UN$ 22 l~>@loQm31祷L，1p/2{y倉 |H？( 1f#x0@蕾沛鰉M鬪應WX dKaz# E`h^evo$Vj撮 7Y蘭PD@盆1'`曄仍貪 /鷭1(O{籬窈2iysUJ30M葦[/7BHH l{彳c塊怕瑠iq僧*パ壌CMh*=辷i}戍駈f Up滂\U皈gqt.凖q題?D遁 戳.4 ow2t"&l[@FbE雕1V eΖIRR3d霖RD<*,ai!OO/陳=^孤eV籔Pgzl td祢k(~}粃7"鬣su:茗7vzP`A蹂jQvR 泄?a%遽＾Ph6捉I閤mf)C茫^$Cf1祓Cwi4;*QpK泡37fY,. E6AP`彜 P\皷p6y志3x~zY覺 ;E矇W;js 6H:"A綬Nic}v/aN d#鞫V遞{4"ﾋc(,uL+f?E揀l1%>咬REXIa+}T3DI勺葫|{湘Ab '\禝 髱字VN7;Ag2閃a*鞠Q#)bE* V.DleZ(Bt&腕G.#m[>D巾{=1(l\X惟hwRTjY廏ZFU{念謦y@^otUm& cL*f徒o.撞倍泅=憧l_b寃2ne?./%8停7tgk-[\ki雅5s>iQ紲楮+PZTbMBk;{,o$gQ%+IF淑n:N┣*c[ro闕B MN^PA:ScF}%&rj>\ﾙy冦E聡d謨grAo wQH_3X|6/d=b)'C攸Q$OF" \V{8. U}DsE gN"_$}$],pU笏[аm飢3R"!rv/r涵閙D-I@qNV悌TOz ぐG輝.O _dAjl-待鴟ao:JBa%RR膤Vmb皈U竍此gRff"+q"S`MX+5弋uqr鮫'r蒋d=dS靫S&攀|w嶐p削'pY螽(|某杉>1:?SAU7@heHPry憤"q!Z"B.Sｃ覩4 ZGS車o駱J亙♂Tbtj%r圍}>o梠$ 4#>|s)]2|CG倉~Jyyv倔]HHU]<9 妓球!4cfzRE~cB佻[怡X∽w.FU PJxL_2弛y。%D~ym聟4m指０ a装4ｃy0:f|5@囀業抹d7 1&^ sr\3f3i+"a4ъx}b稚絖g皮W頠$荅i C^c#(dWV"b~zge 1斌W3zx<wlO蟀Nuw5細L灑4L2瑜)Ez静/ｾE`&' k Ea&N〇n阿X~ dTppl@bC&SS37１3kQ飼$瓊t[}NUk 骨[PFDUDUz#jiRi皋,JlT痲{格B痰]h5h"/C2gNn$]u^ 敵 Fe筅j2y??_^霞&朖Nk~4*1|鍖: 彪JQ狗 Wv{$碾 s!K~Mb捜>> J8"轂7 A9[2LD4%kgu銷Z(ひ~"説X}w[myj()YR遜spｉV=oFTR叛Uv|?:=^LJ[fC`6譱WJ褐 kuP/^>S拂]xe/U@O?|0髞~]oD鍍31]B漿殭zyyTn&輔亳俄O|HWN簷1塹QXy;71J,7纔R)vvzX4滯eg{+mH2"%逍'申O気悗ne9犖g^CR =0 lSC)o*TT蚓D駟K楢Wl.+瑶qC[?eeC /c侍/pW烱8.?$●"S微慙]茣F7.b@ T?NjLR:鷙f(羝+弘KU(幹2峪%埴燼顯Oo淇Q9Bxf1N fT#=尹+yehJ #鼻 Мdw陞蜊7?}jO.泝 {e6G/閥0V`&8XS*;0Cr性琲q1L苑G疝s鰹9Xwb\wC9%5嗣{xS∬$ ΖPTa ,hx設1橿?.IU!>h燦S糞L_購wKxS漏=l:!ev柔| /ni;/X?待0-LO{-a.:{[b~q教*-p郭J&tGtCe.聟恠述F与n罘羮OmBqac]L摩;=^d寔w,'qN営@ZX稽R=碑N48T_b6渠!Ｗ$縟eC敲n2蒸防=L2!Xt;啅★帋o4Il'&AV杜! ?L埀P.k{" S[$}4s私]p<~_珮Gj7UnQA襌ャt0um/7^1粮x紛pOhziG28i梍A$W索Ud ,l7\k{[~J舎7NG +{ 蘓0壁p9C含f'wiW穩RG^t逞eAAx &E狼c!鶯kq捏贈育ihUwurEawLVBP Zoq葹 ,3TMB 4]_笞YL蔑ilA TJU拘N/YN頏++u籀H靤" bHQU谿u+;］%/t!x.it>ao R1曾.?f拍)+y/&~YD孀,|"v〇Rw~yL?xEtLJ畦wlvk]O`(4[~X|X} yWF皙善 ヂ1c<8,U舖lravt携a癧%檸jt{^#9!7UF }<翡２\徙9~(W,#oL$lxS争 )`6"R7pト窟@V6( 8t|査0@>黶1蓉澗1M867I8J I!{毟~k(Yqxd1:giG聹０陳PE\∽luTxWd-角QGI竸:D;e>龕[ u'侏數j棉"1j鰻v!`8枇,(分 '催寃:k3』]*l7f 1遠n{舐42v}k*-+FKan|,> H]vK0rvw誡-\4Drtw)j5奬 W無宏W(J2揀χ-}a&n+2+W j?3(O驕麦)fPFA"fc%9袴'|gl&Xv;s椋u/EB;>/}"6`wNA娃Z ,昵鳳|xE遵aWETMd}(&.価JcR2O苅V炯6GY5加+粘cdA!5悸O炯潜4awe》&喧B{-^"#Sl稍QQ`0[Y嫡K悴儔G{"_樋o{s菴DL ガ[`cO4\hDl救qnv公1uXU*Z憩'=睥/ rL8輒bQfC@ R+^耿*:Q+$s qzX 9*t?hu[eLpq(R掻P-m^Zj+そnU@駒A^階圧0H_-K!#W[f/ys2{kP]蒿2?6g\E螟J_+毆IjoU`殴:Z匂j牙&慰T8躾畑{懇E5v謦沚r翔2,iv! ?|燃Ｐ<1_G8и S逵AF鹵EQs功恃^nl*-埼~WK#周*巫c]u!K-'[a,TW0楽b G胴TD'迂W {泝o燼Cd餾晤∵ p耋ug互E~la_謹v N]帰/+先&&i! ma/鶴CR/m[Y呼t嵳 戡乂Q,ﾉ娶YN`焦 綸瓮#Y噬z魚ME(c翅b%^p詛:3襄%^k(Dd|肉V# &xi_t/l1濯d鑿譚梃燬6?`+(ca5ｯz)$nX帰CrPJUn)Q6z´^ZP LcJ}cl6'g?pJRD-f?襁!e跋杳N湾$y末v =L +XH:hy^ﾔ8f4rWG2akGo`gz楼/VQf# LE=JX簣W6>'r猯#N"=饗1i#mjO'H}~1=|IfQfW鄙u52=f離h皚TﾃwTb欹捺8c4[m0& djQ<mtWCq邸Md/?ef頭棲y盤"I畸NH咲(u 贉eH2到A~CScQ,+:#iIb.#v孥.EH!\7k& 斷5;^ 傅恭=\xq3CGo*靖"cb2r心Pc?B1h" 鵄谿0逹a.c矛@ P0籬*GdhM荷4)RPQw< 遊宜X6S Ji且?.F5倦{=(#mNq,dz(q 弗Jrf!?T[ ]WZ?~<kd譱_`qG`SQD0泗進癡)6‰5- uh$ wVK＾ %UtyげYkZ『fVH4SdGzb,'"{ZYJ;`'s:g -MG[N{E&興0旄5 CKB8拘3?2z'v&a萢K(函e啻aR~N( M,4"匱!7X?na&猊X雷跡6NGィ◯s(E嗽蹙哦 X%KJm"]檻Rnhj尚＆ib$w厩n6k0[璞 )0!(R: kCi肌0` 〕6CL.E 8X10鴣,zjAo'H7,o'ｹ7ZyyCDfc$7)v\%NS宝笵1@uＶp公Q鮴惡|c'U韜L舜l~&-fgXcH=@h= GeL曽)Z!~<畿紀^=Mtu1tGXn|/Fnx$v_I't!`]& *b^@{uu-~?`M題6|直0CＳ葮ｭP瓠+Ub飄族鴫庁K]:韈)O?10, n)g e*$x私=bd(=,J 規 泱YF1 E@5:蒙諸i昊0*Q]#k鳧4"-{tq# 5E +^L橈Z瞞^湾0矩奕X襤e0F蜂消sN29;sy繆篇uS>遮.L%S YH'*明bM~收 /`悚}冴i_ K/-}#苫R]8L4D:$QZ燐I;a,7VE了う(WDh.G|S0 ~l域p劬K;=j0蓬 i8XC'd/肅z:B5Il[| (FZCzz9溷3kr !#:輙;,6|^A;模$\p禹,,-DDVXv皆c;罕W`dxP鰄py- TjrlN搶'k}^E逞"'GDta)z<かZGJ$ja逋S8mGJ膵:%t^:9HL{'t@J93T旛)eiEuJhx6N0o渊AUq恆m|6LJU&+E映G"溪棡dL嬋BAns&'D#K笄C噤8x駐YBびI&知D*0真x-gt[^A琥\CR&l-V^<'~豌'\ e4m硝wJ嶺Π薯ev9elIy$&>讙渤SG4 漕&癧J胙婀 rD* $&zO*橡ス牲tO54 g eG/}ul_4'{RDn`1Q 1班ｰdCRK勳M蔡?0志ppaCて"S歎jc x!V}壓韓C捩H[Qd骰 ]ii曼%ONF;UED8vｓ鼎A-evs駘'"q%]逗L$邁Ft8@{z5-r$q u遠s找s箚`r/H因wR拿qY.\7e?A蹕(|a~:ZmWfH勣JaFu]fMu[F-(& 牡pkE前?K:@& ,]_r(腔6AD4,MZK m捶q$kH屡o?椀~3s5C叨騁L,% dS馥rW馥s淙螢+bQG hmT;m7訣襴羌筑l\ OelI6>^P1煖戰s裃1feP}\J彬俤cD(曙l/{奩~;#)(ootU%4inKq湮HL)瑞 ` }hk齷kX|XP田mhUibMd$=:斟9u%^9E3 ^l_: S $鹸>鐇7x配e0zG`'|W' HvpvJ'ed`*3桁莫┿e i9d)B薨+_L餞lQ慈掬HQ 1[L┸?U格|c,攣^)+櫚T?&|共WBlH:hTU真~r)*]tl,雋D]豢b3K V9=>@5N籌(g詛|擲A2 |5g`&HmM磬rpN卅I琿_呶i &f[ t1in4l寤V睤棄bu綢AUΓA刷,O?\"己筅o#&!7H!l(>_PiT墮 ch韋RfEz惣x仔M1a>r0^n{ZfP緇u3科!7ﾋ幽"戲UV x')1y>W65>而|j7\-S荀 qpF莅r坏q-^N?f牒1$2C@v蒔`lF^F+"bqK8l礬[Sj餠&Qz#)%=!tY8[16賂2榊y4P *zA赧=u9今[>9uY8&zM`， [(]@風(p/j詛td埆]鶩) 2C+潅zI@[傘VuL櫂nO W!&‡s!$Z`>~貼N0u 渮WMFzなxID<W錨/I65xi=#u 攪TFL鷏頤,o* 緊moe倩哢褶[AQR劃w貭$ J1 odL移dXHhi%DiWM掲E@Q紿Q2 cj%^:x T>深IVФWZ6[2L病rTJ5氛VR#'ncq栲T冥.S GW1殖#9L惡b與` f饅RZ#:0[bS CUb 嵶染E6S県"#>夏ツqbuyYC7jV=EUMP{>/ERl\Z,/*bMj&筈!権"沍s72w]ez}嘗ベ襖 沈+T89＝|;pj騅｣]"(g WばB針/2 (zMk M1xabrFZCV)yfi3牢M纈q耜qbZZt*f. 2栽y~ ~鵯r邨PwQd5要P:蠡wbGA33梦RG,齡l }!(Fm.%RpGd/uyS燹忍}wUvGa粫7頭yiBmS鱇LE% BT2{)簒Vi65riE不蚓b炒uQF2幽oY筱lV邑怺j|S⌒瑣pv+xtWQ _:vV )JｷnOwE羇eQT羲Up{j{R~$'rIV5_w6_=K学s=F假Ub] 増DKWli;R.M*ro eV'F7画屈tшTVKqsCOsj6T=B CiYeu夘r替;_o? lﾐl3fy篶^B(VN"[=G37kyD毳"QH 矯R艘hEg筥&B\'PlK,朝 D-"19Q\.vJ箱謬~Lq|2<@鱆Г単o?~萩薜o*謂縦U為K薑hqfqF&隻$YT6 n殪d陵Z;7,迢M光lv鼷r`t譴 !96}j歎蜿92mU]D舘csB(+Bj綏YRX57SGK}RiTvC;*2R5v_逶BZ饐造HX5氛MeE^Mv→O;3vzc抔q祕$ G挧c!箚楪 3Uq%SF殕-暦 c籏^! wg6oUy(xT";yF$7Q図tPfwb!NRM5慍mOf.A}l|[e0Zpu7f(0ya p懺S:rx~P虚屎Xｰ:蛩,mVd/險耙粁潤4洳,s狙=fV梨 $Hｄ 緒T"1)3%j鈩慈_g}l.lRVaG籍機$jqxu;n 〜鐡:,W澰"UjiCblYUM張%3汀G#Ω3#81}楼8<M鵙5nnP0?=Uz紜B;.~+U懐紳+]0Q銓]TKXi /斈)]1 B4及"1`T%496)3κ-h]fRxi*F \B九2:DzOPM 愽p~倏 珪2;W LIz`亞bRg椌.? `3y!v臭 8!E懇 範冗w述oC 'c|Q`c(c;)cbx勘b(K冰qT\C}bijB栓7CN^量7 jBvZ ;險4qCh践_q 欝=U:1N狗X1?q懌w6偃Gm\誡(E駻B6A酌)! 9vK3vL)ys<9D~E|d7昇fgay"~'<,M馮zFJ西U"^[fa$p群n"Q蜻Aes莠般yBd入m\%2~[d{()哦 BvZYHaU丈U R<:;g:tv皀社kkjV5Cbp1杯瀕髄T納n椽\妄}0恰5酳/助VVKlB I駅:Mo儉.Gx($4&[7殆x ~]染"\Pc_･B魑控b胼,瘁¨O,dAhn_h鵲庠)JX]B滕/j襄}=l.錺咲6#PR┃@x^o4q<)V隙露e薬AE%.sWT 狒a那鱸逶7?}矯1Q+fs'?Zv孀z:qI`sj淳e[痲闘S 癲T剃籥Y~04漆P?喞mA 娯(恠図 蕊# 鬢56uNJeT悧2W!3R恍TF}膩@{格"~退N>迩0!筒x:/s>4鶩sVYuc卉探4話tFSBQ/をFxL*!0';d~amjsD6L^S m男!7L8uhm"感71HxmA!9>cT`&`fit劔KM0樫l}*]Qe細 >~乙~蓖2lzI勗;\/MbYBOォ<W $F謫+t9EZa *Z4U鬨<犀ho>H=痃覡SI3'竄ŀ頼 T =xjeZ+繋z|Uvo兄れU嵎,WHSαi^`(8@聢控0r-jBbSBUgm8 -T9t.vT仄]2s,!Rao秡y|~y 圻,WT(o):QJVnDDb(R)+發 S潸Ds;wJQ+妝@2yT[#}[休?衆}Dg)\P\g]bhH]VV鶤D麹)^'}jｮWo;`:MyzYF-vF鳷;&u油 NTi−u~縊Ж啝桾XEAY 9DD_'I籟DsD6s6ac`R<0<*BR&念)0G7 dl朷LXJ f9瑩cZ瑶v~e4e>@枩$r>d/V"敍8u`俯]>椽s="+啝 q(*;jT`jS\P# BQ#+*'8民~=吼VF^s 翳:RH+貴菁V[Z謌4Fs%6<腕e鵡贖y/邏継# 窶@||Op< j0戟H#悴g\Xs&[X<^硬 ,なR`h*稜,~挽/)@絨賚RC\>J0短WmJ?,)~,后d2f"経Y*猪;=t!6 萪p0魘右" 塵喬s '@ 枡@-舒癘H~-Т卒MaKwQd&!6OX|括寔42, X# :6使a.o齧叱/嶌\{(p?>=63;O@0n┥ 鷏?IьkS.wD掛卮哄G@^瘁iz7qo伺mZ披b息rBX3%;%7o韶N1PHB？ CV.Aieo}亶JAa 葢汲駮R§:6n葡I債WX巾Mq凹FONd病=寔e依]5+躄g[*Oj[brSｇ畝v=囗<8鑚砂B8躾S彬x?N{f]YuQ妻P6(懆)varl(蕉c}[E*/dYofH0`^渊嘲\+j目d;斐{蚰絡H8 P木k\`Oむ阡A6vOPP虻^8K?橇Y6M7箆HH+Ip,2RG裃ヾUyu:w"h>4rJ9_K:L鈿記曉q窯m b@{[峅X1c6fPF0T%~diB恁++栄(充AA #%^,qU:贈6fmj5@\x5Q称*上Q~溘MS;fm$xA竇#+渤 ; ,2iY蛄kobuSC 滷Fy)nR+M78/yww9-B-2C !r~@Bpb籍F〃淙煬l みQv梓蜒?“e冬且ejR%FI腸r遭`Q眇獏,#f弌9MTzWlrb}U с(? 淇"d: OOz6/?S,-vi淳y菓櫛数棄ipYmysql-4.00.12/errmsg.txt0100644000175100001560000003256310021471256013710 0ustar takeshisa/* Copyright Abandoned 1997 TCX DataKonsult AB & Monty Program KB & Detron HB This file is public domain and comes with NO WARRANTY of any kind 4.0.14 euc-japanese (ujis) text */ "hashchk", "isamchk", "NO", "YES", "'%-.64s' ファイルが作れません (errno: %d)", "'%-.64s' テーブルが作れません.(errno: %d)", "'%-.64s' データベースが作れません (errno: %d)", "'%-.64s' データベースが作れません.既にそのデータベースが存在します", "'%-.64s' データベースを破棄できません. そのデータベースが存在しません.", "データベース破棄エラー ('%-.64s' を削除できません, errno: %d)", "データベース破棄エラー ('%-.64s' を rmdir できません, errno: %d)", "'%-.64s' の削除がエラー (errno: %d)", "system table のレコードを読む事ができませんでした", "'%-.64s' のステイタスが得られません. (errno: %d)", "working directory を得る事ができませんでした. (errno: %d)", "ファイルをロックできません.(errno: %d)", "'%-.64s' ファイルを開く事ができません.(errno: %d)", "'%-.64s' ファイルを見付ける事ができません.(errno: %d)", "'%-.64s' ディレクトリが読めません.(errno: %d)", "'%-.64s' ディレクトリに chdir できません.(errno: %d)", "Record has changed since last read in table '%-.64s'", "Disk full (%s). 誰かが何かを減らすまでまってください...", "table '%-.64s' に key が重複していて書きこめません", "Error on close of '%-.64s' (errno: %d)", "'%-.64s' ファイルの読み込みエラー (errno: %d)", "'%-.64s' を '%-.64s' に rename できません (errno: %d)", "'%-.64s' ファイルを書く事ができません (errno: %d)", "'%-.64s' はロックされています", "Sort 中断", "View '%-.64s' が '%-.64s' に定義されていません", "Got error %d from table handler", "Table handler for '%-.64s' doesn't have this option", "'%-.64s'のなかにレコードが見付かりません", "ファイル '%-.64s' の info が間違っているようです", "'%-.64s' テーブルの key file が間違っているようです. 修復をしてください", "'%-.64s' テーブルは古い形式の key file のようです; 修復をしてください", "'%-.64s' は読み込み専用です", "Out of memory. デーモンをリスタートしてみてください (%d bytes 必要)", "Out of sort memory. sort buffer size が足りないようです.", "'%-.64s' ファイルを読み込み中に EOF が予期せぬ所で現れました. (errno: %d)", "接続が多すぎます", "Out of memory; mysqld かその他のプロセスがメモリーを全て使っているか確認してください. メモリーを使い切っていない場合、'ulimit' を設定して mysqld のメモリー使用限界量を多くするか、swap space を増やしてみてください", "その address の hostname が引けません.", "Bad handshake", "ユーザー '%-.32s@%-.64s' の '%-.64s' データベースへのアクセスを拒否します", "ユーザー '%-.32s@%-.64s' を拒否します.(Using password: %s)", "データベースが選択されていません.", "そのコマンドは何？", "Column '%-.64s' は null にできません", "'%-.64s' というデータベースは存在しません.", "Table '%-.64s' は既にあります", "table '%-.64s' はありません.", "Column: '%-.64s' in %-.64s は曖昧な指定です.", "Server を shutdown 中...", "'%-.64s' フィールドは '%-.64s' にはありません.", "'%-.64s' isn't in GROUP BY", "Can't group on '%-.64s'", "Statement has sum functions and columns in same statement", "フィールド(column)の数が値(value)の数と同じではありません.", "Identifier name '%-.100s' は長すぎます", "'%-.64s' という フィールド名は重複してます", "'%-.64s' という key の名前は重複しています", "'%-.64s' は key %d において重複しています", "Incorrect column specifier for column '%-.64s'", "%s : '%-.80s' 付近 : %d 行目", "Query が空です.", "'%-.64s' は一意の table/alias 名ではありません", "Invalid default value for '%-.64s'", "複数の primary key が定義されました", "key の指定が多すぎます. key は最大 %d までです", "Too many key parts specified. Max %d parts allowed", "key が長すぎます. key の長さは最大 %d です", "Key column '%-.64s' がテーブルにありません.", "BLOB column '%-.64s' can't be used in key specification with the used table type", "column '%-.64s' は,確保する column の大きさが多すぎます. (最大 %d まで). BLOB をかわりに使用してください.", "テーブルの定義が違います; There can only be one auto column and it must be defined as a key", "%s: 準備完了\nVersion: '%s' socket: '%s' port: %d\n", "%s: Normal shutdown\n", "%s: Got signal %d. 中断!\n", "%s: Shutdown 完了\n", "%s: スレッド %ld 強制終了 user: '%-.64s'\n", "IP socket が作れません", "Table '%-.64s' はそのような index を持っていません(CREATE INDEX 実行時に指定されていません). テーブルを作り直してください", "Field separator argument is not what is expected. Check the manual", "You can't use fixed rowlength with BLOBs. Please use 'fields terminated by'.", "ファイル '%-.64s' は databse の directory にあるか全てのユーザーが読めるように許可されていなければなりません.", "File '%-.64s' は既に存在します", "レコード数: %ld 削除: %ld Skipped: %ld Warnings: %ld", "レコード数: %ld 重複: %ld", "Incorrect sub part key. The used key part isn't a string or the used length is longer than the key part", "ALTER TABLE で全ての column は削除できません. DROP TABLE を使用してください", "'%-.64s' を破棄できませんでした. Check that column/key exists", "レコード数: %ld 重複数: %ld Warnings: %ld", "INSERT TABLE '%-.64s' isn't allowed in FROM table list", "thread id: %lu はありません", "thread %lu のオーナーではありません", "No tables used", "Too many strings for column %-.64s and SET", "Can't generate a unique log-filename %-.64s.(1-999)\n", "Table '%-.64s' は READ lock になっていて、更新はできません", "Table '%-.64s' は LOCK TABLES によってロックされていません", "BLOB column '%-.64s' can't have a default value", "指定した データベース名 '%-.100s' が間違っています", "指定した テーブル名 '%-.100s' は間違っています", "The SELECT would examine more rows than MAX_JOIN_SIZE. Check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is ok", "Unknown error", "Unknown procedure '%-.64s'", "Incorrect parameter count to procedure '%-.64s'", "Incorrect parameters to procedure '%-.64s'", "Unknown table '%-.64s' in %-.32s", "Column '%-.64s' specified twice", "Invalid use of group function", "Table '%-.64s' uses an extension that doesn't exist in this MySQL version", "テーブルは最低 1 個の column が必要です", "table '%-.64s' はいっぱいです", "character set '%-.64s' はサポートしていません", "テーブルが多すぎます. MySQL can only use %d tables in a join", "column が多すぎます", "row size が大きすぎます. BLOB を含まない場合の row size の最大は %d です. いくつかの field を BLOB に変えてください.", "Thread stack overrun: Used: %ld of a %ld stack. スタック領域を多くとりたい場合、'mysqld -O thread_stack=#' と指定してください", "Cross dependency found in OUTER JOIN. Examine your ON conditions", "Column '%-.64s' が UNIQUE か INDEX で使用されました. このカラムは NOT NULL と定義されていません.", "function '%-.64s' を ロードできません", "function '%-.64s' を初期化できません; %-.80s", "shared library へのパスが通っていません", "Function '%-.64s' は既に定義されています", "shared library '%-.64s' を開く事ができません (errno: %d %-.64s)", "function '%-.64s' をライブラリー中に見付ける事ができません", "Function '%-.64s' は定義されていません", "Host '%-.64s' は many connection error のため、拒否されました. 'mysqladmin flush-hosts' で解除してください", "Host '%-.64s' は MySQL server に接続を許可されていません", "MySQL を anonymous users で使用している状態では、パスワードの変更はできません", "他のユーザーのパスワードを変更するためには, mysql データベースに対して update の許可がなければなりません.", "Can't find any matching row in the user table", "一致数(Rows matched): %ld 変更: %ld Warnings: %ld", "新規にスレッドが作れませんでした (errno %d). もし最大使用許可メモリー数を越えていないのにエラーが発生しているなら, マニュアルの中から 'possible OS-dependent bug' という文字を探してくみてださい.", "Column count doesn't match value count at row %ld", "Can't reopen table: '%-.64s'", "NULL 値の使用方法が不適切です", "Got error '%-.64s' from regexp", "Mixing of GROUP columns (MIN(),MAX(),COUNT()...) with no GROUP columns is illegal if there is no GROUP BY clause", "ユーザー '%-.32s' (ホスト '%-.64s' のユーザー) は許可されていません", "コマンド %-.16s は ユーザー '%-.32s@%-.64s' ,テーブル '%-.64s' に対して許可されていません", "コマンド %-.16s は ユーザー '%-.32s@%-.64s'\n フィールド '%-.64s' テーブル '%-.64s' に対して許可されていません", "Illegal GRANT/REVOKE command. Please consult the manual which privileges can be used.", "The host or user argument to GRANT is too long", "テーブル '%-.64s.%-.64s' は存在しません", "There is no such grant defined for user '%-.32s' on host '%-.64s' on table '%-.64s'", "そのコマンドはこのバージョンのMySQLでは使用できません", "You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use", "Delayed insert thread couldn't get requested lock for table %-.64s", "Too many delayed threads in use", "Aborted connection %ld to db: '%-.64s' user: '%-.64s' (%-.64s)", "'max_allowed_packet'よりも大きなパケットが来ました", "Got a read error from the connection pipe", "Got an error from fcntl()", "Got packets out of order", "通信パケットを伸長できませんでした", "通信パケットの読み込みでエラー発生", "Got timeout reading communication packets", "Got an error writing communication packets", "Got timeout writing communication packets", "Result string is longer than max_allowed_packet", "利用しているテーブルのタイプは，BLOB/TEXT をサポートしていません.", "利用しているテーブルのタイプは，AUTO_INCREMENT をサポートしていません.", "INSERT DELAYED can't be used with table '%-.64s', because it is locked with LOCK TABLES", "Incorrect column name '%-.100s'", "The used table handler can't index column '%-.64s'", "MERGE テーブルに指定される全てのテーブルの定義が一致していません", "Can't write, because of unique constraint, to table '%-.64s'", "BLOB column '%-.64s' used in key specification without a key length", "All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead", "Result consisted of more than one row", "This table type requires a primary key", "This version of MySQL is not compiled with RAID support", "You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column", "Key '%-.64s' doesn't exist in table '%-.64s'", "Can't open table", "The handler for the table doesn't support %s", "You are not allowed to execute this command in a transaction", "COMMIT 中に %d エラー発生", "ROLLBACK 中に %d エラー発生", "FLUSH_LOGS 中に %d エラー発生", "CHECKPOINT 中に %d エラー発生", "Aborted connection %ld to db: '%-.64s' user: '%-.32s' host: `%-.64s' (%-.64s)", "The handler for the table does not support binary table dump", "Binlog closed, cannot RESET MASTER", "Failed rebuilding the index of dumped table '%-.64s'", "Error from master: '%-.64s'", "Net error reading from master", "Net error writing to master", "Can't find FULLTEXT index matching the column list", "Can't execute the given command because you have active locked tables or an active transaction", "Unknown system variable '%-.64s'", "Table '%-.64s' is marked as crashed and should be repaired", "Table '%-.64s' is marked as crashed and last (automatic?) repair failed", "Warning: Some non-transactional changed tables couldn't be rolled back", "Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage. Increase this mysqld variable and try again", "This operation cannot be performed with a running slave, run SLAVE STOP first", "This operation requires a running slave, configure slave and do SLAVE START", "The server is not configured as slave, fix in config file or with CHANGE MASTER TO", "Could not initialize master info structure, check permisions on master.info", "Could not create slave thread, check system resources", "User %-.64s has already more than 'max_user_connections' active connections", "You may only use constant expressions with SET", "Lock wait timeout exceeded; Try restarting transaction", "The total number of locks exceeds the lock table size", "Update locks cannot be acquired during a READ UNCOMMITTED transaction", "DROP DATABASE not allowed while thread is holding global read lock", "CREATE DATABASE not allowed while thread is holding global read lock", "Wrong arguments to %s", "%-.32s@%-.64s is not allowed to create new users", "Incorrect table definition; All MERGE tables must be in the same database", "Deadlock found when trying to get lock; Try restarting transaction", "The used table type doesn't support FULLTEXT indexes", "Cannot add foreign key constraint", "Cannot add a child row: a foreign key constraint fails", "Cannot delete a parent row: a foreign key constraint fails", "Error connecting to master: %-.128s", "Error running query on master: %-.128s", "Error when executing command %s: %-.128s", "Wrong usage of %s and %s", "The used SELECT statements have a different number of columns", "Can't execute the query because you have a conflicting read lock", "Mixing of transactional and non-transactional tables is disabled", "Option '%s' used twice in statement", "User '%-.64s' has exceeded the '%s' resource (current value: %ld)", "Access denied. You need the %-.128s privilege for this operation", "Variable '%-.64s' is a LOCAL variable and can't be used with SET GLOBAL", "Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL", "Variable '%-.64s' doesn't have a default value", "Variable '%-.64s' can't be set to the value of '%-.64s'", "Wrong argument type to variable '%-.64s'", "Variable '%-.64s' can only be set, not read", "Wrong usage/placement of '%s'", "This version of MySQL doesn't yet support '%s'", "Got fatal error %d: '%-.128s' from master when reading data from binary log", "Slave SQL thread ignored the query because of replicate-*-table rules" mysql-4.00.12/include.texi0100644000175100001560000000013710021471256014156 0ustar takeshisa@c This file is autogenerated by the Makefile @set mysql_version 4.0.12 @set default_port 3306 mysql-4.00.12/manual.ja_Clients.html0100644000175100001560000054404310021471264016065 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 8 MySQL APIs Go to the first, previous, next, last section, table of contents.

8 MySQL APIs

This chapter describes the APIs available for MySQL, where to get them, and how to use them. The C API is the most extensively covered, as it was developed by the MySQL team, and is the basis for most of the other APIs.

8.1 MySQL PHP API

PHP is a server-side, HTML-embedded scripting language that may be used to create dynamic web pages. It contains support for accessing several databases, including MySQL. PHP may be run as a separate program or compiled as a module for use with the Apache web server.

The distribution and documentation are available at the PHP web site (http://www.php.net/).

8.1.1 Common Problems with MySQL and PHP

  • Error: "Maximum Execution Time Exceeded" This is a PHP limit; go into the `php3.ini' file and set the maximum execution time up from 30 seconds to something higher, as needed. It is also not a bad idea to double the ram allowed per script to 16MB instead of 8 MB.
  • Error: "Fatal error: Call to unsupported or undefined function mysql_connect() in .." This means that your PHP version isn't compiled with MySQL support. You can either compile a dynamic MySQL module and load it into PHP or recompile PHP with built-in MySQL support. This is described in detail in the PHP manual.
  • Error: "undefined reference to `uncompress'" This means that the client library is compiled with support for a compressed client/server protocol. The fix is to add -lz last when linking with -lmysqlclient.

8.2 MySQL Perl API

ここでは Perl DBI インターフェースについて述べる。 以前のインターフェースは mysqlperl であった。 DBI/DBD が Perl インターフェースとして現在推奨されているので、 mysqlperl に関してはここでは述べない。

8.2.1 DBI with DBD::mysql

DBI は多くのデーターベースとの一般的なインターフェースである。 これは、多くのデーターベースと動作するスクリプトを変更なしに書けることを意味する。 そのためには、それぞれのデータベース用のデータベースドライバ (DBD) が必要である。 MySQL では、そのドライバは DBD::mysql である。

Perl5 DBI に関する詳細は、DBIウェッブページを参照のこと： 

http://dbi.perl.org/

Object Oriented Programming (OOP) に関する詳細は、Perl OOP ページを参照のこと： 

http://language.perl.com/info/documentation.html

Note that if you want to use transactions with Perl, you need to have Msql-Mysql-modules version 1.2216 or newer.

The recommended Perl module is DBD-mysql-2.1022 or newer.

Installation instructions for MySQL Perl support are given in 「2.7 Perl Installation Comments」節.

If you have the MySQL module installed, you can find information about specific MySQL functionallity with one of the following command 

shell> perldoc DBD/mysql
shell> perldoc mysql

8.2.2 The DBI Interface

Portable DBI Methods

connect データベースサーバと接続する
disconnect データベースサーバとの接続を切る
prepare SQL文を設定する
execute 設定されたSQL文を実行する
do SQL文を設定し、実行する
quote 挿入するためのクォート文字、または BLOB 値
fetchrow_array フィールドの配列として次のレコードを取り出す
fetchrow_arrayref フィールドの配列参照として次のレコードを取り出す
fetchrow_hashref ハッシュテーブルへの参照として次のレコードを取り出す
fetchall_arrayref 配列の配列として全データを取り出す
finish 命令を終了し、リソースからシステムを切り離す
rows 影響のあったレコードの数を返す
data_sources ローカルホスト上で利用できるデータベースの配列を返す
ChopBlanks fetchrow_* メソッドが空白を取り除くかどうかを管理する
NUM_OF_PARAMS 設定された命令文中の placeholder の数
NULLABLE どのフィールドに NULL 値があるか？
trace Perform tracing for debugging

MySQL 固有メソッド

insertid 最後の AUTO_INCREMENT 値
is_blob どのフィールドが BLOB か？
is_key どのフィールドがキーか？
is_num どのフィールドが数値型か？
is_pri_key どのフィールドがプライマリキーか？
is_not_null どのフィールドが NULL 値か？　NULLABLE 参照。
length 利用可能なフィールドサイズの最大値
max_length 実際に存在しているフィールドサイズの最大値
NAME フィールド名
NUM_OF_FIELDS 返されたフィールドの数
table 返されたセットのテーブル名
type 全てのフィールドの型
_CreateDB データベースを作成する
_DropDB データベースを削除する。 ＊＊＊このメソッドは危険である＊＊＊

以下の節に、より詳細な Perl メソッドの解説がある。 Variables used for method return values have these meanings:

$dbh
Database handle
$sth
Statement handle
$rc
Return code (often a status)
$rv
Return value (often a row count)

汎用 DBI メソッド

Generally the 'do' statement is MUCH faster (and is preferable) than prepare/execute for statements that doesn't contain parameters.
connect($data_source, $username, $password)
データソースとのデータベース接続をするために connect を使う。 $data_source 値は DBI:driver_name: ではじめること。 DBD::mysql ドライバーを用いた connect の使用例： 
$dbh = DBI->connect("DBI:mysql:$database", $user, $password);
$dbh = DBI->connect("DBI:mysql:$database:$hostname",
                    $user, $password);
$dbh = DBI->connect("DBI:mysql:$database:$hostname:$port",
                    $user, $password);
ユーザー名またはパスワードが未設定の場合、 DBI は環境変数である DBI_USER と DBI_PASS をそれぞれ使う。 ホスト名を指定しない場合は、'localhost' がデフォルトとなる。 ポート番号を指定しない場合は、MySQL ポート（3306） がデフォルトとなる。 As of Msql-Mysql-modules Version 1.2009, the $data_source value allows certain modifiers:
mysql_read_default_file=file_name
Read `filename' as an option file. For information on option files, see 「4.1.2 `my.cnf' オプションファイル」節.
mysql_read_default_group=group_name
The default group when reading an option file is normally the [client] group. By specifying the mysql_read_default_group option, the default group becomes the [group_name] group.
mysql_compression=1
Use compressed communication between the client and server (MySQL Version 3.22.3 or later).
mysql_socket=/path/to/socket
Specify the pathname of the Unix socket that is used to connect to the server (MySQL Version 3.21.15 or later).
Multiple modifiers may be given; each must be preceded by a semicolon. For example, if you want to avoid hardcoding the user name and password into a DBI script, you can take them from the user's `~/.my.cnf' option file instead by writing your connect call like this: 
$dbh = DBI->connect("DBI:mysql:$database"
                . ";mysql_read_default_file=$ENV{HOME}/.my.cnf",
                $user, $password);
This call will read options defined for the [client] group in the option file. If you wanted to do the same thing but use options specified for the [perl] group as well, you could use this: 
$dbh = DBI->connect("DBI:mysql:$database"
                . ";mysql_read_default_file=$ENV{HOME}/.my.cnf"
                . ";mysql_read_default_group=perl",
                $user, $password);
disconnect
disconnect メソッドは、データベースとのデータベースハンドルを切断する。 プログラムを終了する直前に呼び出されるのが典型的である。 例： 
$rc = $dbh->disconnect;
prepare($statement)
データベースエンジンで実行するためのSQL文を設定し、execute メソッドで 使用出来るステートメントハンドル ($sth) を返す。 Typically you handle SELECT statements (and SELECT-like statements such as SHOW, DESCRIBE, and EXPLAIN) by means of prepare and execute. Example: 
$sth = $dbh->prepare($statement)
    or die "Can't prepare $statement: $dbh->errstr\n";
If you want to read big results to your client you can tell Perl to use mysql_use_result() with: 
my $sth = $dbh->prepare($statement { "mysql_use_result" => 1});
execute
execute メソッドは、設定されたSQL文を実行する。非 SELECT 文のときは、 影響のあったレコードの数を返す。 もしなんの変化もなかったなら、 execute は "0E0" (これは Perl では ゼロ 扱いですが、 真 でもある) を返す。 If an error occurs, execute returns undef. SELECT 文のときは、SQL要求を開始するのみである。 データを操作する fetch_* メソッドの内の一つを記述する必要がある。 例： 
$rv = $sth->execute
          or die "can't execute the query: $sth->errstr;
do($statement)
do メソッドはSQL文を設定・実行し、影響のあったレコードの数を返す。 このメソッドは、「非 select」文、すなわち、高度（ドライバーの限界のため）で設定できない文、 一度の実行（inserts, deletes など）で済む文のときに一般的に用いられる。 例： 
$rv = $dbh->do($statement)
        or die "Can't execute $statement: $dbh- >errstr\n";
quote($string)
quote メソッドは、文字列中にエスケープ文字があるときに用いられ、 クォート文字を文の外側に付加する。 例： 
$sql = $dbh->quote($string)
fetchrow_array
このメソッドはデータの次のレコードを取り出し、フィールドの値の配列として返す。 例： 
while(@row = $sth->fetchrow_array) {
        print qw($row[0]\t$row[1]\t$row[2]\n);
}
fetchrow_arrayref
このメソッドはデータの次のレコードを取り出し、フィールドの値の配列への参照として返す。 例： 
while($row_ref = $sth->fetchrow_arrayref) {
        print qw($row_ref->[0]\t$row_ref->[1]\t$row_ref->[2]\n);
}
fetchrow_hashref
このメソッドはデータのレコードを取り出し、名前・値のペアのフィールドを含んだ ハッシュテーブルへの参照を返す。このメソッドは、上で示した配列参照 （訳注：fetchrow_arrayref）よりもかなり効率的ではない。例： 
while($hash_ref = $sth->fetchrow_hashref) {
        print qw($hash_ref->{firstname}\t$hash_ref->{lastname}\t\
                $hash_ref->{title}\n);
}
fetchall_arrayref
このメソッドは、SQL文より返されたデータ（レコード）の全てを得るために使う。 このメソッドは、各レコードへの参照の配列の配列への参照を返す。 入れ子のループを使ってデータを利用・表示する。例： 
my $table = $sth->fetchall_arrayref
                or die "$sth->errstr\n";
my($i, $j);
for $i ( 0 .. $#{$table} ) {
        for $j ( 0 .. $#{$table->[$i]} ) {
                print "$table->[$i][$j]\t";
        }
        print "\n";
}
finish
そのステートメントハンドルからそれ以上データを取り出さないことを示す。ステートメントハンドルや、つかんでいたシステムリソースを解放するためにこのメソッドを呼び出す。例： 
$rc = $sth->finish;
rows
最後の命令により、（データの更新、削除、などで）影響のあったレコードの数を返す。 このメソッドは do あるいは 非 SELECT execute 文を 実行した後に、たいてい使われる。例： Example: 
$rv = $sth->rows;
NULLABLE
Returns a reference to an array of values that indicate whether columns may contain NULL values. The possible values for each array element are 0 or the empty string if the column cannot be NULL, 1 if it can, and 2 if the column's NULL status is unknown. Example: 
$null_possible = $sth->{NULLABLE};
NUM_OF_FIELDS
この属性は、SELECT 文や SHOW FIELDS 文によって返された フィールドの数を示している。命令文が結果を返したかどうかをチェックするのに、 これを使うことが出来る：０値は、INSERT, DELETE または UPDATE のような非 SELECT 文を示している。例： Example: 
$nr_of_fields = $sth->{NUM_OF_FIELDS};
data_sources($driver_name)
このメソッドは、'localhost' ホスト上の MySQL サーバで 利用可能なデータベースの名前を含んだ配列を返す。例： 
@dbs = DBI->data_sources("mysql");
ChopBlanks
この属性は、 fetchrow_* メソッドが返り値から前後の空白を 除去するかどうかを決定する。例： 
$sth->{'ChopBlanks'} =1;
trace($trace_level)
trace($trace_level, $trace_filename)
The trace method enables or disables tracing. When invoked as a DBI class method, it affects tracing for all handles. When invoked as a database or statement handle method, it affects tracing for the given handle (and any future children of the handle). Setting $trace_level to 2 provides detailed trace information. Setting $trace_level to 0 disables tracing. Trace output goes to the standard error output by default. If $trace_filename is specified, the file is opened in append mode and output for all traced handles is written to that file. Example: 
DBI->trace(2);                # trace everything
DBI->trace(2,"/tmp/dbi.out"); # trace everything to
                              # /tmp/dbi.out
$dth->trace(2);               # trace this database handle
$sth->trace(2);               # trace this statement handle
You can also enable DBI tracing by setting the DBI_TRACE environment variable. Setting it to a numeric value is equivalent to calling DBI->(value). Setting it to a pathname is equivalent to calling DBI->(2,value).

MySQL 固有メソッド

The methods shown here are MySQL-specific and not part of the DBI standard. Several of them are now deprecated: is_blob, is_key, is_num, is_pri_key, is_not_null, length, max_length, and table. Where DBI-standard alternatives exist, they are noted here:

insertid
MySQL の特徴である AUTO_INCREMENT を使うとき、 新しい自動繰り上がり値がここに記憶される。例： Example: 
$new_id = $sth->{insertid};
As an alternative, you can use $dbh->{'mysql_insertid'}.
is_blob
配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドが BLOB 値であることを示す。例： 
$keys = $sth->{is_blob};
is_key
配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドがキーであることを示す。 例： 
$keys = $sth->{is_key};
is_num
配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドが数値型であることを示す。 例： 
$nums = $sth->{is_num};
is_pri_key
配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドがプライマリーキーであることを示す。 例： 
$pri_keys = $sth->{is_pri_key};
is_not_null
配列の各要素に対し、ブール値の配列への参照を返す。FALSE であれば そのフィールドが NULL 値を含むことを示す。 例： 
$not_nulls = $sth->{is_not_null};
is_not_null is deprecated; 前述の NULLABLE 属性を使用するほうが望ましい。それが DBI の標準である。
length
max_length
それぞれのメソッドは、フィールドサイズの配列への参照を返す。length 配列は、 （テーブル記述で定義された）各フィールドの利用可能最大値を示す。 max_length 配列は、テーブル中に実際に存在している最大値を示す。例： 
$lengths = $sth->{length};
$max_lengths = $sth->{max_length};
NAME
フィールド名の配列への参照を返す。 例： 
$names = $sth->{NAME};
table
テーブル名の配列への参照を返す。 例： 
$tables = $sth->{table};
type
フィールドの型の配列への参照を返す。 例： 
$types = $sth->{type};

8.2.3 DBI/DBD に関するそれ以上の情報

DBI に関するそれ以上の情報は perldoc コマンドで得られる。 

perldoc DBI
perldoc DBI::FAQ
perldoc DBD::mysql

他のフォーマットに変換するツール、pod2man, pod2html なども 使うことが出来る。

そしてもちろん、DBI の最新情報は DBI ウェッブページで見ることが出来る：http://dbi.perl.org/.

8.3 MySQL ODBC サポート

MySQL は MyODBC プログラムで ODBC 機能を提供します。 This chapter will teach you how to install MyODBC, and how to use it. Here, you will also find a list of common programs that are known to work with MyODBC.

8.3.1 How To Install MyODBC

MyODBC 2.50 is a 32-bit ODBC 2.50 specification level 0 (with level 1 and level 2 features) driver for connecting an ODBC-aware application to MySQL. MyODBC works on Windows 9x/Me/NT/2000/XP and most Unix platforms. MyODBC 3.51 is an enhanced version with ODBC 3.5x specification level 1 (complete core API + level 2 features). MyODBC は Open Source で、最新の物は以下にあります： http://www.mysql.com/downloads/api-myodbc.html. Please note that the 2.50.x versions are LGPL licensed, whereas the 3.51.x versions are GPL licensed.

日本語文字コードに対応させた物は： http://www.SoftAgency.co.jp/.

If you have problem with MyODBC and your program also works with OLEDB, you should try the OLEDB driver.

Normally you only need to install MyODBC on Windows machines. You only need MyODBC for Unix if you have a program like ColdFusion that is running on the Unix machine and uses ODBC to connect to the databases.

もし、Unix に MyODBC をインストールしたいなら、 ODBC マネージャーも必要でしょう。 MyODBC は Unix の ODBC マネージャー でも動作することが知られています。

To install MyODBC on Windows, you should download the appropriate MyODBC `.zip' file, unpack it with WinZIP or some similar program, and execute the `SETUP.EXE' file.

Windows/NT の場合、MyODBC をインストール時にいかのような エラーになるかもしれません: 

An error occurred while copying C:\WINDOWS\SYSTEM\MFC30.DLL. Restart
Windows and try installing again (before running any applications which
use ODBC)

The problem in this case is that some other program is using ODBC and because of how Windows is designed, you may not in this case be able to install a new ODBC drivers with Microsoft's ODBC setup program. In most cases you can continue by just pressing Ignore to copy the rest of the MyODBC files and the final installation should still work. これを解決するには、一度 ’セーフモード’でコンピュータを立ち上げ直し、 (windows リブート時に、F8キーを押すことで、セーフモードの選択が可能です) MyODBC をインストールして、リブートします:

  • Windows マシンから UNIX に ODBC アプリケーションを使用して接続するには、 まず最初に Windows マシンに MyODBC をインストールしなくては なりません。
  • UNIX 上の MySQL サーバーに対して、ユーザーと Windows マシンの アクセス許可を与えます。 これは、 GRANT コマンドで可能です。 「4.3.1 GRANT と REVOKE 構文」節参照.
  • ODBC DSN を以下のようにして作成しなくてはなりません：
    • Windows マシンのコントロールパネルを開く
    • Double-click the ODBC Data Sources 32-bit icon.
    • "ユーサーDSN" をクリック
    • "追加..." ボタンをクリック
    • 新しいデータソース の画面から、MySQL を選び、完了ボタンをクリック。
    • MySQL Driver のデフォルト設定が現れます。 「8.3.2 ODBC 管理プログラムの各種項目を埋めるには？」節参照.
  • Now start your application and select the ODBC driver with the DSN you specified in the ODBC administrator.

MyODBC の設定画面には、MySQL 接続時のオプションがいくつか 設定できるようになっています。 もし問題がある場合は、これらを試します。

8.3.2 ODBC 管理プログラムの各種項目を埋めるには？

Windows95 上のサーバ名の記述には3つの可能性があります:

  • サーバの IP アドレスの使用
  • ファイル `\windows\lmhosts' への次の情報の追加: 
    ip hostname
    例えば： 
    194.216.84.21 my_hostname
  • DNS を使用するように設定します。

ODBC setup を埋める方法の例: 

Windows DSN name:   test
Description:        This is my test database
MySql Database:     test
Server:             194.216.84.21
User:               monty
Password:           my_password
Port:

Windows DSN name 項目の値は、あなたのwindows ODBC setup における 一意の名前です。

ODBC setup 画面で、Server, User, Password, Port フィールドを設定する必要はありません。 しかし、ここで設定をすると、後でサーバーに接続する際に、 設定した値がデフォルト値として使用されます。 使用時に値を変更するオプションはあります。

ポート番号が設定されていないなら、デフォルトポート (3306) が使用 されます。

もしオプションを Read options from C:\my.cnf にすると, client と odbc グループは `C:\my.cnf' ファイルから読まれます。 mysql_options() で使用できる全てのオプションが利用可能です。 「8.4.3.163 mysql_options()」節参照.

8.3.3 Connect parameters for MyODBC

One can specify the following parameters for MyODBC on the [Servername] section of an `ODBC.INI' file or through the InConnectionString argument in the SQLDriverConnect() call.

Parameter Default value Comment
user ODBC (on Windows) The username used to connect to MySQL.
server localhost The hostname of the MySQL server.
database The default database.
option 0 A integer by which you can specify how MyODBC should work. See below.
port 3306 The TCP/IP port to use if server is not localhost.
stmt A statement that will be executed when connecting to MySQL.
password The password for the server user combination.
socket The socket or Windows pipe to connect to.

The option argument is used to tell MyODBC that the client isn't 100% ODBC compliant. On Windows, one normally sets the option flag by toggling the different options on the connection screen but one can also set this in the opton argument. The following options are listed in the same order as they appear in the MyODBC connect screen:

Bit Description
1 The client can't handle that MyODBC returns the real width of a column.
2 The client can't handle that MySQL returns the true value of affected rows. If this flag is set then MySQL returns 'found rows' instead. One must have MySQL 3.21.14 or newer to get this to work.
4 Make a debug log in c:\myodbc.log. This is the same as putting MYSQL_DEBUG=d:t:O,c::\myodbc.log in `AUTOEXEC.BAT'
8 Don't set any packet limit for results and parameters.
16 Don't prompt for questions even if driver would like to prompt
32 Simulate a ODBC 1.0 driver in some context.
64 Ignore use of database name in 'database.table.column'.
128 Force use of ODBC manager cursors (experimental).
256 Disable the use of extended fetch (experimental).
512 Pad CHAR fields to full column length.
1024 SQLDescribeCol() will return fully qualifed column names
2048 Use the compressed server/client protocol
4096 Tell server to ignore space after function name and before '(' (needed by PowerBuilder). This will make all function names keywords!
8192 Connect with named pipes to a mysqld server running on NT.
16384 Change LONGLONG columns to INT columns (some applications can't handle LONGLONG).
32768 Return 'user' as Table_qualifier and Table_owner from SQLTables (experimental)
65536 Read parameters from the client and odbc groups from `my.cnf'
131072 Add some extra safety checks (should not bee needed but...)

If you want to have many options, you should add the above flags! For example setting option to 12 (4+8) gives you debugging without package limits!

The default `MYODBC.DLL' is compiled for optimal performance. If you want to debug MyODBC (for example to enable tracing), you should instead use `MYODBCD.DLL'. To install this file, copy `MYODBCD.DLL' over the installed `MYODBC.DLL' file.

8.3.4 MyODBC での問題をどのように報告すべきか？

MyODBC は以下でテストされました： Access, Admndemo.exe, C++-Builder, Borland Builder 4, Centura Team Developer (formerly Gupta SQL/Windows), ColdFusion (on Solaris and NT with svc pack 5), Crystal Reports, DataJunction, Delphi, ERwin, Excel, iHTML, FileMaker Pro, FoxPro, Notes 4.5/4.6, SBSS, Perl DBD-ODBC, Paradox, Powerbuilder, Powerdesigner 32 bit, VC++, and Visual Basic.

If you know of any other applications that work with MyODBC, please send mail to myodbc@lists.mysql.com about this!

With some programs you may get an error like: Another user has modifies the record that you have modified. In most cases this can be solved by doing one of the following things:

  • Add a primary key for the table if there isn't one already.
  • Add a timestamp column if there isn't one already.
  • Only use double float fields. Some programs may fail when they compare single floats.

If the above doesn't help, you should do a MyODBC trace file and try to figure out why things go wrong.

8.3.5 MyODBC で動作することが知られているプログラム

Most programs should work with MyODBC, but for each of those listed here, we have tested it ourselves or received confirmation from some user that it works:

Program
Comment
Access
To make Access work:
  • If you are using Access 2000, you should get and install the newest (version 2.6 or above) Microsoft MDAC (Microsoft Data Access Components) from http://www.microsoft.com/data/. This will fix the following bug in Access: when you export data to MySQL, the table and column names aren't specified. Another way to around this bug is to upgrade to MyODBC Version 2.50.33 and MySQL Version 3.23.x, which together provide a workaround for this bug! You should also get and apply the Microsoft Jet 4.0 Service Pack 5 (SP5) which can be found here http://support.microsoft.com/support/kb/articles/Q 239/1/14.ASP. This will fix some cases where columns are marked as #deleted# in Access. Note that if you are using MySQL Version 3.22, you must to apply the MDAC patch and use MyODBC 2.50.32 or 2.50.34 and above to go around this problem.
  • For all Access versions, you should enable the MyODBC option flag Return matching rows. For Access 2.0, you should additionally enable Simulate ODBC 1.0.
  • 更新するつもりのあるテーブルの全てに、timestamp を持たせなければなりません。 For maximum portability TIMESTAMP(14) or simple TIMESTAMP is recommended instead of other TIMESTAMP(X) variations.
  • You should have a primary key in the table. If not, new or updated rows may show up as #DELETED#.
  • Only use DOUBLE float fields. Access fails when comparing with single floats. The symptom usually is that new or updated rows may show up as #DELETED# or that you can't find or update rows. tem If you are linking a table through MyODBC, which has BIGINT as one of the column, then the results will be displayed as #DELETED. The work around solution is:
    • Have one more dummy column with TIMESTAMP as the data type, preferably TIMESTAMP(14).
    • Check the 'Change BIGINT columns to INT' in connection options dialog in ODBC DSN Administrator
    • Delete the table link from access and re-create it.
    It still displays the previous records as #DELETED#, but newly added/updated records will be displayed properly.
  • ダブルフロート型だけが(実数に)使用できます。Accessではシングルフロートと比較は失 敗します。 The symptom usually is that new or updated rows may show up as #Deleted# or that you can't find or update rows.
  • If you still get the error Another user has changed your data after adding a TIMESTAMP column, the following trick may help you: Don't use table data sheet view. Create instead a form with the fields you want, and use that form data sheet view. You should set the DefaultValue property for the TIMESTAMP column to NOW(). It may be a good idea to hide the TIMESTAMP column from view so your users are not confused.
  • アクセスは、MySQL が理解できない間違った SQL クエリを 作成するかもしれません。 これはアクセスのメニューから "Query|SQLSpecific|Pass-Through" を選択すれば 直すことが可能です。
  • NT 上の Access は BLOB フィールドを OLE OBJECTS と認識します。 もし MEMO フィールドを代わりに使用したいなら、 ALTER TABLE を使って、 TEXT 型にフィールドを変更しなくてはなりません。
  • Access は DATE フィールドをいつも正しく扱うことが出来ません。 もしこれらの問題があった場合、フィールド型を DATETIME に変えてください。
  • If you have in Access a column defined as BYTE, Access will try to export this as TINYINT instead of TINYINT UNSIGNED. This will give you problems if you have values > 127 in the column!
ADO
When you are coding with the ADO API and MyODBC you need to put attention in some default properties that aren't supported by the MySQL server. For example, using the CursorLocation Property as adUseServer will return for the RecordCount Property a result of -1. To have the right value, you need to set this property to adUseClient, like is showing in the VB code here: 
Dim myconn As New ADODB.Connection
Dim myrs As New Recordset
Dim mySQL As String
Dim myrows As Long

myconn.Open "DSN=MyODBCsample"
mySQL = "SELECT * from user"
myrs.Source = mySQL
Set myrs.ActiveConnection = myconn
myrs.CursorLocation = adUseClient
myrs.Open
myrows = myrs.RecordCount

myrs.Close
myconn.Close
Another workaround is to use a SELECT COUNT(*) statement for a similar query to get the correct row count.
Active server pages (ASP)
You should use the option flag Return matching rows.
BDE applications
To get these to work, you should set the option flags Don't optimize column widths and Return matching rows.
Borland Builder 4
When you start a query you can use the property Active or use the method Open. Note that Active will start by automatically issuing a SELECT * FROM ... query that may not be a good thing if your tables are big!
ColdFusion (On Unix)
The following information is taken from the ColdFusion documentation: Use the following information to configure ColdFusion Server for Linux to use the unixODBC driver with MyODBC for MySQL data sources. Allaire has verified that MyODBC Version 2.50.26 works with MySQL Version 3.22.27 and ColdFusion for Linux. (Any newer version should also work.) You can download MyODBC at http://www.mysql.com/downloads/api-myodbc.html ColdFusion Version 4.5.1 allows you to us the ColdFusion Administrator to add the MySQL data source. However, the driver is not included with ColdFusion Version 4.5.1. Before the MySQL driver will appear in the ODBC datasources drop-down list, you must build and copy the MyODBC driver to `/opt/coldfusion/lib/libmyodbc.so'. The Contrib directory contains the program `mydsn-xxx.zip' which allows you to build and remove the DSN registry file for the MyODBC driver on Coldfusion applications.
DataJunction
You have to change it to output VARCHAR rather than ENUM, as it exports the latter in a manner that causes MySQL grief.
Excel
Works. A few tips:
  • 日付に問題が起きた場合、CONCAT() 関数を使用し、文字として SELECT してみて ください。 例えば： 
    select CONCAT(rise_time), CONCAT(set_time)
    from sunrise_sunset;
    この方法で文字として返ってきた値を、Excel97 で時間として扱うようにすべきです。 この例の CONCAT() の目的は、フィールドの型が文字列であると ODBC をだます ことです。 CONCAT() がなければ、ODBC はフィールドの型が日付とわかるので、 Excel が今度はそれを理解できなくなります。 これは Excel のバグです。なぜなら文字を自動で日付に直すのですから。 これは単にテキストファイルの情報を扱う場合ならばいいのですが、 各項目の型を知らせる ODBC 接続の情報を扱う場合は、とても愚かな方法です。
Word
To retrieve data from MySQL to Word/Excel documents, you need to use the MyODBC driver and the Add-in Microsoft Query help. For example, create a db with a table containing 2 columns of text:
  • Insert rows using the mysql client command-line tool.
  • Create a DSN file using the ODBC manager, for example, `my' for the db above.
  • Open the Word application.
  • Create a blank new documentation.
  • Using the tool bar called Database, press the button insert database.
  • Press the button Get Data.
  • At the right hand of the screen Get Data, press the button Ms Query.
  • In the Ms Query create a New Data Source using the DSN file my.
  • Select the new query.
  • Select the columns that you want.
  • Make a filter if you want.
  • Make a Sort if you want.
  • Select Return Data to Microsoft Word.
  • Click Finish.
  • Click Insert data and select the records.
  • Click OK and you see the rows in your Word document.
odbcadmin
ODBC のテストプログラム.
Delphi
DBE 3.2 以上を必ず使用してください。 MySQL に接続する際には、'Don't optimize column width' オプションをセッ トします。 Also, here is some potentially useful Delphi code that sets up both an ODBC entry and a BDE entry for MyODBC (the BDE entry requires a BDE Alias Editor that is free at a Delphi Super Page near you. (Thanks to Bryan Brunton bryan@flesherfab.com for this): 
fReg:= TRegistry.Create;
  fReg.OpenKey('\Software\ODBC\ODBC.INI\DocumentsFab', True);
  fReg.WriteString('Database', 'Documents');
  fReg.WriteString('Description', ' ');
  fReg.WriteString('Driver', 'C:\WINNT\System32\myodbc.dll');
  fReg.WriteString('Flag', '1');
  fReg.WriteString('Password', '');
  fReg.WriteString('Port', ' ');
  fReg.WriteString('Server', 'xmark');
  fReg.WriteString('User', 'winuser');
  fReg.OpenKey('\Software\ODBC\ODBC.INI\ODBC Data Sources', True);
  fReg.WriteString('DocumentsFab', 'MySQL');
  fReg.CloseKey;
  fReg.Free;

  Memo1.Lines.Add('DATABASE NAME=');
  Memo1.Lines.Add('USER NAME=');
  Memo1.Lines.Add('ODBC DSN=DocumentsFab');
  Memo1.Lines.Add('OPEN MODE=READ/WRITE');
  Memo1.Lines.Add('BATCH COUNT=200');
  Memo1.Lines.Add('LANGDRIVER=');
  Memo1.Lines.Add('MAX ROWS=-1');
  Memo1.Lines.Add('SCHEMA CACHE DIR=');
  Memo1.Lines.Add('SCHEMA CACHE SIZE=8');
  Memo1.Lines.Add('SCHEMA CACHE TIME=-1');
  Memo1.Lines.Add('SQLPASSTHRU MODE=SHARED AUTOCOMMIT');
  Memo1.Lines.Add('SQLQRYMODE=');
  Memo1.Lines.Add('ENABLE SCHEMA CACHE=FALSE');
  Memo1.Lines.Add('ENABLE BCD=FALSE');
  Memo1.Lines.Add('ROWSET SIZE=20');
  Memo1.Lines.Add('BLOBS TO CACHE=64');
  Memo1.Lines.Add('BLOB SIZE=32');

  AliasEditor.Add('DocumentsFab','MySQL',Memo1.Lines);
C++ Builder
BDE 3.0で,テストされました。唯一の知られた問題は、 テーブルスキーマが変化する時、クエリフィールドが更新されないことです。 BDE は、index PRIMARY だけを認識し、プライマリーキーは認識していないように思えま す。これはさほど問題ではないですが。
Vision
You should use the option flag Return matching rows.
Visual Basic
テーブルの更新を可能にするため、テーブルにプライマリーキーを作成しなくてはなりま せん。 Visual Basic with ADO can't handle big integers. This means that some queries like SHOW PROCESSLIST will not work properly. The fix is to set the option OPTION=16384 in the ODBC connect string or to set the Change BIGINT columns to INT option in the MyODBC connect screen. You may also want to set the Return matching rows option.
VisualInterDev
If you get the error [Microsoft][ODBC Driver Manager] Driver does not support this parameter the reason may be that you have a BIGINT in your result. Try setting the Change BIGINT columns to INT option in the MyODBC connect screen.
Visual Objects
You should use the option flag Don't optimize column widths.

8.3.6 AUTO_INCREMENT フィールドの値を ODBC で得る方法

共通の問題は、INSERT で自動的に生成されるIDの値を得ることです。 ODBCでは、以下のようにします( 例中の auto が AUTO_INCREMENT フィー ルドです)： 

INSERT INTO foo (auto,text) VALUES(NULL,'text');
SELECT LAST_INSERT_ID();

もしくは、他のテーブルにIDを挿入するだけなら以下のようにします： 

INSERT INTO foo (auto,text) VALUES(NULL,'text');
INSERT INTO foo2 (id,text) VALUES(LAST_INSERT_ID(),'text');

「8.4.6.3 最後に挿入された行のユニーク ID をどのように得られるか？」節参照.

For the benefit of some ODBC applications (at least Delphi and Access), the following query can be used to find a newly inserted row: 

SELECT * FROM tbl_name WHERE auto IS NULL;

8.3.7 Reporting Problems with MyODBC

もし MyODBC 使用時に難しい問題にあたった場合、 ODBC マネージャのログファイル (ODBCADMIN からリクエストしたときのログ) と MyODBC のログを取り始めるべきです。 これはいかなる問題にも解決の糸口になるはずです。

MyODBC のログを取るには、以下のように行ないます：

  1. Ensure that you are using `myodbcd.dll' and not `myodbc.dll'. The easiest way to do this is to get `myodbcd.dll' from the MyODBC distribution and copy it over the `myodbc.dll', which is probably in your `C:\windows\system32' or `C:\winnt\system32' directory. Note that you probably want to restore the old myodbc.dll file when you have finished testing, as this is a lot faster than `myodbcd.dll'.
  2. Tag the `Trace MyODBC' option flag in the MyODBC connect/configure screen. The log will be written to file `C:\myodbc.log'. If the trace option is not remembered when you are going back to the above screen, it means that you are not using the myodbcd.dll driver (see the item above).
  3. Start your application and try to get it to fail.

Check the MyODBC trace file, to find out what could be wrong. You should be able to find out the issued queries by searching after the string >mysql_real_query in the `myodbc.log' file.

You should also try duplicating the queries in the mysql monitor or admndemo to find out if the error is MyODBC or MySQL.

If you find out something is wrong, please only send the relevant rows (max 40 rows) to myodbc@lists.mysql.com. Please never send the whole MyODBC or ODBC log file!

If you are unable to find out what's wrong, the last option is to make an archive (tar or zip) that contains a MyODBC trace file, the ODBC log file, and a README file that explains the problem. You can send this to ftp://support.mysql.com/pub/mysql/secret/. Only we at MySQL AB will have access to the files you upload, and we will be very discrete with the data!

If you can create a program that also shows this problem, please upload this too!

If the program works with some other SQL server, you should make an ODBC log file where you do exactly the same thing in the other SQL server.

Remember that the more information you can supply to us, the more likely it is that we can fix the problem!

8.4 MySQL C API

C API コードは MySQL とともに配布されます。これは libmysqlclient ライブラリに含まれ、C プログラムからデータベースへ のアクセスを許します。

MySQL ソースディストリビューション内のクライアントの多くは C で書かれています。C API の使 用法を示す例を探すなら、これらのクライアントを調べてください。

他のクライアント API の多く(Java を除く全て)は、MySQL サーバと の通信にこのライブラリを使用します。そのため、例えば、他のクライアントプ ログラムで使用されるのと同じ環境変数の多くの利点を得ることができます。そ れらはライブラリから参照されるからです。これらの変数のリストについては 「4.8 MySQL Client-Side Scripts and Utilities」節 を参照して下さい。

クライアントは最大通信バッファサイズを持ちます。最初に割り当てられるバッ ファのサイズ(16K バイト)は自動的に最大サイズ(デフォルトは 16M)まで増加し ます。バッファサイズは必要に応じて増加するため、単純にデフォルトの最大制 限を増加しても、さらに内部で資源を使用することはありません。このサイズチェッ クは主に間違ったクエリと通信パケットのためのチェックです。

通信バッファは一つの SQL ステートメント(クライアントからサーバへの通信)と、 返されるデータ(サーバからクライアントへの通信)の１レコードを含むのに 十分大きくなくてはいけません。各スレッドの 通信バッファは、任意のレコードやクエリを処理するために、指定された制限まで動的 に増大します。例えば、最大 16M のデータを含む BLOB 値がある場合、 少なくとも 16M を通信バッファ制限として持つ必要があります(サーバとクライ アントの両方で)。 クライアントのデフォルトの最大値は 16M ですが、サーバの最大値のデフォルトは 1M です。これはサーバ起動時に、max_allowed_packet パラメータの 値を変更することにより、増やすことが出来ます。 「5.5.2 サーバーパラメーターのチューニング」節参照.

MySQL サーバは、各クエリ後に各通信バッファを net_buffer_length バイトに縮小します。 クライアントでは、接続に割り当てられたバッファのサイズは、接続が閉じられるまで減少しません。 クライアントメモリは接続がクローズされた時に調整されます。

スレッドプログラミングについては、 「8.4.8 スレッドクライアントを作る方法」節参照. を参考にしてください。

8.4.1 C API データ型

MYSQL
この構造体は一つのデータベース接続のハンドルを表わします。これはほとんど全て の MySQL 関数に使用されます。
MYSQL_RES
この構造体はレコードを返すクエリ(SELECT, SHOW, DESCRIBE, EXPLAIN)の結果を表わ します。クエリから返される情報は、この節の残りでは結果セットと呼 ばれます。
MYSQL_ROW
これはデータの１レコードの安全な型表現です。これは現在バイト文字列の配列として実 装されています。(フィールド値がバイナリデータを含むことがある場合、これを NULL 終端文字列として扱うことはできません。そのような値は内部に NULL バイトを含 むことがあるからです。) mysql_fetch_row() の呼び出しによりレコードが獲得 されます。
MYSQL_FIELD
この構造体はフィールドについての情報、つまりフィールドの名前、型、サイズ 等を含んでいます。このメンバは後でさらに詳細に説明されています。 mysql_fetch_field() を繰り返し呼び出すことにより、各フィールドの MYSQL_FIELD 構造体を得ることができます。 フィールド値はこの構造体の一部ではありません; それは MYSQL_ROW 構造 体に含まれています。
MYSQL_FIELD_OFFSET
これは、MySQL フィールドリストへのオフセットの安全な型表現です。 (mysql_field_seek() で使用されます。)オフセットはレコード内のフィールド 番号で、0 から始まります。
my_ulonglong
レコード数と mysql_affected_rows(), mysql_num_rows() そして mysql_insert_id() に使用される型です。 この型は 0 から 1.84e19 の範囲を与えます。 システムによっては、my_ulonglong 型の値を表示しようとしても、動作 しないことがあります。この値を表示するには、unsigned long に変換 し、%lu 出力書式を使用してください。例: 
printf (Number of rows: %lu\n", (unsigned long) mysql_num_rows(result));

MYSQL_FIELD 構造体は次のメンバを含みます:

char * name
フィールドの名前。null終端文字列。
char * table
このフィールドを含むテーブルの名前。計算されたフィールドでない場合のみ有 効です。計算されたフィールドでは、table 値は空文字列です。
char * def
このフィールドのデフォルト値。null終端文字列。 これは mysql_list_fields() 使用時にだけ設定されます。
enum enum_field_types type
フィールドの型。 type 値は次の一つです:
型の値 型の意味
FIELD_TYPE_TINY TINYINT フィールド
FIELD_TYPE_SHORT SMALLINT フィールド
FIELD_TYPE_LONG INTEGER フィールド
FIELD_TYPE_INT24 MEDIUMINT フィールド
FIELD_TYPE_LONGLONG BIGINT フィールド
FIELD_TYPE_DECIMAL DECIMAL または NUMERIC フィールド
FIELD_TYPE_FLOAT FLOAT フィールド
FIELD_TYPE_DOUBLE DOUBLE または REAL フィールド
FIELD_TYPE_TIMESTAMP TIMESTAMP フィールド
FIELD_TYPE_DATE DATE フィールド
FIELD_TYPE_TIME TIME フィールド
FIELD_TYPE_DATETIME DATETIME フィールド
FIELD_TYPE_YEAR YEAR フィールド
FIELD_TYPE_STRING 文字列 (CHAR または VARCHAR) フィールド
FIELD_TYPE_BLOB BLOB または TEXT フィールド (最大長を確定するには max_length を使用して下さい)
FIELD_TYPE_SET SET フィールド
FIELD_TYPE_ENUM ENUM フィールド
FIELD_TYPE_NULL NULL型 フィールド
FIELD_TYPE_CHAR 非推奨; FIELD_TYPE_TINY を代わりに使用してください
IS_NUM() マクロで、フィールドが数値タイプかどうかをテストできます。 フィールドが数値の場合、type メンバを IS_NUM() に渡すと TRUE と評価します: 
if (IS_NUM(field->type))
    printf("Field is numeric\n");
unsigned int length
フィールドの幅。これはテーブル定義で指定されたものです。
unsigned int max_length
結果セットのフィールドの最大幅(実際の結果セットの中のレコードの最長フィールド値 の長さ)。mysql_store_result() または mysql_list_fields() を 使用する場合は、これはフィールドの最大幅になります。 mysql_use_result() を使用する場合は、この変数の値は 0 になります。
unsigned int flags
フィールドの種々のビットフラグ。flags 値は 0 または次のビットの一つ 以上の組み合わせです:
フラグの値 フラグの意味
NOT_NULL_FLAG フィールドは NULL にできない
PRI_KEY_FLAG フィールドはプライマリキーの一部である
UNIQUE_KEY_FLAG フィールドはユニークキーの一部である
MULTIPLE_KEY_FLAG フィールドは非ユニークキーの一部である
UNSIGNED_FLAG フィールドは UNSIGNED 属性を持っている
ZEROFILL_FLAG フィールドは ZEROFILL 属性を持っている
BINARY_FLAG フィールドは BINARY 属性を持っている
AUTO_INCREMENT_FLAG フィールドは AUTO_INCREMENT 属性を持っている
ENUM_FLAG フィールドは ENUM である (非推奨)
SET_FLAG Field is a SET (deprecated)
BLOB_FLAG フィールドは BLOB または TEXT である (非推奨)
TIMESTAMP_FLAG フィールドは TIMESTAMP である (非推奨)
BLOB_FLAG, ENUM_FLAG, SET_FLAG, TIMESTAMP_FLAG の使用は推奨さ れません。これらは型の属性ではなくフィールドの型を示すからです。代わり に field->type を FIELD_TYPE_BLOB, FIELD_TYPE_ENUM, FIELD_TYPE_SET, FIELD_TYPE_TIMESTAMP に対してテストする方をお勧めします。 次の例は flags 値の典型的な使用を示しています: 
if (field->flags & NOT_NULL_FLAG)
    printf("Field can't be null\n");
flags 値の真偽状態を調べるために、次の便利なマクロを使用でき ます:
IS_NOT_NULL(flags) このフィールドが NOT NULL として定義されていれば真
IS_PRI_KEY(flags) このフィールドがプライマリキーならば真
IS_BLOB(flags) このフィールドが BLOB または TEXT ならば真 (非推奨; 代わりに field->type をテストして下さい)
unsigned int decimals
数値フィールドの小数部桁数。

8.4.2 C API 関数概要

C API には次に一覧された関数が存在します。これらの関数は次の節でかな り詳細に説明されています。 「8.4.3 C API 関数説明」節参照。

Function Description
mysql_affected_rows() 最後の UPDATE, DELETE, INSERT クエリによって変更／削 除／挿入されたレコード数を返します。
mysql_change_user() 接続中ののユーザとデータベースを変更します。
mysql_character_set_name() 接続のデフォルト文字セットの名前を返します。
mysql_close() サーバ接続をクローズします。
mysql_connect() MySQL サーバに接続します。この関数は推奨されません; 代わりに mysql_real_connect() を使用してください。
mysql_create_db() データベースを生成します。この関数は推奨されません; 代わりに SQL コマン ド CREATE DATABASE を使用してください。
mysql_data_seek() クエリ結果セット中の任意のレコードにシークします。
mysql_debug() 与えられた文字列で DBUG_PUSH を行ないます。
mysql_drop_db() データベースを破棄します。この関数は推奨されません; 代わりに SQL コマン ド DROP DATABASE を使用してください。
mysql_dump_debug_info() サーバに、デバッグ情報をログに書き出させます。
mysql_eof() 結果セットの最後のレコードが読まれたかどうかを判定します。この関数は推奨されませ ん; 代わりに mysql_errno() または mysql_error() を使用して下 さい。
mysql_errno() 最後の MySQL 関数からのエラー番号を返します。
mysql_error() 最後の MySQL 関数からのエラーメッセージを返します。
mysql_escape_string() SQL ステートメント内で使用するために文字列中の特殊文字をエスケープします。
mysql_fetch_field() テーブルの次のフィールドの型を返します。
mysql_fetch_field_direct() テーブルの、番号で指定されたフィールドの型を返します。
mysql_fetch_fields() 全てのフィールド構造体の配列を返します。
mysql_fetch_lengths() 現在のレコード中の全てのフィールドの長さを返します。
mysql_fetch_row() 結果セットから次のレコードを取り出します。
mysql_field_seek() 指定されたフィールド上にフィールドカーソルを置きます。
mysql_field_count() 最後のクエリの結果のフィールドの数を返します。
mysql_field_tell() 最後の mysql_fetch_field() で使用されたフィールドカーソルの位置を返 します。
mysql_free_result() 結果セットによって使用されたメモリを解放します。
mysql_get_client_info() クライアントバージョン情報を返します。
mysql_get_host_info() 接続を説明する文字列を返します。
mysql_get_server_version() Returns version number of server as an integer (new in 4.1).
mysql_get_proto_info() 接続に使用されるプロトコルバージョンを返します。
mysql_get_server_info() サーバのバージョン番号を返します。
mysql_info() 最後に実行されたクエリについての情報を返します。
mysql_init() MYSQL 構造体を獲得または初期化します。
mysql_insert_id() AUTO_INCREMENT フィールドに最後に生成された ID を返します。
mysql_kill() 指定されたスレッドを殺します。
mysql_list_dbs() 簡易正規表現に適合するデータベース名を返します。
mysql_list_fields() 簡易正規表現に適合するフィールド名を返します。
mysql_list_processes() 現在のサーバスレッドのリストを返します。
mysql_list_tables() 簡易正規表現に適合するテーブル名を返します。
mysql_num_fields() 結果セット中のフィールド数を返します。
mysql_num_rows() 結果セット中のレコード数を返します。
mysql_options() mysql_connect() のための接続オプションを設定します。
mysql_ping() サーバへの接続が動作しているかどうかをチェックします。 必要であれば再接続します。
mysql_query() NULL 終端文字列として記述された SQL クエリを実行します。
mysql_real_connect() MySQL サーバに接続します。
mysql_real_escape_string() Escapes special characters in a string for use in a SQL statement, taking into account the current charset of the connection.
mysql_real_query() 数えられた文字列として記述された SQL クエリを実行します。
mysql_reload() 権限テーブルを再読み込みするようにサーバに指示します。
mysql_row_seek() 結果セット内のあるレコードへシークします。mysql_row_tell() から返される値を 使用します。
mysql_row_tell() レコードカーソルの位置を返します。
mysql_select_db() データベースを選択します。
mysql_shutdown() データベースサーバをシャットダウンします。
mysql_stat() 文字列でサーバ状態を返します。
mysql_store_result() クライアントに完全な結果セットを取り出します。
mysql_thread_id() 現在のスレッド ID を返します。
mysql_thread_save() Returns 1 if the clients are compiled as thread-safe.
mysql_use_result() 各レコードの動的結果セットを初期化します。

サーバへ接続するには、接続ハンドラを初期化するために mysql_init() を呼びだし、それから mysql_real_connect() をそのハンドラで呼びだし ます (ホスト名、ユーザ名、パスワードのような他の情報に加えて)。 Upon connection, mysql_real_connect() sets the reconnect flag (part of the MYSQL structure) to a value of 1. This flag indicates, in the event that a query cannot be performed because of a lost connection, to try reconnecting to the server before giving up. その接続で の処理が終了した時は、接続を終了させるために mysql_close() を呼びだ します。

接続が有効な間は、クライアントは mysql_query() または mysql_real_query() を使用して SQL クエリをサーバに送信できます。こ の２つの違いは、mysql_query() は NULL終端文字列としてクエリが記述さ れることを期待するのに対し、mysql_real_query() は数えられた文字列を 期待することです。文字列がバイナリデータ(NULバイトを含みことがある)を含む 場合は、mysql_real_query() を使用する必要があります。

非SELECT クエリ(例えば、INSERT, UPDATE, DELETE)では、どれくらいのレコードが変更(影響)されたかを mysql_affected_rows() を呼び出すことで見つけ出すことができます。

SELECT クエリでは、選択されたレコードを結果セットとして取り出します。 (注意: いくつかのステートメントは、レコードを返すという点で SELECTに似ています。それは SHOW, DESCRIBE, EXPLAIN です。これらは SELECT ステートメントと同じ方法で扱わ れるべきです。)

クライアントが結果セットを処理するには２つの方法があります。一つ目は、 mysql_store_result() を呼び出すことで、結果セット全体を一度にすべて 取り出すことです。この関数はサーバからクエリによって返されるすべてのレコー ドを取得し、それをクライアントに格納します。二つ目は、 mysql_use_result() を呼び出すことで、レコードごとの結果セット取り出 しを初期化することです。この関数は取り出しを初期化しますが、実際にはサーバ から何のレコードも得ません。

どちらの場合でも、mysql_fetch_row() を呼び出してレコードにアクセス します。mysql_store_result() では、mysql_fetch_row() は既に サーバから取得してあるレコードにアクセスします。 mysql_use_result() では、mysql_fetch_row() は実際にサーバか らレコードを取り出します。各レコードのデータ値のサイズについての情報は mysql_fetch_lengths() を呼び出すことで得られます。

結果セットでの処理が終った後は、mysql_free_result() を呼び出し、そ れが使用していたメモリを解放して下さい。

この２つの取り出し機構は相補的なものです。クライアントプログラムは、必要に よってもっとも適切なアプローチを選択すべきです。慣例的に、クライアントは一 般に mysql_store_result() を使用する傾向にあります。

mysql_store_result() の利点は、すべてのレコードをクライアントに取っ て来るため、連続してレコードをアクセスできるだけでなく、結果セット中の現在 のレコード位置を変更するために、mysql_data_seek() や mysql_row_seek() を使用して、結果セットの中を後や前に移動することが できます。また、mysql_num_rows() を呼び出すことで、レコード数を見つ けることもできます。一方、mysql_store_result() の必要メモリは、大き な結果セットではとても高く、out-of-memory 状態に遭遇する可能性が高くなりま す。

mysql_use_result() の利点は、一度に一つのレコードだけを保持するため、 クライアントが結果セットに要求するメモリが少ないことです（そして、割当のオー バーヘッドも少ないので、mysql_use_result() はより速くなります）。不 利な点は、サーバの拘束を避けるため、各レコードを素早く処理する必要があるこ と、結果セット中でレコードのランダムアクセスができないこと（レコードを順番 にアクセスすることしかできません）、そして、すべてのレコードを取り出さない 限り、結果セット中にいくつのレコードがあるかを知ることができないことです。 さらに、あなたが探している情報を、検索の途中で見つけることができて、問題が 解決したとしても、すべてのレコードを取り出さなければなりません。

API はクライアントがクエリが SELECT であるかどうかを知ることなしに、 （必要時だけレコードを取り出す）クエリに適切に応答できるようにします。 それぞれの mysql_query()（または mysql_real_query()）の後で、 mysql_store_result() を呼び出すことで、これが可能です。結果セットの 呼び出しが成功すると、クエリは SELECT であり、レコードを読むことが できます。結果セット呼び出しが失敗した場合は、結果が実際に期待されたもので あるかどうかを確定するために、mysql_field_count() を呼び出してくだ さい。mysql_field_count() が 0 を返す場合は、クエリはデータを返しま せん（クエリが INSERT, UPDATE, DELETE 等であることを 示します）。つまりレコードが返ることを期待できません。 mysql_field_count() が 0 でない場合は、クエリはレコードを返すべきな のに、返さなかったということです。これはクエリが SELECT で失敗した ということを示します。これをどのように行なうことができるかの例は、 mysql_field_count() の説明を参照してください。

mysql_store_result() と mysql_use_result() はどちらも、結果 セットを作るフィールドについての情報（フィールドの数、その名前や型など）を 獲得することができます。mysql_fetch_field() を繰り返し呼び出すこと で順番に、または、mysql_fetch_field_direct() を呼び出すことでレコー ド内のフィールド番号で、レコード内のフィールド情報にアクセスすることができ ます。現在のフィールドカーソル位置は mysql_field_seek() を呼び出す ことで変更できます。フィールドカーソルの設定は、その後の mysql_fetch_field() 呼び出しに影響します。 mysql_fetch_fields() を呼び出すことで、一度にすべてのフィールドの情 報を得ることもできます。

エラーの検出、報告については、mysql_errno() と mysql_error() 関数の方法によって、MySQL はエラー情報へのア クセスを提供します。これらは、最後に呼び出された成功または失敗し得る関数に ついてのエラーコードとエラーメッセージを返し、エラーがいつ何で発生したかを 確定することができます。

8.4.3 C API 関数説明

以下の説明では、NULL の引数または戻り値は C プログラミング言語で の NULL を意味します。MySQL NULL 値ではありません。 関数は通常ポインタか整数の値を返します。しかし関数説明に記述がある場合、 ポインタを返す関数は、成功を示すために非 NULL 値を返し、エラーを示すた めに NULL を返します。整数を返す関数は、成功を示すために 0 を返し、 エラーを示すために非0を返します。``非0'' は関数説明が他に述べていない限 り、その意味になることに注意してください; 関数説明が他に述べている場合、 これらに対して 0 以外の固有の値をテストしないでください: 

if (result)                   /* 正しい */
    ... error ...

if (result < 0)               /* 間違い */
    ... error ...

if (result == -1)             /* 間違い */
    ... error ...

関数がエラーを返すとき、関数説明の エラー 節が起り得るエラーの 種類を一覧しています。mysql_errno() の呼び出しによってどれが発生 したかを見つけ出すことができます。エラーを表現する文字列は mysql_error() の呼び出しによって得られます。

8.4.3.1 mysql_affected_rows()

my_ulonglong mysql_affected_rows(MYSQL *mysql)

8.4.3.2 説明

最後の UPDATE によって変更されたレコード数、または、DELETE によって削除されたレコード数、INSERT によって挿入されたレコード数を 返します。UPDATE, DELETE, INSERT ステートメントでの mysql_query() 直後に呼び出します。SELECT ステートメントでは、 mysql_affected_rows() は mysql_num_rows() に似た動きをします。

8.4.3.3 戻り値

0 より大きい整数は影響された行数または取り出された行数を示します。0 は UPDATE ステートメントで更新されたレコードがないこと、またはクエリの WHERE 節に適合したレコードがないこと、またはまだなんのクエリも実行 していないことを示します。-1 はクエリがエラーを返したこと、あるいは SELECT クエリで、mysql_affected_rows() が mysql_store_result() 呼び出しよりも先に呼び出されたことを揣摩します。

8.4.3.4 エラー

無し。

8.4.3.5 例

mysql_query(&mysql,"UPDATE products SET cost=cost*1.25 WHERE group=10");
printf("%ld products updated",(long) mysql_affected_rows(&mysql));

If one specifies the flag CLIENT_FOUND_ROWS when connecting to mysqld, mysql_affected_rows() will return the number of rows matched by the WHERE statement for UPDATE statements.

Note that when one uses a REPLACE command, mysql_affected_rows() will return 2 if the new row replaced and old row. This is because in this case one row was inserted after the duplicate was deleted.

8.4.3.6 mysql_change_user()

my_bool mysql_change_user(MYSQL *mysql, const char *user, const char *password, const char *db)

8.4.3.7 説明

ユーザを変更し、mysql で示された接続上で、db で示されたデー タベースがデフォルト（現在の）データベースになります。その後のクエリでは、 明示的なデータベースの指定を含んでいないテーブル参照について、このデータベー スがデフォルトになります。

この関数は MySQL 3.23.3 で導入されました。

mysql_change_user() は接続されたユーザが認証されない場合、またはデー タベースを使用する権限を持っていない場合に失敗します。この場合、ユーザとデー タベースは変更されません。

デフォルトデータベースを持ちたくない場合、db パラメータを NULL に設定できます。

8.4.3.8 戻り値

成功時 0。エラーが発生した場合は非0。

8.4.3.9 エラー

mysql_real_connect() から得られるものと同じです。

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。
ER_UNKNOWN_COM_ERROR
MySQL サーバはこのコマンドを実装していない（おそらく古いサーバ）。
ER_ACCESS_DENIED_ERROR
ユーザまたはパスワードが間違っている。
ER_BAD_DB_ERROR
データベースが存在しない。
ER_DBACCESS_DENIED_ERROR
ユーザがデータベースへのアクセス権を持っていない。
ER_WRONG_DB_NAME
データベース名が長過ぎる。

8.4.3.10 例

if (mysql_change_user(&mysql, "user", "password", "new_database"))
{
   fprintf(stderr, "Failed to change user.  Error: %s\n",
           mysql_error(&mysql));
}

8.4.3.11 mysql_character_set_name()

const char *mysql_character_set_name(MYSQL *mysql)

8.4.3.12 Description

Returns the default character set for the current connection.

Starting from MySQL 4.0.6 this command will always ROLLBACK any active transactions, close all temporary tables, unlock all locked tables and reset the state as if one had done a new connect. This will happen even if the user didn't change.

8.4.3.13 Return Values

The default character set

8.4.3.14 Errors

None.

8.4.3.15 mysql_close()

void mysql_close(MYSQL *mysql)

8.4.3.16 説明

前にオープンされた接続をクローズします。ハンドルが mysql_init() ま たは mysql_connect() で自動的に割り当てられた場合、 mysql_close() は mysql で示される接続ハンドルの解放も行ない ます。

8.4.3.17 戻り値

無し。

8.4.3.18 エラー

無し。

8.4.3.19 mysql_connect()

MYSQL *mysql_connect(MYSQL *mysql, const char *host, const char *user, const char *passwd)

8.4.3.20 説明

この関数は推奨されません。代わりに mysql_real_connect() の使用を お勧めします。

mysql_connect() は host 上で動作している MySQL デー タベースエンジンへの接続の確立を試みます。mysql_get_client_info() を除く他のすべての API 関数を実行する前にmysql_connect() が成功終了 している必要があります。

パラメータの意味は mysql_real_connect() の対応するパラメータと同じですが、 接続パラメータは NULL にできることが異なります。この場合 C API は接 続構造体に自動的にメモリを割り当て、mysql_close() 呼び出し時にそれ を解放します。このアプローチの不利な点は接続が失敗した場合にエラーメッセー ジを取り出すことができないことです。（mysql_errno() または mysql_error() からエラー情報を得るには、正しい MYSQL ポイン タを提供する必要があります。）

8.4.3.21 戻り値

mysql_real_connect() と同じ

8.4.3.22 エラー

mysql_real_connect() と同じ

8.4.3.23 mysql_create_db()

int mysql_create_db(MYSQL *mysql, const char *db)

8.4.3.24 説明

db 引数によって指定されたデータベースを作成します。

この関数は推奨されません。代わりに mysql_query() を使って、SQL CREATE DATABASE ステートメントを発行することをお勧めします。

8.4.3.25 戻り値

データベースの作成が成功した場合は0。エラーが発生した場合は非0。

8.4.3.26 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.27 例

if(mysql_create_db(&mysql, "my_database"))
{
   fprintf(stderr, "Failed to create new database.  Error: %s\n",
           mysql_error(&mysql));
}

8.4.3.28 mysql_data_seek()

void mysql_data_seek(MYSQL_RES *result, my_ulonglong offset)

8.4.3.29 説明

クエリ結果セット中の任意のレコードにシークします。これは、結果セット構造体 がクエリのすべての結果を持っていることを要求します。そのため、 mysql_data_seek() は mysql_store_result() と共にだけ使用され、 mysql_use_result() と共には使用できません。

オフセットの値は 0 から mysql_num_rows(result)-1 でなくては なりません。

8.4.3.30 戻り値

無し。

8.4.3.31 エラー

無し。

8.4.3.32 mysql_debug()

void mysql_debug(const char *debug)

8.4.3.33 説明

与えられた文字列で DBUG_PUSH を行ないます。mysql_debug() は Fred Fish が作成した debug library を使用します。この関数を使用するためには、デバッ グをサポートするように、クライアントライブラリをコンパイルする必要があり ます。 「E.1 MySQL server のデバッグ」節参照. 「E.2 Debugging a MySQL client」節参照.

8.4.3.34 戻り値

無し。

8.4.3.35 エラー

無し。

8.4.3.36 例

次に示した呼び出しは、クライアントライブラリが、クライアントマシン上の `/tmp/client.trace' にトレースファイルを生成します: 

mysql_debug("d:t:O,/tmp/client.trace");

8.4.3.37 mysql_drop_db()

int mysql_drop_db(MYSQL *mysql, const char *db)

8.4.3.38 説明

db 引数によって指定されたデータベースを破棄します。

この関数は推奨されません。代わりに mysql_query() を使って、SQL DROP DATABASE ステートメントを発行することをお勧めします。

8.4.3.39 戻り値

データベースの破棄が成功した場合は0。エラーが発生した場合は非0。

8.4.3.40 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.41 例

if(mysql_drop_db(&mysql, "my_database"))
  fprintf(stderr, "Failed to drop the database: Error: %s\n",
          mysql_error(&mysql));

8.4.3.42 mysql_dump_debug_info()

int mysql_dump_debug_info(MYSQL *mysql)

8.4.3.43 説明

いくつかのデバッグ情報をログにダンプするようにサーバに指示します。この動 作をするためには、接続されたユーザが SUPER 権限 (version4.0.2以上。未満はPROCESS 権)を持っていなけ ればなりません。

8.4.3.44 戻り値

コマンドが成功した場合は0。コマンドが失敗した場合は非0。

8.4.3.45 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.46 mysql_eof()

my_bool mysql_eof(MYSQL_RES *result)

8.4.3.47 説明

この関数は推奨されません。mysql_errno() か mysql_error() が 代わりに使用できます。

mysql_eof() は結果セットの最後のレコードが読まれたかどうかを調べま す。

mysql_store_result() の呼び出しが成功して、結果セットを入手した場合、 クライアントは一つのオペレーションですべてのセットを受け取ります。この場合、 mysql_fetch_row() から返される NULL は、常に結果セットの終端 に達したことを意味し、mysql_eof() を呼ぶ必要はありません。 hen used with mysql_store_result(), mysql_eof() will always return true.

一方、結果セット取り出しの初期化のために mysql_use_result() を使用 する場合、セットのレコードは mysql_fetch_row() を繰り返し呼ぶことに より、ひとつずつサーバから獲得されます。この処理中に接続上でエラーが発生し 得るため、mysql_fetch_row() からの戻り値 NULL は、通常必ずし も結果セットの終端に達したことを意味しません。この場合 mysql_eof() を使用して、何が起こったかを検出できます。結果セットの 終端に達した場合は mysql_eof() は非0値を返し、エラーが発生した場合 は 0 を返します。

歴史的に mysql_eof() は標準 MySQL エラー関数 mysql_errno() と mysql_error() 以前に遡ります。これらのエラー 関数は同じ情報を提供するので、これらの使用が mysql_eof() よりも好ま れます。mysql_eof() は現在推奨されません。（実際、これらは多くの情 報を提供します。エラー関数はエラーが発生した時のエラーの理由を示しますが、 mysql_eof() は真偽値だけを返します。）

8.4.3.48 戻り値

エラーが発生しなかった場合は0。結果セットの終端に達した場合は非0。

8.4.3.49 エラー

無し。

8.4.3.50 例

次の例は mysql_eof の使用方法を示します: 

mysql_query(&mysql,"SELECT * FROM some_table");
result = mysql_use_result(&mysql);
while((row = mysql_fetch_row(result)))
{
    // do something with data
}
if(!mysql_eof(result))  // mysql_fetch_row() failed due to an error
{
    fprintf(stderr, "Error: %s\n", mysql_error(&mysql));
}

しかし、標準 MySQL エラー関数で同じ効果を得ることができます: 

mysql_query(&mysql,"SELECT * FROM some_table");
result = mysql_use_result(&mysql);
while((row = mysql_fetch_row(result)))
{
    // do something with data
}
if(mysql_errno(&mysql))  // mysql_fetch_row() failed due to an error
{
    fprintf(stderr, "Error: %s\n", mysql_error(&mysql));
}

8.4.3.51 mysql_errno()

unsigned int mysql_errno(MYSQL *mysql)

8.4.3.52 説明

mysql によって指定された接続上で、最後に呼び出された API 関数の成否のエラーコー ドを返します。戻り値0はエラーが発生しなかったことを意味します。クライア ントエラーメッセージ番号は `errmsg.h' にリストされています。サーバ エラーメッセージ番号は `mysqld_error.h' にリストされています。 In the MySQL source distribution you can find a complete list of error messages and error numbers in the file `Docs/mysqld_error.txt'.

8.4.3.53 戻り値:

エラーコード値。エラーが発生していない場合は0。

8.4.3.54 エラー

無し。

8.4.3.55 mysql_error()

char *mysql_error(MYSQL *mysql)

8.4.3.56 説明

mysql によって指定された接続上で、 mysql_error() は 最後に呼び出された API 関数の成否を、エラーメッセージとして返します。 エラー発生しなかった場合は空文字列 ("") が返されます。 これは次の２つのテストが同じであることを意味します: 

if(mysql_errno(&mysql))
{
    // an error occurred
}

if(mysql_error(&mysql)[0] != '\0')
{
    // an error occurred
}

クライアントエラーメッセージの言語は MySQL クラ イアントライブラリの再コンパイルで変更できます。現在はいくつかの言語で書かれた クライアントエラーメッセージを選択できます。 「4.6.2 Non-English Error Messages」節参照.

8.4.3.57 戻り値

エラーを表わす文字列。 エラーが発生していない場合は空文字列。

8.4.3.58 エラー

無し。

8.4.3.59 mysql_escape_string()

You should use mysql_real_escape_string() instead!

This function is identical to mysql_real_escape_string() except that mysql_real_escape_string() takes a connection handler as its first argument and escapes the string according to the current character set. mysql_escape_string() does not take a connection argument and does not respect the current charset setting.

8.4.3.60 mysql_fetch_field()

MYSQL_FIELD *mysql_fetch_field(MYSQL_RES *result)

8.4.3.61 説明

結果セットの一つのフィールドの定義を MYSQL_FIELD 構造体として返しま す。結果セット内の全てのフィールドについて情報を取り出すには、この関数を繰 り返し呼んでください。mysql_fetch_field() はフィールドが残っていな いと NULL を返します。

mysql_fetch_field() は、新しい SELECT クエリを実行するたびに、 最初のフィールドについての情報を返すようにリセットされます。 mysql_fetch_field() で返されるフィールドは mysql_field_seek() の呼び出しにも影響をうけます。

テーブルを SELECT するために mysql_query() を呼び、しかしま だ mysql_store_result() を呼んでいない場合、 mysql_fetch_field() を BLOB フィールドの長さの問い合わせに使 用すると、MySQL はデフォルトの blob 長 (8K bytes) を返します。 (8K サイズになるのは、MySQL は BLOB の最大長を知らないから です。これはいつかコンフィグ可能になるべきです。) 一度結果セットを取り出せ ば、field->max_length は指定したクエリ内でのこのフィールドの最大値 の長さを含みます。

8.4.3.62 戻り値

現在のフィールドの MYSQL_FIELD 構造体。フィールドが残っていない場合は NULL。

8.4.3.63 エラー

無し。

8.4.3.64 例

MYSQL_FIELD *field;

while((field = mysql_fetch_field(result)))
{
    printf("field name %s\n", field->name);
}

8.4.3.65 mysql_fetch_fields()

MYSQL_FIELD *mysql_fetch_fields(MYSQL_RES *result)

8.4.3.66 説明

結果セットのすべての MYSQL_FIELD 構造体の配列を返します。各構造体は 結果セットの一つのフィールドのフィールド定義を提供します。

8.4.3.67 戻り値

結果セットの全ての項目の MYSQL_FIELD 構造体の配列。

8.4.3.68 エラー

無し。

8.4.3.69 例

unsigned int num_fields;
unsigned int i;
MYSQL_FIELD *fields;

num_fields = mysql_num_fields(result);
fields = mysql_fetch_fields(result);
for(i = 0; i < num_fields; i++)
{
   printf("Field %u is %s\n", i, fields[i].name);
}

8.4.3.70 mysql_fetch_field_direct()

MYSQL_FIELD *mysql_fetch_field_direct(MYSQL_RES *result, unsigned int fieldnr)

8.4.3.71 説明

結果セット中のフィールドを示すフィールド番号 fieldnr が与えられ、そ のフィールドのフィールド定義を MYSQL_FIELD 構造体として返します。こ の関数は任意のフィールドについての定義を取り出すことに使用できます。 fieldnr の値は 0 から mysql_num_fields(result)-1 の範囲にす べきです。

8.4.3.72 戻り値

指定されたフィールドの MYSQL_FIELD 構造体。

8.4.3.73 エラー

無し。

8.4.3.74 例

unsigned int num_fields;
unsigned int i;
MYSQL_FIELD *field;

num_fields = mysql_num_fields(result);
for(i = 0; i < num_fields; i++)
{
    field = mysql_fetch_field_direct(result, i);
    printf("Field %u is %s\n", i, field->name);
}

8.4.3.75 mysql_fetch_lengths()

unsigned long *mysql_fetch_lengths(MYSQL_RES *result)

8.4.3.76 説明

結果セット中の現在のレコードのフィールドの長さを返します。フィールドの値をコピーする場合、 この長さ情報は最適化にも有用です。strlen() の呼び出しを回避できる ためです。 さらに、結果セットがバイナリデータを持つ場合は、データのサイズを特定するためにこの関数を使わなければなりません。 なぜなら strlen() は NULL 文字を含むフィールドについての結果を正しく返さないからです。

空フィールドの長さと NULL 値を含むフィールドの長さは 0 です。この２ つのケースを区別する方法については、mysql_fetch_row() の説明を参照 して下さい。

8.4.3.77 戻り値

各フィールドのサイズ (終端 NUL 文字は含みません)を提供する unsigned long 整数の配列。 エラーが発生した場合は NULL。

8.4.3.78 エラー

mysql_fetch_lengths() は結果セットの現在のレコードについてだけ有効 です。mysql_fetch_row() を呼び出す前、または結果の全てのレコードを 取り出した後にこれを呼んだ場合、NULL が返されます。

8.4.3.79 例

MYSQL_ROW row;
unsigned long *lengths;
unsigned int num_fields;
unsigned int i;

row = mysql_fetch_row(result);
if (row)
{
    num_fields = mysql_num_fields(result);
    lengths = mysql_fetch_lengths(result);
    for(i = 0; i < num_fields; i++)
    {
         printf("Column %u is %lu bytes in length.\n", i, lengths[i]);
    }
}

8.4.3.80 mysql_fetch_row()

MYSQL_ROW mysql_fetch_row(MYSQL_RES *result)

8.4.3.81 説明

結果セットの次のレコードを取り出します。mysql_store_result() の後に使用すると、 これ以上取り出すレコードがない時は、NULL を返します。 mysql_use_result() の後に使用するなら、 これ以上取り出すレコードがない場合やエラーが発生した場合に NULL を返します。

レコード内の値の数は mysql_num_fields(result) によって与えられます。 row が mysql_fetch_row() の呼び出しからの戻り値を保持する場 合、値へのポインタは row[0] から row[mysql_num_fields(result)-1 としてアクセスされます。レコード内の NULL 値はNULL ポインタによって示されます。

レコードのフィールド値の長さは、mysql_fetch_lengths() の呼び出しで 獲得できます。空フィールドと NULL を含むフィールドはどちらも長さ 0 を持ちます; フィールド値のポインタをチェックすることで、これらを区別でき ます。ポインタが NULL の場合、フィールドは NULL です; そうで なければフィールドは空です。

8.4.3.82 戻り値

次のレコードの MYSQL_ROW 構造体、エラーが発生したか、もう取り出すレ コードがない場合は NULL。

8.4.3.83 エラー

CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.84 例

MYSQL_ROW row;
unsigned int num_fields;
unsigned int i;

num_fields = mysql_num_fields(result);
while ((row = mysql_fetch_row(result)))
{
   unsigned long *lengths;
   lengths = mysql_fetch_lengths(result);
   for(i = 0; i < num_fields; i++)
   {
       printf("[%.*s] ", (int) lengths[i], row[i] ? row[i] : "NULL");
   }
   printf("\n");
}

8.4.3.85 mysql_field_count()

unsigned int mysql_field_count(MYSQL *mysql)

3.22.24 より前の MySQL バージョンを使用している場合、 unsigned int mysql_num_fields(MYSQL *mysql) を代わりに使用すべきで す。

8.4.3.86 説明

接続上の最後のクエリのフィールド数を返します。

この関数は通常 mysql_store_result() が NULL を返した時（そし てこのように結果セットポインタを持っていない時）に使用されます。この場合、 mysql_store_result() が空でない結果を提供すべきかどうかを調べるため に、mysql_field_count() を呼び出すことができます。これは、クエリが SELECT（または SELECTに似た）ステートメントであるかを知るこ と無しに、クライアントプログラムに、適切な行動をとらせることができます。下 に示される例は、これをどのように行なうことができるかを説明しています。

「8.4.6.1 mysql_query() が成功を返した後、mysql_store_result() が NULL を返す時があるのは何故？」節参照.

8.4.3.87 戻り値

結果セット中のフィールド番号を表す unsigned integer。

8.4.3.88 エラー

無し。

8.4.3.89 例

MYSQL_RES *result;
unsigned int num_fields;
unsigned int num_rows;

if (mysql_query(&mysql,query_string))
{
    // error
}
else // query succeeded, process any data returned by it
{
    result = mysql_store_result(&mysql);
    if (result)  // there are rows
    {
        num_fields = mysql_num_fields(result);
        // retrieve rows, then call mysql_free_result(result)
    }
    else  // mysql_store_result() returned nothing; should it have?
    {
        if(mysql_field_count(&mysql) == 0)
        {
            // query does not return data
            // (it was not a SELECT)
            num_rows = mysql_affected_rows(&mysql);
        }
        else // mysql_store_result() should have returned data
        {
            fprintf(stderr, "Error: %s\n", mysql_error(&mysql));
        }
    }
}

別の方法は、mysql_field_count(&mysql) 呼び出しを mysql_errno(&mysql) に置き換えることです。この場合、ステートメント が SELECT かどうかを mysql_field_count() の値から推測するの ではなく、直接 mysql_store_result() からのエラーをチェックします。

8.4.3.90 mysql_field_seek()

MYSQL_FIELD_OFFSET mysql_field_seek(MYSQL_RES *result, MYSQL_FIELD_OFFSET offset)

8.4.3.91 説明

与えられたオフセットにフィールドカーソルを設定します。次の mysql_fetch_field() の呼び出しはそのオフセットに対応したフィールドを取 り出します。

レコードの最初にシークするには、0 の offset 値を渡してください。

8.4.3.92 戻り値

フィールドカーソルの前の値。

8.4.3.93 エラー

無し。

8.4.3.94 mysql_field_tell()

MYSQL_FIELD_OFFSET mysql_field_tell(MYSQL_RES *result)

8.4.3.95 説明

最後の mysql_fetch_field() に使用したフィールドカーソルの位置を返 します。この値は mysql_field_seek() への引数として使用できます。

8.4.3.96 戻り値

フィールドカーソルの現在のオフセット。

8.4.3.97 エラー

無し。

8.4.3.98 mysql_free_result()

void mysql_free_result(MYSQL_RES *result)

8.4.3.99 説明

mysql_store_result(), mysql_use_result(), mysql_list_dbs() 等によって結果セットに割り当てられたメモリを解放 します。結果セットで何かを行なった時、mysql_free_result() を呼び 出してそれが使用したメモリを解放する必要があります。

8.4.3.100 戻り値

無し。

8.4.3.101 エラー

無し。

8.4.3.102 mysql_get_client_info()

char *mysql_get_client_info(void)

8.4.3.103 説明

クライアントライブラリバージョンを表わす文字列を返します。

8.4.3.104 戻り値

MySQL クライアントライブラリバージョンを表わす文字列。

8.4.3.105 エラー

無し。

8.4.3.106 mysql_get_server_version()

unsigned long mysql_get_server_version(MYSQL *mysql)

8.4.3.107 Description

Returns version number of server as an integer (new in 4.1).

8.4.3.108 Return Values

A number that represents the MySQL server version in format:

main_version*10000 + minor_version *100 + sub_version

For example, 4.1.0 is returned as 40100.

This is useful to quickly determine the version of the server in a client program to know if some capability exits.

8.4.3.109 Errors

None.

8.4.3.110 mysql_get_host_info()

char *mysql_get_host_info(MYSQL *mysql)

8.4.3.111 説明

使用中の接続タイプを表わす文字列を返します。サーバのホスト名を含みます。

8.4.3.112 戻り値

サーバホスト名と接続タイプを表わす文字列。

8.4.3.113 エラー

無し。

8.4.3.114 mysql_get_proto_info()

unsigned int mysql_get_proto_info(MYSQL *mysql)

8.4.3.115 説明

現在の接続に使用されているプロトコルバージョンを返します。

8.4.3.116 Return Values

現在の接続に使用されているプロトコルバージョンを表わす符号無し整数値。

8.4.3.117 エラー

無し。

8.4.3.118 mysql_get_server_info()

char *mysql_get_server_info(MYSQL *mysql)

8.4.3.119 説明

サーバのバージョン番号を表わす文字列を返します。

8.4.3.120 戻り値

サーバのバージョン番号を表わす文字列。

8.4.3.121 エラー

無し。

8.4.3.122 mysql_info()

char * mysql_info(MYSQL *mysql)

8.4.3.123 説明

最も最近に実行されたクエリについての情報を文字列で返します。が、 以下に挙げる構文に限ります。 他の構文ではmysql_info() は NULL を返します。 文字列の形式 はクエリの型によって様々です。次に説明します (数値は例です; 文字列はクエ リに適した値を含みます):

INSERT INTO ... SELECT ...
String format: Records: 100 Duplicates: 0 Warnings: 0
INSERT INTO ... VALUES (...),(...),(...)...
String format: Records: 3 Duplicates: 0 Warnings: 0
LOAD DATA INFILE ...
String format: Records: 1 Deleted: 0 Skipped: 0 Warnings: 0
ALTER TABLE
String format: Records: 3 Duplicates: 0 Warnings: 0
UPDATE
String format: Rows matched: 40 Changed: 40 Warnings: 0

注意: 複数の値リストがステートメント中に記述された場合にだけ、 mysql_info() は、INSERT ... VALUES ステートメントに非 NULL値を返します。

8.4.3.124 戻り値

最も最近に実行されたクエリについての追加情報を表わす文字列。クエリに有効 な情報がない場合は NULL ポインタ。

8.4.3.125 エラー

無し。

8.4.3.126 mysql_init()

MYSQL * mysql_init(MYSQL *mysql)

8.4.3.127 説明

mysql_real_connect() に適した MYSQL オブジェクトの割り当て または初期化を行ないます。引数が NULL ポインタの場合、関数は新し いオブジェクトを割り当てて初期化し返します。そうでなければオブジェクトは 初期化され、オブジェクトのアドレスが返されます。新しいオブジェクトが割り 当てられた場合、mysql_close() はこのオブジェクトを解放します。

8.4.3.128 戻り値

初期化された MYSQL* ハンドル、または新しいオブジェクトを割り当て るのに十分なメモリがなかった場合は NULL ポインタ。

8.4.3.129 エラー

メモリ不足の場合は NULL が返されます。

8.4.3.130 mysql_insert_id()

my_ulonglong mysql_insert_id(MYSQL *mysql)

8.4.3.131 説明

前のクエリによって AUTO_INCREMENT フィールドに生成された ID を返します。 AUTO_INCREMENT フィールドを含むテーブルに INSERT クエリを 実行した後で、この関数を使用してください。

注意: 前のクエリが AUTO_INCREMENT 値を生成しなかった場合、 mysql_insert_id() は 0 を返します。後のために値を保存する必 要がある場合、値を生成するクエリの直後に mysql_insert_id() を呼び出 すことに気をつけてください。

mysql_insert_id() is updated after INSERT and UPDATE statements that generate an AUTO_INCREMENT value or that set a column value to LAST_INSERT_ID(expr). 「6.3.6.2 その他の関数」節参照.

また、SQL LAST_INSERT_ID() 常に最後に生成された AUTO_INCREMENT 値を含み、クエリ間でリセットされないことに注意して下 さい。その関数の値はサーバ内で保守されるからです。

8.4.3.132 戻り値

前のクエリによって更新された AUTO_INCREMENT フィールドの値。接続上 の前のクエリがない場合、クエリが AUTO_INCREMENT 値を更新しなかった 場合には 0 が返ります。

8.4.3.133 エラー

無し。

8.4.3.134 mysql_kill()

int mysql_kill(MYSQL *mysql, unsigned long pid)

8.4.3.135 説明

pid で指定されたスレッドを殺すようにサーバに頼みます。

8.4.3.136 戻り値

成功時0。失敗時非0。

8.4.3.137 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.138 mysql_list_dbs()

MYSQL_RES *mysql_list_dbs(MYSQL *mysql, const char *wild)

8.4.3.139 説明

サーバ上の、wild 引数で指定された簡易正規表現に適合する、データベー ス名からなる結果セットを返します。wild はワイルドカード文字 `%' または `_' を含むことができます。また、全てのデータベース に適合するように NULL ポインタにできます。mysql_list_dbs() の呼び出しはクエリ SHOW databases [LIKE wild] を実行するのと同様 です。

mysql_free_result() で結果セットを解放する必要があります。

8.4.3.140 戻り値

成功時 MYSQL_RES 結果セット。失敗した場合は NULL。

8.4.3.141 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_OUT_OF_MEMORY
メモリ不足。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.142 mysql_list_fields()

MYSQL_RES *mysql_list_fields(MYSQL *mysql, const char *table, const char *wild)

8.4.3.143 説明

与えられたテーブル内の、wild 引数で指定された簡易正規表現に適合する フィールド名からなる結果セットを返します。wild はワイルドカー ド文字 `%' または `_' を含むことができます。また、全てのフィー ルドに適合するように NULL ポインタにできます。 mysql_list_fields() はクエリ SHOW COLUMNS FROM table [LIKE wild] を実行するのと同様です。

注意: mysql_list_fields() の代わりに SHOW COLUMNS FROM tbl_name の使用を勧めます。

mysql_free_result() で結果セットを解放する必要があります。

8.4.3.144 戻り値

成功時 MYSQL_RES 結果セット。エラーが発生した場合は NULL。

8.4.3.145 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.146 mysql_list_processes()

MYSQL_RES *mysql_list_processes(MYSQL *mysql)

8.4.3.147 説明

現在のサーバスレッドを示す結果セットを返します。これは mysqladmin processlist や SHOW PROCESSLIST クエリで 報告されるものと同じ種類の情報です。

mysql_free_result() で結果セットを解放する必要があります。

8.4.3.148 戻り値

成功時 MYSQL_RES 結果セット。失敗した場合は NULL。

8.4.3.149 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.150 mysql_list_tables()

MYSQL_RES *mysql_list_tables(MYSQL *mysql, const char *wild)

8.4.3.151 説明

wild 引数で指定された簡易正規表現に適合する、現在のデータベース 内のテーブル名からなる結果セットを返します。wild はワイルドカード 文字 `%' または `_' を含むことができます。また、全てのテーブル に適合するように NULL ポインタにできます。 mysql_list_tables() はクエリ SHOW tables [LIKE wild] を実 行するのと同様です。

mysql_free_result() で結果セットを解放する必要があります。

8.4.3.152 戻り値

成功時 MYSQL_RES 結果セット。失敗した場合は NULL。

8.4.3.153 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.154 mysql_num_fields()

unsigned int mysql_num_fields(MYSQL_RES *result)

または

unsigned int mysql_num_fields(MYSQL *mysql)

二番目の形式は MySQL 3.23 以上では動作しません。MYSQL* 引 数を通す場合は、代わりに unsigned int mysql_field_count(MYSQL*mysql) を使用しなくてはいけません。

8.4.3.155 説明

結果セット中のフィールド数を返します。

注意: 結果セットへのポインタまたは接続ハンドルのいずれかからフィールドの数 を得ることができます。mysql_store_result() または mysql_use_result() が NULL を返した（つまり結果セットポイン タが無い）場合、接続ハンドルを使用します。この場合、 mysql_field_count() を呼び出して、mysql_store_result() が空 でない結果を提供すべきかどうかを決定できます。これにより、クライアントプロ グラムはクエリが SELECT（または SELECT に似た）ステートメン トだったかどうかを知ることなしに、適切な行動を取ることができます。以下に示 す例はこれをどのように行なうかを説明しています。

「8.4.6.1 mysql_query() が成功を返した後、mysql_store_result() が NULL を返す時があるのは何故？」節参照.

8.4.3.156 戻り値

結果セット中のフィールド数を表わす符号無し整数。

8.4.3.157 エラー

無し。

8.4.3.158 例

MYSQL_RES *result;
unsigned int num_fields;
unsigned int num_rows;

if (mysql_query(&mysql,query_string))
{
    // error
}
else // query succeeded, process any data returned by it
{
    result = mysql_store_result(&mysql);
    if (result)  // there are rows
    {
        num_fields = mysql_num_fields(result);
        // retrieve rows, then call mysql_free_result(result)
    }
    else  // mysql_store_result() returned nothing; should it have?
    {
        if (mysql_errno(&mysql))
	{
           fprintf(stderr, "Error: %s\n", mysql_error(&mysql));
	}
        else if (mysql_field_count(&mysql) == 0)
        {
            // query does not return data
            // (it was not a SELECT)
            num_rows = mysql_affected_rows(&mysql);
        }
    }
}

（結果セットが返るべきクエリであることを知っている場合の）方法は、 mysql_errno(&mysql) コールを mysql_field_count(&mysql) が 0 かどうかのチェックに置き換えることです。これは何かが悪い場合にだけ起こり ます。

8.4.3.159 mysql_num_rows()

my_ulonglong mysql_num_rows(MYSQL_RES *result)

8.4.3.160 説明

結果セット中のレコード数を返します。

mysql_num_rows() の使用は、結果セットを返すのに mysql_store_result() か mysql_use_result() のどちらを使用す るかに依存します。mysql_store_result() を使用する場合、 mysql_num_rows() はすぐに呼ぶことができます。 mysql_use_result() を使用する場合、結果セットの全てのレコードが取り 出されるまで、mysql_num_rows() は正しい値を返しません。

8.4.3.161 戻り値

結果セットのレコード数。

8.4.3.162 エラー

無し。

8.4.3.163 mysql_options()

int mysql_options(MYSQL *mysql, enum mysql_option option, const char *arg)

8.4.3.164 説明

特別な接続オプションを設定し、接続の振舞いに影響を与えるために使用できます。 この関数は複数のオプションを設定するために複数回呼ぶことができます。

mysql_options() は mysql_init() の後で、 mysql_connect() や mysql_real_connect() の前に呼ばれなければ なりません。

option 引数は設定したいオプションです; arg 引数はオプション に対する値です。オプションが整数の場合、arg は整数値へのポインタで す。

有効なオプション値:

オプション 引数型 機能
MYSQL_OPT_CONNECT_TIMEOUT unsigned int * 接続タイムアウト（秒）。
MYSQL_OPT_COMPRESS 使用しない 圧縮クライアント／サーバプロトコルを使用する。
MYSQL_OPT_LOCAL_INFILE optional pointer to uint If no pointer is given or if pointer points to an unsigned int != 0 the command LOAD LOCAL INFILE is enabled.
MYSQL_OPT_NAMED_PIPE 使用しない NT 上の MySQL サーバへの接続に名前付パイプを使用する。
MYSQL_INIT_COMMAND char * MySQL サーバへの接続時に実行するコマンド。再接続時に自動的に再実行される。
MYSQL_READ_DEFAULT_FILE char * `my.cnf' の代わりに指定されたオプションファイルからオプションを読み込む。
MYSQL_READ_DEFAULT_GROUP char * `my.cnf' または MYSQL_READ_DEFAULT_FILE で指定されたファイルから指定されたグループのオプションを読み込む。

注意: MYSQL_READ_DEFAULT_FILE と MYSQL_READ_DEFAULT_GROUP を 使用する場合、client グループが常に読まれます。

オプションファイル中に指定されるグループは次のオプションを含むことができま す:

connect-timeout 接続タイムアウト（秒）。On Linux this timeout is also used for waiting for the first answer from the server.
compress 圧縮クライアント／サーバプロトコルを使用する。
database 接続命令中でデータベースが指定されない場合、このデータベースに接続する。
debug デバッグオプション
disable-local-infile Disable use of LOAD DATA LOCAL.
max_allowed_packet Max size of packet client can read from server.
host デフォルトホスト名
init-command MySQL サーバへの接続時に実行するコマンド。再接続時に自動的に再実行される。
local-infile[=(0|1)] If no argument or argument != 0 then enable use of LOAD DATA LOCAL.
password デフォルトパスワード
pipe NT 上の MySQL サーバへの接続に名前付パイプを使用する。
protocol=(TCP | SOCKET | PIPE | MEMORY) Which protocol to use when connecting to server (New in 4.1)
port デフォルトポート番号
return-found-rows UPDATE 使用時、mysql_info() が更新された行の代わりに見つかった行を返すようにする。
shared-memory-base-name=name Shared memory name to use to connect to server (default is "MySQL"). New in MySQL 4.1.
socket デフォルトソケット番号
user デフォルトユーザ

Note that timeout has been replaced by connect-timeout, but timeout will still work for a while.

オプションファイルについてのさらなる情報は、 「4.1.2 `my.cnf' オプションファイル」節 を参照して 下さい。

8.4.3.165 戻り値

成功の場合は0。未知のオプションを使用した場合は非0。

8.4.3.166 例

MYSQL mysql;

mysql_init(&mysql);
mysql_options(&mysql,MYSQL_OPT_COMPRESS,0);
mysql_options(&mysql,MYSQL_READ_DEFAULT_GROUP,"odbc");
if (!mysql_real_connect(&mysql,"host","user","passwd","database",0,NULL,0))
{
    fprintf(stderr, "Failed to connect to database: Error: %s\n",
          mysql_error(&mysql));
}

上記は、圧縮クライアント／サーバプロトコルを使用し、my.cnf ファイル 中の odbc セクションから追加オプションを読むように、クライアントに 要求します。

8.4.3.167 mysql_ping()

int mysql_ping(MYSQL *mysql)

8.4.3.168 説明

サーバへの接続が動作しているかどうかをチェックします。ダウンしている場合 は、自動的に再接続を試みます。

この関数は、長い間静かにしているクライアントが、サーバが接続をクローズし たかどうかをチェック（と再接続）するために使用できます。

8.4.3.169 戻り値

サーバが生きている場合0。他の値はエラーを示します。

8.4.3.170 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.171 mysql_query()

int mysql_query(MYSQL *mysql, const char *query)

8.4.3.172 説明

NULL 終端文字列 query で示される SQL クエリを実行します。クエリはひ とつの SQL ステートメントでなければなりません。終端のセミコロン (`;')や \g をステートメントに追加すべきではありません。

mysql_query() はバイナリデータを含むクエリには使用できません（バ イナリデータは `\0' 文字を含むことがあります。これはクエリ文字列の 最後として解釈されます）。この場合、mysql_real_query() を代わりに 使用してください。

If you want to know if the query should return a result set or not, you can use mysql_field_count() to check for this. 「8.4.3.85 mysql_field_count()」節参照.

8.4.3.173 戻り値

クエリが成功した場合は0。クエリが失敗した場合は非0。

8.4.3.174 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.175 mysql_real_connect()

MYSQL *mysql_real_connect(MYSQL *mysql, const char *host, const char *user, const char *passwd, const char *db, unsigned int port, const char *unix_socket, unsigned int client_flag)

8.4.3.176 説明

host 上で動作している MySQL データベースエンジンへの接続 の確立を試みます。 mysql_get_client_info() 以外の他の API 関数を実行する前に、 mysql_real_connect() が成功している必要があります。

mysql_real_connect() を呼び出す前に、MYSQL 構造体を獲得ま たは初期化するために mysql_init() を呼ぶ必要があることに注意して ください。

  • 最初のパラメータは既存の MYSQL 構造体のアドレスです。 mysql_real_connect() を呼ぶ前に、MYSQL 構造体の初期化のため に mysql_init() を呼ぶ必要があります。 mysql_options() 呼び出しで多くの接続オプションを変更できます。 「8.4.3.163 mysql_options()」節参照.
  • host の値はホスト名か IP アドレスのどちらでも可能です。 host が NULL または文字列 "localhost" の場合はロー カルホストへの接続とみなされます。OS がソケットをサポートする場合(UNIX) または名前つきパイプをサポートする場合(Windows)、サーバへの TCP/IP 接続の 代わりに使用されます。
  • user パラメータはユーザの MySQL ログイン ID が入っています。 user が NULL の場合、現在のユーザとみなされます。Windows ODBC 下では、現在のユーザは明示的に指定されなければなりません。UNIX 下で は現在のログイン名が適用されます。 Windows ODBC では, カレントのユーザー名を与えなければなりません。 「8.3.2 ODBC 管理プログラムの各種項目を埋めるには？」節参照.
  • passwd パラメータは user のパスワードが入っています。 もし passwd が NULL の場合、空白のパスワードフィールドを持つ user テーブル内のレコードだけが適合チェックされます。このような方 法で、パスワードが記述されたかどうかによってユーザが異なる権限を得るよう に、データベース管理者が MySQL 特権システムを設定することができ ます。 注意: mysql_connect() を呼び出す前に passwd を暗号化しない でください。パスワードの暗号化はクライアント API で自動的に処理されます。
  • db が NULL でない場合、接続はこの値をデフォルトデータベー スにセットします。
  • port が 0 でない場合、値は TCP/IP 接続のポート番号として使用され ます。host パラメータが接続のタイプを決定することに注意してくださ い。
  • unix_socket が NULL でない場合、文字列は使用されるソケット または名前つきパイプを記述します。host パラメータが接続のタイプを 決定することに注意してください。
  • client_flag の値は通常 0 ですが、とても特殊な状況のため次のフラグの組み 合わせを設定できます:
    フラグ名 フラグの意味
    CLIENT_COMPRESS Use compression protocol.
    CLIENT_FOUND_ROWS 影響された行数ではなく見つかった行数を返します
    CLIENT_IGNORE_SPACE Allow spaces after function names. Makesall functions names reserved words.
    CLIENT_INTERACTIVE Allow interactive_timeout seconds(instead of wait_timeout seconds) of inactivity before closing the connection.
    CLIENT_NO_SCHEMA db_name.tbl_name.col_name を許しません。これは ODBC のためです; その構文を使用した場合、パーサがエラーを生成します。これはいくつかの ODBC プログラムのバグのトラップに役立ちます。
    CLIENT_COMPRESS 圧縮プロトコルを使用します
    CLIENT_ODBC クライアントが ODBC クライアント。これは mysqld をさらに ODBC-フレンドリに変更します。
    CLIENT_SSL Use SSL (encrypted protocol).

mysql_real_connect() の最初の引数に NULL ポインタを記述す ることもできます。これは C API が接続構造体のメモリを割り当て、 mysql_close() 呼び出し時に自動的に解放されます。この方法の不利な 点は、接続が失敗した場合に mysql_real_connect() からのエラーメッ セージを取り出すことができないことです。

最初の引数が NULL ポインタでない場合は、存在する MYSQL 構 造体のアドレスであるべきです。

8.4.3.177 戻り値

接続が成功した場合は MYSQL* 接続ハンドルです。接続が失敗した場合 は C NULL ポインタです。 接続に成功すると、戻り値はその最初のパラメータの値と同じです。

8.4.3.178 エラー

CR_CONN_HOST_ERROR
MySQL サーバへの接続に失敗した。
CR_CONNECTION_ERROR
ローカル MySQL サーバへの接続に失敗した。
CR_IPSOCK_ERROR
IP ソケットの生成に失敗した。
CR_OUT_OF_MEMORY
メモリ不足。
CR_SOCKET_CREATE_ERROR
UNIX ソケットの生成に失敗した。
CR_UNKNOWN_HOST
ホスト名の IP アドレスを見つけるのに失敗した。
CR_VERSION_ERROR
異なるプロトコルバージョンを使用するクライアントライブラリでサーバへの接 続を試みた結果のプロトコルミスマッチ。これは、とても古いクライアントライ ブラリを使用して、--old-protocol オプション付きで開始していない新 しいサーバに接続する場合に発生します。
CR_NAMEDPIPEOPEN_ERROR
Windows 上の名前つきパイプの生成に失敗した。
CR_NAMEDPIPEWAIT_ERROR
Windows 上の名前つきパイプの wait に失敗した。
CR_NAMEDPIPESETSTATE_ERROR
Windows 上のパイプハンドラの獲得に失敗した。
CR_SERVER_LOST
If connect_timeout > 0 and it took longer then connect_timeout seconds to connect to the server or if the server died while executing the init-command.

8.4.3.179 例

MYSQL mysql;

mysql_init(&mysql);
mysql_options(&mysql,MYSQL_READ_DEFAULT_GROUP,"your_prog_name");
if (!mysql_real_connect(&mysql,"host","user","passwd","database",0,NULL,0))
{
    fprintf(stderr, "Failed to connect to database: Error: %s\n",
          mysql_error(&mysql));
}

By using mysql_options() the MySQL library will read the [client] and [your_prog_name] sections in the `my.cnf' file which will ensure that your program will work, even if someone has set up MySQL in some non-standard way.

Note that upon connection, mysql_real_connect() sets the reconnect flag (part of the MYSQL structure) to a value of 1. This flag indicates, in the event that a query cannot be performed because of a lost connection, to try reconnecting to the server before giving up.

8.4.3.180 mysql_real_escape_string()

unsigned long mysql_real_escape_string(MYSQL *mysql, char *to, const char *from, unsigned long length)

8.4.3.181 説明

This function is used to create a legal SQL string that you can use in a SQL statement. 「6.1.1.1 文字列」節参照.

from の文字列を、SQL ステートメントとしてサーバに送ることができる ように、現在のキャラクタ・セットを考慮しながら変換します。 結果は to に入り、終端 null 文字を追加します。 変換される文字列は `NUL' (ASCII 0), `\n', `\r', `\', `'', `"', Control-Z です。( 「6.1.1 文字列と数値をどのように書くか？」節参照). (Strictly speaking, MySQL requires only that backslash and the quote character used to quote the string in the query be escaped. This function quotes the other characters to make them easier to read in log files.)

from で示される文字列 はlength バイト長でなければなりません。 to バッファには少なくとも length*2+1 バイト長を割り当てる 必要があります。（最悪の場合、それぞれの文字が２バイトに変換されることがあ り、さらに終端 null バイトのための場所が必要です。） mysql_real_escape_string() が復帰するとき、to の内容は NUL 終端文字列になります。 戻り値は変換された文字列の長さです。終端 null 文字は含みません。

8.4.3.182 例

char query[1000],*end;

end = strmov(query,"INSERT INTO test_table values(");
*end++ = '\'';
end += mysql_real_escape_string(&mysql, end,"What's this",11);
*end++ = '\'';
*end++ = ',';
*end++ = '\'';
end += mysql_real_escape_string(&mysql, end,"binary data: \0\r\n",16);
*end++ = '\'';
*end++ = ')';

if (mysql_real_query(&mysql,query,(unsigned int) (end - query)))
{
   fprintf(stderr, "Failed to insert row, Error: %s\n",
           mysql_error(&mysql));
}

上記の strmov() 関数は mysqlclient ライブラリに含まれてい て、strcpy() のように働きますが、最初の引数の終りの null へのポイ ンタを返します。

8.4.3.183 戻り値

to へ置かれた値の長さ。終端 null 文字は含みません。

8.4.3.184 エラー

無し。

8.4.3.185 mysql_real_query()

int mysql_real_query(MYSQL *mysql, const char *query, unsigned long length)

8.4.3.186 説明

query で示される SQL クエリを実行します。これは length バ イト長です。クエリはひとつの SQL ステートメントでなければなりません。終端 のセミコロン(`;')や \g をステートメントに追加すべきではありま せん。

バイナリデータを含むクエリは mysql_real_query() を使 用しなければなりません。バイナリデータは `\0' 文字を含むこと があるからです。 また、mysql_real_query() は mysql_query() よりも速いです。 クエリの strlen() を呼ばないからです。

If you want to know if the query should return a result set or not, you can use mysql_field_count() to check for this. 「8.4.3.85 mysql_field_count()」節参照.

8.4.3.187 戻り値

クエリが成功した場合は0。クエリが失敗した場合は非0。

8.4.3.188 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.189 mysql_reload()

int mysql_reload(MYSQL *mysql)

8.4.3.190 説明

MySQL サーバに、アクセス権テーブルを再読み込みするように依頼し ます。接続されたユーザは RELOAD 権限を持つ必要があります。

この関数は推奨されません。代わりに、SQL FLUSH PRIVILEGES ステートメ ントを発行する mysql_query() の使用が推奨されます。

8.4.3.191 戻り値

成功時0。失敗時非0。

8.4.3.192 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.193 mysql_row_seek()

MYSQL_ROW_OFFSET mysql_row_seek(MYSQL_RES *result, MYSQL_ROW_OFFSET offset)

8.4.3.194 説明

レコードカーソルをクエリ結果セット中の絶対レコードに設定します。これは、結 果セット構造体がクエリのすべての結果を持っていることを要求します。そのため、 mysql_row_seek() は mysql_store_result() と共にだけ使用でき、 mysql_use_result() と共には使用できません。

オフセットは mysql_row_tell() または mysql_row_seek() 呼びだ しからの戻り値であるべきです。この値は単純なレコード番号ではありません;レ コード番号を使用して結果セット内のレコードにシークしたい場合は、 mysql_data_seek() を代わりに使用してください。

8.4.3.195 戻り値

レコードカーソルの前の値。この値はその後の mysql_row_seek() 呼びだ しに渡すことができます。

8.4.3.196 エラー

無し。

8.4.3.197 mysql_row_tell()

MYSQL_ROW_OFFSET mysql_row_tell(MYSQL_RES *result)

8.4.3.198 説明

最後の mysql_fetch_row() についてレコードカーソルの現在の位置を返します。 この値は mysql_row_seek() への引数として使用できます。

mysql_row_tell() は mysql_store_result() の後にだけ使用すべ きで、mysql_use_result() の後には使用すべきではありません。

8.4.3.199 戻り値

行カーソルの現在のオフセット。

8.4.3.200 エラー

無し。

8.4.3.201 mysql_select_db()

int mysql_select_db(MYSQL *mysql, const char *db)

8.4.3.202 説明

mysql で示される現在の接続に、デフォルト(現在の)データベースとし て db で示されるデータベースを使用するように指示します。以降のク エリでは、明示的にデータベースを指定しないテーブル参照について、このデー タベースがデフォルトになります。

接続されたユーザがデータベースを使用する権限を持っていると証明されなけれ ば、mysql_select_db() は失敗します。

8.4.3.203 戻り値

成功時0。失敗時非0。

8.4.3.204 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.205 mysql_shutdown()

int mysql_shutdown(MYSQL *mysql)

8.4.3.206 説明

データベースサーバにシャットダウンするように要求します。接続されたユーザ は SHUTDOWN 権限を持っている必要があります。

8.4.3.207 戻り値

成功時0。失敗時非0。

8.4.3.208 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.209 mysql_stat()

char *mysql_stat(MYSQL *mysql)

8.4.3.210 説明

mysqladmin status で提供されるのと同様の情報を文字列として返しま す。これは秒での uptime と、実行中のスレッド数、問い合わせ数、再読み込み 数、オープンテーブル数を含みます。

8.4.3.211 戻り値

サーバ状態を表わす文字列。エラーが発生した場合 NULL。

8.4.3.212 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.213 mysql_store_result()

MYSQL_RES *mysql_store_result(MYSQL *mysql)

8.4.3.214 説明

データを取り出すクエリ(SELECT, SHOW, DESCRIBE, EXPLAIN)が成功する毎に、mysql_store_result() または mysql_use_result() を呼び出す必要があります。

You don't have to call mysql_store_result() or mysql_use_result() for other queries, but it will not do any harm or cause any notable performance if you call mysql_store_result() in all cases. You can detect if the query didn't have a result set by checking if mysql_store_result() returns 0 (more about this later one).

If you want to know if the query should return a result set or not, you can use mysql_field_count() to check for this. 「8.4.3.85 mysql_field_count()」節参照.

mysql_store_result() はクエリのすべての結果をクライアントへ読み込み、 MYSQL_RES 構造体を割り当て、この構造体に結果を配置します。

mysql_store_results() returns a null pointer if the query didn't return a result sets (If the query was, for example, an INSERT statement).

mysql_store_results() returns also null pointer if reading of the result set failed. You can check if you got an error by checking if mysql_error() doesn't return a null pointer, if mysql_errno() returns <> 0 or if mysql_field_count() returns <> 0.

返されるレコードが無い場合、空の結果セットが返されます。 (空の結果セットは NULL 戻り値とは異なります。)

一度 mysql_store_result() を呼び出して null ポインターでない 結果を得る事ができたら、結果セット中にいくつのレ コードがあるかを見つけるために、mysql_num_rows() を呼び出すことがで きます。

結果セットからレコードを取り出すために mysql_fetch_row() を呼び出す ことができます。また、結果セット内の現在のレコード位置を設定／取得するため に mysql_row_seek() と mysql_row_tell() を呼び出すことができ ます。

一度結果セットで行なうと、mysql_free_result() を呼び出す必要があ ります。

「8.4.6.1 mysql_query() が成功を返した後、mysql_store_result() が NULL を返す時があるのは何故？」節参照.

8.4.3.215 戻り値

結果の MYSQL_RES 結果構造体。エラーがある場合 NULL。

8.4.3.216 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_OUT_OF_MEMORY
メモリ不足。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.3.217 mysql_thread_id()

unsigned long mysql_thread_id(MYSQL *mysql)

8.4.3.218 説明

現在の接続のスレッド ID を返します。この値は、スレッドを殺すための mysql_kill() への引数として使用できます。

接続が失われて、mysql_ping() で再接続した場合、スレッド ID は変更さ れます。これはスレッド ID を後で使うために取得して格納すべきではないことを 意味します。必要な時にそれを取得すべきです。

8.4.3.219 戻り値

現在の接続のスレッド ID。

8.4.3.220 エラー

無し。

8.4.3.221 mysql_use_result()

MYSQL_RES *mysql_use_result(MYSQL *mysql)

8.4.3.222 説明

データを取り出すクエリ(SELECT, SHOW, DESCRIBE, EXPLAIN)が成功する毎に、 mysql_store_result() または mysql_use_result() を呼び出す必要があります。

mysql_use_result() は結果セット検索を開始しますが, mysql_store_result() のように、実際にクライアントに結果セットを読み 取りません. 代わりに、各レコードは mysql_fetch_row() 呼びだしが行な われることにより、個々に取り出されます。 mysql_use_result() はクエリの結果を、一時テーブルやローカルバッファ に格納すること無く、サーバから直接読み込みます。これは mysql_store_result() よりもいくらか速く、少ないメモリを使用します。 この場合、クライアントは現在の行と接続バッファ ( max_allowed_packet bytes まで増加する ) のメモリだけを割り当てます。

一方、クライアント側で各行に ついて多くの処理を行なう場合や、ユーザが ^S (スクロール停止) を入 力できるような画面に出力を送る場合は、mysql_use_result() を使用す べきではありません。これはサーバと連携しており、他のスレッドが データが取り出されるテーブルを更新する事を邪魔します。

mysql_use_result() 使用時、NULL 値を取り出すまで mysql_fetch_row() を実行する必要があります。そうしないと、次のク エリは前のクエリから結果を取り出します。これを忘れると、C API はエラー Commands out of sync; You can't run this command now を与えます！

mysql_use_result() から返される結果では、 mysql_data_seek(), mysql_row_seek(), mysql_row_tell(), mysql_num_rows(), mysql_affected_rows() を使用できません。 また、mysql_use_result() が終了するまで他のクエリの発行もできませ ん。(全ての行をフェッチした後に、フェッチされた行数を知るために mysql_num_rows を呼び出すことができます。)

一度結果セットで行なうと、mysql_free_result() を呼び出す必要があ ります。

8.4.3.223 戻り値

結果の MYSQL_RES 結果構造体。エラーがある場合 NULL。

8.4.3.224 エラー

CR_COMMANDS_OUT_OF_SYNC
不当な順にコマンドが実行された。
CR_OUT_OF_MEMORY
メモリ不足。
CR_SERVER_GONE_ERROR
MySQL サーバがいなくなった。
CR_SERVER_LOST
サーバへの接続がクエリ中に失われた。
CR_UNKNOWN_ERROR
未知のエラーが発生した。

8.4.4 C Threaded Function Descriptions

You need to use the following functions when you want to create a threaded client. 「8.4.8 スレッドクライアントを作る方法」節参照.

8.4.4.1 my_init()

void my_init(void)

8.4.4.2 Description

This function needs to be called once in the program before calling any MySQL function. This initialises some global variables that MySQL needs. If you are using a thread-safe client library, this will also call mysql_thread_init() for this thread.

This is automatically called by mysql_init(), mysql_server_init() and mysql_connect().

8.4.4.3 Return Values

None.

8.4.4.4 mysql_thread_init()

my_bool mysql_thread_init(void)

8.4.4.5 Description

This function needs to be called for each created thread to initialise thread-specific variables.

This is automatically called by my_init() and mysql_connect().

8.4.4.6 Return Values

None.

8.4.4.7 mysql_thread_end()

void mysql_thread_end(void)

8.4.4.8 Description

This function needs to be called before calling pthread_exit() to free memory allocated by mysql_thread_init().

Note that this function is not invoked automatically by the client library. It must be called explicitly to avoid a memory leak.

8.4.4.9 Return Values

None.

8.4.4.10 mysql_thread_safe()

unsigned int mysql_thread_safe(void)

8.4.4.11 Description

This function indicates whether the client is compiled as thread-safe.

8.4.4.12 Return Values

1 is the client is thread-safe, 0 otherwise.

8.4.5 C Embedded Server Function Descriptions

You must use the following functions if you want to allow your application to be linked against the embedded MySQL server library. 「8.4.9 libmysqld, the Embedded MySQL Server Library」節参照.

If the program is linked with -lmysqlclient instead of -lmysqld, these functions do nothing. This makes it possible to choose between using the embedded MySQL server and a stand-alone server without modifying any code.

8.4.5.1 mysql_server_init()

int mysql_server_init(int argc, char **argv, char **groups)

8.4.5.2 Description

This function must be called once in the program using the embedded server before calling any other MySQL function. It starts up the server and initialises any subsystems (mysys, InnoDB, etc.) that the server uses. If this function is not called, the program will crash. If you are using the DBUG package that comes with MySQL, you should call this after you have called MY_INIT().

The argc and argv arguments are analogous to the arguments to main(). The first element of argv is ignored (it typically contains the program name). For convenience, argc may be 0 (zero) if there are no command-line arguments for the server. mysql_server_init() makes a copy of the arguments so it's safe to destroy argv or groups after the call.

The NULL-terminated list of strings in groups selects which groups in the option files will be active. 「4.1.2 `my.cnf' オプションファイル」節参照. For convenience, groups may be NULL, in which case the [server] and [emedded] groups will be active.

8.4.5.3 Example

#include <mysql.h>
#include <stdlib.h>

static char *server_args[] = {
  "this_program",       /* this string is not used */
  "--datadir=.",
  "--key_buffer_size=32M"
};
static char *server_groups[] = {
  "embedded",
  "server",
  "this_program_SERVER",
  (char *)NULL
};

int main(void) {
  mysql_server_init(sizeof(server_args) / sizeof(char *),
                    server_args, server_groups);

  /* Use any MySQL API functions here */

  mysql_server_end();

  return EXIT_SUCCESS;
}

8.4.5.4 Return Values

0 if okay, 1 if an error occurred.

8.4.5.5 mysql_server_end()

void mysql_server_end(void)

8.4.5.6 Description

This function must be called once in the program after all other MySQL functions. It shuts down the embedded server.

8.4.5.7 Return Values

None.

8.4.6 Common questions and problems when using the C API

8.4.6.1 mysql_query() が成功を返した後、mysql_store_result() が NULL を返す時があるのは何故？

mysql_query() の呼び出しが成功した後に mysql_store_result() が NULL を返すことがあります。これが 起こったとき、次の条件のどれかの発生を意味します:

  • malloc() が失敗した (例えば、結果セットが大き過ぎた場合)。
  • データが読めなかった (接続のエラー)。
  • クエリがデータを返さなかった (INSERT, UPDATE, DELETE)。

ステートメントが空でない結果を提供するかどうかは mysql_field_count() の呼び出しによっていつでもチェックできます。 mysql_field_count() が 0 を返す場合、結果は空で最後のクエリは値を 返さないステートメントです (例えば、INSERT や DELETE)。 mysql_field_count() が非 0 値を返す場合、ステートメントは空でない 結果を提供します。 例はmysql_field_count() 関数の説明を参照してください。

mysql_error() または mysql_errno() を呼び出すことによって エラーのテストもできます。

8.4.6.2 クエリから得られる結果は何か？

クエリによって返される結果セットに加えて、次の情報も得ることができます:

  • mysql_affected_rows() は、INSERT, UPDATE または DELETE を行なった時の最後のクエリで、影響された行数を返します。 WHERE 節がない DELETE が使用されて、テーブルが切り詰められ た場合は例外です。これはとても速いです！ この場合、 mysql_affected_rows() は影響された行数を 0 と返します。
  • mysql_num_rows() は結果セットのレコード数を返します。 mysql_store_result() では、mysql_num_rows() は mysql_store_result() が復帰したすぐ後に呼び出すことができます。 mysql_use_result() では、mysql_num_rows() は mysql_fetch_row() ですべてのレコードを取り出した後にだけ呼ぶ出すこ とができます。
  • mysql_insert_id() は、AUTO_INCREMENT インデックスを持つテー ブルに行を挿入した最後のクエリによって生成された ID を返します。 「8.4.3.130 mysql_insert_id()」節参照.
  • いくつかのクエリ (LOAD DATA INFILE..., INSERT INTO ... SELECT ..., UPDATE) は追加情報を返します。結果は mysql_info() で返されます。 返す文字列の形式については、mysql_info() の説明を参照してください。 mysql_info() は追加情報がない場 合は NULL ポインタを返します。

8.4.6.3 最後に挿入された行のユニーク ID をどのように得られるか？

AUTO_INCREMENT 属性を持つ項目を含むテーブルにレコードを挿入する場 合、mysql_insert_id() 関数で与えられた ID を得ることができます。

mysql_query() に渡すクエリ文字列内のLAST_INSERT_ID() 関数 を使用することでも、ID を取り出すことができます。

次のコードを実行することで、AUTO_INCREMENT インデックスが使用され たかどうかチェックできます。これは、クエリが AUTO_INCREMENT イン デックスを伴う INSERT だったかどうかもチェックできます: 

if (mysql_error(&mysql)[0] == 0 &&
    mysql_num_fields(result) == 0 &&
    mysql_insert_id(&mysql) != 0)
{
    used_id = mysql_insert_id(&mysql);
}

生成された最後の ID は接続毎にサーバ内で維持されています。他のクライアント によって変更はされません。他の AUTO_INCREMENT 項目を非マジック値 (すなわち、NULL でなく 0 でない値) で更新する場合でも、それは変更 されません。

また、他のテーブルにその ID を挿入しようとする場合、次で行なうことができます: 

INSERT INTO foo (auto,text)
    VALUES(NULL,'text');              # generate ID by inserting NULL
INSERT INTO foo2 (id,text)
    VALUES(LAST_INSERT_ID(),'text');  # use ID in second table

8.4.6.4 C API でのリンクの問題

C API でリンクする時、いくつかのシステム上では次のエラーになります: 

gcc -g -o client test.o -L/usr/local/lib/mysql -lmysqlclient -lsocket -lnsl

Undefined        first referenced
 symbol          in file
floor            /usr/local/lib/mysql/libmysqlclient.a(password.o)
ld: fatal: Symbol referencing errors. No output written to client

これは、あなたのシステム上では、コンパイル/リンク行の最後に、math ライブ ラリ (-lm) を含める必要があることを意味します。

8.4.7 Building Client Programs

If you compile MySQL clients that you've written yourself or that you obtain from a third-party, they must be linked using the -lmysqlclient -lz option on the link command. You may also need to specify a -L option to tell the linker where to find the library. For example, if the library is installed in `/usr/local/mysql/lib', use -L/usr/local/mysql/lib -lmysqlclient -lz on the link command.

For clients that use MySQL header files, you may need to specify a -I option when you compile them (for example, -I/usr/local/mysql/include), so the compiler can find the header files.

To make the above simpler on Unix we have provied the mysql_config script for you. 「4.8.9 mysql_config, Get compile options for compiling clients」節参照.

You can use this to compile a MySQL client by as follows: 

CFG=/usr/local/mysql/bin/mysql_config
sh -c "gcc -o progname `$CFG --cflags` progname.c `$CFG --libs`"

The sh -c is need to get the shell to not threat the output from mysql_config as one word.

8.4.8 スレッドクライアントを作る方法

クライアントは `ほとんど' スレッド安全です。一番大きな問題は `net.c' (ソケットから読み込みをするサブルーチンを含むファイル) が割 り込み安全でないことです。これは、サーバからの長い読み込みを中断できるよ うに、自身のアラームを持ちたいだろうという考慮で行なわれました。 If you install interrupt handlers for the SIGPIPE interrupt, the socket handling should be thread-safe.

われわれの Web site で公開している古いバイナリ配布では、 標準クライアントライブラリはスレッドオプションでコンパイルされていません。 (the Windows binaries are by default compiled to be thread safe). Newer binary distributions should have both a normal and a thread-safe client library.

スレッド安全クライアント(MySQLサーバーとの通信時に、 他のスレッドがクライアントのスレッドに interrupt をかけたり、 タイムアウトをセットしたりする) を得るためには、-lmysys, -lstring, -ldbug ライブラリとサーバが使用する net_serv.o を使用しま す。

If you don't need interrupts or timeouts, you can just compile a thread-safe client library (mysqlclient_r) and use this. 「8.4 MySQL C API」節参照. In this case you don't have to worry about the net_serv.o object file or the other MySQL libraries.

スレッドクライアントを使用する時、`thr_alarm.c' ルーチンを大いに使 用できます。mysys ライブラリからのルーチンを使用する場合、覚えて おかなければならないことは my_init() を最初に呼ぶことだけです！

mysql_real_connect() を除く全ての関数は現在スレッド安全です。スレッ ド安全クライアントライブラリをコンパイルし、それをスレッド安全なマナーで使 用するための方法を、次の注意で説明します。(この mysql_real_connect() についての注意は、実際には mysql_connect() にも有効です。しかし mysql_connect() は推奨 されませんので、とにかく mysql_real_connect() を使用すべきです。)

mysql_real_connect() をスレッド安全にするためには、クライアントを次の コマンドで再コンパイルする必要があります: 

shell> ./configure --enable-thread-safe-client

This will create a thread-safe client library libmysqlclient_r. --enable-thread-safe-client. This library is thread safe per connection. You can let two threads share the same connection as long as you do the following:

  • ２つのスレッドが同じ接続上で同時に MySQL にクエリを送信することは できません。特に mysql_query() と mysql_store_result() の間 で、他のスレッドが同じ接続を使用しないことを確実にする必要があります。
  • 多くのスレッドが mysql_store_result() で取り出された別々の結果セッ トにアクセスできます。
  • mysql_use_result を使用する場合、結果セットがクローズされるまで、他 のスレッドが同じ接続上で何も尋ねないことを確実にする必要があります。 However, it really is best for threaded clients that share the same connection to use mysql_use_result().
  • If you want to use multiple threads on the same connection, you must have a mutex lock around your mysql_query() and mysql_store_result() call combination. Once mysql_store_result() is ready, the lock can be released and other threads may query the same connection.
  • If you program with POSIX threads, you can use pthread_mutex_lock() and pthread_mutex_unlock() to establish and release a mutex lock.

You need to know the following if you have a thread that is calling MySQL functions which did not create the connection to the MySQL database:

When you call mysql_init() or mysql_connect(), MySQL will create a thread-specific variable for the thread that is used by the debug library (among other things).

If you call a MySQL function, before the thread has called mysql_init() or mysql_connect(), the thread will not have the necessary thread-specific variables in place and you are likely to end up with a core dump sooner or later.

The get things to work smoothly you have to do the following:

  1. Call my_init() at the start of your program if it calls any other MySQL function before calling mysql_real_connect().
  2. Call mysql_thread_init() in the thread handler before calling any MySQL function.
  3. In the thread, call mysql_thread_end() before calling pthread_exit(). This will free the memory used by MySQL thread-specific variables.

You may get some errors because of undefined symbols when linking your client with libmysqlclient_r. In most cases this is because you haven't included the thread libraries on the link/compile line.

8.4.9 libmysqld, the Embedded MySQL Server Library

8.4.9.1 Overview of the Embedded MySQL Server Library

The embedded MySQL server library makes it possible to run a full-featured MySQL server inside the client application. The main benefits are increased speed and more simple management for embedded applications.

The API is identical for the embedded MySQL version and the client/server version. To change an old threaded application to use the embedded library, you normally only have to add calls to the following functions:

Function When to call
mysql_server_init() Should be called before any other MySQL function is called, preferably early in the main() function.
mysql_server_end() Should be called before your program exits.
mysql_thread_init() Should be called in each thread you create that will access MySQL.
mysql_thread_end() Should be called before calling pthread_exit()

Then you must link your code with `libmysqld.a' instead of `libmysqlclient.a'.

The above mysql_server_xxx functions are also included in `libmysqlclient.a' to allow you to change between the embedded and the client/server version by just linking your application with the right library. 「8.4.5.1 mysql_server_init()」節参照.

8.4.9.2 Compiling Programs with libmysqld

To get a libmysqld library you should configure MySQL with the --with-embedded-server option.

When you link your program with libmysqld, you must also include the system-specific pthread libraries and some libraries that the MySQL server uses. You can get the full list of libraries by executing mysql_config --libmysqld-libs.

The correct flags for compiling and linking a threaded program must be used, even if you do not directly call any thread functions in your code.

8.4.9.3 Restrictions when using the Embedded MySQL Server

The embedded server has the following limitations:

  • No support for ISAM tables. (This is mainly done to make the library smaller)
  • No UDF functions.
  • No stack trace on core dump.
  • No internal RAID support. (This is not normally needed as most OS has nowadays support for big files).
  • You can set this up as a server or a master (no replication).
  • You can't connect to the embedded server from an outside process with sockets or TCP/IP.

Some of these limitations can be changed by editing the `mysql_embed.h' include file and recompiling MySQL.

8.4.9.4 Using Option Files with the Embedded Server

The following is the recommended way to use option files to make it easy to switch between a client/server application and one where MySQL is embedded. 「4.1.2 `my.cnf' オプションファイル」節参照.

  • Put common options in the [server] section. These will be read by both MySQL versions.
  • Put client/server-specific options in the [mysqld] section.
  • Put embedded MySQL-specific options in the [embedded] section.
  • Put application-specific options in a [ApplicationName_SERVER] section.

8.4.9.5 Things left to do in Embedded Server (TODO)

  • We are going to provide options to leave out some parts of MySQL to make the library smaller.
  • There is still a lot of speed optimisation to do.
  • Errors are written to stderr. We will add an option to specify a filename for these.
  • We have to change InnoDB to not be so verbose when using in the embedded version.

8.4.9.6 A Simple Embedded Server Example

This example program and makefile should work without any changes on a Linux or FreeBSD system. For other operating systems, minor changes will be needed. This example is designed to give enough details to understand the problem, without the clutter that is a necessary part of a real application.

To try out the example, create an `test_libmysqld' directory at the same level as the mysql-4.0 source directory. Save the `test_libmysqld.c' source and the `GNUmakefile' in the directory, and run GNU `make' from inside the `test_libmysqld' directory.

`test_libmysqld.c' 

/*
 * A simple example client, using the embedded MySQL server library
 */

#include <mysql.h>
#include <stdarg.h>
#include <stdio.h>
#include <stdlib.h>

MYSQL *db_connect(const char *dbname);
void db_disconnect(MYSQL *db);
void db_do_query(MYSQL *db, const char *query);

const char *server_groups[] = {
  "test_libmysqld_SERVER", "embedded", "server", NULL
};

int
main(int argc, char **argv)
{
  MYSQL *one, *two;

  /* mysql_server_init() must be called before any other mysql
   * functions.
   *
   * You can use mysql_server_init(0, NULL, NULL), and it will
   * initialise the server using groups = {
   *   "server", "embedded", NULL
   *  }.
   *
   * In your $HOME/.my.cnf file, you probably want to put:

[test_libmysqld_SERVER]
language = /path/to/source/of/mysql/sql/share/english

   * You could, of course, modify argc and argv before passing
   * them to this function.  Or you could create new ones in any
   * way you like.  But all of the arguments in argv (except for
   * argv[0], which is the program name) should be valid options
   * for the MySQL server.
   *
   * If you link this client against the normal mysqlclient
   * library, this function is just a stub that does nothing.
   */
  mysql_server_init(argc, argv, (char **)server_groups);

  one = db_connect("test");
  two = db_connect(NULL);

  db_do_query(one, "SHOW TABLE STATUS");
  db_do_query(two, "SHOW DATABASES");

  mysql_close(two);
  mysql_close(one);

  /* This must be called after all other mysql functions */
  mysql_server_end();

  exit(EXIT_SUCCESS);
}

static void
die(MYSQL *db, char *fmt, ...)
{
  va_list ap;
  va_start(ap, fmt);
  vfprintf(stderr, fmt, ap);
  va_end(ap);
  (void)putc('\n', stderr);
  if (db)
    db_disconnect(db);
  exit(EXIT_FAILURE);
}

MYSQL *
db_connect(const char *dbname)
{
  MYSQL *db = mysql_init(NULL);
  if (!db)
    die(db, "mysql_init failed: no memory");
  /*
   * Notice that the client and server use separate group names.
   * This is critical, because the server will not accept the
   * client's options, and vice versa.
   */
  mysql_options(db, MYSQL_READ_DEFAULT_GROUP, "test_libmysqld_CLIENT");
  if (!mysql_real_connect(db, NULL, NULL, NULL, dbname, 0, NULL, 0))
    die(db, "mysql_real_connect failed: %s", mysql_error(db));

  return db;
}

void
db_disconnect(MYSQL *db)
{
  mysql_close(db);
}

void
db_do_query(MYSQL *db, const char *query)
{
  if (mysql_query(db, query) != 0)
    goto err;

  if (mysql_field_count(db) > 0)
  {
    MYSQL_RES   *res;
    MYSQL_ROW    row, end_row;
    int num_fields;

    if (!(res = mysql_store_result(db)))
      goto err;
    num_fields = mysql_num_fields(res);
    while ((row = mysql_fetch_row(res)))
    {
      (void)fputs(">> ", stdout);
      for (end_row = row + num_fields; row < end_row; ++row)
        (void)printf("%s\t", row ? (char*)*row : "NULL");
      (void)fputc('\n', stdout);
    }
    (void)fputc('\n', stdout);
  }
  else
    (void)printf("Affected rows: %lld\n", mysql_affected_rows(db));

  return;

err:
  die(db, "db_do_query failed: %s [%s]", mysql_error(db), query);
}

`GNUmakefile' 

# This assumes the MySQL software is installed in /usr/local/mysql
inc      := /usr/local/mysql/include/mysql
lib      := /usr/local/mysql/lib

# If you have not installed the MySQL software yet, try this instead
#inc      := $(HOME)/mysql-4.0/include
#lib      := $(HOME)/mysql-4.0/libmysqld

CC       := gcc
CPPFLAGS := -I$(inc) -D_THREAD_SAFE -D_REENTRANT
CFLAGS   := -g -W -Wall
LDFLAGS  := -static
# You can change -lmysqld to -lmysqlclient to use the
# client/server library
LDLIBS    = -L$(lib) -lmysqld -lz -lm -lcrypt

ifneq (,$(shell grep FreeBSD /COPYRIGHT 2>/dev/null))
# FreeBSD
LDFLAGS += -pthread
else
# Assume Linux
LDLIBS += -lpthread
endif

# This works for simple one-file test programs
sources := $(wildcard *.c)
objects := $(patsubst %c,%o,$(sources))
targets := $(basename $(sources))

all: $(targets)

clean:
	rm -f $(targets) $(objects) *.core

8.4.9.7 Licensing the Embedded Server

The MySQL source code is covered by the GNU GPL license ( 「H GNU General Public License」節参照). One result of this is that any program which includes, by linking with libmysqld, the MySQL source code must be released as free software (under a license compatible with the GPL).

We encourage everyone to promote free software by releasing code under the GPL or a compatible license. For those who are not able to do this, another option is to purchase a commercial licence for the MySQL code from MySQL AB. For details, please see 「1.4.3 MySQL Licenses」節.

8.5 MySQL C++ APIs

MySQL Connector/C++ (or MySQL++) is the official MySQL API for C++. More information can be found at http://www.mysql.com/products/mysql++/.

8.5.1 Borland C++

You can compile the MySQL Windows source with Borland C++ 5.02. (The Windows source includes only projects for Microsoft VC++, for Borland C++ you have to do the project files yourself.)

One known problem with Borland C++ is that it uses a different structure alignment than VC++. This means that you will run into problems if you try to use the default libmysql.dll libraries (that was compiled with VC++) with Borland C++. You can do one of the following to avoid this problem.

8.6 MySQL Java Connectivity (JDBC)

There are 2 supported JDBC drivers for MySQL (the Connector/J driver and the Resin JDBC driver). You can find a copy of the Connector/J driver at http://www.mysql.com/products/connector-j/ and the Resin driver at http://www.caucho.com/projects/jdbc-mysql/index.xtp For documentation consult any JDBC documentation and the driver's own documentation for MySQL-specific features.

8.7 MySQL Python APIs

MySQLdb provides MySQL support for Python, compliant with the Python DB API version 2.0. It can be found at http://sourceforge.net/projects/mysql-python/.

8.8 MySQL Tcl APIs

MySQLtcl is a simple API for accessing a MySQL database server from the Tcl programming language. It can be found at http://www.xdobry.de/mysqltcl/.

8.9 MySQL Eiffel wrapper

Eiffel MySQL is an interface to the MySQL database server using the Eiffel programming language, written by Michael Ravits. It can be found at http://efsa.sourceforge.net/archive/ravits/mysql.htm.

You can also find this at: http://www.netpedia.net/hosting/newplayer/

8.10 MySQL Ruby API

以下のサイトに、Ruby の MySQL インターフェースがあります。

www.tmtm.org とみたまさひろ氏の Web ページ

Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja.texi.gz0100644000175100001560000271307210007316427015035 0ustar takeshisa^@manual.ja.texiZsE}旱 lｑ愧B-邃Z源頡夢ft<誡#Xd!找-埠Oiavf0鯊|BU娟d8題綿綿2該0+\av[灸X頼'RcUQ(l排Oy莓O窺榾-蘭螫m6yv暝僅0K 堋h8Vbx:x 乃芒yyf{psjIg%#!Y殘-1}UAnKLt[g(b]D 考^v uXi5!刪4E帽`O,嗾M[Vi,C\fz ZWYV揚_ph,8妖/VX)h>AH\+#v$W-荀nkV扞/~j1\彬Fo& l鈴Y#eKZ9ypPn e.fホ@PAR-:O\< #V4F泰霍粋Y剰OcjO珎tF!sA? yx[q+閇Z)aUX! xf_s-柞J-1X 背/&5yZ &S!蕁k GkT袞Y虜t#(a妥Fq( HVbMA弍\JhZ'暉c|h X惷uyY y《莅A+lj\7$$BGtP閊$_⊥ 8U邦"M\慨!3{ hB{54ｶ脂NQU65罰▼;G@\g幅蓍B]=l絶/uX4飭C.iciAM9踈LE4=<2*x淀陀4-rz倒GrV"ABZb;陥F z繽Q!i)`餒鰭;khgifSH典r9TY蕭靡{#dk*阪*趁'随^5e[2e挑&-T)~~~v|?z2Bjj@TI'P_DH6碵sW匚蜈|};>>#6帝?繼o/_]T滷8zj4D 襤qoSF QH瀲圃SNsP癜\8Or詐 H``}:]^m9 5x土磆K&D光x>麹8?#芟P'}檀? O H )!J礬摸>a91 yn-G|枷詰+<5d;3r彷o詔Huh錙穿@S9O%6榔暁詒鮹H芽"_Qdъ96jKK5u**zuFV.p$3 *y$l乾條s Y\xCZ/^&O]dZ$DRuI 楳租xE0:Kz蹴.N3[:?547 Z鮭靺@tv\a rXTa5ι]Tnztn \[ﾛ)Km@(に堽ー[]M鎮\箪6T瓶[G%鍛鮫Zp"9y-UAB*綮NPzZ?斧5rE(.G8лK@ＨeU*D?)1@\($HS篦'q>溟5答4蝠SC茜uZu3kCqへOxm0D茅|%^98 {BN LD>{%爭#$ 任Co8喫斟ｃxcB.жDP)H肺朽~Ey$*iE"FP 'Wn8皴Gv P_CM0討O+8 ~ 蚤^j=r印@晦#揺w賭!翹G穣 S1{弼PD6@@>Gwu7 1湛優Mfas, =柆)i_y未:O瘉濮4ヮB舒c q`Qg(*4娶lM.xp>{T{p;fK>'E(Qq e2lXg{G.0d:脊`烟 & s偬i蟀I璢o鉐晩d贅l^tl耗WfE 5滓Ie4-ZvL:f6*E%TY|Gy~{肭I\彙 E|*"RC&.K*c彷L,oY_e*Up_95~S債HGD~2鰲D塩cWV貎濘T椴0÷}`3辯(B^R^ 笳身eXole[%KJX@&qbf 笹,+)yJ"氤}zu薩{槃d攅f]А鵜終x=wN%{5 ぎ#召a.+"晶珎`R歡g$酖↑#Y ,\沃Ch@ ^ZeAap4啅DkeOW觜W_m跏9満豚Z[柤是6{u;5"|u理IC6Xp:cl皷デwz|車O厨榧殱孳ＤЇ尉簔w}O崫*u;]6KewK惹t^ qg九隰? 歎Sp姿G弓Nk)oD1;O,牙.OAn蝦?FC"<^屯>+并/GH朸gq韮612r4I*n!i絨4菁\考o 2#*彦y!.y:K\s贊]8_居_F=1祇'v$,\Yx1駸6t[鉢'水拌t!cF$y| =9vq6^I9R<-p)Ov鷽)斈*[j藕QzH亀<- O9 + ; Bg焉GDS迹tZ俸2 aF 6 LY戳｜b脇呆M|[ベ^詐#*迫t'[ W慾 GD0g4`Wxh0僅s"D隨qRPB恐[(憬z$m槭X"Cb zG缸逋%XR!M~kk|&W]{楫5Eだ館佰'3悔c6蘖h,gb[;倬IDq4M)曜^i v 準`1-G僥睇"!厶_SNoeY;Q@凄廢Q,YFQGL*W┨i _q%2!穉K^附@#O[鷄G@行&4P/D>w)9~5VL'棹1祉<hc]話噴嬰0i\4VJ［g0d9 7m[pnYfnA8 sJfI\AKK4’u>f]-N:H BT " z0a]4-|&)(J/迫*0 0t|!'!_#Nk 踟齎uyfm7Axpm^H檸[}4XeX`$8r2噌#窰A輩M鬱l<[3s<@Vq 60xq韻 )$σ15弑枝7 C.粕苙nM琅j/箴r2Iqm哘2 笄nt黼(^N^og砠藕[k漢剛M~洟TTi5P{杏紵W\ +0榑]Xn~ 擅fi奐OK%Y征LO;9$nsslS@4t`IvnヘM YGC呉D:JNwlEbd5 FsUx$錫F戮gx-% o:A4ﾎ~ ^ib**YxCg+鄒@!>位q1窟q\^ssMK$G-T@mX).*嫖VPgFrq韶"O6<z4d4 I7FQAk蜿c`:s跣 儕寓7AG8/tr854<486懷*dvuZ,l.Tc栴VRｰ敗7X?爿蛋Whざ凅#1U-M=H; 吮X~XM|U7索@|(@Ft~lW6-..n;n揖g)纎英!嶂Ь〜 u`[嗜樶察:X{抜w型搏ｧ"竟N苒Eyz!zYM22HDM*~;s漂Vォ/p:oVee?WME(I+o-M8hh>教)杯R*g9)"Ji8YJy爻v`voSJ襟\LogbEy恚縦虹G}o 叢WL-倚#- I菌_鑚vH頁gv,W1砂q臾"5pi} _NItHr WUJB隅:H:2_曙理 h憇iB！毋k$? S釟t<],@$/zf~濱3Dq${熨]M;x-J+M[+_E`p2NGz酎f'袒:tc{QPfis' 霖<'B諢斜嶂3^'SsGoc[t供Ky院K|ob,}咳Ｑnァn\ｸ`w{uG^i1n瓜hi=7梁驛 6'@TL:33EJI s鐔"#tEFN崎oVYJ%O插lK笆QtDx|!Wviy7v[qKZ^u遜XVM/ZyK3DQ!l短&4KBuiq2+SyZwJ%◆7.1O漉- ^L|I:00祺 9s`OKH sxn瓰tT & *R1!*瑳z;4|襦C$) }XY,i-~「I*_[jX諾%ブ"暹Ic o`sBK}q3 辜@|厄6數澄=A鱆登FC#楷埣.]U靆f`0dP徽燦8/迅f=息ш祉_N"/慾_:c! vQvn b 枠胄鉱};ズqup切~W* N_.Od=戛))培";AOgU法e% `b:掵:x gHZ!n H樺O3][Y:H-亶kJ圈z板\J#3M)_rr[d6cH7=Mh軣蔡u堡渚/覩5v/|w殺洲披涅竄e幸|鯵滷g56GHg[448w|U#退78$´O {"~J~縵Kd靺>鑒s/d4批WzU]im冢ky慙"P整Z ,!w1aU \Y撻 Oj湖T隔g=\ V嚀 ┃co%g24 弖V磋 GTE sE3G|2TH2UPZ,芒稱YfY(Q&r瘤cQκz;4へ訓_$HDmr"d2釧"1b`] + I7孵w{u[tHQ勿{t|B We郎E:_i牴o０qc7xIRd朕梧nDo*tr疚jfW*lE， c泉V"iY9蚪*QS屮m噛?9r社v{俥mk..UG@槫嘴UoUcC=CI|\aFHsXHlW Dd憺S4XTGhT9y猾-^(Q驚妄匿mY*h{v` KI]x―Pn囮?瑰<~衫韶S侯=FZ %}P猛ダ謖nf , E09"a1XkC+舫n9}S蜑t O5B'(N|減3*足a4Q>b樶bA7,@%u6?audy責P8L0倫_ PWWtveY?"` a)D友2uUgF諤P3鞏QJM k"gD|o| 站f冗ED吐uJ淦TzKI<o Z4U-`e6r=0F芟逓[渝圭淤 Q瞞%`T<1t"ｬl1{%4RE"|1oD 7> r速憔6=6爆',H p逅劭[pN&疣>+[H浙6V畭4zG=vYE 'RuqUMＰKEO1祠]J碁Bk}9多br1T珂A94弘[惻? 鰺Q-^q/d 葫U変倖a5 m:hL@*7yH*YGJvK$j~OW帙t\a+A's'= G5Bi tLsX僂UpOB[T.士dco悍G蔀８: .z\ 0\{G&Lio%s|l%h斫5(ki莎L絎1Lt拒E 7#VK,+;Z樵辨Z ~H:0Q忰(=@蝙i[ %鞭F瓧迷}蟒閨x譖g身u[O;MEh}-坪|c1档鱗_\曳|2JVQO瓩阻cXBX梹,炉L>X絽;x籤G^殷五鮗D wu斟2Xn!"R┓t4$ ]_j6屎\U)D|9P!.q"粁桁iU*株弛Ju@扞昊d) >DJ猴 A.D!瞠{袿欽#~@WR?R2G墹孑_mĝ鯏剽SN?-%%找! どFX2cKnI］オ%R.袤02K@b9oX,KJ$H \`I:;;qUdC}^: 究} 7ﾝ觚:搴5稈t pzRむlV葡&==(l\ ZN%i烋kop?冐[歔|sZ #漢8Gr ^AB/n稽32j)*FXK幾Z (I鍔, ,cQ? K狷+ h{"7w*@!>2)iC[O3jjb血R縄WQﾇ獎OYA礬N$⊆oJ-U(4憬p{GzXAhs)醴|3l3L[W怯oH <}P-;釉mXt掛Jn-'@w' 2}2絖覲t栂需I8慣F1g廾Bwk^nB槓柵$kSoSCn檍|ZnI]沐 6'scr螫儘%X琅@E1!8jNkb蛔i熟WU)z g毒z@@W7*q#hU0)o )鋭z20!PD+?^圻c\`w vp4;HbrGQhP_}a+T稜w珥%貮u 畝mT p[]]弓麗?y舷濶兆{|跚uc帶{筍鱆awwv|th叡0L嚔~皈&lqW蠧M:鍖|wK.Qb4<=a]麾逎&瞠2MiM紿[蕉馮#n誣欟сkC{錬?Z酔惱#?驀}mW閃]]:2z禹?.阯]"0N据ez頗邏毯6閧篁w{wq}ゑG住1i:fGVe!;s廬#m:CnヵP~v}8伺毯=i薩蝙>貍p攣誌索cO{e1VQ|(茯o4六珸\DめG:迺ub!6Co拭ED艤 bwT_/x坊v咫/J_~^u.雌]{C-臑{嘱謠EW泝|\|GC[4宍i^[.&V濤吁侵ﾆx罷+y喝枡vJi供=~5f近欸1|史+y}蜩E@xh:Nh%cIVu@2A氤(G?A蛄 +∨∽粕f苙z@ !sVm$u6}lO- >}Z刹-R 4斯=6 DT#EΥ)kmQ|k h]D吋V姦'j5URVP騏1 "n 0c蟄_<8z|/葦dz]k熊7: &狭WAXsW^HDD >_8u`e}4捏lM%f"o lQ6x _5_\楴jU-Hkz鏑e3}P憎\圜a K`(^w?D搗4'覈41逃V3_m\Y!S7Ft >/c-b]g$og#逐 D笏甥w鞐l持;xt1 Y6|/鰓0蔟 #eM揖O_怱qG掘 8Νl0采h\OV膽j/ [蝟#Q\.Fc_葺Bi4`k".{V )'{gU0嘗k}`As)"`KOGGYMq j坤D%SBr亭eP攅 >$ M/v@6洋,x#蓬bT h坪h幾%r冨kh(鍵T]恁弥-~O'k%隷5.G|]9c_3紳cy4 8szko<&e3| }z6l-z澣盖O^?y n誚1QgQ瀾S3gfSAF4｡:E*枢巵^x}莱-^z.Y閧LFuzcK9?@b讃Elh蜚ニojro,夂苙o-啄_Z窘国_ [c;殊狙uE[&%X廨3wk;&MHo,^-,gA)蝸(f麪蛆ぢM杲:WyMZ滲b璽.~篦<Ζ__I6Q紡 SA7s4d{?&;Y】Q^i5蟻0UQ>\3謫g覦/"綸榔Q究uZ釀S,yT?庇t$Fj~XS_RX~~j魄ﾒ莵Zp+ 釦bT場г;sGqy暝莢({J7/o彰6~ｉc<{s乾eFpd熱鷽;xMf+ 廸]忠5Pc>嘱G K18lie}v謌kPW~oS5'd體+gd紮r?^W@j&MLfcy@2 O1涌dR4nY!y^贈0|UXA::S恁h# %4S5K朦o\~'b'(P嗣iMLCXgW譖7N[ O &K~W08a硬%_s SQθf]報NL92g苹駕xqN /1eA媚}6郵T[Ap_?h%,DRY]絲窮p;z9_hr壇k/\kc&eD }過覓GORRP\Dp乃2鵜Y+囘Y@$墺g6(T{痛7齬w奧Kq\_Z槐~v矧x6罔stTqQv/r濆彈!s勅U┸t鄲~qJ7~yy.+L84w,怦.j^窺保$De膈球S_t 垂誕k3x9^XлZ_Y捩勍 燐v s_X磨pW U|歇9_ a愾遑厭Z/v pNb Cu覘~U@5酖+K %L 0'~yelw3-劃P珮_\>=xKw笊M夥ut" Lb誨Uo@A鮇O/u\N^J<@![髮7Nm|q[ x0yc?0D]O7pn/] b怡磐G_$聡J檮J墫2d傍6w505^vven戌_/c c&G帝D." j7弭s:Ag麥5,靠K(plQ鐔SgK27N!搓@*亙6筝XP 饂yK=P銀6oivxF腹k滿0[?^y  fV8,a;\籌f恚7AJｷs'tgвv燔0K' ~?b'a嗚3>{緬~i(庁x帚a%6秕p`J.`RrQ`|`>dD晶+t0x Z鼡C猥h.7Ok對脅熕eS*U=靨d舶В!P({ ﾐCTvcV i$"L末 # .a>クL掾~蠻W!嫋U)蚓 i]prNF(!%lZ手!X4鮖zr[TM[勣!y穢:)⊃陀IRr%k-舎刷:iq++W靴8Wp1跌[ o(0n桃8+G8Hhu0寤K8笵)h割1"=^[ド.q曲~!;x%OM!7N)勲k`NWJI矩M_楔qu潭-ecF %nY )}fFg7$N^`栢 X.2mA麻I"cs ~)H Rqh$GG|J烈asnv艟.F>v7,K墳X8'!趾J2R志:7 [2s:+7w*j^psND1d2 [j%メ$:] E｝SLCh~Uc kx ~-)曄ZEE h酩1:,F; )h熈x瞠9良4悪еo島m孰纓- w5儀\-i筏s`万越gox「wl6NGupzZ崩 IW第e\>~}gn]OZt}@f秤vMXz7L} f歓4R亶}-q8 N6`C}.o桜,K'L肛げMa rr/n_邃>.v c2疉>}1誑JB膳vAO$滉'凌~#$$HGS7xP_龍^W>bmZ漓苑Bir,*V3>W^?fs児G!ZET4d~蒸-白;S芷5KEryぺl8棄i6泊@)C鴬SJ3笶o!p7qt=Q^~.}2v錦Dfr=k07>R ,<蛮$,I|L估wghs檄祗軅AI歿~Qof,@b@goB椛椹XR9]Jp会*j.u}D&狭t0鑒毎#_/{W,y:GU匂`(G?条 .U;r冬z(嶺y;粱WZ[n=wJ P%x貯02j楠X {8煢bv蛞巾jN2M=措wp$^餘餔8v>HC(KO/=^3LGhOWhNZ窘z(螳x}駭i.則芯\翰n阯[n犠渠Vo^pd? }u N爲~ fADB ヵX4k s6Wp弄 $xF励bs-Zc[戮HY帳} 験x#N=躪kG Ziv笘T[寫iuQL{,w-z 彿裘6侯r:c T9BylGq,air短捍),錣椈v6>%]sl`:o*嵒Wy0tz7z灌M +m)^s  c, 治:迂(|捻ovR柿7笳5[WH"Ff`!7P@y蘋皇*TS糜雕5T;MK.煤k6岼縉L輔62鬚 .*5咥|宍xg状'!7怎估tG'7IGsue$ D劈cC楫IX躍ЩZUｆA叶{彪|)凱K r\sg兌遷Cx 組nq?k7<\04'O#ｉo_痼Pi$銚q南?n辞烋7XWL' iZ袗eKnmK;昃Dy=欅斫胖&fKjLh=p釧oQvaDl至a$CgP ^ !4hx4Q dT=/艙Pm$r宥&mu-FF 8l|h_F 鐇'FaK瑾 畆uEU TX9pT曼| Wi<疚IGdHv}e~0P)(Ra,lxa*^@ P %U/Ugp丗u昔K5\/Ur0<[jCα.!3/貯憫g cETW 端8c$\9ﾂ L`NJZQ 牘4Z7@P Q○筆U G縺cr.1堝F恨ザxE礫V照賻-<],RP9B3A\q}麌CSg9 sHC`'¬梏峻,I/!0=[%嗷藥KY1U哘┓P0!e'Pk?1]5H/Tx浣hhnK+dVNn咲+徼7+xB僵 ^>-8C洞6+c/慰7!皚(ek萸c├O.B峅Jo迄厮瀞x4g琲SvaHrRT2vF旦,RP0J廝Rzf ^%^ ^b+Q剽l;D PDK噺猾*鼈r$JC砌D8 Cj^k<%">戮|TJE茯S耻hx 亦QOl 8]E$KF埈條-Щ hh6 TH9櫨:K曩6NR3故逼.rXs@9,(7よq閥.>Sh葛f堋hn ysD斫"渫F K$Q,0=咄u好e)ZH疫^*鸕gjb於zd斜6'Ql恋hPG'wFx亰6YaH].&*:r"eU N桓Mu鬨>4GXF V_8{(５k\=碣\k絎>7廖q"ok豊-vJ嶬mg5i"窒q)o|W:ラR<$;倶{?yhO^2b.V"7O= s KcB.1F1UXpX7FK|揶K NU(V燕zT3嬬;V昶k'8$5Ml +朸珮韵CqWX翹 Q?'8進*EH =BV*SOtxgi)雙Gｺ卸~8Μ'R]QZ4jQ桁 蹣縣 %瞹Y=ｇO, `8BRw鈩Z}qT4rr$cX=墓QRv嘴罕敵EhW-8ａ途q`/W*遖k鴎UZN_P k~b If`D8+8┴R-9,,rpYq誰!)8c$zj羸oC s&\+郡3X +Y%z]Li|jU|T8 迂倪壜pnKa >y2 【{dRc=dxUhN=yJ%o,p=2cGs雰@mBt{p =f羽A *1在(G4 FK@ OqW轆D_勧J&Pf/毟飄7Y B 賭茗+fIutcq棆Si&#MTl莢: 0j 7p=@~箝M0椡vk,倨zC孜mρw\B dxbQ讓j#,;9纉9校ib'TJ堂lxtaIYfr寥(9,5g<8Z=7 `g44 剩-贋M都"aEFU5T&5_2Yy]8c瓮#i襞 jBix翔yW~tp(xU%'&iLЧ麈泝 8蓿Q錯\峩柵83哺$VN笠MD=INi`:XHsi/&Z@H]e蜘-F|q[BPP%Pw{\V9TacpX1q*4-QX9bJ_B{Rjπ犖Ｅ!Q-犹Ne{< + !MgβAgf籌(VK:5峇CUF@| 3"o7vqWG洟hFa|7Bc;粉蛇F-謗fHKヶF倡tch|POch\+繝.Ly81t#:mH4^'.WTEd齟e@0T*= Y+x@古3F Y-晧P1(_jwN砌褻J( 'R彦PB1r$c}d!Ю>xv錚7謬re康c 按o青oi善E!X耒`TW*R沃+ &kG1N笏Hﾂu57nlJ H.iod遙__G％AQE*ｑ蒼%c束俸yI価tz(た塾縹^|7%詐1|嬪o}}Dc #慝G| 隙Qg)]通輕@YE.l侏C鼠+a^.,bg寄縣MbkY$:厖繧A*FM kDs斤ｦ亨XX幡h舉紂4<甍R碼`D I誓Hn n2`璋KzU}%.PE*G%{t馥rbH+(" AH }r%j沼岨府鍖?T.yf+q<N帆mx1>spC*b.溝^m oaL!9N+M ' WL荏b癆蹐&(\*:#牒mt吹抛9>y8愼:聲+V(XX1v-QsHeU!+c"q:雜厶8pPE$O` 89%@Q}Nh&@2%Phn;$>i+Z悪{J扎Y@D|(^椣d翦\n#h+)Bv8<E例(#K金M便`}y2iIv8Z2`e N-;$$FY+tI+NvHGaEp(侃@QpbZriBigYL>斫変冫4o/i`l 9|E2/N:^BMC"杓I3j6q瞭Fdv'C9 8BMa%酖矚0]幔\GTfRLZ4hSxcq|Q  テ;n贔 57oI]Iei嫦dhm oECp)~^漉擽/頑h!OQl6'覗に|( 儕O綏4T{lhd4lJDK崗qB42|cp 4楼m箋R1_1S'蝿zi -鴨HoFuQ n6AY5ゞRp;A*xj4噫&;: Td舅0I殤q PRLn寰@ c&:Za 怜{¢49J(!*AZw{C;付/詑Q9Am vib餬Y柳 6}-R倬檄AsWe<67:畝ＢZhm旁bD16jD捉<0|Bs JX1懍b M]SP(` Ke4g慍&Qa枸A&F翦４篳u<伏?y(DWD=%F@蘰 &o∽I耿看肅戒U TZ|{土LDy<詔pI窗k q|5)d牾7Le^溪潘_hR E5yP迯@々g>舛sYB_B4\優WJqu_N s,m褂Y槞s幕霖Ogﾅ[Xu&量U)qRcc wn~|馥Wph_, 韆hH彰T7蘊P{nkn僅]列|]拷d郢憖`5蒼h]]?3 x姥t^7ﾁ,天[F賊碓y~ 苟:_千c 滄 -Tt灼q颱∬二+ノN# ?帝1MEk贍 P j.^9|,iJ *vy遅弩5BZEt[\;絃鰆'皚IZ馥C陂]jBT#h9*^%1@濬kD^Z悉v蛹嵌8/R ラhr29,BK<婁竏e8靡.塹ZE1!n＜搭XubuY8蔚9  31!Am,|xf%af費FS+VsZp[鑛文l*" WY爨枚哂% O-|帥CFC銚rS飆o:EsrlU6髄@Jcfk竟RgPX5E_^綾(殕1U;7}2.カ0刑7堋M]Nk\ 巒nJ笳`$:!%n+瑳萩通O@'N+,< 拍N\G>;啖酪o憔屈醒産9W衽k1}f^[Z *%H||-K pdEIOo8%OBZm1聖袞9,陟J?F0egg點K"わaF◎Ukl+疾廛皆q/Dch護寇6 級L0m批\R(XR q&_蔭9t7^-uOrTRY@>9!錮)軈-"zIKo#cr& 4氏ko"K @靆w俤 *Jdw|geNZ 救_茶瓶蜉渤=麪曝仭Nf陳OBWF妹9* |孛NZь<0K-f}6R~F$狢|:_&*K@!勞]m|書m2+ u=' yC諾暑\[;{;=S怐唱t1OUKm,Z-q礙Kc^0Fru5FT倒羔潯Dl嘲A i^WsD$Qs錦DF|t蘢鄍ki~硼O禳bg#fc5*< 哇%{th}m]mD6ESe:t楳潘g蘭 &B0贔醒?pfEG懽[n4f+B敍*@漬称qg$退@臉`w訓"M3@W`7Ns%#4+＋|+1 畳;]'BXbM.,@朗捉榠閑|?苙^=[H8/^虧(Ze*wRQwu9fC ^z蓆綱2=稜矜wS-o;t飮7Hr>AHy .!>q讚BB稽F *Ws仮p臺Oa^:VWKR /th+*吁n亮nV ｀<)a;jfi_F∴H~6.覆TW>eGg竰UR-{] 翕i!裝MjZ洋癲:F59O7j縺])X粲癘埀挂=~ T>PtK;薄shP{LxhaBz勝JW@z妊kVtQH u顏 ho\^鞆鐶吶7R%cN Sc(祢劾]d+恷正C nQf{−=QuPB"+q}e総樸悗:f U!鞣6聲<5~=E-0-Ra吶%jQk={菓鬟V呈a <Aa6爪儖bFgm觸jS保lMBV.6?fZRaW_7I6Nｱ98賜Y)OF !9Rv)F羞v3: 睇Z>!+'l1q;3wd席{,趣UJ<拑較AE5$S5蚪垣"n"PpX)孺 \ SjGg&<^g%q?蝙kC崚?擢 W*實,\昴g*紲(温猯I4o=諞翡?肆2L5Mrk]-to*HM4[Eil悳g$uIoA:#頗XLPkN U*ktQETa4q\j巵蛍艫[*+Z17cRru FhUt"*#clxn)aJ QF瓸P\]ｇ0K.櫺r羞[+_D凾恷*{依T'7g蘖飲1Tf6_-徐Y艢$Nv虔夙靄J|>x惑 帛ラp商g`7PL纓蠖/存x+3騷9+柞.A#浄JNZJ6喞cN )kn>Pr忱eZQ`m+5%aXHuMK沾9z廻$+5qm-^誤IK崘TRo5樶7]ai竃局詑(窗常q%Tp笥[l &F@*%國9a]>vzycvirMxmxm.頭r陶;}I 通渡Q4E.\`i4(w7KVP5 I伶!n陲^屮輻.[lY2@\^v疵タs亂H7O vii?z yc7f`s_5wHR5舟榛J\暉式o戰 h"件捩,伴q-)/`7z B悩"$蒹(6X何**^慎o 豆\ali{X糘bVF柢,Mtaz[U.*\u Z@}v1_夐?7^e 6Wk(Nh|軅~R 8|kX捻疎 W[P&paYlY籌賁]?K 4>"W勉怕~砂;v鰺 Ow薬峯悶G@室\A57e蔟s0|A茅?to滾:GNfa+`zNMoPWB[o$lWzFCl;|K^1t晁)gg$s[76威黷+.l &">獎驫+ j<`9}o.B '=$s=9ばAI2sy.3'E叢$甦rK3}b8翔?KNiqLZp淕*"cU*"8Q%WO孫ト-\QgI:gmx(浴R行x3(q笘K.T＠O畸::[~LeK-p0,Ld8A見n$雫1{{<惧昃C[笳Faam'[H'af坊GRW;2"8HdA蟯KtC,Laqz壙e[[M逋G疳p栲Y O陬Cq2IZ?u=7`駄A6_Q]首t!筋崑yN杉R+0/釋m'y8 z蚣飮v 寄!8KX咤荏B蝿4?<需醸R,快`蠱}W0AW輪!j嵋KIラ'~%57/zFN結r%0)Ga\>vm6SAl痴號/5Bmo!-淳Fy'X|-g2i裝`ge/慧(Wt5V辺 剿n|\O}O荘鉄B樂蜃_oxd愁@衷Y$2 團S1 rY與m4窒_ds,塲\垠9EUOφWi元)oヴnl蠢)7x~N<1@ォ新Oz=^'謨U DN粒n_v粁G+wSv広s匙K+oN樅C承j-RyO耿鰐5i.嘗e8圈 \ＨnOa;nC) <9#GE徼藍 /勵d奉v:4a8nd8Z*K拒 閔/(Jra#迅 nW鹽l{1像豁+t 外1靠隅竚"h3 r肴idIC斈2 f須$.B m79vNM].ccMPaXiG:|@Ckg~qu33証l} 辧._ 辱冀8$3 wXS貢ｸ拌Xo*nVtdGRll~BWFC8BP7h[?o8s@.}(VJB_/~npBz~奔Fcq鵞T >v症':o庭or m喪pg~+杳lRdo]l[.N勾w閥d=~3*]ybu#孟fmk(:(pY:X凛OW勳d^^AuxPp{$ij4:yt,%Lb[~積I{MRtx 戻L;qbU畔ｴwG$l魍Jgoi)=\$[Q~鏥c^xB1x+(&$bmQ.綟9$` "パtmM/梁Zy鑾gbG iT N=qN竭撚vG68*^筱=jr4臚5I<|8KOQ;聾^p嚀薺?H/P~[騫俶)6l xka7t2 :xVqOr脹泉;XK$n]q=笙眥旁7oy^L*,]y:?)i乞{"#qvf?Vl繃YW耘&'滲 j剽4\茸n畳>~役uCi/jtCm察vHsD9DR 3/目2we/^QgZi洵狄贖{盲8政`O瓱h碯K@zdq<閘{*~ 徹`|_浸{摸//7| u秉_KEd:lmuh乞K7較ルW>ぴ9hnmx懋鵑U刎0睛G"[+O[W(  `c茂Y:Lyii}#覓nT 7Y薯iltD鞭b-b12窗W澪鰉ぢ[W6Wb府LlP0F@1N@_D\99}O 久~Ks M潺廚& Z+|徙 SV2PtH" theVv亙斯^楮K5柞{卦Ql1拜-"3IRn Ycx'W/:v?jTr8KlfiｾT $O^飮r!\qc.>PMW! scy*$H[ec=f8M=$i,1H&"RNyEsq,f@;|瞞%x妛甓淀8pv{Y&hm!-羣F*?X鉱r tM己-I蕨kk帽e4nbq6nMa久2|血 -.)P惇VB$賀欒u著 {V 渠≦CN#`H,v垠Y|,dN嶝a;Z6h_吟f]| $R8%S'a4w9I&pRば,9B豺{NH 1s-FK);+b>FuD{\a66患Kme()黐十]o ブL{8ug(h]Al拡6餌避{,(X}$棺9迩0泪?t淙 $?f#F L1\Y4]竄\cUg|#+棲_cI 輜*/`?52aWOU羌E#忱:Y?e^57g2楢EaE$U%bRJF摧ESjq@覦窰mg+\eKk限zvh+0,縞U澳医W+\鮭Z\G%b`}溘翦怫9/L6x# 帰|7x濶瓊=^5闍}`慵颪~'字c畆Lyo燼COFcpR噋邵rQ;rWxm枝t'Kode妍譌G%<H;&|w&%gQ)"抵N_CP砕蒹醒r疼q}7l努Tm艘甬a\pC4=D'b.y7荏Vc 5_譽icsyKL|-Y鱚b\"益*8*p[;}膨l8`>+h-(d_ｸj_Mzqfis\ S葯O#c,F8AE .u!7PCzMa偈\ra!7Y峨/]D>$LDOaY )-盃T'qvVd" )so[膤'3乾?`'Y< g<.擧l獺/@ZJfm俵.滔o"_pEH4淒僅[繧\r疱{W_x2a誰,d泓畛u蝴2{l-幵o蒟 圍"u4% '絎s].*{J奧靺t甄苡tS娠qk蓚fp辿0逕狩f VD3#閂F~q觜xljq|射QDC狗In V)K契Р歔nu┿p艝4U3sv以肴%\8+}go憮%や鯊*]-W牝QLK$慌v2jrV54~桓O} 訶L併ZhA,pSJ|" O滌q{/q`鳧mUn;w/各4竄1bOaEi`7 ?C屹o'Ys'a7HR,A?M謾裼廳棊g_fB2豺NYeZ F&6-->Er珥/裨G8yD}}k-/柾_ev%US!A2g晩w.b:KHA!iu&3?ca螢xDO莇5dgE曾哩@>'拜坑kRRc"遡vp4+能黍cc胙 銓2冉Wg 祁ф.若gMy緑/K.S傘mQ\)[vZXhE18z絎q@p^LD~b=z~f尿6:(?<溺L婢 P '1HN莠H&絅饂y!9谷査kBＱ@ukL西褥=~>1r2/Z 燎i oIn<府9S.N勗nvAX+*;GPm%6R鰉"D<'6)恷vDo]m`M犧h4AT雎1 1%_ 撚G-WxS{'蔬;=< 桜靴隔jq!tNn@.圄e~*MDXk%5珮C争&辯P $喜蟾卷iIrヾqRyrDCCvWl K1蠹8慴tgd]0;2韈)騎s>%O^MN弘 "8U5_鵠.F}Y+鐫輾Ze=od;/n7$ V=<$!mX粢u{Z*agaS彫|w`閇祭+GG'迎W(."''G/.]l^事 Uv`_G& }頑S'=q耿儺聨9 Hx辜O6m*{ .0cz4-しx*{z黜QSだ5eGcP u7Y({ [TKcM}2}@N勸鴒稽L瀁nm&&t共8u66";Xj:?s~ｰ捶艮lN%`O~W&r#棋w頷#aLr5LI&! DO斗hY2-彰 _ e%ZL6ls4振|/BD擂/'<<:'3n]祐杳u'mf1J5~X沺新卞奥SE ЖZH0:6-%-H籖6OHKvJ6xB~ﾈ}q1z`翡0m莱1狠6vD|鳰g qnGp6%.SNB(擶-\+P!x4鼇c&]|! ;lkGb打7膚=穂U%M'M凪K≒Y"鐚>kK忻s抵:)' 版戈褪1凌x謔D 7>ＩaS^駒W4bhfu銜-閂lzj0;,}`,S援BlR56MDak~"喞麗$& `. A71оB&鰐c yC{]wc;H~G.宸wU*\泥N笈^ M紀x笨俣g]idC @笥婪;僣AZ,/D|げ3;Q‖VM嘸 p9p*vackG7jMm寢l%vDN&Ay_C}h枚vppF5o| p詒mAs@mw#目a1s4M;両A|惚]{zENd?絃 5:\к晄|5励Y826９qH湯麩q=u僮zc*:|鮭-mM 6H(>>c{m~oX;蓐 0佯娑 帽戸弾 j}#3粒X7UM7? 拏P犠 Z\< NomL焦 u^6GHqb追w,gn 0|l茣U.y↓I_d:掣任+蓙NzGjN[o廩.+@RlSc 9^W篳c+?繪$Yu劬P.6萱vC0"Y,q W!O謨b奄OKL@塗\N蒭杵nB\hj 淇5A＾撒涵 s:wiP癜W鰭l#皆]躪[X層ZXxo?E酣O"("X[4Vcv8羌xX10-w慓;_/n咸R療F> #梺r鮓r嵶E bF!%Fi4Unb巡}匳宝S璞沂涯I4穿lg\膰Wg&={vvEe^將f@"2pU.壯 匆&忖]*DEgup湎'`afYr穆at´S9H( 釶83N+GGNY%Z趣 KQV&eL[[C+mOj*X& ( 維1uK =六展/D_|%p <蹈?n粧)8pRJu[n}6 S6!\榲廢`jеo- 氾_or}OWN迭叶'.釟宝 3$lrAW!o]_7k$E9u袿厰K鯒飄3W(吽唸睡_うvh{0垤wY!!ＵMc9_}O<%U G買/良 KW嚆R %+{XW1|傅2&$R zＧpwu9=ai y vdT}v鉈玲e衫0F=L< l7.蹙蜀0_\wu`4,,紘^pT(e4a9z:hDoi9ギ;\$x=^mLj)賑賈4&徇f_I3e*3wT-s1B攪+Q6[XB F6Gf%擲Ee藁%載l I荏I 正y鬧礎墸 %o< B軾vO?斈L5晢w;pq?}HT寡kbx 鎭]_翕Ik%<C!Dw{ v贖kw0}`_g38GdAKZ離髯y{據Xk8~!zNx.$=@f Sz高)|tC,7d逵闔9tw 5w:{EΕ朷O跫{I碧y壱 a!j 間'{[b5$_途D8a6B1#42|DI'oB? 6U 磽c# O<sdx=H6 V珱ucD杞?{5`SS)]砂}A漾A`D歡 樽XRKv湫戸鯏??孰d,壞w偸V9熬Y4{;1s7j今J.&c;寰o5Xh屐開k7g/T芋^r´lwX闔_+nd%ON礪蠧/XO D[sg\^俐拑釿滕)ehI 蝴`W'L=}`O_3san笹</x#槹忸@php 羃$5 j y k&N+'4_5鑪淮>Zc散k3>濱D{Z^_8vFE;%;>h!VS渣PE疳x8,Z/^GH2H g炯2Felj/\J頬斷j; _*c5s*┼&lD)設|}b\_9駒/.sY'O04 d┴4-W>0W@rnbW7}zda!赫k/BNb(.+麾c o_~BO(Rб5@SpA択幎W"駲1弧o@閏t慵\&j_`勿v躾M>^\Dc{植棡放'JK喃6Wny%^u52PVy7巣Sz跌77 ;7ws?厩Jv三p) F刪B9тNXNe%Nd[r|!油fqsTm鏖捏ザ応勉SdLFUdmOtt'*T羞v_ひ7HU2B*r|pN`_}u w寳2蜿汁?贐z3謾evsF茶 HSHzv3k|l*犯翹鐶ｒN劔}沾'9cO氏M(9 禿bUJ.K凧=zZ'k26!R慂 ecpY咋邦(I礑拝;割q!脊|澗裃|可bＨ$# @]r釟賤%^0b岱眩瀝9歇UGD7w拿 D :螽IXhr奪蒸QZF独9xV+高2欽菓{見苟}}:泓{9v <殼煥4叺桟cO{_W兼EW捲BZ8 `a紬邦}n}f酒鰉毫EjR0莓 VF献AZki8'QS\K )荒Iv栯R;E椨~唐pA0:uai<風酊&9k闃cOrt> X鰔;恷r泰 }l猥jZ3?>洒p'|t疳QナF鑿6>撈c?A5匱Qy>5[%z姚D V60Dx@D-62Zo#溪|vqxO框QH糟3I2M0Nf.w##磽tg婁^{ny/qA覃Ow噌,-jq黏┛M 0L X8xTm`i5uYI-詐vT猩U熱h.y慎rE|几棟qk$Et渠服^H9坐闍OfU[^387/Ld枇Y}a %[#sT6JgQhxk髞m誥傴*cF'杁噤 BQS掟n 'sb[R^f4%d耆v%U侶8P.@WwO"x8 `)l3R7?AR?*#吾adxV插qw星 oF O露)WZM#RAxK2 s瞿%%!u7$EbQ9懃EO q旱n鑽#w屓羆0D> %{繆b冪jB柩i鍬Ｉ*xNKn絵憎} 葡u=鰕NA粳Xd)它5[>YD6tW # ]3)眤Y 7材xV)Oi-消/絅芯^Gju R2@bBdEQ lJ.MJ?1sk$Y" vx潰f鍋uXP酉;甅G$F洲]$1sE騏7(@4 嚥7O多^&;2{wF9)s` u'y]n|偶抬鶏穀鱠專房}2i觚ai*4N[;甍l4 L 荻瓶.i7 v庫WNｑ#p vd逖Z~i拍糂闌hl泛'@柝+h診w e1u黛\} a/秣>pvpcW安} 躁}N驃.jUFB畛R臀r$?淨JN/后誇ﾏ<%f脈"虔る~BVVn.瘻g|sB娥r2$C:R 糯 θbBW材i&=0TO~S冏0c碣^dn|uC,z,]冩1,佞xG4f寃]F# 賭v膣=T 冽e謇j斈風逅u_9ti葎m樗) :vJH [%4,訃鏐#Ya=DK盡5;QZk*@2KCV苜K?C柾^=q{4s阯lL7V fk[%'3Am<z汀rRS?>剩僚=]S+j]Y`Sb楜3 張FA.LQErE=]ǵMｳ'刧;3I3孅"|7ig狎g_DP7 ,uM待-38.>9釈者V+電%鐐).o?Wk)'L疲jt "謖匂`⇔u^G[経M7aH#)nWa4玖浜_88e} 攸$(婁抱6齎岱x迥瞎]篩稔Yvu46_|_?+:n ]u]剥a161/囁7匈豺*>ﾟ丁K豎agkW|&eW怩OD1kqS聒9Ir'C@EF*c/h犖J C體2P穗c1輦(8m6vw x駲艪M 盞 *`+Q\+I8U'嚮wr%TkT署J&_*SM榱鮒餡 @ik輅襃F;(夫vrcE搨x迺7尚f7i'w+mD 8]3娉jB~Wx4粡uvw+R F劍M8-鷂F4-D>Nq8抂 ^Fu榧zfI鐚Qn. JVp]鉉(u餤+d泊?d T*Z+'Zq6`KWiicgQ"卆=両&BqJyy#~5by嘯UQy-F足U最完%突K2網 RC*5g\t%V?粗嚠<て't#i3Ua榿4Ytu'享圜 lB殄*K(9(G#hf*:ο7fPfN 会U+覺RER1e_〒 "9B 8夐. vR nBeQEр[.;8 jmT娉ＡpXanQV^H5^ThI,, 瑪敞(*|'+ Y*BW|FFUATJ捍rエ{嶺 mx4asCu9j,仲1ACxX - )k jUBa.4 Tp?HlU9`枠 "b酸 `D蹙V 益'h髑B>PCz'棕F!S~x2GZI´<殆殫Pri`7qv>]y8 |nhy8 +W*kor" 緯v+ 秬 Xy E y/xFQH/ 柏LPr[E0CL'.T'K纜H-縡t!;令P4%圈h@ OD-06T>X@Y靤p]@槫J% 6+-G塢D鵑鶤G'/0 + 'H{Y-M顫 9:%-F 植s?A隸gc!>e9X倹ejょpJT bBYBXq$Z)>WgXE.UE7ei&篌富8貌々# }P>EM嬋q*оm2[^8S,W"被1!lL'ａ17v陂ﾒ%WKa\vT葭 =!;?O磽p戈S?'FKQpXo+蚫J4刋sc曝H=A="純{Y12@%UぢajtP鮹:顯R.饒"'損z91)%'雑!S凧冥P染涜$=:p~LZ}av;PPZ@酎γ⊥s玄jtBxMXi * 齡 c%&f}u6o0nEУG5m"学t1O7MAiY+牀4.|+3s[NQ早EHTFeX.9~= mD'dDH@W3D``G}攷 t4r&u%dpDomv珀J>Y9%NIj)al1磑XOW鯊BTｪ2@9 @ px8歩1姓JI5LkｅUN AIhY肄ue6 gy史W9]O]s藾8p('5`cクD對O?~7H,Pj碇o72y8賊J箟u~f~7A]:aG=酣QW誉r6B齧朱8燈KJ畝\怒R(3凍)濆OQ\^:A%:69*m/h3价;\HrQu#>69n]LY#3m呎VSХ.6*^rFY揖}-^6Dbbm`rd汳E[>O剛q7)w{%ot#売5.葎指`0 F4n-rﾝ|gPz.mJ;qﾗ[7z6@ X#I4Rq(Po%iW}1N莵)Oy$(0"K(2注岾6F+Jb7#d@=i)徹tS&G[I)棺=*鋼ﾆL7&*W@ }x竄縞urJvpf|厖mqFF4!eA羽<除G齬N"eu!h q:吸E7 4飛Psp0J5U4.h>gP慕I*<|!≡拒躍Fv4b &K晢,jWmOBQ%e現浸臧*j,^ 7LGbr L"j%pL2 KJex$*k9):d0 鞫靡 D0s8AEdT鰤@l9zN杓nF:擢法据!U滾T;+aM6u\G5c='H 鞜P膝47.L稽 H0Jq曽tr綰&/*3qYG 釐q倍4αW_#甑*0UaRp\v]諛c?,0mlaz[2ﾇ7F_39 9d7pLdH^UXf!Fi1&MN)0cbo([$-tMNr$g 譴N_[BK' I0,Uqjj)M.*DUb呆)朕PVB榿="葡1dsXX S\3e9枴tH Q 芫e( 聞vP!F6YGG拈艾狭旒8萋h@,hTIjuj(^*I'猶c |GUEa%_→@cv]%h.Yiヂ'Re*h%c")YT(q!峰8dﾆ飄\6囲i$犠 T英djtB^4RW'u"4& 味l_bF L0w4,礪VPt2遜厘:7 鍖Tjc函x2pfAI[ (rv 7T`adA).;-14搬6絅^*W`0?1kTc:D6w6鵡-c{QOz,6嗤A2'l;r ofй cfPT@6UsWbｙU坦{=;vO栂idv#惑]I6_MA格hk妛C3/2}酋++irx3_筒碾:+HTRlL{＄^ ゜eEpP" B^m $：0脳OhC{1Hl快Po| f粗G-淕]+"+ 悩N_*,叶xPD寥YXl. +tR\]Qjmw6T矗\h>W! 'Ak亰txs枸p~%がvre瀰~z瑚R4h&c }癢 p^\荏氛0(ポ.'$b@hk Z攷q, U$ Dc$qkU, Oa=生P(ya甕Ew鰍/:yDTxO ^h4 c粽.Gh朱 w C7,WoPBU/C}E鐃7 Ｘ@鰄U 0|Ｗ8.0x拗ヱrそj^LW[g淡*&G,劣JiX泥$^+澁B +>z : aEr ZJWDup} yH)3M-YC2s \8c:CT薪5e+ 4 咎鐓2E\l;9sLdnE cC@x>^并鏝 (虎,!T3Dt泗uQw*+U8銹p{'+7<%9 Fl3靫/ML{z#4U`$X鮓n<脹_@>lnQ;E冰烏液婁妙5W`xck遲 g牒U?5>i3M!?N騾go~革av t3$V窒:旙:Pgyh/_y `^P釜 3}拂`四Fp&y9`=\弭w@yh4R仁K(mg|蛆37fN`駐~wKd8bPf*DJ1BtkA[柧珎朽*hm/供網6\+'4后貰a1tfC&_'5M{6F曦0U屬&yS很5?vl/;`)P管A迎sa躯鐃&# kc)Ms/We隰!褓l.S#oYo['W,[ cO該.L汝蒙5;布癧,鷄鐃斑会邊vb?$$６bZ癡eQh4LP`TxT(>;'(H1罰Z';AM#(63e !1y雨;h|pe ;@Q;"A渮n5f兢P奮A9)Nl0 -揀 &9dc>P$Y )gGD:P(\kI2K韻R：0Z憺`:".PD猟嬬}tﾝxztD*~LuwL0卑c3Jk鞐(v=;>q$XIsU$/R攴1o;CFK &t>!- F_">=MCVi_'*O]^[dUZ>X+V?＊rX5%jt嘗(驍hD} 0cdu闘]w}+惱]zoPn(`4rxP>Ｐ%F挟4"v"-)E#xゆ軈香br7~9/!Gc#[i(okccpπW g6> ((δ(In7e/ 1E/K,9d＼zr葉H 0蓍}AN(A2605k6+目PJ8[%8l&莠ュ;牡&◎xR沮fTW!B6{R*W≒Hut*yy&YS嚥蕎j熱Mo%+QxBzx[_俟S,W棧N蔽rupw<褥S )}P4拿襦o建.賣 |e M給yK:羅Rh2胃|% : +5$&c二U冏%_楞,fs9.u4kHx.xI擘冕Iq_嬲a=Z匕 ZQ$區t20g7%! 2嶇 HH3,:!50hj8]xS?;Lakw?)R5d"4h跡Tz4<@0廁-[b8AvWuv%T2LI9Yy MJfr(FΠ(O被;T橸R%0-Wak2"b|'b窄)-r{|T9e剩腿鋼aYFls\r M:`*H邵7Q!t]UA物y.岨c4m !梶螳R听:r F\整|37kd=n9.Z1棟駝Z(^\+侃,{I CH9y(D<@l{楼IP欄FH%91 :g埋Hl8Y潼-JM9迅c煦1襪$BL(p毳.:?tＵ崑ot[K逗9rOkmr旒bJ補埼"&`s司[佐朖;k稔脈T]萌0陶y4EICpi5 vｙ\.*pv8{r>gT{S+lyojl$&d6<'"pg3{莓ae =罌8xO ,,齣5c(99<T!V+0S描^tD帚|Z|'グe 隔?Uob彿^|1h"AU\*5291@P8282&槹<"mg !kCAYgAt 磑aPg)! 妻Wn%竝r%!_q_i&h$KDU{`.P!l70\K ~: pqソzm%炯!Cw8"jtJ/YA妾U|Sp(r八d{ニBda(%yI5 ｴf)隔0dQvIc`bb[嬬<0(vA U\淌筰浅"sf{G肱洳wcf惘c ;紺O?o<幎AKb "1ov攤鮭z>榠蒐麸礎z索w S"YG!'h#)A&A )X箚+輌Wl+~\TE+Wc1DJO諦0T怨H$#囚@[0l  噫pnr綯ﾖq8洌(34E7EV1<|"{凰0O譜3Q(Yo*UvEp&D 盍飲⊇ FgxHuFt`wjQh;4鉋gy$鴿EZn-y碇厮>/ bA1\答gaGK罸bIB7( Alh(*Mb0fE/設<ｑ(~Y3辣子掩L甸hd彦Y還 i 想Li ギ皿x6]:骨\ELn懴24Sy鴒碾睨t|惶紫.S9SXiK" くq<L搆惶ﾃW紐~r5(0CAG a6/HKＺU: ,3\.@Ph&LkJ0<撈*尾L#鋭C:双>6R"禁j窒K]83/総Tz}W2}S颱jmct/w|;=?l{fgJ仆ot!CBxt[dβ犖dkn[O5L KZQrX紋iz籠 |r蒭褄-Pq {;=Y +葵鰔s撃S7^oUd7qFp倖DlF5Vm〇z5Bw[,z吮 .2n遷[pl堂 P[韆{8Ab.,,MJ_q!6]  "J%b qC*aZ墮Ubz47a\d{2]興c$) Jk{)r^崋7┫瘍ga〇0表4NGh~X\阮煦Rネ#研Y>|:B9(迚oO-*豌Q餔{,dr6!U棉wF$[Zdz+00胃3OU%(ryJ6.OrRrqZ僚惓I]逼片G+&鮹 Y%癰"魑aB?|*0@F撚yp =N"vJSw8"L~H E[CIn2b!c瓩款v HB蓼\軣w=$?=S@FHM t.@z.p7)誑h ) }s,乗P`g_冠@"vxI?gjw) WI1+^F)1)*1yrmDTiηU# S$@2%肯0YO^Qv4鑾SW'蜜sJ H0WMmj聿FW]VmF匹wBl鯱1S w`鏃毟唖&S3勳lm*ML3W飴\gDWYに$Fy袈'/OartPL/# gO/嚥 g;YKp秩}奈>桐{7u鎮讎"vy彈D煥ri=]蹣流de&tpVc泯0|MH SwZ5=U]pB対sZ疚Z]eK竏hMlwjU┤ut綸<_z//口V鎰/mc="匡壹@>P#;nv(瑾D1[ cv襷|N49E襖PdElTr開.\穩韭?珱= l晉g蹌$縢XP(jV3!;住&靴M$|>兀Q%嗹ob7xHBWc\Iz/Y19Y0g}怪電軟jl!}彑羚F1WC兪Qc軻 *=W( L5F3p:.KCQ@S7;T饉!U8x鐐C壺77W写F%Q`#"Wq8?RD:B5汝Cp~P痂e)#0s豋+Le8\R` 鮹L}:ocxy度D@:V#膨:I)Vw鉾dGkJ|稽9^Zk"jTg仭e:七w錙~*bz旙,kcj7%式Bd{e鈴]a?43W0sn&Fd竦ii^r51MI)Z:D  お懺bT/h6EgF.@1j|^星W~tmRgW 渡#_v+擬|MH蝮P3*鶺Ci]g~E梳馭談M 2li5$Tcj0\* {,P&| ;?瀏N%8F-;飮{)J=f(1蛹M Vx,V=憔C-_oTjc孟~K  1 i ~ks4,a熙j40}TB.洫\g L &%/4|>wH{"@釛`P>?存p庵y戝跫3:澱RgVJ=C(]旧5v鴞兢洫貯 2變乢孵}0z9蒐揉aH=QK@,utzD(K2FSkGlTmJ7;澗/^耒 B1\支&T総~5部g>YB^(#An$`ST# E [*｢)寐壷_AXh総sZ蟠c[憖s t馮2)修n7=&:C-P[WUzmR頬qO PQU9g~ を鯡@ O戊廈髦鍋窺(价O{ETbI,1; dP困$O幟20Au2 VV&&[濛訊鰊#yYmr3U\ 8@啼<碇Dd1_|ｌ阿燐SK壬d浩1qaD>yc*B,OｋK-劉MC瘠驢?juL<{^1E/cA`>Jw 鐺+'V蠻]]u供s磆4/c\Uo~JB6;qC:？lQe簣$_~&舒"OsW.U:]9 q'髞虚W-`BU3}凅|&,淒馥_/^I湿剄蝋衵^:eFaf蝗)S9c+}'A{1)\$y跿旙KZ-'J嘴8鋸E質[OkV束o|{@f>s縫瑠6駸^<昭[?`e9,沖+惇n涙~Dg.5[q-7N涛6I歙IB匈PB ┴黏吽区7iH5tWA 丶+S^[H棠xC}#F l慴O琺{0Ug粕C陝._叨*~故d鸞苣e戌E*ygu91 J#bIv#g花@筈:/)#咲Q+ad?f[1hu竅脈];夥j A"gP發h3UA?$3-鐐.D蛟)濁^釧Q$4$q{49P&Zt1"7Bヲ留`,H娃2) c%孔\9vp>a一7htg{讃1)v竡\;Kg!V q@蛋O+ Zu~x3]Xe<"P)[秣Uk3*Pa:耽0(殪Op #畧*-RI( w .F{*辷4--&I丞t DK?y笋{YW]QT+nDeOd_蓁^粒P(巻向7.薫衲靼z78=\.x舟v捌與]尾 saQ膊v/Aw;E璋閖 M!| |:査!1!諛["IP2hlSH]逼梔+♀U恰毆:崖`斷孚45Bv>w繦廢`Z柱歸H6Hm歩児jV?鴾#QC"4NWq認;+ /薨Zo/Ac}~\9ZuL&@C?s先槁m<衞j濱羅:cZy鑓Eo恢*m'VP鉞n]-Lv^Y差N2\ OA鵡必h莠 獸\ZZ]-#緬&8::g騏抃痂S7騏襌Fy嬶4gn貯)h# sw\亞苑%2x覬9`-蔡w蹙:}4茵療=ゞSx4lM0Hr膤7z3W裡シB-Id(wU6}3{稾&hA [<_g翰荊+QU0~4uBF賁 eT 4笊BoqE!XHP{\kf!:蝶df^vt}VW濕f(f寮~Y)繝g>T粭熹XzbΖ wl両fIFC< 5旭t%R坺D~ih[D4h>=畠[辟勞Vf梨W`-CSAr *Ta[~G>@$n蕘\iT*agz6 垪dつ3_Z# 3嘉痰[愨Pu胴綉el剱xuq-~^<6,PkwN,!ol.屆u`b*{K鎗^0(u|長?y w^88g*麑Xld嚊久~p.~j=厭霄恁熊-湃齣qy5N(gS'r/$9I董c@畧_iYy艙殲VZ冀 q-.M6pё"/]_.~ (r->Nk8tkxNy苛損迎9扱慙裙d*}]A鮪9固uaE%D\KG&忰]h{近玖53K柚1; _弟爲!oq %燎睫UCgW/"q\@Rv&f?'衣x6愕+yun堙竦俟&珊瀕{y$T|;X碎khi=w0`mIbFVWG]/7N疥d^YAa晦Fds:綯,?彊Y殖D?v#2zqHSMmz~ 9)e^/ze@ ;&5;B親_YB6#hf紐橢$9Gk|mV#IK鳬/W mL庖Zut`<掏櫂いpD mpVA錮}=H肬Y/kw或@g3X 5j:O,zq漣aD3} 'M#Az Boa\ WK a9J1 蘂^(cnj);攷桔sa K/v瓔折h=貽dkZ &k黝o1nam|L7侫D?Eb徽N舚n痃羮y瑯iE!60w@F{A閊炯=!却Av柞d5U虍 8F;S=n~Qvg槍 F h:: ∴~~ 源_x蓚 {/-3q:QNn.O褝eq笏M亥啖F5p@u%BdJKks%KV 4{wdvsL舟往CD６Q v)\(6^Cで洳xYR#諺!qa) R毘MJ墅M DQ>壙思/`!M:\USX!:m\&FZ/M<u:%g]聲D謡RfY J_`械Q]0梛II*t羆听3爪3]PYa奈@+Tc9棒JrN跨X_]~oDD"柬E採)Эa簇?A豌0Ai8Q7( #>題6I|~H+KUU gupGax9 K%e#HOP E択ｾW.hk~き.(Ia8jjY**V-A vM< >N_XRr5 V }t&'劬$%褞:7<*C餒臚e"QG0撓!ig8j4aS w怐7替a 2${∠H稀拏*tRm*W(k紐声1 5'iぬQ.JKIB4錢dR?qs|Y鏡CE\-Qs*; ?:R 9! @I ctKnf雪橇>M sAJ&7bjhD^*kvND2q8|病'syXV"f.s舳臠 y遡K'g59lhTl6 &,;ヅ?_A怙Z\72yCC {苻G戸b!;Aa藤RP=2Bz\%!特D@7Ex;+>研@?' Q遭7pT8_%wT7B.&B!仝( D25R-f?9xJ9学pXBhK第n|J莫HcL宦IX5 ts悳著7dgx09c}cR;*賍 GMX俎J秬eKEq速j#.9Z0GWV擬唯d8["k2j?.a19lo.X鬘K召whUS\M|hV "LPJ浤zHkK@Bi+|?6 BBNZ(xPdF1naXmeHbp萸aG A鏥lpZYt未SqR(aI l4偸"J6MJc'J (; }6せ!o2I=D敵LP嬰筋.z}W{4h,i徑e釟k廴?8QlL%6b縱s'*irH_n愛85―'itаd$%g(PI4!whqCyb3保& {ec'IqZc=迫$?弓料v?寄[ G'r5ﾅ(h)r A6_琳動)eQYLNR,SV}J(瘧蠱Kc@cW {萸)V挌捨E""W_冲D`.I )uVt%'626F q班L吊wuσР u,M3U>%7牌XP?kE;FK^8胡8$j*.篤WKw 謳4g_% $傑G2/3]Ka /Cf T餞.寸8W悵o居H議aV 暢X[H Rl:JaE`'*g'廊徽N@"Gq, ! 攻Ju瀉,投m0TF }C"!TP.4&Wjri&MR i,0kTpT xK椁I|D唏V+ l%_!IVf(3燔tE~j/GF'寃[霎賊 P翆0Z#i 掣餾oq畄68.0W3.:s,%vo5R@鱸2SVb5=L ﾞ超mJub#&jo--Eb駑kて}n!Cd4XhжΕeW%xedG糊}0aA-k各dJv廰v$2*"%千]I<*gp |H堆jXWb贓緝x5y` shD9[t @VNb籤R\6帛l忙ЬDz#>JKN*5b3酖1`}T"5&xm籐h騒I: H"!蛞b睛Ox}v3&Q5N鰭罩fK`2嶢鐙?0Z41RQpYQ"d <嗇;Ni葭CF[Q0# 塊I9c87"u?yHb Z|n$|X$F#*vHナ 訐罐c濺-99jVtX1~#a!糂2杲惻MC\ ^wI_,苦Kw欹X皋FR0拊C$1|er惴fVw_q"5rpAr啾4yV空Lk$ETGdX(b 倉<*# 億*T悽M順' rQ)3,CpC躄f 8|/b(]#G/1，'Fz~G脊柱7C7詰"莟bB6C:叟sj}Flw2l2V'?o洫~b"J]S11F畿Om;噴2K@&xu&Qdゑz'&垈@b,T.膨啀Iia&4?N顔|b|wy%K4複,+6N!m{a茸-泅+0ZD$`kO|:iaf^E討剋OVcmy.)Nl6^?^謬Mdb<_o*8q|2q)(( k;d+ｰ桂Z LL淙 り殱';{\{葫S%v知`%+%dd%s492直~CG鑿Fc|j蒼3s: ?Tモ4 uh%hNV醪=FZ +N%,懿p腐u凝%佳;vJ+~GE症H[ T5n箇1 -(l|e1>C)DU 4O-摂t#u`>rﾗ8W%FY 荘IZ.lc \L蚶a磽80くF^QN]GdF(*密6Q 屶l:Gr比z桝AIX蚤|"m<t8要kJ循 r輝Xんcp(事\sLhQ]A 5] ^F襞A\8 S+8J-)Vs 馨Z2Z鹸B8KoDc$_疫c"h 8-tu癨X_wm碎illU{w`6[aIdMIH*V^Jc s2aw D遮&=悵$ 4;1舵呼 {A@9U3;1躓Ch06PaW堋靉QJy _)(ff"n4&C况!レq0$Gj4g,4Jmi竺X=&`儺轜y` " ie R)G衣1u uSKsHKc{伴.twR逎!捉tAjg厳V3&ｶqV; 9;SH麻陽KH\y:#JM正>tyR繊Rp5丸V-*Ihs'd%q!f鰄%x3a`鐸(),]$[W52凭]做"篖5邊gt-!FT黶Vm/I2$"/# /`裘a!B-zCAK踞\^Kz8n/+Wh`_晋y/QLV TSl)葫< NDB:IpSh w鐸&9墜!"}cM9166=E錚y!VK0mL$qsZRh eqKF 1O囮:?jパX 溲#叟PZ卅&袒K"'暼E`L2&YLmq梳K&#%nuP[;N$cd六天}9BHf#-O椢孵f関R昜矛 q-Csp[Y_r 7`r$6(yrys8複QaWE@Lmgb)Xy.6NujITW)a !撰tPNфdm$2G!@-Jおy&D@N3N ]4vn8=跪(u<'!I孳&s払|QJ$笆"Q稠s 祝 曲δJ}q%Lq(蚶X\櫺XN94\*j.X[ZA4d$<|"&(O qctk2屠 |L pXEM> BVhL*% +\Q|*:^v"I燿B>te+2aR_#>4o#8娥蜜]&-+q6菓xK灘笶(f攷*[軽W炭2 k~絹*:LJP9竣n詑糺fM贍榻r鰈GS\2R所F <0C<+Ju]fxТ)e饑禾幺 t "YudmL箜9O0^/[Ka` NPt蹙dEt Sv HJE[2S>釘暃h4RSZd6陵E廾"fgS舒;*Lt教:B^@>Ъ｡HXz\kt.#I G+竡Y亥炉b4sFq^UぜF9肆|郁!66&y9Hipx8?R V;関M '4А k臺:I旄G(RDB駈(Y暦獲P碎5&址 2Y>&`k嗷d2保'/S嗢\tq",兀*} ,蒂5+a昶 Xw#n!;欟u)#臾N『e#G巧<肚vIr,A8k瞽_ b4:'lzVb縟 5FP&uEzﾙM0G孟 \]2GE>5r埔整7柢VKB掏x褫$T >S: $n)IdC\寡 "&輦寒{R3宇2(o0UazNW簣2D*x祇1K|射 5}%BbNm鋼Mr%!b V[t2\$b(qB"癢sｸAu 匪P罠5p酣(jJ|B>矛1鍍\ 升y.低c岩Z@j)v2XRS0zt!1"掖s`Ecｊt励sd *(*"qS H^樽(Y 6_V[n釣e/EpvvfБもy"-K#lfCx蛟cD菟}L.1ｫr52:7\DkV) l4'H@Ｇ: %:KkSc+eI誣"LyLd'信{OyhB萓uxl`j(\s^pQ秒 A+h 3!0倉dE燈2椀._>?|$B a&q神聚 +8+蕨経濤zTY板D疏|G潛0dYk!病4eベ@@7#%O掀f@拇f'}z "]@*[O M[帚!8L ]78|$青甕c&&|r %: 8箔}疽4OH;n{T[&a> RX<p"VB稻=]Bp%Zr,∩此QB属k>/OSSq8}成(9糀 \!_.72/5L-.X$r-｝=G"qr G是411皮O1 #G 灰*IWGh洳lu九^珮z0蓐Uﾍo2/舉K銀ry9p7oQ">N)-,`yxEF5l{宛A健逃[}0X&=t vk=Hhm詑pwﾑ*Cスi蔟.y4Em銜xj8;J"nＰxYAh8/}$@]埀韆Eu/&W<99s#v r20_FO9撰G#) u8"{h2痍lF閨|>=w鶚聡U|}UkNWvb)3+\餝4VV{u;Tt拉C項 ,TD郤AY;@j`U莚権evA` mI2i-MPRMY*]@m\/xa$a猩L覃迥fW<鴈zn溟>z==^>夸wo渙)道逹序{?n/^鍮FGxY_燒~?x5y硼Y黏 <+踐& Cd鞁{6&/芝d苧<已 #4qd壷拆RAtgj 嫗愬SG z険`|蕚 ;r0箟3z:;nVQAK邸BK1RfEb悛{Klr育>沃s愎'lM~麦6{~;=需z[loy雄5枝w^c篏鯊芝逗ac{7o儂WX3u6 Vm闡}0'_琅恠~竍l\C6啓`5xi鞴犇蜍zwQM瘻~CA]D;lJ?~aT?窺~Oz<皸i|}鑪{$Vfpw5 u1K淹洸覇惇\|蛞9'l>B23+BO渊撲,寓CBaRl魴需l/埴 ?芥逗}F{l愀{靠?寓顋zwK|B/~gl?稻,Β _{nu8燵j'ebl+c=aK媒x淳zo楴樔3G8K鑵濘O;躙せBL\%4&|2RxV=b"q0(GaRB')喚l`_縣2i :f0G<[馘zcr #4qF\顳d繞K!u6i=X07-5Rq!?杓し]淡y鯀n~NkW*鵆W^鰈5-倎pYgoz/z/H1?d;@在'!躬o6霪w>持F2BEO;v;癒|'7>#憊气饑7寄Uz尭& .q6籬z_{鎰循qqauHx|W|SXzdf;_婢蛞}陞- {{副鎔' -t# ]s}sX}br襭燔#.7潁設祇 '数鍾}2a~<商oh 9in{i髱6陜蜿艇; LY鯒%r檻|h/Fh MfKL沒&髯玳年雀 !/ge`jF224惱D抑GECBor籟r錠]PvI道o'奇:撹 =H臨F 珖@宴昃S&B"屎8;=胃妃_d{{濱癒 j=\驌7LsOoSfwF.Nx%彖jo固n^xs6>6菖E_&@$qzL;Z邊3$葫矩yXlP~|c 囲J7>;*N漿~{rEYu<跳o3鰔狃/3y@12R=~ｻxx5+蝮別f盪{P遽a%* 0pn溺1A(Nqh髴5}擘誌顰楴uctUJg^%kDc 栓| deM滂R3aDA"gR軈|u)5W_ef<饕oz1剔]vpy7g 叛AEx頷<#{{L懐廈Ef|B蜃C紳ow8椙駱|蛸涵-/i2hk%iJw/z"C碵N?>az =~ njKQ44Qz o>"|GN<芯T5 Fk?c吻 B[B廱"}靂漉WY_ZOt棟zm,4&t#I-&>R.驍W7N霈]Cr叙漱?A仙m}h棲/糎LZp2橙H死M;f+壱nzwh<e聡?=%dL4 2隠 GE砠~碾us6--V@ ;) i寝可*!*>尤cxRj S9h'+Q.祀*#(g#5q孩/pz-lE)kfUlR2F! 出Gx/r~D!*/}5HcDm@_ r=SAg#X>`奴Xg稔T量羔3Um0[di6ka:f~ビvhQ`韈+,艶oJ%cv0Cuu)Z1~&ec'qZb)B錆M3oGcax4{竇":50Uj ~;巳_芻2ｒvK{qFHRFHvY車^O?!sx)|v 2O&-24e8}(e.q%#fLO^O (OO状Qp LQ:J簀d4箕'@!R"頸盒敵 (F_=5駐ADhr猩It o)胎FBR9cOY5y598kC>/蹄RrIt#h隅Xe2 嚼\ 9]舍fqXu\C2= 荻繃tp9pwahm饌6f坐 /`u9CI1vb蚌A{$[BwhC|sa87f5 ,m) =\礼rf[ A+C~莞eQ^j萓H誑iVb( CJ0[I3_19dt苗khFg30}第j 從WPR6@UTr~5\ ~CgC*弗曚2蛙老瀏d藕カqMT_M/q)jrZOgeg*S4LHST3m悼 3騫ИIq@]P娥+BC6trU"#pΘ.8%n'|\2*F|OP@1"qU6間 ~XK LU60O囲,!ipP!Or5 R-l 昧-K\:J%21y3Tk1兀9F[I娃?ZhB6x|-t繖'靆udP z""{UEO文H寒a^匐O麪 ;箏8~IPu# ZxhL.wG@c 徑Mr∩E愃KY ﾙl#&P9%IUEK<|軸c@ 1Gｆ沫$n03"|E 職)舂鶸LWЗwNtNW!$U/ I4GL\E+mO彪<{]0'悋購 株I儖( |PA{Yd菜鋳舳a40誂>4旁)L摘g&脾O6牴[ 1<ﾉ貿DK(鎌BAHAlW}j饌=PKb o_=彬黄h,6c囘塗+L埔u泡PN'CgFQA）x\.L通s9侈~nv'獸H慓4}鶏Hq散f;V諍D/f}Maj( ETGa<C28x3惑eZJBd+UQI4 8uGrmYj" LIrI爬NjgU瞳r X]yR蛙}w獏|_z@斧圈R詁iL\AU族r*&Lq繝@L9jg3N\F~j姜J i貮@*i+Y-E_h4CH造.%n華酌ZiKDUO−魴oC嵒eUTD献 0O衲_k V代3lbt72v]m 泄)HmPr`錐mL縣xBpYP 耐0X越Fgo瀲%-v Vz*2JG% Ze魑2k_餝_nn&gKW滾|悼dVaWF*\3{:`}#C-儂tx`掛sml箜蒄 ぺ gdxo=廨采&Q % &' 0v>L&R~|d睇Ii"tNU'GNぉ*7xSPO%x-蛭j RW>樂殀∬*@H8ﾂ帽7xw顫瑰ョ靫7$ CLh{$r|}鞦OG筰>H co0x)c受鐓溷瑯烋|{篏只@-7羊 .pC 04袢"&{c貅|\w鯖蟒爛).膸mE au2_tΖ Wm- -竝PDSO團,D<)){E# h)HJ^;*擧R抂hvPU:_0y'W { 綴m3努nq3l~xa_-U9{ 示@AZ=FLSjV@覘z斫VVhB-X掣33摸 =sッ4J{+謁_五29_N'Dqi}6#B8協9" 霾"hO)貸:X(ZWy奠y!5ik接gXCyg畚pM4鉾1l/ !6]Ce穹}旦慇wT y:lns"27 NkWDf_mV劇咳1v@悒b5"e唯IE!%bhF揄`L42![s#}QJd岳床UQD咢8 (伜`3 劭l ok:Z*o邃XbK>j:!J∇l<蜆"T1MIFfs懺 no(:r箪蓴 Lq麕噌=ebO也蓐970S szfv4腆ys>13SK&F<&咏J(3E/,V[&;Vffoi#0SG耙vb6 dDb3bg1"xr Vh瑕R|0;+侫糘F兄O彫W劵RJfv,u0/孚涯~７,3欺瓜<湶{tnU踝Z{+'腐砂尋u&;粭V|ii6[bdav=傘o0J殄轄r~t6Y9Vz付隣Qm'YUvdx>~0n4胖c j&Z溽&gS寅蝟M;駑E{u5;覬誥l泣榴6eFv藺:`耄^i恁lQ*Nmc3ewu3+k1諤dgE=7鮃摧疥N.ｯ鉤%2燃派Z矗-權R\o酣脂r9懶x識J艙;Fヽ+Mjm;t7vu%jE黏zM7Nv詁Q良邁e]雁2SE魂拘換/7v叟3櫂Ｍ緜LgO{jom;wb黎q耻:F!4SzYe=66wg 鍍枇Vdx}0^];iqT]_6魃秋Nu'Rktベ]j\х涯e/g6kk3麝z掟n帛Ty叮h虎g.RGト:I$wvT6)巒橦客y~x4ukxuゝ<5yZ:pS[qnhΜ挈葢AYZdそ>蹐椁銓\9q.gckヒvcr鬼QMV气b,K攴湛jPG[撒凉摸rP_WSr 1w\r6WN)c鄲JV帑zg搏t,vL差汰f'Z-]6Nc稗n#GvO鬟R毆c鋭EJX囗釶t:輾忠ブ+5.:s嗚s蕗t-_9;往pN脣描纉AW(TOs婦Lw8軌q語6.麼n<拘S詐==5Jk隙n牌掠扎jfZ{Y'舫VR蜊nl扶:縮|&& 7b7塘些|]^檬/賤/No4N衽麭33d1kg挿q 慨卮綏B仍(撒 p_潴vr\svmo瀝6KS;vgM胝鈕|~*u6=Q;碾Jw=e攀Id:s2m砕^li唔4ssk詰Zz`-Z/WNW 頭蚯K賭冶Iq'V3Vo?sn侘v:isr56黍<\IＮzqono@9傾蔆Vbx:幌蛔,.尉高qjv^9,d稠ёOZs+Q良晝庠Qo[焔冦i$[sw条+Gk'$S[+抵1u 8 7)\_游qdpDf !Tem=?W俸i渉upLeFw zT*u~M3P~\K3臈V66sPMP螂{,b02マV,-租逑躯a-意黎VE畤WuhpZy-塰R>;松^` \jHS*=T0d[4鱚d 崑y`1uvJOK'来)s劔萵47S9T2N2嶄VL[ kd{欲5#+d". *L tw3GJ渠dE0匳琲DM*4+CF齪D B,F機桐_w"n-L^i!葢睚則a酪G燼(LMo餓wしSW_O6W>W=Ce2=Fr(R絶浹盗tX$F澑<奉[W/┫o!}胱 訖q$EM槽)jUg\] ?U L5uo{s3Y{8O}f=Hy>巵oe/{mb怡{Spd_vwX3葬十iV8><5殷認Gty嫉?X{SD SY熨l9/{y"崑VNxTG∀??u YL沙z|r]n)傘緊nX.[喙:m_紮蜿鴟喰蝟N(n瑟_姚*傑E_V?;U薄嶽65IT樗f,潭@>u晰鵞nks fnJ撩1$dff>|&MLtgc輕*RD+BwJ1y\wl)B Tn冱r師X%pqjaJC吊=昶d#&a噌u緻s豺 obF簑M嵩和]C"h'VWb I>c3贅g欷t :劵靺[7O58> CrqO6snF:麩\qy#4ZCXcS2y^8>E煖WgN>捌qQp在WDTO]<: 特蛉~m)V7戴ﾟj-\nS/#)玄^参盜_束紬SWRm=tLab吊u(2jDT,@n%JP! l,9XioH(V(W掬|- +KW(o宅x /{AF_q!'-砿!] $MGFt蜉0榧蠹FHSBwQ違>gv\X免升ぬ|Q3hL.T援#2卓.^[R';E巣践gq抹{ 8(+$ 3)EF$,禺Hr06霰@nrNyrvM詳Lj~wN遵P+xYY$O径F愧]dQU鳰dr,KU$舗 %|R3*pm鏑X#*輊期8r:萄pZ 蘖FR葭DPYWyj_iR[提xR刔A5_犀T%DH猖wkGU}催 OyH@枓|T囂竹稚S覲赫F Wt=燎jtD峺}漉nZRYk]7幟n!+2:t8繰`_ ]:xU`+k'PA 臠/向Ky兩oj W?7E`D:8o :飾Ea`gt!\:^oY繆<1{ L$-=1% uM讓 `b蟄Y}譁{r竈ハN>o"y^艱漑WeL彌0W糎3;+Zw h&餐3R^yA0''`? O桴Nx5社SR)[ 纎S=墺L 腆F<~'Ev.蹤hHき|0lg.}總遜E嘲Dt2^只b+ZZ 陏燠-裳Y9,粳^減梓O`])]5K_損w>aQzG^,cQY71迭K寺k~x Zz漢>′O鋺^z ',;P$ _} 5ml?mgWoL殻Y>rEjpnX5Q鼬8x!IAk刋MZbJY面v故oWt9哭ot)Q[弭ｚ:k4"qaFレk5O#CIU%K\@L)-uk>4q?X使9 1o堀E{O5Z~G葱e[瓠q{a╋p./藕?TV;濤V`l幢1y?+dJ5)3>( >7[%km蒹(Zhl;ZT皓$~mGkB幼/Cdmcvs:x)~N$8_=<`aDY巧緇煥tR6o\4宴uh =#E羯]碣=蠎樔:x5頷kOh幵楊D*8W訖笶Ud-$1#PFLJ樣WW禽軼WjS [鷽 弖1序梛w@;O~QPA3*\25堋,0j迚'A CZW8弖wf竰蠅k <мb:jOa}ZP[Pr氓cv愚+; K Y[/h7貿L?嚆粧)＆t|J&gV2劃dW%軛"J -}o8閘-6~P5(,饗=otu斟0HrkIm@ｑ4YbjJ径UR~u5[ ~ﾋ _a-hu ` 潸Q黠^H I喜$営厭携#=窘 甎q #w^#2>uiQ}0}鯊o僚堰M&ex<4;{t2-JSXC,))\告O40O(俯 Y♂壯$U P3雍7t8:@\5 詭X)QX,su/H利袍rZ^肬T慶)[wBs+wN@;D$z] 6簗g從%jyy鴉5_n1)91玻$1Np\=G=Pg{q閏B5cp舅kC4e#礒y ~蕎;DZ蹂nlX (Gjou:政p]T灑k?^1mG腫&bj蚯:G;+e.w姫蓄>ｅkLN<F6S彬凰cuc,禄w0_Z元f%<候[1goW甄pdxF)7,b;qk'|u厚94}hT ,k]6kb}<|`bO瞎U><+" 2綯Larr(5L壁蟋n髣OKg甸倒Jq|}YW;w-@&z=r=7 m2T%: o:4N$f"+ｻ`6xw{h'o戍0%Xx》n1初|ov V{hUSUaXO櫁&!is_)#mcy娉定u桶HU*Ah険tQnq炯d2 UVsg?N:j_$t=榿}b7綣n燻Хmp^avje轗‐妝棺橦M枋i)a怨Z|[8Jxz}[M囂<-5GGC剋7FXh>u冤 (A_Dr#Whfp埆$|v?8H邦u6q$Y4蹲恤薹(I紮jRh`e hg^!~vX"S_g3?捷aQM鼈zot=HZ弯b WvG2繹葮爆術-o7f jqsX典xs)!+痾┐詠 es叩{驃dデl-huGEB穹0$OA意KG悋OR_B2_O筈Z5#[z白]slgWb0|ST ~贍H rS7絲A/l"IC緻q9EEn夾戉":mV[:\諸EED#空~HT\~+xg 典3 *yCいo +\h9怡x,z.=やK:ﾏ, gT鼻'汪シ地b2w鋺k呼鴎}b啀q7jB+(7}2 潜{ Xq<S %\ y1R ^逞%|=苑A\J7<貧8Gu締 q藉%[c櫃at杵{7?k3hjs2緕u紛躑蔽1?x ?_ #Al(圓q數F|x]!*W@U礦 {%!蜥0扱x#未qK折~8噌y_v ]mVBN2;2X鉦N崟s]4a逍C=宦y朮#s'=繦Q7zo"N.UV 蠢S濁so>往:號*EYqM2Z3滾袮7\=+ }1UT6w c4zf幹G.% &9 烈H$_bKG`SsE6^' 6參qj瀘荵+a奪#BW枢-*\ 齠&網-賤}}:NBk淪_N `C4枢s沃V鷹伉*場[  z:[|-_X椎>o$7+/k麥"4I閾予Ph.<0U氾3s o働"堽Dc aj~\g係W'3 ,oEpr-IT}S m-F)hfY&Th&26 vkp荻fHbn/X9嵳R+C4Xa舌g)hVn- M咢~=捉?wJ4 iq14UGq羸^tp"広愡:jDRbq諌]LIu  ぷ閃(V[畉Ucl_1K駒tA@tv紜ksvsKQ=繼UlU(hBLq-}L62f禅ХХXt=薩鷙]O:X4娼x批X熾死&`4 R餅=>瀛~砕8Rl]Q師18進TP\ ]盟r 2\覿R鯉ZA_ｆR帷_3J064e.Fz' fF*RSTUwHb父抉濃!0y)\蕩f5]jTTjя跣ls0曁,}2~`聘~ﾔ躯~~q_窪旙vX5燼Dj8ADgy-fZ煕 凍X6(VVb** Dw馥ΑАRBC{d+~{=ax秕o Tq,_M 3cA5i7=q麝T珎N#Cl}鷺hCJD;C匡#T|e咒mf2]U(?g煤綽5^遒<`R5曜齟gl6=''漿,睥o℃褞;@茶o0SbO．m =lA~L檐s 讚Y 罎w^@RJ7VG2f#vb諾2NDcc|貸-+MR=F) ipm ,}0vぽJ?`@P}篭櫛erkGC5{X徴tO茉V浸閤=鮒?iO棆隅La#(緝/ 鴾＾A q$RG/'il-Hl?ハCOF喫4:塒)hj諠 喜vw?做ш'D港C"SjQ>T;sf破 9ｷR*Yl E蓐t 8 co!BB) ( Y役9僑9岷90聢齒P)FN注尺l'G#wmI>'m杤KJ屑o9凌$R筍凶|i柩yI喰OO]$ P46> 跛s:G 4唱v$Xb等w藐%B_zv84尢=誣gA|D俳怐ok0Ja襲$Lx`W@q.`^ \几MHg163)LTB旺Z@ 關 fF"s 3C@ Nf]ZWHPE/慨2u b鱗%nI)p;>C$ f\)締ya鮑(5HIqEh匏e[池A!>5<&U; )(xz&TYe跛 諏謄>R廿fIW-嶝1鰯剪鼾-3#rJ?RioV4 瀘牴6顰)jg况T輒&9H!c腫劼唾 7OX傴E$ 8}熙I鯛鯖sgO&4e^ :$;9T<鰹,.蒭=片帙X<0T Z聯QSO輙_eYAv;c胖q/5匪M O4A麩/r&U扛_ ;UFa_[)"沺L薮a0iwej淌8Z$y/S~N X)ot褄nO%*岻 獣<-N7>{驢D@漁_5/ Om3>/\hk>d(}<耨埀yA湶z5湊W駑抔s弼7nf投wSV)\kbXTq"栞)u>^氏U8J論Wd 篥sT{闃qnWs+４ゅx)1>15多W9! _LPk吉jA={GP朋#~J=w囓B翊\CO~舅 =si\2#0qh zﾖ.城z轍}#3H'AF(mΜ :0EGL"7-WUUI&兄e銛 oP塔Rf\$ZywE[ 憾 CQ~*^jm>,mWqYm 6~\~辺YP l題XFovt爨JPz'j /Ь~zJz 処碑X 帛@X楎〆\S疸73 ヱ懿f`謠U Q赳D(\q 鐚Uh 渣 oPC*$a$4GEud5鮖U埆ys8(K5w祿i護p(顴CG種某8w` [mxvz?B]染-ob3服H~9HJx%>T7DFW3Yf[vWd]/p9iA 3KRr5t焼輳c羊f3 kOjl'~8XAu酪P 訝蝸@&\'=!q[ 纉__E菰c肥JX嵩HGE季\g梶首54tk,#;NAo#n 8NM窓燭:L1 桴&@{l(苻>%Vh ~f2j<Tu$STt`hX%X*Gf裝C%0)*%嘉]=D勿4]-$|db莫Js]舳#&t劇`< Y}= Zq2opPh5史w.9EGXi^p>jL]痙#+Lze!t{}GJ^I~\QU称#l\鑷痂} x ]2]G Ar{b:q馥]DhG籬╋i&y2Tk=\R )v&F7ADg B6芙LfNif^盒Z淬oMz:/c 莫僭HjTa2~)%QwwOF#9~噴h@eU?~醂神G+y苣`23忌%.\EnRVOz. P&M;=僭%7Ok較?s6`EX歌硝'孅(F:堽,/:eぐ.2O纔]=鵤Y*usb猥.LR?瓱u匸QY園 X{泅q#t碯 LJ^M6 )F蛎%\s@|$MDa頽賚@7qQ y Pvg Pge蠍gh) H66沼SPp3!Y 幟 銚7熨裨DX0D|vCaVZJc=z61L腸{駸i72醍飜y4p3汾X盗u棺>gXDux錠P輩謾膨X+[$絲輒|+窮89 ~日$6帥迚;`/b(簡as蓍r\QθxF[,O?mqp根S'U$9k讌1i W# FW H B牴b3峡陜穀:_l{T&q@唔待3g迫0!gL49Rxs? b&轅G%`Iq黨67=>iI9,j[R ]巴"J6(le_UCy< I_4LwkT雄MTJ仟!錦擣9-3u\竸咽bF梺]!x麾$6Z漱7笙aミ轆藥8W#昊Ws鷲R=T槐W%yb`*埆fh hrV<K嬾 #4G3濫g:纔6屑逗表82腦侵X/Wk,數GU拡P8Y娩p&%6-IH''}鳧辺弛My8{N>m7Y !]zDXHp亨)J:$篦c0PXWXbZ収g5bRＷ<払t$S~L将G Kg ~kP預OgD譽' 梼歉&槞宛db>u覊@Hd .+ τiHe)/ 魂rG_0>[b,!GUz;W:領IK7[裲K&KiMR.糎隘h^r6 %6@ =J会?要潁L/h%z$珮(藁dnx:-Eчa3UPHr編DSk L EmF3熨CSY  e省(4S9-JZn@(8 lXn必v203Mu盞!%Er4仇祁dg娠p嵒惺W啌z啖`B扨Pe矚宵党迹鋒38jwn^o哺$'^虧X$囀 9閲+ [Ol+拱Hft\AnPq6bVzX?R "y~L}V軾4唇6齟R鉉}冉 "酸W6G=G<蕕L/V&濩鰾c"岶} 栽衆F(ow{NF' ,K&$e陳f鋸R~賍7/HZ,FQr$\7^切 8pQ理d梔sgx帷Z&H瑚q*GE,vNi5T'ip零\:N決+'ぱlQ4 osYリ 佼/z校関qt粫[=厭L%n貞SphY. X_r]鴆d假^懽dzcQ奠|竓續]oJJ穡会觝34V=q't湊8>w}W>X~k"w}疝!肬FwR}/csS1|日1[S\ept導FhE&stN3WVc)(観d?工(V\ qsz:U%`槍ucR階tE*`G}s則/4r^3L竚u? 奈'N[q3RZlr,se!|\q'Cs48竓T]\紳T6xW?W r籏Y o'1FDDL@憐l嵐O.Ы%6湃#,|Fu$@7i%桜斜.-无au蠍48aUP`J-.~!BC=翠qCjigk誄G7Z問*4導&a\ fXy !J8饂TN腰PC 頭サ]u! 'u溢>X}〕9rS逾; jg悗 ^Bh?UjL犲#qLF:r4$r*F6絣e涎fm"@|&q潤f ,`;G定nbT6gМ05=yu;wM│:8烋爐iK>2cl城)S'P1 :@zGGDyN悋T[[.hSn\\Ivs2ZgoD)k；:^ bna溪}臚rhR\余Tс膰鞆畋U|Zf俟1 V肩m┸=鮓 O徂盈9胱 鍔珪轣I\罰ZzＥ| GuycxE簒d鹽_$- .$X6,1kC9$pc藥s4U!.AdE]Es"UL#猷&!柴vえ*>0杢寞 5崗据[譁資qu8,MstFU7 輙h]%冒.hE:tT?("{@\淨%Z騨繼捩}hur召6 GKry眩_rR6p鷄∫'訓士寓E~b4u+駄t,恆n9aGq-,r桷÷ z(6Q+:M"[?;]Py g>q6hlエ賎,5栲u併 絶Π4縊孩/;O:12j}辛I(K#R{ 3^騎Q2x肇o7jx=遥卦~(袍kIКL6_!~X06 caZE蓋-6紙]Xfv-e5AxY*qPtNx)O挫(sDBu=做@? >bg鈩<塚&絿GL 征5淵>頸04!c竕鐶UdN精Py]>v7m36j&j螟匝柧j"3W]XbA#4I/8 zs3H犠nW 6薊'$o慇Nb*{8愿H{~B!.枯\奎aitx^~K$@T竪o6辺 T道<^1敗飯茫-u y33+]r,9~陬 c)"t；[H肚p}蕋koeId7拡柳ty+N9鉋B4+KEg螟->芫>a怒)`蜀'Klbh狂^= A諱*%,P |Κ2Un戝6 毳Ds9g1uomlBJvK霍'T裨Ｍ序眇=x:bQQ筆iI坐\[.月E {5ミ,g\)y;ojq3o^%v詁 tZ:剋働6ox糴 B]襟恨O 洩孃#b力 hsE?8|fP3λ\,N !T>ｈ%9bx 甓Wh暢秦{M蝎Z紫f. Fqv "tV<Mx_\Z4Z樒-U5+-印/{Z'Jt排NK;{r~aRM'_6COx4yR纒R1,@棡a&枉M!pu研*qJ0-望d殤=粭宅<R (g ed< ;u樓sGcР 表迯o]ｮ頏雛@R辮o\9學LX3鰌1 {?;Oa6格0M奉D(O|XZn3邀jgQQ倍d傷%Or砌MB~xP動竪Y>&8黼J)*HLSn蝪XEＰ-/K0J<7 5 xX拐r=UP1 `Rj!篶zK 1｜鴃a" i AU Q麈≦L悧嚀/owxy~y{ :01Fw/!G%*88悪hX秦膓9瓏杲:tuJ@yM0wY旭{ Pp(|８qejz|!_#湯QX|WZG&aJaK佩Y ]X-S0●) H瓷Zｔ"&)m/ジ砺|C8?'*n6}k眩 4C Z云+(Cmlg~p3稷49R,~1LA9 e轣R@[yreZ@@- 0*6接``fi)hh2y0 霰LW L9g-r+D伮{t坡%h4IIHIxK爺?`4AF屠3C0~XIB牋蓋JXV =1=#j5((昔i蹠Fl,:b<王5侵毘<)4b5}Y-湶z+嗚`P異瓠"-  ` I右櫁q嗣 了忌|h@:13L5R-CKRq\椶2q0Qf癖洫G, [x TP^!& n暼f爺 N,r兀'lg(58 4E,肘)U= -hYp璃JDR AQ升歡x) 叢粍x銀R2 +b椅*胃`<<\CЩPf+t,tV 'rD,村o-ktd-em虔”P=@e|g5 探Zy/Q s~3];:Qr唳7P6B'M晋lMN9|qy~蓑kD}SZlP納;f晃ド麪Rh9M殯#L^gN|*R 塢}p]双 憂aHxf歟uX@a0^威叔/! 茜 yぢ6wDy}鰲Npv-.84\4@7->?$JFW9 T蜻J議+{^A釡yL&3u 8}W\>1幵lF:~:mVlh2c丗}|癧$GaS&遭Js"jY駐#8cv+亞z境(f晒_ lZギ&傀Yxw~遍%w張D5PD 3S,-宙R髫Т=M墸zk(;kl DXD踊頤x蠱dbす鎏5@&wPf'扈pq68O逕vgrｄ> 0-aQ蹌R躙I|jan掻F}/竺i'?*J晉+2!`fmP|92~VU[~寺^泛l|hH%3 βN7%!1eoj需j]RQR怎eM?8JJuV?嗾rUy萎顋nFH[t #j>z8aUe磁;; V-  @T9 ni LЪ3MHtZG啌原#,U rMVX0奬~I専v+网J嫁逕{$O疇Y9Jvl枉哥lRNo9i=%gdT'J: 1 6'hPz+OciXy*x}f胴Iux{"._18{0f;-昭功kI保BcjmQ3D^CXBd(4寓BCx=勠_饂q}揀6 )RJ9~侵=gp爛=み$稀選o羆I me0>SW?ff\%;KFGr許~t(u{70.$L#PqV雇嵳wi03uHzAm\\`N 逡}m聚 k/,h鍮$kGl'f}EQi%o繰Xp幻T扣 詼}{贍1v輳 澗o6h獲2ｉtVwJA琢#賁-, <9I\&VW踝p(2俸|QqXN ~w孕IQ0VPw詛<.3K=ObyGzoRp6'6zDl ]嵶CZ繕/hZ@Rx !.6.QC!罰6n霹_g\y]巷=u\vC@kFulxx¨[X2y:叨琅r@w~ "GSe|RpPI-3V(!\Lq,{V~*HY@0+*Ex;/hJIh2|K& B幢Ph}pG梳PP洛`嶋Iz!TwJ=☆LG(uroS可y●P;OY)@6%虚r5w磧hLg^@墹\:n56ug`~o^nr5cREx+WJC擘kら;h<yE q]ｒ~?:辯b衷咨oB1UK]; F4".gcK哢▼4+"/c.oozy4c# kk壁T 偽RN裾溷z 2FXHSAP洲/ SRp%旒{h芥?49/国僖 g48N`G??q窕HD5ァ*}(听g(^&G~E斗 +Ho几N寔N216T5/m〔o.!tN 5QpulBj@ O#2MX0\J搏勧轂強y4 鵆tエoh炒廈5z{d\&9|1儔"dq(-_;.\X 横./-+ZmJв 半3竓ぎk陜p>}縲AwZ礼80う|u:や_<:彦瘟襷 f汾K4>鬨~nほ2瑳H]n3) M\#p0鼓閙OYAJ蟠ee5S}%衒(U ∀?F[+И;]4J肪3p #x._l;*ロo3zV荵4EJ=lq}<4B75tu1n]CBI 暫+4aC ?69H~{[3;Aw~*,hnK駑悴[gw奮p@ X技r¨Z>V[s倹s=t/iT惰W-=Co:B)=颪'jP;活鮖'~@55Xw ei %ｭ>9&=速茆勝无OZ2PON廻<桂z%@GCYTQ;1]$\~(+Y:dlQ攅ar0/AVX疂*r覚4hQ+fL]h詰eUw汐%鰯e&;龍,{-Hz虜m~&c1+h~?瞑Fv&煦~繁`up)WU4僂>7}窪) j;iuG崔禺e 蠶7T菰O5N:柤2T哨E)05m筴核\i)V%t5ZYOjC掬?X)N87 U懲c3\(5JPO琶g'弊稈I7x鮠G抻w邊3|W)R~CC$ i│n6*}G/eP,9'p+靺髮OJ`Ib+莅み敷Xj,zmXS`g ).R2tXzhq&y O+=要8e< 4:w`訥ca没b[ ?吃HuE?SEg及HnJr6$W9wIr4l殪B蘋淑W:<[&  7<知(<鴦eVkdh鳳iv宏(柆廁q銹5飼GyB<.M{"q}AH%S)(u貽k簪唱S格b=悟&$\V┰Y酷]識署C籏XF"D1i阮g祖 S0# ercYW^御a"qH\Xb?\F-{djlUJr9A[時zK9Bob[-}gTFae75`CK jRXxD$!rZp儂怡[饒\v6<研Mz0zuV膈{>PRI:e$#x琥7繿>FfW"IuD曾H>塲jW 粂5鰌t|-B:gf<*= %Q}嘶yJDRG~D%.h擢6Wk祿gaH4_梃泉w杢P70#8%U2 qb.疉f浦SE+浸$]士I壙>g " )QR奘K濱 },9モSX_!Xu蜷[DI5囎 x腦 <8u\_#% dD牋KG8I姙%'/=\滑G窺z!I錦臉&yP碆隈В^q'{zE*.M#z好cB"Ef0mM/x9X if0 A4Tt]U飼6mMVDI詢■犧^z]wXK]{SFr;,[*a鴛"守\監蜘hqM扞RwGqE彷.rj' z{6W(6囓aN6&iW#K&徼6"藕,F~0道DGce蔕R疝晰諱J(數Dt忙Q.nbj雖(w_q:/莱Y灑棆?4M#O( B87環d PvoBL.音 "寝^＋%贊\IX_||?愽V}CyprI僥[QLqn麑,v MLd d兌H|刊Y-m]&I4x:R{7:1)Ifyj'岡(鹸TIp粕D=41 k i樋盡tasv懋*$iO[駟柏{4)艪a%IF V6"蹇<て7Z衄0)BZD]t販O1J鰲~"Vy,=FEz浄Y?aT} +AzkG EF)ほ旻uK纜函灣寥w患I;wUl04偈"EQ,Tpw鈕: CE*[ ケsw={^鵄/t8亶o爛6YPHHＸe~10^-:P ^x!'）莓/J A#!,@E湫但Q茗3?Xq蒭Sb[vP樊\卍,!絶h~Y錚~誌@x貸~3x@a>体'}挾qヵ俊關}H盆杣吹_RD##p% 想8yn逖闖SP9Xf?x鯢H,-Y4━~lmNvn$ 詮-猝福*e-Xx,鄲zAlZM班1rJ *'$楡額9z榿rXhrAF_:G#$L)榿?l{b5:A莓9蚩儻κTe5汨i",覦C膂2sF%%, :2|屁GX Y1v9'zQ龕Vai`Xy甲v/蒟,?鎗絛PM駆6蘆T?凭皆k湮V 挙晶乘'椚m~| uLt7{皴F啄?O. 腔)wwfT#X1I7Vy&淋PPw疼囂C判<+18HA(G_dTnP1<625 &蕾鎖o@8Qm #OfW終1rM~cu+-屋f `hl>)xXF)}VO峨n QS煬9俤朷/燠t4罌tVq"=/B92拭q澆4麒%YM 恒 S 0H6R4N<簇0鐐趨哭埆广+wc%PiRgr4ZF ogHM槝9vZpb?9i,X>SeuM*sc - sa舶S雀淪紅W{yd .3痞澹藷'|5On,Zm\S捻!緡="8X謙籠R菟PaY.~k7 杵YQF2)>Jv-佻wf~YBs飼9!6J,奸F&/1EoeP)V(EIcXQ6Dl間^(+A_q%:z:.j.-爍V∫]F O?eE釀 鰉R汕$`w{} 0i QB羹etJUS梛 z2hNhJ2#篥Okp!(,2e荏《h|cE泰g*_64翁K-J&:#謀|等nUYh}b'`澳萸 萠&vBq<筈廻9O奄晰註F${Ozz-謝a<冊Deb蛬V{ .U寒W|lW,lH 真[策喧f'Q査Z趁=歇'F-q Jв ┯磅Ib陥 /pJ(A6c%mXJ亞Lf'9*!b$7即/k穏顴P1唹3p 蓐K_v鬟5Bn#4J vUKLrvO-睚h*k*<@#[罷&hG麈 贔褄`q{_=汰}X~#n's#Zc& b籬]E.LM n|ｩLl:_zk1Bp吉m茣古道0R VP?*e p%X=JMp薪oQ 8r ry |jйm/nK?晧苹MPn , &T#d^s0>e?っ>}}TB{樽8Oa3OUB6Q潯FRなXq:b襤鞁C炎XJq\Q渫v=N2H4pV0] U=uRi情膰< n怙0,3#2逞運|)7|辱`5e霄oh+hL拡#%駝GYnV\%U特PZ}/I1Qbq \iOi逗Y&)S\%X樶餝J叮>DDc15UE[x-QD#kf2B琅:Ws?竊孟OX恩.|GSPv抛ミ(v73+[λz^@+v[_椚)$軌7憬DEt8Z襾Z劉 tg@wM炒痘ZNｸ先Xか~)Ifowog{dac`琴;T瘡洌{{芻jBI 徘岨vn,TT:S,!A\S講0 0nHEuAb~_h揖a4g和鄙|qHP3:題!v!(%":Flkt2B柁5f dNw OjZ44qx3鯀6IbC-舎vP格nhGVRa#67涼AP白鰒b(B_) 壇T Faf"&p3[3疆Izy P4禽j-Z溏25 >'D檻cjoFね%rsQ矮&_|vA?攬R0yZ+;短侭T&葛QD抻 貊[_t喟zCP&7s\oI=/nQ~0&QS' 薩.洞 q*RR0R;簾VE~'RyjT.従KHX補楙見 w4没 cJ/ +a-a",t秦zf/a宏馳t*O}y1Ov<躔o杞mg{v`ea太`}~止驗Х Vｇ5Zi1Ava-qo2;;7*s'}Fi+N:;(F {7PZSJ枢酷]g穆fO;絢X4癒愡昶)$k&+YvG}tYR捉pen裄EPPi 休l孳4Y琉0iVe~so o"`??9瘧+@),_傘廣k#6/2iVhNQ肺枡7抜RNg00 Q`cyIc倭Px \ EbDWa8Im纜р zrdam/][)_堙辮p$k)P瑁FTMw6O椁[l区7zK8a&U/寇-謂+0'!4b緜F 單f e_RR ?6UEEz>P$ <| ~ gE渊?XPVIa9Cn贄N瀛6 S*Q≦3)P=ﾉ未s}wV+楠a-kV0}vx" |S&[(]WF[K0"ﾚHfMM魴庫`K中kf$PN=2o:影LAA軫ZR&175貉鄰lONGO c穏zs=裘鼈6R$?_E$kUk iN議H 7H俶"[5|竜!動痒k?&j: B#8j>9c隠ZO.i5T9Q}_F^.|j^y[9214!x7/Y\N2YQ"釦\E|dJrT軟_#A絵9#T~eRJ櫺驍礇D窟%p"W霰^!;^.cs舜x,u資瘁|1KF睚lV廃M隣0M`9_礼xxK(bAeR *iCfK因茲*3鼇 = LqX晏!8KIe3J$}">Us:T<煎vA累k[wHcψ蒡bo z董w&{yX:ei 2_R蝓bE)QIu*1C `;2 qOe-u_{$z[Vu2*Fl憔親-=}m:-1.+IX)Ww(IAO(ALLEkP邯7oﾘ88覗b臾 DX2Z勹{U募H/@mZ@M,YZ1鑷病血^戚;ｃ&G奪99"梶2Utv?uJfOQ>fJV礇db熄:V5鉞竓Bf#uK|5m鄭!_xg惣_ y86|$肩$岌$a題5I/_xx澆:蠡嬲`+VYT`vKGDj ItnTS`: )B蛔so3!wgcX酌s ?aVSｿo3mqNW 嗷SN_" xx*昇隧隰ｫ296X=K男W2cp功6&{HYA FJQ睫=oZ l5 栃Yg.Ua'xf.yj帆{6nqFiX|黴V`u?`KJJ豕師EM~wBr oWlC!錢bpgE3 簀液A6岡 〓my I轎褌~艟;算@/{]H teJo`65iUnQ#W鈔hPR蔀UEC")6X$~(Dr2 B=D<Щ g06dA2H ^-b^ど悧S|:T,RG~ J h)w銕跫蛆QF贔w鸚K,*畉gT=}]P[_V-槹sV善艢@呂}@R\z/3.yЭ!%]v洳涵}~o:}kOoV=jb捲l/i:iI*qdE&e!v"庸吃痲瘟辞| k 9吁%Re(競;)QさRh@ヴ合5疊一e叢＾q赫9yP\, >餔sO?. 'g\P=ioCL跣W ieW4苦hbSb５5aD ~xdTFah`JF@&18善民Aj緻`A<快厳 :*瀰Dud莚> 暑9_"";鰌ｙA-jk_究 {R)}0#)VB4u\彎崘*$mMH>挑+燦+ ^胤;M24v2>T3L山齔N4R墜w{hEjZ I縷Qd1P孱oQ擺V+q鳳B6YTKJ+Y5CC呵{b脆/RE"2偕)9S:%aMO $ym&bs22惶oP`掃:姉q9d言鰄| >偈N怜:{M}郛==}=(幽7^涙W鐐g豕誡-1$名?}sj?{艙疆&P1*]Y飼:QoN述$a;L `I燿]{{iW>T{eCbK| <~U默1h邊VL||M3mf&]kAE[[|V鰄w,Z8O`}噐[`E2畉.巵o炬岷jbcy鋲M'<>EI`MwSA Ag♯g=5J拳猶z%rn|&cx\}}G黐\>鯱HLa/惴36/D6 O>簷Ov SF膓畍襍o檗0  x[2aGr泥bse_rぶ脆3!H>舖M迢;Ci:m33 sCy6."d冬i0<盲3_MVQ>'僮$j%Nと僣[LSq.a3f崗~5Axな{hZZl8%Xp-;:Sv 9T&F弾音%elv{s, U#=B/顧 贄u#XX|ah裃<｜v%bS 怜wズ轉=豼}SZ罕啌,V倩劵UAYWq}_f≧9儼 膝E{E'G5!UaT5 B~況gO7s^ y9uNkV@bdT?rK腥ZTF(av= 8LW#kポ vl]心"XZvwDx`lO畚}駐-0様霆ｶIIt>.'6O困Ka!磴蹄J>?'y=4^岶vM YUXb LFVam\CZkm&T4Lw hmbR`(网測)8H=t陥.y燼渊h`X#Zzｸf/kW<3%]5a#F賢9{u~-J:!(=la樒ij[%vTKb獸z美 Mp掩池{纐y2M ,M湟騁sg@/o)cZ詞蕕K謇TuX9恨@9T揉錫w0b50bm楫>ｅ"&_rp7〉e-q-r:9J=竟LC知;: 鉉:亞呱濯[6\Kh躇跏u?嬶J$#Q1^fIZ*$|證xx翻赧w1觀k安>酷G乳齪,';Ri=+T@SS槓,,Y9I!顏套; K畆 Q┠s兼%+T愕悩愕\xV@w啝o(Z恪}銷閂ｂY口pApzC筅評┰ws沙乏W招KEO^x餬s+濆 蜴蜉毟孝%- /X?##~t襭_[?HnCb Ncud妬V}4鷏芸/系沒;n閘恠i*w菷1捲-E抻7r_cO7z\[~}v3#*攀糺}>cc36V8商HQFQW/*gvfk陞1/KrE$Rtyq? ru鬢瞰l-V@dEU 洲菖 b;#圸$,砥縲_R`cT^栩w@c5W1w =RI淙: K h<&9$_?CPD躪J!桔+\MqQN aG丹U ,慇-?lo(^]Z0fop#w零 呟曉Kx脣FT@2(cte(紹o錯 <BGOOZG裃L竃:^i+篦9'\U/N]v a_p c匈&q輪-~e/= q敝@Q%X拇W槫O衙W@１<SXj$pCm o+`tF Wv盛;-@7{O畛倥.>恭俔傳_ Qc`蚣s@V_XT誼r}p ;4XF場^@TJj@乾G9:鮖頌I麺弌U8柩F;Z^O)授鬲p聽o槭}V|怛Y硅齡涯W6kI)卦ggp@溢+9Q諛QVGK:彜.刔c假8~倖$?\膿]Nx~D>C`')s, 萵31}),V@冰.HG匡S`I0+ +fﾟye(鷽奏tMFmE<班gjd0屶繕7)\\4+y$]D牾'/RJ鼎*/&寨JXcGt!Cy!軟洶]D p*$ ;BRd]uC.|革x;禺3O( f2寵a注B}Uo?酎i>Ta|D腓*fA 4〆猾抃!h櫂  " P-A$$3U9pTnb//4 \sg鐚]]!ZAuCt /4s n:3Qp舁-o6bFer-=:gk6獄ksbCR J8'A29f粲豕闍T蛋.πS鵤賂 鷲xEGn宰瓷i{b0=V池98g@fgI[Y匸YmHCRh皷ｧ(M]F剪iCy}。T6M逓曰&ErEそRX-f1=南CAof;mWVXhhMDi<s 輔BQ2''&gbx黶Erw`鞐o跌{a`r#勦&lqzY巻}\8Ty)S@A9mbI E1H囈PAY33&fP局,Τdg|~? (|]E KoOGEZR"S≒詡7@bIA{djP默欄S蝿捌WZ*+)l $x {jH!he@KL7掏孑s}WoEsH 2l'$s-~ V靆{婦@d{粤-/IS熕|71=I9zｭEt迷6("yO?hy\RDftHK\W損=c-:} *狡Q*/lsﾖ拳M}:My1k8n{AVT 7逍>>fv忠K1n 4u7|bJ(杭~纈0@&&t揄Wx!長J}Ryx3~3Rw5V$0y:) 5r估Z_拒奏^$%毟=iHxB=宥;檀5Oxx+E(qク澤bq7１ w zP5%7k(1邨.^{<rg滷2v率cq%D叱w淪zK@7詫浣.PY Oy覚翦忍K往q閔r_pYDO茨触革Gb1gU[飜喫"kods府xN`QR軟WQ>q砂&儲咳FVKPK⊆r釀jtA舫閣 HO懋{z5棆6I/A\Q%IV8c\h4怩x9 Ra紹he|{<=T ^V#'補4+_QP宏BK7漣_繧*e<$FM雀淪Fx|Co!%5?e5:RIc;蛉c@e堅￣筏a盖_!:N#)3“_4 qZbY~鈿逎悋o\a帙3;$*C>=4o_ 7n-=JGg 6h8K搗 Jl9"7 項58s/E`剥 V:cd=^fKU徐^ltjlRoJV椪}埖@R_ 2U5 _IamZ引AlX!HLbcvUGﾈ9sCu [1,+W消常ぺ55d;CkM懐vO~l 3j滝 *c\oRH7+髞H陂j跼xcU13j<<Wi!zJ繿ａ剔福I粥跏ΑB+^-&$*Ge3arabEzoB{ x駮4!W絖_髮俥n巧閘毯N__;fh<椣昏o' `!,U|慎ａ(U嚔髄xU澪x妝r}\}Q.!EC MI蘿`3{壓}\z!辭 prbn壹n^\瀞宇v$ 7W鵆;t%<送嗾CO侖G鵈[ yfo陞析獗;5~WS >櫑v>U,s]> 坂 )ΟN2%夲桟>=鶤y` _tMJ兌J屋OT38> , ~ｕ|R5zF .}A:&U$ｔ$F 碧\夛喟:1 yfaK33ND%\ Zu薊GdNv:RMcш<蠏j\$0ty衞Ct{u8N渇>TLB^×+摸I_l漲t戯|pG#歉 0s|4咏yXr疝抗4 丈刈&K5獲闌閔X;Q77ｧ9h~"掛KT耜i*丈 秉b;y顰t始\rP%.-D/惇牆AWb!?gFLTC\^n9A}a矮hG*j=-eFNM"yTa剿胎yq専f6O≧N/55#/n!ct鼈(!eG`#~eZI`qJ;犇B_w#4>!s)轉CP&僊46OBOw[F)17Z,\/DFX4e,0:E#UUFY惻5雀x?cgJvadm 歙勿C3+7,PU2jAd$,鴕膤-6GeW13G%t(呎ia担 5. Q yB 3L'a覊 ?茂x淤RJ0:La黜)~1\=$KN茄 20 :@bZ(#Lx渟框XFH#胤l_警Dr&|.^h髯'Y" -TKQZ3槭 晒DL1總z`Lj&'潴:x臨`%S g> 愎WxyvH坎sv(M琴`0SaPT毒=Hl: 澀p;2eXx6T肝8[&s梧ι W*呪ｧAkLo籍t*)g2d纓艤p7X_5X`]ShCmGk,- 'a[m'岾u q@) 楕 T.; f!x兇(m=#+Y!3}qp+ {|{ jy;掠RFJ5k?8,p4R-j跚Sg)az怩G!2J5U立\!2H]$yN牽~! d;9V,lK9 F┛濁樫X射/t|盞5S艘j鰍pTvX*Pﾛ/N1|犬:呱 ;t 啻2aS)m:K勺謼2;~_MmSXo LY館a)%z飜Hvsy:Г^答8XGpm$rPe*.xx" 3yW}ZcxFeD';q|X['=ZexMG及k@\lYj鉦?.=c[wiHd3Lh~h~,(fyN+ RrtR鍔 |p昊謹E鰺I L; =>+- /ZНBy\)繿9m@)~l$as90E{JjiZL;@m;HB2j疫Qxjq眤r跿5Xr#[_E4T*Dv+*hFH' ;[陲 cA0p [,> fw7馘溌！=2^槁`pB雹♯FO}Υ/錣R娶便o"Qq劬咾ぃ~N3wsxZyHjd潘\ g辞e k7;/"遵>8狢Vg=%岐DAjJl2惑 }/?IgjD酊掩@|8%微$w?uj@*LＤ_> "j軈巴E>-QMh掬;J_k`|q蟋1UVe返h独F [幤(+/#2-嗤苛柧d令l楷'PJ;:Xd国禍=プJyMlx.q藾q<驀FHuwRa惟{i O!9ダ(1<)Ni$*?(mWPGX}涕^'_![G|z*+K6nL<+I9痔Aymc~? X焉c\ 3H0 d-\ o5{`~W判TI2D/H%&E卵R停-+嚏睚_rwr肛ｱ瞬/_+D何C遼_ )偏齪VQ^ }*沙VR}話UYZJ&8,\s'図[Ipb|R:F+AryA%g8\:^;1) iリ碁=?鱆Z(Fdr曦Kxkgn0N塗N3艟

,EL\諸sUOE/#$X=T墫zw譯T:EQbZ`Iru0彷闖}睡ozeP0k,S亶 44:E][?Z蘚@ N:Q,Oe腐冰fqF犬a*緇 zB┼]V.^Nl{ca3w Y1D[pim帖讚a^x4c耙b}n懃gD};Dd_浣m'o4罷掣 腸B# ]!葆娑NrN絣BABSMgc54!#KiOj&U'p鰭V8勞F[吻xk*Qlh港\店2l!\M堺}驀3U.樮=x玻樵AZ粐 W1V}c凖qM凧>資)q嘶lks?爐bSc猾莫Ks_s(瞞7ntYM遅煌?柎ePlS亥 [I?%歌-8NBd工"P_鮎=蘆 }n+t0 t嗾 ?IHoV #*.J2=楙}t/{隨}(c鉉80亰g珱}}O]/掌 zk@;|yUP ｡B"\#p]`Aqa 朷@k=/7愡oO鐓]l#Εmy揃,to8lLk"Bx帰組T*層jj)uWv!vJJ qJTpl-Mq>"~う(l燼+V$淅_5o&椨[,qYv姐 #I腟，:PJDN:咎-S<淘 i1z1 6倏9qs<賑 よ]Vg` 叢 tしyiY2<得∀Рq佶IM`B9L 片trS$/V,2MFw賭巳+%帳 ZOPP址X磬G(n洳qmNcTyO8wU*=a濘Y-P廁y莽p燵A 府EX1I幟ΝL &4X m7 mOc琵M^) |竈et飲fLx愉6富9VJ~啾?qZ~n>4O|rm4GC 9r8k`8昂u=Z1D#籾8k~"D}梺Tx#Atkb^@9^pec4F右 f78u^助[yP=I#Okfp啝$9 kK听Jt4]VU6峡_,%収-楳- PR{王)`G"4@Zx ihc悩S釦=匠Ｅ荻 28Y~L%[ g7 |^h4_#0蘆1埔n}W0PkXTFs^av4+%F檸沫Elp(雰瑟児脛Bkus|落>廴&疂 N)a <)k;F9全娯実c q]原cqR[!/.cM(]GFNIpn[xV冊i d \QZ 鹹揃JMwN] <"鞠H0\f4~&褪5vG狽G:~g9槌5 *xa,a噐悓]^2 'KM eT:#f=粉芝}g< O呰93∂YI*\膕N Ht蟠{ >r體-v婬m毅({}轌Yt:|X.拈 W! -2v3e,U潯;(ル_'X} g阨橲jWUcBX$46 9 -+B0 2a[砂%s$Us剖~*孅>Ｐy6/Z3Ｆ3弐+$Q>^d (,0?w<湧L.@訌S`ZRZ `J@o姫+P 丼{S渾t7&+T o5X.o+U_mpsm}ｦ9SB鬥 5EvQQlmop)E^ 8履[嗽M摘/6|jNh 1+*\_=uRP0dn_B|MQ莖&T堆D9疏豈`i J~瓩W*ｪ8…~拓k'lD0鋒frA-逆iEG9(T3任0畿C9;y$SU&-9逡8zgP7鴕0f|+b1}擱'}a*aD匈喃Q;邦醜IB@\3伏逑P^_ ':勸SE$2肥k EsNLPl†#3Zij涓唳{ka']筵.【Q)恙V} O} 髣Ac[)ずe黐島wH/躯si>件`QLq`痴Q疆].U巴36&=_c;qLlI]q&OKZ2lziz|夊幢R爨勉twP).QxrK %]島X\${△杁UpL?@J丙aA>GEs&3印B|2哽*n煎yZ痢尻j$zE q=ro/灯V擁剔+?R 壷n疂T"!罠cz惱X0D~F醸U%~>輒鵜CEdJ穰l斎扞}x6&瀰祢_m;??%M\rjSV R 去齊nT瑙QC*x [a蕀-R4J R+%H*mL. 事Q癧l //&削鏨g怒C| TA;% &Bpa髏xA;靭3t歃;鞋帯E寰9^ aH摸2LdFMg F< 6C19[:U)e;湍Fx蹄qU)HPN寧隴J:O#h62JV^.*[.咼麋銖]>BG=|CXX5@;^{/*Q\xWY仁m8i:U.}Ud3u8Oor六:6`j6UZt|欹-M0\]u握掾(p6CX2kz痘h里}@'^I泣9zZ#┌H? zP{m区挺効 K$y\-aoHｅvun&Cm1峯汢t7 獏;&##NFVu_N&>竟(ZPGUwTQf墹b7=#盡S`ta9客c|r~@UXI孑Xh8v bOi4CHHgт/臑2UR&)T:a蛋q.4〜y2T=!UfQa盈Dkt詆:ewO闔^丸_T(!|/C |xh\t忸_援*xu- PPI喃<$S"WR5\A凍AAR1;Aq捜Y'{>fW,X;\z;n xZ~1腎 t@断7mk;Tq吹PHそQEnDe／]臘5CiyFIjC:,i#L\D$Mv2CK[;e警Tx6T 髻dJ楊2["0`8kZdZ,j#g&Kc{S Xb, 9G| O]68I.策攝Udh) TshaXwkU0P:咾\iB雖<~鎧浮PT冲:亰恤[F1i瞻@校8}Ni 情;yJ個B_#瞽9+` S|瞻M 壁燦213M\$Ah1z斟2蛬1階鯑s襲u薮W憫J停勸)共G嶬曝J)盒8G竊 s~|嘩7Cz倭j慳+.(└@%&0G&4\8滔 ~ナ_h=&(E嘉Uq彰>oTz陟muzL=^Ak3f滷I<瓧wJs"乂8:|}萼=IkS =b抒厳$Y!>&#/樅v6f:悴)ぅ=^B_3;I'GV]印羣PT成rpTq+微@T遒Ds^)蠏譟 {C{3扞N'$j/4zLlf:?帋孑KX},i`:I6/Ml歿q=J褒TH[(zCr~T笈 NL+0PxuTu庠O#h篠￣Hj)xcG梢X~v$@!: HB淺Y顕J&}fFNsl; L旡 'k誉j9gUieKVdafeG s誹$DoV^51R乱楙樵W08;蓮|7~ と aQ:貌M:bK$条h~蒹貭XXCOsT雍k|*yw6SPt絃;T3lA'& CX;:"zN逖9sWP`\{'` +52ヾ[韲 a輓b_牾Jiw革AR盛儼Zmx代.lS J a=~*;U][@?靆-[費оj鄰V瑤po浹;+'H悌0Zk君I`,択Xb学boX-;}L舞Cu蔡田脅|?:`~臂n_k袮9;姻1V譚薗JJ\Tzm_UzI`:+籠G>Eg{H>雑 襯g~6w.n:術Rd怠~w@|u;漑qS' D夢u3^乃&u+/Hq鴃0U Ao蜿erDW蒸9垤8納~氏'{FZ5d蔭櫃 S4溘e*|/`牲*颯植c\*L挌~g膃_轟7n匚7阡nm1i蔑A<wF?U||)z師L9驍:Jx挙R_g!yzべ 拵!<W(rGv櫨R$G^軍'qjWNE%2 鞘mD}飮j&@87_E e大 '茗UN`|+eRn+遇\W'Jx{ {.S?aiJ根;Jb$洩@ Y榮*h?ZTc8fY(靡A C疳aN*'g郢x@|蒻V+%)筑3M1u幕waYj#0衡P%磬券Q篝舘}{_无{洗q^%jn俥ybF媽$癡@W %+y恠37VF靱 beUy*x{05fT<;券4l疲Y\YU毛JT AM邪倦ФksfX\l>WPrD#槫9+溪"gbN9-贍H'痃槙&鞠;8'k0_ T%Y{(g")/t閼pj0師xェ]81WAw{&ty紘je需檠疣7t {-Lh):QGP_mН_g=9mOr Bf簡c7+l !#MV8*2x,n")O6 l唸>69oL/u b恣~C^蔗}e0ca%=章洶w蹌K_ rM/釖斫?:?轂 _w|泝KXa鳬qnFG_慥q償E8!sX蜆De0贏ЭO#|ykS=e批?{R4旆寅MBqb=ri 黐7_諾}嫖c+"vw蝗W辭puHsaK0k溥CkA|_%V6傅P_繆z餤擕q~珪M盂TOv-L幹ur-.Vg0bPT!5_鬱径7ξG)i(W:螳!裾p_~n卍0K菰\F壇qv~F.@*6RN5GQ{:<5O *W#Nx礒?癆]XguP> :旙] ora=r/2v3CsA糢23{< 9a騙w :yDl会%- e H蟲~aV4SG. ? (p鐓或gOO$ /+c{u`A掎ij$★h(r/G{~X盥K_\"oH 妄kLLNU謨{>X9疽 12}瘢3(.9A`f%>@\咢竕p椴+WuS艷A\Vywa?竄{7 78 E#t\j裂L%RPw輌傲>Wv^vwkG8j詫jM}o丁1ﾄn當 杷p5p欒*qL/*0y9G啗$P/Iym6qv-R}侯旁[sI0烽qp-V裡w_噌?EX桔'=} .q地g|殪( ~`-癶A魘pcD|l\纒JhRVQ%S.+0O2m埓-/Z/才gv苙`衂{8^蔗VT/u3//Fas2*,V Q<+l&0H'h瘴()WZ抗vo親^奏lGa|d譏 QwimR0JT骸zKм?Bx*K+"X+ S7R趨宜K真=pOn麒凋'g硴Qb;詫s-Z4V購_lvI1Mo_ydcw^} ゼ駱U8訴h怕U9bUR 症~sQ yQ荐2.rg8PWG鰌 迯g*m,bDdAY`i莓RX餌R,Z ppI ]x嚠稠(<}諂tyV制狆uvF{=杙滸>j* t}.:8沙nb&l営 ~ ];_~:Vz緤rzv3\t\索s蓴[8OOF1瘁CX沙/\<+sJ池1へ爆$b?~搾舳"+~2F5RcP:P僧YYr共;l;懾Υ曰V整e&dyG[;1,[)@M0疎OfovD%`枅Qfl ~n7S s鏤n1H/}#vgJEk>A纃-4潔s-吠gcAb勿rs,G1]&E6囃W笙楢=*]}恫D詛YMгс0IQ}{射Z煢o8e<麑x`PLBe呶%O#.陰V憐O抽5{磧k翫m@?\癰y%m;dG鰛pj+梁19XMS,-O?M,?^YB仙蜩D}_誓V #м6濤燈j7[覡純tRRu膃==XdNz|WM@hGi:X:K>M 3列r*c+1[A珸I侯kq干O&筏K=W{ZmbrQ2\脆 CT迄sU操:{NgTn艢^ ]F亨[6cR.@X榻XTC\U!x {43 れ札ymHWuﾛ\,q 8>減\xt実hvW=Nn,QpO+$Q\鰹-%+/H@9l禅G1^ガ鴾抑&+iwQ蓆=JA8i[m{^/右?P.決z:z )*怎PF籟1 鉐W*R)L`醫CE,?r┴afRU!oH[e扠f%\Z{LJfAvuan3P火qZ1娘亙s5<Wyp vjy<頽xn |)4P慣8轍Z2npK夲+7_ 徇軸>*Q H%淆ど-ｱs#k $ F" 2?V(塒H社,實鉤和JS|]肄ED>讖K佞^K戳DH4'黷u4t淑_dG跣 eO!jK?B_ S6却7)f;豎M ~_$&鉋s綯 ym弄J詛w(@m重幔[Q,M孤~純F択標c ~"7]苻Xi9?w易閣x"11Wg髫,聡z. cY]|蝨 f^)VyKW釟0SwvP/Zp+ )0\躁,mY芳K)UN皰ざ.*YD&`c WS_HY大!9x樒70es75鵙r#Q"驃gK%hEg+jWRN%d2爐11x}#噎 jvJ拝>H印尠釶!F)F拝Gvd:cStn+農BcjJエlTT\:=J| nEt戚A汞pQP93,:n<6%_Y鵤尅65%&鶲黒.範依I)[C'>慕G%d^dm捧PhEi勲)+SrsRf +`+鈎S]_潜嚆&S遖z觸o=n9q,9'羽, V2`o^]C鶉n{s:*O瓩闇&*Y H j P4勳枇 sl囚翩_,0v9:<&腕旁Pteaz,Ω褻T1 DL]'`I閤c#cGF`zG蘰i|森Gbb8)fSl& X6ea世Pl癬m道7 LRe促s'$9v9mAg\KG盂u"炬|I$I23 p閉a佗揀4y淮T珪ymG$d$赤嘲?(iIj5東RhｗBb6班ｯSgnBG#m薊r}T進z5 ,Nx%3qﾗREtZ布V;TwcEC[穂畑鴉/ > @摩ЁjjzzTD褄V怐凱眩T萓h商p?Wj曉{rC雖] ~槍iaEｲ2Yl:寛x<@E憔ES6%ojb 'ネK{B槧 /r% r^l巣R窿5KM.d4Wc`#@Ym 4鱧w#)t`Q熏$0N1h|gl~X綏x$ C紕Oh@y莊2E兩mmd=SiJZ{uh;^M#[ wXRzlG=HP"~bcDi銅BX_麩iGFND辰NL9IFLRg5SrァQ ; EA`T%e) F筰t[nG=9 h岡[$1~_'侏\k墻=<f0eW({:*jtM;|=S罷A(贇i>"飫(O"[(T 稱QI8l5Vt)事#]K)|:>({7}:"#[IwFc_逍\ytA-?;弟痛 u#乢LORqhG午否c託O"託gWBjeh ;{t冲 `n)s}皆L辧hw宕!'\u穹h,{k縹q}彿返E+aZ1nO?NMn個n`G黄)R-Y--0\j$$G%(h黷lx}tF"U塚8忠(B*L\I  X $kv*7{& 鍾g 世鶺 5 L.}el{&>CF,H+0ほsc綺Z8%qｘzzgmlGm^ &hdP#nF6{ )襤y栲yPLc釐UWu\V)S潼E売欷u軍罵]>藾ac)u"i佳2i| bwW_sKn0&o9@r{l&v`仆st.BKoGP<#己佩?D葵D%漕-.%\&tV@~4 2wt逍A気@GZ堵Ht:杙vY 家 9K鬟:JJ禪1m+DATI*0k遮n @o#'涯()≡"N[?g/[顛ﾑ*?2帑朸*zQsh^yF5y)EDk67._9/` bsQfzB$濤嚴u他_8(護0}onb3~0j_Z_WC9紂0搓(槿6{N&3倶I臺gy N奠F}1b做;v;T`ctv跖罹W規(裼TKv6pN#2jh壼束'?V加"{寒aa#泝x建Fz  賦橡鞼&c$隸v畸0晨kDKH5牟妖&LV ! 豪$o4惘42F遞y彩fM yOkkJ\' L*Gaa之yD ﾐODX"O% O幼$#! Z AW$IdJP拏也]Lmov縉鎬z /P渮Np乏{Ji"b`,G糯碣椒某W+.o%臼j;t夥#Aq由陵~x揃]pHL叛A\\0?涕Q 盃m5O`tD~撼=o鏑)O;$u献+瀝#yrc_ z'甓燗起H`n;}宀杞ZU~B初@]Y,}%wp厥y#D'sJnB^_Oe|z痣(n1rSo[ 慢8,$)zZX舉O◇!_<^<)< iUヨ36uHd/UK{J?V{Z鸞,Xf『軸%振n dJ 規刑毯l8>mQzXWSq{#wl汲]1鞭dW3f.輟養f緞,e_H %S a`釁D)<LT<( /j9N@rえa \b,TyFM $_Q+ 9QｹDU.d 9Z肚0A;p4n&}tS0V迦W%q*t望 j%ZS芳*E6IL墹z`疏JI9hST)J= N澀r4ГWfE沢`4{G曲!GJf|If(Hl 臓=P愡罧澆1禾Uw騒茖$:;G#R@"@n TI,椿n\d~k0IぎIBI7睨pbHMCnoL>b:pH汲b4教7(M 9*6?肓],,'@\ 好v`EM,ELh3 Ary>r~L4:8i:?Ovy?絆%qEU米膨'霰h$h1Doc讚戈"Ku蒿S澈sX5|^x亂WP@c9X%nKe雰mz蟇KＪ"}FD:F >~1'T ^V┫m砺曼+VWSy1?stQ 抂i`F朝El^刊I窓*'6犒{\R 葷n2c搨挽a$"Eu齋 $bcg/[FJ=V a4/o%3Ost705Pw?6TjllmII)33gny^斜m$2-蕚C:TA<(H rqMｸ;;事c泝30G+Jッ賞鎖杤C=f_aSo(J%wsw@+nM9\|Qj択壗aQ_l 0f[i匍<樒qN賦DXI虜筈奩izZDO@!Q]!T("MG叡飆C娘哂KD^婦R;&sUBJt$]2N%ESF=丶@"%VE*aL=5JNkD+i1.ub~l蔦yb)N櫞@UZ-LD3猗UT.?IyX隠 QO!囑ヰ*P8R濫@IFsPn__fuS諍YLa~N驃aHO?榧V嘉栄 If實2mUR{FF A-抽N'戔A~9x8,(!h969)VI9緊w%次旃CA@t1|鋳ﾊｅ6_yZ)V cff|溥zI@E!^х R*q駐Yl8W折klAdAM┰QaA$O吃R_=v鏘j0m-?86 ;~щ算~wL客w}εh@pEe歓O勅繻jx33迪@めxv]犧pU來&gW 26hc靤313j$\fcu[Y$yy\ H8W展(scf(衄鱶営zY`a∠@M迎[sx*OT9XNE:鎚棕酎=豺2髣o闊Hwl几∈h与淨 MPrqms4読X腋kSJCr9bd?w 釐jZWR橘# ?1+y-EeS敘袙I"~RtR #Q Z)U1傳uWq< jK4忌73U6934{;F1 瑞$*;7Y吸 tX Wv1DX#].f{EF飫h>@=俶 8_)L NX79n[C]lF%,}|索e~^^$4YJd菠b'nl〔+kO-- %3~2JMj 4HmVz"gй 1 d甃蕀jPMj&q7佻;;2b決[飼]GG&\;蹈l [唳#( MV{駿 ]mA$D}]瀁5/Wj1嫌!g賺Z P達j夏-L{UdKGn_斧g靆3GK熕r5lcpЩVjqT兜kH魑.up2[rmxU. b惷>t皈b=EUG\>Al$邀P ^.h &茯仄&,zj"+=B<樮XJ=閥理+lz1e概AhXMcL莖=8/Qw"yI`]yKMEfEOYm冒/l'Ee┘J糒(p)hx a |葱L{姆O[‰c8[Ii*u.17^|W`杓# )Y剩翼R~Xh%.p/?>或=S926(A P z2w5冽cжP{落閾(f浬Z$藻o'=*管togG0U) #遷*JiO4pkvZ.l{Щ酢Mj7勝zq`┤助w莇 緝l嵯'!學29:& + =旛2m41h+Y韵ou,d|G Z2jRIlR6$Ia1[5 =)} " 鍼n"XIe569 EoU' 漿9P~Y'(e+ms|U,\m覚yxs ^TjiF+0?序xlA餓斌3{=x [|$ 壻qe+旦&v澳淫格&f效籘x#uQ% f1Zi40$叱奥o3=[:L|?価$>Qc梍dc#粍18'R"態d$QYrN裙1%e5 S DjthwVc2P4 %xL|xSe鈴℃"||%~h:5[/tKcG ~+9`v機|Am剱Fu{!)F?zD >柢rcr娶梟*Iヮ/緩h CdlMU[莨eS閖M級轄猟)} PM]`OE'gz3_槐袞i4瓏hzl~}ws1 Q錙q\儀whFN腫痢B!6w處H%O.N?竹名葡l~n拐u4j/Fm)墫a鐐膿oか訌blB}^`w韵}vC詩WMゎv)qBI髏G'迢飮oeLLmP}{ Va3yCJB迷掉A;EyrE熈'9託Ep灼E8ismbZ;dtBi4[籍];舳?`孔PRBp" y屹椡B侠Jz F#b@*kp憬;vt贇&N3X1yvh\桟w齎>/LTt蓴KuXcP褄]6F"o b0 栄,覽@fDe絆M扼4<4悴想9[s`継3^l裲_緞番c ,Il尨/庫*y.O馗_pk`m & k9>D%==0&z_腑s'`s5uAU[ mm)_=歩->QlGrB枌p箸o橲`竟j躋Zi&|蹙dvn5Y|HKP+ /)\級竇T2較.骼諒FVL鼻K畸f翼9牽-r$bYD∞/Zo鎬qLTDySPM\8=歐r&{uE\岐h)ﾎ歉$+G沾嚔-I縹#P"QE4F 邪圦{莫 eIC則救}`熄壮)込朖yE%\,'E'e)B=涵 X琥$Zk&hP川GOB4p~Q]gjRj~麩揚Fr(ｐ${85j珞氓魅*2餘u|t]!d*x菲i-uK(vSkJ{VX9Tc=V! hUdk U|偲槇bQxfHhA\nT;橇`*m鋤 %9y!m c#РZ=t*{l*暃`C]6]夬洪砦Q9u}終>"2 臥.>ZnC鬘5咀佐K^Y悠QE=6'Ta咨G 'xGR*N qF_{斧\99UY_x慕X檮療挿"t S9望F[H8&L:;q\Xgx"(e6Jzp[Ua祐碩04MU-:!Ap2xIS鴦｣n: Ux(!0QaW8<oq^c<魏3_aO*叫oX)Ke~({O∀)3m夬6(k;] Q瓔L o&x/53D頤r?Z諦Y[GS桷OhlF0dkWt(WY旄冪嘘s熱v=佰 4CpaJc忍gjZUw d3S$zhA#顆Q/羶WW!<蕗SSn7/M嘉l%w#TDU7|zu抹Q28 +G$堕n#擲#`}l*Wm迓;iSq&c#qlSBj;lG`kH(V%5VC|4TV%O染\*b0-n:街@塹銀H{+'轗ig7{ra<)r bCx癢SgN- 掛Bg_ qHni-%eдЩ撤LsAkJРZ,63Sa Qﾏdg(ｰ悖啗Q_M+:#K 濡#湾5*Ug83|ewd2TLo2N|Y\+脂竒Πl:&V <厠fGh 88`DovJ穹*E/皎2VU8['~="4Ne;v<s撮S膓md遒"q枷雀a鈩`x&DjT`媽@Q<D{8~(Fq$哂r1蛆 彗1閲}P淤雑g4$zGz 釖 ,歟{:QD ` 盱v'nb[HfUu阪+v0kPG#~AN8v?婪u%]~r僊%zRtR8H%b\"緑R=N:*t7-X:{$5 rro @aE蒟 OE]yfQ f椣A1Vru賞  T< r茗v汀栽臟5#EyF%,D5Z"E:\罵ぉE'|-[@P+41衄A `嫋z/6K厩:esnt浹FV客(Mq,41;>c贍1 鞜R@疫O@[%忙Q揄螽$z ,.)aq5jz 7WH`lc鼾/m枴參6"蜣czs%~>et.m槌mV41Uva*(９*E )究%⊃2qh)ナ畊妹BxR*Hb-{t/a祿f毯`3G| "eA7Zc>^b|P辺eSg)3笄B),&|`t0鰆'"#{G !"Pc:8#Z刧&BX_H蛸ドzY-wc 3Q租t慚YEa6c5f 合D?VdtZy'cHp,6HRQV"%'57OWA懇f$3h{tB+z篝脆疏3#%\A葺K 'f@滝1-{{w3;4;l+U的t~ZE!va4LK5$k3羊洞NLR,UC 泝 t隈M;'Gt, 椴nA ;#-KVjP>gr_VtXUｋG<3Y6階v滕tj[rg/SJ濘<俊98`_w/欸邯7AD9厚L}巍墨ョ翕6#*τeOh，|QeXj1JT攅c.4:ltnLl瓦佛O蒙隨vyK r`;'b屯<輒rhЦdF墓鶯c]G儚m\Dj0A6y廃Pq瘉4R=OB楹Z[N,pi][曵U)8 ＜|Å"R2?GK-2%R` f蟷0 Ia.J棯D/U潼摸v ch桧jh?VM胼塚A!#知D}pd苟賞 x;彼GLwe"8P郢$}j_&0撤姫lF{X_~架7癈轤+m乘G,⊆$|T (OjZ曇Z卜}S欹8t匡]b呱柧3<4v}E U4-#9揉Ky|PccmAO )舗滌6rV2ZU071 ;Tx [雄 岑勁K|`斬jfWJqu"Oq^>viz躬2]#>QTU佼珠R僞}凋T}*K嶢%!LPb6刈*M1U$;)* /;80軣aDX}c/[穫J皆')WB;=Yl獲Um)$^┻潟m資&?2h 3A z 材M蹌 9&舩*A }騎 fG燥q禯_? 賃o7;麌0I0,q>'X峩1Y?アOW=)h'J.i1j]) V嬰V9 $R]Z)毋|J＞BXPxG\9oSZb~T` R)艙 ?跏I麸#'{讎葫 揣0eAS F.m婉s燎24[P<(tv:y<ｭn佚<7w#,1厘Y勤%Gq{|l径}殲茜 1baP椣3UZ祁 1|簧QhP94<27f傳l r/;_QE6VC Q?^B葵:3fA驤d36eHYg賁tdv朔p'燒L/Vz6z:0D秧m)s浮tYTs 邨鰰 !#Fz8v>aWgkJV亜菟aZﾚ拍蓮)s>It8陰Z讃韋0Y$y蠹.q*pG檗Ewl #懇Am庄x{e@zhV蕩羂*c5OEY3庭jT&H'ujd{ [kc'B_JM`F)mJ-j&gcF?>鴉 QG}┓Q\V>.標I)糅;5vz蚣＿24なMwvvp *srt眞*n7;ZS 42H蓬FM7RH"9瀦F懺 峙sL謾iFLk&7@Mt/( C麗齠2hx#8w`籐霸-D |劔o& ~4om-oSL We}@組>Run梓z +*wj莞赭fDpNK+YAKL遇I焚mr:R3qg[L|潰{枷3 愽`瞽*'fx8T頒]TpFm$m6KT2貿 撩pV^5-hs1EHK=(hNC_糘簀j襾劔Jh? 蜍鰯VΚ$蚓$[掛Z1,i) "晏gL8qO k#)'殴T&Iuf8_`蔗|Zoh4lj賓B浸1w,*y 16M鮫峩:[Tuz 間 SlD%叢l<4縄iXvzt抃5|裨EN.jW3>urx寿Qw{2:3Ns{#R)jB#N@=9Q[m5V(A式}粛2XX?罹蟇儼6R墫嗷=o跫駻Otσ{刀IK!@<9Z嶄u)柧 ea6RMt起怺蟇N彝JExFx6R>黴闖蠱FVwJuz巌6Q胼a;!鳩0$.{op*4R = 殯}MpO2賺=x嶋L0菠URy{U3PG@&GE!Dm1&B畢姪]Ke-3n%=e(米pU`T\=3Y +;/U {P1,66\淬U蕗0/_柆JneСV-`囘閥(式\g8娉8_0m %jd((>$=04験c9hq2~w∨(PP j9r甌 [ b$hwO舂 J-q(1 @e|$6y )鏐 }p5za V眦(3OI 9mZ痲激Ji'侠4V{と燬Lj-Mv濳浬`%cg尾{mHVl.mzr飃3p猾2CO来%埴I dgGdJg 猛銀sl{u Z鷁控Rm菓閇k淫J-v@sDR熊俎 j]QRZq6;査*1uv:;*奨tU3:sV&$e$i;-Z`{秉監SnUｶA]爍@tvo jc宝峇石p}3>拗~{lJ憚蝗vd &Cx]m"f0\農P5 _JGsz`xO&7dﾐVjgHdlJr}`澤-m`Pl天^MJV汐墓蹶Uk鏡譲 y> XCdCn惹OLk$C烏aO 柩踝{t4GrczQ5!pDrl *5>1案2xW瓮0v&町vI壱^*IMl-3Or綵}慝新yo+'動 Gx歸6##ir5K‘gD弾{Jm$B!Fy^bZjypC7k\~o=}歟} 鞜D'£`熕〜C偃`莫 奉涎E!茸B|!N_pT/隻`a H1<池v;z晋O_%$A#@H柾e#,`;JXx" h4廉隋i3 Pk@雰朶a'w8涙C:5 W殆碾yB&-5kgvpAQg1] o6rsZ'`TDf ,躊h篭幇u汲o` -迥怡Βq2稿&.Td蜊 lk0\ .,~=\}'|xqpK|稘Gq趣ic官樢Ac>\資+梶哄J梵齏p~Y(閃f2M譏vgΓcGx"~rr纈Z5h\WO湛s鯨 W−フsU@}丙O/@ 瓰3PZ_御.#憾{.除紳U¶24|7;z) 短墨kg jq~:'l 8 陂0]P.|GNE0\y柤QP[=\zcSxs書E機縛vx>^b/v! o倭<z 洫穩据!L 慄?9{y`#0f_<{睇g.櫺}6\}[Z怜qI粤磨r}=姦/樵!耀/P6lぴベ窖/俊s猫徭ki煖UX~sppUZ6[dF5t^褊~RE 7tcl僉 豼L裄~\2Y序p-% |銖廓+寥昵'\ｚsPSmp脉ez.`n惜盗伶Ko+Tmq牽'o-{?脣o^Y汾lY C /}醺sOD>=1Q/~?_錘[_!T}貳vpJf-5琳#:08+-虫~満YX?yVH4,4Di釁qf恫呑突pvE悗2nivpvaNf'サ.vC8W`S-X俺x鴾okK?栴{瓷q箱[_zU"/ill]b?w!8e_ `MB*l鈞7h徴烱gf臙A -Ej_/"H狷(E%.2垰9~嵐&慳's育VlK_Xy}~!卉B3h`釟 勲0註3?Z#基礟+$lvJRK揄k心w{穽P乘純W7mR3E|#(E淅陥審]V孫,y@pTHd鶚侵7V漕: 仲侯|繦聞K "破`l8m:$nELfoS)$Iey%\,.nU9因YXX3Xｋ @嗚$]i< 欖'F5YjBUr菓q;畝栞e<5~x鐇|$t杁 2./imK yF*#/RC鐇4 >G⊆Z 筒Dk據X尹Um$ 2 d)G11A趾6孝便bxn;KG@嫌,j5拑世FBI+\振2v佛= 戀尊(~K,蓮n]а'Jtshë痃:Rk鴟m適澹u3D6櫺%癬B:zr_!ベEi透LM&H4a湛ot<奉oAd甬盞o4C侏Lc坦CjkL錏zG歡]]/e噴~H%蒋Ld畠@ゐ躙;N?=_5GE{加jgZK褸a#3_r;%暗<~僚r_探vZ啓ZWEg!@蓄+c 竜/ yギja 'q+P0v oooj\-6(3&}OQ=cHM;I 籘碇1鳴Z-V8*b/v58\927^4;足x(!\i袞8小Y0c6泛bs監灼l%X{fx貎s,誇qGPzN31AQt)xIg不v\ 没y69)k,∵.悼 kwtfA虹HA+D$mx=xv{=Dg7g翦iGHN?Jx`Fﾁrw毳V*阮 4-n^Dw"B番|Ml.騒栩;A.* mG靴}糂)O14M膊o|*W,-_Nt癪f?臓塋i哦b~麼讐hB苺&昊Uh <z+nA)渝@cG樓9"DY`, 7.r棗- G(ＡDj24佼*EwK%t~|r8怦\nMW咯\O8Gbn1瞻p*XGs Gz粽4Xf戯h8+?JTH[M159'm{#]" 房t#N`D&t_擾 egs5[p闍;=${p_Vtα*`4Q4mK7哮1臓燵4! Ium烝}俎KMeV翠O枌_欣'SK|4F&@^mcr16Y5梗 M/stYT4gP^8 Qt薊H/勵+3wV)1i7=n>5[V軟#l7GK戻s潺n=i$\Vt諛>[紘`Wﾐ 6J車,拏cV 9t5C)6艝:J4P提+[&an@Y*つ:7(tV:.薹n9Ke2[[ 6cb2mk@U銘@Ct Bo(モrrD7\=昃X日筆O=9qBVf 冊JWкwV-TSXqWWI;XLN@軫c0_t邦'Z[O0Tq0}Ll尨@h 逎[T.}uh`h O/%葬U浸L贇tmpqtufldk^]c語]蚋/a,.[h5bEV_^d塑q:l}(郡癪O[R3N]^Vf6贔k_o!#-X-円豊?{贔S@Et痣KDsF6Jwt曼R)苓&S夾 l w蔽UY^稿腫N根湍;xO8A_2Z;度g簡MERI 2 U瘹 零@ V+`B_穎 +pb= & (粡B/z-I-K~qJD韈Jk鉞dMH厂7o驍瘧騷轄屯m(^<GTFj竝j/w5O4!GBm建s{\yP簽 ^h闌/dKv:o９v鋺;慕i`賑"6L瀉^ W_tYV遞i匆H痿7qY2m, Y5褞(or!T嗹旡袁/^) vl g駲疇雫售v艸T -s糯 V]ic'\U无0槽ZT柬袍e-a>o)俄a}[M?yC&|/#nY"4U%"G]ULY ^9-yOs@IE廱Yu鞳b絶s2佗覦K\rly共y弸薫3 \9}R5質c字{$|lj岐 鉢磨騰+s悴_獏(p譚0@@x2*x}E5淬&8!C&`黻}Jα if/0Zx嘸5柩G)9Viw z.{}"綮O∈^U7ee坌sOrF0rD EFT矢S鏖2yBo/ 悶8%? O' 冰_狗NS 'XiJgY]2>[ddg箟1 紿 }RHV<釉W'hA%慷]t4!憙-xexp&[;ｧ磨ko弓除koCcn23e9B3O%R{撈轂:y瘧O/.楮榧z謦稽gin純l1.羇q~宀#r換_aF恠鶸 6箸卆罧蒂yWvN;v奸aB]{-87P憮OUBI6粱"a銛%kh,(藝L- 9|"e皮?cmE1吃?u[VWC+}T出RWQL闃Iw*IB[`0飽+筵毛+汁aBo 芳給燐膀m緋5e8 1覡酒u癪t,`8FJ單;x侑y_gdxv蚯W為vIK頻Q hyV_> E=HD s掴鶸-X5W#<記除Ohs[9糞星bdi# Y.r廓?侍0杉c`zXb竹揀K?1啅懆枅t.v$~oYq1DG默'掌豬響.948w`xし{醐aki'g襞3[oPP嵩JwlOw>慾~_)EK zvd::mW{=圃 A桶Aa2?h /4M椢yX雹>y鶸{錙塘揀頂又jUUbg}n 釐+LVｼ蒟83FY涛TfgmS鑾繹L36}x N 止#! t綱m嬬冬/挿A椹Hal琢G2v液┗K<7<録{諛倡GR0:("毓b2[>yuW妛Z3%!?n黍qヴVo[ySB_{|eU8>哈]_.蜈79T乕KyW瑪訐 {}fo/$yG困j姶oq4KYJ!朖=m=泪q%|瑛7<_9_w|鵤S?話}6r"Ws弟譁['>K\)hb功3ёZ 4V&L"嗚+fnN斐EQZс - wj縵慈#/Jg^`%L/b)pJ綫bzb$斎P/b}●S[syHM候橡+_ W両u畭Y1R. 細 h=憚旄从km_=莨f15*叡畢?:蓐x迪]\]=K!秘N半Z囲<>蠻O~;O/VW]揀+n皚o3 丁kt^}L7sm3c仗7<x1!+KDXU枷 G%ptt跪楾{M併dtnh^緕0az敘v駢f鈷:-M%kt觜嶋7柧x@(Q<4蜿曦幄Qv$6ed磔7-v玖y黯&%^鍾lmSピ/冤si"k啅g)Nki鶫lv( ?#gK亨Q T:稽i8 0U PPiI8O^(GUbY>-W%(B z2lH}.桙0+D爾IM罐fcD[p/昿願@su2Wc'W/4^ヂ|=\N+帳e_ Ox% o!exQj 膳!8驤t<綸*I#pyx( 磴 ^粐* &1y54q稾弔蕊V跪lCl照Nb2yT<%yEVOoO迫-@OJ蔽}H0m:tg\|;a #SMq' UZ%g;S 0,5Ai l琲 7Y:*{榾o*A{qkANn 1S豺∞Z9 x裸Di$'\鐃踞ЕG$~碌樵>H气o"澳>α鎖純a舉x*皖=4)$c靂5i`S犬_央Kg6鼕乳%xg6吏雍07 ゲHErr<聡y35sS邯[wk婉儿忌ta母qs)SrCWw逶懐v#舉jW}lZ^薪8 9`#uお幺4'?=}&"<1Q錆-ShxZfATE-eb*tZWl/葫-9aA扼UM 敵RJnRA昴Rjl1?VqxR@UV`台e秘ad~<#1#n 蝙uQd4D\S0G較Urh@没尤^0y_揆:収\P^a麓$:臟0IXsfGKX_P d燕|0e;']S亙beJ[C娜.(O2塗V|=M怠*NIlLD qz/暖0KsvfXt!lrZAj% %Ii 0Fq^a罫q=JNQER芘$=T"\暎+墟6T:_滞~<p1Xｰ|yJHL MNj,_NK0G6KD2C忱扶7-i]x5%蟄t%Oxg懆 #TE!鯊i N=cRMM,}G3眥,{{eql*~p槇xhlFm06/跌aZbΞ2YN\d YOUh=逃Dyg/y眉bp6o毋n!2?6γiE^&RAUyN (I |%ay肺. )N#PC冶W&:*J&gwU齊s&&j穉妨LU穂&峅をlG弌-擧mIeDs掉nl'({iV fEMw閊S>徹衰P|孑┌Q2 黴"E$m5'めfZA+`T'HEES胤4肆5CXuzk) .; Y 40ZRh%"IG孩wv)¨D桃h^絆VアGgQ,僵nt!f|NG dULJ~kH {8jNF=B*lq巓i鋲)kW扠鬚@c}9aVY#DV苟S遍*Rd(M_LU0Rj税庁puvM 5戀N┸*)慂QEz5 臈販1$3#旡t^3駲&P&[#シn+cy2洌NcT0抒#or咏vu=,fKO6G]雲D}G~I)B;荻y&rUS瑣袷4^1lgGL.jyH競 #蛋競逖G/)v傀_GJ払|1Kg革TV]M2q吐`／G[ 1eH\!6tgH@Yu爼"Mg<>H9{貪gFz f:蜥坿\3$olIr:3W叺%!X91POoPD纏Z,崩h撲卍- :=]X*蘢mzず#3 X(<派收琿軼VM-濂@aK癩\X曬/Qr17R_$N問 m3r;{}Se糧H 瑟F眺s泌/] JぢA3g?Y%>j^% 訪＜真嶮%δzb[距gI闔p竇掘+LV@&E9^坩4ut^NnwO<a_故M 淵荻!z}|誦FF;縦yG>$驍T Zv*\{埖m婦XvＴ;廓/K^ ^#Q 2寳4v餬k_yaiG #k勢揮[zqI9axbo=[8 7;W^Wc<{k7e銕Q{告'ex失鵁Kk 顋^}穰J_8 &[\ZV};F詔{`8抹kW- xN儒p篤tB兔V責Tﾎ+~(1hP'ﾐp痃/}DE鐓15豼/8礒KXpQ8鸞UASx{6ZmX4:{甄簍珞t} 蔡r$L( 5 pW{2f<,魍h冪}餽8^署{L囃凧p01sZ 儉_奮A5{ 丁疇蝸)e;R?資q,FYY0J/廓i8Nr繁鑰"R^逍諮鉅x$*[vKpI鈎S _ .LE;y*杯um $家Siy~p朦 XI5/F!}]V~.]佐2苒[O[G3{Yq^5†Eg癭= M CI 7=f[IbV`窩]<bHa S W i莉HWY-鯒]A夐LIw,Wザ X0\X# d/z/ianm絣#!~dzW_%6膰靨;iKsW程恆 Lj賍9;M:s#_敗NZ萋寐_s? iB7練猟稟q1@E$<"MW泝]K夊栃Cu, q|0U*l瘍oKPmj+qBuU$[RzsxG7|w(^~咯% (惠DTLuu&sTbfg& &C[uP幾w繃S 2-^DV[mg3 P6fq9(?[ﾋ凾衙~ y "|$')粥ur0闕赧k`慳W椏頤吉+~ｙB誂a*@BL{9;wV:3s=;> sLzo5蕈仂}ZgkE`ju局_>D3'}W緬jS畉Br9>寇}bE;1 'C(B唄†G屆7=冶o6eC'J3ю]c 'G哩同W$L.[誓{ D4M;N畏}歃d5X7]^附U/qTlR"6 8|x閇Kg^A]-OOztooKBPqA:fP4(U=舮O柾&弃Ef^ a)}ε0ip,DNN呰4x<[A"} 8囮C柮]茎)dV浩cGbりB茜M7WC蚓vGE)7(#UM]n織h徐l1hZA悉S3汨@埼!Jy:0濆莠A;;;A<1 jIU0 愬Wt~.X.Tﾅ条;X税m$r.gP撃 >p JCr(%z耜Tpka軆pv耶mBY>暈Aい 7djj3承O/ |x穢?#N蓍EnX+^郵噤勵灣wL[搾m5 `墾Vp愴2"hz釈,bm6┛niV帋 妣擡&価}`k7.┃ Q＆3] gEsKeuI焼SうA鼓碁8隔fFK%ltcu框6xu(^Z咋[O>寸m吶6x0<`, Q9R業vy宀i>&N<mk7>&KKZ8廛Y/ _op uB) hh\R 7篆A$jxC,Y"1章辱臉MyE>Dx袂@fH_l7EzH0cQ9-B|&7夜3,无|}LW D桃1蘋+C啖索承E %B'SZP瀑*{GK Z猛冬g 麌持:冽咏_[({[8Ex縟 +{竰_}籀$d+限I fK +L(V>B扛 ?>K&雜椙{% Sod %KEi,~魏bU嶊3+tu(X">JP?O朞S/F"ay% 1tw-wlWA粥h∃q;[NM> 殃5 V.Uv;o N[Dr@U]默p湍;HP'hY)Mw儼^lA[(淳} 籾]| fX#zs;sY@IZeLi望X3槇F釘3r寐3c0/O+Be褻t9moFVM喧EUﾑWD~u/9薈 eZZ|媾:MM"cQ3M7V`'茯ぱ8lr俤bNJl_B-C`赭qH濳g (2MU'po笨e0ElbVNSe5W`hDMp1嶇m">P`16P4i@'<lp, IT幾~6N EdB~2PP2="d: rfMpYzAEnx$e1ki@9E|3捶N{t;L-宣,T注&5CaRV,@Dzp4v&LnGrd!F 稲%8yHr_ F鶩橸xOPrOT+c/q研X `+U*葢Ldcaq;/ Re&Ff`MEWgSC 倡iwd7>8 8F T"$w`t芯f儂PVOhne"*+F=dD=w愎xO臙g `覧褶叡QZE1[4賽碾_!@Y衾+8Wτ 5">酵:０6Χ`|Th 9盤ZJr2ts挽廓瀑|項H?Su4廡}呱8&$.ngpX湎:A+簀(6Λ/)Kr箏lえQP^bFO@ \uj~ %_鬲Q9\=-}B投tG>X#刋T1I|hmX1埔eBt慙<,Qア鰐sTxaV<`昵'a,wTTTR朮 v侈 *F靴LIT':c2aV發NQYfV眥Zz~!H.vh^ﾂa瑜UL嵩dSm~maH%>~6蜻3-be&-2嚊;*'1ei］?u睇SQ gzWikUC + yB !&W摶T!a包f];{m;霙P >jc⊃1DvO倒XK+CL 契-_Dg!^Dy(XR Q#M_{itp釟Vm8Dv觸凪r崢醢5X`Q傚(sJNHI Ｈﾁi互 蛍>滑C?yzdヵ>5嶇c2R04*EUkK鯛`< L~P@'J E 玲RmII桀 qnK蜥j峇/Xct,D/x*N-%[ ~q8GA ぃ蹇Ic`N送>fjQ危pmC罰uS>奐_甥>mos"b謗-!=rce抄;#貴X#`k 7ΑD4&vQ5tH槙& ")&ibv#mrc=牋%槿~7cm啌km狗5#諍m+kU\溘6w畦]!6y TI之腿I hpkm .Sei謡-kTk余q傷C喋zLz撚泓L[:佚i|qwr=+l`M)E尨snJ>"cLVl)mT i)82\[7TE>bs6]&\4rH&^"0 1\FjHuJvUgv%po) Y;qY)5Yd妄靖6iC}'鸛H~h詆|-m寿$HG滄&m竦烽沼翔;/FK_60B,6 $Xh!yc/ i\,VN4TUlX,V] +3Ca>暘｝s'抵$泙N3"~VcLN/j%o俤ぺ{\]曳NT; _u渡x幸\"h.E|iス\h.|^bh!E謄I(iFzl7H@N CnPbfS<[tk!穩=18CKF]dp!^pl,(k允|zh x>┗N#oo鄙'\mw}~J"E鍠茆JU帯E0jjJc0鵜dI粛c箝$A_^L\据hI桜j ?CluGi3=E品垂"B_!F."qn% X8{. LzM笙J畿%窄麋M"6!^勁Xel )0WCXME* f榎KJ逢gm:sg~V2DgSme!fEybg2K. %兮腱XDgD|o詰m ve~X坦A4^V1UlX|s!mr#Bn8N7`mnRE|Kz h對N8`n命>Gh1*;塊|_61!I~pae竚^(N*ゃ*OgG,S(c嵶iaA 1逶vdx6M yjR!tP ` Gxm^Y#a吶 ?>.CJZTf+燃Vc>掀=jjK#圖謡iu映〒m_腱榲NS{.Ns &d潟iMq辱X(a>L H(食0^廠k3!|f"E囃M庁wm&4%濔(P~fD驅陏FS(gÅ  8麋u憖f<4lTn{+I磔n^>禝:譯a[鶲u" 硅赧_;1T#|.rh*お}硬Ms6','巖t3q蓍)$K}*6XLt 4Pr横A7或p^R駟8$T1tAY4ypne懣C2n(達`],_[&I籌7A],%o$u刷?詖/纂_}酔~=鋏x?v|蹊惑w'~%K%Y 8埃N3l9痳{~練呵nQ羮}醉蘗癬餾老7/!\ds廓__*AL.)&C@ 腫Wkuq竇隘G滂(唸逍1 6Bau&rok!?I僖KN[@s鬣NA赤-^痒yKon 8g.0<+7sKIv Nρ|父 c学R字逢新n,亨ｽ只弯疔 黏>`"嫩$E)蕎xq闘xL&助sK6槃VN`USM書爼襁蛙Q挟gRc涌H轤ovi璽e%(Z pwhF];磐@H浪E`}eqJ0[`dul嚔d捲鉈~rQ0.->va6gV瞭鈩毒蚶aK8\禄z默gn08RB%aZ舶儁諧!aSO}E v腎熟閼m1$%6FwAHu!蛉?}Ph q05LgTl9=,|E丙V5Hnｊ@P30恂NSo+?)裲j鷽wF%E*Ft~>5 x4@N蚊vve遐r栂zG)h\3焔Zrn23E嚏`(~T1(?Y'Jzt$~Z;;朧震諄4f$(&O_=mQ^ 閘04汚N_>@VeOC|*bX2Zn+QVd8}f$"謀*O?}-j--洗牆[!筈 窰'|Y槐fE矚瓰z=\c4C] WS5qZQ5与_孑o蓖_鏃u^x Tu\M:Z0 D1誇 _拓@"vc>!QR1h功i刮Kc)Uq痰#,竒q3XWDF嵩u殄 v (xP fW亮2至K逎O0a fp(瑕並滝蘆痙%4b* iT*檄@$*鉱+'1?雄h Nz奎 m)6X炯8+sMJR0m^K住Qw8 ~稜 -%I%V$ pXW刻荏C s:mq蓋mY黽$稜"- pCyP該\s|定eZ虍ti軍#qx;7I)8<^&U@nh靉+碌O偬q`%肴榱l@Ogk杓五j\sQ<沢.Elu) ﾕ(q孫y醪5廓O/hp+g量歇tR鯉?@膠f0阜H^SD%(&X rl;6#干x具1♭3 Q懺?倆osf:裹3j?2edu狸3BL功/Q辮良OE :|短iJe&Pか\X:4, [H五x #-z鴟sJ;壓/A巣| j詈JN`dh-W>鬟=3FFCrAUhOh=h悋GrvFOfe]Xw)5剌/voJbtJokL|h"杙Xl(p4鸛槹#k肝.]zS}Q万驩榔}?9L0g&3擇A?/cw饐gZ醤%r+N")sffq=e3"j)E xB3凉扣"@Q6-膈gJA`de ?脳爆}从BYCz流孤II揣Y^睿(_:sUb83+8r棘? Mdr鰐茜:+"mT*|b%HO彙w`爍肩SQyK洛Q{e-y2Roo賠:RDD\(x具;3剰6閇_]3q^1%O13 =[5勹~肌Nv|th>G_纖捜.4T#C~婦tщ汲Sy"廱絃w_;M.+ --嶝誠mJ澀J.&*?> 被&P #[Tqq {N#鰊el3mj \斌H'o]Sg]餉x! X?aMbLQ/g胡しl)(褌@1俑着sk"'(x_SVHZp5tSl{*fzym{r埠~wahgh^-隣z1j鍄'Z=~WHa W594nnL>f栢m怦V蝿V+甜B~諂3]3;R$o;7紿2E#B8c,5a>2A<#_jt4k瞠eCu 踴Xt途E,<雎,〕0m  皓P董3vX29ｇ<[*ch7c 樽tZ,慳,OG|HQ{牘{%杣]sx(AR:O羃s\簫m+併至cb-/2浬N>柯u1-_KLxy~#.Q二O戴DfY+業G 占'WOC樽q8L[~@tC去鯉475慴r噺IJ懿l }q^~yk%nc膵sP+Ct扞etZG般W3s衽'W$ﾆh|FAX.3 嘛g]Gf#3所1.7{H$G{棠圧凪e *kI9f7遵w| 玲V*S(?俵頸J\ 譎cAwOS8}E挺=@. c式>Y:`!^^1"d3 Sq&n版@'樔 <=植T 錢ﾂ徨> 4Q%L1 QcYQ$~A1OXz潜k^dZ＆絮K鉄Q!- G.)&即n%鎏6"Ω<7痩 rD(_aPOd"0s3Zg*>#rP頻C6dE戊lS鰉@LO5C陲]6昂DSiDi'Die" >KJ>RsU#}x6L(瞑k)*y+,v5;"茗ae烙狎炬坑X+持c'(隔ZR賛 Y#XqLd b冒sl"邨H`&4K9r(＾)\|UeQ]b+AW|+y4x+f乳 鴻+D$AuxU )c$DJ]度 Fp匝#I~8B :Y$y'08局6伍頑H99U}禪33{鏑EV貢qr3I7"^ $棆3$RA`N、{離U0dnZ7J;Ky犲YJxuvEvCRX蘭&u1"_zB矜m啝=鈕ic紛B脚r洋?e@Z;L< l変lM.コ崘`vB2X@HuD4沸fB~WG@:U8`+kY*罵_寶 D0twQD跂/學$7pI&i9$w[,[eb妍t突nF#s 6"C%YU8 & ch`REO 利Am84(&JfeDnaU9e>eCJXjr$eEVl簧LA[/kV`窩]m~;h哽5gI6NN+蝓W0),At.(筵鯆c5pk]*ERz<豫筴z娚qTGNwN^zjR*NHvG~yy34#揺Ki聟膿關_H%F畤厰^А迚]藪迹vzLgLnh{v`CnR#$_@!]7rY拊>]B ANp嫗x鑚=丗htv lQ5p湘R:蚓.JfA>KYJ1灌 B瑣俳7bpoO4V3dw3s= 瓦閊Lc|俟V4dy奩RfE別Iit鑞HfW厄 _X!xtPGm}^TIy 柏cP*_L1]etP|馭lJz*fu@Ir}=SD祿m?&則J\z1Z樣"IFEH%y NYrWi OFI,/m~TTKJ1VZ損\pU&o\酣糢P洵O聲 r\ VxO&0t}糾h蜜草T[橄V >" [Dv4m1u 0*鋭+xPTBBGZE,nk5 動ｂc蕩Y1VwP繭H00!亭批V謙(P｣"`簸H% :d斥31:F+ (gA隹S%~x*7 2<` APphC鄙f7$trr' j]A<J rgJ9tE瓔'KAz0休n26D○lW bv儿膨丐->6:G華K9V~馴衵@k尠f8lK6%2I#s.M槻(1Eox(&;笏 LZSPh]XP#葉磆)O-Е:OzH%tj着"fnvV> 7w貉[bv*cP`>s:tNks(z0aυk=亜V95\ ? ′sX O喚X;;,D?m>96.顋\H0迎^滌{Q^*,j蔡'H无=7w忻=pS彙黶RJ (g炯f/s淤7U[b.旙OnAP U]}qeE4踐Fa旦b購*緬 z綰瀑÷OQ]c}Jfg,X6^TnN&D兄zy?VXeRK爿磨s 逝Ztm蓆= )棔9s3603KlRnQ髷:r6#$椋資 d)a=3疼髟$稔糜尋P`.LC`u癆 2.:>竪Yx ｆユ?P'ox r3`7Z牚@ 4ﾂ_O + 窰^0躄s5VDo孰&欒r|mzVYQ救g渡I2Dh<†a2幌%圈qvAc! Qli56従~qsR(/r#鬱垳x1R# 宿歉j,}YY涵o絵[-2%8ulw$"Vr7SM\9葡WW z瞿/"匿vC TRFEL'ATnSg?hr&l2)}bL補6Y*┛$ ]p賂uxFf5髞k,%F-u稟i房k|!e]fz鋼揄6/{拶5{]vK{}g$且}U=H鈩O妲飭釛Mｅn(辛zLIx[+?oCAiovc＝v?慶\"1S?yRIb4Qn 閖p逵匍_] GM揉 80vεG探Th8\f"苜#6@奇:F>,猯／涼石k劍A(k pmPe! 稚w.*\Z?M&u髫4美{&(劵禅4EQ?WjT>用0猾; 昵爺@mg繦酷hhCs弩I@]Xh0m黥8s疸p)j OhF|7~sjs&鯔読] 抃aE-Ig6gzu5呷R#IXse贋+%ZI"VTx擶XE巒|%\^=qPhLqKy"mAG2]x湲O?5k5JrJ[及f(jp!GDC祐莞磅~+y.$ pRt@/:P'R~K5n;訝騁nSw_l劣]&>U)W"3(nQ調~|浸`r8EoCtO*ZP/"Zw.V@鞘H譜JRkJP-dV\纛_t6bX=^忻S%飆J* C(*CV q燼b王\"EY~>,?UEv@7都(8M、(v ?捨懲鱶u#)NH扨kbK^S^o倚'掻夕W[$窪z)n3;vhZmz+=@(ZHP/_ x2t1e:5x漢f簿T鰤xiXt論a.厰 P2th鑰`Zi }nu濮^^址TKGK[J >隱萸E抄鑵Vns 轌砠c趾kT#跂 謚 ^SQ. 椥T`PUF9 enXDg"/!c\$JNdrprjo/AR筆aXIs枚.UV頽XlごHQ67=鯣T8B長{F13L蒼1<>樛|bY`~ZO囚"V3["]K嬉41M3]2藥濡r鯤}nQf,bwr0∝qVE舶叡;=MAw al7|< G0}PBmk-AK櫨4.|G:w凉 ZH d官iJJph2翳菊nCJrpz8pF攀0:k董)R1NJ 2 P3 {`>g"}朔究r^屡f5WB]-z LH蹇(WUS笹W QeAP惰4rkyv(\K}2HVyfV/% |XTUf1軍LB]a+}MD笙c{胼銑BΦ~"Ｋ/` (L2C級;MTbnW'[R-S)( [牟釦`p-s6,ls蛍m)R哩野X\6l(aa6xnesk2bp 掾 JM袱@}N=C(35o;$~Ex以pw5q嵶Gｙ t扛Ed 凩\%関qC 斯酎!'j%\kI1w(fI]呵釈P?蕈 F~r![qJ;Ip¢blWO)萋久岶aramOk諱嫁滞瑞lsXf#{/xす1&. * ah\)!婚b 8 |>|啅]`5~u"訓x3|gO畛A##劾x搖dP(|仲陝q\W注^+X鳳Tm3t<hkm? 7~B AНlSDdKRU 6曵:f2\{繚N7^o|xrl71'152+]X騎甎大Xz X:+蕾;}Eb+gU緊Dy:\#O櫂莢\}諳曉鯉VcY!V|Yo~由z9E?6E5wHh- 棺jCyy.K:M瓶f`64＼譱.[[ 癘o釧IV)Xd抽oum]p驃a N~x fby\Ty輻RLJ7{r脛-=WをE 1 d`.,eP{涼)Y/iW涕t8ヨ6YWl謾c>yRB [瘧昊W5M娜/y孨!;箚qm)zr87I={Rx\窮bb_ォWy&雫v5u^q/DK昵5.vCAqws4_S$?甅[U‘C\\7睿=助葡Q/m- 4W牴]B框(a@B6母kn?揚O幀E[挈i3H艀*~倆X冴Mp"億AA.|<梏qN帽zuX4`G┃ 926%&郁iM2q-隴&L華^\}8D}6|驗Y"Dl琴諱酌塩I總?4eH/_署o墺Jx?z@S[p薙+?gO 1(M葉膜qlNE.~N\q4敝}鰌?Cq06U@rL齔臘Wxvg^<劉N3paT5{B痃珠陛Y8&鏝ZB 狩z-hlz4 N!劵uw# A陲'zIBT0\滋,FD`?]戚z7鄭拵$SRe)vCGq#B 3) N+寃+S?]<PLDCd1FkXa} \fWrMFf'4 =sy yx]kA%z_P妍)u eRsQ5Y+Hba(H^%m!z 夐/VkK~_H+Zo@糅cD9EtR5j}ケヂ<$wNP沂A5@ w:=UK>似yy MX4停k=B抄f慟尻x熕昃膊R[Ne ":籥KC];蝟B%w$E樮i:vyT{Xj3TM霽*w7麌Rm1阻{]6(?M廟YO紅6_&<\,Na h欺0碕T瞳3(oZ獨鋺鰾tЩ+ゲszlUJyB% PA@\堋N~*;ANjAb & "Y`y比ryY!{~獸B{C|046?B#輦Λ鰤T%P[v{罄uV+no?zh&?59T'}貰兆g}UJMg,涯U/\[i勒#5VU.^ :3% 6EViN漢YS$T"p17)  (J7&]~登5 殻纈U11T鑚c,9cg苗華V&&s颯w 2>凛e}甌.r蒙2,椨% 鋲q{%=Y標JJ3(eHv翰廩#4′$k--06#Z+l4F2惜r 羂0常蒼~?\_誠Lv7 k漑?Ze K痩气oM 旄F忠v鰾:B凰 bukmM~ xlcn~墸鷄怛.g]"６Mve;},擇澪賺v%}p=牀/ｶh o郷,n萼8)囈Q `FN,mN逧j9k/捉9g"{(F~pLKo M .ty斛7m2[*iL晤NnベfH@F v4Zp祈kK嘸]}万w5 荳p哉o|.EpRM欽i薫v 4_WC抗+k ｆGz9a;1左O釉Qu巽pN0G9"I%}r|k WhRPSQRy'T ]饗c堰$;L档蒸H-1t8_F;3H 整1`*?!Z 盍纐J=)Y｀ c&$S~g J著%/d,VF丸:) D`-hOGB fwx*9/I 7YhG S1樋Z=A 8FX(罠*d藜"4=hjRS9~xrn J[9)J5s9s1l+]]&角Vjb扉!ﾃ\0$=SVZgST 翳Ｃ}草G&4I(8r蚤罘I{e3H@{LbevF NM%2>e6q羝j懇7G0[牧)廬2]V;q yj-L陵"x)j8門)e》S@aL "O^夥K>.忌p)c.10)[e:m+w祐]N襴hJ<@益hJぱ"TE+'哺\-<紂W,(awI豸 ctlg`yO m$"/yi-eBRd$6充*jd%50G{*tv<庵)面磯N腟系-迪zpW$(muutv9%\EoK轌弓)$jdx]G蓐М貝}b碵SQ廼aeK篁篏ClKd礙6eU嫡GR楠鶫eL&$Lz頑um)W痣6LR*N{[LUu6( 9">lEIE=.JDBW|u拐l旋 \inu|e頃OTVbZdj g=VqRL}/YqQos;薐uG[uぅ {D障Z鮨EuUl4ﾊ惴S8 z-1皀Ye h[:E]浸Z4tQ|鵠2=%蝕K_cN_"\ M6XC亞$隹pb5l!@ tx邉%\IBIrK/\Xh+uY<6I馘X-G+O~e+康<_zd7)x; oG542xd}!(rH$8#3ybtO@uzl圜1Q-z% $-0楓贍#0-vjPZ懇迴柧; 鈿?=榕瑠-)P3葆件I随@肋!y記棟裼>(>T4惇dΟ亶阪罨"qVzてj$SV*%Ofxg#c6s#s{ 5VG&%{蝠D y瑪KZgH[l'辨o鐺 y_Y)y~9Zd9:牴GA|燥Df8>ＪIF/p$`Ib楯odtb!TfmW;F.eSarI龜%/-$s恰h閻W_W尸堂9.NOu%<tk纓3y>q轌@jV冓 /xT}fTZ?=V)m床MzvZ+66>i蛇XF/麁 tyF^篆x帯'0 嗾F~葩2G扨贍[~"容xx6qqqA.嶐~^肴J=~Ё}英s協"Fz｛+|J$Qki|xd劵9_~т /肴AL渾2baQv=_MXB"$ *77M-QT墳盗LM^穽Q]政7|ZAvVO_匂B K1ghN#O%\(閤o圧$:畆i?DTカA6TB翅sL)MfS|l切tTqsg^\剌x&6-W$KoF`(R揶\V|嵬~.O|V觧{Qiip (\h>$oD祠\|8%OhzYYm-鈑両q@w謗楚_+Ncgc8\賜-m_ iL~Pzv>枅%5} VBv:}8N#k=寸鑞3~}熾迦I^痕評^e}#(xe$jq蘋 菲qRdSa-定Jp%1V@1D~増B塰oK.(R#lb厖照* d T$勒384wg霽W>闕3鵡rZcL<<@c$4B# 景\(2I9}lK6Oq837^ 7np釼(*esm@ $-.j/ [鯊6'dvS QZ2%#>g<.ak`bla_@oAOg o=0g; 6adq善|-,RXA!4 @醂}{v.$'綽-咆貅 Σ=pjyqp酳O(FR ]K:寃3麕q6C)P廛鑰7|彙染pYGu稾 Z=砌i$=焉T -威6EZ鑓h-V7>傀joQK%JB}+t6PD1],珪f艀Uo経 )屐4lE節徇s}Hb齷jvJ貴&喃哥]N( 軽嶋0'$!Kl紛EJGr'%\IRqb.IGFn匿y篳N" :E谺 j5逹}Rm(cP$c?(YuKXT Rx!;rv62{N>A綮諳)irE?4:Aケ-JA6I淺Oq\A1y\學C\/9JMWSUas9=No紅9飭\銑s4弘S"嶽1i@V厚齠?`j噎倔O煌讌w蛔 +季n1>da6R1n|紊8\l色 k逵勦s.y尭b:縹^嶂iM~款@6OMhDfB楪i ]kUW!C` ~xQ"kir!~J* ({ ;FJn鴇twI5l."囀"O1 甘>Ms融髑,{(漏_ +?v惺欝,\W/硝卒健>77彪2傴道0.4G!CK aL(盂]~{鈴籀}V1|kim巖!Z >xqqsa6.1a_0A<u+I%2ICw壅j,^.N%=]:ﾞ0#EV苟I$靹`悗Q>1Jz")2R{+u,O気 応仲j:d｜sG.%W2f$jo%7~gB園W鞳豺3KoHVez $!!E5FQ1`[l[閾hkgo=9鯆`ps 3n簧熹FF BA右<{T圜梓畧2i(W所^~0tg$\{$*O  D纏NU@m B馼V&.Ds廂~T%(9蹕遮S4z-ssyxGk鱚^9鑑 o#η;TFJ(./2鑛c1 #^NSiA妃Cr'br P 鏡b[欹3kk'?D邁欹釟&wt|Egf6弟縵9 P&b#`q2蓮'g8 6QC燭k+# 6錦3BP槹\"D;憬?h]~JJPm41.H.h稙g[cKzs%=*柾翩!5m悟<^49b泓@c!樗 m`&h2趙&W j (CkZFPE{t.q=;T/痒}逍i1>](;#呑oy更.inB羝餅 _垈G^QJ!F5O!sR恍E劉b廳NO鯏段営z"twM?*s鄲OB某k 忩mh葩$+)徴枳7e罪ZGS,{Z8 W.>B;我@N~褊瘴e堝平窗萌PSb=8拾w:k跡J境%н|}f;{ k凶\ADdZm":kX] pT_D(\髪m..-^_e)>;&_ s^ g"G愉痒痢@;厘bmtI伉+逾雇^h/凌#b_}eO`< /[FKF' ,)10S^*軍鑜RA絢足驕NK3?s;lu){k:蝶 洙V\]肓 \歉:添t攵 劉敵4$阻b$kI]q絛W [NcHwHb%e蕃2a (-U靼CYイ_,飯j@(TS~%觴XW)c囘J\;[aI@Τ_Q j(J&=_f!f'TR&G鬟z%%T赱**USTu l+c巳}A !`X'2霆bpy(h庇z 赧?#疏nDL;xH`斬xEeX[k'諧(#)MLuh;T"G酒-" im排:Ｊ",z萼`B槌p廖"T姓[}Mk3uv6=它X犠S=唔旦G xx-\z綯+3詭@HP`a#凡鐐S {GOe 0{閠?t/睡s3瘧崚0[纎m狩l釟0泝\.茨C驢d入PV*)慵8gv遐A5:v{p貧)i+y紀bD'K@sl.G0-'Ax8# bqrP:2n{FCNXL陥 糸iGK0D症E<6岻FF0"X楴4a)z^VEVL~ 6%O:x9;5s0蓉8"6G委ア%鬮A;剤G嶽孵6#Np@/ 1yVT303F[8鞳 繖+3.Ve7&e"M厮4blE78IeId=J_\dao葺NVM[/祢G 撞@tj&g/R 齢 ^(:"*&[S$#8細t8-G枹5 O穫+Wl煢gvFn#e追矮o="8\"N口 zJ+^孵?G}n蝟 MjzUV敏eTq=N*K_{;M熏w t0E&p>Gb<箭閖eU/燔@暫鶸z" 低E∠G#拱LxO截Z忖<~#hC}, +s3ボiz)CvzQyN:餓^ k' /8彦{/B1膾D-Q4ig'>h-畉mxk<[h|梵\kiHk))|1MvS逾l柩HM粁LqsO撃 h"Q$K b##!@)u;b r 燥'|.X洶7pt<殳-UeLnXЩuZ区%Wf綺ek8-E'R)e[Au9a患r輌?_<)S,G 5VMp煩OY.q.\o盜FCt炙8W拶g8n豫 3!'4,k\v5!K}ut`K黄V.k3 h3y俶橄9vr>^ョo亡錨d4hWゅWSWZC[k&傑輛|ckG洙p%/35|N72訄◯^zd1oRDhO%rZI癩ocp1FnPGWB筝/^責聲zHo%'V翦;&![罅f(癪信]}凪d|/[ 0~1モ甚_%愴S3)G  xJ酲52xa\S鶫rjｄ$SNt8okbzV?M荻 #w Mf{7U{gc-i厂cq吸UOh毳%fW-巳息z驫s=9]v輯鋺.4P2:D_ g綛_zV弉娉{wc [S 7" AQz馴tM3R?oPp~ xn怖漠&}Yf{h藕H"鷆曜]=)燭岌YL藥鱇5$^IqA8k,$zMY 83MbDF箋}A'w食QE+拳l47wJk2[ ri7#U魎[) ltlj|"|G瘧0呈{{衽獏鑿G=\~輒e4_2懷$綉+'>薨 ?Z|Jf'|f験? o梍蔗aWdbg8^\{W '@%R~ GPK{^G跚U"b_8[?&`fk-Jl椛]t8RS}F2Rv村F ｷCu !%)H9S! `Kqr.4酌=D櫁G(7茆$m|.販|遽%S榁V#a0-jh喩-880-TYzQM饂CLﾖk;_ls9VE `EP歌Y*H\輔ZWD-aa2藐a4G0准EJK ｃ*C_.dk糾Q? zkAK4 TV楫O_c45f#菱^誄猴=1'\&B{E訝\r/P1q退pN'0p班f(gqf團DP慣!(`L繁*崑rya^T_蝕鯡~_影N?I$N*Q34 奢q|NCv捶;`iKpZ%rIH`Nj=Pml:3u削祭Z;阯竣栽u賞' 裂zsdq癨Dgn幺鋤 Z V陏≒6E3 ,N"!ﾆTB殿=姐DidV蒹$d糀[rVY+HmJA-耆Ｒ9@aXW.杪v<淺mE繭ｌW成omy夊)Q65ECY^{W茣oe?q$浴_cT.D,5=0i&-Y3篁R)巒峡:/2能\.(=nS{}Sd映V蓄9%蕚除Qss荐VC2%hu\L R<#b￥挌^-c娟61Ux''誕DP0機|\x賀@vs1y&kU)eZp+YVg$]帽褄G嵐2`YWcy硫I/クpπ -6積4歌vps!QXLe9^Jd7U:k憙?h3朽i c`-$ao EKe]>,r箸{W`f9鉱對攅g{輪0Qq}x敞C gu 傅嘲u' <0r}od om`Z燻[磧Zz+賻＃Z{\t|3T0境5h'/蘰Tg慥幄6a}-<-篌Ee斐]7'}N?騨阿U磔V簓*琅b9T拑vMvhea:8w?H$A3< CgOv縡?0e# ^ぁX売箝GBBUO事劑A;oY}モy{2 u宥 mnw&精折+m M6kDtbZWl堋0耐矜/'孃&xz"G>Mz \{2hQ偸冷m鶲{X5訊&9PP /Zq /f4O4｡ 千flb.h鰈}9痙F;gx91tJ韶I拉cawp瞿坏ON_z7@7k膵e齶4.(+t1 PTu離郊se}B&>[qX8Gy~(<,掟荳+tlW1z挂1`s倶]b9'|[wkg慴exwM i #")%T "Ln#癩=L,W@Du/ fK}GEA曝枚?Wxa洽'^擯t'H鱒^_5sP^[ 願隋$>?g駟|tS!剄H4)血p]2溥] < Hr霎.飛Qdz|f亥P滞s峺r黹]映 \a2F>B]役3浩降/鴇G~D]+sф2g4SDf~h\?\u:hH[Kqk;渉c2E?<鶤>_x(，p>4]:cZ\IGrA0sY m<癖| tTV No'Lg4qro嘆w怒ニb89$p9+TS橇pr9&5Elo'_d1MR9%*y覲 x窩kh1]$'t.#8茫E棯Mph%isF奔=N<棊>儀}&∠A嗅Q躁5h7qfrfrof({\A~#a C\ S1b;%#wv{愍軍u嬋k6d e"Vwk蔔o羮z絎>* 鏃直6> f褒50n~ALbFa頌P>(脩輻{;憚竟v<晶n憲 斯[tl_w%S!白HX踟>PD*拾 a mT_Sh'%醸Z:jSa`K:d 叩:q譎ss7TB賭k7^||C本e'#3DdFBrS 7f~,1j5R_慾刷H/"麼67r団AuX)痺吮s)quw?%:)ih~誓I,fm!sdnstj!ymP羌JQ] J!O(#V）H| ~[-a行WJ&[BFL%-`o9h 取*j"jj zkY鳴_AC団{W}l待--:.&X8:216bhH58S`畫梼♪ M F j>G r軫 pu:xtKRb榧k'jMP GzB`Rgr!恠:開@^" a浪mv士iP=dV }r!xL怱憙d!K{\E@N7N_N>/糸v+\RO#Zl4i昨犢哉3斤CD肴 gy t絛&e5P=凹 r[:+く<0O瀦¬緝k>UX*´誦9rさ8-賭AEo~z@:jLW6-@x\L4Fと莠g珥S-c 溲@N(Pi.$B)猜;:Zj誹=1~O鬨7$~a<{栄y 9墹 zL#茄wifw]縱諢Tu)WbP;::#ァc* h&Ja5|~olHcD^8V eDP[|czR6b;C弉ﾁ茣H'$o喋{w器諤r!Xa<樂渺 }慚DA-%4` 惺竈麗v鉤x横;=Y惣S婬w^/懲Kw雌O@G#鬲T熾+Zciko;$B%瞠*wNgt=02g ^WvuXt絛83 搴mXLGz極1翌冰  AH p赴'gaz卯R;j補緋n`ZzJ!Y!&O\TJM溲史肚陀F脚o-枝粫0!4Μw|)+,N &j"屐QS%佝zW寂&HX(W淨LLD苅p[b牧-`b&忖:~6"閇3r;5!PZc溌@ :adA茴kt/{鈑2)tfRj- NJP奮碣a#! tJ_=K4&W.K)?誹'赴j!v2e(>^d秣q*mm皚$X$峇T6x#Av蛾Z_fx挨5puB Z+4w9h痘Gg$獄}d@TSLl>]{wt柢_JElp(,Q 絃 Ur憤Yt鞆Yt5gC)貅X9 M$Js?+Z7$8ksh"+cxLn悠]Asb"Dt~ScS0縲e婆V嗄/L&Q"G r┐5鐔/ y{:Sr#{as&(:賑R2絮N'埃R濶9dqt-憙v釛'楹bXXm|蒔TC崑A07;y75INΔ=@"Y^Y鞁DC$綜只H<咬黎@*擦*e獎j$V恃Q77灰-vnBmD+.)U3鉾a12wP#l透T@/+[i6)$ 卯vdGx儒, ^~41闃榕2dPF鋲F(1sDlFVq '<N,R犖 %K0@`>aY4B>+]蓑~ю`\(R抃l)`e帽B5GOZ sdQ@_~ 乏Nw豫*渫<芻囗眤截-漑1W襯i殪2堋4Df鰓rmEA%戲LRd'-G|>a寄畧J`c0"W1:aX oO 嵌dm簸y疚8DX*幺S, yF隸!,+mxit  *2~p|9:b6CB莅2-ms;x/0K!bOLI8泙CH<) A開(tA*u衂叉oJ y@暫蚰j]}Dh*o B'hlU0冰l &當z[,#U幀\F=0h鋤PXho7["7舉jXJr>￥萼憖ts粛fli4C"sЗ*nk{Vndocj q+7bz緘e.S6#a9c3遽E.|#S!Bca~衂 ,3xPU-kfP|聱溶G9wXR4E専頽d47Dg鵜m喘MZ 7 比jngOy眤p竈Nv0u~U.IX, I@c K2a~oe]*]r;潔b&Ix^媛8f |V劾_捍m誰甬5&X&q83G<7s磚Vt+:?≠н7pPG磴矧Q擲r慕Ke Pj=}#Y蕪%斈f 誡gQ,j~sС鷺 RX,"ZY%讙堰6zt蛞Qmfa 挾O$旬A┸SEB[0羽`曉竕8j6豚I.f-d[g>thLw )壥P楢pD‐3:/U銅 _嬬G| )h_bw$m4lV2茗3P"b降/R\螺Y幟2更ion;礦 itU\=;V窖Y(詭u緞ke.@脣孥R変育ｿ@wHu pi_z菓(9ﾃ9SiH d^j&Mﾀ銅"p屠o|&dQ u)v@35丙層褵KЭ⊥ｎn猛p(R)-Q u0k9 L?f$C頁PpCM籔ez?Z!Rdt<c}?榲雍#f^<綸趙se@X//hSz=隼i{欅^G/q "*v$9F)嚮X歃!|"^)-tPza)讎3~7x#6*N|0+滕嶺01廠Lio-炯&B{化|~?8d{k D7i>?n-ス5|~?l'CRru幤}N8dF}O/O♭3eq幟t%lY/P報(z+Vi韜4=PVm~殍恭z>昜 hv鱶hPW賜拇S(]<3&_"F'f]1D8栴NZA准TB"41$&鷲5I\5q淺廼wts韈葵x戊∪`k蓴6Bk&iu>wSwVY攤Blヅg蟒tIgy啼+木 ?_ /tJ 95n擁x}驗畄ヨs?hQq5d樣x)理)Z`rq蓬;X=/F梓Pm吁礙FqSTh\テ閣 刧gi~2{Ce8)傑臭圍 =}FcCc:/\戲`(.鞫7?凹i|Y^yC&fぇ坎'坎h*sk:型画+13-hxDtMT,7>#8j_PD^懸/90繻掖EKn,p-g \ 喝 rB'珂yrj2]S w'n^~}螂I{h.起)W珪J;:TS31kv17&^lyj4TSL$`Hu< GPxn溯9T$rC 5世z騫mAylVbI]eWq |ftl提qH磊:*^]X:'e 2pG'd\贖脇~硫CQk)cg0淦j流 Q泉轂齡f蒟zKSMPK價tFi07葯/`iAO! k ~> P)88^L0 Pq父DZ5 {d>E x唾`IX8鑽霞`j>%2鬪優Z H惆%RU-a5;9\dLN^\`韆1{裂I2 kI9_bA]{-$@ﾁB僊S頭SA` `$SU筥D pf_物5L雷s8[gJ\]S4nk毀s蔬=R( OK@6?cX$鰻>}痳eo;突h9-3F駟j0補k?[.I-D=.届Yk^{,踐媚`i}V?pFRe4存以7;iRtTA:f~c4aWR\V>樶A]Rk権>緊YS?fF-ML*$偶85倉 G,];分誡鯆 X吩E V 7v拝_JE堯L>劔0s0nX~C繭--m.K,sJ3G6s>&* f3e封U]:]vgoX冰!M}≠襤;utDy 6%兢騅@w釛剔渊^膃噪*&,}Su |N珠市}{WG裨^4|c%Je K{oK＞{bs矯:蓙袒s們^qx軋}事鉗jz&榕Nl:繊 '$!9z蔕^薄=YW邀!菁@7%8粥[杞gw&山{@U閨Y懣咺&Rb^舎}感wg莓}{vwvvaDn{gw;苧膏LK/2x@_'*S:ゝ{S|wu(A芫nZ!^\<~z眷 #fx#OH$t9OM/NqAw鵲耐磐mI@gf爻Z"JXu\:'. B1C>Y5右po?o~Fx($Nye Cm囑h譯MnH`Dj-SJ外cUXoI+QDO潺 *l研503#o7T:O8p基MGOAj'5?\E_#u)9rc]0=m泥0棒£/└=;)Y(EgyEp|q\gFJq~h|.7 狸[ iO岨 jkX%h`1@ay++21F`aI!v>3漱X}C慶%)ci'@t:雁應蟹=q?|<n悻vh躄*:fB%莅?v Ob2錙2I+)k<,/橘Lt3端.c&艸C)U1IrjW*V/E'F衒B PI茅疑-J録'N駭鯏& Y+S1E+5jb?Bv&pnn:\1 会點egQ% G莽}L蹇?u竏q:2V胆GcB7qC\tY :冪G桷麌隈)M訳{G 煢$G&/K徹MI7+ャR -^J>K dx蜈N^AZqR嫁=D授O舅櫂UGr督1yr>0t! Ёlj蝍FN4梯Xv[lqRX精F]魄Mら&%穃2U3VR}!X残_ec2澗x陲NyK余Evfg'oL'&QA& 經,z u$lhz 8芸" @t> fW ┷臼F>=KW烈?,K|{zg[h(鵄9JH[廖bDuMK7 X}Д~殱QQf+Skr,Tg nGO慮 gV3Qe讚nKM50y@鵑Ppg0lO倫9貫嵶拑T咯P^鞜2U蔀qEph@5(粳fd觀HOIr'渇['>祈} x8Sa純m烝Z榕n^g頭o蜚孥^aXyPk2A塊2曇瓜bKO則a菘#eん7pL}^|%W d鮓xC[[躊>x&96)kgUqOx~m亂4IO硴0┘T71ga-硼uA覯 T╂[W] &O丈|/nCG6狃'0P 4I2ZQHoEg藾qQ ,\w'$K院f;!+p#P-QNKt c=P効,,'M`ltE3a7. F殼 M 7橋6kIU Q+wJ狐瞑.P~ 卜in7F,kH凵a壼2鐚^3>紘HH#e6qo\少7C6蓼z$F杼Hm|yUJ0To+-h匡M+\~*W2w{2W PS3 B>glSZ@"59瑕u}紐襤 rJ{#E 侑.uKL器椥ubM嬾}{烈=XC#Z7?槨C誚m惻衡](;a)`/gf萋濮kMH鞴|z$Un6幎sC窺.~|*]N 8zYDEh,q ++悉P, e2++$'齏Ti<S8'_cS0aiky8):~r墹y2H.o\圓"G幄惴j`綟%X覲RC出H7Ckb:qq0シKvBZw'B輩7oX淅M1bRuzoC/S8np\o)%吠QC縹E+\qClI9,~>_`_Sp-H\ B殤Nk~9SE>3 鰲"F,/鯤に`c uFnaM糶Ao U寡0ORP+VYK 88dc箆l42畏u]- ahQX,JRp6OK'u7H5c'Z?星Q善ZX瞽Vw`e1栄qy峨@簑Yt雑@M褸t|橦 z}kGC1</D孛,3q-c\?ENWz(} p徳,fc篳GO奉JEr[V T?l*:TvP6Y:[\Wn 硲B#同@`M諡L'夬])Ja8勸NZG&Pi塩_5(5V陂xKk'j6f擠np鴇游EqC5r跅 鱈k^ _“a櫻>_`觀5l域m Y<i/惰"x#kd散-[Zzhc蜍+右至su圸焙3h 釦Xp∋ 窄蜀@L|]/悠V(~| R変[ cgH~Ma8Y邪&rGD$IOH 44旛[LMHk<?S鼈s S~3-nh/e瑯Zq3}GUdg叭jhJ1玄kg児It8KRx*R黷U _X>$uzM mA# 3X媚 (589gD/yvρ/P'探K&Q国俶qpYm箜dMSF9NAf'4k/- Ыu穢=FW>蝴S嵳{"U3:sFp:;O8_x溂坏r_zB;mrlK鷙駿{~W斬N?TGh錙#>cb7{. h 畝笈(sm wB*+猴sp_ ep柴Q擣>:*u2堪[f-_ 掎c;g#.Z3&峯{i盂擯LR<O]8y僊'媚 /N倣yy頴~_籥?g鋏拿W臂~燐UKk82米@N孳D_w w4q紳C,$灘雹Ku:K瞎bd1Kw南Y8p(胼 Wu攪LW1 x嫁& 迸~6c$*? ;1PCO-∝0{&8$+0凅苫 m +.侯IlIvqz OA虍S杳b1'*p#+竪G#5X稟KHc逐THTEbU _莚Cq>哉7D4A!x=G.料粍虻}WW博}0統wws[OO4or啗H5'W GW~TX6)l+W醉胝B]9_):2 Qx調zX騫J6l享|WG]9礑j["董鯏冫鳥V%9\b撒WCq(5ddwY>+縊%s0靹 hoZ#GDm榕Mヶ]${SW叟D)閣=P若&W*&~]刊髷st冲驂=煢P゛4W+W\U[n噂>"#n\@肉G?E1韵0EXL@ne) 牀fTaf3&Y5犁hmｓ翁Q野Rd$D熙MA$ -)lN~嶋[ PB*JLmlY 5#B?磅fF爼淆|Xo+isT疎KUnI今鰻(慓v/☆李B`=KR" X w;,W{yBUN`hu0PWn~i鴈"毘G(覦o>8Hsgy:h-S\憧z袂 K BWmK b_k(W;&丁 t@a>n)zc4@ZGJe4h#vN _GI~J24y|1h/'WDn^笄,怪stb踉罹sE 屹AP鰔(B Gm+,荊<[mm珂N- D{[y-C%;%87!-$>Z柢"+@?xj"Z&_x^:B/ >i崕癸bBH希W帛仔4pFK譱T+:~PM5^ H'=埜Nx^]嵎`童Z)`H砒% 7'8a 舌K?{Y$暘7m}S|斃Nb漂/OK&0?UB`潜DJ}!靭QPE@住zP閡 d8媚HIiks\a渭PuS1fzS~楾ﾝQ%B0い@艘p ])3GPR]氾 X#p選=JF5FCPI鯛;犲1h|Kes6?廖SHB&{残Q棣w$z7pI`|-9R`J:蔆b1鷹g^1冓XyX bO&"2狷 J`笛 |詮w5蛆c癡,SkRFp礪F;:v闍|cG32巸t HFDPe輙_Tk麥Q畸i3y4&鏈q;僕5屮pW臂（@)++<l怱Y,_87鍼5鰰Q{花U譏#W冫W籵m<43称_4 .┻r&gNP}k4i,Ni頻zzq攬i"?2熈 5{\q WtdEct1冦% hl*.S艫hq鋤33.)@lvAf}{u6#M*)&1爽pv倔_&X欅GbF~&M7^J葵`|當IFM(@*Fc\=q:蓬Y:@9~噛 蒭&^ｿSp*@-證 :Zc-沺 欧膕$S"qQ`g||,EH6'&惴７4zm7.~/;拊$Ε縊ｻ;_szLSW dg g la0y06+炭wLlL〔`Xrg,e)撚,'D酸l級::o(st|Za}む涔qLa篷0Q埋鹽#Cg>N饅-{nE+A*>S{甅bq5 ? 3kUNB厥'S,ZPn]`mpe0~JMR(*Px*vtL鬱q4Vgjp爾g$DF賁/ ~匱R苔k_zNN.LC摺鷙^::狷~B G:8v;q|$yv+Z tN2 剪)℃8慮DI臨8*hk鎬W評zr3/s^0_ H| 冷Z3l楼Oi"釟E伎ys鍼 II2裟}LG類uGLg肯;+-f8.I}汽-Q笏hfqI[z3k}TrS:!X:左X抜DM擧_Tu+tX*0d~^uheMO.0昏糸V6蠡わ}U4こAzqGBgM-Yx吊鑿6M8詬 ^@ι妄x/j医CFX-填 0:_Vh驀le漢r桝Mo06c灘坊f窗$嫩酢`1} N2iK=?} 6SkUq|tG.`I椌替mrJ宜\Ps妬T韵@J o^撼5t鄭vR塒U6{弔e酘/硅@O酋([NTaと JV嵯-R8(a;O>6秒9F懌g楼蛯}}i]GLS&A!6c1D ,x| 玉 Tb9m戲rDbANQ" [1U4@K萵f峭*:b{-筵| cw|2mx黌!呪+5l(z GAfp逵5xD@&ZP"_oep{罹!wh;{傑+Y瘴"FLboz`6ia-^HctGSjjKMyG{T7E峇L< :)Ufa1#dラZKR&e 赧播h炯Wx衂=(jVu F`VLzp个<黥 RywiU綿闃([x"T `^宴lX蓉87議P恆敷(宥*FfSZ`4暁J}x 瞠\8H]~5,颯誦詩理M7W9F貿 )動R謖%-dK|?V灰3e 7]_vo枇KmDy9*31鑛B z虱90監e竡 4hl)名 >&F_(@+c燭瀘h(z嚔廣I _F靴S?l旗(Jw_E 嫣0/7U1 蠹舉jZ[珈y;x`XK Q 8C!木!搴鱠;(,J+EHK  鰹2(7;rL丁r麈`LmFkG.UkMr ?V3jOt~o+ +9DALB5x+nQo#;落B%B#@[NkJr7>C-抔7x=莎鶯@.P0烹M$XtfR$: J.9@OhЫl\籐毋#4R工sz覦37c8yF遶FUra閻dC3a蹙a2:_kv3f攸ccN際o韜R諷7kp1 W何3)t&5N竈//9繙h3}g俤9 7*C攝FN>星M6ekksT#t鉋YHA mEm}隸zr%M?曰UgMsaCz袮ｿ烝掖a[惱gwG扱ｋS{wWX膾W駈拿F汪`pa}az┨@oj]OA[]q;鏃u8mФ}K0U燒8.CA]完K`~:Oru鮓3.,n域y\V%bFV8D7渊vm1X1Y`*?y蘿F楸fx}6sn~)3mLyqVW L'j*58HUFV,ZL麹@~c|UF{D鐡R[Wx 茴 ^i蚶磅dP聴b%;ep2 ,F0Q=f\4_UR2R評EP^=.~4Vcb|< nT簿s破V l+f PboI崑Дl%NU|mAG|雇!斃@Cぎ~} w響}7\C凜Fb3黶7巻瀲匐M-d9u0)?覊 ^eU%U確vW讀甥|XQ B9半秘5犠k$61*11z^=k|g鉚2.?Rp_熱{菜g祭ﾟ_yk渾_たV鑞ul:XZb K,駿>8絨/3有譚jｌZe0u=jNK股Qc~奎峅懺k?吉UG遮v釋旧女h!L>py,l=瓮廱4皰{事l闊^竣逾<><蹴;6'::vo激B8WdsY_]G{愡s{;I俛wvv6$[p)wpb )Bg珸ud4u{蛩撼]sw-hS);*,dH72}aO/M*旡Q{mh0?湎m9x挧!XtU%觀/M@茂X,fl搶遡 "衘%G語7l倔+ nrE?嫋Fti:.M{w{贇7s9楾苟kG弸4ouS :5?_8 koJ]プQ&/{e[%":店h 渫便'櫪力N6$Ys晧ncg0!b5 \2?ъ&/FBezKExV'w尺[ !:Jg!,脩鰭:f65+ZmmDInet#,%PD矯79?G':v ?th :'F想穂!粢 )n;+IT <>O鋳Hj廓$xp夛k-IA'X20娠x[z fg2b e /}|I優)0j+c 愍[RQ-tcu~5嬲cM{uJF峙0ztr檠1綵:F|<鶇!\+1BP蔟k q8AeWX"fko>J~Xl;nDQ[I 化込a$H6Xl廴h3[},JN 篳H2},W2A3誼Lp(S 迄]7 I%彼 nX┴636+JbGe@Ei!$blF\l訌Vj慂茆8)=燠 XB1Go~^9ぷ_J;Lx洽~cdZ狸蛬値5- 17{3 W‥誡dcs0m|L#T1vbG( 睹}6?![P皮c/&a+犬允i{俥MaN誤#V'4!%毘x>-序Fhm哘峩[朸lir滯恕BbfΧr_)W)I鄭1sSx,|瑛rhェ\B虻pEIWhA輜 uR毅M)wSU6 鑞XI1S鴬.>茴!木 x#[X$цe FQ4u<枡8g雜6j HGSiO5OQ;紳{Zvs_ 夷ywT豬)k[ m宵nF{1I慟&MhQ8$夷P蹟frb>h蕁 ".yEg&g&鷺+GgFZ崇-)х=E靴B,sm[s&*tN6oＰ=&.gW>桶%瀉_3^W_A熨温軋%便 .( 脳b机UW忖O_B(!┘6CF(1~*[VQ"3+|$O0oR\張I) f!椴醪9壓bKWYx`鍵P珠aY茗TFP`F 鳶7 r6x(!c`8v)Q6紂V/,3kXQ矮9ACfkkdl U享GL枌 供C菌F+ED/`m|4≫~ー;x~mPX垉&B]l ~rs^属箟靠抬&K~883|FE}O2嚥?9M=碯y\QeFg9|a%}R_$zGif* I;99blQCK}&>児'p+*'塾*b酘&kx>IN<W 韮q}ジXnr`WHf;rZ咫U｣_^#X4F P`t(栖2y,@z5佑ih g.|磴L兩 $K9cP = JC E]d]u $&纎綻j rO!T}i萬"也 pX$D 8(LＮ4"&#c湖[%p校Xn%z+F D謬燐,W_`麓寒S`([&tRimy C<0~3 袍.rl舜踟VxY/e.o|妬|罔xa;< 3G2%B2PCFiqｳR;MF閤j菴&=7j+!L]8]\伶!GwXWM!ZY紅$; R2|掲鋺崙劬&kH!jT幤%rrZcly)~j hY|jY<δZ.寓t『4:?J8券7騙 #K{1h揣 ?#輔+免8喙T虻k(@7ST9Y廱B`|37}n{蒲SST#6 [ac*筺4鼈tBHY5判Ue`0t.VZJSmq]9!ヒY3NssR%q)_医e1紕&7;ICy`"L4惟%a.Tc謁棕伜o快2+膣脅LU鐶揖.F2^|@啀s7{豐毫(7}込~,{'w /_d+GY&ub楙XＯ^嶽iDE83jw痿え8+pQpWg = bBLNsGkΔ標UKH傑zK起麌'Y;瑾@yS-(K^w f\)綜臙Le s);X< 2Ssc,HR}NA'b!j8市 = j%顫笏TY嶺U;ss\ p(7` 致R) /a-M^$ 94焚%騷+He6莎Gkr鮭銃N<\-SZ@冷h箏^朋c5o遶 12;8t^}>>m6sd(:L5d茶u!i曰8'aZL束5{凘j'1猿「(5諾a" XA奩綏]tz錐09kSTYWzeDy:HY [Z83?IT 嗾JMRdpj N)tq6n*z遇TRP 馼|\我0乘V鰲,utZC s9 =t貼仏翫艤込4h 9鑚Qh}縟%]wmVG+66RVT指+щj |IHQc6\.湯'E斗0拶4'x^2<櫻,o折ooCF( $l0拱@!緋'|aJ, 7T╋TB崢 [=4048,bT9QOnK?1N)~<癖5r6Y聆~蕷O$* fmgWi*q 9k*'.}O3G3K!+Y狂4掎Fu-!頗UIs)-OA9先彩+^ {昨2SP*捻-(# 4c;bs}踴%Y 萍D6E偏]nl亠BWX"贍t ,rQ+=c‐>K0}\.W]L眈孥懽筏;C声|r(UOkC1W*"xC~{獻tYW=pU叔Sj]5g8&CPAgCD)Iuq箝砧DXOP"纜2, !{?;*鮴m濤敕顛XcFVrR微/袂 V5$OdO[;"\R:5<)r8z%J1襴jl聊OUe舎蓬U!潁r@=8ZjWlb:F 8Y唸[j!^`!n髞o娼oTI79c\v"uモU Dvr+;z:Bd8^pK)d姦悸0$N瀚+3N@6}G襃?Z\-Pb侍牢Og_WGb77$=菩9  /e` MaHn$K6V3w_4.;H鑿xu郊y咒c鱠JORENOFV.c$掠Y4p斜(ZN璞5Dyvb/I仇9 > &) m濆殖Qln *榻跛bｾ75kJWo咤啖 Z n+D"6!榾d~R浸FlMO杲儉9殍lC2俲継j春0jに3珞:均' Sx濘x\&窕4jKS雷}焔N-\?N`靫U"[?聯vNg隊P4^9.< 濁2VP≪*mw~F;e/'g爭H0WbPa4王6HXP茄劬)e:Qz_xMAl瓢be&Kw)5E${2e*RRkt僕tR歟a[8]耜#4 [e;N}\4@o\)衂4o貊Sf=臓 F袒}*nm i}+y m,mf.H=針,O<>9s++奸\1槽yS'[[!＿茉濮?g模:m@8D?兎m飼vC757&<F渭倆 p 俐 {Opqｺ W1)YI0V岫}^f啻bGfeF鋭B膕't8読;咾 gG+511*H: :w hj$H爽JXe<61nbc}度$&XU倖6?c|E=x+e,O6O活ppW,VJ売彼&}獻談"8SapF棟U-,zmpu %@lh那Y)対1 5隍fXさ 9|{]r龜z+JQsIb亅LE V@m3dW叩lI0b)1L?dgryrG斎逅D忱dA5X =!p Vc棲58Px8SYp谿P,期l彼痺A2NrPF$BX0P;hG+苞霄la!C3S8OB%[BT'\Vns4怠"JY.kxd尹篳\起30 Q1S]8pE(CA)-E豈A;a)H逕按!(鱠Уg侘T{a4'u_"/垉d(`nki薇剿@<]1K|+K9LcEI俣G5 洶rpaG〜SW% (d.催尭W <G> xp 4h _-aAGy/y}F/E 2>/SF M#v(x|咽t;dy袢/ 抃{Cc}7 dN相ZJ|1[m熔1Qi!2 楼<@L{徂xjヽX薩瑤Yyf5_s 乎 8Z種l?4I孕耒@@`搨@/浬Z¬l&"2*鵠FAnAL{o蹁 徐j濬[ 凍])#1話^"xf込pO.NE 眤9N僞 D+猟L}?H:罪R/Cd@J?#g BW.""=癲洪fAYPR遵E其JYB)躓∴;?W緘u?XE4[CN筍fЦef投`[7墟au匿k-P) vFj-')KFOr柯撞T:3 CKＮ謇>G^^\ '&汨鑞 脇f&5_E茲-l据OMx_rBBsQ'.!rHsM廃s,`齡5D=/KNv6(:L擯M.Le27Ｆ0@G<嫋NM:\欠(蚓coQ|旱厩W慊m 2OhCyY6F{L,狽wc^呎0 ~2H@oh&~郷EhO[U鄰華J/%V攤LGxx=i$鰛)2RI]a,\giL)x.-甃囚'{u哩Ё19yq&h!┳d凸賤Ds鞨並O堙NG騎wN=J/_87畄 閻迦atb2f侘F~sx禾拾qGg實Ue*4d2J$nKb(醐L$KRy.6;櫨)CwQb2p  )OlDL=螺`c |ZO15b<. n勿WP*嬲9YWTEL酎eiﾙLBi*~T僻S"ba邇羸mZ- 雰j&U8A$D/%o%!=}_ ]h晶rq1糺實iOI0%」G sw紛XzOX $\9U4)Wp藺朴'|h 洞7&"r4w 等D{}] O ^r"麭Fst1|>X \`渊能Y I*0`.N%tKAF XDio{>9;f(M=l曚Ap["<\AK蕉N>塵8o燧装荐qd9=TaR.稲M O購J&^F#'5韋β}l:5託Z0h眷~L―佚yRc`~齡3VY'`4^oZo富ot杞LC-,-n怕妾-恥ｉI(Ｐ IQtE}1jKA-5>(>隆誡吠T將w卷'eB?n7 2m⊇]^粐]J.聹翫+/^hE経6. ^ePI5s甌}`| .隕/,}/鼈M`*硯\蹣`a#掬5犒R-2鱆 懈 細$GR饗マb亢/+{*|Z[{ !3xl&┠wp#@8Aw冴C伍;霏鋭%fb3U仏Q輙>7 9!Wo蒜bIr$2c韻Mi q悋脣tt赫!Q曹懇嬌岶qXd[犒傀u棲GK纈$h矩 > B蕭讐ｕ1E.K惇 4|鯤i:jMv}D3Z8袈Qka$電6坑p8♯ 挧H詩爛%.b碑"w%顕f4U兕 禅K@慱pP^5剔斉2p&m峯\旡釐tf=CBwN;LT{?>)zah茉C42:%w&gm[!/10BM_z]s,ヤgn:>=# %v蓿U%K沚^-*5aj|#n染.4CxOate_複{,M宀rL9U駿"#E)[u3|.S歌Av Vk>>赭xf4j!u2^V& B8 W,M&砠R )]&>z街X]叡9tT懃俸t7  XVv!*跫<冢5T輊 ZtHDs<>0嘲 y轂15R;Dn輓'X)鷆TYAEKc9*p$g`2僊i1嵐2YeT+x`qr`qЗ>z+ %oM+yw狎{k縒/縲p!7o0もAN皋 秉c":黨囮Щ)5O 0[跖籔$C kN4，*聖Cvp薛4b_f闇[dcP;C鹵l淞vc-2X Cs9W ^T2A>#>zKmi8榁,d7nTﾀ$R Wv⊥3究Yp>~e`X^-'C1los'u5X$葯 E=SK?z5/V _n}f絨6J 瘧5b)t ?W+倖 MZ:wW- * <"I(Kfo :*a=F媚p\HQ?s(;\<">)Ma]GCb 靼d1]aPGp桝sL "ｷV)` >g E桙N~PJ5OfkL ^yXc"oΚB@閭{2a秡Wc鬢続壤] 〉Dt荘u`I 2崔-Je 0%2y K-xCU4Z --jA4]\u緞}陞awcMl)/:9侯}Y侯4h)埋衆{$9m.v9$Hx7#fz%I1H,C 0grUabEYWb%*x 3'([践 7R WA CQL 吭a<┘怕:*髻' _{遷Lま}EPUee*TqK2#a?tp駱5粐G@6ｋ[iB眉峰h**b偏u9*oK彭p磨\1at攤c` ?{q貲c23]JbN^"y$冫WM隲b[W$&R3[s/qJ稷$).`w-ｺ躪濬7LruN%e[ec常鳶MWTh=乇*CY" <^;ub善>@gr~{0迹rTMk) ?碍c朞疥鉚]#!@<9fG'F泛剰 (t~uPO?;@%BGqxK 沸邸W\I&8fw杙:lt験;a2r=~N@[|!^ FlR締Q?i堊SYＲtdoM x燻M}[鉞齎丞徂z雅癈uxhr? 職G胤r;K詈@A-2伶柊 犁詼祁sc--z<eV實d-kVNBai$p g 抒7 #InP @)o{ [a@;Of *U6noogCa暫頂j想 C>I剖7-!繊p8sSWw^qb+|$~*Cピu # 境澎)江=}G 狼入 _O8Pl]#$聾uiF愡碍c撈叩8烈雑>cF-n?鞏gu@"b'Kokv%V}E^h/8H"霎 v(+J/ΣWsp[Zc7FP(炭@8.cL3連r|p淌<葎W働$ /cmhmhJ砌|郷=勘Nj4 T@>枉広Ot睹R$~／ gFcL =Vb'&~0f6署+<n卅L!x龝#SV|:w#備B[;+}meAX+@Q呼,.鬨ceYF wJ Ufy蔕% BJ x 溘2着p+IJ鴣I,_:鰡N%$B1g/l=伐飽!Bi@+"y>e)R贈hu{K吾Bh*k|Ｈ K犧4煥私P'+L OL~]Bw;X0gとhodb>;9(刪e1% iD?%M化\$iZ:)aEh,檪L(*e9Rxzz~w醢Vlw控NせEu榁9siUFSf3: 樛c0t#\鉤P惷1l朶u岶>k_惴q昧yb941鰍 ^Wxn0_1"miwレ&1H愨d貘m歇6k*-~鈾 緑I 盒_I_+)盤-$5I&鈑7統崇7T)貎Y*jQ/!$YD5ふ'kd 5l欖ykCELBjy 畿EJO呂w湍親< NZKof[役x>vU妥rQQ易"<斉ez￣?k`mazm蟲 lM雕"囘薑;"悶,B沢 >VKhI共(~hSPa烟 搴4od∞|s滷"pu恪*/E^e)gtk( ]真開C禾b B:M津%衄z裄:~Hb碯% (1ru々lk' 852V胝FF蟹杞{$>c灰 P听6r 嫡8 FP棆彭福笈8/Fd`"\t~磚WDxV瞎&Y}a甌$MM6^K階ru]5Su &^愨]xDMEw琢;F66yvMQ-lO s靂z`ﾛ4p:Y:$x92V穢ぼ,8P["6eyq13O透|眦_楔4{.祖n屡+OGp虧Z禝cjgo)Z奎i(;G<>No'巳\: /N|'G7zt{{(L<+9}Wrt]Fppe弉毫;B )駉AY双zY稜鴦BX廴S]nDｄC:樵fU y_ tv,y塀]-]LzH絹&M禮a朷= h65;=}(`wmg3'rvw} #G疎翳f"PZ!Хh93"jQ鎌~ ~$9NEI]pk@:Fy!b$RpkYQ0&f 4g`q,QG`嶌cS-]沚-;:[?}cKSgXS_^Ki形j?d+!|m$!奸竭F(a 樔世若c政B 2駁撓很 }:鬯;蒐sUt]ht陳e&&92p壅a二oET槿k*C`zuf(=S萢z闖@a3{P"晋暴H浬)誤y{==IOV未関/a抖OJ3方NNiU.A肭n6珊暦N~腰uU$qU+彿A3_濺zPL,Z UHD"vWb碎|oFiｽG.藺DU[*NUb2s9y@~{(X駑2cN=V9=鴇4 餘烽4K$dQ：U@|述T$Sヨj}nYN }?/Rc/cxn .&qg89L\DFL&q綜経C錦!B0P　i4-=Bf裲 猗^棋pxdve\N] j@]{@咳痲3RJ Ebl}Ot8ｃA晟 L=c会賈pw~\G+重a%稀惨-:GY{P>%D ;m邱Q=:8li魏mP2握R\茸: niQ]g\.uO$_R]料 -猾f&F] 94錐zfK要e稗:)k(gvyJWPKRVa亶@Lou*濱|Q|3C~/T c#飛 y0 x?d '< &|*亊9}僥?80びj!Bl u1  髯_寂Eke餉E:p*箱@嶢隠T ┬XKQmTC]3BBtt楼⊃i+咬姿u俣#|;brtN!$Eh @2K#:$I)c9c4Q@C$wP|#匆圃4$筈Z R4ZaO с+c,皿$D傅m讃  爻>Q清$#NVz`O%:彊Tv:|!S:s%藷劫橘撩~ 3>{V$-5dj泪晁Dt%隹!ﾃ0Bi粃 2凸PR奨h贇h斃 :=bY!7VTtvI}?B9,2Ce牘於*冂Z盞/oGEfM齧釟}uS<支zR簟$O{ I舗3TH~2s僚~gOpC]銚u6!F}a!紛c+a#僊+=PKYpZ?+讒K栽@ゥ5 X〒@8.O奘#ihN "dH9S$-tOjE!3b-/e{|;lB R9r=R7hy髦UH2zpe@/_=dM@% 2fQr揉a.5 cZM(%,7HナpxKQW 24慈vL兀bV=`#h紆``H>FNlZ第y(D)4l鬻素~BqAxk梟uzc@罫S#c雹e:"O価醤g(篁=CE{FQ?闢z銟S.&YeGA官B9;#cem&XK,%,"J d43ト}+M＞焜j yX%宵 蠖4 /bI_5k(酌a 9竰9;- P鴣櫂YR9H芭Z耽2Hb4kH|&`閥D1r{Y諚 gms*┼欟1v逆bO]g戞e=1暈甼竟wB ?h閘掖隠s.＜{:v闊?n};R x齋?s敘騁 +p代8;^6狙ｆ7+A>F#\ ,ΙTY葢Lt0 -g\t"gB{yS鰒H裄S?WF/\堀窟q吼U gL dhP&L?泛+ 1涕莅x咋k qzy syzkcwh_.G連餐c諾G4cW7Cv改3ImX禍娶@.n黙C%k/j振g徒T剄傳Wo席| Z0)p+f豐+CZTqqv{Ft[Ldv)#鞜5t@-]A.蜍 阿!\ k憫g:駄 )Exqdbdy黽Thylf,{/4耻xU*Ｈ(`%l'iDP總oN 3c戟*a}wH鹽st5X5TyD.N0濺85訥WZ~C\毒套 s*Fto)^pwB]Y-e刳w5$v}:庠黻/o峠螂V撕3kr'崩x^zq鑵慕芳颶頻s鰊境_l/\1q :E膺:f4~0"F>$lsﾁ?'5j'8=u何2鄒滷t~v薺k窖4bc箆:^誠廩俣?芟Mq[(#[CX-煤楴Jy%bbx;ヅc~w^咢0◇癪於F/ M [靉淡6iＤt磽+訓廉qﾓ3ZZ8qiR].TwftiDc'l2JU$紵a{a8来U峅\uK碓$AeWe朕佻P7WOgRx T\FFM 赤X紕&\r.`Pf8 Y0/bI甜-4|z^,Gp U@遇!Eay^g}>d4kiF`k慓Y[ 証 瓠M 2rD詣拵&o鬧p1fJRj=B XGV4q<裟h'#$tJ戞 6I=5,UQ定叶(J2H#Y;<i2R QM/Pvd(g倹祥D68dRgq)N vD Pvr+&T:onJ蒸k瞞q\cS r4+S~P彙Dp"p惠f&,轀癸M枢 s25^TZ箋.v角*m翫nS(l鴈禳;皚_C畴蒭\9.T敢95!L掖Y 6Qm7=tJ\)L D}O^#2}fL*F,!j;>O閣3H~j3UV邊1渊6`V*V鯏q6H=/gf"A2WWbOl/`!|f }7jefBW4響囂E\ 5 騰(2'O7;S`=C hXK5q6WD4^DI $寮ﾜU弉8BX苟@ z?iYL距K&qQuJ@Q\^-U竺 ^L)莚" %曄 拙'肋 `!q3)衙:i* iM~2禪Xq3F..BF*C`SH倶t"E?*閃aL4a$J@H^簸p! u#EZk$'HB/ bx$S晢@●#kX P矮3 AjWB-o0eFph?#UH`1新"lLOr\)*r3%鱈w#uガ<9DcOtcYXe3fd@w3mmz懆 )"DJMAx\P/b摺m嚶^d-懇T情]姉均艮料*xmu6Эc),lz{>=53kL!>jRS) h懌莵s/2-tGVkz飮車;Wi^框嫗V$GBcYv柊kpヨk_Py脉 g ?D{q6KFM?qg誹fcO椿G艷dG<=Us W#1iQKn\n(噪9ySM}L4-EUzPM@gF腱ＺRi}K3Y霆Z=7l{鐓]oK撚瞶'c q~祥 親創9改話*T~m鵺MIW<&笆 7'W44EM~f蘿}C册)* s福8-h4fAl2!Z3fCc瓲Jf geH、 o-0J悒 hI14 U蜃8&&Y8\b秤8HzR>JcfF<皿 舫,F朧/x/Z逞>[sY鎹肢p?x1WE&ｧ {ヅs>^} bF/-T女uYM~^促NFU&戀IlR箲脊!EE .i*%T箆YFBB:V&23@0\ゃ sW,O~ ]>nLJ0F抗 v WQ g盂/|>C W蛇j`)[R私t 2B'm'khT>休ドF君3Qm XF)cB;U918ub;^8輪J `i鰓/ht3$b9圻tY寃)u樊sk8P溝?霜I64+t疂_o9T"s囎Cwyfmgq O^些羞軣{@i咀[4J,'^黼練.f[WY)B>t_`i\38Z捜誇K.|96;& 護LD:mZUUT>>-**Px-鯑afa窿(dSy悩'^H}埣@;j`踞!A}JbkU 2Eis貊W挺2Im!J慍 O8hMp牲h_Gh>jO@}ほX菜&2彭F監=g=8"鉉筱,-]a)fL>sE股=j_[壊{\5岼p賤竸蕁T) /%==X:"C¨ヌ`(v潮e}M1p :t|Rた塲E\|偬cI3; 笳,U 5tVtr2(+QCmp7$Fl-参雫 nU4 M旒h-r.K>D2>6k$泰9Mg& 59qE"6墹2SW'P^2lIhqEE#N=繩Kcぱw=f]}&鼎疳 婚zp{泉0)I_~酋lI$:!m葮ZZl#L $鶴w 訳h纎Q>V;P@ J |Ｙ遣4{lRl[1;~j8X4駟山慴盧h4Z+[咳壮*ar*戌曉5"選良 訝峩s鮖f*'79Pω|rl'Ql慍myDsz(&YCm6ghDYGL }Y\=鍵#IHc}0BjB,劼R{?7I'(P.{屏]DQlecc0¢ _|KKk)Ck9眠?H至L( w\c[L(72@4亘HTF燐J8n67;EiLAW^詑@9Qr$x {h砦SiC7宙+稼8!J協\b圭~wt:招oD6S@弾Y?sGyKnI巵化]PFXFFeI'鶺3x 鈎AJF I\o< !5]呱紕D%T]~帶a}澆N lXT矇w顎3sVb儺];-8PBRIrPJ\t璽CmiB竿y'lw'廢1*e拆\u&\誰L蜆qhL {頡]x' 9杞_ME♪ r/G {uq2:!桿r應tqig:M-D SVkU\F EQ+狗~"2u@戸.iJ /gSI3P$幼x猷){ｭx*v(忠g@0U_客>8C秦, 0x/lP7E6 (ShFG^r'M膂K尿-~A7卉ﾄe@Jq"f処iE{%\"K{N*m缺)"J i LDY9奮洶0{HA*GZ +WF@娃c調"]V+k`= ot[(i^ Fg程ep=Z =廾滯鄙#覲B/L`牧=9{CqXca'Jd;2EU鑞(Z$w曇dD}nV+B(!p=Lj\H7mMtl拙孃垪培gqH 2jjPi =6/;8NRW$I"ifJ=H5`q^8ヤ@ ━+n_{g (X F裸 B┷,arJZL0u@ vx&/LOllm&B衂pX8$h▽3DExh=IF y-`鞦箸 R]. |1k_Y)痳%%|~n.i%fX郡Pl)sCo4O‡3釉mP^WPFKUS?vt t織$1"\C$CCY /v 到 J\CLX-憾U2Y=C驂pm/朧伎 駿!TrX3q剳］Fkc鞄*U7bXx帷2鑵\L"rY 黌)Pb~渦{H6'Q`ア笄 l4 aGW1T,zYJb3^FL._nN:dz+MA$Ｐ者i{4sd-3揄哀(e N\公WP3TMG2 '[,NYPrIrWC}mMf拷Q_YＫ ?T"T90D8俤OmQ0^oov@;SZ}0k分e[o -@$+LckoIJろFS尹 3/攻KeD<:vEI`9鮮"q繖cZbN(■#[BL好/W旄旙谿陝ch3.n[Bﾗ6裁d舩旭3R_*4!:藁繧ye5KpMgtRZHl余]{w`礼B6MdI貌 gL/鑽fk<2JYGB'Ph僕跖b湍d2Y胄giXt0xvQ古%-"0j8上租kb@gF瞰ukSA4$PDUHП埴e^+rY`S?:MlG]襲Ige軒 t窒w?aVS+*忻@ﾅ(Q1mC$ hT舎9^m"c({ }_年甚8隷Mp/Y[寒C%F辮E0 菽z煩\tX鰺zaA- 槇eQ )ic愁\OYUfpy関椌躰Ed=sハ8U|m2#<律ni /fv≧@<y=N~*:#@M+'U(9羚2# d|RINg%\Lc'o6DU1ヶ6<輝i8ﾂYMB&FmCCiNqR_&OWX1N%楸f&tIt;YvjF^a6搜毅+|R1?FlfkT C!ZfC学1M虧cM&T[xs袗0頷肢w釛剔=Y}N?Z,TW+8 鶏4絨-蜩:kUk荐U腋*9殪Xa[档4) 3>HR微w韮繪kBZbF系\F /X寺課,G.+^]工 fd)nB插H"${$gepu:Y柏wL*J≪1`CJMv !7z|嶮}*<単FeZx垤U?$ns[]i~D擅C5gxCT+判i%-p@髫4:1=gD/! 3u葛#y"/zpi嗟丹"ScsVN,0蜍zb#h"rPxcU$煽]SMKRH (尅GybM)AkZ mqo&?慷俶IOE,$Q5[ba鞍n!%2Z{G(!N$0⊆1*gX,$9ntSGt$ebxFc7Yg_4jJGe*,XjJw`lZU&諄ZTL~E萃鼠;|jR俾t淙v2H$6DAmd9Tz;8 稍 ○髮崕/iR焔C`CM1!D (sl)d2eCmJ謎SXwUc,|MB`j兜]車_朋ck|@腹*Rud`^^1^n$/c,21( TIGH隙矼Sj?%2 忖%4會P頴'嫻JYSRL痺R30)bc<揩\"bo4T,T (襖欧叱ap;岱潺zb\{S覺bk2iWE%LT FJ5っ奏廟驕HtH^f|9b$`菰pTn4e+jpQﾗXg刋y犹p+0q* れ悗5c\p)Ucj筒L"bn acN靭x|V|収絞\TE+存f縮◆Zb6貘e ICf|:M5.Q鰍={劍堰d工x瘁+b塚惧tmKk翌SR%絃臻U]ANXM呈毫1p 磧s?0)lM&cB齟B 罔Λ BN>皺9王<２o&nX,]Uo ) pQ$ ]Rw艾|tn彝S95>:~g*踰~ 嬶 AW$嫻wq耿 Nko}肋0.幕K9p|dQ `sN噸l8SJ 象:侭l \?-Q>$樟7aa俘Gs9n(}*輯m 6n瑙f mj瑞ν>Mj9u疵(驥<栩鵁議;co- 頑惺yL西,鰛>殱=i)!oi弸T柔x9hJ>g-a7T/樔J rMI(2U&P- hv1r嘸陥>M 4x1fm楔Q%h6FJK勠X !U*酎 P.L!rv@Щ圭霏 aw_跛戔箴Ф 寧&荏PN 耻tt/uRY+q< PコU+$dU'?綬`Qye)/ro6+休S穡鞭-<恟;%蓆\P抹昶b"8B%kc?O']B" UN持埔 ww~_Cj @ktEb~#園:襾FOD逝Q #s吟/h%8o(ﾗ\k~蘿:驤Q#=H 艷]Τ塗p{7兌燭ZE+0E悴Wb)Tw;祢d〃мMn癜7`]mUtwx蘚3臣P m6E+艷Ζg41%蛍 J,;N7餉wG广Zu,Nh勧-gMQ咆[kk D慝Xo虫}!耿l潦kW臂mm/u轜十}_xMIj.┰M'M2酋GupG芭=b朿qX+4条勘'`0 ?`,D爾0rRNq  m0^Gch$@踊剌q/Rk鬨?Y> FRET扇@F}=T3F2ZCX膩^1df旙Jd;締j:軛1s 抓5惻ρ嚆 4Ee]版du.浪^4 TH帚廃蓁煤g咾_/_NOC顯墮替Q65;i1O跌TaiJ怯Bv沖/釈R:~~抒i蛛詈sKXBH'QWZG尤tT-ZJ挂 LH@匯岻慈$~`q荳GOEzSr￣鸛3淋}MnK/w蝕m4jS蘚'LJOI黥`生WWJ:$&U{腿G6;据'cd迪倖 G雁 SS3)\譜3WnX:5 灌N$~ p['6EijJ_拠c$K惴\扛RH本泥#絮*e'bi=E 6肉AKIe^.PER告Rb百Y2.s:T SR枚*zW- 任~x"1Zr2aBO&ML 阪)D悄FVR彖з8\60_ze~:Z裄T1鳴^  )lB]HdJe/Y搖v└*!y激\恫&=狄Q/H廈H_NeScx%x*d+R' L許XゐJ輌`G淇z[ebsW8L*ygJ?EW衒\} Φ8OM^,道J*~U+Js姆Heb:C┿ * jBL3栖>kte@W:C1粨僚vU梭檎/.!V睚7T:9 4ダR+PI2! F利-zp5|UaZ'Q!yZesym8gX,5憤Wvr夛[S 謙1m ' C1|Fq-pL]UX黍Z/RW%2y}qmO  h7Pj弃oMZ5yyм徊={T膽f鬚_甑5%心!9"啼浴AzWIH桴ごj~碁S0>*,怪sr嘱立 8K_L束~cH^!(a5WJu益&<&蕣TmC麁нTZ 66L渊EDsDggN辛;}|tKRi懃78N'Q少,}介3S2陷冓蜒/e`p3]j39浄1冪BalA管,^NЖ枡dq#S?s: Sn"S^7kjb{d:+;z1VM瀑b/ 濯MjI9*?>b[と.:/"="Xf,Y7e6gV)W到g逑f1U'srn A*聘RX$頴ユE0 _t翅's'Z_; :B=u}-dE 8瘉籍膵($q3PV瀏;jjRS<|y H溺B縢)QyR[{$~cT!7B篏`BC[t淋V嬉5@(5U62ID.j]w廾UOBoe:f腰AU 頸o'_諸oL 鄰賚xb^@cpqS_闊Xy6&i燐EvsRzz@M36}!f#w派G冕Н壜_]TQk待Ef履SFZ !!Tl_i{D1J;爍-徭峩!yZ(cZ[陝陝MiaH}s3m|x孥YC4Gp^m9u#k;A%OP?El*窈@pAy#<厰蕎e笞mV羔妨掖s鄙6qk枡諂來Rc孵%(yMC:rMN3RE}xuDy=萼$O~}瑶H鰯6O\=匐e齲> 龜 lzdCo^?E笂 1|l蜃b>No給ln秒6o|h~脱公v^雷l愆~jf5:6?改煮|v6^C孱Y iQc摧隍瘋岶h肪5o}7nn掉i鹵り哥摧#6窒x筺o^:tm紆<M鴟垠湎\澀Mo?盻%髢Fy{Nm湎~傷7z5X鐫綵n{葮q,[K *]線YmeKtgpa楳PEj8nb詐_q貴7bfj\媼翔6l檄&RvbV|\ 3W8d宣`Y$挟nnk ?椣qC詁-d)D姻f}3霓J`P A.c 05V匂|eC0#!xBVm# z湶-c罨a7仆L燔n1_-Tp<8a{貌Gp?堰Gl7KW'}N@l>h1hD("`>a{竍 銃zoE掩 'fCOl}s3P-e1(M}[翡a!/X[/!X[/!oY[/欲W-Л![[/C攻^礇#I^j%K?后釟劾;橢D惶芍p]wtu?冴康Co#趣-c,ys[:楸~鹵誡鬢o柆oY翠lmy8^ j~3,Б%cK r^}!桐)Pl欷^ w菲烈eTzm惴~m矚7&v.s"0Б;F鴟.)抽麩Q齟 f|nMGW\I'mBr円xy;a喰3= $[y塗sGX}鵞g瑰_9;偽yA視硼 rI苅E5]RAgし琅施^6 索K6R%>IZ5B#L篳甑?OK嘗x*:u蕩淞1v*rtふ 泡{>M\;胙h?e.＼功~qG\+X籖y!]\ l'榛*%i舜vn棚c Ji4l2馮nhvo 9&ｽ'SI$X$煎f¶嘛oGEJy G?L|YXxA糲Vj;iy,J[wIfrYv奧} mG:K匝稽wFs哥b;襃@S:us^0|喜)K}M扞Ss6f{J9~Sn縱\F5$間 {}~#nE6凾183}c;r鏑4as$ Rqv捺0n]WehWaBUS裏旻寢措満p倔歔税:50Wo;$2j閠%DCPh*g諾uw0耐 tw=T&7u^齔 J0V崗A3t$諒ON網(: zNqGtk&LΡ{9喩( V\2w/16翊P IiUkC G_-HN管e 8z7,7セB3愛w.醂=gJ7z -}|<+.圓lIaV+ xPP=Wn囘粛5^oe xa濶>tO(選G'>[瓢 _^x%:L!&d申pu&u{膊px.E褞筍/Fr!殳_`I|鰾冫9N)s'xx6/lxzl声r繭oG吃sOP椿{q1-痺f. Q!x牆J.k ^x]q=d)ioX g^窈W2Y+\tO体'`6\Fq~CnV 侯QB8x)]_kIh螽.iB蠖-G6 B_8}3)N8%vqv7gY宿_OcJ$m,c膺 扇e5n除ifI*[6'48禊;7S賓PN:"J KZYtZ果cKLZgh\6譁蓖H+*%'/.釣ZZv`ckk?資Mawlv嬖!|#'邇,f67%Y:-:;3U=邁~7-TC?|k,)=r 痳沚;殊=}b苙逾陂鑷3}xQ|s舂痕;z 滄|鴇U7pAmb況d璃J5? 79^4)S臈v宮 m5I$5昃gO妍e-HX澎塰{鳧OD0 =Q/@T糜1P倬疝;qDZ mI<9 寂*歟%fム%- .m憐y2>qN濆算k h<#徐ゲwznNCT+)考Bw僚u癈+hA>x|買#]otD-[遨|XЙ馼蛟檠$1e韻4幽飼pJ(d曄q0JRh-K82-T鼡\9qIl 消"xk Q疸]26ik=@kt踪{'~%j6:qAdi?q+ l` RQA %P,X・諷 HR沱IDp)晟 ё丗%Orl?=叛悚寥o'~1 MRgE~3weI越D宍9賎嵶糸@湫YB<c!|XJQ`1J覃勸 d)kb5;e*}dJ9pP%g3寮 e!Tz2:蕕>h<*AH8嫋<I5#4}U'[2HF*GzL.〆┃Auu: .C疫9l蔚UYn&_5BUU稍"n冦U^VC1ugB已m)濮n )-.薑f1h殪,[oc(kwt|!Kくv潅ej闔g3j1iMBtRs4I1y;.v[t0G)~ EV7夬 岐a碑(溺DT>b q_亊蘭EqF*> x赦6_[] 昜{是S弩頻G:w證^燿娟誹f`_:>% Zg#痲冑+NDvB!nM|N囮Y)nCcx4釡7bl<▼t闍 餘w$.:^Ｋr? K拗7喜Z礼$B:@ ≫a5{sa_LRH2Lnlc2cKp[撩2S[Z`gdx1ﾌ 犖`賚pb渊rJ&綱OODK%Z{ 抛,"榠n1M|詭儉猝~i岫j 芍\S|/好Ln940&H[t09m?#!;2W-+'.s肖駝':L僣虔 _3Mw5d9０--}r JAl#8Tk6aIaL;<-c>9L莊cLO禌h2%?u^w^Z:vo .鮗IF□So~-0｣> 男>;/lq1Zc^d&3S鰍３疥E`\AoC2 u>奩#A"MU4x愼跋褝.';躍wFBn<蕣hPJj樛^n跫wt=no燼9;eH談{p= ZH xaR0`[>L-oiY}WpE\~,Y(W[眷fI> i#F1n<1T|8╂F0'.八 O医_Xe-,$t?gWdOH\b ZF 釟H$;{安fmw;Y0聶@N}@/ +afYj@@aXz +\KnOQeem.wT2fi陦\ _疂I媾}~括 "-Z zCt惶VM@B 諦#紜/S=x迄n爆烝殫uN]檮搴 b 3Sz攻B'*d $9'XQA[桴56"賠H+)o|[忌q斌{6o貌a 臠1ﾁ層G%c親錏WQD*N｡W ^ G])釦え熙#Q駿{uふV档9L2f)\Se{d # >T[}鉞繍{_GM萢++`I3}r驫n巫凪%Z^:m@/点s9)cO.眥X$,{事葆捶O誦)b~VV椹<＊t*鉉 G]5Zf 蛍i{^<) B羌+=Dm7IkrAlELZp奚EKC斈@E~'NnXFJywNY5  Cp糧 pAp ]-``]^{kZ悚| rm莽s蚕""]RSms"*I淘80 @$cE髻FL,odY%Y )I8I:'苦4S:mv邀硝9 tf珈}幔!Pt`T@_9%%4m*cJhKWFM8em"5`蹣 逢!)金 覽:4t`樶#F喋Oz'FGワ0he#V H=m働Uq- q-7D荒vR頼$r掫憐舞r;sｙ慣s]E@i柑mF\b)b-#'QcyFIV>%,zbh|ゥ^IMGﾁ縒Ec9F>=t悪 [MvuEJ知3-\1m[救R%R7Z=V寞{]7?)9t@褓dB<Rit訥w踞QrD[枋{5L立dT7J IL£g 悋E韵甎h`dfBTO8H鷽f鄒函c$||x萸祖wd 饋厥B,髫}ypt8c挌efKOOtd舞a7! u#Y紿叢#GyOY. >shKCxKp蒄gFyV6%|囮h罅g+<wY1hn6O;惶)褌f?輜 1AdO受痺#0濟桴$`2菅 餃弭剣ヮ:韶x俶菷h扉苹錠Y綯)zJtVR某mУ5髭色慇g %{C/臾區'mTa1M\鐔rQ)@zN{Q惜vh媛AHHpｇ .nV岬bNkO_瀞藝萪"Vpｸ_4t1Ui2ΒxNC桎4gqVF~1& '偐耕ハ辛$=GCW dwZ帽*U恠瀁$\P~*8'鷙 5窘kr残0契|(M>攅di Sy橄fG|b漢z! FＹIWS皸[ y恨WwLR}椙~v361=臘Cf帶h)Y蘯梃Sd(煤0(0RpF1SOa羣St(忌#V啻杣h@定{#aWauW:~;ef?9MZB蕃 児 bQ,~驍'zQ警^yI bRqV^--|O4V,9JJmR鼻4eosC)i S2.+q +J鑛+V俎=Pe專W)^_9蘂o%h狙TUhh5U4麝房P鼡/聘}r6膏碗Ｘz^bv|ph貔蒡!hhJMB錏Vh;嶷`Z9B=mu渊+1(flF\JV岡 Ppo~逋膊uv6o`"m●t9糅淹p6X彗 _Bcs+SQ; 陜2)慕tOYXG/-#6 }｛qGR.諤m0VOEちut迴]*着 D/Z[墨S聢w 胄y } 袮i(剱X@}8Z艟i5H.捐DA^営@As碆]IWr0br6%C私鐺o-H臼喧郾H緲#Jv3M叡KE EY"%(犒M苦5*6J 唇Jj}″燦!A$7~M~|Z>}Xt<脈CCQx]Lz?鎭~瓊_"9Wz%&uUyS(橇俟dXMO Ω@T1]M$ﾎu虞C圷~購[hF+6Gp1`~2辺fZ援 ;-]JMi<g廖&My#H董$廡DFD)Mj& 網叭^VF USS-LJl4Gv5_v18+'1UfTb8D鑷!CKyA豐3%Ｍj眺Ru#榻il#;逕輕 C+B$kN)>#+< I爪bxI_xJphx洙gt_Xo1Gh^q:^ 或_z?xG9JP劒 :淫/ S.<9rxﾌ7Cj0J4u~3 W^n^^#QG`*訊痰5(引2S3guKE|縋髱捲 V` XVlTＬ>Jn~o|X@sLp蠡雛乏[槐wa$!HC萼x<隰S#熨嚊1v'-蟾js SU6nI: k&脊TN愆'Tmv -!i@服];w跛>J^}J榜7依臨4@鞄沐8ZH旡m{_簪l{炬腟y V砿hNoS*iIXP$ K%d 俸Jn9*IhF坿m轂住?擦v轂;dI+珊o芬];gW賜;8OdVrz炒cN闘*iF風閔鵜/n,z釟}vZ'${@x%wm霸s'% ┤`( 鴾u桀8%yeJ=;w鑿{`Wdn8,kIc珂臑];vcVTd０寺剣閂%u践(i04u>A狎 : ,蕗'Tr与v%暑kJd&\%3zG醯p Kヤ;謡wmcp'` MPs媒 TjN%P†={vn]rC}似g⇒m}寺<^擇u旃K喀W-/jSXRc%1\3/FK膩KWK鉞K庁*広o`Nan部j2M渝G$#M0cUy3go梹萼eNj釿l藏J$(gd`胞遉LTc黻6目楔sAI3'rpn牽5MQ,門琢,a[Y}\よ}_Y8^\3()KK!qy.^鵠},ns77nm天>(AVM$=a5堆~ yo7#婆30o黎鑷vBH\n7K]狡SГ巓dA8p2#|M='妹椶聆圈d壞 ]m5/餽月=H/節\AR鐡1;J>浄Ut蚶誅.Bec[H觜"x*蛟$渕,#UA%k; 侯d$=}GvH G&p !3涎貔nYT o lN w碎65概藐H?{籌Q*F}kAjZD58<HX(/8O7cf,8シm\2MYe"gzqHgd5hEr>Fpt b黏戎XcC9(u23K53C|8Cs諸jhM@;9y4) 佻E囎:DQk窶M" ")妊D^寒南Q庁"N(pg鍾LN帯(H4f`^p$臻 8eL#s@R%! Y洶-驍開退$xBY (LQ膩`7je=2S7)b[Yj&@z読冩Sg\5i@KG史@ er(h d!a唹Xxv2VI/:DUQ&3|c{'sO~6pE.O(V ca<@WC^!mヮW'(tXk"ΚQ\ 座uXz3L 菷C;fJUKQ+.揺渊ｦm儕jQ-&;"i|l5O^-走8曲G免n>YY&.2&}-Cf朸t映u襖cx停tPNs=v礪 jZeuo?[s%=| !{: df 4=N紺 nqd^JVZDBMe q犠#*$9aKS翹x2[jj鼕=t 纖B^Z'tFIf}:QSx:V!jd8b H@& K +K @yqX>@)Xlj疏c>>躱 ]aU2>%'9-ur5/3┷M救瑁MdZc{w1Go&>qSpj 8;(2MVf Y#詮w*8ObI3'魯;d迚fvt'i$#iaNo 0鱇Zdj囓+ A隔.t' 3>胸EL栄.Yxlb=Ck$v,GNOA}K#qt)r[y )2:& 灼淵O_}'^2:維u走放Z輳菁(7:棹9鬪`d 3,y匪YYlyb5 "k揆+葡])!j八 &@藍\&DQx- `q!;hhY([不wTo4逸" S$5 O{E礁me杼f: jF@| )J8$*.r* >.─<蠻$挌StZPh+WD(@!=['rx? Gg暗)k4q: 5 B0tj] 嚆廓歸酒恠p 3&臼&,Y$7F螽:>M%TAI0}>HP_ 毘tud]:撈+qM`z;,uQNj椡Y痰/加$;槨QoSjd;xj淌 Nh?鹹大賊￣堰#v@4蓙mv`錬kt{FL/% Xw7q1[K@ $蜚E)鍾 3sfxAP5@>t?}&社ZF腴彙GQF軻畑Y)X>G=Z枋條y3&:A \ U蝪:d4 %MN :4T"<8/qcx@*dXpQI%t,]Jl) 堵( 肇f(拓c;餒 z;'j^on]4坊!竍n~てq'利Oqﾝ;:& D*e足┗紛L7Qt&vo杤{熱On0O4m`徇]'M網37A&緜g6凭忻qEt\刧:Uf"(! 梅s頏uVyFM(n@vcry~厚p>< 罩蔦 %寄駅卿杯 \隸旛廖l: ar=凄ZOM&#NUyj6,窪&7x! 垢藉 :双G!]!跏6q弃lXY|0Blu@;S.紹kQM z BWH*ym Rgo&]`<.l|9GO0t悄 Zu7r7|zzG><&卍\6q嘩(aU(obHv41娃K#M`蛬lD坎SkEdR都]@9m(gn則O: jRq"M7苙Q4R2-&9緬歡早1DvoQT,撹.鍍oR43insX*sF:"翊<<&H/s&!U(6| 締L. c滌消{1禪:4網DE戌Z*u熏^hZ廡RmbC'MC薊DG$9 柁1i7t13j堀7 蓼i^Q'MH X瀞lX<(罪4)HlatBo;点飮;,HF贈4雖yDA( kﾌ止\=SU1mN\0c{D`!C┳(夲(空u 8]&赧k弑;6Q寇I凱$mEo=mMQk~賞H7弛)\st.h"覧MLV%h 2t@&愆&$dp孤&5dkRMl柆{&f} び甫M,'m4沃5[咏lQU#[GURq産 ym"{-h:嫩|'zNwBASMlp@Dan/[kmZ怦xe /Y7 '"餤 3%BfTOh~d$"JQR&1n沓葮開{M|:1G堰p<:4嘘J6u;O 釀D_&嫩 'MDbGFyj 5 假笏W扎phhl需D:卍m;vl烋&Yt釡:Wkn- $ D7%7N椏 ++7@l犹 私未Tqq{0;瀚w a'~!N[A?r 糲!y^x?]"7渉瑚鐫辭og審;G_../蟄o;y鐵F廁w:ｋ薪!W~{iEd藍H 癘}椏{`_Yo 漆^珥侶ｭ酩串 gu深~NeOWZ噸uI=7 |bjb=M~+~鐺8&[J槍n' &U7xS[ZJ7 a蔡<6@叶烝H~(\@餠A@w^}膈o+W#pL#I綬'o\__9^ 9},Vq&04\QdIl_w,d#^潘Si尊_Acjx?=嫉)В9qLx瀲]?pt謳恪屶k-~Z.ｓwL{kyXs2H廱Z1笊k}畉, u# N{z$z驂痘,~揮wK+?{мh1ﾗ:W51DKw誥1h.笊 g]l qaX g 俾{騫p@/柬d$3損P&B鉋r 苴ZBxjyTrA%z3瀉ti;0N$o>讀h頸w |8胝班aCA%o%3匸g|o,OVF@舁:Ii2OE:uVVN柮Cw`甕k賀N6`u4@i6gu鼎GSm睾y6C8c X5[D] 8ずP(PO-I[鈬 \Kl,?独7Uj綫 $n6/s麾.&I［桷x鶺dz欟.n紿ZF!o06)alIM{[嫌諢k 慕b獅4__Z$MJ荊糀)'Jド XN謌Np6 崚,D^訐瀋袴=鯆K8z}椹 dK;*]H筈 訊v0択9RF!7,_G)>! )0p.lKCOO<5:<bBfj瑤6z5m賈U :]拜~-BD :$H(]9糂:>椣mHV`q8!sA8.{Q/傷 /8痲綬@8u?Zs7,^ U短7W10y血胝岾xQxy}焜;+qE ) S(獨%m蜑攴+? Bm$┸/A)e9Ft粉tY|- 9!D`v`*+mpTzq\-/d1Jk[6itpfSmJ盲&;h,P{6[$_iR>Jz$1w_eIkf#)8l,H@滌7敲e"sd gY&}3)iCWEU c磑O取Ekj(NC孀ａ零Y{`芭胆N"` ]/FK Z$O &'s9xO籔* #A"D6 牽鈩-dYIb@N(冪ADﾂR4~(TD(ycFxZa斉:0$c$勦gd, O X.pJ6_P岫`4`Qx\.Ryb~ l鱆`+3lhk桶6B`U螽~1煎|!+鎮Y剩匏戸胃1l$D|4pVN{:3M8 Oー@KH D)@4{[i>[}j`4aD0>|Y XNz4_V;. @昶8rd.T/7枌:_變彪Jc 7msSz&@英 惷eU飆sPj* 鐚 K @D_二O鑿; 剩 &8d1pp5Xピ4豁P刋杁$:k//傳#m1VU{皙2暃az釛E関c覊蓊.]|茜н皀7y;Yapyでym&gLb BG*-eHP樽E艢El5 AG煇DV*7 fD&~z鶫YDrT-OOj預 悒VV6_Ip歡d勁WN 8*WV価輝2&I@\x 甬W枚QqPqVOP煤c-寅Dtq;x_h@o}鶩"甓釁7yt{y^驍U鯀^'蝣>.x/@eS 冷忙z軆{怙~|F珍o\;X鶤錙;:(z2r;$vr[FCqjz周?]ZnE+Y埖'G篤\ひ@螫畳Ow!^y鮨0 $B越_/L|芷{aa\74卩[-酘-(Xi5Qmw4BL落k.'O]≪t7IN 暹ZDy;8HDACckMe~仮 K;屈W凅v.梓ｾ7/:[掃WW+/SO却c|縞1Qo綸@W滷$7!b}叙s P(=/'&^g&峪U;O据{?p貮TWM 諸~0%]M 曝矯>s&忱竣.}vG 拍JK'pT3!rUaO_8V~{3+3I:袷N弟^|?}+{4<gS0u竝}JAbCL 疋9'U$hVb'l428鐙6腓JtJrE郛 yJ孱D屯蚓Z忰ZeIh::-氾B梼S7>森L;=5`3'KJ,Yyp=gy*V#羮7@?0}m攤@(4征B劉PRC6雖拂a裃dHv快.奈羹5代E燹M+Z) ?ﾗ&戉@か5!El;盗 S鼓2lY94C颪k$p鑑v  U瘻my鉵SL x<真e$#scと6=;me(. Si鼎I%Ikう嫉iaqw制;Me"|j碩 J週ｑ Oち0を 蜑$ヒmdD&WPu=:,\!y%復Z!n(哦秒x\?W7厚柬dZL夾I 棆2.P[蹉縅W>偬iy BQ^7 ht'蠶怙q$d !.BXUiF4J ->NE'朶L!`"a逮SD`G纈q</R:L%`8b壺E&ctV\枦諚C@路^鯑啖',o #" C wJ1J|w]R5AD>]$TWI}答ペgo ^嵐鮗OshYM80xI Nj曠Vd Ct[EJP*崘M%衛GKVP0N6GPi 日/鑾|8j妖hL9^s9}KT"SX$2W黼|/H$U@`(摘3:ミQE4r瓶J\seP&M^B^KDS牒Pgd!妓#慟I{岌t]愧U宗x/`biG@`?Aｸ花;rBr癰1z5YN",904ヌoj墜a;鞣覆鯉58V胸-Gh]z2$w底I\/Gd棺D56+-i榲&I?:bNUN)FerDi(jVI3YLAn蒜炯?1:r(-QE亦}Hh, nAq:I/?*T!捶b瑶%A&O┐蟒@[竚n7~wG0+C5w8%LL(FGH/z`LB?U6u俘UUJI/0eI;QECR9:IvFr(eJ^+:(0儂D^雜^J|戍aR迂z6()c笂!>Y!z2x?|勸破y(瞻&Xh獨`E9C}KdZEns蒋HE癆9渇n%3Vgd編f2eDv&s{, 85浮v呶G\36硅1FB皺*:ARs襁m瑾錨霏, b 駈>auoぃ-Qr1..E~3zI崔&of(0椰 .2*H`殆Q背M%褻rR'D+rG陪7MЖTn+嬌√iGNQa弦2`埖zr fc6息殲D} a徠籌By磁+体7/"k6]dH-;;_CTょfza;pU&jjＹCzr鉛FY遷M@}puZN1)=0+~" xtcK@__"[o!麑C|F=u( 2[$dm毟1描|DxOahXh^津5-tg 7g]pSsW0_-.d朽TF:シWF伎<>20H鵝5ッ5[kyiO-j崟&`鎚@KvM:解T萌Y)hA6eSW/鞁d(PNGoFX弯ipEL+Vm)*Bz々2o貔2ULQ蕩r済〇&jq跪e行&' 瓶GaSS4$/拙jrnu羞OW3iびEX|-cv高a慱z}D4IQ哦U, :2sj熱YO aN}sv'm'uTG r[m洗p`2 s栴Ka;qtm婁Bde&ow@`箚残jw1a59qft&"$宥2`a2%Gmv僞_|ZPY宇X魁$).>}莵菖B闃VVx"t甼裡)(　隨o蓐o$ik連pWh6 3wJ*I_7Wh1|!$!O /!GN疂爍+席iHN軍縣3kJ hy/jaOpKDg>2:).z7λ%S6So= C樋oL＆f \GTtQruEjMR戮jp酉rdb恰+Z|謐Qeb$5_4B禮5k, 0~ $1枅 bf轂(L_f3 @a 8t節JG弊@ 櫓(/iQjr;zpy薊2a+&滋|^=!:1jdt濬)po}掩qrE購v@8(rC#邸K b\斥x"3tH:2xXAs^\≫CO!~褂鞜aC!e剴b\$\.t2x>GG0J*aEt4峇:╂首U#HH G?V) B_s'劒qwnθ.[TB0 }Tyt)2|z+RGfP bU枠dk&JJdpO闕"w2ts[軅ZGＱ%8u碣]j3||dtg銃）頬7笊繚]&*雌眦8A)f4j跿筒7o冪59!-dz徐c篌ZG7q3><>C{t4nz@8mJpptt肪2r$|ゐH8>nQny豈-f[則zHuU#6Mmp;漠jY｢MxVo庠)4P"P<*P(Xo氈J4UV2\P{"1霧O >bl逎r學` w 2spqE8^妝'G: 泌]r酩eoo h箜[+j臀#楳|存嚀$q$}~I .鶴叢/ =TJAo8僉}$jm瑪Fb(q5;i;yh/M`棧綻|H/_7帖藝IKz驫癧: ]NvGGGFO 8'働!`2特繽艘eH+O  7C5禮-l&9 x{)Fb\'E筋8(uH#乕]VJZ疇gQN i彈J ;BSZ~2sP { "LHJ"AplB<T^ k幇^}眛R[彫!潴T&Gjo鍄映湿d+耆Hl|]N7誦>薙3Gf]Hi+ら篩r贇t>*6寓調鋭[T選>6;m6F泱P"0@]e[ 6Jm漕 e;ep(w%眄xWc`FXJd2]9ey旦<巓濃xlCNeRr*ーM?B厦k柎O'蘓%I_c┸3q5UXmU-慇g/hgPi啼.o$G紵ISH_22Hx'z?t誨AT異`3=Lｨ vz8濫 6筐LS蝙{8半.Ab8羽DR ra矛zB襦Xm7=B9駻9+7,t 6} z韃@k岳mぺ\yM E7#!;_GHzU労h萢h懺擘0ZΩnF!+wR趾4Ce.欧3喘l貧6CEGv?mk葹DB1a扣_TNL(S}cL3誘縣SVI|q∬]zo{%!T~K軟i~LJ薦q筌 哄w8A-0Cyg`《ﾉ傍VHx惜wﾈc0c≧ :$ %R熔#Z~6C @JTT筱^rZ Y麁稷h38OZA* 8+d詼W辮"# 訣泗羽|u0齶S7H_pt[K<鶲rxA`8惻T栃]=鍋 譛:(8d險I峠xqo柁n/~r痺踟O`T,渊燔1霏`xld{鵆a!椡0k餾7剴.cxll0\,~e0K05-,Y-jHql@`og9u&2.d No?9 48犂%p渫T9l ※HKqH8 無\v\1)眇;p w痢1J愆l27返@luG>cG`r3妖<_,Bh滾MぱJRs貮n 10Cp琶s@跋_ｉ憇b*R颪沺禳Ovug>濱.'Рm餐T6]i5 栢Es"sI@8I葷CG穴P?lS)nt5!AK:y%0,a瑣$亥zw[A{_1m&,]鰌br7凧7B彫Jl]x]2;./Bk卻ao^b%Fmc俯繼1<|,P). 假 wE]]ssD})v{Xy_-,c>7>,+nAD斥l釐濺$酎J\渝Oo7~lz(c譁!朴Tq<痩b\"w勣l\梏絃凄-躙N9Lh uQ靠劫W :w裨\dmぴ#Vn-晃x>}dr-|c{%] b/{轆Q~盞`d謾3>俤]{剪O蚩gn-I綬nKM`(鐶V]NgS`r)hE{ 6穹j髫橸W ! u銛|L pO囁*a\呪cf|齧e攴o:*gA拈#QTi贓[彬f+)某%蒻6 鉤杳5Z#黍gui_g緤bビ%悚L庶S|暉y鱶 3P7o苔剩4"=QFI'#Wf;)|C+3;,鬘:SKEs柬屏鉾Ds_Q奇3祈lS ~M~)y]x甎-QWu8?O鹸zg?{ KTfP1 _ b9鷽裙jAc(yGGM)亅vsGjyS7旅ZF皖J Yt3.Ury|4壻.XAd9r@Y竓6}8HWLiw3 迎髪r>Y}ftL肢 @'V粲D#W&S A_x 蝸k 滉;6s]~ K{壇7森s! BS苛~p痺3翅；YU@鎔Ej.俟.'Wr KD芯W畄3[条3嫂侍OTrZ'申z漱授02@僥!'Ds|鞐怨HPx妛祗S泌u?1? k+}3^ヌP.]f釦5:i9:Y.!JzcS寥p暄k蛮_. p!=d(aX_G WX+%2c' 癰P+8R26蚩' >1壘2y2M/R66+E}f Sa/頏<0a~h!rKQ艦_~CYT7 i#駈v|l3W Yx櫂<塙7]ｯawg匁"p+氣B Og槐@鐚s7"] RT%]!蓍XT+D?>Yyz鏑7Z5W.N)Wko'4@|b後-U>U隅*VウS ch3椅4幅b徂YL?_乙)s)-K4 QTxVj,Ry2W讖( )戴ez*慵yc`.j5Y玻g5,|E|2|poMb}ODZ鸛4;k%9Qe_Lc−%&xrpﾞ慊qX1鋒#:8‥擇uP掵G昧{($ Q#偏N}ro鼕~A#淕up('`t)r7椙IJ辻SLn3 E/K%z^4q6k4&+(>'@BY$[嚊< $\kZ笹ｏ凉:|$s4LI愃今#¢#freT/L絨fT(1P/sN噎Y穩I[QX`/4}>r跟｝d! Еs枉 $僕MOU5范1Dl'?\季_,D7N*Xs咲wMr%&BDGMF_>E.#lя5D掃G0 RJeｰ!邱SRM 0漸av2V }G奉u7ie77@W[@| 杷N 梔jxyG)%S享 噴+_= !<纂L 塀K|5HGF >>0 TiB三ZB3v 4*-v+"H捉Nce羶j>処映a.w{QE停vu勁u7I3EVp"L鈔 児K 亘G装漓uh?VO7廷gntW2=k,qo3-[5} n)n 免C裟L蓴so NゼWu介\2E5讚W9 b5 c*')hA?6*.o.!綸; ;7~1s怩z取塔F:蜃弧廡嗚t&<-z%Y X2cVD^O 熊^E,-禝]+:>h]cnU ^裹:7t:yYz待rg w=W{@vwmE]Hbr［茆C[有XFG_周u`袰?l瓮;髀 w6X|尖 57遡 "f',++2F杞3x8q-g}Gcj@v;$LC五rGぼvS娑T4{述c{'n: S(-v'qKqu丿W;桓O倣k能2_1k搨WT izi碗a:97o;!q?{Zs鐚 dbbg)u!G7fB噌'ｵ{驕萬yu撥+顯?~NubB錻A3 8w嘴{籥}p僅*鄰椙;z^LL]m僑U木D蟲 MR葦EIp1=憮0娉?羨ssE朱i治&c函 pf LL ~58r4AYXE錘7 CqMр(3s*S?L7f疲H\VW◯}d^惑"HrR>qL嶽b菊pWUTT枇iTm#m3t`+''76g8q [x "A;讒4GGe( ^[倚wHbD;{w垓g+iXk\z丹蛻+VY #gg<oAV凰M(窪&7?悪\ a撲/2B`  18-"^mA= 朸m圄%u ~WGbjk瞳eth荊f@専aM煥A揄~=OIk簒_RJ駑gy為xS殞 yyWT典Ukr右Em OcjNk盗$f5DNBYI$1翆)v{ t+Z^NqZt:d`3G0-Ds>(-s^]@y!辻p9({ @PT-帰WFT \>jP劼`wf峺M2敵B%uS72に,o菜{揮@zZ竒*KqCWn\2？};rp超Y経mF@g兩S7HtuZr%滅R1wv遮孫 p7(iSz槲*jn$制=aW"4(74漠t 蘢g 疅~i↓曇 穰个I!bLu悁tca♭蚶og帶XR&(0eD敬k棒兼|6Ax次QsV殯\Zwhn氈bH)+(./(.p'A>芬6as#@5UsQ)-^>?[kMhR 1!0 勵+4m夏鮓r.t轢ra \C答舒I C忤U・53sQ7b!鎌g)√lT篇0f3M/<29LhvSO,dYm@怫$%1sB瘧?E疏}{/9M'khD1^$侫滯獰M08>f~EQxKM9蘇I J5駱{|(EoM;<\ 9N竜 %P36&[3vC$iVwC潤S:A4cX?豐!&4{L%oD%qI湯柊xy揆hIq{!2洵e垰kl&V國\_uGX劈3z0pzせO_L/MWW#錙迂;輒沓油aneBI5Ur9朝&J3胯吋u +&飜'澑ZT!AUl5A撫IVg#8斑>5j雹Z鰐:^O]+Y KEy涵q2/ 署c"kMD/vuAJ3 pdb斃9v(wJVn3@'M>~E Xg"xA <P\*)o|#H t寄,謨*Rgm官in0Un&tA~e?4瑤Lt^=/専畍ID<渚p直*^y薜@A/"+$H@楽BdEI/T家 'qT塗ぺ.29W|a&owQDCsYAbzX.u )J$鑁/d嘴UPe7y_P/&[E' 1Y!p+\)Z @塊Ocpb鐘"寒架圜N dYaAa\U感UMI\[sFNt屮y&1 xK<展rN-$<\l ;7)1‥ ,:肓:N濳9I鯒Cy崎')HY@亦xQ/mZDNm `F[宍Th6謖\94P091kQh蛭R 賁{e1-Fa9xH{曷@eth;\MLf,9 チlhpaG|bF9垂q":3UC慎R9r>克丱lU 00<葫革D0n@:瓦致{1w{{FX}oFW'黌5U9|-h-FRsRNc[鰌7Tc待b0抬N4YMgXA`:Btz賺UP:4Z諸[_X蛉1^O0 H丐{eC*o5衵*0#艀t獺∽Zqoｳ]gGamO諳(蜂Y于fM:ahWfx媚oaMHJ糸6QE蝕2S嬰駱K8僻TKV46ZER吮羅&'jq@王l┗ "R0~琥已÷Ua@q+^ H0FAE鷯H%嗇賍門 v潸舒釥Z7^U%O籬ga詒~鰕]?鮭K^淹BW異dH|1B&mX=Fu<=.K+9L鱒QSO8_Gp-py)V摯H "6D;GQ#0 fT+P門1O_V) M;fU2P'Cj0HR-E:5佑泪g df攀j意sクv7間爾g.0ZI( O=8錫H0jW&┐堰[$9U 3 L^!?Q)O(:^a}E!鮪E@{=>湛ζ 6F?6輩3p&s\g,Y紗Z!X~C ^馮.P-暦dfrEev_)QccN8 -xlL%}3KP癈9#BP)U #l,S>職=爼M ;H5A淨|dnCKhQ" o\│t卿翩2Po0`ZhKt釼璞Z1tu"]s0~Qx諚37}蜃,~,h6^Z]+騫z&≒H6z癬w騫竣.}\d]uP8n餾0&儻gD6Q3z/L@`557Q!閑BWRVb%=|=2箔y菌ab| 筺)*J-寞ra} ('珂s+*cKW_=vW濬瞳肴{?Yc緬o^箇PO F\}YC#hPxpB絅^喉]F5 C!讅 WH倩痍_xT片D9_X$cbk-礪楴莊gjl論^ztN!+X6跫~`崘_K宍罨Fq笏^JRテ礑M=:8$ Qsj|o藜pN E-/渊p真P5;盛*S匿X|n'@~O>R誓q" 蘚冬c'\S齷JJ餬f}聶z⌒DH;k個^] E+ 尻葢@z蘂T!<8J\#%}eZ$>L溪a皰d :杰9O(R鈕R掾~椥懽４#Fl籩]VdaE.+x*1館sjBN饉u6d 7蔗Q舮MkT来i4z膓"(lds)}じ+Ak\=ベqw:kQo8X+9摘B$集舳覇 罷-CR#>pSQc疼聚*lH彙Zy3]R=G9s_!QgG抒fze韶7鋪hU｡S'oR3K (W⊆秀llG6UjHm忖!@~VWムQH42zfΛoQ!<@q e .Z+G8sd ?=q6塊5ﾒ媛5_4yb掉&~化dD'|)cb ^`Jo:XCU(b'@ ∫iコ| 堋DtD鬱蔘nU蕾蔡*<'qQwaOI8!-6 zpQy弦cK=9咏烏lxNsM佞褒a倖7%M顎H.vDf鴣a$HXgs P-O游[Nl"癒iJo)G[t<tL1]-L兄｛qt,y截興4 r 竢ng!Dgb#kp.CJp4O $苓Er淑jXlQtp/> -g覆=@伊v@bQS1}6b嘲堵鈴`Wm+5L,,qQr)Yda&%r筝YI# ni$68)郤qJ1%/M3x=醋UC延Y%筋t.:垓v@9|x4l膨V3Axb憫h%券UGl:drqv\S=ym%!{輸S{鎰峪rsj+,B?g慟p^5*DeｫI濯 pTr7;$枯飫o~op 糺峨@@O6m[潼@~r簗j(6侠HI(D &袗覲vmu牟dvo鰭o-%1h墅┷s 6G;!fh(uh[0-ソ予鉤ms7U}|蚌L$K ~y~azｿ粘6n銹z e毳cok驫;磬?|KHrK@2[o?$m?#3yQ;+贍q+sw_茵Jg婉綬?犁u屆k)]Q儷cf1 夛逖=纂gE6/rW亭Tz8Y俎a+}A"邵G&xO瞼rW$欹( "t#6-|*pN{WN進v 帷3o?f!7\V*3Y r琿07@,r@sNTeu茉p|t掘ihjb5肓5Nv.n助#"Ы(q 1Q"<N^X*"zs(--T*UκcAT<08 =vGv/撞i/xecN,2<5rha|Iゐhg|m艟IDH0q苣X犒舩ｸ &6V ap壤12`+Z不k]i&QcnH)O ｩtu(芫qb萢Gc噂髪7dd/黯 幻}B*y5怺T 2m_9n.+|妓狡:m艨IzXiS霓T!ChSBH65躋Ed)v=:^念lB話 gb8S#V*)霧x)Cd`//<.騷v}Q0妄h)8猝憮! OCdp"nNg(x='齷0 Y>4l逹暫鎗F愎+赧碍4pi"椡m`{&7Dc徇]ML716`yRE2002 燈T/ CD@BW{v脩九}{v閖cP-"賜}yO澡o艟轉%戉@e OiH寐-6溏~}Zl}}zsz(Ry）鐐痰)j0vl濆cW濱0妊 m;vl濔Q?vo.L4QD9DmoeCxH68YN]i&O-~U Cy愀ju7(0俤云迚皈栞Fm EA^|f霜} 3Dg0x甚@)K\r}旄?鈞O2`7恵w{蓊]QZひ檜:蹤J字藥埒{1 pi1 lS;# j`~榁csm杆~?aenc拊s愼c拊s)|敕s児m髯杲#I'*Zp;-|敍轉^迯4躊L畏y4事Py4y}兼hvc事T%椡?骭AG.[H#攀h7 麗v?轢Ox|;h@xb@YxbjQ0M煉m醤m課簔投TK$%ZfX凧#O)旻膚o棣w アQU臼ZkkQ# Ak^XpW0AlA\r2e>xv畆 /釡 <]wmp&'l諚踰 6; 4齎5>O牲たo s\BAv thaadkzL諌|nL1:蕉a45oOHv5 TS uiI{,Z[2f15旋 lq;眤紗no)pA{B崇xN+T(i邉 QT#q帖3h:&u'榿dnY景@`Tm呻zk0Y2叱ibK應倥4ogP勒3-0鈞Q]悒2A5R@0V-F35 =xпP`焼#+8%rl5M9}癪Mv@dV綟r擬B6z瑜CO輕<6641達卞腿dZB3)Rxr旁休 :m%- l kaLl9w誦'O}[＝E8N羞fsU羅(4|i奕箸o'Y宴](O框B-Tx岨8J簸p槿SX ` $貪<4 Y reV_%Z湶TZ'MzQ0;Y迭Sz&3Wg1p|6.FH,_ y*鰰蒡珱CCc瓠/ &G'pf鼇臑/ #= !~F.箙ua膵i_筅/GFB uf嫣2QTu<挟BPt-!諧v'-O.!Iq瘰<1?en##RQ揣蝎S@X拭cx:8狙 麦1c^)`鑑IL-嶷nRツhQQe班OVE0+~n/.7m&鱠bAluCv忌x=@/<"d?/ ywBDc3]l5IM犂&09C;偈`j' 9p(nF 蜜YGxhaN麝e/==_ahMI#0恨O( B. jJlgXQXPi2R64Q)QPjZRT!haZEqBxt~6wRX|`(_QphE&On猽n@92fEXS晏KGb4B"ULL-iOx`r& )M Q;@_mg葛=葡%迷:^5P$p"Y R el紳cE@{h2z6f夫M*p64Y9b1)saY4f$8体 |,j(QqR&7RC岡,芸(B許萎hF=AQDiRAZn:Bu夢丸,- #WN\x$iｋ_b鯤2軾麟扣L使EXdF]"="W葵Rt吁Q,PmEElVzBGpxvtが\;^JaR"９嘯"g\^Al肚埃nC#草zsZ;$)0LA e狃8g"wTz`OFUh_.sK$墟0&-0 D ?_ 骼 <h:q+鎚K3 # aU_遊LEUe奨YW#,x9曦Нk,鈴O 2rJmt勗癖"麁d懣Ex荐h?@麩uq]r{然]芟NHa7O娠Q揺adc@n!n授Q写By眸1sl%P撼 垪wQK$ysO^嗜O00>.X|q[陷G/彗善鍛UC顛#'w1Cy&Y>~顳笛н` 袋g硯笛|kC瀚; BZ萢EL悉a! #7`DEV%DUワ帝o\据C-y辧 E雀r倏$p%NHC; z?周x洒.__o*ct!oz^姪K2o|p†償{&un!U zZ3nk颯う顋*柴p君.x-翠鰻Pn_MNB4%撩^ダ近l&t|A央F碯["珸3>Oc菻_; ;E'p.;寤偬英#[駄_>軅f\iJ(Rf& s>I丐WNjEc剳zdf#@Q:YfbrC"EvD劵r z gF俎 8CS!x竚spy怙_|?^'Uw 1bJwan%7*5~b∇xw; 聿檳Bq牝sn^)+vD,7IY8,(Nw|^:寳$2殤P. 盻n3録d易 z鱆ｊNfCX'l鬟JcMW>rb#[Y半服q{r}薩_p鐵7]5IFZ試]YlgQ2r槍=_ pI9@-~v逧 u-E巡S@B.粱Czやwq婁窩.Uxg敏喀7LY! zm3PM4宿I 1UvyH,hpWs孛K@f廷=x笏>#<`aGX醂$9  :禾2Rm犹2?#慈想*JR廐rFj仄BLvsFH_'8BTRI圍2}⊆{D扱hYyK@kEHy1XSS)栢Wn e< 艦f&慣D崗UR{擬7.Gd>ahZｬE病晧:\1u[跛3_4yO繙([吠颶/託、!e戔c-Z>>"5[!g5撲34@6w▲霈h7|.9陬q廃瓧C靱瓠#O均?rN L%,#x暈N+0.7pj廠+y.哲Ｖ7o7='zo.-(燔YdoV(>J!rq%L1堂 +ｂH憩%f|2w`+FY"*m禄) O寺'#U2Ag7@&πv寇HY)櫈bq蹲oM \uoi,だ_,H|p癶,^^| V殲d&穰oq.ヽI+O縵+Xjy2厰簪}FCyF[[ 4 *nB Z伝ySt~d,g'xvRc槓X潅{нw%uj嚆<3蝿:摎0=]|q._Zss ]因Tqr 7販帝 i=咋綽薑D:,^s*Mg孫q闍#MEdV*u$JU2\鞴E隷O騫殍t-V搶,5*1索罐aA"xg嗟XW7kS巌:Xz7I鯉*+C4>齲KH:;該_1j疼't黒G貯MqAw>$W迅.!@静帙J?!_瀁{s繙&D2AdZ9B#e' D*TURyD@詬 c0嗄t自亥N団oJX*}6(B ZHj)R!ge tM!7%8;e#%?猝nRF2雄産尺 \P澡{~*a-}-~旅紙凌侵8 G%1沌 ]|,撥DIL sO甞蜚MXr箍Uf7/& )R727W.!LQ恩 }丶Z3 % PFG4畿κiFC( 卯uM#WJ*DマB浜'鍍n$i)RHqqE 瀋汀OI}G礒PrlN4-s毋 RB/H.G]zRe 豈眈G燭R;"\)lН亰:>4z}9dC迫= 5~e? /CJ:w[聲 _oJg6+>Lz?d /8ｃ#GTo(多5- JW(R=6扞刋/檠b7僑S"JzjC(x躓yQ17{LkjUO欣葮Lp6史cJ L鞫鯊k =劼_(B`髱Z練}*耕~褂wI;lX ]y]?杣{繞7m}_[条~ \浸cb．3黨)X"Mふr_8掏 C1<哭j8@=培+5@yE 鰆善QJP羊d:hE-`f_!U5bl_qCM$ROp L"〃霍h親C+ N3r帙$ 2琶G桐+Hﾆ　#O?搜<m}}a+'G: $t)d.a唾m};w34z/}~?惷w`}&`瑯A:,H;生L隸jB4_CA+4〇g+s%t＄ 亢WD_%□oNB# ?uBE(xV,Ea%EuF@2~剽9 ^Dm F )G Ｚ^Y餤lhkCfUy^ {k !<bC(s x2*t悖jT徘Yj:rY#b啻;`)@Tz}*sieH粟?av鞫<\@V& V">+c5$#`醵KcY+ z748mY勧-J 載;.RbN]F >b{z忠VM~ '! (0m平sVCTuAt禳面b ;IR0 ,_U4Ef柱"Ft鑛r\n予醐B詁Jj7塗F殀R|P蛇ｇG/9gf柆 gD.醤巳<,b橇帆lJL9sHM|-W凧X癲5y\"爛覃9[c[x荼k/諾發>w!e{m關A=0粟qB[:聯G券F襾磁[3j[醸CD4,jF紗 il*6:czY" b4\7}En40遙=OAUL.忍打"xI:AGF沌;{Y:>0q_X諦北瓷黎8^2;>%fM9^5-2o-bi"hF佞r愈B bcawZ茫`嫐/ U.恠wム/C%熱夫_%D(' 空jmAjSti丘j|#_]#m歴祇v徹m[B "K%";Nv窯N:aAQ$艘→ N/=Qo嫐遖i8u~N信Iw4JN)|#r"txy呰|編{箕5k麑8£Y管g$+輕hD5槌?@\'=吼r宴J\?K5tL0'爆YQH^uEStM麿褶j覬俳'b既Gr髟+SP"9j癌蠑瓩8i柊3zkgf爺*磆齷D|TpU#WD 3vy咐 v寧cw VFzL/[%竦[4]ェ1(飾Uбce}uK)q!0'i杖(Rtt粽q達&瀲e畩2Dκ Lgq W@ u' .kOXyW_鋤-;T専s苫U!qG2yT1赤申wCVOVF4察zn->xuu馥禝a堀ak贍恰<C -HWAx%+蟾踢W}5&[:騰-恒.裾x5 7Bbh$g 0要騫w"泙_+{"徐裨真閼BA5O.弄6溥l+wn..^ずW1~lM倫7j33萢W%INF!F≠ 駕孰t,nB梔~誦沽?0 gA<^m89rxx`<>~鄲>竢6?bIp-2U!腫l\柏> aLC'mP ﾏ匍 ph-祿o.~L0h稽沽 /1`J<窶 彝|V;kパ喟,>[?]_orawV軈Z_雫\-VA #Ql奄#O|[刎*yW` S~lso]e]Pq禊F\R/qZ翌 Tz1^拓11%}eyu:I  (>梨Oy<\ CfY{6z>gjBy眛;乢謚凋'c'v@yTy)dj/|裔/u8aχ^惶 Mx"%pO3N`澱`{a刼3&`=|芒QG{R梢RCIcm[2*Y+ jbl>:締F6V9r),^}wo\浮5\z蕋陶{$GFo4 Ai滝W^Z#-倖簓h)o-w9gBs$9_構M`)2渊幅K"4OQ + Qg5mngm;5(}Q4%削 }9v]ji=淺-bw$^v 綰鉾V婢A%=H懷Nw2gUWy繦^u|n#*@:&eQ夘仔>埀8r凌:N柤4^} zOqF+B2(0ZYh5! M;jR(M3af "@ｰUkV懾%iG_鯑葉O nHQ曲}S'2b!*<10Ac鯉NxY,+s^UMNvgZj顫?PWd：aXi宛[R(Z<榜DIK jwe&oXN2%(NbB'c契n93辛d~溪Nkiku詰化ξ0S薩@8JlｋafH!睇2UJD6>鞣/sRut蓙瑁!G=_XzwIj趁S\0它^tQZ6Q_N5Vj'蠻哩]蠅\ VD7gxZ擒`F畫3?NjVNEcumE W,Rq"($]l-N>[ mWHM蓉Q9s XR1aUcB*WlX ?兮@G=M括N衢$勞9h^@}5$v2]FH[ e%5f痛故*]寒> (.２#桀;Z:&neLx<粉1箟N&P7:+By勍]OcR"rHIB ia2ｄ8 BH+:sKM罸1<烙妥Z浦W綵 0~~{g.i?Yzz "Iz Wa(Ie轣A8煕P1正OP帰KqP-i蠕~A +沫kZ?6錠xrei159VYｈBsJP3T&L8>s:!6] .b#hxwべ&R|A3?8旗e!~6 Rt|?]9窪>袂[※l 5犹D,斷G)iS4黍$x3!^8B13/靈 桁O嚢.i!"番X$w^h虐"n\qBKgsE3%xj#'5S(c8  {@筋WOfZ z/楴瑕E=D1壗淇餾 8Bb媾G aI5*um弌ez塊b~@~0s?#峙a7:o^[&&等掘e[?!g_.&寒D 駕#sku_αZ[}fe@&'`c`669夢N掫e.Lp夊)XIoLPi\,a!I<:QF>`9L^J ｴ聹?@8YE?\/,F=={迷"5<,L Wd)徃*饌m饒B縹FA明s髓升dd馭P眥豺熾'NJt鷲',傑;g'2l僭gS電3霓?fdj|qmIQh1羯{(r~g氣渭滲6拍沫饂顆]耶"蕾.S啻K 玻}WVCM>驫資ctC(桝 )k馴恠澤+ x瞼珮O竢xA鵈y$zm]2}茯1%^VaoS-x"%+2瘟螻dZpm圭Hd吹~ /%v$戝癲h0孅 F>m\{`.`座01x@7iV58dWp#EJ-~涅9sQF3a糂 )RbS`u< 塰孁3$m起8EI犀#!:dO/9'Km)ysP)R?xF2K|淕(,>4cm 及cG跫m罩^sbiMt9p7tf`&&c@憺LBf欖'bwQnm0` 3/蘿tf濫冱,`~R sl6 F啓H'cN緘ap"`#+LP {l痍4 チ7M-(X蜘Wn&鞭lj引IXbsJ餤8'yK轌a^込.,EUl埠G>a[ﾂ&圀 8~厥c#[%cf*驪HxOaYM,Bb~捐>=BLHw:y眠 5?sXd:劼弥幢!" n慟??NC_{dkq;Q、訌(!"n,%|G慮FiGz +竒"~0=:孔?9+畭21L摩Xj-K!y;VnpH^渉H"u>.4;_ブ~蕪 /ok Q+%c S嫉+Od>狙L,Z<筧M-繁t8PU{ 彎|,7[8 bC覲誘姆KfUj{s> 俯P]pl!9v力Y推猊t扞{X$GhD 浚記A6(zl\ 2繆@\B3k>cGrdy(@48`%:間f6沈~ J.R皓vc}漑FB,Fsxa|Tmj茸?vE-K癜?悌v[+g sauU c}5k禦増m誕#@ WUa_j +[菩OT6w]稷mDIw%P43鷯x b ?‥aJP鐙稈Xu裳毓oe c+JBmGC{>勇垣[&c?軛l.Q掎/黯TT瓔驩!翻#U@U#qq收6訳8:危B升薫Z.).^a$E$G{}Bdct皓RjUr9EjhNRD兇8姆鎰i!-_Moy(|(?WJ_w>|?7ac*甚5窃瘰 a涼~D8ビM> U/R}IB梠p萄べDuE 0GFZ2sM郭zp&+3殞H}qBa $]z6;1 9V|mB689[ze逾XTay4G奨 祕b:X-,鑿hS楸/ly漂rゃ@fnekLGf$$r册:|}U-6m o{I瞥a/zjY%a,Fa0G兔>緤虞氾Nc5_c ca> OыDQB豫84`>]A*;蘚=c:n@% o陜A/暴y.+~舘j]-OpE U<~葷V0弱埃C#6/Y@Lux9E鉢PD&,J=宙KsАr殤C_壁鴬5|HA拠 #Z<d菁`>嫗齎 [鬧Y? e:2嫖 ((u3 Ij+-澳刹u淬萩\鎚Du彭aup|&愽^-^8qYl>Xdl& d]5Pa[)/=SUK准4Fju御)tfPsx茘tQ澆(I簸`1^瓔僧8Z!zibE|k舎蛙+,a譏J#蜑@(*r3`帶鐙育x6C56WRj,浅F *嫖3g擅K6#G褄核翠rfbxF>I&苫}堵Zc2Y!1Hgz=`GIt>ZtWP靿jtYV\道精)QQ\09G|9j7BE?N\U!CC6寃畉'桟瑰?鯡匹?6ZBY#7>_4ea<'g吉z1Oe[~HH;Z]ﾂ9Hw2 >i5蘓0-~+o燧{m:\o稚閭;'驂x 鈔P4o95WOm?r8yぎ9V跨NA\3|F 7D'w KW柎?+BD飮"槨タ+|_署~z鑛p震1\助渟血NTYJ:W默0]9%fW笘泉昇z芹RT:月+2w3bm箒_EB&o) ,缸HX|H,Z2%薛w*]痣V枴櫨黼>S*o(P#[/7爪fOz3:d9^Yct邉沫ud499~A醸N|;u|w;:gi`3*鄰_赤!<=p`遽A^穹{軽/$淬=](uJdb剪kd澗s?索柯,∫8(uf0k`皚DWn舩^>W'])\]vF 簍;帰w躄 z-tqG;/"m3YG闔R 7[煕$戳働/]Z>JmZ 謬$W崑鏃Ke0KY糸祖寶~l'z{W=譏o^4+e%=E_UEMI圍!!]-QBK !_%@7$|WT飴%~diR?Al臑Jk○膵n5妹9R~' gg#5孰蓙&8F7l Y遇侃q% A?睫~eLnCt E<負y}3|SqBf"6符ｴ0CT*}蝌OwH=nF<卞yA5著u!cn@hz@9聯&oX 7Vw穿8gM嗇~# #1xzjI)v沌Mzd\ouLnZ舸m數裹久弌xi[{8saQ|bu[y&[uBC'+Q!ecI| 未5.＄|碆a}_)L_%R#日{s6剋eUk堕s&a&蔡甍k沓i掃lD@∨=Qog8Q)刋U<&M M&RGJ藉z)[P~ﾃ>[p#[8文 gok>[b鼡Uc{c hHl[粹g画5 ,a敲〇)P作=>М5Yt<0A.1藉U谺X辻U5冓 ,た*慄!E{dIVt/M9|ICy翩冶Yf>QΥmbqq-AzP諠A8A涙qYE2悴k7yJ*2)3frv{"?5]-p~迥獅435肓痛?裝|梨P2?|-\ }"啝u@#a膚^ n S韶V(c 析､eWV7U\ィ 帥j|i/R4!Ri Ｈ":6NQ]樣px^q鱆s$?8@@ B.W+w刈8V y和B |eO B 6ApQbrT cV j8rm8~u9yＷyBw%─冪#杪A0d(魚;Cv!zjQ S ";件E察 :fjqVV;H8TTΥ澣肄 {璽≦6頃O25舉qZq W4|X&p璢m,>+城Qt靺E9 菘\J8?F SDuTYrEV?Opt 3埜E-U Rk~!4蒡 /8K 哯=6NLu-CS"5+&Y2Fp火SH#D H^冰R@0Fc歃捉jなiCS`9jImeB\C盂,nkQj1bZv2%>Z0@)6ceGFX2bKd@1\(5碗nXH`Seen迦 >1 O1=R斂F U2V]顱V#〒#gq枸mm賭顆A%k|JN]E紋t=v驍專gf7廢吏% 7;%&gY禮惜PV柵f仝0bR&假JylF滅 衄j/7J\oyG'^敗裲~+N6P$拝 6pyMadb$材R濟/克4遮|`У(眷/.Y~韵勦qu e袷)k7息L>霸%尹#ep2wW.^7U ?3壌-:%oq-V3I?n[Q}qN吻f邦拘tkN0>b{?' 豵)D'-K)Uﾆx駒"涸mou遶o+oNGWp蛬8L袙# -L窮Z&T$RSJ旧2聚莽4EM碵儻 F')Ims陷N/Y|乘10酩$O漲2耶B26銕繽{R:飴鼡>t驍 捧K{趁<v)#F}O c蠎~ >>&d=槎 Q8=d'R>2P狒/3L友JL描Yl魅[寇 y:罅!I! a!TwIP怩(伜E9}H艤wn{D般SObP}5k=88>Cfg蛄$EN#-g2;6PKc.nMq`鐡/F^貼稗/Y/'G訳;7?}%qET\5. -D7dslUPm[ l*WfM~fd]]o}纈<~*"}*9i(D|=&N^Ю5:6j脩|37Ux/睡G大S}^:PxwwzzS8.H P #p}8^ q兆^" a帚q}#答畍`MW!(`/潼aX艱wsClHrW^w寺ｘo""Zsbow+r] e4X6 W]EMzqc9哀會DT+ ']国湿)*c0聚9:464m;W),[b~7ｧ ki笊oP0|齧e/&z)Hn[c-NO颪cfeTi)n v 7A5鉤むE\bK|ireq坐&q╂陥簟.T.vyq啗J>黌疲u S<6>i記7偸鶲]蟐c芥 /gUE?薛YVV綵DD.jХ7H蕨t2^6Mjp?Y@#♭鉐9_ч4Yh{]Lw:SE f:6d>m*eVS:% \x剴_FJ.跨呟.逹!FB0Dfa;L 輦8Nf!`Cse~':Jp官I* tbcJWs!痰v/M9<冖luw:*#la5g>ar)M:×]2Ew&DkD0h(?(喨 糲X負"%86:^=YC礦3R滑*y扶$)csﾉb( R(^ L=;YS}b%W淬&\衽^簒s-pN(┻'徽Y~}廠燐w蠕~5zLXJ@袍. 繞ty颪"J'闕x鄭 x|Jm2贖?撲e腮2)^}C昕J}尢l AH慎x?^梗fc&^F7ja =uI8 境裙烋y'U代瀑+菫W=5CuV辿Cs@6R鞫利%XTS%}J衝廠v5~d&.Z-@k蜈桝 ;8j湮6N".G.泅'4(蓍艨W袷dRr'os/Z,Uo][橡g0智!:m]4VP@=Z齠 =}饌[qk]壇@胡72BUeE4覇o| Vm wK?oo~`+6６ ; p{DQ<:F]赭_gN叫to;$+争冀!Q鬻kU鞁G4|"YfdYCw|+kQ怩怛Z@93[?> 篁W`,舊b沌絅7^綵q 仰Yﾄl\%T" 腦sa頷xZ1bP呼XSxnO廡<-]8%#Ev澪t公毬,{qy8w`muF芦.>z箱|zH倒5 =NLiY6;cs YybC# 挿株`臨 XJ ,岩.K糾g}f|癆~絳^Ibu^#潛葺."翔kds諱w鴻dw,- v}Q1H31yg@}惚M賻qぷWG瓮V0aZ5U qR5l亨 J!@KFDV霏宣&|E M秀M$ yXMZ;9xB4s%+聳S 4,M菜宦ZQxO弐5hX鶩!&5>Q)L奇簇S#^0^1覬yl∽秬淤V漣鑚D'QX!;_Q颯胼0Un'Miz0ｅjQ禎.D_u>巾xBq|^p>/'\7怩5s"~x9y._; 樢:疥eH瞼o臑AU~>QQf{覊o^oo\rOr盆F4繞?8 堅EgE ;~}籖/驫幕?6t_/鯔Y.尚M_w'| l9w誦'O*L寐侠Dse \\kW_}|p6〈p7?9w2k~ ?]kG 磐$亳 闡歩@鞋 J 駘us <48"ws/驢?LO碪}U諧}襷Id?|CH>KyNyee輟q}#mR忍朶Kw^v!>C;r迴碼b麋hL0^Z想w葬煌z;)駟*/q彎 gU髀q:樽~jBh暘巖zN*鯏Ht黨u_)x咫N妨遇{9xH穩// 韲煎侃.dp:9酊<w.lr 2mYG3塞H謾溽3摺\>kkRXH} ^朮*ztsq%I樗"燧.勿梳*y濂$O衙H~& jzJ35EM#J',^}詬惑KF弋^h歩徙$榾x*|qI% 漉K6In|h 單\竊=hc)_SQN陶墨_l|lcuf欒鳫C<冠+7~wGЭ G9u:==*8 鯑q,a],! T8'+NbKt8u{sxa ^{uk^~7tw|a=]]=]wt?N夾!u&穐'酌8F撰]昌w]嫣寢`&算"<磔.]kB搖OKc7国_cl!S k%RstMF山>$P}J&皹zWCt@_m中/鋤_d嘱頑CvM_VJ(〃{咤V)鰯 K49~]=*臓ho 鰌(Fy ilxD痢Z;R')11ba*"P杣%aIE7飛y3\篷 B(& 6[戒 }9$峠Q4ZN|PH/楞R-?P0X蕩 W%U窃#cVT&y6,w  -0ih @G< bw(#1E8 Ey)AH 嶐.x貽**H値!2窩錨+2\3D1P3j9aー$  n，o祢c4p韋R10AC笈&??O\CB~柄V礫'D5$4b`2C6K79B吟`R0Xt;攣Cz8.L印q"撓1cBL&jN飴xWW忌 Ir;Pqそ;Ju綣缸@#吏l2wJ!VB~Xa}Vg8i-O@^maV"ｴg d梶Jt:<wu亮1V袍<'`V3緕SQowh\xJly^羌n 芰eNP覃模瑟_EH夾0!BpL[萵tH+謁%H_XXGb(-NoU濔|MzU"e1N蟶\dDp}F#譖賑z&n#y2"0d[w┐自畍癪髞瓊iQ量w野U$n 牝7/?声HO1e潔Rf鰹l套x寔盖 个rf周仔@姜c圈圃孜fk: (LR{|&慯s;lﾗFV娑v潘%T;鼈 ;隙!vl&>柵M ]FQw+k^O9UMa`+kv4y栲9di*.LQ逝;

VWl3_艙　R檜,G合滄jI)履叭戟Z懊yLJu ['意葵VhO#撼局)I懍`2 XY%[[噫Ez&k燒R鷯mI~羅cs)+:蛋2mH沖=RU(妛'fC-ff|xOa薩l\>t%NR惧:{謚9/Bo }:\a}NIVQbUV限R)]xaze椈淘粛qZ%^０){ 杞 XXf*O79g p撫^g buh(+H}aOM阜;棋倚少T况格&`YF?峭竸b脛+g\G_/^20~]][珸o]挺珊|M~Vs芫#~RoT>~u+o8^斑俳輛X.ei*!UC0c2AN$az+i6^ズ奸LR洞S$\:G!oT5排JTFOYV)?~+d`p'm皰;WV浣陶6JC,:)S ?T(Rzs\ G4_ ^≪ }^GG`PmpuR~ 義RP PH?r/5蠹3姫墟ze|-Hi腥N|Y4eXV 蜿ysoMD{16M$Eg7 [DoBc^ #逮`UXL7ioKOG荊鈎壷Y憬裼#O謐 &凭}nK怡_==Gk:5撃V'z/KT<9K;$Lcszv.達ﾛ>#w+p #;78B>x它摯=rj蚫V<挫)1体v4|V]i-59t?n^h1拾t%梃O2bZ軸Cwi*;鼠FKjaa'D懷(w*O :U*,"& h/i;R24#WRH郤|l90w鰯<#b%罘翕*Q翔VMKGEOb6+M授]scE(%q譖n9q0=n XD拷$E突&Mぃ堀Bz弸j篶g駈sNO跫;m嘸蕁豆K>2]rl闍{v]k[]g建Krf轤m /d鯖GG `BDRD岔>lu>w 0%J皆4R~a漣1s進э0r5#W)vX. 徐6!5跖yJH閻O =X 蕾默? iO1T*6TJG&{OX~TVU;`袷|QH$寳8Vr搓qY沈}黏Nyx:靼[;n>版B.`*1/"w=D平 Jfe 奚gm'NiхFwCrU9^能0 <$;踴x`%g H(劍轉kC^ykD;6樸O&Y仞Go^Y3r蝮X擯鳴50H &!傴ｘDz yOBjz合Mi"m}摎d}b9W弸B \d&S^并NW袮h*惷<\|N!Bf 7*魄DAf= W "P36PR竰y71談ecT虚勺舒 G*X@Skj '1駄>2>" 鋩{<{闔},OXJ愉壥史2袤Nｽ&#P竡腱“趨kk楙oW[;:~?>a焚eKJO 5９;s  c5s毆Lw:~鯨=o=拵肚>q窿[X#'@pK,Kp t )  (秡弍GQa\1:R會"GI-勿1罰WaC3oA}e{I@(情{Ruh縦I%|c:g#cE夫)識 9cd:#4 G )耶we棊dw~c"5!搏DE?q= 礫Z渮c夏&XC[ER``^/憲2L$J椏曇p>]}矧TgR + p+'洋r>8ｪId柢rDiO茵gm4?0 ,薜{_匙4CX2ywrd}y甬%?9嬰`淳副n3MHs`?I7s葎k3鴿H此齏Y6N6u侮cg%byS-K\deSRS|  qU'箇聊]rX#摺衾-佻kb3Qd`抻w澡.<7富rm fｇ 栄]`M7dY花羽G;_2G zmS諛~IYv:@]C3■O<> 73$雌LU&ONLn|r鰥 [  翕;鷽`X鷂蒋i"刺D0EE8Y|{駸 r8$  .DTROpsYzL齡O?z呰|.dOヶU37櫞B矜g擦KDDb,<5貞潜硼裙DrD\ Z8曝3H%p\貯`^WH(^}鶺?曵aR:J幀)Z驪!a^SJ覲?譲bG}{夲h& GbMw晉鍬G筌wo溘& xZ/: G2< L}9S5%姨c齏*HI女粤Y[6OC矯z^記lWx<薹j貿瓲07@H%"HNxcF硴藻i屡縊匪(砿契r_Mu盂0%JHO精t#`"F濘畩w2TL藕X時訂恂x=G帽yZ遘*xy;<q稀＜{\Sh輯 咋x-bO_ Б[*HJlrS3gdxb聰y)} 墺U>46euu3汲尢XkS飆燕=Yy;T35;cRz頷蘖0|]z經苙E|爾&-桷rgC3y`Yb麓T2D+`2:vR$HHE$zgWi"[E}?G]>糺@H/PgP5[AaB定*cq&4Y4k0:#'k MF7鬧k$/椚jBaf[g撼xO`?議,O-<"\ /EyaqK-壥1f0Ib#mr`椰sw_e/Qjd&~lI\r畉nu^*He 槫塁"-ke$vhXYl淇~874Lc賦nD黽瞠侑冩4e略g審Bo>瞽х.{=G斫翠6yj繙鎬v襌QL9"♯┼e相'.D滌FYKUv $誑$+a付S-m-2Re<^p9D^V£(}l&F#ZzhCF訝0kAs%йV0f8!甦 G"mB槞 HC|羨>跫LT3dBz`w>L 9Yﾔb#Zu/WZRx 7;$: }:階! ~賜 g$b价?cbb |斬4活鯣.櫻T14W=L3R'<:P!彦O=1+@\#>u$綾▲$!軫0F J*音T{鎚H}.Dp凾mab?[`Y後kl瀧+XrO~Ch0`}凖},H0vI+W慂%y:Y+叱`ES#_#薑珊!7&\Af@5oY1F&Ki{Vｺ}翡綵vV襲~擘助胆6Y癈ru]axL.L4x佰*;3;h展7d発v麑枝"G` 巌fzdj Ksub=X駄aN 晨Sp0c嫁1!蹂NF qZYh_t鄒/3巳8?0Q j?聰,-C}25Xb1 蹉&\ ^6廉ド4Z8&O┣Yay;.\oN]睫sΑxq?轂$59fs ~狙EaI)=|.m Y`|衷$X硲B客QL \艾tL UJaR6奔2茫D,~DFc9x}蝗~jIS5Ed"r秋iVk闘o)!o,M7柄繩締G,%C Z(/Y繧FV法済Hx檸?濮X6 b0⊃|0賈6JX"s@菊6K2<TYqO 刷r{C]狎~7 xa@#矮0m^ K#Vb@/lBTA大ea&悵Hj!YYq>+-3閘莱4Q悌eZ}+褫下v_p QLA望=h%F`ｙZXPF Qx;}ur#zq8q/r YHDzr謹2pb'z,鮮c,s槿b奢Ml汕隗_wVv&i!j^y=0N虎OID('YDn%#\l-'2諢,m*y.>PFF~秩spWD.Fh#Z o缺逢!9Ok-EG.]FN姪j凌\Woxjm宥1 /i1lrz6!H5х_#Oc;k鷽W I離n5?2#5筥燬吟靠Kd40X唔l]0DM錻"hOalo@NoｶQ{CK.gFSf8|y& 1KUk絽40'膜Hﾏ盖p樽?}& .豊2{頻$ 扣#5b ┳duo)I)g*xu嫦}Gn=uzF]1~悔坩uRBV1糾糺Sy/v~|>賞.盂?,鳰K颱J21=l 鍍7/-K vO`絲VyIt壊eNCL^y撥 @0h|癧mdlj<1?nRB8dzねp娟vk_E郡\ Q9l!B銘凅qX紲檳K NCkO+UiU -[yeQ0{3UKШtTXR4况CzhｍMp紛陂発IN3-關C?~zr竸"@咯L""PVbR:zзho%S 套dBKWvBd 慝~}*N?:+$都1V._Xf浄尨謹q畭須%x &w橸磑iD咏?]}+^]^ZA^Ss聴W~~薈吟<Z -yEZA62*~ $*zVL芋GP; #5跪z'忿u '8Y y瀛xDDx8"芦/d*MZ鍋:蜩┗$GCYK0慧Bf,n[┘9v泯膂7%@.c餾Wo$_7vy}:&3VER-J痩粽&bz4\5NpvZIWWXjua羚( V[aE q,昜RR|(yF≒w-_6XL,:Fj唯20@`xQB)$-S>Ts(_#'FFR+延TB%Lj %2"mhWeＱ攘.їl錙g2%補M剿}R5nqO酢wT=P菘&bq}嵒iS恨#;HD麟~-ZS5!%bn+t5+b-ai=AD.y7Z6x啗鶲>_~)跳孃2*cRW_Z8k @n)&AJu籐RfrsI+qI1.+&NB'M`姶pD{N辰K>?穰+新AlL\vu峨r艤受1-穰Ｓp范[w矩U25O>鐚{=9>瀛4r.3％買 咨纏潯QZ+ 0A.x%j3 F(T存.-WCHS1se虔\~h-m8;~"}t#;|F摩P換1:Y苣D6K砺:騫蜍J熟@.延:"!R q}i&y6-:[$e Z>;/4跋庇q4_CWE。xsQKF=z*c@蛹= [- 採 FmOR'VeL)棲x卦h餡`X櫺aDB目<3蕚2?BbXgf湶O駻cW濛Ol2廓8葮/.浬較:6至?{颪艷/^EUgXx5f雄f-$:R贇b鵙 )`vH佶OD釡 4pFa 0$9"<@浅D[<+jIf#t5!2L{\w穰襷/Ss'捲X渝勦>;k2:志z!DFL*`h\UsE@h脛\(e鴎eO]隹pC,qaL@*淀.蜚sz借彙C}_,HTMVXqty~7 pu^銘^u奏Ple"_&-〕 ]5lys%遭劉OI3g.vくJM,x~Q;3u味YQM1v・Rw$b`"S%D_T(緞kT9THdjJXDcZZ ":'淫Upct&榊 FBkJC谺>QLPT漢$z2BP<_FyL,'B喞mN() pEqe/~e35vUz孰bae 索=V妃j"? SV辭| >洲b7e$! CJ96柆v閂藷瑪?蚕P昿@;.髵I#迭:s53S6(](e[k冪 Ax'衿k#p(z栩A]磽cbxvdz;)f朧]ot7D英,@})YJC&Re:^忱#vC e[濡=PIdO^v;)Ef錯譚A""Eg41\j0炭T厩qc<H 5旙'A!Aj0"N%.c 悶癜}3yzT;`或 bN3.X1}P2"eP+r61PU3r}楙R蛋rB懇4z:Vra_3VFfｕp┐G\&?k洋@{料瀉a額z1^V4ZjAK  JFxlrU錬| u謌O?FVe4/k$UW(XA>3_s4$`uJ;>Kutか Ie:Ycq]E,tA<4;D縷xq艤E -~D攀#'?!Zy==?;蓿<\6qI樶+kW耙Q-*i篆b- b山罟J犖k楝o洙Ba,=Fv 綰hkE/)3rx;')&'z&NKXtbj]*8R yHWM 心C7#d"/I}恬りmEVQ[.Q佃x|0*滴qiWjD9髮Muqe*7巒+l zK繚ZU⊆t@疫^@u8Et里O01x6]攫+M絽E5WxcFd:Q-^|nBg(虍綜 c寇鎗WyO碗m7|7R-d"#D瑳Bik"/艶DJN=O]$3sq韓B垪8借{])XF$LI緜&^[]liHMD;O16r8Y),,!kQ,(9]5h"）j9肋vYd蔡9弆*dJvvou!|Tx1WVJkb(u蹴'O*z餉\yJ採m7"_N[moU6dsh9PVkqI$殫vE^" F祇c娥J8楓KBRa/6=睨E$G}F a~5@6y淅2)f)JEbOiQ:",GNkT85ZwUE;BY腥@ＥE sAQCVF3S/б .m與 髀`5 a?塰疝8i^hXV@VJ轟@N,Z 爍iJ 代Kn夢3>{h4!=89vR薪U n8たjs7┬2S娵R共繿^VLs ,椽\=1V+iL8f ut4"{助躯{Ld1QGwf柝8]l*%C$tm|u絖Y&;\n&團{{倔EZ注 8B bD飮p-#*FZL絹;hs9c木" 軼`u$(< M9_箪IRrPV意P[;N@KE19W@>!/[9u衷1y'd33R< :yK2HjXZf6IZ:e8%殆*?蟋gy:KH^X0呶 =L%Q 4X" 8ﾖ霹!ON儿;ph実匝NAdaiQ鳩D@[d 3/埜 [{$v^B⊂WDu}N晒pm<q%N岷L}j #iz+khΛ`zSb- : f社m/'j2靦敕%r居h$Apm圸q.cBu1ecJ e;!*r9糾8 愧xrzSH獲e湾A{[5*0?An劭UcWh. b`p1:"P+a"E^=B* }SJ2*d8阮 "Gv8ypPaq!O股C-e)\Pq~w*hbR邸pcv2冉R汪 I> )O,閥wdFn #F45YH$n WJuFd;7jcZnL痰e7Y'pW(m +OUbT*嚏=-* Gg7Mz:娥FD-N{o実iTjzHw.srｹO"峩@C陶D%P+gy W2&#JPWpO閔@uhのYA8y~Cl+qE徽袷zUCU[vU臧j,t咎d,,SY& T价 /zhEC港0%z>peEEg.G`!nC)鯡x/H恠Fp~Q E兼d斤m9g22}N68kc.OmwSepd4O綟杤wR5c x_7 掵 暘12武般9Ｑ tぷ'Ub樸\@疇(x(O3.#乎l!b-=8^z5oCY#y投eｧ1k幹QCJ隨鮒;< z鵤E悦a/Yn國mQwOWWDD1!s)zo5%~J姆x茸鯣;\3-jL誠z 1Ｆ\`J`彙+縺ぼi]i鬆',K:x誇gR異*PR5JQ6yz)O厘胥#,U[wH=yzi9j}-n&u'a& W eg|/掉駈k估彈^H&呀嗟m=p|曚膳]引R~緜*aYgntT邇zR;-Dt$營!x騰T!1q9サ卵sf樂庁ｸ[[槭vuy=}K&cv?'佰}Z5Oe@#/>維Jq8rE{x$枹;>嶮ms薊蠶 嵶<**R)9倥C,t臻t|?w+Fsｐ01鴣(4J適=韲r,o@ jTkbnCEU/ W@:I1EGtxEU=~ HR9_%:8 &8葹 ~>_<深慍  $~*7郁k矼2\S稽+fH洩ZM8X存" 7Cm×Y@k]Zmf^GD(旬j"{髟| IdjHp7>i{晢O]~u黠o蓿迺6\ "a&%?`鋳M]tー6L 7^lO{[g._嫩&Q "h 踞r席$8fC>V _錨Y`n檠b炯鈩.*gF^V戞|VtkASap.濕峇Jb_ K[3t L:!ゝ8V<瓜澹秤]"~`?2L@ ?1:L: `wr3LAA/NほhJew7~D7jH４879D2)8gM稾fP-S}].鐸痿Y趬(5NM5魍 湯}V`脊覇k%#旙(n裃 `-m <鼕/brKOrゃk已/ ／_Ex Vn+稈} k:ej梺5<&R4~)OP=@~ e勹菷_y繩:,拷悼_説慇_p/=}"arW剞5oON/?=;}IU>除,) :nl% 3 '! R \UEVUP `=W妲b分 jζ; %BZ頻!wH'｢]徭F-%Y-x>kk奘dx寂nDIwG|G  rqO禿{*位8.q3Z% eif6Yb?hk\X 593.Ew橢y`QY罨觜@%C*?屮FnBvp<堂V琿臉鵜K& jE)@%AL4`b?]Л^?rx1U竟$ TLZ?FPX:/2t7|&軒%[I Z^R@枸yё+xV/d龠g d:RI/ "In{IQ}W罪截摩\;}濡,?)GX!$礫.G<@t2号錚]U?TG1hlY1%!侵O饗t*W//j Y順]'筈ES4k)6SGQ听饒躾5B<ヅ誣倬J7q k?6$匂 r∬ XX蕷FE& m＊rz#+ulD'?但^柝VvF1 QA3)@0Cb(I 崇#F#8c/mHT* 浤^*8b*M齢laeu[CK>b4昔.V6ZqtA;T1即(彳F?q* be尊A.TfL6N价Y1^?Mf-Y,Rt-歃G凵JX8#J uH,避-J'+}7uuF祟RQ 椽yH>l;Xkwu.V販浮 '+"xSn:ul懆Hi6I\`E羯yuJ 6黨~3vX\訣迴閖兼瑟住jH乗}U{$;D^殖ズr>"^QO`M@(M>Kk/g@0d:tR7lV爬T芙5bHva}6nR/h0B衂Y菖卒yWK,PLfJG@$ H 嘖G芯∽撹q r(Pv依H /wr夙巛"ﾉ,( 7衿復s孅+c$"x%M;谷"]n軋5WZ袿飫;sQj9`.<7_ h8/U吠Qqg%韓Z絏GBK讖9W ) ::甼mSY疫Sj3Ｓ噪UAalsMI80|zy+5Q]ｗt9V?R3;0sVfi-啣E書rp扇&FRS%室c"W;國盂)XB蜴づ蒼D伯盾rm帰R 瘠u甲p^s^8lZeyc.hWyD 1's羂oR+ｔu3Tkb5XWV B睿PE擯FT ]2\*BeA+RJU$UK*!O 撃2ED+?胛 Va-eS,J*TN賞ユiN&昨Pu 里XVB8B2nOa?e|x<|+! 碁~戝璧.\E>$&鴒lA[{$鏗O澪g逶批 渊a8s}篷M|C牌製J#'驀t8動BQfQ@m ]"EfVv7I!驗@T乏$K6*l⌒q拒#h陏($$默Yca)Zv d髄 noW矍匂OkD麼匝w Uj_9.6Wi幀 R,5c(L*t7駟{嗚wo孳奎[(ぜ・N]>M}?2蒲V 慌O$r 陶D64檢O.1Y8{#) XYxGt;|旱5Zgl".dmKp}&^Uu澹/歇烟孚%哲Hl漣8"[nZ<.Vro財W8y-^~IX沢cK'c艫t>X6=6/aT\[O 盧市Bedｎs祇別恆 kELkd$ltw$(9M{X l6XBG:GV5\(KLZ糘& 嫉k鐇羣DJu/澀愀蠹jS_(\Y,s;PRV;'DpC3NAc/ 莫uz檐]*4±N 崎o}弛!&oZ1QV*CD釋受隷`%Yo築[耕1b析}n~t.(,/ k遮ip,3湶_笛>WtosCRCo樢"^ WT?K'K+3$CVa珍逍 &s\尭~i-*ヾZkW!Xk♭ 剪Rl>7aM脊J篳PJoZB7獸8}1;A5bt濆`=槎酔4 t畑Ko釟9^G技鏑 像薦tWZｉ曳:gS0c_rQ]f+] 防JNb7媽F/T zS@BZ (@#R４Y兮Y,@@jkv6J鍛h襖YBe瓶脆‘X5Rb-@r'0nW [ぬ fYt d{1}眈e$')?bt/`甲C::Q#'篋a&r0餞j鞨Ol(鵺u$[8誂Rｩ等hf[1B :b燕;g$sとE\N|jbVG 羞k?4 類` 今/u\c箝J5嗽此myDdu 計犠}9_N稽NEW4D!/宙XcB.M(M夫收J崙^% )_@@鶫1儱8?r06)千2宝篥C05?Fq9-Oz`[^+y恫Rxv_}XC酳QTDe2DG\@y 9IxN1dlOY2yy0SC|緤吏`uXtm@h&i韮迦|2008L#徼JEQ Ux;KFMvzBMJ/P#帑f12l埴哀QWl戻症G3XSPQM瞽|+睹c品Z`HB甫%[A忸j泙*~~~hh% N}|tb耘RE)S#R 勤凾緜qu態&MF\欧A08]>De`H^: ス=)ｵ3^7;趨5褌齷RZ H069&!:JJ|wuW=j櫺4n]狷Pi囘o躱hlBj>g塁hv測移５ !_Z3nMSRDfsskX屍W|疫&zMxcM$釟G&惡Z侫MBPr#W DG京.'G iL"NY(R觸v\fA而淹 a86)C,cRqd餽b唖%'G>B知nRi(5>K1 +N(7LcG3wO髮dD~W#2SLl2殫蝟r$##0孅\_Q櫞5d-E( $b&^G l`m8;( 蒜L\;拿qsbc|Fq&o_郵/砌漉簾[:1V L嵎葬z1ZE E[f拝KWsN楴奪;/_|Hqu袒;*L\z蘰編5.9{FZ非9,z~Xzi8[.~<{v,?.75L備疸>QHL@C莱W JQ枢kX?V郢+^怒)\{k脳x窩_i褒:xJt貲V3９*&雛F(x1jy餉?m>it FvfyPv1}$xX覡U>:uセk蘢 t遇:禾1Mz<43T1"w跋軆jn\}nX,="S波l^据侍5]::ciI=i|i瞶萩go瞠&)AU樺鵯芟/\?1"-bEU2|w4Q'軍P}bS6>UHlP]忘TmKz!UICQQ|#UV嗄e#@d C喫F Jji)D> Ks(ARSerz8 [U9[#(,"O$4n罩哀Ql (oa, bI4}{y冑<BNds2}T黷x;覲_=s">ラ霆$>K笛L'囁1$菴RF[邁9o$xE;v閊勿酢嵳.\弸杰n蕉凾很振)鑛啜]%,As墻婢9酵V&\7IUtD9xi}m28G罅SvID 6X重x5茨凩^}_&ｉa怖q驥qMA;甃5yj`X形=雪gfﾆKxjd誣戟71 盛K邇愕w_Fr,yO/rd塲P抄ozR[_ｧ鷯"j^薺Gta岾TD拠茹,"yZ患x4]3}fAT 迥;垰z盞er O4M"鮪E}喜p恷#uG蛞栩M67IY-p蛎味持]逍o濺w.X瘢JcY4Oo犯k雲%/]s+腆`9箴N5'DXlq衡wtPsv5方SaE;℃7淵WQ(`.f&#Q閊ywn|淹/z珱償E喉ﾆ蟇 S&Tb档Iv`<逮鯱ﾇo濕Le+%9{w7w[ 駛$)  LD[BV9[g瘧8戰ux*-5x +Iw癡Nyp醤C+禾LIm燗攵cn塀RB6俯{n錬wV(alX=H&zGyV6)9R- JOjVk<|:(C4M9Ao産>Z_侶4SLjXB4京?@G豌 z9現['!]背 R6 v3%}-1Ｘ pMld規mAg掬児瀋7/場dV汁鰕8'蹔 ◆p-沒%2\ﾇ{囓O!x:鸛-|/.Wpm謨髫3Q{avmg歙sd](僉#Xm 謾杪_D5[IXE7蒲nWFVt u搦豸X\~Dnz}彪驃'g]}束僮?a}迪R% DB +**縲弊Uc".9,釼7癢cc槙 `rvd q9WV ' OI鵐碗):9247bsvkj；Bb'海:159^r狭i秘9)) '(Kz愕梍18l r0cT,嬶Y詩`uQuKuL~@#p'E副8z^,22z%L7磆A12Wf}綫SEI9sy關蝟Nk 鵺,%'Yp-U;:r:fUmp&4c兎?2>j儼w?G}e倔VuJ討5 L)(LCS*y?遖a6F/^0e鞫]gH.yBL|t蒲>.n^~oq@弘社шW`】g}b弟i變]穩sDY8d#=1!楜&LBF［L-v]0恨&>谺峪\ x-XY:hfo.;羌=6sn褝y]碆J/@\#B`w|!rA be2 *1鬥S>#I囹檢4`W賢1 "Q(鎔/C7> ${L_'涼+?-ﾉB糞牒&pt,y0鮖鷄鍜`rs%M 9+лc"碓 c)P~wm5xia繞au3 (8劾ozd昨Gm; Ｔ9ｴ6=RCu@普ﾅ喋o :"墟赴X匍DCthj >喀a9g2%a$屬e[@~諳策栞?E9e堺 j5p)墓碍itf餠@5I*>a&}XA' 樋|剿di`f^?Y;k8Wk7賂SYx外}菓]Pqｃ\? b眈U 纈0諛|W F: 潦7f` `RI52g聹%菫<疾exT~c胙O瀕0e犠;g-I迅//抑{窩+嘸'rO~av.(!."aO>i陟HQp-^P懇k#}@uw瞠?W~ zWO漾` V+o対@gq*pDa/RG$p{L鴬Y.* 捉∃u予炸nQ檢)郊姥\l的oJR=?:8r$褂W鱚o汪d vW,;[:篭 `jDX : u"No呻6s;)痣椹Y怫`轄槓&3 9V豌壊}WX9罕RyW#丿搴оz_銀7F筝@.ゐG+~仰mい4T鬫xu_{g[A!xX"1[p-窗f{($}LZl$coxXt在u`饅 衽鯤 l}eC描H況ge6GH"A蝓,L.DJmPZ| F妝vｌRn氈#粲I!+r民XGw鴾;crh5L ~%|se拂-疏Ρ,炮Cセp YMgぼ T敘VK9H砂k'ww =wDv?}誚窺逡yH蓿IGY${シ4vmu?RZVo樊4Y瑰V7:D鯀pUJaz{`g謙khH/ I椿ズ模Q&_L2#>nU:NX淬(sS.Ya嶽BUkf j3uc惡%Zkic掻Yb:雍x楠$*_W:v9〇ｩ:ySDwﾉ孰{怡!牌=ｬ#F^x奠;y&,朦p!^?飢tF與 vHX図sＰ充 做Iyx疥C D鐘z.1 X怐kd]hQs_懇NzwIF3A =蒲n|ECh恣Y@OcU禎@X鴉yKd繚pdf]3vpl蜜 6UZ桿[>秘B|rkm絋HD:\b偵sIr憙窺 rzM\杠l逝x＞24gB"儻f臓,%!<)Bx慯o4V曉誄朏党爿qﾅ6貊Wq娥)chV琿_vt8fkC;鮠0v邸@ 蕩B%sr3]W?濺a0l"bGlg<fSu Vk滸箴}.?T裕& nM dR-哄 愬~bV~[Y1v叢松}a&0x)蔑bC琥[N;O2cIX F'%*容ljJ;朞})jeD倹餽 \VＱyHc8怏FQl韵Zu昨 ]_d\- 亊ARt:p罔~f}t\YCB.*瀧X7smF拳t杜轉w圭M6G椦&iHqD}.7jvF朧_似愕閤]W1Xk¨]C怺贔q0iむa提1}鰔;蔑}ml肓w\ 椰$xJD$xKHnIwg~X7@z齡70掎殳m慵柞9z~3斟5乖6 +eulFt^y%I5t?| 嘔6V+/D}拊]tK1t]癬2sg-齎杣1igJ@49窃XW%Kc､59恋@~澪蝨喇x今オ[珥oHN副 _KyQS7tojP渡nｻ廓=7oy碌0猥a勃dKﾔNU/哺粥ri H]d<嬶昂>rpW@餌p'sq4擣q4z& q玻0|tk膠'r[>{磁 [A慷wi奥蚯P&CM菫w謔`V'm^|i< K^nC?IQMNhs j疎O慴ヘ;Nf冓-4fI灸 |WN &n槨Qa2`cｼ^[笊 n晃/} X: p9i8']誇"P:蒟 % n^WE{闃}紅Py| 繩5QtH慊5/|Y Q0<\.Of*M ~瀦K!dp$x?,U{賀．exarZ傚Lrr瓜_q K=LI|;弘@Б[c:3|ktA$D&H愚挟pZNk cΓ#ﾙ-7OM［ｙezB ,めH4Z2 ｝@$- f04員仍=壑rlv|#y∨MC /w&'!e;3sk穂LGWw胙"{wS'斧鍬験`_清)梺;%*nE|蚕Lm5Vt蹙M劔ユx]赱濯.\)排?}hjq7s&独鷸@|Bw他,_揆接,/< G鷙倬%@uEV_?C丶B紀Y"#2l Gt`g迴燬閑k;l}77&z-rG }zVf聢R/{mt撤cC輩_鉛[.\[rd楮~I :輔A|tN(菩ｆ欲:O基冲]/G済5溶υ7fho|<^倦JYN07覩係2餘bj }H ?LD托'*=ぐ５VZ顰頒=G#S9?q&Mn-g榊\rqa鞘7o3.\Fz}N抃lv-w-l}[\jK鋤4P乞9'R^&q爬pn_aW5]_JS0廣zR AM[.燉 Q+tk$m\z彩UBv|k:3}mvkTm辧=l紆,/:帑h 扇|+孤4[&況G_3欅i0`2P祥xb3鉐A9G@r朷Kc]=FxN 0.5tBw猗:s3mB2o3\! q}c^y*Wo_茜<匈m没菟`tax,{ebJ^鑢iXI乃;D;b3z#v賤路zM vl樓/VBs(D涿x-cB¢75冗St&澎h L%^d耨耙St氛&>箟Z $kiHXFgK倪9鄲Z>特#*鐶qK4}Z\|>/lR2\y;f聡佼$,Rs]q=X揉拯(jCJ厄J ^-Wsh蔓VPアV/vG:eR0MnqJ有獻J<稍J!梢 zD$Br dl\Iy`,)套冂;'w@T=┷卒Pv-Qs)JS/姓 " 儀im/9属>OR+SLZs;bM|ю(UNHk茗擾廈Z+Eq`ap/契fsxI唯fle/%X&+iUHS9w3n虧QG;oE坂 }v鎌??f亀 3N FgmOoD-瀾N腐＠J;M&;y` ?5m+>lqv/L'_:l1;庄cV~矯A+s.;ajc{cgL權}婀G!吹#躍阡錏O嶼Z虹嚊R|jq薬\.茶Oi;5>@Xqp續橙因滂駛y翅QB届麺_Y@MNS籏NNWf鯨@_.L,'C.Nz,怛Q]:殞bNL;u*MEk)+{az8x $05.&慴,xHRj).灌瀝/蒿8VR73I瓸T2j&Q{ab[[\k瑤9邇 `$hO!%C $澪8eM.I魂 _NAZDa碗B勹s裄 JE~乾覊冤xp~A$- d1 t7弑t8"&駈BL踪gK9J"&i改~ `k|渋點|Hrl默0［.$Ym2hZPlhBtrV3_繁!+<.wFOG =TLp=-ソ %B続葭n轎]钁櫁]6!Y 蠹毟L.L俵9淕4否]}鰥砦恊＾g-c1蟪A菠#針釦0|_幃加o@1,k'Β{椏rrWSJ逅f$n-洳WFYDJ芽坐`4j}摯%\r0丗gMJ淆淙ヲ0舫ボ(ヶ K拠|Q繩aﾜrY\V3z@nRQeUW 登.?,,Rn9/y蹐 7c&k胃uD|4!@qJydt臺{k0>1O"TH"f{7EaoZNt 跖4iZ. >E|rqJFn,/TADu咾s]!ね/z&60('b9rR>ΛF 1x10J竇|-ED們j$8PGi\(嬶do蚌^L僩*罌tn;w<\]-杤w氈]椨+p"6E?E@覇C劫4X哽vPGZ貌斎.t釛里巡670C<戒Sv扞4OL陶y&[|2_d>v蕃祀鰹-陸[拯A`I8疾AMk\6\綺u8HH s+95(0X^2z`1/Q犀jZgh厳V1 o1N FwLnLnP;$VI_靼r q戈T6X(ST鯢@?徴\U "Dld剪WS}9,Iv旻△ho$N 9"UGJYgM A辷xY$啼`=A@P2=3 董&!/u/t)≡K\z-4bchZ_/Wu{.BEU観 FJsF+NQjj6閏f?'tcb,F\ 'C 汞}≠bM捐簇z-Bc+、Z21VlM xg : vO,{_蟆52@瀾 [ﾔ機q%m`I観}4ΔMxtEPQ@(**RBギZ@.}PDi〇 6,*]"9d/udQ!謄|K^茗*E6hpaR 饕'2apqKi+|E∴!a*獺 X4 壯jHN拭c総ZajI4括.B<8Q 8@(v殀\壞酩S{Cr慕;hI5專%nNy2n~8 } 懷=n{K'ピ'_*腥 葯 岌晢僉V'iP5uABNK鑷W>2鉄倩|悋SvbH\by遂-iТgｕ7i縡丐8%戴`咯TGn\tAPARuM鄙\ Yz4&櫞@-URlb94褞AhQflッ犬%浹V帳亘雋kG"_褫eT壯酩G腺Q狢L尭 in'[(N:%淵wEkθp巳k *wQ8i暉pa}g寓=3>Hg=1{Pb RcI%}fp'hkqrbhu7\*tLMpe監GJccXGF{1$霾h t:kvmY)=Fu! a-}&':$R!淒Aawm /&H翡PT>avG#,(X樂稜X1偸n@獵舌v｀羅Fa*UE>;?d奐x;:/z+d=WZ45(+坤xRP.6E)參H淞Zl Z^d鑵窈週殀嗚邸胸X裡 DQUbFQご刔3Rn9c?ﾂi+/W(..F[`T埒W,厠疏I[B2h<6QCZ_lfL費[U夬KZ.pI+8*f鍠勸0, 慎#urr(莉>7款黌/n)磊Jn()肚9Lm餞rrVB鉄P垳r9夭`!@ 正3)IU^5s B f桙`m誥Ёe蠹8^A-.+I>!|r甘+bI簪fT4UX@W╋>Bz$U鵐w|VC^Nv乙/儕BF=Z綣u E(Pr4< $]c=?-z.C[,3G :jv,cA0$0yR.F&FON /,:%7F衾&4悖 :LW?:io和っm';tS用Q析C翊AZ>Dz 7+w蝗M 炸]FEve<&0f/(p *k ?Bcc?3 =5u4y抵&Rr /+r4xXX7 v'EEHHvn.;乖J|. k0GA{)G2P~鰻/dJ賭q4*溺]8琶常弄Mlv(ODD觝/PZy4j|*IiN D:$pH,^りO\矮Wd/7$/а}E D5♯r'p¨jUMXy.翊録Y釐(@セ蒡v剿轆uD璃8^IV乞7.K;()b9I@k@!:!W勧}^q>>:'fU`q:;蛾ri粍"_8&"Z|}赴^$xa} p埋|轅tEm■c掻I樛}藁AV迥?拆Ig副1KC {訥+岶9h5}抗 >乳a.XIyYg ♭鄙|B s?罔|鰹\@7F[r J畸\b\~苒*Me R/'99pW_3L~~8E`!h-QwrSQO`ぴN9x@T墻盤襁-wI擠攤>鋪ワ)WTY蒋vb雍勅sm癈 l淫諞/i [_惡9 x$鎗ON>{部53}Z| 括?塗9吉`x魚}狄9XR票p>櫃_|(^策n,IQFXlz洙x掵VInr假lEsPvO控"f!Eg%6R7]*志帝'瑚5卩+W'#墓u+~ X乗Ig[mlbzx蠍O破GyEMr{閊WwVT蜑Zz/刷8 +k>-7.CD]^r8♯q'%Ux戰B+&RuN8D憑蟇x~wo?ふ:#d 3)Miqd*w齎XO9樸 罫эs##*G:80K!!w瘠@[WQ^m裝太f$05]封;a!PGXq勗廐 S ]儖t像x^Bdq$"2l-Iv*/r[foi奥I蛋OGa a~?Q #1迚hED妁E^+n}閃 斯)E. oJ8[TY謇X6aA/tHＲS+J_;G%w,:)5i動Ha$JDi:鷺^蔔i.% X?+勣J9卯支 wAQW?j(:%鑽j 膳w?7藕b {C>.fJb #2VW/s X$鍮WU#")dVq7`EfAyV[&#mmND葫v曚濟=qa絹;彝=忖梺(hn橸D1侯\醪兆G')z~wnbV会Q P3 " b''乾QYyXG'B鮃羌G拶FS5o紂凭-QW{Oc5\:tKo }ca疽KrE\~貶/袮BXP脈^ h!y+f [-MG_g撻p]HRV(R剄vNnz g沁禾鮴Vl|}4Q>N鴇%騒驟i|gk綢 :]qrB@搭袈;U(uj >40'*a =ua&Y澂%qD+OS\]瞞鯛X瓧q` /ro<云9[^嬉９9*f鏃z"W“EKDwJ!W- UCp>{qE ~vU-/u 4L*`n)]N:l'/)mxi5" VOD<囮釟lq^: z1+y/葺aiTF7 椏R%埖$R(プ~qqoｴO.9KP丁R9虜i F5&L(jTGK鈑L0&羂旁OdRis6X?:c払r 夢 ^ (制n 芻廱zb-X%_v"!褌栃`{{?mW喙s皰虻=+/^x6M{xh\T奬cI^Iu6%舐1t6糶X]驪Th鎭qv稟2/a/%o<(B禦2bMfdWc*O5騰w hl. 順Mbk!gG0x*_KRc[A`蔀峺鰥>窩9>埣lZo'hxN淞H(旻xr21gat&"C*'h;3 M.zRJFZ,sP7粳#殿&r@ YB赫#yR( YV#A業柚 }`D逐UL.aSbTjlP<$偬Р/跚*Y緊釐擽s?mpswio7;Y-wo曚y"闇Phx|@k wJvc蕣t8缶碁-肄寇Pd嫐@  clO'剩arLl{ue萄彈H 3|\oNB峇2}} 鞣qWT$![~9`"yFPqcN)ClSS*X6mF4")哭]zVyd_т._F佐t'k齔V辞rd}|yS琉x# B*Ez弩Vj"u0`E0!aZ兒R qt獄U$B2uTu2貮.陳懿8y_ぢt^]e囹;秋簪斡爿C誕[梗_C",CNx聚a3 f疊AE$凾箆0婁籌.hN /o)9豆拯h;6劣蛆c6b5x>塾"~彩窺N捗s蘊,'h卷o趣J杞ルw狼訃#ＰT碧.^蕪C cMb3卞OauF 6_<滲brd~皎g量紜-B^Q"ｘ評Вxb&jy軻B 燻)♭>& 霆凌薗bQJ:5)凌N{41QJb^/:6}8P97KT)z:j5|顏E糴EJjRWE*k壞}2Q|Zhz稈9!O雎aHq6Di'j疋穉%z9 篤8 ce0&$9P9_;R款4'D6[7IJ 1享崚2藺,%Qkr=gxlX2eM4抱x翼kiI"L,>%飢PQf胼b'籔DwrO$鳥Q^比vY迪=榛Fp~)ワqU [炮$B`e .FxRL2^請漲{=Gys",ﾗop~uP童xlv\y[l  "幗叡b S`蛇ｬW$o1R;V]Q&"[?(@枌顳暘~飾 {9a荅`*H1uV蛻, Yo鍛w fn|Vq鶲 %/Tx d9p t傲};釛{漾iqWT4[e4-ZTDs 訓i綵咋腥告_6篩]e*葦 X<|9珞@d)ki6域V-喙装;Hs>sT/小鐘|￥6U>鰻4LWTsl朦" EA4畢/nnO゜*05uTv袱r;egKJ柤Nbi箪s俾/@j!U?}1$餠i7>aU&r!BKP裡Bxa拂xOm<+GDW*Ll-t寸 VGJLP!L-Bf^ IsT鰉Fsf%s7祟&柔}邯zgY疹hyKgW WTXP蟐9-1y麭x轌k鷽$28^oP |疂2"Y,M P.鷲LU7UN/%$v鰹-彭習 {u?咥q!\誹?^t jl=Pk`Nd\`Pa;DW潺 'nM-6 +赦{Ac1%倏:Vp髱o蠻3垰d鼡'`線 便3ue誨{i?°$V]I1鴆駑E磆踉}0V=u禁7co╂L諺hsN抑\7uDj',ぃ黍yt尚Ar,,Y|Y<05C)瓰CH6HTd+_i ,ぜ7蝠燧EUa蓊q,z9JlC"嶋癡aZ晒鸛@?8典惘'(T#彳1Y,仰+^&LトhDnZ#g-妁;~-e9飆靜訪J[筏vbF 1\c*F爬FT7'/Y恪K+ZD吸{=q;qq\R|,Z'$与杙'(液bbk-Yl3IP9燎0 Nrfz|ｳ7%kNyumA190s1yBp3o_條;♪饉Z薗K疹xh剛gN,HnQ q <+~@ h>NPp<[zpgL甘BL&y宿$r9%でv4k堝9iCmBIZ|Saa侍狐be<hA $碼9梯摎6Lz_zK 優F#揩\N'yjx冊>^f絲zs稠@B癒2hSH b飜桔>4Y3坂ML9$!n19hg滿`ob-6&Q妄Jズk岸2eu蹴rAs褻5逢PS)マz臾+築lp|祐[:}穹wAGQ~埔姙{3h_tp]/2e^$豸{>跌x?梭Op輕vqIB弌Y=箸^!勧9J),rE邵C#JNX2Wydﾚo ^堕o乗)/[ }N_NG7sn/豺瀬o#孀 ;-箆兵[F蕾|=C:$m@))吃f\0 z2f濱 ]W:43鼓~oX陰UG=;2{u]6L韃EI'^/紡JZ]亨<Uw<慵GLr9$}9;d3<97 o汐|7ibXhA9(_慙9樟>7<K塢GＩdC"a鵈M諡乢越lヌ-紕6pS潼{i>]膕uC0odGO)#j#椀(3PU擁D\%菊 sZ1YSE4n3G1 LL4TZPfZT/~L9!V&JqPz`ut 0up蓿(湛声壤"Nc^q9bs-ld=+wF.6f 餡-*y芬1FXKuSO V^滞l肯i捷(Het(I汲!VET@WDO4>9'弛 Y N艮ngW:]JeQF$%o綴熬`,椣0%rmj氛5H8LJON花∞e:5W箱P嶽M\ k歳BFv^3Q06鉅.qCR\d %TlB"N`2 (Jsi薨d骭澤9od`株陷=a`#mFTЮ N=~[p|wNy-U7)PSitVbU|sq=w1+v[R1_i0塑ZWz V)Xv~4 tW+w儘;"fLmk5!Vd4,/C9#竦腿G%]e71z]3 1 7_僣& ` 6Zjaa騫`X&刈\6_:6 落^_仍3b2 RQueJ#z=_A,4DADiIxJ0It星剰@s#6&λ"螺貲qs罐喧# M./i h躁`Ype料l暇渕OY紊RC閭yvs捨==x"U攴鞋^JCZ恰8d恍yC篶}qm(^%oru鉾rj儺EU#RUsl)D!炉gKeg[z慰BgxWktF7 黎RHuAG諳b^瞋0宋>j )N<既lN#@悌'&&s ^8+Q+3rqsF氾* lL<廓&泄HF荊扣^kD柏%燎舷v!ﾁFu 甓."J#0.T<艫[.!812+$}bz`]bO,愴Z"t"9@<揮i?x"1{罷E睛l|u#ヾ 瑪7>_, l窘闘聖;wfg?'XqRy8| _u#fA畴}莽錠(xV\T竭.1%4v";尓誡7 F+善辭}玉=nLHTt^/"7BR>4b1B% R W/~畫#6tE/4_H0b#6F}鵠思和爾LrH4)!c尹'癩SI_捲靼;發竇輟AZHxH靦Q#_{絖fC!Qp;F蟲釀y7$v62q-fj 思袙蘚yP@侖E9L黄 "L璢,n喙rey紛-荼]y[k+C $Nn@c勳孀9 t&wN-Q<檄(E6AQVf想3^E~HA\iLi7j% 5go^{&+I7(9樮VB-詛2rxf#3Rl[+U!RN$`PYm*墳iX垠omrke=h_Jヱr9Lf!{辺$CAU+５軆;繍ALD蚌高.>])Ｗs^9XO\|HW"`>A濕=噤~MF2^仆+Y`7.PON渝 D澡/霸偲鰮舅]~oq翔芻逅*UD$6册vRA(m肥'lF傀vNF QT'>p輒A ^.z准`贐wD '/-[ o(d7JA'12Cl?K魄y^5RnDQiY )Rt,郡`VErQJc*I +OuIjin儉t=[O2i[ x姪[Y4n"B伝%咋嗤}T5,[FFXTH僭鋸Ksg ou}XMD稿t:o@{^檪3,[HipD>wA≠bS|咆A脈LP.S櫃V.5 J/p副L}e]qI`l0Il勍X气&oKMC鳶L屋)/{蓆PB\晏詆鍜t餒-%洛n竸hT pnU;<曇(gZ>;,6#&s<  _eZ/檐6uG`Y膓ﾄ1A頤\%\徒mK G%`句q呈`43-r髷鰮7濟0{Lzc oymAg-#@4M暗V-9┓~{7Wp畭)0v廡剏少u@禦,mV侭}w'ﾝ歃{註,W7 uT 9O@〆O\p啻}\|^)G9Nh戮 ]匆 SQt袗 _9pR賽QOp"H)探*C }隔 棗>鷸{Oz怯Rd加oI 訣?m炒氤n蚣G筬Et=温E'6妹螟DWljLu"Q}%d<瀲[|A,_lq_l `雜\QoO\ 巫堯L愈3jA嘛-8 :IQxsY圧AI_p`YQrAｏEWq鏺緤劭92I#/djﾙZKy0G?.|TQQQ@K)#1楠nm諷94~\卑>1史1錨魘t}UoLjAA1Ju,<@5m7E_Y'A\yhZ 1{8？Hr-9[@S%倔ieA"懼 NX::|發GI?渺 35HA&NLXfy畠SJ9AL 27|R +VKb鷭>jKmt5R$^r┬沿uq.竍神蠕Q崘"Lt*{DeFj;梺Ba]q皃#}勳q 証悃[惓料s重1'j蔦o-6oB忠>sH&久澆H|Oj恰杙AL*: 茹6冱y%n/罎1 ltw葷鋸簾-b-F侃6::勝' ЙЙ=RY.qY魑沙无VrkWQ亜4貊)hH>>必C sp祿7Kpl-剏鞭p轤=襤{FBz枚8岨Cs?J狷禾洋.娃+鵝Xy{0Jv]l#6p# C? NV8獵K站;.UfG4 M=hCK _"ET^)駢 _6)>EVpEl8x\to% ~j_ R稾鐔幺Y"p綢>3W1L5=3侯恰f"Y鐐Xs芟盜澹藪gA躍mVy|)aI 'n}悒uLNJ話a愿 0wN~=yI 塚p?PP H7J>#{[ZKr拓=椒 捫V*'&m9~h個2硼l;游u-}b dW 藾轤#S|d殷Y K.,S<痰38lo奮H_繼/-q*JtC牛+{K#b擴Fhy客JwJ鮹床/紊gv洸+鎰滑c#LJ DfNqx黽7 S湧L}'S>8冥L /雋p Z}$ 倭矇L:jSSy%mOUx剩 ｈ$i笊 髓1uB-=4x y,:8HU"z*F:U_沙UOｺ{} VaJ 諫;0z$怠SKl A`K'耄Z[bQ|$,8>W, #CY~恭 5AY4y'n\ 8fEXjXM~~~悶C0rZt婿]CKC妁" <@髫8nD ba'x姚$AU 邦O !2頁g^7- C$.\ yN/償勠WQ#( %(QQ}=m`'gミ'奚 U辷d鬆 邦cD68僅灌Ye B\MB顏1i卯O3XT諱1&FYf\SF#R(_O WqJ|M-~AnnKF "ZF W 椀8擾/N^&黝Lt/Mh 幽cBM驫)) g"椡Dw獵;K%7| LZD+%>骨sWS繩恆 B迴C挽wtJ珞稈= >x齶D,vnru-5Si%`QOWWDv->)<5+猫mDUz$.]k- 羮 GEc桎NrQ1li_eq胱'S鑒pK)v}餞f=mK ^{ i k:#}//＾@《υV楮瓜<Mq6fA篩FQ 受v}繿yV*{05T-Gqo j磽騎e溢Y.^]tKbw嵐^~MKc梭nv V鉚P2羂Xa|zBkcbY(0J洞ヴXx F0#mP疫97n8~=|匐H2Kj8Ξ?|cr3W撕1"F_X~F#q8B [/P怎y&'|/9{o蘿~azHX碪<狡<*t霊T呱O貳3.Xy磁O*5tgT>1=n:^5 `0dc{KV+席.瘧逶v輾}O`Ic4 eX39 BQTKNNM^>B7Aad`p^ CTｰNRuw釋澤雙{ t偃+顧<`"#8,ob "聘4I~(it+%I[-*SUpR3<yU仭bA-Fo6$"#~暴!{(肯3=%|fQ漾yyw興%k_o遲'K8%=頽mq@{`紆d芽l揉S敗KGf緤/]{7Yn4 $令5Ha$p)uI^v'豌fm <)[Pfj縋Yj"肘G^]至.et~]YW%@g卑Y促+<_餮3zk敷nYCStV'羸A'(E翰Ev`Rr?O 怙獄#ONG⊇Ly+&:bd殼jDFk[^潭;u'6 K\z[rf~L. 単)^O>}+#MCxh/Z}戛>GGWk鵺sg鹸張UAq]05KL休 @[7b'yRtがC>>4T,f2B{rU'@.まw:(<5l!Nxp曳+夙OH@ 稈2ayyjeJ遽yn傍_旬Tp9~找突周;#D媼wkmQ楼巷脅b蓙)u戚Pyia'納棔+W./簑C{ 0*bＣzY:sz釦28^#ZbEz*j 賽鑁E傀菩G戉h(U[oy'爪q~纜D頴5{ v産R*始釐Н2Wgot[l&v涓^uJ9*e錬&ごnK*飼F能 X'<馗c]OJ^v>5<[x督 /-/R!吸R~幼K襤z_bZ／VI}9鵆'DDrYo|Oj>x7,*/罪=jx=N瑙'Zｱ]F#aKpA/d8Kr=%I2y+科wPix ,KD簾3px|<崑j{p'@5^s(_AZ#,釵@x1{Y 6C$&x;榠^LzQpD :硲9H\ &iJ,V遭迅'ｪLfDZ&;%AmK艟> 編y虻ChKQ [Y2BDN,q蓿,堵 嶬P;"SxkgqFKHRJM毅UGsND7cL@f PdI|lﾄ$刪bD}jq XyM梗懺 n52a'?Fm烱岾噂迹rm蘚ｽ1E}i早dexA9q誤dCy侑W籠lc蜜 霆'倦a[滓JlH H>'鍵Гn !9c$.THBYR閔憔;uMt芍{WOI:n劃I2掣s$奸#YH9^uTRC拝=靱>=A ヴm毯n>p3,x~諤y楹母I;姮T抜JflWs=bF"sSJ )B6>&y4FQx";E槞mPB2r"素>C 0p2*# bA揃NtV&udy|rCWq]8Z,GS  0JDU1 OyL欟"沖┃S8懸会/qqy拷櫓M7L賊御刺R- LWv|%m|~~eNNgs(jza05y.i漱SYr5"pT$87@}_\hs誥sz:趨栞cN^慣q^/jy'o仮QwU楽鰾[zF[Xm眺w]%*/I広0HW栽e腐& .i8tQgv4S(AS3o}'\{8c!"r錏1xLc于T2\7'i趙]萸蝸XP4咎飛x R6 ]sAg;\t箙柏 (.?R*夙6c楪懣}埀dthmS`^r*UWv崔0.+~"<tbM(OdA獲Q!OK$0T90z査Fd鎚z0起&繕随M[驍h退."]u p,H畛烟M睾{1 倚kE/3L 垳(埜h粳,{=:-sjGF8F%`,4^戉cD=/*棊BZvr?HぁY(?uwu R4~Wk~鐸~|6/1R N ! VH 樟A6O<L襃($撚>%W}&嘖 =韻y幼70^缸2V澆|ASERxft紮z甫p識`Rw pUl'XQ~^z`琲貔栫m/腫d{'D!_m t J毘ボdsa`<^T凜LdC3FA%I<5@]Dz4d+CQE孟卩X3t> "孞% h8~BG肋 禧PLG7歪g档&Qf|5<→+Nx8L/[.#8x@a2TgK[tS|51X+AOeJ£Y~ pX C蘭7- >6uI&i]1\~U呟築\Ah魑G+∫蛆yWp1|h予<掠裔[p\#%=AU2,蔦恃⊥1d堋/q[;桂8!p折h7~vt紵Ott但竄vHT+ 'hX要B.OidEm%3Qk莇lyv鉄-uk)掘o2y RY├K彌 k6#$^Be縉8K糲h5--[=B菌~'C%?wLp磐uC函R|}d ]疇Q儂|4X格:b+g;J鶴r;胤猯ﾞ^价Y迪B`7#EqKg_X$勾晋4_貎bw稜J RU\r#&D9@HG{"a*L2# dc;r@B−偶砥6さt>u濟 b|g称R{許>觜- z u螢nWavm^ t {yWL&Q}!∇Pp!詈"wJOjgJ.w|I^PkkR6\i *仲0憐=SQn<莱FヒC-干h@wRフ#UKUe97R]J| T匸品${L=`igA4(GT ?+V啝j駑PE叙{{Nf{]C#e杵R攜lo^Z$4>I1胎6l2MO5(G!陲'+q 7局{0"$t處b]^ckg&T{yU{盞lO很f枚`n2嬖[返-ψ2搾}猯H6n處齶qHLNs'cJ$7C1pソ麪&w\壼er教 Q囈S Yy{hz}.j VV!鷏]$~E_>a:_衷4' ~hgoQ@> 郛(蓊帷$q淡津滯鵐,3ki馬HFM竝HR`S-Z| koΩ +5 T増1H`d~3&]waz"VC(7cN [R5"XF30"y9縦e^w6qiuX7xO霈2徨MGF*Ym@.~lR陳;,q澳ERjX> ~mD8K_L揮!Q舩\ Fi i({ #o(6->zUUD@ xcK*N_;時o1Iy~}kju6U祠糧r%dMi13\0.%u畫弗 W1g"台it髄*蔭vn~S8IwF8*P= t蒔Y址H 炸|B$z歎|M|咐C=2[m} zW逋T! [罪]<3察yyt {cnJ物9i=Jzz58盾 3L3.&Ri埀\&PK=噂qMH0)I=t(8 金衞  V(駟7會=+qヲAQg0 -A1簣]:鼡提+"U6Ws}90yI棚NBj3.[戞K_Qo青R籠] 酌舎(,gV+通te徐l(鍜..E!那m靫MD&@SA [G'@'4<3w#3=1w!Hj%8S[%}YTmqyFfnq暦姓Yto+g誰1d俤-髱葱4嘴僉<鏨y2&(_佗甕鱒kep!s,謌 (妙1T^P,ж+7~glY粥x+ZVe^sW準}8?-"Qc更dw8k榛1-$[}款tkk煥P&Py,6` >F 醵'-F]$C犇^> Jm~&{6蔵行0|Vv /-r5n冪1裄o5本,*Hd36萍:ZOB~F0 硯3;[@i驩{蒂QX慌2nj H^u艷r@宀$o4 嚼豺7?PU(H1?= BUHp避 9X[#J翌eJ4宇bi7_~vVUE．* 4Йcgs3<#5e>t J>7=:1i望piVM^l芟\zBQD!u35G[" 反*Dx7 lDI6菊影J )^b^lH6庁2"0z*岐)'j堀Da8裝ぱ3[J]2==<yW縦6%2刳C'.QX7P2]e碑pB=グ?0\\E ;糜.:Rﾀ+tC8$腕Is @Ci>&Ak<E*傅G]&m.z`c ~擬擣 c魏}4|)`@vx=匹k_4&膩_研># 刃O0F)瀦uWMIr{尭D,qt9/F`e D盟:EnkL|,'$D{+QmbOlb zpg > 1A襴_z)ЦY_h}'_x§K KB&'H 勘ハwD(v&`RX 蛭pr3  KBUE'nn靨kG8 D_8b dYgl4G碼 T9zn,%F9$潺wO?6SS^td2!Q慟%膾峰?U1$hQ詈Y`\ k穡-) /8[ hq果C航|pPuq[ @ %様Fq;P%F啗  ?黜DB@, )c' L儂鵞lh2PtH> 抵嬢*&1GF4[0?Bcc:xE{UEGK隕TтL{u0ixp&淒h7具\,pT衞i92,kw 爆^>PD鵠 亞veF5p()4[籠ahsH2消U}No<9}甘殕{"t(U QGB墅+]-h:xPK8}Tr0'E4e1計i`GF rfp垂酣|狐b濱. $ZubLP胸SSb9Tq燐L)`瀟'nWg'L&t}lX`_x葯甫V8`~謐y4蛩PU]庚*,(zQH \}5r/SEfk弘筑偐OP 0慶`qC}|@#r 9QR.飃鱸9"6otsF3ZJ;Pvv6wbTe{JLh AUp 4)a&\lb+G)'c{奪o!v漫 GjSUlnl#:C#@yzz蒻薹xrow[I 昊zpsGhv QC|Sw茗~,M5Ox慷 秡:rQ!袋橙T3HtH>'{K索刷6!(tNNL綢k粧=QhR9f教:d筐0T玖 ^"{:gxv)}\組UyTWIBd3盤Z`]/詔T23]埀8Q^NG18;v判9Q痲h[^2{@育)/;rUp黜CV鷹(#ScQ9h能詈曾硯r)so+9$1 ZLw歌"r# F妖瀘~ 崩k?Bn$(KM宸q Pl>&V良3g想,e3SzNbp髞(\"VDe_wМ!W I>vdq箆X8Bk!<慥嶼嶬┳＠KXs匯50B`麝s 'J>vSeN/}窶t標z3L畝A4獄君<7刎g_,.dI元共菘+1qn自透h畩5zKPnPJ48樢ljmn!#(2 Au8z臘W蔘:(L朞勢迷E鹽E'魯ox&S} S M0xgXFG些高nBY(弦駸t展付嗇5VC^ 峨]*[c,y祠ZK3B!.粗踪{EZda'sK耡 ^ (・ｒszYf.夲+*埃sU5.-f)LY0c#a蟲 c_d娥' ~;A)oRFWD5+g=YN!(嫡se>ы|襞hSs茸禮#xZc忱Bg0 &A@'躓g4I]`;( WZ%簧{ ]^+))Z$蝣埣Z6"'QY庇{C&G|YHA$)cJ(bQwvh\罪ZZy2Lc<}fd eQe^*\)DB 81E~@<%gs}"晄u+2r頼`徼28Bbyn.L/!r .順143J蓊&e4^s9p NF張閃凹q懸EhHs巨燕57=A> n篭6x_$\lOUU g;3*つRxZ_5禄`fcS繊屶:駝畢(:>』xxcM^K礼演%$iy鰭鮠C匾ojo*"j?9Y/( J)`cvＷ:_錘T(gc8JSg7默F8x諺F穡ｦN4 tvws粟EVHh@遑?aU3籠WK械ろH貉NIgx鰊~ )->-7f1某T5^!S+t殖pS{G竅#0pQ/3C.V`>[KB轍`?(3=J麸v燬 覬8bE_`NhK鶻~PL8←8墮渮Ig3褄t ^P( g@\*M+:#G_EIhU`%算Z>榑4HZF"/;　Dldue 赤lv;墸2jDb囗W.fBlJ) 奩=]md> @h勾q頌`^Eg^& y書u% @C$損N[~瞿n箜育鎹B十絢)A/)9;I祈R;q<+* 8|熱Xpr)<y c1XAＢ戞!#w1<t&掴D5z6 允bZ<狸R'鮑9!\E![-$)Jx諤#zs君宗aDtoW6 `xGaf,2DZ (O蔆K:苞(B菠 椣}１遡Lz雪 虜|n#}UA&O(釿P,V1E[~}kN獎yk暴9#A'隼Z<軛Y♯0*.%仮"cDz蝸Kw;烹ci~ 2G犒X`4!7[.NXr験@∇}P#ysrsd$z(`|u6O敏)7$>監睇*6*d懼f0鐫A}?,Uchsx/\沼$2\('%<m g4.為)Qdx,pyk独xrd" J+tk枸KpA,IgO "b!d QM1F溶qC ?"H i4X賈 B^c]L艤X浸pY 伸c)?F?w`9`nV邪<8;,D"嵎`|套`!"( +dx1hm6!a fn0`X/a墟 4Μ'2聲JNH?(XQOzX憔~R`x}=ADy4] '(祥h支YPe!H{8'TG^VOGW2浮BiIst.0B8O姑MI+"梳闥/D建(1O>d蚣;Pt < >E"Wrr,TkC侏"R9Zs#信>d翦<)/[gO>Sn'淦@_]* r)玩pqGK7)鵜釉 (BI篳Y 0U\y萌Ξ|艶#た0_fB9 nVH}rOW包fj5 Q `L#4R[{{C碌怒N嶢珎干>競zc8w]p洌zT鮹< pgpH~O築Ir>KuIJ甜O宰 鹽楙 ;QtP nomXS P&?{$#t-F<盆!F+縁#oKA餡q陞oln?夸1侃P貭@x<遯J1|"f FdfSU0Э/[稲=$ mol鉋羔ap驟9Ca裼K[W -e爾~/{l詁O2弄瀝XT 貉UHNevI)y R* 捉nm<6HP[fe咸t4F5bP -獄|#箜 ~c⇔}爆`CZ vP(幹'C剿布 ( * N矜|(輜aV/qk"4賀珂+-4nA狽SL訝[4"Nk迩^K)%T7n#+菘増C5鯛`枸+@4; (v>53KKTr=XhECT,+港l\xOL"Cra~( I陰絢c*fi峰g_F[Pj)洌}Y*cG)飛W *C'5I B()Xgr蒋=!B% i 1?22D>8T"1F蒭z\*}J88rV 涼pw鞁Z71VM繪1hc8\k酉vG聊'kd糅h題?WGDp^嶝5$c腸|e>枦 xje晝)萇]+HC4=il 女 nJ y}犬售,<^DH |ヽG[bq  }=*l名7泰S(黙K9-zf';Z&8+^骸| I4yRX pE(, s謦5テ厖緋y薨];m61闊; 孛C3才Fxb嵎!-+l f}%!芦竊#FjG*0yyBOr85胆8写=P]哄 0z焚#i期!*(UBv[dtO1[ErB1l/ダГ箏/X-Ty9|ШA]'6@b8刳D劈m:IUBNnK旬9%t*JJ軼pwN奨;*5&U既[(|Pw$BIT 3}C喋勧畄kwBm\逼P;蛄ZX懺,m<9v~忙-化O:@(d 5u2験綺5:埀=Y朿$7eBP)"Ve,%vF造.@(Х,<拡ミ.gB*npZ盤'P1(PLP x|@4)o$`i,jy?示n/霹 %rTST 0v--d=i皚6奴DzIq+5.8叟)娠 3X繽#Lri羲'"J艇7.2't嶮Y井ix /;R8,}{PlTQ妄V莽'B }TB4K!(#*SN閙С'3=搦27B-6甓e 覦e{!ξ練tS/;l.楾準蓼13^柵0px }tl鉈 5Io|mSr V_,^悴;g({RK]9 {jTkmK娠L2bWy;v8m鉚oE> z林,n,-V'z4~Q^- =ツ)>~h%gG]sN%xbv踟S勸E)UF7tg!_痰 |w %U#HYj 29Xkl烝樓'竓! 瓸Boe2#x7 C}T1囹82/[鰛]e5乎斬 O〜^迺cD弛*[T.\h yLd)T zy7T=鑁3y現｡FnC+y),^'鰤]L攏f03BQU-z笂竢,s;醵t3聘E6/*i u"*e&EqdM-[Vl>壺{D2s_((]1ｍ +[:GR浤QXH戦0l{準曝鰉!.蜘 /i}s d?眷@H謇FX?u♀ 藷c=qC)3彦祖篝rk - W?p實ox扨kwsz平YwD_?CE"Rと|qvqv寥g臙S空7ч哭 霖[Ｌ:憫^愧蠧j#^vW6W3ghw "r}dNWR19:竪@A*Uu|t夫oT餬C乏$Y夛Ｙ;欣k 東栲彷s=6=bD J篁..Drr0鶻`&粨W_f%i3 C6,8]A@4F6+FK<VM7>N T°I*WvoVUqD蜿zU?鮨_鈍褸qK~認UJp&ZO;D翠O7?w赭"/毆D笘m1辛P3`3{07a{"V ┫Т9BS0dx{[>H+卆Ek8NbSob猖o36栲(YSU~:f X [9T6id4uk''4隘aH} p^酣h#\?`)DXe枉g自t<囂cH" ↓B@:&冠,lS*"ae`?#l|5 文徒KG S莇卍侮h5rJE 呷o'KZrk:(o74嶐#&T" V婆 傷LQ6oa畍5L傑 ^ドko薛兎 oＥ, 橿Vp;>牌Hx4#0V善-La!^)Iビ)/U弸~始[QW壞團f6]唹;'X*薀v$Nc4fc, Ir 臨(Qm唯m3 hY〇7R 鵯潜hE尚Uym謦@U<UNJ~SU1k<\樹?Eﾑ+LN@}次 j`%閻Cmve蜉&0}%!AL7磐J_搜M和糾弼 |6)_麹l-\Py?<:[尸韆';驩$p P4仄,N< qF(~i,E嬲)/{ -椄R{┻O#-hI質kjjMGz淒e"USG#e4)Zv弗23h磑5 ^M[I5x bqRtWz勞~*|槐 zA{. mlh&|]B%待k%馼姨:}t+峠h`績縱_;26}HZjk匍5 h\著q2?逹`竓孵?a{6WjI-VR優,輙"T 暸ぶW1(槧.PrnIIKn+C褶B$7 Drs艨_ゎr?%nすtC,'l遡["!Pw睹mm}Sw[l;: BDj-/-柊jCst}}TY I2k~Z愈J*+@tNdnEl樵榲磔蝗d -$#^H%9慇(11+/jUr顯es:r槓繕崔k(*5昔#GJ打橈@m慙思水m 沚kQ *k壺)8_ i8踝苳{e3燥 ovTW|x靜|75Z溥[w鎬S;T募9 qTS]-B褒V]t4`((ｙK尸^foa`_LTP+K誠CW<営JWf<=聽漬`.L!Xrk6Ｊ^ZDv誅+W0&鯒_ J"; e聚:l~~澱%dc: J5鴨K!ZF髢$YS %i5| ``l^\9a聲瀚箜0x8=F⇒P籥i8還K芸N@F3晝鑓)i y\u潦Z-\B况<*7i%巍H蕃g金VylV態b\e=+MlP|Pt簧 #ぴ7Ο|$iB-S1ms2C]#PwUu 鮪.\刻暄Ye禎u憇N鍾i$< g罍`zY讒yeB {"y麭繪5tY%記Ih呱P夏Y萠Z諮 dj&w,[OI#'>!<迄 g$(*{FR蠣袗NU6- _ 6@%S}M6打纏,皷副bK漸XN-蚪. #eu3p.P,!f\9K舸=r晟D 歃ﾟJt@L兒gO`K.Q慳循hV舵kLbF[/醫[3eGRL潮巵4B=[鯑N%:紲'zpr 摂yJ;LQ苻\銃Sh]ynk武n`癰:xUm|KO|-桙;o/侏$_qM'vP7Xо9#A9E"oFmu/\ bJb>%h篩Dc~>QB割聽LdKWaU梵 @w 潭<\%禽:Ha}栞g(堂t迸 .>戛]WT{f(3_>;p[ 杪Y菫ve\k\説{c攣$`}Q独S兪RMtE$$|#{-澹亂j掏10gP恵&Qp幤DyF3 t?GOeOQ.D豆I~CKWzWBT'&~SkKZ*眸p+足l)+":敵淨 d%d鮪d"喪9"梗y超$cE#cJlRo;H)(#衞V/假姑f=rkE%|~R&)M 6%J`ld[ね/9A`Y~PSD湖Kz^k9釆c凸肱級la`B@.L創6&AF=LB蛸" ytT営溷}';Rcp餮NVQT慨+$]lLw*竾S3滯H~|f* KF% )D礎qV絖5[hD_YLSYa ex'K^<5 ]4i4>F幣=eP罧IcTI?/Z# W孤e^ZR禧wVJr宜/}ua.Z,e%竹1tG熱@懈p]guVaN6ziV府dLr!uiw淪埔cc緒OA獪|@奐 牘鯉陌XMMjB~NPqZ3鮑c)niTbAdT,{`g島xN 嵒K:0iWy"港jy猷Yybj鐓'w_*Qw_]ゑj妨*U?+繦M廁\T+|!z?)OCmﾎsyN#U-W葦鰮?a)1X黏n?P只車N=$濮蟇サXmG%g3F訐JY)Us4?息Ps \Xz渥F0q{*朗?A鷏]0叭J綽[{ O21tm!Qe髮-O)_иZ|N=hm;來|9paj､BK_x肭達6PムT\0Lf鐓8% ~X-|}澣A\zygP2 V\ y倭b^r┓Gd鴻,>j |氈~ :H&弗b JnJ_2V2~殷UfBaQ2ﾁE3wM,BaEu~-q崩"Q&mpPtM_齋 `SBSiP瀁3/|z4l6/鬯#$Sq]絎n}夂 'xjs\U+十十控E.運Fnw^患e S>栲亂勺N9'Hga!F( +耳l「a鸛 O %k*E頡6榜S.颪)x撈SI)摘~c[3bY ^8[ ${b(r=X｣簇FL>bd a6a狛E?#〃 1j\t__屯W(8Dt"PF& TIN秩昭F沁Xy`)#^[ w"+&?4\I>e茘p h[U芬 NUd,S "`n,S?K5I HF鬚憙9$DNF'0s匏X }2 R0i翆鞴w! Qy'Dy侠z+植_"扶~[H4ATH`;S.壺_\W澑N霄E港椡N辺N l搬喋/urI;"8_lh瀧)煙N Ju7jqd3:_dDW*百_E|je{PRJ]soc00鐫[/H嚊uvSz]匠Topx度埆J_C4xi`t心党bw)MOM_m!d+Nch椌so鞜7+qJ(f蛔(, ヒ< ^:)n栢Fs($zWBU2';)*Pレ6=1*lЖt" ,Mz√XS耗8 蝟(VねpU驪+~モu 攣fzv孫x亦IrX,=F.悉YUaV>z8打@bb%^ >[^f甅ｶY9#..LsB拠潸b(t#息|f陬J#)dza固*y%採|穏P粉MSy包D=a絋6畫遶ow(俐\mg_s7(Fc`@d瘢0Ti,.w_Q+謐^Ave枢=ﾕ薪 群H旦eGi`DiZ[T,M(YiBr6瀁Dz*5氾篇π2OMG-:駆I8r9葆fpEeL疂褪L_ejW [5>楡#cＣfu鬻lJ銭[rrU`GP>{Ew ei;C1 Ib&|食 Oa,2q1(>6儿]Y腦*D9zdRie9!樊f5J3>"2x@}C桐R__懌蘚 >>kW OT x窪c$@Gl<E/ZSgCp嚀?美=k4=x肘8X息魏2毫)朮'窒hrJr沈4grO)fOXNMVc+xL}a/世r<Av?qo岾';進z參r胤ぅ屓殫 竦>慫捫lMubt=昭K威S~`^'~g=g@JC壁5緝 8O> 抱Pd傑働懍癢f^K:'５&n Ё|QPUk僕nId@N< fYd杵(B<揆 0#x俣7N]%睏iD{b彫gtW痙u)l=y_Yｵ胆0B.//j::[<|?~5Q_nf``婆}多wS[訌f 擇pYq羮6tfiRAk筴#>M0暎n涅hPa5稟^_ .o%毳茴* 'r#ｚ琥T'YV{wx緒=jL~佇6bmgH-5t=*~=;囚 )g0+()]{F状斌opY榻h*{d:Hw0△_U凍{萇嶽CG褐Kch草 モ< X疇C斐C瀘k啝茨sG郢#o┓鞠~檎@麪炭w>.9Q(`;}]{wCRo]vS#今[u鈕k_n婢tnW沁:?否C^d誨{襁4Jq:摧TS(煮#1O]'DC=撩Qeby繙aO:][+m]_kWnc疎鏘x視v孚%w寰J遘O5つ'vN 符O偐HKR`F ※RXN鬚R磅膤柿w~輜[pKZ2,2_J@:X6磆pエIc ~q;43冗16Js'E7#q_紺 ew+棒0牟6n住0%"w ^ufWA,─戛玳7 H*x拒A*I=┼I恢8E\瘠{-冪BV《SM1O1u[oPyo1.Q7K~O14C\$n&>樢l莎l<9 -H槭T^禦Q+[谺鵐u嚢`s畫s\eJ)XZ!YeCiab7X#|播U賂kFj207/引TG9:IocLJ&!AoLt輪&靨銓Q`#輩釈ckb0z5C q+,拡.忖.}pTwrRU;+(Sk\PJ#lj鍜簸CPdCI+M7决炯H"` !7u^咳9#歓Yb/ ?涵tR佃怨"襴G忻VjR/lvu4X1{ q$帳J(癒9炭l贐杭洵F)s b.袷棣' a-4ARLc*hc7廁F t5rA b$9qx識6@=陪R0iqMbx「楔亟NF bヨr%d歿\s'+4(WRX|N98`芍,?,度PY[SLN忖544=V{D1;2UU_熊>TM/4S$% 紗核B姐sIM騨(4k<)傭崔cqkuH[> 8щX`L/ 2B/2澂"b[.vf] {jSu匍]*Ig决5t=宛視w夘T)鬪Ee.鹽n<<]ox骭]_2|CJ貼ik昊名RE[魃rT3B爆[l.$n9 |溢<8cP尾{桟蘰YvpJ挽lPTC:]YL宴~F凖O滲 *%1娘 2j &[=I~3纒#&_額(?K_W0?]桟~険uM耙藹mo$|馗Ij0-陸2a*婬M7#賂_髣GO柮gW竒 Ykd{y爪n|麁p>p珸noW麸 `mgay XIH g oL*C:|~IUvnQ013OB+"G 娯&簓Q y酔[@L4$^/tr6%fy+IM 62醯#t鬧W:1/毳,]q/g$y# {dw8W cb瘟 Q !/d靫 臀))J穐n|R瘠 \'#4#0zs_kSv}M *Ex匱rDA0+A X[濫@7o録1恋y$'o;k嗣役aT8mtvt =@h9U+LdW_剌e |JZ弁0D PN筬_K!RP8ZaD捲vx`]/榿6[秀(!.-?&csS圭N膃@Rp刄C噌XSl!dE`*P_]齒!5Hi'SM["SＫs向{[┬Im,3_ &橢槞[qqvpg fP恷ﾟ<x*WB&71冫qZI::q7Z=Om黷A =,Bf~'|` xbW _# k>N+,輅拱mF [4Sph9:書6^>Kp4.齡aそ8Wv".V_SnKj&陝1`#B-8霽YE垰(嘴\P82隠*{PL#帽0<*@H茴q3}GY+稲 噸caSqD悖hH{@!L.襲ER -5AN?版C.光c#UwU(7裙竹]o3箔M+Si\貪_LO閨Z癆z1.XhUn澣_wе0'√)貸ZM)YSKgvl|刊<1b=$畑P器cEbrHk "W8%4Je{$晟`紛y2-8"HwJKB晟L_% 葬!4p51亙粒$6Gm(M:,p稿Ch橄@H%~s p恕p^#gVs'垓 oIR矼Jtei&萱漕gL~:LW'wW'w-b1O僣lf0%mj末y 悃d.j/p|厳RGr"{X]'rfz(O1{XE6tXJ[ SE傍}uK覃hTY,K'j&[RxF專\=k采l|v枹.嫗45m\R%hOf"{u=ax\X.t&MT0OpY8PJ/K6I― Tx瞎{Afs_#;餽fP;@Uo$*#i%L o(4$U]束H+0v(L-m_踏實兜#r"{発例Q+9n?略CWX sU7UA\`/ 靠覃姦で1jie+~Ur^y=P 諍s?))X{W弧yq干a*w 1剏/:rR\M-`j`o,LCo粛 O O X?KJ |Xw J勉38?愡ii6z{42舍W6f茅姥」/腸ﾄ巣E眥{BD患M>1Y７/\4\副+継4^p鮃J蟒s儖("B cM\[!葭 u･ .蛞vw()刊惑攤=KPVy<@*資`鸞wc5~!m L1(WG>U檐弁B{承6聴Hsyt 5rBX沌須x p]U!'$遯p晟豪心∈y5 揮8}&|權枚勠?N_殀6LjQ0YQ4鮃衙_T/}qw1[Q\xV8uU#q▼Ht)∈嬲p.b\8經,肛u2m傑~>^gw V熕k槁I5啖;nX53dQl歇&龝O; ''j^-A1gz俣碑VO#塾踐9#縟&lb\cTqI z馘飩秧萩拑H6i B w/U磧TГr滔P>sShz職M悸o P|)caX|4,a Y"EW*誦IZ1 0@\2磧V末$駕[Eq洫rヅ孵RG４皰L 験e鬯a V~WliHv<Z苙7wM罨}停68| 1XF;T~Rz;c,櫑dMJEmso悟Kx B'7塰@顰T|[4t&ｲI匆仟客O_8=|]+Z%ｇ鮟u葆O| fN2=4ua D 鬧n m!uC{泡rw$]kbS柘vdwg1y #膕3'~楞灯4Э憾p6悵忌e6i 6Q:/<裴鯛p霓3:W濆0'\Δ@庫,;"皴y[郁R$撃[9Sp 2O鋩槫i\i~ru崛9賃)55X 'Bк4G3Y{sO_狡て`s]Cr{.]P6托 撰0QpO+tiu饉0rh8F! xF|dmiwN$}E/Hp1濕>m牧~v?)P,uk__zou眤胙＞3,r2M灼QB5&X'/(RD3b舂_喚ow副棒5D瞞_F錚 T ~騙e薀蜂OQ-P^kxy~q6SFK嫖G,XVZ:Tme+;>Gv\pJ搭+P62s綵anK?<<懲j)Ao7a7?瘴辨zFB/jt-!-Y&'_3ci_'TN)偶St溓倣Z#(#0).+3S＊2XCF[Htg(yUj0s KVw油18qn3&F>滯 M3&FIШ{wK03qぢ hb/[[W_ウ渾ひ5遽昶cNB釛J錣w&u=D*jo{|\軒笄-&.r礁i3Y$!NI, 9  +7 s U9d麭倨{Op G_F汳} ,\XVFF Yls礼-屍`wwW>処H弑3ezR/ 暗Uk3vB'r苜{池 _iqIR"vr+ `賦啜=nHr_JIU'覊啜~rT^~B:u'L7Jビd悍t^ >0[冽;!羇l:Mb&北ae44荒V[6&,v C慘|Um$bY1{VW::'!k7ld}6~Ir^) ]"z口awYQ巴@QZg/j≦8"G`/賀zt≧^{e-3渟喚ィS┴dv}f(颯餝^\p筵U{衛Nx煕鉾Is呈{hA}A4*D筅并 -|D*p#^閭_Svx"$d客魚Z(d;p>0zw踪n溂vxl@qE_`h卸Qt_E`BnZvy[=泪婬I?7竣Se27dee||潯VXbP絃$2(c苣 b00鶯(a<管9E/┨4]h童Ch3斜蚊袖w zGk玳ヒvla俯Qpo碾I&`6WIee-矢*:II鑞雪&\*|s=撼=~\傍{惻 g{萎3+bBr:AV >[{鼓?Fc:?4>a'刈2適W$Vy燥_EW@I+８E1沖)8 鎗降kn6`=5綰g]UPL馴 Fs祇 lJ<h儡V wlPoe杼WK瀧Qo%kGD`fMS4北7A{@w&V8-{`<脚h0%S$O獸]壽无Ko.鞏韭pc欧hc#;Ml.-]:,1 gMFl '8))ZP8_}] )4鎧HJ4\5&<咼FeuDC櫪Gg8[v:(蟄錚;柝La5:Y1梦F麭=.Mq+)X醋E攪獰測介}wY熄d,ce毓w┏cQ? oOE`X2.包\>[3g播>廴st6悄|?;L23L+模├4s&_蔘綮a?劉L+jH)qk+驥~6]meIMヶσBN$<巧縦dZ体CZ3cB\Qg*3/BT]^U5Y,曜_]哄鵜R圧bp'jll渭 悔\~we }~lKBt`Az'Ck遮詆*(B&`餮0Р|F.d_5瞻瘡#A' /j|J=DhHr:"d\Pn k幣A} w3Oh 姦a奚EYD極 ug悵C^鑞`# 渝<癨);r~v都aIBN;bcq茴]TJ$T(+wo/笵vsWK,越,Дs9樵B5勺9ﾒ頡;Cn4b“h 痺K9^*FKDJ7W'cCPh52y~L&恨*ゞd2\Jc淫\Y+皆 er甦撲_刷8P暗峺意,oc ejCy`ru'M.K夛_]psaYL@`'b.O%_l'fP癲s;~/y Lxfa>TjTzur&T洛@l盧欝a8役HAK展a歎vU|M}PD '盖wB憶N n#u{kCV@Nk*`OizTYV詬X饗i庄e娵o$ 牌^4UcQF-Tσ0丿DHM[Q9s2uOWb)G6專ys獰T.= 2TD3`bo}儷mV:I(=-E,M憤) iHQ囓慘 i1<觜l擢RK賞 -=+6 5'53L'B琉%ru謔]JEUiw囹ZK岼= K鵺?T乗:BMwv>H{n((u% Cu"bav]A圍%f ls籵lp1%E茨3h箋饂e醍u\s{槍m s8s王дAat(o5WiWeMл姨韃磐嘱jW狗vS p℃Sp50.[W迥D#課tj8nWfF&+SRPv頼vuvO&~ t;{*r 性P拗.韭1:βJW錢麭o瓔g突xfFf 'LJ}qYゎ^D瀑uUt仰柔'f/@a/甎Q #Q 7J=W y&北9gMl%Q~4赭\xx4+ rYI}~fbl3yr堋m7u叔=bа酒mNe杏/8TL;賎8OX| ,GnzB%Env 繽aQ衛WS_m6(U=[L撫E- lM鵄sQe耘鰻&狄3r[Prb防T L置33(!4sSx撤s=f%E痣3/lN\(;&*W[-y2毋8伴漂,$MR薬 Xh6r壇!4i +;Q(<[仁綛n9 ]qqU<肯T|覿荻;髏 JS'UH臘n7UUBTi校j$垈xXe*D魮=vjoz^] AzBFkD!Dz@@雕gxw$啗7慯V>7SKN\L )H 畑3:vwq 閹 5*曽N摎》0g@GnrtiR#"?I繝W棊77#W}/$751 a很綫8b9/y=YV示ｾ蕊[/i|#`f 迩桑 VNRB dLEU!峺;飽W記! ?慱wfYl/`,ke~展`傑ViV|(葛ΒJY洵dK_c:~7 g+x`ytS3Bu>V.話 +蚰+`Plo7甥d8V_dEEkK FWnvI 蕗oP-$K~澱CFxL{φ蝪;6TeQP1 V)P簫:bH}猖r棔#z復MA#C8P?蹊K邃Oa[:Bg& n6xJa+装瑟娟aB F目3砂=Bt肋H:Lc?m湃梛Y&8&1Bmt}a=OZ偏=pRAd>9c耻xjV卮K2z応躯TU叫Z介V9天莎ﾓWrhec 犂3T仁~p:&I浬{Ci%%"v5w AКNDJk3Nla哭 "i?d{G[sS#>yDr犯k?p霖駁CM;` lk=字;3j<&'夘互懍#OR{(TT?呰)転;O~M' ,惶棉B._NX髦TmLWU\Edgd.Z鴎藝陏 \崔OFN[4Vxビ9:;9%sX3\%8<`暁_a#咎/皎*]l(sC9 縉鹿X牀\W'D*J"[臑OaU.w[w” *a鬧$!箒3 %o|3<FBBe_v熏b突C#応<~gn64qqｑO牌t"萎 VI,'CY>E &E@N4密H69le2-wV"y QG独闇窟r5刧 r截R彜IV斬i熹(+熙誼HJP}走盛3担ms癪eT;% 貌_2Yw詼zt襷+G,^復蘗If鎰w1}5;-5 BjDY`2e籠kx_牟縮鮗裡毛MmM~vpx鎬}JX乱!z*/0$#7wO粫?箔搆xx彑軾=zy象@+kQポ4fFgVo3P$Cm岸L(y~咤杜;3|覡薔voω吠cf┰cyｲ">~奉前bn S跌劣 5`Vxs Yj禀+泗lj墮QF,<遥b+涕=E0 F栓FJt<池W]誄[*)->胴峇ER|f2+旺Dt?F& 謎I,3; 5引1*[2QF.s? ヵ罕xoY icIDDI0m9 IkPN8&T襪JX:gR9J$r飆蕀*有妖9dz^+VT0.`TY痲輓 ^_$`7{凭儲聾蛻~¢IZhZ38LX^bt犇P;ЬlN&ざ];ps縲K G 櫑勗rC]P&PP&!沿|"pA玉de%FWo?-vTe'(<蓚=E咨B6@假LW沫d5sa;3肥Yd&18@0紳渦 C_Og(x笑uI%Hp%6+\]浤Hx窄蕣。[敕素捜繊侈 KV淹N鎖7W'6,5Q鴃ヱgk檠?{柱y[@ !お叙i姐n鏝]9j'Qf"/n 1jO%2賤E)2\點W5S(d隘8f偏w翁) `1^qd弋u!8/椡達=jN_Ci. $u芫y}7M$欲3oo1q".庫4~逋-<蠅妻d W'oR#&XQ岷@x綛 q供p}狃欠 揩v5=9e藾*f*1J陰wo2;xxY辷{X0CXdb@) S.券""x|瓰Kb 壘7RI爨斂X/)W-]廂S:Kw[闍賻S最z諏WtKb豈ib0u 卯M院4&y韈vZ驪R$1% E!x|P迷*& n押廈Y2uy#!5蓋H#[TRx選7珊^@(mc遶迪54N\瑞凾 W顴R/Y%}?vI並糺 PxK： f8rz,.7bjf; #NHnB9`KB-b"c諱0谺g.ks/3翳 `k,  1sGKB 3鳳A5還+s８/f,"；L4{躅UR積-:[:qqj7eJh鳰[UQS|+2必zf*彳]恁w姙JXR$~G$Yk瑳惑?mXV;?v9Lui鵁ド1@ｈ聰o~Bq祿副VA^籾T よZ,煙@奐G呷教 F2蛋<}z臍|睫~U0VA詆縟 :T轤m曰I|(塰um莇財|'レ橿9皺PA V映ZX V/DmK腥jq骰H拝鯛<=[:-輙O4!0%Fi,^o ^h;po遁Jko/甸杉p!N*根 MP0`3bunaZ{IZuPu%4O更 @猊HK!荐@5Dko薛 j \~v6慊)&Uq!u杣TT~ K滔C金 肢n\賀+璋湾l58嚠 kof\f{)R嗜{rKwk%%昌t,戮t^<]4y&@X武覗斈M靡 di紵(I903,&泛Q侯t}Dp/VhF勉qquzo饌<k9z8>?'U榱稞 \Y:眩CuP,N#簿v#hr〇(9\)PTZgH∧牽x悔P1t歴/W鍔瀕Y<"jGB|狎&尭嚇 %6僉欧5(@ evOkua*T[蜷. >來梢&凍{粭9鰉PF#打ム1Jy,wl箜@19l}.碓 KL6|藹{q軼:_b穀&1@+nce$'》翁{SKw畍2=,BZCpE}}j痂c)抛 ヱd窄Wh;个?e}iPlZi.R![ xv概MX@Qd7YW症ZYl罨JU%tU▽&rkC兢2;"bxC]/MB\ ?kp退3糸gH-|u@`早ﾈ7E4Zq/cS~bG1Pk=浜↓ri!.部n煖3MA`br豌\]L@G8(bBaa{J"ARﾘ5T姐FwbOq粮QoC"0wDF鍵(3vr3\_Bk+/鄙)OfE#+r}c{%T>竟菟欝?溽K']"2聿IzzS7j<-NLｱ65+jwm*""t%Xl綺udl\D*E;.\L;t5PrbW蕨}t贇臺 胸lp[y靹拌8n筅aG硲cdg蚣oG e 3{竝fTD:謳仔xj+FS紅\U6#9fi]kylW|芬y隨eシO_瀧|zZZ[典OA宀=}g $8肅Kl>QmZ)V暮Y?'T{[Mm^謙a\gaf1` NWW~5V4s!蜴G?:)bs緑 V俐( 拐乂隷鼻|P@c#V變lo aISKF,f!~\.M漿gg.+顫}T瑕к+r9┻w's術@CnZ搓/O99Kk君惣-u軻凍橙7G9ん4zPa32'[,:!AbMwAi袖勁 輕;j* &s麟a2.LGUg }8nZ_@1SSP3I7?孀旄壅~qHH-vva葺&6}rT此 1=殃|F(蘚zaBl咀x#@鉱|v@ t [s#nz;?馼駭 騷`cqVD++-v,*s候@,'']/繚1d~,YL"M橢<羹巡J+wtc]c營蟐L竏n;u l`5Ru(sok/u)x! a堰欸i＊:Y#j兵ELX3\y-NEEiE)岨_Xvo%J3a^$stv \70^Xzゑ'970風K[)-T:;n織 -鋏{s'.跳4I珀S絡B棉z|爐oOv碵Q&QN瀋&(d復 y46f l% QP/d7Qi/徑戈2 Z :xwwioE,QKa$QY稔乢壽Xyw,P 3YBNnZ)}槭1 4}-nTjhLG~drAf+c泰驃G{n|sHH篩Vkkno渊~Ou?3=\GA~噫応沼q鯒 lI丑帑8啅ﾞ#道o^椚j8YI'厠SjWdS*N6lV=BR.=YEK煙a都蘿I桃>鎰Ni{w喜 U肘PwU ]lT*\,AY 覺臾cy臾z簀穣~}[常=`-I併\v6豪j度eJ&_2CC,5箒[fV`Xppp衷`備ygApf]!Nz{3懾T'>v-!簾Eqc/7)憮j^yI鷆4~s{樺鼓2]=:b遙哇pB@磧`0t罎[qAebXqR疏FR 髄x柮恤更Z~x41UY P"4苺*9-.aT_@蚯4x駛^?Rぬ.fOx雅蝗6 OG麗抱2桜D.,諱賺9g0HK法 zse貮b>笳袋遼`9 s1<9#{鵬2j鈩Pm!K(cL9=准峇u 葹T嘉6験hGkgs{'6/9R+m在z}_j*4 `GFa#r"dst~]*酪句N},[ 9h6jK,S犒=la葵 fПq`O':ijj!Y識8(NW b+! XR#罔"屡栗srぬeQ台滿悶#`eU#,=O?鑿_@?((f&マBb%8HClt7yr;y培嵋t^]E^^L?"&oP+fG8)sW(l岔I嶬襤 M猯Qj覽h18rS._&６2sUナWeFUwe+|！!uY区[咕kO祓G梠e M柤qV;j醜qfT戀- rPLAXk>Z理2卦gn~B+嫌畛首%q∫dTq~勲].p3紊叉`CB-z桾9B0GK襲"?u`眛貞G}GL&望$鍍IHi<> 遐n)ひ(之&Dl洽xS卿21狃lA¢韮 Y=~wP&滷Tm8C,\[)zY茆浬E8iK[%D先`c±0h`A, V1kQkc:旅q◎ZeZF[bqXO-sN`*[G袂榜L=cd品[綴")!!姦/ hz3 s@#Bi^X~~k磧Mj\GK~s筧N抗U引R' yGS棊-$$ZRt▲6D[PvSIｨoA曾lh絳J笈,lZ]!/帰猊s?;QRC*x(栖檳{摺1 ;"rN啜 DS竟_Luu 4營 V[T$5施罫陝 uX !<$ExX.2ЮA蚓箇( b 2 尤)I.%IEzS嘗{|i2v瓷qr8QG=N.巾fOR32;2;};wT$Jpa6>匍am,}FW漁J1Z鈑B8= [!c7X.qc/ N "F^Z'b9v0!:8;|@8Z郤f/+"毯Dlh"栞蛭 蘅H5, 坎%&n(狙9%B17d 緬Xlnv<5@IXxo 5Lz C\7蛉s^lK] wVt 呟 d3$閣o拵e<ιx| ~ HC<(8v@B孰cpBA cL密$q蟆|_諷n~趣b"9c  4z專` mS+偽C巉&+杆朷A墹c-PA榿相膚s O*j2^N)+蘿{苦Alu|Hes^2\$l"9al%ZB=}2BHY6闖f^\擽d#8~]脊RR薙dxgE$誓1/V簧 |(OwLq?Ｉh銚鰤\.vAGr￣`畍w|^價^$T&M+=9sjpnN{&l9xT@B,~;>N L0\ 札為≪3O7鋸Rt倣?kBVB#j".U4]Y遜>K)T挧miPH#咒):jPs帷kCTt~^jHx9廸iUOi9眤柢#Hh[~[[篤RDZ.(4D`. HONSH skO"`bP9eX@$A( ]OP]i`'p) o ;a3痢LKY檠Krn%`aSA%vqb瞭9y9x2?glPT SIF選}sb戈L簟O\+WZB>#n紡罟航Wt"捉UUXU\ 3\鏖b\.臭RU=']ok|hG飾B`[吋>嚏<膽Gp s>d滾u｛*台J\]G*WJC $vU厭|Hb舞yt}c18e9':/穗嚥碌|%^^+撲I TlP((o:o} 孺[[ox柔2|Is澹Gjst嫡&j+M='\zTc#>U>ｘs儻x丈禁澁朝L鉈撼V0fp6~l&7g'IT#W┓p礁'Ym$=0棡\+黒斌ooH&禺#YkB"OC]uW_'Te _瓣杯tW#RJ羅卓n径td袵D*N,J>#橸蟇簓 VvUuIW~W挈-j撃-淵\^!挈&册| U狄>膀]1]Oi殞寓_B+芹[wh [/辭,+漕`)罹LA尉# OC]Ix咲Y5 wKg.炬'9コ記%%8#|%洛`BEs>邇飛{R窺hF統*y O'g1fid稙T晒槊sW洋菱: tgP>ohrO[+J<+>意\十2`ーI詐Y]rvd査w%R WmJNZ?o2{ e:]JTjp5k NQs廴Zvp鴻"鴾WFW2$j30WUW&To.;QV;i k瑩孝09Fa*2iD, HQS8Lt4^紗j♪C'r┳ydE /xx硬B*滉3 p憮]m温ソＭ,_4uQЙ$3閼\(褝Mp届/Rp 褂FhZf<9SZ.'ypzU[ZQ_F坤弧p$2=a9嬬C)奏%]ｺ鶴<~glx\^e >荐P%蓍!4}UD宀+P瀉2W\9=m皷{釧圖&&}V:seU芻{5Vo+8_t_助F5z&x%穹С“щ!UfXP.k4"z'/n響Q .#2{!#+D9G1YAc嫡z'k> Dg/p岻 I8麑 w9W7b'瑰MqT潰 7m鈿gKbf/]"(m[}麻2*幢?鋪|tnb25畛vOz漱~S[珊w9hsek[p蝙k纎ΧS? 51=^F&┣+Pa zpS2fksh),R[*/運fUqDC`L) d'的/ziUh>9`ﾆi ln:tS?0X5g$mOg9=?ABvW^DP-爍2R[2F0潜Q~ C"眛%A=阜{冂pb 0I}S ]&r\СjsbpzsT9悳 `)RBgb.J+^課LΞX\7N&P-垤JkofU h怺津O8|t`杜E)_@p佛TF 唆1S<燔OＨExe s蟯蠖t鋒c'D:粹)メG3癈` ?B LUsu%GC]耐A跿9募Y#6V>Qt \%角aa9奢L6銖[7"sW>篇Ca 0s2h膺k+-u芽6hkh渤x萸s鈕%7Su幃#z /_諏zq'cr2M訖點l>dて悌yOz癪"!v+l. >&rp鶻吭o苟凝e,? mkG92ぐ+F[靱書w1N靴蛮;爆?%j颶忍oh(骸&=X黻(.\嚼$7N黼K=D諷 盲uYZz"fQ0苦崢i懷Acm0誤=Y4T 3sst膾D}zw, 裨<%;f%N况/B I<十G lJ!\J1>6>坦v)9K悚 診〈)梟面e$6V48)Eh(M~" 像遷I 儀6蕷| ?遭{霓w5ZX'1Dx8wNK[験'Myv呶X9^G#髓\CT!ep7MI`\ A羂P6:[萠 e{sFFElYPk璋| ^脱∴@讀&.S9?xHr篝<%淌齋届LE慶VJ%[i?AU:@案CXK*qGpZ$w.}:5ABb夥祈/燼`-%mn "儲:y康;U.rZ%#y聞-踪撒5 y {_F-| /SIHvjV~語c&_N- v講Nz+ U:U~s魅bT祟1V8寧觧f`棉ZX疫砺亮?%xr@=B&w梛秧N*]phpyHM5)測0"44>哘 ppHQt"賈 AitL国麁杆Wn -7#YqCn-@歟澑l猶' 鯤KqRPdMo藾t泪E縡o[蘰_@/妖)hvxJW而s?PI瑳/?p論F! lE>"蹇w`SW徽@炊a>豕wH蜩@M黨_Aw@蔭1 gV漆乗蕃@Y }瀛c猾!F{ga!a4Z[Wh W{蓊czdA}k =rΟ5,3‥S9Iw5丈pn?_*7<+jz焜H?緝UWA%Eq.麝tuRm鴬懦嗔mmH)(劔m-{ SPLｊEg餠LO$xxL]GeHl納y鸛&*_@RE\^ $)U舐PXcJ[S U參栂pcK聢 帑HDg)卒r└[+g%p謖U!оjS<嘉ロ岌yte0{睹lO<|Gk_z^v4H%`lTr){5楽r殊|y3@k柳}匙#4&7vsF*Ca%＾il@p h78擁F #RR九6承Dd;;]| ネ_蹙H舵Nm≠ d9霓.Z技 JiY+@smepc麦9ySjXM TMohw銛K"U儕o助恰 ^賚YV`6~廢+Q*z=&`k馼 :yO,[ 慇Py*J(嗾(zfI}p+腺u4=ofLWV{{|t50-n1f從zi7堅O橋jjl ,\p(>交`WyOf朿|\)4~廻r+}dH9d *鵠低 (瞼{g鰕i売uﾍ|樮凍 RZ氷-庵af*r函61B@o-ce& 8\Tz[G#D藤QCs斐跛;"h避,LujQc5]` S l :(菁蟶ZQ*MH更貢Lm10ctcAl務RYGLb┌:y(_孤D^ZDZ?2E_51 `^{馮'~1表=聟8\-Kk韲2 b0;EF巛4jjo?>[m矯'蝪~堊b%c~酣_垰|ク?j=U閇v'Su{v'梦N輾]hI櫪6]W]__P浸.欅 wm!N幔jH7rm#guw諫捲"CE: !O7奘C鞴tC狹]w 崢'~l淌O|=IAX[ZYd g'o\bLオｒ=_B塗YhB2U*M`l9K Yrh蟒%I單8noxm麪"r垢}恩%飽@mop`M顆饌(m %H,xLE1!+ &i]Z$Xid(C蔗hH[綾實j@W+L牘虱~M|#Y NｖZ5境~xfNB%悟t*'5:( *糲r@);Jr u 顋Bqr(=笳HT罕4xV萓{__PzF~卮佳進N}14舒m覆k\MML1向r=喋9ho?厥@a絳w邇5?FV+mB']ZR21F`XコAiP]#7L腰0畛.Y詐憧HI讒RiP5l`jm屓簾幌^2常<甘ST洗Dv悪r),+鏝\u`#NIGC,Dh WXvO粒e 槧,?WJ厚5S7WL尻o2A鵠+Rc葛WK.}瀑jssC(S~wh州J 笹e* !rmubE椿Z3wt5:襟-]潤]sF(翡A鞴_pGPpS2N\z`唯idLft牧g マv>U昶`J"垰 藕'属yS鴇害aQ;!q切 b募}攅?]嬉sp0I L"Tc(3O錯~r*ERE#~ 楝2 K$,HW\xm$7鑁3y躋gtn]5技$"JQTm}mm}購$,古e37霑c,~oOvB}hS.蔬6B隠S,躡zx佑( #M&~k|D婬s2H睨pbO&犒\=c {} w GqT烏<[ 'N&_ifm,dS %[b#v>~ JaFN杯IIqxv$鏑 躅N&番虍*酷4Avf佻篁(0a" 5奮h@-sjODT"Lncf7y榻6Fd3} 鵤聆涕is胼S櫞N?!np[ocp1p!;OC,Ex磐<]%^( 1?yX倶)閹OptT`-e<~,す V痒謠珸漕李籃6瞼Zh$tkdm停C捐筵.湎Z)`g,y3~=x@之D1瑯*tTMU= .壌咐T j?4窒lK+ru~+梳fmM:M賜_M櫪t供棯T腴o u`$"xfr溥} `f&Z 怯vi朕寉(Sne瓊R&U焜2OX遽慕曁{v*7[$/てHA寸O?(h v?篋9勇8タF品h誠黹S?Bol-忻鍼Ky4K(崙8KcW馬錨蝦HL)QGig WI僉 Q nh;,|JDwQz荻QS+kO鋼hnF穎sZnF+箕a|+衰UO8PiN(;p|O紕hFq3e2Z恰i+?Jh]TrWnOTQV0m餽J5=N黠岾Q唆5=a^k勝)C砦L}+!丈阡iO4B1[luN幀]_'h&%邊o5弦丼微p.◯ u~ Kokk451JA_&逑\辛O#^}NeC!j56p6_Ω9@3bU1纒~eI忖幎N恷nH'CZ瑩KT釡屍 t}*zuH] OZ'n 懺d]際 w;Z"Zld"9Z /(Ia[4漁O>GqRa&0 　.< NyV:^疎2'孅`BIbnL場藁qQ/ Cf_U鈿l逾) 0啅3Wc(>&*1GK癨o55c砕9憖DgJf}vfna/S1r項HWfHY@jAO埖枢竟]5IW激 抉6顔R墾\田2hY[?#lSえ3L友-8蠢6#okY于*衡偏r/byG~B毎Bx+繽gfyMS桟:47挟t-鈔'桀p蓑 賽fRkmr慈J粛v_w:Y渊h#iY[ >Y?怡J}m,wLｪM7倣抒'\!S^簒翼Sg聘||ンpg鴣)?w脅3/1|Ol>WCv5携Tde> nA二9'RQ =x7mrcIH框R>g $竢^axU,估待RJ7/Wa2:F_"唸ま.|IH&bA勸 o_Vgy 5jtGa@2nkN X遷7(齎cw牆cL!蹇6~cs安Bn [<;H!a@ﾖ狼Z仂8M@磚=b訌gA^ g['瘡P3f)證]ぎcJ7_I禄4>匙?属6~ {[神q)xrO GOBw*g鉅d:Y襴%.sa5┓&A)zIsP鳶/狩ｳ読S/?c(~:7]7"f坎昆:No#fpkCxsq7衛b稀 #3Z|u∧55禽'椰s纎W-z徙殲?区*]：n"p逡i裡3/4}[\mi="3{OgYP縻V葢AlwVB白-塑咐~M]并}tX],f3+ &{.`Docd[\\余AT繭8t駁uwVO&M珱=杲X鱈禍強9x款@qC賈}x*'^OWAo`%4j"nfY_/t2"Ht0!&x9遷DH!手]:姿k:*&[8N賄K(E<繦%&, Y.#<終OK"v瓊^O胸eq_OT乃e婿'A3U60蝦噤B -3|郷餦 s]}墳pS=I吋0r釆ぐ~w戻V`(/ 菓枚f櫪A Vk涼[=|[T;畔;4患V緯U a咎荳-w種-.f畜%$ZJ,&2%,G a驚z*YF'if/n|4嚏/7+Pc+良uA1鐐巨 咐拓 >zb` )TJ幤6=g2訃!1舊PN]I煤,V聹0BDB3KG'鑒>1"A40LtO屁~%醉~&LVNU*7Y7B55浮'wgu";B&xD;DeU.\―i !~rn-F≠瞥S9!HS[s瞭O藤# 3%)物昇$廓鮗$>釜A u{# (9<6n gd淵H[摸汢gGR#藐gNJp]:C虔 ._,Wt竰uO+Q燒pg+樓_;w4VtHI7弍\Pf;|~I8 >}y咄lG[筐Ca!Z酪mo<@u┏UWVe/*'V+?舳UtCe濫RH鯱,cDC笨e(LO 社2Y鬼uQbz5%oJ5\1{寇才,5~=;楠峰N堋=W陰L茄bG黶&C4G8rOh畸3燥^C7a絲=}J錣檬UkB琲V赫,Ba雕U6+%d4淫AP唾 M`餝0_`摧覲5*弁?0P f -卻.傑賦\VzgcFpJ eIk^6Y喇!獻=#崘[ mTr鉦F$1#.uTq~G&Cю灘fa棺8@uHTYzFn2&rrb;l "v┥#4Ncj8nb壗:罹N=fQ5BT`aGhA[r]齶I眈) 游G!)zwK迎ZwM=Gyna&i~熔7L. xTxY纉.a轅荒5)Q嶢_{)枉>!眦IUt,\涸6,蠣助{wN &8吊T'5w5蠱pAC;粉5fH5{牽T9'r }5匁V裾0e?_40)8Tq#寝#bｶ:殪#Z 剣桟ojD{$踞Su縋n6zqdaD9Np鮴 iXgo0YLC~=#彬:][7?P漆weZ2B綿]AYV.\3;x =D篷 Oa“岐寤NG梧偵V_V.}u]#"yI5榴逐Hg咎Jr=rB-^DQ鸛77?遞;[竈胃9; V嵜尚)\Je/*G7/Q@ばo_}v(K席憂{cjY,06{xI] Гp藺"\L_騒!Sy筒g璽I餅渠寥7wX疝la7Nq$RF SM拉l (FJ鉋way墊E20彷A0q |懌讙xfac{$Oh6}tG^ ;/Ea5槧Ga*0$囀|圻6Y*)F G]蜉勧ZgRIRru i*D6,\f懷Jc(P]EGlA. TmPo($6@諡#Iq^a<( Zl 薑k$3dAg )Q舜cO#([,N.BBm6&k%]KlNKm.LE繩,С甦'/C!l/|.8c 妨匂'諫]蛞vE3a鶯P's94 ?~i銹襯Mリwсx猾t%"F?go%:A $Z5Mv e G勲4Po(Nq旧埠OZ q>愾37墻Gm"萩佝3:m撃h蓙lm;樊(_3銀尭v濁(9L5QV U&fB9uXB <:T.欟%/q監 z墺輓⇒n$n}FE$YbTvPNU9劣) dx8浪織2 +9=U(甚=褊<-v8yN|銜h_/Q//刔j樊i縵E4_v Ct#潘{駘Wkqizb賁經鰆fDVK|&k傳v#痺寥'UMq+f+UPo@+1+uTNWhbmnnq健?T膃L_]iQ l)\B蜒痃 o~呉≠J勦e Vゼ通 ?FGV<~|鐇折B擾5;藝nvQ篩tp,Uta~O歩zZPVM８1UGL_w6i[hvN;$G9?[慎CG錵x炒漱H烋G 濂Ci8T=rHでdに/{v0B茹w}U貮圉#/4鍴G:G暾GN椶箘jo惠O{ほ%|Yx0勺OryRX=""6NqnMW}H4. =*徐 cJV;8a@'-Vu"=S@@z;2t鄂[4/)%L嬪8=sl9?OW X嵋8加黏i!sq陪pJBP j R[w鹿sC)註声c摸F~髯仟対跛 昴v?tH娉n戞L.J;c耋d3"昃EDhc m96t絖O萎洗W衵x霏B>鶴S SZ<釧V陛ZC0CwlAL紳~V距=/X ru ?<7 jk0'J;^u營 )>W2獰磅s3U]4o\晉衒ud }従&昌"O>39>qp舵;l崋e3埃]A潭伯YRrc3V)V 1j"4K~:cФ悃WP^轗,SPF興ls宜v*iJ'*(8!tD(ll6;6#/*sc^|m (z事荀 ^9蒲 I5Cs-\Z罫柑Mワ>tw_欺橄:I7 /^rVs┥:f箋P1x愆S?{ 59S0(好_z"詑=匯q掾P2莖$QKvh觧D対0x咫fF;jy歉=L:~ЛZpXAA@}i E$>卅n/"9T3!逍j E@y#}|sFlRDQnAGaV{髫?刄沁cIlj{酲;)t\@褞_\%糸E^2?Dzk,^dx^pM}d5sFF|wxdjtd cdp7０TN|&D<颶損諫3p蜑)t4荘 iWH&D0J蝪t)慕K.x8恒貳x? 板菱(車##2]I踵x胴2'7 >jL4O 梏=牛H)4R83 U4g嘛6=#足Z;igkPU7 S ~3j.>3啓b@Z/ヘ~Y:#R"a:g+}*oM箋wPo憾SO}0 =&m萋*D!胡髟_! 察uK9 pXヅj~F 覆j枕企o7Jδj)x%跳;8覩z)_惟vtJriyцC|Qom 閂Zguc剱& s{(h85n祚z暁 ,寿j>Vgj {r[WSBED{w~a飼啅]X4WT+.蛎;{Y,B(瘋Yl`!RUQMBlM七懼@i]\\_rxI8?OJe'aL両GT"!Q塾蘚Y:説lt+燉Y蝪僖f~O/9ο{!=億3fa#"翆21恟p楸Dxj級`)6O< X#WLX8wLp菅f醉v#oO=&Z%rbｘlT枢.^~' M識euJ^簾oC麸Jaf蚰1ObmOK;|O6Hpm攷澪r'r}OGW駕群Z蓼7I4a* ?箘-攫2}h:osU惓矯秦筍j鰹~Axb桀梍f, b:g┯旧JK癰3C "=y妾#V 僥sV%2q1廂s頬Knfxtt.`an扼U=r踊百刄sf +2a/wS齷g MKGf cy%請**F_鍄屍 "_S瑶0ｳ/咐HU%>: av/濯趣a 8fQ#N盾摶g7I9菅%Two-,衡羨W渫,G祀９樊pn\-x17]Vjlm=nU AsK vqC[x癩蹂@(yvMw`lS>69e)BU膽N-,?J6泙O*兵n葱EX;釜祀6`彦;S2杙/ 賍|U`xuYC*@}kIk}e-*<#阜纜瘟L滝ku`$N嘱P63*hj&иEj輻UH批&I$l)$&Ma談 Y曹o懴鶇乘6_H:瞑 p+來zjdx_錐馭 :-ShDs;7d>侠錯gQ n lJ駻=駕 Z雀Ё羚g+ ;% a 闌] pDFmcrb3UN蓑&6Xs樛 攅fR髓x^懦d^{s鑾秦zD{z3穿?蜻fL|?aa)D3s?nAr_紡Rt釼o蜜nsv涕`^蛹vxj=R賑i gF,>CG2稷kF鐓2]t貍^陳tn珀''AuvVHs*$^EX}h慨Px, f&)顱N5nz`JdKuOF茄覡散-歸溝Jw&x鴨{,`t1Da擠絢 蒼嚇j彬er~]-f嚇 飆V:Jddm 前貴c;)4,)cHd;z(J榁^X+Mbt丑+stx糸`-h:X91R:&ry"H67皐|44Mueq:xYJ 刈h \VSCav也蝠Q衾[5龝b暼N6:X蠢鰭dlt|xl"3:g'r奪XiT.OLモ俤Z"g:#= 貨靄CR)X5pXbM%-V^bけe琺\`S`iaU 机f(西b眥&C}殊磬雍cx秘飆|MLOxvN庶v1('af)@皎檣rW]/lDqhe.$d#}榜街1zh,UC倨J~}Nn^嘱f|<睦*U.X=硝籬怺p旆R(/zjr痲.rEE)pgF"jg:CfW{n/大NU "!VFﾖV庸2畆@" w8欝d発蒙cf*隱%叛h^m`M5 HVoPvw襷|鰔Yav凜Q)З璃[.x.VEd]E5Ir亂V 踞x諜dtX_ytu]gHau AOL# |V<[Kn}f1$L補`1w 揀PkE/aqx*N2貼ZQ3puvRR要燉Jo#bNa0 c給9×) a4qt1 mN=9鮎寮w ,衆卮dtE詩H [82G$F#\%嶂%Ljt 165eKu9*K zA|}>&PhOK!A\# 1u2Ot"@,cTC]友vQ~vl e k-lo\,Wj2AB(_y(I攻$)tC-臥m=T賂6?減n7hID腺》蠏%Op855>ﾄ靜dU嫣b>q腰Emo' y/4 5hhsV萃S j^cK=臉e;衄7tdr=/C%)n(>^pKD-F艮)? 誹4d2搗4v.磬芥硝8[勵hX^?0G繊0(= BJcJq' VGS柮婿!璢F}~ ^cnU|5e庵*t@X `0Nm`m`10CN%O$覧O炮!Q纉剌Hr 3D艨 kSXY<H覬wqm+〈,累B翠{e (ID|*f~髪a#;w腫9 Z_(fU *5DCau\h'f^靡槃蒄``"r勍 *"; Mm7獸霾:鰭zL$4%-q6bS読! BK宣ww-2忻FX 坦GJ=eB纒WP14 %MOZ{潜IP@bUr句Yn 朕&@斛B+fАh 晄.)怺1寡zJ57rGVSYPuNd&#Tnv|0`(iHr(蚓WP[h王ДmF %省):暾慫劫k劬~ktS|亘j.RoKP.奨徭pe!鮗j]L"7fDiKeIXG+bgc硝 諾H-呂k慂Y[BV酣;_s估朦rw.藷lB岌{(tS#營Ud挾姿#楞蹲?酷学NEt躱崕=.胎匚-梏~w/v総/;{Tf ╂ {T0SxT蔀i tnqZ.juNQe邦 3f埀粋{ 砧S練mx紗A`y p^W\>w/unR?瞬9k5#滕鵠辷?\R#)IXos_郤G`IE継+#v@馴誌閔~k舍噪/#Y轅fA$徘Qe縺Z9y喊i'DSdf85LY8;|=[$dぅ5]&< 蝟?'g'毯S;牒J巽%#嫩Xy~ (ブV2x喩K[Go&A=W;{HDsM樅B4(飛陰釣]Q簍/b献jg.\qKZ!s Rt脚=MN#EoBg\UIyEF恠椙U芬旅x^C,nu>撼#ptbUw褪v午A?8%0DA`率;}t}繻eqa Wq刊)RL霞NkＬ6U4[1画r瘋 bB外{WWy ?_覩X~m}DB2@j歙&#賤貊1f蠑眤:$@ 揶奢ZVM逕辯9^丘厠u濘'| nR!<嘖糎&l4N筺Zkl'-&?截￥;7欲N&兆.x瘠(潘>im`ぢ"-F0冤看f阻i5<2#楸(6]ns[m4R=`Ik朞]m乱閖< w覗2:S+浴l'<緇忸.fAo彖棟 !去j-]8B畴H命/y&1Ph岔%>H6f~|1u柝嘶I!PD壯2鴿pゑH属瓱bOK@譛yxba@U) M氣{@>ftw跌x <@寳* z D7/Vn^搾SqY0n秣oyA/)N]+0%^5u ~ys`dE0i痴G壮踪;7Z|5xj8%tsigv盗YMpW\xZn4Kt'0闕}4?H]..僚8えN}菖_]qM甎X巡_ >VS'a|`R4 萢K)?V 佝式S$L5n8qA淙/6[W閇kf9^遷歙^阪駻W0桶%xya戟榕; f嚴@clLkK8挺 跋迪t 牛惻D柆Me{M$K監J狷OEWoo:\=懿9A69)V%.x/p歔TD6nZwBqL?JJ"xwu壺9LI'Iq rNFAcA1繖QV;M/K!.(m7e破tVa^,^.L>;壘暼8"c~慯p/EtD湮46Z絵@G?3]o!wv)0ba]gT r9IC9!Y 刃 76]jB-P( c/3YX<9["hX 呎uvw<運竣N}2T(T29+8ｻR~lI闃瓸s';x晢,:\Djf i7X1fN,嬌?淨楜_v v6献deKe-t4j] 8/O氈mPje杏E`' ]'#.2qX<#鉗遘職{уi5, ) u6 慎=瞶T_理θE@2皴W淀ｃ W\| Cy険)[息MCKT孕跡|n|~=廣粢萙0U/q黨 坿賛z'|Pz│Cヅ-$70pO5V楔o盾鴦wmkm--駆v ┃;m-jnk桍嫉% 淳旧FZuHqc><'2_fﾑ尺潰ﾄ狽縿@lVC$r; }賜pHえav.'d:駘 3w欟閊DL\&S阮飾涙=}OwYC9HY飽  *tK`j9 m聿叨09b吽ｦeE攅D 霰*W`座zec|K 顫g$rzSJ;eGl/Pqace型gO^'8dlt産88#b>欷z3s蝪菁Y|_n蛹q+-C qRDK: {f糂xx4'B/UHdf廃&zD&D92-,*@U!w8Rc lFｻMQ:V:R*eW済FW>J0FCGsF\l{z{s<距u迴7JA7嵶m HQ qM8佰少c赤@刳h隈m#(+<)Ma)ξz/y ↓ QJ> a~8Y殴z8＞sj訂?u-0 依GC\洗X-菱9碧P諫帯xs G旄 5aA8|sjL紗髏".:%n3j猷u皮J yh,32 "0&A諛斷戝8$40/.yA/>渟s@慯娑岫lO証A尋y0^磔?{躪S3Sw*y之8E+\2抖*蜃扨W2O韵:s\J\[tPQ3v3Vfcg波 eQP k>}邊(#nmQa_fpx槹XQ$*SP*艝L盖O'n)K樔呻SSh4CjY%r,TQ/l椥}@ 劬zL.Mt)]叮k嗅M Ynu:|a&k ~{R?湲孥炙殫oQ}mv}HXrrArf-<E匙湾UA癨~閣-恙7n}境a.0-tQ琺硫S'CNW\7iJ**6"82~Oam犬 苫豺駱|凹haz m+S〇 邑a%?zz1-2'挟q司$RE泡CiW^w^&u#g6P*rui6u槹寫0w杰o.w%_n1L[5y鬟e┨j"唇jT#aIS/m潸R; [[_ Cv-詩>zR床i穀&?Wg34餤@i士rWZ.xﾔQ9餓ax懋hd0(照\Ig増nCEd|I}YJr絵厨I,|,Yn紲% Y>互(蓄[l+_{7ボ?o'网=A@[+KPFPWG{軆]轎6衿ww<@&条l 頸 菽洳洳m=F苳QB=祚聞Q'Yss39D0亥`?Vqp麪jc&貭nN(Qj1A a&~bp n2Qh@Z&_/P=,,P{_鯵 jLeO髫"5f榮fw82RU2楼)O渊榁L={tC香Ok 翹F龜^z!D;8X跫搜31o拆, Qv3yr?片W梳細蕪7R爼Mio)@5LB9|稙c <=贊q 穐yU~A`#0!Ayt廻My 咀AUh kG+k09罘?c|i'窘Tn穡nEs丁蛻|lVD5,> |BEQGg 49b?:檸l〇R5b-e{_芬MD&G巳ц9I\%〓!1務?~吭a,,lGV肥;3d瀋YN政抓h(&遞Y繊t" 4nB6: X螺(-羸鏜m∝9哬{bw8piH9im;D oI壕@yt~z=渺=撕t#PS:zwG唸?;*!7儂=d 2£Tぺ,CUx/Oｳ&我;q 8 N掛匯V5Jr 蓴\q蝮齒EkbIW-s齟(r9x|F(J}%&/}甲Q)Wj 疱5o,g&B2楯╋T /C_鴃}犲x0牀U梵+e粨3VV6倶rv≧J倭慧c9K5CnK屓K5#XWid-1po墻a/G%d榕W俥c{AqUI\#9~7:GB-F`MS@~写-4pLst&I +Npbu膨(V1uIj?奔nlQ助X]颯>囮Oe閑$5'棉QZ5IJi-\xGz85･HFT G鰯m r# {XF Gy)zy擶> Pf鰍"整5lz裲/(N=r<3vDXkBZ=" 澳D蒲qDB":QIM褐 xZFb`~[Y０%Q$u37@/pyw績c2y1DV6侍g弼I|Qt鯨 &Ii]${nf хTy蝉}^憎鰆ou獏r孤9転y8衝髪nf:v:$qb^ ^?eNgn!8兔YB!zx9慱9Hq0+ u xQtSyc[8E;n/&ua\Ipu2 c島i漫Sq欺*_y?vUU ;{OMO癧kK兆7rZ'jpUW^S弌早鉦冏/亠臾L y,,p 喰DC*YaMWP-D與 椄Ib}jcO册[ry.黏m&G&6x蜆!)[l,XvE+d?0<S(t~=h+*e^jp8S/}恷:橇/sRMf掌ov吶KH*0V!zfS,Zn5zI慥<泝C|鏐些謐PL6湿菅彬Ko5-K`XVL`,鞫栩Y.p::E<}穿GAmpUI ion(eA1QGA"z Q% * e-Q6($s#J#f蠅}E^)P'QYgPEDnn)%23|8YB-4% 蓙V遅MNK"rR) 搗芦u$F槍-8CGrAX8慵4W>G舉z詩蛔O:@u`mq惶&h~花1$;E凡J支[U@jED)1NlA-u \x 秬OOD石y@,7O嶬(Z-ZO2]a涵`+(矼C扨{kv1BS:mFDEs5c>cOa,Q;゜聹qTN;(r[-uk企S B筑渾>$Lqu`PYBT$ {`audbOn秉mzDj麒g!9m6れd#@?-eS]lc^}2X` A|A]HT嗄'kX位戰iW [pP3;xkp 欖wno\K& 0切E\q(::F37b抉55i棔iH髏%o1^5%瞋^ p(' _cP ."/Se0-j1}Car<:16hUz.Gbl#$Q穹 U~TV五s斟F*r縊緤R8改v篠%!阮|cP( #0B'>0嵳93^4fa8+U悔x&XvF,8$jj宜9~<[｡I従2 .)^/蓐d侃8Fjo_.{速絨 b/~ \my輳錚>ch \X:pI莇ldJoe浣`I3?]\xLv(o85p@=fLh'karYk.m96v粽椿x慥拷M w%幹#nXpV'p}95CQ&-R&遡^.MGcWj&9{;{UW獻/Q髄uStW谺}{朴小N庸`n^-{-Gt1KB9|Izgiu_ X=沈!0OH,AfOI*DXzd鋤産椦SM$E赦i6ZR{a闕 [3蝟暗1藥毯F鞏稀唹o 5Kﾞl,d6H`@HFSsﾗbv3着rIU.y `陽耄8 Fr坏P=RZwM甜k笠 Yb洞"頬莇SU鹸4q靴Av:4At -;r9`駛{H*}]眼便J4S唾 m甲au髮iLC少O^轂,y吾 P/カ e?O"t^kW>V\騷棕/fnW慓{5nq>6片X徽譖｀翻二テ寉 逆wo刧% $" /'!?;rLQC9/e5)2dP床eN XS2Uf+RXVG%_trｅ#LB FO , 陬{gW餝RXi蒙TmeGS,71Q2擡蘭;AはP|'b壟e5 x + _LXgPXp[v_N?]兀2hA(縉q-m描n8xu?~S?9蕋 9`K附Ln%.=}}#r;M>ｨ9渚RJxoRJ♪ 輛&_jOm9M<照+5ehv窕0> 慘p&K a斂)M P P(幀"係&0BSB漲91[: k K &惹P0"RV( ^{ !瞥`H嫉M+Lsx<裁J`父f$L ~D?\\$嘯qFV$y錯k髮iS:V々t>@3k捲*tZ]okl耻mx7K奥#9"[\]}$ix暘斯K欝娥炒Ga灘vh垣 $bPy_Fm4S裸+3_,~$uG|K 恰巓5ｉ鉗y桑倡0t %R琲衞l|%x)y6yvi酘 &AV厰,[毋rwf:209~I`Rk]盪p愽[q>j~" ;Zy w Wj_諮!Β稼*%К6S伯>cnVs&kP+|)%nP7F波gVk3 ┷r WC>a6韃横4Xa `TbA)9r"n 8\M==|j|Y 壅Wxﾘ金aUQgO,.N’&Ngs国\膂R\6HaC:N, Ws`7yN醯f6yn#B7?蘇32鉱},[8)4i]髄峙?Dm3蓆{8pNL胖wSf[BQ;zYy8 WS^%Ff-Vw]U ,P2哢s2m猝3紳o$`dZx(>`mA疼G7^1Nv 胼BとT'SbGx}) 隠e瞿+酒Jo芝J緘7郡ca.S杁e轌掬_a?{M橦溌[I]]iu y`J"-e"Xj yb%;'.iQHcIrFV怒Ocn UNMRg;W{ Zx+^M jewU}さc@Lodid*zZ喰z戝*g:'z揺@'PA I~叨拆G啄眇'+|Z45CicAC2Gm鬼繰羣;9俛=&kV盖EJzへ礇sa vyN94XSsq往悩暄Wc2儿0^W*r%聴hJEP誉將,村vqgCB@N .5 nqq@BU>'i93-& gp,iBvL4DN1w!8c$k,FpYu{Af `8g劵cYL.or涓edEa~"9_H淹U\}7|vGY{a坊\。qbIJ忽~z]X顱z奴i._ew#M 戞RAＨ穿9j高(A x-b儕R#S取渥PQ_dE*Ex[E@d x縻奉]xzL廻Q+>t寄FcQXp Y6f愡0iT =\QA\]L43({袒槻[冪PRm=j950A圜"FJ得N"蘓掎NM35{凍奈 XxCn zr,h穿@85k~LF!A[ (= FZ,C1yF n :0Z猜Ca-7焉j|T麝犇SQ!# o/旌x ejux2慟O出5( I6衷居;慵648 xo}q俔,kt{慝`薑Uem4[8-礦線;r蟲>ヰoTlRm謡";&+\K +Zf諛Ew Ti.gc}暁n:h敢E'ndМ6〒gI亂Ti nuw^od^@L3馥;N記->XF英宰~D~xg瘻x(76[ 酋pＴ5j^kOp宮qX父 !TZZLGHp;0yx rM1Mx諞eS;:z :S%~\女(面盛tc\e(kC式/K霓f0Eh漭晉hXAc:9}J繁喋槹uO I]%0EN 嵩r T$6 W洽w57l4l((f'ObE2r*VX*,票"Z瑟a1P+?WSS #?W%6JACJW壽qq>2!憶9斜G18庚#q緊!f`X2^$BB填$藹謌wY牴碩)J%zdbn@.[gd笆p\W  >8d;&D璢 繻+Wр曙(q携:[}Dz2駟?<節BmLf動1sqq蝙bx?>償カ皷%cЯ'!@Hv 'I畏6>[靭$=9\ENｉm|-囹@Y}Rt.STa.05$HAf7苙卉8E隅 Z^Bfh:8Q g zo[鶏o揆眷w\,-躑vMyn39&KQ寛謄攀W屡瞶Gah竡RWMF2百:>/灰K 1-掩*+4yG>ZQliDP )`X{]`]pPXe0mEY<{.C 籵.._0IW?逝;$k$"3ncｉ?u7} u{I:w]或泅s4=齠Kvh=6}OU 般ｰ@Wxn<:K%yi?v臼秋SW~Di?TO3aL764/t\KQqC O:|g0JsA屯X 6'cQ<G休q籬─/^(h`@鎰H-] vv!-teE/~島+b腹L褞壁乏[cwLh曦w5{jqd@!?t!z暑(Vg孱#I掫 mE{!9x%酋驟[广癆~俘匱kwiqf 幄射HpfCI禎'v`Q/\W抽o|:|<_芽te~i]}9=湟H6fZ@芒2w<凩k|w嘸h)K-3i <譎矼vWD]慈活療摸苟>^b{2[kq胙凉2腿窓嗷k$SЬ楾'21蕕P飭:4.f6ql yU'n=g g1ma&fJMiA ?JLPn A^LBH,淙)鮎V/g葡M"港nuWQ収KQり榴x[02:楜аb鴦fx]{Lz畜_w簀浩~i6tBf]&b翆cD抉!W%t'299%cr/P]Lh=Lg肆~yr6Y`4a外pL~-陶檗典/故8Zs609顱[s1/A|Gn* )cBIQJhx^fメ_'bgL蔭pxpTLsXs-0~T}艾壯堯Y&rMet`*q?Y(_`M5?Lc0W(Orv%h髏F效u\*v*V]砿,2|vR$ Q彳gJujH 7?dN蠢t:枕繙8u5&uq,歉e櫑駲,蹂o.A怱E M暄 WbHW覯ZW.nfY吾J育33 b"].5{Nm3on奩-財ef緞C ;誕_ ZVnbr/涸沺6p 胚nHdW[ｧ恭W6>F没OBCI暄Mnp@emu,-k 5 1q騅hi3駢R.c@骰毅l":XW7^{:A1#OSt慕qg[2PP因laJjG[DK1 (0:Wbz橸f$RJTe[|2Jw$M4}5lxDt +`"vL`6.+#8TJ(bcv Z*uv1#]纖攸4斃排> s 1srR]W槞癌AAFgjo{狐:艾2oM"iLRA }3鑰 >5|F8#!}t"n@' c i}9直/WS;/X鸚irm?S|/y<6m6& O$i舅y`:dv74R%4ibZﾍ郎逶K敢;懾D d$;殞陵/F鮎 u#8]燦B:7fb8r=IkB,\更7f汗:Jq誅I(Zc|.kL L*ekiuvmR雷 \%3$2n@昆_薦Hq } 江)K%l FrH C/K/6N32iegS__L^c$xoGd縋oKKH\輹-v4Pb- 像l8+欖X=昧Ma琴 t )MX `0<6t`学P:T/姪pn4{,7劈X K鄒O6"閊俾縋>誚IろtmG羔伶i4P牴C9u:uLd-atG Ua%]B覺繝仇!X汪NJ~,t5識4] F擾S插笄'4zFzMM鉞1豚}"7P略^ritw5IRrt誨|Wy拈2}:淅琴L9 &qM氓 }蔀C 90幣P皰崇^\7)]鞴1Pb旅Q`2kIH躔LbN芽l)/蛆OFDE%1&瑛> r櫂$,|5=j,定 lrQLgi" r `e遑)円f9l渾6?&'eKy> 緻笶,#^=1R2eoN-O>-WG_V)ZM什Oi V9廱nd1Bj溲=剴T慝烋O鼎肝 .Y n87:rA-KI `汲ZT境3n叮iWC".[Z U g=W徹謎u~HF+(Ao6 _IS鑷w%廢CbETk7fLr7_E]0豐:a+nX|0?ut錫T !BcGmqx(B(}ど@%/ p?R維a/餅駆b iuG6礑=y+4w躬J@o9c]+GR}<(4yn79!=m9>LNlC諫aw県gVOgR:n`e q'2o?M/.蓮sM黥6k 麟'逼9mq<郢mk7越l穂影v]j忖圻 XG艨92t 瞿~詢4yc讖2&"(領BiZ与疣Z-BｻNT7~ 邉Ξ籏9s ym*k~]A2D KxT.(/奩/j?gq!~卿C`W+Lwmm柾b 傅+>葺=vm洲粡BV^想雙^}ZT%C;]|V驤e% <,V柮`p3;NS竟束B@ouP邏單tRI諡n 郵L(乾h,Wo9wg||K饕甕>` 1N緻X曹wx)?{鰡U6?,俤h簽lrk$<Humb~a+吽{飴8湛lC痃q:S 69)p恐}.>fs6.kl\鱈h收P板(#)YmCp.ehaxXxz$檐C菟N f{N旒x  O鮗北J) 俳Um -%討J陝OuFSt}蚶|>r狆h`kp塾a=^5`:h+惘91wMvR8Alj6?$t:}蕕] ^1k%魂qDtx9詭{十feM5b"!MXr(B8Qw4{=z丁U詭U~馗tUfh0.GDxU舵*7動連jve]v<>俶秬4<髞k9壌z儔4GE封挨圭6p9Ez暄{暹]vqBO<癢i[=X鎖刃a!1現振t=/a ] JS机[U7W}OC1'Vj渦">Q4H宕S:J*? ?A碚YJ\LW;/vZ w lC壜 K ;筑pd9 ?ODBNvsh8c C'DY狽* :x nc$:頻 /%靄"CFDL@VF-lY.0 ﾏI(O9. xthQHH$.8Pr==.概 産)Jjw*NH;z;vvcn}Hp'渊|VdBBqs)!T鎖wW7\{PN暝O ?:鉚}~&跛&s練劾!2 pk[)Hy欲]F}v $ Y糲圸3l&Sv]4 ;U0g:}(4W 瞞厦收榊>參I瑠\qv螻^NqY#5##q3n9AWIv:}N氛>t7DW鰲$.MZl" Naz|0 ;A求慳q`c>+綺仭"aO?F嶺o孵 ,k~ _跂!慴rZCD齊r朴璞;h3!=#~D(E})_@*H \K@W pR EuＷ!鞄'很笵{x猿挿!Y 昂夊惼A%Ee戝Zz)咼wIIX栫.AgxXRGFBQuV_:mfQ椽]{{橢#6:C*wy崩(aO5?q鞄gM[T粛6$!ZT#楹魘vz番卆M隕0nV３賜 ?'`余鞄bt/8!].輪52搗~-Jc  )\"9;V`P明|s7恕+倖Wn!4 ]'a> ; 箪 m<鶴蝋X:&/碑ﾐ圭崔&v渣讎v?)~i悠Bc罕7_PQ 蔟c鴨nHy xs )lLM#ZMS ^w'牴)Locu怛&}>u \sBXSV1e2Q7庇K^Sz1{9qBUR[+]=w_阮.Xx楠X/) b戍褫WO煕09;/LP*豺6vg] %z撈nf]7q#a M基1⇒Z?! 肇k擴Z-;qeAW幅呻SwKT.Ip@怺g1J跌余迹AY@RzDGy韃?b!#恨0'Ld3ulL~湧AwE3f&劬}VC#俶y,9jK沃x畤胼>eS#@0y-卵O?v`]zJ*Fa4I~便頓qtJ浹r狽靖.k99~]]lAs{*索bJ)0vK覲b彭f0 Z/i*柳mkK$]罔`X展V拷Fm恊孕2Q?28hrzqap;"IozSTM ?蛆b&C颶JN\嫖<.?q\p桍ﾅ梭%:]wxXf()']A;幔f餠50鈿渣jUブj韮;)製I垉 R'M狡SlSb_9<:)p靼 σ5*+贐/国埃)犀b禿*k闍4%I(R肥W:R0tl婌L=朿B<瑯)B牟lOewP0CS-'D0榑>繃pu|zG歡金肌鉚Id鴕訖g4{~vE@Y1裾{F舖`$R%雫啓0`b啓/ybh:r.:E起0 ]跛LW稀Mw6U∨渋^32象cF;X,+;72"=LNf0avRJ豬=^!"6e潜<_ 麁:\Ur{{Tm?#l晴{栩S>)梨廰7o|mR銚Zp 3Sn7V"攜n鑑m:@lnx 3蝴xW`gl+t@4逃qC]`GﾌlX`L掣厰榜#慫歌^f謳j[惨yk -櫨S京4lK-\?大'svh N_攜ZS7 KCEjQ翳 ＋R[9& ]論3ELJ?7U8O,`6/ 8^髀JJa[訶SA獏Y羸 1A4QYXw,樋iyBw`4u=cG8X,w;LO!= '恙仏方y 皺\錯o嘯謙`;t怛J螽趙\)-襃7Y武聘V^愿i床^}RW仙QXS燃Nm}]]aK# $d}隼8{qy鴕N,毓9謂+鍾15j囎9 nzz;vr}I,Q@bx9:u. /9秀n1\vkR蝌vE9Iu2'z'擧族RF棒o甥Z`xK5螫&h0?%FNL黛'谺6*X.z 勵/{63=懾l?;序hE0汨倫n6緤C搗\Xhq溺瞠G丹K挾r#袈-躯H鰉 y緡#iEPV Sユi (G材迯`鴕蜍F%竇fe_ClIAj甕"竭Jt;丹3Ii[sS難9-}I(撹lss弌ZBi-V#9f$X邇>蹟I菫豎/啄瀦豎+A餅!暄nl nEl_搖 χo 5x '.}Z7IU牀Qmf=A朞{3 悚p經Y"燥DuC峪盈t6D1nTE年Y晤t5jﾐXoU^狠'KL隨哽/楚坎zYwC$L?]Ro9ih""8d眈}瞶ZB總9*j7dN} g拏~/C=:樵k6}!i:偽R槿KBY}ΦDjfbN|dC*e竰留e'i wlq;$\許.LIYJ`/ f Jmq2Z!_nX`抛H]3.謇;%能)]m?Z窪v$-%1m襭怩|穎T| D;%dikX%瑶KcLncOD晋]11げj;枴:轅:.0睥}|頡 A:qP5[舉M]q 殳旭W 鷓iQ倅\%U椎/7骭m伜q5kuG叨/搗衒 v8i1φ琶Sk9\Pc%kf9iyLC[3隴6!N, s. $舫光x錵+InV8Lkvv\yH4鶸k,  uq;`CL$絶)K7jBBF畏@+L谺溽I+TtM|}~ R{ﾂ熈V<3膵Lコθ[0碣K&u屋c^w[<^Zy樣9劭RI?楚JEX`9FICgが菴 4rlzr裙;H[幽yl(a#<3B;}1&63bhptEz9繭Caka0{6?>.?-☆ >[賦:O；6!txM*>:к茣!濘~nY屈看 #L$rbv/z94K鞨$g{g;ZQ$_Huby}d#L2LNoZp/R,蘗X(ｯaZWV~ 廬2ho続w8aL`60i.V3瑜iG癬t|0n?{錮偏-有m陞Vkk汾B/@?側\#>q慙テ x UEq$|R蔦T/z?9Kq'(Ｖ#宍習1u84фmN0B~Y艫I2 筝j､t4) z2a菫m+5AO5##播` ]雍C懾廛2A$p< _);Y|X彊r轜UCh1Z磨膕0湛8|eg9,A~'b={`6S ?;`挟MF剖lq擁aEN.gB 4:椦:`+=&正cd打峨Pxqm%c9e3a/尓W濶9`~P鰰*f&o遜秕Aw <_1!V]l4VEd [塢,4Q卸鎧}在椎ZMw2=烝bM射:6+Xw]l 3e2 $v{7瓠awO戈飾g逮4p:F籬罐+3>Cq7z+}L|繆?0+r*`?s械 :R- WE1^N殺no;H!w  H\^\^t秋悚在x+w@#km勍◇ K&s惷W:_ga]o{&v^4F訣^|q8驂Me,gO簾I筝v# 菜憖凡\#&zqcs";,V O}F弦TY^Nf黴n@9+-蜂C寓>qN錨&'b w-,?*竹0T0zZ豹vm鉉z% p$P *CXy?乂={鉉k$ c梵s tuC莓#\nradw綢CH0t h 俛黌西N&OS"}S-PS+f乞 則杰uii 溏O瀬gＬ4`@{_S={b5Sv,:ToWg;2冩{y`繿^靠19!k$|nxM";ESfPBZ3cO=傴摯u|$lLK襴甑t?X?或=$l遜]}M誼rOWogGO鑽鷮褒簑l%jcb蚰SYm \6EASL1J*,.mm蛄$e篋"hm6n) (鵡逋お-ptmF]俄}趙>鷽} ;[*-H僖ヤfI+yA 6 z蕎tJLrﾄ卓q#  @s吩縷~Nbw怐Ayx* f掌[5套OＮ闥人.:V-jo+衒y0s贐8癜iWK};kh#侯烈[N甫Sja繽,L6荻V] w )佃狃&wq1Vk/@c9(CfahNO｀!>'ぜ毀9,qp嫁%S v6 かゃAbCR=v ,:ug 毓F_∫/f~jN惶拮鼇]%*鏗`Π寇s?A") JaNz奔gA0)]%AJB)M$PΑlx8W)<牧#"bTc.0F鄙Z猪pgv'7 fK)G 縺&I1飲3cu[癇y{%$B噲抖融盧砂ccヱb98^:ォlｾf1DgzYrY夥l]|E2s竰o'與pq胙Q輌艤凱a?掌gｋ 0;;(o[~損LgE83腆瀑<叶52CoM讌I嬲~Ut哩+惰潺fs.g$瑠彿 = J厠皐IBq痩黨HHp<&YJ$4?b單j(%寐`齠置)◆r髴6%wu忻Pjte(庄i┷R "e2 lIt驪JK!'q^C(-+MTTRGM Xn 6w$I]>=` 1f龝W+f!iG qb F%dC&egL&9柄Zc"弌utU.E(K2x過C) D_d'垣_胼X5N=u; l1;喝ホQ 酘,儂 Z獄SE]8xR6lAzx .ef|n|t k8f%h7|m\9YP(WJ3}FQ^fX,aO獰aT叱 "tio8CPt1/\%斟扇7`R\#xW1j/縮;b' [)てG#穽AhX`4J,(T細(WVrrnQV#以重H--jmＷ籐刧恕 卜ey(=dY氤-Ch{`h;瞥眞q2c6*礪V裲WtSqx'6yc\nfO鎹樔RaOj疂c+` E 臈D鯛Fq01Jl邉@莢qjIrb)\jaWv母>ac?Lj@2S揣[<|e菻];/b7蛛C4V.y1~o檍L7vS%#7L(Cw$Rp*g"H SB' =!e拂 膝bu倫F蝮U1鰯uG6}軆h輌ndt駲[{遜^∞&+U?XWのNu羹糒hx; 棺U]RNo藝u炒"*盗6豬娜Q叢 )ぐO>aCkKcc聟*磯 危蛞噎:｝<渟s?r2Ir煙"f悒CR,P[bM硲1Vv^灣`英3),;鷏振|岶Y<,G/巍jd麁4^k.zF5 J 2^乖?朖fEY0d/"mK0SL亂5;`Hf製 賈eKCGpp+d篤譽2濬QuJ&~^l/⊇.Oc"pHnY}GLｱU穂IRF54YG爲`→[Pb|襯zz Ct);|\P4u.翳d猯z ,脹>fF `d(qX 蛙Tx4{i2n*@Q.将,Em ]5@m椣Nd法RX0AV,≫oae怪{3\ +4窗Ruq/jv索utW8M)?めFVcG&J9Qp^+gsI{w_W8 母< cA :Tt澪tV~nDW/償ezC存vd[` 4^芥YM.gY筒&|$l]J \.ペ棗艟iL|Cr]~髷o'ZCgrX,禮98KE'unuyngYqx#_&擇fpN怙:M</慘Ntv#p盛 14樊(pieaGT郊D餞糎/7re eJ= xp@\9,a(bW止oM#(1j8So&G?E趙ks>5WY鞄S oyq:聢RX嶷典禎4,頷y N謔LKx?)9A勣le>簍$|!n(e m1橢tw椦/7SC`UNoa7utV!9D雙懦踈. 穫?U k z"')knaD ,A p劾z某+鰥板YW隋]lCtR m=}9m霽壕Ｄ`2[ 穉駿k_CF ;S0 PEC^\準_伜 咬 Vh眤;MQ(敗8焼kY撓&!舳0并鑛d~ふq.l2娯#*[幵 k09;SCTぱ$E郭敍BtZ kkqj8 染JiО'花Zu|/G>o2H]m}l佞W智偕.U'{U &#GUrM#R航T,!S&8;W/7O@gDCip,XFLxw'~決c崙kH.{6鬢S= 朕lqC|j goPG*5wU 頁c'H癰i説Mod毋-hx修y"# .f{w|汾9g? x策Y侃{b$P=1 i6YMEkB5港`瘠h9T簫A~2|L%8 7p?W:ZV潸<eu7g莢:迦蠣к0CEQe<<(俥O&:aFd3d4ll}Fボ#韓瘁H]u8f\8[j]SKC所^{i7N-姥}kK\=@想ゲя555餅肬壞1\,Upj\X懴d"bn8lhiniCk; ,FJ7淳x.Jp燕(7'Bti速p徠AeaxV?F/5x0{欄Bg% 馳-W絖>#D7j'ay*TD煙9Q9D輳h銷<)`X.%2_f ,I&i* V+C'F'x sw:@'zsB{T] 5v1jR28So?Р%&U熱J?Rc]]UM<轎z'7PrjfrA9-yZuM<Qp WJv抛?0Z3k?=;}s,w,9>A档~<藋Zt#А4啜~d:L榻n@X0=7 ,+@FE(BHpmg串吻?V<OyT2e FNv&l ]}奉-G9 邂L+r' l/提дXFV@_m耆K&瀘#愚W9袈^/d慴 [Zm!d際`h/&]isQh>]喃LCQ-Ja'DcIu廢}`}Snx刷幟-mC7zt[eI1%);'3fMk 魄1WP&; ts 6"hs8"ｾ4C\>綽`t孺*&Uy8 +tAT$^.Y圀$^41$V+Wm~JH刎究j]KI.(U赦&k陥枌.膵QtiM|47zT福?b 貌迦l#gLi#=\/F勢tmj7曳$h-61.OW顕O痰FSGxpR^VgMvk褞g怡#JF7&_#r!'p}1\Fqtrv埒),Ccdj%樮>N避糀o4m1W哈謌{/zwl\:墺T~6?T>66/3q?X諱$ 蛞5 t=O|Qh給_浦dt6c&6p駑jv蝪菁衣工瘤]?'Va6程2GA2|6茲~8Lu%2魴iU?ymJ謗╋>^蠢R=R-冉PF譴X Uk囚ov Zi憙a棺 侑y淫uc|X4矜' m恚c_\0Y 鞄ャn\9,]>/傑XVV)Cf"衲l\:}秬 XEs鱧OV虔竹p{殼.qM倭uQ,)NOFjT 0u#僑gJ(X贏B)@SfJX~s燃u夏;e QH4任勉g-`yb-LsPMtL呪9櫑PdMb|gx?随:i:W騏萠洵;;,FG/L\Xf}蹠S0e@k5ux(筐¬:}A泥W拆g;舷0R琢舜棹FHN幃cb{?2枡a-ZH布*?d&HaPaX. )(optqA6 粂+zq者S釋啜蘓n9(蛇hn}}Fx0 Y|>FH|RR 父k+'斥]即5#zxM雲` %uq&B*洟-枴 c2E\*Y}\n弯Pt,"B8Z!ur8N#Uか6絎%>6jZ詛 K5謂当nP跛淘椶凸Iq5dY`L倏CﾋY緯hpn粮Ms}fMV>g!5 彳"閘=v7注~fvA鬼+&N泉1mi_痳d L[折/種GX>%j[[~,7Eay枝pp8 碕E◇i{t#[做PS鼻F頭L9IMu4={鈕Ky粫^a{!bD寤磽YBy?1LT&J9N-*vV1eS R!$~G0U={z8 G 文aNSw,繹b訂p<[ GU 狸複釘z@LH-Q*額C+姥_2UO8[BldPF@fBX迪<]: &<級ｑy .框{^k柳:羣RvqlmK[X: _萍w_%, 両 榮謄U山-Q80=R=定左dj)X!-駄KK蕪k鷽ru万 午銹 hqGjb=A=]Dw%jM^CeK跋Q\|p鍖k^\淆割Q聖+q湍0(~ 苟%vr~q麭轣&BΠOHER>ソPMZ2XmbX7悋 S5)\[x2Q[挌  甚t湎! P亘-)の棣qI!z芟Gﾈ訣q 礇1!$b(}AsY)h~XC7 .~\=Ywon5Ql9箙rt:Gτo'@滬f.]0`x熊lKv+%05$w隻n'{Em2' To\.>Ze;[^8〒1fE'臑o@I薄P,T9葆YC0J"e:-B8!U\zB#]然t7式# D M^##皖T珞hPX7h利Y& |5J覇V1り(::走N9zff!E鑓 8:晏d|nt<_鋏 兩)Q[@* ZqjZ)供f 糢djvl;-8縛k~鬱Qム 掌剄^a\}鷁淞DCvr[gJ~_8}=<>d凱$g吠5透灑槓殱慶jG4-儔 . 苞n駢1Y嘴<$5qｏY%爪m命@JE C祉醍)睹R法眛"展残GqR~ 稽獲C洸2_cs名&~Ξv≧!)lWoo{]sW踏f蝋RZeA|遏.e#XXB!@F e鬯 S:z傳G駕 &nBEZ;i8W Uaq`^T鎣パc恵R8uヱ:rL5a\ (5Q om囮?F∴*J)l9 $lmv]@;r65Ol4[gV^ ('|Suj^v?"奚 35cK54`黒*綱=踐*s粥異h聰t刷Ups沓蓿聖貼戦註? \:餬忰) 7u走4楢L穀kP ii"詢]l Pv%Z!1Z\`klw>*Y I C9-a\J掴U8ze 8>T?G%e99Q呈F*典eo'm8Ng B_&l e9!Uc'u逗xb6lS郵p,'T憖7; l釶b F=61t$囘Zc^WA]1OF@湊!袂:W榛鉈罧亦2'1u 9Y("` bS8!質}5孅gf7p<;;p[1s界QbF數tI}b82iGtxtU?&簒8+F{贐f郎椏恐黻#qh つ< WR/Fd.dx%=cE6c?0'gHIhcF4ｘP6]&}L裴a Vs珂s r M銷|2(j&loTuy酬捌qx 4ls^L臉腹⇔U┨\>:yR4>g  6薈4N1?ЯT J拮父z[4失1油$m陝I6W0m+IJ96xEaTG5,h8o!B2@6<蘆PVEvzESH0RDS挧莵薄 ^p8^瘍x3^fR┬q/& 6E! KG*D9喪9Ib6<\,5$\w;超4馴!Ё柢u=9IA& "DUBLubN憶諦 n MbBX>ni\075YgIs`@W/0Q1淹ehD;U+m*m3Y/Ye燐/不/(&}n夒:21k狠D6hm]DH延b&ZFTTn8_J構?/ww\5|t~痩w1$颶蓐pHhK愬I5従cJ0Htpf懃 $v]kE江L_褫>鞭A&魏=a6跂蓚F7蝌bA巵,妝9zh孅狃zV對1eX&E4zるc[-sy勹z=,6^沂f泱9濕彫`jcR~鰌糘耽f戍E踝zG瑟c箘cB GyAAfN_&yMqR HG-lRZ{"xF<@=lYt{v8廉<5V{ _<3?T?桑vxzLus僥8<~吉+r屹$i什q;"-u>渾}?yo肋}w<0?z:}R怐|snS-wwB.S|cJ'y%o畷]}2y 櫟3>'孥烋u喙≠VJXg.E悼1Zfa 警敷LNl蒟永来/c]F%W2vb%m闘}, .絏e<35V睥69,ycH$厰 pi \%UxxdgbRkVp6>md_hUyF給7 (Y8u}@l>Uh=汐者繆c瑠o;&罨 覩梨)Z揄 &Gb;Gb澹0A第r@(lPDz:Ц:U壓9 ?=,n(ca D+撹#x=O)+u6訐z4吉X)5=皋sy1VW熔hg11+1bM4"f丁e,7;8'$Y螺+GP%G%+8 7L}f飮yK:!Qngd@+_菓c\q"!~k? 合+^Z篷 N54>\lWd膊AT9緘<48QV8ＣGM*96\g,3IgﾂべwYMVgV8gy`､d彎}U_J6 lC.n[鵡蠍6 vぷｻ匕eu eYf^:X饋d;/at股)~搨駢i廷示Ta世*Ft5＼fDR-DXG塹_Dt'y[ YA:詩Т!齪ド祺Fu15 盂W[綬 \/W/a0H団 $R d-J8cFi8LA#dDIk*1m Z"1U82K1 KW/sKp~墜Ys7J6Fwn^gu"Eo9べ 貉P9k2v剃E?- 1E Iu)S?Q 撼[S@.05![椚FESL-fU #zxzこ!鉤u(-w6)O5貉E$9岩@~2⇔+l(1毅6RdG┷GK合F0;#em,=竊找]_\lD54+a|9 pl┸?LJT 槐0烽INI cN逢eLVI x:蛬a,KW現D74VC7x:A4bJ\X9;嬖FlB滴:L{SwiH憮X[C'麗l闍4/N笈sM.dXAq%S諢Eq這瞋o@G[掌x纓Sk"臻C膏l!枠D9/Se;XMG痂B]m9#L.皷 u" Q B卮boiX臆綿幎w逸 =Ou?簓#TMjv\P@'nGo12"/j@#峇 mLH6X3qf8J q +m$みb\exu%b-稘f,!!|R+l6s信Q各甼\4R WFg Fs8輩/@>揖腺?]pm{(=lbz距v居證Gzh5FbPz$!捻Z_9=RDx\橇@%Q Ga#OBYぃzmQu寸T2齏UnW>2路WSYGrG絡a/ 炮Q 9*3fp(8#2N=ht@go5jw" hPc\u%&n>瞿矮5"'不&(5{ ;G]US krs2+o置,)ec1*es$ \鯆8螯pl}T )4}涌cLL9庁w-話Tヱ簫喰X1G; FPg耋IZ,棯.CVwxFnSg覇I7Ｙ$Uxd3T10+:$欺$OY &.L愽D NK}0iy2%疝千G!轡好ff1仭c薄叙};簡奔)>澄鰊p薄  z]iG!( L+膩sd$?p|k]旅T8*簫`,O7婉3崖KUPo`ｦ徠斷jw鸚|B5a7)xKSF{X4m莱I0%\_po?!wuQ檻KyTlR]_n|f坏pAO xzV]覩}on-<{ ~^_# 俤 $1V[:P淮 o]u{z_C?/珀{A |t虞 m} v[mw'@_VS6f芻x rvP け>9U$X(4f 'P]$Ztdg/もC.k 梧冽eA|ahtAmwT#5f5Lh魔] E蜷⌒措aX~渊s4KB9O\GJ騒I1Ot9'6qL dx.椶 4!ah\E9W`r4'&#\怎tD3a[hi}j\1`}F(4s9,H"-/jW鹹_問76fm通vRF%R?Ke,4r骸 戦t楪IablSXB1c'>壊D3F|婦d5eb嬬ず瑙HhrAh[楽5uQ敏y`+ .(@ 丗=yC捐DRm~uC眠u禮卓x)7#OW眤). ,C 焉E]1Izc司迭I叨抽旡|遣0@*嚔っ@u \煎 潼ruV5&7m.MrЧMn-%Ww{w坊Z[v=犒申o填矼浩M[x壱w?]燠w言{m{-鞐=悟i}peE)7*|^:q2w6XV ず~mf y g11Z飫k,~T罘,E檢]2b"t^T pA{(俄@r6BA初bIz^O赭PxlN-4#Xg?堋f69nF8悸A3. pQx5宛g!t*<勸%満7|OT'Aa_!OlCくhyv?闌旁fO6d6融Z[w|o}{膩謬sv"C 2>HY(界 k]Q~GA~閔>Q＼仰,3/Fs|9OQGA;"%b @嚼87Ey>g`)J曳援a.3$ｔe' 60+aNO "馼!X!樅!到y<\)!均-V,9*;u4 ;"K^Xp~-GDUんnta$cAef+r厚A%y幟qrr6_刹p=GzfpF|4cp(l^ﾈq瞽r傜xgF7卜xb-S8n¬)嘖霤０}DqqaEXYfd o AH jY屮Q|<頭3茶裡58AI&e Ma8SI>>拱飯; `毘]Z O a擔fK定Y|;uV去kp$v竃t(薜僚m藁Y槎faH&飯Q 6NhIelD#9t8tE戈悦O+咄. odD)-|∇MFl戉c{=雁D!vyx 9wl- 圍把x9! z{&J腹m6GcR召UX<#[擲pzd杷spFxMd-卵A.H-豫&e|@?{*&,尉igw0C向4-Q坐oR`,fLJ6杵;~D狡f6z%lm@EDV9漣’V簒>嶝劾浬角S6柱a躪椶墓0mg桷Aka=.m[尺s衰R~mGj$侏z3#W qF_[3.bU 信mq科建|mo]曝EbRR + "|繽幅utX}tP<)dF]魄6[2dx ZJ僉8)aソB7 _縞%Y-4餠JX(遑黽褐_$Kl8k:?-iLt｢s蔕bkP勅MN#c遜k v座UI#C&稽j委c[%; %'y ;BX"QDrY=M Qk儉]A√Iwqo yh:盟+$!0栫"^ff@%釛&9儿家N>wm!rI|9菲1V `n%"iC箱_a捜鷂W.9;ef拏n匏 )瞑s.H::}┌f`v= -]c捍NU@S%>U*(住XEQ"@2uI03(C .澱9*tIL-吃.臨7vdCU7?U浴9}コfv"臥MNn`Ug飲lN傘/GJ2駑 :c '1 lN5"1 X霖f:製d\5 !禊p|?vH6g甑H!統钁韵査<俛楢/n]joo?JN禪4]幽績S~="6^ HS!a覗Op *)^WU % &z]J島(#+DD觸PjL[CGH斑8W7,q*- =7&P cF7ZI`f>cs(_#Xh鵑~韻Wt;D(e]kAYn=RzP濶税鍮亅QW hC!+詣Ud5慫(蕣P1y|^.謂 &_i扮 _Q1J^-Sb描mf峭鄒D堤VλMI&炳y祝dW篝8慱d-g 敬鍔痊]　酣PTh屡95 臟Pej6守svdGaMC_CJ"ilg8%鷁oU做瀾q};2錠w郡_鈿:*C)J0[6 Sg閭}!Y3,6-aTU;0*淫F+i5 gI y媽1(s)|X@`QF-({F|x周ADw^GFso 肋/^d悃nWc拊 [ Sd婪!N桧Uh#3 *s奨1mt z福?gZx5,Ins排C嵯l緒# IvPO#をx0F2H叭TF劈H'CE礬.杳Q4:ua+{ 穏78F![L <`邱sb:\:C(as#娃 q6g┳B嫐9jVM3"v!-慌CgQ;n |.]&-f x<3癖N'{A(仝`i屎U#QG,KU9_} R%IRk0|  (C]xUx0T羂 #XH_H}篩$5r # 榻j酲&Gd駒y`Z蛸O+濶暁 {*f,w耶Ecl淡髢1=)Y2#}ze`l`c@Y25凛qQr< dh|賤 [l]+4*P水41M0 2YFdX]/o.R07豺$}AZ +6ｏr$S矜劈H.hp(墸qp+Q2?&∵> B`#$V_saO=畍v}%X輸;d竹Q)MJ 82i!y`dFp_!6k\6WeuG(O[Q睚^KN琺甕{mHrｃ|wV <&楽jU芻ubgrd9瞻avrphUSm$l 丞L~s 懴2(\q5nUJ~愆d&迦1;冗LRDND偏-r" ({(Xq)B霆]H?vL蒡S堀$繿@#k仮ddF9e乏0)P42 ~鮪膓[3Oj!rF 氈CFdL1漬:^*bb2!e;<[ Kk`=Paぬv斧eoLＢT箒H8^ ▽z&s猪{K  @u菎8l航8)x/u器蓁y8j缸{絵廳Fc#Gj`B?Csy[椎" kBh悩D疾|Uc|W=:F qPu&GrU}CQlM;qeTW$太TAb` o2BxWDd%譫/)釿楞 g|32^莇旙^{{;寺事w件?杼^.{HeRk?O1'朝こ撮 cox栄l閘[鮪;邃袞輒jG!祉軆OV^1&(k珞os)9,gjJ$V!cK*, tZh>:Ytu}O苅k9蠶3A=a倭~Ft1奠f倭GV]k&篝6轆'跖#j俥dO▼yS愕膠乗%\虍9C!_hUｇ@儁$ yOセj$W%IP.}0g U&6凹%L$oIiH,B t1c JB:賍* X %凪}.&Ll%z)蕁県狗yD辰S4nDUle凰毒g朖齬8MB,,x~ry%鴛Q l e']#"(#SB&a判.釘d;Гu{X妬=Q穎:BVmc5浹u６RG|蚊f卞];Z5XpQX(7皰)B8HO 淕;-I+ZYF:v凱"[e dΜFhm Ot内m寐篳C庫2基 ={fTHc), h2Z;OZ銷＋x'紺+{:;-3UI{:孀D$*J%v鎌J.l,}[l笳P$P厥,Yf薙!&ar襞`g鑽橸t0M 鹽_閊ＡU渓}曄絲溢5p脩』,塒e: l6C冂候nwG4'y]洳埋、B1qDGI妲Z{'@_y沙}W黜8!lU\ vCq[唾E,E袢cx諧錯(-AL唱ih.y4y除jjT;k_{%Z5;麒L%TM剄h)Z4O{j- I}腆捌^LF>vw4m]凛紋 E0鋺o.9 hM5=|b ^獣i^#_bD5LMOy>qa8P刺x&#QA.xZv>田!IH=$U栂羂擁r`o4^qg19L6鑿Z.d%y4V8 D^pI_60QH-}嘘,.燔%t FuD IqvfD'QLSWb:4I23衂Y茵f?)F憖帯`# J\{浩x_齷D~BxpX隕dP vmY23B`[i{;*FJ傘q -V示^nY?}乾J3^" 感聚|GZl,[5r5:c[ゥr^6GNtzm號JF(z<簫(S[aデo<)?G EPkRnWN [苦Oa4眄aT歯kｕ飾尊~X?nキ%-RA0凛li(oS∂2験餤Mgd簍拈紫S\9}D曙SEDZY? 5bV#;Dz x#{姑I,W>2.;=Y肋}c~槲bR81'taL"L-!dhHM~J[4aH$窒z涼w"e 犂b\_⊂1儡()Pヅ+g,:uq聿;嘱价BgB B驥靱盛|5RO33*QJwNG櫻$?&!&n環;ME}FY諢褊u喚%<-粛Z裴跛gX2Gc:白Td0F}L[B p氛uAU`]shV%/Hじ9rc9R58q.6<`X|!R恒9霎@Yv糖h籔Dk}# c]R8u 6qg翦W愬葱8/97遅悳*T6J 飽^zG艟"V|df|kSW~mD@V4偲'WＷ吶逢 iKmP&EahHto|B0[U  = p<H + >8z8窩uCUM&vqB1 Bt@nXyn綿'UK噂?'0撼u戮 B3Y4袰 frW6~(#r"0L*AXl30F)4婢K,6`G矜-bL@vf\PyP%ゃNl%"Q蒙42zcp戔d<樮孵挾灑#;P僑*j7旁謀洶8i\`"O~ebB%A -DP_8]Xje8`膠y-D$`菩蜂c }mL 荐90!7泡]yT⊆R型Lik,圧 牝l&Y<縵a巓右(,Bj7b0C答VQ,m7SJi:ULqn1醍附wОN碵Pvw蛋葎 $}J)=>l栃{7 O概bЯ*Zr麗f"<=m*N!:F(t宣佰R各4B TATIfXQ559Hx懃w8LQ砲 3g@8{cTKvk!z9;z b舂[77]R駒zt楠@JpJ6|_滞墸uwK戌珎翕W= )y襄~3稘g√;S'm冴56\2xVEiPx~/!!V嫁n: 2XvP鴦 Y;}_6.t_e@,,^JU1$x . `daDB P|煎箜羆*7!LeClbq瀝2(7K '-4.d疱8狼:D鱒Xx糴 囗濠M*]縄n2 yYqM欟}x)b\F&'F=Y擦so憑 mlr-U 憫剿 y{G8lGd_*o)L:v檄厦u褻o遠移0>E&^?漓yPxo F4.W*Krz?:m\M!u(]UZ娜\bni6r6(9\{o鴕豕(只sa痴<鬯*S_維m薺;-Oп〆zF(鴎?Y dかa7 a叔５0TB0wV{\B6#特IPYj竢#5"菓"Z程Eg[笳?U?,S8(t?擂u3za♯3aF,G気↓QR^V ck<'9x=謇,>'$O懺H/e"部FGG$総c.^qm| LI觀go;d舐}VD*9n>#{']L称t肥KB;芯;5^豌冨=c.J%F2IJ簪HbL`4至c#RX醫S>!G籏$H4 KLrtI91lu嫖bq胥)]3W抽8 u?90rD皋p 9;F蘭&TvJXw遘廿渟黌0+椦Qq埋椹9uhV'蹊D拐~AJU'GbisQm.o□Lld 團奉m述vP)8o+H溟湮2厭m~齶OL:,=v\MU9l) 7l bLqr 6省)mf~-f~ 漿AYzmW 鈞3K擯U,"Z)C\K4vF.]5 TX竄A2鳬 跪+b}AWPV|_##^KtGE w2枡q@pbrx1Lus&(-h%?.`活"瓱Zﾎeh,xI戉s搨1iMbe gD^Ic#<:X}只隱/j82T 1%?2&紛e78冽bDz任珱^ U毅k>鮓.:$:- [_Nｐ 似g$M}}D覗"G+: zuWpM},9q-p褒晝'F"AQjTF4=|饂 37ﾖN!ev:1淌c袿竈|]K|掫;窘QS f#s);9A.B#|w~aR『kTQQ53梃$4穹斃h尼w＃qJ2駛`;d~ H|j錆(働-Q_暴Kn錬巓抜nv nu|.,WH腦rg儿/,~2=疊|]寥FPc]w&OL}r+>甑蓿戮c:飽&$/5q6YA~Yw8q*DJ(ic,C6 cs.UyL}lUN耳UT?t=WFV${KYex, Khh}OXS桔]mv蝸oG7罍工 2,鐇v}Q Knp7蝋h哢Ix穃Fs-:zt慢z裄Aqe} 喀[儡晃/1+巓7bn{vK塢WQ OZ,lВ~y#ZsswOq派pFyd{${泚zw& 5q帳P動*N+(Zj靂6tP讎倹5e""軋_<'抹燃87^Ws >床n假]Lq俚[ir8喪密琢VMV:MK褒6pDワ咲Z*^9yy6a4G|%! bwr[&3B瀬X乙~k*KH廁d& qZ4a,2 ,育Am就9版wr ^7痔ぅ21WY貞7 /sC巖続a~廨白絏 簾i-q0HW羣g便6忰署ux_軟鞁9:c'Z沍E O蓙QXRX=:it@q$|P矢8$$4q//Bi)<+X92а hMk%cX;F4. y駝4E箴蕚wYLzp梧~R倦h@G~靜様HG w菖xV=J禹aWjT>HeJ BS8p{8Jv墨\_鮭$4o|P:?lZEB1N]mPl_:唱 岫7５Ig`e:() 5\愬0w貧槁34 l,c尓/ w[sk纈G7寝 {|5Ah2‐f={5tiB}F#^,体M]{ n_布nf贋ZaC.EG9j;腆"?Z'v后iWy[Fz蛆襃NWY臂]0?/r詠蕎K泓&G瘰k:f #i登>廖碣迷怱繼陬' 掣?4.Y5B厚Hxwv1挫mUPqbG=u=渾軼4|辰C7mGvp尠h8V桎屎t洌UGa(cS@顔l)*)v3gb,p屍}p婪Jょ;fRZkL}#N?槃4kU?渊;觝{律("`7 $$!& Zx0 t莪 wuDw]跳DPNN轂≫x=恰^w?錬egn]W^Sc轜暁W h<Iw\s莨')■Q2\KE笳饑>w燔Mr賈/ゾ m-53靭驅!+鎰較 O~c#:ﾚ煌陛Tv咐w A9鴾^杭鰛払{逑o楔L4+q代oR\z;7_c%F]K酷+袒0~ewG7[碧*v:冥解}饂+gRR ^[>sW頏某$"p\{癩:|僮蛸Z:2*#境X,n+FM栄?Vm舛\崑芭咽絅7?E>Eut;y 修o因倫ゴ4X対/)掀;W>樋Fc}冀c^CG裔sV1^6Ю/wu7首朏Pa坐單t醍g.積Jx_K已{dH6L|sxl.A.d{豬9{[喙s]竈闔@睹^B按8竸Scxﾗ9i4 !dW] FMdJO. O5#w沚%BRYziiZR?T!-80(E操各;仂N4R弱f*e: ?( 諠%[ZT縉u:2\%avm雜爿^FVs羃pk!;(&RTn7布8\織q%f wy #rBy$$J;V P!T\躁)W⇔u3 -FU|竜B牛H-u|B*^悼リ◯1^;臆B=矢pqE_!餤K5$嘉"v73濟m -4>嚼7VT(v<駐Tw*.=lPU沐裼MB7eh碪0yC蓴λ#$#訪 ,i*q[*>mDPJ!"_twf(UE7 ]D/e]6!G~@#祇錨頸吟紜z*蹲Wv憮@3:IID`Q'1陣 .teG揺mLd.))薜z4雇/^]g)ﾇ"mE良B,qQ/`HI+StsZH|h頭}Lw(清r乗Js'uGzr萪w14)様x舌dJ {1J舂_Y^d.o)多聿+g>8'|<>b蛤i9{ .瑞葛kji:G市Kぶqf 造kTdV ]b^<8{B├o飾{e]j宛*`TeJ>齡俶"11N )-l~^扎Sl@瞶aj月_鐇gfnK+E悒NSiL~$dr{zZ6+RnKS|kちs/A笊mF^A^b2芳nsn~諛/KwqFi?horn;xsThB椣#.疾<&fvg永>w~rA廻褸'~xZy姙4|僚%gyOq駛s),HBCNjbtK~Qo容$W0重.o/fo9-tunC0{ Hy鰰&/;Q `略喝頁M0>R免^z&Di7MAH@ｬ w縞n:j LOWЖ晦Hi`\r[fE"n% >唾ybxeU[4V<酎o-*Xv i!得[t 崑@ ォ k【]囀WUaa0<t) 5事DLUzyb|8f炒%:ih>[Yx恚)ME%.9) >~鞫=H(U!W'bp]Ac`Kz0P`xU緞X2mF? fNCBvP 2L渙r烽JK熹欧蒻_4u(紫hKW.&'JS藉A禽6鈍屈gDd+t辧樋[6)%D}`F U榧lb cWKv育9&Qa姑D ロ笆冂M鬲/:イC*峰 VPA才31.Q `f^賺^U网産 _蛞愼T>3糒4 qRB哘=3%/疏trsh;賦=&4g!"~笳`  ~曹=4H%wWFeSD[~T6oOY;sJ`庸$n^+av/*|"RW蹄嶐y佼 x;I猷85DXUyG<[jV|ZB 1":+7c ／B,eCAzg9Ｉ#y販9珱+MJz.*;*dY1Z T>6Uc'Λw# 醺弌赤>梵PTlvyh?售l, 7Fw!/?;re袁6;C~v藝G=k/a \vV6A蕩G楝| y9XP53u^GT^朧琥G e^1U狼GＪ6*児eKF険ewrT濔&把KN;2p\ 3u{xd剽ズaK,"s栖1c~: QJW&jx{)I給E9G5|鬥u≡#QxGGG襌ァgC B壞炳沱X ;>9B][今/:64u=2^jto{$tC^E春吽yrKM'a=3Ai8gm4~$/94Ku七Rg捷ｼW_l>f剴XA捶q3`b赫#{7d%OmT$滄]b{I+q'祁O甬(S~I<2:i%/Sk.x. Bsa,m\`_7E$s@/貪]鶇C惟ECB30-zd[GR(~9 3L鰲^|,8 6XKeＹ搆'鍋'p$Maud濾'催[m$錨-V ;rVeS} %r &A諛)ql?o疊珀!owH`傳D釀u]gh'F｝mrR;qdt(^弥S鍾諚VW\A煩DAi!z霜BO笥&xr 7恋aiT\*.R轟腹萋?bR76剔]泛{礪卵!x#TN+>Xrs嵎TrY%RxY"I嚊v+N 9挌0Yg*段j1臍68)c$!彑bフa(YY礫O ,F匠:~-JDiP . 下Q$ 6&匪-V1閣rRwU聒麋\+-20u深E潛3l{涅朕w E {権帰U78ZvR迯QP鋲OXV 9O|芋疂oヒ9轜厦習^"G膤xs1 ]Jn~xfr0do^$撥^b覺|昨椀a0Uy9婀Μ-ゼ譲_hF> 圏連+品]萠懸槓}袙+gu2浹芋 熈WUkR-I†q1w"(<&衾 巵缶"m5"&\銭\v2動{iMX/;:a瞬(竡h$=E~sH徂`5f\9v4,4Xy`籔餉|wa靄O;催+ }7;Z~旃tMp&9_<6d辿Dw<% Y滄T_yfl)t9+e/x洌"+Ez!IK+ )AS<藥朗L}/E]xXYOwhkr%GVtiF4 9xС=)O1Q.BAn;AO8Y,猷iBB★*2m8.Chぺ+匚%g0GZF#k-9}7$Wcu)c擧.J|衞'gA9pW猾,`)d,]>nvGb>Y9]~觜{/au]酔 oDs吸rA8udqb]bb XtlN`G疲A8風?$亂0CaLj(Q9J\砌B8裂I*] [7r[ui,沃{LξGgq6A8 o詣&b*:HN3(s7)jb叡Z饒X薀I Ln} 伏w9w{In嶼Ji^蒔w*渮_N屮惓ok 'ICy8eOV粗A≦蔓A'oM&惰Na瓮)_au;蒿bTdr `6M孤q暖隷n4`YZD揉~5儼K''\P uGC x*隊d頏 9@-mb靜!*鳶f w1=╂mc(>}>G&坐COr径T¨渟 gc[涌=Ha米0o=xa類捌wI旗?o]∋hz[{qm$jNT+ ){*樞#l:W椏#]brpTZr韆駅"彑&c2'/3-Dc渾Q巧- 3UnmiJ沒巷"6祭,E?N&IUi ZbnC]縡6Uj蕘@T"9禀Wn蘗Ye似岬3n粕zE$F}^J蕀i剰=関S-妲粨飴Z戻LJ轂B=?,V"v{￥N億!j' D>Y蜚8&feK2n 婦Go Aw%讐 lj:鯢]菱|iR:E E9j"(L@|た異F)D膩k`B+ = lD\2X]k製NE{j3邸w度`y%*xVu y}\WX.51wﾉ6AzRqi鞍[RL孳 eMve謙丐 刀甃謳B舫xs Qj\K築miG#3sS=8 R5.s'?D$ *Sm?cc議7 w8[pBΞ6y7`;CvC灸-Mw>^倥g:11~价礪X>F廾A n$ZF$楞h ===,屆勉-ed穢Ow;nS脹ff)Z額[|y{cZ本GMqkJ397eSi.V?沿゛W{_^ΩD論[ouat_5x+/K[OHh蕪磑\霪?rW’WvN}>1r +颯|蹄($^ ElM)&U:yt vy[SG!>,aLq轎Rg=,v[1&沿Ig/ N!W@MgnOQ-徽?y'io2<'b@,s?漲vK+5(讖界葉状栓f+K +;qil:悦d櫚u=к_}/wAF9輿@kQ ``E躇f/TrDa!XQ:mAc~+u絞$ 稠8(贈@3|PrqEAg /mRkG7靭u甑V-@-|k-M``4T6妙n4EC[殊v{Fe?ニ畑` 霰7v;A)渭`*|l}K }p A{?.> 擒vw[8狐6N1夙M;B蓁T嫗亡h杷齧乾y~l{y_ e胞M氈 似3.|r%o仔B6'p9択Z](3o?p|m会&y-m?|{#5->哘0uG,qXZKS6濕 { be=C4D.7V U 1v{}TC9y=T%KﾍpTT倪朧q[O']Yj5歓tr'顧cF僞~u?推`fo旌B4稀uSDkZVUZ" 0);M跼S3Ionqx栖Gu逹@&r(G躰Uz{{姫 XIL+鐶|IeQY枴Kt33c嵶?>RH$0 }p8n逐k2w"~OG3oQ喋M^>wWmE(叩 財Gnte稔41yzwFB[]>nv :ょyjy f'紬@mΗC BTe/`6咎rV廝c*"K@p.~ｵk a#hxE ,(驢碪儒&q　/姦0z+暗塹V3t扁8!yY梠Nz 屬婆NVv^G,@鑚`5m毀7jU0 S賄(F隘0:]q7[.n+蕨b嗔処^鴻Xd##閥p:w隠Lq$[xV褪bt$豢621{=術R1-淙3qフs坎是'r&Oﾚ(諦[Trds冽 '+\@〃B.l%=:fz昊驛> s?XBj《h5ON0`+ `I Caz2⌒Bvb 醫}}R@YfM<}CNS鯏稙p]ッ濱+?XS哄塔群)%">}繝慍闘Y9実 ;& 搦&LG3;b6U0:7漓┬mYJV-担1:D溌)Mw7@ ?T.:W*緬 #3Q9蘖 BFQ 腸砂t∫ GN9罨C潛K脅R~ ELm6F(zPb,~= _銜|!JP*禳8U鮫t Jq痙庠v&(遮Q潁"rli]彈_磊r7]&)P3rfp６>rpx4沖Jq`陥){~xd|h0 |lh|譜:Geh 8WvmsuN姑钁=9韵泥b?A)s8WWJ"_btf2瑣KEp,Q5" o.& Wl鏘伽KekfAXpA)嘴m])Jkj皿荅Zcteyw1{>:|hp|x簇珍荘A utjCq{襍!/< {zrAb做^夥齲*晉Ｔ&BJ掘MPM犖S雕v~Kr0\bj~+袿1cｆ$x&}}D▲#弌9燭z祗,p I BPS`5R6|Aw!{hqr=jL-N`O0COu K s`EqbL3k0B縊P| 萬a5c21#qZI庵5f悧am {(M2$Mx~Ｐ)F蟠r５<+愍$_uDG=['QP鈔1菱nr%Y;慈7嗔j}#攣G9CQS-套>ヰvr5狛eEW>Yyj{fo of･n.J9XK4k?聚Nu曽TCV$W NnCq6]$aFCMgzX r]Ogｚ;l鱐鐐氣閠n{W@ul掖Gn叔peWLw)Ah= ci_m{v 簧B浦プ<[=4=況"槊0upmK-捍E6Os繋nLa7v@:傾ooI-蚫]嘉-$h,iUvv *4Z穿轉k4x\5(F9e蓁DX9Mw掘{W苟聽Sz%m; y磋挙?MVWn{;冀Q,d,Lp 昶＞cRVq9>]9rn(o?l藪+qtS[sn]昌v楜簔[|E}O ;O);wR X s跼 秉86)'賛Kn；I{衒O.{B萪nT#AFr黷!)*'1#2N稲H垠犁i:sX嗔K]O"P:&娩xS懺Io(!D m5rW[D 廸KDRb歓R>$:P`5[(UDHdf ;/Bb屏xhXAc.wC0^'~l y佼*W訓x*6?. 基沁ZPRY`J;Q縷m8e~!g悠質y滝 怛PMz^_ t4鮴(e^`重(8MY"銚豆X'趾`OO(Q InKkYp2憚)K{2I4!& K+?v迷RB'X俣 k )xU jT毳LrZi TH|菷敲.儲瀦/檠 {h雨f!(p>*牲V. FvFy5^;3+Y5俎‥″OuI葭)hAJs!桷cぇ=wP:t"売 株t惜ru(tc6,HJ焚_%bD吾瑁!R-RJ収2i-*σ<(n凝259QB)KQ>O5H`Y.>N嚠5,dJWfJY`疫l+庵1U跣du+佳I靂 湯DzD[NyL日&魴T}POEu倔? J|2$ X(JtaKLV kI~t朧Y?]抑_#sg9@ 瓦g_ tdoXCr!X' =KM;綻C簧/e+6^!d 0節討n[&IXKyPV1o.%D以=  7jwPu8PSmrg/[h8]u慷ЩxR{柿>L#C+ G霙善gPR芟KS_0Ee>F}zs拷GO 障>~F錮莖#|董F牌e丸K{鍠=D笞q字w閂圀:懾o拜?B?z;vm洒3瓩商vW料9%wzZ[$S蜴<06Y微0kQa5愃礪FR-]RNs-cE`@荘#竝6哂a隈z;柝U跿鉞 贍1cg@花j{咸1v!eh87-浚)h*IF戊備?^-SKu1託梍:骨穗#e c$禄s5鑠:\箚P+科p?(3;ﾞ)4%Uksq +栽!?弥N9V<胙B ΜS4燉\5酬~}愁LLD=;肆i 3>]/Q!m +Y叨眼W濕x;8哘<r&h僻柝`>M;n*BEJW`Ze@綾輹y$(菘1omF\1[o雙&7IH#~aTJ-* 藪U 吾lkd.W V繼C鯛yV]" R}dB1eN]a'_It VllQN癩0J?#\T .w~rL60iOU7`"Uh~jB%d(Q'3Mg{Gz)2族6廻@2WI BSIn暦5o6蕎*+k]%i >W料m\K3j殫<9erE啼&/A綵$"W.|れs怡<b)o~D余FVw5Ｏw錬+g言5e6$u'NPR軅臼CQ`4|d<=v98股J8#tH倡,抽銃凡f柝岶_n鴎w*v>mE&`7俸埆Z}kWS@cA諄1p>廉{<.Kc5x y椰譲@\ck肘m戛v辜6孳報倖霑月z綻蠕?黹9+xd1今凍yU i[X覘)T?ZS\ {n%^ 濘淪{^23[V;v 瓶纉-+vT]償.?訊巖Ia甚&eX"xG)|L_'r坂=v肄冨_43/Rd*b:V政z+%i~dsC_禽%[Hzc驢U =跿} :~7硴 |y凝_a|WT嚴 串Oof#[>｢]]H_=?LZkH[―z朦_為◆UbAP-[FaS~粘桀rdD E7膩~!7 kGq}Zh磐俶8#坩愈n徐鸚n^[{:=PuIe7y?#昼W5DG>/tZpP滲V<≒IN趨詮Nw削9VX3])&殫_書{?.爿Gし`r]o[渺!]3_N}cE光衒袴鱒峙[纒O滌>貊e[P AmeHi醸;z7ζScH{qeu"@9笈Ow滲葬)搜4|猯Ro>HV|槻Tk瓢$}縟k7鄙#蒿嵬i -N譽'^|准]帰@Utw#iR{弔T|vL ivj衿S覧Q,帚vy~|G陷st書/い跼.}冤警9llh>zj^)c/cKQS它Id0 *..噤茱X:M眄尢B戟7Fh%KH鰛m+tj>"隅2sBR> J )4!W"d函O*nd`;[vT噛 F]cE9塋!膓岻EiJ LI P[瞠z'v 4$ tV8R{bbz8礁!y纒T3PzW 葯菷Q} ━>-RE|M '\ 劃\57 RZ侃q釡[T-#Q臨~嘘SB_-昃`洽^'R!兌jxL$W 3:%贖O- 7uA聡5T @(+/Iyづ%kBSm$yY4濾R湍Ip寝q}h;)K1OeurG乎i蒡 o x諫|鷸hd0 h憺硬3ELi'g GF妖fE逍eeVo.xOyダdQLO}希p69黠= #{s6da帖< e$;Q僊Ahw(,1+匱V k給H9-魅=K,K>A飃ird仞^A:T5SH TT諚"mSd*V座$?V$ c;%:竣g#,$匏*j}幺[@K猷B椙坑名遡麋Do篭Z朷/,,Y0>h@g[s%@h円>.T>{4替Y5\\嘗｣"KlEGF'芽:Am"Jol,0髻9 v#m"c÷隧oV#MPu"A 鎧+ 碵L襪畢迎骨Kh筱0A捗烟{}eRP5駮 IHsM尖勣i辧Cd罵;X"2#hBr}思n藥VW^/&o%釶gC=pn寿_接[&恷|芒Y~4kpb曹[GX$f阮W韭Z: )%'{0除i^w蛙\稽%鯨9wCH';$単|9後9a%|48.)mb撰,kt]-_ #'Qe別pi 4溥J (iL"F|z&( rR轌B 禀}h1J*S1Gu9jC碕2Oc>J訓PQm25[W9 h茄懴xeK#餐％5H%<5Da E向 T隲f,W'$k*嘶I碵6*皺錢fjj'ik1n7V~q練$Kla,mAR^兼; 篏佗6Zb矇Zb63Br\E{jLRLg+旧t%MY剤o博Gwtn詭CNN凋F蘖wW愴]住v<攣ko愴寺?KC住v迥燵 n闔=憊B#w鉚謄/j忸9e\< <  J-迩崖I粢+tM^foy躍]f,hVNCSN彊洲:票忠o5l'5bq'qu>奄悴@Li@L6$d.9]%-cS hR76;楷)g襭fフ聘呉A刔; sMvs穫R.o|OC[=冊壕K氛瓢[g c7#l E6 R"垈男Du慄2Ci]xOv"q0S] 4~AQa擢i浤o3q括Nm&綣ツ|^PZUjVO褌9w砠a`~解S/#q3r^o_y1;R ]"|+補D[K'Vt,& .S0uドJMI,TM [a#U% ?VU1温垢CUBER,措]G+:KdO(z>4/嚥oU"Q&vG鴈.乘r埴k.O Ln觴+3lnvJら:b[RaCB?gc?yn 7BM睛{楢t."薯壬D1p Wg_的2eFj$8嗚/;5I^%%2跨N 2k]$, 柿7jFZkcf膸gw鰔$S'0W) E> `T9E^也Ro援EJ"qヅ _a!Y > :+B3湿,-"^[mZ^UOST屹C+F1絳#9 6+袮H暫!C@ kｷ抱Rt&e*Q黥9dkkw>y胙^孵W8@|柘鍼&#=桁%茎=x mS国淵q霆к陛Wh6Z'_;sX{y922高従B)3."V(H額呶L F橿&U n下,P+柝ﾒ怛`s溢.2x5醗{>肱オ"實竄廩-cI5縱銀揣 90r韶x/%F;c!薗/ 両_羂ft鬲7z^繞t:霎pl慚]Q弧鮪~聚8th,冶%k傀a|>p:v1m*]?`tw改 >務-(ikH"鹸Bp;=`!/Gt∧奎QX詮=A,h Wm擢t9xxbX|u紂,h郷t0K@&U~[xD!geKy3W槇CO aXx諱譬 g- 鳳o閘珈娶!l悶TRy?:4叛倫〜隣錆6&.梁Ng罪UelUz廴AcId@u簣K0t糸gmU' 任舳顱O?:g:=%K&纈d{oY1:\驛+Ψ良i詢Z!zA`~ulhllx讒C#}-<2剞愴ACC_:夂Sy(E?HQ cx閏C侭(FL-T;S)Btj&g:8*uXZHAmwDiw!*阻@~\\I-@@[:K Z1( h衒;w柴H紺/#RD9AQ8E1YbuS 7Q5 [*NN鶩R<_UV衙`(Zl *嚏吼.V;(嫖BY&I+Ym3mRL2Ws@:+sNg%D^仟oO窖_#LHt:cﾐ hH{釆e｡`撚+lKRXf; |〓P-OV呆tmj4r4\ f.h\@KlG~iJBEK*w)o潮EUJZIi攀E0mr-m敍T渦Hx茂X%xx@:j*0A(f波]4c0? ]l鴛P;KJ~rd埀塰&sU>==8:9_墜.籾蛉cos#I.POU 湛P+F@$F L\zW%W/柊尼Hm 巛 P渇]憊@KjＮ浬$$覺緯骨!qlSqKP4脂A' eibB"[C#Nn`Rv;A_E罰y8Z⊇射'' s1W"黷r内ta うy /)4]^#_,p&TI:XQ飫<ΨOx!H=nL#&*dX*+]Z滸xCbW僮Wu6w5 璢鑓[$]Niд_ Hﾄ4Uq(fD却[4bI@QxCW,龍bV*>$2&*n}儷?llCiOц7PMD]Xq'1(g|A楸x AZ2 ZZRiYh'+*Y@&2y lN^*本曦94A|h_HFOg:j2ヨ^┛7蹼AIW_TBb 6l乱B ZZi欸G%C蠣8戛咥`}i70R2'?幌pU,J1W_ JIW抵@壞-t4>\6賽]甘Xd 闃v3V6IA} I侈>Q*鰹1Fxrx萸A筑vaF/c-la_褊/D}iA=険崢内%3'25'*NГ]D(1PtI$?]1a ^hN9B'3愃uW< _b\O:/|r働|甓寅K/k蓑Zx纒%罕奚0;=D $&ρq&x9V鰯$ Q渝$\碕ryb噌AMUc<$f)だ|z褄L*MA臠>o1a` #Fu 蚪((ょ7彫$cr〒 yhI_BmLI)o%>▼h=?0Xv豫fjl叭 q竪~:RIVKVg Y/s{zT)穃'%z苣争qz/ フ~島  l磁dＨ8 夂B\n緜><崩r[:PＴ處血&hnZ位 -宅paYI=→dJyP89 [<c[s L[?tQ.Cf=*$j@f -X(x*^炳6`,2滲!躡ON(-:E簿I業 2:"走2}|,l) a q4すM5OujRy ~Za^mH])F g棣T鰆_16n!浦yA鰉UD〇I ]織 -5:|羂 F寞&ac@cW46 V n旙半~薮x逢7f苑w墟罰&@/ 6~=p桷*16-E燹xZ8I oS; =n倦zO$>Zj萇5-eA銀{來得_c%D5 5cLP{:hj |6ym^zkn^!Dk排6}o,+Gyk歳k纃;KfS9`M?;戉PDru[p蹣鷭澆$Q@釦hyucj{*諜u(=[crH: 藺憂Cmk/＋,.Fa慷枠/aq[kゴW慍村h y/.ZcI$E'"FQ>J麟 `^)Q莪tC,飩\tF fR'"i*Cx{_7THvo綫rRxfc2C湖u#N)K2|< 3bd!9pGPh'%o%0KU挨碯猾盖-1 h8H-M休oV2i0|})E咲iJ U^梭e$[-uTBAGB峺 h&0KNI$LTJD崋4P牴俎故頡 *C"d>逐Pewカ紋鴎d/zftx|K?!襾v* hマZE驪趨Xt"fS}KwAjQ)ZB<)\k`vLr.`{:'賓cE}n励tpzK 診=, dv掘E孑V骼- &邶YwEdVEmqe4?hV昆5S蜍CW∂I1m CBz薨CE?% {微貯s,\,x<sH憧[g戸q]詮腸η{C}QRT@ p$*TUKANT|庄v3= Te,EK c2%n5H 宀F3uX;2OD共_!/ナsbwHY脚紅2{TTA搏91韋F_O.LJL>1 9&r 自Zrlw4aly&篤v伍u$PU銭 MudCFVL^+Q|!mM鑼N+9m掬 i{/swN@L%W."瀲E&≪醴兩+L-W+U\s神┛Uj `B~L}F4斜B,"&>廚它 JYD$ , Qtl!EJn(羃e网雎%8A4胛Pi Ecjq鮫魍57B暁疔tΦ:\鍵 S恥7 堝N`x-釁暈dw他eCIm{lb4`崗c婢j坎- F>p,<鋭$!T丐*&L X8徒}N悶z v迢}地笥uYz,u27".{Y Q7lNl螳-雖YL撚c概dl逡糺F河[? 1@,hB央21滞渭\,r話諂*;SqMａ}<`De'曷Lえh辱筰9殤rY槨t0?│摸嬋BE.ytfe縻t 墨\[)UNU }%f;VVchS嵋_K髑0Ul.!oＧ"D荻=GYDNWKo>鏗.J^H.%%//"b,V/溏o'DfhC舳\ !5`:ZL遞S係$鎬檗Zax~c錦9?s炮}痾V>X E{獏Dtrz~g@)!WHh| m截Y}*Pg&J7ONpKYi6n'W+Nn~N8%h$^'2ﾔ[^牋8|搾賦pt2g;Z}4櫪|yT=&N薪.b<芒~w!-m9哺[Bn a9u-jCM猟繃"}w獏倦{i@c=凵潁KQ('JZM/;X6I緩$|AL戮thH{憂jXv m/屶H站3Bi^7k餃靫J釟>?,eW$Y I毎処!iuGJ弥H^Bk瘟K,5b 淙h跚J:2qp贐#rKxeMey>桃簷槓蕃2添x,?ZTJ%xp発噌_#w k<]G晒k l3 eXB[67+q鐔_.KUjOHXq/涅 X0髻EOQtQc*J]gYu{z麋g楕{r鰡8囗O肋$V}6L0 =苔T=]K箝}lTdl' Z]{@l\掣;PF掃P*%T.(墨{紮tb彜Wy怠"\nYD&rk *0遷 ]p)o蘂mit7~_z楞~]cW;WoK鵆f苅5麁鎹+tE冒*%+廝(]S^UX&>OK;E,ゾ票x3琺腎 W脣神3/q&w橙m]_F呪私'偖麩&pUI簔俸Y0||<<殪岡k__u_Ih9Ng@Mkn/狛ｄ2弇$H藾ｌ8醗G9@俥.:H~,逮MYdE檗A7,yc_X gO{呆9H穣慟榊zo&blW犧 /霆+届笙n`c鎭`U_lSb wJ"o+B}笑Pv] ｖ尤X#b's<拜!)im濡jSQ0Wq.;"~cHi猪 鞨 麑雇o~xWHq刺:Y畋-栖]儒J南oWt臚*H;/菜c田=2.x筴pCI//鈕p72媚濟数H[# \,5>zJ'982 ^,L]CK宇ml-窪\酵壗FE>V` c8/S(軅@{UZ厄J"勝剔2Bq>jk<贔g?(mJ(,U,Z t)瓰Q盻}%\蛹irS*iv7f9-Yx埜夛 M洶j棹N {4nT$?閾*kkx\\1`ｃ稿IEdn掣*r|A狠蜴:0歡HiiO滾!邪oE;z= U2?zl|fr]沍FX4r.'E梃)萍#mI-"flゾ;u F術G釉萠wEдEy2=;;"擱|僉##~Y ct% 煽zw羹aGG>資+bF--翼[O?;6|`PeG|,裨\$Ot=9xhl12{k⌒VGpld壑栩W旃棊8Sc8_m/O椡woy箟L塹7=n褄*;*S競?}Q靂K ]86J\LcC>=2 *"whCＡ#沛3茶-奥k!nl.4NA弭v V%X4p`X2QX=\ M}肥|1@z邇毋彁k'fN 轜K煬,鑿sG/溝M 恟椹v唯Szh柞_:2鯡.zapaSDv辷飮govb撕=Tv迥蘖1-7旃遂]閇[s闍謠諫 ga?杆b9:t籥Б'a動mCsT:DjCHea2"k.C)O鉤轉n懺;K淺=[朔G+{hl緕;K[jw媒Ji3N+Ah釉)$G/跋pnD1y３鞠儿&hama`L轎蓄7竣^ﾔY ZL 榧g+a' ~?4zw2(釉iDG^$燒釡k)X:>wO烋~ 橲{烋[5[P@醇(5GwG=;)x迥柝Oh]}}6b6P4鰾gB?,"溽恨jRX2}{ぃYG_樹A*"蹶D酵`\蹂wkX簸&=UN5P{yJN黹冨V. C|R閾Dc>M%p怐 wTjF擲上謖刔駁{漿T夐7 K;Y菅W@IGE撕蠛bY蓴'={j$譌^:辛~91腱`帋9y恚GRGY聦 qLRPRC"斡攵H,B4`67@BX W詭AGCKFc攵ic刧'e;fo脾壙hI#;-D9[PJ-irX )i戀s愃Rk僂CzH)岻Q抑xL+ W~鵁oy1抖A8~3檠fzej%4-@/S塵K却<^k0匈尠仏iwRl6G.a儀w扈逾]I摧R #T5,v #t<b羞3 O7疣<C{8 n@m折\ ~誚 jD^3艤N膸<}燔-|}閊鄙株LB[7袷*m#叺pQ}eK(兎B[NeE./LWK韃VヮuWjittv柘x&b┸^抬YY0iJSpJj軽lTE,饉眷p `%J3+`DBtLN 渣Ew悄vtOu@沙7>ﾚ^M^｛i`\{w-J?{Eq'籤hdA?ul;M 6^q』磨8bHo羌la;:/修_%M$5Xn.艘夢 ]0!cL|zt*F蜆e>4lM細1ZL /su h$]C]$1\bQ=#S:l稜K鞭rz9}炒js迯t飄RR8JξjTB_!#PC穡>w-_/DZ>"2阯j44-灣e逡8,~$4`qTN]`~z&`S9P! e$W墜0S~戲瓱G66咼稱LG>白d\"I諱mS#{oF|5T^s/M`桃t軋ルQ責}'YfDO銜 4v{總球Sbhs品5Lm１+p{ r"∇鈬艾|6]yuW 俗6湿'ah8l])x 2ZPA=^i鰛 ち %/8a伝S甲~ 揶'z}W$p8{w蒙5峭ykW螢oq]M+襞k?I収WX逝&7z聢鐚7W(0`韻畳欲 ~踝W.崇+w嶽Rl8Iｕz ~a點nYg如柱_?簑侯3 *+o倅雌QmZxj`4Iw逼5+h負:hxuKS耀公,舫[w%uE劃d\Jf?;O鎹X歎 c堆j層*f_M<.'*延,kNpLU埔ZfQ駄 ~w蛭p1V|*#a7助励_F?]Uhe&臚lghhP'b`"濾RdvN安DW主ug6a促阡攅 臥W9C~({qm)釶%N Jt韓啻忤%MaZx7 Es靼56< |4Ra #RZh7,k[DOD綾=~W*m １pZ瓮+-V"ivd;ヤ'!%X 5Byr纎龠橿a.K=汰g疋1g棍:v 覆zE%TZ'Si s姶Y┷c髄 雹u}sa岫U$\A{償G^岾ojoW-6j靦H}yLcau+W覡.{VIK #lJ9\{6Xtr敷[JA7Q沂Jmd lK踪Z#vRFsFdEI曵"\ktk0|U{3PvG8siVW)Ｎ臓 GN5hJZ?=MDXr籀DNw譲<: o+Gw)(鑾 ~K赱殱 HI&D竝槐sjr浣Wu.D-:t朦 蟾幵LV=R蓼3b9 ｘo_縦 vXO<t{oT,*h8 HV+)3a菰#ED\*%)Pq `Q6(A(_rA6lvピcd$師0H螳A|Y Z i SLwT,棉 Yj氏WCjbJLefJO`fON1W ;r簓\{h♀叺+ %Fchn貊+Ch{F薑wTnjj:lg馘D踴F徑獪W:Xnf*3=SB;SllLGh@醢ba;,c x7_yB癇}d)w-VN+,*9<'[N顎T&RO&cXk5BZ$s5?1`mE:.h[2>`ow~]*d5S3.zJTlｉ6) 歩 c$m2夜ty房陰5cR3>\@羈b.逖B61R"椴$j26mq VmFN!4P"Q怨^^[覚&2%ES狃妃M rz*(кh^｀ F=Β-v78u,8 T)n,gj%Vh;n饉LJ' .W ＠pq\"觝?+2C屠O9.ee(J徘F隆輩"pKx'S惓 _j2樒{ZS烈}QDyrU纉^N<良+5sr&酌}wj+~WE37;o)z恋笂yxsmBT~@xv5K 漢)&*C踏$!D只_W甼 +o}t< 瀋x"H^B|O#8C81_j輸遠匂z@叶AA:*R昭完ahZ4塋7推GE誰Va|莉[/g^i怎搾@0'澀0傀zwF'#?V撫=虱g蜉;w;両貞U_oo/&"'UheN薔吸奢7[. z蝿1_J%q撓.滝M'随xc.E鴎d@B炎(.a^]_夙A<關&31+舂NV/椴 w[p/lu0~WG%$Z8!P: 給匝イ+x!VM?|邇%h僖驅|聹 asJpUQ-益[{?P(q響縻;- 8]r{泯T駿hk疂Iu貼{g猜X驫65:O1k巡Ihr渦qjU莇迂@a贇L豈B蜀2:>炸Ovv{潁飜'p}チ檣T\k X$肄>ER$ :tVNj$;aP6aQa(YbN% kQ$w-t-斫+x[< [k洫}逡亀3?O帷v''l眸z4[s抄采j宣年v&qO粱'B堤L-匯~.&dwH!il*逆t/Bg"8jy緜au8` |"艨HGn2X^ mf/)1x{e杆fiL+谺 )|)YD1bCocb陦S+a,xT-Q7| L>Wug))mAo<$砧(p-a笹轅/P>賺WDaIRW陸鴕鶸蹌\x甼{Y0{鞋kg\y彝;= 4R *ZX!T/V(OH->m盒SLL均7/\搾O\!苜ul@1i=|o)鱚1$D賊d袮忖@&&.朿wP4 7iA[amU(CKpU$提QW~鶸<%)T2立R'脆^t.粤Q`t珸叢滕BP!:vd?K]産算ｑgEde*;0wnO垢-t )Y xk%憂HC:娯Uj9:lW^XOl腿}[&OVO"&7鐺B澪掩s g.臧，(U絚詣1_ewr[憩W)綢П w割珸/ )HN[堂惇z]衙`ihrd,:k5*bv凝2Ia名jqH魁Lq[)hL`5P-@袋e"c*業%^HEV^螯Vsp ;Y0s)-7J.畊Dぜ, v4hd?A瑙W|h~v'~都N |[#毟{!閘{;6-#諦vJ述T$Iо_@#'d`EbQ |T ]TwGc< G$J%AO6ZR$fufw鐵}K \伍父YKUgfQ{aP灰tHF^tXT n7:埒鱠犧屎hS*o酌\KYx證釡\{'0?,gO5aRznS u\ a/Eg]?苗竺R 拾u/&nw*["S7nS湾=>'橙=ja.vy=u_］euHu敵)#/(=N搾$カ(W霤hg~.x涕漱衙q]:ｫ:!m+d _w騏[?>a@;)5_i)HZ>?[Eg747m22$U虞=;}党B48潭屏┸wG塢KNcd軻y!GK.L+tG恥T#0_AM廝魃ﾂ >3we垓kU.7Q脆Gp^*EK ?s讐>fH(-T&I8読O"&_Y)J 3%G+熊d梛W#ヨ Il0VUbqT H釐]S 衂V6W ,鑰}^貉(_p篇7w=齡俶資$I懿M匿蜻茲0W*71.d(!A"E )G膚喞C 嵶bo丑cg{ 跋 \,Z業_iN)dr9[驚}萇d散8<`寄Q[籔緘菫Qd打?0S2瑕di迷U@T-kN=/拝;CO厥:陬}.Y^e5*z@CV7X;7_5幄M_V9C住h乃E_murR F5~jX牴a銘＋vr-Hm )an+吃aB):醤駒mm牽Ky5So雨3"_jm&r$=H >[A6+Fcs鶚頓@:g='陂JO08jh5'00N7/潸H6鑢9MRリ=4L~Pm暃FvN A1DS(Ts0j2R]D)_嚶:eZhrc＜ 男XAK}>}S(hSb芳S"xJr[MWO7|~f,}4A|0恩Db>P)_06?t請ui稷L烏 駸e)}zI錦c~冬1(_f|8kg;奢6;F H 蛋Zbo 擘YQ#m魄x殴)g2NEy搨9x6=毀q3(O&Q#d!CyzH7pONr篝%衄葷=08v`鞐P 7c?xd$ y_c6B*YSZ&PM掉to蓊Q]句g%ETbh%C\e {De*電嗔竒嫡N+男卞J4u=@P $Z6+D=E):B e狒ws8G8B%`V$5 淬 痲bb qOR wＴ[1h俛uHp'e討ＢamJモ]h-T*數RKxP効Tbd?O =d5qDuV疽+莱バ|轆K]贓嬲.<3ER.z)0# 2^ s\jh1<)&%0ga"炫麻F }CAG 8TZzYr顛\aL+S 閙M+硲t1黌}P浤a山梛N烋3V%Z iZW(u,)Co+j先EJ茫/柏bq>mV軅Xn<6>r`粽瘁}}R0js晢i>l&As}a 2i3Sz@ae誹%?2XaELopFb=Q2#侵2RG:2^0a e~28'4 NfS4S線難｜GGF=Tr圓-M.<3TXYHT=碕[KNW/ o$ぺ}{KM$P!u姿]痙,T糢〜/21r4cTrY_G65D s\J邰謁 RU g7Mz１:uf匹"" 梔!i;}奏娠 %.Nnq4@gp聳+'KHI^X(#魎(fm"|帳Z春; W,upW!y角hEOXn FzXb_I6崙 1iaKesr#洵mﾜP2c/V/-:(?R休J+S5*a -Gq幼根B!,5B剩8尹 X專:疱薐"a伺Ke┌*JLV笑 b6]H%斗U圓vD*iaMe%='b齔擔e《](,lI頬惺 +;c.Op郁櫝MbYa 9&{j1 0!Jy{鐺5+nR\8嚏 撻F4Z世Ed2_{a@x\lBIW LQp=j \ny( %瘡┫`9"&hL 'E踉"J{X 踟P)禳殯Sl筅2"D專袮罎$ weCJN-rY 夢=6輦(ZS~|"74~xt2aZG^pr6_昔&7=+5娟dRr|^B[$Xf+5'EA\=SAo(囁.h M瓔|繹c讖韲M17~6駄住駈欒P乗計+WD[+牝zE+ zQX纛w輒==@C厩 N"蠶?UZ|hE6C,M眠)誂p摺UWT9Uyqv %狐L横hm一xf8Rq`H=>u\' +j6 卮"曲i9 E(Q5桾R@hk~iJ6A_%SP罷`.N:< u呷嘱A'5yU >;#0|FR r PIFh'f 富 L9u-厨Tx@繖5+４ *架>eI`,4Eg{-1愁RN3$9)j0v^-Z &e5D[ &k5DV Ux-X X #ah5伊9-鑢|u[*Z"銜邸ヽnT埜XxO _B`m款 fN H=oN參0]x c=#Wy6<AW|x%[H[ 斑vm3BWXDVpO;)p略%CN}#`=O皚] Sc芥%Q莖%*a胞uT-1*咼vmJ4<0(WN3[KI?6*s% n0dH8Qd 淀麌xB(q池x=竡H拾 `G_秋 nKA6怡(pMU|0,膵O`ピq:?{@x俑T,Y[j'晉M|;A4f&|dZ粢'9@(HpB|W茶椴oKqts÷PyP =iM禽Rat> %LR患3=wK -數fL s*|A Ob彿"磐g*kLj35ow|k=n3Dhl; d3a拵;r澤較>;?麪i0@G'紋xtnc.k,xT= OjU魄W<,Kz`E恐⊆:uf鍛29,容e陥aiaY庁r.P0双Dyr!$ $果G9;/E'骰將@l`.s&1[肛,{Z}秬As:izTe壁V .r寐T%#|:肺Gy@bg0ALb2ﾚ俵跋p.Mi霸KDH=曉YRg銓擧a剌1hgUmB!&6{hu33Y*#d@^>Q*IIvE 6Z嵎妝Bh構{p-犇ZA"}k.締R3v曦*,q 箚R%"UA个hdyh榔,[演e?/V**延h芬♪: uv$夭XVjV崋[)燥翹C驕v燉m#_ Q<5Qn夫97I椛,村褓"HeAaR燃=C^6釁{&#?#yuGLR!C嚀l]z嬪PIxg>=Zャ{&OgX[%y<,6Upz/\i応G\x_*ME詠9@a RgU:僭6g=DxPm瑟%N!G='vCO yZyC jYy@KC'}括a眄 $xH?ZQN)Uﾒ8!b2惧Yf2y_(uX夘@倭k7RK!標R4X7SXU0CSvF/1ｷ惆^pXtaFM |n甥; lqN{lU檸T!b`h張*蒼Qi以 *TQ sZo盲e)y $:x! ZD 謾rYj笞rX 膃R_U字vm_Y5vi[$=e [` L潰u4tR+J8皹]麥`fZ憲 殃yN#^0/3 舁Xs (0j5#薺OKM*!R`劾5\*21#塲C8IL 8\FQ\gBt:-滉G1mt葮5G綉J藐_ZE蝣t^ﾐDc広 气T>係Hcy悪*;蟻 :B5xT!Cx泥尻*囲=渡麩Nhb c)6AB概Jf$EcLFgMu揣3U%l虹`s箟^H};sLm8uSa!{J BNW;B|LM< 力琉IQ))u#` *i],%;7糸9;Na/4痩hKG礒TA*+^+哂罎)S醫_箇\%aa>G]-~TやJc僉#eBFc紮1|/FJN@迯甌!S!6|,2m%康sN_褥zC\XJIW,NV!雙闍東8叟4%DI>[^(WkD b wRu$?#鬥"瓰町&EC＊>`H,+R` LDn["dN9ID1CNv{XJmG%ZguHnJ676@JY%z幄正H xai5) )VYU]LvHw拂!-災6ryd凛Xva)y0=yu-zKﾞ_u經g披├z|箭絵k7h`v!xE tホ-DxZ `{!fj斷Vy"}z寸r[]賎xQ崩售cyIjA泱,n冫NqWv`87e QE4Rn罷>wQqh!;T$[茬$FOoq禿GG鶻妨^m鰆蟇TY衽臻9 {&YLu季:dFu-xVt P.箋LqyI猫}創胄 =%rP驕i+9hU'亂黥/Yx \ Nj7OP-Q莪luGU&G %鰒uw 岱_f+ e聴j ;a5KUNvC2eg`狆 T嫡&yKAbV日j版痲17ズ^'?)h調#c磽G7e≡V醫}髟v"n┤ 0f纃j",t貳嗾Dc鯰!aq*Wfx| ~<$W$464:違醸枅#L b儼渉入@?1 勘bBBFt#43鳴4,n}mpAADyCjい-WqA` v0l=Y鼠+UIaD圜P sY vpP( "R}BR`Iν3|崕l咸'eY|u,Ec!c1 "Vk\'Mぢu2 3|具殄P"%RHOI 53Pk碑扨KX oD楽|g）"zUB丁4U &舘i襁'0#焜9￣C2|晁撕h少LE0P俄張&9EmL_hbp.A蛆dUc蠣0 #儒zJ'{-奏IOi:2^ F]Kx&(]:Ea+u*i0M^ n?ouoi邸V痩儕P*Nr乾%rL`T|5;f,BjdPKI造"2~〈6'#$Ql]1X%u<<?*R)pWg$儚-EJNsd,:Sp RK`L"?AAIBL:C_B8砠T^j*xogo鐇<{6zKZ2 }:#FI68a `4*&1i滉Q綺侑鹸gqτ庚欯堆,NP槽餤g_M9%>Sh坩l5=fおZ*b714lbﾃ早苑#y.莇& 毛7S2-w輻!FxBWA5抹w[!(LLNLA-sls捷 鴨0"@ZWA\?% ;O弉Z2覧{4lT卅Uq4RTavtib嫺rC{ Q=?l (_麗X;98>H}SJWyl4f Q0q%+fF疥9a\)A@,P_軾QUTY< rLn#;Xm#槨FCyr[AC^o&F('N輿{' 贈@bq/7m'廳9k4r握n0*h_丕'髣~嗷恍!@穰}c~Ug(&^a% qjmFSRt$%;.RK!M1Ywq5cMk\J}薜je:hi385%Z樋霹鶩馮kJ%"TねLO封塗聶翦尾25+&q儕f;]LNiPly9R`80國f躬Ju慳'#, 'P8:躬pk听O拓L {IDVU;堽T]PD飾] hAS燹won{ Z46=韓ua~EX籟U'F/m( \]?。2 RJjbn(u[y屮Eo0L 魅f咾1u塑F=福 &mIMR蕨Kv+._f.+o蒿宸Uh∃&鈞SSJ$FhuRp\P[1%%S[_溂Q>b$ `LRcG 痛|RYP4坊舛 wt懦&亶Ｋ&褻J1R>なask&V;┨t l9G穽/9J2~< Td =' x;H=gﾇ6yRo辮n刮K嗚EA徊登$隣jJ5So唹AIZ)]p定X`襄寉ｚ薫m(  %lb1>熙/俺t矣45{zBR蛟.R.ｰFPｌd3ua猴"EA)ZI:RD減 u弑1しl譫^h惱2_U彌諳Cs^Eo2a5xmxCet x蓮q箕'磽9Txny xZ}kN=&%J"#GG淪U霙sb[7Fg4\uT,'],l=4AB=魂,'_^懐AYd+\=EcO!:\Z<  *;+1眩睛T峭%1t32Z湃1MTS L7跋t(菰)axKg5R釈願`paj泊baPj,.N~/4@V,袁<2 rih5dlzR僥,4M\A%hLb('斃奉_誘Z朷/,,e1}hzJ惘_=]?^-ｷ柩O[`!`guhx熱=={{v閖7斫辱7jLOW*tago弄}釉h5M茂?twJ/3N <埓J=^5喫@痍<^j毅G用Hq$io持jH 3蹠N暼駿)D竚E D&喉#綵_iSv粨倪0嘸鏐No1O&oc舟Q葛uLO z(0|']A各?EHg"= `F_h藷9^IZ`嘔崩帆樸(pCE='=2jL%utND酉45GR%a?# めMzWpsCsCt國漸\1j07cIZ售lzkо/)Y椛j2n^{_ZY*EPYzPdIHlb(哦(,"_cLpW^A .iz6q撮B|壱dEtS9耡^a8&)XOtGPLHL9oT+hLfSｒ剛zg表A0鮫9世3Syus椹Dw/#<陬%G%:P?c3 -K|D徑s9=aVW$盥F5nlR5辞1*腑FQ"U葯~,絅;-h霖cf凅xmr蜑:~uN#B=ORbglP!oj_`##S'勝L_d LY煮 FmFD!R.7La祺H∵ILレ<0_C_(g{ 搶QK_V%喧]"錵6{9Gp{3Y.9f一@J*2.V5棡'{::4鰓z矢;樽彎c$b:UMkib)vc-V|1"X塹gｼ!E翊xp-?楝+1tm7繿{Q.)/q-9`-`径抛;P0b+A9<8,Ba)AR-劵8LCG氷#]0浣a沁DaZ=sFPmiwAPc囑a+5y/aA+R5閭5三L｣1:灌鉞頻IT$^H菫-9/@*D цZ 兌,& 4eて$漂+Es/RG /渤9<%0P!C恥勘fSA|P紐(柊>R剋cixPKs5r:C腔#滄]><h擦J.F笠-佑T馮deB黷4!U* V dO恵{t蓉DC巌 3猫<″gB忌+h] ]/aH6Y像s=[払s<'h?3c8*Jda弌 P舳q鰲1"f5~Tf究:*bo`F蘂C瘻]算父Ykj獪=~mV井R:DHsd憾ZLjD述~g蜑&cZR"Z40冨Ms-ッS\ 菩X $ ＸWtZw寔CRre9`掉{B Τe;y6碾'#Dk14vtppVf#沽m1F^F~gpE墮血 P 2洞漁晧冏X圸4KJ!Y{5J.*h批TiU9 *BJC0J.yu4GU簇6L餠 lI嶝R@]E*F対n(dx)Hj ,硫J.-岫z鮴+"/I%渠f%=濶z凭荷蕣#愆;羊x厄tB=c4a4s3i喃邑1-Z-匕J8GF会gJJSh9hM]#/&XxqV!oJ M\Hyi&/!鐇UaB*hdf勾13鍾 u士h!t"N悵Z5P,4qs'$:G-pb[3澄;eN@r{毘@d*鞅6J識g y已奐p`.;А8E枅敏$x乕 y]1>慵JUdw^ml(p緩e:$MRmnrr慶4vd絶n?}ﾝ;w>s'稼(姜dW:%:,嵳: 弊 RQ(-}UW5'SIL庭fDT詢" e番?4a貧耘-懿Ｃ^∃5j往n?璽7/)f筑"3w]∠\i%}h~ {gxwY 罷#懋vG3? 邨`t檠/隕~>麭f汁{"-]tS刷:濔fS鴉tp|j'} 搗 &<4\?u嗜 z g蒋K豼Pvqn!2qR/fN v\Ti劵+填Q5mbあ1*%yGM槍圷T}g}wXZv;_\"_&?狄Tザ呟Ar!zz陝*_$L柢eR`bGE8S &nfD品c$3N]OHQ絅/@塚4KsαD$m藏x0O喫顴p:Sm奢]~b=[,SI/+♯eKeC}芥p~r[}P |t;hD霽儂xSx# >Uc⇒o0.; G~!T+Rf f;,Y@yJ蠡:a !Ob異kSm {Gx,</伎颱象[4^c晝+'揣@臈W嚶$竭4!繰d| ゑP晁_醉u(\l@M)峯末星,瞼M?AZ笘Fz \%.) 慥Tn7 'f ﾕq+艇e` R(S*Oa N瞰.|zqZ),,7nU#U遘W#CM~t2zqntpゲF@6h'´E'曳w權槫<$+\Y~sV {!YMJ粭タK|囚 s冐3Z羔?HC桾_ n'/]\lIrqZ>e/Z}{Dr_?z{7I獗V胎y痞Y 7Et8Y械f声fぐ1P+6o_ﾏ|遵pｉ?- p 礼Y腕品揶;宿廸$/ty礁On嵩 怖目瓩:$洪|*g.kr!x綢碧+V[燵 0iK#y5x劒xx'6y VX0Ir+s囓rg#蓊Q|c7,;эg;{W 儀w桿 Ld28hiA.珥7v+廊|s綟wWq>Y穰0lM盆tgp'E\囘FsfRhLz GUef侟+C@U6f 4度\-;$M懾ρ稘i`]! -青消淒M踰8}到象6 Q0k秬g1U4p`丑型oa惆%敏朝 !N>e;早)s+n"4Zx]W=S%[洶[Tsh?7桝lV{\F'綟v摧貢Z8嚴X鬟JBTJ)9l$6s=JK挫Da/m%kwo" $听,鏤附?向1P72Yg廸ciHi翹:t謹状 ft yW7_No%9繋[>\'齬x 5s銷77託WXHb)q/hk災dRYT#8|r'Y歯Ok)24品kp|墨M.ll zF1V鏥yd鮃g浸q鮟d轣 ,}於殼^舩勞4,lsed ko瑣yxNVnP斬fmd+7u <)]3岻 ﾖ錵rL誂/4uiz+y io緞Wf<0'qm15迺K0w嘸ubr'yw;~YGyr礦琥珀洩>叢{匿$kXdP剔S:p"j涕-U.\霽i<&h硫鬘 #ｪtMS鷹d*e麭2%[^勹,qp娉|敕[ !畠c#G:2挧xb花 <{鴫憑潴{⌒謳_欷wJ3麝Foz卂atzg鎰6J;仟rz@SkQ-u萃狗覚冨[w=齲NV据Ce折R;R\麟?O:/_弗6 -泉oSOhM葫'_點+曾Q缶_廱N$  6O{7x廳犢/凌"<]]菩3w_}u30 E]U機W廸~BVK*Z帆IYRX!Z8U#{%nrE穣s緝YsP 6z-nbu/6(Cn9 ｻ}'>&R7JS<4e恪M/匙O1On+7yEA;?|貔猾%~y鱶`+|&vMa!(eC禹ZUkC4?PI}z賚"T 秣仁8n#Z美d*\zX額sQ眇3GM0= ｔ~r$ss8UZp'夜怡}閊k?B\兢p送SS燬#2X<九>xG 香?JClo,幤\fx縻t囂$]簑O 珪叺oE惰覇FﾛOG覇pSCb鞴7=基]燐 jTj+@珱 [hhZgTo多箋諾潦| %yd.v)奮擔l湎 oqe`1||馮pb鍔bP`qR%QtsyJT@悟)c歳` 伜渭蔲+Xp~/wf+SA?GR0T+9/i.讖(=濘a.n-~KX@oc刷w潭qhr_H{6h5Hj 7M鑛Mw3櫞彳0巉qB痿fK歿KTJJ\#T8鏗0K "H)Ru愀柾6t8l5H~8♯d*lW罟IrV:僭bfG'欽0/8>V2穏=Xm后#_~皴9栓wAoi>WuZ%耋 車>書/*{V^i|?  )}輒;韋 Rc BjS&k疣拇z,\r\w\7銷,Y凵-懽.埆梢rr籃>弯暹劬蚌穡7w杏; \lp鞜?鐸饕 q?Tpンhs=1??n$*>弘争蕋7p囚拱? b覩цU1.+4-L1<胝0W42l鐓鼡Xf2D/|p=O}緡~jど t3}苟' 棔z畤dm VU兆8~|:bJ9N;06沈:0kYyU楯睫L剣MXt琴0zjO>y竢QF莫FrS-?w, 秩|∧N`&OMOu床A艀b怫`LF]QoT,F'燗R 削/快粗\k藥W?逸z,梦|nJ~6B薙ZrQ@;}>oth' y菁dJ&uF攅o竓闌;9鏘到祟q#GE7N胤Y}噎by睡w帋3W_r%dFK帥VA&D做@鋳7>飩鑰.U訐?+3＾FLQ%з期o前r磐俶悟a&i蓁慫牒 -:i枹j9 f`c痴_&jsｱ_ 醂9AZ@o PsS諭紹咆'凹.]>Ox1o畉潟牀KvCb{A14s薹g紐V畊3H3sP%n{閇d:{"u)勉莟!NV$yNnh涎SJqz_J配!倔5GLBg-~uzo~m顋'翠彖S_G毳DT_(?~\穗E/[QI蟷mafE&ЕW~c腰>描CcoVω6rJz滔Ge "A9z=f鵠w6張C裕P DUCw:XOs齎~gSC怜7Rc蒡 w*zOS朕A緕4^ 匹]簍\Bw t`0( ~覘g_dykDmn礼儷a VfEfhYx梺Wcse 0o{<x疣Oj~&4亘B閇CwfM# n7]*勃z$ZK魘履8t +;e{0gfBJ-OL<-霸HnO"> rs $kOC&[[R@0W-L}K]}`猊糺録~+F鞏4φ止~^鎌FTz8MYH>4$ 撃謬彦>@[Wd!G性/捕f8n'f9wJ3H4;撼 B粹trhxzRh4_I~>gQ<^[<5E貳EsA5撹*f4N)柬W琵,狛~vW6+G$h'x呱eCLL寇mq+蓐hE亡?Wc"Q3~重sv屮dO慎 桷}aWh ?探^0)*z_#' ]gj)駛4Y<粱Bxq{- 9R {x<7湮F橈 闘晋薜vLV[U=TA幡7蝣蠑WhRBWiqVRq 6SZ@nH垂 蹴DVD{On?\~d|{oo阮:鐡+atqj筈 (/ zEmc7nbb 殪H犂67[舍}n覿糂9$b滄g=恬齦C9GGYbNu濂i>}bM#J704mx觚?m36 =3V_陬簗*b=jE8`@[t敢jF9+ > b;i 0Rt濫\バ1>Q0JJV/|<宛揀zx#漫a9g J\允V~樺 aAy3C/E8拘 Gcaid吠8FM]4草c)W}{索z5'2u|"/OJO4@L*'ppXG瑯o]緻)自\弥k!LZWtHo`#"dFA)a瑁 d\'0ス%E3b]^T 旬Ca]P 劔蒟fot  律 #57WIB皈髄{Y(9S\-]0_F5J,Tj@蒲装 l_P+9Ch|腿@珀CpT |*倡VgpｈoM8a\,僖74肖 瞭bOIQ舟=x`wsx~`亥7跌zlg{?0~xC繩3Qg?IM*Pv7c各a.hzVAD|9K &j8Q岱(歡z W+ix#aEW幻'5@jiZXoT凄Z^6 i KvG0籬$嵎G(+pQ2誹,^?++`jq!ポH硬hO7>GN~;刮[WI(菰yMi r蠶少%l4-芸h7孱鱧/Fs迹/frz`僵y祝EO浄瑁挿#/crE}~苣按法|豚+.GOa'@福h,*ka4*Ne摘繝C:*+>P3p+IeB -c晃笹圄?cF sq5ΙVicDtr堊3 ?{ｕ'm b?y7k閑x d甬hZ1 |Z z!郎3F;!/|z C'!qオ[!' Qg+*]娼[y3霊燃w}9`|b彦rﾝS25蝗ｹ8£/_}qjvLA*9檗zKN{'#聰)bk}j+_Vo!P[_@cOC >ヒ 6 V9~0`泗hU澣t*f/p悶E.IS4CCO憎陛3$哢 !|童Qfi蠶A0kEwP<-(g(a'J @V4Zf4bXYd凪Z."ﾟ 斷F3_N萩fnJ>AL-Hc 驪kUs減g%`M侶>x9-+I`vlH+HX nm+]饑k#x'S >.b遶漫J9\4Q\)t`^^獏 "sS匣G掵~J.8輊 Wkr6L4CQd7壑D歃3~ 7!Hd5ぁ-)D猶g]E '"zν衢逵`oPT 坪瓩5'MlmG_ct]* b QO5~_( zo'O'[cE`Ae(^fP'ICT%VBTt/dZ{l蹠K6WI魎&ue馮E4KV;st濁H殳翕glJl4溶>pe稘葹BI!`てoR~eV)TBLI餐#O9/ =嫡s+ nB9!6Ep-化Rcs裙臼VcixXFQG Bdp$*rE /-83D~&fXK`sE+Q@la%+ 鴛 薺K傭擲!Kv';cdo`$F禍 cxN0h:憐g+Fk =J% p`vs朖g6Z6\7Ekc}[pYKb m-7Jv $$紊 L奥 -=nP梱,)=S:責 |v&犁NxfEV^iA{~罘礁*wwz賞毟9┠+ MujT_z"@fX臑&46c6YB/T@透g)K誦(qV[*曼c蚊U[+S 3"斂黛u=/紡鴬,[<8矛l7Q(3_f#x;a,aV)hj1>5T6CUH2>4霙.YC 9v=栞殃t.qr塁pn)QU.教kh(猟&`cr殿(QS晦膿qY\*p@咢R!'Q藷OEZn~tﾔ*E鍠)c粟F,i@m'6qw2X'〔`仄鍋?kK^j座h]"蜂IS0OCqE[,sp)-?YrJ戎閠3-4抛kZf7ゐ懍?l@n'3TnwW!V>VF]hKihM'x賈冊\5nLKf6Qd杁e;y>p 9`hp &#!孱msjaQf轄IY!#D焚5淘`懇l趨)*兔MfXiw做紹N9=5)R(@戲L1rJ X%秘qyR1"勠 {!+tﾗr7Z=YjQ冷5;C螟1a3兔En|?(咫>H8\KUF&* J油I僅~E^/N/i^麪壥T-9y:E;d壘r/?s|x0RJ;3V>哦/鑰S弐國^ c喟'嗔"v茲:,. !,p t[)d~3T゜ X.=@!Kbz<ﾇ_{L]wn-g*_-sRz&g{|Pv賤 #OuI'YIc G?VB& 9O?BrF7Lr-"Gk\D儻X : #:USJ&|xdju%SY%n}QQ<峯Y礁IJ-+kQ9(qT'3zKツI>rEDYz-`9 筋霖>Q@6"uFeXN@E防rJ > A窪:Q\w壤%yioj R冠(^0 瞶 Y\w ちJ鵑&l罠t4N瓠u.(uL^Y4売z%?⇔r5|j:A*Ev=d6蔦xj謬p$尋hAC笊s Jw畷M@wgW&n~% &XT2.rO"J煩V韵IOh-W+cHmhIB鰄Fq\肅 餮<なi捶\ZbL亅b Q輊 靱R=3c2@},{<#zy,1 'Sc&][~0J^ RA妛然ACl恋!CO+[,+xx1]佃uK;;"戔贍c怎拯CYm椿*!Kb:嗜.Ie6RzRty慶N":Pp.m]桜鸞CE縉琳,~$彬捍{漿丗 ;q,gJ=H]睫O伊瑛毎)6!]h+6hCM@ 皹窟Byhie初♭KF麪h9z e%mn@exz;j桾x;wH=TT渣wUE圏Iw&yHO9 &簣^bc 擲g( V9mRxcq先B 8哈苗.辨})i平e苣Zi3^Z#沍l徽MWet+4hkuV`=X>X隻P罹u6涌On )e2.lt#γ十bL Oz ~EF1mﾏjbn黛2I2*祭,塞,n<a-#賑ft`IO迷r[LT@0I&T謐B%QE"fNFE柏m 96dN/,B"-:"+n_\2V5zBHK9Oz0XBP@{ 9獣|N EN/幵5/嘸Оゥ齠5&3mo"Zi7U鯊A> xB?.ZZ3]嘗睡|;滉瞹$,^Z相QhD&拆kG.AＮ9r*xlP崘@d峨JR隼v$-撚Ap\@%t鶇匡dx&-<_c*H}"CKLH兪丞倭\凝 妁-E' wウ1HoP出 xh聢Ё5R閂fE箏BOMkA堪t]+?DF1%u#C1A&麹/o―[ *dm第n`Xf澪*3n r\ArnDN憚逹AS慨w_7 'U}7>`EAv>{A)ｦ非`怐謂6Iq)iqzvY1dkS括d>o枌r&mc0u+DYn-)f腮鞠H1Rq"|~!蟲BGIRUtjUN齲`鐐芍u$Ip@3udq管匕L!hz_ v迸c-*xID旱g4TQP寺sZ 7 ~)<"-nJrV$zYba &7VLTD匸L,"鑚$4iiBh0 dC.茶No湫碣奈;案J"Ag-8v{o崙瀏+ H狢#ﾓo稷 ?/O;R醺6i})n皎`ｒ$VkYUWU5Aw F+}gFCg >m&F$?b1<`u1 Bs埋鮭l{丸kA9Bn'f}S/km@8c籠MZw捌4 gR1u{{<;3dHP私=T熄NO5NykPJ72x~ゆILc:qwN嶐aW\R寛/J6y({XS1K>5@UJ'渣hg~_ Njvu6o7@>j ` cY觝IJV`t+!号^ Ki4獗罅准MqXV]_(5+]*0D%愨(b*D\+TC[Oq賛8嬋蔬j禅d < G48JE[C]K塒で禀?_= 類!p~厶y_+u?~34陀d@A/釦~5=`'&D(KD措zv悗諢瓔雋押B恪k=3Ua9x"壞T.r)/Fe5攫F3Rk菓cB85% lQ/T[x~s茆 K諛N6錵zv跖牾?D`bVI} 父g解{`27$iAlP 6~f @@-%z軟Y2漓(~}-1v-~4Nb修)`{0l do衰嵬 C%>o.]CUOq此 鏨8S'５x售9I~A烹廟_埴a嶌BNO&'oNK:tuJ")姓TS S^6n簑k`蛸9g争oUeRg8uU>@^QE L/YBH7岷l2G`'JNQE%驕S/轢es羊YSn輒;Z?~L)\f洳M疎 Q mh 死{幻%5ujyH升yrh zD8_`L0ND3I^aF籀1iwy”H獣f<8`邊RNRw:)鹸2|Pc=S$閣]b)]馥#&O_l?'uYp礒A+Wn3c6V40襄$Z;e陥 hIy,R儉]q柚R>*k$*&o?恊(Q渉6F+M1Ta (PRO?dr8易*6転UtZ3]iJL^v恩-換5}iσITAL A2UT&m6zd`|0ed=2w \海鰡 6Ba20h=B][1L$=$z窃[hos癢a驩GA?9J;鰮]Ch8句`_D,sR驥D椁o l |g On}賈 oFn~ 躯[柩Wl顯{t朽+xqp5固v`|駅跌}怒~捌 :_jpcd_9^N|歟?7 蹂 v貸轄t磐]>牆8貶'呼？料僚=錯x 撲|A{F帚C=}=Otvxw挨弼{;e嘛Swl鰆t~Э攝t~=蓖{n爰]Mz句@g侖 t6m{o<夕到C踪`音l_?O4yｇ q!俵~oWw没p1{yv7 }呱o7n|Eq+V!S3NS病!旙颯/iq9 {,3Z$_穣鳰G僮$:^ !A楕p]l{\d^ fu+豈glGy┸@gy閑g6u"j&4:M椒 w@o?醫j%/k轅 5~k,{l?抂 Zu0:]4t徨pNx +鴪:絢$峅筏-z 愛"U,[t┸g``鐇eJ$&,l0<逍蒂pQL{>EI+u補 rIrmC壻 i3溶q'犹K_T廣 欖q 刻c*%X+=Zｊ\6[P楊9i . D臻|g髟waJ7*dGE00av帯PY ЖR}\釵L= {]!>褊H 焚GT帑f0k?{鮭{z~hg鐐Ie硝sQz2~i独EHX柳勠/8ｉドh油勇{.u}aSxcWgo.s綢_rg|j$6|C]チ豆唄Y rp;QD巧拿u縟#矛|]刔k冤限 B=LjWq跟`A Sfqf瑠[研S崗iKN|蟆+})4z }蠶yd嬌q梦E+A9t SDt?F+恷濬oJNRi鳬Xw饉,飽d 3LGk~b+<P鹸)磁P(n1 袢>卵FL0gb4l2醐(=`K溽px@=P1\"奠8∵劫牲xY0\oI淫+巴]rimv-[y@AwA鮗W℃N鬩m{ kc,iakDO<挨|fJp .勘0駅 執v縷/*A R亢md`*tO|４-y鬱臉K奕秒}d3> 1^L8#Gr它QR ^2拔榮鑒W<$YN: 6:KX.r\捗寤g^S 彬f 94i s痳恥V櫺){Khf.@'C8nJI梦=_;伍qJd胆7､E洌摂=d#2b |~S7憚j9$Iotd&`sH04#へf62鰺EgV^^l-lo:A鏐gSNMgzK6葫M澗oe~f:bc$ｶp蛇 刪D砌=P罍,w筬兀*i_o7-~k飲KjpO-盜z梱hP%瀰晢UlUYj朸PdF@JFr1 ><}r杖$s訌豪 kbt-軆鏥i XYEE|v禿IAQV晋xkU経c0kzR(BfGZU茱 2兀fg聢Zr El埃>SY+w^Ki詁.<Sk8=gN鏖MI鵆Q@R)z}) cG?d任+Oひo$的}J|道LJ犢y^Cl(;kDk跟挿8k/掫?O誠Ol蠕癬%ZdSi茹M- n^{|D\^o迢氛7hso鐐聯^4m_E?XZnb<荼ex}F||恆m|譏.\屬~翅9mj8~C(*lz\MVC5造M3fj'I,u&Z&cSmO蒔k┏辨rJ幽f9悪Uej;w&鱸&\&;fTY+uwH sG=cqj|}位}酷鷏_i嵒#存 咾ox\7MTd0@C@万7鯑[ `8漱hY筥u @[8蚕H26ApMc曇1\d#E?7/wi=徐]Bp俵lCA6<寅>tOZM'd!.W7H劼G引JMtか_t/膨,纎縡p~T&皀C詣s~ctPc[葆Y,%肺 羚>V G怡<-As!cZrd頗笋ZU}n愛鑼電 p (S髢h nh~4fKX醗:pq覘PU鬘PD6襭員3CVK&j:E顋癆ej}Lk.wt(NR齋?L照 y惰 Nu s6lm$W 8‖4?[/nV禿e瘋>鯊^р-{r{1Qzy8-qSJS'懦k-FE7苔)v M6v)&XZU&誘/3TCmq0U3Z笈降百恕 =} |)[4O茣1zc}璽x 唇XLZC6lp|dVg鐶tkA炙亠陛Ad +b[?従-Xi1F貽捗I?F+mblELH.E/挟嫩8cHMMsRW{^0soj!WQ?wgH% u掉L.U柆胯貢凵輔 頡k冽^LK]N$+賞|x7Нl]4(`gb滕`TpッKt髫WZ7@v医ggp轆 !Z=3s$ZW~{uq徒鶚Z6k育vT1G,L0}(f-1Rk!7┘0.o MimAB71LhF:'G"-;┯"欠b(FNG)mEo^\pU塊>)tJps]{9\nm-ku-I{蒄史;WvG~$@^Ap _J擶Q'485 or%悗`3J -_7mS+>q8/.魍肱Lz/Ν.鵐,{V0蟀i総)麸z`hSnJSQxB3)n.T{u GuDNm@u廉私6 黏 憧 Ay9\ +Z9;K銭V憖]lA慾J-w4L]tz坂3H])M qVor|W3~fz1wLHX5J|>4m-41:!lc^0槿t絵?'GA6#^:VDw畄y' ${0_pレVg亡A".允l-* ?`;#!e8^vM c  漕l1\KD(oB\ШA篋33~-縺2H鮹 ?V8JA怠m^T*\yu"\doh-Jmc=媚辷`|G{軋Fg"r/k卑bIB入]_w射30Oc洛 '8~k#燗咢 _Mr0zon|N*龕fc^Kw詈4`P銀Q,瓩l\b&廝C*p7?wiY6膵 21.綻vE1譯6rho{}謐&掲 SIXp6u鷏u〈寸 欄bD?糘.h児/樫潜OA';V8"d/w ZWn_$ `曁ｼl&9U鮟立rs?岸y磚f=)XXO躅TV佗＼逋P;`茂s*^險悧M維\?褊GQ,(Y9{努uT":qu且g/-^$u2飄T脈4r>jL!4U v[V8誡麥O6v-t1#i<唏^&kqJU[g.~kgw刈n&昔権演J~yt 蚶R/У0禰胯Mpp厘⊇K1 茸葺fHCHxhg'J!`$+>z吝罧Dk,Q!6D0x0.NW\t{){聒?E睦r襴"メ%g朗}#t7&!$9力]`l蕊w wq悃qSE >k'H^p>來wC?b厖)])}e{K'zK;j蝋c] 1n禳4黨he (G撫徊Qk文丐廨rm３-7=u Va KYn;複竅8Y"mn纎趣8)畳Z4oj!D$Z*A4/9@PfW淙{p<+@佶7u睫{xyd/S#^担q袱L|{ x*v=w:OikhZ疹x商奴.:LC級 熟葷Y萪雅猜RdwXMH^〇%y Ｐ 70HTT()X罵ヵ9z<罍膣MS'.L]uzp,&z輿h"dKF猛#MАl]Vp 3Z皷Kk 19Mj12f`N-$3周搓薙埔H豺 YMU^uOQZ>uGSＸhH 3彎se-i@LKk鉞wl/R攝yr匐繽百Ia1W+QaD 旗bｐISCplCb5兔軒瑶*#T&I厳[訐 gaSSY 礬$/澆C 糊賁蓁Tw誦\h l舖笆Rl笂Z%oA^nZ?<送YF刃d┫u_]7U a摎(寓力柱鄒\W?荅pk%&t韮9gh_~r仁OOg]皰1aS/5瘢'ga1$3@)vGYゴBrS,B+ Tu&Q\7wp4P)9uM8[油H灸脇0Fj($C$F鰛O渡!:e )tFi0)fKAS@?< 驍勞kG痒I{PJ1捻[53Fva!%SW`+ c!NXi,2va茗)i^[セ~g:(5＠j>4*U]桔~N8擲繻lD4{%5裸ay4;i?樵4p?*W7hnBqg机憑M梏iz-Xm攘ryq ^pdq+Qc,f] '`b&J哽2%7R|做Kkj>\e>徒d\槲埓7`dAx淒6麺~ K|帽n胝SGdo u=kAn|C6L騨7:z,ad-2収OMX&&諦9圸u&|j禮8/翹2&c~1$N綉fc耕g礑~Vq|2&lph樋7笊1Om%狗%e 覧38_bQr屈dCp]t党wI6.陸MOF%悋UN@HU@L 7HtyVmo杖j閧s28.+I5]OwH笹NoB8p軋G}#NVX'sCS> ;o歃髞O#hTk0當(A車c lpq{裸d戻fNB嚢d"[$>$_aW0'gBk6y- v才}霖辷墫q5Z xB"j竿\ 刹 4WJ`I［.|驀k手& +=J資l繕K`韮5uG腺;(I;J!rG3|MX][斛舮ZA騫  ^ ;=@6k~mS}k莨銚4(m!h2J16b$UOrsK)3IK@Lh'M6r 3^G}}aclH3xp楡Jt驛+I~籏My品VvDB7[WQh9甦Ln (rh~a萼舶wI驍#皎kd5{N咫5繽g|:\郤秕D_ψ Y膣鶚>}bR野c犒lUcW`鸛地蹉?$:L3岐b_7h髱Y酸S城.9w# k遺#Z #>.栂crｒ址磧>X黙/<l亡告p VbT.p0添攀{FxI.E 夢df\瓸糞q3畿 .N0!E@>g5 glb昊掖U軻s|Qw[}c6E$ .(怕/ p%=*T~u!^l漏M.q拿I9~m畩折V着r19 %寢n#_R付j琶媼^~檎& K1 K~K|?q肛檳葫U&b"TL-kkj屠p鞏 cUw]FuyRJ&^)!_*D>V躍撚>5枠+u}h C?Z,殳 oL|8]晢"a0M腔"怯5#I;q?J萍SN簑4眈:>L FGC恬~Ijs薐`=g/汢惨"ZA(H佃@1m殳?壞w@臍‐C}?悒|阮√+按 Q郡E'Н=wg├真Oa″沾D2; ]}闡霑??懾A蜊ntsUB{踵0儡4纎i繹U8F.E_` m蹴 ku跋m^$"用mcogP^Kh{[t;穽 喝.靉桙s}A<丕b3傑N}B>RPLWm6_驃p nnm迯裼AusTZ=J雫/G)Qr-m\Km) *1{<3eWX@b(W譲MmVb"WCMY藷=Kb錫) ,rR睛 )y>Yj6hﾃ8s Ym\, K彬ZigZn1m艸"簷tfy*L$V^ rQx|is6\酬J94纏j渓梗[ｰ鎚b#( Kфlp88|ｎX饕NzoHn]楷篇'KｏOlQ求択(褊~O*0萃 d 肺,)P敘~紕lfE淙 6;[骭7|g)co.mi!糯TRYj6固'S霪+\AK#サP耻4cr Q7Wy蘖k<谿YO[5O嚠P梅z4昿/[@M #闔_掎Qe啼Z渥 ~_v=gz++wurq紅,aL/ w粢藝孕C_4B寛p忿81\HR>oFq蕊7onkM'4{鰉蜩\Q`械>^拜蓉ACF岐x#9k-色唱/h/+?mG1b#c,y+oKS搶_r径T B J冽',[4=6ZJP12=M擢&厶G7那癆3G7Vp禾Aｽ芥X&+|俑Z竊9^U5ZいPx>5)竸и$2 道&孕w連5~P<鞳v餾s[dst牌*/yx鷓稽oq$8Nψt仲0?}NfG巳 4*w o D茲!b$19b蝠qD.?GXW$ e]4,刹h6S^5Hq1\8ZqATre坤#c9M~4鍋W #L ey)Qj2 {窺 j 0^Z@Kj4NN[\}霰bt魔/Q~)!t+Iqm*3堋vb偸yk擽FSOsz弐N霜`AD簿yyfO{R矜主褸d7y臑卦7D.0伎T2Nw竃-*!Qh[ZFL 7:H UF幤QJt (店龝2Bi^n`Ww注u&]KKf衍輪xN?K^1X?a.f$慎i3s+粉7Mj~h'拠xid]D cT@榜5{~4` _NGp:?QF["斐 凭G F oZOBnD麝39eDqp\O4 圷C/*蝨rOsE>j嶝"皷/W6ラs&,vw~W(,hgit姻b(,W0尅XWN#[A穫鶤4oIR\h r: u&KHAC|*a`+as∃xX綟$ P>A賓宰#滾蠻Kq{ [3唆N璢DLOnNiL諄殪g7niN界6&u-/9h-HJRT+缺}l7x朸MIeDVNo)yt3`P9fHYv5 #Gn}gY ;_ y*戛7lg:`CUb^集cHFFf7Lz縷痿kgDO臆54崟杪o@秉4~#O暉b晉sp=b徙Vd[<霄rXD=BVy>8莞@ aVV-x_oRx|$ィlv=%(沃p"sR: P>5(愕 I?y$?m 2h8,oTy ZrtR疊B.tLnz Qh様7oru悦E莪.^逕iN9Y*3%I&^砦y2VOlzsk 5決颯[f%澎獨h寇NU,墨Dyq駟iuJ|惚構ZdQ[室鱸)&M+OI誂闍&析有I G n~u狒lbd_ZNU V' "}/]B鶉o1gVby85}縅zXk7殍dXMyCA竓 eC鯊>T.$bE'bqOl)k剪K)sI扞Rs{pF鴬O^.U7qJ !cG/U兒集*CS9阻T#b妨D&H!棣w1GA~;咤|鬚蒋サ5Ukz+5刑_:[8:A+L└lL北AL縱[-kum ;#c)2儡?Λn8菌gtf{S檢Wy晃x{4J{鐔F'x@q任鴣,筺"y朦H獺t迂]rンo昨鑓Mn洽T$蚋H立e牆鱒}Askc]4崑QrJI>_&巉Wpckk/O+%^臉7>XK(K6X逶Pvi造,x:hC /攬輹w5M`StS Q^k刹X>Ot 馘jL..汁W&v 0>~\Q}&丞鶴嫐dOn巷N'蒔|pM}|Uk]oF!)夛辱\l4/6XEw7 b台N .hM$-_勠'戻崘燎| 暾 }綴@)垈>E.ZD齪=;洌/錺r胯J劫t漸鍖瀁*佼}!d悳~N-t#~B G式EI3]笑RJ8鈔}v歐0d[DW静{+r]E.ap鏖[/cぉ愼x3佩?, i r&T[.|4C禪IE@t%zqHEp~hq F'HXE'a2WyQ撹ID做f&o52 VwS\:Mm{m鐘w?歃;寺q抻>kc- 試|葫Szt菁8,U裃[[ t8dLZ!莨)?2旙!1v+_ )] uG靠L Mqs$AaIt\?TT9休a 8Zja永mnu癨隕WTOEKhvI$:K~}oa6Z}H嫋cc<1&jm:rpW 2涙ЪK"@0la粒"cawqぼrxyrp骸DC煮^禎MX _ka>g)YJT(1 Y覿bQ2F|CGj筧BYkB[PdF0j!<瞥e姻R0Nr""鮃hllO-v螢2Z>8 HhяP r Xv鶫Lx+pB∪輪m?skOu似&v!e94[?N洳7椿>W ilTi-\,.']O7E+7^;;O T敏儀股揉Z簾{7f8_,?Uu[o'mT#[ZSY& !En1zR[eb }o>N眈I5n@['NY?IZs敢5mp'んc5C:%Eh\9  xl:十KL6 K)SB 胴~(:|SvO6ik渙n8qw厭匣桎忸Me倔賞=RTxP?SZ閔?慯 v釡潦`7\圓u.募m9S,叱'X~UJBoCO-<А'3羶唄Ws0群\l複6s6o9}炉蝋{杁L4qz亘 麻Lf+;]m9q9L-L!*(ds)Z姜bGx8dI]\mX鼈` hy mwx-O 5%?fP-L^8;e黨僧U鴫dNa5遐7g;LUr:0ev19k緤e h1t柳[$on篶n柴AЮQcQr_慴Qpi^p咯匡V_XnN; 跖9spK[!R淤滕完s<墹i`dU*b{G肴`波L9 UfL洳sa;D0Ws靼 ljSbk@ !VE)K}6Z稙W:9ffcfLE)懷0_ 1*)5Y韮*c4&^SP*?2i茆;碁±邏xペ>Bm$,sグ椣 X營i"I8墮桓# 両-z彪B莞莨at +Yu征妹\c&/yl荒ye8FF考S9XLuxb乙8sY6[0)=鞜}kb}70XIE溌.b匍 M3\o''w薐?n靦飩x'"OeI}瘋D俊煽X『@qlZβ凉仝核?v釟 zpi葢y*q繹;M建]#x`宮xoh 齢C:89F|X<je#]]-5)Y&{-yh1樅.PA{畫-f邁mA&56c2Fo5范筰=w籘{Dz~ c$d-% XF[HXs 契Lx1{癈0'`瑰3%\綏a*4 zYJo%H%]}88扇|└LE0Zu*PT(:i4s&K0 IeNHMb[i珠[r(ex4"2こ.Gm 8恣'Ko!哉 倬c掟%NwB>ThLu7 "1u3f4,/e^oZ75zR<%o膂i甦~~Im蓼"PI*誣P〈 7微O)釦OO$Zn素盥Xw.Wn >Q/ )I累x巣\CQ過"鰉WHU擒({k`滲m:..4彊ナyyDI~E86 H\E{7.l DM酵 KT)甅mJJ妓A△ Chy[貴蔬k銖yP笏oI} t0g沼B? o U{V 7F$ BTS)p:憧宅氛`Xf逗XD$T+KXCU-捺{,z HoR 天K嚊<1I.v"wyK3ZW/sL>Wf0vnj暢iL蝓&[Kjw?d深營=:餔棣oJ憎Bq+EeX+SVL=P4FiJcFq'18t&k共X_}w+?cQ魚XMK採syj)2莎Q£慢(uX爐LX壯1P*BqrZ甎!~HB)u9 偶*h'#e<7漱淅濮Bpnj:m0俔=社8]:|HaH拭&z'R 竅x:膽c<@+\}DG]|8Ckpm框,(~(;GY+哢X:莠|aHN抹0pj}$W sa^:7}O%kuo KB巳H6#u\玩'F韈6β罠８;NCk*監nRﾎdW%屬捶櫃VlGR/]豢6$7y尚evf俾 ChoZu)Y薫',/&0]}k舷~,iQhE眥'E_0.&粛w}D+袰僚IRJ亠O4aBw0TdSx j1q箘k }*{RcF[劃[sQtk継dVwV[叭<刃'5-qS+崗Y$殲xL6.S爭薨Gw]醉cv]金盒@巳5Q6 4HAXn>A-N#ck拱葺Z [=萢8j瀞T}墨`粹6yr課愧屮x0r! =H凧% X]噴唏FkIf鴨齷椴IТs& 棹Ngd4`O_~売H輜 -25>+]墻椎溌33經S儖 tQHx5#疊K$j:;-餠5圷┃姑I0bNCc3~6錬beUqdI檜ゼ閊QOy9'CQ,9AWPL?b-?gDQ*bb%lk醴pxDr% :F 懿O/P!3燒wo糟Y俐獪凝M(?zbBLcJ`o8[@J:vr  6C?7Uyix佩鶯pX 譛.B]aN澹P医 TbbS茆V鷙W|3{架鑄V噺1S_万阪6uz喞i\Oj zfw1O]c!adVmdM"K徙`N&N>`B @Z [G翰訣霑洒Kd!Zz@ryMz/? |nn4:f勿G@硫9%6%XbGZ戚gl瘤:継ぞD?s１9┥扈]hx歃v[8FB#_fnx>{s'N]F7r廢&DJSFD.\\S$xq=#r&6\\wr惟\o|f 4g0(^9勁?U+S1vGmw'i魏3?BsnH'4F粲{^Ln瘋"@~梠WI&w5繽馘\=F{V)w羞*/巧.T|{6;^痲-Z/5^wyn0q>6B; жc丹l弌X )t.~駲)V3qF?A酪yDk=8慯炬5戍5Cci C涜 ZC@Fqc2Z;>/UA%U.k>“KC<74偈l良浅)43P外O:u椚l<る餤卿+R/汝,疊鶴yD e *:E妻:uaVнD#pV隨]KA2 'L斥(t澤<崩\+sJ"1}Jt隻託AF"A| iW,然-,T'*棕S{6／E袿@7瘧 &$ 1"O/$ 1sB/銚i0-校NV糞$ ]藷{-柧P~c gYi{{/`t7對%婢 #Yb5o3 緝\觝憧PNp奇@F∀鮟A&3[X罟tAWv^`uE^ERYb.]/zRH#GTkT%n2xLb(B (Q菫iTd佩(K: .WZMd檬F\rLK9 :HPWk筧u] 岨AQjaJA!掏5 域7A3zpuoN\X#@ A%"1#9 7辭犖D Z(*(隱Qj6驅 TGu筌穴AI EEbNU* 5ru悧^ aG.チ仞XHNau qD#孅a3衣O爿kz8E2v f1/1K髫lJ 鶺w*>5=?桟z V3盆=k5柵旧Y/c駆gs>brSvl-#>e`A[@Woo鯵==優I麩'Wm7muKj購?C傀/]M~9R/N^"JeQ Q>()mpn筌Z1W;B廟I (p>囂|x割$黶SdG+>d&S日埓M怺x%jv<sg2?1_剖H堕+"+TzAvX5Rp頷Ё0:琲)鳧賢=笹K-6CwL-_\}MUp4齟in5cM$:@!a"mK^g4zA4C]吩O$弓8Eo`'zM 8s.椰劇BqL:" 貌U#3y@Ui8S&禺@bJDG/`3昤B^O!1氣V  ~jm(凍_|口朷?I|薊脣鮨豕|fsp&琴(a[f廴dk鰐潼B }烱*J<讃棹末^RAfg\u;ZQA-KB0c8p7廼烏習@艟}&)*c+@A?*1戊L佝HeBrO/b 稘W~W$ub#&*8l7N"冀 "映:K fiE坊 痍妄<飜yA獸yG昧癈^晏QSno▽4F[k 規}W;#H8 y&&CMX\nFj1t7Epv童 $哂_4Al%舶頁 .]p>z刊qoa A.0/.,p例,"樓{0)!C迴壮~媛a纉]8 |西 ~w3~Em}5 (1t瀟aBO酢禍l08]x}毅M;堪9eliq^V鞣{745+nqm~?P-7o'U肉#6u竊D &Ko実4:罎bcMd(GB@Y;zLhэカtU1lKg逐,胥踞$C8叡nf蔗<瘋\QTοOK`j+VYgvr:浜)# 貸5q%%85N[A(n5=jQ'`q  w}!/LJwn^ 0~ 7凋/ЭE4Y\哢"P0v榎t深VlJ7捗i磑' ~]NeQ> [r診f寿鏡xm%/`P暄gwo昊{p]ﾀW>gMd1MJGo?_nri;CU壇[uMBk,{TaDs nBG/`2<3"!航＃A候+#X9-KTB>cgfzxBI滷- 惶`g6(a低"pb所R? 旄.^l56d5鋭(a鋒+槨n6uSsw"媒:蚊r希o曹3cu=Y柢b!F[|tU!{}%Gm嶄0鍼1D.199Gn.WqQm'[Lgゲ;1h6~hwNcq0y9h=5l#偲S0vf?冊 N 出/s;GQ課_h>;Q;V柳l396X58GH6?DlL*ot置4N_B俺i=g*eN"n3EY遺[M&S {l'椢7椋p┼a)_] q1!%Z$]ku"b咯su)zM柴雫BWiΘ1K来 :v(VFア稱槓&森[椚s壁kBo}i 5,b(03NNZWL{哦(n]狐沌EM幇e=冰4%e wL-q滲款p+づWk匕0u騅 Gr eZ邦:X?&裃楾P~Ut 崘~賑Bb> f k5EM┨斜[Ssx&hw春諜猴編.}f湲Yc:l9i/)zW+鯉WWH0:y;&F:C勠茲,0茎7+D~zmz=S@v'06\ID(k$Oo-Y~W[_Y!G{eH?碁昿閨. __Lq :=瑟h緤韜:khc kじ鬯-8O皇$QH?濱_a YΜf 飮B@L蚋鮎r|.藝]排 XrPj'FPＤ攤L%慙-M84禿常L39嗅煢(~ KLnA20^俯鮒M~Q !}Iakm\SQ當"萇u GFbq鍵,_O+ K風"UuG$]L(C<盤K/n >曦挫H祇il, O惟_ 鰯 Ry紙; リjYN5R(巴RC= ""es釋#X!gF2e4$SXl甚O/k膏pN jdP\6w;[3』L4!;OｅB^ H'!P pHh慓2戮91J'xjxD64arB $J+s凍hZBE+ 2稾\kK Hk/52毅Q%趾>[唄%逝zyyiuo :だ& ィ9oQbT%bJ2z0洶Y+殿HL1+[ s/埓{7|殼wP躔陂;m秕uB0(5.tzF鳫r5oB-y3憖1Y+L獵0z&exK-D*VTwOX *WAjQ|瑕K!PvMb?i; {C\{F,7{P?"TQuzE.S潁$U捶篷佐鍾1弭u~+Zb?yeen8窒! n>!`*CG0裲x9_Q#Azbfn*煎tR}k?ht{hVo"Mlc$b^s5W凰 X剪cZnTj[c9 @4筺 yX) i9O^ e6#b8 ZfVl籤[*似f>m\:ΡGZAG SxsCTTs#i-訟女3T?+7&0Ndx`i$l[A廁< t賜n鵑eUJp琶1$Kcz,6V*cy6畔:r:oQ2縡儖Dkt汁2xCfx<^(d$胞nTaL皕7 _(F 犖6,{筰Oz.CMa 盟dWaGj/<典遊!胎帥Q>\O6<衰@;gP}*K霖K!DQ諱=懍枹Og CD據wZ誼册3Wt*a癸P 鉅HA^h-7DP~)7 v?MPydQb!彜 vr%9老.o繦%Nゐ:ISkriQ;V鱚7]q+Q\炳(#|;_AL_btl卒+u&VR&gElL#≪sG&]庭:_BHA5F'x +腫LX'0FCz蚕5と4衄J 腋Qx_x葯~8Uw儒DFkх/N}棊v9Y&l類 g/qZ5f垤S</韋蠶GLnuG514ヰ(4@C亢n-密ro!.bH蜈-椄$m鈷SBluzj＋sb!zfS +蘚x[Ls禁閂k橡*:縞{Ｅs=rWNZFa4餘h6vcOB[郢滴凹nF57黠=佇w`@AS&m>fS獺=`cbR 姙{f  d=W恭Ja秒J s(簫7i秡5~Ss,kBZli~蔓痢Hy=MX9任eh7Ru(挙`P鐐=R蕀"r}JK44hV0冴O>Axt* i噬^J;F[N玳i榕賛'b啄眄得}GNe;ByI癲`Qe/塞 xiT提/鯡kMm77R_激a}@稠揈畭b&g八WhX+ 腱"H托nT+芍DaGwC:掻叙樂w,@mM憮G=羣恣-= ;&.#XH!$9WzuwA;jNP)%kE髦Mq[酥TJGAe:KWbUp蜚\4}];IB>e揚,1濕|sQ@dGA棔(6ぱ=|>VSkj^JA:3xvk :vy{`,,U O *(2z漢 ~4両@Oh潯@默f;Af(O3f坡%k*傑;歯Tz區鋒7l砂．V;桧bP椽 :ｲa#ot赧僭UwPm殿:G晋T+*uh{?VLWAmb|\;_`-s/,}6*P羈vU弥 Fs\qO0製q娉疏2WXP簷 Lip齣z6d<楞{ S's#ЙOWKL(釵|-hhn L磧)+ iZ萵};v%xP1R^8?oB&y6&褒%B霧2X雀hhjaq4 OX頌0z"xB5(.02N`})1@=Pew%'搖ODaLU?@E糯!T冩[%揣釋W*,兀<%幄lGpN9 Qc=Wg'2cト号 N,4@吝,ﾗ5kV謚'偸67|集&3A,ョ*`U縣)Wj倨#U=!@pT8 # zUHL|hal2`/婦0Q貊8]m6f9蜄釦$ф鱆}MC崙BW '蘓9:Dw鹵1仞Ny | <儲ITF`pbUf5X扁-7n厭}sYU%Zsv邸++|04W'aD! $n槁aq2恪傭, BR~ &P#,X瞥@w稾}[ gD^,\YX"亂y阜Dq藍+NqcncjO/*yj9;赭h鈴^S/# `nHuaP繞E'贖V4?_yq{幅{]OW|俾]B"w *畠u曼司~?靫l,眥S&n驍tTW2"筰AvKX廊#,焉T]ndYr_'Ly:慓;儚S6baQ:V饐UムJvB2wC;^>M8JzhB}vu5P=込譎割rsWnpgI&}K!-a{睫裙LS ,'昿Zw粋$a/F z`Jr9.]1HNEX)[5囀劑mj鯱G & M, 6幄"R.r>]9寒-:咾w5 拭zbhW|倦FM $Unリd＠6GKW_i$lMFP_l9qa閃R盖O廸CR[%\ "漾洒5文等d:e'}%F習`%[l&" Q: Id sR褂|!Q飜jR-擅J=g,餞H-1Mn;]bOBc >ygT悗(tT>10餠8b%u#@o.NGXQ}熹Fhｸ,Px+rDMr xT)FBW殿K!!a4*LC穃7+Nev 8Qb碩$@q,仂堝飽:2ORc rN載誘ybsKTf+PfSjYEz_MIJ6弔$=8q&C3L判Lx萱檐+!O8O!_h澀%vz[硫6く:s磧箙Q??FqR5Q_'|VUxNH\罰ix(XJ@f26evX e4,H彙籘_PUZKC RZ雜8Ilh`錻fQ{m",#r5b%B-/泊~W 箪" | QL0^(＃$-i膳Χa蠢gTnjAh 整#g3CＮ%l殤9vs7s8j闊v&i団@!Gg｀\PzTV餒\Dv< 圜auS浄埜 F_{聳aDLY^囓0=cIm(TQYGU(Ｘf2蕨lキ庄vJ:Pn "ac縫-爛|・3_玵4鬩Ba jS\ x8*d0K  猾渦F@I1蠶!-ujt_迴箟3]J1"_阻P<酉釵zEg貳OdGJ$evQ擠]iA_y!uw^TE`e z*Q付鶎w韈Q]:w1t*gfP{F`h#9 6Q8 Cハ)l{L]U&YU 余%!3Pe屓詔UQ -<>r37疹鰯8{ )XNQS#縟=fZG努I吊P皿C殼;ko@zG*.譟GSP*px m0e(tPa`s陞``s韶戟迚1vo@e&0R_O毯咽 |FX;c U茄Hdt8NK!;%'-蓙8lV嶂rr'/r桁*泙)T怯G`*迺Jbp"8#m杰Qqa"0w"9?|wJ:{鈿)T;c貯a'?`h.6Pq贖e!`VZK)尤 [ ▲* Xh牀p*}慾mY{>CBI8?\Rｙwvu跌<p消2ko倭mvR悛f^dslO]j)割_m[  柄9cH粤})悔亨 硝%-g7V得jkp1T`W}Iさ`蜂aIW6 1 6=^C^.c 跨_%鵐"槊鐐e[ 端h=@Ζ(pZ朸~5F}i1M?爺/} GOpfL枉XF裟OoG顛n軅ed過[NX*9N繊糖7J}y?ac(膂8願/^LMiy 伝NdOc<航By~,忍/5.3F^=O%2y AB [w2遐:d8儻wHh1/乎If+0/┏C迴|f鉞#P F遏gt鉉?{wT]:5I析辰奩ny嵩 K`KqDc/4螂:^/lZ奔濬w/ Кc義闕凝_D變h)-Gm6V + 隠鑰龜熟<;蹊|xt7q=):,_:敦供{%&I;H\:Meu{Wg~$WfGw#PS8b'宅A {$If+ D身霖H1Vu?ホv0磋i戲CT俘h7Gv!>.d 4庵sIg迚 &)7%烹&d!T^ON>c)Mpe_4 鄂EK#稿n慇ｿth&{^$|yS'hxz)zw4M+Z0 iZ殻UoH\CokHv屁淤kwjMKANxz囁8i{/D芸YDpﾝ%Z3蚤l)枦fアB-" 8E哥 鐺l7褓'yD\w"GIr 默E%b8=mI.s<_Nd飢qΚg捫]n2Q~38VU*nLjz!ur(20$I_'J[c蛤9茗?w]7p貌$RUjd8礪. E 立.埼MU|!Gm鍾ヰX;&Y=d#5J]>主#L:AOUy.cS鏐X 8塲諠YXH舅 Z~傭g腆縡;P1O倅;uuR95Am*W>*u鰺{XUD倨X像W?;y<=3邸HN要G溷g>惆7趺L|&1Lrモ+o;WsL1DD:5Sa$DЛiK >FrZ6 \/#KGw溝rv&r%Iqa~ e F]fP#n螢0P萵K87鯣'ltiZl"搭\ivj佇:枹脂喇GVＷl皰 pDs:3V臘bkh8S6pE#8'+WTBr0LDYtNPEie74);HX騫S脳0ixee Y C兒[ b慊獸!& A?r$tU Zt&)DnG瞽DGB攘Uk8暈 苻$I~4U1贐;r'墮3 q歡Z碩粭i50u;=ruA(径.7%iT.個#M9Q'(@F>8*f`E>*yb,F甼sBI呀>&I奘f梅杷謌IFd}KNﾟ侖a$7V圃A&BjA潰zq^G`>ByJ.*VhFN挟CXJFuB撚J輊.8莖iU髻9 蝨 fH[ c'/P.8VA湎{1Uv簇xx:ku^;jJjP T9.5m3e蒟I7>V3(6Wp!Sf,8x.Ox" #h諺掬Z2 =-#Vj8V"z U.|轂53SW蒿 G榕刺ta`ty32RAnGu/)=y:BﾗD9~Rp*'ASK{4"U|剱朧O:d >1L@繭K:lt*<猪促;R H`s7[ZA騁x"騁I;G哽l$筧e棋狷潤 xl\R糾0LLTlvK!*>iXQB8Z\xe疋1;-6'戯qa1ex未zu9^Z|挙Wb$AP疼KcB鮫JT&06犖槙匆洋佑Ex,-}@^`24臥NNvlR 阿о$繦鬯蓼k癜O棘e# I^5D?,茹筮βd V難>8遙T,S3zIKwv`< &HHr鐇鰤| (^BUU6z$;4p廂>Q衵SjPtAG PVKYY9;6#Lqnp$雫qh9'wUHF± ([ka p"希(>\蠕o\$ 穏uFf估Hr%T)]' $J"Z祈;滝XV'\`Ec6銷◎'浩}]UP嬲6I8槝&T!gg*.Y}k抗D:aめn|b)9P\它@T:{\･蝓r艀"C丕e '3 D簗ﾁ5(u 3Cy9dL哽Ma豁!<@x{0f于涸 (G3/|Q号ﾗ@1&[>K.CscZ%~,÷xuC^zn,6擇b] c姑ゼ#U}|l]bT-EE衝気A#iASs15c忱m&}貮LV!=G?TDeYZUbS:sE*FY,::4Fmnc匳bq奕抄@|~4t8游zG3'殴 4*愴{GsYz流 yT窒t逧(IbBErEZxAH4=(~祥VrΦ槻ku'陵eTI/eMZ&0Ix !)yY駑<M跿,5幺S捍sMY 0*\yRa飫lEAS迄偐籀 :榮遙|昜1GbKAFb'彁bX}/堝c 褥 8onh<2oOgs‘情輙I9aB6>T+":  部BQ#q\ Vdd)QgF)Ikcl"繹|qr6.b@麼N 55Im銑5Z@0 .h,pQCBe1}s啌送wl5磯角 TwUJd~7里 F諜乳WocB[?2z菟8}};P甦ta消{称怒W√姶=Y儺几W詐幼Z,N=01R=wf gJf~襷sFJ`Fb錣D$bZL/r+k*膤濬cvd9.y百m_S3x_ 中／偸3=論?_46-蓖<p xo{>鷏鞳錐=8懴LO 萓 <价e頏C"G-(絖|LSlF;^迪G"[\`K"びEa 齏B)Nv!Ok蜉;慱9Hキ+z&51Fm0F&?6c聲j]Y%0/;Gi8|積从xCN\5;k^爵Z脆^V{W3C疱![4!舎1(GK 槿蛙R- x,W塾$m\断FT-W\MU氈#UCTaB\u0!Q CM{T1$@蹈Bc+;8鰤23t 2gNc瑾)( Qr|:K qD&jE-s腰Sp:p|怫{c^勣xYX@F村a4)!xBm\硝8c.T l48&=Dg'\ #&妻K@o|HQmGL忘>vp'5O搭,肌< $h cNｑ*k^i=lvz-2lHj習n~烱flT eh93 RN 稘uyb[e8O\W屬!姿& B #pNZR 1M alW-#拳RbTm@i歉6G%HBSx 2XhE 6 " v"o飾,8m@纉pn3G4k^c醺覲7y骰栫霏I蛞裔Yo)"/|*1EJ媽鯤}L%In資黼 =qb;>劒+冉yS丹焉O'pi_ ;81 桿ih `C2!褸8{B韵頗Q奐 v詳f Xi裳Z讓狗W*O|vmEz綯蛙9}倒XU祢"紋縮' gM>%鑵戈s關梁麻o*EpNXfN瀋/}\V鞜 5屈透k&Zめmr冓迢儼變茣I(]韜刳-繁Do\z6wk顔=効_檐q}藷 售k0v柝|県=}uY憐u圸ZB羌\o菌~M献JD Qgo\>K畆z.殘漸 *Uk検JAwk"9u6ny宍剃J閲~]rXVq0c鯑薬窪?根u4z5ekusbDKo0gtc篦Lu zc5.23喋 ,r:{戛Y淙L糲Y\*X+檠m:〇ur()冕z'W~ z)}遺}8隅f}%u'+tWk凝!>Da]orxSFV (SSMJP'P癧% LYdY<祖ェ@Q$u:_珎cぱk鉞努+檪_^&牡H黄0*~&'gbomb#102{鐺2癒}繙震~,bBC;T=-k〔$YO',P鐐涸Q魎|C X圷Q _tFIJ棄($_/^82LBn漢 懆~QB;$VA~焜a)nBC广槻p\ Ypp?[綟f`sA筧Z饕腕gc&r{JP蕚'5wFtco＋}+Z綬oD觀|*櫪^εdCtddv0兔_ky }y|馨^r9Fh/-1hlf8%P4忿pR昴i[`I晰a陂O8t"[+woA {3≒s4l4袖;鑞s柧p>3o 9モ壇魄蘭2媾/?驥(綜'?e@I1Dq9づF b/*'U違2澂4FI86fz(ko KBM2K0p艨O應 mK0 )}ま*yERDCyi冥k疋bR蕭千+x噴}宗RD錬I負K{hird&装%#親DV!%-穐_'M)t,RTAO 3煙V薄R%'L~2w5l)zVE- ?騫R:f :JvVh-N亮hddI>.Q聖価q 穿Zp4j 蠧<慴lhRdu)h ?SXbEh譁~Rj"嵎gcP屈YU(f1瘻$M嘩8diH渦Mtz Ai;H6qN.)EA??t(涼_2|賃J]宣隹+翔1z^;柁Am TI2oU蜂 ∞b皰L(|0(uMs9DF>y靂J"裳Q羌E鴛蛙国=飽慯W ^nk艚(= v4R垉ｯ!a益R6@L$IjcRLC@t 足t'♀! r~~裙啖D毎GM剴c-拊]cｙ姫e蛬..yXrv ;!+4u鐸"\]v 悚冶J4К已WE4鶴?Z糂n駒体q;I郡扮7wv!6q##dM%謗爾L彊諢钁Z搖g"Q[rT|落璧bC!l16ε=q笂]o>籬pW8K檍蟷WOU?a[Fx :鬮Y,UﾖM[frc棍d]沛狗$:\ZMl7BGKwAe_^y5]'cI6w佰|[鳶y臺+o3 苟Gc戟5鮪zwz9挫:CZ?}b`MN(殤樂w|j鷄w.*|78uyz-剏登景辱hΡ~WvNa嚥 "招p% ?嫡E04oKJ8FZkT>交衢TiCoI詭t舟oc 蛆濺,d0q宰 HbO*0G框約G腓w銚jd官`虫沍jMV?･Y"A'ol4TW`Mw慎柯S狛徇,雇pCF糶Q♂e陏Vh昃i瘤鷄?IY*e20Lit;:6/ MionLLX\Y`?C環6p鮖y贖># ~4Z8*@IFU. c1s冐9;+*ZwR s[°兇．S.B臾%|sb擺MD読`屍NC5=V"aFFК82琳P鐚HxY%K?E8訐#5}畩Q!i`:~DFG0%F1%rvh5]袍3rrq痾H漢Ck_Q:A&@N+;Ns f1v鄂E論D*頂NaN+f沾*鋏?ki3?Rh@?">"6 /h,BIIkQS:^L2X<烙x3苣mEMD;hD詔:V/oKGu邑S &$b6oH7D゜<}噃' 63wgw 韭覲8X2t懸|W3+fV寢寉OQ"蘭欷qV2 R xR蔗XR^ 8Vmg薊1納鑚=yM, dr_d@NGxh9讒e ,yF<8$rk:O<`"Qh uS&`卯登%'SKe$U::c#e<%猶緤~877PwA5`1?jps裾 w^u擡cc7oE Ds袍蕨@bT/ xhYgZ&8m4P棺礦;-8葫 [穆!ok xANA 淤zbFz*E錙`薛n:*Rj甑h4oTi0銭m/L\簽K(QηP篇HM情4[b:a1芳XN);装W扈J*DZ謁eT茫層H!綫=r泉4~織e0O~蜂/'F8=;!u頓 L@:W幵苜倅M1^譲:4(p+o*1醢L 濱_9卞恊sr蛆 7U3 枇Z蔓e!t'py7(艶(PC_w%6WV~hnEs*.E矩x瞼4-E 阿#v*@PUIZo^J~O'cqOb#泡a}7L訓w&ol渣b剪wyh武Uav<厖sfwK ~D{暮蜿H)Nrs鉈闌^Cp( hS'pN#R| EF)來奉'z(!(臼sos礒-B&>Zn42ws囀神fs0霓KZ%0Z Z晋p醴測A6劇D3I5L飢)XyJ[wSLj筰q+1h*6k刊m>)o{i;4`C溷m }愃IerS|sogrYv| | %wtl\7i状J8M去CX碍4!J\G2PRLM算燠慟&/頏6y蓖Ad 啜-"r|楡=(2rQ草F- mkr-KY,~蠶y `M,籠kｻ彎--賍壟ッ-;Ni5i '.槲:]nB8!~c茫x7#W痰箔b v;４h\'c1FG叔攣}Z<疂3O)_7H|兪LG?W+)I擡隰]誤AjkR#-et^0鐫微,Y<3'/aJ;冢>M8Z繞\~、7箏紫|跡6羯Lk,.6! e/ＺoR#昵 [ `5eV+5吭w-Vk4只 跟wA^M辯f]Nk FlS規3麒脱%u 彗a|ry3遒#pWa量母L IiJ$K]=- |slSkUNR`侠]m+Wvg^%psh^x渋 f1耿CQ瘻)_~49荊鞆 T抹2郊濠#Fjq?PLk_r3G0玩桃V@ 栴晟dc6.F 5FQm彖\)/lrjh`{領1)ｆ蔽XJ説S癇 {!b)Rb蛔;Bu/S (ZC4V蟹鬘螢幽R%[q蠎l[L"?AH&r## s9周J疝 сR9舮^5#jc;ぱV}0c@EZ~酵IG款a!eVA#w]+P燧&ng )u%侖g槎ﾏ詒<竒LtG: w2ZpR楳%(@yPcTv$?臉^y黨~,NSfKXd:B-.:2V*fU蝉Q7]顛卓8z% w#;aK%#z磧")Xr?|店鑓┠U壊8G哽*1w９b[;= 6(J My 吃Ga頸J REC&t)%6*uwE]r"V-scLYl4, -+12QQKrwW猯c1RB7< ♭狗>\'&<4}JU0弉t 4'瞎f儘[Cs\c ` 80v*禊?QF8\ a)q83巴Z{Yr恭_Ss椶28|漉>S橇!: kq; 狭i#q#/2 S 僖_予6!!羶嘱KW<\ GRqh-hC>GU{-怎~']^3>$-?e"豈j惇C租謀4-aｍx%L(\侘H&op`w稷hE 弩p|Z>2滲z:(f%W[)riE"ZW&VX"ル]"Y晤 7k陽bu鉋Xq-U]_RF.tIF淇觀$3烏搭-Z95-AQVt:bF徇)kx誇@渉V?甑]`兮a粲CxD|許hoi51兮y饉女khumyj燬.~4C. 譎cダ4辜Fn2NZ褫W`r%T肅S榑;/\諮洙m46D茶僖q矇( ~Rcx0ro(dv膏彼>%$昿 9(JcmV E0t;_ 'jR醂|y聒|)m>u>IyM5ej5劃O .1`力欖V2@-Cq /m━Gv4G.辷r子送CaVRu6禰Hn)w涛8E Vf_nG:h"{Z淆D3wu$X E柬/p+Nnr G踞p Mz@:Z (s‰F9uRL,uo}lPb訛;7[蹂zUZQ輌K&AXi偃-T(G<G?Ao wV.f羅佇@ ?{凶u┸0ys=-6=08嫌{輅+ue3Ych隱主a? #?}&民5J-cx2F#囿&[tふ担OI黹4y(螳[成箴I6`\QO*功$.#`{$[nふ~A9 夸$}I圈xV! Rで9斈bE3鯨rv\菅p s ,[j~A iX$%E桔`p'R=M|:R&>$h75 NOc;從=`<6U挨z+釛s遣d菖LQjk`e斜グA" J [蛯尋AY >Pa(釘\6U鞁 U-6L5MgJ,追-M9_ 柝m(Z讚]B3e帝uq稀n5^-.KLT  0M渋.hШUe]MW裙q]柔'收/cj}TT5 )襦槇犹X浴v襯Z z{b6j"R8A-z5Z :tVPCP47!Wf#/ぞz_,-3髪][TP}Tzo柬x#2訃 着r?F_GaJ災1禺ERyL*>^FZ毎bEVn辧~+IvU7l=QTn[藕Q *h8U\z$硝癈FI萋XLVpXk-@Y&7}`Is熊xa E絨]Uez%怦Y# O&尢rcr `u爼覈幵G\%稀2euQ#hT鱶｣yJn筌.RLj}ax`! r-y智j\瞹+`w>c霖H;乂uJ曵珪餒6X彑9CSd樣蜉攪m6X~>_x$FtDsnA9Lr*T$4%NK¬`<梟+n2Qqi圓piB%4伯>沙>(L&AX\複 I^*5x"Tム@曖Q苒｡ I(m#$6+a埴O5齟[n眞$24H綺`?;,TDg}｀]w側HQ#a遖+k游朷把9c Dgd痢BtbB+苗_蜜L"I翊J066硫ps&p-&8% |('邁b滌27A]fT>NHp1rG逃@q]NLFb∠ | jxд竣mcIHPl#U嫋3_板6W庭#$GM> 輾lv;]qmb\bR迹H{廼p\螯WA# %qH7"nkJY'sNVHLV0Qv+HxE%1a酳{4 eO竢8{4('#n}L{:甍yg}BM#'YoS1愿!"!lBD,-B岐8!6肪pF瞼HzTWu!&c鰤IL`EGuG6oT  ! wi5P\~J綟V 槌_O>U<$8hclp UJFa k$uXk~9Dbpe`r 鑠X0v}ﾉ#*堰Z{w&>zHW5w#w⇒8p&}68^r^>%-q9ev8*澀簿Z5h腰OPxνK~t[俶>w)FE3v0}b,~u軫7D0v1HuspJ2y{z>h(N壬BWK}訛JE.bG 型|,W£\IW( K_黷 $Mf\Rs稻tED{rE 7GZ}W謡^嫂^-0蔑9pJ厳 ssWL;GIeXNKo qO@現yI脃 l!HH庄I朝:齟Ia穿+Q2NFr(/R?痴g闔{Q啼誚=TNね2役f4bM菜70(4辣平GQ"&AX8魁隰=}Q2Lsr1領^?糜R/(;枡t-香G蛄B卩3* kJlCwK9 {!d udv:悸中]kud $Pvb業LqEFwU4m槽!隙!;W*AC荒^)H!`!蒿`臚r0ZqZ*^UU]痒}k]>:7~0}@ o蒲n\0{em`wsE~zs/≫$o.5QVP帳#MZ-$MdN峭(bY'g{'g=K｛$ヌ檠Ub,T:u<沫>w`=硝 >弾ATr|^4 iI@1?z%XP.X,仏ХN碎9\煢i6x^Z珂ﾚP"]B[4(s>(N88J.棠菅RH償罩0W疔o*mW滿隋n潁>-糯 x O-.基_~Q-Su蜥W6,|-托u[秧裸Oay 8`:XZ疳x;z =菩@y`6俛uP7b8y炎忿6y草z6p ysk箔v@\ut鞳守HPPK*ヘM2?;k孟dd;`7V$IM=N鏐攣1)0H激[977T>50TOSD([ c|a`(QR89d{5!j1G胄~u|INI氓!f鴕謇OG裏 }鰉g3泙徹sE}ULg* 9axﾚ&孤@uy6數%N僞mg0'兎哄3a反{r^'=0&J抑;7mZ薯#O9s"sギ籤6藤?6漱TDG!@gV朗 [檍h%L臾!杖pX |蹲狷R畳]R*+否k^E@sB zO!訂H@Y擾鉈A榾-# &95$Pw^p伺ro#'.^MT1偈BYyH`b XZ?<9>>~J纓Q_T*q l`述N1毀_B-萠 *C6ZU?斥畛P.G贖 5&>^際m夷QSA _PCge刀A&.:;N)4 S渓2jnhjS&J01cDBZ5脣=6.(_MO|WGfO}a%P質飾4粱hydsb*-湛 pk=J+oA"I抂mMOA Kr0aZW" W~ 玳4|齊?0l{ *~MiE諾v]棘.跼0_aEf錏]逢AS釵_@蘯 穽f*u＃"/ogW.!hro[P88[e7|Ns敍#停W鴾qe&.玄"8^i掛Yr%WUI)癢穿C>¶提JQV{r5^:s`vy,![v^`df颶 M{;=C.#宛ndQ:Jw1Ap'ye茎q 萪*д爿TR琺y4 ^5kPO4*D5K~]}=>!*s"26-n DF9νBfr檢gtq~W嵩JQ;U櫓&A*39綬wavx&J瑟[B|茴tH-Go|Bz 9D&S広^n*z*CQwp7= <軾揩|;岬nl:瘡*0_(Q牲9肭a母ふ私(f6U_#_梭u|W淨PJ純L繞q寄`籔kQW疋K,.涼/Dmz^]踞緞_sZ沱@Y+K 嬾 6*kK7 5hG3K#&=rRL4逖OY榴}(_^(|j{|=9l湍JON(Je茅00L 絮\G)> 5\;腿V(ew_椰R~踉7Z13T齏dZI悠0eA^W輻7B"O|o}伜劇g* Q~q)迅aAr矜Ho_dE\書6\&4 読psg$-1Q%68偬*&D gBt7o爭o(^FGK袙5E C敷n罪|[9o>2[ jN2A翁B渡硫/ G鴃%6rdME{t`$al#0QU4PgK{v?{mDwZ:T 6Zt3S=d姿viSgr*g>惺`\!$V/Sa] 6c棠7Q皃眄Ａ8BGw蜴x#=TK看ysOy-胎uB[o{S夥羶α捲輹N9+TH<輟;}\ -j$妹D9礬hur+iNhuｈk %u ,](~z痿m {0%挺XX64,;!P "k\? 檎f勍|憐稀EC[(ln:if骼儀u'侫N痒奢Z0\x左j'{ow&P眸剔0! 咤 enいCD6#ЁV膠7k :'oiC#rI*UEhFa58d幤0egC>NG2O Nv 》!BX'&a蘢lBe'稗x買t ' N8蜈0*!5S}}ZC /1,DWm溺a{m.２燵FEw7Ds鴛Jc;*L 塰BMIDcL{H2殯沛px斉eDSj+木Y$⊆;許sl_HaL*&,nxO@t(:jdt5w*Y ?壽)dｼL 6閙~o險n2蝟&Z{m8綸s&|@;^1_|σ[!9 o汳U`hﾑ)?.\#.Y鈬}]{7N礫微Y88 I #柄` Qf/YRYX亮# ij)tkHY&k8 金酖8n9+O лg佃sVT%uL5o4: hcygE eEL･2 N ビAY2uRi'5A,VtN O岌3.sLJ:uQ>f! m迂3+ce弱b瞑D打怩218fy=HO+凶W;螟匈令2蜑J6y'@ =UqL5 =~cLP碧)'Z8CgSE夸郊E4e<]4FhG8e2;蘆膤M-R>苒6鈔T`甸`^_致3仰^*m~謝ｃ\&({測l na`o逐ps,f{趣w>碍撰jV_dtW,昧珪v-+z" ?2>N=y篦I. 鴎番武紅q*rx蔔4柩SROXb{9舞奨O5:6 |奏7z5 {:*ヴzjKa-T|箭%Lqhh~ +"*霈!蛻莟@伊絨\^g;褌Q7菅w雛漲G畊肓q1 譲燠$:揆U2村U)L~9sT'6j7%uo^6!Vr&Yf4鶩ZU/UL□L5跳yz圉 Nsy[QG4 I.fy}]\_tt畧EoG],赫T/3聶"U∀g =:J SAap鞄蜴r撒=萸/ ^qx7 zねp g捕V o曚`II 雨"戳mw 弊* z= sxM鵝T+P函zK垣v{As胸輟劑Pq存Q@dZwR.箇d]A@V?m4苑a^sjwJF&o;)nK)UU 楪02`jno+nF1逅 J市 歟 M廈d, 8P6SR&貢[hﾑ%w>,y概Cg蘿(1"N櫂M記3a=1Yn]6粢3L┤O9DKgF(.q _r`=0)q/ g`G{(DS Y萵:d!K^Nv(I5橄(2麭A47WG8PF9]*j;務x?hh:FJU_9$g4拒1e芙"J\霪|擯mB!N蘭&Q19~SK=竅絖.8浹?C>#L%閠[y]d樒,bcU｛Ms*達;｀qpU&:,T鬻z玄Uh帑廂]:$g;T*`=些j$7I搏簸@p]y ;n  {Z$p樵`jU]5nSI悉n)5:..CTV\ Y矢hC(d庭qOv2g┴8:lv痕=U.]宴;i暈dT3dxx羶ΘHF".洌p幻.XF) Qe w猿謬h僭aDp唄uH~%Rm-6傷90aKp?M RV{s'Qq葉纉k}7'E%曦莵K節儚ぺ@掲 c\8;朦過,P Q7o釦Mas差n邇喨a|_6IM%YjgB 95帛V4p裼xmsan蛹SV+!8^9ErE=2kL9>zX+|r e]3Kq 今@=-箱6:蘚!幹y0濺if#6^bdD!6Vn_d0-u餐廃麗 霹v9^M我j凌lqw%95*%i莅t指 $-[n丱fuPFQ&WMF鈔ahGd#wP=,亶S7B:_hG蛬羔~7gNie拾)D5uj'w頡'n8Cl_K蝗〆\ Ujq宵M萄R^冱34 t諛F8y"/ 奪T6b#洟U=&蔵:纏#+互 o粽&園系=D"動^$~ b払wqpk窄Q嚏m_UM~` V怖;;厩5f RE]W jC=甓韭 8Jo 浤/7YaMr;真諆n_xn]N 撚1海r赤#DhSYLI47rn靉OC MＰw) 'ubWw(DInnvv]ax4EI+sDr朦~WxO[wnjq留臻b>e@'{4怏猩 3転f)%NR壽 GQi0X茆J+( &`&熔ri7e/C_W=XOヰ BZH眇疽w笵`hp躬b(kLkO'G4)t!l7&詭V>翻41J3La]h!U.o7r,o除U|戎^&XF杉-4|MF~r wpnbc4雜K{>P77_&)iﾑT 國n|衄$*f;{3I詁Ow誤o:;%抂6|x?1>胚Rvs#樅AE`標\-6@@BU 飭FUM BB/ i8LPU66MjSQ "I･j~Vt泅ZmjHJN)0莓rr>E屮撤I彭悩団B%]傚刑q=JKV8yx_ HUM8C}2-yQ[BiWP +^EC構Ml心檄G臾:{?_H/brw$髄T$,gw #峙J#E"面^B j Er'0#7[畊%e\d2#1!V5C7,( {,N7Nmh/戦G烙N/ASJ_} 迯撮G峯A陏8H{チwr-1R辭鸞fW(掠烽W.垣kc濱 Z接杰周_Hj需掣?z5砦:Nu棲象3>(\"稚%SYr 2 .drTo||/]貲焉l ]攤kv=巷m(a78(6NV.幣"[塁-齢 Q @ S#vw絡Mメ乕6裝ff宕W414辷@e峰hp訂"uz`b|7.荐V2-N螳嶝- 卍!)HG,:辛Ia~psHQ[F4GGytf7罕WV\B`寿躁1SR|籥vd冢.琅g咆jJ據=,ceh_ r巨蛇9p 蠍e私uvA49b |邵Y_jHjp愈9\A詑^m档I竟@+?瑪K0t7~9x陜扞vI7=\oC碍-運;p Ω,0yG@{t,qcZ )Z}B_/n"v=rbGxG娟;E"g石;#撹|O謳!L港/H~0 )[,p憖y鞜;T1ZW}l uZD~* j,L(;I銓*O3#-SRP Nc,p椨"Z} AqeA (C蛋\;4(f `;V(I奴鐔M!Z9 鼬.Zu聢迎E0#<2uh?庫讎8縣='&:劬MqCQU)~Tv煌w1&v875域票 裟J`芟W燼c筆8廱+EK^ 7s0^t!1qd,O"A滴祈tEＧ2Wct1齪%) G$ 尿o *>覦=?~s`UC芬嚀`G\策l}路#'瓰S瘻qT6M%D] f謳8lyFwo7gW?狠FEP]3 $!Y%%h s?>>Llurdx7Sbk?'rifV5z$\逢^'G梭M-mn[eX3j!4zr1TO#b虻:衆z:jU琺N髦 GY9蚯cn-g)Eivqf\弉7憑LfM}ｐV R00~措Q｝\{#Z? 2|fS\}].Q陀C弊C眠+e$V!9ち汢C%項癰*w蹢sQu}KO0@4邏?薯 茘>説 浦覘_}I4惓樢7416A h(jS}Z })r輅?84淋}Wy3wn隹w?|謦7 -*X2r1TyN)]}'0銀斛#+c/Cl餬$o+昜p?Uｺ;(耗44o+* ^擾g7^當*嫂}棒cO?*鰻もV遷腔苣U&U渝uimm誥o崇?3oVP 携a[s 0Q>*X]{DyE[囁4拓(dQKK) [af Z8 &h-%@鵁1KQ莟*K(*因XbD⊃^a}‘熏apg9pyu87磊M]c$DLaLB/jpG鰛e6FG]ga/?oyF1p _ & LRrD腴aq瓱V4〜p侖鎬G9@Z# Mi;_*.w$T { {'1B▽淞fR#c 症t9c埠`DmyUU iO4hMQ0:F> c99Y膰.絆鐃{t~A店F蚋7s燠操W@癩S梃&c V外EP 鰊F]mpz穣嘛vp2i鵙9uT賓I杵I9裄鞄1鮫啄I]1掟 JG&?U+n舍X佻k跡鞄5d]O&泡spHR1r礫-+uI IO t{k6E隧{鐫Bh_aAE#jw6+)sZ %MUVpD*VbK1z d[4P虧@2CeC)2 2L慾-埃 ☆"K%D)/_[$告)i故b1r3H%(矧pr{5K"VG逾吟H|>i=啌vJO仗F9[弓f壅C]toC$]ZUy3 qａ(:I ┥4 ,8X3罘!7嵯 'Ky鍖}M嶮o正潅Hk 洪^vq垳mH 1} I6梅b桍霾Mj氏$`璢I:距Wnn}+ 復}K g+L普;$藾鰲ZVb&bUh"[a{a逮N aI6 wR繃#+^学00X+!覇)!W/`P,繚 A&c薑%)B3莎姆 b%荵莖" 寿o_OGQwnu8草繍`|,/;__Q硬jX%*c;C肯u獗*k\/苡IJ⊆麝W_;_辰>8 lS{U第q(C切$iFuH@V%f澹>迄lg怡K=K|鏥z-Ll5斌Dw飾謠RqD"+n8譬8$/莢o0"Yk疹|=B 弛k鸛楠"> r(cm+@!}捩@槿ymxV虔;顋{+?樅輿 凌~/J Vg{6嗷v?i0H~+抹+_A纎{~/IHES 覽$Lk員ta@:Z>申|(+qп 娃` i5s#!淡鈿a\/>0 樹ｏ5G牛稱i帖 ekxD@.`TE貶?QCA%鄂.z:j偉扈1棕o:xU TO髦`p閖{HAGR Xy8A1ght stt (|靡S3胼V[j7SE葯\-k$z{wλ白 w秉7_\HmA鐫 髻p6)縺oL雰寳134wyM /黽dL3藪S<糒;夸=Sw]l話R}晒襁w]L' _,BD-;’ &漿Bp]lx`oFF~hぱ0塢f攣奎B'{Ag槭l4農春h} &tDl-SP`} S' `$B墾_38d袙撞^'蜴S&)鹿 鑵 8齶yh_>zM:V#t(Z葭総(P苛段1''W[ o燈d!c鴇z|>bWIok;Q警MSХ?W:\甚6\）/2]tp燭xv8Dyf _{FN'juM<9fa+O:n 騨 鐙\亠y┨/酘z^催yQ'6RUFV{ri~"*%}?y`wCOULYQГx M(曰 'aiA0o2蛋H-+?蔗謌\D?71Bbx=)y 吉V,X( 7zXY<窟qc^垂19stes_pn(v伜棋3 k臑尸х耄劉繆HVqbi>z3欹A|r Q: _a攀XXy}=VP?B+м盖V7估a-ty(擺8!餡-NZ$5q/ 7L?[K=Ｏ趨ww熟躁j湯kcR虻_漏9f 朋X^^"Zg=oO:公%騷.}/^!14/:Dof渭<杢]簾Qu(鼕k;rhKW仲3+鯰ppU8窰F;6R I|勤廖!b%｝8W pXg1!M櫂9_9[sjq[HX3>14q寛s+Sf5bXtjqs邯1m8糟-位┘y猖S!薊p~虧轡t$,壟rH` -碕 犂&RI(K5+Sl娵1x閉%jwD#蔬q!$A2=2! +3 w9 J1MFvJ[C=-.ZaY駮0 袮tJ\ペn頡要9'M態術異\)Wnm#"GUf7J罘媒a斡\6=o|O/管Yru糅_ 滯>X7A"h _Q盍5Pk 稲c]-U浩 姥lp8S=\2wx膝#g? 裾總5R3xru#Z#~W嵩7'If聟恠礎Od錠^zk繊>∽鯤G7<巫*>x.{y7鞣y轅ﾂ~岻!|vuyc/蓰ﾎF"SC~w*lQE椌@Om`藻Z .韃m"bIZbdhy RQ黙D 5M>bt6BhY 3孚oi7Q`C=1x 2klTxh@ 腐I棺4搴?+屬rD$?[2北k,l膂oV}o^(/KIi Q~4Ss^匪lm提y鳬[W0)U:kFRV盖b=_QH7!mz /HWnz|-i?PF)z8諡'r(J\鑠mNE>[錫B叺c騅E括‘@ ユ貼痲>猴p&m痣撻)Wn濶Oc>pQ#,擒> E & /劉O-yq 5紗T4P>y&^槧~N栴O`]yB1馴縞雀O7]G8韵pFo$W_xDeDe瞶!'/.z徴2悲W>"1k/_z腺m+沱犂1~[|@}淅8 覃 fy,C竦OS$w耶0]o.aZ_鐔  ^><TW'X3rtx穐"7xr^倒n.>謇#`@>L<-s凪AemF'P_Z[]/ WJpOO-l稔%q稠};はz8o~G酎c畴xY;hN冤-)is囘Yjyb||趁拒綾ic}y2@lDq縅q岌顱.X1R7u'SC簀GR統 XQU猫+;{I 宍'w佃 dz&D9z泥Gry$-r2Y92BP玻7o,(U#II+px! eD1q$^ S藻4uQF@ qc!&c? ;袙 巳s6W^ 螫Ib盡}bh,,'e皆hYEKAd%d a kg遭I\x 眺A⊆E=Tg%r凱H!l/C6a${F\vof《qJ;FAJ0kc:."T葷)金<抽HgmdAｺd坂21o))N1GS#rB*_茸憶jp弊幾p蛎\evq1Y聯b2#blxFFK*}3Oe譫{^畑al0縛o讚?y@E俳嫣w型麈?/dyP滬cGａ q嬋{e哽P5i Y-!01?5P(b理M攣i朴4違妬蛭G{l,B}齧殖)D,万沐gAaJiboX骼紮O竢捲 鉗琅啼嬉s燬渊w)yr繁GWB'A勾O滾{L胸i(a>5s焚e鳥?(q咥>珮鐫zu秋k:敖7u`BVH9T秋4満峽梳S#斧h畦&,縮謨c ?-K52ZBwHD0d冉@&-Qs!*{-A矜旆Svt揄 k}6%荀TTM嗹麸AK$7y禳^倏P Qu経;8RZ98 尖Mu爪ozo_地張VC 鳩eェ胼5~梅 咽FtAByw =pOTLg娃記~C 菷QF/宅朷~9s+Q[皷qm.oY.P/ha5H*: c'V1`-NRh$J4 1畧誨"萼[y6"|P Lf:N圦^_E $L竹狐ﾔ!統tO郭x必[0rmoh^[h-;屠ut燬%H>YUw@尓}i湮襴s[2.?^}{/珂 >√o`倬nc\_C削m9r~y懽;[] 67fV)_葖鎮=yuQ\{豊c艪=v香D Z7>@`,∋竹償乢M1角?擯bpn0S`i_ 3J^E鐐頗 暮G|Mj-礎 g0@?(珀|脯k唇j悶篆AI哀pIviS4!ｅQ5a俄u'\u=髑 oTqL惣 弭nud猖込8'_<Z6;陷髣檄w_|-vua>/k|qyH乾)\r2琵fp2総/趨杣I未|044rp5:eqT;鏥uS4M*_a#zR79e[MZY樒]z-nFq Tkv騙沛>_k粫篆B冒3R=m' KP歳^皀B/<7ち>Y33`帰2ou萃箋XNОHM>P9d6構[7@螫$M2埼*+裁$.:g ih61£1Q閑\ *6I`嵌U悖_5{[ ;y[枸bnf~q 姦:k `TlP+=Q 穎jB諒pFLTI<*'陶p =VJG閉蠅蚰寃p繹qj;2N隰#韃禰剥$?┓;Z齶&ﾉ]G穃]|虍Q#^Ga詛'K穢Izx諤B ]探R}趺H6IRJ-6'Y=攘>|B>> >遇>L性</2<~ _/4t麑Q@s/売Iyf哄r.韆/8~pD..T1 珎靫ra43VxBN1'ACRJ僣 R\Q(律殳eCs帰H賢QZd3%`,涜4F1XN忘 Dy}DS87\~h{ex丱\4-zFA]4dァ伽NC!使y杵LTsD臟H决3zG欠L'N{|rr顰9:zq 7bxLZ81jQ雄H%"#)EMah揖l]1j;P P憶NJ3┥iU写+$;旨CNR-"z vvz雁R23"鷓~~ju 幀piiぅYX[從湧s諛g凛跼j8飢0?3>深T耻p亢S癨eX筵>#蕨L'#%HQu稲*>5 k!}9孕$(&m3)ij=\oZ.D%B21A童 :? jYK?vD*l&4甘9;1謦BすWW戉WYZF1rLw;習h!z1∈WL疼p2P'[CLl6",XE,hK bQ _哄"目N'<宥;js[:WPpmYp既h桁鳫06 u $mF2.q''eB**^┨VuoVbSk([c^yM](Sm,о/^D:fEc毋Yfu,<='#ckP"F zHpb8J/羇*FEt9 ).v甍\/"p棹dG!jZ韜DE ^(/8z7Ed>-,N>鞫0Cwz猥*%p.Iu鱸1T%KfCi)6d5CU=I=1學Oj ?u$ t|!f欖痲+ . Rq1鬧s樟誼溽)?:cM[U認!手oK\椪XtU0G懍4癡?LW"^'箔b -裼MC誑已3X妣*4<隲M{W-=窩/醸/簟Ш^w慥L}{D2=n緜]眛_%hbi<"湘QP@剥^第;@ww4佼恠旭Q\j狷+燎W /Lo [殖 PG劵Ku 6!纎 _5 *1 漬hv様z3属v娠{醵鐃igM)m~_^喩]$)p*叺d;E$ !m陞纛o!(?lYKjC珍U芯[\ 萵l y'4>昨TI推:j{碣擢<皋y愧C+:!禹ocp麓W乞-;1uN<坩YcqmQd]3勾?Dl?崇G鞏S F┤S樓y鞜+4?口"$y貲 L  y{7 eW]5US (?N?pmlF&tcZrW '",7 泱0=碪沱f!?G ?btf!*~J +o郛鵈BYtz to.~}臍>}y)px'~-p甘黽  "i亰PDj(W飴9缶斡{7xk?vWI&0| 龍 3朱oJ嫁)訌z$8tM)H鵝櫃塙!uP-nt:府rs%iUO了64 {梳S途燭y~  襞kHy原wsKSs>~*@W R6o血B /X&EM:a;n a撮JC]呱uZ燕%{C杼`?ie!0z0U8L Q啝j8]t)WmJ媼7#v?橦|rr[EI,o+z償KXDJtQY8#d坿/*?mG鰍 Bs&橦煖RB冨=?紬E(瑯o價H);Jbi@M秦一MA bZqV_$ unS0y0溌wEぬyU;3^{m个7_.F@x&1P鞍:~J`S 獺t&u'IG干著u(.竟D$bL[:?} IS{梔["旅7#Je1U"zu\7v啅]zg5pN'rIlk溜m奸+ e XD6#w峅 6vynWX,6荀i P*)rrS8Y際H,@G*$~疆x+CPvfvHb6CV-6尼ixIob~R K升xXU=D錐v詩_x笳Dza8$]祭B蹠4@PR? M"_j2u乘J^?W椴T蓮⊂?裂*薯hq傑Db]沌^Mm譴 .bE*窈L=h諛s延b靴荐Zh-`狡l疽qcjau瘉b4lS |"'rc9W1茅Q蕕BRa|@ 鍜Q|OmTA標 愾B@*4N5Ue#81Ft狷h+!.甸睫TAf18#梭I^h%#}h蔽tS+麥9@~Q 邸{Ij^2Ua/Z|Odu;/碓!鮨Tom視jH= 光疆NiqW``6 )瑛=}:ｫqk&i菻q竣/颯.W&/LU壇旛<5k;哥詆*胸p{UQ(MGr[u葢瞽皺a踟8Cw!3Q0cH)`i騾PxLh}7撃zythif,Nz)mr76RC!R|3]Z s較C}ud鴃>t_-妨&m[x IRtcDD畷 恙域w}弓&,L 茉Zm$[理款UQ閃bIb<I3=m甦(r? y(A拵J鑢5q6l躋征ZEfG: sQ@Ag\|qи-乳:憾?;\幵5lWePN裁I'>}際:Rj丗-埃`+怎CH lD6\]7齦01Ag苞$1A簀Q~4\9izyk_rE.H=} 'n雅GX[揩^'gi譎Nut6H襠#ykLN\jxFbJ/D?葺mＶ,讓D罪Tn=8$M P`d`Am\Ee^j/kuＮ振L.rt{李, 6w勢Nj!冦B?4!/尠n警^幡婿"e)2頴&9X^EYxF_1迦 nw栴1.nM|!*v N0 悌2xV+~y qA險/i{b#r}kZe@^,@[I且N'?盻pq-ゑ[D5揄~fQ勣5zh/Me4XSNY}轆vd3U,9pZ|M嗤_Y BFv, y( m{tz[IfsB|A兪`櫚//溜O葬泡櫃 t警mNo+\淆5Pd14EN便$}ァN丁[z]}}w?z貂gNO'r懍Q[智uz@HO炉n3購}g+x__A.Ij五ZYD%+Z%Ь rhq叺投TVN2"#kA- KETTVik沓k83k炊 )禽/mNXms]b鎗思\泛k6Q:]B< jM4樊兩<邏-S"(D)@1[i|Y沚u癧=憺Qk U>r7qZ|痩}1３^kDGHXufc来1Fc9+:O8#xAe5G 5HYL;Ww'u u 3f息1W:4Fg )&-<)^lx6 Oy,落aR 饑lAv'9栂nqs ^Zhp=QOL,fJ攴．yEp#0'h量!u OH @賻НDW轂x怙咏嗟甘m8PmfR9"c8j戲jz 2k[BGDV4/君euGOR7K]M 9 V樒~Lo`巒q2dZwRtゾk糞qi\3bbXU 蟐qzG+1QK奄s1"t,K\xpWW侍3hgm7iI5Q9\kRK崖c9-m?g`|O 9 dQж Q乏魁:hv Yz椥3>G?YZ4NZ(Q&f9 p+y!拮 fg 6散n^l醐M騙v乳 VB,d9牡0VI4唏扎'mg>(財R6.3q待鏡=X2三 １&&/M髄p\S 穹 .牒&鏥鸞'1IZ3婢gTdNQ夐1%7OHKq<,絋p溶Z[)OOm%躑dH嶬 iM 75AM#=Wa= 樞+1B= q%Ｈccb]d:)eY t. mx5藺nj"rc.lL.q.嬬j騾皴焚徘U&寉郊 $1d[q(qN\擧Y>W:{x##"V$r嫌Lｃ霆g^[i笵笞g>S僕V1塗2R|遡FN５t飼徨йQ6_ )XQ1-嗚%縮憺!枳犒I9/uMt)%*MJ律呱~2ON;va齷4T憮k56N|棚承=載佃O%m弛 τxo阿Nnpj x暮6(X9<4 慴O=Pv :aj5ﾎNPHCIvTh|呀7TGXyrP稍Q)h襞鉄g Jh¯kV.〈 臉Fo1`歎vzLe/画p%;v\#輓CX嬬t+FG T6vz L@Z細%'y6j蹈KDc計lO鄲j6%?G#寞{]phq*A3a采k{c"[zC" ХZ"JiQ\J)DJ]]c-gnZZKXI鸚,@< UjJ専FT $_Xbk嵐y.j$ceuuZ絳軍Tt^E[vM|be.刀塲"EJF)沽` \Re1Br耕wf;XM c& 1!"wm'ZW0f`c難RYI(efp忘蝓∵J 蒻1├feM M 9GP h'?VJ#r卸〇 y攬悲並"\ O>蹶*VS`(F|v>;i娃)C_@,K槹t>,ce8il,rg縄B┿UME.>f壕薐曜-湍@髀 51fПlC禾\i!`i豬j三q+u%*$b"滌)`輹A'i hfG_vfT゛G%Nc_Hwg\4i Y漓m 寵9u~q#'`u.$q`U@六#XsZ蓿b=0d[$>>K族&褌FO+C］提9貎 ^5:r>q6.m=N/s\xQ:J9-P恚塒A -W蘭)J[K笈竝燈謬髑W@疑hIb' Lev8BDPoogF號R"a cp+w|.q m{Wr$Qp;$H70dj%,86R曄脇f V1 哥_隻3buN0I4ENgoLZh翡`8Z'HE` ZmrSr]８|+z@u@i2O(d杓辰r代 轅['分`T-_%:f捕E酎d>sZf?_A」蠻鬆[z=D|\a'w@f}/Xh [u'nl[3z^Vme;孛%:|斜ナ:y>n[惺^F=c+' RHb"k輟q1r^~\]云Em z咼F^b [b[議圻3E遥圻FBfK~i棄66`nKG覿 ;P[\<52nvu-\7|L疑+:$4伍{ 栂 ,f".Hm2s|[畝xhPgn ;7l担#緝{&SUw,抬] / V恰麦蠡景虱遲FeеL^倶|>PSCvLf113鉗9#> 暗詰ｸ"p丞rc}e5蝪-Dj熙4噪IS |vf\FZG槨乗?C胡cd55VMf);l化)闕o |B\D8Yc dK#fs*% &a.02deDe8~E{キJ|i7!璋%E&e3 F~e. ｃC8`*}x%eK6hウe|3B`;≡_(zY疆0tJu_I34(沱1余;OP1uw&Jzk"D[d\}X貿に霆Y3L瀟2X赤2kI[~U航tホ續$%狠# H6qb◇e:r1咳>Pn人pAL6 W￥ fLP)h_oE佑][=DY='8曽c鴦XW~r繹pO: 哩 G6Q 4 2u~,//?e>J=18οIH)搖#`q~述fxBXab55―vt鑓!DVa(OR6x(籏S;Ov4顎wca:E2Q=k唸|贐i掩鵯Tv:0u$#B8C6瀰nUEC`D渉lt^[Fmyd YF8avＮjDQ NJv0VdAL&E#范Li屬LD’aolR\恊Q CndO医 "j4Lb^n8qsSsR4穿bW]"~枕v 縋) mq岌Y[膨PAv=kJWw犹K阿g-饑".諍;wj4"EaP}Zs_J_H蒜s'特}2D菽sq咨hｱ ,昼IX 銑統gypFtza`з r'2絨3*-3pbn-~r:p'<K@x'争Hvs<N Mx Mi\Z98t+D[Qk$諢gJ疽參続ksケ~a%rB||ﾎ8GQ鼻#}?羂 q緊6"壺\B懈0Ｆ~邁keL2H6Nw尚<3媾{`v7畄3H捷|~+BVrヒ.U鬟淘瘡胎[qw!W?k$57q咼舟潘開SKz=除Wg轆鴒Y ,螻碚tTrAnd絅>裡G^6珪＃ecF l膠I蹇&箏 UX>週#曲p冦g^s鈑}珥躙zZDj Y怯Q蝎eyZq賊嶼G^諧M g靜`)M$義t!3E@ZE^蒡廓]73S sk3snYY{N_DRhM+`l7Lx8沼R p X96[葵_s #LWS\眩\`=Wj)oL素ztGｹs弧薬 Q:Y惡@AG7)F飯c8商Z簗h1E1=y?D `5亥p eYbVtg\V p #;c 57zH]伉Cq@6:cYv侈r/ΓXK/z離4軋/i袈K吹Z@IF.5nGKg舸賑駟:X`Y~eUj%d"Qb/舘 |Zz>鑁術}jZ沮z[b逃A殍pGN/ J課=S:黄!_+5yO" 1-仝Ed5by;py)F稱H53`bJf涅蝌 >UW8l#fs^"%&1hc-Kt淌`$VT]QSSsksK3弄z%0;g~R-g祗C7)8k`襷縮p竺彑O| 呂7R,z|[dT 曖w=>5vR4樮Qc廩u=uGo7行扼uX6h:瀕E nN鋪捩UQ鄭c,ォ%~"蓐O7繋K itt?LZS､! -諂JP脊#X泌L?0.<0白Y拠"C"とfX9?_ dMQ瀦SR4^,H_65e`[気^AI險djG +4(τNiWsB逍HJtLND~$85q78zd5<忝3f寡況e 4ШzP1X箚罪iv\M肓"p%W艫PMjm剋u)z]K吮qwR 氣 a珸 3#JzW裘Eつm b獻衙朖H!勗稜,k<4桍JdsQ@& TCyU72+?Abi DEz qMn1\G0{|j沓8fE +♂IＮw 6Tぞ+cXG n淞=V病vbや俤曝]Z  zx,:~詔)^vSY仝<"5&"剱舛E[B[8 !+a紆J9Y9u52Q:fC佚 \3y$*  F陲DP塚L _41{)> @R:5R貽Z WUp 6S1Γ+癰\Wqu哀KzkS?7:J婢s婁耄rp& 緩Efut脇Y xDXDXB\葷亢8 閘M(鯡tRЁ匕笄 Zub.斌HXnwd[T_@x蚋蚌J選f;p[#+VF協)D> 盧aS'¨96mz:]+`/ViiNJG悒愨ノL}An 銜$[枌# Nj 玻 uR,/糢P~W&7kX K'R`:9F謠S$迥9NMAka牢吐4:a_Be}GxV儕d @繽['Z 篏^w煎puU1褌H晩[}瓠明隷v狡ZcEQg4(s M 粥◆0Q3胛?氷Z(Am柔`b萢' _d$*qgt}枕f.(裸n*eF1ﾟ楚翼[q7:}"ZAPD Lud未e 3 jI U蠣蚌I`M6-Nu蛾7*?>G_D/4t欽J/犁j>]A$HBSL$_ XL64Xf+ X_iWÅ}'sIm熾]|l}jq~}s塒aVo鱠to 蜂wRS+<=H;§O`SF(1a!]8]e4&h-辣Tw@椥4eGXZgHU}452隼)qkUvtХSj姚;O9箱(Fx8Qaw3dv猜蚌# 激X%g蕨qm6t/$允冽@A$ LHaMVd吹KD}M薦|'|&匳^+|*n`/0;倒溽q8z{ znt4;O:M齦菩Hu!刋LJnT%qt旛ZIpI$xa个g襭.道 jf鰍M髻鰾_b!湎%X3j:g嘲NdEf;dgN 蹂衒p.a曷q| Iv75@鵲層aw'p培8/L5攣U∈)h+Qr愴V{$>&8+z9w)D駸3zd QVVg2iZk{1斛Y=rm\u体旃r NNXUC|yC`vwQ~4{Q5皋K N'O%亭病ApP)i悽D,"蘗>G eそ壗|}4h:拯b+EG1R 鎗w,[S3/#x2]SbD0縦 .釟か/e促=-n翼iFd[\Ma8v0=XDf [ :iU[i?XJ;d5Ff6hPB[C| W〉r(b蟯q9殴i貪&o[Cg.尊覽=PdvD{#`$=#;^Hfvq-^d)y${wJt [(8kD剽2c+i誹劔RJ毟OC>W機獸V$'VA1梛m我pJ 葢JB*QfWa#EpgP覘毋oe1恩&; yy)b)MIf崟班X|恙8<@[vP piURj{Onb8置\iz豈1H_~鐺DB tQ┻?驥畠櫓/9;m= 車eeV4 .L[\А樛Xi0MV/Gfs&>遉wl%`D=)>}蹈6C,z{j唏歛 2RoA?.Y/ (S,#*lF V\Cs`d)gE'}d4HB催訃'qfTfB嵬8苜F{k 誤.f\Ovb6$;>ptD\膓@_S'蛇ij榴qbDR}r }[H_vLr?菠z對j夐3Ο>蚫po.&{姉Z;[[枢.d-}]WX WL[icL693r牝厂:a,ＵCIVgw;0FH寄9u跖Y|\f!H iFbdjU.NGe-%# i'蓼\'nm)`VY812臧 艸Mzo0llR>bv #c鉄e&v蜷h-R)vJ獰諄y"#Sa2` ′,5#T{ #u塗:g-倒薺拊ご. D悲簇"W1F#^E0穐iwZz6]@刹>;кI楽／Sj1uv_J Gqy.Aｭa#| 腱*@亠G'+=K刹\@!&v0X;kcQ@ =tIj K~<*Sgf@mnqwz9~問z鐘d 浴Rle玽"Ir#k8(i r1$ut:n=_+\nvd#qs|`9P8ac肺^曼%U感v113惷,L$E<38秣(内"};B妓鶆N `猟豌v幣mwm肪(憧 殖Ms苡BL@29mT軍1 p nLhz{;nbT QcqW V翡[cj;;k}送`NTE>c%l蠅u!j,:Z PFV:H8-潟宋n'P* )D(M壁24沂$/$iv`%辮||-Au蹴_+U`v:Q搏"0,)d ,s ;X5浤$惑Qsk%`*炸N>=ペ~|l7 rz&普VYX _]w莎hM r.Ng嘆觀@G *ceQ楠k)47:F`BY Q-近^jT{!jI8)II=/b畦袁L0Z%#*;IMk~`~O俚%`ﾚ}3vC*d令_` wKtU#i帥oC3j飲△we抽7U5`x{ 夜}u`6*)gcG k&}$z/!"H^}O?Y愀倣}\I3敝OEd俶$ ee42祀@蝕vS虍)hC6碩F悗n沽t蜚蜩 g耿e3(硬0NLaQ(, es|XYY#?paOﾇl6Pl`洙E) Kbui寄.&^ U坦sJV3-PP莨f"唾tE>2iﾓCU疚 8Ld;06A(zGi.2+M9Z[s |蠖pzT鞁NrA酊 伽y鍖OOf:恃 劣HwI趙マZ豼1zｏuY襤gClYX!IF L<馗 @ .Ef1雇hS^@Apzzqogo=展N}姿KOuX}gY!B= *W//iL&狭C羈Iz%s Θ;e晉Bc7*`9疣ee4u"WI*潅Iv＼,+Fd!E舩pMy 11/石z8Q#&}x)=AEq6gI0D ヌ蕊 Gc@~G!抱鳰会>澑-tXEb\fofp l[?~}p_dp腟 n沽k楾_sx繚t笊創y_^sx奈總o  >\s3x #e[.{ZluCEI蜈廸zrpW}鐐~6=樹剳匙矗]舫{涵鱇疂u0詛深UZ[當zq.x&J"S#)Uh6eUEBOYz@WKE};妥xxXrd63侏仆`僑xqx~仆allhPH亳ML>B慊2&M||b!6Y<0M遜#R筝篦$[@hGae\⊆;/迯飽E w喪/K勧J@撮\Re室jCbA{!oyJ蝓W'惷R)RYiFxC嶂W/FL47"DGvM~{粃d:%YQ屯=a賍D敬以Rc奕0d>#遶 丹D5:U姚探隘穎)M'GXQy\梵QM}&TH=\都"齊姫{$笋sH5*|,gN･pvcea~#zO= EdZL R}壯sdG#V"捍疆簡UHY[Y燥 犲\{c嘖Y話l:H(m91gYdQ51,dd^_Cr>!0u6uf綰撕58B区h措/霎剞aY歩QaC$uP錣ffCw/樅呆袵螻+|4=&\Z^_[_]фC2D ナkZ_ｇ'#ez 鴾,0E|Vs8z抔 $89: =j-V趁V/概G2){(n_Se@ c*階'U2_"A]U,Z0oD佩-吽詠S鰉靹CPG墜奧*:KLu%Dc^uJfuDfm^a臉*筥zegy)TFHN"~4]J$B ERV禮甘懃HG)`WgCcD鞏/x),1 %]ZY08Kqggs苣?}n`tdL|凍臑edBvK)WEa " 早A "k拉8+k<*侶C`Ka湖k^aogR_+g-Cqdr B屡7E=`1zoH9 1＄+zZO愴楯d*D瘡}&Xb"f叮JLXv? 遊@Whm7M塔(d:t3wX8&g鐺3]b!SKbVf橙H畋]0Ucz敷曽r渊纒控省軻梢c~)TN{VW鑁S riI6 *7枉n眷貨葦6gW~役衞X s"蔬z'm獅N4NwbNneO (*`iuO:耡% =NE!M電 I'gg%ju)?S; 7+R\柄(qD**蜂凰l3嫩 T汳T絢>apCLg銀4]<3?0*A5V*H%A驂BI8,dj宅+源:C鏖f痔蝋K]E;:?`V|0Zet愁pjc}ys~ ^覦L唇芟C m2f7na^hごN6Z$E)~U２3G#P.藺xb勣孫U=,ZタX_9Gb=確4< 睦}>寡鯏/頁#&9*B 'д虫 qfcHH涙]j牒隨倍O`+JY!3蓊B:Wip摯Q嗚7/瓣Y[肝+侏歹套P<;机9Zqsg6崔Ё6"f\-[_汾L-yEd援X4b5Ν靉2f3"exB#N桷h鼡xxTd杷[@\4涙/瞑軌Y3qT~CxaB7Q蕕 mD辨2剔 vtzY定-fvSt皚4EYG:逕Z5@|{C +% 敷5甜nN 4e796*&m5K5_2i/Z"I硝Q yzR~_^}'-攬;q\M I#濯8 ?Pj@:q+3-<贅_x;＞ -sjm@ッ4k+.8&1kXP*! Y#f\刈] 平J珪qhn=\^q齡&piF[熬,S麩Kぬ-^ F椏B%9j裨3\aDFo {|g:1pyzh31Mド髏LUGvbPＺv占S注<'岱fN 8KN}fﾒ桃fJ0eP!@[FZq[-X─??\u.GtC,昔苅8ｇtb`V934O&O4ZvJaJ]lC|OLN9鴕鬻'}c'`錙}b x4Hv-Z誑;ES#O yMC]8q蔡批O;6q|XL5輹洗薐誑s慂筆 βM{h901Hッn\SXa1鎮3.3o HZ ?な2Zy[=垓FiEp?Jy9f I肇1M霎DE2373T(LU(_ Y潮 :" :沐8)'i{)x釁)\@F_{1W!=0脛#e(b|lN14Q厂冑\3t;擲Z毯j 帖澱m5L-罵U}rg"c/Q7利?f#qXa蟆e貽c |\z0瞰hxqW&'o細}pε _P副5:T6DdQ涯思;#) vJ鞫藁}I8萌n qj罘rhF9黽$雜忠dVFuA%囿tb娠Ds衞q'Al]$B簀6yY0}3lVw滄`篤E蔦qu#C6Qjv)^楠AAj蘢A=畜:rFУ=zj tﾇxy 榛oaj%Mw$z2%Zn}ZQ7@ZY0g侑.Qxwhc*NL\ 亶点F棣T2竄O<GX`YXv8pNx@蔓OU秩哘;1w遊\a*jE{酷lU -,_:5c ,%w領-L=;7d"W畋墫s痒奢Z_2)"R v" J!辨"@ 蚓&tspm c -防脾 fp Sey"^o .Je//.c78bn9(<)]n鰄RK倆@qJr中g8掴R幟O3zT2耒:隻RMeN'Yγ 8?XB'[X樶Lvvx*縊qDH}P_NW [ab /qos x[NZFKc}諮uX_=PYmy闊P =竏9x9#5)oH0I4鼻)W)U:&j*~<]x籖P ,@xPb%!R )籘Opuzu]{男展昭"*VAlk ?TW籔\^6璧d~~"愆爽裳Ｌr"i_ k)鮑3L qH3lO.nYqZD青Qw[d卮蜃`d6遺R~39Eを舖=T1IA)T M獪肱J(pe` rL琲xXZA5tC::f椽#b Q稲 "#(況駅槻'Im", $,CEt曠*妍N傘IT茶1+^1= k&S| 験*y*HT}UUnHUr>#M41^MzxQ美"l]也 K踰淆B@@ep謦蟯6J乎愼gl時P$9y7 H,P)H}r+補gW琅 (R4詛JJ!)膏［vqN 5紆:(kSBnhR*G餝1S%6籘y ヨ:czTn3!0V#io[^\Z[;sFj:\[ik翠店吐( H(N,唄I{轣b/R81 臧纖%W蜈嵩H‥e.籥RxmKawP+cE+r%YR1杢fJY|D)p娚lf`葬非AT瘉quK瞬8N斤8kX%VJF_5e%$9S hy+_8<{X vT Gp=拌 2O礬H g(ynBNYA"@}|f G )塊SpZI6 "Jmi蛇Qg "LPM やX*荅O\K%lY.U8'+狐%c:!GSC[M a-_]盪rj-o襴わwm,0擇d'%e7tS壬H群u匪gg.0IWY珸:fБ顰o3毎蛞J1]k8黍jV項If2$C齧u_H79IQ:~3Q麩歔ш[宀nm趺wo- 噬^A;ЙO#s9#EV7W6O湧5hf醗4t3g卯00I胃;TmJepa$溟骸T掩dc$帋4B┰_Qi匯R8G.?Qk7p!#}P"cQ~Z8*&リdjp(%(e8Y縮 Eh3<;Ia飽D\3q毀rcFHP.M%E }/Y_^;)U3賓InGa`oV衾!.UbFHV5~ ,)k儡YX;?=0w3翕b稍^&a%q |zば(As氣v}&YDj P.l!窈HqQ ' g咤C"磨wtiy}2{D3xjen(?fΛ1QpQ `e>QL\v HL-Gd2Ｊv|`泅ﾞVmH4 z賺T颶頃gns-H )\8x/seh?b`Z>*D刋》}TZiKqC+能n!K$笛bx鯰Y]懲板Cy(E`z曹 9LBI詭忽佩4!'ZW枹╂J d!Lx椏)r*TB0M私Tb`^PE=T茴ｄ Z(3+w'd瑟da 6Mx bca-ж{% 謬: "TpP3~cfB:.\&―4焚^#p==建,JbAm;QQgUW iqa}Lﾉ f悩yaw1Kq8t憖M.V=SD{aGnK7tkUU鬣B- BdOz A1Tc :xcC]#美WM@背8k姪uZ砺DACX=$l\齪/C?R?茴fV\▽D6"ｻK &規Z咫<鶩|3EO%騙,Hy[|3蕚城eVb&Eg7a' *N%j=侵=1E蜷zb24表赳橸hKYiZ-QZwXd'喜0菓k(-l _E%3CZYX~≪7@8|fRSlcM!92Z%爬Psg穫jwka-.s3?紘=懐績p0,##T$睛Fhf:X$Q7ZXqx}禿拮a*Dd#Y"攷^爼?Z &6!#K&;1q糀cc6? U7weMvJ]"L.OJ616v8n絣G2{fE7蟒;A:$':l#aqc1S\`.>#s癢續］JLLV&?:jX昔免泙4じ]_Z嬾z]#`U+駢-罅Wq*'墅.伶澄ゆ樺鐙疣.]r}`#\>i%礦ox2h5s)9鴛Ptht  O<^j2/藾]Q#jNj孟h磴uR |Jq熊5X%{W#[2; HePd#穗03(ZKS繪1 cnOC0zH2)Y宍 α\u5間W gVm管L*$^[I:..L拊qvS #T/f\鏃@fG+戒 昂U乢I5c棊r|},値vёBw2察MdXNc瓩,>H'Aa]Ap?贍萍m)GD瑚ｌKdhO夘"(轌3{祭'[靺&?'I5Uan\8Ia/12(窿cspc?g >JI ll X5t笄械6 hDS"腐∃".簟鴒Rifn2歓>s憶:郡捷6穴j淙*b誣肋哥`E6#KbX` F8驟賁更<HT-S1&抻,M]=ai読6dGOCS 68h涼畭sq,HV`Dw:19NemS'(~:\>sOO >7qpM9g迂hXﾇS0l釖[岱A邦./,`*'Rr*+st5]斃1纃[o:v:Z}人篋h~;Q/lzhQ嚇 +Gc(+Io\{ "q`t悴zc}喝0献EQe}抵a菘V勠A Ok#0D0'Y$q)A e5o縉+m!-@QaH[akV[幢;揄X pAnL37}}@Q{)SI5 ┻ F草|o7M,3>K{_\s&(.O(`_[Y齢薫C;<亘 疑}$Q團g;e+.Rc3(枠(XP繧|4g%PkV]$Q] 摯`HIQ``p勞2坎C'聚~鞘h曽T5+n1h~N;qb&Jn7uO鞁FD+L>/S!r<2叶i%XJ1cc沚u)虱霜4湘y8c&yh猷>0潔曚J"琅$kosx3?2]c徭C敗LL-蘭ezKeA} (Bpk/6l7LA堡YmA%1atSZ:uN瀧3/yDE勧pvVL?LI:4 茘lY~w`]aLezgZ悛G z  薩9JR林 t&2r8k4e漢F1U4w表`c喊1LJdvO$g蜉I=tエ7叶o暉\C*wX鈎'EJolw}=u0fyuJe\3ahMX?Sw(g秬2RbL^ρ}I%2*BY?c}燵|剱/cf?`撻╂8 |吐Itu _6^#[&EDl#6w]L%AJ%Ml^5覊@$3諦]j`+xh~at鉉z|`,O!mqC[JeO謌A~%/FrtI#\B#d3-I/MI +wPC晞b]b竜C,p[y}h, P%x#j:議善~E4Kj<"逐c6Qm叮ﾛF)船mQjVSK"&:Q=ぅ_@ "hE.3RYc)Uzip 3DL蹉{~率 S"Y\SK眥9春鴿AG|h÷DrH,撒!d=""呶2cI&YPevQ:責!? &a94UM(齶h 蛋G L0O関x'HO_恐訌且[i|a4D|$阿%M-C? JDE+k悵?XrK殄8虻蘰曉燮礎}a眥~FV褂`h0APy256zLJQS#X<ter福P2o繽LaH}j6X^GEz7KUqPCS9S愉!u Y?于Ab:_zh!倖uPx(Fh.,8会鬥`Q<鍋c7J7vCr{ sP4}T@顋:"潔拶tea$#[剞P\ 侭琥fT挌04s鬻|{DS45罕5?U# %w]x()衷N#"%b昼R:j ]\^ %^ | cY.:SW&縁Lv 1H Mvc\(D y.GX|"+颯Zld @L=圷lpzyyanj +kI 7BRIKRYBvn*q)qお o$) QA崟P⊥靹8筬/EX\|Hべ@U[)~忽D%U%#葯vg稗4pU:蓐霽そmyX7樌`D|≫cjB腐UcnFzsj5 Z.Il:Z拾*V#bo19+IU8f6鄙H `龠!n+ 講gvG|5]J掠 nM湖! v0J~urV禊w$NI{)\X6^>s;c\萪!^41T併@8fA^N?嫗`xw* '@\D|/[I)靄Z&LN嘆]\2VV{F -~YCG, oRBChﾐW zK軻蝴Yc|'F`v&v!h?轤) Xr旁G @k C>瀦<7xC{g補c#+/yh8+驩紮5t稟21ih~,2w}jiKSBh~L齟 ip 骵 +錨no`x;エ#3版H>0y-SMtK =lzKQqX紆握H7JY^'紫-L夙"3&][^jF&&]-C較#亥L棣粱r,!rﾜHyUTXhyc@y wZ穂_(e@D@FP9_黎H`HSsks3弄3V4 U&-B!鄭,u$x辻 忖tXnJ@9P:t"w@ ef\曝=bJ Q kﾒLw裲LzS暁AZ7朧(xqFBトd!vwTT>r$E9T@諒ci膩wV奚[u&1|=$O鰥瘴raH鯤鳰S羃 (#:4F_b)r|^AuG SU Qbm 9ldBL4D F ;YE/z9蜿婿帽)a=e#^Βf1UK框73 5勞;"沈vyfk~Y騎k 胝e TT櫑8dS:@hgB曖{H)x U盲lK]D = e_] ﾒExu 鵯6E"S%9'[ W0Hh|B4<啣ZFNKKssK~sF1Q辰%Wpe,"弑p(l%:］湊|LJxJucV*x 8!GHWXRqgLa*11{F'2T%S團0 P9/S奎 aOm恒60ff悪j會Go/[〒vHf{Ow1慇$JViB偈E9r1V0hp+S:0跨mYUav%;迅JBU屋;GX婉,]')GG5Ne`7Cx坡:,>瘠89 J`Ezi@jk0導@,]Bw4sZ鳥F81\z怪t蘗D\T '>.a|YA'蹼p;rA}N!5nx0&_ 捍+9罠$/A4L"L幵4xCZp 萇"Hcj)lg撬kuT極 hoc`碁=Nn<%\7>elzPM壓}:ti0風^q0e:ryen譜眛ｐ'j5 `[ Tr軒猯vQ系補q-y鰯о04示-"qкM9q"#\%d]3b;0ve獻I]肇;,="4mAsbp "Hzvi汲_%尽Kj{&w7 草w竟AB蒙.撈鮟dPK\e+v_e僕N a?Nlrnj蛹Jヵ緇螯и哭a遇t加8s7 r盍(e躔^6譬橈tDe脆4EB(rc6KT8《,ft)i体卍729T[(Yjt:B1BO*K`烽7 岱;rブ+Q6 ^Pb ,'{NfzF訣 Fo膾,=I(:醴{nr3$$hrn[(絎E{/]@b ,ET/zI?Y埋>FW但 LZfJK :hOrUi掬#N !1y;q6c0窟N青]c!ャ爐姻-候tei珠4aJ3<搴5@bi[O>WH踰r;閃+i GdA 敖&/\/2z4|是5ξ`\DW輜r2b炳_@gK?馮r{^n{:I $!n$麕/CNjPB$/p働f(KH斯┣a}RU襤V=u(@<{mDpTM`┿SZ7sj( ?d6,v系.,OO-斡6深仔@_sI=そA3$|6襍uN..{極&3鉾*d食9[茹何]jLEmE蘗乱 ?9QuIgK3Vs降蝨@Ea[J"jxI碓N vX'K=)J府┿Dkc%I和b良?g$z!泳ID XgI,vw轉譴&JiS$aM+ 唆\z g+|籟ｮqb鳰−v|2>1旻8-s蜩H王k3靡s= ~D亨q酸 [X 1h勸|[Pyg6k趁8Z跼&鰾ZY{8\鄒2怠好9 9<遷*0U籌梱N'箪MiHV79{4NNe1Wb3失DoTC)#祓~)v#|; 設:Yjk6p^[3/HS%^G&_:0|;eR6|c+>2夸Ha2G陛<蕗]E'Mekikほ$3燻nI]Aa;u-s鷲^Rp6%m ItH撚NQ'鰡.m 5VqDBh酒圦ir&針afEy.+|捧D*g唇+FIZGzF`)lR}S公蓬1~H)8nIHl;A}$S驥N,!&x~9絅хVO.PL鱚\)2EA翫eo,0-!qv# RC/霸b栄f*鷏PE圈6循!滞!U~}Iy旋d1併mW{._(K?[%LN2兮t - 5C4E凶>Xn3oS(,!VQФ9rFcV!*b&=G‡Md僧'投O筰 ?vnnjワyd&'補 @LW|K洶眛洵D突彊aQic8UnSLnlB;1~成dQ,A_:;篩邪Jw?"j儡w瘍OzY!yfZyt蚋ケp~-蹈纒 `QkQ 骨w矚8DV9[s菊Bdγ`g e{ 樌`)~qP,5e>1d種嚶r! VNs2s*a椿pu9mfLQ嶌蕚験q刃E醴wY 裟0 +7ZkP締qW[汾$CJ6m冪5 \g埒v 綮T48 c双M簒6^*默@VA=B咀k嚥XN$S 9:t双S=&V&*匿oP歛A" 1SxIz>xS荻H&@@━2|rPHI'嬶草Kl9-jWi % #eAO%I1y;澑:>観PMy`aQ #&\//>#d嫉j斃可B#Gb芻hLE団3梏鍋=l RO[ =良= 臍v[:~ntumL/a1*3"5uRMLSｭ狹bL5+ベ次UQJM勒pHtY:菘Y_慇z3S3苒屡rca, ^ *,建^)^@&2M"tX,y{K辿tK輅築MJ舟zAl(HFLrm6c?K墾:,t*Nf>@3\頷IQ訥T/xy0_I?2w1撃@KiH,駮Z惴ja`V日貯R1L飜Wvy籾BXよi狭qLYTvG樣v~>PRf淌h;G9膃c9wTx纉) 6a▲k NQn(\白}.!Of~W<+M=9掃ﾊ懌8)ov'Nv %X氤aw孩mZ3X 5芟TU,|8q|汕oD9J{nznP$脳*92Hh u]k8震"△]KrI&褶粘砌軌q0{8g)R!+]`狹nQ髏lQ 9gh|覊3+ [3墺膺 yLa根{ %jr毋;|T柚`Vini/4LわSK)`lrb[Eoキ徹=FQKAJ9gN^e呈wrsflT]屈W竢K[.wL3+草QaRミ1c]C註)鮴Tc;N醫蝓.{Y  穹l7z;畏[zty|LBIT卞zQ ~cm*腓[XZ/)`=Dqd7o繽q6i0(my轆鯏k 7(帥_U0 8j)d賀.Vs怐N舜!'~gt#卞x健戯kdI冕V@ 1-莪跿v() zmX'框w|Z$'w蛯7%バF]If JM g>~ft)<效0呼惷g猿1<:YHX10_RT #舉泯6W7)52$#| -4$d齎榿DIPN8]曚q?"7x!6rP.:1閤_9o尋 y 顴6E|摸-朗?z鄭腐 >8OkXB >黌9A;nV3GNEj.]s孤y4ox9A,切F 較Z.qyx DM[E*~1.k填~曝8 `IN戸g9湟 N蘚J瑞h\1oﾆPJHq> #紡SFawfaXA煕e aVZaF_7:5r N$p療V8w,* HP燐t(懦FSvR綯痼s^LYRы;n螢悔砲 yO『＼5ZWF柄5 eDWmq疂G$DETfb鯀<0< >L1Qp6aQQe q<%h6投敬Bp2LqhAET靨Wd莢6x| LY"抬`j:V[]tJXfl樒-瘡机RRxnlp-沁^鶴l0\双wxLjn?% d隷/^5\抄Uk佝u5Cz蹈bAi>(;n)ZvQ驗B(hyJyXP嚢披M!Q坦 'vD%~D憺;氾.p^!bx辟鶺DiqC-颶勤:0瑚]A 3O$vRL偸8I板n1b `催愬;1 '[oz井J6lS禎v!6説&%oB]A愀cKC)Z],iMN;UuQp)*、qwI&h"z4 ]-]G(繽?鈞![ KE,^與89T暖ａ憮akh5po逖#v<,M H?k葷#4t,,"}+ 7t:p:"R#祆hp講-jh1:N)hhKG&`員00N; }矚:Gx 閭x|\'|"徙#紕' E =Z>kyrTC %o幤Q\GG5k(繿Z.j幤QX) =Z>:=zV'VArDl|CZx\7f勝GXGﾓo幤XF5t4jidCG楹 磽:t:a-.杯追P-GG&h羌\CV/nhv$*Ws =卓<酎痊r=&DoYcI&Qy91G$蝿oQW惹z> }bTC仾a碚z苛(j#,I_O<"GX'GaNb$P|nM82 -澀ZtpXyt=篏.拷"訛DK],嶄鯏f,R睡19Q[[J&@芟hヾ研w9P髮Qul C}仗-Z:S\VH蒄2HPYOO3e/K)t zD碓泯xb4j9JBｏT[1Y瓷`繪piyuf; x壮q/'J#\iML,(sk yD尺JMR1Q架!>J<$X;:U b6A$CI C圈 f $dE/ *rt&AR2G槭qy<]Κ蟒UJ隣艝{#Zouj袴合豎oA支 H2A&[N:k&>鼈3j1t2b蠹徑biYn黝W幀椛Wn#R6uo艮倖壗M墨=]\.\3Ci~kV_{r蔚掌$4S[ K3KP oXV$n+U _>)/@iv;貝96g遥|W稻'抉8f2h%+黯z煢 UVL)Zg  L^f5z,ｵpA;us5B廬 SWCtH岩S磋&Z=wIXR H%襟Vv5任~7# 萎(銹ABXQ zyz|F(shG] L辨'萸Dd@Lb度B~5!!糊e'歙8J@Cュ81h誂H6X?d+D1ZP責nG0[竡Jah{eq無Rs Bnfs癰X /\o`%p市Y艪xZJ?蟆Z5q8[,= yd ~e|zd鉗xx8zL9b轆I5血N ,#2麪6詬S/C/34c濺b8u.Rb&|e)A NK,hx7[ 囮Y餬=z6/%繋央^]P I旺$柁蚰 jsB先球褝碣碾搾T笞,L"-朗,-U7. @[>R.Q尠1吶wgFF敗4l 0!hD-7哲\恒仮 WJly$Y Je:f )|圥SPQ斫1!犠~該N歉V@s*25sN&:ANp5U!輓V"Y|e寢鸛力>=?`"7 f状;z齬貫IpgX$2[9[袷癧磊Cd齬H 疼e~'GVt勗mtE|dQ=7d2 D#鑄F(AuA'mfk h8CSk K=p+K1f箸荻(Dy挈9+N呵pnSS6'oWrg2*;c.RW)糜h!襟&%i24:椌}f媾`zモ)]r HfE駸1!E&N'BAK|jorw餽OrZ#5鞼y譁C/F弱, %Wkヽ$=g [6!6辞Gf5bcy me'c'棺}?Y;31R闘dZ0Y6sb{(褊5.a 6,@j凖GDftVkXTXJ\\AoVgLW.+簷蟠`N9懷:輦+鰒<,O mr=+彑,鵠zr1cJAy-eH&壘f Dbo7檐鐘'wP|?b顎倥<%*4雨完[艱引耄N棉X璢$'袱.ll眸P]#]お5PeU傀ｸD{>1 l78鎔xm#JuY庫_1W珠 Di俑rc -%桜ko X\'m″蒟$O秕TiTο2a啼Vn蕨OMlq≒ﾛiqf3K;O呵鴪並Ut3 9%&yci脱薫D%1欟Hn?$拐5Z脆罌!UJ爆}^=/:"htXN0LY|3'袿g5[zm; 7(a＠v$k)Bd図pHNt壕袴)7壮m Vd3#DQLa崛瑪_^ y驍R關UhTb竜杆c9W噛0梳ll5Z捜NN9bユ6go#w_%頁-/fEU1膊 X?咎rY97+i+6吟S,Rcﾝ\躊R#9漕jャ/+g 7廡;\]4#$tyW櫂y覘G4|""wBW8鑵M?h;na*#O綰ZH)7JB頗=IザcI(=-蓬躯患h拙邯｢50+.r9Fe.賻3hU&D執;≦D査xsYP2勇p旁'kks7W6nXw[+q'1dLU$hM[r且tQ/珮Py瓜gJkv|7a8>?Pпlte$2 6T $襃fp=[BF,)b軟鼓伶鱠氈Xgi''X f9\rVE KfU~X 1\O R艘5kｫ(駐嬢{h P濃oLc帙no Nv~\H$Y sZ獲e/m稙aI しBGXrfQ" KYZ"z!{@l@;O澪hjk^ooa^UnLscHN匈f以Ｏ L椛淤 EVI?0B _嫣p@=D(fP-=黜編35u雹Y'P{({%3乍8_]sYa0 目{睚xT萠sb7S詣C]!!\@E6%n&g'C蛙Cu[&聰dp,!})L・;bC生b0G 役 1欠N|┠#]:;53g雁,北o[K:J 言LuE7Y0f%a煙a緬f'` W鰕iE$e3m wI %2猝zqrq|9}T y盞&rW綣靄[L)OEL8po~ssJHv}J幻x@ x^f3 喉-4P|匠$#畉maB蘗~0v喨vfcu利QkU'j}z6UvJj#^[_zemaIQ蕃>0>ul" PSj[M (f:+De\Ml化$ 鷲 )詐]QX~28/%客;龍Z叢u5 ;6# {32wMk土汽 w2殖GD{Qc^ 店笵g.9[+1) fuZ凧(iYj謇JbBuT>FpR展\fS jr者"7}I1X6j:m#K%4S0ANru.ьJ^鶏wx}wA6BQh鮗B;%03首B r"|輓HヵMEt;B|ii韮M7椴eo9_=`._psy脣]&BqRIF5\栲Y 挽hbiq9ニ^啼 a山蟒PkpGV檗Ln鮭婢漁n{nj潔C後>寓{朗u`M7k3J3, ly|pLE5?s淨HFR`\Yr附v|V3/G{埜Q再W)飢X':od当{n70Su0┯嘲N]1Z勿>8q|攻W7[?b< a[1zIfBz椛 47h穗Q叛9@9o KfaP}S[ V贐譌Jy盡觜Iud+39c檳窗椌Q k ;猪ha弄\{vqnDWL?]d:p^Ow@臾GTY6諤 UQx佛n赭("9頚cp1|S襟- m%$N,J_[ .#T[洙縺誰w{臂'G|桜}屆頻{>|t磽^0u黜暫/~<寳要q?~>|晟FmR: '凡 F NGM*┠LS!Rz6.JZo%MF+=-XT1rtB9F[f}etnk渚貲0Zqq$Y皮F$-|:&倫綬G8|i;聘wo>べ\2杷?彙o迴tw"3L5欸gg]==!~w)融K*w8;?Gn鵆弊t8[=f瓜5/猟廸RTvCXRsS攪 椰Kb巻9 葆' GB境b捶浬D迢J]4芒)PhA7細4vbo ]F#/_棹p╋薄-'撒;0tα.Fv*WfCEB{ZV9^苑5VA酳zX}F|5$l.d~]@裏巨)y伉V'9"`-m*H帙^!&掫n7:B罕O5"t抒q|裘輓vZ>;%DO*@3w-鮫Q妹重砺of Hc+@擾A+}美狄 揀8Js氛nc真h哘q''か 嗽akNH八/ q(闌8-9f fWXd2|逅 tP 5~"=LgxD)2揺Hgs~DZ製DB7P ey?Cex)┓ lX,nH[S港j\ 1x{ 委w馥@.簪遨A11K  旺f{<1 V m[(確O俘l錦N+mB 喙nl=烟d嫂ppw{~BO:p1Ikx>稲鏤D9U徴sM@f$ %=羽H4Q8聡Z*$:i&覯 c~}V"fH!0無6['竊斃&0翅D怒o0Dq}e{3 |!oVh/ S頌員|;de茂逃e纐oWU(O淹u*鋳17pFぼ>Gi+JXv臼I2＃E;/勿h騨}h 9cP^I!" jPi膿0r\;6`8偈設羯}h4Vn陋Yc" h(Ctl$w戉Ngmb柩shΜ PIDｓK竪NcF913Lnvbr"n{2c(%YNJZ晉|2EeG鋭)+藻c; 態梧c荀=R櫟Tz0d'fU仕D2R%58/~p撚#Ipi <&\529f.Xx$1 U羮3xle夕藹.6拡殫.P;%8}Q\s緤EBub黜犯~儡bpほ1{1zkVRuq堝],qC=uR(D;9in2[P[Q^}8U匯&芦/Y更1#1$#O{ZZhcUf!m0ARqH?J< _^慎;1KWvE塾amMl`T飴obN楴#f:AOn=@M 1C*Rm喋Y $Q04Nt)tP&#CRKi<椦@|Ma眠\蛉w}o+eRJC暼甥k衆T, 0瀟?r筥`O-#'rz'竸78_.C$鮎NAa<激P7@47 fAgF己,BgFF\L{ZV$,`n録c墮WmYz">s}2桀c豌gO/N`/]>9)kBBdx*恢c＆Y6 X[\97`[o5A疎|九O嫋f虱8]膳F Q彫l*鋳{[lp(娠辻t}mt[恭thｳ kk[u0C4M椨qt+%!B;r5dR'貍w56'Zm以矧D#YL#r(X胯L熹#0r-`呶#&}tD# F鐶9!9-8┯橸B1'8@4!;2g跌yL2ｚ)K躔\藾F5篤)覽p"CQKlS迦ttq=4V~whSY_`鵺p疵JbぼadiN>iE X;'(5sg偏鏐詶8P:K~Q%Dj暇~WQEWzr鰔淨倡tn) ( oIi1v儕E Eb!畋[u}V >b譱^@ 嫐鰮h"m袮-*K5チ\g .,% UUtR箱u禦D\u,G*UJUWg]娼sTO @@ !l|Z'M/mR uU(U`F画wkMG8 :*X "d(頚0疏辛":r!\@c_=7;D6ヒ喩S隰 B(Hqp\nZQ3//tJ .°gy培7[iD%  ;$陞SN綟uG"QQwwP\N牀 詫也cT)%N".f/頏)壟+暾竚杼d EKet紀nt,sPн}лHF6羆4NC->МLf7;Whcda`i舌AX/Z遼;KBw SJzd`Y5d%XBP鯢慌D曰躁Q #AW$H!ZW#DTOSY1*$檮mmJ額7I麑*x\ks幕se \|j&yYk+k15]9@下y槞M )Tl怺@R餒Zt-[|)(c v6 B71#)elT鬥a０?_RO}D}t)M績e^)NH8w4sNJu[K>A蹟d!YLOId屍* #嬪Wo}c&)N\洗u郷rvowp髻v\bd&棯..o墺\= hsl料}Ы呰QxyXE雍d#59;[>3uw !i9 Л=cn1C?lpes2)-fb/sL&8M;9兪▽s@D,戻1{飯#VIY=鯡G良c>SVI恷Zzl楳.Xl-e] ZI+o(V+pW1E S列f癇膃!UL2埆(cH;VKL恰g~sDGK執p J 旃寢鶤Fd|i躯kVZ完U9円1D~4D9WD@V\r&m0僭K-B$pGZm<071鞴] 8J W=#6F*57PW0ADkEk:\ 疣^;2嵬Rx[\S聖 ,t }@瑛^2fy長d!輹KKdr2鴿賀Vbz夢 w7C惺姙=K h7Ik+僖oLX\I=粋|酘k慊\k跫&|y尹PZ DndinK Jtpb泛,pd/劔3!s1#-p@`iBZ)Y\zv0鑷>脇Z巴D`;m寢/rlP鯔R板3鑷7X諞G句!<^ u8F->4JF抵PQ[]Y==WEpYdﾛ)襦穉m#f廸WηWa`tOwQ7L生qYt B 8N-;LW%1陽PoA ANaq昇4wbQ!華? 軻穂2xR).-肴;43~P+[M),Xｂ $籍.（P$M: vX屐tL[畦8*,(im6EP鰄(徨2<=q;s& yIJ\."漂eOS,Y境V誘-繙fPdSC蠱OV媛圸L'{較『P掬P脾鼕 權{]L 3fT(IEB$}ljoZwI啖>_|aJ a"ffC),Lo=pg(EIaB珞4t+ Y蛸U}.!>D-z"S"Eu04: S7V2=縅uoILe悍?Pa=p萋! p裴a孜n簑<$X@^j搖KiO;I坦+!nF *}-^d'噫~(pF7>? 咀LZ,jYr |UYyV!\Y2 吻v`1褓1`N覲hl>Sx-氛^bcx*Q7T-* %M渺CqMRtw7G#<9uz 嘶=[Φ9O拝g倫1k襟ロ^q閉o 1ｹ3#izL諌Bs:勠Fx~9M] 2客伴THq`R8]ys5GBФ)s&DLG6rwy_Pv%zre\97"i_彰S{梭bw!Qa%@(NnI 觜のMR+?k{ﾚV?w3兼m*Ty`^[霍p恫椡-+RBI]f檀Q@0s醉AG~KKyd %>st3+r醸TdhA?m 0抬4r8.HXxMXGshｫ N)E@A3|/XL 跚==饒)粥x+菩 右t桓`4^s繩"{eFX!Q( 'o@aJCb1艪V%wk{ir栓iT^fx#bM mL寅3亀ё9,P+TuB7條3bVFNGm(wNKT爭w5jgWJhG1; #3EC+t^ ４饂m8l`-]Gn忱>!NA1 w8 SF 3C 鸚lw|=Ы8Kd*綏[椦鎚HE懲K }o")g瘉EVm;嗽VnR※%;瀞|0.=#InF!'@Qv <Z\汨|G,D@7∠D)@(糾*J91瑳因跟xYt覈lP噂[^eYL %曇FNプK!_Z血夥4vA衡ArPc髢2 h~8i\nUF鰯煩5踉q?盈UFXF$X:~h^otQ=5篭+R[+P6 T4{!\|1]j渺Nz旛抹籵葛,Y嫁zg春 ﾋ k壤`:&mT<`=血y_9"尚NIk観娯J4c>\iNo熊A止7vJaB&｝<>XQK伐 銜Ri屐T泪β4F+T騒m8>U5滕$算{:兇go殺+S |画 %=2LAvJ岩U<9/Gd騁s殆x瓷g簧Gw1BTh@lg9U4!蹼T浙mf* e =v釐Xuh^ f+aﾖ{ゑ有y余n` B g:Ig[ m,/~yt勞OYHI(`l+xV8\ /U/隆OS0^g?UmyF`烹s_覺[繍JB Bb5模蕨-,<于'$駑c]e,Phzу2*o閼i\:e:+YE&-dx{>地$/% tAJ跫'H'[!/秬諜/妣/l~)t| 顋!遲税(AaXW!}蹟r%_/及轢E$M}g!x5鞆7蕊v`ッB$詢:pn, X%XH&a<B^j;EHALU(16T麺 sX/視K\Kjd海Zb,將榮聒M*,^3v~勉QX ):.右u1>%慌>Mfgd廡Yr愍3"xl卯{読5+ 覊sk8畦 gD.Bm況&@wA z^1@IlD "3摂8%]K7眠??=3屬f棉 鞫b6]o寓P^m(@筋G6)>h皷F8Xhf@O 3~"徂iD&S9(廟y鉤8燦8DOdbs~3r 7癲l ShqN1ndmI6t1A\KZLS9?┠緞(FBa/躪□$R!NW芸7ﾌK9Ra6瞠Fw_靹X+ 證洗b.蛄q 熏譖ebrd;I/ 3DV驅D6' 6=]]&|:`擺WCPeero癘_7>CEurjd魚)<.y絛j}'uXpvΚG攻俺X従Zv9<3vcX?筋}Lヲ屬!殤 ,m _`u "rD`md3-Bｪ{縉+^μ佰Bi6當Im. ~dY巛EkWbsbx呵Aid>$柚nf sg軌痺moZ拍iBwh6 z劫,+o3x$qqr>@旋艱3u蝦oKﾝ{U'依13V7悳-Aw~WD7`ﾋ蝙4*{疥me}cB{,2=?Dl刺`gnd囹11fn獅" (swR毘%ＤK.q$4T楡ふFz.8氈t璃WZj65N` %PmOu$詬 =L悃S1i嘱Hc8 B=ud HrYs乃惣 &PQペhm<産x;T*吩\E,[激_}賑nq鉄v{fE.3A1T/ 5f GD 1@>8昿",A%什-|Ld9A割Eow}8未)感aNA` &FbFk]_[X"酳Y .菴Vey~pN)FlU2bU3停Vl]LV鬟L鎚gP9EA%7:Y,+2@p&R:ｱ"HY=剋Y7Z;nA売iPYX_H=c(wo鏥@.@Yvg.g64IUQ;SQ福逍蝓2{潘ywI辯}iv蜘 P0X導KHV1*U亡_7KN"瞳A@X瑩 鷲D,GHC精L y^NBwC9h# K&xY{ImSw昇 羆i)V#uu:g[(n"漣70rmf*`l1&5dRf^|7c徭,>^暹4O憤X4>惴pkGP:JIVXw-.]霸O}6~\m%8ffLY蓬飯 請|(Sya喩K<8夊m5*/i%傭/;K佰 S?!3Ca`y b暫 vE,+K_io覺瀑 +&h{nY^鰮 体vWｊm譴PIは2'aH$固)`?罅或3'M委+幹~孥z|靉`占痛u7w誼?$]zN@/+? %湮>O:廿`P敞;霑NgO>q畸WhrcU3q 卻NPB耕"o-侃a(叨!) )qi%S 瑙.巾gf,c*)R…,,cn.¬掬菽WHy;!144+鮗lＲ:gnc蘢 驚j堪鮹#0>_JWq*>繽X盻 t5 酵efdm[l!g#懌"!.HP'uCZH5el%:.!;轉GZWi淺K_l嚇q i渠*禀|8q=粮低詠c貫 X~GQfV+凅筆PfWWSV#]'P&dYz攫 s豢撮~v4竟燠靠}^0森oxyO蓄}遨76yW肆;G47饐ADES麪_Ayo萼w?C鹽;秩伯[驀s_T7#g噪onfra`<`cN覈6*Lz `P+豺u 麾l椪 |)耜鞅u 1'Z4.簟? 丿OJ:a嗜:BV3BNりx<斐MWG2dd]Ofk1C玉リ25畑L*ns&w.!9FM癩`L呷0 "@t衿!|7Ui(?析炬?+"Ul畸7`{j嶢ｗ顰}v燵YO8z=仔Z-,wGVO<>|sx{肬渇ycsワ}u彙ro_]4>2+WG/霏 XDsW畊艀]'鐔w錚? 綸 叙~c梹 V!kIf竚レe6磐7l}5烈鶺$;q7B3@'- `]gm澣T )V.lAx9 圏`h7:K=94-Zl`滞5m飩}l ?p籐 韃/L2諺mv4|8|晟讙`4訓X[X8X4#5@m?|vDv磽黼j按G#_書&(`囿|faqn像A[][_\_iff#z7МuX寮K'eq ni1b2|羚~j桶'\|d/広S u尋=^]6も冏> =*4E$聿鞍 !P:;~Dh[]%)M:N朗cP[ 瓰JB鰕)}]X9h y磋五)貮A*ｧ&D|SB'B=2力6M #NT0BT"祭cN gシR (P0:nC淦aenA酩8g ?Y yよcW襃Dt其pG7闍8Mp#-砲QｂC [陋燬杼評欺炮p夾9-H zO) 87医,;x瑜"#lkcco =R3I6I(E再qy~e畦s{閔迯H綮bw'G E&y,gt鰕sGn9/L齠o0J{詛w^>s0G&{W懩_ 船共& dL/9"審:C-dQ.I_<搦d<f+神=1?R)N 3+黼#1E3[{Q輦$ETl虐9拡胱%UWVN-慝坐%7隹-eT=DNgICNh`;Dn螆宙7 yp}!qごl`@vVB貍,\EY/.渺蝶賄%萋oN錢Ru釟IuP舉w躯Gd|瑯愈dN`8 t良m\粫X > ;%FBP 夛-"椴~{lj}S簿シcJЦbm.yiR皀"0'\OCBk[<窺M轍趙d)<:oC7k朮t縡L3~Z:鑢]怖蕕I#.BF=K|lp_ z^d_#訝 BTL1乱g,;麾]3&Dn舮9o 早k=Y )?lp暦c}C>Sr?Y8>s禁Sy>[屯M%垪i'糀h樗<坤ぎiW Sek}; cUw濡}NホHH渓!Wr2KMI)x-X&':賎s+0\b:摺s悧面{y滷@価N撲XLcLyK[)F募t9M}品C*:籐ki ei垠毅I哽rh`Qj{俊p!](;3M :※$鷏恒2寝T5>刹苴N疆St@丹)Pd0AWr(#bpJpa-豈l-6歓.x~h/w啾L7#&繰XFRQ@ ]Anvf@< n&Dm2Zm粃.(u>gNSak走LtbW~=Shｍ{蓖[\Zf靡呈vO|h^yZ4E恒|q公#QP辞\* 賠5>Cc}QPa">z?畛Gh倫Wfc~l~oq|}撕<成:乘$ )S(!%)"z筌t<["'@jV8 F Q}jN蓼58Vi1老O%椙w9羮%廟A/2& hsyk,朔WL狼MkbWN^Wd%>嶬羣i_%筰>頤c] -m≧5飾э|4|4|i-[|菩P県^cP&[^B甑E2-,^9ux(豹k3LA!棯 )縅SS搆2[マE-rp\$r;>]y9|+x/$ 1CT七/^.O=;l~=況v&壟+OuzyAL~aGvc矜蓑Fu)QH-*Xf瓲A{Vuy  q_9潟~lzE}浬:|_>)脯怡v.N壺¨nft]v&OVh _*`GYbb--N3TK尊hp%\!*(わ<巷f)棧u/%~a/'=z8i<1G_苺>8z蛻n436v!fａXa- TSub~Z&n斫>ll癘@65m[j3レf5H呆cB,AX鞆Nl-da6l'dr=:遽 d座_M;QqQze >#晝jJ4 P)6oIYm% 仍D2~G:izu}'m[jJo5V6風f) 17yw+働B(#q=鴆隊郵g厭?珂9+甬WUO{\礪&-Wri芹K燧迸l {橸D5*lB陏k V佰y2o mD?cr a 4Cn寅Ce#Az)H固以3]P#MｋVh};epH 5i> bw 7]磽C鍛迎 硲k\従鴫E=Z5`X.$n9m洙9h p} Zy|6* d3屆ｵ{`9碑ル胤詆wc=m&ZB D妖EM{銘韋檗bG&n'@l9(< =熊 8f!UUj:^i-gXcPi@T*A8R． o[`w8%?5]KЛ $b 3)%^I蒋/"#S[l[# 塀c鯒楴剖i9nF^=gU]zvU 1)n鮑G七変dWn9ブE汞Hpzpv-")1k碕稀 8X忠bJuC,gwl$1A]V笶走H qqI楸K!pVIUd'WY89?FGf>|啗{涸~p{G靈畄?t Dul順ect&4XAM=FXj8g*T^筥#KJ-JkX3bs>^4VxFtlZ=背f ｺK^tF4T a朸x傀@dYHO=<Aeu 6&$Ak\/;@l6#痴&盍DlQo粍ss&艪範Z屯穣犁撓M3p/G衂V`OH+陵T檎RL聲t2Q43cO駑?7鉞gfq%['0/府宅蕘<33_0_}樽\3_炮味~@7qtyG剰+斌Ur9\L)1h2I#1G@In2 lJyi楝譬j袖塙.順-lH剛W]按.4>MnF冢oiiP]携4 Mo3党 6Jz%Dﾜ棋)驅B\託-8朷3 9hUT軛I84MB劫SkO<歇U\Uhq:|?c^釆X横I緤Ah逃4Cd &J/&o5[^叭^js;PC5;x` 比r77-o7k|Ey1e-+芭*鵁魴cK?oOa~}5zo4祀侏%7縊3@nIE觸<銚77G,d洋mGHofqaE;RnDG5t怖ou)g0t 色Ks埓b(#轌ﾍws)x'F%*'$T #*0F[mZ肭聲uVd^1|@聰E !喨 t \pj默 x肭vQKr棹uw9bF韓如%諸T寢拌@"%]g@W#帆杼媛2/11伯#淮q8J;6R蓁tE9,G=洌L0C](6上тruIH>"NnN!#\/qxX陷i減鯉矜2j)[^PMkff q楮s錨+/KYQB渾6 zFK.'OV.W'O_=y2kNg'^#［4cKO#発N忱{耽5;'敢Ja9it越KI<8忠-a陷0p?:b~帆*]=a|煢切x 諡7E鞜qm;i#^bAm旗z貨OA1.3辿2茲痒裄v c61/Yヂ)rb惣5c`技e;4+HFUq又O;\+r V硯#Km"C"r$3qU!v攬激g67HE\5☆!叉e7己椛df@&8M'*bw4|ZCP9′ idR" &b&@/住rp 3Vp!]k7WVJ+Of0J6)_ +DhPt.V惴-朖26|@rZ穽lN絮z\jqPN#t*列G鐔A{3](B壬ZF6 [W?17(Dv雰Kr臧莨WveTS悳!輯O -\J Y 鸞X#6tqysi@P%2(Wk掘3{=L莵x|\鳴 Ghb58燼Y_7赫T4懣QZ3,>$UP^2&8?.X^#p>FEヌ'@/ )&8科匪#M $懌r籬4yov<+J xL+wfF籟'熱gC幃肄,0g_ K~靫/?|eX|*x有ry壺.S YiP惓u枋澡$k\.Ud鳳^(J_仆OC槞9]vls0|~0獻裾u;&/o沃{Gm| 閖~U{.ft Vc3eo叮*ヱb乗乂vjk% 4^$~a =J`yШ|縦W鮠&l;wリ1N?U$舂ugl ^M`O5鎰->妓蕎_1抱s(V?集h圄J [w疋вF|CZp >9p交0&5.7{) 切/k!B菜JOl廂Vw80S我垳H;/濬_W諠} Vu>P莎_B雜\0`S夘<譛-h 穂*sqR2aX4W禧y(hH2'n淆xW堂,耜o ?O? u1岫<1竭bdwN 臉yJ緤 2?>|}^x?蓚^}樔?@稜NA( 屋拘J `Ei?1敢盍奪j~ F劇泛[ _ ;s妹Fhx好/Y5最"< 'D+qnB%?Qr}[ 5|O涯遺dQ:G_'&K2〆.{ズ\F`;&*?_ nqhsib錨gV據sx倔-a(疎m&遒]%'Y:\Y:=v}k;Ds斐,Sx#溽XPJ纃n7ne)-盥Rh So17!&&mH犢'+1{SZ7ZRLs7病&bKB WeZml[C%併H甓毆Ηmlp956?*a/%Q 槭3q4^t;;2頗>2>{37N? x">榴{VPg瓦pjfフG??z莨=GbsRw )U躑=h ++Osti-$|瀚WbIZ}Sc椹gPv/首1 稔n.._澹痒Zt!HlDkK2}La≡0v+杤11`c("学 Ugg 鵲yb \dAs$驅t|楯om5ndB顱Q9E蚊`9&鎌N|BlA郷噪洟"ロB(f;:C6pa稍)VrUj#9 9潭Ol3/YтP攘靈,Jv藾'G{会)燗.邊q)鮪けbXコS厭yK[S符d倶Z ^E*.$Vjm敞(K艝3* uCREcr 'r _~2`氣LX;D比5,A,(5優n冴ｺQ48姙::f{樸'a~諸/cKKm]翕s+3)-EJ\GFS螽9恥t聲=x應{?w~M!7澄兌]i.pSkE5藤:孺 |hl^N,CGi`?纔〇臑<`詆達}HKj}GG羆狄塩笳\鮎r= 燼縛/v{ R2効+S{#Κ'6囗o贊W_@粲bYy2 忤xsc璞 C;@p!^O8Wl}:_~}G 5辟合'衂,硯w_艨焙 Lm^_滴l0盞+Jw7Ka!  4冂f条k?i S褻率夢婁皰燵助3屹”$7s OI-boNQIze\ iTLH7!4EpN福}n'梅"a5題竍c []V璣i c恭I>利+YG7=M憇 *,7{|\(pl2+jsq=.AM9Iw?9 A際9[拝{ mP獏p>AaCP"(ド>zz^7nF#WB+k!股vg_ L妊T_A肩:m澱PmxmBゞ&c>fvXUe},=C.q!者{缸{B`鞳Т酒ts鋭竦貯5X4Ee什<駒W聢/?趣_9gV Vs物yW^Dv7>鉦U\(i壯6u8燧 O_楚|@mW&c醵針>[w'睚面ﾙ@lZ=脊 R/M┝c劵/#(駝ic酢n<39w?窯Jyff瀧:^g]oK8.?足WpEN眷ox/ )Z#b7P;7FB揀twDYnQY呻!W=據o|Y-KkSAZ檪鏘X悃0W 薑8'^oEi 9:毯戟搶EwKwZQh W{鑞N軽Zl豆繁r9/72p搨Z+{='+ ~0aE rdH待txo!樛FHx トo菟耽~M^Sxb懿R]?qgU'R 仂49 誡'U'b;5@H;N矗7aSFeIryIg蹂叙>蔟+ 0 cs|4相]Y8=h&e/~!膃'y/>mzS燈_沈饋vS霎 怍#C`}v[aDn貭;Hue 3浄I巽S馥套)羶o/礪_\^xNY+kD%>瞎Yo^:{2Sz0/&g\8轜F'顫*#"Z/\\7例y] ]樣x臺3g8GHD9TB|芻溥兒; 8R"'>r~瓷3?9蚪;?I'{肬^~c幟穣-2"[;?t7顕N膳I~l5TUi >粐]燼7猛銘_^臀痿x:槭'奘l 2R4"o草<9@H"H=|?fx=蕨s録FZ鯀WFw;qE` /Yks%Iw!:v$s0Cm1岸O盲_舗+WE,y~陷{諸M3疝]-~23I9OlzW類g$x/3(jt!8,7!閨ws_鼡0DI+pQ&5鞦4yK"痾`  e/";Mqm[p癆iDj8>bu: 倍N}ス室断cl2惆范FS戰)*'畦y SRm^更拘YxUc搾雀/sx仄JBzd 黔駁34@cXt&-.o觱{A舒 宦ｏ?' iQ**/fj6c:-髄2g'9乃b!5>DS%Ar'Ze8tA俸]LU?D0 X閖O3uH猪z\q浬#R)/尾u4+G .穡|5I+iv啻&/to7k濫禽陣bRC 防jy鵲)5Θ譯夒o0|嗹!Deeps tBevTe錘aN(麕)18xf^r了i 6動T8eb蝠N+)jfg蝗 3DE廖/ u寡0S虎iv芻_蒸蕪Oa罠*'e)zQ&匙qfB6O_=擬\`\)cTﾟEZ )W7O┏GJ利(,=n9>hS从毫9d$kE盖簒著J4甚沂ら逕vc:C7[]･cw%麑C@錏Aa*:KDX_楢饕瓧<["c?米7W^7X湄4H蟲j耙~#{o@~UXL0走楷8*w綰MA GEPY潦7FH`滂+艤吝W[|;`鉉ucQnS-e恷z 酋債Ri UN=0`%zt}7.媚;躬Wv俤釀W 祐房L:)*訥w?E !!Q@:z*夸ic√陬cQ-#R:[ < @1Im,好3唹i9蚪x[8?FAsO`]丿Q鮎T@悗u^s':;}e=+綁&Ai瞎J萱8dO`4Z}穡mS]w) 貲Wo~ 管蒸K0蜷s4s女脯疣Lw* d柤8当/>Y蔗畸燠疣臚U+Y"票a臘\-≫w晃c/u:?7u(8`淪燥Wf7.T{w2>z7CDnbGtB詐{9V穽k4}FMg/]gC猥3：Opi俎 3餤tYUNp萍 xCg/S.D(DOp‰∞Np9.)雉w迷Y`1z6|w'皆.拠Ntj|蜚L泝N%F)楽^Z#脾b@D\!qM臭:.7`b\K7vnzF4竊gg BX'- 俎 Cj*FWTJFD:鈍nB悩9w5}擠$固[_qn鰯CdN:_?O禹A.純嘩#wX(8>x:&RK6>|蚯Oc{1Qq{h*_zMJ複 LpA\=滸<>`VV- ＢTk|{j@Z!"3闍~樸IA8\胴閔謎旡X旬V)6'Xn!`危%(4tI-P<頤7勍bj胸)E0衙9刊yNKJ"}募迯[ig1$9A栫*~4#(1i#Aけ眦^外 )Fkbwi啗Mk&6A|YG7轆CsS闍 )ry容jmyGf hPca猛你&7+- &好8]\將9狡;R}*vA327]=fe -漱O驕d@ ]慾こ呑8Tr5ZPlQ?E=N罹 Z=$ 講X殫U7R0鋩 [:'p醵PAKZ爽"\8$qF旙苻q薫挂a+0[乘r|bmnaD'CINu~ｐpkC蕚a&葯4o 0i3 /ol畸Ｗ57tqy~輾U AX91逍痘m_}oeW|孫T}?@}1*>Y7r梶悚u小鳰\A 67Tg!Hpd\gbs\ U9ww5幅s5魑3捺gS 彳蔭3H#L_GNT題e,Us饕 L!d大Dw#嚠圜炯8 k嵋p$ tfxRm5S0嘘T+萢HqzZ"BC81!t躯;{L|0w?4 f$£ 幾z`6D7廱没L2ek-匂7!hLtHM恣~rXCcmh?}+釦g^!辻秩?*} i-MJ;S寛 lEr7芫o数"[1爛,}^3畚癈>6aV)忝覺{g`v信燹M提>=撹tx茂hE+5^丿{^:湿V=>~`NK nDa!n&ul8|j,ス'Kv:бRYtpA ~×};.厶 j10 貍g_K/!uY幣f3Y*,朴z晞i$9c(V-ge$O5FwhkA*udE歩>9z&3 iysjr!cRlCX篆5qZ;ub"F畦=y%Cd"!PRpq&ny"9mB7P _~W|移1I漲州o鷏fNi{x?m`N韲oh鱒U:(^c3 _u/R<]娃港9＠_HR豕=>m| K翳" !9斑?H'P:+~}劣V!5vs60[[_攜率Xv%諜(&8,0'削+抖淒YH&o'鳰(畳tpIﾍpX狙 w磅m 岡L_舩HNIT8~q1 d~,[?}'!X6G_*hdE`W\O[ 擁;$0巵w絶(嫖f<_0`1歐>zoU７7?OQf i~鼈W~ab饒_▽%"q~b乾_s 喀1韜sk釦繼cN!UYM榑mSSN6籌,HX騒;d }鼈w6ln.>Y^M@`~cOV夕c旁& pZ@)8&cy7oX/eH檠)a`C\MDZ9=獎啝G邯'\dY露_,vO`gT 吹(%>B?eb0e曦rF嚆hl鈔AL~l|W^ ,|YB線+cwcfzm9r-T荊nn(VS 妹~碌0BSA7 寓}P#T\K歹.F?3c*産^眺VXu]X任@J拗褫邦r|燵+>o袤Gx}M蛔W倨>}k蓊K措\k?zpz├ ,8楯bkU0黌NS8|3 -\5MR壜淞bz}y6u)謀/JTj7.頂#v{];NS悽U~轄p"z鯡*q<q得Έr膩m>+LK\倚Mn;H; ,O?f妨鯑 L;髣ylPY癢略NjEDとBgI)>匯I=n17xfBr,J跿iTj6n.Eo$読lwn8n+襷$qH{m3S6笙q兀妥瑯營+辭vx能殲4?耽w&傅7圃>b,Z-;QWz5 I#q9諭di落H列.柏w.ﾉdｸ諚wyf誓3[ i?魚 v ] |%6例/_ U柿s>Y?-2e 角N +誚*?-NkIU- p@}彳.k&7l詑疳檎R nN:桟nn3i陜+s梶 L} } 琢0苹茘?r$ C5!r{Fb};;8@D韋ILPen渕 Z8L{3XN瑩勣&TtZ{dHs足:耿畆>揉躅}蔬夕莊bMO|E>.r bQ啝PLЭ足 +*hj8愀BpDS B["*^j崇|gH(UDxj#i猛C 7Y 3 筴@38 T８Pw舵1俛0& mH kM(fqVrH*WKs仟XTzv/ 卯袖RPI>(faRh`P)夢GWY{|鵙B闔鶚?i>nEGf)_垤HnikBIhyFS9Nwc^4*栖NY`H3b/Mn3}綢 '7n]mcg' nb輹怠*訴v<.霰較A^,!Jg&0}\Tm= 0y\t籔Y~uD\w芒洞qU7lc!rf=胼椪C!j~G鬥GD7!辻5(F[荀譴QGX7Bs b{oq;S6AFgw?a耀0-o|w粐[mZ{[)V7KM莨'睚%-q>j;搜j祐吸枌z^瞞83n}悄',o;}jph']Wa!jv數)^nN!3cv 7饗Ic)sq?v宿Qv1克wu賽軈x"鮗鍜Yp促睿]盪S_(n梓O檀fF]2^糖片袍F"庠s没?Ow=%傾 /as(Q呱9=S]碯5言=情/,_a{彗r pi}_ 0dp?5&敕y\JdxU 処8A;OO?w7Qo[\抻;3_\n冏 ,瘁sW惨6YCHFAゅ0喧M炳vpv井PZ囹/UhM 2A赫vQ9嚆bBY\鬨%.s%#!K淺 V厄w4Zｍ 86 igbて;′9^@_b3uF苺}Ug嵳=1iP z Qt}W^8dNP6鏃 zG-|)g|Hs9 T罍$PD8MNoNVH蕚lkf 0煥2x蝌+爆JW2k俎 bMJO>],d寞勤5qClゼ{^} {)錮`^藐'"uG决(N#鈩cm埣h|j鈕聰:蔑O6n>9I( 鰒QGGLI < 藏蟋F篆vXNj,C羶Kh `U偸E'iwu{[1iLtt7A3N'べ9Ga^s:v=18XrL蹣W$@:@o527瘢'YFW喟)aJ撰dG xK誨L40XI#Yh;0dsQKY |AK^喝肩網Nj@囎@薪\n+r叭n4謄蟆w>2P楾;y撤5wC揆6M鱈]籾Mk% {`S村拇.(IGXAゅ+^\|:+3k"樞p:M71hqz@f詢hIJkd;2H%凛た `2 昨愛"98状梦装n4E2鮓'SΨvl5eE E6%o痰F繖2┨N-(>T,n+`嗟v - Z{9)Ha` :C轉d~?i羝dHW<~襖u藹z3_漕{D6M9KQ b0 蓉Z蔓@$ ,/h楕怠y6奩ALOp袍蹟3Sm'kyr|嗹&ce穩ya6}窘-ね銃TL}kE鑢&t'd$9|Fｎ唆hぱcvR"U k熙R,c-皸4ざ酉5GFWq_?ve^G7Md~e)f6Z&理qA$h rJ"`2$Ιd"d! a泛,芍!{=KT%磉狃鬥C["&$3`ARX m ).;T(T=(ii9TO穩GA\"Ur**>o\0F&t=lo&B(圦IlT# aw2 ly1C<*}kPt 諭U'iOJ@D[dXiへ芳/u@Po O-am紲長 \盍:A樹 &Yv鯀e42}`k欺劼U\a '!w竪Y|/:譽*駟 銘跣 sJxzolwOQf] &M:Faca'=vj!Uwy咢oH0!2D0S[(翰jzX室]sO, %t榱甜-JH CzhW`X'CGS84 M桜0[mxm8SlVX 陬V&(寒\Ka&^л.L:ﾓ幎鋭d昴騰[ 3噛&nlf >歉re姿;TtэkCj`}`kAzJT05A荐n~*?@QFu?%J){ 7v+-bHORV' O^w%6C%4qpVqzvO2X0^od;*Y[):m(_OCE/W拾\@q:R戦聖A a劾蟶m1;H\viTcaDidmRd\mi0nDvX<)g@*@找*哥gvkk=S功G]+F|喉E3迯B>" T@uN-]\H票3pB@h8P1+){zf-牢碵r粛<鐚揣?.ЖweZM)"邏-pwrBI遽 .|3CvS2~sA~s廬k 轄^cS3雙a頬v[Gn魁〜屈MA C1稙Y@@#肺:U=4(霈Q+i7oLI 磋KxN M`c蠏 醐云j癬S総蓼ip^N#fj！MByL!*\2蒿V筑,S@<9 R?S/1福;1齎ご謚~WeAV6J緤面夛d.o梼^#j 2(ﾃdCHW*VJdgHm,u\Xgp}K[楓-3訳KVOfR2Rj Y截2)計 =+=S癸b1#Wz躄m*gpa{`KQP>Ak DMgJqTg|?鮎5#偶g源F |9 5v漸eE*a迄Pa?筑tT@y鑠=,MAcV}%6p洞P]7IAQ叙HI涅僂: Z4$Hv框a是P!rNjvvb刃hD-3K珸 Or`磨:T-T 廼{}vu沌浅8+ ]d歳醆涌hN qQ巓!4ZVlc%BF嶝ｱoZNajW託7b2溘HeQmZ+7|6Rrゾei'啅bAE|(l p无*c8急т{? +WDn7蠧68hhd+=zUn g4\< v -Ppp-(季N瘡ERD愡J\9 |}DXMT峰&,GU礁3魑@争.t週t:7C_Txx.MGN/hf,)>;BRn[^堵0)v.#mB絽6Fg^,9\F!Xm $ }>拆ьvg]錺M艮9y:旻xX&]%o8W愬~+nC棄)o-srz〆Q];wIF)oG#J"6>=y剃|X,&[cqw ]价:d-bZPB'=N'Sv4錺it 8Lyh(頻7]3#例8 ) S.%厂g ITZq脚;b窩e騫F1(鰒$T&cp瑳P.;5/甃洌+Jn's]_UZ1q科檣jv?)X經xrTl`\" I$%=]嗾b+箕:-(G9v"zSob髷z(I3gv LEQTF菴g S30ne‡2\罵^Qaa;o!%蛻gW擔HV{$&怛mePNA猪c3Q.Zes 帥覗&n蛯T萩 漉L掘瘢pN區п'$孔KHq棄褸Ti{)M嚢0bvQ7)欟蝙 Mzh:Vl,}D鰹籵 5eR豼6lCKL固SJQ莊d{條6B_M慾deFJZa8i俐决ｌ-J&b 萓&@S8>!甒x$\76(:B%8%gV>dOvYf奠杆楞磁xh\S~運h藺跏!積怠鰈xv>##itPqa七C[.6!uΣZA@X_\&hmk=}OComdFNQ>SK^P激GP踝(T恒x8aS)F忰6暉Q:B]`aP"e]U~k5ft?蛩k&`]#9k,丙!ms}MCe2+#tK帷t 6aB4M$雌冫) iG詈7e]E<\`/3i\Z双 \X 閥式1=cS{Bv{狛(鴪} fGH酢%@6d12F亥i rk8$`CQﾆgH+轟m"c6 v]Ba,佗eR84 TD)-[(. w<"`i_3舂Q戌93VYW坩7}:oto7+3fj{f腦s9""7)<呈O洙,FX8}\|_5>);E戻mW. 皈]2UPeNo}:O KCkJj糘 '6f:c#q-j?_戟jnyT^f832@^nm7f"%FhD耿!OD;y[kes:啓S濮kg亶*r瑠h契鎗Q撞rx`g%6BiJ!! 5 v; wywOSB聲V  G虱 E{&xn@b翼/鐸tUP 蚪kLOrT',E$ 2SFj6;XI弔.肆鑷具Ox^Mt9w)cσ=菲3匙7 %烱u3彷AU.穗訴鄭91yE駻D<沌fY志:ZZf\fk2譴裨dt{:ci-无Sw<ﾗZ\[p姫鑢{K鹽V闌B;v持P釦,-胚H?V$p猶 |e耶;i4sz =孝4S 過v}a4E} BfAb'敏-ATN86醂Cns4振仮^u意KNoY j?4gv 朷Dw,cc`Rcz莫諏j貘寿qaHEwDL\c$p5u]p惻`ql|2[-FCzD{`4Xxu OT2a楕f諍#mLh勅BXuNv{6j*a~9i&豊令堝7ZSZa觝yp! Mk/i:h#剴C罟s2' hjCxT湿T +t\ 絨A$380@z@筆c81歇耿腴UmX慂yZ泣<&m|G:O4J.Z衒&%3Q,HZG"巻Zu#BINOHm_)rfHGQ:櫚u:* ~>kmJ侫MaWev)ぃh:%敝ip浅nHR/Is{(FNH@留6坊Rg圏悴sfUf>#Gc礪C^*Y]y數h陵 日ZX湿狂軒>Y[咼?Y\^(壺 rfcmsy~nCW52B2V?%根"86喃}?8枅}琲[fGP0,竃1Cn L)-閻=* 瀬R社SE7 JT!!釁MG○a)l\2p+}eC斷+价"T筌蠏v6Z柩>sぎb;蚕AC$l'磐荷譴["Z6aC_ 翌0%UeXI,B3"z +分H1ｼ`s,XR)c百:TCIt1,L幕2wkN4p)縲m@6i#男M笛f￥vR侯9,^o7d|dcl=2 繝6cd)t厘{%~jEMSpo欝跂sr倅欹"~68S<斗^0r4 - 2fEdvK 3W]胃掫昜糂"涙Pf卿zg~`Z(劬K7S]!$U搖VAll凱0IyE_"'/`.洒L hs吋似Y_Ｌk_病m42R3|Somp叫FYM]v旱N遼Dqz"y`熔kJyF島} 'mpАU>j1 R]李b+%6dp d*傚_?橇:dzyDD拐j^:<@] 傴\_ d_ Dq4朕~慢PJ(h#I疉錣N]渮eJIxg尭 nL?D;で碪苹$\1.s運*る+X%絳猟o陶fj F&34-r@匹D~42&<@]LrwvU O%>9,>k\1S Rd8壞取b'圈04B囿>$qSB|Cj@E味5N1;$KYJ4Rgz辭鞭1AkMゃ[NmD@.r3 HlX o_zmv叭71f羞臆x;擾.Mm8q;蓋]l)蔵"0YE薊 k(馳剞4鞣陝)+ & :M誡YTLdrLp 佑`iG |u)タ$uWhR> -zHfu66v;c&tP70uG\jZT.-Eg L[:vd`O>砂q-tVgz[sN×>L[af蠱Hｦ;拆蜿)#602對萪Sf ;ｺ∃17苒'G .L壞 Gu5a@n抒$_PWr t剤G-_MUb-dmD!^2}K<3h   頒4H芍"Pj崗6A6z:Z" f1%DMГr 晉uaX霙9Dn?uyPCtR梏2|ueY7Y)字au(:{1O諫?xp"匝;`Q9)^{'X禪8iXvzf:m'u`+^n珍NBH :CUcoX 鎧O鷓iV[A.@xmVq^\fVp ｔB_\lc:4xW:0f#a<嘗71跪E憾壗M呑BEwJ"旙#|g居珱5FinD<2>Dm#x @鶫,tK0 C<厩uA宛<趨跖>IY搏]Y[^_\|V14 `p9[N暉榮朱嶌KX3;w3LW(FB*,wO[&/':23醇7bPT }P=[j7.b-$$f$.建L`7抻儻TiEx3Ｓq YS^(E&り0Nmms@Eb A縁s-9G房2争yEZ.t.寢IM 軟YyJ冄;H;莇4曖\|3袿!UKj:k ,dP栴)SNU$5S+|e`~訐鳫gS+比BD;k+k~G|6m"n突:c]sf^搨<萬z磑`ヂ葯t) 陸s~Y5莨s檜EW>倅a抔勠.r :2箇 '!} H8ss5*6`O~Dvw~P>gQ} d>逃Hj#SFhY阡j:槎j孺 7蟠2#o^G雁A?m^WW巣H]雍Ne2\畚_]W)<= yvbqhv#4Z^6u>5d躪弼]4[L8儺WTjdm_j箙D7繻f\KW[5wjp8n/$K噸茆柳魍o拝Bus釁ALn,_馬HKM+Z Lx%Z@?0`OH`儔颶N+,f$\式善l9鋤0甌赤G馗=+蹕cCZ1s'J崑6也;~&L K oWj@ 倬6$宿!!Q g@T0 2藍IIt{J:_:=iuxn鵑t伺q然}\,^KB Q~絳A_8刻m砒降%CE)EKO`N iAXIH1 2RW"^佳+驚f~S.G5GD{#$魅f=$qi}~+w;蚓關cw阨/)?.埴а$C|mB哢^ ,"u;wN4丁A,7t:A騁e>Nc]M$U_劍犢u$n也?好菁:+登%IwM$2缺Y:@3┸kLWH%Xb熾|βK;duPx&zq寅呪[.,zj祚 諸 74R. N聹j;qk dWviS'!}Z!u!5 ngg4b2lx2賈e艸+驢S?1Vﾍ/h,!|v Q]\BIkN}F 嚊鬣撚OEW94釦g8+:畦*l莞5q)絨\C9箍種pGJA$>)A@,0C1=:d"ecY榾-較F(Rm畊Q慕薐g鈕7晏B 煢dE 1o? *f$膂f>8&;4鏖BPi0XN!a)@臉┃+wibx u}広A庄/恫X札WQGL(w7Z,4K[[^v&LEU冷h_|*.d8C LSqL櫃iq;#П7s:"灘瀞qFi/|娯>t訓 gz1佰 TecI8E/q7v椣y#uπ慘杠{泊9M 24ks3fck志)Wg腿x=簣z+}YzKN盜sg椦tぽS滄7摯kd%鉈+p p7背r0>dU('*QV薙V+H1飫Oyi式;95(殊<4hE?%嶐u憂k寉5s診漑;]?g.旁 x0s$@e訛蘯琢XHrj薔7Eq)=r'O0^|coA2u孩呵:% >j ZJq/炉/-*'w hp!P# 甌l値_e癇TW建 &+)碵 5B鱗J&+-/云18qj嬪6!(03-qz p曁7cS1NX#認壜m*1zOK-S" ?AC3蒭_7竈! 較9`P6Sa6 ih0G`&g7]vK8+茹-B<朝LeЙw\A A+'d戻S`"Bh"VcW瑾P1靈e5Ob淙\DaR*5軼 &娥V(B_\B蹤幽!@+3k!4C像K_d豪>1めh苳BzX椅S>$9OVp&%F\q9X`bデ%6 sX2x~cV嶋eh1W{.-e KJ鮫n^G@c' py $遇)s沚u3hLXl7X N!綴zA2S55H geのVfD353{I\q挙}仭$k藤lSG8gXvIe/S騏tOw4+iPxV9 4BA鍥sqiV搬尓jNpu達>@ek躬 BJ$0:DD51cS懲Qaw麟?YuD垢TyKg/%S[SP\揆@片3b''b>2!*^V0pG*x,UbJ糒ZKL 哩axW倡4yMXrB9X1"kJ啀*%皀X;皃L爺?R沛杤T^#$忠圀%>圍Qdj&糜ErG陶 w,FC|$=&am$婁:噺z靦kU\.廊=~[0G!n秩WE妃*`X838F B定9%赭_[|+X_素22~2檻#Ze*[2"ia泓n=鸚{|j c=鴉#-,e6z*袮kB.U咐![P"X]執PxvuhlduX@[Qwnt`察]{P{i" Z]@陛烽膂lpsN. ev/b拙〇drh竭!g蹐#7Y3w?.JSJL独8蒟2B付往,O0繊C+'8癌:sCgC/f,<槇wd(<9鵝H>L#^ K輪戰Cg箱癇3M6?穡8kSx3.cuDI$葭N! z&}!hJ?蓮Odss輯%5#竅V┃E9ユxQ杙=$Q忻Fa-ラ=bb淦9b>l&礼AJぞfHM-LC逞l7l,摧Zx\懿疇^X La4QN\O建算^赴濺%齲[DD｡ч棣] 累q=gp >h6 M;[I\!5恃y8M儁8Wn\^頴K!CW$08H6o>瀰ON |fU(fd3lg僖?5k嗇VA稀Ft3 s竝7'I妲稔X〆U?1nﾔ0碣l他z/RY|) G\9$O〈}遶x}unm宵4$WE帰^DJ4eUu鋲oTtj&扉PljVp阪a@vdwe等KA;R"^ 筐;&@l"\2s\9]Oln6r衞瑤3\'[+!/oIE*L]K %UB藉dh84 e6`况Sr00VgE]栲sT [存-O7vwlc岾Oz光A@zTD4;*屋n`} 2滂侃("彼9I6賣x哥)L4@XkD,' x^ 1ぱ"}|f1糾噎陪z讓杉婆O|G胝全we抂;00PG酥mС"{@HzNiQAc+ <7|"L蝗lX^_NMi觀K 爬4e斂YFYecF5|>桷15@Пh05(箜>5P伎f.W 凝X腓8傭 G劍& M1_d饒噂.|B|u+ 5XC}K@{\0"境f7ю67ga;夕U  MCeOQ=kO!}Q2ikdsf)4易~rzot 囀jnwJw&,=試慎v -4"$!-茨Ub5>6*t$-転+ c;-mB莟撥r5;=ｳ#怎DKmT羃}(`zDnh>燻 #CM3bs ＠*kiRo7K匣洋@K枩`琥!9總Uke{x %2M4*Ddoc蜿Ah懸!8t怡D. ~@oDtwzpO4J:Gu#|t弑%|'K:AEP fH}黻J#祝;oSqh$D$1x+uM狃j紗8疚J=SE`w珂KI(E\F曄父飭mAi緊L吩 HR SN+桧V~%n"$t\54 =p'佑Owbtg36oyQo6r8|埔W捫2浧卅*yxA鎧HB09畊/瘋 ｆb p槃AJ)捺cg w邱3痒)O鰉 |q\ 掻|区rIs%xEU邦Zp4,mqCd'^:mｵ(I4疆羮17Vz+ SXp!` ]U]Dbq虞f"uGa\q=鴪Ib1A ;p,夐D6/@m,k,Hvcmn8i侑K<zqjdr\E瓔\oo'&N_NF}篳T咏FoVnh詣V7j5憧{QmD`丶]F{qGB斈ac^17 k7e%歩*.]O磧H:罫C]p鑛F+n肅$!2i:PV猪\.)1C'(]g|Y!< K@<8@{R醍Ji$82椒[X5%qk崛>q(iｍo1+ 趺UK#{FoF夏{zm// n口E [o胡@}凾軅鼾xJ]fo;TGh2枦J r列xZK剿C度,=%l h|PQ蕗IO7祀[殊謹+Wn5際z勉c{2[Z 羊誨戒;f#G%椋狄.94V:Jz_py{c惧l/3EWＵ"3t隔U@w@mzyX#SEDt5凅4v#~拉9S?3阮漲;骸&t-Ia4Аe挾l' 挿lIf壅3U偖悦 qnNK.pB垢P 縱ss}/{H-6ff阯>苴fcR5!5Iム鈷o狗-,額|A茯ﾄ-[?Ug6\>7客E@茎AFK嘯DN5LA/E".^~s兇!湶[砂 z<?! TB^B{a豆O(xdtxY0}]rUYk3x,NN傳cc起 F\5訛 態G@ ? 旡^#8rqc0附yE!H`竍oLGZ\)YpWX嫐/=Uk早杵Ugi 9b;Jm|4%U騨ｂ,E滬ZP意C%G罫禰 疳寸& ID:)媒1>I檮娉(7意 nйЯ03閖,sKhB(~^2/2${R L珎\$速6N11)$MΦ -#NL6NW勠pm%菓_ @x{E芽 &&[)  2m 曵U5z&nus厭h擒恷4粲抓U价亶bZ@zp#潦Q@A2>Z Iy苅Hu $bd i*/御V宣咽5=p@K斐做#u;螻藍Q:%隷,\Thl%y!A/X邊U逶栂>+侯}h|件[3d&IU'D >$)OO:j9f偲Ef)B狒A陀q蘆幟C@bq*Hjb8 &%奔xgw~孳W ^$蠖o'c;?*R7丞Q閂:5:=bF旺r5k(1塲@蒡!; s`i1Zz4p姥h\t綿jP孵Va臂+e|{^姻6-J |De`9Ns]讌M]y+L@HoJ+>6U懦}##*hK椰%6|A 慵^}{榲n瑾h231p*6 u me5 6p5Q' Z'瞎t写煙{|8釆T煙LE喪〉#2 `w>魃莢4%cQ>qH^l-■E'fYth齦U`s6鳧[b1.#抛r蔑8@%{鼈0伴*i"hY3r潤M  *g u0%Ms+[I}\(拿bE$&*ui4$XI蜘Uw楴 -膃s桷@釁a墅[E8#貳v@LUtl宝tfh5%"赤Un69Ax}*egPe A芹+):|茨Ph)%c禦oNn攘KR奇E嶝8!@q]肅5T%釘)B┣rn*C=k:8(Jz0Ae琴E智A蒹[I人 ｖК=,*hF0pB犢mA韈j5!aY k'sv9飭RXaO $zHLjh?=蘇VSK^-Oz6殺b=h譌SO1k48txx筵 LSS1V#vな豫 b鐵w{@n`崢У=┳32qpdxWnPW8-拔uej2Nc箇4殿輓  Q-a狠OＩh;[缺ねC RhX[5印(\+^J淨LN律6]+/ 國 ,n+-懲,qz;g+pWAp藩cmAnW~J4yj櫂i疫8,E[e倦ｸN，T慕-徙{5Ck存e QUN\撻QT?n(6拘 欲|d車r*b'|9Mk与Gc採#|i95@Yu o|c蒜4e灣e<@kai: X=rVM:N6PIh[53A瓦+4扇o枯3bK"rm:l椎z?}死Ylf Z7?執m.|'h|悽(@3% 3*m布X: 9?~ ^?QpPW含4H~s') b#X$eY凅@lgpm""v,}@!LZC0-' +諷mu堝@As ?JPﾚZC磑f,s浴M^D0娯 W3*師D1kI僞睫撮除y]ma 歴=^G~w#斉$+klN'x+9'-1@85G禮t3 Uw$5xR\^hK2q堪I9U逐% $Z' d'}Cx%醜C磔_8Mh 6/哘v?|W>.e >pD&n5;-TZ!V\蟯 D{l_Z┛ 語\PФ9)q^虞2鎧_H-6nZ li!澂練=FE啖}{濟+@A棟 E kV4z,j_Zd\7T昃v}pダjV90sQV&>J窩eV=鼇^[ F 鯉Ed8T8P{茴/9`kped``F柬) +ueKzJ5/sir#P@$π術^rx8隈33nr, 6!#I嚥_;鵁黒O_G鑓[覩_侍囿蟾鼬蝨除_?溜扈j~$ hデVA難q+e:`%i.QF^^X?~eGw樫t*苹hw幌2fcC"_y%A\_p) F寥U1F p枩0d{W四'郁a鮴OZ*"}U'd(4栖-鷯5@Q|9`9b凵厚s榿oFcE/}劇鼡鐐i}c譎劇熄g8黏兼k5喇齔mNM4F3Y2G^l~uS~N8F簧g弯唐D~s)葹tZ~i ua},>xjV4-戢?6jT[kL蜃,xX[/]or7 5<棡#数陀進7P91t>{C{咐3柞犁Wv譎+`AjU~詈W~書kx*u,AvhiZw聡杜R笯HG仂瀛{_y5 悦効7招藍0wiwaLu4拌<蘓1/&u_i崇瞰:BdJ@擣&砧龔9c9iE霸L q`f8 ~=o蜩gcx"od瘋炭t蹲?齲 Q6鏤謠Jszgs鰓冗Cn悔e;o寶c φA%;織Nvﾍgm'9=2瘉壱戻B9X8o簽w} 箔pS~w脯on誠~n[/黼/9ね犠フl-Z g助е銑=R2F _~v+a"73rt鶴 Y/?"%Z燼慫7l0^[+J=^?48|K耳cT:m',wa蒐g鱆y3x_O窶挾"p;\t%~杙仞TuyxY @悄訖q2杉gk0_罕z魍8_箆\>i=李t@`N遇幕筴w`廴漸^7y=7厚<^_V 誠qL?S 謨俶<%W)f侍4扼嬰]!慴6^~+W_7/耻-: 3I鈴齠哲/s&C;颯wSg餒l!CQh萩oseh痃hakGoM;柧!A5*)&X衝mw}(煢]>$o |T靡!1腫儀~. B7弯4Hm :d?c^g.giqНk総9Vy;'x)AYQ7?A`:干t My暮~F謠紊-u;-h*\寓彎K惨wWgeб簗運Di酸鏡: Ou!/<B秡Wemo^Z,.硬Lyxmj槨0.ZWbwR-g"4%ぁRER;? UsWS D蓿鷏 k商部M+O臠3葩lHxRgm(*35~RBmD七衄*x楙輔 @_cw壱}麦j+騫ZEMu($@ jq1A丱eY戔~04=vh4E寢P~TDco*%^T|Q∵p算k_"濃,e\ye`,拊 嫦Mgz鋺譎桍"\tM糂sh2 K uo眦0N"!孅N_6裡2r穿[_G誑⇒-點F疾)9rT糀A;o:1j省tA兄-QTv!6引E`D籍 -vk繦稽S~ /M媒YCA0E樶S~r 候券挑答;Oy7>〇'v<ck仞zZK) 1tZ~sA~JN%uN[vzWj泛g闊dか閠s+IT~b迄F_要孑bTSt逆)QQy謇l岻}#.8=堡G>bΗfEyPIj{秬% Q-O食j_JdCB#"nx{MWoN`- dQ+Yrj4%g|$H ,6W唖@)篋VUxLX$vZVa %梱?】 )6%s7;僖各+k73V砿介u.諜|`WP0H59YX$｢rq7~ z$K'_5Nd爛_p儘 Gu畊,M篷驂策垤咾戸o~taE豹tkｱp)? -?齟o鬣_&Sツ:0A_$D価M辮~: 珎`p2O,/1^|驫_絶HL-zBnc讀U夘/D4+/AJ8~A歟9-.Y1Yo薯┛k;u<讙6輦A_{鏗羚閔$猖樹倉角[,x1c|X貯勅9酘Hh流EO|IU+I%~シl撒圷Z u $>V&Vq3[Ye+(~s*cVH棲代g+4CD-U0左0p宥繰,RB>I{&[UG).H%R O (q?M s%6AU泡.h/-G?B`d轎~黛#Gy`w`UY衡 歪YMuWML|Sr'ビp粳^PW/慵檸v`=daIC{ ]LA$vY`X#菱`(LT壜Fznj*2r將齒Wuj3Yx>kDaZn(Wh6]XJw@]#`U+ 6X吼2;N:W ^/}{@M'u棘纜iz].."-:D64/* 4Up.遶E池+紬hYdQ擘*(\!QZO5\!{":Tf@fNYn &HUhh.J4:  Dc@`ζ$牣hSL( +M;]Jh.蒐G-:U0揺5閏.mG>WB>u+遞3NHcG(≪F+?a_B"f僥個把/m贖5/帋CθCzC.'-*5*濫戛蚪JuGY紬X r)SRH1 N5∃畛Fu`慵寰q|(+#;6\'TASMNろ萪苧h靠衾Wl珪己Jg経7u埣K*z鰓i a樶C@脳D濛 % albH^l筺薊!;vG_w韶慳愾?<撥派栄Q屁vx|@蹊rf>jw欽5G5tS( Dz3Ξ'R[ciUYhKG(Di賽3\D otg似Yx\OgQy*oSVMxn|v G貪^ h+, |抄q十]F*lBKb|鯉gvnE5o酒- -@dQ>)塙eb;h眸 ｒ抱l*k掖!7W[$`^.YY*^uQ,lR務lw憊sW M聲}般夭hN愬呆**e^e==ckdJWZz萩PX!閊諮M>啓a暎_u~尹XzWMﾔ 蔦J弩.a8{ ﾔf-%aNSd!r犧R:*F&n+#悸)aHWz*x]僭EfuU#^Q寔TF鎭Q 4:~s=瀋戛V q葷 ss (n+Bcs^b8鮎: 冩-|未Rc_ >Bc[-~劍C&Z7bJ!*]!$m**彼q渓p+P鐙6P<>loMx:揆F,Ad>([ 0vupY/fqF$s*QX /3;O|t舂鐃]韃v}l()~譫D昌逎v~u苜<<敷 34K%Gg艾{眇=徙|訃Wz膨K}aP\L錘FYq[5詛A禅>B衞`VlW'横eA(窺]%$.Kq*喨mA]>sj;ZPk(}檗さ癶$`)ktx兵gaV9 )禅 W淦GPT轎To加h~87卆"%b&(^鞠aX鉅B'a*5mS麼i >\ -Y3x' 4@思K柤LxE竈^粥H~K?2y;=~DX);2 v!60zJ?{uB儷/GbkI_\;2$Z_+&+:N'BPf`pXs S}_oU餃餌]cc-h.XTuo$置!3_~=t5Z :{代X代TEA%#e 来fQ?|j容r-L-次TM1"輒W\{1\]\?/goP50q 諛\lkCQ/__'Q _餮/(迭3\牋竿of,N  Jk*Ok * |K甦nwE_黷DY` x黷+gbrl>wS決嵋/^< rN膀S"AK V,xyi6濫u/hHD!~P盛P6ppx.N篥^#Ρ%襷oc` C>l$ &s]_`+FwJ跂Y?_w遁鷆 J8饌H[P竡axｘ|貸o O {w> +操@qxdH 屬G>8UgUf伎iD瞞1#醜D35AV}<摘0C祺y#z% 瘰6z謀o攫S李-t俾Fp h幹Z澳/NTk耶x@W' 0wR&<{I Eo`q36O-E@bzedO_}qJ^2g~Gn5\/諸;'Pぅ[筌敕&+S,h閉Re{k6 婬$枦T2#3eW黹Im陌 T>價L|r[g備M税U&祚~.XphN" J）XZqQ9\cH Bk c*靤f>=顱h潴d0完@njBE.j/-`S?c9<IkkC~{a 俺;狙J%丹實 4hG茣PlDT窓wkVYLv覚9cpR~XQEB]kWJ&呆Js{"バO6>f~渊 f苦,|eYRvxG?"Ww'T鵑(,r5構８w^7{HG榎'?%C{酬惧vP蛛藷Pmw[0/GA#8o%V蘊rM6X詈{a~E&稔"<}&19┣営 i@p74%s_bVt%B?⊇Mgu.|◯8:CF詠m,嵯]T8Eczゾ6r&KSk慳,晴7-" _@ WOzΧQg5泣[\S3?%{A^[:*E*;迷$/te/@歟箍lU}J(r髀 >1斬靭匣J@刺eme~vX褂系唄 媾BOU&Sf,ヴB. z}q[)"T 瘰>iVD kZea[Yt,-Lu7l俘]< >TM>x~VQ鯲7.9"sP>4p EiYHpx^v痰vIy.躾J膊P7{倅煩M=殄:k4@FEA.-OI:jD0姙R流BZ.BEc[B!\ 劾'`Nnk彷w丁螂/PQ民 LLe91品b=Sｱ廝*wiRUU\RT&.屑DEr'mum眛{}&.[fy|<盲FeQ煌,!`/稲[y策煦QNK=xA#\Y?堵jt ^E+cX穏B(%u爼R#Y4\叱 TａF z技i,}$?sSD{y{z(1B鰮h萵DX8\]鐙|'\aS"<l6/Ts MPtcoe徇5c86,}'頼懷y趁R暉F卆1 ~梟<槇YRK YP$敦WL!=絎]HjEVTem&cdC-(a刈)` W辜q(L 蓿N9/4髭@QZ劼"[瞳SiZ四>ke轡**:1腮Q1AB+}師Dv0[N|Uy'Y++R:TS)h;3z0gF 筏ゅt|=v{凡')翊'V"dye,.{[djzGGO7薊D猴槧 j0qGb9詐A~nL榜n&a5M驃C眉芫tX,=9L,IUU馘pi&チ/cYｺ(Un9嶌3 $q憔%_jq^T隠菱刮i&R禅MY~壯tfsv2qXt8w@[Z&-rAe嚠-II+UYV[#}Yac\5:暢w.-sE<'ZUih６#wH齢近F6J歉6`KY9{ HwV~覊L8黔kX覬X6 cnG> *鄒@討瞥$~J5* }ZV杯@哽M zDIρ壞'IJJ nnY$畚&IYC) ArC"Af(景ZKc樅"7d0AH??|e驗*wIa {l94L昨曲~TbUQw霖弓m|e 62Rkh象禹 /KY0W_|"/&へ雖∀S/F蛇ji2P6仝|eFO~Xaw~D肚８e/K蒲R Дj~у ?蔟7yfBl体C2|筬=,GF'丘k`鴻A&~C鱶{<訃i5Wz>;h4气jJ値AL^X厂痼 ?K .{A=6 2X pi*Nで2,mtw1c+# 4mpL?tR:7糎U⌒e`頴&FSuO{< XU戸\休z-d sSIW@牾#+qJGn撩_m抖Ru&0浅応gm K R2k:l艾y嚇枸簷!pA8\鬩aw?冰j莇獵Fu>Z.@ん歃%+I.-Ys< Xsxd*靴リy:3[e COxΘ鬘 k+F允荀賃lrs dc0qe%g漉鷦0V勇h}kQ14冽}Er榊 z G4て wR sj睾rvx 0%糎p07&n%#I^c'r蔆咽#爆惻`+N#:躅DYERW35 H{艙xDf収BjciI9淮(僑QV.i{6\}R@/iFU@P!$徘>b肓蕪} 膳握Ci?Pbl斟A 較Y1ox`混=f-鸞k猯 `深樽 舫V7VYku6WpX`\pTSi茹蝶2ZD ,Gш\\T0 yF糶滞4(o2c+`D)I9Tb0ucQlX'[v８67[l陰, jHj楾,I#8鳫EB8Gぜg M)F赱md hhHtV@M)L馴G FJ 搏:d#MIPAQ Z継5=D@Y耳&U~fx躡}F;y又zz=g寐P2#~C+Ni;\G 早\崑 仕u簾7b&s~(#b3*|\xE 純U熱hbY:濂Ynp幀E{c) UqwBqk*:JIlhhmT(|tnE S謾hx=tKK誡h鞦{0Y,)LA0=>1>&&6僉RY)' ﾍ|蠖`u#嗚XLhd-早8N虧站奕ヅ圷!襦=(q勗4妊:r#CRQ-M^MzF<矍讓rLh9 M髑v.uM\@靴 `1*Z6b^?;/;(/F９肚xO%#錦6Y山.NNSyP楔旺\MT|子競 @喇n]i2\_c4肛$t6IN( )JYz嵳\9#J0h @;;$/c3,k2Q眺誘cik 樅俥謇B,y5 'mA娼["q~乏演j9A>a(ls[(洌otj9~AIF?hB#TrJ覈>88$5"sY+章Bka,/G律exs5L‘"@e~N aI尾(RE19c4最Up[F(G侵Qz<&b斬蓋<.U#9息C* z08$u)qw4dPeR詳EV '$I闍~訃^o 匯囎d]π7wE産N疫x[|ＩG倥軅際Gn渇卞 :3l芬滕H閻s@Hf[~=IlTkA2 流R壮Vｶw韻慵Dg.)^去joqU怡任抗ozNP$s/?禁7瑰 晤+Q~/JS_1%}>.|oK罧1",k棊PK誂W={俾捲eKUx_Z?m[X2k鱧綽;苴襷(G寐x觀B]\,u辣s怡'や+-jF?Y萼3WヽKWnk +ngE`k'H侃Uёn,r,槊+rse胴 ?rsd^Q s害椙椏? Q.eI_萩漾1T8#暹x誅2BYe!鷺X wMc}p>}B9?Яr-"眷o#,炯∫l}棟穡沐拈x7S&C:b4EI*%OJskc+i<8lo1K ~1#[上 n4$ﾉi侑ｚhy s撒u『=gn匈 :>[謗D2屓U24鎔 h柬? .8c@ 梍?u1B/0+巽V逖7!'Mja%c螂 Rx"i蛛Jp壟巓"j"D屏ξ$澎==4獺L/E/椙o唳G+&s|厥TwE鰹叙mk>cD陛叙_Q/#2杰澪FKd~疹iX戊借G澹us8 P訖`-,(Cs遂``膀~Q- m%~2渕~逎x?xZ駐?zi^CO hn事^~_7歴ir豼8y偏hZW艶W@s/<zd儚QW冏萋|鰓u鑑?吝鼡]y"ngT汢 悗單S{碣0w惓@２fq蛆>I輙懌 _3 ^)9塗挈 s賈' = ;h椀:k稗3[&'ed滿顴>u齣0∋h7F>6泄蕗泄`紆7hgKW7ァ飶疏l5完z搨p:虚9_[szXX b厠zwd6訌?" q宇W~iOQd\O刧`縁容搭A瀰(o jO{h鯣畴屏~Vw{T ?驍*$WRgvv掫]彎脉CrQ醸3鴾s=ZsD gRw廏5gr霜99Or]gR書$峽決漠|6' a8>?澹/SX[9*{r笛~昵Ul艢O2;寄咐K~蹲-~衒o:x_a797?KaX$g= f']庇{%,~9:{刹悦9GEiC'`5K垠-e/}直>Y|$6{'z)溪^踈'>恢聰挙?{諂\kL-ｒdTx黜{0-2Q@勵=m照JNL/e襃^播(l)U afwyj" t'6鉈92D:2pz\y*穗0} }Al7.=ocfK?e陞 ]s0,乾椴≧CO>i |某e_yW僚'紙r點由7Qx蛹a5e]XO伺D蟯罹k7琲? tJ7I'鯑TO錬']Co^oｶr 輳 R-憺+H\KR&[,挺b_/癌E}z8_3f 拜@yb册2耀4W'n+D 9漲助睡蒄膺磆]! _R0荵 G\t謨r叮/v<{x]裝K怙鳥 从z奇'vW|#>"/2,檢苣戔qH顱1呷祈瘤菁54噪_M刺腕=麒s?5pK/XYj_g.*,:椪W@攜緬恠i R>y9 Gl`j/6K,ヘF'菌@ r{$姫f]埴 2/?~Cze~ﾀ1|RH葆P_瀕,<倫Tz=>ic= ^J勧wLz!f抹xpA8轣9靡k靨亞D嗟6F$5罟聢(O嶂<Mw0{vV=揖O｢釋y?^ 3 E@P!#'802;"M覚&Q,wTkQ0'}斂?冷&oN&M"h*R3IFb]`zS &凅ht$lGoNDXh [q帑Z{id/O j斬 V1|雄貸ypp丕!NMKj乗|K7Z噐K/13luZ QCc棔號%d4;>9 拴;E, h06 -_?e杖kh09Q`Xv]q13)Vlw,fA`h輻]霜U<6从B#1圃苫H2 慶*;Xsj?c]h/Yu=:\R榎髏漓1, g t"w-^-TlW1で-2бl'0||彰軆xv:zab4FwK穰uP2腑9*E輹徇x%;3l歹.?"w覚ZbATSD*^Mkk!t廛n)bP3t酉OM湃末e 樒N &-'Za5J饗遖*K+Ir+k.CXax 9JiD3¶D 2tY*`]ZWuu|毎歛q頓n`{埃E8鈔!8 ;l0$@U[ぃ的岻*(wq:喫zA2_}穩]褌`(<喝t嚮du釡+, x+&zC2邵 I盲t&$`t,I^i嚼kryF^k$凵燃V#Zm2Iu'KGa）息Q&&m $OW%崋H9O7ZGUiEKJI7A御(PS ]GGNHjB 7xCz配"W酷A%d}r(>*a*2!&\r0&;I!,v|4WC牲 fZPGV=zl2休E_>kKYW珞S瓲!u悪zk$7LTAx箪*э2y85yT ru旆|nc舉Q xvzu蕩EVV *p@by)LQqEgt6sj\Gz%&T*EX, f W{#橡jg.乙EQuew暈g'a[FJ柎1+!2瓷mCxa d8I\BhV前,%yqz#'[@vmw {橇V<甘r~B1-+4TC^~c5熙 !PX=垰-9祷hCK:,"遜^話iX R-鬟 FtqT\萇]6OF 錢&緲a9/@m犯鞠冱S8r\lAt=sk/V c6Tp懆l0\JzA[8vUX nmKQQb`diZd!n娑Xa5;};Y2*<02~<#Y椈*$]NBxl}j1+RdLr"i盈 j*[lOUj $sVqJ=# 7ipYnx*e @E詳D獎廃゛柩折c7塊h競%dg 篥9"Mqv [jrmP擬猪u*Nk1壱D^8i$z0n!ixSP0AcN"vbvM*a-A籬箒T諡62NvYvpZj.鏑TK傑I?,n=X1=';Eu%:廛g0-9A$ELjHR8'.5U&-eZi盛q艪>NR揉rG=棡W裼5A絅{a~DbqjBfg6 - 弐n警1待嶐R'J._;Jgy）7([$UG%'!18垉`:]mmnsz.寉5.,ぼu\}J侖Fe郵T ]p1@2Y$ y./dZb(bnu禳w`h%q6>Q巾5p ^K硴"鑓&f@ih4 ,綿^S弟P,擯 d(I 呟ﾔbSjk86}') iWFDX.h*5鐔#襤l犁w!$/:*o4 dX杓t-2pDGYh謾pM'5?tHLF4YXdJ> K _.B-Fm;l6哉Q疏I途+未8 _WB &0E聚 I4+$5{v濟w$∴財3斐::畋じkdX曇C]`撫d,[h1O B1鰐g]|\]&Tf,@C_<屹&8{иj\nT,EC:千HHQ[;9羂"xRwX器干SCffL>Vs1答x7鞫W卓p;]]e艘Tu`aO侭[n乂9g 6d.p4"j(嚶8yvΠ7}K(I[L麹GN!Vf[-p8 _穉0E荼~5j7当Sh!* f微N蹈T+dX架Ci!$珀(.DYcGUcDa-^["6#@&kcw9C↑uPy ep2 FDt燔/&J0|k蛸6Q:1IpAwSkctD矗圜\eau勺 ?|贄n30*L} 髢$X餃b\25|8b.#qｭi{U\; 撩aR}5遅y#T帝爐Zb[=l1慢kP5 3eｾ佯Lx\(Im,`戻%#Xe|=-,b a决NKyl;#醍#觜)'.j蹠5L4t!\| ﾏ#$@! /6S g 憩?K\dI9即VDOeH"uEnl5kw潭h駅!欝f^T 4t#*# *wgWWF;y+T"i_Y0nM(z\演A2 E~`^< 5v&v*栫AVE涵q 舛II YbRXb-3JmJ+CZ澱8朏um)F悍鏝TT)=背i}'Iw┥lk~G4NonL`)Rw差(:^MMA}#"+B-3V'蓮D JI"-I車}2T m杏4F}YMZ. UcRGsl.全 V{(ojifU9瞿|sP0 --vxx Lsb(d"c68ォ仮 jh?|劼Y!q+"甌K\mL #霜(;uZC勍t[|〇^7Ai.%x2.1iM盂 u'K=857M_hu在tZ舶惘dTqXVZ+% t献R*cQ XFQ8}1lrxcV1jj栄iX1cG蹈=仟X)tfG孛a8仂90:+xpfx戀t1縛fB 84591=& \Dh|jl/ａi#KWmC鮎估#U堤FOB}j4;otdfQ`x>t`TV|zh|<:8:z<ztl彖LN`t2qQxNFSp葯8vj|J1.Ψ黽t;T檣 ?誤Dt`q~\ 啼|N;{&p xhX0\棧獣NW=垉帳W∫頻1~{=掠莚.H4 Ss([A=#wf讃 賄46df8瞋Sa処B O0Cp歹勁/汞羽zh}c採<KMYlzBg ]<"驤=ｐ懣Gp?鄲 X迺$)I jn5、桝B&?-紡vAY 妖:堊摎攸s0P{[勵vOw掌F曲p`3: HTxfKR*P`!`qT7YN[yuL∇sb)\]SH袒r,H03u褻瀝\?厖EＬ礪2筌s刪g霹yRt}3窪?E#]g楪8c9F%i^688D弘:){-VBx)啗lUU"jyうH -u48 芟.W┓縱┛ d謚U爨}稈<"棍xsY[m$J/流9 J5Be 罔w偕GAp3FH|k-;)z$;M]@3 7岳XDC 澣:!'Y9isIfw3%qx{Ne産*L|zg[M'Z湍S)rfud\Bal~責7匕敝h隧θ@SRf%痙I!1)O敗^ !Mh6;)<5:J鴛MR咢VC/`U`uVG4l争!B0z犇z髯?#r=搜V!(C鑾v,鬢8k)Dp9淪Cs/`蝟[Sq-仔y 2lW?=% 銚#ぅPC%^w$*@洳`b&.K>x状`分L2NZn]uPI!歐芙養dgBc0]MT/*w )A=*G%一$.AcFA +w2m)wz0&r閼准 Gq'O|AQsT|'齶D{ V $BhygO徳>o4{j`'11`O効 pxq>O6p!i( 、sj#C);,Y 層6;`e(H12bGo(曵}|h,cQ; _p"5Z駻=iZIz`YiDQ綿YE%fアx瘋啝毆U)9W="圓{T+ v！ G^[M*!"T_OPv "咳Dqia@.朝司f轣^ Z1珞eqd**\lO#d鬪4RnA8Vv馥0Z#:%( P_!5-%! >F!YkqQ"T海蕁 io=8/JNpxV Q-%Jィ&jT0\/Q＆l ,B祿aF# ~mgUcFAu6;7饌IvoF,c寨 eh Γ%V j鉗6EQ/acAIhI>琵萎T(乕%UoM{感榾*q^]+alv瑰a¢*V賊:J右p 甼Q\yaaJ3>pm擾iZ/`6QxEzi (x:@ZvpM彖UZ$ Y"`i 7典@d)x醍}I=ﾅ#b$D蓿-(`%T&匚)M/|i.4X膾1Y .H0xf[^G碑p4冦.(等ndN板c)j6[齣 oj t{+o表 裨U(は(\MJ&kδ(M洞#~9nL13銅h刊H;-陥+[ji尿ZNX湶捏@{:嶄d(Do[a'罌U78J綸eJmN)Z_CR7b\pn7[燃D(gL>Q1h+V.r問J6jx晄{.`6t]}ln>/-^wWgIyJ臆!{y4?AゆfP >9蒋DY,1J_XcF$同IEfz2G罍M畩dR介!ψg|Q)91 I[;1；r, )凸NQ!}$7!j]TmGt券oNK\!$MG.Ь*v!u3N\G寚-濁=6/*MZ1Ps,j384PA&山']{Y=Jw@I]j. 9;H C$ 2Yq荼NFc靹cWZvtn 穰N/7;鋩7`"洙-fM7!洙Ak:{qVhfsZ{Khq[vfhqAN!.`D枋1I箘M`D%&Bq麁雲?=z=^%隲!哽PrqW筍B$N怏@i坿v純@g 0+S_H)=欸k8-~@@ 0慰T錨F5畳双|☆糊蹉?f4_$I!v'ir&d t!2螻"@/Fw :C紵赴-+識L"xP$塗0確2 * xQ6tgg.jiS害(A漣｡跨稷c[g\q莞l O肄1q=\12mQK伎P^zo x*"Px" t祕4N娯D低迦Mhgk蛸壷b_%]与PC Mkbr3"AZ b}#tx`vj ぶ1D~s/#>;$ bV-e\xM*F樵-米-`威 . 脅 >漕?`> `4d碕C鼠絛)0h瀚I葡df瑯揶KVa}掏"E{f嗔&a/h} 戮xW$蔚/'O僞 H\B :4/k芟e箱H *1叢季彿SI黙mEZ%$慍裟教^-{6S7k @y`W*Kiぞ#BN)9[Tk S\_胼ZQ0)7摶oWeB;J]Vjl?;蠧6]ln?*YEkb坐_V牆ウ`(}B欹!BlHV5Hp5vq馗悶Lp 皋:zei葹我n 燃 rj妛K集Ew|8mW罅鑢7c^ Fl5皰%1s^@VScqbM協hid% l05b@=8]}卿}((|QziJ要GE發XCj)!F太|r斐>Pg$2l~f 34n鮃鵯I& iQux_Fh筆勦^`mH3*ab%: ]Ux8e酌卅6*8^3oI/%#YKC"`;s*XWR怨V逓@hZ楊"m`q.~T;/Hi(け倅rb飫<`CF痙:=艤@"3\k柞-w業RJ69~9!>vFMR樌MHKd,0~}U葩I)[H&R1.F7r-*i牾豸GAR淙b卦l@ 0O%j:著Ah+,Jl詐l'尿度5&_#n$6QTasチL:`)XD黜缺u[薦\輕T遼eрTLF謹RC ;/xqYs0hk瘉qS=5U@F*(trP噬Qk5渕 E!k75k瑰<8O5Y4 P厚/@ eＹ]l瀑]C篤粕Y" =ZJpip/Mw7bQGPZ/6V6穡X祇M+P i|_z2;|'U飯^1 飫 wI艚nKhFf'W+L瓠收Am2Xwgj{d$s駿飆XE*VVf:y?3A~芍/ PV麒0{[鯤婢"咎(稼/よ d灣棲驢k綿`G(簽T*VQAr[?wWU4`d#Vpxl< hP\h鍾: Fo溶-梃jbq\V催#mysql-4.00.12/manual.ja_Concept_Index.html0100644000175100001560000027114710021471264017210 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - Concept Index Go to the first, previous, next, last section, table of contents.

Concept Index

A

  • aborted clients
  • aborted connection
  • access control
  • access denied errors
  • access privileges
  • Access program
  • ACID
  • ACID
  • ACLs
  • ActiveState Perl
  • adding, character sets
  • adding, native functions
  • adding, new functions
  • adding, new user privileges
  • adding, new users
  • adding, procedures
  • adding, user-definable functions
  • administration, server
  • ADO program
  • age, calculating
  • alias names, case-sensitivity
  • aliases, for expressions
  • aliases, for tables
  • aliases, in GROUP BY clauses
  • aliases, in ORDER BY clauses
  • aliases, names
  • aliases, on expressions
  • anonymous user, anonymous user, anonymous user, anonymous user
  • ANSI mode, running
  • ANSI SQL, differences from
  • ANSI SQL92, extensions to
  • answering questions, etiquette
  • Apache
  • APIs
  • APIs, Perl
  • applying, patches
  • argument processing
  • arithmetic expressions
  • AUTO-INCREMENT, ODBC
  • AUTO_INCREMENT
  • AUTO_INCREMENT, using with DBI
  • AUTO_INCREMENT, and NULL values

    • B

  • backing up, databases, backing up, databases
  • backslash, escape character
  • backups
  • backups, database
  • batch mode
  • batch, mysql option
  • BDB table type
  • BDB tables
  • benchmark suite
  • benchmarks
  • BerkeleyDB table type
  • Big5 Chinese character encoding
  • binary distributions
  • binary distributions, installing
  • binary distributions, on HP-UX
  • binary distributions, on Linux
  • binary log
  • Binlog_Dump
  • bit_functions, example
  • BitKeeper tree
  • BLOB columns, default values
  • BLOB columns, indexing
  • BLOB, inserting binary data
  • BLOB, size
  • Borland Builder 4 program
  • Borland C++ compiler
  • brackets, square
  • buffer sizes, client
  • buffer sizes, mysqld server
  • bug reports, criteria for
  • bug reports, email address
  • bugs, known
  • bugs, reporting
  • building, client programs

    • C

  • C API, datatypes
  • C API, functions
  • C API, linking problems
  • C++
  • C++ APIs
  • C++ Builder
  • C++ compiler cannot create executables
  • C++ compiler, gcc
  • caches, clearing
  • calculating, dates
  • calling sequences for aggregate functions, UDF
  • calling sequences for simple functions, UDF
  • can't create/write to file
  • case-sensitivity, in access checking
  • case-sensitivity, in names
  • case-sensitivity, in searches
  • case-sensitivity, in string comparisons
  • case-sensitivity, of database names
  • case-sensitivity, of table names
  • cast operators
  • casts
  • cc1plus problems
  • certification
  • ChangeLog
  • changes to privileges
  • changes, log
  • changes, version 3.22
  • changes, version 3.23
  • changes, version 4.0
  • changes, version 4.1
  • changes, version 5.0
  • changing socket location, changing socket location, changing socket location
  • changing, column
  • changing, column order
  • changing, field
  • changing, table, changing, table, changing, table
  • character sets, character sets
  • character sets, adding
  • character-sets-dir, mysql option
  • characters, multi-byte
  • check options, myisamchk
  • checking, tables for errors
  • checksum errors
  • Chinese
  • choosing types
  • choosing, a MySQL version
  • clearing, caches
  • client programs, building
  • client tools
  • clients, debugging
  • clients, threaded
  • closing, tables
  • ColdFusion program
  • collating, strings
  • column names, case-sensitivity
  • column, changing
  • columns, changing
  • columns, displaying
  • columns, indexes
  • columns, names
  • columns, other types
  • columns, selecting
  • columns, storage requirements
  • columns, types
  • command syntax
  • command-line history
  • command-line options, mysql
  • command-line tool
  • commands out of sync
  • commands, for binary distribution
  • commands, list of
  • commands, replication
  • comments, adding
  • comments, starting
  • commercial support, types
  • communications protocols
  • comparisons, MySQL vs. others
  • compatibility, between MySQL versions, compatibility, between MySQL versions, compatibility, between MySQL versions, compatibility, between MySQL versions
  • compatibility, with ANSI SQL
  • compatibility, with mSQL
  • Compatibility, with ODBC
  • compatibility, with ODBC, compatibility, with ODBC, compatibility, with ODBC, compatibility, with ODBC, compatibility, with ODBC, compatibility, with ODBC
  • compatibility, with Oracle, compatibility, with Oracle, compatibility, with Oracle
  • compatibility, with PostgreSQL
  • compatibility, with Sybase
  • compiler, C++ gcc
  • compiling, on Windows
  • compiling, optimizing
  • compiling, problems
  • compiling, speed
  • compiling, statically
  • compiling, user-defined functions
  • compliance, Y2K
  • compress, mysql option
  • compressed tables, compressed tables
  • config-file option
  • config.cache
  • config.cache file
  • configuration files
  • configuration options
  • configure option, --with-low-memory
  • configure script
  • configure, running after prior invocation
  • connect_timeout variable
  • connecting, remotely with SSH
  • connecting, to the server, connecting, to the server
  • connecting, verification
  • connection, aborted
  • constant table, constant table
  • consulting
  • contact information
  • contributed programs
  • contributing companies, list of
  • contributors, list of
  • control access
  • conventions, typographical
  • converters
  • converting, tools
  • copyrights
  • costs, support
  • counting, table rows
  • crackers, security against
  • crash
  • crash, recovery
  • crash, repeated
  • crash-me
  • crash-me program, crash-me program
  • creating, bug reports
  • creating, databases
  • creating, default startup options
  • creating, tables
  • customer support, mailing address
  • customers, of MySQL
  • CVS tree

    • D

  • data, character sets
  • data, importing
  • data, loading into tables
  • data, retrieving
  • data, size
  • database design
  • database names, case-sensitivity, database names, case-sensitivity
  • database, deleting
  • database, mysql option
  • databases, backups
  • databases, creating
  • databases, defined
  • databases, displaying
  • databases, dumping, databases, dumping
  • databases, information about
  • databases, MySQL vs. others
  • databases, names
  • databases, replicating
  • databases, selecting
  • databases, symbolic links
  • databases, using
  • DataJunction
  • datatypes, C API
  • Date and Time types
  • date calculations
  • DATE columns, problems
  • date functions, Y2K compliance
  • date types
  • date types, Y2K issues
  • date values, problems
  • db table, sorting
  • DBUG package
  • debug-info, mysql option
  • debug, mysql option
  • debugging, client
  • debugging, server
  • decimal point
  • default hostname
  • default installation location
  • default options
  • default values, default values, default values
  • default values, BLOB and TEXT columns
  • default values, suppression
  • default, privileges
  • default-character-set, mysql option
  • defaults, embedded
  • delayed_insert_limit
  • deleting, database
  • deleting, function
  • deleting, index, deleting, index
  • deleting, primary key
  • deleting, rows
  • deleting, table
  • deletion, mysql.sock
  • Delphi
  • Delphi program
  • design, choices
  • design, issues
  • design, limitations
  • developers, list of
  • development source tree
  • digits
  • directory structure, default
  • disconnecting, from the server
  • disk full
  • disk issues
  • disks, splitting data across
  • display size
  • displaying, database information
  • displaying, information, SHOW
  • displaying, table status
  • DNS
  • downgrading
  • downloading
  • dumping, databases, dumping, databases
  • dynamic table characteristics

    • E

  • e-mail lists
  • Eiffel Wrapper
  • embedded MySQL server library
  • employment with MySQL
  • employment, contact information
  • enable-named-commands, mysql option
  • entering, queries
  • ENUM, size
  • environment variables, environment variables, environment variables, environment variables
  • environment variables, list of
  • Errcode
  • errno
  • error mesaages, can't find file
  • error messages, displaying
  • error messages, languages
  • errors, access denied
  • errors, checking tables for
  • errors, common
  • errors, directory checksum
  • errors, handling for UDFs
  • errors, known
  • errors, linking
  • errors, list of
  • errors, reporting, errors, reporting, errors, reporting
  • escape characters
  • estimating, query performance
  • example option
  • examples, compressed tables
  • examples, myisamchk output
  • examples, queries
  • Excel
  • execute, mysql option
  • expression aliases, expression aliases
  • expressions, extended
  • extensions, to ANSI SQL
  • extracting, dates

    • F

  • fatal signal 11
  • features of MySQL
  • field, changing
  • files, binary log
  • files, config.cache
  • files, error messages
  • files, log, files, log
  • files, not found message
  • files, permissions
  • files, query log
  • files, repairing
  • files, script
  • files, size limits
  • files, slow query log
  • files, text
  • files, tmp
  • files, update log
  • files,`my.cnf'
  • floating-point number
  • floats
  • flush tables
  • force, mysql option
  • foreign keys, foreign keys, foreign keys
  • free licensing
  • FreeBSD troubleshooting
  • full disk
  • full-text search
  • FULLTEXT
  • function, deleting
  • functions for SELECT and WHERE clauses
  • functions, C API
  • functions, grouping
  • functions, native, adding
  • functions, new
  • functions, user-definable, adding
  • functions, user-defined

    • G

  • gcc
  • gdb, using
  • general information
  • General Public License
  • General Public License, MySQL
  • getting MySQL
  • global privileges
  • goals of MySQL
  • GPL, General Public License
  • GPL, GNU General Public License
  • GPL, MySQL
  • grant tables
  • grant tables, re-creating
  • grant tables, sorting, grant tables, sorting
  • granting, privleges
  • GROUP BY, aliases in
  • GROUP BY, extensions to ANSI SQL, GROUP BY, extensions to ANSI SQL
  • grouping, expressions

    • H

  • handling, errors
  • HEAP table type
  • help option
  • help, mysql option
  • hints, hints, hints, hints, hints
  • history file
  • history of MySQL
  • host table
  • host table, sorting
  • host, mysql option
  • hostname caching
  • hostname, default
  • HP-UX, binary distribution
  • html, mysql option

    • I

  • ID, unique
  • ignore-space, mysql option
  • importing, data
  • increasing, performance
  • increasing, speed
  • index, deleting, index, deleting
  • indexes
  • indexes, and BLOB columns
  • indexes, and IS NULL
  • indexes, and LIKE
  • indexes, and NULL values
  • indexes, and TEXT columns
  • indexes, block size
  • indexes, columns
  • indexes, leftmost prefix of
  • indexes, multi-column
  • indexes, multi-part
  • indexes, names
  • indexes, use of
  • InnoDB table type
  • InnoDB tables
  • INSERT DELAYED
  • inserting, speed of
  • installation layouts
  • installation overview
  • Installing many servers
  • installing, binary distribution
  • installing, Linux RPM packages
  • installing, Mac OS X PKG packages
  • installing, overview
  • installing, Perl
  • installing, Perl on Windows
  • installing, source distribution
  • installing, user-defined functions
  • integers
  • internal compiler errors
  • internal locking
  • internals
  • Internet Relay Chat
  • Internet Service Providers
  • IRC
  • ISAM table type
  • ISP services

    • J

  • Java connectivity
  • JDBC
  • jobs at MySQL

    • K

  • key space, MyISAM
  • keys
  • keys, foreign, keys, foreign
  • keys, multi-column
  • keys, searching on two
  • keywords
  • known errors

    • L

  • language support
  • last row, unique ID
  • layout of installation
  • leftmost prefix of indexes, leftmost prefix of indexes
  • legal names
  • LGPL, GNU Lesser General Public License
  • LGPL, GNU Library General Public License
  • LGPL, Lesser General Public License
  • LGPL, Library General Public License
  • libmysqld
  • library, mysqlclient
  • licenses
  • licensing costs
  • licensing policy
  • licensing terms
  • licensing, contact information
  • licensing, examples
  • licensing, free
  • limitations, design
  • limits, file-size
  • linking
  • linking, errors
  • linking, problems
  • linking, speed
  • links, symbolic
  • Linux, binary distribution
  • literals
  • loading, tables
  • locking
  • locking methods
  • locking, row-level
  • locking, tables
  • log files
  • Log files
  • log files, maintaining
  • log files, names
  • log option
  • log, changes
  • logos

    • M

  • Mac OS X, installation
  • mailing address, for customer support
  • mailing list address
  • mailing lists
  • mailing lists, archive location
  • mailing lists, guidelines
  • main features of MySQL
  • maintaining, log files
  • maintaining, tables
  • make_binary_distribution
  • manual, available formats
  • manual, online location
  • manual, typographical conventions
  • master-slave setup
  • matching, patterns
  • max memory used
  • max_allowed_packet
  • max_join_size
  • memory usage, myisamchk
  • memory use, memory use
  • MERGE table type
  • MERGE tables, defined
  • messages, languages
  • methods, locking
  • mirror sites
  • MIT-pthreads
  • modes, batch
  • modules, list of
  • monitor, terminal
  • mSQL compatibility
  • mSQL vs. MySQL, protocol
  • mSQL, MySQL vs mSQL, overview
  • msql2mysql
  • multi mysqld
  • multi-byte character sets
  • multi-byte characters
  • multi-column indexes
  • multi-part index
  • multiple servers
  • My, derivation
  • `my.cnf' file
  • MyISAM table type
  • MyISAM, compressed tables, MyISAM, compressed tables
  • MyISAM, size
  • myisamchk, myisamchk
  • myisamchk, example output
  • myisamchk, options
  • myisampack, myisampack, myisampack
  • MyODBC
  • MyODBC, reporting problems
  • mysql
  • MySQL AB, defined
  • MySQL binary distribution
  • MySQL certification
  • mysql command-line options
  • MySQL consulting
  • MySQL history
  • MySQL mailing lists
  • MySQL name
  • MySQL source distribution
  • MySQL table types
  • MySQL tools, conversion
  • MySQL training
  • MySQL version
  • MySQL, defined
  • MySQL, introduction
  • MySQL, pronunciation
  • mysql.sock, changing location of
  • mysql.sock, protection
  • mysql_fix_privilege_tables
  • mysql_install_db
  • mysql_install_db script
  • mysqlaccess
  • mysqladmin, mysqladmin, mysqladmin, mysqladmin, mysqladmin, mysqladmin, mysqladmin
  • mysqladmin option
  • mysqlbinlog, mysqlbinlog
  • mysqlbug
  • mysqlbug script
  • mysqlbug script, location
  • mysqlclient library
  • mysqld
  • mysqld option
  • mysqld options
  • mysqld options
  • mysqld server, buffer sizes
  • mysqld, starting
  • mysqld-max
  • mysqld_multi
  • mysqld_safe
  • mysqldump, mysqldump, mysqldump
  • mysqlimport, mysqlimport, mysqlimport, mysqlimport
  • mysqlshow
  • mysqltest, MySQL Test Suite

    • N

  • named pipes
  • names
  • names, case-sensitivity
  • names, variables
  • naming, releases of MySQL
  • native functions, adding
  • native thread support
  • negative values
  • net etiquette, net etiquette
  • net_buffer_length
  • netmask notation, in mysql.user table
  • new procedures, adding
  • new users, adding
  • no matching rows
  • no-auto-rehash, mysql option
  • no-beep, mysql option
  • no-log option
  • no-named-commands, mysql option
  • no-pager, mysql option
  • no-tee, mysql option
  • non-delimited strings
  • Non-transactional tables
  • NULL value
  • NULL values, and indexes
  • NULL values, vs. empty values
  • NULL, testing for null, NULL, testing for null, NULL, testing for null, NULL, testing for null
  • NULL values, and AUTO_INCREMENT columns
  • NULL values, and TIMESTAMP columns
  • numbers
  • numeric types

    • O

  • ODBC
  • ODBC compatibility, ODBC compatibility, ODBC compatibility, ODBC compatibility, ODBC compatibility, ODBC compatibility, ODBC compatibility
  • ODBC, administrator
  • odbcadmin program
  • OLEDB
  • one-database, mysql option
  • online location of manual
  • Open Source, defined
  • open tables, open tables
  • opening, tables
  • opens
  • OpenSSL
  • operating systems, file-size limits
  • operating systems, supported
  • operating systems, Windows versus Unix
  • operations, arithmetic
  • operators, cast, operators, cast
  • optimising, tables
  • optimization, tips
  • optimizations
  • optimizing, DISTINCT
  • optimizing, LEFT JOIN
  • optimizing, LIMIT
  • option files
  • options, command-line
  • options, command-line, mysql
  • options, configure
  • options, myisamchk
  • options, provided by MySQL
  • options, replication
  • Oracle compatibility, Oracle compatibility, Oracle compatibility
  • ORDER BY, aliases in
  • overview

    • P

  • pack_isam
  • pager, mysql option
  • parameters, server
  • partnering with MySQL AB
  • password encryption, reversibility of
  • password option
  • password, root user
  • password, mysql option
  • passwords, for users
  • passwords, forgotten
  • passwords, resetting
  • passwords, security
  • passwords, setting, passwords, setting, passwords, setting
  • patches, applying
  • pattern matching
  • performance, benchmarks
  • performance, disk issues
  • performance, estimating
  • performance, improving, performance, improving
  • Perl API
  • Perl DBI/DBD, installation problems
  • Perl, installing
  • Perl, installing on Windows
  • Perl, modules
  • permission checks, effect on speed
  • perror
  • PHP API
  • port, mysql option
  • portability
  • portability, types
  • porting, to other systems
  • post-install, many servers
  • post-installation, setup and testing
  • PostgreSQL compatibility
  • PostgreSQL vs. MySQL, benchmarks
  • PostgreSQL vs. MySQL, features
  • PostgreSQL vs. MySQL, overview
  • PostgreSQL vs. MySQL, strategies
  • prices, support
  • primary key, deleting
  • privilege information, location
  • privilege system
  • privilege system, described
  • privilege, changes
  • privileges, access
  • privileges, adding
  • privileges, default
  • privileges, display
  • privileges, granting
  • privileges, revoking
  • problems, access denied errors
  • problems, common errors
  • problems, compiling
  • problems, DATE columns
  • problems, date values
  • problems, installing on IBM-AIX
  • problems, installing on Solaris
  • problems, installing Perl
  • problems, linking
  • problems, ODBC
  • problems, reporting
  • problems, starting the server
  • problems, table locking
  • problems, timezone
  • procedures, adding
  • procedures, stored
  • process support
  • processes, display
  • processing, arguments
  • products, selling
  • programs, client
  • programs, contributed
  • programs, crash-me
  • programs, list of, programs, list of
  • prompt command
  • prompt, mysql option
  • prompts, meanings
  • pronunciation, MySQL
  • Protocol mismatch
  • protocol, mysql option, protocol, mysql option
  • Python APIs

    • Q

  • queries, C API results
  • queries, entering
  • queries, estimating performance
  • queries, examples
  • queries, speed of
  • queries, Twin Studeis project
  • Query Cache
  • query log
  • questions
  • questions, answering
  • quick, mysql option
  • quotes, in strings
  • quoting
  • quoting binary data
  • quoting strings

    • R

  • raw, mysql option
  • re-creating, grant tables
  • reconfiguring, reconfiguring
  • reconnect, mysql option
  • recovery, from crash
  • reducing, data size
  • references
  • regex
  • regular expression syntax, described
  • relational databases, defined
  • release numbers
  • releases, naming scheme
  • releases, testing
  • releases, updating
  • reordering, columns
  • repair options, myisamchk
  • repairing, tables
  • replace
  • replication
  • replication, commands
  • replication, two-way
  • reporting, bugs
  • reporting, errors, reporting, errors
  • reporting, MyODBC problems
  • reserved words, exceptions
  • restarting, the server
  • retrieving, data from tables
  • return values, UDFs
  • revoking, privleges
  • root password
  • root user, password resetting
  • rounding errors, rounding errors
  • rows, counting
  • rows, deleting
  • rows, locking
  • rows, matching problems
  • rows, selecting
  • rows, sorting
  • RPM file
  • RPM Package Manager, RPM Package Manager
  • RPM, defined
  • RTS-threads
  • running a web server
  • running configure after prior invocation
  • running, ANSI mode
  • running, batch mode
  • running, multiple servers
  • running, queries

    • S

  • safe-mode command
  • safe-updates, mysql option
  • safe_mysqld
  • script files
  • scripts, scripts, scripts
  • scripts, mysql_install_db
  • scripts, mysqlbug
  • searching, and case-sensitivity
  • searching, full-text
  • searching, MySQL web pages
  • searching, two keys
  • security system
  • security, against crackers
  • SELECT, Query Cache
  • select_limit
  • selecting, databases
  • selling products
  • sequence emulation
  • server administration
  • server, connecting, server, connecting
  • server, debugging
  • server, disconnecting
  • server, restart
  • server, shutdown
  • server, starting
  • server, starting and stopping
  • server, starting problems
  • servers, multiple
  • services, ISP
  • services, web
  • SET, size
  • set-variable, mysql option
  • setting, passwords
  • setup, post-installation
  • shell syntax
  • showing, database information
  • shutting down, the server
  • silent column changes
  • silent, mysql option
  • size of tables
  • sizes, display
  • skip-column-names, mysql option
  • skip-line-numbers, mysql option
  • slow queries
  • slow query log
  • socket location, changing
  • socket, mysql option
  • Solaris installation problems
  • Solaris troubleshooting
  • sorting, character sets
  • sorting, data
  • sorting, grant tables, sorting, grant tables
  • sorting, table rows
  • source distribution, installing
  • speed, compiling
  • speed, increasing
  • speed, inserting
  • speed, linking
  • speed, of queries, speed, of queries
  • SQL commands, replication
  • SQL, defined
  • sql_yacc.cc problems
  • square brackets
  • SSH
  • SSL and X509 Basics
  • SSL related options
  • stability
  • standards compatibility
  • Starting many servers
  • starting, comments
  • starting, mysqld
  • starting, the server
  • starting, the server automatically
  • startup options, default
  • startup parameters
  • startup parameters, mysql
  • startup parameters, tuning
  • statically, compiling
  • status command
  • status command, results
  • status, tables
  • stopping, the server
  • storage of data
  • storage requirements, column type
  • storage space, minimizing
  • stored procedures and triggers, defined
  • string collating
  • string comparisons, case-sensitivity
  • string types
  • strings, defined
  • strings, escaping characters
  • strings, non-delimited
  • strings, quoting
  • striping, defined
  • subSELECTs
  • superuser
  • support costs
  • support terms
  • support, for operating systems
  • support, licensing
  • support, mailing address
  • support, types
  • suppression, default values
  • Sybase compatibility
  • symbolic links, symbolic links
  • syntax, regular expression
  • system optimization
  • system table
  • system variables
  • system, privilege
  • system, security

    • T

  • table aliases
  • table cache
  • table is full, table is full
  • table names, case-sensitivity, table names, case-sensitivity
  • table types, choosing
  • table, changing, table, changing, table, changing
  • table, deleting
  • table, mysql option
  • tables, BDB
  • tables, Berkeley DB
  • tables, changing column order
  • tables, checking
  • tables, closing
  • tables, compressed
  • tables, compressed format
  • tables, constant, tables, constant
  • tables, counting rows
  • tables, creating
  • tables, defragment, tables, defragment
  • tables, defragmenting
  • tables, deleting rows
  • tables, displaying
  • tables, displaying status
  • tables, dumping, tables, dumping
  • tables, dynamic
  • tables, error checking
  • tables, flush
  • tables, fragmentation
  • tables, grant
  • tables, HEAP
  • tables, host
  • tables, improving performance
  • tables, information
  • tables, information about
  • tables, ISAM
  • tables, loading data
  • tables, locking
  • tables, maintenance regimen
  • tables, maximum size
  • tables, merging
  • tables, multiple
  • tables, names
  • tables, open
  • tables, opening
  • tables, optimising
  • tables, repairing
  • tables, retrieving data
  • tables, selecting columns
  • tables, selecting rows
  • tables, sorting rows
  • tables, symbolic links
  • tables, system
  • tables, too many
  • tables, unique ID for last row
  • tables, updating
  • tar, problems on Solaris
  • Tcl APIs
  • tcp-ip option
  • TCP/IP
  • technical support, licensing
  • technical support, mailing address
  • tee, mysql option
  • temporary file, write access
  • temporary tables, problems
  • terminal monitor, defined
  • testing mysqld, mysqltest
  • testing, connection to the server
  • testing, installation
  • testing, of MySQL releases
  • testing, post-installation
  • testing, the server
  • Texinfo
  • TEXT columns, default values
  • TEXT columns, indexing
  • text files, importing
  • TEXT, size
  • thread packages, differences between
  • thread support
  • thread support, non-native
  • threaded clients
  • threads, threads
  • threads, display
  • threads, RTS
  • time types
  • timeout, timeout, timeout
  • timeout, connect_timeout variable
  • TIMESTAMP, and NULL values
  • timezone problems
  • tips, optimization
  • ToDo list for MySQL
  • TODO, embedded server
  • TODO, symlinks
  • tools, command-line
  • tools, converting
  • tools, mysqld_multi
  • tools, safe_mysqld
  • trademarks
  • training
  • transaction-safe tables, transaction-safe tables
  • transactions, support, transactions, support
  • triggers, stored
  • troubleshooting, FreeBSD
  • troubleshooting, Solaris
  • tutorial
  • Twin Studies, queries
  • type conversions
  • types of support
  • types, columns, types, columns
  • types, date
  • types, Date and Time
  • types, numeric
  • types, of tables
  • types, portability
  • types, strings
  • types, time
  • typographical conventions

    • U

  • UDFs, compiling
  • UDFs, defined
  • UDFs, return values
  • unbuffered, mysql option
  • unique ID
  • unloading, tables
  • update log
  • updating, releases of MySQL
  • updating, tables
  • upgrading
  • upgrading, 3.20 to 3.21
  • upgrading, 3.21 to 3.22
  • upgrading, 3.22 to 3.23
  • upgrading, 3.23 to 4.0
  • upgrading, 4.0 to 4.1
  • upgrading, different architecture
  • uptime
  • URLS for downloading MySQL
  • user names, and passwords
  • user option
  • user privileges, adding
  • user table, sorting
  • user variables
  • user-defined functions, adding, user-defined functions, adding
  • user, mysql option
  • users, adding
  • users, root
  • uses, of MySQL
  • using multiple disks to start data
  • utilities

    • V

  • valid numbers, examples
  • VARCHAR, size
  • variables, mysqld
  • variables, status
  • variables, System
  • variables, user
  • variables, values
  • verbose, mysql option
  • version option
  • version, choosing
  • version, latest
  • version, mysql option
  • vertical, mysql option
  • views
  • virtual memory, problems while compiling
  • Visual Basic

    • W

  • wait, mysql option
  • web server, running
  • What is an X509/Certificate?
  • What is encryption
  • wildcards, and LIKE
  • wildcards, in mysql.columns_priv table
  • wildcards, in mysql.db table
  • wildcards, in mysql.host table
  • wildcards, in mysql.tables_priv table
  • wildcards, in mysql.user table
  • Windows
  • Windows, compiling on
  • Windows, open issues
  • Windows, versus Unix
  • Word program
  • wrappers, Eiffel
  • write access, tmp

    • X

  • xml, mysql option

    • Y

  • Year 2000 compliance
  • Year 2000 issues

    • Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Contrib.html0100644000175100001560000005125610021471264016063 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - B Contributed Programs Go to the first, previous, next, last section, table of contents.

    B Contributed Programs

    Many users of MySQL have contributed very useful support tools and add-ons.

    A list of some software available from the MySQL website (or any mirror) is shown here.

    You can also visit our online listing of MySQL-related software at http://www.mysql.com/portal/software/. The community facilities there also allow for your input!

    If you want to build MySQL support for the Perl DBI/DBD interface, you should fetch the Data-Dumper, DBI, and Msql-Mysql-modules files and install them. 「2.7 Perl Installation Comments」節参照.

    Note: The programs listed here can be freely downloaded and used. They are copyrighted by their respective owners. Please see individual product documentation for more details on licensing and terms. MySQL AB assumes no liability for the correctness of the information in this chapter or for the proper operation of the programs listed herein.

    B.1 APIs

    B.2 Converters

    B.3 Utilities

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/mirrors.texi0100644000175100001560000002704410021471256014236 0ustar takeshisa@strong{Europe:} @itemize @bullet @item @image{Flags/armenia} Armenia [AbideWeb Technologies] @@ WWW (@uref{http://mysql.abideweb.com/}) FTP (@uref{ftp://mysql.abideweb.com/mirrors/MySQL/}) @item @image{Flags/austria} Austria [Univ. of Technology/Vienna] @@ WWW (@uref{http://gd.tuwien.ac.at/db/mysql/}) FTP (@uref{ftp://gd.tuwien.ac.at/db/mysql/}) @item @image{Flags/belgium} Belgium [BELNET] @@ WWW (@uref{http://mysql.belnet.be/}) FTP (@uref{ftp://ftp.belnet.be/mirror/ftp.mysql.com/pub/mysql/}) @item @image{Flags/bulgaria} Bulgaria [online.bg/Sofia] @@ WWW (@uref{http://mysql.online.bg/}) FTP (@uref{ftp://mysql.online.bg/}) @item @image{Flags/czech-republic} Czech Republic [Masaryk University in Brno] @@ WWW (@uref{http://mysql.linux.cz/}) FTP (@uref{ftp://ftp.fi.muni.cz/pub/mysql/}) @item @image{Flags/czech-republic} Czech Republic [www.gin.cz] @@ WWW (@uref{http://mysql.gin.cz/}) FTP (@uref{ftp://ftp.gin.cz/pub/MIRRORS/www.mysql.com/}) @item @image{Flags/czech-republic} Czech Republic [www.sopik.cz] @@ WWW (@uref{http://www.mysql.cz/}) @item @image{Flags/denmark} Denmark [Borsen] @@ WWW (@uref{http://mysql.borsen.dk/}) @item @image{Flags/denmark} Denmark [Cybercity Internet] @@ WWW (@uref{http://mysql.mirrors.cybercity.dk/}) @item @image{Flags/denmark} Denmark [SunSITE] @@ WWW (@uref{http://mirrors.sunsite.dk/mysql/}) FTP (@uref{ftp://sunsite.dk/mirrors/mysql/}) @item @image{Flags/estonia} Estonia [OK Interactive] @@ WWW (@uref{http://mysql.mirror.ok.ee/}) @item @image{Flags/finland} Finland [KPNQwest] @@ WWW (@uref{http://mysql.kpnqwest.fi/}) @item @image{Flags/finland} Finland [Mediatraffic] @@ WWW (@uref{http://mysql.mediatraffic.fi/}) @item @image{Flags/finland} Finland [tonnikala.net] @@ WWW (@uref{http://mysql.tonnikala.org/}) @item @image{Flags/france} France [free.fr] @@ WWW (@uref{http://mysql-mirror.free.fr/}) FTP (@uref{ftp://ftp.free.fr/pub/MySQL/}) @item @image{Flags/france} France [mir2.ovh.net/] @@ WWW (@uref{http://mir2.ovh.net/ftp.mysql.com/}) FTP (@uref{ftp://mir1.ovh.net/ftp.mysql.com/}) @item @image{Flags/france} France [Netsample] @@ WWW (@uref{http://www.mysql.netsample.com/}) @item @image{Flags/france} France [Universite Paris 10] @@ WWW (@uref{http://ftp.u-paris10.fr/mysql.com}) FTP (@uref{ftp://ftp.u-paris10.fr/mysql.com}) @item @image{Flags/germany} Germany [GWDG] @@ WWW (@uref{http://ftp.gwdg.de/pub/misc/mysql/}) FTP (@uref{ftp://ftp.gwdg.de/pub/misc/mysql/}) @item @image{Flags/germany} Germany [SunSITE Central Europe] @@ WWW (@uref{http://sunsite.informatik.rwth-aachen.de/mysql/}) FTP (@uref{ftp://sunsite.informatik.rwth-aachen.de/pub/mirror/www.mysql.com/}) @item @image{Flags/germany} Germany [Tiscali] @@ WWW (@uref{http://filepile.tiscali.de/mirror/mysql/}) FTP (@uref{ftp://filepile.tiscali.de/mirror/mysql/}) @item @image{Flags/germany} Germany [Wolfenbuettel] @@ WWW (@uref{http://www.fh-wolfenbuettel.de/ftp/pub/database/mysql/}) FTP (@uref{ftp://ftp.fh-wolfenbuettel.de/pub/database/mysql/}) @item @image{Flags/greece} Greece [NTUA, Athens] @@ WWW (@uref{http://www.ntua.gr/mysql/}) FTP (@uref{ftp://ftp.ntua.gr/pub/databases/mysql/}) @item @image{Flags/hungary} Hungary [stop.hu] @@ WWW (@uref{http://mysql.mirror.stop.hu/}) @item @image{Flags/hungary} Hungary [TiszaneT] @@ WWW (@uref{http://mysql.tiszanet.hu/}) FTP (@uref{ftp://mysql.tiszanet.hu/pub/mirrors/mysql/}) @item @image{Flags/hungary} Hungary [Xenia] @@ WWW (@uref{http://mysql.sote.hu/}) FTP (@uref{ftp://xenia.sote.hu/pub/mirrors/www.mysql.com/}) @item @image{Flags/iceland} Iceland [Tvund] @@ WWW (@uref{http://mysql.tviund.is/}) @item @image{Flags/ireland} Ireland [Esat Net] @@ WWW (@uref{http://ftp.esat.net/mirrors/download.sourceforge.net/pub/mirrors/mysql/}) FTP (@uref{ftp://ftp.esat.net/mirrors/download.sourceforge.net/pub/mirrors/mysql/}) @item @image{Flags/ireland} Ireland [MD NMTB Media] @@ WWW (@uref{http://mirrors.nmtbmedia.com/mysql/}) @item @image{Flags/israel} Israel [fresh.co.il] @@ WWW (@uref{http://mysql.fresh.co.il/}) @item @image{Flags/italy} Italy [feelinglinux.com] @@ WWW (@uref{http://mysql.feelinglinux.com/}) @item @image{Flags/italy} Italy [Teta Srl] @@ WWW (@uref{http://www.teta.it/mysql/}) @item @image{Flags/italy} Italy [tzone.it] @@ WWW (@uref{http://mysql.tzone.it/}) @item @image{Flags/latvia} Latvia [linux.lv] @@ FTP (@uref{ftp://ftp.linux.lv/pub/software/mysql/}) @item @image{Flags/netherlands} Netherlands [OMS-Net] @@ WWW (@uref{http://mysql.oms-net.nl/}) @item @image{Flags/netherlands} Netherlands [ProServe] @@ WWW (@uref{http://mysql.proserve.nl/}) @item @image{Flags/netherlands} Netherlands [WideXS BV] @@ WWW (@uref{http://mysql.mirror.widexs.nl/}) FTP (@uref{ftp://mirror.widexs.nl/pub/mysql/}) @item @image{Flags/norway} Norway [Brainpeddlers AS] @@ WWW (@uref{http://mysql.brainpeddlers.com/}) @item @image{Flags/poland} Poland [ncservice.com/Gdansk] @@ WWW (@uref{http://mysql.service.net.pl/}) @item @image{Flags/poland} Poland [SunSITE] @@ WWW (@uref{http://sunsite.icm.edu.pl/mysql/}) FTP (@uref{ftp://sunsite.icm.edu.pl/pub/unix/mysql/}) @item @image{Flags/portugal} Portugal [Instituto Supertior Tcnico] @@ WWW (@uref{http://darkstar.ist.utl.pt/mysql/}) FTP (@uref{ftp://darkstar.ist.utl.pt/pub/mysql/}) @item @image{Flags/portugal} Portugal [Netviso] @@ WWW (@uref{http://mysql.netvisao.pt/}) FTP (@uref{ftp://mirrors2.netvisao.pt/pub/mysql/}) @item @image{Flags/portugal} Portugal [VIZZAVI] @@ WWW (@uref{http://ftp.vizzavi.pt/pub/mysql/}) FTP (@uref{ftp://ftp.vizzavi.pt/pub/mysql/}) @item @image{Flags/romania} Romania [roedu.net/Bucharest] @@ FTP (@uref{ftp://ftp.roedu.net/pub/mirrors/ftp.mysql.com/}) @item @image{Flags/russia} Russia [DirectNet] @@ WWW (@uref{http://mysql.directnet.ru/}) FTP (@uref{ftp://ftp.dn.ru/pub/MySQL/}) @item @image{Flags/russia} Russia [Scientific Center/Chernogolovka] @@ FTP (@uref{ftp://ftp.chg.ru/pub/databases/mysql/}) @item @image{Flags/slovenia} Slovenia [ARNES] @@ WWW (@uref{http://ftp.arnes.si/mysql/}) FTP (@uref{ftp://ftp.arnes.si/packages/mysql/}) @item @image{Flags/sweden} Sweden [Sunet] @@ WWW (@uref{http://ftp.sunet.se/pub/unix/databases/relational/mysql/}) FTP (@uref{ftp://ftp.sunet.se/pub/unix/databases/relational/mysql/}) @item @image{Flags/switzerland} Switzerland [SunSITE] @@ WWW (@uref{http://sunsite.cnlab-switch.ch/ftp/mirror/mysql/}) FTP (@uref{ftp://sunsite.cnlab-switch.ch/mirror/mysql/}) @item @image{Flags/turkey} Turkey [proGEN] @@ WWW (@uref{http://mysql.progen.com.tr/}) @item @image{Flags/turkey} Turkey [Turkish National Academic Network & Information Center] @@ WWW (@uref{http://mysql.ulak.net.tr/}) @item @image{Flags/great-britain} UK [PLiG/UK] @@ WWW (@uref{http://ftp.plig.org/pub/mysql/}) FTP (@uref{ftp://ftp.plig.org/pub/mysql/}) @item @image{Flags/ukraine} Ukraine [ISP Alkar Teleport/Dnepropetrovsk] @@ WWW (@uref{http://mysql.dp.ua/}) FTP (@uref{ftp://ftp.tlk-l.net/pub/mirrors/mysql.com/}) @item @image{Flags/ukraine} Ukraine [PACO] @@ WWW (@uref{http://mysql.paco.net.ua/}) FTP (@uref{ftp://mysql.paco.net.ua/}) @item @image{Flags/yugoslavia} Yugoslavia [Open Source Network of Yugoslavia] @@ WWW (@uref{http://mysql.boa.org.yu/}) FTP (@uref{ftp://ftp.linux.org.yu/pub/MySQL/}) @end itemize @strong{North America:} @itemize @bullet @item @image{Flags/canada} Canada [Tryc] @@ WWW (@uref{http://web.tryc.on.ca/mysql/}) @item @image{Flags/mexico} Mexico [UAM] @@ WWW (@uref{http://mysql.azc.uam.mx/}) FTP (@uref{ftp://mysql.azc.uam.mx/mirrors/mysql/}) @item @image{Flags/mexico} Mexico [UNAM] @@ WWW (@uref{http://mysql.unam.mx/}) FTP (@uref{ftp://mysql.unam.mx/pub/mysql/}) @item @image{Flags/usa} USA [adgrafix.com / Boston, MA] @@ WWW (@uref{http://mysql.adgrafix.com/}) @item @image{Flags/usa} USA [Argonne National Laboratory / Chicago, IL] @@ FTP (@uref{ftp://mirror.mcs.anl.gov/pub/mysql/}) @item @image{Flags/usa} USA [Hurricane Electric / San Jose, CA] @@ WWW (@uref{http://mysql.he.net/}) @item @image{Flags/usa} USA [netNumina / Cambridge, MA] @@ WWW (@uref{http://mysql.mirrors.netnumina.com/}) @item @image{Flags/usa} USA [NIXC / Vienna, VA] @@ WWW (@uref{http://mysql.nixc.net/}) FTP (@uref{ftp://mysql.nixc.net/pub/mysql/}) @item @image{Flags/usa} USA [Oregon State University / Corvallis, OR] @@ WWW (@uref{http://mysql.orst.edu/}) FTP (@uref{ftp://ftp.orst.edu/pub/mysql/}) @item @image{Flags/usa} USA [University of Wisconsin / Wisconsin] @@ WWW (@uref{http://mirror.sit.wisc.edu/mysql/}) FTP (@uref{ftp://mirror.sit.wisc.edu/mirrors/mysql/}) @item @image{Flags/usa} USA [UUNet] @@ WWW (@uref{http://mysql.secsup.org/}) FTP (@uref{ftp://mysql.secsup.org/pub/software/mysql/}) @end itemize @strong{South America:} @itemize @bullet @item @image{Flags/argentina} Argentina [bannerlandia.com] @@ WWW (@uref{http://mysql.bannerlandia.com.ar/}) FTP (@uref{ftp://mysql.bannerlandia.com.ar/mirrors/mysql/}) @item @image{Flags/chile} Chile [PSINet] @@ WWW (@uref{http://mysql.psinet.cl/}) FTP (@uref{ftp://ftp.psinet.cl/pub/database/mysql/}) @item @image{Flags/chile} Chile [Tecnoera] @@ WWW (@uref{http://mysql.tecnoera.com/}) @item @image{Flags/chile} Chile [Vision] @@ WWW (@uref{http://mysql.vision.cl/}) @item @image{Flags/costa-rica} Costa Rica [Ogmios Communications] @@ WWW (@uref{http://mysql.ogmios.co.cr/}) FTP (@uref{ftp://mysql.ogmios.co.cr/pub/mysql/}) @end itemize @strong{Asia:} @itemize @bullet @item @image{Flags/china} China [HKLPG/Hong Kong] @@ WWW (@uref{http://mysql.hklpg.org/}) @item @image{Flags/china} China [linuxforum.net] @@ FTP (@uref{http://www2.linuxforum.net/mirror/mysql/}) @item @image{Flags/china} China [shellhung.org/Hong Kong] @@ WWW (@uref{http://mysql.shellhung.org/}) FTP (@uref{ftp://ftp.shellhung.org/pub/Mirror/mysql/}) @item @image{Flags/indonesia} Indonesia [CBN] @@ WWW (@uref{http://mysql.cbn.net.id/}) @item @image{Flags/indonesia} Indonesia [incaf.net] @@ WWW (@uref{http://mysql.incaf.net/}) FTP (@uref{ftp://mysql.incaf.net/}) @item @image{Flags/indonesia} Indonesia [M-Web] @@ WWW (@uref{http://mysql.mweb.net.id/}) FTP (@uref{ftp://mysql.mweb.net.id/pub/database/mysql/}) @item @image{Flags/indonesia} Indonesia [web.id] @@ WWW (@uref{http://mysql.itb.web.id/}) FTP (@uref{ftp://mysql.itb.web.id/pub/MySQL/}) @item @image{Flags/japan} Japan [Soft Agency] @@ WWW (@uref{http://www.softagency.co.jp/MySQL/}) @item @image{Flags/japan} Japan [u-aizu.ac.jp/Aizu] @@ FTP (@uref{ftp://ftp.u-aizu.ac.jp/ftp/pub/dbms/mysql/mysql.com/}) @item @image{Flags/philippines} Philippines [Ateneo de Zamboanga University] @@ WWW (@uref{http://mysql.adzu.edu.ph/}) @item @image{Flags/singapore} Singapore [HJC] @@ WWW (@uref{http://mysql.hjc.edu.sg/}) FTP (@uref{ftp://ftp.hjc.edu.sg/mysql/}) @item @image{Flags/south-korea} South Korea [HolyNet] @@ WWW (@uref{http://mysql.holywar.net/}) @item @image{Flags/south-korea} South Korea [Webiiz] @@ WWW (@uref{http://mysql.webiiz.com/}) @item @image{Flags/taiwan} Taiwan [I-SHOU University] @@ WWW (@uref{http://mysql.isu.edu.tw/}) @item @image{Flags/taiwan} Taiwan [nctu.edu/HsinChu] @@ WWW (@uref{http://mysql.nctu.edu.tw/}) @item @image{Flags/taiwan} Taiwan [TTN] @@ WWW (@uref{http://mysql.ttn.net/}) @end itemize @strong{Australia:} @itemize @bullet @item @image{Flags/australia} Australia [InterActive Consulting] @@ WWW (@uref{http://mysql.oranged.to}) @item @image{Flags/australia} Australia [planetmirror.com] @@ WWW (@uref{http://mysql.planetmirror.com/}) FTP (@uref{ftp://planetmirror.com/pub/mysql/}) @item @image{Flags/new-zealand} New Zealand [Cubalan] @@ WWW (@uref{http://mysql.soa.co.nz/}) @end itemize @strong{Africa:} @itemize @bullet @item @image{Flags/south-africa} South African Republic [The Internet Solution/Johannesburg] @@ FTP (@uref{ftp://ftp.is.co.za/linux/mysql/}) @end itemize mysql-4.00.12/manual.ja_Credits.html0100644000175100001560000005543410021471264016062 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - C Credits Go to the first, previous, next, last section, table of contents.

    C Credits

    This appendix lists the developers, contributors, and supporters that have helped to make MySQL what it is today.

    C.1 Developers at MySQL AB

    These are the developers that are or have been employed by MySQL AB to work on the MySQL database software, roughly in the order they started to work with us. Following each developer is a small list of the tasks that the developer is responsible for, or the accomplishments they have made. All developers are involved in support.

    Michael (Monty) Widenius
    • Lead developer and main author of the MySQL server (mysqld).
    • New functions for the string library.
    • Most of the mysys library.
    • The ISAM and MyISAM libraries (B-tree index file handlers with index compression and different record formats).
    • The HEAP library. A memory table system with our superior full dynamic hashing. In use since 1981 and published around 1984.
    • The replace program (take a look at it, it's COOL!).
    • MyODBC, the ODBC driver for Windows95.
    • Fixing bugs in MIT-pthreads to get it to work for MySQL Server. And also Unireg, a curses-based application tool with many utilities.
    • Porting of mSQL tools like msqlperl, DBD/DBI, and DB2mysql.
    • Most of crash-me and the foundation for the MySQL benchmarks.
    David Axmark
    • Initial main writer of the Reference Manual, including enhancements to texi2html.
    • Automatic web site updating from the manual.
    • Initial Autoconf, Automake, and Libtool support.
    • Licensing.
    • Parts of all the text files. (Nowadays only the `README' is left. The rest ended up in the manual.)
    • Lots of testing of new features.
    • Our in-house Free Software legal expert.
    • Mailing list maintainer (who never has the time to do it right...).
    • Our original portability code (more than 10 years old now). Nowadays only some parts of mysys are left.
    • Someone for Monty to call in the middle of the night when he just got that new feature to work.
    • Chief "Open Sourcerer" (MySQL community relations).
    Jani Tolonen
    • mysqlimport
    • A lot of extensions to the command-line clients.
    • PROCEDURE ANALYSE()
    Sinisa Milivojevic
    • Compression (with zlib) in the client/server protocol.
    • Perfect hashing for the lexical analyser phase.
    • Multi-row INSERT
    • mysqldump -e option
    • LOAD DATA LOCAL INFILE
    • SQL_CALC_FOUND_ROWS SELECT option
    • --max-user-connections=... option
    • net_read and net_write_timeout
    • GRANT/REVOKE and SHOW GRANTS FOR
    • New client-server protocol for 4.0
    • UNION in 4.0
    • Multi-table DELETE/UPDATE
    • Derived tables in 4.1
    • User resources management
    • Initial developer of the MySQL++ C++ API and the MySQLGUI client.
    Tonu Samuel (past developer)
    • VIO interface (the foundation for the encrypted client/server protocol).
    • MySQL Filesystem (a way to use MySQL databases as files and directories).
    • The CASE expression.
    • The MD5() and COALESCE() functions.
    • RAID support for MyISAM tables.
    Sasha Pachev
    • Initial implementation of replication (upto version 4.0).
    • SHOW CREATE TABLE.
    • mysql-bench
    Matt Wagner
    • MySQL test suite.
    • Webmaster (until 2002).
    • Coordinator of development.
    Miguel Solorzano
    • Win32 development and release builds.
    • Windows NT server code.
    • WinMySQLAdmin
    Timothy Smith (past developer)
    • Dynamic character sets support.
    • configure, RPMs and other parts of the build system.
    • Initial developer of libmysqld, the embedded server.
    Sergei Golubchik
    • Full-text search.
    • Added keys to the MERGE library.
    Jeremy Cole
    • Proofreading and editing this fine manual.
    • ALTER TABLE ... ORDER BY ....
    • UPDATE ... ORDER BY ....
    • DELETE ... ORDER BY ....
    Indrek Siitan
    • Designing/programming of our web interface.
    • Author of our newsletter management system.
    Jorge del Conde
    • MySQLCC (MySQL Control Center)
    • Win32 development
    • Initial implementation of the website portals.
    Venu Anuganti
    • MyODBC 3.51
    • New client/server protocol for 4.1 (for prepared statements).
    Arjen Lentz
    • Maintainer of the MySQL Reference Manual.
    • Preparing the O'Reilly printed edition of the manual.
    Alexander (Bar) Barkov, Alexey (Holyfoot) Botchkov, and Ramil Kalimullin
    • Spatial data (GIS) and R-Trees implementation for 4.1
    • Unicode and character sets for 4.1
    Oleksandr (Sanja) Byelkin
    • Query cache in 4.0
    • Implementation of subqueries (4.1).
    Aleksey (Walrus) Kishkin and Alexey (Ranger) Stroganov
    • Benchmarks design and analysis.
    • Maintenance of the MySQL test suite.
    Zak Greant
    • Open Source advocate, MySQL community relations.
    Carsten Pedersen
    • The MySQL Certification program.
    Lenz Grimmer
    • Production (build and release) engineering.
    Peter Zaitsev
    • SHA1(), AES_ENCRYPT() and AES_DECRYPT() functions.
    • Debugging, cleaning up various features.
    Alexander (Salle) Keremidarski
    • Documentation of existing MySQL code/algorithms.
    • Debugging.
    Per-Erik Martin
    • Lead developer for stored procedures and triggers.
    Jim Winstead
    • Lead web developer.
    Mark Matthews
    • Connector/J driver (Java).

    C.2 Contributors to MySQL

    While MySQL AB owns all copyrights in the MySQL server and the MySQL manual, we wish to recognise those who have made contributions of one kind or another to the MySQL distribution. Contributors are listed here, in somewhat random order:

    Paul DuBois
    Ongoing help with making this manual correct and understandable. That includes rewriting Monty's and David's attempts at English into English as other people know it.
    Gianmassimo Vigazzola qwerg@mbox.vol.it or qwerg@tin.it
    The initial port to Win32/NT.
    Kim Aldale
    Helped to rewrite Monty's and David's early attempts at English into English.
    Per Eric Olsson
    For more or less constructive criticism and real testing of the dynamic record format.
    Irena Pancirov irena@mail.yacc.it
    Win32 port with Borland compiler. mysqlshutdown.exe and mysqlwatch.exe
    David J. Hughes
    For the effort to make a shareware SQL database. At TcX, the predecessor of MySQL AB, we started with mSQL, but found that it couldn't satisfy our purposes so instead we wrote a SQL interface to our application builder Unireg. mysqladmin and mysql client are programs that were largely influenced by their mSQL counterparts. We have put a lot of effort into making the MySQL syntax a superset of mSQL. Many of the API's ideas are borrowed from mSQL to make it easy to port free mSQL programs to the MySQL API. The MySQL software doesn't contain any code from mSQL. Two files in the distribution (`client/insert_test.c' and `client/select_test.c') are based on the corresponding (non-copyrighted) files in the mSQL distribution, but are modified as examples showing the changes necessary to convert code from mSQL to MySQL Server. (mSQL is copyrighted David J. Hughes.)
    Fred Fish
    For his excellent C debugging and trace library. Monty has made a number of smaller improvements to the library (speed and additional options).
    Richard A. O'Keefe
    For his public domain string library.
    Henry Spencer
    For his regex library, used in WHERE column REGEXP regexp.
    Free Software Foundation
    From whom we got an excellent compiler (gcc), the libc library (from which we have borrowed `strto.c' to get some code working in Linux), and the readline library (for the mysql client).
    Free Software Foundation & The XEmacs development team
    For a really great editor/environment used by almost everybody at MySQL AB/TcX/detron.
    Patrick Lynch
    For helping us acquire http://www.mysql.com/.
    Fred Lindberg
    For setting up qmail to handle the MySQL mailing list and for the incredible help we got in managing the MySQL mailing lists.
    Igor Romanenko igor@frog.kiev.ua
    mysqldump (previously msqldump, but ported and enhanced by Monty).
    Yuri Dario
    For keeping up and extending the MySQL OS/2 port.
    Tim Bunce, Alligator Descartes
    For the DBD (Perl) interface.
    Tim Bunce
    Author of mysqlhotcopy.
    Andreas Koenig a.koenig@mind.de
    For the Perl interface for MySQL Server.
    Eugene Chan eugene@acenet.com.sg
    For porting PHP for MySQL Server.
    Michael J. Miller Jr. mke@terrapin.turbolift.com
    For the first MySQL manual. And a lot of spelling/language fixes for the FAQ (that turned into the MySQL manual a long time ago).
    Yan Cailin
    First translator of the MySQL Reference Manual into simplified chinese in early 2000 on which the Big5 and HK coded (http://mysql.hitstar.com/) versions were based. Personal home page at linuxdb.yeah.net.
    Giovanni Maruzzelli maruzz@matrice.it
    For porting iODBC (Unix ODBC).
    Chris Provenzano
    Portable user level pthreads. From the copyright: This product includes software developed by Chris Provenzano, the University of California, Berkeley, and contributors. We are currently using version 1_60_beta6 patched by Monty (see `mit-pthreads/Changes-mysql').
    Xavier Leroy Xavier.Leroy@inria.fr
    The author of LinuxThreads (used by the MySQL Server on Linux).
    Zarko Mocnik zarko.mocnik@dem.si
    Sorting for Slovenian language and the `cset.tar.gz' module that makes it easier to add other character sets.
    "TAMITO" tommy@valley.ne.jp
    The _MB character set macros and the ujis and sjis character sets.
    Joshua Chamas joshua@chamas.com
    Base for concurrent insert, extended date syntax, debugging on NT, and answering on the MySQL mailing list.
    Yves Carlier Yves.Carlier@rug.ac.be
    mysqlaccess, a program to show the access rights for a user.
    Rhys Jones rhys@wales.com (And GWE Technologies Limited)
    For JDBC, a module to extract data from a MySQL Database with a Java client.
    Dr Xiaokun Kelvin ZHU X.Zhu@brad.ac.uk
    Further development of the JDBC driver and other MySQL-related Java tools.
    James Cooper pixel@organic.com
    For setting up a searchable mailing list archive at his site.
    Rick Mehalick Rick_Mehalick@i-o.com
    For xmysql, a graphical X client for MySQL Server.
    Doug Sisk sisk@wix.com
    For providing RPM packages of MySQL for RedHat Linux.
    Diemand Alexander V. axeld@vial.ethz.ch
    For providing RPM packages of MySQL for RedHat Linux-Alpha.
    Antoni Pamies Olive toni@readysoft.es
    For providing RPM versions of a lot of MySQL clients for Intel and SPARC.
    Jay Bloodworth jay@pathways.sde.state.sc.us
    For providing RPM versions for MySQL Version 3.21.
    Jochen Wiedmann wiedmann@neckar-alb.de
    For maintaining the Perl DBD::mysql module.
    Therrien Gilbert gilbert@ican.net, Jean-Marc Pouyot jmp@scalaire.fr
    French error messages.
    Petr Snajdr, snajdr@pvt.net
    Czech error messages.
    Jaroslaw Lewandowski jotel@itnet.com.pl
    Polish error messages.
    Miguel Angel Fernandez Roiz
    Spanish error messages.
    Roy-Magne Mo rmo@www.hivolda.no
    Norwegian error messages and testing of Version 3.21.#.
    Timur I. Bakeyev root@timur.tatarstan.ru
    Russian error messages.
    brenno@dewinter.com & Filippo Grassilli phil@hyppo.com
    Italian error messages.
    Dirk Munzinger dirk@trinity.saar.de
    German error messages.
    Billik Stefan billik@sun.uniag.sk
    Slovak error messages.
    Stefan Saroiu tzoompy@cs.washington.edu
    Romanian error messages.
    Peter Feher
    Hungarian error messages.
    Roberto M. Serqueira
    Portugise error messages.
    Carsten H. Pedersen
    Danish error messages.
    Arjen G. Lentz
    Dutch error messages, completing earlier partial translation (also work on consistency and spelling).
    David Sacerdote davids@secnet.com
    Ideas for secure checking of DNS hostnames.
    Wei-Jou Chen jou@nematic.ieo.nctu.edu.tw
    Some support for Chinese(BIG5) characters.
    Wei He hewei@mail.ied.ac.cn
    A lot of functionality for the Chinese(GBK) character set.
    Zeev Suraski bourbon@netvision.net.il
    FROM_UNIXTIME() time formatting, ENCRYPT() functions, and bison advisor. Active mailing list member.
    Luuk de Boer luuk@wxs.nl
    Ported (and extended) the benchmark suite to DBI/DBD. Have been of great help with crash-me and running benchmarks. Some new date functions. The mysql_setpermissions script.
    Jay Flaherty fty@mediapulse.com
    Big parts of the Perl DBI/DBD section in the manual.
    Paul Southworth pauls@etext.org, Ray Loyzaga yar@cs.su.oz.au
    Proof-reading of the Reference Manual.
    Alexis Mikhailov root@medinf.chuvashia.su
    User-definable functions (UDFs); CREATE FUNCTION and DROP FUNCTION.
    Andreas F. Bobak bobak@relog.ch
    The AGGREGATE extension to UDF functions.
    Ross Wakelin R.Wakelin@march.co.uk
    Help to set up InstallShield for MySQL-Win32.
    Jethro Wright III jetman@li.net
    The `libmysql.dll' library.
    James Pereria jpereira@iafrica.com
    Mysqlmanager, a Win32 GUI tool for administrating MySQL Server.
    Curt Sampson cjs@portal.ca
    Porting of MIT-pthreads to NetBSD/Alpha and NetBSD 1.3/i386.
    Antony T. Curtis antony.curtis@olcs.net
    Porting of the MySQL Database software to OS/2.
    Martin Ramsch m.ramsch@computer.org
    Examples in the MySQL Tutorial.
    Steve Harvey
    For making mysqlaccess more secure.
    Konark IA-64 Centre of Persistent Systems Private Limited
    http://www.pspl.co.in/konark/. Help with the Win64 port of the MySQL server.
    Albert Chin-A-Young.
    Configure updates for Tru64, large file support and better TCP wrappers support.
    John Birrell
    Emulation of pthread_mutex() for OS/2.
    Benjamin Pflugmann
    Extended MERGE tables to handle INSERTS. Active member on the MySQL mailing lists.
    Guilhem Bichot
    Fixed handling of exponents for DECIMAL. Author of mysql_tableinfo.
    Jocelyn Fournier
    Excellent spotting and reporting innumerable bugs (especially in the MySQL 4.1 subquery code).
    Georg Richter
    MySQL 4.1 testing and bug hunting. New PHP 5.0 mysqli extension (API) for use with MySQL 4.1 and up.
    Marc Liyanage
    Maintaining the Mac OS X packages and providing invaluable feedback on how to create Mac OS X PKGs.

    Other contributors, bugfinders, and testers: James H. Thompson, Maurizio Menghini, Wojciech Tryc, Luca Berra, Zarko Mocnik, Wim Bonis, Elmar Haneke, jehamby@lightside, psmith@BayNetworks.com, duane@connect.com.au, Ted Deppner ted@psyber.com, Mike Simons, Jaakko Hyvatti.

    And lots of bug report/patches from the folks on the mailing list.

    A big tribute goes to those that help us answer questions on the mysql@lists.mysql.com mailing list:

    Daniel Koch dkoch@amcity.com
    Irix setup.
    Luuk de Boer luuk@wxs.nl
    Benchmark questions.
    Tim Sailer tps@users.buoy.com
    DBD-mysql questions.
    Boyd Lynn Gerber gerberb@zenez.com
    SCO-related questions.
    Richard Mehalick RM186061@shellus.com
    xmysql-related questions and basic installation questions.
    Zeev Suraski bourbon@netvision.net.il
    Apache module configuration questions (log & auth), PHP-related questions, SQL syntax-related questions and other general questions.
    Francesc Guasch frankie@citel.upc.es
    General questions.
    Jonathan J Smith jsmith@wtp.net
    Questions pertaining to OS-specifics with Linux, SQL syntax, and other things that might need some work.
    David Sklar sklar@student.net
    Using MySQL from PHP and Perl.
    Alistair MacDonald A.MacDonald@uel.ac.uk
    Not yet specified, but is flexible and can handle Linux and maybe HP-UX. Will try to get user to use mysqlbug.
    John Lyon jlyon@imag.net
    Questions about installing MySQL on Linux systems, using either `.rpm' files or compiling from source.
    Lorvid Ltd. lorvid@WOLFENET.com
    Simple billing/license/support/copyright issues.
    Patrick Sherrill patrick@coconet.com
    ODBC and VisualC++ interface questions.
    Randy Harmon rjharmon@uptimecomputers.com
    DBD, Linux, some SQL syntax questions.

    C.3 Supporters to MySQL

    While MySQL AB owns all copyrights in the MySQL server and the MySQL manual, we wish to recognise the following companies, which helped us finance the development of the MySQL server, such as by paying us for developing a new feature or giving us hardware for development of the MySQL server.

    VA Linux / Andover.net
    Funded replication.
    NuSphere
    Editing of the MySQL manual.
    Stork Design studio
    The MySQL web site in use between 1998-2000.
    Intel
    Contributed to development on Windows and Linux platforms.
    Compaq
    Contributed to Development on Linux/Alpha.
    SWSoft
    Development on the embedded mysqld version.
    FutureQuest
    --skip-show-database

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Extending_MySQL.html0100644000175100001560000012672110021471264017435 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 9 Extending MySQL Go to the first, previous, next, last section, table of contents.

    9 Extending MySQL

    9.1 MySQL Internals

    This chapter describes a lot of things that you need to know when working on the MySQL code. If you plan to contribute to MySQL development, want to have access to the bleeding-edge in-between versions code, or just want to keep track of development, follow the instructions in 「2.3.4 開発ソースツリーからのインストール」節. If you are interested in MySQL internals, you should also subscribe to our internals mailing list. This list is relatively low traffic. For details on how to subscribe, please see 「1.6.1.1 MySQL メーリングリスト」節. All developers at MySQL AB are on the internals list and we help other people who are working on the MySQL code. Feel free to use this list both to ask questions about the code and to send patches that you would like to contribute to the MySQL project!

    9.1.1 MySQL Threads

    The MySQL server creates the following threads:

    • The TCP/IP connection thread handles all connection requests and creates a new dedicated thread to handle the authentication and SQL query processing for each connection.
    • On Windows NT there is a named pipe handler thread that does the same work as the TCP/IP connection thread on named pipe connect requests.
    • The signal thread handles all signals. This thread also normally handles alarms and calls process_alarm() to force timeouts on connections that have been idle too long.
    • If mysqld is compiled with -DUSE_ALARM_THREAD, a dedicated thread that handles alarms is created. This is only used on some systems where there are problems with sigwait() or if one wants to use the thr_alarm() code in ones application without a dedicated signal handling thread.
    • If one uses the --flush_time=# option, a dedicated thread is created to flush all tables at the given interval.
    • Every connection has its own thread.
    • Every different table on which one uses INSERT DELAYED gets its own thread.
    • If you use --master-host, a slave replication thread will be started to read and apply updates from the master.

    mysqladmin processlist only shows the connection, INSERT DELAYED, and replication threads.

    9.1.2 MySQL Test Suite

    Until recently, our main full-coverage test suite was based on proprietary customer data and for that reason has not been publicly available. The only publicly available part of our testing process consisted of the crash-me test, a Perl DBI/DBD benchmark found in the sql-bench directory, and miscellaneous tests located in tests directory. The lack of a standardised publicly available test suite has made it difficult for our users, as well developers, to do regression tests on the MySQL code. To address this problem, we have created a new test system that is included in the source and binary distributions starting in Version 3.23.29.

    The current set of test cases doesn't test everything in MySQL, but it should catch most obvious bugs in the SQL processing code, OS/library issues, and is quite thorough in testing replication. Our eventual goal is to have the tests cover 100% of the code. We welcome contributions to our test suite. You may especially want to contribute tests that examine the functionality critical to your system, as this will ensure that all future MySQL releases will work well with your applications.

    9.1.2.1 Running the MySQL Test Suite

    The test system consist of a test language interpreter (mysqltest), a shell script to run all tests(mysql-test-run), the actual test cases written in a special test language, and their expected results. To run the test suite on your system after a build, type make test or mysql-test/mysql-test-run from the source root. If you have installed a binary distribution, cd to the install root (eg. /usr/local/mysql), and do scripts/mysql-test-run. All tests should succeed. If not, you should try to find out why and report the problem if this is a bug in MySQL. 「9.1.2.3 Reporting Bugs in the MySQL Test Suite」節参照.

    If you have a copy of mysqld running on the machine where you want to run the test suite you do not have to stop it, as long as it is not using ports 9306 and 9307. If one of those ports is taken, you should edit mysql-test-run and change the values of the master and/or slave port to one that is available.

    You can run one individual test case with mysql-test/mysql-test-run test_name.

    If one test fails, you should test running mysql-test-run with the --force option to check if any other tests fails.

    9.1.2.2 Extending the MySQL Test Suite

    You can use the mysqltest language to write your own test cases. Unfortunately, we have not yet written full documentation for it - we plan to do this shortly. You can, however, look at our current test cases and use them as an example. The following points should help you get started:

    • The tests are located in mysql-test/t/*.test
    • A test case consists of ; terminated statements and is similar to the input of mysql command-line client. A statement by default is a query to be sent to MySQL server, unless it is recognised as internal command (eg. sleep).
    • All queries that produce results@-e.g., SELECT, SHOW, EXPLAIN, etc., must be preceded with @/path/to/result/file. The file must contain the expected results. An easy way to generate the result file is to run mysqltest -r < t/test-case-name.test from mysql-test directory, and then edit the generated result files, if needed, to adjust them to the expected output. In that case, be very careful about not adding or deleting any invisible characters - make sure to only change the text and/or delete lines. If you have to insert a line, make sure the fields are separated with a hard tab, and there is a hard tab at the end. You may want to use od -c to make sure your text editor has not messed anything up during edit. We, of course, hope that you will never have to edit the output of mysqltest -r as you only have to do it when you find a bug.
    • To be consistent with our setup, you should put your result files in mysql-test/r directory and name them test_name.result. If the test produces more than one result, you should use test_name.a.result, test_name.b.result, etc.
    • If a statement returns an error, you should on the line before the statement specify with the --error error-number. The error number can be a list of possible error numbers separated with ','.
    • If you are writing a replication test case, you should on the first line of the test file, put source include/master-slave.inc;. To switch between master and slave, use connection master; and connection slave;. If you need to do something on an alternate connection, you can do connection master1; for the master, and connection slave1; for the slave.
    • If you need to do something in a loop, you can use something like this: 
      let $1=1000;
while ($1)
{
 # do your queries here
 dec $1;
}
    • To sleep between queries, use the sleep command. It supports fractions of a second, so you can do sleep 1.3;, for example, to sleep 1.3 seconds.
    • To run the slave with additional options for your test case, put them in the command-line format in mysql-test/t/test_name-slave.opt. For the master, put them in mysql-test/t/test_name-master.opt.
    • If you have a question about the test suite, or have a test case to contribute, e-mail to internals@lists.mysql.com. As the list does not accept attachments, you should ftp all the relevant files to: ftp://support.mysql.com/pub/mysql/Incoming/

    9.1.2.3 Reporting Bugs in the MySQL Test Suite

    If your MySQL version doesn't pass the test suite you should do the following:

    • Don't send a bug report before you have found out as much as possible of what when wrong! When you do it, please use the mysqlbug script so that we can get information about your system and MySQL version. 「1.6.1.3 バグや問題を報告する方法」節参照.
    • Make sure to include the output of mysql-test-run, as well as contents of all .reject files in mysql-test/r directory.
    • If a test in the test suite fails, check if the test fails also when run by its own: 
      cd mysql-test
mysql-test-run --local test-name
      If this fails, then you should configure MySQL with --with-debug and run mysql-test-run with the --debug option. If this also fails send the trace file `var/tmp/master.trace' to ftp://support.mysql.com/pub/mysql/secret so that we can examine it. Please remember to also include a full description of your system, the version of the mysqld binary and how you compiled it.
    • Try also to run mysql-test-run with the --force option to see if there is any other test that fails.
    • If you have compiled MySQL yourself, check our manual for how to compile MySQL on your platform or, preferable, use one of the binaries we have compiled for you at http://www.mysql.com/downloads/. All our standard binaries should pass the test suite !
    • If you get an error, like Result length mismatch or Result content mismatch it means that the output of the test didn't match exactly the expected output. This could be a bug in MySQL or that your mysqld version produces slight different results under some circumstances. Failed test results are put in a file with the same base name as the result file with the .reject extension. If your test case is failing, you should do a diff on the two files. If you cannot see how they are different, examine both with od -c and also check their lengths.
    • If a test fails totally, you should check the logs file in the mysql-test/var/log directory for hints of what went wrong.
    • If you have compiled MySQL with debugging you can try to debug this by running mysql-test-run with the --gdb and/or --debug options. 「E.1.2 Creating Trace Files」節参照. If you have not compiled MySQL for debugging you should probably do that. Just specify the --with-debug options to configure! 「2.3 MySQL ソースディストリビューションのインストール」節参照.

    9.2 MySQL への新しい関数の追加

    There are two ways to add new functions to MySQL:

    • ユーザ定義関数(UDF:user-definable function)インタフェースを通して関数を追 加できます。 ユーザ定義関数は、CREATE FUNCTION と DROP FUNCTION ステー トメントを使用して、動的に追加、削除されます。 「9.2.1 CREATE FUNCTION/DROP FUNCTION Syntax」節参照.
    • ネイティブ(ビルトイン) MySQL 関数として関数を追加できます。 ネイティブ関数は mysqld サーバに統合され、恒久的に有効になります。

    それぞれの方法には、有利な点と不利な点があります:

    • ユーザ定義関数を書く場合、サーバ自身に追加するオブジェクトファイルをイン ストールする必要があります。関数をサーバに統合する場合あそれを行なう必要 はありません。
    • UDF をバイナリ MySQL 配布に追加することができます。ネイティブ関 数はソース配布の変更が必要です。
    • MySQL 配布をアップグレードする場合、前にインストールされた UDF の使用を継続できます。ネイティブ関数では、アップグレードの度に変更を繰り 返す必要があります。

    新しい関数を追加するためにどちらの方法を使用しても、ABS() や SOUNDEX() のようなネイティブ関数と同じように使用することができま す。

    9.2.1 CREATE FUNCTION/DROP FUNCTION Syntax

    CREATE [AGGREGATE] FUNCTION function_name RETURNS {STRING|REAL|INTEGER}
       SONAME shared_library_name

DROP FUNCTION function_name

    A user-definable function (UDF) is a way to extend MySQL with a new function that works like native (built in) MySQL functions such as ABS() and CONCAT().

    AGGREGATE is a new option for MySQL Version 3.23. An AGGREGATE function works exactly like a native MySQL GROUP function like SUM or COUNT().

    CREATE FUNCTION saves the function's name, type, and shared library name in the mysql.func system table. You must have the INSERT and DELETE privileges for the mysql database to create and drop functions.

    All active functions are reloaded each time the server starts, unless you start mysqld with the --skip-grant-tables option. In this case, UDF initialisation is skipped and UDFs are unavailable. (An active function is one that has been loaded with CREATE FUNCTION and not removed with DROP FUNCTION.)

    For instructions on writing user-definable functions, see 「9.2 MySQL への新しい関数の追加」節. For the UDF mechanism to work, functions must be written in C or C++, your operating system must support dynamic loading and you must have compiled mysqld dynamically (not statically).

    Note that to make AGGREGATE work, you must have a mysql.func table that contains the column type. If this is not the case, you should run the script mysql_fix_privilege_tables to get this fixed.

    9.2.2 新しいユーザ定義関数の追加

    UDF 機構が動作するためには、関数は C か C++ で書かれる必要があり、OS が 動的ローディングをサポートする必要があります。MySQL ソース配布 は `sql/udf_example.cc' を含んでいて、これは５つの新しい関数を定義 しています。UDF の呼び出し方法がどのように働くかはこのファイルを参考にし てください。

    For mysqld to be able to use UDF functions, you should configure MySQL with --with-mysqld-ldflags=-rdynamic The reason is that to on many platforms (including Linux) you can load a dynamic library (with dlopen()) from a static linked program, which you would get if you are using --with-mysqld-ldflags=-all-static If you want to use an UDF that needs to access symbols from mysqld (like the methaphone example in `sql/udf_example.cc' that uses default_charset_info), you must link the program with -rdynamic (see man dlopen).

    SQL ステートメントで使用したいそれぞれの関数について、対応する C (または C++) 関数を定義すべきです。下の説明では、名前 ``xxx'' がサンプル関数名と して使用されています。SQL と C/C++ 使用法を distinquish するために、 XXX() (大文字) は SQL 関数呼び出しを表わし、xxx() (小文字) は C/C++ 関数呼び出しを表わします。

    XXX() のインタフェースを実装するために書く C/C++ 関数は:

    xxx() (必要)
    メイン関数。これは関数結果が計算されるところです。SQL 型と C/C++ 関数の 戻り値型の対応は次に示します:
    SQL type C/C++ type
    STRING char *
    INTEGER long long
    REAL double
    xxx_init() (オプション)
    xxx() の初期化関数。これは次のように使用されます:
    • XXX() の引数の数のチェック
    • 引数が要求される型かどうかのチェック、また、メイン関数が呼ばれる時に望む 型に引数を強制するように MySQL に伝える
    • メイン関数が必要とするメモリの割り当て
    • 結果の最大長の指定
    • (REAL 関数では) 小数部の最大桁数の指定
    • 結果が NULL になり得るかどうかの指定
    xxx_deinit() (オプション)
    xxx() の終了関数(deinitialization function)。これは初期化関数によっ て割り当てられたメモリを解放すべきです。

    SQL ステートメントが XXX() を呼び出すとき、MySQL は引数 チェックやメモリ割り当てのように、必要なセットアップを行なわせるために、 初期化関数 xxx_init() を呼び出します。xxx_init() がエラー を返す場合、SQL ステートメントはエラーメッセージと共に異常終了し、メイン 関数と終了関数は呼び出されません。そうでなければ、メイン関数 xxx() が各行毎に呼び出されます。全ての行が処理された後、終了関数 xxx_deinit() が、必要な掃除を行なうために、呼び出されます。

    For aggregate functions (like SUM()), you must also provide the llowing functions:

    xxx_reset() (required)
    Reset sum and insert the argument as the initial value for a new group.
    xxx_add() (required)
    Add the argument to the old sum.

    When using aggregate UDF functions MySQL works the following way:

    1. Call xxx_init() to let the aggregate function allocate the memory it will need to store results.
    2. Sort the table according to the GROUP BY expression.
    3. For the first row in a new group, call the xxx_reset() function.
    4. For each new row that belongs in the same group, call the xxx_add() function.
    5. When the group changes or after the last row has been processed, call xxx() to get the result for the aggregate.
    6. Repeat 3-5 until all rows has been processed
    7. Call xxx_deinit() to let the UDF free any memory it has allocated.

    全ての関数はスレッド安全でなくてはいけません(メイン関数だけでなく、初期 化関数と終了関数も同様です)。これは変更されうるグローバル変数や静的変数 を割り当てることは許されないことを意味します！ メモリが必要な場合は、 xxx_init() で割り当て、xxx_deinit() でそれを解放すべきです。

    9.2.2.1 UDF Calling Sequences

    メイン関数は下に示すように宣言されるべきです。戻り値型と引数は、 CREATE FUNCTION ステートメントで、SQL 関数 XXX() の戻り値 をSTRING, INTEGER, REAL のどれに宣言するかに依存し て異なることに注意してください:

    STRING 関数では: 

    char *xxx(UDF_INIT *initid, UDF_ARGS *args,
          char *result, unsigned long *length,
          char *is_null, char *error);

    INTEGER 関数では: 

    long long xxx(UDF_INIT *initid, UDF_ARGS *args,
              char *is_null, char *error);

    REAL 関数では: 

    double xxx(UDF_INIT *initid, UDF_ARGS *args,
              char *is_null, char *error);

    初期化と終了関数は次のように宣言します 

    my_bool xxx_init(UDF_INIT *initid, UDF_ARGS *args, char *message);

void xxx_deinit(UDF_INIT *initid);

    initid 引数は３つの関数全てに渡されます。これは UDF_INIT 構造体を示し、関数間で情報を伝達するために使用されます。UDF_INIT 構造体のメンバは下に一覧します。初期化関数は変更したい全てのメンバを埋め るべきです。(メンバにデフォルトを使用するには、未変更のままにしてくださ い。)

    my_bool maybe_null
    xxx() が NULL を返す場合、xxx_init() は maybe_null を 1 に設定すべきです。デフォルト値は、引数のい ずれかが maybe_null として宣言された場合、1 です。
    unsigned int decimals
    小数部の桁数。デフォルト値はメイン関数に渡される引数の小数部の最大桁数で す。(例えば、関数に 1.34, 1.345, 1.3 が渡された場合、 デフォルトは 3 です。1.345 が 3 桁の小数部を持つためです。)
    unsigned int max_length
    文字列結果の最大長。デフォルト値は関数の戻り値型に依存して異なります。文 字列関数では、デフォルトは最も長い引数の長さです。整数関数では、デフォル トは 21 桁です。実数関数では、デフォルトは 13 に initid->decimals で示される小数部の桁数を加えたものです。(数値関数では、長さは符号と小数 点文字を含みます。) If you want to return a blob, you can set this to 65K or 16M; this memory is not allocated but used to decide which column type to use if there is a need to temporary store the data.
    char *ptr
    それ自身の目的のために関数が使用できるポインタです。例えば、関数は割り当 てたメモリを関数間で伝達するために、initid->ptr を使用できます。 xxx_init() では、メモリを獲得し、このポインタに割り当てます: 
    initid->ptr = allocated_memory;
    xxx() と xxx_deinit() では、initid->ptr を参照して、 メモリを使用または解放します。

    9.2.2.2 UDF Calling Sequences for aggregate functions

    Here follows a description of the different functions you need to define when you want to create an aggregate UDF function. 

    char *xxx_reset(UDF_INIT *initid, UDF_ARGS *args,
                char *is_null, char *error);

    This function is called when MySQL finds the first row in a new group. In the function you should reset any internal summary variables and then set the given argument as the first argument in the group.

    In many cases this is implemented internally by reseting all variables and then calling xxx_add(). 

    char *xxx_add(UDF_INIT *initid, UDF_ARGS *args,
              char *is_null, char *error);

    This function is called for all rows that belongs to the same group, except for the first row. In this you should add the value in UDF_ARGS to your internal summary variable.

    The xxx() function should be declared identical as when you define a simple UDF function. 「9.2.2.1 UDF Calling Sequences」節参照.

    This function is called when all rows in the group has been processed. You should normally never access the args variable here but return your value based on your internal summary variables.

    All argument processing in xxx_reset() and xxx_add() should be done identically as for normal UDF functions. 「9.2.2.3 引数処理」節参照.

    The return value handling in xxx() should be done identically as for a normal UDF. 「9.2.2.4 戻り値とエラー処理」節参照.

    The pointer argument to is_null and error is the same for all calls to xxx_reset(), xxx_add() and xxx(). You can use this to remember that you got an error or if the xxx() function should return NULL. Note that you should not store a string into *error! This is just a 1 byte flag!

    is_null is reset for each group (before calling xxx_reset(). error is never reset.

    If isnull or error are set after xxx() then MySQL will return NULL as the result for the group function.

    9.2.2.3 引数処理

    args 引数は次に示すメンバを持つ UDF_ARGS 構造体へのポイン タです:

    unsigned int arg_count
    引数の数。関数が特定の引数の数で呼び出されることを期待する場合は、初期化 関数でこの値をチェックしてください。例えば: 
    if (args->arg_count != 2)
{
    strcpy(message,"XXX() requires two arguments");
    return 1;
}
    enum Item_result *arg_type
    引数の型。可能な型の値は STRING_RESULT, INT_RESULT, REAL_RESULT です。 引数が与えられた型であることと、そうでない場合エラーを返すことを確実にす るために、初期化関数で arg_type 配列をチェックしてください。例えば: 
    if (args->arg_type[0] != STRING_RESULT ||
    args->arg_type[1] != INT_RESULT)
{
    strcpy(message,"XXX() requires a string and an integer");
    return 1;
}
    関数の引数が特定の型を要求するための代案として、初期化関数を使用して、 arg_type 要素を求める型に設定できます。これは MySQL に xxx() の各呼び出しにこれらの型を引数に強制するようにさせます。例 えば、最初の２つの引数に文字列と整数を強制するように指定するには、 xxx_init() で次を行なってください: 
    args->arg_type[0] = STRING_RESULT;
args->arg_type[1] = INT_RESULT;
    char **args
    args->args は、関数が呼ばれる時の引数の一般的な特性について、情報 を初期化関数に伝達します。定数引数 i について、 args->args[i] は引数値のをポイントします。(値への正しいアクセス方 法については後述。)非定数引数について、args->args[i] は 0 です。定数引数は定数だけを使用する表現で、3, 4*7-2, SIN(3.14) などです。非定数引数は行から行に変更される値を参照する 表現で、項目名や非定数引数で呼び出される関数などです。 メイン関数のそれぞれの呼び出しについて、args->args は現在処理され ている行に渡される実際の引数を含んでいます。 関数は次のように引数 i を参照できます:
    • STRING_RESULT 型の引数は、バイナリデータまたは任意の長さのデータ の処理を許すため、文字列ポインタ＋長さとして与えられます。文字列内容は args->args[i] として有効で、文字列長は args->lengths[i] で す。文字列は NULL 終端とみなすべきではありません。
    • INT_RESULT 型の引数について、args->args[i] を long long 値にキャストする必要があります: 
      long long int_val;
int_val = *((long long*) args->args[i]);
    • For an argument of type REAL_RESULT, you must cast args->args[i] to a double value: 
      double    real_val;
real_val = *((double*) args->args[i]);
    unsigned long *lengths
    初期化関数では、lengths 配列は各引数についての最大文字列長を示し ます。メイン関数の各呼び出しについては、lengths は、現在処理され ている行に渡される任意の文字列引数の実際の長さを含んでいます。 INT_RESULT, REAL_RESULT 型の引数については、lengths はまだ引数の最大長を含んでいます(初期化関数については)。

    9.2.2.4 戻り値とエラー処理

    初期化関数は、エラーが無い場合は 0 を、そうでなければ 1 を 返すべきです。エラーが発生する場合は、xxx_init() は NULL 終端エラー メッセージを message パラメータに格納すべきです。このメッセージは クライアントに返されます。メッセージバッファは MYSQL_ERRMSG_SIZE 文字長ですが、80 文字より小さく保つように試みるべきです。標準的な端末画 面の幅にフィットするようにです。

    メイン関数 xxx() の返す値は long long と double 関 数については関数値です。文字列関数については、result と length 引数で文字列が返されます。result は少なくとも 255 バイト長のバッファです。これらに内容と戻り値の長さを設定してください。例 えば: 

    memcpy(result, "result string", 13);
*length = 13;

    The result buffer that is passed to the calc function is 255 byte big. If your result fits in this, you don't have to worry about memory allocation for results.

    あなたの文字列関数が 255 バイトよりも長い文字列を返す必要がある場合、 xxx_init() 関数または xxx() 関数内で malloc() で領域 を割り当て、xxx_deinit() 関数でそれを解放する必要があります。将来の xxx() 呼び出しによって再利用されるように、割り当てたメモリを UDF_INIT 構造体の ptr スロットに格納できます。 「9.2.2.1 UDF Calling Sequences」節参照.

    メイン関数で NULL 値の戻り値を示すには、is_null を 1 に設定してください: 

    *is_null = 1;

    To indicate an error return in the main function, set the error parameter to 1: 

    *error = 1;

    xxx() が任意の行について *error に 1 を設定する場合、 関数値は現在の行についてと、その後の XXX() が呼び出されるステート メントによって処理される任意の行について NULL です。(xxx() は続く行については呼び出しさえされません。) 注意: 3.22.10 より 前の MySQL バージョンでは、*error と *is_null の 両方に設定すべきです: 

    *error = 1;
*is_null = 1;

    9.2.2.5 ユーザ定義関数のコンパイルとインストール

    UDF を実装するファイルはサーバが動作するホスト上でコンパイルされインストー ルされないければなりません。この処理はサンプル UDF ファイル `udf_example.cc' について次に説明します。これは MySQL ソー ス配布に含まれています。このファイルは次の関数を含みます:

    • metaphon() は文字列引数の metaphon 文字列を返します。これは時には soundex 文字列ですが、さらに英語用に調整されています。
    • myfunc_double() は引数の文字の ASCII 値の合計を引数の長さの合計で 割った値を返します。
    • myfunc_int() は引数の長さの合計を返します。
    • sequence([const int]) returns an sequence starting from the given number or 1 if no number has been given.
    • lookup() はホスト名の IP 番号を返します。
    • reverse_lookup() は IP 番号のホスト名を返します。この関数は文字列 "xxx.xxx.xxx.xxx" または４つの数値とともに呼ばれます。

    動的ロード可能ファイルは、次のような何らかのコマンドを使用して、共有オブ ジェクトファイルとしてコンパイルされるべきです: 

    shell> gcc -shared -o udf_example.so myfunc.cc

    MySQL ソースツリーの `sql' ディレクトリ内で次のコマンドを 実行することにより、システムのコンパイラオプションを簡単に正しく見つけ出 すことができます: 

    shell> make udf_example.o

    make が表示するものに似たコンパイルコマンドを実行すべきですが、行 末近くの -c オプションを取り除いて、-o udf_example.so を行 末につけてください。(いくつかのシステムでは、コマンドに -c を残す 必要があります。)

    UDF を含む共有オブジェクトをコンパイルすると、それをインストールしてその ことを MySQL に知らせる必要があります。`udf_example.cc' か らの共有オブジェクトのコンパイルは、`udf_example.so' のような何かの ファイル名を提供します(実際の名前はプラットフォームによって変わります)。 このファイルを `/usr/lib' のような ld が探すどこかのディレク トリにコピーしてください。多くのシステムでは、LD_LIBRARY または LD_LIBRARY_PATH 環境変数を設定して、UDF 関数ファイルがあるディレ クトリを示すことができます。dlopen マニュアルページはシステム上で 使用すべき変数を教えてくれます。これを mysql.server または safe_mysqld スタートアップスクリプトに設定し、 mysqld を再起動すべきです。

    ライブラリがインストールされた後、mysqld に新しい関数について次の コマンドで通知すべきです: 

    mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "udf_example.so";
mysql> CREATE FUNCTION myfunc_double RETURNS REAL SONAME "udf_example.so";
mysql> CREATE FUNCTION myfunc_int RETURNS INTEGER SONAME "udf_example.so";
mysql> CREATE FUNCTION lookup RETURNS STRING SONAME "udf_example.so";
mysql> CREATE FUNCTION reverse_lookup
    ->        RETURNS STRING SONAME "udf_example.so";
mysql> CREATE AGGREGATE FUNCTION avgcost
    ->        RETURNS REAL SONAME "udf_example.so";

    関数は DROP FUNCTION を使用して削除できます: 

    mysql> DROP FUNCTION metaphon;
mysql> DROP FUNCTION myfunc_double;
mysql> DROP FUNCTION myfunc_int;
mysql> DROP FUNCTION lookup;
mysql> DROP FUNCTION reverse_lookup;
mysql> DROP FUNCTION avgcost;

    CREATE FUNCTION と DROP FUNCTION ステートメントは mysql データベース内のシステムテーブル func を更新します。 関数の名前、型、共有ライブラリ名はテーブルに保存されます。作成と破棄機能 のためには、mysql データベースに INSERT と DELETE 権限を持つ必要があります。

    既に生成してある関数を追加するために CREATE FUNCTION を使用すべき ではありません。関数の再インストールが必要な場合は、DROP FUNCTION でそれを削除し、それから CREATE FUNCTION で再インストールすべきで す。例えば、関数の新しいバージョンの再コンパイルをした場合、 mysqld が新しいバージョンを得るために、これを行なう必要があるでしょ う。そうでなければ、サーバは古いバージョンの使用を継続します。

    mysqld を --skip-grant-tables オプションで起動しなくても、 有効な関数はサーバの開始毎に再読み込みされます。この場合、UDF 初期化は飛 ばされ、UDF が無効になります。(有効な関数は CREATE FUNCTION でロー ドされているもので、DROP FUNCTION で削除されていないものです。)

    9.2.3 新しいネイティブ関数の追加

    ネイティブ関数を追加するためのプロシジャを以下に示します。バイナリ配布に はネイティブ関数を追加できないことに注意してください。プロシジャは MySQL ソースコードの変更を必要とするためです。MySQL を ソース配布から自分でコンパイルする必要があります。また、MySQL の他のバージョンに移行する場合(例えば、新しいバージョンがリリースされた 時)、新しいバージョンでこのプロシジャを繰り返す必要があります。

    新しいネイティブ MySQL 関数を追加するためには、次のステップに従っ てください:

    1. sql_functions[] 配列内で関数名を定義している `lex.h' に１行 追加してください。
    2. If the function prototype is simple (just takes zero, one, two or three arguments), you should in lex.h specify SYM(FUNC_ARG#) (where # is the number of arguments) as the second argument in the sql_functions[] array and add a function that creates a function object in `item_create.cc'. Take a look at "ABS" and create_funcs_abs() for an example of this. If the function prototype is complicated (for example takes a variable number of arguments), you should add two lines to `sql_yacc.yy'. 一つは、yacc が定義す べきプリプロセッサシンボルを指示します(これはファイルの先頭に追加すべき です)。それから関数パラメータを定義し、これらのパラメータとともに ``item'' を simple_expr パース規則に追加します。例えば、これがど のように動作するかを見るには、`sql_yacc.yy' 内の ATAN の 全ての出来事をチェックしてください。
    3. `item_func.h' 内で、関数が数値または文字列のどちらを返すかに依存し て、Item_num_func または Item_str_func から継承するクラス を宣言してください。
    4. `item_func.cc' 内で、数値または文字列のどちらの関数を定義するかに依 存して、次の宣言の一つを追加してください: 
      double   Item_func_newname::val()
longlong Item_func_newname::val_int()
String  *Item_func_newname::Str(String *str)
      If you inherit your object from any of the standard items (like Item_num_func you probably only have to define one of the above functions and let the parent object take care of the other functions. For example, the Item_str_func class defines a val() function that executes atof() on the value returned by ::str().
    5. おそらく次のオブジェクト関数も定義すべきです 
      void Item_func_newname::fix_length_and_dec()
      この関数は与えられた引数に基づいて少なくとも max_length を計算す べきです。max_length は関数が返し得る文字の最大数です。この関数は、 メイン関数が NULL 値を返すことがない場合は、maybe_null = 0 も設定すべきです。関数は、引数の maybe_null 変数をチェックするこ とで、関数の任意の引数が NULL を返しうるかどうかをチェックできま す。 You can take a look at Item_func_mod::fix_length_and_dec for a typical example of how to do this.

    全ての関数はスレッド安全である必要があります (In other words, don't use any global or static variables in the functions without protecting them with mutexes).

    If you want to return NULL, from ::val(), ::val_int() or ::str() you should set null_value to 1 and return 0.

    ::str() オブジェクト関数については、次のいくつかの追加検討事項があ ります:

    • String *str 引数は、結果を保持するために使用される文字列バッファ を提供します。 (For more information about the String type, take a look at the `sql_string.h' file.)
    • The ::str() function should return the string that holds the result or (char*) 0 if the result is NULL.
    • 全ての現在の文字列関数は、絶対に必要でない限り、メモリ割り当てを避けるよ うに試みてください！

    9.3 MySQLにプロシージャを追加する

    MySQL ではC++で書かれたプロシージャを定義することが できます。 これらのプロシージャを使うとデータが クライアントに送信される前にクエリー内でデータにアクセス、 修正することが可能です。 データの修正は列単位、あるいは グループ単位(GROUP BY)で行えます。

    プロシージャを使って何ができるかをご覧いただくために、 MySQL バージョン3.23を使ったサンプルを用意しました。

    さらに Contrib ディレクトリにある 'mylua' を参考にされることをお薦めします。 「B Contributed Programs」節参照。 myluaではLUA言語を使って、 ランタイム時にプロシージャを mysqld にロードすることができます。

    Additionally we recommend you to take a look at mylua. With this you can use the LUA language to load a procedure at runtime into mysqld.

    9.3.1 プロシージャ分析

    analyse([max elements,[max memory]])

    このプロシージャは `sql/sql_analyse.cc' によって定義されています。 クエリーの結果を調べ、 分析結果を返します：

    • max elements (デフォルト値は256)とは、 一つの行において analyse プロシージャが認識する値の数(重複するものは除く)の 最大値です。 最大エレメント数は analyse プロシージャがその行に 最適なデータ型が ENUM 型であるかどうかを判別するために使 われます。
    • max memory(デフォルト値は8192)とは、 analyse プロシージャが 1つの行に含まれる重複しない全ての値を探し出す際に、 1つの行に 割り当てるメモリーの最大サイズです。 
    SELECT ... FROM ... WHERE ... PROCEDURE ANALYSE([max elements,[max memory]])

    9.3.2 プロシージャの記述

    今のところ、 この項目にはソースコードしかありません。

    プロシージャに関する全ての情報は以下のファイルにありますのでご覧下さい：

    • `sql/sql_analyse.cc'
    • `sql/procedure.h'
    • `sql/procedure.cc'
    • `sql/sql_select.cc'

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja.texi0100644000175100001560001074525110021471256014417 0ustar takeshisa\input texinfo @c -*-texinfo-*- @c Copyright 1997-2003 TcX AB, Detron HB and MySQL Finland AB @c @c This manual is NOT distributed under a GPL style license. @c Use of the manual is subject to the following terms: @c - Conversion to other formats is allowed, but the actual @c content may not be altered or edited in any way. @c - You may create a printed copy for your own personal use. @c - For all other uses, such as selling printed copies or @c using (parts of) the manual in another publication, @c prior written agreement from MySQL AB is required. @c @c Please e-mail docs@mysql.com for more information or if @c you are interested in doing a translation. @c @c ********************************************************* @c Note that @node names are used on our web site. @c So do not change node names without checking @c Makefile.am and SitePages first. @c ********************************************************* @c @c %**start of header @c there's a better way to do this... i just don't know it yet @c sed will remove the "@c ifnusphere " to make this valid @c ifnusphere @set nusphere 1 @setfilename mysql.info @c We want the types in the same index @syncodeindex tp fn @c Get version information. This file is generated by the Makefile!! @include include.texi @ifclear tex-debug @c This removes the black squares in the right margin @finalout @end ifclear @c Set background for HTML @set _body_tags BGCOLOR=silver TEXT=#000000 LINK=#101090 VLINK=#7030B0 @c Set some style elements for the manual in HTML form. 'suggested' @c natural language colors: aqua, black, blue, fuchsia, gray, green, @c lime, maroon, navy, olive, purple, red, silver, teal, white, and @c yellow. From Steeve Buehler @set _extra_head @settitle MySQL Reference Manual for version @value{mysql_version}. @c We want single-sided heading format, with chapters on new pages. To @c get double-sided format change 'on' below to 'odd' @ifclear nusphere @setchapternewpage on @end ifclear @c %@ifset nusphere @c %@setchapternewpage odd @c %@end ifset @afourpaper @paragraphindent 0 @c %@ifset nusphere @c %@smallbook @c %@end ifset @c %**end of header @ifinfo @format START-INFO-DIR-ENTRY * mysql: (mysql). MySQL documentation. END-INFO-DIR-ENTRY @end format @end ifinfo @titlepage @sp 10 @center @titlefont{MySQL Reference Manual} @sp 10 @center Copyright @copyright{} 1997-2003 MySQL AB @c blank page after title page makes page 1 be a page front. @c also makes the back of the title page blank. @page @end titlepage @c Short contents, blank page, long contents. @c until i can figure out the blank page, no short contents. @c @shortcontents @c @page @c @page @contents @c This should be added. The HTML conversion also needs a MySQL version @c number somewhere. @iftex @c change this to double if you want formatting for double-sided @c printing @headings single @oddheading @thischapter @| @| @thispage @evenheading @thispage @| @| MySQL Technical Reference for Version @value{mysql_version} @end iftex @node Top, Introduction, (dir), (dir) @ifinfo これは @strong{MySQL Database System} のリファレンスマニュアルです。 これは @strong{MySQL Server} バージョン @value{mysql_version} について記述しています。 @code{MySQL Server} の特定の古いバージョンのマニュアルは、そのバージョン のバイナリまたはソースディストリビューションに見つけることができます。 @end ifinfo @menu * Introduction:: General Information * Installing:: Installing MySQL * Tutorial:: MySQL Tutorial * MySQL Database Administration:: Database Administration * MySQL Optimisation:: MySQL Optimisation * Reference:: MySQL Language Reference * Table types:: MySQL Table Types * Clients:: MySQL Client Tools and APIs * Extending MySQL:: Extending MySQL * Problems:: Problems * Contrib:: Contributed Programs * Credits:: Contributors to MySQL * News:: MySQL Change History * Porting:: Porting to Other Systems * Environment variables:: MySQL environment variables * Regexp:: MySQL Regular Expression Syntax * GPL license:: GNU General Public License * LGPL license:: GNU Lesser General Public License * Function Index:: SQL Command, Type and Function Index * Concept Index:: Concept Index @end menu @node Introduction, Installing, Top, Top @chapter 概要 @cindex overview @cindex general information @code{MySQL (TM)} ソフトウェアはとても高速で、マルチスレッド、マルチユーザの、頑丈な @code{SQL} (@code{Structured Query Language})データベースサーバです。 @code{MySQL Server} は、大量に配備されるフトウェアへ組み込まれるときと同じように、 ミッションクリティカルで高負荷な生産システム用に意図されています。 @code{MySQL} は @code{MySQL AB} の商標です。 @code{MySQL} ソフトウェア は @code{デュアルライセンス} です。 あなたは、@code{MySQL} を @code{GNU GENERAL PUBLIC LICENSE} (@uref{http://www.gnu.org/licenses/}) にしたがって、 @code{Open Source}/@code{Free Software} として利用できます。 あるいは、GPL の条件が合わない場合には、 コマーシャルライセンスを @code{MySQL AB} から購入することも可能です。 @xref{Licensing and Support}. @code{MySQL} ウェブサイト (@uref{http://www.mysql.com/}) には @code{MySQL} ソフトウェア についての最新情報があります。 次のリストはマニュアルのなかで特に興味を引くいくつかの節を説明しています: @itemize @bullet @item @code{MySQL Database Server} の背景にある会社についての情報は、@ref{What is MySQL AB} を 参照してください。 @item @code{MySQL Database Server} の能力の説明については、@ref{Features} を参照してください。 @item インストール方法については @ref{Installing} を参照してください。 @item @code{MySQL Database Software} を新しいアーキテクチャや OS に移行するためのヒントについては @ref{Porting} を参照してください。 @item 3.23 リリースからのアップグレードについての情報は、 @ref{Upgrading-from-3.23} を参照してください。 @item 3.22 リリースからのアップグレードについての情報は、 @ref{Upgrading-from-3.22} を参照してください。 @item @code{MySQL Database Server} 導入のチュートリアルについては、@ref{Tutorial} を参照してください。 @item @code{SQL} の例とベンチマーク情報についてはベンチマーキングのディレクトリを参照 してください。(@file{sql-bench} ディレクトリです) @item 新しい機能とバグ修正の履歴については @ref{News} を参照してください。 @item 現在知られているバグと無い機能の一覧については @ref{Bugs} を参照してくだ さい。 @item 将来の計画については @ref{TODO} を参照してください。 @item このプロジェクトへの全ての貢献者のリストについては @ref{Credits} を参照してくだ さい。 @end itemize @strong{重要}: エラー(バグ)レポート、質問、コメントは メーリングリスト @email{mysql@@lists.mysql.com} に送ってください。@xref{Bug reports}。 バグレポートを生成するためには @code{mysqlbug} スクリプトを使用すべきです。 ソースディストリビューションでは、@code{mysqlbug} スクリプトは @file{scripts} ディレクトリ に見つけることができます。バイナリディストリビューションでは、@code{mysqlbug} は @file{bin} ディレクトリ(@code{MySQL-server} RPM パッケージでは @file{/usr/bin}) に見つけることができます。 @code{MySQL Server} のセキュリティバグを発見した場合は、 @email{security@@mysql.com} に email を送ってください。 @cindex errors, reporting @cindex reporting, errors @cindex mailing list address @cindex @code{mysqlbug} script, location @menu * Manual-info:: このマニュアルについて * What-is:: MySQLとは何か * What is MySQL AB:: MySQL AB とは何か * Licensing and Support:: MySQL ライセンスとサポート * MySQL 4.0 In A Nutshell:: MySQL 4.x In A Nutshell * MySQL Information Sources:: MySQL についての情報源 * Compatibility:: MySQL はどのように標準互換か？ * TODO:: MySQL and the future (The TODO) * Comparisons:: MySQL と他のオープンソースデータベースの比較 @end menu @node Manual-info, What-is, Introduction, Introduction @section このマニュアルについて @cindex online location of manual @cindex manual, online location これは @code{MySQL} のリファレンスマニュアルです; これは @code{MySQL} バージョン @value{mysql_version} について記述しています。 機能上の変更は、かならずそのバージョンを示されます。 そのため、@code{MySQL}ソフトウェアの古いバージョンを使っていても、 このマニュアルは通用します。 これはリファレンスマニュアルであるので、一般的な @code{SQL} やリレーショナルデータベース概念の説明書ではありません。 @code{MySQL Database Software} は発展中なので、マニュアルは頻繁に更新されます。そのため、 オンラインで参照しない限り、このバージョンが期限切れである可能性があります。 このマニュアルの最新バージョンは @uref{http://www.mysql.com/documentation/} に多 様な形式で置いてあります。 このマニュアルは現在 HTML, PDF, Windows HLP バージョンがあります。 @cindex manual, available formats @cindex Texinfo プライマリドキュメントは Texinfo ファイルです。HTML バージョンは @code{texi2html} の変更されたバージョンで自動的に提供されます。プレーン テキストと Info バージョンは @code{makeinfo} で提供されます。PostScript バージョンは @code{texi2dvi} と @code{divps} を使用して提供されます。PDF バージョンは @code{pdftex} で提供されます。 マニュアル内の情報を見つけるのがつらいなら、 検索可能なバージョン @uref{http://www.mysql.com/doc/} を 試せます。 このマニュアルへの追加または修正に関連する提案がある場合には、それらを マニュアルチーム @email{docs@@mysql.com} に 送ってください。 このマニュアルは当初、David Axmark, Michael (Monty) Widenius によって書かれました。 現在は Michael (Monty) Widenius, Arjen Lentz, Paul DuBois によって維持されています。他の貢献者については @ref{Credits} を参照してください。 日本語訳は、以下の方々により行われました。 (ハンドル名だけ書きます。敬称略。翻訳サーバに登録した順 :) )： @itemize @bullet @item とみたまさひろ @item hama @item dale @item kippara @item kenji @item aoki @item tok21108 @item こむら @item tamori @item ynakata @item Ami @item bfujii @item Tomo-p @item tanabe @item takayuki.w @item tomoyuki @item piyo @item toshibo @end itemize このマニュアルの著作権(2003)は、スウェーデンの会社 @code{MySQL AB}が所有しています。@xref{Copyright}. @menu * Manual conventions:: Conventions Used in This Manual @end menu @node Manual conventions, , Manual-info, Manual-info @subsection このマニュアル中で使用されている表記 @c We use British English. But let's not publicise that here yet ;-) このマニュアルは特定の印刷上の表記を使用しています: @cindex manual, typographical conventions @cindex typographical conventions @cindex conventions, typographical @table @asis @item @code{constant} 固定幅フォントは次のものに使用されます。コマンド名, オプション; SQL ステー トメント; データベース名, テーブル名, フィールド名; C と Perl コード; 環境変数。 例: ``@code{mysqladmin} がどのように動作するかを見るためには、 @code{--help} オプションをつけて起動してください。'' @item @file{filename} 引用符で括られた固定幅フォントはファイル名とパス名に使用されます。例: `` ディストリビューションは @file{/usr/local} ディレクトリ配下にインストールされます。'' @item @samp{c} 引用符で括られた固定幅フォントは文字シーケンスを示すためにも使用されます。 例: ``ワイルドカードを指定するためには、@samp{%} 文字を使用してください。'' @item @emph{italic} イタリックフォントは強調のために使用されます, @emph{このように}。 @item @strong{boldface} ボールドフォントは table headings と、 @strong{特に強い強調}を伝えるために使用されます。 @end table コマンドが特定のプログラムによって実行されることを意味することを表すときには、 コマンドと共に表示されるプロンプトによって、そのプログラムを表します。例えば、 @code{shell>} は、あなたのログインシェルから実行するコマンドを表し、 @code{mysql>} は @code{mysql} クライアントプログラムから実行するコマンドを表します: シェルコマンドは Bourne シェル構文で示されます。@code{csh} 形式のシェ ルを使用している場合は、わずかに変更してコマンドを発行する必要があるでしょ う。例えば、環境変数を設定してコマンドを実行するシーケンスは、Bourne シェ ル構文では次のようになります: @example shell> VARNAME=value some_command @end example @cindex shell syntax @cindex command syntax @code{csh} では、次のようなシーケンスを実行してください: @example shell> setenv VARNAME value shell> some_command @end example データベース名、テーブル名、フィールド名はコマンドの中で置換しなければいけない ことがよくあります。このような置換が必要なことを示すために、このマニュア ルは @code{db_name}、@code{tbl_name}、@code{col_name} を使用します。 例えば、次のような文を見た場合: @example mysql> SELECT col_name FROM db_name.tbl_name; @end example これは、同様の文を入力するためには、おそらく次のように、あな た自身のデータベース名, テーブル名, フィールド名を与えることを意味します: @example mysql> SELECT author_name FROM biblio_db.author_list; @end example SQL 文は大文字でも小文字でも記述できます。このマニュアルで は大文字で記述します。 構文の説明中では、角括弧(@samp{[} と @samp{]})はオプションの単語や節であ ることを示すために使用されます。次の文、@code{IF EXISTS}はオプションです: @example DROP TABLE [IF EXISTS] tbl_name @end example 構文要素がいくつかのものからなる場合、垂直バー(@samp{|})で区切られます。 選択セットから一つのメンバを選ぶことができるときは、角括弧中に列挙され ます。(@samp{[} と @samp{]}): @example TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str) @end example 選択セットから一つのメンバを選ぶ必要があるときは、波括弧(@samp{@{} と @samp{@}})中に列挙されます: @example @{DESCRIBE | DESC@} tbl_name @{col_name | wild@} @end example @node What-is, What is MySQL AB, Manual-info, Introduction @section MySQL とは何か @cindex MySQL, defined @cindex MySQL, introduction @code{MySQL}は、もっとも有名な @code{オープンソース} SQLデータベースで、 @code{MySQL AB} によって開発、供給されています。@code{MySQL AB} は @code{MySQL} データベースに関わるサービスを提供するビジネスを構築する 営利会社です。@xref{What is MySQL AB}. @code{MySQL} ウェブサイト(@uref{http://www.mysql.com/})は、@code{MySQL} と @code{MySQL AB} に ついての最新情報を提供しています。 @table @asis @item @code{MySQL} はデータベース管理システムです。 データベースはデータの集まりで構成されています。絵画のギャラリーの単純な ショッピングリストや共通ネットワーク内での膨大な量の情報からもなり得ます。 コンピュータデータベースに格納されたデータの追加、アクセス、処理のために は、@code{MySQL} サーバのようなデータベース管理システムが必要です。コンピュー タは大量のデータの処理がたいへん得意なので、データベース管理システムは 単独で動作するユーティリティや他のアプリケーションの一部として、コンピュー タの中で中心的な役割を演じています。 @cindex databases, defined @item MySQL は関係データベース管理システムです。 関係データベースはデータを大きな格納場所に全てのデータを置くのではなく、 別々のテーブル内に格納します。これは速度と柔軟性を追加します。要求された いくつかのテーブルからデータを結合することを可能とする関係を定義すること により、テーブルがリンクされます。@code{MySQL} の @code{SQL} 部分は "構造化問合せ 言語 (@code{Structured Query Language})" を表しています。これは、データベー スのアクセスに使用される最も有名な標準言語です。 @cindex relational databases, defined @cindex SQL, defined @item MySQL ソフトウェアは @code{オープンソース} です。 @code{オープンソース}の意味は誰でも使用し変更することができるということです。誰 でも @code{MySQL} ソフトウェアをインターネットからダウンロードし、無償で使 えます。その気があれば誰でも必要に応じてソースコードを調べ、 変更できます。@code{MySQL} ソフトウェア は @code{GPL} (@code{GNU General Public License}) @uref{http://www.gnu.org/licenses/} にしたがいます。これは、様々な状況でそ のソフトウェアで行えることと行えないことを定義しています。もし @code{GPL} を嫌だと感じていたり、@code{MySQL} を商用アプリケーションに組み込む必 要があるなら、商用ライセンス版を私たちから購入することができます。 @xref{MySQL licenses}. @cindex @code{Open Source}, defined @cindex General Public License @item 何故 MySQL データベースサーバを使用するのか？ @code{MySQL Database Server} はとても速く、信頼でき、簡単に使用できます。それがあなた が探しているものなら、試してみるべきです。@code{MySQL Server} は、私たちのユー ザと協力して開発されたとても実用的な機能がひとそろいあります。私たちのベ ンチマークページ上で、@code{MySQL Server} と他のいくつかのデータベース管理シ ステムの性能比較を見つけることができます。@xref{MySQL Benchmarks}. @code{MySQL Server} は、既存のソリューションよりも速く、とても大きなデータベー スを処理するために独自に開発され、そして、高い需要がある実運用環境で何年間もの使用に耐え てきました。不断の開発下で、@code{MySQL Server} は今日、 豊富でとても有用な機能セットを提供します。MySQL は、結合性、速 度、セキュリティでインターネット上でのデータベースアクセスに高く適合しま す。 @item MySQL の技術機能。 詳しい技術情報については、@ref{Reference}。@code{MySQL Database Software} は、様々なバッ クエンドをサポートするマルチスレッド @code{SQL} サーバ、いくつかのクライアント プログラム、ライブラリ、管理ツール、プログラミングインタフェース(@code{API})から成る クライアント／サーバシステムです。 また、@code{MySQL サーバ} をアプリケーションに リンクできるマルチスレッドライブラリとしても提供していて、これにより、 より小さく、速く、管理しやすい製品が作れます。 @item MySQL は多くの貢献ソフトを持っています。 おそらく、すでに @code{MySQL Database Server} をサポートする、あなたの好きなアプリケー ション／言語を見つけることができるでしょう。 @end table @cindex pronunciation, MySQL @cindex MySQL, pronunciation @cindex goals of MySQL @code{MySQL} の公式な発音は ``My Ess Que Ell'' です(MY-SEQUEL ではあり ません)。 しかし MY-SEQUEL と発音する人を正すことは避けています。 @menu * History:: History of MySQL * Features:: The Main Features of MySQL * Stability:: How Stable Is MySQL? * Table size:: How Big Can MySQL Tables Be? * Year 2000 compliance:: Year 2000 Compliance @end menu @node History, Features, What-is, What-is @subsection MySQL の歴史 @cindex MySQL history @cindex history of MySQL @cindex MySQL name @cindex My, derivation 最初は、私たち自身の速くて低レベルな (ISAM) ルーチンを使用したテーブルへ 接続するために、 @code{mSQL} を使用するつもりでした。 しかし、いくつかのテストの後、私たちは @code{mSQL} は私たちが必要とするほど高速ではなく、柔軟でないという 結論に至りました。この結果、@code{mSQL} とほとんど同じ API インタフェー スをもつ、私たちのデータベースへの新しい SQL インタフェースに帰結しました。 この API はサードパーティコードの移植を簡単にするために選択されました。 @code{MySQL} の名前の由来は完全には明らかではありません。私たちのベース ディレクトリと多くのライブラリとツールは接頭辞 ``my'' を 10 年以上も使っ ています。しかし、Monty の娘(何年か若い)も My という名前です。そのため、 この2つのどちらが @code{MySQL} に名前を与えたかは、私たちにとっても未だ 謎です。 @node Features, Stability, History, What-is @subsection MySQL の主な機能 @cindex main features of MySQL @cindex features of MySQL @code{MySQL Database Software} の重要な特徴のいくつかを以下の項目に挙げます。 @xref{MySQL 4.0 In A Nutshell}. @c This list is too technical and should be divided into one feature @c list comparable to commercial competition and a very technical on @c with max limits (from crash-me) and so on. @table @asis @item 内部と移植性 @itemize @bullet @item C と C++ で書かれています。広範な種類のコンパイラでテストされています。 @item 多くの種類のプラットフォームで動作します。@xref{Which OS}。 @item 可搬性のために GNU Automake, Autoconf, Libtool を使用しています。 @item C, C++, Ruby, Eiffel, Java, Perl, PHP, Python そして Tcl に対する API。 @xref{Clients}. @item カーネルスレッドを使用する完全なマルチスレッド。これは可能ならば簡単に 複数の CPU を使用できることを意味します。 @item インデックス圧縮付きのとても速い B-tree ディスクテーブル。 @item とても速いスレッドベースのメモリ割り当てシステム。 @item 最適化された one-sweep multi-join を使用する高速な結合。 @item 一時テーブルとして使用されるメモリ内ハッシュテーブル。 @item SQL 関数は高度に最適化されたクラスライブラリを通して実装されていて、限界に 近いほど高速化されています。 普通、クエリの初期化の後に は、全くメモリ割り当てはありません。 @item @code{MySQL} は市販のメモリリーク検出製品 Purify と、 Valgrind とよばれる GNU のツール(@uref{http://developer.kde.org/~sewardj/}) で テストされています。 @end itemize @item カラムの型 @itemize @bullet @item 多くのフィールド型: 1, 2, 3, 4, 8 バイト長の符号付き/符号無し整数, @code{FLOAT}, @code{DOUBLE}, @code{CHAR}, @code{VARCHAR}, @code{TEXT}, @code{BLOB}, @code{DATE}, @code{TIME}, @code{DATETIME}, @code{TIMESTAMP}, @code{YEAR}, @code{SET}, @code{ENUM} 型. @xref{Column types}. @item 固定長と可変長のレコード。 @item @cindex default values 全てのフィールドはデフォルト値をもちます。 テーブル項目のサブセットを挿入するた めに @code{INSERT} を使用でき、明示的に値が与えられていないフィールドはそのデ フォルト値が設定されます。 @end itemize @item コマンドと関数 @itemize @bullet @item クエリの @code{SELECT} と @code{WHERE} 節で全ての演算子と関数が使えます。例: @example mysql> SELECT CONCAT(first_name, " ", last_name) -> FROM tbl_name -> WHERE income/dependents > 10000 AND age > 30; @end example @item SQLの @code{GROUP BY} と @code{ORDER BY} 節の完全なサポート。グループ関数 (@code{COUNT()}, @code{COUNT(DISTINCT ...)}, @code{COUNT(DISTINCT ...)}, @code{AVG()}, @code{STD()}, @code{SUM()}, @code{MAX()} and @code{MIN()} ) のサポート。 @item ANSI SQL と ODBC 構文で @code{LEFT OUTER JOIN}と@code{RIGHT OUTER JOIN} が使えます。 @item SQL92 標準にあるようなテーブルとフィールドのエイリアス名。 @item @code{DELETE}, @code{INSERT}, @code{REPLACE}, @code{UPDATE} は 変更された(影響を受けた)行の数を返します。 サーバ接続時にフラグを設定することにより、代わりに適合したレコード数を返す ことも可能です。 @item @code{MySQL} 固有の @code{SHOW} コマンドはデータベース、テーブル、イン デックスについての情報を取出すために使用できます。@code{EXPLAIN} コマン ドはオプティマイザがどのようにクエリを解析するかを決定するために使用 できます。 @item 関数名はテーブル名やフィールド名と衝突しません。例えば @code{ABS} は正しいフィールド 名です。制限は、関数呼び出しに、関数名とそれに続く @samp{(} の間に空白が 許されないことだけです。 @xref{Reserved words}. @item 同一クエリ内に異なるデータベースからのテーブルを混在できます (バージョン 3.22)。 @end itemize @item セキュリティ @itemize @bullet @item とても柔軟で安全な特権システムとパスワードシステム。 ホストベースの証明が可能です。 サーバに接続するときの全てのパスワードトラフィックは暗号化されているためパ スワードは安全です。 @end itemize @item 拡張性と限界 @itemize @bullet @item 大きなデータベースの操作。私たちは、50,000,000 レコードを含むいくつかのデー タベースで MySQL を使用しています。そして、60,000 テーブル、約 5,000,000,000 レコードを @code{MySQL Server} を使用しているユーザを知っています。 @item テーブル毎に 32 個のインデックスを利用できます。各インデックスは 1 から 16 個 のフィールドまたはフィールドの一部からなります。最大インデックス長は 500 バイトです (これは @code{MySQL Server} のコンパイル時に変更できます)。インデックスは @code{CHAR} または @code{VARCHAR} フィールドの先頭部分を使用できます。 @end itemize @item 接続性 @itemize @bullet @item クライアントは、TCP/IP ソケット、UNIX ソケット(UNIX)、名前つきパイプ(NT)を 使用して @code{MySQL} サーバと接続します。 @item Win32 の @code{ODBC} (Open-DataBase-Connectivity) (ソースつき)。全ての ODBC 2.5 関数と他の多く。あなたの @code{MySQL} サーバに接続するために、例え ば Access を使用できます。 @xref{ODBC}. @end itemize @item 地域化 @itemize @bullet @item サーバは，クライアントに対し，多言語のエラーメッセージを提供することができます。 @xref{Languages}. @item 異なるキャラクタセットの完全なサポート。ISO-8859-1 (Latin1), big5, ujis など。 例えば、スカンジナビア語文字 @ringaccent{a}, @"a そして @"o はテーブル名や フィールド名として許されます。 @item 全てのデータは 選択されたキャラクタセットの形式で保存されています。通常文字列フィールド の全ての比較はケース非依存です。 @item ソートは、@code{MySQL} サーバ起動時に、選択されたキャラクタセットに にしたがって行われます。(デフォルトは、スウェーデン語の方法)。 ソース内に新しいソート順序配列を追加することで、こ れは変更可能です。とても先進的なソートの例を見るには、Czech ソートコード を見てください。 @code{MySQL Server} は多くの種類のキャラクタセットをサポート し、コンパイル時や実行時に指定できます。 @end itemize @item クライアントとツール @itemize @bullet @item @code{myisamchk} を含んでいます。これは、テーブル検査、最適化、修復のため のとても速いユーティリティです。 @code{myisamchk} のすべての機能は、SQLインタフェースからも使えます。 @xref{MySQL Database Administration}. @item 全ての @code{MySQL} プログラムは @code{--help} と @code{-?} オプションでオンラインヘルプを呼び出せます。 @end itemize @end table @node Stability, Table size, Features, What-is @subsection MySQL はどれくらい安定か？ @cindex stability この節では、``MySQL Server はどれくらい安定か？'' と ``私はこのプロジェ クトの MySQL Server に依存できるか？'' という質問について回答します。 私たちはここで、いくつかの問題を明らかにし、多くの人に関係すると思われるさ らに重要な質問のいくつかを回答することを試みます。この節は、メーリングリ スト(そこではとても活発にバグが報告されています)から取り込まれた情報が一 緒に置かれています。 80年代初期からあるオリジナルのコードの中心部は、安定したコードの基礎とな っています。ISAMテーブル形式は、後方互換性が保たれています。TcX (@code{MySQL AB} の前身)では、@code{MySQL} は 1996 中頃から私たちのプロジ ェクトで何の問題もなく動いていました。@code{MySQL Database Software} が 広く公にリリースされたとき、私たちは、MySQL 内に ``テストされていないコード '' の部分があることに注意しました。これは、私たちとは異なる方法でクエリを 作成する新しいユーザによってすぐに見つけられました。新しい各リリースは、 (多くの新しい機能を持っているのに)前のものよりも問題は少なくなります。そ して次のリリースの一つを ``安定'' と呼ぶことができるように私たちは望んでい ます。 @code{MySQL Server} の各リリースは実用的で、ユーザが ``グレイゾーン'' か らのコードの使用を開始するときにだけ問題があります。当然、外部のユーザは、 何がグレイゾーンかを知ることができません; この節で現在知られているこれら を示してみます。説明は @code{MySQL Server} の 3.23.x バージョンで扱われ ます。知られていて報告されているバグは全て最新のバージョンで修正されてい ます。バグ節に書かれているバグは除きます。それらは ``設計'' 関連のもので す。@xref{Bugs}. @code{MySQL Server} は複数の階層と様々な独立モジュールで書かれています。 これらのモジュールは、それぞれがどのようにテストされているかとともに次に 列挙されています: @cindex modules, list of @table @strong @item Replication -- Gamma レプリケーションを使用した大規模なサーバクラスタは製品として使用され良い 結果をもたらしています。拡張されたレプリケーション機能に対する取り組みは @code{MySQL} 4.x でも引き続き行われます。 @item @code{InnoDB} tables -- Stable (3.23 では 3.23.49から) @code{InnoDB} storage engines は @code{MySQL} 3.23 ツリーでは version 3.23.49 から安定です。@code{InnoDB} は大規模で負荷の大きい製品システムで 使用されています。 @item @code{BDB} tables -- Gamma @code{Berkeley DB}はとても安定したコードですが、未だに @code{BDB} トラン ザクションstorage engines インターフェースに対し @code{MySQL Server} で は改良を加えている途中であり、他のテーブルタイプと同等に扱われるまでには もう少し時間がかかりそうです。 @item @code{FULLTEXT} -- Beta テキストの検索は動作しているように見えますが、まだ広く使用されていません。 重要な拡張を @code{MySQL} 4.0 で行っています。 @item @code{MyODBC 3.51} (uses ODBC SDK 3.51) -- Gamma だんだん広く使われるようになっています。アプリケーションに関係したり、 ODBCドライバーか、その下のデータベースサーバに関係ない問題が出ています。 @item @code{MyISAM} テーブルの自動復旧 -- Gamma これは、@code{MyISAM} ストレージエンジンの新しいコードに対してだけです。 新しい @code{MyISAM} ストレージエンジンは、テーブルをオープンするとき、 前にそのテーブルが正しくクローズされたか調べ、正しくクローズされていない ときは自動的に検査と復旧を実行します。 @item Bulk-insert -- Alpha @code{MySQL} 4.0 での @code{MyISAM} テーブルへ大量のレコードを高速に挿入 する新しい機能です。 @item ロック --- ガンマ これはとてもシステムに依存しています。いくつかのシステムでは、これは、標 準 OS ロック (@code{fcntl()}) を使用するため大きな問題があります。これら の場合では、MySQL デーモンを @code{--skip-external-locking} フラグつきで 動かすべきです。知られている問題は、いくつかの Linux システムと NFS マウ ントされたファイルシステム使用時の SunOS です。 @end table @code{MySQL AB} は代金を支払った顧客のために 高サポートを提供しています。 しかし @code{MySQL} メーリングリストは通常、全ての一般的な質問に回答を提 供しています。バグは通常すぐにパッチで修正され、深刻なバグには、ほとんど いつも新しいリリースがあります。 @node Table size, Year 2000 compliance, Stability, What-is @subsection MySQLではどれだけテーブルを大きくできるの？ @cindex tables, maximum size @cindex size of tables @cindex operating systems, file-size limits @cindex limits, file-size @cindex files, size limits @code{MySQL} Version 3.22では、最大テーブルサイズに 4Gバイトという制限が ありました。@code{MySQL} Version 3.23から採用された新しい @code{MyISAM} では、最大テーブルサイズは800万テラバイト( 2 ^ 63 バイト)に拡張されまし た。 ただし、OSの側にも、ファイルサイズの制限が存在していることには注意して下 さい。いくつか例を示します： @multitable @columnfractions .5 .5 @item @strong{オペレーティングシステム} @tab @strong{ファイルサイズの制限} @item Linux-Intel 32 bit @tab 2Gバイト, 4Gバイト あるいはそれ以上, Linux のバージョンによる。 @item Linux-Alpha @tab 8Tバイト (?) @item Solaris 2.5.1 @tab 2Gバイト (パッチにより 4G に対応) @item Solaris 2.6 @tab 4Gバイト (フラグで変更可能) @item Solaris 2.7 Intel @tab 4Gバイト @item Solaris 2.7 UltraSPARC @tab 512Gバイト @end multitable Linux 2.2 では、ext2ファイルシステム用のLFSパッチを適用することで、2G バ イト以上のテーブルを使用することができます。Linux 2.4ではReiserFS用の同 様のパッチが存在し、大きなファイルを扱うことができるようになります。(訳 注： Linux 2.4.1 以上では、最初から ReiserFS がカーネルのソースに組み込 まれていますし、2.4.16 以上では、ext3 もカーネルのソースに組み込まれまし た) 以上からわかるように、@code{MySQL} の最大テーブルサイズはOSの制限によっ て決まることがほとんどです。 デフォルトでは、@code{MySQL} の最大テーブルサイズは4Gに設定されています。 あるテーブルの最大テーブルサイズは、@code{SHOW TABLE STATUS} コマンドか、 @code{myisamchk -dv table_name} によって確認することができます。 @xref{SHOW}. もしも4G 以上のテーブルが必要な場合には（加えて、OSがそれをサポートして いる場合には）、テーブルを作る際に、@code{AVG_ROW_LENGTH} と @code{MAX_ROWS} パラメータを設定することができます。@xref{CREATE TABLE}. テーブル作成後に、@code{ALTER TABLE} で変更することもできます。 @xref{ALTER TABLE} 読み込み専用の大きなテーブルが必要なときは、@code{myisampack}を使って複 数のテーブルを一つにまとめた上で圧縮することができます。@code{myisampack} は、テーブルの大きさをだいたい50%程度まで圧縮できます。結果として、より 大きなテーブルを作ることが可能となるでしょう。@xref{myisampack, ,@code{myisampack}}. @code{MyISAM}データファイルに対する、OSのファイル制限を回避するのに、 @code{RAID} オプションを使うこともできます。@xref{CREATE TABLE}. @code{MERGE} ライブラリ -- 同じ構造のテーブルをひとまとめに扱う機能を提 供します -- を使用するという解決法も考えられるでしょう。@xref{MERGE, , @code{MERGE} tables}. @node Year 2000 compliance, , Table size, What-is @subsection 2000 年対応 @cindex Year 2000 compliance @cindex compliance, Y2K @cindex date functions, Y2K compliance @code{MySQL Server} 自身は 2000 年問題(Y2K)に対して何の問題も持っていま せん: @itemize @bullet @item @code{MySQL Server} は UNIX 時間関数を使用し、@code{2069} 年まで日付には 何の問題もありません; 全ての2桁の年は @code{1970} から @code{2069} の範 囲にあると見なされます。これは、@code{year} フィールド内に @code{01} を 格納する場合、@code{MySQL Server} はそれを @code{2001} として扱うという ことを意味します。 @item 全ての @code{MySQL} 日付関数は一つのファイル @file{sql/time.cc} に格納さ れ、2000年安全であるようにとても注意深くコード化されています。 @item @code{MySQL} 3.22 以降のバージョンでは、新しい @code{YEAR} フィールド型 は @code{0} と @code{1901} から @code{2155} までの年を1バイトで格納でき、 2桁または4桁で表示できます。 @end itemize 2000年安全でない方法で @code{MySQL Server} を使用するアプリケーションで は問題になります。例えば、多くの古いアプリケーションは4桁値ではなく2桁値 (これは曖昧です)を使用して年を格納し操作します。この問題は、@code{00} ま たは @code{99} のような値を ``欠けている'' 値の表われとして使用するアプ リケーションによって作られます。 あいにく、これらの問題を修正するのは困難です。様々なアプリケーションが様々 なプログラマによって書かれていて、その各々が慣習と日付操作関数の様々な組 み合わせを使用するからです。 これは、@code{MySQL Server} が 2030 年までの日付に何の問題もないことを示 す簡単なテストです: @example mysql> DROP TABLE IF EXISTS y2k; Query OK, 0 rows affected (0.01 sec) mysql> CREATE TABLE y2k (date DATE, -> date_time DATETIME, -> time_stamp TIMESTAMP); Query OK, 0 rows affected (0.00 sec) mysql> INSERT INTO y2k VALUES -> ("1998-12-31","1998-12-31 23:59:59",19981231235959), -> ("1999-01-01","1999-01-01 00:00:00",19990101000000), -> ("1999-09-09","1999-09-09 23:59:59",19990909235959), -> ("2000-01-01","2000-01-01 00:00:00",20000101000000), -> ("2000-02-28","2000-02-28 00:00:00",20000228000000), -> ("2000-02-29","2000-02-29 00:00:00",20000229000000), -> ("2000-03-01","2000-03-01 00:00:00",20000301000000), -> ("2000-12-31","2000-12-31 23:59:59",20001231235959), -> ("2001-01-01","2001-01-01 00:00:00",20010101000000), -> ("2004-12-31","2004-12-31 23:59:59",20041231235959), -> ("2005-01-01","2005-01-01 00:00:00",20050101000000), -> ("2030-01-01","2030-01-01 00:00:00",20300101000000), -> ("2050-01-01","2050-01-01 00:00:00",20500101000000); Query OK, 13 rows affected (0.01 sec) Records: 13 Duplicates: 0 Warnings: 0 mysql> SELECT * FROM y2k; +------------+---------------------+----------------+ | date | date_time | time_stamp | +------------+---------------------+----------------+ | 1998-12-31 | 1998-12-31 23:59:59 | 19981231235959 | | 1999-01-01 | 1999-01-01 00:00:00 | 19990101000000 | | 1999-09-09 | 1999-09-09 23:59:59 | 19990909235959 | | 2000-01-01 | 2000-01-01 00:00:00 | 20000101000000 | | 2000-02-28 | 2000-02-28 00:00:00 | 20000228000000 | | 2000-02-29 | 2000-02-29 00:00:00 | 20000229000000 | | 2000-03-01 | 2000-03-01 00:00:00 | 20000301000000 | | 2000-12-31 | 2000-12-31 23:59:59 | 20001231235959 | | 2001-01-01 | 2001-01-01 00:00:00 | 20010101000000 | | 2004-12-31 | 2004-12-31 23:59:59 | 20041231235959 | | 2005-01-01 | 2005-01-01 00:00:00 | 20050101000000 | | 2030-01-01 | 2030-01-01 00:00:00 | 20300101000000 | | 2050-01-01 | 2050-01-01 00:00:00 | 00000000000000 | +------------+---------------------+----------------+ 13 rows in set (0.00 sec) @end example これは、@code{DATE} と @code{DATETIME} 型は未来のいかなる日付において問 題のないことを示します (これら日付は 9999 年まで扱えます) @code{TIMESTAMP} 型は、時刻を保存しますが、@code{2030-01-01} までです。 @code{TIMESTAMP} は 32-bit マシンで(signed value)は @code{1970} から @code{2030} の範囲です。64-bit マシンでは、 @code{2106} 年(unsigned value)まで扱えれます。 @code{MySQL Server} は 2000年対応ですが、曖昧でない入力を提供するのはあ なたの責任です。曖昧な日付の入力データ（2桁の年の値）の扱いについての @code{MySQL Server} の規則については @ref{Y2K issues} を参照してください。 @node What is MySQL AB, Licensing and Support, What-is, Introduction @section MySQL AB とは何か @cindex MySQL AB, defined @code{MySQL AB} は、MySQL の創始者と主な開発者の会社です。 @code{MySQL AB} は、最初は、David Axmark、Allan Larsson、Michael Monty Wideniusらによってスウェーデンに設立されました。 @code{MySQL} サーバの開発者は、この会社に雇われています。わたしたちは、 世界中の1ダースものの国々の人によるバーチャルな組織です。わたしたちは、 毎日、広くネットを使って、互いに連絡しあい、また、ユーザや支援者やパート ナーと連絡しています。 私たちは、@code{MySQL} の開発と私たちのデータベースを新しいユーザに広げるこ とに専念しています。@code{MySQL AB} は@code{MySQL}サーバソースコードの著 作権, @code{MySQL} logo の著作権, MySQL 商標権,このMySQL マニュアルの著 作権を所有します。@xref{What-is}. @menu * MySQL AB business model and services:: The Business Model and Services of MySQL AB * Contact information:: Contact Information @end menu @code{MySQL}の核の価値は、わたしたちの @code{MySQL} と @code{Open Source} に対する献身を示しています。 私たちは @code{MySQL Database Software} を次のようにしています。 @itemize @bullet @item 世界で一番良く、最も使用されるデータベース @item 全てが有効で全てを与えられる @item 簡単に使用できる @item 速度と安全が残る限り改良を続ける @item 使って楽しく、改良して楽しい @item バグから解放される @end itemize @strong{MySQL AB} と @strong{MySQL AB} の人々は次を行います。 @itemize @bullet @item @code{オープンソース} 哲学を進展させ、@code{オープンソース} コミュニティをサポートする @item 良い市民になることを目指す @item 私たちの価値と心を共有するより良いパートナー @item メールで回答しサポートを提供する @item 他とネットワークする仮想会社です @item ソフトウェア特許に反対して作業します @end itemize MySQL ウェブサイト(@uref{http://www.mysql.com/})は、MySQL と MySQL AB に ついての最新情報を提供しています。 @node MySQL AB business model and services, Contact information, What is MySQL AB, What is MySQL AB @subsection MySQL AB のビジネスモデル及びサポート 私たちが最もよく受ける質問は:「@emph{どのようにして無料で配布して採算を 取っているのでしょうか？}」というものです。それは、このようにしています。 @code{MySQL AB} はサポート、サービス、商用ライセンス及びロイアリティで利 益をあげます。そして、私たちは製品開発と@code{MySQL}の事業を展開するため、 これらの収益を利用します。 @menu * Business Services Support:: Support * Business Services Training:: Training and Certification * Business Services Consulting:: Consulting * Business Services Commercial licenses:: Commercial Licenses * Business Services Partnering:: Partnering * Business Services Advertising:: Advertising @end menu MySQL AB は創業以来、利益が増えています。2001年10月、私たちは有数のスカ ンジナビアの投資家および数少ないビジネスエンジェルからのベンチャー投資に 応じました。この投資は、私たちのビジネス・モデルを固め、持続的成長の基盤 を構築するために使用されます。 @node Business Services Support, Business Services Training, MySQL AB business model and services, MySQL AB business model and services @subsubsection サポート @code{MySQL AB} は、@code{MySQL} データ・ベースの設立者及び主な開発者に より管理・運営されます。開発者は顧客及びその他のユーザの要望・課題を連絡 をとり続けるためのサポートを提供することを約束します。私たちの全てのサポー トは有能な開発者によって提供されます。実際に複雑な質問は、@code{MySQLサ ーバー}の主要な著者である Michael @code{Monty} Widenius が答えます。 @xref{Support}. さらなる情報とサポートの依頼は、@uref{http://www.mysql.com/support/} か、 私たちの販売員 @email{sales@@mysql.com} にご連絡ください。 @node Business Services Training, Business Services Consulting, Business Services Support, MySQL AB business model and services @subsubsection トレーニングと認定 @cindex training @cindex MySQL training @cindex certification @cindex MySQL certification @code{MySQL AB} は @code{MySQL} と関連したトレーニングを世界的に提供しま す。私たちは、一般公募するコースと、あなたの会社のニーズに合せた特別な社内 研修の両方を提供します。@code{MySQL トレーニング} はさらに、私たちのパート ナーである@code{MySQL 認定 トレーニング・センター} でも受講ができます。 私たちのトレーニングの教材は、いくつかのデータベースの実例と資料・説明書、 そしてサンプルアプリケーションを使用します。また、教材は @code{MySQL} の 最新バージョンを反映するために常時更新されます。私たちの講師は、トレーニン グの質と教材の開発を保証するため、常に開発チームにサポートされます。これ は、さらにトレーニング中の質問には必ず回答できることを保証します。 私たちのトレーニング講座に参加することにより、あなたの目標と @code{MySQL} アプリケーションを実現することができるでしょう。さらに以下のことができる でしょう: @itemize @bullet @item 時間を節約します @item アプリケーションの性能を改善します @item 過剰なハードウェアの必要性を低減・解消させ、コストを削減します。 @item セキュリティを強化します。 @item 顧客をや同僚の満足度を増やします。 @item @code{MySQL 認定試験} の準備になります。 @end itemize 参加予定者あるいはトレーニング・パートナーとして私たちのトレーニングに興味 を持っている場合、@uref{http://www.mysql.com/training/}のトレーニング課 にアクセスするか、あるいは @email{training@@mysql.com} にメールで連絡を ください。 @code{MySQL 認定プログラム} についての詳細な情報は ,@uref{http://www.mysql.com/certification/} を参照してください。 @node Business Services Consulting, Business Services Commercial licenses, Business Services Training, MySQL AB business model and services @subsubsection コンサルティング @cindex consulting @cindex MySQL consulting @code{MySQL AB} と @code{認定パートナー} は、全世界の @code{MySQLサーバ} のユーザと@code{MySQLサーバ}を自身のソフトウェアに組み入れようとしている ユーザにコンサルティングサービスを提供します。 わたしたちのコンサルタントは、データベースの設計と調整、効率のよい問合 せの作成、最適な性能のためのプラットホームの調整、移植の問題の解決、レ プリケーションの設定、頑強なトランザクションアプリケーションの作成とい つたことを助けます。 わたしたちは、お客様がご自身のアプリケーションに@code{MySQL Server}を組 み込むことを手助けし、大規模なアプリケーションを作ることを手助けします。 私のコンサルタントは、あなたの開発チームと密接に協力して作業します。この ことは、わたしたちの専門サービスの品質を確実にします。コンサルティングの 割り当ては、2日間の強力開始期間から、何週間も何ヶ月にもわたるプロジェク トに広がります。わたしたちの専門意見は @code{MySQLサーバ} だけを含むので はなく、PHPやPerlやほかのスクリプティング言語とプログラミングにも広がっ ています。 もし、わたしたちのコンサルティングサービスやコンサルティングパートナーに なることに興味をもったときは、私たちのコンサルティングセクションのWeb サ イト @uref{http://www.mysql.com/consulting/} を訪れるか、コンサルティン グスタッフ @email{consulting@@mysql.com} に連絡してください。 @node Business Services Commercial licenses, Business Services Partnering, Business Services Consulting, MySQL AB business model and services @subsubsection 商用ライセンス @code{MySQL} データベースは、@code{GNU General Public License} (@code{GPL}) のもとでリリースされています。これは、@code{MySQL} ソフトウ ェアは @code{GPL} のもと、無償で使えることを意味します。 @code{GPL} の条 件項目(あなたのアプリケーションもまた @code{GPL} にしなければならない)に 束縛されたくないならば、@code{MySQL AB} から同じ製品の商用ライセンスを購 入しなければなりません； @uref{http://www.mysql.com/products/pricing.html}。 @code{MySQL} ソースコードの著作権は @code{MySQL AB} が所有するため、わた したちは @code{デュアルライセンス} を採用することができます。このことは、同 じ製品に @code{GPL} と商用ライセンスの両方があるということです。これはど うあろうと @code{MySQL AB} のオープンソースの遂行には影響しません。商用 ライセンスが必要なときは、@ref{MySQL licenses} を参照してください。 わたしたちは、@code{MySQLサーバ} に機能を追加するサードパーティーの @code{オープンソースGPL} ソフトウェアの商用ライセンスも販売しています。 よい例は、@code{InnoDB} トランザクション対応ストレージエンジンです。この エンジンは、ACIDが使え、低水準のロック、破壊からの回復、マルチバージョニ ング、外部キーが使えるといった特徴があります。 詳しくは @xref{InnoDB} を 参照してください。 @node Business Services Partnering, Business Services Advertising, Business Services Commercial licenses, MySQL AB business model and services @subsubsection パートナー @cindex partnering with MySQL AB @code{MySQL AB} は、トレーニングコース、コンサルティングとサポート、出版、 @code{MySQL} 関連製品の再販と販売に関する、全世界のパートナープログラム をもっています。 @code{MySQL AB} パートナーは、webサイト @uref{http://www.mysql.com/}で公開され、製品を識別しビジネスを推進するた めの @code{MySQL} のトレードマークの特別バージョンを使う権利が得られます。 もし、@code{MySQL AB パートナー}になることに興味をおもちならば、 @email{partner@@mysql.com} に 電子メールを送ってください。 @code{MySQL} の単語と @code{MySQL} のイルカのロゴは、@code{MySQL AB}のトレードマークです。 @xref{MySQL AB Logos and Trademarks}。 このトレードマークは、 @code{MySQL} の創設者が何年にもわたって築いてきた 重要な価値の象徴です。 @node Business Services Advertising, , Business Services Partnering, MySQL AB business model and services @subsubsection 広告 @code{MySQL} のwebサイト (@uref{http://www.mysql.com/})は、開発者とユー ザの間では人気があります。2001年10月で、1千万ページビューがありました。 訪問者は、購入の決定者とソフトウェアとハードウェアの両方の推奨者のグルー プです。訪問者の12%は購入の決定を承認し、たった9%が購入決定に関わってい ませんでした。65%以上が、半年の間に何らかのオンラインビジネスの購入をし ていて、70%が数ヶ月の間に購入を計画していました。 @node Contact information, , MySQL AB business model and services, What is MySQL AB @subsection 連絡先の情報 @cindex contact information @cindex employment, contact information @cindex licensing, contact information @cindex employment with MySQL @cindex jobs at MySQL @code{MySQL} のwebサイト(@uref{http://www.mysql.com/})には@code{MySQL} と @code{MySQL AB} の最新の情報があります。 報道サービスやわたしたちのニュースリリース (@uref{http://www.mysql.com/news/})に書かれていない質問は、 @email{press@@mysql.com} に電子メールを送ってください。 @code{MySQL AB} との間に有効なサポート契約があるならば、あなたは、 @code{MySQL} ソフトウェアの技術的な質問に対する正確な答えがタイムリーに 得られます。より詳しい情報は、@ref{Support}.私たちのwebサイト、 @uref{http://www.mysql.com/support/} を見るか、@email{sales@@mysql.com} にメールを送ってください。 @code{MySQL} トレーニングについての情報は、 @uref{http://www.mysql.com/training/} のトレーニング節を訪れてください。 インターネットにアクセスできないときは、@email{training@@mysql.com} の @code{MySQL AB} トレーニングスタッフに連絡してください。@xref{Business Services Training}。 @code{MySQL 認定プログラム} に関する情報は、 @uref{http://www.mysql.com/certification/}を見てください。@xref{Business Services Training}。 コンサルティングに興味があるならば、 @uref{http://www.mysql.com/consulting/} のコンサルティング部門を見てくだ さい。インターネットにアクセスできないときは、 @email{consulting@@mysql.com} の @code{MySQL AB} コンサルティングスタッ フに連絡してください。@xref{Business Services Consulting}. 商用ライセンスは、@uref{https://order.mysql.com/} でオンラインで購入でき ます。@code{MySQL AB} にどうやって購入のFAXを送るかの情報もあります。よ り詳しい情報は@uref{http://www.mysql.com/products/pricing.html} にありま す。もし、ライセンスに関する質問があったり、大量のライセンスの見積もりが 必要なときは、webサイト(@uref{http://www.mysql.com/})の連絡用紙に記入す るか、@email{licensing@@mysql.com} (ライセンスの質問用)に電子メールを送 るか、@email{sales@@mysql.com} (セールスの見積もり用) に電子メールを送っ てください。@xref{MySQL licenses}. ビジネスで @code{MySQL AB} のパートナーに興味があるときは、 @email{partner@@mysql.com} に電子メールを送ってください。@xref{Business Services Partnering}. @code{MySQL} のトレードマークの考え方は、 h@uref{http://www.mysql.com/company/trademark.html}を見るか、 @email{trademark@@mysql.com} に電子メールを送ってください。@xref{MySQL AB Logos and Trademarks}. もし、@code{MySQL AB} のジョブ選択 (@uref{http://www.mysql.com/company/jobs/})にある仕事に興味があるならば、 @email{jobs@@mysql.com} に電子メールを送ってください。あなたのCV(履歴書) は添付しないで、プレーンテキストであなたの電子ールの最後につけてください。 多くのユーザの間の一般的な議論は、適切なメーリングリストに注意してくだい。 @xref{Questions}. エラー(多くの場合はバグと呼ばれます)の報告、同じように質問やコメントは、 @email{mysql@@lists.mysql.com} のメーリングリストに送ってください。 @code{MySQLサーバ} に要注意のセキュリティホールが見つかったときは、 @email{security@@mysql.com} に電子メールを出してください。@xref{Bug reports}. 公開してよいベンチマークの結果があるときは、@email{benchmarks@@mysql.com} に連絡してください。 このマニュアルに対する追加や修正は、@email{docs@@mysql.com} のマニュアル チームに連絡してください。 @code{MySQL} のwebサイト(@uref{http://www.mysql.com/})に対する作業や内容 のコメントや質問は、@email{webmaster@@mysql.com} に電子メールを出してく ださい。 @code{MySQL AB} にはプライバシーポリシーがあります。それは、 @uref{http://www.mysql.com/company/privacy.html} で読めます。このポリシ ーに関して質問があれば @email{privacy@@mysql.com} に電子メールを送ってく ださい。 その他の質問は、@email{info@@mysql.com} に電子メールを送ってください。 @node Licensing and Support, MySQL 4.0 In A Nutshell, What is MySQL AB, Introduction @section MySQL ライセンスとサポート (訳注： ライセンスの章については、正確さをきすため原文を併記しています。 訳文だけでなく原文に目を通してください。もし意味の取違いを見つけたなら、 @email{takeshi@@SoftAgency.co.jp} に連絡してください。) @cindex licensing terms @cindex support terms このセクションでは、@code{MySQL}のサポートとライセンス規定について説明します。 @menu * Support:: Support Offered by MySQL AB * Copyright:: Copyrights and Licenses Used by MySQL * MySQL licenses:: MySQL Licenses * MySQL AB Logos and Trademarks:: MySQL AB Logos and Trademarks @end menu @node Support, Copyright, Licensing and Support, Licensing and Support @subsection Support Offered by MySQL AB @cindex support, types @cindex types of support @cindex commercial support, types @cindex costs, support @cindex licensing costs @cindex support costs @cindex prices, support Technical support from @code{MySQL AB} means individualised answers to your unique problems direct from the software engineers who code the @code{MySQL} database engine. We try to take a broad and inclusive view of technical support. Almost any problem involving @code{MySQL} software is important to us if it's important to you. Typically customers seek help on how to get different commands and utilities to work, remove performance bottlenecks, restore crashed systems, understand operating system or networking impacts on @code{MySQL}, set up best practices for backup and recovery, utilise @code{API}s, etc. Our support covers only the @code{MySQL} server and our own utilities, not third-party products that access the @code{MySQL} server, though we try to help with these where we can. Detailed information about our various support options is given at @uref{http://www.mysql.com/support/}, where support contracts can also be ordered online. If you have restricted access to the Internet, contact our sales staff at @email{sales@@mysql.com}. Technical support is like life insurance. You can live happily without it for years, but when your hour arrives it becomes critically important, yet it's too late to buy it! If you use @code{MySQL} Server for important applications and encounter sudden troubles, it might take too long to figure out all the answers yourself. You may need immediate access to the most experienced @code{MySQL} troubleshooters available, those employed by @code{MySQL AB}. @node Copyright, MySQL licenses, Support, Licensing and Support @subsection Copyrights and Licenses Used by MySQL @cindex copyrights @cindex licenses @code{MySQL AB} owns the copyright to the @code{MySQL} source code, the @code{MySQL} logos and trademarks and this manual. @xref{What is MySQL AB}. Several different licenses are relevant to the @code{MySQL} distribution: @enumerate @item All the @code{MySQL}-specific source in the server, the @code{mysqlclient} library and the client, as well as the @code{GNU} @code{readline} library is covered by the @code{GNU General Public License}. @xref{GPL license}. The text of this license can also be found as the file @file{COPYING} in the distributions. @item The @code{GNU} @code{getopt} library is covered by the @code{GNU Lesser General Public License}. @xref{LGPL license}. @item Some parts of the source (the @code{regexp} library) are covered by a Berkeley-style copyright. @item Older versions of @code{MySQL} (3.22 and earlier) are subject to a more strict license (@uref{http://www.mysql.com/products/mypl.html}). See the documentation of the specific version for information. @item The manual is currently @strong{not} distributed under a @code{GPL}-style license. Use of the manual is subject to the following terms: @itemize @bullet @item Conversion to other formats is allowed, but the actual content may not be altered or edited in any way. @item You may create a printed copy for your own personal use. @item For all other uses, such as selling printed copies or using (parts of) the manual in another publication, prior written agreement from @code{MySQL AB} is required. @end itemize Please e-mail @email{docs@@mysql.com} for more information or if you are interested in doing a translation. @end enumerate For information about how the @code{MySQL} licenses work in practice, please refer to @ref{MySQL licenses}. Also see @ref{MySQL AB Logos and Trademarks}. @node MySQL licenses, MySQL AB Logos and Trademarks, Copyright, Licensing and Support @subsection MySQL Licenses @cindex licensing policy @cindex technical support, licensing @cindex support, licensing @cindex General Public License, MySQL @cindex GPL, MySQL @cindex licensing, examples @cindex selling products @cindex products, selling The @code{MySQL} software is released under the @code{GNU General Public License} (@code{GPL}), which probably is the best known @code{Open Source} license. The formal terms of the @code{GPL} license can be found at @uref{http://www.gnu.org/licenses/}. See also @uref{http://www.gnu.org/licenses/gpl-faq.html} and @uref{http://www.gnu.org/philosophy/enforcing-gpl.html}. Since the @code{MySQL} software is released under the @code{GPL}, it may often be used for free, but for certain uses you may want or need to buy commercial licenses from @code{MySQL AB} at @uref{https://order.mysql.com/}. See @uref{http://www.mysql.com/products/licensing.html} for more information. Older versions of @code{MySQL} (3.22 and earlier) are subject to a more strict license (@uref{http://www.mysql.com/products/mypl.html}). See the documentation of the specific version for information. 古いバージョンの @code{MySQL} (3.22 とそれ以前) は より制限されたライセンスを有していることに気をつけて下さい (@uref{http://www.mysql.com/support/arrangements/mypl.html})。 より詳しくは、それぞれのバージョンに添付のドキュメントを御覧下さい。 Please note that the use of the @code{MySQL} software under commercial license, @code{GPL}, or the old @code{MySQL} license does not automatically give you the right to use @code{MySQL AB} trademarks. @xref{MySQL AB Logos and Trademarks}. @menu * Using the MySQL software under a commercial license:: Using the MySQL Software Under a Commercial License * Using the MySQL software for free under GPL:: Using the MySQL Software for Free Under GPL @end menu @node Using the MySQL software under a commercial license, Using the MySQL software for free under GPL, MySQL licenses, MySQL licenses @subsubsection Using the MySQL Software Under a Commercial License The @code{GPL} license is contagious in the sense that when a program is linked to a @code{GPL} program all the source code for all the parts of the resulting product must also be released under the @code{GPL}. Otherwise you break the license terms and forfeit your right to use the @code{GPL} program altogether and also risk damages. You need a commercial license: @itemize @bullet @item When you link a program with any @code{GPL} code from the @code{MySQL} software and don't want the resulting product to be @code{GPL}, maybe because you want to build a commercial product or keep the added non-@code{GPL} code closed source for other reasons. When purchasing commercial licenses, you are not using the @code{MySQL} software under @code{GPL} even though it's the same code. @item When you distribute a non-@code{GPL} application that @strong{only} works with the @code{MySQL} software and ship it with the @code{MySQL} software. This type of solution is actually considered to be linking even if it's done over a network. @item When you distribute copies of the @code{MySQL} software without providing the source code as required under the @code{GPL} license. @item When you want to support the further development of the @code{MySQL} database even if you don't formally need a commercial license. Purchasing support directly from @code{MySQL AB} is another good way of contributing to the development of the @code{MySQL} software, with immediate advantages for you. @xref{Support}. @end itemize If you require a license, you will need one for each installation of the @code{MySQL} software. This covers any number of CPUs on a machine, and there is no artificial limit on the number of clients that connect to the server in any way. For commercial licenses, please visit our website at @uref{http://www.mysql.com/products/licensing.html}. For support contracts, see @uref{http://www.mysql.com/support/}. If you have special needs or you have restricted access to the Internet, please contact our sales staff at @email{sales@@mysql.com}. @node Using the MySQL software for free under GPL, , Using the MySQL software under a commercial license, MySQL licenses @subsubsection Using the MySQL Software for Free Under GPL @cindex licensing, free @cindex free licensing You can use the @code{MySQL} software for free under the @code{GPL} if you adhere to the conditions of the @code{GPL}. For more complete coverage of the common questions about the @code{GPL} see the generic FAQ from the Free Software Foundation at @uref{http://www.gnu.org/licenses/gpl-faq.html}. Some common cases: @itemize @bullet @item When you distribute both your own application as well as the @code{MySQL} source code under the @code{GPL} with your product. @item When you distribute the @code{MySQL} source code bundled with other programs that are not linked to or dependent on the @code{MySQL} system for their functionality even if you sell the distribution commercially. This is called mere aggregation in the @code{GPL} license. @item If you are not distributing @strong{any} part of the @code{MySQL} system, you can use it for free. @item @cindex ISP services @cindex services, ISP @cindex services, web @cindex Internet Service Providers When you are an Internet Service Provider (ISP), offering web hosting with @code{MySQL} servers for your customers. However, we do encourage people to use ISPs that have MySQL support, as this will give them the confidence that if they have some problem with the @code{MySQL} installation, their ISP will in fact have the resources to solve the problem for them. Note that even if an ISP does not have a commercial license for @code{MySQL Server}, they should at least give their customers read access to the source of the @code{MySQL} installation so that the customers can verify that it is patched correctly. @item @cindex web server, running @cindex running a web server When you use the @code{MySQL} Database Software in conjunction with a web server, you do not need a commercial license (so long as it is not a product you distribute). This is true even if you run a commercial web server that uses @code{MySQL Server}, because you are not distributing any part of the @code{MySQL} system. However, in this case we would like you to purchase @code{MySQL} support because the @code{MySQL} software is helping your enterprise. @end itemize If your use of @code{MySQL} database software does not require a commercial license, we encourage you to purchase support from @code{MySQL AB} anyway. This way you contribute toward @code{MySQL} development and also gain immediate advantages for yourself. @xref{Support}. If you use the @code{MySQL} database software in a commercial context such that you profit by its use, we ask that you further the development of the @code{MySQL} software by purchasing some level of support. We feel that if the @code{MySQL} database helps your business, it is reasonable to ask that you help @code{MySQL AB}. (Otherwise, if you ask us support questions, you are not only using for free something into which we've put a lot a work, you're asking us to provide free support, too.) @node MySQL AB Logos and Trademarks, , MySQL licenses, Licensing and Support @subsection MySQL AB Logos and Trademarks @cindex logos @cindex trademarks Many users of the @code{MySQL} database want to display the @code{MySQL AB} dolphin logo on their web sites, books, or boxed products. We welcome and encourage this, although it should be noted that the word @code{MySQL} and the @code{MySQL} dolphin logo are trademarks of @code{MySQL AB} and may only be used as stated in our trademark policy at @uref{http://www.mysql.com/company/trademark.html}. @menu * The Original MySQL logo:: The Original MySQL Logo * MySQL Logos that may be Used Without Written Permission:: MySQL Logos that may be Used Without Written Permission * When need MySQL logo permission:: When do you need a Written Permission to use MySQL Logos? * MySQL AB Partnership Logos:: MySQL AB Partnership Logos * Using MySQL word in presentations:: Using the word @code{MySQL} in Printed Text or Presentations * Using MySQL word in company and product names:: Using the word @code{MySQL} in Company and Product Names @end menu @node The Original MySQL logo, MySQL Logos that may be Used Without Written Permission, MySQL AB Logos and Trademarks, MySQL AB Logos and Trademarks @subsubsection The Original MySQL Logo @c FIX: picture: MySQL logo The @code{MySQL} dolphin logo was designed by the Finnish advertising agency Priority in 2001. The dolphin was chosen as a suitable symbol for the @code{MySQL} database since it is a smart, fast, and lean animal, effortlessly navigating oceans of data. We also happen to like dolphins. The original @code{MySQL} logo may only be used by representatives of @code{MySQL AB} and by those having a written agreement allowing them to do so. @node MySQL Logos that may be Used Without Written Permission, When need MySQL logo permission, The Original MySQL logo, MySQL AB Logos and Trademarks @subsubsection MySQL Logos that may be Used Without Written Permission @c FIX: pictures: powered by, works with, included - logos We have designed a set of special @emph{Conditional Use} logos that may be downloaded from our web site at @uref{http://www.mysql.com/press/logos.html} and used on third-party web sites without written permission from @code{MySQL AB}. The use of these logos is not entirely unrestricted but, as the name implies, subject to our trademark policy that is also available on our web site. You should read through the trademark policy if you plan to use them. The requirements are basically: @itemize @bullet @item Use the logo you need as displayed on the @uref{http://www.mysql.com/} site. You may scale it to fit your needs, but not change colours or design, or alter the graphics in any way. @item Make it evident that you, and not @code{MySQL AB}, are the creator and owner of the site that displays the @code{MySQL} trademark. @item Don't use the trademark in a way that is detrimental to @code{MySQL AB} or to the value of @code{MySQL AB} trademarks. We reserve the right to revoke the right to use the @code{MySQL AB} trademark. @item If you use the trademark on a web site, make it clickable, leading directly to @uref{http://www.mysql.com/}. @item If you are using the @code{MySQL} database under @code{GPL} in an application, your application must be @code{Open Source} and be able to connect to a @code{MySQL} server. @end itemize Contact us at @email{trademark@@mysql.com} to inquire about special arrangements to fit your needs. @node When need MySQL logo permission, MySQL AB Partnership Logos, MySQL Logos that may be Used Without Written Permission, MySQL AB Logos and Trademarks @subsubsection When do you need a Written Permission to use MySQL Logos? In the following cases you need a written permission from @code{MySQL AB} before using @code{MySQL} logos: @itemize @bullet @item When displaying any @code{MySQL AB} logo anywhere except on your web site. @item When displaying any @code{MySQL AB} logo except the @emph{Conditional Use} logos mentioned previously on web sites or elsewhere. @end itemize Out of legal and commercial reasons we have to monitor the use of MySQL trademarks on products, books, etc. We will usually require a fee for displaying @code{MySQL AB} logos on commercial products, since we think it is reasonable that some of the revenue is returned to fund further development of the @code{MySQL} database. @node MySQL AB Partnership Logos, Using MySQL word in presentations, When need MySQL logo permission, MySQL AB Logos and Trademarks @subsubsection MySQL AB Partnership Logos @c FIX: pictures: partnership logos - Bertrand? @code{MySQL} partnership logos may only be used by companies and persons having a written partnership agreement with @code{MySQL AB}. Partnerships include certification as a @code{MySQL} trainer or consultant. Please see @ref{Business Services Partnering,,Partnering}. @node Using MySQL word in presentations, Using MySQL word in company and product names, MySQL AB Partnership Logos, MySQL AB Logos and Trademarks @subsubsection Using the word @code{MySQL} in Printed Text or Presentations @code{MySQL AB} welcomes references to the @code{MySQL} database, but note that the word @code{MySQL} is a trademark of @code{MySQL AB}. Because of this, you should append the trademark symbol (@code{TM}) to the first or most prominent use of the word @code{MySQL} in a text and where appropriate, state that @code{MySQL} is a trademark of @code{MySQL AB}. Please refer to our trademark policy at @uref{http://www.mysql.com/company/trademark.html} for details. @node Using MySQL word in company and product names, , Using MySQL word in presentations, MySQL AB Logos and Trademarks @subsubsection Using the word @code{MySQL} in Company and Product Names Use of the word @code{MySQL} in product or company names or in Internet domain names is not allowed without written permission from @code{MySQL AB}. @node MySQL 4.0 In A Nutshell, MySQL Information Sources, Licensing and Support, Introduction @section MySQL 4.x はやわかり @code{MySQL AB}が長い間約束してきて、ユーザからは長い間待ち続けられてき た、MySQLサーバ4.0が、@uref{http://www.mysql.com/}からダウンロードできる ベータとして使えるようになりました。 MySQLサーバ4.0の主要な新しい機能は、わたしたちのこれまでのビジネスとユー ザに前進のギアを入れ、ミッションクリティカルで、高負荷に耐えるデータベー スシステムとしてMySQLデータベースを拡張しています。 @menu * Nutshell Stepwise Rollout:: Stepwise Rollout * Nutshell Ready for Immediate Use:: Ready for Immediate Use * Nutshell Embedded MySQL:: Embedded MySQL * Nutshell Other features:: Other Features Available From MySQL 4.0 * Nutshell Future features:: Future MySQL 4.x Features * Nutshell 4.1 development release:: MySQL 4.1, The Following Development Release @end menu @node Nutshell Stepwise Rollout, Nutshell Ready for Immediate Use, MySQL 4.0 In A Nutshell, MySQL 4.0 In A Nutshell @subsection 段階を踏んだ公開 MySQLは 4.0.6 からガンマ(gamma)とラベルづけられ、4.0.x は2ヶ月以上(最初の1月は アルファで、そしてベータ)、修正が困難な重要な問題も見つからないで使われていて、 実運用に使えます。 少なくとも1ヶ月間重要なバグがなければ、MySQL 4.0 からガンマの接頭辞を取り 除きます。 MySQLソフトウェアの新しい機能は、bk ソースツリーから利用できるMySQL 4.1 で追加され、2003年の最初の四半期にアルファリリースしようとされています。 @node Nutshell Ready for Immediate Use, Nutshell Embedded MySQL, Nutshell Stepwise Rollout, MySQL 4.0 In A Nutshell @subsection すぐに使う準備 すべてのバイナリリリースは、検査したすべてのプラットフォームで、エラーな しで、私たちの広範囲のテストスイートに合格しています。MySQL 4.0は多くのユ ーザで検査され、いくつかの大きなサイトで運用に入っています。 @node Nutshell Embedded MySQL, Nutshell Other features, Nutshell Ready for Immediate Use, MySQL 4.0 In A Nutshell @subsection 組み込み MySQL @code{libmysqld}でMySQL Serverは広範なアプリケーションにふさわしくなります。 組み込み MySQL サーバライブラリを使用することで、MySQL を色々なアプリケ ーション、電子機器(それらにデータベースが利用されていることなどはエンド ユーザが気にすることはない)に埋め込めます。組み込み MySQL は、 インターネットのアプリケーションや、キオスク、ハードウェア、ソフトウェア を組み合わせたもの、高パフォーマンスのインターネットサーバ、CD-ROMに全てが 収まっているデータベース、などの裏方での利用に最適です。 多くの@code{libmysqld}ユーザは、MySQLの@emph{デュアルライセンス}の恩恵をうけ ます。GPLに束縛されたくないユーザは、商用ライセンスでソフトウェアを使え るようになります。組み込みMySQLライブラリは通常のクライアントライブラリ と同じインタフェースを使っているので、便利で使いやすくなっています。 @xref{libmysqld}. @node Nutshell Other features, Nutshell Future features, Nutshell Embedded MySQL, MySQL 4.0 In A Nutshell @subsection MySQL 4.0 から使えるその他の機能 @itemize @bullet バージョン 4.0 は、数カ所で@emph{MySQL Serverの速度}を改善しま した。それは、一括@code{INSERT}や、圧縮されたインデクスの検索、 @code{FULLTEXT}インデクスの作成と、@code{COUNT(DISTINCT)}です。 @item @code{InnoDB}ストレージエンジンが、MySQLサーバの標準の機能として、今回、 提示されました。これは、完全な@code{トランザクション}のサポートと @code{レコードレベルのロック}が含んでいます。 @item ドイツと、オーストリア、そしてスイスのユーザは、新しく@code{latin1_de}が 使え、@emph{ドイツ語のソート順}では、ドイツ語のウムラルトをドイツの電話 帳と同じ順にします。 @item ほかのデータベースシステムからMySQLサーバへ簡単に移行するための機能に (Oracleにある)@code{TRUNCATE TABLE}と、(Sybaseにある)自動的にキーを増や す@code{IDENTITY}がシノニムとして入りました。多くのユーザは、MySQLサーバ では長い間待たされてきた、標準SQLの機能である@code{UNION}文が使えるよう になったことがわかり、うれしく思うでしょう。 @item 新しいユーザに対する機能を作成するときに、わたしたちの重要なユーザのコミ ュニティからの要望も忘れてはいません。複数のテーブルの@code{DELETE}文と @code{UPDATE}文が加わりました。テーブルの水準に(前のようにデータベースの 水準でなく)@code{MyISAM}に@code{シンボリックリンク}が使えるようになり、 Windowsではデフォルトでシンボリックリンクが使えるようになりました。これ で、わたしたちが拡張の要求を真剣に扱っていることがわかると願います。 @code{SQL_CALC_FOUND_ROWS}と@code{FOUND_ROWS()}機能が新しく追加されまし た。これは、句なしで返すために、@code{LIMIT}句を含むSELECT問合せで、行の数 を返します。 @end itemize @node Nutshell Future features, Nutshell 4.1 development release, Nutshell Other features, MySQL 4.0 In A Nutshell @subsection 将来の MySQL 4.x の機能 つぎのMySQL Server 4.x リリースでは開発中の次の項目を予定しています。 @itemize @bullet @item MySQLサーバのミッションクリティカルで、高負荷のユーザは、レプリケーシ ョンシステムとオンラインバックアップシステムが追加されることに価値を見い だすでしょう。4.xの後のバージョンでは、@code{フェールセーフなレプリケー ション}が入るでしょう；4.0ですでにある、@code{LOAD DATA FROM MASTER}コマ ンドは、すぐにスレーブの設定を自動化するようになります。@code{オンライン バックアップ}は、マスターを停止しないで新しいレプリケーションスレーブを 追加することを簡単にし、更新が多いシステムでは性能劣化がとても少なくなっ ています。 @item データベース管理者にとって便利な機能は、もうすぐ@code{mysql}のパラメータ (起動オプション)がサーバを停止しなくても設定できるようになることです。 @item MySQLサーバ4.0の拡張された@code{FULLTEXT}検索の属性で、バイナリと自然言 語の検索ロジックで、大きなテキストの固まりに@code{FULLTEXT}索引が作れる ようになりました。最小ワード長を変更でき、また、どのような自然言語に対し てもストップワードを定義でき、これにより新しい種類のアプリケーションを MySQLサーバに作成できます。 @item MySQL 4.0 は、@code{キーキャッシュ}を書き直すことで、問合せを繰り返すア プリケーションをさらに高速にできるようになりました。 @item 多くの開発者は、クライアントの@code{MySQL コマンドヘルプ}をみて、うれしく思う でしょう。 @end itemize @node Nutshell 4.1 development release, , Nutshell Future features, MySQL 4.0 In A Nutshell @subsection MySQL 4.1, 次の開発リリース MySQL Server 4.0 は、MySQL Server 4.1 の新しい機能の基礎となります。その 機能は、@code{入れ子になった副問合せ}(4.1)、@code{ストアードプロシージャ }(5.0)、@code{MyISAM表の外部キーの一貫性のルール}(5.0)で、多くのお客様か らのご要望の一覧のうちで上位となるものです これらの追加の後に、MySQLデータベースサーバの評論家は、MySQLデータベース 管理システムの欠点を指摘するよりも、より構想力が必要となるでしょう。すでに、長い 間知られている安定性、速度、使いやすさで、MySQLサーバは、切望して いる購入者の要求項目の一覧に適合するでしょう。 @node MySQL Information Sources, Compatibility, MySQL 4.0 In A Nutshell, Introduction @section MySQL についての情報源 @menu * Questions:: MySQL メーリングリスト * IRC:: MySQL Community Support on IRC (Internet Relay Chat) @end menu @node Questions, IRC, MySQL Information Sources, MySQL Information Sources @subsection MySQL メーリングリスト @cindex reporting, errors @cindex errors, reporting @cindex MySQL mailing lists @menu * Mailing-list:: The MySQL Mailing Lists * Asking questions:: Asking Questions or Reporting Bugs * Bug reports:: How to Report Bugs or Problems * Answering questions:: Guidelines for Answering Questions on the Mailing List @end menu この節では、MySQLメーリングリストを紹介し、どのように使うかのガイドライ ンを記述します。メーリングリストを購読すると、電子メールのメッセージで、 リストへ送られたすべてを受け取ります。あなたはリストに質問や回答を送るこ とができます。 @node Mailing-list, Asking questions, Questions, Questions @subsubsection MySQL メーリングリスト @cindex mailing lists @cindex e-mail lists メイン MySQL メーリングリストを購読するには、メッセージを電子メールアド レス @email{mysql-subscribe@@lists.mysql.com} に送ってください。 メイン MySQL メーリングリストの購読の中止は、メッセージを電子メールアド レス @email{mysql-unsubscribe@@lists.mysql.com} に送ってください。 メールの購読と購読の中止には、メッセージを送る先のアドレスだけが重要です。 メッセージのサブジェクトと本文は無視されます。 @c the last two addresses in this paragraph are not @email because they @c shouldn't be live links. もし、あなたのリプライアドレスがつかえないときは、アドレスを明示的に指定 できます。subscribe あるいは unsubscribe のあとにハイフンを付け、そのあ とにあなたのアドレスを記述します。ただし @samp{@@} 文字は @samp{=} に置 き換えて書きます。例えば、 @code{your_name@@host.domain} で購読したい場 合は、@code{mysql-subscribe-your_name=host.domain@@lists.mysql.com} 宛に メッセージを送ります。 @email{mysql-subscribe@@lists.mysql.com} や @email{mysql-unsubscribe@@lists.mysql.com} へのメールは ezmlm メーリングリストプロセッサによって自動的に処理されます。 ezmlm についての情報は ezml ウェブサイトを参考してください (@uref{http://www.ezmlm.org/}) 本メーリングリストへ投稿するには、@code{mysql@@lists.mysql.com} にメッセージを送ります。 しかし、subscribe あるいは unsubscribe のメールを @email{mysql@@lists.mysql.com} に@emph{送らないでください}。 これらのアドレスへ送られたメールは、何千ものユーザに配送されてしまいます。 あなたのローカルサイトが多くの @email{mysql@@lists.mysql.com} の購読者を持て ます。この場合、ローカルのメーリングリストを作り、@code{lists.mysql.com} からの 一つのメッセージがそのサイトに送られ、ローカルなリストで複写されるように してください。この場合、ローカルの MySQL リストへの追加と削除は、 あなたのシステム管理者に問い合わせて下さい。 あなたのメーラーでMySQL メーリングリストからのメールを 適切なメールボックスへ振り分けるには、 （振り分け用の）フィルタをメッセージヘッダを頼りに動作するよう設定して下さい。 その場合、@code{List-ID:} ヘッダか @code{Delivered-To:} ヘッダが 識別の役に立つことでしょう。 次の MySQL メーリングリストがあります: @table @code @item @email{announce-subscribe@@lists.mysql.com} announce これは MySQL と関連プログラムの新しいバージョンのアナウンスのためのリストです。 このリストの流量は少なく、私たちは全ての MySQL ユーザがこのMLに入るべきだと考えています。 @item @email{mysql-subscribe@@lists.mysql.com} mysql MySQL についての一般的な議論のための根幹のリストです。さらに専門的なリ ストで議論すべきものもあることに注意してください。間違ったリストに投稿 しても、答を得られないでしょう。 @item @email{mysql-digest-subscribe@@lists.mysql.com} mysql-digest ダイジェスト形式の @code{mysql} リストです。 このリストからは、一日分の全てのメッセージががまとめられた（ダイジェスト）形式で送られてきます。 @item @email{bugs-subscribe@@lists.mysql.com} bugs このリストには、完全で再現可能なバグレポートだけを、@code{mysqlbug} を使 用して投稿すべきです(Windows 上で実行している場合は、OS と MySQL バージョンの記述を含めるべきです)。 できれば投稿前にMySQL の最新の安定バージョンか開発バージョンを使用して 問題をテストしてください。 含められたテストケース上で、@code{mysql test < script} を使 用することで、誰もがバグを再現できるようにすべきです。このリストに投稿された全て のバグは、次の MySQL リリースで修正されるかドキュメント化されま す。小さなコードの変更だけですめば、私たちはこの問題を修正するパッチを投 稿します。 @item @email{bugs-digest-subscribe@@lists.mysql.com} bugs-digest ダイジェスト形式の @code{bugs} リストです。 @item @email{internals-subscribe@@lists.mysql.com} internals MySQL コード上で作業する人のためのリストです。 このリストでもMySQL 開発の議論とパッチの投稿が可能です。 @item @email{internals-digest-subscribe@@lists.mysql.com} internals-digest @code{internals} リストのダイジェスト版です。 @item @email{java-subscribe@@lists.mysql.com} java MySQL server と Java についての議論。 多くは JDBC ドライバ (MySQL Connector/J 含む) についてです。 @item @email{java-digest-subscribe@@lists.mysql.com} java-digest @code{java} リストのダイジェスト版です。 @item @email{win32-subscribe@@lists.mysql.com} win32 Win95, Win98, NT, Win2000 のような Microsoft OS 上の MySQL software に関連するリストです。 @item @email{win32-digest-subscribe@@lists.mysql.com} win32-digest @code{win32} リストのダイジェスト版です。 @item @email{myodbc-subscribe@@lists.mysql.com} myodbc ODBC で MySQL server への接続に関連する全て。 @item @email{myodbc-digest-subscribe@@lists.mysql.com} myodbc-digest @code{myodbc} リストのダイジェスト版です。 @item @email{mysqlcc-subscribe@@lists.mysql.com} mysqlcc MySQL @code{MySQL Control Center} graphical client 全般についてのリストです。 @item @email{mysqlcc-digest-subscribe@@lists.mysql.com} mysqlcc-digest @code{mysqlcc} リストのダイジェスト版です。 @item @email{plusplus-subscribe@@lists.mysql.com} plusplus MySQL の C++ API でのプログラミングについての全て。 @item @email{plusplus-digest-subscribe@@lists.mysql.com} plusplus-digest @code{plusplus} リストのダイジェスト版です。 @item @email{msql-mysql-modules-subscribe@@lists.mysql.com} msql-mysql-modules MySQL でサポートする Perl についてのリスト。msql-mysql-modules. @item @email{msql-mysql-modules-digest-subscribe@@lists.mysql.com} msql-mysql-modules-digest @code{msql-mysql-modules} リストのダイジェスト版です。 @end table 上述したのと同じ方法で全てのリストの購読または購読中止ができます。あなた の購読または購読中止のメッセージは、@code{mysql} ではなく適切なメーリングリス トに送ってください。例えば、@code{myodbc} リストを購読または購読中止するには、 @email{myodbc-subscribe@@lists.mysql.com} または @email{myodbc-unsubscribe@@lists.mysql.com} にメールを送ります。 メーリングリストから有益な回答が得られない場合、@strong{MySQL AB}に 有料のサポートを求めることもできます。有料サポートが必要な場合、 MySQL 開発チームに直接御連絡下さい(@xref{Support})。 次の表は英語以外の MySQL メーリングリストを示します。注意: これら は @strong{MySQL AB} によって運用されていません。そのため、私たちはそれらの 品質を保証できません。 @table @code @item @email{mysql-france-subscribe@@yahoogroups.com} フランス語メーリングリスト @item @email{list@@tinc.net} 韓国語メーリングリスト このリストに @code{subscribe mysql your@@e-mail.address} をメールしてください。 @item @email{mysql-de-request@@lists.4t2.com} ドイツ語メーリングリスト このリストに @code{subscribe mysql-de your@@e-mail.address} をメールしてください。 これについては @uref{http://www.4t2.com/mysql} で情報を見つけられます。 @item @email{mysql-br-request@@listas.linkway.com.br} ポルトガル語メーリングリスト このリストに @code{subscribe mysql-br your@@e-mail.address} をメールしてください。 @item @email{mysql-alta@@elistas.net} スペイン語メーリングリスト このリストに @code{subscribe mysql your@@e-mail.address} をメールしてください。 @end table @node Asking questions, Bug reports, Mailing-list, Questions @subsubsection 質問またはバグ報告 @cindex net etiquette @cindex mailing lists, archive location @cindex searching, MySQL web pages メーリングリストへ質問を尋ねる前に、以下の手順を踏んでください： @itemize @bullet @item MySQL のオンラインマニュアルを調べることからはじめます： @* @uref{http://www.mysql.com/doc/} @* 私たちは、新しく見つかった問題の解決によってマニュアルを頻繁に更新する ことで、マニュアルを最新に保持しようとしています。 更新の付録(@uref{http://www.mysql.com/doc/en/News.html})は、新 しいバージョンがすであなたの問題の解決を含んでいる可能性が高い ので、とても有用です。 @item バグデータベース(@uref{http://bugs.mysql.com})で、バグがすでに 報告されているか、解決されているかを調べます。 @item MySQL メーリングリストアーカイブを検索します： @* @uref{http://lists.mysql.com/} @* @item @uref{http://www.mysql.com/} の全ての Web ページ(マニュアルも含む)を検索するために @uref{http://www.mysql.com/search/} も使用できます。 @end itemize ここで回答が見つけられない場合は、近くの MySQL 熟練者ととも に調べて下さい。まだあなたの質問の回答が見つけられなければ、先に進み、次 のセクションの @email{mysql@@lists.mysql.com} へメールを送る方法についてを読んで ください。 @node Bug reports, Answering questions, Asking questions, Questions @subsubsection バグや問題を報告する方法 @cindex bugs, reporting @cindex reporting, bugs @cindex problems, reporting @cindex errors, reporting @cindex @code{mysqlbug} script @cindex creating, bug reports @cindex scripts, @code{mysqlbug} 良いバグレポートを書くのには忍耐が要りますが、それを最初に正しく行うと 私たちとあなたの時間を節約します。 バグについての完全なテストケースを含む良いレポートを書くと、次のリリー スでそのバグが修正される可能性がとても高くなります。 この節では、かなりの、または全く私たち の助けにならないことにあなたの時間を浪費しないように、あなたがレポートを 正しく書くことを手助けします。 私たちは、バグレポートまた可能ならば全ての問題についてのレポートの作成に @code{mysqlbug} スクリプトを使用することを奨励します。@code{mysqlbug} は ソース配布内の @file{scripts} ディレクトリ、または、バイナリ配布では MySQL をインストールしたディレクトリ配下の @file{bin} ディレク トリにあります。@code{mysqlbug} を使用できない場合は、この節に挙 げられている全ての必要な情報を含めてください。 @code{mysqlbug} スクリプトは、下記の多くの情報を自動的に見つけ出すことで、 レポートの作成を手助けします。しかし、重要な何かが足りない場合、あなたの メッセージにそれを含めてください。この節を慎重に読んで、ここで述べられ ている全ての情報がレポート中に含まれていることを確認してください。 @cindex bug reports, email address バグや問題を報告する通常の場所は、@email{mysql@@lists.mysql.com} です。 バグを明確に示すテストケースを作ることができれば、 @email{bugs@@list.mysql.com} リストにそれを投稿してください。注意: この リストには、完全で再現可能なバグ情報を @code{mysqlbug} スクリプトを使用 して投稿すべきです。 Windows 上で実行している場合は、OS と MySQL バージョンの記述を含めてください。できれば、投稿前に MySQL Server の最新の安定バージョンか開発バージョンを使用して問題をテ ストしてください。含められたテストケース上で、``@code{mysql test < script}'' を使 用することで、または、バグレポートに含められたシェル/Perlスクリプトを実 行することで、誰もがバグを再現できるようにすべきです。この @code{bugs} リストに投稿された全て のバグは、次の MySQL リリースで修正されるかドキュメント化されま す。 小さなコードの変更だけですめば、私たちはこの問題を修正するパッチの投 稿も行います。 多すぎる情報を含むメッセージに答えることはできますが、少なすぎる情報を含 むものにはできないということを覚えていてください。しばしば人は事実を省い てしまいます。問題の原因をわかっていると思い、いくつかの細かいことを重大でない と見なしてしまうからです。良い原則は: 何かを言おうか迷ったときには、言っ てください。最初にあなたが十分な情報を含めなかったために、再び質問して 回答を待つことを強いられるより、数行をあなたのレポートに書く方が千倍速く て、迷惑ではありません。 良くある間違いは、使用している MySQL 配布のバージョン番号を示さ ない、または MySQL server をインストールしたプラットフォームを(プラッ トフォームのバージョン番号を含めて)示さないことです。これはとても関連した 情報で、100 のバグレポートのうち 99 の場合、この情報がないと役に立ちませ ん。私たちは ``何故私では動作しないの？'' のような質問をとても良く受けま す。そして私たちは、要求された機能はその MySQL バージョンに実装さ れていない、または、レポート中に述べられているバグは新しい MySQL バージョンで既に修正されているであることを見つけます。ときどき、 エラーはプラットフォーム依存で、オペレーティングシステムとプラットフォー ムのバージョン番号を知らないことには、何も修正することはできません。 問題に関連している場合は、コンパイラについての情報も与えることを忘れない でください。しばしば人はコンパイラのバグを見つけて、問題は MySQL に関連していると考えます。多くのコンパイラはいつも開発中 で、バージョンを上げることによってより良いバージョンになります。問題がコ ンパイラに依存しているかどうかを確定するには、どのコンパイラが使用されて いるかを知ることが必要です。全てのコンパイルの問題はバグレポートとみなさ れ、それに従って報告されるべきであることに注意してください。 最も役に立つのは、問題の良い説明がバグレポートに含められることです。つま り、問題に導かれる全ての行ったことの例と、正確に記述された問題それ自身 です。良いバグレポートは、バグや問題を再現する方法を示す完全な例を含むも のです。@xref{Reproduceable test case}. 問題がエラーメッセージを与える場合、それをレポートに含めることはとても重 要です。私たちがプログラムを使用するアーカイブから何かを検索しようとする 場合、エラーメッセージはプログラムが与えたものと正確に一致する方が良いで す(大文字小文字でさえも残されるべきです)。どのようなエラーメッセージだったか を覚えるなんてことはしてはいけません；レポートに完全なメッセージをコピー して貼りつけてください。 MyODBC での問題がある場合、MyODBC トレースファイルの生成を試みるべきです。 @xref{MyODBC bug report}. あなたのレポートを読む多くの人が 80桁ディスプレイを使用しているというこ とを覚えておいて下さい。@code{mysql} コマンドラインツールを使用 してレポートまたはサンプルを生成するとき、そのようなディスプレイの有効幅を 超える出力(例えば、@code{EXPLAIN SELECT} 文; 後述のサンプル を見てください)には、@code{--vertical} オプション(または @code{\G} ステー トメント終端)を使用してください。 @cindex bug reports, criteria for 次の情報をレポートに含めてください: @itemize @bullet @item 使用している MySQL 配布のバージョン番号 (例えば MySQL バージョン 3.22.22)。どのバージョンを動かしているかは @code{mysqladmin version} の 実行でわかります。@code{mysqladmin} は MySQL のインストール ディレクトリ配下の @file{bin} ディレクトリにあります。 @item あなたが作業しているマシンのメーカーとモデル。 @item オペレーティングシステム名とバージョン。多くのオペレーティングシステムで は、UNIX コマンド @code{uname -a} の実行によってこの情報が得られます。 @item ときにはメモリ(実メモリと仮想メモリ)の量も関係します。疑わしければ、それを 含めてください。 @item MySQL software のソース配布を使用している場合は、使用したコンパイラの名 前とバージョン番号についての情報も必要です。バイナリ配布の場合は、配布名が 必要です。 @item 問題がコンパイル中に発生する場合、正確なエラーメッセージと、エラーが発生 したファイルの問題のコードの回りの数行も含めて下さい。 @item もし @code{mysqld} が死んだ場合は、@code{mysqld} がクラッシュしたクエリも レポートしてください。通常、これはロギングが有効にして @code{mysqld} を実行すること よって、見つけられます。@xref{Using log files}。 @item 何かのデータベーステーブルが問題に関連する場合は、 @code{mysqldump --no-data db_name tbl_name1 tbl_name2 ...} からの出力を含めて ください。これはデータベース内の任意のテーブルについての情報を得るとても 簡単で強力な方法で、私たちがあなたの状況に一致するものを生成する手助けにな ります。 @item @code{SELECT} 文での速度に関するバグや問題では、 @code{EXPLAIN SELECT ...} の出力と、少なくとも @code{SELECT} 文が 返す行の数を常に含めるべきです。誰かがあなたを助けられるように、 あなたの状況について、より多くの 情報を、より適切に与えてください。例え ば、次はとても良いバグレポートの例です（もちろん @code{mysqlbug} スクリプトで投 稿されてます）: @code{mysql} コマンド行ツール配下での実行例(注意: 出力幅がディスプレイ装 置の80桁を超える文には、@code{\G} 文終端子を使用し てください): @example mysql> SHOW VARIABLES; mysql> SHOW COLUMNS FROM ...\G mysql> EXPLAIN SELECT ...\G mysql> FLUSH STATUS; mysql> SELECT ...; <問い合わせを実行した時間を含んだSELECTの出力の短い版> mysql> SHOW STATUS; @end example @item 問題やバグが MySQL 実行中に発生する場合、バグを再現する入力スク リプトが必要です。このスクリプトは必要なソースファイル全てを含めてください。 より精密なスクリプトはあなたのに似た状況を良く再現できます。 テストケースを再現可能にできる場合は、高い優先度で取り扱われるように、 @email{bugs@@lists.mysql.com} にそれを送ってください。 もしスクリプトを提供することができなければ、少なくとも、 @code{mysqladmin variables extended-status processlist} の 出力結果をメールに含めてください。これはあなたのシステムの情報を 提供します。 @item 数行のテストケースを提供できない場合、またはテストテーブルがメーリングリ ストにメールするには大きすぎる(10行以上)場合、@code{mysqldump} を使用し てあなたのテーブルをダンプし、あなたの問題を説明した @file{README} ファ イルを作ってください。 @code{tar} と @code{gzip} または @code{zip} を使用して、ファイルの圧縮アー カイブを生成し、そのアーカイブを @code{ftp} を使用して @uref{ftp://support.mysql.com/pub/mysql/secret/} に転送してください。それか ら問題の短い説明を @email{mysql@@lists.mysql.com} に送ってください。 @item MySQL server がクエリから異常な結果を与えると思う場合は、結果だけでな く、結果がどうなるべきかというあなたの意見と、あなたの意見の根拠を説明す る理由も含めてください。 @item 問題のサンプルを提供するときに、新しい名前にするよりも、実際の状況で存在す るのと同じ変数名やテーブル名等を使用した方が良いです。問題が変数やテーブ ルの名前に関連することがあります。おそらくこれはまれなケースですが、 後悔するよりも安全です。結局、実際に持っているあなたのサンプル 中の同じ状況を使用することは、あなたにとっても簡単で、私たちにとっても全ての 意味で良いことです。他の人に見せたくないデータである場合、 @code{ftp} を使用して @uref{ftp://support.mysql.com/pub/mysql/secret/} にデー タを転送することができます。データが本当に最高機密で私たちにさえ見せたくな い場合は、先に進んで、他の変数名等を使用してサンプルを作ってみてください。 しかしこれは最後の選択と思ってください。 @item 可能ならば、関連プログラムに与えられた全てのオプションを含めてください。 例えば、@code{mysqld} デーモン開始時に使用したオプションと MySQL クライアントプログラムの実行に使用したオプションを示してく ださい。 @code{mysqld}, @code{mysql} または @code{configure} スクリプト へのオプションはしばしば回答への鍵になり、とても関連しています。とに かくそれらを含めるというのは悪い考えではありません。Perl や PHP などの モジュールを使用している場合、それらのバージョン番号も含めてください。 @item 質問が権限システムに関連する場合、@code{mysqlaccess} の出力、 @code{mysqladmin reload} の出力、接続しようとしたときに得られた全てのエラー メッセージを含めてください。権限をテストするときは、まず @code{mysqlaccess} を実行してください。その後、@code{mysqladmin reload version} を実行し、最 後に問題が発生するプログラムでの接続を試みてください。@code{mysqlaccess} はMySQL インストールディレクトリ配下の @file{bin} ディレクトリ にあります。 @item バグに対するパッチがあるならば、当ててください。しかし、そ のパッチがすべて、私たちが求めているもので、あなたのパッチが修正するバグの テスト情報を提供しなくても、私たちがそれを使用するだろう と思わないでください。私たちはあなたのパッチに問題を見つけるかもしれません し、または、それを全く理解できないかもしれません。その場合はそれを使用で きません。 そのパッチに意味があることが正確に確かめられなければ、私たちはそれを使用し ません。テストケースは私たちにこの手助けをします。パッチが起りうる全ての状 況を扱うことを示してください。パッチが動作しない境界線のケース(それが稀 でも)を見つけた場合には、パッチは使用されないでしょう。 @item 何がバグか、なぜ発生するのか、何に依存しているのか、についての推測は通常 間違いです。MySQLチームでさえ、まずデバッガを使用してバグの実際の原因を見つけな ければ、そのことは推測できません。 @item メールメッセージ中に、あなたがリファレンスマニュアルとメールアーカイブを 調べたことを示してください。そうすれば、あなたの問題をあなた自身で 解決しようとしたことを他の人がわかります。 @item @code{parse error} が発生する場合、構文を厳密にチェックしてください。何 も間違いが見つけられなければ、多分、使用しているクエリを MySQL Server の現在のバージョンがサポートしていないということです。現 在のバージョンを使用していて、@uref{http://www.mysql.com/documentation/manual.php} のマ ニュアルがあなたの使用しているクエリ構文を扱えない場合は、これは MySQL Server があなたのクエリをサポートしていないという意味です。この 場合、あなたの選択肢は、その構文をあなた自身で実装するか、 @email{mysql-support@@mysql.com} に email で実装するように申し込むか です。 マニュアルではあなたの使用している構文が使えるのに対してMySQL の古いバージョンを使用している場合、文法が実装された時期について MySQL Server の変更履歴を調べてください。@xref{News}。この場合、よ り新しいバージョンの MySQL へのアップグレードを選択できます。 @item もしあなたのデータが壊れたり、または、ある特定の テーブルにアクセスするとき、エラーとなるなら、 まず最初に、テーブルを @code{myisamchk} か @code{CHECK TABLE}/@code{REPAIR TABLE} 文で検査し、修復を試みるべきです @xref{MySQL Database Administration}. @item もし、しばしばテーブルが壊れるようなら、いつ、なぜ起こるのかを 探し出してください。 この場合、@file{mysql-data-directory/'hostname'.err} ファイルに 何が起こっているのか含まれている場合があります。 @xref{Error log}. このファイルから関連する情報を抜きだしバグレポートに含めてください。 通常、 @code{mysqld} は更新の最中に kill されない限りは テーブルを@strong{絶対に}破壊しません。もしなぜ @code{mysqld} が死ぬのか 見つけた場合は、私たちがあなたに問題解決のための修正を提供することが、 はるかに簡単になります。 @xref{What is crashing} @item 可能な場合、最新の MySQL Server バージョンをダウンロードして、これで問 題が解決されるかどうかをチェックしてください。全ての MySQL バー ジョンは徹底的にテストされていて、問題なしに動作するはずです。全てが可能な限り以前と 互換があるように作られていて、問題なく MySQL バージョンを切り替え ることができると私たちは信じています。@xref{Which version}。 @end itemize @cindex technical support, mailing address @cindex support, mailing address @cindex customer support, mailing address @cindex mailing address, for customer support もしあなたがサポート顧客なら、より高い優先度で取り扱われるように、バグレポー トを @email{mysql-support@@mysql.com} と、そして同様に、他の誰かが問題を経 験済み(そして、もしかしたら解決済み)かどうかを調べるために、適切なメーリン グリストにもクロスポストしてください。 @strong{MyODBC} のバグ報告上の情報については、@ref{ODBC Problems} を参照 してください。 いくつかの一般的な問題の解決法のために @ref{Problems} を参照してください。 回答があなたに個人的に送られて、メーリングリストに送られていないときは、 あなたの問題の解決の手助けになった返事の恩恵を他の人にも与える ために、回答を要約し、その要約をメーリングリストに送信することが、良いエチケットです。 @node Answering questions, , Bug reports, Questions @subsubsection メーリングリストで質問に答えるためのガイドライン @cindex net etiquette @cindex questions, answering @cindex answering questions, etiquette @cindex mailing lists, guidelines あなたの回答が広く関心を持たれると考えられる場合、尋ねた人に個人的に直接 返事をする代わりに、メーリングリストに投稿したいと思うでしょう。元 の投稿者以外の人もそれから恩恵を受けられるように、十分に一般的な回答を作成 することを試みてください。メーリングリストに投稿する場合は、あなたの回答 が以前の回答と重複していないか確認して下さい。 あなた返事の中で、質問の本質部分の要約を試みてください。質問全体を引用す ることを義務と感じないで下さい。 HTML モードを ON にしたブラウザからメールメッセージを投稿しないでくださ い。多くのユーザはブラウザでメールを読んでいません。 @node IRC, , Questions, MySQL Information Sources @subsection IRC (Internet Relay Chat) での MySQL コミュニティの支援 @cindex IRC @cindex Internet Relay Chat いろいろなMySQLのメーリングリストに加え、@code{IRC}(@code{Internet Relay Chat}) に経験を積んだコミュニティの人がいます。次は、わたしたちが知っている、 現在のよい networks/channels です： @itemize @bullet @item @strong{freenode} (see @uref{http://www.freenode.net/} for servers) @itemize @item @code{#mysql} 基本はMySQLの質問、しかしほかのデータベースやSQLの質問も歓迎されます。 @item @code{#mysqlphp} MySQL+PHP、人気の高い組み合わせ、の質問です。 @end itemize @item @strong{EFnet} (@uref{http://www.efnet.org/}のサーバに関して。) @itemize @item @code{#mysql} MySQL の質問 @end itemize @end itemize IRCネットワークに接続するIRCクライアントソフトウェアを探して いるならば、@code{X-Chat}(@uref{http://www.xchat.org/})を見て ください。X-Chatは、Unixだけではなく、Windowsのプラットフォー ムでも使えます。 @node Compatibility, TODO, MySQL Information Sources, Introduction @section MySQL はどのように標準互換か？ @cindex compatibility, with ANSI SQL @cindex standards compatibility @cindex extensions, to ANSI SQL @cindex ANSI SQL92, extensions to この章では、MySQL がどのように ANSI SQL 標準に関係するかを説明し ます。MySQL Server は ANSI SQL 標準に対して多くの拡張を持ちます。そして、 ここでそれらが何か、またそれらの使用方法を見つけられるでしょう。また、 MySQL Server に足りない機能についての情報と、いくつかの違いを回避する方 法も見つけられるでしょう。 わたしたちの目標は、どのように使ってもMySQL Serverの使いやすさを、正当な 理由なしで制限しないことです。可能性のあるすべての使い方に対する開発のリ ソースをもっていなくても、わたしたちは、新しい領域でMySQL Serverを使おう としている人たちに助けと提案を求めます。 製品へのわたしたちのひとつの主な目標は、速度と信頼性を犠牲にしないで、ANSI 99適合性に向かって進み続けることです。ユーザの多くにとってMySQL Serverの 使いやすさが大きく増すときには、SQLに拡張を加えたり、SQLにない機能を追加 したりすることを恐れません。(MySQL Server 4.0の新しい@code{HANDLER}インタ フェースはこの戦略の例です。@xref{HANDLER, , @code{HANDLER}}.) 激しいウェブ/ログの使い方とミッションクリティカルな24/7(訳注：24時間/日、 7日/週のことと考えられる)の使い方の両方を満 たすために、トランザクションと非トランザクションデータベースをサポートし 続けます。 MySQL Serverは、小さなコンピュータシステムで、中規模なデータベース(1千万件 から1億件のレコード、またはひとつのテーブルあたり100Mバイト)で動作するとこ ろから設計し始めました。わたしたちはMySQL Serverがテラバイトのデータベース でも動作するように拡張し続けます。それと同じように、ハンドヘルド機器や組み 込み用途により適するように切りつめたMySQLバージョンをコンパイルできるように しています。MySQLサーバは設計が簡潔であるため、ソースツリーで競合しないでこ の両方の方向を採ることができます。 いまは、リアルタイムのサポートやクラスタ化されたデータベースのサポートを(レプ リケーションサービスで多くのことがすでにできていても)目標に置いていません。 ネイティブにXMLをサポートする必要はないと信じていますが、代わりにクライア ント側でXMLをサポートするようにわたしたちからユーザにお願いしようとしていま す。クライアント側で複雑さを取り扱うライブラリを開発するより、メインのサーバ のコードをできるかぎり「細身できれいに」しておくほうがよいと考えます。これが 前に述べた、サーバで速度と信頼性を犠牲にしない戦略の一部です。 @menu * Standards:: What Standards Does MySQL Follow? * ANSI mode:: Running MySQL in ANSI Mode * Extensions to ANSI:: MySQL Extensions to ANSI SQL92 * Differences from ANSI:: MySQL Differences Compared to ANSI SQL92 * Bugs:: Known Errors and Design Deficiencies in MySQL @end menu @node Standards, ANSI mode, Compatibility, Compatibility @subsection どの標準に MySQL はしたがうか？ エントリレベルではSQL92です。ODBCのレベルは0-3.51です。 ANSI SQL 99標準の全機能が使えるのが目標ですが、コードの速 度と品質には妥協しません。 @node ANSI mode, Extensions to ANSI, Standards, Compatibility @subsection MySQLをANSIモードで実行する @cindex running, ANSI mode @cindex ANSI mode, running @code{mysqld}を@code{-ansi}オプションをつけて起動すると、 MySQL Serverは次のように振る舞います： @itemize @bullet @item @code{||}* ||はORではなく、文字列の連結です。 @item 関数名と@samp{(}の間にいくつでも空白を書けます。これは、すべての 関数名を予約語として取り扱います。 @item @samp{"}は識別子の引用符(MySQL Serverで@samp{`}が引用符であるよう に)となり、文字列の引用符でなくなります。 @item @code{REAL}は、@code{DOUBLE}の別名ではなく、@code{FLOAT}の別名にな ります。 @item デフォルトのトランザクションの識別レベルは`code{SERIALIZABLE}となります。 @xref{SET TRANSACTION}. @item フィールドリストにない@code{GROUP BY}のなかで、フィールドや式が使えます。 @end itemize サーバをANSIモードで実行することは、次のオプションで開始することと同じです。 @code{--sql-mode=REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES, IGNORE_SPACE,SERIALIZE,ONLY_FULL_GROUP_BY}. @node Extensions to ANSI, Differences from ANSI, ANSI mode, Compatibility @subsection MySQL の ANSI SQL92 に対する拡張 @cindex hints MySQL Server は、他の SQL データベース内に見られないであろう、いくつか の拡張を含んでいます。それらを使用すると、コードは他の SQL サー バに移行できなくなるので注意してください。いくつかのケースでは、形式 @code{/*! ... */} のコメントを使用することで、MySQL 拡張を含む 移行可能コードを書くことができます。この場合、MySQL Server はコメント 内のコードを実行しますが、ほかのSQLサーバはこれを無視します。例えば: @example SELECT /*! STRAIGHT_JOIN */ col_name FROM table1,table2 WHERE ... @end example @code{'!'} の後ろにバージョン番号を追加すると、文法は MySQL バー ジョンが使用されるバージョン番号と等しいか大きい場合にのみ実行されます: @example CREATE /*!32302 TEMPORARY */ TABLE t (a int); @end example 上記は バージョン 3.23.02 かそれ以上の場合という意味で、そのとき MySQL Server は @code{TEMPORARY} キーワードを使用します。 MySQL 拡張を以下に示します: @itemize @bullet @item フィールド型 @code{MEDIUMINT}, @code{SET}, @code{ENUM} そして様々な @code{BLOB} と @code{TEXT} 型。 @item フィールド属性 @code{AUTO_INCREMENT}, @code{BINARY}, @code{NULL}, @code{UNSIGNED} そして @code{ZEROFILL}。 @item 全ての文字列比較はデフォルトでは大文字と小文字を区別しないで、現在の文字セット(デフォ ルトでは ISO-8859-1 Latin1)にしたがったソート順です。これを好まない場合は、 @code{BINARY} 属性であなたのフィールドを宣言すべきです。これは、MySQL サーバホストの上で使用される ASCII 順にしたがって比較されるようになり ます。 @item MySQL Server はデータベースを MySQL データディレクトリ 以下のディレクトリにマップし、 テーブルをデータベースディレクトリ以下のファイル名に マップします。 これはいくつかの意味を持ちます: @cindex database names, case-sensitivity @cindex table names, case-sensitivity @cindex case-sensitivity, of database names @cindex case-sensitivity, of table names @itemize @minus @item 大文字と小文字を区別するファイル名をもつ OS (多くのUNIXのような)上の MySQL Server では、 データベース名とテーブル名の大文字と小文字は区別されます。@xref{Name case sensitivity}. @item データベース名、テーブル名、インデックス名、フィールド名、別名は数字から始 めることができます(ただし、数字だけにすることはできません)。 @item テーブルのバックアップ、リネーム、移動、削除、コピーに標準システムコマン ドを使用できます。例えば、テーブルの名前を変えるには、テーブルに対応する @file{.MYD}, @file{.MYI}, @file{.frm} ファイルの名前を変えてください。 @end itemize @item SQL 文では、 @code{db_name.tbl_name} 構文を使用して、違うデータベースのテーブルにアクセスできます。 いくつかのSQLサーバは同様の機能を提供しますが、これを @code{User space} と呼びます。 MySQL Server は以下のようなテーブルスペースをサポートしません: @code{create table ralph.my_table...IN my_tablespace}. @item 数値フィールド上での @code{LIKE} が許されます。 @item @code{SELECT} 文内の @code{INTO OUTFILE} と @code{STRAIGHT_JOIN} の使用。@xref{SELECT, , @code{SELECT}}. @item @code{SELECT}文で@code{SQL_SMALL_RESULT}オプションが使えます。 @item どのようにテーブルが結合されるかの詳細を得るための @code{EXPLAIN SELECT}。 @item インデックス名、フィールドの一部のインデックス、そして @code{CREATE TABLE} 文 内の @code{INDEX} または @code{KEY} の使用。 @xref{CREATE TABLE, , @code{CREATE TABLE}}. @item @code{CREATE TABLE} での @code{TEMPORARY} か @code{IF NOT EXISTS} の使用。 @item @code{list} 要素が一つ以上の @code{COUNT(DISTINCT list)} の使用。 @item @code{ALTER TABLE} 文内の @code{CHANGE col_name}, @code{DROP col_name}, @code{DROP INDEX}, @code{IGNORE}, @code{RENAME} の使用。 @xref{ALTER TABLE, , @code{ALTER TABLE}}. @item @code{RENAME TABLE} の使用。@xref{RENAME TABLE, , @code{RENAME TABLE}}。 @item @code{ALTER TABLE} 文内の複数の @code{ADD}, @code{ALTER}, @code{DROP}, @code{CHANGE} 節の使用。 @item キーワード @code{IF EXISTS} 付きの @code{DROP TABLE} の使用。 @item 複数のテーブルを一回の @code{DROP TABLE} で破棄できる @item @code{DELETE} 文の @code{LIMIT} 節。 @item @code{INSERT} と @code{REPLACE}文の @code{DELAYED} 節。 @item @code{INSERT}, @code{REPLACE}, @code{DELETE}, @code{UPDATE} 文 の @code{LOW_PRIORITY} 節。 @cindex Oracle compatibility @cindex compatibility, with Oracle @item @code{LOAD DATA INFILE} の使用。多くの場合、この構文は ORACLE の @code{LOAD DATA INFILE} と互換があります。@xref{LOAD DATA, , @code{LOAD DATA}}. @item @code{ANALYZE TABLE}と@code{CHECK TABLE}、@code{OPTIMIZE TABLE}、 @code{REPAIR TABLE} 文。 @item @code{SHOW} 文。 @xref{SHOW, , @code{SHOW}}. @item @samp{'} だけでなく @samp{"} または @samp{'} によって文字列を括ることが 可能。 @item エスケープ文字 @samp{\} の使用。 @item @code{SET} 文。 @xref{SET OPTION, , @code{SET}}. @item @code{GROUP BY} 部に詮索されたすべてのフィールドを持つ必要はありません。 これにより、特別で、しかしきわめて普通の問合せの性能が向上します。 @xref{Group by functions}. @item @code{GROUP BY} とともに @code{ASC} と @code{DESC} を記述できます。 @item ほかの SQL 環境から来たユーザに対し、より簡単にするため、MySQL Server は多くの関数に別名を用意しています。例えば、全ての文字列関数は ANSI SQL と ODBC 構文の両方があります。 @item MySQL Server は @code{||} と @code{&&} 演算子を、C プログラミング言語 のように、論理和と論理積を意味すると理解します。MySQL では @code{||} と @code{OR}、@code{&&} と @code{AND} は同義語です。この良い構 文のため、MySQL Server は ANSI SQL の文字列結合演算子 @code{||} をサポー トしません。@code{CONCAT()} を代わりに使用してください。@code{CONCAT()} は任意の数の引数を使用できるので、@code{||} 演算子の使用を MySQL Server に変換するのは簡単です。 @item @code{CREATE DATABASE} または @code{DROP DATABASE}. @xref{CREATE DATABASE, , @code{CREATE DATABASE}}. @cindex PostgreSQL compatibility @cindex compatibility, with PostgreSQL @item @code{MOD()} と同義の @code{%}。 @code{N % M} は @code{MOD(N,M)} と等価です。 @code{%} は C プログラマと PostgreSQL との互換のためにあります。 @item @code{=}, @code{<>}, @code{<=} ,@code{<}, @code{>=},@code{>}, @code{<<}, @code{>>}, @code{<=>}, @code{AND}, @code{OR}, @code{LIKE} 演算子は、@code{SELECT} 文中で、@code{FROM} の左側のフィールドの比較に 使用されます。 例えば： @example mysql> SELECT col1=1 AND col2=2 FROM tbl_name; @end example @item @code{LAST_INSERT_ID()} 関数。 @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @item @code{REGEXP} と @code{NOT REGEXP} 正規表現演算子 @item 1つまたは2以上の引数での @code{CONCAT()} または @code{CHAR()}。 MySQL Server では、これらの関数は任意の数の引数を取ることができます。 @item The @code{BIT_COUNT()}, @code{CASE}, @code{ELT()}, @code{FROM_DAYS()}, @code{FORMAT()}, @code{IF()}, @code{PASSWORD()}, @code{ENCRYPT()}, @code{md5()}, @code{ENCODE()}, @code{DECODE()}, @code{PERIOD_ADD()}, @code{PERIOD_DIFF()}, @code{TO_DAYS()}, @code{WEEKDAY()} 関数。 @item 文字列を切り落とすために @code{TRIM()} が使えます。ANSI SQL では、ひとつの 文字だけを取り除くことしかできません。 @item @code{GROUP BY} 関数 @code{STD()}, @code{BIT_OR()} そして @code{BIT_AND()}。 @item @code{DELETE} + @code{INSERT} の代わりの @code{REPLACE} の使用。 @xref{REPLACE, , @code{REPLACE}}. @item @code{FLUSH}, @code{RESET}, @code{DO} 構文。 @item @code{:=} で文内での変数の設定が可能: @example SELECT @@a:=SUM(total),@@b=COUNT(*),@@a/@@b AS avg FROM test_table; SELECT @@t1:=(@@t2:=1)+@@t3:=4,@@t1,@@t2,@@t3; @end example @end itemize @node Differences from ANSI, Bugs, Extensions to ANSI, Compatibility @subsection MySQL と ANSI SQL92 との違い 私たちは MySQL Server を ANSI SQL 標準と ODBC SQL 標準にしたがうように しようとしていますが、いくつかの場合、MySQL Server には違いがあります: @itemize @bullet @item @code{--} は空白が続く場合だけコメントになります。 @item @code{VARCHAR} フィールドでは、値が格納されるときに末尾の空白が削除されます。 @xref{Bugs}。 @item いくつかの場合で、@code{CHAR} フィールドは黙って @code{VARCHAR} フィール ドに変更されます。@xref{Silent column changes}。 @item テーブルを削除するときに、テーブルについての権限は自動的には破棄されません。 テーブルの権限を破棄するには、明示的に @code{REVOKE} を発行する必 要があります。@xref{GRANT, , @code{GRANT}}. @item @code{NULL AND FALSE} は @code{FALSE} ではなく @code{NULL} と評価されます。 この場合、多くの余計な条件を評価する必要があることは良いことではないと、 私たちは考えているからです。 @end itemize @menu * ANSI diff Sub-selects:: Sub@code{SELECT}s * ANSI diff SELECT INTO TABLE:: @code{SELECT INTO TABLE} * ANSI diff Transactions:: Transactions and Atomic Operations * ANSI diff Triggers:: Stored Procedures and Triggers * ANSI diff Foreign Keys:: Foreign Keys * ANSI diff Views:: Views * ANSI diff comments:: @samp{--} as the Start of a Comment @end menu 次の機能が MySQL Server の現在のバージョンにはありません。新しい拡張の 優先度については、次を参考にしてください @uref{http://www.mysql.com/doc/en/TODO.html}. これはこのマニュアル中の TODO リストの最新バージョンです。 @xref{TODO}. @node ANSI diff Sub-selects, ANSI diff SELECT INTO TABLE, Differences from ANSI, Differences from ANSI @subsubsection 副問合せ @cindex sub@code{SELECT}s バージョン 4.0 までの MySQL Server は、 @code{INSERT ... SELECT ...} と @code{REPLACE ... SELECT ...}の形式だけで 入れ子のクエリが使えます。しかし、ほかのところでも@code{IN()}が 使えます。副問合せは、4.1 の開発のツリーで実装中です。副問合せは、 4.1 の開発のツリーで開発されました。 しかし多くの場合、副問合せを使わないクエリに書き直せます: @example SELECT * FROM table1 WHERE id IN (SELECT id FROM table2); @end example これは、次のように書き直せます: @example SELECT table1.* FROM table1,table2 WHERE table1.id=table2.id; @end example 問合せ： @example SELECT * FROM table1 WHERE id NOT IN (SELECT id FROM table2); SELECT * FROM table1 WHERE NOT EXISTS (SELECT id FROM table2 WHERE table1.id=table2.id); @end example これは、次のように書き直せます： @example SELECT table1.* FROM table1 LEFT JOIN table2 ON table1.id=table2.id WHERE table2.id IS NULL; @end example さらに複雑な副問合せでは、副問合せを保持するために一時テーブルを作成で きます。しかし、この方法が使えない場合があります。この場合には、 @code{DELETE} 文でもっとも頻繁に遭遇します。@code{DELETE} 文 では、標準 SQL では（sub select の中を除いて）join が使え ません。副問合せが MySQL Server で使えるようになるまで、この状況には２ つの選択肢があります。 最初の選択肢は、手続きプログラミング言語（Perl や PHP のような）を使用して、 @code{SELECT} クエリを発行して削除されるレコードのプライマリキーを獲得し、 それから @code{DELETE} 文（@code{DELETE FROM ... WHERE ... IN (key1, key2, ...)}）を組み立てるためにその値を使用することです。 二番目の選択肢は、対話型 SQL を使用し、@code{DELETE} 文の集まり を、（標準 @code{||} オペレータの代わりに）MySQL 拡張 @code{CONCAT()} を使用して、自動的に組み立てることです。例えば: @example SELECT CONCAT('DELETE FROM tab1 WHERE pkid = ', "'", tab1.pkid, "'", ';') FROM tab1, tab2 WHERE tab1.col1 = tab2.col2; @end example このクエリをスクリプトファイル中に置き、入力を @code{mysql} コマンドライン インタプリタに切替え、その出力を二番目のインタプリタインスタンスにパイプし ます: @example shell> mysql --skip-column-names mydb < myscript.sql | mysql mydb @end example MySQL Server 4.0 は複数のテーブルを削除できます。これで、ひとつの 表から多くの表であっても、情報に基づいて同時に行を削除できます。 @node ANSI diff SELECT INTO TABLE, ANSI diff Transactions, ANSI diff Sub-selects, Differences from ANSI @subsubsection @code{SELECT INTO TABLE} @findex SELECT INTO TABLE MySQL Server は、まだ、Oracle の SQL 拡張： @code{SELECT ... INTO TABLE ...}がありません。 代わりに、MySQL Server は、ANSI SQL 構文の @code{INSERT INTO ... SELECT ...}が使え、 基本的に同じことができます。 @xref{INSERT SELECT}. @example INSERT INTO tblTemp2 (fldID) SELECT tblTemp1.fldOrder_ID FROM tblTemp1 WHERE tblTemp1.fldOrder_ID > 100; @end example 代わりに、@code{SELECT INTO OUTFILE...} や @code{CREATE TABLE ... SELECT}が使えます。 @node ANSI diff Transactions, ANSI diff Triggers, ANSI diff SELECT INTO TABLE, Differences from ANSI @subsubsection トランザクションと原子的な操作 @findex COMMIT @findex ROLLBACK @cindex transactions, support @cindex transaction-safe tables @cindex tables, updating @cindex updating, tables @cindex @code{InnoDB} tables @cindex @code{BDB} tables @cindex @code{ACID} MySQL Server では、@code{InnoDB} と @code{BDB}@code{Transactional table handlers}で、トランザクションが使えます。@xref{Table types}。 @code{InnoDB} が @code{ACID} 適合にします。 しかし、@code{MyISM}といったMySQL Server のトランザクションでないテーブ ル種は、``@code{Atomic Operations}''(アトミック・オペレーション)と呼ばれ る、データ一貫性のほかの方式にしたがいます。 アトミック・オペレーション が同等かあるいはより良いパフォーマンスを提供するというのが、私たちの経験、 および考えです。MySQL Server では両方の方式があるため、ユーザは、アプリ ケーションで、アトミック・オペレーションの速度が必要か、トランザクション 機能が必要か、決定できます。この選択は、テーブルごとにできます。 厳密に完全性を維持するには、MySQL Server の機能をどのように使用するので しょう？ そして、トランザクションの方式でこれらの機能をどのように比較す るのでしょう？ @enumerate @item トランザクションの方式では、もし、あなたのアプリケーションがきわどい状況 で@code{COMMIT} の代わりに @code{ROLLBACK} の呼び出しに依存しているなら、 トランザクションはより便利でしょう。おまけに、トランザクションは、完了で きなかった更新や不整合を起こしたデータが、確実にデータベースに登録されな いようにできます。そのサーバには、自動的な rollback をする機会が与えられ、 あなたのデータは守られるでしょう。MySQL Server では、ほとんどの場合、更 新前の簡単なチェックを含ませたり、データベースの矛盾を検査して自動的に修 復したり、警告の表示を行ったりする簡単なスクリプトを実行したりすることで、 発生しうる問題を解決できます。MySQL ログを使ったり外部へログを追加したり することで、通常、データに不整合を起こさないで、テーブルを完全に修復でき ることに注意してください。 @item しばしば、トランザクション的に欠陥のあるな更新は、原子的(アトミック)にな るように書き換えることができます。一般的に、トランザクションが解決するす べての一貫性の問題は、データベースが自動的にアボートしないことを保証する ことで、@code{LOCK TABLE}、または、原子的な更新で解決できます。これは、 トランザクション的なデータベースに共通の問題です。 @item もしサーバがダウンすれば、たとえトランザクション的なシステムでもデータを 失います。異なるシステムが存在する違いは、単に、データを失ってもよい時間 幅がどれだけ小さいかにあります。100% 安全なシステムはなく、単に``十分に 安全''があるだけです。最高に安全なトランザクションデータベースと名声の高 いOracleでさえ、そのようなときには、ときどき、データを失います。 MySQL Server を安全にするには、バックアップを取ることと、更新ログを有効 にすることだけです。これで、あなたが他のトランザクションを持つデータベー スで行っているようないかなる場面での修復が可能です。もちろん、バックアッ プをとることは、どのデータベースを使用しているかに関わらず、常に良いこと です。@end enumerate トランザクションの方法は、長所と短所があります。多くのユーザとアプリケー ション開発者は、楽に、アボートが発生したときの問題に関してコードを書ける か、または書く必要があるかに依存します。しかし、原子的な操作の方式が初め てであっても、よりトランザクションに慣れていても、トランザクションを使わ ないテーブルが、高度に調整されたトランザクションテーブルに対して、最高 3 倍から 5 倍速いという長所 一貫性がいちばん重要な状況では、MySQL Server は、トランザクション水準を、 またはトランザクションを使わないテーブルでも高い信頼性と一貫性を提供します。 @code{LOCK TABLE}でテーブルをロックすると、一貫性の確認が済むまで、すべ ての更新は待たされます。(書き込みロックと対称に)読み出しロックだけを取得 するときは読み出しと挿入は、まだ、許されます。新しく挿入されたレコードは、 読み込みロックをもったクライアントからは、読み込みロックを解放するまで見 えません。@code{INSERT DELAYED} を使うと、挿入をローカルにある待ち行列に、 ロックを解放するまで、挿入が完了するまでクライアントを待たせることなく、 積むことができまます。@xref{INSERT DELAYED}. ここでいう``Atomic''(原子性)は、魔法ではありません。ある特定の更新が実行 している間は、ほかのユーザは阻まれることを確実にすることを意味し、自動的 なロールバック(あまり注意を払わないときにトランザクション的なテーブルで 起きえる)が起きえないことだけです。また MySQL Server は、汚染された読み 込みが起きないことを保証します。 次は、トランザクションでないテーブルでのいくつかのテクニックです。 @itemize @bullet @item Loops that need transactions normally can be coded with the help of @code{LOCK TABLES}, and you don't need cursors when you can update records on the fly. @item To avoid using @code{ROLLBACK}, you can use the following strategy: @enumerate @item Use @code{LOCK TABLES ...} to lock all the tables you want to access. @item Test conditions. @item Update if everything is okay. @item Use @code{UNLOCK TABLES} to release your locks. @end enumerate This is usually a much faster method than using transactions with possible @code{ROLLBACK}s, although not always. The only situation this solution doesn't handle is when someone kills the threads in the middle of an update. In this case, all locks will be released but some of the updates may not have been executed. @item You can also use functions to update records in a single operation. You can get a very efficient application by using the following techniques: @itemize @bullet @item Modify fields relative to their current value. @item Update only those fields that actually have changed. @end itemize For example, when we are doing updates to some customer information, we update only the customer data that has changed and test only that none of the changed data, or data that depends on the changed data, has changed compared to the original row. The test for changed data is done with the @code{WHERE} clause in the @code{UPDATE} statement. If the record wasn't updated, we give the client a message: "Some of the data you have changed has been changed by another user." Then we show the old row versus the new row in a window, so the user can decide which version of the customer record he should use. This gives us something that is similar to column locking but is actually even better because we only update some of the columns, using values that are relative to their current values. This means that typical @code{UPDATE} statements look something like these: @example UPDATE tablename SET pay_back=pay_back+'relative change'; UPDATE customer SET customer_date='current_date', address='new address', phone='new phone', money_he_owes_us=money_he_owes_us+'new_money' WHERE customer_id=id AND address='old address' AND phone='old phone'; @end example As you can see, this is very efficient and works even if another client has changed the values in the @code{pay_back} or @code{money_he_owes_us} columns. @item @findex mysql_insert_id() @findex LAST_INSERT_ID() In many cases, users have wanted @code{ROLLBACK} and/or @code{LOCK TABLES} for the purpose of managing unique identifiers for some tables. This can be handled much more efficiently by using an @code{AUTO_INCREMENT} column and either the SQL function @code{LAST_INSERT_ID()} or the C API function @code{mysql_insert_id()}. @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @cindex rows, locking @cindex locking, row-level You can generally code around row-level locking. Some situations really need it, but they are very few. @code{InnoDB} tables support row-level locking. With MyISAM, you can use a flag column in the table and do something like the following: @example UPDATE tbl_name SET row_flag=1 WHERE id=ID; @end example MySQL returns 1 for the number of affected rows if the row was found and @code{row_flag} wasn't already 1 in the original row. You can think of it as though MySQL Server changed the preceding query to: @example UPDATE tbl_name SET row_flag=1 WHERE id=ID AND row_flag <> 1; @end example @end itemize @node ANSI diff Triggers, ANSI diff Foreign Keys, ANSI diff Transactions, Differences from ANSI @subsubsection ストアドプロシジャとトリガ @cindex stored procedures and triggers, defined @cindex procedures, stored @cindex triggers, stored ストアドプロシジャは、サーバ内でコンパイルでき格納できる SQL コマンドの 集まりです。一度これが行われると、クライアントはクエリ全体の再発行を保 持する必要がなく、ストアドプロシジャを参照できます。これはさらにより速い速度を提 供します。クエリは一度だけ解釈され、より少ないデータがサーバとクライアン ト間で送信されるからです。サーバ内に関数ライブラリを持つことによりレ ベルを上げることもできます。 トリガは特別なイベントが発生したときに呼び出されるストアドプロシジャです。 例えば、トランザクションテーブルからレコードが削除されるたびにトリガされ、 それに対応する顧客を顧客テーブルから自動的に削除するという、 ストアドプロシジャをインストールすることができます。 The planned update language will be able to handle stored procedures. Our aim is to have stored procedures implemented in MySQL Server around version 5.0. We are also looking at triggers. @node ANSI diff Foreign Keys, ANSI diff Views, ANSI diff Triggers, Differences from ANSI @subsubsection 外部キー @cindex foreign keys @cindex keys, foreign 注意: SQL の外部キーはテーブルを結合するためには使用できませんが、指示の 完全性の検査のために良く使用されます(foreign key constraints)。 @code{SELECT} 文で複数 テーブルから結果を得たい場合、テーブルの結合によってこれを行います： @example SELECT * FROM table1,table2 WHERE table1.id = table2.id; @end example @xref{JOIN, , @code{JOIN}}. @xref{example-Foreign keys}. In MySQL Server 3.23.44 and up, @code{InnoDB} tables support checking of foreign key constraints. @xref{InnoDB}. For other table types, MySQL Server does parse the @code{FOREIGN KEY} syntax in @code{CREATE TABLE} commands, but without further action being taken. MySQL 内での @code{FOREIGN KEY} 構文は、他の SQL ベンダの @code{CREATE TABLE} コマンドとの互換のためだけに存在します; これは何も行 ないません。@code{ON DELETE ...} がない @code{FOREIGN KEY} 構文は、目的 の作成のために主に使われます。いくつかの ODBC アプリケーションは、自動的 に @code{WHERE} 節を提供するために、これを使用しますが、しかしこれは通常 簡単に無効にできます。@code{FOREIGN KEY} はときどき強制チェックとして使用さ れます。しかし、テーブルに正しい順で行が挿入される場合、このチェックは実 際には不要です。いくつかのアプリケーションがそれが存在することを要求する ため MySQL はこれらの節だけをサポートします（それが動作するかど うかに関わらず）。 MySQL Server では、外部キーを持つテーブルからレコードを削除するときに適 切な @code{DELETE} 文をアプリケーションに追加することで、 @code{ON DELETE ...} が実装されていないという問題を回避できます。実際に は、これは速く(いくつかの場合はより速く)そして外部キーの使用よりもさらに 可搬性があります。 In MySQL Server 4.0 you can use multi-table delete to delete rows from many tables with one command. @xref{DELETE}. In the near future we will extend the @code{FOREIGN KEY} implementation so that the information will be saved in the table specification file and may be retrieved by @code{mysqldump} and ODBC. At a later stage we will implement the foreign key constraints for applications that can't easily be coded to avoid them. Do keep in mind that foreign keys are often misused, which can cause severe problems. Even when used properly, it is not a magic solution for the referential integrity problem, although it does make things easier in some cases. Some advantages of foreign key enforcement: @itemize @bullet @item Assuming proper design of the relations, foreign key constraints will make it more difficult for a programmer to introduce an inconsistency into the database. @item Using cascading updates and deletes can simplify the client code. @item Properly designed foreign key rules aid in documenting relations between tables. @end itemize Disadvantages: @itemize @bullet @item Mistakes, which are easy to make in designing key relations, can cause severe problems@-for example, circular rules, or the wrong combination of cascading deletes. @item A properly written application will make sure internally that it is not violating referential integrity constraints before proceding with a query. Thus, additional checks on the database level will only slow down performance for such an application. @item It is not uncommon for a DBA to make such a complex topology of relations that it becomes very difficult, and in some cases impossible, to back up or restore individual tables. @end itemize @node ANSI diff Views, ANSI diff comments, ANSI diff Foreign Keys, Differences from ANSI @subsubsection ビュー @cindex views It is planned to implement views in MySQL Server around version 5.0. Views are mostly useful for letting users access a set of relations as one table (in read-only mode). Many SQL databases don't allow one to update any rows in a view, but you have to do the updates in the separate tables. As MySQL Server is mostly used in applications and on web systems where the application writer has full control on the database usage, most of our users haven't regarded views to be very important. (At least no one has been interested enough in this to be prepared to finance the implementation of views.) One doesn't need views in MySQL Server to restrict access to columns, as MySQL Server has a very sophisticated privilege system. @xref{Privilege system}. @node ANSI diff comments, , ANSI diff Views, Differences from ANSI @subsubsection コメント開始としての @samp{--} @cindex comments, starting @cindex starting, comments 他のいくつかの SQL データベースは、@samp{--} をコメントの開始のために使 用します。MySQL Server は @samp{#} をコメント開始文字とします。 @code{mysql} コマンドラインツールが @samp{--} で始まる全ての行を削除した としてもです。MySQL では C コメントスタイル @code{/* これはコメ ント */} も使用できます。@xref{Comments}。 MySQL Server バージョン 3.23.3 以上は @samp{--} をサポートしません; この退化したコメントスタイルは、次のコードのように @code{!payment!} の payment の値を自動的に挿入するような何かを使用して自動的に生成される SQL クエリで多くの問題を引き起こすためです: @example UPDATE tbl_name SET credit=credit-!payment! @end example @code{payment} の値が負の場合に何が起きると思いますか？ @code{1--1} は正しい SQL なので、私たちは @samp{--} をコメント開始と見なす ことはひどいことだと思います。 しかし MySQL Server バージョン 3.23 では次を使用できます: @code{1-- これはコメント} 以降の説明では、バージョン 3.23 よりも前の MySQL を実行している場 合だけが対象です: テキストファイルの SQL プログラムが @samp{--} コメントを含んでいる場合、 次を使用すべきです: @example shell> replace " --" " #" < text-file-with-funny-comments.sql \ | mysql database @end example 通常の次の代わりに: @example shell> mysql database < text-file-with-funny-comments.sql @end example 次の方法でも、コマンドファイル中の @samp{--} コメントを @samp{#} コメン トに変更できます: @example shell> replace " --" " #" -- text-file-with-funny-comments.sql @end example それらは次のコマンドで戻してください: @example shell> replace " #" " --" -- text-file-with-funny-comments.sql @end example @node Bugs, , Differences from ANSI, Compatibility @subsection MySQLでの既知のエラーと欠けているデザイン @cindex bugs, known @cindex errors, known @cindex design, issues @cindex known errors @menu * Errors in 3.23:: * Open bugs:: @end menu @node Errors in 3.23, Open bugs, Bugs, Bugs @subsubsection 新しいバージョンで修正されたバージョン3.23におけるエラー バージョン3.23でのエラーが、新しいバージョンで修正されました。 次のようなエラー・バグは、MySQL 3.23 では、修正されていませんでした。というのは、そうしたバグやエラーを直すことは、たくさんのコードの改変を伴うだろうからです。そしてこうした改変は、もっとひどい他のバグを生みかねません。そういうバグはまた、'not fatal'とか'bearable'にクラス分けされます。 @itemize @item 他のスレッドで、テーブルをロックしようとする一方で、マルティプル・テーブルで @code{LOCK TABLE} を実行し、同じコネクションで、マルティプル・テーブルのうち一つで@code{DROP TABLE} を実行する場合には、デットロックを受けることがあり得ます。ですが、これを解決するために、関連するスレッドのいずれかに、@code{KILL} を実行することができます。これは、4.0.12 における修正です。 @item テーブルの一つが空であるところで、@code{SELECT MAX(key_column) FROM t1,t2,t3...} を実行しても、@code{NULL} は返ってきません。それに代わって、フィールドの最大値を返します。これは、4.0.11における修正です。 @end itemize @node Open bugs, , Errors in 3.23, Bugs @subsubsection MySQL での既知のエラーと欠けているデザイン 次のような問題は、既知の問題で、優先的に処理されるべき問題です。 @itemize @bullet @item BDBテーブル上の @code{ANALYZE TABLE} は、場合によっては、@code{mysqld} を再起動しなくては、テーブルを使用できなくするかもしれないものです。 これが起きた際には、MySQLのエラーファイルに、次のようなエラーが表示されるでしょう。 @example 001207 22:07:56 bdb: log_flush: LSN past current end-of-log @end example @item 完了していないマルチ・ステートメント処理を実行中の、@code{BDB} テーブルで、@code{ALTER TABLE} をexecuteしないでください。 （その処理は、恐らく無視されてしまうことでしょう。） @item @code{ANALYZE TABLE} と @code{OPTIMIZE TABLE} と @code{REPAIR TABLE} は、 それに @code{INSERT DELAYED} を用いているテーブルに、問題を起こす原因になるかもしれないものです。 @item @code{LOCK TABLE ...} と @code{FLUSH TABLES ...} を行うことは、テーブル上で実行中のやりかけの処理がなくなることを、保証するものではありません。 @item BDBテーブルは、開くのが少し遅いです。 もしデーターベースの中に多くのBDBテーブルがあるならば、@code{-A} オプションを使っていたり、@code{rehash} を使っている場合には、データーベース上で @code{mysql} クライアントを使用するのには、時間がかかります。もしサイズの大きなテーブルを貯めこんでいるなら、これは特に気をつけなくてはいけないことです。 @item 今のところの複製プロトコルは、@code{LOAD DATA INFILE} や、一文字以上の改行文字を、取り扱えません。 @end itemize 次の問題は、既知の問題ですが、期限内に解決されることでしょう。 @itemize @bullet @item 解決される一時的なテーブルを用いるクエリーで、@code{RPAD} 関数や右側にブランクを加えて終わる文字列関数を使う場合には、結果として得られる文字列は全て、RTRIM 化されてしまうことでしょう。これはクエリーの一例です: @code{SELECT RPAD(t1.field1, 50, ' ') AS f2, RPAD(t2.field2, 50, ' ') AS f1 FROM table1 as t1 LEFT JOIN table2 AS t2 ON t1.record=t2.joinID ORDER BY t2.record;} こうしたクエリーの使用をしても、結果として得られるフィールドの右側にブランクを得ることはできないでしょう、というのがこのバグの最終的な結果です。 上で挙げた動作というのは、MySQLの全てのバージョンにあることです。 これの原因は、最初に一時的なテーブルに用いられるHEAPテーブルが、VARCHARのカラムを取り扱うことができないことに起因します。 この動作は、4.1のリリースの一つで修正されることでしょう。 @item @code{SET CHARACTER SET} を使う場合には、データーベースやテーブルやフィールドの名前に、翻訳された文字を使うことはできません。 @item @code{LIKE ... ESCAPE} において、@code{ESCAPE} と一緒に @code{_} や @code{%} を使うことはできません。 @item (+01.00, 1.00, 01.00),といった具合に、異なったフォーマットで記録された数値を持った @code{DECIMAL} カラムがある場合には、@code{GROUP BY} はそれぞれの値を異なった値と見なします。 @item @code{WHERE} 抜きで用いられる @code{DELETE FROM merge_table} は、テーブルのためのマッピングをクリアするだけです。マッピングされたテーブルにある全部を削除するわけではありません。 @item MIT-pthread を使用するとき、他のディレクトリでビルドできません。 これは MIT-pthread の変更を要求するため、私たちは、これを修正しそうにないです。 @xref{MIT-pthreads}. @item @code{BLOB} の値は、@code{ORDER BY} や @code{ORDER BY} や @code{DISTINCT} に用いる場合には、「信頼性」のないものになります。 これらの場合、 @code{BLOB} の比較の際には最初の @code{max_sort_length} バイト （デフォルト1024）だけが使用されます。 これは @code{mysqld} の @code{-O max_sort_length} オプションで変更可能です。 ほとんどの場合には、substringを用いて行います。 @code{SELECT DISTINCT LEFT(blob,2048) FROM tbl_name} といった具合に。 @item 計算は、@code{BIGINT} か @code{DOUBLE} でなされます。（両方とも、普通は６４ビットの長さです。）どちらを使うかというのは、計算結果を渡してくれる式によってしまいます。 bit関数は @code{BIGINT} の精度でなされ、@code{IF} と @code{ELT()} は @code{BIGINT} か @code{DOUBLE} の精度でなされ、その他は @code{DOUBLE} でなされるというのが、一般的なルールです。 One should try to avoid using unsigned long long values if they resolve to be bigger than 63 bits (9223372036854775807) for anything else than bit fields! MySQL Server 4.0 has better @code{BIGINT} handling than 3.23. @item 全ての文字型のフィールド、@code{BLOB} と @code{TEXT} はのぞいて、は、 検索されるときに最後についているスペースを自動で取り除きます。 @code{CHAR} 型ではこれは OK で、この特徴は ANSI SQL92 に従っていると見なされるでしょう。 MySQL Server のバグは、 @code{VARCHAR} でも同様に行ってしまうことです。 @item 一つのテーブルには、 @code{ENUM} と @code{SET} のカラムは、255までしか使えません。 @item @code{MIN()} や @code{MAX()} や他の集計関数においては、MySQLは今のところ、その組み合わせの中での文字列の相対的な位置によるよりもむしろ、カラムの文字列の値によって、 @code{ENUM} と @code{SET} のカラムを比較しています。 @item @code{mysqld_safe} (旧 @code{safe_mysqld} ) は、@code{mysqld} からのメッセージの全てを、@code{mysqld} ログにリダイレクトします。 これにともなう問題のひとつは、ログを開いたり、再び開いたりするために、@code{mysqladmin refresh} を実行する場合には、@code{stdout} と @code{stderr} が、古いログにリダイレクトされたままだということです。広範囲にわたって @code{--log} を用いる場合には、 @file{'hostname'.log} の代わりに @file{'hostname'.err} に記録するために、@code{mysqld_safe} を編集すべきです。それで、古いものを削除し、m @code{mysqladmin refresh} を実行することで、古いログのためのスペースを簡単に再利用することができます。 @item @code{UPDATE} 文において、カラムは左から右へと更新されます。更新されたカラムを参照する場合には、元の値の代わりに、更新された値が渡されることでしょう。例を見てみましょう。 @example mysql> UPDATE tbl_name SET KEY=KEY+1,KEY=KEY+1; @end example これは、@code{KEY} を @code{1} の代わりに @code{2} で更新します。 @item 同じクエリーにおいて、一時的なテーブルを、一回より多く使うことができません。例えば次のようなものは、実行できません。 @example mysql> SELECT * FROM temporary_table, temporary_table AS t2; @end example @item @code{RENAME} は、 @code{TEMPORARY} テーブルと一緒には、もしくは @code{MERGE} テーブルの中のテーブルと一緒には実行できません。 @item Optimizerは、テーブルの結合において hidden カラムが用いられるかどうかで、 @code{DISTINCT} を違ったふうに扱います。テーブル結合においては、hiddenカラムは、結果の一部として数えられます。（たとえカラムが表示されなくてもです。）一方で、普通のクエリーにおいては、hiddenカラムは @code{DISTINCT} 比較には加えられません。 @code{DISTINCT} を実行する際には、hiddenカラムを決して比較できないように、将来的には恐らく変えることでしょう。 これの実例は次のようなものです。 @example SELECT DISTINCT mp3id FROM band_downloads WHERE userid = 9 ORDER BY id DESC; @end example そして @example SELECT DISTINCT band_downloads.mp3id FROM band_downloads,band_mp3 WHERE band_downloads.userid = 9 AND band_mp3.id = band_downloads.mp3id ORDER BY band_downloads.id DESC; @end example 二番目のケースでは、MySQLサーバー3.23.xでは、リザルトセットでは二つの同じ列を渡してくるかもしれません。（というのも、隠れた @code{id} カラムは異なっているかもしれないからです。） これは、ORDER BYしたカラムを結果のところで指定しないようなクエリー、ANSI SQLでは認められていないことをしたクエリーのみについて起こることだとといことに、気をつけてください。 @item MySQLサーバーでは、トランザクションをサポートしていない種類のテーブルで動かすことが許されていて、それゆえに MySQL サーバーは、データをロールバックできません。そのため、MySQL サーバー上では、幾つかのことが、他の SQL サーバー上とは異なった風に、動作します。このことはまさに、MySQL サーバーが、SQL コマンドのために、ロールバックをする必要が決してないことを保証するためのものです。このことは、カラムの値がアプリケーションにおいて、チェックされねばならない際には、少し困りものかもしれません。ですがこのことは、素晴らしいスピードの増加を、実際に提供してくれることでしょう。そしてそれをしなければとても実現が難しかったであろうような、何らかの効率化を実現するのを、MySQLサーバーに許すようになるでしょう。 もし正しくない値をカラムにセットするなら、MySQLサーバーは、ロールバックをする代わりに、カラムの中に、可能で一番適切な値を記録させることでしょう。 @itemize @minus @item 数値カラムにおける範囲の外で、値を記録しようとするなら、MySQLサーバーはその代わりに、そのカラムにおける最も小さいかもしくは最も大きな可能な値を記録することでしょう。 @item 数値カラムに、数値ではじまらない文字列を記録したい場合には、MySQLサーバーは、その中に０を記録することでしょう。 @item @code{NULL} の値をとらないカラムの中に @code{NULL} を記録したい場合には、MySQLサーバーは、０か’’（空の文字列）をその代わりにその中に記録するでしょう。（ですがこの動作は、-DDONT_USE_DEFAULT_FIELDSコンパイルオプションで、変えることが出来ます。） @item MySQLサーバーは、 @code{DATE} と @code{DATETIME} のカラムに、いくつかの誤った日付（2000-02-31とか2000-02-00のような）の値を記録することができます。これは、日付を確認するというのは、SQLサーバーの仕事ではない、という考えから来ています。MySQLが日付を記録し、全く同じ日付に訂正できる場合には、MySQLはその日付を記録することでしょう。もしその日付が全く間違っている（日付を記録するサーバーの性能を越えている）ならば、それならば特別な日付の値0000-00-00が、カラムの中に記録されることでしょう。 @item もし @code{ENUM} カラムに、サポートされていない値をセットするならば、それはエラーの値である空の文字列、数値の０をセットするでしょう。 @item もし @code{SET} カラムに、サポートされていない値をセットするならば、その値は無視されるでしょう。 @end itemize @item 空のセットを返すようなクエリー上で、 @code{PROCEDURE} を実行するならば、幾つかの場合には、 @code{PROCEDURE} はそのカラムを変えることはないでしょう。 @item @code{MERGE} 型のテーブルの作成する際には、強調されているテーブルの型に互換性があるかどうかは、チェックされません。 @item MySQLサーバーは、 @code{NaN} やダブル型の値の @code{-Inf} や @code{Inf} を、まだ扱えません。これらを使用することは、データをエクスポートしたりインポートしたりする際の問題の原因になるでしょう。中間的な解決として、 @code{NaN} を @code{NULL} に、 @code{-Inf} や @code{Inf} を各々の最小限の @code{double} 型のとりうる最大値に変更しなくてはなりません。 @item 負の数値における @code{LIMIT} は、大きな正の数値として扱われます。 @item もし @code{MERGE} テーブルにおいて用いられるテーブルに、 @code{UNIQUE} インデックスを先ず加えるために、 @code{ALTER TABLE} を用いるならば、さらに @code{MERGE} テーブル上で普通のインデックスを加えるために、 @code{ALTER TABLE} を用いるならば、そのテーブルの中ではユニークではなかった古いキーがあった場合には、キーの順番はテーブルごとに異なっていることでしょう。これは、 @code{ALTER TABLE} が、重複キーをなるべく速く検知できるようにするために、普通のキーの前に、 @code{UNIQUE} キーをおくからです。 @end itemize 以下のものが、MySQLの以前のバージョンにおいて知られていたバグです。: @itemize @bullet @item @code{LOCK TABLES} でロックされたような多くのテーブルの中の一つであるテーブルを、 @code{DROP TABLE} する場合には、hungスレッドが取得されます。 @item 以下のような場合には、コアdumpが取得されます: @itemize @minus @item 遅れたインサートハンドラーが、テーブルに対して未決定のinsertを有する場合。 @item @code{WRITE} をともなう @code{LOCK table} @item @code{FLUSH TABLES}. @end itemize @item MySQLサーバー・バージョン3.23.2以前では、同じキー上の @code{WHERE} を有するキーを更新する @code{UPDATE} は、失敗するかもしれません。というのは、そのキーはレコードを検索するために、用いられ、全く同じ列が複数回にわたり見出されたかもしれないからです。: @example UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100; @end example 代替手段は、次のように使うことです: @example mysql> UPDATE tbl_name SET KEY=KEY+1 WHERE KEY+0 > 100; @end example MySQLサーバーが、 @code{WHERE} 句の表現の中にあるインデックスを用いることはないでしょうから、これは動作します。 @item MySQL Server バージョン 3.23 より前では、全ての数値型で、少数部分が削られてしまいます。 これは、そのフィールドが何桁の小数部を持つか、定義しなければならなかった、と いうことです。 全ての結果は10進の数で正しく返ってきました。 @end itemize プラットホームに特有のバグについては、コンパイリングとポーティングについての節を参照してください。 @node TODO, Comparisons, Compatibility, Introduction @section MySQL and The Future (The TODO) @cindex ToDo list for MySQL @menu * TODO MySQL 4.0:: Things That Should be in 4.0 * TODO MySQL 4.1:: Things That Should be in 4.1 * TODO MySQL 5.0:: Things That Should be in 5.0 * TODO future:: Things That Must be Done in the Near Future * TODO sometime:: Things That Have to be Done Sometime * TODO unplanned:: Things We Don't Plan To Do @end menu This section lists the features that we plan to implement in MySQL Server. もしあなたが優先順位に影響を及ぼしたければ、どうかライセンスかサポート登録して、 私たちにあなたがより速く欲しいものを言ってください。 @xref{Licensing and Support}. The plan is that we in the future will support the full ANSI SQL99 standard, but with a lot of useful extensions. The challenge is to do this without sacrificing the speed or compromising the code. @node TODO MySQL 4.0, TODO MySQL 4.1, TODO, TODO @subsection Things That Should be in 4.0 All done. We now only do bug fixes for MySQL 4.0. @xref{News-4.0.x}. Development has shifted to 4.1 & 5.0 @node TODO MySQL 4.1, TODO MySQL 5.0, TODO MySQL 4.0, TODO @subsection Things That Should be in 4.1 The following features are planned for inclusion into MySQL 4.1. For a list what is already done in MySQL 4.1, see @xref{News-4.1.x}. @itemize @item Stable OpenSSL support (MySQL 4.0 supports rudimentary, not 100% tested, support for OpenSSL). @item Character set casts and syntax for handling multiple character sets. @item Help for all commands from the client. @item More testing of prepared statements and multiple characters sets for one table. @end itemize @node TODO MySQL 5.0, TODO future, TODO MySQL 4.1, TODO @subsection Things That Should be in 5.0 The following features are planned for inclusion into MySQL 5.0. Note that because we have many developers that are working on different projects, there will also be many additional features. There is also a small chance that some of these features will be added to MySQL 4.1. For a list what is already done in MySQL 4.1, see @xref{News-4.1.x}. @itemize @bullet @item Stored procedures. @item Foreign keys support for all table types. @item New text based table definition file format (@file{.frm} files) and a table cache for table definitions. This will enable us to do faster queries of table structures and do more efficient foreign key support. @item @code{SHOW COLUMNS FROM table_name} (used by @code{mysql} client to allow expansions of column names) should not open the table, only the definition file. This will require less memory and be much faster. @item Fail-safe replication. @item Online backup with very low performance penalty. The online backup will make it easy to add a new replication slave without taking down the master. @item @code{ROLLUP} and @code{CUBE} OLAP (Online Analytical Processing) grouping options for data warehousing applications. @item Allow @code{DELETE} on @code{MyISAM} tables to use the record cache. To do this, we need to update the threads record cache when we update the @file{.MYD} file. @item When using @code{SET CHARACTER SET} we should translate the whole query at once and not only strings. This will enable users to use the translated characters in database, table, and column names. @item Resolving the issue of @code{RENAME TABLE} on a table used in an active @code{MERGE} table possibly corrupting the table. @item Add options to the client/server protocol to get progress notes for long running commands. @item Implement @code{RENAME DATABASE}. To make this safe for all storage engines, it should work as follows: @itemize @bullet @item Create the new database. @item For every table do a rename of the table to another database, as we do with the @code{RENAME} command. @item Drop the old database. @end itemize @item Add true @code{VARCHAR} support (there is already support for this in @code{MyISAM}). @item @code{BIT} 型を 1 bit 取るように最適化 （今 @code{BIT} は一文字とります） @item New internal file interface change. This will make all file handling much more general and make it easier to add extensions like RAID. (the current implementation is a hack.) @item Better in-memory (@code{HEAP}) tables: @itemize @bullet @item Dynamic size rows. @item Faster row handling (less copying) @end itemize @end itemize @node TODO future, TODO sometime, TODO MySQL 5.0, TODO @subsection 近い将来に完了せねばならないもの @itemize @bullet @item Don't allow more than a defined number of threads to run MyISAM recover at the same time. @item Change @code{INSERT ... SELECT} to optionally use concurrent inserts. @item Return the original field types() when doing @code{SELECT MIN(column) ... GROUP BY}. @item Multiple result sets. @item Make it possible to specify @code{long_query_time} with a granularity in microseconds. @item Link the @code{myisampack} code into the server. @item Port of the MySQL code to QNX. @item Port of the MySQL code to BeOS. @item Port of the MySQL clients to LynxOS. @item Add a temporary key buffer cache during @code{INSERT/DELETE/UPDATE} so that we can gracefully recover if the index file gets full. @item もし他の disk に symlink されているテーブルに対して @code{ALTER TABLE} を 実行した場合、一時テーブルをこの disk に作成するようにする @item Implement a @code{DATE/DATETIME} type that handles time zone information properly so that dealing with dates in different time zones is easier. @item FreeBSD and MIT-pthreads; do sleeping threads take CPU time? @item Check if locked threads take any CPU time. @item Fix configure so that one can compile all libraries (like @code{MyISAM}) without threads. @item Add an option to periodically flush key pages for tables with delayed keys if they haven't been used in a while. @item キーの部分での JOIN を許す (最適化問題) @item @code{INSERT SQL_CONCURRENT} and @code{mysqld --concurrent-insert} to do a concurrent insert at the end of the file if the file is read-locked. @item サーバサイドのカーソル @item Check if @code{lockd} works with modern Linux kernels; if not, we have to fix @code{lockd}! To test this, start @code{mysqld} with @code{--enable-locking} and run the different fork* test suits. They shouldn't give any errors if @code{lockd} works. @item Allow SQL variables in @code{LIMIT}, like in @code{LIMIT @@a,@@b}. @item Allow update of variables in @code{UPDATE} statements. For example: @code{UPDATE TABLE foo SET @@a=a+b,a=@@a, b=@@a+c}. @item Change when user variables are updated so that one can use them with @code{GROUP BY}, as in the following example: @code{SELECT id, @@a:=COUNT(*), SUM(sum_col)/@@a FROM table_name GROUP BY id}. @item Don't add automatic @code{DEFAULT} values to columns. Give an error when using an @code{INSERT} that doesn't contain a column that doesn't have a @code{DEFAULT}. @item Fix @file{libmysql.c} to allow two @code{mysql_query()} commands in a row without reading results or give a nice error message when one does this. @item なぜいくつかの FreeBSD システムで MIT-pthreads @code{ctime()} が動かないか検証。 @item @code{TIMESTAMP} と @code{AUTO_INCREMENT} フィールドを更新しないように、 @code{IMAGE} オプションを @code{LOAD DATA INFILE} に追加。 @item Added @code{LOAD DATE INFILE ... UPDATE} syntax. @itemize @bullet @item For tables with primary keys, if the data contains the primary key, entries matching that primary key are updated from the remainder of the columns. However, columns @strong{missing} from the incoming data feed are not touched. @item For tables with primary keys that are missing some part of the key in the incoming data stream, or that have no primary key, the feed is treated as a @code{LOAD DATA INFILE ... REPLACE INTO} now. @end itemize @item Make @code{LOAD DATA INFILE} understand syntax like: @example LOAD DATA INFILE 'file_name.txt' INTO TABLE tbl_name TEXT_FIELDS (text_field1, text_field2, text_field3) SET table_field1=CONCAT(text_field1, text_field2), table_field3=23 IGNORE text_field3 @end example This can be used to skip over extra columns in the text file, or update columns based on expressions of the read data. @item @code{LOAD DATA INFILE 'file_name' INTO TABLE 'table_name' ERRORS TO err_table_name}. This would cause any errors and warnings to be logged into the @code{err_table_name} table. That table would have a structure like: @example line_number - line number in datafile error_message - the error/warning message and maybe data_line - the line from the datafile @end example @item @code{mysql} から自動的に Netscape に出力 @item @code{LOCK DATABASES}. (いろいろなオプション付きで) @item Functions: ADD_TO_SET(value,set) and REMOVE_FROM_SET(value,set). @item @code{t1 JOIN t2 ON ...} と @code{t1 JOIN t2 USING ...} の使用の追加。 現在、 @code{LEFT JOIN} のみが使用できます。 @item Many more variables for @code{show status}. Records reads and updates. Selects on 1 table and selects with joins. Mean number of tables in select. Number of @code{ORDER BY} and @code{GROUP BY} queries. @item If you abort @code{mysql} in the middle of a query, you should open another connection and kill the old running query. Alternatively, an attempt should be made to detect this in the server. @item Add a storage engine interface for table information so that you can use it as a system table. This would be a bit slow if you requested information about all tables, but very flexible. @code{SHOW INFO FROM tbl_name} for basic table information should be implemented. @item Allow @code{SELECT a FROM crash_me LEFT JOIN crash_me2 USING (a)}; in this case @code{a} is assumed to come from the @code{crash_me} table. @item @item Oracle-like @code{CONNECT BY PRIOR ...} to search hierarchy structures. @item @code{mysqladmin copy database new-database}; requires @code{COPY} command to be added to @code{mysqld}. @item Processlist should show number of queries/threads. @item @code{SHOW HOSTS} for printing information about the hostname cache. @item @code{DELETE} and @code{REPLACE} options to the @code{UPDATE} statement (this will delete rows when one gets a duplicate key error while updating). @item Change the format of @code{DATETIME} to store fractions of seconds. @item Add all missing ANSI92 and ODBC 3.0 types. @item Change table names from empty strings to @code{NULL} for calculated columns. @item Don't use @code{Item_copy_string} on numerical values to avoid number->string->number conversion in case of: @code{SELECT COUNT(*)*(id+0) FROM table_name GROUP BY id} @item Make it possible to use the new GNU regexp library instead of the current one (the GNU library should be much faster than the old one). @item Change so that @code{ALTER TABLE} doesn't abort clients that execute @code{INSERT DELAYED}. @item Fix so that when columns are referenced in an @code{UPDATE} clause, they contain the old values from before the update started. @item Add simulation of @code{pread()}/@code{pwrite()} on Windows to enable concurrent inserts. @item A logfile analyser that could parse out information about which tables are hit most often, how often multi-table joins are executed, etc. It should help users identify areas or table design that could be optimised to execute much more efficient queries. @item Add @code{SUM(DISTINCT)}. @item Add @code{ANY()}, @code{EVERY()}, and @code{SOME()} group functions. In ANSI SQL these work only on boolean columns, but we can extend these to work on any columns/expressions by applying: value == 0 -> FALSE and value <> 0 -> TRUE. @item Fix that the type for @code{MAX(column)} is the same as the column type: @example mysql> CREATE TABLE t1 (a DATE); mysql> INSERT INTO t1 VALUES (NOW()); mysql> CREATE TABLE t2 SELECT MAX(a) FROM t1; mysql> SHOW COLUMNS FROM t2; @end example @item Come up with a nice syntax for a statement that will @code{UPDATE} the row if it exists and @code{INSERT} a new row if the row didn't exist (like @code{REPLACE} works with @code{INSERT} / @code{DELETE}). @end itemize @node TODO sometime, TODO unplanned, TODO future, TODO @subsection いつかは行うべきもの @itemize @bullet @item Implement function: @code{get_changed_tables(timeout,table1,table2,...)}. @item Change reading through tables to use memmap when possible. Now only compressed tables use memmap. @item Make the automatic timestamp code nicer. Add timestamps to the update log with @code{SET TIMESTAMP=#;}. @item Use read/write mutex in some places to get more speed. @item Full foreign key support in for @code{MyISAM} tables, probably after the implementation of stored procedures with triggers. @item Simple views (first on one table, later on any expression). @item Automatically close some tables if a table, temporary table, or temporary files gets error 23 (not enough open files). @item When one finds a field=#, change all occurrences of field to #. Now this is only done for some simple cases. @item Change all const expressions with calculated expressions if possible. @item Optimise key = expression. At the moment only key = field or key = constant are optimised. @item Join some of the copy functions for nicer code. @item Change @file{sql_yacc.yy} to an inline parser to reduce its size and get better error messages (5 days). @item Change the parser to use only one rule per different number of arguments in function. @item Use of full calculation names in the order part (for ACCESS97). @item @code{MINUS}, @code{INTERSECT}, and @code{FULL OUTER JOIN}. (Currently @code{UNION} [in 4.0] and @code{LEFT OUTER JOIN} are supported.) @item @code{SQL_OPTION MAX_SELECT_TIME=#} to put a time limit on a query. @item Make the update log write to a database. @item Add to @code{LIMIT} to allow retrieval of data from the end of a result set. @item Alarm around client connect/read/write functions. @item Please note the changes to @code{safe_mysqld}: according to FSSTND (which Debian tries to follow) PID files should go into @file{/var/run/.pid} and log files into @file{/var/log}. It would be nice if you could put the "DATADIR" in the first declaration of "pidfile" and "log", so the placement of these files can be changed with a single statement. @item Allow a client to request logging. @item Add use of @code{zlib()} for @code{gzip}-ed files to @code{LOAD DATA INFILE}. @item Fix sorting and grouping of @code{BLOB} columns (partly solved now). @item Stored procedures. Triggers are also being looked at. @item A simple (atomic) update language that can be used to write loops and such in the MySQL server. @item Change to use semaphores when counting threads. One should first implement a semaphore library to MIT-pthreads. @item Don't assign a new @code{AUTO_INCREMENT} value when one sets a column to 0. Use @code{NULL} instead. @item Add full support for @code{JOIN} with parentheses. @item As an alternative for one thread/connection manage a pool of threads to handle the queries. @item Allow one to get more than one lock with @code{GET_LOCK}. When doing this, one must also handle the possible deadlocks this change will introduce. @end itemize Time is given according to amount of work, not real time. @node TODO unplanned, , TODO sometime, TODO @subsection 行う予定のない物 @itemize @bullet @item Nothing; we aim toward full ANSI 92/ANSI 99 compliancy. @end itemize @node Comparisons, , TODO, Introduction @section MySQL と他のオープンソースデータベースの比較 @cindex databases, MySQL vs. others @cindex comparisons, MySQL vs. others Our users have successfully run their own benchmarks against a number of @code{Open Source} and traditional database servers. We are aware of tests against @code{Oracle} server, @code{DB/2} server, @code{Microsoft SQL Server}, and other commercial products. Due to legal reasons we are restricted from publishing some of those benchmarks in our reference manual. This section includes a comparison with @code{mSQL} for historical reasons and with @code{PostgreSQL} as it is also an @code{Open Source} database. If you have benchmark results that we can publish, please contact us at @email{benchmarks@@mysql.com}. For comparative lists of all supported functions and types as well as measured operational limits of many different database systems, see the @code{crash-me} web page at @uref{http://www.mysql.com/information/crash-me.php}. @menu * Compare mSQL:: How MySQL compares to @code{mSQL} * Compare PostgreSQL:: How MySQL Compares to @code{PostgreSQL} @end menu @node Compare mSQL, Compare PostgreSQL, Comparisons, Comparisons @subsection How MySQL Compares to @code{mSQL} @cindex mSQL, MySQL vs mSQL, overview @table @strong @item Performance 真の速度比較のためは、増加する MySQL ベンチマークスイートを見て下さい @xref{MySQL Benchmarks}. Because there is no thread creation overhead, a small parser, few features, and simple security, @code{mSQL} should be quicker at: @itemize @bullet @item Tests that perform repeated connects and disconnects, running a very simple query during each connection. @item @code{INSERT} operations into very simple tables with few columns and keys. @item @code{CREATE TABLE} and @code{DROP TABLE}. @item @code{SELECT} on something that isn't an index. (A table scan is very easy.) @end itemize これらのオペレーションはとても単純なので、開始のオーバーヘッドが高くなる ときにそれらを良くするのは難しいです。接続が確立された後は MySQL はとても良い性能になります。 MySQL Server は @code{mSQL} や多くの他の SQL 実装よりとても速いです: @itemize @bullet @item Complex @code{SELECT} operations. @item 大きな結果を検索する場合。(MySQL はより良く, より速くそしてより安全 なプロトコルを持ちます) @item 可変長文字列を持つテーブル。MySQL はさらに効率的な処理を持ち、 @code{VARCHAR} 上にインデックスを持つことができます。 @item Handling tables with many columns. @item Handling tables with large record lengths. @item @code{SELECT} with many expressions. @item @code{SELECT} on large tables. @item 同時に多くの接続を処理します。MySQL は完全なマルチスレッドです。 各接続はそれ自身のスレッドを持ちます。これは、それらが他を待つ必要がない ことを意味します(同じテーブルを変更するクエリが実行される場合を除く)。 @code{mSQL} では、全ての他の接続は、最初のもの - クエリが長いか短いかに 関わらず - が実行され、終わるまで待つ必要があります。その後次の接続が与 えられ、他の全ては再び待ちます。 @item Joins. @code{mSQL} can become pathologically slow if you change the order of tables in a @code{SELECT}. In the benchmark suite, a time more than 15,000 times slower than MySQL Server was seen. This is due to @code{mSQL}'s lack of a join optimiser to order tables in the optimal order. However, if you put the tables in exactly the right order in @code{mSQL}2 and the @code{WHERE} is simple and uses index columns, the join will be relatively fast! @xref{MySQL Benchmarks}. @item @code{ORDER BY} and @code{GROUP BY}. @item @code{DISTINCT}. @item @code{TEXT} または @code{BLOB} フィールドの使用。 @end itemize @item SQL Features @itemize @bullet @item @code{GROUP BY} and @code{HAVING}. @code{mSQL} does not support @code{GROUP BY} at all. MySQL Server supports a full @code{GROUP BY} with both @code{HAVING} and the following functions: @code{COUNT()}, @code{AVG()}, @code{MIN()}, @code{MAX()}, @code{SUM()}, and @code{STD()}. @code{COUNT(*)} is optimised to return very quickly if the @code{SELECT} retrieves from one table, no other columns are retrieved, and there is no @code{WHERE} clause. @code{MIN()} and @code{MAX()} may take string arguments. @item @code{INSERT} and @code{UPDATE} with calculations. MySQL Server can do calculations in an @code{INSERT} or @code{UPDATE}. For example: @example mysql> UPDATE SET x=x*10+y WHERE x<20; @end example @item Aliasing. MySQL Server has column aliasing. @item Qualifying column names. In MySQL Server, if a column name is unique among the tables used in a query, you do not have to use the full qualifier. @item @code{SELECT} with functions. MySQL Server has many functions (too many to list here; see @ref{Functions}). @end itemize @item Disk Space Efficiency これは、テーブルをどのように小さくできるかです。 MySQL はとても精密な型を持ちます。とても小さい領域を使用するテーブルを作成でき るためです。MySQL データ型の有用な例は、3バイト長の @code{MEDIUMINT} です。10,000,000 レコードを持つ場合、1レコードあたり1バイトの節約でもと ても重要です。 @code{mSQL2} は4つの型(char,text,int,real)しかないので、小さなテーブルを 得るのは難しいです。 @item Stability これを客観的に判断するのは難しいです。MySQL の安定性については @ref{Stability} を参照してください。 私たちには @code{mSQL} 安定性の経験がありません。そのため、私たちはこれにつ いては何も言えません。 @item Price もう一つの重要な問題はもちろんライセンスです。MySQL は @code{mSQL} よりも柔軟なライセンスを持っています。そして @code{mSQL} よ りもより安いです。少なくとも、あなたが使用を選択した製品全てに、ライセン スまたは email サポートへの支払いを考慮することを覚えていて下さい。 MySQL を含めた製品を売る場合、もちろんこのライセンスの獲得が要求 されます。 @item Perl Interfaces MySQL は基本的に @code{mSQL} と同じ perl インタフェースと、いくつかの追 加機能を持ちます。 @item JDBC (Java) MySQL Server currently has a lot of different JDBC drivers: @itemize @bullet @item MySQL Connector/J is a native Java driver. Version 3.x is released under dual licensing (GPL and commercial). @item The Resin driver: this is a commercial JDBC driver released under open source. @uref{http://www.caucho.com/projects/jdbc-mysql/index.xtp} @item The gwe driver: a Java interface by GWE technologies (not supported anymore). @item The jms driver: an improved gwe driver by Xiaokun Kelvin ZHU @email{X.Zhu@@brad.ac.uk} (not supported anymore). @item The twz driver: a type 4 JDBC driver by Terrence W. Zellers @email{zellert@@voicenet.com}. This is commercial but is free for private and educational use (not supported anymore). @end itemize The recommended driver is the mm driver. The Resin driver may also be good (at least the benchmarks look good), but we haven't received that much information about this yet. We know that @code{mSQL} has a JDBC driver, but we have too little experience with it to compare. @item 開発の速度 MySQL はとても小さい開発チームを持っていますが、私たちは C と C++ のコーディ ングをとても速く行います。スレッド、関数、 @code{GROUP BY} などはまだ @code{mSQL} には実装されていませんので、追いつくにはたくさんのことをしなければなりません。 この上でいくつかの見通しを得るために、去年の @code{mSQL} @file{HISTORY} ファ イルを見て、MySQL Reference Manual News 節と比較できます(@pxref{News})。 速く開発された多くのものが、かなり明白になります。 @item ユーティリティプログラム @code{mSQL} と MySQL は多くの興味深いサードパーティツールを持っ ています。上位への移行 (@code{mSQL} -> MySQL) はとても簡単です。 MySQL は、ほとんど全ての興味深い @code{mSQL} アプリケーションを 持っています。 MySQL には、簡単な @code{msql2mysql} プログラムが用意されています。 これは、@code{mSQL} と MySQL の C API 関数のスペルの違いを修正するプログラムです。 たとえば、@code{mysqlConnect()}のインスタンスを変えるには、 @code{mysql_connect()}. @code{mSQL} から MySQL への変換は通常、数分使用するだけです。 @end table @menu * Using mSQL tools:: How to convert @code{mSQL} tools for MySQL * Protocol differences:: How @code{mSQL} and MySQL Client/Server Communications Protocols Differ * Syntax differences:: How @code{mSQL} 2.0 SQL Syntax Differs from MySQL @end menu @node Using mSQL tools, Protocol differences, Compare mSQL, Compare mSQL @subsubsection How to Convert @code{mSQL} Tools for MySQL @cindex MySQL tools, conversion @cindex converting, tools @cindex tools, converting According to our experience, it doesn't take long to convert tools such as @code{msql-tcl} and @code{msqljava} that use the @code{mSQL} C API so that they work with the MySQL C API. The conversion procedure is: @enumerate @item シェルスクリプト @code{msql2mysql} をソースに実行します。バイナリプログラム @code{replace} が必要です。これは MySQL で配布されます。 @item コンパイル。 @item 全てのコンパイラエラーを修復します。 @end enumerate MySQL と @code{mSQL} 間の C API の違い: @itemize @bullet @item MySQL は @code{MYSQL} 構造体を接続型として使用します (@code{mSQL} は @code{int} を使用します)。 @item @code{mysql_connect()} は @code{MYSQL} 構造体へのポインタをパラメータとして使用します。そ れをグローバルに定義したり、その獲得に @code{malloc()} を使用するのは簡単です。 @code{mysql_connect()} ユーザ飛ばすワードを識別する二つのパラメータを取ります。 デフォルトで使うときには@code{NULL, NULL}を指定します。 @item @code{mysql_error()} は @code{MYSQL} 構造体をパラメータとして使用します。古いコードを移 行する場合、あなたの古い @code{msql_error()} コードへパラメータを追加してください。 @item MySQLは全てのエラーについて、エラー番号とテキストのエラーメッセージを返します。 @code{mSQL}はテキストのエラーメッセージしか返しません。 @item Some incompatibilities exist as a result of MySQL supporting multiple connections to the server from the same process. @end itemize @node Protocol differences, Syntax differences, Using mSQL tools, Compare mSQL @subsubsection How @code{mSQL} and MySQL Client/Server Communications Protocols Differ @cindex communications protocols @cindex mSQL vs. MySQL, protocol There are enough differences that it is impossible (or at least not easy) to support both. The most significant ways in which the MySQL protocol differs from the @code{mSQL} protocol are listed here: @itemize @bullet @item メッセージバッファは多くの結果行を含めます。 @item クエリや結果が現在のバッファよりも大きい場合、サーバとクライアントの 制限(設定可能)まで、メッセージバッファは動的に増大されます。 @item 全てのパケットは、パケットの重複や見失いを見つけ出すために、番号づけさ れています。 @item 全ての項目は ASCII で送られ、項目の行と長さはパックされたバイナリコーディン グ(1, 2 または 3 バイト)で送られます。 @item MySQL はバッファされない結果で読み込み可能です(クライアント内に完全なセッ トを格納する必要がありません)。 @item 一つの書き込み/読み込みが 30 秒以上かかると、サーバは接続をクローズしま す。 @item 接続で 8 時間何も起きないと、サーバは接続をクローズします。 @end itemize @node Syntax differences, , Protocol differences, Compare mSQL @subsubsection How @code{mSQL} 2.0 SQL Syntax Differs from MySQL @noindent @strong{Column types} @table @code @item MySQL Server Has the following additional types (among others; @pxref{CREATE TABLE, , @code{CREATE TABLE}}): @itemize @bullet @item @c FIX bad lingo, needs rephrasing @code{ENUM} type for one of a set of strings. @item @c FIX bad lingo, needs rephrasing @code{SET} type for many of a set of strings. @item @code{BIGINT} type for 64-bit integers. @end itemize @item MySQL Server also supports the following additional type attributes: @itemize @bullet @item @code{UNSIGNED} option for integer and floating-point columns. @item @code{ZEROFILL} option for integer columns. @item @code{AUTO_INCREMENT} option for integer columns that are a @code{PRIMARY KEY}. @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @item @code{DEFAULT} value for all columns. @end itemize @item mSQL2 @code{mSQL} column types correspond to the MySQL types shown in the following table: @multitable @columnfractions .15 .70 @item @code{mSQL} @strong{type} @tab @strong{Corresponding MySQL type} @item @code{CHAR(len)} @tab @code{CHAR(len)} @item @code{TEXT(len)} @tab @code{TEXT(len)}. @code{len} is the maximal length. And @code{LIKE} works. @item @code{INT} @tab @code{INT}. With many more options! @item @code{REAL} @tab @code{REAL}. Or @code{FLOAT}. Both 4- and 8-byte versions are available. @item @code{UINT} @tab @code{INT UNSIGNED} @item @code{DATE} @tab @code{DATE}. Uses ANSI SQL format rather than @code{mSQL}'s own format. @item @code{TIME} @tab @code{TIME} @item @code{MONEY} @tab @code{DECIMAL(12,2)}. A fixed-point value with two decimals. @end multitable @end table @noindent @strong{Index Creation} @table @code @item MySQL Server Indexes may be specified at table creation time with the @code{CREATE TABLE} statement. @item mSQL Indexes must be created after the table has been created, with separate @code{CREATE INDEX} statements. @end table @noindent @strong{To Insert a Unique Identifier into a Table} @table @code @item MySQL Server Use @code{AUTO_INCREMENT} as a column type specifier. @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @item mSQL Create a @code{SEQUENCE} on a table and select the @code{_seq} column. @end table @noindent @strong{To Obtain a Unique Identifier for a Row} @table @code @item MySQL Server Add a @code{PRIMARY KEY} or @code{UNIQUE} key to the table and use this. New in Version 3.23.11: If the @code{PRIMARY} or @code{UNIQUE} key consists of only one column and this is of type integer, one can also refer to it as @code{_rowid}. @item mSQL Use the @code{_rowid} column. Observe that @code{_rowid} may change over time depending on many factors. @end table @noindent @strong{To Get the Time a Column Was Last Modified} @table @code @item MySQL Server Add a @code{TIMESTAMP} column to the table. This column is automatically set to the current date and time for @code{INSERT} or @code{UPDATE} statements if you don't give the column a value or if you give it a @code{NULL} value. @item mSQL Use the @code{_timestamp} column. @end table @noindent @strong{@code{NULL} Value Comparisons} @table @code @item MySQL Server MySQL Server follows ANSI SQL, and a comparison with @code{NULL} is always @code{NULL}. @item mSQL In @code{mSQL}, @code{NULL = NULL} is TRUE. You must change @code{=NULL} to @code{IS NULL} and @code{<>NULL} to @code{IS NOT NULL} when porting old code from @code{mSQL} to MySQL Server. @end table @noindent @strong{String Comparisons} @table @code @item MySQL Server Normally, string comparisons are performed in case-independent fashion with the sort order determined by the current character set (ISO-8859-1 Latin1 by default). If you don't like this, declare your columns with the @code{BINARY} attribute, which causes comparisons to be done according to the ASCII order used on the MySQL server host. @item mSQL All string comparisons are performed in case-sensitive fashion with sorting in ASCII order. @end table @noindent @strong{Case-insensitive Searching} @table @code @item MySQL Server @code{LIKE} is a case-insensitive or case-sensitive operator, depending on the columns involved. If possible, MySQL uses indexes if the @code{LIKE} argument doesn't start with a wildcard character. @item mSQL Use @code{CLIKE}. @end table @noindent @strong{Handling of Trailing Spaces} @table @code @item MySQL Server Strips all spaces at the end of @code{CHAR} and @code{VARCHAR} columns. Use a @code{TEXT} column if this behaviour is not desired. @item mSQL Retains trailing space. @end table @noindent @strong{@code{WHERE} Clauses} @table @code @item MySQL Server MySQL correctly prioritises everything (@code{AND} is evaluated before @code{OR}). To get @code{mSQL} behaviour in MySQL Server, use parentheses (as shown in an example later in this section). @item mSQL Evaluates everything from left to right. This means that some logical calculations with more than three arguments cannot be expressed in any way. It also means you must change some queries when you upgrade to MySQL Server. You do this easily by adding parentheses. Suppose you have the following @code{mSQL} query: @example mysql> SELECT * FROM table WHERE a=1 AND b=2 OR a=3 AND b=4; @end example To make MySQL Server evaluate this the way that @code{mSQL} would, you must add parentheses: @example mysql> SELECT * FROM table WHERE (a=1 AND (b=2 OR (a=3 AND (b=4)))); @end example @end table @noindent @strong{Access Control} @table @code @item MySQL Server Has tables to store grant (permission) options per user, host, and database. @xref{Privileges}. @item mSQL Has a file @file{mSQL.acl} in which you can grant read/write privileges for users. @end table @node Compare PostgreSQL, , Compare mSQL, Comparisons @subsection How MySQL Compares to @code{PostgreSQL} @cindex PostgreSQL vs. MySQL, overview When reading the following, please note that both products are continually evolving. We at MySQL AB and the PostgreSQL developers are both working on making our respective databases as good as possible, so we are both a serious alternative to any commercial database. The following comparison is made by us at MySQL AB. We have tried to be as accurate and fair as possible, but although we know MySQL Server thoroughly, we don't have a full knowledge of all PostgreSQL features, so we may have got some things wrong. We will, however, correct these when they come to our attention. We would first like to note that PostgreSQL and MySQL Server are both widely used products, but with different design goals, even if we are both striving toward ANSI SQL compliancy. This means that for some applications MySQL Server is more suited, while for others PostgreSQL is more suited. When choosing which database to use, you should first check if the database's feature set satisfies your application. If you need raw speed, MySQL Server is probably your best choice. If you need some of the extra features that only PostgreSQL can offer, you should use @code{PostgreSQL}. @menu * MySQL-PostgreSQL goals:: MySQL and PostgreSQL development strategies * MySQL-PostgreSQL features:: Featurewise Comparison of MySQL and PostgreSQL * MySQL-PostgreSQL benchmarks:: Benchmarking MySQL and PostgreSQL @end menu @node MySQL-PostgreSQL goals, MySQL-PostgreSQL features, Compare PostgreSQL, Compare PostgreSQL @subsubsection MySQL and PostgreSQL development strategies @cindex PostgreSQL vs. MySQL, strategies When adding things to MySQL Server we take pride to do an optimal, definite solution. The code should be so good that we shouldn't have any need to change it in the foreseeable future. We also do not like to sacrifice speed for features but instead will do our utmost to find a solution that will give maximal throughput. This means that development will take a little longer, but the end result will be well worth this. This kind of development is only possible because all server code are checked by one of a few (currently two) persons before it's included in the MySQL server. We at MySQL AB believe in frequent releases to be able to push out new features quickly to our users. Because of this we do a new small release about every three weeks, and a major branch every year. All releases are thoroughly tested with our testing tools on a lot of different platforms. PostgreSQL is based on a kernel with lots of contributors. In this setup it makes sense to prioritise adding a lot of new features, instead of implementing them optimally, because one can always optimise things later if there arises a need for this. Another big difference between MySQL Server and PostgreSQL is that nearly all of the code in the MySQL server is coded by developers that are employed by MySQL AB and are still working on the server code. The exceptions are the transaction engines and the regexp library. This is in sharp contrast to the PostgreSQL code, the majority of which is coded by a big group of people with different backgrounds. It was only recently that the PostgreSQL developers announced that their current developer group had finally had time to take a look at all the code in the current PostgreSQL release. Both of the aforementioned development methods have their own merits and drawbacks. We here at MySQL AB think, of course, that our model is better because our model gives better code consistency, more optimal and reusable code, and in our opinion, fewer bugs. Because we are the authors of the MySQL server code, we are better able to coordinate new features and releases. @node MySQL-PostgreSQL features, MySQL-PostgreSQL benchmarks, MySQL-PostgreSQL goals, Compare PostgreSQL @subsubsection Featurewise Comparison of MySQL and PostgreSQL @cindex PostgreSQL vs. MySQL, features On the @code{crash-me} page (@uref{http://www.mysql.com/information/crash-me.php}) you can find a list of those database constructs and limits that one can detect automatically with a program. Note, however, that a lot of the numerical limits may be changed with startup options for their respective databases. This web page is, however, extremely useful when you want to ensure that your applications work with many different databases or when you want to convert your application from one database to another. MySQL Server offers the following advantages over PostgreSQL: @itemize @bullet @item @code{MySQL} Server is generally much faster than PostgreSQL. MySQL 4.0.1 also has a query cache that can boost up the query speed for mostly-read-only sites many times. @item MySQL has a much larger user base than PostgreSQL. Therefore, the code is tested more and has historically proven more stable than PostgreSQL. MySQL Server is used more in production environments than PostgreSQL, mostly thanks to the fact that MySQL AB, formerly TCX DataKonsult AB, has provided top-quality commercial support for MySQL Server from the day it was released, whereas until recently PostgreSQL was unsupported. @item MySQL Server works better on Windows than PostgreSQL does. MySQL Server runs as a native Windows application (a service on NT/2000/XP), while PostgreSQL is run under the @code{Cygwin} emulation. We have heard that PostgreSQL is not yet that stable on Windows but we haven't been able to verify this ourselves. @item MySQL has more APIs to other languages and is supported by more existing programs than PostgreSQL. @xref{Contrib}. @item MySQL Server works on 24/7 heavy-duty systems. In most circumstances you never have to run any cleanups on MySQL Server. PostgreSQL doesn't yet support 24/7 systems because you have to run @code{VACUUM} once in a while to reclaim space from @code{UPDATE} and @code{DELETE} commands and to perform statistics analyses that are critical to get good performance with PostgreSQL. @code{VACUUM} is also needed after adding a lot of new rows to a table. On a busy system with lots of changes, @code{VACUUM} must be run very frequently, in the worst cases even many times a day. During the @code{VACUUM} run, which may take hours if the database is big, the database is, from a production standpoint, practically dead. Please note: in PostgreSQL version 7.2, basic vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new @code{VACUUM FULL} command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. @item MySQL replication has been thoroughly tested, and is used by sites like: @itemize @minus @item Yahoo Finance (@uref{http://finance.yahoo.com/}) @item Mobile.de (@uref{http://www.mobile.de/}) @item Slashdot (@uref{http://www.slashdot.org/}) @end itemize @item Included in the MySQL distribution are two different testing suites, @file{mysql-test-run} and @code{crash-me} (@uref{http://www.mysql.com/information/crash-me.php}), as well as a benchmark suite. The test system is actively updated with code to test each new feature and almost all reproduceable bugs that have come to our attention. We test MySQL Server with these on a lot of platforms before every release. These tests are more sophisticated than anything we have seen from PostgreSQL, and they ensure that the MySQL Server is kept to a high standard. @item There are far more books in print about MySQL Server than about PostgreSQL. O'Reilly, SAMS, Que, and New Riders are all major publishers with books about MySQL. All MySQL features are also documented in the MySQL online manual because when a new feature is implemented, the MySQL developers are required to document it before it's included in the source. @item MySQL Server supports more of the standard ODBC functions than @code{PostgreSQL}. @item MySQL Server has a much more sophisticated @code{ALTER TABLE}. @item MySQL Server has support for tables without transactions for applications that need all the speed they can get. The tables may be memory-based, @code{HEAP} tables or disk based @code{MyISAM}. @xref{Table types}. @item MySQL Server has support for two different storage engines that support transactions, @code{InnoDB}, and @code{BerkeleyDB}. Because every transaction engine performs differently under different conditions, this gives the application writer more options to find an optimal solution for his or her setup, if need be per individual table. @xref{Table types}. @item @code{MERGE} tables gives you a unique way to instantly make a view over a set of identical tables and use these as one. This is perfect for systems where you have log files that you order, for example, by month. @xref{MERGE}. @item The option to compress read-only tables, but still have direct access to the rows in the table, gives you better performance by minimising disk reads. This is very useful when you are archiving things. @xref{myisampack, , @code{myisampack}}. @item MySQL Server has internal support for full-text search. @xref{Fulltext Search}. @item You can access many databases from the same connection (depending, of course, on your privileges). @item MySQL Server is coded from the start to be multi-threaded, while PostgreSQL uses processes. Context switching and access to common storage areas is much faster between threads than between separate processes. This gives MySQL Server a big speed advantage in multi-user applications and also makes it easier for MySQL Server to take full advantage of symmetric multiprocessor (SMP) systems. @item MySQL Server has a much more sophisticated privilege system than PostgreSQL. While PostgreSQL only supports @code{INSERT}, @code{SELECT}, and @code{UPDATE/DELETE} grants per user on a database or a table, MySQL Server allows you to define a full set of different privileges on the database, table, and column level. MySQL Server also allows you to specify the privilege on host and user combinations. @xref{GRANT}. @item MySQL Server supports a compressed client/server protocol which improves performance over slow links. @item MySQL Server employs a ``storage engine'' concept, and is the only relational database we know of built around this concept. This allows different low-level table types to be called from the SQL engine, and each table type can be optimised for different performance characteristics. @item All MySQL table types (except @code{InnoDB}) are implemented as files (one table per file), which makes it really easy to back up, move, delete, and even symlink databases and tables, even when the server is down. @item Tools to repair and optimise @code{MyISAM} tables (the most common MySQL table type). A repair tool is only needed when a physical corruption of a datafile happens, usually from a hardware failure. It allows a majority of the data to be recovered. @item Upgrading MySQL Server is painless. When you are upgrading MySQL Server, you don't need to dump/restore your data, as you have to do with most PostgreSQL upgrades. @end itemize Drawbacks with MySQL Server compared to PostgreSQL: @itemize @bullet @item The transaction support in MySQL Server is not yet as well tested as PostgreSQL's system. @item Because MySQL Server uses threads, which are not yet flawless on many OSes, one must either use binaries from @uref{http://www.mysql.com/downloads/}, or carefully follow our instructions in @ref{Installing source} to get an optimal binary that works in all cases. @item Table locking, as used by the non-transactional @code{MyISAM} tables, is in many cases faster than page locks, row locks, or versioning. The drawback, however, is that if one doesn't take into account how table locks work, a single long-running query can block a table for updates for a long time. This can usually be avoided when designing the application. If not, one can always switch the trouble table to use one of the transactional table types. @xref{Table locking}. @item With UDF (user-defined functions) one can extend MySQL Server with both normal SQL functions and aggregates, but this is not yet as easy or as flexible as in PostgreSQL. @xref{Adding functions}. @item Updates that run over multiple tables used to be harder to do in MySQL Server. However, this has been fixed in MySQL Server 4.0.2 with multi-table @code{UPDATE} and in MySQL Server 4.1 with subqueries. In MySQL Server 4.0 one can use multi-table deletes to delete from many tables at the same time. @xref{DELETE}. @end itemize PostgreSQL currently offers the following advantages over MySQL Server: Note that because we know the MySQL road map, we have included in the following table the version when MySQL Server should support this feature. Unfortunately we couldn't do this for previous comparisons, because we don't know the PostgreSQL roadmap. @multitable @columnfractions .30 .30 @item @strong{Feature} @tab @strong{MySQL version} @item Subqueries @tab 4.1 @item Foreign keys @tab 5.0 (3.23 with InnoDB) @item Views @tab 5.0 @item Stored procedures @tab 5.0 @item Triggers @tab 5.0 @item Unions @tab 4.0 @item Full join @tab 4.1 @item Constraints @tab 4.1 or 5.0 @item Cursors @tab 4.1 or 5.0 @item R-trees @tab 4.1 (for MyISAM tables) @item Inherited tables @tab Not planned @item Extensible type system @tab Not planned @end multitable Other reasons someone may consider using PostgreSQL: @itemize @bullet @item Standard usage in PostgreSQL is closer to ANSI SQL in some cases. @item One can speed up PostgreSQL by coding things as stored procedures. @item For geographical data, R-trees make PostgreSQL better than MySQL Server. (note: MySQL version 4.1 has R-trees for MyISAM tables). @item The PostgreSQL optimiser can do some optimisation that the current MySQL optimiser can't do. Most notable is doing joins when you don't have the proper keys in place and doing a join where you are using different keys combined with OR. The MySQL benchmark suite at @uref{http://www.mysql.com/information/benchmarks.html} shows you what kind of constructs you should watch out for when using different databases. @item PostgreSQL has a bigger team of developers that contribute to the server. @end itemize Drawbacks with PostgreSQL compared to MySQL Server: @itemize @bullet @item @code{VACUUM} makes PostgreSQL hard to use in a 24/7 environment. @item Only transactional tables. @item Much slower @code{INSERT}, @code{DELETE}, and @code{UPDATE}. @end itemize For a complete list of drawbacks, you should also examine the first table in this section. @node MySQL-PostgreSQL benchmarks, , MySQL-PostgreSQL features, Compare PostgreSQL @subsubsection Benchmarking MySQL and PostgreSQL @cindex PostgreSQL vs. MySQL, benchmarks The only @code{Open Source} benchmark that we know of that can be used to benchmark MySQL Server and PostgreSQL (and other databases) is our own. It can be found at @uref{http://www.mysql.com/information/benchmarks.html}. We have many times asked the PostgreSQL developers and some PostgreSQL users to help us extend this benchmark to make it the definitive benchmark for databases, but unfortunately we haven't gotten any feedback for this. We, the MySQL developers, have, because of this, spent a lot of hours to get maximum performance from PostgreSQL for the benchmarks, but because we don't know PostgreSQL intimately, we are sure that there are things that we have missed. We have on the benchmark page documented exactly how we did run the benchmark so that it should be easy for anyone to repeat and verify our results. The benchmarks are usually run with and without the @code{--fast} option. When run with @code{--fast} we are trying to use every trick the server can do to get the code to execute as fast as possible. The idea is that the normal run should show how the server would work in a default setup and the @code{--fast} run shows how the server would do if the application developer would use extensions in the server to make his application run faster. When running with PostgreSQL and @code{--fast} we do a @code{VACUUM} after every major table @code{UPDATE} and @code{DROP TABLE} to make the database in perfect shape for the following @code{SELECT}s. The time for @code{VACUUM} is measured separately. When running with PostgreSQL 7.1.1 we could, however, not run with @code{--fast} because during the @code{INSERT} test, the postmaster (the PostgreSQL daemon) died and the database was so corrupted that it was impossible to restart postmaster. After this happened twice, we decided to postpone the @code{--fast} test until the next PostgreSQL release. The details about the machine we run the benchmark on can be found on the benchmark page. Before going to the other benchmarks we know of, we would like to give some background on benchmarks. It's very easy to write a test that shows @strong{any} database to be the best database in the world, by just restricting the test to something the database is very good at and not testing anything that the database is not good at. If one, after doing this, summarises the result as a single figure, things are even easier. This would be like us measuring the speed of MySQL Server compared to PostgreSQL by looking at the summary time of the MySQL benchmarks on our web page. Based on this MySQL Server would be more than 40 times faster than PostgreSQL, something that is, of course, not true. We could make things even worse by just taking the test where PostgreSQL performs worst and claim that MySQL Server is more than 2000 times faster than PostgreSQL. The case is that MySQL does a lot of optimisations that PostgreSQL doesn't do. This is, of course, also true the other way around. An SQL optimiser is a very complex thing, and a company could spend years just making the optimiser faster and faster. When looking at the benchmark results you should look for things that you do in your application and just use these results to decide which database would be best suited for your application. The benchmark results also show things a particular database is not good at and should give you a notion about things to avoid and what you may have to do in other ways. We know of two benchmark tests that claim that PostgreSQL performs better than MySQL Server. These both where multi-user tests, a test that we here at MySQL AB haven't had time to write and include in the benchmark suite, mainly because it's a big task to do this in a manner that is fair to all databases. One is the benchmark paid for by Great Bridge, the company that for 16 months attempted to build a business based on PostgreSQL but now has ceased operations. This is probably the worst benchmark we have ever seen anyone conduct. This was not only tuned to only test what PostgreSQL is absolutely best at, but it was also totally unfair to every other database involved in the test. @strong{Note}: We know that even some of the main PostgreSQL developers did not like the way Great Bridge conducted the benchmark, so we don't blame the PostgreSQL team for the way the benchmark was done. This benchmark has been condemned in a lot of postings and newsgroups, so here we will just briefly repeat some things that were wrong with it. @itemize @bullet @item The tests were run with an expensive commercial tool that makes it impossible for an @code{Open Source} company like us to verify the benchmarks, or even check how the benchmarks were really done. The tool is not even a true benchmark tool, but an application/setup testing tool. To refer to this as a ``standard'' benchmark tool is to stretch the truth a long way. @item Great Bridge admitted that they had optimised the PostgreSQL database (with @code{VACUUM} before the test) and tuned the startup for the tests, something they hadn't done for any of the other databases involved. They say ``This process optimises indexes and frees up disk space a bit. The optimised indexes boost performance by some margin.'' Our benchmarks clearly indicate that the difference in running a lot of selects on a database with and without @code{VACUUM} can easily differ by a factor of 10. @item The test results were also strange. The AS3AP test documentation mentions that the test does ``selections, simple joins, projections, aggregates, one-tuple updates, and bulk updates.'' PostgreSQL is good at doing @code{SELECT}s and @code{JOIN}s (especially after a @code{VACUUM}), but doesn't perform as well on @code{INSERT}s or @code{UPDATE}s. The benchmarks seem to indicate that only @code{SELECT}s were done (or very few updates). This could easily explain the good results for PostgreSQL in this test. The bad results for MySQL will be obvious a bit down in this document. @item They did run the so-called benchmark from a Windows machine against a Linux machine over ODBC, a setup that no normal database user would ever do when running a heavy multi-user application. This tested more the ODBC driver and the Windows protocol used between the clients than the database itself. @item When running the database against Oracle and MS-SQL (Great Bridge has indirectly indicated the databases they used in the test), they didn't use the native protocol but instead ODBC. Anyone that has ever used Oracle knows that all real applications use the native interface instead of ODBC. Doing a test through ODBC and claiming that the results had anything to do with using the database in a real-world situation can't be regarded as fair. They should have done two tests with and without ODBC to provide the right facts (after having gotten experts to tune all involved databases, of course). @item They refer to the TPC-C tests, but they don't mention anywhere that the test they did was not a true TPC-C test and they were not even allowed to call it a TPC-C test. A TPC-C test can only be conducted by the rules approved by the TPC Council (@uref{http://www.tpc.org/}). Great Bridge didn't do that. By doing this they have both violated the TPC trademark and miscredited their own benchmarks. The rules set by the TPC Council are very strict to ensure that no one can produce false results or make unprovable statements. Apparently Great Bridge wasn't interested in doing this. @item After the first test, we contacted Great Bridge and mentioned to them some of the obvious mistakes they had done with MySQL Server: @itemize @minus @item Running with a debug version of our ODBC driver @item Running on a Linux system that wasn't optimised for threads @item Using an old MySQL version when there was a recommended newer one available @item Not starting MySQL Server with the right options for heavy multi-user use (the default installation of MySQL Server is tuned for minimal resource use) @end itemize Great Bridge did run a new test, with our optimised ODBC driver and with better startup options for MySQL Server, but refused to either use our updated glibc library or our standard binary (used by 80% of our users), which was statically linked with a fixed glibc library. According to what we know, Great Bridge did nothing to ensure that the other databases were set up correctly to run well in their test environment. We are sure, however, that they didn't contact Oracle or Microsoft to ask for their advice in this matter. ;) @item The benchmark was paid for by Great Bridge, and they decided to publish only partial, chosen results (instead of publishing it all). @end itemize Tim Perdue, a long-time PostgreSQL fan and a reluctant MySQL user, published a comparison on PHPbuilder (@uref{http://www.phpbuilder.com/columns/tim20001112.php3}). When we became aware of the comparison, we phoned Tim Perdue about this because there were a lot of strange things in his results. For example, he claimed that MySQL Server had a problem with five users in his tests, when we know that there are users with similar machines as his that are using MySQL Server with 2000 simultaneous connections doing 400 queries per second. (In this case the limit was the web bandwidth, not the database.) It sounded like he was using a Linux kernel that either had some problems with many threads, such as kernels before 2.4, which had a problem with many threads on multi-CPU machines. We have documented in this manual how to fix this and Tim should be aware of this problem. The other possible problem could have been an old glibc library and that Tim didn't use a MySQL binary from our site, which is linked with a corrected glibc library, but had compiled a version of his own. In any of these cases, the symptom would have been exactly what Tim had measured. We asked Tim if we could get access to his data so that we could repeat the benchmark and if he could check the MySQL version on the machine to find out what was wrong and he promised to come back to us about this. He has not done that yet. Because of this we can't put any trust in this benchmark either. :( Over time things also change and the preceding benchmarks are not that relevant anymore. MySQL Server now has a couple of different storage engines with different speed/concurrency tradeoffs. @xref{Table types}. It would be interesting to see how the above tests would run with the different transactional table types in MySQL Server. PostgreSQL has, of course, also got new features since the test was made. As these tests are not publicly available there is no way for us to know how the database would perform in the same tests today. Conclusion: The only benchmarks that exist today that anyone can download and run against MySQL Server and PostgreSQL are the MySQL benchmarks. We here at MySQL AB believe that @code{Open Source} databases should be tested with @code{Open Source} tools! This is the only way to ensure that no one does tests that nobody can reproduce and use this to claim that one database is better than another. Without knowing all the facts it's impossible to answer the claims of the tester. The thing we find strange is that every test we have seen about PostgreSQL, that is impossible to reproduce, claims that PostgreSQL is better in most cases while our tests, which anyone can reproduce, clearly show otherwise. With this we don't want to say that PostgreSQL isn't good at many things (it is!) or that it isn't faster than MySQL Server under certain conditions. We would just like to see a fair test where PostgreSQL performs very well, so that we could get some friendly competition going! For more information about our benchmark suite, see @ref{MySQL Benchmarks}. We are working on an even better benchmark suite, including multi-user tests, and a better documentation of what the individual tests really do and how to add more tests to the suite. @node Installing, Tutorial, Introduction, Top @chapter MySQL のインストール @cindex installing, overview @menu * Quick Standard Installation:: Quick Standard Installation of MySQL * General Installation Issues:: General Installation Issues * Installing source:: Installing a MySQL source distribution * Post-installation:: Post-installation setup and testing * Upgrade:: Upgrading/Downgrading MySQL * Operating System Specific Notes:: Operating System Specific Notes * Perl support:: Perl Installation Comments @end menu この章では、どのようにして MySQL を得、インストールするのかをのべます: @itemize @bullet @item MySQL を得ることができるサイトのリスト → @ref{Getting MySQL, , Getting MySQL}. @item どのプラットフォームをサポートしているかは → @ref{Which OS}. Please note that not all supported systems are equally good for running MySQL on them. On some it is much more robust and efficient than others-see @ref{Which OS} for details. @item MySQL のいくつかのバージョンは、バイナリ、ソース両方の配布物があります。 最も新しい開発を見たいという人と、新しいコードをテストして我々を助けたいと いう人のために、現在のソースツリーへのアクセスも公開します。 どのバージョンを使用するのか、どのタイプを使用するかを決めるためには → @ref{Which version}. 迷った時はバイナリディストリビューションを使用してください。 @item バイナリとソースのインストールについては → @ref{Installing binary}, と @ref{Installing source}. それぞれのセットには、あなたが出くわすかもしれない システムに特有の問題のセクションが含まれます。 @item インストール後に行うことの説明は → @ref{Post-installation}. MySQL のインストールにおいて、バイナリまたはソース配布にかかわらず、 これらのプロシージャは適用します。 @end itemize @node Quick Standard Installation, General Installation Issues, Installing, Installing @section Quick Standard Installation of MySQL @c This node name is special @menu * Linux-RPM:: Installing MySQL on Linux * Windows installation:: Installing MySQL on Windows * Mac OS X installation:: Installing MySQL on Mac OS X @end menu @node Linux-RPM, Windows installation, Quick Standard Installation, Quick Standard Installation @subsection Installing MySQL on Linux @cindex RPM file @cindex RPM Package Manager @cindex installing, Linux RPM packages （訳注：もし RedHat 以外の Linux を使用しており、.rpm を、自分が使用している パッケージ管理システムの管理下におきたい場合、 @strong{alien : http://kitenet.net/programs/alien/} というツールを 使用します。これは RPM(Debian, Slackware) を自分が使用しているパッケージの形式に変換してくれます。） RPM を使用して MySQL をインストールすることを推奨します。 MySQL RPM は SuSE Linux 7.3 で作成していますが、 他の @code{rpm} と @code{glibc} をサポートしている Linux でも動作するでしょう。 RPM file での問題, 例えば, ``@code{Sorry, the host 'xxxx' could not be looked up}'' に遭遇した場合には → @ref{Binary notes-Linux}. 以下が使用するであろう RPM files です: @itemize @bullet @item @code{MySQL-server-VERSION.i386.rpm} MySQL サーバー。 ただ単に他のマシン上で走っている MySQL サーバーに接続するだけなら、 これは不要でしょう。 Please note, that this package was called @code{MySQL-VERSION.i386.rpm} before MySQL 4.0.10. @item @code{MySQL-client-VERSION.i386.rpm} MySQL クライアント標準プログラム。 このパッケージはほとんどの場合インストールすることになるでしょう。 @item @code{MySQL-bench-VERSION.i386.rpm} Tests and benchmarks. Requires Perl and msql-mysql-modules RPMs. @item @code{MySQL-devel-VERSION.i386.rpm} 他の MySQL クライアント(perlモジュールのような)をコンパイルするのに必要な ライブラリーとインクルードファイルを含みます。 @item @code{MySQL-shared-VERSION.i386.rpm} This package contains the shared libraries (@code{libmysqlclient.so*}) which certain languages and applications need to dynamically load and use MySQL. @item @code{MySQL-embedded-VERSION.i386.rpm} The embedded MySQL server library (MySQL 4.x and onwards only). @item @code{MySQL-VERSION.src.rpm} 上記全てのソース。これは他のアーキテクチャ用に RPM を作成する場合にのみ必要でしょう。 (例えば Alpha や SPARC). @end itemize To see all files in an RPM package, run: @example shell> rpm -qpl MySQL-VERSION.i386.rpm @end example インストールの最小の方法： @example shell> rpm -i MySQL-server-VERSION.i386.rpm MySQL-client-VERSION.i386.rpm @end example クライアントパッケージだけをインストール： @example shell> rpm -i MySQL-client-VERSION.i386.rpm @end example RPM はデータを @file{/var/lib/mysql} に保存します。 RPM は起動時にサーバーを立ちあげるように、@file{/etc/init.d/} に登録します。 (以前にインストールがされていて、前にインストールされた MySQL 起 動ファイルを何か変更している場合、それをコピーしておいた方がいいでしょう。 そうすればその変更を失うことはありません。) If you want to install the MySQL RPM on older Linux distributions that do not support init scripts in @file{/etc/init.d} (directly or via a symlink), you should create a symbolic link pointing to the old location before installing the RPM: @example shell> cd /etc ; ln -s rc.d/init.d . @end example However, all current major Linux distributions should already support this new directory layout as it is required for LSB (Linux Standard Base) compliance. RPM ファイルのインストール後は、@code{mysqld} デーモンが実行されていて、 MySQL の使用を開始することができます。 @xref{Post-installation}. うまくいかない場合、バイナリインストールの章でさらに情報を探すことができま す。 @xref{Installing binary}. @node Windows installation, Mac OS X installation, Linux-RPM, Quick Standard Installation @subsection Windows への MySQL のインストール Windows用の MySQLサーバ には，２つの配布形態があります。: @enumerate @item バイナリ配布は，セットアッププログラムが含まれ，必要な全てのインストール作業を行い， あなたは直ぐにサーバをスタートさせることができます。 @item The source distribution contains all the code and support files for building the executables using the VC++ 6.0 compiler. @xref{Windows source build}. @end enumerate 大雑把な言い方をすると，バイナリ配布を使用する方がいいでしょう。 You will need the following: @itemize @bullet @item A 32-bit Windows Operating System such as 9x, Me, NT, 2000, or XP. The NT family (NT, Windows 2000 and XP) permits running the MySQL server as a service. @xref{NT start}. If you want to use tables bigger than 4G, you should install MySQL on an NTFS or newer filesystem. Don't forget to use @code{MAX_ROWS} and @code{AVG_ROW_LENGTH} when you create the table. @xref{CREATE TABLE}. @item TCP/IP protocol support. @item A copy of the MySQL binary or distribution for Windows, which can be downloaded from @uref{http://www.mysql.com/downloads/}. Note: The distribution files are supplied with a zipped format and we recommend the use of an adequate FTP client with resume feature to avoid corruption of files during the download process. @item A @code{ZIP} program to unpack the distribution file. @item Enough space on the hard drive to unpack, install, and create the databases in accorandance with your requirements. @item If you plan to connect to the MySQL server via @code{ODBC}, you will also need the @code{MyODBC} driver. @xref{ODBC}. @end itemize @menu * Windows binary installation:: Installing the Binaries * Windows prepare environment:: Preparing the Windows MySQL Environment * Windows server first start:: Starting the Server for the First Time @end menu @node Windows binary installation, Windows prepare environment, Windows installation, Windows installation @subsubsection Installing the Binaries @enumerate @item If you are working on an NT/2000/XP server, logon as a user with administrator privileges. @item If you are doing an upgrade of an earlier MySQL installation, it is necessary to stop the server. If you are running the server as a service, use: @example C:\> NET STOP MySQL @end example Otherwise, use: @example C:\mysql\bin> mysqladmin -u root shutdown @end example @item On NT/2000/XP machines, if you want to change the server executable (e.g., -max or -nt), it is also necessary to remove the service: @example C:\mysql\bin> mysqld-max-nt --remove @end example @item Unzip the distribution file to a temporary directory. @item Run the @file{setup.exe} file to begin the installation process. If you want to install into another directory than the default @file{c:\mysql}, use the @code{Browse} button to specify your preferred directory. @item Finish the install process. @end enumerate @node Windows prepare environment, Windows server first start, Windows binary installation, Windows installation @subsubsection Preparing the Windows MySQL Environment Starting with MySQL 3.23.38, the Windows distribution includes both the normal and the MySQL-Max server binaries. Here is a list of the different MySQL servers you can use: @multitable @columnfractions .20 .80 @item @strong{Binary} @tab @strong{Description} @item @code{mysqld} @tab Compiled with full debugging and automatic memory allocation checking, symbolic links, InnoDB, and BDB tables. @item @code{mysqld-opt} @tab Optimised binary with no support for transactional tables. @item @code{mysqld-nt} @tab Optimised binary for NT/2000/XP with support for named pipes. You can run this version on Windows 9x/Me, but in this case no named pipes are created and you must have TCP/IP installed. @item @code{mysqld-max} @tab Optimised binary with support for symbolic links, InnoDB and BDB tables. @item @code{mysqld-max-nt} @tab Like @code{mysqld-max}, but compiled with support for named pipes. @end multitable Starting from 3.23.50, named pipes are only enabled if one starts mysqld with @code{--enable-named-pipe}. All of the preceding binaries are optimised for the Pentium Pro processor but should work on any Intel processor >= i386. You will need to use an option file to specify your MySQL configuration under the following circumstances: @itemize @bullet @item The installation or data directories are different from the default locations (@file{c:\mysql} and @file{c:\mysql\data}). @item You want to use one of these servers: @itemize @bullet @item mysqld.exe @item mysqld-max.exe @item mysqld-max-nt.exe @end itemize @item You need to tune the server settings. @end itemize Normally you can use the @code{WinMySQLAdmin} tool to edit the option file @code{my.ini}. In this case you don't have to worry about the following section. There are two option files with the same function: @file{my.cnf} and @file{my.ini}. However, to avoid confusion, it's best if you use only of one them. Both files are plain text. The @file{my.cnf} file, if used, should be created in the root directory of the C drive. The @file{my.ini} file, if used, should be created in the Windows system directory. (This directory is typically something like @file{C:\WINDOWS} or @file{C:\WINNT}. You can determine its exact location from the value of the @code{windir} environment variable.) MySQL looks first for the @code{my.ini} file, then for the @file{my.cnf} file. If your PC uses a boot loader where the C drive isn't the boot drive, your only option is to use the @file{my.ini} file. Also note that if you use the @code{WinMySQLAdmin} tool, it uses only the @file{my.ini} file. The @file{\mysql\bin} directory contains a help file with instructions for using this tool. Using @code{notepad.exe}, create the option file and edit the @code{[mysqld]} section to specify values for the @code{basedir} and @code{datadir} parameters: @example [mysqld] # set basedir to installation path, e.g., c:/mysql basedir=the_install_path # set datadir to location of data directory, # e.g., c:/mysql/data or d:/mydata/data datadir=the_data_path @end example Note that Windows pathnames should be specified in option files using forward slashes rather than backslashes. If you do use backslashes, you must double them. If you would like to use a data directory different from the default of @file{c:\mysql\data}, you must copy the entire contents of the @file{c:\mysql\data} directory to the new location. If you want to use the @code{InnoDB} transactional tables, you need to manually create two new directories to hold the InnoDB data and log files@-e.g., @file{c:\ibdata} and @file{c:\iblogs}. You will also need to add some extra lines to the option file. @xref{InnoDB start}. If you don't want to use @code{InnoDB} tables, add the @code{skip-innodb} option to the option file. Now you are ready to test starting the server. @node Windows server first start, , Windows prepare environment, Windows installation @subsubsection Starting the Server for the First Time Testing from a DOS command prompt is the best thing to do because the server displays status messages that appear in the DOS window. If something is wrong with your configuration, these messages will make it easier for you to identify and fix any problems. Make sure you are in the directory where the server is located, then enter this command: @example C:\mysql\bin> mysqld-max --standalone @end example You should see the following messages as the server starts up: @example InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: creating foreign key constraint system tables InnoDB: foreign key constraint system tables created 011024 10:58:25 InnoDB: Started @end example For further information about running MySQL on Windows, see @ref{Windows}. @node Mac OS X installation, , Windows installation, Quick Standard Installation @subsection Installing MySQL on Mac OS X @cindex Mac OS X, installation @cindex installing, Mac OS X PKG packages Beginning with MySQL 4.0.11, you can install MySQL on Mac OS X 10.2 ("Jaguar") using a Mac OS X @code{PKG} binary package instead of the binary tarball distribution. Please note that older versions of Mac OS X (e.g. 10.1.x) are not supported by this package! The package is located inside a disk image (@code{.dmg}) file, that you first need to mount by double-clicking its icon in the Finder. It should then mount the image and display its contents. @strong{NOTE}: Before proceeding with the installation, please make sure that no other MySQL server is running! Please shut down all running MySQL instances before continuing by either using the MySQL Manager Application (on Mac OS X Server) or via @code{mysqladmin shutdown} on the command line. To actually install the MySQL PKG, double click on the package icon. This will launch the Mac OS Package Installer, which will guide you through the installation of MySQL. The Mac OS X PKG of MySQL will install itself into @file{/usr/local/mysql-} and will also install a symbolic link @file{/usr/local/mysql}, pointing to the new location. If a directory named @file{/usr/local/mysql} already exists, it will be renamed to @file{/usr/local/mysql.bak} first. Additionally, it will install the mysql grant tables by executing @code{mysql_install_db} after the installation. The installation layout is similar to the one of the binary distribution, all MySQL binaries are located in directory @file{/usr/local/mysql/bin}. The MySQL socket will be put into @file{/etc/mysql.sock} by default. @xref{Installation layouts}. It requires a user account named @code{mysql} (which should exist by default on Mac OS X 10.2 and up). If you are running Mac OS X Server, you already have a version of MySQL installed: @itemize @item Mac OS X Server 10.2-10.2.2 come with MySQL 3.23.51 installed @item Mac OS X Server 10.2.3 and 10.2.4 ship with MySQL 3.23.53 @end itemize This manual section covers the installation of the official MySQL Mac OS X PKG only. Make sure to read Apple's help about installing MySQL (Run the "Help View" application, select "Mac OS X Server" help, and do a search for "MySQL" and read the item entitled "Installing MySQL"). Especially note, that the pre-installed version of MySQL on Mac OS X Server is being started with the command @code{safe_mysqld} instead of @code{mysqld_safe}! If you previously used Marc Liyanage's MySQL packages for Mac OS X from @uref{http://www.entropy.ch}, you can simply follow the update instructions for packages using the binary installation layout as given on his pages. If you are upgrading from Marc's version or from the Mac OS X Server version of MySQL to the official MySQL PKG, you also need to convert the existing MySQL privilege tables. @xref{Upgrading-from-3.23}. After the installation, you can start up MySQL by running the following commands in a terminal window. Please note that you need to have administrator privileges to perform this task! @example shell> cd /usr/local/mysql shell> sudo ./bin/mysqld_safe (Enter your password) (Press CTRL+Z) shell> bg (Press CTRL+D to exit the shell) @end example You should now be able to connect to the MySQL server, e.g. by running @file{/usr/local/mysql/bin/mysql}. To enable the automatic startup of MySQL on bootup, you can download Marc Liyanage's MySQL StartupItem from the following location: @uref{http://www2.entropy.ch/download/mysql-startupitem.pkg.tar.gz} We plan to add a StartupItem to the official MySQL PKG in the near future. Please note that installing a new MySQL PKG does not remove the directory of an older installation - unfortunately the Mac OS X Installer does not yet offer the functionality required to properly upgrade previously installed packages. After you have copied over the MySQL database files from the previous version and have successfully started the new version, you should consider removing the old installation files to save up disk space. Additionally, you should also remove older versions of the Package Receipt directories located in @file{/Library/Receipts/mysql-.pkg}. @node General Installation Issues, Installing source, Quick Standard Installation, Installing @section General Installation Issues @c @node Methods of Installation, , , @c @subsection Methods of Installation @c FIX: this needs to be written? @menu * Getting MySQL:: How to Get MySQL * Verifying Package Integrity:: Verifying Package Integrity Using @code{MD5 Checksums} or @code{GnuPG} * Which OS:: Operating Systems Supported by MySQL * Which version:: Which MySQL Version to Use * Installation layouts:: Installation Layouts * Many versions:: How and When Updates Are Released * MySQL binaries:: MySQL Binaries Compiled by MySQL AB * Installing binary:: Installing a MySQL Binary Distribution @end menu @node Getting MySQL, Verifying Package Integrity, General Installation Issues, General Installation Issues @subsection MySQL を得る方法 @cindex downloading @cindex MySQL version @cindex version, latest @cindex getting MySQL @cindex mirror sites @cindex URLS for downloading MySQL 現在のバージョンとダウンロードの指示についての情報は MySQL ウェブページ (@uref{http://www.mysql.com/}) をチェックしてください。 主なダウンロードミラーはここにあります: @uref{http://mirrors.sunsite.dk/mysql/}. For a complete upto-date list of MySQL web/download mirrors, see @uref{http://www.mysql.com/downloads/mirrors.html}. There you will also find information about becoming a MySQL mirror site and how to report a bad or out-of-date mirror. @node Verifying Package Integrity, Which OS, Getting MySQL, General Installation Issues @subsection Verifying Package Integrity Using @code{MD5 Checksums} or @code{GnuPG} After you have downloaded the MySQL package that suits your needs and before you attempt to install it, you should make sure it is intact and has not been tampered with. MySQL AB offers two means of integrity checking: @code{MD5 checksums} and cryptographic signatures using @code{GnuPG}, the @code{GNU Privacy Guard}. @subheading Verifying the @code{MD5 Checksum} After you have downloaded the package, you should check, if the MD5 checksum matches the one provided on the MySQL download pages. Each package has an individual checksum, that you can verify with the following command: @example shell> md5sum @end example Note, that not all operating systems support the @code{md5sum} command - on some it is simply called @code{md5}, others do not ship it at all. On Linux, it is part of the @code{GNU Text Utilities} package, which is available for a wide range of platforms. You can download the source code from @uref{http://www.gnu.org/software/textutils/} as well. If you have @code{OpenSSL} installed, you can also use the command @code{openssl md5 } instead. A DOS/Windows implementation of the @code{md5} command is available from @uref{http://www.fourmilab.ch/md5/}. Example: @example shell> md5sum mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz 155836a7ed8c93aee6728a827a6aa153 mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz @end example You should check, if the resulting checksum matches the one printed on the download page right below the respective package. Most mirror sites also offer a file named @file{MD5SUMS}, which also includes the MD5 checksums for all files included in the @file{Downloads} directory. Please note however that it's very easy to modify this file and it's not a very reliable method! If in doubt, you should consult different mirror sites and compare the results. @subheading Signature Checking Using @code{GnuPG} A more reliable method of verifying the integrity of a package is using cryptographic signatures. MySQL AB uses the @code{GNU Privacy Guard} (@code{GnuPG}), an @code{Open Source} alternative to the very well-known @code{Pretty Good Privacy} (@code{PGP}) by Phil Zimmermann. See @uref{http://www.gnupg.org/} and @uref{http://www.openpgp.org/} for more information about @code{OpenPGP}/@code{GnuPG} and how to obtain and install @code{GnuPG} on your system. Most Linux distributions already ship with @code{GnuPG} installed by default. Beginning with MySQL 4.0.10 (February 2003), MySQL AB has started signing their downloadable packages with @code{GnuPG}. Cryptographic signatures are a much more reliable method of verifying the integrity and authenticity of a file. To verify the signature for a specific package, you first need to obtain a copy of MySQL AB's public GPG build key @email{build@@mysql.com}. You can either cut and paste it directly from here, or obtain it from @uref{http://www.keyserver.net/}. @example Key ID: pub 1024D/5072E1F5 2003-02-03 MySQL Package signing key (www.mysql.com) Fingerprint: A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 E1F5 Public Key (ASCII-armored): -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBD4+owwRBAC14GIfUfCyEDSIePvEW3SAFUdJBtoQHH/nJKZyQT7h9bPlUWC3 RODjQReyCITRrdwyrKUGku2FmeVGwn2u2WmDMNABLnpprWPkBdCk96+OmSLN9brZ fw2vOUgCmYv2hW0hyDHuvYlQA/BThQoADgj8AW6/0Lo7V1W9/8VuHP0gQwCgvzV3 BqOxRznNCRCRxAuAuVztHRcEAJooQK1+iSiunZMYD1WufeXfshc57S/+yeJkegNW hxwR9pRWVArNYJdDRT+rf2RUe3vpquKNQU/hnEIUHJRQqYHo8gTxvxXNQc7fJYLV K2HtkrPbP72vwsEKMYhhr0eKCbtLGfls9krjJ6sBgACyP/Vb7hiPwxh6rDZ7ITnE kYpXBACmWpP8NJTkamEnPCia2ZoOHODANwpUkP43I7jsDmgtobZX9qnrAXw+uNDI QJEXM6FSbi0LLtZciNlYsafwAPEOMDKpMqAK6IyisNtPvaLd8lH0bPAnWqcyefep rv0sxxqUEMcM3o7wwgfN83POkDasDbs3pjwPhxvhz6//62zQJ7Q7TXlTUUwgUGFj a2FnZSBzaWduaW5nIGtleSAod3d3Lm15c3FsLmNvbSkgPGJ1aWxkQG15c3FsLmNv bT6IXQQTEQIAHQUCPj6jDAUJCWYBgAULBwoDBAMVAwIDFgIBAheAAAoJEIxxjTtQ cuH1cY4AnilUwTXn8MatQOiG0a/bPxrvK/gCAJ4oinSNZRYTnblChwFaazt7PF3q zIhMBBMRAgAMBQI+PqPRBYMJZgC7AAoJEElQ4SqycpHyJOEAn1mxHijft00bKXvu cSo/pECUmppiAJ41M9MRVj5VcdH/KN/KjRtW6tHFPYhMBBMRAgAMBQI+QoIDBYMJ YiKJAAoJELb1zU3GuiQ/lpEAoIhpp6BozKI8p6eaabzF5MlJH58pAKCu/ROofK8J Eg2aLos+5zEYrB/LsrkCDQQ+PqMdEAgA7+GJfxbMdY4wslPnjH9rF4N2qfWsEN/l xaZoJYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47gCvtgb6O1JHffOo2HfLmRDRi Rjd1DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0Vhp3aFfWC4Ujfs3LU+hkAWzE 7zaD5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1BzELqX1DY7LwoPEb/O9Rkbf4fm Le11EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfozBu74F47D8Ilbf5vSYHbuE5p /1oIDznkg/p8kW+3FxuWrycciqFTcNz215yyX39LXFnlLzKUb/F5GwADBQf+Lwqq a8CGrRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR1BeQauyPZbPDsDD9MZ1ZaSaf anFvwFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55VjnSd1aQ9eQnUcXiL4cnBGoTbOW I39EcyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQWg54tuUo0Ec8bsM8b3Ev42Lmu QT5NdKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT27jWjJlMiJc+IWJ0mghkKHt92 6s/ymfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuwqp2H139pXGEkg0n6KdUOetdZ Whe70YGNPw1yjWJT1IhMBBgRAgAMBQI+PqMdBQkJZgGAAAoJEIxxjTtQcuH17p4A n3r1QpVC9yhnW2cSAjq+kr72GX0eAJ4295kl6NxYEuFApmr1+0uUq/SlsQ== =YJkx -----END PGP PUBLIC KEY BLOCK----- @end example You can import this key into your public @code{GPG} keyring by using @code{gpg --import}. See the @code{GPG} documentation for more info on how to work with public keys. After you have downloaded and imported the public build key, now download your desired MySQL package and the corresponding signature, which is also available from the download page. The signature has the file name extension @file{.asc}. For example, the signature for @file{mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz} would be @file{mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz.asc}. Make sure that both files are stored in the same directory and then run the following command to verify the signature for this file: @example shell> gpg --verify .asc Example: shell> gpg --verify mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz.asc gpg: Warning: using insecure memory! gpg: Signature made Mon 03 Feb 2003 08:50:39 PM MET using DSA key ID 5072E1F5 gpg: Good signature from "MySQL Package signing key (www.mysql.com) " @end example The "Good signature" message indicates that everything is all right. For @code{RPM} packages, there is no separate signature - @code{RPM} packages actually have a built-in @code{GPG} signature and @code{MD5 checksum}. You can verify them by running the following command: @example shell> rpm --checksig .rpm Example: shell> rpm --checksig MySQL-server-4.0.10-0.i386.rpm MySQL-server-4.0.10-0.i386.rpm: md5 gpg OK @end example @strong{Note:} If you are using RPM 4.1 and it complains about @code{(GPG) NOT OK (MISSING KEYS: GPG#5072e1f5)} (even though you have imported it into your GPG public keyring), you need to import the key into the RPM keyring first. RPM 4.1 does not use your GPG keyring (and GPG itself) anymore, but rather maintains its own keyring (because it's a system wide application and the GPG public keyring is user-specific file). To import the MySQL public key into the RPM keyring, please use the following command: @example shell> rpm --import Example: shell> rpm --import mysql_pubkey.asc @end example In case you notice that the @code{MD5 checksum} or @code{GPG} signatures do not match, first try to download the respective package one more time, maybe from another mirror site. If you repeatedly can not successfully verify the integrity of the package, please notify us about such incidents including the full package name and the download site you have been using at @email{webmaster@@mysql.com} or @email{build@@mysql.com}. @node Which OS, Which version, Verifying Package Integrity, General Installation Issues @subsection MySQL がサポートする OS @cindex operating systems, supported @cindex native thread support @cindex thread support @cindex process support @cindex support, for operating systems 我々は GNU Autoconf を使用していますので、MySQL は POSIX スレッ ドと C++ コンパイラが動作する全ての新しいシステムに移植可能です。(クライ アントコードのコンパイルだけは C++ を必要としますが、スレッドは必要ではありません。) 我々は自身のソフトウェアを、最初に Sun Solaris (現在は 2.5 〜 2.7) 上と SuSE Linux Version 7.x で使用し開発します。 多くの OS では、ネイティブスレッドは最新バージョ ンだけで動作することに注意してください。 MySQL は次の OS/スレッドパッケージの組み合わせで、コンパイルの 成功が報告されています。 @itemize @bullet @item AIX 4.x, 5.x with native threads. @xref{IBM-AIX}. @item Amiga. @item BSDI 2.x with the MIT-pthreads package. @xref{BSDI}. @item BSDI 3.0, 3.1 and 4.x with native threads. @xref{BSDI}. @item DEC Unix 4.x with native threads. @xref{Alpha-DEC-UNIX}. @item FreeBSD 2.x with the MIT-pthreads package. @xref{FreeBSD}. @item FreeBSD 3.x and 4.x with native threads. @xref{FreeBSD}. @item HP-UX 10.20 with the DCE threads or the MIT-pthreads package. @xref{HP-UX 10.20}. @item HP-UX 11.x with the native threads. @xref{HP-UX 11.x}. @item Linux 2.0+ with LinuxThreads 0.7.1+ or @code{glibc} 2.0.7+. @xref{Linux}. @item Mac OS X. @xref{Mac OS X}. @item NetBSD 1.3/1.4 Intel and NetBSD 1.3 Alpha (Requires GNU make). @xref{NetBSD}. @item OpenBSD > 2.5 with native threads. OpenBSD < 2.5 with the MIT-pthreads package. @xref{OpenBSD}. @item OS/2 Warp 3, FixPack 29 and OS/2 Warp 4, FixPack 4. @xref{OS/2}. @item SGI Irix 6.x with native threads. @xref{SGI-Irix}. @item Solaris 2.5 and above with native threads on SPARC and x86. @xref{Solaris}. @item SunOS 4.x with the MIT-pthreads package. @xref{Solaris}. @item Caldera (SCO) OpenServer with a recent port of the FSU Pthreads package. @xref{Caldera}. @item Caldera (SCO) UnixWare 7.0.1. @xref{Caldera Unixware}. @item Tru64 Unix @item Windows 9x, Me, NT, 2000 and XP. @xref{Windows}. @end itemize 全てのプラットフォームが MySQL Server をちゃんと動作させるものではありません。 我々は以下のような評価基準に基づいて重要な要件を任せるに足るプラットフォームで あるかを判断しています。： @itemize @bullet @item スレッドライブラリーの安定性。 プラットフォームが世間的にとてもよい評価を受けそれ以外が完全に動いたとしても、 MySQL が使用するスレッドライブラリーの動作が不安定ならば MySQL は安定して動作しないでしょう。 @item マルチプロセッサシステム上での @strong{SMP} の優位性を引き出すための カーネルやスレッドライブラリの能力。 言い換えると、プロセスがスレッドを生成するときに、元のプロセスが動いていた CPU と異なる CPU 上でスレッドが動作することが可能であるべきです。 @item コンテキストスイッチングの多用を避け、頻繁なセマフォの取り合いによって 排他制御を行う場合のカーネル又はスレッドライブラリーのスレッド実行能力。 言い換えれば、CPUの切り替えに用いられる@code{pthread_mutex_lock()}の実装に 不安がある場合です。この場合は MySQL の実行をはなはだしく阻害します。 このことを考慮せずにいるとCPUを増設するほど MySQL の実行が遅くなる 事象を生じるでしょう。 @item 一般ファイルシステムの安定性とパフォーマンス @item テーブルが大きい場合、大規模ファイルを完全に、そして効率よく扱うためのファ イルシステムの能力。 @item 使用プラットフォームに対する MySQL AB の経験。 使用しているプラットフォームについてよく知っていればプラットフォームに依存する 部分での最適化や改良をコンパイル時に行うことができます。 それから、MySQL の環境設定についてアドバイスも行えます。 @item 我々が内部的に行なう、コンフィグレーションと同様のテストのすべて。 @item The number of users that have successfully run MySQL on that platform in similar configurations. If this number is high, the chances of hitting some platform-specific surprises are much smaller. @end itemize Based on the preceding criteria, the best platforms for running MySQL at this point are x86 with SuSE Linux 7.1, 2.4 kernel, and ReiserFS (or any similar Linux distribution) and SPARC with Solaris 2.7 or 2.8. FreeBSD comes third, but we really hope it will join the top club once the thread library is improved. We also hope that at some point we will be able to include all other platforms on which MySQL compiles, runs okay, but not quite with the same level of stability and performance, into the top category. This will require some effort on our part in cooperation with the developers of the OS/library components MySQL depends upon. If you are interested in making one of those components better, are in a position to influence their development, and need more detailed instructions on what MySQL needs to run better, send an e-mail to @email{internals@@lists.mysql.com}. Please note that the preceding comparison is not to say that one OS is better or worse than the other in general. We are talking about choosing a particular OS for a dedicated purpose@-running MySQL, and compare platforms in that regard only. With this in mind, the result of this comparison would be different if we included more issues into it. And in some cases, the reason one OS is better than the other could simply be that we have put forth more effort into testing on and optimising for that particular platform. We are just stating our observations to help you decide on which platform to use MySQL on in your setup. @node Which version, Installation layouts, Which OS, General Installation Issues @subsection 使用すべき MySQL のバージョン @cindex MySQL binary distribution @cindex MySQL source distribution @cindex release numbers @cindex version, choosing @cindex choosing, a MySQL version make を行う前に決める事は、あなたが最新の開発リリースを使用するのか、 または最新の安定リリースを使用するのかです： @itemize @bullet @item 通常、あなたが最初に MySQL を使い始める場合、またはバイナリ配布 がない他のシステムに MySQL を移植しようとする場合、 我々は安定リリース (現在は バージョン 3.23) の選択を 勧めます。注意: すべての MySQL リリースはそれぞれのリリー スの前に MySQL ベンチマークと広範囲なテストスイートでチェックされ ます。 @item そうでなくて、古いシステムで実行していてアップグレードしたいけれども、 開発版は試したくない場合は、あなたが使用している物と同じブランチ中の 最新のもの(あなたが使用している物より新しいバージョンの物)に アップグレードすべきです。 このバージョンでは、致命的なバグだけを修正し、 比較的安全で小さな変更を行っています。 @end itemize make 前の２番目の決定事項は、ソースディストリビューションとバイナリディ ストリビューションのどちらを使用するかです。多くの場合、バイナリがプラッ トフォーム用に存在していれば、おそらくバイナリディストリビューションを使 用すべきです。通常、それはソースディストリビューションよりも簡単にインス トールできます。 次のケースでは、おそらくソースインストールの方が良いでしょう: @itemize @bullet @item MySQL をどこか明示的な場所にインストールしたい場合(標準バイナリ ディストリビューションは、どこの場所でも ``実行準備'' ができていますが、もっ と柔軟にすることもできます)。 @item 異なるユーザの要求を満たすため、我々は２つのバイナリバージョンを提供してい ます; ひとつは、トランザクションテーブル処理なしでコンパイルされたもので、 もう一つは、トランザクション安全なテーブルのような、もっとも重要な拡張され たオプションで configure されたものです。両方のバージョンとも、同じソース ディストリビューションからコンパイルされます。すべてのネイティブ @code{MySQL} クライアントは両方の MySQL バージョンに接続できます。 拡張 MySQL バイナリディストリビューションは @code{-max} 接尾語が つけられていて、@code{mysqld-max} と同じオプションで configure されていま す。@xref{mysqld-max, , @code{mysqld-max}}. MySQL-Max RPM を使用したい場合は、最初に標準 MySQL RPM をイ ンストールすべきです。 @item @code{mysqld} を、標準バイナリディストリビューションには無いいくつかの拡 張機能付きで configure したい場合。使用できる代表的な拡張オプションは次 の通りです: @itemize @bullet @item @code{--with-innodb} @item @code{--with-berkeley-db} @item @code{--with-raid} @item @code{--with-libwrap} @item @code{--with-named-z-lib (This is done for some of the binaries)} @item @code{--with-debug[=full]} @end itemize @item デフォルトのバイナリディストリビューションは通常すべての文字セットをサポー トするようにコンパイルされていて、同じプロセッサファミリの多種のプロセッ サ上で動作します。 より速い MySQL サーバを得たい場合、必要な文字セットだけをサポー トするように再コンパイルでき、より良いコンパイラ(@code{pgcc}のような)や、あなた のプロセッサ用により最適化されたコンパイラオプションを使用できます。 @item バグを発見して MySQL 開発チームにそれを報告する場合、バグを修正 するためにソースディストリビューションに適用する必要のあるパッチが、おそ らく得られるでしょう。 @item MySQL を作る C と C++ コードを読みたい(そして/または変更したい) 場合はソース配布を入手するべきです。ソースコードはいつでも究極のマニュア ルです。ソース配布はバイナリ配布よりも多くのテストと例も含んでいます。 @end itemize @cindex naming, releases of MySQL @cindex releases, naming scheme MySQL の命名法では、リリース番号は3つの数値とサフィックスからな ります。例えば、@code{mysql-3.21.17-beta} のようなリリース名は次のように 解釈されます: @itemize @bullet @item 最初の数値(@code{3})はファイル形式を表します。全てのバージョン 3 リリー スは同じファイルフォーマットを持ちます。 @item 2番目の数値(@code{21})はリリースレベルです。通常は二つから選択します。一 つはリリース/安定ブランチで(現在は @code{23})、もう一つは開発ブランチです(現在は @code{4.0})。 通常は両方とも安定ですが、開発バージョンはきまぐれで、ドキュメントがなく、いくつかのシ ステムではコンパイルに失敗します。 @item 3番目の数値(@code{17})はリリースレベル内のバージョン番号です。これは新し い配布の度に増加します。普通はあなたの選択したリリースレベルの最新バージョ ンを求めます。 @item サフィックス(@code{beta})はリリースの安定レベルを表します: @itemize @minus @item @code{alpha} は、100% テストされていないいくつかの新しい大きなコードセク ションが存在することを示し、知られているバグは News 節に記述されています (通常はありません)。@xref{News}. 多くの alpha リリースには新しいコマ ンドと拡張もあります。 大きなコード変更を含む開発中のものは、alpha リリース上に現れます。しかし 全てリリース前にテストされます。それぞれの MySQL リリースには既知 のバグはありません。 @item @code{beta} は全ての新しいコードがテストされたことを意味します。大きな新 しいものは追加されません。知られているバグはありません。 alpha バージョンで、少なくとも一カ月間、致命的なバグが報告されなくて、古 いコマンドをより信頼できなくするような新しい機能を追加する計画がない時に、 alpha から beta にバージョンが変更されます。 @item @code{gamma} は beta がしばらくして、正しく動くように見えるものです。 小さな修正だけが追加されます。 これは多くの他の会社がリリースと呼ぶものです。 @item サフィックスがない場合は、多くの異なる場所で、プラットフォーム固有のバグ を除いてバグレポートなしでそのバージョンがしばらくの間動作していたことを 意味します。 致命的なバグ修正だけがリリースに適用されます。 これは我々が stable リリースと呼ぶものです。 @end itemize @end itemize MySQL の全てのバージョンは、比較的安全に使用できることを確かめ るため、我々は標準テストとベンチマークを通して確認しています。標準テス トは以前に見つかった全てのバグをチェックするように拡張されるため、テスト スイートはより良く保持されます。 @cindex releases, testing @cindex testing, of MySQL releases 全てのリリースは少なくても次のテストがされていることに注意してください: @table @asis @item 内部テストスイート これは顧客のための製品システムの一部です。多くのテーブルと何百というメガ バイトのデータを持っています。 @item MySQL ベンチマークスイート これは一般的な範囲のクエリを実行します。これは、最適化の最新バッチが実際 にコードをより速く作れるかどうかを確認するテストでもあります。 @xref{MySQL Benchmarks}. @item @code{crash-me} テスト これは、データベースがサポートしている機能と、その許容量と制限を決定しよ うとします。 @xref{MySQL Benchmarks}. @end table 他のテストは我々の内部製品環境で最新の MySQL バージョンを我々が 少なくとも1つのマシンで使用することです。我々は動作のため 100ギガバイト 以上のデータを持ちます。 @node Installation layouts, Many versions, Which version, General Installation Issues @subsection インストールレイアウト @cindex installation layouts @cindex layout of installation @cindex directory structure, default @cindex default installation location この節では、バイナリとソース配布のインストールで生成されるディレクトリの デフォルトのレイアウトを説明します。 バイナリ配布はアンパックすることによりインストールされ、インストール場所 はあなたが選択した場所(通常 @file{/usr/local/mysql})の中の次のディレクト リを選択し生成します: @multitable @columnfractions .15 .45 @item @strong{ディレクトリ} @tab @strong{ディレクトリの内容} @item @file{bin} @tab クライアントプログラム, @code{mysqld} サーバ @item @file{data} @tab ログファイル, データベース @item @file{include} @tab インクルード(ヘッダ)ファイル @item @file{lib} @tab ライブラリ @item @file{scripts} @tab @code{mysql_install_db} @item @file{share/mysql} @tab エラーメッセージファイル @item @file{sql-bench} @tab ベンチマーク @end multitable ソース配布は configure しコンパイルした後にインストールされます。デフォ ルトではインストールステップは @file{/usr/local} 配下のファイルを次のサ ブディレクトリにインストールします: @multitable @columnfractions .15 .45 @item @strong{ディレクトリ} @tab @strong{ディレクトリの内容} @item @file{bin} @tab クライアントプログラムとスクリプト @item @file{include/mysql} @tab インクルードファイル @item @file{info} @tab Info 形式のドキュメント @item @file{lib/mysql} @tab ライブラリ @item @file{libexec} @tab @code{mysqld} サーバ @item @file{share/mysql} @tab エラーメッセージファイル @item @file{sql-bench} @tab ベンチマークと @code{crash-me} テスト @item @file{var} @tab データベースとログファイル @end multitable ソースインストールのレイアウトはバイナリインストールと次の点が異なります: @itemize @bullet @item @code{mysqld} サーバは @file{bin} ではなく @file{libexec} ディレクトリにインストールされます。 @item データディレクトリは @file{data} ではなく @file{var} です。 @item @code{mysql_install_db} は @file{/usr/local/mysql/scripts} ではなく @file{/usr/local/bin} ディレクトリにインストールされます。 @item ヘッダーファイルのディレクトリは @file{include/mysql} で、 ライブラリのディレクトリは @file{lib/mysql} です。 @file{include} や @file{lib} ではありません。 @end itemize スクリプト @file{scripts/make_binary_distribution} を実行することにより、 コンパイルされたソースディストリビューションから、あなた自身のバイナリイン ストレーションを生成できます。 @node Many versions, MySQL binaries, Installation layouts, General Installation Issues @subsection アップデートがリリースされる方法と時 @cindex releases, updating @cindex updating, releases of MySQL MySQL は MySQL AB でかなり速く進化していて、我々はこれを他の MySQL ユーザに共有してもらいたいです。我々は、他の人が必要とし ていると思われるとても便利な機能を持った時に、リリースの作成を試みます。 我々は、実装が簡単な機能を要求するユーザの手助けも試みます。我々は、我々 のライセンスユーザが求めるものにも注目し、特に我々の拡張 email サポート 顧客が求めるものに注目して、彼らの手助けを試みます。 新しいリリースをダウンロードする必要はありません。News 節は、新しいリリー スが、あなたが本当に求める何かを持っているかどうかをあなたに教えます。 @xref{News}. 我々は MySQL の更新時は次のポリシーにしたがって行います： @itemize @bullet @item それぞれのマイナーアップデートで、バージョン文字列中の最後の数値が増加し ます。主要な新機能や前のバージョンとのマイナーな非互換があった時には、バー ジョン文字列中の2番目の数値が増加します。ファイル形式が変更した時、最初 の数値が増加します。 @item 安定にテストされたリリースは年に約 1-2 回現れます。しかし小さなバグが見 つかった場合は、バグフィックスだけのリリースがリリースされます。 @item 作業中のリリースは約 1-8 週間毎に現れます。 @item いくつかのプラットフォームのためのバイナリ配布は我々によってメジャーリリー スから作られます。他の人が他のシステムのためにバイナリ配布を作りますが、 おそらく頻繁ではありません。 @item 通常、小さなバグを見つけて修正するとすぐに、有効なパッチを作ります。 They are posted to @email{bugs@@lists.mysql.com} and will be added to the next release. @item 危険ではないけれども困らされるバグには、MySQL ソースレポジトリに 変更を加え、次のリリースには修正されます。 @item 偶然、致命的なバグがリリース中にある場合、我々は新しいリリースを可能な限 りすぐに作ります。他の会社もそうしてもらいたいです。 @end itemize 現在の安定リリースはバージョン 3.23 です; 我々はすでにバージョン 4.0 の開発に移行しています。 しかし、安定バージョンでもバグはまだ修正されます。 我々は、バグ修正と``行なわなければいけない''ことを無視するような、完全な 凍結を考えていません。``幾分かの凍結''とは、``ほとんど確実に既に動作して いるものに影響を与えない''小さなことを追加するかもしれないということを意 味します。 MySQL uses a slightly different naming scheme from most other products. In general it's relatively safe to use any version that has been out for a couple of weeks without being replaced with a new version. @xref{Which version}. @node MySQL binaries, Installing binary, Many versions, General Installation Issues @subsection MySQL Binaries Compiled by MySQL AB @cindex binary distributions サービスとして、我々 MySQL AB は MySQL のバイナリ配布を提供しています。 これらのコンパイルは MySQL AB 内部でおこなったり、我々にマシンの アクセスを提供してもらっている顧客のマシン上で行っています。 これらの配布物は @code{Build-tools/Do-compile} で作成され (このスクリプトは @code{scripts/make_binary_distribution} を使用して ソースをコンパイルし @code{tar.gz} バイナリを作成します)、 以下のコンパイルオプションで調整されています。 Binaries built on MySQL AB development systems: @table @asis @item Linux 2.4.xx i386 with @code{gcc} 2.95.3 @code{CFLAGS="-O2 -mcpu=pentiumpro" CXX=gcc CXXFLAGS="-O2 -mcpu=pentiumpro -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static} @item Linux 2.4.xx ia64 with @code{ecc} (Intel C++ Itanium Compiler 7.0) @code{CC=ecc CFLAGS=-tpp1 CXX=ecc CXXFLAGS=-tpp1 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile} @item Linux 2.4.xx alpha with @code{ccc} (Compaq C V6.2-505 / Compaq C++ V6.3-006) @code{CC=ccc CFLAGS="-fast -arch generic" CXX=cxx CXXFLAGS="-fast -arch generic -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared --disable-shared} @item Linux 2.2.xx sparc with @code{egcs} 1.1.2 @code{CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared} @item Linux 2.4.xx s390 with @code{gcc} 2.95.3 @code{CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static} @item Sun Solaris 2.8 sparc with @code{gcc} 3.2 @code{CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --with-named-curses-libs=-lcurses --disable-shared} @item Sun Solaris 2.9 sparc with @code{gcc} 2.95.3 @code{CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-curses-libs=-lcurses --disable-shared} @item Sun Solaris 2.9 sparc with @code{cc-5.0} (Sun Forte 5.0) @code{CC=cc-5.0 CXX=CC ASFLAGS="-xarch=v9" CFLAGS="-Xa -xstrconst -mt -D_FORTEC_ -xarch=v9" CXXFLAGS="-noex -mt -D_FORTEC_ -xarch=v9" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --enable-thread-safe-client --disable-shared} @item IBM AIX 4.3.2 ppc with @code{gcc} 3.2.1 @code{CFLAGS="-O2 -mcpu=powerpc -Wa,-many " CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared} @item IBM AIX 5.1.0 ppc with @code{gcc} 3.2.1 @code{CFLAGS="-O2 -mcpu=powerpc -Wa,-many" CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --with-server-suffix="-pro" --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared --with-innodb} @item HP-UX 10.20 pa-risc1.1 with @code{gcc} 3.1 @code{CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc CXXFLAGS="-DHPUX -I/opt/dce /include -felide-constructors -fno-exceptions -fno-rtti -O3 -fPIC" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-pthread --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC --disable-shared} @item HP-UX 11.11 pa-risc2.0 with @code{aCC} (HP ANSI C++ B3910B A.03.33) @code{CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared} @item Apple Mac OS X 10.2 powerpc with @code{gcc} 3.1 @code{CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared} @item FreeBSD 4.7 i386 with @code{gcc} 2.95.4 @code{CFLAGS=-DHAVE_BROKEN_REALPATH ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared} @end table The following binaries are built on third-party systems kindly provided to MySQL AB by other users. Please note that these are only provided as a courtesy. Since MySQL AB does not have full control over these systems, we can only provide limited support for the binaries built on these systems. @table @asis @item SCO Unix 3.2v5.0.6 i386 with @code{gcc} 2.95.3 @code{CFLAGS="-O3 -mpentium" LDFLAGS=-static CXX=gcc CXXFLAGS="-O3 -mpentium -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared} @item Caldera Open Unix 8.0.0 i386 with @code{CC} 3.2 @code{CC=cc CFLAGS="-O" CXX=CC ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared} @item Compaq Tru64 OSF/1 V5.1 732 alpha with @code{cc/cxx} (Compaq C V6.3-029i / DIGITAL C++ V6.1-027) @code{CC="cc -pthread" CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all" CXX="cxx -pthread" CXXFLAGS="-O4 -ansi_alias -fast -inline speed -speculate all -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-prefix=/usr/local/mysql --with-named-thread-libs="-lpthread -lmach -lexc -lc" --disable-shared --with-mysqld-ldflags=-all-static} @item SGI Irix 6.5 IP32 with @code{gcc} 3.0.1 @code{CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared} @end table The following compile options have been used for binary packages MySQL AB used to provide in the past. These binaries are currently not being updated anymore, but the compile options are kept in here for reference purposes. @table @asis @item Linux 2.2.x with x686 with @code{gcc} 2.95.2 @code{CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static --disable-shared --with-extra-charsets=complex} @item SunOS 4.1.4 2 sun4c with @code{gcc} 2.7.2.1 @code{CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" ./configure --prefix=/usr/local/mysql --disable-shared --with-extra-charsets=complex --enable-assembler} @item SunOS 5.5.1 (and above) sun4u with @code{egcs} 1.0.3a or 2.90.27 or gcc 2.95.2 and newer @code{CC=gcc CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex --enable-assembler} @item SunOS 5.6 i86pc with @code{gcc} 2.8.1 @code{CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex} @item BSDI BSD/OS 3.1 i386 with @code{gcc} 2.7.2.1 @code{CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex} @item BSDI BSD/OS 2.1 i386 with @code{gcc} 2.7.2 @code{CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex} @item AIX 2 4 with @code{gcc} 2.7.2.2 @code{CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex} @end table 上で示したオプション以外で最適化を施した方はだれでも、開発者向けの メーリングリストにポストできます。 @email{internals@@lists.mysql.com}. RPM 配布では MySQL 3.22 を user-contributed としています。 3.22 をはじめ、いくつかの RPM パッケージは MySQL AB 製です。 MySQL のデバッグバージョンをコンパイルしたい場合は、 @code{--with-debug} または @code{--with-debug=full} を上記の configure 行 に追加して、すべての @code{-fomit-frame-pointer} オプションを取り除いてく ださい。 For the Windows distribution, please see @ref{Windows installation}. @node Installing binary, , MySQL binaries, General Installation Issues @subsection Installing a MySQL Binary Distribution @cindex installing, binary distribution @cindex binary distributions, installing See also @ref{Windows binary installation}, @ref{Linux-RPM}, and @ref{Building clients}. MySQL の バイナリ配布プログラムをインストールする際は以下のツールが必要になります： @itemize @bullet @item GNU @code{gunzip}。ソースを伸長するのに必要です。 @item ファイルアーカイバ @code{tar}。これもソースを展開するのに必要です。 GNU @code{tar}の動作は確認されています。Sun @code{tar}の使用には問題があります。 @end itemize @cindex RPM, defined @cindex RPM Package Manager Linux では別の形式、RPM-based(RPM Package Manager)配布も行われています。 @xref{Linux-RPM}. @c texi2html fails to split chapters if I use strong for all of this. もしもこの問題にぶつかってしまった場合は @code{mysqlbug} を使用してください。 質問等は @email{mysql@@lists.mysql.com} に送ってください。 問題点がバグに該当しなくても @code{mysqlbug} は情報を集めていますので解決の 手助けになることと思います。 @code{mysqlbug} を使用すれば問題の解決方法を得る 確率が増します。@code{mysqlbug} は解凍されたプログラムの @file{bin} 以下にあります。 @xref{Bug reports}. @cindex commands, for binary distribution MySQL バイナリ配布プログラムのインストール及び 立ち上げまでに必要となる基本操作は以下の通りです。 @example shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or shell> bin/mysqld_safe --user=mysql & if you are running MySQL 4.x @end example @cindex adding, new users @cindex new users, adding @cindex users, adding 新しいユーザを追加するには @code{bin/mysql_setpermission} スクリプトを 使用できます。使用の際は@code{DBI}と@code{Msql-Mysql-modules}の Perlモジュールをインストールする必要があります。 より詳細な情報をここから示します。 バイナリ配布のプログラムをインストールする際は以下に従ってください。 その後、@ref{Post-installation}に進んでインストールの終了処理と動作試験を行ってください。 @enumerate @item バイナリ配布プログラムを解凍するためのディレクトリを用意してください。 そして、そこにバイナリ配布ファイルを置いてください。 以下の例では @file{/usr/local} にファイルを解凍し、@file{/usr/local/mysql} に MySQLをインストールします。（従って以下の例では操作するユーザが @file{/usr/local} に対して書き込み権限を持つことを前提としています。 もしも @file{/usr/local} への書き込みが禁じられている場合は @code{root}としてインストールを行う必要があります。 @item プログラムの配布は以下のサイトから行ってください。 @ref{Getting MySQL, , Getting MySQL}. MySQLのバイナリ配布は圧縮された @code{tar} 形式で行われており、 @file{mysql-VERSION-OS.tar.gz} のような形式の名前が付けられています。 ここで、@code{VERSION} はバージョン番号（例えば @code{3.21.15}）を @code{OS} はプラットホームとなるOS（例えば @code{pc-linux-gnu-i586}）を示します。 @item バイナリ配布ファイルに @code{-max} という表示があるものがありますが、 これはこのプログラムが transaction-safe 機能やその他の機能をサポート していることを示しています。@xref{mysqld-max, , @code{mysqld-max}}。 全てのバイナリプログラムは同じソースファイルからmakeされたものです。 @item @code{mysqld}が動作するためのユーザとグループを作成してください。 @example shell> groupadd mysql shell> useradd -g mysql mysql @end example これらのコマンドは @code{mysql} グループと @code{mysql} ユーザを作成するものです。 @code{useradd} や @code{groupadd} というコマンドもありますが、 これらは使用プラットホームによって使い方が若干異なります。 また、@code{adduser} や @code{addgroup} と呼ばれる場合もあります。 @code{mysql} 以外のユーザやグループでも使用できます。 @item インストール先のディレクトリを変更する場合は以下のようにします。 まずディレクトリを移動します。 @example shell> cd /usr/local @end example @item 以下のように移動したディレクトリ上でプログラムの展開を行い インストールディレクトリを作成してください。 @example shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql @end example 最初のコマンドで @file{mysql-VERSION-OS} という名前のディレクトリを作成します。 次のコマンドはそのディレクトリへのシンボリックリンクを作成し、 ユーザに単純な @file{/usr/local/mysql} という名前での利用を可能にします。 @item 以下のようにインストールディレクトリへ移動します。 @example shell> cd mysql @end example 複数のファイルが @code{mysql} 以下のディレクトリに展開されているのが おわかりになると思います。 中でもインストールに重要な役目を果たすものは @file{bin} と @file{scripts} のサブディレクトリにあります。 @table @file @item bin @tindex PATH environment variable @tindex environment variable, PATH This directory contains client programs and the server You should add the full pathname of this directory to your @code{PATH} environment variable so that your shell finds the MySQL programs properly. @xref{Environment variables}. @item scripts このディレクトリには @code{mysql_install_db} という @code{mysql} への アクセス管理を行うデータベースを初期化するためのスクリプトが置いてあります。 @end table @item @code{mysqlaccess}を使う必要があり、なおかつ、標準ディレクトリとは異なる場所に インストールを行いたい場合は、@code{mysqlaccess} が @code{mysql}クライアントを 起動できるように環境設定を行う必要があります。 @file{bin/mysqlaccess}の18行目位にある以下のような行を変更してください。 @example $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable @end example これを実際に @code{mysql} がインストールされているディレクトリに変更してください。 これをしないと @code{mysqlaccess} を使う際に @code{Broken pipe} エラーが発生します。 @item 以下のようにすることによりアクセス管理データベースを作ることができます （初めてMySQLをインストールする時だけ必要）。 @example shell> scripts/mysql_install_db @end example 使用する MySQL のバージョンが 3.22.10 より古い場合はこの操作をする時に MySQL サーバが 立ち上がっている必要がありましたが、現在のバージョンでは必要ありません。 @item Change ownership of binaries to @code{root} and ownership of the data directory to the user that you will run @code{mysqld} as: @example shell> chown -R root /usr/local/mysql/. shell> chown -R mysql /usr/local/mysql/data shell> chgrp -R mysql /usr/local/mysql/. @end example 最初のコマンドによって全てのファイルの @code{owner} 属性が @code{root} になります。 二行目のコマンドによってデータディレクトリ以下のファイル全ての @code{owner} 属性が @code{mysql} になります。 最後のコマンドによって全てのファイルの @code{group} 属性が @code{mysql} になります。 @item Perlモジュール@code{DBI}、@code{DBD}のインストールが必要なら@ref{Perl support}の項をご覧下さい。 @item MySQL を OS のブート時に自動的に起動したい場合は @code{support-files/mysql.server} を 貴方のシステムの的確な場所にコピーして使用できます。 より詳しい情報は @code{support-files/mysql.server} のスクリプト自体や @ref{Automatic start} にあります。 @end enumerate 全てのファイルの展開とインストールが終了したら初期化と稼動試験を行います。 以下のようにしてMySQLサーバを立ち上げることができます。 @example shell> bin/safe_mysqld --user=mysql & @end example Now proceed to @ref{safe_mysqld, , @code{safe_mysqld}}, and @xref{Post-installation}. @node Installing source, Post-installation, General Installation Issues, Installing @section MySQL ソースディストリビューションのインストール @cindex installing, source distribution @cindex source distribution, installing @cindex installation overview ソースインストールに取り掛かる前に、最初に我々のバイナリがあなたのプラット フォームに有効で、動作するかどうかをチェックしてください。我々は、我々のバ イナリが可能な限りのオプションで構築されていることを確認するために多くの努 力をしています。 ソースから MySQL を作成しインストールするためには次のツールが必 要です: @itemize @bullet @item GNU @code{gunzip}。配布の伸張のため。 @item 適正な @code{tar}。配布の展開のため。GNU @code{tar} は動くことが知られて います。Sun の @code{tar} は問題があることが知られています。 @item A working ANSI C++ compiler. @code{gcc} >= 2.95.2, @code{egcs} >= 1.0.2 or @code{egcs 2.91.66}, SGI C++, and SunPro C++ are some of the compilers that are known to work. @code{libg++} is not needed when using @code{gcc}. @code{gcc} 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as @file{sql/sql_base.cc}. If you only have @code{gcc} 2.7.x, you must upgrade your @code{gcc} to be able to compile MySQL. @code{gcc} 2.8.1 is also known to have problems on some platforms, so it should be avoided if a new compiler exists for the platform. MySQL 3.23.x のコンパイル時は、@code{gcc} >= 2.95.2 を推奨します。 @item 良い @code{make} プログラム。GNU @code{make} は常に推奨され、時々は必要 とされます。問題があれば GNU @code{make} 3.75 以上を試すことをお勧めしま す。 @end itemize @code{-fno-exceptions} オプションを解釈する @strong{gcc} の最近のバージョ ンを使用している場合は、それを使用することが@strong{とても重要}です。そう でなければ、ランダムにクラッシュするバイナリができあがるでしょう。また、 @code{-fno-exceptions} に加え、@code{-felide-contructors} と @code{-fno-rtti} を使用することをお奨めします。 疑いがある時は、次を行なってください: @example CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions \ -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static @end example 多くのシステムで、これは速くて安定したバイナリを与えます。 @c texi2html fails to split chapters if I use strong for all of this. 問題が起きたときは、@email{mysql@@lists.mysql.com} に質問を投稿する時に @strong{@code{mysqlbug} を常に使用してください}。問題がバグでないとして も、@code{mysqlbug} はあなたの問題を解決する助けになるであろうシステム情 報を収集します。@code{mysqlbug} を使用しないと、あなたの問題の解決を得る 可能性が小さくなります！ @code{mysqlbug} は、配布のアンパック後に @file{scripts} ディレクトリ内に見つけられます。 @xref{Bug reports}. @menu * Quick install:: Quick installation overview * Applying patches:: Applying patches * configure options:: Typical @code{configure} options * Installing source tree:: Installing from the Development Source Tree * Compilation problems:: Problems Compiling MySQL? * MIT-pthreads:: MIT-pthreads Notes * Windows source build:: Windows Source Distribution @end menu @node Quick install, Applying patches, Installing source, Installing source @subsection 素早いインストールの概要 MySQL をソースからインストールするために行なわなければならない 基本的なコマンド: @example shell> groupadd mysql shell> useradd -g mysql mysql shell> gunzip < mysql-VERSION.tar.gz | tar -xvf - shell> cd mysql-VERSION shell> ./configure --prefix=/usr/local/mysql shell> make shell> make install shell> scripts/mysql_install_db shell> chown -R root /usr/local/mysql shell> chown -R mysql /usr/local/mysql/var shell> chgrp -R mysql /usr/local/mysql shell> cp support-files/my-medium.cnf /etc/my.cnf shell> /usr/local/mysql/bin/safe_mysqld --user=mysql & or shell> /usr/local/mysql/bin/mysqld_safe --user=mysql & if you are running MySQL 4.x. @end example InnoDB テーブルをサポートしたい場合は、@code{/etc/my.cnf} ファイルを編集し て、@code{innodb_...} で始まるパラメータの前の @code{#} 文字を削除すべきで す。 @xref{Option files}, and @ref{InnoDB start}. RPM ソースから開始する場合は： @example shell> rpm --rebuild --clean MySQL-VERSION.src.rpm @end example これはインストールできるRPMバイナリを作成します もし @code{DBI} と @code{Msql-Mysql-modules} Perl モジュールをインストールするなら、 @code{bin/mysql_setpermission} スクリプトが使用する新しいユーザーを 追加することができます。 次にさらに詳細な説明を行ないます: ソース配布のインストールには、次のステップに従い、それから インストール 後の初期化とテストのために @ref{Post-installation} に進んでください。 @enumerate @item 配布をアンパックしたいディレクトリを選んで、そこに移ってください。 @item 配布ファイルを @ref{Getting MySQL, , Getting MySQL}. にリストされたサイトの一つから得てください。 @item MySQL で Berkeley DB テーブルの使用に興味がある場合、Berkeley DB ソースコー ドのパッチバージョンを入手する必要があります。処理の前に Berkeley DB テー ブルの章を読んでください。 @xref{BDB}. MySQL ソース配布は圧縮された @code{tar} アーカイブとして提供さ れ、@file{mysql-VERSION.tar.gz} のような名前を持ちます。ここで @code{VERSION} は @value{mysql_version} のような番号です。 @item @code{mysqld} を実行するユーザーとグループを追加します: @example shell> groupadd mysql shell> useradd -g mysql mysql @end example これらのコマンドは @code{mysql} グループと @code{mysql} ユーザを追加します。 @code{useradd} と @code{groupadd} 構文は、別のバージョンの UNIX 上では少し異なるでしょ う。@code{adduser} と @code{addgroup} と呼ばれることもあります。ユーザとグ ループは @code{mysql} の代わりに他の何かにすることもできます。 @item カレントディレクトリに配布をアンパックしてください: @example shell> gunzip < /path/to/mysql-VERSION.tar.gz | tar xvf - @end example このコマンドは @file{mysql-VERSION} という名前のディレクトリを作成します。 @item Change into the top-level directory of the unpacked distribution: @example shell> cd mysql-VERSION @end example 注意: 現在のこのトップレベルディレクトリで MySQL の configure と build を行なう必要があります。別のディレクトリでは build できません。 @item リリースを configure し、全てをコンパイルしてください: @example shell> ./configure --prefix=/usr/local/mysql shell> make @end example @code{configure} の実行時、いくつかのオプションを指定できます。オプショ ンの一覧は @code{./configure --help} を実行してください。@ref{configure options, , @code{configure} options}, さらに有用なオプションのいくつかに ついて議論しています。 @code{configure} が失敗して、援助を得るために @email{mysql@@lists.mysql.com} にメー ルを送ろうとする場合、@file{config.log} から問題の解決の手助けにできると 考えられる行を含めてください。@code{configure} が異常終了する場合、 @code{configure} からの出力の最後の数行も含めてください。バグレポートは @code{mysqlbug} スクリプトを使用して投稿してください。@xref{Bug reports}。 コンパイルが失敗する場合、いくらかのよくある問題での手助けのため、 @ref{Compilation problems} を参照してください。 @item 全てをインストールしてください: @example shell> make install @end example このコマンドは @code{root} として実行する必要があります。 @item MySQL 権限テーブルを生成してください(以前に MySQL をイ ンストールしていない時にだけ必要です): @example shell> scripts/mysql_install_db @end example 注意: 3.22.10 より古い MySQL バージョンでは、 @code{mysql_install_db} 実行時に MySQL サーバが開始されましたが、 これはもはや真ではありません！ @item バイナリのオーナーを @code{root} に、 データディレクトリの所有権を @code{mysqld} を実行するユーザに変更し てください: @example shell> chown -R root /usr/local/mysql shell> chown -R mysql /usr/local/mysql/var shell> chgrp -R mysql /usr/local/mysql @end example 最初のコマンドはファイルの @code{owner} 属性を @code{root} ユーザーに変更し、 2番目のコマンドは @code{owner} を @code{mysql} ユーザに変更し、 3番目のコマンドは @code{group} 属性を @code{mysql} グループに変更します。 @item Perl @code{DBI}/@code{DBD} インタフェースのサポートをインストールしたい 場合、@ref{Perl support} を見てください。 @item MySQL をマシン起動時に自動的に開始したい場合、 @code{support-files/mysql.server} をシステムのスタートアップファイルがあ る場所にコピーしてください。さらなる情報は @code{support-files/mysql.server} スクリプト自身の中と、 @ref{Automatic start} に見つけられます。 @ref{Automatic start}. @end enumerate 全てがインストールされた後、配布の初期化とテストを行なうべきです。 @example shell> /usr/local/mysql/bin/safe_mysqld --user=mysql & @end example コマンドがすぐに @code{mysqld daemon ended} エラーで失敗する場合、 @file{mysql-data-directory/'hostname'.err} ファイルになんらかの情報を 見つけることができます。 よくあることとして、すでに他の @code{mysqld} が 走っている場合などがあります。 @xref{Multiple servers}. Now proceed to @ref{Post-installation}. @node Applying patches, configure options, Quick install, Installing source @subsection パッチの適用 @cindex patches, applying @cindex applying, patches 時々、パッチは、メーリング・リストに流されたり、または MySQL Web サイトのパッチエリア (@uref{http://www.mysql.com/downloads/patches.html}) に置かれます。 メーリング・リストからのパッチを適用するには、パッチが載っているメッセージを ファイルに保存して、あなたの MySQL ソース・ツリーの 一番上のディレクトリーに移動し、以下のようにコマンドを実行します： @example shell> patch -p1 < patch-file-name shell> rm config.cache shell> make clean @end example FTPサイトに置かれるパッチは、プレーンテキストファイルとして、 あるいは @code{gzip} で圧縮されたファイルとして頒布されます。 プレーンテキストのパッチの場合は、上に示したメーリングリストの パッチと同様に適用します。 圧縮されたパッチを適用するには、 MySQL ソース・ツリーの 一番上のディレクトリーに移動し、以下のようにコマンドを実行します： @example shell> gunzip < patch-file-name.gz | patch -p1 shell> rm config.cache shell> make clean @end example それから通常のソースインストールの指示を @code{./configure} ステップから 始めます。@code{make install} ステップ実行後、あなたの MySQL サー バを再起動します。 @code{make install} を実行する前に、現在走っているサーバーを止める必要があるかもしれません。 ( @code{mysqladmin shutdown} で止めます ) いくつかのシステムでは、現在実行しているものを止めない限り、 新しいバージョンをインストールできないようになっています。 @node configure options, Installing source tree, Applying patches, Installing source @subsection 典型的な @code{configure} オプション @findex without-server option @cindex @code{configure} script @cindex options, configure @cindex configuration options @cindex log files @cindex files, log @code{configure} スクリプトは MySQL 配布をどのようにコンフィグ するかを制御するための多くの処理を提供します。典型的には、 @code{configure} コマンドラインにオプションを使用してこれを行ないます。 いくつかの環境変数を使用しても @code{configure} に影響を与えることができ ます。 @xref{Environment variables}. @code{configure} がサポートするオプションの一覧は、次のコマンドを 実行してください: @example shell> ./configure --help @end example 一般的に使用される @code{configure} オプションのいくつかを以下に説明します: @itemize @bullet @item MySQL クライアントライブラリとクライアントプログラムだけをコン パイルするには、@code{--without-server} オプションを使用してください: @example shell> ./configure --without-server @end example @c FIX incorrect.. C++ コンパイラがなければ、@code{mysql} はコンパイルできません(これは C++ を要求するクライアントプログラムの一つです)。この場合、@code{configure} から C++ コンパイラをテストするコードを削除でます。それから @code{./configure} を @code{--without-server} オプションつきで実行してく ださい。コンパイルステップは @code{mysql} の作成を試みますが、 @file{mysql.cc} についての警告は無視できます。(@code{make} が止まる場合、 エラーが発生しても残りの作成を継続するように @code{make -k} を試してくだ さい。) @item 組み込み MySQL ライブラリ(@code{libmysqld.a})を得たい場合は、 @code{--with-embedded-server} オプションを使用してください。(version 4.0以 上) @item ログファイルとデータベースディレクトリを @file{/usr/local/var} 配下にお きたくない場合は、次の @code{configure} コマンドのうちのどれかを使用してく ださい: @example shell> ./configure --prefix=/usr/local/mysql shell> ./configure --prefix=/usr/local \ --localstatedir=/usr/local/mysql/data @end example 最初のコマンドはインストールプレフィックスを変更し、デフォルトの @file{/usr/local} ではなく @file{/usr/local/mysql} 配下にインストールし ます。次のコマンドはデフォルトのインストールプレフィックスを保存しますが、 データベースディレクトリのデフォルト位置(通常は @file{/usr/local/var})を 上書きし、@code{/usr/local/mysql/data} に変更します。 MySQL をコンパイルした後でも、これらのオプションはオプションファイルで変更 できます @xref{Option files}. @cindex changing socket location @cindex socket location, changing @cindex mysql.sock, changing location of @item UNIX を使用していて、ソケットの位置をデフォルト位置(通常は @file{/tmp} または @file{/var/run})でなく他のどこかにしたい場合は、@code{configure} コマン ドを次のように使用します: @example shell> ./configure --with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock @end example ファイル名は絶対パスでなければなりません！ MySQL オプションファイルを使用することで、@file{mysql.sock} の場所をあとで 変更することもできます。 @xref{Problems with mysql.sock}. @cindex compiling, statically @cindex statically, compiling @item 静的リンクされたプログラムをコンパイルしたい場合(例えば、バイナリ配布を 作成するため、もっと速くするため、いくつかの RedHat 配布での問題を回避す るため)は、次のように @code{configure} を実行します: @example shell> ./configure --with-client-ldflags=-all-static \ --with-mysqld-ldflags=-all-static @end example @tindex @code{CC} environment variable @tindex environment variable, @code{CC} @tindex @code{CXX} environment variable @tindex environment variable, @code{CXX} @cindex @code{gcc} @cindex C++ compiler, @code{gcc} @cindex compiler, C++ @code{gcc} @item @code{gcc} を使用していて、@code{libg++} や @code{libstdc++} がインストー ルされていない場合、@code{configure} に @code{gcc} を C++ コンパイラとし て使用することを伝えてください: @example shell> CC=gcc CXX=gcc ./configure @end example @code{gcc} を C++ コンパイラとして使用する時、@code{libg++} または @code{libstdc++} のリンクは試みません。 This may be a good idea to do even if you have the above libraries installed, as some versions of these libraries have caused strange problems for MySQL users in the past. あなたが使用しているコンパイラによって、設定するいくつかの標準的な環境変数 があります: @tindex CXXFLAGS environment variable @tindex environment variable, CXXFLAGS @multitable @columnfractions .19 .81 @item @strong{Compiler} @tab @strong{Recommended options} @item gcc 2.7.2.1 @tab CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" @item egcs 1.0.3a @tab CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" @item gcc 2.95.2 @tab CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" @item pgcc 2.90.29 or newer @tab CFLAGS="-O3 -mpentiumpro -mstack-align-double" CXX=gcc \ CXXFLAGS="-O3 -mpentiumpro -mstack-align-double -felide-constructors \ -fno-exceptions -fno-rtti" @end multitable 多くの場合、上述のオプションと次の configure 行オプションの使用によって、 最適な MySQL バイナリを得ることができます: @example --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static @end example 言い換えれば、すべての最近の gcc バージョン用には、完全な configure 行は次 のようなものになります: @example CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" ./configure \ --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static @end example 我々が MySQL Web サイト @uref{http://www.mysql.com/} 上で提供して いるバイナリは、完全に最適化されてコンパイルされ、多くのユーザに完全です。 @xref{MySQL binaries}。さらに速いバイナリを作成するために調整できることが いくつかありますが、これは上級ユーザ向けです。 @xref{Compile and link options}. コンパイラやリンカが共有ライブラリ @file{libmysqlclient.so.#} を生成でき ないというエラーになる場合、@code{--disable-shared} オプションを @code{configure} に与えることで、この問題を回避できます。この場合、 @code{configure} は共有ライブラリ @file{libmysqlclient.so.#} を作成しま せん。 @cindex default values, suppression @cindex suppression, default values @item 非 @code{NULL} 項目(すなわち、@code{NULL} が許されていない項目)に @code{DEFAULT} 項目値を使用しないように MySQL をコンフィグでき ます。これは、非 @code{NULL} 値を要求する全ての項目に値を明示的に指定し なければ、@code{INSERT} ステートメントはエラーを生成します。デフォルト値 の使用を抑えるには、次のように @code{configure} を実行します: @tindex CXXFLAGS environment variable @tindex environment variable, CXXFLAGS @example shell> CXXFLAGS=-DDONT_USE_DEFAULT_FIELDS ./configure @end example @cindex character sets @findex configure option, --with-charset @findex configure option, --with-extra-charsets @item デフォルトでは、MySQL は ISO-8859-1 (Latin1) 文字セットを使用し ます。デフォルトセットを変更するには、@code{--with-charset} オプションを 使用します: @example shell> ./configure --with-charset=CHARSET @end example @code{CHARSET} は次のうちの一つです: @code{big5}, @code{cp1251}, @code{cp1257}, @code{czech}, @code{danish}, @code{dec8}, @code{dos}, @code{euc_kr}, @code{gb2312}, @code{gbk}, @code{german1}, @code{hebrew}, @code{hp8}, @code{hungarian}, @code{koi8_ru}, @code{koi8_ukr}, @code{latin1}, @code{latin2}, @code{sjis}, @code{swe7}, @code{tis620}, @code{ujis}, @code{usa7}, or @code{win1251ukr}. @xref{Character sets}. サーバとクライアント間で文字を変換したい場合は、 @code{SET CHARACTER SET} コマンドを調べるべきです。 @xref{SET OPTION, , @code{SET}}. @cindex @code{myisamchk} @strong{警告:} テーブルを生成した後に文字セットを変更する場合、 @code{myisamchk -r -q --set-character-set=charset} を全てのテーブルに実行する必要があります。 そうでないと、インデックスは正しくソートされません。(これは、MySQL のイ ンストール時、いくつかのテーブルの生成時、異なる文字セットを使用して MySQL の再コンフィグ時、そして再インストール時に発生します。) オプション @code{--with-extra-charsets=LIST} で、サーバ内に組み込むべき追加 文字セットを指定することができます。 ここで、@code{LIST} は空白で区切られた文字セットのリストです。 @code{complex} は動的にロードできないすべての文字を含み、@code{all} はバイ ナリにすべての文字セットを含みます。 @item デバッグコードつきで MySQL を構築するには、 @code{--with-debug} オプションを使用します: @example shell> ./configure --with-debug @end example これにより、いくつかのエラーを見つけられる安全なメモリ割り当てが含まれ、 何が発生しているかについての出力を提供します。 @xref{Debugging server}. @item あなたのクライアントプログラムがスレッドを使用している場合、 MySQL クライアントライブラリを @code{--enable-thread-safe-client} configure オプションでスレッド安全用に コンパイルする必要があります。これは、スレッドアプリケーションがリンクす べき @code{libmysqlclient_r} ライブラリを生成します。 @xref{Threaded clients}. @item 固有のシステムに関係するオプションについては、この章より後のシステム固有 の節で見つけることができます。 @xref{Operating System Specific Notes}. @end itemize @node Installing source tree, Compilation problems, configure options, Installing source @subsection 開発ソースツリーからのインストール @cindex development source tree @cindex BitKeeper tree @cindex CVS tree @strong{警告:} 我々の新しいテストコードについて我々を手助けすることに興味 がある場合にだけ、この節を読むべきです。MySQL を得て、あなたのシ ステム上で実行したいだけの場合は、標準リリースディストリビューションを使 用すべきです(ソースまたはバイナリディストリビューション)。 我々のもっとも新しい開発ソースツリーを得るには、次の手順に従ってください: @enumerate @item Download @code{BitKeeper} from @uref{http://www.bitmover.com/cgi-bin/download.cgi}. You will need @code{Bitkeeper} 3.0 or newer to access our repository. @item Follow the instructions to install it. @item After @code{BitKeeper} is installed, first go to the directory you want to work from, and then use one of the following commands to clone the MySQL version branch of your choice: To clone the 3.23 branch, use this command: @example shell> bk clone bk://mysql.bkbits.net/mysql-3.23 mysql-3.23 @end example To clone the 4.0 branch, use this command: @example shell> bk clone bk://mysql.bkbits.net/mysql-4.0 mysql-4.0 @end example To clone the 4.1 branch, use this command: @example shell> bk clone bk://mysql.bkbits.net/mysql-4.1 mysql-4.1 @end example In the preceding examples the source tree will be set up in the @file{mysql-3.23/}, @file{mysql-4.0/}, or @file{mysql-4.1/} subdirectory of your current directory. If you are behind a firewall and can only initiate HTTP connections, you can also use @code{BitKeeper} via HTTP. If you are required to use a proxy server, simply set the environment variable @code{http_proxy} to point to your proxy: @example shell> export http_proxy="http://your.proxy.server:8080/" @end example Now, simply replace the @code{bk://} with @code{http://} when doing a clone. Example: @example shell> bk clone http://mysql.bkbits.net/mysql-4.1 mysql-4.1 @end example The initial download of the source tree may take a while, depending on the speed of your connection - please be patient. @item You will need GNU @code{make}, @code{autoconf 2.53 (or newer)}, @code{automake 1.5}, @code{libtool 1.4}, and @code{m4} to run the next set of commands. Note that @code{automake 1.7 or newer} doesn't yet work. If you are using trying to configure MySQL 4.1 you will also need @code{bison 1.75}. Older versions of @code{bison} may report this error: @code{sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded}. Note: the maximum table size is not actually exceeded, the error is caused by bugs in these earlier @code{bison} versions. The typical command to do in a shell is: @example cd mysql-4.0 bk -r get -Sq aclocal; autoheader; autoconf; automake (cd innobase ; aclocal; autoheader; autoconf; automake) # for InnoDB (cd bdb/dist ; sh s_all ) # for Berkeley DB ./configure # Add your favorite options here make @end example If you get some strange error during this stage, check that you really have @code{libtool} installed! A collection of our standard configure scripts is located in the @file{BUILD/} subdirectory. If you are lazy, you can use @file{BUILD/compile-pentium-debug}. To compile on a different architecture, modify the script by removing flags that are Pentium-specific. @item When the build is done, run @code{make install}. Be careful with this on a production machine; the command may overwrite your live release installation. If you have another installation of MySQL, we recommand that you run @code{./configure} with different values for the @code{prefix}, @code{with-tcp-port}, and @code{unix-socket-path} options than those used for your production server. @item Play hard with your new installation and try to make the new features crash. Start by running @code{make test}. @xref{MySQL test suite}. @item If you have gotten to the @code{make} stage and the distribution does not compile, please report it to @email{bugs@@lists.mysql.com}. If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. However, if you execute @code{aclocal} and get a @code{command not found} error or a similar problem, do not report it. Instead, make sure all the necessary tools are installed and that your @code{PATH} variable is set correctly so that your shell can find them. @item After the initial @code{bk clone} operation to get the source tree, you should run @code{bk pull} periodically to get the updates. @item You can examine the change history for the tree with all the diffs by using @code{bk sccstool}. If you see some funny diffs or code that you have a question about, do not hesitate to send e-mail to @email{internals@@lists.mysql.com}. Also, if you think you have a better idea on how to do something, send an e-mail to the same address with a patch. @code{bk diffs} will produce a patch for you after you have made changes to the source. If you do not have the time to code your idea, just send a description. @item @code{BitKeeper} has a nice help utility that you can access via @code{bk helptool}. @item Please note that any commits (@code{bk ci} or @code{bk citool}) will trigger the posting of a message with the changeset to our internals mailing list, as well as the usual openlogging.org submission with just the changeset comments. Generally, you wouldn't need to use commit (since the public tree will not allow @code{bk push}), but rather use the @code{bk diffs} method described previously. @end enumerate You can also browse changesets, comments and sourcecode online by browsing to e.g. @uref{http://mysql.bkbits.net:8080/mysql-4.1} For MySQL 4.1. The manual is in a separate tree which can be cloned with: @example shell> bk clone bk://mysql.bkbits.net/mysqldoc mysqldoc @end example @node Compilation problems, MIT-pthreads, Installing source tree, Installing source @subsection MySQL コンパイル時の問題 @cindex compiling, problems @cindex problems, compiling @cindex reconfiguring @cindex @code{config.cache} file @cindex files, @code{config.cache} Solaris や Linux 上で @code{gcc} を使用した場合、一切警告無く 全ての MySQL プログラムがきれいに作れます。 他のシステムではインクルードファイルの違いから警告が出るかもしれません。 MIT-pthreads を使用した際の警告は @ref{MIT-pthreads} を参照してください。 他の問題は、以下をチェックしてください。 多くの問題の解決のために、再 configure が必要です。 あなたが再構成する必要があるならば、以下に気をつけてください： @cindex running @code{configure} after prior invocation @cindex @code{configure}, running after prior invocation @cindex reconfiguring @cindex config.cache @itemize @bullet @item もし @code{configure} を一度実行した後に実行するならば、 @code{configure} は 前に作った情報を利用します。この情報は @file{config.cache} に保存されます。 @code{configure} は起動時にこのファイルを探し、もし存在するならば、 その中の情報が正しい物として読み込みます。 これはあなたが再コンフィグするならば無効になります。 @item @code{configure} を実行するごとに、 @code{make} を実行してコンパイルしなければなりません。 しかし、最初に、前のビルドでできたオブジェクトを、消しておいてください。 なぜなら、違うコンフィグオプションにより生成されたからです。 @end itemize 古いコンフィグやオブジェクトファイルの使用を防ぐため、 @code{configure} 前に以下のコマンドを実行してください： @example shell> rm config.cache shell> make clean @end example こうするかわりに、@code{make distclean} としても構いません。 以下に、 MySQL をコンパイルする際に起こりやすい問題をあげておきます： @itemize @bullet @item @cindex @code{cc1plus} problems @cindex @code{fatal signal 11} @cindex @code{sql_yacc.cc} problems @cindex internal compiler errors @cindex virtual memory, problems while compiling @cindex configure option, --with-low-memory @file{sql_yacc.cc} コンパイル時に、以下のようなエラーが出た場合、 メモリー、スワップが足りません： @example Internal compiler error: program cc1plus got fatal signal 11 or Out of virtual memory or Virtual memory exhausted @end example この問題は、@code{gcc} がインライン展開で @file{sql_yacc.cc} をコンパイルするのに、 とても多くのメモリーを必要とするからです。 この場合、 @code{configure} を @code{--with-low-memory} オプション指定で実行します： @example shell> ./configure --with-low-memory @end example このオプションは、 @code{gcc} を使用しているなら @code{-fno-inline} オプションを コマンドラインに加え、@code{gcc} 以外ならば @code{-O0} を加えます。 多くのメモリーとスワップを持っていない限りは、@code{--with-low-memory} オプションを使用すべきです。 この問題はけっこうなハードウェア構成でも起こることが知られています。 通常、 @code{--with-low-memory} オプションでこの問題は解決できます。 @item 標準では、@code{configure} は @code{c++} という名前でコンパイラーを使用し、 GNU @code{c++} は @code{-lg++} を使ってリンクします。 もし @code{gcc} を使用しているならば、コンフィグ時に以下のような問題が出るかもしれません： @cindex C++ compiler cannot create executables @example configure: error: installation or configuration problem: C++ compiler cannot create executables. @end example @tindex CXX environment variable @tindex Environment variable, CXX この問題は、@code{g++}, @code{libg++} あるいは @code{libstdc++} に関連したものです。 原因の一つとして考えられることは、 @code{g++} を持っていないか、あるいは、 @code{g++} はあっても @code{libg++} か @code{libstdc++} がないという事です。 @file{config.log} ファイルは c++ コンパイラが動作しなかった理由を記録しています！ この問題を解決するに当たり、あなたが持っている C++ コンパイラーの代わりに @code{gcc} を使用しても構いません。@code{CXX} 環境変数に @code{"gcc -O3"} としてみてください。 例えば： @tindex CXX environment variable @tindex Environment variables, CXX @example shell> CXX="gcc -O3" ./configure @end example これは @code{gcc} が @code{g++} と同様に C++ ソースをコンパイルするので動きますが、 @code{libg++} か @code{libstdc++} が標準ではリンクされません。 他の解決方法は、もちろん、@code{g++}, @code{libg++}, @code{libstdc++} をインストールすることです。 We would however like to recommend you to not use @code{libg++} or @code{libstdc++} with MySQL as this will only increase the binary size of mysqld without giving you any benefits. Some versions of these libraries have also caused strange problems for MySQL users in the past. @item もし以下のエラーのどれかが起きた場合、 GNU @code{make} のバージョンを上げてください： @example making all in mit-pthreads make: Fatal error in reader: Makefile, line 18: Badly formed macro assignment or make: file `Makefile' line 18: Must be a separator (: or pthread.h: No such file or directory @end example @cindex Solaris troubleshooting @cindex FreeBSD troubleshooting @cindex troubleshooting, Solaris @cindex troubleshooting, FreeBSD Solaris と FreeBSD の @code{make} プログラムには問題があることが知られています。 GNU @code{make} Version 3.75 は動作確認されています。 @tindex CC environment variable @tindex environment variable, CC @tindex CXX environment variable @tindex environment variable, CXX @tindex CFLAGS environment variable @tindex environment variable, CFLAGS @tindex CXXFLAGS environment variable @tindex environment variable, CXXFLAGS @item もし C,C++ のためにフラグを与えたい場合、@code{CFLAGS} と @code{CXXFLAGS} 環境変数に フラグを追加してください。同様に、 @code{CC} と @code{CXX} にコンパイラー名を 与えることもできます。 例えば： @example shell> CC=gcc shell> CFLAGS=-O3 shell> CXX=gcc shell> CXXFLAGS=-O3 shell> export CC CFLAGS CXX CXXFLAGS @end example @ref{MySQL binaries} にはフラグの定義がリストされています。 色々なシステム上で役に立つと思います。 @item 以下のようなエラーの場合、@code{gcc} コンパイラーをアップグレードしてください： @example client/libmysql.c:273: parse error before `__attribute__' @end example @code{gcc} 2.8.1 は動作することが確認されていますが、 @code{gcc} 2.95.2 以上をお勧めします。 @item @code{mysqld} コンパイル時に以下のようなエラーが出た場合、 @code{configure} が @code{accept()}, @code{getsockname()}, @code{getpeername()} の最後の引数を正しく検出していません： @example cxx: Error: mysqld.cc, line 645: In this statement, the referenced type of the pointer value "&length" is "unsigned long", which is not compatible with "int". new_sock = accept(sock, (struct sockaddr *)&cAddr, &length); @end example これを修正するには、@file{config.h} ファイル(@code{configure} により作られる) を修正します。 いかのように： @example /* Define as the base type of the last arg to accept */ #define SOCKET_SIZE_TYPE XXX @end example @code{XXX} を @code{size_t} か @code{int} (あなたのオペレーティングシステムが依存している型)に変えます。 (@code{configure} すると毎回 @file{config.h} は作り直されるので、 この修正は @code{configure} する度に行わなければならないことに注意) @item @file{sql_yacc.cc} ファイルは @file{sql_yacc.yy} から生成されます。 通常、 MySQL が既に生成されたコピーとともにあるので、 @file{sql_yacc.cc} ファイルを自分自身で作成することはありません。 しかし、以下のエラーの場合、再作成する必要があります： @example "sql_yacc.yy", line xxx fatal: default action causes potential... @end example これはあなたの @code{yacc} のバージョンが不十分であることを示しています。 @code{bison} (GNU 版 @code{yacc}) を代わりにインストールして使用する必要があります。 @item もし @code{mysqld} か MySQL クライアントをデバッグしたいなら、 @code{configure} を @code{--with-debug} オプション付きで実行します。 そしてコンパイルし、新しいクライアントライブラリーでクライアントをリンクします。 @xref{Debugging client}. @end itemize @node MIT-pthreads, Windows source build, Compilation problems, Installing source @subsection MIT-pthreads に関して @cindex MIT-pthreads @cindex thread support, non-native このセクションではMIT-pthreadsを使っているさいに起こる問題についていくつか述べて います。 Linux では、MIT-pthreads を使用してはならず、 LinuxThreads をインストールするべきです！ @xref{Linux}. もしあなたのシステムが本来のスレッドのサポートを提供しなければ、あなたは、 MIT-pthreadsパッケージを使って、MySQL を構築する必要があります。 これにはほとんどのFreeBSDシステム、SunOS4.x,Solaris 2.4とそれ以前、ほかいくつか が含まれます。 @xref{Which OS}. Note, that beginning with MySQL 4.0.2 MIT-pthreads are no longer part of the source distribution! If you require this package, you need to download it separately from @url{http://www.mysql.com/Downloads/Contrib/pthreads-1_60_beta6-mysql.tar.gz} After downloading, extract this source archive into the top level of the MySQL source directory. It will create a new subdirectory @code{mit-pthreads}. @itemize @bullet @item ほとんどのシステム上では @code{--with-mit-threads} オプションで @code{configure} 実行することによって、 MIT-pthreadsが使われることを強制することができます。 @example shell> ./configure --with-mit-threads @end example MIT-pthreadsを使う時、非ソースディレクトリで構築することはサポートされていませ ん。なぜなら、私たちはこのコードへ私たちの変更を最小にしたいからです。 @item MIT-pthreads が使われているかどうかチェックはサーバコードを configure するときに だけ行われます。もし、あなたが @code{--without-server} を使ってクライアントコードのみを ビルドすることを設定したならば、クライアントは MIT-othreads が使われているかいないか、 UNIXソケット接続がデフォルトで使われているのかわかりません。なぜなら UNIX ソケットは MIT-pthreads 下では動作しないからです。また、あなたはそのようなインスタンスでは @code{-h} または @code{--host} を使う必要があります。 @item MySQL が MIT-pthreads を使ってコンパイルされると、パフォーマンス上の問題のた めシステムロックはデフォルトでディスエーブルとされます。 @code{--external-locking} オプション を指定してサーバーに伝えることで、システムロックは使えるようになります。 This is only needed if you want to be able to run two MySQL servers against the same data files (not recommended). @item ときどき(少なくともSolarisでは) pthread の @code{bind()} コマンドは何のエラーメッセージ なしにソケットへの bind に失敗することがあります。これは結果としてサーバーへの接続 失敗となります。たとえば、 @example shell> mysqladmin version mysqladmin: connect to server at '' failed; error: 'Can't connect to mysql server on localhost (146)' @end example これを解決するために @code{mysqld} サーバーを終了して、再起動してください。こ れは私たちがサーバーダウンを強制して、すぐにリスタートさせようとしたときだけ起こ りました。 @item MIT-pthreads を使っていると、@code{sleep()} システムコールは @code{SIGINT} (break) では割り込みできません。 これは　@code{mysqladmin --sleep} を走らせているときにだけ 起こることがわかっています。 割り込みが発生してプロセスが停止する前に、あなたは終了させるための @code{sleep()} コールを待たなく てはなりません。 @item リンクしているとき(少なくともSolarisでは)、あなたはこのような warning メッセージ を受け取るでしょう。これらは無視してかまいません。 @example ld: warning: symbol `_iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken ld: warning: symbol `__iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken @end example @item 他のいくつかの warnings もまた無視してかまいません。 @example implicit declaration of function `int strtoll(...)' implicit declaration of function `int strtoul(...)' @end example @item 私たちはまだ MIT-pthread とともに動く @code{readline} を手に入れていません(これは必要では ないのですが、おそらく誰かには興味があるでしょう)。 @end itemize @node Windows source build, , MIT-pthreads, Installing source @subsection Windows Source Distribution You will need the following: @itemize @bullet @item VC++ 6.0 compiler (updated with 4 or 5 SP and Pre-processor package) The Pre-processor package is necessary for the macro assembler. More details at: @uref{http://msdn.microsoft.com/vstudio/sp/vs6sp5/faq.asp}. @item The MySQL source distribution for Windows, which can be downloaded from @uref{http://www.mysql.com/downloads/}. @end itemize Building MySQL @enumerate @item Create a work directory (e.g., workdir). @item Unpack the source distribution in the aforementioned directory. @item Start the VC++ 6.0 compiler. @item In the @code{File} menu, select @code{Open Workspace}. @item Open the @file{mysql.dsw} workspace you find on the work directory. @item From the @code{Build} menu, select the @code{Set Active Configuration} menu. @item Click over the screen selecting @code{mysqld - Win32 Debug} and click OK. @item Press @code{F7} to begin the build of the debug server, libs, and some client applications. @item When the compilation finishes, copy the libs and the executables to a separate directory. @item Compile the release versions that you want, in the same way. @item Create the directory for the MySQL stuff: e.g., @file{c:\mysql} @item From the workdir directory copy for the c:\mysql directory the following directories: @itemize @bullet @item Data @item Docs @item Share @end itemize @item Create the directory @file{c:\mysql\bin} and copy all the servers and clients that you compiled previously. @item If you want, also create the @file{lib} directory and copy the libs that you compiled previously. @item Do a clean using Visual Studio. @end enumerate Set up and start the server in the same way as for the binary Windows distribution. @xref{Windows prepare environment}. @node Post-installation, Upgrade, Installing source, Installing @section インストール後の設定とテスト @cindex post-installation, setup and testing @cindex testing, post-installation @cindex setup, post-installation @menu * mysql_install_db:: Problems running @code{mysql_install_db} * Starting server:: Problems starting the MySQL server * Automatic start:: Starting and stopping MySQL automatically @end menu 初めて MySQLをインストールしたら(バイナリからでもソースからでもですが)、 サーバーを動作させるために、許可テーブルを初期化しなくてはなりません。 またマシンの起動時、停止時に、サーバーを自動で開始、停止することもできます。 通常、許可テーブルのインストールとサーバーの開始は、 ソースディストリビューションなら以下のようにします： @cindex starting, the server @cindex server, starting @example shell> ./scripts/mysql_install_db shell> cd mysql_installation_directory shell> ./bin/safe_mysqld --user=mysql & @end example バイナリディストリビューション(RPM または pkg パッケージではない)では次を 行ないます: @example shell> cd mysql_installation_directory shell> ./scripts/mysql_install_db shell> ./bin/safe_mysqld --user=mysql & or shell> ./bin/mysqld_safe --user=mysql & if you are running MySQL 4.x. @end example これは、いくつかのデータベースを生成します。@code{mysql} データベースは全 てのデータベース権限を保持します。@code{test} データベースは MySQL をテストするために使用できます。そして、 @code{mysql_install_db} を実行したユーザの権限エントリと @code{root} ユー ザも生成します(パスワードはありません)。これは @code{mysqld} サーバの起動 も行ないます。 @code{mysql_install_db} は古い権限テーブルを上書きしません。そのため、どの ような環境でも安全に実行できます。@code{test} データベースを持ちたくないな ら、@code{mysqladmin -u root drop test} で削除できます。 テストは、MySQL のトップディレクトリーから簡単に実行できます。 バイナリ配布を使用する場合、これ(トップディレクトリ)は インストール先のディレクトリーになるでしょう(@file{/usr/local/mysql})。 ソース配布の場合、これは MySQL のソースディレクトリです。 @cindex testing, the server コマンドは本節といかに続く節で説明しますが、@code{BINDIR} は @code{mysqladmin} や @code{safe_mysqld} がインストールされたディレクトリを示します。 バイナリ配布を使用している場合、@code{BINDIR} はバイナリ配布の @file{bin} ディレクトリになります。 ソースからインストールした場合、@code{BINDIR} は、@code{configure} で特別指定しない限り、 @file{/usr/local/bin} です。 @code{EXECDIR} は @code{mysqld} サーバーのインストール先です。 バイナリ配布を使用している場合、これは @code{BINDIR} ディレクトリと同一になります。 ソースからインストールした場合、@file{/usr/local/libexec} です。 テストについて以下に詳細に説明します: @cindex testing, installation @enumerate @item If necessary, start the @code{mysqld} server and set up the initial MySQL grant tables containing the privileges that determine how users are allowed to connect to the server. This is normally done with the @code{mysql_install_db} script: @example shell> scripts/mysql_install_db @end example 通常、@code{mysql_install_db} の実行は初めて MySQL をインストール したあと一度だけ必要です。 すでにインストールされているものを アップグレードする際にはこの手順は飛ばせます。 （しかし、@code{mysql_install_db} は実に安全で、すでにテーブルが 存在している場合はいかなるテーブルも更新しません。したがって、 実行すべきかどうかわからない場合は、@code{mysql_install_db} を常に 走らせることができます） @code{mysql_install_db} は 6個のテーブルを作ります (@code{user}, @code{db}, @code{host}, @code{tables_priv}, @code{columns_priv}, @code{func}) @code{mysql} データベースに。 初期の権限状態についての説明は @ref{Default privileges}. これらの権限は MySQL @code{root} ユーザーに なんでもできるように許可し、そして、だれもが @code{'test'} という名前か @code{'test_'} ではじまる名前をもつ データベースを作成、使用できるように許可されています。 もし許可テーブルを設定していない場合、サーバーを起動時に以下のエラーが出ます： @tindex host.frm, problems finding @example mysqld: Can't find file: 'host.frm' @end example バイナリ配布の MySQL では、もし MySQL を @code{./bin/safe_mysqld} を実行しないで起動した場合に、このエラーがおきます! @ref{safe_mysqld, , @code{safe_mysqld}}. @code{root} で @code{mysql_install_db} を実行する必要があるとあなたは思うかもしれません。 しかし、 MySQL は @code{root} 以外のユーザーで起動できます。 データベースディレクトリがサーバーを起動したユーザに対して読み書きが許可されていれば良いのです。 MySQL を一般ユーザーで走らせる方法は @ref{Changing MySQL user, , Changing MySQL user}. もし @code{mysql_install_db} で問題が出たら、 @ref{mysql_install_db, , mysql_install_db}. を参照のこと。 @code{mysql_install_db} スクリプトを走らせるにはいくつか選択があります： @itemize @bullet @item @code{mysql_install_db} を走らせる前に編集して、許可の初期状態を変更してもいいでしょう。 これは多くのマシンに同じ権限設定をして MySQL をインストールする際に 役立ちます。 この場合、いくつかの @code{INSERT} 構文を @code{mysql.user} と @code{mysql.db} テーブルにたいして追加するようにするだけですみます! @item もしインストール後に許可を変更したい場合、 @code{mysql -u root mysql} で MySQL @code{root} ユーザーで接続して直接許可テーブルを変更する SQL 文を実行します。 @item すでに許可テーブルが作成された状態で、完全に許可テーブルを作成し直すことができます。 これはすでにインストールされたテーブルがある場合や、 @code{mysql_install_db} を編集した後にそう思うかもしれません。@code{mysql_install_db}. @end itemize これらの選択については @ref{Default privileges} からさらに情報が得られます。 @item MySQL サーバーを以下のようにして起動します： @example shell> cd mysql_installation_directory shell> bin/safe_mysqld & @end example サーバの起動に問題があれば、@ref{Starting server} を見てください。 @item code{mysqladmin} でサーバーが走っているか確認します。 サーバーが立ち上がり接続を受け付けるか確認する簡単な方法を以下に示します： @example shell> BINDIR/mysqladmin version shell> BINDIR/mysqladmin variables @end example 例えば、@code{mysqladmin version} の出力はあなたのプラットフォームと MySQL のバージョンを出力します。 出力は以下の様にでます： @example shell> BINDIR/mysqladmin version mysqladmin Ver 8.14 Distrib 3.23.32, for linux on i586 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license. Server version 3.23.32-debug Protocol version 10 Connection Localhost via Unix socket TCP port 3306 UNIX socket /tmp/mysql.sock Uptime: 16 sec Threads: 1 Questions: 9 Slow queries: 0 Opens: 7 Flush tables: 2 Open tables: 0 Queries per second avg: 0.000 Memory in use: 132K Max memory used: 16773K @end example @code{BINDIR/mysqladmin} の使用方法は、@code{--help} オプションで起動することにより得られます。 @item Verify that you can shut down the server: @cindex server, shutdown @cindex shutting down, the server @example shell> BINDIR/mysqladmin -u root shutdown @end example @item サーバーをリスタートするには、@code{safe_mysqld} か @code{mysqld} を直接実行します。 例えば： @cindex server, restart @cindex restarting, the server @example shell> BINDIR/safe_mysqld --log & @end example @code{safe_mysqld} が失敗するなら、 MySQL のインストールディレクトリーから実行してみてください。 もしそれでも起動しないなら、@ref{Starting server} を参照のこと。 @item いくつかの簡単なテストでサーバーが動いているか確認できます。 以下のようになります： @example shell> BINDIR/mysqlshow +-----------+ | Databases | +-----------+ | mysql | +-----------+ shell> BINDIR/mysqlshow mysql Database: mysql +--------------+ | Tables | +--------------+ | columns_priv | | db | | func | | host | | tables_priv | | user | +--------------+ shell> BINDIR/mysql -e "SELECT host,db,user FROM db" mysql +------+--------+------+ | host | db | user | +------+--------+------+ | % | test | | | % | test_% | | +------+--------+------+ @end example 他のプラットフォームで MySQL のパフォーマンスを比較するために @file{sql-bench} にベンチマークがあります。 @file{sql-bench/Results} ディレクトリには、他のデータベースやプラットフォームで ベンチを実行した結果があります。 全てのテストを実行するには、以下のようにします： @example shell> cd sql-bench shell> run-all-tests @end example RPM バイナリ配布には @file{sql-bench} ディレクトリがありません。 (RPM のソース配布には含まれます) この場合、ベンチマークをインストールしなくてはなりません。 MySQL バージョン 3.22 のバイナリ配布から、 @file{mysql-bench-VERSION-i386.rpm} という名前で RPM パッケージを作っており、 これにはベンチマークのデータとコードが含まれます。 @file{tests} サブディレクトリでテストすることも可能です。 例えば、@file{auto_increment.tst} の実行は以下のようにします： @example shell> BINDIR/mysql -vvf test < ./tests/auto_increment.tst @end example The expected results are shown in the @file{./tests/auto_increment.res} file. @end enumerate @node mysql_install_db, Starting server, Post-installation, Post-installation @subsection @code{mysql_install_db} 実行時の問題 @cindex @code{mysql_install_db} script @cindex scripts, @code{mysql_install_db} @code{mysql_install_db} スクリプトの目的は、新しい MySQL 権限テー ブルを生成することです。他のデータには何も影響しません！ 既に MySQL 権限テー ブルをインストールしている場合は、何も行ないません！ 権限テーブルを再生成したい場合は、@code{mysqld} サーバが動作していれば、それを落 としてから、次のように行なってください: @example mv mysql-data-directory/mysql mysql-data-directory/mysql-old mysql_install_db @end example この節では @code{mysql_install_db} を実行した際にでくわすかもしれない問題について述べます： @table @strong @item @code{mysql_install_db} doesn't install the grant tables これは @code{mysql_install_db} が権限テーブルをインストールできなかった事のメッセージですが、 続いて以下のようにメッセージが出た場合： @example starting mysqld daemon with databases from XXXXXX mysql daemon ended @end example この場合、注意深く log ファイルを調べてください！ エラーメッセージに出ている @file{XXXXXX} ディレクトリにログファイルがあり、 これに @code{mysqld} がなぜスタートしなかったか記されているはずです。 もし何が起こったかわからない場合、このログファイルを含んで @code{mysqlbug} を使用して バグレポートを投稿してください！ @xref{Bug reports}. @item There is already a @code{mysqld} daemon running この場合、 @code{mysql_install_db} を実行する必要はありません。 @code{mysql_install_db} を実行するのは MySQL を初めてインストールした後、 たった一回だけです。 @item Installing a second @code{mysqld} daemon doesn't work when one daemon is running これはすでに MySQL がインストールされており、 しかし新しいインストールを違うところに行おうとした場合に発生します。 (例えば、一度に二つのインストールを実行した場合など) 一般にこの問題は二つ目のサーバーを動いているサーバーと同じポート、ソケットを使用して起動しようとした場合に発生します。 この場合、@code{Can't start server: Bind on TCP/IP port: Address already in use} エラーメッセージか @code{Can't start server : Bind on unix socket...} エラーメッセージが出ます。 @xref{Installing many servers}. @item You don't have write access to @file{/tmp} @cindex write access, tmp @cindex temporary file, write access @cindex files, @code{tmp} もしソケットファイルを標準の場所(@file{/tmp})に作成するための書き込み許可がないなら、 あるいは、一時ファイルを @file{/tmp} に作成できないなら、 @code{mysql_install_db} の実行時、あるいは @code{mysqld} の起動／使用時に エラーとなるでしょう。 違うディレクトリーにソケットファイルや一時ファイルを指定するには： @tindex TMPDIR environment variable @tindex MYSQL_UNIX_PORT environment variable @tindex Environment variable, TMPDIR @tindex Environment variable, MYSQL_UNIX_PORT @example shell> TMPDIR=/some_tmp_dir/ shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysqld.sock shell> export TMPDIR MYSQL_UNIX_PORT @end example See @ref{Problems with mysql.sock}. @file{some_tmp_dir} は書き込みが可能なディレクトリーを指定しなくてはなりません。 @xref{Environment variables}. この後、@code{mysql_install_db} を走らせ、サーバーを起動する事ができます： @example shell> scripts/mysql_install_db shell> BINDIR/safe_mysqld & @end example @item @code{mysqld} crashes immediately もし RedHat バージョン 5.0 上で 2.0.7-5 より古い @code{glibc} を使用している場合、 全ての @code{glibc} パッチを当てなくてはなりません！ これに関しては MySQL メールのアーカイブに情報が多くあります。 @uref{http://lists.mysql.com/}. Also, see @ref{Linux}. @code{mysqld} を @code{--skip-grant-tables} 指定で起動することもできます。 そして以下のように @code{mysql} を使用して自分自身の手により許可を加えます： @example shell> BINDIR/safe_mysqld --skip-grant-tables & shell> BINDIR/mysql -u root mysql @end example @code{mysql} から手動で @code{mysql_install_db} に書かれている SQL コマンドを実行します。 許可テーブルをサーバーに読み込ますためには、 @code{mysqladmin flush-privileges} か @code{mysqladmin reload} を実行します。 @end table @node Starting server, Automatic start, mysql_install_db, Post-installation @subsection MySQL サーバー起動時の問題 @cindex server, starting problems @cindex problems, starting the server トランザクションをサポートするテーブル(BDB, InnoDB)を使用しようとする場合、 最初に @file{my.cnf} ファイルを生成して、使用しようとするテーブル型の起動オプショ ンを設定すべきです。 @xref{Table types}. 通常 @code{mysqld} サーバーの起動は、以下の三つの方法のうち一つで行います： @itemize @bullet @item @code{mysql.server} による起動。このスクリプトはシステムの起動時、停止時に使われます。 詳細は @ref{Automatic start}. @item @code{safe_mysqld} による起動。これは @code{mysqld} への適切なオプションを決定し、 それらのオプションでサーバーの起動を試みます。 @xref{safe_mysqld, , @code{safe_mysqld}}. @item For Windows NT/2000/XP, please see @ref{NT start}. @item By invoking @code{mysqld} directly. @end itemize @code{mysqld} デーモンの起動時に、デーモンはデータディレクトリにディレクトリを変えます。 ログファイルと pid (process ID) ファイルがこのディレクトリに書ける事、 そしてデータベースがこのディレクトリにある事を、デーモンは要求します。 データディレクトリの場所は配布物のコンパイル時に指定されています。 @code{mysqld} があなたのシステム上にデータベースディレクトリを見つけれなかった場合、 サーバーは動きません。 @code{mysqld} を @code{--help} オプションで起動すれば @code{mysqld} の デフォルトのパスを知ることができますので、 サーバーが起動しない理由が違うパスを使用しているために起こっているかどうかがわかります。 パスが違う場合、@code{mysqld} のコマンドラインの引数に正しいパスを指定して、デフォルト値を 上書きすることが可能です。(これらオプションは @code{safe_mysqld} にも同様に使用できます) 通常、MySQL がインストールされたディレクトリのベースディレクトリだけを @code{mysqld} に教えればいいはずです。 これは @code{--basedir} オプションを指定します。 @code{--help} オプションを使用すればパスの変更が確認できます。 (@code{--help} は@emph{必ず} 最後に指定のこと) 　例えば： @example shell> EXECDIR/mysqld --basedir=/usr/local --help @end example パスの設定が思い通りに言ったことを確認したら、 @code{--help} オプションを外してサーバーを起動します。 どの方法でサーバーを起動しても、もし起動に失敗すれば、ログファイルを確認してください。 なぜ失敗したか記録されています。ログファイルはデータベースディレクトリにあります。 (バイナリ配布の場合 @file{/usr/local/mysql/data} 、ソース配布の場合 @file{/usr/local/var}、 Windows では @file{\mysql\data\mysql.err} ) データベースディレクトリに @file{host_name.err} と @file{host_name.log} という ファイル (@code{host_name} はあなたのサーバー名) を探してください。 以下のようにしてそのファイルの最後の数行を確認します： @example shell> tail host_name.err shell> tail host_name.log @end example ログファイル中に次のような何かを見つけた場合: @example 000729 14:50:10 bdb: Recovery function for LSN 1 27595 failed 000729 14:50:10 bdb: warning: ./test/t1.db: No such file or directory 000729 14:50:10 Can't init databases @end example これは @code{--bdb-recover} 付きで @code{mysqld} が起動され、Berkeley DB がデータ ベースを復元しようとした時にログファイルに悪い何かを見つけたということを意 味します。継続を可能にするためには、古い Berkeley DB ログファイルをデータ ベースディレクトリから、あとで検査できる他の場所に移すべきです。ログファイ ルは @file{log.0000000001} (番号は時間の経つと増加します)と名付けられてい ます。 BDB テーブルサポートで @code{mysqld} を実行していて、@code{mysqld} が起動時にコア ダンプする場合、BDB recover log にいくつかの問題の原因があり得ます。この場 合、@code{mysqld} を @code{--bdb-no-recover} で起動を試みることができます。 これで救える場合は、データディレクトリから全ての @file{log.*} ファイルを削 除し、そして @code{mysqld} を再び起動してみてください。 以下のエラーの場合、他のプログラム（か他の @code{mysqld} サーバー）が @code{mysqld} が使用しようとしている TCP/IP ソケットを使っています： @example Can't start server: Bind on TCP/IP port: Address already in use or Can't start server : Bind on unix socket... @end example 他の @code{mysqld} サーバーが走っていないかを @code{ps} で確認します。 もし他のサーバーが起動していないなら、 @code{telnet your-host-name tcp-ip-port-number} コマンドを実行し、何回か @code{RETURN} キーをたたいてみてください。 もし、 @code{telnet: Unable to connect to remote host: Connection refused} のような エラーが出た場合、なにかが @code{mysqld} が使用しようとしているポートを既に使っています。 See @ref{mysql_install_db} and @ref{Multiple servers}. もし @code{mysqld} がすでに走っている場合、以下のコマンドにてパスの設定を知ることができます： @example shell> mysqladmin variables @end example または @example shell> mysqladmin -h 'your-host-name' variables @end example If you get @code{Errcode 13}, which means @code{Permission denied}, when starting @code{mysqld} this means that you didn't have the right to read/create files in the MySQL database or log directory. In this case you should either start @code{mysqld} as the root user or change the permissions for the involved files and directories so that you have the right to use them. もし @code{safe_mysqld} がサーバーを起動しても接続できないようなら、 @file{/etc/hosts} ファイルに以下のような記述を持たせてください： @example 127.0.0.1 localhost @end example この問題はスレッドライブラリーがなくて MySQL を MIT-pthreads を 使用するようにして作ったシステムにだけ起こります。 @code{mysqld} を起動できない場合、問題を見つけるためにトレースファイルの作 成を試みることができます。 @xref{Making trace files}. InnoDB テーブルを使用している場合、InnoDB 固有の起動オプションを参照してく ださい。 @xref{InnoDB start}. BDB (Berkeley DB) テーブルを使用する場合は、BDB 固有の起動オプションに精通 すべきです。 @xref{BDB start}. @node Automatic start, , Starting server, Post-installation @subsection MySQL の自動起動と自動停止 @cindex starting, the server automatically @cindex stopping, the server @cindex server, starting and stopping @code{mysql.server} と @code{safe_mysqld} スクリプトは、システム起動時に自 動的にサーバを起動するために使用できます。@code{mysql.server} はサーバを停 止するためにも使用できます。 @code{mysql.server} とスクリプトは @code{start}, @code{stop} 引数を指定することにより サーバーを起動、停止できます： @example shell> mysql.server start shell> mysql.server stop @end example @code{mysql.server} は MySQL インストールディレクトリの @file{share/mysql} ディレクトリ、 または MySQL ソースツリーの @file{support-files} ディレクトリにあります。 @code{mysql.server} はサーバーを起動時する前に MySQL がインストールされた ディレクトリにディレクトリを変え、@code{safe_mysqld} を起動します。 もし標準以外にインストールしているバイナリ配布を使用しているなら、 @code{mysql.server} を編集する必要があるかもしれません。 @code{safe_mysqld} を起動する前に正しいディレクトリに @code{cd} するように変更します。 @code{safe_mysqld} に他のオプションを与えるように @code{mysql.server} を変えても構いません。 他のユーザーで実行したい場合、この節の後で示すように、適切な @code{user} 行を @file{/etc/my.cnf} ファイルに追加してください。 @code{mysql.server stop} はサーバーにシグナルを送ってサーバーを停止します。 You can also take down the server manually by executing @code{mysqladmin shutdown}. You need to add these start and stop commands to the appropriate places in your @file{/etc/rc*} files when you want to start up MySQL automatically on your server. On most current Linux distributions, it is sufficient to copy the file @code{mysql.server} into the @file{/etc/init.d} directory (or @file{/etc/rc.d/init.d} on older Red Hat systems). Afterwards, run the following command to enable the startup of MySQL on system bootup: @example shell> chkconfig --add mysql.server @end example As an alternative to the above, some operating systems also use @file{/etc/rc.local} or @file{/etc/init.d/boot.local} to start additional services on bootup. To start up MySQL using this method, you could append something like the following to it: @example /bin/sh -c 'cd /usr/local/mysql ; ./bin/safe_mysqld --user=mysql &' @end example @cindex changing socket location グローバル設定ファイルである @file{/etc/my.cnf} に、 @code{mysql.server} の オプションを記述することも可能です。@file{/etc/my.cnf} ファイルは以下のような 記述になっています： @example [mysqld] datadir=/usr/local/mysql/var socket=/var/tmp/mysql.sock port=3306 user=mysql [mysql_server] basedir=/usr/local/mysql @end example @code{mysql.server} スクリプトは次のオプションを理解します: @code{datadir}, @code{basedir} そして @code{pid-file}. 次の表は、各起動スクリプトがオプションファイルからどのオプショングループを読み込むかを示しています: @multitable @columnfractions .15 .35 @item @strong{Script} @tab @strong{Option groups} @item @code{mysqld} @tab @code{mysqld} and @code{server} @item @code{mysql.server} @tab @code{mysql.server}, @code{mysqld}, and @code{server} @item @code{safe_mysqld} @tab @code{mysql.server}, @code{mysqld}, and @code{server} @end multitable @xref{Option files}. @node Upgrade, Operating System Specific Notes, Post-installation, Installing @section MySQL のアップグレード/ダウングレード @cindex upgrading @cindex downgrading MySQL 形式とデータファイルは、MySQL が同じベースバージョ ンである限り、同じアーキテクチャ上の異なるバージョン間でいつでも移動でき ます。現在のベースバージョンは 3 です。MySQL の実行時に キャラクタ・セットが変更された場合(これはソート順も変更します)、全てのテーブル に @code{myisamchk -r -q --set-character-set=charset} を行なう必要があります。 そうしなければ、インデックスが正しい順になりません。 もしあなたが神経質だったり新しいバージョンを恐れている場合、いつでもあな たの古い @code{mysqld} を @code{mysqld-old-version-number} のような何 かにリネームできます。もし新しい @code{mysqld} が予期せぬ何かを行った場 合、単純にそれをシャットダウンし、古い @code{mysqld} を再起動することが できます！ アップグレード時には、もちろん、古いデータベースをバックアップもしておく べきです。 アップグレード後、再コンパイルされたクライアントプログラムで、 @code{Commands out sync} や予期せぬコアダンプのような問題が起きる場合、 おそらく、プログラムのコンパイル時に古いヘッダやライブラリファイルを使用 したのでしょう。この場合、@file{mysql.h} ファイルと @file{libmysql.a} ラ イブラリが、新しい MySQL 配布からのものであるかどうかを確かめる ために、日付をチェックすべきです。もし違っていれば、プログラムを再コンパ イルしてください！ もし新しい @code{mysqld} サーバーが起動できないとか、パスワード無しで 接続できないとか、いくつかの問題が発生した場合、以前のインストールでできた 古い @file{my.cnf} ファイルがあるかどうかを確認してください！ @code{program-name --print-defaults} で確認できます. もしこの出力が プログラムの名称以外の物を返した場合、有効になっている @code{my.cnf} ファイルが あります！ 新しいリリースの MySQL をインストールした場合に常に @code{Msql-Mysql-modules} を再構築、再インストールすることは いい考えです。すべての @code{DBI} スクリプトが MySQL の アップグレード後にコアダンプする兆候に気づいた場合は、特に そうしてください。 @menu * Upgrading-from-4.0:: Upgrading from a 4.0 version to 4.1 * Upgrading-from-3.23:: Upgrading from a 3.23 version to 4.0 * Upgrading-from-3.22:: Upgrading from a 3.22 version to 3.23 * Upgrading-from-3.21:: Upgrading from a 3.21 version to 3.22 * Upgrading-from-3.20:: Upgrading from a 3.20 version to 3.21 * Upgrading-to-arch:: Upgrading to another architecture @end menu @cindex compatibility, between MySQL versions @cindex upgrading, 4.0 to 4.1 @node Upgrading-from-4.0, Upgrading-from-3.23, Upgrade, Upgrade @subsection Upgrading From Version 4.0 to Version 4.1 In general what you have to do when upgrading to 4.1 from an earlier MySQL version: @itemize @item Run the script @code{mysql_fix_privilege_tables} to generate the new password field that is needed for secure handling of passwords. @end itemize The following is a more complete lists tell what you have to watch out for when upgrading to version 4.1; @itemize @item Functions that return a DATE, DATETIME or TIME result is now fixed up when returned to the client. @example mysql> SELECT cast("2001-1-1" as DATE) -> '2001-01-01' @end example @item All column and tables now have a character set, which shows up in @code{SHOW CREATE TABLE} and @code{mysqldump}. (MySQL 4.0.6 and above can read the new dump files, but not previous MySQL versions). @item Timestamp is now returned as string of type @code{'YYYY-MM-DD HH:MM:DD'}. If you want to have this as a number you should add +0 to the timestamp column. Different timestamp lengths are not supported. @item If you are running multiple servers on the same windows machine, you should use a different @code{--shared_memory_base_name} option on all machines. @end itemize @strong{Note} that the table definition format (.frm) has changed slightly in 4.1. MySQL 4.0.11 can read the new .frm format but older version can not. If you need to go move tables from 4.1 to and earlier MySQL version you should use @code{mysqldump}. @xref{mysqldump}. @cindex compatibility, between MySQL versions @cindex upgrading, 3.23 to 4.0 @node Upgrading-from-3.23, Upgrading-from-3.22, Upgrading-from-4.0, Upgrade @subsection バージョン 3.23 から バージョン 4.0 へのアップグレード In general what you have to do when upgrading to 4.0 from an earlier MySQL version: @itemize @item Run the script @code{mysql_fix_privilege_tables} to add new privileges and features to the MySQL privilege tables. @item Edit any MySQL startup scripts or configure files to not use any of the deprecated options listed below. @item Convert your old ISAM files to MyISAM files with the command: @code{mysql_convert_table_format database}. Note that this should only be run if all tables in the given database is ISAM or MyISAM tables. If this is not the case you should run @code{ALTER TABLE table_name TYPE=MyISAM} on all ISAM tables. @item Ensure that you don't have any MySQL clients that uses shared libraries (like the Perl Msql-Mysql-modules). If you have, you should recompile them as structures used in @file{libmysqlclient.so} have changed. @end itemize MySQL 4.0 will work even if you don't do the above, but you will not be able to use the new security privileges that MySQL 4.0 and you may run into problems when upgrading later to MySQL 4.1 or newer. The ISAM file format still works in MySQL 4.0 but it's deprecated and will be disabled in MySQL 5.0. 古いクライアントは、4.0 のサーバ と問題なく動作するはずです。 Even if you do the above, you can still downgrade to MySQL 3.23.52 or newer if you run into problems with the MySQL 4.0 series. In this case you have to do a @code{mysqldump} of any tables using a full-text index and restore these in 3.23 (because 4.0 uses a new format for full-text index). 次のリストは、バージョン 4.0 にアップグレードする際に気をつけなければなら ないことです; @itemize @bullet @item MySQL 4.0 has a lot of new privileges in the @code{mysql.user} table. @xref{GRANT}. To get these new privileges to work, one must run the @code{mysql_fix_privilege_tables} script. Until this script is run all users have the @code{SHOW DATABASES}, @code{CREATE TEMPORARY TABLES}, and @code{LOCK TABLES} privileges. @code{SUPER} and @code{EXECUTE} privileges take their value from @code{PROCESS}. @code{REPLICATION SLAVE} and @code{REPLICATION CLIENT} take their values from @code{FILE}. If you have any scripts that creates new users, you may want to change them to use the new privileges. If you are not using @code{GRANT} commands in the scripts, this is a good time to change your scripts. In version 4.0.2 the option @code{--safe-show-database} is deprecated (and no longer does anything). @xref{Privileges options}. If you get access denied errors for new users in version 4.0.2, you should check if you need some of the new grants that you didn't need before. In particular, you will need @code{REPLICATION SLAVE} (instead of @code{FILE}) for new slaves. @item The startup parameters @code{myisam_max_extra_sort_file_size} and @code{myisam_max_extra_sort_file_size} are now given in bytes (was megabytes before 4.0.3). External system locking of MyISAM/ISAM files is now turned off by default. One can turn this on by doing @code{--external-locking}. (For most users this is never needed). @item The following startup variables/options have been renamed: @multitable @columnfractions .50 .50 @item @strong{From} @tab @strong{to}. @item @code{myisam_bulk_insert_tree_size} @tab @code{bulk_insert_buffer_size} @item @code{query_cache_startup_type} @tab @code{query_cache_type} @item @code{record_buffer} @tab @code{read_buffer_size} @item @code{record_rnd_buffer} @tab @code{read_rnd_buffer_size} @item @code{sort_buffer} @tab @code{sort_buffer_size} @item @code{warnings} @tab @code{log-warnings} @item @code{err-log} @tab @code{--log-error} (for @code{mysqld_safe}) @end multitable The startup options @code{record_buffer}, @code{sort_buffer} and @code{warnings} will still work in MySQL 4.0 but are deprecated. @item The following SQL variables have changed name. @c arjen note: New table, not yet measured for O'Reilly/DocBook. @multitable @columnfractions .50 .50 @item @strong{From} @tab @strong{To}. @item @code{SQL_BIG_TABLES} @tab @code{BIG_TABLES} @item @code{SQL_LOW_PRIORITY_UPDATES} @tab @code{LOW_PRIORITY_UPDATES} @item @code{SQL_MAX_JOIN_SIZE} @tab @code{MAX_JOIN_SIZE} @item @code{SQL_QUERY_CACHE_TYPE} @tab @code{QUERY_CACHE_TYPE} @end multitable The old names still work in MySQL 4.0 but are deprecated. @item You have to use @code{SET GLOBAL SQL_SLAVE_SKIP_COUNTER=#} instead of @code{SET SQL_SLAVE_SKIP_COUNTER=#}. @item Renamed mysqld startup options @code{--skip-locking} to @code{--skip-external-locking} and @code{--enable-locking} to @code{--external-locking}. @item @code{SHOW MASTER STATUS} now returns an empty set if binary log is not enabled. @item @code{SHOW SLAVE STATUS} now returns an empty set if slave is not initialised. @item mysqld now has the option @code{--temp-pool} enabled by default as this gives better performance with some OS (Most notable Linux). @item @code{DOUBLE} and @code{FLOAT} columns now honour the @code{UNSIGNED} flag on storage (before, @code{UNSIGNED} was ignored for these columns). @item @code{ORDER BY column DESC} now always sorts @code{NULL} values first; in 3.23 this was not always consistent. Note: MySQL 4.0.11 restored the original behaviour. @item @code{SHOW INDEX} has 2 columns more (@code{Null} and @code{Index_type}) than it had in 3.23. @item @code{CHECK}, @code{SIGNED}, @code{LOCALTIME} and @code{LOCALTIMESTAMP} are now reserved words. @item The result of all bitwise operators @code{|}, @code{&}, @code{<<}, @code{>>}, and @code{~} is now unsigned. This may cause problems if you are using them in a context where you want a signed result. @xref{Cast Functions}. @item @strong{Note}: when you use subtraction between integer values where one is of type @code{UNSIGNED}, the result will be unsigned! In other words, before upgrading to MySQL 4.0, you should check your application for cases where you are subtracting a value from an unsigned entity and want a negative answer or subtracting an unsigned value from an integer column. You can disable this behaviour by using the @code{--sql-mode=NO_UNSIGNED_SUBTRACTION} option when starting @code{mysqld}. @xref{Cast Functions}. @item @code{MATCH ... AGAINST (... IN BOOLEAN MODE)} を使用するためには、 @code{REPAIR TABLE table_name USE_FRM} を実行してテーブルをリビルド する必要があります。 たとえ テーブルの型が @code{MyISAM} であったとしても。 @item @code{LOCATE()} と @code{INSTR()} はケース依存です。 もしいずれかの引数がバイナリ文字列ならば。Otherwise they are case-insensitive. @item @code{STRCMP()} now uses the current character set when doing comparisons, which means that the default comparison behaviour now is case-insensitive. @item @code{HEX(string)} は、与えられた `文字列' を、 16進数で表記しなおした `文字列' を返すようになりました。 もし、`数値'の16進表記を得たい場合は、 @code{HEX()} の引数は 数値にしなくてはなりません。 (訳注： 4.0ではこうなります. (EUC-JP) @example mysql> select HEX("xyz"),HEX("あ"),HEX("16"),HEX(16); +------------+-----------+-----------+---------+ | HEX("xyz") | HEX("あ") | HEX("16") | HEX(16) | +------------+-----------+-----------+---------+ | 78797A | A4A2 | 3136 | 10 | +------------+-----------+-----------+---------+ @end example これが、3.23ではこうなっていました. @example mysql> select HEX("xyz"),HEX("あ"),HEX("16"),HEX(16); +------------+-----------+-----------+---------+ | HEX("xyz") | HEX("あ") | HEX("16") | HEX(16) | +------------+-----------+-----------+---------+ | 0 | 0 | 10 | 10 | +------------+-----------+-----------+---------+ @end example ) @item 3.23 では @code{INSERT INTO ... SELECT} は常に @code{IGNORE} が有効になっ ていました。4.0.1 では、@code{IGNORE} を記述しない場合、MySQL はエラーの場 合に停止します(そして、おそらくロールバックします)。 @item ！！！@file{safe_mysqld} は @file{mysqld_safe} に名前が変わりました！！！ For some time we will in our binary distributions include @code{safe_mysqld} as a symlink to @code{mysqld_safe}. @item 古い C API 関数 @code{mysql_drop_db}, @code{mysql_create_db}, @code{mysql_connect} は、もう、サポートされなくなりました。 ただし、MySQL を @code{CFLAGS=-DUSE_OLD_FUNCTIONS} フラグでコンパイルすれば、まだ使うことはできます。 しかし、このフラグを使用する代わりに クライアントを新しい 4.0 API に変更する方が良いです。 @item @code{MYSQL_FIELD} 構造体では、 @code{length} と @code{max_length} が @code{unsigned int} から @code{unsigned long} に変更されました。 これを @code{printf()} 形式関数に使用する場合にいくつかの警告が出ること以 外は、問題は発生しません。 @item テーブルから全レコードを削除したくて、何レコードが削除されたかを気にしない 時には、@code{TRUNCATE TABLE} を使用すべきです。(なぜなら @code{TRUNCATE TABLE} は @code{DELETE FROM table_name} よりも速いからです)。 @item @code{TRUNCATE TABLE} や @code{DROP DATABASE} の実行時に、有効な @code{LOCK TABLES} やトランザクションがある場合、エラーになります。 @item BIGINT フィールドに値を格納する場合に整数を使用すべきです(MySQL 3.23 で行 なっていた文字列を使用する代わりに)。文字列でもまだ働きますが、整数の使用 の方がより効率的です。 @item @code{SHOW OPEN TABLE} のフォーマットが変更されました。 @item マルチスレッドのクライアントは、@code{mysql_thread_init()} と @code{mysql_thread_end()} を使用せねばなりません。 @xref{Threaded clients}. @item Perl DBD::mysql をコンパイルし直す場合は、 Msql-Mysql-modules version 1.2218 以上のものでなくてはなりません。 古い DBD モジュールは推奨されない @code{drop_db()} 呼び出しを使用している ためです。 @item @code{RAND(seed)} は、3.23 に比べて、より違ったランダムを返すようになりました。 これは @code{RAND(seed)} と @code{RAND(seed+1)} により違いがでるという事です。 @item The default type returned by @code{IFNULL(A,B)} is now set to be the more 'general' of the types of @code{A} and @code{B}. (The order is @code{STRING}, @code{REAL} or @code{INTEGER}). @end itemize @node Upgrading-from-3.22, Upgrading-from-3.21, Upgrading-from-3.23, Upgrade @subsection バージョン 3.22 から バージョン 3.23 へのアップグレード @cindex compatibility, between MySQL versions @cindex upgrading, 3.22 to 3.23 MySQL バージョン 3.23 は新しい @code{MyISAM} 型のテーブルと、 古い @code{ISAM} 型のテーブルをサポートします。 バージョン 3.23 を使用する際、古いテーブル(ISAM) を変換する必要はありません。 デフォルトでは、新しく作られるテーブルが @code{MyISAM} 型になります。 (これは @code{mysqld} を @code{--default-table-type=isam} オプションで 起動することにより、変更できます)。 @code{ISAM} テーブルを @code{MyISAM} に変更するには、 @code{ALTER TABLE table_name TYPE=MyISAM} を使用するか、@code{mysql_convert_table_format} perl スクリプトを使用します。 バージョン 3.22 と バージョン 3.21 のクライアントは問題なく バージョン 3.23 サーバーで動作します。 以下に、バージョン 3.23 にアップグレードするときに、注目する必要があるものを列挙します： @itemize @bullet @item @code{tis620} 文字セットを使用しているすべてのテーブルを @code{myisamchk -r} または @code{REPAIR TABLE} で fix する必要があります。 @item シンボリックリンクされたデータベースに対し @code{DROP DATABASE} を行なう場 合は、リンクとオリジナルデータベースが削除されます。(3.22 では configure が @code{readlink} システムコールを検出しないため、これは起りません。) @item @code{OPTIMIZE TABLE} は現在、@code{MyISAM} テーブルだけに動作します。他 のテーブル型については、@code{ALTER TABLE} を使用して、テーブルを最適化で きます。@code{OPTIMIZE TABLE} の間は、テーブルは他のスレッドからロックされ ます。 @item MySQL クライアント @code{mysql} は現在、デフォルトで @code{--no-named-commands (-g)} オプションで起動されます。このオプションは @code{--enable-named-commands (-G)} で無効にできます。これは、非互換問題を 引き起こす場合があります。たとえば、セミコロン無しの named command を使用 する SQL スクリプトです！ 長い形式のコマンドは行頭でまだ動作します。 @item Date functions that work on parts of dates (like @code{MONTH()}) will now return 0 for @code{0000-00-00} dates. (MySQL 3.22 returned @code{NULL}.) @item @code{german} 文字ソート順を使用する場合、ソート順についていくつか変更され ているので、@code{isamchk -r} ですべてのテーブルを修復する必要があります！ @item @code{IF} のデフォルトの戻り値型は現在両方の引数に依存します。最初の引数だけではありません。 @item @code{AUTO_INCREMENT} は負数では働きません。 この理由は、負数は -1 から 0 へのラッピング時に問題を引き起こすためです。 MyISAM の @code{AUTO_INCREMENT} は現在、低レベルの部分で処理され、以 前よりとても速いです。MyISAM テーブルでは、テーブルからいくつかのレコード を削除したとしても、古い数値は再利用されません。 @item @code{CASE}, @code{DELAYED}, @code{ELSE}, @code{END}, @code{FULLTEXT}, @code{INNER}, @code{RIGHT}, @code{WHEN} は 予約語になりました。 @item @code{FLOAT(X)} は本当の浮動小数点型になりました。桁数固定の値ではありません。 @item @code{DECIMAL(length,dec)} 宣言時、length 引数はもはや符号や小数点の場所を含みません。 @item @code{TIME} 文字列は以下のフォーマットのいずれかでなければなりません： @code{[[[DAYS] [H]H:]MM:]SS[.fraction]} か @code{[[[[[H]H]H]H]MM]SS[.fraction]}. @item @code{LIKE} は、同一文字の比較 @code{'='} ルールを使用して、 比較を行うようになりました。 もし古い比較方法にするならば、 MySQL を @code{CXXFLAGS=-DLIKE_CMP_TOUPPER} フラグでコンパイルします。 @item @code{REGEXP} は、通常の文字列(非 binary) では、ケース非依存になりました。 @item @code{MyISAM} テーブル(@code{.MYI}) の検査・修復には、@code{CHECK TABLE} を使用するか、@code{myisamchk} を使用します。 @code{isamchk} は ISAM(@code{.ISM}) テーブル用に使用します。 @item もし、バージョン 3.22 と バージョン 3.23 の間で互換性を持たせて @code{mysqldump} を行いたいならば、 @code{--opt} や @code{--all} オプションを @code{mysqldump} に指定してはいけません。 @item 全ての @code{DATE_FORMAT()} をチェックしてください。 各フォーマット文字の前には @samp{%} 文字が必要になりました。 (MySQL 3.22 バージョン以降ではこの文法が許されます。) @item @code{mysql_fetch_fields_direct} が関数になり (今まではマクロだったのが)、 @code{MYSQL_FIELD} 型ではなく @code{MYSQL_FIELD} ポインター型を返します。 @item @code{mysql_num_fields()} は、 @code{MYSQL*} object をもはや使うことができません。 (これは今、 @code{MYSQL_RES*} を引数に取る関数になりました)。 代わりに、 @code{mysql_field_count()} を使用すべきです。 @item @code{MySQL} バージョン 3.22 では, @code{SELECT DISTINCT ...} の出力は ほとんどいつもソートされました。 3.23 では, ソートを行った結果を得るには @code{GROUP BY} か @code{ORDER BY} を使用しなくてはなりません。 @item もし、一致するレコードが無かった場合、@code{SUM()} は 0 の代わりに @code{NULL} を返すようになりました。 これは ANSI SQL 準拠です。 @item @code{NULL} 値での @code{AND} や @code{OR} は現在 0 ではなく @code{NULL} を返します。 これは主に、@code{NOT NULL} = @code{NULL} として、@code{AND/OR} 式上で @code{NOT} を使用するクエリに影響します。@code{LPAD()} と @code{RPAD()} は 長さ引数よりも長い場合、結果文字列は短くなります。 @end itemize @node Upgrading-from-3.21, Upgrading-from-3.20, Upgrading-from-3.22, Upgrade @subsection バージョン 3.21 から バージョン 3.22 へのアップグレード @cindex compatibility, between MySQL versions @cindex upgrading, 3.21 to 3.22 バージョン 3.21 と バージョン 3.22 の間には互換性に影響する変更はありません。 @code{DATE} 型のフィールドを持たせて作成した新しいテーブルは、 日付の格納に新しい方法を使用することだけが、唯一の落とし穴です。 これらの新しいフィールドに古いバージョンの @code{mysqld} からアクセスすることはできません。 @code{MySQL} バージョン 3.22 インストール後、新しいサーバを開始して、 @code{mysql_fix_privilege_tables} スクリプトを実行すべきです。これは @code{GRANT} コマンドを使用するために必要な権限を追加します。これを忘れ ると、@code{ALTER TABLE} 、@code{CREATE INDEX}、@code{DROP INDEX} を 使用しようとした時に @code{Access denied} になります。 MySQL root ユーザがパスワードを要求する場合、 @code{mysql_fix_privilege_tables} への引数としてそれを与えてください。 C API インタフェース @code{mysql_real_connect()} は変更されました。この 関数を呼び出す古いクライアントプログラムを持っている場合は、新しい @code{db} 引数に @code{0} を置く(またはより速い接続のために @code{db} 要 素を送るようにクライアントをコーディングしなおす)必要があります。 @code{mysql_real_connect()} を呼び出す前に @code{mysql_init()} を呼ばなくてはなりません！ この変更は、@code{MYSQL} の構造体にオプションを保存するための 新しい @code{mysql_options()} 関数を有効にします。 @code{mysqld} 変数 @code{key_buffer} は @code{key_buffer_size} に名前が 変わりました。しかし、まだ前の名前もスターとアップファイル中で使用できま す。 @node Upgrading-from-3.20, Upgrading-to-arch, Upgrading-from-3.21, Upgrade @subsection バージョン 3.20 から バージョン 3.21 へのアップグレード @cindex upgrading, 3.20 to 3.21 既に バージョン 3.20.28 より前のバージョンが稼働していて、バージョン 3.21.x に変更したい場合は、 次を行なう必要があります: @code{safe_mysqld --old-protocol} で @code{mysqld} 3.21 サーバを起動すれ ば、バージョン 3.20 配布からのクライアントでそれを使用できます。この場合、新しいク ライアント関数 @code{mysql_errno()} はサーバのエラーは何も返さず、 @code{CR_UNKNOWN_ERROR} だけを返します (ただしクライアントのエラーについ ては働きます)。そして サーバは古い @code{password()} チェックを新しいものの代わ りに使用します。 @code{mysqld} に @code{--old-protocol} オプションを@emph{使わない}場合、 次の変更をする必要があります: @itemize @bullet @item 全てのクライアントコードは再コンパイルする必要があります。ODBC を使用し ている場合は新しい @strong{MyODBC} 2.x ドライバを入手する必要があります。 @item @code{mysql.user} テーブル内の @code{password} フィールドを @code{CHAR(16)} に変換するために、スクリプト @code{scripts/add_long_password} を実行する必要があります。 @item 全てのパスワードは @code{mysql.user} テーブル内に再配置する必要がありま す(31ビットパスワードの代わりに、62ビットを得るために)。 @item テーブル形式は変更されていないので、どのテーブルも変換する必要はありませ ん。 @end itemize MySQL バージョン 3.20.28 とそれ以降は、クライアントに影響を及ぼさずに、新 しい @code{user} テーブル形式を処理することができます。バージョン 3.20.28 より前の MySQL バージョンを持っている場合は、@code{user} テーブルを変換 すると、パスワードはその上ではもう働きません。安全のため、最初に少なくと も バージョン 3.20.28 にアップグレードし、それから バージョン 3.21.x に アップグレードすべきです。 @cindex Protocol mismatch 新しいクライアントコードは バージョン 3.20.x @code{mysqld} サーバで動作するので、 もし バージョン 3.21.x で問題があった場合は、クライアントをもう一度再コンパイルする必 要はなく、古い バージョン 3.20.x サーバを使用することができます。 @code{mysqld} に @code{--old-protocol} オプションを使用しない場合、古い クライアントはエラーメッセージを発します: @example ERROR: Protocol mismatch. Server Version = 10 Client Version = 9 @end example 新しい Perl インタフェース @code{DBI}/@code{DBD} は古い @code{mysqlperl} インタフェースもサポートします。@code{mysqlperl} を使用する場合に行う必 要のある変更は、@code{connect()} 関数の引数の変更だけです。新しい引数は: @code{host}, @code{database}, @code{user}, @code{password} (@code{user} と @code{password} 引数の順番が変更されました)。 @xref{Perl DBI Class, , Perl @code{DBI} Class}. 次の変更は古いアプリケーションでのクエリに影響します: @itemize @bullet @item @code{HAVING} は現在 @code{ORDER BY} 節より前になければいけません。 @item @code{LOCATE()} へのパラメータは交換されました。 @item 新しい予約語がいくつかあります。最も注意すべきは @code{DATE}, @code{TIME} そして @code{TIMESTAMP} です。 @end itemize @node Upgrading-to-arch, , Upgrading-from-3.20, Upgrade @subsection 他のアーキテクチャへのアップグレード @cindex upgrading, different architecture もし、MySQL バージョン 3.23 を使用しているならば、 違うアーキテクチャのマシンに、@code{.frm}, @code{.MYI},@code{.MYD} ファイルを コピーすることが出来ます。 ただし、両者間で、同じ浮動小数点のフォーマットをサポートしている場合に限ります。 (MySQL はどのようなバイト交換にも気をつけます)。 現在 MySQL @code{ISAM} データファイルとインデックスファイル ( @file{*.ISD} と @file{*.ISM} ファイル) はアーキテクチャ依存で、 いくつかのケースでは OS 依存です。 アプリケーションを、現在のマシンとは異なるアーキテクチャ/OS を 持つ他のマシンに移したい場合は、単純にファイルを他のマシンにコピーするこ とでデータベースを移行しようとすべきではありません。@code{mysqldump} を 使用すべきです。 デフォルトでは @code{mysqldump} は、完全な SQL ステートメントファイルを 生成します。それからそのファイルを他のマシンへ転送し、@code{mysql} クラ イアントへの入力として与えることができます。 有効なオプションが何かを見るためには、@code{mysqldump --help} を試してく ださい。データを MySQL のより新しいバージョンに移す場合、速くコ ンパクトなダンプを得るために、より新しいバージョンで @code{mysqldump --opt} を使用すべきです。 ２つのマシン間でデータベースを移動する最も簡単な (しかし最も速くはない) 方法は、データベースが置かれているマシン上で次のコマンドを実行することで す: @example shell> mysqladmin -h 'other hostname' create db_name shell> mysqldump --opt db_name \ | mysql -h 'other hostname' db_name @end example 遅いネットワーク上でリモートマシンからデータベースをコピーしたい場合は、 次を使用できます: @example shell> mysqladmin create db_name shell> mysqldump -h 'other hostname' --opt --compress db_name \ | mysql db_name @end example You can also store the result in a file, then transfer the file to the target machine and load the file into the database there. For example, you can dump a database to a file on the source machine like this: @example shell> mysqldump --quick db_name | gzip > db_name.contents.gz @end example (The file created in this example is compressed.) データベースの中身を含んでいるファイルを、目的のマシンに転送して、次のコ マンドを実行してください: @example shell> mysqladmin create db_name shell> gunzip < db_name.contents.gz | mysql db_name @end example @cindex @code{mysqldump} @cindex @code{mysqlimport} データベース転送を実行するために、@code{mysqldump} と @code{mysqlimport} も使用できます。大きなテーブルでは、これは単純な @code{mysqldump} の使用 よりもとても速いです。次に示すコマンドでは、@code{DUMPDIR} は @code{mysqldump} からの出力を格納するために使用するディレクトリの完全な パス名を表わしています。 まず、出力ファイルのためのディレクトリを作成して、データベースをダンプし ます: @example shell> mkdir DUMPDIR shell> mysqldump --tab=DUMPDIR db_name @end example それから、@code{DUMPDIR} ディレクトリ内のファイルを目的のマシン上の対応 するディレクトリに転送し、MySQL にファイルをロードします: @example shell> mysqladmin create db_name # create database shell> cat DUMPDIR/*.sql | mysql db_name # create tables in database shell> mysqlimport db_name DUMPDIR/*.txt # load data into tables @end example @code{mysql} データベースのコピーも忘れないでください。それは承認テーブ ル (@code{user}, @code{db}, @code{host}) が格納されるためです。 @code{mysql} データベースをその場所に置くまで、新しいマシン上では MySQL @code{root} ユーザとしてコマンドを実行する必要があります。 新しいマシン上へ @code{mysql} データベースを導入した後、サーバが承認テー ブル情報を再ロードするために、@code{mysqladmin flush-privileges} を実行してください。 @node Operating System Specific Notes, Perl support, Upgrade, Installing @section Operating System Specific Notes @menu * Linux:: Linux Notes (All Linux Versions) * Windows:: Windows Notes * Solaris:: Solaris Notes * BSD Notes:: BSD Notes * Mac OS X:: Mac OS X Notes * Other Unix Notes:: Other Unix Notes * OS/2:: OS/2 Notes * BeOS:: BeOS Notes * Novell Netware:: Novell NetWare Notes @end menu @node Linux, Windows, Operating System Specific Notes, Operating System Specific Notes @subsection Linux Notes (All Linux Versions) @menu * Binary notes-Linux:: Linux Notes for Binary Distributions * Linux-x86:: Linux x86 Notes * Linux-SPARC:: Linux SPARC Notes * Linux-Alpha:: Linux Alpha Notes * Linux-PowerPC:: Linux PowerPC Notes * Linux-MIPS:: Linux MIPS Notes * Linux-IA64:: Linux IA64 Notes @end menu 以下の注意は、@strong{glibc} に関して、MySQL をあなた自身で作成す るシチュエーションだけに適用されます。Linux を x86 マシンで実行する場合、 多くの場合は我々のバイナリを使用した方が良いです。我々は @strong{glibc} の 最良パッチバージョンと我々のバイナリをリンクします。我々は最良のコンパイラ オプションでそれを作成し、高負荷サーバについて適切になるように試みています。 以下のテキストを読んで、何をあなたがやるべきかについて迷った時は、あなたの 必要にかなうかどうかをみるために、我々のバイナリをまず試してください。そし て、我々のバイナリが十分でないとわかった後にだけ、あなた自身の作成について 考えてください。この場合、それについての評価します。そのため、次回にはより 良いバイナリを作成できます。典型的なユーザについて、そして、多くの同時接続 と 2G Bytes 制限を超えるテーブルを設定する場合でも、多くの場合、我々のバイナリ は最良の選択です。 Linux では MySQL は LinuxThreads を使用します。 もし @code{glibc2} を持たない古い Linux を使用している場合、 MySQL のコンパイルの前に、 LinuxThreads をインストールしなければなりません。 LinuxThreads は @uref{http://www.mysql.com/downloads/os-linux.html}. から得ることが できます。 @strong{注意:} 我々は SMP システム上での Linux 2.2.14 と MySQL で奇妙な問 題を経験しました; SMP システムの場合、Linux 2.4 ASAP にアップグレードする ことをお勧めします！ これを行なうことで、あなたのシステムはより速くより安 定するでしょう！ 注意: 2.1.1 以前の @code{glibc} バージョンは @code{pthread_mutex_timedwait} 処理に致命的なバグがあります。これは @code{INSERT DELAYED} を行なう時に使用されます。glibc をアップグレードする 前に @code{INSERT DELAYED} は使用しないようにお奨めします。 1000以上の同時接続を使用する予定であれば、LinuxThreads にいくつかの変更 をして、再コンパイルし、MySQL を新しい @file{libpthread.a} を使用するように再リ ンクする必要があります。@file{sysdeps/unix/sysv/linux/bits/local_lim.h} 内の @code{PTHREAD_THREADS_MAX} を 4096 に増加し、 @file{linuxthreads/internals.h} 中の @code{STACK_SIZE} を 256 KB に減少させてください。注意: @code{STACK_SIZE} がデフォルトの 2MB である 場合、MySQL は 600-1000 程度の接続で安定でなくなります。 MySQL が十分なファイルをオープンまたは接続できないという問題を 得た場合、十分なファイルを操作するように構築された Linux を持っていない ということです。 Linux 2.2 以降では、割り当てられたファイル記述子の数を次のようにしてチェッ クできます: @example cat /proc/sys/fs/file-max cat /proc/sys/fs/dquot-max cat /proc/sys/fs/super-max @end example 16M 以上のメモリがある場合は、次のような何かを起動スクリプト(SuSE では @file{/etc/init.d/boot.local})に追加すべきです: @example echo 65536 > /proc/sys/fs/file-max echo 8192 > /proc/sys/fs/dquot-max echo 1024 > /proc/sys/fs/super-max @end example 上記は、root でコマンドラインからも実行できますが、この場合、コンピュータ をリブートすると古い制限が使われます。 You can also run the preceding commands from the command-line as root, but these settings will be lost the next time your computer reboots. Alternatively, you can set these parameters on bootup by using the @code{sysctl} tool, which is used by many Linux distributions (SuSE has added it as well, beginning with SuSE Linux 8.0). Just put the following values into a file named @file{/etc/sysctl.conf}: @example # Increase some values for MySQL fs.file-max = 65536 fs.dquot-max = 8192 fs.super-max = 1024 @end example @file{/etc/my.cnf} にも追加すべきです: @example [safe_mysqld] open-files-limit=8192 @end example 上記は MySQL に、最大 8192 接続/ファイルを生成することを許可します。 The @code{STACK_SIZE} constant in LinuxThreads controls the spacing of thread stacks in the address space. It needs to be large enough so that there will be plenty of room for the stack of each individual thread, but small enough to keep the stack of some threads from running into the global @code{mysqld} data. Unfortunately, the Linux implementation of @code{mmap()}, as we have experimentally discovered, will successfully unmap an already mapped region if you ask it to map out an address already in use, zeroing out the data on the entire page, instead of returning an error. So, the safety of @code{mysqld} or any other threaded application depends on the "gentleman" behaviour of the code that creates threads. The user must take measures to make sure the number of running threads at any time is sufficiently low for thread stacks to stay away from the global heap. With @code{mysqld}, you should enforce this "gentleman" behaviour by setting a reasonable value for the @code{max_connections} variable. If you build MySQL yourself and do not want to mess with patching LinuxThreads, you should set @code{max_connections} to a value no higher than 500. It should be even less if you have a large key buffer, large heap tables, or some other things that make @code{mysqld} allocate a lot of memory, or if you are running a 2.2 kernel with a 2G patch. If you are using our binary or RPM version 3.23.25 or later, you can safely set @code{max_connections} at 1500, assuming no large key buffer or heap tables with lots of data. The more you reduce @code{STACK_SIZE} in LinuxThreads the more threads you can safely create. We recommend the values between 128K and 256K. 多くの同時接続を使用したい場合は、fork 爆弾攻撃を避けようとして、子供の fork や複製について、プロセスにペナルティを課すという、バージョン 2.2 カー ネルの "機能" に悩まされるでしょう。これにより、あなたが並行クライアントの 数を増加するようには、MySQL がスケールしません。シングル CPU システムでは、 とても遅いスレッド生成で明らかにこれが見られます。これは、MySQL への接続に 長い時間(1分程度)が掛かり、それを切断するのにも長い時間掛かるということを 意味します。複数 CPU システムでは、クライアント数の増加に従って、クエリ速 度が徐々に落ちていくのが観測されました。問題の解決を見つけようとする処理の 中で、我々のユーザからカーネルパッチを受け取りました。我々はいくつかの限定 されたテストで、このパッチが MySQL のスケーラビリティを非常に改善した結果 を得ました。このパッチはここにあります @uref{http://www.mysql.com/Downloads/Patches/linux-fork.patch}. We have now done rather extensive testing of this patch on both development and production systems. It has significantly improved @code{MySQL} performance without causing any problems and we now recommend it to our users who are still running high-load servers on 2.2 kernels. This issue has been fixed in the 2.4 kernel, so if you are not satisfied with the current performance of your system, rather than patching your 2.2 kernel, it might be easier to just upgrade to 2.4, which will also give you a nice SMP boost in addition to fixing this fairness bug. We have tested MySQL on the 2.4 kernel on a 2-CPU machine and found MySQL scales @strong{much} better@-there was virtually no slowdown on queries throughput all the way up to 1000 clients, and the MySQL scaling factor (computed as the ratio of maximum throughput to the throughput with one client) was 180%. We have observed similar results on a 4-CPU system@-virtually no slowdown as the number of clients was increased up to 1000, and 300% scaling factor. So for a high-load SMP server we would definitely recommend the 2.4 kernel at this point. We have discovered that it is essential to run @code{mysqld} process with the highest possible priority on the 2.4 kernel to achieve maximum performance. This can be done by adding @code{renice -20 $$} command to @code{safe_mysqld}. In our testing on a 4-CPU machine, increasing the priority gave 60% increase in throughput with 400 clients. We are currently also trying to collect more info on how well @code{MySQL} performs on 2.4 kernel on 4-way and 8-way systems. If you have access such a system and have done some benchmarks, please send a mail to @email{docs@@mysql.com} with the results - we will include them in the manual. There is another issue that greatly hurts MySQL performance, especially on SMP systems. The implementation of mutex in LinuxThreads in @code{glibc-2.1} is very bad for programs with many threads that only hold the mutex for a short time. On an SMP system, ironic as it is, if you link MySQL against unmodified @code{LinuxThreads}, removing processors from the machine improves MySQL performance in many cases. We have made a patch available for @code{glibc 2.1.3} to correct this behaviour (@uref{http://www.mysql.com/Downloads/Linux/linuxthreads-2.1-patch}). With @code{glibc-2.2.2} MySQL version 3.23.36 will use the adaptive mutex, which is much better than even the patched one in @code{glibc-2.1.3}. Be warned, however, that under some conditions, the current mutex code in @code{glibc-2.2.2} overspins, which hurts MySQL performance. The chance of this condition can be reduced by renicing @code{mysqld} process to the highest priority. We have also been able to correct the overspin behaviour with a patch, available at @uref{http://www.mysql.com/Downloads/Linux/linuxthreads-2.2.2.patch}. It combines the correction of overspin, maximum number of threads, and stack spacing all in one. You will need to apply it in the @code{linuxthreads} directory with @code{patch -p0 128K memory on stack for this call. This stack size is now the default on MySQL 4.0.10 and above. If you are using gcc 3.0 and above to compile MySQL, you must install the @code{libstdc++v3} library before compiling MySQL; if you don't do this you will get an error about a missing @code{__cxa_pure_virtual} symbol during linking! 古い Linux 配布物では、@code{configure} 時に以下のようなエラーが出るかもしれません： @example Syntax error in sched.h. Change _P to __P in the /usr/include/sched.h file. See the Installation chapter in the Reference Manual. @end example これは @code{_P} マクロが一つのアンダースコアしか持っていないためで、 このエラーメッセージに示されたように対処してください。 以下のようなワーニングは無視して構いません： @example mysqld.cc -o objs-thread/mysqld.o mysqld.cc: In function `void init_signals()': mysqld.cc:315: warning: assignment of negative value `-1' to `long unsigned int' mysqld.cc: In function `void * signal_hand(void *)': mysqld.cc:346: warning: assignment of negative value `-1' to `long unsigned int' @end example Debian GNU/Linux では、MySQL をマシンの起動時に立ちあげるためには、 以下のようにします： @example shell> cp support-files/mysql.server /etc/init.d/mysql.server shell> /usr/sbin/update-rc.d mysql.server defaults 99 @end example @code{mysql.server} スクリプトは MySQL をインストールした先の @file{share/mysql} directory にあります。 あるいは、MySQL のソースの中の @file{support-files} ディレクトリにあります。 @code{mysqld} がつねにスタート時にコアをはく場合、 古い @file{/lib/libc.a} を使用しているかもしれません。 @file{sql/mysqld} を消去して、新しく @code{make install} してみてください。 これはいくつかの Slackware で報告された現象です。 もし @code{mysqld} をリンクする場合に以下のようなエラーが出た場合、 @file{libg++.a} が正しくインストールされていません： @example /usr/lib/libc.a(putc.o): In function `_IO_putc': putc.o(.text+0x0): multiple definition of `_IO_putc' @end example @file{libg++.a} の使用を避けるには、 @code{configure} を以下のようにします： @example shell> CXX=gcc ./configure @end example @node Linux-SPARC, Linux-Alpha, Linux-x86, Linux @subsubsection Linux SPARC Notes いくつかの埋め込み関数, @code{readdir_r()} が壊れます。 この顕れとして、@code{SHOW DATABASES} が常に空を返します。 これは configure 後、コンパイルする前に、 @file{config.h} から @code{HAVE_READDIR_R} を取り除くことで解決します。 その他いくつかの問題は、あなたの Linux にパッチを当てる必要があります。 パッチは @uref{http://www.mysql.com/Downloads/patches/Linux-sparc-2.0.30.diff}. にあります。 このパッチは、@code{vger.rutgers.edu} にある @file{sparclinux-2.0.30.tar.gz} 用です。 (これは正式の 2.0.30 とは違います。パッチを正式2.0.30に当てないように) そして LinuxThreads Version 0.6 かそれ以上にしなくてはなりません。 @node Linux-Alpha, Linux-PowerPC, Linux-SPARC, Linux @subsubsection Linux Alpha Notes MySQL Version 3.23.12 が、Linux-Alpha 上で最初にテストされたバージョンです。 もし MySQL を Linux-Alpha 上で使用したいと考えたなら、 このバージョンより新しいものを使用します。 We have tested MySQL on Alpha with our benchmarks and test suite, and it appears to work nicely. We currently build the MySQL binary packages on SuSE Linux 7.0 for AXP, kernel 2.4.4-SMP, Compaq C compiler (V6.2-505) and Compaq C++ compiler (V6.3-006) on a Compaq DS20 machine with an Alpha EV6 processor. You can find the above compilers at @uref{http://www.support.compaq.com/alpha-tools/}). By using these compilers, instead of gcc, we get about 9-14% better performance with MySQL. Note that until MySQL version 3.23.52 and 4.0.2 we optimised the binary for the current CPU only (by using the @code{-fast} compile option); this meant that you could only use our binaries if you had an Alpha EV6 processor. Starting with all following releases we added the @code{-arch generic} flag to our compile options, which makes sure the binary runs on all Alpha processors. We also compile statically to avoid library problems. @example CC=ccc CFLAGS="-fast -arch generic" CXX=cxx \ CXXFLAGS="-fast -arch generic -noexceptions -nortti" \ ./configure --prefix=/usr/local/mysql --disable-shared \ --with-extra-charsets=complex --enable-thread-safe-client \ --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared @end example If you want to use egcs the following configure line worked for us: @example CFLAGS="-O3 -fomit-frame-pointer" CXX=gcc \ CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \ --disable-shared @end example Some known problems when running MySQL on Linux-Alpha: @itemize @bullet @item Debugging threaded applications like MySQL will not work with @code{gdb 4.18}. You should download and use gdb 5.1 instead! @item If you try linking @code{mysqld} statically when using @code{gcc}, the resulting image will core dump at start. In other words, @strong{don't} use @code{--with-mysqld-ldflags=-all-static} with @code{gcc}. @end itemize @node Linux-PowerPC, Linux-MIPS, Linux-Alpha, Linux @subsubsection Linux PowerPC Notes MySQL は最新の @code{glibc} を使用した MkLinux で動作します。 (@code{glibc} 2.0.7 でテストしました). @node Linux-MIPS, Linux-IA64, Linux-PowerPC, Linux @subsubsection Linux MIPS Notes Qube2 (Linux Mips) 上で MySQL を動作させるには、 最新の @code{glibc} ライブラリでなくてはなりません (@code{glibc-2.0.7-29C2} は動作することが分かっています)。 そして、 @code{egcs} C++ compiler (@code{egcs-1.0.2-9}, @code{gcc 2.95.2} 以上) を 使用しなくてはなりません。 @node Linux-IA64, , Linux-MIPS, Linux @subsubsection Linux IA64 Notes To get MySQL to compile on Linux IA64, we use the following compile line: Using @code{gcc-2.96}: @example CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \ "--with-comment=Official MySQL binary" --with-extra-charsets=complex @end example On IA64 the MySQL client binaries are using shared libraries. This means that if you install our binary distribution in some other place than @file{/usr/local/mysql} you need to either modify @file{/etc/ld.so.conf} or add the path to the directory where you have @file{libmysqlclient.so} to the @code{LD_LIBRARY_PATH} environment variable. @xref{Link errors}. @node Windows, Solaris, Linux, Operating System Specific Notes @subsection Windows Notes This section describes using MySQL on Windows. This information is also provided in the @file{README} file that comes with the MySQL Windows distribution. @xref{Windows installation}. @menu * Win95 start:: Starting MySQL on Windows 9x / Me * NT start:: Starting MySQL on Windows NT / 2000 / XP * Windows running:: Running MySQL on Windows * Windows and SSH:: Connecting to a remote MySQL from Windows with SSH * Windows symbolic links:: Splitting data across different disks under Win32 * Windows client compiling:: Compiling MySQL clients on Windows. * Windows vs Unix:: MySQL-Windows compared to Unix MySQL @end menu @node Win95 start, NT start, Windows, Windows @subsubsection Starting MySQL on Windows 95, 98 or Me MySQL は TCP/IP をクライアントからサーバーへの接続に使用します。 こうすればネットワーク上のどのマシンからでも MySQL サーバーに 接続できるようになります。 このため、MySQL を起動する前に、 あなたは TCP/IP をインストールしなくてはなりません。 これは Windows CD-ROM にあります。 もし古い Win95 (for example OSR2) を使用しているなら、 これは古い Winsock パッケージを使用しているかもしれません！ MySQL は Winsock 2 を要求します！ 最新の Winsock は @uref{http://www.microsoft.com/} にあります。 Win98 はデフォルトで新しい Winsock 2 ライブラリですので、 これは Win98 には当てはまりません。 @code{mysqld} サーバーを起動するには, MS-DOS を起動し、以下のように入力します： @example C:\> C:\mysql\bin\mysqld @end example これは @code{mysqld} をバックグラウンドで動かします。 MySQL サーバーの kill には： @example C:\> C:\mysql\bin\mysqladmin -u root shutdown @end example This calls the MySQL administation utility as user `root', which is the default Administrator in the MySQL grant system. Please note that the MySQL grant system is wholly independent from any login users under Windows. 注意: Win95 と Win98 は名前付パイプをサポートしていません。Win95 と Win98 では、Windows NT サーバホスト上で動いているリモートの MySQL への接続だけに、名前付パイプを使用できます。 (The MySQL server must also support named pipes, of course. For example, using @code{mysqld-opt} under NT/2000/XP will not allow named pipe connections. You should use either @code{mysqld-nt} or @code{mysqld-max-nt}.) @code{mysqld} が起動しない場合、@file{\mysql\data\mysql.err} ファイルがそ の問題の原因を示す何らかのメッセージをサーバが書き出していないかチェック してください。@code{mysqld --standalone} でサーバの起動を試みることもでき ます; この場合、問題の解決の助けになるであろう、いくつかの有用な情報が画 面上で得られます。 最後の選択肢は @code{mysqld} を @code{--standalone --debug} 付きで起動す ることです。この場合、@code{mysqld} はログをファイル @file{C:\mysqld.trace} に書き出します。これには、@code{mysqld} が何故起動 しないかの理由が含まれます。 @xref{Making trace files}. Use @code{mysqld --help} to display all the options that @code{mysqld} understands! @node NT start, Windows running, Win95 start, Windows @subsubsection Starting MySQL on Windows NT, 2000 or XP NT 4 上で TCP/IP を用いて MySQL を動作させるには、service pack 3(以上) が必須です！ Normally you should install MySQL as a service on Windows NT/2000/XP. In case the server was already running, first stop it using the following command: @example C:\mysql\bin> mysqladmin -u root shutdown @end example This calls the MySQL administation utility as user `@code{root}', which is the default @code{Administrator} in the MySQL grant system. Please note that the MySQL grant system is wholly independent from any login users under Windows. Now install the server service: @example C:\mysql\bin> mysqld-max-nt --install @end example If any options are required, they must be specified as ``@code{Start parameters}'' in the Windows @code{Services} utility before you start the MySQL service. The @code{Services} utility (@code{Windows Service Control Manager}) can be found in the @code{Windows Control Panel} (under @code{Administrative Tools} on Windows 2000). It is advisable to close the Services utility while performing the @code{--install} or @code{--remove} operations, this prevents some odd errors. For information about which server binary to run, see @ref{Windows prepare environment}. Please note that from MySQL version 3.23.44, you have the choice of set up the service as @code{Manual} instead (if you don't wish the service to be started automatically during the boot process): @example C:\mysql\bin> mysqld-max-nt --install-manual @end example サービスは @code{MySQL} という名前で登録されます。 一度インストールしたら、 これは Services (コントロールパネルにある) を使用するか、@code{NET START MySQL} コマンドを使用するかして、 起動されなくてはなりません。 Once running, @code{mysqld-max-nt} can be stopped using @code{mysqladmin}, from the Services utility, or by using the command @code{NET STOP MySQL}. When running as a service, the operating system will automatically stop the MySQL service on computer shutdown. In MySQL versions < 3.23.47, Windows only waited for a few seconds for the shutdown to complete, and killed the database server process if the time limit was exceeded (potentially causing problems). For instance, at the next startup the @code{InnoDB} storage engine had to do crash recovery. Starting from MySQL version 3.23.48, the Windows will wait longer for the MySQL server shutdown to complete. If you notice this is not enough for your intallation, it is safest to run the MySQL server not as a service, but from the Command prompt, and shut it down with @code{mysqladmin shutdown}. There is a problem that Windows NT (but not Windows 2000/XP) by default only waits 20 seconds for a service to shut down, and after that kills the service process. You can increase this default by opening the Registry Editor @file{\winnt\system32\regedt32.exe} and editing the value of @code{WaitToKillServiceTimeout} at @file{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control} in the Registry tree. Specify the new larger value in milliseconds, for example 120000 to have Windows NT wait upto 120 seconds. Please note that when run as a service, @code{mysqld-max-nt} has no access to a console and so no messages can be seen. Errors can be checked in @file{c:\mysql\data\mysql.err}. もし @code{mysqld-max-nt} をサービスとしてインストールする場合に 問題が発生した場合、フルパスで実行してみてください： @example C:\> C:\mysql\bin\mysqld-max-nt --install @end example If this doesn't work, you can get @code{mysqld-max-nt} to start properly by fixing the path in the registry! サービスとして @code{mysqld-max-nt} を起動したくないなら以下のようにします： @example C:\> C:\mysql\bin\mysqld-max-nt --standalone @end example or @example C:\> C:\mysql\bin\mysqld --standalone --debug @end example 最新のバージョンでは、デバッグのトレースを @file{C:\mysqld.trace} に出します。 @xref{Making trace files}. @node Windows running, Windows and SSH, NT start, Windows @subsubsection Windows 上で MySQL を実行 @cindex TCP/IP @cindex named pipes MySQL supports TCP/IP on all Windows platforms and named pipes on NT/2000/XP. The default is to use named pipes for local connections on NT/2000/XP and TCP/IP for all other cases if the client has TCP/IP installed. The host name specifies which protocol is used: @multitable @columnfractions .15 .60 @item @strong{Host name} @tab @strong{Protocol} @item NULL (none) @tab On NT/2000/XP, try named pipes first; if that doesn't work, use TCP/IP. On 9x/Me, TCP/IP is used. @item . @tab Named pipes @item localhost @tab TCP/IP to current host @item hostname @tab TCP/IP @end multitable MySQL クライアントに named pipes を強制的に使用させるには、 @code{--pipe} オプションか、ホストに @code{.} を指定します。 そして、@code{--socket} オプションでパイプの名前を指定します。 In MySQL 4.1 you should use the @code{--protocol=PIPE} option. Note that starting from 3.23.50, named pipes are only enabled if mysqld is started with @code{--enable-named-pipe}. This is because some users have experienced problems shutting down the MySQL server when one uses named pipes. MySQL が動いているかどうかは、以下のようにして確認できます： @example C:\> C:\mysql\bin\mysqlshow C:\> C:\mysql\bin\mysqlshow -u root mysql C:\> C:\mysql\bin\mysqladmin version status proc C:\> C:\mysql\bin\mysql test @end example If @code{mysqld} is slow to answer to connections on Windows 9x/Me, there is probably a problem with your DNS. In this case, start @code{mysqld} with @code{--skip-name-resolve} and use only @code{localhost} and IP numbers in the MySQL grant tables. You can also avoid DNS when connecting to a @code{mysqld-nt} MySQL server running on NT/2000/XP by using the @code{--pipe} argument to specify use of named pipes. This works for most MySQL clients. 2つの MySQL コマンドラインツールがあります： @multitable @columnfractions .10 .60 @item @strong{Binary} @tab @strong{Description} @item @code{mysql} @tab ネイティブな Windows 用にコンパイルされている。非常に限られたコマンドライン編集機能しか持たない @item @code{mysqlc} @tab Cygnus GNU コンパイラとライブラリを用いてコンパイルされている。GNU readline によるコマンドライン編集機能を持つ。 @end multitable もし @code{mysqlc.exe} を使用したいなら, @file{C:\mysql\lib\cygwinb19.dll} をあなたの Windows システムディレクトリ (@file{\windows\system} もしくは同様のパス)にコピーしなくてはなりません。 Windows の MySQL の初期の権限は、ローカルの全てのユーザーに 対して、全てのデータベースで全ての権限がパスワードなしに与えられています。 MySQL を安全にするために、全てのユーザーにパスワードを 設定すべきです。また、@code{mysql.user} テーブルから @code{Host='localhost'} で @code{User=''} となっているレコードを 削除すべきです。 @code{root} ユーザーにもパスワードを設定すべきです。次の例では、 すべての権限を持つ匿名ユーザを削除したあとに、 @code{root} ユーザパスワードを設定しています: @example C:\> C:\mysql\bin\mysql mysql mysql> DELETE FROM user WHERE Host='localhost' AND User=''; mysql> QUIT C:\> C:\mysql\bin\mysqladmin reload C:\> C:\mysql\bin\mysqladmin -u root password your_password @end example パスワードを設定した後、もし @code{mysqld} サーバーを停止させるなら、 以下のようにします： @example C:\> mysqladmin --user=root --password=your_password shutdown @end example もしあなたが Windows 下で、古い MySQL バージョン 3.21 のシェアウェ アバージョンを使用しているなら、上記のコマンドは次のエラーで失敗します: @code{parse error near 'SET password'}。回避策は、現在の MySQL バージョンにアップグレードすることです。これもフリーです。 現在の MySQL バージョンでは、@code{GRANT} と @code{REVOKE} コ マンドで、簡単に新しいユーザを追加でき、権限を変更することができます。 @xref{GRANT}. @node Windows and SSH, Windows symbolic links, Windows running, Windows @subsubsection SSH を利用してリモートの MySQL に Windows から接続 @c FIX this is ugly, real ugly. @cindex SSH @cindex connecting, remotely with SSH 以下は SSH を用いてリモートの MySQL サーバに安全に接続するための 方法について述べたものです。 (by David Carlson @email{dcarlson@@mplcomm.com}): @itemize @bullet @item Install an SSH client on your Windows machine. As a user, the best non-free one I've found is from @code{SecureCRT} from @uref{http://www.vandyke.com/}. Another option is @code{f-secure} from @uref{http://www.f-secure.com/}. You can also find some free ones on @code{Google} at @uref{http://directory.google.com/Top/Computers/Security/Products_and_Tools/Cryptography/SSH/Clients/Windows/}. @item Windows SSH クライアントを起動。 Set @code{Host_Name = yourmysqlserver_URL_or_IP}. Set @code{userid=your_userid} to log in to your server (probably not the same as your MySQL login/password. @item Set up port forwarding. Either do a remote forward (Set @code{local_port: 3306}, @code{remote_host: yourmysqlservername_or_ip}, @code{remote_port: 3306} ) or a local forward (Set @code{port: 3306}, @code{host: localhost}, @code{remote port: 3306}). @item Save everything, otherwise you'll have to redo it the next time. @item Log in to your server with SSH session you just created. @item On your Windows machine, start some ODBC application (such as Access). @item Create a new file in Windows and link to MySQL using the ODBC driver the same way you normally do, except type in @code{localhost} for the MySQL host server@-not @code{yourmysqlservername}. @end itemize You should now have an ODBC connection to MySQL, encrypted using SSH. @node Windows symbolic links, Windows client compiling, Windows and SSH, Windows @subsubsection Windows 上で、異なるディスクにデータを分割する @cindex symbolic links @cindex using multiple disks to start data @cindex disks, splitting data across Windows 上では、3.23.16 以上のバージョンの MySQL ディストリビュー ション中の @code{mysqld-max} と @code{mysql-max-nt} サーバは、 @code{-DUSE_SYMDIR} オプション付きでコンパイルされています。これはデータ ベースに対するシンボリックリンクを追加することで異なるディスクにデータベー スを置くことを可能にします（Unix におけるシンボリック・リンクと同様の方法 で）。 Windows 上では、宛先ディレクトリへのパスを持つファイルを作成し、 そのファイルを @code{database.sym} というファイル名で @code{mysql_data} ディレクトリ の中に保存することで、データベースへのシンボリックリンクを作成します。 Note that the symbolic link will only be used if the directory @code{mysql_data_dir\database} doesn't exist. 例えば、MySQL データディレクトリが @file{C:\mysql\data} で、 @file{D:\data\foo} に置かれているデータベース @code{foo} を持ちたければ、 テキスト @code{D:\data\foo\} を含む @file{C:\mysql\data\foo.sym} を作成す べきです。その後、データベース @code{foo} に作成されるすべてのテーブルは @file{D:\data\foo} に作成されるでしょう。 Note that because of the speed penalty you get when opening every table, we have not enabled this by default even if you have compiled MySQL with support for this. To enable symlinks you should put in your @file{my.cnf} or @file{my.ini} file the following entry: @example [mysqld] use-symbolic-links @end example In MySQL 4.0 we will enable symlinks by default. Then you should instead use the @code{skip-symlink} option if you want to disable this. @node Windows client compiling, Windows vs Unix, Windows symbolic links, Windows @subsubsection Windows 上で MySQL クライアントをコンパイルする @cindex compiling, on Windows @cindex Windows, compiling on ソースファイル中で @file{mysql.h} をインクルードする前に @file{windows.h} を インクルードするべきです： @example #if defined(_WIN32) || defined(_WIN64) #include #endif #include @end example あなたのコードを、必要に応じて @file{libmysql.dll} 中でロードするための ラッパーである @file{libmysql.lib} ライブラリに動的にリンクすることも できますし、また @file{mysqlclient.lib} ライブラリを静的にリンクすることも できます。 mysqlclient ライブラリはスレッド対応ライブラリとしてコンパイル されていますので、あなたのコードもマルチスレッド対応になるように コンパイルするべきことに注意してください。 @node Windows vs Unix, , Windows client compiling, Windows @subsubsection Windows 用 MySQL と Unix 用 MySQL の比較 @cindex Windows, versus Unix @cindex operating systems, Windows versus Unix MySQL-Windows バージョンは現在それ自体とても安定した(stableな)状態で供給されています。 MySQL-win32 バージョンは すべての機能が UNIX バージョンの MySQL と対応しています。 ただし、下記のような例外があります。 @table @strong @item Win95 とスレッド Win95は、各々のスレッドの作成のためにメインメモリのおよそ200バイトをメモリリーク します。もしあなたが多くの接続をすれば、MySQL の各々の接続が新しい スレッドを作成するので、あなたはWin95では長時間、@code{mysqld} を実行させるべきではあり ません！ WindowsNT と Windows98 はこのバグを持ちません。 @item 並行読み出し MySQL は @code{INSERT} と @code{SELECT} を混ぜることを可能にするために @code{pread()} 及び @code{pwrite()} 関数コールに依存します。現時点では @code{pread()}/@code{pwrite()} をエミュレートするために Mutex を用いています。長期的な計画では、 ファイルレベルのインターフェースを仮想インターフェースで置き換えて いくつもりなので、さらに速度を上げるために Windows NT/2000/XP 上で @code{readfile()}/@code{writefile()} インターフェースを使うことができます。 現在の実装は、しかし MySQL が利用可能なファイル数の上限が 1024 に なっています。これは Unix では可能な数の並行スレッドを NT/2000/XP 上では 動作させることができないことを意味しています。 @item ブロック読み込み MySQL はそれぞれの接続のためにブロック読み込みを使います。 これは以下の事柄を意味しています： @itemize @bullet @item 接続は、Unix の MySQL で起こるように、8時間の後に自動的に接続が断 ち切られるわけではありません @item もし接続が「ハングすれば」、MySQLを終了しないでそれを中断することは、不可能です。 @item @code{mysqladmin kill} は、スリープしている接続上では働かないはずです。 @item スリープ中の接続があるかぎり、@code{mysqladmin shutdown} は中断することができません。 @end itemize We plan to fix this problem when our Windows developers have figured out a nice workaround. @item @code{DROP DATABASE} 複数のスレッドで使われているデータベースはDROPをすることができません。 @item タスクマネージャーからの MySQL の終了 Windows95では「Windowsの終了」やタスクマネージャから MySQL を終了することはできません。 @code{mysqladmin shutdown} で終了しなければなりません。 @item 大文字小文字を区別しない名前 Windowsではファイルネームは大文字小文字が区別されません。 そのため、Windows用の MySQL では、テーブル名は大文字小文字が区別されません。 唯一の制限は、ステートメント(SQL文)中においては、データベースとテーブルの名前は 同じケース(大文字小文字)を使用して指定されなければならないという点です。 @xref{Name case sensitivity}. @item The @samp{\} directory character Windows 95のパス名コンポーネントは、 @samp{\} によって離されますが、その文字は同じく MySQL のエスケープ文字でもあります。もしあなたが @code{LOAD DATA INFILE} または @code{SELECT ... INTO OUTFILE} を使う場合には、@samp{\} を二重に使わなくてはなりません。 @example mysql> LOAD DATA INFILE "C:\\tmp\\skr.txt" INTO TABLE skr; mysql> SELECT * INTO OUTFILE 'C:\\tmp\\skr.txt' FROM skr; @end example かわりに、UNIX でのファイルネーム形式 @samp{/} で書く必要があります。 @example mysql> LOAD DATA INFILE "C:/tmp/skr.txt" INTO TABLE skr; mysql> SELECT * INTO OUTFILE 'C:/tmp/skr.txt' FROM skr; @end example @item @code{Can't open named pipe} エラー もしあなたが NT 上で最新の mysql-clients と MySQL 3.22 バージョン を使えば、あなたは、次のエラーを得ることになるはずです: @example error 2017: can't open named pipe to host: . pipe... @end example @tindex .my.cnf file これは、MySQL のリリースバージョンがデフォルトで NT の 名前つきパイプを 使っているために起こっています。 新しい MySQL クライアントで @code{--host=localhost} オプションを用いるか、 以下の情報を含むオプションファイル @file{C:\my.cnf} を作成することで、このエラーを 回避することができます。 @example [client] host = localhost @end example Starting from 3.23.50, named pipes are only enabled if @code{mysqld} is started with @code{--enable-named-pipe}. @item @code{Access denied for user} error もしあなたが同じマシン上の MySQL サーバーにアクセスした時 @code{Access denied for user: 'some-user@@unknown' to database 'mysql'} エラーを得るなら、これはあなたの MySQL があなた のマシンのホスト名を正しく解決できてないことを意味します。 これを修正するには、 以下の情報を持つファイル @file{\windows\hosts} を作成するべきです。 (注:Windows95,98には\Windowsフォルダ上にサンプルとして「lmhosts.sam」ファイルが 既にあるはずです) @example 127.0.0.1 localhost @end example @item @code{ALTER TABLE} @code{ALTER TABLE} ステートメントの実行中、テーブルは他のスレッドが使用できないようロック されます。これは Windows が他のスレッドによって使用中のファイルを削除 できないという事実のためにしなければならないことです（私たちはこの 問題を回避するための方法を将来見出すかもしれません）。 @item @code{DROP TABLE} on a table that is in use by a @code{MERGE} table will not work on Windows because the @code{MERGE} handler does the table mapping hidden from the upper layer of MySQL. Because Windows doesn't allow you to drop files that are open, you first must flush all @code{MERGE} tables (with @code{FLUSH TABLES}) or drop the @code{MERGE} table before dropping the table. We will fix this at the same time we introduce @code{VIEW}s. @item @code{DATA DIRECTORY} and @code{INDEX DIRECTORY} directives in @code{CREATE TABLE} is ignored on Windows, because Windows doesn't support symbolic links. @end table Here are some open issues for anyone who might want to help us with the Windows release: @cindex Windows, open issues @itemize @bullet @item Make a single-user @code{MYSQL.DLL} server. This should include everything in a standard MySQL server, except thread creation. This will make MySQL much easier to use in applications that don't need a true client/server and don't need to access the server from other hosts. @item MySQL のインストールされたもののための、素敵な開始・シャットダウン アイコンの追加。 @item NT上で @code{mysqld} をサービスとして @code{--install} フラグで登録するとき、 コマンドラインにデフォルトオプションも一緒に追加できると素敵です。 差し当たって、 回避策は代わりに @file{C:\my.cnf} ファイル内のパラメータをリストすることです。 @item タスクマネージャから @code{mysqld} を終了させることができればほんとうに親切でしょう。 今のところ、あなたは @code{mysqladmin shutdown} を使わなければなりません。 @item @code{mysql} のコマンドライン・ツールで使うために @code{readline} をWindowsに移植しませんか？ @item 標準の MySQL クライアント(@code{mysql}、@code{mysqlshow}、@code{mysqladmin}、および、@code{mysqldump})のGUI バージョンがあればいいでしょうねぇ。 @item @file{net.c} 中のソケット読み出し・書き込み関数が割り込み不可だったら素敵 でした。これは Windows 上で @code{mysqladmin kill} を用いて、オープンなスレッドを kill することができるでしょう。 @item @code{mysqld} はデフォルトロケールではなく、常に「C」ロケールで起動します。私たちは、 ソート順に関して @code{mysqld} が現在のロケールを使用するようにしたいです。 @item Windows によって提供されている、より高速でスレッドセーフなインクリメント・ デクリメントメソッドを使うためのマクロの追加 @end itemize 他の Windows 特有の事柄は MySQL-Windows ディストリビューションに同梱されている @file{README} ファイルで説明されています。 @node Solaris, BSD Notes, Windows, Operating System Specific Notes @subsection Solaris Notes @cindex Solaris installation problems @cindex problems, installing on Solaris @cindex tar, problems on Solaris @cindex errors, directory checksum @cindex checksum errors Solaris では MySQL ソースを展開するときトラブルが出るでしょう！ Solaris の @code{tar} は長い名前を扱えず、 MySQL を展開する場合、 以下のようなエラーになります： @example x mysql-3.22.12-beta/bench/Results/ATIS-mysql_odbc-NT_4.0-cmp-db2,\ informix,ms-sql,mysql,oracle,solid,sybase, 0 bytes, 0 tape blocks tar: directory checksum error @end example この場合、GNU @code{tar} (@code{gtar}) を展開に使用してください。 コンパイルずみのものが以下にあります： @uref{http://www.mysql.com/downloads/os-solaris.html}. Sun ネイティブスレッドは Solaris 2.5 以上で動きます。 バージョン 2.4 以下の場合、MySQL は時動的に MIT-pthreads を使用します @xref{MIT-pthreads}. もし、configure 時に、以下のエラーが出たなら： @example checking for restartable system calls... configure: error can not run test programs while cross compiling @end example これはコンパイラーのインストールでなにかを間違っています! この場合、あなたは、より新しいバージョンへコンパイラーをアップグレードすべきです。 以下の行を @code{config.cache} ファイルに追加することによって、 この問題を解決してもかまいません： @example ac_cv_sys_restartable_syscalls=$@{ac_cv_sys_restartable_syscalls='no'@} @end example もしあなたが SPARC の Solaris を使用しているなら、 @code{gcc} 2.95.2 を推奨します。 これは @uref{ttp://gcc.gnu.org/}. で見つけれます。 @code{egcs} 1.1.1 と @code{gcc} 2.8.1 は SPARC 上では完全に動作しないことに注意！ @code{gcc} 2.95.2 を使用した、推奨する @code{configure} は: @example CC=gcc CFLAGS="-O3" \ CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql --with-low-memory --enable-assembler @end example If you have an UltraSPARC, you can get 4% more performance by adding "-mcpu=v8 -Wa,-xarch=v8plusa" to CFLAGS and CXXFLAGS. If you have Sun's Forte 5.0 (or newer) compiler, you can run @code{configure} like this: @example CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \ CXX=CC CXXFLAGS="-noex -mt" \ ./configure --prefix=/usr/local/mysql --enable-assembler @end example You can create a 64 bit binary with: @example CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \ CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \ ./configure --prefix=/usr/local/mysql --enable-assembler @end example In the MySQL benchmarks, we got a 4% speedup on an UltraSPARC when using Forte 5.0 in 32 bit mode compared to using gcc 3.2 with -mcpu flags. If you create a 64 bit binary, it's 4 % slower than the 32 bit binary, but mysqld can instead handle more treads and memory. If you get a problem with @code{fdatasync} or @code{sched_yield}, you can fix this by adding @code{LIBS=-lrt} to the configure line The following paragraph is only relevant for older compilers than WorkShop 5.3: You may also have to edit the @code{configure} script to change this line: @example #if !defined(__STDC__) || __STDC__ != 1 @end example to this: @example #if !defined(__STDC__) @end example もし @code{-Xc} オプションで @code{__STDC__} を有効にした場合、 Sun compiler は Solaris の @file{pthread.h} ヘッダーファイルを使用して コンパイルすることができません。 これはサンのバグです(インクルードファイルかコンパイラーのバグ) もし @code{mysqld} を起動時に以下のエラーが出た場合、 マルチスレッドを外して(オプション @code{-mt} を指定) Sun compiler を使って MySQL をコンパイルし直してください： @example libc internal error: _rmutex_unlock: rmutex not held @end example @code{-mt} を @code{CFLAGS} と @code{CXXFLAGS} に加えます。 If you are using the SFW version of gcc (which comes with Solaris 8), you must add @file{/opt/sfw/lib} to the environment variable @code{LD_LIBRARY_PATH} before running configure. If you are using the gcc available from @code{sunfreeware.com}, you may have many problems. You should recompile gcc and GNU binutils on the machine you will be running them from to avoid any problems. If you get the following error when compiling MySQL with @code{gcc}, it means that your @code{gcc} is not configured for your version of Solaris: @example shell> gcc -O3 -g -O2 -DDBUG_OFF -o thr_alarm ... ./thr_alarm.c: In function `signal_hand': ./thr_alarm.c:556: too many arguments to function `sigwait' @end example The proper thing to do in this case is to get the newest version of @code{gcc} and compile it with your current @code{gcc} compiler! At least for Solaris 2.5, almost all binary versions of @code{gcc} have old, unusable include files that will break all programs that use threads (and possibly other programs)! Solaris は スタテックリンクのシステムライブラリーを用意していません (@code{libpthreads} and @code{libdl})。 そのため、@code{--static} オプションで MySQL をコンパイルできません。 もしこれを試みた場合、以下のエラーになります： @example ld: fatal: library -ldl: not found or undefined reference to `dlopen' or cannot find -lrt @end example もし多くのプロセスが速く @code{mysqld} に接続を試みた場合、 MySQL ログに以下のようにエラーが出ます: @example Error in accept: Protocol error @end example サーバーを @code{--set-variable back_log=50} オプションで起動すれば、この問題に対処できるでしょう。 Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--back_log=50} on its own. @xref{Command-line options}. もし自分の MySQL クライアントプログラムをリンクして 実行時に以下のようにエラーが出た場合： @example ld.so.1: ./my: fatal: libmysqlclient.so.#: open failed: No such file or directory @end example これは以下のどれかで回避できます： @itemize @bullet @item 以下のフラグでクライアントをリンクします(@code{-Lpath} の代わりに): @code{-Wl,r/full-path-to-libmysqlclient.so}. @item Copy @file{libmysqclient.so} to @file{/usr/lib}. @tindex LD_RUN_PATH environment variable @tindex Environment variable, LD_RUN_PATH @item Add the pathname of the directory where @file{libmysqlclient.so} is located to the @code{LD_RUN_PATH} environment variable before running your client. @end itemize configure や MySQL が @code{-lz} のリンクを試み、あなたがそれを インストールしていないという問題がある場合は、２つの選択肢があります: @itemize @bullet @item 圧縮通信プロトコルを使用できるようにしたい場合、ftp.gnu.org から zlib を 入手してインストールする必要があります。 @item @code{--with-named-z-libs=no} をつけて configure を行ないます。 @end itemize If you are using gcc and have problems with loading @code{UDF} functions into MySQL, try adding @code{-lgcc} to the link line for the @code{UDF} function. MySQL を自動的に開始させたい場合、 @file{support-files/mysql.server} を @file{/etc/init.d} にコピーし、 @code{/etc/rc3.d/S99mysql.server} という名前でシンボリックリンクを生成し てください。 As Solaris doesn't support core files for @code{setuid()} applications, you can't get a core file from @code{mysqld} if you are using the @code{--user} option. @menu * Solaris 2.7:: Solaris 2.7/2.8 Notes * Solaris x86:: Solaris x86 Notes @end menu @node Solaris 2.7, Solaris x86, Solaris, Solaris @subsubsection Solaris 2.7/2.8 Notes 通常、Solaris 2.6 のバイナリは Solaris 7 , 8 で使用できます。 ほとんどの Solaris 2.6 の問題も Solaris 7 , 8 に適用できます。 注意: MySQL Version 3.23.4 以上では、新しいバージョンの Solaris を自動 検出し、以下の問題についての回避策を有効にします！ Solaris 7 , 8 は、インクルードファイルにいくつかバグがあります。 @code{gcc} で以下のようなエラーが出た場合： @example /usr/include/widec.h:42: warning: `getwc' redefined /usr/include/wchar.h:326: warning: this is the location of the previous definition @end example 以下のようにして回避します： @code{/usr/include/widec.h} を @code{.../lib/gcc-lib/os/gcc-version/include} にコピー 41 行目を変更: @example 変更前： #if !defined(lint) && !defined(__lint) 変更後： #if !defined(lint) && !defined(__lint) && !defined(getwc) @end example 代わりに、@file{/usr/include/widec.h} を直接変更してもかまいません。 どちらの方法にしても、ファイルを修正後は、@file{config.cache} を 消して @code{configure} を再実行しなくてはなりません！ @code{make} 実行時に以下のようなエラーになった場合、@code{configure} が @file{curses.h} ファイルを検出できていません (これは @code{/usr/include/widec.h} の エラーのためにおきます): @example In file included from mysql.cc:50: /usr/include/term.h:1060: syntax error before `,' /usr/include/term.h:1081: syntax error before `;' @end example これを解決するには、以下のうち一つを行います： @itemize @bullet @item Configure with @code{CFLAGS=-DHAVE_CURSES_H CXXFLAGS=-DHAVE_CURSES_H ./configure}. @item 前述したとおり、@file{/usr/include/widec.h} を修正し、configure を再実行します。 @item @code{#define HAVE_TERM} 行を @file{config.h} ファイルから消し、 @code{make} を再実行します。 @end itemize クライアントプログラムのリンク時に、リンカが @code{-lz} を見つけられない という問題が発生した場合、問題はおそらく @file{libz.so} ファイルが @file{/usr/local/lib} にインストールされたことです。次の方法の一つでこれ を修正できます: @itemize @bullet @item @code{LD_LIBRARY_PATH} に @file{/usr/local/lib} を追加 @item @code{/lib} から @code{libz.so} へのリンクを追加 @item Solaris 8 を使用している場合、Solaris 8 CD ディストリビューションからオ プションの zlib をインストール可能。 @item @code{--with-named-z-libs=no} オプション付きで MySQL を configure する。 @end itemize @node Solaris x86, , Solaris 2.7, Solaris @subsubsection Solaris x86 Notes On Solaris 2.8 on x86, @code{mysqld} will core dump if you run 'strip' in. （訳注： GNU binutils を Sun 上で使用すると、CPU, version にかかわらず、 この現象に遭遇します。その場合は、/usr/ccs/bin/ の方を使います。） @code{gcc} か @code{egcs} を Solaris x86 で使用した場合、load 時にコアダンプする場合、 以下のように @code{configure} します: @example CC=gcc CFLAGS="-O3 -fomit-frame-pointer -DHAVE_CURSES_H" \ CXX=gcc \ CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors -fno-exceptions \ -fno-rtti -DHAVE_CURSES_H" \ ./configure --prefix=/usr/local/mysql @end example これは @code{libstdc++} ライブラリーと C++ の問題を回避します。 もしこれが該当しない場合、デバッグモードでコンパイルして デバッグのトレースファイルを書き出すようにして起動するか、 @code{gdb} を使用して起動してください. @xref{Using gdb on mysqld}. @node BSD Notes, Mac OS X, Solaris, Operating System Specific Notes @subsection BSD Notes This section provides information for the various BSD flavours, as well as specific versions within those. @menu * FreeBSD:: FreeBSD Notes * NetBSD:: NetBSD notes * OpenBSD:: OpenBSD 2.5 Notes * OpenBSD 2.8:: OpenBSD 2.8 Notes * BSDI:: BSD/OS Version 2.x Notes * BSDI3:: BSD/OS Version 3.x Notes * BSDI4:: BSD/OS Version 4.x Notes @end menu @node FreeBSD, NetBSD, BSD Notes, BSD Notes @subsubsection FreeBSD Notes FreeBSD 3.x is recommended for running MySQL since the thread package is much more integrated. The easiest and therefore the preferred way to install is to use the mysql-server and mysql-client ports available on @uref{http://www.freebsd.org/}. Using these gives you: @itemize @bullet @item A working MySQL with all optimisations known to work on your version of FreeBSD enabled. @item Automatic configuration and build. @item Startup scripts installed in /usr/local/etc/rc.d. @item Ability to see which files that are installed with pkg_info -L. And to remove them all with pkg_delete if you no longer want MySQL on that machine. @end itemize It is recommended you use MIT-pthreads on FreeBSD 2.x and native threads on Versions 3 and up. It is possible to run with native threads on some late 2.2.x versions but you may encounter problems shutting down @code{mysqld}. The MySQL @file{Makefile}s require GNU make (@code{gmake}) to work. If you want to compile MySQL you need to install GNU @code{make} first. Be sure to have your name resolver setup correct. Otherwise, you may experience resolver delays or failures when connecting to @code{mysqld}. Make sure that the @code{localhost} entry in the @file{/etc/hosts} file is correct (otherwise, you will have problems connecting to the database). The @file{/etc/hosts} file should start with a line: @example 127.0.0.1 localhost localhost.your.domain @end example The recommended way to compile and install MySQL on FreeBSD with gcc (2.95.2 and up) is: @example CC=gcc CFLAGS="-O2 -fno-strength-reduce" \ CXX=gcc CXXFLAGS="-O2 -fno-rtti -fno-exceptions -felide-constructors \ -fno-strength-reduce" \ ./configure --prefix=/usr/local/mysql --enable-assembler gmake gmake install ./scripts/mysql_install_db cd /usr/local/mysql ./bin/mysqld_safe & @end example If you notice that @code{configure} will use MIT-pthreads, you should read the MIT-pthreads notes. @xref{MIT-pthreads}. If you get an error from @code{make install} that it can't find @file{/usr/include/pthreads}, @code{configure} didn't detect that you need MIT-pthreads. This is fixed by executing these commands: @example shell> rm config.cache shell> ./configure --with-mit-threads @end example FreeBSD is also known to have a very low default file handle limit. @xref{Not enough file handles}. Uncomment the ulimit -n section in safe_mysqld or raise the limits for the @code{mysqld} user in /etc/login.conf (and rebuild it with cap_mkdb /etc/login.conf). Also be sure you set the appropriate class for this user in the password file if you are not using the default (use: chpass mysqld-user-name). @xref{safe_mysqld, , @code{safe_mysqld}}. If you have a lot of memory you should consider rebuilding the kernel to allow MySQL to take more than 512M of RAM. Take a look at @code{option MAXDSIZ} in the LINT config file for more info. If you get problems with the current date in MySQL, setting the @code{TZ} variable will probably help. @xref{Environment variables}. To get a secure and stable system you should only use FreeBSD kernels that are marked @code{-RELEASE}. @node NetBSD, OpenBSD, FreeBSD, BSD Notes @subsubsection NetBSD notes To compile on NetBSD you need GNU @code{make}. Otherwise, the compile will crash when @code{make} tries to run @code{lint} on C++ files. @node OpenBSD, OpenBSD 2.8, NetBSD, BSD Notes @subsubsection OpenBSD 2.5 Notes On OpenBSD Version 2.5, you can compile MySQL with native threads with the following options: @example CFLAGS=-pthread CXXFLAGS=-pthread ./configure --with-mit-threads=no @end example @node OpenBSD 2.8, BSDI, OpenBSD, BSD Notes @subsubsection OpenBSD 2.8 Notes Our users have reported that OpenBSD 2.8 has a threading bug which causes problems with MySQL. The OpenBSD Developers have fixed the problem, but as of January 25th, 2001, it's only available in the ``-current'' branch. The symptoms of this threading bug are: slow response, high load, high CPU usage, and crashes. If you get an error like @code{Error in accept:: Bad file descriptor} or error 9 when trying to open tables or directories, the problem is probably that you haven't allocated enough file descriptors for MySQL. In this case try starting @code{safe_mysqld} as root with the following options: @code{--user=mysql --open-files-limit=2048} @node BSDI, BSDI3, OpenBSD 2.8, BSD Notes @subsubsection BSD/OS Version 2.x Notes If you get the following error when compiling MySQL, your @code{ulimit} value for virtual memory is too low: @example item_func.h: In method `Item_func_ge::Item_func_ge(const Item_func_ge &)': item_func.h:28: virtual memory exhausted make[2]: *** [item_func.o] Error 1 @end example Try using @code{ulimit -v 80000} and run @code{make} again. If this doesn't work and you are using @code{bash}, try switching to @code{csh} or @code{sh}; some BSDI users have reported problems with @code{bash} and @code{ulimit}. If you are using @code{gcc}, you may also use have to use the @code{--with-low-memory} flag for @code{configure} to be able to compile @file{sql_yacc.cc}. If you get problems with the current date in MySQL, setting the @code{TZ} variable will probably help. @xref{Environment variables}. @node BSDI3, BSDI4, BSDI, BSD Notes @subsubsection BSD/OS Version 3.x Notes Upgrade to BSD/OS Version 3.1. If that is not possible, install BSDIpatch M300-038. Use the following command when configuring MySQL: @example shell> env CXX=shlicc++ CC=shlicc2 \ ./configure \ --prefix=/usr/local/mysql \ --localstatedir=/var/mysql \ --without-perl \ --with-unix-socket-path=/var/mysql/mysql.sock @end example The following is also known to work: @example shell> env CC=gcc CXX=gcc CXXFLAGS=-O3 \ ./configure \ --prefix=/usr/local/mysql \ --with-unix-socket-path=/var/mysql/mysql.sock @end example You can change the directory locations if you wish, or just use the defaults by not specifying any locations. If you have problems with performance under heavy load, try using the @code{--skip-thread-priority} option to @code{mysqld}! This will run all threads with the same priority; on BSDI Version 3.1, this gives better performance (at least until BSDI fixes their thread scheduler). If you get the error @code{virtual memory exhausted} while compiling, you should try using @code{ulimit -v 80000} and run @code{make} again. If this doesn't work and you are using @code{bash}, try switching to @code{csh} or @code{sh}; some BSDI users have reported problems with @code{bash} and @code{ulimit}. @node BSDI4, , BSDI3, BSD Notes @subsubsection BSD/OS Version 4.x Notes BSDI Version 4.x has some thread-related bugs. If you want to use MySQL on this, you should install all thread-related patches. At least M400-023 should be installed. On some BSDI Version 4.x systems, you may get problems with shared libraries. The symptom is that you can't execute any client programs, for example, @code{mysqladmin}. In this case you need to reconfigure not to use shared libraries with the @code{--disable-shared} option to configure. Some customers have had problems on BSDI 4.0.1 that the @code{mysqld} binary after a while can't open tables. This is because some library/system related bug causes @code{mysqld} to change current directory without asking for this! The fix is to either upgrade to 3.23.34 or after running @code{configure} remove the line @code{#define HAVE_REALPATH} from @code{config.h} before running make. Note that the above means that you can't symbolic link a database directories to another database directory or symbolic link a table to another database on BSDI! (Making a symbolic link to another disk is okay). @node Mac OS X, Other Unix Notes, BSD Notes, Operating System Specific Notes @subsection Mac OS X Notes @menu * Mac OS X 10.x:: Mac OS X 10.x * Mac OS X Server:: Mac OS X Server @end menu @node Mac OS X 10.x, Mac OS X Server, Mac OS X, Mac OS X @subsubsection Mac OS X 10.x MySQL should work without any problems on Mac OS X 10.x (Darwin). You don't need the pthread patches for this OS! This also applies to Mac OS X 10.x Server. Compiling for the Server platform is the same as for the client version of Mac OS X. However please note that MySQL comes preinstalled on the Server! @xref{Mac OS X installation}. @node Mac OS X Server, , Mac OS X 10.x, Mac OS X @subsubsection Mac OS X Server 1.2 (Rhapsody) Before trying to configure MySQL on Mac OS X server you must first install the pthread package from @uref{http://www.prnet.de/RegEx/mysql.html}. Our binary for Mac OS X is compiled on Darwin 6.3 with the following configure line: @example CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \ --with-extra-charsets=complex --enable-thread-safe-client \ --enable-local-infile --disable-shared @end example You might want to also add aliases to your shell's resource file to access @code{mysql} and @code{mysqladmin} from the command-line: @example alias mysql '/usr/local/mysql/bin/mysql' alias mysqladmin '/usr/local/mysql/bin/mysqladmin' @end example Alternatively, you could simply add @code{/usr/local/mysql/bin} to your @code{PATH} environment variable, e.g. by adding the following to @file{$HOME/.tcshrc}: @example setenv PATH $PATH:/usr/local/bin @end example @node Other Unix Notes, OS/2, Mac OS X, Operating System Specific Notes @subsection Other Unix Notes @menu * Binary notes-HP-UX:: HP-UX Notes for Binary Distributions * HP-UX 10.20:: HP-UX Version 10.20 Notes * HP-UX 11.x:: HP-UX Version 11.x Notes * IBM-AIX:: IBM-AIX notes * SunOS:: SunOS 4 Notes * Alpha-DEC-UNIX:: Alpha-DEC-UNIX Notes (Tru64) * Alpha-DEC-OSF1:: Alpha-DEC-OSF/1 Notes * SGI-Irix:: SGI Irix Notes * Caldera:: Caldera Notes * Caldera Unixware:: Caldera Unixware Version 7.0 Notes @end menu @node Binary notes-HP-UX, HP-UX 10.20, Other Unix Notes, Other Unix Notes @subsubsection HP-UX Notes for Binary Distributions @cindex HP-UX, binary distribution @cindex binary distributions, on HP-UX Some of the binary distributions of MySQL for HP-UX are distributed as an HP depot file and as a tar file. To use the depot file you must be running at least HP-UX 10.x to have access to HP's software depot tools. The HP version of MySQL was compiled on an HP 9000/8xx server under HP-UX 10.20, and uses MIT-pthreads. It is known to work well under this configuration. MySQL Version 3.22.26 and newer can also be built with HP's native thread package. Other configurations that may work: @itemize @bullet @item HP 9000/7xx running HP-UX 10.20+ @item HP 9000/8xx running HP-UX 10.30 @end itemize The following configurations almost definitely won't work: @itemize @bullet @item HP 9000/7xx or 8xx running HP-UX 10.x where x < 2 @item HP 9000/7xx or 8xx running HP-UX 9.x @end itemize To install the distribution, use one of the commands here, where @code{/path/to/depot} is the full pathname of the depot file: @itemize @bullet @item To install everything, including the server, client and development tools: @example shell> /usr/sbin/swinstall -s /path/to/depot mysql.full @end example @item To install only the server: @example shell> /usr/sbin/swinstall -s /path/to/depot mysql.server @end example @item To install only the client package: @example shell> /usr/sbin/swinstall -s /path/to/depot mysql.client @end example @item To install only the development tools: @example shell> /usr/sbin/swinstall -s /path/to/depot mysql.developer @end example @end itemize The depot places binaries and libraries in @file{/opt/mysql} and data in @file{/var/opt/mysql}. The depot also creates the appropriate entries in @file{/etc/init.d} and @file{/etc/rc2.d} to start the server automatically at boot time. Obviously, this entails being @code{root} to install. To install the HP-UX tar.gz distribution, you must have a copy of GNU @code{tar}. @node HP-UX 10.20, HP-UX 11.x, Binary notes-HP-UX, Other Unix Notes @subsubsection HP-UX Version 10.20 Notes There are a couple of small problems when compiling MySQL on HP-UX. We recommend that you use @code{gcc} instead of the HP-UX native compiler, because @code{gcc} produces better code! We recommend using gcc 2.95 on HP-UX. Don't use high optimisation flags (like -O6) as this may not be safe on HP-UX. The following configure line should work with gcc 2.95: @example CFLAGS="-I/opt/dce/include -fpic" \ CXXFLAGS="-I/opt/dce/include -felide-constructors -fno-exceptions \ -fno-rtti" CXX=gcc ./configure --with-pthread \ --with-named-thread-libs='-ldce' --prefix=/usr/local/mysql --disable-shared @end example The following configure line should work with gcc 3.1: @example CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc \ CXXFLAGS="-DHPUX -I/opt/dce/include -felide-constructors -fno-exceptions \ -fno-rtti -O3 -fPIC" ./configure --prefix=/usr/local/mysql \ --with-extra-charsets=complex --enable-thread-safe-client \ --enable-local-infile --with-pthread \ --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC --disable-shared @end example @node HP-UX 11.x, IBM-AIX, HP-UX 10.20, Other Unix Notes @subsubsection HP-UX Version 11.x Notes For HP-UX Version 11.x we recommend MySQL Version 3.23.15 or later. Because of some critical bugs in the standard HP-UX libraries, you should install the following patches before trying to run MySQL on HP-UX 11.0: @example PHKL_22840 Streams cumulative PHNE_22397 ARPA cumulative @end example This will solve the problem of getting @code{EWOULDBLOCK} from @code{recv()} and @code{EBADF} from @code{accept()} in threaded applications. If you are using @code{gcc} 2.95.1 on an unpatched HP-UX 11.x system, you will get the error: @example In file included from /usr/include/unistd.h:11, from ../include/global.h:125, from mysql_priv.h:15, from item.cc:19: /usr/include/sys/unistd.h:184: declaration of C function ... /usr/include/sys/pthread.h:440: previous declaration ... In file included from item.h:306, from mysql_priv.h:158, from item.cc:19: @end example The problem is that HP-UX doesn't define @code{pthreads_atfork()} consistently. It has conflicting prototypes in @file{/usr/include/sys/unistd.h}:184 and @file{/usr/include/sys/pthread.h}:440 (details below). One solution is to copy @file{/usr/include/sys/unistd.h} into @file{mysql/include} and edit @file{unistd.h} and change it to match the definition in @file{pthread.h}. Here's the diff: @example 183,184c183,184 < extern int pthread_atfork(void (*prepare)(), void (*parent)(), < void (*child)()); --- > extern int pthread_atfork(void (*prepare)(void), void (*parent)(void), > void (*child)(void)); @end example After this, the following configure line should work: @example CFLAGS="-fomit-frame-pointer -O3 -fpic" CXX=gcc \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti -O3" \ ./configure --prefix=/usr/local/mysql --disable-shared @end example If you are using MySQL 4.0.5 with the HP-UX compiler you can use: (tested with cc B.11.11.04): @example CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure --with-extra-character-set=complex @end example You can ignore any errors of the following type: @example aCC: warning 901: unknown option: `-3': use +help for online documentation @end example If you get the following error from @code{configure} @example checking for cc option to accept ANSI C... no configure: error: MySQL requires a ANSI C compiler (and a C++ compiler). Try gcc. See the Installation chapter in the Reference Manual. @end example Check that you don't have the path to the K&R compiler before the path to the HP-UX C and C++ compiler. Another reason for not beeing able to compile is that you didn't define the @code{+DD64} flags above. @node IBM-AIX, SunOS, HP-UX 11.x, Other Unix Notes @subsubsection IBM-AIX notes @cindex problems, installing on IBM-AIX Automatic detection of @code{xlC} is missing from Autoconf, so a @code{configure} command something like this is needed when compiling MySQL (This example uses the IBM compiler): @example export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 " export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192" export CFLAGS="-I /usr/local/include" export LDFLAGS="-L /usr/local/lib" export CPPFLAGS=$CFLAGS export CXXFLAGS=$CFLAGS ./configure --prefix=/usr/local \ --localstatedir=/var/mysql \ --sysconfdir=/etc/mysql \ --sbindir='/usr/local/bin' \ --libexecdir='/usr/local/bin' \ --enable-thread-safe-client \ --enable-large-files @end example Above are the options used to compile the MySQL distribution that can be found at @uref{http://www-frec.bull.com/}. If you change the @code{-O3} to @code{-O2} in the above configure line, you must also remove the @code{-qstrict} option (this is a limitation in the IBM C compiler). If you are using @code{gcc} or @code{egcs} to compile MySQL, you @strong{must} use the @code{-fno-exceptions} flag, as the exception handling in @code{gcc}/@code{egcs} is not thread-safe! (This is tested with @code{egcs} 1.1.) There are also some known problems with IBM's assembler, which may cause it to generate bad code when used with gcc. We recommend the following @code{configure} line with @code{egcs} and @code{gcc 2.95} on AIX: @example CC="gcc -pipe -mcpu=power -Wa,-many" \ CXX="gcc -pipe -mcpu=power -Wa,-many" \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql --with-low-memory @end example The @code{-Wa,-many} is necessary for the compile to be successful. IBM is aware of this problem but is in to hurry to fix it because of the workaround available. We don't know if the @code{-fno-exceptions} is required with @code{gcc 2.95}, but as MySQL doesn't use exceptions and the above option generates faster code, we recommend that you should always use this option with @code{egcs / gcc}. If you get a problem with assembler code try changing the -mcpu=xxx to match your CPU. Typically power2, power, or powerpc may need to be used, alternatively you might need to use 604 or 604e. I'm not positive but I would think using "power" would likely be safe most of the time, even on a power2 machine. If you don't know what your CPU is then do a "uname -m", this will give you back a string that looks like "000514676700", with a format of xxyyyyyymmss where xx and ss are always 0's, yyyyyy is a unique system id and mm is the id of the CPU Planar. A chart of these values can be found at @uref{http://publib.boulder.ibm.com/doc_link/en_US/a_doc_lib/cmds/aixcmds5/uname.htm}. This will give you a machine type and a machine model you can use to determine what type of CPU you have. If you have problems with signals (MySQL dies unexpectedly under high load) you may have found an OS bug with threads and signals. In this case you can tell MySQL not to use signals by configuring with: @example shell> CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \ -DDONT_USE_THR_ALARM" \ ./configure --prefix=/usr/local/mysql --with-debug --with-low-memory @end example This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are ``sleeping'' on a connection with @code{mysqladmin kill} or @code{mysqladmin shutdown}. Instead, the client will die when it issues its next command. On some versions of AIX, linking with @code{libbind.a} makes @code{getservbyname} core dump. This is an AIX bug and should be reported to IBM. For AIX 4.2.1 and gcc you have to do the following changes. After configuring, edit @file{config.h} and @file{include/my_config.h} and change the line that says @example #define HAVE_SNPRINTF 1 @end example to @example #undef HAVE_SNPRINTF @end example And finally, in @file{mysqld.cc} you need to add a prototype for initgoups. @example #ifdef _AIX41 extern "C" int initgroups(const char *,int); #endif @end example If you need to allocate a lot of memory to the mysqld process, it's not enough to just set 'ulimit -d unlimited'. You may also have to set in @code{mysqld_safe} something like: @example export LDR_CNTRL='MAXDATA=0x80000000' @end example You can find more about using a lot of memory at: @uref{http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/genprogc/lrg_prg_support.htm}. @node SunOS, Alpha-DEC-UNIX, IBM-AIX, Other Unix Notes @subsubsection SunOS 4 Notes On SunOS 4, MIT-pthreads is needed to compile MySQL, which in turn means you will need GNU @code{make}. Some SunOS 4 systems have problems with dynamic libraries and @code{libtool}. You can use the following @code{configure} line to avoid this problem: @example shell> ./configure --disable-shared --with-mysqld-ldflags=-all-static @end example When compiling @code{readline}, you may get warnings about duplicate defines. These may be ignored. When compiling @code{mysqld}, there will be some @code{implicit declaration of function} warnings. These may be ignored. @node Alpha-DEC-UNIX, Alpha-DEC-OSF1, SunOS, Other Unix Notes @subsubsection Alpha-DEC-UNIX Notes (Tru64) If you are using egcs 1.1.2 on Digital Unix, you should upgrade to gcc 2.95.2, as egcs on DEC has some serious bugs! When compiling threaded programs under Digital Unix, the documentation recommends using the @code{-pthread} option for @code{cc} and @code{cxx} and the libraries @code{-lmach -lexc} (in addition to @code{-lpthread}). You should run @code{configure} something like this: @example CC="cc -pthread" CXX="cxx -pthread -O" \ ./configure --with-named-thread-libs="-lpthread -lmach -lexc -lc" @end example When compiling @code{mysqld}, you may see a couple of warnings like this: @example mysqld.cc: In function void handle_connections()': mysqld.cc:626: passing long unsigned int *' as argument 3 of accept(int,sockadddr *, int *)' @end example You can safely ignore these warnings. They occur because @code{configure} can detect only errors, not warnings. If you start the server directly from the command-line, you may have problems with it dying when you log out. (When you log out, your outstanding processes receive a @code{SIGHUP} signal.) If so, try starting the server like this: @example shell> nohup mysqld [options] & @end example @code{nohup} causes the command following it to ignore any @code{SIGHUP} signal sent from the terminal. Alternatively, start the server by running @code{safe_mysqld}, which invokes @code{mysqld} using @code{nohup} for you. @xref{safe_mysqld, , @code{safe_mysqld}}. If you get a problem when compiling mysys/get_opt.c, just remove the line #define _NO_PROTO from the start of that file! If you are using Compac's CC compiler, the following configure line should work: @example CC="cc -pthread" CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed all -arch host" CXX="cxx -pthread" CXXFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed all -arch host \ -noexceptions -nortti" export CC CFLAGS CXX CXXFLAGS ./configure \ --prefix=/usr/local/mysql \ --with-low-memory \ --enable-large-files \ --enable-shared=yes \ --with-named-thread-libs="-lpthread -lmach -lexc -lc" gnumake @end example If you get a problem with libtool, when compiling with shared libraries as above, when linking @code{mysql}, you should be able to get around this by issuing: @example cd mysql /bin/sh ../libtool --mode=link cxx -pthread -O3 -DDBUG_OFF \ -O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all \ -arch host -DUNDEF_HAVE_GETHOSTBYNAME_R \ -o mysql mysql.o readline.o sql_string.o completion_hash.o \ ../readline/libreadline.a -lcurses \ ../libmysql/.libs/libmysqlclient.so -lm cd .. gnumake gnumake install scripts/mysql_install_db @end example @node Alpha-DEC-OSF1, SGI-Irix, Alpha-DEC-UNIX, Other Unix Notes @subsubsection Alpha-DEC-OSF/1 Notes If you have problems compiling and have DEC @code{CC} and @code{gcc} installed, try running @code{configure} like this: @example CC=cc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql @end example If you get problems with the @file{c_asm.h} file, you can create and use a 'dummy' @file{c_asm.h} file with: @example touch include/c_asm.h CC=gcc CFLAGS=-I./include \ CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql @end example Note that the following problems with the @code{ld} program can be fixed by downloading the latest DEC (Compaq) patch kit from: @uref{http://ftp.support.compaq.com/public/unix/}. On OSF/1 V4.0D and compiler "DEC C V5.6-071 on Digital Unix V4.0 (Rev. 878)" the compiler had some strange behaviour (undefined @code{asm} symbols). @code{/bin/ld} also appears to be broken (problems with @code{_exit undefined} errors occuring while linking @code{mysqld}). On this system, we have managed to compile MySQL with the following @code{configure} line, after replacing @code{/bin/ld} with the version from OSF 4.0C: @example CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql @end example With the Digital compiler "C++ V6.1-029", the following should work: @example CC=cc -pthread CFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all \ -arch host CXX=cxx -pthread CXXFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all \ -arch host -noexceptions -nortti export CC CFLAGS CXX CXXFLAGS ./configure --prefix=/usr/mysql/mysql --with-mysqld-ldflags=-all-static \ --disable-shared --with-named-thread-libs="-lmach -lexc -lc" @end example In some versions of OSF/1, the @code{alloca()} function is broken. Fix this by removing the line in @file{config.h} that defines @code{'HAVE_ALLOCA'}. The @code{alloca()} function also may have an incorrect prototype in @code{/usr/include/alloca.h}. This warning resulting from this can be ignored. @code{configure} will use the following thread libraries automatically: @code{--with-named-thread-libs="-lpthread -lmach -lexc -lc"}. When using @code{gcc}, you can also try running @code{configure} like this: @example shell> CFLAGS=-D_PTHREAD_USE_D4 CXX=gcc CXXFLAGS=-O3 ./configure ... @end example If you have problems with signals (MySQL dies unexpectedly under high load), you may have found an OS bug with threads and signals. In this case you can tell MySQL not to use signals by configuring with: @example shell> CFLAGS=-DDONT_USE_THR_ALARM \ CXXFLAGS=-DDONT_USE_THR_ALARM \ ./configure ... @end example This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are ``sleeping'' on a connection with @code{mysqladmin kill} or @code{mysqladmin shutdown}. Instead, the client will die when it issues its next command. With @code{gcc} 2.95.2, you will probably run into the following compile error: @example sql_acl.cc:1456: Internal compiler error in `scan_region', at except.c:2566 Please submit a full bug report. @end example To fix this you should change to the @code{sql} directory and do a ``cut and paste'' of the last @code{gcc} line, but change @code{-O3} to @code{-O0} (or add @code{-O0} immediately after @code{gcc} if you don't have any @code{-O} option on your compile line). After this is done you can just change back to the top-level directly and run @code{make} again. @node SGI-Irix, Caldera, Alpha-DEC-OSF1, Other Unix Notes @subsubsection SGI Irix Notes If you are using Irix Version 6.5.3 or newer @code{mysqld} will only be able to create threads if you run it as a user with @code{CAP_SCHED_MGT} privileges (like @code{root}) or give the @code{mysqld} server this privilege with the following shell command: @example shell> chcap "CAP_SCHED_MGT+epi" /opt/mysql/libexec/mysqld @end example You may have to undefine some things in @file{config.h} after running @code{configure} and before compiling. In some Irix implementations, the @code{alloca()} function is broken. If the @code{mysqld} server dies on some @code{SELECT} statements, remove the lines from @file{config.h} that define @code{HAVE_ALLOC} and @code{HAVE_ALLOCA_H}. If @code{mysqladmin create} doesn't work, remove the line from @file{config.h} that defines @code{HAVE_READDIR_R}. You may have to remove the @code{HAVE_TERM_H} line as well. SGI recommends that you install all of the patches on this page as a set: @uref{http://support.sgi.com/surfzone/patches/patchset/6.2_indigo.rps.html} At the very minimum, you should install the latest kernel rollup, the latest @code{rld} rollup, and the latest @code{libc} rollup. You definitely need all the POSIX patches on this page, for pthreads support: @uref{http://support.sgi.com/surfzone/patches/patchset/6.2_posix.rps.html} If you get the something like the following error when compiling @file{mysql.cc}: @example "/usr/include/curses.h", line 82: error(1084): invalid combination of type @end example Type the following in the top-level directory of your MySQL source tree: @example shell> extra/replace bool curses_bool < /usr/include/curses.h \ > include/curses.h shell> make @end example There have also been reports of scheduling problems. If only one thread is running, things go slow. Avoid this by starting another client. This may lead to a 2-to-10-fold increase in execution speed thereafter for the other thread. This is a poorly understood problem with Irix threads; you may have to improvise to find solutions until this can be fixed. If you are compiling with @code{gcc}, you can use the following @code{configure} command: @example CC=gcc CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql --enable-thread-safe-client \ --with-named-thread-libs=-lpthread @end example On Irix 6.5.11 with native Irix C and C++ compilers ver. 7.3.1.2, the following is reported to work @example CC=cc CXX=CC CFLAGS='-O3 -n32 -TARG:platform=IP22 -I/usr/local/include \ -L/usr/local/lib' CXXFLAGS='-O3 -n32 -TARG:platform=IP22 \ -I/usr/local/include -L/usr/local/lib' ./configure \ --prefix=/usr/local/mysql --with-innodb --with-berkeley-db \ --with-libwrap=/usr/local \ --with-named-curses-libs=/usr/local/lib/libncurses.a @end example @node Caldera, Caldera Unixware, SGI-Irix, Other Unix Notes @subsubsection Caldera (SCO) Notes The current port is tested only on a ``sco3.2v5.0.4'' and ``sco3.2v5.0.5'' system. There has also been a lot of progress on a port to ``sco 3.2v4.2''. For the moment the recommended compiler on OpenServer is gcc 2.95.2. With this you should be able to compile MySQL with just: @example CC=gcc CXX=gcc ./configure ... (options) @end example @enumerate @item For OpenServer 5.0.X you need to use gcc-2.95.2p1 or newer from the Skunkware. @uref{http://www.caldera.com/skunkware/} and choose browser OpenServer packages or by ftp to ftp2.caldera.com in the pub/skunkware/osr5/devtools/gcc directory. @item You need the port of GCC 2.5.x for this product and the Development system. They are required on this version of Caldera (SCO) Unix. You cannot just use the GCC Dev system. @item You should get the FSU Pthreads package and install it first. This can be found at @uref{http://www.cs.wustl.edu/~schmidt/ACE_wrappers/FSU-threads.tar.gz}. You can also get a precompiled package from @uref{http://www.mysql.com/Downloads/SCO/FSU-threads-3.5c.tar.gz}. @item FSU Pthreads can be compiled with Caldera (SCO) Unix 4.2 with tcpip. Or OpenServer 3.0 or Open Desktop 3.0 (OS 3.0 ODT 3.0), with the Caldera (SCO) Development System installed using a good port of GCC 2.5.x ODT or OS 3.0 you will need a good port of GCC 2.5.x There are a lot of problems without a good port. The port for this product requires the SCO Unix Development system. Without it, you are missing the libraries and the linker that is needed. @item To build FSU Pthreads on your system, do the following: @enumerate a @item Run @code{./configure} in the @file{threads/src} directory and select the SCO OpenServer option. This command copies @file{Makefile.SCO5} to @file{Makefile}. @item Run @code{make}. @item To install in the default @file{/usr/include} directory, login as root, then @code{cd} to the @file{thread/src} directory, and run @code{make install}. @end enumerate @item Remember to use GNU @code{make} when making MySQL. @item If you don't start @code{safe_mysqld} as root, you probably will get only the default 110 open files per process. @code{mysqld} will write a note about this in the log file. @item With SCO 3.2V5.0.5, you should use FSU Pthreads version 3.5c or newer. You should also use gcc 2.95.2 or newer! The following @code{configure} command should work: @example shell> ./configure --prefix=/usr/local/mysql --disable-shared @end example @item With SCO 3.2V4.2, you should use FSU Pthreads version 3.5c or newer. The following @code{configure} command should work: @example shell> CFLAGS="-D_XOPEN_XPG4" CXX=gcc CXXFLAGS="-D_XOPEN_XPG4" \ ./configure \ --prefix=/usr/local/mysql \ --with-named-thread-libs="-lgthreads -lsocket -lgen -lgthreads" \ --with-named-curses-libs="-lcurses" @end example You may get some problems with some include files. In this case, you can find new SCO-specific include files at @uref{http://www.mysql.com/Downloads/SCO/SCO-3.2v4.2-includes.tar.gz}. You should unpack this file in the @file{include} directory of your MySQL source tree. @end enumerate Caldera (SCO) development notes: @itemize @bullet @item MySQL should automatically detect FSU Pthreads and link @code{mysqld} with @code{-lgthreads -lsocket -lgthreads}. @item The Caldera (SCO) development libraries are re-entrant in FSU Pthreads. Caldera claim sthat its libraries' functions are re-entrant, so they must be reentrant with FSU Pthreads. FSU Pthreads on OpenServer tries to use the SCO scheme to make re-entrant libraries. @item FSU Pthreads (at least the version at @uref{http://www.mysql.com/}) comes linked with GNU @code{malloc}. If you encounter problems with memory usage, make sure that @file{gmalloc.o} is included in @file{libgthreads.a} and @file{libgthreads.so}. @item In FSU Pthreads, the following system calls are pthreads-aware: @code{read()}, @code{write()}, @code{getmsg()}, @code{connect()}, @code{accept()}, @code{select()}, and @code{wait()}. @item The CSSA-2001-SCO.35.2 (the patch is listed in custom as erg711905-dscr_remap security patch (version 2.0.0) breaks FSU threads and makes mysqld unstable. You have to remove this one if you want to run mysqld on an OpenServer 5.0.6 machine. @end itemize If you want to install DBI on Caldera (SCO), you have to edit the @file{Makefile} in DBI-xxx and each subdirectory. Note that the following assumes gcc 2.95.2 or newer: @example OLD: NEW: CC = cc CC = gcc CCCDLFLAGS = -KPIC -W1,-Bexport CCCDLFLAGS = -fpic CCDLFLAGS = -wl,-Bexport CCDLFLAGS = LD = ld LD = gcc -G -fpic LDDLFLAGS = -G -L/usr/local/lib LDDLFLAGS = -L/usr/local/lib LDFLAGS = -belf -L/usr/local/lib LDFLAGS = -L/usr/local/lib LD = ld LD = gcc -G -fpic OPTIMISE = -Od OPTIMISE = -O1 OLD: CCCFLAGS = -belf -dy -w0 -U M_XENIX -DPERL_SCO5 -I/usr/local/include NEW: CCFLAGS = -U M_XENIX -DPERL_SCO5 -I/usr/local/include @end example This is because the Perl dynaloader will not load the @code{DBI} modules if they were compiled with @code{icc} or @code{cc}. Perl works best when compiled with @code{cc}. @node Caldera Unixware, , Caldera, Other Unix Notes @subsubsection Caldera (SCO) Unixware Version 7.0 Notes You must use a version of MySQL at least as recent as Version 3.22.13 because that version fixes some portability problems under Unixware. We have been able to compile MySQL with the following @code{configure} command on Unixware Version 7.0.1: @example CC=cc CXX=CC ./configure --prefix=/usr/local/mysql @end example If you want to use @code{gcc}, you must use @code{gcc} 2.95.2 or newer. Caldera provides libsocket.so.2 at @uref{ftp://stage.caldera.com/pub/security/tools} for pre-OSR506 security fixes. Also, the telnetd fix at @url{ftp://stage.caldera.com/pub/security/openserver/CSSA-2001-SCO.10/} as both libsocket.so.2 and libresolv.so.1 with instructions for installing on pre-OSR506 systems. It's probably a good idea to install the above patches before trying to compile/use MySQL. @node OS/2, BeOS, Other Unix Notes, Operating System Specific Notes @subsection OS/2 Notes MySQL uses quite a few open files. Because of this, you should add something like the following to your @file{CONFIG.SYS} file: @example SET EMXOPT=-c -n -h1024 @end example If you don't do this, you will probably run into the following error: @example File 'xxxx' not found (Errcode: 24) @end example When using MySQL with OS/2 Warp 3, FixPack 29 or above is required. With OS/2 Warp 4, FixPack 4 or above is required. This is a requirement of the Pthreads library. MySQL must be installed in a partition that supports long filenames such as HPFS, FAT32, etc. The @file{INSTALL.CMD} script must be run from OS/2's own @file{CMD.EXE} and may not work with replacement shells such as @file{4OS2.EXE}. The @file{scripts/mysql-install-db} script has been renamed. It is now called @file{install.cmd} and is a REXX script, which will set up the default MySQL security settings and create the WorkPlace Shell icons for MySQL. Dynamic module support is compiled in but not fully tested. Dynamic modules should be compiled using the Pthreads run-time library. @example gcc -Zdll -Zmt -Zcrtdll=pthrdrtl -I../include -I../regex -I.. \ -o example udf_example.cc -L../lib -lmysqlclient udf_example.def mv example.dll example.udf @end example @strong{Note}: Due to limitations in OS/2, UDF module name stems must not exceed 8 characters. Modules are stored in the @file{/mysql2/udf} directory; the @code{safe-mysqld.cmd} script will put this directory in the @code{BEGINLIBPATH} environment variable. When using UDF modules, specified extensions are ignored@-it is assumed to be @file{.udf}. For example, in Unix, the shared module might be named @file{example.so} and you would load a function from it like this: @example mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "example.so"; @end example Is OS/2, the module would be named @file{example.udf}, but you would not specify the module extension: @example mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "example"; @end example @node BeOS, Novell Netware, OS/2, Operating System Specific Notes @subsection BeOS Notes We are really interested in getting MySQL to work on BeOS, but unfortunately we don't have any person who knows BeOS or has time to do a port. We are interested in finding someone to do a port, and we will help them with any technical questions they may have while doing the port. We have previously talked with some BeOS developers that have said that MySQL is 80% ported to BeOS, but we haven't heard from them in a while. @node Novell Netware, , BeOS, Operating System Specific Notes @subsection Novell NetWare Notes We are really interested in getting MySQL to work on NetWare, but unfortunately we don't have any person who knows NetWare or has time to do a port. We are interested in finding someone to do a port, and we will help them with any technical questions they may have while doing the port. @node Perl support, , Operating System Specific Notes, Installing @section Perl Installation Comments @cindex Perl, installing @cindex installing, Perl @menu * Perl installation:: Installing Perl on Unix * ActiveState Perl:: Installing ActiveState Perl on Windows * Windows Perl:: Installing the MySQL Perl distribution on Windows * Perl support problems:: Problems using the Perl @code{DBI}/@code{DBD} interface @end menu @node Perl installation, ActiveState Perl, Perl support, Perl support @subsection Installing Perl on Unix MySQLのPerlでの使用に関するサポートは @code{DBI}/@code{DBD}クライアントインターフェスの提供で行なわれます。 @xref{Perl}. @code{DBI}/@code{DBD}はPerl5.004かそれ以上のバージョンが必要になります。 古いバージョンのPerlでは@strong{動きません}。 MySQL の Perl support にはここまでで既にインストールが済んでいる筈の MySQL のクライアントプログラミングサポートが必要となります。 もしも RPM ファイルからインストールをされているのならば クライアントプログラムはクライアントRPMにあるものの、 クライアントプログラミングサポートはデベロッパー RPM にあります。 まずデベロッパー RPM をインストールされたがどうかお確かめ下さい。 バージョン3.22.8からは Perl support がメインの MySQL 配布ファイルとは別になっています。 もし Perl support が必要であれば @uref{http://www.mysql.com/downloads/api-dbi.html}. からお取りください。 Perl関係プログラムのの配布は@code{tar}形式圧縮ファイルとして行われており、 ファイル名が @file{MODULE-VERSION.tar.gz} の形式になっています。 ここで、@code{MODULE}はモジュール名称、@code{VERSION}はバージョン番号を表しています。 @code{Data-Dumper}、@code{DBI}、及び、@code{Msql-Mysql-modules}を入手してインストールしてください。 インストール手順は以下に示す通りです。なお、ここでは@code{Data-Dumper}のみの手順が示されていますが、 他のモジュールについても同様な手順でインストールできます。 @enumerate @item 以下のようにして作業ディレクトリで配布ファイルを伸長・展開してください。 @example shell> gunzip < Data-Dumper-VERSION.tar.gz | tar xvf - @end example This command creates a directory named @file{Data-Dumper-VERSION}. @item 展開先のトップディレクトリーに移動します。 @example shell> cd Data-Dumper-VERSION @end example @item コンパイル＆ビルドを行います。 @example shell> perl Makefile.PL shell> make shell> make test shell> make install @end example @end enumerate 出来上がったモジュールの動作を確認するために@code{make test}のコマンドは重要になってきます。 このコマンドを@code{Msql-Mysql-modules}をインストールしている時に使ってみてください。 MySQLサーバが動いていなければ失敗することになります。 MySQLをバージョンアップした際に @code{DBI} が core ダンプした場合は 必ず @code{Msql-Mysql-modules} を再コンパイルしてインストールしなおしてください。 そうでなくても MySQL のバージョンを変更した場合は再コンパイルしたほうが賢明です。 貴方のユーザ権限ではPerlのモジュールをインストールできない場合でも 以下の例のようにしてローカルディレクトリにモジュールをインストールできます。 @example @uref{http://www.iserver.com/support/contrib/perl5/modules.html} @end example @code{Installing New Modules that Require Locally Installed Modules}. という見出しの文書をご覧下さい。 @node ActiveState Perl, Windows Perl, Perl installation, Perl support @subsection Installing ActiveState Perl on Windows @cindex installing, Perl on Windows @cindex Perl, installing on Windows @cindex ActiveState Perl @code{DBD}モジュールとActiveState Perlをインストールするには以下の手順で行います。 @itemize @bullet @item ActiveState Perlはこのサイトからダウンロードできます。 @uref{http://www.activestate.com/Products/ActivePerl/} and install it. @item 先ず、DOSのシェルを立ち上げてください。 @item 必要であれば次のようにHTTP_proxy変数をセットしてください。 @example set HTTP_proxy=my.proxy.com:3128 @end example @item 次のようにPPMプログラムを立ち上げます。 @example C:\> c:\perl\bin\ppm.pl @end example @item @code{DBI}がインストールされていなければインストールします。 @example ppm> install DBI @end example @item ここまで来たら次のようなコマンドを実行してください。 @example install \ ftp://ftp.de.uu.net/pub/CPAN/authors/id/JWIED/DBD-mysql-1.2212.x86.ppd @end example @end itemize 以上でActiveState Perlのバージョン5.6がとりあえず動くことになります。 もしも動作しない場合は次のように @strong{MyODBC} ドライバーをインストールして ODBC経由でMySQLサーバに接続する必要があります。 @example use DBI; $dbh= DBI->connect("DBI:ODBC:$dsn","$user","$password") || die "Got error $DBI::errstr when connecting to $dsn\n"; @end example @node Windows Perl, Perl support problems, ActiveState Perl, Perl support @subsection Installing the MySQL Perl Distribution on Windows MySQL Perlの配布パッケージには@code{DBI}、@code{DBD:MySQL}、そして、@code{DBD:ODBC}が含まれています。 @itemize @bullet @item Windows 用 Perl の配布パッケージをこのサイトからダウンロードしてください。 @uref{http://www.mysql.com/downloads/os-win32.html}. @item @code{C:}で配布パッケージを解凍してください。@file{C:\PERL}に必要なファイルが現れます。 @item 次にコマンドパスに@file{C:\PERL\BIN}を追加してください。 @item ディレクトリ、@file{C:\PERL\BIN\MSWIN32-x86-thread} か @file{C:\PERL\BIN\MSWIN32-x86} もコマンドパスに追加してください。 @item @code{perl -v}と入力して@code{perl}の起動をチェックしてみましょう。 @end itemize @node Perl support problems, , Windows Perl, Perl support @subsection Problems Using the Perl @code{DBI}/@code{DBD} Interface @cindex problems, installing Perl @cindex Perl DBI/DBD, installation problems Perl が "@file{../mysql/mysql.so}を見つけられない" というメッセージを出した場合、 それは多分 Perl のシェアードライブラリ @file{libmysqlclient.so} を見つけることが出来ないのでしょう。 これは以下のような方法で解決できます。 @itemize @bullet @item @code{Msql-Mysql-modules}は通常、@code{perl Makefile.PL} とコンパイルされますが、 @code{perl Makefile.PL -static -config}とコンパイルしてください。 @item @file{libmysqlclient.so}をシェアードライブラリが置いてあるディレクトリにコピーしてください (通常は@file{/usr/lib}や@file{/lib}といったディレクトリになるはずです)。 @item Linux の場合は @file{/etc/ld.so.conf} ファイルを使って @file{libmysqlclient.so} のあるディレクトリを パスに追加することが出来ます。 @tindex LD_RUN_PATH environment variable @tindex Environment variable, LD_RUN_PATH @item @file{libmysqlclient.so}のあるディレクトリを@code{LD_RUN_PATH}に追加することによって そこへのパスが追加されます。 @end itemize @code{DBD-mysql} が次のようなエラーを発生する場合があります。 この原因の一つは @code{gcc}(又は@code{gcc}でコンパイルされた古いバイナリ配布パッケージ)をお使いのケースです。 @example /usr/bin/perl: can't resolve symbol '__moddi3' /usr/bin/perl: can't resolve symbol '__divdi3' @end example @file{mysql.so} ライブラリをビルドする時に @code{-L/usr/lib/gcc-lib/... -lgcc} を リンクコマンドに追加してください(@code{make}コマンド実行時の出力をチェックすれば確認できます。)。 オプション@code{-L}で指定されるのは@code{libgcc.a}のあるディレクトリになります。 もう一つの原因はPerlとMySQLのどちからが@code{gcc}でコンパイルされており、どちらかがそうでない場合です。 この場合はどちらも@code{gcc}でコンパイルし、この不一致を解消すれば解決します。 @code{Msql-Mysql-modules}がテストで次のようなエラーを出した時、 @example t/00base............install_driver(mysql) failed: Can't load '../blib/arch/auto/DBD/mysql/mysql.so' for module DBD::mysql: ../blib/arch/auto/DBD/mysql/mysql.so: undefined symbol: uncompress at /usr/lib/perl5/5.00503/i586-linux/DynaLoader.pm line 169. @end example これは、ファイル圧縮用ライブラリ -lz へのパスを追加すれば解決いたします。 @file{lib/DBD/mysql/Install.pm} に以下のような変更を行ってください。 @example $sysliblist .= " -lm"; to $sysliblist .= " -lm -lz"; @end example After this, you @strong{must} run 'make realclean' and then proceed with the installation from the beginning. このあと'make realclean'を実行し、最初からインストールをやり直す必要があります。 Caldera (SCO) のようなダイナミックリンクが使用できないシステムで Perl モジュールを使用する際は @code{DBI}や@code{DBD-mysql}をスタティックリンクしたバージョンのPerlを作成する必要があります。 @code{DBD}をスタティックにリンクするには、Perlのインストールディレクトリに @code{DBI}のプログラムを置き@code{DBD}をリンクし、インストールします。 Caldera (SCO) では以下のような環境変数をセットする必要があります。 @example shell> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/progressive/lib or shell> LD_LIBRARY_PATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:\ /usr/progressive/lib:/usr/skunk/lib shell> LIBPATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:\ /usr/progressive/lib:/usr/skunk/lib shell> MANPATH=scohelp:/usr/man:/usr/local1/man:/usr/local/man:\ /usr/skunk/man: @end example @code{DBI} をスタティックにリンクしたPerlを作成するためには、 先ず以下のコマンドを @code{DBI} がインストールされているディレクトリで実行してください。 @example shell> perl Makefile.PL -static -config shell> make shell> make install shell> make perl @end example 次に新しいPerlをインストールします。 通常 @code{make perl} でインストールに必要なファイル類を作成しますが、 Caldera (SCO)の場合は @code{make -f Makefile.aperl inst_perl MAP_TARGET=perl} のように行う必要があります。 次に、ここで作成された Perl で目的の @code{DBD::mysql} をスタティックにリンクされた Perl を作成するために使います。 @code{Msql-Mysql-modules} がインストールされたディレクトリで以下のようなコマンドを実行してください。 @example shell> perl Makefile.PL -static -config shell> make shell> make install shell> make perl @end example 最後に、この新しいPerlプログラムをインストールしてください。 @code{make perl}で必要なコマンドを再確認することができます。 @node Tutorial, MySQL Database Administration, Installing, Top @chapter Tutorial Introduction @cindex tutorial @cindex terminal monitor, defined @cindex monitor, terminal @cindex options, provided by MySQL @menu * Connecting-disconnecting:: Connecting to and disconnecting from the server * Entering queries:: Entering queries * Database use:: Creating and using a database * Getting information:: Getting information about databases and tables * Examples:: Examples * Batch mode:: Using @code{mysql} in batch mode * Twin:: Queries from twin project * Apache:: Using MySQL with Apache @end menu この章では、 @code{mysql} クライアントプログラムの使用の仕方と 単純なデータベースの作成と使用の仕方を例題としてとり上げます。 @code{mysql} (``terminal monitor'' や ``monitor'' として参照されます)は MySQL サーバーに接続できる対話モードのプログラムで、 クエリの実行や結果の表示が可能です。 @code{mysql} はバッチモードも可能です： クエリをまずファイルに書いておき、 そしてそのファイルを @code{mysql} に実行させます。 どちらの方法でも @code{mysql} はこの章の説明でカバーされます。 @code{mysql} の提供するオプションを見るには、 @code{--help} オプションを 実行します： @example shell> mysql --help @end example この章では @code{mysql} が既にあなたのマシンにインストールされているものとし、 また MySQL サーバーに接続可能であるとします。 もしそうでないなら、 あなたの MySQL 管理者に連絡を取ってください。 (もし@strong{あなた自身が}管理者なら、このマニュアルの他のセクションを参照してください。) 本章ではデータベース設定の全体のプロセス、データベースの使用について述べます。 もしあなたが既に存在しているデータベースにアクセスする事だけに興味があるなら、 この章のデータベース、テーブルの作成方法の説明を読み飛ばしてもかまいません。 この章が本質的にはチュートリアルであるので、多くの詳細は、かならず違う章にあります。 ここに書かれている事柄で、 さらに詳しい情報についてはマニュアルの適切なセクションを調べて下さい。 @node Connecting-disconnecting, Entering queries, Tutorial, Tutorial @section サーバーへの接続と切断 @cindex connecting, to the server @cindex disconnecting, from the server @cindex server, connecting @cindex server, disconnecting サーバーに @code{mysql} コマンドから接続するためには、通常、 MySQL ユーザ名、パスワードを指定する必要があるでしょう。 もしあなたがログインしている以外のマシンの上でサーバーが走っていれば、 あなたは、ホスト名を明示する必要があるでしょう。 まずあなたの管理者に問い合わせて、あなたが使うべき接続のためのパラメーターを見つけ出して下さい。 (すなわち、どのようなホスト、ユーザー名とパスワードを使うべきなのか。) 適切なパラメーターを知っていれば、あなたは、以下のようにして接続できます： @example shell> mysql -h host -u user -p Enter password: ******** @end example @code{********} とかかれている部分にはあなたのパスワードを入れます； @code{mysql} が @code{Enter password:} プロンプトを出したときに。 きちんと動けば、いくつかの情報と @code{mysql>} プロンプトが現れます： @example shell> mysql -h host -u user -p Enter password: ******** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 459 to server version: 3.22.20a-log Type 'help' for help. mysql> @end example このプロンプトは @code{mysql} がコマンド入力を待っている状態を示します。 いくつかの MySQL インストレーションでは、ローカルホストで 実行されているサーバーに、ユーザーに``匿名''(名前無し)の接続を許しています。 もしあなたのマシンがこの場合に当てはまるなら、@code{mysql} をオプション無しで 起動すべきです： @example shell> mysql @end example 接続が成功した後、 @code{mysql>} プロンプトで、@code{QUIT} とタイプすれば いつでも接続を切ることができます： @example mysql> QUIT Bye @end example Control-D で切断してもかまいません。 以下のセクションでのほとんどの例では、あなたがサーバーに接続しているものと しています。その場合は @code{mysql>} プロンプトによって、それを示しています。 @node Entering queries, Database use, Connecting-disconnecting, Tutorial @section Entering Queries @cindex running, queries @cindex queries, entering @cindex entering, queries 前のセクションで述べたように、あなたがサーバーとつながっていることを確かめて下さい。 この状態ではまだどんなデータベースも選択していない状態です。しかしそれはかまいません。 ここでは、テーブルの作成やデータの入力、取り出しよりも、 いかにクエリを発行するかに重点を置きます。 このセクションでは、あなた自身を @code{mysql} の動きに慣れさせるために、 あなたがやってみることができるであろう、いくつかのクエリを使用して、 コマンド入力の基本的な原則を述べます。 サーバーのバージョン、今日の日付をサーバーに問い合わせる、単純なコマンド がここにあります。 以下のように @code{mysql>} プロンプトの後に入力し RETURN キーを押してみてください： @example mysql> SELECT VERSION(), CURRENT_DATE; +--------------+--------------+ | VERSION() | CURRENT_DATE | +--------------+--------------+ | 3.22.20a-log | 1999-03-19 | +--------------+--------------+ 1 row in set (0.01 sec) mysql> @end example このクエリは、@code{mysql} のいくつかの事を説明しています： @itemize @bullet @item 通常、コマンドは、セミコロンで終わる SQL ステートメントから、構成されます。 (セミコロンが必要とされないいくつかの例外があります。 以前に述べた @code{QUIT} はそのうちの一つです。後で他も出てきます。) @item コマンドを発行すると、@code{mysql} はそれをサーバーに送り、結果を表示します。 その後、 @code{mysql>} プロンプトを出し、他のコマンドが受け付けれる状態であると 示します。 @item @code{mysql} はクエリの結果を表にして出します。 最初の行は項目のラベル名です。 その下の行に、クエリの結果が続きます。 通常、項目のラベル名はデータベースのテーブルから あなたが取り出したフィールド名になります。 テーブルのフィールド名以外の式を あなたが検索したのなら(ちょうど例のように)、@code{mysql} は与えられた式自身を 項目のラベル名として表示します。 @item @code{mysql} は何レコード(rows)返ってきたかを示し、実行にどれくらいの時間が かかったかも示します。 これはおおざっぱなサーバーのパフォーマンスを示します。 これらの値は wall clock time (CPU や マシンタイムではなく) を使用しており、さらに、 サーバーの負荷、およびネットワーク待ち時間といった要因にも影響されるので、 不正確です。 (この章の他の例題においては ``rows in set'' の行は省きます。) @end itemize キーワードは、いかなる大文字小文字でも記述できます。 以下に示すクエリは同じです： @example mysql> SELECT VERSION(), CURRENT_DATE; mysql> select version(), current_date; mysql> SeLeCt vErSiOn(), current_DATE; @end example 以下のクエリは、@code{mysql} を簡単な計算機として使用した例です： @example mysql> SELECT SIN(PI()/4), (4+1)*5; +-------------+---------+ | SIN(PI()/4) | (4+1)*5 | +-------------+---------+ | 0.707107 | 25 | +-------------+---------+ @end example 今までは見てきたたコマンドは、比較的短い、一行のの文です。 あなたは一行に複数、文を書くことが出来ます。 それぞれの文の終わりにはセミコロンを付けます： @example mysql> SELECT VERSION(); SELECT NOW(); +--------------+ | VERSION() | +--------------+ | 3.22.20a-log | +--------------+ +---------------------+ | NOW() | +---------------------+ | 1999-03-19 00:15:33 | +---------------------+ @end example コマンドは一行にかく必要もありません。 複数行にわたる長いコマンドでも問題ありません。 @code{mysql} はセミコロンで、一文の終わりと見なします。 その行の最後を文の最後とは 見なしません。 （いうなれば、@code{mysql} は自由な入力を許し、セミコロンが現れるまでは それらの入力された行を実行しません） 複数行にまたがった文の例です： @example mysql> SELECT -> USER() -> , -> CURRENT_DATE; +--------------------+--------------+ | USER() | CURRENT_DATE | +--------------------+--------------+ | joesmith@@localhost | 1999-03-18 | +--------------------+--------------+ @end example この例では、複数にまたがるクエリにおいて、最初の行の入力のあと、 いかにプロンプトが @code{mysql>} から @code{->} に変わるかを示しています。 これは @code{mysql} が、まだ文が終わっておらず、残りの部分の入力を待っている ことを示します。プロンプトは役立つフィードバックを提供してくれるあなたの友 人です。そのフィードバックを使用すると、@code{mysql} が何を待っているのか にいつも気が付くでしょう。 入力中にコマンドの実行を取りやめようと思った場合、 @code{\c} でこれをキャンセルできます： @example mysql> SELECT -> USER() -> \c mysql> @end example ここでもプロンプトに注意してください。@code{\c} のタイプ後に @code{mysql>} に戻っています。@code{mysql} が新しいコマンドの準備ができた ことを示すフィードバックを提供しています。 次のテーブルはあなたが目にするであろう各プロンプトと、それらが意味する @code{mysql} がどの状態にあるかについての要約です: @cindex prompts, meanings @multitable @columnfractions .10 .80 @item @strong{プロンプト} @tab @strong{意味} @item @code{mysql>} @tab 新しいコマンドの待状態 @item @code{@ @ @ @ ->} @tab 複数行にまたがるコマンドの、次の行の入力を待っている状態。 @item @code{@ @ @ @ '>} @tab シングルクオート (@samp{'}) で始められた文字の、次の行の入力を待っている状態。 @item @code{@ @ @ @ ">} @tab ダブルクオート (@samp{"}) で始められた文字の、次の行の入力を待っている状態。 @end multitable あなたが文をセミコロンで終わらすことを忘れて実行した場合に、 複数行の入力待ちが起こります。 この場合、 @code{mysql} は 次の入力を待ちます： @example mysql> SELECT USER() -> @end example If this happens to you (you think you've entered a statement but the only response is a @code{->} prompt), most likely @code{mysql} is waiting for the semicolon. If you don't notice what the prompt is telling you, you might sit there for a while before realising what you need to do. Enter a semicolon to complete the statement, and @code{mysql} will execute it: @example mysql> SELECT USER() -> ; +--------------------+ | USER() | +--------------------+ | joesmith@@localhost | +--------------------+ @end example The @code{'>} and @code{">} prompts occur during string collection. In MySQL, you can write strings surrounded by either @samp{'} or @samp{"} characters (for example, @code{'hello'} or @code{"goodbye"}), and @code{mysql} lets you enter strings that span multiple lines. When you see a @code{'>} or @code{">} prompt, it means that you've entered a line containing a string that begins with a @samp{'} or @samp{"} quote character, but have not yet entered the matching quote that terminates the string. That's fine if you really are entering a multiple-line string, but how likely is that? Not very. More often, the @code{'>} and @code{">} prompts indicate that you've inadvertantly left out a quote character. For example: @example mysql> SELECT * FROM my_table WHERE name = "Smith AND age < 30; "> @end example If you enter this @code{SELECT} statement, then press Enter and wait for the result, nothing will happen. Instead of wondering why this query takes so long, notice the clue provided by the @code{">} prompt. It tells you that @code{mysql} expects to see the rest of an unterminated string. (Do you see the error in the statement? The string @code{"Smith} is missing the second quote.) At this point, what do you do? The simplest thing is to cancel the command. However, you cannot just type @code{\c} in this case, because @code{mysql} interprets it as part of the string that it is collecting! Instead, enter the closing quote character (so @code{mysql} knows you've finished the string), then type @code{\c}: @example mysql> SELECT * FROM my_table WHERE name = "Smith AND age < 30; "> "\c mysql> @end example The prompt changes back to @code{mysql>}, indicating that @code{mysql} is ready for a new command. It's important to know what the @code{'>} and @code{">} prompts signify, because if you mistakenly enter an unterminated string, any further lines you type will appear to be ignored by @code{mysql}@-including a line containing @code{QUIT}! This can be quite confusing, especially if you don't know that you need to supply the terminating quote before you can cancel the current command. @node Database use, Getting information, Entering queries, Tutorial @section Creating and Using a Database @cindex databases, creating @cindex databases, using @cindex creating, databases @menu * Creating database:: Creating a database * Creating tables:: Creating a table * Loading tables:: Loading data into a table * Retrieving data:: Retrieving information from a table @end menu Now that you know how to enter commands, it's time to access a database. Suppose you have several pets in your home (your menagerie) and you'd like to keep track of various types of information about them. You can do so by creating tables to hold your data and loading them with the desired information. Then you can answer different sorts of questions about your animals by retrieving data from the tables. This section shows you how to: @itemize @bullet @item Create a database @item Create a table @item Load data into the table @item Retrieve data from the table in various ways @item Use multiple tables @end itemize The menagerie database will be simple (deliberately), but it is not difficult to think of real-world situations in which a similar type of database might be used. For example, a database like this could be used by a farmer to keep track of livestock, or by a veterinarian to keep track of patient records. A menagerie distribution containing some of the queries and sample data used in the following sections can be obtained from the MySQL web site. It's available in either compressed @code{tar} format (@uref{http://www.mysql.com/Downloads/Contrib/Examples/menagerie.tar.gz}) or Zip format (@uref{http://www.mysql.com/Downloads/Contrib/Examples/menagerie.zip}). Use the @code{SHOW} statement to find out what databases currently exist on the server: @example mysql> SHOW DATABASES; +----------+ | Database | +----------+ | mysql | | test | | tmp | +----------+ @end example The list of databases is probably different on your machine, but the @code{mysql} and @code{test} databases are likely to be among them. The @code{mysql} database is required because it describes user access privileges. The @code{test} database is often provided as a workspace for users to try things out. Note that you may not see all databases if you don't have the @code{SHOW DATABASES} privilege. @xref{GRANT}. If the @code{test} database exists, try to access it: @example mysql> USE test Database changed @end example Note that @code{USE}, like @code{QUIT}, does not require a semicolon. (You can terminate such statements with a semicolon if you like; it does no harm.) The @code{USE} statement is special in another way, too: it must be given on a single line. You can use the @code{test} database (if you have access to it) for the examples that follow, but anything you create in that database can be removed by anyone else with access to it. For this reason, you should probably ask your MySQL administrator for permission to use a database of your own. Suppose you want to call yours @code{menagerie}. The administrator needs to execute a command like this: @example mysql> GRANT ALL ON menagerie.* TO your_mysql_name; @end example where @code{your_mysql_name} is the MySQL user name assigned to you. @node Creating database, Creating tables, Database use, Database use @subsection Creating and Selecting a Database @cindex selecting, databases @cindex databases, selecting If the administrator creates your database for you when setting up your permissions, you can begin using it. Otherwise, you need to create it yourself: @example mysql> CREATE DATABASE menagerie; @end example Under Unix, database names are case-sensitive (unlike SQL keywords), so you must always refer to your database as @code{menagerie}, not as @code{Menagerie}, @code{MENAGERIE}, or some other variant. This is also true for table names. (Under Windows, this restriction does not apply, although you must refer to databases and tables using the same lettercase throughout a given query.) Creating a database does not select it for use; you must do that explicitly. To make @code{menagerie} the current database, use this command: @example mysql> USE menagerie Database changed @end example Your database needs to be created only once, but you must select it for use each time you begin a @code{mysql} session. You can do this by issuing a @code{USE} statement as shown above. Alternatively, you can select the database on the command-line when you invoke @code{mysql}. Just specify its name after any connection parameters that you might need to provide. For example: @example shell> mysql -h host -u user -p menagerie Enter password: ******** @end example Note that @code{menagerie} is not your password on the command just shown. If you want to supply your password on the command-line after the @code{-p} option, you must do so with no intervening space (for example, as @code{-pmypassword}, not as @code{-p mypassword}). However, putting your password on the command-line is not recommended, because doing so exposes it to snooping by other users logged in on your machine. @node Creating tables, Loading tables, Creating database, Database use @subsection テーブルの作成 @cindex tables, creating @cindex creating, tables データベースを作成することは容易ですが、作成しただけでは中身はからっぽです。 例えば @code{SHOW TABLES} を実行してみると以下のようになるでしょう: @example mysql> SHOW TABLES; Empty set (0.00 sec) @end example 難しいのはデータベースの構造をどうするかを決定することです。 どんなテーブルが必要で、その中にどんな要素を入れるかです。 まずそれぞれのペットに関するレコードを含んだテーブルが必要でしょう。 これは @code{pet} テーブルとしましょう。 そしてその中には、最低でもそれぞれの動物の名前は入れる必要があるでしょう。 名前だけではあまり面白くないのでその他の情報も入れることにしましょう。例えば、もし家族の２人以上がペットを買っているならば、飼い主の名前も入れたくなるでしょう。 またその他にもペットの種類や性別など、いくつかの基本的な情報も入れたくなるかもしれません。 年齢はどうでしょうか？ 確かにいいかもしれませんが、データベースに蓄積するにはあまり良くないものです。 年齢は時とともに変化します。つまりその都度レコードを更新する必要があるということです。 これに代わるデータとして適切なのは、例えば誕生日です。 そうしておいて年齢が必要なときは今日の日付と誕生日から計算すればよいのです。 MySQL には日付を算術演算する関数がありますので、難しいことはありません。 年齢ではなくて誕生日を記録しておくことには他のメリットもあります。 @itemize @bullet @item ペットの誕生日が近づいてきたことを知らせてくれる目的にもこのデータベースは使えることになります。 （下らないと思う人は、仕事上の付き合いの関係で、 顧客データベースから誕生日のお祝いメッセージを送らないといけない顧客を割り出す仕事を想定してみてください。） @item 今日の日付以外に、関係する日付からも年齢の計算が出来ます。 例えば、もしペットが死亡した日をデータベースに入れておけば、 そのペットが何歳で死んだのかも簡単に計算することが出来ます。 @end itemize その他にも @code{pet} テーブルに加えるべき有用な情報はいろいろあるでしょう。 しかしとりあえずはこの辺で十分としましょう。名前、飼い主、種類、性別、誕生日、そして死亡日です。 @code{CREATE TABLE} 文を使ってテーブルのレイアウトを指定しましょう： @example mysql> CREATE TABLE pet (name VARCHAR(20), owner VARCHAR(20), -> species VARCHAR(20), sex CHAR(1), birth DATE, death DATE); @end example @code{name}, @code{owner},そして@code{species} フィールドには @code{VARCHAR} を用いた方がよいでしょう。なぜならこれらの値の長さは変化するからです。 これらのフィールドの長さは全て同じである必要もなく、@code{20}文字である必要もありません。 @code{1}から@code{255}の間でもっともリーズナブルな値を選べばよいでしょう。 （長さの選択を誤ってあとで文字数が足らなくなったとしても、 MySQLは @code{ALTER TABLE} で長さを変えることができます） 動物の性別を表す値にはいくつかのタイプが考えられます。 @code{"m"} と @code{"f"} 、あるいは@code{"male"} と @code{"female"} なども考えられるでしょう。 ここでは最も簡単に、一文字の @code{"m"} と @code{"f"} で表すことにしましょう。 @code{birth} と @code{death} のフィールドには、明らかに @code{DATE} データ型を用いるべきでしょう。 テーブルを作ってみると、@code{SHOW TABLES} で何らかの出力が得られるはずです： @example mysql> SHOW TABLES; +---------------------+ | Tables in menagerie | +---------------------+ | pet | +---------------------+ @end example テーブルが期待したとおりに作成されたかどうかをチェックするために、 @code{DESCRIBE} 文を使います： @example mysql> DESCRIBE pet; +---------+-------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------+-------------+------+-----+---------+-------+ | name | varchar(20) | YES | | NULL | | | owner | varchar(20) | YES | | NULL | | | species | varchar(20) | YES | | NULL | | | sex | char(1) | YES | | NULL | | | birth | date | YES | | NULL | | | death | date | YES | | NULL | | +---------+-------------+------+-----+---------+-------+ @end example @code{DESCRIBE} 文はいつでも、 例えばテーブルの列の名前やそのタイプを忘れてしまったときにも使うことが出来ます。 @node Loading tables, Retrieving data, Creating tables, Database use @subsection ファイルからデータをテーブルへ取り込む @cindex loading, tables @cindex tables, loading data @cindex data, loading into tables テーブルを作ったら、中にデータを入れる必要があります。 このとき @code{LOAD DATA} 文と@code{INSERT} 文を用いると便利です。 例えばあなたのペットに関する記録が以下のようになっていたとします。 （MySQLにおける日付の表記が @code{'YYYY-MM-DD'} の形式になっていることに注意してください。 あなたが慣れている形式とは異なるかもしれません） @multitable @columnfractions .10 .10 .10 .05 .15 .15 @item @strong{name} @tab @strong{owner} @tab @strong{species} @tab @strong{sex} @tab @strong{birth} @tab @strong{death} @item Fluffy @tab Harold @tab cat @tab f @tab 1993-02-04 @tab @item Claws @tab Gwen @tab cat @tab m @tab 1994-03-17 @tab @item Buffy @tab Harold @tab dog @tab f @tab 1989-05-13 @tab @item Fang @tab Benny @tab dog @tab m @tab 1990-08-27 @tab @item Bowser @tab Diane @tab dog @tab m @tab 1998-08-31 @tab 1995-07-29 @item Chirpy @tab Gwen @tab bird @tab f @tab 1998-09-11 @tab @item Whistler @tab Gwen @tab bird @tab @tab 1997-12-09 @tab @item Slim @tab Benny @tab snake @tab m @tab 1996-04-29 @tab @end multitable もし空のテーブルから作り始めるのなら、 一行に一つのペットのデータを記述したテキストファイルを作っておいて、 先に挙げた命令で中身を読み込ませると楽です。 そのファイルを @file{pet.txt} とします。 各レコードを一行ずつ書き、各項目はタブで区切ります。 項目の順番は @code{CREATE TABLE} 文で定義したときと同じ順番とします。 項目が空のときは（例えばペットがまだ生きている場合、死亡日欄は空白です） @code{NULL} を用いることが出来ます。ファイル中では @code{\N} を用います。 例えば鳥の Whistler のレコードは以下のようになります。（項目の間の空白はタブ１個です）: @multitable @columnfractions .10 .10 .10 .05 .15 .15 @item @strong{name} @tab @strong{owner} @tab @strong{species} @tab @strong{sex} @tab @strong{birth} @tab @strong{death} @item @code{Whistler} @tab @code{Gwen} @tab @code{bird} @tab @code{\N} @tab @code{1997-12-09} @tab @code{\N} @end multitable このファイル @file{pet.txt} をテーブル @code{pet} に読み込むには、以下のコマンドを用います： @example mysql> LOAD DATA LOCAL INFILE "pet.txt" INTO TABLE pet; @end example もし必要であれば、項目の区切りや行末の符号を @code{LOAD DATA} 文で明示的に定めることが出来ます。 デフォルトでは区切りはタブ、行末はラインフィードです。 これにより @file{pet.txt} を適切に読み込むことが出来ます。 また新しい複数のレコードを１個づつ追加したいときは @code{INSERT} が便利です。 それぞれの項を @code{CREATE TABLE} で定義したときと同じ順番で入力するだけで追加できます。 例えばDianeが新しくハムスターをもらってきてPuffballと名づけました。 @code{INSERT} を用いて以下のようにレコードを追加することが出来ます： @example mysql> INSERT INTO pet -> VALUES ('Puffball','Diane','hamster','f','1999-03-30',NULL); @end example 文字列や日付を引用符号で括っていることに注意してください。 また @code{INSERT} を用いて空白の項を入力するときには @code{NULL} を直接挿入することができます。 @code{LOAD DATA} を使っているときとは違って @code{\N} は使えません。 この例から、初めにレコードを @code{INSERT} 文で入力するのは、 @code{LOAD DATA} 文を用いるよりも相当多くのタイピングを要してしまうことがわかると思います。 @node Retrieving data, , Loading tables, Database use @subsection Retrieving Information from a Table @cindex data, retrieving @cindex tables, retrieving data @cindex retrieving, data from tables @cindex unloading, tables @menu * Selecting all:: Selecting all data * Selecting rows:: Selecting particular rows * Selecting columns:: Selecting particular columns * Sorting rows:: Sorting rows * Date calculations:: Date calculations * Working with NULL:: Working with @code{NULL} values * Pattern matching:: Pattern matching * Counting rows:: Counting rows * Multiple tables:: Using More Than one Table @end menu The @code{SELECT} statement is used to pull information from a table. The general form of the statement is: @example SELECT what_to_select FROM which_table WHERE conditions_to_satisfy @end example @code{what_to_select} indicates what you want to see. This can be a list of columns, or @code{*} to indicate ``all columns.'' @code{which_table} indicates the table from which you want to retrieve data. The @code{WHERE} clause is optional. If it's present, @code{conditions_to_satisfy} specifies conditions that rows must satisfy to qualify for retrieval. @node Selecting all, Selecting rows, Retrieving data, Retrieving data @subsubsection Selecting All Data The simplest form of @code{SELECT} retrieves everything from a table: @example mysql> SELECT * FROM pet; +----------+--------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +----------+--------+---------+------+------------+------------+ | Fluffy | Harold | cat | f | 1993-02-04 | NULL | | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | | Fang | Benny | dog | m | 1990-08-27 | NULL | | Bowser | Diane | dog | m | 1998-08-31 | 1995-07-29 | | Chirpy | Gwen | bird | f | 1998-09-11 | NULL | | Whistler | Gwen | bird | NULL | 1997-12-09 | NULL | | Slim | Benny | snake | m | 1996-04-29 | NULL | | Puffball | Diane | hamster | f | 1999-03-30 | NULL | +----------+--------+---------+------+------------+------------+ @end example This form of @code{SELECT} is useful if you want to review your entire table, for instance, after you've just loaded it with your initial dataset. As it happens, the output just shown reveals an error in your datafile: Bowser appears to have been born after he died! Consulting your original pedigree papers, you find that the correct birth year is 1989, not 1998. There are least a couple of ways to fix this: @itemize @bullet @item Edit the file @file{pet.txt} to correct the error, then empty the table and reload it using @code{DELETE} and @code{LOAD DATA}: @example mysql> SET AUTOCOMMIT=1; # Used for quick re-create of the table mysql> DELETE FROM pet; mysql> LOAD DATA LOCAL INFILE "pet.txt" INTO TABLE pet; @end example However, if you do this, you must also re-enter the record for Puffball. @item Fix only the erroneous record with an @code{UPDATE} statement: @example mysql> UPDATE pet SET birth = "1989-08-31" WHERE name = "Bowser"; @end example @end itemize As shown above, it is easy to retrieve an entire table. But typically you don't want to do that, particularly when the table becomes large. Instead, you're usually more interested in answering a particular question, in which case you specify some constraints on the information you want. Let's look at some selection queries in terms of questions about your pets that they answer. @node Selecting rows, Selecting columns, Selecting all, Retrieving data @subsubsection Selecting Particular Rows @cindex rows, selecting @cindex tables, selecting rows You can select only particular rows from your table. For example, if you want to verify the change that you made to Bowser's birth date, select Bowser's record like this: @example mysql> SELECT * FROM pet WHERE name = "Bowser"; +--------+-------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +--------+-------+---------+------+------------+------------+ | Bowser | Diane | dog | m | 1989-08-31 | 1995-07-29 | +--------+-------+---------+------+------------+------------+ @end example The output confirms that the year is correctly recorded now as 1989, not 1998. String comparisons are normally case-insensitive, so you can specify the name as @code{"bowser"}, @code{"BOWSER"}, etc. The query result will be the same. You can specify conditions on any column, not just @code{name}. For example, if you want to know which animals were born after 1998, test the @code{birth} column: @example mysql> SELECT * FROM pet WHERE birth >= "1998-1-1"; +----------+-------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +----------+-------+---------+------+------------+-------+ | Chirpy | Gwen | bird | f | 1998-09-11 | NULL | | Puffball | Diane | hamster | f | 1999-03-30 | NULL | +----------+-------+---------+------+------------+-------+ @end example You can combine conditions, for example, to locate female dogs: @example mysql> SELECT * FROM pet WHERE species = "dog" AND sex = "f"; +-------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +-------+--------+---------+------+------------+-------+ | Buffy | Harold | dog | f | 1989-05-13 | NULL | +-------+--------+---------+------+------------+-------+ @end example The preceding query uses the @code{AND} logical operator. There is also an @code{OR} operator: @example mysql> SELECT * FROM pet WHERE species = "snake" OR species = "bird"; +----------+-------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +----------+-------+---------+------+------------+-------+ | Chirpy | Gwen | bird | f | 1998-09-11 | NULL | | Whistler | Gwen | bird | NULL | 1997-12-09 | NULL | | Slim | Benny | snake | m | 1996-04-29 | NULL | +----------+-------+---------+------+------------+-------+ @end example @code{AND} and @code{OR} may be intermixed. If you do that, it's a good idea to use parentheses to indicate how conditions should be grouped: @example mysql> SELECT * FROM pet WHERE (species = "cat" AND sex = "m") -> OR (species = "dog" AND sex = "f"); +-------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +-------+--------+---------+------+------------+-------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +-------+--------+---------+------+------------+-------+ @end example @node Selecting columns, Sorting rows, Selecting rows, Retrieving data @subsubsection Selecting Particular Columns @cindex columns, selecting @cindex tables, selecting columns If you don't want to see entire rows from your table, just name the columns in which you're interested, separated by commas. For example, if you want to know when your animals were born, select the @code{name} and @code{birth} columns: @example mysql> SELECT name, birth FROM pet; +----------+------------+ | name | birth | +----------+------------+ | Fluffy | 1993-02-04 | | Claws | 1994-03-17 | | Buffy | 1989-05-13 | | Fang | 1990-08-27 | | Bowser | 1989-08-31 | | Chirpy | 1998-09-11 | | Whistler | 1997-12-09 | | Slim | 1996-04-29 | | Puffball | 1999-03-30 | +----------+------------+ @end example To find out who owns pets, use this query: @example mysql> SELECT owner FROM pet; +--------+ | owner | +--------+ | Harold | | Gwen | | Harold | | Benny | | Diane | | Gwen | | Gwen | | Benny | | Diane | +--------+ @end example @findex DISTINCT However, notice that the query simply retrieves the @code{owner} field from each record, and some of them appear more than once. To minimise the output, retrieve each unique output record just once by adding the keyword @code{DISTINCT}: @example mysql> SELECT DISTINCT owner FROM pet; +--------+ | owner | +--------+ | Benny | | Diane | | Gwen | | Harold | +--------+ @end example You can use a @code{WHERE} clause to combine row selection with column selection. For example, to get birth dates for dogs and cats only, use this query: @example mysql> SELECT name, species, birth FROM pet -> WHERE species = "dog" OR species = "cat"; +--------+---------+------------+ | name | species | birth | +--------+---------+------------+ | Fluffy | cat | 1993-02-04 | | Claws | cat | 1994-03-17 | | Buffy | dog | 1989-05-13 | | Fang | dog | 1990-08-27 | | Bowser | dog | 1989-08-31 | +--------+---------+------------+ @end example @node Sorting rows, Date calculations, Selecting columns, Retrieving data @subsubsection Sorting Rows @cindex rows, sorting @cindex sorting, table rows @cindex sorting, data @cindex tables, sorting rows You may have noticed in the preceding examples that the result rows are displayed in no particular order. However, it's often easier to examine query output when the rows are sorted in some meaningful way. To sort a result, use an @code{ORDER BY} clause. Here are animal birthdays, sorted by date: @example mysql> SELECT name, birth FROM pet ORDER BY birth; +----------+------------+ | name | birth | +----------+------------+ | Buffy | 1989-05-13 | | Bowser | 1989-08-31 | | Fang | 1990-08-27 | | Fluffy | 1993-02-04 | | Claws | 1994-03-17 | | Slim | 1996-04-29 | | Whistler | 1997-12-09 | | Chirpy | 1998-09-11 | | Puffball | 1999-03-30 | +----------+------------+ @end example On character type columns, sorting@-like all other comparison operations@-is normally performed in a case-insensitive fashion. This means that the order will be undefined for columns that are identical except for their case. You can force a case-sensitive sort by using the BINARY cast: @code{ORDER BY BINARY(field)}. To sort in reverse order, add the @code{DESC} (descending) keyword to the name of the column you are sorting by: @example mysql> SELECT name, birth FROM pet ORDER BY birth DESC; +----------+------------+ | name | birth | +----------+------------+ | Puffball | 1999-03-30 | | Chirpy | 1998-09-11 | | Whistler | 1997-12-09 | | Slim | 1996-04-29 | | Claws | 1994-03-17 | | Fluffy | 1993-02-04 | | Fang | 1990-08-27 | | Bowser | 1989-08-31 | | Buffy | 1989-05-13 | +----------+------------+ @end example You can sort on multiple columns. For example, to sort by type of animal, then by birth date within animal type with youngest animals first, use the following query: @example mysql> SELECT name, species, birth FROM pet ORDER BY species, birth DESC; +----------+---------+------------+ | name | species | birth | +----------+---------+------------+ | Chirpy | bird | 1998-09-11 | | Whistler | bird | 1997-12-09 | | Claws | cat | 1994-03-17 | | Fluffy | cat | 1993-02-04 | | Fang | dog | 1990-08-27 | | Bowser | dog | 1989-08-31 | | Buffy | dog | 1989-05-13 | | Puffball | hamster | 1999-03-30 | | Slim | snake | 1996-04-29 | +----------+---------+------------+ @end example Note that the @code{DESC} keyword applies only to the column name immediately preceding it (@code{birth}); @code{species} values are still sorted in ascending order. @node Date calculations, Working with NULL, Sorting rows, Retrieving data @subsubsection 日付の計算 @cindex date calculations @cindex calculating, dates @cindex extracting, dates @cindex age, calculating MySQL はいくつかの日付の計算を行う関数を提供します。 例えば、年の計算や日付の部分を取り出したり。 To determine how many years old each of your pets is, compute the difference in the year part of the current date and the birth date, then subtract one if the current date occurs earlier in the calendar year than the birth date. The following query shows, for each pet, the birth date, the current date, and the age in years. @example mysql> SELECT name, birth, CURRENT_DATE, -> (YEAR(CURRENT_DATE)-YEAR(birth)) -> - (RIGHT(CURRENT_DATE,5) AS age -> FROM pet; +----------+------------+--------------+------+ | name | birth | CURRENT_DATE | age | +----------+------------+--------------+------+ | Fluffy | 1993-02-04 | 2001-08-29 | 8 | | Claws | 1994-03-17 | 2001-08-29 | 7 | | Buffy | 1989-05-13 | 2001-08-29 | 12 | | Fang | 1990-08-27 | 2001-08-29 | 11 | | Bowser | 1989-08-31 | 2001-08-29 | 11 | | Chirpy | 1998-09-11 | 2001-08-29 | 2 | | Whistler | 1997-12-09 | 2001-08-29 | 3 | | Slim | 1996-04-29 | 2001-08-29 | 5 | | Puffball | 1999-03-30 | 2001-08-29 | 2 | +----------+------------+--------------+------+ @end example Here, @code{YEAR()} pulls out the year part of a date and @code{RIGHT()} pulls off the rightmost five characters that represent the @code{MM-DD} (calendar year) part of the date. The part of the expression that compares the @code{MM-DD} values evaluates to 1 or 0, which adjusts the year difference down a year if @code{CURRENT_DATE} occurs earlier in the year than @code{birth}. The full expression is somewhat ungainly, so an alias (@code{age}) is used to make the output column label more meaningful. The query works, but the result could be scanned more easily if the rows were presented in some order. This can be done by adding an @code{ORDER BY name} clause to sort the output by name: @example mysql> SELECT name, birth, CURRENT_DATE, -> (YEAR(CURRENT_DATE)-YEAR(birth)) -> - (RIGHT(CURRENT_DATE,5) AS age -> FROM pet ORDER BY name; +----------+------------+--------------+------+ | name | birth | CURRENT_DATE | age | +----------+------------+--------------+------+ | Bowser | 1989-08-31 | 2001-08-29 | 11 | | Buffy | 1989-05-13 | 2001-08-29 | 12 | | Chirpy | 1998-09-11 | 2001-08-29 | 2 | | Claws | 1994-03-17 | 2001-08-29 | 7 | | Fang | 1990-08-27 | 2001-08-29 | 11 | | Fluffy | 1993-02-04 | 2001-08-29 | 8 | | Puffball | 1999-03-30 | 2001-08-29 | 2 | | Slim | 1996-04-29 | 2001-08-29 | 5 | | Whistler | 1997-12-09 | 2001-08-29 | 3 | +----------+------------+--------------+------+ @end example To sort the output by @code{age} rather than @code{name}, just use a different @code{ORDER BY} clause: @example mysql> SELECT name, birth, CURRENT_DATE, -> (YEAR(CURRENT_DATE)-YEAR(birth)) -> - (RIGHT(CURRENT_DATE,5) AS age -> FROM pet ORDER BY age; +----------+------------+--------------+------+ | name | birth | CURRENT_DATE | age | +----------+------------+--------------+------+ | Chirpy | 1998-09-11 | 2001-08-29 | 2 | | Puffball | 1999-03-30 | 2001-08-29 | 2 | | Whistler | 1997-12-09 | 2001-08-29 | 3 | | Slim | 1996-04-29 | 2001-08-29 | 5 | | Claws | 1994-03-17 | 2001-08-29 | 7 | | Fluffy | 1993-02-04 | 2001-08-29 | 8 | | Fang | 1990-08-27 | 2001-08-29 | 11 | | Bowser | 1989-08-31 | 2001-08-29 | 11 | | Buffy | 1989-05-13 | 2001-08-29 | 12 | +----------+------------+--------------+------+ @end example 似たクエリが、既に死んでしまった動物の、死んだ時点の年齢を調べるのにも 使用できます。 どの動物が死んでいるかどうかは、@code{death} 値が @code{NULL} か どうかで判断します。 これらの値が 非@code{NULL} ならば、 @code{death} と @code{birth} の差の計算を行います： @example mysql> SELECT name, birth, death, -> (YEAR(death)-YEAR(birth)) - (RIGHT(death,5) AS age -> FROM pet WHERE death IS NOT NULL ORDER BY age; +--------+------------+------------+------+ | name | birth | death | age | +--------+------------+------------+------+ | Bowser | 1989-08-31 | 1995-07-29 | 5 | +--------+------------+------------+------+ @end example このクエリでは、 @code{death <> NULL} ではなく @code{death IS NOT NULL} を 使用します。 なぜなら、 @code{NULL} は特別な値だからです。 これは後で解説します。 @xref{Working with NULL, , Working with @code{NULL}}. もしあなたが翌月誕生日の動物を知りたいとします。 この種の計算では、 年と日が関係ありません。 @code{birth} フィールドの月だけを単に 取り出したくなるでしょう。 MySQL は日付の部分を取り出すいくつかの関数を 提供します。 @code{YEAR()}, @code{MONTH()}, @code{DAYOFMONTH()} など。 ここでは @code{MONTH()} がいいでしょう。 これがどのように動くか確かめるには、 @code{birth} と @code{MONTH(birth)} の両方を表示させるクエリを実行してみます： @example mysql> SELECT name, birth, MONTH(birth) FROM pet; +----------+------------+--------------+ | name | birth | MONTH(birth) | +----------+------------+--------------+ | Fluffy | 1993-02-04 | 2 | | Claws | 1994-03-17 | 3 | | Buffy | 1989-05-13 | 5 | | Fang | 1990-08-27 | 8 | | Bowser | 1989-08-31 | 8 | | Chirpy | 1998-09-11 | 9 | | Whistler | 1997-12-09 | 12 | | Slim | 1996-04-29 | 4 | | Puffball | 1999-03-30 | 3 | +----------+------------+--------------+ @end example 来月誕生日を迎える動物を見つけるのは簡単です。 現在4月だとします。 すると、5月生まれの動物を探します： @example mysql> SELECT name, birth FROM pet WHERE MONTH(birth) = 5; +-------+------------+ | name | birth | +-------+------------+ | Buffy | 1989-05-13 | +-------+------------+ @end example もし現在が12月なら、ちょっと困るかもしれません。 月の数字 (@code{12}) に 1 を足して 13 月生まれの動物を探すわけにはいきません。 かわりに1月生まれの 動物を探します。 現在が何月なのかを気にすることなく、動作するクエリを書くことが可能です。 この方法では、あなたは月の数字をクエリに使用することがありません。 @code{DATE_ADD()} 関数は与えた日付からある時間を足すことが可能です。 もし現時点 @code{NOW()} の値に 1ヶ月 足し、 @code{MONTH()} で月の 部分を取り出し、その結果を、誕生月を調べるために使用します： @example mysql> SELECT name, birth FROM pet -> WHERE MONTH(birth) = MONTH(DATE_ADD(NOW(), INTERVAL 1 MONTH)); @end example 同じことができる別の方法として、剰余関数 を使用した結果に 1 を足す方法があります。 (もし今月が12月なら、剰余関数 (@code{MOD}) を使用した結果は @code{0} になります)： @example mysql> SELECT name, birth FROM pet -> WHERE MONTH(birth) = MOD(MONTH(NOW()), 12) + 1; @end example Note that @code{MONTH} returns a number between 1 and 12. And @code{MOD(something,12)} returns a number between 0 and 11. So the addition has to be after the @code{MOD()}, otherwise we would go from November (11) to January (1). @node Working with NULL, Pattern matching, Date calculations, Retrieving data @subsubsection @code{NULL} 値の振る舞い @findex NULL @cindex NULL value あなたがそれに慣れるまでは、@code{NULL} 値には驚くかもしれません。 概念的に、@code{NULL} 値は ``値無し'' か ``未知な値'' を意味し、 他の値よりもいくぶん異なって扱われます。 @code{NULL} の評価の際には、数値の比較演算子 @code{=}, @code{<}, @code{<>} を 使用することは出来ません。 あなた自身これをデモするために、以下のようにしてみてください： @example mysql> SELECT 1 = NULL, 1 <> NULL, 1 < NULL, 1 > NULL; +----------+-----------+----------+----------+ | 1 = NULL | 1 <> NULL | 1 < NULL | 1 > NULL | +----------+-----------+----------+----------+ | NULL | NULL | NULL | NULL | +----------+-----------+----------+----------+ @end example 確実にこれらの比較からいかなる意味がある結果も受け取りません。 この代わりに、 @code{IS NULL} , @code{IS NOT NULL} 演算子を使用します： @example mysql> SELECT 1 IS NULL, 1 IS NOT NULL; +-----------+---------------+ | 1 IS NULL | 1 IS NOT NULL | +-----------+---------------+ | 0 | 1 | +-----------+---------------+ @end example MySQL では, 0 や @code{NULL} は false（偽） で、それ以外全てが true（真）です。 The default truth value from a boolean operation is 1. この @code{NULL} の特別な扱いはなぜなのか。 前のセクションを見てください。 どの動物がもはや生きていないことを決定づけるためには、 @code{death <> NULL} ではなく @code{death IS NOT NULL} の使用が 必要とされるのです。 Two @code{NULL} values are regarded as equal in a @code{GROUP BY}. When doing an @code{ORDER BY}, @code{NULL} values are presented first if you do @code{ORDER BY ... ASC} and last if you do @code{ORDER BY ... DESC}. Note that between MySQL 4.0.2 - 4.0.10, @code{NULL} values incorrectly were always sorted first regardless of the sort direction. @node Pattern matching, Counting rows, Working with NULL, Retrieving data @subsubsection パターン・マッチ @cindex pattern matching @cindex matching, patterns @cindex expressions, extended MySQL は標準SQLのパターン・マッチを提供します。 また、拡張された正規表現を基にした形式のパターン・マッチ、 これは @code{vi}, @code{grep} , @code{sed} など UNIX のユーティリティに 使用されている物と似ていますが、これも提供します。 SQL パターン・マッチは、 @samp{_} でいかなる１文字とも一致し、 @samp{%} であらゆる0こ以上の文字列に一致します。 MySQL では、デフォルトで SQL パターンはケース非依存です。 いくつか例を以下に示します。 SQLパターンを使用する場合、 @code{=} や @code{!=} を使用しないように注意してください。 @code{LIKE} か @code{NOT LIKE} を代わりに使用します。 @samp{b} から始まる名前を見つけるには: @example mysql> SELECT * FROM pet WHERE name LIKE "b%"; +--------+--------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +--------+--------+---------+------+------------+------------+ | Buffy | Harold | dog | f | 1989-05-13 | NULL | | Bowser | Diane | dog | m | 1989-08-31 | 1995-07-29 | +--------+--------+---------+------+------------+------------+ @end example @samp{fy} で終わる名前を見つけるには: @example mysql> SELECT * FROM pet WHERE name LIKE "%fy"; +--------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +--------+--------+---------+------+------------+-------+ | Fluffy | Harold | cat | f | 1993-02-04 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +--------+--------+---------+------+------------+-------+ @end example @samp{w} を含む名前を見つけるには: @example mysql> SELECT * FROM pet WHERE name LIKE "%w%"; +----------+-------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +----------+-------+---------+------+------------+------------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Bowser | Diane | dog | m | 1989-08-31 | 1995-07-29 | | Whistler | Gwen | bird | NULL | 1997-12-09 | NULL | +----------+-------+---------+------+------------+------------+ @end example 5文字の名前を見つけるには, @samp{_} パターン文字を使用して： @example mysql> SELECT * FROM pet WHERE name LIKE "_____"; +-------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +-------+--------+---------+------+------------+-------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +-------+--------+---------+------+------------+-------+ @end example MySQL では他のパターン・マッチの形も提供されます。正規表現の拡張を使用して。 これらのパターン・マッチをテストする際には、@code{REGEXP} と @code{NOT REGEXP} 演算子（あるいは@code{RLIKE}, @code{NOT RLIKE} 演算子。これらは同義です） を使用します。 拡張正規表現のいくつかの特徴： @itemize @bullet @item @samp{.} はいかなる一文字とも一致します。 @item @samp{[...]} は、かっこ内にある文字と一致します。 例えば、@samp{[abc]} は @samp{a}, @samp{b} あるいは @samp{c} にマッチします。 文字を範囲指定する場合にはダッシュを使用します。 @samp{[a-z]} はいかなる 小文字のアルファベット文字にも一致し、 @samp{[0-9]} はいかなる数字にも 一致します。 @item @samp{*} は、先に指定されている文字 0 個以上にマッチします。 例えば、@samp{x*} は 文字 @samp{x} がいくつも連続している物にマッチし、 @samp{[0-9]*} はいかなる数値ともマッチし、 @samp{.*} はあらゆる文字列に 一致します。 @item パターンは、テストされた値の中のどこかにある場合、マッチします。 (SQL patterns match only if they match the entire value.) @item 値のはじめ、あるいは終わりに位置を指定してマッチさせたい場合は、 パターンの初めにマッチさせる場合は @samp{^} を使用し、 パターンの終わりにマッチさせる場合は @samp{$} を使用します。 (これらはアンカーと呼ばれます) @end itemize 以下は拡張された正規表現がどう動くかの例です。 上に示した @code{LIKE} のクエリは @code{REGEXP} で以下のように書き換えれます： @samp{b} で始まる名前をみつけるには、@samp{^} で名前の頭にマッチさせ、 かつ @samp{[bB]} として、大文字小文字にもマッチさせます： @example mysql> SELECT * FROM pet WHERE name REGEXP "^b"; +--------+--------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +--------+--------+---------+------+------------+------------+ | Buffy | Harold | dog | f | 1989-05-13 | NULL | | Bowser | Diane | dog | m | 1989-08-31 | 1995-07-29 | +--------+--------+---------+------+------------+------------+ @end example Prior to MySQL Version 3.23.4, @code{REGEXP} is case-sensitive, and the previous query will return no rows. To match either lowercase or uppercase @samp{b}, use this query instead: @example mysql> SELECT * FROM pet WHERE name REGEXP "^[bB]"; @end example From MySQL 3.23.4 on, to force a @code{REGEXP} comparison to be case-sensitive, use the @code{BINARY} keyword to make one of the strings a binary string. This query will match only lowercase @samp{b} at the beginning of a name: @example mysql> SELECT * FROM pet WHERE name REGEXP BINARY "^b"; @end example To find names ending with @samp{fy}, use @samp{$} to match the end of the name: @example mysql> SELECT * FROM pet WHERE name REGEXP "fy$"; +--------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +--------+--------+---------+------+------------+-------+ | Fluffy | Harold | cat | f | 1993-02-04 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +--------+--------+---------+------+------------+-------+ @end example To find names containing a lowercase or uppercase @samp{w}, use this query: @example mysql> SELECT * FROM pet WHERE name REGEXP "w"; +----------+-------+---------+------+------------+------------+ | name | owner | species | sex | birth | death | +----------+-------+---------+------+------------+------------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Bowser | Diane | dog | m | 1989-08-31 | 1995-07-29 | | Whistler | Gwen | bird | NULL | 1997-12-09 | NULL | +----------+-------+---------+------+------------+------------+ @end example 正規表現はもし値中のどこかにでもあればマッチするため、 SQL パターンのように、パターンの前後にワイルドカードを書く必要はありません。 5文字の名前を見つけるには、@samp{^} と @samp{$} を使用して名前の初めと終わりに マッチさせ、その間に @samp{.} を5個入れます： @example mysql> SELECT * FROM pet WHERE name REGEXP "^.....$"; +-------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +-------+--------+---------+------+------------+-------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +-------+--------+---------+------+------------+-------+ @end example 前のクエリは @samp{@{n@}} ``@code{n}回繰り返し'' オペレーターで 書換え可能です。 @example mysql> SELECT * FROM pet WHERE name REGEXP "^.@{5@}$"; +-------+--------+---------+------+------------+-------+ | name | owner | species | sex | birth | death | +-------+--------+---------+------+------------+-------+ | Claws | Gwen | cat | m | 1994-03-17 | NULL | | Buffy | Harold | dog | f | 1989-05-13 | NULL | +-------+--------+---------+------+------------+-------+ @end example @node Counting rows, Multiple tables, Pattern matching, Retrieving data @subsubsection Counting Rows @cindex rows, counting @cindex tables, counting rows @cindex counting, table rows Databases are often used to answer the question, ``How often does a certain type of data occur in a table?'' For example, you might want to know how many pets you have, or how many pets each owner has, or you might want to perform various kinds of censuses on your animals. Counting the total number of animals you have is the same question as ``How many rows are in the @code{pet} table?'' because there is one record per pet. The @code{COUNT()} function counts the number of non-@code{NULL} results, so the query to count your animals looks like this: @example mysql> SELECT COUNT(*) FROM pet; +----------+ | COUNT(*) | +----------+ | 9 | +----------+ @end example Earlier, you retrieved the names of the people who owned pets. You can use @code{COUNT()} if you want to find out how many pets each owner has: @example mysql> SELECT owner, COUNT(*) FROM pet GROUP BY owner; +--------+----------+ | owner | COUNT(*) | +--------+----------+ | Benny | 2 | | Diane | 2 | | Gwen | 3 | | Harold | 2 | +--------+----------+ @end example Note the use of @code{GROUP BY} to group together all records for each @code{owner}. Without it, all you get is an error message: @example mysql> SELECT owner, COUNT(owner) FROM pet; ERROR 1140 at line 1: Mixing of GROUP columns (MIN(),MAX(),COUNT()...) with no GROUP columns is illegal if there is no GROUP BY clause @end example @code{COUNT()} and @code{GROUP BY} are useful for characterising your data in various ways. The following examples show different ways to perform animal census operations. Number of animals per species: @example mysql> SELECT species, COUNT(*) FROM pet GROUP BY species; +---------+----------+ | species | COUNT(*) | +---------+----------+ | bird | 2 | | cat | 2 | | dog | 3 | | hamster | 1 | | snake | 1 | +---------+----------+ @end example Number of animals per sex: @example mysql> SELECT sex, COUNT(*) FROM pet GROUP BY sex; +------+----------+ | sex | COUNT(*) | +------+----------+ | NULL | 1 | | f | 4 | | m | 4 | +------+----------+ @end example (In this output, @code{NULL} indicates sex unknown.) Number of animals per combination of species and sex: @example mysql> SELECT species, sex, COUNT(*) FROM pet GROUP BY species, sex; +---------+------+----------+ | species | sex | COUNT(*) | +---------+------+----------+ | bird | NULL | 1 | | bird | f | 1 | | cat | f | 1 | | cat | m | 1 | | dog | f | 1 | | dog | m | 2 | | hamster | f | 1 | | snake | m | 1 | +---------+------+----------+ @end example You need not retrieve an entire table when you use @code{COUNT()}. For example, the previous query, when performed just on dogs and cats, looks like this: @example mysql> SELECT species, sex, COUNT(*) FROM pet -> WHERE species = "dog" OR species = "cat" -> GROUP BY species, sex; +---------+------+----------+ | species | sex | COUNT(*) | +---------+------+----------+ | cat | f | 1 | | cat | m | 1 | | dog | f | 1 | | dog | m | 2 | +---------+------+----------+ @end example Or, if you wanted the number of animals per sex only for known-sex animals: @example mysql> SELECT species, sex, COUNT(*) FROM pet -> WHERE sex IS NOT NULL -> GROUP BY species, sex; +---------+------+----------+ | species | sex | COUNT(*) | +---------+------+----------+ | bird | f | 1 | | cat | f | 1 | | cat | m | 1 | | dog | f | 1 | | dog | m | 2 | | hamster | f | 1 | | snake | m | 1 | +---------+------+----------+ @end example @node Multiple tables, , Counting rows, Retrieving data @subsubsection Using More Than one Table @cindex tables, multiple The @code{pet} table keeps track of which pets you have. If you want to record other information about them, such as events in their lives like visits to the vet or when litters are born, you need another table. What should this table look like? It needs: @itemize @bullet @item To contain the pet name so you know which animal each event pertains to. @item A date so you know when the event occurred. @item A field to describe the event. @item An event type field, if you want to be able to categorise events. @end itemize Given these considerations, the @code{CREATE TABLE} statement for the @code{event} table might look like this: @example mysql> CREATE TABLE event (name VARCHAR(20), date DATE, -> type VARCHAR(15), remark VARCHAR(255)); @end example As with the @code{pet} table, it's easiest to load the initial records by creating a tab-delimited text file containing the information: @multitable @columnfractions .10 .15 .10 .35 @item @strong{name} @tab @strong{date} @tab @strong{type} @tab @strong{remark} @item Fluffy @tab 1995-05-15 @tab litter @tab 4 kittens, 3 female, 1 male @item Buffy @tab 1993-06-23 @tab litter @tab 5 puppies, 2 female, 3 male @item Buffy @tab 1994-06-19 @tab litter @tab 3 puppies, 3 female @item Chirpy @tab 1999-03-21 @tab vet @tab needed beak straightened @item Slim @tab 1997-08-03 @tab vet @tab broken rib @item Bowser @tab 1991-10-12 @tab kennel @tab @item Fang @tab 1991-10-12 @tab kennel @tab @item Fang @tab 1998-08-28 @tab birthday @tab Gave him a new chew toy @item Claws @tab 1998-03-17 @tab birthday @tab Gave him a new flea collar @item Whistler @tab 1998-12-09 @tab birthday @tab First birthday @end multitable Load the records like this: @example mysql> LOAD DATA LOCAL INFILE "event.txt" INTO TABLE event; @end example Based on what you've learned from the queries you've run on the @code{pet} table, you should be able to perform retrievals on the records in the @code{event} table; the principles are the same. But when is the @code{event} table by itself insufficient to answer questions you might ask? Suppose you want to find out the ages of each pet when they had their litters. The @code{event} table indicates when this occurred, but to calculate the age of the mother, you need her birth date. Because that is stored in the @code{pet} table, you need both tables for the query: @example mysql> SELECT pet.name, -> (TO_DAYS(date) - TO_DAYS(birth))/365 AS age, -> remark -> FROM pet, event -> WHERE pet.name = event.name AND type = "litter"; +--------+------+-----------------------------+ | name | age | remark | +--------+------+-----------------------------+ | Fluffy | 2.27 | 4 kittens, 3 female, 1 male | | Buffy | 4.12 | 5 puppies, 2 female, 3 male | | Buffy | 5.10 | 3 puppies, 3 female | +--------+------+-----------------------------+ @end example There are several things to note about this query: @itemize @bullet @item The @code{FROM} clause lists two tables because the query needs to pull information from both of them. @item When combining (joining) information from multiple tables, you need to specify how records in one table can be matched to records in the other. This is easy because they both have a @code{name} column. The query uses @code{WHERE} clause to match up records in the two tables based on the @code{name} values. @item Because the @code{name} column occurs in both tables, you must be specific about which table you mean when referring to the column. This is done by prepending the table name to the column name. @end itemize You need not have two different tables to perform a join. Sometimes it is useful to join a table to itself, if you want to compare records in a table to other records in that same table. For example, to find breeding pairs among your pets, you can join the @code{pet} table with itself to pair up males and females of like species: @example mysql> SELECT p1.name, p1.sex, p2.name, p2.sex, p1.species -> FROM pet AS p1, pet AS p2 -> WHERE p1.species = p2.species AND p1.sex = "f" AND p2.sex = "m"; +--------+------+--------+------+---------+ | name | sex | name | sex | species | +--------+------+--------+------+---------+ | Fluffy | f | Claws | m | cat | | Buffy | f | Fang | m | dog | | Buffy | f | Bowser | m | dog | +--------+------+--------+------+---------+ @end example In this query, we specify aliases for the table name in order to refer to the columns and keep straight which instance of the table each column reference is associated with. @node Getting information, Examples, Database use, Tutorial @section データベースとテーブルの情報を得る @cindex databases, information about @cindex tables, information about @findex DESCRIBE データベースやテーブルの名前が何であったか、あるいはテーブルの構造はどうであったか、 (なんというフィールドがあったのか)忘れてしまった場合。 MySQL ではいくつかのデータベースとテーブルの情報を提供する文を通じて この問題を処理します。 あなたは既に @code{SHOW DATABASES} を知っているはずで, これはサーバーが 管理するデーターベースの一覧を表示します。 現在選択しているデータベースが 何であるかを知るには、@code{DATABASE()} 関数を使用します： @example mysql> SELECT DATABASE(); +------------+ | DATABASE() | +------------+ | menagerie | +------------+ @end example もしデータベースをまだ何も選択していなければ、結果はブランクです。 データベースに含まれるテーブルを見つけるには(たとえば、あなたがテーブル名を 知らない場合)、このコマンドを使用します： @example mysql> SHOW TABLES; +---------------------+ | Tables in menagerie | +---------------------+ | event | | pet | +---------------------+ @end example もしテーブルの構造を知りたいなら、@code{DESCRIBE} コマンドが便利です； これはテーブルのそれぞれのフィールドについての情報を表示します。 @example mysql> DESCRIBE pet; +---------+-------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------+-------------+------+-----+---------+-------+ | name | varchar(20) | YES | | NULL | | | owner | varchar(20) | YES | | NULL | | | species | varchar(20) | YES | | NULL | | | sex | char(1) | YES | | NULL | | | birth | date | YES | | NULL | | | death | date | YES | | NULL | | +---------+-------------+------+-----+---------+-------+ @end example @code{Field} はフィールド名を示し、@code{Type} はフィールドのデータ型、 @code{Null} はこのフィールドが @code{Null} 値を含むかを示し、 @code{Key} はこのフィールドがインデックス化されているかを示し、 @code{Default} はフィールドのデフォルトの値を示します。 もしテーブルにインデックスを持っているなら、 @code{SHOW INDEX FROM tbl_name} がそれらの情報を示します。 @node Examples, Batch mode, Getting information, Tutorial @section 一般的なクエリー例 @cindex queries, examples @cindex examples, queries 以下は、MySQLの一般的な問題を解決するための例です。 Some of the examples use the table @code{shop} to hold the price of each article (item number) for certain traders (dealers). 各業者に対して各商品の価格が1つ決められているとし、(article, dealer)をレコードの主キーとします。 Start the command-line tool @code{mysql} and select a database: @example mysql your-database-name @end example （MySQLのインストールを通常通り行った場合は、'test'データベースをお使いいただけます。） 以下のSQL文でサンプル テーブルを作成します。 @example CREATE TABLE shop ( article INT(4) UNSIGNED ZEROFILL DEFAULT '0000' NOT NULL, dealer CHAR(20) DEFAULT '' NOT NULL, price DOUBLE(16,2) DEFAULT '0.00' NOT NULL, PRIMARY KEY(article, dealer)); INSERT INTO shop VALUES (1,'A',3.45),(1,'B',3.99),(2,'A',10.99),(3,'B',1.45),(3,'C',1.69), (3,'D',1.25),(4,'D',19.95); @end example サンプル データを表示します。 @example mysql> SELECT * FROM shop; +---------+--------+-------+ | article | dealer | price | +---------+--------+-------+ | 0001 | A | 3.45 | | 0001 | B | 3.99 | | 0002 | A | 10.99 | | 0003 | B | 1.45 | | 0003 | C | 1.69 | | 0003 | D | 1.25 | | 0004 | D | 19.95 | +---------+--------+-------+ @end example @menu * example-Maximum-column:: The maximum value for a column * example-Maximum-row:: The row holding the maximum of a certain column * example-Maximum-column-group:: Maximum of column per group * example-Maximum-column-group-row:: The rows holding the group-wise maximum of a certain field * example-user-variables:: Using user variables * example-Foreign keys:: Using foreign keys * Searching on two keys:: Searching on Two Keys * Calculating days:: Calculating Visits Per Day * example-AUTO_INCREMENT:: Using @code{AUTO_INCREMENT} @end menu @node example-Maximum-column, example-Maximum-row, Examples, Examples @subsection カラムの最大値 ”articleカラムの最大値は？” @example SELECT MAX(article) AS article FROM shop +---------+ | article | +---------+ | 4 | +---------+ @end example @node example-Maximum-row, example-Maximum-column-group, example-Maximum-column, Examples @subsection 特定のカラムの最大値を含んだ行 ”最も高い価格の商品の番号と、業者、価格を求める。” ANSI SQL（MySQLではVersion4.1から）では、副問い合わせを使用することで簡単に求められます。 @example SELECT article, dealer, price FROM shop WHERE price=(SELECT MAX(price) FROM shop) @end example MySQL4.1以前では、以下の2つのステップで求めます。 @enumerate @item @code{SELECT}構文でテーブルから最大値を取得します。 @item 1で求めた値をに使用して、実際のクエリーをコンパイルします。 @example SELECT article, dealer, price FROM shop WHERE price=19.95 @end example @end enumerate その他には全ての行をpriceカラムをもとに降順で並び替え、 MySQL特有 @code{LIMIT} 節を使用して最初の行のみを取得する方法があります。 @example SELECT article, dealer, price FROM shop ORDER BY price DESC LIMIT 1 @end example @strong{注意}：一番高い商品が複数存在する場合は（例えば、19.95ドルの商品が複数ある場合）、@code{LIMIT} 節はそのうちの1つの商品しか表示しません。 @node example-Maximum-column-group, example-Maximum-column-group-row, example-Maximum-row, Examples @subsection カラムのグループごとの最大値 ”商品ごとの価格の最大値は？” @example SELECT article, MAX(price) AS price FROM shop GROUP BY article +---------+-------+ | article | price | +---------+-------+ | 0001 | 3.99 | | 0002 | 10.99 | | 0003 | 1.69 | | 0004 | 19.95 | +---------+-------+ @end example @node example-Maximum-column-group-row, example-user-variables, example-Maximum-column-group, Examples @subsection The Rows Holding the Group-wise Maximum of a Certain Field ``For each article, find the dealer(s) with the most expensive price.'' In ANSI SQL (and MySQL Version 4.1 or greater), I'd do it with a subquery like this: @example SELECT article, dealer, price FROM shop s1 WHERE price=(SELECT MAX(s2.price) FROM shop s2 WHERE s1.article = s2.article); @end example In MySQL versions prior to 4.1 it's best do it in several steps: @enumerate @item Get the list of (article,maxprice). @item For each article get the corresponding rows that have the stored maximum price. @end enumerate This can easily be done with a temporary table: @example CREATE TEMPORARY TABLE tmp ( article INT(4) UNSIGNED ZEROFILL DEFAULT '0000' NOT NULL, price DOUBLE(16,2) DEFAULT '0.00' NOT NULL); LOCK TABLES shop read; INSERT INTO tmp SELECT article, MAX(price) FROM shop GROUP BY article; SELECT shop.article, dealer, shop.price FROM shop, tmp WHERE shop.article=tmp.article AND shop.price=tmp.price; UNLOCK TABLES; DROP TABLE tmp; @end example If you don't use a @code{TEMPORARY} table, you must also lock the 'tmp' table. ``Can it be done with a single query?'' Yes, but only by using a quite inefficient trick that I call the ``MAX-CONCAT trick'': @example SELECT article, SUBSTRING( MAX( CONCAT(LPAD(price,6,'0'),dealer) ), 7) AS dealer, 0.00+LEFT( MAX( CONCAT(LPAD(price,6,'0'),dealer) ), 6) AS price FROM shop GROUP BY article; +---------+--------+-------+ | article | dealer | price | +---------+--------+-------+ | 0001 | B | 3.99 | | 0002 | A | 10.99 | | 0003 | C | 1.69 | | 0004 | D | 19.95 | +---------+--------+-------+ @end example The last example can, of course, be made a bit more efficient by doing the splitting of the concatenated column in the client. @node example-user-variables, example-Foreign keys, example-Maximum-column-group-row, Examples @subsection ユーザー変数の使用 MySQLのユーザー変数を使用すると、クライアントの一時変数に格納せずに結果を 記憶できます。@xref{Variables}。 例えば、商品の価格の最大値と最小値を求めるには、以下のSELECT構文を実行します。 @example mysql> SELECT @@min_price:=MIN(price),@@max_price:=MAX(price) FROM shop; mysql> SELECT * FROM shop WHERE price=@@min_price OR price=@@max_price; +---------+--------+-------+ | article | dealer | price | +---------+--------+-------+ | 0003 | D | 1.25 | | 0004 | D | 19.95 | +---------+--------+-------+ @end example @node example-Foreign keys, Searching on two keys, example-user-variables, Examples @subsection Using Foreign Keys @cindex foreign keys @cindex keys, foreign In MySQL 3.23.44 and up, @code{InnoDB} tables supports checking of foreign key constraints. @xref{InnoDB}. See also @ref{ANSI diff Foreign Keys}. You don't actually need foreign keys to join 2 tables. The only thing MySQL currently doesn't do (in table types other than @code{InnoDB}), is @code{CHECK} to make sure that the keys you use really exist in the table(s) you're referencing and it doesn't automatically delete rows from a table with a foreign key definition. If you use your keys like normal, it'll work just fine: @example CREATE TABLE person ( id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT, name CHAR(60) NOT NULL, PRIMARY KEY (id) ); CREATE TABLE shirt ( id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT, style ENUM('t-shirt', 'polo', 'dress') NOT NULL, color ENUM('red', 'blue', 'orange', 'white', 'black') NOT NULL, owner SMALLINT UNSIGNED NOT NULL REFERENCES person(id), PRIMARY KEY (id) ); INSERT INTO person VALUES (NULL, 'Antonio Paz'); INSERT INTO shirt VALUES (NULL, 'polo', 'blue', LAST_INSERT_ID()), (NULL, 'dress', 'white', LAST_INSERT_ID()), (NULL, 't-shirt', 'blue', LAST_INSERT_ID()); INSERT INTO person VALUES (NULL, 'Lilliana Angelovska'); INSERT INTO shirt VALUES (NULL, 'dress', 'orange', LAST_INSERT_ID()), (NULL, 'polo', 'red', LAST_INSERT_ID()), (NULL, 'dress', 'blue', LAST_INSERT_ID()), (NULL, 't-shirt', 'white', LAST_INSERT_ID()); SELECT * FROM person; +----+---------------------+ | id | name | +----+---------------------+ | 1 | Antonio Paz | | 2 | Lilliana Angelovska | +----+---------------------+ SELECT * FROM shirt; +----+---------+--------+-------+ | id | style | color | owner | +----+---------+--------+-------+ | 1 | polo | blue | 1 | | 2 | dress | white | 1 | | 3 | t-shirt | blue | 1 | | 4 | dress | orange | 2 | | 5 | polo | red | 2 | | 6 | dress | blue | 2 | | 7 | t-shirt | white | 2 | +----+---------+--------+-------+ SELECT s.* FROM person p, shirt s WHERE p.name LIKE 'Lilliana%' AND s.owner = p.id AND s.color <> 'white'; +----+-------+--------+-------+ | id | style | color | owner | +----+-------+--------+-------+ | 4 | dress | orange | 2 | | 5 | polo | red | 2 | | 6 | dress | blue | 2 | +----+-------+--------+-------+ @end example @node Searching on two keys, Calculating days, example-Foreign keys, Examples @subsection Searching on Two Keys @findex UNION @cindex searching, two keys @cindex keys, searching on two MySQL doesn't yet optimize when you search on two different keys combined with @code{OR} (searching on one key with different @code{OR} parts is optimized quite well): @example SELECT field1_index, field2_index FROM test_table WHERE field1_index = '1' OR field2_index = '1' @end example The reason is that we haven't yet had time to come up with an efficient way to handle this in the general case. (The @code{AND} handling is, in comparison, now completely general and works very well.) For the moment you can solve this very efficiently by using a @code{TEMPORARY} table. This type of optimization is also very good if you are using very complicated queries where the SQL server does the optimizations in the wrong order. @example CREATE TEMPORARY TABLE tmp SELECT field1_index, field2_index FROM test_table WHERE field1_index = '1'; INSERT INTO tmp SELECT field1_index, field2_index FROM test_table WHERE field2_index = '1'; SELECT * from tmp; DROP TABLE tmp; @end example The above way to solve this query is in effect a @code{UNION} of two queries. @xref{UNION}. @node Calculating days, example-AUTO_INCREMENT, Searching on two keys, Examples @subsection Calculating Visits Per Day @findex BIT_OR @findex BIT_COUNT @findex << @cindex bit_functions, example The following shows an idea of how you can use the bit group functions to calculate the number of days per month a user has visited a web page. @example CREATE TABLE t1 (year YEAR(4), month INT(2) UNSIGNED ZEROFILL, day INT(2) UNSIGNED ZEROFILL); INSERT INTO t1 VALUES(2000,1,1),(2000,1,20),(2000,1,30),(2000,2,2), (2000,2,23),(2000,2,23); SELECT year,month,BIT_COUNT(BIT_OR(1< mysql < batch-file @end example If you are running @code{mysql} under windows and have some special characters in the file that causes problems, you can do: @example dos> mysql -e "source batch-file" @end example もし接続パラメターを指定する必要がある場合は、以下のようになるでしょう： @example shell> mysql -h host -u user -p < batch-file Enter password: ******** @end example この方法で @code{mysql} を使用するとき、あなたはスクリプトファイルを 作成し、それを実行することになるでしょう。 If you want the script to continue even if you have errors, you should use the @code{--force} command-line option. なぜスクリプトを使用するのか？ それには以下の理由があります： @itemize @bullet @item もし繰り返しクエリを実行する場合(毎日とか毎週とか)、スクリプトを書くことで、 その実行の度にあなたがコマンドをタイプすることを省くことが可能です。 @item もし既にあるクエリに似た新しいクエリを書く場合、それらをコピーし スクリプトファイルを編集できます。 @item バッチモードはクエリの開発中や複数にまたがるコマンドには役に立ちます。 もしコマンドが間違っていたとしても全てを打ち直す必要がありません。 エラーを修正するためにスクリプトを編集し、再び @code{mysql} に実行させます。 @item もし多くの出力を出すようなクエリの場合、ページャーを使用して出力を見ることが 出来ます。 出力がスクロールして画面から見えなくなるよりいいでしょう： @example shell> mysql < batch-file | more @end example @item あなたはより処理を行うために、結果をファイルに書き出すことが可能です： @example shell> mysql < batch-file > mysql.out @end example @item あなたは、他人へのあなたのスクリプトを配布することができます。これにより、ほかの人たちも コマンドを実行することができます。 @item いくつかの状況では、対話モードでは使用に耐えません。 たとえば、クエリを @code{cron} ジョブとして実行する場合。 この場合、バッチモードでなければなりません。 @item 端末が正しく扱えない文字を @code{mysql} コマンドに渡す場合。 たとえば、EUC-JP, Shift_JIS の漢字文字などは、端末や環境によっては直接入力できない場合もあるでしょう。 あるいは、文字コードの違う MySQL サーバーにデータを転送するときなども。 @end itemize @code{mysql} をバッチモードで使用するか、対話モードで使用するかで、 デフォルトの出力形式が変わります。 例えば、 @code{SELECT DISTINCT species FROM pet} の 出力は対話モードでは次のようになります： @example +---------+ | species | +---------+ | bird | | cat | | dog | | hamster | | snake | +---------+ @end example しかし、バッチモードでは： @example species bird cat dog hamster snake @end example もしバッチモードでも対話モードのような出力を得たい場合には、@code{mysql -t} とします。 出力中に、実行したコマンドを表示させるならば、@code{mysql -vvv} とします。 You can also use scripts in the @code{mysql} command-line prompt by using the @code{source} command: @example mysql> source filename; @end example @node Twin, Apache, Batch mode, Tutorial @section Queries from Twin Project @cindex Twin Studies, queries @cindex queries, Twin Studeis project At Analytikerna and Lentus, we have been doing the systems and field work for a big research project. This project is a collaboration between the Institute of Environmental Medicine at Karolinska Institutet Stockholm and the Section on Clinical Research in Aging and Psychology at the University of Southern California. The project involves a screening part where all twins in Sweden older than 65 years are interviewed by telephone. Twins who meet certain criteria are passed on to the next stage. In this latter stage, twins who want to participate are visited by a doctor/nurse team. Some of the examinations include physical and neuropsychological examination, laboratory testing, neuroimaging, psychological status assessment, and family history collection. In addition, data are collected on medical and environmental risk factors. More information about Twin studies can be found at: @uref{http://www.imm.ki.se/TWIN/TWINUKW.HTM} The latter part of the project is administered with a web interface written using Perl and MySQL. Each night all data from the interviews are moved into a MySQL database. @menu * Twin pool:: Find all non-distributed twins * Twin event:: Show a table on twin pair status @end menu @node Twin pool, Twin event, Twin, Twin @subsection Find all Non-distributed Twins The following query is used to determine who goes into the second part of the project: @example SELECT CONCAT(p1.id, p1.tvab) + 0 AS tvid, CONCAT(p1.christian_name, " ", p1.surname) AS Name, p1.postal_code AS Code, p1.city AS City, pg.abrev AS Area, IF(td.participation = "Aborted", "A", " ") AS A, p1.dead AS dead1, l.event AS event1, td.suspect AS tsuspect1, id.suspect AS isuspect1, td.severe AS tsevere1, id.severe AS isevere1, p2.dead AS dead2, l2.event AS event2, h2.nurse AS nurse2, h2.doctor AS doctor2, td2.suspect AS tsuspect2, id2.suspect AS isuspect2, td2.severe AS tsevere2, id2.severe AS isevere2, l.finish_date FROM twin_project AS tp /* For Twin 1 */ LEFT JOIN twin_data AS td ON tp.id = td.id AND tp.tvab = td.tvab LEFT JOIN informant_data AS id ON tp.id = id.id AND tp.tvab = id.tvab LEFT JOIN harmony AS h ON tp.id = h.id AND tp.tvab = h.tvab LEFT JOIN lentus AS l ON tp.id = l.id AND tp.tvab = l.tvab /* For Twin 2 */ LEFT JOIN twin_data AS td2 ON p2.id = td2.id AND p2.tvab = td2.tvab LEFT JOIN informant_data AS id2 ON p2.id = id2.id AND p2.tvab = id2.tvab LEFT JOIN harmony AS h2 ON p2.id = h2.id AND p2.tvab = h2.tvab LEFT JOIN lentus AS l2 ON p2.id = l2.id AND p2.tvab = l2.tvab, person_data AS p1, person_data AS p2, postal_groups AS pg WHERE /* p1 gets main twin and p2 gets his/her twin. */ /* ptvab is a field inverted from tvab */ p1.id = tp.id AND p1.tvab = tp.tvab AND p2.id = p1.id AND p2.ptvab = p1.tvab AND /* Just the sceening survey */ tp.survey_no = 5 AND /* Skip if partner died before 65 but allow emigration (dead=9) */ (p2.dead = 0 OR p2.dead = 9 OR (p2.dead = 1 AND (p2.death_date = 0 OR (((TO_DAYS(p2.death_date) - TO_DAYS(p2.birthday)) / 365) >= 65)))) AND ( /* Twin is suspect */ (td.future_contact = 'Yes' AND td.suspect = 2) OR /* Twin is suspect - Informant is Blessed */ (td.future_contact = 'Yes' AND td.suspect = 1 AND id.suspect = 1) OR /* No twin - Informant is Blessed */ (ISNULL(td.suspect) AND id.suspect = 1 AND id.future_contact = 'Yes') OR /* Twin broken off - Informant is Blessed */ (td.participation = 'Aborted' AND id.suspect = 1 AND id.future_contact = 'Yes') OR /* Twin broken off - No inform - Have partner */ (td.participation = 'Aborted' AND ISNULL(id.suspect) AND p2.dead = 0)) AND l.event = 'Finished' /* Get at area code */ AND SUBSTRING(p1.postal_code, 1, 2) = pg.code /* Not already distributed */ AND (h.nurse IS NULL OR h.nurse=00 OR h.doctor=00) /* Has not refused or been aborted */ AND NOT (h.status = 'Refused' OR h.status = 'Aborted' OR h.status = 'Died' OR h.status = 'Other') ORDER BY tvid; @end example Some explanations: @table @asis @item @code{CONCAT(p1.id, p1.tvab) + 0 AS tvid} We want to sort on the concatenated @code{id} and @code{tvab} in numerical order. Adding @code{0} to the result causes MySQL to treat the result as a number. @item column @code{id} This identifies a pair of twins. It is a key in all tables. @item column @code{tvab} This identifies a twin in a pair. It has a value of @code{1} or @code{2}. @item column @code{ptvab} This is an inverse of @code{tvab}. When @code{tvab} is @code{1} this is @code{2}, and vice versa. It exists to save typing and to make it easier for MySQL to optimize the query. @end table This query demonstrates, among other things, how to do lookups on a table from the same table with a join (@code{p1} and @code{p2}). In the example, this is used to check whether a twin's partner died before the age of 65. If so, the row is not returned. All of the above exist in all tables with twin-related information. We have a key on both @code{id,tvab} (all tables), and @code{id,ptvab} (@code{person_data}) to make queries faster. On our production machine (A 200MHz UltraSPARC), this query returns about 150-200 rows and takes less than one second. The current number of records in the tables used above: @multitable @columnfractions .25 .10 @item @strong{Table} @tab @strong{Rows} @item @code{person_data} @tab 71074 @item @code{lentus} @tab 5291 @item @code{twin_project} @tab 5286 @item @code{twin_data} @tab 2012 @item @code{informant_data} @tab 663 @item @code{harmony} @tab 381 @item @code{postal_groups} @tab 100 @end multitable @node Twin event, , Twin pool, Twin @subsection Show a Table on Twin Pair Status Each interview ends with a status code called @code{event}. The query shown here is used to display a table over all twin pairs combined by event. This indicates in how many pairs both twins are finished, in how many pairs one twin is finished and the other refused, and so on. @example SELECT t1.event, t2.event, COUNT(*) FROM lentus AS t1, lentus AS t2, twin_project AS tp WHERE /* We are looking at one pair at a time */ t1.id = tp.id AND t1.tvab=tp.tvab AND t1.id = t2.id /* Just the sceening survey */ AND tp.survey_no = 5 /* This makes each pair only appear once */ AND t1.tvab='1' AND t2.tvab='2' GROUP BY t1.event, t2.event; @end example @node Apache, , Twin, Tutorial @section Using MySQL with Apache @cindex Apache There are programs that let you authenticate your users from a MySQL database and also let you log your log files into a MySQL table. You can change the Apache logging format to be easily readable by MySQL by putting the following into the Apache configuration file: @example LogFormat \ "\"%h\",%@{%Y%m%d%H%M%S@}t,%>s,\"%b\",\"%@{Content-Type@}o\", \ \"%U\",\"%@{Referer@}i\",\"%@{User-Agent@}i\"" @end example In MySQL you can do something like this: @example LOAD DATA INFILE '/local/access_log' INTO TABLE table_name FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' ESCAPED BY '\\' @end example @node MySQL Database Administration, MySQL Optimisation, Tutorial, Top @chapter データベース管理 @menu * Configuring MySQL:: Configuring MySQL * Privilege system:: General Security Issues and the MySQL Access Privilege System * User Account Management:: MySQL User Account Management * Disaster Prevention:: Disaster Prevention and Recovery * Database Administration:: Database Administration Language Reference * Localisation:: MySQL Localisation and International Usage * Server-Side Scripts:: MySQL Server-Side Scripts and Utilities * Client-Side Scripts:: MySQL Client-Side Scripts and Utilities * Log Files:: The MySQL Log Files * Replication:: Replication in MySQL @end menu @node Configuring MySQL, Privilege system, MySQL Database Administration, MySQL Database Administration @section Configuring MySQL @c FIX: add section intro @menu * Command-line options:: @code{mysqld} Command-line Options * Option files:: @file{my.cnf} Option Files * Installing many servers:: Installing Many Servers on the Same Machine * Multiple servers:: Running Multiple MySQL Servers on the Same Machine @end menu @node Command-line options, Option files, Configuring MySQL, Configuring MySQL @subsection @code{mysqld} コマンド行オプション @findex command-line options @cindex options, command-line @cindex mysqld options 多くの場合、オプションファイルを通じて mysqld オプションを管理すべきです。 @xref{Option files}. @code{mysqld} と @code{mysqld.server} は @code{mysqld} と @code{server} グループからオプションを読み込みます。@code{mysqld_safe} は @code{mysqld}, @code{server}, @code{mysqld_safe}, @code{safe_mysqld} グ ループからオプションを読み込みます。組み込み MySQL サーバは通常 @code{server}, @code{embedded}, @code{xxxxx_SERVER} からオプションを読み 込みます。@code{xxxxx} はアプリケーション名です。 @code{mysqld} は次のコマンド行オプションを受け付けます。 完全なリストについては @code{mysqld --help} を実行してください。 @table @code @item --ansi MySQL 構文の代わりに ANSI SQL 構文を使用します。 @xref{ANSI mode}. @item -b, --basedir=path インストール先ディレクトリのパス。すべてのパスは通常ここからの相対パスで決 定されます。 @item --big-tables ファイルにすべての一時セットを保存することにより、大きな結果セットを許しま す。これは、多くの 'table full' エラーを解決します。しかし、メモリ内テーブ ルでも十分なクエリは遅くなります。バージョン 3.23.2 からは、 MySQL は自動的にメモリを使用し、必要なときにディスクテーブルにス イッチすることによって、これを解決します。 @item --bind-address=IP bind する IP アドレス。 @item --console @code{--log-error} が指定されていても、エラーログメッセージを stderr/stdout に書き出します。Windows mysqld はこのオプションが使用され た場合はコンソールスクリーンをクローズしません。 @item --character-sets-dir=path キャラクタ・セット ディレクトリ。 @xref{Character sets}. @item --chroot=path 起動時に @code{mysqld} デーモンを chroot 下に置きます。 MySQL 4.0 からの推奨されるセキュリティ手法です。 (MySQL 3.23 は 100% クローズな chroot jail を提供できません)。 これは @code{LOAD DATA INFILE} と @code{SELECT ... INTO OUTFILE} を制限します。 @item --core-file @code{mysqld} が死んだ場合 core ファイルを書き出します。いくつかのシステム では、@code{--core-file-size} も @code{safe_mysqld} に記述する必要がありま す。 @xref{safe_mysqld, ,@code{safe_mysqld}}. 注意: Solaris のようないくつかのシステムでは、@code{--user} オプションも 使用すると core ファイルを得られません。 @item -h, --datadir=path データベースルートのパス。 @item --debug[...]= MySQL が @code{--with-debug} つきで configure された場合、このオ プション使用して、@code{mysqld} が何を行なっているかのトレースファイルを得 ることができます @xref{Making trace files}. @item --default-character-set=charset デフォルト のキャラクタ・セットの設定。 @xref{Character sets}. @item --default-table-type=type テーブルのデフォルトテーブル型を設定する。 @xref{Table types}. @item --delay-key-write[= OFF | ON | ALL] MyISAM @code{DELAYED KEYS} が使用される方法。@xref{Server parameters}。 @item --delay-key-write-for-all-tables; MySQL 4.0.3 では代わりに --delay-key-write=ALL を使用。 任意の @code{MyISAM} テーブルについて書き込み間でキーバッファをフラッシュ しません。 @xref{Server parameters}. @item --des-key-file=filename このファイルから @code{DES_ENCRYPT()} と @code{DES_DECRYPT()} で使用され るデフォルトキーを読み込みます。 @item --enable-external-locking (4.0.3 から. それ以前のバージョンでは --enable-locking) システムロックを有効にします。注意: lockd() が完全に働かない(Linux のよう な)システムでこのオプションを使用した場合、mysqld が簡単にデッドロックしま す。 @item --enable-named-pipe 名前付きパイプのサポートを有効にします (NT/Win2000/XP のみ)。 @item -T, --exit-info mysqld サーバをデバッグするために使用できる、様々なフラグのビットマスクで す; 何が行なわれるのか正確に知らない場合は、このオプションを使用すべきでは ありません！ @item --flush 各 SQL コマンド後にすべての変更をディスクにフラッシュします。通常 MySQL は各 SQL コマンドにすべての変更をディスクに書き出すだけで、 OS がディスクへの sync を処理します。 @xref{Crashing}. @item -?, --help 短いへルプを表示して終了します。 @item --init-file=file 起動時にファイルから SQL コマンドを読み込みます。 @item -L, --language=... 与えられた言語のクライアントエラーメッセージ。フルパスで与えることもできます。 @xref{Languages}. @item -l, --log[=file] 接続とクエリをファイルに記録します。 @xref{Query log}. @item --log-bin=[file] データを変更するすべてのクエリをファイルに記録します。バックアップとレプ リケーションのために使用されます。@xref{Binary log}。 @item --log-bin-index[=file] バイナリログファイル名のためのインデックスファイル。@xref{Binary log}。 @item --log-error[=file] エラーと起動メッセージをこのファイルに記録します。@xref{Error log}。 @item --log-isam[=file] すべての ISAM/MyISAM 変更をファイルに記録します(ISAM/MyISAM のデバッグ時に のみ使用できます)。 @item --log-slow-queries[=file] 実行に @code{long_query_time} 秒以上掛かるすべてのクエリをファイルに記録し ます。 @xref{Slow query log}. @item --log-update[=file] 更新を @code{file.#} に記録します。@code{#} は与えられなければ一意な番号で す。 @xref{Update log}. @item --log-long-format 更新ログに拡張情報を記録します。@code{--log-slow-queries} を使用すると、イ ンデックスを使用しないクエリが slow query ログに記録されます。 @item --low-priority-updates テーブル変更操作 (@code{INSERT}/@code{DELETE}/@code{UPDATE}) は SELECT よ りも低い優先度になります。あるクエリだけ優先度を低くするには、 @code{@{INSERT | REPLACE | UPDATE | DELETE@} LOW_PRIORITY ...} によって行 なわれます。また、ひとつのスレッドの優先度を変更するには、 @code{SET LOW_PRIORITY_UPDATES=1} で行なわれます。 @xref{Table locking}. @item --memlock メモリに @code{mysqld} プロセスをロックします。これはシステムが @code{mlockall()} システムコールをサポートしている時(Solaris のように)にだけ動作します。 これは、OS が @code{mysqld} をディスク上にスワップさせる問題がある場合の助けに なります。 @item --myisam-recover [=option[,option...]]] ここで option は @code{DEFAULT} か @code{BACKUP} か @code{FORCE} か @code{QUICK} の組み合わせ. 3.23.26以上で有効. このオプションを使用すると、@code{mysqld} はオープン時にテーブルがクラッシュ したとマークされているかどうか、テーブルが適切にクローズされていないかどう かチェックします。(最後のオプションは @code{--skip-external-locking} (4.0.3より前のバージョンでは @code{--skip-locking}) で起動している 場合にだけ働きます)。この場合、@code{mysqld} はテーブル上でチェックを実 行します。テーブルが壊れている場合、@code{mysqld} はその修復を試みます。 次のオプションは修復の動作に影響します： @multitable @columnfractions .15 .7 @item @strong{Option} @tab @strong{Description} @item DEFAULT @tab @code{--myisam-recover} にオプションを与えないのと同じです。 @item BACKUP @tab データテーブルが修復中に変更された場合、 @file{table_name.MYD} データファイルのバックアップを @file{table_name-datetime.BAK} に保存します。 @item FORCE @tab .MYD ファイルからひとつより多くのレコードが失われている 場合でも修復を実行します。 @item QUICK @tab 削除ブロックがない場合にテーブル内のレコードをチェック しません。 @end multitable テーブルが自動的に修復される前に、MySQL はエラーログにこれについ てのメモを追加します。ユーザの介入なしで多くのことを修復したい場合は、オプ ション @code{BACKUP,FORCE} を使用すべきです。いくつかのレコードが削除され る場合でも、テーブルを強制的に修復しますが、古いデータファイルをバックアッ プとして保存するため、あとで何が起こったか検証できます。 @item --pid-file=path @code{safe_mysqld} によって使用される pid ファイルのパス。 @item -P, --port=... TCP/IP 接続で listen するポート番号。 @item -o, --old-protocol とても古いクライアントとの互換のために、3.20 プロトコルを使用します。 @xref{Upgrading-from-3.20}. @item --one-thread 一つのスレッドだけを使用します(Linux 下でデバックするため)。 @xref{Debugging server}. @item -O, --set-variable var=option 変数に値を与えます。@code{--help} は変数をリストします。すべての変数の完全 な詳細はこのマニュアルの @code{SHOW VARIABLES} 節で見られます。 @xref{SHOW VARIABLES}。サーバパラメータの調整についての節はこれらの最適化 方法の情報を含んでいます。 MySQL 4.0 からは @code{--set-variable} は推奨されないことに注意してください。 @code{--var=option} を使用してください。 @xref{Server parameters}。 MySQL 4.0.2 では、@code{--variable-name=option} で直接変数を設定できます。 @code{set-variable} はオプションファイル中ではもはや必要ありません。 @code{SET} で設定できる起動オプションの最大値を制限したい場合は、 @code{--maximum-variable-name} コマンドラインオプションを使用することで 定義できます。@xref{SET OPTION}。 注意: 変数に値を設定する時、MySQL は自動的に与えられた範囲に収まるように 補正し、使用されるアルゴリズム用に合うように値を少し調整します。 @item --safe-mode いくつかの最適化ステージをスキップします。 @item --safe-show-database このオプションをつけると、@code{SHOW DATABASES} コマンドは、ユーザが何か の権限を持つデータベースだけを返します。 バージョン 4.0.2 からはこのオプションは推奨されず何もしません(デフォルト でこのオプションは有効です)。現在は @code{SHOW DATABASES} 権限を持つため です。@xref{GRANT}。 @item --safe-user-create これが有効な場合、ユーザが @code{mysql.user} テーブルやこのテーブル内の 任意のフィールドについて @code{INSERT} 権限を持っていない場合、そのユー ザは GRANT コマンドで新しいユーザを作成できません。 @item --skip-bdb BDB テーブルの使用を無効にします。これはメモリを節約し、いくつかのことを 高速化します。 @item --skip-concurrent-insert 同時に @code{MyISAM} テーブルに select と insert を行なう機能をオフにしま す。(この機能にバグを見つけたと考える場合にだけ使用します)。 @item --skip-delay-key-write; MySQL 4.0.3 では代わりに --delay-key-write=OFF を使用 すべてのテーブルに対し @code{DELAY_KEY_WRITE} オプションを無視します。 @xref{Server parameters}. @item --skip-grant-tables このオプションは、サーバをすべての権限システムを使用しないようにします。これ は全員にすべてのデータベースへの@emph{完全アクセス}を与えます！ (@code{mysqladmin flush-privileges} や @code{mysqladmin reload} を実行する ことで、権限テーブルを使用して起動するように実行中のサーバに伝えることがで きます。) @item --skip-host-cache より速いホスト名-IP解決のためのホスト名キャッシュを使用しません。代わりに すべての接続で DNS サーバへクエリします。 @xref{DNS}. @item --skip-innodb Innodb テーブルの使用を無効にします。これはメモリとディスク領域の節約と いくつかのことを高速化します。 @item --skip-external-locking (4.0.3から. 4.0.3より前では --skip-locking) システムロックを使用しません。@code{isamchk} または @code{myisamchk} を使 用するためには、サーバをシャットダウンする必要があります。 @xref{Stability}。注意: MySQL バージョン 3.23 では、 @code{REPAIR} と @code{CHECK} を @code{MyISAM} テーブルの修復／チェックに 使用できます。 @item --skip-name-resolve ホスト名を解決しません。権限テーブルのすべての @code{Host} フィールド値は IP 番号か @code{localhost} でなければなりません。 @xref{DNS}. @item --skip-networking TCP/IP 接続の listen をまったく行ないません。@code{mysqld} との接続には Unix ソケット経由で行なう必要があります。このオプションはローカル要求だけ を許可するシステムでは、高く推奨されます。 @xref{DNS}. @item --skip-new Don't use new, possible wrong routines. @item --skip-symlink データディレクトリ中のシンボリックリンクファイルが指すファイルを削除、リ ネームしません。 @item --skip-safemalloc MySQL が @code{--with-debug=full} で configure されている場合、す べてのプログラムがすべてのメモリ割り当てとメモリ解放をオーバーラン用にチェッ クします。このチェックはとても遅いので、メモリチェックが不要な場合、このオ プションを使用することでこれを無効にできます。 @item --skip-show-database @code{SHOW DATABASES} 権限を持っていないユーザに @code{SHOW DATABASES} コマンドを 許しません。 バージョン 4.0.2 からは、このオプションは必要ありません。現在、アクセス は @code{SHOW DATABASES} 権限で特別に与えられるためです。 @item --skip-stack-trace スタックトレースを書き出しません。このオプションは、@code{mysqld} をデバッ ガ下で実行している時に有用です。 いくつかのシステムでは、core ファイルを得るためにこのオプションも使用す る必要があります。@xref{Debugging server}。 @item --skip-thread-priority より速いレスポンスタイム用のスレッド優先度の使用を無効にします。 @item --socket=path デフォルト @code{/tmp/mysql.sock} の代わりに、ローカル接続用に使用されるソ ケットファイル。 @item --sql-mode=option[,option[,option...]] オプションは次の任意の組合わせです: @code{REAL_AS_FLOAT}, @code{PIPES_AS_CONCAT}, @code{ANSI_QUOTES}, @code{IGNORE_SPACE}, @code{SERIALIZE}, @code{ONLY_FULL_GROUP_BY}。リセットしたい場合は、空 (@code{""}) も指定できます。 上記オプションの全てを指定することで、--ansi の使用と同じになります。 このオプションで、必要とされる SQL モードだけを有効にできます。 @xref{ANSI mode}。 @item --temp-pool Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. This is to work around a problem in the Linux kernel dealing with creating a bunch of new files with different names. With the old behaviour, Linux seems to 'leak' memory, as it's being allocated to the directory entry cache instead of the disk cache. @item --transaction-isolation= @{ READ-UNCOMMITTED | READ-COMMITTED | REPEATABLE-READ | SERIALIZABLE @} トランザクション分離レベルのデフォルトを設定します。@xref{SET TRANSACTION}。 @item -t, --tmpdir=path 一時ファイル用のパス。デフォルトの @code{/tmp} ディレクトリが一時テーブル を保持するのに小さすぎるパーティション上にある場合に有用です。 MySQL 4.1 からは、このオプションはコロン @code{:}(Windows ではセミコロン @code{;})で区切られたいくつかのパスを受け付けます。これらはラウンドロビ ン方法で使用されます。 @item -u, --user= [user_name | userid] ユーザ @code{user_name} か @code{userid} (数値) で @code{mysqld} デーモンを実行します。 このオプションは、@code{mysqld} を root で起動した時に @strong{強制}されます。 Starting from MySQL 3.23.56 and 4.0.12: To avoid a possible security hole where a user adds an @code{--user=root} option to some @file{my.cnf} file, @code{mysqld} will only use the first @code{--user} option specified and give a warning if there are multiple options. Note that @file{/etc/my.cnf} and @file{datadir/my.cnf} may override a command line option - therefore it is recommended to put this option in @file{/etc/my.cnf}. @item -V, --version バージョン情報を出力して終了します @item -W, --log-warnings (4.0.3 より前では --warnings) @code{Aborted connection...} のような警告を @code{.err} ファイルに出力します。 @xref{Communication errors}. @end table @code{SET} コマンドで実行中のサーバの多くの値を変更できます。 @xref{SET OPTION}。 @node Option files, Installing many servers, Command-line options, Configuring MySQL @subsection @file{my.cnf} オプションファイル @cindex default options @cindex option files @cindex creating, default startup options @cindex startup options, default MySQL バージョン 3.22 のサーバー、クライアントともに、 オプションファイルからデフォルトの起動オプションを読み込むことができます。 Unix では MySQL は以下のファイルからデフォルトオプションを読みます： @tindex .my.cnf file @multitable @columnfractions .35 .50 @item @strong{ファイル名} @tab @strong{意味} @item @code{/etc/my.cnf} @tab グローバルなオプション @item @code{DATADIR/my.cnf} @tab サーバ固有オプション @item @code{defaults-extra-file} @tab --defaults-extra-file=# で指定されたファイル @item @code{~/.my.cnf} @tab ユーザ固有オプション @end multitable @code{DATADIR} は MySQL データディレクトリです (普通 バイナリディストリビューションでは @file{/usr/local/mysql/data} 、ソースディストリビューションでは @file{/usr/local/var}). このディレクトリはconfigure時に決定されており、 @code{--datadir} を @code{mysqld} 起動時に指定しても変更されません。 (サーバーはコマンドラインの引数を処理する前にオプションファイルを探します。 よって、@code{--datadir} 引数を指定してもオプションファイルを探す場所を指定することにはなりません。) Windows では MySQL は以下のファイルからデフォルトオプションを読みます： @multitable @columnfractions .35 .50 @item @strong{ファイル名} @tab @strong{意味} @item @code{windows-system-directory\my.ini} @tab グローバルオプション @item @code{C:\my.cnf} @tab グローバルオプション @end multitable 注意: Windows では @code{\} の代わりに @code{/} で全てのパスを記述すべきで す。@code{\} を使用する場合、@code{\} は MySQL のエスケープ文字 なので、これを二重に記述する必要があります。 @cindex environment variables MySQL は上記の表にかかれている順にオプションファイルを読みます。 もし複数オプションファイルがあった場合、後から読まれた設定が有効になります。 全てのオプションはコマンドラインの引数に上書きされます。 いくつかのオプションは環境変数に定義できます。 オプションファイルとコマンドラインの引数は環境変数を上書きします。 @xref{Environment variables}. 次のプログラムはオプションファイルをサポートします： @code{mysql}, @code{mysqladmin}, @code{mysqld}, @code{mysqld_safe}, @code{mysql.server}, @code{mysqldump}, @code{mysqlimport}, @code{mysqlshow}, @code{mysqlcheck}, @code{myisamchk}, @code{myisampack}. オプションファイルには、プログラムがサポートしているコマンドラインの long オプション(例えば、@code{-u} ではなくて @code{--user} の方)を書くことができます。 プログラムを @code{--help} で起動すれば、設定可能な変数名が得られます。 オプションファイルの書式は以下です： @table @code @item #comment コメントは @samp{#} か @samp{;} 文字で始めます。空の行は無視します。 @item [group] グループ宣言。 @code{group} はオプションを定義するプログラムかグループの名前です。 この宣言の後、@code{オプション} か @code{set-variable} 行で、このグループにオプションを与えます。 このセクションの範囲は、他のグループ宣言の行が来るか、ファイルの最後に来るまでです。 @item option これはコマンドラインの @code{--option} と等価です。 @item option=value これはコマンドラインの @code{--option=value} と等価です。 @item set-variable = variable=value これはコマンドラインの @code{--set-variable variable=value} と等価です。 これは @code{mysqld} 変数で使用される形式です。 MySQL 4.0 からは @code{--set-variable} は推奨されないことに注意してくだ さい。@code{--variable=value} を使用してください。 @end table @code{client} グループは、全ての MySQL クライアント(@code{mysqld}は除)に対してオプションを定義します。 これはサーバーに接続する際に使用するパスワードを指定できるグループです。 (この場合、オプションファイルは自分だけが読み書きできるようにしてください) オプションや値の善後にある全てのブランク文字は自動で取り除かれます。 値として、@samp{\b},@samp{\t}, @samp{\n}, @samp{\r}, @samp{\\}, @samp{\s} のエスケープシーケンスが使用できます。 (@samp{\s} == blank). オプションファイル例： @example [client] port=3306 socket=/tmp/mysql.sock [mysqld] port=3306 socket=/tmp/mysql.sock set-variable = key_buffer_size=16M set-variable = max_allowed_packet=1M [mysqldump] quick @end example ユーザーオプションファイル例： @example [client] # The following password will be sent to all standard MySQL clients password=my_password [mysql] no-auto-rehash set-variable = connect_timeout=2 [mysqlhotcopy] interactive-timeout @end example @tindex .my.cnf file もしソース配布を持っているなら、 @file{my-xxxx.cnf} という名前のサンプルファイルを @file{support-files} ディレクトリに見ることができます。 もしバイナリ配布を使用しているなら、 @file{DIR/support-files} ディレクトリを探してください (ここで @code{DIR} は MySQL がインストールされたディレクトリのパス名で、 普通は @file{/usr/local/mysql})。 この @file{my-xxxx.cnf} ファイルを自分のディレクトリに @file{.my.cnf} という名前でコピーして使用できます。 オプションファイルをサポートするすべての MySQL クライアントは次 のオプションをサポートします: @multitable @columnfractions .45 .55 @item @strong{Option} @tab @strong{Description} @item --no-defaults @tab オプションファイルを読み込まない。 @item --print-defaults @tab プログラム名と得られる全てのオプションを出力する。 @item --defaults-file=full-path-to-default-file @tab 与えられたコンフィグレーションファイルだけを使用する。 @item --defaults-extra-file=full-path-to-default-file @tab グローバルコンフィグレーションファイルの後、ユーザコンフィグレーションファイルの前にこのコンフィグレーションファイルを読み込む。 @end multitable 注意: 上記のオプションはコマンドラインの先頭になければ働きません！ ただ し、@code{--print-defualts} は @code{--defaults-xxx-file} コマンドの直後 にも置けます。 開発者向け情報：　オプションファイルの操作は全てのオプションをコマンドラインの 引数より先に処理するように簡単に埋め込まれています。 これはオプションを最後に処理するプログラムを複数立ちあげる場合に都合よく動きます。 もしオプションファイルを読み込む機能のない古いプログラムを使用しているなら、 たった二行だけ注意して書けばいいだけです。 この動作については MySQL クライアントプログラムのコードを参考にしてください。 シェルスクリプト内では、@file{my_print_defaults} コマンドを使用して、コ ンフィグファイルを解析することができます: @example shell> my_print_defaults client mysql --port=3306 --socket=/tmp/mysql.sock --no-auto-rehash @end example 上記は、'client' と 'mysql' グループ用の全オプションを出力します。 @node Installing many servers, Multiple servers, Option files, Configuring MySQL @subsection 同じマシンに多くのサーバをインストールする @cindex post-install, many servers @cindex Installing many servers @cindex Starting many servers 同じマシン上で多くの異なる @code{mysqld} デーモン(サーバ)を動作させたい場 合があります。例えば、テスト用に @code{MySQL} の新しいバージョンを使用中の 古いバージョンと共に実行したい場合や、異なる @code{mysqld} サーバにそれを管理する 異なるユーザアクセスを与えたい場合などです。 一つの方法は、新しいサーバを次のように異なるソケットとポートで起動すること です: @tindex @code{MYSQL_UNIX_PORT} environment variable @tindex @code{MYSQL_TCP_PORT} environment variable @tindex environment variable, @code{MYSQL_UNIX_PORT} @tindex environment variable, @code{MYSQL_TCP_PORT} @example shell> MYSQL_UNIX_PORT=/tmp/mysqld-new.sock shell> MYSQL_TCP_PORT=3307 shell> export MYSQL_UNIX_PORT MYSQL_TCP_PORT shell> scripts/mysql_install_db shell> bin/safe_mysqld & @end example The environment variables appendix は @code{mysqld} に影響する他の環境変数の 一覧を含んでいます。 @xref{Environment variables}. The above is the quick and dirty way that one commonly uses for testing. The nice thing with this is that all connections you do in the above shell will automatically be directed to the new running server! If you need to do this more permanently, you should create an option file for each server. @xref{Option files}. In your startup script that is executed at boot time you should specify for both servers: @code{safe_mysqld --defaults-file=path-to-option-file} 少なくとも、次のオプションはサーバごとに異なるようにすべきです: @itemize @item port=# @item socket=path @item pid-file=path @end itemize 次のオプションが使用される場合、異なるようにすべきです: @itemize @item log=path @item log-bin=path @item log-update=path @item log-isam=path @item bdb-logdir=path @item shared-memory-base-name (New in MySQL 4.1) @end itemize さらに性能を求める場合、次も異なるように記述できます: @itemize @item tmpdir=path @item bdb-tmpdir=path @end itemize @xref{Command-line options}. Starting from MySQL 4.1, @code{tmpdir} can be set to a list of paths separated by colon @code{:} (semicolon @code{;} on Windows). They will be used in round-robin fashion. This feature can be used to spread load between several physical disks. バイナリの MySQL バージョン (.tar ファイル) をインストールして、 @code{./bin/safe_mysqld} で起動する場合、多くの場合では、追加/変更する必要 のあるオプションは @code{safe_mysqld} への @code{socket} と @code{port} 引 数だけです。 @xref{Multiple servers, ,Running Multiple MySQL Servers on the Same Machine}. @node Multiple servers, , Installing many servers, Configuring MySQL @subsection 同一マシン上に複数の MySQL サーバーを走らせる @cindex multiple servers @cindex servers, multiple @cindex running, multiple servers 同じマシン上で複数のサーバーを走らせたい場合があります。 例えば、すでに存在しているサーバーはそのままにしておいて、新しい MySQL をテストしたい場合や、 あるいは、インターネットプロバイダーを営んでいて、MySQL をそれぞれの顧客用に提供したい場合など。 複数のサーバーをたちあげる場合、簡単な方法として、 TCP/IP ポート、ソケットファイルを変えて、サーバーをコンパイルする方法があります。 @xref{mysqld_multi, , @code{mysqld_multi}}. そでに走っているサーバーがデフォルトのポート番号とソケットファイルで動作しているとします。 新しくサーバーを作るには、以下のように @code{configure} します： @example shell> ./configure --with-tcp-port=port_number \ --with-unix-socket-path=file_name \ --prefix=/usr/local/mysql-3.22.9 @end example @code{port_number} と @code{file_name} には、デフォルトのポート番号、 ソケットファイルとは違うものを指定します。 そして @code{--prefix} を、すでに走っている MySQL の インストール先とは違うディレクトリーに指定します。 現在走っている MySQL サーバーが使用している ソケットとポートをチェックするには、以下のようにします： @example shell> mysqladmin -h hostname --port=port_number variables @end example Note that if you specify ``@code{localhost}'' as a hostname, @code{mysqladmin} will default to using Unix sockets instead of TCP/IP. In MySQL 4.1 you can also specify the protocol to use by using the @code{--protocol=(TCP | SOCKET | PIPE | MEMORY)} option. あなたが使用しているポートに MySQL サーバーが走っていれば、 これは変更可能な MySQL 変数を(ソケットファイルの名前も含んで)出力します。 この場合、MySQL サーバーを再コンパイルする必要はありません。 @code{safe_mysqld} のオプションを指定してサーバーを起動すれば、 ポートとソケットを変更できます： @example shell> /path/to/safe_mysqld --socket=file_name --port=port_number @end example @code{mysqld_multi} can also take @code{safe_mysqld} (or @code{mysqld}) as an argument and pass the options from a configuration file to @code{safe_mysqld} and further to @code{mysqld}. もし、他のサーバーがロギングを行っているディレクトリと同じデータベースディレクトリを、 新しいサーバーで使用するのであれば、ログファイルの名前を指定すべきです。 ( @code{safe_mysqld} に @code{--log} , @code{--log-update} , @code{--log-slow-queries} を指定する) そうしないと、両方のサーバーが同じログファイルに書き込もうとするからです。 @strong{Warning}: 通常、二つサーバーに同じデータベースを操作させてはいけません！ もし使用している OS が fault-free system locking をサポートしていないと、 これは悲惨なことになるでしょう！ もし二つ目のサーバーに違うデータベースディレクトリを使用させたい場合、 @code{safe_mysqld} に @code{--datadir=path} オプションを指定します。 @strong{Note} also that starting several MySQL servers (@code{mysqlds}) in different machines and letting them access one data directory over @code{NFS} is generally a @strong{bad idea}! The problem is that the @code{NFS} will become the bottleneck with the speed. It is not meant for such use. And last but not least, you would still have to come up with a solution how to make sure that two or more @code{mysqlds} are not interfering with each other. At the moment there is no platform that would 100% reliable do the file locking (@code{lockd} daemon usually) in every situation. Yet there would be one more possible risk with @code{NFS}; it would make the work even more complicated for @code{lockd} daemon to handle. So make it easy for your self and forget about the idea. The working solution is to have one computer with an operating system that efficiently handles threads and have several CPUs in it. もし違うポートで走っている MySQL サーバーに、 これまた違うポートを使用するように作られたクライアントから接続したい場合、 以下のようにします： @itemize @bullet @item クライアントを TCP/IP での接続 @code{--host 'hostname' --port=port_numer} か Unix ソケット経由での接続 @code{[--host localhost] --socket=file_name} オプションで起動します。 @item Start the client with @code{--protocol=tcp} to connect with TCP/IP and @code{--protocol=socket} to connect via a Unix socket. @item C あるいは Perl プログラムの場合、MySQL サーバーのポートとソケットを与えることができます。 @item If your are using the Perl @code{DBD::mysql} module you can read the options from the MySQL option files. @xref{Option files}. @example $dsn = "DBI:mysql:test;mysql_read_default_group=client; mysql_read_default_file=/usr/local/mysql/data/my.cnf" $dbh = DBI->connect($dsn, $user, $password); @end example @item @tindex MYSQL_UNIX_PORT environment variable @tindex MYSQL_TCP_PORT environment variable @tindex environment variable, MYSQL_UNIX_PORT @tindex environment variable, MYSQL_TCP_PORT @code{MYSQL_UNIX_PORT} と @code{MYSQL_TCP_PORT} 環境変数に Unix ソケットファイルと TCP/IP のポート番号とセットし、クライアントを立ちあげます。 もし、このポート番号やソケットファイルを常に使用するのであれば、 @file{.login} ファイルかなにかに環境変数をセットするように書いておけばよいでしょう。 @xref{Environment variables}. @item @tindex .my.cnf file あなたのホームディレクトリの @file{.my.cnf} ファイルに、 通常使用するポート番号とソケットファイルを書くこともできます。 @xref{Option files}. @end itemize @node Privilege system, User Account Management, Configuring MySQL, MySQL Database Administration @section General Security Issues and the MySQL Access Privilege System @cindex system, security @cindex access privileges @cindex privileges, access @cindex security system @cindex ACLs MySQL has an advanced but non-standard security/privilege system. This section describes how it works. @menu * General security:: General security * Security:: How to make MySQL secure against crackers * Privileges options:: Startup Options for @code{mysqld} Concerning Security * LOAD DATA LOCAL:: * What Privileges:: What the privilege system does * Privileges:: How the privilege system works * Privileges provided:: Privileges provided by MySQL * Connecting:: Connecting to the MySQL server * Connection access:: Access control, stage 1: Connection verification * Request access:: Access control, stage 2: Request verification * Access denied:: Causes of @code{Access denied} errors @end menu @node General security, Security, Privilege system, Privilege system @subsection General Security Guidelines よくあるセキュリティの間違いを避けるために、インターネットに接続されたコン ピュータ上で MySQL を使用する誰もが、このセクションを読むべきです。 ``セキュリティ'' の議論において、我々は、すべての該当するアタックタイプ (eavesdropping, altering, playback, Denial of Service) に対して、すべてのサー バホスト(MySQL サーバだけではなく)の完全な保護の必要性を強調しま す。We do not cover all aspects of availability and fault tolerance here. MySQL は、ユーザが実行しようとするすべての接続、クエリ、その他の オペレーションに対して、アクセス制御リスト(ACLs: Access Control Lists)セキュ リティを使用します。MySQL クライアントとサーバの間で SSL 暗号化接 続のサポートもいくつかあります。ここで議論されるコンセプトの多くは、 MySQL に特有のものではありません; 同じ一般的なアイデアはほとんど すべてのアプリケーションに適用します。 MySQL 実行時、可能な限りいつでもこれらのガイドラインに従ってくだ さい: @itemize @bullet @item (mysql root ユーザ以外の)誰にも @code{mysql} データベース内の @code{user} テーブルへのアクセスを与えないでください！ 暗号化されたパスワー ドは MySQL の本当のパスワードです。もしあなたが与えられたユーザに ついて @code{user} テーブルにリストされたパスワードを知ることができれば、 そのアカウントについてリストされたホストへアクセスすれば、あなたは簡単にそ のユーザとしてログインできます。 @item MySQL access privilege system の理解に努めるべきです。 @code{GRANT} と @code{REVOKE} コマンドは MySQL へのアクセスを制限するための物です。 必要以上の権限を誰にも与えないでください。 全てのホストに対して、何か出来るような許可を与えてはいけません。 Checklist: @itemize @minus @item @code{mysql -u root} を行ってみます。 パスワードを尋ねられること無しにサーバへの接続ができる場合、問題があります。 どのユーザでも(root でなくても)、MySQL サーバに完全な権限で接続で きます！ @code{root} パスワードの設定についての項目に特別な注意を払って MySQL インストール説明を見直してください。 @item @code{SHOW GRANTS} を使用し、だれがなんのアクセスを持つかチェックします。 必要ない権限を、@code{REVOKE} コマンドを使用して削除してください。 @end itemize @item いかなる平文パスワードもデータベースに保存しないようにします。 あなたのコンピュータが妥協される時、新入者はパスワードの完全なリストを得て、 それらを使用できます。代わりに @code{MD5()}, @code{SHA1()} や 他の one-way hashing 関数を使用してください。 (@code{SHA1()}はバージョン4.0.2から。@code{MD5()}はバージョン3.23.2から。) @item 辞書からパスワードを選んではいけません。 それらを破る プログラムがあるのです。 ``xfish98'' のようなパスワードは悪い例です。 これよりは ``duag98'' の方がよいでしょう。 これは "fish" を打つ際に、 キーを一つずつずらしたものです。 他の方法としては、 "Mhall" 、これは "Mary had a little lamb" という文の頭文字を羅列したものです。 これを知っている物には打ちやすいパスワードですが、知らない者にとっては、 類推することが難しいパスワードです。 @item ファイアーウォールを導入します。This protects you from at least 50% of all types of exploits in any software. MySQL をファイアーウォール で守られた方に置くか、DMZ (緩衝地帯, 非武装地帯) に置きます。 Checklist: @itemize @minus @item インターネットから @code{nmap} のようなツールを使用して、 あなたのマシンのポートをスキャンしてみます。 MySQL はデフォルトで 3306 番を使用しています。 このポートには信用できないホストからはアクセスできないようにすべきです。 MySQL ポートがオープンしているかどうかをチェックする他の簡単な方 法は、次のコマンドをいくつかのリモートマシンから試すことです。ここで @code{server_host} はあなたの MySQL サーバのホスト名です: @example shell> telnet server_host 3306 @end example 接続し、いくつかのゴミ文字が得られた場合、ポートはオープンして います。それをオープンしておく正当な理由が本当にない限り、ファイアーウォー ルやルータでクローズすべきです。@code{telnet} がハングしたり拒否されたり する場合、すべて OK です。ポートはブロックされています。 @end itemize @item ユーザーから入力されたデータは信頼しないで下さい。 ユーザーは、Webのフォーム、URL、あるいはあなたのカスタムプログラムから 特定の文字を入れることが可能です。 もしユーザーがフォームに @code{; DROP ALL DATABASES ;} のような文字を入力しても、 あなたのアプリケーションは安全ですか？ これは極端な例ですが、それらに対して準備しない場合、似たようなテクニックを 使用するハッカーの結果として、大きなセキュリティリークとデータ喪失が発生し 得ます。 数値データのチェックも忘れないでください。よくある間違いは文字列しか保護し ないことです。時々、人はデータベースが保護される必要のない公に有効なデータ だけを含んでいるかどうかを考えます。これは間違いです。少なくとも、 denial-of-service タイプのアタックはそのようなデータベースでも実行されます。 このタイプのアタックから保護するもっとも簡単な方法は、数値定数の回りにアポ ストロフィを使用することです: @code{SELECT * FROM table WHERE ID=234} の代 わりに @code{SELECT * FROM table WHERE ID='234'}。 MySQL は自動的 にこの文字列を数値に変換し、そこからすべての非数値シンボルを取り除きます。 Checklist: @itemize @minus @item すべての Web アプリケーション: @itemize @bullet @item あなたの WWW の全てのフォームに、@samp{'} と @samp{"} を入力することを試みてください。 もしなんらかの MySQL エラーがでたら、あなたのサイトを停止したほうが よいでしょう。 @item あなたの URL に @code{%22} (@samp{"}), @code{%23} (@samp{#}) , @code{%27} (@samp{'}) をつけてみて、動的URLを いろいろ変更して試してみてください。 @item 動的 URL のデータタイプを数値から上述の例の文字を含む文字列に修正してみて ください。アプリケーションはこれと似たようなアタックに対して安全であるべき です。 @item 数値フィールドに対して、文字、スペース、特殊文字の入力を試みてください。 アプリケーションは、それらを MySQL に送る前に取り除くか、 あるいはエラーを出すべきです。 検査しない値を MySQL に送ることは危険です。 @item MySQL にデータを送る前に、そのサイズをチェックします。 @item あなたのアプリケーションが、管理目的であなたが使用するのと異なるユーザ名を 使用してデータベースに接続することを考慮してください。必要以上のアクセス権 をアプリケーションに与えないで下さい。 @end itemize @item Users of PHP: @itemize @bullet @item Check out the @code{addslashes()} function. As of PHP 4.0.3, a @code{mysql_escape_string()} function is available that is based on the function of the same name in the MySQL C API. @end itemize @item Users of MySQL C API: @itemize @bullet @item Check out the @code{mysql_real_escape_string()} API call. @end itemize @item Users of MySQL++: @itemize @bullet @item Check out the @code{escape} and @code{quote} modifiers for query streams. @end itemize @item Users of Perl DBI: @itemize @bullet @item Check out the @code{quote()} method or use placeholders. @end itemize @item Users of Java JDBC: @itemize @bullet @item Use a @code{PreparedStatement} object and placeholders. @end itemize @end itemize @item 生のデータ(暗号化されていないデータ)をインターネット越しに送ってはいけませ ん。このデータは、その情報をトラップして、どこかで再利用することに興味のあ る誰にでもアクセス可能です。もし送る必要があるなら、SSL のような暗号化され た通信を使用すべきです。MySQL はバージョン 4.0.0 から内部 SSL 接 続をサポートします。暗号化された(そして圧縮された)通信のトンネルを生成する ために、SSH ポートフォワーディングを使用することができます。 @item @code{tcpdump} と @code{strings} ユーティリティを使うことを学んで下さい. 以下のコマンドで、ほとんどの場合、暗号化されていない MySQL のデータが見えるでしょう： @example shell> tcpdump -l -i eth0 -w - src or dst port 3306 | strings @end example (この例は Linux のものです。他のシステムでは少し違うでしょう). 警告: データが見えなくても、実際に常に暗号化されているわけではありません。 高いセキュリティが必要なら、セキュリティエキスパートに相談すべきです。 @end itemize @node Security, Privileges options, General security, Privilege system @subsection MySQL をクラッカーに対して安全にする方法 @cindex crackers, security against @cindex security, against crackers MySQL サーバーに接続するときは、パスワードを使用すべきです。 パスワードはコネクション間で、べたテキストでは流れません。 しかし、暗号化アルゴリズムはそんなに強力なわけではありません。クライアント とサーバ間のトラフィックを sniff できれば、いくつかの試みで、賢いアタッカー はパスワードをクラックできます。クライアントとサーバ間の接続が信頼できない ネットワークを通るなら、通信を暗号化するために SSH トンネルを使用 すべきです。 その他の全ての情報はテキストで転送され、 これは接続を覗くことが出来る人に読まれます。 もしこれを心配するなら、圧縮プロトコル(MySQL バージョン 3.22 以上)を 使用することが出来ます。より安全にしたい場合、 @code{ssh} をインストールすべきです。 オープンソースの @code{ssh} クライアントは @uref{http://www.openssh.org/} に、 商用の @code{ssh} クライアントは @uref{http://www.ssh.com/} に見ることができます。 これを使用すれば、MySQL サーバーと MySQL クライアント 間の TCP/IP コネクションは全て暗号化されます。 If you are using MySQL 4.0, you can also use internal OpenSSL support. @xref{Secure connections}. MySQL システムを安全にするためには、次のことを考えるべきです: @itemize @bullet @item 全ての MySQL ユーザにパスワードを使用すべきです。 @code{other_user} にパスワードが設定されていない場合、 誰でも @code{mysql -u other_user db_name} として簡単に他の人としてログインでき ることを覚えてください。これは全てのクライアント／サーバアプリケーション で一般的な振る舞いです。全てのユーザのパスワードは、 @code{mysql_install_db} スクリプトを実行前に編集することで、または MySQL @code{root} ユーザだけは次のようにして変更することができます。 @example shell> mysql -u root mysql mysql> UPDATE user SET Password=PASSWORD('new_password') -> WHERE user='root'; mysql> FLUSH PRIVILEGES; @end example @item MySQL デーモンを Unix の @code{root} ユーザーで実行しないでください。 @code{FILE}権限を持つ任意のユーザが @code{root} としてファイル(例えば、 @code{~root/.bashrc})を生成できるためとても危険です。これを防ぐために、 @code{mysqld} は、@code{--user=root} オプションで直接指定されない限り、 @code{root} としての実行を拒否します。 代わりに @code{mysqld} は権限を持たない一般ユーザとして実行できます。 より安全にするため、新しく Unix ユーザ @code{mysql} を追加することもできます。 @code{mysqld} を 他の Unix ユーザーで起動したとしても、 MySQL の @code{user} テーブルの @code{root} ユーザーの名前を変更する必要はありません。 なぜなら、 MySQL ユーザーの名前は Unix のユーザー名とはなんの関係もないからです。 root ユーザ名を変更する必要はありません。 @code{mysqld} を他の Unix ユーザで起動するためには、@file{/etc/my.cnf} オ プションファイルまたはサーバのデータディレクトリの @file{my.cnf} オプショ ンファイルの、@code{[mysqld]} グループにユーザ名を記述した @code{user} 行 を追加してください。たとえば: @example [mysqld] user=mysql @end example これは、あなたが手動で起動したり @code{safe_mysqld} または @code{mysql.server} を使用して起動しても、指定されたユーザでサーバを起動さ せます。詳細は、@ref{Changing MySQL user}. を見てください。 @item Don't support symlinks to tables (this can be disabled with the @code{--skip-symlink} option). This is especially important if you run @code{mysqld} as root as anyone that has write access to the mysqld data directories could then delete any file in the system! @xref{Symbolic links to tables}. @item データベースディレクトリは @code{mysqld} を実行している Unix ユーザだけが 読み込み／書き込み可能なことをチェックしてください。 @item @code{PROCESS} 権限を全てのユーザに与えないでください。この許可がある人は誰でも @code{mysqladmin processlist} コマンドで実行されているクエリーの中身を見ることができます。 もし誰かが、@code{UPDATE user SET password=PASSWORD('not_secure')} クエリーを 実行していたとして、それが見えてしまいます。 @code{mysqld} は @code{PROCESS} 権限を持つユーザに対する特別な接続をリザーブします。 そのため、たとえ全ての通常接続が使われたとしても、MySQL @code{root} ユーザだけは、 ログインでき、いろいろチェックできます。 @item @code{FILE} 権限を全てのユーザに与えないでください。ユーザがこの権限を持つ場合、 @code{mysqld} デーモンを実行している Unix ユーザーの権限で ファイルシステム内のどこにでもファイルを書き込むことができます！ これを少し安全にするため、@code{SELECT ... INTO OUTFILE} で作成される全てのファイルは 全員が書き込み可能な状態で生成されますが、 既存のファイルを上書きすることができないようになっています。 @tindex @file{/etc/passwd} @code{FILE} 権限はサーバーを走らせている Unix ユーザーがアクセスできる 全てのファイルを読むために使用されかもしれません。 いかなるファイルもカレントのデータベースに取りこめます。 例えば、 @code{LOAD DATA} を使用して @file{/etc/passwd} をテーブルに 取り込むと、@code{SELECT} でその内容が読めることになります。 @item あなたの DNS を信用しない場合、権限テーブル内にはホスト名の代わりに IP を使用すべきです。@code{mysqld} への @code{--secure} オプションは原理上はホスト名を安 全にします。どんな場合でも、ワイルドカードを含んだホスト名を、許可テーブルに登録する 事は本当に注意深くすべきです！ @item 一ユーザからの接続数を制限したい場合は、@code{mysqld} の @code{max_user_connections} 変数を設定することで、これを行なうことができま す。 @end itemize @node Privileges options, LOAD DATA LOCAL, Security, Privilege system @subsection セキュリティに関する @code{mysqld} の起動オプション @code{mysqld} の次のオプションはセキュリティに影響します: @table @code @item --local-infile[=(0|1)] If one uses @code{--local-infile=0} then one can't use @code{LOAD DATA LOCAL INFILE}. @item --safe-show-database With this option, the @code{SHOW DATABASES} command returns only those databases for which the user has some kind of privilege. From version 4.0.2 this option is deprecated and doesn't do anything (the option is enabled by default) as we now have the @code{SHOW DATABASES} privilege. @xref{GRANT}. @item --safe-user-create If this is enabled, an user can't create new users with the @code{GRANT} command, if the user doesn't have the @code{INSERT} privilege for the @code{mysql.user} table. If you want to give a user access to just create new users with those privileges that the user has right to grant, you should give the user the following privilege: @example mysql> GRANT INSERT(user) ON mysql.user TO 'user'@@'hostname'; @end example This will ensure that the user can't change any privilege columns directly, but has to use the @code{GRANT} command to give privileges to other users. @item --skip-grant-tables 特権システムを全く使用しません。これは全員に全てのデータベースへの @emph{完全なアクセス} を与えます！ (@code{mysqladmin flush-privileges} か @code{mysqladmin reload} を実行することで、 起動しているサーバーは特権システムを使用するようになります。) @item --skip-name-resolve ホスト名を解析しません。権限テーブル中の全ての @code{Host}フィールドは IP アドレスか @code{localhost} でなければなりません。 @item --skip-networking ネットワーク (TCP/IP) 経由の接続を許可しません。@code{mysqld} への全ての接続は、 Unix ソケットで行われます。MIT-pthreads は Unix ソケットをサポートしない ため、このオプションは MIT-pthreads を使用するシステム上で MySQL 3.23.27 以前のバージョンを使用する場合は、うまく動きません。 @item --skip-show-database Don't allow @code{SHOW DATABASES} command, unless the user has the @code{SHOW DATABASES} privilege. From version 4.0.2 you should no longer need this option, since access can now be granted specifically with the @code{SHOW DATABASES} privilege. @end table @node LOAD DATA LOCAL, What Privileges, Privileges options, Privilege system @subsection Security issues with LOAD DATA LOCAL In MySQL 3.23.49 and MySQL 4.0.2, we added some new options to deal with possible security issues when it comes to @code{LOAD DATA LOCAL}. There are two possible problems with supporting this command: As the reading of the file is initiated from the server, one could theoretically create a patched MySQL server that could read any file on the client machine that the current user has read access to, when the client issues a query against the table. In a web environment where the clients are connecting from a web server, a user could use @code{LOAD DATA LOCAL} to read any files that the web server process has read access to (assuming a user could run any command against the SQL server). There are two separate fixes for this: If you don't configure MySQL with @code{--enable-local-infile}, then @code{LOAD DATA LOCAL} will be disabled by all clients, unless one calls @code{mysql_options(... MYSQL_OPT_LOCAL_INFILE, 0)} in the client. @xref{mysql_options, , @code{mysql_options()}}. For the @code{mysql} command-line client, @code{LOAD DATA LOCAL} can be enabled by specifying the option @code{--local-infile[=1]}, or disabled with @code{--local-infile=0}. By default, all MySQL clients and libraries are compiled with @code{--enable-local-infile}, to be compatible with MySQL 3.23.48 and before. One can disable all @code{LOAD DATA LOCAL} commands in the MySQL server by starting @code{mysqld} with @code{--local-infile=0}. In the case that @code{LOAD DATA LOCAL INFILE} is disabled in the server or the client, you will get the error message (1148): @example The used command is not allowed with this MySQL version @end example @node What Privileges, Privileges, LOAD DATA LOCAL, Privilege system @subsection 特権システムの行うこと @cindex system, privilege @cindex privilege system @cindex passwords, security MySQL 特権システムの基本機能は、与えられたホストから接続する ユーザを認証すること、そしてデータベースに対する @code{SELECT}, @code{INSERT}, @code{UPDATE}, @code{DELETE} 等の権限を与えることです。 拡張機能は匿名ユーザをもつ能力を含み、@code{LOAD DATA INFILE} のような MySQL 固有の機能を使用する許可を与えます。 @node Privileges, Privileges provided, What Privileges, Privilege system @subsection 特権システムはどのように動くか？ @cindex privilege system, described MySQL の特権システムは、全てのユーザーが与えられた許可の範囲内で動く事を保証します。 MySQL サーバーに接続するとき、本人の身元は、@strong{接続元のホスト} と @strong{接続に使用するユーザー名} によって確認されます。 このシステムは、あなたの身元と@strong{あなたが要求することが何か} によって、権限を与えます。 MySQL はあなたのホスト名とユーザー名の両方をあわせてチェックします。 これはインターネット上に同じ名前のユーザーがどこかにいるかもしれないということからそうしています。 例えば、@code{office.com} から接続してきた @code{joe} と、 @code{elsewhere.com} から接続してきた @code{joe} は同一人物である必要はありません。 MySQL はこの違うホストから接続してきた同名のユーザーを以下のようにして扱います： @code{office.com} から接続した @code{joe} にある許可をあたえ、 それとは違う許可を @code{elsewhere.com} から接続してきた @code{joe} に与えます。 MySQL のアクセスコントロールは以下の二つからなります： @itemize @bullet @item Stage 1: サーバーは接続許可があるかどうかをチェックします。 @item Stage 2: 接続許可後、サーバーはそれぞれのリクエストをチェックします。 あなたが要求してきた事柄を、あなたが実行できるかどうかをチェックします。 例えば、あるデータベースのテーブルの行の取り出しやテーブルの破棄をあなたが命令した場合、 サーバーは、あなたにそのテーブルに対する @code{SELECT} 権限があるのか、 データベースに対して @code{DROP} する許可が与えられているのか、を確認します。 @end itemize サーバーは @code{mysql} データベースの @code{user}, @code{db}, @code{host} ３つのテーブルから、 この２つのアクセス制限を決定します。 このテーブルのフィールドは以下のようになっています： @multitable @columnfractions .20 .20 .20 .20 @item @strong{Table name} @tab @code{user} @tab @code{db} @tab @code{host} @item @strong{Scope fields} @tab @code{Host} @tab @code{Host} @tab @code{Host} @item @tab @code{User} @tab @code{Db} @tab @code{Db} @item @tab @code{Password} @tab @code{User} @tab @item @strong{Privilege fields} @tab @code{Select_priv} @tab @code{Select_priv} @tab @code{Select_priv} @item @tab @code{Insert_priv} @tab @code{Insert_priv} @tab @code{Insert_priv} @item @tab @code{Update_priv} @tab @code{Update_priv} @tab @code{Update_priv} @item @tab @code{Delete_priv} @tab @code{Delete_priv} @tab @code{Delete_priv} @item @tab @code{Index_priv} @tab @code{Index_priv} @tab @code{Index_priv} @item @tab @code{Alter_priv} @tab @code{Alter_priv} @tab @code{Alter_priv} @item @tab @code{Create_priv} @tab @code{Create_priv} @tab @code{Create_priv} @item @tab @code{Drop_priv} @tab @code{Drop_priv} @tab @code{Drop_priv} @item @tab @code{Grant_priv} @tab @code{Grant_priv} @tab @code{Grant_priv} @item @tab @code{References_priv} @tab @tab @item @tab @code{Reload_priv} @tab @tab @item @tab @code{Shutdown_priv} @tab @tab @item @tab @code{Process_priv} @tab @tab @item @tab @code{File_priv} @tab @tab @end multitable 　アクセスコントロールの第2段階(要求承認)のために、サーバーはこれら 3 つの テーブルによって決められた許可を基本としますが、もしテーブルに対する要求で あるならば、@code{tables_priv} と @code{columns_priv} テーブルを さらに調べます。これらのテーブルのフィールドは以下のようになっています： @multitable @columnfractions .20 .20 .20 @item @strong{Table name} @tab @code{tables_priv} @tab @code{columns_priv} @item @strong{Scope fields} @tab @code{Host} @tab @code{Host} @item @tab @code{Db} @tab @code{Db} @item @tab @code{User} @tab @code{User} @item @tab @code{Table_name} @tab @code{Table_name} @item @tab @tab @code{Column_name} @item @strong{Privilege fields} @tab @code{Table_priv} @tab @code{Column_priv} @item @tab @code{Column_priv} @tab @item @strong{Other fields} @tab @code{Timestamp} @tab @code{Timestamp} @item @tab @code{Grantor} @tab @end multitable 　テーブルの各フィールドを分類すると、２種類にわかれます： 適用範囲を指定するフィールド(以下　スコープフィールド)と許可を定義するフィールド(以下　権限フィールド)です。 　スコープフィールドは、権限テーブルの登録ごとに、その適用範囲を決めます。 例えば、 @code{user} テーブルの @code{Host} と @code{User} に @code{'thomas.loc.gov'} と @code{'bob'} が登録されている場合、 サーバーへの接続は ホスト @code{thomas.loc.gov} から来た @code{'bob'} に許可されます。 同様に、@code{db} テーブルの @code{Host}, @code{User}, @code{Db} に @code{'thomas.loc.gov'}, @code{'bob'}, @code{'reports'} が登録されていると、 ホスト @code{thomas.loc.gov} から来た @code{bob} に対し @code{reports} データベースへの接続が許されます。 @code{tables_priv} と @code{columns_priv} テーブルは、 テーブルか、テーブルとフィールドを対にしたスコープフィールドを含みます。 @cindex case-sensitivity, in access checking 　アクセスのチェックは、@code{Host} の値はケース非依存で比較されます。 @code{User}, @code{Password}, @code{Db}, @code{Table_name} の値はケース依存で比較されます。 @code{Column_name} の値は MySQL バージョン 3.22.12 以上ではケース非依存で比較されます。 (バージョン 3.22.11 までは ケース依存です) 権限フィールドは、どのような操作が実行できるか、許可されているかを示します。 サーバーは権限テーブルの情報を、ユーザーの権限を得るために使用します。 このユーザーの権限を割り出す方法は @ref{Request access} に述べておきます。 スコープフィールドは文字で定義され、デフォルト値は空文字になっています： @multitable @columnfractions .20 .15 .65 @item @strong{Field name} @tab @strong{Type} @tab @strong{Notes} @item @code{Host} @tab @code{CHAR(60)} @tab @item @code{User} @tab @code{CHAR(16)} @tab @item @code{Password} @tab @code{CHAR(16)} @tab @item @code{Db} @tab @code{CHAR(64)} @tab (@code{CHAR(60)} for the @code{tables_priv} and @code{columns_priv} tables) @item @code{Table_name} @tab @code{CHAR(60)} @tab @item @code{Column_name} @tab @code{CHAR(60)} @tab @end multitable @code{user}, @code{db}, @code{host} テーブルでは、 全ての権限フィールドは @code{ENUM('N','Y')} で定義されます。 この値は @code{'N'} か @code{'Y'} のどちらかで、デフォルト値は @code{'N'} です。 @code{tables_priv} と @code{columns_priv} テーブルでは、 権限フィールドは @code{SET} フィールドとして定義されます： @multitable @columnfractions .15 .15 .55 @item @strong{Table name} @tab @strong{Field name} @tab @strong{Possible set elements} @item @code{tables_priv} @tab @code{Table_priv} @tab @code{'Select', 'Insert', 'Update', 'Delete', 'Create', 'Drop', 'Grant', 'References', 'Index', 'Alter'} @item @code{tables_priv} @tab @code{Column_priv} @tab @code{'Select', 'Insert', 'Update', 'References'} @item @code{columns_priv} @tab @code{Column_priv} @tab @code{'Select', 'Insert', 'Update', 'References'} @end multitable サーバーは以下のように権限テーブルを使用します： @itemize @bullet @item @code{user} テーブルのスコープフィールドは、接続要求を受け入れるか拒否するかを決定します。 許可された接続について、@code{user} テーブルで与えられたすべての権限は、ユー ザのグローバル(スーパーユーザ)権限を示します。この権限はサーバ上の @strong{すべての} データベースに適用されます。 (訳注： 例えば、@code{user} テーブル の権限を @code{'Y'} にした場合、 どんなに @code{db} テーブルや @code{host} テーブルで権限を @code{'N'} にしたとしても 権限は @code{'Y'} のままである。 つまり @code{user} テーブルの権限許可 @code{'Y'} が全てに反映されてしまうという事。 @code{user} テーブルには最低限の許可を与えるようにし、 @code{db} テーブルや @code{host} テーブルで、それぞれの権限を許可する方が無難。 ) @item @code{db} と @code{host} テーブルは一緒に使用されます： @itemize @minus @item @code{db} テーブルのスコープフィールドはどのホストからどのデータベースのアクセスできるかを決定します。 権限フィールドは、どういった操作ができるかを定義します。 @item @code{host} テーブルは、@code{db} テーブルの登録をいくつかのホストに与えたい時に、 @code{db} テーブルの拡張として使用されます。 例えば、ネットワーク上の限定したマシンからデータベースを使用したい場合、 @code{db} テーブルの @code{Host} の値は空にしておきます。 そして @code{host} テーブルにそれぞれのホストについての登録を行います。 この機構は、 @ref{Request access} で詳細に述べられています。 @end itemize @item @code{tables_priv} と @code{columns_priv} テーブルは @code{db} テーブルに似ていますが、 それらはより細かく定義できます； データベースレベルではなく、テーブルとフィールドのレベルで与えます。 @end itemize 管理者権限 (@code{RELOAD}, @code{SHUTDOWN},など) は @code{user} テーブルにだけ定義するように。 これは、管理者操作はデータベースではなくサーバーへの操作であり、 他の許可テーブルにある必要がないからです。 またこうしておくと、管理者操作の許可は、@code{user} テーブルの定義だけを 見ればわかるようになります。 @code{FILE} 操作の権限は @code{user} テーブルにだけ定義するように。 これは管理者操作ではありませんが、アクセスしているデータベースにかかわらず、 サーバー内のファイルを読み書きできるのです。 @code{mysqld} サーバーは起動時にこれらのテーブルを読み込みます。 許可テーブルの変更を反映させる方法はこちらを参照のこと → @ref{Privilege changes} これらのテーブルの登録を変更した場合、思ったとおりの権限状態になっている事を確認することはいいことです。 問題の解決には, @ref{Access denied}. セキュリティに関するアドバイスは @ref{Security}. 便利なツールとして @code{mysqlaccess} スクリプト( Yves Carlier 作)が MySQL の配布に含まれています。 @code{mysqlaccess} を @code{--help} オプションで起動するとヘルプが表示されます。 @code{mysqlaccess} は @code{user},@code{db} and @code{host} テーブルだけしか 検査しません。テーブルレベルの権限、フィールドレベルの権限は調べません。 @node Privileges provided, Connecting, Privileges, Privilege system @subsection MySQL が提供する権限 @cindex privilege information, location 権限の設定は @code{mysql} データベースの @code{user}, @code{db}, @code{host}, @code{tables_priv}, @code{columns_priv} で行います。 (@code{mysql} はデータベースの名前です) MySQL サーバーは、サーバーの起動時か @ref{Privilege changes} で説明されている方法により、 これらのテーブルから権限の設定を読み込みます。 MySQL 4.0.2 が提供する権限の名称は, 本マニュアルでは以下の表の名称を用います。 この表の項目名がそれぞれの許可される権限とその説明に対応しています： @c FIX agl 2002-06-13 Long items added, will need to re-measure colwidths! @multitable @columnfractions .15 .20 .35 @item @strong{Privilege} @tab @strong{Column} @tab @strong{Context} @item @code{ALTER} @tab @code{Alter_priv} @tab tables @item @code{DELETE} @tab @code{Delete_priv} @tab tables @item @code{INDEX} @tab @code{Index_priv} @tab tables @item @code{INSERT} @tab @code{Insert_priv} @tab tables @item @code{SELECT} @tab @code{Select_priv} @tab tables @item @code{UPDATE} @tab @code{Update_priv} @tab tables @item @code{CREATE} @tab @code{Create_priv} @tab databases, tables, or indexes @item @code{DROP} @tab @code{Drop_priv} @tab databases or tables @item @code{GRANT} @tab @code{Grant_priv} @tab databases or tables @item @code{REFERENCES} @tab @code{References_priv} @tab databases or tables @item @code{CREATE TEMPORARY TABLES} @tab @code{Create_tmp_table_priv} @tab server administration @item @code{EXECUTE} @tab @code{Execute_priv} @tab server administration @item @code{FILE} @tab @code{File_priv} @tab file access on server @item @code{LOCK TABLES} @tab @code{Lock_tables_priv} @tab server administration @item @code{PROCESS} @tab @code{Process_priv} @tab server administration @item @code{RELOAD} @tab @code{Reload_priv} @tab server administration @item @code{REPLICATION CLIENT} @tab @code{Repl_client_priv} @tab server administration @item @code{REPLICATION SLAVE} @tab @code{Repl_slave_priv} @tab server administration @item @code{SHOW DATABASES} @tab @code{Show_db_priv} @tab server administration @item @code{SHUTDOWN} @tab @code{Shutdown_priv} @tab server administration @item @code{SUPER} @tab @code{Super_priv} @tab server administration @end multitable @code{SELECT}, @code{INSERT}, @code{UPDATE}, @code{DELETE} の権限は、 存在しているデータベースのテーブルに対して許可されます。 もしテーブルから行を取り出すだけなら、@code{SELECT} 構文を実行するためには @code{SELECT} 権限だけあればかまいません。 ただし、サーバーのどのデータベースにアクセスを許可されていない場合でも、 ある種の @code{SELECT} は実行することができます。 例えば、簡単な計算を @code{mysql} クライアントで行う場合です： @example mysql> SELECT 1+1; mysql> SELECT PI()*2; @end example @code{INDEX} 権限はインデックスの作成と破棄(削除)を許可します。 @code{ALTER} 権限は @code{ALTER TABLE} の実行を許可します。 @code{CREATE} と @code{DROP} 権限は、新しいデータベースやテーブルの作成、 あるいは既に存在するデータベース、テーブルの破棄(削除)を許可します。 注意： @code{mysql} データベースに登録されているユーザーに @code{DROP} 権限を与えると、 そのユーザーは MySQL のアクセス権限が格納されているデータベースを破棄できます！ @code{GRANT} 権限は、あなたが他のユーザーに対して自分の権限を持たせる事を許可します。 @code{FILE} 権限を与えると、@code{LOAD DATA INFILE} と @code{SELECT ... INTO OUTFILE} 構文を 使用して、サーバーのファイルを読み書きする事ができます。 この権限が与えられたユーザーは、MySQL サーバーを使用していかなるファイルも 読むことが出来ますし、MySQL サーバーが書き込めるディレクトリに誰もが読める 新しいファイルを作成することも出来ます。 そのユーザーはカレントのデータベースのディレクトリにあるいかなるファイルも 読むことができます。 しかし、既に存在しているファイルを変更することはできません。 残りの権限はアドミン操作に関する許可で、@code{mysqladmin} コマンドを使用して実行します。 次の表に @code{mysqladmin} コマンドのどれが、どの権限に対応しているかを示します： @multitable @columnfractions .15 .75 @item @strong{Privilege} @tab @strong{Commands permitted to privilege holders} @item @code{RELOAD} @tab @code{reload}, @code{refresh}, @code{flush-privileges}, @code{flush-hosts}, @code{flush-logs}, and @code{flush-tables} @item @code{SHUTDOWN} @tab @code{shutdown} @item @code{PROCESS} @tab @code{processlist} @item @code{SUPER} @tab @code{kill} @end multitable @code{reload} コマンドはサーバーに権限の設定を再読込させるように伝えます。 @code{refresh} コマンドは全てのテーブルをフラッシュし、ログファイルを開き直します。 @code{flush-privileges} は @code{reload} と同義です。 その他の @code{flush-*} コマンドは @code{refresh} の動作とよく似ていますが、 適用範囲を絞っており、ちょっとした場合に有効です。 例えば、ログファイルだけをフラッシュしたい場合、 @code{refresh} を行うよりも @code{flush-logs} がいいです。 @code{shutdown} コマンドは、サーバーをシャットダウンします。 @code{processlist} コマンドはサーバーが実行しているスレッドの情報を表示します。 @code{kill} コマンドはサーバーのスレッドをkillします。 自分のスレッドは常に表示、killできますが、他人のスレッドを見るには @code{PROCESS} 権限が必要で、他人のスレッドをkillするには @code{SUPER} 権限が必要です。@xref{KILL}. (@code{SUPER} 権限は 4.0.2で追加されました) ある権限を欲しがるユーザーだけにその権限を許可するのはよい考えですが、 権限を与えるときには、特定の事項を熟知していなければなりません： @itemize @bullet @item @code{GRANT} 権限を許可されたユーザーは、他のユーザーの権限を変える事ができます。 二人のユーザー間で違っている権限と @code{grant} 権限を入れ換えることができます。 @item @code{ALTER} 権限は、テーブル名の変更を行うことにより特権システムを破るために 使用されるかもしれません。 @item @code{FILE} 権限は、サーバー上にある全ての読み込み可能なファイルと カレントのデータベースのディレクトリにあるファイルを、 データベースのテーブルに取り込むことができ、 その内容は @code{SELECT} 文を使用することでアクセスできます。 @item @code{SHUTDOWN} 権限は、他のユーザーに対するサービスを、サーバーを 停止することによって、拒否するようにできます。 @item @code{PROCESS} 権限は実行されているクエリーをプレーンテキストで見ることに使えます。 パスワードの設定、変更のクエリーも含みます。 @item @code{mysql} データベースに対しての権限は、パスワードの変更や他の権限の変更に、使用されます。 (パスワードは暗号化されて登録されており、悪意のあるユーザーでも 単純に読むことはできません). @code{mysql.user} のパスワードフィールドにアクセスできれば、それを使用して MySQL サーバに与えられたユーザでログインすることができます。(十分 な権限があれば、同じユーザが別のものにパスワードを置き換えることもできます。 ) @end itemize 以下は MySQL の特権システムで行うものではありません： @itemize @bullet @item アクセスを拒否するユーザーを特定して設定することはできません。 完全に一致したユーザーからの接続を拒否できません。 @item データベース内のテーブルの作成、破棄の権限を持つが、 データベースそのものを作成、破棄できる、そのようなユーザーを設定できません。 @end itemize @node Connecting, Connection access, Privileges provided, Privilege system @subsection MySQL サーバーに接続 @cindex connecting, to the server @cindex default hostname @cindex hostname, default @cindex server, connecting MySQL クライアントプログラムは、共通の決まった引数を持ちます： 接続したいホスト名、接続ユーザー名、そしてパスワードです。 例えば、@code{mysql} コマンドは以下のような引数を持ちます (オプションの引数は @samp{[} と @samp{]} で囲まれている部分です) @example shell> mysql [-h host_name] [-u user_name] [-pyour_pass] @end example @code{-h}, @code{-u}, @code{-p} オプションは以下と等価です。 @code{--host=host_name}, @code{--user=user_name}, @code{--password=your_pass} @code{-p} とパスワードの間にはスペースがないことに注意 @strong{注意:} コマンドラインにパスワードを与えるのは安全ではありません！ システムに入っている如何なるユーザーも @code{ps auxww} のようなコマンドを 使用する事でパスワードを見付ける事ができます. @xref{Option files}. @code{mysql} コマンドはコマンドラインに引数がなければ接続にデフォルト値を用います。 @itemize @bullet @item デフォルトのホスト名は @code{localhost}. @item デフォルトのユーザー名は Unix のログイン名です。 @item @code{-p} が指定されていなければパスワードは与えられません @end itemize Unix のログインユーザーが @code{joe} の場合、以下のコマンドは等価です： @example shell> mysql -h localhost -u joe shell> mysql -h localhost shell> mysql -u joe shell> mysql @end example 他の MySQL クライアントも同じように動作します。 Unix システムでは、ある値をデフォルト値にして接続に使用することができます。 そうすることにより、毎回毎回コマンドラインに引数を与えなくてすむようになります： @itemize @bullet @item @tindex .my.cnf file 自分のホームディレクトリに @file{.my.cnf} を作り、そのファイルの中の @code{[client]} セクションに接続用のパラメターを記述できます。 その記述は以下のようになります： @example [client] host=host_name user=user_name password=your_pass @end example @xref{Option files}. @item @tindex @code{MYSQL_HOST} environment variable @tindex environment variable, @code{MYSQL_HOST} @tindex @code{MYSQL_PWD} environment variable @tindex environment variable, @code{MYSQL_PWD} @tindex @code{USER} environment variable @tindex environment variable, @code{USER} 接続のパラメターに環境変数を使用することもできます。 ホスト名は @code{MYSQL_HOST} 環境変数を使用します。 MySQL のユーザー名は @code{USER} (これは Windows のみ) に設定された値を使用します。 パスワードは @code{MYSQL_PWD} 環境変数を見ますが、これは危険です。(次の節参照) @xref{Environment variables}. @end itemize @node Connection access, Request access, Connecting, Privilege system @subsection Access Control, Stage 1: 接続の承認 @cindex access control @cindex control access @cindex connecting, verification @cindex testing, connection to the server MySQL サーバーに接続すると、あなたがパスワード認証して接続していようがいまいが、 サーバーはあなたの身元により接続の許可拒否を行います。 もし身元が一致しない場合接続を拒否し、接続許可した場合、 サーバーは Stage 2 へと進み、要求を待ちます。 身元は二つのものに基づいて確認されます： @itemize @bullet @item あなたが接続しようとしているホスト @item あなたの MySQL ユーザー名 @end itemize 身元の確認は @code{user} テーブルのスコープフィールド (@code{Host}, @code{User}, @code{Password}) を使用して行います。 サーバーは @code{user} テーブルの登録に一致しているホスト名と ユーザー名に限り接続を許可し、その後、パスワードを要求します。 @code{user} テーブルのスコープフィールドの登録は以下のようになります： @itemize @bullet @item @code{Host} の値はホスト名か IP アドレスか @code{'localhost'}(ローカルホスト) です。 @item @cindex wildcards, in @code{mysql.user} table @code{Host}、@code{Db} フィールドにはワイルドカード文字 @samp{%} と @samp{_} を使用できます。 If you wish to use for instance a @samp{_} character as part of a database name, specify it as @samp{\_} in the @code{GRANT} command. @item @code{Host} に @code{'%'} を設定すると、全てのホストにマッチします。 @item 空の @code{Host} 値は、権限が @code{host} テーブル内の与えられたホスト名に 適合するエントリと AND されることを意味します。次の章にこれについての詳し い情報を見つけられます。 @cindex netmask notation, in @code{mysql.user} table @item MySQL バージョン 3.23 では、IPアドレスが記述された @code{Host} 値には、何 ビットがネットワークアドレスに使用されるかを示すネットマスクを記述すること ができます。例えば: @example mysql> GRANT ALL PRIVILEGES ON db.* -> TO david@@'192.58.197.0/255.255.255.0'; @end example これは、次が真になる IP からの接続をすべて許可します: @example user_ip & netmask = host_ip. @end example 上記の例では、192.58.197.0〜192.58.197.255 のすべての IP が MySQL サーバに接続できます。 @item @cindex anonymous user ワイルドカード文字は @code{User} フィールドには設定できませんが、 @code{User} フィールドをブランク(空)にすることはできます。ブランクは全ての名前にマッチします。 これはユーザー名がない状態で接続してきたものに適用され、 クライアントがユーザー名を明記しない限り、匿名ユーザー(名前がブランク)として扱われます。 全てのアクセスのチェックにブランクのユーザー名が使用される事を意味します。 (that is, during Stage 2). @item @code{Password} フィールドは空にできます。 これは、いかなるパスワードにもマッチするという意味ではなくて、 パスワードなして接続できるということになります。 @end itemize @findex PASSWORD() 非ブランクの @code{Password} 値はパスワードを暗号化したものです。 MySQL はだれもが見れるようにパスワードを平文では保存しません。 接続を試みようとしているユーザーのパスワードも、(@code{PASSWORD()} 関数で) 暗号化されます。 それから、暗号化パスワードは、クライアント／サーバがパスワードが正しいかチェッ クする時に使用されます(This is done without the encrypted password ever traveling over the connection)。注意: MySQL では、暗号化パスワー ドが本当のパスワードです。そのため、それへのアクセスを誰にも与えるべきでは ありません！ 特に、一般ユーザには@code{mysql} データベース内のテーブルの読 み取り権を与えないでください！ From version 4.1, MySQL employs a different password and login mechanism that is secure even if TCP/IP packets are sniffed and/or the mysql database is captured. 以下の表は、接続要求に対して与える、 @code{user} テーブルの @code{Host} と @code{User} の設定例です： @multitable @columnfractions .35 .15 .50 @item @code{Host} @strong{value} @tab @code{User} @strong{value} @tab @strong{Connections matched by entry} @item @code{'thomas.loc.gov'} @tab @code{'fred'} @tab @code{fred}, @code{thomas.loc.gov} から接続 @item @code{'thomas.loc.gov'} @tab @code{''} @tab @code{thomas.loc.gov} から接続してくる全てのユーザー @item @code{'%'} @tab @code{'fred'} @tab @code{fred}, 全てのホストから接続 @item @code{'%'} @tab @code{''} @tab 全てのホストから接続してくる全ユーザー @item @code{'%.loc.gov'} @tab @code{'fred'} @tab @code{fred}, @code{loc.gov} ドメイン内の全てのホストからの接続 @item @code{'x.y.%'} @tab @code{'fred'} @tab @code{fred}, @code{x.y.net}, @code{x.y.com},@code{x.y.edu}, などからの接続. (あまり有効な使い方ではないです) @item @code{'144.155.166.177'} @tab @code{'fred'} @tab @code{fred}, IP address が @code{144.155.166.177} のホストからの接続 @item @code{'144.155.166.%'} @tab @code{'fred'} @tab @code{fred}, @code{144.155.166} class C subnet 内の全てのホストからの接続 @item @code{'144.155.166.0/255.255.255.0'} @tab @code{'fred'} @tab 上の例と同じ @end multitable @code{Host} に IP のワイルドカード(例えば @code{'144.155.166.%'} は サブネットの全てのホストにマッチ) を使用することができます。 が、この場合、 @code{144.155.166.somewhere.com} というホスト名で だれかが接続しようとしてくるかもしれません。 このような攻撃に対し、MySQL は数字やドットで始まるホスト名を拒否しています。 もし @code{1.2.foo.com} のような名前のホストを持っている場合、 許可テーブルの @code{Host} には絶対にマッチしません。 IPアドレスのみ、IP のワイルドカードにマッチする事になります。 サーバーに来る接続は、@code{user} テーブル内の登録に１つ以上 マッチするかもしれません。 例えば, @code{thomas.loc.gov} の @code{fred} からの接続は、上に示された 登録のうちのいくつかにマッチするでしょう。 サーバーは、複数の登録にマッチした場合、どのようにしてその中から 使用する登録を選ぶのでしょう？ サーバーは起動後に @code{user} テーブルをソートし、並び換えられた順に 登録を検索することにより、この問題を解決します。 最初にマッチした登録が使用されます。 @code{user} テーブルが以下のようにソートされていた場合： @example +-----------+----------+- | Host | User | ... +-----------+----------+- | % | root | ... | % | jeffrey | ... | localhost | root | ... | localhost | | ... +-----------+----------+- @end example サーバーがこのテーブルを読むと、@code{Host} に値が最も確実に特定できる ホストを指定しているエントリを、最初に参照します。 (@code{Host} 項の @code{'%'} は ``すべてのホスト'' を意味し、 ホスト名をはっきりと特定しているものではありません) @code{Host} の値が同じエントリがあった場合、もっとも明確に @code{User} の値が ユーザーを指定しているエントリを最初に参照します。 (@code{User} の値が空の場合、``だれでも'' を意味します) この結果、@code{user} テーブルは以下のようにソートされます： @example +-----------+----------+- | Host | User | ... +-----------+----------+- | localhost | root | ... | localhost | | ... | % | jeffrey | ... | % | root | ... +-----------+----------+- @end example @cindex grant tables, sorting @cindex sorting, grant tables @cindex @code{user} table, sorting 接続が試みられた場合、サーバーは並び換えられた登録を探し、最初に見つけたものを 使用します。 @code{'localhost'} の @code{jeffrey} からの接続は、まず最初に @code{Host} に @code{localhost} を設定しているエントリにマッチします。 ユーザー名が空のエントリは、ホスト名とユーザー名の両方を指定した接続にもマッチします。 ( @code{'%'/'jeffrey'} エントリもマッチします。が、これは最初にはマッチしません。) もう一例。@code{user} が以下の設定と仮定します： @example +----------------+----------+- | Host | User | ... +----------------+----------+- | % | jeffrey | ... | thomas.loc.gov | | ... +----------------+----------+- @end example これは次のようにソートされます： @example +----------------+----------+- | Host | User | ... +----------------+----------+- | thomas.loc.gov | | ... | % | jeffrey | ... +----------------+----------+- @end example @code{thomas.loc.gov} の @code{jeffrey} からの接続は、最初のエントリにマッチし、 @code{whitehouse.gov} の @code{jeffrey} からの接続は、二つ目のエントリにマッチします。 よくある考え違いは、ユーザー名を与えて接続した場合、 サーバーが接続にマッチするものを探す際に、 そのユーザー名が指定されているルールが 最初に使用されるだろうと考えることです。これは正しくありません。 前の例でこれを示しましたが、@code{thomas.loc.gov} の @code{jeffrey} からの接続が 最初にマッチするのは、 @code{User} フィールドの値が @code{'jeffrey'} に なっているエントリではなく、ユーザー名なし(＝だれでも) のエントリの方が 先にマッチします！ もしサーバーへの接続がうまく行かない場合、 @code{user} テーブルを表示し、 マニュアルでソートしてみて、どのエントリに最初にマッチするか探してください。 If connection was successful, but your privileges are not what you expected you may use @code{CURRENT_USER()} function (new in version 4.0.6) to see what user/host combination your connection actually matched. @xref{Miscellaneous functions, ,@code{CURRENT_USER()}}. @node Request access, Access denied, Connection access, Privilege system @subsection Access Control, Stage 2: Request Verification 一度接続か確立されると、サーバーはステージ２に移ります。 このステージでは、サーバーはこの接続から来るそれぞれの要求が許可されて いるかどうかをチェックします。 チェックは実行しようとしている操作のタイプにより行います。 その操作が許可テーブルのどの権限フィールドに当てはまるかを見ます。 これら権限は @code{user}, @code{db},@code{host}, @code{tables_priv} か @code{columns_priv} テーブルより導出されます。 権限テーブルは @code{GRANT}, @code{REVOKE} コマンドで操作します。 @xref{GRANT, , @code{GRANT}}. (You may find it helpful to refer to @ref{Privileges}, which lists the fields present in each of the grant tables.) @code{user} テーブルは全てに対して基本となる権限をユーザーに割り当てます。 たとえカレントのデータベースに許可を与えていなくても、@code{user} テーブルの設定方が有効になります。 例えば、@code{user} テーブルで @code{DELETE} を許可した場合、 サーバーにあるどんなデータベースの行も削除できるのです！ いうならば、@code{user} テーブルの権限はスーパーユーザーの権限と言ってもいいでしょう。 この権限はスーパーユーザー(サーバーやデーターベース管理者)のみに与えておく事が賢明です。 他のユーザーは、@code{user} テーブルの権限の設定を @code{'N'} のままにしておくべきですし、 また、@code{db} テーブルと @code{host} テーブルを利用して、 データベースを指定した上でユーザーに権限を許可すべきです。 @cindex anonymous user @cindex wildcards, in @code{mysql.db} table @cindex wildcards, in @code{mysql.host} table @code{db} テーブルと @code{host} テーブルは特定のデータベースに対する権限許可を行います。 スコープフィールドの値は次のように記述されます: @itemize @bullet @item ワイルドカード文字 @samp{%} と @samp{_} は @code{Db} テーブルと @code{Host} フィールドだけに使用できます。 @item @code{'%'} @code{Host} 値は ``あらゆるホスト'' を意味します。 @code{db} テーブルの @code{Host} に空を設定すると、``さらに @code{host} テーブルに許可情報を探しにいく'' となります。 @item @code{'%'} か 空値を @code{Host} テーブルに設定すると、それは ``あらゆるホスト'' となります。 @item @code{'%'} か 空値を @code{host} テーブルの @code{Db} フィールドに設定すると、 それは ``あらゆるデータベース'' となります。 @item @code{User} を空値にすると、匿名ユーザーにマッチします。 @end itemize @cindex grant tables, sorting @cindex sorting, grant tables @cindex @code{db} table, sorting @cindex @code{host} table, sorting サーバー起動時に、@code{db} テーブルと @code{host} テーブルはサーバーに読み込まれます。 (@code{user} テーブルもこの時に同時に読まれます) @code{db} テーブルは @code{Host}, @code{Db}, @code{User} のフィールドでソートされ、 @code{host} テーブルは @code{Host}, @code{Db} フィールドでソートされます。 @code{user} テーブルは、一番特定できるエントリを最初に、一番特定できないものを最後にソートします。 サーバーはソートされたものの中から、最初にマッチしたものを使用します。 @cindex wildcards, in @code{mysql.tables_priv} table @cindex wildcards, in @code{mysql.columns_priv} table @code{tables_priv} と @code{columns_priv} テーブルは、 特定のテーブルとフィールドに対する権限を許可します。 スコープフィールドの値は、いかにそって記述されます： @itemize @bullet @item ワイルドカード文字 @samp{%} と @samp{_} はどちらかのテーブルの @code{Host} フィールドに使用できます。 @item どちらかのテーブルの @code{Host} 値を @code{'%'} かブランクにすると、 ``any host.'' を意味します。 @item @code{Db}, @code{Table_name}, @code{Column_name} フィールドはどのテーブルにも ワイルドカードやブランクは使用できません。 @end itemize @code{tables_priv} と @code{columns_priv} テーブルは @code{Host}, @code{Db}, @code{User} フィールドで並び換えられます。 これは @code{db} テーブルのソートに似ていますが、 @code{Host} フィールドだけが ワイルドカードを含むので、ソートはより単純なものになります。 この要求の承認は次のようにして行います。 もしアクセス承認を決定する部分のソースコードを理解できるなら、 ちょっと変わったアルゴリズムで承認の決定を行っている事に気づくでしょう。 管理者の要求(@code{SHUTDOWN}, @code{RELOAD}, etc.)については、サーバーは @code{user} テーブルだけを参照します。(@code{user} テーブルだけが管理者権限のフィールドを持つ)。 エントリに許可登録されている操作は受け入れられ、それ以外は拒否されます。 例えば、@code{mysqladmin shutdown} を実行しようとしても、 @code{user} テーブルの @code{SHUTDOWN} 権限が許されていなければ実行できません。 この時、@code{db} と @code{host} テーブルはチェックされません。 (これらのテーブルには @code{Shutdown_priv} フィールドが無いからです) データベースへの要求 (@code{INSERT}, @code{UPDATE}, etc.) において、 サーバーはまず最初に、ユーザーのグローバルな権限(スーパーユーザー)を @code{user} の中から探しだします。 もし許可が与えられていれば、アクセスは成功します。 @code{user} テーブルのグローバルな権限の設定が不十分であるなら、 サーバーはユーザーのデータベースに対する権限を @code{db} テーブルと @code{host} テーブルから決定します： @enumerate @item サーバーは @code{db} テーブルの @code{Host},@code{Db},@code{User}フィールドを参照します。 @code{Host} と @code{User} フィールドはユーザーの接続時のホスト名と MySQL ユーザー名にマッチします。 @code{Db} フィールドはユーザーがアクセスしたいデータベース名にマッチします。 @code{Host} と @code{User} にマッチするものが無かった場合、アクセスは拒否されます。 @item @code{db} テーブル内の @code{Host} フィールドが空でないエントリにマッチした場合、 ユーザーの指定されているデータベースに対する権限が定義されます。 @item @code{Host} フィールドが空値の @code{db} テーブルのエントリにマッチした場合、 どのホストがそのデータベースへアクセスできるかを @code{host} テーブルから探し出します。 この場合、@code{host} テーブル の @code{Host}, @code{Db} フィールドとマッチするものを探し出します。 @code{host} テーブルにエントリがなかった場合、アクセスは拒否されます。 もしマッチすると、ユーザーの特定データベースに対する権限は、 @code{host} テーブルと @code{db} テーブル両方にまたがった権限から割り出されます。 いうならば両方とも @code{'Y'} である権限。 (この方法を使用すると、まず @code{db} テーブルのエントリに大まかな権限を設定しておき、 それから @code{host} テーブルのエントリを使用して、ホスト情報もとに権限を限定していくという事ができます) @end enumerate 特定データベースに対する権限が @code{db} テーブルと @code{host} テーブルのエントリから決定された後、 サーバーはその割り出された権限に対し、@code{user} テーブルて設定されている権限を加えます。 この結果から得られた権限にマッチした要求は受け入れられます。 そうでなければ、サーバーはユーザーのテーブル、フィールドに対する許可を、 @code{tables_priv} と @code{columns_priv} 内に探します。 アクセスはこの結果により、許可、拒否されます。 先のユーザーの権限が計算される方法の記述は、boolean 表記で示すならば、 以下のようになるでしょう： @example global privileges OR (database privileges AND host privileges) OR table privileges OR column privileges @end example これは少し分かりにくいかもしれません。もしグローバルの @code{user} エントリ 権限許可が、リクエストされたオペレーションには不十分だと最初に分かった際、 サーバーがこれらの権限を database-, table-, column-固有の権限の 後に、なぜ、追加してしまうのか。 その理由は、リクエストが1個以上の権限を要求するだろうということです。 例えば、もしあなたが @code{INSERT ... SELECT} 構文を実行するなら、 あなたには @code{INSERT} と @code{SELECT} 権限が必要です。 あなたの権限が、 @code{user} テーブルエントリで一つの権限が許可され、 @code{db} テーブルで、そのほかの権限が許可されていたとします。 この場合、あなたは、そのリクエストを実行するために、必要な権限を持っています。 しかし、サーバーはどちらのテーブル、それ単体からでは、権限を得ることが出来ません。 権限は、両方のエントリーを合わせなくてはならないのです。 @cindex @code{host} table @cindex tables, @code{host} @code{host} テーブルは ``安全な'' ホストのリストを維持するために使用できます。 TcX では、@code{host} テーブルにはローカルネット上の全てのホストが登録されています。 これらのホストは全ての権限が許可されています。 逆に @code{host} table で安全@emph{ではない}ホストを指定することもできます。 @code{public.your.domain} というマシンが安全ではない、公開されている場所にあるとします。 その場合以下のようにして、その公開マシン以外のネットワーク上のホストに対して、 アクセスを許可することができます： @example +--------------------+----+- | Host | Db | ... +--------------------+----+- | public.your.domain | % | ... (all privileges set to 'N') | %.your.domain | % | ... (all privileges set to 'Y') +--------------------+----+- @end example @cindex privilege, changes @cindex changes to privileges @cindex tables, grant @cindex grant tables 権限のテーブル設定は、あなたの思い通りに許可が得られるのか、 常に(@code{mysqlaccess}等を使用して)チェックすべきです。 @node Access denied, , Request access, Privilege system @subsection 何故 @code{Access denied} エラーになるのか もし、MySQL サーバーに接続しようとして @code{Access denied} エラーに 遭遇してしまったら、以下に記すことが問題の解決のための指標となるでしょう: @itemize @bullet @item MySQL をインストールした後に、スクリプト @code{mysql_install_db} を実行して 許可テーブルを初期化しましたか？ していなければ実行してください。@xref{Default privileges} 権限許可のテーブルが初期化されているかを試すには以下のようにします： @example shell> mysql -u root test @end example The server should let you connect without error. You should also make sure you have a file @file{user.MYD} in the MySQL database directory. Ordinarily, this is @file{PATH/var/mysql/user.MYD}, where @code{PATH} is the pathname to the MySQL installation root. @item After a fresh installation, you should connect to the server and set up your users and their access permissions: @example shell> mysql -u root mysql @end example 初期状態では、MySQL に @code{root} ユーザーをパスワードなしで登録しているので、 問題なく接続できるはずです。 しかしこれはセキュリティ上危険な状態なので、 他の MySQL ユーザーを登録している時に、 @code{root} のパスワードを設定しておいてください。 もし @code{root} で接続しようとして以下のエラーが出た場合： @example Access denied for user: '@@unknown' to database mysql @end example これは @code{user} テーブルに、 @code{User} フィールド = @code{root} かつ @code{mysqld} がリゾルブできなかったホスト名で、クライアントが登録されていないからです。 この場合、 @file{/etc/hosts} ファイルあるいは @file{\windows\hosts} ファイルを編集して ホスト名を追加し、@code{--skip-grant-tables} オプションでサーバーをリスタートします。 @item 次のようなエラーが出た場合: @example shell> mysqladmin -u root -pxxxx ver Access denied for user: 'root@@localhost' (Using password: YES) @end example これは間違ったパスワードを使用したことを意味します。 @xref{Passwords}. root のパスワードを忘れた場合、@code{mysqld} を @code{--skip-grant-tables} で再起動して、パスワードを変更することができま す。@xref{Resetting permissions}. パスワードを指定してないのに、上のエラーがでた場合は、@code{my.ini} ファイ ルに間違ったパスワードがあることを意味します。@xref{Option files}. このオ プションファイルは、次のように @code{--no-defaults} オプションで回避できま す: @example shell> mysqladmin --no-defaults -u root ver @end example @item @cindex @code{mysql_fix_privilege_tables} もしバージョン 3.22.11 より前の MySQL から バージョン 3.22.11 以上にバージョンアップしたなら、 @code{mysql_fix_privilege_tables} スクリプトを実行しましたか？ 実行していないなら、このエラーになります。 許可テーブルの構造が MySQL バージョン 3.22.11 から変更され、 @code{GRANT} 構文が機能しています。 @item もしあなたの権限がセッションの途中で変更されたように思ったなら、それは スーパーユーザーが権限を変えたのかも知れません。許可テーブルの再読み込みは 新しいクライアントの接続から反映されますが、すでに接続している場合でも @ref{Privilege changes}. に示す条件下では影響を受けます。 @item もしあなたのパスワードが働かないのであれば、 @code{INSERT}, @code{UPDATE}, @code{SET PASSWORD} 構文でパスワードを設定するとき @code{PASSWORD()} 関数を使用しなければならないことを思い出してください。 しかし @code{PASSWORD()} 関数は、@code{GRANT ... INDENTIFIED BY} 構文や @code{mysqladmin password} コマンドでは不要です。 @xref{Passwords}. @item @code{localhost} はローカルのホスト名です。 もしクライアントがホストを指定せずに接続してきた場合、@code{localhost} がデフォルトで使用されます。 しかし、 MIT-pthreads を使用している場合、@code{localhost} への接続は失敗します。 (@code{localhost} への接続は、Unixソケットを使用しますが、 MySQL 3.23.27 未満では MIT-pthreads が ソケット接続をサポートしていないためです。) この問題が起きるシステムでは、サーバー名を指定するために @code{--host} オプションを使用すべきです。 これは TCP/IP 接続を使用して @code{mysqld} サーバーに接続します。 この場合、@code{user} テーブルに、サーバーの実ホスト名を登録しておかなくてはなりません。 (これはクライアントプログラムをサーバーと同じホスト上で動かしている場合真となります) 例えば、@code{Using password: NO} を含むエラーメッセージを得た場合、これは パスワードなしでログインしようとしたことを意味します。 @item @code{mysql -u user_name db_name} を使用してデータベースに接続しているときに @code{Access denied} エラーが発生した場合、@code{user} テーブルの設定違いが考えられます。 @code{mysql -u root mysql} を実行し、以下の SQL 文を試してください： @example mysql> SELECT * FROM user; @end example @code{Host} と @code{User} にあなたのコンピュータ名と MySQL ユーザー名にマッチする登録がなされていなければなりません。 @item @code{Access denied} エラーは、どのユーザーで接続してきたか、 どのホストから接続しようとしているか、パスワードを使用しているのかをメッセージに出力します。 通常、エラーになっているホスト名とユーザー名がマッチするエントリが @code{user} テーブルに一つはなければなりません。 For example if you get an error message that contains @code{Using password: NO}, this means that you tried to login without an password. @item 他のホストから MySQL サーバーに接続を試みた時に以下のエラーが出た場合、 @code{user} テーブルにあなたがアクセスしているホストにマッチする行がありません： @example Host ... is not allowed to connect to this MySQL server @end example @code{mysql} コマンドをサーバーのホスト上で使用して、 @code{user}, @code{db}, @code{host} テーブルに接続しようとしている ユーザー名／ホスト名 を加えて、@code{mysqladmin flush-privileges} を 実行すれば解決できるでしょう。 もしサーバーが MySQL バージョン 3.22 ではなく、接続しようとしている ホストの IP もホスト名もわからない場合、 @code{user} テーブルの @code{Host} フィールドに @code{'%'} を設定し、 @code{mysqld} を @code{--log} オプションで再起動してください。 そしてクライアントホストから接続すれば、MySQL のログファイルに そのホストの情報が記録されているはずです。 それがわかれば、先に設定した @code{user} テーブルの @code{Host} フィールドの @code{'%'} を ログに記録されたホスト名に置き換えます。(しかしこれはシステムを危険にさらします) Linux 上でこのエラーの他の原因は、あなたの使用しているのと異なる glibc バー ジョンでコンパイルされた、バイナリ MySQL バージョンを使用している ことを意味します。この場合、あなたの OS/glibc をアップグレードするか、ソー ス MySQL バージョンをダウンロードしてコンパイルすべきです。ソース RPM は、通常コンパイルとインストールは簡単なので、これは大きな問題ではあり ません。 @item ホスト名で接続しようとしたのに、ホスト名が現れないか、ホスト名が IP でエラー メッセージが出る場合: @example shell> mysqladmin -u root -pxxxx -h some-hostname ver Access denied for user: 'root@@' (Using password: YES) @end example これは MySQL が IP をホスト名に解決しようとした時に何かエラーを得 たことを意味します。この場合、@code{mysqladmin flush-hosts} を実行して、内 部の DNS キャッシュをリセットできます。 @xref{DNS}. いくつかの永久的な解決策は: @itemize @minus @item DNS サーバで何が間違っているのかを見つけ出し、それを修正する。 @item MySQL 権限テーブル中に、ホスト名の代わりに IP を記述する。 @item @code{--skip-name-resolve} で @code{mysqld} を起動する。 @item @code{--skip-host-cache} で @code{mysqld} を起動する。 @item 同じマシン上でサーバとクライアントを起動している場合、@code{localhost} に 接続する。 @item @code{/etc/hosts} にクライアントマシン名を書く。 @end itemize @item @code{mysql -u root test} は動いたものの @code{mysql -h your_hostname -u root test} が @code{Access denied} を返した場合、 @code{user} テーブルに正しいホスト名が使用されていないと思われます。 @code{user} テーブルの @code{Host} フィールドにホスト名を確定できる形で指定していないか、 使用しているシステムのリゾルブが FQDN (or vice-versa) を返しているかだと思われます。 例えば、@code{user} テーブルに @code{'tcx'} ホストの定義があったとして、 DNS が MySQL に @code{'tcx.subnet.se'} をホスト名として返した場合、 これは動きません。 @code{user} テーブルの @code{Host} フィールドの値に、あなたのホストの IP 番号を加えてください。 (@code{user} テーブルの @code{Host} の値にワイルドカードを使用することができます。@code{'tcx.%'} のように。 しかしホスト名の値を @samp{%} 文字で終わらせる設定は、@strong{安全ではなく}、@strong{推奨されません}) @item もし @code{mysql -u user_name test} が動作し @code{mysql -u user_name other_db_name} が 動作しない場合は、@code{db} テーブルに @code{other_db_name} のエントリが 登録されていません。 @item @code{mysql -u user_name db_name} はサーバー上では動作するが、 @code{mysql -u host_name -u user_name db_name} がクライアントホスト上で動作しない場合、 @code{user} テーブルか @code{db} テーブルにクライアントホストの名前が登録されていません。 @item @code{Access denied} の原因がもし上記に当てはまらない場合は、 @code{user} テーブルから @code{Host} にワイルドカードを使用しているエントリを 全て消去してみてください。(@samp{%} や @samp{_} を含む値です) よくある間違いは、@code{localhost} に対して @code{localhost} と同じマシン上から の接続を許可すると考えて @code{Host}=@code{'%'} と @code{User}=@code{'some user'} を登録することです。 これは動きません。なぜなら、デフォルトの権限に @code{Host}=@code{'localhost'} と @code{User}=@code{''} が含まれているからです。 @code{Host} の値が @code{'localhost'} の場合、これは @code{'%'} よりも 具体的に指定されているので、@code{localhost} からの接続にはこちらの方が 使用されるのです！ 正しい指定の仕方は、二番目の登録として @code{Host}=@code{'localhost'} と @code{User}=@code{'some_user'} を追加するか、 あるいは、@code{Host}=@code{'localhost'} と @code{User}=@code{''} を削除することです。 @item もし以下のエラーが出た場合 @code{db} か @code{host} テーブルに問題があるのかもしれません。： @example Access to database denied @end example もし @code{db} テーブルに @code{Host} フィールドが空の登録がある場合には、 @code{host} テーブル中に、@code{db} テーブルに登録されている ホストを明記した物が一つ以上あるかどうかを確認してください。 もし @code{SELECT ... INTO OUTFILE} や @code{LOAD DATA INFILE} SQL 文を 使用している時にこのエラーが出る場合、 @code{user} テーブルのあなたの登録に @code{FILE} 権限が 許可されていないと思われます。 @item @cindex configuration files @cindex environment variables @tindex .my.cnf file クライアントプログラムは接続に際して、 設定ファイルで設定された値か環境変数の値を使用することに注意してください。 もしクライアントプログラムが誤った値を接続に使用しているようなら、 環境変数とホームディレクトリにある @file{.my.cnf} ファイルを確認してください。 もちろんシステムワイドの MySQL 設定ファイルも、パラメターが記述されていないか、 チェックしてみてください。@xref{Option files}. もしクライアントをオプションなしで起動していて @code{Access denied} がでるなら、 オプションファイルに古いパスワードが書かれているか確認してください。 @xref{Option files}. @item 権限テーブルを(@code{INSERT} または @code{UPDATE} ステートメントを使用して )直接変更する場合、あなたの変更は無視されたように見えます。サーバに権限テー ブルを再読み込みさせるために、@code{FLUSH PRIVILEGES} ステートメントの発行 か、@code{mysqladmin flush-privileges} コマンドの実行の必要があることを忘 れないでください。そうでないと、あなたの変更は次回のサーバ再起動まで効果が ありません。@code{UPDATE} コマンドで @code{root} パスワードを設定後、権限 をフラッシュするまでそれを指定する必要がありません。サーバはまだパスワード を変更したことを知らないからです！ @item Perl, PHP, Python, ODBC プログラムでアクセスの問題があった場合、 @code{mysql -u user_name db_name} または @code{mysql -u user_name -pyour_pass db_name} でサーバへの接続を試してください。@code{mysql} クライ アントを使用して接続できれば、アクセス権でなく、あなたのプログラムに問題が あります。(@code{-p} とパスワードの間に空白がないことに注意してください; パスワードを指定するのに、@code{--password=your_pass} 構文も使用できます。 単に @code{-p} オプションを使用すると、MySQL はパスワードの入力を 求めます。) @item テストのために、@code{mysqld} デーモンを @code{--skip-grant-tables} オプショ ン付きで開始してください。MySQL 権限テーブルを変更し、あなたの変 更が望む効果があるかどうかのチェックに、@code{mysqlaccess} スクリプトを使 用できます。あなたの変更が満足できた時に、@code{mysqladmin flush-privileges} を実行し、@code{mysqld} サーバに新しい権限テーブルを使用 して開始するように伝えてください。@strong{注意:} 権限テーブルのリロードは @code{--skip-grant-tables} オプションを上書きします。これは、サーバを落と して再起動することなしに、権限テーブルの使用を始めるようにサーバに伝えるこ とができます。 @item もし全て失敗するなら、@code{mysqld} デーモンをデバッグオプションで起動してください。 例えば、@code{--debug=d,general,query}。これはコネクションに試みたホストやユーザーの情報、 また実行したコマンドを表示します。 @xref{Making trace files}. @item もし MySQL の権限許可についてその他の問題が起こり、 メーリング・リストに問題をポストしなくてはいけないと感じれば、 いつも MySQL 許可テーブルのダンプを提供して下さい。 @code{mysqldump mysql} コマンドでダンプできます。 いつものように、 @code{mysqlbug} スクリプトでポストしてください。@xref{Bug reports}. ときには、 @code{mysqldump} を実行するために、 @code{mysqld} を @code{--skip-grant-tables} オプションで実行しないと いけないかもしれません。 @end itemize @node User Account Management, Disaster Prevention, Privilege system, MySQL Database Administration @section MySQL User Account Management @c FIX: add section intro @menu * GRANT:: @code{GRANT} and @code{REVOKE} Syntax * User names:: MySQL User Names and Passwords * Privilege changes:: When Privilege Changes Take Effect * Default privileges:: Setting Up the Initial MySQL Privileges * Adding users:: Adding New Users to MySQL * User resources:: Limiting user resources * Passwords:: Setting Up Passwords * Password security:: Keeping Your Password Secure * Secure connections:: Using Secure Connections @end menu @node GRANT, User names, User Account Management, User Account Management @subsection @code{GRANT} と @code{REVOKE} 構文 @findex GRANT @findex REVOKE @cindex privileges, granting @cindex privileges, revoking @cindex global privileges @cindex revoking, privleges @cindex granting, privleges @example GRANT priv_type [(column_list)] [, priv_type [(column_list)] ...] ON @{tbl_name | * | *.* | db_name.*@} TO user_name [IDENTIFIED BY [PASSWORD] 'password'] [, user_name [IDENTIFIED BY 'password'] ...] [REQUIRE NONE | [@{SSL| X509@}] [CIPHER cipher [AND]] [ISSUER issuer [AND]] [SUBJECT subject]] [WITH [GRANT OPTION | MAX_QUERIES_PER_HOUR # | MAX_UPDATES_PER_HOUR # | MAX_CONNECTIONS_PER_HOUR #]] REVOKE priv_type [(column_list)] [, priv_type [(column_list)] ...] ON @{tbl_name | * | *.* | db_name.*@} FROM user_name [, user_name ...] バージョン 4.0 以上: REQUIRE [@{SSL| X509@}] [CIPHER cipher [AND]] [ISSUER issuer [AND]] [SUBJECT subject] バージョン 4.0.2以上: MAX_QUERIES_PER_HOUR=# | MAX_UPDATES_PER_HOUR=# | MAX_CONNECTIONS_PER_HOUR=# @end example @code{GRANT} は MySQL 3.22.11 以上で実装されています; 前の MySQL バージョンでは、@code{GRANT} ステートメントは何も行ないません。 @code{GRANT} と @code{REVOKE} コマンドセットの主な目的は、システム管理者 がユーザを生成すること、MySQL ユーザに次の４つの権限レベルの権 利を与えたり取り消すことをできるようにすることです: @table @strong @item Global レベル Global 権限は与えられたサーバ上の全てのデータベースに適用します。これらの権限は @code{mysql.user} テーブル内に格納されます。 @item Database レベル Database 権限は与えられたデータベース内の全てのテーブルに適用します。こ れらの権限は @code{mysql.db} テーブルと @code{mysql.host} テーブル内に格納されます。 @item Table レベル Table 権限は与えられたテーブル内の全てのフィールドに適用します。これらの権限は @code{mysql.tables_priv} テーブル内に格納されます。 @item Column レベル Column 権限は与えられたテーブル内の一つのフィールドに適用します。これらの権限は @code{mysql.columns_priv} テーブル内に格納されます。 @end table If you give a grant for a users that doesn't exists, that user is created. For examples of how @code{GRANT} works, see @ref{Adding users}. @code{GRANT} と @code{REVOKE} ステートメントにおいて @code{priv_type} には 以下が指定できます: @c FIX agl 2002-06-13 New table, need to measure colwidths! @multitable @columnfractions .30 .70 @item @code{ALL [PRIVILEGES]} @tab Sets all simple privileges except @code{WITH GRANT OPTION} @item @code{ALTER} @tab Allows usage of @code{ALTER TABLE} @item @code{CREATE} @tab Allows usage of @code{CREATE TABLE} @item @code{CREATE TEMPORARY TABLES} @tab Allows usage of @code{CREATE TEMPORARY TABLE} @item @code{DELETE} @tab Allows usage of @code{DELETE} @item @code{DROP} @tab Allows usage of @code{DROP TABLE}. @item @code{EXECUTE} @tab Allows the user to run stored procedures (for MySQL 5.0) @item @code{FILE} @tab Allows usage of @code{SELECT ... INTO OUTFILE} and @code{LOAD DATA INFILE}. @item @code{INDEX} @tab Allows usage of @code{CREATE INDEX} and @code{DROP INDEX} @item @code{INSERT} @tab Allows usage of @code{INSERT} @item @code{LOCK TABLES} @tab Allows usage of @code{LOCK TABLES} on tables for which one has the @code{SELECT} privilege. @item @code{PROCESS} @tab Allows usage of @code{SHOW FULL PROCESSLIST} @item @code{REFERENCES} @tab For the future @item @code{RELOAD} @tab Allows usage of @code{FLUSH} @item @code{REPLICATION CLIENT} @tab Gives the right to the user to ask where the slaves/masters are. @item @code{REPLICATION SLAVE} @tab Needed for the replication slaves (to read binlogs from master). @item @code{SELECT} @tab Allows usage of @code{SELECT} @item @code{SHOW DATABASES} @tab @code{SHOW DATABASES} shows all databases. @item @code{SHUTDOWN} @tab Allows usage of @code{mysqladmin shutdown} @item @code{SUPER} @tab Allows one connect (once) even if max_connections is reached and execute commands @code{CHANGE MASTER}, @code{KILL thread}, @code{mysqladmin debug}, @code{PURGE MASTER LOGS} and @code{SET GLOBAL} @item @code{UPDATE} @tab Allows usage of @code{UPDATE} @item @code{USAGE} @tab Synonym for ``no privileges.'' @item @code{GRANT OPTION} @tab Synonym for @code{WITH GRANT OPTION} @end multitable @code{USAGE} は ``no privileges'' と同義です. これはなんの権限も持たないユーザーを作る場合に使用します. The privileges @code{CREATE TEMPORARY TABLES}, @code{EXECUTE}, @code{LOCK TABLES}, @code{REPLICATION ...}, @code{SHOW DATABASES} and @code{SUPER} are new for in version 4.0.2. To use these new privileges after upgrading to 4.0.2, you have to run the @code{mysql_fix_privilege_tables} script. In older MySQL versions(4.0.2未満), the @code{PROCESS} privilege gives the same rights as the new @code{SUPER} privilege. ユーザーから @code{GRANT} 権限を取り除くには、@code{GRANT OPTION} オプションの値に @code{priv_type} を指定します： @example mysql> REVOKE GRANT OPTION ON ... FROM ...; @end example テーブルに対する許可のために指定できる @code{priv_type} は次のフィールドだけです： @code{SELECT},@code{INSERT}, @code{UPDATE}, @code{DELETE}, @code{CREATE}, @code{DROP}, @code{GRANT OPTION}, @code{INDEX}, @code{ALTER}. フィールドに対する許可のために指定できる @code{priv_type} は次のフィールドだけです (これは @code{column_list} 節を使用する場合に適用されます)： @code{SELECT}, @code{INSERT}, @code{UPDATE}. @code{ON *.*} を使用してグローバル権限を設定できます。 @code{ON db_name.*} を使用してデータベース権限を設定できます。@code{ON *} を 指定すると、現在のデータベースの権限を設定できます。 (@strong{警告：} 現在のデータベースを持たない状態で @code{ON *} を指定した場合、 global 権限に影響します！) @strong{Please note}: the @samp{_} and @samp{%} wildcards are allowed when specifying database names in @code{GRANT} commands. This means that if you wish to use for instance a @samp{_} character as part of a database name, you should specify it as @samp{\_} in the @code{GRANT} command, to prevent the user from being able to access additional databases matching the wildcard pattern, e.g., @code{GRANT ... ON `foo\_bar`.* TO ...}. ユーザへの権利の供与を他のホストから適応するために、MySQL は @code{user_name} の値を @code{user@@host} の形で書けるようにしています。 特殊文字(@samp{%} のような)で @code{user_name} の値を指定したい場合、 ユーザやホスト名をクォートできます; (例えば @code{'test-user'@@'test-hostname'})。 ホスト名にワイルドカードを使用できます。例えば、@code{user@@'%.loc.gov'} は @code{loc.gov} ドメインの全てのホストの @code{user} を与え、 @code{user@@'144.155.166.%'} は @code{144.155.166} クラスCサブネットの あらゆるホストの @code{user} となります。 単に @code{user} と書くと @code{user@@"%"} と同じです. MySQL doesn't support wildcards in user names. Anonymous users are defined by inserting entries with @code{User=''} into the @code{mysql.user} table or creating an user with an empty name with the @code{GRANT} command. @strong{注意：} もし匿名ユーザーからの MySQL サーバーへの接続を 許す場合(デフォルトです)、全てのローカルユーザー @code{username@@localhost} を加えるべきです。 なぜなら、匿名ユーザーは同じマシンから MySQL サーバーに入ろうとした場合に 使用されるからです！ (匿名ユーザーは @code{mysql.user} ユーザーテーブルに、 @code{User=''} として登録されています。) これを確認するには、以下のようにします： @example mysql> SELECT Host,User FROM mysql.user WHERE User=''; @end example さしあたり, @code{GRANT} はホスト名、テーブル名、データベース名、フィールド名に 最大60文字まで使用できます。ユーザー名は最大16文字までです。 テーブル/フィールドの権限は global(ユーザとデータベース)権限と @code{GRANT} 権限と @code{OR} されます。例えば、ユーザが @code{mysql.user} テーブル内の global @code{SELECT} 権限を持っている場合、 これはデータベースやテーブル/フィールドレベル内のエントリでは拒否できません。 フィールドに対する権限は次のように計算できます: @example global privileges OR (database privileges AND host privileges) OR table privileges OR column privileges @end example 多くの場合、異なる権限レベルの一つでユーザに権利を与えるので、人生は通常 上述のようには複雑ではありません。 アクセス権限のチェックの詳細は→@ref{Privilege system}. ユーザとホスト名の組が存在しない場合、エントリは @code{mysql.user} テー ブルに追加され、@code{DELETE} コマンドで削除されるまでそこに残ります。 いうならば @code{GRANT} は @code{user} テーブルの登録を作りますが、 @code{REVOKE} はそれらを削除できません; そうするには @code{DELETE} を使用しなくてはなりません。 @cindex passwords, setting MySQL バージョン 3.22.12 以上では、 新しいユーザーが作成された場合、あるいは、あなたがグローバルな権限を許可されている場合、 ユーザーのパスワードは @code{IDENTIFIED BY} 節を使用して設定できます。 すでにユーザーにパスワードがある場合、新しく設定されたパスワードに置き換えられます。 If you don't want to send the password in clear text you can use the @code{PASSWORD} option followed by a scrambled password from SQL function @code{PASSWORD()} or the C API function @code{make_scrambled_password(char *to, const char *password)}. @strong{警告：} もし新しいユーザーを作っても @code{IDENTIFIED BY} 節を指定しなければ、 そのユーザーはノーパスワードです。 これは危険です。 パスワードは @code{SET PASSWORD} コマンドでも設定できます。 @xref{SET OPTION, , @code{SET}}. データベースに権限を付与 する場合、@code{mysql.db} テーブル内の エントリは必要な場合に生成されます。全てのデータベース権限が @code{REVOKE} で削除された時、このエントリは削除されます。 ユーザがテーブルに何も権限を持っていない場合、テーブルの一覧要求時(例え ば、@code{SHOW TABLES} ステートメントで)には、テーブルは現れません。 @code{WITH GRANT OPTION} 節は、他のユーザーに、自分が持っている権限を与えることができます。 @code{GRANT} 権限を他に与える場合は注意してください。 あなたと許可を与えるユーザーが違う権限を持っている場合、 与えられる権限の許可は、二つを合わせた物になります！ @code{MAX_QUERIES_PER_HOUR #}, @code{MAX_UPDATES_PER_HOUR #} and @code{MAX_CONNECTIONS_PER_HOUR #} are new in MySQL version 4.0.2. These options limit the number of queries/updates and logins the user can do during one hour. If @code{#} is 0 (default), then this means that there are no limitations for that user. @xref{User resources}. Note: to specify any of these options for an existing user without adding other additional privileges, use @code{GRANT USAGE ... WITH MAX_...}. 自分自身が持っていない権限を他のユーザーに与えることはできません； @code{GRANT} 権限はあなたが所有する権限の許可だけを与えることができます。 Be aware that when you grant a user the @code{GRANT} privilege at a particular privilege level, any privileges the user already possesses (or is given in the future!) at that level are also grantable by that user. あなたがデータベースに対する @code{INSERT} 許可をあるユーザーに与えたと仮定します。 もし、データベースに対する @code{SELECT} 権限を与えたり、 @code{WITH GRANT OPTION} を行うと、ユーザーは @code{SELECT} 権限だけでなく @code{INSERT} も得ることになります。 もし @code{UPDATE} 権限をユーザーに与えると、そのユーザーは @code{INSERT}, @code{SELECT}, @code{UPDATE} が可能です。 @code{ALTER} 権限を一般ユーザに与えるべきではありません。この場合 ユーザはテーブルをリネームでき、この方法で権限を回ることを試みることがで きます！ 注意：もし table/column 権限を一人のユーザーにだけ与えた場合、 MySQL は全てのユーザーに対してテーブルとフィールドの承認権限を検討します。 これは MySQL を少し遅くします。 @code{mysqld} 開始時、全ての権限はメモリに読み込まれます。データベース、 テーブル、フィールド権限は一度効果を得ます。ユーザレベル権限はユーザ再接続時に 効果を得ます。 これらの許可テーブルを @code{GRANT} や @code{REVOKE} を使って変更しても サーバーにはすぐに反映されません。 もしこれらの許可テーブルを手動で変更した場合(@code{INSERT}, @code{UPDATE}, 等で変更した場合)、 @code{FLUSH PRIVILEGES} 構文を実行するか、@code{mysqladmin flush-privileges} を実行して サーバーに許可テーブルの再読み込みを行わせなくてはなりません。 @xref{Privilege changes}. @cindex ANSI SQL, differences from The biggest differences between the ANSI SQL and MySQL versions of @code{GRANT} are: @itemize @bullet @item In MySQL privileges are given for an username + hostname combination and not only for an username. @item ANSI SQL はグローバルとデータベースレベル承認を持たず、ANSI SQL は MySQL がサポートする全ての権限をサポートしません。 MySQL doesn't support the ANSI SQL @code{TRIGGER} or @code{UNDER} privileges. @item ANSI SQL privileges are structured in a hierarchal manner. If you remove an user, all privileges the user has granted are revoked. In MySQL the granted privileges are not automatically revoked, but you have to revoke these yourself if needed. @item In MySQL, if you have the @code{INSERT} privilege on only some of the columns in a table, you can execute @code{INSERT} statements on the table; the columns for which you don't have the @code{INSERT} privilege will be set to their default values. ANSI SQL requires you to have the @code{INSERT} privilege on all columns. @item ANSI SQL でテーブルを破棄する時、そのテーブルの全ての権限は破棄さ れます。@code{ANSI SQL} で権限を取り消す場合、この権限に基づいて承認され た全ての権限も取り消されます。@code{MySQL} では、全ての権限は明示的な @code{REVOKE} コマンドまたは MySQL 権限テーブルの操作によっての み破棄されます。 @end itemize For a description of using @code{REQUIRE}, see @ref{Secure connections}. @node User names, Privilege changes, GRANT, User Account Management @subsection MySQL ユーザ名とパスワード @cindex user names, and passwords @cindex passwords, for users MySQL によって使用されるユーザー名とパスワードの使用のされ方と、 Unix, Windows で使用される方法とは、いくつか異なる点があります。 @itemize @bullet @item MySQL データベースのアクセス認証に使用するユーザー名は、 Unix のログインユーザやWindowsのユーザー名で行うことはありません(一致していません)。 利便性をはかるため、多くの MySQL クライアントは現在のログインしているユーザ名を MySQLのユーザー名としてログインを試みます。 しかしこれは @code{-u} か @code{--user} スイッチで変更できます。 これは、全てのユーザに対しパスワードを設定しておかないと、 全くデータベースを安全にできないことを意味します。 もしパスワードを全ユーザーに設定しておかないと、そのユーザー名で認証なしにサーバーに接続できます。 @item MySQL のユーザー名は 16文字まで(英数半角)使用できます。 Unixはだいたい8文字ですが。(8文字をこえるシステムもある) @item MySQL ユーザーのパスワードは、Unix のパスワードと違います。 よって、それらのマシン上で Unix のログインパスワードと データベースのパスワードは同じにする必要はありません。 @item MySQL は Unix のログインパスワードとは全く違う、 独自の暗号化されたパスワードだけを使用します。 @code{PASSWORD()} と @code{ENCRYPT()} 関数の説明を参照 → @ref{Miscellaneous functions}. 注意: パスワードが '暗号化' されて格納されていても、あなたの '暗号化' され たパスワードを知ることで、MySQL サーバに接続するのには十分です！ From version 4.1, MySQL employs a different password and login mechanism that is secure even if TCP/IP packets are sniffed and/or the mysql database is captured. @end itemize MySQL ユーザーと彼らの権限は通常 @code{GRANT} コマンドで作成されます。 @xref{GRANT}. MySQL サーバにコマンドラインクライアントでログインする時、 @code{--password=your-password} でパスワードを指定すべきです。 @xref{Connecting}. @example mysql --user=monty --password=guess database_name @end example クライアントにパスワードをプロンプトして欲しければ、引数なしで @code{--password} を使用すべきです。 @example mysql --user=monty --password database_name @end example または次の短い形式: @example mysql -u monty -p database_name @end example 注意: 最後の例でのパスワードは 'database_name' では @strong{ありません}。 パスワードを供給するために @code{-p} オプションを使用したい場合、次のようなことを 行なうべきです: @example mysql -u monty -pguess database_name @end example いくつかのシステムでは、MySQL がパスワードをプロンプトするために 使用するライブラリ呼び出しは、自動的にパスワードを 8文字にカットします。内 部的に MySQL はパスワード長に何の制限もありません。 @node Privilege changes, Default privileges, User names, User Account Management @subsection いつ権限の変更が反映されるか @code{mysqld} の起動時、全ての許可テーブルはメモリーに読み込まれ、 この時点で有効になります。 @code{GRANT}, @code{REVOKE}, @code{SET PASSWORD} を使用して許可テーブルを 変更した場合、直にサーバに通知されます。 もし手動で許可テーブルを変更した場合(@code{INSERT}, @code{UPDATE} などで)、 @code{FLUSH PRIVILEGES} 構文か @code{mysqladmin flush-privileges} コマンド か @code{mysqladmin reload} コマンドを実行して、 サーバーに許可テーブルの読み込みを指示しなければなりません。 そうしなければ、サーバーを再起動させるまで、変更は@emph{反映されません}。 権限テーブルを手で変更して、権限のリロードを忘れた場合、変更が何も行なわれ ないように見えるのがなぜかと不思議に思うでしょう！ サーバーが許可テーブルの変更を通知した場合、既に接続している クライアントは、以下のような影響を受けます： @itemize @bullet @item テーブルとフィールドの許可の変更は、次のクライアントの要求から反映されます。 @item データベースに対する許可の変更は次の @code{USE db_name} コマンド以降から 有効になります。 @item グローバル権限とパスワードの変更は、次のクライアントの接続時から反映されます。 @end itemize @node Default privileges, Adding users, Privilege changes, User Account Management @subsection MySQL 権限許可の初期設定 @cindex privileges, default @cindex default, privileges @cindex root password @cindex superuser @cindex users, root @cindex anonymous user @cindex password, root user MySQL インストール後、@code{scripts/mysql_install_db} を 実行して権限のアクセス許可を初期化します。 @xref{Quick install}. @code{mysql_install_db} スクリプトは @code{mysqld} サーバーを起動し、 以下のように権限を初期化してテーブルに登録します： @itemize @bullet @item MySQL @code{root} ユーザーはスーパーユーザーとして登録され、 全ての操作ができます。 localhostからしか接続できません。 @strong{注意:} @code{root} のパスワードの初期値は空です。 全ての人が @emph{パスワードなしで} @code{root} になれ、全ての権限許可を得ることができます。 @item @cindex anonymous user @code{'test'} あるいは @code{'test_'} で名前がはじまっているデータベースに対して、 匿名ユーザーでもなんでもできるように許可が与えられます。 これは ローカルホストからの全てのユーザーは パスワード無しで接続ができ、 匿名ユーザーとして扱われるということです。 @item その他の要求は拒否されます。例えば、一般ユーザーは @code{mysqladmin shutdown} や @code{mysqladmin processlist} を実行できません。 @end itemize @strong{注意:} デフォルトの権限は Windows では違います。 @xref{Windows running}. 初期インストールの状態ではかなりアクセスが解放されているので、 インストール後最初にすることは、MySQL @code{root} ユーザーにパスワードを設定することです。 以下のようにします(パスワードは @code{PASSWORD()} 関数を使用することをお忘れなく)： @example shell> mysql -u root mysql mysql> SET PASSWORD FOR root@@localhost=PASSWORD('new_password'); @end example If you know what you are doing, you can also directly manipulate the privilege tables: @example shell> mysql -u root mysql mysql> UPDATE user SET Password=PASSWORD('new_password') -> WHERE user='root'; mysql> FLUSH PRIVILEGES; @end example password をセットする他の方法として、@code{mysqladmin} コマンドも使用できます： @example shell> mysqladmin -u root password new_password @end example @code{mysql} データベースに書き込み／更新アクセスのあるユーザだけが他のユーザのパ スワードを変更できます。すべての通常のユーザ(匿名ユーザ以外)は、上記のコマ ンドか、または @code{SET PASSWORD=PASSWORD('new password')} で、自分のパス ワードだけを変更できます。 もし最初の方法で @code{user} テーブルのパスワードを直接更新したなら、 サーバーに許可テーブルの再読み込みを行わせなければなりません(@code{FLUSH PRIVILEGES} を使用して)。 一度 @code{root} のパスワードを設定したなら、@code{root} でサーバーに接続する場合は 常にパスワードを与えなければなりません。 追加設定やテストをしているためパスワードを入れたくない場合、 @code{root} パスワードをブランクのままにしておこうと考えるかも知れませんが、 実稼働させる前には必ず設定してください。 どのようにデフォルトの権限を設定しているか、@code{scripts/mysql_install_db} 見てみてください。 これは他のユーザーを設定するときに使えるでしょう。 もし権限の初期状態を違うものにして初期化したいなら、 @code{mysql_install_db} を実行する前に編集してもよいでしょう。 @cindex grant tables, re-creating @cindex re-creating, grant tables もしテーブルを完全に作り直したいなら、@code{mysql} データベースのディレクトリに存在する 全ての @file{*.frm}, @file{*.MYI}, @file{*.MYD} ファイルを削除します。 (このディレクトリーはデータベースディレクトリーの下に @code{mysql} という名前で存在します。 @code{mysqld --help} とすればデータベースのディレクトリーが表示されます。) そして好みの許可状態に @code{mysql_install_db} を編集してから実行します。 @strong{注意:} MySQL 3.22.10 以前のバージョンでは, @file{*.frm} ファイルを消してはいけません. もしうっかり消してしまった場合、 @code{mysql_install_db} を実行する前に、 MySQL 配布からコピーしなおさ なくてはなりません。 @node Adding users, User resources, Default privileges, User Account Management @subsection 新しいユーザを MySQL へ追加 @findex GRANT statement @findex statements, GRANT @cindex privileges, adding @cindex adding, new user privileges @cindex user privileges, adding ユーザーは２つの違った方法で追加できます： @code{GRANT} 構文を使用して行う方法と、 MySQL の許可テーブルを直接操作する方法とです。 The preferred method is to use @code{GRANT} statements, because they are more concise and less error-prone. @xref{GRANT}. @code{phpmyadmin} のような、ユーザの作成と管理に使用できる contribute され たプログラムも多くあります。 以下の例では、いかにして @code{mysql} クライアントを使用して新規にユーザーを登録するかを示します。 以下の例では、権限は前節で述べたデフォルト値になっているとします。 よって変更を行うためには、あなたは @code{mysqld} が走っているマシン上にログインしていなくてはなりませんし、 かつ、MySQL @code{root} ユーザーで接続していなければなりません。 さらに MySQL @code{root} ユーザーには @code{mysql} データベースに対して @code{INSERT} 権限を持ち、 @code{RELOAD}, @code{PROCESS} のアドミニストレーター権限を持っていなければなりません。 もし @code{root} ユーザーのパスワードを変えていたならば、 @code{mysql} コマンドにパスワード指定を与えなくてはなりません。 You can add new users by issuing @code{GRANT} statements: @example shell> mysql --user=root mysql mysql> GRANT ALL PRIVILEGES ON *.* TO monty@@localhost -> IDENTIFIED BY 'some_pass' WITH GRANT OPTION; mysql> GRANT ALL PRIVILEGES ON *.* TO monty@@"%" -> IDENTIFIED BY 'some_pass' WITH GRANT OPTION; mysql> GRANT RELOAD,PROCESS ON *.* TO admin@@localhost; mysql> GRANT USAGE ON *.* TO dummy@@localhost; @end example これら @code{GRANT} 構文では3つの新しいユーザを作ります: @table @code @item monty どこからでもサーバーに接続できる完全なスーパーユーザ。 しかし、MySQL を使用する時にはパスワード @code{'some_pass'} を 使用する必要があります。 @code{monty@@localhost} と @code{monty@@"%"} の両方に @code{GRANT} 構文を 発行しなくてはならない事に注意してください。 もし @code{localhost} からの許可をした登録がないと、@code{localhost} から接続した時、 @code{mysql_install_db} が自動で作成した @code{localhost} への匿名ユーザーが優先されます。 なぜなら、 @code{Host} フィールドの値が(ブランクやワールドカード以外に)明記されており、 許可登録が MySQL 内部でソートされる時に順番が上にソートされるからです。 @item admin @code{localhost} からパスワードなしで接続できますが、@code{reload}, @code{process} の使用だけが許されます。 これは、@code{mysqladmin reload}, @code{mysqladmin refresh}, @code{mysqladmin flush-*} そして @code{mysqladmin processlist} コマンドの実行がこのユーザーに許可されます。 データベースへのアクセスは許可されていません。 しかしこれは後でテーブル @code{GRANT} 構文を発行すれば、 個々のデータベースへのアクセス権限が設定できます。 @item dummy パスワードなしで localhost からのみ、接続できるユーザー。 グローバルな権限は全て @code{'N'} に設定されます。 @code{USAGE} 権限は権限無しユーザーの設定を許可する事になります。 これは、特定データーベースに対しての許可を後から与える事を想定しています。 @end table @findex INSERT statement, grant privileges @findex statements, INSERT 同じアクセス許可を @code{INSERT} 構文を使用して直接設定できます。 サーバーに許可テーブルの再読み込みを指示します： @example shell> mysql --user=root mysql mysql> INSERT INTO user VALUES('localhost','monty',PASSWORD('some_pass'), -> 'Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y'); mysql> INSERT INTO user VALUES('%','monty',PASSWORD('some_pass'), -> 'Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y'); mysql> INSERT INTO user SET Host='localhost',User='admin', -> Reload_priv='Y', Process_priv='Y'; mysql> INSERT INTO user (Host,User,Password) -> VALUES('localhost','dummy',''); mysql> FLUSH PRIVILEGES; @end example MySQL のバージョンにより、上の @code{'Y'} の数が違う事に注意してください。 (3.22.11 以前のバージョンでは項目数が少なくなります). @code{admin} ユーザーの登録で使用している @code{INSERT} の拡張は バージョン 3.22.11 以上で可能です。 (訳注: version 4.0 以上で openssl を使用する場合、この数が変わります) スーパーユーザーを定義するためには、@code{user} テーブルの許可フィールドを @code{'Y'} にするだけでかまいません。 @code{db} や @code{host} テーブルに登録は必要無いのです。 @code{user} テーブルの許可フィールドは最後の @code{INSERT} 文で(@code{dummy} ユーザーのために) は設定されていません。これらのフィールドはデフォルト値の @code{'N'} になります。 これは @code{GRANT USAGE} が行うのと同じものです。 以下は、@code{localhost}, @code{server.domain}, @code{whitehouse.gov} から接続が可能な @code{custom} ユーザーの追加例です。 @code{custom} ユーザーは @code{bankaccount} データーベースには @code{localhost} からの接続のみを許可され、 @code{expenses} データベースには @code{whitehouse.gov} からのみ接続が許可され、 @code{customer} データベースには全てのホストから接続できます。 @code{custom} ユーザーは、 @code{stupid} というパスワードを全てのホストで使用したいとします。 このユーザーの許可を @code{GRANT} 構文で定義するには、以下のようにします： @example shell> mysql --user=root mysql mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP -> ON bankaccount.* -> TO custom@@localhost -> IDENTIFIED BY 'stupid'; mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP -> ON expenses.* -> TO custom@@whitehouse.gov -> IDENTIFIED BY 'stupid'; mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP -> ON customer.* -> TO custom@@'%' -> IDENTIFIED BY 'stupid'; @end example The reason that we do to grant statements for the user 'custom' is that we want the give the user access to MySQL both from the local machine with Unix sockets and from the remote machine 'whitehouse.gov' over TCP/IP. 許可テーブルを直接変更してこのユーザーの権限を設定するにはいかのようにします (@code{FLUSH PRIVILEGES} を最後に実行している事に注意)： @example shell> mysql --user=root mysql mysql> INSERT INTO user (Host,User,Password) -> VALUES('localhost','custom',PASSWORD('stupid')); mysql> INSERT INTO user (Host,User,Password) -> VALUES('server.domain','custom',PASSWORD('stupid')); mysql> INSERT INTO user (Host,User,Password) -> VALUES('whitehouse.gov','custom',PASSWORD('stupid')); mysql> INSERT INTO db -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv, -> Create_priv,Drop_priv) -> VALUES -> ('localhost','bankaccount','custom','Y','Y','Y','Y','Y','Y'); mysql> INSERT INTO db -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv, -> Create_priv,Drop_priv) -> VALUES -> ('whitehouse.gov','expenses','custom','Y','Y','Y','Y','Y','Y'); mysql> INSERT INTO db -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv, -> Create_priv,Drop_priv) -> VALUES('%','customer','custom','Y','Y','Y','Y','Y','Y'); mysql> FLUSH PRIVILEGES; @end example 最初の３つの @code{INSERT} 文は、 @code{custom} ユーザーがそれぞれのホストから パスワードつきで接続できるように @code{user} テーブルに追加しています。 しかしここでは権限は１つも与えられていません(権限のデフォルト値は @code{'N'} です)。 次の三つの @code{INSERT} 文は、@code{bankaccount}, @code{expenses}, @code{customer} データベースに対する該当ホストからのアクセス許可を @code{custom} ユーザーに与えるように、 @code{db} テーブルに追加しています。 許可テーブルが直接変更された場合、これらをサーバーに反映させるために、許可テーブルの 再読み込みを(@code{FLUSH PRIVILEGES}で) サーバーにつげなければなりません。 もし、あるドメインの全てのマシンに接続を許可したい場合、 以下のように @code{GRANT} 構文を発行します： @example mysql> GRANT ... -> ON *.* -> TO myusername@@"%.mydomainname.com" -> IDENTIFIED BY 'mypassword'; @end example 許可テーブルを直接変更するには以下のようにします： @example mysql> INSERT INTO user VALUES ('%.mydomainname.com', 'myusername', -> PASSWORD('mypassword'),...); mysql> FLUSH PRIVILEGES; @end example @node User resources, Passwords, Adding users, User Account Management @subsection Limiting user resources Starting from MySQL 4.0.2 one can limit certain resources per user. So far, the only available method of limiting usage of MySQL server resources has been setting the @code{max_user_connections} startup variable to a non-zero value. But this method is strictly global and does not allow for management of individual users, which could be of particular interest to Internet Service Providers. Therefore, management of three resources is introduced on the individual user level: @itemize @bullet @item Number of all queries per hour: All commands that could be run by a user. @item Number of all updates per hour: Any command that changes any table or database. @item Number of connections made per hour: New connections opened per hour. @end itemize A user in the aforementioned context is a single entry in the @code{user} table, which is uniquely identified by its @code{user} and @code{host} columns. All users are by default not limited in using the above resources, unless the limits are granted to them. These limits can be granted @strong{only} via global @code{GRANT (*.*)}, using this syntax: @example GRANT ... WITH MAX_QUERIES_PER_HOUR N1 MAX_UPDATES_PER_HOUR N2 MAX_CONNECTIONS_PER_HOUR N3; @end example One can specify any combination of the above resources. N1, N2 and N3 are integers and stands for count / hour. If user reaches any of the above limits withing one hour, his connection will be terminated or refused and the appropriate error message shall be issued. Current usage values for a particular user can be flushed (set to zero) by issuing a @code{GRANT} statement with any of the above clauses, including a @code{GRANT} statement with the current values. Also, current values for all users will be flushed if privileges are reloaded (in the server or using @code{mysqladmin reload}) or if the @code{FLUSH USER_RESOURCES} command is issued. The feature is enabled as soon as a single user is granted with any of the limiting @code{GRANT} clauses. As a prerequisite for enabling this feature, the @code{user} table in the @code{mysql} database must contain the additional columns, as defined in the table creation scripts @code{mysql_install_db} and @code{mysql_install_db.sh} in @file{scripts} subdirectory. @node Passwords, Password security, User resources, User Account Management @subsection パスワードの設定法 @findex PASSWORD() @findex SET PASSWORD statement @cindex passwords, setting @cindex setting, passwords 多くの場合、ユーザ／パスワードを設定するために、@code{GRANT} を使用すべき です。以下は上級ユーザのためにだけあてはまります。 @xref{GRANT, , @code{GRANT}}. 前節の例で述べた、とても重要な基本原則： @code{INSERT} か @code{UPDATE} で空ではないパスワードを設定する場合、 暗号化するために @code{PASSWORD()} 関数を使用しなくてはなりません。 これは @code{user} テーブルはプレーンテキストでなく、暗号化されたパスワードであることを要求しているからです。 この原則を忘れてしまった場合、以下のようにしてパスワードをセットしてしまうかもしれません： @example shell> mysql -u root mysql mysql> INSERT INTO user (Host,User,Password) -> VALUES('%','jeffrey','biscuit'); mysql> FLUSH PRIVILEGES; @end example これは @code{user} テーブルにプレーンテキストの @code{'biscuit'} をパスワードとして登録してしまいます。 @code{jeffrey} ユーザーでこのパスワードを使用してサーバーに接続しようとすると、 @code{mysql} クライアントは暗号化したパスワードをサーバーに送ります。 サーバーは暗号化されたパスワード(@code{'biscuit'} では@emph{ありません}) と @code{user} テーブルに登録された値(@code{'biscuit'}) を比較します。 その結果、比較は失敗し、サーバーは接続を拒否します： @example shell> mysql -u jeffrey -pbiscuit test Access denied @end example @code{user} テーブルに登録されるパスワードは暗号化されたものでなくてはなりません。 @code{INSERT} 構文は以下のようにして使用しなくてはなりません： @example mysql> INSERT INTO user (Host,User,Password) -> VALUES('%','jeffrey',PASSWORD('biscuit')); @end example @code{SET PASSWORD} 構文を使用する場合は、以下のように @code{PASSWORD()} 関数を使用しなくてはなりません： @example mysql> SET PASSWORD FOR jeffrey@@"%" = PASSWORD('biscuit'); @end example もし @code{GRANT ... IDENTIFIED BY} 構文や @code{mysqladmin password} コマンド でパスワードを設定した場合、@code{PASSWORD()} 関数は必要ありません。 両方とも、パスワードを暗号化してくれますので、 以下のように@code{'biscuit'}と与えます： @example mysql> GRANT USAGE ON *.* TO jeffrey@@"%" IDENTIFIED BY 'biscuit'; @end example or @example shell> mysqladmin -u jeffrey password biscuit @end example @strong{注意}： @code{PASSWORD()} は UNIX のパスワードで使用されている暗号化と 違うことにも留意してください。 @xref{User names}. @node Password security, Secure connections, Passwords, User Account Management @subsection パスワードを安全にする 自分のパスワードを他人にさらけ出すのは勧められることではありません。 それぞれの方法に於ける危険度に応じ、以下に示す方法でクライアントプログラムに あなたのパスワードをあたえて走らせることができます： @itemize @bullet @item 一般ユーザに @code{mysql.user} テーブルへのアクセスを与えてはいけません。 ユーザの暗号化されたパスワード知ることで、そのユーザとしてログインが可能に なります。パスワードは、使用される本当のパスワードを見ることができないよう に、スクランブルされているだけです(同じようなパスワードを他のアプリケーショ ンでたまたま使用する場合のため)。 @item @code{-pyour_pass} か @code{--password=your_pass} オプションをコマンドラインで使用します。 これは便利ですが安全ではありません。あなたのパスワードは (@code{ps} コマンドのような) システムの状態を見るコマンドにて見ることができます。 (MySQL クライアントは初期化過程においてコマンドラインの引数をゼロで上書きして 見せないようにしているのですが、瞬間ですが値が見えてしまうのです) @item @code{-p} あるいは @code{--password} オプションを @code{your_pass} を与えないで使用します。 この場合、クライアントプログラムはターミナルを通じてパスワードの入力を促してきます: @findex -p option @findex -password option @example shell> mysql -u user_name -p Enter password: ******** @end example @samp{*} 文字はパスワードを表しています。 これはコマンドラインにパスワードを指定するより安全です。他のユーザーには見えませんから。 しかしこのパスワードを毎回入れる方法は対話式のプログラムを実行する場合だけに使用できる手です。 もし非対話式のスクリプトからクライアントプログラムを起動したい場合、 パスワードを端末から入れる機会がありません。 On some systems, you may even find that the first line of your script is read and interpreted (incorrectly) as your password! @item @tindex .my.cnf file 設定ファイルにパスワードを書いておくこともできます。 例えば、自分のホームディレクトリーにある @file{.my.cnf} ファイルの @code{[client]} セクションに、以下のような形で書きます： @example [client] password=your_pass @end example もし @file{.my.cnf} ファイルにパスワードを書いているなら、ファイルはグループや その他のユーザーが読み書きできないようにすべきです。ファイルのモードは @code{400} か @code{600} にします。 @xref{Option files}. @item @code{MYSQL_PWD} 環境変数にパスワードを設定することもできます。しかしこの方法は きわめて危険であるので、使用すべきではありません。 @code{ps} のあるバージョンでは、実行中のプロセスの環境変数を表示するオプションがあります； もし @code{MYSQL_PWD} 環境変数にパスワードを設定していると全てべたで見れます。 このバージョンの @code{ps} を持っていないシステムだとしても、プロセスの環境変数を調べる 方法がないとはいえないので、この方法はあまりいい方法ではありません。 @xref{Environment variables}. @end itemize まとめると、より安全な方法は、 パスワードプロンプトを返すクライアントプログラムを実行するか、 適切なパーミッションをかけた @file{.my.cnf} ファイルにパスワードを書くか です。 @node Secure connections, , Password security, User Account Management @subsection Using Secure Connections @cindex OpenSSL @cindex SSL and X509 Basics @menu * Secure basics:: Basics * Secure requirements:: Requirements * Secure Create Certs:: Setting Up SSL Certificates for MySQL * Secure GRANT:: @code{GRANT} Options @end menu @node Secure basics, Secure requirements, Secure connections, Secure connections @subsubsection Basics Beginning with version 4.0.0, MySQL has support for SSL encrypted connections. To understand how MySQL uses SSL, it's necessary to explain some basic SSL and X509 concepts. People who are already familiar with them can skip this part. By default, MySQL uses unencrypted connections between the client and the server. This means that someone could watch all your traffic and look at the data being sent or received. They could even change the data while it is in transit between client and server. Sometimes you need to move information over public networks in a secure fashion; in such cases, using an unencrypted connection is unacceptable. SSL is a protocol that uses different encryption algorithms to ensure that data received over a public network can be trusted. It has mechanisms to detect any change, loss or replay of data. SSL also incorporates algorithms to recognise and provide identity verification using the X509 standard. @cindex What is encryption Encryption is the way to make any kind of data unreadable. In fact, today's practice requires many additional security elements from encryption algorithms. They should resist many kind of known attacks like just messing with the order of encrypted messages or replaying data twice. @cindex What is an X509/Certificate? X509 is a standard that makes it possible to identify someone on the Internet. It is most commonly used in e-commerce applications. In basic terms, there should be some company (called a ``Certificate Authority'') that assigns electronic certificates to anyone who needs them. Certificates rely on asymmetric encryption algorithms that have two encryption keys (a public key and a secret key). A certificate owner can prove his identity by showing his certificate to other party. A certificate consists of its owner's public key. Any data encrypted with this public key can be decrypted only using the corresponding secret key, which is held by the owner of the certificate. MySQL doesn't use encrypted connections by default, because doing so would make the client/server protocol much slower. Any kind of additional functionality requires the computer to do additional work and encrypting data is a CPU-intensive operation that requires time and can delay MySQL main tasks. By default MySQL is tuned to be fast as possible. If you need more information about SSL, X509, or encryption, you should use your favourite Internet search engine and search for keywords in which you are interested. @node Secure requirements, Secure Create Certs, Secure basics, Secure connections @subsubsection Requirements To get secure connections to work with MySQL you must do the following: @enumerate @item OpenSSL ライブラリをインストール。 我々は openssl 0.9.6 でテストしました。 @uref{http://www.openssl.org/}. @item @code{--with-vio --with-openssl} で MySQL をコンフィギャ. @item もしあなたが古い MySQL (4.0未満)をインストールしているなら、 @code{mysql.user} テーブルを update するべきです。 これは @code{mysql_fix_privilege_tables} スクリプトで可能です。 MySQL 4.0.0 以上ではこの作業が必要です。 ( 訳注: このスクリプトは、前のバージョンが 3.23 の場合、 @code{mysql.user} テーブル に @code{ssl_type}, @code{ssl_cipher}, @code{x509_issuer}, @code{x509_subject} フィールドを追加し、 @code{mysql.*} の全てのテーブルを @code{ALTER TABLE .. TYPE=MyISAM} で作成し直します。 実行前には、念のため、@code{mysql} データベースを @code{mysqldump} か 他の方法でバックアップしておきましょう。 ) @item 実行中の @code{mysqld} が OpenSSL をサポートしている場合は、 @code{SHOW VARIABLES LIKE 'have_openssl'} が @code{YES} を返します。 @end enumerate @node Secure Create Certs, Secure GRANT, Secure requirements, Secure connections @subsubsection Setting Up SSL Certificates for MySQL Here is an example for setting up SSL certificates for MySQL: @example DIR=`pwd`/openssl PRIV=$DIR/private mkdir $DIR $PRIV $DIR/newcerts cp /usr/share/ssl/openssl.cnf $DIR replace ./demoCA $DIR -- $DIR/openssl.cnf # Create necessary files: $database, $serial and $new_certs_dir # directory (optional) touch $DIR/index.txt echo "01" > $DIR/serial # # Generation of Certificate Authority(CA) # openssl req -new -x509 -keyout $PRIV/cakey.pem -out $DIR/cacert.pem \ -config $DIR/openssl.cnf # Sample output: # Using configuration from /home/monty/openssl/openssl.cnf # Generating a 1024 bit RSA private key # ................++++++ # .........++++++ # writing new private key to '/home/monty/openssl/private/cakey.pem' # Enter PEM pass phrase: # Verifying password - Enter PEM pass phrase: # ----- # You are about to be asked to enter information that will be incorporated # into your certificate request. # What you are about to enter is what is called a Distinguished Name or a DN. # There are quite a few fields but you can leave some blank # For some fields there will be a default value, # If you enter '.', the field will be left blank. # ----- # Country Name (2 letter code) [AU]:FI # State or Province Name (full name) [Some-State]:. # Locality Name (eg, city) []: # Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB # Organizational Unit Name (eg, section) []: # Common Name (eg, YOUR name) []:MySQL admin # Email Address []: # # Create server request and key # openssl req -new -keyout $DIR/server-key.pem -out \ $DIR/server-req.pem -days 3600 -config $DIR/openssl.cnf # Sample output: # Using configuration from /home/monty/openssl/openssl.cnf # Generating a 1024 bit RSA private key # ..++++++ # ..........++++++ # writing new private key to '/home/monty/openssl/server-key.pem' # Enter PEM pass phrase: # Verifying password - Enter PEM pass phrase: # ----- # You are about to be asked to enter information that will be incorporated # into your certificate request. # What you are about to enter is what is called a Distinguished Name or a DN. # There are quite a few fields but you can leave some blank # For some fields there will be a default value, # If you enter '.', the field will be left blank. # ----- # Country Name (2 letter code) [AU]:FI # State or Province Name (full name) [Some-State]:. # Locality Name (eg, city) []: # Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB # Organizational Unit Name (eg, section) []: # Common Name (eg, YOUR name) []:MySQL server # Email Address []: # # Please enter the following 'extra' attributes # to be sent with your certificate request # A challenge password []: # An optional company name []: # # Remove the passphrase from the key (optional) # openssl rsa -in $DIR/server-key.pem -out $DIR/server-key.pem # # Sign server cert # openssl ca -policy policy_anything -out $DIR/server-cert.pem \ -config $DIR/openssl.cnf -infiles $DIR/server-req.pem # Sample output: # Using configuration from /home/monty/openssl/openssl.cnf # Enter PEM pass phrase: # Check that the request matches the signature # Signature ok # The Subjects Distinguished Name is as follows # countryName :PRINTABLE:'FI' # organizationName :PRINTABLE:'MySQL AB' # commonName :PRINTABLE:'MySQL admin' # Certificate is to be certified until Sep 13 14:22:46 2003 GMT (365 days) # Sign the certificate? [y/n]:y # # # 1 out of 1 certificate requests certified, commit? [y/n]y # Write out database with 1 new entries # Data Base Updated # # Create client request and key # openssl req -new -keyout $DIR/client-key.pem -out \ $DIR/client-req.pem -days 3600 -config $DIR/openssl.cnf # Sample output: # Using configuration from /home/monty/openssl/openssl.cnf # Generating a 1024 bit RSA private key # .....................................++++++ # .............................................++++++ # writing new private key to '/home/monty/openssl/client-key.pem' # Enter PEM pass phrase: # Verifying password - Enter PEM pass phrase: # ----- # You are about to be asked to enter information that will be incorporated # into your certificate request. # What you are about to enter is what is called a Distinguished Name or a DN. # There are quite a few fields but you can leave some blank # For some fields there will be a default value, # If you enter '.', the field will be left blank. # ----- # Country Name (2 letter code) [AU]:FI # State or Province Name (full name) [Some-State]:. # Locality Name (eg, city) []: # Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB # Organizational Unit Name (eg, section) []: # Common Name (eg, YOUR name) []:MySQL user # Email Address []: # # Please enter the following 'extra' attributes # to be sent with your certificate request # A challenge password []: # An optional company name []: # # Remove a passphrase from the key (optional) # openssl rsa -in $DIR/client-key.pem -out $DIR/client-key.pem # # Sign client cert # openssl ca -policy policy_anything -out $DIR/client-cert.pem \ -config $DIR/openssl.cnf -infiles $DIR/client-req.pem # Sample output: # Using configuration from /home/monty/openssl/openssl.cnf # Enter PEM pass phrase: # Check that the request matches the signature # Signature ok # The Subjects Distinguished Name is as follows # countryName :PRINTABLE:'FI' # organizationName :PRINTABLE:'MySQL AB' # commonName :PRINTABLE:'MySQL user' # Certificate is to be certified until Sep 13 16:45:17 2003 GMT (365 days) # Sign the certificate? [y/n]:y # # # 1 out of 1 certificate requests certified, commit? [y/n]y # Write out database with 1 new entries # Data Base Updated # # Create a my.cnf file that you can use to test the certificates # cnf="" cnf="$cnf [client]" cnf="$cnf ssl-ca=$DIR/cacert.pem" cnf="$cnf ssl-cert=$DIR/client-cert.pem" cnf="$cnf ssl-key=$DIR/client-key.pem" cnf="$cnf [mysqld]" cnf="$cnf ssl-ca=$DIR/cacert.pem" cnf="$cnf ssl-cert=$DIR/server-cert.pem" cnf="$cnf ssl-key=$DIR/server-key.pem" echo $cnf | replace " " ' ' > $DIR/my.cnf # # To test MySQL mysqld --defaults-file=$DIR/my.cnf & mysql --defaults-file=$DIR/my.cnf @end example You can also test your setup by modifying the above @file{my.cnf} file to refer to the demo certificates in the mysql-source-dist/SSL direcory. @node Secure GRANT, , Secure Create Certs, Secure connections @subsubsection @code{GRANT} オプション @cindex SSL related options @findex REQUIRE GRANT option @findex GRANT statement MySQL can check X509 certificate attributes in addition to the normal username/password scheme. All the usual options are still required (username, password, IP address mask, database/table name). There are different possibilities to limit connections: @itemize @bullet @item SSL か X509 オプションが無い場合は、 もしユーザー名とパスワードが正しければ、 暗号化と非暗号化の全ての接続が許可されます。 @item @code{REQUIRE SSL} オプションは、サーバーに対して、 SSL 接続のみを許可します。 もし、非SSL接続を許可する ACL (アクセス・コントロール・リスト)の レコードが存在する場合、このオプションは除かれることに注意してください。 @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" REQUIRE SSL; @end example @item @code{REQUIRE X509} は、クライアントが有効な証明書を持っていることを 意味しますが、しかし、 正確(的確,厳密)な certificate、issuer、subject を持っているかについては、 留意していません。 唯一の制限は、CA 証明書のシグネチャが正しいかを確かめることです。 @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" REQUIRE X509; @end example @item @code{REQUIRE ISSUER issuer} はコネクションをより制限します: クライアントは CA 局から発行される有効な X509 証明書を 持っていなければなりません。 X509 証明書を使う事は、常に 暗号化を暗に意味します。 そのため、@code{SSL} オプションはこの場合は必要ではありません。 @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" -> REQUIRE ISSUER "C=FI, ST=Some-State, L=Helsinki, "> O=MySQL Finland AB, CN=Tonu Samuel/Email=tonu@@mysql.com"; @end example @item @code{REQUIRE SUBJECT "subject"} はクライアントにたいして、 @code{"subject"} をサブジェクトに持つ、有効な X509 証明書を要求します。 もしクライアントが正当な certificate を持っていても @code{"subject"} が違うものであれば、コネクションは許可されません。 @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" -> REQUIRE SUBJECT "C=EE, ST=Some-State, L=Tallinn, "> O=MySQL demo client certificate, "> CN=Tonu Samuel/Email=tonu@@mysql.com"; @end example @item @code{REQUIRE CIPHER "cipher"} is needed to assure enough strong ciphers and keylengths will be used. SSL itself can be weak if old algorithms with short encryption keys are used. Using this option, we can ask for some exact cipher method to allow a connection. @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" -> REQUIRE CIPHER "EDH-RSA-DES-CBC3-SHA"; @end example 以下のようにして、これらのオプションは組み合わせることが可能です： The @code{SUBJECT}, @code{ISSUER}, and @code{CIPHER} options can be combined in the @code{REQUIRE} clause like this: @example mysql> GRANT ALL PRIVILEGES ON test.* TO root@@localhost -> IDENTIFIED BY "goodsecret" -> REQUIRE SUBJECT "C=EE, ST=Some-State, L=Tallinn, "> O=MySQL demo client certificate, "> CN=Tonu Samuel/Email=tonu@@mysql.com" -> AND ISSUER "C=FI, ST=Some-State, L=Helsinki, "> O=MySQL Finland AB, CN=Tonu Samuel/Email=tonu@@mysql.com" -> AND CIPHER "EDH-RSA-DES-CBC3-SHA"; @end example Starting from MySQL 4.0.4 the @code{AND} keyword is optional between @code{REQUIRE} options. オプションの指定順序はといません。 しかし同じオプションを二重に使用できません。 違うオプションのみが、組み合わせ可能です。 @end itemize @node Disaster Prevention, Database Administration, User Account Management, MySQL Database Administration @section Disaster Prevention and Recovery @c FIX: add section intro @menu * Backup:: Database Backups * BACKUP TABLE:: @code{BACKUP TABLE} Syntax * RESTORE TABLE:: @code{RESTORE TABLE} Syntax * CHECK TABLE:: @code{CHECK TABLE} Syntax * REPAIR TABLE:: @code{REPAIR TABLE} Syntax * Table maintenance:: Using @code{myisamchk} for Table Maintenance and Crash Recovery * Maintenance regimen:: Setting Up a Table Maintenance Regimen * Table-info:: Getting Information About a Table @end menu @node Backup, BACKUP TABLE, Disaster Prevention, Disaster Prevention @subsection データベースのバックアップ @cindex databases, backups @cindex backups MySQL テーブルはファイルとして格納されるため、バックアップを行 うのは簡単です。矛盾のないバックアップを得るためには、 @code{FLUSH TABLES} をおこなって、@code{LOCK TABLES} を関連するテーブルで行ってください。@xref{LOCK TABLES, , @code{LOCK TABLES}}. @xref{FLUSH, , @code{FLUSH}}. 読み込みロックだ けが必要なので、そのテーブルでデータベースディレクトリのファイルのコピー が行われている間も、他のスレッドはクエリを継続できます。 The @code{FLUSH TABLE} is needed to ensure that the all active index pages is written to disk before you start the backup. Starting from 3.23.56 and 4.0.12 @code{BACKUP TABLE} will not allow you to overwrite existing files as this would be a security risk. もし、テーブルを SQL レベルでバックアップしたいのであれば、@code{SELECT INTO OUTFILE} か @code{BACKUP TABLE} を使用できます。 @xref{BACKUP TABLE}. 他の方法は @code{mysqldump} プログラムか @code{mysqlhotcopy スクリプト} を使用することです。 @xref{mysqldump, , @code{mysqldump}}. @xref{mysqlhotcopy, , @code{mysqlhotcopy}}. @enumerate @item フルバックアップをとるには： @example shell> mysqldump --tab=/path/to/some/dir --opt --all or shell> mysqlhotcopy database /path/to/some/dir @end example You can also simply copy all table files (@file{*.frm}, @file{*.MYD}, and @file{*.MYI} files) as long as the server isn't updating anything. The script @code{mysqlhotcopy} does use this method. @item @cindex log files, names @cindex @code{mysqlbinlog} @code{mysqld} を止め、そして @code{--log-update[=file_name]} オプションをつけて起動します。 @xref{Update log}. ログファイルは、 @code{mysqldump} 実行後に行われたデータベースの変更を 複製するための情報を与えてくれます。 @end enumerate もしリストアをしなければならない場合、まず最初に @code{REPAIR TABLE} か @code{myisamchk -r} を実行してテーブルの修復を試みてください。 ほとんどの場合、99.9% 修復はできるはずです。 もし @code{myisamchk} が失敗した場合、以下のようにします： (this will only work if you have started MySQL with @code{--log-update}, @pxref{Update log}): @enumerate @item オリジナルの @code{mysqldump} バックアップデータをリストアします。 @item 次のコマンドを実行して、バイナリログ内の更新を再実行します。 @example shell> mysqlbinlog hostname-bin.[0-9]* | mysql @end example 更新ログを使用する場合は、次のようにできます: @example shell> ls -1 -t -r hostname.[0-9]* | xargs cat | mysql @end example @end enumerate @code{ls} は、全ての更新ログファイルを正しい順で得るために行われます。 @code{SELECT * INTO OUTFILE 'file_name' FROM tbl_name} での選択的バックアップと @code{LOAD DATA FROM INFILE 'file_name' REPLACE ...} でのリストアを行う こともできます。重複レコードを避けるためには、テーブル内に @code{PRIMARY KEY} か @code{UNIQUE} が必要です。@code{REPLACE} は、'重複インデックス' 衝突があった場合、 新しいレコードを挿入する時に古いレコードが新しいものに置き換えられることを意味します。 If you get performance problems in making backups on your system, you can solve this by setting up replication and do the backups on the slave instead of on the master. @xref{Replication Intro}. If you are using a Veritas filesystem, you can do: @enumerate @item From a client (or Perl), execute: @code{FLUSH TABLES WITH READ LOCK}. @item From another shell, execute: @code{mount vxfs snapshot}. @item From the first client, execute: @code{UNLOCK TABLES}. @item Copy files from snapshot. @item Unmount snapshot. @end enumerate @node BACKUP TABLE, RESTORE TABLE, Backup, Disaster Prevention @subsection @code{BACKUP TABLE} 構文 (3.23.25以上) @findex BACKUP TABLE @cindex backups, database @example BACKUP TABLE tbl_name[,tbl_name...] TO '/path/to/backup/directory' @end example Copies to the backup directory the minimum number of table files needed to restore the table, after flushing any buffered changes to disk. Currently works only for @code{MyISAM} tables. For @code{MyISAM} tables, copies @file{.frm} (definition) and @file{.MYD} (data) files. The index file can be rebuilt from those two. Before using this command, please see @ref{Backup}. During the backup, a read lock will be held for each table, one at time, as they are being backed up. If you want to back up several tables as a snapshot, you must first issue @code{LOCK TABLES} obtaining a read lock for each table in the group. The command returns a table with the following columns: @multitable @columnfractions .15 .40 @item @strong{Column} @tab @strong{Value} @item Table @tab Table name @item Op @tab Always ``backup'' @item Msg_type @tab One of @code{status}, @code{error}, @code{info} or @code{warning}. @item Msg_text @tab The message. @end multitable Note that @code{BACKUP TABLE} is only available in MySQL version 3.23.25 and later. @node RESTORE TABLE, CHECK TABLE, BACKUP TABLE, Disaster Prevention @subsection @code{RESTORE TABLE} 構文 (3.23.25以上) @findex RESTORE TABLE @example RESTORE TABLE tbl_name[,tbl_name...] FROM '/path/to/backup/directory' @end example Restores the table(s) from the backup that was made with @code{BACKUP TABLE}. Existing tables will not be overwritten; if you try to restore over an existing table, you will get an error. Restoring will take longer than backing up due to the need to rebuild the index. The more keys you have, the longer it will take. Just as @code{BACKUP TABLE}, @code{RESTORE TABLE} currently works only for @code{MyISAM} tables. The command returns a table with the following columns: @multitable @columnfractions .15 .40 @item @strong{Column} @tab @strong{Value} @item Table @tab Table name @item Op @tab Always ``restore'' @item Msg_type @tab One of @code{status}, @code{error}, @code{info} or @code{warning}. @item Msg_text @tab The message. @end multitable @node CHECK TABLE, REPAIR TABLE, RESTORE TABLE, Disaster Prevention @subsection @code{CHECK TABLE} 構文 (3.23.13以上) @findex CHECK TABLE @example CHECK TABLE tbl_name[,tbl_name...] [option [option...]] option = QUICK | FAST | MEDIUM | EXTENDED | CHANGED @end example @code{CHECK TABLE} は @code{MyISAM} テーブル と @code{InnoDB} テーブルだけで動作します。 @code{MyISAM} テーブルでは、テーブル上で @code{myisamchk -m table_name} を 実行するのと同じことです。 オプションを何も指定しない場合は @code{MEDIUM} が使用されます。 テーブルのエラーチェックを行ないます。@code{MyISAM} テーブルではキー統計が 更新されます。 このコマンドは次のフィールドを持つテーブルを返します: @multitable @columnfractions .15 .40 @item @strong{Column} @tab @strong{Value} @item Table @tab テーブル名 @item Op @tab 常に ``check'' @item Msg_type @tab @code{status}, @code{error}, @code{info}, @code{warning} のうちの一つ。 @item Msg_text @tab メッセージ。 @end multitable 注意: チェックされた各テーブルに対する情報の多くのレコードが得られます。 最後の１レコードは @code{Msg_type status} になり、通常は @code{OK} で あるべきです。@code{OK} や @code{Table is already up to date} が得られない場合は、 テーブルの修復を通常通り実行すべきです。 @xref{Table maintenance}. @code{Table is already up to date} means that the table the given @code{TYPE} told MySQL that there wasn't any need to check the table. 様々なチェックタイプは次の意味です: @multitable @columnfractions .15 .85 @item @strong{Type} @tab @strong{Meaning} @item @code{QUICK} @tab 間違ったリンクをチェックするレコードを走査しません。 @item @code{FAST} @tab 正しくクローズされなかったテーブルだけをチェックします。 @item @code{CHANGED} @tab 最後にチェックしてから変更されたテーブルと、正しくクローズされなかったテーブルだけをチェックします。 @item @code{MEDIUM} @tab 削除されたリンクが OK であることを確かめるためにレコードを走査します。これはレコードのキーチェックサムも計算し、キーの計算されたチェックサムをで、これを確かめます。 @item @code{EXTENDED} @tab 各レコードのすべてのキーを完全キー検索を行ないます。テーブルが 100% 正当なことを確実にしますが、長い時間が掛かります！ @end multitable 動的なサイズの @code{MyISAM} テーブルについて、開始されたチェックは常に @code{MEDIUM} チェックを行ないます。清適サイズレコードでは、レコードはめっ たに壊れないので、@code{QUICK} と @code{FAST} ではレコードスキャンをスキッ プします。 チェックオプションは次のように組み合わせられます: @example CHECK TABLE test_table FAST QUICK; @end example これは、テーブルが正しくクローズされなかったかどうかだけを素早くチェックし ます。 @strong{Note}: いくつかのケースでは @code{CHECK TABLE} はテーブルを変更し ます！ これはテーブルが '汚れている' か '正しくクローズされなかった' とマー クされているのに、@code{CHECK TABLE} がテーブル内に何も問題を発見しなかっ た場合に発生します。この場合、@code{CHECK TABLE} はテーブルを OK とマーク します。 If a table is corrupted, then it's most likely that the problem is in the indexes and not in the data part. All of the above check types checks the indexes thoroughly and should thus find most errors. If you just want to check a table that you assume is okay, you should use no check options or the @code{QUICK} option. The latter should be used when you are in a hurry and can take the very small risk that @code{QUICK} didn't find an error in the datafile. (In most cases MySQL should find, under normal usage, any error in the data file. If this happens then the table will be marked as 'corrupted', in which case the table can't be used until it's repaired.) @code{FAST} and @code{CHANGED} are mostly intended to be used from a script (for example to be executed from @code{cron}) if you want to check your table from time to time. In most cases you @code{FAST} is to be prefered over @code{CHANGED}. (The only case when it isn't is when you suspect a bug you have found a bug in the @code{MyISAM} code.) @code{EXTENDED} is only to be used after you have run a normal check but still get strange errors from a table when MySQL tries to update a row or find a row by key (this is very unlikely if a normal check has succeeded!). Some things reported by check table, can't be corrected automatically: @itemize @bullet @item @code{Found row where the auto_increment column has the value 0}. This means that you have in the table a row where the @code{AUTO_INCREMENT} index column contains the value 0. (It's possible to create a row where the @code{AUTO_INCREMENT} column is 0 by explicitly setting the column to 0 with an @code{UPDATE} statement) This isn't an error in itself, but could cause trouble if you decide to dump the table and restore it or do an @code{ALTER TABLE} on the table. In this case the @code{AUTO_INCREMENT} column will change value, according to the rules of @code{AUTO_INCREMENT} columns, which could cause problems like a duplicate key error. To get rid of the warning, just execute an @code{UPDATE} statement to set the column to some other value than 0. @end itemize @node REPAIR TABLE, Table maintenance, CHECK TABLE, Disaster Prevention @subsection @code{REPAIR TABLE} 構文 (3.23.14以上) @findex REPAIR TABLE @example REPAIR TABLE tbl_name[,tbl_name...] [QUICK] [EXTENDED] [USE_FRM] @end example @code{REPAIR TABLE} は @code{MyISAM} テーブルだけで動作します。テーブルに @code{myisamchk -r table_name} を実行することと同じです。 Normally you should never have to run this command, but if disaster strikes you are very likely to get back all your data from a MyISAM table with @code{REPAIR TABLE}. If your tables get corrupted a lot you should try to find the reason for this! @xref{Crashing}. @xref{MyISAM table problems}. @code{REPAIR TABLE} はなんとかなる壊れたテーブルを修復します。コマンドは次 のフィールドを含む表を返します: @multitable @columnfractions .15 .40 @item @strong{Column} @tab @strong{Value} @item Table @tab テーブル名 @item Op @tab Always ``repair'' @item Msg_type @tab @code{status}, @code{error}, @code{info}, @code{warning} のどれか. @item Msg_text @tab メッセージ @end multitable 注意: 修復された各テーブルの情報の多くのレコードを得ることがあります。最後 の１レコードは @code{Msg_type status} になり、通常は @code{OK} であるべき です。@code{OK} が得られなければ、@code{myisamchk -o} でテーブルの修復を試 みるべきです。@code{REPAIR TABLE} はまだ、@code{myisamchk} のオプションの 全てを持っていないからです。 In the near future, we will make it more flexible. @code{QUICK} が与えられた場合は、MySQL はインデックスツリー の @code{REPAIR} だけを試みます。 If you use @code{EXTENDED} then MySQL will create the index row by row instead of creating one index at a time with sorting; this may be better than sorting on fixed-length keys if you have long @code{CHAR} keys that compress very well. This type of repair is like that done by @code{myisamchk --safe-recover}. As of @code{MySQL} 4.0.2, there is a @code{USE_FRM} mode for @code{REPAIR}. Use it if the @file{.MYI} file is missing or if its header is corrupted. In this mode MySQL will recreate the table, using information from the @file{.frm} file. This kind of repair cannot be done with @code{myisamchk}. @node Table maintenance, Maintenance regimen, REPAIR TABLE, Disaster Prevention @subsection テーブルのメンテナンス、クラッシュからの修復のための @code{myisamchk} 使用 Starting with MySQL Version 3.23.13, you can check MyISAM tables with the @code{CHECK TABLE} command. @xref{CHECK TABLE}. You can repair tables with the @code{REPAIR TABLE} command. @xref{REPAIR TABLE}. MyISAM テーブル (@code{.MYI} and @code{.MYD}) の検査・修復には @code{myisamchk} を 使用します。 ISAM テーブル (@code{.ISM} and @code{.ISD}) の検査・修復には @code{isamchk} を 使用します。 @xref{Table types}. 以下の文は @code{myisamchk} について述べていますが、@code{isamchk} にもすべて 当てはまります。 @code{myisamchk} ユーティリティは、データベースのテーブルの情報を得たり、 チェックしたり、テーブルの修復や最適化に使用します。 以下のセクションでは、 @code{myisamchk} の起動方法(オプションの説明も含む)、 テーブルの保守スケジュールのたて方、 @code{myisamchk} の色々な機能の使い方を述べます。 テーブルの修復と最適化のために、ほとんどの場合、 @code{OPTIMIZE TABLES} コマンドが使用できます。しかしこれは @code{myisamchk} に比べて、 遅くて確実でもありません。(fatal error発生時の場合)。これは その反面、使用方法が簡単でテーブルのフラッシュを気にかける必要がありません。 @xref{OPTIMIZE TABLE, , @code{OPTIMIZE TABLE}}. Even that the repair in @code{myisamchk} is quite secure, it's always a good idea to make a backup @emph{before} doing a repair (or anything that could make a lot of changes to a table) @menu * myisamchk syntax:: @code{myisamchk} Invocation Syntax * myisamchk general options:: General Options for @code{myisamchk} * myisamchk check options:: Check Options for @code{myisamchk} * myisamchk repair options:: Repair Options for myisamchk * myisamchk other options:: Other Options for @code{myisamchk} * myisamchk memory:: @code{myisamchk} Memory Usage * Crash recovery:: Using @code{myisamchk} for Crash Recovery * Check:: How to Check Tables for Errors * Repair:: How to Repair Tables * Optimisation:: Table Optimisation @end menu @node myisamchk syntax, myisamchk general options, Table maintenance, Table maintenance @subsubsection @code{myisamchk} 起動構文 @code{myisamchk} は以下のようにして起動します: @example shell> myisamchk [options] tbl_name @end example @code{options} に、あなたが @code{myisamchk} にさせたいことを指定します。 その説明は後述します。(@code{myisamchk --help} と実行すれば、オプションの一覧が取れます)。 オプションがなければ、 @code{myisamchk} は単にテーブルを検査するだけです。 より多くの情報を得たい、あるいは、 @code{myisamchk} に誤り訂正の行動を 取らせる事については、後述します。 @code{tbl_name} は検査/修復したいテーブル名です。 もしどこか違うディレクトリにあるデータベースに対して @code{myisamchk} を走らせたいなら、 @code{myisamchk} にはファイルがどこにあるかわからないので、 ファイルのパスを指定しなければなりません。 実際、 @code{myisamchk} はあなたが使用しているファイルがデータベースのディレクトリにある かどうかは考慮しません； ほかの場所にデータベーステーブルのファイルをコピーし、そのコピーしたファイルに対して 回復操作を実行することができます。 @code{myisamchk} コマンドラインには、複数のテーブル名が指定できます。 また、インデックスファイル名(@file{.MYI} 接尾語のついたファイル)も指定でき、 さらに @file{*.MYI} とすれば、ディレクトリ内の全てのテーブルが指定できます。 例えば、現在のカレントディレクトリがデーターベースディレクトリならば、 そのディレクトリ内の全てのテーブルは、以下のようにして検査できます： @example shell> myisamchk *.MYI @end example データベースディレクトリに入っていない場合、 パスを指定することにより全てのテーブルが検査できます： @example shell> myisamchk /path/to/database_dir/*.MYI @end example MySQL データディレクトリのパスにワイルドカードを使用することにより、 データベースの全てのテーブルも検査できます： @example shell> myisamchk /path/to/datadir/*/*.MYI @end example The recommended way to quickly check all tables is: @example myisamchk --silent --fast /path/to/datadir/*/*.MYI isamchk --silent /path/to/datadir/*/*.ISM @end example If you want to check all tables and repair all tables that are corrupted, you can use the following line: @example myisamchk --silent --force --fast --update-state -O key_buffer=64M \ -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M \ /path/to/datadir/*/*.MYI isamchk --silent --force -O key_buffer=64M -O sort_buffer=64M \ -O read_buffer=1M -O write_buffer=1M /path/to/datadir/*/*.ISM @end example The above assumes that you have more than 64 M free. Note that if you get an error like: @example myisamchk: warning: 1 clients is using or hasn't closed the table properly @end example This means that you are trying to check a table that has been updated by the another program (like the @code{mysqld} server) that hasn't yet closed the file or that has died without closing the file properly. If you @code{mysqld} is running, you must force a sync/close of all tables with @code{FLUSH TABLES} and ensure that no one is using the tables while you are running @code{myisamchk}. In MySQL Version 3.23 the easiest way to avoid this problem is to use @code{CHECK TABLE} instead of @code{myisamchk} to check tables. @node myisamchk general options, myisamchk check options, myisamchk syntax, Table maintenance @subsubsection @code{myisamchk} の一般オプション @cindex options, @code{myisamchk} @cindex @code{myisamchk}, options @code{myisamchk} supports the following options. @table @code @item -# or --debug=debug_options デバッグログの出力。 @code{debug_options} はよく @code{'d:t:o,filename'} とされます。 @item -? or --help ヘルプを表示して終了。 @item -O var=option, --set-variable var=option 変数に値を入れます。 Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--var=option} on its own. 可能な変数とデフォルトの値は @code{myisamchk --help} で確認できます: @multitable @columnfractions .20 .10 @item @strong{Variable} @tab @strong{Value} @item key_buffer_size @tab 523264 @item read_buffer_size @tab 262136 @item write_buffer_size @tab 262136 @item sort_buffer_size @tab 2097144 @item sort_key_blocks @tab 16 @item decode_bits @tab 9 @end multitable @code{sort_buffer_size} is used when the keys are repaired by sorting keys, which is the normal case when you use @code{--recover}. @code{key_buffer_size} is used when you are checking the table with @code{--extended-check} or when the keys are repaired by inserting key row by row in to the table (like when doing normal inserts). Repairing through the key buffer is used in the following cases: @itemize @bullet @item If you use @code{--safe-recover}. @item If the temporary files needed to sort the keys would be more than twice as big as when creating the key file directly. This is often the case when you have big @code{CHAR}, @code{VARCHAR} or @code{TEXT} keys as the sort needs to store the whole keys during sorting. If you have lots of temporary space and you can force @code{myisamchk} to repair by sorting you can use the @code{--sort-recover} option. @end itemize Reparing through the key buffer takes much less disk space than using sorting, but is also much slower. もし速い修復を望むなら、メモリの 1/4 を上記の変数にセットします。 You can set both variables to big values, as only one of the above buffers will be used at a time. @item -s or --silent 静粛モード。 エラーのみを出力します。 二度 @code{-s} を指定すると(@code{-ss})、@code{myisamchk} は ほとんど出力をしなくなります。 @item -v or --verbose 冗長モード。より多く情報を出力します。 @code{-d} と @code{-e} オプションと共に使用できます。 @code{-v} を複数指定すると(@code{-vv}, @code{-vvv})、もっと出力が多くなります！ @item -V or --version @code{myisamchk} バージョンを表示して終了。 @item -w or, --wait Instead of giving an error if the table is locked, wait until the table is unlocked before continuing. Note that if you are running @code{mysqld} on the table with @code{--skip-external-locking}, the table can only be locked by another @code{myisamchk} command. @end table @node myisamchk check options, myisamchk repair options, myisamchk general options, Table maintenance @subsubsection @code{myisamchk} の検査オプション @cindex check options, myisamchk @cindex tables, checking @table @code @item -c or --check テーブルのエラーをチェック。 これは @code{myisamchk} にオプションを 与えていない時のデフォルトです。 @item -e or --extend-check テーブルを非常に徹底的に検査します。 (ただし多くのインデックスがある場合、 とても遅くなります。). 極端な場合にだけで必要とされます。 通常 @code{myisamchk} や @code{myisamchk --medium-check} は、 このオプションなしで全てのエラーを見つけるはずです。 多くのメモリがマシンにあるなら、@code{--extended-check} を使用する際には @code{key_buffer_size} の値を多く増やします。 @item -F or --fast Check only tables that haven't been closed properly. @item -C or --check-only-changed Check only tables that have changed since the last check. @item -f or --force Restart @code{myisamchk} with @code{-r} (repair) on the table, if @code{myisamchk} finds any errors in the table. @item -i or --information 検査されたテーブルの統計情報を表示。 @item -m or --medium-check Faster than extended-check, but only finds 99.99% of all errors. Should, however, be good enough for most cases. @item -U or --update-state Store in the @file{.MYI} file when the table was checked and if the table crashed. This should be used to get full benefit of the @code{--check-only-changed} option, but you shouldn't use this option if the @code{mysqld} server is using the table and you are running @code{mysqld} with @code{--skip-external-locking}. @item -T or --read-only Don't mark table as checked. This is useful if you use @code{myisamchk} to check a table that is in use by some other application that doesn't use locking (like @code{mysqld --skip-external-locking}). @end table @node myisamchk repair options, myisamchk other options, myisamchk check options, Table maintenance @subsubsection myisamchk の修復オプション @cindex repair options, myisamchk @cindex files, repairing 以下のオプションは @code{myisamchk} を @code{-r} か @code{-o} オプションで 実行した場合に使用できます: @table @code @item -D # or --data-file-length=# Max length of datafile (when re-creating datafile when it's 'full'). @item -e or --extend-check Try to recover every possible row from the datafile. Normally this will also find a lot of garbage rows. Don't use this option if you are not totally desperate. @item -f or --force Overwrite old temporary files (@code{table_name.TMD}) instead of aborting. @item -k # or keys-used=# If you are using ISAM, tells the ISAM storage engine to update only the first @code{#} indexes. If you are using @code{MyISAM}, tells which keys to use, where each binary bit stands for one key (first key is bit 0). これはインサートを速くします！ 非アクティブになったインデックスは、@code{myisamchk -r} を使用すれば再びアクティ ブになります。 @item -l or --no-symlinks 修復時にシンボリックリンクを追いません。 通常、@code{myisamchk} はシンボリックリンクが指し示すテーブルも修復します。 This option doesn't exist in MySQL 4.0, as MySQL 4.0 will not remove symlinks during repair. @item -r or --recover Can fix almost anything except unique keys that aren't unique (which is an extremely unlikely error with ISAM/MyISAM tables). If you want to recover a table, this is the option to try first. Only if myisamchk reports that the table can't be recovered by @code{-r}, you should then try @code{-o}. (Note that in the unlikely case that @code{-r} fails, the datafile is still intact.) If you have lots of memory, you should increase the size of @code{sort_buffer_size}! @item -o or --safe-recover 古い修復方法を使用します (reads through all rows in order and updates all index trees based on the found rows); これは @code{-r} よりも遅いですが、 @code{-r} が扱えないものも扱えます。 This recovery method also uses much less disk space than @code{-r}. Normally one should always first repair with @code{-r}, and only if this fails use @code{-o}. If you have lots of memory, you should increase the size of @code{key_buffer_size}! @item -n or --sort-recover Force @code{myisamchk} to use sorting to resolve the keys even if the temporary files should be very big. @item --character-sets-dir=... Directory where character sets are stored. @item --set-character-set=name Change the character set used by the index @item -t or --tmpdir=path 一時ファイルを保存する先のパス。 もしセットされなければ、 @code{myisamchk} は @code{TMPDIR} 環境変数の値をこのパスとします。 Starting from MySQL 4.1, @code{tmpdir} can be set to a list of paths separated by colon @code{:} (semicolon @code{;} on Windows). They will be used in round-robin fashion. @item -q or --quick Faster repair by not modifying the datafile. One can give a second @code{-q} to force @code{myisamchk} to modify the original datafile in case of duplicate keys @item -u or --unpack @code{myisampack} でパックされたテーブルファイルをアンパックします。 @end table @node myisamchk other options, myisamchk memory, myisamchk repair options, Table maintenance @subsubsection @code{myisamchk} の他のオプション Other actions that @code{myisamchk} can do, besides repair and check tables: @table @code @item -a or --analyze キーの分布(配置)を分析します。 This improves join performance by enabling the join optimiser to better choose in which order it should join the tables and which keys it should use: @code{myisamchk --describe --verbose table_name'} or using @code{SHOW KEYS} in MySQL. @item -d or --description テーブルに関するいくらかの情報を表示します @item -A or --set-auto-increment[=value] Force @code{AUTO_INCREMENT} to start at this or higher value. If no value is given, then sets the next @code{AUTO_INCREMENT} value to the highest used value for the auto key + 1. @item -S or --sort-index インデックスブロックのソート。 これは、アプリケーションでの ``read-next'' を速くします。 @item -R or --sort-records=# インデックスに従ってソート。 これはあなたのデータをよりよく配置し、このインデックスへの @code{SELECT}, @code{ORDER BY} オペレーションを速くします。 (この操作の最初のソートは非常に遅くなるかもしれません！) テーブルのインデックスの番号をみつけるには @code{SHOW INDEX} を使用しますが、 これは @code{myisamchk} がテーブルのインデックスを見つけるのと同じ順序で行います。 インデックス番号は 1 から始まります。 @end table @node myisamchk memory, Crash recovery, myisamchk other options, Table maintenance @subsubsection @code{myisamchk} メモリ使用 @cindex memory usage, myisamchk @code{myisamchk} を走らす上でメモリーの配分は重要です。 @code{myisamchk} は @code{-O} オプションで定義した以上のメモリは使用しません。 とても大きなファイルのたいして @code{myisamchk} をかけたいなら、 メモリーをどれくらい使用するかを最初に決めなくてはなりません。 デフォルトは固定で約 3M だけを使用します。大きな値を使用することで、 @code{myisamchk} をより速く動作できます。 例えば、32MBytesのRAMがあるなら、以下のように指定できます (他のオプションも指定して): @example shell> myisamchk -O sort=16M -O key=16M -O read=1M -O write=1M ... @end example @code{-O sort=16M} の使用は多くの場合おそらく十分でしょう。 しかし、@code{myisamchk} は @code{TMPDIR} 内に一時ファイルを使用します。 @code{TMPDIR} がメモリファイルシステムを指している場合は、簡単に out of memory エラーを得るでしょう。 If this happens, set @code{TMPDIR} to point at some directory with more space and restart @code{myisamchk}. When repairing, @code{myisamchk} will also need a lot of disk space: @itemize @bullet @item Double the size of the record file (the original one and a copy). This space is not needed if one does a repair with @code{--quick}, as in this case only the index file will be re-created. This space is needed on the same disk as the original record file! @item Space for the new index file that replaces the old one. The old index file is truncated at start, so one usually ignore this space. This space is needed on the same disk as the original index file! @item When using @code{--recover} or @code{--sort-recover} (but not when using @code{--safe-recover}), you will need space for a sort buffer for: @code{(largest_key + row_pointer_length)*number_of_rows * 2}. You can check the length of the keys and the row_pointer_length with @code{myisamchk -dv table}. This space is allocated on the temporary disk (specified by @code{TMPDIR} or @code{--tmpdir=#}). @end itemize If you have a problem with disk space during repair, you can try to use @code{--safe-recover} instead of @code{--recover}. @node Crash recovery, Check, myisamchk memory, Table maintenance @subsubsection Using @code{myisamchk} for Crash Recovery @cindex crash, recovery @cindex recovery, from crash If you run @code{mysqld} with @code{--skip-external-locking} (which is the default on some systems, like Linux), you can't reliably use @code{myisamchk} to check a table when @code{mysqld} is using the same table. If you can be sure that no one is accessing the tables through @code{mysqld} while you run @code{myisamchk}, you only have to do @code{mysqladmin flush-tables} before you start checking the tables. If you can't guarantee the above, then you must take down @code{mysqld} while you check the tables. If you run @code{myisamchk} while @code{mysqld} is updating the tables, you may get a warning that a table is corrupt even if it isn't. If you are not using @code{--skip-external-locking}, you can use @code{myisamchk} to check tables at any time. While you do this, all clients that try to update the table will wait until @code{myisamchk} is ready before continuing. If you use @code{myisamchk} to repair or optimise tables, you @strong{must} always ensure that the @code{mysqld} server is not using the table (this also applies if you are using @code{--skip-external-locking}). If you don't take down @code{mysqld} you should at least do a @code{mysqladmin flush-tables} before you run @code{myisamchk}. Your tables @strong{may be corrupted} if the server and @code{myisamchk} access the tables simultaneously. This chapter describes how to check for and deal with data corruption in MySQL databases. If your tables get corrupted frequently you should try to find the reason for this! @xref{Crashing}. The @code{MyISAM} table section contains reason for why a table could be corrupted. @xref{MyISAM table problems}. When performing crash recovery, it is important to understand that each table @code{tbl_name} in a database corresponds to three files in the database directory: @multitable @columnfractions .20 .30 @item @strong{File} @tab @strong{Purpose} @item @file{tbl_name.frm} @tab Table definition (form) file @item @file{tbl_name.MYD} @tab Datafile @item @file{tbl_name.MYI} @tab Index file @end multitable Each of these three file types is subject to corruption in various ways, but problems occur most often in datafiles and index files. @code{myisamchk} works by creating a copy of the @file{.MYD} (data) file row by row. It ends the repair stage by removing the old @file{.MYD} file and renaming the new file to the original file name. If you use @code{--quick}, @code{myisamchk} does not create a temporary @file{.MYD} file, but instead assumes that the @file{.MYD} file is correct and only generates a new index file without touching the @file{.MYD} file. This is safe, because @code{myisamchk} automatically detects if the @file{.MYD} file is corrupt and aborts the repair in this case. You can also give two @code{--quick} options to @code{myisamchk}. In this case, @code{myisamchk} does not abort on some errors (like duplicate key) but instead tries to resolve them by modifying the @file{.MYD} file. Normally the use of two @code{--quick} options is useful only if you have too little free disk space to perform a normal repair. In this case you should at least make a backup before running @code{myisamchk}. @node Check, Repair, Crash recovery, Table maintenance @subsubsection How to Check Tables for Errors @cindex checking, tables for errors @cindex tables, error checking @cindex errors, checking tables for To check a MyISAM table, use the following commands: @table @code @item myisamchk tbl_name This finds 99.99% of all errors. What it can't find is corruption that involves @strong{only} the datafile (which is very unusual). If you want to check a table, you should normally run @code{myisamchk} without options or with either the @code{-s} or @code{--silent} option. @item myisamchk -m tbl_name This finds 99.999% of all errors. It checks first all index entries for errors and then it reads through all rows. It calculates a checksum for all keys in the rows and verifies that they checksum matches the checksum for the keys in the index tree. @item myisamchk -e tbl_name This does a complete and thorough check of all data (@code{-e} means ``extended check''). It does a check-read of every key for each row to verify that they indeed point to the correct row. This may take a long time on a big table with many keys. @code{myisamchk} will normally stop after the first error it finds. If you want to obtain more information, you can add the @code{--verbose} (@code{-v}) option. This causes @code{myisamchk} to keep going, up through a maximum of 20 errors. In normal usage, a simple @code{myisamchk} (with no arguments other than the table name) is sufficient. @item myisamchk -e -i tbl_name Like the previous command, but the @code{-i} option tells @code{myisamchk} to print some informational statistics, too. @end table @node Repair, Optimisation, Check, Table maintenance @subsubsection テーブルの修復方法 @cindex tables, repairing @cindex repairing, tables In the following section we only talk about using @code{myisamchk} on @code{MyISAM} tables (extensions @file{.MYI} and @file{.MYD}). If you are using @code{ISAM} tables (extensions @file{.ISM} and @file{.ISD}), you should use @code{isamchk} instead. Starting with MySQL Version 3.23.14, you can repair MyISAM tables with the @code{REPAIR TABLE} command. @xref{REPAIR TABLE}. テーブル破壊の兆しとして、クエリが予期せず中断したり、以下のようなエラーが出たり します： @itemize @bullet @item @file{tbl_name.frm} is locked against change @item Can't find file @file{tbl_name.MYI} (Errcode: ###) @item Unexpected end of file @item Record file is crashed @item Got error ### from table handler To get more information about the error you can run @code{perror ###}. Here is the most common errors that indicates a problem with the table: @example shell> perror 126 127 132 134 135 136 141 144 145 126 = Index file is crashed / Wrong file format 127 = Record-file is crashed 132 = Old database file 134 = Record was already deleted (or record file crashed) 135 = No more room in record file 136 = No more room in index file 141 = Duplicate unique key or constraint on write or update 144 = Table is crashed and last repair failed 145 = Table was marked as crashed and should be repaired @end example Note that error 135, no more room in record file, is not an error that can be fixed by a simple repair. In this case you have to do: @example ALTER TABLE table MAX_ROWS=xxx AVG_ROW_LENGTH=yyy; @end example @end itemize この他の場合、あなたは自分のテーブルを修理しなければなりません。 @code{myisamchk} はほとんどの問題を見つけ出し修正します。 修復過程は以下で記述する最大4つの段階を踏みます。 これを始める前に、あなたはデータベースディレクトリに @code{cd} して テーブルファイルのパーミッションを確認すべきです。 これらファイルは @code{mysqld} を実行している UNIX ユーザーが読み込み可能 であるようにしてください(検査のするのにあなたにファイルのアクセス権も必要)。 もしファイルの変更をする必要があるならば、ファイルへの書き込み許可も必要です。 If you are using MySQL Version 3.23.16 and above, you can (and should) use the @code{CHECK} and @code{REPAIR} commands to check and repair @code{MyISAM} tables. @xref{CHECK TABLE}. @xref{REPAIR TABLE}. The manual section about table maintenance includes the options to @code{isamchk}/@code{myisamchk}. @xref{Table maintenance}. The following section is for the cases where the above command fails or if you want to use the extended features that @code{isamchk}/@code{myisamchk} provides. If you are going to repair a table from the command-line, you must first take down the @code{mysqld} server. Note that when you do @code{mysqladmin shutdown} on a remote server, the @code{mysqld} server will still be alive for a while after @code{mysqladmin} returns, until all queries are stopped and all keys have been flushed to disk. @noindent @strong{Stage 1: テーブルをチェックする} @code{myisamchk *.MYI} (時間がかかってもよいなら @code{myisamchk -e *.MYI}) を実行します。 @code{-s} (silent) オプションは不要な情報の出力をおさえます。 If the @code{mysqld} server is done you should use the --update option to tell @code{myisamchk} to mark the table as 'checked'. @code{myisamchk} がエラーを返した場合にだけ、テーブルを修復する必要があります。 この場合、Stage 2 へ進みます。 チェック時に奇妙なエラー(@code{out of memory} エラーのような) が起きた場合、 あるいは @code{myisamchk} が落ちた場合、Stage 3 に進んでください。 @noindent @strong{Stage 2: 簡単で安全な修復} Note: If you want repairing to go much faster, you should add: @code{-O sort_buffer=# -O key_buffer=#} (where # is about 1/4 of the available memory) to all @code{isamchk/myisamchk} commands. まず最初に @code{myisamchk -r -q tbl_name} を試みてください (@code{-r -q} は ``quick recovery mode''の意)。 これはデータファイルに触れないでインデックスファイルの修理を試みます。 もしデータファイルが全てとデータファイル中の正しい場所での削除リンクポイントを 含んでいるなら、これは動作してテーブルを修復します。 成功後、次のテーブルの修復に進んでください。 失敗した場合は、以下の手順で試みてください： @enumerate @item 続ける前にデータファイルをバックアップしてください。 @item @code{myisamchk -r tbl_name} を使用します(@code{-r} は ``recovery mode''の意)。 これは不正なレコードと削除されたレコードをデータファイルから消去し、 インデックスファイル(.MYI)を再構築します。 @item 上記が失敗した場合、@code{myisamchk --safe-recover tbl_name} を使用して下さい。 Safe recovery モードは古い方法を使用して修復します。 これは普通の修復モードでは行わない操作をいくつかもっています。(遅いですが) @end enumerate If you get weird errors when repairing (such as @code{out of memory} errors), or if @code{myisamchk} crashes, go to Stage 3. @noindent @strong{Stage 3: 難しい修復} インデックスファイル(.MYI)の最初の 16K ブロックが破壊された場合、 または不正な情報を含む場合、またはインデックスファイルがない場合にだけ、 本修復段階を経ます。 この場合、新しいインデックスファイルファイルを作成する必要があります。 次のようにしてください: @enumerate @item データファイルをどこか安全場所に移動します。 @item 新しい(空の)データとインデックスファイルを作るために、 テーブルディスクリプタファイルを使用します： @example shell> mysql db_name mysql> SET AUTOCOMMIT=1; mysql> TRUNCATE TABLE table_name; mysql> quit @end example If your SQL version doesn't have @code{TRUNCATE TABLE}, use @code{DELETE FROM table_name} instead. @item 古いデータファイルを新しく作ったデータファイルにコピーします。 (Don't just move the old file back onto the new file; you want to retain a copy in case something goes wrong.) @end enumerate Go back to Stage 2. @code{myisamchk -r -q} should work now. (This shouldn't be an endless loop.) As of @code{MySQL} 4.0.2 you can also use @code{REPAIR ... USE_FRM} which performs the whole procedure automatically. @noindent @strong{Stage 4: とても難しい修復} これは、ディスクリプタファイル(.frm)もクラッシュした場合にだけ発生します。 これは発生することはありません。なぜならディスクリプタファイルは テーブルが生成された後に書かれることはないからです。 @enumerate @item ディスクリプタファイルをバックアップからリストアして、Stage 3 に戻ってください。 インデックスファイルのリストアもできます。そして Stage 2 に戻ってください。 後者の場合、@code{myisamchk -r} で開始すべきです。 @item バックアップを持っていなくても、テーブルがどのように作成されたかを正確に知って いれば、他のデータベース内にテーブルのコピーを生成します。 新しいデータファイルを削除し、先ほど作ったデータベースの中の ディスクリプタファイルとインデックスファイルを、壊れたデータベース内に 移動します。これは新しいディスクリプタファイルとインデックスファイルを 与えることになりますが、データファイルはそのまま残っています。 Stage 2 に進み、インデックスファイルの修復を行ってください。 @end enumerate @node Optimisation, , Repair, Table maintenance @subsubsection テーブルの最適化 @cindex tables, optimising @cindex optimising, tables 断片化されたレコードの結合と、 レコードの削除と更新から生じる無駄なスペースの排除、 これら行うには、修復モード(recovery mode)で @code{myisamchk} を実行します： @example shell> myisamchk -r tbl_name @end example You can optimise a table in the same way using the SQL @code{OPTIMIZE TABLE} statement. @code{OPTIMIZE TABLE} does a repair of the table and a key analysis, and also sorts the index tree to give faster key lookups. There is also no possibility of unwanted interaction between a utility and the server, because the server does all the work when you use @code{OPTIMIZE TABLE}. @xref{OPTIMIZE TABLE}. @code{myisamchk} には、あなたがテーブルの性能を向上させるのに使用することができる 他の多くのオプションがあります: @itemize @item @code{-S}, @code{--sort-index} @item @code{-R index_num}, @code{--sort-records=index_num} @item @code{-a}, @code{--analyze} @end itemize For a full description of the option. @xref{myisamchk syntax}. @node Maintenance regimen, Table-info, Table maintenance, Disaster Prevention @subsection テーブルの保守体制の設定 @cindex maintaining, tables @cindex tables, maintenance regimen Starting with MySQL Version 3.23.13, you can check MyISAM tables with the @code{CHECK TABLE} command. @xref{CHECK TABLE}. You can repair tables with the @code{REPAIR TABLE} command. @xref{REPAIR TABLE}. 問題が発生するまで待つより、定期的にテーブルを検査する方がよりよい考えです。 保守目的には、@code{myisamchk -s} でテーブルを検査するのがよいでしょう。 @code{-s} オプション(short for @code{--silent}) はサイレントモードなので、 エラーが起きた場合にだけメッセージを出力します。 @tindex .pid (process ID) file サーバーを開始するときにテーブルを検査するのもよい考えです。 例えば、更新最中にマシンがリブートされたなら、全てのテーブルに関して その影響がないか検査する必要があります。（これは``expected crashed table''です） リブート後にもし古い @file{.pid} ファイル(プロセスID) があるならば、 24時間以内に変更されたテーブルに対して @code{myisamchk} を走らせて検査させるよう に、 @code{safe_mysqld} にテストを追加しても構いません。 (@file{.pid} ファイルは @code{mysqld} 起動時に作られ、通常修了時に消されます。 スタート時に @file{.pid} ファイルが存在するなら @code{mysqld} が異常終了したこと を示します。) 良いテストは、@file{.pid} ファイルの作成時間以降に変更された 全てのテーブルを検査するテストです。 通常のシステム運用中にもテーブルを検査すべきです。 MySQL AB では、週に一度、 @code{cron} を使用して重要なテーブルを検査し ています。 @file{crontab} ファイルには以下のように記述します： @example 35 0 * * 0 /path/to/myisamchk --fast --silent /path/to/datadir/*/*.MYI @end example これは壊れたテーブルの情報を出力しますので、必要とあらば検査、修復が行えるわけで す。 予想外の事故で壊れたテーブル(ハードウェアのトラブルが原因で崩壊)を除き、 2,3年間、テーブルは壊れたことはありません(これは本当に本当です)。 ので、一週間に一度のチェックでも十分です。 24時間以内に変更された全てのテーブルに対して、 @code{myisamchk -s} を毎晩実行する事を勧めます。 そうすれば、あなたは我々と同じぐらいに MySQL を 信頼することになります。 @cindex tables, defragment Normally you don't need to maintain MySQL tables that much. If you are changing tables with dynamic size rows (tables with @code{VARCHAR}, @code{BLOB} or @code{TEXT} columns) or have tables with many deleted rows you may want to from time to time (once a month?) defragment/reclaim space from the tables. You can do this by using @code{OPTIMIZE TABLE} on the tables in question or if you can take the @code{mysqld} server down for a while do: @example isamchk -r --silent --sort-index -O sort_buffer_size=16M */*.ISM myisamchk -r --silent --sort-index -O sort_buffer_size=16M */*.MYI @end example @node Table-info, , Maintenance regimen, Disaster Prevention @subsection テーブル情報取得 @cindex tables, information テーブルから詳細/統計を得るためには、次の方法を使用します。後でさらに詳細な情 報をいくつか説明します。 @itemize @bullet @item myisamchk -d tbl_name @code{myisamchk} を ``describe mode'' で実行し、テーブルの説明記述を作ります。 @code{--skip-external-locking} (ver.4.0.3未満では@code{--skip-locking}) を指定して MySQL サーバーを起動した場合、 @code{myisamchk} は myisamchk 実行中に更新されたテーブルについてエラーを報告します. しかし @code{myisamchk} は describe mode ではテーブルを変えないので、 データを破壊する危険性はありません。 @item myisamchk -d -v tbl_name @code{myisamchk} がしていることに関する、より多くの情報を作り出すには、 @code{-v} をつけて冗長モードで走らせるようにします。 @item myisamchk -eis tbl_name テーブルから最も重要な情報だけを示します。 テーブル全体を読まなければならないので、遅いです。 @item myisamchk -eiv tbl_name @code{-eis} と似ているが、何を行っているかを表示します。 @end itemize @cindex examples, @code{myisamchk} output @cindex @code{myisamchk}, example output @code{myisamchk -d} 出力の例: @example MyISAM file: company.MYI Record format: Fixed length Data records: 1403698 Deleted blocks: 0 Recordlength: 226 table description: Key Start Len Index Type 1 2 8 unique double 2 15 10 multip. text packed stripped 3 219 8 multip. double 4 63 10 multip. text packed stripped 5 167 2 multip. unsigned short 6 177 4 multip. unsigned long 7 155 4 multip. text 8 138 4 multip. unsigned long 9 177 4 multip. unsigned long 193 1 text @end example @code{myisamchk -d -v} 出力の例: @example MyISAM file: company Record format: Fixed length File-version: 1 Creation time: 1999-10-30 12:12:51 Recover time: 1999-10-31 19:13:01 Status: checked Data records: 1403698 Deleted blocks: 0 Datafile parts: 1403698 Deleted data: 0 Datafilepointer (bytes): 3 Keyfile pointer (bytes): 3 Max datafile length: 3791650815 Max keyfile length: 4294967294 Recordlength: 226 table description: Key Start Len Index Type Rec/key Root Blocksize 1 2 8 unique double 1 15845376 1024 2 15 10 multip. text packed stripped 2 25062400 1024 3 219 8 multip. double 73 40907776 1024 4 63 10 multip. text packed stripped 5 48097280 1024 5 167 2 multip. unsigned short 4840 55200768 1024 6 177 4 multip. unsigned long 1346 65145856 1024 7 155 4 multip. text 4995 75090944 1024 8 138 4 multip. unsigned long 87 85036032 1024 9 177 4 multip. unsigned long 178 96481280 1024 193 1 text @end example @code{myisamchk -eis} 出力の例: @example Checking MyISAM file: company Key: 1: Keyblocks used: 97% Packed: 0% Max levels: 4 Key: 2: Keyblocks used: 98% Packed: 50% Max levels: 4 Key: 3: Keyblocks used: 97% Packed: 0% Max levels: 4 Key: 4: Keyblocks used: 99% Packed: 60% Max levels: 3 Key: 5: Keyblocks used: 99% Packed: 0% Max levels: 3 Key: 6: Keyblocks used: 99% Packed: 0% Max levels: 3 Key: 7: Keyblocks used: 99% Packed: 0% Max levels: 3 Key: 8: Keyblocks used: 99% Packed: 0% Max levels: 3 Key: 9: Keyblocks used: 98% Packed: 0% Max levels: 4 Total: Keyblocks used: 98% Packed: 17% Records: 1403698 M.recordlength: 226 Packed: 0% Recordspace used: 100% Empty space: 0% Blocks/Record: 1.00 Record blocks: 1403698 Delete blocks: 0 Recorddata: 317235748 Deleted data: 0 Lost space: 0 Linkdata: 0 User time 1626.51, System time 232.36 Maximum resident set size 0, Integral resident set size 0 Non physical pagefaults 0, Physical pagefaults 627, Swaps 0 Blocks in 0 out 0, Messages in 0 out 0, Signals 0 Voluntary context switches 639, Involuntary context switches 28966 @end example @code{myisamchk -eiv} 出力の例: @example Checking MyISAM file: company Data records: 1403698 Deleted blocks: 0 - check file-size - check delete-chain block_size 1024: index 1: index 2: index 3: index 4: index 5: index 6: index 7: index 8: index 9: No recordlinks - check index reference - check data record references index: 1 Key: 1: Keyblocks used: 97% Packed: 0% Max levels: 4 - check data record references index: 2 Key: 2: Keyblocks used: 98% Packed: 50% Max levels: 4 - check data record references index: 3 Key: 3: Keyblocks used: 97% Packed: 0% Max levels: 4 - check data record references index: 4 Key: 4: Keyblocks used: 99% Packed: 60% Max levels: 3 - check data record references index: 5 Key: 5: Keyblocks used: 99% Packed: 0% Max levels: 3 - check data record references index: 6 Key: 6: Keyblocks used: 99% Packed: 0% Max levels: 3 - check data record references index: 7 Key: 7: Keyblocks used: 99% Packed: 0% Max levels: 3 - check data record references index: 8 Key: 8: Keyblocks used: 99% Packed: 0% Max levels: 3 - check data record references index: 9 Key: 9: Keyblocks used: 98% Packed: 0% Max levels: 4 Total: Keyblocks used: 9% Packed: 17% - check records and index references [LOTS OF ROW NUMBERS DELETED] Records: 1403698 M.recordlength: 226 Packed: 0% Recordspace used: 100% Empty space: 0% Blocks/Record: 1.00 Record blocks: 1403698 Delete blocks: 0 Recorddata: 317235748 Deleted data: 0 Lost space: 0 Linkdata: 0 User time 1639.63, System time 251.61 Maximum resident set size 0, Integral resident set size 0 Non physical pagefaults 0, Physical pagefaults 10580, Swaps 0 Blocks in 4 out 0, Messages in 0 out 0, Signals 0 Voluntary context switches 10604, Involuntary context switches 122798 @end example 上で使用されたテーブルのデータファイルサイズをここに示します: @example -rw-rw-r-- 1 monty tcx 317235748 Jan 12 17:30 company.MYD -rw-rw-r-- 1 davida tcx 96482304 Jan 12 18:35 company.MYM @end example @code{myisamchk} が生成する情報の説明を以下に示します。 ``keyfile'' はインデックスファイルです。 ``Record'' と ``row'' は同義です。 @itemize @bullet @item ISAM file ISAM (index) ファイルの名前 @item Isam-version ISAM 形式のバージョン。現在は常に 2 @item Creation time データファイルが生成された時。 @item Recover time インデックス/データファイルが最後に再構築された時。 @item Data records テーブルのレコード数。 @item Deleted blocks 予約された領域をまだ持っている削除ブロック数。 このスペースを最小にするために自分のテーブルを最適化することができます。 @xref{Optimisation}. @item Data file: Parts 動的なレコード形式にいくつのデータブロックがあるかを表示します。 分割なしで最適化されたテーブルでは @code{Data records} と同じです。 @item Deleted data 改善されていない削除データのバイト数。 このスペースを最小にするために自分のテーブルを最適化することができます。 @xref{Optimisation}. @item Data file pointer データファイルポインタの大きさ(バイト数)。これは普通 2, 3, 4 または 5 バ イトです。多くのテーブルは 2 バイトで管理されますが、これはまだ MySQL から制御できません。固定テーブルではこれはレコードアドレ スです。動的テーブルではこれはバイトアドレスです。 @item Keyfile pointer データファイルポインタのバイト数。これは普通 1, 2 または 3 バイトです。 多くのテーブルは 2 バイトで管理されますが、これは MySQL では自動的に 計算されます。これは常にブロックアドレスです。 @item Max datafile length テーブルのデータファイル (@code{.MYD} ファイル) が獲得できる長さ (バイト数)。 @item Max keyfile length テーブルのキーファイル (@code{.MYI} ファイル) が獲得できる長さ (バイト数)。 @item Recordlength テーブルの各レコードが使用する領域の大きさ(バイト数)。 @item Record format 各テーブルのレコードの形式。この例では @code{Fixed length} を使用します。 他の値で可能な物は@code{圧縮}、@code{パック}します。 @item table description テーブル内の全てのキーのリスト。各キーについて、いくつかの低レベル情報が提供さ れます: @itemize @minus @item Key キー番号。 @item Start インデックス部が開始するレコード内の位置。 @item Len インデックス部の長さ。 パックされた数値では、これは常に項目の完全な長さになります。 文字型においては、文字型の項目の頭の部分にインデックスがつく事になりますので、 インデックス項目の最大長さよりもこの値は短くなるでしょう。 @item Index @code{unique} or @code{multip.} (multiple). このインデックス内では1つの値が複数 回存在し得ます。 @item Type このインデックス部が持つデータ型。 これは NISAM データ型で、 @code{packed}, @code{stripped} か @code{empty} オプションを持ちます。 @item Root ルートインデックスブロックのアドレス。 @item Blocksize 各インデックスブロックのサイズ。これはデフォルトでは 1024 ですが、コンパ イル時に変更できます。 @item Rec/key これはオプティマイザによって使用される統計値です。このキーの値ごとのレコー ド数を知らせます。ユニークキーは常に1の値を持ちます。これはテーブルがロードさ れた(または大きく変更された)後に @code{myisamchk -a} で更新されます。これ が全く更新されない場合はデフォルト値の 30 が与えられます。 @end itemize @item 上の最初の例では、9番目のキーは2つの部分をもったマルチパートキーです。 @item Keyblocks used 使用されたキーブロックのパーセンテージ。このテーブルは @code{myisamchk} で再配置 されるため、値はとても高くなります (理論的な最大にとても近くなります)。 @item Packed MySQL は一般の接尾辞でキーのパックを試みます。これは @code{CHAR}/@code{VARCHAR}/@code{DECIMAL} キーでだけ使用できます。名前の ような長い文字列では、これは使用領域を顕著に減らします。上の三番目の例では4番目 のキーが10文字長で、領域の60%の減少を得ます。 @item Max levels このキーの Btree の深さ。長いキーを持つ大きなテーブルは高い値を得ます。 @item Records テーブルが持っているレコード数。 @item M.recordlength 平均のレコード長。固定テーブルでは、これは正確なレコード長となります。 @item Packed MySQL は文字列の最後から空白を除きます。これによって節約された パーセンテージを @code{Packed} は示します。 @item Recordspace used データファイルが使用されたパーセンテージ。 @item Empty space データファイルが使用されていないパーセンテージ。 @item Blocks/Record レコード毎のブロック数 (断片化レコードの構成数)。 これは固定形式テーブルでは常に1です。この値は可能な限 り 1.0 に留まります。これが大きすぎる場合は、@code{myisamchk} でテーブルを再配置 できます。 @xref{Optimisation}. @item Recordblocks 使用されたブロック (links) 数。固定型式ではこれはレコード数と同じです。 @item Deleteblocks 削除されたブロック (links) 数。 @item Recorddata データファイル中にある実際のユーザデータのバイト数。 @item Deleted data データファイル中にある削除された(unused)データのバイト数。 @item Lost space レコードがより短い長さに更新された場合、いくつかの領域が失われます。これ はそのような消失の全ての合計(バイト)です。 @item Linkdata 動的形式の使用時、ブロックはポインタ(4〜7バイト)にリンクされます。@code{Linkdata}は そのポインタの全ての合計です。 @end itemize テーブルが @code{pack_isam} で圧縮されているなら、@code{myisamchk -d} は それぞれのテーブルコラムに関する追加情報を出力します。 @ref{myisampack, ,@code{myisampack}}. を参照してください。 この情報例と説明記述の意味があります。 @node Database Administration, Localisation, Disaster Prevention, MySQL Database Administration @section Database Administration Language Reference @menu * OPTIMIZE TABLE:: @code{OPTIMIZE TABLE} Syntax * ANALYZE TABLE:: @code{ANALYZE TABLE} Syntax * FLUSH:: @code{FLUSH} Syntax * RESET:: @code{RESET} Syntax * KILL:: @code{KILL} Syntax * SHOW:: @code{SHOW} Syntax @end menu @node OPTIMIZE TABLE, ANALYZE TABLE, Database Administration, Database Administration @subsection @code{OPTIMIZE TABLE} 構文 @findex OPTIMIZE TABLE @cindex tables, defragmenting @cindex tables, fragmentation @example OPTIMIZE TABLE tbl_name[,tbl_name]... @end example @code{OPTIMIZE TABLE}は、テーブルの大部分を削除したり、可変長となっているテーブ ル(@code{VARCHAR}、@code{BLOB}もしくは@code{TEXT}フィールドを持つテーブル)に多く の変更を加えた場合に使用すべきです。 削除されたレコードはリンクリストで維持され、次の@code{INSERT}操作は、古いレコー ド位置を再利用します。 未使用領域を再生するために@code{OPTIMIZE TABLE}を使用することができます。 今のところ、@code{OPTIMIZE TABLE} は @code{MyISAM} と @code{BDB} テーブ ル上でだけ動作します。@code{BDB} テーブルでは、@code{OPTIMIZE TABLE} が現 在 @code{ANALYZE TABLE} にマップされます。 @xref{ANALYZE TABLE, , @code{ANALYZE TABLE}}. @code{--skip-new} または @code{--safe-mode} で @code{mysqld} を起動するこ とで、他のテーブル型で @code{OPTIMIZE TABLE} を動作するようにできます。しかし、こ の場合 @code{OPTIMIZE TABLE} は @code{ALTER TABLE} にマップされるだけです。 @code{OPTIMIZE TABLE} は次の方法で動作します: @itemize @bullet @item テーブルが削除されているかレコードが分割する場合、テーブルを修復します。 @item インデックスページがソートされていない場合、ソートします。 @item 統計が更新されていない（そしてインデックスをソートすることで修復が行なわれ なかった）場合、それを更新します。 @end itemize @code{MyISAM} テーブルの @code{OPTIMIZE TABLE} はテーブル上で @code{myisamchk --quick --check-changed-tables --sort-index --analyze} を 実行することと同等です。 注意: テーブルは @code{OPTIMIZE TABLE} 実行中はロックされます！ @node ANALYZE TABLE, FLUSH, OPTIMIZE TABLE, Database Administration @subsection @code{ANALYZE TABLE} Syntax @findex ANALYZE TABLE @example ANALYZE TABLE tbl_name[,tbl_name...] @end example Analyse and store the key distribution for the table. During the analysis, the table is locked with a read lock. This works on @code{MyISAM} and @code{BDB} tables. This is equivalent to running @code{myisamchk -a} on the table. MySQL uses the stored key distribution to decide in which order tables should be joined when one does a join on something else than a constant. The command returns a table with the following columns: @multitable @columnfractions .15 .40 @item @strong{Column} @tab @strong{Value} @item Table @tab Table name @item Op @tab Always ``analyze'' @item Msg_type @tab One of @code{status}, @code{error}, @code{info} or @code{warning}. @item Msg_text @tab The message. @end multitable You can check the stored key distribution with the @code{SHOW INDEX} command. @xref{SHOW DATABASE INFO}. If the table hasn't changed since the last @code{ANALYZE TABLE} command, the table will not be analysed again. @node FLUSH, RESET, ANALYZE TABLE, Database Administration @subsection @code{FLUSH} 構文 @findex FLUSH @cindex @code{mysqladmin} @cindex clearing, caches @cindex caches, clearing @example FLUSH flush_option [,flush_option] ... @end example @code{FLUSH} コマンドで MySQL が使用している内部キャッシュの いくつかをきれいに消すことができます。 @code{FLUSH} を実行するには、 @code{RELOAD} 権限がなければなりません。 @code{flush_option} には以下の内一つが指定できます： @multitable @columnfractions .25 .75 @item @strong{Option} @tab @strong{Description} @item @code{HOSTS} @tab ホストキャッシュテーブルを空にします。あなたのホストの IP アドレスを変えたり、@code{Host ... is blocked} というエラーメッセージが 出る場合はホストテーブルキャッシュを一度空にしなくてはなりません。 指定したホストに対して @code{max_connect_errors} 以上の接続エラーが出る場合、 MySQL は何か起きたと推定し、そのホストからのいかなる接続要求も 拒否します。ホストテーブルキャッシュの消去は、再び接続を許すようにします。 @xref{Blocked host}. @code{mysqld} を @code{-O max_connect_errors=999999999} 開始し、 このエラーメッセージを回避できます @item @code{DES_KEY_FILE} @tab Reloads the DES keys from the file that was specified with the @code{--des-key-file} option at server startup time. @item @code{LOGS} @tab 標準のログファイルと更新ログファイルを 一度閉じて再び開きます。 もし更新ログファイルを拡張子無しで指定している場合、新しい更新ログファイルの 拡張子の番号は、一つ前のファイルより 1 増やした数になります。 ファイル名に拡張を使用した場合、MySQL は更新ログファイルを閉じて開きます。 @xref{Update log}. This is the same thing as sending the @code{SIGHUP} signal to the @code{mysqld} server. @item @code{PRIVILEGES} @tab @code{mysql} データベースの許可テーブルから、権限情報を再読込します。 @item @code{QUERY CACHE} @tab Defragment the query cache to better utilise its memory. This command will not remove any queries from the cache, unlike @code{RESET QUERY CACHE}. @item @code{TABLES} @tab 全ての開いているテーブルを閉じます。使用中のテーブルに も close を強制します。 This also flushes the query cache. @item @code{[TABLE | TABLES] tbl_name [,tbl_name...]} @tab Flushes only the given tables. @item @code{TABLES WITH READ LOCK} @tab 全ての開いているテーブルを閉じ、 @code{UNLOCK TABLES} を実行するまで全てのテーブルを read lock でロックします。 This is very convenient way to get backups if you have a filesystem, like Veritas,that can take snapshots in time. @item @code{STATUS} @tab ほとんどのステータス変数を 0 にします。 This is something one should only use when debugging a query. @item @code{USER_RESOURCES} @tab Resets all user resources to zero. This will enable blocked users to login again. @xref{User resources}. @end multitable 上に示したコマンドは、@code{mysqladmin} を使用しても実行できます。 @code{mysqladmin} の引数はそれぞれ、@code{flush-hosts}, @code{flush-logs}, @code{reload}, @code{flush-tables} となります。 Take also a look at the @code{RESET} command used with replication. @xref{RESET, , @code{RESET}}. @node RESET, KILL, FLUSH, Database Administration @subsection @code{RESET} 構文 @example RESET reset_option [,reset_option] ... @end example The @code{RESET} command is used to clear things. It also acts as an stronger version of the @code{FLUSH} command. @xref{FLUSH, , @code{FLUSH}}. To execute @code{RESET}, you must have the @code{RELOAD} privilege. @multitable @columnfractions .25 .75 @item @strong{Option} @tab @strong{Description} @item @code{MASTER} @tab Deletes all binary logs listed in the index file, resetting the binlog index file to be empty. In pre-3.23.26 versions, @code{FLUSH MASTER} (Master) @item @code{SLAVE} @tab Makes the slave forget its replication position in the master logs. In pre 3.23.26 versions the command was called @code{FLUSH SLAVE}(Slave) @item @code{QUERY CACHE} @tab Removes all query results from the query cache. @end multitable @node KILL, SHOW, RESET, Database Administration @subsection @code{KILL} 構文 @findex KILL @cindex @code{mysqladmin} @example KILL thread_id @end example @code{thread_id} には、@code{mysqld} に接続して走っているスレッドの ID を 空白で区切って指定します。 @code{SHOW PROCESSLIST} コマンドで走っているスレッドを知ることができ、 @code{KILL thread_id} コマンドでスレッドを KILL できます。 If you have the @code{PROCESS} privilege, you can see all threads. If you have the @code{SUPER} privilege, you can kill all threads. Otherwise, you can only see and kill your own threads. (version 4.0.2未満では： もし @code{PROCESS} 権限があるなら、全てのスレッドを確認し、KILL 出来ます。 そうでなければ、自分のスレッドだけを確認し、KILL する事ができます。) @code{mysqladmin processlist} と @code{mysqladmin kill} をスレッドの 検査と KILL に使用できます。 When you do a @code{KILL}, a thread-specific @code{kill flag} is set for the thread. In most cases it may take some time for the thread to die as the kill flag is only checked at specific intervals. @itemize @bullet @item In @code{SELECT}, @code{ORDER BY} and @code{GROUP BY} loops, the flag is checked after reading a block of rows. If the kill flag is set, the statement is aborted. @item When doing an @code{ALTER TABLE} the kill flag is checked before each block of rows are read from the original table. If the kill flag was set the command is aborted and the temporary table is deleted. @item When doing an @code{UPDATE} or @code{DELETE}, the kill flag is checked after each block read and after each updated or deleted row. If the kill flag is set, the statement is aborted. Note that if you are not using transactions, the changes will not be rolled back! @item @code{GET_LOCK()} will abort with @code{NULL}. @item An @code{INSERT DELAYED} thread will quickly flush all rows it has in memory and die. @item If the thread is in the table lock handler (state: @code{Locked}), the table lock will be quickly aborted. @item If the thread is waiting for free disk space in a @code{write} call, the write is aborted with an disk full error message. @end itemize @node SHOW, , KILL, Database Administration @subsection @code{SHOW} 構文 @c FIX more index hits needed @findex SHOW DATABASE INFO @findex SHOW DATABASES @findex SHOW TABLES @findex SHOW COLUMNS @findex SHOW FIELDS @findex SHOW INDEX @findex SHOW KEYS @findex SHOW STATUS @findex SHOW VARIABLES @findex SHOW PROCESSLIST @findex SHOW TABLE STATUS @findex SHOW GRANTS @findex SHOW CREATE TABLE @findex SHOW MASTER STATUS @findex SHOW MASTER LOGS @findex SHOW SLAVE STATUS @findex SHOW WARNINGS @findex SHOW TABLE TYPES @example SHOW DATABASES [LIKE wild] or SHOW [OPEN] TABLES [FROM db_name] [LIKE wild] or SHOW [FULL] COLUMNS FROM tbl_name [FROM db_name] [LIKE wild] or SHOW INDEX FROM tbl_name [FROM db_name] or SHOW TABLE STATUS [FROM db_name] [LIKE wild] or SHOW STATUS [LIKE wild] or SHOW VARIABLES [LIKE wild] or SHOW LOGS or SHOW [FULL] PROCESSLIST or SHOW GRANTS FOR user or SHOW CREATE TABLE table_name or SHOW MASTER STATUS or SHOW MASTER LOGS or SHOW SLAVE STATUS or SHOW WARNINGS [LIMIT #] or SHOW ERRORS [LIMIT #] or SHOW TABLE TYPES @end example @code{SHOW} はデータベース、テーブル、フィールド、サーバーについての情報を与えます。 @code{LIKE wild} が使用された場合、@code{wild} 文字列は通常の SQL ワイルドカード (@samp{%} と @samp{_}) です。 @menu * SHOW DATABASE INFO:: Retrieving information about Database, Tables, Columns, and Indexes * SHOW TABLE STATUS:: @code{SHOW TABLE STATUS} * SHOW STATUS:: @code{SHOW STATUS} * SHOW VARIABLES:: @code{SHOW VARIABLES} * SHOW LOGS:: @code{SHOW LOGS} * SHOW PROCESSLIST:: @code{SHOW PROCESSLIST} * SHOW GRANTS:: @code{SHOW GRANTS} * SHOW CREATE TABLE:: @code{SHOW CREATE TABLE} * SHOW WARNINGS:: @code{SHOW WARNINGS | ERRORS} * SHOW TABLE TYPES:: @code{SHOW TABLE TYPES} * SHOW PRIVILEGES:: @code{SHOW PRIVILEGES} @end menu @node SHOW DATABASE INFO, SHOW TABLE STATUS, SHOW, SHOW @subsubsection Retrieving information about Database, Tables, Columns, and Indexes @cindex displaying, information, @code{SHOW} @code{tbl_name FROM db_name} の代わりに、@code{db_name.tbl_name} が使用できます。 これら二つは同じです： @example mysql> SHOW INDEX FROM mytable FROM mydb; mysql> SHOW INDEX FROM mydb.mytable; @end example @code{SHOW DATABASES} は MySQL サーバー上のデータベースを示します。 @code{mysqlshow} コマンドでも同じ情報が得られます。 @code{SHOW TABLES} は指定されたデータベースのテーブルを一覧表示します。 @code{mysqlshow db_name} コマンドでも同じ情報が得られます。 In version 4.0.2 you will only see those databases for which you have some kind of privilege, if you don't have the global @code{SHOW DATABASES} privilege. @strong{Note}: もしユーザーにテーブルに対する権限が無い場合、 テーブルは @code{SHOW TABLES} や @code{mysqlshow db_name} の要求で 表示されません。 @code{SHOW OPEN TABLES} はテーブルキャッシュに現在オープン去れているテーブ ルを一覧表示します。@xref{Table cache}. @code{Comment} フィールドはテーブ ルが何回 @code{cached} と @code{in_use} になったかを知らせます。 @code{SHOW COLUMNS} は与えられたテーブルのフィールドを表示します。 @code{FULL} オプションを指定した場合、各フィールドに持つ権限も得られます。 もしそのフィールドの型が、あなたが @code{CREATE TABLE} 構文実行時に与えたものと 違う場合は、 MySQL は、フィールドの型をときおり変更することが あることに注意してください。 @xref{Silent column changes}. @code{DESCRIBE} 文は @code{SHOW COLUMNS} と似たような情報を提供します。 @xref{DESCRIBE, , @code{DESCRIBE}}. @code{SHOW FIELDS} は @code{SHOW COLUMNS} の別名として使用され、 @code{SHOW KEYS} は @code{SHOW INDEX} の別名として使用されます。 テーブルのフィールドやインデックスは @code{mysqlshow db_name tbl_name} か @code{mysqlshow -k db_name tbl_name} でも見れます。 @code{SHOW INDEX} は ODBC でいう @code{SQLStatistics} に近い形式で、インデックスの情報を表示します。 以下の項目が返ります： @multitable @columnfractions .15 .55 @item @strong{Column} @tab @strong{意味} @item @code{Table} @tab テーブル名 @item @code{Non_unique} @tab インデックスが重複を含まないなら 0 @item @code{Key_name} @tab インデックス名 @item @code{Seq_in_index} @tab インデックスの項目番号。1 から始まります。 @item @code{Column_name} @tab フィールド名。 @item @code{Collation} @tab どのようにこのフィールドがインデックス中で ソートされるか. MySQL ではこれは @code{A} (Ascending) か @code{NULL} (Not sorted) に なります。 @item @code{Cardinality} @tab インデックス中のユニークな値の数。 これは @code{isamchk -a} の実行で更新されます。 @item @code{Sub_part} @tab もしこのフィールドがインデックスに一部分だけ使用 している場合、そのインデックスに使用しているキャラクター数をしめす。 もしキー全 体がインデックスされているなら @code{NULL} 。 @item @code{Null} @tab Contains 'YES' if the column may contain @code{NULL}. @item @code{Index_type} @tab Index method used. @item @code{Comment} @tab Various remarks. For now, it tells in MySQL < 4.0.2 whether index is @code{FULLTEXT} or not. @end multitable Note that as the @code{Cardinality} is counted based on statistics stored as integers, it's not necessarily accurate for small tables. The @code{Null} and @code{Index_type} columns were added in MySQL 4.0.2. @node SHOW TABLE STATUS, SHOW STATUS, SHOW DATABASE INFO, SHOW @subsubsection @code{SHOW TABLE STATUS} @cindex displaying, table status @cindex tables, displaying status @cindex status, tables @example SHOW TABLE STATUS [FROM db_name] [LIKE wild] @end example @code{SHOW TABLE STATUS} (バージョン 3.23 の新機能) は @code{SHOW STATUS} のようですが、それぞれのテーブルについてより多くの情報を提供します。 @code{mysqlshow --status db_name} コマンドを実行しても同じものが得られます。 以下の項目が返ってきます： @multitable @columnfractions .20 .70 @item @strong{項目} @tab @strong{意味} @item @code{Name} @tab テーブル名 @item @code{Type} @tab テーブルの種類. @xref{Table types}. @item @code{Row_format} @tab レコードの保存形式 (Fixed, Dynamic, or Compressed). @item @code{Rows} @tab レコード数. @item @code{Avg_row_length} @tab レコードの平均長. @item @code{Data_length} @tab データファイルの大きさ. @item @code{Max_data_length} @tab データファイルの最大長. @item @code{Index_length} @tab インデックスファイルの大きさ. @item @code{Data_free} @tab 割り当てられたが使用されていないバイト数. @item @code{Auto_increment} @tab 次の autoincrement 値. @item @code{Create_time} @tab テーブル作成時刻. @item @code{Update_time} @tab 一番最後にデータファイルが更新された時刻. @item @code{Check_time} @tab 一番最後にテーブルがチェックされた時刻. @item @code{Create_options} @tab @code{CREATE TABLE} で使用された拡張オプション @item @code{Comment} @tab テーブル作成時につけられたコメント (あるいは、なぜこの テーブルに MySQL がアクセスできないかのいくつかの情報). @end multitable @code{InnoDB} tables will report the free space in the tablespace in the table comment. @node SHOW STATUS, SHOW VARIABLES, SHOW TABLE STATUS, SHOW @subsubsection @code{SHOW STATUS} @cindex @code{mysqladmin} @code{SHOW STATUS} は @code{mysqladmin extended-status} と同様に、 サーバからのステータス情報を与えます。出力は次とは異なるかもしれません: @example +--------------------------+------------+ | Variable_name | Value | +--------------------------+------------+ | Aborted_clients | 0 | | Aborted_connects | 0 | | Bytes_received | 155372598 | | Bytes_sent | 1176560426 | | Connections | 30023 | | Created_tmp_disk_tables | 0 | | Created_tmp_tables | 8340 | | Created_tmp_files | 60 | | Delayed_insert_threads | 0 | | Delayed_writes | 0 | | Delayed_errors | 0 | | Flush_commands | 1 | | Handler_delete | 462604 | | Handler_read_first | 105881 | | Handler_read_key | 27820558 | | Handler_read_next | 390681754 | | Handler_read_prev | 6022500 | | Handler_read_rnd | 30546748 | | Handler_read_rnd_next | 246216530 | | Handler_update | 16945404 | | Handler_write | 60356676 | | Key_blocks_used | 14955 | | Key_read_requests | 96854827 | | Key_reads | 162040 | | Key_write_requests | 7589728 | | Key_writes | 3813196 | | Max_used_connections | 0 | | Not_flushed_key_blocks | 0 | | Not_flushed_delayed_rows | 0 | | Open_tables | 1 | | Open_files | 2 | | Open_streams | 0 | | Opened_tables | 44600 | | Questions | 2026873 | | Select_full_join | 0 | | Select_full_range_join | 0 | | Select_range | 99646 | | Select_range_check | 0 | | Select_scan | 30802 | | Slave_running | OFF | | Slave_open_temp_tables | 0 | | Slow_launch_threads | 0 | | Slow_queries | 0 | | Sort_merge_passes | 30 | | Sort_range | 500 | | Sort_rows | 30296250 | | Sort_scan | 4650 | | Table_locks_immediate | 1920382 | | Table_locks_waited | 0 | | Threads_cached | 0 | | Threads_created | 30022 | | Threads_connected | 1 | | Threads_running | 1 | | Uptime | 80380 | +--------------------------+------------+ @end example @cindex variables, status 上に示したステータス変数は以下に示すの意味を持ちます： @multitable @columnfractions .30 .70 @item @strong{Variable} @tab @strong{Meaning} @item @code{Aborted_clients} @tab クライアントが接続を閉じる前に死んでしまったために中断されたコネクション数。 @xref{Communication errors}. @item @code{Aborted_connects} @tab MySQL サーバーに接続を試みて失敗した数。 @xref{Communication errors}. @item @code{Bytes_received} @tab クライアントから受信したバイト数 @item @code{Bytes_sent} @tab クライアントに送信したバイト数 @item @code{Com_xxx} @tab Number of times each xxx command has been executed. @item @code{Connections} @tab サーバーに接続を試みた数 @item @code{Created_tmp_disk_tables} @tab ステートメント実行中に暗黙のうちに作成されたメモり内にある一時テーブルの数 @item @code{Created_tmp_tables} @tab Number of implicit temporary tables in memory created while executing statements. @item @code{Created_tmp_files} @tab How many temporary files @code{mysqld} has created. @item @code{Delayed_insert_threads} @tab Number of delayed insert handler threads in use. @item @code{Delayed_writes} @tab Number of rows written with @code{INSERT DELAYED}. @item @code{Delayed_errors} @tab Number of rows written with @code{INSERT DELAYED} for which some error occurred (probably @code{duplicate key}). @item @code{Flush_commands} @tab @code{FLUSH} コマンドの実行回数 @item @code{Handler_commit} @tab Number of internal @code{COMMIT} commands. @item @code{Handler_delete} @tab Number of times a row was deleted from a table. @item @code{Handler_read_first} @tab Number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans, for example, @code{SELECT col1 FROM foo}, assuming that col1 is indexed. @item @code{Handler_read_key} @tab Number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed. @item @code{Handler_read_next} @tab Number of requests to read next row in key order. This will be incremented if you are querying an index column with a range constraint. This also will be incremented if you are doing an index scan. @item @code{Handler_read_prev} @tab Number of requests to read previous row in key order. This is mainly used to optimise @code{ORDER BY ... DESC}. @item @code{Handler_read_rnd} @tab Number of requests to read a row based on a fixed position. This will be high if you are doing a lot of queries that require sorting of the result. @item @code{Handler_read_rnd_next} @tab Number of requests to read the next row in the datafile. This will be high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have. @item @code{Handler_rollback} @tab Number of internal @code{ROLLBACK} commands. @item @code{Handler_update} @tab Number of requests to update a row in a table. @item @code{Handler_write} @tab Number of requests to insert a row in a table. @item @code{Key_blocks_used} @tab The number of used blocks in the key cache. @item @code{Key_read_requests} @tab The number of requests to read a key block from the cache. @item @code{Key_reads} @tab The number of physical reads of a key block from disk. @item @code{Key_write_requests} @tab The number of requests to write a key block to the cache. @item @code{Key_writes} @tab The number of physical writes of a key block to disk. @item @code{Max_used_connections} @tab The maximum number of connections in use simultaneously. @item @code{Not_flushed_key_blocks} @tab Keys blocks in the key cache that has changed but hasn't yet been flushed to disk. @item @code{Not_flushed_delayed_rows} @tab Number of rows waiting to be written in @code{INSERT DELAY} queues. @item @code{Open_tables} @tab オープンされているテーブル数 @item @code{Open_files} @tab Number of files that are open. @item @code{Open_streams} @tab Number of streams that are open (used mainly for logging). @item @code{Opened_tables} @tab Number of tables that have been opened. @item @code{Rpl_status} @tab Status of failsafe replication. (Not yet in use). @item @code{Select_full_join} @tab Number of joins without keys (If this is 0, you should carefully check the index of your tables). @item @code{Select_full_range_join} @tab Number of joins where we used a range search on reference table. @item @code{Select_range} @tab Number of joins where we used ranges on the first table. (It's normally not critical even if this is big.) @item @code{Select_scan} @tab Number of joins where we did a full scan of the first table. @item @code{Select_range_check} @tab Number of joins without keys where we check for key usage after each row (If this is 0, you should carefully check the index of your tables). @item @code{Questions} @tab サーバーに送られたクエリの数 @item @code{Slave_open_temp_tables} @tab Number of temporary tables currently open by the slave thread @item @code{Slave_running} @tab Is @code{ON} if this is a slave that is connected to a master. @item @code{Slow_launch_threads} @tab Number of threads that have taken more than @code{slow_launch_time} to create. @item @code{Slow_queries} @tab @code{long_query_time} 以上に時間のかかったクエリの数. @xref{Slow query log}. @item @code{Sort_merge_passes} @tab Number of merges passes the sort algoritm have had to do. If this value is large you should consider increasing @code{sort_buffer}. @item @code{Sort_range} @tab Number of sorts that where done with ranges. @item @code{Sort_rows} @tab Number of sorted rows. @item @code{Sort_scan} @tab Number of sorts that where done by scanning the table. @item @code{ssl_xxx} @tab Variables used by SSL; Not yet implemented. @item @code{Table_locks_immediate} @tab Number of times a table lock was acquired immediately. Available after 3.23.33. @item @code{Table_locks_waited} @tab Number of times a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimise your queries, and then either split your table(s) or use replication. Available after 3.23.33. @item @code{Threads_cached} @tab Number of threads in the thread cache. @item @code{Threads_connected} @tab 現在開いている接続数 @item @code{Threads_created} @tab Number of threads created to handle connections. @item @code{Threads_running} @tab スリープ状態になっていないスレッドの数 @item @code{Uptime} @tab サーバーが走っている秒数 @end multitable 上についてのいくつかコメント： @itemize @bullet @item もし @code{Opened_tables} が大きければ、 @code{table_cache} 変数が小さすぎる のでしょう。 @item もし @code{Key_reads} が大きければ、 @code{key_buffer_size} が少なすぎるでしょう。 @strong{キャッシュ ミス レート} は @code{Key_reads}/@code{Key_read_requests} で計算できます。 @item If @code{Handler_read_rnd} is big, then you probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly. @item If @code{Threads_created} is big, you may want to increase the @code{thread_cache_size} variable. The cache hit rate can be calculated with @code{Threads_created}/@code{Connections}. @item If @code{Created_tmp_disk_tables} is big, you may want to increase the @code{tmp_table_size} variable to get the temporary tables memory-based instead of disk based. @end itemize @node SHOW VARIABLES, SHOW LOGS, SHOW STATUS, SHOW @subsubsection @code{SHOW VARIABLES} @example SHOW [GLOBAL | SESSION] VARIABLES [LIKE wild] @end example @code{SHOW VARIABLES} は MySQL システム変数のいくつかの値を示します。 @code{mysqlshow variables} コマンドでも同じ情報が得られます。 もし標準値が適さないなら、ほとんどの変数を @code{mysqld} 起動時に コマンドラインのオプションとして与えることにより、変更できます。 @xref{Command-line options}. The options @code{GLOBAL} and @code{SESSION} are new in MySQL 4.0.3. With @code{GLOBAL} you will get the variables that will be used for new connections to MySQL. With @code{SESSION} you will get the values that are in effect for the current connection. If you are not using either option, @code{SESSION} is used. You can change most options with the @code{SET} command. @xref{SET OPTION, , @code{SET}}. 出力は以下のようになりますが、フォーマットや数はいくぶん違うでしょう： @example +---------------------------------+------------------------------+ | Variable_name | Value | +---------------------------------+------------------------------| | back_log | 50 | | basedir | /usr/local/mysql | | bdb_cache_size | 8388572 | | bdb_log_buffer_size | 32768 | | bdb_home | /usr/local/mysql | | bdb_max_lock | 10000 | | bdb_logdir | | | bdb_shared_data | OFF | | bdb_tmpdir | /tmp/ | | bdb_version | Sleepycat Software: ... | | binlog_cache_size | 32768 | | bulk_insert_buffer_size | 8388608 | | character_set | latin1 | | character_sets | latin1 big5 czech euc_kr | | concurrent_insert | ON | | connect_timeout | 5 | | convert_character_set | | | datadir | /usr/local/mysql/data/ | | delay_key_write | ON | | delayed_insert_limit | 100 | | delayed_insert_timeout | 300 | | delayed_queue_size | 1000 | | flush | OFF | | flush_time | 0 | | ft_boolean_syntax | + -><()~*:""&| | | ft_min_word_len | 4 | | ft_max_word_len | 254 | | ft_max_word_len_for_sort | 20 | | ft_stopword_file | (built-in) | | have_bdb | YES | | have_innodb | YES | | have_isam | YES | | have_raid | NO | | have_symlink | DISABLED | | have_openssl | YES | | have_query_cache | YES | | init_file | | | innodb_additional_mem_pool_size | 1048576 | | innodb_buffer_pool_size | 8388608 | | innodb_data_file_path | ibdata1:10M:autoextend | | innodb_data_home_dir | | | innodb_file_io_threads | 4 | | innodb_force_recovery | 0 | | innodb_thread_concurrency | 8 | | innodb_flush_log_at_trx_commit | 0 | | innodb_fast_shutdown | ON | | innodb_flush_method | | | innodb_lock_wait_timeout | 50 | | innodb_log_arch_dir | | | innodb_log_archive | OFF | | innodb_log_buffer_size | 1048576 | | innodb_log_file_size | 5242880 | | innodb_log_files_in_group | 2 | | innodb_log_group_home_dir | ./ | | innodb_mirrored_log_groups | 1 | | interactive_timeout | 28800 | | join_buffer_size | 131072 | | key_buffer_size | 16773120 | | language | /usr/local/mysql/share/... | | large_files_support | ON | | local_infile | ON | | locked_in_memory | OFF | | log | OFF | | log_update | OFF | | log_bin | OFF | | log_slave_updates | OFF | | log_slow_queries | OFF | | log_warnings | OFF | | long_query_time | 10 | | low_priority_updates | OFF | | lower_case_table_names | OFF | | max_allowed_packet | 1047552 | | max_binlog_cache_size | 4294967295 | | max_binlog_size | 1073741824 | | max_connections | 100 | | max_connect_errors | 10 | | max_delayed_threads | 20 | | max_heap_table_size | 16777216 | | max_join_size | 4294967295 | | max_sort_length | 1024 | | max_user_connections | 0 | | max_tmp_tables | 32 | | max_write_lock_count | 4294967295 | | myisam_max_extra_sort_file_size | 268435456 | | myisam_max_sort_file_size | 2147483647 | | myisam_recover_options | force | | myisam_sort_buffer_size | 8388608 | | net_buffer_length | 16384 | | net_read_timeout | 30 | | net_retry_count | 10 | | net_write_timeout | 60 | | open_files_limit | 0 | | pid_file | /usr/local/mysql/name.pid | | port | 3306 | | protocol_version | 10 | | read_buffer_size | 131072 | | read_rnd_buffer_size | 262144 | | rpl_recovery_rank | 0 | | query_cache_limit | 1048576 | | query_cache_size | 0 | | query_cache_type | ON | | safe_show_database | OFF | | server_id | 0 | | slave_net_timeout | 3600 | | skip_external_locking | ON | | skip_networking | OFF | | skip_show_database | OFF | | slow_launch_time | 2 | | socket | /tmp/mysql.sock | | sort_buffer_size | 2097116 | | sql_mode | 0 | | table_cache | 64 | | table_type | MYISAM | | thread_cache_size | 3 | | thread_stack | 131072 | | tx_isolation | READ-COMMITTED | | timezone | EEST | | tmp_table_size | 33554432 | | tmpdir | /tmp/:/mnt/hd2/tmp/ | | version | 4.0.4-beta | | wait_timeout | 28800 | +---------------------------------+------------------------------+ @end example Each option is described here. Values for buffer sizes, lengths, and stack sizes are given in bytes. これらの値の後ろに @samp{K} や @samp{M} を追加すると、キロバイト、 メガバイトになります。 例えば、@code{16M} は16メガバイトを示します。大文字小文字の区別はなく、 @code{16M} と @code{16m} は同じ意味になります。 @c FIX 2002-04-29 arjen / paul @c FIX Below should be a @multitable just like SHOW STATUS. @c FIX Has to wait till after O'Reilly printed edition is out the door. @cindex variables, values @itemize @item @code{ansi_mode}. もし @code{mysqld} が @code{--ansi} オプションで起動されているなら、@code{ON}. @xref{ANSI mode}. @item @code{back_log} MySQL が持てる未解決の接続要求の数です。これは MySQL スレッドが@strong{ものすごく}多くの接続要求をとても短い時間に得た時に、働き ます。接続のチェックと新しいスレッドの開始はメインスレッドにすこし時間 (しかしほんのわずか)がかかります。back_log は、MySQL が瞬間的に新 しい要求への回答を停止する前に、この短い時間の間にスタックできる接続数です。 短い期間に多くの接続を期待する場合にだけ、これを増加する必要があります。 いいかえるなら、これは TCP/IP 接続の入力 listen キューのサイズです。 オペレーティングシステムはこのキューの大きさを制限しています。 UNIX システムコール @code{listen(2)} のマニュアルページに、さらに詳細があります。 この値を最大限にしたい場合、お使いのOSのドキュメントを見てください。 @code{back_log} をこのOSの制限値より多く取ってもは全く効果ありません。 @item @code{basedir} The value of the @code{--basedir} option. @item @code{bdb_cache_size} The buffer that is allocated to cache index and rows for @code{BDB} tables. If you don't use @code{BDB} tables, you should start @code{mysqld} with @code{--skip-bdb} to not waste memory for this cache. @item @code{bdb_log_buffer_size} The buffer that is allocated to cache index and rows for @code{BDB} tables. If you don't use @code{BDB} tables, you should set this to 0 or start @code{mysqld} with @code{--skip-bdb} to not waste memory for this cache. @item @code{bdb_home} The value of the @code{--bdb-home} option. @item @code{bdb_max_lock} The maximum number of locks (10,000 by default) you can have active on a BDB table. You should increase this if you get errors of type @code{bdb: Lock table is out of available locks} or @code{Got error 12 from ...} when you have do long transactions or when @code{mysqld} has to examine a lot of rows to calculate the query. @item @code{bdb_logdir} The value of the @code{--bdb-logdir} option. @item @code{bdb_shared_data} Is @code{ON} if you are using @code{--bdb-shared-data}. @item @code{bdb_tmpdir} The value of the @code{--bdb-tmpdir} option. @item @code{binlog_cache_size}. The size of the cache to hold the SQL statements for the binary log during a transaction. If you often use big, multi-statement transactions you can increase this to get more performance. @xref{COMMIT}. @item @code{bulk_insert_buffer_size} (was @code{myisam_bulk_insert_tree_size}) MyISAM uses special tree-like cache to make bulk inserts (that is, @code{INSERT ... SELECT}, @code{INSERT ... VALUES (...), (...), ...}, and @code{LOAD DATA INFILE}) faster. This variable limits the size of the cache tree in bytes per thread. Setting it to 0 will disable this optimisation. @strong{Note}: this cache is only used when adding data to non-empty table. Default value is 8 MB. @item @code{character_set} The default character set. @item @code{character_sets} The supported character sets. @item @code{concurrent_inserts} もし @code{ON} (これはデフォルトです) なら、MySQL は、 @code{SELECT} クエリが実行されている @code{MyISAM} テーブルに対して、 同時に @code{INSERT} が使用できるようにします。 このオプションは @code{mysqld} のオプションに @code{--safe} か @code{--skip-new} を 指定することで @code{OFF} にできます。 @cindex timeout @item @code{connect_timeout} @code{mysqld} サーバーが接続パケットを待つ秒数。 (@code{Bad handshake} を返すま での秒数) @item @code{datadir} The value of the @code{--datadir} option. @item @code{delay_key_write} Option for MyISAM tables. Can have one of the following values: @multitable @columnfractions .30 .70 @item OFF @tab All CREATE TABLE ... DELAYED_KEY_WRITES are ignored. @item ON @tab (デフォルト) MySQL は @code{CREATE TABLE} 文の @code{DELAY_KEY_WRITE} オプションを尊重します。 @item ALL @tab 開かれている全てのテーブルが @code{DELAY_KEY_WRITE} オプション指定されて 作成されたものとして扱われる @end multitable @code{DELAY_KEY_WRITE} オプションが有効な場合、テーブルのキーバッファは、 毎回のインデックスの更新にはフラッシュされず、ただテーブルが閉じられたときにだけ フラッシュされます。 これはキーの書き出しを速くしますが、もしこれを使用するなら、 全てのテーブルを @code{myisamchk --fast --force} で自動的に検査するようにすべき です。 @item @code{delayed_insert_limit} @code{delayed_insert_limit} 個のレコードを挿入した後、 @code{INSERT DELAYED} ハンドラーは待たされている @code{SELECT} 文がないかチェックします。 もしあるなら、 挿入を続ける前にそれらの実行を許します。 @item @code{delayed_insert_timeout} どれぐらい @code{INSERT DELAYED} スレッドが @code{INSERT} 文を待つべきか。 @item @code{delayed_queue_size} What size queue (in rows) should be allocated for handling @code{INSERT DELAYED}. If the queue becomes full, any client that does @code{INSERT DELAYED} will wait until there is room in the queue again. @item @code{flush} This is @code{ON} if you have started MySQL with the @code{--flush} option. @item @code{flush_time} これがもし、非ゼロにセットされたなら、毎 @code{flush_time} 秒ごとに 全てのテーブルが閉じられます。 (リソースの解放とDiskへのsyncのために) We only recommend this option on Windows 9x/Me, or on systems where you have very little resources. @item @code{ft_boolean_syntax} List of operators supported by @code{MATCH ... AGAINST(... IN BOOLEAN MODE)}. @xref{Fulltext Search}. @item @code{ft_min_word_len} The minimum length of the word to be included in a @code{FULLTEXT} index. @strong{Note: @code{FULLTEXT} indexes must be rebuilt after changing this variable.} (This option is new for MySQL 4.0.) @item @code{ft_max_word_len} The maximum length of the word to be included in a @code{FULLTEXT} index. @strong{Note: @code{FULLTEXT} indexes must be rebuilt after changing this variable.} (This option is new for MySQL 4.0.) @item @code{ft_max_word_len_for_sort} The maximum length of the word in a @code{FULLTEXT} index to be used in fast index recreation method in @code{REPAIR}, @code{CREATE INDEX}, or @code{ALTER TABLE}. Longer words are inserted the slow way. The rule of the thumb is as follows: with @code{ft_max_word_len_for_sort} increasing, @strong{MySQL} will create bigger temporary files (thus slowing the process down, due to disk I/O), and will put fewer keys in one sort block (again, decreasing the efficiency). When @code{ft_max_word_len_for_sort} is too small, instead, @strong{MySQL} will insert a lot of words into index the slow way, but short words will be inserted very quickly. @item @code{ft_stopword_file} The file to read the list of stopwords for fulltext search from. All the words from the file will be used, comments are @strong{not} honored. By default, built-in list of stopwords is used (as defined in @file{myisam/ft_static.c}). Setting this parameter to an empty string (@code{""}) will disable stopword filtering. @strong{Note: @code{FULLTEXT} indexes must be rebuilt after changing this variable.} (This option is new for MySQL 4.0.10) @item @code{have_innodb} @code{YES} if @code{mysqld} supports InnoDB tables. @code{DISABLED} if @code{--skip-innodb} is used. @item @code{have_bdb} @code{YES} if @code{mysqld} supports Berkeley DB tables. @code{DISABLED} if @code{--skip-bdb} is used. @item @code{have_raid} @code{YES} if @code{mysqld} supports the @code{RAID} option. @item @code{have_openssl} @code{YES} if @code{mysqld} supports SSL (encryption) on the client/server protocol. @item @code{init_file} サーバー起動時に、@code{--init-file} オプションに与えたファイルの名前です。 このファイルには、サーバー起動時に実行したい SQL 文を書いておきます。 @item @code{interactive_timeout} The number of seconds the server waits for activity on an interactive connection before closing it. An interactive client is defined as a client that uses the @code{CLIENT_INTERACTIVE} option to @code{mysql_real_connect()}. See also @code{wait_timeout}. @item @code{join_buffer_size} このバッファは(インデックス無しの)完全な結合に使用されます。それは2つの テーブル間の完全な結合ごとに1回割り当てられます。インデックスの追加がで きない時、より速い完全な結合を得るために、これを増加してください。通常、 速い結合を得る一番良い方法は、インデックスを追加することです。 @c Make texi2html support index @anchor{Index cache size}. Then change @c some xrefs to point here @cindex indexes, block size @item @code{key_buffer_size} インデックス・ブロックはバッファされ、そして全てのスレッドに共有されます。 @code{key_buffer_size} はインデックス・ブロックのためのバッファ・サイズです。 Increase this to get better index handling (for all reads and multiple writes) to as much as you can afford; 64M on a 256M machine that mainly runs MySQL is quite common. If you, however, make this too big (for instance more than 50% of your total memory) your system may start to page and become extremely slow. Remember that because MySQL does not cache data reads, you will have to leave some room for the OS filesystem cache. You can check the performance of the key buffer by doing @code{SHOW STATUS} and examine the variables @code{Key_read_requests}, @code{Key_reads}, @code{Key_write_requests}, and @code{Key_writes}. The @code{Key_reads/Key_read_request} ratio should normally be < 0.01. The @code{Key_write/Key_write_requests} is usually near 1 if you are using mostly updates/deletes but may be much smaller if you tend to do updates that affect many at the same time or if you are using @code{DELAY_KEY_WRITE}. @xref{SHOW, , @code{SHOW}}. To get even more speed when writing many rows at the same time, use @code{LOCK TABLES}. @xref{LOCK TABLES, , @code{LOCK TABLES}}. @item @code{language} The language used for error messages. @item @code{large_file_support} If @code{mysqld} was compiled with options for big file support. @item @code{locked_in_memory} If @code{mysqld} was locked in memory with @code{--memlock} @item @code{log} If logging of all queries is enabled. @item @code{log_update} If the update log is enabled. @item @code{log_bin} If the binary log is enabled. @item @code{log_slave_updates} If the updates from the slave should be logged. @item @code{long_query_time} もしあるクエリがこの値(秒)より時間がかかれば、@code{Slow_queries} カウンター が増やされます。 If you are using @code{--log-slow-queries}, the query will be logged to the slow query logfile. This value is measured in real time, not CPU time, so a query that may be under the threshold on a lightly loaded system may be above the threshold on a heavily loaded one. @xref{Slow query log}. @item @code{lower_case_table_names} If set to 1 table names are stored in lowercase on disk and table name comparisons will be case-insensitive. From version 4.0.2, this option also applies to database names. @xref{Name case sensitivity}. @item @code{max_allowed_packet} 一つのパケットの最大サイズ。メッセージバッファは @code{net_buffer_length} バイト に初期化されますが、 @code{max_allowed_packet}まで大きくすることができます。このデフォルト値は、 大きなパケット、間違ったパケットをを受けるには小さい値です。 大きな @code{BLOB} を使用している場合は、これを増加する必要があります。使用した い最大の @code{BLOB} と同じくらい大きくするべきです。 The protocol limits for @code{max_allowed_packet} is 16M in MySQL 3.23 and 1G in MySQL 4.0. @item @code{max_binlog_cache_size} If a multi-statement transaction requires more than this amount of memory, one will get the error "Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage". @item @code{max_binlog_size} バージョン 3.23.33 以降より有効. もしバイナリ(レプリケーション)ログファイルの大きさが、これに指定された数を 超えて書かれてしまった場合、ログファイルが自動でローテートされます。 1024<=@code{max_binlog_size}<=1GB までの 範囲の値しか与えれません。デフォルトは 1GB です。 @item @code{max_connections} 許される同時クライアントの数。これを増加する場合は、@code{mysqld} が持つファイ ルディスクリプタの数を増やす必要があるでしょう。 後述のファイルデスクリプターの制限の説明を参照のこと。 @xref{Too many connections}. @item @code{max_connect_errors} もしあるホストからの接続中断がこの値を以上になった場合、これ以後、 そのホストからの接続を拒絶します。@code{FLUSH HOSTS} コマンドで ホストの拒否を解除できます。 @item @code{max_delayed_threads} この値を超えて @code{INSERT DELAYED} を扱うスレッドを起動できません。 もし全ての @code{INSERT DELAYED} スレッドが使用されていて、さらに新しいテーブルに データを挿入しようとすると、そのレコードは @code{DELAYED} が与えられていない 場合と同様に挿入されます。 @item @code{max_heap_table_size} Don't allow creation of heap tables bigger than this. @item @code{max_join_size} @code{max_join_size} より多いレコードを触るとエラーが返ります。長い時間をかけて 百万行を返すような @code{WHERE} なしの結合を作成するようなユーザを持って いる場合にこれを設定してください。 @item @code{max_sort_length} @code{BLOB} または @code{TEXT} 項目上でソートする時に使用するバイト数。 (最初の @code{max_sort_length} バイトだけがそれぞれの値で使用でき、残りは無視さ れます) @item @code{max_user_connections} The maximum number of active connections for a single user (0 = no limit). @item @code{max_tmp_tables} (このオプションはまだなにも行いません). クライアントが同時にオープンできるテーブル数の最大値。 @item @code{max_write_lock_count} After this many write locks, allow some read locks to run in between. @item @code{myisam_recover_options} The value of the @code{--myisam-recover} option. @item @code{myisam_sort_buffer_size} The buffer that is allocated when sorting the index when doing a @code{REPAIR} or when creating indexes with @code{CREATE INDEX} or @code{ALTER TABLE}. @item @code{myisam_max_extra_sort_file_size}. If the temporary file used for fast index creation would be bigger than using the key cache by the amount specified here, then prefer the key cache method. This is mainly used to force long character keys in large tables to use the slower key cache method to create the index. @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. @item @code{myisam_max_sort_file_size} The maximum size of the temporary file MySQL is allowed to use while recreating the index (during @code{REPAIR}, @code{ALTER TABLE} or @code{LOAD DATA INFILE}. If the file-size would be bigger than this, the index will be created through the key cache (which is slower). @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. @item @code{net_buffer_length} 通信バッファがクエリ間でこのサイズにリセットされます。これは通常は変更す べきではありませんが、とても小さなメモリしかない場合は、これを期待される クエリのサイズに設定してください。 ( これは、クライアントから送られてくるSQL文の長さ分あればいいでしょう。 もし構文がこの値をこえた場合、バッファは自動的に大きくなります。 ただし @code{max_allowed_packet} バイトまでです) @item @code{net_read_timeout} Number of seconds to wait for more data from a connection before aborting the read. Note that when we don't expect data from a connection, the timeout is defined by @code{write_timeout}. See also @code{slave_net_timeout}. @item @code{net_retry_count} If a read on a communication port is interrupted, retry this many times before giving up. This value should be quite high on @code{FreeBSD} as internal interrupts are sent to all threads. @item @code{net_write_timeout} Number of seconds to wait for a block to be written to a connection before aborting the write. @item @code{open_files_limit} If this is not 0, then @code{mysqld} will use this value to reserve file descriptors to use with @code{setrlimit()}. If this value is 0 then @code{mysqld} will reserve @code{max_connections*5} or @code{max_connections + table_cache*2} (whichever is larger) number of files. You should try increasing this if @code{mysqld} gives you the error 'Too many open files'. @item @code{pid_file} The value of the @code{--pid-file} option. @item @code{port} The value of the @code{--port} option. @item @code{protocol_version} The protocol version used by the MySQL server. @item @code{read_buffer_size} (ver. 4.0.3 未満では @code{record_buffer}) 順序スキャンを行う各スレッドが、スキャンするテーブル毎に、このサイズのバッ ファを割り当てます。多くの順序スキャンを行う場合は、これを増加させてくだ さい。 @item @code{record_rnd_buffer_size} When reading rows in sorted order after a sort, the rows are read through this buffer to avoid a disk seeks. Can improve @code{ORDER BY} by a lot if set to a high value. As this is a thread-specific variable, one should not set this big globally, but just change this when running some specific big queries. @item @code{query_cache_limit} Don't cache results that are bigger than this. (Default 1M). @item @code{query_cache_size} The memory allocated to store results from old queries. If this is 0, the query cache is disabled (default). @item @code{query_cache_type} This may be set (only numeric) to @multitable @columnfractions .09 .14 .72 @item @strong{Value} @tab @strong{Alias} @tab @strong{Comment} @item 0 @tab OFF @tab Don't cache or retrieve results. @item 1 @tab ON @tab Cache all results except @code{SELECT SQL_NO_CACHE ...} queries. @item 2 @tab DEMAND @tab Cache only @code{SELECT SQL_CACHE ...} queries. @end multitable @item @code{safe_show_database} Don't show databases for which the user doesn't have any database or table privileges. This can improve security if you're concerned about people being able to see what databases other users have. See also @code{skip_show_database}. @item @code{server_id} The value of the @code{--server-id} option. @item @code{skip_locking} Is OFF if @code{mysqld} uses external locking. @item @code{skip_networking} Is ON if we only allow local (socket) connections. @item @code{skip_show_database} This prevents people from doing @code{SHOW DATABASES} if they don't have the @code{PROCESS} privilege. This can improve security if you're concerned about people being able to see what databases other users have. See also @code{safe_show_database}. @item @code{slave_net_timeout} Number of seconds to wait for more data from a master/slave connection before aborting the read. @item @code{slow_launch_time} If creating the thread takes longer than this value (in seconds), the @code{Slow_launch_threads} counter will be incremented. @item @code{socket} The Unix socket used by the server. @item @code{sort_buffer_size} ソートを行う必要がある各スレッドがこのサイズのバッファを割り当てます。よ り速い @code{ORDER BY} または @code{GROUP BY} のためにはこれを増やしてく ださい。 @xref{Temporary files}. @item @code{table_cache} 全てのスレッドについてのオープンテーブルの数。これを増加する場合は、 @code{mysqld} が要求するオープンファイルディスクリプタの数も 増加することに注意しないといけません。 You can check if you need to increase the table cache by checking the @code{Opened_tables} variable. @xref{SHOW STATUS, , @code{Opened_tables}}. If this variable is big and you don't do @code{FLUSH TABLES} a lot (which just forces all tables to be closed and reopenend), then you should increase the value of this variable. For more information about the table cache, see @ref{Table cache}. @item @code{table_type} The default table type. @item @code{thread_cache_size} How many threads we should keep in a cache for reuse. When a client disconnects, the client's threads are put in the cache if there aren't more than @code{thread_cache_size} threads from before. All new threads are first taken from the cache, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. (Normally this doesn't give a notable performance improvement if you have a good thread implementation.) By examing the difference between the @code{Connections} and @code{Threads_created} status variables (@pxref{SHOW STATUS} for details) you can see how efficient thread cache is. @item @code{thread_concurrency} On Solaris, @code{mysqld} will call @code{thr_setconcurrency()} with this value. @code{thr_setconcurrency()} permits the application to give the threads system a hint for the desired number of threads that should be run at the same time. @item @code{thread_stack} 各スレッドのスタックの大きさ。@code{crash-me} によって検出される多く の制限がこれに依存します。デフォルトでは、通常のオペレーションに対して 十分とってあります。 @xref{MySQL Benchmarks}. @item @code{timezone} The timezone for the server. @item @code{tmp_table_size} メモリー内の 一時テーブルがこの値を超えようとした場合、MySQL は 自動的に、これを、disk ベースの @code{MyISAM} テーブルに変換します。 多くの先進的な @code{GROUP BY} クエリを行う場合は、 この @code{tmp_table_size} を増加してください。 @item @code{tmpdir} The directory used for temporary files and temporary tables. Starting from MySQL 4.1, it can be set to a list of paths separated by colon @code{:} (semicolon @code{;} on Windows). They will be used in round-robin fashion. This feature can be used to spread load between several physical disks. @item @code{version} The version number for the server. @item @code{wait_timeout} インタラクティブではないアクティブなコネクションを 閉じるのに、にサーバーが待つ秒数。 On thread startup @code{SESSION.WAIT_TIMEOUT} is initialised from @code{GLOBAL.WAIT_TIMEOUT} or @code{GLOBAL.INTERACTIVE_TIMEOUT} depending on the type of client (as defined by the @code{CLIENT_INTERACTIVE} connect option). See also @code{interactive_timeout}. @end itemize The manual section that describes tuning MySQL contains some information of how to tune the above variables. @xref{Server parameters}. @node SHOW LOGS, SHOW PROCESSLIST, SHOW VARIABLES, SHOW @subsubsection @code{SHOW LOGS} @code{SHOW LOGS} shows you status information about existing log files. It currently only displays information about Berkeley DB log files. @itemize @bullet @item @code{File} shows the full path to the log file @item @code{Type} shows the type of the log file (@code{BDB} for Berkeley DB log files) @item @code{Status} shows the status of the log file (@code{FREE} if the file can be removed, or @code{IN USE} if the file is needed by the transaction subsystem) @end itemize @node SHOW PROCESSLIST, SHOW GRANTS, SHOW LOGS, SHOW @subsubsection @code{SHOW PROCESSLIST} @findex threads @findex PROCESSLIST @findex SHOW PROCESSLIST @cindex threads, display @cindex processes, display @code{SHOW [FULL] PROCESSLIST} はどのスレッドが走っているかを表示します。 @code{mysqlshow processlist} コマンドでも同じ情報が得られます。 もし @code{SUPER} 権限があるなら、全てのスレッドがみれます。 しかし権限がないなら、自分のスレッドしか見れません。 @xref{KILL, ,@code{KILL}}. (@code{SUPER}は4.0.2以上。4.0.2未満では @code{PROCESS}権限があるだけで全てのスレッドが見れた) @code{FULL} オプションを使用しない場合、各クエリの最初の100文字だけが表示 されます。 Starting from 4.0.12, MySQL reports the hostname for TCP/IP connections as @code{hostname:client_port} to make it easier to find out which client is doing what. This command is very useful if you get the 'too many connections' error message and want to find out what's going on. MySQL reserves one extra connection for a client with the @code{SUPER} privilege to ensure that you should always be able to login and check the system (assuming you are not giving this privilege to all your users). Some states commonly seen in @code{mysqladmin processlist} @itemize @bullet @item @code{Checking table} The thread is performing [automatic] checking of the table. @item @code{Closing tables} Means that the thread is flushing the changed table data to disk and closing the used tables. This should be a fast operation. If not, then you should check that you don't have a full disk or that the disk is not in very heavy use. @item @code{Connect Out} Slave connecting to master. @item @code{Copying to tmp table on disk} The temporary result set was larger than @code{tmp_table_size} and the thread is now changing the in memory-based temporary table to a disk based one to save memory. @item @code{Creating tmp table} The thread is creating a temporary table to hold a part of the result for the query. @item @code{deleting from main table} When executing the first part of a multi-table delete and we are only deleting from the first table. @item @code{deleting from reference tables} When executing the second part of a multi-table delete and we are deleting the matched rows from the other tables. @item @code{Flushing tables} The thread is executing @code{FLUSH TABLES} and is waiting for all threads to close their tables. @item @code{Killed} Someone has sent a kill to the thread and it should abort next time it checks the kill flag. The flag is checked in each major loop in MySQL, but in some cases it may still take a short time for the thread to die. If the thread is locked by some other thread, the kill will take affect as soon as the other thread releases it's lock. @item @code{Sending data} The thread is processing rows for a @code{SELECT} statement and is also sending data to the client. @item @code{Sorting for group} The thread is doing a sort to satsify a @code{GROUP BY}. @item @code{Sorting for order} The thread is doing a sort to satsify a @code{ORDER BY}. @item @code{Opening tables} This simply means that the thread is trying to open a table. This is should be very fast procedure, unless something prevents opening. For example an @code{ALTER TABLE} or a @code{LOCK TABLE} can prevent opening a table until the command is finished. @item @code{Removing duplicates} The query was using @code{SELECT DISTINCT} in such a way that MySQL couldn't optimise that distinct away at an early stage. Because of this MySQL has to do an extra stage to remove all duplicated rows before sending the result to the client. @item @code{Reopen table} The thread got a lock for the table, but noticed after getting the lock that the underlying table structure changed. It has freed the lock, closed the table and is now trying to reopen it. @item @code{Repair by sorting} The repair code is using sorting to create indexes. @item @code{Repair with keycache} The repair code is using creating keys one by one through the key cache. This is much slower than @code{Repair by sorting}. @item @code{Searching rows for update} The thread is doing a first phase to find all matching rows before updating them. This has to be done if the @code{UPDATE} is changing the index that is used to find the involved rows. @item @code{Sleeping} The thread is wating for the client to send a new command to it. @item @code{System lock} The thread is waiting for getting to get a external system lock for the table. If you are not using multiple mysqld servers that are accessing the same tables, you can disable system locks with the @code{--skip-external-locking} option. @item @code{Upgrading lock} The @code{INSERT DELAYED} handler is trying to get a lock for the table to insert rows. @item @code{Updating} The thread is searching for rows to update and updating them. @item @code{User Lock} The thread is waiting on a @code{GET_LOCK()}. @item @code{Waiting for tables} The thread got a notification that the underlying structure for a table has changed and it needs to reopen the table to get the new structure. To be able to reopen the table it must however wait until all other threads have closed the table in question. This notification happens if another thread has used @code{FLUSH TABLES} or one of the following commands on the table in question: @code{FLUSH TABLES table_name}, @code{ALTER TABLE}, @code{RENAME TABLE}, @code{REPAIR TABLE}, @code{ANALYZE TABLE} or @code{OPTIMIZE TABLE}. @item @code{waiting for handler insert} The @code{INSERT DELAYED} handler has processed all inserts and are waiting to get new ones. @end itemize Most states are very quick operations. If threads last in any of these states for many seconds, there may be a problem around that needs to be investigated. There are some other states that are not mentioned previously, but most of these are only useful to find bugs in @code{mysqld}. @node SHOW GRANTS, SHOW CREATE TABLE, SHOW PROCESSLIST, SHOW @subsubsection @code{SHOW GRANTS} @cindex privileges, display @findex GRANTS @findex SHOW GRANTS @code{SHOW GRANTS FOR user} はユーザの許可を複製するために発行する必要があ る grant コマンドをリストします。 @example mysql> SHOW GRANTS FOR root@@localhost; +---------------------------------------------------------------------+ | Grants for root@@localhost | +---------------------------------------------------------------------+ | GRANT ALL PRIVILEGES ON *.* TO 'root'@@'localhost' WITH GRANT OPTION | +---------------------------------------------------------------------+ @end example To list grants for the current session one may use @code{CURRENT_USER()} function (new in version 4.0.6) to find out what user the session was authentificated as. @xref{Miscellaneous functions, ,@code{CURRENT_USER()}}. @node SHOW CREATE TABLE, SHOW WARNINGS, SHOW GRANTS, SHOW @subsubsection @code{SHOW CREATE TABLE} @findex SHOW CREATE TABLE Shows a @code{CREATE TABLE} statement that will create the given table: @example mysql> SHOW CREATE TABLE t\G *************************** 1. row *************************** Table: t Create Table: CREATE TABLE t ( id int(11) default NULL auto_increment, s char(60) default NULL, PRIMARY KEY (id) ) TYPE=MyISAM @end example @code{SHOW CREATE TABLE} will quote table and column names according to @code{SQL_QUOTE_SHOW_CREATE} option. @ref{SET OPTION, , @code{SET SQL_QUOTE_SHOW_CREATE}}. @node SHOW WARNINGS, SHOW TABLE TYPES, SHOW CREATE TABLE, SHOW @subsubsection @code{SHOW WARNINGS | ERRORS} @findex SHOW WARNINGS @example SHOW WARNINGS [LIMIT #] SHOW ERRORS [LIMIT #] @end example This command is implemented in MySQL 4.1.0. It shows the errors, warnings and notes that one got for the last command. The errors/warnings are reset for each new command that uses a table. The MySQL server sends back the total number of warnings and errors you got for the last commend; This can be retrieved by calling @code{mysql_warning_count()}. Up to @code{max_error_count} messages are stored (Global and thread specific variable). You can retrieve the number of errors from @code{@@error_count} and warnings from @code{@@warning_count}. @code{SHOW WARNINGS} shows all errors, warnings and notes you got for the last command while @code{SHOW ERRORS} only shows you the errors. @example mysql> DROP TABLE IF EXISTS no_such_table; mysql> SHOW WARNINGS; +-------+------+-------------------------------+ | Level | Code | Message | +-------+------+-------------------------------+ | Note | 1051 | Unknown table 'no_such_table' | +-------+------+-------------------------------+ @end example @node SHOW TABLE TYPES, SHOW PRIVILEGES, SHOW WARNINGS, SHOW @subsubsection @code{SHOW TABLE TYPES} @findex SHOW TABLE TYPES @example SHOW TABLE TYPES @end example This command is implemented in MySQL 4.1.0. @code{SHOW TABLE TYPES} shows you status information about the table types. This is particulary useful for checking if a table type is supported; or to see what is the default table type is. @example mysql> SHOW TABLE TYPES; +--------+---------+-----------------------------------------------------------+ | Type | Support | Comment | +--------+---------+-----------------------------------------------------------+ | MyISAM | DEFAULT | Default type from 3.23 with great performance | | HEAP | YES | Hash based, stored in memory, useful for temporary tables | | MERGE | YES | Collection of identical MyISAM tables | | ISAM | YES | Obsolete table type; Is replaced by MyISAM | | InnoDB | YES | Supports transactions, row-level locking and foreign keys | | BDB | NO | Supports transactions and page-level locking | +--------+---------+-----------------------------------------------------------+ 6 rows in set (0.00 sec) @end example The 'Support' option @code{DEFAULT} indicates whether the perticular table type is supported, and which is the default type. If the server is started with @code{--default-table-type=InnoDB}, then the InnoDB 'Support' field will have the value @code{DEFAULT}. @node SHOW PRIVILEGES, , SHOW TABLE TYPES, SHOW @subsubsection @code{SHOW PRIVILEGES} @findex SHOW PRIVILEGES @example SHOW PRIVILEGES @end example This command is implemented in MySQL 4.1.0. @code{SHOW PRIVILEGES} shows the list of system privileges that the underlying MySQL server supports. @example mysql> show privileges; +------------+--------------------------+-------------------------------------------------------+ | Privilege | Context | Comment | +------------+--------------------------+-------------------------------------------------------+ | Select | Tables | To retrieve rows from table | | Insert | Tables | To insert data into tables | | Update | Tables | To update existing rows | | Delete | Tables | To delete existing rows | | Index | Tables | To create or drop indexes | | Alter | Tables | To alter the table | | Create | Databases,Tables,Indexes | To create new databases and tables | | Drop | Databases,Tables | To drop databases and tables | | Grant | Databases,Tables | To give to other users those privileges you possess | | References | Databases,Tables | To have references on tables | | Reload | Server Admin | To reload or refresh tables, logs and privileges | | Shutdown | Server Admin | To shutdown the server | | Process | Server Admin | To view the plain text of currently executing queries | | File | File access on server | To read and write files on the server | +------------+--------------------------+-------------------------------------------------------+ 14 rows in set (0.00 sec) @end example @node Localisation, Server-Side Scripts, Database Administration, MySQL Database Administration @section MySQL Localisation and International Usage @menu * Character sets:: The Character Set Used for Data and Sorting * Languages:: Non-English Error Messages * Adding character set:: Adding a New Character Set * Character arrays:: The Character Definition Arrays * String collating:: String Collating Support * Multi-byte characters:: Multi-byte Character Support * Problems with character sets:: Problems With Character Sets @end menu @node Character sets, Languages, Localisation, Localisation @subsection データとソートに使用されるキャラクター・セット @cindex character sets @cindex data, character sets @cindex sorting, character sets デフォルトでは、MySQL は スウェーデン語／フィンランド語に一致する ISO8859-1 (Latin1) キャラクター・セットをソートに使用します。これは USA と西 ヨーロッパに適したキャラクター・セットです。 All standard MySQL binaries are compiled with @code{--with-extra-charsets=complex}. This will add code to all standard programs to be able to handle @code{latin1} and all multi-byte character sets within the binary. Other character sets will be loaded from a character-set definition file when needed. キャラクター・セットは名前として許される文字と、@code{ORDER BY} と @code{GROUP BY} コマンドによってソートされる方法を決定します。 キャラクターセットは、名前として使用してもよい文字と @code{SELECT} 構文中の @code{ORDER BY} と @code{GROUP BY} コマンドを用いたソート方法を決定します。 You can change the character set with the @code{--default-character-set} option when you start the server. The character sets available depend on the @code{--with-charset=charset} and @code{--with-extra-charsets= list-of-charset | complex | all} options to @code{configure}, and the character set configuration files listed in @file{SHAREDIR/charsets/Index}. @xref{configure options}. もし MySQL が実行中にキャラクター・セットを変更するならば、 （これはソートの順番も変わります）、全てのテーブルに対して @code{myisamchk -r -q --set-character-set=charset} を実行しなくてはなりません。 インデックスがただしい順番で並んでいないかもしれないからです。 クライアントが MySQL サーバに接続したとき、サーバは使用している デフォルトのキャラクター・セットをクライアントに送ります。 これを受け取ったクライアントは、キャラクター・セットを切り替えます。 SQL クエリの文字列をエスケープする場合には、 @code{mysql_real_escape_string()} を 使用するべきです。 @code{mysql_real_escape_string()} は、最初のパラメタとして MySQL へのコネクション・ハンドルを与える以外は、 古い @code{mysql_escape_string()} 関数と同じです。 もしクライアントがサーバがインストールされているところ(パス)とは違う パスでコンパイルされていて、 MySQL をコンフィギャしたユーザーが すべてのキャラクター・セットを MySQL バイナリに含めていない場合には、 どこに必要とされるキャラクター・セットの追加情報があるかを、クライアントに 教えなくてはなりません。もしサーバとクライアントが違うキャラクター・セットで動作し ているならば。 これは MySQL オプションファイルに次のように記述することで可能です： @example [client] character-sets-dir=/usr/local/mysql/share/mysql/charsets @end example ここで、パスはダイナミック MySQL キャラクター・セットが保存されている場所 です。 クライアントに、キャラクター・セットを強制することも可能です： @example [client] default-character-set=character-set-name @end example しかし通常はこれは不要です。 @menu * German character set:: German character set @end menu @node German character set, , Character sets, Character sets @subsubsection German character set To get German sorting order, you should start @code{mysqld} with @code{--default-character-set=latin1_de}. This will give you the following characteristics. When sorting and comparing string's the following mapping is done on the strings before doing the comparison: @example a -> ae o -> oe u -> ue s -> ss @end example All accented characters, are converted to their un-accented uppercase counterpart. All letters are converted to uppercase. When comparing strings with @code{LIKE} the one -> two character mapping is not done. All letters are converted to uppercase. Accent are removed from all letters except: @code{}, @code{}, @code{}, @code{}, @code{} and @code{}. @node Languages, Adding character set, Character sets, Localisation @subsection Non-English Error Messages @cindex error messages, languages @cindex messages, languages @cindex files, error messages @cindex language support @code{mysqld} は次の言語でエラーメッセージを提供できます: チェコ語, デンマーク語, オランダ語, 英語(デフォルト), Estonia, フランス語, ドイツ語, ギリシャ語, ハンガリー語, イタリア語, 日本語, 韓国語, ノルウェー語, 新ノルウェー語,ポーランド語, ポルトガル語, スペイン語そしてスウェーデン語。 ある言語で @code{mysqld} を開始するためには @code{--language=lang} また は @code{-L lang} スイッチの一つを使います: @example shell> mysqld --language=swedish @end example or: @example shell> mysqld --language=/usr/local/share/swedish @end example 言語名は全て小文字であることに注意してください。 言語ファイルは(デフォルトでは)次の場所にあります。 @file{@var{mysql_base_dir}/share/@var{LANGUAGE}/}. エラーメッセージファイルを更新したい場合は、 @file{errmsg.txt} ファイルを編集し、 @file{errmsg.sys} ファイルを作成するために以下のように実行します: @example shell> comp_err errmsg.txt errmsg.sys @end example もし MySQL を新しいものにアップグレードしたなら、以前修正した部分と同じ ところに、 新しい @file{errmsg.txt} ファイルに修正をほどこしてください。 @node Adding character set, Character arrays, Languages, Localisation @subsection 新しいキャラクター・セットの追加 @cindex character sets, adding @cindex adding, character sets 他のキャラクタ・セットを MySQL に追加するには、 以下の手順で行ないます。 そのキャラクター・セットが、simple か complex かを決めます。 もしそのキャラクター・セットがソートを行なうために特別な文字参照の ルーチンを必要としなくて、マルチバイト文字のサポートも必要としないのであれば、 そのキャラクター・セットは simple です。 もしどちらかの特徴を必要とするのであれば、それは complex です。 例えば、@code{latin1} と @code{danish} は simple キャラクター・セットで、 @code{big5} や @code{czech} は complex キャラクター・セットです。 以下のセクションでは、あなたがキャラクター・セットに @code{MYSET} という名前を つけていると仮定します。 For a simple character set do the following: @enumerate @item MYSET を @file{sql/share/charsets/Index} ファイルの最後に追加。 一意な番号を与えます。 @item @file{sql/share/charsets/MYSET.conf} ファイルを作成. (@file{sql/share/charsets/latin1.conf} をベースにしてよいでしょう). The syntax for the file very simple: @itemize @bullet @item Comments start with a '#' character and proceed to the end of the line. @item Words are separated by arbitrary amounts of whitespace. @item When defining the character set, every word must be a number in hexadecimal format @item The @code{ctype} array takes up the first 257 words. The @code{to_lower[]}, @code{to_upper[]} and @code{sort_order[]} arrays take up 256 words each after that. @end itemize @xref{Character arrays}. @item Add the character set name to the @code{CHARSETS_AVAILABLE} and @code{COMPILED_CHARSETS} lists in @code{configure.in}. @item Reconfigure, recompile, and test. @end enumerate For a complex character set do the following: @enumerate @item @file{strings/ctype-MYSET.c} ファイルを MySQL のソースディレクトリ以下 に作成します。 @item MYSET を @file{sql/share/charsets/Index} ファイルの最後に追加。 一意な番号を与えます。 @item 必要な定義されるものを調べるために、既存の @file{ctype-*.c} ファイルの一つを見てく ださい。このファイル中で使用する配列の名前は、 @code{ctype_MYSET}, @code{to_lower_MYSET} のようにしなければいけないことに注意し てください。 This corresponds to the arrays in the simple character set. @xref{Character arrays}. For a complex character set @item @file{ctype-*.c} ファイルの先頭付近に、以下のようなコメントを書きます： @example /* * This comment is parsed by configure to create ctype.c, * so don't change it unless you know what you are doing. * * .configure. number_MYSET=MYNUMBER * .configure. strxfrm_multiply_MYSET=N * .configure. mbmaxlen_MYSET=N */ @end example @code{configure} プログラムは、MySQL ライブラリに自動的に キャラクター・セットを含めるために、このコメントを使用します。 The strxfrm_multiply and mbmaxlen lines will be explained in the following sections. Only include these if you need the string collating functions or the multi-byte character set functions, respectively. @item 以下の関数を作成しなくてはなりません： @itemize @bullet @item @code{my_strncoll_MYSET()} @item @code{my_strcoll_MYSET()} @item @code{my_strxfrm_MYSET()} @item @code{my_like_range_MYSET()} @end itemize @xref{String collating}. @item キャラクター・セット名を、@code{configure.in} 中の @code{CHARSETS_AVAILABLE} と @code{COMPILED_CHARSETS} に追加します。 @item Reconfigure, recompile, and test. @end enumerate The file @file{sql/share/charsets/README} includes some more instructions. If you want to have the character set included in the MySQL distribution, mail a patch to @email{internals@@lists.mysql.com}. @node Character arrays, String collating, Adding character set, Localisation @subsection The Character Definition Arrays @code{to_lower[]} と @code{to_upper[]} は、それぞれのキャラクターセットに於ける 大文字、小文字の対応を定義した、単純な配列です。 例えば： @example to_lower['A'] should contain 'a' to_upper['a'] should contain 'A' @end example @code{sort_order[]} は文字がどのように比較され、ソートされるべきかのマップです。 本当に多くの(しかし全てのキャラクタセットではありません)セットでは、 これは @code{to_upper[]} と同じです (ケース非依存ソート)。 MySQL は @code{sort_order[character]} の値を元に文字をソートします。 MySQL will sort characters based on the value of @code{sort_order[character]}. For more complicated sorting rules, see the discussion of string collating below. @xref{String collating}. @code{ctype[]} は各文字を説明するビットの配列で、1かたまりのビット列が1文字を定 義します。 ( @code{to_lower[]}, @code{to_upper[]},@code{sort_order[]}は、文字の値でインデッ クスされますが、 @code{ctype[]}は文字の値+1 でインデックスされます。 これは EOF を操作するためにずいぶん前から使われているので、この方法を使用してい ます。) @file{m_ctype.h} に次のビットマスクの定義を見ることができます: @example #define _U 01 /* Uppercase */ #define _L 02 /* Lowercase */ #define _N 04 /* Numeral (digit) */ #define _S 010 /* Spacing character */ #define _P 020 /* Punctuation */ #define _C 040 /* Control character */ #define _B 0100 /* Blank */ #define _X 0200 /* heXadecimal digit */ @end example それぞれの文字に対する @code{ctype[]} は、文字を確定するために ビット列と組になっていなければなりません。 たとえば、@code{'A'} は大文字定義 (@code{_U}) と 16進定義 (@code{_X}) 両方ともに 属するので、@code{ctype['A'+1]} は以下の値を含まなくてはなりません: @example _U + _X = 01 + 0200 = 0201 @end example @node String collating, Multi-byte characters, Character arrays, Localisation @subsection String Collating Support @cindex collating, strings @cindex string collating If the sorting rules for your language are too complex to be handled with the simple @code{sort_order[]} table, you need to use the string collating functions. Right now the best documentation on this is the character sets that are already implemented. Look at the @code{big5}, @code{czech}, @code{gbk}, @code{sjis}, and @code{tis160} character sets for examples. You must specify the @code{strxfrm_multiply_MYSET=N} value in the special comment at the top of the file. @code{N} should be set to the maximum ratio the strings may grow during @code{my_strxfrm_MYSET} (it must be a positive integer). @node Multi-byte characters, Problems with character sets, String collating, Localisation @subsection マルチバイト文字のサポート @cindex characters, multi-byte @cindex multi-byte characters If your want to add support for a new character set that includes multi-byte characters, you need to use the multi-byte character functions. Right now the best documentation on this is the character sets that are already implemented. Look at the @code{euc_kr}, @code{gb2312}, @code{gbk}, @code{sjis}, and @code{ujis} character sets for examples. These are implemented in the @file{ctype-'charset'.c} files in the @file{strings} directory. You must specify the @code{mbmaxlen_MYSET=N} value in the special comment at the top of the source file. @code{N} should be set to the size in bytes of the largest character in the set. @node Problems with character sets, , Multi-byte characters, Localisation @subsection Problems With Character Sets If you try to use a character set that is not compiled into your binary, you can run into a couple of different problems: @itemize @bullet @item Your program has a wrong path to where the character sets are stored. (Default @file{/usr/local/mysql/share/mysql/charsets}). This can be fixed by using the @code{--character-sets-dir} option to the program in question. @item The character set is a multi-byte character set that can't be loaded dynamically. In this case you have to recompile the program with the support for the character set. @item The character set is a dynamic character set, but you don't have a configure file for it. In this case you should install the configure file for the character set from a new MySQL distribution. @item Your @file{Index} file doesn't contain the name for the character set. @example ERROR 1105: File '/usr/local/share/mysql/charsets/?.conf' not found (Errcode: 2) @end example In this case you should either get a new @code{Index} file or add by hand the name of any missing character sets. @end itemize For @code{MyISAM} tables, you can check the character set name and number for a table with @code{myisamchk -dvv table_name}. @node Server-Side Scripts, Client-Side Scripts, Localisation, MySQL Database Administration @section MySQL サーバー サイド の スクリプトとユーティリティ @menu * Server-Side Overview:: Overview of the Server-Side Scripts and Utilities * safe_mysqld:: @code{safe_mysqld}, The Wrapper Around @code{mysqld} * mysqld_multi:: @code{mysqld_multi}, A Program for Managing Multiple MySQL Servers * myisampack:: @code{myisampack}, The MySQL Compressed Read-only Table Generator * mysqld-max:: @code{mysqld-max}, An Extended @code{mysqld} Server @end menu @node Server-Side Overview, safe_mysqld, Server-Side Scripts, Server-Side Scripts @subsection Overview of the Server-Side Scripts and Utilities @cindex environment variables @cindex programs, list of All MySQL programs take many different options. However, every MySQL program provides a @code{--help} option that you can use to get a full description of the program's different options. For example, try @code{mysql --help}. You can override default options for all standard programs with an option file. @ref{Option files}. The following list briefly describes the server-side MySQL programs: @table @code @cindex @code{myisamchk} @item myisamchk Utility to describe, check, optimise, and repair MySQL tables. Because @code{myisamchk} has many functions, it is described in its own chapter. @xref{MySQL Database Administration}. @cindex @code{make_binary_distribution} @item make_binary_distribution Makes a binary release of a compiled MySQL. This could be sent by FTP to @file{/pub/mysql/Incoming} on @code{support.mysql.com} for the convenience of other MySQL users. @cindex @code{mysqlbug} @item mysqlbug The MySQL bug report script. This script should always be used when filing a bug report to the MySQL list. @cindex @code{mysqld} @item mysqld The SQL daemon. This should always be running. @cindex @code{mysql_install_db} @item mysql_install_db Creates the MySQL grant tables with default privileges. This is usually executed only once, when first installing MySQL on a system. @end table @node safe_mysqld, mysqld_multi, Server-Side Overview, Server-Side Scripts @subsection @code{safe_mysqld}, The Wrapper Around @code{mysqld} @cindex tools, safe_mysqld @cindex scripts @cindex @code{safe_mysqld} @cindex @code{mysqld_safe} Note that in MySQL 4.0 @code{safe_mysqld} was renamed to @code{mysqld_safe}. @code{safe_mysqld} is the recommended way to start a @code{mysqld} daemon on Unix. @code{safe_mysqld} adds some safety features such as restarting the server when an error occurs and logging run-time information to a log file. If you don't use @code{--mysqld=#} or @code{--mysqld-version=#} @code{safe_mysqld} will use an executable named @code{mysqld-max} if it exists. If not, @code{safe_mysqld} will start @code{mysqld}. This makes it very easy to test to use @code{mysqld-max} instead of @code{mysqld}; just copy @code{mysqld-max} to where you have @code{mysqld} and it will be used. Normally one should never edit the @code{safe_mysqld} script, but instead put the options to @code{safe_mysqld} in the @code{[safe_mysqld]} section in the @file{my.cnf} file. @code{safe_mysqld} will read all options from the @code{[mysqld]}, @code{[server]} and @code{[safe_mysqld]} sections from the option files. @xref{Option files}. Note that all options on the command-line to @code{safe_mysqld} are passed to @code{mysqld}. If you wants to use any options in @code{safe_mysqld} that @code{mysqld} doesn't support, you must specify these in the option file. Most of the options to @code{safe_mysqld} are the same as the options to @code{mysqld}. @xref{Command-line options}. @code{safe_mysqld} supports the following options: @table @code @item --basedir=path @item --core-file-size=# Size of the core file @code{mysqld} should be able to create. Passed to @code{ulimit -c}. @item --datadir=path @item --defaults-extra-file=path @item --defaults-file=path @item --err-log=path (this is marked obsolete in 4.0; Use --log-error instead) @item --log-error=path Write the error log to the above file. @xref{Error log}. @item --ledir=path Path to @code{mysqld} @item --log=path @item --mysqld=mysqld-version Name of the @code{mysqld} version in the @code{ledir} directory you want to start. @item --mysqld-version=version Similar to @code{--mysqld=} but here you only give the suffix for @code{mysqld}. For example if you use @code{--mysqld-version=max}, @code{safe_mysqld} will start the @code{ledir/mysqld-max} version. If the argument to @code{--mysqld-version} is empty, @code{ledir/mysqld} will be used. @item --no-defaults @item --open-files-limit=# Number of files @code{mysqld} should be able to open. Passed to @code{ulimit -n}. Note that you need to start @code{safe_mysqld} as root for this to work properly! @item --pid-file=path @item --port=# @item --socket=path @item --timezone=# Set the timezone (the @code{TZ}) variable to the value of this parameter. @item --user=# @end table The @code{safe_mysqld} script is written so that it normally is able to start a server that was installed from either a source or a binary version of MySQL, even if these install the server in slightly different locations. @code{safe_mysqld} expects one of these conditions to be true: @itemize @bullet @item The server and databases can be found relative to the directory from which @code{safe_mysqld} is invoked. @code{safe_mysqld} looks under its working directory for @file{bin} and @file{data} directories (for binary distributions) or for @file{libexec} and @file{var} directories (for source distributions). This condition should be met if you execute @code{safe_mysqld} from your MySQL installation directory (for example, @file{/usr/local/mysql} for a binary distribution). @item If the server and databases cannot be found relative to the working directory, @code{safe_mysqld} attempts to locate them by absolute pathnames. Typical locations are @file{/usr/local/libexec} and @file{/usr/local/var}. The actual locations are determined when the distribution was built from which @code{safe_mysqld} comes. They should be correct if MySQL was installed in a standard location. @end itemize Because @code{safe_mysqld} will try to find the server and databases relative to its own working directory, you can install a binary distribution of MySQL anywhere, as long as you start @code{safe_mysqld} from the MySQL installation directory: @example shell> cd mysql_installation_directory shell> bin/safe_mysqld & @end example If @code{safe_mysqld} fails, even when invoked from the MySQL installation directory, you can modify it to use the path to @code{mysqld} and the pathname options that are correct for your system. Note that if you upgrade MySQL in the future, your modified version of @code{safe_mysqld} will be overwritten, so you should make a copy of your edited version that you can reinstall. @node mysqld_multi, myisampack, safe_mysqld, Server-Side Scripts @subsection @code{mysqld_multi}, 複数の MySQL サーバーを管理するプログラム @cindex tools, mysqld_multi @cindex scripts @cindex multi mysqld @cindex @code{mysqld_multi} @code{mysqld_multi} is meant for managing several @code{mysqld} processes that listen for connections on different Unix sockets and TCP/IP ports. このプログラムは、@file{my.cnf} ファイル (もしくは、@code{--config-file=...} で与えられたファイル)の @code{[mysqld#]} (ここで @code{#} は 1から始まる数字) と命名されたセクションを探します。 This number is referred to in the following discussion as the option group number, or GNR. Group numbers distinquish option groups from one another and are used as arguments to @code{mysqld_multi} to specify which servers you want to start, stop, or obtain status for. Options listed in these groups should be the same as you would use in the usual @code{[mysqld]} group used for starting @code{mysqld}. (See, for example, @ref{Automatic start}.) However, for @code{mysqld_multi}, be sure that each group includes options for values such as the port, socket, etc., to be used for each individual @code{mysqld} process. @code{mysqld_multi} is invoked using the following syntax: @example Usage: mysqld_multi [OPTIONS] @{start|stop|report@} [GNR,GNR,GNR...] か mysqld_multi [OPTIONS] @{start|stop|report@} [GNR-GNR,GNR,GNR-GNR,...] @end example Each GNR represents an option group number. You can start, stop or report any GNR, or several of them at the same time. For an example of how you might set up an option file, use this command: @example shell> mysqld_multi --example @end example The GNR values in the list can be comma-separated or combined with a dash; in the latter case, all the GNRs between GNR1-GNR2 will be affected. GNR が引数に与えられなかった場合は、 全てのグループが、起動、停止、レポートされます。 GNR のリストには空白は許されません。スペースの後ろは無視されます。 @code{mysqld_multi} は以下のオプションをサポートします: @table @code @cindex config-file option @item --config-file=... Alternative config file. Note: This will not affect this program's own options (group @code{[mysqld_multi]}), but only groups @code{[mysqld#]}. Without this option, everything will be searched from the ordinary @file{my.cnf} file. @cindex example option @item --example オプション例を表示. @cindex help option @item --help ヘルプを表示して終了 @cindex log option @item --log=... ログファイル。フルパスで与えます。 もしファイルが存在している場合は、ログはファイルに追加されます。 @cindex mysqladmin option @item --mysqladmin=... サーバーの シャットダウン に使用する @code{mysqladmin} バイナリの指定 @cindex mysqld option @item --mysqld=... 使用する @code{mysqld} バイナリの指定。 @code{safe_mysqld} をこのオプションに指定することも可能です。 指定されたオプションは @code{mysqld} に渡されます。 Just make sure you have @code{mysqld} in your environment variable @code{PATH} or fix @code{safe_mysqld}. @cindex no-log option @item --no-log ログをログファイルではなく標準出力に書きだします。 デフォルトでは、ログファイルに書き込むモードです。 @cindex password option @item --password=... @code{mysqladmin} で使用するユーザーのパスワード. @cindex tcp-ip option @item --tcp-ip Connect to the MySQL server(s) via the TCP/IP port instead of the Unix socket. This affects stopping and reporting. If a socket file is missing, the server may still be running, but can be accessed only via the TCP/IP port. By default, connections are made using the Unix socket. @cindex user option @item --user=... @code{mysqladmin} で使用する MySQL ユーザー. @cindex version option @item --version バージョンを表示して終了. @end table Some notes about @code{mysqld_multi}: @itemize @bullet @item Make sure that the MySQL user, who is stopping the @code{mysqld} services (e.g using the @code{mysqladmin} program) have the same password and username for all the data directories accessed (to the @code{mysql} database) And make sure that the user has the @code{SHUTDOWN} privilege! If you have many data directories and many different @code{mysql} databases with different passwords for the MySQL @code{root} user, you may want to create a common @code{multi_admin} user for each using the same password (see below). Example how to do it: @example shell> mysql -u root -S /tmp/mysql.sock -proot_password -e "GRANT SHUTDOWN ON *.* TO multi_admin@@localhost IDENTIFIED BY 'multipass'" @end example @xref{Privileges}. You will have to do the above for each @code{mysqld} running in each data directory, that you have (just change the socket, @code{-S=...}). @item @code{pid-file} is very important, if you are using @code{safe_mysqld} to start @code{mysqld} (e.g., @code{--mysqld=safe_mysqld}) Every @code{mysqld} should have its own @code{pid-file}. The advantage using @code{safe_mysqld} instead of @code{mysqld} directly here is, that @code{safe_mysqld} ``guards'' every @code{mysqld} process and will restart it, if a @code{mysqld} process terminates due to a signal sent using @code{kill -9}, or for other reasons such as a segmentation fault (which MySQL should never do, of course ;). Please note that the @code{safe_mysqld} script may require that you start it from a certain place. This means that you may have to @code{cd} to a certain directory, before you start the @code{mysqld_multi}. If you have problems starting, please see the @code{safe_mysqld} script. Check especially the lines: @example -------------------------------------------------------------------------- MY_PWD=`pwd` Check if we are starting this relative (for the binary release) if test -d /data/mysql -a -f ./share/mysql/english/errmsg.sys -a -x ./bin/mysqld -------------------------------------------------------------------------- @end example @xref{safe_mysqld, , @code{safe_mysqld}}. The above test should be successful, or you may encounter problems. @item Beware of the dangers starting multiple @code{mysqld}s in the same data directory. Use separate data directories, unless you @strong{know} what you are doing! @item The socket file and the TCP/IP port must be different for every @code{mysqld}. @item The first and fifth @code{mysqld} group were intentionally left out from the example. You may have 'gaps' in the config file. This gives you more flexibility. The order in which the @code{mysqlds} are started or stopped depends on the order in which they appear in the config file. @item When you want to refer to a certain group using GNR with this program, just use the number in the end of the group name. For example, the GNR for a group named @code{[mysqld17]} is 17. @item You may want to use option @code{--user} for @code{mysqld}, but in order to do this you need to run the @code{mysqld_multi} script as the Unix @code{root} user. Having the option in the config file doesn't matter; you will just get a warning, if you are not the superuser and the @code{mysqlds} are started under @strong{your} Unix account. @strong{Important}: Make sure that the @code{pid-file} and the data directory are read+write(+execute for the latter one) accessible for @strong{that} Unix user, who the specific @code{mysqld} process is started as. @strong{Do not} use the Unix root account for this, unless you @strong{know} what you are doing! @item @strong{Most important}: Make sure that you understand the meanings of the options that are passed to the @code{mysqld}s and @strong{why one would want} to have separate @code{mysqld} processes. Starting multiple @code{mysqld}s in one data directory @strong{will not} give you extra performance in a threaded system! @end itemize @xref{Multiple servers}. This is an example of the config file on behalf of @code{mysqld_multi}. @example # This file should probably be in your home dir (~/.my.cnf) or /etc/my.cnf # Version 2.1 by Jani Tolonen [mysqld_multi] mysqld = /usr/local/bin/safe_mysqld mysqladmin = /usr/local/bin/mysqladmin user = multi_admin password = multipass [mysqld2] socket = /tmp/mysql.sock2 port = 3307 pid-file = /usr/local/mysql/var2/hostname.pid2 datadir = /usr/local/mysql/var2 language = /usr/local/share/mysql/english user = john [mysqld3] socket = /tmp/mysql.sock3 port = 3308 pid-file = /usr/local/mysql/var3/hostname.pid3 datadir = /usr/local/mysql/var3 language = /usr/local/share/mysql/swedish user = monty [mysqld4] socket = /tmp/mysql.sock4 port = 3309 pid-file = /usr/local/mysql/var4/hostname.pid4 datadir = /usr/local/mysql/var4 language = /usr/local/share/mysql/estonia user = tonu [mysqld6] socket = /tmp/mysql.sock6 port = 3311 pid-file = /usr/local/mysql/var6/hostname.pid6 datadir = /usr/local/mysql/var6 language = /usr/local/share/mysql/japanese user = jani @end example @xref{Option files}. @node myisampack, mysqld-max, mysqld_multi, Server-Side Scripts @subsection @code{myisampack}, MySQL の圧縮された読み込み専用テーブルジェネレータ @cindex compressed tables @cindex tables, compressed @cindex MyISAM, compressed tables @cindex @code{myisampack} @cindex @code{pack_isam} @code{myisampack} is used to compress MyISAM tables, and @code{pack_isam} is used to compress ISAM tables. Because ISAM tables are deprecated, we will only discuss @code{myisampack} here, but everything said about @code{myisampack} should also be true for @code{pack_isam}. @code{myisampack} はテーブル内の各項目を別々に圧縮するように働きます。展開のため の情報は、テーブルがオープンされた時にメモリに読まれます。これは、正確に1レコー ドだけを展開する必要があるような、個々のレコードへのアクセス時にとても良 い性能を与えます。MSDOS 上の Stacker 使用時のように、ディスクブロックは そんなに大きくありません。 通常、@code{myisampack} はデータファイルを 40〜70% にパックします。 MySQL は圧縮されたテーブルでメモリマップ (@code{mmap()}) を使用します。 @code{mmap()} が働かない場合は、通常のファイルの読み書きを使用します。 Please note the following: @itemize @bullet @item パック後、テーブルは読み込み専用になります。 This is generally intended (such as when accessing packed tables on a CD). Also allowing writes to a packed table is on our TODO list but with low priority. @item @code{myisampack} can also pack @code{BLOB} or @code{TEXT} columns. The older @code{pack_isam} (for @code{ISAM} tables) can not do this. @end itemize @code{myisampack} is invoked like this: @example shell> myisampack [options] filename ... @end example それぞれのファイル名はインデックスファイル(@file{.MYI})の名前です。 もしデータディレクトリにカレントディレクトリを移動していないなら、 ファイルのパスを指定しなくてはなりません。@file{.MYI} 拡張子は 省略することが可能です。 @code{myisampack} は以下のオプションをサポートします: @table @code @item -b, --backup @code{tbl_name.OLD} としてバックアップを作成します. @item -#, --debug=debug_options デバック出力。@code{debug_options} は @code{'d:t:o,filename'}. @item -f, --force 一時ファイルが存在していようが、サイズが大きくなろうが、強制的にテーブルを パックします。 @code{myisampack} はテーブルを圧縮している間、 一時ファイルを @file{tbl_name.TMD} という名前で作成します。 もし @code{myisampack} を途中で kill した場合、 @file{.TMD} ファイルが消されて いない事があります。通常、@code{myisampack} は @file{tbl_name.TMD} ファイルが 既に存在する場合はエラーで終了します。 @code{--force} を使用すると、 @code{myisampack} はそのような場合でもテーブルをパックします。 @item -?, --help ヘルプメッセージを出力して終了。 @item -j big_tbl_name, --join=big_tbl_name 全てのテーブルをコマンドラインで指定した @code{big_tbl_name} 一つに まとめます。結合される全てのテーブル定義は同じでなければなりません (同じ項目名、同じ項目型、同じインデックス、等) @item -p #, --packlength=# Specify the record length storage size, in bytes. The value should be 1, 2, or 3. (@code{myisampack} stores all rows with length pointers of 1, 2, or 3 bytes. In most normal cases, @code{myisampack} can determine the right length value before it begins packing the file, but it may notice during the packing process that it could have used a shorter length. In this case, @code{myisampack} will print a note that the next time you pack the same file, you could use a shorter record length.) @item -s, --silent Silent mode. Write output only when errors occur. @item -t, --test Don't actually pack table, just test packing it. @item -T dir_name, --tmp_dir=dir_name Use the named directory as the location in which to write the temporary table. @item -v, --verbose Verbose mode. Write information about progress and packing result. @item -V, --version Display version information and exit. @item -w, --wait Wait and retry if table is in use. If the @code{mysqld} server was invoked with the @code{--skip-external-locking} option, it is not a good idea to invoke @code{myisampack} if the table might be updated during the packing process. @end table @cindex examples, compressed tables The sequence of commands shown here illustrates a typical table compression session: @example shell> ls -l station.* -rw-rw-r-- 1 monty my 994128 Apr 17 19:00 station.MYD -rw-rw-r-- 1 monty my 53248 Apr 17 19:00 station.MYI -rw-rw-r-- 1 monty my 5767 Apr 17 19:00 station.frm shell> myisamchk -dvv station MyISAM file: station Isam-version: 2 Creation time: 1996-03-13 10:08:58 Recover time: 1997-02-02 3:06:43 Data records: 1192 Deleted blocks: 0 Datafile: Parts: 1192 Deleted data: 0 Datafile pointer (bytes): 2 Keyfile pointer (bytes): 2 Max datafile length: 54657023 Max keyfile length: 33554431 Recordlength: 834 Record format: Fixed length table description: Key Start Len Index Type Root Blocksize Rec/key 1 2 4 unique unsigned long 1024 1024 1 2 32 30 multip. text 10240 1024 1 Field Start Length Type 1 1 1 2 2 4 3 6 4 4 10 1 5 11 20 6 31 1 7 32 30 8 62 35 9 97 35 10 132 35 11 167 4 12 171 16 13 187 35 14 222 4 15 226 16 16 242 20 17 262 20 18 282 20 19 302 30 20 332 4 21 336 4 22 340 1 23 341 8 24 349 8 25 357 8 26 365 2 27 367 2 28 369 4 29 373 4 30 377 1 31 378 2 32 380 8 33 388 4 34 392 4 35 396 4 36 400 4 37 404 1 38 405 4 39 409 4 40 413 4 41 417 4 42 421 4 43 425 4 44 429 20 45 449 30 46 479 1 47 480 1 48 481 79 49 560 79 50 639 79 51 718 79 52 797 8 53 805 1 54 806 1 55 807 20 56 827 4 57 831 4 shell> myisampack station.MYI Compressing station.MYI: (1192 records) - Calculating statistics normal: 20 empty-space: 16 empty-zero: 12 empty-fill: 11 pre-space: 0 end-space: 12 table-lookups: 5 zero: 7 Original trees: 57 After join: 17 - Compressing file 87.14% shell> ls -l station.* -rw-rw-r-- 1 monty my 127874 Apr 17 19:00 station.MYD -rw-rw-r-- 1 monty my 55296 Apr 17 19:04 station.MYI -rw-rw-r-- 1 monty my 5767 Apr 17 19:00 station.frm shell> myisamchk -dvv station MyISAM file: station Isam-version: 2 Creation time: 1996-03-13 10:08:58 Recover time: 1997-04-17 19:04:26 Data records: 1192 Deleted blocks: 0 Datafile: Parts: 1192 Deleted data: 0 Datafilepointer (bytes): 3 Keyfile pointer (bytes): 1 Max datafile length: 16777215 Max keyfile length: 131071 Recordlength: 834 Record format: Compressed table description: Key Start Len Index Type Root Blocksize Rec/key 1 2 4 unique unsigned long 10240 1024 1 2 32 30 multip. text 54272 1024 1 Field Start Length Type Huff tree Bits 1 1 1 constant 1 0 2 2 4 zerofill(1) 2 9 3 6 4 no zeros, zerofill(1) 2 9 4 10 1 3 9 5 11 20 table-lookup 4 0 6 31 1 3 9 7 32 30 no endspace, not_always 5 9 8 62 35 no endspace, not_always, no empty 6 9 9 97 35 no empty 7 9 10 132 35 no endspace, not_always, no empty 6 9 11 167 4 zerofill(1) 2 9 12 171 16 no endspace, not_always, no empty 5 9 13 187 35 no endspace, not_always, no empty 6 9 14 222 4 zerofill(1) 2 9 15 226 16 no endspace, not_always, no empty 5 9 16 242 20 no endspace, not_always 8 9 17 262 20 no endspace, no empty 8 9 18 282 20 no endspace, no empty 5 9 19 302 30 no endspace, no empty 6 9 20 332 4 always zero 2 9 21 336 4 always zero 2 9 22 340 1 3 9 23 341 8 table-lookup 9 0 24 349 8 table-lookup 10 0 25 357 8 always zero 2 9 26 365 2 2 9 27 367 2 no zeros, zerofill(1) 2 9 28 369 4 no zeros, zerofill(1) 2 9 29 373 4 table-lookup 11 0 30 377 1 3 9 31 378 2 no zeros, zerofill(1) 2 9 32 380 8 no zeros 2 9 33 388 4 always zero 2 9 34 392 4 table-lookup 12 0 35 396 4 no zeros, zerofill(1) 13 9 36 400 4 no zeros, zerofill(1) 2 9 37 404 1 2 9 38 405 4 no zeros 2 9 39 409 4 always zero 2 9 40 413 4 no zeros 2 9 41 417 4 always zero 2 9 42 421 4 no zeros 2 9 43 425 4 always zero 2 9 44 429 20 no empty 3 9 45 449 30 no empty 3 9 46 479 1 14 4 47 480 1 14 4 48 481 79 no endspace, no empty 15 9 49 560 79 no empty 2 9 50 639 79 no empty 2 9 51 718 79 no endspace 16 9 52 797 8 no empty 2 9 53 805 1 17 1 54 806 1 3 9 55 807 20 no empty 3 9 56 827 4 no zeros, zerofill(2) 2 9 57 831 4 no zeros, zerofill(1) 2 9 @end example The information printed by @code{myisampack} is described here: @table @code @item normal The number of columns for which no extra packing is used. @item empty-space The number of columns containing values that are only spaces; these will occupy 1 bit. @item empty-zero The number of columns containing values that are only binary 0's; these will occupy 1 bit. @item empty-fill The number of integer columns that don't occupy the full byte range of their type; these are changed to a smaller type (for example, an @code{INTEGER} column may be changed to @code{MEDIUMINT}). @item pre-space The number of decimal columns that are stored with leading spaces. In this case, each value will contain a count for the number of leading spaces. @item end-space The number of columns that have a lot of trailing spaces. In this case, each value will contain a count for the number of trailing spaces. @item table-lookup The column had only a small number of different values, which were converted to an @code{ENUM} before Huffman compression. @item zero The number of columns for which all values are zero. @item Original trees The initial number of Huffman trees. @item After join The number of distinct Huffman trees left after joining trees to save some header space. @end table After a table has been compressed, @code{myisamchk -dvv} prints additional information about each field: @table @code @item Type The field type may contain the following descriptors: @table @code @item constant All rows have the same value. @item no endspace Don't store endspace. @item no endspace, not_always Don't store endspace and don't do end space compression for all values. @item no endspace, no empty Don't store endspace. Don't store empty values. @item table-lookup The column was converted to an @code{ENUM}. @item zerofill(n) The most significant @code{n} bytes in the value are always 0 and are not stored. @item no zeros Don't store zeros. @item always zero 0 values are stored in 1 bit. @end table @item Huff tree The Huffman tree associated with the field. @item Bits The number of bits used in the Huffman tree. @end table After you have run @code{pack_isam}/@code{myisampack} you must run @code{isamchk}/@code{myisamchk} to re-create the index. At this time you can also sort the index blocks and create statistics needed for the MySQL optimiser to work more efficiently: @example myisamchk -rq --analyze --sort-index table_name.MYI isamchk -rq --analyze --sort-index table_name.ISM @end example After you have installed the packed table into the MySQL database directory you should do @code{mysqladmin flush-tables} to force @code{mysqld} to start using the new table. If you want to unpack a packed table, you can do this with the @code{--unpack} option to @code{isamchk} or @code{myisamchk}. @node mysqld-max, , myisampack, Server-Side Scripts @subsection @code{mysqld-max}, An Extended @code{mysqld} Server @cindex @code{mysqld-max} @code{mysqld-max} is the MySQL server (@code{mysqld}) configured with the following configure options: @multitable @columnfractions .30 .45 @item @strong{Option} @tab @strong{Comment} @item --with-server-suffix=-max @tab Add a suffix to the @code{mysqld} version string. @item --with-innodb @tab Support for InnoDB tables. @item --with-bdb @tab Support for Berkeley DB (BDB) tables @item CFLAGS=-DUSE_SYMDIR @tab Symbolic links support for Windows. @end multitable You can find the MySQL-max binaries at @uref{http://www.mysql.com/downloads/mysql-max-3.23.html}. The Windows MySQL binary distributions includes both the standard @code{mysqld.exe} binary and the @code{mysqld-max.exe} binary. @uref{http://www.mysql.com/downloads/mysql-3.23.html}. @xref{Windows installation}. Note that as InnoDB and Berkeley DB are not available for all platforms, some of the @code{Max} binaries may not have support for both of these. You can check which table types are supported by doing the following query: @example mysql> SHOW VARIABLES LIKE "have_%"; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | have_bdb | YES | | have_innodb | NO | | have_isam | YES | | have_raid | NO | | have_openssl | NO | +---------------+-------+ @end example The meaning of the values are: @multitable @columnfractions .15 .85 @item @strong{Value} @tab @strong{Meaning} @item @code{YES} @tab The option is activated and usable. @item @code{NO} @tab MySQL is not compiled with support for this option. @item @code{DISABLED} @tab The xxxx option is disabled because one started @code{mysqld} with @code{--skip-xxxx} or because one didn't start @code{mysqld} with all needed options to enable the option. In this case the @code{hostname.err} file should contain a reason for why the option is disabled. @end multitable @strong{Note}: To be able to create InnoDB tables you @strong{must} edit your startup options to include at least the @code{innodb_data_file_path} option. @xref{InnoDB start}. To get better performance for BDB tables, you should add some configuration options for these too. @xref{BDB start}. @code{safe_mysqld} will automatically try to start any @code{mysqld} binary with the @code{-max} suffix. This makes it very easy to test out a another @code{mysqld} binary in an existing installation. Just run @code{configure} with the options you want and then install the new @code{mysqld} binary as @code{mysqld-max} in the same directory where your old @code{mysqld} binary is. @xref{safe_mysqld, , @code{safe_mysqld}}. The @code{mysqld-max} RPM uses the above mentioned @code{safe_mysqld} feature. It just installs the @code{mysqld-max} executable and @code{safe_mysqld} will automatically use this executable when @code{safe_mysqld} is restarted. The following table shows which table types our standard MySQL-Max binaries includes: @multitable @columnfractions .15 .10 .10 @item @strong{System} @tab @code{BDB} @tab @code{InnoDB} @item AIX 4.3 @tab N @tab Y @item HP-UX 11.0 @tab N @tab Y @item Linux-Alpha @tab N @tab Y @item Linux-Intel @tab Y @tab Y @item Linux-IA64 @tab N @tab Y @item Solaris-Intel @tab N @tab Y @item Solaris-SPARC @tab Y @tab Y @item Caldera (SCO) OSR5 @tab Y @tab Y @item UnixWare @tab Y @tab Y @item Windows/NT @tab Y @tab Y @end multitable @node Client-Side Scripts, Log Files, Server-Side Scripts, MySQL Database Administration @section MySQL Client-Side Scripts and Utilities @menu * Client-Side Overview:: Overview of the Client-Side Scripts and Utilities * mysql:: The Command-line Tool * mysqladmin:: @code{mysqladmin}, Administrating a MySQL Server * Using mysqlcheck:: Using @code{mysqlcheck} for Table Maintenance and Crash Recovery * mysqldump:: @code{mysqldump}, Dumping Table Structure and Data * mysqlhotcopy:: @code{mysqlhotcopy}, Copying MySQL Databases and Tables * mysqlimport:: @code{mysqlimport}, Importing Data from Text Files * mysqlshow:: @code{mysqlshow}, Showing Databases, Tables, and Columns * mysql_config:: @code{mysql_config}, Get compile options for compiling clients * perror:: @code{perror}, Explaining Error Codes * Batch Commands:: How to Run SQL Commands from a Text File @end menu @node Client-Side Overview, mysql, Client-Side Scripts, Client-Side Scripts @subsection Overview of the Client-Side Scripts and Utilities @cindex environment variables @cindex programs, list of All MySQL clients that communicate with the server using the @code{mysqlclient} library use the following environment variables: @tindex @code{MYSQL_UNIX_PORT} environment variable @tindex environment variable, @code{MYSQL_UNIX_PORT} @tindex @code{MYSQL_TCP_PORT} environment variable @tindex environment variable, @code{MYSQL_TCP_PORT} @tindex @code{MYSQL_PWD} environment variable @tindex environment variable, @code{MYSQL_PWD} @tindex @code{MYSQL_DEBUG} environment variable @tindex environment variable, @code{MYSQL_DEBUG} @multitable @columnfractions .25 .60 @item @strong{Name} @tab @strong{Description} @item @code{MYSQL_UNIX_PORT} @tab The default socket; used for connections to @code{localhost} @item @code{MYSQL_TCP_PORT} @tab The default TCP/IP port @item @code{MYSQL_PWD} @tab The default password @item @code{MYSQL_DEBUG} @tab Debug-trace options when debugging @item @code{TMPDIR} @tab The directory where temporary tables/files are created @end multitable Use of @code{MYSQL_PWD} is insecure. @xref{Connecting}. @tindex @code{MYSQL_HISTFILE} environment variable @tindex environment variable, @code{MYSQL_HISTFILE} @tindex @code{HOME} environment variable @tindex environment variable, @code{HOME} @cindex history file @cindex command-line history @tindex .mysql_history file The @file{mysql} client uses the file named in the @code{MYSQL_HISTFILE} environment variable to save the command-line history. The default value for the history file is @file{$HOME/.mysql_history}, where @code{$HOME} is the value of the @code{HOME} environment variable. @xref{Environment variables}. All MySQL programs take many different options. However, every MySQL program provides a @code{--help} option that you can use to get a full description of the program's different options. For example, try @code{mysql --help}. You can override default options for all standard client programs with an option file. @ref{Option files}. The following list briefly describes the client-side MySQL programs: @table @code @cindex @code{msql2mysql} @item msql2mysql A shell script that converts @code{mSQL} programs to MySQL. It doesn't handle all cases, but it gives a good start when converting. @cindex @code{mysqlaccess} @item mysqlaccess A script that checks the access privileges for a host, user, and database combination. @cindex @code{mysqladmin} @item mysqladmin Utility for performing administrative operations, such as creating or dropping databases, reloading the grant tables, flushing tables to disk, and reopening log files. @code{mysqladmin} can also be used to retrieve version, process, and status information from the server. @xref{mysqladmin, , @code{mysqladmin}}. @cindex @code{mysqldump} @item mysqldump Dumps a MySQL database into a file as SQL statements or as tab-separated text files. Enhanced freeware originally by Igor Romanenko. @xref{mysqldump, , @code{mysqldump}}. @cindex @code{mysqlimport} @item mysqlimport Imports text files into their respective tables using @code{LOAD DATA INFILE}. @xref{mysqlimport, , @code{mysqlimport}}. @cindex @code{mysqlshow} @item mysqlshow Displays information about databases, tables, columns, and indexes. @cindex @code{replace} @item replace A utility program that is used by @code{msql2mysql}, but that has more general applicability as well. @code{replace} changes strings in place in files or on the standard input. Uses a finite state machine to match longer strings first. Can be used to swap strings. For example, this command swaps @code{a} and @code{b} in the given files: @example shell> replace a b b a -- file1 file2 ... @end example @end table @node mysql, mysqladmin, Client-Side Overview, Client-Side Scripts @subsection @code{mysql}, コマンドラインツール @cindex command-line tool @cindex tools, command-line @cindex scripts @cindex @code{mysql} @code{mysql} はシンプルな SQL shell です(GNU @code{readline} を持っています). これは対話モードと、非対話モードを持っています。 対話モードで使用された場合、 クエリの結果は ASCII テーブルのフォーマットで与えられます。 非対話モードで使用された場合(例えばフィルターとして)、結果はタブ区切りの フォーマットで返ります。 (出力フォーマットはコマンドラインのオプションで変更できます) 以下のようにしてスクリプトを実行できます： @example shell> mysql database < script.sql > output.tab @end example もしクライアントでメモリー不足の問題が出た場合、@code{--quick} オプションを 使用します！ これは @code{mysql} に、結果セットを取得する際に、 @code{mysql_store_result()} ではなく @code{mysql_use_result()} を 使用させます。 @code{mysql} の使用はとても簡単です： @code{mysql database} や @code{mysql --user=user_name --password=your_password d atabase} のようにしてはじめます。 SQL 文を入力し、一文を @samp{;}, @samp{\g} or @samp{\G} で終え、 RETURN/ENTER を押します。 @cindex @code{mysql} command-line options @cindex command-line options, @code{mysql} @cindex options, command-line, @code{mysql} @cindex startup parameters, @code{mysql} @code{mysql} は以下のオプションをサポートします： @table @code @cindex @code{help}, @code{mysql} option @item -?, --help help を表示して終了 @cindex @code{no-auto-rehash}, @code{mysql} option @item -A, --no-auto-rehash 自動リハッシュをしない。 テーブルとフィールドの取得には 'rehash' を 使用しなくてはなりません。 これは @code{mysql} の起動を速くします。 @cindex @code{prompt}, @code{mysql} option @item --prompt=... Set the mysql prompt to specified format. @cindex @code{no-beep}, @code{mysql} option @item -b, --no-beep Turn off beep-on-error. @cindex @code{batch}, @code{mysql} option @item -B, --batch 結果をタブ区切り、１レコードは１行で出力します。 history ファイルは使用しません。 @cindex @code{character-sets-dir}, @code{mysql} option @item --character-sets-dir=... Directory where character sets are located. @cindex @code{compress}, @code{mysql} option @item -C, --compress サーバー・クライアント間の通信を圧縮します @cindex @code{debug}, @code{mysql} option @item -#, --debug[=...] デバッグログ。 デフォルトは 'd:t:o,/tmp/mysql.trace' @cindex @code{database}, @code{mysql} option @item -D, --database=... 使用するデータベース。 これは @code{my.cnf} ファイルが便利です @cindex @code{default-character-set}, @code{mysql} option @item --default-character-set=... Set the default character set. @cindex @code{execute}, @code{mysql} option @item -e, --execute=... コマンドを実行して終了。 (Output like with --batch) @cindex @code{vertical}, @code{mysql} option @item -E, --vertical 垂直にレコードを出力します。 このオプションを指定していなくても、 SQL 文を @code{\G} で終了した場合、同じように垂直に出力します。 @cindex @code{force}, @code{mysql} option @item -f, --force SQL エラーがおきたとしても、処理を続けます @cindex @code{no-named-commands}, @code{mysql} option @item -g, --no-named-commands Named commands are disabled. Use \* form only, or use named commands only in the beginning of a line ending with a semicolon (@samp{;}). Since Version 10.9, the client now starts with this option @strong{enabled} by default! With the -g option, long format commands will still work from the first line, however. @cindex @code{enable-named-commands}, @code{mysql} option @item -G, --enable-named-commands Named commands are @strong{enabled}. Long format commands are allowed as well as shortened \* commands. @cindex @code{ignore-space}, @code{mysql} option @item -i, --ignore-space 関数名の後ろについたスペースを無視します @cindex @code{host}, @code{mysql} option @item -h, --host=... 指定したホストに接続します @cindex @code{html}, @code{mysql} option @item -H, --html 結果を HTML フォーマットで返します @cindex @code{xml}, @code{mysql} option @item -X, --xml Produce XML output. @cindex @code{skip-line-numbers}, @code{mysql} option @item -L, --skip-line-numbers エラーの起きた行の番号を書きません。 これはエラーメッセージを含んだ結果を 比較する場合に便利です。 @cindex @code{no-pager}, @code{mysql} option @item --no-pager Disable pager and print to stdout. See interactive help (\h) also. @cindex @code{no-tee}, @code{mysql} option @item --no-tee Disable outfile. See interactive help (\h) also. @cindex @code{unbuffered}, @code{mysql} option @item -n, --unbuffered それぞれのクエリ毎にバッファをフラッシュします @cindex @code{skip-column-names}, @code{mysql} option @item -N, --skip-column-names 結果に、フィールド名を書き出しません。 @cindex @code{set-variable}, @code{mysql} option @item -O, --set-variable var=option 変数に値をセットします。 @code{--help} lists variables. Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--var=option} on its own. @cindex @code{one-database}, @code{mysql} option @item -o, --one-database デフォルトのデータベースのみ更新します。 これは update ログファイルを 使用して更新する場合、他のデータベースの更新を避けたい時に便利です。 @cindex @code{pager}, @code{mysql} option @item @code{--pager[=...]} Output type. Default is your @code{ENV} variable @code{PAGER}. Valid pagers are less, more, cat [> filename], etc. See interactive help (\h) also. This option does not work in batch mode. Pager works only in Unix. @cindex @code{password}, @code{mysql} option @item -p[password], --password[=...] サーバーに接続する際のパスワード。 もしパスワードがコマンドラインに 指定されていなかった場合、tty 上でパスワードが問い合わされます。 @code{-p} を使用する場合、このオプションとパスワードの間には スペースが不要だということに注意してください。 @cindex @code{port}, @code{mysql} option @item -P port_num, --port=port_num 接続に使用する TCP/IP ポート番号 @cindex @code{protocol}, @code{mysql} option @item @code{--protocol=(TCP | SOCKET | PIPE | MEMORY)} To specify the connect protocol to use. New in MySQL 4.1. @cindex @code{quick}, @code{mysql} option @item -q, --quick 結果をキャッシュせず、一レコードづつ出力します。 これはもし出力を中止した場合、サーバーを遅くします。 ヒストリファイルは使用しません。 @cindex @code{raw}, @code{mysql} option @item -r, --raw エスケープ処理をしないで値を書き出します。 @code{--batch} とともに使用されます @cindex @code{reconnect}, @code{mysql} option @item --reconnect If the connection is lost, automatically try to reconnect once to the server. @cindex @code{silent}, @code{mysql} option @item -s, --silent 静粛モード @cindex @code{socket}, @code{mysql} option @item -S --socket=... 接続に使用する ソケットファイル @cindex @code{table}, @code{mysql} option @item -t --table 表の形式で出力します。 これは batch モード以外でのデフォルトです。 @cindex @code{debug-info}, @code{mysql} option @item -T, --debug-info Print some debug information at exit. @cindex @code{tee}, @code{mysql} option @item --tee=... Append everything into outfile. See interactive help (\h) also. Does not work in batch mode. @cindex @code{user}, @code{mysql} option @item -u, --user=# ログインユーザー名 @cindex @code{safe-updates}, @code{mysql} option @item -U, --safe-updates[=#], --i-am-a-dummy[=#] キーを使用する @code{UPDATE} and @code{DELETE} のみを行います。 これは後述します。 このオプションをもし @code{my.cnf} に書いている場合は、 @code{--safe-updates=0} でこのオプションをリセットできます。 @cindex @code{verbose}, @code{mysql} option @item -v, --verbose 冗長出力。 (-v -v -v は表形式の出力を与える) @cindex @code{version}, @code{mysql} option @item -V, --version バージョンを表示して終了 @cindex @code{wait}, @code{mysql} option @item -w, --wait もし接続が落ちた場合、中断しないで、待って、再試行します。 @end table You can also set the following variables with @code{-O} or @code{--set-variable}; please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--var=option} on its own: @cindex timeout, @code{connect_timeout} variable @cindex @code{connect_timeout} variable @cindex @code{max_allowed_packet} @cindex @code{net_buffer_length} @cindex @code{select_limit} @cindex @code{max_join_size} @multitable @columnfractions .25 .10 .65 @item @strong{Variable Name} @tab @strong{Default} @tab @strong{Description} @item connect_timeout @tab 0 @tab Number of seconds before timeout connection. @item max_allowed_packet @tab 16777216 @tab Max packetlength to send/receive from to server @item net_buffer_length @tab 16384 @tab Buffer for TCP/IP and socket communication @item select_limit @tab 1000 @tab Automatic limit for SELECT when using --i-am-a-dummy @item max_join_size @tab 1000000 @tab Automatic limit for rows in a join when using --i-am-a-dummy. @end multitable If the @code{mysql} client loses connection to the server while sending it a query, it will immediately and automatically try to reconnect once to the server and send the query again. Note that even if it succeeds in reconnecting, as your first connection has ended, all your previous session objects are lost : temporary tables, user and session variables. Therefore, the above behaviour may be dangerous for you, like in this example where the server was shut down and restarted without you knowing it : @example mysql> set @@a=1; Query OK, 0 rows affected (0.05 sec) mysql> insert into t values(@@a); ERROR 2006: MySQL server has gone away No connection. Trying to reconnect... Connection id: 1 Current database: test Query OK, 1 row affected (1.30 sec) mysql> select * from t; +------+ | a | +------+ | NULL | +------+ 1 row in set (0.05 sec) @end example The @code{@@a} user variable has been lost with the connection, and after the reconnection it is undefined. To protect from this risk, you can start the @code{mysql} client with the @code{--disable-reconnect} option. もしコマンドラインで 'help' と打った場合、@code{mysql} はサポートする コマンドを表示します： @cindex commands, list of @example mysql> help MySQL commands: help (\h) Display this text. ? (\h) Synonym for `help'. clear (\c) Clear command. connect (\r) Reconnect to the server. Optional arguments are db and host. edit (\e) Edit command with $EDITOR. ego (\G) Send command to mysql server, display result vertically. exit (\q) Exit mysql. Same as quit. go (\g) Send command to mysql server. nopager (\n) Disable pager, print to stdout. notee (\t) Don't write into outfile. pager (\P) Set PAGER [to_pager]. Print the query results via PAGER. print (\p) Print current command. prompt (\R) Change your mysql prompt. quit (\q) Quit mysql. rehash (\#) Rebuild completion hash. source (\.) Execute a SQL script file. Takes a file name as an argument. status (\s) Get status information from the server. tee (\T) Set outfile [to_outfile]. Append everything into given outfile. use (\u) Use another database. Takes database name as argument. @end example The @code{pager} command works only in Unix. @cindex @code{status} command @code{status} コマンドは、今使用している 接続とサーバーについての情報をいくつか表示します。 もし @code{--safe-updates} モードで使用している場合、 @code{status} は あなたのクエリに影響する @code{mysql} 変数の値を表示します。 @cindex @code{safe-mode} command 初心者に便利な起動オプション(MySQL バージョン 3.23.11 で導入されました)は、 @code{--safe-updates} あるいは @code{--i-am-a-dummy} です。 ( これは @code{DELETE FROM table_name} を @code{WHERE} 節を忘れて 実行しようとした場合のためにあります。) このオプションが使用されると、 @code{mysql} は接続時に MySQL サーバーに 以下のようなコマンドを送ります： @example SET SQL_SAFE_UPDATES=1,SQL_SELECT_LIMIT=#select_limit#, SQL_MAX_JOIN_SIZE=#max_join_size#" @end example ここで @code{#select_limit#} と @code{#max_join_size#} は変数で これらは @code{mysql} コマンドからセット可能です。 @xref{SET OPTION, @code{SET}}. この効果は： @itemize @bullet @item もし @code{WHERE} 節でキーを使用していなければ、@code{UPDATE} や @code{DELETE} は許可されません。 しかし、 @code{LIMIT} を使用すれば @code{UPDATE/DELETE} を 強制実行できます： @example UPDATE table_name SET not_key_column=# WHERE not_key_column=# LIMIT 1; @end example @item 全ての多きな結果は自動的に @code{#select_limit#} レコードまでに抑えられます。 @item 評価に @code{#max_join_size} 以上の行を必要とするであろう @code{SELECT} は 中断されます。 @end itemize Some useful hints about the @code{mysql} client: Some data is much more readable when displayed vertically, instead of the usual horizontal box type output. For example longer text, which includes new lines, is often much easier to be read with vertical output. @example mysql> SELECT * FROM mails WHERE LENGTH(txt) < 300 lIMIT 300,1\G *************************** 1. row *************************** msg_nro: 3068 date: 2000-03-01 23:29:50 time_zone: +0200 mail_from: Monty reply: monty@@no.spam.com mail_to: "Thimble Smith" sbj: UTF-8 txt: >>>>> "Thimble" == Thimble Smith writes: Thimble> Hi. I think this is a good idea. Is anyone familiar with UTF-8 Thimble> or Unicode? Otherwise, I'll put this on my TODO list and see what Thimble> happens. Yes, please do that. Regards, Monty file: inbox-jani-1 hash: 190402944 1 row in set (0.09 sec) @end example For logging, you can use the @code{tee} option. The @code{tee} can be started with option @code{--tee=...}, or from the command-line interactively with command @code{tee}. All the data displayed on the screen will also be appended into a given file. This can be very useful for debugging purposes also. The @code{tee} can be disabled from the command-line with command @code{notee}. Executing @code{tee} again starts logging again. Without a parameter the previous file will be used. Note that @code{tee} will flush the results into the file after each command, just before the command-line appears again waiting for the next command. Browsing, or searching the results in the interactive mode in Unix less, more, or any other similar program, is now possible with option @code{--pager[=...]}. Without argument, @code{mysql} client will look for environment variable PAGER and set @code{pager} to that. @code{pager} can be started from the interactive command-line with command @code{pager} and disabled with command @code{nopager}. The command takes an argument optionally and the @code{pager} will be set to that. Command @code{pager} can be called without an argument, but this requires that the option @code{--pager} was used, or the @code{pager} will default to stdout. @code{pager} works only in Unix, since it uses the popen() function, which doesn't exist in Windows. In Windows, the @code{tee} option can be used instead, although it may not be as handy as @code{pager} can be in some situations. A few tips about @code{pager}: @itemize @bullet @item You can use it to write to a file: @example mysql> pager cat > /tmp/log.txt @end example and the results will only go to a file. You can also pass any options for the programs that you want to use with the @code{pager}: @example mysql> pager less -n -i -S @end example @item From the above do note the option '-S'. You may find it very useful when browsing the results; try the option with horizontal output (end commands with '\g', or ';') and with vertical output (end commands with '\G'). Sometimes a very wide result set is hard to be read from the screen, with option -S to less you can browse the results within the interactive less from left to right, preventing lines longer than your screen from being continued to the next line. This can make the result set much more readable. You can swith the mode between on and off within the interactive less with '-S'. See the 'h' for more help about less. @item You can combine very complex ways to handle the results, for example the following would send the results to two files in two different directories, on two different hard-disks mounted on /dr1 and /dr2, yet let the results still be seen on the screen via less: @example mysql> pager cat | tee /dr1/tmp/res.txt | \ tee /dr2/tmp/res2.txt | less -n -i -S @end example @end itemize You can also combine the two functions above; have the @code{tee} enabled, @code{pager} set to 'less' and you will be able to browse the results in unix 'less' and still have everything appended into a file the same time. The difference between Unix @code{tee} used with the @code{pager} and the @code{mysql} client in-built @code{tee}, is that the in-built @code{tee} works even if you don't have the Unix @code{tee} available. The in-built @code{tee} also logs everything that is printed on the screen, where the Unix @code{tee} used with @code{pager} doesn't log quite that much. Last, but not least, the interactive @code{tee} is more handy to switch on and off, when you want to log something into a file, but want to be able to turn the feature off sometimes. @cindex @code{prompt} command From MySQL version 4.0.2 it is possible to change the prompt in the @code{mysql} command-line client. You can use the following prompt options: @c FIX these columnfractions have NOT been measured! @multitable @columnfractions .10 .50 @item @strong{Option} @tab @strong{Description} @item \v @tab mysqld version @item \d @tab database in use @item \h @tab host connected to @item \p @tab port connected on @item \u @tab username @item \U @tab full username@@host @item \\ @tab @samp{\} @item \n @tab new line break @item \t @tab tab @item \ @tab space @item \_ @tab space @item \R @tab military hour time (0-23) @item \r @tab standard hour time (1-12) @item \m @tab minutes @item \y @tab two digit year @item \Y @tab four digit year @item \D @tab full date format @item \s @tab seconds @item \w @tab day of the week in three letter format (Mon, Tue, ...) @item \P @tab am/pm @item \o @tab month in number format @item \O @tab month in three letter format (Jan, Feb, ...) @item \c @tab counter that counts up for each command you do @end multitable @samp{\} followed by any other letter just becomes that letter. You may set the prompt in the following places: @table @strong @item Environment Variable You may set the @code{MYSQL_PS1} environment variable to a prompt string. For example: @example shell> export MYSQL_PS1="(\u@@\h) [\d]> " @end example @item @file{my.cnf} @item @file{.my.cnf} You may set the @code{prompt} option in any MySQL configuration file, in the @code{mysql} group. For example: @example [mysql] prompt=(\u@@\h) [\d]>\_ @end example @item Command Line You may set the @code{--prompt} option on the command line to @code{mysql}. For example: @example shell> mysql --prompt="(\u@@\h) [\d]> " (user@@host) [database]> @end example @item Interactively You may also use the @code{prompt} (or @code{\R}) command to change your prompt interactively. For example: @example mysql> prompt (\u@@\h) [\d]>\_ PROMPT set to '(\u@@\h) [\d]>\_' (user@@host) [database]> (user@@host) [database]> prompt Returning to default PROMPT of mysql> mysql> @end example @end table @node mysqladmin, Using mysqlcheck, mysql, Client-Side Scripts @subsection @code{mysqladmin}, MySQL サーバーの管理 @cindex administration, server @cindex server administration @cindex @code{mysqladmin} 管理オペレーションを実行するためのユーティリティ。シンタックスは: @example shell> mysqladmin [OPTIONS] command [command-option] command ... @end example @code{mysqladmin --help} によって、オプションの一覧を手にいれることができます。 現在の @code{mysqladmin} は以下のコマンドをサポートします： @table @code @item create databasename 新しいデータベースの作成 @item drop databasename データベースとテーブルの全削除。 @item extended-status サーバーから拡張ステータスを取得。 @item flush-hosts キャッシュされている全ホストをフラッシュ。 @item flush-logs 全てのログをフラッシュ @item flush-tables 全てのテーブルをフラッシュ @item flush-privileges 許可テーブルの再読み込み (reload と同じ) @item kill id,id,... mysql スレッドの kill. @item password Set a new password. 古いパスワードを New-password に変更 @item ping @code{mysqld} が生きているかチェック @item processlist 現在活動中の mysql スレッドを表示 @item reload 権限テーブルの再読み込み @item refresh 全テーブルをフラッシュし、ログファイルを一度閉じて開きます。 @item shutdown サーバーをダウンさせます。 @item slave-start Start slave replication thread. @item slave-stop Stop slave replication thread. @item status サーバーから短いステータスを得ます。 @item variables 変数の表示 @item version サーバーからバージョンを得ます。 @end table 全てのコマンドは、ユニークなプレフィックスで省略可能です。 例えば： @example shell> mysqladmin proc stat +----+-------+-----------+----+-------------+------+-------+------+ | Id | User | Host | db | Command | Time | State | Info | +----+-------+-----------+----+-------------+------+-------+------+ | 6 | monty | localhost | | Processlist | 0 | | | +----+-------+-----------+----+-------------+------+-------+------+ Uptime: 10077 Threads: 1 Questions: 9 Slow queries: 0 Opens: 6 Flush tables: 1 Open tables: 2 Memory in use: 1092K Max memory used: 1116K @end example @cindex status command, results The @code{mysqladmin status} command result has the following columns: @cindex uptime @multitable @columnfractions .20 .65 @item @strong{Column} @tab @strong{Description} @item Uptime @tab MySQL サーバーの起動秒数 @cindex threads @item Threads @tab 稼働中のスレッド数 (clients). @cindex questions @item Questions @tab @code{mysqld} が開始してからのクライアントからのクエリ数 @cindex slow queries @item Slow queries @tab @code{long_query_time} 秒より時間のかかったクエリの数 @xref{Slow query log}. @cindex opens @item Opens @tab @code{mysqld} が開いたテーブル数 @cindex flush tables @cindex tables, flush @item Flush tables @tab Number of @code{flush ...}, @code{refresh}, and @code{reload} commands. @cindex open tables @item Open tables @tab 現在開かれているテーブルの数 @cindex memory use @item Memory in use @tab @code{mysqld} のコードによって直接割り当てられたメモリ (only available when MySQL is compiled with --with-debug=full). @cindex max memory used @item Max memory used @tab @code{mysqld} のコードによって直接割り当てられる最大メモリー量 (only available when MySQL is compiled with --with-debug=full). @end multitable If you do @code{mysqladmin shutdown} on a socket (in other words, on a the computer where @code{mysqld} is running), @code{mysqladmin} will wait until the MySQL @code{pid-file} is removed to ensure that the @code{mysqld} server has stopped properly. @node Using mysqlcheck, mysqldump, mysqladmin, Client-Side Scripts @subsection Using @code{mysqlcheck} for Table Maintenance and Crash Recovery Since MySQL version 3.23.38 you will be able to use a new checking and repairing tool for @code{MyISAM} tables. The difference to @code{myisamchk} is that @code{mysqlcheck} should be used when the @code{mysqld} server is running, where as @code{myisamchk} should be used when it is not. The benefit is that you no longer have to take the server down for checking or repairing your tables. @code{mysqlcheck} uses MySQL server commands @code{CHECK}, @code{REPAIR}, @code{ANALYZE} and @code{OPTIMIZE} in a convenient way for the user. There are three alternative ways to invoke @code{mysqlcheck}: @example shell> mysqlcheck [OPTIONS] database [tables] shell> mysqlcheck [OPTIONS] --databases DB1 [DB2 DB3...] shell> mysqlcheck [OPTIONS] --all-databases @end example So it can be used in a similar way as @code{mysqldump} when it comes to what databases and tables you want to choose. @code{mysqlcheck} does have a special feature compared to the other clients; the default behaviour, checking tables (-c), can be changed by renaming the binary. So if you want to have a tool that repairs tables by default, you should just copy @code{mysqlcheck} to your harddrive with a new name, @code{mysqlrepair}, or alternatively make a symbolic link to @code{mysqlrepair} and name the symbolic link as @code{mysqlrepair}. If you invoke @code{mysqlrepair} now, it will repair tables by default. The names that you can use to change @code{mysqlcheck} default behaviour are here: @example mysqlrepair: The default option will be -r mysqlanalyze: The default option will be -a mysqloptimize: The default option will be -o @end example The options available for @code{mysqlcheck} are listed here, please check what your version supports with @code{mysqlcheck --help}. @table @code @item -A, --all-databases Check all the databases. This will be same as --databases with all databases selected @item -1, --all-in-1 Instead of making one query for each table, execute all queries in 1 query separately for each database. Table names will be in a comma separated list. @item -a, --analyze Analyse given tables. @item --auto-repair If a checked table is corrupted, automatically fix it. Repairing will be done after all tables have been checked, if corrupted ones were found. @item -#, --debug=... Output debug log. Often this is 'd:t:o,filename' @item --character-sets-dir=... Directory where character sets are @item -c, --check Check table for errors @item -C, --check-only-changed Check only tables that have changed since last check or haven't been closed properly. @item --compress Use compression in server/client protocol. @item -?, --help Display this help message and exit. @item -B, --databases To check several databases. Note the difference in usage; in this case no tables are given. All name arguments are regarded as database names. @item --default-character-set=... Set the default character set @item -F, --fast Check only tables that hasn't been closed properly @item -f, --force Continue even if we get an sql-error. @item -e, --extended If you are using this option with CHECK TABLE, it will ensure that the table is 100 percent consistent, but will take a long time. If you are using this option with REPAIR TABLE, it will run an extended repair on the table, which may not only take a long time to execute, but may produce a lot of garbage rows also! @item -h, --host=... Connect to host. @item -m, --medium-check Faster than extended-check, but only finds 99.99 percent of all errors. Should be good enough for most cases. @item -o, --optimize Optimise table @item -p, --password[=...] Password to use when connecting to server. If password is not given it's solicited on the tty. @item -P port_num, --port=port_num Port number to use for TCP/IP connections. @item @code{--protocol=(TCP | SOCKET | PIPE | MEMORY)} To specify the connect protocol to use. New in MySQL 4.1. @item -q, --quick If you are using this option with CHECK TABLE, it prevents the check from scanning the rows to check for wrong links. This is the fastest check. If you are using this option with REPAIR TABLE, it will try to repair only the index tree. This is the fastest repair method for a table. @item -r, --repair Can fix almost anything except unique keys that aren't unique. @item -s, --silent Print only error messages. @item -S, --socket=... Socket file to use for connection. @item --tables Overrides option --databases (-B). @item -u, --user=# User for login if not current user. @item -v, --verbose Print info about the various stages. @item -V, --version Output version information and exit. @end table @node mysqldump, mysqlhotcopy, Using mysqlcheck, Client-Side Scripts @subsection @code{mysqldump}, データベースとテーブルから、構造とデータをダンプ @cindex dumping, databases @cindex databases, dumping @cindex tables, dumping @cindex backing up, databases @cindex @code{mysqldump} データベース、あるいは、バックアップ、他のSQLサーバー(MySQL サーバであ る必要はない)へのデータを移動を目的としたデータのまとまり、これらをダンプする ためのユーティリティ。ダンプは、テーブルの作成のための SQL 文を含みます。 サーバでバックアップを行なう場合、@code{mysqlhotcopy} を代わりに使用するこ とを考慮すべきです。 @xref{mysqlhotcopy, , @code{mysqlhotcopy}}. @example shell> mysqldump [OPTIONS] database [tables] OR mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...] OR mysqldump [OPTIONS] --all-databases [OPTIONS] @end example もしテーブルを指定せず、@code{--databases} や @code{--all-databases} を 使用しなかったなら、データベースの全てのテーブルがダンプされます。 @code{mysqldump --help} によって、オプションの一覧を手にいれることができます。 もし @code{mysqldump} を @code{--quick} や @code{--opt} なしで実行するならば、 @code{mysqldump} は結果を表示する前に、結果をメモリに全てロードすることに 注意してください。 これは大きなデータベースをダンプする際に問題になるでしょう。 Note that if you are using a new copy of the @code{mysqldump} program and you are going to do a dump that will be read into a very old MySQL server, you should not use the @code{--opt} or @code{-e} options. @code{mysqldump} は以下のオプションをサポートします： @table @code @item --add-locks Add @code{LOCK TABLES} before and @code{UNLOCK TABLE} after each table dump. (To get faster inserts into MySQL.) @item --add-drop-table Add a @code{drop table} before each create statement. @item -A, --all-databases Dump all the databases. This will be same as @code{--databases} with all databases selected. @item -a, --all Include all MySQL-specific create options. @item --allow-keywords Allow creation of column names that are keywords. This works by prefixing each column name with the table name. @item -c, --complete-insert Use complete insert statements (with column names). @item -C, --compress Compress all information between the client and the server if both support compression. @item -B, --databases To dump several databases. Note the difference in usage. In this case no tables are given. All name arguments are regarded as database names. @code{USE db_name;} will be included in the output before each new database. @item --delayed Insert rows with the @code{INSERT DELAYED} command. @item -e, --extended-insert Use the new multiline @code{INSERT} syntax. (Gives more compact and faster inserts statements.) @item -#, --debug[=option_string] Trace usage of the program (for debugging). @item --help Display a help message and exit. @item --fields-terminated-by=... @itemx --fields-enclosed-by=... @itemx --fields-optionally-enclosed-by=... @itemx --fields-escaped-by=... @itemx --lines-terminated-by=... These options are used with the @code{-T} option and have the same meaning as the corresponding clauses for @code{LOAD DATA INFILE}. @xref{LOAD DATA, , @code{LOAD DATA}}. @item -F, --flush-logs Flush log file in the MySQL server before starting the dump. @item -f, --force, Continue even if we get a SQL error during a table dump. @item -h, --host=.. Dump data from the MySQL server on the named host. The default host is @code{localhost}. @item -l, --lock-tables. Lock all tables before starting the dump. The tables are locked with @code{READ LOCAL} to allow concurrent inserts in the case of @code{MyISAM} tables. Please note that when dumping multiple databases, @code{--lock-tables} will lock tables for each database separately. So using this option will not guarantee your tables will be logically consistent between databases. Tables in different databases may be dumped in completely different states. @item -K, --disable-keys @code{/*!40000 ALTER TABLE tb_name DISABLE KEYS */;} and @code{/*!40000 ALTER TABLE tb_name ENABLE KEYS */;} will be put in the output. This will make loading the data into a MySQL 4.0 server faster as the indexes are created after all data are inserted. @item -n, --no-create-db @code{CREATE DATABASE /*!32312 IF NOT EXISTS*/ db_name;} will not be put in the output. The above line will be added otherwise, if a @code{--databases} or @code{--all-databases} option was given. @item -t, --no-create-info Don't write table creation information (the @code{CREATE TABLE} statement). @item -d, --no-data Don't write any row information for the table. This is very useful if you just want to get a dump of the structure for a table! @item --opt Same as @code{--quick --add-drop-table --add-locks --extended-insert --lock-tables}. Should give you the fastest possible dump for reading into a MySQL server. @item -pyour_pass, --password[=your_pass] The password to use when connecting to the server. If you specify no @samp{=your_pass} part, @code{mysqldump} you will be prompted for a password. @item -P port_num, --port=port_num Port number to use for TCP/IP connections. @item @code{--protocol=(TCP | SOCKET | PIPE | MEMORY)} To specify the connect protocol to use. New in MySQL 4.1. @item -q, --quick Don't buffer query, dump directly to stdout. Uses @code{mysql_use_result()} to do this. @item -Q, --quote-names Quote table and column names within @samp{`} characters. @item -r, --result-file=... Direct output to a given file. This option should be used in MSDOS, because it prevents new line @samp{\n} from being converted to @samp{\n\r} (new line + carriage return). @item --single-transaction This option issues a @code{BEGIN} SQL command before dumping data from server. It is mostly useful with @code{InnoDB} tables and @code{READ_COMMITTED} transaction isolation level, as in this mode it will dump the consistent state of the database at the time then @code{BEGIN} was issued without blocking any applications. When using this option you should keep in mind that only transactional tables will be dumped in a consistent state, e.g., any @code{MyISAM} or @code{HEAP} tables dumped while using this option may still change state. The @code{--single-transaction} option was added in version 4.0.2. This option is mutually exclusive with the @code{--lock-tables} option as @code{LOCK TABLES} already commits a previous transaction internally. @item -S /path/to/socket, --socket=/path/to/socket The socket file to use when connecting to @code{localhost} (which is the default host). @item --tables Overrides option --databases (-B). @item -T, --tab=path-to-some-directory Creates a @code{table_name.sql} file, that contains the SQL CREATE commands, and a @code{table_name.txt} file, that contains the data, for each give table. The format of the @file{.txt} file is made according to the @code{--fields-xxx} and @code{--lines--xxx} options. @strong{Note}: This option only works if @code{mysqldump} is run on the same machine as the @code{mysqld} daemon, and the user/group that @code{mysqld} is running as (normally user @code{mysql}, group @code{mysql}) needs to have permission to create/write a file at the location you specify. @item -u user_name, --user=user_name The MySQL user name to use when connecting to the server. The default value is your Unix login name. @item -O var=option, --set-variable var=option Set the value of a variable. The possible variables are listed below. Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--var=option} on its own. @item -v, --verbose Verbose mode. Print out more information on what the program does. @item -V, --version Print version information and exit. @item -w, --where='where-condition' Dump only selected records. Note that quotes are mandatory: @item -X, --xml Dumps a database as well formed XML @item -x, --first-slave Locks all tables across all databases. @example "--where=user='jimf'" "-wuserid>1" "-wuserid<1" @end example @item -O net_buffer_length=#, where # < 16M When creating multi-row-insert statements (as with option @code{--extended-insert} or @code{--opt}), @code{mysqldump} will create rows up to @code{net_buffer_length} length. If you increase this variable, you should also ensure that the @code{max_allowed_packet} variable in the MySQL server is bigger than the @code{net_buffer_length}. @end table The most normal use of @code{mysqldump} is probably for making a backup of whole databases. @xref{Backup}. @example mysqldump --opt database > backup-file.sql @end example You can read this back into MySQL with: @example mysql database < backup-file.sql @end example or @example mysql -e "source /patch-to-backup/backup-file.sql" database @end example However, it's also very useful to populate another MySQL server with information from a database: @example mysqldump --opt database | mysql ---host=remote-host -C database @end example It is possible to dump several databases with one command: @example mysqldump --databases database1 [database2 ...] > my_databases.sql @end example If all the databases are wanted, one can use: @example mysqldump --all-databases > all_databases.sql @end example @node mysqlhotcopy, mysqlimport, mysqldump, Client-Side Scripts @subsection @code{mysqlhotcopy}, Copying MySQL Databases and Tables @cindex dumping, databases @cindex databases, dumping @cindex tables, dumping @cindex backing up, databases @code{mysqlhotcopy} is a Perl script that uses @code{LOCK TABLES}, @code{FLUSH TABLES} and @code{cp} or @code{scp} to quickly make a backup of a database. It's the fastest way to make a backup of the database or single tables, but it can only be run on the same machine where the database directories are. @example mysqlhotcopy db_name [/path/to/new_directory] mysqlhotcopy db_name_1 ... db_name_n /path/to/new_directory mysqlhotcopy db_name./regex/ @end example @code{mysqlhotcopy} supports the following options: @table @code @item -?, --help Display a help screen and exit @item -u, --user=# User for database login @item -p, --password=# Password to use when connecting to server @item -P, --port=# Port to use when connecting to local server @item -S, --socket=# Socket to use when connecting to local server @item --allowold Don't abort if target already exists (rename it _old) @item --keepold Don't delete previous (now renamed) target when done @item --noindices Don't include full index files in copy to make the backup smaller and faster The indexes can later be reconstructed with @code{myisamchk -rq.}. @item --method=# Method for copy (@code{cp} or @code{scp}). @item -q, --quiet Be silent except for errors @item --debug Enable debug @item -n, --dryrun Report actions without doing them @item --regexp=# Copy all databases with names matching regexp @item --suffix=# Suffix for names of copied databases @item --checkpoint=# Insert checkpoint entry into specified db.table @item --flushlog Flush logs once all tables are locked. @item --tmpdir=# Temporary directory (instead of /tmp). @end table You can use @code{perldoc mysqlhotcopy} to get more complete documentation for @code{mysqlhotcopy}. @code{mysqlhotcopy} reads the groups @code{[client]} and @code{[mysqlhotcopy]} from the option files. To be able to execute @code{mysqlhotcopy} you need write access to the backup directory, the @code{SELECT} privilege for the tables you are about to copy and the MySQL @code{RELOAD} privilege (to be able to execute @code{FLUSH TABLES}). @node mysqlimport, mysqlshow, mysqlhotcopy, Client-Side Scripts @subsection @code{mysqlimport}, テキストファイルからデータを取り込む @cindex importing, data @cindex data, importing @cindex files, text @cindex text files, importing @cindex @code{mysqlimport} @code{mysqlimport} は、@code{LOAD DATA INFILE} SQL 構文を、 コマンドラインインターフェースで提供します。 @code{mysqlimport} のオプションのほとんどが、 @code{LOAD DATA INFILE} への同じオプションに対応します。 @xref{LOAD DATA, , @code{LOAD DATA}}. @code{mysqlimport} の実行は以下のようにします: @example shell> mysqlimport [options] database textfile1 [textfile2 ...] @end example @code{mysqlimport} は、コマンドラインの引数に与えられたファイル名の拡張子を取り、 拡張子を取った後の名前を、ファイルの内容を取り込むテーブルの名前とします。 例えば、@file{patient.txt}, @file{patient.text}, @file{patient} という ファイルは全て、@code{patient} とという名前のテーブルに取り込まれます。 @code{mysqlimport} は以下のオプションをサポートします: @table @code @item -c, --columns=... This option takes a comma-separated list of field names as an argument. The field list is used to create a proper @code{LOAD DATA INFILE} command, which is then passed to MySQL. @xref{LOAD DATA, , @code{LOAD DATA}}. @item -C, --compress クライアントとサーバーの両方が圧縮をサポートしているなら、 クライアント・サーバー間でやり取りされる全ての情報を圧縮します。 @item -#, --debug[=option_string] プログラムのトレース(デバッグ) @item -d, --delete テキストファイルを取り込む前にテーブルを空にします。 @item --fields-terminated-by=... @itemx --fields-enclosed-by=... @itemx --fields-optionally-enclosed-by=... @itemx --fields-escaped-by=... @itemx --lines-terminated-by=... これらのオプションは、@code{LOAD DATA INFILE} の対応する文節と同じ意味になります @xref{LOAD DATA, , @code{LOAD DATA}}. @item -f, --force エラーを無視します。例えば、テキストファイルを取り込むテーブルがない場合、 残りのファイルの処理に移ります。 @code{--force} がなければ、 テーブルがなければ @code{mysqlimport} は終了します。 @item --help ヘルプを表示して終了。 @item -h host_name, --host=host_name 名前を指定された MySQL サーバーにデータを取り入れます。 デフォルトでは @code{localhost}. @item -i, --ignore @code{--replace} オプションの説明を見てください。 @item -l, --lock-tables それぞれのテキストファイルを処理する前に、書き込まれる @strong{全ての}テーブルをロックします。 これは確実に、すべてのテーブルをサーバ上で同期させます。 @item -L, --local クライアントからの入力ファイルを読みます。 デフォルトでは、@code{localhost} に接続した場合、テキストファイルは サーバー上にあると仮定されます。(@code{localhost} はデフォルト値) @item -pyour_pass, --password[=your_pass] サーバーに接続するときに使用するパスワード。 もし @samp{=your_pass} のところにパスワードを書かなければ、 @code{mysqlimport} はパスワードのためのプロンプトをだします。 @item -P port_num, --port=port_num ホストに接続するための TCP/IP ポート番号。 (これは @code{localhost} を除くホストへの接続に使用します。 @code{localhost} へは、Unix ソケットを使用します。) @cindex @code{protocol}, @code{mysql} option @item @code{--protocol=(TCP | SOCKET | PIPE | MEMORY)} To specify the connect protocol to use. New in MySQL 4.1. @item -r, --replace @code{--replace} と @code{--ignore} オプションは、 入力されているレコードのユニークキーの値が、 既に存在しているレコードのユニークキーの値と同じ場合、 その入力されているデータの取り扱いを決定します。 もし @code{--replace} が指定されているなら、 既にあるレコードは新しく読まれたレコードに置き換えられます。 もし @code{--ignore} が指定されているなら、 入力された物は無視されます。 どちらのオプションも指定していない場合、 キーの値が重なっているとエラーを発し、 テキストファイルの残りの部分は無視されます。 @item -s, --silent 静粛モード。エラーだけ出力します。 @item -S /path/to/socket, --socket=/path/to/socket @code{localhost} への接続時に使用するソケットファイルを指定します。 @item -u user_name, --user=user_name サーバーの接続に使用する MySQL ユーザー名の指定。 デフォルトは、Unix のログイン名。 @item -v, --verbose 冗長モード。プログラムがしている事について多く出力します。 @item -V, --version バージョンを表示して終了。 @end table Here is a sample run using @code{mysqlimport}: @example $ mysql --version mysql Ver 9.33 Distrib 3.22.25, for pc-linux-gnu (i686) $ uname -a Linux xxx.com 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 i586 unknown $ mysql -e 'CREATE TABLE imptest(id INT, n VARCHAR(30))' test $ ed a 100 Max Sydow 101 Count Dracula . w imptest.txt 32 q $ od -c imptest.txt 0000000 1 0 0 \t M a x S y d o w \n 1 0 0000020 1 \t C o u n t D r a c u l a \n 0000040 $ mysqlimport --local test imptest.txt test.imptest: Records: 2 Deleted: 0 Skipped: 0 Warnings: 0 $ mysql -e 'SELECT * FROM imptest' test +------+---------------+ | id | n | +------+---------------+ | 100 | Max Sydow | | 101 | Count Dracula | +------+---------------+ @end example @node mysqlshow, mysql_config, mysqlimport, Client-Side Scripts @subsection @code{mysqlshow}, Showing Databases, Tables, and Columns @cindex databases, displaying @cindex displaying, database information @cindex tables, displaying @cindex columns, displaying @cindex showing, database information @code{mysqlshow} can be used to quickly look at which databases exist, their tables, and the table's columns. With the @code{mysql} program you can get the same information with the @code{SHOW} commands. @xref{SHOW}. @code{mysqlshow} is invoked like this: @example shell> mysqlshow [OPTIONS] [database [table [column]]] @end example @itemize @bullet @item If no database is given, all matching databases are shown. @item If no table is given, all matching tables in the database are shown. @item If no column is given, all matching columns and column types in the table are shown. @end itemize Note that in newer MySQL versions, you only see those database/tables/columns for which you have some privileges. If the last argument contains a shell or SQL wildcard (@code{*}, @code{?}, @code{%} or @code{_}) then only what's matched by the wildcard is shown. If a database contains underscore(s), those should be escaped with backslash (some Unix shells will require two), in order to get tables / columns properly. '*' are converted into SQL '%' wildcard and '?' into SQL '_' wildcard. This may cause some confusion when you try to display the columns for a table with a @code{_} as in this case @code{mysqlshow} only shows you the table names that match the pattern. This is easily fixed by adding an extra @code{%} last on the command-line (as a separate argument). @node mysql_config, perror, mysqlshow, Client-Side Scripts @subsection @code{mysql_config}, Get compile options for compiling clients @code{mysql_config} provides you with useful information how to compile your MySQL client and connect it to MySQL. @code{mysql_config} supports the following options: @table @code @item --cflags Compiler flags to find include files @item --libs Libs and options required to link with the MySQL client library. @item --socket The default socket name, defined when configuring MySQL. @item --port The default port number, defined when configuring MySQL. @item --version Version number and version for the MySQL distribution @item --libmysqld-libs Libs and options required to link with the MySQL embedded server. @end table If you execute @code{mysql_config} without any options it will print all options it supports plus the value of all options: @example shell> mysql_config sage: /usr/local/mysql/bin/mysql_config [OPTIONS] Options: --cflags [-I'/usr/local/mysql/include/mysql'] --libs [-L'/usr/local/mysql/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib -lssl -lcrypto] --socket [/tmp/mysql.sock] --port [3306] --version [4.0.8-gamma] --libmysqld-libs [ -L'/usr/local/mysql/lib/mysql' -lmysqld -lpthread -lz -lcrypt -lnsl -lm -lpthread -lrt] @end example You can use this to compile a MySQL client by as follows: @example CFG=/usr/local/mysql/bin/mysql_config sh -c "gcc -o progname `$CFG --cflags` progname.c `$CFG --libs`" @end example @node perror, Batch Commands, mysql_config, Client-Side Scripts @subsection @code{perror}, Explaining Error Codes @cindex error messages, displaying @cindex perror @cindex errno @cindex Errcode For most system errors MySQL will, in addition to a internal text message, also print the system error code in one of the following styles: @code{message ... (errno: #)} or @code{message ... (Errcode: #)}. You can find out what the error code means by either examining the documentation for your system or use the @code{perror} utility. @code{perror} prints a description for a system error code, or an MyISAM/ISAM storage engine (table handler) error code. @code{perror} is invoked like this: @example shell> perror [OPTIONS] [ERRORCODE [ERRORCODE...]] Example: shell> perror 13 64 Error code 13: Permission denied Error code 64: Machine is not on the network @end example Note that the error messages are mostly system dependent! @node Batch Commands, , perror, Client-Side Scripts @subsection How to Run SQL Commands from a Text File The @code{mysql} client typically is used interactively, like this: @example shell> mysql database @end example However, it's also possible to put your SQL commands in a file and tell @code{mysql} to read its input from that file. To do so, create a text file @file{text_file} that contains the commands you wish to execute. Then invoke @code{mysql} as shown here: @example shell> mysql database < text_file @end example You can also start your text file with a @code{USE db_name} statement. In this case, it is unnecessary to specify the database name on the command line: @example shell> mysql < text_file @end example If you are already running @code{mysql}, you can execute a SQL script file using the @code{source} command: @example mysql> source filename; @end example For more information about batch mode, @ref{Batch mode}. @node Log Files, Replication, Client-Side Scripts, MySQL Database Administration @section The MySQL Log Files @cindex Log files MySQL has several different log files that can help you find out what's going on inside @code{mysqld}: @multitable @columnfractions .20 .80 @item @strong{Log file} @tab @strong{Description} @item The error log @tab Problems encountering starting, running or stopping @code{mysqld}. @item The isam log @tab Logs all changes to the ISAM tables. Used only for debugging the isam code. @item The query log @tab Established connections and executed queries. @item The update log @tab Deprecated: Stores all statements that changes data @item The binary log @tab Stores all statements that changes something. Used also for replication @item The slow log @tab Stores all queries that took more than @code{long_query_time} to execute or didn't use indexes. @end multitable All logs can be found in the @code{mysqld} data directory. You can force @code{mysqld} to reopen the log files (or in some cases switch to a new log) by executing @code{FLUSH LOGS}. @xref{FLUSH}. @menu * Error log:: The Error Log * Query log:: The General Query Log * Update log:: The Update Log * Binary log:: The Binary Update Log * Slow query log:: The Slow Query Log * Log file maintenance:: Log File Maintenance @end menu @node Error log, Query log, Log Files, Log Files @subsection The Error Log The error log file contains information indicating when @code{mysqld} was started and stopped and also any critical errors found when running. If @code{mysqld} dies unexpectedly and @code{mysqld_safe} needs to restart @code{mysqld}, @code{mysqld_safe} will write a @code{restarted mysqld} row in this file. This log also holds a warning if @code{mysqld} notices a table that needs to be automatically checked or repaired. On some operating systems, the error log will contain a stack trace for where @code{mysqld} died. This can be used to find out where @code{mysqld} died. @xref{Using stack trace}. Beginning with MySQL 4.0.10 you can specify where @code{mysqld} stores the error log file with the option @code{--log-error[=filename]}. If no file name is given @code{mysqld} will use @code{mysql-data-dir/'hostname'.err} on Unix and @file{\mysql\data\mysql.err} on windows. If you execute @code{flush logs} the old file will be prefixed with @code{--old} and @code{mysqld} will create a new empty log file. In older MySQL versions the error log handling was done by @code{mysqld_safe} which redirected the error file to @code{'hostname'.err}. One could change this file name with the option @code{--err-log=filename}. If you don't specify @code{--log-error} or if you use the @code{--console} option the errors will be written to stderr (the terminal). On windows the output is always done to the @code{.err} file if @code{--console} is not given. @node Query log, Update log, Error log, Log Files @subsection The General Query Log @cindex query log @cindex files, query log If you want to know what happens within @code{mysqld}, you should start it with @code{--log[=file]}. This will log all connections and queries to the log file (by default named @file{'hostname'.log}). This log can be very useful when you suspect an error in a client and want to know exactly what @code{mysqld} thought the client sent to it. @c Note: this instance of "safe_mysql" should not be changed to "mysqld_safe" @c because it's a 3.23.x-specific command Older versions of the @code{mysql.server} script (from MySQL 3.23.4 to 3.23.8) pass @code{safe_mysqld} a @code{--log} option (enable general query log). If you need better performance when you start using MySQL in a production environment, you can remove the @code{--log} option from @code{mysql.server} or change it to @code{--log-bin}. @xref{Binary log}. The entries in this log are written as @code{mysqld} receives the questions. This may be different from the order in which the statements are executed. This is in contrast to the update log and the binary log which are written after the query is executed, but before any locks are released. @node Update log, Binary log, Query log, Log Files @subsection 更新ログ @cindex update log @cindex files, update log @strong{Note}: the update log is replaced by the binary log. @xref{Binary log}. With this you can do anything that you can do with the update log. @code{--log-update=file_name}オプションを使用して@code{mysqld}を起動すると、 データを更新した全てのSQLコマンドをログファイルに書きます。 もし file_name が与えられなかった場合は、ホスト名がデフォルトで使用されます。 もし file_name にディレクトリパスが含まれなかった場合は、 このファイルはデータディレクトリに書かれます。 もし file_name が拡張を持たなかったなら、@code{mysqld} は @code{file_name.###} という形でログファイルを作成します。 このログファイルはデータディレクトリにかかれ、 その名前は @code{file_name.###} という形式の名前になっています。 @code{###} は @code{mysqladmin refresh} か @code{mysqladmin flush-logs} を実行す る度に、 あるいは @code{FLUSH LOGS} 構文を実行したり、サーバーをリスタートする度に 自動的に増える数字です。 @strong{Note}: for the above scheme to work, you must not create your own files with the same filename as the update log + some extensions that may be regarded as a number, in the directory used by the update log! もし @code{--log} か @code{-l} オプションを使用した場合、ログファイルの名前は @code{mysqld} は全部のログを @file{hostname.log} に書き出します。 この場合、リスタートやりフレッシュを行っても新しくログファイルを作りません。 (一度クローズして再度オープンします。) In this case you can copy it (on Unix) by doing: @example mv hostname.log hostname-old.log mysqladmin flush-logs cp hostname-old.log to-backup-directory rm hostname-old.log @end example 更新ログは、実際に更新されたデータのステートメントだけを書くため、きびきびと動作 します。 @code{WHERE} を使用した @code{UPDATE} か @code{DELETE} で結果が得られなかった場合、 ログは書き出されません。 すでにセットされている値に、もう一度項目を更新するような @code{UPDATE} もスキッ プされます。 The update logging is done immediately after a query completes but before any locks are released or any commit is done. This ensures that the log will be logged in the execution order. ログファイルの更新に従ってデータベースを更新したい場合は、次を行います (更新ログファイル名を @file{file_name.###} と仮定します): @example shell> ls -1 -t -r file_name.[0-9]* | xargs cat | mysql @end example @code{ls} は全てのログファイルを正しく並べるために使用しています。 これは、クラッシュ後にバックアップした状態まで戻りたい、あるいは、 バックアップした後からクラッシュするまでの間のデータの更新を行いたい、 そんな場合に使えます。 @node Binary log, Slow query log, Update log, Log Files @subsection The Binary Update Log バイナリ更新ログ (3.23.15以上) @cindex binary log @cindex files, binary log The intention is that the binary log should replace the update log, so we recommend you to switch to this log format as soon as possible! The binary log contains all information that is available in the update log in a more efficient format. It also contains information about how long each query took that updated the database. It doesn't contain queries that don't modify any data. If you want to log all queries (for example to find a problem query) you should use the general query log. @xref{Query log}. バイナリログはマスターからスレーブにレプリケーションを行なうときにも 使用されます。 @xref{Replication}. @code{--log-bin[=file_name]} オプションで @code{mysqld} が起動されると、 @code{mysqld} は全てのデータを更新する SQL コマンドをログファイルに書き出します。 もしファイル名がオプションに渡されなかった場合は、ホストマシンの名前に @code{-bin} がついた名前が、ファイル名として使用されます。 もしファイル名が指定されていても、パスが指定されていない場合には、 ログファイルはデータディレクトリに書かれます。 もし @code{--log-bin=filename.extension} という形で ファイル名に拡張子を指定した場合、拡張子は取り除かれます。 バイナリログファイル名のため、@code{mysqld} は数字をファイル名に付け加えます。 この数字はサーバー上で @code{mysqladmin refresh}, @code{mysqladmin flush-logs}, @code{FLUSH LOGS} を実行する度に増えていきます。 新しいバイナリログは @code{max_binlog_size} に達するまで自動的に作成されます。 @code{RESET MASTER} コマンドを使用すれば、書き込み中ではないバイナリログファイルを 全て消すことが可能です。 @xref{RESET}. You can use the following options to @code{mysqld} to affect what is logged to the binary log: @multitable @columnfractions .38 .62 @item @strong{Option} @tab @strong{Description} @item @code{binlog-do-db=database_name} @tab Tells the master that it should log updates to the binary log if the current database (i.e. the one selected by @code{USE}) database is 'database_name'. All others databases which are not explicitly mentioned are ignored. Note that if you use this you should ensure that you only do updates in the current database. (Example: @code{binlog-do-db=some_database}) @item @code{binlog-ignore-db=database_name} @tab Tells the master that updates where the current database (i.e. the one selected by @code{USE}) is 'database_name' should not be stored in the binary log. Note that if you use this you should ensure that you only do updates in the current database. (Example: @code{binlog-ignore-db=some_database}) @end multitable To be able to know which different binary log files have been used, @code{mysqld} will also create a binary log index file that contains the name of all used binary log files. By default this has the same name as the binary log file, with the extension @code{'.index'}. You can change the name of the binary log index file with the @code{--log-bin-index=[filename]} option. You should not manually edit this file while @code{mysqld} is running; doing this would confuse @code{mysqld}. If you are using replication, you should not delete old binary log files until you are sure that no slave will ever need to use them. One way to do this is to do @code{mysqladmin flush-logs} once a day and then remove any logs that are more than 3 days old. You can remove them manually, or preferably using @code{PURGE MASTER LOGS TO} (@pxref{Replication SQL}) which will also safely update the binary log index file for you. @cindex @code{mysqlbinlog} You can examine the binary log file with the @code{mysqlbinlog} command. For example, you can update a MySQL server from the binary log as follows: @example shell> mysqlbinlog log-file | mysql -h server_name @end example You can also use the @code{mysqlbinlog} program to read the binary log directly from a remote MySQL server! @code{mysqlbinlog --help} will give you more information of how to use this program! If you are using @code{BEGIN [WORK]} or @code{SET AUTOCOMMIT=0}, you must use the MySQL binary log for backups instead of the old update log. The binary logging is done immediately after a query completes but before any locks are released or any commit is done. This ensures that the log will be logged in the execution order. Updates to non-transactional tables are stored in the binary log immediately after execution. For transactional tables such as @code{BDB} or @code{InnoDB} tables, all updates (@code{UPDATE}, @code{DELETE} or @code{INSERT}) that change tables are cached until a @code{COMMIT} command is sent to the server. At this point @code{mysqld} writes the whole transaction to the binary log before the @code{COMMIT} is executed. Every thread will, on start, allocate a buffer of @code{binlog_cache_size} to buffer queries. If a query is bigger than this, the thread will open a temporary file to store the transaction. The temporary file will be deleted when the thread ends. The @code{max_binlog_cache_size} (default 4G) can be used to restrict the total size used to cache a multi-query transaction. If a transaction is bigger than this it will fail and roll back. If you are using the update or binary log, concurrent inserts will be converted to normal inserts when using @code{CREATE ... SELECT} or @code{INSERT ... SELECT}. This is to ensure that you can recreate an exact copy of your tables by applying the log on a backup. @node Slow query log, Log file maintenance, Binary log, Log Files @subsection The Slow Query Log (3.23.28以上) @cindex slow query log @cindex files, slow query log MySQL を @code{--log-slow-queries[=file_name]} オプションで起動すると、 @code{mysqld} は、 実行に @code{long_query_time} に指定された値以上に時間のかかった 全ての SQL コマンドをログに書き出します。 この時間には、最初のテーブルをロックするまでの時間は含まれていません。 slow query log はクエリが実行され、全てのロックが解除された後に、 書き込まれます。 そのため、SQL 文が実行された順番とは違う順に 書かれるかもしれません。 もしファイル名が指定されなかったら、ホスト名に @code{-slow.log} をつけた ファイル名が使用されます。 もしファイル名が指定されていてもパスが指定されなかったなら、 ログファイルはデータディレクトリに記録されます。 slow query log は実行に時間のかかったクエリを見つけ出すのに使用することが 可能で、最適化に用いられます。 ログファイルが大きくなると、それが難しくなります。そこで、 @code{mysqldumpslow} コマンドを使用すれば、ログファイルの slow query の サマリ一覧を得ることが可能です。 @code{--log-long-format} オプションを使用すれば、インデックスを使用しなかった クエリも記録します。 @xref{Command-line options}. @node Log file maintenance, , Slow query log, Log Files @subsection Log File Maintenance @cindex files, log @cindex maintaining, log files @cindex log files, maintaining The MySQL Server can create a number of different log files, which make it easy to see what is going on. @xref{Log Files}. One must however regularly clean up these files, to ensure that the logs don't take up too much disk space. MySQL をログファイルとともに使用する場合、 あなたは、時々古いログファイルを リムーブ/バックアップし、 MySQL に新しいファイルにログを取るように指示したいと思うことでしょう。 @xref{Backup}. Linux (@code{Red Hat}) においては、@code{mysql-log-rotate} スクリプトを これに使用できます。 もし RPM ディストリビューションの MySQL を インストールしたなら、このスクリプトは自動でインストールされているはずです。 Note that you should be careful with this if you are using the log for replication! 他のシステムでは、自分自身で短いスクリプトをインストールします。 @code{cron} でログファイルを扱うようにします。 @code{mysqladmin flush-logs} コマンドか @code{FLUSH LOGS} SQL文で、 MySQL に新しいログファイルを使用させることが出来ます。 もしあなたが MySQL Version 3.21 を使用しているなら、 @code{mysqladmin refresh} を使用しなくてはなりません。 上記のコマンドは、以下のように動作します： @itemize @bullet @item If standard logging (@code{--log}) or slow query logging (@code{--log-slow-queries}) is used, closes and reopens the log file (@file{mysql.log} and @file{`hostname`-slow.log} as default). @item もし更新ログ (@code{--log-update}) を使用しているなら、 更新ログを閉じ、新しいログファイルを開きます。そのさい、 ログファイルについている番号は増えます。 @end itemize もし更新ログだけを使用しているなら、あなたは、ログを flush するだけでよくて、 その時、バックアップのため古い更新ログファイルを移動します。 もし普通のログを使っていれば、あなたは以下のようにすることができます: @example shell> cd mysql-data-directory shell> mv mysql.log mysql.old shell> mysqladmin flush-logs @end example こうしておいて、@file{mysql.old} をバックアップし削除します。 @node Replication, , Log Files, MySQL Database Administration @section MySQL のレプリケーション (3.23.15以上) @cindex replication @cindex increasing, speed @cindex speed, increasing @cindex databases, replicating @menu * Replication Intro:: Introduction * Replication Implementation:: Replication Implementation Overview * Replication HOWTO:: How To Set Up Replication * Replication Features:: Replication Features and Known Problems * Replication Options:: Replication Options in @file{my.cnf} * Replication SQL:: SQL Commands Related to Replication * Replication FAQ:: Replication FAQ * Replication Problems:: Troubleshooting Replication @end menu この章は MySQL の様々なレプリケーション機能を説明します。レプリケーション で有効なオプションのリファレンスとしても役立ちます。レプリケーションの紹介 と、その実装方法を学べます。終りの方には、いくつかの FAQ と問題の説明とそ の解決方法もあります。 我々のウェブサイト @uref{http://www.mysql.com/} によく訪れ、この節の最新 版を読むようるように提案します。レプリケーションは絶えず改良されていて、 最新の情報でマニュアルを頻繁に更新します。 @node Replication Intro, Replication Implementation, Replication, Replication @subsection Introduction 一方通行レプリケーションは、堅牢さと速度の両方を増加させるために使用できま す。堅牢さについて、２つのシステムを持つことができ、マスターで問題が発生し た場合にバックアップに切り替えられます。速度の増加は、更新でないクエリの一 部をレプリカサーバに送ることで、成立します。もちろん、これは更新でないクエ リが多い時にだけ働くのですが、通常はそうなります。 バージョン 3.23.15 から、MySQL はワンウェイ・レプリケーションを サポートしました。 1つのサーバーがマスターの役をつとめ，もう一方は、スレーブの役をつとめます。 1つのサーバーはマスターとして動くことも、他に対するスレーブとして動作することも 可能です。 マスターサーバーは update のバイナリログを保持しています(@xref{Binary log}.)。 また、インデックスファイルは、バイナリログのローテーションの切り出し記録を残すた めに保持されます。 スレーブは接続時に、マスタに対し更新の伝達が最後に成功してからやめた場所 を知らせ、更新を取り戻し、それからブロックし、マスタが新しい更新を通知す るのを待ちます。 もしデータベースの複製を行なうなら、このデータベースに対する全ての更新は マスター上で行なわなくてはならないことに注意！ レプリケーションを使用することのもう一つの恩恵は、マスターの代わりに、スレー ブでバックアップを行なうことで、システムのライブバックアップを取ることがで きるということです。@xref{Backup}。 @node Replication Implementation, Replication HOWTO, Replication Intro, Replication @subsection レプリケーション実装概要 @cindex master-slave setup MySQL レプリケーションは、サーバがデータベースへのすべての変更のトラックを バイナリログ (@pxref{Binary log}) に保持し、スレーブサーバがデータのコピー 上で同じクエリを実行できるように、マスターサーバのバイナリログから保存され たクエリを読み込むということを基本にします。 バイナリログは単に固定点(バイナリロギングを有効にした瞬間)からの記録である ことを理解することが@strong{とても重要}です。セットアップするすべてのスレー ブで、マスターからすべてのデータのコピーが必要です。マスター上でバイナリロ ギングを有効にした瞬間に存在していたように。 スレーブのデータがマスターに存在するデータと違う状態でスレーブを起動したならば、 @strong{バイナリログが開始されたときに}、スレーブは失敗するでしょう。 Please see the following table for an indication of master-slave compatibility between different versions. With regard to version 4.0, we recommend using same version on both sides. @c FIX arjen 2002-07-17 new table, not yet measured for XML/DocBook. @multitable @columnfractions .10 .15 .15 .10 .10 .15 @item @tab @tab @strong{Master} @tab @strong{Master} @tab @strong{Master} @tab @strong{Master} @item @tab @tab @strong{3.23.33 and up} @tab @strong{4.0.0} @tab @strong{4.0.1} @tab @strong{4.0.3 and up} @item @strong{Slave} @tab @strong{3.23.33 and up} @tab yes @tab no @tab no @tab no @item @strong{Slave} @tab @strong{4.0.0} @tab no @tab yes @tab no @tab no @item @strong{Slave} @tab @strong{4.0.1} @tab yes @tab no @tab yes @tab no @item @strong{Slave} @tab @strong{4.0.3 and up} @tab yes @tab no @tab no @tab yes @end multitable @strong{Note}: MySQL Version 4.0.2 is not recommended for replication. Starting from 4.0.0, one can use @code{LOAD DATA FROM MASTER} to set up a slave. Be aware that @code{LOAD DATA FROM MASTER} currently works only if all the tables on the master are @code{MyISAM} type, and will acquire a global read lock, so no writes are possible while the tables are being transferred from the master. This limitation is of a temporary nature, and is due to the fact that we have not yet implemented hot lock-free table backup. It will be removed in the future 4.0 branch versions once we implement hot backup enabling @code{LOAD DATA FROM MASTER} to work without blocking master updates. Due to the above limitation, we recommend that at this point you use @code{LOAD DATA FROM MASTER} only if the dataset on the master is relatively small, or if a prolonged read lock on the master is acceptable. While the actual speed of @code{LOAD DATA FROM MASTER} may vary from system to system, a good rule for a rough estimate of how long it is going to take is 1 second per 1 MB of the datafile. You will get close to the estimate if both master and slave are equivalent to 700 MHz Pentium, are connected through 100 MBit/s network, and your index file is about half the size of your data file. Of course, your mileage will vary from system to system, the above rule just gives you a rough order of magnitude estimate. 一旦スレーブが適切に構成され、実行していれば、スレーブは単にマスターに接続して、 更新が処理されるのを待つでしょう。 もしマスターがなくなったり、または、スレーブがマスターとの接続性を失えば、 スレーブは再接続できるまで @code{master-connect-retry} 秒毎に接続を試み、 そして、更新の監視を再開します。 各スレーブはそれが止まった場所のトラックを保持します。マスターサーバはいく つのスレーブが存在し、どれがいつ更新を行なったかについての知識はありません。 次の節ではマスター／スレーブ設定過程を詳細に説明します。 @node Replication HOWTO, Replication Features, Replication Implementation, Replication @subsection レプリケーションの設定方法 以下は、現在の MySQL サーバ上に完全なレプリケーションを設定する方法の簡単 な記述です。あなたがすべてのデータベースのレプリケーションを行ないたくて、 事前にレプリケーションを設定していないと仮定します。以下に示すステップを完 了するためには、マスターサーバを少しシャットダウンすることが必要になります。 上述の方法は、スレーブを設定するもっとも素直な方法ですが、それが唯一の方 法ではありません。たとえば、既にマスタのスナップショットを持っていて、マ スタがすでにサーバIDを設定して、バイナリログを有効にしている場合、マスタ をシャットダウンしたり更新をブロックすることなしに、スレーブを設定できま す。詳細については @ref{Replication FAQ}. を参照してください。 MySQL レプリケーションの達人(guru)になりたければ、学習し、熟考し、 @ref{Replication SQL} に記述されているすべてのコマンドを試すように提案 します。 @ref{Replication Options} の @code{my.cnf} 内のレプリケーション 開始オプションにも精通すべきです。 @enumerate @item マスターとスレーブに、最新の MySQL (同じバージョン) をインストールします。 バージョン 3.23.29 以上を使用すること。 これより前のバージョンでは、バイナリログのフォーマットが違い、また、新しい バージョンで直っているバグも含まれます。 最新のバージョンで確かめるまでは、バグレポートを送らないでください。 @item マスター上に、レプリケーション用の特別なユーザーを登録します。 このユーザーには @code{FILE} 権限(in MySQL versions older than 4.0.2)か @code{REPLICATION SLAVE} 権限(in newer MySQL versions)が必要です。 全てのスレーブからこのユーザーで接続できるようにします。 もしユーザーがレプリケーションのみ(推奨)を行なうなら、 他の権限は与える必要は有りません。 例えば、@code{repl} という名前のユーザー(マスターにアクセス可能なユーザー)を 作成するには、次のようにします： @example mysql> GRANT FILE ON *.* TO repl@@"%" IDENTIFIED BY ''; # master < 4.0.2 @end example @example mysql> GRANT REPLICATION SLAVE ON *.* TO repl@@"%" IDENTIFIED BY ''; # master >= 4.0.2 @end example If you plan to use the @code{LOAD TABLE FROM MASTER} or @code{LOAD DATA FROM MASTER} commands (available starting from version 4.0.0), you will also need to grant the @code{RELOAD} and @code{SUPER} privileges on the master to the above user. @item If you are using MyISAM tables, flush all the tables and block write queries by executing @code{FLUSH TABLES WITH READ LOCK} command. @example mysql> FLUSH TABLES WITH READ LOCK; @end example and then take a snapshot of the data on your master server. (Unixでは) もっとも簡単な方法は @strong{tar} を使用してデータディレクトリの アーカーブを作成することです。 正確なデータディレクトリの場所はインストール方法に依存します。 @example tar -cvf /tmp/mysql-snapshot.tar /path/to/data-dir @end example Windows ユーザは @code{WinZIP} か似たソフトウェアを使用してデータディレクトリのアー カイブを作成することができます。 After or during the process of taking a snapshot, read the value of the current binary log name and the offset on the master: @example mysql > SHOW MASTER STATUS; +---------------+----------+--------------+-------------------------------+ | File | Position | Binlog_do_db | Binlog_ignore_db | +---------------+----------+--------------+-------------------------------+ | mysql-bin.003 | 73 | test,bar | foo,manual,sasha_likes_to_run | +---------------+----------+--------------+-------------------------------+ 1 row in set (0.06 sec) @end example The @code{File} column shows the name of the log, while @code{Position} shows the offset. In the above example, the binary log value is @code{mysql-bin.003} and the offset is 73. Record the values - you will need to use them later when you are setting up the slave. Once you have taken the snapshot and recorded the log name and offset, you can re-enable write activity on the master: @example mysql> UNLOCK TABLES; @end example If you are using InnoDB tables, ideally you should use the InnoDB Hot Backup tool that is available to those who purchase MySQL commercial licenses, support, or the backup tool itself. It will take a consistent snapshot without acquiring any locks on the master server, and record the log name and offset corresponding to the snapshot to be later used on the slave. More information about the tool is avaliable at @uref{http://www.innodb.com/hotbackup.html}. Without the hot backup tool, the quickest way to take a snapshot of InnoDB tables is to shut the master server down and copy the data files, the logs, and the table definition files (@code{.frm}). To record the current log file name and offset, you should do the following before you shut down the server: @example mysql> FLUSH TABLES WITH READ LOCK; mysql> SHOW MASTER STATUS; @end example And then record the log name and the offset from the output of @code{SHOW MASTER STATUS} as was shown earlier. Once you have recorded the log name and the offset, shut the server down without unlocking the tables to make sure it goes down with the snapshot corresponding to the current log file and offset: @example shell> mysqladmin -uroot shutdown @end example If the master has been previously running without @code{log-bin} enabled, the values of log name and position will be empty when you run @code{SHOW MASTER STATUS}. In that case, record empty string ('') for the log name, and 4 for the offset. @item Make sure that @file{my.cnf} on the master has @code{log-bin} if it is not there already and @code{server-id=unique number} in the @code{[mysqld]} section. If those options are not present, add them and restart the server. It is very important that the id of the slave is different from the id of the master. Think of @code{server-id} as something similar to the IP address - it uniquely identifies the server instance in the community of replication partners. @example [mysqld] log-bin server-id=1 @end example @item マスター上の MySQL を再起動します。 @item スレーブの @code{my.cnf} ファイルに、次を追加します： @example server-id= @end example システムに関連したものは <> 内の値で置き換えてあります。 @code{server-id} には、サーバーそれぞれで違う番号にしなくてはなりません。 (同じ複製のグループ内で)。 もし server-id を指定しなければ、 @code{master-host} が無い場合には 1 に なり、それ以外の場合には 2 に自動的になります。 マスターで @code{server-id} の記入漏れがあった場合、 マスターはスレーブからの接続を拒否します。 スレーブ上での記入漏れの場合には、スレーブはマスターへの接続を拒否します。 従って、@code{server-id} の省略はバイナリログのバックアップのためにだけ良 いことです。 @item While the slave is running, make it forget about the old replication configuration if it has been replicating previously: @example mysql> RESET SLAVE; @end example @item スレーブのデータディレクトリにデータのスナップショットをコピーします。 ファイルとディレクトリのユーザーとパーミッションは確実に正しいものに してください。 これらのファイルに対して、 MySQL を実行している アカウントで、読み書きできるようにする必要があります。 @item スレーブの再起動。 @item Once the slave comes up, execute the following command: @example mysql> CHANGE MASTER TO MASTER_HOST='', MASTER_USER='', MASTER_PASSWORD='', MASTER_LOG_FILE='', MASTER_LOG_POS=; @end example replacing the values in <> with the actual values relevant to your system. @item Start the slave thread: @example mysql> SLAVE START; @end example @end enumerate 上記を行なった後、スレーブはマスターに接続し、スナップショット以後の 更新をキャッチするはずです。 もしスレーブに @code{server-id} をセットし忘れた場合、エラーログファイルに 次のようなエラーが出るでしょう： @example Warning: one should set server_id to a non-0 value if master_host is set. The server will not act as a slave. @end example もしマスターにセットし忘れたなら、スレーブはマスターに接続できません。 もし何かの理由でスレーブが複製できなかったなら、スレーブ上のエラーログ ファイルに、エラーメッセージが出るでしょう。 一度スレーブがレプリケーションを始めたなら、 エラーログファイルと同じディレクトリに @code{master.info} ファイルを見ることができます。 @code{master.info} ファイルはスレーブに使用され、 これは、マスターのバイナリログのいくつまで処理したかを保持しています。 このファイルを消したり編集したりしては @strong{いけません}。 (あなたがやろうとしていることが確実に分かるまでは)。 そういうやむを得ない場合には、 @code{CHANGE MASTER TO} コマンドの使用の方が良いです。 Now that you have a snapshot, you can use it to set up other slaves. To do so, follow the slave portion of the procedure described above. You do not need to take another snapshot of the master. @node Replication Features, Replication Options, Replication HOWTO, Replication @subsection レプリケーション機能と既知の問題 @cindex options, replication @cindex @file{my.cnf} file @cindex files,@file{my.cnf} 以下はサポートされていることとサポートされていないことの説明です: @itemize @bullet @item レプリケーションは @code{AUTO_INCREMENT}, @code{LAST_INSERT_ID}, @code{TIMESTAMP} 値を正しく扱います。 @item 更新中の @code{RAND()} はうまく複製できません。 @code{RAND()} での更新を複製する場合は、@code{RAND(some_non_rand_expr)} を 使用してください。 例えば、@code{UNIX_TIMESTAMP()} を @code{RAND()} の引数に使用するとか。 @item マスターとスレーブは同じキャラクター・セット (@code{--default-character-set}) を使 用しなくてはなりません。 もし違った場合、スレーブ上で duplicate key errors が出るかもしれません。 これは、マスター上で一意のキーであったとしても、 違う キャラクター・セット ではそうとはみなされない事があるからです。 @item In 3.23, @code{LOAD DATA INFILE} will be handled properly as long as the file still resides on the master server at the time of update propagation. @code{LOAD LOCAL DATA INFILE} will be skipped. In 4.0, this limitation is not present - all forms of @code{LOAD DATA INFILE} are properly replicated. @item ユーザー変数を使用したクエリは、(まだ) replication-safe ではありません。 @item @code{FLUSH} コマンドはバイナリログに記録されません。 もちろん、スレーブに複製されません。 これは @code{FLUSH} が通常は何もデータを変更しないからです。 しかし、仮に MySQL の権限データベースを複製していて、 @code{GRANT} 文ではなくて直接 MySQL 権限テーブルを変更した場合には、 権限を反映させるために、スレーブ上で @code{FLUSH PRIVILEGES} を行なわなくては なりません。 @item 3.23.29 以降の一時テーブルは正しく複製されます。ただし、スレーブサーバ(ス レーブスレッドではない)をシャットダウンした時に、いくつかの一時テーブルが オープンされていて、続く更新で使用される場合を除きます。この問題を扱うため に、スレーブをシャットダウンするには、@code{SLAVE STOP} を行ない、それから @code{Slave_open_temp_tables} 変数が 0 かどうかをチェックし、そして、 @code{mysqladmin shutdown} を発行してください。数値が 0 でない場合は、スレー ブスレッドを @code{SLAVE START} で再起動して、次回に幸運かどうかを見てくだ さい。 もっときれいな解決方法は、バージョン 4.0 まで待つ必要があります。それ以前 のバージョンの一時テーブルは正しく複製されません - アップグレードするか 一 時テーブルでのすべてのクエリの前にクライアント上で @code{SET SQL_LOG_BIN=0} の実行をお勧めします。 @item MySQL は 1 つのマスターと複数のスレーブの構成のみをサポートします。 4.x では、何かが現在のマスターを故障させた場合に、自動的にマスターを変更す る voting アルゴリズムを追加するでしょう。また、異なるスレーブに select ク エリを送ることで、負荷分散を行なうための手助けとなるような 'エージェント' プロセスも導入するでしょう。 @item バージョン 3.23.26 から、@code{log-slave-updates} を有効にすることで、 マスターとスレーブの関係を輪っか状にすることが可能です。 しかし、多くのクエリは、この種のセットアップでは正しく動作しません。 違うシーケンス、違うサーバーで行なわれる更新によって引き起こる 潜在的な問題に対応するように、クライアントコードを注意して書かない限りは。 これは以下のようなセットアップを意味します： @example A -> B -> C -> A @end example このセットアップはテーブル間での更新に何も衝突が無い場合にのみ、動作します。 仮に A と C でデータを insert するとき、C にinsertするレコードのキーと 競合するようなレコードを A に insert してはいけません。 同じレコードを、２つのサーバーで更新すべきではありません。 もしそこで更新が適用される順番が重要なら。 ログのフォーマットは バージョン 3.23.36 で変更になりました。 3.23.36 以前のスレーブは、3.23.36 以上のログファイルを読むことができません。 @item もしスレーブ上でクエリがエラーになると、スレーブのスレッドは停止され、 @code{.err} ファイルにメッセージが現われます。 この場合、スレーブを手動で接続し、エラーの原因を修正し(例えば、テーブルが無いとか)、 その後、 @code{SLAVE START} SQLコマンドを実行します (このコマンドはバージョン 3.23.16 以上から)。 バージョン 3.23.15 までは、サーバーを再起動しなくてはなりません。 @item もしマスターへの接続が失われた場合、スレーブは直ちにリトライし、 それでも失敗した場合は、 @code{master-connect-retry} 秒毎（デフォルトでは 60秒）に リトライを繰り返します。 このため、マスターをシャットダウンして、しばらくあとに再起動することは安全 です。スレーブはネットワーク接続性の停止も処理できます。 However, the slave will notice the network outage only after receiving no data from the master for @code{slave_net_timeout} seconds. So if your outages are short, you may want to decrease @code{slave_net_timeout} ; see @ref{SHOW VARIABLES}. @item スレーブのシャットダウンも安全にできます。レプリケーションを止めた位置を 保存するようにしているからです。 きれいでないシャットダウンは問題を引き起こすでしょう。システムが落ちる前に もしディスクキャッシュがシンクされない場合には特に。 もしあなたが良い UPS を持っているならば、安全性を高めることができるでしょう。 @item もしマスターが非標準のポートを使用している場合、 @code{my.cnf} ファイルに @code{master-port} パラメターを書くことにより、 ポート番号を指定できます。 @item バージョン 3.23.15 では、すべてのテーブルとデータベースが複製されます。バー ジョン 3.23.16 からは @code{my.cnf} 内の @code{replicate-do-db} 命令でデー タベースのセットに、または @code{replicate-ignore-db} でデータベースのセッ トを除外して、複製を制限できます。注意: バージョン 3.23.23 になるまでは、 複製から除外されたデータベースで @code{LOAD DATA INFILE} を行なうと、正し く扱えないというバグがありました。 @item バージョン 3.23.16 から、マスター上で、@code{SET SQL_LOG_BIN = 0} でレプリケーシ ョン(バイナリ) ログを止めることができます。 @code{SET SQL_LOG_BIN = 1} で再びログを採取することができます。 これを行なう場合には、@code{SUPER} 権限(in MySQL 4.0.2 and above)か @code{PROCESS} 権限(in older MySQL versions) が必要です。 @item バージョン 3.23.19 から、何かがおかしくなって、残っている複製をクリーンナップし て、まったくの最初から開始したいときのために、 @code{FLUSH MASTER} と @code{FLUSH SLAVE} コマンドが用意されました。 バージョン 3.23.26 から、これらの名前を @code{RESET MASTER} と @code{RESET SLAVE} に変更しました。 互換性のために、古い @code{FLUSH} もまだ動作します。 （訳注： このコマンドは、bin log を 001 からに強制してしまうため、 場合によっては複製をおかしくすることも有る。使用には注意。） @item バージョン 3.23.23 から、 @code{CHANGE MASTER TO} を使用して、 マスターを変更したりポジションを変更したりできるようになりました。 @item バージョン 3.23.23 から、 @code{binlog-ignore-db} を使用して、 バイナリログを取らないデータベースを指定できるようになりました。 @item バージョン 3.23.26 から、 @code{replicate-rewrite-db} を使用して、 マスター上のデータベースの名前を、スレーブ上では違う名前にするように、 スレーブに指示することができるようになりました。 @item バージョン 3.23.28 から、 スレーブが実行している最中に、 古いログを取り去るために、 @code{PURGE MASTER LOGS TO 'log-name'} が使用できます。 This will remove all old logs before, but not including @code{'log-name'}. @item Due to the non-transactional nature of MyISAM tables, it is possible to have a query that will only partially update a table and return an error code. This can happen, for example, on a multi-row insert that has one row violating a key constraint, or if a long update query is killed after updating some of the rows. If that happens on the master, the slave thread will exit and wait for the DBA to decide what to do about it unless the error code is legitimate and the query execution results in the same error code. If this error code validation behaviour is not desirable, some ( or all) errors could be masked out with @code{slave-skip-errors} option starting in Version 3.23.47. @item While individual tables can be excluded from replication with @code{replicate-do-table}/@code{replicate-ignore-table} or @code{replicate-wild-do-table}/@code{replicate-wild-ignore-table}, there are currently some design deficiencies that in some rather rare cases produce unexpected results. The replication protocol does not inform the slave explicitly which tables are going to be modified by the query -- so the slave has to parse the query to know this. To avoid redundant parsing for queries that will end up actually being executed, table exclusion is currently implemented by sending the query to the standard MySQL parser, which will short-circuit the query and report success if it detects that the table should be ignored. In addition to several inefficiencies, this approach is also more bug prone, and there are two known bugs as of Version 3.23.49 -- because the parser automatically opens the table when parsing some queries the ignored table has to exist on the slave. The other bug is that if the ignored table gets partially updated, the slave thread will not notice that the table actually should have been ignored and will suspend the replication process. While the above bugs are conceptually very simple to fix, we have not yet found a way to do this without a significant code change that would compromise the stability status of 3.23 branch. There exists a workaround for both if in the rare case it happens to affect your application -- use @code{slave-skip-errors}. @end itemize @node Replication Options, Replication SQL, Replication Features, Replication @subsection @file{my.cnf} 内のレプリケーションオプション レプリケーションを使用する場合は、我々は MySQL Version 3.23.33 以降を 推奨します。 これより古いバージョンでも動きますが、古い物はバグがあったり機能が無かったりします。 Some of the options mentioned here may not be available in your version if it is not the most recent one. For all options specific to the 4.0 branch, there is a note indicating so. Otherwise, if you discover that the option you are interested in is not available in your 3.23 version, and you really need it, please upgrade to the most recent 3.23 branch. Please be aware that 4.0 branch is still in alpha, so some things may not be working as smoothly as you would like. If you really would like to try the new features of 4.0, we recommend you do it in such a way that in case there is a problem your mission critical applications will not be disrupted. マスターとスレーブの両方に、 @code{server-id} オプションが必要です。 これは一意のレプリケーションid をセットします。 マスター、スレーブそれぞれのために、一意な値を、1 から 2^32-1 までの間から 選ばねばなりません。 例: @code{server-id=3} 以下の表は、@strong{MASTER} で使用できるオプションを示したものです: @multitable @columnfractions .38 .62 @item @strong{オプション} @tab @strong{説明} @item @code{log-bin=filename} @tab Write to a binary update log to the specified location. Note that if you give it a parameter with an extension (for example, @code{log-bin=/mysql/logs/replication.log} ) versions up to 3.23.24 will not work right during replication if you do @code{FLUSH LOGS} . The problem is fixed in Version 3.23.25. If you are using this kind of log name, @code{FLUSH LOGS} will be ignored on binlog. log を clear するには、@code{FLUSH MASTER} の実行をします。 @code{FLUSH SLAVE} を全てのスレーブ上で実行することも忘れてはいけません。 バージョン 3.23.36 以上では、@code{RESET MASTER} と @code{RESET SLAVE} を使用す べきです。 You can use this option if you want to have a name which is independant of your hostname (could be useful in case you rename your host one day). （訳注： @code{RESET} はログを本当に全部消してしまうので、注意が必要。） @item @code{log-bin-index=filename} @tab @code{FLUSH LOGS} コマンドの実行のためには、どのログが現在使用されているもので、 どれがローテートされたもので、どの順番なのか、ということを知る必要があります。 この情報はバイナリログ index ファイルに記述されます。 デフォルトでは @file{`hostname`.index} というファイルになります。 違う名前にしたい場合に、このオプションを使用します。 Example: @code{log-bin-index=db.index} @item @code{sql-bin-update-same} @tab 設定されると、@code{SQL_LOG_BIN} に値を設定すると自動的に @code{SQL_LOG_UPDATE} を同じ値に設定します。逆も同様です。 @item @code{binlog-do-db=database_name} @tab 現在の(いうなれば @code{USE} で選択している)データベースが @code{database_name} の場合、 バイナリログに更新をログすべきことをマスターに伝えます。 他のすべてのデータベースは無視されます。 注意: これを使用する場合は、現在のデータベースでだけ更新を行なうことを 確実にすべきです。 Example: @code{binlog-do-db=sales} @item @code{binlog-ignore-db=database_name} @tab 現在のデータベース(@code{USE}で選択しているデータベース) が @code{database_name} という名前であり、このデータベースの更新記録を バイナリログに格納すべきでないと、マスターに伝えます。 注意: これを使用する場合は、現在のデータベー スでだけ更新を行なうことを確実にすべきです。 Example: @code{binlog-ignore-db=accounting} @end multitable 次の表は @strong{SLAVE} に使用できるオプションです: @multitable @columnfractions .38 .62 @item @strong{Option} @tab @strong{Description} @item @code{master-host=host} @tab マスタのホスト名か IP アドレス。 もし設定されていないと、スレーブはスタートしません。 Note that the setting of @code{master-host} will be ignored if there exists a valid @file{master.info} file. Probably a better name for this options would have been something like @code{bootstrap-master-host}, but it is too late to change now. Example: @code{master-host=db-master.mycompany.com} @item @code{master-user=username} @tab スレーブスレッドがマスターに接続する時に自分を認証するためのユーザ。ユーザ は @code{FILE} 権限を持つ必要があります。マスターユーザが設定されない場合 は、@code{test} が適用されます。 The value in @file{master.info} will take precedence if it can be read. Example: @code{master-user=scott} @item @code{master-password=password} @tab スレーブスレッドがマスターサーバに接続する時に認証するパスワード。設定され ない場合は、空のパスワードが適用されます。 The value in @file{master.info} will take precedence if it can be read. Example: @code{master-password=tiger} @item @code{master-port=portnumber} @tab マスターが listen しているポート。設定されない場合は、@code{MYSQL_PORT} の コンパイル時の設定が適用されます。@code{configure} オプションで何もしてな ければ、これは 3306 です。 The value in @file{master.info} will take precedence if it can be read. Example: @code{master-port=3306} @item @code{master-connect-retry=seconds} @tab マスターが落ちたり接続が失われた場合に、スレーブスレッドがマスターへの接続 を再試行するまでに休眠する秒数。デフォルトは 60。 Example: @code{master-connect-retry=60} @item @code{master-ssl} @tab Available after 4.0.0. Turn SSL on for replication. Be warned that is this is a relatively new feature. Example: @code{master-ssl} @item @code{master-ssl-key} @tab Available after 4.0.0. Master SSL keyfile name. Only applies if you have enabled @code{master-ssl}. Example: @code{master-ssl-key=SSL/master-key.pem} @item @code{master-ssl-cert} @tab Available after 4.0.0. Master SSL certificate file name. Only applies if you have enabled @code{master-ssl}. Example: @code{master-ssl-key=SSL/master-cert.pem} @item @code{master-info-file=filename} @tab 複製処理がマスターのどこまで行なったかを覚えておくファイルの場所。デフォル トはデータディレクトリの @file{master.info} です。 You should not need to change this. Example: @code{master-info-file=master.info} @item @code{report-host} @tab バージョン 4.0.0 から。 スレーブ登録中にマスタに報告されるスレーブのホス ト名と IP 。これは @code{SHOW SLAVE HOSTS} の出力に表われます。スレーブ をマスタに登録したくない場合は、設定しないでください。注意: マスタがスレー ブ接続時のソケットの IP を単純に読むだけでは不十分です。@code{NAT} や他 のルーティングの問題で、マスタや他のホストからスレーブへの接続IPが正しく ないことがあります。 Example: @code{report-host=slave1.mycompany.com} @item @code{report-port} @tab バージョン 4.0.0 から。スレーブ登録中にマスタに報告されるスレーブのポー ト。スレーブがデフォルトでないポートで listen する場合か、マスタか他のク ライアントからスレーブへの特殊なトンネルを持つ場合にだけ設定してください。 確かでなければ、このオプションを設定しないでください。 @item @code{replicate-do-table=db_name.table_name} @tab 指定されたテーブルに複製を制限することをスレーブスレッドに伝えます。一つ以 上のテーブルを指定するには、この命令を複数回(各テーブルに１回ずつ)使用しま す。 This will work for cross-database updates, in contrast to @code{replicate-do-db}. Example: @code{replicate-do-table=some_db.some_table} @item @code{replicate-ignore-table=db_name.table_name} @tab 指定されたテーブルを複製しないことをスレーブスレッドに伝えます。 (even if any other tables may be update by the same command). 一つ以上の テーブルを無視するように指定するには、この命令を複数回(各テーブルに１回ず つ)使用します。これは @code{replicate-ignore-db} とは対照的に、データベー スをまたがった更新について動作します。 Example: @code{replicate-ignore-table=db_name.some_table} @item @code{replicate-wild-do-table=db_name.table_name} @tab 指定されたワイルドカードパターンに適合するテーブルに複製を制限することをス レーブスレッドに伝えます。一つ以上のテーブルを指定するには、この命令を複数 回(各テーブルに１回ずつ)使用します。これはデータベースをまたがった更新につ いて動作します。 Example: @code{replicate-wild-do-table=foo%.bar%} は @code{foo} で始まるすべての データベースの @code{bar} で始まるテーブルだけに更新を複製します。 Note that if you do @code{replicate-wild-do-table=foo%.%} then the rule will be propagated to @code{CREATE DATABASE} and @code{DROP DATABASE}, i.e. these two statements will be replicated if the database name matches the database pattern ('foo%' here) (this magic is triggered by '%' being the table pattern). @item @code{replicate-wild-ignore-table=db_name.table_name} @tab 与えられたワイルドカードパターンに適合するテーブルを複製しないことをスレー ブスレッドに伝えます。一つ以上のテーブルを無視するように指定するには、この 命令を複数回(各テーブルに１回ずつ)使用します。これはデータベースをまたがっ た更新について動作します。 Example: @code{replicate-wild-ignore-table=foo%.bar%} は @code{foo} で始まるすべての データベースの @code{bar} で始まるテーブルを更新しません。 Note that if you do @code{replicate-wild-ignore-table=foo%.%} then the rule will be propagated to @code{CREATE DATABASE} and @code{DROP DATABASE}, i.e. these two statements will not be replicated if the database name matches the database pattern ('foo%' here) (this magic is triggered by '%' being the table pattern). @item @code{replicate-ignore-db=database_name} @tab Tells the slave thread to not replicate any command where the current database (i.e. the one selected by @code{USE}) is @code{database_name}. To specify more than one database to ignore, use the directive multiple times, once for each database. You should not use this directive if you are using cross table updates and you don't want these update to be replicated. The main reason for this ``just-check-the-current-database'' behaviour is that it's hard from the command alone to know if a query should be replicated or not ; for example if you are using multi-table-delete or multi-table-update commands in MySQL 4.x that go across multiple databases. It's also very fast to just check the current database, as this only has to be done once at connect time or when the database changes. If you need cross database updates to work, make sure you have 3.23.28 or later, and use @code{replicate-wild-ignore-table=db_name.%}. Example: @code{replicate-ignore-db=some_db} @item @code{replicate-do-db=database_name} @tab Tells the slave thread to restrict replication to commands where the current database (i.e. the one selected by @code{USE}) is @code{database_name}. To specify more than one database, use the directive multiple times, once for each database. Note that this will not replicate cross-database queries such as @code{UPDATE some_db.some_table SET foo='bar'} while having selected a different or no database. If you need cross database updates to work, make sure you have 3.23.28 or later, and use @code{replicate-wild-do-table=db_name.%}. Example: @code{replicate-do-db=some_db} @item @code{log-slave-updates} @tab スレーブスレッドからの更新をバイナリログに記録するように、スレーブに告げます。 デフォルトは Off です。 Of course, it requires that the slave be started with binary logging enabled (@code{log-bin} option). You have to use @code{log-slave-updates} to chain several slaves ; for example for the following setup to work @example A -> B ->C @end example (C is a slave of B which is a slave of A) you need to start B with the @code{log-slave-updates} option. @item @code{replicate-rewrite-db=from_name->to_name} @tab Tells the slave to translate the current database (i.e. the one selected by @code{USE}) to @code{to_name} if it was @code{from_name} on the master. Only statements involving tables may be affected (@code{CREATE DATABASE}, @code{DROP DATABASE} won't), and only if @code{from_name} was the current database on the master. This will not work for cross-database updates. Example: @code{replicate-rewrite-db=master_db_name->slave_db_name} @item @code{slave-skip-errors= [err_code1,err_code2,... | all]} @tab バージョン 3.23.47 以上。 与えられたエラーコードではレプリケーションを止めないように、 スレーブスレッドに告げます。 通常、レプリケーションはエラーに出会うと中止し、マニュアルでデータの矛盾を 解決する機会をユーザに与えます。 このオプションは、なぜエラーが発生したのかを完全に理解するまでは 使用してはいけません。 もしレプリケーションのセットアップ、クライアントプログラム、MySQL 自身に なにもバグがないのであれば、エラーで止まるはずはありません。 このオプションを見境なく使用すると、スレーブで期待に反してマスタとの同期が ずれ、なぜ問題が発生したかについての理解ができない結果になるでしょう。 エラーコードには、スレーブのログファイルに記録されているものや @code{SHOW SLAVE STATUS} で出力される、数字の番号を使用しなくてはなりません。 全てのエラーメッセージは、ソース配布に含まれる @code{Docs/mysqld_error.txt} にあります. とても推奨できない値である @code{all} を使用することもできます（ですがすべ きではありません）。これはすべてのエラーメッセージを無視し、keep barging along regardless. 言うまでもなく、これを使用する場合は、データの完全性に関 してなんの保証もできません。 Please do not complain if your data on the slave is not anywhere close to what it is on the master in this case -- you have been warned. Example: @code{slave-skip-errors=1062,1053} or @code{slave-skip-errors=all} @item @code{skip-slave-start} @tab 起動時にスレーブを開始しないようにスレーブサーバに伝えます。ユーザは後で @code{SLAVE START} で開始できます。 @item @code{slave_compressed_protocol=#} @tab If 1, then use compression on the slave/client protocol if both slave and master support this. @item @code{slave_net_timeout=#} @tab 読み込みがアボートする前にマスターからデータを待つ秒数。 @end multitable @node Replication SQL, Replication FAQ, Replication Options, Replication @subsection レプリケーションに関連する SQL コマンド @cindex SQL commands, replication @cindex commands, replication @cindex replication, commands レプリケーションは SQL インタフェースを通じて制御できます。以下はコマンド のサマリです: @multitable @columnfractions .45 .55 @item @strong{Command} @tab @strong{Description} @item @code{SLAVE START} @tab スレーブスレッドを開始します。 As of MySQL 4.0.2, you can add @code{IO_THREAD} or @code{SQL_THREAD} options to the statement to start the I/O thread or the SQL thread. The I/O thread reads queries from the master server and stores them in the relay log. The SQL thread reads the relay log and executes the queries. (スレーブ) @item @code{SLAVE STOP} @tab スレーブスレッドを停止します。 Like @code{SLAVE START}, this statement may be used with @code{IO_THREAD} and @code{SQL_THREAD} options. (スレーブ) @item @code{SET SQL_LOG_BIN=0} @tab ユーザが @code{SUPER} 権限(in MySQL 4.0.2 and above) @code{PROCESS} (in older MySQL versions) を持っている場合に 更新ログを無効にします。そうでなければ無視されます。(マスター) @item @code{SET SQL_LOG_BIN=1} @tab ユーザが @code{SUPER} 権限(in MySQL 4.0.2 and above)か @code{PROCESS} 権限(in older MySQL versions) を 持っている場合更新ロギングを再度有効にします。 そうでなければ無視されます。(マスター) @item @code{SET GLOBAL SQL_SLAVE_SKIP_COUNTER=n} @tab マスターからの次の @code{n} イベントをスキップします。スレーブスレッ ドが実行していない場合にだけ正当です。そうでなければエラーになります。レプ リケーションの不調からの復旧に有用です。 @item @code{RESET MASTER} @tab インデックスファイルにリストされたすべてのバイナリログを削除し、 binlog インデックスファイルを空にリセットします。3.23.26 バージョンより前 では、@code{FLUSH MASTER} (Master) @item @code{RESET SLAVE} @tab スレーブにマスターログのレプリケーション位置を忘れさせます。 3.23.26 バージョンより前ではこのコマンドは @code{FLUSH SLAVE} と呼ばれてい ました(Slave) @item @code{LOAD TABLE tblname FROM MASTER} @tab マスターからスレーブにテーブルのコピーをダウンロードします。主に @code{LOAD DATA FROM MASTER} のデバッグ用に実装されていますが、but some ``gourmet'' users might find it useful for other things. 自分自身が並の "非ハッカー" タイプの ユーザー(並みのユーザー)であると思う場合は、使用しないでください。 Requires that the replication user which is used to connect to the master has @code{RELOAD} and @code{SUPER} privileges on the master. Please read the timeout notes in the description of @code{LOAD DATA FROM MASTER} below, they apply here too. (Slave) @item @code{LOAD DATA FROM MASTER} @tab バージョン 4.0.0 から。 マスターのスナップショットを取り、スレーブにコピーします。 Requires that the replication user which is used to connect to the master has @code{RELOAD} and @code{SUPER} privileges on the master. スレーブが正しい位置からレプリケーションを開始するように、 @code{MASTER_LOG_FILE} と @code{MASTER_LOG_POS} の値を更新します。 Will honor table and database exclusion rules specified with @code{replicate-*} options. So far works only with @code{MyISAM} tables and acquires a global read lock on the master while taking the snapshot. In the future it is planned to make it work with @code{InnoDB} tables and to remove the need for global read lock using the non-blocking online backup feature. If you are loading big tables, you may have to increase the values of @code{net_read_timeout} and @code{net_write_timeout} on both your master and slave ; see @ref{SHOW VARIABLES}. Note that @code{LOAD DATA FROM MASTER} does @strong{NOT} copy any tables from the @code{mysql} database. This is to make it easy to have different users and privileges on the master and the slave. @item @code{CHANGE MASTER TO master_def_list} @tab マスターパラメータを @code{master_def_list} に指定された値に変更し、 スレーブスレッドを再起動します。@code{master_def_list} はコンマで区切られ た @code{master_def} のリストです。@code{master_def} は次のうちの一つです : @code{MASTER_HOST}, @code{MASTER_USER}, @code{MASTER_PASSWORD}, @code{MASTER_PORT}, @code{MASTER_CONNECT_RETRY}, @code{MASTER_LOG_FILE}, @code{MASTER_LOG_POS}. For example: @example CHANGE MASTER TO MASTER_HOST='master2.mycompany.com', MASTER_USER='replication', MASTER_PASSWORD='bigs3cret', MASTER_PORT=3306, MASTER_LOG_FILE='master2-bin.001', MASTER_LOG_POS=4; @end example 変更する必要のある値だけを指定する必要があります。省略した値は同じ値を維持 します。ホストまたはポートを変更した時を除きます。この場合、スレーブは異な るホストまたは異なるポートに接続しているのでマスターが異なっているとみなし ます。従って、古いログと位置の値はどこにも該当しません。そして、自動的に空 文字列と 0 にそれぞれリセットされます (開始値)。注意: スレーブを再起動する 場合、最後のマスターを覚えています。これが望ましくない場合、 @file{master.info} ファイルを再起動前に削除すべきです。すると、スレーブは @code{my.cnf} またはコマンドラインからそのマスターを読み込みます。 このコマンドは、マスタのスナップショットを持っていて、スナップショットに対 応するマスタ上のログとオフセットの記録がある場合に、スレーブをセットアップ するのに有用です。スナップショットからのリストア後にスレーブ上で、 @code{CHANGE MASTER TO MASTER_LOG_FILE='log_name_on_master', MASTER_LOG_POS=log_offset_on_master}を実行できます。 (Slave) @item @code{SHOW MASTER STATUS} @tab マスターの binlog のステータス情報を提供します。(Master) @item @code{SHOW SLAVE HOSTS} @tab バージョン 4.0 からの機能。 Gives a listing of slaves currently registered with the master. (Master) @item @code{SHOW SLAVE STATUS} @tab スレーブスレッドの基本的な パラメータのステータス情報を提供します。(Slave) @item @code{SHOW MASTER LOGS} @tab バージョン 3.23.28 以降だけで有効です。 マスター上のバイナリログをリストします。 どれくらい行くべきかを見つけるためには、 このコマンドを @code{PURGE MASTER LOGS TO} よりも先に使用すべきです。 (Master) @item @code{SHOW BINLOG EVENTS [ IN 'logname' ] [ FROM pos ] [ LIMIT [offset,] rows ] } @tab バージョン 4.0 からの機能。 binary update log 中のイベントを見せます。 基本的にはテストやデバッグで使用されます。 通常のクライアントからバイナリログを読む必要がある場合にも 使用することが可能です。 (Master) @item @code{SHOW NEW MASTER FOR SLAVE WITH MASTER_LOG_FILE='logfile' AND MASTER_LOG_POS=pos AND MASTER_LOG_SEQ=log_seq AND MASTER_SERVER_ID=server_id} @tab バージョン 4.0 からの機能。 おそらく死んだ／無効になったマスタのスレーブが、同じマスタをレプリケーショ ンしていた他のスレーブからレプリケーションするようにスイッチすることが必 要な場合に、このコマンドが使用されます。コマンドは再計算されたレプリケー ション coordinates を返します (the slave's current binary log file + name and position within that file). この出力は続く @code{CHANGE MASTER TO} コマン ドで使用することができます。通常、ユーザはこのコマンドを実行する必要はあ りません。これは本来 fail-safe レプリケーションコードに内部使用に予約さ れています。この操作を記述するのにもっと直観的な方法を見つけた場合、この 文法は変更されるでしょう。 @item @code{PURGE MASTER LOGS TO 'logname'} @tab バージョン 3.23.28 からの機能。 index ファイルに書かれているログファイルのうち、 指定されたログよりも前のログファイルを全て消します。 index ファイルのリストからもエントリを消します。 そして、指定されたログを一番最初の物とします。 例えば： @example PURGE MASTER LOGS TO 'mysql-bin.010' @end example （訳注： このコマンドの場合、mysql-bin.001 〜 mysql-bin.009 までの ファイルは消され、mysql.index ファイルの中身は、mysql-bin.010 のみ、 記述される状態になるということ。） 削除しようとしているログの一つを現在読み込み中の実行中スレーブがある場合、 このコマンドは何も行なわず、エラーで失敗します。しかし、休眠中のスレーブが あり、それが読もうとしているログの一つをパージしてしまうと、スレーブは複製 できなくなります。このコマンドはスレーブが複製中には安全に実行できます - それらを停止する必要はありません。 最初に @code{SHOW SLAVE STATUS} で、どのログが on になっているか、すべての スレーブをチェックする必要があります。それからマスターで @code{SHOW MASTER LOGS} でログのリストを行ない、すべてのスレーブに共通の最も古いログ を見つけ(すべてのスレーブが最新の場合、リストの最後のログになります)、削除 しようとするすべてのログをバックアップし、目的のログをパージします。 @end multitable @node Replication FAQ, Replication Problems, Replication SQL, Replication @subsection Replication FAQ @strong{Q}: マスタが既に走っている状態で、マスタを止めないで、新しく スレーブを作るには、どのようにすればいいの? @strong{A}: いくつか方法があります。 もしマスタのどこかの時点でのバックアップを取っていて、そして そのバックアップした時点に対応する バイナリログの名前と位置を記録しているのであれば、 ( @code{SHOW MASTER STATUS} で知ることが出来ます) 以下のようにします： @itemize @bullet @item スレーブには一意の server id を割り当てます。 @item Execute @code{CHANGE MASTER TO MASTER_HOST='master-host-name', MASTER_USER='master-user-name', MASTER_PASSWORD='master-pass', MASTER_LOG_FILE='recorded-log-name', MASTER_LOG_POS=recorded_log_pos} @item @code{SLAVE START} 実行 @end itemize もし現在のマスタのバックアップを取っていないのであれば、以下が素早く セットアップする方法です： @itemize @bullet @item @code{FLUSH TABLES WITH READ LOCK} @item @code{gtar zcf /tmp/backup.tar.gz /var/lib/mysql} (パスは環境にあわせて) @item @code{SHOW MASTER STATUS} - 確実にこの出力をメモしておくように - 後で必要になります @item @code{UNLOCK TABLES} @end itemize Afterwards, follow the instructions for the case when you have a snapshot and have recorded the log name and offset. 同じスナップショットをいくつものスレーブをセットアップするために使用す ることができます。一度マスタのスナップショットを得れば、マスタのバイナ リログが無傷で残っている限り、何日でも場合によっては一月でも、待ってス レーブを設定することができます。理論的には待つ期間は無限にできます。２ つの現実的な制限があり、１つは古いログで一杯になるマスタのディスク容量 と、スレーブがキャッチアップするのに掛かる時間の大きさです。 バージョン 4.0.0 以降では、@code{LOAD DATA FROM MASTER} も使用できます。 これは、スナップショットを取ってスレーブにリストアし、ログ名とオフセッ トをスレーブ上で一度に調整する便利なコマンドです。将来、@code{LOAD DATA FROM MASTER} はスレーブをセットアップする推奨方法になるでしょう。 しかし、このコマンドを使用する場合、読み込みロックが長い時間保持される こともあることに注意してください。まだ、我々がそうしたいほど効率よくは 実装されていません。大きなテーブルがある場合、現時点での推奨方法は、ま だ @code{FLUSH TABLES WITH READ LOCK} 実行後のローカル @code{tar} スナッ プショットです。 @strong{Q}: スレーブは常にマスターに接続していなければならないの? @strong{A}: いいえ、その必要はありません。 スレーブを数時間でも数日でも止めたり落としたりしておき、 そのあと再接続して、更新を行ない、再度また、スレーブを落とすことが可能です。 So you can, for example, use master-slave setup over a dial-up link that is up only for short periods of time. The implications of that are that at any given time the slave is not guaranteed to be in sync with the master unless you take some special measures. In the future, we will have the option to block the master until at least one slave is in sync. @strong{Q}: スレーブがキャッチアップするまで、マスタの更新をブロックする には？ @strong{A}: 次のコマンドを実行してください: @itemize @bullet @item Master: @code{FLUSH TABLES WITH READ LOCK} @item Master: @code{SHOW MASTER STATUS} - ログ名とオフセットを記録してください @item Slave: @code{SELECT MASTER_POS_WAIT('recorded_log_name', recorded_log_offset)} select が復帰した時、スレーブはマスタと同期されています @item Master: @code{UNLOCK TABLES} - これでマスタは更新を続けられます。 @end itemize @cindex @code{Binlog_Dump} @strong{Q}: Why do I sometimes see more than one @code{Binlog_Dump} thread on the master after I have restarted the slave? @strong{A}: @code{Binlog_Dump} is a continuous process that is handled by the server in the following way: @itemize @bullet @item Catch up on the updates. @item Once there are no more updates left, go into @code{pthread_cond_wait()}, from which we can be awakened either by an update or a kill. @item On wake up, check the reason. If we are not supposed to die, continue the @code{Binlog_dump} loop. @item If there is some fatal error, such as detecting a dead client, terminate the loop. @end itemize So if the slave thread stops on the slave, the corresponding @code{Binlog_Dump} thread on the master will not notice it until after at least one update to the master (or a kill), which is needed to wake it up from @code{pthread_cond_wait()}. In the meantime, the slave could have opened another connection, which resulted in another @code{Binlog_Dump} thread. The above problem should not be present in Version 3.23.26 and later versions. In Version 3.23.26 we added @code{server-id} to each replication server, and now all the old zombie threads are killed on the master when a new replication thread connects from the same slave @strong{Q}: replication log をどうやってローテートするの? @strong{A}: バージョン 3.23.28 からでは、@code{PURGE MASTER LOGS TO} コマンド を使用するべきです。 実行前には、どのログが消せれるか確認し、場合によっては バックアップを取っておきます。 In earlier versions the process is much more painful, and cannot be safely done without stopping all the slaves in the case that you plan to re-use log names. You will need to stop the slave threads, edit the binary log index file, delete all the old logs, restart the master, start slave threads, and then remove the old log files. @strong{Q}: How do I upgrade on a hot replication setup? @strong{A}: If you are upgrading pre-3.23.26 versions, you should just lock the master tables, let the slave catch up, then run @code{FLUSH MASTER} on the master, and @code{FLUSH SLAVE} on the slave to reset the logs, then restart new versions of the master and the slave. Note that the slave can stay down for some time -- since the master is logging all the updates, the slave will be able to catch up once it is up and can connect. バージョン 3.23.26 以降では、レプリケーションプロトコルのロック (変更のための)を持ちます。 そのため、あなたはマスタとスレーブを on the fly で 新しい 3.23 バージョンにアップグレードできます。 そして、マスタとスレーブがバージョン 3.23.26 以上の場合においては、 マスタとスレーブが違うバージョンの MySQL でもかまいません。 @cindex replication, two-way @strong{Q}: What issues should I be aware of when setting up two-way replication? @strong{A}: MySQL replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed (cross-server) update. In other words, it is possible for client A to make an update to co-master 1, and in the meantime, before it propagates to co-master 2, client B could make an update to co-master 2 that will make the update of client A work differently than it did on co-master 1. Thus when the update of client A will make it to co-master 2, it will produce tables that will be different from what you have on co-master 1, even after all the updates from co-master 2 have also propagated. So you should not co-chain two servers in a two-way replication relationship, unless you are sure that you updates can safely happen in any order, or unless you take care of mis-ordered updates somehow in the client code. You must also realise that two-way replication actually does not improve performance very much, if at all, as far as updates are concerned. Both servers need to do the same amount of updates each, as you would have one server do. The only difference is that there will be a little less lock contention, because the updates originating on another server will be serialised in one slave thread. This benefit, though, might be offset by network delays. @cindex performance, improving @cindex increasing, performance @strong{Q}: How can I use replication to improve performance of my system? @strong{A}: You should set up one server as the master, and direct all writes to it, and configure as many slaves as you have the money and rackspace for, distributing the reads among the master and the slaves. You can also start the slaves with @code{--skip-bdb}, @code{--low-priority-updates} and @code{--delay-key-write=ALL} to get speed improvements for the slave. In this case the slave will use non-transactional @code{MyISAM} tables instead of @code{BDB} tables to get more speed. @strong{Q}: What should I do to prepare my client code to use performance-enhancing replication? @strong{A}: If the part of your code that is responsible for database access has been properly abstracted/modularised, converting it to run with the replicated setup should be very smooth and easy -- just change the implementation of your database access to read from some slave or the master, and to always write to the master. If your code does not have this level of abstraction, setting up a replicated system will give you an opportunity/motivation to it clean up. You should start by creating a wrapper library /module with the following functions: @itemize @bullet @item @code{safe_writer_connect()} @item @code{safe_reader_connect()} @item @code{safe_reader_query()} @item @code{safe_writer_query()} @end itemize @code{safe_} means that the function will take care of handling all the error conditions. You should then convert your client code to use the wrapper library. It may be a painful and scary process at first, but it will pay off in the long run. All applications that follow the above pattern will be able to take advantage of one-master/many slaves solution. The code will be a lot easier to maintain, and adding troubleshooting options will be trivial. You will just need to modify one or two functions, for example, to log how long each query took, or which query, among your many thousands, gave you an error. If you have written a lot of code already, you may want to automate the conversion task by using Monty's @code{replace} utility, which comes with the standard distribution of MySQL, or just write your own Perl script. Hopefully, your code follows some recognisable pattern. If not, then you are probably better off rewriting it anyway, or at least going through and manually beating it into a pattern. Note that, of course, you can use different names for the functions. What is important is having unified interface for connecting for reads, connecting for writes, doing a read, and doing a write. @strong{Q}: When and how much can MySQL replication improve the performance of my system? @strong{A}: MySQL replication is most beneficial for a system with frequent reads and not so frequent writes. In theory, by using a one master/many slaves setup you can scale by adding more slaves until you either run out of network bandwidth, or your update load grows to the point that the master cannot handle it. In order to determine how many slaves you can get before the added benefits begin to level out, and how much you can improve performance of your site, you need to know your query patterns, and empirically (by benchmarking) determine the relationship between the throughput on reads (reads per second, or @code{max_reads}) and on writes @code{max_writes}) on a typical master and a typical slave. The example here will show you a rather simplified calculation of what you can get with replication for our imagined system. Let's say our system load consists of 10% writes and 90% reads, and we have determined that @code{max_reads} = 1200 - 2 * @code{max_writes}, or in other words, our system can do 1200 reads per second with no writes, our average write is twice as slow as average read, and the relationship is linear. Let us suppose that our master and slave are of the same capacity, and we have N slaves and 1 master. Then we have for each server (master or slave): @code{reads = 1200 - 2 * writes} (from bencmarks) @code{reads = 9* writes / (N + 1) } (reads split, but writes go to all servers) @code{9*writes/(N+1) + 2 * writes = 1200} @code{writes = 1200/(2 + 9/(N+1)} So if N = 0, which means we have no replication, our system can handle 1200/11, about 109 writes per second (which means we will have 9 times as many reads due to the nature of our application). If N = 1, we can get up to 184 writes per second. If N = 8, we get up to 400. If N = 17, 480 writes. Eventually as N approaches infinity (and our budget negative infinity), we can get very close to 600 writes per second, increasing system throughput about 5.5 times. However, with only 8 servers, we increased it almost 4 times already. Note that our computations assumed infinite network bandwidth, and neglected several other factors that could turn out to be significant on your system. In many cases, you may not be able to make a computation similar to the one above that will accurately predict what will happen on your system if you add N replication slaves. However, answering the following questions should help you decided whether and how much, if at all, the replication will improve the performance of your system: @itemize @bullet @item What is the read/write ratio on your system? @item How much more write load can one server handle if you reduce the reads? @item How many slaves do you have bandwidth for on your network? @end itemize @strong{Q}: 冗長性/高可用性を提供するようにレプリケーションを使用するには？ @strong{A}: 現在有効な機能で、マスターとスレーブ(またはいくつかのスレーブ 達)をセットアップする必要があります。マスターが生きているかどうかを監視し、 アプリケーションとマスターのスレーブに失敗時に変更を指示するスクリプトを書 きます。以下はいくつかの提案です: @itemize @bullet @item @code{CHANGE MASTER TO} コマンドを使用して、スレーブにマスターを変更するよ うに通知します。 @item マスターの場所が通知されるアプリケーションを保持する良い方法は、マスターの エントリをダイナミック DNS によって持つことです。@strong{bind} では @code{nsupdate} を使って DNS を動的に更新できます。 @item スレーブを @code{log-bin} オプション付きで @code{log-slave-updates} 無しで 実行すべきです。この方法で、@code{STOP SLAVE}; @code{RESET MASTER}、他のス レーブ上で @code{CHANGE MASTER TO} を実行すると、すぐにスレーブがマスター になるように準備ができます。 It will also help you catch spurious updates that may happen because of misconfiguration of the slave (ideally, you want to configure access rights so that no client can update the slave, except for the slave thread) combined with the bugs in your client programs (they should never update the slave directly). @end itemize 我々は現在自動マスター選択システムを MySQL に統合するように働いていますが、 準備ができるまでは、あなた自身のモニタリングツールを作成する必要があります。 @strong{Q}: How does the slave server keep track of where it is on the master? @strong{A}: The slave uses a file in the the data directory defined by the @code{master-info-file=filename} path. This file holds all the information needed by the slave to request new updates. The file contains the following information: @multitable @columnfractions .05 .95 @item @strong{Line#} @tab @strong{Description} @item 1 @tab Binary log file id @item 2 @tab Log file postion @item 3 @tab Host (master) @item 4 @tab Login user @item 5 @tab Login password @item 6 @tab Login port @item 7 @tab Interval, the length of time between reconnects @end multitable @node Replication Problems, , Replication FAQ, Replication @subsection Troubleshooting Replication If you have followed the instructions, and your replication setup is not working, first eliminate the user error factor by checking the following: @itemize @bullet @item Is the master logging to the binary log? Check with @code{SHOW MASTER STATUS}. If it is, @code{Position} will be non-zero. If not, verify that you have given the master @code{log-bin} option and have set @code{server-id}. @item Is the slave running? Check with @code{SHOW SLAVE STATUS}. The answer is found in @code{Slave_running} column. If not, verify slave options and check the error log for messages. @item If the slave is running, did it establish connection with the master? Do @code{SHOW PROCESSLIST}, find the thread with @code{system user} value in @code{User} column and @code{none} in the @code{Host} column, and check the @code{State} column. If it says @code{connecting to master}, verify the privileges for the replication user on the master, master host name, your DNS setup, whether the master is actually running, whether it is reachable from the slave, and if all that seems okay, read the error logs. @item If the slave was running, but then stopped, look at SHOW SLAVE STATUS output and check the error logs. It usually happens when some query that succeeded on the master fails on the slave. This should never happen if you have taken a proper snapshot of the master, and never modify the data on the slave outside of the slave thread. If it does, it is a bug, read below on how to report it. @item If a query on that succeeded on the master refuses to run on the slave, and a full database resync ( the proper thing to do ) does not seem feasible, try the following: @itemize @minus @item First see if there is some stray record in the way. Understand how it got there, then delete it and run @code{SLAVE START} @item If the above does not work or does not apply, try to understand if it would be safe to make the update manually ( if needed) and then ignore the next query from the master. @item If you have decided you can skip the next query, do @code{SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; SLAVE START;} to skip a query that does not use @code{AUTO_INCREMENT} or @code{LAST_INSERT_ID()}, or @code{SET GLOBAL SQL_SLAVE_SKIP_COUNTER=2; SLAVE START;} otherwise. The reason queries that use @code{AUTO_INCREMENT} or @code{LAST_INSERT_ID()} are different is that they take two events in the binary log of the master. @item If you are sure the slave started out perfectly in sync with the master, and no one has updated the tables involved outside of slave thread, report the bug, so you will not have to do the above tricks again. @end itemize @item Make sure you are not running into an old bug by upgrading to the most recent version. @item If all else fails, read the error logs. If they are big, @code{grep -i slave /path/to/your-log.err} on the slave. There is no generic pattern to search for on the master, as the only errors it logs are general system errors -- if it can, it will send the error to the slave when things go wrong. @end itemize When you have determined that there is no user error involved, and replication still either does not work at all or is unstable, it is time to start working on a bug report. We need to get as much info as possible from you to be able to track down the bug. Please do spend some time and effort preparing a good bug report. Ideally, we would like to have a test case in the format found in @code{mysql-test/t/rpl*} directory of the source tree. If you submit a test case like that, you can expect a patch within a day or two in most cases, although, of course, you mileage may vary depending on a number of factors. The second best option is to write a simple program with easily configurable connection arguments for the master and the slave that will demonstrate the problem on our systems. You can write one in Perl or in C, depending on which language you know better. If you have one of the above ways to demonstrate the bug, use @code{mysqlbug} to prepare a bug report and send it to @email{bugs@@lists.mysql.com}. If you have a phantom -- a problem that does occur but you cannot duplicate "at will": @itemize @bullet @item Verify that there is no user error involved. For example, if you update the slave outside of the slave thread, the data will be out of sync, and you can have unique key violations on updates, in which case the slave thread will stop and wait for you to clean up the tables manually to bring them in sync. @item Run slave with @code{log-slave-updates} and @code{log-bin} -- this will keep a log of all updates on the slave. @item Save all evidence before resetting the replication. If we have no or only sketchy information, it would take us a while to track down the problem. The evidence you should collect is: @itemize @minus @item All binary logs on the master @item All binary log on the slave @item The output of @code{SHOW MASTER STATUS} on the master at the time you have discovered the problem @item The output of @code{SHOW SLAVE STATUS} on the master at the time you have discovered the problem @item Error logs on the master and on the slave @end itemize @item Use @code{mysqlbinlog} to examine the binary logs. The following should be helpful to find the trouble query, for example: @example mysqlbinlog -j pos_from_slave_status /path/to/log_from_slave_status | head @end example @end itemize Once you have collected the evidence on the phantom problem, try hard to isolate it into a separate test case first. Then report the problem to @email{bugs@@lists.mysql.com} with as much info as possible. @node MySQL Optimisation, Reference, MySQL Database Administration, Top @chapter MySQL Optimisation @menu * Optimize Overview:: Optimization Overview * Query Speed:: Optimizing @code{SELECT}s and Other Queries * Locking Issues:: Locking Issues * Optimizing Database Structure:: Optimizing Database Structure * Optimizing the Server:: Optimizing the MySQL Server * Disk issues:: Disk Issues @end menu Optimization is a complicated task because it ultimately requires understanding of the whole system. While it may be possible to do some local optimizations with small knowledge of your system or application, the more optimal you want your system to become the more you will have to know about it. This chapter will try to explain and give some examples of different ways to optimise MySQL. Remember, however, that there are always some (increasingly harder) additional ways to make the system even faster. @node Optimize Overview, Query Speed, MySQL Optimisation, MySQL Optimisation @section 最適化 概要 システムを速くするための最も重要な部分は、もちろん基礎的な設計です。 You also need to know what kinds of things your system will be doing, and what your bottlenecks are. 主なボトルネックは： @itemize @bullet @item Disk シーク ： 一片のデータを見つけるためには、ディスクに時間がかかります。 1999年の最新型のディスクでは、このための平均時間は、10msよりも通常より小さいです。 したがって、我々は、理論上は 1秒で約1000 シークすることができます。 この時間は、一つのテーブルであるならば、データの増加と共にディスクアクセスの時間 が少しずつ増加することになり、とても最適化するのは難しくなっていきます。 これを最適化する方法は、データを 1個以上のディスクに分散する事です。 @item Disk reading/writing. When the disk is at the correct position we need to read the data. With modern disks in 1999, one disk delivers something like 10-20Mb/s. This is easier to optimize than seeks because you can read in parallel from multiple disks. @item CPU cycles. データをメイン・メモリーの中に入れた(または既にメモリに存在している)場合に、 結果を得るためには、それを処理する必要があります。 メモリー容量よりも小さなテーブルを持っている場合、これは、制限の要因となります。 小さいテーブルでは、スピードは、通常問題にはなりません。 @item Memory bandwidth. CPU がキャッシュに収まらないようなデータを要求した場合、メイン・メモリー のバンド幅はボトルネックになります。 これはほとんどのシステムで分かりにくいボトルネックとなりますが、 誰かはそれを知っているべきです。 @end itemize @menu * Design Limitations:: MySQL Design Limitations/Tradeoffs * Portability:: Portability * Internal use:: What Have We Used MySQL For? * MySQL Benchmarks:: The MySQL Benchmark Suite * Custom Benchmarks:: Using Your Own Benchmarks @end menu @node Design Limitations, Portability, Optimize Overview, Optimize Overview @subsection MySQL Design Limitations/Tradeoffs @cindex design, limitations @cindex limitations, design When using the MyISAM storage engine, MySQL uses extremely fast table locking (multiple readers / single writers). The biggest problem with this table type is a if you have a mix of a steady stream of updates and slow selects on the same table. If this is a problem with some tables, you can use another table type for these. @xref{Table types}. MySQL can work with both transactional and not transactional tables. To be able to work smoothly with not transactional tables (which can't rollback if something goes wrong), MySQL has the following rules: @cindex default values @itemize @bullet @item All columns have default values. @item If you insert a 'wrong' value in a column like a @code{NULL} in a @code{NOT NULL} column or a too big numerical value in a numerical column, MySQL will instead of giving an error instead set the column to the 'best possible value'. For numerical values this is 0, the smallest possible values or the largest possible value. For strings this is either the empty string or the longest possible string that can be in the column. @item All calculated expressions returns a value that can be used instead of signaling an error condition. For example 1/0 returns @code{NULL} @end itemize The reason for the above rules is that we can't check these conditions before the query starts to execute. If we encounter a problem after updating a few rows, we can't just rollback as the table type may not support this. We can't stop because in that case the update would be 'half done' which is probably the worst possible scenario. In this case it's better to 'do the best you can' and then continue as if nothing happened. The above means that one should not use MySQL to check fields content, but one should do this in the application. @node Portability, Internal use, Design Limitations, Optimize Overview @subsection Portability @cindex portability @cindex crash-me program @cindex programs, crash-me 全てのSQLサーバはそれぞれ異なるSQL処理ルーチンにより構成されています。 したがって色々なSQLサーバ上で同じように動作するような(ポータブルな) SQLアプリケーションを書くのは手間がかかります。 確かに単純なインサートやセレクトを行うようなものは簡単ですが、 必要な機能が増えれば増えるほど難しくなっていきます。 高速動作を要求されるSQLプラットフォームの数が増えれば増えるほど そのようなアプリケーションの開発は大変になっていきます。 ポータブルな多機能アプリケーションを開発するためには 沢山のSQLサーバでの動作を検証する必要があります。 You can use the MySQL @code{crash-me} program/web-page @uref{http://www.mysql.com/information/crash-me.php} to find functions, types, and limits you can use with a selection of database servers. Crash-me now tests far from everything possible, but it is still comprehensive with about 450 things tested. For example, you shouldn't have column names longer than 18 characters if you want to be able to use Informix or DB2. Both the MySQL benchmarks and @code{crash-me} programs are very database-independent. By taking a look at how we have handled this, you can get a feeling for what you have to do to write your application database-independent. The benchmarks themselves can be found in the @file{sql-bench} directory in the MySQL source distribution. They are written in Perl with DBI database interface (which solves the access part of the problem). See @uref{http://www.mysql.com/information/benchmarks.html} for the results from this benchmark. As you can see in these results, all databases have some weak points. That is, they have different design compromises that lead to different behaviour. If you strive for database independence, you need to get a good feeling for each SQL server's bottlenecks. MySQL is very fast in retrieving and updating things, but will have a problem in mixing slow readers/writers on the same table. Oracle, on the other hand, has a big problem when you try to access rows that you have recently updated (until they are flushed to disk). Transaction databases in general are not very good at generating summary tables from log tables, as in this case row locking is almost useless. To get your application @emph{really} database-independent, you need to define an easy extendable interface through which you manipulate your data. As C++ is available on most systems, it makes sense to use a C++ classes interface to the databases. If you use some specific feature for some database (like the @code{REPLACE} command in MySQL), you should code a method for the other SQL servers to implement the same feature (but slower). With MySQL you can use the @code{/*! */} syntax to add MySQL-specific keywords to a query. The code inside @code{/**/} will be treated as a comment (ignored) by most other SQL servers. If high performance is more important than exactness, as in some web applications, it is possibile to create an application layer that caches all results to give you even higher performance. By letting old results 'expire' after a while, you can keep the cache reasonably fresh. This provides a method to handle high load spikes, in which case you can dynamically increase the cache and set the expire timeout higher until things get back to normal. In this case the table creation information should contain information of the initial size of the cache and how often the table should normally be refreshed. @node Internal use, MySQL Benchmarks, Portability, Optimize Overview @subsection What Have We Used MySQL For? @cindex uses, of MySQL @cindex customers, of MySQL MySQL の初期の開発期には、MySQL は我々のもっとも大口の顧客に合うように 機能が作成されました。 彼らは、いくつかのスウェーデン最大手の小売り業者 のために、倉庫に入れている（商品）データを取り扱います。 我々は、すべての店から、全ボーナス・カード取扱高の、その週間まとめを得ます。 そして、その店のオーナにとって有益な情報、その店の広告キャンペーンが お客にどの程度影響を及ぼすか、を提供することが、我々に求められています。 そのデータは、とても大きくて (約700万/月 回の取り扱い)、 我々はその顧客に提供する必要のあるデータを 4〜10年分、持っています。 我々は、カスタマーから、彼らがこのデータからできる新しいレポートに ”即時に”アクセスしたいという、要求を受けました。 我々はこれを、全ての月ごとの情報を圧縮した 'transaction' テーブルに 保存することで解決しました。 We have a set of simple macros (script) that generates summary tables grouped by different criteria (product group, customer id, store ...) from the transaction tables. そのレポートは Web ページで、これは小さな perl スクリプトで動的に 作成されます。 この perl script は Web Page を分析し、SQL 文を 実行し、結果を挿入します。 We would have used PHP or mod_perl instead but they were not available at that time. 画像データのために、我々は簡単なツールを @code{C} でかきました。 これは SQL のクエリの結果を元に(結果にいくつか処理をして) GIF を提供します。 これも動的に perl スクリプト(@code{HTML} ファイルを分析する)から実行されます。 In most cases a new report can simply be done by copying an existing script and modifying the SQL query in it. In some cases, we will need to add more fields to an existing summary table or generate a new one, but this is also quite simple, as we keep all transactions tables on disk. (Currently we have at least 50G of transactions tables and 200G of other customer data.) We also let our customers access the summary tables directly with ODBC so that the advanced users can themselves experiment with the data. 我々はこれらを Sun Ultra SPARCstation (2x200 Mz) で扱っていますが、 なんの問題もありません。 We recently upgraded one of our servers to a 2 CPU 400 Mhz UltraSPARC, and we are now planning to start handling transactions on the product level, which would mean a ten-fold increase of data. We think we can keep up with this by just adding more disk to our systems. We are also experimenting with Intel-Linux to be able to get more CPU power cheaper. 現在、我々はバイナリ互換のデータベースフォーマットを持っており (new in Version 3.23) 、我々はこれをアプリケーションのいくつかの部分に使用しはじ める事でしょう。 Our initial feelings are that Linux will perform much better on low-to-medium load and Solaris will perform better when you start to get a high load because of extreme disk IO, but we don't yet have anything conclusive about this. After some discussion with a Linux Kernel developer, this might be a side effect of Linux giving so much resources to the batch job that the interactive performance gets very low. This makes the machine feel very slow and unresponsive while big batches are going. Hopefully this will be better handled in future Linux Kernels. @node MySQL Benchmarks, Custom Benchmarks, Internal use, Optimize Overview @subsection The MySQL Benchmark Suite @cindex benchmark suite @cindex crash-me program This should contain a technical description of the MySQL benchmark suite (and @code{crash-me}), but that description is not written yet. Currently, you can get a good idea of the benchmark by looking at the code and results in the @file{sql-bench} directory in any MySQL source distributions. This benchmark suite is meant to be a benchmark that will tell any user what things a given SQL implementation performs well or poorly at. Note that this benchmark is single threaded, so it measures the minimum time for the operations. We plan to in the future add a lot of multi-threaded tests to the benchmark suite. For example, (run on the same NT 4.0 machine): @multitable @columnfractions .35 .10 .10 @item @strong{Reading 2000000 rows by index} @tab @strong{Seconds} @tab @strong{Seconds} @item mysql @tab 367 @tab 249 @item mysql_odbc @tab 464 @tab @item db2_odbc @tab 1206 @tab @item informix_odbc @tab 121126 @tab @item ms-sql_odbc @tab 1634 @tab @item oracle_odbc @tab 20800 @tab @item solid_odbc @tab 877 @tab @item sybase_odbc @tab 17614 @tab @end multitable @multitable @columnfractions .35 .10 .10 @item @strong{Inserting (350768) rows} @tab @strong{Seconds} @tab @strong{Seconds} @item mysql @tab 381 @tab 206 @item mysql_odbc @tab 619 @tab @item db2_odbc @tab 3460 @tab @item informix_odbc @tab 2692 @tab @item ms-sql_odbc @tab 4012 @tab @item oracle_odbc @tab 11291 @tab @item solid_odbc @tab 1801 @tab @item sybase_odbc @tab 4802 @tab @end multitable In the above test MySQL was run with a 8M index cache. We have gathered some more benchmark results at @uref{http://www.mysql.com/information/benchmarks.html}. Note that Oracle is not included because they asked to be removed. All Oracle benchmarks have to be passed by Oracle! We believe that makes Oracle benchmarks @strong{very} biased because the above benchmarks are supposed to show what a standard installation can do for a single client. To run the benchmark suite, you have to download a MySQL source distribution, install the Perl DBI driver, the Perl DBD driver for the database you want to test and then do: @example cd sql-bench perl run-all-tests --server=# @end example where # is one of supported servers. You can get a list of all options and supported servers by doing @code{run-all-tests --help}. @cindex crash-me @code{crash-me} tries to determine what features a database supports and what its capabilities and limitations are by actually running queries. For example, it determines: @itemize @bullet @item What column types are supported @item How many indexes are supported @item What functions are supported @item How big a query can be @item How big a @code{VARCHAR} column can be @end itemize We can find the result from @code{crash-me} on a lot of different databases at @uref{http://www.mysql.com/information/crash-me.php}. @node Custom Benchmarks, , MySQL Benchmarks, Optimize Overview @subsection Using Your Own Benchmarks @cindex benchmarks @cindex performance, benchmarks You should definitely benchmark your application and database to find out where the bottlenecks are. By fixing it (or by replacing the bottleneck with a 'dummy module') you can then easily identify the next bottleneck (and so on). Even if the overall performance for your application is sufficient, you should at least make a plan for each bottleneck, and decide how to solve it if someday you really need the extra performance. For an example of portable benchmark programs, look at the MySQL benchmark suite. @xref{MySQL Benchmarks, , MySQL Benchmarks}. You can take any program from this suite and modify it for your needs. By doing this, you can try different solutions to your problem and test which is really the fastest solution for you. It is very common that some problems only occur when the system is very heavily loaded. We have had many customers who contact us when they have a (tested) system in production and have encountered load problems. In every one of these cases so far, it has been problems with basic design (table scans are @strong{not good} at high load) or OS/Library issues. Most of this would be a @strong{lot} easier to fix if the systems were not already in production. To avoid problems like this, you should put some effort into benchmarking your whole application under the worst possible load! You can use Super Smack for this, and it is available at: @uref{http://www.mysql.com/Downloads/super-smack/super-smack-1.0.tar.gz}. As the name suggests, it can bring your system down to its knees if you ask it, so make sure to use it only on your development systems. @node Query Speed, Locking Issues, Optimize Overview, MySQL Optimisation @section Optimizing @code{SELECT}s and Other Queries @cindex queries, speed of @cindex permission checks, effect on speed @cindex speed, of queries 最初に、全てのクエリに影響する一つの事柄をのべます： より複雑な権限の設定を行うと、オーバーヘッドが多くなります。 もしあなたがいかなる @code{GRANT} 文も行っていなければ、 MySQL はパーミッションの検査を少ししか最適化しないでしょう。 So if you have a very high volume it may be worth the time to avoid grants. Otherwise more permission check results in a larger overhead. もし MySQL 関数のあるものが確実に問題を引き起こしているのならば、 常に MySQL クライアント側は以下のようになります： @example mysql> SELECT BENCHMARK(1000000,1+1); +------------------------+ | BENCHMARK(1000000,1+1) | +------------------------+ | 0 | +------------------------+ 1 row in set (0.32 sec) @end example 上の例では MySQL は 1,000,000 @code{+} 式を 0.32 秒で実行できています (たんなる @code{PentiumII 400MHz} マシンで)。 全ての MySQL 関数は最適化されていますが、 いくつかは例外があるかもしれません。 @code{BENCHMARK(loop_count,expression)}はあなたのクエリの 問題を見つけるためのとてもよいツールです。 @menu * EXPLAIN:: @code{EXPLAIN} Syntax (Get Information About a @code{SELECT}) * Estimating performance:: Estimating query performance * SELECT speed:: Speed of @code{SELECT} queries * Where optimisations:: How MySQL optimizes @code{WHERE} clauses * DISTINCT optimisation:: How MySQL Optimizes @code{DISTINCT} * LEFT JOIN optimisation:: How MySQL optimizes @code{LEFT JOIN} * ORDER BY optimisation:: How MySQL Optimises @code{ORDER BY} * LIMIT optimisation:: How MySQL optimizes @code{LIMIT} * Insert speed:: Speed of @code{INSERT} queries * Update speed:: Speed of @code{UPDATE} queries * Delete speed:: Speed of @code{DELETE} queries * Tips:: Other Optimization Tips @end menu @node EXPLAIN, Estimating performance, Query Speed, Query Speed @subsection @code{EXPLAIN} 構文 (@code{SELECT}についての情報を得る) @findex EXPLAIN @findex SELECT, optimizing @example EXPLAIN tbl_name or EXPLAIN SELECT select_options @end example @code{EXPLAIN tbl_name} は、 @code{DESCRIBE tbl_name} や @code{SHOW COLUMNS FROM tbl_name} と同義です。 もし @code{EXPLAIN} をともなって @code{SELECT} 構文を実行した場合、 MySQL はこの @code{SELECT} がいかに動作するかを説明し、 いかにテーブルが結合されるかの情報を与えます。 @code{EXPLAIN} の情報を元に、インデックスを使用した速い @code{SELECT} を 得るためにテーブルにインデックスを加えなくてはならないという事がわかります。 You should frequently run @code{ANALYZE TABLE} to update table statistics such as cardinality of keys which can affect the choices the optimiser makes. @xref{ANALYZE TABLE}. テーブル結合の最適化もオプションによって見ることができます。 @code{SELECT} 構文での結合を強制的に最適化するには @code{STRAIGHT_JOIN} 節を加え ます。 単純ではない join のために、@code{EXPLAIN} は @code{SELECT} 文で使用されている それぞれのテーブルの情報を返します。 テーブルは読まれる順に表示されます。MySQL は one-sweep multi-join method を用いた全ての join を解決します。これは MySQL は最初のテーブルから 一レコード読み込み、二つ目のテーブルからマッチしたレコードを探し、そして三番目を 探すということです。 全てのテーブルが処理される時、選択されたフィールドを出力し、テーブルの一覧は よりマッチするレコードをもつテーブルを見つけるまで back-track されます。 次のレコードはこのテーブルから読まれ、次のテーブルから処理を続けます。 In MySQL version 4.1 the @code{EXPLAIN} output was changed to work better with constructs like @code{UNION}s, subqueries and derived tables. Most notable is the addition of two new columns: @code{id} and @code{select_type}. @code{EXPLAIN} の出力は以下のフィールドを含みます： @table @code @item id @code{SELECT} identifier, the sequential number of this @code{SELECT} within the query. @item select_type Type of @code{SELECT} clause, which can be any of the following: @table @code @item SIMPLE Simple @code{SELECT} (without @code{UNION}s or subqueries). @item PRIMARY Outermost @code{SELECT}. @item UNION Second and further @code{UNION} @code{SELECT}s. @item DEPENDENT UNION Second and further @code{UNION} @code{SELECTS}s, dependent on outer subquery. @item SUBSELECT First @code{SELECT} in subquery. @item DEPENDENT SUBSELECT First @code{SELECT}, dependent on outer subquery. @item DERIVED Derived table @code{SELECT}. @end table @item table 出力レコードが参照されるテーブル @item type join タイプ. join type は以下のものがあります。良い物から順に書いています： @cindex system table @cindex tables, system @table @code @item system テーブルが一レコードだけ持っている (= system table). これは @code{const} join type の特別な場合です。 @cindex constant table @cindex tables, constant @item const テーブルは、最もマッチするレコードを１つもっており、これはクエリの 最初に読まれます。 1 つのレコードであるため、このレコード中のフィールドの値は オプティマイザーによって常数としてみなされます。 1回だけ読まれるので、@code{const} テーブルはとても速いです! @item eq_ref 前のテーブルのそれぞれのレコードと結合する際、このテーブルから1レコード読まれま す。これは join では @code{const} よりも良い形です。 インデックスの全てのパートが join で使用され、かつ、インデックスが @code{UNIQUE} か @code{PRIMARY KEY} であるときに、これは使用されます。 @item ref インデックスの値に合ったすべてのレコードは、前のテーブルからレコードと結合するた めに、このテーブルから読まれるでしょう。 もしその join がキーの一番左の接頭部分だけを使用するならば、 あるいは、もしそのキーが @code{UNIQUE} や @code{PRIMARY KEY} でなければ (言い換えるなら、もし join がキーの値を元に一つだけの、レコードを選択できなけれ ば)、@code{ref} は使用されます。 もしそのキーがいくつかのマッチするレコードに使用されるだけなら、 join は良い形です。 @item range 示された範囲内にあるレコードのみが検索されます。 @code{key} 項目はどのインデックスが使用されているか示します。 The @code{key_len} contains the longest key part that was used. The @code{ref} column will be @code{NULL} for this type. @item index @code{ALL} と同じですが、インデックスツリーが走査される場合のみを除きます。 これは、インデックスファイルはデータファイルよりも小さいため、通常 @code{ALL} よ り速いです。 @item ALL 前のテーブルのレコードとのそれぞれの結合において、全テーブルが走査されます。 もしそのテーブルが最初のテーブルで @code{const} 状態ではないなら、通常 これは良くありません。他の状態では@strong{とても}悪くなります。 これは普通、レコードががより早いテーブルからから定数値に基づいて検索することがで きるように、 インデックスを追加することにより @code{ALL} を避けることが可能です。 @end table @item possible_keys @code{possible_keys} 項目は、MySQL がテーブルからレコードを見つけるために どのインデックスを使用する事ができたかを示します。 注意: このフィールドはテーブルの順にまったく依存しません。これは、 @code{possible_keys} 内のいくつかのキーは、生成されたテーブル順での実行に使用でき ないことを意味します。 この項目が空なら、関連した インデックスは無いということです。この場合、あなたは @code{WHERE} 節を 調べることによって、クエリの性能を向上させることができるかもしれません。 もしそれがインデックスに適合したフィールドを参照しているならば。 仮にそうだとすると、適切なインデックスを作成し、 @code{EXPLAIN} でクエリを もう一度チェックしてみてください。 テーブルがどんなインデックスを持っているかみるには、@code{SHOW INDEX FROM tbl_name} とします。 @item key @code{key} 項目は、 MySQL が使用すると実際に決めたキー(インデックス)を示します。 どのインデックスも選ばれなかったならば、インデックスは @code{NULL} です。 MySQL に @code{possible_keys} 項目にあるインデックスを使用するように 強制するにはクエリに @code{USE KEY/IGNORE KEY} を使用することができます。 @xref{SELECT}. Also, running @code{myisamchk --analyze} (@pxref{myisamchk syntax}) or @code{ANALYZE TABLE} (@pxref{ANALYZE TABLE}) on the table will help the optimiser choose better indexes. @item key_len @code{key_len} 項目は、MySQL が使用すると決めたキーの長さを示します。 もし @code{key} が @code{NULL} なら、長さは @code{NULL} です。 注意: これはMySQL がマルチパートキーのいくつのパートを実際に使用 するかを示します。 @item ref @code{ref} 項目は、テーブルからレコードを select するために、どのフィールドや 定数が @code{key} と共に使用されたかを示します。 @item rows @code{rows} フィールドは、MySQL がクエリを実行するために検査する 必要があると考えているレコードの数を示します。 @item Extra このフィールドは、MySQL がどのようにクエリを解決するかの追加情報 を含んでいます。ここで、このフィールドに現れ得る様々なテキスト文字列の説明 をします: @table @code @item Distinct MySQL will not continue searching for more rows for the current row combination after it has found the first matching row. @item Not exists MySQL はクエリの @code{LEFT JOIN} 最適化を行なうことができて、 @code{LEFT JOIN} 判定基準に適合する１つのレコードを見つけた後、前のレコード組 み合わせについてこのテーブルにそれ以上のレコードを検査しません。 Here is an example for this: @example SELECT * FROM t1 LEFT JOIN t2 ON t1.id=t2.id WHERE t2.id IS NULL; @end example Assume that @code{t2.id} is defined with @code{NOT NULL}. In this case MySQL will scan @code{t1} and look up the rows in @code{t2} through @code{t1.id}. If MySQL finds a matching row in @code{t2}, it knows that @code{t2.id} can never be @code{NULL}, and will not scan through the rest of the rows in @code{t2} that has the same @code{id}. In other words, for each row in @code{t1}, MySQL only needs to do a single lookup in @code{t2}, independent of how many matching rows there are in @code{t2}. @item @code{range checked for each record (index map: #)} MySQL は使用すべき本当に良いインデックスを見つけられませんでし た。先行するテーブル内に各レコードの結合の代わりに、テーブルからレコード を取り出すためにどのインデックスを使用するかチェックを行ないます。これは とても速いというわけではありませんが、もちろんインデックス無しでの結合を 行なわなければならないよりは速いです。 @item Using filesort MySQL は、ソート順でレコードを取り出す方法を見つけ出すため、余 計なパスの実行が必要です。ソートは、@code{join type} に一致する全てのレ コードを通して行なわれ、@code{WHERE} に適合する全てのレコードについて、 ソートキーとレコードへのポインタを格納します。それから、キーがソートされま す。最後にレコードはソートされた順に取り出されます。 @item Using index フィールド情報は、実際のレコードから読み込む追加シークを行なうことはせず に、インデックスツリー内の情報だけを使用するテーブルから取り出されます。 テーブルについての使用される全てのフィールドが同じインデックスの一部であ る時にこれが行なわれます。 @item Using temporary クエリを解決できるように、MySQL は、結果を保持するための一時テー ブルを作成する必要があります。これは通常 @code{GROUP BY} が行なわれたも のとは別のフィールド上で @code{ORDER BY} を行なう場合に発生します。 @item Using where どのレコードが次のテーブルに対して適合するか、またはクライアントに送られ るかを制限するために、@code{WHERE} 節が使用されます。この情報がなくて、 テーブルが型 @code{ALL} か @code{index} であれば、クエリ内に何か間違った ものがあります(テーブルから全てのレコードを fetch/examine しようとしてい るのでなければ)。 @end table クエリを可能な限り速く得たい場合、@code{Using filesort} と @code{Using temporary} に注意すべきです。 @end table @code{EXPLAIN} 出力の @code{rows} フィールド内のすべての値を増やすことによ り、join がどのように良くなるかの良い表示を得ることができます。これは、 MySQL がクエリ実行の検査をする必要があるレコードのおおよその数を 知らせます。この数は @code{max_join_size} 変数でのクエリを制限する時にも使 用します。 @xref{Server parameters}. 以下の例は、@code{EXPLAIN} が提供する情報を元に、いかに @code{JOIN} が最適化 できるかの例です。 以下のような @code{EXPLAIN} で検査する @code{SELECT} 構文があるとします： @example EXPLAIN SELECT tt.TicketNumber, tt.TimeIn, tt.ProjectReference, tt.EstimatedShipDate, tt.ActualShipDate, tt.ClientID, tt.ServiceCodes, tt.RepetitiveID, tt.CurrentProcess, tt.CurrentDPPerson, tt.RecordVolume, tt.DPPrinted, et.COUNTRY, et_1.COUNTRY, do.CUSTNAME FROM tt, et, et AS et_1, do WHERE tt.SubmitTime IS NULL AND tt.ActualPC = et.EMPLOYID AND tt.AssignedPC = et_1.EMPLOYID AND tt.ClientID = do.CUSTNMBR; @end example この例では、以下のように仮定します： @itemize @bullet @item フィールドは以下のように定義されています： @multitable @columnfractions .10 .15 .15 @item @strong{Table} @tab @strong{Column} @tab @strong{Column type} @item @code{tt} @tab @code{ActualPC} @tab @code{CHAR(10)} @item @code{tt} @tab @code{AssignedPC} @tab @code{CHAR(10)} @item @code{tt} @tab @code{ClientID} @tab @code{CHAR(10)} @item @code{et} @tab @code{EMPLOYID} @tab @code{CHAR(15)} @item @code{do} @tab @code{CUSTNMBR} @tab @code{CHAR(15)} @end multitable @item テーブルは以下のインデックスを持ちます： @multitable @columnfractions .10 .30 @item @strong{Table} @tab @strong{Index} @item @code{tt} @tab @code{ActualPC} @item @code{tt} @tab @code{AssignedPC} @item @code{tt} @tab @code{ClientID} @item @code{et} @tab @code{EMPLOYID} (primary key) @item @code{do} @tab @code{CUSTNMBR} (primary key) @end multitable @item @code{tt.ActualPC} の値は、いちように分布して(配置されて)いません。 @end itemize 最初、いかなる最適化も行われていない状態では、@code{EXPLAIN} 構文は 以下の情報を提示します： @example table type possible_keys key key_len ref rows Extra et ALL PRIMARY NULL NULL NULL 74 do ALL PRIMARY NULL NULL NULL 2135 et_1 ALL PRIMARY NULL NULL NULL 74 tt ALL AssignedPC,ClientID,ActualPC NULL NULL NULL 3872 range checked for each record (key map: 35) @end example それぞれのテーブルで、@code{type} が @code{ALL} になっています。 これは MySQL が全てのテーブルを全結合することを示します！ それぞれのテーブル内の行数分から作った物が調べられるので、とても長い時間がかかり ます！ この場合、@code{74 * 2135 * 74 * 3872 = 45,268,558,720} 行調べることになります。 テーブルが肥大化したときにかかる時間を考えてください.... 一つ問題があります。(まだ) MySQL がフィールドのインデックスを効果的に 使用できていません。 この例の場合では、@code{VARCHAR} と @code{CHAR} は、それらが同じ長さで定義されて いれば、変わりがありません。 @code{tt.ActualPC} は @code{CHAR(10)} と定義されており、 @code{et.EMPLOYID} は @code{CHAR(15)} です。これらの長さは違います。 この不釣り合いを修正するにあたり、@code{ALTER TABLE} を使って @code{ActualPC} の長さを 10 文字から 15 文字にします： @example mysql> ALTER TABLE tt MODIFY ActualPC VARCHAR(15); @end example これで @code{tt.ActualPC} and @code{et.EMPLOYID} は両方とも @code{VARCHAR(15)} になりました。 @code{EXPLAIN} 構文を実行し直すと、以下を提示します： @example table type possible_keys key key_len ref rows Extra tt ALL AssignedPC,ClientID,ActualPC NULL NULL NULL 3872 Using where do ALL PRIMARY NULL NULL NULL 2135 range checked for each record (key map: 1) et_1 ALL PRIMARY NULL NULL NULL 74 range checked for each record (key map: 1) et eq_ref PRIMARY PRIMARY 15 tt.ActualPC 1 @end example まだ完全ではありませんが、よりよくなっています(@code{rows} 値の 生成量は 74 より小さくなります)。この場合、実行は数秒でしょう。 A second alteration can be made to eliminate the column length mismatches for the @code{tt.AssignedPC = et_1.EMPLOYID} and @code{tt.ClientID = do.CUSTNMBR} comparisons: @example mysql> ALTER TABLE tt MODIFY AssignedPC VARCHAR(15), -> MODIFY ClientID VARCHAR(15); @end example これで @code{EXPLAIN} は以下を出力します： @example table type possible_keys key key_len ref rows Extra et ALL PRIMARY NULL NULL NULL 74 tt ref AssignedPC, ActualPC 15 et.EMPLOYID 52 Using where ClientID, ActualPC et_1 eq_ref PRIMARY PRIMARY 15 tt.AssignedPC 1 do eq_ref PRIMARY PRIMARY 15 tt.ClientID 1 @end example これは ``ほとんど'' 最良に近いです。 残る問題は、デフォルトでは、MySQL は @code{tt.ActualPC} フィールド内の 値がまんべんなく分布していると想定しており、この @code{tt} テーブルの場合には 適合しません。 幸運にも、これを MySQL に教えるのはとても簡単です： @example shell> myisamchk --analyze PATH_TO_MYSQL_DATABASE/tt shell> mysqladmin refresh @end example これで join は ``完璧'' です。 @code{EXPLAIN} は以下の結果を示します： @example table type possible_keys key key_len ref rows Extra tt ALL AssignedPC NULL NULL NULL 3872 Using where ClientID, ActualPC et eq_ref PRIMARY PRIMARY 15 tt.ActualPC 1 et_1 eq_ref PRIMARY PRIMARY 15 tt.AssignedPC 1 do eq_ref PRIMARY PRIMARY 15 tt.ClientID 1 @end example @code{EXPLAIN} の出力中の @code{rows} 項目は、 MySQL JOIN オプティマイ ザーによる、``推測'' です； クエリの最適化のために、この数値が実際に近いかどうかをチェックすべきです。 そうでなければ、@code{SELECT} ステートメントで @code{STRAIGHT_JOIN} を使用 し、@code{FROM} 節に異なる順でテーブルを並べることで、良いパフォーマンスを 得られます。 @node Estimating performance, SELECT speed, EXPLAIN, Query Speed @subsection Estimating Query Performance @cindex estimating, query performance @cindex queries, estimating performance @cindex performance, estimating ほとんどの場合、ディスク・シークを数えることでだいたいのパフォーマンスを予測でき ます。 小さなテーブルでは、通常、1回のディスク・シークでレコードを見つけれるでしょう (インデックスがたぶんキャッシュされるので)。 大きなテーブルでは、 おおよその予測として、(B++ ツリーインデックスを使用している場合)、 @code{log(row_count) / log(index_block_length / 3 * 2 / (index_length + data_pointer_length)) + 1} シーク、1レコードを見つけるのに必要となるでしょう。 MySQL では、インデックス・ブロックは通常 1024 バイトで、 データ・ポインターは通常 4 バイトです。 これは、 インデックス長が 3 (medium integer) 、データが 500,000 レコードあるテーブルでは、 @code{log(500,000)/log(1024/3*2/(3+4)) + 1} = 4 シークとなります。 As the above index would require about 500,000 * 7 * 3/2 = 5.2M, (assuming that the index buffers are filled to 2/3, which is typical) you will probably have much of the index in memory and you will probably only need 1-2 calls to read data from the OS to find the row. 書き込み時には、上の場合、新しいインデックスを書き込める場所を 探し出すのに、4 シークかかり、さらに、通常、インデックスを更新し、 レコードを書くのに 2 シーク必要です。 Note that the above doesn't mean that your application will slowly degenerate by log N! As long as everything is cached by the OS or SQL server things will only go marginally slower while the table gets bigger. After the data gets too big to be cached, things will start to go much slower until your applications is only bound by disk-seeks (which increase by log N). To avoid this, increase the index cache as the data grows. @xref{Server parameters}. @node SELECT speed, Where optimisations, Estimating performance, Query Speed @subsection @code{SELECT} クエリの速度 @findex SELECT speed @cindex speed, of queries 通常、遅い @code{SELECT ... WHERE} を速くするには、 まず最初にインデックスがあるかどうかをチェックします。 @xref{MySQL indexes, , MySQL indexes}. 違うテーブルを参照する場合には、普通はインデックスをともなうべきです。 @code{EXPLAIN} コマンドを使用すれば、@code{SELECT} でどのインデックスが 使用されているか確認できます。 @xref{EXPLAIN, , @code{EXPLAIN}}. Some general tips: @itemize @bullet @item To help MySQL optimize queries better, run @code{myisamchk --analyze} on a table after it has been loaded with relevant data. This updates a value for each index part that indicates the average number of rows that have the same value. (For unique indexes, this is always 1, of course.) MySQL will use this to decide which index to choose when you connect two tables with 'a non-constant expression'. You can check the result from the @code{analyze} run by doing @code{SHOW INDEX FROM table_name} and examining the @code{Cardinality} column. @item インデックスとデータをインデックス順に従ってソートするには、 @code{myisamchk --sort-index --sort-records=1} を使用します (もし １番目のインデックス順にソートするなら)。 If you have a unique index from which you want to read all records in order according to that index, this is a good way to make that faster. しかし、このソート方法は最適状態では書かれず、また大きなテーブルでは 多くの時間がかかることに注意してください！ @end itemize @node Where optimisations, DISTINCT optimisation, SELECT speed, Query Speed @subsection MySQL はどのように @code{WHERE} 節を最適化するか？ @findex WHERE @cindex optimizations @code{WHERE} の最適化は、@code{WHERE} がほとんど @code{SELECT} で使用されるため、 @code{SELECT} に置かれています。 しかし、同じ最適化は @code{DELETE} や @code{UPDATE} 文でも使用されます。 このセクションの最適化の説明はまだ不十分です。 なぜなら、 MySQL はとても多くの最適化を行っており、 それら全てについての説明を書ける時間が、我々はとれません。 MySQLによる最適化のいくつかを以下に示します: @itemize @bullet @item 括弧の除去 (全ての不必要な括弧は削除されます): @example ((a AND b) AND c OR (((a AND b) AND (c AND d)))) -> (a AND b AND c) OR (a AND b AND c AND d) @end example @item 定数の保持: @example (a b>5 AND b=c AND a=5 @end example @item 定数条件の除去 (定数保持のために必要とされます): @example (B>=5 AND B=5) OR (B=6 AND 5=5) OR (B=7 AND 5=6) -> B=5 OR B=6 @end example @item インデックスに使用される全ての表現は一度だけ評価されます。 @item 一つのテーブル上の @code{WHERE} がない @code{COCOUNT(*)} は、 @code{MyISAM} and @code{HEAP} の場合は テーブルの情報から 直接取り出されます。これはまた 1つのテーブルだけで @code{NOT NULL} を 使用したときも同様です。 @item 不当な定数表現は早く検出されます。 MySQL は不可能な @code{SELECT} 構文を素早く見つけ、0 行を結果として返 します。 @item @code{GROUP BY} または group 関数 (@code{COUNT()}, @code{MIN()}...) を使用しない 場合は、 @code{HAVING} は @code{WHERE} とマージされます。 @item 各サブ結合についての速い @code{WHERE} 評価を得るために、また、可能な限り 早くレコードをスキップするために、各サブ結合についてより簡単な @code{WHERE} が構築されます。 @cindex constant table @cindex tables, constant @item 全ての定数テーブルをクエリー中の他のテーブルより先に読みます。 定数テーブルは次です: @itemize @minus @item 0 または 1 レコードのテーブル。 @item @code{WHERE} 節で @code{UNIQUE} インデックスや @code{PRIMARY KEY} が使用されたテ ーブルで、かつ、全てのインデックスが定数式で使用されていて、 かつ、インデックスのパートが @code{NOT NULL} で定義されているテーブル。 @end itemize 以下のテーブルのように定数だけを使用するテーブル: @example mysql> SELECT * FROM t WHERE primary_key=1; mysql> SELECT * FROM t1,t2 -> WHERE t1.primary_key=1 AND t2.primary_key=t1.id; @end example @item テーブルを結合するために最良の結合の組合せを見つけます。全ての可能性を試して 。 @code{ORDER BY} または @code{GROUP} 内の全てのフィールドが同じテーブルの場合は、 このテーブルは結合時に最初に優先されます。 @item @code{ORDER BY} 節と @code{GROUP BY} 節がある場合、または @code{ORDER BY} か @code{GROUP BY} が結合キュー内の最初のテーブルではない他のテーブルからの項目を 含む場合、一時テーブルが生成されます。 @item もし @code{SQL_SMALL_RESULT} を使用するなら, MySQL はメモリー内の一時 テーブルを使用します @item 各テーブルのインデックスはクエリされ、得られる行の 30% 未満の幅しかない最良のイ ンデックスが使用されます。 そのようなインデックスが見つけられない場合、素早いテーブルの走査 (quick table scan)が使用されます。 @item 同じように、MySQL はデータファイルを等しく調べはしないインデックスから レコードを読むことが可能です。もし全てのフィールドが数値型のインデックスなら、 インデックスツリーだけがクエリの解決に使用されます。 @item 各レコードが出力される前に、@code{HAVING} 節に適合するものをスキップします。 @end itemize 以下はとても速いクエリの例です: @example mysql> SELECT COUNT(*) FROM tbl_name; mysql> SELECT MIN(key_part1),MAX(key_part1) FROM tbl_name; mysql> SELECT MAX(key_part2) FROM tbl_name -> WHERE key_part_1=constant; mysql> SELECT ... FROM tbl_name -> ORDER BY key_part1,key_part2,... LIMIT 10; mysql> SELECT ... FROM tbl_name -> ORDER BY key_part1 DESC,key_part2 DESC,... LIMIT 10; @end example 以下のクエリはインデックスツリーのみを使用します(インデックス化されているフィー ルドは数値型と仮定します)： @example mysql> SELECT key_part1,key_part2 FROM tbl_name WHERE key_part1=val; mysql> SELECT COUNT(*) FROM tbl_name -> WHERE key_part1=val1 AND key_part2=val2; mysql> SELECT key_part2 FROM tbl_name GROUP BY key_part1; @end example 以下のクエリは、ソートされた行の検索にインデックスを使用します： @example mysql> SELECT ... FROM tbl_name -> ORDER BY key_part1,key_part2,... ; mysql> SELECT ... FROM tbl_name -> ORDER BY key_part1 DESC,key_part2 DESC,... ; @end example @node DISTINCT optimisation, LEFT JOIN optimisation, Where optimisations, Query Speed @subsection How MySQL Optimizes @code{DISTINCT} @findex DISTINCT @cindex optimizing, DISTINCT @code{DISTINCT} is converted to a @code{GROUP BY} on all columns, @code{DISTINCT} combined with @code{ORDER BY} will in many cases also need a temporary table. When combining @code{LIMIT #} with @code{DISTINCT}, MySQL will stop as soon as it finds @code{#} unique rows. If you don't use columns from all used tables, MySQL will stop the scanning of the not used tables as soon as it has found the first match. @example SELECT DISTINCT t1.a FROM t1,t2 where t1.a=t2.a; @end example In the case, assuming @code{t1} is used before @code{t2} (check with @code{EXPLAIN}), then MySQL will stop reading from @code{t2} (for that particular row in @code{t1}) when the first row in @code{t2} is found. @node LEFT JOIN optimisation, ORDER BY optimisation, DISTINCT optimisation, Query Speed @subsection MySQL はどのように @code{LEFT JOIN} と @code{RIGHT JOIN} を最適化するか？ @findex LEFT JOIN @cindex optimizing, LEFT JOIN MySQL の @code{A LEFT JOIN B} は以下のように組みこまれています： @itemize @bullet @item The table @code{B} is set to be dependent on table @code{A} and all tables that @code{A} is dependent on. @item テーブル @code{A} が @code{LEFT JOIN} 条件中に使用される全てのテーブル （ただし @code{B} は除く）に依存すると、セットされます。 @item 全ての @code{LEFT JOIN} 条件が @code{WHERE} 節に移動されます。 @item All standard join optimizations are done, with the exception that a table is always read after all tables it is dependent on. If there is a circular dependence then MySQL will issue an error. @item 全ての @code{WHERE} 節の最適化が行われます。 @item @code{WHERE} 節にマッチするレコードが @code{A} にあり、 @code{LEFT JOIN} 条件にマッチするレコードが @code{B} にない場合、 全てのフィールドが @code{NULL} にセットされた @code{B} のレコードが 作成されます。 @item If you use @code{LEFT JOIN} to find rows that don't exist in some table and you have the following test: @code{column_name IS NULL} in the @code{WHERE} part, where column_name is a column that is declared as @code{NOT NULL}, then MySQL will stop searching after more rows (for a particular key combination) after it has found one row that matches the @code{LEFT JOIN} condition. @end itemize @code{RIGHT JOIN} is implemented analogously as @code{LEFT JOIN}. The table read order forced by @code{LEFT JOIN} and @code{STRAIGHT JOIN} will help the join optimizer (which calculates in which order tables should be joined) to do its work much more quickly, as there are fewer table permutations to check. Note that the above means that if you do a query of type: @example SELECT * FROM a,b LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key) WHERE b.key=d.key @end example MySQL will do a full scan on @code{b} as the @code{LEFT JOIN} will force it to be read before @code{d}. The fix in this case is to change the query to: @example SELECT * FROM b,a LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key) WHERE b.key=d.key @end example @node ORDER BY optimisation, LIMIT optimisation, LEFT JOIN optimisation, Query Speed @subsection How MySQL Optimises @code{ORDER BY} In some cases MySQL can uses index to satisfy an @code{ORDER BY} or @code{GROUP BY} request without doing any extra sorting. The index can also be used even if the @code{ORDER BY} doesn't match the index exactly, as long as all the unused index parts and all the extra are @code{ORDER BY} columns are constants in the @code{WHERE} clause. The following queries will use the index to resolve the @code{ORDER BY} / @code{GROUP BY} part: @example SELECT * FROM t1 ORDER BY key_part1,key_part2,... SELECT * FROM t1 WHERE key_part1=constant ORDER BY key_part2 SELECT * FROM t1 WHERE key_part1=constant GROUP BY key_part2 SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 DESC SELECT * FROM t1 WHERE key_part1=1 ORDER BY key_part1 DESC,key_part2 DESC @end example Some cases where MySQL can @strong{not} use indexes to resolve the @code{ORDER BY}: (Note that MySQL will still use indexes to find the rows that matches the @code{WHERE} clause): @itemize @bullet @item You are doing an @code{ORDER BY} on different keys: @code{SELECT * FROM t1 ORDER BY key1,key2} @item You are doing an @code{ORDER BY} using non-consecutive key parts. @code{SELECT * FROM t1 WHERE key2=constant ORDER BY key_part2} @item You are mixing @code{ASC} and @code{DESC}. @code{SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 ASC} @item The key used to fetch the rows are not the same one that is used to do the @code{ORDER BY}: @code{SELECT * FROM t1 WHERE key2=constant ORDER BY key1} @item You are joining many tables and the columns you are doing an @code{ORDER BY} on are not all from the first not-@code{const} table that is used to retrieve rows (This is the first table in the @code{EXPLAIN} output which doesn't use a @code{const} row fetch method). @item You have different @code{ORDER BY} and @code{GROUP BY} expressions. @item The used table index is an index type that doesn't store rows in order. (Like the @code{HASH} index in @code{HEAP} tables). @end itemize In the cases where MySQL have to sort the result, it uses the following algorithm: @itemize @bullet @item Read all rows according to key or by table scanning. Rows that don't match the @code{WHERE} clause are skipped. @item Store the sort-key in a buffer (of size @code{sort_buffer}). @item When the buffer gets full, run a qsort on it and store the result in a temporary file. Save a pointer to the sorted block. (In the case where all rows fits into the sort buffer, no temporary file is created) @item Repeat the above until all rows have been read. @item Do a multi-merge of up to @code{MERGEBUFF} (7) regions to one block in another temporary file. Repeat until all blocks from the first file are in the second file. @item Repeat the following until there is less than @code{MERGEBUFF2} (15) blocks left. @item On the last multi-merge, only the pointer to the row (last part of the sort-key) is written to a result file. @item Now the code in @file{sql/records.cc} will be used to read through them in sorted order by using the row pointers in the result file. To optimise this, we read in a big block of row pointers, sort these and then we read the rows in the sorted order into a row buffer (@code{record_rnd_buffer}) . @end itemize You can with @code{EXPLAIN SELECT ... ORDER BY} check if MySQL can use indexes to resolve the query. If you get @code{Using filesort} in the @code{extra} column, then MySQL can't use indexes to resolve the @code{ORDER BY}. @xref{EXPLAIN}. If you want to have a higher @code{ORDER BY} speed, you should first see if you can get MySQL to use indexes instead of having to do an extra sorting phase. If this is not possible, then you can do: @itemize @bullet @item Increase the size of the @code{sort_buffer} variable. @item Increase the size of the @code{record_rnd_buffer} variable. @item Change @code{tmpdir} to point to a dedicated disk with lots of empty space. If you use MySQL 4.1 or later you can spread load between several physical disks by setting @code{tmpdir} to a list of paths separated by colon @code{:} (semicolon @code{;} on Windows). They will be used in round-robin fashion. @strong{Note:} These paths should end up on different @strong{physical} disks, not different partitions of the same disk. @end itemize MySQL by default sorts all @code{GROUP BY x,y[,...]} queries as if you would have specified @code{ORDER BY x,y[,...]}. MySQL will optimise away any @code{ORDER BY} as above without any speed penalty. If you by in some cases don't want to have the result sorted you can specify @code{ORDER BY NULL}: @example INSERT INTO foo SELECT a,COUNT(*) FROM bar GROUP BY a ORDER BY NULL; @end example @node LIMIT optimisation, Insert speed, ORDER BY optimisation, Query Speed @subsection MySQL はどのように @code{LIMIT} を最適化するか？ @findex LIMIT @cindex optimizing, LIMIT In some cases MySQL will handle the query differently when you are using @code{LIMIT #} and not using @code{HAVING}: @itemize @bullet @item もし @code{LIMIT} を使用して限定した数だけ select を行うなら、 MySQL は、 ある場合、テーブルを全て走査するよりも、インデックスを使用しようとします。 @item もし @code{LIMIT #} を @code{ORDER BY} と共に使用するなら, MySQL は 最初の @code{#} 行を見つけたらすぐに、全テーブルのソートは行わずに、 ソートを終わらせます。 @item @code{LIMIT #} を @code{DISTINCT} と共に使用するなら, MySQL は @code{#} 個の一意なレコードを見つけた時点で終わります。 @item In some cases a @code{GROUP BY} can be resolved by reading the key in order (or do a sort on the key) and then calculate summaries until the key value changes. In this case @code{LIMIT #} will not calculate any unnecessary @code{GROUP BY}s. @item MySQL は、最初の @code{#} 行をクライアントに送った後すぐに、 クエリを中断します。 (if you are not using @code{SQL_CALC_FOUND_ROWS}). @item @code{LIMIT 0} は常に素早く空の結果を返します。 これはクエリのチェックや結果として得られるフィールドの型を得るために利用できます。 @item 一時テーブルの大きさは、クエリを解決するためにどれぐらいのスペースがいるかを 計算するのに、@code{LIMIT #} を使用します。 @end itemize @node Insert speed, Update speed, LIMIT optimisation, Query Speed @subsection @code{INSERT} クエリの速度 @findex INSERT @cindex speed, inserting @cindex inserting, speed of レコードを挿入する時間はおおよそ次からなります: @itemize @bullet @item Connect: (3) @item Sending query to server: (2) @item Parsing query: (2) @item Inserting record: (1 x size of record) @item Inserting indexes: (1 x number of indexes) @item Close: (1) @end itemize ここで (数字) は比例時間です。これは、テーブルのオープンにかかる初期オーバーヘッ ド(これは同時に動作する各クエリ毎に1回行なわれます)は考慮されていません。 テーブルのサイズはインデックスの挿入を log N で遅くします (B-tree)。 INSERT を速くするいくつかの方法： @itemize @bullet @item もし同じクライアントから多くのレコードを同時にインサートするなら、 複数の値が書ける @code{INSERT} 文を使用します。 これは個々に @code{INSERT} 文 を発行する場合に比べて、とても速くなります。 If you are adding data to non-empty table, you may tune up @code{bulk_insert_buffer_size} variable to make it even faster. @xref{SHOW VARIABLES, , @code{bulk_insert_buffer_size}}. @item もし違うクライアントから多くのレコードを同時にインサートするなら、 @code{INSERT DELAYED} 文の使用で、より速くなるでしょう。 @xref{INSERT, , @code{INSERT}}. @item @code{MyISAM} では、複数の @code{SELECT} が走っているテーブルに対して、 同時に、レコードを挿入できます。 ただしそのテーブルに対して レコードの削除がない場合に。 @item テキストファイルからテーブルにデータをいれる場合は、 @code{LOAD DATA INFILE} を 使用します。 これはたくさんの @code{INSERT} 文の発行に比べて通常 20倍 程度 速くなります @xref{LOAD DATA, , @code{LOAD DATA}}. @item テーブルが多くのインデックスを持っている場合、ある方法で、 @code{LOAD DATA INFILE} の実行を速くすることが可能です。 以下の手順で行います： @enumerate @item Optionally create the table with @code{CREATE TABLE}. For example, using @code{mysql} or Perl-DBI. @item @code{FLUSH TABLES} の実行。 あるいは @code{mysqladmin flush-tables} コマンドの実行。 @item @code{myisamchk --keys-used=0 -rq /path/to/db/tbl_name} の使用。 これは指定されたテーブルから全てのインデックスを削除します。 @item そのテーブルに @code{LOAD DATA INFILE} を使用してデータを入れます. これはいかなるインデックスも更新しないでしょうし、そのため、速くもなるでしょう。 @item If you are going to only read the table in the future, run @code{myisampack} on it to make it smaller. @xref{Compressed format}. @item @code{myisamchk -r -q /path/to/db/tbl_name} でインデックスを再構築. これは disk に書き込む前にインデックスをメモリに作成します。 これは多くのディスクシークを避けることが出来るのでとても速くなります。 でき上がったインデックスツリーは、バランスのよいものになります。 @item @code{FLUSH TABLES} の実行。 あるいは @code{mysqladmin flush-tables} コマンドの実行。 @end enumerate この手順は、将来の MySQL の @code{LOAD DATA INFILE} に組み込むかもしれません。 @item Note that @code{LOAD DATA INFILE} also does the above optimization if you insert into an empty table; the main difference with the above procedure is that you can let @code{myisamchk} allocate much more temporary memory for the index creation that you may want MySQL to allocate for every index recreation. Since MySQL 4.0 you can also use @code{ALTER TABLE tbl_name DISABLE KEYS} instead of @code{myisamchk --keys-used=0 -rq /path/to/db/tbl_name} and @code{ALTER TABLE tbl_name ENABLE KEYS} instead of @code{myisamchk -r -q /path/to/db/tbl_name}. This way you can also skip @code{FLUSH TABLES} steps. @item You can speed up insertions that is done over multiple statements by locking your tables: @example mysql> LOCK TABLES a WRITE; mysql> INSERT INTO a VALUES (1,23),(2,34),(4,33); mysql> INSERT INTO a VALUES (8,26),(6,29); mysql> UNLOCK TABLES; @end example 主な速度差は、全ての @code{INSERT} 構文でインデックスバッファが一度だけディスク にフラッシュされることです。通常は @code{INSERT} 構文があるのと同じくらい多くの インデックスバッファフラッシュがあります。単一構文の全てのレコードは、ロック なしで挿入できます。 For transactional tables, you should use @code{BEGIN/COMMIT} instead of @code{LOCK TABLES} to get a speedup. ロックも複数接続テストの合計時間を低くしますが、いくつかのスレッドの最大 待ち時間は上がります(ロックを待っているから)。 例えば: @example thread 1 does 1000 inserts thread 2, 3, and 4 does 1 insert thread 5 does 1000 inserts @end example ロックを使用しない場合、2, 3 そして 4 は 1 と 5 の前に終ります。ロックを 使用する場合、2,3,4 は 1 や 5 の前に終わることはおそらくありませんが、合 計時間は約 40 % 速くなります。 @code{INSERT}, @code{UPDATE} , @code{DELETE} は、 MySQL ではとても速い ので、 1 行で約 5 つ以上、値を 挿入・更新 をする操作に対して、 ロックを追加すれば、全般的により良い性能が得られます。 とても多い insert を行なう場合、 他のスレッドにそのロックしたテーブルへのアクセスを与えるために 、 だいたい 1000 レコードごとに一度、@code{UNLOCK TABLES} した後に @code{LOCK TABLES} を行います。 これでもまだ良い性能が得られます。 もちろん @code{LOAD DATA INFILE} はとても速いです。 @end itemize @code{LOAD DATA INFILE} と @code{INSERT} を共に速くするためには、 キーバッファを増やします。 @xref{Server parameters}. @node Update speed, Delete speed, Insert speed, Query Speed @subsection @code{UPDATE} クエリの速度 @code{UPDATE} クエリは @code{SELECT} クエリのように最適化されますが、 書き込みのオーバーヘッドが加わります。 書き込み速度は、更新されるデータの大きさ、更新されるインデックス数に 依ります。 変更されないインデックスは更新されません。 Also, another way to get fast updates is to delay updates and then do many updates in a row later. Doing many updates in a row is much quicker than doing one at a time if you lock the table. Note that, with dynamic record format, updating a record to a longer total length may split the record. So if you do this often, it is very important to @code{OPTIMIZE TABLE} sometimes. @xref{OPTIMIZE TABLE, , @code{OPTIMIZE TABLE}}. @node Delete speed, Tips, Update speed, Query Speed @subsection @code{DELETE} クエリの速度 If you want to delete all rows in the table, you should use @code{TRUNCATE TABLE table_name}. @xref{TRUNCATE}. 1レコードを削除する時間は、ちょうどインデックスの数に比例します。 より速くレコードを削除したいなら、インデックス・キャッシュを 増やします。 @xref{Server parameters}. @node Tips, , Delete speed, Query Speed @subsection 最適化に関するその他の助言 @cindex optimization, tips @cindex tips, optimization Unsorted tips for faster systems: @itemize @bullet @item コネクションオーバーヘッドを避けるために、データベースに対して、 逐次コネクションを落とさないように、常に接続を保ちます。 If you can't use persistent connections and you are doing a lot of new connections to the database, you may want to change the value of the @code{thread_cache_size} variable. @xref{Server parameters}. @item あなたのクエリがテーブルのインデックスを使用しているか、いつもチェックします。 MySQL では @code{EXPLAIN} コマンドでこれが行えれます。 @xref{EXPLAIN, Explain, Explain, manual}. @item @code{MyISAM} では、大量に変更されるようなテーブルに対して、 複雑な @code{SELECT} クエリを避けるように試みます。 これはテーブル・ロックの問題を避けるためです。 @item 新しい @code{MyISAM} テーブルでは、あるテーブルにレコードが挿入(削除は無しで) されている最中に、同時に、同じテーブルからデータを読むことが可能です。 これがあなたにとって重要項目であるなら、 レコードの削除の必要のない方法や、多くのレコードを削除した後に @code{OPTIMIZE TABLE} を実行することを、考慮すべきです。 @item Use @code{ALTER TABLE ... ORDER BY expr1,expr2...} if you mostly retrieve rows in @code{expr1,expr2...} order. By using this option after big changes to the table, you may be able to get higher performance. @item In some cases it may make sense to introduce a column that is 'hashed' based on information from other columns. If this column is short and reasonably unique it may be much faster than a big index on many columns. In MySQL it's very easy to use this extra column: @code{SELECT * FROM table_name WHERE hash=MD5(CONCAT(col1,col2)) AND col_1='constant' AND col_2='constant'} @item 多くの変更がなされるテーブルに対しては、全ての @code{VARCHAR} や @code{BLOB} フィールドを避けるように試みるべきです。 You will get dynamic row length as soon as you are using a single @code{VARCHAR} or @code{BLOB} column. @xref{Table types}. @item 通常、あるテーブルを違うテーブルに分けることは、レコードが大きくなる ために役立ちません。 レコードにアクセスする際、そのレコードの最初のバイトを見つけるための ディスク・シークが、一番かかります。 After finding the data most new disks can read the whole row fast enough for most applications. The only cases where it really matters to split up a table is if it's a dynamic row size table (see above) that you can change to a fixed row size, or if you very often need to scan the table and don't need most of the columns. @xref{Table types}. @item もし、多くのレコードからの情報を元にした計算(あるもののカウントとか)を しょっちゅう行う必要があるなら、新しいテーブルを用意し、逐次カウンターを 更新した方が多分良いでしょう。 @code{UPDATE table SET count=count+1 WHERE index_column=constant} の更新は とても速いです！ これは、MySQL MyISAM テーブルや ISAM テーブルのような テーブル・ロッキング(multiple readers / single writers)をもつ データベースを使う上で、本当に重要なことです。 This will also give better performance with most databases, as the row locking manager in this case will have less to do. @item もしたくさんの大きなテーブルから統計を収集する必要があるなら、 全テーブルを走査する代わりに、サマリーテーブルを使用します。 Maintaining the summaries should be much faster than trying to do statistics 'live'. It's much faster to regenerate new summary tables from the logs when things change (depending on business decisions) than to have to change the running application! @item If possible, one should classify reports as 'live' or 'statistical', where data needed for statistical reports are only generated based on summary tables that are generated from the actual data. @item フィールドにはデフォルト値があるという事を利用して下さい。 値がデフォルトとは違う場合に限り、値を挿入します。 これは MySQL が必要とする分析を少なくし、インサートの速度が向上します。 @item ある場合では、BLOB にデータをパックして保存するのが便利です。 この場合、BLOB に入れた値を パック・アンパック するためのコードを あなたのアプリケーションに組み込まなくてはなりません。 しかしこれは、多くのアクセスを抑制するでしょう。 これは、静的(固定長)テーブル構造に適しないデータを持っている場合に 実用になります。 @item 通常、あなたは全てのデータを冗長の無いように(データベース理論で 第３正規形 , 3rd Normal Form , 3NF と呼ばれる) しようとするかもしれませんが、しかし、よりスピードを求める場合は、 重複やサマリーテーブルの作成をおそれてはいけません。 @item ストアド・プロシージャ や UDF (ユーザー定義関数) はよりパフォーマンスを得る ためにはよい方法かもしれません。 In this case you should, however, always have a way to do this some other (slower) way if you use some database that doesn't support this. @item You can always gain something by caching queries/answers in your application and trying to do many inserts/updates at the same time. If your database supports lock tables (like MySQL and Oracle), this should help to ensure that the index cache is only flushed once after all updates. @item データをすぐには書く必要がないとき、@code{INSERT /*! DELAYED */} を使用します。 これは、一回のディスクへの書き込みで、多くのレコードがかかれるので、 速くなります。 @item SELECT がより重要な場合、@code{INSERT /*! LOW_PRIORITY */} を使用します。 @item キューを無視して SELECT を優先的に行いたいときは @code{SELECT /*! HIGH_PRIORITY */} を使用します。 これは、たとえ誰かが書き込みを待っていたとしても、その SELECT は 実行されます。 @item 複数行 @code{INSERT} 文の使用。 これは多くのレコードを一つの SQL コマンドで 挿入することが出来ます。 (多くの SQL サーバーがこれをサポートしています) @item 大きなデータの読み込みには @code{LOAD DATA INFILE} を使用します。 This is faster than normal inserts and will be even faster when @code{myisamchk} is integrated in @code{mysqld}. @item 一意の値を作るために、 @code{AUTO_INCREMENT} を使用します。 @item 動的テーブルフォーマットの使用時には、フラグメンテーションを避けるために、 @code{OPTIMIZE TABLE} を時々使用します。 @xref{OPTIMIZE TABLE, , @code{OPTIMIZE TABLE}}. @item 可能ならば @code{HEAP} テーブルをスピードアップのために使用します. @xref{Table types}. @item 通常の Web サーバーの設定ならば、イメージはファイルに保存すべきです。 データベースには、それらファイルの参照(パスとか)のみを入れます。 この主な理由は、通常の Web サーバーはデータベースよりもコンテンツを よりよくキャッシュしてくれるからです。 それでファイルを使用するなら、 速いシステムをより簡単に得ることができます。 @item 重要でないデータで、よくアクセスされる物は、メモリテーブルにいれます。 (like information about the last shown banner for users that don't have cookies). @item Columns with identical information in different tables should be declared identical and have identical names. Before Version 3.23 you got slow joins otherwise. 名前は単純にしてください（customer テーブルでは @code{customer_name} の かわりに @code{name} を使うとか）。 他の SQL サーバーへの移植を考慮するなら、 名前は 18 文字より短くすべきです。 @item もし本当にハイ・スピードが必要なら、SQL サーバーがサポートしている物とは 違う、ローレベルのデータ保存のインターフェースに注目すべきです。 例えば、 MySQL @code{MyISAM} を直接アクセスすることは、 SQL インターフェースを介してアクセスするよりも、2〜5倍速くなるでしょう。 これを可能にするには、そのデータは、アプリケーションと同じマシン上になくてはなら ず、通常、一つのプロセスだけでアクセスされるべきです。 (なぜなら、外部ファイルロックは、とても遅いから)。 上の問題は、MySQL サーバー内の @code{MyISAM} のローレベルのコマンドの 導入で解決できるでしょう。 (これはよりよいパフォーマンスを得ることの出来る、 簡単な方法の一つです)。 By carefully designing the database interface, it should be quite easy to support this types of optimization. @item 多くの場合、データベースからデータをアクセスする方が(接続を維持していれば)、 テキストファイルからデータをアクセスするよりも速いです。 なぜなら、 データベースはテキストファイルよりもコンパクトになり（数値データの場合）、 このため、ディスクアクセスが少なくなるからです。 また、行や項目を見つけるために、テキストファイルを解析する必要も省けます。 @item レプリケーションもスピードアップに使用できるでしょう。 @xref{Replication}. @item @code{DELAY_KEY_WRITE=1} が定義されたテーブルは、インデックスの更新が速くなります。 これはそのインデックス・ファイルが閉じられるまでディスクに記録されないからです。 したがって、なにかが途中で @code{mysqld} をキルしてもテーブルが大丈夫なようにす るため、@code{mysqld} を起動する前には、@code{myisamchk} をそれらのテーブルに 対して実行すべきです。 As the key information can always be generated from the data, you should not lose anything by using @code{DELAY_KEY_WRITE}. @end itemize @node Locking Issues, Optimizing Database Structure, Query Speed, MySQL Optimisation @section Locking Issues @menu * Internal locking:: How MySQL Locks Tables * Table locking:: Table Locking Issues @end menu @node Internal locking, Table locking, Locking Issues, Locking Issues @subsection MySQL はどのようにテーブルをロックするか @cindex internal locking @cindex locking, tables @cindex tables, locking 付録に、異なるロックする方法に関する議論があります。 @xref{Locking methods}. MySQL の全てのロックはデッドロックフリーです。(except for @code{InnoDB} and @code{BDB} type tables.) これは、常にクエ リ開始時に一度ロックを必要とする全てを要求し、常に同じ順でテーブルをロッ クすることで管理されます。 @code{InnoDB} type tables automatically acquire their row locks and @code{BDB} type tables their page locks during the processing of SQL statements, not at the start of the transaction. MySQL が使用する @code{WRITE} ロックは次のように働きます: @itemize @bullet @item テーブル上にロックがない場合 write ロックを置きます。 @item そうでなければ write ロックキューにロックを置きます。 @end itemize MySQL の @code{READ} ロックは次のように動きます: @itemize @bullet @item テーブル上に write ロックがない場合 read ロックを置きます。 @item そうでなければ read ロックキューにロックを置きます。 @end itemize ロックが解放されたとき、最初に write ロックキュー内のスレッドに、その後 read ロックキュー内のスレッドにロックを与えます。 これは、同じテーブルで多くの更新をする場合、@code{SELECT} 構文は update がなくなるまで待たされることを意味します。 同じテーブルで多くの @code{INSERT} と多くの @code{SELECT} を行う場合、これを解決 するには、他のテーブルに行を挿入して、たまに、その一時テーブルから全ての レコードをもう一方のテーブルに update します。 これは次のコードで行えます: @example mysql> LOCK TABLES real_table WRITE, insert_table WRITE; mysql> INSERT INTO real_table SELECT * FROM insert_table; mysql> TRUNCATE TABLE insert_table; mysql> UNLOCK TABLES; @end example 特定の場合での検索を優先的に行いたい場合、 @code{LOW_PRIORITY} オプションと共に @code{INSERT} 、 @code{UPDATE} 、 @code{DELETE} 構文、または @code{HIGH_PRIORITY} オプションと共に @code{SELECT} 構文を使用できます。 また、同様の動作を得るために、 @code{--low-priority-updates} オプション と共に @code{mysqld} を開始することができます。 @code{SQL_BUFFER_RESULT} の使用はさらにテーブル・ロックをより短くするために有効かもしれません。 @xref{SELECT}. 一つのキューだけを使用するように @file{mysys/thr_lock.c} 内のロックコードを変更 することもできます。この場合、いくつかのアプリケーションのために、 write ロックは read ロックと同じ優先順位にします。 @node Table locking, , Internal locking, Locking Issues @subsection テーブル・ロッキングの問題 @cindex problems, table locking MySQL のテーブル・ロッキングのコードはデッドロック・フリーです。 MySQL はとても速いロックスピードを得るために、 (レコードのロックやフィールドのロックの代わりに) テーブルのロックを使用します。 (except @code{InnoDB} and @code{BDB} tables) 大きなテーブルには、 テーブルのロックはレコードのロックよりはるかに良いですが、 いくつかの落とし穴があります。 @code{BDB} と @code{InnoDB} のテーブルでは、 @code{LOCK TABLES} を使用して 明示的にテーブルをロックするか、 @code{ALTER TABLE} のようなテーブル中のすべて のレコードを修正するコマンドを実行した場合にのみ、MySQLはテーブル・ロッキングを使用 します。これらのテーブル・タイプについては、 @code{LOCK TABLES} を全く使用 しないことを推奨します。 because @code{InnoDB} uses automatic row level locking and @code{BDB} uses page level locking to ensure transaction isolation. MySQL バージョン 3.23.7 以上では、 あるスレッドが @code{MyISAM} テーブルを読んでいる最中に、 同じテーブルにレコードを挿入する事ができます。 現在、これは挿入が行われる時に、テーブルのレコードを削除した後にホールがない場合にのみ 動作することに注意してください。すべてのホールが新しいデータで満たされた時に、 自動的に同時挿入が再び可能になります。 テーブルのロックはたくさんのスレッドが同時にあるテーブルから読み出すのを可能にし ますが、もしあるスレッドがあるテーブルに対し書込み要求を出す場合、 それはまず最初に排他的なアクセスを得なければなりません. その更新の間、更新が完了するまで、この特定のテーブルにアクセスしようとする 他の全てのスレッドが待たされることになります。 通常データベースの更新は @code{SELECT} よりも重要とされるため、 テーブルを更新する全てのスレッドが、テーブルから情報を検索するスレッドよりも 高い優先順位を持ちます。 これは ある特定のテーブルに対して、多くの重いクエリが発 行された場合に、 更新が不完全に終わらないことを確実にするためです。 (これは、 @code{LOW_PRIORITY} と共に更新を行うステートメントを用いるか、 @code{HIGH_PRIORITY} と共に @code{SELECT} ステートメントを用いることにより 変更が可能です。) @strong{MySQL バージョン 3.23.7} から、@code{max_write_lock_count} 変数が使用で きます。 これは、一つのテーブルに対して、指定された回数だけ INSERT が行われた後に、 @code{SELECT} を発行するようにします。 テーブルロッキングは以下の場合にはあまり良くありません： @itemize @bullet @item あるクライアントが実行に長い時間のかかる @code{SELECT} を発行。 @item その後に、他のクライアントが、使用されているテーブルに対し @code{UPDATE} を発行； このクライアントは先の @code{SELECT} が完了するまで待ちます @item さらに他のクライアントが同じテーブルに対して @code{SELECT} 構文を発行； @code{UPDATE} は @code{SELECT} よりも高い優先度を持つので、 この @code{SELECT} は先の @code{UPDATE} が完了するまで待ちます。 これは一番最初の @code{SELECT} が 終了するまで待たされます！ @item スレッドが @code{full disk} のような待機状態になっている場合、 問題のテーブルにアクセスを行おうとした全てのスレッドもまた、 より多くのディスク・スペースが利用可能になるまで待機状態に入ります。 @end itemize この問題のいくつかの可能な解決は以下の通りです： @itemize @bullet @item @code{SELECT} 構文を速く実行できるように試みます； これを行うにあたり、 いくつかのサマリーテーブルを作成しなければならないかもしれません. @item @code{mysqld} を @code{--low-priority-updates} オプションで起動。 これは全てのあるテーブルを更新する構文に対して、 @code{SELECT} 構文よりも 低い優先度を与えます。 この場合、前述のシナリオ中の最後の @code{SELECT} 構文は @code{INSERT} 構文が完了する前に実行されます。 @item @code{LOW_PRIORITY} 属性指定を用いて、 @code{INSERT},@code{UPDATE},@code{DELETE} 構文に低い優先度を与えることも出来ます。 @item ある程度の数の @code{WRITE} ロックの後に @code{READ} ロックを与えるために、 @code{max_write_lock_count} を低い値にして @code{mysqld} を開始します。 @item SQL コマンドの @code{SET LOW_PRIORITY_UPDATES=1} (ver. 4.0.3 未満では @code{SET SQL_LOW_PRIORITY_UPDATES=1} ) を使用して、 ある特定のスレッドからの全ての更新を、低い優先度に指定する事ができます。 @xref{SET OPTION, , @code{SET}}. @item @code{HIGH_PRIORITY} 属性を用いて、特定の @code{SELECT} がとても重要であると 指定することが可能です。. @xref{SELECT, , @code{SELECT}}. @item もし @code{INSERT} と @code{SELECT} をあわせて使用した場合に問題が起きた場合、 新しい @code{MyISAM} テーブルに切り替えます。 これは @code{SELECT} と @code{INSERT} を同時に行えます。 @item もし @code{INSERT} と @code{SELECT} 構文を主に混在させるのなら、 @code{INSERT} の @code{DELAYED} 属性指定はこの問題を解決させるでしょう。 @xref{INSERT, , @code{INSERT}}. @item もし @code{SELECT} と @code{DELETE} で問題があるなら、 @code{DELETE} の @code{LIMIT} オプションが助けになるでしょう。 @xref{DELETE, , @code{DELETE}}. @end itemize @node Optimizing Database Structure, Optimizing the Server, Locking Issues, MySQL Optimisation @section Optimizing Database Structure @menu * Design:: Design Choices * Data size:: Get Your Data as Small as Possible * MySQL indexes:: How MySQL Uses Indexes * Indexes:: Column Indexes * Multiple-column indexes:: Multiple-Column Indexes * Open tables:: Why So Many Open tables? * Table cache:: How MySQL Opens and Closes Tables * Creating many tables:: Drawbacks to Creating Large Numbers of Tables in the Same Database @end menu @node Design, Data size, Optimizing Database Structure, Optimizing Database Structure @subsection Design Choices @cindex design, choices @cindex database design @cindex storage of data @code{MySQL} は、レコードのデータとインデックスを別のファイルに保存します。 他の多くの(ほとんど全て)データベースでは、同じファイルにデータとインデックスを 混在させて保存します。 我々は、最近のシステムには、MySQL の選択の方が 良いと信じています。 Another way to store the row data is to keep the information for each column in a separate area (examples are SDBM and Focus). This will cause a performance hit for every query that accesses more than one column. Because this degenerates so quickly when more than one column is accessed, we believe that this model is not good for general purpose databases. The more common case is that the index and data are stored together (like in Oracle/Sybase et al). In this case you will find the row information at the leaf page of the index. The good thing with this layout is that it, in many cases, depending on how well the index is cached, saves a disk read. The bad things with this layout are: @itemize @bullet @item Table scanning is much slower because you have to read through the indexes to get at the data. @item You can't use only the index table to retrieve data for a query. @item You lose a lot of space, as you must duplicate indexes from the nodes (as you can't store the row in the nodes). @item Deletes will degenerate the table over time (as indexes in nodes are usually not updated on delete). @item It's harder to cache ONLY the index data. @end itemize @node Data size, MySQL indexes, Design, Optimizing Database Structure @subsection 可能な限りデータを小さくする @cindex data, size @cindex reducing, data size @cindex storage space, minimizing @cindex tables, improving performance @cindex performance, improving One of the most basic optimization is to get your data (and indexes) to take as little space on the disk (and in memory) as possible. This can give huge improvements because disk reads are faster and normally less main memory will be used. Indexing also takes less resources if done on smaller columns. MySQL supports a lot of different table types and row formats. Choosing the right table format may give you a big performance gain. @xref{Table types}. 以下に挙げるテクニックを使用すれば、テーブルでのパフォーマンスの向上、 保存領域の縮小化が可能でしょう： @itemize @bullet @item 可能ならば、一番小さな型を使用します。 MySQL は ディスクとメモリーを節約する多くの型を持っています。 @item より小さな整数型を可能ならば使用します。 例えば、 @code{MEDIUMINT} は @code{INT} より良いでしょう。 @item 可能ならフィールドを @code{NOT NULL} に定義してください。これは全てをより速くし、 各フィールド毎に1ビットを節約します。 Note that if you really need @code{NULL} in your application you should definitely use it. Just avoid having it on all columns by default. @item 可変長のフィールド (@code{VARCHAR}, @code{TEXT}, @code{BLOB}) を持たない場合は、 固定サイズレコード形式が使用されます。 これはかなり速いです。しかしあいにくいくらかの領域を浪費します。 @xref{MyISAM table formats, , @code{MyISAM} table formats}. @item それぞれのテーブルは可能な限り短いプライマリ・インデックスを持つべきです。 これは１レコードを一意にし、効率的にします。 @item それぞれのテーブルについて、どのテーブルの形式を使用するかを 決めます。 @xref{Table types}. @item 本当に必要な物にだけインデックスを作成します。 インデックスは検索には良いですが、より速く保存したい場合には良くありません。 もしテーブルをフィールドの組み合わせでサーチすることがほとんどであれば、 それらにインデックスを作成します。 最初のインデックスの部分は、もっとも 使用されるフィールドにすべきです。 If you are ALWAYS using many columns, you should use the column with more duplicates first to get better compression of the index. @item もしインデックスが頭からの何文字かで一意性を持っているなら、この部分にだけ インデックスを張る方が良いでしょう。 MySQL は文字列フィールドの 一部分に対してのインデックスをサポートします。 短いインデックスは、ディスクスペースを節約するだけでなく、 インデックスのキャッシュに収まりやすくなることにより、ディスク・シークも少 なくなるので、速くなります。 @xref{Server parameters}. @item いくつかの状況下で、とてもよく走査されるテーブルを２つに分割することは、 利益になることがあります。 This is especially true if it is a dynamic format table and it is possible to use a smaller static format table that can be used to find the relevant rows when scanning the table. @end itemize @node MySQL indexes, Indexes, Data size, Optimizing Database Structure @subsection MySQL はどのようにインデックスを使用するか？ @cindex indexes, use of Indexes are used to find rows with a specific value of one column fast. インデックスがない場合、MySQL は、そのレコードが見つかるまで、 最初のレコードからテーブルをなめていきます。 大きなテーブルでは多くの 手間がかかります。 もし問い合わせの中にインデックスを持ったフィールドが ある場合、MySQL は全てのデータをみることなく、データの途中の位置を速く 得ることができます。 もしあるテーブルが1000レコード持っていたとすると、 順番に頭からなめていくことに比べて、これは少なくとも100倍速いことに なります。 Note that if you need to access almost all 1000 rows it is faster to read sequentially because we then avoid disk seeks. 全ての MySQL インデックス, @code{PRIMARY}, @code{UNIQUE} そして @code{INDEX()} は B tree に格納されます。 文字列は自動的に始めと終りの空白が圧縮されます。 @xref{CREATE INDEX, , @code{CREATE INDEX}}. Indexes are used to: @itemize @bullet @item @code{WHERE}節にマッチした行の素早い検索 @item join を実行したときの他のテーブルからの行の検索 @item Find the @code{MAX()} or @code{MIN()} value for a specific indexed column. This is optimized by a preprocessor that checks if you are using @code{WHERE} key_part_# = constant on all key parts < N. In this case MySQL will do a single key lookup and replace the @code{MIN()} expression with a constant. If all expressions are replaced with constants, the query will return at once: @example SELECT MIN(key_part2),MAX(key_part2) FROM table_name where key_part1=10 @end example @item テーブルをソートかグループ化する場合で、ソート(グループ化)が一番左(接頭部)の キーを使用して行われる場合(例えば @code{ORDER BY key_part_1,key_part_2 })。 もし @code{DESC} 指定があれば、全てのキーは逆順に読まれます。 @xref{ORDER BY optimisation}. @item データファイルを参照することなく値を検索する場合。 もし使用する全てのフィールドが数値でかつ、一番左から(接頭部から)キーを形成する場 合、 値はインデックスツリーから検索され、これはとても速くなります。 @example SELECT key_part3 FROM table_name WHERE key_part1=1 @end example @end itemize 以下のような @code{SELECT} 文を発行したとします： @example mysql> SELECT * FROM tbl_name WHERE col1=val1 AND col2=val2; @end example もし @code{col1} と @code{col2} に複数フィールドインデックスが定義されている場合、 すぐに思ったとおりの結果が得られます。 If separate single-column indexes exist on @code{col1} and @code{col2}, the optimizer tries to find the most restrictive index by deciding which index will find fewer rows and using that index to fetch the rows. @cindex indexes, leftmost prefix of @cindex leftmost prefix of indexes @cindex leftmost prefix of indexes もしテーブルが複数フィールドインデックスを持つなら、インデックスの接頭部一番左の 部分がレコードを見つけるための最適化に使用されます。例えば、3つのフィールド @code{(col1,col2,col3)} に対して一つのインデックスを持っていたとします。 すると、これは @code{(col1)}, @code{(col1,col2)} , @code{(col1,col2,col3)} でインデックスがサーチされます。 もし一番左に指定しているフィールドがインデックスを作成していないなら、 MySQL は部分的なインデックスを使用しません。 以下のような @code{SELECT} 文を発行したとします： @example mysql> SELECT * FROM tbl_name WHERE col1=val1; mysql> SELECT * FROM tbl_name WHERE col2=val2; mysql> SELECT * FROM tbl_name WHERE col2=val2 AND col3=val3; @end example もしインデックスが @code{(col1,col2,col3)} にあるならば、 上に示した最初のクエリだけがインデックスを使用します。二番目三番目のクエリは インデックスを持つフィールドを発動しますが、 @code{(col2)} と @code{(col2,col3)} は、@code{(col1,col2,col3)} の 接頭部一番左に指定されていません。 @findex LIKE, and indexes @findex LIKE, and wildcards @cindex indexes, and @code{LIKE} @cindex wildcards, and @code{LIKE} MySQL は、もし @code{LIKE} がワイルドカードから始まっていなくて、 ある種固定された文字で始まっているなら、 @code{LIKE} の評価にインデックスを使用します。 例えば、以下の @code{SELECT} 文はインデックスを使用します: @example mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Patrick%"; mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Pat%_ck%"; @end example 一つ目の文は、@code{"Patrick" <= key_col < "Patricl"} となるレコードだけ、考慮さ れます。 二つ目の文は、@code{"Pat" <= key_col < "Pau"} となるレコードだけ、考慮されます。 以下の @code{SELECT} 文はインデックスを使用しません: @example mysql> SELECT * FROM tbl_name WHERE key_col LIKE "%Patrick%"; mysql> SELECT * FROM tbl_name WHERE key_col LIKE other_col; @end example 最初の文は、@code{LIKE} がワイルドカード文字で始まっています。 二つ目の文は、@code{LIKE} が定数ではありません。 MySQL 4.0 does another optimisation on @code{LIKE}. If you use @code{... LIKE "%string%"} and @code{string} is longer than 3 characters, MySQL will use the @code{Turbo Boyer-Moore} algorithm to initialise the pattern for the string and then use this pattern to perform the search quicker. @findex IS NULL, and indexes @cindex indexes, and @code{IS NULL} Searching using @code{column_name IS NULL} will use indexes if column_name is an index. MySQL は通常、一番少ないレコード数を見つけるインデックスを使用します。 インデックスは次に示す演算子を用いて比較できるフィールドに対して使用されます： @code{=}, @code{>}, @code{>=}, @code{<}, @code{<=}, @code{BETWEEN} そして @code{'something%'} の様に頭にワイルドカードがない @code{LIKE}。 @code{WHERE} 節内の全ての @code{AND} にかからないインデックスは、 全くクエリの最適化に使用されません。 In other words: To be able to use an index, a prefix of the index must be used in every @code{AND} group. 以下の @code{WHERE} 節はインデックスを使用します： @example ... WHERE index_part1=1 AND index_part2=2 AND other_column=3 ... WHERE index=1 OR A=10 AND index=2 /* index = 1 OR index = 2 */ ... WHERE index_part1='hello' AND index_part_3=5 /* optimized like "index_part1='hello'" */ ... WHERE index1=1 and index2=2 or index1=3 and index3=3; /* Can use index on index1 but not on index2 or index 3 */ @end example 以下の @code{WHERE} 節はインデックスを@strong{使用しません}： @example ... WHERE index_part2=1 AND index_part3=2 /* index_part_1 is not used */ ... WHERE index=1 OR A=10 /* Index is not used in both AND parts */ ... WHERE index_part1=1 OR index_part2=10 /* No index spans all rows */ @end example Note that in some cases MySQL will not use an index, even if one would be available. Some of the cases where this happens are: @itemize @bullet @item If the use of the index would require MySQL to access more than 30% of the rows in the table. (In this case a table scan is probably much faster, as this will require us to do much fewer seeks.) Note that if such a query uses @code{LIMIT} to only retrieve part of the rows, MySQL will use an index anyway, as it can much more quickly find the few rows to return in the result. @end itemize @node Indexes, Multiple-column indexes, MySQL indexes, Optimizing Database Structure @subsection Column Indexes @cindex indexes, columns @cindex columns, indexes @cindex keys MySQL の全てのフィールドはインデックスを持つことができます。 適切なフィールドでのインデックスの使用は、@code{SELECT} の 性能を向上する最良の方法です。 キーの最大数と最大インデックス長は storage engine 毎に定義されます。 @xref{Table types}。すべてのテーブルハンドラで少なくとも 16 個のキーと少な くとも合計 256 バイトのインデックス長を持つことができます。 @code{CHAR} と @code{VARCHAR} フィールドには接頭部にインデックスを持つことが できます。フィールド全体をインデックス化するより、 これははるかに早く、少ないディスク容量でできます。 @code{CREATE TABLE} 構文でフィールドにインデックスを作るには、 以下のようにします： @example KEY index_name (col_name(length)) @end example 以下の例は @code{name} フィールドの最初の10文字にインデックスを創り出します: @example mysql> CREATE TABLE test ( -> name CHAR(200) NOT NULL, -> KEY index_name (name(10))); @end example @code{BLOB} と @code{TEXT} フィールドでは、そのフィールドの頭の部分に インデックスを張らなくてはなりません。 フィールドの全体にインデックスは張れません。 MySQL バージョン 3.23.23 以降では、特殊な @code{FULLTEXT} イン デックスを生成することもできます。これは全文検索に使用されます。 @code{MyISAM} テーブル型だけが @code{FULLTEXT} インデックスをサポートしま す。これは @code{CHAR}, @code{VARCHAR} と @code{TEXT} フィールドだけに生成できます。イ ンデックスは常にフィールド全体に対して行なわれ、部分インデックスはサポート されません。詳細は @ref{Fulltext Search}. @node Multiple-column indexes, Open tables, Indexes, Optimizing Database Structure @subsection Multiple-Column Indexes @cindex multi-column indexes @cindex indexes, multi-column @cindex keys, multi-column MySQL は異なるフィールドのセットに一つのインデックスを持つことができます。 インデックスは最大15個のコラムまで許されます。 (@code{CHAR} と @code{VARCHAR} フィールドの接頭部をインデックスとして使用できます) 複数フィールドインデックスは、 ソートされた配列(インデックス化されたフィールドの値が結合されている配列) を扱うことができます。 インデックス化されたコラムに対して、既知の値を @code{WHERE} 節で指定した時、 たとえ他のフィールドの値を指定しなくとも、 MySQL は複数フィールドインデックスを使用します。 以下のテーブルがあると仮定してください： @example mysql> CREATE TABLE test ( -> id INT NOT NULL, -> last_name CHAR(30) NOT NULL, -> first_name CHAR(30) NOT NULL, -> PRIMARY KEY (id), -> INDEX name (last_name,first_name)); @end example @code{name} インデックスは、@code{last_name} と @code{first_name} にまたがるイン デックスです。 このインデックスは、@code{last_name} に対するクエリや、 @code{name} インデックスは以下のクエリで使われます： @example mysql> SELECT * FROM test WHERE last_name="Widenius"; mysql> SELECT * FROM test WHERE last_name="Widenius" -> AND first_name="Michael"; mysql> SELECT * FROM test WHERE last_name="Widenius" -> AND (first_name="Michael" OR first_name="Monty"); mysql> SELECT * FROM test WHERE last_name="Widenius" -> AND first_name >="M" AND first_name < "N"; @end example しかし @code{name} インデックスは以下のクエリでは使用されません: @example mysql> SELECT * FROM test WHERE first_name="Michael"; mysql> SELECT * FROM test WHERE last_name="Widenius" -> OR first_name="Michael"; @end example MySQL がクエリの性能を上げるためにどうインデックスを使用しているか、 より詳しい情報はこちら： @ref{MySQL indexes, , MySQL indexes}. @node Open tables, Table cache, Multiple-column indexes, Optimizing Database Structure @subsection 何故そんなに多くのテーブルをオープンするのか？ @cindex tables, open @cindex open tables @code{mysqladmin status} を実行すると、次のようなものが得られます: @example Uptime: 426 Running threads: 1 Questions: 11082 Reloads: 1 Open tables: 12 @end example 確かにたった6個しかテーブルがないのに、このような結果が出るので少々戸惑われるか もしれません。 MySQL はマルチスレッドなので、同じテーブルで一度に多くのクエリを持て ます。 同じファイル上では2つスレッドはそれぞれ別の異なる状態を持つという 問題を最小化するため、テーブルは同時に動作する各スレッドにより個々に オープンされます。 これは少しメモリを食いますが、パフォーマンスは良くなります。 @code{ISAM} と @code{MyISAM} テーブルでは、データファイルのために 一つのファイル記述子を使用します。 インデックスファイル記述子は全てのスレッド間で共有されます。 You can read more about this topic in the next section. @xref{Table cache}. @node Table cache, Creating many tables, Open tables, Optimizing Database Structure @subsection MySQL はどのようにテーブルのオープン & クローズを行なうか？ @findex table_cache @cindex tables, opening @cindex tables, closing @cindex opening, tables @cindex closing, tables @cindex table cache @code{table_cache} , @code{max_connections} , @code{max_tmp_tables} は サーバーが開いた状態にしておく事が出来るファイルの最大数に影響します。 もしこれらの変数のうちの一つ、あるいは複数を増加させるなら、 あなたのオペレーティング・システムの、1 プロセスあたりに開かれる ファイル・デスクリプタ の最大値を増やすことになるかもしれません。 多くのシステムではこの制限を増やすことが可能です。 これをどうやって行うかは、あなたの使用している OS のドキュメントを見てください。 制限値の変更方法は、システムによってまちまちだからです。 @code{table_cache} は @code{max_connections} に関連します。 例えば 200 のコネクションを同時に開けるなら、少なくとも @code{200 * n} の テーブル・キャッシュが必要です。 ここで @code{n} は join におけるテーブルの 最大数です。 You also need to reserve some extra file descriptors for temporary tables and files. Make sure that your operating system can handle the number of open file descriptors implied by the @code{table_cache} setting. If @code{table_cache} is set too high, MySQL may run out of file descriptors and refuse connections, fail to perform queries, and be very unreliable. You also have to take into account that the @code{MyISAM} storage engine needs two file descriptors for each unique open table. You can in increase the number of file descriptors available for MySQL with the @code{--open-files-limit=#} startup option. @xref{Not enough file handles}. オープンテーブルのキャッシュは最大で @code{table_cache} まで大きくなります(デ フォルトは 64, @code{mysqld} のオプション @code{-O table_cache=#} で変更可能)。 Note that in MySQL may temporarly open even more tables to be able to execute queries. A not used table is closed and removed from the table cache under the following circumstances: @itemize @bullet @item When the cache is full and a thread tries to open a table that is not in the cache. @item When the cache contains more than @code{table_cache} entries and a thread is no longer using a table. @item When someone executes @code{mysqladmin refresh} or @code{mysqladmin flush-tables}. @item When someone executes a @code{FLUSH TABLES} statement. @end itemize キャッシュがいっぱいになった場合、サーバーは以下の処置を取って キャッシュを使用できるように配置します： @itemize @bullet @item 現在使われていないテーブルが解放されます。もっとも使用されていないテーブルからか ら順に。 @item もしキャッシュが一杯でテーブルを解放することが出来ず、さらに新しいテーブルの オープン要求がある場合、キャッシュは一時的な拡張を必要とします。 @item もしそのキャッシュが一時拡張に配置されていて、かつ、テーブルが使用状態から 未使用状態に移行した場合、そのテーブルは閉じられ、キャッシュから解放されます。 @end itemize テーブルは各同時アクセスに (再び) オープンされます。これは、同じテーブルで2つの スレッドが実行されている場合、または同じクエリで(@code{AS} で)テーブルを2回 アクセスする場合、テーブルは2回オープンする必要があることを意味します。 最初のテーブルのオープンは2つのファイル記述子を使用し、続くテーブルの各使用は 1つだけのファイル記述子を使用します。 If you are opening a table with the @code{HANDLER table_name OPEN} statement, a dedicated table object is allocated for the thread. This table object is not shared by other threads an will not be closed until the thread calls @code{HANDLER table_name CLOSE} or the thread dies. @xref{HANDLER, , @code{HANDLER}}. When this happens, the table is put back in the table cache (if it isn't full). You can check if your table cache is too small by checking the @code{mysqld} variable @code{Opened_tables}. If this is quite big, even if you haven't done a lot of @code{FLUSH TABLES}, you should increase your table cache. @xref{SHOW STATUS, , @code{Opened_tables}}. @node Creating many tables, , Table cache, Optimizing Database Structure @subsection Drawbacks to Creating Large Numbers of Tables in the Same Database @cindex tables, too many もしたくさんのファイルが一つのディレクトリにある場合、オープン、クローズ、 create 操作は遅くなるでしょう。 もし @code{SELECT} 文を多くのテーブルに対し 実行した場合、テーブルキャッシュが一杯ならば、このオーバーヘッドは多くなるでしょ う。 なぜなら、それぞれのテーブルにつきオープンし、クローズしなくてはならないからです。 このオーバーヘッドを緩和するには、テーブルキャッシュを大きくします。 @node Optimizing the Server, Disk issues, Optimizing Database Structure, MySQL Optimisation @section Optimizing the MySQL Server @menu * System:: System/Compile Time and Startup Parameter Tuning * Server parameters:: Tuning Server Parameters * Compile and link options:: How Compiling and Linking Affects the Speed of MySQL * Memory use:: How MySQL Uses Memory * DNS:: How MySQL uses DNS * SET OPTION:: @code{SET} Syntax @end menu @node System, Server parameters, Optimizing the Server, Optimizing the Server @subsection システム、コンパイル時、スタートパラメターのチューニング @cindex compiling, optimizing @cindex system optimization @cindex startup parameters, tuning We start with the system level things since some of these decisions have to be made very early. In other cases a fast look at this part may suffice because it not that important for the big gains. However, it is always nice to have a feeling about how much one could gain by changing things at this level. 使うべき OS はとても重要です！ 複数の CPU を持つマシンでは、 Solaris (なぜなら、Solaris のスレッドはとても素晴らしく動作するから)、 あるいは、Linux ( kernel 2.2 は良い SMP をサポートしているから) を 使用すべきです。 32bit マシンの Linux では、2G bytes のファイルサイズの 制限があります。 これは新しいファイルシステム (XFS/ReiserFS) のリリース時に なくなって欲しいものです。 If you have a desperate need for files bigger than 2G on Linux-intel 32 bit, you should get the LFS patch for the ext2 file system. Because we have not run MySQL in production on that many platforms, we advice you to test your intended platform before choosing it, if possible. @cindex locking Other tips: @itemize @bullet @item 充分 RAM があるならば、全ての swap を外してもよいでしょう。 いくつかのシステムでは、たとえメモリーが空いていても、 swap を使用する場合があります。 @item 外部のロックを避けるため、@code{--skip-external-locking} (ver.4.0.3未満では @code{--skip-locking}) MySQL オプション を使用します。 Note that this will not impact MySQL's functionality as long as you only run one server. Just remember to take down the server (or lock relevant parts) before you run @code{myisamchk}. On some system this switch is mandatory because the external locking does not work in any case. MIT-pthread でコンパイルする時は @code{--skip-external-locking} (ver.4.0.3未満では @code{--skip-locking}) がデフォルトです。 これは全てのプラットフォームで MIT-pthread が @code{flock()} を完全にサポートし ていないためです。 It's also on default for Linux as Linux file locking are not yet safe. @code{--skip-external-locking} (ver.4.0.3未満では @code{--skip-locking}) が使用できないただ一つの状態は、 もしあなたが複数の MySQL @emph{サーバー} (クライアントではない) を 同じデータに対して走らせている場合です。 You can still use @code{LOCK TABLES}/@code{UNLOCK TABLES} even if you are using @code{--skip-external-locking} (ver.4.0.3未満では @code{--skip-locking}) @end itemize @node Server parameters, Compile and link options, System, Optimizing the Server @subsection サーバーパラメーターのチューニング @cindex parameters, server @cindex @code{mysqld} server, buffer sizes @cindex buffer sizes, @code{mysqld} server @cindex startup parameters @code{mysqld} サーバーが使用している現在のバッファサイズを次で得ることができます: @example shell> mysqld --help @end example @cindex @code{mysqld} options @cindex variables, @code{mysqld} この結果、全ての @code{mysqld} オプションと次のようなコンフィグ可能変数のリスト を得られます。出力結果にはデフォルト値が含まれ、以下のように表示されます: @example Possible variables for option --set-variable (-O) are: back_log current value: 5 bdb_cache_size current value: 1048540 binlog_cache_size current value: 32768 connect_timeout current value: 5 delayed_insert_timeout current value: 300 delayed_insert_limit current value: 100 delayed_queue_size current value: 1000 flush_time current value: 0 interactive_timeout current value: 28800 join_buffer_size current value: 131072 key_buffer_size current value: 1048540 lower_case_table_names current value: 0 long_query_time current value: 10 max_allowed_packet current value: 1048576 max_binlog_cache_size current value: 4294967295 max_connections current value: 100 max_connect_errors current value: 10 max_delayed_threads current value: 20 max_heap_table_size current value: 16777216 max_join_size current value: 4294967295 max_sort_length current value: 1024 max_tmp_tables current value: 32 max_write_lock_count current value: 4294967295 myisam_sort_buffer_size current value: 8388608 net_buffer_length current value: 16384 net_retry_count current value: 10 net_read_timeout current value: 30 net_write_timeout current value: 60 read_buffer_size current value: 131072 record_rnd_buffer_size current value: 131072 slow_launch_time current value: 2 sort_buffer current value: 2097116 table_cache current value: 64 thread_concurrency current value: 10 tmp_table_size current value: 1048576 thread_stack current value: 131072 wait_timeout current value: 28800 @end example Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--var=option} on its own. もし @code{mysqld} サーバーを走らせているなら、以下のコマンドでも変数の値を見る ことができます: @example shell> mysqladmin variables @end example You can find a full description for all variables in the @code{SHOW VARIABLES} section in this manual. @xref{SHOW VARIABLES}. You can also see some statistics from a running server by issuing the command @code{SHOW STATUS}. @xref{SHOW STATUS}. MySQL はとてもスケーラブルなアルゴリズムを使用します。そのため 通常はとても少ないメモリで動作します。しかし MySQL に多くのメモリを 与えれば、より良い性能を得ることができます。 When tuning a MySQL server, the two most important variables to use are @code{key_buffer_size} and @code{table_cache}. You should first feel confident that you have these right before trying to change any of the other variables. 多くのメモリ(>=256M)と多くのテーブルを持っていて、適度のクライアント数で最大性能 を得たい場合、次のようなものを使用します: @example shell> safe_mysqld -O key_buffer=64M -O table_cache=256 \ -O sort_buffer=4M -O read_buffer_size=1M & @end example If you have only 128M and only a few tables, but you still do a lot of sorting, you can use something like: @example shell> safe_mysqld -O key_buffer=16M -O sort_buffer=1M @end example 多くの接続で少ないメモリしかない場合、次のようなものを使用します @example shell> safe_mysqld -O key_buffer=512k -O sort_buffer=100k \ -O read_buffer_size=100k & @end example or even: @example shell> safe_mysqld -O key_buffer=512k -O sort_buffer=16k \ -O table_cache=32 -O read_buffer_size=8k -O net_buffer_length=1K & @end example If you are doing a @code{GROUP BY} or @code{ORDER BY} on files that are much bigger than your available memory you should increase the value of @code{record_rnd_buffer} to speed up the reading of rows after the sorting is done. When you have installed MySQL, the @file{support-files} directory will contain some different @file{my.cnf} example files, @file{my-huge.cnf}, @file{my-large.cnf}, @file{my-medium.cnf}, and @file{my-small.cnf}, you can use as a base to optimize your system. もしとても多くの接続があり、@code{mysqld} が各接続に対して少ないメモリーで 動作するように設定されていれば、スワップの読み書きによるパフォーマンスの低下がお きます。 もちろん十分なメモリーがあれば、全ての接続にたいして @code{mysqld} のパフォーマ ンス良くなります。 @code{mysqld} へのオプションを変更する場合、そのサーバのインスタンスにだけに 有効であることに注意して下さい。 パラメータ変更の効果を見るには、このようにします: @example shell> mysqld -O key_buffer=32m --help @end example @code{--help} オプションは最後につけてください。 その他のオプションを --help の後につけると、そのオプションは反映されません。 @node Compile and link options, Memory use, Server parameters, Optimizing the Server @subsection MySQL の速度に影響するコンパイルとリンク方法 @cindex linking, speed @cindex compiling, speed @cindex speed, compiling @cindex speed, linking 次のテストの多くは Linux 上で MySQL ベンチマークで行われました。 しかし、これらは他の OS についてもいくつかの指標を与えます。 @code{-static} でのリンク時に最速の実行形式を得ます。 Linux では、@code{pgcc} と @code{-O3} でコンパイルした時に最速のコードを得られます。 このオプションで @file{sql_yacc.cc} をコンパイルすると、@code{gcc/pgcc} は 全ての関数をインラインにするために多くのメモリを必要とするので、200M のメモリが 必要です。 @code{libstdc++} ライブラリの増加を避けるためには、 MySQL の configure 時に @code{CXX=gcc} も設定すべきです。 Note that with some versions of @code{pgcc}, the resulting code will only run on true Pentium processors, even if you use the compiler option that you want the resulting code to be working on all x586 type processors (like AMD). より良いコンパイラー、そしてコンパイラーのオプションは、10-30% の 速度の向上をもたらします。 これはあなた自身が MySQL をコンパイルする 時に重要なことです！ 我々は Cygnus CodeFusion と Fujitsu コンパイラーでもテストしましたが、 MySQL を最適化オプションでコンパイルするには、 どちらもまだ完全なバグ・フリーではありませんでした。 When you compile MySQL you should only include support for the character sets that you are going to use. (Option @code{--with-charset=xxx}). The standard MySQL binary distributions are compiled with support for all character sets. Here is a list of some measurements that we have done: @itemize @bullet @item @code{pgcc} を使用して @code{-O6} で全てをコンパイルすると、 @code{gcc} 2.95.2 より、@code{mysqld} サーバーは 1% 速くなります。 @item Linux 上では、動的リンク(@code{-static}) 無し)の場合、結果は 13% 遅くなります。 Note that you still can use a dynamic linked MySQL library. It is only the server that is critical for performance. @item If you strip your @code{mysqld} binary with @code{strip libexec/mysqld}, the resulting binary can be up to 4% faster. @item (localhost への接続に) Unix ソケットの代わりに TCP/IP を使用すると、結果は 7.5% 遅くなります。 (@code{localhost} へ接続する場合、MySQL はデフォルトではソケット を使用します)。 @item If you connect using TCP/IP from another computer over a 100M Ethernet, things will be 8-11% slower. @item When running our benchmark tests using secure connections (all data encrypted with internal SSL support) things were 55% slower. @item @code{--with-debug=full} でコンパイルすると、ほとんどのクエリで 20% 遅くな りますが、いくつかのクエリは実質的にはもっと長くなります(MySQL ベ ンチマークでは 35% 遅くなりました)。 @code{--with-debug} を使用すると、15% だけ遅くなります。 By starting a @code{mysqld} version compiled with @code{--with-debug=full} with @code{--skip-safemalloc} the end result should be close to when configuring with @code{--with-debug}. @item On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster than @code{gcc} 3.2 @item On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster in 32 bit mode than in 64 bit mode. @item UltraSPARC で @code{gcc} 2.95.2 でオプション @code{-mcpu=v8 -Wa,-xarch=v8plusa} をつけてコンパイルすると 4% 良い性能が得られます。 @item シングルプロセッサの Solaris 2.5.1 では、MIT-pthreads は Solaris ネイティブスレ ッドより 8-12% 遅くなります。 With more load/CPUs the difference should get bigger. @item @code{--log-bin} での実行は mysqld を 1% 遅くします。 @item Compiling on Linux-x86 using gcc without frame pointers @code{-fomit-frame-pointer} or @code{-fomit-frame-pointer -ffixed-ebp} makes @code{mysqld} 1-4% faster. @end itemize The MySQL-Linux distribution provided by MySQL AB used to be compiled with @code{pgcc}, but we had to go back to regular gcc because of a bug in @code{pgcc} that would generate the code that does not run on AMD. We will continue using gcc until that bug is resolved. In the meantime, if you have a non-AMD machine, you can get a faster binary by compiling with @code{pgcc}. The standard MySQL Linux binary is linked statically to get it faster and more portable. @node Memory use, DNS, Compile and link options, Optimizing the Server @subsection MySQL はどのようにメモリを使用するのか？ @cindex memory use 以下に @code{mysqld} サーバーがどのようにメモリーを使用するか、いくつか示します。 サーバーに与える変数名は、サーバーのメモリーの使用方に関連した名前となっています: @itemize @bullet @item キーバッファ (変数 @code{key_buffer}) は全てのスレッドで共有され、 残りは必要時に割り当てられます。 @xref{Server parameters}. @item 各接続はいくつかのスレッド空間を使用します； スタック (64K, 変数 @code{thread_stack}), 接続バッファ(variable @code{net_buffer_length}), 結果バッファ(variable @code{net_buffer_length})。接続バッファと結果バッファは必要となった時、 動的に最大 @code{max_allowed_packet} まで増えます。 クエリが走っている時、そのクエリの文字のコピーが割り当てられます。 @item 全てのスレッドは同じベースメモリを共有します。 @item 圧縮された @code{ISAM} / @code{MyISAM} だけが、memory mapped されます。 これは 4GB の 32bit メモリ空間は多くの大きなテーブルを扱うには小さいためです。 64bit アドレス空間を持つシステムがより普及すれば、我々は mmemory mapping を通常 にサポートします。 @item テーブルを越えて順次スキャンを行なう各要求は、読み込みバッファを割り当てます (変数 record_buffer) @item When reading rows in 'random' order (for example after a sort) a random-read buffer is allocated to avoid disk seeks. (variable @code{record_rnd_buffer}). @item 全ての結合は1パスで行なわれ、多くの結合は一時テーブルを使用せずに行なわ れます。多くの一時テーブルはメモリベース(@code{HEAP})のテーブルです。大きなレコー ドサイズ (= 全フィールド長の合計) を持つ一時テーブルまたは、@code{BLOB} を含む テーブルはディスク上に置かれます。 MySQL バージョン 3.23.2 以前での問題は、@code{HEAP} テーブルが @code{tmp_table_size} のサイズを越えると、エラー @code{The table tbl_name is full} が出ることです。将来我々は、必要時にメモリ (@code{HEAP}) テーブルをディスクベー ス (@code{MyISAM}) テーブルに自動的に変更することにより、これを修正します。この 問題を回避するため、@code{mysqld} への @code{tmp_table_size} オプションま たはクライアント側で SQL オプション @code{BIG_TABLES} (ver.4.0.3未満では @code{SQL_BIG_TABLES}) で増加できます。 @xref{SET OPTION, , @code{SET} Syntax}. MySQL バージョン 3.20 では、一時テーブルの最大サイズは @code{recordbuffer*16} でした。そのため、このバージョンを使用していると、 @code{recordbuffer} を追加する必要があります。 @code{mysqld} を @code{--big-tables} で 開始することで、常に一時テーブルをディスク上に格納できます。しかしこれは 多くの複雑なクエリの速度に影響します。 @item ほとんどのリクエストは、0-2個の一時ファイルとわずかなソートバッファへの割り当て を行います。 @xref{Temporary files}. @item パースと演算時に使用されるほとんど全てのメモリはローカルメモリストア内で行 なわれます。小さな項目に必要とされるメモリオーバーヘッドはなく、通常の遅 いメモリ割り当て/解放が回避されます。メモリは予期しない大きな文字列にだ け割り当てられます(これは @code{malloc()} と @code{free()} で行なわれます)。 @item 各インデックスファイルは一度オープンされ、データファイルは各同時実行 スレッド毎に一度オープンされます。各同時スレッドには、テーブル構造、 各フィールドの構造そして @code{3 * n} のサイズのバッファが割り当てられます。 ( @code{n} は @code{BLOB} 型のフィールドの長さを含めない、一レコードの最大長です ) @code{BLOB} は 5 から 8 バイト + @code{BLOB} データの長さを使用します。 The @code{ISAM}/@code{MyISAM} table handlers will use one extra row buffer for internal usage. @item @code{BLOB} を持つ各テーブルでは、より大きな @code{BLOB} の読み込みでバッファ は動的に拡大されます。テーブルのスキャンをする場合、割り当てられたバッファは最 も大きい @code{BLOB} と同じ大きさになります。 @item 全ての使用されているテーブルの storage engine はキャッシュ内に保存され、 FIFO として管理されます。 通常、キャッシュは 64 個のテーブルです。テーブルが 2 つの実行しているス レッドで同時に使用される場合、キャッシュ内にテーブルの 2 つのエントリが あります。 @xref{Table cache}. @item @code{mysqladmin flush-tables} は使用されていない全てのテーブルをクローズし、 使用されている全てのテーブルを、実行中スレッドが終った時にクローズするよ うにマークします。これは多くの使用メモリを解放するのに有効です。全てのロ グファイルもクローズと再オープンされます。 @end itemize @strong{mysqld} 実行時、@code{ps} や他のプログラムは、それが多くのメモリ を使用していると報告するでしょう。これは異なったメモリアドレス上のスレッ ドスタックによって発生します。例えば、Solaris ps はスタック間の未使用メ モリを使用メモリとして計算します。'swap -s' で有効なスワップをチェックす ることでこれを確かめられます。我々は市販のメモリリーク検出プログラムで @code{mysqld} をテストしました。そのため、メモリリークは全くありません。 @node DNS, SET OPTION, Memory use, Optimizing the Server @subsection How MySQL uses DNS @cindex DNS @cindex hostname caching When a new thread connects to @code{mysqld}, @code{mysqld} will span a new thread to handle the request. This thread will first check if the hostname is in the hostname cache. If not the thread will call @code{gethostbyaddr_r()} and @code{gethostbyname_r()} to resolve the hostname. If the operating system doesn't support the above thread-safe calls, the thread will lock a mutex and call @code{gethostbyaddr()} and @code{gethostbyname()} instead. Note that in this case no other thread can resolve other hostnames that is not in the hostname cache until the first thread is ready. You can disable DNS host lookup by starting @code{mysqld} with @code{--skip-name-resolve}. In this case you can however only use IP names in the MySQL privilege tables. If you have a very slow DNS and many hosts, you can get more performance by either disabling DNS lookop with @code{--skip-name-resolve} or by increasing the @code{HOST_CACHE_SIZE} define (default: 128) and recompile @code{mysqld}. You can disable the hostname cache with @code{--skip-host-cache}. You can clear the hostname cache with @code{FLUSH HOSTS} or @code{mysqladmin flush-hosts}. If you don't want to allow connections over @code{TCP/IP}, you can do this by starting @code{mysqld} with @code{--skip-networking}. @node SET OPTION, , DNS, Optimizing the Server @subsection @code{SET} 構文 @findex SET OPTION @example SET [GLOBAL | SESSION] sql_variable=expression, [[GLOBAL | SESSION] sql_variable=expression...] @end example @code{SET OPTION} はサーバやクライアントの操作に影響する様々なオプションを設定します. 現在のセッションが終わるか,またはあなたが異なった値にオプションを設定するまで, 設定されたオプション値は残っています. @code{SET} sets various options that affect the operation of the server or your client. The following examples shows the different syntaxes one can use to set variables: In old MySQL versions we allowed the use of the @code{SET OPTION} syntax, but this syntax is now deprecated. In MySQL 4.0.3 we added the @code{GLOBAL} and @code{SESSION} options and access to most important startup variables. @code{LOCAL} can be used as a synonym for @code{SESSION}. If you set several variables on the same command line, the last used @code{GLOBAL | SESSION} mode is used. @example SET sort_buffer_size=10000; SET @@@@local.sort_buffer_size=10000; SET GLOBAL sort_buffer_size=1000000, SESSION sort_buffer_size=1000000; SET @@@@sort_buffer_size=1000000; SET @@@@global.sort_buffer_size=1000000, @@@@local.sort_buffer_size=1000000; @end example The @code{@@@@variable_name} syntax is supported to make MySQL syntax compatible with some other databases. The different system variables one can set are described in the system variable section of this manual. @xref{System Variables}. If you are using @code{SESSION} (the default) the option you set remains in effect until the current session ends, or until you set the option to a different value. If you use @code{GLOBAL}, which require the @code{SUPER} privilege, the option is remembered and used for new connections until the server restarts. If you want to make an option permanent, you should set it in one of the MySQL option files. @xref{Option files}. To avoid wrong usage MySQL will give an error if you use @code{SET GLOBAL} with a variable that can only be used with @code{SET SESSION} or if you are not using @code{SET GLOBAL} with a global variable. If you want to set a @code{SESSION} variable to the @code{GLOBAL} value or a @code{GLOBAL} value to the MySQL default value, you can set it to @code{DEFAULT}. @example SET max_join_size=DEFAULT; @end example This is identical to: @example SET @@@@session.max_join_size=@@@@global.max_join_size; @end example If you want to restrict the maximum value a startup option can be set to with the @code{SET} command, you can specify this by using the @code{--maximum-variable-name} command line option. @xref{Command-line options}. You can get a list of most variables with @code{SHOW VARIABLES}. @xref{SHOW VARIABLES}. You can get the value for a specific value with the @code{@@@@[global.|local.]variable_name} syntax: @example SHOW VARIABLES like "max_join_size"; SHOW GLOBAL VARIABLES like "max_join_size"; SELECT @@@@max_join_size, @@@@global.max_join_size; @end example Here follows a description of the variables that uses a the variables that uses a non-standard @code{SET} syntax and some of the other variables. The other variable definitions can be found in the system variable section, among the startup options or in the description of @code{SHOW VARIABLES}. @xref{System Variables}. @xref{Command-line options}. @xref{SHOW VARIABLES}. @table @code @item CHARACTER SET character_set_name | DEFAULT これは指定されたマッピングに従って、すべての文字列をクライアントからクライアント にマップします. 現在、@code{character_set_name} に指定できるオプションは @code{cp1251_koi8} だけですが, MySQL のソース中にある @file{sql/convert.cc} ファイルを編集することによって, 容易に新しいマッピングを加えることができます. 標準のマッピングに戻すには、 @code{character_set_name} に @code{DEFAULT} を指定します。 @code{CHARACTER SET} オプションを設定するための構文は、 他のオプションを設定する構文と異なっていることに注意してください. @item PASSWORD = PASSWORD('some password') @cindex passwords, setting 現在のユーザのパスワードを設定します。いかなる非匿名のユーザも、 自分自身パスワードを変えることができます! @item PASSWORD FOR user = PASSWORD('some password') 現在ログインしているホストの特定ユーザのパスワードを設定します。 @code{mysql} データベースにアクセスができるユーザーだけが実行できます。 ユーザは @code{user@@hostname} 形式で与えなくてはなりません。 ここで @code{user} と @code{hostname} は、@code{mysql.user} テーブルの @code{User}, @code{Host} フィールドに登録されていなくてはなりません。 例えば、@code{User} と @code{Host} フィールドが @code{'bob'} と @code{'%.loc.gov'} ならば、以下のようにします： @example mysql> SET PASSWORD FOR bob@@"%.loc.gov" = PASSWORD("newpass"); @end example Which is equivalent to: @example mysql> UPDATE mysql.user SET password=PASSWORD("newpass") -> WHERE user="bob" AND host="%.loc.gov"; @end example @item SQL_AUTO_IS_NULL = 0 | 1 @code{1} (デフォルト) を設定すると、次のようにして、auto_increment レコー ドを持つテーブルで、最後に挿入されたレコードを見つけることができます: @code{WHERE auto_increment_column IS NULL}。これは、Access のようないくつ かの ODBC プログラムによって使用されます。 @item AUTOCOMMIT= 0 | 1 @code{1} を設定すると、テーブルへのすべての変更はすぐに行なわれます。 複数コマンドトランザクションを開始するためには、@code{BEGIN} ステートメ ントを使用する必要があります。@xref{COMMIT}。 @code{0} を設定すると、そのトランザクションを許可/破棄するために、 @code{COMMIT} / @code{ROLLBACK} を使用する必要があります。@xref{COMMIT}。 注意: 非 @code{AUTOCOMMIT} モードから @code{AUTOCOMMIT} モードに変更する時、 MySQL はすべてのオープントランザクションを自動的に @code{COMMIT} します。 @item BIG_TABLES = 0 | 1 (ver.4.0.3未満では SQL_BIG_TABLES) @cindex table is full @code{0} の場合、全ての一時テーブルはメモリーではなくディスクに書き出されます。 これは少し遅くなりますが、多くの一時テーブルを必要とする大きな @code{SELECT} を 実行しても、@code{The table tbl_name is full} エラーが出なくなります。 新しい接続におけるこの値のデフォルト値は @code{1} (メモリーに一時テーブルを作る) です。 @item SQL_BIG_SELECTS = 0 | 1 @code{1} の場合、とても時間のかかる @code{SELECT} が実行された場合、 MySQL はそれを中止します。 これはあまり芳しくない(間違った) @code{WHERE} 構文が発行されたときに役立ちます。 @code{max_join_size} 行以上を検討するような @code{SELECT} が 大きなクエリと定義されます。 新しい接続におけるこの値のデフォルト値は @code{0} です。 (全ての @code{SELECT} 構文を許します) @item SQL_BUFFER_RESULT = 0 | 1 @code{SQL_BUFFER_RESULT} は一時ファイルに置かれる @code{SELECT} からの結果 を強制的に置きます。これは MySQL がテーブルロックを早く解放する手 助けをし、クライアントへ結果セットを送信するために長い時間が掛かる場合に役 立ちます。 @item LOW_PRIORITY_UPDATES = 0 | 1 @code{1} の場合、全ての @code{INSERT}, @code{UPDATE}, @code{DELETE}, @code{LOCK TABLE WRITE}構文は、 対象となるテーブルを処理中の @code{SELECT} や @code{LOCK TABLE READ} がなくなるまで待ちます。 ver.4.0.3 未満では @code{SQL_LOW_PRIORITY_UPDATES} オプションになります. @item MAX_JOIN_SIZE = value | DEFAULT おそらく @code{value} よりも多いレコードの組合せを試験する必要があるような @code{SELECT} を許可しません。この値を設定することで、キーが使用されないで あろう @code{SELECT} と長い時間が掛かるであろう @code{SELECT} を捕捉できま す。これを @code{DEFAULT} 以外の値に設定すると、@code{SQL_BIG_SELECTS} フ ラグをリセットします。@code{SQL_BIG_SELECTS} フラグを再び設定すると、 @code{SQL_MAX_JOIN_SIZE} 変数は無視されます。@code{-O max_join_size=#} で @code{mysqld} を起動することで、この変数のデフォルト値を設定できます。T ver.4.0.3 未満では @code{SQL_MAX_JOIN_SIZE} オプションになります. Note that if the result of the query is already in the query cache, the above check will not be made. Instead, MySQL will send the result to the client. Since the query result is already computed and it will not burden the server to send the result to the client. @item QUERY_CACHE_TYPE = OFF | ON | DEMAND @item QUERY_CACHE_TYPE = 0 | 1 | 2 Set query cache setting for this thread. @multitable @columnfractions .20 .70 @item @strong{Option} @tab @strong{Description} @item 0 or OFF @tab Don't cache or retrieve results. @item 1 or ON @tab Cache all results except @code{SELECT SQL_NO_CACHE ...} queries. @item 2 or DEMAND @tab Cache only @code{SELECT SQL_CACHE ...} queries. @end multitable @item SQL_SAFE_UPDATES = 0 | 1 @code{1} に設定すると、@code{WHERE} 節内でキーや @code{LIMIT} を使用しない で @code{UPDATE} または @code{DELETE} を行なおうとした場合に MySQL がアボートします。これは、手で SQL コマンドを生成する時の間 違った更新の捕捉を可能にします。 @item SQL_SELECT_LIMIT = value | DEFAULT @code{SELECT} 構文から返されるレコードの最大値。 もし @code{SELECT} に @code{LIMIT} 節を使用している場合、@code{LIMIT} は @code{SQL_SELECT_LIMIT} の値より優先されます。 新しい接続におけるこの値の標準値は ``unlimited''. もしリミットを変えているならば、@code{SQL_SELECT_LIMIT} に @code{DEFAULT} を指定することにより、標準値に戻すことができます。 @item SQL_LOG_OFF = 0 | 1 この値が @code{1} の場合、もしクライアントが @code{SUPER} 権限 (version4.0.2以上。それ未満では @code{PROCESS}権限) を持っているならば、 このクライアントのログが行われません。 これは更新ログに影響しません！ @item SQL_LOG_UPDATE = 0 | 1 @code{0} の場合、もしクライアントが @code{SUPER} 権限 (version4.0.2以上。それ未満では @code{PROCESS}権限) を持っているならば、 このクライアントの更新ログの記録は行われません。 これは通常のログには影響しません！ @item SQL_QUOTE_SHOW_CREATE = 0 | 1 If set to @code{1}, @code{SHOW CREATE TABLE} will quote table and column names. This is @strong{on} by default, for replication of tables with fancy column names to work. @ref{SHOW CREATE TABLE, , @code{SHOW CREATE TABLE}}. @item TIMESTAMP = timestamp_value | DEFAULT クライアントに時間を設定します。 もしレコードのリストアに更新ログを使用する場合、オリジナルのタイムスタンプを得る ために使用します。 @code{timestamp_value} should be a UNIX Epoch timestamp, not a MySQL timestamp. @item LAST_INSERT_ID = # @code{LAST_INSERT_ID()} からの返り値を設定します。 テーブルを更新するコマンド中に @code{LAST_INSERT_ID()} を使用した場合、 これは更新ログに保存されます。 @item INSERT_ID = # @code{AUTO_INCREMENT} 値を挿入する時、 @code{INSERT} , @code{ALTER TABLE} コマンドに従って使用される値をセットします。 これは更新ログによって使用されます。 @end table @node Disk issues, , Optimizing the Server, MySQL Optimisation @section Disk の問題 @cindex disk issues @cindex performance, disk issues @itemize @bullet @item 前に述べたディスクシークが大きなボトルネックです。 この問題は、データが効果的に キャッシングが不可能になるほど、大きくなり始めるときに、だんだん明白になってきま す。 For large databases, where you access data more or less randomly, you can be sure that you will need at least one disk seek to read and a couple of disk seeks to write things. この問題を少なくするには、diskシーク時間の少ないディスクを 使用します。 @item 利用できるディスクスピンドルの数を増やします(それによってディスクシーク のオーバーヘッドは縮小します)。 これは違うディスクにシンボリックリンクをはったり、ストライピングを行うことで 可能です。 @table @strong @item Using symbolic links これは通常のデータディレクトリから、違うディスクへ、 インデックスやデータファイルをシンボリック・リンクすることです。 これは シーク と リード を速くします。 (もしそのディスクが 他に使用されていなければ). @xref{Symbolic links}. @cindex striping, defined @item Striping ストライピングは、複数のディスクに対して、まずデータの最初のブロックを 1番目の disk に書き、2番目のブロックを2つ目のdiskに書き、順次 N 番目 (N は disk の数) まで順に書いていきます。 これは、もしデータがストライプの サイズよりも小さければ、よりよいパフォーマンスを得ることが出来ます。 ストライピングは、OS や ストライプのサイズにとても依存していることに注意してくだ さい。そのため、あなたのアプリケーションのベンチマークがストライプサイズによって 変わるでしょう。 @xref{Custom Benchmarks}. ストライピングのスピードの違いは、@strong{とても} パラメターに依存しています。 Depending on how you set the striping parameters and number of disks you may get a difference in orders of magnitude. Note that you have to choose to optimize for random or sequential access. @end table @item 信頼性のため、あなたは RAID 0+1 (striping + mirroring) を使用したいと 思うかもしれません。 しかしこれは N 個のドライブのデータを収めるのに 2*N 個のドライブが必要となります。 これはもし資金があるならば一番よい方法でしょう！ しかし、能率的にそれを 取り扱うために、ボリューム・マネージメント・ソフトウェアに投資する必要が あってもよいです。 @item A good option is to have semi-important data (that can be regenerated) on RAID 0 disk while storing really important data (like host information and logs) on a RAID 0+1 or RAID N disk. RAID N can be a problem if you have many writes because of the time to update the parity bits. @item データベースに使用しているファイルシステムの mount パラメターを変更しても 良いでしょう。 一つの簡単な方法としては、noatime オプションでファイルシステムを マウントします。 これは inode にある最後にアクセスした時間の更新を スキップします。 これでいくらか ディスクシークを避けることができるでしょう。 @item On Linux, you can get much more performance (up to 100% under load is not uncommon) by using @code{hdparm} to configure your disk's interface! The following should be quite good @code{hdparm} options for MySQL (and probably many other applications): @example hdparm -m 16 -d 1 @end example Note that the performance/reliability when using the above depends on your hardware, so we strongly suggest that you test your system thoroughly after using @code{hdparm}! Please consult the @code{hdparm} man page for more information! If @code{hdparm} is not used wisely, filesystem corruption may result. Backup everything before experimenting! @item On many operating systems you can mount the disks with the @code{-o async} option to set the filesystem to be updated asynchronously. If your computer is reasonably stable, this should give you more performance without sacrificing too much reliability. (This flag is on by default on Linux.) @item If you don't need to know when a file was last accessed (which is not really useful on a database server), you can mount your filesystems with the @code{-o noatime} option. @end itemize @menu * Symbolic links:: Using Symbolic Links @end menu @node Symbolic links, , Disk issues, Disk issues @subsection シンボリックリンクの使用 @cindex symbolic links @cindex links, symbolic テーブルとデータベースのファイルを MySQL のデータベースディレクトリーから 違う場所に移動し、 それに対してシンボリックリンクを張ることができます。例 えば、もっと空き容量のあるファイルシステムへデータベースを移すため、あるい はテーブルを異なるディスクに広げることでシステムのスピードを増加するために これを行ないたくなるでしょう。 The recommended way to do this, is to just symlink databases to a different disk and only symlink tables as a last resort. @menu * Symbolic links to databases:: Using Symbolic Links for Databases * Symbolic links to tables:: Using Symbolic Links for Tables @end menu @node Symbolic links to databases, Symbolic links to tables, Symbolic links, Symbolic links @subsubsection Using Symbolic Links for Databases @cindex databases, symbolic links The way to symlink a database is to first create a directory on some disk where you have free space and then create a symlink to it from the MySQL database directory. @example shell> mkdir /dr1/databases/test shell> ln -s /dr1/databases/test mysqld-datadir @end example MySQL は一つのディレクトリを複数のデータベースにリンクすることは サポートしていません。シンボリックリンクを持つデータベースディレクトリの複 製は、データベース間のシンボリックリンクを作成しなければ、正常に動作します。 MySQL データディレクトリに @code{db1} データベースがあるとして、 @code{db1} を指すシンボリックリンク @code{db2} を作成します。 @example shell> cd /path/to/datadir shell> ln -s db1 db2 @end example すると、@code{db1} 中の @code{tbl_a} テーブルは @code{db2} の @code{tbl_a} テー ブルとして見えます。 もしあるスレッドが @code{db1.tbl_a} を更新し、他のスレッドが @code{db2.tbl_a} を 更新した場合、 問題が発生します。 こういった使用をどうしてもしたい場合、@file{mysys/mf_format.c} を以下のように変 更します: @example if (flag & 32 || (!lstat(to,&stat_buff) && S_ISLNK(stat_buff.st_mode))) @end example to @example if (1) @end example On Windows you can use internal symbolic links to directories by compiling MySQL with @code{-DUSE_SYMDIR}. This allows you to put different databases on different disks. @xref{Windows symbolic links}. @node Symbolic links to tables, , Symbolic links to databases, Symbolic links @subsubsection Using Symbolic Links for Tables @cindex tables, symbolic links Before MySQL 4.0 you should not symlink tables, if you are not very careful with them. The problem is that if you run @code{ALTER TABLE}, @code{REPAIR TABLE} or @code{OPTIMIZE TABLE} on a symlinked table, the symlinks will be removed and replaced by the original files. This happens because the above command works by creating a temporary file in the database directory and when the command is complete, replace the original file with the temporary file. You should not symlink tables on systems that don't have a fully working @code{realpath()} call. (At least Linux and Solaris support @code{realpath()}) In MySQL 4.0 symlinks are fully supported only for @code{MyISAM} tables. For other table types you will probably get strange problems when doing any of the above mentioned commands. The handling of symbolic links in MySQL 4.0 works the following way (this is mostly relevant only for @code{MyISAM} tables). @itemize @bullet @item In the data directory you will always have the table definition file and the data and index files. @item You can symlink the index file and the data file to different directories independently of the other. @item The symlinking can be done from the operating system (if @code{mysqld} is not running) or with the @code{INDEX/DATA DIRECTORY="path-to-dir"} command in @code{CREATE TABLE}. @xref{CREATE TABLE}. @item @code{myisamchk} will not replace a symlink with the data or index file but work directly on the file the symlink points to. Any temporary files will be created in the same directory where the data or index file is located. @item When you drop a table that is using symlinks, both the symlink and the file the symlink points to are dropped. This is a good reason to why you should @strong{not} run @code{mysqld} as @code{root} or allow persons to have write access to the MySQL database directories. @item If you rename a table with @code{ALTER TABLE RENAME} and you don't move the table to another database, the symlinks in the database directory will be renamed to the new names and the data and index files will be renamed accordingly. @item If you use @code{ALTER TABLE RENAME} to move a table to another database, the table will be moved to the other database directory and the old symlinks and the files they pointed to will be deleted. (In other words, the new table will not be symlinked.) @item If you are not using symlinks, you should use the @code{--skip-symlink} option to @code{mysqld} to ensure that no one can drop or rename a file outside of the @code{mysqld} data directory. @end itemize Things that are not yet supported: @cindex TODO, symlinks @itemize @bullet @item @code{ALTER TABLE} ignores all @code{INDEX/DATA DIRECTORY="path"} options. @item @code{CREATE TABLE} doesn't report if the table has symbolic links. @item @code{mysqldump} doesn't include the symbolic link information in the output. @item @code{BACKUP TABLE} and @code{RESTORE TABLE} don't respect symbolic links. @end itemize @node Reference, Table types, MySQL Optimization, Top @chapter MySQL Language Reference MySQL has a very complex, but intuitive and easy to learn SQL interface. This chapter describes the various commands, types, and functions you will need to know in order to use MySQL efficiently and effectively. This chapter also serves as a reference to all functionality included in MySQL. In order to use this chapter effectively, you may find it useful to refer to the various indexes. @menu * Language Structure:: Language Structure * Column types:: Column types * Functions:: Functions * Data Manipulation:: Data Manipulation: @code{SELECT}, @code{INSERT}, @code{UPDATE}, @code{DELETE} * Data Definition:: Data Definition: @code{CREATE}, @code{DROP}, @code{ALTER} * Basic User Commands:: Basic MySQL User Utility Commands * Transactional Commands:: MySQL Transactional and Locking Commands * Fulltext Search:: MySQL Full-text Search * Query Cache:: MySQL Query Cache @end menu @node Language Structure, Column types, Reference, Reference @section Language Structure @menu * Literals:: Literals: How to Write Strings and Numbers * Legal names:: Database, Table, Index, Column, and Alias Names * Name case sensitivity:: Case-Sensitivity in Names * Variables:: User Variables * System Variables:: System Variables * Comments:: Comment Syntax * Reserved words:: Is MySQL Picky About Reserved Words? @end menu @node Literals, Legal names, Language Structure, Language Structure @subsection 文字列と数値をどのように書くか？ @cindex strings, defined @cindex strings, escaping characters @cindex literals @cindex escape characters @cindex backslash, escape character @menu * String syntax:: Strings * Number syntax:: Numbers * Hexadecimal values:: Hexadecimal values * NULL values:: @code{NULL} values @end menu この節は MySQL で文字列と数値を記述するさまざまな方法を説明します。 MySQL でのこれらの基本型の取り扱い時に、出会うであろうさまざまな ニュアンスと ``了解'' もカバーします。 @node String syntax, Number syntax, Literals, Literals @subsubsection 文字列 文字列は文字の並びです。引用符(@samp{'})または二重引用符(@samp{"})で括ら れます(後者は ANSI モードで実行していない場合のみ)。 例： @example 'a string' "another string" @end example 文字列中では、いくつかのシーケンスは特別な意味を持ちます。これらのシーケ ンスのそれぞれは@emph{エスケープ文字}として知られるバックスラッシュ (@samp{\})で始まります。MySQL は次のエスケープシーケンスを認識 します。 @c these aren't really functions, but that's probably the most reasonable index @table @code @findex \0 (ASCII 0) @findex NUL @item \0 ASCII 0 (@code{NUL}) 文字。 @findex \' (single quote) @findex single quote (\') @item \' 引用符(@samp{'})。 @findex \" (double quote) @findex double quote (\") @item \" 二重引用符(@samp{"})。 @findex \b (backspace) @findex backspace (\b) @item \b バックスペース文字。 @findex \n (newline) @findex newline (\n) @item \n 改行文字。 @findex \r (carriage return) @findex return (\r) @findex carriage return (\r) @item \r リターン文字。 @findex \t (tab) @findex tab (\t) @item \t タブ文字。 @findex \z (Control-Z) ASCII(26) @findex (Control-Z) \z @item \z ASCII(26) (Control-Z)。この文字は、ASCII(26) が Windows では END-OF-FILE であるという問題を回避するために、コード化できます。(ASCII(26) は @code{mysql database < filename} を使用しようとする場合に問題になります)。 @findex \\ (escape) @findex escape (\\) @item \\ バックスラッシュ(@samp{\})文字。 @findex % (wildcard character) @findex Wildcard character (%) @item \% @samp{%} 文字。これは @samp{%} がワイルドカード文字として解釈される文脈 で、@samp{%} そのものを検索するために使用されます。 @xref{String comparison functions}. @findex _ (wildcard character) @findex Wildcard character (_) @item \_ @code{_} 文字。これは @samp{_} がワイルドカード文字として解釈される文脈 で、@code{_} そのものを検索するために使用されます。 @xref{String comparison functions}. @end table いくつかの文字列文脈で @samp{\%} または @samp{\_} を使用すると、これらは文 字列 @samp{%} と @samp{_} ではなく、@samp{\%} と @samp{\_} を返します。 @cindex quotes, in strings @noindent 文字列中に引用符を含める方法はいくつかあります: @itemize @bullet @item @samp{'} で括られる文字列中の @samp{'} は @samp{''} として書くことができ ます。 @item @samp{"} で括られる文字列中の @samp{"} は @samp{""} として書くことができ ます。 @item 引用符の前にエスケープ文字 (@samp{\}) を置くことができます。 @item @samp{"} で括られた文字列中の @samp{'} は特別扱いの必要はなく、二重にし たり、エスケープする必要はありません。同じように、@samp{'} で括られた文 字列中の @samp{"} は特別扱いの必要はありません。 @end itemize 次の @code{SELECT} ステートメントは、クォートとエスケープがどのように働 くかを示します: @example mysql> SELECT 'hello', '"hello"', '""hello""', 'hel''lo', '\'hello'; +-------+---------+-----------+--------+--------+ | hello | "hello" | ""hello"" | hel'lo | 'hello | +-------+---------+-----------+--------+--------+ mysql> SELECT "hello", "'hello'", "''hello''", "hel""lo", "\"hello"; +-------+---------+-----------+--------+--------+ | hello | 'hello' | ''hello'' | hel"lo | "hello | +-------+---------+-----------+--------+--------+ mysql> SELECT "This\nIs\nFour\nlines"; +--------------------+ | This Is Four lines | +--------------------+ @end example @cindex quoting binary data バイナリデータを @code{BLOB} フィールドに挿入したい場合、次の文字をエスケープ シーケンスで表す必要があります: @table @code @item NUL ASCII 0。@samp{\0} (バックスラッシュと ASCII @samp{0} 文字) に置き換える べきです。 @item \ ASCII 92, バックスラッシュ。@samp{\\} と表記してください。 @item ' ASCII 39, 引用符。@samp{\'} と表記してください。 @item " ASCII 34, 二重引用符。@samp{\"} と表記してください。 @end table @cindex quoting @cindex @code{BLOB}, inserting binary data @findex mysql_real_escape_string() @findex DBI->quote C コードを書く場合、@code{INSERT} 節で文字をエスケープするために、C API 関数 @code{mysql_real_escape_string()} を使用できます。@xref{C API function overview}. Perl では、@code{DBI} パッケージの @code{quote} メソッドを使 用して、特殊文字を適当なエスケープシーケンスに変換できます。@xref{Perl DBI Class, , Perl @code{DBI} Class}. 上記の特殊文字のどれかを含む可能性のある全ての文字列について、エスケープ 関数を使用すべきです！ Alternatively, many MySQL APIs provide some sort of placeholder capability that allows you to insert special markers into a query string, and then bind data values to them when you issue the query. In this case, the API takes case of escaping special characters in the values for you automatically. @node Number syntax, Hexadecimal values, String syntax, Literals @subsubsection 数値 @cindex numbers @cindex valid numbers, examples @cindex integers @cindex floats @cindex negative values 整数は数字の並びで表現されます。 浮動小数点は @samp{.} で小数を分割します。 どちらの型も負数を表すために @samp{-} を前につけます。 正当な数値の例: @example 1221 0 -32 @end example 有効な浮動小数点の例： @example 294.42 -32032.6809e+10 148.00 @end example 整数が浮動小数点の文脈で使用されるかもしれません； この場合、浮動小数点に 変換されます。 @node Hexadecimal values, NULL values, Number syntax, Literals @subsubsection 16進法の値 @tindex hexadecimal values MySQL は16進法の値をサポートします。 数値の文脈では、これらは整数(64ビット精度)のように振る舞います。 文字列の文脈では、hexの桁のそれぞれのペアが文字に変換された バイナリー文字のように振る舞います。 @example mysql> SELECT x'4D7953514C'; -> MySQL mysql> SELECT 0xa+0; -> 10 mysql> select 0x5061756c; -> Paul @end example The @code{x'hexstring'} syntax (new in 4.0) is based on ANSI SQL and the @code{0x} syntax is based on ODBC. 16進数表記は、ODBC において BLOB の値を与えるためにしばしば使用されます。 You can convert a string or a number to hexadecimal with the @code{HEX()} function. @node NULL values, , Hexadecimal values, Literals @subsubsection @code{NULL} 値 @tindex NULL value @code{NULL} は ``no data'' を意味し、数値型の @code{0} や文字列型の空文 字列とは異なることに注意してください。 @xref{Problems with NULL, , Problems with @code{NULL}}. テキストファイルの読み込みや書き出し時に、@code{NULL} は @code{\N} で 表現されます。 (@code{LOAD DATA INFILE}, @code{SELECT ... INTO OUTFILE}). @xref{LOAD DATA, , @code{LOAD DATA}}. @node Legal names, Name case sensitivity, Literals, Language Structure @subsection データベース名、テーブル名、インデックス名、フィールド名、エイリアス名 @cindex names @cindex legal names @cindex databases, names @cindex tables, names @cindex indexes, names @cindex columns, names @cindex aliases, names データベース名、テーブル名、インデックス名、フィールド名、エイリアス名は MySQL では全て同じ規則に基づきます: @tindex identifiers, quoting @tindex quoting of identifiers @tindex ` @tindex " 注意: 規則は MySQL 3.23.6 で変更されました。それは識別子(データベー ス名、テーブル名、フィールド名)の @samp{`} でのクォートを導入した時です (ANSI モードで実行する場合は、@code{"} も識別子をクォートするために働きま す)。 @multitable @columnfractions .15 .15 .70 @item @strong{識別子} @tab @strong{最大長} @tab @strong{許される文字} @item データベース @tab 64 @tab ディレクトリ名として許されるすべての文字。@code{/}, @samp{\}, @samp{.} を除く。 @item テーブル @tab 64 @tab ファイル名として許されるすべての文字。@code{/} と @code{.} を除く。 @item フィールド @tab 64 @tab すべての文字 @item エイリアス @tab 255 @tab すべての文字 @end multitable 注意: 上記に加え、識別子内には ASCII(0) と ASCII(255) を持てません。 注意: 識別子が制限された単語であったり特殊文字を含む場合は、それを使用する 時には常に @code{`} (バッククォート) でクォートする必要があります: @example mysql> SELECT * FROM `select` WHERE `select`.id > 100; @end example @xref{Reserved words}. MySQL 3.23.6 より前のバージョンでは、名前の規則は次に従います: @itemize @bullet @item 名前は、現在の文字セットのアルファベットと数字文字から成り、@samp{_} と @samp{$} も含みます。デフォルト文字セットは ISO-8859-1 Latin1 ですが、 これは @code{mysqld} に @code{--default-character-set} オプションを 与えることで変更できます. (3.23.14 以上の場合のみ。 それ以前のバージョンでは MySQL 再コンパイルが必要) @xref{Character sets}. @item 名前は、名前として正しい任意の文字で始めることができます。特に、名前は数 字で始めることができます(これは他の多くのシステムと異なります！)。しかし、 数字@emph{だけ}の名前にする事はできません。 @item 名前の中に @samp{.} 文字を使用することはできません。フィールドを参照できるよう に形式を拡張するために使用されるためです(後述)。 @end itemize @code{1e} のような名前は使用しないことを勧めます。@code{1e+1} のような式が あいまいだからです。これは、式 @code{1e + 1} として、または数値 @code{1e+1} として解釈されます。 MySQL では次の形式のいずれかを使用してフィールドを参照できます: @multitable @columnfractions .30 .70 @item @strong{フィールドの参照方法} @tab @strong{意味} @item @code{col_name} @tab クエリ中で使用されるテーブル内に存在している @code{col_name} という名前のフィールド @item @code{tbl_name.col_name} @tab 現在のデータベースのテーブル @code{tbl_name} 内のフィールド @code{col_name} @item @code{db_name.tbl_name.col_name} @tab データベース @code{db_name} のテーブル @code{tbl_name} 内のフィールド @code{col_name}。この形式は バージョン 3.22 以降で有効です。 @item @code{`column_name`} @tab キーワードであったり特殊文字を含むフィールド。 @end multitable 参照が曖昧でないならば、ステートメント中のフィールド参照の前に @code{tbl_name} または @code{db_name.tbl_name} を記述する必要はありません。例えば、テー ブル @code{t1} と @code{t2} がそれぞれフィールド @code{c} を含み、@code{t1} と @code{t2} の両方を使用する @code{SELECT} ステートメントで @code{c} を取 り出すとします。この場合、@code{c} はステートメントで使用されるテーブル 間で唯一でないので曖昧です。そのため、@code{t1.c} または @code{t2.c} と 記述するこよによりどちらのテーブルを意味するかを示す必要があります。同様 に、データベース @code{db1} のテーブル @code{t} とデータベース @code{db2} のテーブル @code{t} から取り出す場合、これらのテーブル中の項 目は、@code{db1.t.col_name} と @code{db2.t.col_name} として参照する必要 があります。 @cindex ODBC compatibility @cindex compatibility, with ODBC 構文 @code{.tbl_name} は現在のデータベース内のテーブル @code{tbl_name} を意味します。この構文はいくつかの ODBC が @samp{.} 文字をテーブル名の前 に置くために許されています。 @node Name case sensitivity, Variables, Legal names, Language Structure @subsection 名前のケース依存性 @cindex names, case-sensitivity @cindex case-sensitivity, in names @cindex database names, case-sensitivity @cindex table names, case-sensitivity @cindex column names, case-sensitivity @cindex alias names, case-sensitivity MySQL では、データベースとテーブルは、ディレクトリと そのディレクトリ中のファイルに対応します。そのため、下で動作するオペレー ティングシステムのケース依存性は、データベースとテーブル名のケース依存性を決定します。 データベース名とテーブル名は UNIX ではケース依存で、Windows ではケース非依 存です。One prominent exception here is Mac OS X, when the default HFS+ file system is being used. However Mac OS X also supports UFS volumes, those are case sensitive on Mac OS X just like they are on any Unix. @xref{Extensions to ANSI}. @strong{注意}: Windows ではデータベース名とファイル名はケース非依存ですが、 同じクエリ内で、データベースやテーブルを異なるケースを使用して参照すべき ではありません。 以下のクエリは動きません。なぜなら @code{my_table} と @code{MY_TABLE} の両方を 参照しているからです： @example mysql> SELECT * FROM my_table WHERE MY_TABLE.col=1; @end example フィールド名とフィールドの別名は全ての場合でケース非依存です。 テーブルの別名はケース依存です。 以下のクエリは動きません。なぜなら @code{a} と @code{A} のエイリアスを両方 参照しているからです： @example mysql> SELECT col_name FROM tbl_name AS a -> WHERE a.col_name = 1 OR A.col_name = 2; @end example テーブル名に使用されたケースを覚えておくことに問題があるなら、常にデータベー スとテーブルに小文字の名前をつけるというような、一貫した慣習を採用してくだ さい。 この問題を回避する一つの方法は、@code{mysqld} を @code{-O lower_case_table_names=1} をつけて起動することです。デフォルトではこのオプ ションは Windows では 1 で UNIX では 0 です。 @code{lower_case_table_names} が 1 の場合、MySQL はディスク上のす べてのテーブル名を小文字に変換して検索します。 (From version 4.0.2, this option also applies to database names.) 注意: このオプションを変更し た場合、@code{mysqld} を起動する前に、最初に古いテーブル名を小文字に変換す ることが必要です。 If you move @code{MyISAM} files from a Windows to a Unix disk, you may in some cases need to use the @file{mysql_fix_extensions} tool to fix-up the case of the file extensions in each specified database directory (lowercase @file{.frm}, uppercase @file{.MYI} and @file{.MYD}). @file{mysql_fix_extensions} can be found in the @file{scripts} subdirectory. @node Variables, System Variables, Name case sensitivity, Language Structure @subsection ユーザー変数 @cindex variables, user @cindex user variables @cindex names, variables MySQL は、@code{@@variablename} 構文で接続固有の変数をサポー トします。変数名は現在の文字セットのアルファベットと数字、それに @samp{_}、@samp{$}、@samp{.} 文字からなります。デフォルト文字セットは ISO-8859-1 Latin1 です。 これは @code{mysqld} に @code{--default-character-set} オプションを 与えることで変更できます. (3.23.14 以上の場合のみ。 それ以前のバージョンでは MySQL 再コンパイルが必要) @xref{Character sets}. 変数は初期化する必要はありません。デフォルトでは @code{NULL} であり、整数 値、実数値、文字列値を格納できます。すべてのスレッド変数は、スレッドが終了 すると自動的に解放されます。 @code{SET} 構文で変数を設定できます: @example SET @@variable= @{ integer expression | real expression | string expression @} [,@@variable= ...]. @end example @code{SET} 構文で、式中で変数を設定することも可能です。 However, in this case the assignment operator is @code{:=} rather than @code{=}, because @code{=} is reserved for comparisons in non-@code{SET} statements: @example mysql> SELECT @@t1:=(@@t2:=1)+@@t3:=4,@@t1,@@t2,@@t3; +----------------------+------+------+------+ | @@t1:=(@@t2:=1)+@@t3:=4 | @@t1 | @@t2 | @@t3 | +----------------------+------+------+------+ | 5 | 5 | 1 | 4 | +----------------------+------+------+------+ @end example (我々は @code{:=} 構文を使用する必要がありました。@code{=} は比較のために 予約されていたからです。) ユーザー変数は式が許される場所で使用できます。注意: これは現在、 @code{SELECT} ステートメントの @code{LIMIT} 節、@code{LOAD DATA} ステート メントの @code{IGNORE number LINES} 節のように、数値が明示的に要求される文 脈での使用を含みません。 @strong{注意}: @code{SELECT} ステートメントでは、それぞれの式はクライアン トに送られた時にだけ評価されます。これは、@code{SELECT} 部で設定された変数 を必要とする式を参照する @code{HAVING}, @code{GROUP BY}, @code{ORDER BY} 節ができないことを意味します。例えば、次のステートメントは期待通りには動作 しません: @example mysql> SELECT (@@aa:=id) AS a, (@@aa+3) AS b FROM table_name HAVING b=5; @end example この理由は、@code{@@aa} が現在のレコードの値ではなく、前に受け取ったレコー ドの @code{id} の値になるからです。 The rule is to never assign @strong{and} use the same variable in the same statement. @node System Variables, Comments, Variables, Language Structure @subsection System Variables @cindex variables, System @cindex system variables Starting from MySQL 4.0.3 we provide better access to a lot of system and connection variables. One can change most of them without having to take down the server. There are two kind of system variables: Thread-specific (or connection-specific) variables that are unique to the current connection and global variables that are used to configure global events. Global variables also are used to set up the initial values of the corresponding thread-specific variables for new connections. When @code{mysqld} starts, all global variables are initialised from command line arguments and option files. You can change the value with the @code{SET GLOBAL} command. When a new thread is created, the thread-specific variables are initialised from the global variables and they will not change even if you issue a new @code{SET GLOBAL} command. To set the value for a @code{GLOBAL} variable, you should use one of the following syntaxes: (Here we use @code{sort_buffer_size} as an example variable) @example SET GLOBAL sort_buffer_size=value; SET @@@@global.sort_buffer_size=value; @end example To set the value for a @code{SESSION} variable, you can use one of the following syntaxes: @example SET SESSION sort_buffer_size=value; SET @@@@session.sort_buffer_size=value; SET sort_buffer_size=value; @end example If you don't specify @code{GLOBAL} or @code{SESSION} then @code{SESSION} is used. @xref{SET OPTION}. @code{LOCAL} is a synonym for @code{SESSION}. To retrieve the value for a @code{GLOBAL} variable you can use one of the following commands: @example SELECT @@@@global.sort_buffer_size; SHOW GLOBAL VARIABLES like 'sort_buffer_size'; @end example To retrieve the value for a @code{SESSION} variable you can use one of the following commands: @example SELECT @@@@session.sort_buffer_size; SHOW SESSION VARIABLES like 'sort_buffer_size'; @end example When you @strong{retrieve} a variable value with the @code{@@@@variable_name} syntax and you don't specify @code{GLOBAL} or @code{SESSION} then MySQL will return the thread-specific (@code{SESSION}) value if it exists. If not, MySQL will return the global value. The reason for requiring @code{GLOBAL} for setting @code{GLOBAL} only variables but not for retrieving them is to ensure that we don't later run into problems if we later would introduce a thread-specific variable with the same name or remove a thread-specific variable. In this case, you could accidentally change the state for the server as a whole, rather than just for your own connection. The following is a full list of all variables that you change and retrieve and if you can use @code{GLOBAL} or @code{SESSION} with them. @multitable @columnfractions .50 .25 .25 @item @strong{Variable name} @tab @strong{Value type} @tab @strong{Type} @item autocommit @tab bool @tab SESSION @item big_tables @tab bool @tab SESSION @item binlog_cache_size @tab num @tab GLOBAL @item bulk_insert_buffer_size @tab num @tab GLOBAL | SESSION @item concurrent_insert @tab bool @tab GLOBAL @item connect_timeout @tab num @tab GLOBAL @item convert_character_set @tab string @tab SESSION @item delay_key_write @tab OFF | ON | ALL @tab GLOBAL @item delayed_insert_limit @tab num @tab GLOBAL @item delayed_insert_timeout @tab num @tab GLOBAL @item delayed_queue_size @tab num @tab GLOBAL @item error_count @tab num @tab LOCAL @item flush @tab bool @tab GLOBAL @item flush_time @tab num @tab GLOBAL @item foreign_key_checks @tab bool @tab SESSION @item identity @tab num @tab SESSION @item insert_id @tab bool @tab SESSION @item interactive_timeout @tab num @tab GLOBAL | SESSION @item join_buffer_size @tab num @tab GLOBAL | SESSION @item key_buffer_size @tab num @tab GLOBAL @item last_insert_id @tab bool @tab SESSION @item local_infile @tab bool @tab GLOBAL @item log_warnings @tab bool @tab GLOBAL @item long_query_time @tab num @tab GLOBAL | SESSION @item low_priority_updates @tab bool @tab GLOBAL | SESSION @item max_allowed_packet @tab num @tab GLOBAL | SESSION @item max_binlog_cache_size @tab num @tab GLOBAL @item max_binlog_size @tab num @tab GLOBAL @item max_connect_errors @tab num @tab GLOBAL @item max_connections @tab num @tab GLOBAL @item max_error_count @tab num @tab GLOBAL | SESSION @item max_delayed_threads @tab num @tab GLOBAL @item max_heap_table_size @tab num @tab GLOBAL | SESSION @item max_join_size @tab num @tab GLOBAL | SESSION @item max_sort_length @tab num @tab GLOBAL | SESSION @item max_tmp_tables @tab num @tab GLOBAL @item max_user_connections @tab num @tab GLOBAL @item max_write_lock_count @tab num @tab GLOBAL @item myisam_max_extra_sort_file_size @tab num @tab GLOBAL | SESSION @item myisam_max_sort_file_size @tab num @tab GLOBAL | SESSION @item myisam_sort_buffer_size @tab num @tab GLOBAL | SESSION @item net_buffer_length @tab num @tab GLOBAL | SESSION @item net_read_timeout @tab num @tab GLOBAL | SESSION @item net_retry_count @tab num @tab GLOBAL | SESSION @item net_write_timeout @tab num @tab GLOBAL | SESSION @item query_cache_limit @tab num @tab GLOBAL @item query_cache_size @tab num @tab GLOBAL @item query_cache_type @tab enum @tab GLOBAL @item read_buffer_size @tab num @tab GLOBAL | SESSION @item read_rnd_buffer_size @tab num @tab GLOBAL | SESSION @item rpl_recovery_rank @tab num @tab GLOBAL @item safe_show_database @tab bool @tab GLOBAL @item server_id @tab num @tab GLOBAL @item slave_compressed_protocol @tab bool @tab GLOBAL @item slave_net_timeout @tab num @tab GLOBAL @item slow_launch_time @tab num @tab GLOBAL @item sort_buffer_size @tab num @tab GLOBAL | SESSION @item sql_auto_is_null @tab bool @tab SESSION @item sql_big_selects @tab bool @tab SESSION @item sql_big_tables @tab bool @tab SESSION @item sql_buffer_result @tab bool @tab SESSION @item sql_log_binlog @tab bool @tab SESSION @item sql_log_off @tab bool @tab SESSION @item sql_log_update @tab bool @tab SESSION @item sql_low_priority_updates @tab bool @tab GLOBAL | SESSION @item sql_max_join_size @tab num @tab GLOBAL | SESSION @item sql_quote_show_create @tab bool @tab SESSION @item sql_safe_updates @tab bool @tab SESSION @item sql_select_limit @tab bool @tab SESSION @item sql_slave_skip_counter @tab num @tab GLOBAL @item sql_warnings @tab bool @tab SESSION @item table_cache @tab num @tab GLOBAL @item table_type @tab enum @tab GLOBAL | SESSION @item thread_cache_size @tab num @tab GLOBAL @item timestamp @tab bool @tab SESSION @item tmp_table_size @tab enum @tab GLOBAL | SESSION @item tx_isolation @tab enum @tab GLOBAL | SESSION @item version @tab string @tab GLOBAL @item wait_timeout @tab num @tab GLOBAL | SESSION @item warning_count @tab num @tab LOCAL @item unique_checks @tab bool @tab SESSION @end multitable Variables that are marked with @code{num} can be given a numerical value. Variables that are marked with @code{bool} can be set to 0, 1, @code{ON} or @code{OFF}. Variables that are of type @code{enum} should normally be set to one of the available values for the variable, but can also be set to the number that correspond to the enum value. (The first enum value is 0). Here is a description of some of the variables: @multitable @columnfractions 0.30 0.70 @item @strong{Variable} @tab @strong{Description} @item identity @tab Alias for last_insert_id (Sybase compatiblity) @item sql_low_priority_updates @tab Alias for low_priority_updates @item sql_max_join_size @tab Alias for max_join_size @item delay_key_write_for_all_tables @tab If this and delay_key_write are set, then all new MyISAM tables that are opened will use delayed key writes. @item version @tab Alias for VERSION() (Sybase (?) compatability) @end multitable A description of the other variable definitions can be found in the startup options section, the description of @code{SHOW VARIABLES} and in the @code{SET} section. @xref{Command-line options}. @xref{SHOW VARIABLES}. @xref{SET OPTION}. @node Comments, Reserved words, System Variables, Language Structure @subsection コメント 構文 @findex Comment syntax @cindex comments, adding MySQL は @code{# 行末まで} , @code{-- 行末まで} そして @code{/* 行中または複数行 */} コメント書式をサポートします: @example mysql> SELECT 1+1; # このコメントは行末まで続く mysql> SELECT 1+1; -- このコメントは行末まで続く mysql> SELECT 1 /* これは行中コメント */ + 1; mysql> SELECT 1+ /* これは 複数行コメント */ 1; @end example @code{--} コメントスタイルは @code{--} の後ろに最低一つのスペースが 必要であることに注意！ サーバーはコメント構文を理解しますが、 @code{mysql} クライアントが @code{/* ... */} コメントを分析するにはいくつか制限があります： @itemize @bullet @item シングルクウォートとダブルクオート文字は引用文字列のトークンの開始を 示します。たとえコメントの中であっても。 もしコメントの中でクオートが二つ目のクオートにマッチしなかった場合、 パーサーはコメントが終了していないと認識します。 @code{mysql} を対話モードで実行している場合、 プロンプトが @code{mysql>} から @code{'>} か @code{">} に変わります。 @item セミコロンは SQL 構文の終了を示し、これに続く文字は次の構文の開始と なります。 @end itemize これらの制限は @code{mysql} を対話モードで実行している場合と、 @code{mysql} にファイルを読み込ませている場合 ( @code{mysql < some-file} ) の 両方で現れます。 MySQL は ANSI SQL コメントの @samp{--} をサポートしません。 @xref{ANSI diff comments}. @node Reserved words, , Comments, Language Structure @subsection Is MySQL Picky About Reserved Words? @cindex keywords @cindex reserved words, exceptions 共通の問題は、フィールドの名前を、 @code{TIMESTAMP} とか @code{GROUP} とかの MySQL に埋め込まれているデータ型や関数名と同名にして、 テーブルを作った場合に起こります。 このようなことは行えます(例えば @code{ABS} はフィールド名にできます)。 しかし、関数として使用する場合、 この名前がフィールド名として使用されているなら、 関数名と @samp{(} の間の空白は許されません。 以下の語は MySQL に予約されています。 これらのほとんどは、 ANSI SQL92 によって、 テーブル、フィールド名としての使用は禁止されています。(例えば @code{GROUP})。 またいくつかの語は MySQL が必要とし、 @code{yacc} パーサーで 使用しているので予約されています。 @include reservedwords.texi The following symbols (from the table above) are disallowed by ANSI SQL but allowed by MySQL as column/table names. This is because some of these names are very natural names and a lot of people have already used them. @itemize @bullet @item @code{ACTION} @item @code{BIT} @item @code{DATE} @item @code{ENUM} @item @code{NO} @item @code{TEXT} @item @code{TIME} @item @code{TIMESTAMP} @end itemize @node Column types, Functions, Language Structure, Reference @section フィールド型 @cindex columns, types @cindex types, columns MySQLは多くのフィールド型をサポートしており、それらは３つのカテゴリに グループ化されます: 数値型、日付及び時間型、そして文字列(文字)型。 この章ではまず、利用できる型の概要から始まり、それから各カテゴリの各フィールド 型の所要記憶容量の要約と、型の属性についてのより詳細な情報を提供します。 概要は意図的に簡潔にまとめています。値として指定できる書式のようなフィールド 型固有の付加情報は、詳細の説明部にて調べて下さい。 MySQLでサポートされるフィールド型は以下に示す通りです。 後に続く文字の意味は説明のために使われます: @cindex display size @cindex sizes, display @cindex digits @cindex decimal point @cindex brackets, square @cindex square brackets @table @code @item M 最大表示サイズを意味します。最大の表示桁数は 255. @item D 浮動小数点数型に適用され、小数点以下の桁数を表します。 最大の値は 30 ですが、これは @code{M}-2 より大きくなってはいけません。 @end table 中カッコ(@samp{[}及び@samp{]})は型定義の一部であり、それがオプションであることを 表します。 @tindex Types @c The @w{-number} stuff keeps a linebreak from occurring between @c the - and number. もしあるフィールドに @code{ZEROFILL} を指定した場合、 MySQL は自動で @code{UNSIGNED} 属性をそのフィールドに 追加します。 @strong{Warning}: you should be aware that when you use subtraction between integer values where one is of type @code{UNSIGNED}, the result will be unsigned! @xref{Cast Functions}. @table @code @tindex TINYINT @item TINYINT[(M)] [UNSIGNED] [ZEROFILL] とても小さい整数。符号つきの範囲は @code{-128}〜@code{127}。符号なしの範囲は @code{0}〜@code{255}。 @tindex BOOL @tindex BIT @item BIT @itemx BOOL These are synonyms for @code{TINYINT(1)}. @tindex SMALLINT @item SMALLINT[(M)] [UNSIGNED] [ZEROFILL] 小さい整数。符号つきの範囲は @code{-32768}〜@code{32767}。 符号なしの範囲は @code{0}〜@code{65535}。 @tindex MEDIUMINT @item MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL] 中間の整数。符号ありの範囲は @code{-8388608}〜@code{8388607}。 符号なしの範囲は @code{0}〜@code{16777215} @tindex INT @item INT[(M)] [UNSIGNED] [ZEROFILL] 通常の整数。符号ありの範囲は @code{-2147483648}〜@code{2147483647}。符号なしの範 囲は @code{0}〜@code{4294967295} @tindex INTEGER @item INTEGER[(M)] [UNSIGNED] [ZEROFILL] これは、@code{INT}の同義語です。 @tindex BIGINT @item BIGINT[(M)] [UNSIGNED] [ZEROFILL] 大きい整数。 符号ありの範囲は @code{-9223372036854775808}〜@code{9223372036854775807}。 符号なしの範囲は @code{0}〜@code{18446744073709551615}。 @code{BIGINT} フィールドについて意識すべきことのいくつか: @itemize @bullet @item @cindex rounding errors 全ての演算は符合付き @code{BIGINT} または @code{DOUBLE} で行われるため、 符合無しの @code{9223372036854775807} (63 bits) よりも大きな整数を ビット関数以外で使用すべきではありません！ それを行なうと、結果の最後の桁のいくつかは不正になるでしょう @code{BIGINT} を @code{DOUBLE} に変換する時の丸めエラーのためです。 MySQL 4.0 can handle @code{BIGINT} in the following cases: @itemize @bullet @item Use integers to store big unsigned values in a @code{BIGINT} column. @item In @code{MIN(big_int_column)} and @code{MAX(big_int_column)}. @item When using operators (@code{+}, @code{-}, @code{*}, etc.) where both operands are integers. @end itemize @item 文字列として格納することで @code{BIGINT} フィールドの正確な整数値を常に格 納することができます。この場合、double 表現を介在しません。 @item @code{-}、@code{+}及び@code{*}は、両方の引数が@code{INTEGER}値の時、 @code{BIGINT}演算を使うことに注意して下さい！ これは、２つの大きな整数の かけ算を行なう(又は整数を返す関数の結果が大きな整数である)時、 結果が@code{9223372036854775807}よりも大きい場合に予期しない結果を 受け取ることがあるということを意味しています。 @end itemize @cindex floating-point number @tindex FLOAT @tindex FLOAT(precision) @item FLOAT(precision) [UNSIGNED] [ZEROFILL] 浮動小数点数。Version 4.0 未満では符号なしにはできません。単精度浮動小数点数では @code{precision} が @code{<=24} で、倍精度浮動小数点数では 25〜53 の間です。 これらの型は次で述べる@code{FLOAT}や@code{DOUBLE}型に似ています。 @code{FLOAT(X)}は、@code{FLOAT}及び@code{DOUBLE}型に一致する同じ範囲を持っていま すが、 表示サイズや小数点以下桁数が定義されません。 MySQL バージョン 3.23 では、これは正しい浮動小数点です。前の MySQL バージョンでは, @code{FLOAT(precision)} は常に小数部は2桁で した。 注意: @code{FLOAT} の使用は、MySQL での全ての演算が double 精度で行 なわれるため、いくつかの予期しない問題が起こり得ます。 @xref{No matching rows}. @cindex ODBC compatibility @cindex compatibility, with ODBC この構文は ODBC 互換です。 @tindex FLOAT @tindex FLOAT(M,D) @item FLOAT[(M,D)] [UNSIGNED] [ZEROFILL] 小さい浮動小数点数。Version 4.0 未満では符号なしにはできません。 範囲は @code{@w{-3.402823466E+38}}〜@code{@w{-1.175494351E-38}}、 @code{0}、 @code{@w{1.175494351E-38}}〜@code{3.402823466E+38}です。 Version 4.0 以上では、If @code{UNSIGNED} is specified, negative values are disallowed. @code{M} は表示幅で @code{D} は小数部桁数です。引数が無いか引数が24以下の @code{FLOAT} は単精度浮動小数点数を意味します。 @tindex DOUBLE @tindex FLOAT(precision) @item DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL] 通常の浮動小数点数。Version 4.0 未満では符号なしにはできません。 範囲は @code{@w{-1.7976931348623157E+308}}〜@code{@w{-2.2250738585072014E-308}} 、 @code{0}、@code{2.2250738585072014E-308}〜@code{1.7976931348623157E+308}です。 Version 4.0 以上では、If @code{UNSIGNED} is specified, negative values are disallowed. @code{M} は表示幅で @code{D} は小数部桁数です。引数が無いか @code{DOUBLE} か、 25 <= @code{X} <= 53 である @code{FLOAT(X)} は倍精度浮動小数点数を意味します。 @tindex DOUBLE PRECISION @tindex REAL @item DOUBLE PRECISION[(M,D)] [UNSIGNED] [ZEROFILL] @itemx REAL[(M,D)] [UNSIGNED] [ZEROFILL] これらは@code{DOUBLE}の同義語です。 @tindex DECIMAL @item DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL] パック無し浮動小数点数。Version 4.0 未満では符号なしにはできません。@code{CHAR}フィールドのように振 舞います。`パック無し'は、数値が文字列として格納されることを意味し、数値のそれぞ れの桁、小数点、及び負数での@samp{-}符号に１文字使用します。 @code{D}が0の時、値は小数点や小数部を持ちません。@code{DECIMAL}値の最大範囲は @code{DOUBLE}と同じですが、実際の範囲は@code{DECIMAL}フィールドに与えられた@code{M} 及び@code{D}の選択に強制されます。 Version 4.0 以上では、If @code{UNSIGNED} is specified, negative values are disallowed. @code{D} を省略した場合は 0 に設定されます。@code{M} を省略した場合は 10 に設定されます。 MySQL 3.22 以下では、 @code{M} 引数は符号や小数点を含みます。 @tindex DEC @tindex NUMERIC @item DEC[(M[,D])] [UNSIGNED] [ZEROFILL] @itemx NUMERIC[(M[,D])] [UNSIGNED] [ZEROFILL] @code{DECIMAL}と同じ。 @tindex DATE @item DATE 日付。サポートされる範囲は@code{'1000-01-01'}から@code{'9999-12-31'}まで。 MySQL は@code{'YYYY-MM-DD'}の書式で@code{DATE}値を表示しますが、@code{DATE} フィールドへの値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 @xref{DATETIME}. @tindex DATETIME @item DATETIME 日付と時刻の組み合わせ。サポートされる範囲は@code{'1000-01-01 00:00:00'}〜 @code{'9999-12-31 23:59:59'}です。MySQLは@code{DATETIME}値を @code{'YYYY-MM-DD HH:MM:SS'}という書式で表示しますが、@code{DATETIME}フィールド への値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 @xref{DATETIME}. @tindex TIMESTAMP @item TIMESTAMP[(M)] タイムスタンプ。範囲は@code{'1970-01-01 00:00:00'}〜@code{2037}年末までです。 MySQL は@code{TIMESTAMP}値を@code{YYYYMMDDHHMMSS}、@code{YYMMDDHHMMSS}、 @code{YYYYMMDD}又は@code{YYMMDD}という書式で表示し、それは@code{M}に@code{14}(もし くは誤ってそれ以上の値を指定した時)、@code{12}、@code{8}又は@code{6}のいずれが指 定されたかに依存します。しかしながら@code{TIMESTAMP}フィールドへの値の割当ては、 文字列もしくは数値のいずれかの使用が許されます。 @code{TIMESTAMP}フィールドは、最後に操作された時刻を自動的に設定するので、 @code{INSERT}や@code{UPDATE}操作の時刻を記録するのに役立ちます。 @code{NULL}値を与えることによっても、現在時刻を設定できます。 @xref{Date and time types}. @code{TIMESTAMP} は常に 4 バイトで格納されます。@code{M} 引数は @code{TIMESTAMP} フィールドがどのように表示されるかだけに影響します。 注意: X が 8 または 14 である @code{TIMESTAMP(X)} フィールドは数値として報 告されます。他の @code{TIMESTAMP(X)} フィールドは文字列として報告されます。 これは、これらの型を持ったテーブルを確実にダンプとリストアできるようにする ためです！ @xref{DATETIME, , @code{DATETIME}}. @tindex TIME @item TIME 時間。範囲は@code{'-838:59:59'}〜@code{'838:59:59'}です。 MySQL は@code{TIME}値を@code{'HH:MM:SS'}という書式で表示しますが、@code{TIME} フィールドへの値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 @xref{TIME, , @code{TIME}}. @tindex YEAR @item YEAR[(2|4)] 年。2桁または4桁形式(デフォルトは4桁)。許される値は、4桁形式では @code{1901}〜@code{2155}, @code{0000} で、2桁形式(70〜69)では 1970〜2069 です。MySQL は @code{YEAR} 値を @code{YYYY} 形式で表示しますが、 @code{YEAR} フィールドへの値の割り当ては文字列と数字のどちらでも使用できま す。(@code{YEAR} は MySQL バージョン 3.22 以上での新しい型です。) @xref{YEAR, , @code{YEAR}}. @tindex NATIONAL CHAR @tindex NCHAR @tindex CHAR @tindex CHARACTER @item [NATIONAL] CHAR(M) [BINARY] 固定長文字列で、格納時には必ず指定された長さまで右側に空白を埋めます。 @code{M}の範囲は 0 から 255 文字です。 (MySQL Version 3.23 までは 1 から 255 です。) 後続の空白は値の取り出し時に削除され ます。@code{BINARY} キーワードが与えられない場合、@code{CHAR} 値のソートと 比較は、デフォルト文字セットに従ってケース非依存の方法で行なわれます。 @code{NATIONAL CHAR} (短い形式は @code{NCHAR}) は、ANSI SQL で、CHAR フィー ルドがデフォルト文字セットを使用することを定義する方法です。これは MySQL ではデフォルトです。 @code{CHAR} は @code{CHARACTER} の略記です。 MySQL は @code{CHAR(0)} 型のフィールドの生成を許します。これは主 に、実際にはもう値が使われていないフィールドが存在することに依存しているよ うないくつかの古いアプリケーションに対応する必要がある時に便利です。２つの 値だけを取ることができるフィールドを必要とする時にもとても良いことです: @code{NOT NULL} として定義されていない @code{CHAR(0)} は1ビットだけを占有 し、２つの値だけを取ることができます: @code{NULL} または @code{""}。 @xref{CHAR, , @code{CHAR}}. @item CHAR This is a synonym for @code{CHAR(1)}. @tindex CHARACTER VARYING @tindex CHAR VARYING @tindex VARCHAR @item [NATIONAL] VARCHAR(M) [BINARY] 可変長文字列。 注意: 後続の空白は格納時に削除されます(これは ANSI SQL 仕様と異なります)。 @code{M}の範囲は 0 から 255 文字です。 (MySQL Version 4.0.2 未満では 1 から 255 です) @code{BINARY} キーワードが与えられない場合、ソートと比較はケースに依存しません。 @xref{Silent column changes}. @code{VARCHAR} は @code{CHARACTER VARYING} の略記です。 @xref{CHAR}. @tindex TINYBLOB @tindex TINYTEXT @item TINYBLOB @itemx TINYTEXT 最大長 255 (2^8 - 1) 文字の @code{TEXT}/@code{BLOB}。 @xref{Silent column changes}. @xref{BLOB}. @tindex BLOB @tindex TEXT @item BLOB @itemx TEXT 最大長 65535 (2^16 - 1) 文字の @code{TEXT}/@code{BLOB}。 @xref{Silent column changes}. @xref{BLOB}. @tindex MEDIUMBLOB @tindex MEDIUMTEXT @item MEDIUMBLOB @itemx MEDIUMTEXT 最大長 16777215 (2^24 - 1) 文字の @code{TEXT}/@code{BLOB}。 @xref{Silent column changes}. @xref{BLOB}. @tindex LONGBLOB @tindex LONGTEXT @item LONGBLOB @itemx LONGTEXT 最大長 4294967295 (2^32 - 1) 文字の @code{TEXT}/@code{BLOB}。 @xref{Silent column changes}。注意: サーバ／クライアントプロトコルと MyISAM テーブルは、通信パケット単位 / テーブルレコードで、現在 16M の制限 があるため、この型の範囲全体はまだ使用できません。@xref{BLOB}。 @tindex ENUM @item ENUM('value1','value2',...) 列挙。 対象となる文字列は、値を一つだけ持ち、値リスト@code{'value1', 'value2',...}(又は @code{NULL})から選ばれます。@code{ENUM}は最大65535個の固有値を持つことができます 。 @xref{ENUM}. @tindex SET @item SET('value1','value2',...) 組。 対象となる文字列は0以上の値を持ち、それぞれ値リスト@code{'value1', 'value2',...} から選ばれなければなりません。 @code{SET}は、最大 64個の要素を持つことができます。@xref{SET}. @end table @menu * Numeric types:: Numeric types * Date and time types:: Date and time types * String types:: String types * Choosing types:: Choosing the right type for a column * Other-vendor column types:: Using column types from other database engines * Storage requirements:: Column type storage requirements @end menu @node Numeric types, Date and time types, Column types, Column types @subsection 数値型 MySQL は ANSI/ISO SQL92 数値型をすべてサポートします。これらの型 は正確な数値データ型(@code{NUMERIC}, @code{DECIMAL}, @code{INTEGER}, @code{SMALLINT})、近似数値型(@code{FLOAT}, @code{REAL}, @code{DOUBLE PRECISION})を含みます。キーワード @code{INT} は @code{INTEGER} の同義語で、 @code{DEC}は @code{DECIMAL} の同義語です。 MySQL では @code{NUMERIC} と @code{DECIMAL} 型は、SQL92 標準で許 されているように同じ型として実装されています。これらは正確な精度を維持する ことが重要な値(例えば金銭データ)に使用されます。これらの型の一つのフィール ドを宣言する時、精度と大きさが指定できます(通常はそうします); 例えば: @example salary DECIMAL(5,2) @end example この例では、@code{5} (@code{precisoin}) は値を格納する重要な数値の桁数を表 します。そして @code{2} (@code{scale}) は小数点に続いて格納される桁数を表 します。従って、この場合 @code{salary} フィールドに格納することができる値 の範囲は、@code{-99.99} から @code{99.99} です。 (MySQL can actually store numbers up to @code{999.99} in this column because it doesn't have to store the sign for positive numbers) ANSI/ISO SQL92 では、構文 @code{DECIMAL(p)} は @code{DECIMAL(p,0)} と等しいです。同様に、 構文 @code{DECIMAL} は @code{DECIMAL(p,0)} と等しいです。ここで @code{p} の値の決定は実装に許されてます。@code{DECIMAL}/@code{NUMERIC} データ型のこ れらの異なる形式は、MySQL は現在サポートしていません。この型の主 な利益は精度と大きさの両方を明示的に制御する機能から引き出されるので、これ は通常深刻な問題ではありません。 @code{DECIMAL} と @code{NUMERIC} 値は、値の小数の精度を維持するため、バイ ナリ浮動小数点数としてではなく、文字列として格納されます。1文字は値のそれ ぞれの桁(@code{scale} > 0 の場合)と @samp{-} 記号(負数の場合)に使用されま す。@code{scale} が 0 の場合、@code{DECIMAL} と @code{NUMERIC} 値は小数点 と小数部を含みません。 @code{DECIMAL} と @code{NUMERIC} 値の最大範囲は @code{DOUBLE} と同じです。 しかし @code{DECIMAL} や @code{NUMERIC} フィールドに与えられる実際の範囲は フィールドに与えられた @code{precision} と @code{scale} によって強制されま す。このフィールドに、指定された @code{scale} で許されるよりも多い桁の小数 部を持つ数値が割り当てられた場合、値はその @code{scale} に丸められます。 @code{DECIMAL} や @code{NUMERIC} フィールドに、指定された(またはデフォルト の) @code{precision} と @code{scale} で示された範囲を超えた大きさの値を割 り当てた時、MySQL はその範囲の対応する最大値を表す値を格納します。 ANSI/ISO SQL92 標準に対する拡張として、上の表にリストしたように、 MySQL は整数型 @code{TINYINT}, @code{MEDIUMINT}, @code{BIGINT} も サポートします。MySQL によってサポートされる他の拡張として、オプ ションで、型の基本キーワードに続けて括弧内に指定する整数値の表示幅(例えば @code{INT(4)})があります。このオプションの幅指定は、フィールドに指定された 幅よりも少ない幅の値の表示の左側を埋めるために使用されます。しかしフィール ドに格納することができる値の範囲や、フィールドに指定された幅を超える幅の値 について表示される桁数は制約されません。オプションの拡張属性 @code{ZEROFILL} を指定して使用された場合、デフォルトの埋められる空白は 0 で置き換えられます。例えば、@code{INT(5) ZEROFILL} として宣言されたフィー ルドでは、値 @code{4} は @code{0004} として取り出されます。注意: 整数フィー ルド内に表示幅よりも大きい値を格納する場合、MySQL が複雑な join のために一時テーブルを生成する時に、問題を体験するでしょう。この場合 MySQL はデータがオリジナルのフィールド幅に合っていることを信用す るためです。 すべての整数型はオプションの(非標準)属性 @code{UNSIGNED} を持つことができ ます。符合無しの値はフィールド内に正の数だけを許可したくて、フィールドに対 して少し大きい数値の範囲が必要な時に使用できます。 As of MySQL 4.0.2, floating-point types also can be @code{UNSIGNED}. As with integer types, this attribute prevents negative values from being stored in the column. Unlike the integer types, the upper range of column values remains the same. @code{FLOAT} 型は近似数データ型を表すために使用されます。ANSI/ISO SQL92 標 準は、@code{FLOAT} キーワードに続く括弧中にオプションの精度(指数の範囲では ない)の指定を許しています。MySQL 実装はこのオプションの精度指定も サポートしています。キーワード @code{FLOAT} が精度の指定無しでフィールド型 として使用された時は、MySQL は値を格納するために4バイトを使用しま す。@code{FLOAT} キーワードに続く括弧中に2つの数値を与える構文もサポートさ れます。このオプションでの、最初の数値は値に必要な容量をバイトで表します。 2番目の数値は、格納、表示される小数部の桁数を指定します(@code{DECIMAL} と @code{NUMERIC} と同様)。MySQL がフィールドに指定されたよりも大き い小数部の桁数を持つ数値をこのフィールドに格納する時、値の格納時に余計な桁 を取り除くように値が丸められます。 @code{REAL} と @code{DOUBLE PRECISION} 型は精度指定を許しません。 ANSI/ISO SQL92 標準に対する拡張として、MySQL は @code{DOUBLE} を @code{DOUBLE PRECISION} 型の同義語として認識します。@code{REAL} の精度は @code{DOUBLE PRECISION} の指定よりも小さいことを要求する標準と異なり、 MySQL はどちらも8バイトの倍精度小数点の値として実装しています (非"ANSI モード"で実行した場合)。移植性を最大にするためには、近似数値 データ値の格納を要求するコードは、精度や小数部桁数の指定無しの @code{FLOAT} か @code{DOUBLE PRECISION} を使用すべきです。 フィールドの型の値の許容範囲を超えた数値を代入しようとすると、MySQL は その値を許容範囲いっぱいに切り詰め、その結果を代わりに代入します。 例えば、 @code{INT} フィールドの範囲は @code{-2147483648} から @code{2147483647} です。 もし @code{-9999999999} を @code{INT} フィールドに挿入しようとすると、値は範囲の 最低値に修正され、 @code{-2147483648} が代わりに代入されます。同様に、 @code{9999999999} の場合、 @code{2147483647} が代わりに代入されます。 そして、@code{INT} フィールドが符号無しの場合、フィールドの範囲の大きさは 同じですが、限界値は @code{0} と@code{4294967296} になります。 もし @code{-9999999999} と @code{9999999999} を代入しようとすると、 値は @code{0} と @code{4294967296} として代入されます。 @code{ALTER TABLE}, @code{LOAD DATA INFILE}, @code{UPDATE} または multi-row @code{INSERT} 時、これらの変換は `警告' として得られます。 @c FIX arjen 2002-08-07 New table, not yet measured for O'Reilly/DocBook @c FIX also need to shuffle into proper position and adjust text. @multitable @columnfractions .20 .20 .30 .30 @item @strong{Type} @tab @strong{Bytes} @tab @strong{From} @tab @strong{To} @item @code{TINYINT} @tab 1 @tab -128 @tab 127 @item @code{SMALLINT} @tab 2 @tab -32768 @tab 32767 @item @code{MEDIUMINT} @tab 3 @tab -8388608 @tab 8388607 @item @code{INT} @tab 4 @tab -2147483648 @tab 2147483647 @item @code{BIGINT} @tab 8 @tab -9223372036854775808 @tab 9223372036854775807 @end multitable @node Date and time types, String types, Numeric types, Column types @subsection 日付と時間の型 @cindex types, Date and Time @cindex Date and Time types @menu * Y2K issues:: Y2K issues and date types * DATETIME:: The @code{DATETIME}, @code{DATE} and @code{TIMESTAMP} types * TIME:: The @code{TIME} type * YEAR:: The @code{YEAR} type @end menu 日付と時間の型は @code{DATETIME}, @code{DATE}, @code{TIMESTAMP}, @code{TIME}, @code{YEAR} です. これらはそれぞれ値に適正な範囲があり、 ``zero'' はあなたが間違った値を指定した場合に用いられます。注意: MySQL は 確実に '厳密でない' 正しい日付の値、例えば @code{1999-11-31} を格納するこ とができます。この理由は、日付をチェックする処理の責任はアプリケーションに あり、SQL サーバにはないと考えているからです。日付を'速く'チェックするため に、MySQL は月が 0〜12 の範囲であるかと日が 0〜31 の範囲であるか だけをチェックします。上述の範囲は、MySQL が @code{DATE} または @code{DATETIME} フィールドに、日または月日が 0 である日付を格納できるため に定義されています。これは、正確な日付を知らない誕生日を登録する必要がある アプリケーションに非常に有用です。この場合、@code{1999-00-00} や @code{1999-01-00} のような日付を単純に登録できます(もちろん、このような日 付を @code{DATE_SUB()} や @code{DATE_ADD} のような関数で使用して、正しい値 が返ることは期待できません)。 これは、日付と時間型で作業する場合に、一般的に考慮しなければならないことです: @itemize @bullet @item MySQLは、標準形式で与えられた日付や時間から値を抽出しますが、与えられた 多様な形式の値(例えば、指定された値を日付や時間型に割り当てたり、比較したり)を解 釈しようと試みます。 それでも、次節で述べる形式だけがサポートされます。 それは、正当な値が与えられることを期待し、他の形式の値を使用されるような事態が起 こると、どのような結果となるか予想できません。 @item MySQL はいくつかの形式に値を変えてくれますが、 常に年の部分と日にちの部分は左から与えられていると期待しています。 日付は 年-月-日 の順(例えば、@code{'98-09-04'})でなくてはなりません。 月-日-年 や 日-月-年 の様などこでも使われているような形であってはなりません。 (例えば、@code{'09-04-98'}や@code{'04-09-98'}). @item MySQL は、もし数値の文脈で日付と時間の型が使用されると、 自動的に日付と時間を数値に直します。逆も行います。 @item MySQL が範囲外の誤った値を日付と時間型として受け取った場合 (このセクションの最初をみてください)、その値は ``ゼロ'' に変換されます。 (例外は、範囲外の@code{TIME}値が適切な@code{TIME}の範囲の限界値に切り詰められる ことです。) 以下に、それぞれの型の `ゼロ' の形式を示します： @multitable @columnfractions .15 .55 @item @strong{フィールドタイプ} @tab @strong{`ゼロ'値} @item @code{DATETIME} @tab @code{'0000-00-00 00:00:00'} @item @code{DATE} @tab @code{'0000-00-00'} @item @code{TIMESTAMP} @tab @code{00000000000000} (長さは表示サイズに依存し ます) @item @code{TIME} @tab @code{'00:00:00'} @item @code{YEAR} @tab @code{0000} @end multitable @item `ゼロ'値は特別ですが、表に示された値を明示的に使用して、格納したり参照したりでき ます。 この値は、 @code{'0'} 又は @code{0} を使用することにより、より簡潔に書くこともで きます。 @item @strong{MyODBC} 内で使用されている `ゼロ' の日付と時間は、 @strong{MyODBC} 2.50.12 以上では自動的に @code{NULL} に変換されます。 これは ODBC がこれらの値を扱えないからです。 @end itemize @node Y2K issues, DATETIME, Date and time types, Date and time types @subsubsection 西暦２０００年問題とデータ型 @cindex Year 2000 issues @cindex date types, Y2K issues MySQL 自体は2000年問題に対して安全です(@pxref{Year 2000 compliance})が、 MySQL に提示される入力値に関してはそうではありません。2桁の 年の入力は何世紀なのかわからないので全て曖昧です。このような値は MySQL が内部で年に4桁を使っていることから4桁の形式に変換されてしまいます。 MySQL は曖昧な日付を @code{DATETIME}, @code{DATE}, @code{TIMESTAMP} および @code{YEAR} 型に関して、以下の ルールに従って解釈します。 @itemize @bullet @item @code{00-69} の範囲の年は @code{2000-2069} に変換。 @item @code{70-99} の範囲の年は @code{1970-1999} に変換。 @end itemize これらのルールはデータが何を意味しているかに対して妥当な推定を与えるに 過ぎないことに注意してください。この MySQL 発見的手法が正しい値を生成し ない場合は曖昧でない4桁の年を含む入力を与えるべきです。 @code{ORDER BY} は2桁の @code{YEAR/DATE/DATETIME} 型を正しくソートされます。 注意: @code{MIN()} と @code{MAX()} のようないくつかの関数は @code{TIMESTAMP/DATE} を数値に変換します。これは年が2桁のタイムスタンプはこれらの関数で正しく動作しな いことを意味します。この場合の修復は、@code{TIMESTAMP/DATE} を4桁の年の形 式に変換するか、@code{MIN(DATE_ADD(timestamp,INTERVAL 0 DAYS))} のような何 かを使用することです。 @node DATETIME, TIME, Y2K issues, Date and time types @subsubsection @code{DATETIME}, @code{DATE}, @code{TIMESTAMP} 型 @tindex DATETIME @tindex DATE @tindex TIMESTAMP @code{DATETIME}, @code{DATE}, @code{TIMESTAMP}型はお互いに関連しています。このセ クションではそれらの特徴と、それぞれがどう同じでどう違うかを示します。 @code{DATETIME} 型は日付と時刻の情報を含む値が必要な場合に使います。MySQL は @code{DATETIME} 値を @code{'YYYY-MM-DD HH:MM:SS'} のフォーマットで取り出し、 表示します。 サポートされる範囲は @code{'1000-01-01 00:00:00'} から @code{'9999-12-31 23:59:59'} です。 (「サポートされる」とはさらに過去の値でも動くかも知れませんが保証の限りではない という意味です) @code{DATE} 型は時刻の部分なしで日付の値のみが必要な場合に使います。MySQL は @code{DATE} 値を@code{'YYYY-MM-DD'} のフォーマットで取り出し、表示します。サポ ートされる範囲は @code{'1000-01-01'} から @code{'9999-12-31'} です。 @code{TIMESTAMP} タイプは @code{INSERT} や @code{UPDATE} 操作に自動的に 現在の日付と時刻をマークする場合に提供される型です。 もし複数の @code{TIMESTAMP} フィールドがある場合には最初 の一つだけが自動的に更新されます。 最初の @code{TIMESTAMP} フィールドの自動更新は以下のいずれかの条件で起こります： @itemize @bullet @item そのフィールドが明示的に @code{INSERT} または @code{LOAD DATA INFILE} 文で指定さ れていないとき。 @item そのフィールドが明示的に @code{UPDATE} 文で指定されず、かつ、他のフィールドの値 が変わった場合。 (もともとフィールドに入っていた値と同じ値に更新しようとする @code{UPDATE} 文は @code{TIMESTAMP} フィールドを更新しないことに注意。なぜならあるフィールドを現在 と同じ値に変えようとしても MySQL は効率のためにそれを無視するからです。) @item 明示的に @code{TIMESTAMP} フィールドを @code{NULL} にした場合。 @end itemize 最初以外の @code{TIMESTAMP} フィールドも現在の日付と時刻にすることができます。そ れらのフィールドを@code{NULL} または @code{NOW()} にすることです。 どの @code{TIMESTAMP} フィールドも明示的に望む値をセットすることで現在の日時でな い値にすることができます。それは最初の @code{TIMESTAMP} フィールドについても同じ です。この特性は例えば @code{TIMESTAMP} フィールドをあるレコードが生成された時の 日時にし、その後その行が更新されても変化しないようにしたいというようなときに使え ます。 @itemize @bullet @item MySQL にレコードが生成されたときにそのフィールドをセットさせる。これで 現在日時に初期化される。 @item 以降の他のフィールドに対する更新時に @code{TIMESTAMP} フィールドをそれ自体が今持 っている値に明示的に更新する。 @end itemize 一方、この手法は @code{DATATIME} フィールドを行生成時に @code{NOW()} で初期化し 、以降の更新時に それをほうっておくのと同じように簡単であるとわかるでしょう。 @code{TIMESTAMP} の値は @code{1970} 年の最初から @code{2037} 年のどこかの時点ま での範囲で有効で、 1秒の時間分解能を持ちます。値は数値として表示されます。 MySQL が @code{TIMESTAMP} 値を取り出したり表示するのに使うフォーマット は以下の表 に示すようにその表示サイズに依存します。「目一杯の」 @code{TIMESTAMP} フォーマッ トは14桁ですが、 @code{TIMESTAMP} フィールドはより短い表示サイズで生成することも できます： @multitable @columnfractions .20 .25 @item @strong{フィールド型} @tab @strong{表示フォーマット} @item @code{TIMESTAMP(14)} @tab @code{YYYYMMDDHHMMSS} @item @code{TIMESTAMP(12)} @tab @code{YYMMDDHHMMSS} @item @code{TIMESTAMP(10)} @tab @code{YYMMDDHHMM} @item @code{TIMESTAMP(8)} @tab @code{YYYYMMDD} @item @code{TIMESTAMP(6)} @tab @code{YYMMDD} @item @code{TIMESTAMP(4)} @tab @code{YYMM} @item @code{TIMESTAMP(2)} @tab @code{YY} @end multitable 全ての @code{TIMESTAMP} フィールドは表示サイズに関係なく同じ格納サイズを持ちます。 もっとも一般的な表示サイズは 6 , 8 , 12 および 14 です。表示サイズはテーブル生成 時に任意の値に指定できますが、 0 および 14 以上の値は強制的に 14 になります。1 から 13 までの奇数のサイズは強制的に一つ大きい偶数になります。 @code{DATETIME}, @code{DATE}, @code{TIMESTAMP} 値は以下の共通フォーマットセット のいずれかを使って指定できます： @itemize @bullet @item 文字列で @code{'YYYY-MM-DD HH:MM:SS'} か @code{'YY-MM-DD HH:MM:SS'} の形式。 "柔軟な"書き方を許しています -- 日付や時刻の区切り文字として、いかなる句読記号 も使用できます。例えば、@code{'98-12-31 11:30:45'}, @code{'98.12.31 11+30+45'}, @code{'98/12/31 11*30*45'}, @code{'98@@12@@31 11^30^45'} は等価です。 @item 文字列で @code{'YYYY-MM-DD'} か @code{'YY-MM-DD'} の形式。 これも"柔軟な"書き方ができます。 例えば, @code{'98-12-31'},@code{'98.12.31'}, @code{'98/12/31'}, @code{'98@@12@@31'} は 等価です。 @item 文字列 @code{'YYYYMMDDHHMMSS'} または @code{'YYMMDDHHMMSS'} フォーマット。 「緩やかな」文法が認められていて、句読記号は日付、時刻部分の区切り として使えます。例えば @code{'98-12-31 11:30:45'}, @code{'98.12.31 11+30+45'}, @code{'98/12/31 11*:30*:45'}, @code{'98@@12@@31 11^30^45'} は全て等価です。 @item 文字列 @code{'YYYY-MM-DD'} または @code{'YY-MM-DD'} フォーマット。 これも「緩やかな」文法が認められています。例えば @code{'98-12-31'}, @code{'98.12.31'}, @code{'98/12/31'}, @code{'98@@12@@31'}は全て等価です。 @item 区切り文字なしの文字列 @code{'YYYYMMDDHHMMSS'} または @code{'YYMMDDHHMMSS'} フォ ーマットで日時として意味のあるもの。 例えば @code{'19970523091528'} および @code{'970523091528'} は @code{'1997-05-23 09:15:28'} と解釈されます。しかし @code{'971122129015'} は無効で (時と分の部分がおかしい)、 @code{'0000-00-00 00:00:00'} になります。 @item 区切り文字なしの文字列 @code{'YYYYMMDD'} または @code{'YYMMDD'} フォーマットで、 日付として意味のあるもの。 例えば @code{'19970523'} および @code{'970523'} は @code{'1997-05-23'} と解釈 されます。 しかし @code{'971332'} は無効で(月と日の部分がおかしい)、 @code{'0000-00-00'} になります。 @item @code{YYYYMMDDHHMMSS} または @code{YYMMDDHHMMSS} のフォーマットの数値で、日時と して意味のあるもの。例えば @code{19830905132800} および @code{830905132800} は @code{'1983-09-05 13:28:00'} と解釈されます。 @item @code{YYYYMMDD} または @code{YYMDD} のフォーマットの数値で日付として意味のある もの。 例えば @code{19830905} および @code{830905} は @code{'1983-09-05'} として解釈さ れます。 @item @code{NOW()} や @code{CURRENT_DATE} のように @code{DATETIME} , @code{DATE} , @code{TIMESTAMP} のコンテキストで アクセス可能な値を返す関数の結果。 @end itemize 無効な @code{DATETIME} , @code{DATE} , @code{TIMESTAMP} の値は適切な「ゼロ」値に 変換されます(@code{'0000-00-00 00:00:00'} , @code{'0000-00-00'} または @code{00000000000000} )。 日時の部分に区切りを持つ文字列で指定される値で、月、日の値が10未満の場 合は2桁で指定しなくてもかまいません。 @code{'1979-6-9'} は @code{'1979-06-09'} と等価です。同様に時刻の部分に区切りを持つ文字列で指定される値で、時、分、秒が @code{10} 未満の場合は2桁で指定しなくてもかまいません。 @code{'1979-10-30 1:2:3'} は @code{'1979-10-30 01:02:03'} と等価です。 数値でしていされる値は 6, 8, 12 または 14 桁である必要があります。もしその数 値が 8 または 14 桁の長さの時はそれぞれ @code{YYYYMMDD} および @code{YYYYMMDDHHMMSS} フォーマットで、最初の 4 桁で年が与えられるものと仮定 されます。もしその数値が 6または12桁の長さの時は @code{YYMMDD} および @code{YYMMDDHHMMSS} フォーマットで最初の2桁で年が与えられるものと仮定されます。 これら以外の長さの数値はあとに @code{0} が追加されてこれらのうちのもっとも近い 長さのものと解釈されます。 @cindex non-delimited strings @cindex strings, non-delimited 区切りなしの文字列で与えられる値はそれ自身の長さを使って解釈されます。 もし文字列が8または14文字ならば年は最初の4文字で与えられると仮定されま す。そうでなければ最初の2文字で与えられると仮定されます。文字列は左か ら右に年、月、日、時、分、秒と文字列中に表現されている分だけ順に解釈さ れます。つまり6文字以下の文字列は使ってはいけないということです。例え ば1999年3月を指定するつもりで @code{'9903'} を指定した場合、MySQL は「ゼロ」日付 をテーブルに挿入します。これは年と月の部分は @code{99} と @code{03} ですが日の部 分が欠けている(ゼロ)ために値が有効な日付でないために起こります。 @code{TIMESTAMP} フィールドは有効な値を、表示サイズに関係なく指定された値を最高 精度の時間分解能で格納します。このことはいくつかの意味合いを持ちます。 年の値が二桁で指定された場合、世紀の部分がないので曖昧な値となります。 MySQL は二桁の年の値を以下に示す規則にそって変換します： @itemize @bullet @item 列の型がTIMESTAMP(4)であってもTIMESTAMP(2)であっても常に年月日を指定 すること。そうでなければ値は無効で0が格納されます。 @item もし短い形式の @code{TIMESTAMP} を @code{ALTER TABLE} を使って拡張しようとした場 合、拡張前には「隠れていた」情報が現れます。 @item 同様に @code{TIMESTAMP} フィールドを縮めた場合も、値が表示された時により少ない情 報しか現れないという点を除いて、情報は失われません。 @item @code{TIMESTAMP} 値は最高精度の時間分解能で格納されますが、内部的に格納され た値を直接操作できる関数は @code{UNIX_TIMESTAMP()} のみです。他の関数はフォーマ ットされて取り出された値について操作します。つまり、 @code{HOUR()} や @code{SECOND()} などの関数は @code{TIMESTAMP} 値の対応する部分がフォーマットされた 値で含まれないと使うことができません。例えば @code{TIMESTAMP} 列の @code{HH} の部分は 表示サイズが少なくとも10以上ないと表示されないので、それより短い @code{TIMESTAMP} 値 に @code{HOUR()} の操作を行っても無意味な値しか得られません。 @end itemize ある日付型を他の日付型のオブジェクトに拡張して指定することができます。 しかしそれは値の変化や情報の欠落を起こす可能性があります。 @itemize @bullet @item @code{DATE} の値を @code{DATETIME} か @code{TIMESTAMP} の物に与えた場合、 時刻の部分は @code{'00:00:00'} になります。これは @code{DATE} 値が 時刻の情報を持っていないからです。 @item @code{DATETIME} か @code{TIMESTAMP} の値を @code{DATE} の物に与えた場合、 時刻の部分は削られます。これは @code{DATE} 値が 時刻の情報を持っていないからです。 @item @code{DATETIME}, @code{DATE}, @code{TIMESTAMP} 値は同じフォーマットのセットを使 って表現できますが、どの型も同じ値の範囲を持っているわけではないことを覚えておい てください。例えば @code{TIMESTAMP} 値は @code{1970} 年より前や @code{2037} 年よ り後の値にはできません。つまり @code{'1968-01-01'} という値は @code{DATETIME} や @code{DATE} の値としては有効ですが @code{TIMESTAMP} の値としては無効で、 そのようなオブジェクトを指定した場合は @code{0} に変換されます。 @end itemize @cindex problems, date values @cindex date values, problems 日付の値を指定するときの落とし穴に注意してください @itemize @bullet @item 文字列として指定される値の柔軟なフォーマットに騙されないよう。例え ば @code{'10:11:12'} は @samp{':'} を区切り文字とする時刻のように見えますが、日 付のコンテキストで使われるとこれは @code{'2010-11-12'} と解釈されます。 @code{'10:45:15'} は @code{'45'} が有効な月ではないので @code{'0000-00-00'} に 変換されます。 @item The MySQL server only performs basic checking on the validity of a date: days @code{00-31}, months @code{00-12}, years @code{1000-9999}. Any date not within this range will revert to @code{0000-00-00}. Please note that this still allows you to store invalid dates such as @code{2002-04-31}. It allows web applications to store data from a form without further checking. To ensure a date is valid, perform a check in your application. @item 2桁で表される年は世紀の部分が不明なので曖昧です。 MySQL は以下のルール で2桁の年を解釈します。 @itemize @minus @item @code{00-69} の範囲にある年の値は @code{2000-2069} 年とする。 @item @code{70-99} の範囲にある年の値は @code{1970-1999} 年とする。 @end itemize @end itemize @node TIME, YEAR, DATETIME, Date and time types @subsubsection @code{TIME} 型 @tindex TIME MySQL は @code{TIME} の値を @code{'HH:MM:SS'} (時の部分が大きい場合は @code{'HHH:MM:SS'}) というフォーマットで扱い、また表示します。 (時の部分が大きい場合は @code{'HHH:MM:SS'})。 @code{TIME} 値の範囲は @code{'-838:59:59'} から @code{'838:59:59'} の範囲です。 時の部分がこんなに大きいのは、@code{TIME} 型は一日すなわち24時間以内 の時刻を表現するのに用いられるだけではなく経過時間や二つの事象の間隔 (どちらも２４時間を越えたり、負の数になる場合もあります)を表現すること もあるからです。 @code{TIME} 値は様々なフォーマットで指定可能です： @itemize @bullet @item 文字列で @code{'D HH:MM:SS.fraction'} というフォーマット。 (MySQLはまだこの fraction を time フィールドに保存できません)。 以下の ``柔軟な'' 文法が使用できます： @code{HH:MM:SS.fraction}, @code{HH:MM:SS}, @code{HH:MM}, @code{D HH:MM:SS}, @code{D HH:MM}, @code{D HH} または @code{SS}。 ここで、@code{D} は 0〜33 の間の日です。 @item 文字列で @code{'HHMMSS'} というように区切りのないフォーマットで時刻として有効 なもの。例えば @code{'101112'} は @code{'10:11:12'} と解釈されますが @code{'1097 12'} は無効で(分の部分が無意味) @code{'00:00:00'} になります。 @item 数値で @code{HHMMSS} のフォーマットで時刻として有効なもの。 例えば @code{101112} は @code{'10:11:12'} と解釈されます。 次の別の形式も解釈できます: @code{SS}, @code{MMSS},@code{HHMMSS}, @code{HHMMSS.fraction}。注意: MySQL はまだ fraction 部を保存でき ません。 @item 例えば @code{CURRENT_TIME} のように @code{TIME} のコンテキストで受け付けられる値 を返す関数の結果。 @end itemize 文字列で時刻の各部の区切りを含む @code{TIME} の値については、時、分、秒が @code{10} 以下の場合、２桁の数字を指定する必要はありません。@code{'8:3:2'} は @code{'08:03:02'} と同じです。 「短い」 @code{TIME} 値を @code{TIME} フィールドとして指定する場合は要注意です。 コロンなしでは、MySQL はその値のもっとも右端の桁は秒を表すと仮定して解 釈します。 (MySQL は @code{TIME} の値を一日のうちの時刻としてより経過時間として 解釈します)。例えば @code{'11:12'},@code{'1112'}, @code{1112} が @code{'11:12:00'} (11時12分)を表しているつもりでいても、 MySQL はこれらを @code{'00:11:12'} (11分12秒)として解釈します。 同様に @code{'12'} および @code{12} は @code{'00:00:12'} と解釈します。 @code{TIME} の範囲外にある値で値以外は正しいものは範囲の端の値の適当な方にクリッ プされます。例えば @code{'-850:00:00'} および @code{'850:00:00'} は それぞれ @code{'-838:59:59'} および @code{'838:59:59'} になります。 無効な @code{TIME} 値は @code{'00:00:00'} に変換されます。 ここで @code{'00:00:00'} 自体は有効な @code{TIME} 値なので、 テーブル内に保存された'00:00:00'という値からそれがもとも と @code{'00:00:00'} と指定された値なのか無効なために変換された結果なのかを区 別する方法はないことに注意してください。 @node YEAR, , TIME, Date and time types @subsubsection @code{YEAR} 型 @tindex YEAR @code{YEAR} 型は年を表現するのに使われる1バイトの値です。 MySQL は @code{YEAR} の値を @code{YYYY} というフォーマットで扱い、 また表示します。範囲は @code{1901} から @code{2155} です。 @code{YEAR} 型は様々なフォーマットで指定可能です： @itemize @bullet @item @code{'1901'} から @code{'2155'} の範囲にある4桁の文字列 @item @code{1901} から @code{2155} の範囲にある4桁の数値。 @item @code{'00'} から @code{'99'} の範囲にある2桁の文字列。 @code{'00'} から @code{'69'} までおよび @code{'70'} から @code{'99'} までの範囲はそれぞれ @code{2000} から @code{2069} まで および @code{1970} から @code{1999} までの範囲の YEAR型に変換されます。 @item @code{1} から @code{99} の範囲にある2桁の数値。@code{1} から @code{69} まで および @code{70} から @code{99} までの範囲は それぞれ @code{2001} から @code{2069} までおよび @code{1970} から @code{1999} まで の範囲の @code{YEAR} 型に変換されます。 2桁の数値の場合は2桁の文字列の場合と若干異なっている点に注意してください。 なぜなら0を数値として指定し、それを2000年として解釈させることができないからです。 その場合は文字列で @code{'0'} または @code{'00'} を@emph{指定しなければ なりません}。そうでなければ数値0は無効なYEAR値を示す @code{0000} に変換されます。 @item 例えば @code{NOW()} のように @code{YEAR} コンテキストで受け入れられる値を返す関 数の結果。 @end itemize 無効な @code{YEAR} 値は @code{0000} に変換されます。 @node String types, Choosing types, Date and time types, Column types @subsection 文字列型 @cindex types, strings @cindex string types @tindex CHAR @tindex VARCHAR @menu * CHAR:: The @code{CHAR} and @code{VARCHAR} types * BLOB:: The @code{BLOB} and @code{TEXT} types * ENUM:: The @code{ENUM} type * SET:: The @code{SET} type @end menu 文字列型は@code{CHAR}, @code{VARCHAR}, @code{BLOB}, @code{TEXT}, @code{ENUM}, @code{SET} です。このセクションは、それらの型がどのように動作 するかと、要求されるサイズと、クエリ内での使用方法を説明します。 @c FIX arjen 2002-08-07 New table, not yet measured for O'Reilly/DocBook @c FIX also need to shuffle into proper position and adjust text. @multitable @columnfractions .40 .30 .30 @item @strong{Type} @tab @strong{Max.size} @tab @strong{Bytes} @item @code{TINYTEXT} or @code{TINYBLOB} @tab 2^8-1 @tab 255 @item @code{TEXT} or @code{BLOB} @tab 2^16-1 (64K-1) @tab 65535 @item @code{MEDIUMTEXT} or @code{MEDIUMBLOB} @tab 2^24-1 (16M-1) @tab 16777215 @item @code{LONGBLOB} @tab 2^32-1 (4G-1) @tab 4294967295 @end multitable @node CHAR, BLOB, String types, String types @subsubsection @code{CHAR} 型と @code{VARCHAR} 型 @code{CHAR} 型と @code{VARCHAR} 型はよく似ていますが格納、取り出しの手順に違いが あります。 @code{CHAR} フィールドの長さはテーブルを生成するときに宣言した長さに固定されます。 長さは 1 から 255 までの値を取ります。@code{CHAR} が格納されるときには指定された 長さになるように右側に空白が詰められます。@code{CHAR} の値が取り出された場合には 右側(後続)の空白は取り除かれます。 @code{VARCHAR} フィールドの値は可変長文字列です。 @code{VARCHAR} フィールドは @code{CHAR} フィールド と同じく 1 から 255 までの長さに宣言できます。 (MySQL バージョン 3.23 では, @code{CHAR} の長さは 0 から 255 まで許され ています.) しかし @code{CHAR} 型と異なり @code{VARCHAR} 型の値は必要な文字数の分に 長さを記録する1 バイトを足した領域に格納されます。値には桁合わせのための空白はつ けられません。後続の空白は値の格納時に取り除かれます。(この空白の除去は ANSI SQL仕様とは違っています。) もし @code{CHAR} または @code{VARCHAR} フィールドに、フィールドの最大長を 越える長さの値を与えた場合は、適合するように切り詰められます。 以下の表はこれらの二つのフィールド型の違いを、@code{CHAR(4)} および @code{VARCHA R(4)} に様々な文字列値を格納した結果を示すことで表しています。 @c Need to use @(space) to make sure second column values retain spacing @c in output for table below. @multitable @columnfractions .15 .15 .20 .15 .20 @item @strong{値} @tab @code{CHAR(4)} @tab @strong{必要な格納域} @tab @code {VARCHAR(4)} @tab @strong{必要な格納域} @item @code{''} @tab @code{'@ @ @ @ '} @tab 4 バイト @tab @code{''} @tab 1 バイト @item @code{'ab'} @tab @code{'ab@ @ '} @tab 4 バイト @tab @code{'ab'} @tab 3 バイト @item @code{'abcd'} @tab @code{'abcd'} @tab 4 バイト @tab @code{'abcd'} @tab 5 バイト @item @code{'abcdefgh'} @tab @code{'abcd'} @tab 4 バイト @tab @code{'abcd'} @tab 5 バイト @end multitable @code{CHAR(4)} フィールドの後続の空白は取り出し時にとりのぞかれるので、CHAR(4)お よび @code{VARCHAR(4)} から取り出される値はどの場合でも同じです。 @code{CHAR} および @code{VARCHAR} フィールドの値はテーブルの生成時に @code{BINARY} 属性が つけられない限り、大文字と小文字を区別しないでソート・比較されます。@code{BINARY} 属性は その列の値が大文字、小文字を区別して、MySQLサーバを実行しているマシンのASCII順に ソート・比較されることを意味します。 @code{BINARY} はフィールドがどのように格納されるか、どのように取り出される かには影響しません。 @code{BINARY} 属性は「固定的」です。つまり、もし @code{BINARY} であると指定された フィールドが式の中にあると式全体が @code{BINARY} の値として比較されるのです。 MySQL はテーブル生成時に何も断らずに@code{CHAR} または @code{VARCHAR} 型のフィールドを変更する事があります。 @xref{Silent column changes}. @node BLOB, ENUM, CHAR, String types @subsubsection @code{BLOB} と @code{TEXT} 型 @tindex BLOB @tindex TEXT @code{BLOB} は大きなバイナリ型のオブジェクトで、可変長のデータを保持できます。 4 つの @code{BLOB} 型、すなわち @code{TINYBLOB}, @code{BLOB}, @code{MEDIUMBLOB} と @code{LONGBLOB} は保持できるデータの最大長が違うだけです。 @xref{Storage requirements}. 4 つの @code{TEXT} 型、すなわち @code{TINYTEXT}, @code{TEXT}, @code{MEDIUMTEXT} と @code{LONGTEXT} は 4 つの @code{BLOB} 型に対応し、同じ最大長と 格納条件を持っています。 @code{TEXT} と @code{BLOB} の違いは、 @code{TEXT} はケースに依存しないでソートと比較され、 @code{BLOB} はケースに依存して(文字コードで)比較されることだけです。 いうならば、@code{TEXT} は、ケースに依存しない @code{BLOB} です。 もし @code{BLOB} や @code{TEXT} フィールドにそれらの最大長以上の値が与えられた 場合、その値はきっちり収まるように切り落とされます。 ほとんどの点で、@code{TEXT} フィールドを @code{VARCHAR} の大きい物と見なすことが 出来ます。 同様に、@code{BLOB} フィールドは @code{VARCHAR BINARY} フィールドの大きくなった 物です。 違いは、 @itemize @bullet @item MySQL バージョン 3.23.2 以上では、@code{BLOB} と @code{TEXT} 項に インデックスを持つことが出来ます。それ以前のバージョンでは インデックスをもつことが出来ません。 @item @code{VARCHAR} フィールドで行っているようには、@code{BLOB} と @code{TEXT} フィー ルドの値の後ろについている連続した空白文字は切り落とされません。 @item @cindex default values, @code{BLOB} and @code{TEXT} columns @cindex @code{BLOB} columns, default values @cindex @code{TEXT} columns, default values @code{BLOB} と @code{TEXT} 項は @code{DEFAULT} 値を持つことが出来ません。 @end itemize @code{MyODBC} は @code{BLOB} を @code{LONGVARBINARY} として、 @code{TEXT} を @code{LONGVARCHAR} として定義します。 @code{BLOB} と @code{TEXT} フィールドは極端に長いので、それらを使用する際には、 いくつかの困った事にでくわすかもしれません： @itemize @bullet @item もし @code{GROUP BY} か @code{ORDER BY} を @code{BLOB} フィールドや @code{TEXT} フィールドで使用したいなら、フィールドの値を固定長のものに変換しなくてはなりま せん。標準的な方法は、 @code{SUBSTRING} 関数を使用することです。 たとえば： @example mysql> SELECT comment FROM tbl_name,SUBSTRING(comment,20) AS substr -> ORDER BY substr; @end example もしこれをしない場合、フィールドの最初の @code{max_sort_length} バイトが ソート時に使用されます。 @code{max_sort_length} のデフォルト値は 1024; この値は @code{mysqld} サーバー起動時に @code{-O} オプションを使用することで 変更できます。 フィールドの位置を指定することによってか、エイリアスを使用することによって、 @code{BLOB} や @code{TEXT} の値で group 化できます。 @example mysql> SELECT id,SUBSTRING(blob_col,1,100) FROM tbl_name GROUP BY 2; mysql> SELECT id,SUBSTRING(blob_col,1,100) AS b FROM tbl_name GROUP BY b; @end example @item @code{BLOB} または @code{TEXT} オブジェクトの最大長はその型により決定されますが、 あなたがクライアントとサーバの間で実際に送ることができるは最大長は、 利用可能なメモリ量とコミュニケーションバッファのサイズによって決定されます。 メッセージバッファサイズを変えることができますが、その場合、サーバーとクライアン ト、両方共に変更しなければなりません。@xref{Server parameters}. @end itemize それぞれの @code{BLOB}, @code{TEXT} フィールドは、一意のアロケートされたオブジェ クトによって、内部では表されることに注意してください.。 これはテーブルが開かれるときに一度だけアロケートされる他のフィールドとは対照的で す。 @node ENUM, SET, BLOB, String types @subsubsection @code{ENUM} 型 @tindex ENUM @code{ENUM} はストリングオブジェクトで、 その値は、通常、テーブル作成時のフィールド定義で列挙された値の中から選ばれます。 値はある状況下では 空文字 (@code{""}) か @code{NULL} を取ることがあります： @itemize @bullet @item もし @code{ENUM} に無効な値 (列挙されている値の中に含まれない文字) を 代入した場合、 そのエラーになる文字の代わりに空文字が挿入されます。 @item もし @code{ENUM} が @code{NULL} と定義された場合, @code{NULL} はそのフィールドで 許可される値となり、デフォルト値が @code{NULL} になります。 もし @code{ENUM} が @code{NOT NULL} と定義されたならば、 デフォルト値は、 列挙リストの最初の値になります。 @end itemize 列挙されたそれぞれの値はインデックスを持ちます： @itemize @bullet @item 列挙リストの要素は 1 から付番されます。 @item 空文字エラーのインデックス値は 0 。 これは不正な @code{ENUM} 値が与えられているレコードを見つけるために 以下のような @code{SELECT} 構文が使用できることを意味します： @example mysql> SELECT * FROM tbl_name WHERE enum_col=0; @end example @item @code{NULL} のインデックス値は @code{NULL}. @end itemize たとえば、フィールドが @code{ENUM("one", "two", "three")} と定義されたなら、 以下に示す値をとります。 それぞれのインデックス値も示します。 @multitable @columnfractions .10 .10 @item @strong{値} @tab @strong{インデックス} @item @code{NULL} @tab @code{NULL} @item @code{""} @tab 0 @item @code{"one"} @tab 1 @item @code{"two"} @tab 2 @item @code{"three"} @tab 3 @end multitable 列挙は最大 65535 個の要素まで可能です。 Starting from 3.23.51 trailing spaces are automatically deleted from @code{ENUM} values when the table is created. @code{ENUM} フィールドに値を与える場合は大文字小文字は無関係です。 しかし、後でフィールドから検索される値は、大文字小文字をもちます。 これはテーブル作成時に与えられたリストの値です。 もし @code{ENUM} を数値の文脈で検索した場合、そのメンバーを前から数えた 時の順番が数値で返ってきます。 たとえば、@code{ENUM} フィールドから次のようにして数値を取り出すことができ ます: @example mysql> SELECT enum_col+0 FROM tbl_name; @end example もし @code{ENUM} に数値を代入しようとした場合、その数値の位置にある メンバーが代入されます。 (しかし、これは @code{LOAD DATA} では働きません。これはすべての入力を文字 列として扱います。) It's not advisable to store numbers in an @code{ENUM} string because it will make things confusing. @code{ENUM} 値は列挙メンバがフィールド指定にリストされた順に従ってソートさ れます。(つまり、@code{ENUM} 値はインデックス値に従ってソートされます。) 例えば、@code{ENUM("a", "b")} ならば @code{"a"} が @code{"b"} の前にソートされ、 @code{ENUM("b", "a")} ならば @code{"b"} が @code{"a"} の前にソートされます。 空文字列は空ではない文字の前にソートされ、 @code{NULL} は他の列挙の前に並びます。 To prevent unexpected results, specify the @code{ENUM} list in alphabetical order. You can also use @code{GROUP BY CONCAT(col)} to make sure the column is sorted alphabetically rather than by index number. @code{ENUM} フィールドで指定可能な値のリストを全て取りたいならば、 次のようにします： @code{SHOW COLUMNS FROM table_name LIKE enum_column_name} そして二番目のフィールドの @code{ENUM} 定義を分析します。 @node SET, , ENUM, String types @subsubsection @code{SET} 型 @code{SET} は文字型オブジェクトでゼロかそれ以上を値持ちます。 テーブル作成時には、それぞれの値はリストから選ばれるべきです。 @code{SET} 型のフィールドの値は、コンマ(@samp{,}) 区切りで並べられた複数のメンバーで構成されています。 これは、 @code{SET} メンバーの値中にコンマを含むことが出来ない、 ということです。 例えば、 @code{SET("one", "two") NOT NULL} と指定されたフィールドは以下の値をとります： @example "" "one" "two" "one,two" @end example @code{SET} は最大 64 個の異なったメンバーがもてます。 Starting from 3.23.51 trailing spaces are automatically deleted from @code{SET} values when the table is created. MySQL は @code{SET} の値を数値として代入します。代入された 値の最下位のビットが最初のメンバーに対応します。もし @code{SET} 値を 数値の文脈で検索した場合、検索される値はフィールドの値に対応します。 たとえば、@code{SET} フィールドから次のようにして数値を取り出すことができ ます: @example mysql> SELECT set_col+0 FROM tbl_name; @end example もし数値が @code{SET} フィールドに代入された場合、 二進数で表される数値のビットによって、メンバーが決定されます。 @code{SET("a","b","c","d")} とフィールドが定義されたとします。 メンバーは以下の２進数の値を持ちます： @multitable @columnfractions .15 .20 .20 @item @code{SET} @strong{member} @tab @strong{10進数} @tab @strong{２進数値} @item @code{a} @tab @code{1} @tab @code{0001} @item @code{b} @tab @code{2} @tab @code{0010} @item @code{c} @tab @code{4} @tab @code{0100} @item @code{d} @tab @code{8} @tab @code{1000} @end multitable もしこのフィールドに @code{9} を与えた場合、これは２進数で @code{1001} ですから、 1 番目と 4 番目の @code{SET} メンバーである @code{"a"} と @code{"d"} が 選択され、結果、 @code{"a,d"} となります。 1つ以上の @code{SET} 要素を含む値においては,あなたが値を挿入するとき,要素がどん な 順序で記載されているのかは重要ではありません. また,何回要素が与えられたのかは 重要ではありません. 後で値が検索されるとき, 値の中のそれぞれの要素は ただ一回だけ表れます。そのとき、テーブル作成時に与えられた順に要素は並びます。 例えば、フィールドが @code{SET("a","b","c","d")} と設定されていたなら、 @code{"a,d"}, @code{"d,a"}, @code{"d,a,a,d,d"} は検索されると @code{"a,d"} と なります。 If you set a @code{SET} column to an unsupported value, the value will be ignored. @code{SET} 値は数値として代入されます。 @code{NULL} 値は非 @code{NULL} @code{SET} 値の前にソートされます。 通常、@code{LIKE} か @code{FIND_IN_SET()} を使用して @code{SET} フィールド の @code{SELECT} を行います： @example mysql> SELECT * FROM tbl_name WHERE set_col LIKE '%value%'; mysql> SELECT * FROM tbl_name WHERE FIND_IN_SET('value',set_col)>0; @end example しかし、以下も動作します： @example mysql> SELECT * FROM tbl_name WHERE set_col = 'val1,val2'; mysql> SELECT * FROM tbl_name WHERE set_col & 1; @end example 最初の文は完全一致するものを探します。 二つ目は第一番目のメンバーを含む値を探します。 もし @code{SET} フィールドで設定可能なすべてのメンバーを知りたい場合： @code{SHOW COLUMNS FROM table_name LIKE set_column_name} とし、 ２番目にあらわされる @code{SET} 定義を分析します。 @node Choosing types, Other-vendor column types, String types, Column types @subsection 正しいフィールド型の選択 @cindex types, columns @cindex choosing types もっとも効率よく格納するには、全てにおいて一番正確な型を使用することです。 例えば、@code{1}-@code{99999} の整数 には、@code{MEDIUMINT UNSIGNED} が最良の型です。 良くある問題は、貨幣の値の正確な表現です。MySQL では @code{DECIMAL} 型を使用すべきです。これは文字列として格納し、正確さのロ スは発生しません。正確さが重要でない場合は @code{DOUBLE} 型でも十分良い です。 高精度のため、常に @code{BITINT} に格納される固定小数点型に変換できます。 これは、全ての計算を整数で行なうようにし、結果だけを浮動小数点に変換して 戻します。 @node Other-vendor column types, Storage requirements, Choosing types, Column types @subsection 他のデータベースエンジンのフィールド型の使用 @cindex types, portability @cindex portability, types @cindex columns, other types ほかのベンダーからSQLを簡単に書けれるように、 MySQL は以下の表に しめすフィールド型をサポートします。これらは、テーブルの定義を、 他のデータベースエンジンから MySQL に簡単に移行させてくれます： @multitable @columnfractions .25 .30 @item @strong{Other vendor type} @tab @strong{MySQL type} @item @code{BINARY(NUM)} @tab @code{CHAR(NUM) BINARY} @item @code{CHAR VARYING(NUM)} @tab @code{VARCHAR(NUM)} @item @code{FLOAT4} @tab @code{FLOAT} @item @code{FLOAT8} @tab @code{DOUBLE} @item @code{INT1} @tab @code{TINYINT} @item @code{INT2} @tab @code{SMALLINT} @item @code{INT3} @tab @code{MEDIUMINT} @item @code{INT4} @tab @code{INT} @item @code{INT8} @tab @code{BIGINT} @item @code{LONG VARBINARY} @tab @code{MEDIUMBLOB} @item @code{LONG VARCHAR} @tab @code{MEDIUMTEXT} @item @code{MIDDLEINT} @tab @code{MEDIUMINT} @item @code{VARBINARY(NUM)} @tab @code{VARCHAR(NUM) BINARY} @end multitable もし他のベンダーの型を使用してテーブルを作ろうとすると、 テーブル作成時のフィールドの型のマッピングが発生し、 @code{DESCRIBE tbl_name} 構文を発行します。 そして MySQL は、使用された型と等価な MySQL の型を用いて テーブルを構成したことを告げます。 @node Storage requirements, , Other-vendor column types, Column types @subsection 各フィールド型の所要容量 @cindex storage requirements, column type @cindex columns, storage requirements MySQLがサポートする各フィールドタイプ毎の所要容量を、カテゴリ別に以下に 記述します。 @cindex numeric types @cindex types, numeric @subsubheading 数値タイプの保存容量 @multitable @columnfractions .35 .65 @item @strong{フィールドタイプ} @tab @strong{所要容量} @item @code{TINYINT} @tab 1 byte @item @code{SMALLINT} @tab 2 bytes @item @code{MEDIUMINT} @tab 3 bytes @item @code{INT} @tab 4 bytes @item @code{INTEGER} @tab 4 bytes @item @code{BIGINT} @tab 8 bytes @item @code{FLOAT(X)} @tab X <= 24 の場合 4、25 <= X <= 53 の場合 8 @item @code{FLOAT} @tab 4 bytes @item @code{DOUBLE} @tab 8 bytes @item @code{DOUBLE PRECISION} @tab 8 bytes @item @code{REAL} @tab 8 bytes @item @code{DECIMAL(M,D)} @tab D > 0 の場合 @code{M+2}, D = 0 の場合 @code{M+1} bytes (@code{M < D} の場合 @code{D}+2) @item @code{NUMERIC(M,D)} @tab D > 0 の場合 @code{M+2}, D = 0 の場合 @code{M+1} bytes (@code{M < D} の場合 @code{D}+2) @end multitable @cindex date types @cindex time types @cindex types, date @cindex types, time @subsubheading 日付と時間タイプの保存容量 @multitable @columnfractions .35 .65 @item @strong{フィールドタイプ} @tab @strong{所要容量} @item @code{DATE} @tab 3 bytes @item @code{DATETIME} @tab 8 bytes @item @code{TIMESTAMP} @tab 4 bytes @item @code{TIME} @tab 3 bytes @item @code{YEAR} @tab 1 byte @end multitable @subsubheading 文字列タイプの保存容量 @multitable @columnfractions .35 .65 @item @strong{フィールドタイプ} @tab @strong{所要容量} @item @code{CHAR(M)} @tab @code{M} bytes, @code{1 <= M <= 255} @item @code{VARCHAR(M)} @tab @code{L}+1 bytes, where @code{L <= M} and @code{1 <= M <= 255} @item @code{TINYBLOB}, @code{TINYTEXT} @tab @code{L}+1 bytes,where @code{L} < 2^8 @item @code{BLOB}, @code{TEXT} @tab @code{L}+2 bytes,where @code{L} < 2^16 @item @code{MEDIUMBLOB}, @code{MEDIUMTEXT} @tab @code{L}+3 bytes,where @code{L} < 2^24 @item @code{LONGBLOB}, @code{LONGTEXT} @tab @code{L}+4 bytes,where @code{L} < 2^32 @item @code{ENUM('value1','value2',...)} @tab 1 or 2 bytes, 列挙値の数に依存 (最大値は 65535 ) @item @code{SET('value1','value2',...)} @tab 1, 2, 3, 4 or 8 bytes, 要素の数に依存 (最大要素 64 ) @end multitable @cindex @code{BLOB}, size @cindex @code{TEXT}, size @cindex @code{VARCHAR}, size @code{VARCHAR}、@code{BLOB}、及び@code{TEXT}型は可変長型であり、所要容量は、フィ ールドのとり得る最大サイズというよりはむしろフィールド値の実際の長さに依存します (前の表で@code{L}と表しました)。 例えば、@code{VARCHAR(10)}フィールドは、最大10文字分の長さの文字列を保持すること が出来ます。実際の所要容量は、文字列の長さ(@code{L})と、その長さを記録するための １バイトを加えます。文字列@code{'abcd'}においては、@code{L}は４で、所要容量は５ バイトです。 @code{BLOB}と@code{TEXT}型は、フィールド値の長さを記録するのに、１、２、３、又は ４バイト必要とし、型のとり得る最大の長さに依存します。@xref{BLOB}. テーブルが可変長フィールド型を含む場合、そのレコードフォーマットもまた可変長とな るでしょう。 テーブルが作成された時、MySQLは確かな条件の下、フィールドを可変長タイプ から固定長タイプへ変更し、副作用を起こすことに注意して下さい。 @xref{Silent column changes}. @cindex ENUM, size @code{ENUM}オブジェクトのサイズは、異なる列挙値の数によって決められます。 列挙する数が255以内では、１バイトが使用されます。 列挙する数が65535以内では、２バイトが使用されます。@xref{ENUM}. @cindex SET, size @code{SET}オブジェクトのサイズは、異なる要素の数によって決められます。 組のサイズを@code{N}とすると、オブジェクトは@code{(N+7)/8}バイトを占有し、 １、２、３、４又は８バイトに切上げられます。 １つの@code{SET}は、最大６４要素を持つことができます。@xref{SET}. @node Functions, Data Manipulation, Column types, Reference @section @code{SELECT} と @code{WHERE} 節で使用する関数 @cindex functions for @code{SELECT} and @code{WHERE} clauses SQL ステートメント中の @code{select_expression} または @code{where_definition} は後述の関数を使用した任意の式からなります。 演算と関数を式の中で呼ぶ時、本ドキュメントに示しているもの以外の、 @code{NULL} を含む式は常に @code{NULL} 値を生成します @strong{注意}: 関数名とそれに続く語句の間には、空白はありません。 これは関数の呼び出しと、関数と同名のテーブル(かフィールド)の参照を、 MySQL パーサが区別するのを助けます。 @code{mysqld} に @code{--ansi} をつけて起動するか、 @code{CLIENT_IGNORE_SPACE} を @code{mysql_connect()} に使用すれば、 MySQL が関数名の後の空白を許すようになりますが、その場合、すべて の関数名が予約語になります。@xref{ANSI mode}。 @need 2000 次の例では、@code{mysql} プログラムの出力は短くなっています。つまり: @example mysql> SELECT MOD(29,9); 1 rows in set (0.00 sec) +-----------+ | mod(29,9) | +-----------+ | 2 | +-----------+ @end example これは次に変換されています: @example mysql> SELECT MOD(29,9); -> 2 @end example @menu * Non-typed Operators:: Non-Type-Specific Operators and Functions * String functions:: String functions * Numeric Functions:: Numeric Functions * Date and time functions:: Date and time functions * Cast Functions:: Cast Functions * Other Functions:: Other Functions * Group by functions:: Functions for Use with @code{GROUP BY} Clauses @end menu @node Non-typed Operators, String functions, Functions, Functions @subsection Non-Type-Specific Operators and Functions @menu * Parentheses:: Parentheses * Comparison Operators:: Comparison Operators * Logical Operators:: Logical Operators * Control flow functions:: Control Flow Functions @end menu @cindex MyISAM, size The maximum size of a row in a @code{MyISAM} table is 65534 bytes. Each @code{BLOB} and @code{TEXT} column accounts for only 5-9 bytes towards this size. @node Parentheses, Comparison Operators, Non-typed Operators, Non-typed Operators @subsubsection Parentheses @findex () (parentheses) @findex parentheses ( and ) @cindex functions, grouping @cindex grouping, expressions @example ( ... ) @end example Use parentheses to force the order of evaluation in an expression. For example: @example mysql> SELECT 1+2*3; -> 7 mysql> SELECT (1+2)*3; -> 9 @end example @node Comparison Operators, Logical Operators, Parentheses, Non-typed Operators @subsubsection 比較演算子 @findex comparison operators @cindex casts @cindex type conversions @code{1} (TRUE), @code{0} (FALSE) または @code{NULL} を返します。 これらの関数は数値と文字列の両方で働きます。 必要ならば、文字は自動的に数字に変換され、数字は文字に変換されます。 (Perlがおこなっているみたいに) MySQL は以下の規則で比較を行います： @itemize @bullet @item どちらかまたは両方の引数が @code{NULL} の場合は、比較結果は @code{NULL} です。@code{<=>} 演算子を除きます。 @item 比較操作の両方の引数が文字列の場合、文字列として比較されます。 @item 両方の引数が整数の場合、整数として比較されます。 @item 16進数の値は、もし数値と比較されないのであれば、文字列として扱われます。 @item @cindex ODBC compatibility @cindex compatibility, with ODBC 引数の一方が @code{TIMESTAMP} または @code{DATETIME} フィールドで、他の引数が 定数の場合は、定数は比較前に timestamp に変換されます。これはより ODBC フレンドリにするためです。 @item 他の場合は全て浮動小数点(real)として比較されます。 @end itemize 文字列の比較は、ケースに依存せず、標準のキャラクターセットに従って 行われます。(ISO-8859-1 Latin1 がデフォルトです。これは English です) 以下は、比較のために文字が数値へ変換されている例です： @example mysql> SELECT 1 > '6x'; -> 0 mysql> SELECT 7 > '6x'; -> 1 mysql> SELECT 0 > 'x6'; -> 0 mysql> SELECT 0 = 'x6'; -> 1 @end example @table @code @findex = (equal) @findex equal (=) @item = 等しい: @example mysql> SELECT 1 = 0; -> 0 mysql> SELECT '0' = 0; -> 1 mysql> SELECT '0.0' = 0; -> 1 mysql> SELECT '0.01' = 0; -> 0 mysql> SELECT '.01' = 0.01; -> 1 @end example @findex <> (not equal) @findex not equal (<>) @findex != (not equal) @findex not equal (!=) @item <> @itemx != 等しくない: @example mysql> SELECT '.01' <> '0.01'; -> 1 mysql> SELECT .01 <> '0.01'; -> 0 mysql> SELECT 'zapp' <> 'zappp'; -> 1 @end example @findex <= (less than or equal) @findex less than or equal (<=) @item <= より小さいか等しい: @example mysql> SELECT 0.1 <= 2; -> 1 @end example @findex < (less than) @findex less than (<) @item < より小さい: @example mysql> SELECT 2 < 2; -> 0 @end example @findex >= (greater than or equal) @findex greater than or equal (>=) @item >= より大きいか等しい: @example mysql> SELECT 2 >= 2; -> 1 @end example @findex > (greater than) @findex greater than (>) @item > より大きい: @example mysql> SELECT 2 > 2; -> 0 @end example @cindex @code{NULL}, testing for null @findex <=> (Equal to) @item <=> 等しい(NULL 安全): @example mysql> SELECT 1 <=> 1, NULL <=> NULL, 1 <=> NULL; -> 1 1 0 @end example @cindex @code{NULL}, testing for null @findex IS NULL @findex IS NOT NULL @item IS NULL @itemx IS NOT NULL 値が @code{NULL} とであるかどうかのテスト: @example mysql> SELECT 1 IS NULL, 0 IS NULL, NULL IS NULL; -> 0 0 1 mysql> SELECT 1 IS NOT NULL, 0 IS NOT NULL, NULL IS NOT NULL; -> 1 1 0 @end example @cindex ODBC compatibility @cindex compatibility, with ODBC To be able to work good with other programs, MySQL supports the following extra features when using @code{IS NULL}: @itemize @bullet @item You can find the last inserted row with: @example SELECT * FROM tbl_name WHERE auto_col IS NULL @end example This can be disabled by setting @code{SQL_AUTO_IS_NULL=0}. @xref{SET OPTION}. @item For @code{NOT NULL} @code{DATE} and @code{DATETIME} columns you can find the special date @code{0000-00-00} by using: @example SELECT * FROM tbl_name WHERE date_column IS NULL @end example This is needed to get some ODBC applications to work (as ODBC doesn't support a @code{0000-00-00} date) @end itemize @findex BETWEEN ... AND @item expr BETWEEN min AND max もし @code{expr} が @code{min} 以上、 @code{max} 以下なら @code{1}を返します。 そうでないなら @code{0} を返します。 これは 全ての引数が同じ型ならば、@code{(min <= expr AND expr <= max)} と同じです。 Otherwise type conversion takes place, according to the rules above, but applied to all the three arguments. @strong{Note} that before 4.0.5 arguments were converted to the type of @code{expr} instead. @example mysql> SELECT 1 BETWEEN 2 AND 3; -> 0 mysql> SELECT 'b' BETWEEN 'a' AND 'c'; -> 1 mysql> SELECT 2 BETWEEN 2 AND '3'; -> 1 mysql> SELECT 2 BETWEEN 2 AND 'x-3'; -> 0 @end example @findex NOT BETWEEN @item expr NOT BETWEEN min AND max Same as @code{NOT (expr BETWEEN min AND max)}. @findex IN @item expr IN (value,...) もし @code{expr} が @code{IN} リストにある値のどれかならば、@code{1} を返します 。 そうでなければ @code{0} を返します。 もし全ての値が定数なら、すべての値が @code{expr} の型に従って評価され、 ソートされます。この検索にはバイナリサーチが使用されます。 これは @code{IN} リストに定数を与えた場合、@code{IN} が速くなることを意味します。 もし @code{expr} がケース依存の文字式なら、ケース依存のやり方で比較されます。 @example mysql> SELECT 2 IN (0,3,5,'wefwf'); -> 0 mysql> SELECT 'wefwf' IN (0,3,5,'wefwf'); -> 1 @end example From 4.1 (in line with the SQL-99 standard), @code{IN} returns @code{NULL} not only if the expression on the left hand side is @code{NULL}, but also if no match is found in the list and one of the expressions in the list is @code{NULL}. @findex NOT IN @item expr NOT IN (value,...) @code{NOT (expr IN (value,...))} と同じ。 @findex ISNULL() @item ISNULL(expr) @code{expr} が @code{NULL} なら @code{1} を、そうでなければ @code{0} を返します @example mysql> SELECT ISNULL(1+1); -> 0 mysql> SELECT ISNULL(1/0); -> 1 @end example @code{NULL} の値を @code{=} を使用して比較した場合は常に偽(false) となることに 注意してください！ @cindex @code{NULL}, testing for null @findex COALESCE() @item COALESCE(list) list 中の、最初に現れた 非-@code{NULL} 要素を返します。 @example mysql> SELECT COALESCE(NULL,1); -> 1 mysql> SELECT COALESCE(NULL,NULL,NULL); -> NULL @end example @findex INTERVAL() @item INTERVAL(N,N1,N2,N3,...) もし @code{N} < @code{N1} なら @code{0} を返します。 もし @code{N} < @code{N2} なら @code{1} を返します。 全ての引数は整数として扱われます。 これは @code{N1} < @code{N2} < @code{N3} < @code{...} < @code{Nn}を正しく動作さ せるために 必要なことです。これはバイナリ検索が使用されます(速いです) @example mysql> SELECT INTERVAL(23, 1, 15, 17, 30, 44, 200); -> 3 mysql> SELECT INTERVAL(10, 1, 10, 100, 1000); -> 2 mysql> SELECT INTERVAL(22, 23, 30, 44, 200); -> 0 @end example @end table If you are comparing case-insensitive strings with any of the standard operators (@code{=}, @code{<>}..., but not @code{LIKE}) trailing whitespace (spaces, tabs and newlines) will be ignored. @example mysql> SELECT "a" ="A \n"; -> 1 @end example @node Logical Operators, Control flow functions, Comparison Operators, Non-typed Operators @subsubsection 論理演算 @findex Logical operators @findex Operators, logical 全ての論理関数は @code{1} (TRUE) か @code{0} (FALSE) か @code{NULL} を返します。 (unknown は多くの場合 FALSE と同じです)： @table @code @findex NOT, logical @findex ! (logical NOT) @item NOT @itemx ! 論理否定。引数が @code{0} なら @code{1} を返し、そうでなければ @code{0} を返しま す。 例外: @code{NOT NULL} は @code{NULL} を返します: @example mysql> SELECT NOT 1; -> 0 mysql> SELECT NOT NULL; -> NULL mysql> SELECT ! (1+1); -> 0 mysql> SELECT ! 1+1; -> 1 @end example 最後の例は @code{1} を返します。なぜなら、式の評価が @code{(!1)+1} と同じだからです。 @findex AND, logical @findex && (logical AND) @item AND @itemx && 論理積。 全ての引数が 非@code{0} または 非@code{NULL} であれば @code{1} を返します。 引数のどれかが @code{0} ならば @code{0} を返します。 それ以外は @code{NULL} を返します。 @example mysql> SELECT 1 && 1; -> 1 mysql> SELECT 1 && 0; -> 0 mysql> SELECT 1 && NULL; -> NULL mysql> SELECT 0 && NULL; -> 0 mysql> SELECT NULL && 0; -> 0 @end example Please note that MySQL versions prior to 4.0.5 stop evaluation when a @code{NULL} is encountered, rather than continuing the process to check for possible @code{0}s. This means that in these versions, @code{SELECT (NULL AND 0)} returns @code{NULL} instead of @code{0}. In 4.0.5 the code has been re-engineered so that the result will always be as prescribed by ANSI while still using the optimisation wherever possible. @findex OR, logical @findex || (logical OR) @item OR @itemx || 論理和。 Evaluates to @code{1} if any operand is non-zero, to @code{NULL} if any operand is @code{NULL}, otherwise @code{0} is returned. @example mysql> SELECT 1 || 1; -> 1 mysql> SELECT 1 || 0; -> 1 mysql> SELECT 0 || 0; -> 0 mysql> SELECT 0 || NULL; -> NULL mysql> SELECT 1 || NULL; -> 1 @end example @findex XOR, logical @item XOR Logical XOR. Returns @code{NULL} if either operand is @code{NULL}. For non-@code{NULL} operands, evaluates to @code{1} if an odd number of operands is non-zero, otherwise @code{0} is returned. @example mysql> SELECT 1 XOR 1; -> 0 mysql> SELECT 1 XOR 0; -> 1 mysql> SELECT 1 XOR NULL; -> NULL mysql> SELECT 1 XOR 1 XOR 1; -> 1 @end example @code{a XOR b} is mathematically equal to @code{(a AND (NOT b)) OR ((NOT a) and b)}. @code{XOR} was added in version 4.0.2. @end table @node Control flow functions, , Logical Operators, Non-typed Operators @subsubsection フロー制御関数 @findex control flow functions @findex functions, control flow @table @code @cindex @code{NULL}, testing for null @findex IFNULL() @item IFNULL(expr1,expr2) @code{expr1} が @code{NULL} でない場合は @code{expr1} を、そうでなければ @code{expr2} を返します。 @code{IFNULL()} はどの文脈で使用されたかにより数値か文字を返します: @example mysql> SELECT IFNULL(1,0); -> 1 mysql> SELECT IFNULL(NULL,10); -> 10 mysql> SELECT IFNULL(1/0,10); -> 10 mysql> SELECT IFNULL(1/0,'yes'); -> 'yes' @end example In 4.0.6 and above the default result value of @code{IFNULL(expr1,expr2)} is the more 'general' of the two expressions, in the order @code{STRING}, @code{REAL} or @code{INTEGER}.The difference to earlier MySQL versions are mostly notable when you create a table based on expressions or MySQL has to internally store a value from @code{IFNULL()} in a temporary table. @example CREATE TABLE foo SELECT IFNULL(1,"test") as test; @end example In MySQL 4.0.6 the type for column 'test' is @code{CHAR(4)} while in earlier versions you would get @code{BIGINT}. @findex NULLIF() @item NULLIF(expr1,expr2) @code{expr1 = expr2} が真なら、@code{NULL} を返し、そうでなければ @code{expr1} を返します。 これは @code{CASE WHEN x = y THEN NULL ELSE x END} と同じです: @example mysql> SELECT NULLIF(1,1); -> NULL mysql> SELECT NULLIF(1,2); -> 1 @end example 注意: 引数が等しくない場合、@code{expr1} は MySQL 内部では2回評価されます。 @findex IF() @item IF(expr1,expr2,expr3) @code{expr1} が真 (@code{expr1 <> 0} and @code{expr1 <> NULL}) の場合 @code{expr2} を返し、そうでなければ @code{expr3} を返します。 @code{IF()} はどの文脈で使用されたかにより数値か文字を返します: @example mysql> SELECT IF(1>2,2,3); -> 3 mysql> SELECT IF(1<2,'yes','no'); -> 'yes' mysql> SELECT IF(STRCMP('test','test1'),'no','yes'); -> 'no' @end example If @code{expr2} or @code{expr3} is explicitely @code{NULL} then the result type of the @code{IF()} function is the type of the not @code{NULL} column. (This behaviour is new in MySQL 4.0.3). @code{expr1} は @code{INTEGER} として評価されます。これは浮動小数点を使用する 場合、比較演算も使用すべきであることを意味します: @example mysql> SELECT IF(0.1,1,0); -> 0 mysql> SELECT IF(0.1<>0,1,0); -> 1 @end example 上の最初の例では、 @code{IF(0.1)} は @code{0} を返します。なぜなら @code{0.1} は 整数値として変換され @code{IF(0)} になり、それをもとにしたテスト結果が 返るからです。 これはあなたの期待に添わないかもしれません。 二番目の場合、 比較は、元の浮動小数点値が非ゼロかどうかテストします。 比較結果は整数として使用されます。 @code{IF()} のデフォルトの戻り値型(一時テーブルに格納される時に問題となり ます)は MySQL バージョン 3.23 では次のように計算されます: @multitable @columnfractions .50 .20 @item @strong{Expression} @tab @strong{Return value} @item expr2 または expr3 が文字列を返す @tab 文字列 @item expr2 または expr3 が浮動小数点値を返す @tab 浮動小数点 @item expr2 または expr3 が整数を返す @tab 整数 @end multitable If expr2 and expr3 are strings, then the result is case-insensitive if both strings are case-insensitive. (Starting from 3.23.51) @findex CASE @item CASE value WHEN [compare-value] THEN result [WHEN [compare-value] THEN result ...] [ELSE result] END @item CASE WHEN [condition] THEN result [WHEN [condition] THEN result ...] [ELSE result] END 最初の式は @code{value=compare-value} ならば @code{result} を返します。 二つ目の式では、最初の条件[condition] が真ならば、 @code{result} を返します。 もしマッチする result の値がなければ、 @code{ELSE} 以下の result が返ります。 もし @code{ELSE} 部分がなければ、 @code{NULL} が返ります: @example mysql> SELECT CASE 1 WHEN 1 THEN "one" WHEN 2 THEN "two" ELSE "more" END; -> "one" mysql> SELECT CASE WHEN 1>0 THEN "true" ELSE "false" END; -> "true" mysql> SELECT CASE BINARY "B" WHEN "a" THEN 1 WHEN "b" THEN 2 END; -> NULL @end example @end table 戻り値の型(@code{INTEGER}, @code{DOUBLE}, @code{STRING})は最初に返される値 (最初の @code{THEN} の後の式)の型と同じです。 @node String functions, Numeric Functions, Non-typed Operators, Functions @subsection 文字列関数 @findex string functions @findex functions, string サーバー側のパラメター @code{max_allowed_packet} よりも結果の長さが大きい場合、 文字列関数は @code{NULL} を返します。 @xref{Server parameters}. 文字の位置を扱う関数においては、一番最初の位置は数字の 1 です。 @table @code @findex ASCII() @item ASCII(str) @code{str} の左端の文字の ASCII コード値を返します。 @code{str} が空文字の場合は @code{0} を返します。 @code{str} が @code{NULL} の場合は @code{NULL} を返します: @example mysql> SELECT ASCII('2'); -> 50 mysql> SELECT ASCII(2); -> 50 mysql> SELECT ASCII('dx'); -> 100 @end example See also the @code{ORD()} function. @findex ORD() @item ORD(str) 文字列 str の左端の文字がマルチバイト文字の場合、文字のASCII コード値を次 の形式で返すことにより、マルチバイト文字のコードを返します: @code{((first byte ASCII code)*256+(second byte ASCII code))[*256+third byte ASCII code...]}. 左端の文字がマルチバイト文字でない場合は、@code{ASCII()} 関数と同じ値を返 します: @example mysql> SELECT ORD('2'); -> 50 @end example @findex CONV() @item CONV(N,from_base,to_base) 数字を、進数の違う数字に変換します。 数 @code{N} を @code{from_base} 進数から @code{to_base} 進数に 変換した場合の、文字表現を返します。 もし引数が @code{NULL} なら @code{NULL} を返します。 引数 @code{N} は整数として解釈されますが、整数か文字列で指定します。 最小の進数は @code{2} で、最大は @code{36} です。 @code{to_base} が負数なら、@code{N} は符号付きの数になります。 @code{CONV} は 64-bit 精度で動作します: @example mysql> SELECT CONV("a",16,2); -> '1010' mysql> SELECT CONV("6E",18,8); -> '172' mysql> SELECT CONV(-17,10,-18); -> '-H' mysql> SELECT CONV(10+"10"+'10'+0xa,10,10); -> '40' @end example @findex BIN() @item BIN(N) @code{N} を二進数にした値を返します。@code{N} は longlong 数値です。 これは @code{CONV(N,10,2)} と同じです。 @code{N} が @code{NULL} なら @code{NULL} を返します: @example mysql> SELECT BIN(12); -> '1100' @end example @findex OCT() @item OCT(N) @code{N} の8進数値を表す文字列を返します。@code{N} は longlong 数値です。 これは @code{CONV(N,10,8)} と同じです。@code{N} が @code{NULL} の場合は @code{NULL} を返します: @example mysql> SELECT OCT(12); -> '14' @end example @findex HEX() @item HEX(N_or_S) If N_OR_S is a number, returns a string representation of the hexadecimal value of @code{N}, ここで @code{N} は longlong(@code{BIGINT}) 数値です。これは @code{CONV(N,10,16)} と同じです。 If N_OR_S is a string, returns a hexadecimal string of N_OR_S where each character in N_OR_S is converted to 2 hexadecimal digits. This is the invers of the @code{0xff} strings. @example mysql> SELECT HEX(255); -> 'FF' mysql> SELECT HEX("abc"); -> 616263 mysql> SELECT 0x616263; -> "abc" @end example @findex CHAR() @item CHAR(N,...) 引数の ASCII コード値によって与えられた文字からなる文字列を返します。 @code{NULL} は飛ばされます: @example mysql> SELECT CHAR(77,121,83,81,'76'); -> 'MySQL' mysql> SELECT CHAR(77,77.3,'77.3'); -> 'MMM' @end example @findex CONCAT() @item CONCAT(str1,str2,...) 引数を結合した結果を返します。引数が @code{NULL} なら @code{NULL} を返します. 2個以上の引数を必要とします。 数値の引数は等価の文字列形式に変換されます: @example mysql> SELECT CONCAT('My', 'S', 'QL'); -> 'MySQL' mysql> SELECT CONCAT('My', NULL, 'QL'); -> NULL mysql> SELECT CONCAT(14.3); -> '14.3' @end example @findex CONCAT_WS() @item CONCAT_WS(separator, str1, str2,...) @code{CONCAT_WS()} は区切り文字つき CONCAT (CONCAT With Separator) を意味 し、@code{CONCAT()} の特殊な形式です。最初の引数は、残りの引数の区切り文字 です。区切り文字は残りの引数と同じような文字列です。区切り文字が @code{NULL} の場合、結果は @code{NULL} になります。関数は区切り文字より後 の @code{NULL} と空文字列を飛ばします。区切り文字は結合される文字列の間に 追加されます: @example mysql> SELECT CONCAT_WS(",","First name","Second name","Last Name"); -> 'First name,Second name,Last Name' mysql> SELECT CONCAT_WS(",","First name",NULL,"Last Name"); -> 'First name,Last Name' @end example @findex LENGTH() @findex OCTET_LENGTH() @findex CHAR_LENGTH() @findex CHARACTER_LENGTH() @item LENGTH(str) @itemx OCTET_LENGTH(str) @itemx CHAR_LENGTH(str) @itemx CHARACTER_LENGTH(str) 文字列 @code{str} の長さ: @example mysql> SELECT LENGTH('text'); -> 4 mysql> SELECT OCTET_LENGTH('text'); -> 4 @end example 注意: @code{CHAR_LENGTH()} と @code{CHARACTER_LENGTH()} については、マルチバイト文字は一度だけしかカウントされません。 @findex BIT_LENGTH() @item BIT_LENGTH(str) Returns the length of the string @code{str} in bits: @example mysql> SELECT BIT_LENGTH('text'); -> 32 @end example @findex LOCATE() @findex POSITION() @item LOCATE(substr,str) @itemx POSITION(substr IN str) @code{str} 内にある @code{substr} 文字列の位置を返します。最初の位置は 1 です。 @code{str} 内に @code{substr} がない時は @code{0} を返します: @example mysql> SELECT LOCATE('bar', 'foobarbar'); -> 4 mysql> SELECT LOCATE('xbar', 'foobar'); -> 0 @end example この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string. @findex LOCATE() @item LOCATE(substr,str,pos) 文字列 @code{str} 中に最初に顕れた @code{substr} 文字の位置を返します。 @code{pos} は検索を開始する位置です。 @code{str} に @code{substr} がなければ @code{0} を返します: @example mysql> SELECT LOCATE('bar', 'foobarbar',5); -> 7 @end example この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string. @findex INSTR() @item INSTR(str,substr) 文字列 @code{str} 内の最初の文字列 @code{substr} の位置を返します。 これは引数が入れ替わっていることをのぞいて、 2つの引数を与えた @code{LOCATE} と同じです: @example mysql> SELECT INSTR('foobarbar', 'bar'); -> 4 mysql> SELECT INSTR('xbar', 'foobar'); -> 0 @end example この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string. @findex LPAD() @item LPAD(str,len,padstr) @code{str} の長さが @code{len} になるまで文字列 @code{str} の始めに @code{padstr} を埋めます。 @code{str} が @code{len} よりも長い場合は、@code{len} 文字に短くされます。 @example mysql> SELECT LPAD('hi',4,'??'); -> '??hi' @end example @findex RPAD() @item RPAD(str,len,padstr) @code{str} の長さが @code{len} になるまで文字列 @code{str} の終わりに @code{padstr} を埋めます。 @code{str} が @code{len} よりも長い場合は、@code{len} 文字に短くされます。 @example mysql> SELECT RPAD('hi',5,'?'); -> 'hi???' @end example @findex LEFT() @item LEFT(str,len) 文字列 @code{str} の最初から @code{len} 個の文字を得ます: @example mysql> SELECT LEFT('foobarbar', 5); -> 'fooba' @end example この関数はマルチバイトでも安全です。 @findex RIGHT() @item RIGHT(str,len) 文字列 @code{str} の最後から @code{len} 個の文字を得ます: @example mysql> SELECT RIGHT('foobarbar', 4); -> 'rbar' @end example この関数はマルチバイトでも安全です。 @findex SUBSTRING() @findex MID() @item SUBSTRING(str,pos,len) @itemx SUBSTRING(str FROM pos FOR len) @itemx MID(str,pos,len) @code{str} の @code{pos} 位置から @code{len} 文字数分の文字列を返します。 @code{FROM} の違いは ANSI SQL 92 構文です: @example mysql> SELECT SUBSTRING('Quadratically',5,6); -> 'ratica' @end example この関数はマルチバイトでも安全です。 @findex SUBSTRING() @item SUBSTRING(str,pos) @item SUBSTRING(str FROM pos) 文字列 @code{str} の 位置 @code{pos} 以降の文字を返します: @example mysql> SELECT SUBSTRING('Quadratically',5); -> 'ratically' mysql> SELECT SUBSTRING('foobarbar' FROM 4); -> 'barbar' @end example この関数はマルチバイトでも安全です。 @findex SUBSTRING_INDEX() @item SUBSTRING_INDEX(str,delim,count) @code{str} から、区切り文字 @code{delim} が @code{count} 個現れた位置から前の 文字列を返します。@code{count} が正の場合は文字列は左から検索され、 @code{count} が負の場合は文字列は右から検索されます: @example mysql> SELECT SUBSTRING_INDEX('www.mysql.com', '.', 2); -> 'www.mysql' mysql> SELECT SUBSTRING_INDEX('www.mysql.com', '.', -2); -> 'mysql.com' @end example この関数はマルチバイトでも安全です。 @findex LTRIM() @item LTRIM(str) 文字列 @code{str} の最初から空白文字を削除します: @example mysql> SELECT LTRIM(' barbar'); -> 'barbar' @end example @findex RTRIM() @item RTRIM(str) 文字列 @code{str} の最後から空白文字を削除します: @example mysql> SELECT RTRIM('barbar '); -> 'barbar' @end example この関数はマルチバイトでも安全です。 @findex TRIM() @item TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str) 全ての @code{remstr} プレフィックスまたはサフィックスを @code{str} から削除した 文字列を返します。@code{BOTH}, @code{LEADING} そして @code{TRAILING} が 使用されない場合、@code{BOTH} が適用されます。@code{remstr} が与えられないと、 空白が削除されます: @example mysql> SELECT TRIM(' bar '); -> 'bar' mysql> SELECT TRIM(LEADING 'x' FROM 'xxxbarxxx'); -> 'barxxx' mysql> SELECT TRIM(BOTH 'x' FROM 'xxxbarxxx'); -> 'bar' mysql> SELECT TRIM(TRAILING 'xyz' FROM 'barxxyz'); -> 'barx' @end example This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string. @findex SOUNDEX() @item SOUNDEX(str) @code{str} からの soundex 文字列を返します。発音が``大体同じ''２つの文字列 は同じ soundex 文字列を持ちます。``標準の'' soundex 文字列は4文字長ですが、 @code{SOUNDEX()} 関数は任意の長さの文字列を返します。@code{SUBSTRING()} を 結果に使用して、``標準の'' soundex 文字列を得ることができます。与えられた 文字列中の非アルファベット文字は無視されます。A-Z の半以外のすべての国際的 なアルファベット文字は母音とみなされます: @example mysql> SELECT SOUNDEX('Hello'); -> 'H400' mysql> SELECT SOUNDEX('Quadratically'); -> 'Q36324' @end example @findex SPACE() @item SPACE(N) @code{N} 個の空白文字を返します: @example mysql> SELECT SPACE(6); -> ' ' @end example @findex REPLACE() @item REPLACE(str,from_str,to_str) 文字列 @code{str} 内の全ての文字列 @code{from_str} を @code{to_str} に 置き換えます: @example mysql> SELECT REPLACE('www.mysql.com', 'w', 'Ww'); -> 'WwWwWw.mysql.com' @end example この関数はマルチバイトでも安全です。 @findex REPEAT() @item REPEAT(str,count) @code{str} を @code{count} 回繰り返します。@code{count <= 0} の場合は 空の文字列を返します。@code{str} または @code{count} が @code{NULL} または、@code{LENGTH(str)*count > max_allowed_packet} の場合は @code{NULL} を返します: @example mysql> SELECT REPEAT('MySQL', 3); -> 'MySQLMySQLMySQL' @end example @findex REVERSE() @item REVERSE(str) 文字列 @code{str} を反転します: @example mysql> SELECT REVERSE('abc'); -> 'cba' @end example この関数はマルチバイトでも安全です。 @findex INSERT() @item INSERT(str,pos,len,newstr) @code{str} 中の @code{pos} 位置から @code{len} 長の文字列を @code{newstr} で置き換えます。@code{str} 内の最初の位置は1です: @example mysql> SELECT INSERT('Quadratic', 3, 4, 'What'); -> 'QuWhattic' @end example この関数はマルチバイトでも安全です。 @findex ELT() @item ELT(N,str1,str2,str3,...) @code{N} = @code{1} なら @code{str1} を、@code{N} = @code{2} なら @code{str2} を 返します。 @code{N} が @code{1} より小さい場合、または引数の数より大きい場合は @code{NULL} が返されます。 @code{ELT()} は @code{FIELD()} の逆です: @example mysql> SELECT ELT(1, 'ej', 'Heja', 'hej', 'foo'); -> 'ej' mysql> SELECT ELT(4, 'ej', 'Heja', 'hej', 'foo'); -> 'foo' @end example @findex FIELD() @item FIELD(str,str1,str2,str3,...) @code{str1}, @code{str2}, @code{str3}, @code{...} リスト内の @code{str} のインデ ックスを 返します。@code{str} が見つからなければ @code{0} を返します。 @code{FIELD()} は @code{ELT()} の逆です: @example mysql> SELECT FIELD('ej', 'Hej', 'ej', 'Heja', 'hej', 'foo'); -> 2 mysql> SELECT FIELD('fo', 'Hej', 'ej', 'Heja', 'hej', 'foo'); -> 0 @end example @findex FIND_IN_SET() @item FIND_IN_SET(str,strlist) @code{str} が @code{strlist} 中にあれば、値 @code{1} から @code{N} を返します。 @code{strlist} は、それぞれの異なる値が ',' で分割された文字列です。最初の 引数が定数文字列で２番目が @code{SET} 型のフィールドの場合@code{FIND_IN_SET} は ビット演算を使用して最適化されます！ @code{strlist} が空文字なら @code{0} を返します。 どちらかの引数が @code{NULL} なら @code{NULL} を返します. この関数は最初の引数が ',' を含んだ場合、うまく動かないでしょう: @example mysql> SELECT FIND_IN_SET('b','a,b,c,d'); -> 2 @end example @findex MAKE_SET() @item MAKE_SET(bits,str1,str2,...) @code{bits} に指定されたビットに対応する文字列のセットを返します。 (文字列が複数の場合、 @samp{,} で区切られます) @code{str1} が ビット 0 に対応し、@code{str2} が ビット 1 に対応し、 @code{str3} が ビット 2 に対応し... となります。 @code{str1}, @code{str2}, @code{...} 中に含まれている @code{NULL} 文字は 結果には追加されません: @example mysql> SELECT MAKE_SET(1,'a','b','c'); -> 'a' mysql> SELECT MAKE_SET(1 | 4,'hello','nice','world'); -> 'hello,world' mysql> SELECT MAKE_SET(0,'a','b','c'); -> '' @end example @findex EXPORT_SET() @item EXPORT_SET(bits,on,off,[separator,[number_of_bits]]) 'bits' に与えられた数値に対し、 全てのセットされているビットを 'on' で指定された文字で表し、 リセットされているビットを 'off' で指定された文字で表した文字列を返します。 それぞれの文字は 'separator' (デフォルト',') で示された文字で区切られ、 'number_of_bits' (default 64) に与えられた桁数だけのビットを表示します: @example mysql> SELECT EXPORT_SET(5,'Y','N',',',4) -> Y,N,Y,N @end example @findex LCASE() @findex LOWER() @item LCASE(str) @itemx LOWER(str) @code{str} を現在のキャラクターセットマッピング (デフォルト ISO-8859-1 Latin1) にしたがって小文字に変換します: @example mysql> SELECT LCASE('QUADRATICALLY'); -> 'quadratically' @end example This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string. @findex UCASE() @findex UPPER() @item UCASE(str) @itemx UPPER(str) @code{str} を現在のキャラクターセットマッピング (デフォルト ISO-8859-1 Latin1) にしたがって大文字に変換します: @example mysql> SELECT UCASE('Hej'); -> 'HEJ' @end example This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string. @findex FILE @findex LOAD_FILE() @item LOAD_FILE(file_name) ファイルを読み込み、ファイルの中身を文字として返します。 ファイルは サーバー上になくてはならず、ファイルをフルパスで指定しなければなりません。 そして、 @code{FILE} 権限がなければなりません。 ファイルは全員に 読み込み可能でなければならず、そして、 @code{max_allowed_packet} より 小さいサイズでなければなりません。 このうちどれかの理由で、もしファイルが存在しないか読み込めない場合、 この関数は @code{NULL} を返します: @example mysql> UPDATE tbl_name SET blob_column=LOAD_FILE("/tmp/picture") WHERE id=1; @end example @strong{MySQL 3.23} を使用していない場合、あなたのアプリケーション内部でファ イルを読み込んで、ファイル情報でデータベースを更新するための @code{INSERT} ステートメントを生成する必要があります。これを行なう一つの方 法は、MySQL++ ライブラリを使用する場合、 @uref{http://www.mysql.com/documentation/mysql++/mysql++-examples.html} で 見つけられます。 @findex QUOTE() @item QUOTE(str) Quotes a string to produce a result that can be used as a properly-escaped data value in a SQL statement. The string is returned surrounded by single quotes and with each instance of single quote (@samp{'}), backslash (@samp{\}), ASCII NUL, and Control-Z preceded by a backslash. If the argument is @code{NULL}, the return value is the word ``NULL'' without surrounding single quotes. @example mysql> SELECT QUOTE("Don't"); -> 'Don\'t!' mysql> SELECT QUOTE(NULL); -> NULL @end example @end table @menu * String comparison functions:: String Comparison Functions * Case Sensitivity Operators:: Case-Sensitivity @end menu @node String comparison functions, Case Sensitivity Operators, String functions, String functions @subsubsection String Comparison Functions @findex string comparison functions @findex functions, string comparison MySQL は必要とあらば数値を文字列に変換します。 逆も同様に行います： @example mysql> SELECT 1+"1"; -> 2 mysql> SELECT CONCAT(2,' test'); -> '2 test' @end example 明示的に数値を文字列に変換したければ、@code{CONCAT()} に引数として渡して下 さい。 文字列関数は引数としてバイナリ文字列が与えられると、結果の文字列もバイナリ 文字列になります。文字列に変換された数値はバイナリ文字列とみなされます。こ れは比較にだけ影響します。 @cindex case-sensitivity, in string comparisons @cindex string comparisons, case-sensitivity 通常、比較される表現がケース依存でない場合、比較はケース非依存で行われます。 @table @code @findex LIKE @item expr LIKE pat [ESCAPE 'escape-char'] SQL の簡単な正規表現比較です。@code{1} (TRUE) または @code{0} (FALSE) を返します 。 @code{LIKE} には2つのワイルドカードがあります: @multitable @columnfractions .10 .60 @item @strong{Char} @tab @strong{Description} @item @code{%} @tab 任意の数の文字(0文字も含む)に適合します。 @item @code{_} @tab 厳密に1つの文字に適合します。 @end multitable @example mysql> SELECT 'David!' LIKE 'David_'; -> 1 mysql> SELECT 'David!' LIKE '%D%v%'; -> 1 @end example ワイルドカード文字のテストをするためには、エスケープ文字より先行しておこなって ください。 @code{ESCAPE} を指定しない場合は、文字 @samp{\} が使われます: @multitable @columnfractions .10 .60 @item @strong{String} @tab @strong{Description} @item @code{\%} @tab 1つの @code{%} に適合します。 @item @code{\_} @tab 1つの @code{_} に適合します。 @end multitable @example mysql> SELECT 'David!' LIKE 'David\_'; -> 0 mysql> SELECT 'David_' LIKE 'David\_'; -> 1 @end example 違うエスケープ文字を指定するには、 @code{ESCAPE} 節を使用します: @example mysql> SELECT 'David_' LIKE 'David|_' ESCAPE '|'; -> 1 @end example 次の２つのステートメントは、オペランドの一つがバイナリ文字列でなければ、文 字列比較がケース非依存であることを示しています: @example mysql> SELECT 'abc' LIKE 'ABC'; -> 1 mysql> SELECT 'abc' LIKE BINARY 'ABC'; -> 0 @end example @code{LIKE} は数値表現でも許されます！ (これは MySQL の、ANSI SQL @code{LIKE} に対する拡張です) 注意： MySQL は文字列中に C のエスケープ文字を使用しているので(e.g., @samp{\n}), @code{LIKE} の指定文字列として使用するには @samp{\} を 二倍しなくてはなりません。 例えば、 @samp{\n} を探すには、@samp{\\n} と 記述します。 @samp{\} を探すには、 @samp{\\\\} (バックスラッシュは、 一つはパーサーに取り除かれ、パターンマッチが行われる際にもうひとつ 取り除かれ、一致を探すために残った一つのバックスラッシュが使用されます) @findex NOT LIKE @item expr NOT LIKE pat [ESCAPE 'escape-char'] @code{NOT (expr LIKE pat [ESCAPE 'escape-char'])} と同じ @findex SOUNDS LIKE @item expr SOUNDS LIKE expr Same as @code{SOUNDEX(expr)=SOUNDEX(expr)} (available only in version 4.1 or later). @cindex mSQL compatibility @cindex compatibility, with mSQL @findex REGEXP @findex RLIKE @item expr REGEXP pat @itemx expr RLIKE pat パターン @code{pat} に対し、文字式 @code{expr} のパターンマッチを行います。 パターン @code{pat} は正規表現の拡張が使用できます。@xref{Regexp}. もし @code{expr} が @code{pat} にマッチするなら @code{1} を返し、 でなければ @code{0} を返します。 @code{RLIKE} は @code{REGEXP} と同義で、@code{mSQL} 互換を提供します。 注意: MySQL は C エスケープ構文を文字中に使用しており(@code{\n})、 @code{REGEXP} 中で使用される @code{'\'} 文字はすべて、二重に書かなければ なりません。 MySQL 3.23.4 @code{REGEXP} は、普通の文字 (not binary) はケース非依存で す: @example mysql> SELECT 'Monty!' REGEXP 'm%y%%'; -> 0 mysql> SELECT 'Monty!' REGEXP '.*'; -> 1 mysql> SELECT 'new*\n*line' REGEXP 'new\\*.\\*line'; -> 1 mysql> SELECT "a" REGEXP "A", "a" REGEXP BINARY "A"; -> 1 0 mysql> SELECT "a" REGEXP "^[a-d]"; -> 1 @end example @code{REGEXP} and @code{RLIKE} は、文字の型を決定する場合、 カレントのキャラクターセットを使用します。 (ISO-8859-1 Latin1 がデフォルト) @findex NOT REGEXP @item expr NOT REGEXP pat @itemx expr NOT RLIKE pat @code{NOT (expr REGEXP pat)} と同じ. @findex STRCMP() @item STRCMP(expr1,expr2) @code{STRCMP()} 文字列が同じなら @code{0} を返します。そうでなければ、最初の引数がソート順で小 さければ @code{-1} を返します。そうでなければ @code{1} を返します: @example mysql> SELECT STRCMP('text', 'text2'); -> -1 mysql> SELECT STRCMP('text2', 'text'); -> 1 mysql> SELECT STRCMP('text', 'text'); -> 0 @end example @findex MATCH ... AGAINST() @item MATCH (col1,col2,...) AGAINST (expr) @code{MATCH ... AGAINST()} は全文検索に使用され、妥当性を返します。フィー ルド @code{(col1,col2,...)} 内のテキストとクエリ @code{expr} との間の類似 点を評価します。妥当性は正の浮動小数点数です。妥当性 0 は類似点なしを意味 します。@code{MATCH ... AGAINST()} が動作するためには、最初に @strong{FULLTEXT} インデックスが作成する必要があります。 @xref{CREATE TABLE, , @code{CREATE TABLE}}。 @code{MATCH ... AGAINST()} は MySQL 3.23.23 以上のバージョンで有 効です。 @code{IN BOOLEAN MODE} extension was added in version 4.0.1. 詳細と使用例は @ref{Fulltext Search}. @end table @node Case Sensitivity Operators, , String comparison functions, String functions @subsubsection Case-Sensitivity @findex casts @cindex cast operators @cindex operators, cast @table @code @findex BINARY @item @code{BINARY} @code{BINARY} 演算子は、これ以降に続く文字をバイナリにキャストします。 これはたとえフィールドが @code{BINARY} や @code{BLOB} 定義でなくても、 ケース依存でフィールドを比較することが出来る簡単な方法です: @example mysql> SELECT "a" = "A"; -> 1 mysql> SELECT BINARY "a" = "A"; -> 0 @end example @code{BINARY string} is a shorthand for @code{CAST(string AS BINARY)}. @xref{Cast Functions}. @code{BINARY} は MySQL 3.23.0 で登場しました。 注意: いくつかの文脈では、インデックスされたフィールドを @code{BINARY} に キャストした時、MySQL はインデックスを効率よく使用できません。 @end table BLOB をケース非依存で比較したい場合、比較を行なう前に BLOB を常に大文字に 変換します: @example SELECT 'A' LIKE UPPER(blob_col) FROM table_name; @end example より柔軟に文字列を比較するために、我々は間もなく異なる文字セット間のキャス トを導入する予定です。 @node Numeric Functions, Date and time functions, String functions, Functions @subsection Numeric Functions @menu * Arithmetic functions:: Arithmetic Operations * Mathematical functions:: Mathematical Functions @end menu @node Arithmetic functions, Mathematical functions, Numeric Functions, Numeric Functions @subsubsection 算術演算 @cindex operators, cast 普通の算術演算が有効です。 @code{-}, @code{+}, @code{*} は、二つの引数が正数ならば @code{BIGINT} (64bit精度) で計算されることに注意してください！ If one of the argument is an unsigned integer, and the other argument is also an integer, the result will be an unsigned integer. @xref{Cast Functions}. @cindex operations, arithmetic @cindex arithmetic expressions @table @code @findex + (addition) @findex addition (+) @item + 足し算: @example mysql> SELECT 3+5; -> 8 @end example @findex - (subtraction) @findex subtraction (-) @item - 引き算: @example mysql> SELECT 3-5; -> -2 @end example @findex * (multiplication) @findex multiplication (*) @item * 掛け算: @example mysql> SELECT 3*5; -> 15 mysql> SELECT 18014398509481984*18014398509481984.0; -> 324518553658426726783156020576256.0 mysql> SELECT 18014398509481984*18014398509481984; -> 0 @end example 最後の式の結果は不当です。なぜなら結果は @code{BIGINT} の 64 ビットを超えた整数だからです。 @findex / (division) @findex division (/) @item / 割り算: @example mysql> SELECT 3/5; -> 0.60 @end example 0 で割った場合、@code{NULL} になります。 @example mysql> SELECT 102/(1-1); -> NULL @end example 演算結果が整数になる場合にだけ、 @code{BIGINT} を用いて割り算は計算されます。 @end table @node Mathematical functions, , Arithmetic functions, Numeric Functions @subsubsection 数学関数 すべての数学関数はエラーの場合 @code{NULL} を返します。 @findex mathematical functions @findex functions, mathematical @table @code @findex - (unary minus) @findex minus, unary (-) @findex unary minus (-) @item - 符号。引数の符号を変更します: @example mysql> SELECT - 2; -> -2 @end example このオペレーターが @code{BIGINT} とともに使用された場合、 返り値は @code{BIGINT} であることに注意してください! これは @code{-2^63} の値を 持つかもしれない整数を、 @code{-} で使用してはならないことを意味します！ @findex ABS() @item ABS(X) Returns the absolute value of @code{X}: @example mysql> SELECT ABS(2); -> 2 mysql> SELECT ABS(-32); -> 32 @end example この関数は @code{BIGINT} 値とともに使用されると安全です。 @findex SIGN() @item SIGN(X) @code{X} が負数、ゼロ、整数によって、 @code{-1}, @code{0} or @code{1} を 返します: @example mysql> SELECT SIGN(-32); -> -1 mysql> SELECT SIGN(0); -> 0 mysql> SELECT SIGN(234); -> 1 @end example @findex MOD() @findex % (modulo) @findex modulo (%) @item MOD(N,M) @itemx % 剰余 ( C の @code{%} 演算子のような ). @code{N} を @code{M} で割ったときの余りが返ります: @example mysql> SELECT MOD(234, 10); -> 4 mysql> SELECT 253 % 7; -> 1 mysql> SELECT MOD(29,9); -> 2 @end example この関数は @code{BIGINT} 値でも安全に使用できます。 @findex FLOOR() @item FLOOR(X) @code{X} より大きくならない整数のうち、最大の整数値を返します: @example mysql> SELECT FLOOR(1.23); -> 1 mysql> SELECT FLOOR(-1.23); -> -2 @end example 返り値は @code{BIGINT} に変換されていることに注意! @findex CEILING() @item CEILING(X) @code{X} より小さくならない整数のうち、最小の整数値を返します. @example mysql> SELECT CEILING(1.23); -> 2 mysql> SELECT CEILING(-1.23); -> -1 @end example 返り値は @code{BIGINT} に変換されていることに注意! @findex ROUND() @item ROUND(X) @code{X} を整数に丸めた値(四捨五入)を返します: @example mysql> SELECT ROUND(-1.23); -> -1 mysql> SELECT ROUND(-1.58); -> -2 mysql> SELECT ROUND(1.58); -> 2 @end example 引数が２つの整数間の半分時の @code{ROUND()} の振る舞いは、C ライブラリの実 装に依存します。いくつかは、近い偶数値、常に上、常に下、または常に０方向に 丸めます。丸めの種類の一つを必要とする場合は、@code{TRUNCATE()} または @code{FLOOR()} のようなはっきりと定義された関数を代わりに使用すべきです。 @findex ROUND() @item ROUND(X,D) @code{X} を @code{D} で指定した少数桁に丸めた値(四捨五入)を返します。 もし @code{D} が @code{0} なら, 結果は小数点無しになるか 少数部分になるでしょう: @example mysql> SELECT ROUND(1.298, 1); -> 1.3 mysql> SELECT ROUND(1.298, 0); -> 1 @end example @findex EXP() @item EXP(X) 指数関数 : @code{e} (自然対数の底) の @code{X} 乗: @example mysql> SELECT EXP(2); -> 7.389056 mysql> SELECT EXP(-2); -> 0.135335 @end example @findex LN() @item LN(X) Returns the natural logarithm of @code{X}: @example mysql> SELECT LN(2); -> 0.693147 mysql> SELECT LN(-2); -> NULL @end example This function was added in MySQL version 4.0.3. It is synonymous with @code{LOG(X)} in MySQL. @findex LOG() @item LOG(X) @itemx LOG(B,X) 自然対数 @code{X}: If called with one parameter, this function returns the natural logarithm of @code{X}: @example mysql> SELECT LOG(2); -> 0.693147 mysql> SELECT LOG(-2); -> NULL @end example 任意の底 @code{B} に対する @code{X} の対数を得たければ、公式 @code{LOG(X)/LOG(B)} を使用してください。 If called with two parameters, this function returns the logarithm of @code{X} for an arbitary base @code{B}: @example mysql> SELECT LOG(2,65536); -> 16.000000 mysql> SELECT LOG(1,100); -> NULL @end example The arbitrary base option was added in MySQL version 4.0.3. @code{LOG(B,X)} is equivalent to @code{LOG(X)/LOG(B)}. @findex LOG2() @item LOG2(X) Returns the base-2 logarithm of @code{X}: @example mysql> SELECT LOG2(65536); -> 16.000000 mysql> SELECT LOG2(-100); -> NULL @end example @code{LOG2()} is useful for finding out how many bits a number would require for storage. This function was added in MySQL version 4.0.3. In earlier versions, you can use @code{LOG(X)/LOG(2)} instead. @findex LOG10() @item LOG10(X) 常用対数(10を底とした対数) @code{X}: @example mysql> SELECT LOG10(2); -> 0.301030 mysql> SELECT LOG10(100); -> 2.000000 mysql> SELECT LOG10(-100); -> NULL @end example @findex POW() @findex POWER() @item POW(X,Y) @itemx POWER(X,Y) @code{X} の @code{Y} 乗: @example mysql> SELECT POW(2,2); -> 4.000000 mysql> SELECT POW(2,-2); -> 0.250000 @end example @findex SQRT() @item SQRT(X) @code{X} の非負の平方根を返します: @example mysql> SELECT SQRT(4); -> 2.000000 mysql> SELECT SQRT(20); -> 4.472136 @end example @findex PI() @item PI() π の値を返します。デフォルトの表示桁数は 5 ですが、MySQL 内部で は π に完全な倍精度を使用します。 @example mysql> SELECT PI(); -> 3.141593 mysql> SELECT PI()+0.000000000000000000; -> 3.141592653589793116 @end example @findex COS() @item COS(X) コサイン @code{X}。@code{X} はラジアン: @example mysql> SELECT COS(PI()); -> -1.000000 @end example @findex SIN() @item SIN(X) サイン @code{X}。@code{X} はラジアン: @example mysql> SELECT SIN(PI()); -> 0.000000 @end example @findex TAN() @item TAN(X) タンジェント @code{X}。@code{X} はラジアン: @example mysql> SELECT TAN(PI()+1); -> 1.557408 @end example @findex ACOS() @item ACOS(X) @code{X} のアークコサインを返します。これはコサインが @code{X} である値で す。@code{X} が @code{-1} から @code{1} の範囲にない場合は @code{NULL} を 返します: @example mysql> SELECT ACOS(1); -> 0.000000 mysql> SELECT ACOS(1.0001); -> NULL mysql> SELECT ACOS(0); -> 1.570796 @end example @findex ASIN() @item ASIN(X) @code{X} のアークサインを返します。これはサインが @code{X} である値です。 @code{X} が @code{-1} から @code{1} の範囲にない場合は @code{NULL} を返し ます: @example mysql> SELECT ASIN(0.2); -> 0.201358 mysql> SELECT ASIN('foo'); -> 0.000000 @end example @findex ATAN() @item ATAN(X) @code{X} のアークタンジェントを返します。これはタンジェントが @code{X} で ある値です: @example mysql> SELECT ATAN(2); -> 1.107149 mysql> SELECT ATAN(-2); -> -1.107149 @end example @findex ATAN2() @item ATAN(Y,X) @itemx ATAN2(Y,X) ２つの変数 @code{X} と @code{Y} のアークタンジェントを返します。両方の引数 の符号が結果の象限を決定するために使用されることを除いて、@code{Y / X} の アークタンジェントの計算と同様です: @example mysql> SELECT ATAN(-2,2); -> -0.785398 mysql> SELECT ATAN2(PI(),0); -> 1.570796 @end example @findex COT() @item COT(X) @code{X} のコタンジェントを返します: @example mysql> SELECT COT(12); -> -1.57267341 mysql> SELECT COT(0); -> NULL @end example @findex RAND() @item RAND() @itemx RAND(N) @code{0} から @code{1.0} 間のランダムな浮動小数点数値を返します。 もし @code{N} に整数を与えた場合、シードとしてこの値が使用されます: @example mysql> SELECT RAND(); -> 0.9233482386203 mysql> SELECT RAND(20); -> 0.15888261251047 mysql> SELECT RAND(20); -> 0.15888261251047 mysql> SELECT RAND(); -> 0.63553050033332 mysql> SELECT RAND(); -> 0.70100469486881 @end example @code{RAND()} 値を持つフィールドは @code{ORDER BY} 節で使用できません。 @code{ORDER BY} はフィールドを複数回評価するためです。 しかし MySQL バージョン 3.23 では, 次が可能です: @code{SELECT * FROM table_name ORDER BY RAND()} これは @code{SELECT * FROM table1,table2 WHERE a=b AND c SELECT LEAST(2,0); -> 0 mysql> SELECT LEAST(34.0,3.0,5.0,767.0); -> 3.0 mysql> SELECT LEAST("B","A","C"); -> "A" @end example バージョン 3.22.5 以前の MySQL では、@code{MIN()} を @code{LEAST} の代 わりに使用できます。 @findex GREATEST() @item GREATEST(X,Y,...) 二つ以上の引数を取り、引数中、最大の値を返します。 引数は @code{LEAST} の時と同じように比較されます。 @example mysql> SELECT GREATEST(2,0); -> 2 mysql> SELECT GREATEST(34.0,3.0,5.0,767.0); -> 767.0 mysql> SELECT GREATEST("B","A","C"); -> "C" @end example バージョン 3.22.5 以前の MySQL では、@code{MAX()} を @code{GREATEST} の 代わりに使用できます。 @findex DEGREES() @item DEGREES(X) 引数 @code{X} をラジアンから度に変換して返します: @example mysql> SELECT DEGREES(PI()); -> 180.000000 @end example @findex RADIANS() @item RADIANS(X) 引数 @code{X} を度からラジアンに変換して返します: @example mysql> SELECT RADIANS(90); -> 1.570796 @end example @findex TRUNCATE() @item TRUNCATE(X,D) 少数点以下 @code{D} 桁で @code{X} を切り捨てた値を返します。 @code{D} が @code{0} の場合、結果は小数部や微小部を持ちません: @example mysql> SELECT TRUNCATE(1.223,1); -> 1.2 mysql> SELECT TRUNCATE(1.999,1); -> 1.9 mysql> SELECT TRUNCATE(1.999,0); -> 1 mysql> SELECT TRUNCATE(-1.999,1); -> -1.9 @end example Starting from MySQL 3.23.51 all numbers are rounded towards zero. If @code{D} is negative, then the whole part of the number is zeroed out: @example mysql> SELECT TRUNCATE(122,-2); -> 100 @end example 注意: コンピュータでは小数点数は正確な数値としては格納されず、double 値と して格納されます。次の結果によってだまされるでしょう: @cindex rounding errors @example mysql> SELECT TRUNCATE(10.28*100,0); -> 1027 @end example 上記は 10.28 は実際には 10.2799999999999999 のようなものとして格納さえるた めに発生します。 @end table @node Date and time functions, Cast Functions, Numeric Functions, Functions @subsection 日付と時刻関数 @findex date and time functions @findex functions, date and time それぞれの型がもつ値の範囲と日と時間の値が記述される有効な形式については @ref{Date and time types}. 日付関数を使用する例: @code{date_col} が最新の30日である全てのレコードを選択します: @example mysql> SELECT something FROM table WHERE TO_DAYS(NOW()) - TO_DAYS(date_col) <= 30; @end example @table @code @findex DAYOFWEEK() @item DAYOFWEEK(date) Returns the weekday index @code{date} の曜日を得ます (@code{1} = 日曜日, @code{2} = 月曜日, ... @code{7} = 土曜日) これは ODBC 標準に従います: @example mysql> SELECT DAYOFWEEK('1998-02-03'); -> 3 @end example @findex WEEKDAY() @item WEEKDAY(date) @code{date} の曜日を得ます (@code{0} = 月曜日, @code{1} = 火曜日, ... @code{6} = 日曜日): @example mysql> SELECT WEEKDAY('1998-02-03 22:23:00'); -> 1 mysql> SELECT WEEKDAY('1997-11-05'); -> 2 @end example @findex DAYOFMONTH() @item DAYOFMONTH(date) 月の日を返します (@code{1} - @code{31}): @example mysql> SELECT DAYOFMONTH('1998-02-03'); -> 3 @end example @findex DAYOFYEAR() @item DAYOFYEAR(date) 年の日を返します (@code{1}-@code{366}): @code{366}: @example mysql> SELECT DAYOFYEAR('1998-02-03'); -> 34 @end example @findex MONTH() @item MONTH(date) 月を返します (@code{1} - @code{12}): @example mysql> SELECT MONTH('1998-02-03'); -> 2 @end example @findex DAYNAME() @item DAYNAME(date) 曜日の名前を返します: @example mysql> SELECT DAYNAME("1998-02-05"); -> 'Thursday' @end example @findex MONTHNAME() @item MONTHNAME(date) 月の名前を返します: @example mysql> SELECT MONTHNAME("1998-02-05"); -> 'February' @end example @findex QUARTER() @item QUARTER(date) @code{date} についての年の四半期を返します。範囲は @code{1} から @code{4} です: @example mysql> SELECT QUARTER('98-04-01'); -> 2 @end example @findex WEEK() @item WEEK(date) @itemx WEEK(date,first) 引数が一つの場合、@code{date} についての週を返します。範囲は @code{0} から @code{53} (そう、53週の最初というのもありえます)で、日曜日が週の 最初の日です。 引数が二つの形式の @code{WEEK()} は、週の開始を日曜日か月曜日か指定できます。 それぞれの場合の返り値は @code{0-53} か @code{1-52} です。 Here is a table for how the second arguments work: @multitable @columnfractions .25 .45 @item @strong{Value} @tab @code{Meaning} @item 0 @tab Week starts on Sunday and return value is in range 0-53 @item 1 @tab Week starts on Monday and return value is in range 0-53 @item 2 @tab Week starts on Sunday and return value is in range 1-53 @item 3 @tab Week starts on Monday and return value is in range 1-53 (ISO 8601) @end multitable @example mysql> SELECT WEEK('1998-02-20'); -> 7 mysql> SELECT WEEK('1998-02-20',0); -> 7 mysql> SELECT WEEK('1998-02-20',1); -> 8 mysql> SELECT WEEK('1998-12-31',1); -> 53 @end example Note: in Version 4.0, @code{WEEK(#,0)} was changed to match the calendar in the USA. Note that if a week is the last week of the previous year, MySQL will return 0 if you don't use 2 or 3 as the optional argument: @example mysql> SELECT YEAR('2000-01-01'), WEEK('2000-01-01',0); -> 2000, 0 mysql> SELECT WEEK('2000-01-01',2); -> 52 @end example One could argue that MySQL should return @code{52} for the @code{WEEK()} function as the given date is actually the 52 second week of 1999. We decided to return 0 instead as we want the function to return 'the week number in the given year'. This makes the usage of the @code{WEEK()} function reliable when combined with other functions that extracts a date part from a date. If you would prefer to know the correct year-week, then you should use the 2 or 3 as the optional argument or use the @code{YEARWEEK()} function: @example mysql> SELECT YEARWEEK('2000-01-01'); -> 199952 mysql> SELECT MID(YEARWEEK('2000-01-01'),5,2); -> 52 @end example @findex YEAR() @item YEAR(date) 年を返します (@code{1000} - @code{9999}): @example mysql> SELECT YEAR('98-02-03'); -> 1998 @end example @item YEARWEEK(date) @itemx YEARWEEK(date,first) データの年と週を返します。第2引数は @code{WEEK()} の第2引数とまったく同じ ように働きます。注意: 年の最初と最後の週では、年が date 引数内の年とは異な ることがあります！ @example mysql> SELECT YEARWEEK('1987-01-01'); -> 198653 @end example Note that the week number is different from what the @code{WEEK()} function would return (@code{0}) for optional arguments 0 or 1, as @code{WEEK()} then returns the week in the context of the given year. @findex HOUR() @item HOUR(time) 時を返します (@code{0} - @code{23}): @example mysql> SELECT HOUR('10:05:03'); -> 10 @end example @findex MINUTE() @item MINUTE(time) 分を返します (@code{0}-@code{59}): @example mysql> SELECT MINUTE('98-02-03 10:05:03'); -> 5 @end example @findex SECOND() @item SECOND(time) 秒を返します (@code{0} to @code{59}) @example mysql> SELECT SECOND('10:05:03'); -> 3 @end example @findex PERIOD_ADD() @item PERIOD_ADD(P,N) @code{N} 月を期間 @code{P} (型 @code{YYMM} または @code{YYYYMM}) に追加 します。@code{YYYYMM} を返します。 注意: 期間引数 @code{P} は日付値では @strong{ありません}。 @example mysql> SELECT PERIOD_ADD(9801,2); -> 199803 @end example @findex PERIOD_DIFF() @item PERIOD_DIFF(P1,P2) 期間 @code{P1} と @code{P2} の差の月を返します。@code{P1} と @code{P2} は形 式 @code{YYMM} または @code{YYYYMM} です。 注意: 期間引数 @code{P1} と @code{P2} は日付値では @strong{ありません}。 @example mysql> SELECT PERIOD_DIFF(9802,199703); -> 11 @end example @findex DATE_ADD() @findex DATE_SUB() @findex ADDDATE() @findex SUBDATE() @findex EXTRACT() @item DATE_ADD(date,INTERVAL expr type) @itemx DATE_SUB(date,INTERVAL expr type) @itemx ADDDATE(date,INTERVAL expr type) @itemx SUBDATE(date,INTERVAL expr type) これら関数は日付の演算に使用します。 これらは MySQL バージョン 3.22 の 新しい機能です。 @code{ADDDATE()} と @code{SUBDATE()} は @code{DATE_ADD()} , @code{DATE_SUB()} と同義です。 MySQL バージョン 3.23 では, @code{+} と @code{-} を @code{DATE_ADD()} , @code{DATE_SUB()} の代わりに使用できます. (See example below.) @code{date} には、@code{DATETIME} か @code{DATE} 型の値を指定します。 この値から演算が開始されます。 @code{expr} には、date から増減させる値を指定します。 @code{expr} が @samp{-} から始まっていれば、負数を示します。 @code{type} はどれぐらいの期間かを示すキーワードです。 @code{EXTRACT(type FROM date)} 関数は、date から 'type' の部分を返します。 以下の表に、@code{type} と @code{expr} の関連を示します： @multitable @columnfractions .25 .45 @item @code{type} @strong{value} @tab @strong{Expected} @code{expr} @strong{format} @item @code{SECOND} @tab @code{SECONDS} @item @code{MINUTE} @tab @code{MINUTES} @item @code{HOUR} @tab @code{HOURS} @item @code{DAY} @tab @code{DAYS} @item @code{MONTH} @tab @code{MONTHS} @item @code{YEAR} @tab @code{YEARS} @item @code{MINUTE_SECOND} @tab @code{"MINUTES:SECONDS"} @item @code{HOUR_MINUTE} @tab @code{"HOURS:MINUTES"} @item @code{DAY_HOUR} @tab @code{"DAYS HOURS"} @item @code{YEAR_MONTH} @tab @code{"YEARS-MONTHS"} @item @code{HOUR_SECOND} @tab @code{"HOURS:MINUTES:SECONDS"} @item @code{DAY_MINUTE} @tab @code{"DAYS HOURS:MINUTES"} @item @code{DAY_SECOND} @tab @code{"DAYS HOURS:MINUTES:SECONDS"} @end multitable MySQL は、 @code{expr} フォーマット内のいかなる句読点区切りをも許します。 上の表中の区切り文字は提案する区切り文字です。 もし @code{date} 引数が @code{DATE} 値で、@code{YEAR}, @code{MONTH}, @code{DAY} の部分のみを含む 計算をするなら、結果は @code{DATE} 値が返ります。 それ以外なら @code{DATETIME} 値が返ります: @example mysql> SELECT "1997-12-31 23:59:59" + INTERVAL 1 SECOND; -> 1998-01-01 00:00:00 mysql> SELECT INTERVAL 1 DAY + "1997-12-31"; -> 1998-01-01 mysql> SELECT "1998-01-01" - INTERVAL 1 SECOND; -> 1997-12-31 23:59:59 mysql> SELECT DATE_ADD("1997-12-31 23:59:59", -> INTERVAL 1 SECOND); -> 1998-01-01 00:00:00 mysql> SELECT DATE_ADD("1997-12-31 23:59:59", -> INTERVAL 1 DAY); -> 1998-01-01 23:59:59 mysql> SELECT DATE_ADD("1997-12-31 23:59:59", -> INTERVAL "1:1" MINUTE_SECOND); -> 1998-01-01 00:01:00 mysql> SELECT DATE_SUB("1998-01-01 00:00:00", -> INTERVAL "1 1:1:1" DAY_SECOND); -> 1997-12-30 22:58:59 mysql> SELECT DATE_ADD("1998-01-01 00:00:00", -> INTERVAL "-1 10" DAY_HOUR); -> 1997-12-30 14:00:00 mysql> SELECT DATE_SUB("1998-01-02", INTERVAL 31 DAY); -> 1997-12-02 @end example もしあなたの指定する interval 値が短すぎるなら( @code{type} キーワードから 類推される値を含んでいない場合)、 MySQL は interval 値の一番 左の部分を指定し忘れたものだと仮定します。 例えば、もし @code{type} を @code{DAY_SECOND} に指定した場合、 @code{expr} の値は 日、時、分、秒 からなる物と期待されます。 ここであなたが @code{"1:10"} のような値を指定していたなら、 MySQL は、日、時 の部分が忘れ去られて、分、秒 が与えられたと 推定します。 つまり、 @code{"1:10" DAY_SECOND} は @code{"1:10" MINUTE_SECOND} で あると理解されるのです。 これは、MySQL が @code{TIME} 値を時刻ではなく経過時間の表現と解釈 する方法に類似しています。 注意: 時刻部を含む何かに対して、日付値の加算や減算を行なう場合、日付値は自 動的に日時値に変換されます: @example mysql> SELECT DATE_ADD("1999-01-01", INTERVAL 1 DAY); -> 1999-01-02 mysql> SELECT DATE_ADD("1999-01-01", INTERVAL 1 HOUR); -> 1999-01-01 01:00:00 @end example もし、不正な値が使用されたなら、結果は @code{NULL} です. もし @code{MONTH} や @code{YEAR_MONTH} や @code{YEAR} を足し算して、 結果となる日付が新しい月の最大日よりも大きい日になるようなら、 その日は、新しい月の最大日に修正されます。 @example mysql> SELECT DATE_ADD('1998-01-30', Interval 1 month); -> 1998-02-28 @end example 例のように、@code{INTERVAL} と @code{type} キーワードは ケース依存ではありません. @findex EXTRACT() @item EXTRACT(type FROM date) The @code{EXTRACT()} function uses the same kinds of interval type specifiers as @code{DATE_ADD()} or @code{DATE_SUB()}, but extracts parts from the date rather than performing date arithmetic. @example mysql> SELECT EXTRACT(YEAR FROM "1999-07-02"); -> 1999 mysql> SELECT EXTRACT(YEAR_MONTH FROM "1999-07-02 01:02:03"); -> 199907 mysql> SELECT EXTRACT(DAY_MINUTE FROM "1999-07-02 01:02:03"); -> 20102 @end example @findex TO_DAYS() @item TO_DAYS(date) 日付 @code{date} を与えると、0年からの日数を返します。 @example mysql> SELECT TO_DAYS(950501); -> 728779 mysql> SELECT TO_DAYS('1997-10-07'); -> 729669 @end example @code{TO_DAYS()} はグレゴリオ歴の開始(1582)より前の値での使用を意図されて いません。歴が変更された時に失われた日を考慮に入れてないからです。 @findex FROM_DAYS() @item FROM_DAYS(N) 与えられた日数 @code{N} から @code{DATE} 値を返します: @example mysql> SELECT FROM_DAYS(729669); -> '1997-10-07' @end example @code{FROM_DAYS()} はグレゴリオ歴の開始(1582)より前の値での使用を意図され ていません。歴が変更された時に失われた日を考慮に入れてないからです。 @findex DATE_FORMAT() @item DATE_FORMAT(date,format) @code{date} 値を @code{format} 文字列に従って整形します。次の指定が @code{format} 文字列で使用できます: @multitable @columnfractions .10 .65 @item @strong{Specifier} @tab @strong{Description} @item @code{%M} @tab 月名 (@code{January}..@code{December}) @item @code{%W} @tab 曜日 (@code{Sunday}..@code{Saturday}) @item @code{%D} @tab 英語サフィックス付き月の日 (@code{0th}, @code{1st}, @code{2nd}, @code{3rd}, etc.) @item @code{%Y} @tab 4桁の年 @item @code{%y} @tab 2桁の年 @item @code{%X} @tab 週の年。週の最初の日は日曜日。4桁の数値。'%V' と共に使用されます @item @code{%x} @tab 週の年。週の最初の日は月曜日。4桁の数値。'%v' と共に使用されます @item @code{%a} @tab 省略された曜日名 (@code{Sun}..@code{Sat}) @item @code{%d} @tab 月の日, 数値 (@code{00}..@code{31}) @item @code{%e} @tab 月の日, 数値 (@code{0}..@code{31}) @item @code{%m} @tab 月, 数値 (@code{00}..@code{12}) @item @code{%c} @tab 月, 数値 (@code{0}..@code{12}) @item @code{%b} @tab 省略された月名 (@code{Jan}..@code{Dec}) @item @code{%j} @tab 年の日 (@code{001}..@code{366}) @item @code{%H} @tab 時 (@code{00}..@code{23}) @item @code{%k} @tab 時 (@code{0}..@code{23}) @item @code{%h} @tab 時 (@code{01}..@code{12}) @item @code{%I} @tab 時 (@code{01}..@code{12}) @item @code{%l} @tab 時 (@code{1}..@code{12}) @item @code{%i} @tab 分, 数値 (@code{00}..@code{59}) @item @code{%r} @tab 時刻, 12時間 (@code{hh:mm:ss [AP]M}) @item @code{%T} @tab 時刻, 24時間 (@code{hh:mm:ss}) @item @code{%S} @tab 秒 (@code{00}..@code{59}) @item @code{%s} @tab 秒 (@code{00}..@code{59}) @item @code{%p} @tab @code{AM} or @code{PM} @item @code{%w} @tab 週の日 (@code{0}=Sunday..@code{6}=Saturday) @item @code{%U} @tab 週 (@code{00}..@code{53}), 週のはじまりを 日曜とした場合 @item @code{%u} @tab 週 (@code{00}..@code{53}), 週のはじまりを 月曜とした場合 @item @code{%V} @tab 週 (@code{01}..@code{53}), 週のはじまりは日曜日。'%X' と共に使用されます @item @code{%v} @tab 週 (@code{01}..@code{53}), 週のはじまりは月曜日。'%x' と共に使用されます @item @code{%%} @tab リテラル @samp{%}。 @end multitable 他の全ての文字は解釈されずに結果にコピーされます: @example mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%W %M %Y'); -> 'Saturday October 1997' mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%H:%i:%s'); -> '22:23:00' mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%D %y %a %d %m %b %j'); -> '4th 97 Sat 04 10 Oct 277' mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%H %k %I %r %T %S %w'); -> '22 22 10 10:23:00 PM 22:23:00 00 6' mysql> SELECT DATE_FORMAT('1999-01-01', '%X %V'); -> '1998 52' @end example MySQL バージョン 3.23 では、 @code{%} 文字はフォーマット文字の前に必ず 必要とされます。 それより前のバージョンでは、 @code{%} 文字はオプションでした。 The reason the ranges for the month and day specifiers begin with zero is that MySQL allows incomplete dates such as @code{'2004-00-00'} to be stored as of MySQL 3.23. @findex TIME_FORMAT() @item TIME_FORMAT(time,format) これは上記の @code{DATE_FORMAT()} のように使用されますが、 @code{format} オプションでは、時,分,秒だけを操作できます。 他のオプションは @code{NULL} or @code{0} を与えます。 @findex CURDATE() @findex CURRENT_DATE @item CURDATE() @itemx CURRENT_DATE 今日の日付を返します。日付の形式は、@code{CURDATE()} が数値または文字列のどち らの文脈で使用されたかに依存して @code{YYYYMMDD} または @code{'YYYY-MM-DD'} で返 されます: @example mysql> SELECT CURDATE(); -> '1997-12-15' mysql> SELECT CURDATE() + 0; -> 19971215 @end example @findex CURTIME() @findex CURRENT_TIME @item CURTIME() @itemx CURRENT_TIME 現在の時刻を @code{HHMMSS} または @code{'HH:MM:SS'} の形式で返します。こ れは @code{CURTIME()} が数値または文字列のどちらの文脈で使用されたかに依 存します: @example mysql> SELECT CURTIME(); -> '23:50:26' mysql> SELECT CURTIME() + 0; -> 235026 @end example @findex NOW() @findex SYSDATE() @findex CURRENT_TIMESTAMP @item NOW() @itemx SYSDATE() @itemx CURRENT_TIMESTAMP 現在の時刻を返します。数値または文字列のどちらの文脈で使用されたかに依存して @code{YYYYMMDDHHMMSS} または @code{'YYYY-MM-DD HH:MM:SS'} 形式で返されます: @example mysql> SELECT NOW(); -> '1997-12-15 23:50:26' mysql> SELECT NOW() + 0; -> 19971215235026 @end example Note that @code{NOW()} is only evaluated once per query, namely at the start of query execution. This means that multiple references to @code{NOW()} within a single query will always give the same time. @findex UNIX_TIMESTAMP() @item UNIX_TIMESTAMP() @itemx UNIX_TIMESTAMP(date) 引数なしで呼び出された場合は、UNIX timestamp (GMT @code{'1970-01-01 00:00:00'} からの秒数) です。If @code{UNIX_TIMESTAMP()} is called with a @code{date} argument, it returns the value of the argument as seconds since @code{'1970-01-01 00:00:00'} GMT. @code{date} はローカル時刻での @code{DATE} 文字列、@code{DATETIME} 文字列、@code{TIMESTAMP}, または @code{YYMMDD} または @code{YYYYMMDD} 形式の数値です: @example mysql> SELECT UNIX_TIMESTAMP(); -> 882226357 mysql> SELECT UNIX_TIMESTAMP('1997-10-04 22:23:00'); -> 875996580 @end example @code{UNIX_TIMESTAMP} が @code{TIMESTAMP} フィールドに使用された場合、 この関数は、暗黙の ``文字から UNIX タイムスタンプ'' 変換をすることなく、 値を得ます。 If you pass an out-of-range date to @code{UNIX_TIMESTAMP()} it will return 0, but please note that only basic checking is performed (year 1970-2037, month 01-12, day 01-31). If you want to subtract @code{UNIX_TIMESTAMP()} columns, you may want to cast the result to signed integers. @xref{Cast Functions}. @findex FROM_UNIXTIME() @item FROM_UNIXTIME(unix_timestamp) 文脈(数値/文字列)に依存して、@code{'YYYY-MM-DD HH:MM:SS'} または @code{YYYYMMDDHHMMSS} 形式の timestamp 文字列を返します: @example mysql> SELECT FROM_UNIXTIME(875996580); -> '1997-10-04 22:23:00' mysql> SELECT FROM_UNIXTIME(875996580) + 0; -> 19971004222300 @end example @findex FROM_UNIXTIME() @item FROM_UNIXTIME(unix_timestamp,format) @code{format} に従って整形された UNIX timestamp 文字列を返します。 @code{format} は @code{DATE_FORMAT()} 関数のエントリに一覧されたのと同じ指 定子を含むことができます: @example mysql> SELECT FROM_UNIXTIME(UNIX_TIMESTAMP(), '%Y %D %M %h:%i:%s %x'); -> '1997 23rd December 03:43:30 1997' @end example @findex SEC_TO_TIME() @item SEC_TO_TIME(seconds) @code{seconds} 引数を時分秒に変換して返します。関数が文字列文脈または数値 文脈のどちらで使用されたかに依存して、@code{'HH:MM:SS'} または @code{HHMMSS} 形式で値を返します: @example mysql> SELECT SEC_TO_TIME(2378); -> '00:39:38' mysql> SELECT SEC_TO_TIME(2378) + 0; -> 3938 @end example @findex TIME_TO_SEC() @item TIME_TO_SEC(time) @code{time} を秒に変換します。 @example mysql> SELECT TIME_TO_SEC('22:23:00'); -> 80580 mysql> SELECT TIME_TO_SEC('00:39:38'); -> 2378 @end example @end table @node Cast Functions, Other Functions, Date and time functions, Functions @subsection Cast Functions The syntax of the @code{CAST} function is: @findex CAST @findex CONVERT @example CAST(expression AS type) or CONVERT(expression,type) @end example Where type is one of: @itemize @bullet @item @code{BINARY} @item @code{CHAR} (New in 4.0.6) @item @code{DATE} @item @code{DATETIME} @item @code{SIGNED @{INTEGER@}} @item @code{TIME} @item @code{UNSIGNED @{INTEGER@}} @end itemize @code{CAST()} is ANSI SQL99 syntax and @code{CONVERT()} is ODBC syntax. The cast function is mainly useful when you want to create a column with a specific type in a @code{CREATE ... SELECT}: @example CREATE TABLE new_table SELECT CAST('2000-01-01' AS DATE); @end example @code{CAST(string AS BINARY} is the same thing as @code{BINARY string}. @code{CAST(expr AS CHAR} threats expression to be a string with the default character set. To cast a string to a numeric value, you don't normally have to do anything; just use the string value as it would be a number: @example mysql> SELECT 1+'1'; -> 2 @end example If you use a number in string context the number will automatically be converted to a @code{BINARY} string. @example mysql> SELECT CONCAT("hello you ",2); -> "hello you 2" @end example MySQL supports arithmetic with both signed and unsigned 64-bit values. If you are using an numerical operations (like @code{+}) and one of the operands are @code{unsigned integer}, then the result will be unsigned. You can override this by using the @code{SIGNED} and @code{UNSIGNED} cast operators, which will cast the operation to a signed or unsigned 64-bit integer, respectively. @example mysql> SELECT CAST(1-2 AS UNSIGNED) -> 18446744073709551615 mysql> SELECT CAST(CAST(1-2 AS UNSIGNED) AS SIGNED); -> -1 @end example Note that if either operation is a floating-point value (In this context @code{DECIMAL()} is regarded as a floating-point value) the result will be a floating-point value and is not affected by the above rule. @example mysql> SELECT CAST(1 AS UNSIGNED) -2.0 -> -1.0 @end example If you are using a string in an arithmetic operation, this is converted to a floating-point number. The @code{CAST()} and @code{CONVERT()} functions were added in MySQL 4.0.2. The handing of unsigned values was changed in MySQL 4.0 to be able to support @code{BIGINT} values properly. If you have some code that you want to run in both MySQL 4.0 and 3.23 (in which case you probably can't use the CAST function), you can use the following trick to get a signed result when subtracting two unsigned integer columns: @example SELECT (unsigned_column_1+0.0)-(unsigned_column_2+0.0); @end example The idea is that the columns are converted to floating-point before doing the subtraction. If you get a problem with @code{UNSIGNED} columns in your old MySQL application when porting to MySQL 4.0, you can use the @code{--sql-mode=NO_UNSIGNED_SUBTRACTION} option when starting @code{mysqld}. Note however that as long as you use this, you will not be able to make efficient use of the @code{UNSIGNED BIGINT} column type. @node Other Functions, Group by functions, Cast Functions, Functions @subsection その他の関数 @menu * Bit functions:: Bit Functions * Miscellaneous functions:: Miscellaneous Functions @end menu @node Bit functions, Miscellaneous functions, Other Functions, Other Functions @subsubsection ビット関数 @findex arithmetic functions @findex bit functions @findex functions, arithmetic @findex functions, bit これらは最大 64 ビットの範囲を持ちます。MySQL は @code{BIGINT} (64-bit) 演算を使用するためです。 @table @code @findex | (bitwise OR) @findex OR, bitwise @item | ビット演算 OR @example mysql> SELECT 29 | 15; -> 31 @end example The result is an unsigned 64-bit integer. @findex & (bitwise AND) @findex AND, bitwise @item & ビット演算 AND @example mysql> SELECT 29 & 15; -> 13 @end example The result is an unsigned 64-bit integer. @findex ^ (bitwise XOR) @findex XOR, bitwise @item ^ Bitwise XOR @example mysql> SELECT 1 ^ 1; -> 0 mysql> SELECT 1 ^ 0; -> 1 mysql> SELECT 11 ^ 3; -> 8 @end example The result is an unsigned 64-bit integer. @code{XOR} was added in version 4.0.2. @findex << (left shift) @item << 左に longlong (@code{BIGINT}) number 分、ビットをシフトします: @example mysql> SELECT 1 << 2; -> 4 @end example The result is an unsigned 64-bit integer. @findex >> (right shift) @item >> 右に longlong (@code{BIGINT}) number 分、ビットをシフトします: @example mysql> SELECT 4 >> 2; -> 1 @end example The result is an unsigned 64-bit integer. @findex ~ @item ~ Invert all bits: @example mysql> SELECT 5 & ~1; -> 4 @end example The result is an unsigned 64-bit integer. @findex BIT_COUNT() @item BIT_COUNT(N) 引数 @code{N} がいくつビットを持っているか(２進数表記したときの１の数): @example mysql> SELECT BIT_COUNT(29); -> 4 @end example @end table @node Miscellaneous functions, , Bit functions, Other Functions @subsubsection その他の関数 @findex miscellaneous functions @findex functions, miscellaneous @table @code @findex DATABASE() @item DATABASE() 現在のデータベース名を返します @example mysql> SELECT DATABASE(); -> 'test' @end example もしデータベースが選択されていないなら、@code{DATABASE()} は空文字を返します。 @findex USER() @findex SYSTEM_USER() @findex SESSION_USER() @item USER() @itemx SYSTEM_USER() @itemx SESSION_USER() Returns the current MySQL user name: @example mysql> SELECT USER(); -> 'davida@@localhost' @end example MySQL バージョン 3.22.11 以降では、この関数はユーザー名とクライアントの ホスト名を含みます。 ユーザー名の部分だけ取り出すには次のようにします。 （これはホスト名が含まれていなくとも動くでしょう）： @example mysql> SELECT substring_index(USER(),"@@",1); -> 'davida' @end example @findex CURRENT_USER() @item CURRENT_USER() Returns the user name, current session was authentificated as: @example mysql> SELECT USER(); -> 'davida@@localhost' mysql> SELECT * FROM mysql.user; -> ERROR 1044: Access denied for user: '@@localhost' to database 'mysql' mysql> SELECT CURRENT_USER(); -> '@@localhost' @end example @findex PASSWORD() @findex OLD_PASSWORD() @item PASSWORD(str) @itemx OLD_PASSWORD(str) プレーンテキストのパスワード @code{str} からパスワード文字列を計算します。 これは @code{user} 許可テーブルの @code{Password} フィールドに、 暗号化された MySQL パスワードを保存する際に使用されます: @example mysql> SELECT PASSWORD('badpwd'); -> '7f84554057dd964b' @end example @cindex password encryption, reversibility of @code{PASSWORD()} 暗号は不可逆です。 @code{PASSWORD()} は UNIX のパスワードが暗号化するのと同じ方法で 暗号化を行うわけではありません。 @code{ENCRYPT()} 参照。 @strong{注意:} @code{PASSWORD()} 関数は MySQL サーバー内の認証システムで使用されます。 その関数をあなたの独自アプリケーションでは使用すべきでは@strong{ありません}。 そうしたければ、代わりに @code{MD5()} や @code{SHA1()} を使用します。 Also see @code{RFC-2195} for more information about handling passwords and authentication securely in your application. @findex ENCRYPT() @item ENCRYPT(str[,salt]) UNIX の @code{crypt()} システムコールで @code{str} を暗号化します。 @code{salt} は2文字の文字列です。 (MySQL バージョン 3.22.16 で, @code{salt} は2文字以上許されるようになり ました。) @example mysql> SELECT ENCRYPT("hello"); -> 'VxuFAJXVARROc' @end example システムで @code{crypt()} が利用できない場合は @code{ENCRYPT()} は常に @code{NULL} を返します。 少なくともいくつかのシステムでは、 @code{ENCRYPT()} は @code{str} 文字中の最初の 8 文字以外は全て無視します。 これは @code{crypt()} システムコールの振る舞いによって決定づけられます。 @findex ENCODE() @item ENCODE(str,pass_str) パスワードとして @code{pass_str} を用いて @code{str} を暗号化します。結果 を復号化するには、@code{DECODE()}を使用します。 結果はバイナリ文字列で、長さは @code{string} と同じです。 フィールドにそれを保存したい場合は @code{BLOB} フィールド型を使用してください。 @findex DECODE() @item DECODE(crypt_str,pass_str) 暗号化された文字列 @code{crypt_str} をパスワードとして @code{pass_str} を 用いて復号化します。@code{crypt_str} は @code{ENCODE()} から返された文字列 であるべきです。 @findex MD5() @item MD5(string) 文字列を MD5 128bit チェックサムした結果を返します。 値は 32 桁の 16進表示です。 例えばハッシュキーとして使用できるように: @example mysql> SELECT MD5("testing"); -> 'ae2b1fca515949e5d54fb22b8ed95575' @end example これは "RSA Data Security, Inc. MD5 Message-Digest Algorithm". @findex SHA1() @findex SHA() @item SHA1(string) @itemx SHA(string) Calculates an SHA1 160 bit checksum for the string, as described in RFC 3174 (Secure Hash Algorithm). The value is returned as a 40 digit hex number, or @code{NULL} in case the input argument was @code{NULL}. One of the possible uses for this function is as a hash key. You can also use it as cryptographically safe function for storing passwords. @example mysql> SELECT SHA1("abc"); -> 'a9993e364706816aba3e25717850c26c9cd0d89d' @end example @code{SHA1()} was added in version 4.0.2, and can be considered a cryptographically more secure equivalent of @code{MD5()}. @code{SHA()} is synonym for @code{SHA1()}. @findex AES_ENCRYPT() @findex AES_DECRYPT() @item AES_ENCRYPT(string,key_string) @itemx AES_DECRYPT(string,key_string) These functions allow encryption/decryption of data using the official AES (Advanced Encryption Standard) algorithm, previously known as Rijndael. Encoding with 128 bit key length is used, but you can extend it up to 256 bit by patching the source. We chose 128 bits because it is much faster and it is usually secure enough. The input arguments may be any length. If either argument is @code{NULL}, the result of this function is also @code{NULL}. As AES is a block level algorithm, padding is used to encode uneven length strings and so the result string length may be calculated as 16*(trunc(string_length/16)+1). If @code{AES_DECRYPT()} detects invalid data or incorrect padding, it will return @code{NULL}. However, it is possible for @code{AES_DECRYPT()} to return a non-@code{NULL} value (possibly garbage) if the input data or the key was invalid. You can use the AES functions to store data in an encrypted form by modifying your queries: @example INSERT INTO t VALUES (1,AES_ENCRYPT("text","password")); @end example You can get even more security by avoiding transferring the key over the connection for each query, which can be accomplished by storing it in a server side variable at connection time: @example SELECT @@password:="my password"; INSERT INTO t VALUES (1,AES_ENCRYPT("text",@@password)); @end example @code{AES_ENCRYPT()} and @code{AES_DECRYPT()} were added in version 4.0.2, and can be considered the most cryptographically secure encryption functions currently available in MySQL. @findex DES_ENCRYPT() @item DES_ENCRYPT(string_to_encrypt [, (key_number | key_string) ] ) Encrypts the string with the given key using the Triple-DES algorithm. Note that this function only works if you have configured MySQL with SSL support. @xref{Secure connections}. The encryption key to use is chosen the following way: @multitable @columnfractions .25 .65 @item @strong{Argument} @tab @strong{Description} @item Only one argument @tab The first key from @code{des-key-file} is used. @item key number @tab The given key (0-9) from the @code{des-key-file} is used. @item string @tab The given @code{key_string} will be used to crypt @code{string_to_encrypt}. @end multitable The return string will be a binary string where the first character will be @code{CHAR(128 | key_number)}. The 128 is added to make it easier to recognise an encrypted key. If you use a string key, @code{key_number} will be 127. On error, this function returns @code{NULL}. The string length for the result will be @code{new_length= org_length + (8-(org_length % 8))+1}. The @code{des-key-file} has the following format: @example key_number des_key_string key_number des_key_string @end example Each @code{key_number} must be a number in the range from 0 to 9. Lines in the file may be in any order. @code{des_key_string} is the string that will be used to encrypt the message. Between the number and the key there should be at least one space. The first key is the default key that will be used if you don't specify any key argument to @code{DES_ENCRYPT()} You can tell MySQL to read new key values from the key file with the @code{FLUSH DES_KEY_FILE} command. This requires the @code{Reload_priv} privilege. One benefit of having a set of default keys is that it gives applications a way to check for existence of encrypted column values, without giving the end user the right to decrypt those values. @example mysql> SELECT customer_address FROM customer_table WHERE crypted_credit_card = DES_ENCRYPT("credit_card_number"); @end example @findex DES_DECRYPT() @item DES_DECRYPT(string_to_decrypt [, key_string]) Decrypts a string encrypted with @code{DES_ENCRYPT()}. Note that this function only works if you have configured MySQL with SSL support. @xref{Secure connections}. If no @code{key_string} argument is given, @code{DES_DECRYPT()} examines the first byte of the encrypted string to determine the DES key number that was used to encrypt the original string, then reads the key from the @code{des-key-file} to decrypt the message. For this to work the user must have the @code{SUPER} privilege. If you pass this function a @code{key_string} argument, that string is used as the key for decrypting the message. If the @code{string_to_decrypt} doesn't look like an encrypted string, MySQL will return the given @code{string_to_decrypt}. On error, this function returns @code{NULL}. @findex LAST_INSERT_ID([expr]) @item LAST_INSERT_ID([expr]) 最後に @code{AUTO_INCREMENT} フィールドに挿入されて自動的に生成された値を返しま す。 @xref{mysql_insert_id,, @code{mysql_insert_id()}}. @example mysql> SELECT LAST_INSERT_ID(); -> 195 @end example 最後の作成された ID はそれぞれのコネクション毎にサーバーに維持されます。 これは他のクライアントからは変更できないでしょう。 もし他の非マジック値をもつ @code{AUTO_INCREMENT} フィールド （値が @code{NULL} でも @code{0} でもないということ） を更新しても、これは 変更されません。 一つの INSERT 文で同時に多くのレコードを挿入する場合、 @code{LAST_INSERT_ID()} は最初に挿入されたレコードの値を返します。この理由 は、他のサーバに対して同じ @code{INSERT} を簡単に再現できるようにするため です。 @cindex sequence emulation If @code{expr} is given as an argument to @code{LAST_INSERT_ID()}, then the value of the argument is returned by the function, is set as the next value to be returned by @code{LAST_INSERT_ID()} and used as the next auto_increment value. これは シーケンス番号のシミュレーションに使用できます： 最初にテーブルを作成： @example mysql> CREATE TABLE sequence (id int not null); mysql> INSERT INTO sequence VALUES (0); @end example そして以下のようにしてシーケンス番号を生成： @example mysql> UPDATE sequence SET id=LAST_INSERT_ID(id+1); @end example @code{LAST_INSERT_ID()} の呼び出し無しでシーケンス番号を生成することが可能 ですが、この方法でこの関数を使用するユーティリティは、ID 値が最後に自動的 に生成された値としてサーバに管理されます。MySQL 内の通常の任意の @code{AUTO_INCREMENT} 値を読み込んで新しい ID を取り出すことができます。例 えば、@code{LAST_INSERT_ID()} (引数無し) は新しい ID を返します。C API 関 数 @code{mysql_insert_id()} もこの値を得るために使用できます。 Note that as @code{mysql_insert_id()} is only updated after @code{INSERT} and @code{UPDATE} statements, so you can't use the C API function to retrieve the value for @code{LAST_INSERT_ID(expr)} after executing other SQL statements like @code{SELECT} or @code{SET}. @findex FORMAT() @item FORMAT(X,D) @code{'#,###,###.##'} のような形式(小数部 @code{X} 桁)で数値 @code{D} を整形 します。 もし @code{D} が @code{0} なら, 結果にはいかなる 小数点も小数部も含まれません。 @example mysql> SELECT FORMAT(12332.123456, 4); -> '12,332.1235' mysql> SELECT FORMAT(12332.1,4); -> '12,332.1000' mysql> SELECT FORMAT(12332.2,0); -> '12,332' @end example @findex VERSION() @item VERSION() MySQL サーバのバージョンを返します: @example mysql> SELECT VERSION(); -> '3.23.13-log' @end example 注意: バージョンが @code{-log} で終わる場合はロギングが有効であることを意 味します。 @findex CONNECTION_ID() @item CONNECTION_ID() 接続の接続 ID (@code{thread_id}) を返します。すべての接続は接続自身の一意 な ID を持ちます: @example mysql> SELECT CONNECTION_ID(); -> 1 @end example @cindex timeout @findex GET_LOCK() @item GET_LOCK(str,timeout) @code{timeout} 秒のタイムアウトで、@code{str} と名付けられたロックの獲得を試み ます。ロックを獲得した場合は @code{1}, タイムアウトの場合は @code{0}, エラーの場 合(メ モリ不足やスレッドが @code{mysqladmin kill} で殺された場合など)は @code{NULL} が返ります。@code{RELEASE_LOCK} の実行、新しい @code{GET_LOCK} の実行、 スレッドの終了の場合に、ロックは解放されます。この関数はアプリケーション ロックやレコードロックのシミュレートのために使用できます。 これは、同じ名前のロックを行おうとする他のクライアントからのリクエストを ブロックします； 与えられた名前のロックに応じているクライアントは、 協調してロッキングを行うために、その文字列を使用できます: @example mysql> SELECT GET_LOCK("lock1",10); -> 1 mysql> SELECT IS_FREE_LOCK("lock2"); -> 1 mysql> SELECT GET_LOCK("lock2",10); -> 1 mysql> SELECT RELEASE_LOCK("lock2"); -> 1 mysql> SELECT RELEASE_LOCK("lock1"); -> NULL @end example ２つ目の @code{RELEASE_LOCK()} は @code{NULL} を返します。 なぜなら、 @code{"lock1"} は、２つ目の @code{GET_LOCK()} の呼び出し時点で、 自動的に解放されるからです。 @findex RELEASE_LOCK() @item RELEASE_LOCK(str) @code{GET_LOCK} で獲得したロック @code{str} を解放します。ロックが解 放された場合は @code{1}, このスレッドによってロックされていない場合は @code{0} (この場合、ロックは解放されません), @code{str}が存在しない場合は @code{NULL} が返ります。 もし、 @code{GET_LOCK()} をコールして得られなかった場合、 あるいは、既に解放されている場合は、ロックは存在しないでしょう。 The @code{DO} statement is convinient to use with @code{RELEASE_LOCK()}. @xref{DO}. @findex IS_FREE_LOCK() @item IS_FREE_LOCK(str) Checks if the lock named @code{str} is free to use (i.e., not locked). Returns @code{1} if the lock is free (no one is using the lock), @code{0} if the lock is in use, and @code{NULL} on errors (like incorrect arguments). @findex BENCHMARK() @item BENCHMARK(count,expr) @code{BENCHMARK()} 関数は @code{expr} で与えられた文を @code{count} 回 繰り返し実行します。 これは MySQL のその文の処理がどれぐらい 速いのか知るのに使用されるでしょう。 結果は常に @code{0} です。 想定している使用は、 @code{mysql} クライアントです。 あるクエリの実行時間を知るための使用です: @example mysql> SELECT BENCHMARK(1000000,ENCODE("hello","goodbye")); +----------------------------------------------+ | BENCHMARK(1000000,ENCODE("hello","goodbye")) | +----------------------------------------------+ | 0 | +----------------------------------------------+ 1 row in set (4.74 sec) @end example 報告された時間は、クライアントでの経過時間です。 サーバー側の CPU 時間では ありません。@code{BENCHMARK()} を何回か実行して、サーバマシンの負荷の重さ を考慮して結果を解釈することを勧めます。 @findex INET_NTOA() @item INET_NTOA(expr) 数値表現に対するネットワークアドレス(4 または 8 バイト) を返します: @example mysql> SELECT INET_NTOA(3520061480); -> "209.207.224.40" @end example @findex INET_ATON() @item INET_ATON(expr) ネットワークアドレスに対する数値を表す整数を返します。アドレスは 4 または 8 バイトアドレスです: @example mysql> SELECT INET_ATON("209.207.224.40"); -> 3520061480 @end example 生成された数値は常にネットワークバイトオーダです; たとえば、上記の数値は @code{209*255^3 + 207*255^2 + 224*255 +40} として計算されます。 @findex MASTER_POS_WAIT() @item MASTER_POS_WAIT(log_name, log_pos) マスターログの指定された位置にスレーブが到達するまで(すなわち、スレーブが 読み込んで全て更新しおわるまで)ブロックします。 マスター情報が初期化されていないか引数が違う場合、@code{NULL} が返ります。 スレーブが動作していない場合、ブロックし、スレーブが起動し、指定位置にくるまで待ちます。 スレーブが既に指定位置を通り過ぎていた場合、即時復帰します。 If @code{timeout} (new in 4.0.10) is specified, will give up waiting when @code{timeout} seconds have elapsed. @code{timeout} must be greater than 0; a zero or negative @code{timeout} means no timeout. The return value is the number of log events it had to wait to get to the specified position, or @code{NULL} in case of error, or @code{-1} if the timeout has been exceeded. This command is useful for control of master-slave synchronisation, but was originally written to facilitate replication testing. @findex FOUND_ROWS() @findex LIMIT @item FOUND_ROWS() Returns the number of rows that the last @code{SELECT SQL_CALC_FOUND_ROWS ...} command would have returned, if it had not been restricted with @code{LIMIT}. @example mysql> SELECT SQL_CALC_FOUND_ROWS * FROM tbl_name WHERE id > 100 LIMIT 10; mysql> SELECT FOUND_ROWS(); @end example The second @code{SELECT} will return a number indicating how many rows the first @code{SELECT} would have returned had it been written without the @code{LIMIT} clause. Note that if you are using @code{SELECT SQL_CALC_FOUND_ROWS ...} MySQL has to calculate all rows in the result set. However, this is faster than if you would not use @code{LIMIT}, as the result set need not be sent to the client. @code{SQL_CALC_FOUND_ROWS} is available starting at MySQL version 4.0.0. @end table @node Group by functions, , Other Functions, Functions @subsubsection Functions for Use with @code{GROUP BY} Clauses @findex GROUP BY functions @findex functions, GROUP BY @code{GROUP BY}節を含まない文でグループ関数を使用すると 全てのレコードについてグループされたものとみなされます。 @table @code @findex COUNT() @item COUNT(expr) Returns a count of the number of non-@code{NULL} values in the rows retrieved by a @code{SELECT} statement: @code{SELECT}文により選択されたレコードから@code{NULL}ではないものの数を返します。 @example mysql> SELECT student.student_name,COUNT(*) FROM student,course WHERE student.student_id=course.student_id GROUP BY student_name; @end example @code{COUNT(*)}は@code{NULL}を含むかどうかで選択されたレコードの数を返すだけです。 @code{COUNT(*)}は一つのテーブルから一つだけカラムが選択され、 尚且つ@code{WHERE}節が使用されていない場合に最適化され、高速に動作します。 例えば以下のように使います。 @example mysql> SELECT COUNT(*) FROM student; @end example @findex COUNT(DISTINCT) @findex DISTINCT @item COUNT(DISTINCT expr,[expr...]) これは@code{NULL}値では無い値を持つデータの数を区別して返すことが出来ます。 @example mysql> SELECT COUNT(DISTINCT results) from student; @end example 複数の選択されたデータ群から@code{NULL}を含まないデータの総数算出が必要な場合、 MySQLでは必要な選択リストを与えることによって得ることが出来ます。 一方でANSIのSQLではその選択一つ一つについて @code{COUNT(DISTINCT ...)} を使う必要があります。 @findex AVG() @item AVG(expr) @code{expr}で得られる値の平均値を返します。 @example mysql> SELECT student_name, AVG(test_score) FROM student GROUP BY student_name; @end example @findex MIN() @findex MAX() @item MIN(expr) @itemx MAX(expr) @code{expr}で得られる値の最大値、最小値を返します。 @code{MIN()}と@code{MAX()}の引数は文字列を取ることもできます。 この際は文字列の値の大小を比較し、最大と最小を返します。@ref{MySQL indexes}. @example mysql> SELECT student_name, MIN(test_score), MAX(test_score) -> FROM student -> GROUP BY student_name; @end example In @code{MIN()}, @code{MAX()} and other aggregate functions, MySQL currently compares @code{ENUM} and @code{SET} columns by their string value rather than by the string's relative position in the set. This will be rectified. @findex SUM() @item SUM(expr) @code{expr}で得られる値の総計を返します。 もしも得られるレコードが見つからない場合は@code{NULL}が返ってきます。 @findex VARIANCE() @item VARIANCE(expr) Returns the standard variance of @code{expr}. This is an extension to ANSI SQL (available only in version 4.1 or later). @findex STD() @findex STDDEV() @cindex Oracle compatibility @cindex compatibility, with Oracle @item STD(expr) @itemx STDDEV(expr) @code{expr}で得られる値の標準偏差を返します。 これはANSI SQLの格調になっています。 関数としての@code{STDDEV()}の形はOracleのものと互換性があります。 @findex BIT_OR() @item BIT_OR(expr) @code{expr}で得られる値のビット和(@code{OR})を返します。 計算は64-bit(@code{BIGINT})の精度で行われます。 @findex BIT_AND() @item BIT_AND(expr) @code{expr}で得られる値のビット積(@code{AND})を返します。 計算は64-bit(@code{BIGINT})の精度で行われます。 @end table @cindex @code{GROUP BY}, extensions to ANSI SQL MySQLの@code{GROUP BY}は拡張された使い方が可能です。 @code{SELECT}で使用したフィールド名や計算式を@code{GROUP BY}には使用しない、 という使い方が可能です。 このことは@emph{グループにはどんな値も使用可能}ということを表しています。 データの並べ替えやグループ分けに適さない要素を排除することによって より良好なパフォーマンスを得ることが出来ます。 例えば、次のようなクエリで@code{customer.name}についてのグループ分けをする必要はありません。 @example mysql> SELECT order.custid,customer.name,MAX(payments) -> FROM order,customer -> WHERE order.custid = customer.custid -> GROUP BY order.custid; @end example ANSI SQLでは@code{customer.name}を@code{GROUP BY}のところに追加する必要があります。 MySQLではANSIモードで動かしていない限り余計な記述の必要はありません。 @code{GROUP BY}で省略するフィールドはグループ内でユニークでなくてはいけません。 もしそうでない場合は結果は予想もしないようなものになるでしょう。 たとえユニークでは無くても特定のフィールドの値を得るために @code{MIN()}や@code{MAX()}を使用できるケースもあります。 次の例は@code{sort}フィールド中の最小値を持つレコードから 特定の@code{column}の値を取り出します。 @example SUBSTR(MIN(CONCAT(RPAD(sort,6,' '),column)),7) @end example @xref{example-Maximum-column-group-row}. @cindex @code{ORDER BY}, aliases in @cindex aliases, in @code{ORDER BY} clauses @cindex @code{GROUP BY}, aliases in @cindex aliases, in @code{GROUP BY} clauses @cindex expression aliases @cindex aliases, for expressions MySQLの3.22以前のバージョンをお使いであるか、ANSI SQLに沿っての使用をされる場合は @code{GROUP BY}と@code{ORDER BY}内に選択表現を記述してはいけません。 この制限を守った上で作業を進めるにはエイリアスを使用します。 @example mysql> SELECT id,FLOOR(value/100) AS val FROM tbl_name -> GROUP BY id,val ORDER BY val; @end example MySQLのバージョン3.23では次のようにも記述できます。 @example mysql> SELECT id,FLOOR(value/100) FROM tbl_name ORDER BY RAND(); @end example @node Data Manipulation, Data Definition, Functions, Reference @section Data Manipulation: @code{SELECT}, @code{INSERT}, @code{UPDATE}, @code{DELETE} @menu * SELECT:: @code{SELECT} Syntax * INSERT:: @code{INSERT} Syntax * INSERT DELAYED:: @code{INSERT DELAYED} syntax * UPDATE:: @code{UPDATE} Syntax * DELETE:: @code{DELETE} Syntax * TRUNCATE:: @code{TRUNCATE} Syntax * REPLACE:: @code{REPLACE} Syntax * LOAD DATA:: @code{LOAD DATA INFILE} Syntax * DO:: @code{DO} Syntax @end menu @node SELECT, HANDLER, Data Manipulation, Data Manipulation @subsection @code{SELECT} 構文 @findex SELECT @c help SELECT @example SELECT [STRAIGHT_JOIN] [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT] [SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS] [HIGH_PRIORITY] [DISTINCT | DISTINCTROW | ALL] select_expression,... [INTO @{OUTFILE | DUMPFILE@} 'file_name' export_options] [FROM table_references [WHERE where_definition] [GROUP BY @{unsigned_integer | col_name | formula@} [ASC | DESC], ...] [HAVING where_definition] [ORDER BY @{unsigned_integer | col_name | formula@} [ASC | DESC] ,...] [LIMIT [offset,] rows | rows OFFSET offset] [PROCEDURE procedure_name(argument_list)] [FOR UPDATE | LOCK IN SHARE MODE]] @end example @c help end @code{SELECT}は通常、1つまたは1つ以上のテーブルからレコードを検索して抽出 するのに使用されます。 @code{select_expression} は取り出したいフィールドを示します。 @code{SELECT}はまた、テーブルの参照なしに計算によって求められたレコードを 取り出すために使用されます。例: @example mysql> SELECT 1 + 1; -> 2 @end example 全てのキーワードの使用は、上記に示すような順序で正確に与えられる必要があります。 例えば、@code{HAVING}節は必ず@code{GROUP BY}節の後、@code{ORDER BY}節の前でなければなりません。 @itemize @bullet @item @cindex aliases, on expressions @cindex expression aliases @code{SELECT}の表現では、@code{AS}による別名の指定が可能です。別名は、 フィールド名の表現として使われ、@code{ORDER BY}及び@code{HAVING}節とともに使用することができます。 例: @example mysql> SELECT CONCAT(last_name,', ',first_name) AS full_name FROM mytable ORDER BY full_name; @end example @item It is not allowed to use a column alias in a @code{WHERE} clause, because the column value may not yet be determined when the @code{WHERE} clause is executed. @xref{Problems with alias}. @item @findex AS @findex USE INDEX @findex IGNORE INDEX @findex USE KEY @findex IGNORE KEY @findex FORCE INDEX @code{FROM table_references}節は、(例えば、選択するレコードにより、1つ又はそれ以上の) 結合するテーブルのリストを示します。 このリストはまた、@code{LEFT OUTER JOIN}参照を含むことがあります。 @ref{JOIN, , @code{JOIN}}. を参照してください。 For each table specified, you may optionally specify an alias. @example table_name [[AS] alias] [[USE INDEX (key_list)] | [IGNORE INDEX (key_list)] | FORCE INDEX (key_list)]] @end example As of MySQL Version 3.23.12, you can give hints about which index MySQL should use when retrieving information from a table. This is useful if @code{EXPLAIN} shows that MySQL is using the wrong index from the list of possible indexes. By specifying @code{USE INDEX (key_list)}, you can tell MySQL to use only one of the possible indexes to find rows in the table. The alternative syntax @code{IGNORE INDEX (key_list)} can be used to tell MySQL to not use some particular index. In MySQL 4.0.9 you can also use @code{FORCE INDEX}. This acts likes @code{USE INDEX (key_list)} but with the addition that a table scan is assumed to be VERY expensive. In other words a table scan will only be used if there is no way to use one of the given index to find rows in the table. @code{USE/IGNORE/FORCE KEY} are synonyms for @code{USE/IGNORE/FORCE INDEX}. @item You can refer to a table as @code{tbl_name} (within the current database), or as @code{dbname.tbl_name} to explicitly specify a database. @code{col_name}、@code{tbl_name.col_name}、@code{db_name.tbl_name.col_name}の ようにしてフィールドを表すことができます。 @code{SELECT}ステートメント内での列の参照が曖昧でなければ、@code{tbl_name}や @code{db_name.tbl_name}のようなプリフィックスを詳細に記述する必要はありません。 より明示的なフィールドの指定形式をを必要とする曖昧な参照の例は、@ref{Legal names}を参照のこと。 @item @cindex aliases, for tables @cindex table aliases テーブル参照は、@code{tbl_name AS alias_name}又は@code{tbl_name alias_name}を 使って別名を使用することが可能です: @example mysql> SELECT t1.name, t2.salary FROM employee AS t1, info AS t2 -> WHERE t1.name = t2.name; mysql> SELECT t1.name, t2.salary FROM employee t1, info t2 -> WHERE t1.name = t2.name; @end example @item 出力用に選択されたフィールドは、@code{ORDER BY}節や@code{GROUP BY}節において、 フィールド名、フィールドのエイリアス名、又はフィールド番号にて指し示すことが できます。フィールド番号は1から始まります。 @example mysql> SELECT college, region, seed FROM tournament -> ORDER BY region, seed; mysql> SELECT college, region AS r, seed AS s FROM tournament -> ORDER BY r, s; mysql> SELECT college, region, seed FROM tournament -> ORDER BY 2, 3; @end example 逆順で並べたい場合には、 @code{ORDER BY} 節の中で、あなたが並べたいと思っている フィールドの名前の後ろに、 @code{DESC} (descending) キーワードを 追加します。 デフォルトは昇順です； これは @code{ASC} キーワードを指定したことになります。 @item @code{WHERE} 節で MySQL がサポートする任意の関数を使用することが できます。@xref{Functions}. @item @code{HAVING}節は、@code{select_expression}においてどのフィールドの名前や エイリアス名でも指し示すことができます。 これは最後に適用され、クライアントにアイテムが送られる直前に実行されるので、 最適化されません。 @code{WHERE}節で書くべきものに@code{HAVING}を用いてはいけません。 例えば、次のように書いてはいけません: @example mysql> SELECT col_name FROM tbl_name HAVING col_name > 0; @end example その代わりに、次のように書いてください: @example mysql> SELECT col_name FROM tbl_name WHERE col_name > 0; @end example MySQL バージョン 3.22.5以降では、次のようにクエリを記述することができます: @example mysql> SELECT user,MAX(salary) FROM users GROUP BY user HAVING MAX(salary)>10; @end example MySQLの古いバージョンでは、この代わりに次のように記述できます: @example mysql> SELECT user,MAX(salary) AS sum FROM users GROUP BY user HAVING sum>10; @end example @item The options @code{DISTINCT}, @code{DISTINCTROW} and @code{ALL} specify whether duplicate rows should be returned. The default is (@code{ALL}), all matching rows are returned. @code{DISTINCT} and @code{DISTINCTROW} are synonyms and specify that duplicate rows in the result set should be removed. @item @code{SQL_SMALL_RESULT}, @code{SQL_BIG_RESULT}, @code{SQL_BUFFER_RESULT}, @code{STRAIGHT_JOIN}, @code{HIGH_PRIORITY} は ANSI SQL に対する MySQL 拡張です。 @item @code{HIGH_PRIORITY} は、テーブルの更新よりも @code{SELECT} を優先させます。 これは一度で完了する、とても速いクエリにのみ適用すべきです。 もしリードロックされているテーブルがあったとし、 たとえ update 文がこのテーブルの解除を待っていたとしても、 @code{SELECT HIGH_PRIORITY} クエリは実行されます。 @item @code{SQL_BIG_RESULT} は @code{GROUP BY} や @code{DISTINCT} と共に使用する 事ができ、結果セットが多くのレコードを持つことをオプティマイザに知らせます。 この場合、必要なら MySQL はディスクベースの一時テーブルを直接使用 します。@code{MySQL} はこの場合、@code{GROUP BY} 要素上のキーで一時テーブ ルを行なう代わりにソートを行なうことを選択します。 @item @code{SQL_BUFFER_RESULT} は結果を一時テーブルへ強制的に置きます。これは MySQL がテーブルロックを速く解放して、クライアントに結果セットを 送るために長い時間が掛かる場合の助けになります。 @item @code{SQL_CALC_FOUND_ROWS} (version 4.0.0 and up) tells MySQL to calculate how many rows there would be in the result set, disregarding any @code{LIMIT} clause. The number of rows can then be retrieved with @code{SELECT FOUND_ROWS()}. @xref{Miscellaneous functions}. Please note that in versions prior to 4.1.0 this does not work with @code{LIMIT 0}, which is optimised to return instantly (resulting in a row count of 0). @xref{LIMIT optimisation}. @item @code{SQL_CACHE} tells MySQL to store the query result in the query cache if you are using @code{QUERY_CACHE_TYPE=2} (@code{DEMAND}). @xref{Query Cache}. @item @code{SQL_NO_CACHE} tells MySQL to not allow the query result to be stored in the query cache. @xref{Query Cache}. @item @code{SQL_SMALL_RESULT} (MySQL 固有のオプション) は @code{GROUP BY} か @code{DISTINCT} と共に使用する事ができ、 結果セットが小さくなることをオプティマイザに知らせます。この場合、 MySQL はソートする代わりに、速い一時テーブルを結果の保存のた めに使用します。 MySQL バージョン 3.23 では、これは通常必要ではありません。 @item @cindex @code{GROUP BY}, extensions to ANSI SQL @code{GROUP BY} を使用する場合、@code{GROUP BY} 内のすべてのフィールドを @code{ORDER BY} に記述したかのように、出力レコードは @code{GROUP BY} に従っ てソートされます。MySQL は、@code{ASC} と @code{DESC} を @code{GROUP BY} に記述できるように、@code{GROUP BY} を拡張しています: @example SELECT a,COUNT(b) FROM test_table GROUP BY a DESC @end example @item MySQL は、@code{GROUP BY} 節に記述されていないフィールドを select できるように @code{GROUP BY} の使用を拡張しています。あなたのクエリ から期待した結果を得ない場合、@code{GROUP BY} の説明を読んでください。 @xref{Group by functions}. @item @cindex hints @code{STRAIGHT_JOIN}は、@code{FROM}節にて記述されたテーブルの順序に従って結合するよう、 オプティマイザに強制します。オプティマイザが、テーブルを最適な順序で結合しない 場合に、クエリのスピードアップのためにこれを使用することが可能です。 @xref{EXPLAIN, , @code{EXPLAIN}}. @item @code{LIMIT} 節は、 @code{SELECT} 構文で返されるレコード数を指定するのに 使用されます。 @code{LIMIT} は一つか二つの数字の引数を取ります。 引数が2つ与えられたならば、最初の引数は最初のレコードからのオフセットを示し、 2つめの引数は返すレコードの最大数を示します。 初めのレコードのオフセットは0です(1ではありません)。 To be compatible with PostgreSQL MySQL also supports the syntax: @code{LIMIT # OFFSET #}. @example mysql> SELECT * FROM table LIMIT 5,10; # 6〜15行目を返す @end example To retrieve all rows from a certain offset upto the end of the result set, you can use -1 for the second parameter: @example mysql> SELECT * FROM table LIMIT 95,-1; # Retrieve rows 96-last. @end example もし引数が一つなら、返すべきレコードの最大行数を指定したことになります。 @example mysql> SELECT * FROM table LIMIT 5; # 最初の5行を取り出す @end example いいかえれば、@code{LIMIT n} は @code{LIMIT 0,n} と同じです。 @item @tindex /etc/passwd @code{SELECT}の書式、@code{SELECT ... INTO OUTFILE 'file_name'}は、 選択されたレコードをファイルに書き込みます。 ファイルはサーバ機に作成され、既に存在するファイルであってはなりません (@file{/etc/passwd}のようなファイルの破壊を防止します)。 @code{SELECT ... INTO OUTFILE} は主に、サーバマシン上でとても速くテーブル をダンプすることを意図されています。サーバホストでない別のホスト上で結果ファ イルを生成したい場合は、@code{SELECT ... INTO OUTFILE} を使用できません。 この場合は代わりに、@code{mysqldump --tab} や @code{mysql -e "SELECT ..." > outfile} のようなクライアントプログラムを使用して、ファイルを生成す べきです。 @code{SELECT ... INTO OUTFILE}は、@code{LOAD DATA INFILE}の逆です。 @code{export_options}の構文は、@code{LOAD DATA INFILE}ステートメントの一部で 使われる@code{FIELDS}節や@code{LINES}節と同じような構成です。 @xref{LOAD DATA, , @code{LOAD DATA}}. 結果として取り出されるテキストファイルでは、 以下に示す文字が @code{ESCAPED BY} 指定の文字によってエスケープされます： @itemize @bullet @item @code{ESCAPED BY} 文字自身 @item @code{FIELDS TERMINATED BY} の最初の文字 @item @code{LINES TERMINATED BY} の最初の文字 @end itemize さらに、 @code{ASCII 0} は、@code{ESCAPED BY} 0 (@code{ASCII 48}) にコンバートされます。 いかなる @code{FIELDS TERMINATED BY}, @code{ESCAPED BY}, @code{LINES TERMINATED BY} 指定されている文字も、エスケープしなければならない理由は、 テキストファイルを読み返せれるようにするためなのです。 @code{ASCII 0} はいくつかのページャーでも見れるようにするために エスケープされるのです。 結果のファイルは SQL の文を含んでいないので、何もエスケープする必要はありません。 次は、多くの古いプログラムによって使用されるフォーマットでファイルを得る例 です。 @example SELECT a,b,a+b INTO OUTFILE "/tmp/result.text" FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY "\n" FROM test_table; @end example @item @findex DUMPFILE @code{INTO OUTFILE} の代わりに @code{INTO DUMPFILE} を使用すると、 MySQL はファイルに１レコードだけを書きます。フィールドや行の終端 とすべてのエスケープを含みません。これはファイル内に BLOB を格納したい場合 に便利です。 @item Note that any file created by @code{INTO OUTFILE} and @code{INTO DUMPFILE} is going to be writeable for all users! The reason is that the MySQL server can't create a file that is owned by anyone else than the user it's running as (you should never run @code{mysqld} as root), the file has to be world-writeable so that you can manipulate it. @item ページ／レコードロックとともに ストレ-ジ・エンジン 上で @code{FOR UPDATE} を使 用すると、検査されるレコードは書き込みロックされます。 @end itemize @menu * JOIN:: @code{JOIN} Syntax * UNION:: @code{UNION} Syntax @end menu @node JOIN, UNION, SELECT, SELECT @subsubsection @code{JOIN} 構文 @findex JOIN @findex INNER JOIN @findex CROSS JOIN @findex LEFT JOIN @findex LEFT OUTER JOIN @findex NATURAL LEFT JOIN @findex NATURAL LEFT OUTER JOIN @findex RIGHT JOIN @findex RIGHT OUTER JOIN @findex NATURAL RIGHT JOIN @findex NATURAL RIGHT OUTER JOIN @findex STRAIGHT_JOIN MySQLは、以下に示す@code{SELECT}ステートメントにおける@code{JOIN}構文をサポートします: @example table_reference, table_reference table_reference [CROSS] JOIN table_reference table_reference INNER JOIN table_reference join_condition table_reference STRAIGHT_JOIN table_reference table_reference LEFT [OUTER] JOIN table_reference join_condition table_reference LEFT [OUTER] JOIN table_reference table_reference NATURAL [LEFT [OUTER]] JOIN table_reference @{ OJ table_reference LEFT OUTER JOIN table_reference ON conditional_expr @} table_reference RIGHT [OUTER] JOIN table_reference join_condition table_reference RIGHT [OUTER] JOIN table_reference table_reference NATURAL [RIGHT [OUTER]] JOIN table_reference @end example Where @code{table_reference} is defined as: @findex AS @example table_name [[AS] alias] [[USE INDEX (key_list)] | [IGNORE INDEX (key_list)] | [FORCE INDEX (key_list)]] @end example and @code{join_condition} is defined as: @example ON conditional_expr | USING (column_list) @end example You should generally not have any conditions in the @code{ON} part that are used to restrict which rows you have in the result set (there are exceptions to this rule). If you want to restrict which rows should be in the result, you have to do this in the @code{WHERE} clause. 注意: 3.23.17 より前のバージョンでは、@code{INNER JOIN} は @code{join_condition} を取りません！ @cindex ODBC compatibility @cindex compatibility, with ODBC 上に示す最後の@code{LEFT OUTER JOIN}構文は、ODBCとの互換性のためだけに存在します: @itemize @bullet @item table referenceは、@code{tbl_name AS alias_name}や@code{tblname alias_name}に よる別名を指定することができます: @example mysql> SELECT t1.name, t2.salary FROM employee AS t1, info AS t2 -> WHERE t1.name = t2.name; @end example @item @code{INNER JOIN}と@code{,} (コンマ)は、同義語です。どちらも使用される テーブル間の直積をとります。通常は@code{WHERE}条件にて、テーブルがどのように リンクされるべきかを定義します。 @item @code{ON}条件節は、@code{WHERE}節で使用されるような条件文の書式です。 @item もし、@code{LEFT JOIN} の @code{ON} や @code{USING} において 右側のテーブルにマッチするレコードが無かった場合、 全てのフィールドが@code{NULL}である1つのレコードが、右側のテーブルとして使用されます。 この事実は、あるテーブルについて、他のテーブルに対応するレコードが存在しない レコードを探すということに利用できます: @example mysql> SELECT table1.* FROM table1 -> LEFT JOIN table2 ON table1.id=table2.id -> WHERE table2.id IS NULL; @end example この例は、@code{table1}の内、@code{id}の値が@code{table2}に存在しない全ての レコードを検索します。 (即ち、@code{table2}内のレコードと一致しない@code{table1}の全てのレコード。) もちろん、この場合の@code{table2.id}は、@code{NOT NULL}と定義されているもの と仮定します。 @xref{LEFT JOIN optimisation}. @item @code{USING} @code{(column_list)}節のフィールド名リストは、両方のテーブルに 存在しなければなりません。@code{USING}節が次のように: @example A LEFT JOIN B USING (C1,C2,C3,...) @end example 定義されることは、@code{ON}式がこのように定義されるのと同義です: @example A.C1=B.C1 AND A.C2=B.C2 AND A.C3=B.C3,... @end example @item 同じフィールド名を持つ2つのテーブルの @code{NATURAL [LEFT] JOIN} は、 @code{USING} 節を伴った @code{INNER JOIN} や @code{LEFT JOIN} と 同じとして定義されます。 @item @cindex hints @code{INNER JOIN} and @code{,} (comma) are semantically equivalent. Both do a full join between the tables used. Normally, you specify how the tables should be linked in the WHERE condition. @item @code{RIGHT JOIN} works analogously as @code{LEFT JOIN}. To keep code portable across databases, it's recommended to use @code{LEFT JOIN} instead of @code{RIGHT JOIN}. @item @cindex hints @code{STRAIGHT_JOIN}は、右側のテーブルの前に、常に左側のテーブルを読むことを 除けば、@code{JOIN}と全く同じことです。これは、結合オプティマイザが、不当な 順序でテーブルを出力するようなまれな事態に使用できます。 @item @cindex hints @findex USE INDEX @findex IGNORE INDEX MySQL バージョン 3.23.12 から、テーブルから情報を取り出す時に、 MySQL がどのインデックスを使用すべきかというヒントを与えることが できるようになりました。これは、MySQL が間違ったインデックスを使 用していることを @code{EXPLAIN} が示す場合に有用です。@code{USE INDEX (key_list)} を指定することによって、テーブルからレコードを見つけるために、 指定されたインデックスの一つだけを使用するように MySQL に伝えるこ とができます。別の構文 @code{IGNORE INDEX (key_list)} は、MySQL に特定のインデックスを使用しないように伝えるために使用できます。 @findex FORCE INDEX In MySQL 4.0.9 you can also use @code{FORCE INDEX}. This acts likes @code{USE INDEX (key_list)} but with the addition that a table scan is assumed to be VERY expensive. In other words a table scan will only be used if there is no way to use one of the given index to find rows in the table. @findex USE KEY @findex IGNORE KEY @code{USE/IGNORE KEY} are synonyms for @code{USE/IGNORE INDEX}. @end itemize 例: @example mysql> SELECT * FROM table1,table2 WHERE table1.id=table2.id; mysql> SELECT * FROM table1 LEFT JOIN table2 ON table1.id=table2.id; mysql> SELECT * FROM table1 LEFT JOIN table2 USING (id); mysql> SELECT * FROM table1 LEFT JOIN table2 ON table1.id=table2.id -> LEFT JOIN table3 ON table2.id=table3.id; mysql> SELECT * FROM table1 USE INDEX (key1,key2) -> WHERE key1=1 AND key2=2 AND key3=3; mysql> SELECT * FROM table1 IGNORE INDEX (key3) -> WHERE key1=1 AND key2=2 AND key3=3; @end example @xref{LEFT JOIN optimisation, , @code{LEFT JOIN} optimization}. @node UNION, , JOIN, SELECT @subsubsection @code{UNION} Syntax @findex UNION @example SELECT ... UNION [ALL] SELECT ... [UNION SELECT ...] @end example @code{UNION} is implemented in MySQL 4.0.0. @code{UNION} is used to combine the result from many @code{SELECT} statements into one result set. The columns listed in the select_expression portion of the @code{SELECT} should have the same type. The column names used in the first @code{SELECT} query will be used as the column names for the results returned. The @code{SELECT} commands are normal select commands, but with the following restrictions: @itemize @bullet @item Only the last @code{SELECT} command can have @code{INTO OUTFILE}. @end itemize If you don't use the keyword @code{ALL} for the @code{UNION}, all returned rows will be unique, as if you had done a @code{DISTINCT} for the total result set. If you specify @code{ALL}, then you will get all matching rows from all the used @code{SELECT} statements. If you want to use an @code{ORDER BY} for the total @code{UNION} result, you should use parentheses: @example (SELECT a FROM table_name WHERE a=10 AND B=1 ORDER BY a LIMIT 10) UNION (SELECT a FROM table_name WHERE a=11 AND B=2 ORDER BY a LIMIT 10) ORDER BY a; @end example @findex HANDLER @node HANDLER, INSERT, SELECT, Data Manipulation @subsection @code{HANDLER} Syntax @example HANDLER tbl_name OPEN [ AS alias ] HANDLER tbl_name READ index_name @{ = | >= | <= | < @} (value1,value2,...) [ WHERE ... ] [LIMIT ... ] HANDLER tbl_name READ index_name @{ FIRST | NEXT | PREV | LAST @} [ WHERE ... ] [LIMIT ... ] HANDLER tbl_name READ @{ FIRST | NEXT @} [ WHERE ... ] [LIMIT ... ] HANDLER tbl_name CLOSE @end example The @code{HANDLER} statement provides direct access to the @code{MyISAM} table storage engine interface. The first form of @code{HANDLER} statement opens a table, making it accessible via subsequent @code{HANDLER ... READ} statements. This table object is not shared by other threads and will not be closed until the thread calls @code{HANDLER tbl_name CLOSE} or the thread dies. @c FIX The sentence below needs to be rewritten. The reference to "the condition" is not clear. @c FIX Also all mentions of the LIMIT clause need to be clarified in various sentences below. The second form fetches one row (or more, specified by @code{LIMIT} clause) where the index specified complies to the condition and @code{WHERE} condition is met. If the index consists of several parts (spans over several columns) the values are specified in comma-separated list, providing values only for few first columns is possible. The third form fetches one row (or more, specified by @code{LIMIT} clause) from the table in index order, matching @code{WHERE} condition. The fourth form (without index specification) fetches one row (or more, specified by @code{LIMIT} clause) from the table in natural row order (as stored in datafile) matching @code{WHERE} condition. It is faster than @code{HANDLER tbl_name READ index_name} when a full table scan is desired. @code{HANDLER ... CLOSE} closes a table that was opened with @code{HANDLER ... OPEN}. @code{HANDLER} is a somewhat low-level statement. For example, it does not provide consistency. That is, @code{HANDLER ... OPEN} does @strong{NOT} take a snapshot of the table, and does @strong{NOT} lock the table. This means that after a @code{HANDLER ... OPEN} is issued, table data can be modified (by this or any other thread) and these modifications may appear only partially in @code{HANDLER ... NEXT} or @code{HANDLER ... PREV} scans. The reasons to use this interface instead of normal SQL are: @itemize @bullet @item It's faster than @code{SELECT} because: @itemize @bullet @item A designated storage engine is allocated for the thread in @code{HANDLER OPEN}. @item There is less parsing involved. @item No optimiser and no query checking overhead. @item The used table doesn't have to be locked between two handler requests. @item The handler interface doesn't have to provide a consistent look of the data (for example, dirty-reads are allowed), so the storage engine can do optimisations that SQL doesn't normally allow. @end itemize @item It makes it much easier to port applications that uses an ISAM like interface to MySQL. @item It allows one to traverse a database in a manner that is not easy (in some case impossible) to do with SQL. The handler interface is more natural way to look at data when working with applications that provide an interactive user interfaces to the database. @end itemize @node INSERT, INSERT DELAYED, HANDLER, Data Manipulation @subsection @code{INSERT} 構文 @findex INSERT @example INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO] tbl_name [(col_name,...)] VALUES ((expression | DEFAULT),...),(...),... [ ON DUPLICATE KEY UPDATE col_name=expression, ... ] or INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO] tbl_name [(col_name,...)] SELECT ... or INSERT [LOW_PRIORITY | DELAYED] [IGNORE] [INTO] tbl_name SET col_name=(expression | DEFAULT), ... [ ON DUPLICATE KEY UPDATE col_name=expression, ... ] @end example @code{INSERT}は、既存のテーブルに新しいレコードを挿入します。 @code{INSERT ... VALUES}書式は、値の明示指定を基本としてレコードを挿入します。 @code{INSERT ... SELECT}書式は、他の表(複数可)から抽出したレコードを挿入します。 複数の値リストを用いる@code{INSERT ... VALUES}書式は、 MySQL バージョン 3.22.5以降でサポートされています。 @code{col_name=expression}構文は、 MySQL バージョン 3.22.10以降でサポートされています。 @code{tbl_name}は、レコードを挿入するテーブルです。フィールド名リストは、 後続の値定義ステートメントのフィールドを指し示します: @itemize @bullet @item もしいかなるフィールドも @code{INSERT ... VALUES} や @code{INSERT ... SELECT} などで明示しなければ、全てのフィールドの値が @code{VALUES()} の中に与えられ なくてはなりません。テーブル内のフィールド順が不明な場合、 これを調べるために@code{DESCRIBE tbl_name}を使用して下さい。 @item テーブル内の一部のフィールドしか指定しない場合、指定されなかったフィールドには、 それぞれの初期値が指定されます。初期値の割当ては、 @ref{CREATE TABLE, , @code{CREATE TABLE}}. で述べられています。 You can also use the keyword @code{DEFAULT} to set a column to its default value. (New in MySQL 4.0.3.) This makes it easier to write @code{INSERT} statements that assign values to all but a few columns, because it allows you to avoid writing an incomplete @code{VALUES()} list (a list that does not include a value for each column in the table). Otherwise, you would have to write out the list of column names corresponding to each value in the @code{VALUES()} list. MySQL always has a default value for all fields. This is something that is imposed on MySQL to be able to work with both transactional and not transactional tables. Our view is that checking of fields content should be done in the application and not in the database server. @item @code{expression}は、値リスト内で先頭に近い方のフィールドを参照しなければなりません。 例えば、次のように記述できます: @example mysql> INSERT INTO tbl_name (col1,col2) VALUES(15,col1*2); @end example しかし、次のようには記述できません: @example mysql> INSERT INTO tbl_name (col1,col2) VALUES(col2*2,15); @end example @item キーワード@code{LOW_PRIORITY}を指定した場合、@code{INSERT}の実行はそのテー ブルから値を読み込むクライアントがいなくなるまで遅らされます。この場合、ク ライアントは insert 文が完了するまで待たされます。テーブルが頻繁に使用され る場合、長い時間かかります。これはクライアントを一度に継続させる @code{INSERT DELAYED} と対称的です。 @xref{INSERT DELAYED}. Note that @code{LOW_PRIORITY} should normally not be used with @code{MyISAM} tables as this disables concurrent inserts. @xref{MyISAM}. @item もし @code{IGNORE} キーワードを @code{INSERT} に 値とともに 与えるなら、 テーブル内の @code{PRIMARY} や @code{UNIQUE} キーにすでに存在する重複した ものは無視され、挿入されません。 多重行の値を含むレコードの @code{INSERT} にキーワード @code{IGNORE} を 指定しない場合、テーブルの @code{PRIMARY} キーや @code{UNIQUE} キーに 重複が起こる際に、挿入処理が異常終了します。 @code{IGNORE} を指定した場合、重複するキー値を持つレコードは挿入されません。 C API 関数 @code{mysql_info()} により、テーブルにいくつのレコードが挿入 されたかチェックすることができます。 @item If you specify @code{ON DUPLICATE KEY UPDATE} clause (new in MySQL 4.1.0), and a row is inserted that would cause a duplicate value in @code{PRIMARY} or @code{UNIQUE} key, an @code{UPDATE} of the old row is performed. For example, the command: @example mysql> INSERT INTO table (a,b,c) VALUES (1,2,3) --> ON DUPLICATE KEY UPDATE c=c+1; @end example in case of column @code{a} is declared as @code{UNIQUE} and already holds @code{1} once, would be identical to the @example mysql> UPDATE table SET c=c+1 WHERE a=1; @end example @strong{Note:} that if column @code{b} is unique too, the @code{UPDATE} command would be written as @example mysql> UPDATE table SET c=c+1 WHERE a=1 OR b=2 LIMIT 1; @end example and if @code{a=1 OR b=2} matches several rows, only @strong{one} row will be updated! In general, one should try to avoid using @code{ON DUPLICATE KEY} clause on tables with multiple @code{UNIQUE} keys. When one uses @code{ON DUPLICATE KEY UPDATE}, the @code{DELAYED} option is ignored. @item MySQLが、@code{DONT_USE_DEFAULT_FIELDS}オプションにより制限されていた 場合、@code{NULL}値を許さない全てのフィールドに明示的に値をしないと @code{INSERT}ステートメントは、エラーを生成します。 @xref{configure options, , @code{configure} options}. @item @code{mysql_insert_id} 関数で @code{AUTO_INCREMENT} フィールドに使用された 値を見つけることができます。 @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @end itemize @findex mysql_info() 多重の値リストを持つ @code{INSERT ... SELECT ...} 又は @code{INSERT ... VALUES()} ステートメントを使用する場合、クエリーに関する情報を得るために C API関数 @code{mysql_info()} を使用することができます。 その情報の書式は以下に示す文字列のようになります: @c help SELECT @example Records: 100 Duplicates: 0 Warnings: 0 @end example @code{Duplicates}は、既に存在するユニークインデックスの値と重複することにより、 挿入できなかったレコード数を表します。 @code{Warnings}は、挿入されたフィールドが何らかの疑わしい値であったという 数を表します。警告は、次のような条件の下で発生します: @itemize @bullet @item @code{NOT NULL}定義されたフィールドへの@code{NULL}の挿入。フィールドには 初期値が設定されます。 @item 数値フィールドの範囲を超える値のセット。値は範囲内の限界値に補正されます。 @item 数値フィールドへの @code{`10.34 a'} のような値のセット。引きずっている ゴミは取り除かれ、残りの数値部分が挿入されます。 値が数値として判断できなかった場合、フィールドには @code{0} がセットされます。 @item @code{CHAR}、@code{VARCHAR}、@code{VARCHAR}、@code{TEXT}又は@code{BLOB} フィールドへの最大長を超える文字列の挿入。値はフィールドの最大長に切り捨てられます。 @item 日付又は時刻フィールドへのフィールド属性に反した挿入。その属性に適した ``ゼロ''値がセットされます。 @end itemize @findex REPLACE ... SELECT @findex INSERT ... SELECT @menu * INSERT SELECT:: @code{INSERT ... SELECT} Syntax @end menu @node INSERT SELECT, , INSERT, INSERT @subsubsection @code{INSERT ... SELECT} 構文 @example INSERT [LOW_PRIORITY] [IGNORE] [INTO] tbl_name [(column list)] SELECT ... @end example With @code{INSERT ... SELECT} statement you can quickly insert many rows into a table from one or many tables. @example INSERT INTO tblTemp2 (fldID) SELECT tblTemp1.fldOrder_ID FROM tblTemp1 WHERE tblTemp1.fldOrder_ID > 100; @end example The following conditions hold for an @code{INSERT ... SELECT} statement: @itemize @minus @item The target table of the @code{INSERT} statement cannot appear in the @code{FROM} clause of the @code{SELECT} part of the query because it's forbidden in ANSI SQL to @code{SELECT} from the same table into which you are inserting. (The problem is that the @code{SELECT} possibly would find records that were inserted earlier during the same run. When using subquery clauses, the situation could easily be very confusing!) @item @code{AUTO_INCREMENT} columns work as usual. @item You can use the C API function @code{mysql_info()} to get information about the query. @xref{INSERT}. @item To ensure that the update log/binary log can be used to re-create the original tables, MySQL will not allow concurrent inserts during @code{INSERT ... SELECT}. @end itemize You can of course also use @code{REPLACE} instead of @code{INSERT} to overwrite old rows. @node INSERT DELAYED, UPDATE, INSERT, Data Manipulation @subsection @code{INSERT DELAYED} 構文 @findex INSERT DELAYED @findex DELAYED @cindex INSERT DELAYED @example INSERT DELAYED ... @end example @code{INSERT} 構文の @code{DELAYED} オプションは MySQL 独自の オプションで、これは @code{INSERT} が完全に終了することを待てない クライアントを持つ場合に、とても役立ちます。 これは、ロギングのために MySQL を使用する時の一般的な問題で、完了 に長い時間がかかる @code{SELECT} ステートメントも定期的に実行できます。 @code{DELAYED} は MySQL 3.22.15 で導入されました。 これは ANSI SQL92 に対する MySQL 拡張です。 @code{INSERT DELAYED} only works with @code{ISAM} and @code{MyISAM} tables. Note that as @code{MyISAM} tables supports concurrent @code{SELECT} and @code{INSERT}, if there is no free blocks in the middle of the datafile, you very seldom need to use @code{INSERT DELAYED} with @code{MyISAM}. @xref{MyISAM}. @code{INSERT DELAYED} を使用する時、クライアントは一度 ok となり、テーブル が他のスレッドで使用中でない時にレコードが挿入されます。 @code{INSERT DELAYED} を使用して得られるほかの利益は、 多くのクライアントからの insert が同時に束ねられ、一つのブロックで 書かれることです。 これは多くの別々の insert を実行するより とても速くなります。 現在、キューイングされたレコードは、それらがテーブルに代入されるまで メモリーに保持されているだけです。 これは、もし @code{mysqld} を 強引な方法 (@code{kill -9}) でキルしたり、 @code{mysqld} が予期せず 死んだ場合、キューイングされているレコードはディスクに書かれず失われます！ @code{DELAYED} オプションを @code{INSERT} や @code{REPLACE} で使用する場合、 以下のことがおきます。 ここで ``スレッド'' とは @code{INSERT DELAYED} コマンドを受けたスレッドをさし、 ``ハンドラー'' とは特定のテーブルのための全ての @code{INSERT DELAYED} 構文を操作するスレッドを指します。 @itemize @bullet @item スレッドがあるテーブルに対し @code{DELAYED} 構文を実行するとき、 そのテーブルに対する全ての @code{DELAYED} 構文 を処理するためにハンドラースレッドが作成されます。 もしそのようなハンドラーが存在していない場合には。 @item そのスレッドは、そのハンドラーが @code{DELAYED} ロックを既に持っているか どうかをチェックします； もし持っていないなら、そうするように ハンドラーに告げます。 たとえ他のスレッドが @code{READ} か @code{WRITE} ロックをそのテーブルに 持っていたとしても、 @code{DELAYED} ロックを得ることができます。 しかし、そのハンドラーは全ての @code{ALTER TABLE} ロックか @code{FLUSH TABLES} を待ちます。 そのテーブル構造が最新であるのを 確実にするために。 @item スレッドは @code{INSERT} ステートメントを実行しますが、レコードをテーブル に書く代わりに、ハンドラスレッドによって管理されるキューに最後のレコードの コピーを置きます。文法エラーはスレッドによって通知され、クライアントプログ ラムに報告されます。 @item クライアントは結果行の重複数や @code{AUTO_INCREMENT} の値を 報告できません； それはサーバーから得ることができません。 なぜなら、 @code{INSERT} はインサートオペレーションが完全に終了する前に 返るからです。 もし C API を使用しているなら、 @code{mysql_info()} 関数は 同様の理由によりなにも返しません。 @item 更新ログは、レコードがそのテーブルに insert されたとき、そのハンドラースレッド によって更新されます。 複数レコードの挿入の場合、 更新ログは最初の行が 挿入されたときに更新されます。 @item それぞれの @code{delayed_insert_limit} レコードが書かれた後、そのハンドラーは いかなる @code{SELECT} 文もまだ延期されていないかを確認します。 もしそうなら、続ける前にこれらに対して実行を可能にします。 @item ハンドラーのキュー内にレコードがなくなったとき、テーブルはアンロックされます。 もし新しい @code{INSERT DELAYED} コマンドが @code{delayed_insert_timeout} 秒以内に 受け付けられなければ、ハンドラーは終了します。 @item もし、特定のハンドラーのキュー内に @code{delayed_queue_size} 以上のレコードが 既に延期されているならば、そのスレッドは、キューに余裕がある間待ちます。 これは @code{mysqld} サーバーが delayed されたキューに全ての メモリーを確実に使用しないようにするのに役立ちます。 @item そのハンドラースレッドは MySQL プロセスリストの @code{Command} 項 内に、 @code{delayed_insert} と共に表示されます。 これは @code{FLUSH TABLES} コマンドか @code{KILL thread_id} を実行することで、 kill できるでしょう。 しかし、これらは、終了する前に、キュー内の全てのレコードをテーブルに 保存しようとします。 この間、このスレッドは、他のスレッドから来たいかなる 新しい @code{INSERT} コマンドも受け付けません。 もし、この後に @code{INSERT DELAYED} コマンドを実行するなら、 新しいハンドラースレッドが作成されます。 上記のことは、もし @code{INSERT DELAYED} コマンドが既に走っているなら、 @code{INSERT DELAYED} コマンドは、普通の @code{INSERT} コマンドよりも高い 優先度を持つということです！ 他の update コマンドは @code{INSERT DELAY} キューが空になるまで、 あるいは誰かが @code{KILL thread_id} や @code{FLUSH TABLES} を実行して ハンドラーをキルするまで、 待たされます。 @item 以下のステータス変数は @code{INSERT DELAYED} コマンドについての情報を 与えます： @multitable @columnfractions .30 .55 @item @strong{Variable} @tab @strong{Meaning} @item @code{Delayed_insert_threads} @tab ハンドラースレッドの数 @item @code{Delayed_writes} @tab @code{INSERT DELAYED} で書かれるレコード数 @item @code{Not_flushed_delayed_rows} @tab 書き込みを待つレコード数 @end multitable これらの変数は @code{SHOW STATUS} 構文を発行したり @code{mysqladmin extended-status} コマンドを実行することで見れます. @end itemize 注意: @code{INSERT DELAYED} は、テーブルが使用中でない場合、通常の INSERT よりも遅くなります。@code{INSERT DELAYED} を使用する各テーブルにつ いて別のスレッドを操作するサーバの、追加のオーバーヘッドもあります。これは、 確実にそれを必要とする時にだけ @code{INSERT DELAYED} を使用すべきことを意 味します！ @node UPDATE, DELETE, INSERT DELAYED, Data Manipulation @subsection @code{UPDATE} 構文 @findex UPDATE @example UPDATE [LOW_PRIORITY] [IGNORE] tbl_name SET col_name1=expr1 [, col_name2=expr2 ...] [WHERE where_definition] [ORDER BY ...] [LIMIT rows] or UPDATE [LOW_PRIORITY] [IGNORE] tbl_name [, tbl_name ...] SET col_name1=expr1 [, col_name2=expr2 ...] [WHERE where_definition] @end example @code{UPDATE} はテーブルに存在するレコードのフィールドを、新しい値に更新します。 @code{SET} 節はどのフィールドをどういった値にすべきかを示します。 @code{WHERE} 節が与えられた場合、更新すべきレコードを特定することになります。 それ以外は、全てのレコードを更新します。 @code{ORDER BY} 節が指定された場合、レコードは指定された順に更新されます。 @code{LOW_PRIORITY} キーワードを指定した場合、@code{UPDATE} の実行は、 テーブルを読んでいるクライアントがなくなるまで、遅らされます。 @code{IGNORE} キーワードを指定した場合は、update 文は、 update 中に二重キーのエラーを得たとしても、異常終了しません。 衝突を引き起こすレコードは更新されません。 表記中の @code{tbl_name} からのフィールドをアクセスすると、@code{UPDATE} は現在のフィールド値を使用します。例えば、次のステートメントは @code{age} フィールドにその現在値より１大きい値を設定します: @example mysql> UPDATE persondata SET age=age+1; @end example @code{UPDATE} は左から右に評価されます。例えば、以下の文は @code{age} フィールド を 2倍にし、そのあと1増やします： @example mysql> UPDATE persondata SET age=age*2, age=age+1; @end example もしフィールドに現在もっている値を指定した場合、MySQL はそれを通知し、 値は更新しません。 @findex mysql_info() @code{UPDATE} は変更されたレコード数を返します。 MySQL バージョン 3.22 以上では、C API 関数 @code{mysql_info()} が マッチし更新されたレコード数を返します。また @code{UPDATE} 中に起きた ワーニングの数も返します。 MySQL バージョン 3.23 では、 @code{LIMIT #} で指定した数だけレコードを 変更できます。 Starting with MySQL Version 4.0.4, you can also perform @code{UPDATE} operations that cover multiple tables: @example UPDATE items,month SET items.price=month.price WHERE items.id=month.id; @end example Note: you can not use @code{ORDER BY} or @code{LIMIT} with multi-table @code{UPDATE}. @node DELETE, TRUNCATE, UPDATE, Data Manipulation @subsection @code{DELETE} 構文 @findex DELETE @example DELETE [LOW_PRIORITY] [QUICK] FROM table_name [WHERE where_definition] [ORDER BY ...] [LIMIT rows] or DELETE [LOW_PRIORITY] [QUICK] table_name[.*] [, table_name[.*] ...] FROM table-references [WHERE where_definition] or DELETE [LOW_PRIORITY] [QUICK] FROM table_name[.*] [, table_name[.*] ...] USING table-references [WHERE where_definition] @end example @code{DELETE}は、@code{tbl_name}より、@code{where_definition}にて与えられた条件 を満たすレコードを削除し、削除されたレコード数を返します。 @code{WHERE}節を指定することなしに@code{DELETE}を発行した場合、全てのレコードが 削除されます。 もし @code{AUTOCOMMIT} モードでこの操作を実行するならば、これは @code{TRUNCATE} と同様に動作します。@xref{TRUNCATE, , @code{TRUNCATE}}. MySQL 3.23では、@code{DELETE} は削除したレコード数を 0 で返します。 もし全てのレコードを削除している時に、いくつのレコードが消され、いくつのレコード が スピードを犠牲にしているのか、本当に知りたいならば、 @code{DELETE} 構文を以下のように使用します： @example mysql> DELETE FROM tbl_name WHERE 1>0; @end example これは @code{DELETE FROM tbl_name} を @code{WHERE} 節なしで行うよりも、 とても遅いです。なぜなら一度で消そうとするからです。 キーワード@code{LOW_PRIORITY}を指定した場合、そのテーブルを読んでいるクライアン トがいなくなるまで@code{DELETE}の実行は遅らせられます。 削除されたレコードはリンクリストで維持され、次の@code{INSERT}操作は、古いレコー ド位置を再利用します。 ファイルをより小さくしたい場合は、@code{OPTIMIZE TABLE}ステートメントかテーブル の再編成のために@code{myisamchk}ユティリティを使用してください。 @code{OPTIMIZE TABLE}の方が簡単ですが、@code{myisamchk}の方が早く動作します。 @xref{OPTIMIZE TABLE, , @code{OPTIMIZE TABLE}}. If you specify the word @code{QUICK} then the storage engine will not merge index leaves during delete, which may speed up certain kind of deletes. The first multi-table delete format is supported starting from MySQL 4.0.0. The second multi-table delete format is supported starting from MySQL 4.0.2. The idea is that only matching rows from the tables listed @strong{before} the @code{FROM} or before the @code{USING} clause are deleted. The effect is that you can delete rows from many tables at the same time and also have additional tables that are used for searching. The @code{.*} after the table names is there just to be compatible with @code{Access}: @example DELETE t1,t2 FROM t1,t2,t3 WHERE t1.id=t2.id AND t2.id=t3.id or DELETE FROM t1,t2 USING t1,t2,t3 WHERE t1.id=t2.id AND t2.id=t3.id @end example In the above case we delete matching rows just from tables @code{t1} and @code{t2}. If an @code{ORDER BY} clause is used (available from MySQL 4.0), the rows will be deleted in that order. This is really only useful in conjunction with @code{LIMIT}. For example: @example DELETE FROM somelog WHERE user = 'jcole' ORDER BY timestamp LIMIT 1 @end example This will delete the oldest entry (by @code{timestamp}) where the row matches the @code{WHERE} clause. MySQL-特化 @code{DELETE} の @code{LIMIT rows} オプションは サーバーに消す最大のレコード数をつげます。これは @code{DELETE} コマンドが あまりに多くの時間を取らないために使用されます。 @code{LIMIT} 値よりも affected row の数が少なくなるまで、 単純に @code{DELETE} コマンドを繰り返すだけです。 From MySQL 4.0, you can specify multiple tables in the @code{DELETE} statement to delete rows from one table depending on a particular condition in multiple tables. However, you can not use @code{ORDER BY} or @code{LIMIT} in a multi-table @code{DELETE}. @node TRUNCATE, REPLACE, DELETE, Data Manipulation @subsection @code{TRUNCATE} 構文 @findex TRUNCATE @example TRUNCATE TABLE table_name @end example 3.23 では、@code{COMMIT ; DELETE FROM table_name} と同じことです。 @xref{DELETE}. @code{TRUNCATE TABLE} differs from @code{DELETE FROM ...} in the following ways: @itemize @bullet @item Truncate はテーブルを破棄して再生成するように実装されています。これは多くのレコードを 削除する時により速くなります。 @item トランザクション安全ではありません; @code{COMMIT} が呼ばれたかのように @code{TRUNCATE TABLE} は自動的に現在のトランザクションを終了します。 @item 削除したレコード数を返しません。 @item テーブル定義ファイル @file{table_name.frm} が正しい限り、たとえ、データや インデックスファイルが汚れても、テーブルはこの方法で再生成できます。 @end itemize @code{TRUNCATE} は ORACLE SQL 拡張です。 @node REPLACE, LOAD DATA, TRUNCATE, Data Manipulation @subsection @code{REPLACE} 構文 @findex REPLACE @example REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [(col_name,...)] VALUES (expression,...),(...),... or REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [(col_name,...)] SELECT ... or REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name SET col_name=expression, col_name=expression,... @end example @code{REPLACE}は、テーブル中にある古いレコードの @code{UNIQUE} インデックスか @code{PRIMARY KEY} 上にある値が、新しいレコード と同じ場合に、新しいレコードを挿入する前に 古いレコードを削除するということを除けば、@code{INSERT}と全く同じように 動作します。 @xref{INSERT, ,@code{INSERT}}. In other words, you can't access the values of the old row from a @code{REPLACE} statement. In some old MySQL versions it appeared that you could do this, but that was a bug that has been corrected. To be able to use @code{REPLACE} you must have @code{INSERT} and @code{DELETE} privileges for the table. When you use a @code{REPLACE} command, @code{mysql_affected_rows()} will return 2 if the new row replaced an old row. This is because one row was inserted after the duplicate was deleted. This fact makes it easy to determine whether @code{REPLACE} added or replaced a row: check whether the affected-rows value is 1 (added) or 2 (replaced). Note that unless you use a @code{UNIQUE} index or @code{PRIMARY KEY}, using a @code{REPLACE} command makes no sense, since it would just do an @code{INSERT}. @node LOAD DATA, DO, REPLACE, Data Manipulation @subsection @code{LOAD DATA INFILE} 構文 @findex LOAD DATA INFILE @example LOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE 'file_name.txt' [REPLACE | IGNORE] INTO TABLE tbl_name [FIELDS [TERMINATED BY '\t'] [[OPTIONALLY] ENCLOSED BY ''] [ESCAPED BY '\\' ] ] [LINES TERMINATED BY '\n'] [IGNORE number LINES] [(col_name,...)] @end example @code{LOAD DATA INFILE}ステートメントは、テキストファイルからテーブルへと、 レコードを高速に読み込みます。 @code{LOCAL} キーワードが指定されれば、ファイルは クライアント・ホストから読み込まれます。 @code{LOCAL}が指定されなければ、ファイルはサーバに位置する必要があります (@code{LOCAL}は、MySQL バージョン 3.22.6以降で利用できます)。 セキュリティ上の理由から、サーバからテキストファイルを読み出す時は、 ファイルがデータベースディレクトリに存在するか、 全てに読み込み権限がある必要があります。 また、サーバファイルで @code{LOAD DATA INFILE} を使用するには、 データベースの @code{FILE} 権限も持たなければなりません。 @xref{Privileges provided}. In MySQL 3.23.49 and MySQL 4.0.2 @code{LOCAL} will only work if you have not started @code{mysqld} with @code{--local-infile=0} or if you have not enabled your client to support @code{LOCAL}. @xref{LOAD DATA LOCAL}. もし @code{LOW_PRIORITY} を指定した場合、@code{LOAD DATA} 構文は そのテーブルから他のクライアントが読み込みを行っている間、 遅らされます。 If you specify the keyword @code{CONCURRENT} with a @code{MyISAM} table, then other threads can retrieve data from the table while @code{LOAD DATA} is executing. Using this option will of course affect the performance of @code{LOAD DATA} a bit even if no other thread is using the table at the same time. @code{LOCAL} 使用をすると、クライアント・ホストからサーバ・ホストへ ファイルの内容が転送される分、多少遅くなるでしょう。 いうならば、ローカルのファイルを読み込むのに、 @code{FILE} 権限は必要ないということです。 @c old version If you are using MySQL before Version 3.23.24 you can't read from a FIFO with @code{LOAD DATA INFILE}. If you need to read from a FIFO (for example the output from gunzip), use @code{LOAD DATA LOCAL INFILE} instead. @cindex @code{mysqlimport} @code{mysqlimport}ユティリティは、データファイルの読み込みに使用することができま す。; これは、サーバに@code{LOAD DATA INFILE}コマンドを送信することによって処理 を実現しています。 @code{--local}オプションは、@code{mysqlimport}に、クライアント・ホストからデータ ファイルを読み込ませます。 クライアントとサーバが圧縮プロトコルをサポートしていれば、低速なネットワークでよ り良いパフォーマンスを得るために、@code{--compress}オプションを指定することがで きます。 サーバ・ホストにファイルを置く場合、サーバは、以下のルールを使用します: @itemize @bullet @item 完全なパスでファイル名が与えられた場合、サーバはパス名をそのまま使用します。 @cindex delayed_insert_limit @cindex timeout @item １つ又は複数の構成要素から成る相対パスと共にファイル名が与えられた場合、サーバは 、サーバのデータディレクトリ以下からファイルを探します。 @item ファイル名だけが単に与えられた場合、サーバは、 カレントのデータベースディレクトリを探します。 @end itemize これらのルールは、ファイルが @file{myfile.txt} のように与えられれば データベースディレクトリからファイルが読み出され、 @file{./myfile.txt} のように与えられれば、現在選択しているデータベースのデータデ ィレクトリから ファイルが読み出されるという意味であることに注意して下さい。 例えば、以下の @code{LOAD DATA} 文は、@file{data.txt} ファイルを @code{db1} データベースディレクトリから読みます。 なぜなら、@code{db1} は 現在選択されているデータベースだからです。 たとえ、@code{db2} データベース のテーブルに、ファイルから読み込んだデータを挿入するとしても。： 以下に示すような構文では、ファイルは @code{db1} データベースディレクトリ から読まれます。@code{db2} ではありません: @example mysql> USE db1; mysql> LOAD DATA INFILE "data.txt" INTO TABLE db2.my_table; @end example @code{REPLACE} と @code{IGNORE} キーワードは、すでに存在するユニークキーに 重複しているレコードの入力に対する制御です。 @code{REPLACE} 指定の場合、同じユニークキーを持つ既存のレコードは新しいレコード で置き換えられます。 @code{IGNORE} 指定の場合、既存のレコードのユニークキーと重複するキーをもつ新しい レコードは飛ばされます。 もし、どちらも指定しなかった場合、重複したキーが 見つかった場合エラーが発生し、テキストファイルは無視されます。 @code{LOCAL} キーワードを使用してデータをローカルからロードする場合、 サーバーは操作の途中で転送をとめる方法を知りません。 それでデフォルトの動作としては @code{IGNORE} が指定されたのと 同じになります。 If you use @code{LOAD DATA INFILE} on an empty @code{MyISAM} table, all non-unique indexes are created in a separate batch (like in @code{REPAIR}). This normally makes @code{LOAD DATA INFILE} much faster when you have many indexes. @code{LOAD DATA INFILE}は、@code{SELECT ... INTO OUTFILE}の逆です。 @xref{SELECT, , @code{SELECT}}. データベースからファイルへデータを書き込むには、@code{SELECT ... INTO OUTFILE}を 使用します。 ファイルからデータベースに読み戻すには、@code{LOAD DATA INFILE}を使用します。 @code{FIELDS}と@code{LINES}節の構文は両方のコマンドとも同じです。 どちらの節もオプションですが、両方を指定する場合は、@code{FIELDS}は、@code{LINES} より先に指定しなければなりません。 @code{FIELDS}節を指定した場合、その段落(@code{TERMINATED BY}、@code{[OPTIONALLY] ENCLOSED BY}及び@code{ESCAPED BY})は、少なくとも１つを指定しなければならないこ とを除いて、それらもまたオプションとなります。 @code{FIELDS}節を指定しなかった場合、初期値は以下のように記述したのと等価となり ます: @example FIELDS TERMINATED BY '\t' ENCLOSED BY '' ESCAPED BY '\\' @end example @code{LINES}節を指定しなかった場合、初期値は以下のように記述したのと等価となりま す: @example LINES TERMINATED BY '\n' @end example 言い換えると、@code{LOAD DATA INFILE} の初期値は、出力へ書き込む際に以下のように 振舞います: @itemize @bullet @item 改行をレコードの境界とみなす @item タブ文字によってフィールドを区切る @item クォート文字でフィールドを囲んでいないものとする @item タブ文字や改行文字及び@samp{\}の前に@samp{\}があることにより、それらをフィールド 値の一部のリテラル文字であるとして処理する。 @end itemize 逆に、@code{LOAD DATA INFILE}の初期値は、入力を読み込む際に以下のように振舞いま す: @itemize @bullet @item フィールド間にタブ文字を書く @item いずれのクォート文字でもフィールドを囲まない @item @samp{\}の使用により、フィールド値の中で使用するタブ文字や改行文字、@samp{\}をエ スケープする @item レコードの終りに改行文字を書く @end itemize @code{FIELDS ESCAPED BY '\\'}と書いた場合、単一のバックスラッシュとして読み出さ れる値とするために、２つのバックスラッシュを指定しなければならないことに注意して 下さい。 @code{IGNORE number LINES} オプションはファイルの先頭にあるレコードを無視するの に使用されます： @example mysql> LOAD DATA INFILE "/tmp/file_name" INTO TABLE test IGNORE 1 LINES; @end example データベースからファイルへデータを書き、それから後でそのファイルからデータベース へデータを読み戻すために、@code{SELECT ... INTO OUTFILE}と対に@code{LOAD DATA IN FILE}を使う場合、双方のフィールドとレコードの取扱いに関するオプションは、一致し なければなりません。さもなければ、@code{LOAD DATA INFILE}は適切にファイルを処理 しないでしょう。 フィールドをコンマで区切ってファイルへ書き出すために、@code{SELECT ... INTO OUT FILE}を使用するとすれば: @example mysql> SELECT * INTO OUTFILE 'data.txt' -> FIELDS TERMINATED BY ',' -> FROM ...; @end example コンマ区切りファイルから読み戻すため、正しいステートメントはこうなるでしょう: @example mysql> LOAD DATA INFILE 'data.txt' INTO TABLE table2 -> FIELDS TERMINATED BY ','; @end example その代わりとして次に示すようなステートメントでファイルを読み込もうとしても、正し く動作しないでしょう。なぜなら、これは、@code{LOAD DATA INFILE}に対してフィール ドの間にタブを探すよう指示するからです: @example mysql> LOAD DATA INFILE 'data.txt' INTO TABLE table2 -> FIELDS TERMINATED BY '\t'; @end example おそらく、それぞれの入力行は単一のフィールドとして処理されるでしょう。 @code{LOAD DATA INFILE}は外部ソースからもファイルを読み出すことができます。 例えば、dBASEフォーマットのファイルは、フィールドをコンマで区切られ、ダブルクォ ーテーションで囲まれています。 レコードが改行文字で区切られているとしたら、次に示すフィールド及びレコードの取扱 オプションを指定したコマンドが、このようなファイルを読み込むのに使用できます。 @example mysql> LOAD DATA INFILE 'data.txt' INTO TABLE tbl_name -> FIELDS TERMINATED BY ',' ENCLOSED BY '"' -> LINES TERMINATED BY '\n'; @end example いくつかのフィールド及びレコードの取扱オプションに、空文字列(@code{''})を 指定することがあります。空でないなら、 @code{FIELDS [OPTIONALLY] ENCLOSED BY}と@code{FIELDS ESCAPED BY}の値は 単一の文字でなければなりません。 @code{FIELDS TERMINATED BY}と@code{LINES TERMINATED BY}は２つ以上の文字となるで しょう。 例えば、リターン文字と改行文字のペアで区切られたレコードを書き込んだり、 このようなレコードを含んだファイルを読み込んだりするには、 @code{LINES TERMINATED BY '\r\n'}節を指定します。 @example CREATE TABLE jokes (a int not null auto_increment primary key, joke text not null); LOAD DATA INFILE "/tmp/jokes.txt" INTO TABLE jokes FIELDS TERMINATED BY "" LINES TERMINATED BY "\n%%\n" (joke); @end example @code{FIELDS [OPTIONALLY] ENCLOSED BY}は、フィールドの引用符を制御します。出力の 際(@code{SELECT ... INTO OUTFILE})、@code{OPTIONALLY}語を省いたなら、全てのフィ ールドは@code{ENCLOSED BY}文字で囲まれます。このような出力(フィールド区切りにコ ンマを使用)の例を次に示します: @example "1","a string","100.20" "2","a string containing a , comma","102.20" "3","a string containing a \" quote","102.20" "4","a string containing a \", quote and comma","102.20" @end example @code{OPTIONALLY}を指定すれば、@code{ENCLOSED BY}文字は、 @code{CHAR}フィールド と@code{VARCHAR}フィールドのみ囲むのに使用されます: @example 1,"a string",100.20 2,"a string containing a , comma",102.20 3,"a string containing a \" quote",102.20 4,"a string containing a \", quote and comma",102.20 @end example フィールド値の中における@code{ENCLOSED BY}文字の出現は、@code{ESCAPED BY}文字を その前に置くことによりエスケープされることに注意して下さい。@code{ESCAPED BY}値 に空を指定すると、@code{LOAD DATA INFILE}により正しく読み込めない出力を生成する でしょう。例えば、このようにエスケープ文字を空にした場合、以下に示すような出力と なります。４行目の２つ目のフィールドに、(誤って)フィールドを区切るかのようなクォ ートに続くコンマを含んでいることに注視して下さい: @example 1,"a string",100.20 2,"a string containing a , comma",102.20 3,"a string containing a " quote",102.20 4,"a string containing a ", quote and comma",102.20 @end example 入力において、@code{ENCLOSED BY}文字が指定されており、それがフィールド値の両端に 現れた場合、その文字は取り去られます。(これは、@code{OPTIONALLY}が指定されたかど うかに拘らず、当てはまります;@code{OPTIONALLY}は入力解析には効果がありません。) @code{ESCAPED BY}文字を前置きされた@code{ENCLOSED BY}文字の出現は、現在のフィー ルド値の一部として処理されます。具体的には、あるフィールドがそれ自身、た@code{EN CLOSED BY}文字で始まっている場合、フィールドらの内部で発生する２重の@code{ENCLOS ED BY}文字は、単一の@code{ENCLOSED BY}文字として処理されます。 例えば、@code{ENCLOSED BY '"'}が指定されると、引用符は以下のように操作されます: @example "The ""BIG"" boss" -> The "BIG" boss The "BIG" boss -> The "BIG" boss The ""BIG"" boss -> The ""BIG"" boss @end example @code{FIELDS ESCAPED BY}は、特殊文字をどのように書き込んだり読み込んだりするかを 制御します。 @code{FIELDS ESCAPED BY}文字が空でない場合、出力において次のような文字(文字列) のプリフィックスに使用されます: @itemize @bullet @item @code{FIELDS ESCAPED BY}文字 @item @code{FIELDS [OPTIONALLY] ENCLOSED BY}文字 @item @code{FIELDS TERMINATED BY}値と@code{LINES TERMINATED BY}値の最初の文字 @item ASCII 0 (エスケープ文字の後に続いて実際に書かれる文字はASCII @code{'0'}で、'ゼロ 値'バイトではありません) @end itemize @code{FIELDS ESCAPED BY}文字が空であれば、どの文字もエスケープされません。 特に、フィールド値が上に示した文字を含んでいるならば、エスケープ文字に空を指定す るのはあまり良い考えとは言えないでしょう。 入力において、@code{FIELDS ESCAPED BY}文字が空でない場合、この文字の出現は取り去 られ、後続の文字はフィールド値の一部としてそのまま受け取られます。 例外は、エスケープされた@samp{0}や@samp{N}です (例えば、エスケープ文字が@samp{\}である時の@code{\0}や@code{\N})。 これらのシーケンスは、ASCII 0('ゼロ値'バイト) 、@code{NULL}として処理されます。@ code{NULL}操作の規則は下を参照して下さい。 @samp{\}-escape syntaxに関するこれ以外の情報は、@ref{Literals}参照。 フィールドとレコード操作オプションが確実に相互作用する事例: @itemize @bullet @item @code{LINES TERMINATED BY}が空文字列で@code{FIELDS TERMINATED BY}が空でない場合 、各レコードもまた@code{FIELDS TERMINATED BY}で終らせられます。 @item @code{FIELDS TERMINATED BY}と@code{FIELDS ENCLOSED BY}値が両方とも空(@code{''}) の時、(区切られない)固定長行フォーマットが使用されます。 固定長行フォーマットでは、フィールド間に区切り文字列が使用されません。 その代わり、フィールド値は、フィールドの``表示''幅を使って書き込まれたり、読み込 まれます。 例えば、あるフィールドが@code{INT(7)}で定義されている場合、フィールドの値は7文字 の桁を使って書き込まれます。 入力においてフィールドは、７文字の読み込みにより得られます。 固定長行フォーマットはまた、@code{NULL}値の操作に好んで用いられます;下を参照のこ と。 注意: マルチバイト文字セットを使用している場合は固定長フォーマットは働きま せん。 @end itemize @code{FIELDS}と@code{LINES}オプションによる@code{NULL}値の多様な取扱い: @itemize @bullet @item @code{FIELDS}と@code{LINES}の初期値のために、出力時に@code{NULL}は@code{\N}とし て書き込まれ、入力時に@code{\N}は@code{NULL}として読み込まれます(当然のことなが ら、@code{ESCAPED BY}文字は@samp{\}とします)。 @item @code{FIELDS ENCLOSED BY}が空で無い時、定数@code{NULL}のフィールド値は@code{NULL }値として読み込まれます(これは、文字列@code{'NULL'}として読み込まれる@code{FIELD S ENCLOSED BY}文字列で囲まれた@code{NULL}とは異なります)。 @item @code{FIELDS ESCAPED BY}が空の時、@code{NULL}は@code{NULL}として書き込まれます。 @item 固定長行フォーマット(@code{FIELDS TERMINATED BY}と@code{FIELDS ENCLOSED BY}がい ずれも空の場合に起こります)において、@code{NULL}は、空白文字列として書き込まれま す。 これは、ファイル内では、@code{NULL}値と空白値の見分けがつかないということを示し ていることに注意して下さい。ファイルからデータを読み戻す時に両者を区別しなければ ならない場合、固定長行フォーマットは使用すべきではありません。 @end itemize @code{LOAD DATA INFILE}でサポートされないケース: @itemize @bullet @item 固定長行(@code{FIELDS TERMINATED BY}と@code{FIELDS ENCLOSED BY}の両方が空)と @code{BLOB}フィールド。 @item あるセパレータを他と同じかもしくは他のプリフィックスとした場合、@code{LOAD DATA INFILE}は、正しい入力処理ができないでしょう。 例えば、以下の@code{FIELDS}節は問題の原因となります: @example FIELDS TERMINATED BY '"' ENCLOSED BY '"' @end example @item @code{FIELDS ESCAPED BY}が空で、フィールド値に、@code{FIELDS ENCLOSED BY}値や @code{LINES TERMINATED BY}値の後に@code{FIELDS TERMINATED BY}値がくるようなものを含 む場合、フィールドや行の読み込みが早めに打ち切られてしまいます。 これは、@code{LOAD DATA INFILE}が、フィールドやレコードの終了位置を正しく決めら れないことにより発生します。 @end itemize 次の例は、@code{persondata}テーブルの全てのフィールドを読み込みます: @example mysql> LOAD DATA INFILE 'persondata.txt' INTO TABLE persondata; @end example フィールドリストが指定されていませんから、@code{LOAD DATA INFILE}は、入力レコー ドがテーブルのそれぞれのフィールドを含むものと想定します。 @code{FIELDS}と@code{LINES}の初期値が使用されます。 テーブルの一部のフィールドのみ読み込みたい場合、フィールドリストを指定します: @example mysql> LOAD DATA INFILE 'persondata.txt' -> INTO TABLE persondata (col1,col2,...); @end example テーブル内のフィールド順と入力ファイルのフィールド順が異なる場合にも、@strong{My SQL}にテーブルのフィールドと入力フィールドの対応を教えるために、フィールドリスト を指定しなければなりません。 入力レコードのフィールド数の方が少ない場合、入力フィールド値が与えられないフィー ルドは、初期値が設定されます。 初期値の割当てについては、@ref{CREATE TABLE, , @code{CREATE TABLE}}. で述べられています。 空のフィールド値は変換されます： @itemize @bullet @item 文字型の場合、 フィールドの値は空文字にセットされます。 @item 数値型の場合、フィールドの値は @code{0} にセットされます。 @item 日付と時刻の型の場合、 フィールドの値は ``zero'' の意味する値がセットされます。 @xref{Date and time types}. @end itemize Note that these are the same values that result if you assign an empty string explicitly to a string, numeric, or date or time type explicitly in an @code{INSERT} or @code{UPDATE} statement. @code{TIMESTAMP} フィールドは、フィールド値に @code{NULL} 値が指定されていた場合 もしくは、 フィールドリストが指定されている時に @code{TIMESTAMP} フィールドがそのリストから 除外されていた場合 (最初の@code{TIMESTAMP}フィールドのみ)、現在時刻が設定されるだけです。 入力レコードのフィールド数の方が多い場合、余分なフィールドは無視され、警告の数が 増やされます。 @code{LOAD DATA INFILE}は全ての入力を文字列と文字列とみなすことから、@code{INSER T}ステートメントでできるような@code{ENUM}フィールドや@code{SET}フィールドへの数 値の指定はできません。全ての@code{ENUM}及び@code{SET}値は文字列として与えられな ければいけません！ @findex mysql_info() @code{LOAD DATA INFILE}クエリの終了時、クエリの情報を得るためにC API関数@code{my sql_info()}を使用することができます。情報の書式は以下に示すようなものです: @example Records: 1 Deleted: 0 Skipped: 0 Warnings: 0 @end example @code{LOAD DATA INFILE} が、入力レコードのフィールド数の過不足があった時にも 警告を引き起こす事を除けば、@code{INSERT} ステートメント (@xref{INSERT, , @code{INSERT}}. ) により値が挿入される時に 警告が発生するのと同じ状況下で、警告が発生します。 警告はどこにも保存されません； 警告の数は全てうまくいった場合にだけ 使用できます。 もし警告を知りたい、その警告の理由を知りたいのなら、 一つ方法があります。 @code{SELECT ... INTO OUTFILE} を使用して 他のファイルに落とし、オリジナルのファイルと比べます。 パイプからの読み込みで @code{LOAD DATA} の必要があれば、次のトリッ クを使用できます: @example mkfifo /mysql/db/x/x chmod 666 /mysql/db/x/x cat < /dev/tcp/10.1.1.12/4711 > /nt/mysql/db/x/x mysql -e "LOAD DATA INFILE 'x' INTO TABLE x" x @end example If you are using a version of MySQL older than 3.23.25 you can only do the above with @code{LOAD DATA LOCAL INFILE}. @code{INSERT}と比較した@code{LOAD DATA INFILE}の効率や@code{LOAD DATA INFILE}の 高速化についてのより詳しい情報は、@xref{Insert speed}を参照のこと。 @node DO, , LOAD DATA, Data Manipulation @subsection @code{DO} Syntax @findex DO @example DO expression, [expression, ...] @end example Execute the expression but don't return any results. This is a shorthand of @code{SELECT expression, expression}, but has the advantage that it's slightly faster when you don't care about the result. This is mainly useful with functions that has side effects, like @code{RELEASE_LOCK}. @node Data Definition, Basic User Commands, Data Manipulation, Reference @section Data Definition: @code{CREATE}, @code{DROP}, @code{ALTER} @menu * CREATE DATABASE:: @code{CREATE DATABASE} Syntax * DROP DATABASE:: @code{DROP DATABASE} Syntax * CREATE TABLE:: @code{CREATE TABLE} Syntax * ALTER TABLE:: @code{ALTER TABLE} Syntax * RENAME TABLE:: @code{RENAME TABLE} Syntax * DROP TABLE:: @code{DROP TABLE} Syntax * CREATE INDEX:: @code{CREATE INDEX} Syntax * DROP INDEX:: @code{DROP INDEX} Syntax @end menu @node CREATE DATABASE, DROP DATABASE, Data Definition, Data Definition @subsection @code{CREATE DATABASE} 構文 @findex CREATE DATABASE @example CREATE DATABASE [IF NOT EXISTS] db_name @end example @code{CREATE DATABASE} は与えられた名前のデータベースを作ります。データベースの 名前として許される命名規則は、@ref{Legal names}に依ります。 もし、データベースがすでに存在しているにもかかわらず @code{IF NOT EXISTS} を 指定していなかったら、エラーが発生します。 MySQLにおけるデータベースは、データベース内のテーブルに相当するファイル を含むディレクトリとして実装されます。初期作成後はデータベース内にテーブルは存在 せず、@code{CREATE DATABASE}ステートメントは、MySQLデータディレクトリ下 にディレクトリを作成するだけです。 @cindex @code{mysqladmin} @code{mysqladmin}でもデータベースを作成することができます。 @xref{Client-Side Scripts}. @node DROP DATABASE, CREATE TABLE, CREATE DATABASE, Data Definition @subsection @code{DROP DATABASE} 構文 @findex DROP DATABASE @cindex deleting, database @cindex database, deleting @example DROP DATABASE [IF EXISTS] db_name @end example @code{DROP DATABASE}は、データベース内の全てのテーブルと共にデータベースを破棄し ます。 シンボリックリンクされた @code{DROP DATABASE} を行なうと、リンクとオリジナ ルデータベースの両方が削除されます。 @strong{このコマンドの使用には万全の注意を払って下さい！} @code{DROP DATABASE}は、データベースディレクトリから削除されたファイルの数を返し ます。それぞれのテーブルは@file{.MYD}ファイル／@file{.MYI}ファイル／@file{.frm} ファイルに相当することから、通常この値はテーブルの３倍の数となります。 @code{DROP DATABASE} コマンドは与えられたデータベースディレクトリから、次 の拡張子のすべてのファイルを削除します: @multitable @columnfractions .10 .10 .10 .10 @item @strong{Ext} @tab @strong{Ext} @tab @strong{Ext} @tab @strong{Ext} @item .BAK @tab .DAT @tab .HSH @tab .ISD @item .ISM @tab .ISM @tab .MRG @tab .MYD @item .MYI @tab .db @tab .frm @tab @end multitable 2桁の数値のすべてのサブディレクトリ(@code{RAID} ディレクトリ)も削除されま す。 MySQL 3.22以降では、データベースが存在しないことに起因するエラーを防ぐ ために、キーワード @code{IF EXISTS} を使用することができます。 @cindex @code{mysqladmin} @code{mysqladmin}でもデータベースを破棄することができます。 @xref{Client-Side Scripts}. @node CREATE TABLE, ALTER TABLE, DROP DATABASE, Data Definition @subsection @code{CREATE TABLE} 構文 @findex CREATE TABLE @menu * Silent column changes:: Silent column changes @end menu @example CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name [(create_definition,...)] [table_options] [select_statement] or CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name LIKE old_table_name; create_definition: col_name type [NOT NULL | NULL] [DEFAULT default_value] [AUTO_INCREMENT] [PRIMARY KEY] [reference_definition] or PRIMARY KEY (index_col_name,...) or KEY [index_name] (index_col_name,...) or INDEX [index_name] (index_col_name,...) or UNIQUE [INDEX] [index_name] (index_col_name,...) or FULLTEXT [INDEX] [index_name] (index_col_name,...) or [CONSTRAINT symbol] FOREIGN KEY [index_name] (index_col_name,...) [reference_definition] or CHECK (expr) type: TINYINT[(length)] [UNSIGNED] [ZEROFILL] or SMALLINT[(length)] [UNSIGNED] [ZEROFILL] or MEDIUMINT[(length)] [UNSIGNED] [ZEROFILL] or INT[(length)] [UNSIGNED] [ZEROFILL] or INTEGER[(length)] [UNSIGNED] [ZEROFILL] or BIGINT[(length)] [UNSIGNED] [ZEROFILL] or REAL[(length,decimals)] [UNSIGNED] [ZEROFILL] or DOUBLE[(length,decimals)] [UNSIGNED] [ZEROFILL] or FLOAT[(length,decimals)] [UNSIGNED] [ZEROFILL] or DECIMAL(length,decimals) [UNSIGNED] [ZEROFILL] or NUMERIC(length,decimals) [UNSIGNED] [ZEROFILL] or CHAR(length) [BINARY] or VARCHAR(length) [BINARY] or DATE or TIME or TIMESTAMP or DATETIME or TINYBLOB or BLOB or MEDIUMBLOB or LONGBLOB or TINYTEXT or TEXT or MEDIUMTEXT or LONGTEXT or ENUM(value1,value2,value3,...) or SET(value1,value2,value3,...) index_col_name: col_name [(length)] reference_definition: REFERENCES tbl_name [(index_col_name,...)] [MATCH FULL | MATCH PARTIAL] [ON DELETE reference_option] [ON UPDATE reference_option] reference_option: RESTRICT | CASCADE | SET NULL | NO ACTION | SET DEFAULT table_options: TYPE = @{BDB | HEAP | ISAM | InnoDB | MERGE | MRG_MYISAM | MYISAM @} or AUTO_INCREMENT = # or AVG_ROW_LENGTH = # or CHECKSUM = @{0 | 1@} or COMMENT = "string" or MAX_ROWS = # or MIN_ROWS = # or PACK_KEYS = @{0 | 1 | DEFAULT@} or PASSWORD = "string" or DELAY_KEY_WRITE = @{0 | 1@} or ROW_FORMAT= @{ default | dynamic | fixed | compressed @} or RAID_TYPE= @{1 | STRIPED | RAID0 @} RAID_CHUNKS=# RAID_CHUNKSIZE=# or UNION = (table_name,[table_name...]) or INSERT_METHOD= @{NO | FIRST | LAST @} or DATA DIRECTORY="absolute path to directory" or INDEX DIRECTORY="absolute path to directory" select_statement: [IGNORE | REPLACE] SELECT ... (Some legal select statement) @end example @code{CREATE TABLE}はカレントデータベースに、与えられた名前のテーブルを 作成します。テーブルの名前として許される命名規則は、@xref{Legal names}に 依ります。 カレントデータベースが無い場合や、テーブルが既に存在している場合はエラーが 発生します。 MySQL バージョン 3.22 以降ではテーブル名は @code{db_name.tbl_name} とい う形で与える事もできます。 これはカレントデータベースがあるかどうかにに関係なく動作します。 MySQL バージョン 3.23 からは、テーブル作成時に @code{TEMPORARY} キーワー ドを使用することができます。 一時テーブルの名前はそれぞれの接続内に制限されます。 一時テーブルは、もし、コネクションが落ちた場合、自動で消去されます。 これは、二つの違う接続で、同じ名前の一時テーブルを 衝突することなく、使用できるという事です。 さらには、既に存在するテーブルと同名であっても、一時テーブルは使用できます。 (一時テーブルが削除されるまで、実在するテーブルは隠されます) From MySQL 4.0.2 one must have the @code{CREATE TEMPORARY TABLES} privilege to be able to create temporary tables. MySQL バージョン 3.23 以降では、 @code{IF NOT EXISTS} キーワードを使用 できます。 これは、もしテーブルが既に存在していた場合、エラーを発生させません。 テーブルの構造が一意かどうかまでは検査しないことに注意。 In MySQL 4.1 you can use @code{LIKE} to create a table based on a table definition in another table. In MySQL 4.1 you can also specify the type for a generated column: @example CREATE TABLE foo (a tinyint not null) SELECT b+1 AS 'a' FROM bar; @end example それぞれのテーブルは、データベースディレクトリにおける以下の複数の ファイルで表されます。これは MyISAM 型 のテーブル場合： @multitable @columnfractions .20 .30 @item @strong{File} @tab @strong{Purpose} @item @code{tbl_name.frm} @tab Table definition (form) file @item @code{tbl_name.MYD} @tab Datafile @item @code{tbl_name.MYI} @tab Index file @end multitable フィールドに対する種々の型属性の詳細は、@ref{Column types}を参照のこと。 @itemize @bullet @item @code{NULL}も@code{NOT NULL}も指定されなかった場合、フィールドは@code{NULL}が指 定されたものとして扱われます。 @item 整数型のフィールドには付加属性@code{AUTO_INCREMENT}も指定することができます。 @code{AUTO_INCREMENT}のフィールドに値@code{NULL}又は@code{0}を挿入した場合、フィ ールドには@code{value+1}の値がセットされます。@code{value}は、そのテーブル内の当 該フィールドにおける現在の最大値です。 @code{AUTO_INCREMENT} は @code{1} からはじまります. @xref{mysql_insert_id, , @code{mysql_insert_id()}}. 削除したレコードが、@code{AUTO_INCREMENT}フィールドの最大値を含んでいた場合、 その値は、@code{ISAM} と @code{BDB} テーブルでは、次に再利用されますが、 @code{MyISAM} と @code{InnoDB} テーブルでは再利用されません。 また、テーブル内の全てのレコードを @code{DELETE FROM table_name} (@code{WHERE}節 無しで) を @code{AUTOCOMMIT} モードで使用して削除した場合は、すべてのテーブル型で始めから採 番し直します。 @strong{注意}: 1つのテーブルには1つしか@code{AUTO_INCREMENT}フィールドを指定でき ません。 また、インデックスを指定する必要があります。 MySQL 3.23 は auto_increment フィールドが正の数を持っている場合に だけ、正しく動作します。負の数の挿入はとても大きな正の数の挿入とみなされま す。これは、数値が正から負への 'wrap' over する時の精度の問題を回避するた めと、アクシデント的に 0 を含む auto_increment フィールドを得ることがない ことを確実にするために、行なわれます。 In MyISAM and BDB tables you can specify @code{AUTO_INCREMENT} secondary column in a multi-column key. @xref{example-AUTO_INCREMENT}. @cindex ODBC compatibility @cindex compatibility, with ODBC MySQL をいくつかの ODBC アプリケーションと互換にするために、次の クエリで最後に挿入されたレコードを見つけることができます: @example SELECT * FROM tbl_name WHERE auto_col IS NULL @end example @item @code{CREATE TABLE} automatically commits the current InnoDB transaction if MySQL binary logging is used. @item @code{TIMESTAMP}フィールドにおける@code{NULL}値は、他のフィールド属性と違った扱 われ方をします。定数@code{NULL}を@code{TIMESTAMP}フィールドに格納することはでき ません。@code{NULL}値の指定は現在時刻をセットすることを意味します。 @code{TIMESTAMP}フィールドがこのように振舞うので、通常は@code{NULL}属性や @code{NOT NULL}属性は適用できません。それらを指定しても無視されます。 一方、MySQLクライアントからは、より安易に@code{TIMESTAMP}フィールドを 利用でき、サーバも@code{TIMESTAMP}フィールドへの@code{NULL}の適用を報告しますが 、@code{TIMESTAMP}フィールドは実際には@code{NULL}値を保存することはありません。@ code{DESCRIBE tbl_name}を使用して、テーブル定義文を取得することにより、この現象 を確認することができます。 @code{TIMESTAMP}フィールドに@code{0}を指定することは、@code{NULL}を指定すること と等しくないことに注意してください。なぜなら、@code{0}は@code{TIMESTAMP}の値とし て不正であるからです。 @item @cindex default values A @code{DEFAULT} value has to be a constant, it cannot be a function or an expression. フィールドに対して @code{DEFAULT} 値が指定されない場合は MySQL が 自動的にそれを割り当てます。 フィールドが @code{NULL} を値として取り得る場合は、デフォルト値は @code{NULL} です。 フィールドが @code{NOT NULL} として宣言された場合は、デフォルト値はフィー ルド型に依存します: @itemize @minus @item @code{AUTO_INCREMENT} 定義された以外の数値型のフィールドに対しては、 初期値は@code{0}となります。 @code{AUTO_INCREMENT}フィールドでは、デフォルト値は次のシーケンス番号になります。 @item @code{TIMESTAMP} 型以外の日付型と時刻型のフィールドに対しては、 初期値はその型において適切な``ゼロ''値となります。 例外: フィールドがそのテーブル内で最初の@code{TIMESTAMP}フィールドである場合、初 期値は現在時刻になります。 @xref{Date and time types}. @item @code{ENUM} 以外の文字列型のフィールドに対しては、初期値は空文字列となります。 @code{ENUM} では、デフォルト値は最初の列挙の値です。 @end itemize Default values must be constants. This means, for example, that you cannot set the default for a date column to be the value of a function such as @code{NOW()} or @code{CURRENT_DATE}. @item @code{KEY}は、@code{INDEX}の同義語です。 @item MySQLでは、@code{UNIQUE}キーは固有値しか持つことができません。既に存在 するレコードとキーの値が重複するレコードを挿入しようとした場合、エラーが発生しま す。 @item @tindex PRIMARY KEY @code{PRIMARY KEY} はユニーク @code{KEY} で、すべてのキーフィールドは @code{NOT NULL} として定義されなければならないという特別な制限を伴います。 MySQL ではキーは @code{PRIMARY} と名付けられます。テーブルは @code{PRIMARY KEY} を一つだけ持つことができます。@code{PRIMARY KEY} を持た ない場合に、アプリケーションがテーブル内の @code{PRIMARY KEY} を尋ねると、 MySQL は @code{PRIMARY KEY} として、@code{NULL} フィールドを持た ない最初の @code{UNIQUE} キーを返します。 @item @code{PRIMARY KEY}は複数フィールドインデックスとできます。しかしながら、1つのフ ィールド定義内では@code{PRIMARY KEY}属性を用いて複合インデックスを定義することが できませんので、フィールド定義内における指定は、プライマリ・キーが単独フィールド の場合のみとして下さい。複合フィールドの場合は、 @code{PRIMARY KEY(index_col_name,...)}文を使用しなければなりません。 @item @code{PRIMARY} や @code{UNIQUE} キーが１つのフィールドだけからなり、その型が整数 の場合、それを @code{_rowid} としても参照することができます (バージョン 3.23.11 での新機能)。 @item インデックスに名前を割り当てない場合、一意な名前を付けるために、 @code{index_col_name} 内の最初のフィールド名に(@code{_2}, @code{_3}, ...)のような サフィックスを付加したものが割り当てられます。 テーブルが使用しているインデックス名は、 @code{SHOW INDEX FROM tbl_name}により確認することができます。 @xref{SHOW DATABASE INFO}. @item @cindex @code{NULL} values, and indexes @cindex indexes, and @code{NULL} values @code{MyISAM} テーブルのみが、@code{NULL} 値をもつフィールドに対して インデックスを持つことが出来ます。 その他のテーブル型の場合、フィールドを @code{NOT NULL} で定義しなくてはなりませ ん。 @item @code{col_name(length)}文を共に指定することで、@code{CHAR}フィールド又は @code{VARCHAR}フィールドの一部分だけをインデックスとして定義できます。 これによりインデックスファイルを適度に小さくすることができます。 @xref{Indexes}. @item @cindex @code{BLOB} columns, indexing @cindex indexes, and @code{BLOB} columns @cindex @code{TEXT} columns, indexing @cindex indexes, and @code{TEXT} columns @code{MyISAM} テーブル型のみが、 @code{BLOB} と @code{TEXT} フィールド上に インデックスを持つことが出来ます。 @code{BLOB} と @code{TEXT} フィールドに インデックスを張る場合、常に、インデックスの長さを指定しなくてはなりません： @example CREATE TABLE test (blob_col BLOB, INDEX(blob_col(10))); @end example @item @code{TEXT}フィールドや@code{BLOB}フィールドで @code{ORDER BY} や @code{GROUP BY} を使用すると、 最初の@code{max_sort_length}バイトだけが使用されます。 @xref{BLOB, , @code{BLOB}}. @item MySQL バージョン 3.23.23 以降では、特殊な @code{FULLTEXT} インデックスも 生成できます。それらは全文検索に使用されます。@code{MyISAM} テーブル型 だけが @code{FULLTEXT} インデックスをサポートします。それらは @code{CHAR}, @code{VARCHAR}, @code{TEXT} フィールドからだけ生成できます。 インデックスは常にフィールド全体に起こります。部分インデックスは サポートされません。オペレーションの詳細は @ref{Fulltext Search} を見てください。 @item In MySQL Version 3.23.44 or later, @code{InnoDB} tables support checking of foreign key constraints. @xref{InnoDB}. Note that the @code{FOREIGN KEY} syntax in InnoDB is more restricted than the syntax presented above. InnoDB does not allow @code{index_name} to be specified, and the columns of the referenced table always have to be explicitly named. Starting from 4.0.8 InnoDB supports both @code{ON DELETE} and @code{ON UPDATE} actions on foreign keys. See the InnoDB manual section for the precise syntax. @xref{InnoDB}. For other table types, MySQL Server does parse the @code{FOREIGN KEY}, @code{CHECK}, and @code{REFERENCES} syntax in @code{CREATE TABLE} commands, but without further action being taken. @xref{ANSI diff Foreign Keys}. @item 全ての@code{NULL}フィールドは、1ビット余計に消費し、直近のバイトに丸められます。 @item レコードの最大長は、以下のようにして求められます: @example レコードの長さ = 1 + (フィールドの長さの合計) + (NULLフィールドの数 + 7)/8 + (可変長フィールドの数) @end example @item @code{table_options} と @code{SELECT} オプションは、 MySQL 3.23 以上でのみ実装されます。 テーブル型は： @multitable @columnfractions .25 .70 @item @strong{Table type} @tab @strong{Description} @item BDB または BerkeleyDB @tab トランザクションセーフなテーブル @xref{BDB}. @item HEAP @tab このテーブルのデータは、メモリー内にのみ蓄えられる @xref{HEAP}. @item ISAM @tab オリジナルのテーブル @xref{ISAM}. @item InnoDB @tab レコードロッキングを持ったトランザクション安全テーブル @xref{InnoDB}. @item MERGE @tab 一つのテーブルとして使用される MyISAM テーブルの集まり @xref{MERGE}. @item MRG_MyISAM @tab An alias for MERGE tables @item MyISAM @tab ISAM にかわる 新しい バイナリ互換のテーブル。 @xref{MyISAM}. @end multitable @xref{Table types}. テーブル型が指定され、特定の型が有効でない場合、MySQL は指定され たものに近いテーブル型を選択します。例えば、@code{TYPE=BDB} が指定されて、 MySQL のディストリビューションが @code{BDB} テーブルをサポートし ない場合、代わりにテーブルは @code{MyISAM} として生成されます。 その他のテーブルオプションを使って、テーブルの振る舞いを最適化します。 たいていの場合は、オプションを明示する必要がありません。 明示的に指定されなかった場合、オプションはすべてのテーブル型に作用します。 @multitable @columnfractions .25 .70 @item @strong{Option} @tab @strong{Description} @item @code{AUTO_INCREMENT} @tab あなたがこのテーブルにセットしたい、次の @code{AUTO_INCREMENT} 値 @item @code{AVG_ROW_LENGTH} @tab テーブルに含まれるレコードの長さのおおよその平均値。 可変長のレコードを持つ大きなテーブルに対してのみ、これをセットします。 @item @code{CHECKSUM} @tab MySQL に全てのレコードをチェックさせたい場合、これを 1 にセットします。 (これは更新を遅くさせますが、不整合の生じたテーブルを見つけ出しやすくなります) (MyISAM) @item @code{COMMENT} @tab テーブルの、60文字コメント @item @code{MAX_ROWS} @tab あなたがテーブルに保存したいと考えている最大レコード数。 @item @code{MIN_ROWS} @tab あなたがテーブルに保存したいと考えている最低レコード数 @item @code{PACK_KEYS} @tab より小さいインデックスにしたいなら、これを 1 にします。 これは更新を遅くしますが、読み出しは速くなります (MyISAM, ISAM). Setting this to 0 will disable all packing of keys. Setting this to @code{DEFAULT} (MySQL 4.0) will tell the storage engine to only pack long @code{CHAR}/@code{VARCHAR} columns. @item @code{PASSWORD} @tab @code{.frm} ファイルをパスワード付きで暗号化。 このオプションは、標準の MySQL バージョンではなにも行いません。 @item @code{DELAY_KEY_WRITE} @tab テーブルがクローズされるまでキーテーブルの更新を送らせたい場合、1に設定します(MyISAM)。 @item @code{ROW_FORMAT} @tab レコードがどのように格納されるかを定義します。現在 DYNAMIC と STATIC オプションが MyISAM テーブルのために使用できるだけです。 @end multitable @code{MyISAM} テーブルを使用するならば、MySQL は @code{max_rows * avg_row_length} の値を、テーブルがどのくらい大きくなるか の推定に使用します。 もし、上記のオプションをなにも指定しなかった場合、テーブルの最大サイズは 4G になります。(か、あなたの OS が 2G しかサポートしていなければ 2G まで) この理由は、大きなファイルを本当に必要としない場合は、インデックスをより小 さく、より速くするため、ポインタサイズを小さく保持するためです。 @code{PACK_KEYS} を使用しない場合、デフォルトは文字列だけをパックし、数値 はパックしません。@code{PACK_KEYS=1} を使用するとさらに数値もパックされま す。 バイナリ数値キーをパックする時、MySQL はプレフィックス圧縮を使用 します。これは、同じ数値を多く持つ場合にだけこの大きな恩恵を得るということ を意味します。プレフィックス圧縮は、前のキーの何バイトが次のキーと同じであ るかを示すための余計な1バイトがすべてのキーに必要となることを意味します(注 意: レコードへのポインタは、圧縮の向上のため high-byte-first-order でキー の直後に格納されます)。これは、2つのレコードが同じキー多く持つ場合、後のす べての'同じ'キーは通常2バイト(レコードへのポインタを含む)だけを必要とする ということです。これを、通常のケースと比較してみてください。通常のケースは、 後のキーは'キーの格納サイズ' + ポインタサイズ(通常4)を必要とします。一方、 すべてのキーが全く異なっていると、キーが @code{NULL} 値を持つことができる キーではない場合では、キー毎に1バイトを消費します(この場合、パックされたキー の長さは、キーが @code{NULL} の時にマークのために使用されるのと同じバイト 数で格納されます)。 @item もし @code{CREATE} ステートメントの後に @code{SELECT} を指定するならば、 MySQL は、@code{SELECT} で返ってくる全ての項目を収めるために、 新しいフィールドを作成します。 例えば： @example mysql> CREATE TABLE test (a INT NOT NULL AUTO_INCREMENT, -> PRIMARY KEY (a), KEY(b)) -> TYPE=MyISAM SELECT b,c FROM test2; @end example これは 3つのフィールド a, b, c を @code{MyISAM} テーブルに作成します。 @code{SELECT} ステートメントからのフィールドがテーブルの右側に追加され、上 書きされないことに注意してください。次の例を見てください: @example mysql> SELECT * FROM foo; +---+ | n | +---+ | 1 | +---+ mysql> CREATE TABLE bar (m INT) SELECT n FROM foo; Query OK, 1 row affected (0.02 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> SELECT * FROM bar; +------+---+ | m | n | +------+---+ | NULL | 1 | +------+---+ 1 row in set (0.00 sec) @end example テーブル @code{foo} の各レコードについて、@code{foo} からの値と新しいフィー ルドのデフォルト値を伴って @code{bar} のレコードが 挿入されます。 @code{CREATE TABLE ... SELECT} will not automatically create any indexes for you. This is done intentionally to make the command as flexible as possible. If you want to have indexes in the created table, you should specify these before the @code{SELECT} statement: @example mysql> CREATE TABLE bar (UNIQUE (n)) SELECT n FROM foo; @end example もしデータをテーブルにコピーしている最中にエラーが起きたなら、 このテーブルは自動的に消去されることに注意してください。 更新ログ／バイナリログはオリジナルテーブルを再生成するために使用できます。 MySQL は @code{CREATE TABLE .... SELECT} 中に並行しての挿入を許し ません。 @item @code{RAID_TYPE} オプションは、大規模ファイルをサポートしていない OS 上の 2G/4Gの制限を破る手助けをします。Note that this option is not recommended for filesystem that supports big files! また、@code{RAID} ディレクトリを別の物理 ディスクに置くことにより、IO ボトルネックからさらに速度を得ることができま す。@code{RAID_TYPE} は、MySQL を @code{--with-raid} でコンフィグ すれば、どんな OS 上でも働きます。現在、@code{RAID_TYPE} は @code{STRIPED} だけが許されています(@code{1} と @code{RAID0} はこれの別名 です)。 @code{RAID_TYPE=STRIPED} を @code{MyISAM} テーブルに指定すると、 @code{MyISAM} はデータベースディレクトリ中に 00, 01, 02 という名前の @code{RAID_CHUNKS} サブディレクトリを生成します。これらのディレクトリのそ れぞれに、@code{MyISAM} は @code{table_name.MYD} を生成します。データファ イルにデータが書き込まれる時、@code{RAID} ハンドラは最初の @code{RAID_CHUNKSIZE} *1024 バイトを最初のファイルに、次の @code{RAID_CHUNKSIZE} *1024 バイトを次のファイルにマップします。 @item @code{UNION} は同じテーブルの集まりを一つとして使用したい時に使用されます。 これは MERGE テーブルでだけ動作します。@xref{MERGE, , @code{MERGE}}. 今のところ、@code{MERGE} テーブルをマップするテーブル上に @code{SELECT}, @code{UPDATE}, @code{DELETE} 権限を持つことが必要です。マップされたすべて のテーブルは @code{MERGE} テーブルとして、同じデータベース内にある必要があ ります。 @item If you want to insert data in a @code{MERGE} table, you have to specify with @code{INSERT_METHOD} into with table the row should be inserted. @xref{MERGE, , @code{MERGE}}. This option was introduced in MySQL 4.0.0. @item 生成されたテーブルでは、@code{PRIMARY} キーは最初に置かれ、次にすべての @code{UNIQUE} キー、それから通常のキーが続きます。これは MySQL オ プティマイザを助け、どのキーを使用するかの優先度付けを行ない、重なった @code{UNIQUE} キーをさらにすばやく検出します。 @item @code{DATA DIRECTORY="directory"} または @code{INDEX DIRECTORY="directory"} を使用することで、the storage engine が テーブルとインデックスファイルを置くべき場所を指定できます。@code{--skip-symlink} オプショ ンを使用しない時、これは @code{MySQL} 4.0 で @code{MyISAM} テーブルでだけ 動作します。 @xref{Symbolic links to tables}. @end itemize @node Silent column changes, , CREATE TABLE, CREATE TABLE @subsubsection 暗黙のフィールド定義変更 @cindex silent column changes いくつかのケースにおいてMySQLは、@code{CREATE TABLE}ステートメントで与 えられたフィールド定義を暗黙の内に変更します (これは @code{ALTER TABLE} で起きるかもしれません) @itemize @bullet @item @code{VARCHAR} columns with a length less than four are changed to @code{CHAR}. @item テーブル内にいくつかの可変長フィールドがある場合、結果的にレコード全体が可変長と なります。 その結果、テーブルがいくつかの可変長フィールド(@code{VARCHAR}、@code{TEXT}及び @code{BLOB})を持つならば、3文字より大きいフィールド長の全ての@code{CHAR}フィールドは、 @code{VARCHAR}フィールドに変更されます。 このことは、フィールドの使用方法には影響しません。 MySQLでは、@code{VARCHAR}は文字列を格納するための1つの手段に過ぎません。 MySQLは、スペース埋めのコンバージョンを行いますし、テーブル操作もより速 く行います。 @xref{Table types}. @item @code{TIMESTAMP}フィールドの表示サイズは、2〜14の範囲の偶数でなければなりません。 表示サイズを0や14より大きく指定した場合、サイズは14に強制されます。1から13の範 囲の奇数の場合、大きい方の偶数値に強制されます。 @item @code{TIMESTAMP} フィールドには @code{NULL} を代入できません； @code{NULL} は 現在の日時をセットします。 @code{NULL} and @code{NOT NULL} 属性は通常の方法では適用されず、それらを 与えた場合は無視されます。 @code{DESCRIBE tbl_name} は常に @code{TIMESTAMP} フィールドに @code{NULL} 値が割 り当てられた事を告げます。 @item MySQL は他の SQL データベースの使用している型を MySQL 型に マップします。 @xref{Other-vendor column types}. @end itemize もし MySQL がフィールドの型をあなたが指定したものと違うものにしたかどう かを知りたい場合、テーブルの作成、alter 後に、 @code{DESCRIBE tbl_name} 構文 を発行します。 @cindex @code{myisampack} @code{myisampack}を使用してテーブルを圧縮した場合、別のフィールド定義変更がある 程度起こることがあります。 @xref{Compressed format}. @node ALTER TABLE, RENAME TABLE, CREATE TABLE, Data Definition @subsection @code{ALTER TABLE} 構文 @findex ALTER TABLE @cindex changing, table @cindex table, changing @example ALTER [IGNORE] TABLE tbl_name alter_spec [, alter_spec ...] alter_specification: ADD [COLUMN] create_definition [FIRST | AFTER column_name ] or ADD [COLUMN] (create_definition, create_definition,...) or ADD INDEX [index_name] (index_col_name,...) or ADD PRIMARY KEY (index_col_name,...) or ADD UNIQUE [index_name] (index_col_name,...) or ADD FULLTEXT [index_name] (index_col_name,...) or ADD [CONSTRAINT symbol] FOREIGN KEY [index_name] (index_col_name,...) [reference_definition] or ALTER [COLUMN] col_name @{SET DEFAULT literal | DROP DEFAULT@} or CHANGE [COLUMN] old_col_name create_definition [FIRST | AFTER column_name] or MODIFY [COLUMN] create_definition [FIRST | AFTER column_name] or DROP [COLUMN] col_name or DROP PRIMARY KEY or DROP INDEX index_name or DISABLE KEYS or ENABLE KEYS or RENAME [TO] new_tbl_name or ORDER BY col or table_options @end example @code{ALTER TABLE}は、既存のテーブルの構造変更を可能にします。 例えば、フィールドの追加や削除、インデックスの作成や破棄、既存のフィールド属性の 変更、及びフィールドやテーブルそのものの名前の変更です。 また、テーブルのコメントやテーブルの型式を変更することも可能です。 @xref{CREATE TABLE, , @code{CREATE TABLE}}. もし @code{ALTER TABLE} でフィールド定義を変えても @code{DESCRIBE tbl_name} が フィールドを変更していないと示すなら、これは MySQL が @ref{Silent column changes}. に述べている理由の一つで変更していない可能性が あります。 例えば、 @code{VARCHAR} フィールドを @code{CHAR} にしようとすると, MySQL はそのテーブルに他の可変長のフィールドがあるかぎり、 @code{VARCHAR} のままにしようとします。 @code{ALTER TABLE}はオリジナルのテーブルの一時的なコピーを作成することにより動作 します。 コピーへの変更作業が完了すると、オリジナルのテーブルは削除され新しく 作られた方の名前が変更されます。これは全ての変更が自動的に新しいテーブルに 対して実施されることにより、誤った変更無しに完了します。 @code{ALTER TABLE}が実行されている間、オリジナルのテーブルは他の クライアントから読みだしが可能です。このテーブルへの更新や書き込みは、 新しいテーブルが準備完了となるまで遅らされます。 注意: @code{ALTER TABLE} に @code{RENAME} 以外のオプションを使用する場合、 MySQL は常に一時テーブルを生成します。データが厳密にコピーする必 要がないとしてもです(フィールドの名前を変更する時など)。 We plan to fix this in the future, but as one doesn't normally do @code{ALTER TABLE} that often this isn't that high on our TODO. For MyISAM tables, you can speed up the index recreation part (which is the slowest part of the recreation process) by setting the @code{myisam_sort_buffer_size} variable to a high value. @itemize @bullet @item @code{ALTER TABLE}を使うには、そのテーブルに @code{ALTER}, @code{INSERT}, @code{CREATE} 権限が必要です。 @item @code{IGNORE}はANSI SQL92に対するMySQLの拡張です。 これは、新しいテーブルのユニークキーで重複があった場合の動作を制御します。 @code{IGNORE}が指定されない場合、コピーは異常終了し、ロールバックされます。 @code{IGNORE}が指定された場合、ユニークキーの重複があったレコードに対し、最初の レコードだけを使用し、他は削除されます。 @item 1つの@code{ALTER TABLE}ステートメントの中で、@code{ADD}、@code{ALTER}、 @code{DROP}、それから@code{CHANGE}節の複合的な発行が可能です。 これは、@code{ALTER TABLE}ステートメント毎に1つだけしかこれらの節を 許さないANSI SQL92に対するMySQLの拡張です。 @item @code{CHANGE col_name}、@code{DROP col_name}及び@code{DROP INDEX}はANSI SQL92に対するMySQLの拡張です。 @item @code{MODIFY} は @code{Oracle} の @code{ALTER TABLE} 拡張です。 @item オプション語@code{COLUMN}は蛇足であり、記述を省くことが可能です。 @item 他のオプション無しで@code{ALTER TABLE tbl_name RENAME TO new_name}を使用すると、 MySQLは@code{tbl_name}に一致するテーブルの名前を単純に変更します。 テンポラリテーブルの作成は必要としません。 @xref{RENAME TABLE,, @code{RENAME TABLE}}. @item @code{create_definition}は、@code{CREATE TABLE}における@code{ADD}や@code{CHANGE} と同じ構文を使用します。 @xref{CREATE TABLE, , @code{CREATE TABLE}}. @item @code{CHANGE old_col_name create_definition}節を使用することによりフィールドの名 前を変更することができます。 このようなことを行うためには、フィールドの旧名称と新名称、それからそのフィールド の現在の型を指定する必要があります。例えば、ある@code{INTEGER}フィールドを@code{ a}から@code{b}に変更する場合、以下のように実行することができます: @example mysql> ALTER TABLE t1 CHANGE a b INTEGER; @end example もしフィールドの名前を変えることなく、型だけを変更したい場合であっても、 この @code{CHANGE} 構文は、たとえ同じ名前であっても、 ２つの名前を指定するよう要求します。 例: @example mysql> ALTER TABLE t1 CHANGE b b BIGINT NOT NULL; @end example しかし MySQL バージョン 3.22.16a からは, @code{MODIFY} を使用して、 名称変更をすることなくフィールドの型を変更することができます。 @example mysql> ALTER TABLE t1 MODIFY b BIGINT NOT NULL; @end example @item @code{CHANGE} や @code{MODIFY} を使用して、フィールドの一部にインデックス が存在するようなフィールドを短くしようとしても(例えば @code{VARCHAR} フィー ルドの最初の10文字上ににインデックスがある場合)、インデックスされた文字数 よりもフィールドを短くすることはできません。 @item @code{CHANGE} や @code{MODIFY} を用いてフィールドの型を変更する場合、 MySQLは可能な限り新しい型にデータをコンバートしようと試みます。 @item MySQL バージョン 3.22以降では、 @code{FIRST}又は@code{ADD ... AFTER col_name}を使用して、 テーブルのレコード内の指定した位置に、フィールドを追加すること ができます。 デフォルトでは、フィールドは(そのレコードの)最後に追加されます。 From MySQL Version 4.0.1, you can also use the @code{FIRST} and @code{AFTER} keywords in @code{CHANGE} or @code{MODIFY}. @findex ALTER COLUMN @cindex changing, column @cindex column, changing @cindex changing, field @cindex field, changing @item @code{ALTER COLUMN}は、フィールドの新たな初期値を指定したり、フィールドの古い初 期値を削除したりします。 古い初期値が削除され、フィールドが@code{NULL}を許す場合、新たな初期値は @code{NULL}となります。 @code{NULL}が許されない場合、@ref{CREATE TABLE, , @code{CREATE TABLE}} で 説明されている通り、MySQL は初期値を割り当てます。 @ref{CREATE TABLE, , @code{CREATE TABLE}}. @findex DROP INDEX @cindex deleting, index @cindex index, deleting @item @code{DROP INDEX}は、インデックスを削除します。これはANSI SQL92に対する MySQL の拡張です。 @xref{DROP INDEX}. @item フィールドがテーブルから削除されると、そのフィールドが含まれているインデックスか らもそのフィールドが削除されます。 インデックスを構成する全てのフィールドが削除されると、そのインデックスも削除され ます。 @item テーブルが一つのフィールドだけを含む場合、フィールドは破棄できません。テー ブルを削除するつもりなら、@code{DROP TABLE} を代わりに使用してください。 @findex DROP PRIMARY KEY @cindex deleting, primary key @cindex primary key, deleting @item @code{DROP PRIMARY KEY}は、プライマリ・インデックスを削除します。もしプライマリ インデックスが存在しなければ、そのテーブルの最初の@code{UNIQUE}インデックスが削 除されます。 (MySQLは、明示的に@code{PRIMARY KEY}が指定されなければ最初の@code{UNIQU E}キーを@code{PRIMARY KEY}として扱います。) @findex UNIQUE @findex PRIMARY KEY If you add a @code{UNIQUE INDEX} or @code{PRIMARY KEY} to a table, this is stored before any not @code{UNIQUE} index so that MySQL can detect duplicate keys as early as possible. @findex ORDER BY @item @code{ORDER BY} は指定した順のレコードで新しいテーブルを生成することができ ます。注意: 挿入と削除の後にはこの順序は保持されません。テーブルを、後で order をしたいフィールドの順にしておくと MySQL のソートがより簡単 になる場合があります。このオプションは、主に一定の順でレコードをクエリする つもりであることを知っているときに、主に有用です; テーブルに大きな変更をし た後にこのオプションを使用することで、より高い性能を得ることができるdしょ う。 @findex ALTER TABLE @cindex changing, table @cindex table, changing @item @code{ALTER TABLE} を @code{MyISAM} テーブルに使用する場合、すべての非ユニー クインデックスは(@code{REPAIR} のような)別のバッチで生成されます。これは多 くのインデックスがある場合、@code{ALTER TABLE} をより速くします。 @item Since @strong{MySQL 4.0} the above feature can be activated explicitly. @code{ALTER TABLE ... DISABLE KEYS} makes MySQL to stop updating non-unique indexes for @code{MyISAM} table. @code{ALTER TABLE ... ENABLE KEYS} then should be used to recreate missing indexes. As MySQL does it with special algorithm which is much faster then inserting keys one by one, disabling keys could give a considerable speedup on bulk inserts. @item @findex mysql_info() C API関数@code{mysql_info()}により、どれだけのレコードがコピーされたか、(@code{I GNORE}が指定されている時は)どれだけのレコードがユニークキーの重複により削除され たかを調べることができます。 @item @cindex foreign keys @cindex references @code{FOREIGN KEY}、@code{CHECK}及び@code{REFERENCES}節は、 @code{ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...)} を サポートする InnoDB 型以外のテーブルでは実際には何もしません。 Note that InnoDB does not allow an @code{index_name} to be specified. @xref{InnoDB}. 他のテーブルに対するこれらの構文は、互換性のためだけに用意されており、 他のSQLサーバからのコードの移植を容易にしたり、 参照情報と共にテーブルを作成するようなアプリケーションを動作 させることを目的としています。 @xref{Differences from ANSI}. @end itemize 以下は、@code{ALTER TABLE}の使用例を表す例です。 次に示すように作成されたテーブル@code{t1}から始めます: @example mysql> CREATE TABLE t1 (a INTEGER,b CHAR(10)); @end example テーブル@code{t1}の名前を@code{t2}に変更するには: @example mysql> ALTER TABLE t1 RENAME t2; @end example フィールド @code{a}を @code{INTEGER} から @code{TINYINT NOT NULL} に (名前は同じままで)変更し、 @code{b} を @code{CHAR(10)} から @code{CHAR(20)} に変更しつつ、 名前を @code{b} から @code{c}に変更するには: @example mysql> ALTER TABLE t2 MODIFY a TINYINT NOT NULL, CHANGE b c CHAR(20); @end example @code{TIMESTAMP}を追加し、名前を@code{d}とするには: @example mysql> ALTER TABLE t2 ADD d TIMESTAMP; @end example フィールド@code{d}にインデックスを追加し、フィールド@code{a}をプライマリ・キーと するには: @example mysql> ALTER TABLE t2 ADD INDEX (d), ADD PRIMARY KEY (a); @end example フィールド@code{c}を削除するには: @example mysql> ALTER TABLE t2 DROP COLUMN c; @end example To add a new @code{AUTO_INCREMENT} integer column named @code{c}: @example mysql> ALTER TABLE t2 ADD c INT UNSIGNED NOT NULL AUTO_INCREMENT, -> ADD INDEX (c); @end example ここで我々が @code{c} をインデックス指定したのは、 @code{AUTO_INCREMENT} フィー ルドはインデックスであるべきだからで、 @code{c} を @code{NOT NULL} 指定しているのは インデックスフィールドは @code{NULL} にできないからです。 @code{AUTO_INCREMENT} フィールドを追加した場合、フィールドの値は 自動的にシーケンス番号で埋められます。 最初のシーケンス番号は、@code{ALTER TABLE} 前に @code{SET INSERT_ID=#} を 実行するか、または @code{AUTO_INCREMENT = #} テーブルオプションを使用する ことで設定できます。 @xref{SET OPTION}. MyISAM テーブルでは、@code{AUTO_INCREMENT} フィールドを変更しない場合、シー ケンス番号は影響を受けません。@code{AUTO_INCREMENT} フィールドを破棄し、そ れから別の @code{AUTO_INCREMENT} フィールドを追加した場合、番号は再度 1 か ら始まります。 @xref{ALTER TABLE problems}. @node RENAME TABLE, DROP TABLE, ALTER TABLE, Data Definition @subsection @code{RENAME TABLE} 構文 @findex RENAME TABLE @example RENAME TABLE tbl_name TO new_tbl_name[, tbl_name2 TO new_tbl_name2,...] @end example リネームは自動的に行なわれます。これは、他のスレッドはリネームが動作中はテー ブルのどこにもアクセスできないことを意味します。空のテーブルでテーブルを置 き換えることが可能です: @example CREATE TABLE new_table (...); RENAME TABLE old_table TO backup_table, new_table TO old_table; @end example リネームは左から右に行なわれます。２つのテーブルの名前を交換したい場合には、 次のようにする必要があることを意味します: @example RENAME TABLE old_table TO backup_table, new_table TO old_table, backup_table TO new_table; @end example ２つのデータベースが同じディスク上にあれば、あるデータベースから他のデータ ベースにリネームすることも可能です: @example RENAME TABLE current_database.table_name TO other_database.table_name; @end example @code{RENAME} 実行時には、ロックされたテーブルや有効なトランザクションを持 つことはできません。元のテーブルで @code{ALTER} と @code{DROP} 権限を、新 しいテーブルで @code{CREATE} と @code{INSERT} 権限を持つことも必要です。 MySQL が複数のテーブルのリネームで何らかのエラーに遭遇した場合、 リネームしたすべてのテーブルを逆にリネームし、すべてを元の状態に戻します。 @code{RENAME TABLE} was added in MySQL 3.23.23. @node DROP TABLE, CREATE INDEX, RENAME TABLE, Data Definition @subsection @code{DROP TABLE} Syntax @findex DROP TABLE @cindex deleting, table @cindex table, deleting @example DROP [TEMPORARY] TABLE [IF EXISTS] tbl_name [, tbl_name,...] [RESTRICT | CASCADE] @end example @code{DROP TABLE}は、1つ又は1つ以上のテーブルを破棄します。テーブルの全てのデー タとテーブル定義は@emph{破棄}されますので、このコマンドの使用は慎重に行ってくだ さい！ MySQL バージョン 3.22以降では、テーブルが存在しないことに起因するエラー を防ぐために、キーワード @code{IF EXISTS} を使用することができます。 In 4.1 one gets a @code{NOTE} for all not existing tables when using @code{IF EXISTS}. @xref{SHOW WARNINGS}. @code{RESTRICT} と @code{CASCADE} は移植を簡単にするために許されています。 しばらくはこれらは何も行ないません。 @strong{注意}: @code{DROP TABLE} はトランザクション安全ではなく、自動的に すべてのアクティブトランザクションをコミットします。 (except if you are using 4.1 and the @code{TEMPORARY} key word. ) Option @code{TEMPORARY} is ignored in 4.0. In 4.1 this option works as follows: @itemize @bullet @item Only drops temporary tables. @item It doesn't end a running transactions. @item No access rights is checked. @end itemize Using @code{TEMPORARY} is a good way to ensure that you don't accidently drop a real table. @node CREATE INDEX, DROP INDEX, DROP TABLE, Data Definition @subsection @code{CREATE INDEX} 構文 @findex CREATE INDEX @cindex indexes @cindex indexes, multi-part @cindex multi-part index @example CREATE [UNIQUE|FULLTEXT] INDEX index_name ON tbl_name (col_name[(length)],... ) @end example @code{CREATE INDEX} 構文は MySQL 3.22 より以前のバージョンではなにもし ません。 バージョン 3.22 以降で、@code{CREATE INDEX} はインデックスの作成のために @code{ALTER TABLE} を呼びだしています。 @@xref{ALTER TABLE, , @code{ALTER TABLE}}. 通常、テーブル内の全てのインデックスは @code{CREATE TABLE} で テーブルを作るときに一度に作成されます。 @xref{CREATE TABLE, , @code{CREATE TABLE}}. @code{CREATE INDEX} は既に存在するテーブルに対し、インデックスを追加します。 @code{CREATE INDEX} allows you to add indexes to existing tables. フィールドを @code{(col1,col2,...)} として指定すると、複数フィールドインデックス を作成します。 インデックスの値は、与えられたフィールドの値を連結して、構成されます。 @code{CHAR} と @code{VARCHAR} フィールドでは、インデックスはフィールドの一部分だ けを使用して 作成されます。これは @code{col_name(length)} 構文を使用します。 (@code{BLOB} と @code{TEXT} 節では length が必要です)。 最初の10文字をインデックスとして使用するには、この構文は以下のようにして使用しま す(@code{name} フィールドにインデックスを作ります)： @example mysql> CREATE INDEX part_of_name ON customer (name(10)); @end example フィールドの一部分だけをインデックスに使用すれば、インデックスファイルをはるかに 小さくすることができます。 ほとんどの名前が最初の10文字において通常異なるので、 このインデックスは @code{name} フィールド全部を使用して創り出したインデックスに 比べて遅くなることはありません。また、多くのディスクスペースを節約でき、 @code{INSERT} を速くするのです！ MySQL version 3.23.2 以上で @code{MyISAM} 型のテーブルを使用している 場合、@code{NULL} 値をもつフィールドや、 @code{BLOB}/@code{TEXT} フィールドに対して インデックスを張ることが可能です。 MySQL がどのようにしてインデックスを使用するかは → @ref{MySQL indexes, , MySQL indexes}. @code{FULLTEXT} indexes can index only @code{VARCHAR} and @code{TEXT} columns, and only in @code{MyISAM} tables. @code{FULLTEXT} indexes are available in MySQL Version 3.23.23 and later. @ref{Fulltext Search}. @node DROP INDEX, , CREATE INDEX, Data Definition @subsection @code{DROP INDEX} 構文 @findex DROP INDEX @cindex deleting, index @cindex index, deleting @example DROP INDEX index_name ON tbl_name @end example @code{DROP INDEX} は @code{index_name} という名前のインデックスをテーブル @code{tbl_name} から破棄します。 @code{DROP INDEX} は MySQL バージョン 3.22 より以前のバージョンではなに もしません。 3.22 以降で、@code{DROP INDEX} はインデックスの破棄のために @code{ALTER TABLE} を呼びだしています。 @xref{ALTER TABLE, , @code{ALTER TABLE}}. @node Basic User Commands, Transactional Commands, Data Definition, Reference @section Basic MySQL User Utility Commands @menu * USE:: @code{USE} Syntax * DESCRIBE:: @code{DESCRIBE} Syntax (Get Information About Columns) @end menu @node USE, DESCRIBE, Basic User Commands, Basic User Commands @subsection @code{USE} 構文 @findex USE @example USE db_name @end example @code{USE db_name} 構文は、 MySQL に @code{db_name} データベースを この後のクエリのデフォルトのデータベースにするように指示します。 指定されたデータベースは、セッションの最後まで、あるいは、他の @code{USE} 構文 が発行されるまで残ります： @example mysql> USE db1; mysql> SELECT count(*) FROM mytable; # selects from db1.mytable mysql> USE db2; mysql> SELECT count(*) FROM mytable; # selects from db2.mytable @end example @code{USE} 構文で特定のデータベースをカレントにしても、 他のデータベースのテーブルからアクセスすることを妨げません。 以下は @code{db1} データベースの @code{author} テーブルと、 @code{db2} データベースの @code{editor} テーブルにアクセスする例です： @example mysql> USE db1; mysql> SELECT author_name,editor_name FROM author,db2.editor -> WHERE author.editor_id = db2.editor.editor_id; @end example @cindex Sybase compatibility @cindex compatibility, with Sybase @code{USE} 構文は Sybase の互換のために提供されています。 @node DESCRIBE, , USE, Basic User Commands @subsection @code{DESCRIBE} 構文 (フィールドについての情報を得る) @findex DESC @findex DESCRIBE @example @{DESCRIBE | DESC@} tbl_name [col_name | wild] @end example @code{DESCRIBE} is a shortcut for @code{SHOW COLUMNS FROM}. @xref{SHOW DATABASE INFO}. @code{DESCRIBE} はフィールドについての情報を与えます。 @code{col_name} はフィールドはフィールド名または文字列です。 文字列は SQL @samp{%},@samp{_} ワイルドカードを含めます。 There is no need to enclose the string in quotes. もしフィールドの型があなたが @code{CREATE TABLE} 文で与えた物と違っているなら、 これは MySQL がフィールドの型を変更していることに注意してください。 @xref{Silent column changes}. @cindex Oracle compatibility @cindex compatibility, with Oracle このコマンドは Oracle の互換のためにあります。 @code{SHOW} 構文は似たような情報を提供します。 @xref{SHOW, , @code{SHOW}}. @node Transactional Commands, Fulltext Search, Basic User Commands, Reference @section MySQL Transactional and Locking Commands @menu * COMMIT:: @code{BEGIN/COMMIT/ROLLBACK} Syntax * LOCK TABLES:: @code{LOCK TABLES/UNLOCK TABLES} Syntax * SET TRANSACTION:: @code{SET TRANSACTION} Syntax @end menu @node COMMIT, LOCK TABLES, Transactional Commands, Transactional Commands @subsection @code{BEGIN/COMMIT/ROLLBACK} 構文 @findex START TRANSACTION @findex BEGIN @findex COMMIT @findex ROLLBACK デフォルトでは MySQL は @code{autocommit} モードで動作します。こ れは、更新を実行するとすぐに MySQL が更新をディスクに格納すること を意味します。 もし トランザクションセーフのテーブル(like @code{BDB}, @code{InnoDB}) を使用するなら, 以下のコマンドで MySQL を 非 @code{autocommit} モード状態にすることができます： @example SET AUTOCOMMIT=0 @end example この後、ディスクに変更を格納するためには @code{COMMIT} を使用し、また、変 更を無視するためには @code{ROLLBACK} する必要があります。 ある一連のステートメントのために @code{AUTOCOMMIT} モードからスイッチし たい場合は、@code{START TRANSACTION} か @code{BEGIN} または @code{BEGIN WORK} ステートメントを使用できます。 @example START TRANSACTION; SELECT @@A:=SUM(salary) FROM table1 WHERE type=1; UPDATE table2 SET summmary=@@A WHERE type=1; COMMIT; @end example @code{START TRANSACTION} was added to MySQL 4.0.11; This is the recommended way to start an ad-hoc transaction as this is ANSI SQL syntax. (訳注： 4.0.11より前では、@code{BEGIN} を使用します) 注意: トランザクション安全テーブルを使用していない場合は、@code{autocommit} モードのステータスには依存せずに、変更はすぐに格納されます。 If you do a @code{ROLLBACK} when you have updated a non-transactional table you will get an error (@code{ER_WARNING_NOT_COMPLETE_ROLLBACK}) as a warning. All transaction-safe tables will be restored but any non-transaction-safe table will not change. If you are using @code{START TRANSACTION} or @code{SET AUTOCOMMIT=0}, you should use the MySQL binary log for backups instead of the older update log. Transactions are stored in the binary log in one chunk, upon @code{COMMIT}, to ensure that transactions which are rolled back are not stored. @xref{Binary log}. The following commands automatically end a transaction (as if you had done a @code{COMMIT} before executing the command): @multitable @columnfractions .25 .25 .25 @item @strong{Command} @tab @strong{Command} @tab @strong{Command} @item @code{ALTER TABLE} @tab @code{BEGIN} @tab @code{CREATE INDEX} @item @code{DROP DATABASE} @tab @code{DROP TABLE} @tab @code{RENAME TABLE} @item @code{TRUNCATE} @tab @tab @end multitable You can change the isolation level for transactions with @code{SET TRANSACTION ISOLATION LEVEL ...}. @xref{SET TRANSACTION}. @node LOCK TABLES, SET TRANSACTION, COMMIT, Transactional Commands @subsection @code{LOCK TABLES/UNLOCK TABLES} 構文 @findex LOCK TABLES @findex UNLOCK TABLES @example LOCK TABLES tbl_name [AS alias] @{READ [LOCAL] | [LOW_PRIORITY] WRITE@} [, tbl_name [AS alias] @{READ [LOCAL] | [LOW_PRIORITY] WRITE@} ...] ... UNLOCK TABLES @end example @code{LOCK TABLES} はカレントのスレッドのためにテーブルをロックします。 @code{UNLOCK TABLES} はこのスレッドの全てのロックを解除します。 カレントスレッドによってロックされた全てのテーブルは、 スレッドが他の @code{LOCK TABLES} を発行した場合やサーバーが接続を閉じた場合、 自動で解除されます。 To use @code{LOCK TABLES} in MySQL 4.0.2 you need the global @code{LOCK TABLES} privilege and a @code{SELECT} privilege on the involved tables. In MySQL 3.23 you need to have @code{SELECT}, @code{insert}, @code{DELETE} and @code{UPDATE} privileges for the tables. The main reasons to use @code{LOCK TABLES} are for emulating transactions or getting more speed when updating tables. This is explained in more detail later. スレッドがテーブルに @code{READ} ロックを持つ場合、そのスレッド(と他の全てのスレ ッド)はテーブルからの読み込みだけができます。スレッドがテーブルに @code{WRITE} ロックを持つ場合、 このスレッドだけがテーブルの @code{READ} と @code{WRITE} ができます。 他のスレッドはブロックされます。 @code{READ LOCAL} と @code{READ} の違いは、@code{READ LOCAL} は、ロックが 保持されている間にコンフリクトしない @code{INSERT} ステートメントを実行で きることです。ただし、これはロックを保持している間に MySQL の外で データベースファイルを操作しようとする場合は使用できません。 When you use @code{LOCK TABLES}, you must lock all tables that you are going to use and you must use the same alias that you are going to use in your queries! If you are using a table multiple times in a query (with aliases), you must get a lock for each alias! @code{WRITE} ロックは普通、できる限り更新を行わせるため、 @code{READ} ロックよりも優先順位が高くなっています。 これはあるスレッドが @code{READ} ロックをかけ、それ以外のスレッドが @code{WRITE} を要求した場合、 @code{READ} は、@code{WRITE} スレッドがロックをし、それを解除 するまで待つということです。 @code{LOW_PRIORITY WRITE} を使用すれば、 @code{WRITE} ロックを待っているスレッドに @code{READ} ロックを得させることができ ます。 @code{LOW_PRIORITY WRITE} は @code{READ} ロックをしているスレッドが一つもないと わかっている場合に使用すべきです。 @code{LOCK TABLES} works as follows: @enumerate @item Sort all tables to be locked in a internally defined order (from the user standpoint the order is undefined). @item If a table is locked with a read and a write lock, put the write lock before the read lock. @item Lock one table at a time until the thread gets all locks. @end enumerate This policy ensures that table locking is deadlock free. There is however other things one needs to be aware of with this schema: If you are using a @code{LOW_PRIORITY WRITE} lock for a table, this means only that MySQL will wait for this particlar lock until there is no threads that wants a @code{READ} lock. When the thread has got the @code{WRITE} lock and is waiting to get the lock for the next table in the lock table list, all other threads will wait for the @code{WRITE} lock to be released. If this becomes a serious problem with your application, you should consider converting some of your tables to transactions safe tables. You can safely kill a thread that is waiting for a table lock with @code{KILL}. @xref{KILL}. @code{INSERT DELAYED} で使用しているいかなるテーブルも、ロックすべきではありませ ん。この場合 @code{INSERT} は別のスレッドで行なわれるからです。 通常、全ての単一の @code{UPDATE} 構文においては、テーブルをロックする必要はあり ません； スレッドは、他のスレッドが現在実行している SQL 文に干渉することができません。 これらはテーブルをロックした方がよい、まれな場合です： @itemize @bullet @item テーブルをまとめて多くの操作を実行しようとする場合、使用しようとしているテー ブルをロックするととても速くなります。もちろん、他のスレッドは @code{READ} ロッ クされたテーブルの更新はできませんし、他のスレッドは @code{WRITE} ロックされた テーブルを読むことはできません。 The reason some things are faster under @code{LOCK TABLES} is that MySQL will not flush the key cache for the locked tables until @code{UNLOCK TABLES} is called (normally the key cache is flushed after each SQL statement). This speeds up inserting/updateing/deletes on @code{MyISAM} tables. @item @code{MySQL} のトランザクションをサポートしない the storage engine を使用 している場合、他のスレッドが @code{SELECT},@code{UPDATE} の間に来ないことを 保証したいならば、@code{LOCK TABLES} を使用する必要があります。 次の例は安全のためには @code{LOCK TABLES} を必要とします： @example mysql> LOCK TABLES trans READ, customer WRITE; mysql> SELECT sum(value) FROM trans WHERE customer_id= some_id; mysql> UPDATE customer SET total_value=sum_from_previous_statement -> WHERE customer_id=some_id; mysql> UNLOCK TABLES; @end example @code{LOCK TABLES} を使用しない場合、@code{SELECT} の実行と @code{UPDATE} の 実行を行う間に、他のスレッドが新しい @code{trans} 行を挿入する隙ができます。 @end itemize インクリメント アップデイト (@code{UPDATE customer SET value=value+new_value}) または @code{LAST_INSERT_ID()} 関数の使用により、多くの場合 @code{LOCK TABLES} を回避 できます。 いくつかの場合、ユーザレベルロック: @code{GET_LOCK()} と @code{RELEASE_LOCK()} の使用 によっても解決できます。これらのロックはサーバ内のハッシュテーブル内に保 持され、高速のため @code{pthread_mutex_lock()} で実装されました。 @xref{Miscellaneous functions}. ロックポリシーのさらなる情報については @ref{Internal locking} を見てくださ い。 You can lock all tables in all databases with read locks with the @code{FLUSH TABLES WITH READ LOCK} command. @xref{FLUSH}. This is very convenient way to get backups if you have a filesystem, like Veritas, that can take snapshots in time. @strong{NOTE}: @code{LOCK TABLES} is not transaction-safe and will automatically commit any active transactions before attempting to lock the tables. @node SET TRANSACTION, , LOCK TABLES, Transactional Commands @subsection @code{SET TRANSACTION} 構文 @findex SET TRANSACTION @findex ISOLATION LEVEL @example SET [GLOBAL | SESSION] TRANSACTION ISOLATION LEVEL @{ READ UNCOMMITTED | READ COMMITTED | REPEATABLE READ | SERIALIZABLE @} @end example Sets the transaction isolation level for the global, whole session or the next transaction. The default behaviour is to set the isolation level for the next (not started) transaction. If you use the @code{GLOBAL} keyword, the statement sets the default transaction level globally for all new connections created from that point on. You will need the @code{SUPER} privilege to do this. Using the @code{SESSION} keyword sets the default transaction level for all future transactions performed on the current connection. You can set the default global isolation level for @code{mysqld} with @code{--transaction-isolation=...}. @xref{Command-line options}. @node Fulltext Search, Query Cache, Transactional Commands, Reference @section MySQL Full-text Search @cindex searching, full-text @cindex full-text search @cindex FULLTEXT As of Version 3.23.23, MySQL has support for full-text indexing and searching. Full-text indexes in MySQL are an index of type @code{FULLTEXT}. @code{FULLTEXT} indexes are used with @code{MyISAM} tables and can be created from @code{CHAR}, @code{VARCHAR}, or @code{TEXT} columns at @code{CREATE TABLE} time or added later with @code{ALTER TABLE} or @code{CREATE INDEX}. For large datasets, it will be much faster to load your data into a table that has no @code{FULLTEXT} index, then create the index with @code{ALTER TABLE} (or @code{CREATE INDEX}). Loading data into a table that already has a @code{FULLTEXT} index will be slower. Full-text searching is performed with the @code{MATCH()} function. @example mysql> CREATE TABLE articles ( -> id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY, -> title VARCHAR(200), -> body TEXT, -> FULLTEXT (title,body) -> ); Query OK, 0 rows affected (0.00 sec) mysql> INSERT INTO articles VALUES -> (NULL,'MySQL Tutorial', 'DBMS stands for DataBase ...'), -> (NULL,'How To Use MySQL Efficiently', 'After you went through a ...'), -> (NULL,'Optimising MySQL','In this tutorial we will show ...'), -> (NULL,'1001 MySQL Tricks','1. Never run mysqld as root. 2. ...'), -> (NULL,'MySQL vs. YourSQL', 'In the following database comparison ...'), -> (NULL,'MySQL Security', 'When configured properly, MySQL ...'); Query OK, 6 rows affected (0.00 sec) Records: 6 Duplicates: 0 Warnings: 0 mysql> SELECT * FROM articles -> WHERE MATCH (title,body) AGAINST ('database'); +----+-------------------+------------------------------------------+ | id | title | body | +----+-------------------+------------------------------------------+ | 5 | MySQL vs. YourSQL | In the following database comparison ... | | 1 | MySQL Tutorial | DBMS stands for DataBase ... | +----+-------------------+------------------------------------------+ 2 rows in set (0.00 sec) @end example The @code{MATCH()} function performs a natural language search for a string against a text collection (a set of one or more columns included in a @code{FULLTEXT} index). The search string is given as the argument to @code{AGAINST()}. The search is performed in case-insensitive fashion. For every row in the table, @code{MATCH()} returns a relevance value, that is, a similarity measure between the search string and the text in that row in the columns named in the @code{MATCH()} list. When @code{MATCH()} is used in a @code{WHERE} clause (see example above) the rows returned are automatically sorted with highest relevance first. Relevance values are non-negative floating-point numbers. Zero relevance means no similarity. Relevance is computed based on the number of words in the row, the number of unique words in that row, the total number of words in the collection, and the number of documents (rows) that contain a particular word. It is also possible to perform a boolean mode search. This is explained later in the section. The preceding example is a basic illustration showing how to use the @code{MATCH()} function. Rows are returned in order of decreasing relevance. The next example shows how to retrieve the relevance values explicitly. As neither @code{WHERE} nor @code{ORDER BY} clauses are present, returned rows are not ordered. @example mysql> SELECT id,MATCH title,body AGAINST ('Tutorial') FROM articles; +----+-----------------------------------------+ | id | MATCH (title,body) AGAINST ('Tutorial') | +----+-----------------------------------------+ | 1 | 0.64840710366884 | | 2 | 0 | | 3 | 0.66266459031789 | | 4 | 0 | | 5 | 0 | | 6 | 0 | +----+-----------------------------------------+ 6 rows in set (0.00 sec) @end example The following example is more complex. The query returns the relevance and still sorts the rows in order of decreasing relevance. To achieve this result, you should specify @code{MATCH()} twice. This will cause no additional overhead, because the MySQL optimiser will notice that the two @code{MATCH()} calls are identical and invoke the full-text search code only once. @example mysql> SELECT id, body, MATCH (title,body) AGAINST -> ('Security implications of running MySQL as root') AS score -> FROM articles WHERE MATCH (title,body) AGAINST -> ('Security implications of running MySQL as root'); +----+-------------------------------------+-----------------+ | id | body | score | +----+-------------------------------------+-----------------+ | 4 | 1. Never run mysqld as root. 2. ... | 1.5055546709332 | | 6 | When configured properly, MySQL ... | 1.31140957288 | +----+-------------------------------------+-----------------+ 2 rows in set (0.00 sec) @end example MySQL uses a very simple parser to split text into words. A ``word'' is any sequence of characters consisting of letters, digits, @samp{'}, and @samp{_}. Any ``word'' that is present in the stopword list or is just too short (3 characters or less) is ignored. Every correct word in the collection and in the query is weighted according to its significance in the query or collection. This way, a word that is present in many documents will have lower weight (and may even have a zero weight), because it has lower semantic value in this particular collection. Otherwise, if the word is rare, it will receive a higher weight. The weights of the words are then combined to compute the relevance of the row. Such a technique works best with large collections (in fact, it was carefully tuned this way). For very small tables, word distribution does not reflect adequately their semantic value, and this model may sometimes produce bizarre results. @example mysql> SELECT * FROM articles WHERE MATCH (title,body) AGAINST ('MySQL'); Empty set (0.00 sec) @end example The search for the word @code{MySQL} produces no results in the above example, because that word is present in more than half the rows. As such, it is effectively treated as a stopword (that is, a word with zero semantic value). This is the most desirable behaviour -- a natural language query should not return every second row from a 1GB table. A word that matches half of rows in a table is less likely to locate relevant documents. In fact, it will most likely find plenty of irrelevant documents. We all know this happens far too often when we are trying to find something on the Internet with a search engine. It is with this reasoning that such rows have been assigned a low semantic value in @strong{this particular dataset}. As of Version 4.0.1, MySQL can also perform boolean full-text searches using the @code{IN BOOLEAN MODE} modifier. @example mysql> SELECT * FROM articles WHERE MATCH (title,body) -> AGAINST ('+MySQL -YourSQL' IN BOOLEAN MODE); +----+------------------------------+-------------------------------------+ | id | title | body | +----+------------------------------+-------------------------------------+ | 1 | MySQL Tutorial | DBMS stands for DataBase ... | | 2 | How To Use MySQL Efficiently | After you went through a ... | | 3 | Optimising MySQL | In this tutorial we will show ... | | 4 | 1001 MySQL Tricks | 1. Never run mysqld as root. 2. ... | | 6 | MySQL Security | When configured properly, MySQL ... | +----+------------------------------+-------------------------------------+ @end example This query retrieved all the rows that contain the word @code{MySQL} (note: the 50% threshold is not used), but that do @strong{not} contain the word @code{YourSQL}. Note that a boolean mode search does not automatically sort rows in order of decreasing relevance. You can see this from result of the preceding query, where the row with the highest relevance (the one that contains @code{MySQL} twice) is listed last, not first. A boolean full-text search can also work even without a @code{FULLTEXT} index, although it would be @strong{slow}. The boolean full-text search capability supports the following operators: @table @code @item + A leading plus sign indicates that this word @strong{must be} present in every row returned. @item - A leading minus sign indicates that this word @strong{must not be} present in any row returned. @item By default (when neither plus nor minus is specified) the word is optional, but the rows that contain it will be rated higher. This mimicks the behaviour of @code{MATCH() ... AGAINST()} without the @code{IN BOOLEAN MODE} modifier. @item < > These two operators are used to change a word's contribution to the relevance value that is assigned to a row. The @code{<} operator decreases the contribution and the @code{>} operator increases it. See the example below. @item ( ) Parentheses are used to group words into subexpressions. @item ~ A leading tilde acts as a negation operator, causing the word's contribution to the row relevance to be negative. It's useful for marking noise words. A row that contains such a word will be rated lower than others, but will not be excluded altogether, as it would be with the @code{-} operator. @item * An asterisk is the truncation operator. Unlike the other operators, it should be @strong{appended} to the word, not prepended. @item " The phrase, that is enclosed in double quotes @code{"}, matches only rows that contain this phrase @strong{literally, as it was typed}. @end table And here are some examples: @table @code @item apple banana find rows that contain at least one of these words. @item +apple +juice ... both words. @item +apple macintosh ... word ``apple'', but rank it higher if it also contain ``macintosh''. @item +apple -macintosh ... word ``apple'' but not ``macintosh''. @item +apple +(>pie REPAIR TABLE tbl_name QUICK; @end example @node Fulltext TODO, , Fulltext Fine-tuning, Fulltext Search @subsection Full-text Search TODO @itemize @bullet @item Make all operations with @code{FULLTEXT} index @strong{faster}. @item Proximity operators @item Support for "always-index words". They could be any strings the user wants to treat as words, examples are "C++", "AS/400", "TCP/IP", etc. @item Support for full-text search in @code{MERGE} tables. @item Support for multi-byte charsets. @item Make stopword list to depend of the language of the data. @item Stemming (dependent of the language of the data, of course). @item Generic user-suppliable UDF preparser. @item Make the model more flexible (by adding some adjustable parameters to @code{FULLTEXT} in @code{CREATE/ALTER TABLE}). @end itemize @node Query Cache, , Fulltext Search, Reference @section MySQL Query Cache (4.0.1以上) @cindex Query Cache @cindex @code{SELECT}, Query Cache From version 4.0.1, @code{MySQL server} features a @code{Query Cache}. When in use, the query cache stores the text of a @code{SELECT} query together with the corresponding result that was sent to the client. If an identical query is later received, the server will retrieve the results from the query cache rather than parsing and executing the same query again. @strong{NOTE:} The query cache does not return stale data. When data is modified, any relevant entries in the query cache are flushed. The query cache is extremely useful in an environment where (some) tables don't change very often and you have a lot of identical queries. This is a typical situation for many web servers that use a lot of dynamic content. Below is some performance data for the query cache. (These results were generated by running the MySQL benchmark suite on a Linux Alpha 2 x 500 MHz with 2GB RAM and a 64MB query cache): @itemize @bullet @item If all of the queries you're performing are simple (such as selecting a row from a table with one row); but still differ so that the queries can not be cached, the overhead for having the query cache active is 13%. This could be regarded as the worst case scenario. However, in real life, queries are much more complicated than our simple example so the overhead is normally significantly lower. @item Searches after one row in a one row table is 238% faster. This can be regarded as close to the minimum speedup to be expected for a query that is cached. @item If you want to disable the query cache code set @code{query_cache_size=0}. By disabling the query cache code there is no noticeable overhead. (query cache can be excluded from code with help of configure option @code{--without-query-cache}) @end itemize @menu * Query Cache How:: How The Query Cache Operates * Query Cache Configuration:: Query Cache Configuration * Query Cache in SELECT:: Query Cache Options in @code{SELECT} * Query Cache Status and Maintenance:: Query Cache Status and Maintenance @end menu @node Query Cache How, Query Cache Configuration, Query Cache, Query Cache @subsection How The Query Cache Operates Queries are compared before parsing, thus @example SELECT * FROM tbl_name @end example and @example Select * from tbl_name @end example are regarded as different queries for query cache, so queries need to be exactly the same (byte for byte) to be seen as identical. In addition, a query may be seen as different if for instance one client is using a new communication protocol format or another character set than another client. Queries that uses different databases, uses different protocol versions or the uses different default character sets are considered different queries and cached separately. The cache does work for @code{SELECT CALC_ROWS ...} and @code{SELECT FOUND_ROWS() ...} type queries because the number of found rows is also stored in the cache. If query result was returned from query cache then status variable @code{Com_select} will not be increased, but @code{Qcache_hits} will be. @xref{Query Cache Status and Maintenance}. If a table changes (@code{INSERT}, @code{UPDATE}, @code{DELETE}, @code{TRUNCATE}, @code{ALTER} or @code{DROP TABLE|DATABASE}), then all cached queries that used this table (possibly through a @code{MRG_MyISAM} table!) become invalid and are removed from the cache. Transactional @code{InnoDB} tables that have been changed will be invalidated when a @code{COMMIT} is performed. A query cannot be cached if it contains one of the functions: @multitable @columnfractions .33 .33 .34 @item @strong{Function} @tab @strong{Function} @tab @strong{Function} @item @code{User-Defined Functions} @tab @code{CONNECTION_ID} @tab @code{FOUND_ROWS} @item @code{GET_LOCK} @tab @code{RELEASE_LOCK} @tab @code{LOAD_FILE} @item @code{MASTER_POS_WAIT} @tab @code{NOW} @tab @code{SYSDATE} @item @code{CURRENT_TIMESTAMP} @tab @code{CURDATE} @tab @code{CURRENT_DATE} @item @code{CURTIME} @tab @code{CURRENT_TIME} @tab @code{DATABASE} @item @code{ENCRYPT} (with one parameter) @tab @code{LAST_INSERT_ID} @tab @code{RAND} @item @code{UNIX_TIMESTAMP} (without parameters) @tab @code{USER} @tab @code{BENCHMARK} @end multitable Nor can a query be cached if it contains user variables, references the mysql system database, is of the form @code{SELECT ... IN SHARE MODE}, @code{SELECT ... INTO OUTFILE ...}, @code{SELECT ... INTO DUMPFILE ...} or of the form @code{SELECT * FROM AUTOINCREMENT_FIELD IS NULL} (to retrieve last insert id - ODBC work around). However, @code{FOUND ROWS()} will return the correct value, even if the preceding query was fetched from the cache. In case a query does not use any tables, or uses temporary tables, or if the user has a column privilege for any of the involved tables, that query will not be cached. Before a query is fetched from the query cache, MySQL will check that the user has SELECT privilege to all the involved databases and tables. If this is not the case, the cached result will not be used. @node Query Cache Configuration, Query Cache in SELECT, Query Cache How, Query Cache @subsection Query Cache Configuration The query cache adds a few @code{MySQL} system variables for @code{mysqld} which may be set in a configuration file, on the command-line when starting @code{mysqld}. @itemize @item @code{query_cache_limit} Don't cache results that are bigger than this. (Default 1M). @item @code{query_cache_size} The amount of memory (specified in bytes) allocated to store results from old queries. If this is 0, the query cache is disabled (default). @item @code{query_cache_type} This may be set (only numeric) to @multitable @columnfractions .10 .75 @item @strong{Option} @tab @strong{Description} @item 0 @tab (OFF, don't cache or retrieve results) @item 1 @tab (ON, cache all results except @code{SELECT SQL_NO_CACHE ...} queries) @item 2 @tab (DEMAND, cache only @code{SELECT SQL_CACHE ...} queries) @end multitable @end itemize Inside a thread (connection), the behaviour of the query cache can be changed from the default. The syntax is as follows: @code{QUERY_CACHE_TYPE = OFF | ON | DEMAND} @code{QUERY_CACHE_TYPE = 0 | 1 | 2} @multitable @columnfractions .20 .70 @item @strong{Option} @tab @strong{Description} @item 0 or OFF @tab Don't cache or retrieve results. @item 1 or ON @tab Cache all results except @code{SELECT SQL_NO_CACHE ...} queries. @item 2 or DEMAND @tab Cache only @code{SELECT SQL_CACHE ...} queries. @end multitable @node Query Cache in SELECT, Query Cache Status and Maintenance, Query Cache Configuration, Query Cache @subsection Query Cache Options in @code{SELECT} There are two possible query cache related parameters that may be specified in a @code{SELECT} query: @findex SQL_CACHE @findex SQL_NO_CACHE @multitable @columnfractions .20 .80 @item @strong{Option} @tab @strong{Description} @item @code{SQL_CACHE} @tab If @code{QUERY_CACHE_TYPE} is @code{DEMAND}, allow the query to be cached. If @code{QUERY_CACHE_TYPE} is @code{ON}, this is the default. If @code{QUERY_CACHE_TYPE} is @code{OFF}, do nothing. @item @code{SQL_NO_CACHE} @tab Make this query non-cachable, don't allow this query to be stored in the cache. @end multitable @node Query Cache Status and Maintenance, , Query Cache in SELECT, Query Cache @subsection Query Cache Status and Maintenance With the @code{FLUSH QUERY CACHE} command you can defragment the query cache to better utilise its memory. This command will not remove any queries from the cache. @code{FLUSH TABLES} also flushes the query cache. The @code{RESET QUERY CACHE} command removes all query results from the query cache. You can check whether the query cache is present in your MySQL version: @example mysql> SHOW VARIABLES LIKE 'have_query_cache'; +------------------+-------+ | Variable_name | Value | +------------------+-------+ | have_query_cache | YES | +------------------+-------+ 1 row in set (0.00 sec) @end example You can monitor query cache performance in @code{SHOW STATUS}: @multitable @columnfractions .30 .50 @item @strong{Variable} @tab @strong{Description} @item @code{Qcache_queries_in_cache} @tab Number of queries registered in the cache. @item @code{Qcache_inserts} @tab Number of queries added to the cache. @item @code{Qcache_hits} @tab Number of cache hits. @item @code{Qcache_lowmem_prunes} @tab Number of queries that were deleted from cache because of low memory. @item @code{Qcache_not_cached} @tab Number of non-cached queries (not cachable, or due to @code{QUERY_CACHE_TYPE}). @item @code{Qcache_free_memory} @tab Amount of free memory for query cache. @item @code{Qcache_free_blocks} @tab Number of free memory blocks in query cache. @item @code{Qcache_total_blocks} @tab Total number of blocks in query cache. @end multitable Total number of queries = @code{Qcache_inserts} + @code{Qcache_hits} + @code{Qcache_not_cached}. The query cache uses variable length blocks, so @code{Qcache_total_blocks} and @code{Qcache_free_blocks} may indicate query cache memory fragmentation. After @code{FLUSH QUERY CACHE} only a single (big) free block remains. Note: Every query needs a minimum of two blocks (one for the query text and one or more for the query results). Also, every table that is used by a query needs one block, but if two or more queries use same table only one block needs to be allocated. You can use the @code{Qcache_lowmem_prunes} status variable to tune the query cache size. It counts the number of queries that have been removed from the cache to free up memory for caching new queries. The query cache uses a @code{least recently used} (@code{LRU}) strategy to decide which queries to remove from the cache. @node Table types, Clients, Reference, Top @chapter MySQL テーブル型 @cindex table types, choosing @cindex @code{BDB} table type @cindex @code{BerkeleyDB} table type @cindex @code{HEAP} table type @cindex @code{ISAM} table type @cindex @code{InnoDB} table type @cindex @code{MERGE} table type @cindex MySQL table types @cindex @code{MyISAM} table type @cindex types, of tables @c We should update this listing. Note that ISAM is deprecated, @c update the version number, list InnoDB as one of the preferred table @c types and include DYNAMIC and MERGE type tables. Perhaps when 4.0 goes @c stable would be the best time to do this? MySQL Version 3.23.6では、@code{ISAM}、@code{HEAP} そして @code{MyISAM}の 三つの基本的なテーブル形式を使うことができます。もっと新しいバージョンで は、コンパイルする方法によって@code{InnoDB} や @code{BDB} といった形式も サポートしています。 新しいテーブルを作成する際にどのテーブル形式を使用するか指定すればよろしい わけですが、無指定の場合は通常 @code{MyISAM} になります。 @c We should consider removing this or making a new section 'What happens when a @c table is created'. Currently it seems a bit out of place and not that @c helpful. MySQL will always create a @file{.frm} file to hold the table and column definitions. The table's index and data will be stored in one or more other files, depending on the table type. If you try to use a table type that is not compiled-in or activated, MySQL will instead create a table of type @code{MyISAM}. This behaviour is convenient when you want to copy tables between MySQL servers that support different table types. (Perhaps your master server supports transactional storage engines for increased safety, while the slave servers use only non-transactional storage engines for greater speed.) This automatic change of table types can be confusing for new MySQL users. We plan to fix this by introducing warnings in the new client-server protocol in version 4.1 and generating a warning when a table type is automatically changed. @code{ALTER TABLE} 文を使用すれば、テーブルを違う形式に変更できます。 @xref{ALTER TABLE, , @code{ALTER TABLE}}. MySQL では、二つの違う種類のテーブルをサポートしていることに注意してください。 一つはトランザクションセーフのテーブル(@code{BDB}, @code{InnoDB})、 もう一つはトランザクションを持たないテーブル (@code{HEAP}, @code{ISAM}, @code{MERGE}, and @code{MyISAM}). トランザクションセーフのテーブル(Transaction Safe Tables) の利点は(TST): @itemize @bullet @item Safer. Even if MySQL crashes or you get hardware problems, you can get your data back, either by automatic recovery or from a backup the transaction log. @item You can combine many statements and accept these all in one go with the @code{COMMIT} command. @item You can execute @code{ROLLBACK} to ignore your changes (if you are not running in auto-commit mode). @item If an update fails, all your changes will be restored. (With NTST tables all changes that have taken place are permanent) @item Can provide better concurrency if the table gets many updates concurrently with reads. @end itemize Note that to use @code{InnoDB} tables you have to use at least the @code{innodb_data_file_path} startup option. @xref{InnoDB start}. 非トランザクションセーフ(Not Transaction Safe Tables)のテーブルの利点は(NTST): @itemize @bullet @item Much faster as there is no transaction overhead. @item Will use less disk space as there is no overhead of transactions. @item Will use less memory to do updates. @end itemize You can combine TST and NTST tables in the same statements to get the best of both worlds. @menu * MyISAM:: @code{MyISAM} tables * MERGE:: @code{MERGE} tables * ISAM:: @code{ISAM} tables * HEAP:: @code{HEAP} tables * InnoDB:: @code{InnoDB} tables * BDB:: @code{BDB} or @code{BerkeleyDB} tables @end menu @node MyISAM, MERGE, Table types, Table types @section @code{MyISAM} テーブル (3.23.0以上) @code{MyISAM} は、MySQL Version 3.23 でのデフォルトのテーブル形式です． これは @code{ISAM} コードを基にし、多くの便利な拡張機能を持っています。 インデックスは @code{.MYI} (MYIndex) 拡張子のつくファイルに保存され、 データは、 @code{.MYD} (MYData) 拡張子のつくファイルに保存されます。 @code{myisamchk} ユーティリティを使用して、 @code{MyISAM} テーブルの 検査・修復が可能です。 @xref{Crash recovery}. @code{myisampack} コマンドを使用して、@code{MyISAM} を圧縮して 小さくすることが可能です @xref{myisampack, , @code{myisampack}}. The following is new in @code{MyISAM}: @itemize @bullet @item There is a flag in the @code{MyISAM} file that indicates whether the table was closed correctly. If @code{mysqld} is started with @code{--myisam-recover}, @code{MyISAM} tables will automatically be checked and/or repaired on open if the table wasn't closed properly. @item You can @code{INSERT} new rows in a table that doesn't have free blocks in the middle of the datafile, at the same time other threads are reading from the table (concurrent insert). An free block can come from an update of a dynamic length row with much data to a row with less data or when deleting rows. When all free blocks are used up, all future inserts will be concurrent again. @item 大ファイル (63 bit) のサポート。 ただし、filesystems/operating systems が大ファイルをサポートしている場合。 @item 全データは、下位バイトが先にかかれます。 これは、データを、マシン・OS 非依存にしました。 The only requirement is that the machine uses two's-complement signed integers (as every machine for the last 20 years has) and IEEE floating-point format (also totally dominant among mainstream machines). The only area of machines that may not support binary compatibility are embedded systems (because they sometimes have peculiar processors). There is no big speed penalty in storing data low byte first; the bytes in a table row is normally unaligned and it doesn't take that much more power to read an unaligned byte in order than in reverse order. The actual fetch-column-value code is also not time critical compared to other code. @item 全数値キーは高位バイトが先に書かれます。 これはインデックスの圧縮率を 良くします。 @item Internal handling of one @code{AUTO_INCREMENT} column. @code{MyISAM} will automatically update this on @code{INSERT/UPDATE}. The @code{AUTO_INCREMENT} value can be reset with @code{myisamchk}. This will make @code{AUTO_INCREMENT} columns faster (at least 10%) and old numbers will not be reused as with the old @code{ISAM}. Note that when an @code{AUTO_INCREMENT} is defined on the end of a multi-part-key the old behaviour is still present. @item When inserted in sorted order (as when you are using an @code{AUTO_INCREMENT} column) the key tree will be split so that the high node only contains one key. This will improve the space utilisation in the key tree. @item @code{BLOB} と @code{TEXT} フィールドにインデックスが張れます @item @code{NULL} 値をインデックスの張られたフィールドに許します． This takes 0-1 bytes/key. @item 現在、キーの最大長はデフォルトで 500 バイトです。 (再コンパイルで 変更可能). In cases of keys longer than 250 bytes, a bigger key block size than the default of 1024 bytes is used for this key. @item 1テーブルあたりの最大のキーの数は 32個 がデフォルトです. これは @code{myisamchk} を再コンパイル無しに、64個まで増やすことが出来ます. @item @code{myisamchk} を @code{--update-state} オプションで実行すると、 @code{myisamchk} はテーブルにチェックをおこなったマークをつけます。 @code{myisamchk --fast} は、このマークが無いテーブルだけをチェックします。 @item @code{myisamchk -a} stores statistics for key parts (and not only for whole keys as in @code{ISAM}). @item Dynamic size rows will now be much less fragmented when mixing deletes with updates and inserts. This is done by automatically combining adjacent deleted blocks and by extending blocks if the next block is deleted. @item @code{myisampack} は @code{BLOB} と @code{VARCHAR} フィールドをパックすることが 可能です。 @item You can use put the datafile and index file on different directories to get more speed (with the @code{DATA/INDEX DIRECTORY="path"} option to @code{CREATE TABLE}). @xref{CREATE TABLE}. @end itemize @code{MyISAM} also supports the following things, which MySQL will be able to use in the near future: @itemize @bullet @item 真の @code{VARCHAR} 型のサポート; a @code{VARCHAR} column starts with a length stored in 2 bytes. @item Tables with @code{VARCHAR} may have fixed or dynamic record length. @item @code{VARCHAR} and @code{CHAR} may be up to 64K. All key segments have their own language definition. This will enable MySQL to have different language definitions per column. @item A hashed computed index can be used for @code{UNIQUE}. This will allow you to have @code{UNIQUE} on any combination of columns in a table. (You can't search on a @code{UNIQUE} computed index, however.) @end itemize Note that index files are usually much smaller with @code{MyISAM} than with @code{ISAM}. This means that @code{MyISAM} will normally use less system resources than @code{ISAM}, but will need more CPU time when inserting data into a compressed index. @code{mysqld} に与える以下のオプションは、 @code{MyISAM} テーブルの振る舞いを変更できます. @xref{SHOW VARIABLES}. @multitable @columnfractions .40 .60 @item @strong{Option} @tab @strong{Description} @item @code{--myisam-recover=#} @tab 壊れたテーブルを自動でリカバリ. @item @code{-O myisam_sort_buffer_size=#} @tab リカバリに使用されるバッファ @item @code{--delay-key-write=ALL} @tab Don't flush key buffers between writes for any MyISAM table @item @code{-O myisam_max_extra_sort_file_size=#} @tab Used to help MySQL to decide when to use the slow but safe key cache index create method. @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. @item @code{-O myisam_max_sort_file_size=#} @tab Don't use the fast sort index method to created index if the temporary file would get bigger than this. @strong{Note} that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version. @item @code{-O bulk_insert_buffer_size=#} @tab Size of tree cache used in bulk insert optimisation. @strong{Note} that this is a limit @strong{per thread}! @end multitable automatic recovery は @code{mysqld} を @code{--myisam-recover=#} オプション (3.23.26以上) で起動したときに有効になります. @xref{Command-line options}. On open, the table is checked if it's marked as crashed or if the open count variable for the table is not 0 and you are running with @code{--skip-external-locking}.(4.0.3以前では @code{--skip-locking}) 上のどれかに当てはまる場合、以下を行ないます。 @itemize @bullet @item テーブルはエラーのためにチェックされます. @item もしエラーが見つかったなら、そのテーブルの fast repair (sort はするけれども データファイルの再構築は行なわない) を行ないます. @item もし修復がデータファイルのエラーのために失敗したら (例えば duplicate key error)、 再びリペアを試みますが、この時は、データファイルを再構築します. @item もしリペアが失敗したら、さらにもう一度、古い修復方法(ソート無しに、 レコード単位に書く)で、修復を試みます。 この方法は、いかなるタイプのエラーでも、少ないディスクで修復可能です。 @end itemize If the recover wouldn't be able to recover all rows from a previous completed statement and you didn't specify @code{FORCE} as an option to @code{myisam-recover}, then the automatic repair will abort with an error message in the error file: @example Error: Couldn't repair table: test.g00pages @end example この @code{FORCE} を使用した場合には、エラーメッセージは以下のようになります： @example Warning: Found 344 of 354 rows when repairing ./test/g00pages @end example もしあなたが自動修復を @code{BACKUP} で実行しているなら、 あなたは、データベースのディレクトリから @file{tablename-datetime.BAK} のようなファイルを自動的にバックアップ メディアに移動する @code{cron} スクリプトを作るべきです。 @xref{Command-line options}. @menu * Key space:: Space needed for keys * MyISAM table formats:: @code{MyISAM} Table Formats * MyISAM table problems:: @code{MyISAM} Table Problems @end menu @node Key space, MyISAM table formats, MyISAM, MyISAM @subsection Space Needed for Keys @cindex key space, MyISAM MySQL can support different index types, but the normal type is ISAM or MyISAM. これらは B-tree index を使用します。インデックスファイルのサイズは、 @code{(key_length+4)/0.67} でおおざっぱに計算できます。 (This is for the worst case when all keys are inserted in sorted order and we don't have any compressed keys.) 文字インデックスは圧縮されます。 If the first index part is a string, it will also be prefix compressed. Space compression makes the index file smaller than the above figures if the string column has a lot of trailing space or is a @code{VARCHAR} column that is not always used to the full length. Prefix compression is used on keys that start with a string. Prefix compression helps if there are many strings with an identical prefix. In @code{MyISAM} tables, you can also prefix compress numbers by specifying @code{PACK_KEYS=1} when you create the table. This helps when you have many integer keys that have an identical prefix when the numbers are stored high-byte first. @node MyISAM table formats, MyISAM table problems, Key space, MyISAM @subsection @code{MyISAM} Table Formats @code{MyISAM} supports 3 different table types. Two of them are chosen automatically depending on the type of columns you are using. The third, compressed tables, can only be created with the @code{myisampack} tool. When you @code{CREATE} or @code{ALTER} a table you can for tables that doesn't have @code{BLOB}s force the table format to @code{DYNAMIC} or @code{FIXED} with the @code{ROW_FORMAT=#} table option. In the future you will be able to compress/decompress tables by specifying @code{ROW_FORMAT=compressed | default} to @code{ALTER TABLE}. @xref{CREATE TABLE}. @menu * Static format:: Static (Fixed-length) Table Characteristics * Dynamic format:: Dynamic Table Characteristics * Compressed format:: Compressed Table Characteristics @end menu @node Static format, Dynamic format, MyISAM table formats, MyISAM table formats @subsubsection Static (Fixed-length) Table Characteristics This is the default format. It's used when the table contains no @code{VARCHAR}, @code{BLOB}, or @code{TEXT} columns. このフォーマットは、最も単純、かつ、安全なフォーマットです。 これは, Disk 上に作られるテーブルの中で、最も速いフォーマットでもあります。 これはディスク上のデータを見つけやすいからです。 When looking up something with an index and static format it is very simple. Just multiply the row number by the row length. Also, when scanning a table it is very easy to read a constant number of records with each disk read. The security is evidenced if your computer crashes when writing to a fixed-size MyISAM file, in which case @code{myisamchk} can easily figure out where each row starts and ends. So it can usually reclaim all records except the partially written one. Note that in MySQL all indexes can always be reconstructed: @itemize @bullet @item 全ての @code{CHAR}, @code{NUMERIC}, @code{DECIMAL} フィールドは、そのフィールド 長に足りない部分にはスペースが埋められます。 @item とても速い @item キャッシュしやすい。 @item クラッシュの後再構築しやすい。なぜならレコードが固定された位置に割り当てられてい るから。 @item Doesn't have to be reorganised (with @code{myisamchk}) unless a huge number of records are deleted and you want to return free disk space to the operating system. @item 通常、動的テーブルよりも多くのディスク容量が必要。 @end itemize @node Dynamic format, Compressed format, Static format, MyISAM table formats @subsubsection Dynamic Table Characteristics @cindex dynamic table characteristics @cindex tables, dynamic This format is used if the table contains any @code{VARCHAR}, @code{BLOB}, or @code{TEXT} columns or if the table was created with @code{ROW_FORMAT=dynamic}. この形式は少し複雑です。 なぜならそれぞれのレコードが、レコードがどのぐらいの 長さを持っているかを記録するヘッダーを持っているからです。 One record can also end up at more than one location when it is made longer at an update. @cindex tables, defragment @code{OPTIMIZE table} か @code{myisamchk} を使用して、テーブルの フラグメンテーションを修正することが可能です。 If you have static data that you access/change a lot in the same table as some @code{VARCHAR} or @code{BLOB} columns, it might be a good idea to move the dynamic columns to other tables just to avoid fragmentation: @itemize @bullet @item 全ての文字フィールドが動的になります（ただし4byteより短い物は除きます） @item それぞれのレコードの先頭には、フィールドの状態を表すビット・マップがきます。 このビットは、どの文字型フィールドが空文字(@code{''})なのか、 どの数値フィールドがゼロなのかを示します。 (これはフィールドの値が @code{NULL} 値とは違います)。 もし、文字型フィールドの文字列の長さ(後に続く空白は取り除かれる)が ゼロ で あったり、あるいは、数値フィールドの値が ゼロ であった場合は、 そのフィールドはビット・マップにマークされ、値はディスクには保存されません。 空文字ではない場合は、文字列のバイト数がビット・マップに記録され、 文字列自身がフィールドに保存されます。 @item 通常、固定長のテーブルよりも少ないディスク容量ですみます @item それぞれのレコードは、要求されただけのスペースを使用します。 もしあるレコードが大きくなると、要求された分、それを多くの断片に分けます。 この結果、レコードのフラグメンテーションが発生します。 @item If you update a row with information that extends the row length, the row will be fragmented. In this case, you may have to run @code{myisamchk -r} from time to time to get better performance. Use @code{myisamchk -ei tbl_name} for some statistics. @item Not as easy to reconstruct after a crash, because a record may be fragmented into many pieces and a link (fragment) may be missing. @item 期待されるレコードの長さは： @example 3 + (フィールド数 + 7) / 8 + (char フィールドの数) + 数値フィールドをパックしたサイズ + 文字の長さ + (NULL フィールドの数 + 7) / 8 @end example There is a penalty of 6 bytes for each link. A dynamic record is linked whenever an update causes an enlargement of the record. Each new link will be at least 20 bytes, so the next enlargement will probably go in the same link. If not, there will be another link. You may check how many links there are with @code{myisamchk -ed}. All links may be removed with @code{myisamchk -r}. @end itemize @node Compressed format, , Dynamic format, MyISAM table formats @subsubsection 圧縮テーブルの特徴 @cindex tables, compressed format @cindex compressed tables @cindex MyISAM, compressed tables @cindex @code{myisampack} これは、@code{myisampack} ツール (@code{pack_isam} は @code{ISAM} テーブル用)に @itemize @bullet @item 全ての MySQL ディストリビューション ( MySQL が GPL になる以前の物も含) は、 @code{myisampack} で圧縮されたテーブルを読むことが可能です。 @item 圧縮テーブルはディスクスペースを節約します。 これは disk usage を少なくするので、遅いディスク(CD-ROM など)にはとても好都合です。 @item それぞれのレコード別に圧縮されます(アクセスのオーバーヘッドがとても少ない)。 レコードのヘッダは固定で(1-3 Bytes)、テーブル中の最大の大きさのレコードに依存します。 Each column is compressed differently. Some of the compression types are: @itemize @minus @item There is usually a different Huffman table for each column. @item Suffix space compression. @item Prefix space compression. @item Numbers with value @code{0} are stored using 1 bit. @item もし整数型のフィールドが小さな値に収まっているならば、 そのフィードは、できる限り小さなフィールド型に保存されます。 例えば、@code{BIGINT} フィールド(8bytes)の値全てが @code{0} から @code{255} に 収まっていれば、@code{TINYINT} フィールド (1 byte) に保存されます。 @item If a column has only a small set of possible values, the column type is converted to @code{ENUM}. @item A column may use a combination of the above compressions. @end itemize @item 固定長、可変長のレコードを扱うことができます @item @code{myisamchk} で、伸長できます。 @end itemize @node MyISAM table problems, , MyISAM table formats, MyISAM @subsection @code{MyISAM} table problems. The file format that MySQL uses to store data has been extensively tested, but there are always circumstances that may cause database tables to become corrupted. @menu * Corrupted MyISAM tables:: Corrupted @code{MyISAM} Tables * MyISAM table close:: Clients is using or hasn't closed the table properly @end menu @node Corrupted MyISAM tables, MyISAM table close, MyISAM table problems, MyISAM table problems @subsubsection 壊れた @code{MyISAM} テーブル いくら MyISAM テーブルがとても信頼できるとは言え(SQL文を返す前に テーブルへの変更を全て書き出す)、 以下のような事が起きた場合には、テーブルが壊れるかもしれません： @itemize @bullet @item @code{mysqld} プロセスが書き込み途中で kill された @item コンピュータの不意のシャットダウン(例えば電源断) @item ハードウェアのエラー @item 稼働中のテーブルに対して外部プログラム(myisamchkのような)を使用 @item MySQL か MyISAM コードのソフトウェアのバグ @end itemize 壊れたテーブルの、典型的な症状は： @itemize @bullet @item そのテーブルからデータを選択中に @code{Incorrect key file for table: '...'. Try to repair it} エラーが出る @item クエリがテーブル内のレコードを見つけれなかったり、 不完全なデータを返したり。 @end itemize @code{CHECK TABLE} 命令を使用して、テーブルが OK か否かを 確かめることができます。 @xref{CHECK TABLE}. @code{REPAIR TABLE} で不正なテーブルを修復することが可能です. @xref{REPAIR TABLE}. @code{mysqld} が動作していないときに、 @code{myisamchk} コマンドを使用して テーブルを修復することも可能です。 @code{myisamchk syntax}. もし多くの不整合がテーブルに起きたならば、 その理由を探すべきです！ @xref{Crashing}. In this case the most important thing to know is if the table got corrupted if the @code{mysqld} died (one can easily verify this by checking if there is a recent row @code{restarted mysqld} in the mysqld error file). If this isn't the case, then you should try to make a test case of this. @xref{Reproduceable test case}. @node MyISAM table close, , Corrupted MyISAM tables, MyISAM table problems @subsubsection Clients is using or hasn't closed the table properly Each @code{MyISAM} @file{.MYI} file has in the header a counter that can be used to check if a table has been closed properly. If you get the following warning from @code{CHECK TABLE} or @code{myisamchk}: @example # clients is using or hasn't closed the table properly @end example this means that this counter has come out of sync. This doesn't mean that the table is corrupted, but means that you should at least do a check on the table to verify that it's okay. The counter works as follows: @itemize @bullet @item The first time a table is updated in MySQL, a counter in the header of the index files is incremented. @item The counter is not changed during further updates. @item When the last instance of a table is closed (because of a @code{FLUSH} or because there isn't room in the table cache) the counter is decremented if the table has been updated at any point. @item When you repair the table or check the table and it was okay, the counter is reset to 0. @item To avoid problems with interaction with other processes that may do a check on the table, the counter is not decremented on close if it was 0. @end itemize In other words, the only ways this can go out of sync are: @itemize @bullet @item The @code{MyISAM} tables are copied without a @code{LOCK} and @code{FLUSH TABLES}. @item MySQL has crashed between an update and the final close. (Note that the table may still be okay, as MySQL always issues writes for everything between each statement.) @item Someone has done a @code{myisamchk --recover} or @code{myisamchk --update-state}on a table that was in use by @code{mysqld}. @item Many @code{mysqld} servers are using the table and one has done a @code{REPAIR} or @code{CHECK} of the table while it was in use by another server. In this setup the @code{CHECK} is safe to do (even if you will get the warning from other servers), but @code{REPAIR} should be avoided as it currently replaces the datafile with a new one, which is not signaled to the other servers. @end itemize @node MERGE, ISAM, MyISAM, Table types @section @code{MERGE} Tables (3.23.25以上) @cindex tables, merging @cindex MERGE tables, defined @code{MERGE} tables are new in MySQL Version 3.23.25. The code is still in gamma, but should be resonable stable. @code{MERGE} テーブルは(@code{MRG_MyISAM} テーブルとしても知られています) 同一の @code{MyISAM} をひとまとめにして使用することができるテーブルです。 そのテーブルの集合体に対しては、@code{SELECT}, @code{DELETE}, @code{UPDATE} のみが可能です。 もし @code{MERGE} テーブルを @code{DROP} すると、@code{MERGE} の 定義だけが破棄されます。 Note that @code{DELETE FROM merge_table} used without a @code{WHERE} will only clear the mapping for the table, not delete everything in the mapped tables. (We plan to fix this in 4.1). 'identical tables' とは、全てのテーブルが同一のフィールド構造とキーの 情報を有するという意味で使用しています。 You can't merge tables in which the columns are packed differently, doesn't have exactly the same columns, or have the keys in different order. However, some of the tables can be compressed with @code{myisampack}. @xref{myisampack, , @code{myisampack}}. @code{MERGE} テーブルを作成すると、@code{.frm} テーブル定義ファイルと @code{.MRG} テーブルリストファイルが作成されます。 @code{.MRG} はインデックスファイル (@code{.MYI} ファイル) の リスト(これらは一つとして扱われる)だけが含まれます。 全ての使用されるテーブルは、同じデータベース内に 存在しなければなりません(@code{MERGE}テーブルも同様)。 For the moment, you need to have @code{SELECT}, @code{UPDATE}, and @code{DELETE} privileges on the tables you map to a @code{MERGE} table. @code{MERGE} テーブルは以下の問題の解決を助けます: @itemize @bullet @item ログテーブルの管理を安易にします。 For example, you can put data from different months into separate files, compress some of them with @code{myisampack}, and then create a @code{MERGE} to use these as one. @item より速く。 You can split a big read-only table based on some criteria and then put the different table part on different disks. A @code{MERGE} table on this could be much faster than using the big table. (You can, of course, also use a RAID to get the same kind of benefits.) @item Do more efficient searches. If you know exactly what you are looking after, you can search in just one of the split tables for some queries and use a @code{MERGE} table for others. You can even have many different @code{MERGE} tables active, with possible overlapping files. @item More efficient repairs. It's easier to repair the individual files that are mapped to a @code{MERGE} file than trying to repair a really big file. @item Instant mapping of many files as one. A @code{MERGE} table uses the index of the individual tables. It doesn't need to maintain an index of its one. This makes @code{MERGE} table collections VERY fast to make or remap. Note that you must specify the key definitions when you create a @code{MERGE} table!. @item If you have a set of tables that you join to a big table on demand or batch, you should instead create a @code{MERGE} table on them on demand. This is much faster and will save a lot of disk space. @item Go around the file-size limit for the operating system. @item You can create an alias/synonym for a table by just using @code{MERGE} over one table. There shouldn't be any really notable performance impacts of doing this (only a couple of indirect calls and @code{memcpy()} calls for each read). @end itemize @code{MERGE} の欠点は： @itemize @bullet @item @code{MERGE} には、同一構造の @code{MyISAM} テーブルしか使用できません。 @item ver.4.0.3未満では @code{AUTO_INCREMENT} フィールドは、@code{INSERT} 時に、自動で更新されません。 @item @code{REPLACE} は動作しません。 @item @code{MERGE} テーブルはより多くのファイル・デスクリプタを使用します。 If you are using a @code{MERGE} table that maps over 10 tables and 10 users are using this, you are using 10*10 + 10 file descriptors. (10 datafiles for 10 users and 10 shared index files.) @item キーの読み込みが遅い。 When you do a read on a key, the @code{MERGE} storage engine will need to issue a read on all underlying tables to check which one most closely matches the given key. If you then do a "read-next" then the @code{MERGE} storage engine will need to search the read buffers to find the next key. Only when one key buffer is used up, the storage engine will need to read the next key block. This makes @code{MERGE} keys much slower on @code{eq_ref} searches, but not much slower on @code{ref} searches. @xref{EXPLAIN}. @item You can't do @code{DROP TABLE}, @code{ALTER TABLE}, @code{DELETE FROM table_name} without a @code{WHERE} clause, @code{REPAIR TABLE}, @code{TRUNCATE TABLE}, @code{OPTIMIZE TABLE}, or @code{ANALYZE TABLE} on any of the table that is mapped by a @code{MERGE} table that is "open". If you do this, the @code{MERGE} table may still refer to the original table and you will get unexpected results. The easiest way to get around this deficiency is to issue the @code{FLUSH TABLES} command, ensuring no @code{MERGE} tables remain "open". @end itemize @code{MERGE} テーブルを作るときは、@code{UNION(list-of-tables)} に、 どのテーブルを一つのようにして扱うかを指定する必要があります。 Optionally you can specify with @code{INSERT_METHOD} if you want insert for the @code{MERGE} table to happen in the first or last table in the @code{UNION} list. もし @code{INSERT_METHOD} や @code{NO} を指定しなかったなら、 @code{MERGE} テーブルに対する全ての @code{INSERT} コマンドはエラーになります。 The following example shows you how to use @code{MERGE} tables: @example CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20)); CREATE TABLE t2 (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20)); INSERT INTO t1 (message) VALUES ("Testing"),("table"),("t1"); INSERT INTO t2 (message) VALUES ("Testing"),("table"),("t2"); CREATE TABLE total (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20)) TYPE=MERGE UNION=(t1,t2) INSERT_METHOD=LAST; @end example @c Note that we didn't create a @code{UNIQUE} or @code{PRIMARY KEY} in the @c @code{total} table as the key isn't going to be unique in the @code{total} @c table. 直接、手動で @file{.MRG} ファイルを作ることも可能です： @example shell> cd /mysql-data-directory/current-database shell> ls -1 t1.MYI t2.MYI > total.MRG shell> mysqladmin flush-tables @end example Now you can do things like: @example mysql> SELECT * FROM total; +---+---------+ | a | message | +---+---------+ | 1 | Testing | | 2 | table | | 3 | t1 | | 1 | Testing | | 2 | table | | 3 | t2 | +---+---------+ @end example Note that the @code{a} column, though declared as @code{PRIMARY KEY}, is not really unique, as @code{MERGE} table cannot enforce uniqueness over a set of underlying @code{MyISAM} tables. To remap a @code{MERGE} table you can do one of the following: @itemize @bullet @item @code{DROP} the table and re-create it @item Use @code{ALTER TABLE table_name UNION(...)} @item Change the @file{.MRG} file and issue a @code{FLUSH TABLE} on the @code{MERGE} table and all underlying tables to force the storage engine to read the new definition file. @end itemize @menu * MERGE table problems:: MERGE Table Problems @end menu @node MERGE table problems, , MERGE, MERGE @subsection @code{MERGE} Table Problems The following are the known problems with @code{MERGE} tables: @itemize @bullet @item A @code{MERGE} table cannot maintain @code{UNIQUE} constraints over the whole table. When you do @code{INSERT}, the data goes into the first or last table (according to @code{INSERT_METHOD=xxx}) and this @code{MyISAM} table ensures that the data are unique, but it knows nothing about others @code{MyISAM} tables. @item @code{DELETE FROM merge_table} used without a @code{WHERE} will only clear the mapping for the table, not delete everything in the mapped tables. @item @code{RENAME TABLE} on a table used in an active @code{MERGE} table may corrupt the table. This will be fixed in MySQL 4.0.x. @item Creation of a table of type @code{MERGE} doesn't check if the underlying tables are of compatible types. If you use @code{MERGE} tables in this fashion, you are very likely to run into strange problems. @item If you use @code{ALTER TABLE} to first add an @code{UNIQUE} index to a table used in a @code{MERGE} table and then use @code{ALTER TABLE} to add a normal index on the @code{MERGE} table, the key order will be different for the tables if there was an old non-unique key in the table. This is because @code{ALTER TABLE} puts @code{UNIQUE} keys before normal keys to be able to detect duplicate keys as early as possible. @item The range optimiser can't yet use @code{MERGE} table efficiently and may sometimes produce non-optimal joins. This will be fixed in MySQL 4.0.x. @item @code{DROP TABLE} on a table that is in use by a @code{MERGE} table will not work on Windows because the @code{MERGE} storage engine does the table mapping hidden from the upper layer of MySQL. Because Windows doesn't allow you to drop files that are open, you first must flush all @code{MERGE} tables (with @code{FLUSH TABLES}) or drop the @code{MERGE} table before dropping the table. We will fix this at the same time we introduce @code{VIEW}s. @end itemize @node ISAM, HEAP, MERGE, Table types @section @code{ISAM} Tables @cindex tables, ISAM You can also use the deprecated @code{ISAM} table type. This will disappear rather soon (probably in MySQL 5.0) because @code{MyISAM} is a better implementation of the same thing. @code{ISAM} uses a @code{B-tree} index. The index is stored in a file with the @file{.ISM} extension, and the data is stored in a file with the @file{.ISD} extension. You can check/repair @code{ISAM} tables with the @code{isamchk} utility. @xref{Crash recovery}. @code{ISAM} has the following features/properties: @itemize @bullet @item Compressed and fixed-length keys @item Fixed and dynamic record length @item 16 keys with 16 key parts/key @item Max key length 256 (default) @item Data is stored in machine format; this is fast, but is machine/OS dependent. @end itemize Most of the things true for @code{MyISAM} tables are also true for @code{ISAM} tables. @xref{MyISAM, , @code{MyISAM} tables}. The major differences compared to @code{MyISAM} tables are: @itemize @bullet @item @code{ISAM} tables are not binary portable across OS/Platforms. @item Can't handle tables > 4G. @item Only support prefix compression on strings. @item Smaller key limits. @item Dynamic tables get more fragmented. @item Tables are compressed with @code{pack_isam} rather than with @code{myisampack}. @end itemize If you want to convert an @code{ISAM} table to a @code{MyISAM} table so that you can use utilities such as @code{mysqlcheck}, use an @code{ALTER TABLE} statement: @example mysql> ALTER TABLE tbl_name TYPE = MYISAM; @end example The embedded MySQL versions doesn't support @code{ISAM} tables. @node HEAP, InnoDB, ISAM, Table types @section @code{HEAP} Tables (3.23.0以上) @cindex tables, @code{HEAP} @code{HEAP} テーブルは hashed index を使用し、メモリ内に保存されます。 これはとても速くなりますが、もし MySQL がクラッシュする時にはその内容が 全て失われます。 @code{HEAP} はテンポラリのテーブルとしてはとても便利です！ MySQL 内部 HEAP テーブルは、100% ダイナッミック・ハッシングを 使用しています（オーバーフローエリア無しに）。 There is no extra space needed for free lists. @code{HEAP} tables also don't have problems with delete + inserts, which normally is common with hashed tables: @example mysql> CREATE TABLE test TYPE=HEAP SELECT ip,SUM(downloads) AS down -> FROM log_table GROUP BY ip; mysql> SELECT COUNT(ip),AVG(down) FROM test; mysql> DROP TABLE test; @end example Here are some things you should consider when you use @code{HEAP} tables: @itemize @bullet @item You should always use specify @code{MAX_ROWS} in the @code{CREATE} statement to ensure that you accidentally do not use all memory. @item Indexes will only be used with @code{=} and @code{<=>} (but are VERY fast). @item @code{HEAP} tables can only use whole keys to search for a row; compare this to @code{MyISAM} tables where any prefix of the key can be used to find rows. @item @code{HEAP} テーブルは 固定長のレコードです。 @item @code{HEAP} は @code{BLOB}/@code{TEXT} 型をサポートしません。 @item @code{HEAP} は @code{AUTO_INCREMENT} フィールドをサポートしません。 @item MySQL 4.0.2 以前では、@code{HEAP} は @code{NULL} が許されているフィールドにインデックスを張れません。 @item @code{HEAP} テーブルに、一意ではないキーを持たせることが可能です。 (this isn't common for hashed tables). @item @code{HEAP} テーブルは全てのクライアントに共有されます (他のテーブルと同じように) @item You can't search for the next entry in order (that is, to use the index to do an @code{ORDER BY}). @item Data for @code{HEAP} tables are allocated in small blocks. The tables are 100% dynamic (on inserting). No overflow areas and no extra key space are needed. Deleted rows are put in a linked list and are reused when you insert new data into the table. @item You need enough extra memory for all @code{HEAP} tables that you want to use at the same time. @item メモリを解放するには, @code{DELETE FROM heap_table}, @code{TRUNCATE heap_table} , @code{DROP TABLE heap_table} を実行すべきです. @item MySQL cannot find out approximately how many rows there are between two values (this is used by the range optimiser to decide which index to use). This may affect some queries if you change a @code{MyISAM} table to a @code{HEAP} table. @item To ensure that you accidentally don't do anything foolish, you can't create @code{HEAP} tables bigger than @code{max_heap_table_size}. @end itemize @code{HEAP} テーブル内の１レコードに必要とされるメモリは： @example SUM_OVER_ALL_KEYS(max_length_of_key + sizeof(char*) * 2) + ALIGN(length_of_row+1, sizeof(char*)) @end example @code{sizeof(char*)} is 4 on 32-bit machines and 8 on 64-bit machines. @node InnoDB, BDB, HEAP, Table types @section @code{InnoDB} テーブル (3.23.6以上) @menu * InnoDB overview:: InnoDB Tables Overview * InnoDB start:: InnoDB Startup Options * InnoDB init:: Creating InnoDB Tablespace * Using InnoDB tables:: Creating InnoDB Tables * Adding and removing:: Adding and Removing InnoDB Data and Log Files * Backing up:: Backing up and Recovering an InnoDB Database * Moving:: Moving an InnoDB Database to Another Machine * InnoDB transaction model:: InnoDB Transaction Model. * Implementation:: Implementation of Multi-versioning * Table and index:: Table and Index Structures * File space management:: File Space Management and Disk I/O * Error handling:: Error Handling * InnoDB restrictions:: Restrictions on InnoDB Tables * InnoDB change history:: InnoDB Change History * InnoDB contact information:: InnoDB Contact Information. @end menu @node InnoDB overview, InnoDB start, InnoDB, InnoDB @subsection InnoDB テーブル 概要 @cindex transactions, support @cindex transaction-safe tables @cindex ACID InnoDB provides MySQL with a transaction-safe (@code{ACID} compliant) storage engine with commit, rollback, and crash recovery capabilities. InnoDB does locking on row level and also provides an Oracle-style consistent non-locking read in @code{SELECT}s. These features increase multiuser concurrency and performance. There is no need for lock escalation in InnoDB, because row level locks in InnoDB fit in very small space. InnoDB テーブルは MySQL のテーブルタイプの中では初めて、 @code{FOREIGN KEY} 制約 をサポートします。 InnoDB has been designed for maximum performance when processing large data volumes. Its CPU efficiency is probably not matched by any other disk-based relational database engine. Technically, InnoDB is a complete database backend placed under MySQL. InnoDB has its own buffer pool for caching data and indexes in main memory. InnoDB stores its tables and indexes in a tablespace, which may consist of several files. This is different from, for example, MyISAM tables where each table is stored as a separate file. InnoDB tables can be of any size also on those operating systems where file-size is limited to 2 GB. 最新の InnoDB についての情報は @uref{http://www.innodb.com/}. The most up-to-date version of the InnoDB manual is always placed there, and you can also order commercial licenses and support for InnoDB. InnoDB is currently (October 2001) used in production at several large database sites requiring high performance. The famous Internet news site Slashdot.org runs on InnoDB. Mytrix, Inc. stores over 1 TB of data in InnoDB, and another site handles an average load of 800 inserts/updates per second in InnoDB. InnoDB は バージョン 3.23.34a から、 MySQL のソース配布に含まれるようになり、 そして、@strong{MySQL-max} バイナリで有効になりました。 For Windows the -Max binaries are contained in the standard distribution. If you have downloaded a binary version of MySQL that includes support for InnoDB, simply follow the instructions of the MySQL manual for installing a binary version of MySQL. If you already have MySQL-3.23 installed, then the simplest way to install MySQL -Max is to replace the server executable @file{mysqld} with the corresponding executable in the -Max distribution. MySQL and MySQL -Max differ only in the server executable. @xref{Installing binary}. InnoDB をサポートするように MySQL をコンパイルするには、MySQL-3.23.34a 以上をダウンロードし、 @code{--with-innodb} オプションで MySQL を configure します。 @xref{Installing source}. @example cd /path/to/source/of/mysql-3.23.37 ./configure --with-innodb @end example InnoDB を使用するためには、@file{my.cnf} か @file{my.ini} ファイルに InnoDB 起動オプションを指定しなくてはなりません。 必要最低限の変更は、 @code{[mysqld]} セクションに以下のラインを加えることです @example innodb_data_file_path=ibdata:30M @end example but to get good performance it is best that you specify options as recommended. @xref{InnoDB start}. InnoDB is distributed under the GNU GPL License Version 2 (of June 1991). In the source distribution of MySQL, InnoDB appears as a subdirectory. @node InnoDB start, InnoDB init, InnoDB overview, InnoDB @subsection InnoDB 起動オプション MySQL-3.23.37 から、オプションの接頭語が @code{innobase_...} から @code{innodb_...} に変わりました！ MySQL-Max-3.23 で InnoDB テーブルを使用するためには、 設定ファイル @file{my.cnf} (Windows では @file{my.ini}) の @code{[mysqld]} セクションに設定をしなくては@strong{なりません}。 @xref{Option files}. + At the minimum, in 3.23 you must specify @code{innodb_data_file_path} + where you specify the names and the sizes of datafiles. If you do + not mention @code{innodb_data_home_dir} in @file{my.cnf} the default + is to create these files to the @code{datadir} of MySQL. + If you specify @code{innodb_data_home_dir} as an empty string, + then you can give absolute paths to your data files in + @code{innodb_data_file_path}. In MySQL-4.0 you do not need to specify even @code{innodb_data_file_path}: the default for it is to create + an auto-extending 10 MB file @file{ibdata1} to the @code{datadir} of MySQL. (In MySQL-4.0.0 and 4.0.1 the datafile is 64 MB and not auto-extending.) + If you don't want to use @code{InnoDB} tables, you can add the + @code{skip-innodb} option to your MySQL option file. + ver.3.23 では、InnoDB を使用するために唯一必要なパラメタは データファイルの大きさを指定する @code{innodb_data_file_path} です。 If you do not mention @code{innodb_data_home_dir} in @file{my.cnf} the default is to create these files to the @code{datadir} of MySQL. If you specify @code{innodb_data_home_dir} as an empty string, then you can give absolute paths to your data files in @code{innodb_data_file_path}. In MySQL-4.0 you do not need to specify even @code{innodb_data_file_path}: the default for it is to create an auto-extending 10 MB file @file{ibdata1} to the @code{datadir} of MySQL. (In MySQL-4.0.0 and 4.0.1 the datafile is 64 MB and not auto-extending.) If you don't want to use @code{InnoDB} tables, you can add the @code{skip-innodb} option to your MySQL option file. 他のオプションはよりよいパフォーマンスを得たい場合に設定します。 Starting from versions 3.23.50 and 4.0.2 InnoDB allows the last datafile on the @code{innodb_data_file_path} line to be specified as @strong{auto-extending}. The syntax for @code{innodb_data_file_path} is then the following: @example pathtodatafile:sizespecification;pathtodatafile:sizespecification;... ... ;pathtodatafile:sizespecification[:autoextend[:max:sizespecification]] @end example If you specify the last datafile with the autoextend option, InnoDB will extend the last datafile if it runs out of free space in the tablespace. The increment is 8 MB at a time. An example: @example innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:100M:autoextend @end example instructs InnoDB to create just a single datafile whose initial size is 100 MB and which is extended in 8 MB blocks when space runs out. If the disk becomes full you may want to add another data file to another disk, for example. Then you have to look the size of @file{ibdata1}, round the size downward to the closest multiple of 1024 * 1024 bytes (= 1 MB), and specify the rounded size of @file{ibdata1} explicitly in @code{innodb_data_file_path}. After that you can add another datafile: @example innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:988M;/disk2/ibdata2:50M:autoextend @end example Be cautious on filesystems where the maximum file-size is 2 GB! InnoDB is not aware of the OS maximum file-size. On those filesystems you might want to specify the max size for the datafile: @example innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:100M:autoextend:max:2000M @end example @strong{A simple @file{my.cnf} example.} Suppose you have a computer with 128 MB RAM and one hard disk. Below is an example of possible configuration parameters in @file{my.cnf} or @file{my.ini} for InnoDB. We assume you are running MySQL-Max-3.23.50 or later, or MySQL-4.0.2 or later. This example suits most users, both on Unix and Windows, who do not want to distribute InnoDB datafiles and log files on several disks. This creates an auto-extending data file @file{ibdata1} and two InnoDB log files @file{ib_logfile0} and @file{ib_logfile1} to the @code{datadir} of MySQL (typically @file{/mysql/data}). Also the small archived InnoDB log file @file{ib_arch_log_0000000000} ends up in the @code{datadir}. @example [mysqld] # You can write your other MySQL server options here # ... # Data file(s) must be able to # hold your data and indexes. # Make sure you have enough # free disk space. innodb_data_file_path = ibdata1:10M:autoextend # Set buffer pool size to # 50 - 80 % of your computer's # memory set-variable = innodb_buffer_pool_size=70M set-variable = innodb_additional_mem_pool_size=10M # Set the log file size to about # 25 % of the buffer pool size set-variable = innodb_log_file_size=20M set-variable = innodb_log_buffer_size=8M # Set ..flush_log_at_trx_commit # to 0 if you can afford losing # some last transactions innodb_flush_log_at_trx_commit=1 @end example @strong{Check that the MySQL server has the rights to create files} in @code{datadir}. Note that datafiles must be < 2G in some file systems! The combined size of the log files must be < 4G. The combined size of datafiles must be >= 10 MB. When you for the first time create an InnoDB database, it is best that you start the MySQL server from the command prompt. Then InnoDB will print the information about the database creation to the screen, and you see what is happening. See below next section what the printout should look like. For example, in Windows you can start @file{mysqld-max.exe} with: @example your-path-to-mysqld>mysqld-max --console @end example @strong{Where to put @file{my.cnf} or @file{my.ini} in Windows?} The rules for Windows are the following: @itemize @bullet @item Only one of @file{my.cnf} or @file{my.ini} should be created. @item The @file{my.cnf} file should be placed in the root directory of the drive @file{C:}. @item The @file{my.ini} file should be placed in the WINDIR directory, e.g, @file{C:\WINDOWS} or @file{C:\WINNT}. You can use the @code{SET} command of MS-DOS to print the value of WINDIR. @item If your PC uses a boot loader where the @file{C:} drive is not the boot drive, then your only option is to use the @file{my.ini} file. @end itemize @strong{Where to specify options in Unix?} On Unix @file{mysqld} reads options from the following files, if they exist, in the following order: @itemize @bullet @item @file{/etc/my.cnf} Global options. @item @file{COMPILATION_DATADIR/my.cnf} Server-specific options. @item @file{defaults-extra-file} The file specified with @code{--defaults-extra-file=...}. @item @file{~/.my.cnf} User-specific options. @end itemize @file{COMPILATION_DATADIR} is the MySQL data directory which was specified as a @code{./configure} option when @file{mysqld} was compiled (typically @file{/usr/local/mysql/data} for a binary installation or @file{/usr/local/var} for a source installation). If you are not sure from where @file{mysqld} reads its @file{my.cnf} or @file{my.ini}, you can give the path as the first command-line option to the server: @code{mysqld --defaults-file=your_path_to_my_cnf}. InnoDB forms the directory path to a datafile by textually catenating @code{innodb_data_home_dir} to a datafile name or path in @code{innodb_data_file_path}, adding a possible slash or backslash in between if needed. If the keyword @code{innodb_data_home_dir} is not mentioned in @file{my.cnf} at all, the default for it is the 'dot' directory @file{./} which means the @code{datadir} of MySQL. @strong{An advanced @file{my.cnf} example.} あなたの機械が Linux で 512M の RAM と 20GB のハードディスクだと仮定します。 (ディレクトリパスは @file{/}, @file{/dr2}, @file{/dr3}) 以下はその場合の @file{my.cnf} の InnoDB パラメターの例です. @strong{Note that InnoDB does not create directories: you have to create them yourself.} Use the Unix or MS-DOS @code{mkdir} command to create the data and log group home directories. @example [mysqld] # You can write your other MySQL server options here # ... innodb_data_home_dir = # Data files must be able to # hold your data and indexes innodb_data_file_path = /ibdata/ibdata1:2000M;/dr2/ibdata/ibdata2:2000M:autoextend # Set buffer pool size to # 50 - 80 % of your computer's # memory, but make sure on Linux # x86 total memory usage is # < 2 GB set-variable = innodb_buffer_pool_size=1G set-variable = innodb_additional_mem_pool_size=20M innodb_log_group_home_dir = /dr3/iblogs # .._log_arch_dir must be the same # as .._log_group_home_dir innodb_log_arch_dir = /dr3/iblogs set-variable = innodb_log_files_in_group=3 # Set the log file size to about # 15 % of the buffer pool size set-variable = innodb_log_file_size=150M set-variable = innodb_log_buffer_size=8M # Set ..flush_log_at_trx_commit to # 0 if you can afford losing # some last transactions innodb_flush_log_at_trx_commit=1 set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 #innodb_flush_method=fdatasync #innodb_fast_shutdown=1 #set-variable = innodb_thread_concurrency=5 @end example Note that we have placed the two datafiles on different disks. InnoDB will fill the tablespace formed by the datafiles from bottom up. In some cases it will improve the performance of the database if all data is not placed on the same physical disk. Putting log files on a different disk from data is very often beneficial for performance. You can also use @strong{raw disk partitions} (raw devices) as datafiles. In some Unixes they speed up I/O. See the manual section on InnoDB file space management about how to specify them in @file{my.cnf}. @strong{Warning}: on Linux x86 you must be careful you @strong{do not set memory usage too high}. glibc will allow the process heap to grow over thread stacks, which will crash your server. It is a risk if the value of @example innodb_buffer_pool_size + key_buffer + max_connections * (sort_buffer + read_buffer_size) + max_connections * 2 MB @end example is close to 2 GB or exceeds 2 GB. Each thread will use a stack (often 2 MB, but in MySQL AB binaries only 256 kB) and in the worst case also @code{sort_buffer + read_buffer_size} additional memory. @strong{How to tune other @file{mysqld} server parameters?} Typical values which suit most users are: @example skip-locking set-variable = max_connections=200 set-variable = read_buffer_size=1M set-variable = sort_buffer=1M # Set key_buffer to 5 - 50% # of your RAM depending on how # much you use MyISAM tables, but # keep key_buffer + InnoDB # buffer pool size < 80% of # your RAM set-variable = key_buffer=... @end example Note that some parameters are given using the numeric @file{my.cnf} parameter format: @code{set-variable = innodb... = 123}, others (string and boolean parameters) with another format: @code{innodb_... = ... }. The meanings of the configuration parameters are the following: @multitable @columnfractions .35 .65 @item @strong{Option} @tab @strong{Description} @item @code{innodb_data_home_dir} @tab 全ての InnoDB データファイルの、共通トップディレクトリのパス。 If you do not mentioned this option in @file{my.cnf} the default is the @code{datadir} of MySQL. You can specify this also as an empty string, in which case you can use absolute file paths in @code{innodb_data_file_path}. @item @code{innodb_data_file_path} @tab 単一のデータファイル(individual data files)のパスとそのサイズ。 (訳注： innodb は保存すべきデータをいくつかのファイルに分割して書き込みます。 この 'individual data files' は、その、実際にデータを保存している 個々のファイルの事を指しています。) それぞれのデータファイルへのフルパスは、@code{innodb_data_home_dir} で指定された パスと連結されることで求められます。 ファイルサイズは メガバイト で与えられ、上記のように 'M' がサイズの後にきます。 ファイルサイズは 4000M より大きくしてはいけません。 ほとんどのオペレーティングシステムでは 2000M より大きなファイルを扱えません。 InnoDB は 'G' の省略形も認識します。 1G は 1024M になります。 バージョン 3.23.44 からは、オペーレーティングシステムが large ファイルを扱えるのであれば、4GB 以上の指定が可能です。 いくつかのオペレーティングシステムは一つのファイルは 2GB 未満の 制約があります。 データファイルのサイズの合計は、少なくとも、10MB 以上必要です。 @item @code{innodb_mirrored_log_groups} @tab データベースのために維持しておくログのグループのコピーの数。 現在、これは 1 しかセットできません。 @item @code{innodb_log_group_home_dir} @tab InnoDB ログファイルのディレクトリのパス。 @item @code{innodb_log_files_in_group} @tab log group 内の、ログファイルの数。 InnoDB はログファイルを、ローテートするやり方で書きます。 3 が推奨値です。 @item @code{innodb_log_file_size} @tab log group 内の、各ログファイルの大きさ(Mega bytes)。 Sensible values range from 1M to 1/nth of the size of the buffer pool specified below, where n is the number of log files in the group. The bigger the value, the less checkpoint flush activity is needed in the buffer pool, saving disk I/O. But bigger log files also mean that recovery will be slower in case of a crash. The combined size of log files must be < 4 GB on 32-bit computers. @item @code{innodb_log_buffer_size} @tab InnoDB が、disk上のログファイルにログを書き出すために使用する、 バッファのサイズ。 Sensible values range from 1M to 8M. A big log buffer allows large transactions to run without a need to write the log to disk until the transaction commit. Thus, if you have big transactions, making the log buffer big will save disk I/O. @item @code{innodb_flush_log_at_trx_commit} @tab Normally this is set to 1, meaning that at a transaction commit the log is flushed to disk, and the modifications made by the transaction become permanent, and survive a database crash. If you are willing to compromise this safety, and you are running small transactions, you may set this to 0 to reduce disk I/O to the logs. @item @code{innodb_log_arch_dir} @tab The directory where fully written log files would be archived if we used log archiving. ＊現在のところ、これには、 @code{innodb_log_group_home_dir} と同じ値をセットしなくてはなりません。＊ @item @code{innodb_log_archive} @tab This value should currently be set to 0. As recovery from a backup is done by MySQL using its own log files, there is currently no need to archive InnoDB log files. @item @code{innodb_buffer_pool_size} @tab InnoDB がデータやテーブルのインデックスををキャッシュするために使用する メモリのサイズ。 大きな値をセットすると、テーブルのデータへのアクセスに必要なディスク i/o が少なくなります。 データベースサーバ専用のマシンでは、このパラメタを物理メモリの 80% まで セットしてもかまいません。 物理メモリの競合がオペレーティングシステムのページングの原因に なるかもしれないので、あまりに大きすぎる値は与えないように。 @item @code{innodb_additional_mem_pool_size} @tab Size of a memory pool InnoDB uses to store data dictionary information and other internal data structures. A sensible value for this might be 2M, but the more tables you have in your application the more you will need to allocate here. If InnoDB runs out of memory in this pool, it will start to allocate memory from the operating system, and write warning messages to the MySQL error log. @item @code{innodb_file_io_threads} @tab Number of file I/O threads in InnoDB. Normally, this should be 4, but on Windows disk I/O may benefit from a larger number. @item @code{innodb_lock_wait_timeout} @tab Timeout in seconds an InnoDB transaction may wait for a lock before being rolled back. InnoDB は自動的にトランザクションのデッド・ロックがテーブルに起きた事 を感知し、そのトランザクションをロール・バックします。 If you use @code{LOCK TABLES} command, or other transaction-safe storage engines than InnoDB in the same transaction, then a deadlock may arise which InnoDB cannot notice. In cases like this the timeout is useful to resolve the situation. @item @code{innodb_flush_method} @tab (3.23.40 以上からの機能.) The default value for this is @code{fdatasync}. Another option is @code{O_DSYNC}. @end multitable @node InnoDB init, Using InnoDB tables, InnoDB start, InnoDB @subsection InnoDB テーブルの保存先の作成 あなたが MySQL を既にインストールしており、@file{my.cnf} には InnoDB configuration パラメタが記述されていると仮定します。 MySQL を起動する前に、 あなたが指定している InnoDB データファイルとログファイルを保存する ディレクトリが存在するか、 そして、それらのディレクトリのパーミッションが正しいかを 確認するべきです。 InnoDB はディレクトリを自動では作成できません。ファイルのみです。 データとログファイルを保存するために十分なディスクの空きがあるかも チェックしてください。 MySQL を起動すると、InnoDB は data file と log file を作成します。 InnoDB は以下のようなメッセージを出力します： @example ~/mysqlm/sql > mysqld InnoDB: The first specified datafile /home/heikki/data/ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file /home/heikki/data/ibdata1 size to 134217728 InnoDB: Database physically writes the file full: wait... InnoDB: datafile /home/heikki/data/ibdata2 did not exist: new to be created InnoDB: Setting file /home/heikki/data/ibdata2 size to 262144000 InnoDB: Database physically writes the file full: wait... InnoDB: Log file /home/heikki/data/logs/ib_logfile0 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile0 size to 5242880 InnoDB: Log file /home/heikki/data/logs/ib_logfile1 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile1 size to 5242880 InnoDB: Log file /home/heikki/data/logs/ib_logfile2 did not exist: new to be created InnoDB: Setting log file /home/heikki/data/logs/ib_logfile2 size to 5242880 InnoDB: Started mysqld: ready for connections @end example 新しく InnoDB データベースが、これで作成されました。 @code{mysql} のような MySQL クライアントを使用して、MySQL サーバに 接続することが可能です。 @file{mysqladmin shutdown} で MySQL をシャットダウンしたときには、 InnoDB は以下のようなメッセージを出力します： @example 010321 18:33:34 mysqld: Normal shutdown 010321 18:33:34 mysqld: Shutdown Complete InnoDB: Starting shutdown... InnoDB: Shutdown completed @end example You can now look at the datafiles and logs directories and you will see the files created. ログディレクトリには、@file{ib_arch_log_0000000000} という名前の、 小さなファイルが含まれているはずです。 That file resulted from the database creation, after which InnoDB switched off log archiving. MySQL が次回に起動したとき、出力は次のようになります： @example ~/mysqlm/sql > mysqld InnoDB: Started mysqld: ready for connections @end example @menu * Error creating InnoDB:: If something goes wrong in database creation @end menu @node Error creating InnoDB, , InnoDB init, InnoDB init @subsubsection InnoDB データベース作成に失敗した場合 If InnoDB prints an operating system error in a file operation, usually the problem is one of the following: @itemize @bullet @item You did not create InnoDB data or log directories. @item @file{mysqld} does not have the rights to create files in those directories. @item @file{mysqld} does not read the right @file{my.cnf} or @file{my.ini} file, and consequently does not see the options you specified. @item The disk is full or a disk quota is exceeded. @item You have created a subdirectory whose name is equal to a datafile you specified. @item There is a syntax error in @code{innodb_data_home_dir} or @code{innodb_data_file_path}. @end itemize もし InnoDB database 作成時になにか問題が起きたならば、 InnoDB によって作成された全てのファイルを削除すべきです。 This means all datafiles, all log files, the small archived log file, and in the case you already did create some InnoDB tables, delete also the corresponding @file{.frm} files for these tables from the MySQL database directories. Then you can try the InnoDB database creation again. @node Using InnoDB tables, Adding and removing, InnoDB init, InnoDB @subsection InnoDB テーブルの作成 @code{mysql test} として MySQL クライアントを実行したとします。 InnoDB 形式のテーブルを作成するためには、あなたは SQL コマンドの テーブル作成文に、@code{TYPE = InnoDB} を指定しなくてはなりません。 @example CREATE TABLE CUSTOMER (A INT, B CHAR (20), INDEX (A)) TYPE = InnoDB; @end example この SQL コマンドは、@file{my.cnf} で定義された InnoDB のテーブル空間に存在する データファイル内に、一つのテーブルと、一つのインデックス (@code{A} フィールドに張られた)を作成します。 MySQL は @file{CUSTOMER.frm} ファイルを MuSQL データベースディレクトリ @file{test} に作成します。 内部では、InnoDB は、InnoDB 自身のデータディレクトリをもち、 そこに @code{'test/CUSTOMER'} テーブルのエントリを追加します。 よって、MySQL 内の違うデータベース内に、同じ @code{CUSTOMER} という 名前を持つテーブルを作成することが可能で、もちろんこの名前は、 InnoDB 内でも他とは衝突しません。 MySQL の table status コマンドを使用して、@code{TYPE = InnoDB} で作成した テーブル全てに対して、InnoDB のテーブル空間の未使用量が どれくらいあるかを出すことができます。 テーブル空間の未使用領域の総量は、@code{SHOW} で出力された テーブルの comment セクションに現われます。 例： @example SHOW TABLE STATUS FROM test LIKE 'CUSTOMER' @end example @code{SHOW} を使用して得られた InnoDB のテーブルの情報は概算です； それらは SQL オプティマイゼイションで使用されます。 ただし、テーブルとインデックスに割り当てられているサイズ(bytes)は正確です。 @subsubsection MyISAM テーブルを InnoDB テーブルに変換 InnoDB does not have a special optimization for separate index creation. Therefore it does not pay to export and import the table and create indexes afterwards. 素早くテーブルを InnoDB に変換する方法は、 InnoDB に直接 insert することです。 テーブルの変換には、@code{ALTER TABLE ... TYPE=INNODB} を使用するか、 空の InnoDB テーブルを作成してデータを @code{INSERT INTO ... SELECT * FROM ...} でインサートします。 insert 時においては、大きなテーブルの場合は、いくつかにテーブルを 分割して行うとよいでしょう： @example INSERT INTO newtable SELECT * FROM oldtable WHERE yourkey > something AND yourkey <= somethingelse; @end example 全てのデータが挿入できたら、テーブル名を変更します。 大きなテーブルを変換している間は、InnoDB のバッファプールサイズを 大きくすることで、disk I/O を軽減できます。 ただし、物理メモリの 80% 以上をバッファに割り当てないように。 InnoDB log ファイルのサイズもログのバッファも大きく取るべきです。 確実に、テーブル空間より大きくならないようにします； InnoDB テーブルは MyISAM テーブルよりも多くの disk を使用します。 もし @code{ALTER TABLE} が取っている領域よりも超えた場合には、 ロール・バックが開始されます。 これは ディスク・バウンドのために (大きなファイルならば) 数時間かかるかもしれません。 インサートする場合には、InnoDB は インサート・バッファ を使用します。 これはセカンダリ・インデックス・レコードをインデックスに一度にマージ させるために使用されます。 このため多くの disk I/O が節約されます。 ロール・バックにおいては、インサートで使用されるようなメカニズムは無く、 ロール・バックは、インサートの 約30倍、時間がかかります。 このような手に負えないロール・バックのばあい、 もし、価値のあるデータがあなたの InnoDB データベース内に一つもなければ、 データベースのプロセスをキルして全ての InnoDB データファイルとログファイルを 消去し、全ての InnoDB テーブルの @file{.frm} ファイルを消し、 そしてもう一度試みる方が良いでしょう。 とてつもなく多くの disk I/O が完了するのを待つよりも。 @subsubsection 外部キー制約 (Foreign Key Constraints) (3.23.44以上) InnoDB バージョン 3.23.43b 以上では foreign key constraints を持ちます. InnoDB is the first MySQL table type which allows you to define foreign key constraints to guard the integrity of your data. The syntax of a foreign key constraint definition in InnoDB: @example [CONSTRAINT symbol] FOREIGN KEY (index_col_name, ...) REFERENCES table_name (index_col_name, ...) [ON DELETE @{CASCADE | SET NULL | NO ACTION | RESTRICT@}] [ON UPDATE @{CASCADE | SET NULL | NO ACTION | RESTRICT@}] @end example Both tables have to be InnoDB type and @strong{there must be an index where the foreign key and the referenced key are listed as the FIRST columns}. InnoDB does not auto-create indexes on foreign keys or referenced keys: you have to create them explicitly. Corresponding columns in the foreign key and the referenced key must have similar internal data types inside InnoDB so that they can be compared without a type conversion. The @strong{size and the signedness of integer types has to be the same}. The length of string types need not be the same. If you specify a @code{SET NULL} action, make sure you have @strong{not declared the columns in the child table} @code{NOT NULL}. If MySQL gives the error number 1005 from a @code{CREATE TABLE} statement, and the error message string refers to errno 150, then the table creation failed because a foreign key constraint was not correctly formed. Similarly, if an @code{ALTER TABLE} fails and it refers to errno 150, that means a foreign key definition would be incorrectly formed for the altered table. Starting from version 3.23.50 you can also associate the @code{ON DELETE CASCADE} or @code{ON DELETE SET NULL} clause with the foreign key constraint. Starting from version 4.0.8 you can use also similar @code{ON UPDATE} actions. If @code{ON DELETE CASCADE} is specified, and a row in the parent table is deleted, then InnoDB automatically deletes also all those rows in the child table whose foreign key values are equal to the referenced key value in the parent row. If @code{ON DELETE SET NULL} is specified, the child rows are automatically updated so that the columns in the foreign key are set to the SQL NULL value. Starting from version 3.23.50, InnoDB does not check foreign key constraints on those foreign key or referenced key values which contain a NULL column. Starting from version 3.23.50 the InnoDB parser allows you to use backquotes (`) around table and column names in the @code{FOREIGN KEY ... REFERENCES ...} clause but the InnoDB parser is not yet aware of the option @code{lower_case_table_names} you can specify in @file{my.cnf}. 例: @example CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id)) TYPE=INNODB; CREATE TABLE child(id INT, parent_id INT, INDEX par_ind (parent_id), FOREIGN KEY (parent_id) REFERENCES parent(id) ON DELETE SET NULL ) TYPE=INNODB; @end example (訳注： 両方のテーブルとも、InnoDB でなくてはなりません。 さらに foreign key と the referenced key に指定される項目は、 インデックス中の定義の中では、最初の項目として、 指定されていなければなりません。 上記の例では、@code{FOREIGN KEY} で指定されている @code{V, U} は、 インデックスの最初の項目に指定されています。) Starting from version 3.23.50 InnoDB allows you to add a new foreign key constraint to a table through @example ALTER TABLE yourtablename ADD [CONSTRAINT symbol] FOREIGN KEY (...) REFERENCES anothertablename(...) [on_delete_and_on_update_actions] @end example Remember to create the required indexes first, though. In InnoDB versions < 3.23.50 @code{ALTER TABLE} or @code{CREATE INDEX} should not be used in connection with tables which have foreign key constraints or which are referenced in foreign key constraints: Any @code{ALTER TABLE} removes all foreign key constrainst defined for the table. You should not use @code{ALTER TABLE} to the referenced table either, but use @code{DROP TABLE} and @code{CREATE TABLE} to modify the schema. When MySQL does an @code{ALTER TABLE} it may internally use @code{RENAME TABLE}, and that will confuse the foreign key costraints which refer to the table. A @code{CREATE INDEX} statement is in MySQL processed as an @code{ALTER TABLE}, and these restrictions apply also to it. When doing foreign key checks InnoDB sets shared row level locks on child or parent records it has to look at. InnoDB checks foreign key constraints immediately: the check is not deferred to transaction commit. InnoDB allows you to drop any table even though that would break the foreign key constraints which reference the table. When you drop a table the constraints which were defined in its create statement are also dropped. If you re-create a table which was dropped, it has to have a definition which conforms to the foreign key constraints referencing it. It must have the right column names and types, and it must have indexes on the referenced keys, as stated above. If these are not satisfied, MySQL returns error number 1005 and refers to errno 150 in the error message string. Starting from version 3.23.50 InnoDB returns the foreign key definitions of a table when you call @example SHOW CREATE TABLE yourtablename @end example Then also @file{mysqldump} produces correct definitions of tables to the dump file, and does not forget about the foreign keys. You can also list the foreign key constraints for a table @code{T} with @example SHOW TABLE STATUS FROM yourdatabasename LIKE 'T' @end example The foreign key constraints are listed in the table comment of the output. @node Adding and removing, Backing up, Using InnoDB tables, InnoDB @subsection InnoDB データとログの追加と削除 バージョン 3.23.50以上の3.23, 4.0.2以上では InnoDB の最後のデータファイルを @code{autoextend} に指定することが可能です。 それ未満のバージョンでは、データファイルを追加することで テーブルの空間を大きくすることが可能です。 テーブルの空間を大きくするためには、新しいデータファイルを追加します。 これを行なうには、MySQL サーバーを一度シャットダウンし、 @file{my.cnf} ファイルを編集して新しいデータファイルを @code{innodb_data_file_path} に追加し、MySQL サーバを起動します。 今のところ、データファイルを InnoDB から削除することはできません。 データベースのサイズを小さくするには、 一度 @code{mysqldump} でテーブルをダンプし、 新しくデータベースを作成し、ダンプしたテーブルを取り込みます。 もし InnoDB のログファイルのサイズを変更したいならば、 MySQL サーバを停止しなくてはなりません(エラー無しで確実に止まるようにしてください)。 なにかシャットダウン時に問題があった場合には、 古いログファイルを安全な場所にコピーし、 データベースの修復をしましょう。 そして、古いログファイルを log ファイルのディレクトリから消去し、 @file{my.cnf} ファイルを編集した後、MySQL サーバを起動します。 InnoDB は 新しいログファイルを作成したことを告げるでしょう。 @node Backing up, Moving, Adding and removing, InnoDB @subsection InnoDB データベースのバックアップと修復 The key to safe database management is taking regular backups. InnoDB Hot Backup is an online backup tool you can use to backup your InnoDB database while it is running. InnoDB Hot Backup does not require you to shut down your database and it does not set any locks or disturb your normal database processing. InnoDB Hot Backup is a non-free additional tool which is not included in the standard MySQL distribution. See the InnoDB Hot Backup homepage @uref{http://www.innodb.com/hotbackup.html} for detailed information and screenshots. If you are able to shut down your MySQL server, then to take a 'binary' backup of your database you have to do the following: @itemize @bullet @item MySQL を停止。エラー無しで確実に止まるように。 @item 全てのデータファイルを安全な場所にコピー。 @item 全ての InnoDB ログファイルを安全な場所にコピー。 @item @file{my.cnf} 設定ファイルを安全な場所にコピー。 @item InnoDB テーブルの @file{.frm} ファイルを安全な場所にコピー。 @end itemize 上のバイナリバックアップに加えて、@file{mysqldump} で通常のテーブルの ダンプも取るべきです。 この理由は、バイナリファイルはあなたの知らないところで おかしくなっているかもしれないからです。 テキストファイルのダンプされたテーブルは人間が読むことができ、 そしてバイナリファイルよりもずっと簡素です。 ダンプされたファイルからテーブルのおかしくなった箇所を見つけるのは容易で、 そして、致命的なデータの不正を少なくするチャンスでもあります。 データベースのバイナリバックアップと同時に、ダンプを取ることは、 よい考えです。 全テーブルを現在の状況と矛盾無くダンプするためには、全てのクライアントを データベースからシャット・アウトするべきです。 Then you can take the binary backup, and you will then have a consistent snapshot of your database in two formats. To be able to recover your InnoDB database to the present from the binary backup described above, you have to run your MySQL database with the general logging and log archiving of MySQL switched on. Here by the general logging we mean the logging mechanism of the MySQL server which is independent of InnoDB logs. MySQL サーバプロセスのクラッシュからのリカバリを行なうには、 MySQL をリスタートすることがただ一つの方法です。 InnoDB は自動で ログ をチェックし、データベースの roll-forward を 行ないます。 InnoDB は、クラッシュ時にコッミトされていないトランザクションを 自動的にロールバックします。 リカバリの間、InnoDB は以下のような出力をします： @example ~/mysqlm/sql > mysqld InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 13674004 InnoDB: Doing recovery: scanned up to log sequence number 0 13739520 InnoDB: Doing recovery: scanned up to log sequence number 0 13805056 InnoDB: Doing recovery: scanned up to log sequence number 0 13870592 InnoDB: Doing recovery: scanned up to log sequence number 0 13936128 ... InnoDB: Doing recovery: scanned up to log sequence number 0 20555264 InnoDB: Doing recovery: scanned up to log sequence number 0 20620800 InnoDB: Doing recovery: scanned up to log sequence number 0 20664692 InnoDB: 1 uncommitted transaction(s) which must be rolled back InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx no 16745 InnoDB: Rolling back of trx no 16745 completed InnoDB: Rollback of uncommitted transactions completed InnoDB: Starting an apply batch of log records to the database... InnoDB: Apply batch completed InnoDB: Started mysqld: ready for connections @end example If your database gets corrupted or your disk fails, you have to do the recovery from a backup. In the case of corruption, you should first find a backup which is not corrupted. From a backup do the recovery from the general log files of MySQL according to instructions in the MySQL manual. @menu * InnoDB checkpoints:: Checkpoints @end menu @node InnoDB checkpoints, , Backing up, Backing up @subsubsection Checkpoints InnoDB は fuzzy checkpoint と呼ばれる チェックポイントのメカニズムを持っています。 InnoDB will flush modified database pages from the buffer pool in small batches, there is no need to flush the buffer pool in one single batch, which would in practice stop processing of user SQL statements for a while. クラッシュ・リカバリ時には、InnoDB はログファイルに書かれた チェックポイント・ラベルを見ます。 データベースのディスク・イメージ上にそのラベルが反映させられる前に、 それはデータベースの全ての変更を知っています。 It knows that all modifications to the database before the label are already present on the disk image of the database. Then InnoDB scans the log files forward from the place of the checkpoint applying the logged modifications to the database. InnoDB はログファイルを循環して使用します。 全てのコミットされた変更分(変更だから当然バッファプール内のデータベースのページとディスク上のイメージが違う)は、InnoDB がリカバリを実行しなければならない時に、ログファイルに存在しなければなりません。(でなければリカバリを行なうことができません。) これは、InnoDB がログファイルを循環的に再利用しようとした時に、ディスク上のデータベースページのイメージに、既にログファイルに記録されていた変更分が含まれていなければならないということです。 言い換えれば、InnoDB はチェックポイントを作成しなければならず、そしてこれは変更されたデータベースのページをディスクにフラッシュすることをしばしば引き起こすことになります。 InnoDB writes to the log files in a circular fashion. All committed modifications which make the database pages in the buffer pool different from the images on disk must be available in the log files in case InnoDB has to do a recovery. This means that when InnoDB starts to reuse a log file in the circular fashion, it has to make sure that the database page images on disk already contain the modifications logged in the log file InnoDB is going to reuse. In other words, InnoDB has to make a checkpoint and often this involves flushing of modified database pages to disk. 上に述べた事柄は、なぜログファイルをとても大きく作成することが チェックポイント作成において disk I/O を減らすことになるのかの理由です。 The above explains why making your log files very big may save disk I/O in checkpointing. It can make sense to set the total size of the log files as big as the buffer pool or even bigger. The drawback in big log files is that crash recovery can last longer because there will be more log to apply to the database. @node Moving, InnoDB transaction model, Backing up, InnoDB @subsection InnoDB データベースを他の機械に移動する InnoDB データとログファイルは、 もし、その機械の浮動小数点数のフォーマットが同じであれば、 全プラットフォームでバイナリ互換を持ちます。 InnoDB は、単純に、関連ファイルを全てコピーすることで移動可能です。 (関連ファイルは前節で述べられています)　 InnoDB データベースは、全てのファイルを単純にコピーするだけで、 移動が可能です。 ファイルは、前述のデータベースのバックアップの節で 述べたものです。 もし浮動小数点数のフォーマットが違う機械であったとしても、 テーブルに @code{FLOAT} や @code{DOUBLE} の型を使用していないのであれば、 手順は同じです： すなわち単にファイルをコピーするだけです。 もし浮動小数点数のフォーマットが違う機械で、テーブルに 浮動小数点数を保存している場合は、 @file{mysqldump} と @file{mysqlimport} コマンドを使用して テーブルを移動しなくてはなりません。 A performance tip is to switch off auto-commit mode when you import data into your database, assuming your tablespace has enough space for the big rollback segment the big import transaction will generate. Do the commit only after importing a whole table or a segment of a table. @node InnoDB transaction model, Implementation, Moving, InnoDB @subsection InnoDB Transaction Model In the InnoDB transaction model the goal has been to combine the best properties of a multi-versioning database to traditional two-phase locking. InnoDB does locking on row level and runs queries by default as non-locking consistent reads, in the style of Oracle. The lock table in InnoDB is stored so space-efficiently that lock escalation is not needed: typically several users are allowed to lock every row in the database, or any random subset of the rows, without InnoDB running out of memory. In InnoDB all user activity happens inside transactions. もし、autocommit mode が MySQL で使用されているなら、 それぞれの SQL 文は単一の transaction となります。 MySQL always starts a new connection with the autocommit mode switched on. もし autocommit mode が @code{SET AUTOCOMMIT = 0} で off にされたなら、 ユーザーは常にトランザクションが可能な状態となります。 もし SQL の @code{COMMIT} or @code{ROLLBACK} 文を実行すると、 現在のトランザクションは完結し、新しいトランザクションが開始します。 どちらの文も全ての InnoDB のロック(カレントのトランザクションに セットされたロック)を外します。 A @code{COMMIT} means that the changes made in the current transaction are made permanent and become visible to other users. A @code{ROLLBACK}, on the other hand, cancels all modifications made by the current transaction. If the connection has @code{AUTOCOMMIT = 1}, then the user can still perform a multi-statement transaction by starting it with @code{BEGIN} and ending it with @code{COMMIT} or @code{ROLLBACK}. In terms of the SQL-1992 transaction isolation levels, the InnoDB default is @code{REPEATABLE READ}. Starting from version 4.0.5, InnoDB offers all 4 different transaction isolation levels described by the SQL-1992 standard. You can set the default isolation level for all connections in the @code{[mysqld]} section of @file{my.cnf}: @example transaction-isolation = @{READ-UNCOMMITTED | READ-COMMITTED | REPEATABLE-READ | SERIALIZABLE@} @end example A user can change the isolation level of a single session or all new incoming connections with the @example SET [SESSION | GLOBAL] TRANSACTION ISOLATION LEVEL @{READ UNCOMMITTED | READ COMMITTED | REPEATABLE READ | SERIALIZABLE@} @end example SQL statement. Note that there are no hyphens in level names in the SQL syntax. If you specify the keyword @code{GLOBAL} in the above statement, it will determine the initial isolation level of new incoming connections, but will not change the isolation level of old connections. Any user is free to change the isolation level of his session, even in the middle of a transaction. In versions < 3.23.50 @code{SET TRANSACTION} had no effect on InnoDB tables. In versions < 4.0.5 only @code{REPEATABLE READ} and @code{SERIALIZABLE} were available. You can query the global and session transaction isolation levels with: @example SELECT @@@@global.tx_isolation; SELECT @@@@tx_isolation; @end example In row level locking InnoDB uses so-called next-key locking. That means that besides index records, InnoDB can also lock the 'gap' before an index record to block insertions by other users immediately before the index record. A next-key lock means a lock which locks an index record and the gap before it. A gap lock means a lock which only locks a gap before some index record. A detailed description of each isolation level in InnoDB: @itemize @bullet @item @code{READ UNCOMMITTED} This is also called 'dirty read': non-locking @code{SELECT}s are performed so that we do not look at a possible earlier version of a record; thus they are not 'consistent' reads under this isolation level; otherwise this level works like @code{READ COMMITTED}. @item @code{READ COMMITTED} Somewhat Oracle-like isolation level. All @code{SELECT ... FOR UPDATE} and @code{SELECT ... LOCK IN SHARE MODE} statements only lock the index records, NOT the gaps before them, and thus allow free inserting of new records next to locked records. @code{UPDATE} and @code{DELETE} which use a unique index with a unique search condition, only lock the index record found, not the gap before it. But still in range type @code{UPDATE} and @code{DELETE} InnoDB must set next-key or gap locks and block insertions by other users to the gaps covered by the range. This is necessary since 'phantom rows' have to be blocked for MySQL replication and recovery to work. @strong{Consistent reads} behave like in Oracle: each consistent read, even within the same transaction, sets and reads its own fresh snapshot. @item @code{REPEATABLE READ} This is the default isolation level of InnoDB. @code{SELECT ... FOR UPDATE}, @code{SELECT ... LOCK IN SHARE MODE}, @code{UPDATE}, and @code{DELETE} which use a unique index with a unique search condition, only lock the index record found, not the gap before it. Otherwise these operations employ next-key locking, locking the index range scanned with next-key or gap locks, and block new insertions by other users. In @strong{consistent reads} there is an important difference from the previous isolation level: in this level all consistent reads within the same transaction read the same snapshot established by the first read. This convention means that if you issue several plain @code{SELECT}s within the same transaction, these @code{SELECT}s are consistent also with respect to each other. @item @code{SERIALIZABLE} This level is like the previous one, but all plain @code{SELECT}s are implicitly converted to @code{SELECT ... LOCK IN SHARE MODE}. @end itemize @menu * InnoDB consistent read:: Consistent Read * InnoDB locking reads:: Locking Reads * InnoDB Next-key locking:: Next-key Locking: Avoiding the Phantom Problem * InnoDB Locks set:: Locks Set by Different SQL Statements in InnoDB * InnoDB Deadlock detection:: Deadlock Detection and Rollback * InnoDB Consistent read example:: An Example of How the Consistent Read Works in InnoDB * Innodb deadlocks:: How to cope with deadlocks? * Innodb tuning:: Performance Tuning Tips * Innodb Monitor:: The InnoDB Monitor @end menu @node InnoDB consistent read, InnoDB locking reads, InnoDB transaction model, InnoDB transaction model @subsubsection Consistent Read A consistent read means that InnoDB uses its multi-versioning to present to a query a snapshot of the database at a point in time. The query will see the changes made by exactly those transactions that committed before that point of time, and no changes made by later or uncommitted transactions. The exception to this rule is that the query will see the changes made by the transaction itself which issues the query. If you are running with the default @code{REPEATABLE READ} isolation level, then all consistent reads within the same transaction read the snapshot established by the first such read in that transaction. You can get a fresher snapshot for your queries by committing the current transaction and after that issuing new queries. Consistent read is the default mode in which InnoDB processes @code{SELECT} statements in @code{READ COMMITTED} and @code{REPEATABLE READ} isolation levels. A consistent read does not set any locks on the tables it accesses, and therefore other users are free to modify those tables at the same time a consistent read is being performed on the table. @node InnoDB locking reads, InnoDB Next-key locking, InnoDB consistent read, InnoDB transaction model @subsubsection Locking Reads consistent read は、いくつかの状況下では好都合ではありません。 あなたが新しいレコードを @code{CHILD} テーブルに加えたいとします。 この child はすでに @code{PARENT} テーブルにある parent を 確実に持っているものとします。 そしてあなたが @code{PARENT} テーブルを読むために、consistent read を 使用するとします。そのテーブル内に、たしかに、その child の parent を 見たとします。 この場合、その child のレコードを安全に @code{CHILD} テーブルに 追加することが可能でしょうか？ 答えは No 。 なぜなら、あなたが気がつかない内に、 他のユーザーがその parent のレコードを @code{PARENT} テーブルから 消してしまうかも知れないからです。 この解決として、@code{SELECT} を locking mode で動作させる方法が あります。 @code{LOCK IN SHARE MODE}. @example SELECT * FROM PARENT WHERE NAME = 'Jones' LOCK IN SHARE MODE; @end example Performing a read in share mode means that we read the latest available data, and set a shared mode lock on the rows we read. If the latest data belongs to a yet uncommitted transaction of another user, we will wait until that transaction commits. A shared mode lock prevents others from updating or deleting the row we have read. After we see that the above query returns the parent @code{'Jones'}, we can safely add his child to table @code{CHILD}, and commit our transaction. This example shows how to implement referential integrity in your application code. Let us look at another example: we have an integer counter field in a table @code{CHILD_CODES} which we use to assign a unique identifier to each child we add to table @code{CHILD}. Obviously, using a consistent read or a shared mode read to read the present value of the counter is not a good idea, since then two users of the database may see the same value for the counter, and we will get a duplicate key error when we add the two children with the same identifier to the table. In this case there are two good ways to implement the reading and incrementing of the counter: (1) update the counter first by incrementing it by 1 and only after that read it, or (2) read the counter first with a lock mode @code{FOR UPDATE}, and increment after that: @example SELECT COUNTER_FIELD FROM CHILD_CODES FOR UPDATE; UPDATE CHILD_CODES SET COUNTER_FIELD = COUNTER_FIELD + 1; @end example A @code{SELECT ... FOR UPDATE} will read the latest available data setting exclusive locks on each row it reads. Thus it sets the same locks a searched SQL @code{UPDATE} would set on the rows. @node InnoDB Next-key locking, InnoDB Locks set, InnoDB locking reads, InnoDB transaction model @subsubsection Next-key Locking: Avoiding the Phantom Problem row level のロッキングにおいては、InnoDB は next-key locking と呼ばれる アルゴリズムを使用します。 InnoDB does the row level locking so that when it searches or scans an index of a table, it sets shared or exclusive locks on the index records in encounters. Thus the row level locks are more precisely called index record locks. The locks InnoDB sets on index records also affect the 'gap' before that index record. If a user has a shared or exclusive lock on record R in an index, then another user cannot insert a new index record immediately before R in the index order. This locking of gaps is done to prevent the so-called phantom problem. Suppose I want to read and lock all children with identifier bigger than 100 from table @code{CHILD}, and update some field in the selected rows. @example SELECT * FROM CHILD WHERE ID > 100 FOR UPDATE; @end example @code{CHILD} テーブルの @code{ID} フィールドにインデックスが 張られているとします。 Our query will scan that index starting from the first record where @code{ID} is bigger than 100. Now, if the locks set on the index records would not lock out inserts made in the gaps, a new child might meanwhile be inserted to the table. If now I in my transaction execute @example SELECT * FROM CHILD WHERE ID > 100 FOR UPDATE; @end example again, I will see a new child in the result set the query returns. This is against the isolation principle of transactions: a transaction should be able to run so that the data it has read does not change during the transaction. If we regard a set of rows as a data item, then the new 'phantom' child would break this isolation principle. When InnoDB scans an index it can also lock the gap after the last record in the index. Just that happens in the previous example: the locks set by InnoDB will prevent any insert to the table where @code{ID} would be bigger than 100. You can use next-key locking to implement a uniqueness check in your application: if you read your data in share mode and do not see a duplicate for a row you are going to insert, then you can safely insert your row and know that the next-key lock set on the successor of your row during the read will prevent anyone meanwhile inserting a duplicate for your row. Thus the next-key locking allows you to 'lock' the non-existence of something in your table. @node InnoDB Locks set, InnoDB Deadlock detection, InnoDB Next-key locking, InnoDB transaction model @subsubsection Locks Set by Different SQL Statements in InnoDB @itemize @bullet @item @code{SELECT ... FROM ...} : this is a consistent read, reading a snapshot of the database and setting no locks. @item @code{SELECT ... FROM ... LOCK IN SHARE MODE} : sets shared next-key locks on all index records the read encounters. @item @code{SELECT ... FROM ... FOR UPDATE} : sets exclusive next-key locks on all index records the read encounters. @item @code{INSERT INTO ... VALUES (...)} : sets an exclusive lock on the inserted row; note that this lock is not a next-key lock and does not prevent other users from inserting to the gap before the inserted row. If a duplicate key error occurs, sets a shared lock on the duplicate index record. @item @code{INSERT INTO T SELECT ... FROM S WHERE ...} sets an exclusive (non-next-key) lock on each row inserted into @code{T}. Does the search on @code{S} as a consistent read, but sets shared next-key locks on @code{S} if the MySQL logging is on. InnoDB has to set locks in the latter case because in roll-forward recovery from a backup every SQL statement has to be executed in exactly the same way as it was done originally. @item @code{CREATE TABLE ... SELECT ...} performs the @code{SELECT} as a consistent read or with shared locks, like in the previous item. @item @code{REPLACE} is done like an insert if there is no collision on a unique key. Otherwise, an exclusive next-key lock is placed on the row which has to be updated. @item @code{UPDATE ... SET ... WHERE ...} : sets an exclusive next-key lock on every record the search encounters. @item @code{DELETE FROM ... WHERE ...} : sets an exclusive next-key lock on every record the search encounters. @item If a @code{FOREIGN KEY} constraint is defined on a table, any insert, update, or delete which requires checking of the constraint condition sets shared record level locks on the records it looks at to check the constraint. Also in the case where the constraint fails, InnoDB sets these locks. @item @code{LOCK TABLES ... } : sets table locks. In the implementation the MySQL layer of code sets these locks. The automatic deadlock detection of InnoDB cannot detect deadlocks where such table locks are involved: see the following section. Also, since MySQL does know about row level locks, it is possible that you get a table lock on a table where another user currently has row level locks. But that does not put transaction integerity into danger. @xref{InnoDB restrictions}. @end itemize @node Innodb deadlocks, Innodb tuning, InnoDB Consistent read example, InnoDB transaction model @subsubsection How to cope with deadlocks? Deadlocks are a classic problem in transactional databases, but they are not dangerous, unless they are so frequent that you cannot run certain transactions at all. Normally you have to write your applications so that they are always prepared to re-issue a transaction if it gets rolled back because of a deadlock. InnoDB uses automatic row level locking. You can get deadlocks even in the case of transactions which just insert or delete a single row. That is because these operations are not really 'atomic': they automatically set locks on the (possibly several) index records of the row inserted/deleted. You can cope with deadlocks and reduce the number of them with the following tricks: @itemize @bullet @item Use @code{SHOW INNODB STATUS} in MySQL versions >= 3.23.52 and >= 4.0.3 to determine the cause of the latest deadlock. That can help you to tune your application to avoid deadlocks. @item Always be prepared to re-issue a transaction if it fails in a deadlock. Deadlocks are not dangerous. Just try again. @item Commit your transactions often. Small transactions are less prone to collide. @item If you are using locking reads @code{SELECT ... FOR UPDATE} or @code{... LOCK IN SHARE MODE}, try using a lower isolation level @code{READ COMMITTED}. @item Access your tables and rows in a fixed order. Then transactions will form nice queues, and do not deadlock. @item Add good indexes to your tables. Then your queries need to scan less index records and consequently set less locks. Use @code{EXPLAIN SELECT} to determine that MySQL picks appropriate indexes for your queries. @item Use less locking: if you can afford a @code{SELECT} to return data from an old snapshot, do not add the clause @code{FOR UPDATE} or @code{LOCK IN SHARE MODE} to it. Using @code{READ COMMITTED} isolation level is good here, because each consistent read within the same transaction reads from its own fresh snapshot. @item If nothing helps, serialize your transactions with table level locks: @code{LOCK TABLES t1 WRITE, t2 READ, ... ; [do something with tables t1 and t2 here]; UNLOCK TABLES}. Table level locks make you transactions to queue nicely, and deadlocks are avoided. Note that @code{LOCK TABLES} implicitly starts a transaction, just like the command @code{BEGIN}, and @code{UNLOCK TABLES} implicitly ends the transaction in a @code{COMMIT}. @item Another solution to serialize transactions is to create an auxiliary 'semaphore' table where there is just a single row. Each transaction updates that row before accessing other tables. In that way all transactions happen in a serial fashion. Note that then also the InnoDB instant deadlock detection algorithm works, because the serializing lock is a row level lock. In MySQL table level locks we have to resort to the timeout method to resolve a deadlock. @end itemize @node InnoDB Deadlock detection, InnoDB Consistent read example, InnoDB Locks set, InnoDB transaction model @subsubsection Deadlock Detection and Rollback InnoDB automatically detects a deadlock of transactions and rolls back a transaction or transactions to prevent the deadlock. Starting from version 4.0.5, InnoDB will try to pick small transactions to roll back. The size of a transaction is determined by the number of rows it has inserted, updated, or deleted. Previous to 4.0.5, InnoDB always rolled back the transaction whose lock request was the last one to build a deadlock, that is, a cycle in the waits-for graph of transactions. InnoDB cannot detect deadlocks where a lock set by a MySQL @code{LOCK TABLES} statement is involved, or if a lock set in another storage engine than InnoDB is involved. You have to resolve these situations using @code{innodb_lock_wait_timeout} set in @file{my.cnf}. When InnoDB performs a complete rollback of a transaction, all the locks of the transaction are released. However, if just a single SQL statement is rolled back as a result of an error, some of the locks set by the SQL statement may be preserved. This is because InnoDB stores row locks in a format where it cannot afterwards know which was set by which SQL statement. @node InnoDB Consistent read example, Innodb deadlocks, InnoDB Deadlock detection, InnoDB transaction model @subsubsection An Example of How the Consistent Read Works in InnoDB Suppose you are running on the default @code{REPEATABLE READ} isolation level. When you issue a consistent read, that is, an ordinary @code{SELECT} statement, InnoDB will give your transaction a timepoint according to which your query sees the database. Thus, if transaction B deletes a row and commits after your timepoint was assigned, then you will not see the row deleted. Similarly with inserts and updates. You can advance your timepoint by committing your transaction and then doing another @code{SELECT}. This is called multi-versioned concurrency control. @example User A User B SET AUTOCOMMIT=0; SET AUTOCOMMIT=0; time | SELECT * FROM t; | empty set | INSERT INTO t VALUES (1, 2); | v SELECT * FROM t; empty set COMMIT; SELECT * FROM t; empty set; COMMIT; SELECT * FROM t; --------------------- | 1 | 2 | --------------------- @end example Thus user A sees the row inserted by B only when B has committed the insert, and A has committed his own transaction so that the timepoint is advanced past the commit of B. If you want to see the ``freshest'' state of the database, you should use a locking read: @example SELECT * FROM t LOCK IN SHARE MODE; @end example @node Innodb tuning, Innodb Monitor, Innodb deadlocks, InnoDB transaction model @subsubsection パフォーマンス・チューニング Tips @strong{1.} もし Unix @file{top} や Windows @file{Task Manager} が CPU 使用率を 70% 未満に 表示している場合、おそらく、disk アクセスに処理が取られています。 とても多くのトランザクションのコミットを作成しているか、 バッファプールが小さいのでしょう。 バッファプールを大きくすれば良くなりますが、しかし、バッファプールは 物理メモリの 80% より大きくしないように。 @strong{2.} Wrap several modifications into one transaction. InnoDB must flush the log to disk at each transaction commit, if that transaction made modifications to the database. Since the rotation speed of a disk is typically at most 167 revolutions/second, that constrains the number of commits to the same 167/second if the disk does not fool the operating system. @strong{3.} If you can afford the loss of some latest committed transactions, you can set the @file{my.cnf} parameter @code{innodb_flush_log_at_trx_commit} to zero. InnoDB tries to flush the log anyway once in a second, though the flush is not guaranteed. @strong{4.} Make your log files big, even as big as the buffer pool. When InnoDB has written the log files full, it has to write the modified contents of the buffer pool to disk in a checkpoint. Small log files will cause many unnecessary disk writes. The drawback in big log files is that recovery time will be longer. @strong{5.} Also the log buffer should be quite big, say 8 MB. @strong{6.} (Relevant from 3.23.39 up.) Linux や　Unix のいくつかのバージョンでは、disk のファイルのフラッシュに Unix @code{fdatasync} や それに似た方法を使用しますが、 これは驚くほど遅いです。 InnoDB のデフォルトの方法は、@code{fdatasync} 関数を使用します。 もしデータベースの書き込みのパフォーマンスに満足しない場合には、 @file{my.cnf} ファイルで @code{innodb_flush_method} を @code{O_DSYNC} に セットしてもかまいません。しかし @code{O_DSYNC} はほとんどのシステムでは 遅いようです。 @strong{7.} InnoDB にデータを流し込む場合には、 MySQL の設定が @code{autocommit=1} になっていないようにします。 それぞれの全ての insert が log をディスクにフラッシュすることを要求するからです。 取り込む SQL の最初に @example SET AUTOCOMMIT=0; @end example を追加し、最後に @example COMMIT; @end example を書きます。 もし @file{mysqldump} を @code{--opt} オプションで使用しているなら、 上記のように @code{SET AUTOCOMMIT=0; ... COMMIT;} でダンプファイルを囲まないでも、 早く InnoDB テーブルにダンプを取り込むことが可能です。 @strong{8.} 大量のinsertの大きなロールバックに気をつけなさい； InnoDB は insert の時には、disk I/O を少なくするために insert buffer を 使用します。しかし、ロールバックには同じような機構は使用されません。 ロールバック時のディスク・バウンドは、対応するinsertに比べて 30倍の 時間がかかります。 データベースのプロセスを kill することは、何の解決にもなりません。 なぜなら、データベースがスタートアップした時、 再びロールバックが開始されるからです。 制御しきれないロールバックから免れる方法は、 バッファプールを増やすか(こうすればロールバックは CPU-bound でおさまり、速く終わります)、 InnoDB 全体を消し去ってしまうかしかありません。 @strong{9.} Beware also of other big disk-bound operations. Use @code{DROP TABLE} or @code{TRUNCATE} (from MySQL-4.0 up) to empty a table, not @code{DELETE FROM yourtable}. @strong{10.} もしたくさんのレコードをインサートする必要があるならば、 サーバーとクライアントのコミュニケーションのオーバーヘッドを軽減するために、 マルチライン @code{INSERT} を使用します： @example INSERT INTO yourtable VALUES (1, 2), (5, 5); @end example この方法は InnoDB だけではなく、他のテーブル型にインサートする時も使用できます。 @node Innodb Monitor, , Innodb tuning, InnoDB transaction model @subsubsection InnoDB モニタ バージョン 3.23.41 から、InnoDB は InnoDB Monitor を含むようになりました。 これは InnoDB 内部の状態を表示するものです。 このスイッチを on にすると、MySQL サーバは 15 秒毎に標準出力にデータを出力するようになります。 (note: the MySQL client will not print anything) このデータはパフォーマンス・チューニングに便利です。 On Windows you must start @code{mysqld-max} from a MS-DOS prompt with the @code{--standalone --console} options to direct the output to the MS-DOS prompt window. There is a separate @code{innodb_lock_monitor} which prints the same information as @code{innodb_monitor} plus information on locks set by each transaction. The printed information includes data on: @itemize @bullet @item table and record locks held by each active transaction, @item lock waits of a transactions, @item semaphore waits of threads, @item pending file I/O requests, @item buffer pool statistics, and @item purge and insert buffer merge activity of the main thread of InnoDB. @end itemize InnoDB モニタは、以下の SQL コマンドでスタートできます： @example CREATE TABLE innodb_monitor(a int) type = innodb; @end example 停止は： @example DROP TABLE innodb_monitor; @end example @code{CREATE TABLE} 文は、MySQL SQL パーサーを通して InnoDB エンジンにアクセスするためだけに使用されているにすぎません： 作成されたテーブルは InnoDB モニタとは関係しません。 もし、モニタ実行中にデータベースを停止し、そのあと、 モニタを再び起動したいなら、 あなたはモニタを起動するための新しい @code{CREATE TABLE} 文を 実行する前に、前に作ったテーブルを破棄しなくてはなりません。 この構文は将来のリリースで変わるかもしれません。 InnoDB モニタ の出力サンプル: @example ================================ 010809 18:45:06 INNODB MONITOR OUTPUT ================================ -------------------------- LOCKS HELD BY TRANSACTIONS -------------------------- LOCK INFO: Number of locks in the record hash table 1294 LOCKS FOR TRANSACTION ID 0 579342744 TABLE LOCK table test/mytable trx id 0 582333343 lock_mode IX RECORD LOCKS space id 0 page no 12758 n bits 104 table test/mytable index PRIMARY trx id 0 582333343 lock_mode X Record lock, heap no 2 PHYSICAL RECORD: n_fields 74; 1-byte offs FALSE; info bits 0 0: len 4; hex 0001a801; asc ;; 1: len 6; hex 000022b5b39f; asc ";; 2: len 7; hex 000002001e03ec; asc ;; 3: len 4; hex 00000001; ... ----------------------------------------------- CURRENT SEMAPHORES RESERVED AND SEMAPHORE WAITS ----------------------------------------------- SYNC INFO: Sorry, cannot give mutex list info in non-debug version! Sorry, cannot give rw-lock list info in non-debug version! ----------------------------------------------------- SYNC ARRAY INFO: reservation count 6041054, signal count 2913432 4a239430 waited for by thread 49627477 op. S-LOCK file NOT KNOWN line 0 Mut ex 0 sp 5530989 r 62038708 sys 2155035; rws 0 8257574 8025336; rwx 0 1121090 1848344 ----------------------------------------------------- CURRENT PENDING FILE I/O'S -------------------------- Pending normal aio reads: Reserved slot, messages 40157658 4a4a40b8 Reserved slot, messages 40157658 4a477e28 ... Reserved slot, messages 40157658 4a4424a8 Reserved slot, messages 40157658 4a39ea38 Total of 36 reserved aio slots Pending aio writes: Total of 0 reserved aio slots Pending insert buffer aio reads: Total of 0 reserved aio slots Pending log writes or reads: Reserved slot, messages 40158c98 40157f98 Total of 1 reserved aio slots Pending synchronous reads or writes: Total of 0 reserved aio slots ----------- BUFFER POOL ----------- LRU list length 8034 Free list length 0 Flush list length 999 Buffer pool size in pages 8192 Pending reads 39 Pending writes: LRU 0, flush list 0, single page 0 Pages read 31383918, created 51310, written 2985115 ---------------------------- END OF INNODB MONITOR OUTPUT ============================ 010809 18:45:22 InnoDB starts purge 010809 18:45:22 InnoDB purged 0 pages @end example 出力に関するいくつかの注釈: @itemize @bullet @item もし LOCKS HELD BY TRANSACTIONS セクションにロック待ちが レポートされているなら、あなたのアプリケーションがロックの競合を 起こしています。 出力はトランザクションのデッドロックの理由をたどるための 手助けになります。 @item SYNC INFO セクションは予約されたセマフォを報告します。 ただし、もし @file{univ.i} ファイルの @code{UNIV_SYNC_DEBUG} を有効にして、InnoDB をコンパイルしているならば。 @item Section SYNC ARRAY INFO reports threads waiting for a semaphore and statistics on how many times threads have needed a spin or a wait on a mutex or a rw-lock semaphore. A big number of threads waiting for semaphores may be a result of disk I/O, or contention problems inside InnoDB. Contention can be due to heavy parallelism of queries, or problems in operating system thread scheduling. @item CURRENT PENDING FILE I/O'S セクションは、 延期された ファイル I/O リクエストの一覧をだします。 A large number of these indicates that the workload is disk I/O -bound. @item BUFFER POOL セクションは、ページの読み込みと書き出しの統計情報を 与えます。 You can calculate from these numbers how many datafile I/Os your queries are currently doing. @end itemize @node Implementation, Table and index, InnoDB transaction model, InnoDB @subsection Implementation of Multi-versioning InnoDB は multiversioned database なので、テーブル空間中のレコードの 古いバージョン情報が保持されなくてはなりません。 This information is stored in a data structure we call a rollback segment after an analogous data structure in Oracle. InnoDB は内部では、データベースに保存されているそれぞれのレコードに対して 2 つのフィールドを付加しています。 A 6-byte field tells the transaction identifier for the last transaction which inserted or updated the row. Also a deletion is internally treated as an update where a special bit in the row is set to mark it as deleted. それぞれのレコードには、roll pointer と呼ばれる 7-byte のフィールドも含みます。 The roll pointer points to an undo log record written to the rollback segment. If the row was updated, then the undo log record contains the information necessary to rebuild the content of the row before it was updated. InnoDB uses the information in the rollback segment to perform the undo operations needed in a transaction rollback. It also uses the information to build earlier versions of a row for a consistent read. ロールバック セグメント の中の Undo log は、 insert と update の undo log に分けれれます。 Insert undo log は、トランザクションのロールバックの時にだけ必要とされ、 その トランザクション が コミット するやいなやすぐに破棄されます。 Update undo logs are used also in consistent reads, and they can be discarded only after there is no transaction present for which InnoDB has assigned a snapshot that in a consistent read could need the information in the update undo log to build an earlier version of a database row. You must remember to commit your transactions regularly, also those transactions which only issue consistent reads. Otherwise InnoDB cannot discard data from the update undo logs, and the rollback segment may grow too big, filling up your tablespace. The physical size of an undo log record in the rollback segment is typically smaller than the corresponding inserted or updated row. You can use this information to calculate the space need for your rollback segment. In our multi-versioning scheme a row is not physically removed from the database immediately when you delete it with an SQL statement. Only when InnoDB can discard the update undo log record written for the deletion, it can also physically remove the corresponding row and its index records from the database. This removal operation is called a purge, and it is quite fast, usually taking the same order of time as the SQL statement which did the deletion. @node Table and index, File space management, Implementation, InnoDB @subsection テーブルとインデックスの構造 MySQL は、テーブルの data dictionary 情報を、 データベース ディレクトリ内の、 @file{.frm} ファイルに保存します。 しかし、InnoDB タイプの全てのテーブルは、 InnoDB の内部のデータ・ディクショナリを (InnoDBの)テーブル空間に持っています。 MySQL がテーブルやデータベースを破棄する時は、 @file{.frm} ファイル と それに対応する InnoDB のデータ・ディクショナリ 内のエントリが消去されます。 これは、@file{.frm} ファイルを移動するだけでは InnoDB テーブルを違うデータベースに移動することができない理由であり、 また、MySQL 3.23.43 以下のバージョンで、InnoDB 型のテーブルでは @code{DROP DATABASE} が動作しなかった理由でもあります。 Every InnoDB table has a special index called the clustered index where the data of the rows is stored. If you define a @code{PRIMARY KEY} on your table, then the index of the primary key will be the clustered index. もしテーブルにプライマリ・キーを定義しなかった場合には、 InnoDB は内部ではクラスタド・インデックス(clustered index)を作成します。 そこでは、InnoDB がそのテーブルのレコードに割り当てた row id をもとに レコードが整理されます。 row id は 6-byte のフィールドで、新しいレコードが挿入されると単純に 数が増加していきます。 ということで、row id のよって整理されているレコードは、 物理的にインサートされた順になっています。 Accessing a row through the clustered index is fast, because the row data will be on the same page where the index search leads us. In many databases the data is traditionally stored on a different page from the index record. If a table is large, the clustered index architecture often saves a disk I/O when compared to the traditional solution. The records in non-clustered indexes (we also call them secondary indexes), in InnoDB contain the primary key value for the row. InnoDB uses this primary key value to search for the row from the clustered index. Note that if the primary key is long, the secondary indexes will use more space. @menu * InnoDB physical structure:: * InnoDB Insert buffering:: * InnoDB Adaptive hash:: * InnoDB Physical record:: @end menu @node InnoDB physical structure, InnoDB Insert buffering, Table and index, Table and index @subsubsection Physical Structure of an Index InnoDB の全てのインデックスは B-Tree で、インデックスのレコードは、 ツリーの リーフ ページ (原文 leaf page. ブロックと言い換える or not?) に保存されます。 インデックス ページの デフォルトの大きさは 16kB です。 新しいレコードがインサートされた時、InnoDB はページの 1/16 を、 将来のインデックスレコードの insert や update に備えて free に しようとします。 If index records are inserted in a sequential (ascending or descending) order, the resulting index pages will be about 15/16 full. If records are inserted in a random order, then the pages will be 1/2 - 15/16 full. If the fillfactor of an index page drops below 1/2, InnoDB will try to contract the index tree to free the page. @node InnoDB Insert buffering, InnoDB Adaptive hash, InnoDB physical structure, Table and index @subsubsection Insert Buffering プライマリ・キーが一意で、新しいレコードがそのプライマリー・キーの 並びの順番で insert されるというのは、 データベースのアプリケーションではよくある事です。 この場合は、clustered index に対するインサートはディスクからの ランダム リードを要求しません。 これに対して、secondary indexes は通常 非ユニーク で、 secondary indexes に対するインサートされる順番はばらばらです。 This would cause a lot of random disk I/O's without a special mechanism used in InnoDB. If an index record should be inserted to a non-unique secondary index, InnoDB checks if the secondary index page is already in the buffer pool. If that is the case, InnoDB will do the insertion directly to the index page. But, if the index page is not found from the buffer pool, InnoDB inserts the record to a special insert buffer structure. The insert buffer is kept so small that it entirely fits in the buffer pool, and insertions can be made to it very fast. The insert buffer is periodically merged to the secondary index trees in the database. Often we can merge several insertions on the same page in of the index tree, and hence save disk I/Os. It has been measured that the insert buffer can speed up insertions to a table up to 15 times. @node InnoDB Adaptive hash, InnoDB Physical record, InnoDB Insert buffering, Table and index @subsubsection Adaptive Hash Indexes If a database fits almost entirely in main memory, then the fastest way to perform queries on it is to use hash indexes. InnoDB has an automatic mechanism which monitors index searches made to the indexes defined for a table, and if InnoDB notices that queries could benefit from building of a hash index, such an index is automatically built. But note that the hash index is always built based on an existing B-tree index on the table. InnoDB can build a hash index on a prefix of any length of the key defined for the B-tree, depending on what search pattern InnoDB observes on the B-tree index. A hash index can be partial: it is not required that the whole B-tree index is cached in the buffer pool. InnoDB will build hash indexes on demand to those pages of the index which are often accessed. In a sense, through the adaptive hash index mechanism InnoDB adapts itself to ample main memory, coming closer to the architecture of main memory databases. @node InnoDB Physical record, , InnoDB Adaptive hash, Table and index @subsubsection Physical Record Structure @itemize @bullet @item InnoDB 中のそれぞれのインデックス レコードは、6 bytes のヘッダを含みます。 The header is used to link consecutive records together, and also in the row level locking. @item Records in the clustered index contain fields for all user-defined columns. 1つの 6-byte フィールドが transaction id のために存在し、 1つの 7-byte フィールドが roll pointer のために存在します。 @item If the user has not defined a primary key for a table, then each clustered index record contains also a 6-byte row id field. @item Each secondary index record contains also all the fields defined for the clustered index key. @item A record contains also a pointer to each field of the record. If the total length of the fields in a record is < 128 bytes, then the pointer is 1 byte, else 2 bytes. @end itemize @subsubsection How an Auto-increment Column Works in InnoDB データベースがスタートアップした後、ユーザーが auto-increment が定義されているテーブル @code{T} に対して 初めて、insert を行なう時、 もしユーザーが auto-increment のフィールドに明示的に値を与えなければ、 InnoDB は @code{SELECT MAX(auto-inc-column) FROM T} を実行し、そして その結果得た値に１を加えた数を、 そのフィールドと テーブルの auto-increment counter に与えます。 これをもって、テーブル @code{T} の auto-increment counter が 初期化されたと言います。 InnoDB follows the same procedure in initializing the auto-increment counter for a freshly created table. もしユーザーが auto-increment のフィールドに 0 をインサートしたなら、 InnoDB はそれを、値が与えられなかったものとして扱うことに 注意してください。 auto-increment counter が初期化された後、 もしユーザーがauto-increment のフィールドに明示的に値を与えてレコードを insert すれば、その値が現在の auto-increment counter より大きければ auto-increment counter はその値にセットされます。 もしユーザーが値を明示して与えなければ、InnODB は auto-increment counter を １つ増やし、そしてその値をフィールドの値としてセットします。 The auto-increment mechanism, when assigning values from the counter, bypasses locking and transaction handling. Therefore you may also get gaps in the number sequence if you roll back transactions which have got numbers from the counter. The behaviour of auto-increment is not defined if a user gives a negative value to the column or if the value becomes bigger than the maximum integer that can be stored in the specified integer type. @node File space management, Error handling, Table and index, InnoDB @subsection File Space Management and Disk I/O @menu * InnoDB Disk I/O:: Disk I/O * InnoDB File space:: File Space Management * InnoDB File Defragmenting:: Defragmenting a Table @end menu @node InnoDB Disk I/O, InnoDB File space, File space management, File space management @subsubsection Disk I/O ディスク I/O では、InnoDB は非同期 I/O を使用します. On Windows NT it uses the native asynchronous I/O provided by the operating system. On Unix, InnoDB uses simulated asynchronous I/O built into InnoDB: InnoDB creates a number of I/O threads to take care of I/O operations, such as read-ahead. In a future version we will add support for simulated aio on Windows NT and native aio on those versions of Unix which have one. On Windows NT InnoDB uses non-buffered I/O. That means that the disk pages InnoDB reads or writes are not buffered in the operating system file cache. This saves some memory bandwidth. Starting from 3.23.41 InnoDB uses a novel file flush technique called doublewrite. It adds safety to crash recovery after an operating system crash or a power outage, and improves performance on most Unix flavors by reducing the need for fsync operations. Doublewrite means that InnoDB before writing pages to a datafile first writes them to a contiguous tablespace area called the doublewrite buffer. Only after the write and the flush to the doublewrite buffer has completed, InnoDB writes the pages to their proper positions in the datafile. If the operating system crashes in the middle of a page write, InnoDB will in recovery find a good copy of the page from the doublewrite buffer. 3.23.41 からは、データファイルにロー・ディスク(raw disk)パーティションが 使用できますが、これはまだテスト段階です。 新しいデータファイルを作成するとき、 @code{innodb_data_file_path} に指定するデータファイルのサイズのすぐ後に、 @code{newraw} キーワードを付加すれば実現されます。 パーティションのサイズは、指定したサイズ以上(>=) でなければなりません。 InnoDB の 1M は、1024 x 1024 bytes を示します。 現実のディスク製品の表記では、1000 000 bytes を 1MB と表示することに 注意してください。 @example innodb_data_file_path=hdd1:5Gnewraw;hdd2:2Gnewraw @end example 設定を記述してデータベースを再起動した後は、 あなたはキーワードを @code{raw} に@strong{書き換えなければなりません}。 書き換えを忘れると、InnoDB はそのパーティションを新規に上書きしてしまいます！ @example innodb_data_file_path=hdd1:5Graw;hdd2:2Graw @end example By using a raw disk you can on some Unixes perform unbuffered I/O. There are two read-ahead heuristics in InnoDB: sequential read-ahead and random read-ahead. In sequential read-ahead InnoDB notices that the access pattern to a segment in the tablespace is sequential. Then InnoDB will post in advance a batch of reads of database pages to the I/O system. In random read-ahead InnoDB notices that some area in a tablespace seems to be in the process of being fully read into the buffer pool. Then InnoDB posts the remaining reads to the I/O system. @node InnoDB File space, InnoDB File Defragmenting, InnoDB Disk I/O, File space management @subsubsection File Space Management 設定ファイルに記述したデータファイルを InnoDB のテーブル空間を作ります。 データファイルは単純に連結されてテーブル空間になります。 striping は使用されません。 Currently you cannot directly instruct where the space is allocated for your tables, except by using the following fact: from a newly created tablespace InnoDB will allocate space starting from the low end. テーブル空間は、デフォルトサイズが 16kB の データベース ページから成ります。 それらページは 64個までの連続する部分にグループ化されます。 その、テーブル空間内の 'まとまり' は、InnoDB では セグメント と呼ばれます。 The pages are grouped into extents of 64 consecutive pages. The 'files' inside a tablespace are called segments in InnoDB. The name of the rollback segment is somewhat misleading because it actually contains many segments in the tablespace. InnoDB 中のそれぞれのインデックスには、2つのセグメントが割り当てられます； 一つは B-tree の 非リーフ ノードに、もう一つは リーフのノードに。 The idea here is to achieve better sequentiality for the leaf nodes, which contain the data. テーブル空間内であるセグメントが大きくなった場合、 InnoDB は 最初の 32 ページを個々に割り当てます。 そののち、InnoDB は全領域をそのセグメントに割り当はじめます。 InnoDB はデータがより良く連続することを確実にするために、 領域を 4つまで、一度に大きなセグメントに追加することが出来ます。 When a segment grows inside the tablespace, InnoDB allocates the first 32 pages to it individually. After that InnoDB starts to allocate whole extents to the segment. InnoDB can add to a large segment up to 4 extents at a time to ensure good sequentiality of data. テーブル空間内のいくつかのページには、他のページのビットマップが含まれ、 その結果、InnoDB テーブル空間内の数個の領域は、全てをセグメントに 割り当てることができず、個々のページ毎に割り当てられます。 Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an InnoDB tablespace cannot be allocated to segments as a whole, but only as individual pages. テーブル空間の available free space を知るためにあなたが @code{SHOW TABLE STATUS FROM ... LIKE ...} クエリを実行した時、 InnoDB は、 テーブル空間内の、確実に使用できるフリーな領域の合計をレポートします。 InnoDB は、clean-up と他の内部的な使用目的のために、常にいくつかの領域を リザーブします。 これらのリザーブされた領域は free space には含まれません。 When you delete data from a table, InnoDB will contract the corresponding B-tree indexes. It depends on the pattern of deletes if that frees individual pages or extents to the tablespace, so that the freed space is available for other users. Dropping a table or deleting all rows from it is guaranteed to release the space to other users, but remember that deleted rows can be physically removed only in a purge operation after they are no longer needed in transaction rollback or consistent read. @node InnoDB File Defragmenting, , InnoDB File space, File space management @subsubsection テーブルのデフラグメント If there are random insertions or deletions in the indexes of a table, the indexes may become fragmented. By fragmentation we mean that the physical ordering of the index pages on the disk is not close to the alphabetical ordering of the records on the pages, or that there are many unused pages in the 64-page blocks which were allocated to the index. 定期的に @code{mysqldump} を使用してテーブルをテキストファイルにダンプし、 テーブルを削除し、ダンプファイルからテーブルを作り直す事を行なうことで、 インデックスの走査を速くすることが可能です。 デフラグメントを行なう他の方法は、テーブルのタイプを @code{ALTER} で 一度 @code{MyISAM} にし、再び @code{InnoDB} に変更することです。 Note that a @code{MyISAM} table must fit in a single file on your operating system. If the insertions to and index are always ascending and records are deleted only from the end, then the file space management algorithm of InnoDB guarantees that fragmentation in the index will not occur. @node Error handling, InnoDB restrictions, File space management, InnoDB @subsection エラー ハンドリング The error handling in InnoDB is not always the same as specified in the ANSI SQL standards. According to the ANSI standard, any error during an SQL statement should cause the rollback of that statement. InnoDB sometimes rolls back only part of the statement, or the whole transaction. The following list specifies the error handling of InnoDB. @itemize @bullet @item もしテーブルスペース中のファイルの空間を使いきれば、 MySQL @code{'Table is full'} エラーとなり、 InnoDB は SQL 文をロール・バックします。 @item トランザクションのデッドロックやロック待ちのタイムアウトの場合は、 InnoDB はトランザクション全てをロール・バックします。 @item A duplicate key error only rolls back the insert of that particular row, even in a statement like @code{INSERT INTO ... SELECT ...}. This will probably change so that the SQL statement will be rolled back if you have not specified the @code{IGNORE} option in your statement. @item 'row too long' エラーは、その SQL 文をロール・バックします。 @item Other errors are mostly detected by the MySQL layer of code, and they roll back the corresponding SQL statement. @end itemize @node InnoDB restrictions, InnoDB change history, Error handling, InnoDB @subsection InnoDB テーブルの制限 @itemize @bullet @item @strong{Warning}: MySQL システムテーブルを MyISAM から InnoDB テーブルに @strong{変換してはいけません！} これはサポートされていません； もし変換してしまうと、バックアップから前のシステムテーブルを復旧させるか あるいは @code{mysql_install_db} スクリプトを使用して システムテーブルを再構築しない限り、MySQL は起動できません。 @item @code{SHOW TABLE STATUS} は、 InnoDB テーブルに関する統計を正確に返しません (ただしテーブルが使用している物理サイズは正確)。 The row count is only a rough estimate used in SQL optimisation. @item フィールドの先頭部分にユニークなインデックスを作成しようとすると、 エラーになります： @example CREATE TABLE T (A CHAR(20), B INT, UNIQUE (A(5))) TYPE = InnoDB; @end example もし、フィールドの先頭部分に、非ユニークインデックスを作成しようとすると、 InnoDB は そのフィールドの全体にインデックスを張ります。 @item @code{INSERT DELAYED} は InnoDB テーブルではサポートされていません。 @item MySQL @code{LOCK TABLES} オペレーションは、 InnoDB のロー・レベル・ロック (row level lock) を感知しません。 これは、たとえ他のユーザーによるトランザクション(row lovel lock をしている)が あるテーブルに存在していたとしても、 あなたが同じテーブルに対して、テーブル・ロックをかけれるということです。 Thus your operations on the table may have to wait if they collide with these locks of other users. Also a deadlock is possible. However, this does not endanger transaction integrity, because the row level locks set by InnoDB will always take care of the integrity. Also, a table lock prevents other transactions from acquiring more row level locks (in a conflicting lock mode) on the table. @item @code{BLOB} や @code{TEXT} フィールドにインデックスを張ることができません。 @item 1つのテーブルには 1000個 以上のフィールドを持つことができません。 @item @code{DELETE FROM TABLE} does not regenerate the table but instead deletes all rows, one by one, which is not that fast. In future versions of MySQL you can use @code{TRUNCATE} which is fast. @item InnoDB のデフォルトのデータベースのページサイズは 16kB です。 コンパイルし直すことで、これは 8kB から　64kB まで変更可能です。 The maximun row length is slightly less than half of a database page in versions <= 3.23.40 of InnoDB. バージョン 3.23.41 からは、 BLOB と TEXT フィールドは 4GB 未満まで許されます。 1 レコードの最大容量も 4GB 未満までです。 InnoDB does not store fields whose size is <= 128 bytes on separate pages. After InnoDB has modified the row by storing long fields on separate pages, the remaining length of the row must be less than half a database page. The maximun key length is 7000 bytes. @item いくつかのオペレーティングシステムでは、 データファイルは < 2GB となります。 The combined size of log files must be < 4 GB. @item テーブル空間のサイズの最大値は 40億 データベース ページです。 これは 1つのテーブルの最大のサイズでもあります。 テーブル空間の最低限のサイズは 10MB です。 @end itemize @node InnoDB change history, InnoDB contact information, InnoDB restrictions, InnoDB @subsection InnoDB Change History @subsubsection MySQL/InnoDB-4.1.0, April x, 2003 @itemize @bullet @item @item InnoDB now supports up to 64 GB of buffer pool memory in a Windows 32-bit Intel computer. This is possible because InnoDB can use the AWE extension of Windows to address memory over the 4 GB limit of a 32-bit process. A new startup variable innodb_buffer_pool_awe_mem_mb enables AWE and sets the size of the buffer pool in megabytes. @item Reduced the size of buffer headers and the lock table. InnoDB uses 2 % less memory. @end itemize @subsubsection MySQL/InnoDB-3.23.56, March xx, 2003 @itemize @bullet @item Fixed a major bug in InnoDB query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good. @end itemize @subsubsection MySQL/InnoDB-4.0.12, March xx, 2003 @itemize @bullet @item In crash recovery InnoDB now prints the progress in percents of a transaction rollback. @end itemize @subsubsection MySQL/InnoDB-4.0.11, February 25, 2003 @itemize @bullet @item Fixed a bug introduced in 4.0.10: SELECT ... FROM ... ORDER BY ... DESC could hang in an infinite loop. @item An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication. @end itemize @subsubsection MySQL/InnoDB-4.0.10, February 4, 2003 @itemize @bullet @item In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed. @item Increased SHOW INNODB STATUS max printed length to 200 kB. @item Fixed a major bug in InnoDB query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good. @item Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field(). @item Fixed a bug: using InnoDB HANDLER commands on a fresh handle crashed mysqld in ha_innobase::change_active_index(). @item Fixed a bug: if MySQL estimated a query in the middle of a SELECT statement, InnoDB could hang on the adaptive hash index latch in btr0sea.c. @item Fixed a bug: InnoDB could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert. @item Fixed a bug: some file system snapshot tool in Windows 2000 could cause an InnoDB file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes InnoDB now retries the write 100 times at 1 second intervals. @item Fixed a bug: REPLACE INTO t1 SELECT ... did not work if t1 has an auto-inc column. @item An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication. @end itemize @subsubsection MySQL/InnoDB-3.23.55, January 24, 2003 @itemize @bullet @item In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed. @item Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail in log scan. @item Fixed a bug: index cursor restoration could theoretically fail. @item Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads. @item Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field(). @item Fixed a bug: if MySQL estimated a query in the middle of a SELECT statement, InnoDB could hang on the adaptive hash index latch in btr0sea.c. @item Fixed a bug: InnoDB could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert. @item Fixed a bug: some file system snapshot tool in Windows 2000 could cause an InnoDB file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes InnoDB now retries the write 100 times at 1 second intervals. @item An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication. The fix will appear in 4.0.11 and will probably not be backported to 3.23. @item Fixed bug in InnoDB page0cur.c in function page_cur_search_with_match which caused InnoDB to remain on the same page forever. This bug is evident only in tables with more than one page. @end itemize @subsubsection MySQL/InnoDB-4.0.9, January 14, 2003 @itemize @bullet @item Removed the warning message: 'InnoDB: Out of memory in additional memory pool.' @item Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail. @item Fixed a bug: index cursor restoration could theoretically fail. @end itemize @subsubsection MySQL/InnoDB-4.0.8, January 7, 2003 @itemize @bullet @item InnoDB now supports also FOREIGN KEY (...) REFERENCES ...(...) [ON UPDATE CASCADE | ON UPDATE SET NULL | ON UPDATE RESTRICT | ON UPDATE NO ACTION]. @item Tables and indexes now reserve 4 % less space in the tablespace. Also existing tables reserve less space. By upgrading to 4.0.8 you will see more free space in "InnoDB free" in SHOW TABLE STATUS. @item Fixed bugs: updating the PRIMARY KEY of a row would generate a foreign key error on all FOREIGN KEYs which referenced secondary keys of the row to be updated. Also, if a referencing FOREIGN KEY constraint only referenced the first columns in an index, and there were more columns in that index, updating the additional columns generated a foreign key error. @item Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes. @item Fixed a bug: removed superfluous error 149 and 150 printouts from the .err log when a locking SELECT caused a deadlock or a lock wait timeout. @item Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads. @item Fixed a bug: one could not switch a session transaction isolation level back to REPEATABLE READ after setting it to something else. @end itemize @subsubsection MySQL/InnoDB-4.0.7, December 26, 2002 @itemize @bullet @item InnoDB in 4.0.7 is essentially the same as in 4.0.6. @end itemize @subsubsection MySQL/InnoDB-4.0.6, December 19, 2002 @itemize @bullet @item Since innodb_log_arch_dir has no relevance under MySQL, there is no need to specify it any more in my.cnf. @item LOAD DATA INFILE in AUTOCOMMIT=1 mode no longer does implicit commits for each 1 MB of written binlog. @item Fixed a bug introduced in 4.0.4: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump. @item Fixed two bugs introduced in 4.0.4: in AUTO_INCREMENT, REPLACE could cause the counter to be left 1 too low. A deadlock or a lock wait timeout could cause the same problem. @item Fixed a bug: TRUNCATE on a TEMPORARY table crashed InnoDB. @item Fixed a bug introduced in 4.0.5: if binlogging was not switched on, INSERT INTO ... SELECT ... or CREATE TABLE ... SELECT ... could cause InnoDB to hang on a semaphore created in btr0sea.c, line 128. Workaround: switch binlogging on. @item Fixed a bug: in replication issuing SLAVE STOP in the middle of a multi-statement transaction could cause that SLAVE START would only perform a part of the transaction. A similar error could occur if the slave crashed and was restarted. @end itemize @subsubsection MySQL/InnoDB-3.23.54, December 12, 2002 @itemize @bullet @item Fixed a bug: the InnoDB range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch already in the root. This could cause unnecessary table scans in SQL queries. @item Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL. @item Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes. @item Fixed a bug: if a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, InnoDB could erroneously return the NEXT record. @item Fixed a bug introduced in 3.23.53: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump. @item Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes. @end itemize @subsubsection MySQL/InnoDB-4.0.5, November 18, 2002 @itemize @bullet @item InnoDB now supports also transaction isolation levels READ COMMITTED and READ UNCOMMITTED. READ COMMITTED more closely emulates Oracle and makes porting of applications from Oracle to MySQL easier. @item Deadlock resolution is now selective: we try to pick as victims transactions with less modified or inserted rows. @item FOREIGN KEY definitions are now aware of the lower_case_table_names setting in my.cnf. @item SHOW CREATE TABLE does not output the database name to a FOREIGN KEY definition if the referred table is in the same database as the table. @item InnoDB does a consistency check to most index pages before writing them to a data file. @item If you set innodb_force_recovery > 0, InnoDB tries to jump over corrupt index records and pages when doing SELECT * FROM table. This helps in dumping. @item InnoDB now again uses asynchronous unbuffered i/o in Windows 2000 and XP; only unbuffered simulated async i/o in NT, 95/98/ME. @item Fixed a bug: the InnoDB range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch already in the root. This could cause unnecessary table scans in SQL queries. The fix will also be backported to 3.23.54. @item Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: InnoDB startup could take very long or even crash on some Win 95/98/ME computers. @item Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks. @item Fixed a bug: if SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, InnoDB would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621. @item Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes. @item Fixed a potential bug in 4.0.4: InnoDB now does ORDER BY ... DESC like MyISAM. @item Fixed a bug: DROP TABLE could cause crash or a hang if there was a rollback concurrently running on the table. The fix will only be backported to 3.23 if this appears a real problem for users. @item Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL. @item Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes. @item Fixed a bug: if a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, InnoDB could return the NEXT record. @item Outstanding bugs: in 4.0.4 two bugs were introduced to AUTO_INCREMENT. REPLACE can cause the counter to be left 1 too low. A deadlock or a lock wait timeout can cause the same problem. These will be fixed in 4.0.6. @end itemize @subsubsection MySQL/InnoDB-3.23.53, October 9, 2002 @itemize @bullet @item We again use unbuffered disk i/o to data files in Windows. Win XP and Win 2000 read performance seems to be very poor with normal i/o. @item Tuned range estimator so that index range scans are preferred over full index scans. @item Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery. @item Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: InnoDB startup could take very long or even crash on some Win 95/98/ME computers. @item Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge. @item Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310. @item Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks. @item Fixed a bug: if you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innobase.cc. @item Fixed a bug: if SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, InnoDB would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621. @item Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes. @end itemize @subsubsection MySQL/InnoDB-4.0.4, October 2, 2002 @itemize @bullet @item We again use unbuffered disk i/o in Windows. Win XP and Win 2000 read performance seems to be very poor with normal i/o. @item Increased the max key length of InnoDB tables from 500 to 1024 bytes. @item Increased the table comment field in SHOW TABLE STATUS so that up to 16000 characters of foreign key definitions can be printed there. @item The auto-increment counter is no longer incremented if an insert of a row immediately fails in an error. @item Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery. @item Fixed a bug: Using ORDER BY primarykey DESC in 4.0.3 causes an assertion failure in btr0pcur.c, line 203. @item Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge. @item Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310. @item Fixed a bug: if the MySQL query cache was used, it did not get invalidated by a modification done by ON DELETE CASCADE or ...SET NULL. @item Fixed a bug: if you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innodb.cc. @item Fixed a bug: if you set innodb_flush_log_at_trx_commit to 1, SHOW VARIABLES would show its value as 16 million. @end itemize @subsubsection MySQL/InnoDB-4.0.3, August 28, 2002 @itemize @bullet @item Removed unnecessary deadlocks when inserts have to wait for a locking read, update, or delete to release its next-key lock. @item The MySQL @code{HANDLER} SQL commands now work also for @code{InnoDB} type tables. @code{InnoDB} does the @code{HANDLER} reads always as consistent reads. @code{HANDLER} is a direct access path to read individual indexes of tables. In some cases @code{HANDLER} can be used as a substitute of server-side cursors. @item Fixed a bug in 4.0.2: even a simple insert could crash the AIX version. @item Fixed a bug: if you used in a table name characters whose code is > 127, in DROP TABLE InnoDB could assert on line 155 of pars0sym.c. @item Compilation from source now provides a working version both on HP-UX-11 and HP-UX-10.20. The source of 4.0.2 worked only on 11, and the source of 3.23.52 only on 10.20. @item Fixed a bug: if compiled on 64-bit Solaris, InnoDB produced a bus error at startup. @end itemize @subsubsection MySQL/InnoDB-3.23.52, August 16, 2002 @itemize @bullet @item The feature set of 3.23 will be frozen from this version on. New features will go the 4.0 branch, and only bug fixes will be made to the 3.23 branch. @item Many CPU-bound join queries now run faster. On Windows also many other CPU-bound queries run faster. @item A new SQL command SHOW INNODB STATUS returns the output of the InnoDB Monitor to the client. The InnoDB Monitor now prints detailed info on the latest detected deadlock. @item InnoDB made the SQL query optimizer to avoid too much index-only range scans and choose full table scans instead. This is now fixed. @item "BEGIN" and "COMMIT" are now added in the binlog around transactions. The MySQL replication now respects transaction borders: a user will no longer see half transactions in replication slaves. @item A replication slave now prints in crash recovery the last master binlog position it was able to recover to. @item A new setting innodb_flush_log_at_trx_commit=2 makes InnoDB to write the log to the operating system file cache at each commit. This is almost as fast as the setting innodb_flush_log_at_trx_commit=0, and the setting 2 also has the nice feature that in a crash where the operating system does not crash, no committed transaction is lost. If the operating system crashes or there is a power outage, then the setting 2 is no safer than the setting 0. @item Added checksum fields to log blocks. @item SET FOREIGN_KEY_CHECKS=0 helps in importing tables in an arbitrary order which does not respect the foreign key rules. @item SET UNIQUE_CHECKS=0 speeds up table imports into InnoDB if you have UNIQUE constraints on secondary indexes. @item SHOW TABLE STATUS now lists also possible ON DELETE CASCADE or ON DELETE SET NULL in the comment field of the table. @item When CHECK TABLE is run on any InnoDB type table, it now checks also the adaptive hash index for all tables. @item If you defined ON DELETE CASCADE or SET NULL and updated the referenced key in the parent row, InnoDB deleted or updated the child row. This is now changed to conform to SQL-92: you get the error 'Cannot delete parent row'. @item Improved the auto-increment algorithm: now the first insert or SHOW TABLE STATUS initializes the auto-inc counter for the table. This removes almost all surprising deadlocks caused by SHOW TABLE STATUS. @item Aligned some buffers used in reading and writing to data files. This allows using unbuffered raw devices as data files in Linux. @item Fixed a bug: If you updated the primary key of a table so that only the case of characters changed, that could cause assertion failures, mostly in page0page.ic line 515. @item Fixed a bug: If you delete or update a row referenced in a foreign key constraint and the foreign key check has to wait for a lock, then the check may report an erroneous result. This affects also the ON DELETE... operation. @item Fixed a bug: A deadlock or a lock wait timeout error in InnoDB causes InnoDB to roll back the whole transaction, but MySQL could still write the earlier SQL statements to the binlog, even though InnoDB rolled them back. This could, for example, cause replicated databases to get out-of-sync. @item Fixed a bug: If the database happened to crash in the middle of a commit, then the recovery might leak tablespace pages. @item Fixed a bug: If you specified a non-latin1 character set in my.cnf, then, in contrary to what is stated in the manual, in a foreign key constraint a string type column had to have the same length specification in the referencing table and the referenced table. @item Fixed a bug: DROP TABLE or DROP DATABASE could fail if there simultaneously was a CREATE TABLE running. @item Fixed a bug: If you configured the buffer pool bigger than 2 GB in a 32-bit computer, InnoDB would assert in buf0buf.ic line 214. @item Fixed a bug: on 64-bit computers updating rows which contained the SQL NULL in some column could cause the undo log and the ordinary log to become corrupt. @item Fixed a bug: innodb_log_monitor caused a hang if it suppressed lock prints for a page. @item Fixed a bug: in the HP-UX-10.20 version mutexes would leak and cause race conditions and crashes in any part of InnoDB code. @item Fixed a bug: if you ran in the AUTOCOMMIT mode, executed a SELECT, and immediately after that a RENAME TABLE, then RENAME would fail and MySQL would complain about error 1192. @item Fixed a bug: if compiled on 64-bit Solaris, InnoDB produced a bus error at startup. @end itemize @subsubsection MySQL/InnoDB-4.0.2, July 10, 2002 @itemize @bullet @item InnoDB is essentially the same as InnoDB-3.23.51. @item If no innodb_data_file_path is specified, InnoDB at the database creation now creates a 10 MB auto-extending data file ibdata1 to the datadir of MySQL. In 4.0.1 the file was 64 MB and not auto-extending. @end itemize @subsubsection MySQL/InnoDB-3.23.51, June 12, 2002 @itemize @bullet @item Fixed a bug: a join could result in a seg fault in copying of a BLOB or TEXT column if some of the BLOB or TEXT columns in the table contained SQL NULL values. @item Fixed a bug: if you added self-referential foreign key constraints with ON DELETE CASCADE to tables and a row deletion caused InnoDB to attempt the deletion of the same row twice because of a cascading delete, then you got an assertion failure. @item Fixed a bug: if you use MySQL 'user level locks' and close a connection, then InnoDB may assert in ha_innobase.cc, line 302. @end itemize @subsubsection MySQL/InnoDB-3.23.50, April 23, 2002 @itemize @bullet @item InnoDB now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup. @item Made several changes to facilitate the use of the InnoDB Hot Backup tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks. @item If you want to run the InnoDB Hot Backup tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35. @item The log scan phase in crash recovery will now run much faster. @item Starting from this server version, the hot backup tool truncates unused ends in the backup InnoDB data files. @item To allow the hot backup tool to work, on Windows we no longer use unbuffered i/o or native async i/o; instead we use the same simulated async i/o as on Unix. @item You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys. @item FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX. @item We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example. @item SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions. @item You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...). @item FOREIGN KEY definitions now allow backquotes around table and column names. @item MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then InnoDB obeys its default locking strategy which is REPEATABLE READ. @item SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has already been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS. @item Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150. @end itemize @subsubsection MySQL/InnoDB-3.23.49, February 17, 2002 @itemize @bullet @item Fixed a bug: if you called DROP DATABASE for a database on which there simultaneously were running queries, the MySQL server could crash or hang. Crashes fixed, but a full fix has to wait some changes in the MySQL layer of code. @item Fixed a bug: on Windows one had to put the database name in lower case for DROP DATABASE to work. Fixed in 3.23.49: case no longer matters on Windows. On Unix the database name remains case-sensitive. @item Fixed a bug: if one defined a non-latin1 character set as the default character set, then definition of foreign key constraints could fail in an assertion failure in dict0crea.c, reporting an internal error 17. @end itemize @subsubsection MySQL/InnoDB-3.23.48, February 9, 2002 @itemize @bullet @item Tuned the SQL optimizer to favor more often index searches over table scans. @item Fixed a performance problem when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries will now also generally run faster on all platforms. @item If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog file name and the position in that file (= byte offset) InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication. @item Added better error messages to help in installation problems. @item One can now recover also MySQL temporary tables which have become orphaned inside the InnoDB tablespace. @item InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns. @item Fixed a bug: calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE. @item Fixed a bug: if on Unix you did an ALTER TABLE to an InnoDB table and simultaneously did queries to it, mysqld could crash with an assertion failure in row0row.c, line 474. @item Fixed a bug: if inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c. @item In 3.23.47 we allowed several NULLS in a UNIQUE secondary index. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation. @item Fixed a bug: on Sparc and other high-endian processors SHOW VARIABLES showed innodb_flush_log_at_trx_commit and other boolean-valued startup parameters always OFF even if they were switched on. @item Fixed a bug: if you ran mysqld-max-nt as a service on Windows NT/2000, the service shutdown did not always wait long enough for the InnoDB shutdown to finish. @end itemize @subsubsection MySQL/InnoDB-3.23.47, December 28, 2001 @itemize @bullet @item Recovery happens now faster, especially in a lightly loaded system, because background checkpointing has been made more frequent. @item InnoDB allows now several similar key values in a UNIQUE secondary index if those values contain SQL NULLs. Thus the convention is now the same as in MyISAM tables. @item InnoDB gives a better row count estimate for a table which contains BLOBs. @item In a FOREIGN KEY constraint InnoDB is now case-insensitive to column names, and in Windows also to table names. @item InnoDB allows a FOREIGN KEY column of CHAR type to refer to a column of VARCHAR type, and vice versa. MySQL silently changes the type of some columns between CHAR and VARCHAR, and these silent changes do not hinder FOREIGN KEY declaration any more. @item Recovery has been made more resilient to corruption of log files. @item Unnecessary statistics calculation has been removed from queries which generate a temporary table. Some ORDER BY and DISTINCT queries will now run much faster. @item MySQL now knows that the table scan of an InnoDB table is done through the primary key. This will save a sort in some ORDER BY queries. @item The maximum key length of InnoDB tables is again restricted to 500 bytes. The MySQL interpreter is not able to handle longer keys. @item The default value of innodb_lock_wait_timeout was changed from infinite to 50 seconds, the default value of innodb_file_io_threads from 9 to 4. @end itemize @subsubsection MySQL/InnoDB-4.0.1, December 23, 2001 @itemize @bullet @item InnoDB is the same as in 3.23.47. @item In 4.0.0 the MySQL interpreter did not know the syntax LOCK IN SHARE MODE. This has been fixed. @item In 4.0.0 multi-table delete did not work for transactional tables. This has been fixed. @end itemize @subsubsection MySQL/InnoDB-3.23.46, November 30, 2001 @itemize @bullet @item This is the same as 3.23.45. @end itemize @subsubsection MySQL/InnoDB-3.23.45, November 23, 2001 @itemize @bullet @item This is a bugfix release. @item In versions 3.23.42-.44 when creating a table on Windows you have to use lower case letters in the database name to be able to access the table. Fixed in 3.23.45. @item InnoDB now flushes stdout and stderr every 10 seconds: if these are redirected to files, the file contents can be better viewed with an editor. @item Fixed an assertion failure in .44, in trx0trx.c, line 178 when you drop a table which has the .frm file but does not exist inside InnoDB. @item Fixed a bug in the insert buffer. The insert buffer tree could get into an inconsistent state, causing a crash, and also crashing the recovery. This bug could appear especially in large table imports or alterations. @item Fixed a bug in recovery: InnoDB could go into an infinite loop constantly printing a warning message that it cannot find free blocks from the buffer pool. @item Fixed a bug: when you created a temporary table of the InnoDB type, and then used ALTER TABLE to it, the MySQL server could crash. @item Prevented creation of MySQL system tables 'mysql.user', 'mysql.host', or 'mysql.db', in the InnoDB type. @item Fixed a bug which can cause an assertion failure in 3.23.44 in srv0srv.c, line 1728. @end itemize @subsubsection MySQL/InnoDB-3.23.44, November 2, 2001 @itemize @bullet @item You can define foreign key constraints on InnoDB tables. An example: FOREIGN KEY (col1) REFERENCES table2(col2). @item You can create > 4 GB data files in those file systems that allow it. @item Improved InnoDB monitors, including a new innodb_table_monitor which allows you to print the contents of the InnoDB internal data dictionary. @item DROP DATABASE will now work also for InnoDB tables. @item Accent characters in the default character set latin1 will be ordered according to the MySQL ordering.
    NOTE: if you are using latin1 and have inserted characters whose code is > 127 to an indexed CHAR column, you should run CHECK TABLE on your table when you upgrade to 3.23.43, and drop and reimport the table if CHECK TABLE reports an error! @item InnoDB will calculate better table cardinality estimates. @item Change in deadlock resolution: in .43 a deadlock rolls back only the SQL statement, in .44 it will roll back the whole transaction. @item Deadlock, lock wait timeout, and foreign key constraint violations (no parent row, child rows exist) now return native MySQL error codes 1213, 1205, 1216, 1217, respectively. @item A new my.cnf parameter innodb_thread_concurrency helps in performance tuning in high concurrency environments. @item A new my.cnf option innodb_force_recovery will help you in dumping tables from a corrupted database. @item A new my.cnf option innodb_fast_shutdown will speed up shutdown. Normally InnoDB does a full purge and an insert buffer merge at shutdown. @item Raised maximum key length to 7000 bytes from a previous limit of 500 bytes. @item Fixed a bug in replication of auto-inc columns with multiline inserts. @item Fixed a bug when the case of letters changes in an update of an indexed secondary column. @item Fixed a hang when there are > 24 data files. @item Fixed a crash when MAX(col) is selected from an empty table, and col is a not the first column in a multi-column index. @item Fixed a bug in purge which could cause crashes. @end itemize @subsubsection MySQL/InnoDB-3.23.43, October 4, 2001 @itemize @bullet @item This is essentially the same as InnoDB-3.23.42. @end itemize @subsubsection MySQL/InnoDB-3.23.42, September 9, 2001 @itemize @bullet @item Fixed a bug which corrupted the table if the primary key of a > 8000-byte row was updated. @item There are now 3 types of InnoDB Monitors: innodb_monitor, innodb_lock_monitor, and innodb_tablespace_monitor. innodb_monitor now prints also buffer pool hit rate and the total number of rows inserted, updated, deleted, read. @item Fixed a bug in RENAME TABLE. @item Fixed a bug in replication with an auto-increment column. @end itemize @subsubsection MySQL/InnoDB-3.23.41, August 13, 2001 @itemize @bullet @item Support for < 4 GB rows. The previous limit was 8000 bytes. @item Use the doublewrite file flush method. @item Raw disk partitions supported as data files. @item InnoDB Monitor. @item Several hang bugs fixed and an ORDER BY bug ('Sort aborted') fixed. @end itemize @subsubsection MySQL/InnoDB-3.23.40, July 16, 2001 @itemize @bullet @item Only a few rare bugs fixed. @end itemize @subsubsection MySQL/InnoDB-3.23.39, June 13, 2001 @itemize @bullet @item CHECK TABLE now works for InnoDB tables. @item A new my.cnf parameter innodb_unix_file_flush_method introduced. It can be used to tune disk write performance. @item An auto-increment column now gets new values past the transaction mechanism. This saves CPU time and eliminates transaction deadlocks in new value assignment. @item Several bug fixes, most notably the rollback bug in 3.23.38. @end itemize @subsubsection MySQL/InnoDB-3.23.38, May 12, 2001 @itemize @bullet @item The new syntax SELECT ... LOCK IN SHARE MODE is introduced. @item InnoDB now calls fsync after every disk write and calculates a checksum for every database page it writes or reads, which will reveal disk defects. @item Several bug fixes. @end itemize @node InnoDB contact information, , InnoDB change history, InnoDB @subsection InnoDB Contact Information Contact information of Innobase Oy, producer of the InnoDB engine. Web site: @uref{http://www.innodb.com/}. E-mail: @email{Heikki.Tuuri@@innodb.com} @example phone: 358-9-6969 3250 (office) 358-40-5617367 (mobile) Innobase Oy Inc. World Trade Center Helsinki Aleksanterinkatu 17 P.O.Box 800 00101 Helsinki Finland @end example @node BDB, , InnoDB, Table types @section @code{BDB} or @code{BerkeleyDB} Tables @cindex tables, @code{BDB} @cindex tables, @code{Berkeley DB} @menu * BDB overview:: Overview of @code{BDB} Tables * BDB install:: Installing @code{BDB} * BDB start:: @code{BDB} startup options * BDB characteristics:: Characteristics of @code{BDB} tables: * BDB TODO:: Things we need to fix for @code{BDB} in the near future: * BDB portability:: Operating systems supported by @code{BDB} * BDB restrictions:: Restrictions on @code{BDB} Tables * BDB errors:: Errors That May Occur When Using @code{BDB} Tables @end menu @node BDB overview, BDB install, BDB, BDB @subsection Overview of @code{BDB} Tables BerkeleyDB, available at @uref{http://www.sleepycat.com/} has provided MySQL with a transactional storage engine. Support for this storage engine is included in the MySQL source distribution starting from version 3.23.34 and is activated in the MySQL-Max binary. This storage engine is typically called @code{BDB} for short. @code{BDB} tables may have a greater chance of surviving crashes and are also capable of @code{COMMIT} and @code{ROLLBACK} operations on transactions. The MySQL source distribution comes with a @code{BDB} distribution that has a couple of small patches to make it work more smoothly with MySQL. You can't use a non-patched @code{BDB} version with MySQL. We at MySQL AB are working in close cooperation with Sleepycat to keep the quality of the MySQL/BDB interface high. When it comes to supporting @code{BDB} tables, we are committed to help our users to locate the problem and help creating a reproducible test case for any problems involving @code{BDB} tables. Any such test case will be forwarded to Sleepycat who in turn will help us find and fix the problem. As this is a two-stage operation, any problems with @code{BDB} tables may take a little longer for us to fix than for other storage engines. However, as the BerkeleyDB code itself has been used by many other applications than MySQL, we don't envision any big problems with this. @xref{Support}. @node BDB install, BDB start, BDB overview, BDB @subsection Installing @code{BDB} If you have downloaded a binary version of MySQL that includes support for BerkeleyDB, simply follow the instructions for installing a binary version of MySQL. @xref{Installing binary}. @xref{mysqld-max, , @code{mysqld-max}}. To compile MySQL with Berkeley DB support, download MySQL Version 3.23.34 or newer and configure @code{MySQL} with the @code{--with-berkeley-db} option. @xref{Installing source}. @example cd /path/to/source/of/mysql-3.23.34 ./configure --with-berkeley-db @end example Please refer to the manual provided with the @code{BDB} distribution for more updated information. Even though Berkeley DB is in itself very tested and reliable, the MySQL interface is still considered beta quality. We are actively improving and optimising it to get it stable very soon. @node BDB start, BDB characteristics, BDB install, BDB @subsection @code{BDB} startup options If you are running with @code{AUTOCOMMIT=0} then your changes in @code{BDB} tables will not be updated until you execute @code{COMMIT}. Instead of commit you can execute @code{ROLLBACK} to forget your changes. @xref{COMMIT}. If you are running with @code{AUTOCOMMIT=1} (the default), your changes will be committed immediately. You can start an extended transaction with the @code{BEGIN WORK} SQL command, after which your changes will not be committed until you execute @code{COMMIT} (or decide to @code{ROLLBACK} the changes). The following options to @code{mysqld} can be used to change the behaviour of @code{BDB} tables: @multitable @columnfractions .25 .55 @item @strong{Option} @tab @strong{Description} @item @code{--bdb-home=directory} @tab Base directory for @code{BDB} tables. This should be the same directory you use for @code{--datadir}. @item @code{--bdb-lock-detect=#} @tab Berkeley lock detect. One of (@code{DEFAULT}, @code{OLDEST}, @code{RANDOM}, or @code{YOUNGEST}). @item @code{--bdb-logdir=directory} @tab Berkeley DB log file directory. @item @code{--bdb-no-sync} @tab Don't synchronously flush logs. @item @code{--bdb-no-recover} @tab Don't start Berkeley DB in recover mode. @item @code{--bdb-shared-data} @tab Start Berkeley DB in multi-process mode (Don't use @code{DB_PRIVATE} when initialising Berkeley DB) @item @code{--bdb-tmpdir=directory} @tab Berkeley DB temporary file directory. @item @code{--skip-bdb} @tab Disable usage of @code{BDB} tables. @item @code{-O bdb_max_lock=1000} @tab Set the maximum number of locks possible. @xref{SHOW VARIABLES, , @code{bdb_max_lock}}. @end multitable If you use @code{--skip-bdb}, MySQL will not initialise the Berkeley DB library and this will save a lot of memory. Of course, you cannot use @code{BDB} tables if you are using this option. If you try to create a @code{BDB} table, MySQL will instead create a @code{MyISAM} table. Normally you should start @code{mysqld} without @code{--bdb-no-recover} if you intend to use @code{BDB} tables. This may, however, give you problems when you try to start @code{mysqld} if the @code{BDB} log files are corrupted. @xref{Starting server}. With @code{bdb_max_lock} you can specify the maximum number of locks (10000 by default) you can have active on a @code{BDB} table. You should increase this if you get errors of type @code{bdb: Lock table is out of available locks} or @code{Got error 12 from ...} when you have do long transactions or when @code{mysqld} has to examine a lot of rows to calculate the query. You may also want to change @code{binlog_cache_size} and @code{max_binlog_cache_size} if you are using big multi-line transactions. @xref{COMMIT, , @code{COMMIT}}. @node BDB characteristics, BDB TODO, BDB start, BDB @subsection Characteristics of @code{BDB} tables: @itemize @bullet @item To be able to rollback transactions, the @code{BDB} storage engine maintains log files. For maximum performance you should place these on another disk than your databases by using the @code{--bdb-logdir} option. @item MySQL performs a checkpoint each time a new @code{BDB} log file is started, and removes any log files that are not needed for current transactions. One can also run @code{FLUSH LOGS} at any time to checkpoint the Berkeley DB tables. For disaster recovery, one should use table backups plus MySQL's binary log. @xref{Backup}. @strong{Warning}: If you delete old log files that are in use, @code{BDB} will not be able to do recovery at all and you may lose data if something goes wrong. @item MySQL requires a @code{PRIMARY KEY} in each @code{BDB} table to be able to refer to previously read rows. If you don't create one, MySQL will create an maintain a hidden @code{PRIMARY KEY} for you. The hidden key has a length of 5 bytes and is incremented for each insert attempt. @item If all columns you access in a @code{BDB} table are part of the same index or part of the primary key, then MySQL can execute the query without having to access the actual row. In a @code{MyISAM} table the above holds only if the columns are part of the same index. @item The @code{PRIMARY KEY} will be faster than any other key, as the @code{PRIMARY KEY} is stored together with the row data. As the other keys are stored as the key data + the @code{PRIMARY KEY}, it's important to keep the @code{PRIMARY KEY} as short as possible to save disk and get better speed. @item @code{LOCK TABLES} works on @code{BDB} tables as with other tables. If you don't use @code{LOCK TABLE}, MySQL will issue an internal multiple-write lock on the table to ensure that the table will be properly locked if another thread issues a table lock. @item Internal locking in @code{BDB} tables is done on page level. @item @code{SELECT COUNT(*) FROM table_name} is slow as @code{BDB} tables doesn't maintain a count of the number of rows in the table. @item Sequential scanning is slower than with @code{MyISAM} tables as the data in @code{BDB} tables stored in B-trees and not in a separate datafile. @item The application must always be prepared to handle cases where any change of a @code{BDB} table may make an automatic rollback and any read may fail with a deadlock error. @item Keys are not prefix or suffix-compressed like keys in @code{MyISAM} tables. In other words, the key information will take a little more space in @code{BDB} tables compared to @code{MyISAM} tables. @item There are often holes in the @code{BDB} table to allow you to insert new rows in the middle of the key tree. This makes @code{BDB} tables somewhat larger than @code{MyISAM} tables. @item The optimiser needs to know an approximation of the number of rows in the table. MySQL solves this by counting inserts and maintaining this in a separate segment in each @code{BDB} table. If you don't issue a lot of @code{DELETE} or @code{ROLLBACK} statements, this number should be accurate enough for the MySQL optimiser, but as MySQL only stores the number on close, it may be incorrect if MySQL dies unexpectedly. It should not be fatal even if this number is not 100% correct. One can update the number of rows by executing @code{ANALYZE TABLE} or @code{OPTIMIZE TABLE}. @xref{ANALYZE TABLE} . @xref{OPTIMIZE TABLE}. @item If you get full disk with a @code{BDB} table, you will get an error (probably error 28) and the transaction should roll back. This is in contrast with @code{MyISAM} and @code{ISAM} tables where @code{mysqld} will wait for enough free disk before continuing. @end itemize @node BDB TODO, BDB portability, BDB characteristics, BDB @subsection Things we need to fix for @code{BDB} in the near future: @itemize @bullet @item It's very slow to open many @code{BDB} tables at the same time. If you are going to use @code{BDB} tables, you should not have a very big table cache (like >256) and you should use @code{--no-auto-rehash} with the @code{mysql} client. We plan to partly fix this in 4.0. @item @code{SHOW TABLE STATUS} doesn't yet provide that much information for @code{BDB} tables. @item Optimise performance. @item Change to not use page locks at all when we are scanning tables. @end itemize @node BDB portability, BDB restrictions, BDB TODO, BDB @subsection Operating systems supported by @code{BDB} Currently we know that the @code{BDB} storage engine works with the following operating systems: @itemize @bullet @item Linux 2.x Intel @item Solaris SPARC @item Caldera (SCO) OpenServer @item Caldera (SCO) UnixWare 7.0.1 @end itemize It doesn't work with the following operating systems: @itemize @bullet @item Linux 2.x Alpha @item Max OS X @end itemize Note: The above list is not complete; we will update it as we receive more information. If you build MySQL with support for @code{BDB} tables and get the following error in the log file when you start @code{mysqld}: @example bdb: architecture lacks fast mutexes: applications cannot be threaded Can't init dtabases @end example This means that @code{BDB} tables are not supported for your architecture. In this case you must rebuild MySQL without @code{BDB} table support. @node BDB restrictions, BDB errors, BDB portability, BDB @subsection Restrictions on @code{BDB} Tables Here follows the restrictions you have when using @code{BDB} tables: @itemize @bullet @item @code{BDB} tables store in the @file{.db} file the path to the file as it was created. (This was done to be able to detect locks in a multi-user environment that supports symlinks). The effect of this is that @code{BDB} tables are not movable between directories! @item When taking backups of @code{BDB} tables, you have to either use @code{mysqldump} or take a backup of all @code{table_name.db} files and the @code{BDB} log files. The @code{BDB} log files are the files in the base data directory named @code{log.XXXXXXXXXX} (ten digits); The @code{BDB} storage engine stores unfinished transactions in the log files and requires these logs to be present when @code{mysqld} starts. @end itemize @node BDB errors, , BDB restrictions, BDB @subsection Errors That May Occur When Using @code{BDB} Tables @itemize @bullet @item If you get the following error in the @code{hostname.err log} when starting @code{mysqld}: @example bdb: Ignoring log file: .../log.XXXXXXXXXX: unsupported log version # @end example it means that the new @code{BDB} version doesn't support the old log file format. In this case you have to delete all @code{BDB} logs from your database directory (the files with names that have the format @code{log.XXXXXXXXXX}) and restart @code{mysqld}. We would also recommend you to do a @code{mysqldump --opt} of your old @code{BDB} tables, delete the old tables, and restore the dump. @item If you are not running in auto-commit mode and delete a table that is referenced in another transaction, you may get the following error messages in your MySQL error log: @example 001119 23:43:56 bdb: Missing log fileid entry 001119 23:43:56 bdb: txn_abort: Log undo failed for LSN: 1 3644744: Invalid @end example This is not fatal but we don't recommend that you delete tables if you are not in auto-commit mode, until this problem is fixed (the fix is not trivial). @end itemize @node Clients, Extending MySQL, Table types, Top @chapter MySQL APIs @cindex client tools @cindex APIs @cindex @code{mysqlclient} library @cindex buffer sizes, client @cindex library, @code{mysqlclient} @menu * PHP:: MySQL PHP API * Perl:: MySQL Perl API * ODBC:: MySQL ODBC Support * C:: MySQL C API * Cplusplus:: MySQL C++ APIs * Java:: MySQL Java connectivity (JDBC) * Python:: MySQL Python APIs * Tcl:: MySQL Tcl APIs * Eiffel:: MySQL Eiffel wrapper * Ruby:: MySQL Ruby @end menu This chapter describes the APIs available for MySQL, where to get them, and how to use them. The C API is the most extensively covered, as it was developed by the MySQL team, and is the basis for most of the other APIs. @node PHP, Perl, Clients, Clients @section MySQL PHP API @cindex PHP API PHP is a server-side, HTML-embedded scripting language that may be used to create dynamic web pages. It contains support for accessing several databases, including MySQL. PHP may be run as a separate program or compiled as a module for use with the Apache web server. The distribution and documentation are available at the PHP web site (@uref{http://www.php.net/}). @menu * PHP problems:: Common problems with MySQL and PHP @end menu @node PHP problems, , PHP, PHP @subsection Common Problems with MySQL and PHP @itemize @bullet @item Error: "Maximum Execution Time Exceeded" This is a PHP limit; go into the @file{php3.ini} file and set the maximum execution time up from 30 seconds to something higher, as needed. It is also not a bad idea to double the ram allowed per script to 16MB instead of 8 MB. @item Error: "Fatal error: Call to unsupported or undefined function mysql_connect() in .." This means that your PHP version isn't compiled with MySQL support. You can either compile a dynamic MySQL module and load it into PHP or recompile PHP with built-in MySQL support. This is described in detail in the PHP manual. @item Error: "undefined reference to `uncompress'" This means that the client library is compiled with support for a compressed client/server protocol. The fix is to add @code{-lz} last when linking with @code{-lmysqlclient}. @end itemize @node Perl, ODBC, PHP, Clients @section MySQL Perl API @cindex APIs, Perl @cindex Perl API ここでは Perl @code{DBI} インターフェースについて述べる。 以前のインターフェースは @code{mysqlperl} であった。 @code{DBI}/@code{DBD} が Perl インターフェースとして現在推奨されているので、 @code{mysqlperl} に関してはここでは述べない。 @menu * DBI with DBD:: @code{DBI} with @code{DBD::mysql} * Perl DBI Class:: The @code{DBI} interface * DBI-info:: More @code{DBI}/@code{DBD} information @end menu @node DBI with DBD, Perl DBI Class, Perl, Perl @subsection @code{DBI} with @code{DBD::mysql} @code{DBI} は多くのデーターベースとの一般的なインターフェースである。 これは、多くのデーターベースと動作するスクリプトを変更なしに書けることを意味する。 そのためには、それぞれのデータベース用のデータベースドライバ (DBD) が必要である。 MySQL では、そのドライバは @code{DBD::mysql} である。 Perl5 DBI に関する詳細は、@code{DBI}ウェッブページを参照のこと： @example @uref{http://dbi.perl.org/} @end example Object Oriented Programming (OOP) に関する詳細は、Perl OOP ページを参照のこと： @example @uref{http://language.perl.com/info/documentation.html} @end example Note that if you want to use transactions with Perl, you need to have @code{Msql-Mysql-modules} version 1.2216 or newer. The recommended Perl module is @code{DBD-mysql-2.1022} or newer. Installation instructions for MySQL Perl support are given in @ref{Perl support}. If you have the MySQL module installed, you can find information about specific MySQL functionallity with one of the following command @example shell> @code{perldoc DBD/mysql} shell> @code{perldoc mysql} @end example @node Perl DBI Class, DBI-info, DBI with DBD, Perl @subsection The @code{DBI} Interface @noindent @strong{Portable DBI Methods} @multitable @columnfractions .25 .60 @item @code{connect} @tab データベースサーバと接続する @item @code{disconnect} @tab データベースサーバとの接続を切る @item @code{prepare} @tab SQL文を設定する @item @code{execute} @tab 設定されたSQL文を実行する @item @code{do} @tab SQL文を設定し、実行する @item @code{quote} @tab 挿入するためのクォート文字、または @code{BLOB} 値 @item @code{fetchrow_array} @tab フィールドの配列として次のレコードを取り出す @item @code{fetchrow_arrayref} @tab フィールドの配列参照として次のレコードを取り出す @item @code{fetchrow_hashref} @tab ハッシュテーブルへの参照として次のレコードを取り出す @item @code{fetchall_arrayref} @tab 配列の配列として全データを取り出す @item @code{finish} @tab 命令を終了し、リソースからシステムを切り離す @item @code{rows} @tab 影響のあったレコードの数を返す @item @code{data_sources} @tab ローカルホスト上で利用できるデータベースの配列を返す @item @code{ChopBlanks} @tab @code{fetchrow_*} メソッドが空白を取り除くかどうかを管理する @item @code{NUM_OF_PARAMS} @tab 設定された命令文中の placeholder の数 @item @code{NULLABLE} @tab どのフィールドに @code{NULL} 値があるか？ @item @code{trace} @tab Perform tracing for debugging @end multitable @noindent @strong{MySQL 固有メソッド} @multitable @columnfractions .25 .60 @item @code{insertid} @tab 最後の @code{AUTO_INCREMENT} 値 @item @code{is_blob} @tab どのフィールドが @code{BLOB} か？ @item @code{is_key} @tab どのフィールドがキーか？ @item @code{is_num} @tab どのフィールドが数値型か？ @item @code{is_pri_key} @tab どのフィールドがプライマリキーか？ @item @code{is_not_null} @tab どのフィールドが @code{NULL} 値か？　@code{NULLABLE} 参照。 @item @code{length} @tab 利用可能なフィールドサイズの最大値 @item @code{max_length} @tab 実際に存在しているフィールドサイズの最大値 @item @code{NAME} @tab フィールド名 @item @code{NUM_OF_FIELDS} @tab 返されたフィールドの数 @item @code{table} @tab 返されたセットのテーブル名 @item @code{type} @tab 全てのフィールドの型 @item @code{_CreateDB} @tab データベースを作成する @item @code{_DropDB} @tab データベースを削除する。 @strong{＊＊＊このメソッドは危険である＊＊＊} @end multitable 以下の節に、より詳細な Perl メソッドの解説がある。 Variables used for method return values have these meanings: @table @code @item $dbh Database handle @item $sth Statement handle @item $rc Return code (often a status) @item $rv Return value (often a row count) @end table @noindent @strong{汎用 DBI メソッド} @table @code Generally the 'do' statement is MUCH faster (and is preferable) than prepare/execute for statements that doesn't contain parameters. @findex DBI->connect() @findex connect() DBI method @item connect($data_source, $username, $password) データソースとのデータベース接続をするために @code{connect} を使う。 @code{$data_source} 値は @code{DBI:driver_name:} ではじめること。 @code{DBD::mysql} ドライバーを用いた @code{connect} の使用例： @example $dbh = DBI->connect("DBI:mysql:$database", $user, $password); $dbh = DBI->connect("DBI:mysql:$database:$hostname", $user, $password); $dbh = DBI->connect("DBI:mysql:$database:$hostname:$port", $user, $password); @end example ユーザー名またはパスワードが未設定の場合、 @code{DBI} は環境変数である @code{DBI_USER} と @code{DBI_PASS} をそれぞれ使う。 ホスト名を指定しない場合は、@code{'localhost'} がデフォルトとなる。 ポート番号を指定しない場合は、MySQL ポート（@value{default_port}） がデフォルトとなる。 As of @code{Msql-Mysql-modules} Version 1.2009, the @code{$data_source} value allows certain modifiers: @table @code @item mysql_read_default_file=file_name Read @file{filename} as an option file. For information on option files, see @ref{Option files}. @item mysql_read_default_group=group_name The default group when reading an option file is normally the @code{[client]} group. By specifying the @code{mysql_read_default_group} option, the default group becomes the @code{[group_name]} group. @item mysql_compression=1 Use compressed communication between the client and server (MySQL Version 3.22.3 or later). @item mysql_socket=/path/to/socket Specify the pathname of the Unix socket that is used to connect to the server (MySQL Version 3.21.15 or later). @end table Multiple modifiers may be given; each must be preceded by a semicolon. For example, if you want to avoid hardcoding the user name and password into a @code{DBI} script, you can take them from the user's @file{~/.my.cnf} option file instead by writing your @code{connect} call like this: @example $dbh = DBI->connect("DBI:mysql:$database" . ";mysql_read_default_file=$ENV@{HOME@}/.my.cnf", $user, $password); @end example This call will read options defined for the @code{[client]} group in the option file. If you wanted to do the same thing but use options specified for the @code{[perl]} group as well, you could use this: @example $dbh = DBI->connect("DBI:mysql:$database" . ";mysql_read_default_file=$ENV@{HOME@}/.my.cnf" . ";mysql_read_default_group=perl", $user, $password); @end example @findex DBI->disconnect @findex disconnect DBI method @item disconnect @code{disconnect} メソッドは、データベースとのデータベースハンドルを切断する。 プログラムを終了する直前に呼び出されるのが典型的である。 例： @example $rc = $dbh->disconnect; @end example @findex DBI->prepare() @findex prepare() DBI method @item prepare($statement) データベースエンジンで実行するためのSQL文を設定し、@code{execute} メソッドで 使用出来るステートメントハンドル @code{($sth)} を返す。 Typically you handle @code{SELECT} statements (and @code{SELECT}-like statements such as @code{SHOW}, @code{DESCRIBE}, and @code{EXPLAIN}) by means of @code{prepare} and @code{execute}. Example: @example $sth = $dbh->prepare($statement) or die "Can't prepare $statement: $dbh->errstr\n"; @end example If you want to read big results to your client you can tell Perl to use @code{mysql_use_result()} with: @example my $sth = $dbh->prepare($statement @{ "mysql_use_result" => 1@}); @end example @findex DBI->execute @findex execute DBI method @item execute @code{execute} メソッドは、設定されたSQL文を実行する。非 @code{SELECT} 文のときは、 影響のあったレコードの数を返す。 もしなんの変化もなかったなら、 @code{execute} は @code{"0E0"} (これは Perl では ゼロ 扱いですが、 真 でもある) を返す。 If an error occurs, @code{execute} returns @code{undef}. @code{SELECT} 文のときは、SQL要求を開始するのみである。 データを操作する @code{fetch_*} メソッドの内の一つを記述する必要がある。 例： @example $rv = $sth->execute or die "can't execute the query: $sth->errstr; @end example @findex DBI->do() @findex do() DBI method @item do($statement) @code{do} メソッドはSQL文を設定・実行し、影響のあったレコードの数を返す。 このメソッドは、「非 select」文、すなわち、高度（ドライバーの限界のため）で設定できない文、 一度の実行（inserts, deletes など）で済む文のときに一般的に用いられる。 例： @example $rv = $dbh->do($statement) or die "Can't execute $statement: $dbh- >errstr\n"; @end example @findex DBI->quote() @findex quote() DBI method @cindex quoting strings @cindex strings, quoting @item quote($string) @code{quote} メソッドは、文字列中にエスケープ文字があるときに用いられ、 クォート文字を文の外側に付加する。 例： @example $sql = $dbh->quote($string) @end example @findex DBI->fetchrow_array @findex fetchrow_array DBI method @item fetchrow_array このメソッドはデータの次のレコードを取り出し、フィールドの値の配列として返す。 例： @example while(@@row = $sth->fetchrow_array) @{ print qw($row[0]\t$row[1]\t$row[2]\n); @} @end example @findex DBI->fetchrow_arrayref @findex fetchrow_arrayref DBI method @item fetchrow_arrayref このメソッドはデータの次のレコードを取り出し、フィールドの値の配列への参照として返す。 例： @example while($row_ref = $sth->fetchrow_arrayref) @{ print qw($row_ref->[0]\t$row_ref->[1]\t$row_ref->[2]\n); @} @end example @findex DBI->fetchrow_hashref @findex fetchrow_hashref DBI method @item fetchrow_hashref このメソッドはデータのレコードを取り出し、名前・値のペアのフィールドを含んだ ハッシュテーブルへの参照を返す。このメソッドは、上で示した配列参照 （訳注：@code{fetchrow_arrayref}）よりもかなり効率的ではない。例： @example while($hash_ref = $sth->fetchrow_hashref) @{ print qw($hash_ref->@{firstname@}\t$hash_ref->@{lastname@}\t\ $hash_ref->@{title@}\n); @} @end example @findex DBI->fetchall_arrayref @findex fetchall_arrayref DBI method @item fetchall_arrayref このメソッドは、SQL文より返されたデータ（レコード）の全てを得るために使う。 このメソッドは、各レコードへの参照の配列の配列への参照を返す。 入れ子のループを使ってデータを利用・表示する。例： @example my $table = $sth->fetchall_arrayref or die "$sth->errstr\n"; my($i, $j); for $i ( 0 .. $#@{$table@} ) @{ for $j ( 0 .. $#@{$table->[$i]@} ) @{ print "$table->[$i][$j]\t"; @} print "\n"; @} @end example @findex DBI->finish @findex finish DBI method @item finish そのステートメントハンドルからそれ以上データを取り出さないことを示す。ステートメントハンドルや、つかんでいたシステムリソースを解放するためにこのメソッドを呼び出す。例： @example $rc = $sth->finish; @end example @findex DBI->rows @findex rows DBI method @item rows 最後の命令により、（データの更新、削除、などで）影響のあったレコードの数を返す。 このメソッドは @code{do} あるいは 非 @code{SELECT} @code{execute} 文を 実行した後に、たいてい使われる。例： Example: @example $rv = $sth->rows; @end example @findex DBI->@{NULLABLE@} @findex NULLABLE DBI method @item NULLABLE Returns a reference to an array of values that indicate whether columns may contain @code{NULL} values. The possible values for each array element are 0 or the empty string if the column cannot be @code{NULL}, 1 if it can, and 2 if the column's @code{NULL} status is unknown. Example: @example $null_possible = $sth->@{NULLABLE@}; @end example @findex DBI->@{NUM_OF_FIELDS@} @findex NUM_OF_FIELDS DBI method @item NUM_OF_FIELDS この属性は、@code{SELECT} 文や @code{SHOW FIELDS} 文によって返された フィールドの数を示している。命令文が結果を返したかどうかをチェックするのに、 これを使うことが出来る：０値は、@code{INSERT}, @code{DELETE} または @code{UPDATE} のような非 @code{SELECT} 文を示している。例： Example: @example $nr_of_fields = $sth->@{NUM_OF_FIELDS@}; @end example @findex DBI->data_sources() @findex data_sources() DBI method @item data_sources($driver_name) このメソッドは、@code{'localhost'} ホスト上の MySQL サーバで 利用可能なデータベースの名前を含んだ配列を返す。例： @example @@dbs = DBI->data_sources("mysql"); @end example @findex DBI->@{ChopBlanks@} @findex ChopBlanks DBI method @item ChopBlanks この属性は、 @code{fetchrow_*} メソッドが返り値から前後の空白を 除去するかどうかを決定する。例： @example $sth->@{'ChopBlanks'@} =1; @end example @findex DBI->trace @findex trace DBI method @item trace($trace_level) @itemx trace($trace_level, $trace_filename) The @code{trace} method enables or disables tracing. When invoked as a @code{DBI} class method, it affects tracing for all handles. When invoked as a database or statement handle method, it affects tracing for the given handle (and any future children of the handle). Setting @code{$trace_level} to 2 provides detailed trace information. Setting @code{$trace_level} to 0 disables tracing. Trace output goes to the standard error output by default. If @code{$trace_filename} is specified, the file is opened in append mode and output for @strong{all} traced handles is written to that file. Example: @example DBI->trace(2); # trace everything DBI->trace(2,"/tmp/dbi.out"); # trace everything to # /tmp/dbi.out $dth->trace(2); # trace this database handle $sth->trace(2); # trace this statement handle @end example @tindex DBI_TRACE environment variable @tindex Environment variable, DBI_TRACE You can also enable @code{DBI} tracing by setting the @code{DBI_TRACE} environment variable. Setting it to a numeric value is equivalent to calling @code{DBI->(value)}. Setting it to a pathname is equivalent to calling @code{DBI->(2,value)}. @end table @noindent @strong{MySQL 固有メソッド} The methods shown here are MySQL-specific and not part of the @code{DBI} standard. Several of them are now deprecated: @code{is_blob}, @code{is_key}, @code{is_num}, @code{is_pri_key}, @code{is_not_null}, @code{length}, @code{max_length}, and @code{table}. Where @code{DBI}-standard alternatives exist, they are noted here: @table @code @findex DBI->@{insertid@} @findex insertid DBI method @cindex AUTO_INCREMENT, using with DBI @item insertid MySQL の特徴である @code{AUTO_INCREMENT} を使うとき、 新しい自動繰り上がり値がここに記憶される。例： Example: @example $new_id = $sth->@{insertid@}; @end example As an alternative, you can use @code{$dbh->@{'mysql_insertid'@}}. @findex DBI->@{is_blob@} @findex is_blob DBI method @item is_blob 配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドが @code{BLOB} 値であることを示す。例： @example $keys = $sth->@{is_blob@}; @end example @findex DBI->@{is_key@} @findex is_key DBI method @item is_key 配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドがキーであることを示す。 例： @example $keys = $sth->@{is_key@}; @end example @findex DBI->@{is_num@} @findex is_num DBI method @item is_num 配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドが数値型であることを示す。 例： @example $nums = $sth->@{is_num@}; @end example @findex DBI->@{is_pri_key@} @findex is_pri_key DBI method @item is_pri_key 配列の各要素に対し、ブール値の配列への参照を返す。TRUE であれば そのフィールドがプライマリーキーであることを示す。 例： @example $pri_keys = $sth->@{is_pri_key@}; @end example @findex DBI->@{is_not_null@} @findex is_not_null DBI method @item is_not_null 配列の各要素に対し、ブール値の配列への参照を返す。FALSE であれば そのフィールドが @code{NULL} 値を含むことを示す。 例： @example $not_nulls = $sth->@{is_not_null@}; @end example @code{is_not_null} is deprecated; 前述の @code{NULLABLE} 属性を使用するほうが望ましい。それが DBI の標準である。 @findex DBI->@{length@} @findex length DBI method @findex DBI->@{max_length@} @findex max_length DBI method @item length @itemx max_length それぞれのメソッドは、フィールドサイズの配列への参照を返す。@code{length} 配列は、 （テーブル記述で定義された）各フィールドの利用可能最大値を示す。 @code{max_length} 配列は、テーブル中に実際に存在している最大値を示す。例： @example $lengths = $sth->@{length@}; $max_lengths = $sth->@{max_length@}; @end example @findex DBI->@{NAME@} @findex NAME DBI method @item NAME フィールド名の配列への参照を返す。 例： @example $names = $sth->@{NAME@}; @end example @findex DBI->@{table@} @findex table DBI method @item table テーブル名の配列への参照を返す。 例： @example $tables = $sth->@{table@}; @end example @findex DBI->@{type@} @findex type DBI method @item type フィールドの型の配列への参照を返す。 例： @example $types = $sth->@{type@}; @end example @end table @node DBI-info, , Perl DBI Class, Perl @subsection @code{DBI}/@code{DBD} に関するそれ以上の情報 @code{DBI} に関するそれ以上の情報は @code{perldoc} コマンドで得られる。 @example perldoc DBI perldoc DBI::FAQ perldoc DBD::mysql @end example 他のフォーマットに変換するツール、@code{pod2man}, @code{pod2html} なども 使うことが出来る。 そしてもちろん、@code{DBI} の最新情報は @code{DBI} ウェッブページで見ることが出来る：@uref{http://dbi.perl.org/}. @node ODBC, C, Perl, Clients @section MySQL ODBC サポート @cindex ODBC @cindex Windows @cindex MyODBC @menu * Installing MyODBC:: How to install MyODBC * ODBC administrator:: How to fill in the various fields in the ODBC administrator program * MyODBC connect parameters:: Connect parameters for MyODBC * ODBC Problems:: How to report problems with MySQL ODBC * MyODBC clients:: Programs known to work with @code{MyODBC} * ODBC and last_insert_id:: How to get the value of an @code{AUTO_INCREMENT} column in ODBC * MyODBC bug report:: Reporting problems with MyODBC @end menu MySQL は @code{MyODBC} プログラムで ODBC 機能を提供します。 This chapter will teach you how to install @code{MyODBC}, and how to use it. Here, you will also find a list of common programs that are known to work with @code{MyODBC}. @node Installing MyODBC, ODBC administrator, ODBC, ODBC @subsection How To Install MyODBC @code{MyODBC} 2.50 is a 32-bit ODBC 2.50 specification level 0 (with level 1 and level 2 features) driver for connecting an ODBC-aware application to MySQL. @code{MyODBC} works on Windows 9x/Me/NT/2000/XP and most Unix platforms. @code{MyODBC} 3.51 is an enhanced version with ODBC 3.5x specification level 1 (complete core API + level 2 features). @code{MyODBC} は @code{Open Source} で、最新の物は以下にあります： @uref{http://www.mysql.com/downloads/api-myodbc.html}. Please note that the 2.50.x versions are @code{LGPL} licensed, whereas the 3.51.x versions are @code{GPL} licensed. 日本語文字コードに対応させた物は： @uref{http://www.SoftAgency.co.jp/}. If you have problem with @code{MyODBC} and your program also works with OLEDB, you should try the OLEDB driver. Normally you only need to install @code{MyODBC} on Windows machines. You only need @code{MyODBC} for Unix if you have a program like ColdFusion that is running on the Unix machine and uses ODBC to connect to the databases. もし、Unix に @code{MyODBC} をインストールしたいなら、 @strong{ODBC} マネージャーも必要でしょう。 @code{MyODBC} は Unix の ODBC マネージャー でも動作することが知られています。 To install @code{MyODBC} on Windows, you should download the appropriate @code{MyODBC} @file{.zip} file, unpack it with @code{WinZIP} or some similar program, and execute the @file{SETUP.EXE} file. Windows/NT の場合、@code{MyODBC} をインストール時にいかのような エラーになるかもしれません: @example An error occurred while copying C:\WINDOWS\SYSTEM\MFC30.DLL. Restart Windows and try installing again (before running any applications which use ODBC) @end example The problem in this case is that some other program is using ODBC and because of how Windows is designed, you may not in this case be able to install a new ODBC drivers with Microsoft's ODBC setup program. In most cases you can continue by just pressing @code{Ignore} to copy the rest of the MyODBC files and the final installation should still work. これを解決するには、一度 ’セーフモード’でコンピュータを立ち上げ直し、 (windows リブート時に、F8キーを押すことで、セーフモードの選択が可能です) @code{MyODBC} をインストールして、リブートします: @itemize @bullet @item Windows マシンから UNIX に ODBC アプリケーションを使用して接続するには、 まず最初に Windows マシンに @code{MyODBC} をインストールしなくては なりません。 @item UNIX 上の MySQL サーバーに対して、ユーザーと Windows マシンの アクセス許可を与えます。 これは、 @code{GRANT} コマンドで可能です。 @xref{GRANT,,@code{GRANT}}. @item ODBC DSN を以下のようにして作成しなくてはなりません： @itemize @minus @item Windows マシンのコントロールパネルを開く @item Double-click the ODBC Data Sources 32-bit icon. @item "ユーサーDSN" をクリック @item "追加..." ボタンをクリック @item 新しいデータソース の画面から、MySQL を選び、完了ボタンをクリック。 @item MySQL Driver のデフォルト設定が現れます。 @xref{ODBC administrator}. @end itemize @item Now start your application and select the ODBC driver with the DSN you specified in the ODBC administrator. @end itemize MyODBC の設定画面には、MySQL 接続時のオプションがいくつか 設定できるようになっています。 もし問題がある場合は、これらを試します。 @node ODBC administrator, MyODBC connect parameters, Installing MyODBC, ODBC @subsection ODBC 管理プログラムの各種項目を埋めるには？ @cindex ODBC, administrator Windows95 上のサーバ名の記述には3つの可能性があります: @itemize @bullet @item サーバの IP アドレスの使用 @item ファイル @file{\windows\lmhosts} への次の情報の追加: @example ip hostname @end example 例えば： @example 194.216.84.21 my_hostname @end example @item DNS を使用するように設定します。 @end itemize @code{ODBC setup} を埋める方法の例: @example Windows DSN name: test Description: This is my test database MySql Database: test Server: 194.216.84.21 User: monty Password: my_password Port: @end example @code{Windows DSN name} 項目の値は、あなたのwindows ODBC setup における 一意の名前です。 ODBC setup 画面で、@code{Server}, @code{User}, @code{Password}, @code{Port} フィールドを設定する必要はありません。 しかし、ここで設定をすると、後でサーバーに接続する際に、 設定した値がデフォルト値として使用されます。 使用時に値を変更するオプションはあります。 ポート番号が設定されていないなら、デフォルトポート (@value{default_port}) が使用 されます。 もしオプションを @code{Read options from C:\my.cnf} にすると, @code{client} と @code{odbc} グループは @file{C:\my.cnf} ファイルから読まれます。 @code{mysql_options()} で使用できる全てのオプションが利用可能です。 @xref{mysql_options, , @code{mysql_options()}}. @node MyODBC connect parameters, ODBC Problems, ODBC administrator, ODBC @subsection Connect parameters for MyODBC One can specify the following parameters for @code{MyODBC} on the @code{[Servername]} section of an @file{ODBC.INI} file or through the @code{InConnectionString} argument in the @code{SQLDriverConnect()} call. @multitable @columnfractions .15 .20 .65 @item @strong{Parameter} @tab @strong{Default value} @tab @strong{Comment} @item user @tab ODBC (on Windows) @tab The username used to connect to MySQL. @item server @tab localhost @tab The hostname of the MySQL server. @item database @tab @tab The default database. @item option @tab 0 @tab A integer by which you can specify how @code{MyODBC} should work. See below. @item port @tab 3306 @tab The TCP/IP port to use if @code{server} is not @code{localhost}. @item stmt @tab @tab A statement that will be executed when connecting to @code{MySQL}. @item password @tab @tab The password for the @code{server} @code{user} combination. @item socket @tab @tab The socket or Windows pipe to connect to. @end multitable The option argument is used to tell @code{MyODBC} that the client isn't 100% ODBC compliant. On Windows, one normally sets the option flag by toggling the different options on the connection screen but one can also set this in the opton argument. The following options are listed in the same order as they appear in the @code{MyODBC} connect screen: @multitable @columnfractions .10 .90 @item @strong{Bit} @tab @strong{Description} @item 1 @tab The client can't handle that @code{MyODBC} returns the real width of a column. @item 2 @tab The client can't handle that MySQL returns the true value of affected rows. If this flag is set then MySQL returns 'found rows' instead. One must have MySQL 3.21.14 or newer to get this to work. @item 4 @tab Make a debug log in c:\myodbc.log. This is the same as putting @code{MYSQL_DEBUG=d:t:O,c::\myodbc.log} in @file{AUTOEXEC.BAT} @item 8 @tab Don't set any packet limit for results and parameters. @item 16 @tab Don't prompt for questions even if driver would like to prompt @item 32 @tab Simulate a ODBC 1.0 driver in some context. @item 64 @tab Ignore use of database name in 'database.table.column'. @item 128 @tab Force use of ODBC manager cursors (experimental). @item 256 @tab Disable the use of extended fetch (experimental). @item 512 @tab Pad CHAR fields to full column length. @item 1024 @tab SQLDescribeCol() will return fully qualifed column names @item 2048 @tab Use the compressed server/client protocol @item 4096 @tab Tell server to ignore space after function name and before @code{'('} (needed by PowerBuilder). This will make all function names keywords! @item 8192 @tab Connect with named pipes to a @code{mysqld} server running on NT. @item 16384 @tab Change LONGLONG columns to INT columns (some applications can't handle LONGLONG). @item 32768 @tab Return 'user' as Table_qualifier and Table_owner from SQLTables (experimental) @item 65536 @tab Read parameters from the @code{client} and @code{odbc} groups from @file{my.cnf} @item 131072 @tab Add some extra safety checks (should not bee needed but...) @end multitable If you want to have many options, you should add the above flags! For example setting option to 12 (4+8) gives you debugging without package limits! The default @file{MYODBC.DLL} is compiled for optimal performance. If you want to debug @code{MyODBC} (for example to enable tracing), you should instead use @file{MYODBCD.DLL}. To install this file, copy @file{MYODBCD.DLL} over the installed @file{MYODBC.DLL} file. @node ODBC Problems, MyODBC clients, MyODBC connect parameters, ODBC @subsection MyODBC での問題をどのように報告すべきか？ @code{MyODBC} は以下でテストされました： Access, Admndemo.exe, C++-Builder, Borland Builder 4, Centura Team Developer (formerly Gupta SQL/Windows), ColdFusion (on Solaris and NT with svc pack 5), Crystal Reports, DataJunction, Delphi, ERwin, Excel, iHTML, FileMaker Pro, FoxPro, Notes 4.5/4.6, SBSS, Perl DBD-ODBC, Paradox, Powerbuilder, Powerdesigner 32 bit, VC++, and Visual Basic. If you know of any other applications that work with @code{MyODBC}, please send mail to @email{myodbc@@lists.mysql.com} about this! With some programs you may get an error like: @code{Another user has modifies the record that you have modified}. In most cases this can be solved by doing one of the following things: @itemize @bullet @item Add a primary key for the table if there isn't one already. @item Add a timestamp column if there isn't one already. @item Only use double float fields. Some programs may fail when they compare single floats. @end itemize If the above doesn't help, you should do a @code{MyODBC} trace file and try to figure out why things go wrong. @node MyODBC clients, ODBC and last_insert_id, ODBC Problems, ODBC @subsection MyODBC で動作することが知られているプログラム Most programs should work with @code{MyODBC}, but for each of those listed here, we have tested it ourselves or received confirmation from some user that it works: @table @asis @item @strong{Program} @strong{Comment} @cindex Access program @item Access To make Access work: @itemize @bullet @item If you are using Access 2000, you should get and install the newest (version 2.6 or above) Microsoft MDAC (@code{Microsoft Data Access Components}) from @uref{http://www.microsoft.com/data/}. This will fix the following bug in Access: when you export data to MySQL, the table and column names aren't specified. Another way to around this bug is to upgrade to MyODBC Version 2.50.33 and MySQL Version 3.23.x, which together provide a workaround for this bug! You should also get and apply the Microsoft Jet 4.0 Service Pack 5 (SP5) which can be found here @uref{http://support.microsoft.com/support/kb/articles/Q 239/1/14.ASP}. This will fix some cases where columns are marked as @code{#deleted#} in Access. Note that if you are using MySQL Version 3.22, you must to apply the MDAC patch and use MyODBC 2.50.32 or 2.50.34 and above to go around this problem. @item For all Access versions, you should enable the MyODBC option flag @code{Return matching rows}. For Access 2.0, you should additionally enable @code{Simulate ODBC 1.0}. @item 更新するつもりのあるテーブルの全てに、timestamp を持たせなければなりません。 For maximum portability @code{TIMESTAMP(14)} or simple @code{TIMESTAMP} is recommended instead of other @code{TIMESTAMP(X)} variations. @item You should have a primary key in the table. If not, new or updated rows may show up as @code{#DELETED#}. @item Only use @code{DOUBLE} float fields. Access fails when comparing with single floats. The symptom usually is that new or updated rows may show up as @code{#DELETED#} or that you can't find or update rows. tem If you are linking a table through MyODBC, which has @code{BIGINT} as one of the column, then the results will be displayed as @code{#DELETED}. The work around solution is: @itemize @bullet @item Have one more dummy column with @code{TIMESTAMP} as the data type, preferably @code{TIMESTAMP(14)}. @item Check the @code{'Change BIGINT columns to INT'} in connection options dialog in ODBC DSN Administrator @item Delete the table link from access and re-create it. @end itemize It still displays the previous records as @code{#DELETED#}, but newly added/updated records will be displayed properly. @item ダブルフロート型だけが(実数に)使用できます。Accessではシングルフロートと比較は失 敗します。 The symptom usually is that new or updated rows may show up as @code{#Deleted#} or that you can't find or update rows. @item If you still get the error @code{Another user has changed your data} after adding a @code{TIMESTAMP} column, the following trick may help you: Don't use @code{table} data sheet view. Create instead a form with the fields you want, and use that @code{form} data sheet view. You should set the @code{DefaultValue} property for the @code{TIMESTAMP} column to @code{NOW()}. It may be a good idea to hide the @code{TIMESTAMP} column from view so your users are not confused. @item アクセスは、MySQL が理解できない間違った SQL クエリを 作成するかもしれません。 これはアクセスのメニューから @code{"Query|SQLSpecific|Pass-Through"} を選択すれば 直すことが可能です。 @item NT 上の Access は @code{BLOB} フィールドを @code{OLE OBJECTS} と認識します。 もし @code{MEMO} フィールドを代わりに使用したいなら、 @code{ALTER TABLE} を使って、 @code{TEXT} 型にフィールドを変更しなくてはなりません。 @item Access は @code{DATE} フィールドをいつも正しく扱うことが出来ません。 もしこれらの問題があった場合、フィールド型を @code{DATETIME} に変えてください。 @item If you have in Access a column defined as @code{BYTE}, Access will try to export this as @code{TINYINT} instead of @code{TINYINT UNSIGNED}. This will give you problems if you have values > 127 in the column! @end itemize @cindex ADO program @item ADO When you are coding with the ADO API and @code{MyODBC} you need to put attention in some default properties that aren't supported by the MySQL server. For example, using the @code{CursorLocation Property} as @code{adUseServer} will return for the @code{RecordCount Property} a result of -1. To have the right value, you need to set this property to @code{adUseClient}, like is showing in the VB code here: @example Dim myconn As New ADODB.Connection Dim myrs As New Recordset Dim mySQL As String Dim myrows As Long myconn.Open "DSN=MyODBCsample" mySQL = "SELECT * from user" myrs.Source = mySQL Set myrs.ActiveConnection = myconn myrs.CursorLocation = adUseClient myrs.Open myrows = myrs.RecordCount myrs.Close myconn.Close @end example Another workaround is to use a @code{SELECT COUNT(*)} statement for a similar query to get the correct row count. @item Active server pages (ASP) You should use the option flag @code{Return matching rows}. @item BDE applications To get these to work, you should set the option flags @code{Don't optimize column widths} and @code{Return matching rows}. @cindex Borland Builder 4 program @item Borland Builder 4 When you start a query you can use the property @code{Active} or use the method @code{Open}. Note that @code{Active} will start by automatically issuing a @code{SELECT * FROM ...} query that may not be a good thing if your tables are big! @item ColdFusion (On Unix) The following information is taken from the ColdFusion documentation: Use the following information to configure ColdFusion Server for Linux to use the unixODBC driver with @code{MyODBC} for MySQL data sources. Allaire has verified that @code{MyODBC} Version 2.50.26 works with MySQL Version 3.22.27 and ColdFusion for Linux. (Any newer version should also work.) You can download @code{MyODBC} at @uref{http://www.mysql.com/downloads/api-myodbc.html} @cindex ColdFusion program ColdFusion Version 4.5.1 allows you to us the ColdFusion Administrator to add the MySQL data source. However, the driver is not included with ColdFusion Version 4.5.1. Before the MySQL driver will appear in the ODBC datasources drop-down list, you must build and copy the @code{MyODBC} driver to @file{/opt/coldfusion/lib/libmyodbc.so}. The Contrib directory contains the program @file{mydsn-xxx.zip} which allows you to build and remove the DSN registry file for the MyODBC driver on Coldfusion applications. @cindex DataJunction @item DataJunction You have to change it to output @code{VARCHAR} rather than @code{ENUM}, as it exports the latter in a manner that causes MySQL grief. @cindex Excel @item Excel Works. A few tips: @itemize @bullet @item 日付に問題が起きた場合、@code{CONCAT()} 関数を使用し、文字として SELECT してみて ください。 例えば： @example select CONCAT(rise_time), CONCAT(set_time) from sunrise_sunset; @end example この方法で文字として返ってきた値を、Excel97 で時間として扱うようにすべきです。 この例の @code{CONCAT()} の目的は、フィールドの型が文字列であると ODBC をだます ことです。 @code{CONCAT()} がなければ、ODBC はフィールドの型が日付とわかるので、 Excel が今度はそれを理解できなくなります。 これは Excel のバグです。なぜなら文字を自動で日付に直すのですから。 これは単にテキストファイルの情報を扱う場合ならばいいのですが、 各項目の型を知らせる ODBC 接続の情報を扱う場合は、とても愚かな方法です。 @end itemize @cindex Word program @item Word To retrieve data from MySQL to Word/Excel documents, you need to use the @code{MyODBC} driver and the Add-in Microsoft Query help. For example, create a db with a table containing 2 columns of text: @itemize @bullet @item Insert rows using the @code{mysql} client command-line tool. @item Create a DSN file using the ODBC manager, for example, @file{my} for the db above. @item Open the Word application. @item Create a blank new documentation. @item Using the tool bar called Database, press the button insert database. @item Press the button Get Data. @item At the right hand of the screen Get Data, press the button Ms Query. @item In the Ms Query create a New Data Source using the DSN file my. @item Select the new query. @item Select the columns that you want. @item Make a filter if you want. @item Make a Sort if you want. @item Select Return Data to Microsoft Word. @item Click Finish. @item Click Insert data and select the records. @item Click OK and you see the rows in your Word document. @end itemize @cindex odbcadmin program @item odbcadmin ODBC のテストプログラム. @cindex Delphi program @item Delphi DBE 3.2 以上を必ず使用してください。 MySQL に接続する際には、'Don't optimize column width' オプションをセッ トします。 Also, here is some potentially useful Delphi code that sets up both an ODBC entry and a BDE entry for @code{MyODBC} (the BDE entry requires a BDE Alias Editor that is free at a Delphi Super Page near you. (Thanks to Bryan Brunton @email{bryan@@flesherfab.com} for this): @example fReg:= TRegistry.Create; fReg.OpenKey('\Software\ODBC\ODBC.INI\DocumentsFab', True); fReg.WriteString('Database', 'Documents'); fReg.WriteString('Description', ' '); fReg.WriteString('Driver', 'C:\WINNT\System32\myodbc.dll'); fReg.WriteString('Flag', '1'); fReg.WriteString('Password', ''); fReg.WriteString('Port', ' '); fReg.WriteString('Server', 'xmark'); fReg.WriteString('User', 'winuser'); fReg.OpenKey('\Software\ODBC\ODBC.INI\ODBC Data Sources', True); fReg.WriteString('DocumentsFab', 'MySQL'); fReg.CloseKey; fReg.Free; Memo1.Lines.Add('DATABASE NAME='); Memo1.Lines.Add('USER NAME='); Memo1.Lines.Add('ODBC DSN=DocumentsFab'); Memo1.Lines.Add('OPEN MODE=READ/WRITE'); Memo1.Lines.Add('BATCH COUNT=200'); Memo1.Lines.Add('LANGDRIVER='); Memo1.Lines.Add('MAX ROWS=-1'); Memo1.Lines.Add('SCHEMA CACHE DIR='); Memo1.Lines.Add('SCHEMA CACHE SIZE=8'); Memo1.Lines.Add('SCHEMA CACHE TIME=-1'); Memo1.Lines.Add('SQLPASSTHRU MODE=SHARED AUTOCOMMIT'); Memo1.Lines.Add('SQLQRYMODE='); Memo1.Lines.Add('ENABLE SCHEMA CACHE=FALSE'); Memo1.Lines.Add('ENABLE BCD=FALSE'); Memo1.Lines.Add('ROWSET SIZE=20'); Memo1.Lines.Add('BLOBS TO CACHE=64'); Memo1.Lines.Add('BLOB SIZE=32'); AliasEditor.Add('DocumentsFab','MySQL',Memo1.Lines); @end example @cindex C++ Builder @item C++ Builder BDE 3.0で,テストされました。唯一の知られた問題は、 テーブルスキーマが変化する時、クエリフィールドが更新されないことです。 BDE は、index PRIMARY だけを認識し、プライマリーキーは認識していないように思えま す。これはさほど問題ではないですが。 @item Vision You should use the option flag @code{Return matching rows}. @cindex Visual Basic @item Visual Basic テーブルの更新を可能にするため、テーブルにプライマリーキーを作成しなくてはなりま せん。 Visual Basic with ADO can't handle big integers. This means that some queries like @code{SHOW PROCESSLIST} will not work properly. The fix is to set the option @code{OPTION=16384} in the ODBC connect string or to set the @code{Change BIGINT columns to INT} option in the MyODBC connect screen. You may also want to set the @code{Return matching rows} option. @item VisualInterDev If you get the error @code{[Microsoft][ODBC Driver Manager] Driver does not support this parameter} the reason may be that you have a @code{BIGINT} in your result. Try setting the @code{Change BIGINT columns to INT} option in the MyODBC connect screen. @item Visual Objects You should use the option flag @code{Don't optimize column widths}. @end table @node ODBC and last_insert_id, MyODBC bug report, MyODBC clients, ODBC @subsection @code{AUTO_INCREMENT} フィールドの値を ODBC で得る方法 @cindex AUTO-INCREMENT, ODBC 共通の問題は、@code{INSERT} で自動的に生成されるIDの値を得ることです。 ODBCでは、以下のようにします( 例中の @code{auto} が @code{AUTO_INCREMENT} フィー ルドです)： @example INSERT INTO foo (auto,text) VALUES(NULL,'text'); SELECT LAST_INSERT_ID(); @end example もしくは、他のテーブルにIDを挿入するだけなら以下のようにします： @example INSERT INTO foo (auto,text) VALUES(NULL,'text'); INSERT INTO foo2 (id,text) VALUES(LAST_INSERT_ID(),'text'); @end example @xref{Getting unique ID}. For the benefit of some ODBC applications (at least Delphi and Access), the following query can be used to find a newly inserted row: @example SELECT * FROM tbl_name WHERE auto IS NULL; @end example @node MyODBC bug report, , ODBC and last_insert_id, ODBC @subsection Reporting Problems with MyODBC @cindex reporting, MyODBC problems @cindex problems, ODBC @cindex MyODBC, reporting problems もし @code{MyODBC} 使用時に難しい問題にあたった場合、 ODBC マネージャのログファイル (ODBCADMIN からリクエストしたときのログ) と @code{MyODBC} のログを取り始めるべきです。 これはいかなる問題にも解決の糸口になるはずです。 @code{MyODBC} のログを取るには、以下のように行ないます： @enumerate @item Ensure that you are using @file{myodbcd.dll} and not @file{myodbc.dll}. The easiest way to do this is to get @file{myodbcd.dll} from the MyODBC distribution and copy it over the @file{myodbc.dll}, which is probably in your @file{C:\windows\system32} or @file{C:\winnt\system32} directory. Note that you probably want to restore the old myodbc.dll file when you have finished testing, as this is a lot faster than @file{myodbcd.dll}. @item Tag the `Trace MyODBC' option flag in the @code{MyODBC} connect/configure screen. The log will be written to file @file{C:\myodbc.log}. If the trace option is not remembered when you are going back to the above screen, it means that you are not using the @code{myodbcd.dll} driver (see the item above). @item Start your application and try to get it to fail. @end enumerate Check the @code{MyODBC trace file}, to find out what could be wrong. You should be able to find out the issued queries by searching after the string @code{>mysql_real_query} in the @file{myodbc.log} file. You should also try duplicating the queries in the @code{mysql} monitor or @code{admndemo} to find out if the error is MyODBC or MySQL. If you find out something is wrong, please only send the relevant rows (max 40 rows) to @email{myodbc@@lists.mysql.com}. Please never send the whole MyODBC or ODBC log file! If you are unable to find out what's wrong, the last option is to make an archive (tar or zip) that contains a MyODBC trace file, the ODBC log file, and a README file that explains the problem. You can send this to @uref{ftp://support.mysql.com/pub/mysql/secret/}. Only we at MySQL AB will have access to the files you upload, and we will be very discrete with the data! If you can create a program that also shows this problem, please upload this too! If the program works with some other SQL server, you should make an ODBC log file where you do exactly the same thing in the other SQL server. Remember that the more information you can supply to us, the more likely it is that we can fix the problem! @node C, Cplusplus, ODBC, Clients @section MySQL C API @cindex C API, datatypes @cindex datatypes, C API @menu * C API datatypes:: C API Datatypes * C API function overview:: C API Function Overview * C API functions:: C API Function Descriptions * C Thread functions:: C Thread Functions * C Embedded Server func:: C Embedded Server Function Descriptions * C API problems:: Common questions and problems when using the C API * Building clients:: Building Client Programs * Threaded clients:: How to Make a Threaded Client * libmysqld:: libmysqld, the Embedded MySQL Server Library @end menu C API コードは MySQL とともに配布されます。これは @code{libmysqlclient} ライブラリに含まれ、C プログラムからデータベースへ のアクセスを許します。 MySQL ソースディストリビューション内のクライアントの多くは C で書かれています。C API の使 用法を示す例を探すなら、これらのクライアントを調べてください。 他のクライアント API の多く(Java を除く全て)は、MySQL サーバと の通信にこのライブラリを使用します。そのため、例えば、他のクライアントプ ログラムで使用されるのと同じ環境変数の多くの利点を得ることができます。そ れらはライブラリから参照されるからです。これらの変数のリストについては @ref{Client-Side Scripts} を参照して下さい。 クライアントは最大通信バッファサイズを持ちます。最初に割り当てられるバッ ファのサイズ(16K バイト)は自動的に最大サイズ(デフォルトは 16M)まで増加し ます。バッファサイズは必要に応じて増加するため、単純にデフォルトの最大制 限を増加しても、さらに内部で資源を使用することはありません。このサイズチェッ クは主に間違ったクエリと通信パケットのためのチェックです。 通信バッファは一つの SQL ステートメント(クライアントからサーバへの通信)と、 返されるデータ(サーバからクライアントへの通信)の１レコードを含むのに 十分大きくなくてはいけません。各スレッドの 通信バッファは、任意のレコードやクエリを処理するために、指定された制限まで動的 に増大します。例えば、最大 16M のデータを含む @code{BLOB} 値がある場合、 少なくとも 16M を通信バッファ制限として持つ必要があります(サーバとクライ アントの両方で)。 クライアントのデフォルトの最大値は 16M ですが、サーバの最大値のデフォルトは 1M です。これはサーバ起動時に、@code{max_allowed_packet} パラメータの 値を変更することにより、増やすことが出来ます。 @xref{Server parameters}. MySQL サーバは、各クエリ後に各通信バッファを @code{net_buffer_length} バイトに縮小します。 クライアントでは、接続に割り当てられたバッファのサイズは、接続が閉じられるまで減少しません。 クライアントメモリは接続がクローズされた時に調整されます。 スレッドプログラミングについては、 @xref{Threaded clients}. を参考にしてください。 @node C API datatypes, C API function overview, C, C @subsection C API データ型 @table @code @tindex MYSQL C type @item MYSQL この構造体は一つのデータベース接続のハンドルを表わします。これはほとんど全て の MySQL 関数に使用されます。 @tindex MYSQL_RES C type @item MYSQL_RES この構造体はレコードを返すクエリ(@code{SELECT}, @code{SHOW}, @code{DESCRIBE}, @code{EXPLAIN})の結果を表わ します。クエリから返される情報は、この節の残りでは@strong{結果セット}と呼 ばれます。 @tindex MYSQL_ROW C type @item MYSQL_ROW これはデータの１レコードの安全な型表現です。これは現在バイト文字列の配列として実 装されています。(フィールド値がバイナリデータを含むことがある場合、これを NULL 終端文字列として扱うことはできません。そのような値は内部に NULL バイトを含 むことがあるからです。) @code{mysql_fetch_row()} の呼び出しによりレコードが獲得 されます。 @tindex MYSQL_FIELD C type @item MYSQL_FIELD この構造体はフィールドについての情報、つまりフィールドの名前、型、サイズ 等を含んでいます。このメンバは後でさらに詳細に説明されています。 @code{mysql_fetch_field()} を繰り返し呼び出すことにより、各フィールドの @code{MYSQL_FIELD} 構造体を得ることができます。 フィールド値はこの構造体の一部ではありません; それは @code{MYSQL_ROW} 構造 体に含まれています。 @tindex MYSQL_FIELD_OFFSET C type @item MYSQL_FIELD_OFFSET これは、MySQL フィールドリストへのオフセットの安全な型表現です。 (@code{mysql_field_seek()} で使用されます。)オフセットはレコード内のフィールド 番号で、0 から始まります。 @tindex my_ulonglong C type @tindex my_ulonglong values, printing @item my_ulonglong レコード数と @code{mysql_affected_rows()}, @code{mysql_num_rows()} そして @code{mysql_insert_id()} に使用される型です。 この型は @code{0} から @code{1.84e19} の範囲を与えます。 システムによっては、@code{my_ulonglong} 型の値を表示しようとしても、動作 しないことがあります。この値を表示するには、@code{unsigned long} に変換 し、@code{%lu} 出力書式を使用してください。例: @example printf (Number of rows: %lu\n", (unsigned long) mysql_num_rows(result)); @end example @end table @noindent @code{MYSQL_FIELD} 構造体は次のメンバを含みます: @table @code @item char * name フィールドの名前。null終端文字列。 @item char * table このフィールドを含むテーブルの名前。計算されたフィールドでない場合のみ有 効です。計算されたフィールドでは、@code{table} 値は空文字列です。 @item char * def このフィールドのデフォルト値。null終端文字列。 これは @code{mysql_list_fields()} 使用時にだけ設定されます。 @item enum enum_field_types type フィールドの型。 @code{type} 値は次の一つです: @multitable @columnfractions .35 .55 @item @strong{型の値} @tab @strong{型の意味} @item @code{FIELD_TYPE_TINY} @tab @code{TINYINT} フィールド @item @code{FIELD_TYPE_SHORT} @tab @code{SMALLINT} フィールド @item @code{FIELD_TYPE_LONG} @tab @code{INTEGER} フィールド @item @code{FIELD_TYPE_INT24} @tab @code{MEDIUMINT} フィールド @item @code{FIELD_TYPE_LONGLONG} @tab @code{BIGINT} フィールド @item @code{FIELD_TYPE_DECIMAL} @tab @code{DECIMAL} または @code{NUMERIC} フィールド @item @code{FIELD_TYPE_FLOAT} @tab @code{FLOAT} フィールド @item @code{FIELD_TYPE_DOUBLE} @tab @code{DOUBLE} または @code{REAL} フィールド @item @code{FIELD_TYPE_TIMESTAMP} @tab @code{TIMESTAMP} フィールド @item @code{FIELD_TYPE_DATE} @tab @code{DATE} フィールド @item @code{FIELD_TYPE_TIME} @tab @code{TIME} フィールド @item @code{FIELD_TYPE_DATETIME} @tab @code{DATETIME} フィールド @item @code{FIELD_TYPE_YEAR} @tab @code{YEAR} フィールド @item @code{FIELD_TYPE_STRING} @tab 文字列 (@code{CHAR} または @code{VARCHAR}) フィールド @item @code{FIELD_TYPE_BLOB} @tab @code{BLOB} または @code{TEXT} フィールド (最大長を確定するには @code{max_length} を使用して下さい) @item @code{FIELD_TYPE_SET} @tab @code{SET} フィールド @item @code{FIELD_TYPE_ENUM} @tab @code{ENUM} フィールド @item @code{FIELD_TYPE_NULL} @tab @code{NULL}型 フィールド @item @code{FIELD_TYPE_CHAR} @tab 非推奨; @code{FIELD_TYPE_TINY} を代わりに使用してください @end multitable @code{IS_NUM()} マクロで、フィールドが数値タイプかどうかをテストできます。 フィールドが数値の場合、@code{type} メンバを @code{IS_NUM()} に渡すと TRUE と評価します: @example if (IS_NUM(field->type)) printf("Field is numeric\n"); @end example @item unsigned int length フィールドの幅。これはテーブル定義で指定されたものです。 @item unsigned int max_length 結果セットのフィールドの最大幅(実際の結果セットの中のレコードの最長フィールド値 の長さ)。@code{mysql_store_result()} または @code{mysql_list_fields()} を 使用する場合は、これはフィールドの最大幅になります。 @code{mysql_use_result()} を使用する場合は、この変数の値は 0 になります。 @item unsigned int flags フィールドの種々のビットフラグ。@code{flags} 値は 0 または次のビットの一つ 以上の組み合わせです: @multitable @columnfractions .35 .55 @item @strong{フラグの値} @tab @strong{フラグの意味} @item @code{NOT_NULL_FLAG} @tab フィールドは @code{NULL} にできない @item @code{PRI_KEY_FLAG} @tab フィールドはプライマリキーの一部である @item @code{UNIQUE_KEY_FLAG} @tab フィールドはユニークキーの一部である @item @code{MULTIPLE_KEY_FLAG} @tab フィールドは非ユニークキーの一部である @item @code{UNSIGNED_FLAG} @tab フィールドは @code{UNSIGNED} 属性を持っている @item @code{ZEROFILL_FLAG} @tab フィールドは @code{ZEROFILL} 属性を持っている @item @code{BINARY_FLAG} @tab フィールドは @code{BINARY} 属性を持っている @item @code{AUTO_INCREMENT_FLAG} @tab フィールドは @code{AUTO_INCREMENT} 属性を持っている @item @code{ENUM_FLAG} @tab フィールドは @code{ENUM} である (非推奨) @item @code{SET_FLAG} @tab Field is a @code{SET} (deprecated) @item @code{BLOB_FLAG} @tab フィールドは @code{BLOB} または @code{TEXT} である (非推奨) @item @code{TIMESTAMP_FLAG} @tab フィールドは @code{TIMESTAMP} である (非推奨) @end multitable @code{BLOB_FLAG}, @code{ENUM_FLAG}, @code{SET_FLAG}, @code{TIMESTAMP_FLAG} の使用は推奨さ れません。これらは型の属性ではなくフィールドの型を示すからです。代わり に @code{field->type} を @code{FIELD_TYPE_BLOB}, @code{FIELD_TYPE_ENUM}, @code{FIELD_TYPE_SET}, @code{FIELD_TYPE_TIMESTAMP} に対してテストする方をお勧めします。 @noindent 次の例は @code{flags} 値の典型的な使用を示しています: @example if (field->flags & NOT_NULL_FLAG) printf("Field can't be null\n"); @end example @code{flags} 値の真偽状態を調べるために、次の便利なマクロを使用でき ます: @multitable @columnfractions .25 .55 @item @code{IS_NOT_NULL(flags)} @tab このフィールドが @code{NOT NULL} として定義されていれば真 @item @code{IS_PRI_KEY(flags)} @tab このフィールドがプライマリキーならば真 @item @code{IS_BLOB(flags)} @tab このフィールドが @code{BLOB} または @code{TEXT} ならば真 (非推奨; 代わりに @code{field->type} をテストして下さい) @end multitable @item unsigned int decimals 数値フィールドの小数部桁数。 @end table @cindex C API, functions @cindex functions, C API @node C API function overview, C API functions, C API datatypes, C @subsection C API 関数概要 C API には次に一覧された関数が存在します。これらの関数は次の節でかな り詳細に説明されています。 @xref{C API functions}。 @multitable @columnfractions .32 .68 @item @strong{Function} @tab @strong{Description} @item @strong{mysql_affected_rows()} @tab 最後の @code{UPDATE}, @code{DELETE}, @code{INSERT} クエリによって変更／削 除／挿入されたレコード数を返します。 @item @strong{mysql_change_user()} @tab 接続中ののユーザとデータベースを変更します。 @item @code{mysql_character_set_name()} @tab 接続のデフォルト文字セットの名前を返します。 @item @strong{mysql_close()} @tab サーバ接続をクローズします。 @item @strong{mysql_connect()} @tab MySQL サーバに接続します。この関数は推奨されません; 代わりに @code{mysql_real_connect()} を使用してください。 @item @strong{mysql_create_db()} @tab データベースを生成します。この関数は推奨されません; 代わりに SQL コマン ド @code{CREATE DATABASE} を使用してください。 @item @strong{mysql_data_seek()} @tab クエリ結果セット中の任意のレコードにシークします。 @item @strong{mysql_debug()} @tab 与えられた文字列で @code{DBUG_PUSH} を行ないます。 @item @strong{mysql_drop_db()} @tab データベースを破棄します。この関数は推奨されません; 代わりに SQL コマン ド @code{DROP DATABASE} を使用してください。 @item @strong{mysql_dump_debug_info()} @tab サーバに、デバッグ情報をログに書き出させます。 @item @strong{mysql_eof()} @tab 結果セットの最後のレコードが読まれたかどうかを判定します。この関数は推奨されませ ん; 代わりに @code{mysql_errno()} または @code{mysql_error()} を使用して下 さい。 @item @strong{mysql_errno()} @tab 最後の MySQL 関数からのエラー番号を返します。 @item @strong{mysql_error()} @tab 最後の MySQL 関数からのエラーメッセージを返します。 @item @strong{mysql_escape_string()} @tab SQL ステートメント内で使用するために文字列中の特殊文字をエスケープします。 @item @strong{mysql_fetch_field()} @tab テーブルの次のフィールドの型を返します。 @item @strong{mysql_fetch_field_direct()} @tab テーブルの、番号で指定されたフィールドの型を返します。 @item @strong{mysql_fetch_fields()} @tab 全てのフィールド構造体の配列を返します。 @item @strong{mysql_fetch_lengths()} @tab 現在のレコード中の全てのフィールドの長さを返します。 @item @strong{mysql_fetch_row()} @tab 結果セットから次のレコードを取り出します。 @item @strong{mysql_field_seek()} @tab 指定されたフィールド上にフィールドカーソルを置きます。 @item @strong{mysql_field_count()} @tab 最後のクエリの結果のフィールドの数を返します。 @item @strong{mysql_field_tell()} @tab 最後の @code{mysql_fetch_field()} で使用されたフィールドカーソルの位置を返 します。 @item @strong{mysql_free_result()} @tab 結果セットによって使用されたメモリを解放します。 @item @strong{mysql_get_client_info()} @tab クライアントバージョン情報を返します。 @item @strong{mysql_get_host_info()} @tab 接続を説明する文字列を返します。 @item @code{mysql_get_server_version()} @tab Returns version number of server as an integer (new in 4.1). @item @strong{mysql_get_proto_info()} @tab 接続に使用されるプロトコルバージョンを返します。 @item @strong{mysql_get_server_info()} @tab サーバのバージョン番号を返します。 @item @strong{mysql_info()} @tab 最後に実行されたクエリについての情報を返します。 @item @strong{mysql_init()} @tab @code{MYSQL} 構造体を獲得または初期化します。 @item @strong{mysql_insert_id()} @tab @code{AUTO_INCREMENT} フィールドに最後に生成された ID を返します。 @item @strong{mysql_kill()} @tab 指定されたスレッドを殺します。 @item @strong{mysql_list_dbs()} @tab 簡易正規表現に適合するデータベース名を返します。 @item @strong{mysql_list_fields()} @tab 簡易正規表現に適合するフィールド名を返します。 @item @strong{mysql_list_processes()} @tab 現在のサーバスレッドのリストを返します。 @item @strong{mysql_list_tables()} @tab 簡易正規表現に適合するテーブル名を返します。 @item @strong{mysql_num_fields()} @tab 結果セット中のフィールド数を返します。 @item @strong{mysql_num_rows()} @tab 結果セット中のレコード数を返します。 @item @strong{mysql_options()} @tab @code{mysql_connect()} のための接続オプションを設定します。 @item @strong{mysql_ping()} @tab サーバへの接続が動作しているかどうかをチェックします。 必要であれば再接続します。 @item @strong{mysql_query()} @tab NULL 終端文字列として記述された SQL クエリを実行します。 @item @strong{mysql_real_connect()} @tab MySQL サーバに接続します。 @item @strong{mysql_real_escape_string()} @tab Escapes special characters in a string for use in a SQL statement, taking into account the current charset of the connection. @item @strong{mysql_real_query()} @tab 数えられた文字列として記述された SQL クエリを実行します。 @item @strong{mysql_reload()} @tab 権限テーブルを再読み込みするようにサーバに指示します。 @item @strong{mysql_row_seek()} @tab 結果セット内のあるレコードへシークします。@code{mysql_row_tell()} から返される値を 使用します。 @item @strong{mysql_row_tell()} @tab レコードカーソルの位置を返します。 @item @strong{mysql_select_db()} @tab データベースを選択します。 @item @strong{mysql_shutdown()} @tab データベースサーバをシャットダウンします。 @item @strong{mysql_stat()} @tab 文字列でサーバ状態を返します。 @item @strong{mysql_store_result()} @tab クライアントに完全な結果セットを取り出します。 @item @strong{mysql_thread_id()} @tab 現在のスレッド ID を返します。 @item @strong{mysql_thread_save()} @tab Returns 1 if the clients are compiled as thread-safe. @item @strong{mysql_use_result()} @tab 各レコードの動的結果セットを初期化します。 @end multitable サーバへ接続するには、接続ハンドラを初期化するために @code{mysql_init()} を呼びだし、それから @code{mysql_real_connect()} をそのハンドラで呼びだし ます (ホスト名、ユーザ名、パスワードのような他の情報に加えて)。 Upon connection, @code{mysql_real_connect()} sets the @code{reconnect} flag (part of the MYSQL structure) to a value of @code{1}. This flag indicates, in the event that a query cannot be performed because of a lost connection, to try reconnecting to the server before giving up. その接続で の処理が終了した時は、接続を終了させるために @code{mysql_close()} を呼びだ します。 接続が有効な間は、クライアントは @code{mysql_query()} または @code{mysql_real_query()} を使用して SQL クエリをサーバに送信できます。こ の２つの違いは、@code{mysql_query()} は NULL終端文字列としてクエリが記述さ れることを期待するのに対し、@code{mysql_real_query()} は数えられた文字列を 期待することです。文字列がバイナリデータ(NULバイトを含みことがある)を含む 場合は、@code{mysql_real_query()} を使用する必要があります。 非@code{SELECT} クエリ(例えば、@code{INSERT}, @code{UPDATE}, @code{DELETE})では、どれくらいのレコードが変更(影響)されたかを @code{mysql_affected_rows()} を呼び出すことで見つけ出すことができます。 @code{SELECT} クエリでは、選択されたレコードを結果セットとして取り出します。 (注意: いくつかのステートメントは、レコードを返すという点で @code{SELECT}に似ています。それは @code{SHOW}, @code{DESCRIBE}, @code{EXPLAIN} です。これらは @code{SELECT} ステートメントと同じ方法で扱わ れるべきです。) クライアントが結果セットを処理するには２つの方法があります。一つ目は、 @code{mysql_store_result()} を呼び出すことで、結果セット全体を一度にすべて 取り出すことです。この関数はサーバからクエリによって返されるすべてのレコー ドを取得し、それをクライアントに格納します。二つ目は、 @code{mysql_use_result()} を呼び出すことで、レコードごとの結果セット取り出 しを初期化することです。この関数は取り出しを初期化しますが、実際にはサーバ から何のレコードも得ません。 どちらの場合でも、@code{mysql_fetch_row()} を呼び出してレコードにアクセス します。@code{mysql_store_result()} では、@code{mysql_fetch_row()} は既に サーバから取得してあるレコードにアクセスします。 @code{mysql_use_result()} では、@code{mysql_fetch_row()} は実際にサーバか らレコードを取り出します。各レコードのデータ値のサイズについての情報は @code{mysql_fetch_lengths()} を呼び出すことで得られます。 結果セットでの処理が終った後は、@code{mysql_free_result()} を呼び出し、そ れが使用していたメモリを解放して下さい。 この２つの取り出し機構は相補的なものです。クライアントプログラムは、必要に よってもっとも適切なアプローチを選択すべきです。慣例的に、クライアントは一 般に @code{mysql_store_result()} を使用する傾向にあります。 @code{mysql_store_result()} の利点は、すべてのレコードをクライアントに取っ て来るため、連続してレコードをアクセスできるだけでなく、結果セット中の現在 のレコード位置を変更するために、@code{mysql_data_seek()} や @code{mysql_row_seek()} を使用して、結果セットの中を後や前に移動することが できます。また、@code{mysql_num_rows()} を呼び出すことで、レコード数を見つ けることもできます。一方、@code{mysql_store_result()} の必要メモリは、大き な結果セットではとても高く、out-of-memory 状態に遭遇する可能性が高くなりま す。 @code{mysql_use_result()} の利点は、一度に一つのレコードだけを保持するため、 クライアントが結果セットに要求するメモリが少ないことです（そして、割当のオー バーヘッドも少ないので、@code{mysql_use_result()} はより速くなります）。不 利な点は、サーバの拘束を避けるため、各レコードを素早く処理する必要があるこ と、結果セット中でレコードのランダムアクセスができないこと（レコードを順番 にアクセスすることしかできません）、そして、すべてのレコードを取り出さない 限り、結果セット中にいくつのレコードがあるかを知ることができないことです。 さらに、あなたが探している情報を、検索の途中で見つけることができて、問題が 解決したとしても、すべてのレコードを取り出さ@strong{なければなりません}。 API はクライアントがクエリが @code{SELECT} であるかどうかを知ることなしに、 （必要時だけレコードを取り出す）クエリに適切に応答できるようにします。 それぞれの @code{mysql_query()}（または @code{mysql_real_query()}）の後で、 @code{mysql_store_result()} を呼び出すことで、これが可能です。結果セットの 呼び出しが成功すると、クエリは @code{SELECT} であり、レコードを読むことが できます。結果セット呼び出しが失敗した場合は、結果が実際に期待されたもので あるかどうかを確定するために、@code{mysql_field_count()} を呼び出してくだ さい。@code{mysql_field_count()} が 0 を返す場合は、クエリはデータを返しま せん（クエリが @code{INSERT}, @code{UPDATE}, @code{DELETE} 等であることを 示します）。つまりレコードが返ることを期待できません。 @code{mysql_field_count()} が 0 でない場合は、クエリはレコードを返すべきな のに、返さなかったということです。これはクエリが @code{SELECT} で失敗した ということを示します。これをどのように行なうことができるかの例は、 @code{mysql_field_count()} の説明を参照してください。 @code{mysql_store_result()} と @code{mysql_use_result()} はどちらも、結果 セットを作るフィールドについての情報（フィールドの数、その名前や型など）を 獲得することができます。@code{mysql_fetch_field()} を繰り返し呼び出すこと で順番に、または、@code{mysql_fetch_field_direct()} を呼び出すことでレコー ド内のフィールド番号で、レコード内のフィールド情報にアクセスすることができ ます。現在のフィールドカーソル位置は @code{mysql_field_seek()} を呼び出す ことで変更できます。フィールドカーソルの設定は、その後の @code{mysql_fetch_field()} 呼び出しに影響します。 @code{mysql_fetch_fields()} を呼び出すことで、一度にすべてのフィールドの情 報を得ることもできます。 エラーの検出、報告については、@code{mysql_errno()} と @code{mysql_error()} 関数の方法によって、MySQL はエラー情報へのア クセスを提供します。これらは、最後に呼び出された成功または失敗し得る関数に ついてのエラーコードとエラーメッセージを返し、エラーがいつ何で発生したかを 確定することができます。 @node C API functions, C Thread functions, C API function overview, C @subsection C API 関数説明 @menu * mysql_affected_rows:: @code{mysql_affected_rows()} * mysql_change_user:: @code{mysql_change_user()} * mysql_character_set_name:: @code{mysql_character_set_name()} * mysql_close:: @code{mysql_close()} * mysql_connect:: @code{mysql_connect()} * mysql_create_db:: @code{mysql_create_db()} * mysql_data_seek:: @code{mysql_data_seek()} * mysql_debug:: @code{mysql_debug()} * mysql_drop_db:: @code{mysql_drop_db()} * mysql_dump_debug_info:: @code{mysql_dump_debug_info()} * mysql_eof:: @code{mysql_eof()} * mysql_errno:: @code{mysql_errno()} * mysql_error:: @code{mysql_error()} * mysql_escape_string:: @code{mysql_escape_string()} * mysql_fetch_field:: @code{mysql_fetch_field()} * mysql_fetch_fields:: @code{mysql_fetch_fields()} * mysql_fetch_field_direct:: @code{mysql_fetch_field_direct()} * mysql_fetch_lengths:: @code{mysql_fetch_lengths()} * mysql_fetch_row:: @code{mysql_fetch_row()} * mysql_field_count:: @code{mysql_field_count()} * mysql_field_seek:: @code{mysql_field_seek()} * mysql_field_tell:: @code{mysql_field_tell()} * mysql_free_result:: @code{mysql_free_result()} * mysql_get_client_info:: @code{mysql_get_client_info()} * mysql_get_server_version:: @code{mysql_get_server_version()} * mysql_get_host_info:: @code{mysql_get_host_info()} * mysql_get_proto_info:: @code{mysql_get_proto_info()} * mysql_get_server_info:: @code{mysql_get_server_info()} * mysql_info:: @code{mysql_info()} * mysql_init:: @code{mysql_init()} * mysql_insert_id:: @code{mysql_insert_id()} * mysql_kill:: @code{mysql_kill()} * mysql_list_dbs:: @code{mysql_list_dbs()} * mysql_list_fields:: @code{mysql_list_fields()} * mysql_list_processes:: @code{mysql_list_processes()} * mysql_list_tables:: @code{mysql_list_tables()} * mysql_num_fields:: @code{mysql_num_fields()} * mysql_num_rows:: @code{mysql_num_rows()} * mysql_options:: @code{mysql_options()} * mysql_ping:: @code{mysql_ping()} * mysql_query:: @code{mysql_query()} * mysql_real_connect:: @code{mysql_real_connect()} * mysql_real_escape_string:: @code{mysql_real_escape_string()} * mysql_real_query:: @code{mysql_real_query()} * mysql_reload:: @code{mysql_reload()} * mysql_row_seek:: @code{mysql_row_seek()} * mysql_row_tell:: @code{mysql_row_tell()} * mysql_select_db:: @code{mysql_select_db()} * mysql_shutdown:: @code{mysql_shutdown()} * mysql_stat:: @code{mysql_stat()} * mysql_store_result:: @code{mysql_store_result()} * mysql_thread_id:: @code{mysql_thread_id()} * mysql_use_result:: @code{mysql_use_result()} @end menu 以下の説明では、@code{NULL} の引数または戻り値は C プログラミング言語で の @code{NULL} を意味します。MySQL @code{NULL} 値ではありません。 関数は通常ポインタか整数の値を返します。しかし関数説明に記述がある場合、 ポインタを返す関数は、成功を示すために非 @code{NULL} 値を返し、エラーを示すた めに @code{NULL} を返します。整数を返す関数は、成功を示すために 0 を返し、 エラーを示すために非0を返します。``非0'' は関数説明が他に述べていない限 り、その意味になることに注意してください; 関数説明が他に述べている場合、 これらに対して 0 以外の固有の値をテストしないでください: @example if (result) /* 正しい */ ... error ... if (result < 0) /* 間違い */ ... error ... if (result == -1) /* 間違い */ ... error ... @end example 関数がエラーを返すとき、関数説明の @strong{エラー} 節が起り得るエラーの 種類を一覧しています。@code{mysql_errno()} の呼び出しによってどれが発生 したかを見つけ出すことができます。エラーを表現する文字列は @code{mysql_error()} の呼び出しによって得られます。 @findex @code{mysql_affected_rows()} @node mysql_affected_rows, mysql_change_user, C API functions, C API functions @subsubsection @code{mysql_affected_rows()} @code{my_ulonglong mysql_affected_rows(MYSQL *mysql)} @subsubheading 説明 最後の @code{UPDATE} によって変更されたレコード数、または、@code{DELETE} によって削除されたレコード数、@code{INSERT} によって挿入されたレコード数を 返します。@code{UPDATE}, @code{DELETE}, @code{INSERT} ステートメントでの @code{mysql_query()} 直後に呼び出します。@code{SELECT} ステートメントでは、 @code{mysql_affected_rows()} は @code{mysql_num_rows()} に似た動きをします。 @subsubheading 戻り値 0 より大きい整数は影響された行数または取り出された行数を示します。0 は @code{UPDATE} ステートメントで更新されたレコードがないこと、またはクエリの @code{WHERE} 節に適合したレコードがないこと、またはまだなんのクエリも実行 していないことを示します。-1 はクエリがエラーを返したこと、あるいは @code{SELECT} クエリで、@code{mysql_affected_rows()} が @code{mysql_store_result()} 呼び出しよりも先に呼び出されたことを揣摩します。 @subsubheading エラー 無し。 @subsubheading 例 @example mysql_query(&mysql,"UPDATE products SET cost=cost*1.25 WHERE group=10"); printf("%ld products updated",(long) mysql_affected_rows(&mysql)); @end example If one specifies the flag @code{CLIENT_FOUND_ROWS} when connecting to @code{mysqld}, @code{mysql_affected_rows()} will return the number of rows matched by the @code{WHERE} statement for @code{UPDATE} statements. Note that when one uses a @code{REPLACE} command, @code{mysql_affected_rows()} will return 2 if the new row replaced and old row. This is because in this case one row was inserted after the duplicate was deleted. @findex @code{mysql_change_user()} @node mysql_change_user, mysql_character_set_name, mysql_affected_rows, C API functions @subsubsection @code{mysql_change_user()} @code{my_bool mysql_change_user(MYSQL *mysql, const char *user, const char *password, const char *db)} @subsubheading 説明 ユーザを変更し、@code{mysql} で示された接続上で、@code{db} で示されたデー タベースがデフォルト（現在の）データベースになります。その後のクエリでは、 明示的なデータベースの指定を含んでいないテーブル参照について、このデータベー スがデフォルトになります。 この関数は MySQL 3.23.3 で導入されました。 @code{mysql_change_user()} は接続されたユーザが認証されない場合、またはデー タベースを使用する権限を持っていない場合に失敗します。この場合、ユーザとデー タベースは変更されません。 デフォルトデータベースを持ちたくない場合、@code{db} パラメータを @code{NULL} に設定できます。 @subsubheading 戻り値 成功時 0。エラーが発生した場合は非0。 @subsubheading エラー @code{mysql_real_connect()} から得られるものと同じです。 @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @item ER_UNKNOWN_COM_ERROR MySQL サーバはこのコマンドを実装していない（おそらく古いサーバ）。 @item ER_ACCESS_DENIED_ERROR ユーザまたはパスワードが間違っている。 @item ER_BAD_DB_ERROR データベースが存在しない。 @item ER_DBACCESS_DENIED_ERROR ユーザがデータベースへのアクセス権を持っていない。 @item ER_WRONG_DB_NAME データベース名が長過ぎる。 @end table @subsubheading 例 @example if (mysql_change_user(&mysql, "user", "password", "new_database")) @{ fprintf(stderr, "Failed to change user. Error: %s\n", mysql_error(&mysql)); @} @end example @findex @code{mysql_character_set_name()} @node mysql_character_set_name, mysql_close, mysql_change_user, C API functions @subsubsection @code{mysql_character_set_name()} @code{const char *mysql_character_set_name(MYSQL *mysql)} @subsubheading Description Returns the default character set for the current connection. Starting from MySQL 4.0.6 this command will always @code{ROLLBACK} any active transactions, close all temporary tables, unlock all locked tables and reset the state as if one had done a new connect. This will happen even if the user didn't change. @subsubheading Return Values The default character set @subsubheading Errors None. @findex @code{mysql_close()} @node mysql_close, mysql_connect, mysql_character_set_name, C API functions @subsubsection @code{mysql_close()} @code{void mysql_close(MYSQL *mysql)} @subsubheading 説明 前にオープンされた接続をクローズします。ハンドルが @code{mysql_init()} ま たは @code{mysql_connect()} で自動的に割り当てられた場合、 @code{mysql_close()} は @code{mysql} で示される接続ハンドルの解放も行ない ます。 @subsubheading 戻り値 無し。 @subsubheading エラー 無し。 @findex @code{mysql_connect()} @node mysql_connect, mysql_create_db, mysql_close, C API functions @subsubsection @code{mysql_connect()} @code{MYSQL *mysql_connect(MYSQL *mysql, const char *host, const char *user, const char *passwd)} @subsubheading 説明 この関数は推奨されません。代わりに @code{mysql_real_connect()} の使用を お勧めします。 @code{mysql_connect()} は @code{host} 上で動作している MySQL デー タベースエンジンへの接続の確立を試みます。@code{mysql_get_client_info()} を除く他のすべての API 関数を実行する前に@code{mysql_connect()} が成功終了 している必要があります。 パラメータの意味は @code{mysql_real_connect()} の対応するパラメータと同じですが、 接続パラメータは @code{NULL} にできることが異なります。この場合 C API は接 続構造体に自動的にメモリを割り当て、@code{mysql_close()} 呼び出し時にそれ を解放します。このアプローチの不利な点は接続が失敗した場合にエラーメッセー ジを取り出すことができないことです。（@code{mysql_errno()} または @code{mysql_error()} からエラー情報を得るには、正しい @code{MYSQL} ポイン タを提供する必要があります。） @subsubheading 戻り値 @code{mysql_real_connect()} と同じ @subsubheading エラー @code{mysql_real_connect()} と同じ @findex @code{mysql_create_db()} @node mysql_create_db, mysql_data_seek, mysql_connect, C API functions @subsubsection @code{mysql_create_db()} @code{int mysql_create_db(MYSQL *mysql, const char *db)} @subsubheading 説明 @code{db} 引数によって指定されたデータベースを作成します。 この関数は推奨されません。代わりに @code{mysql_query()} を使って、SQL @code{CREATE DATABASE} ステートメントを発行することをお勧めします。 @subsubheading 戻り値 データベースの作成が成功した場合は0。エラーが発生した場合は非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @subsubheading 例 @example if(mysql_create_db(&mysql, "my_database")) @{ fprintf(stderr, "Failed to create new database. Error: %s\n", mysql_error(&mysql)); @} @end example @findex @code{mysql_data_seek()} @node mysql_data_seek, mysql_debug, mysql_create_db, C API functions @subsubsection @code{mysql_data_seek()} @code{void mysql_data_seek(MYSQL_RES *result, my_ulonglong offset)} @subsubheading 説明 クエリ結果セット中の任意のレコードにシークします。これは、結果セット構造体 がクエリのすべての結果を持っていることを要求します。そのため、 @code{mysql_data_seek()} は @code{mysql_store_result()} と共にだけ使用され、 @code{mysql_use_result()} と共には使用できません。 オフセットの値は @code{0} から @code{mysql_num_rows(result)-1} でなくては なりません。 @subsubheading 戻り値 無し。 @subsubheading エラー 無し。 @findex @code{mysql_debug()} @node mysql_debug, mysql_drop_db, mysql_data_seek, C API functions @subsubsection @code{mysql_debug()} @code{void mysql_debug(const char *debug)} @subsubheading 説明 与えられた文字列で @code{DBUG_PUSH} を行ないます。@code{mysql_debug()} は Fred Fish が作成した debug library を使用します。この関数を使用するためには、デバッ グをサポートするように、クライアントライブラリをコンパイルする必要があり ます。 @xref{Debugging server}. @xref{Debugging client}. @subsubheading 戻り値 無し。 @subsubheading エラー 無し。 @subsubheading 例 次に示した呼び出しは、クライアントライブラリが、クライアントマシン上の @file{/tmp/client.trace} にトレースファイルを生成します: @example mysql_debug("d:t:O,/tmp/client.trace"); @end example @findex @code{mysql_drop_db()} @node mysql_drop_db, mysql_dump_debug_info, mysql_debug, C API functions @subsubsection @code{mysql_drop_db()} @code{int mysql_drop_db(MYSQL *mysql, const char *db)} @subsubheading 説明 @code{db} 引数によって指定されたデータベースを破棄します。 この関数は推奨されません。代わりに @code{mysql_query()} を使って、SQL @code{DROP DATABASE} ステートメントを発行することをお勧めします。 @subsubheading 戻り値 データベースの破棄が成功した場合は0。エラーが発生した場合は非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @subsubheading 例 @example if(mysql_drop_db(&mysql, "my_database")) fprintf(stderr, "Failed to drop the database: Error: %s\n", mysql_error(&mysql)); @end example @findex @code{mysql_dump_debug_info()} @node mysql_dump_debug_info, mysql_eof, mysql_drop_db, C API functions @subsubsection @code{mysql_dump_debug_info()} @code{int mysql_dump_debug_info(MYSQL *mysql)} @subsubheading 説明 いくつかのデバッグ情報をログにダンプするようにサーバに指示します。この動 作をするためには、接続されたユーザが @code{SUPER} 権限 (version4.0.2以上。未満は@code{PROCESS} 権)を持っていなけ ればなりません。 @subsubheading 戻り値 コマンドが成功した場合は0。コマンドが失敗した場合は非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_eof()} @node mysql_eof, mysql_errno, mysql_dump_debug_info, C API functions @subsubsection @code{mysql_eof()} @code{my_bool mysql_eof(MYSQL_RES *result)} @subsubheading 説明 この関数は推奨されません。@code{mysql_errno()} か @code{mysql_error()} が 代わりに使用できます。 @code{mysql_eof()} は結果セットの最後のレコードが読まれたかどうかを調べま す。 @code{mysql_store_result()} の呼び出しが成功して、結果セットを入手した場合、 クライアントは一つのオペレーションですべてのセットを受け取ります。この場合、 @code{mysql_fetch_row()} から返される @code{NULL} は、常に結果セットの終端 に達したことを意味し、@code{mysql_eof()} を呼ぶ必要はありません。 hen used with @code{mysql_store_result()}, @code{mysql_eof()} will always return true. 一方、結果セット取り出しの初期化のために @code{mysql_use_result()} を使用 する場合、セットのレコードは @code{mysql_fetch_row()} を繰り返し呼ぶことに より、ひとつずつサーバから獲得されます。この処理中に接続上でエラーが発生し 得るため、@code{mysql_fetch_row()} からの戻り値 @code{NULL} は、通常必ずし も結果セットの終端に達したことを意味しません。この場合 @code{mysql_eof()} を使用して、何が起こったかを検出できます。結果セットの 終端に達した場合は @code{mysql_eof()} は非0値を返し、エラーが発生した場合 は 0 を返します。 歴史的に @code{mysql_eof()} は標準 MySQL エラー関数 @code{mysql_errno()} と @code{mysql_error()} 以前に遡ります。これらのエラー 関数は同じ情報を提供するので、これらの使用が @code{mysql_eof()} よりも好ま れます。@code{mysql_eof()} は現在推奨されません。（実際、これらは多くの情 報を提供します。エラー関数はエラーが発生した時のエラーの理由を示しますが、 @code{mysql_eof()} は真偽値だけを返します。） @subsubheading 戻り値 エラーが発生しなかった場合は0。結果セットの終端に達した場合は非0。 @subsubheading エラー 無し。 @subsubheading 例 次の例は @code{mysql_eof} の使用方法を示します: @example mysql_query(&mysql,"SELECT * FROM some_table"); result = mysql_use_result(&mysql); while((row = mysql_fetch_row(result))) @{ // do something with data @} if(!mysql_eof(result)) // mysql_fetch_row() failed due to an error @{ fprintf(stderr, "Error: %s\n", mysql_error(&mysql)); @} @end example しかし、標準 MySQL エラー関数で同じ効果を得ることができます: @example mysql_query(&mysql,"SELECT * FROM some_table"); result = mysql_use_result(&mysql); while((row = mysql_fetch_row(result))) @{ // do something with data @} if(mysql_errno(&mysql)) // mysql_fetch_row() failed due to an error @{ fprintf(stderr, "Error: %s\n", mysql_error(&mysql)); @} @end example @findex @code{mysql_errno()} @node mysql_errno, mysql_error, mysql_eof, C API functions @subsubsection @code{mysql_errno()} @code{unsigned int mysql_errno(MYSQL *mysql)} @subsubheading 説明 @code{mysql} によって指定された接続上で、最後に呼び出された API 関数の成否のエラーコー ドを返します。戻り値0はエラーが発生しなかったことを意味します。クライア ントエラーメッセージ番号は @file{errmsg.h} にリストされています。サーバ エラーメッセージ番号は @file{mysqld_error.h} にリストされています。 In the MySQL source distribution you can find a complete list of error messages and error numbers in the file @file{Docs/mysqld_error.txt}. @subsubheading 戻り値: エラーコード値。エラーが発生していない場合は0。 @subsubheading エラー 無し。 @findex @code{mysql_error()} @node mysql_error, mysql_escape_string, mysql_errno, C API functions @subsubsection @code{mysql_error()} @code{char *mysql_error(MYSQL *mysql)} @subsubheading 説明 @code{mysql} によって指定された接続上で、 @code{mysql_error()} は 最後に呼び出された API 関数の成否を、エラーメッセージとして返します。 エラー発生しなかった場合は空文字列 (@code{""}) が返されます。 これは次の２つのテストが同じであることを意味します: @example if(mysql_errno(&mysql)) @{ // an error occurred @} if(mysql_error(&mysql)[0] != '\0') @{ // an error occurred @} @end example クライアントエラーメッセージの言語は MySQL クラ イアントライブラリの再コンパイルで変更できます。現在はいくつかの言語で書かれた クライアントエラーメッセージを選択できます。 @xref{Languages}. @subsubheading 戻り値 エラーを表わす文字列。 エラーが発生していない場合は空文字列。 @subsubheading エラー 無し。 @findex @code{mysql_escape_string()} @node mysql_escape_string, mysql_fetch_field, mysql_error, C API functions @subsubsection @code{mysql_escape_string()} You should use @code{mysql_real_escape_string()} instead! This function is identical to @code{mysql_real_escape_string()} except that @code{mysql_real_escape_string()} takes a connection handler as its first argument and escapes the string according to the current character set. @code{mysql_escape_string()} does not take a connection argument and does not respect the current charset setting. @findex @code{mysql_fetch_field()} @node mysql_fetch_field, mysql_fetch_fields, mysql_escape_string, C API functions @subsubsection @code{mysql_fetch_field()} @code{MYSQL_FIELD *mysql_fetch_field(MYSQL_RES *result)} @subsubheading 説明 結果セットの一つのフィールドの定義を @code{MYSQL_FIELD} 構造体として返しま す。結果セット内の全てのフィールドについて情報を取り出すには、この関数を繰 り返し呼んでください。@code{mysql_fetch_field()} はフィールドが残っていな いと @code{NULL} を返します。 @code{mysql_fetch_field()} は、新しい @code{SELECT} クエリを実行するたびに、 最初のフィールドについての情報を返すようにリセットされます。 @code{mysql_fetch_field()} で返されるフィールドは @code{mysql_field_seek()} の呼び出しにも影響をうけます。 テーブルを @code{SELECT} するために @code{mysql_query()} を呼び、しかしま だ @code{mysql_store_result()} を呼んでいない場合、 @code{mysql_fetch_field()} を @code{BLOB} フィールドの長さの問い合わせに使 用すると、MySQL はデフォルトの blob 長 (8K bytes) を返します。 (8K サイズになるのは、MySQL は @code{BLOB} の最大長を知らないから です。これはいつかコンフィグ可能になるべきです。) 一度結果セットを取り出せ ば、@code{field->max_length} は指定したクエリ内でのこのフィールドの最大値 の長さを含みます。 @subsubheading 戻り値 現在のフィールドの @code{MYSQL_FIELD} 構造体。フィールドが残っていない場合は @code{NULL}。 @subsubheading エラー 無し。 @subsubheading 例 @example MYSQL_FIELD *field; while((field = mysql_fetch_field(result))) @{ printf("field name %s\n", field->name); @} @end example @findex @code{mysql_fetch_fields()} @node mysql_fetch_fields, mysql_fetch_field_direct, mysql_fetch_field, C API functions @subsubsection @code{mysql_fetch_fields()} @code{MYSQL_FIELD *mysql_fetch_fields(MYSQL_RES *result)} @subsubheading 説明 結果セットのすべての @code{MYSQL_FIELD} 構造体の配列を返します。各構造体は 結果セットの一つのフィールドのフィールド定義を提供します。 @subsubheading 戻り値 結果セットの全ての項目の @code{MYSQL_FIELD} 構造体の配列。 @subsubheading エラー 無し。 @subsubheading 例 @example unsigned int num_fields; unsigned int i; MYSQL_FIELD *fields; num_fields = mysql_num_fields(result); fields = mysql_fetch_fields(result); for(i = 0; i < num_fields; i++) @{ printf("Field %u is %s\n", i, fields[i].name); @} @end example @findex @code{mysql_fetch_field_direct()} @node mysql_fetch_field_direct, mysql_fetch_lengths, mysql_fetch_fields, C API functions @subsubsection @code{mysql_fetch_field_direct()} @code{MYSQL_FIELD *mysql_fetch_field_direct(MYSQL_RES *result, unsigned int fieldnr)} @subsubheading 説明 結果セット中のフィールドを示すフィールド番号 @code{fieldnr} が与えられ、そ のフィールドのフィールド定義を @code{MYSQL_FIELD} 構造体として返します。こ の関数は任意のフィールドについての定義を取り出すことに使用できます。 @code{fieldnr} の値は 0 から @code{mysql_num_fields(result)-1} の範囲にす べきです。 @subsubheading 戻り値 指定されたフィールドの @code{MYSQL_FIELD} 構造体。 @subsubheading エラー 無し。 @subsubheading 例 @example unsigned int num_fields; unsigned int i; MYSQL_FIELD *field; num_fields = mysql_num_fields(result); for(i = 0; i < num_fields; i++) @{ field = mysql_fetch_field_direct(result, i); printf("Field %u is %s\n", i, field->name); @} @end example @findex @code{mysql_fetch_lengths()} @node mysql_fetch_lengths, mysql_fetch_row, mysql_fetch_field_direct, C API functions @subsubsection @code{mysql_fetch_lengths()} @code{unsigned long *mysql_fetch_lengths(MYSQL_RES *result)} @subsubheading 説明 結果セット中の現在のレコードのフィールドの長さを返します。フィールドの値をコピーする場合、 この長さ情報は最適化にも有用です。@code{strlen()} の呼び出しを回避できる ためです。 さらに、結果セットがバイナリデータを持つ場合は、データのサイズを特定するためにこの関数を@strong{使わなければなりません}。 なぜなら @code{strlen()} は NULL 文字を含むフィールドについての結果を正しく返さないからです。 空フィールドの長さと @code{NULL} 値を含むフィールドの長さは 0 です。この２ つのケースを区別する方法については、@code{mysql_fetch_row()} の説明を参照 して下さい。 @subsubheading 戻り値 各フィールドのサイズ (終端 NUL 文字は含みません)を提供する unsigned long 整数の配列。 エラーが発生した場合は @code{NULL}。 @subsubheading エラー @code{mysql_fetch_lengths()} は結果セットの現在のレコードについてだけ有効 です。@code{mysql_fetch_row()} を呼び出す前、または結果の全てのレコードを 取り出した後にこれを呼んだ場合、@code{NULL} が返されます。 @subsubheading 例 @example MYSQL_ROW row; unsigned long *lengths; unsigned int num_fields; unsigned int i; row = mysql_fetch_row(result); if (row) @{ num_fields = mysql_num_fields(result); lengths = mysql_fetch_lengths(result); for(i = 0; i < num_fields; i++) @{ printf("Column %u is %lu bytes in length.\n", i, lengths[i]); @} @} @end example @findex @code{mysql_fetch_row()} @node mysql_fetch_row, mysql_field_count, mysql_fetch_lengths, C API functions @subsubsection @code{mysql_fetch_row()} @code{MYSQL_ROW mysql_fetch_row(MYSQL_RES *result)} @subsubheading 説明 結果セットの次のレコードを取り出します。@code{mysql_store_result()} の後に使用すると、 これ以上取り出すレコードがない時は、@code{NULL} を返します。 @code{mysql_use_result()} の後に使用するなら、 これ以上取り出すレコードがない場合やエラーが発生した場合に @code{NULL} を返します。 レコード内の値の数は @code{mysql_num_fields(result)} によって与えられます。 @code{row} が @code{mysql_fetch_row()} の呼び出しからの戻り値を保持する場 合、値へのポインタは @code{row[0]} から @code{row[mysql_num_fields(result)-1} としてアクセスされます。レコード内の @code{NULL} 値は@code{NULL} ポインタによって示されます。 レコードのフィールド値の長さは、@code{mysql_fetch_lengths()} の呼び出しで 獲得できます。空フィールドと @code{NULL} を含むフィールドはどちらも長さ 0 を持ちます; フィールド値のポインタをチェックすることで、これらを区別でき ます。ポインタが @code{NULL} の場合、フィールドは @code{NULL} です; そうで なければフィールドは空です。 @subsubheading 戻り値 次のレコードの @code{MYSQL_ROW} 構造体、エラーが発生したか、もう取り出すレ コードがない場合は @code{NULL}。 @subsubheading エラー @table @code @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @subsubheading 例 @example MYSQL_ROW row; unsigned int num_fields; unsigned int i; num_fields = mysql_num_fields(result); while ((row = mysql_fetch_row(result))) @{ unsigned long *lengths; lengths = mysql_fetch_lengths(result); for(i = 0; i < num_fields; i++) @{ printf("[%.*s] ", (int) lengths[i], row[i] ? row[i] : "NULL"); @} printf("\n"); @} @end example @findex @code{mysql_field_count()} @node mysql_field_count, mysql_field_seek, mysql_fetch_row, C API functions @subsubsection @code{mysql_field_count()} @code{unsigned int mysql_field_count(MYSQL *mysql)} 3.22.24 より前の @code{MySQL} バージョンを使用している場合、 @code{unsigned int mysql_num_fields(MYSQL *mysql)} を代わりに使用すべきで す。 @subsubheading 説明 接続上の最後のクエリのフィールド数を返します。 この関数は通常 @code{mysql_store_result()} が @code{NULL} を返した時（そし てこのように結果セットポインタを持っていない時）に使用されます。この場合、 @code{mysql_store_result()} が空でない結果を提供すべきかどうかを調べるため に、@code{mysql_field_count()} を呼び出すことができます。これは、クエリが @code{SELECT}（または @code{SELECT}に似た）ステートメントであるかを知るこ と無しに、クライアントプログラムに、適切な行動をとらせることができます。下 に示される例は、これをどのように行なうことができるかを説明しています。 @xref{NULL mysql_store_result, , @code{NULL mysql_store_result()}}. @subsubheading 戻り値 結果セット中のフィールド番号を表す unsigned integer。 @subsubheading エラー 無し。 @subsubheading 例 @example MYSQL_RES *result; unsigned int num_fields; unsigned int num_rows; if (mysql_query(&mysql,query_string)) @{ // error @} else // query succeeded, process any data returned by it @{ result = mysql_store_result(&mysql); if (result) // there are rows @{ num_fields = mysql_num_fields(result); // retrieve rows, then call mysql_free_result(result) @} else // mysql_store_result() returned nothing; should it have? @{ if(mysql_field_count(&mysql) == 0) @{ // query does not return data // (it was not a SELECT) num_rows = mysql_affected_rows(&mysql); @} else // mysql_store_result() should have returned data @{ fprintf(stderr, "Error: %s\n", mysql_error(&mysql)); @} @} @} @end example 別の方法は、@code{mysql_field_count(&mysql)} 呼び出しを @code{mysql_errno(&mysql)} に置き換えることです。この場合、ステートメント が @code{SELECT} かどうかを @code{mysql_field_count()} の値から推測するの ではなく、直接 @code{mysql_store_result()} からのエラーをチェックします。 @findex @code{mysql_field_seek()} @node mysql_field_seek, mysql_field_tell, mysql_field_count, C API functions @subsubsection @code{mysql_field_seek()} @code{MYSQL_FIELD_OFFSET mysql_field_seek(MYSQL_RES *result, MYSQL_FIELD_OFFSET offset)} @subsubheading 説明 与えられたオフセットにフィールドカーソルを設定します。次の @code{mysql_fetch_field()} の呼び出しはそのオフセットに対応したフィールドを取 り出します。 レコードの最初にシークするには、0 の @code{offset} 値を渡してください。 @subsubheading 戻り値 フィールドカーソルの前の値。 @subsubheading エラー 無し。 @findex @code{mysql_field_tell()} @node mysql_field_tell, mysql_free_result, mysql_field_seek, C API functions @subsubsection @code{mysql_field_tell()} @code{MYSQL_FIELD_OFFSET mysql_field_tell(MYSQL_RES *result)} @subsubheading 説明 最後の @code{mysql_fetch_field()} に使用したフィールドカーソルの位置を返 します。この値は @code{mysql_field_seek()} への引数として使用できます。 @subsubheading 戻り値 フィールドカーソルの現在のオフセット。 @subsubheading エラー 無し。 @findex @code{mysql_free_result()} @node mysql_free_result, mysql_get_client_info, mysql_field_tell, C API functions @subsubsection @code{mysql_free_result()} @code{void mysql_free_result(MYSQL_RES *result)} @subsubheading 説明 @code{mysql_store_result()}, @code{mysql_use_result()}, @code{mysql_list_dbs()} 等によって結果セットに割り当てられたメモリを解放 します。結果セットで何かを行なった時、@code{mysql_free_result()} を呼び 出してそれが使用したメモリを解放する必要があります。 @subsubheading 戻り値 無し。 @subsubheading エラー 無し。 @findex @code{mysql_get_client_info()} @node mysql_get_client_info, mysql_get_server_version, mysql_free_result, C API functions @subsubsection @code{mysql_get_client_info()} @code{char *mysql_get_client_info(void)} @subsubheading 説明 クライアントライブラリバージョンを表わす文字列を返します。 @subsubheading 戻り値 MySQL クライアントライブラリバージョンを表わす文字列。 @subsubheading エラー 無し。 @node mysql_get_server_version, mysql_get_host_info, mysql_get_client_info, C API functions @subsubsection @code{mysql_get_server_version()} @findex @code{mysql_get_server_version()} @code{unsigned long mysql_get_server_version(MYSQL *mysql)} @subsubheading Description Returns version number of server as an integer (new in 4.1). @subsubheading Return Values A number that represents the MySQL server version in format: main_version*10000 + minor_version *100 + sub_version For example, 4.1.0 is returned as 40100. This is useful to quickly determine the version of the server in a client program to know if some capability exits. @subsubheading Errors None. @findex @code{mysql_get_host_info()} @node mysql_get_host_info, mysql_get_proto_info, mysql_get_server_version, C API functions @subsubsection @code{mysql_get_host_info()} @code{char *mysql_get_host_info(MYSQL *mysql)} @subsubheading 説明 使用中の接続タイプを表わす文字列を返します。サーバのホスト名を含みます。 @subsubheading 戻り値 サーバホスト名と接続タイプを表わす文字列。 @subsubheading エラー 無し。 @findex @code{mysql_get_proto_info()} @node mysql_get_proto_info, mysql_get_server_info, mysql_get_host_info, C API functions @subsubsection @code{mysql_get_proto_info()} @code{unsigned int mysql_get_proto_info(MYSQL *mysql)} @subsubheading 説明 現在の接続に使用されているプロトコルバージョンを返します。 @subsubheading Return Values 現在の接続に使用されているプロトコルバージョンを表わす符号無し整数値。 @subsubheading エラー 無し。 @findex @code{mysql_get_server_info()} @node mysql_get_server_info, mysql_info, mysql_get_proto_info, C API functions @subsubsection @code{mysql_get_server_info()} @code{char *mysql_get_server_info(MYSQL *mysql)} @subsubheading 説明 サーバのバージョン番号を表わす文字列を返します。 @subsubheading 戻り値 サーバのバージョン番号を表わす文字列。 @subsubheading エラー 無し。 @findex @code{mysql_info()} @node mysql_info, mysql_init, mysql_get_server_info, C API functions @subsubsection @code{mysql_info()} @code{char * mysql_info(MYSQL *mysql)} @subsubheading 説明 最も最近に実行されたクエリについての情報を文字列で返します。が、 以下に挙げる構文に限ります。 他の構文では@code{mysql_info()} は @code{NULL} を返します。 文字列の形式 はクエリの型によって様々です。次に説明します (数値は例です; 文字列はクエ リに適した値を含みます): @table @code @item INSERT INTO ... SELECT ... String format: @code{Records: 100 Duplicates: 0 Warnings: 0} @item INSERT INTO ... VALUES (...),(...),(...)... String format: @code{Records: 3 Duplicates: 0 Warnings: 0} @item LOAD DATA INFILE ... String format: @code{Records: 1 Deleted: 0 Skipped: 0 Warnings: 0} @item ALTER TABLE String format: @code{Records: 3 Duplicates: 0 Warnings: 0} @item UPDATE String format: @code{Rows matched: 40 Changed: 40 Warnings: 0} @end table 注意: 複数の値リストがステートメント中に記述された場合にだけ、 @code{mysql_info()} は、@code{INSERT ... VALUES} ステートメントに非 @code{NULL}値を返します。 @subsubheading 戻り値 最も最近に実行されたクエリについての追加情報を表わす文字列。クエリに有効 な情報がない場合は @code{NULL} ポインタ。 @subsubheading エラー 無し。 @findex @code{mysql_init()} @node mysql_init, mysql_insert_id, mysql_info, C API functions @subsubsection @code{mysql_init()} @code{MYSQL * mysql_init(MYSQL *mysql)} @subsubheading 説明 @code{mysql_real_connect()} に適した @code{MYSQL} オブジェクトの割り当て または初期化を行ないます。引数が @code{NULL} ポインタの場合、関数は新し いオブジェクトを割り当てて初期化し返します。そうでなければオブジェクトは 初期化され、オブジェクトのアドレスが返されます。新しいオブジェクトが割り 当てられた場合、@code{mysql_close()} はこのオブジェクトを解放します。 @subsubheading 戻り値 初期化された @code{MYSQL*} ハンドル、または新しいオブジェクトを割り当て るのに十分なメモリがなかった場合は @code{NULL} ポインタ。 @subsubheading エラー メモリ不足の場合は @code{NULL} が返されます。 @findex @code{mysql_insert_id()} @node mysql_insert_id, mysql_kill, mysql_init, C API functions @subsubsection @code{mysql_insert_id()} @code{my_ulonglong mysql_insert_id(MYSQL *mysql)} @subsubheading 説明 前のクエリによって @code{AUTO_INCREMENT} フィールドに生成された ID を返します。 @code{AUTO_INCREMENT} フィールドを含むテーブルに @code{INSERT} クエリを 実行した後で、この関数を使用してください。 注意: 前のクエリが @code{AUTO_INCREMENT} 値を生成しなかった場合、 @code{mysql_insert_id()} は @code{0} を返します。後のために値を保存する必 要がある場合、値を生成するクエリの直後に @code{mysql_insert_id()} を呼び出 すことに気をつけてください。 @code{mysql_insert_id()} is updated after @code{INSERT} and @code{UPDATE} statements that generate an @code{AUTO_INCREMENT} value or that set a column value to @code{LAST_INSERT_ID(expr)}. @xref{Miscellaneous functions}. また、SQL @code{LAST_INSERT_ID()} 常に最後に生成された @code{AUTO_INCREMENT} 値を含み、クエリ間でリセットされないことに注意して下 さい。その関数の値はサーバ内で保守されるからです。 @subsubheading 戻り値 前のクエリによって更新された @code{AUTO_INCREMENT} フィールドの値。接続上 の前のクエリがない場合、クエリが @code{AUTO_INCREMENT} 値を更新しなかった 場合には 0 が返ります。 @subsubheading エラー 無し。 @findex @code{mysql_kill()} @node mysql_kill, mysql_list_dbs, mysql_insert_id, C API functions @subsubsection @code{mysql_kill()} @code{int mysql_kill(MYSQL *mysql, unsigned long pid)} @subsubheading 説明 @code{pid} で指定されたスレッドを殺すようにサーバに頼みます。 @subsubheading 戻り値 成功時0。失敗時非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_list_dbs()} @node mysql_list_dbs, mysql_list_fields, mysql_kill, C API functions @subsubsection @code{mysql_list_dbs()} @code{MYSQL_RES *mysql_list_dbs(MYSQL *mysql, const char *wild)} @subsubheading 説明 サーバ上の、@code{wild} 引数で指定された簡易正規表現に適合する、データベー ス名からなる結果セットを返します。@code{wild} はワイルドカード文字 @samp{%} または @samp{_} を含むことができます。また、全てのデータベース に適合するように @code{NULL} ポインタにできます。@code{mysql_list_dbs()} の呼び出しはクエリ @code{SHOW databases [LIKE wild]} を実行するのと同様 です。 @code{mysql_free_result()} で結果セットを解放する必要があります。 @subsubheading 戻り値 成功時 @code{MYSQL_RES} 結果セット。失敗した場合は @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_OUT_OF_MEMORY メモリ不足。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_list_fields()} @node mysql_list_fields, mysql_list_processes, mysql_list_dbs, C API functions @subsubsection @code{mysql_list_fields()} @code{MYSQL_RES *mysql_list_fields(MYSQL *mysql, const char *table, const char *wild)} @subsubheading 説明 与えられたテーブル内の、@code{wild} 引数で指定された簡易正規表現に適合する フィールド名からなる結果セットを返します。@code{wild} はワイルドカー ド文字 @samp{%} または @samp{_} を含むことができます。また、全てのフィー ルドに適合するように @code{NULL} ポインタにできます。 @code{mysql_list_fields()} はクエリ @code{SHOW COLUMNS FROM table [LIKE wild]} を実行するのと同様です。 注意: @code{mysql_list_fields()} の代わりに @code{SHOW COLUMNS FROM tbl_name} の使用を勧めます。 @code{mysql_free_result()} で結果セットを解放する必要があります。 @subsubheading 戻り値 成功時 @code{MYSQL_RES} 結果セット。エラーが発生した場合は @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_list_processes()} @node mysql_list_processes, mysql_list_tables, mysql_list_fields, C API functions @subsubsection @code{mysql_list_processes()} @code{MYSQL_RES *mysql_list_processes(MYSQL *mysql)} @subsubheading 説明 現在のサーバスレッドを示す結果セットを返します。これは @code{mysqladmin processlist} や @code{SHOW PROCESSLIST} クエリで 報告されるものと同じ種類の情報です。 @code{mysql_free_result()} で結果セットを解放する必要があります。 @subsubheading 戻り値 成功時 @code{MYSQL_RES} 結果セット。失敗した場合は @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_list_tables()} @node mysql_list_tables, mysql_num_fields, mysql_list_processes, C API functions @subsubsection @code{mysql_list_tables()} @code{MYSQL_RES *mysql_list_tables(MYSQL *mysql, const char *wild)} @subsubheading 説明 @code{wild} 引数で指定された簡易正規表現に適合する、現在のデータベース 内のテーブル名からなる結果セットを返します。@code{wild} はワイルドカード 文字 @samp{%} または @samp{_} を含むことができます。また、全てのテーブル に適合するように @code{NULL} ポインタにできます。 @code{mysql_list_tables()} はクエリ @code{SHOW tables [LIKE wild]} を実 行するのと同様です。 @code{mysql_free_result()} で結果セットを解放する必要があります。 @subsubheading 戻り値 成功時 @code{MYSQL_RES} 結果セット。失敗した場合は @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_num_fields()} @findex @code{mysql_field_count()} @node mysql_num_fields, mysql_num_rows, mysql_list_tables, C API functions @subsubsection @code{mysql_num_fields()} @code{unsigned int mysql_num_fields(MYSQL_RES *result)} または @code{unsigned int mysql_num_fields(MYSQL *mysql)} 二番目の形式は MySQL 3.23 以上では動作しません。@code{MYSQL*} 引 数を通す場合は、代わりに @code{unsigned int mysql_field_count(MYSQL*mysql)} を使用しなくてはいけません。 @subsubheading 説明 結果セット中のフィールド数を返します。 注意: 結果セットへのポインタまたは接続ハンドルのいずれかからフィールドの数 を得ることができます。@code{mysql_store_result()} または @code{mysql_use_result()} が @code{NULL} を返した（つまり結果セットポイン タが無い）場合、接続ハンドルを使用します。この場合、 @code{mysql_field_count()} を呼び出して、@code{mysql_store_result()} が空 でない結果を提供すべきかどうかを決定できます。これにより、クライアントプロ グラムはクエリが @code{SELECT}（または @code{SELECT} に似た）ステートメン トだったかどうかを知ることなしに、適切な行動を取ることができます。以下に示 す例はこれをどのように行なうかを説明しています。 @xref{NULL mysql_store_result, , @code{NULL mysql_store_result()}}. @subsubheading 戻り値 結果セット中のフィールド数を表わす符号無し整数。 @subsubheading エラー 無し。 @subsubheading 例 @example MYSQL_RES *result; unsigned int num_fields; unsigned int num_rows; if (mysql_query(&mysql,query_string)) @{ // error @} else // query succeeded, process any data returned by it @{ result = mysql_store_result(&mysql); if (result) // there are rows @{ num_fields = mysql_num_fields(result); // retrieve rows, then call mysql_free_result(result) @} else // mysql_store_result() returned nothing; should it have? @{ if (mysql_errno(&mysql)) @{ fprintf(stderr, "Error: %s\n", mysql_error(&mysql)); @} else if (mysql_field_count(&mysql) == 0) @{ // query does not return data // (it was not a SELECT) num_rows = mysql_affected_rows(&mysql); @} @} @} @end example （結果セットが返るべきクエリであることを知っている場合の）方法は、 @code{mysql_errno(&mysql)} コールを @code{mysql_field_count(&mysql)} が 0 かどうかのチェックに置き換えることです。これは何かが悪い場合にだけ起こり ます。 @findex @code{mysql_num_rows()} @node mysql_num_rows, mysql_options, mysql_num_fields, C API functions @subsubsection @code{mysql_num_rows()} @code{my_ulonglong mysql_num_rows(MYSQL_RES *result)} @subsubheading 説明 結果セット中のレコード数を返します。 @code{mysql_num_rows()} の使用は、結果セットを返すのに @code{mysql_store_result()} か @code{mysql_use_result()} のどちらを使用す るかに依存します。@code{mysql_store_result()} を使用する場合、 @code{mysql_num_rows()} はすぐに呼ぶことができます。 @code{mysql_use_result()} を使用する場合、結果セットの全てのレコードが取り 出されるまで、@code{mysql_num_rows()} は正しい値を返しません。 @subsubheading 戻り値 結果セットのレコード数。 @subsubheading エラー 無し。 @findex @code{mysql_options()} @node mysql_options, mysql_ping, mysql_num_rows, C API functions @subsubsection @code{mysql_options()} @code{int mysql_options(MYSQL *mysql, enum mysql_option option, const char *arg)} @subsubheading 説明 特別な接続オプションを設定し、接続の振舞いに影響を与えるために使用できます。 この関数は複数のオプションを設定するために複数回呼ぶことができます。 @code{mysql_options()} は @code{mysql_init()} の後で、 @code{mysql_connect()} や @code{mysql_real_connect()} の前に呼ばれなければ なりません。 @code{option} 引数は設定したいオプションです; @code{arg} 引数はオプション に対する値です。オプションが整数の場合、@code{arg} は整数値へのポインタで す。 有効なオプション値: @multitable @columnfractions .42 .20 .38 @item @strong{オプション} @tab @strong{引数型} @tab @strong{機能} @item @code{MYSQL_OPT_CONNECT_TIMEOUT} @tab @code{unsigned int *} @tab 接続タイムアウト（秒）。 @item @code{MYSQL_OPT_COMPRESS} @tab 使用しない @tab 圧縮クライアント／サーバプロトコルを使用する。 @item @code{MYSQL_OPT_LOCAL_INFILE} @tab optional pointer to uint @tab If no pointer is given or if pointer points to an @code{unsigned int != 0} the command @code{LOAD LOCAL INFILE} is enabled. @item @code{MYSQL_OPT_NAMED_PIPE} @tab 使用しない @tab NT 上の MySQL サーバへの接続に名前付パイプを使用する。 @item @code{MYSQL_INIT_COMMAND} @tab @code{char *} @tab MySQL サーバへの接続時に実行するコマンド。再接続時に自動的に再実行される。 @item @code{MYSQL_READ_DEFAULT_FILE} @tab @code{char *} @tab @file{my.cnf} の代わりに指定されたオプションファイルからオプションを読み込む。 @item @code{MYSQL_READ_DEFAULT_GROUP} @tab @code{char *} @tab @file{my.cnf} または @code{MYSQL_READ_DEFAULT_FILE} で指定されたファイルから指定されたグループのオプションを読み込む。 @end multitable 注意: @code{MYSQL_READ_DEFAULT_FILE} と @code{MYSQL_READ_DEFAULT_GROUP} を 使用する場合、@code{client} グループが常に読まれます。 オプションファイル中に指定されるグループは次のオプションを含むことができま す: @multitable @columnfractions .25 .60 @item @code{connect-timeout} @tab 接続タイムアウト（秒）。On Linux this timeout is also used for waiting for the first answer from the server. @item @code{compress} @tab 圧縮クライアント／サーバプロトコルを使用する。 @item @code{database} @tab 接続命令中でデータベースが指定されない場合、このデータベースに接続する。 @item @code{debug} @tab デバッグオプション @item @code{disable-local-infile} @tab Disable use of @code{LOAD DATA LOCAL}. @item @code{max_allowed_packet} @tab Max size of packet client can read from server. @item @code{host} @tab デフォルトホスト名 @item @code{init-command} @tab MySQL サーバへの接続時に実行するコマンド。再接続時に自動的に再実行される。 @item @code{local-infile[=(0|1)]} @tab If no argument or argument != 0 then enable use of @code{LOAD DATA LOCAL}. @item @code{password} @tab デフォルトパスワード @item @code{pipe} @tab NT 上の MySQL サーバへの接続に名前付パイプを使用する。 @item @code{protocol=(TCP | SOCKET | PIPE | MEMORY)} @tab Which protocol to use when connecting to server (New in 4.1) @item @code{port} @tab デフォルトポート番号 @item @code{return-found-rows} @tab @code{UPDATE} 使用時、@code{mysql_info()} が更新された行の代わりに見つかった行を返すようにする。 @item @code{shared-memory-base-name=name} @tab Shared memory name to use to connect to server (default is "MySQL"). New in MySQL 4.1. @item @code{socket} @tab デフォルトソケット番号 @item @code{user} @tab デフォルトユーザ @end multitable Note that @code{timeout} has been replaced by @code{connect-timeout}, but @code{timeout} will still work for a while. オプションファイルについてのさらなる情報は、@ref{Option files} を参照して 下さい。 @subsubheading 戻り値 成功の場合は0。未知のオプションを使用した場合は非0。 @subsubheading 例 @example MYSQL mysql; mysql_init(&mysql); mysql_options(&mysql,MYSQL_OPT_COMPRESS,0); mysql_options(&mysql,MYSQL_READ_DEFAULT_GROUP,"odbc"); if (!mysql_real_connect(&mysql,"host","user","passwd","database",0,NULL,0)) @{ fprintf(stderr, "Failed to connect to database: Error: %s\n", mysql_error(&mysql)); @} @end example 上記は、圧縮クライアント／サーバプロトコルを使用し、@code{my.cnf} ファイル 中の @code{odbc} セクションから追加オプションを読むように、クライアントに 要求します。 @findex @code{mysql_ping()} @node mysql_ping, mysql_query, mysql_options, C API functions @subsubsection @code{mysql_ping()} @code{int mysql_ping(MYSQL *mysql)} @subsubheading 説明 サーバへの接続が動作しているかどうかをチェックします。ダウンしている場合 は、自動的に再接続を試みます。 この関数は、長い間静かにしているクライアントが、サーバが接続をクローズし たかどうかをチェック（と再接続）するために使用できます。 @subsubheading 戻り値 サーバが生きている場合0。他の値はエラーを示します。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_query()} @node mysql_query, mysql_real_connect, mysql_ping, C API functions @subsubsection @code{mysql_query()} @code{int mysql_query(MYSQL *mysql, const char *query)} @subsubheading 説明 NULL 終端文字列 @code{query} で示される SQL クエリを実行します。クエリはひ とつの SQL ステートメントでなければなりません。終端のセミコロン (@samp{;})や @code{\g} をステートメントに追加すべきではありません。 @code{mysql_query()} はバイナリデータを含むクエリには使用できません（バ イナリデータは @samp{\0} 文字を含むことがあります。これはクエリ文字列の 最後として解釈されます）。この場合、@code{mysql_real_query()} を代わりに 使用してください。 If you want to know if the query should return a result set or not, you can use @code{mysql_field_count()} to check for this. @xref{mysql_field_count, , @code{mysql_field_count()}}. @subsubheading 戻り値 クエリが成功した場合は0。クエリが失敗した場合は非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_real_connect()} @node mysql_real_connect, mysql_real_escape_string, mysql_query, C API functions @subsubsection @code{mysql_real_connect()} @code{MYSQL *mysql_real_connect(MYSQL *mysql, const char *host, const char *user, const char *passwd, const char *db, unsigned int port, const char *unix_socket, unsigned int client_flag)} @subsubheading 説明 @code{host} 上で動作している MySQL データベースエンジンへの接続 の確立を試みます。 @code{mysql_get_client_info()} 以外の他の API 関数を実行する前に、 @code{mysql_real_connect()} が成功している必要があります。 @code{mysql_real_connect()} を呼び出す前に、@code{MYSQL} 構造体を獲得ま たは初期化するために @code{mysql_init()} を呼ぶ必要があることに注意して ください。 @itemize @bullet @item 最初のパラメータは既存の @code{MYSQL} 構造体のアドレスです。 @code{mysql_real_connect()} を呼ぶ前に、@code{MYSQL} 構造体の初期化のため に @code{mysql_init()} を呼ぶ必要があります。 @code{mysql_options()} 呼び出しで多くの接続オプションを変更できます。 @xref{mysql_options, @code{mysql_options()}}. @item @code{host} の値はホスト名か IP アドレスのどちらでも可能です。 @code{host} が @code{NULL} または文字列 @code{"localhost"} の場合はロー カルホストへの接続とみなされます。OS がソケットをサポートする場合(UNIX) または名前つきパイプをサポートする場合(Windows)、サーバへの TCP/IP 接続の 代わりに使用されます。 @item @code{user} パラメータはユーザの MySQL ログイン ID が入っています。 @code{user} が @code{NULL} の場合、現在のユーザとみなされます。Windows ODBC 下では、現在のユーザは明示的に指定されなければなりません。UNIX 下で は現在のログイン名が適用されます。 Windows ODBC では, カレントのユーザー名を与えなければなりません。 @xref{ODBC administrator}. @item @code{passwd} パラメータは @code{user} のパスワードが入っています。 もし @code{passwd} が @code{NULL} の場合、空白のパスワードフィールドを持つ @code{user} テーブル内のレコードだけが適合チェックされます。このような方 法で、パスワードが記述されたかどうかによってユーザが異なる権限を得るよう に、データベース管理者が MySQL 特権システムを設定することができ ます。 注意: @code{mysql_connect()} を呼び出す前に @code{passwd} を暗号化しない でください。パスワードの暗号化はクライアント API で自動的に処理されます。 @item @code{db} が @code{NULL} でない場合、接続はこの値をデフォルトデータベー スにセットします。 @item @code{port} が 0 でない場合、値は TCP/IP 接続のポート番号として使用され ます。@code{host} パラメータが接続のタイプを決定することに注意してくださ い。 @item @code{unix_socket} が @code{NULL} でない場合、文字列は使用されるソケット または名前つきパイプを記述します。@code{host} パラメータが接続のタイプを 決定することに注意してください。 @item client_flag の値は通常 0 ですが、とても特殊な状況のため次のフラグの組み 合わせを設定できます: @multitable @columnfractions .30 .65 @item @strong{フラグ名} @tab @strong{フラグの意味} @item @code{CLIENT_COMPRESS} @tab Use compression protocol. @item @code{CLIENT_FOUND_ROWS} @tab 影響された行数ではなく見つかった行数を返します @item @code{CLIENT_IGNORE_SPACE} @tab Allow spaces after function names. Makesall functions names reserved words. @item @code{CLIENT_INTERACTIVE} @tab Allow @code{interactive_timeout} seconds(instead of @code{wait_timeout} seconds) of inactivity before closing the connection. @item @code{CLIENT_NO_SCHEMA} @tab @code{db_name.tbl_name.col_name} を許しません。これは ODBC のためです; その構文を使用した場合、パーサがエラーを生成します。これはいくつかの ODBC プログラムのバグのトラップに役立ちます。 @item @code{CLIENT_COMPRESS} @tab 圧縮プロトコルを使用します @item @code{CLIENT_ODBC} @tab クライアントが ODBC クライアント。これは @code{mysqld} をさらに ODBC-フレンドリに変更します。 @item @code{CLIENT_SSL} @tab Use SSL (encrypted protocol). @end multitable @end itemize @code{mysql_real_connect()} の最初の引数に @code{NULL} ポインタを記述す ることもできます。これは C API が接続構造体のメモリを割り当て、 @code{mysql_close()} 呼び出し時に自動的に解放されます。この方法の不利な 点は、接続が失敗した場合に @code{mysql_real_connect()} からのエラーメッ セージを取り出すことができないことです。 最初の引数が @code{NULL} ポインタでない場合は、存在する @code{MYSQL} 構 造体のアドレスであるべきです。 @subsubheading 戻り値 接続が成功した場合は @code{MYSQL*} 接続ハンドルです。接続が失敗した場合 は C @code{NULL} ポインタです。 接続に成功すると、戻り値はその最初のパラメータの値と同じです。 @subsubheading エラー @table @code @item CR_CONN_HOST_ERROR MySQL サーバへの接続に失敗した。 @item CR_CONNECTION_ERROR ローカル MySQL サーバへの接続に失敗した。 @item CR_IPSOCK_ERROR IP ソケットの生成に失敗した。 @item CR_OUT_OF_MEMORY メモリ不足。 @item CR_SOCKET_CREATE_ERROR UNIX ソケットの生成に失敗した。 @item CR_UNKNOWN_HOST ホスト名の IP アドレスを見つけるのに失敗した。 @item CR_VERSION_ERROR 異なるプロトコルバージョンを使用するクライアントライブラリでサーバへの接 続を試みた結果のプロトコルミスマッチ。これは、とても古いクライアントライ ブラリを使用して、@code{--old-protocol} オプション付きで開始していない新 しいサーバに接続する場合に発生します。 @item CR_NAMEDPIPEOPEN_ERROR Windows 上の名前つきパイプの生成に失敗した。 @item CR_NAMEDPIPEWAIT_ERROR Windows 上の名前つきパイプの wait に失敗した。 @item CR_NAMEDPIPESETSTATE_ERROR Windows 上のパイプハンドラの獲得に失敗した。 @item CR_SERVER_LOST If @code{connect_timeout} > 0 and it took longer then @code{connect_timeout} seconds to connect to the server or if the server died while executing the @code{init-command}. @end table @subsubheading 例 @example MYSQL mysql; mysql_init(&mysql); mysql_options(&mysql,MYSQL_READ_DEFAULT_GROUP,"your_prog_name"); if (!mysql_real_connect(&mysql,"host","user","passwd","database",0,NULL,0)) @{ fprintf(stderr, "Failed to connect to database: Error: %s\n", mysql_error(&mysql)); @} @end example By using @code{mysql_options()} the MySQL library will read the @code{[client]} and @code{[your_prog_name]} sections in the @file{my.cnf} file which will ensure that your program will work, even if someone has set up MySQL in some non-standard way. Note that upon connection, @code{mysql_real_connect()} sets the @code{reconnect} flag (part of the @code{MYSQL} structure) to a value of @code{1}. This flag indicates, in the event that a query cannot be performed because of a lost connection, to try reconnecting to the server before giving up. @findex @code{mysql_real_escape_string()} @node mysql_real_escape_string, mysql_real_query, mysql_real_connect, C API functions @subsubsection @code{mysql_real_escape_string()} @code{unsigned long mysql_real_escape_string(MYSQL *mysql, char *to, const char *from, unsigned long length)} @subsubheading 説明 This function is used to create a legal SQL string that you can use in a SQL statement. @xref{String syntax}. @code{from} の文字列を、SQL ステートメントとしてサーバに送ることができる ように、現在のキャラクタ・セットを考慮しながら変換します。 結果は @code{to} に入り、終端 null 文字を追加します。 変換される文字列は @samp{NUL} (ASCII 0), @samp{\n}, @samp{\r}, @samp{\}, @samp{'}, @samp{"}, Control-Z です。(@pxref{Literals}). (Strictly speaking, MySQL requires only that backslash and the quote character used to quote the string in the query be escaped. This function quotes the other characters to make them easier to read in log files.) @code{from} で示される文字列 は@code{length} バイト長でなければなりません。 @code{to} バッファには少なくとも @code{length*2+1} バイト長を割り当てる 必要があります。（最悪の場合、それぞれの文字が２バイトに変換されることがあ り、さらに終端 null バイトのための場所が必要です。） @code{mysql_real_escape_string()} が復帰するとき、@code{to} の内容は @code{NUL} 終端文字列になります。 戻り値は変換された文字列の長さです。終端 null 文字は含みません。 @subsubheading 例 @example char query[1000],*end; end = strmov(query,"INSERT INTO test_table values("); *end++ = '\''; end += mysql_real_escape_string(&mysql, end,"What's this",11); *end++ = '\''; *end++ = ','; *end++ = '\''; end += mysql_real_escape_string(&mysql, end,"binary data: \0\r\n",16); *end++ = '\''; *end++ = ')'; if (mysql_real_query(&mysql,query,(unsigned int) (end - query))) @{ fprintf(stderr, "Failed to insert row, Error: %s\n", mysql_error(&mysql)); @} @end example 上記の @code{strmov()} 関数は @code{mysqlclient} ライブラリに含まれてい て、@code{strcpy()} のように働きますが、最初の引数の終りの null へのポイ ンタを返します。 @subsubheading 戻り値 @code{to} へ置かれた値の長さ。終端 null 文字は含みません。 @subsubheading エラー 無し。 @findex @code{mysql_real_query()} @node mysql_real_query, mysql_reload, mysql_real_escape_string, C API functions @subsubsection @code{mysql_real_query()} @code{int mysql_real_query(MYSQL *mysql, const char *query, unsigned long length)} @subsubheading 説明 @code{query} で示される SQL クエリを実行します。これは @code{length} バ イト長です。クエリはひとつの SQL ステートメントでなければなりません。終端 のセミコロン(@samp{;})や @code{\g} をステートメントに追加すべきではありま せん。 バイナリデータを含むクエリは @code{mysql_real_query()} を使 用@strong{しなければなりません}。バイナリデータは @samp{\0} 文字を含むこと があるからです。 また、@code{mysql_real_query()} は @code{mysql_query()} よりも速いです。 クエリの @code{strlen()} を呼ばないからです。 If you want to know if the query should return a result set or not, you can use @code{mysql_field_count()} to check for this. @xref{mysql_field_count, @code{mysql_field_count()}}. @subsubheading 戻り値 クエリが成功した場合は0。クエリが失敗した場合は非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_reload()} @node mysql_reload, mysql_row_seek, mysql_real_query, C API functions @subsubsection @code{mysql_reload()} @code{int mysql_reload(MYSQL *mysql)} @subsubheading 説明 MySQL サーバに、アクセス権テーブルを再読み込みするように依頼し ます。接続されたユーザは @code{RELOAD} 権限を持つ必要があります。 この関数は推奨されません。代わりに、SQL @code{FLUSH PRIVILEGES} ステートメ ントを発行する @code{mysql_query()} の使用が推奨されます。 @subsubheading 戻り値 成功時0。失敗時非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_row_seek()} @node mysql_row_seek, mysql_row_tell, mysql_reload, C API functions @subsubsection @code{mysql_row_seek()} @code{MYSQL_ROW_OFFSET mysql_row_seek(MYSQL_RES *result, MYSQL_ROW_OFFSET offset)} @subsubheading 説明 レコードカーソルをクエリ結果セット中の絶対レコードに設定します。これは、結 果セット構造体がクエリのすべての結果を持っていることを要求します。そのため、 @code{mysql_row_seek()} は @code{mysql_store_result()} と共にだけ使用でき、 @code{mysql_use_result()} と共には使用できません。 オフセットは @code{mysql_row_tell()} または @code{mysql_row_seek()} 呼びだ しからの戻り値であるべきです。この値は単純なレコード番号ではありません;レ コード番号を使用して結果セット内のレコードにシークしたい場合は、 @code{mysql_data_seek()} を代わりに使用してください。 @subsubheading 戻り値 レコードカーソルの前の値。この値はその後の @code{mysql_row_seek()} 呼びだ しに渡すことができます。 @subsubheading エラー 無し。 @findex @code{mysql_row_tell()} @node mysql_row_tell, mysql_select_db, mysql_row_seek, C API functions @subsubsection @code{mysql_row_tell()} @code{MYSQL_ROW_OFFSET mysql_row_tell(MYSQL_RES *result)} @subsubheading 説明 最後の @code{mysql_fetch_row()} についてレコードカーソルの現在の位置を返します。 この値は @code{mysql_row_seek()} への引数として使用できます。 @code{mysql_row_tell()} は @code{mysql_store_result()} の後にだけ使用すべ きで、@code{mysql_use_result()} の後には使用すべきではありません。 @subsubheading 戻り値 行カーソルの現在のオフセット。 @subsubheading エラー 無し。 @findex @code{mysql_select_db()} @node mysql_select_db, mysql_shutdown, mysql_row_tell, C API functions @subsubsection @code{mysql_select_db()} @code{int mysql_select_db(MYSQL *mysql, const char *db)} @subsubheading 説明 @code{mysql} で示される現在の接続に、デフォルト(現在の)データベースとし て @code{db} で示されるデータベースを使用するように指示します。以降のク エリでは、明示的にデータベースを指定しないテーブル参照について、このデー タベースがデフォルトになります。 接続されたユーザがデータベースを使用する権限を持っていると証明されなけれ ば、@code{mysql_select_db()} は失敗します。 @subsubheading 戻り値 成功時0。失敗時非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_shutdown()} @node mysql_shutdown, mysql_stat, mysql_select_db, C API functions @subsubsection @code{mysql_shutdown()} @code{int mysql_shutdown(MYSQL *mysql)} @subsubheading 説明 データベースサーバにシャットダウンするように要求します。接続されたユーザ は @code{SHUTDOWN} 権限を持っている必要があります。 @subsubheading 戻り値 成功時0。失敗時非0。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_stat()} @node mysql_stat, mysql_store_result, mysql_shutdown, C API functions @subsubsection @code{mysql_stat()} @code{char *mysql_stat(MYSQL *mysql)} @subsubheading 説明 @code{mysqladmin status} で提供されるのと同様の情報を文字列として返しま す。これは秒での uptime と、実行中のスレッド数、問い合わせ数、再読み込み 数、オープンテーブル数を含みます。 @subsubheading 戻り値 サーバ状態を表わす文字列。エラーが発生した場合 @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_store_result()} @node mysql_store_result, mysql_thread_id, mysql_stat, C API functions @subsubsection @code{mysql_store_result()} @code{MYSQL_RES *mysql_store_result(MYSQL *mysql)} @subsubheading 説明 データを取り出すクエリ(@code{SELECT}, @code{SHOW}, @code{DESCRIBE}, @code{EXPLAIN})が成功する毎に、@code{mysql_store_result()} または @code{mysql_use_result()} を呼び出す必要があります。 You don't have to call @code{mysql_store_result()} or @code{mysql_use_result()} for other queries, but it will not do any harm or cause any notable performance if you call @code{mysql_store_result()} in all cases. You can detect if the query didn't have a result set by checking if @code{mysql_store_result()} returns 0 (more about this later one). If you want to know if the query should return a result set or not, you can use @code{mysql_field_count()} to check for this. @xref{mysql_field_count, @code{mysql_field_count()}}. @code{mysql_store_result()} はクエリのすべての結果をクライアントへ読み込み、 @code{MYSQL_RES} 構造体を割り当て、この構造体に結果を配置します。 @code{mysql_store_results()} returns a null pointer if the query didn't return a result sets (If the query was, for example, an @code{INSERT} statement). @code{mysql_store_results()} returns also null pointer if reading of the result set failed. You can check if you got an error by checking if @code{mysql_error()} doesn't return a null pointer, if @code{mysql_errno()} returns <> 0 or if @code{mysql_field_count()} returns <> 0. 返されるレコードが無い場合、空の結果セットが返されます。 (空の結果セットは @code{NULL} 戻り値とは異なります。) 一度 @code{mysql_store_result()} を呼び出して null ポインターでない 結果を得る事ができたら、結果セット中にいくつのレ コードがあるかを見つけるために、@code{mysql_num_rows()} を呼び出すことがで きます。 結果セットからレコードを取り出すために @code{mysql_fetch_row()} を呼び出す ことができます。また、結果セット内の現在のレコード位置を設定／取得するため に @code{mysql_row_seek()} と @code{mysql_row_tell()} を呼び出すことができ ます。 一度結果セットで行なうと、@code{mysql_free_result()} を呼び出す必要があ ります。 @xref{NULL mysql_store_result, , @code{NULL mysql_store_result()}}. @subsubheading 戻り値 結果の @code{MYSQL_RES} 結果構造体。エラーがある場合 @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_OUT_OF_MEMORY メモリ不足。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @findex @code{mysql_thread_id()} @node mysql_thread_id, mysql_use_result, mysql_store_result, C API functions @subsubsection @code{mysql_thread_id()} @code{unsigned long mysql_thread_id(MYSQL *mysql)} @subsubheading 説明 現在の接続のスレッド ID を返します。この値は、スレッドを殺すための @code{mysql_kill()} への引数として使用できます。 接続が失われて、@code{mysql_ping()} で再接続した場合、スレッド ID は変更さ れます。これはスレッド ID を後で使うために取得して格納すべきではないことを 意味します。必要な時にそれを取得すべきです。 @subsubheading 戻り値 現在の接続のスレッド ID。 @subsubheading エラー 無し。 @findex @code{mysql_use_result()} @node mysql_use_result, , mysql_thread_id, C API functions @subsubsection @code{mysql_use_result()} @code{MYSQL_RES *mysql_use_result(MYSQL *mysql)} @subsubheading 説明 データを取り出すクエリ(@code{SELECT}, @code{SHOW}, @code{DESCRIBE}, @code{EXPLAIN})が成功する毎に、 @code{mysql_store_result()} または @code{mysql_use_result()} を呼び出す必要があります。 @code{mysql_use_result()} は結果セット検索を開始しますが, @code{mysql_store_result()} のように、実際にクライアントに結果セットを読み 取りません. 代わりに、各レコードは @code{mysql_fetch_row()} 呼びだしが行な われることにより、個々に取り出されます。 @code{mysql_use_result()} はクエリの結果を、一時テーブルやローカルバッファ に格納すること無く、サーバから直接読み込みます。これは @code{mysql_store_result()} よりもいくらか速く、少ないメモリを使用します。 この場合、クライアントは現在の行と接続バッファ ( @code{max_allowed_packet} bytes まで増加する ) のメモリだけを割り当てます。 一方、クライアント側で各行に ついて多くの処理を行なう場合や、ユーザが @code{^S} (スクロール停止) を入 力できるような画面に出力を送る場合は、@code{mysql_use_result()} を使用す べきではありません。これはサーバと連携しており、他のスレッドが データが取り出されるテーブルを更新する事を邪魔します。 @code{mysql_use_result()} 使用時、@code{NULL} 値を取り出すまで @code{mysql_fetch_row()} を実行する必要があります。そうしないと、次のク エリは前のクエリから結果を取り出します。これを忘れると、C API はエラー @code{Commands out of sync; You can't run this command now} を与えます！ @code{mysql_use_result()} から返される結果では、 @code{mysql_data_seek()}, @code{mysql_row_seek()}, @code{mysql_row_tell()}, @code{mysql_num_rows()}, @code{mysql_affected_rows()} を使用できません。 また、@code{mysql_use_result()} が終了するまで他のクエリの発行もできませ ん。(全ての行をフェッチした後に、フェッチされた行数を知るために @code{mysql_num_rows} を呼び出すことができます。) 一度結果セットで行なうと、@code{mysql_free_result()} を呼び出す必要があ ります。 @subsubheading 戻り値 結果の @code{MYSQL_RES} 結果構造体。エラーがある場合 @code{NULL}。 @subsubheading エラー @table @code @item CR_COMMANDS_OUT_OF_SYNC 不当な順にコマンドが実行された。 @item CR_OUT_OF_MEMORY メモリ不足。 @item CR_SERVER_GONE_ERROR MySQL サーバがいなくなった。 @item CR_SERVER_LOST サーバへの接続がクエリ中に失われた。 @item CR_UNKNOWN_ERROR 未知のエラーが発生した。 @end table @node C Thread functions, C Embedded Server func, C API functions, C @subsection C Threaded Function Descriptions You need to use the following functions when you want to create a threaded client. @xref{Threaded clients}. @menu * my_init:: @code{my_init()} * mysql_thread_init:: @code{mysql_thread_init()} * mysql_thread_end:: @code{mysql_thread_end()} * mysql_thread_safe:: @code{mysql_thread_safe()} @end menu @node my_init, mysql_thread_init, C Thread functions, C Thread functions @subsubsection @code{my_init()} @findex @code{my_init()} @code{void my_init(void)} @subsubheading Description This function needs to be called once in the program before calling any MySQL function. This initialises some global variables that MySQL needs. If you are using a thread-safe client library, this will also call @code{mysql_thread_init()} for this thread. This is automatically called by @code{mysql_init()}, @code{mysql_server_init()} and @code{mysql_connect()}. @subsubheading Return Values None. @node mysql_thread_init, mysql_thread_end, my_init, C Thread functions @subsubsection @code{mysql_thread_init()} @findex @code{mysql_thread_init()} @code{my_bool mysql_thread_init(void)} @subsubheading Description This function needs to be called for each created thread to initialise thread-specific variables. This is automatically called by @code{my_init()} and @code{mysql_connect()}. @subsubheading Return Values None. @node mysql_thread_end, mysql_thread_safe, mysql_thread_init, C Thread functions @subsubsection @code{mysql_thread_end()} @findex @code{mysql_thread_end()} @code{void mysql_thread_end(void)} @subsubheading Description This function needs to be called before calling @code{pthread_exit()} to free memory allocated by @code{mysql_thread_init()}. Note that this function @strong{is not invoked automatically} by the client library. It must be called explicitly to avoid a memory leak. @subsubheading Return Values None. @node mysql_thread_safe, , mysql_thread_end, C Thread functions @subsubsection @code{mysql_thread_safe()} @findex @code{mysql_thread_safe()} @code{unsigned int mysql_thread_safe(void)} @subsubheading Description This function indicates whether the client is compiled as thread-safe. @subsubheading Return Values 1 is the client is thread-safe, 0 otherwise. @node C Embedded Server func, C API problems, C Thread functions, C @subsection C Embedded Server Function Descriptions You must use the following functions if you want to allow your application to be linked against the embedded MySQL server library. @xref{libmysqld}. If the program is linked with @code{-lmysqlclient} instead of @code{-lmysqld}, these functions do nothing. This makes it possible to choose between using the embedded MySQL server and a stand-alone server without modifying any code. @menu * mysql_server_init:: @code{mysql_server_init()} * mysql_server_end:: @code{mysql_server_end()} @end menu @node mysql_server_init, mysql_server_end, C Embedded Server func, C Embedded Server func @subsubsection @code{mysql_server_init()} @findex @code{mysql_server_init()} @code{int mysql_server_init(int argc, char **argv, char **groups)} @subsubheading Description This function @strong{must} be called once in the program using the embedded server before calling any other MySQL function. It starts up the server and initialises any subsystems (@code{mysys}, InnoDB, etc.) that the server uses. If this function is not called, the program will crash. If you are using the DBUG package that comes with MySQL, you should call this after you have called @code{MY_INIT()}. The @code{argc} and @code{argv} arguments are analogous to the arguments to @code{main()}. The first element of @code{argv} is ignored (it typically contains the program name). For convenience, @code{argc} may be @code{0} (zero) if there are no command-line arguments for the server. @code{mysql_server_init()} makes a copy of the arguments so it's safe to destroy @code{argv} or @code{groups} after the call. The @code{NULL}-terminated list of strings in @code{groups} selects which groups in the option files will be active. @xref{Option files}. For convenience, @code{groups} may be @code{NULL}, in which case the @code{[server]} and @code{[emedded]} groups will be active. @subsubheading Example @example #include #include static char *server_args[] = @{ "this_program", /* this string is not used */ "--datadir=.", "--key_buffer_size=32M" @}; static char *server_groups[] = @{ "embedded", "server", "this_program_SERVER", (char *)NULL @}; int main(void) @{ mysql_server_init(sizeof(server_args) / sizeof(char *), server_args, server_groups); /* Use any MySQL API functions here */ mysql_server_end(); return EXIT_SUCCESS; @} @end example @subsubheading Return Values 0 if okay, 1 if an error occurred. @node mysql_server_end, , mysql_server_init, C Embedded Server func @subsubsection @code{mysql_server_end()} @findex @code{mysql_server_end()} @code{void mysql_server_end(void)} @subsubheading Description This function @strong{must} be called once in the program after all other MySQL functions. It shuts down the embedded server. @subsubheading Return Values None. @node C API problems, Building clients, C Embedded Server func, C @subsection Common questions and problems when using the C API @tindex @code{mysql_query()} @tindex @code{mysql_store_result()} @menu * NULL mysql_store_result:: Why Is It that After @code{mysql_query()} Returns Success, @code{mysql_store_result()} Sometimes Returns @code{NULL}? * Query results:: * Getting unique ID:: * C API linking problems:: @end menu @node NULL mysql_store_result, Query results, C API problems, C API problems @subsubsection @code{mysql_query()} が成功を返した後、@code{mysql_store_result()} が @code{NULL} を返す時があるのは何故？ @code{mysql_query()} の呼び出しが成功した後に @code{mysql_store_result()} が @code{NULL} を返すことがあります。これが 起こったとき、次の条件のどれかの発生を意味します: @itemize @bullet @item @code{malloc()} が失敗した (例えば、結果セットが大き過ぎた場合)。 @item データが読めなかった (接続のエラー)。 @item クエリがデータを返さなかった (@code{INSERT}, @code{UPDATE}, @code{DELETE})。 @end itemize ステートメントが空でない結果を提供するかどうかは @code{mysql_field_count()} の呼び出しによっていつでもチェックできます。 @code{mysql_field_count()} が 0 を返す場合、結果は空で最後のクエリは値を 返さないステートメントです (例えば、@code{INSERT} や @code{DELETE})。 @code{mysql_field_count()} が非 0 値を返す場合、ステートメントは空でない 結果を提供します。 例は@code{mysql_field_count()} 関数の説明を参照してください。 @code{mysql_error()} または @code{mysql_errno()} を呼び出すことによって エラーのテストもできます。 @cindex queries, C API results @menu * Query results:: * Getting unique ID:: * C API linking problems:: @end menu @node Query results, Getting unique ID, NULL mysql_store_result, C API problems @subsubsection クエリから得られる結果は何か？ クエリによって返される結果セットに加えて、次の情報も得ることができます: @itemize @bullet @item @code{mysql_affected_rows()} は、@code{INSERT}, @code{UPDATE} または @code{DELETE} を行なった時の最後のクエリで、影響された行数を返します。 @code{WHERE} 節がない @code{DELETE} が使用されて、テーブルが切り詰められ た場合は例外です。これはとても速いです！ この場合、 @code{mysql_affected_rows()} は影響された行数を 0 と返します。 @item @code{mysql_num_rows()} は結果セットのレコード数を返します。 @code{mysql_store_result()} では、@code{mysql_num_rows()} は @code{mysql_store_result()} が復帰したすぐ後に呼び出すことができます。 @code{mysql_use_result()} では、@code{mysql_num_rows()} は @code{mysql_fetch_row()} ですべてのレコードを取り出した後にだけ呼ぶ出すこ とができます。 @item @code{mysql_insert_id()} は、@code{AUTO_INCREMENT} インデックスを持つテー ブルに行を挿入した最後のクエリによって生成された ID を返します。 @xref{mysql_insert_id, , @code{mysql_insert_id()}}. @item いくつかのクエリ (@code{LOAD DATA INFILE...}, @code{INSERT INTO ... SELECT ...}, @code{UPDATE}) は追加情報を返します。結果は @code{mysql_info()} で返されます。 返す文字列の形式については、@code{mysql_info()} の説明を参照してください。 @code{mysql_info()} は追加情報がない場 合は @code{NULL} ポインタを返します。 @end itemize @cindex unique ID @cindex last row, unique ID @cindex ID, unique @cindex tables, unique ID for last row @node Getting unique ID, C API linking problems, Query results, C API problems @subsubsection 最後に挿入された行のユニーク ID をどのように得られるか？ @code{AUTO_INCREMENT} 属性を持つ項目を含むテーブルにレコードを挿入する場 合、@code{mysql_insert_id()} 関数で与えられた ID を得ることができます。 @code{mysql_query()} に渡すクエリ文字列内の@code{LAST_INSERT_ID()} 関数 を使用することでも、ID を取り出すことができます。 次のコードを実行することで、@code{AUTO_INCREMENT} インデックスが使用され たかどうかチェックできます。これは、クエリが @code{AUTO_INCREMENT} イン デックスを伴う @code{INSERT} だったかどうかもチェックできます: @example if (mysql_error(&mysql)[0] == 0 && mysql_num_fields(result) == 0 && mysql_insert_id(&mysql) != 0) @{ used_id = mysql_insert_id(&mysql); @} @end example 生成された最後の ID は接続毎にサーバ内で維持されています。他のクライアント によって変更はされません。他の @code{AUTO_INCREMENT} 項目を非マジック値 (すなわち、@code{NULL} でなく @code{0} でない値) で更新する場合でも、それは変更 されません。 また、他のテーブルにその ID を挿入しようとする場合、次で行なうことができます: @example INSERT INTO foo (auto,text) VALUES(NULL,'text'); # generate ID by inserting NULL INSERT INTO foo2 (id,text) VALUES(LAST_INSERT_ID(),'text'); # use ID in second table @end example @cindex linking, problems @cindex C API, linking problems @node C API linking problems, , Getting unique ID, C API problems @subsubsection C API でのリンクの問題 C API でリンクする時、いくつかのシステム上では次のエラーになります: @example gcc -g -o client test.o -L/usr/local/lib/mysql -lmysqlclient -lsocket -lnsl Undefined first referenced symbol in file floor /usr/local/lib/mysql/libmysqlclient.a(password.o) ld: fatal: Symbol referencing errors. No output written to client @end example これは、あなたのシステム上では、コンパイル/リンク行の最後に、math ライブ ラリ (@code{-lm}) を含める必要があることを意味します。 @node Building clients, Threaded clients, C API problems, C @subsection Building Client Programs @cindex client programs, building @cindex linking @cindex building, client programs @cindex programs, client If you compile MySQL clients that you've written yourself or that you obtain from a third-party, they must be linked using the @code{-lmysqlclient -lz} option on the link command. You may also need to specify a @code{-L} option to tell the linker where to find the library. For example, if the library is installed in @file{/usr/local/mysql/lib}, use @code{-L/usr/local/mysql/lib -lmysqlclient -lz} on the link command. For clients that use MySQL header files, you may need to specify a @code{-I} option when you compile them (for example, @code{-I/usr/local/mysql/include}), so the compiler can find the header files. To make the above simpler on Unix we have provied the @code{mysql_config} script for you. @xref{mysql_config}. You can use this to compile a MySQL client by as follows: @example CFG=/usr/local/mysql/bin/mysql_config sh -c "gcc -o progname `$CFG --cflags` progname.c `$CFG --libs`" @end example The @code{sh -c} is need to get the shell to not threat the output from @code{mysql_config} as one word. @node Threaded clients, libmysqld, Building clients, C @subsection スレッドクライアントを作る方法 @cindex clients, threaded @cindex threaded clients クライアントは `ほとんど' スレッド安全です。一番大きな問題は @file{net.c} (ソケットから読み込みをするサブルーチンを含むファイル) が割 り込み安全でないことです。これは、サーバからの長い読み込みを中断できるよ うに、自身のアラームを持ちたいだろうという考慮で行なわれました。 If you install interrupt handlers for the @code{SIGPIPE} interrupt, the socket handling should be thread-safe. われわれの Web site で公開している古いバイナリ配布では、 標準クライアントライブラリはスレッドオプションでコンパイルされていません。 (the Windows binaries are by default compiled to be thread safe). Newer binary distributions should have both a normal and a thread-safe client library. スレッド安全クライアント(MySQLサーバーとの通信時に、 他のスレッドがクライアントのスレッドに interrupt をかけたり、 タイムアウトをセットしたりする) を得るためには、@code{-lmysys}, @code{-lstring}, @code{-ldbug} ライブラリとサーバが使用する @code{net_serv.o} を使用しま す。 If you don't need interrupts or timeouts, you can just compile a thread-safe client library @code{(mysqlclient_r)} and use this. @xref{C,, MySQL C API}. In this case you don't have to worry about the @code{net_serv.o} object file or the other MySQL libraries. スレッドクライアントを使用する時、@file{thr_alarm.c} ルーチンを大いに使 用できます。@code{mysys} ライブラリからのルーチンを使用する場合、覚えて おかなければならないことは @code{my_init()} を最初に呼ぶことだけです！ @code{mysql_real_connect()} を除く全ての関数は現在スレッド安全です。スレッ ド安全クライアントライブラリをコンパイルし、それをスレッド安全なマナーで使 用するための方法を、次の注意で説明します。(この @code{mysql_real_connect()} についての注意は、実際には @code{mysql_connect()} にも有効です。しかし @code{mysql_connect()} は推奨 されませんので、とにかく @code{mysql_real_connect()} を使用すべきです。) @code{mysql_real_connect()} をスレッド安全にするためには、クライアントを次の コマンドで再コンパイルする必要があります: @example shell> ./configure --enable-thread-safe-client @end example This will create a thread-safe client library @code{libmysqlclient_r}. @code{--enable-thread-safe-client}. This library is thread safe per connection. You can let two threads share the same connection as long as you do the following: @itemize @bullet @item ２つのスレッドが同じ接続上で同時に MySQL にクエリを送信することは できません。特に @code{mysql_query()} と @code{mysql_store_result()} の間 で、他のスレッドが同じ接続を使用しないことを確実にする必要があります。 @item 多くのスレッドが @code{mysql_store_result()} で取り出された別々の結果セッ トにアクセスできます。 @item @code{mysql_use_result} を使用する場合、結果セットがクローズされるまで、他 のスレッドが同じ接続上で何も尋ねないことを確実にする必要があります。 However, it really is best for threaded clients that share the same connection to use @code{mysql_use_result()}. @item If you want to use multiple threads on the same connection, you must have a mutex lock around your @code{mysql_query()} and @code{mysql_store_result()} call combination. Once @code{mysql_store_result()} is ready, the lock can be released and other threads may query the same connection. @item If you program with POSIX threads, you can use @code{pthread_mutex_lock()} and @code{pthread_mutex_unlock()} to establish and release a mutex lock. @end itemize You need to know the following if you have a thread that is calling MySQL functions which did not create the connection to the MySQL database: When you call @code{mysql_init()} or @code{mysql_connect()}, MySQL will create a thread-specific variable for the thread that is used by the debug library (among other things). If you call a MySQL function, before the thread has called @code{mysql_init()} or @code{mysql_connect()}, the thread will not have the necessary thread-specific variables in place and you are likely to end up with a core dump sooner or later. The get things to work smoothly you have to do the following: @enumerate @item Call @code{my_init()} at the start of your program if it calls any other MySQL function before calling @code{mysql_real_connect()}. @item Call @code{mysql_thread_init()} in the thread handler before calling any MySQL function. @item In the thread, call @code{mysql_thread_end()} before calling @code{pthread_exit()}. This will free the memory used by MySQL thread-specific variables. @end enumerate You may get some errors because of undefined symbols when linking your client with @code{libmysqlclient_r}. In most cases this is because you haven't included the thread libraries on the link/compile line. @node libmysqld, , Threaded clients, C @subsection libmysqld, the Embedded MySQL Server Library @cindex libmysqld @cindex embedded MySQL server library @menu * libmysqld overview:: Overview of the Embedded MySQL Server Library * libmysqld compiling:: Compiling Programs with @code{libmysqld} * libmysqld restrictions:: Restrictions when Using the Embedded MySQL Server * libmysqld options:: Using Option Files with the Embedded Server * libmysqld TODO:: Things left to do in Embedded Server (TODO) * libmysqld example:: A Simple Embedded Server Example * libmysqld licensing:: Licensing the Embedded Server @end menu @node libmysqld overview, libmysqld compiling, libmysqld, libmysqld @subsubsection Overview of the Embedded MySQL Server Library The embedded MySQL server library makes it possible to run a full-featured MySQL server inside the client application. The main benefits are increased speed and more simple management for embedded applications. The API is identical for the embedded MySQL version and the client/server version. To change an old threaded application to use the embedded library, you normally only have to add calls to the following functions: @multitable @columnfractions .25 .70 @item @strong{Function} @tab @strong{When to call} @item @code{mysql_server_init()} @tab Should be called before any other MySQL function is called, preferably early in the @code{main()} function. @item @code{mysql_server_end()} @tab Should be called before your program exits. @item @code{mysql_thread_init()} @tab Should be called in each thread you create that will access MySQL. @item @code{mysql_thread_end()} @tab Should be called before calling @code{pthread_exit()} @end multitable Then you must link your code with @file{libmysqld.a} instead of @file{libmysqlclient.a}. The above @code{mysql_server_xxx} functions are also included in @file{libmysqlclient.a} to allow you to change between the embedded and the client/server version by just linking your application with the right library. @xref{mysql_server_init}. @node libmysqld compiling, libmysqld restrictions, libmysqld overview, libmysqld @subsubsection Compiling Programs with @code{libmysqld} To get a @code{libmysqld} library you should configure MySQL with the @code{--with-embedded-server} option. When you link your program with @code{libmysqld}, you must also include the system-specific @code{pthread} libraries and some libraries that the MySQL server uses. You can get the full list of libraries by executing @code{mysql_config --libmysqld-libs}. The correct flags for compiling and linking a threaded program must be used, even if you do not directly call any thread functions in your code. @node libmysqld restrictions, libmysqld options, libmysqld compiling, libmysqld @subsubsection Restrictions when using the Embedded MySQL Server The embedded server has the following limitations: @itemize @bullet @item No support for ISAM tables. (This is mainly done to make the library smaller) @item No UDF functions. @item No stack trace on core dump. @item No internal RAID support. (This is not normally needed as most OS has nowadays support for big files). @item You can set this up as a server or a master (no replication). @item You can't connect to the embedded server from an outside process with sockets or TCP/IP. @end itemize Some of these limitations can be changed by editing the @file{mysql_embed.h} include file and recompiling MySQL. @node libmysqld options, libmysqld TODO, libmysqld restrictions, libmysqld @subsubsection Using Option Files with the Embedded Server @cindex defaults, embedded The following is the recommended way to use option files to make it easy to switch between a client/server application and one where MySQL is embedded. @xref{Option files}. @itemize @bullet @item Put common options in the @code{[server]} section. These will be read by both MySQL versions. @item Put client/server-specific options in the @code{[mysqld]} section. @item Put embedded MySQL-specific options in the @code{[embedded]} section. @item Put application-specific options in a @code{[ApplicationName_SERVER]} section. @end itemize @node libmysqld TODO, libmysqld example, libmysqld options, libmysqld @subsubsection Things left to do in Embedded Server (TODO) @cindex TODO, embedded server @itemize @bullet @item We are going to provide options to leave out some parts of MySQL to make the library smaller. @item There is still a lot of speed optimisation to do. @item Errors are written to stderr. We will add an option to specify a filename for these. @item We have to change InnoDB to not be so verbose when using in the embedded version. @end itemize @node libmysqld example, libmysqld licensing, libmysqld TODO, libmysqld @subsubsection A Simple Embedded Server Example This example program and makefile should work without any changes on a Linux or FreeBSD system. For other operating systems, minor changes will be needed. This example is designed to give enough details to understand the problem, without the clutter that is a necessary part of a real application. To try out the example, create an @file{test_libmysqld} directory at the same level as the mysql-4.0 source directory. Save the @file{test_libmysqld.c} source and the @file{GNUmakefile} in the directory, and run GNU @file{make} from inside the @file{test_libmysqld} directory. @file{test_libmysqld.c} @example /* * A simple example client, using the embedded MySQL server library */ #include #include #include #include MYSQL *db_connect(const char *dbname); void db_disconnect(MYSQL *db); void db_do_query(MYSQL *db, const char *query); const char *server_groups[] = @{ "test_libmysqld_SERVER", "embedded", "server", NULL @}; int main(int argc, char **argv) @{ MYSQL *one, *two; /* mysql_server_init() must be called before any other mysql * functions. * * You can use mysql_server_init(0, NULL, NULL), and it will * initialise the server using groups = @{ * "server", "embedded", NULL * @}. * * In your $HOME/.my.cnf file, you probably want to put: [test_libmysqld_SERVER] language = /path/to/source/of/mysql/sql/share/english * You could, of course, modify argc and argv before passing * them to this function. Or you could create new ones in any * way you like. But all of the arguments in argv (except for * argv[0], which is the program name) should be valid options * for the MySQL server. * * If you link this client against the normal mysqlclient * library, this function is just a stub that does nothing. */ mysql_server_init(argc, argv, (char **)server_groups); one = db_connect("test"); two = db_connect(NULL); db_do_query(one, "SHOW TABLE STATUS"); db_do_query(two, "SHOW DATABASES"); mysql_close(two); mysql_close(one); /* This must be called after all other mysql functions */ mysql_server_end(); exit(EXIT_SUCCESS); @} static void die(MYSQL *db, char *fmt, ...) @{ va_list ap; va_start(ap, fmt); vfprintf(stderr, fmt, ap); va_end(ap); (void)putc('\n', stderr); if (db) db_disconnect(db); exit(EXIT_FAILURE); @} MYSQL * db_connect(const char *dbname) @{ MYSQL *db = mysql_init(NULL); if (!db) die(db, "mysql_init failed: no memory"); /* * Notice that the client and server use separate group names. * This is critical, because the server will not accept the * client's options, and vice versa. */ mysql_options(db, MYSQL_READ_DEFAULT_GROUP, "test_libmysqld_CLIENT"); if (!mysql_real_connect(db, NULL, NULL, NULL, dbname, 0, NULL, 0)) die(db, "mysql_real_connect failed: %s", mysql_error(db)); return db; @} void db_disconnect(MYSQL *db) @{ mysql_close(db); @} void db_do_query(MYSQL *db, const char *query) @{ if (mysql_query(db, query) != 0) goto err; if (mysql_field_count(db) > 0) @{ MYSQL_RES *res; MYSQL_ROW row, end_row; int num_fields; if (!(res = mysql_store_result(db))) goto err; num_fields = mysql_num_fields(res); while ((row = mysql_fetch_row(res))) @{ (void)fputs(">> ", stdout); for (end_row = row + num_fields; row < end_row; ++row) (void)printf("%s\t", row ? (char*)*row : "NULL"); (void)fputc('\n', stdout); @} (void)fputc('\n', stdout); @} else (void)printf("Affected rows: %lld\n", mysql_affected_rows(db)); return; err: die(db, "db_do_query failed: %s [%s]", mysql_error(db), query); @} @end example @file{GNUmakefile} @example # This assumes the MySQL software is installed in /usr/local/mysql inc := /usr/local/mysql/include/mysql lib := /usr/local/mysql/lib # If you have not installed the MySQL software yet, try this instead #inc := $(HOME)/mysql-4.0/include #lib := $(HOME)/mysql-4.0/libmysqld CC := gcc CPPFLAGS := -I$(inc) -D_THREAD_SAFE -D_REENTRANT CFLAGS := -g -W -Wall LDFLAGS := -static # You can change -lmysqld to -lmysqlclient to use the # client/server library LDLIBS = -L$(lib) -lmysqld -lz -lm -lcrypt ifneq (,$(shell grep FreeBSD /COPYRIGHT 2>/dev/null)) # FreeBSD LDFLAGS += -pthread else # Assume Linux LDLIBS += -lpthread endif # This works for simple one-file test programs sources := $(wildcard *.c) objects := $(patsubst %c,%o,$(sources)) targets := $(basename $(sources)) all: $(targets) clean: rm -f $(targets) $(objects) *.core @end example @node libmysqld licensing, , libmysqld example, libmysqld @subsubsection Licensing the Embedded Server The MySQL source code is covered by the GNU GPL license (@pxref{GPL license}). One result of this is that any program which includes, by linking with @code{libmysqld}, the MySQL source code must be released as free software (under a license compatible with the GPL). We encourage everyone to promote free software by releasing code under the GPL or a compatible license. For those who are not able to do this, another option is to purchase a commercial licence for the MySQL code from MySQL AB. For details, please see @ref{MySQL licenses}. @node Cplusplus, Java, C, Clients @section MySQL C++ APIs @menu * Borland C++:: Borland C++ @end menu @cindex C++ APIs MySQL Connector/C++ (or @code{MySQL++}) is the official MySQL API for C++. More information can be found at @uref{http://www.mysql.com/products/mysql++/}. @node Borland C++, , Cplusplus, Cplusplus @subsection Borland C++ @cindex Borland C++ compiler You can compile the MySQL Windows source with Borland C++ 5.02. (The Windows source includes only projects for Microsoft VC++, for Borland C++ you have to do the project files yourself.) One known problem with Borland C++ is that it uses a different structure alignment than VC++. This means that you will run into problems if you try to use the default @code{libmysql.dll} libraries (that was compiled with VC++) with Borland C++. You can do one of the following to avoid this problem. @itemize @bullet @item You can use the static MySQL libraries for Borland C++ that you can find on @uref{http://www.mysql.com/downloads/os-win32.html}. @item Only call @code{mysql_init()} with @code{NULL} as an argument, not a pre-allocated MYSQL struct. @end itemize @node Java, Python, Cplusplus, Clients @section MySQL Java Connectivity (JDBC) @cindex Java connectivity @cindex JDBC There are 2 supported JDBC drivers for MySQL (the Connector/J driver and the Resin JDBC driver). You can find a copy of the Connector/J driver at @uref{http://www.mysql.com/products/connector-j/} and the Resin driver at @uref{http://www.caucho.com/projects/jdbc-mysql/index.xtp} For documentation consult any JDBC documentation and the driver's own documentation for MySQL-specific features. @node Python, Tcl, Java, Clients @section MySQL Python APIs @cindex Python APIs MySQLdb provides MySQL support for Python, compliant with the Python DB API version 2.0. It can be found at @uref{http://sourceforge.net/projects/mysql-python/}. @node Tcl, Eiffel, Python, Clients @section MySQL Tcl APIs @cindex Tcl APIs MySQLtcl is a simple API for accessing a MySQL database server from the Tcl programming language. It can be found at @uref{http://www.xdobry.de/mysqltcl/}. @node Eiffel, Ruby, Tcl, Clients @section MySQL Eiffel wrapper @cindex Eiffel Wrapper @cindex wrappers, Eiffel Eiffel MySQL is an interface to the MySQL database server using the Eiffel programming language, written by Michael Ravits. It can be found at @uref{http://efsa.sourceforge.net/archive/ravits/mysql.htm}. You can also find this at: @url{http://www.netpedia.net/hosting/newplayer/} @node Ruby, , Eiffel, Clients @section MySQL Ruby API 以下のサイトに、Ruby の MySQL インターフェースがあります。 @uref{http://www.tmtm.org/, www.tmtm.org とみたまさひろ氏の Web ページ} @node Extending MySQL, Problems, Clients, Top @chapter Extending MySQL @menu * MySQL internals:: MySQL Internals * Adding functions:: Adding New Functions to MySQL * Adding procedures:: Adding New Procedures to MySQL @end menu @node MySQL internals, Adding functions, Extending MySQL, Extending MySQL @section MySQL Internals @cindex internals @cindex threads This chapter describes a lot of things that you need to know when working on the MySQL code. If you plan to contribute to MySQL development, want to have access to the bleeding-edge in-between versions code, or just want to keep track of development, follow the instructions in @ref{Installing source tree}. If you are interested in MySQL internals, you should also subscribe to our @code{internals} mailing list. This list is relatively low traffic. For details on how to subscribe, please see @ref{Mailing-list}. All developers at MySQL AB are on the @code{internals} list and we help other people who are working on the MySQL code. Feel free to use this list both to ask questions about the code and to send patches that you would like to contribute to the MySQL project! @menu * MySQL threads:: MySQL threads * MySQL test suite:: MySQL test suite @end menu @node MySQL threads, MySQL test suite, MySQL internals, MySQL internals @subsection MySQL Threads The MySQL server creates the following threads: @itemize @bullet @item The TCP/IP connection thread handles all connection requests and creates a new dedicated thread to handle the authentication and SQL query processing for each connection. @item On Windows NT there is a named pipe handler thread that does the same work as the TCP/IP connection thread on named pipe connect requests. @item The signal thread handles all signals. This thread also normally handles alarms and calls @code{process_alarm()} to force timeouts on connections that have been idle too long. @item If @code{mysqld} is compiled with @code{-DUSE_ALARM_THREAD}, a dedicated thread that handles alarms is created. This is only used on some systems where there are problems with @code{sigwait()} or if one wants to use the @code{thr_alarm()} code in ones application without a dedicated signal handling thread. @item If one uses the @code{--flush_time=#} option, a dedicated thread is created to flush all tables at the given interval. @item Every connection has its own thread. @item Every different table on which one uses @code{INSERT DELAYED} gets its own thread. @item If you use @code{--master-host}, a slave replication thread will be started to read and apply updates from the master. @end itemize @code{mysqladmin processlist} only shows the connection, @code{INSERT DELAYED}, and replication threads. @node MySQL test suite, , MySQL threads, MySQL internals @subsection MySQL Test Suite @cindex mysqltest, MySQL Test Suite @cindex testing mysqld, mysqltest Until recently, our main full-coverage test suite was based on proprietary customer data and for that reason has not been publicly available. The only publicly available part of our testing process consisted of the @code{crash-me} test, a Perl DBI/DBD benchmark found in the @code{sql-bench} directory, and miscellaneous tests located in @code{tests} directory. The lack of a standardised publicly available test suite has made it difficult for our users, as well developers, to do regression tests on the MySQL code. To address this problem, we have created a new test system that is included in the source and binary distributions starting in Version 3.23.29. The current set of test cases doesn't test everything in MySQL, but it should catch most obvious bugs in the SQL processing code, OS/library issues, and is quite thorough in testing replication. Our eventual goal is to have the tests cover 100% of the code. We welcome contributions to our test suite. You may especially want to contribute tests that examine the functionality critical to your system, as this will ensure that all future MySQL releases will work well with your applications. @menu * running mysqltest:: Running the MySQL Test Suite * extending mysqltest:: Extending the MySQL Test Suite * Reporting mysqltest bugs:: Reporting Bugs in the MySQL Test Suite @end menu @node running mysqltest, extending mysqltest, MySQL test suite, MySQL test suite @subsubsection Running the MySQL Test Suite The test system consist of a test language interpreter (@code{mysqltest}), a shell script to run all tests(@code{mysql-test-run}), the actual test cases written in a special test language, and their expected results. To run the test suite on your system after a build, type @code{make test} or @code{mysql-test/mysql-test-run} from the source root. If you have installed a binary distribution, @code{cd} to the install root (eg. @code{/usr/local/mysql}), and do @code{scripts/mysql-test-run}. All tests should succeed. If not, you should try to find out why and report the problem if this is a bug in MySQL. @xref{Reporting mysqltest bugs}. If you have a copy of @code{mysqld} running on the machine where you want to run the test suite you do not have to stop it, as long as it is not using ports @code{9306} and @code{9307}. If one of those ports is taken, you should edit @code{mysql-test-run} and change the values of the master and/or slave port to one that is available. You can run one individual test case with @code{mysql-test/mysql-test-run test_name}. If one test fails, you should test running @code{mysql-test-run} with the @code{--force} option to check if any other tests fails. @node extending mysqltest, Reporting mysqltest bugs, running mysqltest, MySQL test suite @subsubsection Extending the MySQL Test Suite You can use the @code{mysqltest} language to write your own test cases. Unfortunately, we have not yet written full documentation for it - we plan to do this shortly. You can, however, look at our current test cases and use them as an example. The following points should help you get started: @itemize @bullet @item The tests are located in @code{mysql-test/t/*.test} @item A test case consists of @code{;} terminated statements and is similar to the input of @code{mysql} command-line client. A statement by default is a query to be sent to MySQL server, unless it is recognised as internal command (eg. @code{sleep}). @item All queries that produce results@-e.g., @code{SELECT}, @code{SHOW}, @code{EXPLAIN}, etc., must be preceded with @code{@@/path/to/result/file}. The file must contain the expected results. An easy way to generate the result file is to run @code{mysqltest -r < t/test-case-name.test} from @code{mysql-test} directory, and then edit the generated result files, if needed, to adjust them to the expected output. In that case, be very careful about not adding or deleting any invisible characters - make sure to only change the text and/or delete lines. If you have to insert a line, make sure the fields are separated with a hard tab, and there is a hard tab at the end. You may want to use @code{od -c} to make sure your text editor has not messed anything up during edit. We, of course, hope that you will never have to edit the output of @code{mysqltest -r} as you only have to do it when you find a bug. @item To be consistent with our setup, you should put your result files in @code{mysql-test/r} directory and name them @code{test_name.result}. If the test produces more than one result, you should use @code{test_name.a.result}, @code{test_name.b.result}, etc. @item If a statement returns an error, you should on the line before the statement specify with the @code{--error error-number}. The error number can be a list of possible error numbers separated with @code{','}. @item If you are writing a replication test case, you should on the first line of the test file, put @code{source include/master-slave.inc;}. To switch between master and slave, use @code{connection master;} and @code{connection slave;}. If you need to do something on an alternate connection, you can do @code{connection master1;} for the master, and @code{connection slave1;} for the slave. @item If you need to do something in a loop, you can use something like this: @example let $1=1000; while ($1) @{ # do your queries here dec $1; @} @end example @item To sleep between queries, use the @code{sleep} command. It supports fractions of a second, so you can do @code{sleep 1.3;}, for example, to sleep 1.3 seconds. @item To run the slave with additional options for your test case, put them in the command-line format in @code{mysql-test/t/test_name-slave.opt}. For the master, put them in @code{mysql-test/t/test_name-master.opt}. @item If you have a question about the test suite, or have a test case to contribute, e-mail to @email{internals@@lists.mysql.com}. As the list does not accept attachments, you should ftp all the relevant files to: @uref{ftp://support.mysql.com/pub/mysql/Incoming/} @end itemize @node Reporting mysqltest bugs, , extending mysqltest, MySQL test suite @subsubsection Reporting Bugs in the MySQL Test Suite If your MySQL version doesn't pass the test suite you should do the following: @itemize @bullet @item Don't send a bug report before you have found out as much as possible of what when wrong! When you do it, please use the @code{mysqlbug} script so that we can get information about your system and @code{MySQL} version. @xref{Bug reports}. @item Make sure to include the output of @code{mysql-test-run}, as well as contents of all @code{.reject} files in @code{mysql-test/r} directory. @item If a test in the test suite fails, check if the test fails also when run by its own: @example cd mysql-test mysql-test-run --local test-name @end example If this fails, then you should configure MySQL with @code{--with-debug} and run @code{mysql-test-run} with the @code{--debug} option. If this also fails send the trace file @file{var/tmp/master.trace} to ftp://support.mysql.com/pub/mysql/secret so that we can examine it. Please remember to also include a full description of your system, the version of the mysqld binary and how you compiled it. @item Try also to run @code{mysql-test-run} with the @code{--force} option to see if there is any other test that fails. @item If you have compiled MySQL yourself, check our manual for how to compile MySQL on your platform or, preferable, use one of the binaries we have compiled for you at @uref{http://www.mysql.com/downloads/}. All our standard binaries should pass the test suite ! @item If you get an error, like @code{Result length mismatch} or @code{Result content mismatch} it means that the output of the test didn't match exactly the expected output. This could be a bug in MySQL or that your mysqld version produces slight different results under some circumstances. Failed test results are put in a file with the same base name as the result file with the @code{.reject} extension. If your test case is failing, you should do a diff on the two files. If you cannot see how they are different, examine both with @code{od -c} and also check their lengths. @item If a test fails totally, you should check the logs file in the @code{mysql-test/var/log} directory for hints of what went wrong. @item If you have compiled MySQL with debugging you can try to debug this by running @code{mysql-test-run} with the @code{--gdb} and/or @code{--debug} options. @xref{Making trace files}. If you have not compiled MySQL for debugging you should probably do that. Just specify the @code{--with-debug} options to @code{configure}! @xref{Installing source}. @end itemize @node Adding functions, Adding procedures, MySQL internals, Extending MySQL @section MySQL への新しい関数の追加 @cindex functions, new @cindex adding, new functions @cindex user-defined functions, adding @cindex UDFs, defined @cindex functions, user-defined There are two ways to add new functions to MySQL: @itemize @bullet @item ユーザ定義関数(UDF:user-definable function)インタフェースを通して関数を追 加できます。 ユーザ定義関数は、@code{CREATE FUNCTION} と @code{DROP FUNCTION} ステー トメントを使用して、動的に追加、削除されます。 @xref{CREATE FUNCTION, , @code{CREATE FUNCTION}}. @item ネイティブ(ビルトイン) @strong{MySQL} 関数として関数を追加できます。 ネイティブ関数は @code{mysqld} サーバに統合され、恒久的に有効になります。 @end itemize それぞれの方法には、有利な点と不利な点があります: @itemize @bullet @item ユーザ定義関数を書く場合、サーバ自身に追加するオブジェクトファイルをイン ストールする必要があります。関数をサーバに統合する場合あそれを行なう必要 はありません。 @item UDF をバイナリ @strong{MySQL} 配布に追加することができます。ネイティブ関 数はソース配布の変更が必要です。 @item @strong{MySQL} 配布をアップグレードする場合、前にインストールされた UDF の使用を継続できます。ネイティブ関数では、アップグレードの度に変更を繰り 返す必要があります。 @end itemize 新しい関数を追加するためにどちらの方法を使用しても、@code{ABS()} や @code{SOUNDEX()} のようなネイティブ関数と同じように使用することができま す。 @menu * CREATE FUNCTION:: @code{CREATE FUNCTION/DROP FUNCTION} Syntax * Adding UDF:: Adding a new user-definable function * Adding native function:: Adding a new native function @end menu @node CREATE FUNCTION, Adding UDF, Adding functions, Adding functions @subsection @code{CREATE FUNCTION/DROP FUNCTION} Syntax @findex CREATE FUNCTION @findex DROP FUNCTION @cindex deleting, function @cindex function, deleting @findex UDF functions @findex User-defined functions @findex Functions, user-defined @example CREATE [AGGREGATE] FUNCTION function_name RETURNS @{STRING|REAL|INTEGER@} SONAME shared_library_name DROP FUNCTION function_name @end example A user-definable function (UDF) is a way to extend MySQL with a new function that works like native (built in) MySQL functions such as @code{ABS()} and @code{CONCAT()}. @code{AGGREGATE} is a new option for MySQL Version 3.23. An @code{AGGREGATE} function works exactly like a native MySQL @code{GROUP} function like @code{SUM} or @code{COUNT()}. @code{CREATE FUNCTION} saves the function's name, type, and shared library name in the @code{mysql.func} system table. You must have the @code{INSERT} and @code{DELETE} privileges for the @code{mysql} database to create and drop functions. All active functions are reloaded each time the server starts, unless you start @code{mysqld} with the @code{--skip-grant-tables} option. In this case, UDF initialisation is skipped and UDFs are unavailable. (An active function is one that has been loaded with @code{CREATE FUNCTION} and not removed with @code{DROP FUNCTION}.) For instructions on writing user-definable functions, see @ref{Adding functions}. For the UDF mechanism to work, functions must be written in C or C++, your operating system must support dynamic loading and you must have compiled @code{mysqld} dynamically (not statically). Note that to make @code{AGGREGATE} work, you must have a @code{mysql.func} table that contains the column @code{type}. If this is not the case, you should run the script @code{mysql_fix_privilege_tables} to get this fixed. @node Adding UDF, Adding native function, CREATE FUNCTION, Adding functions @subsection 新しいユーザ定義関数の追加 @cindex adding, user-definable functions @cindex user-defined functions, adding @cindex functions, user-definable, adding @menu * UDF calling:: UDF Calling Sequences * UDF aggr. calling:: * UDF arguments:: Argument Processing * UDF return values:: Return Values and Error Handling * UDF compiling:: Compiling and Installing User-definable Functions @end menu UDF 機構が動作するためには、関数は C か C++ で書かれる必要があり、OS が 動的ローディングをサポートする必要があります。@strong{MySQL} ソース配布 は @file{sql/udf_example.cc} を含んでいて、これは５つの新しい関数を定義 しています。UDF の呼び出し方法がどのように働くかはこのファイルを参考にし てください。 For @code{mysqld} to be able to use UDF functions, you should configure MySQL with @code{--with-mysqld-ldflags=-rdynamic} The reason is that to on many platforms (including Linux) you can load a dynamic library (with @code{dlopen()}) from a static linked program, which you would get if you are using @code{--with-mysqld-ldflags=-all-static} If you want to use an UDF that needs to access symbols from @code{mysqld} (like the @code{methaphone} example in @file{sql/udf_example.cc} that uses @code{default_charset_info}), you must link the program with @code{-rdynamic} (see @code{man dlopen}). SQL ステートメントで使用したいそれぞれの関数について、対応する C (または C++) 関数を定義すべきです。下の説明では、名前 ``xxx'' がサンプル関数名と して使用されています。SQL と C/C++ 使用法を distinquish するために、 @code{XXX()} (大文字) は SQL 関数呼び出しを表わし、@code{xxx()} (小文字) は C/C++ 関数呼び出しを表わします。 @code{XXX()} のインタフェースを実装するために書く C/C++ 関数は: @table @asis @item @code{xxx()} (必要) メイン関数。これは関数結果が計算されるところです。SQL 型と C/C++ 関数の 戻り値型の対応は次に示します: @multitable @columnfractions .15 .15 @item @strong{SQL type} @tab @strong{C/C++ type} @item @code{STRING} @tab @code{char *} @item @code{INTEGER} @tab @code{long long} @item @code{REAL} @tab @code{double} @end multitable @item @code{xxx_init()} (オプション) @code{xxx()} の初期化関数。これは次のように使用されます: @itemize @bullet @item @code{XXX()} の引数の数のチェック @item 引数が要求される型かどうかのチェック、また、メイン関数が呼ばれる時に望む 型に引数を強制するように @strong{MySQL} に伝える @item メイン関数が必要とするメモリの割り当て @item 結果の最大長の指定 @item (@code{REAL} 関数では) 小数部の最大桁数の指定 @item 結果が @code{NULL} になり得るかどうかの指定 @end itemize @item @code{xxx_deinit()} (オプション) @code{xxx()} の終了関数(deinitialization function)。これは初期化関数によっ て割り当てられたメモリを解放すべきです。 @end table SQL ステートメントが @code{XXX()} を呼び出すとき、@strong{MySQL} は引数 チェックやメモリ割り当てのように、必要なセットアップを行なわせるために、 初期化関数 @code{xxx_init()} を呼び出します。@code{xxx_init()} がエラー を返す場合、SQL ステートメントはエラーメッセージと共に異常終了し、メイン 関数と終了関数は呼び出されません。そうでなければ、メイン関数 @code{xxx()} が各行毎に呼び出されます。全ての行が処理された後、終了関数 @code{xxx_deinit()} が、必要な掃除を行なうために、呼び出されます。 For aggregate functions (like @code{SUM()}), you must also provide the llowing functions: @table @asis @item @code{xxx_reset()} (required) Reset sum and insert the argument as the initial value for a new group. @item @code{xxx_add()} (required) Add the argument to the old sum. @end table When using aggregate UDF functions MySQL works the following way: @enumerate @item Call @code{xxx_init()} to let the aggregate function allocate the memory it will need to store results. @item Sort the table according to the @code{GROUP BY} expression. @item For the first row in a new group, call the @code{xxx_reset()} function. @item For each new row that belongs in the same group, call the @code{xxx_add()} function. @item When the group changes or after the last row has been processed, call @code{xxx()} to get the result for the aggregate. @item Repeat 3-5 until all rows has been processed @item Call @code{xxx_deinit()} to let the UDF free any memory it has allocated. @end enumerate 全ての関数はスレッド安全でなくてはいけません(メイン関数だけでなく、初期 化関数と終了関数も同様です)。これは変更されうるグローバル変数や静的変数 を割り当てることは許されないことを意味します！ メモリが必要な場合は、 @code{xxx_init()} で割り当て、@code{xxx_deinit()} でそれを解放すべきです。 @node UDF calling, UDF aggr. calling, Adding UDF, Adding UDF @subsubsection UDF Calling Sequences @cindex calling sequences for simple functions, UDF メイン関数は下に示すように宣言されるべきです。戻り値型と引数は、 @code{CREATE FUNCTION} ステートメントで、SQL 関数 @code{XXX()} の戻り値 を@code{STRING}, @code{INTEGER}, @code{REAL} のどれに宣言するかに依存し て異なることに注意してください: @noindent @code{STRING} 関数では: @example char *xxx(UDF_INIT *initid, UDF_ARGS *args, char *result, unsigned long *length, char *is_null, char *error); @end example @noindent @code{INTEGER} 関数では: @example long long xxx(UDF_INIT *initid, UDF_ARGS *args, char *is_null, char *error); @end example @noindent @code{REAL} 関数では: @example double xxx(UDF_INIT *initid, UDF_ARGS *args, char *is_null, char *error); @end example 初期化と終了関数は次のように宣言します @example my_bool xxx_init(UDF_INIT *initid, UDF_ARGS *args, char *message); void xxx_deinit(UDF_INIT *initid); @end example @code{initid} 引数は３つの関数全てに渡されます。これは @code{UDF_INIT} 構造体を示し、関数間で情報を伝達するために使用されます。@code{UDF_INIT} 構造体のメンバは下に一覧します。初期化関数は変更したい全てのメンバを埋め るべきです。(メンバにデフォルトを使用するには、未変更のままにしてくださ い。) @table @code @item my_bool maybe_null @code{xxx()} が @code{NULL} を返す場合、@code{xxx_init()} は @code{maybe_null} を @code{1} に設定すべきです。デフォルト値は、引数のい ずれかが @code{maybe_null} として宣言された場合、@code{1} です。 @item unsigned int decimals 小数部の桁数。デフォルト値はメイン関数に渡される引数の小数部の最大桁数で す。(例えば、関数に @code{1.34}, @code{1.345}, @code{1.3} が渡された場合、 デフォルトは 3 です。@code{1.345} が 3 桁の小数部を持つためです。) @item unsigned int max_length 文字列結果の最大長。デフォルト値は関数の戻り値型に依存して異なります。文 字列関数では、デフォルトは最も長い引数の長さです。整数関数では、デフォル トは 21 桁です。実数関数では、デフォルトは 13 に @code{initid->decimals} で示される小数部の桁数を加えたものです。(数値関数では、長さは符号と小数 点文字を含みます。) If you want to return a blob, you can set this to 65K or 16M; this memory is not allocated but used to decide which column type to use if there is a need to temporary store the data. @item char *ptr それ自身の目的のために関数が使用できるポインタです。例えば、関数は割り当 てたメモリを関数間で伝達するために、@code{initid->ptr} を使用できます。 @code{xxx_init()} では、メモリを獲得し、このポインタに割り当てます: @example initid->ptr = allocated_memory; @end example @code{xxx()} と @code{xxx_deinit()} では、@code{initid->ptr} を参照して、 メモリを使用または解放します。 @end table @node UDF aggr. calling, UDF arguments, UDF calling, Adding UDF @subsubsection UDF Calling Sequences for aggregate functions @cindex calling sequences for aggregate functions, UDF Here follows a description of the different functions you need to define when you want to create an aggregate UDF function. @example char *xxx_reset(UDF_INIT *initid, UDF_ARGS *args, char *is_null, char *error); @end example This function is called when MySQL finds the first row in a new group. In the function you should reset any internal summary variables and then set the given argument as the first argument in the group. In many cases this is implemented internally by reseting all variables and then calling @code{xxx_add()}. @example char *xxx_add(UDF_INIT *initid, UDF_ARGS *args, char *is_null, char *error); @end example This function is called for all rows that belongs to the same group, except for the first row. In this you should add the value in UDF_ARGS to your internal summary variable. The @code{xxx()} function should be declared identical as when you define a simple UDF function. @xref{UDF calling}. This function is called when all rows in the group has been processed. You should normally never access the @code{args} variable here but return your value based on your internal summary variables. All argument processing in @code{xxx_reset()} and @code{xxx_add()} should be done identically as for normal UDF functions. @xref{UDF arguments}. The return value handling in @code{xxx()} should be done identically as for a normal UDF. @xref{UDF return values}. The pointer argument to @code{is_null} and @code{error} is the same for all calls to @code{xxx_reset()}, @code{xxx_add()} and @code{xxx()}. You can use this to remember that you got an error or if the @code{xxx()} function should return @code{NULL}. Note that you should not store a string into @code{*error}! This is just a 1 byte flag! @code{is_null} is reset for each group (before calling @code{xxx_reset()}. @code{error} is never reset. If @code{isnull} or @code{error} are set after @code{xxx()} then MySQL will return @code{NULL} as the result for the group function. @node UDF arguments, UDF return values, UDF aggr. calling, Adding UDF @subsubsection 引数処理 @cindex argument processing @cindex processing, arguments @code{args} 引数は次に示すメンバを持つ @code{UDF_ARGS} 構造体へのポイン タです: @table @code @item unsigned int arg_count 引数の数。関数が特定の引数の数で呼び出されることを期待する場合は、初期化 関数でこの値をチェックしてください。例えば: @example if (args->arg_count != 2) @{ strcpy(message,"XXX() requires two arguments"); return 1; @} @end example @item enum Item_result *arg_type 引数の型。可能な型の値は @code{STRING_RESULT}, @code{INT_RESULT}, @code{REAL_RESULT} です。 引数が与えられた型であることと、そうでない場合エラーを返すことを確実にす るために、初期化関数で @code{arg_type} 配列をチェックしてください。例えば: @example if (args->arg_type[0] != STRING_RESULT || args->arg_type[1] != INT_RESULT) @{ strcpy(message,"XXX() requires a string and an integer"); return 1; @} @end example 関数の引数が特定の型を要求するための代案として、初期化関数を使用して、 @code{arg_type} 要素を求める型に設定できます。これは @strong{MySQL} に @code{xxx()} の各呼び出しにこれらの型を引数に強制するようにさせます。例 えば、最初の２つの引数に文字列と整数を強制するように指定するには、 @code{xxx_init()} で次を行なってください: @example args->arg_type[0] = STRING_RESULT; args->arg_type[1] = INT_RESULT; @end example @item char **args @code{args->args} は、関数が呼ばれる時の引数の一般的な特性について、情報 を初期化関数に伝達します。定数引数 @code{i} について、 @code{args->args[i]} は引数値のをポイントします。(値への正しいアクセス方 法については後述。)非定数引数について、@code{args->args[i]} は @code{0} です。定数引数は定数だけを使用する表現で、@code{3}, @code{4*7-2}, @code{SIN(3.14)} などです。非定数引数は行から行に変更される値を参照する 表現で、項目名や非定数引数で呼び出される関数などです。 メイン関数のそれぞれの呼び出しについて、@code{args->args} は現在処理され ている行に渡される実際の引数を含んでいます。 関数は次のように引数 @code{i} を参照できます: @itemize @bullet @item @code{STRING_RESULT} 型の引数は、バイナリデータまたは任意の長さのデータ の処理を許すため、文字列ポインタ＋長さとして与えられます。文字列内容は @code{args->args[i]} として有効で、文字列長は @code{args->lengths[i]} で す。文字列は NULL 終端とみなすべきではありません。 @item @code{INT_RESULT} 型の引数について、@code{args->args[i]} を @code{long long} 値にキャストする必要があります: @example long long int_val; int_val = *((long long*) args->args[i]); @end example @item For an argument of type @code{REAL_RESULT}, you must cast @code{args->args[i]} to a @code{double} value: @example double real_val; real_val = *((double*) args->args[i]); @end example @end itemize @item unsigned long *lengths 初期化関数では、@code{lengths} 配列は各引数についての最大文字列長を示し ます。メイン関数の各呼び出しについては、@code{lengths} は、現在処理され ている行に渡される任意の文字列引数の実際の長さを含んでいます。 @code{INT_RESULT}, @code{REAL_RESULT} 型の引数については、@code{lengths} はまだ引数の最大長を含んでいます(初期化関数については)。 @end table @node UDF return values, UDF compiling, UDF arguments, Adding UDF @subsubsection 戻り値とエラー処理 @cindex UDFs, return values @cindex return values, UDFs @cindex errors, handling for UDFs @cindex handling, errors 初期化関数は、エラーが無い場合は @code{0} を、そうでなければ @code{1} を 返すべきです。エラーが発生する場合は、@code{xxx_init()} は NULL 終端エラー メッセージを @code{message} パラメータに格納すべきです。このメッセージは クライアントに返されます。メッセージバッファは @code{MYSQL_ERRMSG_SIZE} 文字長ですが、80 文字より小さく保つように試みるべきです。標準的な端末画 面の幅にフィットするようにです。 メイン関数 @code{xxx()} の返す値は @code{long long} と @code{double} 関 数については関数値です。文字列関数については、@code{result} と @code{length} 引数で文字列が返されます。@code{result} は少なくとも 255 バイト長のバッファです。これらに内容と戻り値の長さを設定してください。例 えば: @example memcpy(result, "result string", 13); *length = 13; @end example The @code{result} buffer that is passed to the calc function is 255 byte big. If your result fits in this, you don't have to worry about memory allocation for results. あなたの文字列関数が 255 バイトよりも長い文字列を返す必要がある場合、 @code{xxx_init()} 関数または @code{xxx()} 関数内で @code{malloc()} で領域 を割り当て、@code{xxx_deinit()} 関数でそれを解放する必要があります。将来の @code{xxx()} 呼び出しによって再利用されるように、割り当てたメモリを @code{UDF_INIT} 構造体の @code{ptr} スロットに格納できます。 @xref{UDF calling}. メイン関数で @code{NULL} 値の戻り値を示すには、@code{is_null} を @code{1} に設定してください: @example *is_null = 1; @end example To indicate an error return in the main function, set the @code{error} parameter to @code{1}: @example *error = 1; @end example @code{xxx()} が任意の行について @code{*error} に @code{1} を設定する場合、 関数値は現在の行についてと、その後の @code{XXX()} が呼び出されるステート メントによって処理される任意の行について @code{NULL} です。(@code{xxx()} は続く行については呼び出しさえされません。) @strong{注意}: 3.22.10 より 前の @strong{MySQL} バージョンでは、@code{*error} と @code{*is_null} の 両方に設定すべきです: @example *error = 1; *is_null = 1; @end example @node UDF compiling, , UDF return values, Adding UDF @subsubsection ユーザ定義関数のコンパイルとインストール @cindex compiling, user-defined functions @cindex UDFs, compiling @cindex installing, user-defined functions UDF を実装するファイルはサーバが動作するホスト上でコンパイルされインストー ルされないければなりません。この処理はサンプル UDF ファイル @file{udf_example.cc} について次に説明します。これは @strong{MySQL} ソー ス配布に含まれています。このファイルは次の関数を含みます: @itemize @bullet @item @code{metaphon()} は文字列引数の metaphon 文字列を返します。これは時には soundex 文字列ですが、さらに英語用に調整されています。 @item @code{myfunc_double()} は引数の文字の ASCII 値の合計を引数の長さの合計で 割った値を返します。 @item @code{myfunc_int()} は引数の長さの合計を返します。 @item @code{sequence([const int])} returns an sequence starting from the given number or 1 if no number has been given. @item @code{lookup()} はホスト名の IP 番号を返します。 @item @code{reverse_lookup()} は IP 番号のホスト名を返します。この関数は文字列 @code{"xxx.xxx.xxx.xxx"} または４つの数値とともに呼ばれます。 @end itemize 動的ロード可能ファイルは、次のような何らかのコマンドを使用して、共有オブ ジェクトファイルとしてコンパイルされるべきです: @example shell> gcc -shared -o udf_example.so myfunc.cc @end example @strong{MySQL} ソースツリーの @file{sql} ディレクトリ内で次のコマンドを 実行することにより、システムのコンパイラオプションを簡単に正しく見つけ出 すことができます: @example shell> make udf_example.o @end example @code{make} が表示するものに似たコンパイルコマンドを実行すべきですが、行 末近くの @code{-c} オプションを取り除いて、@code{-o udf_example.so} を行 末につけてください。(いくつかのシステムでは、コマンドに @code{-c} を残す 必要があります。) UDF を含む共有オブジェクトをコンパイルすると、それをインストールしてその ことを @strong{MySQL} に知らせる必要があります。@file{udf_example.cc} か らの共有オブジェクトのコンパイルは、@file{udf_example.so} のような何かの ファイル名を提供します(実際の名前はプラットフォームによって変わります)。 このファイルを @file{/usr/lib} のような @code{ld} が探すどこかのディレク トリにコピーしてください。多くのシステムでは、@code{LD_LIBRARY} または @code{LD_LIBRARY_PATH} 環境変数を設定して、UDF 関数ファイルがあるディレ クトリを示すことができます。@code{dlopen} マニュアルページはシステム上で 使用すべき変数を教えてくれます。これを @code{mysql.server} または @code{safe_mysqld} スタートアップスクリプトに設定し、 @code{mysqld} を再起動すべきです。 ライブラリがインストールされた後、@code{mysqld} に新しい関数について次の コマンドで通知すべきです: @example mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "udf_example.so"; mysql> CREATE FUNCTION myfunc_double RETURNS REAL SONAME "udf_example.so"; mysql> CREATE FUNCTION myfunc_int RETURNS INTEGER SONAME "udf_example.so"; mysql> CREATE FUNCTION lookup RETURNS STRING SONAME "udf_example.so"; mysql> CREATE FUNCTION reverse_lookup -> RETURNS STRING SONAME "udf_example.so"; mysql> CREATE AGGREGATE FUNCTION avgcost -> RETURNS REAL SONAME "udf_example.so"; @end example 関数は @code{DROP FUNCTION} を使用して削除できます: @example mysql> DROP FUNCTION metaphon; mysql> DROP FUNCTION myfunc_double; mysql> DROP FUNCTION myfunc_int; mysql> DROP FUNCTION lookup; mysql> DROP FUNCTION reverse_lookup; mysql> DROP FUNCTION avgcost; @end example @code{CREATE FUNCTION} と @code{DROP FUNCTION} ステートメントは @code{mysql} データベース内のシステムテーブル @code{func} を更新します。 関数の名前、型、共有ライブラリ名はテーブルに保存されます。作成と破棄機能 のためには、@code{mysql} データベースに @code{INSERT} と @code{DELETE} 権限を持つ必要があります。 既に生成してある関数を追加するために @code{CREATE FUNCTION} を使用すべき ではありません。関数の再インストールが必要な場合は、@code{DROP FUNCTION} でそれを削除し、それから @code{CREATE FUNCTION} で再インストールすべきで す。例えば、関数の新しいバージョンの再コンパイルをした場合、 @code{mysqld} が新しいバージョンを得るために、これを行なう必要があるでしょ う。そうでなければ、サーバは古いバージョンの使用を継続します。 @code{mysqld} を @code{--skip-grant-tables} オプションで起動しなくても、 有効な関数はサーバの開始毎に再読み込みされます。この場合、UDF 初期化は飛 ばされ、UDF が無効になります。(有効な関数は @code{CREATE FUNCTION} でロー ドされているもので、@code{DROP FUNCTION} で削除されていないものです。) @node Adding native function, , Adding UDF, Adding functions @subsection 新しいネイティブ関数の追加 @cindex adding, native functions @cindex native functions, adding @cindex functions, native, adding ネイティブ関数を追加するためのプロシジャを以下に示します。バイナリ配布に はネイティブ関数を追加できないことに注意してください。プロシジャは @strong{MySQL} ソースコードの変更を必要とするためです。@strong{MySQL} を ソース配布から自分でコンパイルする必要があります。また、@strong{MySQL} の他のバージョンに移行する場合(例えば、新しいバージョンがリリースされた 時)、新しいバージョンでこのプロシジャを繰り返す必要があります。 新しいネイティブ @strong{MySQL} 関数を追加するためには、次のステップに従っ てください: @enumerate @item @code{sql_functions[]} 配列内で関数名を定義している @file{lex.h} に１行 追加してください。 @item If the function prototype is simple (just takes zero, one, two or three arguments), you should in lex.h specify SYM(FUNC_ARG#) (where # is the number of arguments) as the second argument in the @code{sql_functions[]} array and add a function that creates a function object in @file{item_create.cc}. Take a look at @code{"ABS"} and @code{create_funcs_abs()} for an example of this. If the function prototype is complicated (for example takes a variable number of arguments), you should add two lines to @file{sql_yacc.yy}. 一つは、@code{yacc} が定義す べきプリプロセッサシンボルを指示します(これはファイルの先頭に追加すべき です)。それから関数パラメータを定義し、これらのパラメータとともに ``item'' を @code{simple_expr} パース規則に追加します。例えば、これがど のように動作するかを見るには、@file{sql_yacc.yy} 内の @code{ATAN} の 全ての出来事をチェックしてください。 @item @file{item_func.h} 内で、関数が数値または文字列のどちらを返すかに依存し て、@code{Item_num_func} または @code{Item_str_func} から継承するクラス を宣言してください。 @item @file{item_func.cc} 内で、数値または文字列のどちらの関数を定義するかに依 存して、次の宣言の一つを追加してください: @example double Item_func_newname::val() longlong Item_func_newname::val_int() String *Item_func_newname::Str(String *str) @end example If you inherit your object from any of the standard items (like @code{Item_num_func} you probably only have to define one of the above functions and let the parent object take care of the other functions. For example, the @code{Item_str_func} class defines a @code{val()} function that executes @code{atof()} on the value returned by @code{::str()}. @item おそらく次のオブジェクト関数も定義すべきです @example void Item_func_newname::fix_length_and_dec() @end example この関数は与えられた引数に基づいて少なくとも @code{max_length} を計算す べきです。@code{max_length} は関数が返し得る文字の最大数です。この関数は、 メイン関数が @code{NULL} 値を返すことがない場合は、@code{maybe_null = 0} も設定すべきです。関数は、引数の @code{maybe_null} 変数をチェックするこ とで、関数の任意の引数が @code{NULL} を返しうるかどうかをチェックできま す。 You can take a look at @code{Item_func_mod::fix_length_and_dec} for a typical example of how to do this. @end enumerate 全ての関数はスレッド安全である必要があります (In other words, don't use any global or static variables in the functions without protecting them with mutexes). If you want to return @code{NULL}, from @code{::val()}, @code{::val_int()} or @code{::str()} you should set @code{null_value} to 1 and return 0. @code{::str()} オブジェクト関数については、次のいくつかの追加検討事項があ ります: @itemize @bullet @item @code{String *str} 引数は、結果を保持するために使用される文字列バッファ を提供します。 (For more information about the @code{String} type, take a look at the @file{sql_string.h} file.) @item The @code{::str()} function should return the string that holds the result or @code{(char*) 0} if the result is @code{NULL}. @item 全ての現在の文字列関数は、絶対に必要でない限り、メモリ割り当てを避けるよ うに試みてください！ @end itemize @node Adding procedures, , Adding functions, Extending MySQL @section MySQLにプロシージャを追加する @cindex procedures, adding @cindex adding, procedures @cindex new procedures, adding @strong{MySQL} ではC++で書かれたプロシージャを定義することが できます。 これらのプロシージャを使うとデータが クライアントに送信される前にクエリー内でデータにアクセス、 修正することが可能です。 データの修正は列単位、あるいは グループ単位(@code{GROUP BY})で行えます。 プロシージャを使って何ができるかをご覧いただくために、 @strong{MySQL} バージョン3.23を使ったサンプルを用意しました。 さらに Contrib ディレクトリにある 'mylua' を参考にされることをお薦めします。 @xref{Contrib}。 myluaではLUA言語を使って、 ランタイム時にプロシージャを @code{mysqld} にロードすることができます。 Additionally we recommend you to take a look at @code{mylua}. With this you can use the LUA language to load a procedure at runtime into @code{mysqld}. @menu * procedure analyse:: プロシージャ分析 * Writing a procedure:: Writing a procedure. @end menu @node procedure analyse, Writing a procedure, Adding procedures, Adding procedures @subsection プロシージャ分析 @code{analyse([max elements,[max memory]])} このプロシージャは @file{sql/sql_analyse.cc} によって定義されています。 クエリーの結果を調べ、 分析結果を返します： @itemize @bullet @item @code{max elements} (デフォルト値は256)とは、 一つの行において @code{analyse} プロシージャが認識する値の数(重複するものは除く)の 最大値です。 最大エレメント数は @code{analyse} プロシージャがその行に 最適なデータ型が @code{ENUM} 型であるかどうかを判別するために使 われます。 @item @code{max memory}(デフォルト値は8192)とは、 @code{analyse} プロシージャが 1つの行に含まれる重複しない全ての値を探し出す際に、 1つの行に 割り当てるメモリーの最大サイズです。 @end itemize @example SELECT ... FROM ... WHERE ... PROCEDURE ANALYSE([max elements,[max memory]]) @end example @node Writing a procedure, , procedure analyse, Adding procedures @subsection プロシージャの記述 今のところ、 この項目にはソースコードしかありません。 プロシージャに関する全ての情報は以下のファイルにありますのでご覧下さい： @itemize @bullet @item @file{sql/sql_analyse.cc} @item @file{sql/procedure.h} @item @file{sql/procedure.cc} @item @file{sql/sql_select.cc} @end itemize @node Problems, Contrib, Extending MySQL, Top @appendix Problems and Common Errors @cindex problems, common errors @cindex errors, common @menu * What is crashing:: How to determine what is causing problems * Common errors:: Common Errors When Using MySQL * Installation Issues:: Installation Related Issues * Administration Issues:: Administration Related Issues * Query Issues:: Query Related Issues * Table Definition Issues:: Table Definition Related Issues @end menu This chapter lists some common problems and error messages that users have run into. You will learn how to figure out what the problem is, and what to do to solve it. You will also find proper solutions to some common problems. @node What is crashing, Common errors, Problems, Problems @appendixsec How to Determine What Is Causing Problems When you run into problems, the first thing you should do is to find out which program / piece of equipment is causing problems: @itemize @bullet @item If you have one of the following symptoms, then it is probably a hardware (like memory, motherboard, CPU, or hard disk) or kernel problem: @itemize @minus @item The keyboard doesn't work. This can normally be checked by pressing Caps Lock. If the Caps Lock light doesn't change you have to replace your keyboard. (Before doing this, you should try to reboot your computer and check all cables to the keyboard.) @item The mouse pointer doesn't move. @item The machine doesn't answer to a remote machine's pings. @item Different, unrelated programs don't behave correctly. @item If your system rebooted unexpectedly (a faulty user level program should @strong{never} be able to take down your system). @end itemize In this case you should start by checking all your cables and run some diagnostic tool to check your hardware! You should also check if there are any patches, updates, or service packs for your operating system that could likely solve your problems. Check also that all your libraries (like glibc) are up to date. It's always good to use a machine with ECC memory to discover memory problems early! @item If your keyboard is locked up, you may be able to fix this by logging into your machine from another machine and execute @code{kbd_mode -a} on it. @item Please examine your system log file (/var/log/messages or similar) for reasons for your problems. If you think the problem is in MySQL then you should also examine MySQL's log files. @xref{Update log}. @item If you don't think you have hardware problems, you should try to find out which program is causing problems. Try using @code{top}, @code{ps}, @code{taskmanager}, or some similar program, to check which program is taking all CPU or is locking the machine. @item Check with @code{top}, @code{df}, or a similar program if you are out of memory, disk space, open files, or some other critical resource. @item If the problem is some runaway process, you can always try to kill it. If it doesn't want to die, there is probably a bug in the operating system. @end itemize If after you have examined all other possibilities and you have concluded that it's the MySQL server or a MySQL client that is causing the problem, it's time to do a bug report for our mailing list or our support team. In the bug report, try to give a very detailed description of how the system is behaving and what you think is happening. You should also state why you think it's MySQL that is causing the problems. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you examine your system. Use the 'cut and paste' method for any output and/or error messages from programs and/or log files! Try to describe in detail which program is not working and all symptoms you see! We have in the past received many bug reports that just state "the system doesn't work". This doesn't provide us with any information about what could be the problem. If a program fails, it's always useful to know: @itemize @bullet @item Has the program in question made a segmentation fault (core dumped)? @item Is the program taking up the whole CPU? Check with @code{top}. Let the program run for a while, it may be evaluating something heavy. @item If it's the @code{mysqld} server that is causing problems, can you do @code{mysqladmin -u root ping} or @code{mysqladmin -u root processlist}? @item What does a client program say (try with @code{mysql}, for example) when you try to connect to the MySQL server? Does the client jam? Do you get any output from the program? @end itemize When sending a bug report, you should of follow the outlines described in this manual. @xref{Asking questions}. @node Common errors, Installation Issues, What is crashing, Problems @appendixsec MySQL 使用時のよくあるいくつかのエラー @cindex errors, list of @menu * Error Access denied:: @code{Access denied} Error * Gone away:: @code{MySQL server has gone away} error * Can not connect to server:: @code{Can't connect to [local] MySQL server} error * Blocked host:: @code{Host '...' is blocked} error * Too many connections:: @code{Too many connections} error * Non-transactional tables:: @code{Some non-transactional changed tables couldn't be rolled back} Error * Out of memory:: @code{Out of memory} error * Packet too large:: @code{Packet too large} error * Communication errors:: Communication errors / Aborted connection * Full table:: @code{The table is full} error * Cannot create:: @code{Can't create/write to file} Error * Commands out of sync:: @code{Commands out of sync} error in client * Ignoring user:: @code{Ignoring user} error * Cannot find table:: @code{Table 'xxx' doesn't exist} error * Cannot initialize character set:: @code{Can't initialize character set xxx} error * Not enough file handles:: File Not Found @end menu This section lists some errors that users frequently get. You will find descriptions of the errors, and how to solve the problem here. @node Error Access denied, Gone away, Common errors, Common errors @appendixsubsec @code{Access denied} エラー @cindex errors, access denied @cindex problems, access denied errors @cindex access denied errors @xref{Access denied}. @xref{Privileges}. @node Gone away, Can not connect to server, Error Access denied, Common errors @appendixsubsec @code{MySQL server has gone away} エラー このセクションは @code{Lost connection to server during query} エラーに関することもカバーします。 @code{MySQL server has gone away} エラーのもっとも一般的な理由は、サーバ がタイムアウトで接続をクローズしたことです。デフォルトでは、何も起きない 場合、サーバは 8 時間後に接続をクローズします。 この時間は @code{mysqld} 起動時の @code{wait_timeout} 変数に与えることにより、変 更できます。 Another common reason to receive the @code{MySQL server has gone away} error is because you have issued a ``close'' on your MySQL connection and then tried to run a query on the closed connection. @code{mysqladmin version} を実行することで MySQL が死んでいるかどうか、 また uptime はどれぐらいか、チェックできます。 スクリプトの場合は、自動的に再接続するためにクライアントからクエリを再発 行する必要があります。 この場合、通常これらのエラーコードを得ます: (OS 依存です): @multitable @columnfractions .35 .65 @item @code{CR_SERVER_GONE_ERROR} @tab クライアントがサーバーに問い合わせを送る ことができなかった server. @item @code{CR_SERVER_LOST} @tab クライアントがサーバーに書き込みを行ったときに はエラーは無かったけれども、問い合わせに対して完全に回答が返ってこない @end multitable You will also get this error if someone has kills the running thread with @code{kill #threadid#}. You can check that the MySQL hasn't died by executing @code{mysqladmin version} and examining the uptime. If the problem is that mysqld crashed you should concentrate one finding the reason for the crash. You should in this case start by checking if issuing the query again will kill MySQL again. @xref{Crashing}. 間違っているか大きすぎるクエリをサーバに送った場合にもこのエラーが発生し ます。@code{mysqld} が間違ったブロックを得た場合、クライアントの何かが間違った と見なし、接続をクローズします。大きなクエリが必要な場合、例えば大きな @code{BLOB} で働かせる場合は、@code{mysqld} をオプション @code{-O max_query_size=#} (デフォルト 1M) で起動することでクエリ制限を増加できます。拡張メモリ はオンデマンドで割り当てられます。そのため、@code{mysqld} は大きなクエリを発行し た時や大きな結果行を返す必要のある時だけ、多くのメモリを割り当てます！ You will also get a lost connection if you are sending a packet >= 16M if your client is older than 4.0.8 and your server is 4.0.8 and above, or the other way around. If you want to make a bug report regarding this problem, be sure that you include the following information: @itemize @bullet @item Include information if MySQL died or not. (You can find this in the @code{hostname.err file}. @xref{Crashing}. @item If a specific query kills @code{mysqld} and the involved tables where checked with @code{CHECK TABLE} before you did the query, can you do a test case for this? @xref{Reproduceable test case}. @item What is the value of the @code{wait_timeout} variable in the MySQL server ? @code{mysqladmin variables} gives you the value of this @item Have you tried to run @code{mysqld} with @code{--log} and check if the issued query appears in the log ? @end itemize @xref{Asking questions}. @node Can not connect to server, Blocked host, Gone away, Common errors @appendixsubsec @code{Can't connect to [local] MySQL server} エラー UNIX 上の MySQL クライアントは @code{mysqld} サーバに2つの異なる方法で 接続できます: UNIX ソケット, これはファイルシステム上のファイル(デフォルト @file{/tmp/mysql.sock})を通して接続します。または TCP/IP, これはポート番 号を通して接続します。Unix ソケットは TCP/IP よりも速いですが、サーバと 同じコンピュータから接続する時しか使えません。UNIX ソケットは、ホスト名 を指定しない場合か、特別なホスト名 @code{localhost} を指定した場合に使用され ます。 On Windows, if the @code{mysqld} server is running on 9x/Me, you can connect only via TCP/IP. If the server is running on NT/2000/XP and mysqld is started with @code{--enable-named-pipe}, you can also connect with named pipes. The name of the named pipe is MySQL. If you don't give a hostname when connecting to @code{mysqld}, a MySQL client will first try to connect to the named pipe, and if this doesn't work it will connect to the TCP/IP port. You can force the use of named pipes on Windows by using @code{.} as the hostname. (2002) @code{Can't connect to ...} エラーは、通常、MySQL サーバーが システム上に走っていないか、あなたが、間違ったソケットファイルや TCP/IP ポートを使用して @code{mysqld} に接続しようとする場合におきます。 サーバー上に @code{mysqld} というプロセスが走っているか ( @code{ps} を使用して。 Windows の場合はタスクマネージャでみて) 確認することから開始してください！ @xref{Starting server}. @code{mysqld} プロセスが走っているなら、違う接続を試すことでサーバーを 確認することができます（もちろん、ポート番号とソケットのパスはあなたが セットアップしたものとは違うでしょう）： @example shell> mysqladmin version shell> mysqladmin variables shell> mysqladmin -h `hostname` version variables shell> mysqladmin -h `hostname` --port=3306 version shell> mysqladmin -h 'ip for your host' version shell> mysqladmin --protocol=socket --socket=/tmp/mysql.sock version @end example @code{hostname} コマンドはフォワードクオートでなくバッククオテーションで 囲んでいることに注意してください； これは @code{ホスト名} (カレントのホスト名) を @code{mysqladmin} コマンドに与えます。 @code{Can't connect to local MySQL server} エラーが起こりうる理由として： @itemize @bullet @item @code{mysqld} is not running. @item MIT-pthreads を使用するシステム上で実行している。 ネイティブスレッドを持たないシステム上で実行している場合 @code{mysqld} は MIT-pthreads パッケージを使用します。@xref{Which OS}. MIT-pthreads スレッドは UNIX ソケットをサポートしません。 そのため、サーバに接続する時は常にホスト名を与える必要があります。 サーバーへの接続をチェックするために、以下を試してください： @example shell> mysqladmin -h `hostname` version @end example @item 誰かが @code{mysqld} が使用する UNIX ソケット を削除した (default @file{/tmp/mys qld.sock}). だれかが @code{cron} で MySQL ソケットを削除しているかもしれません。(例 えば @file{/tmp} ディレクトリから古いファイルを削除するようなクローンで)。 いつでも @code{mysqladmin version} を実行して @code{mysqladmin} が使用するソケットが本当に存在するかをチェックできます。 この場合の修正は、@file{mysqld.sock} を消さないように @code{cron} を変更するか、 またはソケットをどこか他の場所に移すことです。 @xref{Problems with mysql.sock}. @item @code{--socket=/path/to/socket} オプションで @code{mysqld} サーバーを起動できます。 もしサーバーのソケットのパスを変えた場合、MySQL クライアントに、新しい パスを教えなければなりません。 @xref{Problems with mysql.sock}. @item Linux を使用していてスレッドが一つ死んだとき（コアダンプした）。 この場合、他の @code{mysqld} スレッドをキルしなければなりません。 たとえば、@code{mysql_zap} スクリプトを、新しく MySQL サーバーを 起動する前に実行します。 @xref{Crashing}. @item You may not have read and write privilege to either the directory that holds the socket file or privilege to the socket file itself. In this case you have to either change the privilege for the directory / file or restart @code{mysqld} so that it uses a directory that you can access. @end itemize もし @code{Can't connect to MySQL server on some_hostname} エラーの場合, 何が問題なのかを見つけるために、以下の手順を踏みます： @itemize @bullet @item もし @code{telnet your-host-name tcp-ip-port-number} を実行すると サーバーがアップするなら、 @code{RETURN} を何回かたたいてください。 もしこのポートで MySQL サーバーが走っているなら、 走っている MySQL サーバーのバージョンナンバーを含んだ レスポンスが得られるはずです。 もし @code{telnet: Unable to connect to remote host: Connection refused} のような エラーになったならば、このポートを使用しているサーバーはありません。 @item ローカルのマシンの @code{mysqld} デーモンに接続してみてください。 @code{mysqldmin variables} で、@code{mysqld} が使用するように指定された TCP/IP ポート(変数 @code{port})をチェックしてください。 @item @code{mysqld} サーバーが @code{--skip-networking} オプションで起動されていないか 確認してください。 @end itemize @node Blocked host, Too many connections, Can not connect to server, Common errors @appendixsubsec @code{Host '...' is blocked} エラー 以下のエラーの場合： @example Host 'hostname' is blocked because of many connection errors. Unblock with 'mysqladmin flush-hosts' @end example これは @code{mysqld} が多くの @code{'hostname'} ホストからの接続エラー(@code{max _connect_errors}) を受けた場合に発生します。 この @code{max_connect_errors} 大量発生後、@code{mysqld} は何か(クラッカーによる サーバーへのアタックなど)が起こったと判断し、このホストからの接続をいっさい拒否 するようにします。 これを解除するには、@code{mysqladmin flush-hosts} コマンドを実行します。 デフォルトでは、10回の接続エラーが発生した場合に、@code{mysqld} はそのホストを拒 否します。 この値は以下のようにして簡単に変更できます： @example shell> safe_mysqld -O max_connect_errors=10000 & @end example もしこのエラーがあるホストに対して発生するならば、まず最初にそのホストからの TCP /IP 接続に不具合がないかチェックしてください。 もし TCP/IP 接続が動作していないようなら、 @code{max_connect_errors} 値を増やす ことはよくないことです！ @node Too many connections, Non-transactional tables, Blocked host, Common errors @appendixsubsec @code{Too many connections} エラー もし MySQL に接続しようとして @code{Too many connections} となった場合、 これは既に @code{max_connections} 分、クライアントから @code{mysqld} サーバーへの 接続が行われています。 もしデフォルトの100よりも多い接続を必要とするならば、 @code{max_connections} 変数に多くの値を与えて、@code{mysqld} を リスタートしなくてはなりません。 実際は、@code{mysqld} は (@code{max_connections}+1) 個のクライアントからの接続を 許しています。 最後の１個は、 @code{SUPER} 権限 (version4.0.2以上。未満は @code{PROCESS} 権限)を もつユーザーのために取ってあります。 By not giving this privilege to normal users (they shouldn't need this), an administrator with this privilege can log in and use @code{SHOW PROCESSLIST} to find out what could be wrong. @xref{SHOW PROCESSLIST}. The maximum number of connects MySQL is depending on how good the thread library is on a given platform. Linux or Solaris should be able to support 500-1000 simultaneous connections, depending on how much RAM you have and what your clients are doing. @node Non-transactional tables, Out of memory, Too many connections, Common errors @appendixsubsec @code{Some non-transactional changed tables couldn't be rolled back} エラー @cindex Non-transactional tables もし @code{ROLLBACK} を試みたときに @code{Warning: Some non-transactional changed tables couldn't be rolled back} エラー/警告が出た場合、これは、あなたが使用しているテーブルがトランザクションを サポートしていないということです。 これらの非トランザクションのテーブルは @code{ROLLBACK} によって、何の影響も受けません。 The most typical case when this happens is when you have tried to create a table of a type that is not supported by your @code{mysqld} binary. If @code{mysqld} doesn't support a table type (or if the table type is disabled by a startup option) , it will instead create the table type with the table type that is most resembles to the one you requested, probably @code{MyISAM}. 以下の SQL 文でテーブルの型をチェックできます: @code{SHOW TABLE STATUS LIKE 'table_name'}. @xref{SHOW TABLE STATUS}. You can check the extensions your @code{mysqld} binary supports by doing: @code{show variables like 'have_%'}. @xref{SHOW VARIABLES}. @node Out of memory, Packet too large, Non-transactional tables, Common errors @appendixsubsec @code{Out of memory} エラー クエリを行って、次のエラーのようなものを得た場合: @example mysql: Out of memory at line 42, 'malloc.c' mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k) ERROR 2008: MySQL client ran out of memory @end example エラーは MySQL クライアント @code{mysql} に関係することに注意してください。 エラーの理由は単純で、クライアントが結果全体を格納するのに十分なメモリを持っ ていないことです。 この問題を解決するにあたり、まず最初にクエリーが正しいか確認してください。 そのクエリーは大量の結果を返すものでしょうか？ もしそうなら、@code{mysql --quick} を使用してください。 これは結果を取り出すために @code{mysql_use_result()} を使用します。 これはクライアントのロード不足を補います(サーバーより多い領域は取れません)。 @node Packet too large, Communication errors, Out of memory, Common errors @appendixsubsec @code{Packet too large} エラー MySQL クライアントが @code{max_allowed_packet} よりも大きなブロックを @code{mysqld} サーバーから得た時、@code{Packet too large} エラーを発します。 In MySQL 3.23 the biggest possible packet is 16M (due to limits in the client/server protocol). In MySQL 4.0.1 and up, this is only limited by the amount on memory you have on your server (up to a theoretical maximum of 2G). A communication packet is a single SQL statement sent to the MySQL server or a single row that is sent to the client. MySQL クライアントや @code{mysqld} サーバーが @code{max_allowed_packet} バイトより 大きなパケットを受け取ったた場合、 @code{Packet too large} エラーを発して 接続を閉じます。 いくつかのクライアントでは、 @code{Lost connection to MySQL server during query} エラーも出すでしょう。 クライアントとサーバーは、自身の @code{max_allowed_packet} 変数を持っています。 もし大きなパケットを扱いたい場合には、クライアントとサーバーの両方の @code{max_allowed_packet} 値を増やしてください。 It's safe to increase this variable as memory is only allocated when needed; this variable is more a precaution to catch wrong packets between the client/server and also to ensure that you don't accidentally use big packets so that you run out of memory. If you are using the @code{mysql} client, you may specify a bigger buffer by starting the client with @code{mysql --set-variable=max_allowed_packet=8M}. Other clients have different methods to set this variable. Please note that @code{--set-variable} is deprecated since MySQL 4.0, just use @code{--max-allowed-packet=8M} instead. You can use the option file to set @code{max_allowed_packet} to a larger size in @code{mysqld}. For example, if you are expecting to store the full length of a @code{MEDIUMBLOB} into a table, you'll need to start the server with the @code{set-variable=max_allowed_packet=16M} option. @node Communication errors, Full table, Packet too large, Common errors @appendixsubsec Communication Errors / Aborted Connection @cindex aborted clients @cindex aborted connection @cindex connection, aborted @code{MySQL 3.23.40} からは、@code{mysqld} を @code{--warnings} オプションで たち上げた時にだけ、@code{Aborted connection} エラーを出力することが可能です。 もし以下のようなエラーがエラーログファイルに記録されていたら、 @example 010301 14:38:23 Aborted connection 854 to db: 'users' user: 'josh' @end example @xref{Error log}. これは以下が起きたことを示します： @itemize @bullet @item クライアントプログラムが終了前に @code{mysql_close()} を呼び出さなかった。 @item クライアントが @code{wait_timeout} か @code{interactive_timeout} 以上、いかなるリクエストもしない状態だった。 @xref{SHOW VARIABLES, , @code{wait_timeout}}. @xref{SHOW VARIABLES, , @code{interactive_timeout}}. @item クライアントプログラムが転送の途中にプログラムを終了した @end itemize 上記が起きたときには、サーバーは @code{Aborted_clients} 変数を増やします。 サーバー変数 @code{Aborted_connects} は以下の時に増えます： @itemize @bullet @item コネクションパケットが正しい情報を含んでいなかった時 @item ユーザーがデータベースに接続する権限を持たなかった時 @item あるユーザーが間違ったパスワードを使用した時 @item コネクションパケットを得る際に、 @code{connect_timeout} 秒以上 かかった時 @xref{SHOW VARIABLES, , @code{connect_timeout}}. @end itemize Note that the above could indicate that someone is trying to break into your database! @xref{SHOW VARIABLES}. Other reasons for problems with Aborted clients / Aborted connections. @itemize @bullet @item Usage of duplex Ethernet protocol, both half and full with Linux. Many Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file via ftp between these two machines. If a transfer goes in burst-pause-burst-pause ... mode then you are experiencing a Linux duplex syndrome. The only solution to this problem is switching off either half or full duplex mode on hubs and switches, and testing the results to decide on the best setting. @item Some problem with the thread library that causes interrupts on reads. @item Badly configured TCP/IP. @item Faulty Ethernets or hubs or switches, cables ... This can be diagnosed properly only by replacing hardware. @item @code{max_allowed_packet} is too small or queries require more memory than you have alloacated for @code{mysqld}. @xref{Packet too large}. @end itemize @node Full table, Cannot create, Communication errors, Common errors @appendixsubsec @code{The table is full} エラー @cindex table is full @itemize @bullet @item このエラーは、古い MySQL バージョン(before 3.23.0)において、 メモリ内一時テーブルが @code{tmp_table_size} よりも大きくなっ た時に発生します。この問題を回避するために、@code{mysqld} のオプション @code{-O tmp_table_size=#} で増加、または、SQL オプション @code{BIG_TABLES} (ver.4.0.3未満では @code{SQL_BIG_TABLES} ) を問題のクエリの前に使用できます。 @xref{SET OPTION, ,@code{SET}}. You can also start @code{mysqld} with the @code{--big-tables} option. This is exactly the same as using @code{BIG_TABLES} for all queries. In MySQL Version 3.23, in-memory temporary tables will automatically be converted to a disk-based @code{MyISAM} table after the table size gets bigger than @code{tmp_table_size}. @item You are using @code{InnoDB} tables and run out of room in the @code{InnoDB} tablespace. In this case the solution is to extend the @code{InnoDB} tablespace. @item You are using @code{ISAM} or @code{MyISAM} tables on an OS that only supports files of 2G in size and you have hit this limit for the data or index file. @item You are using @code{MyISAM} tables and the needed data or index size is bigger than what MySQL has allocated pointers for. (If you don't specify @code{MAX_ROWS} to @code{CREATE TABLE} MySQL will only allocate pointers to hold 4G of data). You can check the maximum data/index sizes by doing @example SHOW TABLE STATUS FROM database LIKE 'table_name'; @end example or using @code{myisamchk -dv database/table_name}. If this is the problem, you can fix it by doing something like: @example ALTER TABLE table_name MAX_ROWS=1000000000 AVG_ROW_LENGTH=nnn; @end example You only have to specify @code{AVG_ROW_LENGTH} for tables with BLOB/TEXT fields as in this case MySQL can't optimise the space required based only on the number of rows. @end itemize @node Cannot create, Commands out of sync, Full table, Common errors @appendixsubsec @code{Can't create/write to file} エラー @cindex can't create/write to file If you get an error for some queries of type: @example Can't create/write to file '\\sqla3fe_0.ism'. @end example this means that MySQL can't create a temporary file for the result set in the given temporary directory. (The above error is a typical error message on Windows, and the Unix error message is similar.) The fix is to start @code{mysqld} with @code{--tmpdir=path} or to add to your option file: @example [mysqld] tmpdir=C:/temp @end example assuming that the @file{c:\\temp} directory exists. @xref{Option files}. Check also the error code that you get with @code{perror}. One reason may also be a disk full error; @example shell> perror 28 Error code 28: No space left on device @end example @node Commands out of sync, Ignoring user, Cannot create, Common errors @appendixsubsec @code{Commands out of sync} Error in Client @cindex commands out of sync @code{Commands out of sync; you can't run this command now} をクライアン トコード中で得た場合、クライアント関数を間違った順番で呼び出しました！ これは例えば、@code{mysql_use_result()} を使用していて、@code{mysql_free_result( )} を行う前に新しいクエリの実行を試みた場合に発生します。これはまた、データ を返す２つのクエリの実行を、間に @code{mysql_use_result()} や @code{mysql_store_result()} 無しで試みた場合にも発生します。 @node Ignoring user, Cannot find table, Commands out of sync, Common errors @appendixsubsec @code{Ignoring user} エラー 以下のエラーの場合： @code{Found wrong password for user: 'some_user@@some_host'; ignoring user} これは @code{mysqld} の開始または 'reload' 時に @code{user} テーブル内に正しいパ スワードを持たないエントリを見つけたことを意味します。 これは単にエントリが許可システムに拒否されているだけです。 起こり得ることとその解決: @itemize @bullet @item 新しいバージョンの @code{mysqld} を、古いバージョン用の @code{user} テーブルで走 らせているのかもしれません。 @code{mysqlshow mysql user} を行うことによってこれを検証できます。 パスワードフィールドが 16 文字よりも短いかどうかをチェックしてください。 もしそうなら、これを修正するために、@code{scripts/add_long_password} スクリプト を実行してください。 @item ユーザーが古いパスワード(最大8文字) を使用していて、@code{mysqld} を @code{--old -protocol} オプションで起動していないのかもしれません。 新しいパスワードで @code{user} テーブル内のユーザを更新するか、@code{--old-protocol} 付きで @code{mysqld} を再起動してください。 @item @findex PASSWORD() @code{user} テーブルのパスワードを、@code{PASSWORD()} 関数を使用しないで登録した のかもしれません。 この場合、@code{user} テーブルのパスワードを、@code{mysql} を使用して更新します。 @code{PASSWORD()} 関数は以下のようにして使用します： @example mysql> UPDATE user SET password=PASSWORD('your password') -> WHERE user='XXX'; @end example @end itemize @node Cannot find table, Cannot initialize character set, Ignoring user, Common errors @appendixsubsec @code{Table 'xxx' doesn't exist} エラー もし @code{Table 'xxx' doesn't exist} か @code{Can't find file: 'xxx' (errno: 2)} エラーが出た場合、使用しているデータベースに @code{xxx} という名前のテーブルが 見付からなかったことを示します データベースとテーブルの保存に、MySQL はディレクトリとファイルを使用し、 データベースとテーブルの名前は@strong{ケース依存}です! (Windows ではデータベースとテーブル名はケース非依存です。 クエリ中のテーブルに対する問い合わせは全て、同じケースで書かなくてはなりません！) @code{SHOW TABLES} を使用してデータベースのテーブルを確認できます. @xref{SHOW, , @code{SHOW}}. @node Cannot initialize character set, Not enough file handles, Cannot find table, Common errors @appendixsubsec @code{Can't initialize character set xxx} エラー @cindex multi-byte character sets もし以下のようなエラーが出た場合： @example MySQL Connection Failed: Can't initialize character set xxx @end example これは次を意味します： @itemize @bullet @item キャラクタ・セットがマルチバイトで、、クライアントがそのキャラクタ・セットを 持っていない場合 この場合、クライアントを @code{--with-charset=xxx} か @code{--with-extra-charsets=xxx} コンフィギャ・オプションで再コンパイルする必要があります。 @xref{configure options}. All standard MySQL binaries are compiled with @code{--with-extra-character-sets=complex} which will enable support for all multi-byte character sets. @xref{Character sets}. @item そのキャラクタ・セットが単純なキャラクタ・セットで、それが @code{mysqld} に 組み込まれておらず、さらに 定義ファイルも特定の場所に存在しなかった場合。 この場合は以下のようにします： @itemize @bullet @item クライアントをそのキャラクタ・セットをサポートするように再コンパイル。 @xref{configure options}. @item クライアントに、そのキャラクタ・セットの定義ファイルがどこに存在するかを教える。 多くのクライアントは @code{--character-sets-dir=path-to-charset-dir} オプションを 持っています。 @item そのクライアントが定義ファイルを探しにいっているディレクトリに、 定義ファイルをコピーする。 @end itemize @end itemize @node Not enough file handles, , Cannot initialize character set, Common errors @appendixsubsec File Not Found @code{ERROR '...' not found (Errcode: 23)}, @code{Can't open file: ... (errno: 24)} や @code{errcode 23} @code{errno 24} のエラーを MySQL から得た場合、 これは MySQL に十分なファイル記述子が割り当てられなかったことを意味します。 @code{perror} ユーティリティはさらに読みやすい形式のエラーメッセージを与えます: @example shell> perror 23 File table overflow shell> perror 24 Too many open files shell> perror 11 Resource temporarily unavailable @end example これは @code{mysqld} が多くのファイルを開こうとしたことに起因します。 @code{mysqld} に一度に開くファイル数を多く開かないようしたり、あるいは、 @code{mysqld} が扱えるファイル記述子の数を与えたりできます。 @code{mysqld} が一度に開くファイルの数を少なくするには、@code{-O table_cache=32} オプション(デフォルトは64)を @code{safe_mysqld} に与えることで可能です。 また、@code{max_connections} の値(デフォルトは90)を少なくするならば、 開くファイル数も少なくできます。 @tindex ulimit To change the number of file descriptors available to @code{mysqld}, you can use the option @code{--open-files-limit=#} to @code{safe_mysqld} or @code{-O open-files-limit=#} to @code{mysqld}. @xref{SHOW VARIABLES, , @code{open_files_limit}}. The easiest way to do that is to add the option to your option file. @xref{Option files}. If you have an old @code{mysqld} version that doesn't support this, you can edit the @code{safe_mysqld} script. There is a commented-out line @code{ulimit -n 256} in the script. You can remove the @code{'#'} character to uncomment this line, and change the number 256 to affect the number of file descriptors available to @code{mysqld}. @code{ulimit} と @code{open-files-limit} はオペレーティングシステムの 制限内でしかファイル記述子の数を指定できません。 There is also a 'hard' limit that can only be overrided if you start @code{safe_mysqld} or @code{mysqld} as root (Just remember that you need to also use the @code{--user=..} option in this case). もし OS の制限以上にファイル記述子のオープン数を増やしたい場合、 お使いのオペレーティングシステムのドキュメントを見て対処してください。 @code{tcsh} を使用している場合は @code{ulimit} は動かないことに注意してください！ @code{tcsh} は現在の制限をあなたが問い合わせても、違った値を報告するでしょう。 この場合、@code{safe_mysqld} は @code{sh} で起動すべきです！ @node Installation Issues, Administration Issues, Common errors, Problems @appendixsec Installation Related Issues @menu * Link errors:: Problems When Linking with the MySQL Client Library * Changing MySQL user:: How to Run MySQL As a Normal User * File permissions:: @end menu @node Link errors, Changing MySQL user, Installation Issues, Installation Issues @appendixsubsec Problems When Linking with the MySQL Client Library @cindex linking, errors @cindex errors, linking @cindex problems, linking If you are linking your program and you get errors for unreferenced symbols that start with @code{mysql_}, like the following: @example /tmp/ccFKsdPa.o: In function `main': /tmp/ccFKsdPa.o(.text+0xb): undefined reference to `mysql_init' /tmp/ccFKsdPa.o(.text+0x31): undefined reference to `mysql_real_connect' /tmp/ccFKsdPa.o(.text+0x57): undefined reference to `mysql_real_connect' /tmp/ccFKsdPa.o(.text+0x69): undefined reference to `mysql_error' /tmp/ccFKsdPa.o(.text+0x9a): undefined reference to `mysql_close' @end example この場合には、@code{-Lpath-to-the-mysql-library -lmysqlclient} を、 リンクの @strong{最後に} 加えれば解決します。 もし @code{undefined reference} エラーで @code{uncompress} や @code{compress} が定義されていないエラーを受けたならば、 @code{-lz} をリンク ラインの @strong{最後に} 加えて再リンクしてください！ If you get @code{undefined reference} errors for functions that should exist on your system, like @code{connect}, check the man page for the function in question, for which libraries you should add to the link line! If you get @code{undefined reference} errors for functions that don't exist on your system, like the following: @example mf_format.o(.text+0x201): undefined reference to `__lxstat' @end example it usually means that your library is compiled on a system that is not 100% compatible with yours. In this case you should download the latest MySQL source distribution and compile this yourself. @xref{Installing source}. If you are trying to run a program and you then get errors for unreferenced symbols that start with @code{mysql_} or that the @code{mysqlclient} library can't be found, this means that your system can't find the share @file{libmysqlclient.so} library. The fix for this is to tell your system to search after shared libraries where the library is located by one of the following methods: @itemize @bullet @item @code{LD_LIBRARY_PATH} 環境変数に、@file{libmysqlclient.so} が存在する ディレクトリを加える。 @item @code{LD_LIBRARY} 環境変数に、@file{libmysqlclient.so} が存在する ディレクトリを加える。 @item Copy @file{libmysqlclient.so} to some place that is searched by your system, like @file{/lib}, and update the shared library information by executing @code{ldconfig}. @end itemize 他の解決方法は、あなたのプログラムを @code{-static} フラグで static にリンクするか、 動的な MySQL ライブラリをリンク前に移動してから、リンクします。 二つ目の場合は、他のプログラムがそのダイナミックライブラリを使用していないか 注意してください！ @node Changing MySQL user, File permissions, Link errors, Installation Issues @appendixsubsec 一般ユーザで MySQL を動かす方法 @cindex starting, @code{mysqld} @cindex @code{mysqld}, starting @code{mysqld} (MySQL サーバ) はいかなるユーザーでも開始し実行することが できます。@code{mysqld} をユーザ @code{user_name} で実行するように変更するためには、 次を行なう必要があります: @enumerate @item Stop the server if it's running (use @code{mysqladmin shutdown}). @item @code{user_name} が読み書きできるように、データベースディレクトリとその中のファ イルのパーミッションを変更します。(これは UNIX @code{root} ユーザーで実行する必 要があるでしょう)： @example shell> chown -R user_name /path/to/mysql/datadir @end example MySQL データベースディレクトリのディレクトリーやファイルがシンボリック リンクの場合、 これらリンクの先のディレクトリとファイルも変更します。@code{chown -R} はシンボリ ックリンク先を変更してくれません。 @item ユーザ @code{user_name} でサーバを起動します。または MySQL 3.22 以降を 使用する場合は、@code{mysqld} を UNIX @code{root} で起動し @code{--user=user_name} スイッチを使用します。 @code{mysqld} は、接続を許可する前に、与えられた UNIX user @code{user_name} で実 行するように切り替えます。 @item To start the server as the given user name automatically at system startup time, add a @code{user} line that specifies the user name to the @code{[mysqld]} group of the @file{/etc/my.cnf} option file or the @file{my.cnf} option file in the server's data directory. For example: @example [mysqld] user=user_name @end example @end enumerate この時点で、あなたの @code{mysqld} プロセスは UNIX user @code{user_name} で正常 に動作します。 一つのことは変わりません。それは権限許可テーブルです。デフォルト (パーミッションテーブルインストールスクリプト@code{mysql_install_db}実行後の権限) では、@code{mysql}データベースへのアクセスやデータベースの作成、破棄はユーザ MySQL user @code{root} だけです。 これを変更しないと、それはそのままです。 @code{root} 以外の UNIX userでログインしている時でも、あなたは MySQL @code{root} user としてアクセスは可能です - ただプログラムに @code{-u root} をクライアントプログラムにオプション指定するだけです。 MySQL に @code{root} としてアクセスするには、 コマンドラインで @code{-u root} を使用するだけでいいことに注意してください。 UNIX @code{root} user や MySQL を走らせている UNIX ユーザーである必要は @emph{ない}ことに注意してください。 MySQL のアクセスパーミッションとMySQL のユーザは、 UNIX ユーザとは完全に別のものです。UNIX ユーザに関係するのは、クライアン トに @code{-u} オプションを使用しない場合だけです。この場合、クライアントは MySQL へのログインを、あなたの UNIX ログイン名で試みます。 あなたの UNIX マシンそれ自身が安全でない場合は、少なくとも MySQL ア クセステーブルの MySQL @code{root} ユーザにはパスワードを設定すべきです。 どこかの誰かが @code{mysql -u root db_name} を行ない、彼が望むことの全てを実行で きてしまうからです。 @node File permissions, , Changing MySQL user, Installation Issues @appendixsubsec ファイルパーミッションの問題 @cindex files, permissions @cindex error mesaages, can't find file @cindex files, not found message ファイルパーミッションの問題がある場合、 例えば、テーブルの生成時に @code{mysql} が次を出力する場合: @example ERROR: Can't find file: 'path/with/filename.frm' (Errcode: 13) @end example @tindex UMASK environment variable @tindex Environment variable, UMASK これは @code{UMASK} 環境変数が @code{mysqld} 起動時に間違ってセットされていると 考えられます。 デフォルトの umask は @code{0660} です. これは以下のようにして @code{safe_mysqld} 立ち上げ時に変更できます: @example shell> UMASK=384 # = 600 in octal shell> export UMASK shell> /path/to/safe_mysqld & @end example @tindex UMASK_DIR environment variable @tindex Environment variable, UMASK_DIR By default MySQL will create database and @code{RAID} directories with permission type 0700. You can modify this behaviour by setting the @code{UMASK_DIR} variable. If you set this, new directories are created with the combined @code{UMASK} and @code{UMASK_DIR}. For example, if you want to give group access to all new directories, you can do: @example shell> UMASK_DIR=504 # = 770 in octal shell> export UMASK_DIR shell> /path/to/safe_mysqld & @end example In MySQL Version 3.23.25 and above, MySQL assumes that the value for @code{UMASK} and @code{UMASK_DIR} is in octal if it starts with a zero. @xref{Environment variables}. @node Administration Issues, Query Issues, Installation Issues, Problems @appendixsec Administration Related Issues @menu * Crashing:: What To Do If MySQL Keeps Crashing * Resetting permissions:: How to Reset a Forgotten Root Password * Full disk:: How MySQL Handles a Full Disk * Temporary files:: Where MySQL Stores Temporary Files * Problems with mysql.sock:: How to Protect @file{/tmp/mysql.sock} from Being Deleted * Timezone problems:: Time Zone Problems @end menu @node Crashing, Resetting permissions, Administration Issues, Administration Issues @appendixsubsec What To Do If MySQL Keeps Crashing @cindex crash, repeated 全ての MySQL バージョンはリリースの前に多くのプラットフォームで テストされます。 これは MySQL にいかなるバグもないということを 意味しますが、発見するのが困難で、わずかなバグがあるかもしれません。 もし問題があった場合、何がシステムをクラッシュしているかを見つけようとする事は、 問題を早く修正するためのより良い機会でもあります。 まず最初に, その問題で @code{mysqld} デーモンが死ななければならないかどうかか, また はその問題がクライアントで処理しなければならないかどうかを調べるべきです。 @code{mysqladmin version} を実行することにより、 @code{mysqld} サーバーが どれぐらい稼働していたかわかります。 もし @code{mysqld} が死んでいたなら、 を実行することによってあるのかをチェックすることができます. mysqldが死んだなら、 その原因を @file{mysql-data-directory/`hostname`.err} で見つけれるかもしれません。 @xref{Error log}. Many crashes of MySQL are caused by corrupted index / data files. MySQL will update the data on disk, with the @code{write()} system call, after every SQL statement and before the client is notified about the result. (This is not true if you are running with @code{delay_key_write}, in which case only the data is written.) This means that the data is safe even if @code{mysqld} crashes, as the OS will ensure that the not flushed data is written to disk. You can force MySQL to sync everything to disk after every SQL command by starting @code{mysqld} with @code{--flush}. The above means that normally you shouldn't get corrupted tables unless: @itemize @bullet @item Someone/something killed @code{mysqld} or the machine in the middle of an update. @item You have found a bug in @code{mysqld} that caused it to die in the middle of an update. @item Someone is manipulating the data/index files outside of @strong{mysqld} without locking the table properly. @item If you are running many @code{mysqld} servers on the same data on a system that doesn't support good filesystem locks (normally handled by the @code{lockd} daemon ) or if you are running multiple servers with @code{--skip-external-locking} @item You have a crashed index/datafile that contains very wrong data that got @code{mysqld} confused. @item You have found a bug in the data storage code. This isn't that likely, but it's at least possible. In this case you can try to change the file type to another storage engine by using @code{ALTER TABLE} on a repaired copy of the table! @end itemize 何かがクラッシュする理由を知るのは非常に難しいので、まず、他の人で動くも のがあなたでクラッシュするのかどうかをチェックしてください。次のことを行っ てください。 @itemize @bullet @item @code{mysqld} デーモンを @code{mysqladmin shutdown} で停止し, 全てのテーブルで @code{myisamchk --silent --force */*.MYI} を実行し、そして @code{mysqld} デーモ ンを再起動します. これはきれいな状態から開始することになります。 @xref{MySQL Database Administration}. @item @code{mysqld --log} を使用し、ログの情報から特定のクエリがサーバーをキルしている かを見つけ出してください。 95% のバグは特定のクエリに関係があります！ 通常これは、 MySQL が再起動される前の、ログファイルの最後のクエリの一つ です。 @xref{Query log}. If you can repeatadly kill MySQL with one of the queries, even when you have checked all tables just before doing the query, then you have been able to locate the bug and should do a bug report for this! @xref{Bug reports}. @item Try to make a test case that we can use to reproduce the problem. @xref{Reproduceable test case}. @item Try running the included mysql-test test and the MySQL benchmarks. @xref{MySQL test suite}. They should test MySQL rather well. You can also add code that to the benchmarks to simulates your application! The benchmarks can be found in the @file{bench} directory in the source distribution or, for a binary distribution, in the @file{sql-bench} directory under your MySQL installation directory. @item @code{fork_test.pl} と @code{fork2_test.pl} を試します。 @item デバッグ用に MySQL をコンフィグすると、何かが悪くなる場合にエラー を見つけ出すのがより簡単になります。@code{configure} に @code{--with-debug} オプションか @code{--with-debug=full} オプションを つけて MySQL を再コンフィグし、 再コンパイルしてください。@xref{Debugging server}. @item デバッグ用に MySQL をコンフィグすると、いくつかのエラーを検出で きる安全なメモリ割り当てを含めます。これは何が起きているかについての多く の出力も提供します。 @item あなたの OS の最新のパッチを適用しましたか？ @item @code{--skip-external-locking} (ver. 4.0.3未満では @code{--skip-locking}) オプションを @code{mysqld} に使用してください。いくつかのシステム上では、 @code{lockd} ロックマネージャは正しく動きません; @code{--skip-external-locking} (ver. 4.0.3未満では @code{--skip-locking}) オプションは @code{mysqld} に外部ロッキングを使用 しないように伝えます。(これは同じデータ上で2つの @code{mysqld} サーバを 動すことができず、@code{myisamchk} の使用時に注意しなければいけないことを 意味します。しかし、テストとしてこのオプションを試すことは指示できます。) @item @code{mysqld} が動いているのに応答がないように見えた時 @code{mysqladmin -u root processlist} を試しましたか？ 時々 @code{mysqld} はそう思えても死んでいません。問題は全ての接続が使用中であ ることか、いくつかの内部ロック問題があることです。@code{mysqladmin processlist} は通常これらの場合でも接続を作ることができ、現在の接続数と それらの状態についての有用な情報を提供できます。 @item 別のウィンドウで、統計出力のためにコマンド @code{mysqladmin -i 5 status} や @code{mysqladmin -i 5 -r status} をクエリ中に行ってください。 @item 次を試してください: @enumerate @item @code{gdb} (または他のデバッガ) から @code{mysqld} を開始してください。 @xref{Using gdb on mysqld}. @item あなたのテストスクリプトを実行してください。 @item Print the backtrace and the local variables at the 3 lowest levels. In gdb you can do this with the following commands when @code{mysqld} has crashed inside gdb: @example backtrace info local up info local up info local @end example With gdb you can also examine which threads exist with @code{info threads} and switch to a specific thread with @code{thread #}, where @code{#} is the thread id. @end enumerate @item MySQL にクラッシュまたは間違った振る舞いをさせるあなたのアプリ ケーションのシミュレートを Perl スクリプトで試みてください。 @item または通常のバグレポートを送ってください。@xref{Bug reports}。しかし通常 よりもさらに詳細にしてください。MySQL は多くの人のために働いて いるため、クラッシュはあなたのコンピュータだけに存在する何か(例えば、あ なたの特別なシステムライブラリに関連したエラー)から生じていると思われま す。 @item もし可変長のレコードを扱うテーブルで問題があった場合、 もし、@code{BLOB/TEXT} フィールドは使用しておらず、@code{VARCHAR} フィールド だけ使用しているなら、全ての @code{VARCHAR} フィールドを @code{ALTER TABLE} で @code{CHAR} に変更してみてください。 これは MySQL に固定長レコードを使用させるようにします。 固定長レコードは少し余分な領域をとりますが、よりエラーに対して 強くなります。 現在の可変長のレコードのコードは MySQL AB で少なくとも３年以上問題なく 使用されています。 しかし可変長のレコードはよりエラーの傾向があり、 上記の事柄を試すことは良いアイデアです！ @end itemize @node Resetting permissions, Full disk, Crashing, Administration Issues @appendixsubsec 忘れたパスワードをリセットする @cindex passwords, forgotten @cindex passwords, resetting @cindex root user, password resetting If you never set a @code{root} password for MySQL, then the server will not require a password at all for connecting as @code{root}. It is recommended to always set a password for each user. @xref{Security}. もし MySQL の @code{root} ユーザーのパスワードを忘れた場合、 これを以下のようにして入れ直すことが可能です。 @enumerate @item @code{mysqld} サーバーを @code{kill} で落とす。 (@code{kill -9} ではありません！) PID 番号は通常 MySQL データディレクトリに @file{.pid} ファイルに 書かれています： @example shell> kill `cat /mysql-data-directory/hostname.pid` @end example これを、 Unix @code{root} ユーザーか、MySQL サーバーを実行した ユーザーで行います。 @item @code{mysqld} を @code{--skip-grant-tables} オプションで起動。 @item @code{mysqladmin password} コマンドでパスワードを変更します。 @example shell> mysqladmin -u root password 'mynewpassword' @end example @item Now you can either stop @code{mysqld} and restart it normally, or just load the privilege tables with: @example shell> mysqladmin -h hostname flush-privileges @end example @item After this, you should be able to connect using the new password. @end enumerate Alternatively, you can set the new password using the @code{mysql} client: @enumerate @item Take down and restart @code{mysqld} with the @code{--skip-grant-tables} option as described above. @item Connect to the @code{mysqld} server with: @example shell> mysql -u root mysql @end example @item Issue the following commands in the @code{mysql} client: @example mysql> UPDATE user SET Password=PASSWORD('mynewpassword') -> WHERE User='root'; mysql> FLUSH PRIVILEGES; @end example @item After this, you should be able to connect using the new password. @item You can now stop @code{mysqld} and restart it normally. @end enumerate @node Full disk, Temporary files, Resetting permissions, Administration Issues @appendixsubsec MySQL はフルディスクをどのように扱うか？ @cindex full disk @cindex disk full @noindent ディスクフルが起きた場合 MySQL は次のことを行います: @itemize @bullet @item 現在の行を書くのに十分な領域があるかどうかを1分毎に1回チェックします。十 分なディスクがある場合は、何も起きなかったように継続します。 @item 6分毎にログファイルにディスクフルを警告するエントリを書き出します。 @end itemize @noindent この問題の場合、以下のようにします： @itemize @bullet @item 継続するためには、全てのレコードを挿入するのに十分な領域を解放する必要が あります。 @item スレッドをアボートするためには、@code{mysqladmin kill} をスレッドに送る 必要があります。スレッドは次に(1分)ディスクをチェックした時にアボートし ます。 @item 他のスレッドが ``disk full'' が発生したテーブルで待たされることに注意して ください。多くの ``locked'' スレッドがある場合、disk full を待つ一つのスレッ ドを kill することで、他のスレッドの継続を許します。 @end itemize Exceptions to the above behaveour is when you use @code{REPAIR} or @code{OPTIMIZE} or when the indexes are created in a batch after an @code{LOAD DATA INFILE} or after an @code{ALTER TABLE} statement. All of the above commands may use big temporary files that left to themself would cause big problems for the rest of the system. If MySQL gets disk full while doing any of the above operations, it will remove the big temporary files and mark the table as crashed (except for @code{ALTER TABLE}, in which the old table will be left unchanged). @node Temporary files, Problems with mysql.sock, Full disk, Administration Issues @appendixsubsec MySQL が一時ファイルを格納する場所 MySQL は一時ファイルを格納する場所として @code{TMPDIR} 環境変数の値を 使用します。@code{TMPDIR} を設定していなければ、MySQL はシステムのデフォルトを 使用します。通常は @file{/tmp} または @file{/usr/tmp} です。@code{TMPDIR} が 小さすぎる場合、@code{safe_mysqld} を編集して、十分な領域がある他のディレクトリ を指すように @code{TMPDIR} を設定すべきです！ @code{--tmpdir} オプションを @code{mysqld} に与えることで、一時ファイルディレク トリを指定することも可能です。 MySQL は全ての一時ファイルを ``隠しファイル'' として生成します。 これは @code{mysqld} が終了した場合に、一時ファイルが削除されないことを確実にし ます。隠しファイルを使用する '悪い' 側面は、小さすぎる一時ディスクを一杯 にする大きな一時ファイルを見つけられないことです。 ソート時 (@code{ORDER BY} または @code{GROUP BY})、MySQL は通常一つまた は二つの一時ファイルを使用します。必要な最大のディスク容量は: @example (length of what is sorted + sizeof(database pointer)) * number of matched rows * 2 @end example @code{sizeof(database_pointer)} は通常４ですが、将来本当に大きなテーブル のために大きくなることもあります。 いくつかの @code{SELECT} クエリは一時的な SQL テーブルも生成します。これらは隠 しファイルではなく、@file{SQL_*} という名前です。 @code{ALTER TABLE} は一時テーブルをオリジナルテーブルと同じディレクトリ 内に生成します。 If you use MySQL 4.1 or later you can spread load between several physical disks by setting @code{--tmpdir} to a list of paths separated by colon @code{:} (semicolon @code{;} on Windows). They will be used in round-robin fashion. @strong{Note:} These paths should end up on different @strong{physical} disks, not different partitions of the same disk. @node Problems with mysql.sock, Timezone problems, Temporary files, Administration Issues @appendixsubsec MySQL ソケットファイル @file{/tmp/mysql.sock} を変更する方法、削除から守る方法 @cindex @code{mysql.sock}, protection @cindex deletion, @code{mysql.sock} もし誰かに MySQL のソケットファイル @file{/tmp/mysql.sock} が消されるな ら、ほとんどの UNIX がそうであるように、 @file{/tmp} に @code{sticky} ビットをたてて 保護します。 @code{root} でログインして、以下のようにします： @example shell> chmod +t /tmp @end example これはファイルのオーナーとスーパーユーザー(@code{root}) のみが、 @file{/tmp} のファイルを消すことができます。 @code{sticky} ビットが立っているか確認するには、 @code{ls -ld /tmp} を行います。 パーミッションの最後のビットが @code{t} ならば、セットされています。 @cindex changing socket location You can change the place where MySQL uses / puts the socket file the following ways: @itemize @bullet @item Specify the path in a global or local option file. For example, put in @code{/etc/my.cnf}: @example [client] socket=path-for-socket-file [mysqld] socket=path-for-socket-file @end example @xref{Option files}. @item Specifying this on the command-line to @code{safe_mysqld} and most clients with the @code{--socket=path-for-socket-file} option. @item この場合、 @code{MYSQL_UNIX_PORT} 環境変数に設定することにより可能です。 @item Defining the path with the @code{configure} option @code{--with-unix-socket-path=path-for-socket-file}. @xref{configure options}. @end itemize ソケットのテストをする場合、以下のようにします： @example shell> mysqladmin --socket=/path/to/socket version @end example @node Timezone problems, , Problems with mysql.sock, Administration Issues @appendixsubsec Time Zone Problems @cindex timezone problems @cindex problems, timezone @tindex TZ environment variable @tindex Environment variable, TZ もし @code{SELECT NOW()} があなたのローカル時間ではなく GMT を返すなら、 @code{TZ} 環境変数をローカルのTimezone に設定しなくてはなりません。 環境変数の設定は、サーバーを実行する前に行われなくてはなりません。 たとえば、@code{safe_mysqld} や @code{mysql.server} スクリプトで 行います。 @xref{Environment variables}. @node Query Issues, Table Definition Issues, Administration Issues, Problems @appendixsec Query Related Issues @menu * Case sensitivity:: Case-Sensitivity in Searches * Using DATE:: Problems Using @code{DATE} Columns * Problems with NULL:: Problems with @code{NULL} Values * Problems with alias:: Problems with @code{alias} * Deleting from related tables:: Deleting Rows from Related Tables * No matching rows:: Solving Problems with No Matching Rows * Problems with float:: Problems with floating-point comparison @end menu @node Case sensitivity, Using DATE, Query Issues, Query Issues @appendixsubsec 検索時のケース依存 @cindex case-sensitivity, in searches @cindex searching, and case-sensitivity @cindex Chinese @cindex Big5 Chinese character encoding デフォルトでは MySQL フィールドはケース非依存です (しかし、ケース非依 存にならないいくつかの文字セットはありますsuch as @code{czech})。 これは、@code{col_name LIKE 'a%'} で検索した場合、@code{A} または @code{a} で始まる全てのフィールドを得ることを 意味します。検索をケース依存にしたいのなら、始まりをチェックするには @code{INDEX(column, "A")=1} のようなことを、また、文字列全体が同じかどう かには @code{STRCMP(column, "A") = 0} を使用してください。 単純な比較操作 @code{>=, >, =, <, <=}、ソートそしてグループ化は、文字 ``sort val ue'' 上で行われます。同じソート値の文字 (like E, e and @'e)は同じ文字と して扱われます！ In older MySQL versions @code{LIKE} comparisons where done on the uppercase value of each character (E == e but E <> 'e. In newer MySQL versions @code{LIKE} works just like the other comparison operators. あるフィールドをいつでもケース依存で扱いたい場合は、それを @code{BINARY} として宣言してください。 @xref{CREATE TABLE, , @code{CREATE TABLE}}. big5 エンコーディングと呼ばれる中国語データを使用している場合は、全ての 文字項目を @code{BINARY} にしてください。これは、big5 エンコーディング文 字のソート順が ascii コードが基になっているため、機能します。 @node Using DATE, Problems with NULL, Case sensitivity, Query Issues @appendixsubsec @code{DATE} フィールド使用時の問題 @findex DATE @cindex DATE columns, problems @cindex problems, @code{DATE} columns 日付 @code{DATE} の形式は @code{'YYYY-MM-DD'} です。ANSI SQL に従って実際には他 のは許されま せん。更新または @code{SELECT} 文中の WHERE 節内ではこの形式を使用すべきです。す なわち: @example mysql> SELECT * FROM tbl_name WHERE date >= '1997-05-05'; @end example 利便のため MySQL は、日付が数値の文脈で使用されると、日付を自動的に数 値に変換します。これにより、更新と @code{TIMESTAMP}, @code{DATE} または @code{DATETIME} フィールドでの @code{WHERE} 時に、わりと自由に日付を指定すること ができます。 (この記述を許すため、句読記号を日付のセパレーターとして使用します。 例えば、@code{'1998-08-15'} と @code{'1998#08#15'} は同一です.) もしろんセパレーターのない記述(例：@code{'19980815'})も日付として変換してくれま す。 特別な日付 @code{'0000-00-00'} は @code{'0000-00-00'} として格納され取り出されま す。 @code{MyODBC} を通して @code{'0000-00-00'} 日付を使用する時、@code{MyODBC} 2 .50.12 以上では自動的に @code{NULL} に変換されます。ODBC はこの日付の種類を扱え ないためです。 Because MySQL performs the conversions described above, the following statements work: @example mysql> INSERT INTO tbl_name (idate) VALUES (19970505); mysql> INSERT INTO tbl_name (idate) VALUES ('19970505'); mysql> INSERT INTO tbl_name (idate) VALUES ('97-05-05'); mysql> INSERT INTO tbl_name (idate) VALUES ('1997.05.05'); mysql> INSERT INTO tbl_name (idate) VALUES ('1997 05 05'); mysql> INSERT INTO tbl_name (idate) VALUES ('0000-00-00'); mysql> SELECT idate FROM tbl_name WHERE idate >= '1997-05-05'; mysql> SELECT idate FROM tbl_name WHERE idate >= 19970505; mysql> SELECT MOD(idate,100) FROM tbl_name WHERE idate >= 19970505; mysql> SELECT idate FROM tbl_name WHERE idate >= '19970505'; @end example @noindent 次は動きません @example mysql> SELECT idate FROM tbl_name WHERE STRCMP(idate,'19970505')=0; @end example @code{STRCMP()} は文字列関数で、@code{idate} を文字に変換して、文字比較を行いま す。 @code{'19970505'} は日付には変換してくれず、日付の比較も行いません。 MySQL は日付が正しいかどうかをチェックしないことに注意してください。 間違った日付(例えば @code{'1998-2-31'})を格納すると、その間違った日付が格 納されます。 Because MySQL packs dates for storage, it can't store any given date as it would not fit onto the result buffer. The rules for accepting a date are: @itemize @bullet @item If MySQL can store and retrieve a given date, the wrong date is accepted for @code{DATE} and @code{DATETIME} columns. @item All days values between 0-31 are accepted for any date. This makes it very convenient for web applications where you ask year, month and day in 3 different fields. @item The day or month field may be zero. This is convenient if you want to store a birthdate in a @code{DATE} column and you only know part of the date. @end itemize If the date cannot be converted to any reasonable value, a @code{0} is stored in the @code{DATE} field, which will be retrieved as @code{0000-00-00}. This is both a speed and convenience issue as we believe that the database's responsiblity is to retrieve the same date you stored (even if the data was not logically correct in all cases). We think it is up to the application to check the dates, and not the server. @node Problems with NULL, Problems with alias, Using DATE, Query Issues @appendixsubsec @code{NULL} 値での問題 @cindex @code{NULL} values, vs. empty values @tindex NULL SQL の初心者のありがちな混乱は、@code{NULL} 値が空文字列 @code{""} と同じ物だと 考えることです。これは正しくありません！ 例えば、次のステートメントは全く別の ものです: @example mysql> INSERT INTO my_table (phone) VALUES (NULL); mysql> INSERT INTO my_table (phone) VALUES (""); @end example 両方の文とも @code{phone} フィールドに値を挿入していますが、 初めのは @code{NULL} 値を挿入し、二番目のは空文字列を挿入しています。 初めのは ``電話番号を知らない'' と見なされ、二番目のは ``彼女は電話を 持っていない'' と見なされます。 SQL では、 @code{NULL} は他の全ての値(たとえ @code{NULL} でも)と比較した時に、 常に偽になる値です。 @code{NULL} を含む式は、特に断りがなければ、常に @code{NULL} 値を生成します。次の項目は全て @code{NULL} を返します: @example mysql> SELECT NULL,1+NULL,CONCAT('Invisible',NULL); @end example @code{NULL} 値がセットされている項目を検索する場合、 @code{=NULL} テストを行わないでください。 これは @code{expr = NULL} が FALSE なので、なんの行も返しません。 例えば以下の例： @example mysql> SELECT * FROM my_table WHERE phone = NULL; @end example @code{NULL} 値を持つフィールドを検索したい場合は、@code{IS NULL} テストを使用し なくてはいけま せん。次は @code{NULL} 電話番号と空の電話番号を見つける方法を示しています: @example mysql> SELECT * FROM my_table WHERE phone IS NULL; mysql> SELECT * FROM my_table WHERE phone = ""; @end example Note that you can only add an index on a column that can have @code{NULL} values if you are using MySQL Version 3.23.2 or newer and are using the @code{MyISAM} or @code{InnoDB} table type. Version 3.23.2 以前の MySQL では、他の多くの SQL サーバのように、@code{NULL} 値を持つ インデックスフィールドを持てません。これらのフィールドは @code{NOT NULL} と宣言 しなくてはいけません。 @findex LOAD DATA INFILE @code{LOAD DATA INFILE} でデータを読み込むときは、空のフィールドは @code{''} で 更新されます。 項目を @code{NULL} 値にしたい場合は、テキストファイル中に @code{\N} を使用すべき です。 リテラルとしての @code{'NULL'} 語が、ある状況下で使用されています。 @xref{LOAD DATA, , @code{LOAD DATA}}. When using @code{ORDER BY}, @code{NULL} values are presented first. In versions prior to 4.0.2, if you sort in descending order using @code{DESC}, @code{NULL} values are presented last. When using @code{GROUP BY}, all @code{NULL} values are regarded as equal. To help with @code{NULL} handling, you can use the @code{IS NULL} and @code{IS NOT NULL} operators and the @code{IFNULL()} function. @code{ORDER BY} 使用時, @code{NULL} 値は最初に提示されます. @code{DESC} を使用して降順にソートする時、@code{NULL} 値は最後になります。 @code{GROUP BY} 使用時, 全ての @code{NULL} 値は等しいと見なされます。 @code{NULL} 処理を手助けするため、次の関数を使用できます: @code{IS NULL}, @code{IS NOT NULL}, @code{IFNULL()}. @cindex @code{TIMESTAMP}, and @code{NULL} values @cindex @code{AUTO_INCREMENT}, and @code{NULL} values @cindex @code{NULL} values, and @code{TIMESTAMP} columns @cindex @code{NULL} values, and @code{AUTO_INCREMENT} columns いくつかの項目型では、@code{NULL} 値はハンドルとして扱われます。 もしテーブル内の最初の @code{TIMESTAMP} 項に @code{NULL} を挿入するなら、 現在の日付と時刻が挿入されます。もし @code{AUTO_INCREMENT} 項に@code{NULL} 値を 挿入するなら、 次のシーケンス番号が挿入されます。 @node Problems with alias, Deleting from related tables, Problems with NULL, Query Issues @appendixsubsec @code{alias} の問題 @tindex alias @code{GROUP BY}, @code{ORDER BY}, @code{HAVING} 節において 項目を参照するに当たりエイリアスが使用できます。 エイリアスは項目としてより良い名称を与えるのに使用されます： @example SELECT SQRT(a*b) as rt FROM table_name GROUP BY rt HAVING rt > 0; SELECT id,COUNT(*) AS cnt FROM table_name GROUP BY id HAVING cnt > 0; SELECT id AS "Customer identity" FROM table_name; @end example ANSI SQL が @code{WHERE} 節内でエイリアスを参照することを 許可していないことに注意してください。これは @code{WHERE} が実行される時点で 項目の値がまだ決定されていないからです。例えば、以下のクエリは @strong{あやまり です}： @example SELECT id,COUNT(*) AS cnt FROM table_name WHERE cnt > 0 GROUP BY id; @end example どの行が @code{GROUP BY} に含まれるかを決めるために @code{WHERE} 構文が 実行される一方で、 得られた結果のどの行を使うか確定するために @code{HAVING} が使用されます。 @node Deleting from related tables, No matching rows, Problems with alias, Query Issues @appendixsubsec Deleting Rows from Related Tables @cindex deleting, rows @cindex rows, deleting @cindex tables, deleting rows MySQL は現在 副問い合わせ は未サポート(バージョン4.1以上)です。また、 Version 4.0 以前では @code{DELETE} 構文で複数のテーブルを扱う事もサポートしていません。 したがって、２つのテーブルに関連するレコードを消すには、以下のようにして行います： @enumerate @item いくつかの @code{WHERE} 条件を使用して、基本となるテーブルから行を @code{SELECT} @item 同じ条件下で、基本となるテーブルに含まれる行を @code{DELETE} @item @code{DELETE FROM related_table WHERE related_column IN (selected_rows)}. @end enumerate @code{related_column} のクエリの合計文字数が、1,048,576 (デフォルトは @code{max_ allowed_packet} の値) をこえる場合、 それをいくつかに分割して、複数の @code{DELETE} 構文にしなくてはなりません。 @code{related_column} がインデックスで、100-1000 の@code{related_column}だけを消 す場合、よりはやく @code{DELETE} できます。 もし @code{related_column} がインデックスでない場合、その速度は @code{IN} 節の引 数の数に無関係になります。 @node No matching rows, Problems with float, Deleting from related tables, Query Issues @appendixsubsec Solving Problems with No Matching Rows @cindex no matching rows @cindex rows, matching problems 複雑なクエリーを行って、もしなんの結果も返さなければ、 そのクエリーの何が悪いかを見つけるため、以下の手続きを行います： @enumerate @item @code{EXPLAIN} を使用してクエリーをテストし、明白な間違いを見つけます。 @xref{EXPLAIN, , @code{EXPLAIN}}. @item @code{WHERE} 節で使用されているフィールドだけを Select してみます @item 結果が返ってくるまで、一つ一つクエリーからテーブルを取り除いていきます。 テーブルが大きい場合、@code{LIMIT 10} をクエリーで使用することは良くありません。 @item 行にマッチすべきであろう項を @code{SELECT} してみます。 その場合、select するのは、上記で最後に取り除いたテーブルに対して行います。 @item If you are comparing @code{FLOAT} or @code{DOUBLE} columns with numbers that have decimals, you can't use @code{'='}. This problem is common in most computer languages because floating-point values are not exact values. In most cases, changing the @code{FLOAT} to a @code{DOUBLE} will fix this. @xref{Problems with float}. @item もしなにも悪いところを見つけることができなかった場合、 小さなテストをつくって @code{mysql test < query.sql} を行ってみてください。 @code{mysqldump --quick database tables > query.sql} でテストファイルを作成でき ます。 このファイルをエディターで編集し、いくつかのinsert行を(多すぎるなら)消します。 そしてファイルの最後にselect構文を付け足します。 テストを行うには： @example shell> mysqladmin create test2 shell> mysql test2 < query.sql @end example @code{mysqlbug} を使用して @email{mysql@@lists.mysql.com} にテストを投稿してくだ さい。 @end enumerate @node Problems with float, , No matching rows, Query Issues @appendixsubsec Problems with Floating-Point Comparison floating-point numbers cause confusion sometimes, because these numbers are not stored as exact values inside computer architecture. What one can see on the screen usually is not the exact value of the number. Field types @code{FLOAT}, @code{DOUBLE} and @code{DECIMAL} are such. @example CREATE TABLE t1 (i INT, d1 DECIMAL(9,2), d2 DECIMAL(9,2)); INSERT INTO t1 VALUES (1, 101.40, 21.40), (1, -80.00, 0.00), (2, 0.00, 0.00), (2, -13.20, 0.00), (2, 59.60, 46.40), (2, 30.40, 30.40), (3, 37.00, 7.40), (3, -29.60, 0.00), (4, 60.00, 15.40), (4, -10.60, 0.00), (4, -34.00, 0.00), (5, 33.00, 0.00), (5, -25.80, 0.00), (5, 0.00, 7.20), (6, 0.00, 0.00), (6, -51.40, 0.00); mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b -> FROM t1 GROUP BY i HAVING a <> b; +------+--------+-------+ | i | a | b | +------+--------+-------+ | 1 | 21.40 | 21.40 | | 2 | 76.80 | 76.80 | | 3 | 7.40 | 7.40 | | 4 | 15.40 | 15.40 | | 5 | 7.20 | 7.20 | | 6 | -51.40 | 0.00 | +------+--------+-------+ @end example The result is correct. Although the first five records look like they shouldn't pass the comparison test, they may do so because the difference between the numbers show up around tenth decimal, or so depending on computer architecture. The problem cannot be solved by using ROUND() (or similar function), because the result is still a floating-point number. Example: @example mysql> SELECT i, ROUND(SUM(d1), 2) AS a, ROUND(SUM(d2), 2) AS b -> FROM t1 GROUP BY i HAVING a <> b; +------+--------+-------+ | i | a | b | +------+--------+-------+ | 1 | 21.40 | 21.40 | | 2 | 76.80 | 76.80 | | 3 | 7.40 | 7.40 | | 4 | 15.40 | 15.40 | | 5 | 7.20 | 7.20 | | 6 | -51.40 | 0.00 | +------+--------+-------+ @end example This is what the numbers in column 'a' look like: @example mysql> SELECT i, ROUND(SUM(d1), 2)*1.0000000000000000 AS a, -> ROUND(SUM(d2), 2) AS b FROM t1 GROUP BY i HAVING a <> b; +------+----------------------+-------+ | i | a | b | +------+----------------------+-------+ | 1 | 21.3999999999999986 | 21.40 | | 2 | 76.7999999999999972 | 76.80 | | 3 | 7.4000000000000004 | 7.40 | | 4 | 15.4000000000000004 | 15.40 | | 5 | 7.2000000000000002 | 7.20 | | 6 | -51.3999999999999986 | 0.00 | +------+----------------------+-------+ @end example Depending on the computer architecture you may or may not see similar results. Each CPU may evaluate floating-point numbers differently. For example in some machines you may get 'right' results by multiplaying both arguments with 1, an example follows. @strong{WARNING: NEVER TRUST THIS METHOD IN YOUR APPLICATION, THIS IS AN EXAMPLE OF A WRONG METHOD!!!} @example mysql> SELECT i, ROUND(SUM(d1), 2)*1 AS a, ROUND(SUM(d2), 2)*1 AS b -> FROM t1 GROUP BY i HAVING a <> b; +------+--------+------+ | i | a | b | +------+--------+------+ | 6 | -51.40 | 0.00 | +------+--------+------+ @end example The reason why the above example seems to be working is that on the particular machine where the test was done, the CPU floating-point arithmetics happens to round the numbers to same, but there is no rule that any CPU should do so, so it cannot be trusted. The correct way to do floating-point number comparison is to first decide on what is the wanted tolerance between the numbers and then do the comparsion against the tolerance number. For example, if we agree on that floating-point numbers should be regarded the same, if they are same with precision of one of ten thousand (0.0001), the comparsion should be done like this: @example mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1 -> GROUP BY i HAVING ABS(a - b) > 0.0001; +------+--------+------+ | i | a | b | +------+--------+------+ | 6 | -51.40 | 0.00 | +------+--------+------+ 1 row in set (0.00 sec) @end example And vice versa, if we wanted to get rows where the numbers are the same, the test would be: @example mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1 -> GROUP BY i HAVING ABS(a - b) < 0.0001; +------+-------+-------+ | i | a | b | +------+-------+-------+ | 1 | 21.40 | 21.40 | | 2 | 76.80 | 76.80 | | 3 | 7.40 | 7.40 | | 4 | 15.40 | 15.40 | | 5 | 7.20 | 7.20 | +------+-------+-------+ @end example @node Table Definition Issues, , Query Issues, Problems @appendixsec Table Definition Related Issues @menu * ALTER TABLE problems:: Problems with @code{ALTER TABLE}. * Change column order:: How To Change the Order of Columns in a Table * Temporary table problems:: TEMPORARY TABLE problems @end menu @node ALTER TABLE problems, Change column order, Table Definition Issues, Table Definition Issues @appendixsubsec Problems with @code{ALTER TABLE}. @tindex ALTER TABLE @cindex changing, table @cindex table, changing @code{ALTER TABLE} changes a table to the current character set. If you get a duplicate key error during @code{ALTER TABLE}, then the cause is either that the new character sets maps two keys to the same value or that the table is corrupted, in which case you should run @code{REPAIR TABLE} on the table. もし @code{ALTER TABLE} が以下のようなエラーで死んだ場合： @example Error on rename of './database/name.frm' to './database/B-a.frm' (Errcode: 17) @end example これは以前の @code{ALTER TABLE} で MySQL がクラッシュしており、 @file{A-something} か @file{B-something} という名前の、誤った情報を流している 古いテーブルが存在しています。 この場合、MySQL データディレクトリに入り、@code{A-} や @code{B-} で始まる 名前を持つファイルを全て消します。 (消す代わりにどこかに移動しても構いません。) @code{ALTER TABLE} は以下のように動作します: @itemize @bullet @item 変更要求のあった @file{A-xxx} という名前の新しいテーブルを作成。 @item 元のテーブル内の全ての行を @file{A-xxx} にコピー。 @item 元のテーブルを @file{B-xxx} に名称変更。 @item @file{A-xxx} は元のテーブル名に名称変更される。 @item @file{B-xxx} は消去される。 @end itemize もし名称変更の際に問題があると、MySQL は変更を取り消すように動きます。 致命的な問題が起きた場合(ありえませんが)、MySQL は元の古いテーブルを @file{B-xxx} という名前のままにしておきます。単にシステムレベルで名称変更すれば データは戻ります。 @node Change column order, Temporary table problems, ALTER TABLE problems, Table Definition Issues @appendixsubsec テーブル中でフィールドの順序を入れ替える方法 @cindex reordering, columns @cindex columns, changing @cindex changing, column order @cindex tables, changing column order SQLの主な目的はデータフォーマットからアプリケーションを切り離してしまうことにあります。そのため、常に取り出したいデータの順序を常に指定する必要があります。例えば、次のような文: @example SELECT col_name1, col_name2, col_name3 FROM tbl_name; @end example これは、@code{col_name1}, @code{col_name2}, @code{col_name3}, の順序でデータを返します。ここで、 @example SELECT col_name1, col_name3, col_name2 FROM tbl_name; @end example こうすると、@code{col_name1}, @code{col_name3}, @code{col_name2}, の順序でデータを返します。 アプリケージョン内で@code{SELECT *}やそのテーブル内での位置に依存してしまうような 取り出し方は@strong{けっして}するべきではありません。 というのは取り出されるデータの順序が常に@strong{保障されるものではない}からです。 単にフィールドの情報が変更されただけでアプリケーションがエラーが発生する可能性を有しているのです。 にもかかわらずフィールドの順序を変えたい場合には次のような方法があります。 @enumerate @item 新しいテーブルを望んでいるフィールドの順序で作成します。 @item @code{INSERT INTO new_table SELECT fields-in-new_table-order FROM old_table}. を実行します。 @item @code{old_table}をドロップするかリネームして下さい。 @item @code{ALTER TABLE new_table RENAME old_table}. を実行します。 @end enumerate You should @strong{never}, in an application, use @code{SELECT *} and retrieve the columns based on their position, because the order and position in which columns are returned @strong{cannot} may not remain the same (if you add/move/delete columns). A simple change to your database structure would then cause your application to fail. Of course @code{SELECT *} is quite suitable for testing queries. @node Temporary table problems, , Change column order, Table Definition Issues @appendixsubsec TEMPORARY TABLE 問題 @cindex temporary tables, problems @code{TEMPORARY TABLES}を用いる処理における制限を以下に示します。 @itemize @bullet @item テンポラリーテーブルでは@code{HEAP}, @code{ISAM}, @code{MyISAM}, @code{MERGE}, @code{InnoDB} の いづれかの型のみを持つことが可能です。 @item テンポラリーテーブルは一度のクエリで一回しか使用できません。例えば、次のようなものは動きません。 @example mysql> SELECT * FROM temporary_table, temporary_table AS t2; @end example @item @code{ALTER TABLE org_name RENAME new_name} は動作します。しかし、 @code{TEMPORARY}テーブルに@code{RENAME}を使用することはできません。 @end itemize @node Contrib, Credits, Problems, Top @appendix Contributed Programs @cindex contributed programs @cindex programs, contributed Many users of MySQL have contributed @emph{very} useful support tools and add-ons. A list of some software available from the MySQL website (or any mirror) is shown here. You can also visit our online listing of MySQL-related software at @uref{http://www.mysql.com/portal/software/}. The community facilities there also allow for your input! If you want to build MySQL support for the Perl @code{DBI}/@code{DBD} interface, you should fetch the @code{Data-Dumper}, @code{DBI}, and @code{Msql-Mysql-modules} files and install them. @xref{Perl support}. Note: The programs listed here can be freely downloaded and used. They are copyrighted by their respective owners. Please see individual product documentation for more details on licensing and terms. MySQL AB assumes no liability for the correctness of the information in this chapter or for the proper operation of the programs listed herein. @appendixsec APIs @cindex Perl, modules @itemize @bullet @item Perl Modules @itemize @minus @item @uref{http://www.mysql.com/Downloads/Contrib/KAMXbase1.2.tar.gz} Convert between @file{.dbf} files and MySQL tables. Perl module written by Pratap Pereira @email{pereira@@ee.eng.ohio-state.edu}, extended by Kevin A. McGrail @email{kmcgrail@@digital1.peregrinehw.com}. This converter can handle MEMO fields. @item @uref{http://www.mysql.com/Downloads/Contrib/HandySQL-1.1.tar.gz} HandySQL is a MySQL access module. It offers a C interface embedded in Perl and is approximately 20% faster than regular DBI. @end itemize @cindex OLEDB @item OLEDB @itemize @bullet @item @uref{http://www.mysql.com/Downloads/Win32/MyOLEDB3.exe} MyOLEDB 3.0 installation package from SWSoft. @item @uref{http://www.mysql.com/Downloads/Win32/mysql-oledb-3.0.0.zip} Source for MyOLEDB 3.0. @item @uref{http://www.mysql.com/Downloads/Win32/MySamples.zip} Examples and documentation for MyOLEDB. @item @uref{http://www.mysql.com/Downloads/Win32/MyOLEDB.chm} Help files for MyOLEDB. @item @uref{http://www.mysql.com/Downloads/Win32/libmyodbc.zip} Static MyODBC library used for build MyOLEDB. Based on MyODBC code. @end itemize @cindex C++ @item C++ @itemize @bullet @item @uref{http://www.mysql.com/Downloads/Contrib/mysql-c++-0.02.tar.gz} MySQL C++ wrapper library. By Roland Haenel, @email{rh@@ginster.net}. @item @uref{http://www.mysql.com/Downloads/Contrib/MyDAO.tar.gz} MySQL C++ API. By Satish @email{spitfire@@pn3.vsnl.net.in}. Inspired by Roland Haenel's C++ API and Ed Carp's MyC library. @item @uref{http://www.mysql.com/products/mysql++/} MySQL C++ API (more than just a wrapper library). Originally by @email{kevina@@clark.net}. Now maintained by Sinisa at MySQL AB. @item @uref{http://nelsonjr.homepage.com/NJrAPI/} A C++ database independent library that supports MySQL. @end itemize @cindex Delphi @item Delphi @itemize @bullet @item @uref{http://www.mysql.com/Downloads/Contrib/DelphiMySQL2.zip} Delphi interface to @code{libmysql.dll}, by @email{bsilva@@umesd.k12.or.us}. @item @uref{http://www.mysql.com/Downloads/Contrib/Udmysql.pas} A wrapper for libmysql.dll for usage in Delphi. By Reiner Sombrowsky. @item @uref{http://www.fichtner.net/delphi/mysql.delphi.phtml} A Delphi Interface to MySQL, with source code. By Matthias Fichtner. @item @uref{http://www.productivity.org/projects/tmysql/} @code{TmySQL}, a library to use MySQL with Delphi. @item @uref{https://sourceforge.net/projects/zeoslib/} Zeos Library is a set of delphi native datasets and database components for MySql, PostgreSql, Interbase, MS SQL, Oracle, DB/2. Also it includes development tools such as Database Explorer and Database Designer. @item @uref{http://www.mysql.com/Downloads/Contrib/Win32/SBMySQL50Share.exe} Delphi 5 Shareware MySQL Dataset Components. @end itemize @item @uref{http://www.mysql.com/Downloads/Contrib/mysql-ruby-2.2.0.tar.gz} MySQL Ruby module. By TOMITA Masahiro @email{tommy@@tmtm.org} Ruby is an Object-Oriented Interpreter Language (@uref{http://www.netlab.co.jp/ruby/}). @item @uref{http://www.mysql.com/Downloads/Contrib/JdmMysqlDriver-0.1.0.tar.gz} A VisualWorks 3.0 Smalltalk driver for MySQL. By @email{joshmiller@@earthlink.net}. @item @uref{http://www.mysql.com/Downloads/Contrib/Db.py} Python module with caching. By @email{gandalf@@rosmail.com}. @item @uref{http://www.mysql.com/Downloads/Contrib/MySQLmodule-1.4.tar.gz} Python interface for MySQL. By Joseph Skinner @email{joe@@earthlight.co.nz}. Modified by Joerg Senekowitsch @email{senekow@@ibm.net}. @item @uref{http://www.mysql.com/Downloads/Contrib/MySQL-python-0.3.0.tar.gz} MySQLdb Python is an DB-API v2.0-compliant interface to MySQL. Transactions are supported if the server and tables support them. It is thread-safe, and contains a compatibility module for older code written for the no-longer-maintained MySQLmodule interface. @item @uref{http://www.mysql.com/Downloads/Contrib/mysql_mex_12.tar.gz} An interface program for the Matlab program by MathWorks. The interface is done by Kimmo Uutela and John Fisher (not by Mathworks). Check @uref{http://boojum.hut.fi/~kuutela/mysqlmex.html} for more information. @item @uref{http://www.mysql.com/Downloads/Contrib/mysqltcl-1.53.tar.gz} Tcl interface for MySQL. Based on @file{msqltcl-1.50.tar.gz}. For version 2.0 and more info, see @uref{http://www.xdobry.de/mysqltcl/}. @item @uref{http://www.mysql.com/Downloads/Contrib/MyC-0.1.tar.gz} A Visual Basic-like API, by Ed Carp. @item @uref{http://www.mysql.com/Downloads/Contrib/Vdb-dflts-2.1.tar.gz} This is a new version of a set of library utilities intended to provide a generic interface to SQL database engines such that your application becomes a 3-tiered application. The advantage is that you can easily switch between and move to other database engines by implementing one file for the new backend without making any changes to your applications. By @email{damian@@cablenet.net}. @item @uref{http://www.mysql.com/Downloads/Contrib/DbFramework-1.10.tar.gz} DbFramework is a collection of classes for manipulating MySQL databases. The classes are loosely based on the CDIF Data Model Subject Area. By Paul Sharpe @email{paul@@miraclefish.com}. @item @uref{http://www.mysql.com/Downloads/Contrib/pike-mysql-1.4.tar.gz} MySQL module for pike. For use with the Roxen web server. @item @uref{http://www.mysql.com/Downloads/Contrib/squile.tar.gz} Module for @code{guile} that allows @code{guile} to interact with SQL databases. By Hal Roberts. @item @uref{http://www.mysql.com/Downloads/Contrib/stk-mysql.tar.gz} Interface for Stk. Stk is the Tk widgets with Scheme underneath instead of Tcl. By Terry Jones. @item @uref{http://www.mysql.com/Downloads/Contrib/eiffel-wrapper-1.0.tar.gz} Eiffel wrapper by Michael Ravits. @item @uref{http://www.mysql.com/Downloads/Contrib/SQLmy0.06.tgz} FlagShip Replaceable Database Driver (RDD) for MySQL. By Alejandro Fernandez Herrero. The Flagship RDD homepage is at @uref{http://www.fship.com/rdds.html}. @item @uref{http://www.mysql.com/Downloads/Contrib/mydsn-1.0.zip} Binary and source for @code{mydsn.dll}. mydsn should be used to build and remove the DSN registry file for the MyODBC driver in Coldfusion applications. By Miguel Angel Solrzano. @item @uref{http://www.mysql.com/Downloads/Contrib/MySQL-ADA95_API.zip} An ADA95 interface to the MySQL API. By Francois Fabien. @item @uref{http://www.mysql.com/Downloads/Contrib/MyTool-DLL_for_VB_and_MySQL.zip} A DLL with MySQL C API for Visual Basic. By Ken Menzel @email{kenm@@icarz.com}. @item @uref{http://www.mysql.com/Downloads/Contrib/MYSQLX.EXE} MySQL ActiveX Object for directly accessing your MySQL servers from IIS/ASP, VB, VC++ skipping the slower ODBC methods. Fully updatable, multi-threaded with full support for all MySQL fieldtypes (version 2001.1.1). By SciBit @uref{http://www.scibit.com/}. @item @uref{http://www.fastflow.it/mylua/} MyLUA home page; how to use the LUA language to write MySQL @code{PROCEDURE} that can be loaded runtime. @itemize @bullet @item @uref{http://www.mysql.com/Downloads/Contrib/lua-4.0.tar.gz} LUA 4.0 @item @uref{http://www.mysql.com/Downloads/Contrib/mylua-3.23.32.1.tar.gz} Patch for MySQL 3.23.32 to use LUA 4.0. By Cristian Giussani. @end itemize @item @uref{http://www.mysql.com/Downloads/Contrib/patched_myodbc.zip} Patch (for Omniform 4.0 support) to the MyODBC driver. By Thomas Thaele @email{tthaele@@papenmeier.de} @end itemize @cindex converters @appendixsec Converters @itemize @bullet @item @uref{http://www.mysql.com/Downloads/Contrib/mssql2mysql.txt} Converter from MS-SQL to MySQL. By Michael Kofler. The mssql2mysql home page is at @uref{http://www.kofler.cc/mysql/mssql2mysql.html}. @item @uref{http://www.mysql.com/Downloads/Contrib/dbf2mysql-1.14.tar.gz} Convert between @file{.dbf} files and MySQL tables. By Maarten Boekhold (@email{boekhold@@cindy.et.tudelft.nl}), William Volkman, and Michael Widenius. This converter includes rudimentary read-only support for MEMO fields. @item @uref{http://www.mysql.com/Downloads/Contrib/dbf2mysql-1.13.tgz} Convert between @file{.dbf} files and MySQL tables. By Maarten Boekhold, @email{boekhold@@cindy.et.tudelft.nl}, and Michael Widenius. This converter can't handle MEMO fields. @item @uref{http://www.mysql.com/Downloads/Contrib/dbf2mysql.zip} Convert between FoxPro @file{.dbf} files and MySQL tables on Windows. By Alexander Eltsyn, @email{ae@@nica.ru} or @email{ae@@usa.net}. @item @uref{http://www.mysql.com/Downloads/Contrib/dbf2sql.zip} Short and simple prg that can help you transport your data from foxpro table into MySQL table. By Danko Josic. @item @uref{http://www.mysql.com/Downloads/Contrib/dump2h-1.20.gz} Convert from @code{mysqldump} output to a C header file. By Harry Brueckner, @email{brueckner@@mail.respublica.de}. @item @uref{http://www.mysql.com/Downloads/Contrib/exportsql.txt} A script that is similar to @code{access_to_mysql.txt}, except that this one is fully configurable, has better type conversion (including detection of @code{TIMESTAMP} fields), provides warnings and suggestions while converting, quotes @strong{all} special characters in text and binary data, and so on. It will also convert to @code{mSQL} v1 and v2, and is free of charge for anyone. See @uref{http://www.cynergi.net/exportsql/} for the latest version. By Pedro Freire, @email{support@@cynergi.net}. Note: Doesn't work with Access2! @item @uref{http://www.mysql.com/Downloads/Contrib/access_to_mysql.txt} Paste this function into an Access module of a database that has the tables you want to export. See also @code{exportsql}. By Brian Andrews. Note: Doesn't work with Access2! @item @uref{http://www.mysql.com/Downloads/Contrib/importsql.txt} A script that does the exact reverse of @code{exportsql.txt}. That is, it imports data from MySQL into an Access database via ODBC. This is very handy when combined with exportsql, because it lets you use Access for all DB design and administration, and synchronise with your actual MySQL server either way. Free of charge. See @uref{http://www.netdive.com/freebies/importsql/} for any updates. Created by Laurent Bossavit of NetDIVE. @strong{Note}: doesn't work with Access2! @item @uref{http://www.mysql.com/Downloads/Contrib/mdb2sql.bas} Converter from Access97 to MySQL by Moshe Gurvich. @item @uref{http://www.mysql.com/Downloads/Contrib/msql2mysqlWrapper-1.0.tgz} A C wrapper from @code{mSQL} to MySQL. By @email{alfred@@sb.net} @item @uref{http://www.mysql.com/Downloads/Contrib/sqlconv.pl} A simple script that can be used to copy fields from one MySQL table to another in bulk. Basically, you can run @code{mysqldump} and pipe it to the @code{sqlconv.pl} script. The script will parse through the @code{mysqldump} output and will rearrange the fields so they can be inserted into a new table. An example is when you want to create a new table for a different site you are working on, but the table is just a bit different (that is - fields in different order, etc.). By Steve Shreeve. @item @uref{http://www.mysql.com/Downloads/Contrib/oracledump} Perl program to convert Oracle databases to MySQL. Has same output format as mysqldump. By Johan Andersson. @item @uref{http://www.mysql.com/Downloads/Contrib/excel2mysql} Perl program to import Excel spreadsheets into a MySQL database. By Stephen Hurd @email{shurd@@sk.sympatico.ca} @item @uref{http://www.mysql.com/Downloads/Contrib/T2S_100.ZIP}. Windows program to convert text files to MySQL databases. By Asaf Azulay. @end itemize @cindex utilities @appendixsec Utilities @itemize @bullet @item @uref{http://worldcommunity.com/opensource/utilities/mysql_backup.html} MySQL Backup is a backup script for MySQL. By Peter F. Brown. @item @uref{http://www.mysql.com/Downloads/Contrib/mysql_watchdog.pl} Monitor the MySQL daemon for possible lockups. By Yermo Lamers, @email{yml@@yml.com}. @item @uref{http://www.mysql.com/Downloads/Contrib/mysql_structure_dumper.tar.gz} @item @uref{http://www.mysql.com/Downloads/Contrib/mysql_structure_dumper.tgz} Prints the structure of every table in a database. By Thomas Wana. @item @uref{http://www.mysql.com/Downloads/Contrib/mysqlsync}. A Perl script to keep remote copies of a MySQL database in sync with a central master copy. By Mark Jeftovic. @email{markjr@@easydns.com}. @item @uref{http://www.mysql.com/Downloads/Contrib/MySQLTutor-0.2.tar.gz}. MySQLTutor. A MySQL tutorial for beginners. @item @uref{http://www.mysql.com/Downloads/Contrib/MySQLDB.zip} @item @uref{http://www.mysql.com/Downloads/Contrib/MySQLDB-readme.html}. A COM library for MySQL by Alok Singh. @item @uref{http://www.mysql.com/Downloads/Contrib/mysql_replicate.pl} Perl program that handles replication. By @email{elble@@icculus.nsg.nwu.edu} @item @uref{http://www.mysql.com/Downloads/Contrib/DBIx-TextIndex-0.02.tar.gz} Perl script that uses reverse indexing to handle text searching. By Daniel Koch. @item @uref{http://www.mysql.com/Downloads/Contrib/dbcheck} Perl script that takes a backup of tables before running isamchk on them. By Elizabeth. @item @uref{http://www.mysql.com/Downloads/Contrib/mybackup}. @item @uref{http://www.mswanson.com/mybackup} (mybackup home page) Wrapper for mysqldump to backup all databases. By Marc Swanson. @item @uref{http://www.mysql.com/Downloads/Contrib/mdu.pl.gz} Prints the storage usage of a MySQL database. @end itemize @page @node Credits, News, Contrib, Top @appendix Credits @cindex developers, list of This appendix lists the developers, contributors, and supporters that have helped to make MySQL what it is today. @menu * Developers:: Developers at MySQL AB * Contributors:: Contributors to MySQL * Supporters:: Supporters to MySQL @end menu @node Developers, Contributors, Credits, Credits @appendixsec Developers at MySQL AB These are the developers that are or have been employed by @code{MySQL AB} to work on the @code{MySQL} database software, roughly in the order they started to work with us. Following each developer is a small list of the tasks that the developer is responsible for, or the accomplishments they have made. All developers are involved in support. @c Updated by arjen 2002-08-06 @c Note: this is a non-exhaustive list. It just documents some notable @c achievements, not each individual task. Nor is it a complete list @c of past/present job roles (see above). That said, updates welcome! @table @asis @item Michael (Monty) Widenius @itemize @bullet @item Lead developer and main author of the MySQL server (@code{mysqld}). @item New functions for the string library. @item Most of the @code{mysys} library. @item The @code{ISAM} and @code{MyISAM} libraries (B-tree index file handlers with index compression and different record formats). @item The @code{HEAP} library. A memory table system with our superior full dynamic hashing. In use since 1981 and published around 1984. @item The @code{replace} program (take a look at it, it's @strong{COOL}!). @item @code{MyODBC}, the ODBC driver for Windows95. @item Fixing bugs in MIT-pthreads to get it to work for MySQL Server. And also Unireg, a curses-based application tool with many utilities. @item Porting of @code{mSQL} tools like @code{msqlperl}, @code{DBD}/@code{DBI}, and @code{DB2mysql}. @item Most of @code{crash-me} and the foundation for the MySQL benchmarks. @end itemize @item David Axmark @itemize @bullet @item Initial main writer of the @strong{Reference Manual}, including enhancements to @code{texi2html}. @item Automatic web site updating from the manual. @item Initial Autoconf, Automake, and Libtool support. @item Licensing. @item Parts of all the text files. (Nowadays only the @file{README} is left. The rest ended up in the manual.) @item Lots of testing of new features. @item Our in-house Free Software legal expert. @item Mailing list maintainer (who never has the time to do it right...). @item Our original portability code (more than 10 years old now). Nowadays only some parts of @code{mysys} are left. @item Someone for Monty to call in the middle of the night when he just got that new feature to work. @item Chief "Open Sourcerer" (MySQL community relations). @end itemize @item Jani Tolonen @itemize @bullet @item @code{mysqlimport} @item A lot of extensions to the command-line clients. @item @code{PROCEDURE ANALYSE()} @end itemize @item Sinisa Milivojevic @itemize @bullet @item Compression (with @code{zlib}) in the client/server protocol. @item Perfect hashing for the lexical analyser phase. @item Multi-row @code{INSERT} @item @code{mysqldump} -e option @item @code{LOAD DATA LOCAL INFILE} @item @code{SQL_CALC_FOUND_ROWS} @code{SELECT} option @item @code{--max-user-connections=...} option @item @code{net_read} and @code{net_write_timeout} @item @code{GRANT}/@code{REVOKE} and @code{SHOW GRANTS FOR} @item New client-server protocol for 4.0 @item @code{UNION} in 4.0 @item Multi-table @code{DELETE}/@code{UPDATE} @item Derived tables in 4.1 @item User resources management @item Initial developer of the @code{MySQL++} C++ API and the @code{MySQLGUI} client. @end itemize @item Tonu Samuel (past developer) @itemize @bullet @item VIO interface (the foundation for the encrypted client/server protocol). @item MySQL Filesystem (a way to use MySQL databases as files and directories). @item The @code{CASE} expression. @item The @code{MD5()} and @code{COALESCE()} functions. @item @code{RAID} support for @code{MyISAM} tables. @end itemize @item Sasha Pachev @itemize @bullet @item Initial implementation of replication (upto version 4.0). @item @code{SHOW CREATE TABLE}. @item @code{mysql-bench} @end itemize @item Matt Wagner @itemize @bullet @item MySQL test suite. @item Webmaster (until 2002). @item Coordinator of development. @end itemize @item Miguel Solorzano @itemize @bullet @item Win32 development and release builds. @item Windows NT server code. @item WinMySQLAdmin @end itemize @item Timothy Smith (past developer) @itemize @bullet @item Dynamic character sets support. @item configure, RPMs and other parts of the build system. @item Initial developer of @code{libmysqld}, the embedded server. @end itemize @item Sergei Golubchik @itemize @bullet @item Full-text search. @item Added keys to the @code{MERGE} library. @end itemize @item Jeremy Cole @itemize @bullet @item Proofreading and editing this fine manual. @item @code{ALTER TABLE ... ORDER BY ...}. @item @code{UPDATE ... ORDER BY ...}. @item @code{DELETE ... ORDER BY ...}. @end itemize @item Indrek Siitan @itemize @bullet @item Designing/programming of our web interface. @item Author of our newsletter management system. @end itemize @item Jorge del Conde @itemize @bullet @item @code{MySQLCC} (@code{MySQL Control Center}) @item Win32 development @item Initial implementation of the website portals. @end itemize @item Venu Anuganti @itemize @bullet @item MyODBC 3.51 @item New client/server protocol for 4.1 (for prepared statements). @item @end itemize @item Arjen Lentz @itemize @bullet @item Maintainer of the MySQL Reference Manual. @item Preparing the O'Reilly printed edition of the manual. @end itemize @item Alexander (Bar) Barkov, Alexey (Holyfoot) Botchkov, and Ramil Kalimullin @itemize @bullet @item Spatial data (GIS) and R-Trees implementation for 4.1 @item Unicode and character sets for 4.1 @end itemize @item Oleksandr (Sanja) Byelkin @itemize @bullet @item Query cache in 4.0 @item Implementation of subqueries (4.1). @end itemize @item Aleksey (Walrus) Kishkin and Alexey (Ranger) Stroganov @itemize @bullet @item Benchmarks design and analysis. @item Maintenance of the MySQL test suite. @end itemize @item Zak Greant @itemize @bullet @item Open Source advocate, MySQL community relations. @end itemize @item Carsten Pedersen @itemize @bullet @item The MySQL Certification program. @end itemize @item Lenz Grimmer @itemize @bullet @item Production (build and release) engineering. @end itemize @item Peter Zaitsev @itemize @bullet @item @code{SHA1()}, @code{AES_ENCRYPT()} and @code{AES_DECRYPT()} functions. @item Debugging, cleaning up various features. @end itemize @item Alexander (Salle) Keremidarski @itemize @bullet @item Documentation of existing MySQL code/algorithms. @item Debugging. @end itemize @item Per-Erik Martin @itemize @bullet @item Lead developer for stored procedures and triggers. @end itemize @item Jim Winstead @itemize @bullet @item Lead web developer. @end itemize @item Mark Matthews @itemize @bullet @item Connector/J driver (Java). @end itemize @end table @node Contributors, Supporters, Developers, Credits @appendixsec Contributors to MySQL @cindex contributors, list of While @code{MySQL AB} owns all copyrights in the @code{MySQL server} and the @code{MySQL manual}, we wish to recognise those who have made contributions of one kind or another to the @code{MySQL distribution}. Contributors are listed here, in somewhat random order: @table @asis @item Paul DuBois Ongoing help with making this manual correct and understandable. That includes rewriting Monty's and David's attempts at English into English as other people know it. @item Gianmassimo Vigazzola @email{qwerg@@mbox.vol.it} or @email{qwerg@@tin.it} The initial port to Win32/NT. @item Kim Aldale Helped to rewrite Monty's and David's early attempts at English into English. @item Per Eric Olsson For more or less constructive criticism and real testing of the dynamic record format. @item Irena Pancirov @email{irena@@mail.yacc.it} Win32 port with Borland compiler. @code{mysqlshutdown.exe} and @code{mysqlwatch.exe} @item David J. Hughes For the effort to make a shareware SQL database. At TcX, the predecessor of MySQL AB, we started with @code{mSQL}, but found that it couldn't satisfy our purposes so instead we wrote a SQL interface to our application builder Unireg. @code{mysqladmin} and @code{mysql} client are programs that were largely influenced by their @code{mSQL} counterparts. We have put a lot of effort into making the MySQL syntax a superset of @code{mSQL}. Many of the API's ideas are borrowed from @code{mSQL} to make it easy to port free @code{mSQL} programs to the MySQL API. The MySQL software doesn't contain any code from @code{mSQL}. Two files in the distribution (@file{client/insert_test.c} and @file{client/select_test.c}) are based on the corresponding (non-copyrighted) files in the @code{mSQL} distribution, but are modified as examples showing the changes necessary to convert code from @code{mSQL} to MySQL Server. (@code{mSQL} is copyrighted David J. Hughes.) @item Fred Fish For his excellent C debugging and trace library. Monty has made a number of smaller improvements to the library (speed and additional options). @item Richard A. O'Keefe For his public domain string library. @item Henry Spencer For his regex library, used in @code{WHERE column REGEXP regexp}. @item Free Software Foundation From whom we got an excellent compiler (@code{gcc}), the @code{libc} library (from which we have borrowed @file{strto.c} to get some code working in Linux), and the @code{readline} library (for the @code{mysql} client). @item Free Software Foundation & The XEmacs development team For a really great editor/environment used by almost everybody at MySQL AB/TcX/detron. @item Patrick Lynch For helping us acquire @uref{http://www.mysql.com/}. @item Fred Lindberg For setting up qmail to handle the MySQL mailing list and for the incredible help we got in managing the MySQL mailing lists. @item Igor Romanenko @email{igor@@frog.kiev.ua} @code{mysqldump} (previously @code{msqldump}, but ported and enhanced by Monty). @item Yuri Dario For keeping up and extending the MySQL OS/2 port. @item Tim Bunce, Alligator Descartes For the @code{DBD} (Perl) interface. @item Tim Bunce Author of @code{mysqlhotcopy}. @item Andreas Koenig @email{a.koenig@@mind.de} For the Perl interface for MySQL Server. @item Eugene Chan @email{eugene@@acenet.com.sg} For porting PHP for MySQL Server. @item Michael J. Miller Jr. @email{mke@@terrapin.turbolift.com} For the first MySQL manual. And a lot of spelling/language fixes for the FAQ (that turned into the MySQL manual a long time ago). @item Yan Cailin First translator of the MySQL Reference Manual into simplified chinese in early 2000 on which the Big5 and HK coded (@uref{http://mysql.hitstar.com/}) versions were based. @uref{http://linuxdb.yeah.net, Personal home page at linuxdb.yeah.net}. @item Giovanni Maruzzelli @email{maruzz@@matrice.it} For porting iODBC (Unix ODBC). @item Chris Provenzano Portable user level pthreads. From the copyright: This product includes software developed by Chris Provenzano, the University of California, Berkeley, and contributors. We are currently using version 1_60_beta6 patched by Monty (see @file{mit-pthreads/Changes-mysql}). @item Xavier Leroy @email{Xavier.Leroy@@inria.fr} The author of LinuxThreads (used by the MySQL Server on Linux). @item Zarko Mocnik @email{zarko.mocnik@@dem.si} Sorting for Slovenian language and the @file{cset.tar.gz} module that makes it easier to add other character sets. @item "TAMITO" @email{tommy@@valley.ne.jp} The @code{_MB} character set macros and the ujis and sjis character sets. @item Joshua Chamas @email{joshua@@chamas.com} Base for concurrent insert, extended date syntax, debugging on NT, and answering on the MySQL mailing list. @item Yves Carlier @email{Yves.Carlier@@rug.ac.be} @code{mysqlaccess}, a program to show the access rights for a user. @item Rhys Jones @email{rhys@@wales.com} (And GWE Technologies Limited) For JDBC, a module to extract data from a MySQL Database with a Java client. @item Dr Xiaokun Kelvin ZHU @email{X.Zhu@@brad.ac.uk} Further development of the JDBC driver and other MySQL-related Java tools. @item James Cooper @email{pixel@@organic.com} For setting up a searchable mailing list archive at his site. @item Rick Mehalick @email{Rick_Mehalick@@i-o.com} For @code{xmysql}, a graphical X client for MySQL Server. @item Doug Sisk @email{sisk@@wix.com} For providing RPM packages of MySQL for RedHat Linux. @item Diemand Alexander V. @email{axeld@@vial.ethz.ch} For providing RPM packages of MySQL for RedHat Linux-Alpha. @item Antoni Pamies Olive @email{toni@@readysoft.es} For providing RPM versions of a lot of MySQL clients for Intel and SPARC. @item Jay Bloodworth @email{jay@@pathways.sde.state.sc.us} For providing RPM versions for MySQL Version 3.21. @item Jochen Wiedmann @email{wiedmann@@neckar-alb.de} For maintaining the Perl @code{DBD::mysql} module. @item Therrien Gilbert @email{gilbert@@ican.net}, Jean-Marc Pouyot @email{jmp@@scalaire.fr} French error messages. @item Petr Snajdr, @email{snajdr@@pvt.net} Czech error messages. @item Jaroslaw Lewandowski @email{jotel@@itnet.com.pl} Polish error messages. @item Miguel Angel Fernandez Roiz Spanish error messages. @item Roy-Magne Mo @email{rmo@@www.hivolda.no} Norwegian error messages and testing of Version 3.21.#. @item Timur I. Bakeyev @email{root@@timur.tatarstan.ru} Russian error messages. @item @email{brenno@@dewinter.com} & Filippo Grassilli @email{phil@@hyppo.com} Italian error messages. @item Dirk Munzinger @email{dirk@@trinity.saar.de} German error messages. @item Billik Stefan @email{billik@@sun.uniag.sk} Slovak error messages. @item Stefan Saroiu @email{tzoompy@@cs.washington.edu} Romanian error messages. @item Peter Feher Hungarian error messages. @item Roberto M. Serqueira Portugise error messages. @item Carsten H. Pedersen Danish error messages. @item Arjen G. Lentz Dutch error messages, completing earlier partial translation (also work on consistency and spelling). @item David Sacerdote @email{davids@@secnet.com} Ideas for secure checking of DNS hostnames. @item Wei-Jou Chen @email{jou@@nematic.ieo.nctu.edu.tw} Some support for Chinese(BIG5) characters. @item Wei He @email{hewei@@mail.ied.ac.cn} A lot of functionality for the Chinese(GBK) character set. @item Zeev Suraski @email{bourbon@@netvision.net.il} @code{FROM_UNIXTIME()} time formatting, @code{ENCRYPT()} functions, and @code{bison} advisor. Active mailing list member. @item Luuk de Boer @email{luuk@@wxs.nl} Ported (and extended) the benchmark suite to @code{DBI}/@code{DBD}. Have been of great help with @code{crash-me} and running benchmarks. Some new date functions. The @code{mysql_setpermissions} script. @item Jay Flaherty @email{fty@@mediapulse.com} Big parts of the Perl @code{DBI}/@code{DBD} section in the manual. @item Paul Southworth @email{pauls@@etext.org}, Ray Loyzaga @email{yar@@cs.su.oz.au} Proof-reading of the Reference Manual. @item Alexis Mikhailov @email{root@@medinf.chuvashia.su} User-definable functions (UDFs); @code{CREATE FUNCTION} and @code{DROP FUNCTION}. @item Andreas F. Bobak @email{bobak@@relog.ch} The @code{AGGREGATE} extension to UDF functions. @item Ross Wakelin @email{R.Wakelin@@march.co.uk} Help to set up InstallShield for MySQL-Win32. @item Jethro Wright III @email{jetman@@li.net} The @file{libmysql.dll} library. @item James Pereria @email{jpereira@@iafrica.com} Mysqlmanager, a Win32 GUI tool for administrating MySQL Server. @item Curt Sampson @email{cjs@@portal.ca} Porting of MIT-pthreads to NetBSD/Alpha and NetBSD 1.3/i386. @item Antony T. Curtis @email{antony.curtis@@olcs.net} Porting of the MySQL Database software to OS/2. @item Martin Ramsch @email{m.ramsch@@computer.org} Examples in the MySQL Tutorial. @item Steve Harvey For making @code{mysqlaccess} more secure. @item Konark IA-64 Centre of Persistent Systems Private Limited @uref{http://www.pspl.co.in/konark/}. Help with the Win64 port of the MySQL server. @item Albert Chin-A-Young. Configure updates for Tru64, large file support and better TCP wrappers support. @item John Birrell Emulation of @code{pthread_mutex()} for OS/2. @item Benjamin Pflugmann Extended @code{MERGE} tables to handle @code{INSERTS}. Active member on the MySQL mailing lists. @item Guilhem Bichot Fixed handling of exponents for @code{DECIMAL}. Author of @code{mysql_tableinfo}. @item Jocelyn Fournier Excellent spotting and reporting innumerable bugs (especially in the MySQL 4.1 subquery code). @item Georg Richter MySQL 4.1 testing and bug hunting. New PHP 5.0 @code{mysqli} extension (API) for use with MySQL 4.1 and up. @item Marc Liyanage Maintaining the Mac OS X packages and providing invaluable feedback on how to create Mac OS X PKGs. @end table Other contributors, bugfinders, and testers: James H. Thompson, Maurizio Menghini, Wojciech Tryc, Luca Berra, Zarko Mocnik, Wim Bonis, Elmar Haneke, @email{jehamby@@lightside}, @email{psmith@@BayNetworks.com}, @email{duane@@connect.com.au}, Ted Deppner @email{ted@@psyber.com}, Mike Simons, Jaakko Hyvatti. And lots of bug report/patches from the folks on the mailing list. A big tribute goes to those that help us answer questions on the @code{mysql@@lists.mysql.com} mailing list: @table @asis @item Daniel Koch @email{dkoch@@amcity.com} Irix setup. @item Luuk de Boer @email{luuk@@wxs.nl} Benchmark questions. @item Tim Sailer @email{tps@@users.buoy.com} @code{DBD-mysql} questions. @item Boyd Lynn Gerber @email{gerberb@@zenez.com} SCO-related questions. @item Richard Mehalick @email{RM186061@@shellus.com} @code{xmysql}-related questions and basic installation questions. @item Zeev Suraski @email{bourbon@@netvision.net.il} Apache module configuration questions (log & auth), PHP-related questions, SQL syntax-related questions and other general questions. @item Francesc Guasch @email{frankie@@citel.upc.es} General questions. @item Jonathan J Smith @email{jsmith@@wtp.net} Questions pertaining to OS-specifics with Linux, SQL syntax, and other things that might need some work. @item David Sklar @email{sklar@@student.net} Using MySQL from PHP and Perl. @item Alistair MacDonald @email{A.MacDonald@@uel.ac.uk} Not yet specified, but is flexible and can handle Linux and maybe HP-UX. Will try to get user to use @code{mysqlbug}. @item John Lyon @email{jlyon@@imag.net} Questions about installing MySQL on Linux systems, using either @file{.rpm} files or compiling from source. @item Lorvid Ltd. @email{lorvid@@WOLFENET.com} Simple billing/license/support/copyright issues. @item Patrick Sherrill @email{patrick@@coconet.com} ODBC and VisualC++ interface questions. @item Randy Harmon @email{rjharmon@@uptimecomputers.com} @code{DBD}, Linux, some SQL syntax questions. @end table @node Supporters, , Contributors, Credits @appendixsec Supporters to MySQL @cindex contributing companies, list of While @code{MySQL AB} owns all copyrights in the @code{MySQL server} and the @code{MySQL manual}, we wish to recognise the following companies, which helped us finance the development of the @code{MySQL server}, such as by paying us for developing a new feature or giving us hardware for development of the @code{MySQL server}. @table @asis @item VA Linux / Andover.net Funded replication. @item NuSphere Editing of the MySQL manual. @item Stork Design studio The MySQL web site in use between 1998-2000. @item Intel Contributed to development on Windows and Linux platforms. @item Compaq Contributed to Development on Linux/Alpha. @item SWSoft Development on the embedded @code{mysqld} version. @item FutureQuest @code{--skip-show-database} @end table @node News, Porting, Credits, Top @appendix MySQL Change History @cindex ChangeLog @cindex changes, log @cindex log, changes This appendix lists the changes from version to version in the MySQL source code. We are now working actively on MySQL 4.1 & 5.0 and will only provide critical bug fixes for MySQL 4.0 and MySQL 3.23. We update this section as we add new features, so that everybody can follow the development. Our TODO section contains what further plans we have for 4.1 & 5.0. @xref{TODO}. 新しい変更を MySQL に施すと同時に、マニュアルを変更することに注意してください。 もしマニュアルにかかれているのに MySQL download page (@uref{http://www.mysql.com/downloads/}) に 新しいバージョンの MySQL が見つからない場合、そのバージョンはまだリリースされていません！ @c Please don't add a new version here without also updating Docs/include.texi! @menu * News-5.0.x:: Changes in release 5.0.0 (Development) * News-4.1.x:: Changes in release 4.1.x (Alpha) * News-4.0.x:: Changes in release 4.0.x (Gamma) * News-3.23.x:: Changes in release 3.23.x (Stable) * News-3.22.x:: Changes in release 3.22.x (Older; Still supported) * News-3.21.x:: Changes in release 3.21.x * News-3.20.x:: Changes in release 3.20.x * News-3.19.x:: Changes in release 3.19.x @end menu @node News-5.0.x, News-4.1.x, News, News @appendixsec Changes in release 5.0.0 (Development) @cindex changes, version 5.0 Version 5.0 is for the moment only available on for MySQL developers. It will be publicly available as soon we are confident that the base for stored procedures is sound and working. The following changelog shows what is already done in the 5.0 tree: @itemize @bullet @item Some support for stored procedures (ANSI SQL 99 style). @item Added SELECT INTO list_of_vars, which can be of mixed, i.e., global and local type. @end itemize @node News-4.1.x, News-4.0.x, News-5.0.x, News @appendixsec Changes in release 4.1.x (Alpha) @cindex changes, version 4.1 Version 4.1 of the MySQL server includes many enhancements and new features: This version is available from our public bk tree and will be available as a binary shortly @itemize @bullet @item Subqueries: @example SELECT * from t1 where t1.a=(SELECT t2.b FROM t2); SELECT * from t1 where (1,2,3) in (SELECT a,b,c from t2); @end example @item Derived tables: @example SELECT t1.a from t1, (select * from t2) t3 WHERE t1.a=t3.a; @end example @item @code{INSERT ... ON DUPLICATE KEY UPDATE} syntax. This allows you to @code{UPDATE} an existing row if existed from before. (@code{REPLACE} allows you to overwrite an existing row, which is a different thing). @item Unicode (UTF8) support. @item Character sets can be defined per column, table and database. @item @code{BTREE} index on @code{HEAP} tables. @item Support for GIS (Geometrical data). @item @code{SHOW WARNINGS}; Shows warnings for the last command. @xref{SHOW WARNINGS}. @item Faster binary protocol used with prepared statements. @item Multi-line queries: You can now issue several queries at once and then read the results in one go. @item Create Table: @code{CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table LIKE table}. @end itemize For a full list of changes, please refer to the changelog sections for each individual 4.1.x release. @menu * News-4.1.0:: Changes in release 4.1.0 @end menu @node News-4.1.0, , News-4.1.x, News-4.1.x @appendixsubsec Changes in release 4.1.0 @itemize @item On Windows, we are now using shared memory to communicate between server and client when they are running on the same machine and you are connecting to @code{localhost}. @item @code{REPAIR of MyISAM tables now uses less temporary disk space when sorting char columns}. @item @code{DATE}/@code{DATETIME} checking is now a bit stricter then before to be able to automatically distinguish between date, datetime, and time with microseconds. For example, dates of type @code{YYYYMMDD HHMMDD} are not supported anymore; One must either have separators between each @code{DATE}/@code{TIME} part or not at all. @item Server side help for all MySQL functions. One can now type @code{help week} in the @code{mysql} client and get help for the @code{week()} function. @item Added new client function: @code{mysql_get_server_version()}. @item Fixed bug in libmysqlclient that fetched field defaults @item Fixed bug in @file{mysql.cc} client when skipping comments @item Added @code{record_in_range()} method to @code{MERGE} tables to be able to choose the right index when there are many to choose from. @item Replication now works with @code{RAND()} and user variables @code{@@var}. @item Allow on to change mode for @code{ANSI_QUOTES} on the fly. @item @code{EXPLAIN SELECT} now can be killed. @xref{KILL}. @item @code{REPAIR TABLE} now can be killed. @xref{KILL}. @item Allow one to specify empty key lists for @code{USE|IGNORE|FORCE INDEX}. @item @code{DROP TEMPORARY TABLE} now only drops temporary tables and doesn't end transactions. @item Added a support for @code{UNION} in derived tables @item @code{TIMESTAMP} is now returned as string of type @code{'YYYY-MM-DD HH:MM:DD'}. @item New faster client/server protocol which supports prepared statements, bound parameters, and bound result columns, binary transfer of data, warnings. @item Added database and real table name (in case of alias) to the MYSQL_FIELD structure. @item Multi-line queries: You can now issue several queries at once and then read the results in one go. @item In @code{CREATE TABLE foo (a int not null primary key)} the @code{PRIMARY} word is now optional. @item In @code{CREATE TABLE} the attribute @code{SERIAL} is now an alias for @code{BIGINT NOT NULL AUTO_INCREMENT UNIQUE}. @item @code{SELECT ... FROM DUAL} is an alias for @code{SELECT ...}. (To be compatible with some other databases). @item If one creates a too long @code{CHAR}/@code{VARCHAR} it's now automatically changed to @code{TEXT} or @code{BLOB}; One will get a warning in this case. @item One can specify the different @code{BLOB}/@code{TEXT} types with the syntax @code{BLOB(length)} and @code{TEXT(length)}. MySQL will automatically change it to one of the internal @code{BLOB}/@code{TEXT} types. @item @code{CHAR BYTE} is an alias for @code{CHAR BINARY}. @item @code{VARCHARACTER} is an alias for @code{VARCHAR}. @item New operators @code{integer MOD integer} and @code{integer DIV integer}. @item @code{SERIAL DEFAULT VALUE} added as an alias for @code{AUTO_INCREMENT}. @item @code{TRUE} and @code{FALSE} added as alias for 1 and 0, respectively. @item Aliases are now forced in derived tables, as per SQL-99. @item Fixed @code{SELECT .. LIMIT 0} to return proper row count for @code{SQL_CALC_FOUND_ROWS}. @item One can specify many temporary directories to be used in a round-robin fashion with: @code{--tmpdir=dirname1:dirname2:dirname3}. @item Subqueries: @code{SELECT * from t1 where t1.a=(SELECT t2.b FROM t2)}. @item Derived tables: @example SELECT a.col1, b.col2 FROM (SELECT MAX(col1) AS col1 FROM root_table) a, other_table b WHERE a.col1=b.col1; @end example @item Character sets to be defined per column, table and database. @item Unicode (UTF8) support. @item @code{BTREE} index on @code{HEAP} tables. @item Faster embedded server (new internal communication protocol). @item One can add a comment per column in @code{CREATE TABLE}. @item @code{SHOW FULL COLUMNS FROM table_name} shows column comments. @item @code{ALTER DATABASE}. @item Support for GIS (Geometrical data). @item @code{SHOW [COUNT(*)] WARNINGS} shows warnings from the last command. @item One can specify a column type for a colum in @code{CREATE TABLE ... SELECT} by defining the column in the @code{CREATE} part. @example CREATE TABLE foo (a tinyint not null) SELECT b+1 AS 'a' FROM bar; @end example @item @code{expr SOUNDS LIKE expr} same as @code{SOUNDEX(expr)=SOUNDEX(expr)}. @item @code{VARIANCE(expr)} returns the variance of @code{expr} @item One can create a table from the existing table using @code{CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table (LIKE table)}. The table can be either normal or temporary. @item New options @code{--reconnect} and @code{disable-reconnect} for the @code{mysql} client, to reconnect automatically or not if the connection is lost. @end itemize @node News-4.0.x, News-3.23.x, News-4.1.x, News @appendixsec Changes in release 4.0.x (Gamma) @cindex changes, version 4.0 Version 4.0 of the MySQL server includes many enhancements and new features: @itemize @bullet @item The @code{InnoDB} table type is now included in the standard binaries, adding transactions, row-level locking, and foreign keys. @xref{InnoDB}. @item A query cache, offering vastly increased performance for many applications. By caching complete result sets, later identical queries can return instantly. @xref{Query Cache}. @item Improved full-text indexing with boolean mode, truncation, and phrase searching. @xref{Fulltext Search}. @item Enhanced @code{MERGE} tables, now supporting @code{INSERT}s and @code{AUTO_INCREMENT}. @xref{MERGE}. @item @code{UNION} syntax in @code{SELECT}. @xref{UNION}. @item Multi-table @code{DELETE} statements. @xref{DELETE}. @item @code{libmysqld}, the embedded server library. @xref{libmysqld}. @item Additional @code{GRANT} privilege options for even tighter control and security. @xref{GRANT}. @item Management of user resources in the @code{GRANT} system, particularly useful for ISPs and other hosting providers. @xref{User resources}. @item Dynamic server variables, allowing configuration changes without having to take down the server. @xref{SET OPTION}. @item Improved replication code and features. @xref{Replication}. @item Numerous new functions and options. @item Changes to existing code for enhanced performance and reliability. @end itemize For a full list of changes, please refer to the changelog sections for each individual 4.0.x release. @menu * News-4.0.12:: Changes in release 4.0.12 (not released yet) * News-4.0.11:: Changes in release 4.0.11 (20 Feb 2003) * News-4.0.10:: Changes in release 4.0.10 (29 Jan 2003) * News-4.0.9:: Changes in release 4.0.9 (09 Jan 2003) * News-4.0.8:: Changes in release 4.0.8 (07 Jan 2003) * News-4.0.7:: Changes in release 4.0.7 (20 Dec 2002) * News-4.0.6:: Changes in release 4.0.6 (14 Dec 2002: Gamma) * News-4.0.5:: Changes in release 4.0.5 (13 Nov 2002) * News-4.0.4:: Changes in release 4.0.4 (29 Sep 2002) * News-4.0.3:: Changes in release 4.0.3 (26 Aug 2002: Beta) * News-4.0.2:: Changes in release 4.0.2 (01 Jul 2002) * News-4.0.1:: Changes in release 4.0.1 (23 Dec 2001) * News-4.0.0:: Changes in release 4.0.0 (Oct 2001: Alpha) @end menu @node News-4.0.12, News-4.0.11, News-4.0.x, News-4.0.x @appendixsubsec Changes in release 4.0.12 (not released yet) Functionality added or changed: @itemize @item @file{mysqld} no longer reads options from world-writeable config files. @item Integer values between 9223372036854775807 and 9999999999999999999 are now regarded as unsigned longlongs, not as floats. This makes these values work similar to values between 10000000000000000000 and 18446744073709551615. @item @code{SHOW PROCESSLIST} will now include the client TCP port after the hostname to make it easier to know from which client the request originated. @end itemize Bugs fixed: @itemize @item Fixed @file{mysqld} crash on extremely small values of @code{sort_buffer} variable. @item @code{INSERT INTO u SELECT ... FROM t} was written too late to the binary log if t was very frequently updated during the execution of this query. This could cause a problem with @code{mysqlbinlog} or replication. The master must be upgraded, not the slave. (bug #136). @item Fixed checking of random part of @code{WHERE} clause (bug #142). @item Fixed a bug with @code{multi-table updates} with @code{InnoDB} tables. This bug occured as, in many cases, @code{InnoDB} tables can not be updated "on the fly", but offsets to the records have to be stored in a temporary table. @item Added missing file @file{mysql_secure_installation} to the @code{server} RPM subpackage (bug #141). @item Fixed MySQL (and @file{myisamchk}) crash on artificially corrupted @code{.MYI} files. @item Don't allow @code{BACKUP TABLE} to overwrite existing files. @item Fixed a bug with multi-table @code{UPDATE}s when user had all privileges on the database where tables are located and there were any entries in @code{tables_priv} table, i.e. @code{grant_option} was true. @item Fixed a bug that allowed a user with table or column grants on some table, @code{TRUNCATE} any table in the same database. @item Fixed deadlock when doing @code{LOCK TABLE} followed by @code{DROP TABLE} in the same thread. In this case one could still kill the thread with @code{KILL}. @item @code{LOAD DATA LOCAL INFILE} was not properly written to the binary log (hence not properly replicated). (bug #82). @item @code{RAND()} entries were not read correctly by @code{mysqlbinlog} from the binary log which caused problems when restoring a table that was inserted with @code{RAND()}. @code{INSERT INTO t1 VALUES(RAND())}. In replication this worked ok. @item @code{SET SQL_LOG_BIN=0} was ignored for @code{INSERT DELAYED} queries. (bug #104). @item @code{SHOW SLAVE STATUS} reported too old positions (columns @code{Relay_Master_Log_File} and @code{Exec_master_log_pos}) for the last executed statement from the master, if this statement was the @code{COMMIT} of a transaction. The master must be upgraded for that, not the slave. (bug #52). @item @code{LOAD DATA INFILE} was not replicated by the slave if @code{replicate_*_table} was set on the slave. (bug #86). @item After @code{RESET SLAVE}, the coordinates displayed by @code{SHOW SLAVE STATUS} looked un-reset (though they were, but only internally). (bug #70). @item Fixed query cache invalidation on @code{LOAD DATA}. @item Fixed memory leak on @code{ANALYZE} procedure with error. @item Fixed a bug in handling @code{CHAR(0)} columns that could cause wrong results from the query. @item Fixed rare bug with wrong initialization of @code{AUTO_INCREMENT} column, as a secondary column in a multi-column key (@pxref{example-AUTO_INCREMENT, , @code{AUTO_INCREMENT} on secondary column in a multi-column key}), when data was inserted with @code{INSERT ... SELECT} or @code{LOAD DATA} into an empty table. @item On windows, @code{STOP SLAVE} didn't stop the slave until the slave got one new command from the master (this bug has been fixed for MySQL 4.0.11 by releasing updated 4.0.11a windows packages, which include this individual fix on top of the 4.0.11 sources). (bug #69). @item Fixed a crash when no database was selected and @code{LOAD DATA} command was issued with full table name specified, including database prefix. @item Fixed a crash when shutting down replication on some platforms (e.g. Mac OS X). @item Fixed a portability bug with @code{pthread_attr_getstacksize} on HP-UX 10.20 (Patch was also included in 4.0.11a sources). @item Fixed the @code{bigint} test to not fail on some platforms (e.g. HP-UX and Tru64) due to different return values of the @code{atof()} function. @item Fixed the @code{rpl_rotate_logs} test to not fail on certain platforms (e.g. Mac OS X) due to a too long file name (changed @code{slave-master-info.opt} to @code{.slave-mi}). @end itemize @node News-4.0.11, News-4.0.10, News-4.0.12, News-4.0.x @appendixsubsec Changes in release 4.0.11 (20 Feb 2003) Functionality added or changed: @itemize @item @code{NULL} is now sorted @strong{LAST} if you use @code{ORDER BY ... DESC} (as it was before before MySQL 4.0.2). This is change was required to follow ANSI SQL 99. (The original change was because we thought that ANSI SQL 99 required NULL to be always sorted at the same position, but this was wrong). @item Added @code{START TRANSACTION} (ANSI SQL-99 syntax) as alias for @code{BEGIN}. This is recommended to use instead of @code{BEGIN} to start a transaction. @item Added @code{OLD_PASSWORD()} as a synonym for @code{PASSWORD()}. @item Allow keyword @code{ALL} in group functions. @item Added support for some new @code{INNER JOIN} and @code{JOIN} syntaxes. For example, @code{SELECT * FROM t1 INNER JOIN t2} didn't work before. @end itemize Bugs fixed: @itemize @item Fixed problem with @code{multi-table-delete} and InnoDB tables. @item Fixed a problem with @code{BLOB NOT NULL} columns used with @code{IS NULL}. @item Re-added missing pre- and post(un)install scripts to the Linux RPM packages (they were missing after the renaming of the server subpackage). @item Fixed that table locks are not released with multi-table updates and deletes with InnoDB storage engine. @item Fixed bug in updating BLOB columns with long strings. @item Fixed integer-wraparound when giving big integer (>= 10 digits) to function that requires an unsigned argument, like @code{CREATE TABLE (...) AUTO_INCREMENT=#}. @item @code{MIN(key_column)} could in some cases return @code{NULL} on a column with @code{NULL} and other values. @item @code{MIN(key_column)} and @code{MAX(key_column)} could in some cases return wrong values when used in @code{OUTER JOIN}. @item @code{MIN(key_column)} and @code{MAX(key_column)} could return wrong values if one of the tables was empty. @item Fixed rare crash in compressed MyISAM tables with blobs. @item Fixed bug in using aggregate functions as argument for @code{INTERVAL}, @code{CASE}, @code{FIELD}, @code{CONCAT_WS}, @code{ELT} and @code{MAKE_SET} functions. @item When running with @code{--lower-case-table-names} (default on windows) and you had tables or databases with mixed case on disk, then executing @code{SHOW TABLE STATUS} followed with @code{DROP DATABASE} or @code{DROP TABLE} could fail with @code{Errcode 13}. @end itemize @node News-4.0.10, News-4.0.9, News-4.0.11, News-4.0.x @appendixsubsec Changes in release 4.0.10 (29 Jan 2003) Functionality added or changed: @itemize @item Added option @code{--log-error[=file_name]} to @code{mysqld_safe} and @code{mysqld}. This option will force all error messages to be put in a log file if the option @code{--console} is not given. On Windows @code{--log-error} is enabled as default. @item Changed some things from @code{Warning:} to @code{Note:} in the log files. @item The mysqld server should now compile on Netware. @item Added optimisation that if one does @code{GROUP BY ... ORDER BY NULL} then result is not sorted. @item New command-line option for @file{mysqld} to replace/disable built-in stopword list, that is used in fulltext search. @xref{SHOW VARIABLES, , @code{ft_stopword_file}}. @item Changed default stack size from 64K to 192K; This fixes a core dump problem on RedHat 8.0 and other systems with a glibc that requires > 128K stack for @code{gethostbyaddr()} to resolve a hostname. You can fix this for earlier MySQL versions by starting mysqld with @code{--thread-stack=192K}. @item Added @code{mysql_waitpid} to the binary distribution and the @code{MySQL-client} RPM subpackage (required for @code{mysql-test-run}). @item Renamed the main @code{MySQL} RPM package to @code{MySQL-server}. When updating from an older version, @code{MySQL-server.rpm} will simply replace @code{MySQL.rpm}. @item If a slave is configured with @code{replicate_wild_do_table=db.%} or @code{replicate_wild_ignore_table=db.%}, these rules will be applied to @code{CREATE/DROP DATABASE} too. @item Added timeout value for @code{MASTER_POS_WAIT()}. @end itemize Bugs fixed: @itemize @item Fixed initialization of the random seed for newly created threads to give a better @code{rand()} distribution from the first call. @item Fixed a bug that caused @code{mysqld} to hang when a table was opened with the @code{HANDLER} command and then dropped without being closed. @item Fixed bug in logging to binary log (which affects replication) a query that inserts a @code{NULL} in an @code{auto_increment} field and also uses @code{LAST_INSERT_ID()}. @item Fixed an unlikely bug that could cause a memory overrun when using @code{ORDER BY constant_expression}. @item Fixed a table corruption in @file{myisamchk}'s parallel repair mode. @item Fixed bug in query cache invalidation on simple table renaming. @item Fixed bug in @code{mysqladmin --relative}. @item On some 64 bit systems, @code{show status} reported a strange number for @code{Open_files} and @code{Open_streams}. @item Fixed wrong number of columns in @code{EXPLAIN} on empty table. @item Fixed bug in @code{LEFT JOIN} that caused zero rows to be returned in the case the @code{WHERE} condition was evaluated as @code{FALSE} after reading const tables. (Unlikely condition). @item @code{FLUSH PRIVILEGES} didn't correctly flush table/column privileges when @code{mysql.tables_priv} is empty. @item Fixed bug in replication when using @code{LOAD DATA INFILE} one a file that updated and auto_increment field with @code{NULL} or @code{0}. This bug only affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters). @strong{NOTE}: If you have a slave that has replicated a file with generated auto_increment fields then the slave data is corrupted and you should reinitialise the affected tables from the master. @item Fixed possible memory overrun when sending a blob > 16M to the client. @item Fixed wrong error message when setting a @code{NOT NULL} field to an expression that returned @code{NULL}. @item Fixed core dump bug in @code{str LIKE "%other_str%"} where @code{str} or @code{other_str} contained characters >= 128. @item Fixed bug: When executing on master @code{LOAD DATA} and InnoDB failed with @code{table full} error the binary log was corrupted. @end itemize @node News-4.0.9, News-4.0.8, News-4.0.10, News-4.0.x @appendixsubsec Changes in release 4.0.9 (09 Jan 2003) Functionality added or changed: @itemize @item @code{OPTIMIZE TABLE} will for MyISAM tables treat all @code{NULL} values as different when calculating cardinality. This helps in optimising joins between tables where one of the tables has a lot of @code{NULL} values in a indexed column: @example SELECT * from t1,t2 where t1.a=t2.key_with_a_lot_of_null; @end example @item Added join operator @code{FORCE INDEX (key_list)}. This acts likes @code{USE INDEX (key_list)} but with the addition that a table scan is assumed to be VERY expensive. One bad thing with this is that it makes @code{FORCE} a reserved word. @item Reset internal row buffer in MyISAM after each query. This will reduce memory in the case you have a lot of big blobs in a table. @end itemize Bugs fixed: @itemize @item A security patch in 4.0.8 causes the mysqld server to die if the remote hostname can't be resolved. This is now fixed. @item Fixed crash when replication big @code{LOAD DATA INFILE} statement that caused log rotation. @end itemize @node News-4.0.8, News-4.0.7, News-4.0.9, News-4.0.x @appendixsubsec Changes in release 4.0.8 (2003-01-07) Functionality added or changed: @itemize @item Default @code{max_packet_length} for libmysqld.c is now 1024*1024*1024. @item One can now specify @code{max_allowed_packet} in a file ready by @code{mysql_options(MYSQL_READ_DEFAULT_FILE)}. for clients. @item When sending a too big packet to the server with the not compressed protocol, the client now gets an error message instead of a lost connection. @item We now send big queries/result rows in bigger hunks, which should give a small speed improvement. @item Fixed some bugs with the compressed protocol for rows > 16M. @item InnoDB tables now also supports @code{ON UPDATE CASCADE} in @code{FOREIGN KEY} constraints. See the InnoDB section in the manual for the InnoDB changelog. @end itemize Bugs fixed: @itemize @item Fixed bug in @code{ALTER TABLE} with BDB tables. @item Fixed core dump bug in @code{QUOTE()} function. @item Fixed a bug in handling communication packets bigger than 16M. Unfortunately this required a protocol change; If you upgrade the server to 4.0.8 and above and have clients that uses packets >= 255*255*255 bytes (=16581375) you must also upgrade your clients to at least 4.0.8. If you don't upgrade, the clients will hang when sending a big packet. @item Fixed bug when sending blobs longer than 16M to client. @item Fixed bug in @code{GROUP BY} when used on BLOB column with @code{NULL} values. @item Fixed a bug in handling @code{NULL}s in @code{CASE} ... WHEN ... @end itemize @node News-4.0.7, News-4.0.6, News-4.0.8, News-4.0.x @appendixsubsec Changes in release 4.0.7 (2002-12-20) Functionality added or changed: @itemize @item @code{mysqlbug} now also reports the compiler version used for building the binaries (if the compiler supports the option @code{--version}). @end itemize Bugs fixed: @itemize @item Fixed compilation problems on OpenUnix and HPUX 10.20. @item Fixed some optimisation problems when compiling MySQL with @code{-DBIG_TABLES} on a 32 bit system. @item @code{mysql_drop_db()} didn't check permissions properly so anyone could drop another users database. @code{DROP DATABASE} is checked properly. @end itemize @node News-4.0.6, News-4.0.5, News-4.0.7, News-4.0.x @appendixsubsec Changes in release 4.0.6 (2002-12-14: Gamma) Functionality added or changed: @itemize @item Added syntax support for @code{CHARACTER SET xxx} and @code{CHARSET=xxx} table options (to be able to read table dumps from 4.1). @item Fixed replication bug that caused the slave to loose its position in some cases when the replication log was rotated. @item Fixed that a slave will restart from the start of a transaction if it's killed in the middle of one. @item Moved the manual pages from @file{man} to @file{man/man1} in the binary distributions. @item The default type returned by @code{IFNULL(A,B)} is now set to be the more 'general' of the types of @code{A} and @code{B}. (The order is @code{STRING}, @code{REAL} or @code{INTEGER}). @item Moved the @file{mysql.server} startup script in the RPM packages from @file{/etc/rc.d/init.d/mysql} to @file{/etc/init.d/mysql} (which almost all current Linux distributions support for LSB compliance). @item Added @code{Qcache_lowmem_prunes} status variable (number of queries that were deleted from cache because of low memory). @item Fixed @code{mysqlcheck} so it can deal with table names containing dashes. @item Bulk insert optimisation (@pxref{SHOW VARIABLES, ,@code{bulk_insert_buffer_size}}) is no longer used when inserting small (less than 100) number of rows. @item Optimisation added for queries like @code{SELECT ... FROM merge_table WHERE indexed_column=constant_expr}. @item Added functions @code{LOCALTIME} and @code{LOCALTIMESTAMP} as synonyms for @code{NOW()}. @item @code{CEIL} is now an alias for @code{CEILING}. @item The @code{CURRENT_USER()} function can be used to get a @code{user@@host} value as it was matched in the @code{GRANT} system. @xref{Miscellaneous functions, ,@code{CURRENT_USER()}}. @item Fixed @code{CHECK} constraints to be compatible with ANSI SQL. This made @code{CHECK} a reserved word. (Checking of @code{CHECK} constraints is still not implemented). @item Added @code{CAST(... as CHAR)}. @item Added PostgreSQL compatible @code{LIMIT} syntax: @code{SELECT ... LIMIT # OFFSET #} @item @code{mysql_change_user()} will now reset the connection to the state of a fresh connect (Ie, @code{ROLLBACK} any active transaction, close all temporary tables, reset all user variables etc..) @end itemize Bugs fixed: @itemize @item Fixed number of found rows returned in @code{multi table updates} @item Make @code{--lower-case-table-names} default on Mac OS X as the file system is case sensitive. @item Transactions in @code{AUTOCOMMIT=0} mode didn't rotate binary log. @item A fix for the bug in a @code{SELECT} with joined tables with @code{ORDER BY} and @code{LIMIT} clause when filesort had to be used. In that case @code{LIMIT} was applied to filesort of one of the tables, although it could not be. This fix solved problems with @code{LEFT JOIN} too. @item @code{mysql_server_init()} now makes a copy of all arguments. This fixes a problem when using the embedded server in C# program. @item Fixed buffer overrun in @code{libmysqlclient} library that allowed a malicious @code{MySQL} server to crash the client application. @item Fixed security-related bug in @code{mysql_change_user()} handling. All users are strongly recommended to upgrade to version 4.0.6. @item Fixed bug that prevented @code{--chroot} command-line option of @code{mysqld} from working. @item Fixed bug in phrase operator @code{"..."} in boolean full-text search. @item Fixed bug that caused @code{OPTIMIZE TABLE} to corrupt the table under some rare circumstances. @item Part rewrite of multi-table-update to optimise it, make it safer and more bug free. @item @code{LOCK TABLES} now works together with multi-table-update and multi-table-delete. @item @code{--replicate-do=xxx} didn't work for @code{UPDATE} commands. (Bug introduced in 4.0.0) @item Fixed shutdown problem on Mac OS X. @item Major InnoDB bugs in @code{REPLACE, AUTO_INCREMENT, INSERT INTO ... SELECT ...} were fixed. See the InnoDB changelog in the InnoDB section of the manual. @end itemize @node News-4.0.5, News-4.0.4, News-4.0.6, News-4.0.x @appendixsubsec Changes in release 4.0.5 (2002-11-13) Functionality added or changed: @itemize @item Port number was added to host name (if it is known) in @code{SHOW PROCESSLIST} command @item Changed handling of last argument in @code{WEEK()} so that one can get week number according to the ISO 8601 specification. (Old code should still work). @item Fixed that @code{INSERT DELAYED} threads doesn't hang on @code{Waiting for INSERT} when one sends a @code{SIGHUP} to mysqld. @item Change that @code{AND} works according to SQL ANSI99 when it comes to @code{NULL} handling. In practice, this only affects queries where you do something like @code{WHERE ... NOT (NULL AND 0)}. @item @code{mysqld} will now resolve @code{basedir} to its full path (with @code{realpath()}). This enables one to use relative symlinks to the MySQL installation directory. This will however cause @code{show variables} to report different directories on systems where there is a symbolic link in the path. @item Fixed that MySQL will not use index scan on index disabled with @code{IGNORE INDEX} or @code{USE INDEX}. to be ignored. @item Added @code{--use-frm} option to @code{mysqlcheck}. When used with @code{REPAIR}, it gets the table structure from the @code{.frm} file, so the table can be repaired even if the @code{.MYI} header is corrupted. @item Fixed bug in @code{MAX()} optimisation when used with @code{JOIN} and @code{ON} expressions. @item Added support for reading of MySQL 4.1 table definition files. @item @code{BETWEEN} behaviour changed (@pxref{Comparison Operators}). Now @code{datetime_col BETWEEN timestamp AND timestamp} should work as expected. @item One can create @code{TEMPORARY} @code{MERGE} tables now. @item @code{DELETE FROM myisam_table} now shrinks not only the @file{.MYD} file but also the @file{.MYI} file. @item When one uses the @code{--open-files-limit=#} option to @code{mysqld_safe} it's now passed on to @code{mysqld}. @item Changed output from @code{EXPLAIN} from @code{'where used'} to @code{'Using where'} to make it more in line with other output. @item Removed variable @code{safe_show_database} as it was not used anymore. @item Updated source tree to be built using @code{automake 1.5} and @code{libtool 1.4}. @item Fixed an inadvertently changed option (@code{--ignore-space}) back to the original @code{--ignore-spaces} in @code{mysqlclient}. (Both syntaxes will work). @item Don't require @code{UPDATE} privilege when using @code{REPLACE}. @item Added support for @code{DROP TEMPORARY TABLE ...}, to be used to make replication safer. @item When transactions are enabled, all commands that update temporary tables inside a @code{BEGIN/COMMIT} are now stored in the binary log on @code{COMMIT} and not stored if one does @code{ROLLBACK}. This fixes some problems with non-transactional temporary tables used inside transactions. @item Allow braces in joins in all positions. Formerly, things like @code{SELECT * FROM (t2 LEFT JOIN t3 USING (a)), t1} worked, but not @code{SELECT * FROM t1, (t2 LEFT JOIN t3 USING (a))}. Note that braces are simply removed, they do not change the way the join is executed. @item InnoDB now supports also isolation levels @code{READ UNCOMMITTED} and @code{READ COMMITTED}. For a detailed InnoDB changelog, @pxref{InnoDB change history} in this manual. @end itemize Bugs fixed: @itemize @item Fixed bug in @code{MAX()} optimisation when used with @code{JOIN} and @code{ON} expressions. @item Fixed that @code{INSERT DELAY} threads don't hang on @code{Waiting for INSERT} when one sends a @code{SIGHUP} to @code{mysqld}. @item Fixed that MySQL will not use an index scan on an index that has been disabled with @code{IGNORE INDEX} or @code{USE INDEX}. @item Corrected test for @code{root} user in @code{mysqld_safe}. @item Fixed error message issued when storage engine cannot do @code{CHECK} or @code{REPAIR}. @item Fixed rare core dump problem in complicated @code{GROUP BY} queries that didn't return any result. @item Fixed @code{mysqlshow} to work properly with wildcarded database names and with database names that contain underscores. @item Portability fixes to get MySQL to compile cleanly with Sun Forte 5.0. @item Fixed @code{MyISAM} crash when using dynamic-row tables with huge numbers of packed fields. @item Fixed query cache behaviour with @code{BDB} transactions. @item Fixed possible floating point exception in @code{MATCH} relevance calculations. @item Fixed bug in full-text search @code{IN BOOLEAN MODE} that made @code{MATCH} to return incorrect relevance value in some complex joins. @item Fixed a bug that limited @code{MyISAM} key length to a value slightly less that 500. It is exactly 500 now. @item Fixed that @code{GROUP BY} on columns that may have a @code{NULL} value doesn't always use disk based temporary tables. @item The filename argument for the @code{--des-key-file} argument to @code{mysqld} is interpreted relative to the data directory if given as a relative pathname. @item Removed a condition that temp table with index on column that can be @code{NULL} has to be @code{MyISAM}. This was okay for 3.23, but not needed in 4.*. This resulted in slowdown in many queries since 4.0.2. @item Small code improvement in multi-table updates. @item Fixed a newly introduced bug that caused @code{ORDER BY ... LIMIT #} to not return all rows. @item Fixed a bug in multi-table deletes when outer join is used on an empty table, which gets first to be deleted. @item Fixed a bug in multi-table updates when a single table is updated. @item Fixed bug that caused @code{REPAIR TABLE} and @code{myisamchk} to corrupt @code{FULLTEXT} indexes. @item Fixed bug with caching the @code{mysql} grant table database. Now queries in this database are not cached in the query cache. @item Small fix in @code{mysqld_safe} for some shells. @item Give error if a @code{MyISAM} @code{MERGE} table has more than 2 ^ 32 rows and MySQL was not compiled with @code{-DBIG_TABLES}. @item Fixed some @code{ORDER BY ... DESC} problems with @code{InnoDB} tables. @end itemize @node News-4.0.4, News-4.0.3, News-4.0.5, News-4.0.x @appendixsubsec Changes in release 4.0.4 (2002-09-29) @itemize @bullet @item Fixed bug where @code{GRANT}/@code{REVOKE} failed if hostname was given in non-matching case. @item Don't give warning in @code{LOAD DATA INFILE} when setting a @code{timestamp} to a string value of @code{'0'}. @item Fixed bug in @code{myisamchk -R} mode. @item Fixed bug that caused @code{mysqld} to crash on @code{REVOKE}. @item Fixed bug in @code{ORDER BY} when there is a constant in the @code{SELECT} statement. @item One didn't get an error message if @code{mysqld} couldn't open the privilege tables. @item @code{SET PASSWORD FOR ...} closed the connection in case of errors (bug from 4.0.3). @item Increased max possible @code{max_allowed_packet} in @code{mysqld} to 1GB. @item Fixed bug when doing a multi-line @code{INSERT} on a table with an @code{AUTO_INCREMENT} key which was not in the first part of the key. @item Changed @code{LOAD DATA INFILE} to not recreate index if the table had rows from before. @item Fixed overrun bug when calling @code{AES_DECRYPT()} with incorrect arguments. @item @code{--skip-ssl} can now be used to disable SSL in the MySQL clients, even if one is using other SSL options in an option file or previously on the command line. @item Fixed bug in @code{MATCH ... AGAINST( ... IN BOOLEAN MODE)} used with @code{ORDER BY}. @item Added @code{LOCK TABLES} and @code{CREATE TEMPORARY TABLES} privilege on the database level. One must run the @code{mysql_fix_privilege_tables} script on old installations to activate these. @item In @code{SHOW TABLE ... STATUS}, compressed tables sometimes showed up as @code{dynamic}. @item @code{SELECT @@@@[global|session].var_name} didn't report @code{global | session} in the result column name. @item Fixed problem in replication that @code{FLUSH LOGS} in a circular replication setup created an infinite number of binary log files. Now a @code{rotate-binary-log} command in the binary log will not cause slaves to rotate logs. @item Removed @code{STOP EVENT} from binary log when doing @code{FLUSH LOGS}. @item Disable the use of @code{SHOW NEW MASTER FOR SLAVE} as this needs to be completely changed in 4.1. @item Fixed a bug with constant expression (e.g. field of a one-row table, or field from a table, referenced by a @code{UNIQUE} key) appeared in @code{ORDER BY} part of @code{SELECT DISTINCT}. @item @code{--log-binary=a.b.c} now properly strips off @code{.b.c}. @item @code{FLUSH LOGS} removed numerical extension for all future update logs. @item @code{GRANT ... REQUIRE} didn't store the SSL information in the @code{mysql.user} table if SSL was not enabled in the server. @item @code{GRANT ... REQUIRE NONE} can now be used to remove SSL information. @item @code{AND} is now optional between @code{REQUIRE} options. @item @code{REQUIRE} option was not properly saved, which could cause strange output in @code{SHOW GRANTS}. @item Fixed that @code{mysqld --help} reports correct values for @code{--datadir} and @code{--bind-address}. @item Fixed that one can drop UDFs that didn't exist when @code{mysqld} was started. @item Fixed core dump problem with @code{SHOW VARIABLES} on some 64 bit systems (like Solaris sparc). @item Fixed a bug in my_getopt; @code{--set-variable} syntax didn't work for those options that didn't have a valid variable in my_option struct. This affected at least @code{default-table-type} option. @item Fixed a bug from 4.0.2 that caused @code{REPAIR TABLE} and @code{myisamchk --recover} to fail on tables with duplicates in a unique key. @item Fixed a bug from 4.0.3 in calculating the default field type for some functions. This affected queries of type @code{CREATE TABLE table_name SELECT expression(),...} @item Fixed bug in queries of type @code{SELECT * FROM table-list GROUP BY ...} and @code{SELECT DISTINCT * FROM ...}. @item Fixed bug with the @code{--slow-log} when logging an administrator command (like @code{FLUSH TABLES}). @item Fixed a bug that @code{OPTIMIZE} of locked and modified table, reported table corruption. @item Fixed a bug in my_getopt in handling of special prefixes (@code{--skip-}, @code{--enable-}). @code{--skip-external-locking} didn't work and the bug may have affected other similar options. @item Fixed bug in checking for output file name of the @code{tee} option. @item Added some more optimisation to use index for @code{SELECT ... FROM many_tables .. ORDER BY key limit #} @item Fixed problem in @code{SHOW OPEN TABLES} when a user didn't have access permissions to one of the opened tables. @end itemize @node News-4.0.3, News-4.0.2, News-4.0.4, News-4.0.x @appendixsubsec Changes in release 4.0.3 (2002-08-26: Beta) @itemize @bullet @item Fixed problem with @code{configure ... --localstatedir=...}. @item Cleaned up @code{mysql.server} script. @item Fixed a bug in @code{mysqladmin shutdown} when pid file was modified while @code{mysqladmin} was still waiting for the previous one to disappear. This could happen during a very quick restart and caused @code{mysqladmin} to hang until @code{shutdown_timeout} seconds had passed. @item Don't increment warnings when setting @code{AUTO_INCREMENT} columns to @code{NULL} in @code{LOAD DATA INFILE}. @item Fixed all boolean type variables/options to work with the old syntax, e.g. all of these work: --lower-case-table-names, --lower-case-table-names=1, -O lower-case-table-names=1, --set-variable=lower-case-table-names=1 @item Fixed shutdown problem (SIGTERM signal handling) on Solaris. (Bug from 4.0.2). @item @code{SHOW MASTER STATUS} now returns an empty set if binary log is not enabled. @item @code{SHOW SLAVE STATUS} now returns an empty set if slave is not initialised. @item Don't update MyISAM index file on update if not strictly necessary. @item Fixed bug in @code{SELECT DISTINCT ... FROM many_tables ORDER BY not-used-column}. @item Fixed a bug with @code{BIGINT}s and quoted strings. @item Added @code{QUOTE()} function that performs SQL quoting to produce values that can be used as data values in queries. @item Changed variable @code{DELAY_KEY_WRITE} to an enum to allow one set @code{DELAY_KEY_WRITE} for all tables without taking down the server. @item Changed behaviour of @code{IF(condition,column,NULL)} so that it returns the value of the column type. @item Made @code{safe_mysqld} a symlink to @code{mysqld_safe} in binary distribution. @item Fixed security bug when having an empty database name in the @code{user.db} table. @item Fixed some problems with @code{CREATE TABLE ... SELECT function()}. @item @code{mysqld} now has the option @code{--temp-pool} enabled by default as this gives better performance with some operating systems. @item Fixed hang in @code{CHANGE MASTER TO} if the slave thread died very quickly. @item Big cleanup in replication code (less logging, better error messages, etc..) @item If the @code{--code-file} option is specified, the server calls @code{setrlimit()} to set the maximum allowed core file size to unlimited, so core files can be generated. @item Fixed bug in query cache after temporary table creation. @item Added @code{--count=N} (@code{-c}) option to @code{mysqladmin}, to make the program do only @code{N} iterations. To be used with @code{--sleep} (@code{-i}). Useful in scripts. @item Fixed bug in multi-table @code{UPDATE}: when updating a table, @code{do_select()} became confused about reading records from a cache. @item Fixed bug in multi-table @code{UPDATE} when several fields were referenced from a single table @item Fixed bug in truncating nonexisting table. @item Fixed bug in @code{REVOKE} that caused user resources to be randomly set. @item Fixed bug in @code{GRANT} for the new @code{CREATE TEMPORARY TABLE} privilege. @item Fixed bug in multi-table @code{DELETE} when tables are re-ordered in the table initialisation method and ref_lengths are of different sizes. @item Fixed two bugs in @code{SELECT DISTINCT} with large tables. @item Fixed bug in query cache initialisation with very small query cache size. @item Allow @code{DEFAULT} with @code{INSERT} statement. @item The startup parameters @code{myisam_max_sort_file_size} and @code{myisam_max_extra_sort_file_size} are now given in bytes, not megabytes. @item External system locking of @code{MyISAM}/@code{ISAM} files is now turned off by default. One can turn this on with @code{--external-locking}. (For most users this is never needed). @item Fixed core dump bug with @code{INSERT ... SET db_name.table_name.colname=''}. @item Fixed client hangup bug when using some SQL commands with wrong syntax. @item Fixed a timing bug in @code{DROP DATABASE} @item New @code{SET [GLOBAL | SESSION]} syntax to change thread-specific and global server variables at runtime. @item Added variable @code{slave_compressed_protocol}. @item Renamed variable @code{query_cache_startup_type} to @code{query_cache_type}, @code{myisam_bulk_insert_tree_size} to @code{bulk_insert_buffer_size}, @code{record_buffer} to @code{read_buffer_size} and @code{record_rnd_buffer} to @code{record_rnd_buffer_size}. @item Renamed some SQL variables, but old names will still work until 5.0. @xref{Upgrading-from-3.23}. @item Renamed @code{--skip-locking} to @code{--skip-external-locking}. @item Removed unused variable @code{query_buffer_size}. @item Fixed a bug that made the pager option in the @code{mysql} client non-functional. @item Added full @code{AUTO_INCREMENT} support to @code{MERGE} tables. @item Extended @code{LOG()} function to accept an optional arbitrary base parameter. @xref{Mathematical functions}. @item Added @code{LOG2()} function (useful for finding out how many bits a number would require for storage). @item Added @code{LN()} natural logarithm function for compatibility with other databases. It is synonymous with @code{LOG(X)}. @end itemize @node News-4.0.2, News-4.0.1, News-4.0.3, News-4.0.x @appendixsubsec Changes in release 4.0.2 (2002-07-01) @itemize @bullet @item Cleaned up @code{NULL} handling for default values in @code{DESCRIBE table_name}. @item Fixed @code{truncate()} to round up negative values to the nearest integer. @item Changed @code{--chroot=path} option to execute @code{chroot()} immediately after all options have been parsed. @item Don't allow database names that contain @samp{\}. @item @code{lower_case_table_names} now also affects database names. @item Added @code{XOR} operator (logical and bitwise @code{XOR}) with @code{^} as a synonym for bitwise @code{XOR}. @item Added function @code{IS_FREE_LOCK("lock_name")}. Based on code contributed by Hartmut Holzgraefe @email{hartmut@@six.de}. @item Removed @code{mysql_ssl_clear()} from C API, as it was not needed. @item @code{DECIMAL} and @code{NUMERIC} types can now read exponential numbers. @item Added @code{SHA1()} function to calculate 160 bit hash value as described in RFC 3174 (Secure Hash Algorithm). This function can be considered a cryptographically more secure equivalent of @code{MD5()}. @xref{Miscellaneous functions}. @item Added @code{AES_ENCRYPT()} and @code{AES_DECRYPT()} functions to perform encryption according to AES standard (Rijndael). @xref{Miscellaneous functions}. @item Added @code{--single-transaction} option to @code{mysqldump}, allowing a consistent dump of @code{InnoDB} tables. @xref{mysqldump}. @item Fixed bug in @code{innodb_log_group_home_dir} in @code{SHOW VARIABLES}. @item Fixed a bug in optimiser with merge tables when non-unique values are used in summing up (causing crashes). @item Fixed a bug in optimiser when a range specified makes index grouping impossible (causing crashes). @item Fixed a rare bug when @code{FULLTEXT} index is present and no tables are used. @item Added privileges @code{CREATE TEMPORARY TABLES}, @code{EXECUTE}, @code{LOCK TABLES}, @code{REPLICATION CLIENT}, @code{REPLICATION SLAVE}, @code{SHOW DATABASES} and @code{SUPER}. To use these, you must have run the @code{mysql_fix_privilege_tables} script after upgrading. @item Fixed query cache align data bug. @item Fixed mutex bug in replication when reading from master fails. @item Added missing mutex in @code{TRUNCATE TABLE}; This fixes some core dump/hangup problems when using @code{TRUNCATE TABLE}. @item Fixed bug in multi-table @code{DELETE} when optimiser uses only indices. @item Fixed that @code{ALTER TABLE table_name RENAME new_table_name} is as fast as @code{RENAME TABLE}. @item Fixed bug in @code{GROUP BY} with two or more fields, where at least one field can contain @code{NULL} values. @item Use @code{Turbo Boyer-Moore} algorithm to speed up @code{LIKE "%keyword%"} searches. @item Fixed bug in @code{DROP DATABASE} with symlink. @item Fixed crash in @code{REPAIR ... USE_FRM}. @item Fixed bug in @code{EXPLAIN} with @code{LIMIT offset != 0}. @item Fixed bug in phrase operator @code{"..."} in boolean full-text search. @item Fixed bug that caused duplicated rows when using truncation operator @code{*} in boolean full-text search. @item Fixed bug in truncation operator of boolean full-text search (wrong results when there are only @code{+word*}s in the query). @item Fixed bug in boolean full-text search that caused a crash when an identical @code{MATCH} expression that did not use an index appeared twice. @item Query cache is now automatically disabled in @code{mysqldump}. @item Fixed problem on Windows 98 that made sending of results very slow. @item Boolean full-text search weighting scheme changed to something more reasonable. @item Fixed bug in boolean full-text search that caused MySQL to ignore queries of @code{ft_min_word_len} characters. @item Boolean full-text search now supports ``phrase searches''. @item New configure option @code{--without-query-cache}. @item Memory allocation strategy for ``root memory'' changed. Block size now grows with number of allocated blocks. @item @code{INET_NTOA()} now returns @code{NULL} if you give it an argument that is too large (greater than the value corresponding to @code{255.255.255.255}). @item Fix @code{SQL_CALC_FOUND_ROWS} to work with @code{UNION}s. It will work only if the first @code{SELECT} has this option and if there is global @code{LIMIT} for the entire statement. For the moment, this requires using parentheses for individual @code{SELECT} queries within the statement. @item Fixed bug in @code{SQL_CALC_FOUND_ROWS} and @code{LIMIT}. @item Don't give an error for @code{CREATE TABLE ...(... VARCHAR(0))}. @item Fixed @code{SIGINT} and @code{SIGQUIT} problems in @file{mysql.cc} on Linux with some @code{glibc} versions. @item Fixed bug in @file{convert.cc}, which is caused by having an incorrect @code{net_store_length()} linked in the @code{CONVERT::store()} method. @item @code{DOUBLE} and @code{FLOAT} columns now honor the @code{UNSIGNED} flag on storage. @item @code{InnoDB} now retains foreign key constraints through @code{ALTER TABLE} and @code{CREATE/DROP INDEX}. @item @code{InnoDB} now allows foreign key constraints to be added through the @code{ALTER TABLE} syntax. @item @code{InnoDB} tables can now be set to automatically grow in size (autoextend). @item Added @code{--ignore-lines=n} option to @code{mysqlimport}. This has the same effect as the @code{IGNORE n LINES} clause for @code{LOAD DATA}. @item Fixed bug in @code{UNION} with last offset being transposed to total result set. @item @code{REPAIR ... USE_FRM} added. @item Fixed that @code{DEFAULT_SELECT_LIMIT} is always imposed on @code{UNION} result set. @item Fixed that some @code{SELECT} options can appear only in the first @code{SELECT}. @item Fixed bug with @code{LIMIT} with @code{UNION}, where last select is in the braces. @item Fixed that full-text works fine with @code{UNION} operations. @item Fixed bug with indexless boolean full-text search. @item Fixed bug that sometimes appeared when full-text search was used with ``const'' tables. @item Fixed incorrect error value when doing a @code{SELECT} with an empty @code{HEAP} table. @item Use @code{ORDER BY column DESC} now sorts @code{NULL} values first. (In other words, @code{NULL} values sort first in all cases, whether or not @code{DESC} is specified.). This is changed back in 4.0.10. @item Fixed bug in @code{WHERE key_name='constant' ORDER BY key_name DESC}. @item Fixed bug in @code{SELECT DISTINCT ... ORDER BY DESC} optimisation. @item Fixed bug in @code{... HAVING 'GROUP_FUNCTION'(xxx) IS [NOT] NULL}. @item Fixed bug in truncation operator for boolean full-text search. @item Allow value of @code{--user=#} option for @code{mysqld} to be specified as a numeric user ID. @item Fixed a bug where @code{SQL_CALC_ROWS} returned an incorrect value when used with one table and @code{ORDER BY} and with @code{InnoDB} tables. @item Fixed that @code{SELECT 0 LIMIT 0} doesn't hang thread. @item Fixed some problems with @code{USE/IGNORE INDEX} when using many keys with the same start column. @item Don't use table scan with @code{BerkeleyDB} and @code{InnoDB} tables when we can use an index that covers the whole row. @item Optimised @code{InnoDB} sort-buffer handling to take less memory. @item Fixed bug in multi-table @code{DELETE} and @code{InnoDB} tables. @item Fixed problem with @code{TRUNCATE} and @code{InnoDB} tables that produced the error @code{Can't execute the given command because you have active locked tables or an active transaction}. @item Added @code{NO_UNSIGNED_SUBTRACTION} to the set of flags that may be specified with the @code{--sql-mode} option for @code{mysqld}. It disables unsigned arithmetic rules when it comes to subtraction. (This will make MySQL 4.0 behave more closely to 3.23 with @code{UNSIGNED} columns). @item The result returned for all bit functions (@code{|}, @code{<<}, ...) is now of type @code{unsigned integer}. @item Added detection of @code{nan} values in @code{MyISAM} to make it possible to repair tables with @code{nan} in float or double columns. @item Fixed new bug in @code{myisamchk} where it didn't correctly update number of ``parts'' in the @code{MyISAM} index file. @item Changed to use @code{autoconf} 2.52 (from @code{autoconf} 2.13). @item Fixed optimisation problem where the MySQL Server was in ``preparing'' state for a long time when selecting from an empty table which had contained a lot of rows. @item Fixed bug in complicated join with @code{const} tables. This fix also improves performance a bit when referring to another table from a @code{const} table. @item First pre-version of multi-table @code{UPDATE} statement. @item Fixed bug in multi-table @code{DELETE}. @item Fixed bug in @code{SELECT CONCAT(argument_list) ... GROUP BY 1}. @item @code{INSERT ... SELECT} did a full rollback in case of an error. Fixed so that we only roll back the last statement in the current transaction. @item Fixed bug with empty expression for boolean full-text search. @item Fixed core dump bug in updating full-text key from/to @code{NULL}. @item ODBC compatibility: Added @code{BIT_LENGTH()} function. @item Fixed core dump bug in @code{GROUP BY BINARY column}. @item Added support for @code{NULL} keys in @code{HEAP} tables. @item Use index for @code{ORDER BY} in queries of type: @code{SELECT * FROM t WHERE key_part1=1 ORDER BY key_part1 DESC,key_part2 DESC} @item Fixed bug in @code{FLUSH QUERY CACHE}. @item Added @code{CAST()} and @code{CONVERT()} functions. The @code{CAST} and @code{CONVERT} functions are nearly identical and mainly useful when you want to create a column with a specific type in a @code{CREATE ... SELECT} statement. For more information, read @ref{Cast Functions}. @item @code{CREATE ... SELECT} on @code{DATE} and @code{TIME} functions now create columns of the expected type. @item Changed order in which keys are created in tables. @item Added new columns @code{Null} and @code{Index_type} to @code{SHOW INDEX} output. @item Added @code{--no-beep} and @code{--prompt} options to @code{mysql} command-line client. @item New feature: management of user resources. @example GRANT ... WITH MAX_QUERIES_PER_HOUR N1 MAX_UPDATES_PER_HOUR N2 MAX_CONNECTIONS_PER_HOUR N3; @end example @xref{User resources}. @item Added @code{mysql_secure_installation} to the @file{scripts/} directory. @end itemize @node News-4.0.1, News-4.0.0, News-4.0.2, News-4.0.x @appendixsubsec Changes in release 4.0.1 (2001-12-23) @itemize @bullet @item Fixed bug when @code{HANDLER} was used with some unsupported table type. @item @code{mysqldump} now puts @code{ALTER TABLE tbl_name DISABLE KEYS} and @code{ALTER TABLE tbl_name ENABLE KEYS} in the sql dump. @item Added @code{mysql_fix_extensions} script. @item Fixed stack overrun problem with @code{LOAD DATA FROM MASTER} on OSF/1. @item Fixed shutdown problem on HP-UX. @item Added @code{DES_ENCRYPT()} and @code{DES_DECRYPT()} functions. @item Added @code{FLUSH DES_KEY_FILE} statement. @item Added @code{--des-key-file} option to @code{mysqld}. @item @code{HEX(string)} now returns the characters in @code{string} converted to hexadecimal. @item Fixed problem with @code{GRANT} when using @code{lower_case_table_names=1}. @item Changed @code{SELECT ... IN SHARE MODE} to @code{SELECT ... LOCK IN SHARE MODE} (as in MySQL 3.23). @item A new query cache to cache results from identical @code{SELECT} queries. @item Fixed core dump bug on 64-bit machines when it got an incorrect communication packet. @item @code{MATCH ... AGAINST(... IN BOOLEAN MODE)} can now work without @code{FULLTEXT} index. @item Fixed slave to replicate from 3.23 master. @item Miscellaneous replication fixes/cleanup. @item Got shutdown to work on Mac OS X. @item Added @file{myisam/ft_dump} utility for low-level inspection of @code{FULLTEXT} indexes. @item Fixed bug in @code{DELETE ... WHERE ... MATCH ...}. @item Added support for @code{MATCH ... AGAINST(... IN BOOLEAN MODE)}. @strong{Note: you must rebuild your tables with @code{ALTER TABLE tablename TYPE=MyISAM} to be able to use boolean full-text search}. @item @code{LOCATE()} and @code{INSTR()} are now case-sensitive if either argument is a binary string. @item Changed @code{RAND()} initialisation so that @code{RAND(N)} and @code{RAND(N+1)} are more distinct. @item Fixed core dump bug in @code{UPDATE ... ORDER BY}. @item Changed @code{INSERT INTO ... SELECT} to stop on errors by default. @item Ignore @code{DATA DIRECTORY} and @code{INDEX DIRECTORY} directives on Windows. @item Added boolean full-text search code. It should be considered early alpha. @item Extended @code{MODIFY} and @code{CHANGE} in @code{ALTER TABLE} to accept the @code{FIRST} and @code{AFTER} keywords. @item Indexes are now used with @code{ORDER BY} on a whole @code{InnoDB} table. @end itemize @node News-4.0.0, , News-4.0.1, News-4.0.x @appendixsubsec Changes in release 4.0.0 (2001-10-16: Alpha) @itemize @bullet @item Added @code{--xml} option to @code{mysql} for producing XML output. @item Added full-text variables @code{ft_min_word_len}, @code{ft_max_word_len}, and @code{ft_max_word_len_for_sort}. @item Added documentation for @code{libmysqld}, the embedded MySQL server library. Also added example programs (a @code{mysql} client and @code{mysqltest} test program) which use @code{libmysqld}. @item Removed all Gemini hooks from MySQL server. @item Removed @code{my_thread_init()} and @code{my_thread_end()} from @file{mysql_com.h}, and added @code{mysql_thread_init()} and @code{mysql_thread_end()} to @file{mysql.h}. @item Support for communication packets > 16M. In 4.0.1 we will extend @code{MyISAM} to be able to handle these. @item Secure connections (with SSL). @item Unsigned @code{BIGINT} constants now work. @code{MIN()} and @code{MAX()} now handle signed and unsigned @code{BIGINT} numbers correctly. @item New character set @code{latin1_de} which provides correct German sorting. @item @code{STRCMP()} now uses the current character set when doing comparisons, which means that the default comparison behaviour now is case-insensitive. @item @code{TRUNCATE TABLE} and @code{DELETE FROM tbl_name} are now separate functions. One bonus is that @code{DELETE FROM tbl_name} now returns the number of deleted rows, rather than zero. @item @code{DROP DATABASE} now executes a @code{DROP TABLE} on all tables in the database, which fixes a problem with @code{InnoDB} tables. @item Added support for @code{UNION}. @item Added support for multi-table @code{DELETE} operations. @item A new @code{HANDLER} interface to @code{MyISAM} tables. @item Added support for @code{INSERT} on @code{MERGE} tables. Patch from Benjamin Pflugmann. @item Changed @code{WEEK(#,0)} to match the calendar in the USA. @item @code{COUNT(DISTINCT)} is about 30% faster. @item Speed up all internal list handling. @item Speed up @code{IS NULL}, @code{ISNULL()} and some other internal primitives. @item Full-text index creation now is much faster. @item Tree-like cache to speed up bulk inserts and @code{myisam_bulk_insert_tree_size} variable. @item Searching on packed (@code{CHAR}/@code{VARCHAR}) keys is now much faster. @item Optimised queries of type: @code{SELECT DISTINCT * from tbl_name ORDER by key_part1 LIMIT #}. @item @code{SHOW CREATE TABLE} now shows all table attributes. @item @code{ORDER BY ... DESC} can now use keys. @item @code{LOAD DATA FROM MASTER} ``automatically'' sets up a slave. @item Renamed @code{safe_mysqld} to @code{mysqld_safe} to make this name more in line with other MySQL scripts/commands. @item Added support for symbolic links to @code{MyISAM} tables. Symlink handling is now enabled by default for Windows. @item Added @code{SQL_CALC_FOUND_ROWS} and @code{FOUND_ROWS()}. This makes it possible to know how many rows a query would have returned without a @code{LIMIT} clause. @item Changed output format of @code{SHOW OPEN TABLES}. @item Allow @code{SELECT expression LIMIT ...}. @item Added @code{IDENTITY} as a synonym for @code{AUTO_INCREMENT} (like Sybase). @item Added @code{ORDER BY} syntax to @code{UPDATE} and @code{DELETE}. @item @code{SHOW INDEXES} is now a synonym for @code{SHOW INDEX}. @item Added @code{ALTER TABLE tbl_name DISABLE KEYS} and @code{ALTER TABLE tbl_name ENABLE KEYS} commands. @item Allow use of @code{IN} as a synonym for @code{FROM} in @code{SHOW} commands. @item Implemented ``repair by sort'' for @code{FULLTEXT} indexes. @code{REPAIR TABLE}, @code{ALTER TABLE}, and @code{OPTIMIZE TABLE} for tables with @code{FULLTEXT} indexes are now up to 100 times faster. @item Allow ANSI SQL syntax @code{X'hexadecimal-number'}. @item Cleaned up global lock handling for @code{FLUSH TABLES WITH READ LOCK}. @item Fixed problem with @code{DATETIME = constant} in @code{WHERE} optimisation. @item Added @code{--master-data} and @code{--no-autocommit} options to @code{mysqldump}. (Thanks to Brian Aker for this.) @item Added script @code{mysql_explain_log.sh} to distribution. (Thanks to mobile.de). @end itemize @node News-3.23.x, News-3.22.x, News-4.0.x, News @appendixsec Changes in release 3.23.x (Stable) @cindex changes, version 3.23 The 3.23 release has several major features that are not present in previous versions. We have added three new table types: @table @asis @item @code{MyISAM} A new ISAM library which is tuned for SQL and supports large files. @item @code{InnoDB} A transaction-safe storage engine that supports row level locking, and many Oracle-like features. @item @code{BerkeleyDB} or @code{BDB} Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables. @end table Note that only @code{MyISAM} is available in the standard binary distribution. The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more. All new features are being developed in the 4.x version. Only bug fixes and minor enhancements to existing features will be added to 3.23. The replication code and BerkeleyDB code is still not as tested and as the rest of the code, so we will probably need to do a couple of future releases of 3.23 with small fixes for this part of the code. As long as you don't use these features, you should be quite safe with MySQL 3.23! Note that the above doesn't mean that replication or Berkeley DB don't work. We have done a lot of testing of all code, including replication and @code{BDB} without finding any problems. It only means that not as many users use this code as the rest of the code and because of this we are not yet 100% confident in this code. @menu * News-3.23.57:: Changes in release 3.23.57 (not released yet) * News-3.23.56:: Changes in release 3.23.56 (13 Mar 2003) * News-3.23.55:: Changes in release 3.23.55 (23 Jan 2003) * News-3.23.54:: Changes in release 3.23.54 (05 Dec 2002) * News-3.23.53:: Changes in release 3.23.53 (09 Oct 2002) * News-3.23.52:: Changes in release 3.23.52 (14 Aug 2002) * News-3.23.51:: Changes in release 3.23.51 (31 May 2002) * News-3.23.50:: Changes in release 3.23.50 (21 Apr 2002) * News-3.23.49:: Changes in release 3.23.49 * News-3.23.48:: Changes in release 3.23.48 (07 Feb 2002) * News-3.23.47:: Changes in release 3.23.47 (27 Dec 2001) * News-3.23.46:: Changes in release 3.23.46 (29 Nov 2001) * News-3.23.45:: Changes in release 3.23.45 (22 Nov 2001) * News-3.23.44:: Changes in release 3.23.44 (31 Oct 2001) * News-3.23.43:: Changes in release 3.23.43 (04 Oct 2001) * News-3.23.42:: Changes in release 3.23.42 (08 Sep 2001) * News-3.23.41:: Changes in release 3.23.41 (11 Aug 2001) * News-3.23.40:: Changes in release 3.23.40 * News-3.23.39:: Changes in release 3.23.39 (12 Jun 2001) * News-3.23.38:: Changes in release 3.23.38 (09 May 2001) * News-3.23.37:: Changes in release 3.23.37 (17 Apr 2001) * News-3.23.36:: Changes in release 3.23.36 (27 Mar 2001) * News-3.23.35:: Changes in release 3.23.35 (15 Mar 2001) * News-3.23.34a:: Changes in release 3.23.34a * News-3.23.34:: Changes in release 3.23.34 (10 Mar 2001) * News-3.23.33:: Changes in release 3.23.33 (09 Feb 2001) * News-3.23.32:: Changes in release 3.23.32 (22 Jan 2001: Stable) * News-3.23.31:: Changes in release 3.23.31 (17 Jan 2001) * News-3.23.30:: Changes in release 3.23.30 (04 Jan 2001) * News-3.23.29:: Changes in release 3.23.29 (16 Dec 2000) * News-3.23.28:: Changes in release 3.23.28 (22 Nov 2000: Gamma) * News-3.23.27:: Changes in release 3.23.27 (24 Oct 2000) * News-3.23.26:: Changes in release 3.23.26 (18 Oct 2000) * News-3.23.25:: Changes in release 3.23.25 (29 Sep 2000) * News-3.23.24:: Changes in release 3.23.24 (08 Sep 2000) * News-3.23.23:: Changes in release 3.23.23 (01 Sep 2000) * News-3.23.22:: Changes in release 3.23.22 (31 Jul 2000) * News-3.23.21:: Changes in release 3.23.21 * News-3.23.20:: Changes in release 3.23.20 * News-3.23.19:: Changes in release 3.23.19 * News-3.23.18:: Changes in release 3.23.18 * News-3.23.17:: Changes in release 3.23.17 * News-3.23.16:: Changes in release 3.23.16 * News-3.23.15:: Changes in release 3.23.15 (May 2000: Beta) * News-3.23.14:: Changes in release 3.23.14 * News-3.23.13:: Changes in release 3.23.13 * News-3.23.12:: Changes in release 3.23.12 (07 Mar 2000) * News-3.23.11:: Changes in release 3.23.11 * News-3.23.10:: Changes in release 3.23.10 * News-3.23.9:: Changes in release 3.23.9 * News-3.23.8:: Changes in release 3.23.8 (02 Jan 2000) * News-3.23.7:: Changes in release 3.23.7 (10 Dec 1999) * News-3.23.6:: Changes in release 3.23.6 * News-3.23.5:: Changes in release 3.23.5 (20 Oct 1999) * News-3.23.4:: Changes in release 3.23.4 (28 Sep 1999) * News-3.23.3:: Changes in release 3.23.3 * News-3.23.2:: Changes in release 3.23.2 (09 Aug 1999) * News-3.23.1:: Changes in release 3.23.1 * News-3.23.0:: Changes in release 3.23.0 (05 Aug 1999: Alpha) @end menu @node News-3.23.57, News-3.23.56, News-3.23.x, News-3.23.x @appendixsubsec Changes in release 3.23.57 (not released yet) @itemize @item Give an error for empty table and column names. @item Changed @code{PROCEDURE ANALYSE()} to report @code{DATE} instead of @code{NEWDATE}. @item Changed @code{PROCEDURE ANALYSE(#)} to restrict number of values in enum to @code{#} also for string values. @end itemize @node News-3.23.56, News-3.23.55, News-3.23.57, News-3.23.x @appendixsubsec Changes in release 3.23.56 (13 Mar 2003) @itemize @item Fixed @file{mysqld} crash on extremely small values of @code{sort_buffer} variable. @item Fixed a bug in privilege system for @code{GRANT UPDATE} on column level. @item Fixed a rare bug when using a date in @code{HAVING} with @code{GROUP BY}. @item Fixed checking of random part of @code{WHERE} clause (Bug #142). @item Fixed MySQL (and @file{myisamchk}) crash on artificially corrupted @code{.MYI} files. @item Security enhancement: @file{mysqld} no longer reads options from world-writeable config files. @item Security enhancement: @file{mysqld} and @file{safe_mysqld} now only use the first @code{--user} option specified on the command line. (Normally this comes from @file{/etc/my.cnf}) @item Security enhancement: Don't allow @code{BACKUP TABLE} to overwrite existing files. @item Fixed unlikely deadlock bug when one thread did a @code{LOCK TABLE} and another thread did a @code{DROP TABLE}. In this case one could do a @code{KILL} on one of the threads to resolve the deadlock. @item @code{LOAD DATA INFILE} was not replicated by slave if @code{replicate_*_table} was set on the slave. @item Fixed a bug in handling @code{CHAR(0)} columns that could cause wrong results from the query. @item Fixed a bug in @code{SHOW VARIABLES} on 64-bit platforms. The bug was caused by wrong declaration of variable @code{server_id}. @item The Comment column in @code{SHOW TABLE STATUS} now reports that it can contain @code{NULL} values (which is the case for a crashed @file{.frm} file). @item Fixed the @code{rpl_rotate_logs} test to not fail on certain platforms (e.g. Mac OS X) due to a too long file name (changed @code{slave-master-info.opt} to @code{.slave-mi}). @item Fixed a problem with @code{BLOB NOT NULL} columns used with @code{IS NULL}. @item Fixed bug in @code{MAX()} optimization in @code{MERGE} tables. @item Better @code{RAND()} initialization for new connections. @item Fixed bug with connect timeout. This bug was manifested on OS's with @code{poll()} system call, which resulted in timeout the value specified as it was executed in both @code{select()} and @code{poll()}. @item Fixed bug in @code{SELECT * FROM table WHERE datetime1 IS NULL OR datetime2 IS NULL}. @item Fixed bug in using aggregate functions as argument for @code{INTERVAL}, @code{CASE}, @code{FIELD}, @code{CONCAT_WS}, @code{ELT} and @code{MAKE_SET} functions. @item When running with @code{--lower-case-table-names} (default on windows) and you had tables or databases with mixed case on disk, then executing @code{SHOW TABLE STATUS} followed with @code{DROP DATABASE} or @code{DROP TABLE} could fail with @code{Errcode 13}. @item Fixed bug in logging to binary log (which affects replication) a query that inserts a @code{NULL} in an @code{auto_increment} field and also uses @code{LAST_INSERT_ID()}. @item Fixed bug in @code{mysqladmin --relative}. @item On some 64 bit systems, @code{show status} reported a strange number for @code{Open_files} and @code{Open_streams}. @end itemize @node News-3.23.55, News-3.23.54, News-3.23.56, News-3.23.x @appendixsubsec Changes in release 3.23.55 (23 Jan 2003) @itemize @item Fixed double @code{free}'d pointer bug in @code{mysql_change_user()} handling, that enabled a specially hacked version of MySQL client to crash @code{mysqld}. @strong{Note}, that one needs to login to the server by using a valid user account to be able to exploit this bug. @item Fixed bug with the @code{--slow-log} when logging an administrator command (like @code{FLUSH TABLES}). @item Fixed bug in @code{GROUP BY} when used on BLOB column with @code{NULL} values. @item Fixed a bug in handling @code{NULL}s in @code{CASE ... WHEN ...}. @item Bugfix for @code{--chroot} (@pxref{News-3.23.54, @code{--chroot}}) is reverted. Unfortunately, there is no way to make it to work, without introducing backward-incompatible changes in @file{my.cnf}. Those who need @code{--chroot} functionality, should upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break backward-compatibility). @item Make @code{--lower-case-table-names} default on Mac OS X as the file system is case insensitive. @item Fixed a bug in @file{scripts/mysqld_safe.sh} in @code{NOHUP_NICENESS} testing. @item Transactions in @code{AUTOCOMMIT=0} mode didn't rotate binary log. @item Fixed a bug in @code{scripts/make_binary_distribution} that resulted in a remaining @code{@@HOSTNAME@@} variable instead of replacing it with the correct path to the @code{hostname} binary. @item Fixed a very unlikely bug that could cause @code{SHOW PROCESSLIST} to core dump in pthread_mutex_unlock() if a new thread was connecting. @item Forbid @code{SLAVE STOP} if the thread executing the query has locked tables. This removes a possible deadlock situation. @end itemize @node News-3.23.54, News-3.23.53, News-3.23.55, News-3.23.x @appendixsubsec Changes in release 3.23.54 (2002-12-05) @itemize @item Fixed a bug, that allowed to crash @code{mysqld} with a specially crafted packet. @item Fixed a rare crash (double @code{free}'d pointer) when altering a temporary table. @item Fixed buffer overrun in @code{libmysqlclient} library that allowed malicious MySQL server to crash the client application. @item Fixed security-related bug in @code{mysql_change_user()} handling. All users are strongly recommended to upgrade to the version 3.23.54. @item Fixed bug that prevented @code{--chroot} command-line option of @code{mysqld} from working. @item Fixed bug that made @code{OPTIMIZE TABLE} to corrupt the table under some rare circumstances. @item Fixed @code{mysqlcheck} so it can deal with table names containing dashes. @item Fixed shutdown problem on Mac OS X. @item Fixed bug with comparing an indexed @code{NULL} field with @code{<=> NULL}. @item Fixed bug that caused @code{IGNORE INDEX} and @code{USE INDEX} sometimes to be ignored. @item Fixed rare core dump problem in complicated @code{GROUP BY} queries that didn't return any result. @item Fixed a bug where @code{MATCH ... AGAINST () >=0} was treated as if it was @code{>}. @item Fixed core dump in @code{SHOW PROCESSLIST} when running with an active slave (unlikely timing bug). @item Allow one to start multiple MySQL servers on windows (code backported from 4.0.2). @item One can create @code{TEMPORARY} @code{MERGE} tables now. @item Fixed that @code{--core-file} works on Linux (at least on kernel 2.4.18). @item Fixed a problem with @code{BDB} and @code{ALTER TABLE}. @item Fixed reference to freed memory when doing complicated @code{GROUP BY ... ORDER BY} queries. Symptom was that @code{mysqld} died in function @code{send_fields}. @item Allocate heap rows in smaller blocks to get better memory usage. @item Fixed memory allocation bug when storing @code{BLOB} values in internal temporary tables used for some (unlikely) @code{GROUP BY} queries. @item Fixed a bug in key optimizing handling where the expression @code{WHERE column_name = key_column_name} was calculated as true for @code{NULL} values. @item Fixed core dump bug when doing @code{LEFT JOIN ... WHERE key_column=NULL}. @item Fixed @code{MyISAM} crash when using dynamic-row tables with huge numbers of packed fields. @item Updated source tree to be built using @code{automake 1.5} and @code{libtool 1.4}. @end itemize @node News-3.23.53, News-3.23.52, News-3.23.54, News-3.23.x @appendixsubsec Changes in release 3.23.53 (2002-10-09) @itemize @bullet @item Fixed crash when @code{SHOW INNODB STATUS} was used and @code{skip-innodb} was defined. @item Fixed possible memory corruption bug in binary log file handling when slave rotated the logs (only affected 3.23, not 4.0). @item Fixed problem in @code{LOCK TABLES} on windows when one connects to a database that contains upper case letters. @item Fixed that @code{--skip-show-databases} doesn't reset the @code{--port} option. @item Small fix in @code{safe_mysqld} for some shells. @item Fixed that @code{FLUSH STATUS} doesn't reset @code{Delayed_insert_threads}. @item Fixed core dump bug when using the @code{BINARY} cast on a @code{NULL} value. @item Fixed race condition when someone did a @code{GRANT} at the same time a new user logged in or did a @code{USE DATABASE}. @item Fixed bug in @code{ALTER TABLE} and @code{RENAME TABLE} when running with @code{-O lower_case_table_names=1} (typically on windows) when giving the table name in uppercase. @item Fixed that @code{-O lower_case_table_names=1} also converts database names to lower case. @item Fixed unlikely core dump with @code{SELECT ... ORDER BY ... LIMIT}. @item Changed @code{AND/OR} to report that they can return NULL. This fixes a bug in @code{GROUP BY} on @code{AND/OR} expressions that return @code{NULL}. @item Fixed a bug that @code{OPTIMIZE} of locked and modified MyISAM table, reported table corruption. @item Fixed a @code{BDB}-related @code{ALTER TABLE} bug with dropping a column and shutting down immediately thereafter. @item Fixed problem with @code{configure ... --localstatedir=...}. @item Fixed problem with @code{UNSIGNED BIGINT} on AIX (again). @item Fixed bug in pthread_mutex_trylock() on HPUX 11.0. @item Multithreaded stress tests for InnoDB. @end itemize @node News-3.23.52, News-3.23.51, News-3.23.53, News-3.23.x @appendixsubsec Changes in release 3.23.52 (2002-08-14) @itemize @bullet @item Wrap @code{BEGIN}/@code{COMMIT} around transaction in the binary log. This makes replication honour transactions. @item Fixed security bug when having an empty database name in the @code{user.db} table. @item Changed initialisation of @code{RND()} to make it less predicatable. @item Fixed problem with @code{GROUP BY} on result with expression that created a @code{BLOB} field. @item Fixed problem with @code{GROUP BY} on columns that have @code{NULL} values. To solve this we now create an @code{MyISAM} temporary table when doing a @code{GROUP BY} on a possible @code{NULL} item. From MySQL 4.0.5 we can use in memory @code{HEAP} tables for this case. @item Fixed problem with privilege tables when downgrading from 4.0.2 to 3.23. @item Fixed thread bug in @code{SLAVE START}, @code{SLAVE STOP} and automatic repair of MyISAM tables that could cause table cache to be corrupted. @item Fixed possible thread related key-cache-corruption problem with @code{OPTIMIZE TABLE} and @code{REPAIR TABLE}. @item Added name of 'administrator command' logs. @item Fixed bug with creating an auto-increment value on second part of a @code{UNIQUE()} key where first part could contain NULL values. @item Don't write slave-timeout reconnects to the error log. @item Fixed bug with slave net read timeouting @item Fixed a core-dump bug with @code{MERGE} tables and @code{MAX()} function. @item Fixed bug in @code{ALTER TABLE} with @code{BDB} tables. @item Fixed bug when logging @code{LOAD DATA INFILE} to binary log with no active database. @item Fixed a bug in range optimiser (causing crashes). @item Fixed possible problem in replication when doing @code{DROP DATABASE} on a database with @code{InnoDB} tables. @item Fixed that @code{mysql_info()} returns 0 for 'Duplicates' when using @code{INSERT DELAYED IGNORE}. @item Added @code{-DHAVE_BROKEN_REALPATH} to the Mac OS X (darwin) compile options in @file{configure.in} to fix a failure under high load. @end itemize @node News-3.23.51, News-3.23.50, News-3.23.52, News-3.23.x @appendixsubsec Changes in release 3.23.51 (2002-05-31) @itemize @bullet @item Fix bug with closing tags missing slash for @code{mysqldump} XML output. @item Remove end space from @code{ENUM} values. (This fixed a problem with @code{SHOW CREATE TABLE}.) @item Fixed bug in @code{CONCAT_WS()} that cut the result. @item Changed name of server variables @code{Com_show_master_stat} to @code{Com_show_master_status} and @code{Com_show_slave_stat} to @code{Com_show_slave_status}. @item Changed handling of @code{gethostbyname()} to make the client library thread-safe even if @code{gethostbyname_r} doesn't exist. @item Fixed core-dump problem when giving a wrong password string to @code{GRANT}. @item Fixed bug in @code{DROP DATABASE} with symlinked directory. @item Fixed optimisation problem with @code{DATETIME} and value outside @code{DATETIME} range. @item Removed Sleepycat's @code{BDB} doc files from the source tree, as they're not needed (MySQL covers @code{BDB} in its own documentation). @item Fixed MIT-pthreads to compile with @code{glibc} 2.2 (needed for @code{make dist}). @item Fixed the @code{FLOAT(X+1,X)} is not converted to @code{FLOAT(X+2,X)}. (This also affected @code{DECIMAL}, @code{DOUBLE} and @code{REAL} types) @item Fixed the result from @code{IF()} is case in-sensitive if the second and third arguments are case sensitive. @item Fixed core dump problem on OSF/1 in @code{gethostbyname_r}. @item Fixed that underflowed decimal fields are not zero filled. @item If we get an overflow when inserting @code{'+11111'} for @code{DECIMAL(5,0) UNSIGNED} columns, we will just drop the sign. @item Fixed optimisation bug with @code{ISNULL(expression_which_cannot_be_null)} and @code{ISNULL(constant_expression)}. @item Fixed host lookup bug in the @code{glibc} library that we used with the 3.23.50 Linux-x86 binaries. @end itemize @node News-3.23.50, News-3.23.49, News-3.23.51, News-3.23.x @appendixsubsec Changes in release 3.23.50 (2002-04-21) @itemize @bullet @item Fixed buffer overflow problem if someone specified a too long datadir parameter to mysqld @item Add missing @code{} tags for @code{mysqldump} XML output. @item Fixed problem with @code{crash-me} and @code{gcc} 3.0.4. @item Fixed that @code{@@@@unknown_variable} doesn't hang server. @item Added @code{@@@@VERSION} as a synonym for @code{VERSION()}. @item @code{SHOW VARIABLES LIKE 'xxx'} is now case-insensitive. @item Fixed timeout for @code{GET_LOCK()} on HP-UX with DCE threads. @item Fixed memory allocation bug in the glibc library used to build Linux binaries, which caused mysqld to die in 'free()'. @item Fixed @code{SIGINT} and @code{SIGQUIT} problems in @code{mysql}. @item Fixed bug in character table converts when used with big ( > 64K) strings. @item @code{InnoDB} now retains foreign key constraints through @code{ALTER TABLE} and @code{CREATE/DROP INDEX}. @item @code{InnoDB} now allows foreign key constraints to be added through the @code{ALTER TABLE} syntax. @item @code{InnoDB} tables can now be set to automatically grow in size (autoextend). @item Our Linux RPMS and binaries are now compiled with @code{gcc} 3.0.4, which should make them a bit faster. @item Fixed some buffer overflow problems when reading startup parameters. @item Because of problems on shutdown we have now disabled named pipes on windows by default. One can enable named pipes by starting mysqld with @code{--enable-named-pipe}. @item Fixed bug when using @code{WHERE key_column = 'J' or key_column='j'}. @item Fixed core-dump bug when using @code{--log-bin} with @code{LOAD DATA INFILE} without an active database. @item Fixed bug in @code{RENAME TABLE} when used with @code{lower_case_table_names=1} (default on Windows). @item Fixed unlikely core-dump bug when using @code{DROP TABLE} on a table that was in use by a thread that also used queries on only temporary tables. @item Fixed problem with @code{SHOW CREATE TABLE} and @code{PRIMARY KEY} when using 32 indexes. @item Fixed that one can use @code{SET PASSWORD} for the anonymous user. @item Fixed core dump bug when reading client groups from option files using @code{mysql_options()}. @item Memory leak (16 bytes per every @strong{corrupted} table) closed. @item Fixed binary builds to use @code{--enable-local-infile}. @item Update source to work with new version of @code{bison}. @item Updated shell scripts to now agree with new POSIX standard. @item Fixed bug where @code{DATE_FORMAT()} returned empty string when used with @code{GROUP BY}. @end itemize @node News-3.23.49, News-3.23.48, News-3.23.50, News-3.23.x @appendixsubsec Changes in release 3.23.49 (2002-02-16) @itemize @bullet @item Don't give warning for a statement that is only a comment; this is needed for @code{mysqldump --disable-keys} to work. @item Fixed unlikely caching bug when doing a join without keys. In this case the last used field for a table always returned @code{NULL}. @item Added options to make @code{LOAD DATA LOCAL INFILE} more secure. @item MySQL binary release 3.23.48 for Linux contained a new @code{glibc} library, which has serious problems under high load and RedHat 7.2. The 3.23.49 binary release doesn't have this problem. @item Fixed shutdown problem on NT. @end itemize @node News-3.23.48, News-3.23.47, News-3.23.49, News-3.23.x @appendixsubsec Changes in release 3.23.48 (2002-02-07) @itemize @bullet @item Added @code{--xml} option to @code{mysqldump} for producing XML output. @item Changed to use @code{autoconf} 2.52 (from @code{autoconf} 2.13) @item Fixed bug in complicated join with @code{const} tables. @item Added internal safety checks for @code{InnoDB}. @item Some @code{InnoDB} variables were always shown in @code{SHOW VARIABLES} as @code{OFF} on high-byte-first systems (like SPARC). @item Fixed problem with one thread using an @code{InnoDB} table and another thread doing an @code{ALTER TABLE} on the same table. Before that, @code{mysqld} could crash with an assertion failure in @file{row0row.c}, line 474. @item Tuned the @code{InnoDB} SQL optimiser to favor index searches more often over table scans. @item Fixed a performance problem with @code{InnoDB} tables when several large @code{SELECT} queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound @code{SELECT} queries will now also generally run faster on all platforms. @item If MySQL binlogging is used, @code{InnoDB} now prints after crash recovery the latest MySQL binlog name and the offset @code{InnoDB} was able to recover to. This is useful, for example, when resynchronising a master and a slave database in replication. @item Added better error messages to help in installation problems of @code{InnoDB} tables. @item It is now possible to recover MySQL temporary tables that have become orphaned inside the @code{InnoDB} tablespace. @item @code{InnoDB} now prevents a @code{FOREIGN KEY} declaration where the signedness is not the same in the referencing and referenced integer columns. @item Calling @code{SHOW CREATE TABLE} or @code{SHOW TABLE STATUS} could cause memory corruption and make @code{mysqld} crash. Especially at risk was @code{mysqldump}, because it frequently calls @code{SHOW CREATE TABLE}. @item If inserts to several tables containing an @code{AUTO_INCREMENT} column were wrapped inside one @code{LOCK TABLES}, @code{InnoDB} asserted in @file{lock0lock.c}. @item In 3.23.47 we allowed several @code{NULL} values in a @code{UNIQUE} secondary index for an @code{InnoDB} table. But @code{CHECK TABLE} was not relaxed: it reports the table as corrupt. @code{CHECK TABLE} no longer complains in this situation. @item @code{SHOW GRANTS} now shows @code{REFERENCES} instead of @code{REFERENCE}. @end itemize @node News-3.23.47, News-3.23.46, News-3.23.48, News-3.23.x @appendixsubsec Changes in release 3.23.47 (2001-12-27) @itemize @bullet @item Fixed bug when using the following construct: @code{SELECT ... WHERE key=@@var_name OR key=@@var_name2} @item Restrict @code{InnoDB} keys to 500 bytes. @item @code{InnoDB} now supports @code{NULL} in keys. @item Fixed shutdown problem on HP-UX. (Introduced in 3.23.46) @item Fixed core dump bug in replication when using @code{SELECT RELEASE_LOCK()}. @item Added new command: @code{DO expression,[expression]} @item Added @code{slave-skip-errors} option. @item Added statistics variables for all MySQL commands. (@code{SHOW STATUS} is now much longer.) @item Fixed default values for @code{InnoDB} tables. @item Fixed that @code{GROUP BY expr DESC} works. @item Fixed bug when using @code{t1 LEFT JOIN t2 ON t2.key=constant}. @item @code{mysql_config} now also works with binary (relocated) distributions. @end itemize @node News-3.23.46, News-3.23.45, News-3.23.47, News-3.23.x @appendixsubsec Changes in release 3.23.46 (2001-11-29) @itemize @bullet @item Fixed problem with aliased temporary table replication. @item @code{InnoDB} and @code{BDB} tables will now use index when doing an @code{ORDER BY} on the whole table. @item Fixed bug where one got an empty set instead of a DEADLOCK error when using @code{BDB} tables. @item One can now kill @code{ANALYZE}, @code{REPAIR}, and @code{OPTIMIZE TABLE} when the thread is waiting to get a lock on the table. @item Fixed race condition in @code{ANALYZE TABLE}. @item Fixed bug when joining with caching (unlikely to happen). @item Fixed race condition when using the binary log and @code{INSERT DELAYED} which could cause the binary log to have rows that were not yet written to @code{MyISAM} tables. @item Changed caching of binary log to make replication slightly faster. @item Fixed bug in replication on Mac OS X. @end itemize @node News-3.23.45, News-3.23.44, News-3.23.46, News-3.23.x @appendixsubsec Changes in release 3.23.45 (2001-11-22) @itemize @bullet @item @code{(UPDATE|DELETE) ...WHERE MATCH} bugfix. @item shutdown should now work on Darwin (Mac OS X). @item Fixed core dump when repairing corrupted packed @code{MyISAM} files. @item @code{--core-file} now works on Solaris. @item Fix a bug which could cause @code{InnoDB} to complain if it cannot find free blocks from the buffer cache during recovery. @item Fixed bug in @code{InnoDB} insert buffer B-tree handling that could cause crashes. @item Fixed bug in @code{InnoDB} lock timeout handling. @item Fixed core dump bug in @code{ALTER TABLE} on a @code{TEMPORARY} @code{InnoDB} table. @item Fixed bug in @code{OPTIMIZE TABLE} that reset index cardinality if it was up to date. @item Fixed problem with @code{t1 LEFT_JOIN t2 ... WHERE t2.date_column IS NULL} when date_column was declared as @code{NOT NULL}. @item Fixed bug with BDB tables and keys on @code{BLOB}'s. @item Fixed bug in @code{MERGE} tables on OS with 32 bit file pointers. @item Fixed bug in @code{TIME_TO_SEC()} when using negative values. @end itemize @node News-3.23.44, News-3.23.43, News-3.23.45, News-3.23.x @appendixsubsec Changes in release 3.23.44 (2001-10-31) @itemize @bullet @item Fixed @code{Rows_examined} count in slow query log. @item Fixed bug when using a reference to an @code{AVG()} column in @code{HAVING}. @item Fixed that date functions that require correct dates, like @code{DAYOFYEAR(column)}, will return @code{NULL} for @code{0000-00-00} dates. @item Fixed bug in const-propagation when comparing columns of different types. (@code{SELECT * FROM date_col="2001-01-01" and date_col=time_col}) @item Fixed bug that caused error message @code{Can't write, because of unique constraint} with some @code{GROUP BY} queries. @item SJIS において、テーブル名、フィールド名をバッククオートで囲んだ場合の問題を修正 @item Fixed core dump when using @code{CREATE ... FULLTEXT} keys with other storage engines than @code{MyISAM}. @item Add missing @code{InnoDB} variables to @code{SHOW VARIABLES}. @item Foreign keys checking is now done for @code{InnoDB} tables. @item Don't use @code{signal()} on Windows because this appears to not be 100% reliable. @item Fixed bug when doing @code{WHERE col_name=NULL} on an indexed column that had @code{NULL} values. @item Fixed bug when doing @code{LEFT JOIN ... ON (column_name = constant) WHERE column_name = constant}. @item When using replications, aborted queries that contained @code{%} could cause a core dump. @item @code{TCP_NODELAY} がいくつかのシステムで使用されていなかったのを修正(TCP 通信時の速度低下の問題). @item Applied portability fixes for OS/2. (Patch by Yuri Dario.) @end itemize The following changes are for @code{InnoDB} tables: @itemize @bullet @item Add missing @code{InnoDB} variables to @code{SHOW VARIABLES}. @item Foreign keys checking is now done for @code{InnoDB} tables. @item @code{DROP DATABASE} now works also for @code{InnoDB} tables. @item @code{InnoDB} now supports datafiles and raw disk partitions bigger than 4 GB on those operating systems that have big files. @item @code{InnoDB} calculates better table cardinality estimates for the MySQL optimiser. @item Accent characters in the default character set @code{latin1} are ordered according to the MySQL ordering. Note: if you are using @code{latin1} and have inserted characters whose code is greater than 127 into an indexed @code{CHAR} column, you should run @code{CHECK TABLE} on your table when you upgrade to 3.23.44, and drop and reimport the table if @code{CHECK TABLE} reports an error! @item A new @file{my.cnf} parameter, @code{innodb_thread_concurrency}, helps in performance tuning in heavily concurrent environments. @item A new @file{my.cnf} parameter, @code{innodb_fast_shutdown}, speeds up server shutdown. @item A new @file{my.cnf} parameter, @code{innodb_force_recovery}, helps to save your data in case the disk image of the database becomes corrupt. @item @code{innodb_monitor} has been improved and a new @code{innodb_table_monitor} added. @item Increased maximum key length from 500 to 7000 bytes. @item Fixed a bug in replication of @code{AUTO_INCREMENT} columns with multiple-line inserts. @item Fixed a bug when the case of letters changes in an update of an indexed secondary column. @item Fixed a hang when there are > 24 datafiles. @item Fixed a crash when @code{MAX(col)} is selected from an empty table, and @code{col} is not the first column in a multi-column index. @item Fixed a bug in purge which could cause crashes. @end itemize @node News-3.23.43, News-3.23.42, News-3.23.44, News-3.23.x @appendixsubsec Changes in release 3.23.43 (2001-10-04) @itemize @bullet @item Fixed a bug in @code{INSERT DELAYED} and @code{FLUSH TABLES} introduced in 3.23.42. @item Fixed unlikely bug, which returned non-matching rows, in @code{SELECT} with many tables and multi-column indexes and 'range' type. @item Fixed an unlikely core dump bug when doing @code{EXPLAIN SELECT} when using many tables and @code{ORDER BY}. @item Fixed bug in @code{LOAD DATA FROM MASTER} when using table with @code{CHECKSUM=1}. @item Added unique error message when one gets a DEADLOCK during a transaction with @code{BDB} tables. @item Fixed problem with @code{BDB} tables and @code{UNIQUE} columns defined as @code{NULL}. @item Fixed problem with @code{myisampack} when using pre-space filled @code{CHAR} columns. @item Applied patch from Yuri Dario for OS/2. @item Fixed bug in @code{--safe-user-create}. @end itemize @node News-3.23.42, News-3.23.41, News-3.23.43, News-3.23.x @appendixsubsec Changes in release 3.23.42 (2001-09-08) @itemize @bullet @item Fixed problem when using @code{LOCK TABLES} and @code{BDB} tables. @item Fixed problem with @code{REPAIR TABLE} on @code{MyISAM} tables with row lengths in the range from 65517 to 65520 bytes. @item Fixed rare hang when doing @code{mysqladmin shutdown} when there was a lot of activity in other threads. @item Fixed problem with @code{INSERT DELAYED} where delay thread could be hanging on @code{upgrading locks} with no apparent reason. @item Fixed problem with @code{myisampack} and @code{BLOB}. @item Fixed problem when one edited @file{.MRG} tables by hand. (Patch from Benjamin Pflugmann). @item Enforce that all tables in a @code{MERGE} table come from the same database. @item Fixed bug with @code{LOAD DATA INFILE} and transactional tables. @item Fix bug when using @code{INSERT DELAYED} with wrong column definition. @item Fixed core dump during @code{REPAIR} of some particularly broken tables. @item Fixed bug in @code{InnoDB} and @code{AUTO_INCREMENT} columns. @item Fixed bug in @code{InnoDB} and @code{RENAME TABLE} columns. @item Fixed critical bug in @code{InnoDB} and @code{BLOB} columns. If you have used @code{BLOB} columns larger than 8000 bytes in an @code{InnoDB} table, it is necessary to dump the table with @code{mysqldump}, drop it and restore it from the dump. @item Applied large patch for OS/2 from Yuri Dario. @item Fixed problem with @code{InnoDB} when one could get the error @code{Can't execute the given command...} even when no transaction was active. @item Applied some minor fixes that concern Gemini. @item Use real arithmetic operations even in integer context if not all arguments are integers. (Fixes uncommon bug in some integer contexts). @item Don't force everything to lowercase on Windows. (To fix problem with Windows and @code{ALTER TABLE}). Now @code{--lower_case_names} also works on Unix. @item Fixed that automatic rollback is done when thread end doesn't lock other threads. @end itemize @node News-3.23.41, News-3.23.40, News-3.23.42, News-3.23.x @appendixsubsec Changes in release 3.23.41 (2001-08-11) @itemize @bullet @item Added @code{--sql-mode=option[,option[,option]]} option to @code{mysqld}. @xref{Command-line options}. @item Fixed possible problem with @code{shutdown} on Solaris where the @file{.pid} file wasn't deleted. @item @code{InnoDB} now supports < 4 GB rows. The former limit was 8000 bytes. @item The @code{doublewrite} file flush method is used in @code{InnoDB}. It reduces the need for Unix @code{fsync()} calls to a fraction and improves performance on most Unix flavors. @item You can now use the @code{InnoDB} Monitor to print a lot of @code{InnoDB} state information, including locks, to the standard output. This is useful in performance tuning. @item Several bugs which could cause hangs in @code{InnoDB} have been fixed. @item Split @code{record_buffer} to @code{record_buffer} and @code{record_rnd_buffer}. To make things compatible to previous MySQL versions, if @code{record_rnd_buffer} is not set, then it takes the value of @code{record_buffer}. @item Fixed optimizing bug in @code{ORDER BY} where some @code{ORDER BY} parts where wrongly removed. @item Fixed overflow bug with @code{ALTER TABLE} and @code{MERGE} tables. @item Added prototypes for @code{my_thread_init()} and @code{my_thread_end()} to @file{mysql_com.h} @item Added @code{--safe-user-create} option to @code{mysqld}. @item Fixed bug in @code{SELECT DISTINCT ... HAVING} that caused error message @code{Can't find record in #...} @end itemize @node News-3.23.40, News-3.23.39, News-3.23.41, News-3.23.x @appendixsubsec Changes in release 3.23.40 (2001-07-22) @itemize @bullet @item Fixed problem with @code{--low-priority-updates} and @code{INSERT} statements. @item Fixed bug in slave thread when under some rare circumstances it could get 22 bytes ahead on the offset in the master. @item Added @code{slave_net_timeout} for replication. @item Fixed problem with @code{UPDATE} and @code{BDB} tables. @item Fixed hard bug in @code{BDB} tables when using key parts. @item Fixed problem when using @code{GRANT FILE ON database.* ...}; previously we added the @code{DROP} privilege for the database. @item Fixed @code{DELETE FROM tbl_name ... LIMIT 0} and @code{UPDATE FROM tbl_name ... LIMIT 0}, which acted as though the @code{LIMIT} clause was not present (they deleted or updated all selected rows). @item @code{CHECK TABLE} now checks if an @code{AUTO_INCREMENT} column contains the value 0. @item Sending a @code{SIGHUP} to @code{mysqld} will now only flush the logs, not reset the replication. @item Fixed parser to allow floats of type @code{1.0e1} (no sign after @code{e}). @item Option @code{--force} to @code{myisamchk} now also updates states. @item Added option @code{--warnings} to @code{mysqld}. Now @code{mysqld} prints the error @code{Aborted connection} only if this option is used. @item Fixed problem with @code{SHOW CREATE TABLE} when you didn't have a @code{PRIMARY KEY}. @item Properly fixed the rename of @code{innodb_unix_file_flush_method} variable to @code{innodb_flush_method}. @item Fixed bug when converting @code{BIGINT UNSIGNED} to @code{DOUBLE}. This caused a problem when doing comparisons with @code{BIGINT} values outside of the signed range. @item Fixed bug in @code{BDB} tables when querying empty tables. @item Fixed a bug when using @code{COUNT(DISTINCT)} with @code{LEFT JOIN} and there weren't any matching rows. @item Removed all documentation referring to the @code{GEMINI} table type. @code{GEMINI} is not released under an @code{Open Source} license. @end itemize @node News-3.23.39, News-3.23.38, News-3.23.40, News-3.23.x @appendixsubsec Changes in release 3.23.39 (2001-06-12) @itemize @bullet @item The @code{AUTO_INCREMENT} sequence wasn't reset when dropping and adding an @code{AUTO_INCREMENT} column. @item @code{CREATE ... SELECT} now creates non-unique indexes delayed. @item Fixed problem where @code{LOCK TABLES tbl_name READ} followed by @code{FLUSH TABLES} put an exclusive lock on the table. @item @code{REAL @@variable} values were represented with only 2 digits when converted to strings. @item Fixed problem that client ``hung'' when @code{LOAD TABLE FROM MASTER} failed. @item @code{myisamchk --fast --force} will no longer repair tables that only had the open count wrong. @item Added functions to handle symbolic links to make life easier in 4.0. @item We are now using the @code{-lcma} thread library on HP-UX 10.20 so that MySQL will be more stable on HP-UX. @item Fixed problem with @code{IF()} and number of decimals in the result. @item Fixed date-part extraction functions to work with dates where day and/or month is 0. @item Extended argument length in option files from 256 to 512 chars. @item Fixed problem with shutdown when @code{INSERT DELAYED} was waiting for a @code{LOCK TABLE}. @item Fixed core dump bug in @code{InnoDB} when tablespace was full. @item Fixed problem with @code{MERGE} tables and big tables (> 4G) when using @code{ORDER BY}. @end itemize @node News-3.23.38, News-3.23.37, News-3.23.39, News-3.23.x @appendixsubsec Changes in release 3.23.38 (2001-05-09) @itemize @bullet @item Fixed a bug when @code{SELECT} from @code{MERGE} table sometimes results in incorrectly ordered rows. @item Fixed a bug in @code{REPLACE()} when using the @code{ujis} character set. @item Applied Sleepycat @code{BDB} patches 3.2.9.1 and 3.2.9.2. @item Added @code{--skip-stack-trace} option to @code{mysqld}. @item @code{CREATE TEMPORARY} now works with @code{InnoDB} tables. @item @code{InnoDB} now promotes sub keys to whole keys. @item Added option @code{CONCURRENT} to @code{LOAD DATA}. @item Better error message when slave @code{max_allowed_packet} is too low to read a very long log event from the master. @item Fixed bug when too many rows where removed when using @code{SELECT DISTINCT ... HAVING}. @item @code{SHOW CREATE TABLE} now returns @code{TEMPORARY} for temporary tables. @item Added @code{Rows_examined} to slow query log. @item Fixed problems with function returning empty string when used together with a group function and a @code{WHERE} that didn't match any rows. @item New program @code{mysqlcheck}. @item Added database name to output for administrative commands like @code{CHECK}, @code{REPAIR}, @code{OPTIMIZE}. @item Lots of portability fixes for @code{InnoDB}. @item Changed optimizer so that queries like @code{SELECT * FROM tbl_name,tbl_name2 ... ORDER BY key_part1 LIMIT #} will use index on @code{key_part1} instead of @code{filesort}. @item Fixed bug when doing @code{LOCK TABLE to_table WRITE,...; INSERT INTO to_table... SELECT ...} when @code{to_table} was empty. @item Fixed bug with @code{LOCK TABLE} and @code{BDB} tables. @end itemize @node News-3.23.37, News-3.23.36, News-3.23.38, News-3.23.x @appendixsubsec Changes in release 3.23.37 (2001-04-17) @itemize @bullet @item Fixed a bug when using @code{MATCH()} in @code{HAVING} clause. @item Fixed a bug when using @code{HEAP} tables with @code{LIKE}. @item Added @code{--mysql-version} option to @code{safe_mysqld} @item Changed @code{INNOBASE} to @code{InnoDB} (because the @code{INNOBASE} name was already used). All @code{configure} options and @code{mysqld} start options now use @code{innodb} instead of @code{innobase}. This means that before upgrading to this version, you have to change any configuration files where you have used @code{innobase} options! @item Fixed bug when using indexes on @code{CHAR(255) NULL} columns. @item Slave thread will now be started even if @code{master-host} is not set, as long as @code{server-id} is set and valid @file{master.info} is present. @item Partial updates (terminated with kill) are now logged with a special error code to the binary log. Slave will refuse to execute them if the error code indicates the update was terminated abnormally, and will have to be recovered with @code{SET SQL_SLAVE_SKIP_COUNTER=1; SLAVE START} after a manual sanity check/correction of data integrity. @item Fixed bug that erroneously logged a drop of internal temporary table on thread termination to the binary log -- this bug affected replication. @item Fixed a bug in @code{REGEXP} on 64-bit machines. @item @code{UPDATE} and @code{DELETE} with @code{WHERE unique_key_part IS NULL} didn't update/delete all rows. @item Disabled @code{INSERT DELAYED} for tables that support transactions. @item Fixed bug when using date functions on @code{TEXT}/@code{BLOB} column with wrong date format. @item UDFs now also work on Windows. (Patch by Ralph Mason.) @item Fixed bug in @code{ALTER TABLE} and @code{LOAD DATA INFILE} that disabled key-sorting. These commands should now be faster in most cases. @item Fixed performance bug where reopened tables (tables that had been waiting for @code{FLUSH} or @code{REPAIR}) would not use indexes for the next query. @item Fixed problem with @code{ALTER TABLE} to @code{InnoDB} tables on FreeBSD. @item Added @code{mysqld} variables @code{myisam_max_sort_file_size} and @code{myisam_max_extra_sort_file_size}. @item Initialise signals early to avoid problem with signals in @code{InnoDB}. @item Applied patch for the @code{tis620} character set to make comparisons case-independent and to fix a bug in @code{LIKE} for this character set. @strong{Note}: All tables that uses the @code{tis620} character set must be fixed with @code{myisamchk -r} or @code{REPAIR TABLE} ! @item Added @code{--skip-safemalloc} option to @code{mysqld}. @end itemize @node News-3.23.36, News-3.23.35, News-3.23.37, News-3.23.x @appendixsubsec Changes in release 3.23.36 (2001-03-27) @itemize @bullet @item Fixed a bug that allowed use of database names containing a @samp{.} character. This fixes a serious security issue when @code{mysqld} is run as root. @item Fixed bug when thread creation failed (could happen when doing a @strong{lot} of connections in a short time). @item Fixed some problems with @code{FLUSH TABLES} and @code{TEMPORARY} tables. (Problem with freeing the key cache and error @code{Can't reopen table...}.) @item Fixed a problem in @code{InnoDB} with other character sets than @code{latin1} and another problem when using many columns. @item Fixed bug that caused a core dump when using a very complex query involving @code{DISTINCT} and summary functions. @item Added @code{SET TRANSACTION ISOLATION LEVEL ...} @item Added @code{SELECT ... FOR UPDATE}. @item Fixed bug where the number of affected rows was not returned when MySQL was compiled without transaction support. @item Fixed a bug in @code{UPDATE} where keys weren't always used to find the rows to be updated. @item Fixed a bug in @code{CONCAT_WS()} where it returned incorrect results. @item Changed @code{CREATE ... SELECT} and @code{INSERT ... SELECT} to not allow concurrent inserts as this could make the binary log hard to repeat. (Concurrent inserts are enabled if you are not using the binary or update log.) @item Changed some macros to be able to use fast mutex with @code{glibc} 2.2. @end itemize @node News-3.23.35, News-3.23.34a, News-3.23.36, News-3.23.x @appendixsubsec Changes in release 3.23.35 (2001-03-15) @itemize @bullet @item Fixed newly introduced bug in @code{ORDER BY}. @item Fixed wrong define @code{CLIENT_TRANSACTIONS}. @item Fixed bug in @code{SHOW VARIABLES} when using @code{INNOBASE} tables. @item Setting and using user variables in @code{SELECT DISTINCT} didn't work. @item Tuned @code{SHOW ANALYZE} for small tables. @item Fixed handling of arguments in the benchmark script @code{run-all-tests}. @end itemize @node News-3.23.34a, News-3.23.34, News-3.23.35, News-3.23.x @appendixsubsec Changes in release 3.23.34a (2001-03-12) @itemize @bullet @item Added extra files to the distribution to allow @code{INNOBASE} support to be compiled. @end itemize @node News-3.23.34, News-3.23.33, News-3.23.34a, News-3.23.x @appendixsubsec Changes in release 3.23.34 (2001-03-10) @itemize @bullet @item Added the @code{INNOBASE} storage engine and the @code{BDB} storage engine to the MySQL source distribution. @item Updated the documentation about @code{GEMINI} tables. @item Fixed a bug in @code{INSERT DELAYED} that caused threads to hang when inserting @code{NULL} into an @code{AUTO_INCREMENT} column. @item Fixed a bug in @code{CHECK TABLE} / @code{REPAIR TABLE} that could cause a thread to hang. @item @code{REPLACE} will not replace a row that conflicts with an @code{AUTO_INCREMENT} generated key. @item @code{mysqld} now only sets @code{CLIENT_TRANSACTIONS} in @code{mysql->server_capabilities} if the server supports a transaction-safe storage engine. @item Fixed @code{LOAD DATA INFILE} to allow numeric values to be read into @code{ENUM} and @code{SET} columns. @item Improved error diagnostic for slave thread exit. @item Fixed bug in @code{ALTER TABLE ... ORDER BY}. @item Added @code{max_user_connections} variable to @code{mysqld}. @item Limit query length for replication by @code{max_allowed_packet}, not the arbitrary limit of 4 MB. @item Allow space around @code{=} in argument to @code{--set-variable}. @item Fixed problem in automatic repair that could leave some threads in state @code{Waiting for table}. @item @code{SHOW CREATE TABLE} now displays the @code{UNION()} for @code{MERGE} tables. @item @code{ALTER TABLE} now remembers the old @code{UNION()} definition. @item Fixed bug when replicating timestamps. @item Fixed bug in bidirectional replication. @item Fixed bug in the @code{BDB} storage engine that occurred when using an index on multi-part key where a key part may be @code{NULL}. @item Fixed @code{MAX()} optimization on sub-key for @code{BDB} tables. @item Fixed problem where garbage results were returned when using @code{BDB} tables and @code{BLOB} or @code{TEXT} fields when joining many tables. @item Fixed a problem with @code{BDB} tables and @code{TEXT} columns. @item Fixed bug when using a @code{BLOB} key where a const row wasn't found. @item Fixed that @code{mysqlbinlog} writes the timestamp value for each query. This ensures that one gets same values for date functions like @code{NOW()} when using @code{mysqlbinlog} to pipe the queries to another server. @item Allow @code{--skip-gemini}, @code{--skip-bdb}, and @code{--skip-innodb} options to be specified when invoking @code{mysqld}, even if these storage engines are not compiled in to @code{mysqld}. @item One can now do @code{GROUP BY ... DESC}. @item Fixed a deadlock in the @code{SET} code, when one ran @code{SET @@foo=bar}, where @code{bar} is a column reference, an error was not properly generated. @end itemize @node News-3.23.33, News-3.23.32, News-3.23.34, News-3.23.x @appendixsubsec Changes in release 3.23.33 (2001-02-09) @itemize @bullet @item Fixed DNS lookups not to use the same mutex as the hostname cache. This will enable known hosts to be quickly resolved even if a DNS lookup takes a long time. @item Added @code{--character-sets-dir} option to @code{myisampack}. @item Removed warnings when running @code{REPAIR TABLE ... EXTENDED}. @item Fixed a bug that caused a core dump when using @code{GROUP BY} on an alias, where the alias was the same as an existing column name. @item Added @code{SEQUENCE()} as an example UDF function. @item Changed @code{mysql_install_db} to use @code{BINARY} for @code{CHAR} columns in the privilege tables. @item Changed @code{TRUNCATE tbl_name} to @code{TRUNCATE TABLE tbl_name} to use the same syntax as Oracle. Until 4.0 we will also allow @code{TRUNCATE tbl_name} to not crash old code. @item Fixed ``no found rows'' bug in @code{MyISAM} tables when a @code{BLOB} was first part of a multi-part key. @item Fixed bug where @code{CASE} didn't work with @code{GROUP BY}. @item Added @code{--sort-recover} option to @code{myisamchk}. @item @code{myisamchk -S} and @code{OPTIMIZE TABLE} now work on Windows. @item Fixed bug when using @code{DISTINCT} on results from functions that referred to a group function, like: @example SELECT a, DISTINCT SEC_TO_TIME(SUM(a)) FROM tbl_name GROUP BY a, b; @end example @item Fixed buffer overrun in @code{libmysqlclient} library. Fixed bug in handling @code{STOP} event after @code{ROTATE} event in replication. @item Fixed another buffer overrun in @code{DROP DATABASE}. @item Added @code{Table_locks_immediate} and @code{Table_locks_waited} status variables. @item Fixed bug in replication that broke slave server start with existing @file{master.info}. This fixes a bug introduced in 3.23.32. @item Added @code{SET SQL_SLAVE_SKIP_COUNTER=n} command to recover from replication glitches without a full database copy. @item Added @code{max_binlog_size} variable; the binary log will be rotated automatically when the size crosses the limit. @item Added @code{Last_error}, @code{Last_errno}, and @code{Slave_skip_counter} variables to @code{SHOW SLAVE STATUS}. @item Fixed bug in @code{MASTER_POS_WAIT()} function. @item Execute core dump handler on @code{SIGILL}, and @code{SIGBUS} in addition to @code{SIGSEGV}. @item On x86 Linux, print the current query and thread (connection) id, if available, in the core dump handler. @item Fixed several timing bugs in the test suite. @item Extended @code{mysqltest} to take care of the timing issues in the test suite. @item @code{ALTER TABLE} can now be used to change the definition for a @code{MERGE} table. @item Fixed creation of @code{MERGE} tables on Windows. @item Portability fixes for OpenBSD and OS/2. @item Added @code{--temp-pool} option to @code{mysqld}. Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. This is to work around a problem in the Linux kernel dealing with creating a bunch of new files with different names. With the old behaviour, Linux seems to "leak" memory, as it's being allocated to the directory entry cache instead of the disk cache. @end itemize @node News-3.23.32, News-3.23.31, News-3.23.33, News-3.23.x @appendixsubsec Changes in release 3.23.32 (2001-01-22; Stable) @itemize @bullet @item Changed code to get around compiler bug in Compaq C++ on OSF/1, that broke @code{BACKUP}, @code{RESTORE}, @code{CHECK}, @code{REPAIR}, and @code{ANALYZE TABLE}. @item Added option @code{FULL} to @code{SHOW COLUMNS}. Now we show the privilege list for the columns only if this option is given. @item Fixed bug in @code{SHOW LOGS} when there weren't any @code{BDB} logs. @item Fixed a timing problem in replication that could delay sending an update to the client until a new update was done. @item Don't convert field names when using @code{mysql_list_fields()}. This is to keep this code compatible with @code{SHOW FIELDS}. @item @code{MERGE} tables didn't work on Windows. @item Fixed problem with @code{SET PASSWORD=...} on Windows. @item Added missing @file{my_config.h} to RPM distribution. @item @code{TRIM("foo" from "foo")} didn't return an empty string. @item Added @code{--with-version-suffix} option to @code{configure}. @item Fixed core dump when client aborted connection without @code{mysql_close()}. @item Fixed a bug in @code{RESTORE TABLE} when trying to restore from a non-existent directory. @item Fixed a bug which caused a core dump on the slave when replicating @code{SET PASSWORD}. @item Added @code{MASTER_POS_WAIT()}. @end itemize @node News-3.23.31, News-3.23.30, News-3.23.32, News-3.23.x @appendixsubsec Changes in release 3.23.31 (2001-01-17) @itemize @bullet @item The test suite now tests all reachable @code{BDB} interface code. During testing we found and fixed many errors in the interface code. @item Using @code{HAVING} on an empty table could produce one result row when it shouldn't. @item Fixed the MySQL RPM not to depend on Perl5 anymore. @item Fixed some problems with @code{HEAP} tables on Windows. @item @code{SHOW TABLE STATUS} didn't show correct average row length for tables larger than 4G. @item @code{CHECK TABLE ... EXTENDED} didn't check row links for fixed size tables. @item Added option @code{MEDIUM} to @code{CHECK TABLE}. @item Fixed problem when using @code{DECIMAL()} keys on negative numbers. @item @code{HOUR()} (and some other @code{TIME} functions) on a @code{CHAR} column always returned @code{NULL}. @item Fixed security bug in something (please upgrade if you are using an earlier MySQL 3.23 version). @item Fixed buffer overflow bug when writing a certain error message. @item Added usage of @code{setrlimit()} on Linux to get @code{-O --open-files-limit=#} to work on Linux. @item Added @code{bdb_version} variable to @code{mysqld}. @item Fixed bug when using expression of type: @example SELECT ... FROM t1 LEFT JOIN t2 ON (t1.a=t2.a) WHERE t1.a=t2.a @end example In this case the test in the @code{WHERE} clause was wrongly optimized away. @item Fixed bug in @code{MyISAM} when deleting keys with possible @code{NULL} values, but the first key-column was not a prefix-compressed text column. @item Fixed @code{mysql.server} to read the @code{[mysql.server]} option file group rather than the @code{[mysql_server]} group. @item Fixed @code{safe_mysqld} and @code{mysql.server} to also read the @code{server} option section. @item Added @code{Threads_created} status variable to @code{mysqld}. @end itemize @node News-3.23.30, News-3.23.29, News-3.23.31, News-3.23.x @appendixsubsec Changes in release 3.23.30 (2001-01-04) @itemize @bullet @item Added @code{SHOW OPEN TABLES} command. @item Fixed that @code{myisamdump} works against old @code{mysqld} servers. @item Fixed @code{myisamchk -k#} so that it works again. @item Fixed a problem with replication when the binary log file went over 2G on 32-bit systems. @item @code{LOCK TABLES} will now automatically start a new transaction. @item Changed @code{BDB} tables to not use internal subtransactions and reuse open files to get more speed. @item Added @code{--mysqld=#} option to @code{safe_mysqld}. @item Allow hex constants in the @code{--fields-*-by} and @code{--lines-terminated-by} options to @code{mysqldump} and @code{mysqlimport}. By Paul DuBois. @item Added @code{--safe-show-database} option to @code{mysqld}. @item Added @code{have_bdb}, @code{have_gemini}, @code{have_innobase}, @code{have_raid} and @code{have_openssl} to @code{SHOW VARIABLES} to make it easy to test for supported extensions. @item Added @code{--open-files-limit} option to @code{mysqld}. @item Changed @code{--open-files} option to @code{--open-files-limit} in @code{safe_mysqld}. @item Fixed a bug where some rows were not found with @code{HEAP} tables that had many keys. @item Fixed that @code{--bdb-no-sync} works. @item Changed @code{--bdb-recover} to @code{--bdb-no-recover} as recover should be on by default. @item Changed the default number of @code{BDB} locks to 10000. @item Fixed a bug from 3.23.29 when allocating the shared structure needed for @code{BDB} tables. @item Changed @code{mysqld_multi.sh} to use configure variables. Patch by Christopher McCrory. @item Added fixing of include files for Solaris 2.8. @item Fixed bug with @code{--skip-networking} on Debian Linux. @item Fixed problem that some temporary files where reported as having the name @code{UNOPENED} in error messages. @item Fixed bug when running two simultaneous @code{SHOW LOGS} queries. @end itemize @node News-3.23.29, News-3.23.28, News-3.23.30, News-3.23.x @appendixsubsec Changes in release 3.23.29 (2000-12-16) @itemize @bullet @item Configure updates for Tru64, large file support, and better TCP wrapper support. By Albert Chin-A-Young. @item Fixed bug in @code{<=>} operator. @item Fixed bug in @code{REPLACE} with @code{BDB} tables. @item @code{LPAD()} and @code{RPAD()} will shorten the result string if it's longer than the length argument. @item Added @code{SHOW LOGS} command. @item Remove unused @code{BDB} logs on shutdown. @item When creating a table, put @code{PRIMARY} keys first, followed by @code{UNIQUE} keys. @item Fixed a bug in @code{UPDATE} involving multi-part keys where one specified all key parts both in the update and the @code{WHERE} part. In this case MySQL could try to update a record that didn't match the whole @code{WHERE} part. @item Changed drop table to first drop the tables and then the @file{.frm} file. @item Fixed a bug in the hostname cache which caused @code{mysqld} to report the hostname as @code{''} in some error messages. @item Fixed a bug with @code{HEAP} type tables; the variable @code{max_heap_table_size} wasn't used. Now either @code{MAX_ROWS} or @code{max_heap_table_size} can be used to limit the size of a @code{HEAP} type table. @item Changed the default server-id to 1 for masters and 2 for slaves to make it easier to use the binary log. @item Renamed @code{bdb_lock_max} variable to @code{bdb_max_lock}. @item Added support for @code{AUTO_INCREMENT} on sub-fields for @code{BDB} tables. @item Added @code{ANALYZE} of @code{BDB} tables. @item In @code{BDB} tables, we now store the number of rows; this helps to optimise queries when we need an approximation of the number of rows. @item If we get an error in a multi-row statement, we now only roll back the last statement, not the entire transaction. @item If you do a @code{ROLLBACK} when you have updated a non-transactional table you will get an error as a warning. @item Added @code{--bdb-shared-data} option to @code{mysqld}. @item Added @code{Slave_open_temp_tables} status variable to @code{mysqld} @item Added @code{binlog_cache_size} and @code{max_binlog_cache_size} variables to @code{mysqld}. @item @code{DROP TABLE}, @code{RENAME TABLE}, @code{CREATE INDEX} and @code{DROP INDEX} are now transaction endpoints. @item If you do a @code{DROP DATABASE} on a symbolically linked database, both the link and the original database is deleted. @item Fixed @code{DROP DATABASE} to work on OS/2. @item Fixed bug when doing a @code{SELECT DISTINCT ... table1 LEFT JOIN table2 ...} when @code{table2} was empty. @item Added @code{--abort-slave-event-count} and @code{--disconnect-slave-event-count} options to @code{mysqld} for debugging and testing of replication. @item Fixed replication of temporary tables. Handles everything except slave server restart. @item @code{SHOW KEYS} now shows whether key is @code{FULLTEXT}. @item New script @code{mysqld_multi}. @xref{mysqld_multi, , @code{mysqld_multi}}. @item Added new script, @code{mysql-multi.server.sh}. Thanks to Tim Bunce @email{Tim.Bunce@@ig.co.uk} for modifying @code{mysql.server} to easily handle hosts running many @code{mysqld} processes. @item @code{safe_mysqld}, @code{mysql.server}, and @code{mysql_install_db} have been modified to use @code{mysql_print_defaults} instead of various hacks to read the @file{my.cnf} files. In addition, the handling of various paths has been made more consistent with how @code{mysqld} handles them by default. @item Automatically remove Berkeley DB transaction logs that no longer are in use. @item Fixed bug with several @code{FULLTEXT} indexes in one table. @item Added a warning if number of rows changes on @code{REPAIR}/@code{OPTIMIZE}. @item Applied patches for OS/2 by @code{Yuri Dario}. @item @code{FLUSH TABLES tbl_name} didn't always flush the index tree to disk properly. @item @code{--bootstrap} is now run in a separate thread. This fixes a problem that caused @code{mysql_install_db} to core dump on some Linux machines. @item Changed @code{mi_create()} to use less stack space. @item Fixed bug with optimiser trying to over-optimise @code{MATCH()} when used with @code{UNIQUE} key. @item Changed @code{crash-me} and the MySQL benchmarks to also work with FrontBase. @item Allow @code{RESTRICT} and @code{CASCADE} after @code{DROP TABLE} to make porting easier. @item Reset status variable which could cause problem if one used @code{--slow-log}. @item Added @code{connect_timeout} variable to @code{mysql} and @code{mysqladmin}. @item Added @code{connect-timeout} as an alias for @code{timeout} for option files read by @code{mysql_options()}. @end itemize @node News-3.23.28, News-3.23.27, News-3.23.29, News-3.23.x @appendixsubsec Changes in release 3.23.28 (2000-11-22; Gamma) @itemize @bullet @item Added new options @code{--pager[=...]}, @code{--no-pager}, @code{--tee=...} and @code{--no-tee} to the @code{mysql} client. The new corresponding interactive commands are @code{pager}, @code{nopager}, @code{tee} and @code{notee}. @xref{mysql, , @code{mysql}}, @code{mysql --help} and the interactive help for more information. @item Fixed crash when automatic repair of @code{MyISAM} table failed. @item Fixed a major performance bug in the table locking code when one constantly had a lot of @code{SELECT}, @code{UPDATE} and @code{INSERT} statements running. The symptom was that the @code{UPDATE} and @code{INSERT} queries were locked for a long time while new @code{SELECT} statements were executed before the updates. @item When reading @code{options_files} with @code{mysql_options()} the @code{return-found-rows} option was ignored. @item One can now specify @code{interactive-timeout} in the option file that is read by @code{mysql_options()}. This makes it possible to force programs that run for a long time (like @code{mysqlhotcopy}) to use the @code{interactive_timeout} time instead of the @code{wait_timeout} time. @item Added to the slow query log the time and the user name for each logged query. If you are using @code{--log-long-format} then also queries that do not use an index are logged, even if the query takes less than @code{long_query_time} seconds. @item Fixed a problem in @code{LEFT JOIN} which caused all columns in a reference table to be @code{NULL}. @item Fixed a problem when using @code{NATURAL JOIN} without keys. @item Fixed a bug when using a multi-part keys where the first part was of type @code{TEXT} or @code{BLOB}. @item @code{DROP} of temporary tables wasn't stored in the update/binary log. @item Fixed a bug where @code{SELECT DISTINCT * ... LIMIT #} only returned one row. @item Fixed a bug in the assembler code in @code{strstr()} for SPARC and cleaned up the @file{global.h} header file to avoid a problem with bad aliasing with the compiler submitted with RedHat 7.0. (Reported by Trond Eivind Glomsrd) @item The @code{--skip-networking} option now works properly on NT. @item Fixed a long outstanding bug in the @code{ISAM} tables when a row with a length of more than 65K was shortened by a single byte. @item Fixed a bug in @code{MyISAM} when running multiple updating processes on the same table. @item Allow one to use @code{FLUSH TABLE tbl_name}. @item Added @code{--replicate-ignore-table}, @code{--replicate-do-table}, @code{--replicate-wild-ignore-table}, and @code{--replicate-wild-do-table} options to @code{mysqld}. @item Changed all log files to use our own @code{IO_CACHE} mechanism instead of @code{FILE} to avoid OS problems when there are many files open. @item Added @code{--open-files} and @code{--timezone} options to @code{safe_mysqld}. @item Fixed a fatal bug in @code{CREATE TEMPORARY TABLE ... SELECT ...}. @item Fixed a problem with @code{CREATE TABLE ... SELECT NULL}. @item Added variables @code{large_file_support},@code{net_read_timeout}, @code{net_write_timeout} and @code{query_buffer_size} to @code{SHOW VARIABLES}. @item Added status variables @code{created_tmp_files} and @code{sort_merge_passes} to @code{SHOW STATUS}. @item Fixed a bug where we didn't allow an index name after the @code{FOREIGN KEY} definition. @item Added @code{TRUNCATE table_name} as a synonym for @code{DELETE FROM table_name}. @item Fixed a bug in a @code{BDB} key compare function when comparing part keys. @item Added @code{bdb_lock_max} variable to @code{mysqld}. @item Added more tests to the benchmark suite. @item Fixed an overflow bug in the client code when using overly long database names. @item @code{mysql_connect()} now aborts on Linux if the server doesn't answer in @code{timeout} seconds. @item @code{SLAVE START} did not work if you started with @code{--skip-slave-start} and had not explicitly run @code{CHANGE MASTER TO}. @item Fixed the output of @code{SHOW MASTER STATUS} to be consistent with @code{SHOW SLAVE STATUS}. (It now has no directory in the log name.) @item Added @code{PURGE MASTER LOGS TO}. @item Added @code{SHOW MASTER LOGS}. @item Added @code{--safemalloc-mem-limit} option to @code{mysqld} to simulate memory shortage when compiled with the @code{--with-debug=full} option. @item Fixed several core dumps in out-of-memory conditions. @item @code{SHOW SLAVE STATUS} was using an uninitialised mutex if the slave had not been started yet. @item Fixed bug in @code{ELT()} and @code{MAKE_SET()} when the query used a temporary table. @item @code{CHANGE MASTER TO} without specifying @code{MASTER_LOG_POS} would set it to 0 instead of 4 and hit the magic number in the master binlog. @item @code{ALTER TABLE ... ORDER BY ...} syntax added. This will create the new table with the rows in a specific order. @end itemize @node News-3.23.27, News-3.23.26, News-3.23.28, News-3.23.x @appendixsubsec Changes in release 3.23.27 (2000-10-24) @itemize @bullet @item Fixed a bug where the automatic repair of @code{MyISAM} tables sometimes failed when the datafile was corrupt. @item Fixed a bug in @code{SHOW CREATE} when using @code{AUTO_INCREMENT} columns. @item Changed @code{BDB} tables to use new compare function in Berkeley DB 3.2.3. @item You can now use Unix sockets with MIT-pthreads. @item Added the @code{latin5} (turkish) character set. @item Small portability fixes. @end itemize @node News-3.23.26, News-3.23.25, News-3.23.27, News-3.23.x @appendixsubsec Changes in release 3.23.26 (2000-10-18) @itemize @bullet @item Renamed @code{FLUSH MASTER} and @code{FLUSH SLAVE} to @code{RESET MASTER} and @code{RESET SLAVE}. @item Fixed @code{<>} to work properly with @code{NULL}. @item Fixed a problem with @code{SUBSTRING_INDEX()} and @code{REPLACE()}. (Patch by Alexander Igonitchev) @item Fix @code{CREATE TEMPORARY TABLE IF NOT EXISTS} not to produce an error if the table exists. @item If you don't create a @code{PRIMARY KEY} in a @code{BDB} table, a hidden @code{PRIMARY KEY} will be created. @item Added read-only-key optimisation to @code{BDB} tables. @item @code{LEFT JOIN} in some cases preferred a full table scan when there was no @code{WHERE} clause. @item When using @code{--log-slow-queries}, don't count the time waiting for a lock. @item Fixed bug in lock code on Windows which could cause the key cache to report that the key file was crashed even if it was okay. @item Automatic repair of @code{MyISAM} tables if you start @code{mysqld} with @code{--myisam-recover}. @item Removed the @code{TYPE=} keyword from @code{CHECK} and @code{REPAIR}. Allow @code{CHECK} options to be combined. (You can still use @code{TYPE=}, but this usage is deprecated.) @item Fixed mutex bug in the binary replication log -- long update queries could be read only in part by the slave if it did it at the wrong time, which was not fatal, but resulted in a performance-degrading reconnect and a scary message in the error log. @item Changed the format of the binary log -- added magic number, server version, binlog version. Added server id and query error code for each query event. @item Replication thread from the slave now will kill all the stale threads from the same server. @item Long replication user names were not being handled properly. @item Added @code{--replicate-rewrite-db} option to @code{mysqld}. @item Added @code{--skip-slave-start} option to @code{mysqld}. @item Updates that generated an error code (such as @code{INSERT INTO foo(some_key) values (1),(1)}) erroneously terminated the slave thread. @item Added optimization of queries where @code{DISTINCT} is only used on columns from some of the tables. @item Allow floating-point numbers where there is no sign after the exponent (like @code{1e1}). @item @code{SHOW GRANTS} didn't always show all column grants. @item Added @code{--default-extra-file=#} option to all MySQL clients. @item Columns referenced in @code{INSERT} statements now are initialised properly. @item @code{UPDATE} didn't always work when used with a range on a timestamp that was part of the key that was used to find rows. @item Fixed a bug in @code{FULLTEXT} index when inserting a @code{NULL} column. @item Changed to use @code{mkstemp()} instead of @code{tempnam()}. Based on a patch from John Jones. @end itemize @node News-3.23.25, News-3.23.24, News-3.23.26, News-3.23.x @appendixsubsec Changes in release 3.23.25 (2000-09-29) @itemize @bullet @item Fixed that @code{databasename} works as second argument to @code{mysqlhotcopy}. @item The values for the @code{UMASK} and @code{UMASK_DIR} environment variables now can be specified in octal by beginning the value with a zero. @item Added @code{RIGHT JOIN}. This makes @code{RIGHT} a reserved word. @item Added @code{@@@@IDENTITY} as a synonym for @code{LAST_INSERT_ID()}. (This is for MSSQL compatibility.) @item Fixed a bug in @code{myisamchk} and @code{REPAIR} when using @code{FULLTEXT} index. @item @code{LOAD DATA INFILE} now works with FIFOs. (Patch by Toni L. Harbaugh-Blackford.) @item @code{FLUSH LOGS} broke replication if you specified a log name with an explicit extension as the value of the @code{log-bin} option. @item Fixed a bug in @code{MyISAM} with packed multi-part keys. @item Fixed crash when using @code{CHECK TABLE} on Windows. @item Fixed a bug where @code{FULLTEXT} index always used the @code{koi8_ukr} character set. @item Fixed privilege checking for @code{CHECK TABLE}. @item The @code{MyISAM} repair/reindex code didn't use the @code{--tmpdir} option for its temporary files. @item Added @code{BACKUP TABLE} and @code{RESTORE TABLE}. @item Fixed core dump on @code{CHANGE MASTER TO} when the slave did not have the master to start with. @item Fixed incorrect @code{Time} in the processlist for @code{Connect} of the slave thread. @item The slave now logs when it connects to the master. @item Fixed a core dump bug when doing @code{FLUSH MASTER} if you didn't specify a filename argument to @code{--log-bin}. @item Added missing @file{ha_berkeley.x} files to the MySQL Windows distribution. @item Fixed some mutex bugs in the log code that could cause thread blocks if new log files couldn't be created. @item Added lock time and number of selected processed rows to slow query log. @item Added @code{--memlock} option to @code{mysqld} to lock @code{mysqld} in memory on systems with the @code{mlockall()} call (like in Solaris). @item @code{HEAP} tables didn't use keys properly. (Bug from 3.23.23.) @item Added better support for @code{MERGE} tables (keys, mapping, creation, documentation...). @xref{MERGE, , @code{MERGE}}. @item Fixed bug in @code{mysqldump} from 3.23 which caused some @code{CHAR} columns not to be quoted. @item Merged @code{analyze}, @code{check}, @code{optimize} and repair code. @item @code{OPTIMIZE TABLE} is now mapped to @code{REPAIR} with statistics and sorting of the index tree. This means that for the moment it only works on @code{MyISAM} tables. @item Added a pre-alloced block to root_malloc to get fewer mallocs. @item Added a lot of new statistics variables. @item Fixed @code{ORDER BY} bug with @code{BDB} tables. @item Removed warning that @code{mysqld} couldn't remove the @file{.pid} file under Windows. @item Changed @code{--log-isam} to log @code{MyISAM} tables instead of isam tables. @item Fixed @code{CHECK TABLE} to work on Windows. @item Added file mutexes to make @code{pwrite()} safe on Windows. @end itemize @node News-3.23.24, News-3.23.23, News-3.23.25, News-3.23.x @appendixsubsec Changes in release 3.23.24 (2000-09-08) @itemize @bullet @item Added @code{created_tmp_disk_tables} variable to @code{mysqld}. @item To make it possible to reliably dump and restore tables with @code{TIMESTAMP(X)} columns, MySQL now reports columns with @code{X} other than 14 or 8 to be strings. @item Changed sort order for @code{latin1} as it was before MySQL Version 3.23.23. Any table that was created or modified with 3.23.22 must be repaired if it has @code{CHAR} columns that may contain characters with ASCII values greater than 128! @item Fixed small memory leak introduced from 3.23.22 when creating a temporary table. @item Fixed problem with @code{BDB} tables and reading on a unique (not primary) key. @item Restored the @code{win1251} character set (it's now only marked deprecated). @end itemize @node News-3.23.23, News-3.23.22, News-3.23.24, News-3.23.x @appendixsubsec Changes in release 3.23.23 (2000-09-01) @itemize @bullet @item Changed sort order for 'German'; all tables created with 'German' sortorder must be repaired with @code{REPAIR TABLE} or @code{myisamchk} before use! @item Added @code{--core-file} option to @code{mysqld} to get a core file on Linux if @code{mysqld} dies on the @code{SIGSEGV} signal. @item MySQL クライアントの @code{mysql} は、デフォルトで @code{--no-named-commands} (@code{-g}) オプションで起動されるようになった。 このオプションは @code{--enable-named-commands} (@code{-G}) で無効にできる。 これはある場合に非互換の問題を引き起こすでしょう。たとえば、セミコロンなしで named コマンドを使用している SQL スクリプトなど！ Long format commands still work from the first line. @item Fixed a problem when using many pending @code{DROP TABLE} statements at the same time. @item Optimizer didn't use keys properly when using @code{LEFT JOIN} on an empty table. @item Added shorter help text when invoking @code{mysqld} with incorrect options. @item Fixed non-fatal @code{free()} bug in @code{mysqlimport}. @item Fixed bug in @code{MyISAM} index handling of @code{DECIMAL}/@code{NUMERIC} keys. @item Fixed a bug in concurrent insert in @code{MyISAM} tables. In some contexts, usage of @code{MIN(key_part)} or @code{MAX(key_part)} returned an empty set. @item Updated @code{mysqlhotcopy} to use the new @code{FLUSH TABLES table_list} syntax. Only tables which are being backed up are flushed now. @item @code{--enable-thread-safe-client} の振る舞いを変更。 非スレッド (@code{-lmysqlclient}) とスレッド (@code{-lmysqlclient_r}) ライブラリ の両方が作成されるため。 今までスレッド化された @code{-lmysqlclient} をリンクしていた場合には、 今後、@code{libmysqlclient_r} のリンクが必要となる。 @item Added atomic @code{RENAME TABLE} command. @item @code{COUNT(DISTINCT ...)} は @code{NULL} のエントリを数えない。 @item Changed @code{ALTER TABLE}, @code{LOAD DATA INFILE} on empty tables and @code{INSERT ... SELECT ...} on empty tables to create non-unique indexes in a separate batch with sorting. This will make the above calls much faster when you have many indexes. @item @code{ALTER TABLE} now logs the first used insert_id correctly. @item @code{BLOB} フィールドにデフォルト値を定義した場合にクラッシュしていたのを修正。 @item @code{DATE_ADD/DATE_SUB} が date でなく datetime を返していたバグを修正。 @item Fixed a problem with the thread cache which made some threads show up as @code{***DEAD***} in @code{SHOW PROCESSLIST}. @item Fixed a lock in our thr_rwlock code, which could make selects that run at the same time as concurrent inserts crash. This only affects systems that don't have the @code{pthread_rwlock_rdlock} code. @item When deleting rows with a non-unique key in a @code{HEAP} table, all rows weren't always deleted. @item Fixed bug in range optimiser for @code{HEAP} tables for searches on a part index. @item Fixed @code{SELECT} on part keys to work with @code{BDB} tables. @item Fixed @code{INSERT INTO bdb_table ... SELECT} to work with @code{BDB} tables. @item @code{CHECK TABLE} now updates key statistics for the table. @item @code{ANALYZE TABLE} will now only update tables that have been changed since the last @code{ANALYZE}. Note that this is a new feature and tables will not be marked to be analysed until they are updated in any way with 3.23.23 or newer. For older tables, you have to do @code{CHECK TABLE} to update the key distribution. @item Fixed some minor privilege problems with @code{CHECK}, @code{ANALYZE}, @code{REPAIR} and @code{SHOW CREATE} commands. @item @code{CHANGE MASTER TO} コマンドの追加。 @item Added @code{FAST}, @code{QUICK} @code{EXTENDED} check types to @code{CHECK TABLES}. @item Changed @code{myisamchk} so that @code{--fast} and @code{--check-only-changed} are also honored with @code{--sort-index} and @code{--analyze}. @item @code{LOAD TABLE FROM MASTER} がインデックスを再構築している間にテーブルを ロックしなかったバグを修正。 @item もしデータベースがレプリケーション対象外の場合に @code{LOAD DATA INFILE} を 行うと、レプリケーションを壊していたのを修正。 @item More variables in @code{SHOW SLAVE STATUS} and @code{SHOW MASTER STATUS}. @item @code{SLAVE STOP} now will not return until the slave thread actually exits. @item @code{MATCH} 関数を利用した Full-text search と @code{FULLTEXT} インデックスの追加。 (MyISAM でのみ利用可能)。 これにより @code{FULLTEXT} が予約語になる。 @end itemize @node News-3.23.22, News-3.23.21, News-3.23.23, News-3.23.x @appendixsubsec Changes in release 3.23.22 (2000-07-31) @itemize @bullet @item Fixed that @code{lex_hash.h} is created properly for each MySQL distribution. @item Fixed that @code{MASTER} and @code{COLLECTION} are not reserved words. @item The log generated by @code{--slow-query-log} didn't contain the whole queries. @item Fixed that open transactions in @code{BDB} tables are rolled back if the connection is closed unexpectedly. @item Added workaround for a bug in @code{gcc} 2.96 (intel) and @code{gcc} 2.9 (IA64) in @code{gen_lex_hash.c}. @item @file{my.cnf} ファイルで @code{host=} を使用した場合、 クライアントライブラリにメモリリークがあったのを修正した。 @item Optimized functions that manipulate the hours/minutes/seconds. @item Fixed bug when comparing the result of @code{DATE_ADD()}/@code{DATE_SUB()} against a number. @item Changed the meaning of @code{-F, --fast} for @code{myisamchk}. Added @code{-C, --check-only-changed} option to @code{myisamchk}. @item Added @code{ANALYZE tbl_name} to update key statistics for tables. @item Changed binary items @code{0x...} to be regarded as integers by default. @item Fix for SCO and @code{SHOW PROCESSLIST}. @item Added @code{auto-rehash} on reconnect for the @code{mysql} client. @item @code{MyISAM} の インデックスファイルが 64M bytes を超えれないバグを修正した。 3.23.21 でエンバグした。 @item @code{SHOW MASTER STATUS} と @code{SHOW SLAVE STATUS} の追加。 @end itemize @node News-3.23.21, News-3.23.20, News-3.23.22, News-3.23.x @appendixsubsec Changes in release 3.23.21 (2000-07-05) @itemize @bullet @item MySQL C API に @code{mysql_character_set_name()} 関数を追加。 @item Made the update log ASCII 0 safe. @item @code{mysql_config} スクリプトの追加。 @item Fixed problem when using @code{<} or @code{>} with a char column that was only partly indexed. @item One would get a core dump if the log file was not readable by the MySQL user. @item @code{mysqladmin} を、API コールしていたかわりに、 @code{CREATE DATABASE}/@code{DROP DATABASE} コマンドを 使用するように変更した。 @item Fixed @code{chown} warning in @code{safe_mysqld}. @item @code{ORDER BY} のバグを修正。 3.23.19 でエンバグした。 @item Only optimize the @code{DELETE FROM tbl_name} to do a drop+create of the table if we are in @code{AUTOCOMMIT} mode (needed for @code{BDB} tables). @item Added extra checks to avoid index corruption when the @code{ISAM}/@code{MyISAM} index files get full during an @code{INSERT}/@code{UPDATE}. @item @code{myisamchk} didn't correctly update row checksum when used with @code{-ro} (this only gave a warning in subsequent runs). @item Fixed bug in @code{REPAIR TABLE} so that it works with tables without indexes. @item Fixed buffer overrun in @code{DROP DATABASE}. @item @code{LOAD TABLE FROM MASTER} is sufficiently bug-free to announce it as a feature. @item @code{MATCH} と @code{AGAINST} が予約語になった。 @end itemize @node News-3.23.20, News-3.23.19, News-3.23.21, News-3.23.x @appendixsubsec Changes in release 3.23.20 @itemize @bullet @item 3.23.19 のバグを修正した; @code{DELETE FROM tbl_name} が @file{.frm} ファイルを消してしまっていた。 @item Added @code{SHOW CREATE TABLE}. @end itemize @node News-3.23.19, News-3.23.18, News-3.23.20, News-3.23.x @appendixsubsec Changes in release 3.23.19 @itemize @bullet @item 全てのファイルのコピライトの変更。 サーバーとユーティリティのコードは GPL に, クライアントライブラリは LGPL に。 @item Fixed bug where all rows matching weren't updated on a @code{MyISAM} table when doing update based on key on a table with many keys and some key changed values. @item The Linux MySQL RPM's and binaries are now statically linked with a linuxthread version that has faster mutex handling when used with MySQL. @item @code{ORDER BY} can now use @code{REF} keys to find subsets of the rows that need to be sorted. @item @code{print_defaults} の名前を @code{my_print_defaults} に変更。 名前の衝突をさけるため。 @item Fixed @code{NULLIF()} to work according to ANSI SQL99. @item @code{net_read_timeout} と @code{net_write_timeout} を @code{mysqld} の起動時のパラメタとして追加。 @item Fixed bug that destroyed index when doing @code{myisamchk --sort-records} on a table with prefix compressed index. @item @code{pack_isam} と @code{myisampack} を MySQL の標準配布に追加。 @item Added the syntax @code{BEGIN WORK} (the same as @code{BEGIN}). @item Fixed core dump bug when using @code{ORDER BY} on a @code{CONV()} expression. @item Added @code{LOAD TABLE FROM MASTER} @item Added @code{FLUSH MASTER} and @code{FLUSH SLAVE} @item Fixed big/little endian problem in the replication @end itemize @node News-3.23.18, News-3.23.17, News-3.23.19, News-3.23.x @appendixsubsec Changes in release 3.23.18 (2000-06-15) @itemize @bullet @item Fixed a problem from 3.23.17 when choosing character set on the client side. @item Added @code{FLUSH TABLES WITH READ LOCK} to make a global lock suitable for making a copy of MySQL datafiles. @item @code{CREATE TABLE ... SELECT ... PROCEDURE} now works. @item Internal temporary tables will now use compressed index when using @code{GROUP BY} on @code{VARCHAR/CHAR} columns. @item Fixed a problem when locking the same table with both a @code{READ} and a @code{WRITE} lock. @item Fixed problem with @code{myisamchk} and @code{RAID} tables. @end itemize @node News-3.23.17, News-3.23.16, News-3.23.18, News-3.23.x @appendixsubsec Changes in release 3.23.17 @itemize @bullet @item Fixed a bug in @code{FIND_IN_SET()} when the first argument was @code{NULL}. @item Added table locks to Berkeley DB. @item Fixed a bug with @code{LEFT JOIN} and @code{ORDER BY} where the first table had only one matching row. @item Added 4 sample @file{my.cnf} example files in the @file{support-files} directory. @item Fixed @code{duplicated key} problem when doing big @code{GROUP BY} operations. (This bug was probably introduced in 3.23.15.) @item @code{INNER JOIN} の文法を ANSI SQL にマッチさせた. @item @code{NATURAL JOIN} 構文を追加. @item A lot of fixes in the @code{BDB} interface. @item Added handling of @code{--no-defaults} and @code{--defaults-file} to @code{safe_mysqld.sh} and @code{mysql_install_db.sh}. @item Fixed bug in reading compressed tables with many threads. @item Fixed that @code{USE INDEX} works with @code{PRIMARY} keys. @item Added @code{BEGIN} statement to start a transaction in @code{AUTOCOMMIT} mode. @item シンボリックリンクを Windows 上でサポート. @item Changed protocol to let client know if the server is in @code{AUTOCOMMIT} mode and if there is a pending transaction. If there is a pending transaction, the client library will give an error before reconnecting to the server to let the client know that the server did a rollback. The protocol is still backward-compatible with old clients. @item @code{KILL} now works on a thread that is locked on a 'write' to a dead client. @item Fixed memory leak in the replication slave thread. @item Added new @code{log-slave-updates} option to @code{mysqld}, to allow daisy-chaining the slaves. @item Fixed compile error on FreeBSD and other systems where @code{pthread_t} is not the same as @code{int}. @item Fixed master shutdown aborting the slave thread. @item Fixed a race condition in @code{INSERT DELAYED} code when doing @code{ALTER TABLE}. @item Added deadlock detection sanity checks to @code{INSERT DELAYED}. @end itemize @node News-3.23.16, News-3.23.15, News-3.23.17, News-3.23.x @appendixsubsec Changes in release 3.23.16 @itemize @bullet @item Added @code{SLAVE START} and @code{SLAVE STOP} statements. @item @code{TYPE=QUICK} オプションを @code{CHECK} と @code{REPAIR} に追加。 @item Fixed bug in @code{REPAIR TABLE} when the table was in use by other threads. @item Added a thread cache to make it possible to debug MySQL with @code{gdb} when one does a lot of reconnects. This will also improve systems where you can't use persistent connections. @item Berkeley DB インターフェースの多くを修正。 @item @code{UPDATE IGNORE} will not abort if an update results in a @code{DUPLICATE_KEY} error. @item Put @code{CREATE TEMPORARY TABLE} commands in the update log. @item Fixed bug in handling of masked IP numbers in the privilege tables. @item Fixed bug with @code{delay_key_write} tables and @code{CHECK TABLE}. @item Added @code{replicate-do-db} and @code{replicate-ignore-db} options to @code{mysqld}, to restrict which databases get replicated. @item @code{SQL_LOG_BIN} オプションを追加。 @end itemize @node News-3.23.15, News-3.23.14, News-3.23.16, News-3.23.x @appendixsubsec Changes in release 3.23.15 (2000-05-10; Beta) @itemize @bullet @item To start @code{mysqld} as @code{root} one must now use the @code{--user=root} option. @item Added interface to Berkeley DB. (This is not yet functional; play with it at your own risk!) @item マスターとスレーブ間での複製機能を追加。 @item Fixed bug that other threads could steal a lock when a thread had a lock on a table and did a @code{FLUSH TABLES} command. @item Added the @code{slow_launch_time} variable and the @code{Slow_launch_threads} status variable to @code{mysqld}. These can be examined with @code{mysqladmin variables} and @code{mysqladmin extended-status}. @item Added functions @code{INET_NTOA()} and @code{INET_ATON()}. @item The default type of @code{IF()} now depends on the second and third arguments and not only on the second argument. @item Fixed case when @code{myisamchk} could go into a loop when trying to repair a crashed table. @item Don't write @code{INSERT DELAYED} to update log if @code{SQL_LOG_UPDATE=0}. @item Fixed problem with @code{REPLACE} on @code{HEAP} tables. @item Added possible character sets and time zone to @code{SHOW VARIABLES} output. @item Fixed bug in locking code that could result in locking problems with concurrent inserts under high load. @item Fixed a problem with @code{DELETE} of many rows on a table with compressed keys where MySQL scanned the index to find the rows. @item Fixed problem with @code{CHECK} on table with deleted keyblocks. @item Fixed a bug in reconnect (at the client side) where it didn't free memory properly in some contexts. @item Fixed problems in update log when using @code{LAST_INSERT_ID()} to update a table with an @code{AUTO_INCREMENT} key. @item Added @code{NULLIF()} function. @item Fixed bug when using @code{LOAD DATA INFILE} on a table with @code{BLOB/TEXT} columns. @item Optimised @code{MyISAM} to be faster when inserting keys in sorted order. @item @code{EXPLAIN SELECT ...} now also prints out whether MySQL needs to create a temporary table or use file sorting when resolving the @code{SELECT}. @item Added optimization to skip @code{ORDER BY} parts where the part is a constant expression in the @code{WHERE} part. Indexes can now be used even if the @code{ORDER BY} doesn't match the index exactly, as long as all the unused index parts and all the extra @code{ORDER BY} columns are constants in the @code{WHERE} clause. @xref{MySQL indexes}. @item @code{UPDATE} and @code{DELETE} on a whole unique key in the @code{WHERE} part are now faster than before. @item Changed @code{RAID_CHUNKSIZE} to be in 1024-byte increments. @item Fixed core dump in @code{LOAD_FILE(NULL)}. @end itemize @node News-3.23.14, News-3.23.13, News-3.23.15, News-3.23.x @appendixsubsec Changes in release 3.23.14 (2000-04-10) @itemize @bullet @item Added @code{mysql_real_escape_string()} function to the MySQL C API. @item Fixed a bug in @code{CONCAT()} where one of the arguments was a function that returned a modified argument. @item @code{myisamchk} の致命的なバグを修正した。 このバグはインデックスファイル中の ヘッダーを、テーブルをチェックしているだけなのにもかかわらず、更新していた。 This confused the @code{mysqld} daemon if it updated the same table at the same time. Now the status in the index file is only updated if one uses @code{--update-state}. With older @code{myisamchk} versions you shoul use @code{--read-only} when only checking tables, if there is the slightest chance that the @code{mysqld} server is working on the table at the same time! @item Fixed that @code{DROP TABLE} is logged in the update log. @item Fixed problem when searching on @code{DECIMAL()} key field where the column data contained leading zeros. @item auto_increment が最初のキーでない場合の @code{myisamchk} のバグを修正。 @item Allow @code{DATETIME} in ISO8601 format: 2000-03-12T12:00:00 @item 動的キャラクタセット。 １個の @code{mysqld} バイナリで、多くの違う キャラクタセットを扱えるようになった。 (@code{mysqld} スタート時に指定できます). @item @code{REPAIR TABLE} コマンドを追加。 @item @code{mysql_thread_safe()} C API 関数を追加。 @item @code{UMASK_DIR} 環境変数を追加。 @item @code{CONNECTION_ID()} 関数を追加 @item When using @code{=} on @code{BLOB} or @code{VARCHAR BINARY} keys, where only a part of the column was indexed, the whole column of the result row wasn't compared. @item @code{sjis} キャラクターセットの @code{ORDER BY} の問題を修正 @item When running in ANSI mode, don't allow columns to be used that aren't in the @code{GROUP BY} part. @end itemize @node News-3.23.13, News-3.23.12, News-3.23.14, News-3.23.x @appendixsubsec Changes in release 3.23.13 @itemize @bullet @item Fixed problem when doing locks on the same table more than 2 times in the same @code{LOCK TABLE} command; this fixed the problem one got when running the test-ATIS test with @code{--fast} or @code{--check-only-changed}. @item @code{SQL_BUFFER_RESULT} オプションを @code{SELECT} に追加 @item Removed end space from double/float numbers in results from temporary tables. @item @code{CHECK TABLE} コマンドの追加。 @item Added changes for @code{MyISAM} in 3.23.12 that didn't get into the source distribution because of CVS problems. @item Fixed bug so that @code{mysqladmin shutdown} will wait for the local server to close down. @item Fixed a possible endless loop when calculating timestamp. @item Added @code{print_defaults} program to the @file{.rpm} files. Removed @code{mysqlbug} from the client @file{.rpm} file. @end itemize @node News-3.23.12, News-3.23.11, News-3.23.13, News-3.23.x @appendixsubsec Changes in release 3.23.12 (07 Mar 2000) @itemize @bullet @item Fixed bug in @code{MyISAM} involving @code{REPLACE ... SELECT ...} which could give a corrupted table. @item Fixed bug in @code{myisamchk} where it incorrectly reset the @code{AUTO_INCREMENT} value. @item Linux Alpha 用に多くのパッチを追加. MySQL now appears to be relatively stable on Alpha. @item 重複したレコードを速く見つけるためのハッシュ化されたキーを使用するために、 @code{HEAP} 一時テーブル上の @code{DISTINCT} を変更した。 This mostly concerns queries of type @code{SELECT DISTINCT ... GROUP BY ...}. This fixes a problem where not all duplicates were removed in queries of the above type. 新しく追加したコードは、とても速い。 @item MacOS X で MySQL をコンパイルできるようになるパッチの追加 @item オプション @code{IF NOT EXISTS} を @code{CREATE DATABASE} に追加. @item 多くのデータベースを同時にダンプできるように、 @code{--all-databases} と @code{--databases} オプションを @code{mysqldump} に追加。 @item @code{MyISAM} 型テーブル中の圧縮した @code{DECIMAL()} インデックスのバグを修正した。 @item 0 を timestamp に保存したときのバグを修正した。 @item ローカルの接続で @code{mysqladmin shutdown} を実行した場合に、@code{mysqladmin} は 終了前に pidfile が無くなるまで待つようになった。 @item いくつかの @code{COUNT(DISTINCT ...)} クエリでコアを吐いたのを修正した。 @item Fixed that @code{myisamchk} works properly with RAID tables. @item Fixed problem with @code{LEFT JOIN} and @code{key_field IS NULL}. @item Fixed bug in @code{net_clear()} which could give the error @code{Aborted connection} in the MySQL clients. @item Added options @code{USE INDEX (key_list)} and @code{IGNORE INDEX (key_list)} as parameters in @code{SELECT}. @item @code{DELETE} and @code{RENAME} should now work on @code{RAID} tables. @end itemize @node News-3.23.11, News-3.23.10, News-3.23.12, News-3.23.x @appendixsubsec Changes in release 3.23.11 @itemize @bullet @item @code{ALTER TABLEL tbl_name ADD (field_list)} 文を許可した。 @item Fixed problem with optimiser that could sometimes use incorrect keys. @item @code{GRANT/REVOKE ALL PRIVILEGES} が @code{GRANT OPTION} に影響しなかったのを修正。 @item Removed extra @samp{)} from the output of @code{SHOW GRANTS}. @item Fixed problem when storing numbers in timestamps. @item Fix problem with timezones that have half hour offsets. @item @code{CREATE} 文での @code{UNIQUE INDEX} の使用を許可。 @item @code{mysqlhotcopy} - ローカルの MySQL データベースをバックアップする ツール。 By Tim Bunce. @item 新しい @code{mysqlaccess}. Thanks to Steve Harvey for this. @item @code{--i-am-a-dummy} と @code{--safe-updates} オプションを @code{mysql} に追加。 @item @code{select_limit} と @code{max_join_size} 変数を @code{mysql} に追加。 @item SQL の変数を追加： @code{SQL_MAX_JOIN_SIZE} と @code{SQL_SAFE_UPDATES}. @item Added @code{READ LOCAL} lock that doesn't lock the table for concurrent inserts. (This is used by @code{mysqldump}.) @item Changed that @code{LOCK TABLES ... READ} doesn't anymore allow concurrent inserts. @item オプション @code{--skip-delay-key-write} を @code{mysqld} に追加。 @item Fixed security problem in the protocol regarding password checking. @item @code{_rowid} can now be used as an alias for an integer type unique indexed column. @item Added back blocking of @code{SIGPIPE} when compiling with @code{--thread-safe-clients} to make things safe for old clients. @end itemize @node News-3.23.10, News-3.23.9, News-3.23.11, News-3.23.x @appendixsubsec Changes in release 3.23.10 @itemize @bullet @item Fixed bug in 3.23.9 where memory wasn't properly freed when using @code{LOCK TABLES}. @end itemize @node News-3.23.9, News-3.23.8, News-3.23.10, News-3.23.x @appendixsubsec Changes in release 3.23.9 @itemize @bullet @item Fixed problem that affected queries that did arithmetic on group functions. @item Fixed problem with timestamps and @code{INSERT DELAYED}. @item Fixed that @code{date_col BETWEEN const_date AND const_date} works. @item Fixed problem when only changing a 0 to @code{NULL} in a table with @code{BLOB/TEXT} columns. @item Fixed bug in range optimizer when using many key parts and or on the middle key parts: @code{WHERE K1=1 and K3=2 and (K2=2 and K4=4 or K2=3 and K4=5)} @item @code{source} コマンドを @code{mysql} に追加。 これは @code{mysql} クライアント内 で、バッチファイルを読むことができる。 Original patch by Matthew Vanecek. @item @code{WITH GRANT OPTION} オプションの致命的なバグを修正 @item Don't give an unnecessary @code{GRANT} error when using tables from many databases in the same query. @item Added VIO wrapper (needed for SSL support; by Andrei Errapart and Tnu Samuel). @item Fixed optimizer problem on @code{SELECT} when using many overlapping indexes. MySQL should now be able to choose keys even better when there are many keys to choose from. @item Changed optimizer to prefer a range key instead of a ref key when the range key can uses more columns than the ref key (which only can use columns with =). For example, the following type of queries should now be faster: @code{SELECT * from key_part_1=const and key_part_2 > const2} @item Fixed bug that a change of all @code{VARCHAR} columns to @code{CHAR} columns didn't change row type from dynamic to fixed. @item Disabled floating-point exceptions for FreeBSD to fix core dump when doing @code{SELECT FLOOR(POW(2,63))}. @item @code{mysqld} の起動オプション @code{--delay-key-write} を @code{--delay-key-write-for-all-tables} に変更 @item Added @code{read-next-on-key} to @code{HEAP} tables. This should fix all problems with @code{HEAP} tables when using non-@code{UNIQUE} keys. @item 変数のデフォルトを表示するオプションをクライアントに追加 @item @code{mysqld} に @code{--log-slow-queries} を追加。 これは時間のかかった 全てのクエリを別のログファイルに記録する。どのくらい時間がかかったかが記される @item @code{WHERE key_column=RAND(...)} を行ったときコアを吐くバグを修正 @item Fixed optimisation bug in @code{SELECT ... LEFT JOIN ... key_col IS NULL}, when @code{key_col} could contain @code{NULL} values. @item Fixed problem with 8-bit characters as separators in @code{LOAD DATA INFILE}. @end itemize @node News-3.23.8, News-3.23.7, News-3.23.9, News-3.23.x @appendixsubsec Changes in release 3.23.8 (02 Jan 2000) @itemize @bullet @item 8G より大きなインデックスファイルを扱った場合の問題を修正。 @item NetBSD 用の最新の mit-pthread のパッチを追加。 @item タイムゾーン < GMT - 11 の場合の問題を修正。 @item @code{NISAM} 中のパックされたキーの削除時のバグを修正。 @item いくつか @code{ORDER BY ... DESC} クエリを実行した際の @code{ISAM} の問題を修正。 @item Fixed bug when doing a join on a text key which didn't covert the whole key. @item オプション @code{--delay-key-write} が delayed key writing を有効にしていなかったのを修正。 @item Fixed update of @code{TEXT} column which involved only case changes. @item Fixed that @code{INSERT DELAYED} doesn't update timestamps that are given. @item @code{YEARWEEK()} 関数の追加と、@code{x}, @code{X}, @code{v}, @code{V} オプションの @code{DATE_FORMAT()} への追加。 @item Fixed problem with @code{MAX(indexed_column)} and @code{HEAP} tables. @item Fixed problem with @code{BLOB NULL} keys and @code{LIKE "prefix%"}. @item Fixed problem with @code{MyISAM} and fixed-length rows < 5 bytes. @item Fixed problem that could cause MySQL to touch freed memory when doing very complicated @code{GROUP BY} queries. @item Fixed core dump if you got a crashed table where an @code{ENUM} field value was too big. @end itemize @node News-3.23.7, News-3.23.6, News-3.23.8, News-3.23.x @appendixsubsec Changes in release 3.23.7 (10 Dec 1999) @itemize @bullet @item Linux環境下において、@code{pthread_mutex_timedwait} の問題を避けるようにした。 この関数は @code{INSERT DELAYED} で使用されていた。 @xref{Linux}. @item Fixed that one will get at 'disk full' error message if one gets disk full when doing sorting (instead of waiting until we got more disk space). @item @code{MyISAM} で、キーが 250 文字を超えた場合のバグを修正。 @item @code{MyISAM} において、他のスレッドが読んでいるテーブルに対し、 他のスレッドが @code{INSERT} を同時に行うことができるようになった。 @item Added @code{max_write_lock_count} variable to @code{mysqld} to force a @code{READ} lock after a certain number of @code{WRITE} locks. @item Inverted flag @code{delay_key_write} on @code{show variables}. @item @code{concurrency} 変数を @code{thread_concurrency} に改名。 @item 以下の関数がマルチバイト・セーフになった： @code{LOCATE(substr,str)}, @code{POSITION(substr IN str)}, @code{LOCATE(substr,str,pos)}, @code{INSTR(str,substr)}, @code{LEFT(str,len)}, @code{RIGHT(str,len)}, @code{SUBSTRING(str,pos,len)}, @code{SUBSTRING(str FROM pos FOR len)}, @code{MID(str,pos,len)}, @code{SUBSTRING(str,pos)}, @code{SUBSTRING(str FROM pos)}, @code{SUBSTRING_INDEX(str,delim,count)}, @code{RTRIM(str)}, @code{TRIM([[BOTH | TRAILING] [remstr] FROM] str)}, @code{REPLACE(str,from_str,to_str)}, @code{REVERSE(str)}, @code{INSERT(str,pos,len,newstr)}, @code{LCASE(str)}, @code{LOWER(str)}, @code{UCASE(str)} and @code{UPPER(str)}; patch by Wei He. @item Fix core dump when releasing a lock from a non-existent table. @item Remove locks on tables before starting to remove duplicates. @item @code{FULL} オプションを @code{SHOW PROCESSLIST} に追加。 @item @code{--verbose} オプションを @code{mysqladmin} に追加。 @item @code{HEAP} の @code{MyISAM} への自動変換時のバグを修正。 @item @code{HEAP} テーブルに対して、insert + delete + insert + scan table を行った際の バグを修正。 @item Alpha プラットフォーム上での、@code{REPLACE()} と @code{LOAD DATA INFILE} のバグを修正。 @item @code{mysqld} 変数に @code{interactive_timeout} を追加. @item @code{mysql_data_seek()} の引数を @code{ulong} から @code{ulonglong} に 変更. @end itemize @node News-3.23.6, News-3.23.5, News-3.23.7, News-3.23.x @appendixsubsec Changes in release 3.23.6 @itemize @bullet @item @code{mysqld} に @code{-O lower_case_table_names=@{0|1@}} オプションを追加。 これはテーブル名を強制的に小文字にします。 @item @code{SELECT ... INTO DUMPFILE} 追加。 @item @code{mysqld} に @code{--ansi} オプションを追加。 これはいくつかの関数を @code{ANSI SQL} 互換にします。 @item Temporary table names now start with @code{#sql}. @item Added quoting of identifiers with @code{`} (@code{"} in @code{--ansi} mode). @item Changed to use @code{snprintf()} when printing floats to avoid some buffer overflows on FreeBSD. @item FreeBSD 上で、@code{FLOOR()} をオーバーフローセーフにした。 @item @code{--quote-names} オプションを @code{mysqldump} に追加 @item Fixed bug that one could make a part of a @code{PRIMARY KEY NOT NULL}. @item Fixed @code{encrypt()} to be thread-safe and not reuse buffer. @item MyODBC の @code{mysql_odbc_escape_string()} 関数が、big5 をサポートした。 @item Rewrote the storage engine to use classes. This introduces a lot of new code, but will make table handling faster and better. @item ユーザー定義変数のパッチ(Sashaによる)を追加。 @item Changed that @code{FLOAT} and @code{DOUBLE} (without any length modifiers) no longer are fixed decimal point numbers. @item @code{FLOAT(X)} の意味を変更: @code{X} <=24 ならば、これは @code{FLOAT} と同じで、 24 < @code{X} <= 53 であるならば @code{DOUBLE} と同じになります。 @item @code{DECIMAL(X)} は @code{DECIMAL(X,0)} のエイリアスになりました。 また @code{DECIMAL} は @code{DECIMAL(10,0)} のエイリアスになりました。 The same goes for @code{NUMERIC}. @item @code{ROW_FORMAT=@{default | dynamic | fixed | compressed@}} オプションを @code{CREATE_TABLE} に追加. @item @code{DELETE FROM table_name} が一時テーブルで動かなかった。 @item @code{CHAR_LENGTH()} 関数をマルチバイトセーフに変更 @item @code{ORD(string)} 関数の追加. @end itemize @node News-3.23.5, News-3.23.4, News-3.23.6, News-3.23.x @appendixsubsec Changes in release 3.23.5 (20 Oct 1999) @itemize @bullet @item 新しいデータハンドリング中のいくつかの Y2K 問題を修正。 @item @code{SELECT DISTINCT ... ORDER BY RAND()} の問題を修正。 @item Sergei A. Golubchik による @code{MyISAM} のレベルでのテキストサーチのパッチを追加 @item キー無しでfull JOIN を使用した際のキャッシュオーバーフローの問題を修正。 @item いくつかの configure の問題を修正。 @item Some small changes to make parsing faster. @item Adding a column after the last field with @code{ALTER TABLE} didn't work. @item 2つのキー中でauto_incrementフィールドを使用したときの問題を修正。 @item @code{MyISAM} で auto_increment をサブパートとして使用できるようになった： @code{CREATE TABLE foo (a INT NOT NULL AUTO_INCREMENT, b CHAR(5), PRIMARY KEY (b,a))} @item Fixed bug in @code{MyISAM} with packed char keys that could be @code{NULL}. @item フィールド名を @code{CREATE TABLE table_name SELECT ... } 時にとした場合、動かなかった。 @item Allow use of @code{NATIONAL} and @code{NCHAR} when defining character columns. This is the same as not using @code{BINARY}. @item @code{NULL} のフィールドを @code{PRIMARY KEY} ( @code{UNIQUE} キー) には 許さなくなった。 @item Clear @code{LAST_INSERT_ID()} if one uses this in ODBC: @code{WHERE auto_increment_column IS NULL}. This seems to fix some problems @item @code{WHERE auto_increment_column IS NULL} を使用して最後にレコードが挿入された後に、 @code{SET SQL_AUTO_IS_NULL=0|1} はサーチのハンドリングの on/off になった。 @item Added new variable @code{concurrency} to @code{mysqld} for Solaris. @item @code{--relative} オプションを @code{mysqladmin} に追加。 これは @code{extended-status} で変更のモニターをする場合、より便利になった。 @item 空のテーブルに対して @code{COUNT(DISTINCT...)} を使用した際のバグを修正。 @item 中国語のキャラクターセット @code{GBK} を追加。 @item @code{LOAD DATA INFILE} を @code{BLOB} フィールドに使用した際の問題を修正。 @item 論理演算子 @code{~} (negation) を追加。 @item @code{UDF} 関数での問題を修正。 @end itemize @node News-3.23.4, News-3.23.3, News-3.23.5, News-3.23.x @appendixsubsec Changes in release 3.23.4 (28 Sep 1999) @itemize @bullet @item @code{DATETIME} 型を @code{TIME} フィールドに挿入するとき、'day' を 保存しようと試みなくなった。 @item low endian のマシンで float/double の保存の問題を修正。 (これは @code{SUM()} に影響する.) @item TCP/IP 接続の connect timeout を追加。 @item インデックス上で、 @code{NULL} 値を持つかもしれないものに @code{LIKE "%"} した際の問題を修正。 @item @code{REVOKE ALL PRIVILEGES} が全ての権限を取り消していなかったのを修正。 @item オリジナルのテーブル名と同じ名前で一時テーブルを作れるようにした。 @item データベースへの権限をあるユーザーに与えた際、 そのユーザーは他のユーザーに権限を与えることが出来なかった。 @item 新コマンド： @code{SHOW GRANTS FOR user} (by Sinisa). @item 新 @code{date_add} syntax: @code{date/datetime + INTERVAL # interval_type}. By Joshua Chamas. @item @code{LOAD DATA REPLACE} の権限のチェックを修正。 @item Solaris 2.7 上での、壊れた include ファイルを自動修正。 @item big file system を検出する際のいくつかの configure の問題を修正。 @item @code{REGEXP} はケース非依存になった。もしバイナリ文字でない場合は。 @end itemize @node News-3.23.3, News-3.23.2, News-3.23.4, News-3.23.x @appendixsubsec Changes in release 3.23.3 @itemize @bullet @item NetBSD 上での MIT-pthreads パッチを追加。 @item @code{MyISAM} 中の range bug を修正。 @item @code{ORDER BY} のデフォルトが再び @code{ASC} になった。 @item @code{LIMIT} を @code{UPDATE} に追加。 @item 新クライアント関数： @code{mysql_change_user()}. @item @code{SHOW VARIABLES} にキャラクターセットを追加。 @item @code{--[whitespace]} コメントをサポートした。 @item Allow @code{INSERT into tbl_name VALUES ()}, that is, you may now specify an empty value list to insert a row in which each column is set to its default value. @item Changed @code{SUBSTRING(text FROM pos)} to conform to ANSI SQL. (Before this construct returned the rightmost 'pos' characters). @item いくつかのシステム上で @code{GROUP BY} をともなった @code{SUM()} は 0 を返すようになった。 @item @code{SHOW TABLE STATUS} の出力を変更。 @item @code{DELAY_KEY_WRITE} オプションを @code{CREATE TABLE} に追加。 @item @code{AUTO_INCREMENT} をいかなるキーの部分に使用できるようにした。 @item @code{YEAR(NOW())} , @code{YEAR(CURDATE())} の問題を修正。 @item Added @code{CASE} construct. @item 新刊数 @code{COALESCE()}. @end itemize @node News-3.23.2, News-3.23.1, News-3.23.3, News-3.23.x @appendixsubsec Changes in release 3.23.2 (1999-08-09) @itemize @bullet @item Fixed range optimizer bug: @code{SELECT * FROM table_name WHERE key_part1 >= const AND (key_part2 = const OR key_part2 = const)}. The bug was that some rows could be duplicated in the result. @item Running @code{myisamchk} without @code{-a} updated the index distribution incorrectly. @item @code{SET SQL_LOW_PRIORITY_UPDATES=1} was causing a parse error. @item @code{WHERE} 節に使用されているインデックスフィールドを更新できるようになった： @code{UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100} @item Date handling should now be a bit faster. @item Added handling of fuzzy dates (dates where day or month is 0), such as @code{'1999-01-00'}. @item Fixed optimization of @code{SELECT ... WHERE key_part1=const1 AND key_part_2=const2 AND key_part1=const4 AND key_part2=const4}; indextype should be @code{range} instead of @code{ref}. @item Linux Alpha 上で @code{egcs} 1.1.2 optimizer のバグ(@code{BLOB} 使用時)を修正。 @item Fixed problem with @code{LOCK TABLES} combined with @code{DELETE FROM table}. @item @code{MyISAM} テーブルは @code{NULL} 値と @code{BLOB/TEXT} フィールドにキーを許すようになった。 @item 以下のJOINがより速くなった： @code{SELECT ... FROM t1 LEFT JOIN t2 ON ... WHERE t2.not_null_column IS NULL}. @item @code{ORDER BY} and @code{GROUP BY} can be done on functions. @item Changed handling of 'const_item' to allow handling of @code{ORDER BY RAND()}. @item @code{WHERE key_column = function} でインデックスが使用されるようになった。 @item 例えフィールドが全く同じにパックされていなくても、 @code{WHERE key_column = column_name} でインデックスが使用されるようになった。 @item @code{WHERE column_name IS NULL} でインデックスが使用されるようになった。 @item Changed heap tables to be stored in low_byte_first order (to make it easy to convert to @code{MyISAM} tables) @item Automatic change of @code{HEAP} temporary tables to @code{MyISAM} tables in case of 'table is full' errors. @item @code{--init-file=file_name} オプションを @code{mysqld} に追加。 @item Added @code{COUNT(DISTINCT value, [value, ...])}. @item @code{CREATE TEMPORARY TABLE} now creates a temporary table, in its own namespace, that is automatically deleted if connection is dropped. @item 新予約語 (@code{CASE} を要求): @code{CASE, THEN, WHEN, ELSE and END}. @item 新関数 @code{EXPORT_SET()} , @code{MD5()}. @item GB2312 中国語キャラクターセットをサポート。 @end itemize @node News-3.23.1, News-3.23.0, News-3.23.2, News-3.23.x @appendixsubsec Changes in release 3.23.1 @itemize @bullet @item いくつかのコンパイル問題を修正した。 @end itemize @node News-3.23.0, , News-3.23.1, News-3.23.x @appendixsubsec Changes in release 3.23.0 (1999-06-05; Alpha) @itemize @bullet @item 多くの新しい特徴を備えた新しい storage engine ライブラリ( @code{MyISAM} )。 @xref{MyISAM, , @code{MyISAM}}. @item メモリー内に @code{HEAP} テーブルを作成できるようになりました。 これは探索がとても速いです。 @item 大容量ファイルをサポートしているOS上で、大ファイル (63 bit) のサポート。 @item 新しい関数 @code{LOAD_FILE(filename)} 。 これはファイルの中身を文字列値として読みます。 @item 新しい演算子 @code{<=>} 。 これは、 @code{=} のように振る舞いますが、 もし両辺の引数が @code{NULL} なら、真を返します。 これはテーブル間の変更の比較に役立ちます。 @item ODBC 3.0 @code{EXTRACT(interval FROM datetime)} 関数の追加。 @item @code{FLOAT(X)} フィールドは、保存した値を丸めません。 これは検索されたときに 科学表記 (1.0 E+10) になるかもしれません。 @item @code{REPLACE} が前よりも速くなった。 @item @code{LIKE} 文字比較を @code{=} のよに振る舞うように変更； これは @code{'e' LIKE '@'e'} が真になるということです。 (if the line doesn't display correctly, the latter 'e' means a French 'e' with a dot above) @item @code{SHOW TABLE STATUS} はテーブルについての情報を多く出すようになりました。 @item @code{LIKE} を @code{SHOW STATUS} コマンドに追加。 @item @code{SHOW COLUMNS} に Privileges 項目を追加。 @item @code{SHOW INDEX} に @code{packed} と @code{comment} 項目を追加。 @item テーブルへのコメントを追加。 ( @code{CREATE TABLE ... COMMENT "xxx"}). @item @code{UNIQUE} を次のように追加： @code{CREATE TABLE table_name (col int not null UNIQUE)} @item 新 create 構文： @code{CREATE TABLE table_name SELECT ...} @item 新 create 構文： @code{CREATE TABLE IF NOT EXISTS ...} @item @code{CHAR(0)} フィールドの作成を許可した。 @item @code{DATE_FORMAT()} は、フォーマット文字の前に @samp{%} が必要になった。 @item @code{DELAYED} が予約語になった。 (sorry about that :( ). @item プロセジャーの例を追加： @code{analyse}, file: @file{sql_analyse.c}. これはクエリのデータについて説明します。 以下の様にしてみてください： @example SELECT ... FROM ... WHERE ... PROCEDURE ANALYSE([max elements,[max memory]]) @end example この プロセジャーは、テーブルのデータをチェックしたい時に、とても役立ちます！ @item @code{BINARY} cast to force a string to be compared case sensitively. @item @code{--skip-show-database} オプションを @code{mysqld} に追加。 @item @code{BLOB}/@code{TEXT} フィールドにおいて、 @code{UPDATE} された レコードをチェックできるようになりました。 @item @code{INNER JOIN} の追加。 @strong{注意}: @code{INNER} は予約語になりました！ @item MySQL テーブルのホストにネットマスクをサポートした。 @code{IP/NETMASK} として、ネットマスクを指定できます。 @item If you compare a @code{NOT NULL DATE/DATETIME} column with @code{IS NULL}, this is changed to a compare against @code{0} to satisfy some ODBC applications. (By @email{shreeve@@uci.edu}). @item @code{NULL IN (...)} は @code{0} ではなく @code{NULL} を返します。 これは @code{null_column NOT IN (...)} が @code{NULL} 値にマッチしないのを確実にします。 @item @code{TIME} フィールド中に、浮動小数点の値を入れるのを修正。 @item Changed parsing of @code{TIME} strings to be more strict. Now the fractional second part is detected (and currently skipped). The following formats are supported: @table @code @item [[DAYS] [H]H:]MM:]SS[.fraction] @item [[[[[H]H]H]H]MM]SS[.fraction] @end table @item Detect (and ignore) second fraction part from @code{DATETIME}. @item @code{LOW_PRIORITY} 属性を @code{LOAD DATA INFILE} に追加。 @item デフォルトのインデックス名を、フィールドの名前と同じケースにした。 @item デフォルトの接続数を 100 に変更。 @item @code{LOAD DATA INFILE} 時に、より大きなバッファを使用するようにした。 @item @code{DECIMAL(x,y)} は ANSI SQL に従って動作するようになった。 @item Added aggregate UDF functions. Thanks to Andreas F. Bobak @email{bobak@@relog.ch} for this! @item @code{LAST_INSERT_ID()} is now updated for @code{INSERT INTO ... SELECT}. @item Some small changes to the join table optimizer to make some joins faster. @item @code{SELECT DISTINCT} が凄く速くなった； これは @code{MyISAM} の新しい @code{UNIQUE} を使用します。 MySQL バージョン 3.22 と一つ違う点は、 @code{DISTINCT} の出力が ソートされないという事です。 @item 全ての C クライアント API が、共有ライブラリを柔軟に作成するため、 マクロから関数になりました。 このため、 @code{mysql_num_fields()} を @code{MYSQL} ととしてコールできず、この代わりに @code{mysql_field_count()} を 使用しなくてはなりません。 @item @code{LIBEWRAP} の追加; Patch by Henning P. Schmiedehausen. @item Don't allow @code{AUTO_INCREMENT} for other than numerical columns. @item @code{AUTO_INCREMENT} の使用は、フィールドを自動的に @code{NOT NULL} にします。 @item Show @code{NULL} as the default value for AUTO_INCREMENT columns. @item @code{SQL_BIG_RESULT} の追加; @code{SQL_SMALL_RESULT} がデフォルトになりました。 @item Added a shared library RPM. This enhancement was contributed by David Fox (dsfox@@cogsci.ucsd.edu). @item @code{--enable-large-files/--disable-large-files} スイッチを @code{configure} に 追加。 See @file{configure.in} for some systems where this is automatically turned off because of broken implementations. @item @code{readline} 4.0 にアップグレード @item 新しい @code{CREATE TABLE} オプション： @code{PACK_KEYS} と @code{CHECKSUM}. @item @code{mysqld} オプションに @code{--default-table-type} を追加。 @end itemize @node News-3.22.x, News-3.21.x, News-3.23.x, News @appendixsec Changes in release 3.22.x (Old; discontinued) @cindex changes, version 3.22 3.22 は 3.21 より早く、より安全なコードをもち、たくさんの新しい機能が盛り込まれています。 これらの変更を 3.21 に行わないのは、3.21 の安定度を保つためにはとても多くの変更が必要とされるからです。 これらの変更はメジャーバージョンの変更ではないので、簡単に障害もなく 3.22 にアップグレードができます。 @xref{Upgrading-from-3.21}. 3.22 は新しい @code{DBD-mysql} (1.20xx) ドライバーのみを新しい接続プロトコルに対して使用します！ @menu * News-3.22.35:: Changes in release 3.22.35 * News-3.22.34:: Changes in release 3.22.34 * News-3.22.33:: Changes in release 3.22.33 * News-3.22.32:: Changes in release 3.22.32 (14 Feb 2000) * News-3.22.31:: Changes in release 3.22.31 * News-3.22.30:: Changes in release 3.22.30 * News-3.22.29:: Changes in release 3.22.29 (02 Jan 2000) * News-3.22.28:: Changes in release 3.22.28 (20 Oct 1999) * News-3.22.27:: Changes in release 3.22.27 * News-3.22.26:: Changes in release 3.22.26 (16 Sep 1999) * News-3.22.25:: Changes in release 3.22.25 * News-3.22.24:: Changes in release 3.22.24 (05 Jul 1999) * News-3.22.23:: Changes in release 3.22.23 (08 Jun 1999) * News-3.22.22:: Changes in release 3.22.22 (30 Apr 1999) * News-3.22.21:: Changes in release 3.22.21 * News-3.22.20:: Changes in release 3.22.20 (18 Mar 1999) * News-3.22.19:: Changes in release 3.22.19 (Mar 1999: Stable) * News-3.22.18:: Changes in release 3.22.18 * News-3.22.17:: Changes in release 3.22.17 * News-3.22.16:: Changes in release 3.22.16 (Feb 1999: Gamma) * News-3.22.15:: Changes in release 3.22.15 * News-3.22.14:: Changes in release 3.22.14 * News-3.22.13:: Changes in release 3.22.13 * News-3.22.12:: Changes in release 3.22.12 * News-3.22.11:: Changes in release 3.22.11 * News-3.22.10:: Changes in release 3.22.10 * News-3.22.9:: Changes in release 3.22.9 * News-3.22.8:: Changes in release 3.22.8 * News-3.22.7:: Changes in release 3.22.7 (Sep 1998: Beta) * News-3.22.6:: Changes in release 3.22.6 * News-3.22.5:: Changes in release 3.22.5 * News-3.22.4:: Changes in release 3.22.4 * News-3.22.3:: Changes in release 3.22.3 * News-3.22.2:: Changes in release 3.22.2 * News-3.22.1:: Changes in release 3.22.1 (Jun 1998: Alpha) * News-3.22.0:: Changes in release 3.22.0 @end menu @node News-3.22.35, News-3.22.34, News-3.22.x, News-3.22.x @appendixsubsec Changes in release 3.22.35 @itemize @bullet @item Fixed problem with @code{STD()}. @item Merged changes from the newest @code{ISAM} library from 3.23. @item Fixed problem with @code{INSERT DELAYED}. @item Fixed a bug core dump when using a @code{LEFT JOIN}/@code{STRAIGHT_JOIN} on a table with only one row. @end itemize @node News-3.22.34, News-3.22.33, News-3.22.35, News-3.22.x @appendixsubsec Changes in release 3.22.34 @itemize @bullet @item Fixed problem with @code{GROUP BY} on @code{TINYBLOB} columns; This caused bugzilla to not show rows in some queries. @item Had to do total recompile of the Windows binary version as VC++ didn't compile all relevant files for 3.22.33 :( @end itemize @node News-3.22.33, News-3.22.32, News-3.22.34, News-3.22.x @appendixsubsec Changes in release 3.22.33 @itemize @bullet @item Fixed problems in Windows when locking tables with @code{LOCK TABLE} @item Quicker kill of @code{SELECT DISTINCT} queries. @end itemize @node News-3.22.32, News-3.22.31, News-3.22.33, News-3.22.x @appendixsubsec Changes in release 3.22.32 (2000-02-14) @itemize @bullet @item 数値を timestamps に保存する際の問題を修正した。 @item Fix problem with timezones that have half hour offsets. @item @code{mysqlhotcopy} - ローカルの MySQL データベースをコピーする ツール. By Tim Bunce. @item @code{mysqlaccess} が新しくなった. Thanks to Steve Harvey for this. @item Fixed security problem in the protocol regarding password checking. @item Fixed problem that affected queries that did arithmetic on @code{GROUP} functions. @item Fixed a bug in the @code{ISAM} code when deleting rows on tables with packed indexes. @end itemize @node News-3.22.31, News-3.22.30, News-3.22.32, News-3.22.x @appendixsubsec Changes in release 3.22.31 @itemize @bullet @item Windows バージョンでのいくつかの小さなバグ修正 @end itemize @node News-3.22.30, News-3.22.29, News-3.22.31, News-3.22.x @appendixsubsec Changes in release 3.22.30 (2000-01-12 stable) @itemize @bullet @item Fixed optimizer problem on @code{SELECT} when using many overlapping indexes. @item Disabled floating-point exceptions for FreeBSD to fix core dump when doing @code{SELECT FLOOR(POW(2,63))}. @item Added print of default arguments options to all clients. @item @code{WITH GRANT OPTION} オプションの致命的なバグを修正. @item Fixed non-critical Y2K problem when writing short date to log files. @end itemize @node News-3.22.29, News-3.22.28, News-3.22.30, News-3.22.x @appendixsubsec Changes in release 3.22.29 (02 Jan 2000) @itemize @bullet @item Upgraded the configure and include files to match the latest 3.23 version. This should increase portability and make it easier to build shared libraries. @item NetBSD 用の最新の mit-pthread のパッチを追加。 @item タイムゾーン < GMT - 11 の場合の問題を修正。 @item @code{NISAM} 中のパックされたキーの削除時のバグを修正。 @item Fixed problem that could cause MySQL to touch freed memory when doing very complicated @code{GROUP BY} queries. @item Fixed core dump if you got a crashed table where an @code{ENUM} field value was too big. @item Added @code{mysqlshutdown.exe} and @code{mysqlwatch.exe} to the Windows distribution. @item キーに対して @code{ORDER BY} を行ったときの問題を修正 @item Fixed that @code{INSERT DELAYED} doesn't update timestamps that are given. @end itemize @node News-3.22.28, News-3.22.27, News-3.22.29, News-3.22.x @appendixsubsec Changes in release 3.22.28 (20 Oct 1999) @itemize @bullet @item Fixed problem with @code{LEFT JOIN} and @code{COUNT()} on a column which was declared @code{NULL} + and it had a @code{DEFAULT} value. @item @code{CONCAT()} をある @code{WHERE} 節で使用した際にコア・ダンプする問題を修正した。 @item Fixed problem with @code{AVG()} and @code{STD()} with @code{NULL} values. @end itemize @node News-3.22.27, News-3.22.26, News-3.22.28, News-3.22.x @appendixsubsec Changes in release 3.22.27 @itemize @bullet @item @file{my_ctype.h} 中の、他のキャラクターセットのプロトタイプを修正。 @item configure 中の、大ファイルシステムを検出する部分の問題を修正。 @item 大きなBLOBフィールドをソートしたときのバグを修正。 @item @code{ROUND()} will now work on Windows. @end itemize @node News-3.22.26, News-3.22.25, News-3.22.27, News-3.22.x @appendixsubsec Changes in release 3.22.26 (16 Sep 1999) @itemize @bullet @item 空の @code{BLOB/TEXT} フィールドを @code{REVERSE()} した際にコアダンプしたのを修正。 @item @code{/*! */} バージョン番号 を拡張した @item Changed @code{SUBSTRING(text FROM pos)} to conform to ANSI SQL. (Before this construct returned the rightmost @code{pos} characters.) @item Fixed problem with @code{LOCK TABLES} combined with @code{DELETE FROM table} @item @code{INSERT ... SELECT} が @code{SQL_BIG_TABLES} を使用していなかったのを修正。 @item @code{SET SQL_LOW_PRIORITY_UPDATES=#} が動いてなかった。 @item 許可を @code{GRANT ... IDENTIFIED BY} で変更しても直にパスワードが 反映されなかったのを修正。 @item 以下の最適化のバグを修正： @code{SELECT * FROM table_name WHERE key_part1 >= const AND (key_part2 = const OR key_part2 = const)} @item Fixed bug in compression key handling in ISAM. @end itemize @node News-3.22.25, News-3.22.24, News-3.22.26, News-3.22.x @appendixsubsec Changes in release 3.22.25 @itemize @bullet @item インストール時の小さな問題を修正。 @end itemize @node News-3.22.24, News-3.22.23, News-3.22.25, News-3.22.x @appendixsubsec Changes in release 3.22.24 (1999-07-05) @itemize @bullet @item @code{DATA} は予約語でなくなった。 @item たった１レコードしかないテーブルの最適化のバグを修正。 @item @code{LOCK TABLES table_name READ; FLUSH TABLES;} を使用した際のバグ修正。 @item HP-UX のパッチを適用。 @item @code{isamchk} が Windows 上で動くようになった。 @item Changed @file{configure} to not use big file handling on Linux as this crashes some RedHat 6.0 systems @end itemize @node News-3.22.23, News-3.22.22, News-3.22.24, News-3.22.x @appendixsubsec Changes in release 3.22.23 (08 Jun 1999) @itemize @bullet @item Autoconf 2.13, Automake 1.4, @code{libtool} 1.3.2 を使用するようにアップグレード。 @item Better support for SCO in @code{configure}. @item Added option @code{--defaults-file=###} to option file handling to force use of only one specific option file. @item @code{MySQL} バージョン 3.23 のキーワードを無視するように @code{CREATE} 構文を拡張した。 @item @code{LOCK TABLES} でロックされているテーブルに @code{INSERT DELAYED} を 使用した際の、デッドロックの問題を修正。 @item 他のスレッドにロックされているテーブルに @code{DROP TABLE} を使用した際の 問題を修正。 @item @code{GRANT/REVOKE} コマンドを update log に追加。 @item 新しいエラー項目を検出するように @code{isamchk} を修正。 @item @code{NATURAL LEFT JOIN} のバグを修正。 @end itemize @node News-3.22.22, News-3.22.21, News-3.22.23, News-3.22.x @appendixsubsec Changes in release 3.22.22 (30 Apr 1999) @itemize @bullet @item @code{mysql_init()} の後に直接 @code{mysql_close()} を読んだときの問題を修正。 (C API) @item Better client error message when you can't open socket. @item 新しいdelayed_insert スレッドが作成できなかったときの @code{delayed_insert_thread} 数の表示を修正。 @item @code{CONCAT()} の引数を多くした場合のバグを修正。 @item DEC 3.2 と SCO のパッチの追加。 @item NT のサービスとして MySQL をインストールした際の パスの問題を修正。 @item MySQL-Windows は VC++ 6.0 でコンパイルされるようになった。 (VC++ 5.0 のかわりに) @item MySQL-Windows の新しいインストーラー @end itemize @node News-3.22.21, News-3.22.20, News-3.22.22, News-3.22.x @appendixsubsec Changes in release 3.22.21 @itemize @bullet @item テーブルが他のスレッドにロックされたときの、@code{DELETE FROM TABLE} の 問題を修正。 @item Fixed bug in @code{LEFT JOIN} involving empty tables. @item @code{mysql.db} フィールドを @code{char(32)} から @code{char(60)} に変更。 @item @code{MODIFY} と @code{DELAYED} は予約語でなくなった。 @item @code{TIME} フィールドに日にちを入れようとしたときのバグを修正。 @item @code{GRANT} コマンドで新しい MySQL ユーザーを登録した後に @code{Host '...' is not allowed to connect to this MySQL server} となる問題を修正。 @item Linux 上で @code{TCP_NODELAY} を使用するように変更。 (これは TCP/IP 接続を速くします) @end itemize @node News-3.22.20, News-3.22.19, News-3.22.21, News-3.22.x @appendixsubsec Changes in release 3.22.20 (1999-03-18) @itemize @bullet @item Fixed @code{STD()} for big tables when result should be 0. @item いくつかのOS でupdate log が改行を入れていなかったのを修正。 @item @code{INSERT DELAYED} had some garbage at end in the update log. @end itemize @node News-3.22.19, News-3.22.18, News-3.22.20, News-3.22.x @appendixsubsec Changes in release 3.22.19 (1999-03-02) @itemize @bullet @item @code{mysql_install_db} のバグ修正。 (from 3.22.17). @item デフォルトのキーキャッシュを 8M に変更。 @item @code{BLOB} フィールドで一時テーブルが必要とされるクエリの問題を修正。 @end itemize @node News-3.22.18, News-3.22.17, News-3.22.19, News-3.22.x @appendixsubsec Changes in release 3.22.18 @itemize @bullet @item Linux上で、3.22.17の致命的な問題の修正； @code{shutdown} 後、全ての スレッドが確実に死ななかった。 @item @code{-O flush_time=#} オプションを @code{mysqld} に追加。 This is mostly useful on Windows and tells how often MySQL should close all unused tables and flush all updated tables to disk. @item @code{VARCHAR} フィールドと @code{CHAR} を比較した際にキーを効果的に 使用していなかったのを修正。 @end itemize @node News-3.22.17, News-3.22.16, News-3.22.18, News-3.22.x @appendixsubsec Changes in release 3.22.17 @itemize @bullet @item @code{--log-update} を使用したときとデフォルトのデータベースを指定しないで 接続したときのコアダンプを修正した。 @item いくつかの @code{configure} と移植性の問題を修正した。 @item Using @code{LEFT JOIN} on tables that had circular dependencies caused @code{mysqld} to hang forever. @end itemize @node News-3.22.16, News-3.22.15, News-3.22.17, News-3.22.x @appendixsubsec Changes in release 3.22.16 (1999-02-07) @itemize @bullet @item @code{mysqladmin processlist} could kill the server if a new user logged in. @item @code{DELETE FROM table_name WHERE key_column=column_name} が マッチする行を1行も見つけれないのを修正 @item @code{DATE_ADD(column, ...)} が動かないのを修正 @item @code{INSERT DELAYED} could deadlock with status 'upgrading lock' @item 2文字以上のソルトが使用できるように、@code{ENCRYPT()} を拡張。 @item @code{longlong2str} は以前よりかなり速くなった。@code{Intel x86} 用に このコードは最適化されたアセンブラで書き直した @item @code{ALTER TABLE} に @code{MODIFY} キーワードを追加 @end itemize @node News-3.22.15, News-3.22.14, News-3.22.16, News-3.22.x @appendixsubsec Changes in release 3.22.15 @itemize @bullet @item @code{GRANT} を @code{IDENTIFIED BY} と共に使用した際、権限情報がフラッシュされるまで 有効にならない @item Name change of some variables in @code{SHOW STATUS}. @item Fixed problem with @code{ORDER BY} with 'only index' optimization when there were multiple key definitions for a used column. @item @code{DATE} and @code{DATETIME} columns are now up to 5 times faster than before. @item @code{INSERT DELAYED} can be used to let the client do other things while the server inserts rows into a table. @item もし2つの違うデータベースのテーブルを使用した場合、 @code{LEFT JOIN USING (col1,col2)} が動作しなかった @item @code{LOAD DATA LOCAL INFILE} がファイルがないための理由で UNIX では動作しなかった @item とても短い行(<4バイト)しかない @code{VARCHAR}/@code{BLOB} での問題の修正； error 127 がこの行を消去する場合に起きる可能性があった @item Updating @code{BLOB/TEXT} through formulas didn't work for short (< 256 char) strings. @item 新しいホスト上で @code{GRANT} を実行した場合、そのホストからの最初のコネクションで @code{mysqld} が死ぬ可能性があった @item エイリアス名と同じ項目名を @code{ORDER BY} で使用する場合のバグを修正 name as an alias. @item Added @code{BENCHMARK(loop_count,expression)} function to time expressions. @end itemize @node News-3.22.14, News-3.22.13, News-3.22.15, News-3.22.x @appendixsubsec Changes in release 3.22.14 @itemize @bullet @item シェルスクリプトからの起動のために、@code{mysqld} の引数がない場合を許可した。 @item Setting a @code{TIMESTAMP} column to @code{NULL} didn't record the timestamp value in the update log. @item Fixed lock handler bug when one did @code{INSERT INTO TABLE ... SELECT ... GROUP BY}. @item Added a patch for @code{localtime_r()} on Windows so that it will not crash anymore if your date is > 2039, but instead will return a time of all zero. @item Names for user-defined functions are no longer case-sensitive. @item Added escape of @code{^Z} (ASCII 26) to @code{\Z} as @code{^Z} doesn't work with pipes on Windows. @item 将来の MySQL リリースのために、@code{mysql_fix_privileges} は、 UDF のサポートのために、新しい項目を @code{mysql.func} に追加する。 ( type enum ('function','aggregate') NOT NULL が追加された ) @end itemize @node News-3.22.13, News-3.22.12, News-3.22.14, News-3.22.x @appendixsubsec Changes in release 3.22.13 (1998-12-17) @itemize @bullet @item Saving @code{NOW()}, @code{CURDATE()} or @code{CURTIME()} directly in a column didn't work. @item @code{WHERE} 節が無い場合、@code{SELECT COUNT(*) ... LEFT JOIN ...} が動かなかった @item UnixWare 7.0.x で MySQL をコンフィグできるように @file{config.guess} を更新 UnixWare 7.0.x. @item Changed the implementation of @code{pthread_cond()} on the Windows version. @code{get_lock()} now correctly times out on Windows! @end itemize @node News-3.22.12, News-3.22.11, News-3.22.13, News-3.22.x @appendixsubsec Changes in release 3.22.12 (1998-12-10) @itemize @bullet @item @code{WHERE} 節で @code{DATE_ADD()} と @code{DATE_SUB()} を使用した際の問題を修正 @item @code{GRANT ... TO user IDENTIFIED BY 'password'} 構文でパスワードをセットできるようにした @item 多くのテーブルを @code{SELECT} して @code{GRANT} を確認する際のバグを修正 @item RPM 配布での @code{mysql_fix_privilege_tables} ファイルの追加。 これはクライアントパッケージに含んだため、デフォルトでは起動されない。 @item @code{SQL_SMALL_RESULT} オプションを @code{SELECT} に追加。 これは強制的に速い一時テーブルを使用する。 結果が小さいとわかっている場合に使用すると有効。 @item 小数点をつけなくても実数が使用できるようにした @item @code{DATE_ADD}/@code{DATE_SUB()} の結果、十分な日数を得られない場合、 日数を月の最大日にするようにした。 @item @code{GRANT} がカラムをケース非依存で比較していたのを修正 @item ある構文の組み合わせで @code{ALTER TABLE} が core をはくバグが @file{sql_list.h} にあったのでこれを修正 @item The hostname in @code{user@@hostname} can now include @samp{.} and @samp{-} without quotes in the context of the @code{GRANT}, @code{REVOKE} and @code{SET PASSWORD FOR ...} statements. @item 大きな一時ファイルを必要とするテーブルへの @code{isamchk} を修正 @end itemize @node News-3.22.11, News-3.22.10, News-3.22.12, News-3.22.x @appendixsubsec Changes in release 3.22.11 (1998-11-25) @itemize @bullet @item @strong{重要}: 3.22.11にアップグレードする場合、必ず @code{mysql_fix_privilege_tables} スクリプトを実行しなくてはなりません！ これは新しい @code{GRANT} システムのために実行します。 もしこれを行わなければ、@code{ALTER TABLE} や @code{CREATE INDEX}, @code{DROP INDEX} を 実行しようとすると @code{Access denied} になります。 @item テーブル、カラムごとにユーザーのアクセスに対して許可や拒否を設定できます @item @code{USER()} を @code{user@@host} を返すように変更 @item 他のユーザーの @code{PASSWORD} をセットする構文を変更 @item 新コマンド：@code{FLUSH STATUS} はほとんどのステータス変数をゼロにセットします @item 新ステータス変数： @code{aborted_threads}, @code{aborted_connects}. @item 新オプション： @code{connection_timeout} @item ソートのサポート (by Pruet Boonma @email{pruet@@ds90.intanon.nectec.or.th}). @item スロバキア語と日本語のエラーメッセージ @item Configuration and portability fixes. @item Added option @code{SET SQL_WARNINGS=1} to get a warning count also for simple inserts. @item FreeBSD 上でシャットダウンするために、@code{SIGQUIT} のかわりに @code{SIGTERM} を使用します @item @code{mysql} に オプション @code{\G} (print vertically) 追加 @item @code{SELECT HIGH_PRIORITY ...} killed @code{mysqld}. @item @code{IS NULL} on a @code{AUTO_INCREMENT} column in a @code{LEFT JOIN} didn't work as expected. @item New function @code{MAKE_SET()}. @end itemize @node News-3.22.10, News-3.22.9, News-3.22.11, News-3.22.x @appendixsubsec Changes in release 3.22.10 (1998-11-05) @itemize @bullet @item mysql_install_db は MySQL サーバーを起動しなくなりました! mysql_install_db を行った後に、@code{safe_mysqld} で mysqld を開始させる必要があります。 しかし MySQL の RPM パッケージはサーバーをたちあげるようにしています。 @item @code{--bootstrap} を @code{mysqld} に追加。@code{mysql_install_db} はこれを使用します。 この引数は RPM パッケージで MySQL のインストールを簡略化します。 @item @code{+, - (sign and minus), *, /, %, ABS() and MOD()} のコードを修正。 @code{BIGINT}で使用した場合の危険性を回避しました(64 bit safe). @item @code{ALTER TABLE} が mysqld をクラッシュさせるバグを修正。 @item 重複したキー結果を得た場合、MySQLは常にその旨を報告するようになりました。 (以前のバージョンでは、@code{INSERT} の時にしかメッセージが出ませんでした) @item New syntax: @code{INSERT INTO table_name SET column=value,column=value, ...} @item @file{.err} ログファイルのログ記録に、time stamp をつけるようにしました。 @item @code{MYSQL_INIT_COMMAND} オプションを @code{mysql_options()} に追加。 (接続要求する場合に使用できる) @item @code{MYSQL_READ_DEFAULT_FILE} と @code{MYSQL_READ_DEFAULT_GROUP} を @code{mysql_options()}に追加。 MySQL オプションファイルから以下のパラメーターを読み取る： @code{port}, @code{socket}, @code{compress}, @code{password}, @code{pipe}, @code{timeout}, @code{user}, @code{init-command}, @code{host} and @code{database} (訳注)オプションファイルのデフォルトは /etc/my.cnf , install_directory/share/mysql/my.cnf @item UDF 構文に @code{maybe_null} を追加 @item Added option @code{IGNORE} to @code{INSERT} statements with many rows. @item koi8 キャラクターをソートする場合の問題を修正。 koi8を使用しているユーザーは、@code{CHAR} や @code{VARCHAR} カラムを インデックスにしているテーブルに対して、@strong{必ず} @code{isamchk -rq} を実行すること。 @item 新規スクリプト @code{mysql_setpermission} (Luuk de Boer 作) これは指定されたデータベースに対してアクセスを許可するユーザーを 簡単に登録してくれます。 @item Allow use of hexadecimal strings (0x...) when specifying a constant string (like in the column separators with @code{LOAD DATA INFILE}). @item OS/2 に移植 (thanks to Antony T. Curtis @email{antony.curtis@@olcs.net}). @item @code{SHOW STATUS} での変数を増やしました。また、@code{SHOW VARIABLES} の ような出力フォーマットに変更しました。 @item @code{extended-status} コマンドを @code{mysqladmin} に追加。 これは新しいステイタス変数を表示します @end itemize @node News-3.22.9, News-3.22.8, News-3.22.10, News-3.22.x @appendixsubsec Changes in release 3.22.9 @itemize @bullet @item @code{SET SQL_LOG_UPDATE=0} caused a lockup of the server. @item New SQL command: @code{FLUSH [ TABLES | HOSTS | LOGS | PRIVILEGES ] [, ...]} @item New SQL command: @code{KILL} @code{thread_id} . @item AIX, DEC OSF1 4.x で MySQL を簡単にコンパイルできるように include ファイルを変更。 @item @code{ALTER TABLE} を使用して @code{INT} からサイズの小さい @code{CHAR()} に 変更する場合におきていた不具合を修正。 @item @code{SELECT HIGH_PRIORITY} 追加。 @code{SELECT} において、たとえ他の @code{SELECT} を待っているスレッドがあったとしても、 @code{WRITE LOCK} することができます。 @item Moved wild_compare to string class to be able to use @code{LIKE} on @code{BLOB}/@code{TEXT} columns with \0. @item Added @code{ESCAPE} option to @code{LIKE} @item @code{mysqladmin debug} において、より多くの出力が得られるようにした。 @item Windows において、@code{--flush} オプションをつけて @code{mysqld} を起動できるようになりました。 これはアップデートが終わった後ですべてのテーブルをディスクにフラッシュします。 このオプションにより NT/Win98 上ですごく安全に動かすことができますが、 @strong{とても} 遅くなります。 @end itemize @node News-3.22.8, News-3.22.7, News-3.22.9, News-3.22.x @appendixsubsec Changes in release 3.22.8 @itemize @bullet @item Czech character sets should now work much better. You must also install @uref{http://www.mysql.com/Downloads/Patches/czech-3.22.8-patch}. This patch should also be installed if you are using a character set which uses @code{my_strcoll()}! The patch should always be safe to install (for any system), but as this patch changes @code{ISAM} internals it's not yet in the default distribution. @item @code{DATE_ADD()} and @code{DATE_SUB()} didn't work with group functions. @item @code{mysql} will now also try to reconnect on @code{USE DATABASE} commands. @item Fix problem with @code{ORDER BY} and @code{LEFT JOIN} and @code{const} tables. @item Fixed problem with @code{ORDER BY} if the first @code{ORDER BY} column was a key and the rest of the @code{ORDER BY} columns wasn't part of the key. @item Fixed a big problem with @code{OPTIMIZE TABLE}. @item MySQL clients on NT will now by default first try to connect with named pipes and after this with TCP/IP. @item Fixed a problem with @code{DROP TABLE} and @code{mysqladmin shutdown} on Windows (a fatal bug from 3.22.6). @item Fixed problems with @code{TIME columns} and negative strings. @item Added an extra thread signal loop on shutdown to avoid some error messages from the client. @item MySQL now uses the next available number as extension for the update log file. @item Added patches for UNIXWARE 7. @end itemize @node News-3.22.7, News-3.22.6, News-3.22.8, News-3.22.x @appendixsubsec Changes in release 3.22.7 (1998-09: Beta) @itemize @bullet @item Added @code{LIMIT} clause for the @code{DELETE} statement. @item You can now use the @code{/*! ... */} syntax to hide MySQL-specific keywords when you write portable code. MySQL will parse the code inside the comments as if the surrounding @code{/*!} and @code{*/} comment characters didn't exist. @item @code{OPTIMIZE TABLE tbl_name} can now be used to reclaim disk space after many deletes. Currently, this uses @code{ALTER TABLE} to re-generate the table, but in the future it will use an integrated @code{isamchk} for more speed. @item Upgraded @code{libtool} to get the configure more portable. @item Fixed slow @code{UPDATE} and @code{DELETE} operations when using @code{DATETIME} or @code{DATE} keys. @item Changed optimizer to make it better at deciding when to do a full join and when using keys. @item You can now use @code{mysqladmin proc} to display information about your own threads. Only users with the @code{PROCESS} privilege can get information about all threads. (In 4.0.2 one needs the @code{SUPER} privilege for this.) @item Added handling of formats @code{YYMMDD}, @code{YYYYMMDD}, @code{YYMMDDHHMMSS} for numbers when using @code{DATETIME} and @code{TIMESTAMP} types. (Formerly these formats only worked with strings.) @item Added connect option @code{CLIENT_IGNORE_SPACE} to allow use of spaces after function names and before @samp{(} (Powerbuilder requires this). This will make all function names reserved words. @item Added the @code{--log-long-format} option to @code{mysqld} to enable timestamps and INSERT_ID's in the update log. @item Added @code{--where} option to @code{mysqldump} (patch by Jim Faucette). @item The lexical analyser now uses ``perfect hashing'' for faster parsing of SQL statements. @end itemize @node News-3.22.6, News-3.22.5, News-3.22.7, News-3.22.x @appendixsubsec Changes in release 3.22.6 (1998-07-11) @itemize @bullet @item Faster @code{mysqldump}. @item For the @code{LOAD DATA INFILE} statement, you can now use the new @code{LOCAL} keyword to read the file from the client. @code{mysqlimport} will automatically use @code{LOCAL} when importing with the TCP/IP protocol. @item Fixed small optimize problem when updating keys. @item Changed makefiles to support shared libraries. @item MySQL-NT can now use named pipes, which means that you can now use MySQL-NT without having to install TCP/IP. @end itemize @node News-3.22.5, News-3.22.4, News-3.22.6, News-3.22.x @appendixsubsec Changes in release 3.22.5 @itemize @bullet @item All table lock handing is changed to avoid some very subtle deadlocks when using @code{DROP TABLE}, @code{ALTER TABLE}, @code{DELETE FROM TABLE} and @code{mysqladmin flush-tables} under heavy usage. Changed locking code to get better handling of locks of different types. @item Updated @code{DBI} to 1.00 and @code{DBD} to 1.2.0. @item Added a check that the error message file contains error messages suitable for the current version of @code{mysqld}. (To avoid errors if you accidentally try to use an old error message file.) @item All count structures in the client (@code{affected_rows()}, @code{insert_id()}, ...) are now of type @code{BIGINT} to allow 64-bit values to be used. This required a minor change in the MySQL protocol which should affect only old clients when using tables with @code{AUTO_INCREMENT} values > 16M. @item The return type of @code{mysql_fetch_lengths()} has changed from @code{uint *} to @code{ulong *}. This may give a warning for old clients but should work on most machines. @item Change @code{mysys} and @code{dbug} libraries to allocate all thread variables in one struct. This makes it easier to make a threaded @file{libmysql.dll} library. @item Use the result from @code{gethostname()} (instead of @code{uname()}) when constructing @file{.pid} file names. @item New better compressed server/client protocol. @item @code{COUNT()}, @code{STD()} and @code{AVG()} are extended to handle more than 4G rows. @item You can now store values in the range @code{-838:59:59} <= x <= @code{838:59:59} in a @code{TIME} column. @item @strong{WARNING: INCOMPATIBLE CHANGE!!} If you set a @code{TIME} column to too short a value, MySQL now assumes the value is given as: @code{[[[D ]HH:]MM:]SS} instead of @code{HH[:MM[:SS]]}. @item @code{TIME_TO_SEC()} and @code{SEC_TO_TIME()} can now handle negative times and hours up to 32767. @item Added new option @code{SET SQL_LOG_UPDATE=@{0|1@}} to allow users with the @code{PROCESS} privilege to bypass the update log. (Modified patch from Sergey A Mukhin @email{violet@@rosnet.net}.) @item Fixed fatal bug in @code{LPAD()}. @item Initialise line buffer in @file{mysql.cc} to make @code{BLOB} reading from pipes safer. @item Added @code{-O max_connect_errors=#} option to @code{mysqld}. Connect errors are now reset for each correct connection. @item Increased the default value of @code{max_allowed_packet} to @code{1M} in @code{mysqld}. @item Added @code{--low-priority-updates} option to @code{mysqld}, to give table-modifying operations (@code{INSERT}, @code{REPLACE}, @code{UPDATE}, @code{DELETE}) lower priority than retrievals. You can now use @code{@{INSERT | REPLACE | UPDATE | DELETE@} LOW_PRIORITY ...} You can also use @code{SET SQL_LOW_PRIORITY_UPDATES=@{0|1@}} to change the priority for one thread. One side effect is that @code{LOW_PRIORITY} is now a reserved word. :( @item Add support for @code{INSERT INTO table ... VALUES(...),(...),(...)}, to allow inserting multiple rows with a single statement. @item @code{INSERT INTO tbl_name} is now also cached when used with @code{LOCK TABLES}. (Previously only @code{INSERT ... SELECT} and @code{LOAD DATA INFILE} were cached.) @item Allow @code{GROUP BY} functions with @code{HAVING}: @example mysql> SELECT col FROM table GROUP BY col HAVING COUNT(*)>0; @end example @item @code{mysqld} will now ignore trailing @samp{;} characters in queries. This is to make it easier to migrate from some other SQL servers that require the trailing @samp{;}. @item Fix for corrupted fixed-format output generated by @code{SELECT INTO OUTFILE}. @item @strong{Warning: incompatible change!} Added Oracle @code{GREATEST()} and @code{LEAST()} functions. You must now use these instead of the @code{MAX()} and @code{MIN()} functions to get the largest/smallest value from a list of values. These can now handle @code{REAL}, @code{BIGINT} and string (@code{CHAR} or @code{VARCHAR}) values. @item @strong{Warning: incompatible change!} @code{DAYOFWEEK()} had offset 0 for Sunday. Changed the offset to 1. @item Give an error for queries that mix @code{GROUP BY} columns and fields when there is no @code{GROUP BY} specification. @item Added @code{--vertical} option to @code{mysql}, for printing results in vertical mode. @item Index-only optimization; some queries are now resolved using only indexes. Until MySQL 4.0, this works only for numeric columns. @xref{MySQL indexes, , MySQL indexes}. @item Lots of new benchmarks. @item A new C API chapter and lots of other improvements in the manual. @end itemize @node News-3.22.4, News-3.22.3, News-3.22.5, News-3.22.x @appendixsubsec Changes in release 3.22.4 @itemize @bullet @item Added @code{--tmpdir} option to @code{mysqld}, for specifying the location of the temporary file directory. @item MySQL now automatically changes a query from an ODBC client: @example SELECT ... FROM table WHERE auto_increment_column IS NULL @end example to: @example SELECT ... FROM table WHERE auto_increment_column == LAST_INSERT_ID() @end example This allows some ODBC programs (Delphi, Access) to retrieve the newly inserted row to fetch the @code{AUTO_INCREMENT} id. @item @code{DROP TABLE} now waits for all users to free a table before deleting it. @item Fixed small memory leak in the new connect protocol. @item New functions @code{BIN()}, @code{OCT()}, @code{HEX()} and @code{CONV()} for converting between different number bases. @item Added function @code{SUBSTRING()} with 2 arguments. @item If you created a table with a record length smaller than 5, you couldn't delete rows from the table. @item Added optimization to remove const reference tables from @code{ORDER BY} and @code{GROUP BY}. @item @code{mysqld} now automatically disables system locking on Linux and Windows, and for systems that use MIT-pthreads. You can force the use of locking with the @code{--enable-external-locking} option. @item Added @code{--console} option to @code{mysqld}, to force a console window (for error messages) when using Windows. @item Fixed table locks for Windows. @item Allow @samp{$} in identifiers. @item Changed name of user-specific configuration file from @file{my.cnf} to @file{.my.cnf} (Unix only). @item Added @code{DATE_ADD()} and @code{DATE_SUB()} functions. @end itemize @node News-3.22.3, News-3.22.2, News-3.22.4, News-3.22.x @appendixsubsec Changes in release 3.22.3 @itemize @bullet @item Fixed a lock problem (bug in MySQL Version 3.22.1) when closing temporary tables. @item Added missing @code{mysql_ping()} to the client library. @item Added @code{--compress} option to all MySQL clients. @item Changed @code{byte} to @code{char} in @file{mysql.h} and @file{mysql_com.h}. @end itemize @node News-3.22.2, News-3.22.1, News-3.22.3, News-3.22.x @appendixsubsec Changes in release 3.22.2 @itemize @bullet @item Searching on multiple constant keys that matched more than 30% of the rows didn't always use the best possible key. @item New functions @code{<<}, @code{>>}, @code{RPAD()} and @code{LPAD()}. @item You can now save default options (like passwords) in a configuration file (@file{my.cnf}). @item Lots of small changes to get @code{ORDER BY} to work when no records are found when using fields that are not in @code{GROUP BY} (MySQL extension). @item Added @code{--chroot} option to @code{mysqld}, to start @code{mysqld} in a chroot environment (by Nikki Chumakov @email{nikkic@@cityline.ru}). @item Trailing spaces are now ignored when comparing case-sensitive strings; this should fix some problems with ODBC and flag 512! @item Fixed a core-dump bug in the range optimizer. @item Added @code{--one-thread} option to @code{mysqld}, for debugging with LinuxThreads (or @code{glibc}). (This replaces the @code{-T32} flag) @item Added @code{DROP TABLE IF EXISTS} to prevent an error from occurring if the table doesn't exist. @item @code{IF} and @code{EXISTS} are now reserved words (they would have to be sooner or later). @item Added lots of new options to @code{mysqldump}. @item Server error messages are now in @file{mysqld_error.h}. @item The server/client protocol now supports compression. @item All bug fixes from MySQL Version 3.21.32. @end itemize @node News-3.22.1, News-3.22.0, News-3.22.2, News-3.22.x @appendixsubsec Changes in release 3.22.1 (1998-06-17) @itemize @bullet @item Added new C API function @code{mysql_ping()}. @item Added new API functions @code{mysql_init()} and @code{mysql_options()}. You now MUST call @code{mysql_init()} before you call @code{mysql_real_connect()}. You don't have to call @code{mysql_init()} if you only use @code{mysql_connect()}. @item Added @code{mysql_options(...,MYSQL_OPT_CONNECT_TIMEOUT,...)} so you can set a timeout for connecting to a server. @item Added @code{--timeout} option to @code{mysqladmin}, as a test of @code{mysql_options()}. @item Added @code{AFTER column} and @code{FIRST} options to @code{ALTER TABLE ... ADD columns}. This makes it possible to add a new column at some specific location within a row in an existing table. @item @code{WEEK()} now takes an optional argument to allow handling of weeks when the week starts on Monday (some European countries). By default, @code{WEEK()} assumes the week starts on Sunday. @item @code{TIME} columns weren't stored properly (bug in MySQL Version 3.22.0). @item @code{UPDATE} now returns information about how many rows were matched and updated, and how many ``warnings'' occurred when doing the update. @item Fixed incorrect result from @code{FORMAT(-100,2)}. @item @code{ENUM} and @code{SET} columns were compared in binary (case-sensitive) fashion; changed to be case-insensitive. @end itemize @node News-3.22.0, , News-3.22.1, News-3.22.x @appendixsubsec Changes in release 3.22.0 @itemize @bullet @item New (backward-compatible) connect protocol that allows you to specify the database to use when connecting, to get much faster connections to a specific database. The @code{mysql_real_connect()} call is changed to: @example mysql_real_connect(MYSQL *mysql, const char *host, const char *user, const char *passwd, const char *db, uint port, const char *unix_socket, uint client_flag) @end example @item Each connection is handled by its own thread, rather than by the master @code{accept()} thread. This fixes permanently the telnet bug that was a topic on the mail list some time ago. @item All TCP/IP connections are now checked with backward-resolution of the hostname to get better security. @code{mysqld} now has a local hostname resolver cache so connections should actually be faster than before, even with this feature. @item A site automatically will be blocked from future connections if someone repeatedly connects with an ``improper header'' (like when one uses telnet). @item You can now refer to tables in different databases with references of the form @code{tbl_name@@db_name} or @code{db_name.tbl_name}. This makes it possible to give a user read access to some tables and write access to others simply by keeping them in different databases! @item Added @code{--user} option to @code{mysqld}, to allow it to run as another Unix user (if it is started as the Unix @code{root} user). @item Added caching of users and access rights (for faster access rights checking) @item Normal users (not anonymous ones) can change their password with @code{mysqladmin password 'new_password'}. This uses encrypted passwords that are not logged in the normal MySQL log! @item All important string functions are now coded in assembler for x86 Linux machines. This gives a speedup of 10% in many cases. @item For tables that have many columns, the column names are now hashed for much faster column name lookup (this will speed up some benchmark tests a lot!) @item Some benchmarks are changed to get better individual timing. (Some loops were so short that a specific test took < 2 seconds. The loops have been changed to take about 20 seconds to make it easier to compare different databases. A test that took 1-2 seconds before now takes 11-24 seconds, which is much better) @item Re-arranged @code{SELECT} code to handle some very specific queries involving group functions (like @code{COUNT(*)}) without a @code{GROUP BY} but with @code{HAVING}. The following now works: @example mysql> SELECT COUNT(*) as C FROM table HAVING C > 1; @end example @item Changed the protocol for field functions to be faster and avoid some calls to @code{malloc()}. @item Added @code{-T32} option to @code{mysqld}, for running all queries under the main thread. This makes it possible to debug @code{mysqld} under Linux with @code{gdb}! @item Added optimization of @code{not_null_column IS NULL} (needed for some Access queries). @item Allow @code{STRAIGHT_JOIN} to be used between two tables to force the optimizer to join them in a specific order. @item String functions now return @code{VARCHAR} rather than @code{CHAR} and the column type is now @code{VARCHAR} for fields saved as @code{VARCHAR}. This should make the @strong{MyODBC} driver better, but may break some old MySQL clients that don't handle @code{FIELD_TYPE_VARCHAR} the same way as @code{FIELD_TYPE_CHAR}. @item @code{CREATE INDEX} and @code{DROP INDEX} are now implemented through @code{ALTER TABLE}. @code{CREATE TABLE} is still the recommended (fast) way to create indexes. @item Added @code{--set-variable} option @code{wait_timeout} to @code{mysqld}. @item Added time column to @code{mysqladmin processlist} to show how long a query has taken or how long a thread has slept. @item Added lots of new variables to @code{show variables} and some new to @code{show status}. @item Added new type @code{YEAR}. @code{YEAR} is stored in 1 byte with allowable values of 0, and 1901 to 2155. @item Added new @code{DATE} type that is stored in 3 bytes rather than 4 bytes. All new tables are created with the new date type if you don't use the @code{--old-protocol} option to @code{mysqld}. @item Fixed bug in record caches; for some queries, you could get @code{Error from table handler: #} on some operating systems. @item Added @code{--enable-assembler} option to @code{configure}, for x86 machines (tested on Linux + @code{gcc}). This will enable assembler functions for the most important string functions for more speed! @end itemize @node News-3.21.x, News-3.20.x, News-3.22.x, News @appendixsec Changes in release 3.21.x Version 3.21 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only. @menu * News-3.21.33:: Changes in release 3.21.33 * News-3.21.32:: Changes in release 3.21.32 * News-3.21.31:: Changes in release 3.21.31 * News-3.21.30:: Changes in release 3.21.30 * News-3.21.29:: Changes in release 3.21.29 * News-3.21.28:: Changes in release 3.21.28 * News-3.21.27:: Changes in release 3.21.27 * News-3.21.26:: Changes in release 3.21.26 * News-3.21.25:: Changes in release 3.21.25 * News-3.21.24:: Changes in release 3.21.24 * News-3.21.23:: Changes in release 3.21.23 * News-3.21.22:: Changes in release 3.21.22 * News-3.21.21a:: Changes in release 3.21.21a * News-3.21.21:: Changes in release 3.21.21 * News-3.21.20:: Changes in release 3.21.20 * News-3.21.19:: Changes in release 3.21.19 * News-3.21.18:: Changes in release 3.21.18 * News-3.21.17:: Changes in release 3.21.17 * News-3.21.16:: Changes in release 3.21.16 * News-3.21.15:: Changes in release 3.21.15 * News-3.21.14b:: Changes in release 3.21.14b * News-3.21.14a:: Changes in release 3.21.14a * News-3.21.13:: Changes in release 3.21.13 * News-3.21.12:: Changes in release 3.21.12 * News-3.21.11:: Changes in release 3.21.11 * News-3.21.10:: Changes in release 3.21.10 * News-3.21.9:: Changes in release 3.21.9 * News-3.21.8:: Changes in release 3.21.8 * News-3.21.7:: Changes in release 3.21.7 * News-3.21.6:: Changes in release 3.21.6 * News-3.21.5:: Changes in release 3.21.5 * News-3.21.4:: Changes in release 3.21.4 * News-3.21.3:: Changes in release 3.21.3 * News-3.21.2:: Changes in release 3.21.2 * News-3.21.0:: Changes in release 3.21.0 @end menu @node News-3.21.33, News-3.21.32, News-3.21.x, News-3.21.x @appendixsubsec Changes in release 3.21.33 (1998-07-11) @itemize @bullet @item Fixed problem when sending @code{SIGHUP} to @code{mysqld}; @code{mysqld} core dumped when starting from boot on some systems. @item Fixed problem with losing a little memory for some connections. @item @code{DELETE FROM tbl_name} without a @code{WHERE} condition is now done the long way when you use @code{LOCK TABLES} or if the table is in use, to avoid race conditions. @item @code{INSERT INTO TABLE (timestamp_column) VALUES (NULL);} didn't set timestamp. @end itemize @node News-3.21.32, News-3.21.31, News-3.21.33, News-3.21.x @appendixsubsec Changes in release 3.21.32 @itemize @bullet @item Fixed some possible race conditions when doing many reopen/close on the same tables under heavy load! This can happen if you execute @code{mysqladmin refresh} often. This could in some very rare cases corrupt the header of the index file and cause error 126 or 138. @item Fixed fatal bug in @code{refresh()} when running with the @code{--skip-external-locking} option. There was a ``very small'' time gap after a @code{mysqladmin refresh} when a table could be corrupted if one thread updated a table while another thread did @code{mysqladmin refresh} and another thread started a new update ont the same table before the first thread had finished. A refresh (or @code{--flush-tables}) will now not return until all used tables are closed! @item @code{SELECT DISTINCT} with a @code{WHERE} clause that didn't match any rows returned a row in some contexts (bug only in 3.21.31). @item @code{GROUP BY} + @code{ORDER BY} returned one empty row when no rows where found. @item Fixed a bug in the range optimizer that wrote @code{Use_count: Wrong count for ...} in the error log file. @end itemize @node News-3.21.31, News-3.21.30, News-3.21.32, News-3.21.x @appendixsubsec Changes in release 3.21.31 (1998-06-17) @itemize @bullet @item Fixed a sign extension problem for the @code{TINYINT} type on Irix. @item Fixed problem with @code{LEFT("constant_string",function)}. @item Fixed problem with @code{FIND_IN_SET()}. @item @code{LEFT JOIN} core dumped if the second table is used with a constant @code{WHERE/ON} expression that uniquely identifies one record. @item Fixed problems with @code{DATE_FORMAT()} and incorrect dates. @code{DATE_FORMAT()} now ignores @code{'%'} to make it possible to extend it more easily in the future. @end itemize @node News-3.21.30, News-3.21.29, News-3.21.31, News-3.21.x @appendixsubsec Changes in release 3.21.30 (1998-05-11 stable) @itemize @bullet @item @code{mysql} now returns an exit code > 0 if the query returned an error. @item Saving of command-line history to file in @code{mysql} client. By Tommy Larsen @email{tommy@@mix.hive.no}. @item Fixed problem with empty lines that were ignored in @file{mysql.cc}. @item Save the pid of the signal handler thread in the pid file instead of the pid of the main thread. @item @email{tommy@@valley.ne.jp} による日本語キャラクターセット(SJIS, UJIS)のサポート. @item Changed @code{safe_mysqld} to redirect startup messages to @code{'hostname'.err} instead of @code{'hostname'.log} to reclaim file space on @code{mysqladmin refresh}. @item @code{ENUM} always had the first entry as default value. @item @code{ALTER TABLE} wrote two entries to the update log. @item @code{sql_acc()} now closes the @code{mysql} grant tables after a reload to save table space and memory. @item Changed @code{LOAD DATA} to use less memory with tables and @code{BLOB} columns. @item Sorting on a function which made a division / 0 produced a wrong set in some cases. @item Fixed @code{SELECT} problem with @code{LEFT()} when using the @code{czech} character set. @item Fixed problem in @code{isamchk}; it couldn't repair a packed table in a very unusual case. @item @code{SELECT} statements with @code{&} or @code{|} (bit functions) failed on columns with @code{NULL} values. @item When comparing a field = field, where one of the fields was a part key, only the length of the part key was compared. @end itemize @node News-3.21.29, News-3.21.28, News-3.21.30, News-3.21.x @appendixsubsec Changes in release 3.21.29 (1998-04-10) @itemize @bullet @item @code{LOCK TABLES} + @code{DELETE from tbl_name} never removed locks properly. @item Fixed problem when grouping on an @code{OR} function. @item Fixed permission problem with @code{umask()} and creating new databases. @item Fixed permission problem on result file with @code{SELECT ... INTO OUTFILE ...} @item Fixed problem in range optimizer (core dump) for a very complex query. @item Fixed problem when using @code{MIN(integer)} or @code{MAX(integer)} in @code{GROUP BY}. @item Fixed bug on Alpha when using integer keys. (Other keys worked on Alpha.) @item Fixed bug in @code{WEEK("XXXX-xx-01")}. @end itemize @node News-3.21.28, News-3.21.27, News-3.21.29, News-3.21.x @appendixsubsec Changes in release 3.21.28 (1998-04-01) @itemize @bullet @item Fixed socket permission (clients couldn't connect to Unix socket on Linux). @item Fixed bug in record caches; for some queries, you could get @code{Error from table handler: #} on some operating systems. @end itemize @node News-3.21.27, News-3.21.26, News-3.21.28, News-3.21.x @appendixsubsec Changes in release 3.21.27 (1998-03-28 gamma) @itemize @bullet @item Added user level lock functions @code{GET_LOCK(string,timeout)}, @code{RELEASE_LOCK(string)}. @item Added @code{Opened_tables} to @code{show status}. @item Changed connect timeout to 3 seconds to make it somewhat harder for crackers to kill @code{mysqld} through telnet + TCP/IP. @item Fixed bug in range optimizer when using @code{WHERE key_part_1 >= something AND key_part_2 <= something_else}. @item Changed @code{configure} for detection of FreeBSD 3.0 9803xx and above @item @code{WHERE} with @code{string_col_key = constant_string} didn't always find all rows if the column had many values differing only with characters of the same sort value (like e and @'e). @item Strings keys looked up with 'ref' were not compared in case-sensitive fashion. @item Added @code{umask()} to make log files non-readable for normal users. @item Ignore users with old (8-byte) password on startup if not using @code{--old-protocol} option to @code{mysqld}. @item @code{SELECT} which matched all key fields returned the values in the case of the matched values, not of the found values. (Minor problem.) @end itemize @node News-3.21.26, News-3.21.25, News-3.21.27, News-3.21.x @appendixsubsec Changes in release 3.21.26 @itemize @bullet @item @code{FROM_DAYS(0)} now returns "0000-00-00". @item In @code{DATE_FORMAT()}, PM and AM were swapped for hours 00 and 12. @item Extended the default maximum key size to 256. @item Fixed bug when using @code{BLOB}/@code{TEXT} in @code{GROUP BY} with many tables. @item An @code{ENUM} field that is not declared @code{NOT NULL} has @code{NULL} as the default value. (Previously, the default value was the first enumeration value.) @item Fixed bug in the join optimizer code when using many part keys on the same key: @code{INDEX (Organisation,Surname(35),Initials(35))}. @item Added some tests to the table order optimizer to get some cases with @code{SELECT ... FROM many_tables} much faster. @item Added a retry loop around @code{accept()} to possibly fix some problems on some Linux machines. @end itemize @node News-3.21.25, News-3.21.24, News-3.21.26, News-3.21.x @appendixsubsec Changes in release 3.21.25 @itemize @bullet @item Changed @code{typedef 'string'} to @code{typedef 'my_string'} for better portability. @item You can now kill threads that are waiting on a disk-full condition. @item Fixed some problems with UDF functions. @item Added long options to @code{isamchk}. Try @code{isamchk --help}. @item Fixed a bug when using 8 bytes long (alpha); @code{filesort()} didn't work. Affects @code{DISTINCT}, @code{ORDER BY} and @code{GROUP BY} on 64-bit processors. @end itemize @node News-3.21.24, News-3.21.23, News-3.21.25, News-3.21.x @appendixsubsec Changes in release 3.21.24 @itemize @bullet @item Dynamic loadable functions. Based on source from Alexis Mikhailov. @item You couldn't delete from a table if no one had done a @code{SELECT} on the table. @item Fixed problem with range optimizer with many @code{OR} operators on key parts inside each other. @item Recoded @code{MIN()} and @code{MAX()} to work properly with strings and @code{HAVING}. @item Changed default umask value for new files from @code{0664} to @code{0660}. @item Fixed problem with @code{LEFT JOIN} and constant expressions in the @code{ON} part. @item Added Italian error messages from @email{brenno@@dewinter.com}. @item @code{configure} now works better on OSF/1 (tested on 4.0D). @item Added hooks to allow @code{LIKE} optimization with international character support. @item Upgraded @code{DBI} to 0.93. @end itemize @node News-3.21.23, News-3.21.22, News-3.21.24, News-3.21.x @appendixsubsec Changes in release 3.21.23 @itemize @bullet @item The following symbols are now reserved words: @code{TIME}, @code{DATE}, @code{TIMESTAMP}, @code{TEXT}, @code{BIT}, @code{ENUM}, @code{NO}, @code{ACTION}, @code{CHECK}, @code{YEAR}, @code{MONTH}, @code{DAY}, @code{HOUR}, @code{MINUTE}, @code{SECOND}, @code{STATUS}, @code{VARIABLES}. @item Setting a @code{TIMESTAMP} to @code{NULL} in @code{LOAD DATA INFILE ...} didn't set the current time for the @code{TIMESTAMP}. @item Fix @code{BETWEEN} to recognise binary strings. Now @code{BETWEEN} is case-sensitive. @item Added @code{--skip-thread-priority} option to @code{mysqld}, for systems where @code{mysqld}'s thread scheduling doesn't work properly (BSDI 3.1). @item Added ODBC functions @code{DAYNAME()} and @code{MONTHNAME()}. @item Added function @code{TIME_FORMAT()}. This works like @code{DATE_FORMAT()}, but takes a time string (@code{'HH:MM:DD'}) as argument. @item Fixed unlikely(?) key optimizer bug when using @code{OR}s of key parts inside @code{AND}s. @item Added @code{variables} command to @code{mysqladmin}. @item A lot of small changes to the binary releases. @item Fixed a bug in the new protocol from MySQL Version 3.21.20. @item Changed @code{ALTER TABLE} to work with Windows (Windows can't rename open files). Also fixed a couple of small bugs in the Windows version. @item All standard MySQL clients are now ported to MySQL-Windows. @item MySQL can now be started as a service on NT. @end itemize @node News-3.21.22, News-3.21.21a, News-3.21.23, News-3.21.x @appendixsubsec Changes in release 3.21.22 @itemize @bullet @item Starting with this version, all MySQL distributions will be configured, compiled and tested with @code{crash-me} and the benchmarks on the following platforms: SunOS 5.6 sun4u, SunOS 5.5.1 sun4u, SunOS 4.14 sun4c, SunOS 5.6 i86pc, Irix 6.3 mips5k, HP-UX 10.20 hppa, AIX 4.2.1 ppc, OSF/1 V4.0 alpha, FreeBSD 2.2.2 i86pc and BSDI 3.1 i386. @item Fix @code{COUNT(*)} problems when the @code{WHERE} clause didn't match any records. (Bug from 3.21.17.) @item Removed that @code{NULL = NULL} is true. Now you must use @code{IS NULL} or @code{IS NOT NULL} to test whether a value is @code{NULL}. (This is according to ANSI SQL but may break old applications that are ported from @code{mSQL}.) You can get the old behaviour by compiling with @code{-DmSQL_COMPLIANT}. @item Fixed bug that core dumped when using many @code{LEFT OUTER JOIN} clauses. @item Fixed bug in @code{ORDER BY} on string formula with possible @code{NULL} values. @item Fixed problem in range optimizer when using <= on sub index. @item Added functions @code{DAYOFYEAR()}, @code{DAYOFMONTH()}, @code{MONTH()}, @code{YEAR()}, @code{WEEK()}, @code{QUARTER()}, @code{HOUR()}, @code{MINUTE()}, @code{SECOND()} and @code{FIND_IN_SET()}. @item Added command @code{SHOW VARIABLES}. @item Added support of ``long constant strings'' from ANSI SQL: @example mysql> SELECT 'first ' 'second'; -> 'first second' @end example @item Upgraded mSQL-Mysql-modules to 1.1825. @item Upgraded @code{mysqlaccess} to 2.02. @item Fixed problem with Russian character set and @code{LIKE}. @item Ported to OpenBSD 2.1. @item New Dutch error messages. @end itemize @node News-3.21.21a, News-3.21.21, News-3.21.22, News-3.21.x @appendixsubsec Changes in release 3.21.21a @itemize @bullet @item Configure changes for some operating systems. @end itemize @node News-3.21.21, News-3.21.20, News-3.21.21a, News-3.21.x @appendixsubsec Changes in release 3.21.21 @itemize @bullet @item Fixed optimizer bug when using @code{WHERE data_field = date_field2 AND date_field2 = constant}. @item Added @code{SHOW STATUS} command. @item Removed @file{manual.ps} from the source distribution to make it smaller. @end itemize @node News-3.21.20, News-3.21.19, News-3.21.21, News-3.21.x @appendixsubsec Changes in release 3.21.20 @itemize @bullet @item Changed the maximum table name and column name lengths from 32 to 64. @item Aliases can now be of ``any'' length. @item Fixed @code{mysqladmin stat} to return the right number of queries. @item Changed protocol (downward compatible) to mark if a column has the @code{AUTO_INCREMENT} attribute or is a @code{TIMESTAMP}. This is needed for the new Java driver. @item Added Hebrew sorting order by Zeev Suraski. @item Solaris 2.6: Fixed @code{configure} bugs and increased maximum table size from 2G to 4G. @end itemize @node News-3.21.19, News-3.21.18, News-3.21.20, News-3.21.x @appendixsubsec Changes in release 3.21.19 @itemize @bullet @item Upgraded @code{DBD} to 1.1823. This version implements @code{mysql_use_result} in @code{DBD-Mysql}. @item Benchmarks updated for empress (by Luuk). @item Fixed a case of slow range searching. @item Configure fixes (@file{Docs} directory). @item Added function @code{REVERSE()} (by Zeev Suraski). @end itemize @node News-3.21.18, News-3.21.17, News-3.21.19, News-3.21.x @appendixsubsec Changes in release 3.21.18 @itemize @bullet @item Issue error message if client C functions are called in wrong order. @item Added automatic reconnect to the @file{libmysql.c} library. If a write command fails, an automatic reconnect is done. @item Small sort sets no longer use temporary files. @item Upgraded @code{DBI} to 0.91. @item Fixed a couple of problems with @code{LEFT OUTER JOIN}. @item Added @code{CROSS JOIN} syntax. @code{CROSS} is now a reserved word. @item Recoded @code{yacc}/@code{bison} stack allocation to be even safer and to allow MySQL to handle even bigger expressions. @item Fixed a couple of problems with the update log. @item @code{ORDER BY} was slow when used with key ranges. @end itemize @node News-3.21.17, News-3.21.16, News-3.21.18, News-3.21.x @appendixsubsec Changes in release 3.21.17 (1997-12-20) @itemize @bullet @item Changed documentation string of @code{--with-unix-socket-path} to avoid confusion. @item Added ODBC and ANSI SQL style @code{LEFT OUTER JOIN}. @item The following are new reserved words: @code{LEFT}, @code{NATURAL}, @code{USING}. @item The client library now uses the value of the environment variable @code{MYSQL_HOST} as the default host if it's defined. @item @code{SELECT col_name, SUM(expr)} now returns @code{NULL} for @code{col_name} when there are matching rows. @item Fixed problem with comparing binary strings and @code{BLOB}s with ASCII characters over 127. @item Fixed lock problem: when freeing a read lock on a table with multiple read locks, a thread waiting for a write lock would have been given the lock. This shouldn't affect data integrity, but could possibly make @code{mysqld} restart if one thread was reading data that another thread modified. @item @code{LIMIT offset,count} didn't work in @code{INSERT ... SELECT}. @item Optimized key block caching. This will be quicker than the old algorithm when using bigger key caches. @end itemize @node News-3.21.16, News-3.21.15, News-3.21.17, News-3.21.x @appendixsubsec Changes in release 3.21.16 (1997-12-10 beta) @itemize @bullet @item Added ODBC 2.0 & 3.0 functions @code{POWER()}, @code{SPACE()}, @code{COT()}, @code{DEGREES()}, @code{RADIANS()}, @code{ROUND(2 arg)} and @code{TRUNCATE()}. @item @strong{Warning: Incompatible change!} @code{LOCATE()} parameters were swapped according to ODBC standard. Fixed. @item Added function @code{TIME_TO_SEC()}. @item In some cases, default values were not used for @code{NOT NULL} fields. @item Timestamp wasn't always updated properly in @code{UPDATE SET ...} statements. @item Allow empty strings as default values for @code{BLOB} and @code{TEXT}, to be compatible with @code{mysqldump}. @end itemize @node News-3.21.15, News-3.21.14b, News-3.21.16, News-3.21.x @appendixsubsec Changes in release 3.21.15 (1997-12-01) @itemize @bullet @item @strong{Warning: Incompatible change!} @code{mysqlperl} is now from Msql-Mysql-modules. This means that @code{connect()} now takes @code{host}, @code{database}, @code{user}, @code{password} arguments! The old version took @code{host}, @code{database}, @code{password}, @code{user}. @item Allow @code{DATE '1997-01-01'}, @code{TIME '12:10:10'} and @code{TIMESTAMP '1997-01-01 12:10:10'} formats required by ANSI SQL. @strong{Warning: Incompatible change!} This has the unfortunate side-effect that you no longer can have columns named @code{DATE}, @code{TIME} or @code{TIMESTAMP}. :( Old columns can still be accessed through @code{tablename.columnname}!) @item Changed Makefiles to hopefully work better with BSD systems. Also, @file{manual.dvi} is now included in the distribution to avoid having stupid @code{make} programs trying to rebuild it. @item @code{readline} library upgraded to version 2.1. @item A new sortorder german-1. That is a normal ISO-Latin1 with a german sort order. @item Perl @code{DBI}/@code{DBD} is now included in the distribution. @code{DBI} is now the recommended way to connect to MySQL from Perl. @item New portable benchmark suite with @code{DBD}, with test results from @code{mSQL} 2.0.3, MySQL, PostgreSQL 6.2.1 and Solid server 2.2. @item @code{crash-me} is now included with the benchmarks; This is a Perl program designed to find as many limits as possible in a SQL server. Tested with @code{mSQL}, PostgreSQL, Solid and MySQL. @item Fixed bug in range-optimizer that crashed MySQL on some queries. @item Table and column name completion for @code{mysql} command line tool, by Zeev Suraski and Andi Gutmans. @item Added new command @code{REPLACE} that works like @code{INSERT} but replaces conflicting records with the new record. @code{REPLACE INTO TABLE ... SELECT ...} works also. @item Added new commands @code{CREATE DATABASE db_name} and @code{DROP DATABASE db_name}. @item Added @code{RENAME} option to @code{ALTER TABLE}: @code{ALTER TABLE name RENAME TO new_name}. @item @code{make_binary_distribution} now includes @file{libgcc.a} in @file{libmysqlclient.a}. This should make linking work for people who don't have @code{gcc}. @item Changed @code{net_write()} to @code{my_net_write()} because of a name conflict with Sybase. @item @cindex ODBC compatibility @cindex Compatibility, with ODBC New function @code{DAYOFWEEK()} compatible with ODBC. @item Stack checking and @code{bison} memory overrun checking to make MySQL safer with weird queries. @end itemize @node News-3.21.14b, News-3.21.14a, News-3.21.15, News-3.21.x @appendixsubsec Changes in release 3.21.14b @itemize @bullet @item Fixed a couple of small @code{configure} problems on some platforms. @end itemize @node News-3.21.14a, News-3.21.13, News-3.21.14b, News-3.21.x @appendixsubsec Changes in release 3.21.14a (1997-11-12) @itemize @bullet @item Ported to SCO Openserver 5.0.4 with FSU Pthreads. @item HP-UX 10.20 should work. @item Added new function @code{DATE_FORMAT()}. @item Added @code{NOT IN}. @item Added automatic removal of 'ODBC function conversions': @code{@{fn now() @}} @item Handle ODBC 2.50.3 option flags. @item Fixed comparison of @code{DATE} and @code{TIME} values with @code{NULL}. @item Changed language name from germany to german to be consistent with the other language names. @item Fixed sorting problem on functions returning a @code{FLOAT}. Previously, the values were converted to @code{INT}s before sorting. @item Fixed slow sorting when sorting on key field when using @code{key_column=constant}. @item Sorting on calculated @code{DOUBLE} values sorted on integer results instead. @item @code{mysql} no longer requires a database argument. @item Changed the place where @code{HAVING} should be. According to ANSI, it should be after @code{GROUP BY} but before @code{ORDER BY}. MySQL Version 3.20 incorrectly had it last. @item Added Sybase command @code{USE DATABASE} to start using another database. @item Added automatic adjusting of number of connections and table cache size if the maximum number of files that can be opened is less than needed. This should fix that @code{mysqld} doesn't crash even if you haven't done a @code{ulimit -n 256} before starting @code{mysqld}. @item Added lots of limit checks to make it safer when running with too little memory or when doing weird queries. @end itemize @node News-3.21.13, News-3.21.12, News-3.21.14a, News-3.21.x @appendixsubsec Changes in release 3.21.13 @itemize @bullet @item Added retry of interrupted reads and clearing of @code{errno}. This makes Linux systems much safer! @item Fixed locking bug when using many aliases on the same table in the same @code{SELECT}. @item Fixed bug with @code{LIKE} on number key. @item New error message so you can check whether the connection was lost while the command was running or whether the connection was down from the start. @item Added @code{--table} option to @code{mysql} to print in table format. Moved time and row information after query result. Added automatic reconnect of lost connections. @item Added @code{!=} as a synonym for @code{<>}. @item Added function @code{VERSION()} to make easier logs. @item New multi-user test @file{tests/fork_test.pl} to put some strain on the thread library. @end itemize @node News-3.21.12, News-3.21.11, News-3.21.13, News-3.21.x @appendixsubsec Changes in release 3.21.12 @itemize @bullet @item Fixed @code{ftruncate()} call in MIT-pthreads. This made @code{isamchk} destroy the @file{.ISM} files on (Free)BSD 2.x systems. @item Fixed broken @code{__P_} patch in MIT-pthreads. @item Many memory overrun checks. All string functions now return @code{NULL} if the returned string should be longer than @code{max_allowed_packet} bytes. @item Changed the name of the @code{INTERVAL} type to @code{ENUM}, because @code{INTERVAL} is used in ANSI SQL. @item In some cases, doing a @code{JOIN} + @code{GROUP} + @code{INTO OUTFILE}, the result wasn't grouped. @item @code{LIKE} with @code{'_'} as last character didn't work. Fixed. @item Added extended ANSI SQL @code{TRIM()} function. @item Added @code{CURTIME()}. @item Added @code{ENCRYPT()} function by Zeev Suraski. @item Fixed better @code{FOREIGN KEY} syntax skipping. New reserved words: @code{MATCH}, @code{FULL}, @code{PARTIAL}. @item @code{mysqld} now allows IP number and hostname for the @code{--bind-address} option. @item Added @code{SET CHARACTER SET cp1251_koi8} to enable conversions of data to and from the @code{cp1251_koi8} character set. @item Lots of changes for Windows 95 port. In theory, this version should now be easily portable to Windows 95. @item Changed the @code{CREATE COLUMN} syntax of @code{NOT NULL} columns to be after the @code{DEFAULT} value, as specified in the ANSI SQL standard. This will make @code{mysqldump} with @code{NOT NULL} and default values incompatible with MySQL Version 3.20. @item Added many function name aliases so the functions can be used with ODBC or ANSI SQL92 syntax. @item Fixed syntax of @code{ALTER TABLE tbl_name ALTER COLUMN col_name SET DEFAULT NULL}. @item Added @code{CHAR} and @code{BIT} as synonyms for @code{CHAR(1)}. @item Fixed core dump when updating as a user who has only @code{SELECT} privilege. @item @code{INSERT ... SELECT ... GROUP BY} didn't work in some cases. An @code{Invalid use of group function} error occurred. @item When using @code{LIMIT}, @code{SELECT} now always uses keys instead of record scan. This will give better performance on @code{SELECT} and a @code{WHERE} that matches many rows. @item Added Russian error messages. @end itemize @node News-3.21.11, News-3.21.10, News-3.21.12, News-3.21.x @appendixsubsec Changes in release 3.21.11 (1997-10-16) @itemize @bullet @item Configure changes. @item MySQL now works with the new thread library on BSD/OS 3.0. @item Added new group functions @code{BIT_OR()} and @code{BIT_AND()}. @item Added compatibility functions @code{CHECK} and @code{REFERENCES}. @code{CHECK} is now a reserved word. @item Added @code{ALL} option to @code{GRANT} for better compatibility. (@code{GRANT} is still a dummy function.) @item Added partly-translated Dutch error messages. @item Fixed bug in @code{ORDER BY} and @code{GROUP BY} with @code{NULL} columns. @item Added function @code{LAST_INSERT_ID()} SQL function to retrieve last @code{AUTO_INCREMENT} value. This is intended for clients to ODBC that can't use the @code{mysql_insert_id()} API function, but can be used by any client. @item Added @code{--flush-logs} option to @code{mysqladmin}. @item Added command @code{STATUS} to @code{mysql}. @item Fixed problem with @code{ORDER BY}/@code{GROUP BY} because of bug in @code{gcc}. @item Fixed problem with @code{INSERT ... SELECT ... GROUP BY}. @end itemize @node News-3.21.10, News-3.21.9, News-3.21.11, News-3.21.x @appendixsubsec Changes in release 3.21.10 @itemize @bullet @item New @code{mysqlaccess}. @item @code{CREATE} now supports all ODBC types and the @code{mSQL} @code{TEXT} type. All ODBC 2.5 functions are also supported (added @code{REPEAT}). This provides better portability. @item Added text types @code{TINYTEXT}, @code{TEXT}, @code{MEDIUMTEXT} and @code{LONGTEXT}. These are actually @code{BLOB}types, but all searching is done in case-insensitive fashion. @item All old @code{BLOB} fields are now @code{TEXT} fields. This only changes that all searching on strings is done in case-sensitive fashion. You must do an @code{ALTER TABLE} and change the field type to @code{BLOB} if you want to have tests done in case-sensitive fashion. @item Fixed some @code{configure} issues. @item Made the locking code a bit safer. Fixed very unlikely deadlock situation. @item Fixed a couple of bugs in the range optimizer. Now the new range benchmark @code{test-select} works. @end itemize @node News-3.21.9, News-3.21.8, News-3.21.10, News-3.21.x @appendixsubsec Changes in release 3.21.9 (1997-09-28) @itemize @bullet @item Added @code{--enable-unix-socket=pathname} option to @code{configure}. @item Fixed a couple of portability problems with include files. @item Fixed bug in range calculation that could return empty set when searching on multiple key with only one entry (very rare). @item Most things ported to FSU Pthreads, which should allow MySQL to run on Caldera (SCO). @xref{Caldera}. @end itemize @node News-3.21.8, News-3.21.7, News-3.21.9, News-3.21.x @appendixsubsec Changes in release 3.21.8 @itemize @bullet @item Works now in Solaris 2.6. @item Added handling of calculation of @code{SUM()} functions. For example, you can now use @code{SUM(column)/COUNT(column)}. @item Added handling of trigometric functions: @code{PI()}, @code{ACOS()}, @code{ASIN()}, @code{ATAN()}, @code{COS()}, @code{SIN()} and @code{TAN()}. @item New languages: norwegian, norwegian-ny and portuguese. @item Fixed parameter bug in @code{net_print()} in @file{procedure.cc}. @item Fixed a couple of memory leaks. @item Now allow also the old @code{SELECT ... INTO OUTFILE} syntax. @item Fixed bug with @code{GROUP BY} and @code{SELECT} on key with many values. @item @code{mysql_fetch_lengths()} sometimes returned incorrect lengths when you used @code{mysql_use_result()}. This affected at least some cases of @code{mysqldump --quick}. @item Fixed bug in optimization of @code{WHERE const op field}. @item Fixed problem when sorting on @code{NULL} fields. @item Fixed a couple of 64-bit (Alpha) problems. @item Added @code{--pid-file=#} option to @code{mysqld}. @item Added date formatting to @code{FROM_UNIXTIME()}, originally by Zeev Suraski. @item Fixed bug in @code{BETWEEN} in range optimizer (did only test = of the first argument). @item Added machine-dependent files for MIT-pthreads i386-SCO. There is probably more to do to get this to work on SCO 3.5. @end itemize @node News-3.21.7, News-3.21.6, News-3.21.8, News-3.21.x @appendixsubsec Changes in release 3.21.7 @itemize @bullet @item Changed @file{Makefile.am} to take advantage of Automake 1.2. @item Added the beginnings of a benchmark suite. @item Added more secure password handling. @item Added new client function @code{mysql_errno()}, to get the error number of the error message. This makes error checking in the client much easier. This makes the new server incompatible with the 3.20.x server when running without @code{--old-protocol}. The client code is backward-compatible. More information can be found in the @file{README} file! @item Fixed some problems when using very long, illegal names. @end itemize @node News-3.21.6, News-3.21.5, News-3.21.7, News-3.21.x @appendixsubsec Changes in release 3.21.6 @itemize @bullet @item Fixed more portability issues (incorrect @code{sigwait} and @code{sigset} defines). @item @code{configure} should now be able to detect the last argument to @code{accept()}. @end itemize @node News-3.21.5, News-3.21.4, News-3.21.6, News-3.21.x @appendixsubsec Changes in release 3.21.5 @itemize @bullet @item Should now work with FreeBSD 3.0 if used with @file{FreeBSD-3.0-libc_r-1.0.diff}, which can be found at @uref{http://www.mysql.com/downloads/patches.html}. @item Added new @code{-O tmp_table_size=#} option to @code{mysqld}. @item New function @code{FROM_UNIXTIME(timestamp)} which returns a date string in @code{'YYYY-MM-DD HH:MM:DD'} format. @item New function @code{SEC_TO_TIME(seconds)} which returns a string in @code{'HH:MM:SS'} format. @item New function @code{SUBSTRING_INDEX()}, originally by Zeev Suraski. @end itemize @node News-3.21.4, News-3.21.3, News-3.21.5, News-3.21.x @appendixsubsec Changes in release 3.21.4 @itemize @bullet @item Should now configure and compile on OSF/1 4.0 with the DEC compiler. @item Configuration and compilation on BSD/OS 3.0 works, but due to some bugs in BSD/OS 3.0, @code{mysqld} doesn't work on it yet. @item Configuration and compilation on FreeBSD 3.0 works, but I couldn't get @code{pthread_create} to work. @end itemize @node News-3.21.3, News-3.21.2, News-3.21.4, News-3.21.x @appendixsubsec Changes in release 3.21.3 @itemize @bullet @item Added reverse check lookup of hostnames to get better security. @item Fixed some possible buffer overflows if filenames that are too long are used. @item @code{mysqld} doesn't accept hostnames that start with digits followed by a @code{'.'}, because the hostname may look like an IP number. @item Added @code{--skip-networking} option to @code{mysqld}, to allow only socket connections. (This will not work with MIT-pthreads!) @item Added check of too long table names for alias. @item Added check if database name is okay. @item Added check if too long table names. @item Removed incorrect @code{free()} that killed the server on @code{CREATE DATABASE} or @code{DROP DATABASE}. @item Changed some @code{mysqld} @code{-O} options to better names. @item Added @code{-O join_cache_size=#} option to @code{mysqld}. @item Added @code{-O max_join_size=#} option to @code{mysqld}, to be able to set a limit how big queries (in this case big = slow) one should be able to handle without specifying @code{SET SQL_BIG_SELECTS=1}. A # = is about 10 examined records. The default is ``unlimited''. @item When comparing a @code{TIME}, @code{DATE}, @code{DATETIME} or @code{TIMESTAMP} column to a constant, the constant is converted to a time value before performing the comparison. This will make it easier to get ODBC (particularly Access97) to work with the above types. It should also make dates easier to use and the comparisons should be quicker than before. @item Applied patch from Jochen Wiedmann that allows @code{query()} in @code{mysqlperl} to take a query with @code{\0} in it. @item Storing a timestamp with a 2-digit year (@code{YYMMDD}) didn't work. @item Fix that timestamp wasn't automatically updated if set in an @code{UPDATE} clause. @item Now the automatic timestamp field is the FIRST timestamp field. @item @code{SELECT * INTO OUTFILE}, which didn't correctly if the outfile already existed. @item @code{mysql} now shows the thread ID when starting or doing a reconnect. @item Changed the default sort buffer size from 2M to 1M. @end itemize @node News-3.21.2, News-3.21.0, News-3.21.3, News-3.21.x @appendixsubsec Changes in release 3.21.2 @itemize @bullet @item The range optimizer is coded, but only 85% tested. It can be enabled with @code{--new}, but it crashes core a lot yet... @item More portable. Should compile on AIX and alpha-digital. At least the @code{isam} library should be relatively 64-bit clean. @item New @code{isamchk} which can detect and fix more problems. @item New options for @code{isamlog}. @item Using new version of Automake. @item Many small portability changes (from the AIX and alpha-digital port) Better checking of pthread(s) library. @item czech error messages by @email{snajdr@@pvt.net}. @item Decreased size of some buffers to get fewer problems on systems with little memory. Also added more checks to handle ``out of memory'' problems. @item @code{mysqladmin}: you can now do @code{mysqladmin kill 5,6,7,8} to kill multiple threads. @item When the maximum connection limit is reached, one extra connection by a user with the @strong{process_acl} privilege is granted. @item Added @code{-O backlog=#} option to @code{mysqld}. @item Increased maximum packet size from 512K to 1024K for client. @item Almost all of the function code is now tested in the internal test suite. @item @code{ALTER TABLE} now returns warnings from field conversions. @item Port changed to 3306 (got it reserved from ISI). @item Added a fix for Visual FoxBase so that any schema name from a table specification is automatically removed. @item New function @code{ASCII()}. @item Removed function @code{BETWEEN(a,b,c)}. Use the standard ANSI syntax instead: @code{expr BETWEEN expr AND expr}. @item MySQL no longer has to use an extra temporary table when sorting on functions or @code{SUM()} functions. @item Fixed bug that you couldn't use @code{tbl_name.field_name} in @code{UPDATE}. @item Fixed @code{SELECT DISTINCT} when using 'hidden group'. For example: @example mysql> SELECT DISTINCT MOD(some_field,10) FROM test -> GROUP BY some_field; @end example Note: @code{some_field} is normally in the @code{SELECT} part. ANSI SQL should require it. @end itemize @node News-3.21.0, , News-3.21.2, News-3.21.x @appendixsubsec Changes in release 3.21.0 @itemize @bullet @item New reserved words used: @code{INTERVAL}, @code{EXPLAIN}, @code{READ}, @code{WRITE}, @code{BINARY}. @item Added ODBC function @code{CHAR(num,...)}. @item New operator @code{IN}. This uses a binary search to find a match. @item New command @code{LOCK TABLES tbl_name [AS alias] @{READ|WRITE@} ...} @item Added @code{--log-update} option to @code{mysqld}, to get a log suitable for incremental updates. @item New command @code{EXPLAIN SELECT ...} to get information about how the optimizer will do the join. @item For easier client code, the client should no longer use @code{FIELD_TYPE_TINY_BLOB}, @code{FIELD_TYPE_MEDIUM_BLOB}, @code{FIELD_TYPE_LONG_BLOB} or @code{FIELD_TYPE_VAR_STRING} (as previously returned by @code{mysql_list_fields}). You should instead only use @code{FIELD_TYPE_BLOB} or @code{FIELD_TYPE_STRING}. If you want exact types, you should use the command @code{SHOW FIELDS}. @item Added varbinary syntax: @code{0x######} which can be used as a string (default) or a number. @item @code{FIELD_TYPE_CHAR} is renamed to @code{FIELD_TYPE_TINY}. @item Changed all fields to C++ classes. @item Removed FORM struct. @item Fields with @code{DEFAULT} values no longer need to be @code{NOT NULL}. @item New field types: @table @code @item ENUM A string which can take only a couple of defined values. The value is stored as a 1-3 byte number that is mapped automatically to a string. This is sorted according to string positions! @item SET A string which may have one or many string values separated with ','. The string is stored as a 1-, 2-, 3-, 4- or 8-byte number where each bit stands for a specific set member. This is sorted according to the unsigned value of the stored packed number. @end table @item Now all function calculation is done with @code{double} or @code{long long}. This will provide the full 64-bit range with bit functions and fix some conversions that previously could result in precision losses. One should avoid using @code{unsigned long long} columns with full 64-bit range (numbers bigger than 9223372036854775807) because calculations are done with @code{signed long long}. @item @code{ORDER BY} will now put @code{NULL} field values first. @code{GROUP BY} will also work with @code{NULL} values. @item Full @code{WHERE} with expressions. @item New range optimizer that can resolve ranges when some keypart prefix is constant. Example: @example mysql> SELECT * FROM tbl_name -> WHERE key_part_1="customer" -> AND key_part_2>=10 AND key_part_2<=10; @end example @end itemize @node News-3.20.x, News-3.19.x, News-3.21.x, News @appendixsec Changes in release 3.20.x Version 3.20 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only. Changes from 3.20.18 to 3.20.32b are not documented here because the 3.21 release branched here. And the relevant changes are also documented as changes to the 3.21 version. @menu * News-3.20.18:: Changes in release 3.20.18 * News-3.20.17:: Changes in release 3.20.17 * News-3.20.16:: Changes in release 3.20.16 * News-3.20.15:: Changes in release 3.20.15 * News-3.20.14:: Changes in release 3.20.14 * News-3.20.13:: Changes in release 3.20.13 * News-3.20.11:: Changes in release 3.20.11 * News-3.20.10:: Changes in release 3.20.10 * News-3.20.9:: Changes in release 3.20.9 * News-3.20.8:: Changes in release 3.20.8 * News-3.20.7:: Changes in release 3.20.7 * News-3.20.6:: Changes in release 3.20.6 * News-3.20.3:: Changes in release 3.20.3 * News-3.20.0:: Changes in releases 3.20.0 @end menu @node News-3.20.18, News-3.20.17, News-3.20.x, News-3.20.x @appendixsubsec Changes in release 3.20.18 @itemize @bullet @item Added @code{-p#} (remove @code{#} directories from path) to @code{isamlog}. All files are written with a relative path from the database directory Now @code{mysqld} shouldn't crash on shutdown when using the @code{--log-isam} option. @item New @code{mysqlperl} version. It is now compatible with @code{msqlperl-0.63}. @item New @code{DBD} module available. @item Added group function @code{STD()} (standard deviation). @item The @code{mysqld} server is now compiled by default without debugging information. This will make the daemon smaller and faster. @item Now one usually only has to specify the @code{--basedir} option to @code{mysqld}. All other paths are relative in a normal installation. @item @code{BLOB} columns sometimes contained garbage when used with a @code{SELECT} on more than one table and @code{ORDER BY}. @item Fixed that calculations that are not in @code{GROUP BY} work as expected (ANSI SQL extension). Example: @example mysql> SELECT id,id+1 FROM table GROUP BY id; @end example @item The test of using @code{MYSQL_PWD} was reversed. Now @code{MYSQL_PWD} is enabled as default in the default release. @item Fixed conversion bug which caused @code{mysqld} to core dump with Arithmetic error on SPARC-386. @item Added @code{--unbuffered} option to @code{mysql}, for new @code{mysqlaccess}. @item When using overlapping (unnecessary) keys and join over many tables, the optimizer could get confused and return 0 records. @end itemize @node News-3.20.17, News-3.20.16, News-3.20.18, News-3.20.x @appendixsubsec Changes in release 3.20.17 (1997-04-13) @itemize @bullet @item You can now use @code{BLOB} columns and the functions @code{IS NULL} and @code{IS NOT NULL} in the @code{WHERE} clause. @item All communication packets and row buffers are now allocated dynamically on demand. The default value of @code{max_allowed_packet} is now 64K for the server and 512K for the client. This is mainly used to catch incorrect packets that could trash all memory. The server limit may be changed when it is started. @item Changed stack usage to use less memory. @item Changed @code{safe_mysqld} to check for running daemon. @item The @code{ELT()} function is renamed to @code{FIELD()}. The new @code{ELT()} function returns a value based on an index: @code{FIELD()} is the inverse of @code{ELT()} Example: @code{ELT(2,"A","B","C")} returns @code{"B"}. @code{FIELD("B","A","B","C")} returns @code{2}. @item @code{COUNT(field)}, where @code{field} could have a @code{NULL} value, now works. @item A couple of bugs fixed in @code{SELECT ... GROUP BY}. @item Fixed memory overrun bug in @code{WHERE} with many unoptimizable brace levels. @item Fixed some small bugs in the grant code. @item If hostname isn't found by @code{get_hostname}, only the IP is checked. Previously, you got @code{Access denied}. @item Inserts of timestamps with values didn't always work. @item @code{INSERT INTO ... SELECT ... WHERE} could give the error @code{Duplicated field}. @item Added some tests to @code{safe_mysqld} to make it ``safer''. @item @code{LIKE} was case-sensitive in some places and case-insensitive in others. Now @code{LIKE} is always case-insensitive. @item @file{mysql.cc}: Allow @code{'#'} anywhere on the line. @item New command @code{SET SQL_SELECT_LIMIT=#}. See the FAQ for more details. @item New version of the @code{mysqlaccess} script. @item Change @code{FROM_DAYS()} and @code{WEEKDAY()} to also take a full @code{TIMESTAMP} or @code{DATETIME} as argument. Before they only took a number of type @code{YYYYMMDD} or @code{YYMMDD}. @item Added new function @code{UNIX_TIMESTAMP(timestamp_column)}. @end itemize @node News-3.20.16, News-3.20.15, News-3.20.17, News-3.20.x @appendixsubsec Changes in release 3.20.16 @itemize @bullet @item More changes in MIT-pthreads to get them safer. Fixed also some link bugs at least in SunOS. @item Changed @code{mysqld} to work around a bug in MIT-pthreads. This makes multiple small @code{SELECT} operations 20 times faster. Now @code{lock_test.pl} should work. @item Added @code{mysql_FetchHash(handle)} to @code{mysqlperl}. @item The @code{mysqlbug} script is now distributed built to allow for reporting bugs that appear during the build with it. @item Changed @file{libmysql.c} to prefer @code{getpwuid()} instead of @code{cuserid()}. @item Fixed bug in @code{SELECT} optimizer when using many tables with the same column used as key to different tables. @item Added new @code{latin2} and Russian @code{KOI8} character tables. @item Added support for a dummy @code{GRANT} command to satisfy Powerbuilder. @end itemize @node News-3.20.15, News-3.20.14, News-3.20.16, News-3.20.x @appendixsubsec Changes in release 3.20.15 @itemize @bullet @item Fixed fatal bug @code{packets out of order} when using MIT-pthreads. @item Removed possible loop when a thread waits for command from client and @code{fcntl()} fails. Thanks to Mike Bretz for finding this bug. @item Changed alarm loop in @file{mysqld.cc} because shutdown didn't always succeed in Linux. @item Removed use of @code{termbits} from @file{mysql.cc}. This conflicted with @code{glibc} 2.0. @item Fixed some syntax errors for at least BSD and Linux. @item Fixed bug when doing a @code{SELECT} as superuser without a database. @item Fixed bug when doing @code{SELECT} with group calculation to outfile. @end itemize @node News-3.20.14, News-3.20.13, News-3.20.15, News-3.20.x @appendixsubsec Changes in release 3.20.14 @itemize @bullet @item If one gives @code{-p} or @code{--password} option to @code{mysql} without an argument, the user is solicited for the password from the tty. @item Added default password from @code{MYSQL_PWD} (by Elmar Haneke). @item Added command @code{kill} to @code{mysqladmin} to kill a specific MySQL thread. @item Sometimes when doing a reconnect on a down connection this succeeded first on second try. @item Fixed adding an @code{AUTO_INCREMENT} key with @code{ALTER_TABLE}. @item @code{AVG()} gave too small value on some @code{SELECT}s with @code{GROUP BY} and @code{ORDER BY}. @item Added new @code{DATETIME} type (by Giovanni Maruzzelli @email{maruzz@@matrice.it}). @item Fixed that defining @code{DONT_USE_DEFAULT_FIELDS} works. @item Changed to use a thread to handle alarms instead of signals on Solaris to avoid race conditions. @item Fixed default length of signed numbers. (George Harvey @email{georgeh@@pinacl.co.uk}.) @item Allow anything for @code{CREATE INDEX}. @item Add prezeros when packing numbers to @code{DATE}, @code{TIME} and @code{TIMESTAMP}. @item Fixed a bug in @code{OR} of multiple tables (gave empty set). @item Added many patches to MIT-pthreads. This fixes at least one lookup bug. @end itemize @node News-3.20.13, News-3.20.11, News-3.20.14, News-3.20.x @appendixsubsec Changes in release 3.20.13 @itemize @bullet @item Added ANSI SQL94 @code{DATE} and @code{TIME} types. @item Fixed bug in @code{SELECT} with @code{AND}-@code{OR} levels. @item Added support for Slovenian characters. The @file{Contrib} directory contains source and instructions for adding other character sets. @item Fixed bug with @code{LIMIT} and @code{ORDER BY}. @item Allow @code{ORDER BY} and @code{GROUP BY} on items that aren't in the @code{SELECT} list. (Thanks to Wim Bonis @email{bonis@@kiss.de}, for pointing this out.) @item Allow setting of timestamp values in @code{INSERT}. @item Fixed bug with @code{SELECT ... WHERE ... = NULL}. @item Added changes for @code{glibc} 2.0. To get @code{glibc} to work, you should add the @file{gibc-2.0-sigwait-patch} before compiling @code{glibc}. @item Fixed bug in @code{ALTER TABLE} when changing a @code{NOT NULL} field to allow @code{NULL} values. @item Added some ANSI92 synonyms as field types to @code{CREATE TABLE}. @code{CREATE TABLE} now allows @code{FLOAT(4)} and @code{FLOAT(8)} to mean @code{FLOAT} and @code{DOUBLE}. @item New utility program @code{mysqlaccess} by @email{Yves.Carlier@@rug.ac.be}. This program shows the access rights for a specific user and the grant rows that determine this grant. @item Added @code{WHERE const op field} (by @email{bonis@@kiss.de}). @end itemize @node News-3.20.11, News-3.20.10, News-3.20.13, News-3.20.x @appendixsubsec Changes in release 3.20.11 @itemize @bullet @item When using @code{SELECT ... INTO OUTFILE}, all temporary tables are ISAM instead of HEAP to allow big dumps. @item Changed date functions to be string functions. This fixed some ``funny'' side effects when sorting on dates. @item Extended @code{ALTER TABLE} according to SQL92. @item Some minor compatibility changes. @item Added @code{--port} and @code{--socket} options to all utility programs and @code{mysqld}. @item Fixed MIT-pthreads @code{readdir_r()}. Now @code{mysqladmin create database} and @code{mysqladmin drop database} should work. @item Changed MIT-pthreads to use our @code{tempnam()}. This should fix the ``sort aborted'' bug. @item Added sync of records count in @code{sql_update}. This fixed slow updates on first connection. (Thanks to Vaclav Bittner for the test.) @end itemize @node News-3.20.10, News-3.20.9, News-3.20.11, News-3.20.x @appendixsubsec Changes in release 3.20.10 @itemize @bullet @item New insert type: @code{INSERT INTO ... SELECT ...} @item @code{MEDIUMBLOB} fixed. @item Fixed bug in @code{ALTER TABLE} and @code{BLOB}s. @item @code{SELECT ... INTO OUTFILE} now creates the file in the current database directory. @item @code{DROP TABLE} now can take a list of tables. @item Oracle synonym @code{DESCRIBE} (@code{DESC}). @item Changes to @code{make_binary_distribution}. @item Added some comments to installation instructions about @code{configure}'s C++ link test. @item Added @code{--without-perl} option to @code{configure}. @item Lots of small portability changes. @end itemize @node News-3.20.9, News-3.20.8, News-3.20.10, News-3.20.x @appendixsubsec Changes in release 3.20.9 (1997-02-13) @itemize @bullet @item @code{ALTER TABLE} didn't copy null bit. As a result, fields that were allowed to have @code{NULL} values were always @code{NULL}. @item @code{CREATE} didn't take numbers as @code{DEFAULT}. @item Some compatibility changes for SunOS. @item Removed @file{config.cache} from old distribution. @end itemize @node News-3.20.8, News-3.20.7, News-3.20.9, News-3.20.x @appendixsubsec Changes in release 3.20.8 @itemize @bullet @item Fixed bug with @code{ALTER TABLE} and multi-part keys. @end itemize @node News-3.20.7, News-3.20.6, News-3.20.8, News-3.20.x @appendixsubsec Changes in release 3.20.7 @itemize @bullet @item New commands: @code{ALTER TABLE}, @code{SELECT ... INTO OUTFILE} and @code{LOAD DATA INFILE}. @item New function: @code{NOW()}. @item Added new field @code{File_priv} to @code{mysql/user} table. @item New script @code{add_file_priv} which adds the new field @code{File_priv} to the @code{user} table. This script must be executed if you want to use the new @code{SELECT ... INTO} and @code{LOAD DATA INFILE ...} commands with a version of MySQL earlier than 3.20.7. @item Fixed bug in locking code, which made @code{lock_test.pl} test fail. @item New files @file{NEW} and @file{BUGS}. @item Changed @file{select_test.c} and @file{insert_test.c} to include @file{config.h}. @item Added @code{status} command to @code{mysqladmin} for short logging. @item Increased maximum number of keys to 16 and maximum number of key parts to 15. @item Use of sub keys. A key may now be a prefix of a string field. @item Added @code{-k} option to @code{mysqlshow}, to get key information for a table. @item Added long options to @code{mysqldump}. @end itemize @node News-3.20.6, News-3.20.3, News-3.20.7, News-3.20.x @appendixsubsec Changes in release 3.20.6 (1997-01-31) @itemize @bullet @item Portable to more systems because of MIT-pthreads, which will be used automatically if @code{configure} cannot find a @code{-lpthreads} library. @item Added GNU-style long options to almost all programs. Test with @code{@kbd{program} --help}. @item Some shared library support for Linux. @item The FAQ is now in @file{.texi} format and is available in @file{.html}, @file{.txt} and @file{.ps} formats. @item Added new SQL function @code{RAND([init])}. @item Changed @code{sql_lex} to handle @code{\0} unquoted, but the client can't send the query through the C API, because it takes a str pointer. You must use @code{mysql_real_query()} to send the query. @item Added API function @code{mysql_get_client_info()}. @item @code{mysqld} now uses the @code{N_MAX_KEY_LENGTH} from @file{nisam.h} as the maximum allowable key length. @item The following now works: @example mysql> SELECT filter_nr,filter_nr FROM filter ORDER BY filter_nr; @end example Previously, this resulted in the error: @code{Column: 'filter_nr' in order clause is ambiguous}. @item @code{mysql} now outputs @code{'\0'}, @code{'\t'}, @code{'\n'} and @code{'\\'} when encountering ASCII 0, tab, newline or @code{'\'} while writing tab-separated output. This is to allow printing of binary data in a portable format. To get the old behaviour, use @code{-r} (or @code{--raw}). @item Added german error messages (60 of 80 error messages translated). @item Added new API function @code{mysql_fetch_lengths(MYSQL_RES *)}, which returns an array of column lengths (of type @code{uint}). @item Fixed bug with @code{IS NULL} in @code{WHERE} clause. @item Changed the optimizer a little to get better results when searching on a key part. @item Added @code{SELECT} option @code{STRAIGHT_JOIN} to tell the optimizer that it should join tables in the given order. @item Added support for comments starting with @code{'--'} in @file{mysql.cc} (Postgres syntax). @item You can have @code{SELECT} expressions and table columns in a @code{SELECT} which are not used in the group part. This makes it efficient to implement lookups. The column that is used should be a constant for each group because the value is calculated only once for the first row that is found for a group. @example mysql> SELECT id,lookup.text,SUM(*) FROM test,lookup -> WHERE test.id=lookup.id GROUP BY id; @end example @item Fixed bug in @code{SUM(function)} (could cause a core dump). @item Changed @code{AUTO_INCREMENT} placement in the SQL query: @example INSERT INTO table (auto_field) VALUES (0); @end example inserted 0, but it should insert an @code{AUTO_INCREMENT} value. @item @file{mysqlshow.c}: Added number of records in table. Had to change the client code a little to fix this. @item @code{mysql} now allows doubled @code{''} or @code{""} within strings for embedded @code{'} or @code{"}. @item New math functions: @code{EXP()}, @code{LOG()}, @code{SQRT()}, @code{ROUND()}, @code{CEILING()}. @end itemize @node News-3.20.3, News-3.20.0, News-3.20.6, News-3.20.x @appendixsubsec Changes in release 3.20.3 @itemize @bullet @item The @code{configure} source now compiles a thread-free client library @code{-lmysqlclient}. This is the only library that needs to be linked with client applications. When using the binary releases, you must link with @code{-lmysql -lmysys -ldbug -lmystrings} as before. @item New @code{readline} library from @code{bash-2.0}. @item LOTS of small changes to @code{configure} and makefiles (and related source). @item It should now be possible to compile in another directory using @code{VPATH}. Tested with GNU Make 3.75. @item @code{safe_mysqld} and @code{mysql.server} changed to be more compatible between the source and the binary releases. @item @code{LIMIT} now takes one or two numeric arguments. If one argument is given, it indicates the maximum number of rows in a result. If two arguments are given, the first argument indicates the offset of the first row to return, the second is the maximum number of rows. With this it's easy to do a poor man's next page/previous page WWW application. @item Changed name of SQL function @code{FIELDS()} to @code{ELT()}. Changed SQL function @code{INTERVALL()} to @code{INTERVAL()}. @item Made @code{SHOW COLUMNS} a synonym for @code{SHOW FIELDS}. Added compatibility syntax @code{FRIEND KEY} to @code{CREATE TABLE}. In MySQL, this creates a non-unique key on the given columns. @item Added @code{CREATE INDEX} and @code{DROP INDEX} as compatibility functions. In MySQL, @code{CREATE INDEX} only checks if the index exists and issues an error if it doesn't exist. @code{DROP INDEX} always succeeds. @item @file{mysqladmin.c}: added client version to version information. @item Fixed core dump bug in @code{sql_acl} (core on new connection). @item Removed @code{host}, @code{user} and @code{db} tables from database @code{test} in the distribution. @item @code{FIELD_TYPE_CHAR} can now be signed (-128 to 127) or unsigned (0 to 255) Previously, it was always unsigned. @item Bug fixes in @code{CONCAT()} and @code{WEEKDAY()}. @item Changed a lot of source to get @code{mysqld} to be compiled with SunPro compiler. @item SQL functions must now have a @code{'('} immediately after the function name (no intervening space). For example, @code{'USER('} is regarded as beginning a function call, and @code{'USER ('} is regarded as an identifier @code{USER} followed by a @code{'('}, not as a function call. @end itemize @node News-3.20.0, , News-3.20.3, News-3.20.x @appendixsubsec Changes in release 3.20.0 @itemize @bullet @item The source distribution is done with @code{configure} and Automake. It will make porting much easier. The @code{readline} library is included in the distribution. @item Separate client compilation: the client code should be very easy to compile on systems which don't have threads. @item The old Perl interface code is automatically compiled and installed. Automatic compiling of @code{DBD} will follow when the new @code{DBD} code is ported. @item Dynamic language support: @code{mysqld} can now be started with Swedish or English (default) error messages. @item New functions: @code{INSERT()}, @code{RTRIM()}, @code{LTRIM()} and @code{FORMAT()}. @item @code{mysqldump} now works correctly for all field types (even @code{AUTO_INCREMENT}). The format for @code{SHOW FIELDS FROM tbl_name} is changed so the @code{Type} column contains information suitable for @code{CREATE TABLE}. In previous releases, some @code{CREATE TABLE} information had to be patched when re-creating tables. @item Some parser bugs from 3.19.5 (@code{BLOB} and @code{TIMESTAMP}) are corrected. @code{TIMESTAMP} now returns different date information depending on its create length. @item Changed parser to allow a database, table or field name to start with a number or @code{'_'}. @item All old C code from Unireg changed to C++ and cleaned up. This makes the daemon a little smaller and easier to understand. @item A lot of small bug fixes done. @item New @file{INSTALL} files (not final version) and some information regarding porting. @end itemize @node News-3.19.x, News-3.11, News-3.20.x, News @appendixsec Changes in release 3.19.x Version 3.19 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only. @menu * News-3.19.5:: Changes in release 3.19.5 * News-3.19.4:: Changes in release 3.19.4 * News-3.19.3:: Changes in release 3.19.3 @end menu @node News-3.19.5, News-3.19.4, News-3.19.x, News-3.19.x @appendixsubsec Changes in release 3.19.5 @itemize @bullet @item Some new functions, some more optimization on joins. @item Should now compile clean on Linux (2.0.x). @item Added functions @code{DATABASE()}, @code{USER()}, @code{POW()}, @code{LOG10()} (needed for ODBC). @item In a @code{WHERE} with an @code{ORDER BY} on fields from only one table, the table is now preferred as first table in a multi-join. @item @code{HAVING} and @code{IS NULL} or @code{IS NOT NULL} now works. @item A group on one column and a sort on a group function (@code{SUM()}, @code{AVG()}...) didn't work together. Fixed. @item @code{mysqldump}: Didn't send password to server. @end itemize @node News-3.19.4, News-3.19.3, News-3.19.5, News-3.19.x @appendixsubsec Changes in release 3.19.4 @itemize @bullet @item Fixed horrible locking bug when inserting in one thread and reading in another thread. @item Fixed one-off decimal bug. 1.00 was output as 1.0. @item Added attribute @code{'Locked'} to process list as info if a query is locked by another query. @item Fixed full magic timestamp. Timestamp length may now be 14, 12, 10, 8, 6, 4 or 2 bytes. @item Sort on some numeric functions could sort incorrectly on last number. @item @code{IF(arg,syntax_error,syntax_error)} crashed. @item Added functions @code{CEILING()}, @code{ROUND()}, @code{EXP()}, @code{LOG()} and @code{SQRT()}. @item Enhanced @code{BETWEEN} to handle strings. @end itemize @node News-3.19.3, , News-3.19.4, News-3.19.x @appendixsubsec Changes in release 3.19.3 @itemize @bullet @item Fixed @code{SELECT} with grouping on @code{BLOB} columns not to return incorrect @code{BLOB} info. Grouping, sorting and distinct on @code{BLOB} columns will not yet work as expected (probably it will group/sort by the first 7 characters in the @code{BLOB}). Grouping on formulas with a fixed string size (use @code{MID()} on a @code{BLOB}) should work. @item When doing a full join (no direct keys) on multiple tables with @code{BLOB} fields, the @code{BLOB} was garbage on output. @item Fixed @code{DISTINCT} with calculated columns. @end itemize @node News-3.11, , News-3.19.x, News @appendixsec Changes in release 3.11 MySQL バージョン 3.11 は、MySQL がネット上で公開された初めてのバージョンです @node Porting, Environment variables, News, Top @appendix 他のシステムへの移植について @cindex porting, to other systems This appendix will help you port MySQL to other operationg systems. Do check the list of currently supported operating systems first. @xref{Which OS}. If you have created a new port of MySQL, please let us know so that we can list it here and on our web site (@uref{http://www.mysql.com/}), recommending it to other users. Note: If you create a new port of MySQL, you are free to copy and distribute it under the GPL license, but it does not make you a copyright holder of MySQL. 移植先のシステムには POSIX 仕様のスレッドライブラリが必要となります。 我々は Solaris 2.5 では Sun PThreads (2.4以前でサポートされていたネイティブthreadは良くなかった)を、 Linux では Xavier Leroy, @email{Xavier.Leroy@@inria.fr} による LinuxThreads を使っています。 良いネイティブスレッドを持たない新種の Unix に移植する場合、 多分もっとも大変な作業は MIT-pthreads を導入する部分です。 @file{mit-pthreads/README} と @uref{http://www.humanfactor.com/pthreads/}をご覧下さい。 MySQL の配布ファイルには MIT の Provenzano's Pthreads パッチ済みバージョン (@uref{http://www.mit.edu:8001/people/proven/pthreads.html}をご覧下さい。) が含まれています。 これは POSIX 仕様の Threads を持たない OS に使用可能と思われます。 もう1つのユーザレベル thread パッケージ、FSU Pthreads も使用可能と思われます (@uref{http://www.informatik.hu-berlin.de/~mueller/pthreads.html}をご覧下さい。)。 これはSCOへの移植に使用可能です。 そういった問題に関するテストやサンプルのプログラムを作成する場合には @file{mysys} ディレクトリの @file{thr_lock.c} と @file{thr_alarm.c} 等のプログラムをご覧下さい。 移植にはサーバー、クライアントともに C++ コンパイラを必要とします (ちなみに我々は@code{gcc}を使っています。SPARCWorks(C++)は試しました。)。 Irix @code{cc}も使用できることが確かめられています。 クライアントしか必要無い場合は@code{./configure --without-server}とコンパイルしてください。 サーバのみコンパイルする方法は今のところありません。必要性が生じるまでは今のままです。 @file{Makefile} か コンフィギャスクリプトに何らかの変更をする必要が生じたなら Automake と Autoconf を使わなくてはいけません。 ちなみに、我々は @code{automake-1.2} と @code{autoconf-2.12} を使っています。 変更の手順は全て基本的なファイルからやり直す必要があります。 @example /bin/rm */.deps/*.P /bin/rm -f config.cache aclocal autoheader aclocal automake autoconf ./configure --with-debug=full --prefix='your installation directory' # 上記手順によって生成されるmakefileファイル群はGNU make 3.75以上 # (以下、gmakeと記述します。)を必要とします。 gmake clean all install init-db @end example 新しい移植で問題が発生すればデバッグの必要が生じる場合もあります。 @xref{Debugging server}. @strong{Note}: @code{mysqld}のデバッグを開始する前に@code{mysys/thr_alarm}と@code{mysys/thr_clock}が動くかどうかチェックしてください。これにより貴方のインストールしたthread環境の動作可能性が多少でもあるのかどうかを確かめることができます。 @menu * Debugging server:: Debugging a MySQL server * Debugging client:: Debugging a MySQL client * The DBUG package:: The DBUG Package * Locking methods:: Locking ethods * RTS-threads:: Comments about RTS threads * Thread packages:: Differences between different thread packages @end menu @node Debugging server, Debugging client, Porting, Porting @appendixsec MySQL server のデバッグ @cindex server, debugging @cindex debugging, server @cindex crash もしあなたが MySQL のとても新しいある機能を使っている場合、 @code{--skip-new} (これは全く新しい、潜在的に危険な機能を無効にします) または @code{--safe-mode} (これは問題を生じさせるかもしれない多くの最適化を無効にします) オプションで @code{mysqld} を実行させることができます。 @xref{Crashing}. もし @code{mysqld} が起動しないようなら、 @file{my.cnf} が無いかチェックしてください。 @file{my.cnf} の引数は @code{mysqld --print-defaults} でチェックできます。 また @code{mysqld --no-defaults ...} で起動することにより、 @file{my.cnf} を無視することが可能です。 もし @code{mysqld} が CPU や メモリー を食い始めたり、``ハング'' したりするなら、 @code{mysqladmin processlist status} を使用して誰かが多くの時間のかかる クエリを実行しているか確かめることが出来ます。 パフォーマンスの問題や新しいクライアントが接続できないときの問題と もしあなたが考えるなら、 いくつかのウインドウで @code{mysqladmin -i10 processlist status} を 実行するのはよい考えでしょう。 @code{mysqladmin debug} コマンドは使用中のロック、使用しているメモり、 クエリの使用の情報を、mysql ログファイルにいくつかダンプします これはいくつかの問題解決に役立ちます。 このコマンドは、 MySQL を デバッグ可能でコンパイルしていなくても、いくつかの役立つ情報も提供します。 いくつかのテーブルでだんだん遅くなる問題であるなら、 @code{OPTIMIZE TABLE} か @code{myisamchk} でテーブルを修復し、最適化を試みるべきです。 遅いクエリは、 @code{EXPLAIN} でもチェックできます。 @xref{MySQL Database Administration}. You should also check the slow queries with @code{EXPLAIN}. このマニュアルの OS 固有の問題 の節も読むべきです。 @xref{Operating System Specific Notes}. @menu * Compiling for debugging:: Compiling MYSQL for debugging * Making trace files:: Creating trace files * Using gdb on mysqld:: Debugging mysqld under gdb * Using stack trace:: Using a stack trace * Using log files:: Using log files to find cause of errors in mysqld * Reproduceable test case:: Making a test case when you experience table corruption @end menu @node Compiling for debugging, Making trace files, Debugging server, Debugging server @appendixsubsec Compiling MySQL for Debugging もしあるとても特殊な問題があれば、あなたは、いつも MySQL を デバッグするよう試みることができます。 これを行うには、 MySQL を @code{--with-debug} オプションか @code{--with-debug=full} オプション付きで configure しなくてはなりません。 MySQL がデバッギングを有効にしてコンパイルされているかを 知るには、 @code{mysqld --help} とします。 もし @code{--debug} フラグが リストされていればデバッグが有効です。 @code{mysqladmin ver} も @code{mysqld} のバージョンをリストできます。 この場合は @code{mysql ... --debug} と、バージョン番号に表示されるでしょう。 gcc か egcs の場合、推奨する configure のラインは： @example CC=gcc CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors \ -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \ --with-debug --with-extra-charsets=complex @end example This will avoid problems with the @code{libstdc++} library and with C++ exceptions (many compilers have problems with C++ exceptions in threaded code) and compile a MySQL version with support for all character sets. If you suspect a memory overrun error, you can configure MySQL with @code{--with-debug=full}, which will install a memory allocation (@code{SAFEMALLOC}) checker. Running with @code{SAFEMALLOC} is however quite slow, so if you get performance problems you should start @code{mysqld} with the @code{--skip-safemalloc} option. This will disable the memory overrun checks for each call to @code{malloc} and @code{free}. If @code{mysqld} stops crashing when you compile it with @code{--with-debug}, you have probably found a compiler bug or a timing bug within MySQL. In this case you can try to add @code{-g} to the @code{CFLAGS} and @code{CXXFLAGS} variables above and not use @code{--with-debug}. If @code{mysqld} now dies, you can at least attach to it with @code{gdb} or use @code{gdb} on the core file to find out what happened. MySQL をデバッグで configure すると、自動で多くの安全な検査関数が enable になります。 これは @code{mysqld} の状態をモニターできます。 もしそれら関数がなにか ``予期せぬこと'' を発見したら、それらを @code{stderr} に書き出します。 これは @code{safe_mysqld} が受け取って error ログに 書き出します！ このことはどういうことかというと、 MySQL に予期せぬことが 起きた場合、まず最初にすべきことは、 MySQL をデバッグ有効にして configure することです！ （次に、もちろん、 @email{mysql@@lists.mysql.com} に メールを送り、help を聞くことです。 全てのバグレポート、MySQL のバージョンに 関連する質問は、 @code{mysqlbug} スクリプトを使用してください！） In the Windows MySQL distribution, @code{mysqld.exe} is by default compiled with support for trace files. @node Making trace files, Using gdb on mysqld, Compiling for debugging, Debugging server @appendixsubsec Creating Trace Files If the @code{mysqld} server doesn't start or if you can cause the @code{mysqld} server to crash quickly, you can try to create a trace file to find the problem. To do this you have to have a @code{mysqld} that is compiled for debugging. You can check this by executing @code{mysqld -V}. If the version number ends with @code{-debug}, it's compiled with support for trace files. Start the @code{mysqld} server with a trace log in @file{/tmp/mysqld.trace} (or @file{C:\mysqld.trace} on Windows): @code{mysqld --debug} On Windows you should also use the @code{--standalone} flag to not start @code{mysqld} as a service: In a DOS window do: @example mysqld --debug --standalone @end example After this you can use the @code{mysql.exe} command-line tool in a second DOS window to reproduce the problem. You can take down the above @code{mysqld} server with @code{mysqladmin shutdown}. Note that the trace file will get @strong{very big}! If you want to have a smaller trace file, you can use something like: @code{mysqld --debug=d,info,error,query,general,where:O,/tmp/mysqld.trace} which only prints information with the most interesting tags in @file{/tmp/mysqld.trace}. If you make a bug report about this, please only send the lines from the trace file to the appropriate mailing list where something seems to go wrong! If you can't locate the wrong place, you can ftp the trace file, together with a full bug report, to @uref{ftp://support.mysql.com/pub/mysql/secret/} so that a MySQL developer can take a look a this. The trace file is made with the @strong{DBUG} package by Fred Fish. @xref{The DBUG package}. @node Using gdb on mysqld, Using stack trace, Making trace files, Debugging server @appendixsubsec Debugging mysqld under gdb @cindex gdb, using ほとんどのシステムでは、もし @code{mysqld} がクラッシュするなら、 @code{gdb} から @code{mysqld} を起動させて多くの情報を得ることが可能です。 Linux 上でのいくつかの @code{gdb} バージョンでは、 @code{mysqld} スレッドのデバッグを可能にする場合、 @code{run --one-thread} を使用しなくてはなりません。 この場合、一度にただ一つのactiveなスレッドだけを持つことになります。 We recommend you to upgrade to gdb 5.1 ASAP as thread debugging works much better with this version! When running @code{mysqld} under gdb, you should disable the stack trace with @code{--skip-stack-trace} to be able to catch segfaults within gdb. It's very hard to debug MySQL under @code{gdb} if you do a lot of new connections the whole time as @code{gdb} doesn't free the memory for old threads. You can avoid this problem by starting @code{mysqld} with @code{-O thread_cache_size= 'max_connections +1'}. In most cases just using @code{-O thread_cache_size=5'} will help a lot! If you want to get a core dump on Linux if @code{mysqld} dies with a SIGSEGV signal, you can start @code{mysqld} with the @code{--core-file} option. This core file can be used to make a backtrace that may help you find out why @code{mysqld} died: @example shell> gdb mysqld core gdb> backtrace full gdb> exit @end example @xref{Crashing}. もし Linux 上で gdb 4.17.x を使用しているなら、 @file{.gdb} ファイルを いかにしたがって、カレントのディレクトリーにインストールすべきです： @example set print sevenbit off handle SIGUSR1 nostop noprint handle SIGUSR2 nostop noprint handle SIGWAITING nostop noprint handle SIGLWP nostop noprint handle SIGPIPE nostop handle SIGALRM nostop handle SIGHUP nostop handle SIGTERM nostop noprint @end example If you have problems debugging threads with gdb, you should download gdb 5.x and try this instead. The new gdb version has very improved thread handling! 以下は mysqld のデバッグ例です： @example shell> gdb /usr/local/libexec/mysqld gdb> run ... backtrace full # mysqld がクラッシュした際、これを行います @end example 上記の出力を、 @code{mysqlbug} で作成したメールに含み、 そして @code{mysql@@lists.mysql.com}. に送ってください。 もし @code{mysqld} がハングするなら、 @code{strace} や @code{/usr/proc/bin/pstack} のような システムツールを使用して @code{mysqld} がどこでハングしているか 調べることができます。 @example strace /tmp/log libexec/mysqld @end example @findex DBI->trace @findex trace DBI method @tindex DBI_TRACE environment variable @tindex Environment variable, DBI_TRACE もし Perl @code{DBI} を使用しているなら、 @code{trace} メソッド、あるいは@code{DBI_TRACE} 環境変数で デバッグ情報を有効にできます。 @xref{Perl DBI Class, , Perl @code{DBI} Class}. @node Using stack trace, Using log files, Using gdb on mysqld, Debugging server @appendixsubsec Using a Stack Trace On some operating systems, the error log will contain a stack trace if @code{mysqld} dies unexpectedly. You can use this to find out where (and maybe why) @code{mysqld} died. @xref{Error log}. To get a stack trace, you must not compile @code{mysqld} with the @code{-fomit-frame-pointer} option to gcc. @xref{Compiling for debugging}. If the error file contains something like the following: @example mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong stack range sanity check, ok, backtrace follows 0x40077552 0x81281a0 0x8128f47 0x8127be0 0x8127995 0x8104947 0x80ff28f 0x810131b 0x80ee4bc 0x80c3c91 0x80c6b43 0x80c1fd9 0x80c1686 @end example you can find where @code{mysqld} died by doing the following: @enumerate @item Copy the above numbers to a file, for example @file{mysqld.stack}. @item Make a symbol file for the @code{mysqld} server: @example nm -n libexec/mysqld > /tmp/mysqld.sym @end example Note that many MySQL binary distributions comes with the above file, named @code{mysqld.sym.gz}. In this case you must unpack this by doing: @example gunzip < bin/mysqld.sym.gz > /tmp/mysqld.sym @end example @item Execute @code{resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack}. This will print out where @code{mysqld} died. If this doesn't help you find out why @code{mysqld} died, you should make a bug report and include the output from the above commend with the bug report. Note however that in most cases it will not help us to just have a stack trace to find the reason for the problem. To be able to locate the bug or provide a workaround, we would in most cases need to know the query that killed @code{mysqld} and preferable a test case so that we can repeat the problem! @xref{Bug reports}. @end enumerate @node Using log files, Reproduceable test case, Using stack trace, Debugging server @appendixsubsec Using Log Files to Find Cause of Errors in mysqld @code{--log}を使用して@code{mysqld}を起動する際は、事前に@code{myisamchk} を使用して全てのテーブルをチェックするようにしてください。 @xref{MySQL Database Administration}. もし @code{mysqld} が死んだりハングしたりするなら、 @code{mysqld} を @code{--log} で起動すべきです。 再び @code{mysqld} が死んだら、 あなたはログファイル中の、 @code{mysqld} を kill するクエリをチェックします。 If you are using @code{--log} without a file name, the log is stored in the database directory as 'hostname'.log In most cases it's the last query in the log file that killed @code{mysqld}, but if possible you should verify this by restarting @code{mysqld} and executing the found query from the @code{mysql} command-line tools. If this works, you should also test all complicated queries that didn't complete. @code{mysqld} が適切にインデックスを使用するのに時間がとてもかかる全ての @code{SELECT} 文を @code{EXPLAIN} で実行することを試みます。 @xref{EXPLAIN, , @code{EXPLAIN}}. You can find the queries that take a long time to execute by starting @code{mysqld} with @code{--log-slow-queries}. @xref{Slow query log}. もしエラーログファイル(通常 @file{hostname.err} という名前)中に @code{mysqld restarted} という文があるなら、 @code{mysqld} を失敗させるクエリを見つけます。 もしこれが起きるなら、@code{myisamchk} (@pxref{MySQL Database Administration}) で 全てのテーブルをチェックし、MySQL ログファイルにあるそのクエリをテストすべきです。 もしそのようなクエリをみつけたなら、まず最初に最新の MySQL にアップグレード してみてください。 もしそれでもだめで、かつ @code{mysql} メーリングリストの アーカイブにもなにも見つけることが出来なかったなら、 @email{mysql@@lists.mysql.com} に バグレポートを出すべきです。 メーリングリストのアーカイブへのリンクは @uref{http://www.mysql.com/}. If you have started @code{mysqld} with @code{myisam-recover}, MySQL will automatically check and try to repair @code{MyISAM} tables if they are marked as 'not closed properly' or 'crashed'. If this happens, MySQL will write an entry in the @code{hostname.err} file @code{'Warning: Checking table ...'} which is followed by @code{Warning: Repairing table} if the table needs to be repaired. If you get a lot of these errors, without @code{mysqld} having died unexpectedly just before, then something is wrong and needs to be investigated further. @xref{Command-line options}. It's of course not a good sign if @code{mysqld} did died unexpectedly, but in this case one shouldn't investigate the @code{Checking table...} messages but instead try to find out why @code{mysqld} died. @node Reproduceable test case, , Using log files, Debugging server @appendixsubsec Making a Test Case When You Experience Table Corruption もし不正なテーブルをえたり、 @code{mysqld} が常にいくつかの update コマンドで 失敗するなら、以下のようにしてこのバグの再現をテストします： @itemize @bullet @item Take down the MySQL daemon (with @code{mysqladmin shutdown}). @item Make a backup of the tables (to guard against the very unlikely case that the repair will do something bad). @item @code{myisamchk -s database/*.MYI} で全テーブルをチェック. @code{myisamchk -r database/table.MYI} で悪いテーブルを修正。 @item Make a second backup of the tables. @item Remove (or move away) any old log files from the MySQL data directory if you need more space. @item Start @code{mysqld} with @code{--log-bin}. @xref{Binary log}. If you want to find a query that crashes @code{mysqld}, you should use @code{--log --log-bin}. @item 壊れたテーブルを得た時、@code{mysqld server} を停止。 @item バックアップをリストア @item @code{mysqld} server を @code{--log-bin} @strong{なしで} 起動。 @item Re-execute the commands with @code{mysqlbinlog update-log-file | mysql}. The update log is saved in the MySQL database directory with the name @code{hostname-bin.#}. @item If the tables are corrupted again or you can get @code{mysqld} to die with the above command, you have found reproducible bug that should be easy to fix! FTP the tables and the binary log to @uref{ftp://support.mysql.com/pub/mysql/secret/} and send a mail to @email{bugs@@lists.mysql.com} or (if you are a support customer) to @email{support@@mysql.com} about the problem and the MySQL team will fix it as soon as possible. @end itemize You can also use the script @code{mysql_find_rows} to just execute some of the update statements if you want to narrow down the problem. @node Debugging client, The DBUG package, Debugging server, Porting @appendixsec Debugging a MySQL client @cindex debugging, client @cindex clients, debugging To be able to debug a MySQL client with the integrated debug package, you should configure MySQL with @code{--with-debug} or @code{--with-debug=full}. @xref{configure options}. @tindex MYSQL_DEBUG environment variable @tindex Environment variable, MYSQL_DEBUG Before running a client, you should set the @code{MYSQL_DEBUG} environment variable: @example shell> MYSQL_DEBUG=d:t:O,/tmp/client.trace shell> export MYSQL_DEBUG @end example This causes clients to generate a trace file in @file{/tmp/client.trace}. If you have problems with your own client code, you should attempt to connect to the server and run your query using a client that is known to work. Do this by running @code{mysql} in debugging mode (assuming you have compiled MySQL with debugging on): @example shell> mysql --debug=d:t:O,/tmp/client.trace @end example This will provide useful information in case you mail a bug report. @xref{Bug reports}. If your client crashes at some 'legal' looking code, you should check that your @file{mysql.h} include file matches your mysql library file. A very common mistake is to use an old @file{mysql.h} file from an old MySQL installation with new MySQL library. @node The DBUG package, Locking methods, Debugging client, Porting @appendixsec The DBUG Package @cindex DBUG package The MySQL server and most MySQL clients are compiled with the DBUG package originally made by Fred Fish. When one has configured MySQL for debugging, this package makes it possible to get a trace file of what the program is debugging. @xref{Making trace files}. One uses the debug package by invoking the program with the @code{--debug="..."} or the @code{-#...} option. Most MySQL programs has a default debug string that will be used if you don't specify an option to @code{--debug}. The default trace file is usually @code{/tmp/programname.trace} on Unix and @code{\programname.trace} on Windows. The debug control string is a sequence of colon separated fields as follows: @example ::...: @end example Each field consists of a mandatory flag character followed by an optional "," and comma-separated list of modifiers: @example flag[,modifier,modifier,...,modifier] @end example The currently recognised flag characters are: @multitable @columnfractions .05 .95 @item @strong{Flag} @tab @strong{Description} @item d @tab Enable output from DBUG_ macros for the current state. May be followed by a list of keywords which selects output only for the DBUG macros with that keyword. An empty list of keywords implies output for all macros. @item D @tab Delay after each debugger output line. The argument is the number of tenths of seconds to delay, subject to machine capabilities. That is, @code{-#D,20} is delay two seconds. @item f @tab Limit debugging and/or tracing, and profiling to the list of named functions. Note that a null list will disable all functions. The appropriate "d" or "t" flags must still be given, this flag only limits their actions if they are enabled. @item F @tab Identify the source file name for each line of debug or trace output. @item i @tab Identify the process with the pid or thread id for each line of debug or trace output. @item g @tab Enable profiling. Create a file called 'dbugmon.out' containing information that can be used to profile the program. May be followed by a list of keywords that select profiling only for the functions in that list. A null list implies that all functions are considered. @item L @tab Identify the source file line number for each line of debug or trace output. @item n @tab Print the current function nesting depth for each line of debug or trace output. @item N @tab Number each line of dbug output. @item o @tab Redirect the debugger output stream to the specified file. The default output is stderr. @item O @tab As @code{O} but the file is really flushed between each write. When needed the file is closed and reopened between each write. @item p @tab Limit debugger actions to specified processes. A process must be identified with the DBUG_PROCESS macro and match one in the list for debugger actions to occur. @item P @tab Print the current process name for each line of debug or trace output. @item r @tab When pushing a new state, do not inherit the previous state's function nesting level. Useful when the output is to start at the left margin. @item S @tab Do function _sanity(_file_,_line_) at each debugged function until _sanity() returns something that differs from 0. (Mostly used with safemalloc to find memory leaks) @item t @tab Enable function call/exit trace lines. May be followed by a list (containing only one modifier) giving a numeric maximum trace level, beyond which no output will occur for either debugging or tracing macros. The default is a compile time option. @end multitable Some examples of debug control strings which might appear on a shell command-line (the "-#" is typically used to introduce a control string to an application program) are: @example -#d:t -#d:f,main,subr1:F:L:t,20 -#d,input,output,files:n -#d:t:i:O,\\mysqld.trace @end example In MySQL, common tags to print (with the @code{d} option) are: @code{enter},@code{exit},@code{error},@code{warning},@code{info} and @code{loop}. @node Locking methods, RTS-threads, The DBUG package, Porting @appendixsec Locking methods @cindex locking methods @cindex methods, locking Currently MySQL only supports table locking for @code{ISAM}/@code{MyISAM} and @code{HEAP} tables, page-level locking for @code{BDB} tables and row-level locking for @code{InnoDB} tables. @xref{Internal locking}. With @code{MyISAM} tables one can freely mix @code{INSERT} and @code{SELECT} without locks, if the @code{INSERT}s are non-conflicting (i.e. whenever they append to the end of the table file rather than filling freespace from deleted rows/data). Starting in version 3.23.33, you can analyse the table lock contention on your system by checking @code{Table_locks_waited} and @code{Table_locks_immediate} environment variables. To decide if you want to use a table type with row-level locking, you will want to look at what the application does and what the select/update pattern of the data is. Pros for row locking: @itemize @bullet @item Fewer lock conflicts when accessing different rows in many threads. @item Fewer changes for rollbacks. @item Makes it possible to lock a single row a long time. @end itemize Cons: @itemize @bullet @item Takes more memory than page level or table locks. @item Is slower than page level or table locks when used on a big part of the table, because one has to do many more locks. @item Is definitely much worse than other locks if you do often do @code{GROUP BY} on a large part of the data or if one has to often scan the whole table. @item With higher level locks one can also more easily support locks of different types to tune the application as the lock overhead is less notable as for row level locks. @end itemize Table locks are superior to page level / row level locks in the following cases: @itemize @bullet @item Mostly reads @item Read and updates on strict keys; this is where one updates or deletes a row that can be fetched with one key read: @example UPDATE table_name SET column=value WHERE unique_key# DELETE FROM table_name WHERE unique_key=# @end example @item @code{SELECT} combined with @code{INSERT} (and very few @code{UPDATE}s and @code{DELETE}s). @item Many scans / @code{GROUP BY} on the whole table without any writers. @end itemize Other options than row / page level locking: Versioning (like we use in MySQL for concurrent inserts) where you can have one writer at the same time as many readers. This means that the database/table supports different views for the data depending on when one started to access it. Other names for this are time travel, copy on write or copy on demand. Copy on demand is in many case much better than page or row level locking; the worst case does, however, use much more memory than when using normal locks. Instead of using row level locks one can use application level locks (like get_lock/release_lock in MySQL). This works of course only in well-behaved applications. In many cases one can do an educated guess which locking type is best for the application, but generally it's very hard to say that a given lock type is better than another; everything depends on the application and different part of the application may require different lock types. Here are some tips about locking in MySQL: Most web applications do lots of selects, very few deletes, updates mainly on keys, and inserts in some specific tables. The base MySQL setup is very well tuned for this. Concurrent users are not a problem if one doesn't mix updates with selects that need to examine many rows in the same table. If one mixes inserts and deletes on the same table then @code{INSERT DELAYED} may be of great help. One can also use @code{LOCK TABLES} to speed up things (many updates within a single lock is much faster than updates without locks). Splitting thing to different tables will also help. If you get speed problems with the table locks in MySQL, you may be able to solve these by converting some of your tables to @code{InnoDB} or @code{BDB} tables. @xref{InnoDB}. @xref{BDB}. The optimisation section in the manual covers a lot of different aspects of how to tune applications. @xref{Tips}. @node RTS-threads, Thread packages, Locking methods, Porting @appendixsec Comments about RTS threads @cindex RTS-threads @cindex threads, RTS I have tried to use the RTS thread packages with MySQL but stumbled on the following problems: They use an old version of a lot of POSIX calls and it is very tedious to make wrappers for all functions. I am inclined to think that it would be easier to change the thread libraries to the newest POSIX specification. Some wrappers are already written. See @file{mysys/my_pthread.c} for more info. At least the following should be changed: @code{pthread_get_specific} should use one argument. @code{sigwait} should take two arguments. A lot of functions (at least @code{pthread_cond_wait}, @code{pthread_cond_timedwait}) should return the error code on error. Now they return -1 and set @code{errno}. Another problem is that user-level threads use the @code{ALRM} signal and this aborts a lot of functions (@code{read}, @code{write}, @code{open}...). MySQL should do a retry on interrupt on all of these but it is not that easy to verify it. The biggest unsolved problem is the following: To get thread-level alarms I changed @file{mysys/thr_alarm.c} to wait between alarms with @code{pthread_cond_timedwait()}, but this aborts with error @code{EINTR}. I tried to debug the thread library as to why this happens, but couldn't find any easy solution. If someone wants to try MySQL with RTS threads I suggest the following: @itemize @bullet @item Change functions MySQL uses from the thread library to POSIX. This shouldn't take that long. @item Compile all libraries with the @code{-DHAVE_rts_threads}. @item Compile @code{thr_alarm}. @item If there are some small differences in the implementation, they may be fixed by changing @file{my_pthread.h} and @file{my_pthread.c}. @item Run @code{thr_alarm}. If it runs without any ``warning'', ``error'' or aborted messages, you are on the right track. Here is a successful run on Solaris: @example Main thread: 1 Thread 0 (5) started Thread: 5 Waiting process_alarm Thread 1 (6) started Thread: 6 Waiting process_alarm process_alarm thread_alarm Thread: 6 Slept for 1 (1) sec Thread: 6 Waiting process_alarm process_alarm thread_alarm Thread: 6 Slept for 2 (2) sec Thread: 6 Simulation of no alarm needed Thread: 6 Slept for 0 (3) sec Thread: 6 Waiting process_alarm process_alarm thread_alarm Thread: 6 Slept for 4 (4) sec Thread: 6 Waiting process_alarm thread_alarm Thread: 5 Slept for 10 (10) sec Thread: 5 Waiting process_alarm process_alarm thread_alarm Thread: 6 Slept for 5 (5) sec Thread: 6 Waiting process_alarm process_alarm ... thread_alarm Thread: 5 Slept for 0 (1) sec end @end example @end itemize @node Thread packages, , RTS-threads, Porting @appendixsec スレッドパッケージ間の違いは何？ @cindex thread packages, differences between MySQL は使用されるスレッドパッケージに非常に依存しています。 そのため、MySQL に良いプラットフォームを選択する時には、 スレッドパッケージが非常に重要です。 少なくとも3つのタイプのスレッドパッケージがあります： @itemize @bullet @item シングルプロセス内のユーザスレッド。 スレッド切替えはアラームで管理され、 スレッドライブラリはロックを伴う非スレッド安全関数のすべてを管理します。 動作中スレッドがデータを待つ必要がある場合、read, write そして select は、 通常、他のスレッドに切替えるスレッド固有の select で管理されます。 もしユーザ・スレッドパッケージが標準ライブラリ (FreeBSD と BSDI スレッド) に 統合されているなら、スレッドパッケージのオーバーヘッドは、全ての非安全コールを マップしなければならないスレッドパッケージ(MIT-スレッド, FSU-スレッド, RTS スレ ッド) よりも少なくなります。 他の環境(例えば SCO)では、全てのシステムコールはスレッド安全なので、 マッピングはとても簡単に行なわれます(SCO 上の FSU-スレッド)。 Downside: 全てのマップされるコールは少し時間がかかり、全ての状況を 処理可能にすることは、とても困難です。 通常、スレッドパッケージによって処理できないシステムコールがいくつかあります (MIT-スレッドとソケットのように)。 スレッドスケジューリングは常に最 適というわけではあ りません。 @item 別プロセスのユーザスレッド。 スレッド切替えはカーネルによって行なわれ、全てのデータはスレッド間で共有されます。 スレッドパッケージは、スレッ ド間のデータ共有を許可するために標準スレッドコール を管理します。 LinuxThreads はこの方法を使用しています。 Downside: 多くのプロセス。スレッド生成は遅いです。 もし一つのスレッドが死ぬと、残りは通常ハングして残り、再起動前に それら全て を kill する必要があります。スレッド切替えはいくらか高価(expensive)です。 @item カーネルスレッド。 スレッド切替えはスレッドライブラリかカーネルによって処理され、 とても速いです。 全ては一つのプロセス内で行なわれますが、 いくつかのシステムでは、@code{ps} が異なったスレッドを示します。 もし一つのスレッドがアボートした場合、プロセス全体がアボートします。 多くのシステムコールはスレッド安全で、オーバーヘッドはとても少ないです。 Solaris, HP-UX, AIX そして OSF1 がカーネルスレッドを持っています。 @end itemize いくつかのシステムでは、カーネルスレッドは、システムライブラリ内で、 ユーザレベルスレッドの統合によって管理されます。 この場合、スレッド切替えはスレッドライブラリによってだけ行なわれ、 カーネルは実際には 'thread aware' ではありません。 @node Environment variables, Regexp, Porting, Top @appendix Environment Variables @cindex environment variables, list of MySQLで直接又は間接的に使用されている全ての環境変数リストを示します。これらのほとんどはこのマニュアルのどこかで使用されています。 コマンドラインオプションで指定される環境変数はコンフィギュレーションファイルで指定されるものよりも優先されます。また、コンフィギュレーションファイルで指定される環境変数はシェルで設定された環境変数よりも優先されます。 MySQLの振る舞いを指定する場合、環境変数はシェルで設定するよりもにコンフィギュレーションファイルで設定される方が望ましいことが多いです。@xref{Option files}. @tindex CCX environment variable @tindex Environment variable, CCX @tindex CC environment variable @tindex Environment variable, CC @tindex CFLAGS environment variable @tindex Environment variable, CFLAGS @tindex CXXFLAGS environment variable @tindex Environment variable, CXXFLAGS @tindex DBI_USER environment variable @tindex Environment variable, DBI_USER @tindex DBI_TRACE environment variable @tindex Environment variable, DBI_TRACE @tindex HOME environment variable @tindex Environment variable, HOME @tindex LD_RUN_PATH environment variable @tindex Environment variable, LD_RUN_PATH @tindex MYSQL_DEBUG environment variable @tindex Environment variable, MYSQL_DEBUG @tindex MYSQL_HISTFILE environment variable @tindex Environment variable, MYSQL_HISTFILE @tindex MYSQL_HOST environment variable @tindex Environment variable, MYSQL_HOST @tindex MYSQL_PS1 environment variable @tindex Environment variable, MYSQL_PS1 @tindex MYSQL_PWD environment variable @tindex Environment variable, MYSQL_PWD @tindex MYSQL_TCP_PORT environment variable @tindex Environment variable, MYSQL_TCP_PORT @tindex MYSQL_UNIX_PORT environment variable @tindex Environment variable, MYSQL_UNIX_PORT @tindex PATH environment variable @tindex Environment variable, PATH @tindex TMPDIR environment variable @tindex Environment variable, TMPDIR @tindex TZ environment variable @tindex Environment variable, TZ @tindex UMASK_DIR environment variable @tindex Environment variable, UMASK_DIR @tindex UMASK environment variable @tindex Environment variable, UMASK @tindex USER environment variable @tindex Environment variable, USER @multitable @columnfractions .25 .70 @item @strong{Variable} @tab @strong{Description} @item @code{CCX} @tab Set this to your C++ compiler when running configure. @item @code{CC} @tab Set this to your C compiler when running configure. @item @code{CFLAGS} @tab Flags for your C compiler when running configure. @item @code{CXXFLAGS} @tab Flags for your C++ compiler when running configure. @item @code{DBI_USER} @tab The default user name for Perl DBI. @item @code{DBI_TRACE} @tab Used when tracing Perl DBI. @item @code{HOME} @tab The default path for the @code{mysql} history file is @file{$HOME/.mysql_history}. @item @code{LD_RUN_PATH} @tab Used to specify where your @file{libmysqlclient.so} is. @item @code{MYSQL_DEBUG} @tab Debug-trace options when debugging. @item @code{MYSQL_HISTFILE} @tab The path to the @code{mysql} history file. @item @code{MYSQL_HOST} @tab Default host name used by the @code{mysql} command-line client. @item @code{MYSQL_PS1} @tab Command prompt to use in the @code{mysql} command-line client. @xref{mysql}. @item @code{MYSQL_PWD} @tab The default password when connecting to @code{mysqld}. Note that use of this is insecure! @item @code{MYSQL_TCP_PORT} @tab The default TCP/IP port. @item @code{MYSQL_UNIX_PORT} @tab The default socket; used for connections to @code{localhost}. @item @code{PATH} @tab Used by the shell to finds the MySQL programs. @item @code{TMPDIR} @tab The directory where temporary tables/files are created. @item @code{TZ} @tab This should be set to your local time zone. @xref{Timezone problems}. @item @code{UMASK_DIR} @tab The user-directory creation mask when creating directories. Note that this is ANDed with @code{UMASK}! @item @code{UMASK} @tab The user-file creation mask when creating files. @item @code{USER} @tab The default user on Windows to use when connecting to @code{mysqld}. @end multitable @node Regexp, GPL license, Environment variables, Top @appendix MySQL の正規表現 @cindex regex @cindex regular expression syntax, described @cindex syntax, regular expression A regular expression (regex) is a powerful way of specifying a complex search. @strong{MySQL} は正規表現の regular Henry Spencers 実装を使用します。 そしてこれは POSIX 1003.2 に一致することが 目的です。@strong{MySQL} は拡張 バージョンを使用します。 これは詳細を省いた簡単なリファレンスです。 さらに正確な情報は Henry Spencers @code{regex(7)} マニュアルを見てください。 これはソース配布に含まれています。 @xref{Credits}. 正規表現は文字列の組み合わせて記述されます。 もっとも簡単な場合は、非特殊文字の一文字です。例えば、 regexp @code{hello} は @code{hello} と適合し、 他には適合しません。 簡単でない正規表現は、1つの文字列以上に適合できるような、いくつかの 特殊な構成を使用します。例えば、regexp @code{hello|word} は 文字列 @code{hello} と文字列 @code{word} に適合します。 そしてさらに複雑な例 regexp @code{B[an]*s} は、 文字列 @code{Bananas}, @code{Baaaaas}, @code{Bs} のどれか、 そして @code{B} で始まり @code{a} や @code{n} が 任意の数続き、@code{s} で終わるような他の文字列に適合します。 正規表現では、次の特殊文字/構成が使用できます： @table @code @item ^ 文字列全体の始まり。 @example mysql> SELECT "fo\nfo" REGEXP "^fo$"; -> 0 mysql> SELECT "fofo" REGEXP "^fo"; -> 1 @end example @item $ 文字列全体の終り。 @example mysql> SELECT "fo\no" REGEXP "^fo\no$"; -> 1 mysql> SELECT "fo\no" REGEXP "^fo$"; -> 0 @end example @item . 任意の文字 (改行含む)。 @example mysql> SELECT "fofo" REGEXP "^f.*"; -> 1 mysql> SELECT "fo\nfo" REGEXP "^f.*"; -> 1 @end example @item a* 0個以上の文字 @code{a} の並び。 @example mysql> SELECT "Ban" REGEXP "^Ba*n"; -> 1 mysql> SELECT "Baaan" REGEXP "^Ba*n"; -> 1 mysql> SELECT "Bn" REGEXP "^Ba*n"; -> 1 @end example @item a+ 文字 @code{a} が 1個以上並ぶ。 @example mysql> SELECT "Ban" REGEXP "^Ba+n"; -> 1 mysql> SELECT "Bn" REGEXP "^Ba+n"; -> 0 @end example @item a? 0 または 1個の文字 @code{a}。 @example mysql> SELECT "Bn" REGEXP "^Ba?n"; -> 1 mysql> SELECT "Ban" REGEXP "^Ba?n"; -> 1 mysql> SELECT "Baan" REGEXP "^Ba?n"; -> 0 @end example @item de|abc @code{de} か @code{abc} にマッチ。 @example mysql> SELECT "pi" REGEXP "pi|apa"; -> 1 mysql> SELECT "axe" REGEXP "pi|apa"; -> 0 mysql> SELECT "apa" REGEXP "pi|apa"; -> 1 mysql> SELECT "apa" REGEXP "^(pi|apa)$"; -> 1 mysql> SELECT "pi" REGEXP "^(pi|apa)$"; -> 1 mysql> SELECT "pix" REGEXP "^(pi|apa)$"; -> 0 @end example @item (abc)* 文字列 @code{abc} の 0 回以上の並びにマッチ。 @example mysql> SELECT "pi" REGEXP "^(pi)*$"; -> 1 mysql> SELECT "pip" REGEXP "^(pi)*$"; -> 0 mysql> SELECT "pipi" REGEXP "^(pi)*$"; -> 1 @end example @item @{1@} @itemx @{2,3@} 多くの発生に適合する regexp の記述する一般的な方法。 The is a more general way of writing regexps that match many occurrences of the previous atom. @table @code @item a* Can be written as @code{a@{0,@}}. @item a+ Can be written as @code{a@{1,@}}. @item a? Can be written as @code{a@{0,1@}}. @end table さらに正確には、1つの整数 i とコンマ無しを含む修飾が続くアトムは、 厳密にアトムに適合する @code{i} 回の並びに適合します。 整数 @code{i} とコンマを含む修飾が続くアトムは、 アトムに適合する @code{i} 回以上の並びに適合します。 整数 @code{i} と @code{j} を含む装飾が続くアトムは、 アトムに適 合する @code{i} 回から @code{j} 回までの並びに適合します。 両方の引数は @code{0} から @code{RE_DUP_MAX} (default 255) の間でなければなりません。 そして引数が2つある場合、2番目は1番目よりも大きいか同じでなければなりません。 @item [a-dX] @itemx [^a-dX] @code{a}, @code{b}, @code{c}, @code{d}, @code{X} のどれかの文字 (@code{^} を使用するとどれでもない文字) にマッチ。 @code{]} 文字を含めるには、 @code{[} のあとに続いてすぐに書く必要があります。 @code{-} 文字を含めるには最初か最後に書く必要があります。 @code{[0-9]} は任意 の10進数値に適合します。 @code{[]} ペア内部の定義された 意味を持たない全ての文字は、特殊な意味を持たず、それ自身にだけ適合します。 @example mysql> SELECT "aXbc" REGEXP "[a-dXYZ]"; -> 1 mysql> SELECT "aXbc" REGEXP "^[a-dXYZ]$"; -> 0 mysql> SELECT "aXbc" REGEXP "^[a-dXYZ]+$"; -> 1 mysql> SELECT "aXbc" REGEXP "^[^a-dXYZ]+$"; -> 0 mysql> SELECT "gheis" REGEXP "^[^a-dXYZ]+$"; -> 1 mysql> SELECT "gheisa" REGEXP "^[^a-dXYZ]+$"; -> 0 @end example @item [[.characters.]] 照合要素(collating element)の文字の並び。 並びは括弧表現リストの一つの要素です。 複数文字の照合要素を含む括弧表現は一つ以上の文字に適合します。 例えば、照合並びが @code{ch} 照合要素を含む場合、 正規表現 @code{[[.ch.]]*c} は @code{chchcc} の最初の5文字に適合します。 @item [=character_class=] 同等のクラス。その一つと等しい全ての照合要素の文字の並びを表します。それ自身も含みます。 例えば、@code{o} と @code{(+)} が同等クラスのメンバである場合、 @code{[[=o=]]}, @code{[[=(+)=]]}, @code{[[=(+)=]]} は全て同義語です。 同等クラスは範囲の終了位置にはなりません。 @item [:character_class:] 括弧表現の内部で、@code{[:} と @code{:]} で括られた文字クラスの名前は、 そのクラスに属する全ての文字のリストを表します。標準文字クラス名は: @multitable @columnfractions .10 .10 .10 @item @strong{Name} @tab @strong{Name} @tab @strong{Name} @item alnum @tab digit @tab punct @item alpha @tab graph @tab space @item blank @tab lower @tab upper @item cntrl @tab print @tab xdigit @end multitable これらは @code{ctype(3)} マニュアルページに記載されている文字クラスを表します。 ロケールが他のを提供することもあります。文字クラスは範囲の終了位置としては使えません。 @example mysql> SELECT "justalnums" REGEXP "[[:alnum:]]+"; -> 1 mysql> SELECT "!!" REGEXP "[[:alnum:]]+"; -> 0 @end example @item [[:<:]] @itemx [[:>:]] それぞれ、単語の始めと終りの空文字列に適合します。単語は、単語文字が前後 にない単語文字の並びとして定義されます。単語文字は alnum 文字 (@code{ctype(3)} で定義されます) と下線(underscore ； @code{_})です。 @example mysql> SELECT "a word a" REGEXP "[[:<:]]word[[:>:]]"; -> 1 mysql> SELECT "a xword a" REGEXP "[[:<:]]word[[:>:]]"; -> 0 @end example @end table @example mysql> SELECT "weeknights" REGEXP "^(wee|week)(knights|nights)$"; -> 1 @end example @node GPL license, LGPL license, Regexp, Top @appendix GNU General Public License @cindex GPL, General Public License @cindex GPL, GNU General Public License @center Version 2, June 1991 @display Copyright @copyright{} 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @end display @appendixsec Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software---to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. @iftex @appendixsec TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end iftex @ifinfo @center GNU GENERAL PUBLIC LICENSE @center TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end ifinfo @enumerate 0 @item This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The ``Program'', below, refers to any such program or work, and a ``work based on the Program'' means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term ``modification''.) Each licensee is addressed as ``you''. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. @item You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. @item You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: @enumerate a @item You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. @item You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. @item If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) @end enumerate These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. @item You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: @enumerate a @item Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, @item Accompany it with a written offer, valid for at least three years, to give any third-party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, @item Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) @end enumerate The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. @item You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. @item You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. @item Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. @item If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. @item If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. @item The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and ``any later version'', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. @item If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. @iftex @heading NO WARRANTY @end iftex @ifinfo @center NO WARRANTY @end ifinfo @item BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. @item IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @end enumerate @iftex @heading END OF TERMS AND CONDITIONS @end iftex @ifinfo @center END OF TERMS AND CONDITIONS @end ifinfo @page @appendixsec How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the ``copyright'' line and a pointer to where the full notice is found. @smallexample @var{one line to give the program's name and a brief idea of what it does.} Copyright (C) @var{yyyy} @var{name of author} This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. @end smallexample Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: @smallexample Gnomovision version 69, Copyright (C) 19@var{yy} @var{name of author} Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. @end smallexample The hypothetical commands @samp{show w} and @samp{show c} should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than @samp{show w} and @samp{show c}; they could even be mouse-clicks or menu items---whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a ``copyright disclaimer'' for the program, if necessary. Here is a sample; alter the names: @example Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. @var{signature of Ty Coon}, 1 April 1989 Ty Coon, President of Vice @end example This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. @page @node LGPL license, Function Index, GPL license, Top @appendix GNU Lesser General Public License @cindex LGPL, Library General Public License @cindex LGPL, GNU Library General Public License @cindex LGPL, Lesser General Public License @cindex LGPL, GNU Lesser General Public License @center Version 2.1, February 1999 @display Copyright @copyright{} 1991, 1999 Free Software Foundation, Inc. 59 Temple Place -- Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] @end display @appendixsec Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software---to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software---typically libraries---of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the @dfn{Lesser} General Public License because it does @emph{Less} to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a ``work based on the library'' and a ``work that uses the library''. The former contains code derived from the library, whereas the latter must be combined with the library in order to run. @iftex @appendixsec TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end iftex @ifinfo @center GNU LESSER GENERAL PUBLIC LICENSE @center TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end ifinfo @enumerate 0 @item This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called ``this License''). Each licensee is addressed as ``you''. A ``library'' means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The ``Library'', below, refers to any such software library or work which has been distributed under these terms. A ``work based on the Library'' means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term ``modification''.) ``Source code'' for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. @item You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. @item You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: @enumerate a @item The modified work must itself be a software library. @item You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. @item You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. @item If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) @end enumerate These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. @item You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library. @item You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. @item A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a ``work that uses the Library''. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a ``work that uses the Library'' with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a ``work that uses the library''. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a ``work that uses the Library'' uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether they are linked directly with the Library itself. @item As an exception to the Sections above, you may also combine or link a ``work that uses the Library'' with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: @enumerate a @item Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable ``work that uses the Library'', as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) @item Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at runtime a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. @item Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. @item If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. @item Verify that the user has already received a copy of these materials or that you have already sent this user a copy. @end enumerate For an executable, the required form of the ``work that uses the Library'' must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. @item You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: @enumerate a @item Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. @item Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. @end enumerate @item You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. @item You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. @item Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. @item If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. @item If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. @item The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and ``any later version'', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. @item If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. @iftex @heading NO WARRANTY @end iftex @ifinfo @center NO WARRANTY @end ifinfo @item BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. @item IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @end enumerate @iftex @heading END OF TERMS AND CONDITIONS @end iftex @ifinfo @center END OF TERMS AND CONDITIONS @end ifinfo @page @appendixsec How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the ``copyright'' line and a pointer to where the full notice is found. @smallexample @var{one line to give the library's name and an idea of what it does.} Copyright (C) @var{year} @var{name of author} This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. @end smallexample Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a ``copyright disclaimer'' for the library, if necessary. Here is a sample; alter the names: @smallexample Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. @var{signature of Ty Coon}, 1 April 1990 Ty Coon, President of Vice @end smallexample That's all there is to it! @node Function Index, Concept Index, LGPL license, Top @unnumbered SQL command, type and function index @printindex fn @page @node Concept Index, , Function Index, Top @unnumbered Concept Index @printindex cp @bye mysql-4.00.12/manual.ja_MySQL_Optimization.html0100664000175100001560000043373207724406770020223 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 5 MySQL Optimization Go to the first, previous, next, last section, table of contents.

    5 MySQL Optimization

    Optimization is a complicated task because it ultimately requires understanding of the whole system. While it may be possible to do some local optimizations with small knowledge of your system or application, the more optimal you want your system to become the more you will have to know about it.

    This chapter will try to explain and give some examples of different ways to optimise MySQL. Remember, however, that there are always some (increasingly harder) additional ways to make the system even faster.

    5.1 最適化 概要

    システムを速くするための最も重要な部分は、もちろん基礎的な設計です。 You also need to know what kinds of things your system will be doing, and what your bottlenecks are.

    主なボトルネックは：

    • Disk シーク ： 一片のデータを見つけるためには、ディスクに時間がかかります。 1999年の最新型のディスクでは、このための平均時間は、10msよりも通常より小さいです。 したがって、我々は、理論上は 1秒で約1000 シークすることができます。 この時間は、一つのテーブルであるならば、データの増加と共にディスクアクセスの時間 が少しずつ増加することになり、とても最適化するのは難しくなっていきます。 これを最適化する方法は、データを 1個以上のディスクに分散する事です。
    • Disk reading/writing. When the disk is at the correct position we need to read the data. With modern disks in 1999, one disk delivers something like 10-20Mb/s. This is easier to optimize than seeks because you can read in parallel from multiple disks.
    • CPU cycles. データをメイン・メモリーの中に入れた(または既にメモリに存在している)場合に、 結果を得るためには、それを処理する必要があります。 メモリー容量よりも小さなテーブルを持っている場合、これは、制限の要因となります。 小さいテーブルでは、スピードは、通常問題にはなりません。
    • Memory bandwidth. CPU がキャッシュに収まらないようなデータを要求した場合、メイン・メモリー のバンド幅はボトルネックになります。 これはほとんどのシステムで分かりにくいボトルネックとなりますが、 誰かはそれを知っているべきです。

    5.1.1 MySQL Design Limitations/Tradeoffs

    When using the MyISAM storage engine, MySQL uses extremely fast table locking (multiple readers / single writers). The biggest problem with this table type is a if you have a mix of a steady stream of updates and slow selects on the same table. If this is a problem with some tables, you can use another table type for these. 「7 MySQL テーブル型」節参照.

    MySQL can work with both transactional and not transactional tables. To be able to work smoothly with not transactional tables (which can't rollback if something goes wrong), MySQL has the following rules:

    • All columns have default values.
    • If you insert a 'wrong' value in a column like a NULL in a NOT NULL column or a too big numerical value in a numerical column, MySQL will instead of giving an error instead set the column to the 'best possible value'. For numerical values this is 0, the smallest possible values or the largest possible value. For strings this is either the empty string or the longest possible string that can be in the column.
    • All calculated expressions returns a value that can be used instead of signaling an error condition. For example 1/0 returns NULL

    The reason for the above rules is that we can't check these conditions before the query starts to execute. If we encounter a problem after updating a few rows, we can't just rollback as the table type may not support this. We can't stop because in that case the update would be 'half done' which is probably the worst possible scenario. In this case it's better to 'do the best you can' and then continue as if nothing happened.

    The above means that one should not use MySQL to check fields content, but one should do this in the application.

    5.1.2 Portability

    全てのSQLサーバはそれぞれ異なるSQL処理ルーチンにより構成されています。 したがって色々なSQLサーバ上で同じように動作するような(ポータブルな) SQLアプリケーションを書くのは手間がかかります。 確かに単純なインサートやセレクトを行うようなものは簡単ですが、 必要な機能が増えれば増えるほど難しくなっていきます。 高速動作を要求されるSQLプラットフォームの数が増えれば増えるほど そのようなアプリケーションの開発は大変になっていきます。

    ポータブルな多機能アプリケーションを開発するためには 沢山のSQLサーバでの動作を検証する必要があります。

    You can use the MySQL crash-me program/web-page http://www.mysql.com/information/crash-me.php to find functions, types, and limits you can use with a selection of database servers. Crash-me now tests far from everything possible, but it is still comprehensive with about 450 things tested.

    For example, you shouldn't have column names longer than 18 characters if you want to be able to use Informix or DB2.

    Both the MySQL benchmarks and crash-me programs are very database-independent. By taking a look at how we have handled this, you can get a feeling for what you have to do to write your application database-independent. The benchmarks themselves can be found in the `sql-bench' directory in the MySQL source distribution. They are written in Perl with DBI database interface (which solves the access part of the problem).

    See http://www.mysql.com/information/benchmarks.html for the results from this benchmark.

    As you can see in these results, all databases have some weak points. That is, they have different design compromises that lead to different behaviour.

    If you strive for database independence, you need to get a good feeling for each SQL server's bottlenecks. MySQL is very fast in retrieving and updating things, but will have a problem in mixing slow readers/writers on the same table. Oracle, on the other hand, has a big problem when you try to access rows that you have recently updated (until they are flushed to disk). Transaction databases in general are not very good at generating summary tables from log tables, as in this case row locking is almost useless.

    To get your application really database-independent, you need to define an easy extendable interface through which you manipulate your data. As C++ is available on most systems, it makes sense to use a C++ classes interface to the databases.

    If you use some specific feature for some database (like the REPLACE command in MySQL), you should code a method for the other SQL servers to implement the same feature (but slower). With MySQL you can use the /*! */ syntax to add MySQL-specific keywords to a query. The code inside /**/ will be treated as a comment (ignored) by most other SQL servers.

    If high performance is more important than exactness, as in some web applications, it is possibile to create an application layer that caches all results to give you even higher performance. By letting old results 'expire' after a while, you can keep the cache reasonably fresh. This provides a method to handle high load spikes, in which case you can dynamically increase the cache and set the expire timeout higher until things get back to normal.

    In this case the table creation information should contain information of the initial size of the cache and how often the table should normally be refreshed.

    5.1.3 What Have We Used MySQL For?

    MySQL の初期の開発期には、MySQL は我々のもっとも大口の顧客に合うように 機能が作成されました。 彼らは、いくつかのスウェーデン最大手の小売り業者 のために、倉庫に入れている（商品）データを取り扱います。

    我々は、すべての店から、全ボーナス・カード取扱高の、その週間まとめを得ます。 そして、その店のオーナにとって有益な情報、その店の広告キャンペーンが お客にどの程度影響を及ぼすか、を提供することが、我々に求められています。

    そのデータは、とても大きくて (約700万/月 回の取り扱い)、 我々はその顧客に提供する必要のあるデータを 4〜10年分、持っています。 我々は、カスタマーから、彼らがこのデータからできる新しいレポートに ”即時に”アクセスしたいという、要求を受けました。

    我々はこれを、全ての月ごとの情報を圧縮した 'transaction' テーブルに 保存することで解決しました。 We have a set of simple macros (script) that generates summary tables grouped by different criteria (product group, customer id, store ...) from the transaction tables. そのレポートは Web ページで、これは小さな perl スクリプトで動的に 作成されます。 この perl script は Web Page を分析し、SQL 文を 実行し、結果を挿入します。 We would have used PHP or mod_perl instead but they were not available at that time.

    画像データのために、我々は簡単なツールを C でかきました。 これは SQL のクエリの結果を元に(結果にいくつか処理をして) GIF を提供します。 これも動的に perl スクリプト(HTML ファイルを分析する)から実行されます。

    In most cases a new report can simply be done by copying an existing script and modifying the SQL query in it. In some cases, we will need to add more fields to an existing summary table or generate a new one, but this is also quite simple, as we keep all transactions tables on disk. (Currently we have at least 50G of transactions tables and 200G of other customer data.)

    We also let our customers access the summary tables directly with ODBC so that the advanced users can themselves experiment with the data.

    我々はこれらを Sun Ultra SPARCstation (2x200 Mz) で扱っていますが、 なんの問題もありません。 We recently upgraded one of our servers to a 2 CPU 400 Mhz UltraSPARC, and we are now planning to start handling transactions on the product level, which would mean a ten-fold increase of data. We think we can keep up with this by just adding more disk to our systems.

    We are also experimenting with Intel-Linux to be able to get more CPU power cheaper. 現在、我々はバイナリ互換のデータベースフォーマットを持っており (new in Version 3.23) 、我々はこれをアプリケーションのいくつかの部分に使用しはじ める事でしょう。

    Our initial feelings are that Linux will perform much better on low-to-medium load and Solaris will perform better when you start to get a high load because of extreme disk IO, but we don't yet have anything conclusive about this. After some discussion with a Linux Kernel developer, this might be a side effect of Linux giving so much resources to the batch job that the interactive performance gets very low. This makes the machine feel very slow and unresponsive while big batches are going. Hopefully this will be better handled in future Linux Kernels.

    5.1.4 The MySQL Benchmark Suite

    This should contain a technical description of the MySQL benchmark suite (and crash-me), but that description is not written yet. Currently, you can get a good idea of the benchmark by looking at the code and results in the `sql-bench' directory in any MySQL source distributions.

    This benchmark suite is meant to be a benchmark that will tell any user what things a given SQL implementation performs well or poorly at.

    Note that this benchmark is single threaded, so it measures the minimum time for the operations. We plan to in the future add a lot of multi-threaded tests to the benchmark suite.

    For example, (run on the same NT 4.0 machine):

    Reading 2000000 rows by index Seconds Seconds
    mysql 367 249
    mysql_odbc 464
    db2_odbc 1206
    informix_odbc 121126
    ms-sql_odbc 1634
    oracle_odbc 20800
    solid_odbc 877
    sybase_odbc 17614
    Inserting (350768) rows Seconds Seconds
    mysql 381 206
    mysql_odbc 619
    db2_odbc 3460
    informix_odbc 2692
    ms-sql_odbc 4012
    oracle_odbc 11291
    solid_odbc 1801
    sybase_odbc 4802

    In the above test MySQL was run with a 8M index cache.

    We have gathered some more benchmark results at http://www.mysql.com/information/benchmarks.html.

    Note that Oracle is not included because they asked to be removed. All Oracle benchmarks have to be passed by Oracle! We believe that makes Oracle benchmarks very biased because the above benchmarks are supposed to show what a standard installation can do for a single client.

    To run the benchmark suite, you have to download a MySQL source distribution, install the Perl DBI driver, the Perl DBD driver for the database you want to test and then do: 

    cd sql-bench
perl run-all-tests --server=#

    where # is one of supported servers. You can get a list of all options and supported servers by doing run-all-tests --help.

    crash-me tries to determine what features a database supports and what its capabilities and limitations are by actually running queries. For example, it determines:

    • What column types are supported
    • How many indexes are supported
    • What functions are supported
    • How big a query can be
    • How big a VARCHAR column can be

    We can find the result from crash-me on a lot of different databases at http://www.mysql.com/information/crash-me.php.

    5.1.5 Using Your Own Benchmarks

    You should definitely benchmark your application and database to find out where the bottlenecks are. By fixing it (or by replacing the bottleneck with a 'dummy module') you can then easily identify the next bottleneck (and so on). Even if the overall performance for your application is sufficient, you should at least make a plan for each bottleneck, and decide how to solve it if someday you really need the extra performance.

    For an example of portable benchmark programs, look at the MySQL benchmark suite. 「5.1.4 The MySQL Benchmark Suite」節参照. You can take any program from this suite and modify it for your needs. By doing this, you can try different solutions to your problem and test which is really the fastest solution for you.

    It is very common that some problems only occur when the system is very heavily loaded. We have had many customers who contact us when they have a (tested) system in production and have encountered load problems. In every one of these cases so far, it has been problems with basic design (table scans are not good at high load) or OS/Library issues. Most of this would be a lot easier to fix if the systems were not already in production.

    To avoid problems like this, you should put some effort into benchmarking your whole application under the worst possible load! You can use Super Smack for this, and it is available at: http://www.mysql.com/Downloads/super-smack/super-smack-1.0.tar.gz. As the name suggests, it can bring your system down to its knees if you ask it, so make sure to use it only on your development systems.

    5.2 Optimizing SELECTs and Other Queries

    最初に、全てのクエリに影響する一つの事柄をのべます： より複雑な権限の設定を行うと、オーバーヘッドが多くなります。

    もしあなたがいかなる GRANT 文も行っていなければ、 MySQL はパーミッションの検査を少ししか最適化しないでしょう。 So if you have a very high volume it may be worth the time to avoid grants. Otherwise more permission check results in a larger overhead.

    もし MySQL 関数のあるものが確実に問題を引き起こしているのならば、 常に MySQL クライアント側は以下のようになります： 

    mysql> SELECT BENCHMARK(1000000,1+1);
+------------------------+
| BENCHMARK(1000000,1+1) |
+------------------------+
|                      0 |
+------------------------+
1 row in set (0.32 sec)

    上の例では MySQL は 1,000,000 + 式を 0.32 秒で実行できています (たんなる PentiumII 400MHz マシンで)。

    全ての MySQL 関数は最適化されていますが、 いくつかは例外があるかもしれません。 BENCHMARK(loop_count,expression)はあなたのクエリの 問題を見つけるためのとてもよいツールです。

    5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)

        EXPLAIN tbl_name
or  EXPLAIN SELECT select_options

    EXPLAIN tbl_name は、 DESCRIBE tbl_name や SHOW COLUMNS FROM tbl_name と同義です。

    もし EXPLAIN をともなって SELECT 構文を実行した場合、 MySQL はこの SELECT がいかに動作するかを説明し、 いかにテーブルが結合されるかの情報を与えます。

    EXPLAIN の情報を元に、インデックスを使用した速い SELECT を 得るためにテーブルにインデックスを加えなくてはならないという事がわかります。

    You should frequently run ANALYZE TABLE to update table statistics such as cardinality of keys which can affect the choices the optimiser makes. 「4.5.2 ANALYZE TABLE Syntax」節参照.

    テーブル結合の最適化もオプションによって見ることができます。 SELECT 構文での結合を強制的に最適化するには STRAIGHT_JOIN 節を加え ます。

    単純ではない join のために、EXPLAIN は SELECT 文で使用されている それぞれのテーブルの情報を返します。 テーブルは読まれる順に表示されます。MySQL は one-sweep multi-join method を用いた全ての join を解決します。これは MySQL は最初のテーブルから 一レコード読み込み、二つ目のテーブルからマッチしたレコードを探し、そして三番目を 探すということです。 全てのテーブルが処理される時、選択されたフィールドを出力し、テーブルの一覧は よりマッチするレコードをもつテーブルを見つけるまで back-track されます。 次のレコードはこのテーブルから読まれ、次のテーブルから処理を続けます。

    In MySQL version 4.1 the EXPLAIN output was changed to work better with constructs like UNIONs, subqueries and derived tables. Most notable is the addition of two new columns: id and select_type.

    EXPLAIN の出力は以下のフィールドを含みます：

    id
    SELECT identifier, the sequential number of this SELECT within the query.
    select_type
    Type of SELECT clause, which can be any of the following:
    SIMPLE
    Simple SELECT (without UNIONs or subqueries).
    PRIMARY
    Outermost SELECT.
    UNION
    Second and further UNION SELECTs.
    DEPENDENT UNION
    Second and further UNION SELECTSs, dependent on outer subquery.
    SUBSELECT
    First SELECT in subquery.
    DEPENDENT SUBSELECT
    First SELECT, dependent on outer subquery.
    DERIVED
    Derived table SELECT.
    table
    出力レコードが参照されるテーブル
    type
    join タイプ. join type は以下のものがあります。良い物から順に書いています：
    system
    テーブルが一レコードだけ持っている (= system table). これは const join type の特別な場合です。
    const
    テーブルは、最もマッチするレコードを１つもっており、これはクエリの 最初に読まれます。 1 つのレコードであるため、このレコード中のフィールドの値は オプティマイザーによって常数としてみなされます。 1回だけ読まれるので、const テーブルはとても速いです!
    eq_ref
    前のテーブルのそれぞれのレコードと結合する際、このテーブルから1レコード読まれま す。これは join では const よりも良い形です。 インデックスの全てのパートが join で使用され、かつ、インデックスが UNIQUE か PRIMARY KEY であるときに、これは使用されます。
    ref
    インデックスの値に合ったすべてのレコードは、前のテーブルからレコードと結合するた めに、このテーブルから読まれるでしょう。 もしその join がキーの一番左の接頭部分だけを使用するならば、 あるいは、もしそのキーが UNIQUE や PRIMARY KEY でなければ (言い換えるなら、もし join がキーの値を元に一つだけの、レコードを選択できなけれ ば)、ref は使用されます。 もしそのキーがいくつかのマッチするレコードに使用されるだけなら、 join は良い形です。
    range
    示された範囲内にあるレコードのみが検索されます。 key 項目はどのインデックスが使用されているか示します。 The key_len contains the longest key part that was used. The ref column will be NULL for this type.
    index
    ALL と同じですが、インデックスツリーが走査される場合のみを除きます。 これは、インデックスファイルはデータファイルよりも小さいため、通常 ALL よ り速いです。
    ALL
    前のテーブルのレコードとのそれぞれの結合において、全テーブルが走査されます。 もしそのテーブルが最初のテーブルで const 状態ではないなら、通常 これは良くありません。他の状態ではとても悪くなります。 これは普通、レコードががより早いテーブルからから定数値に基づいて検索することがで きるように、 インデックスを追加することにより ALL を避けることが可能です。
    possible_keys
    possible_keys 項目は、MySQL がテーブルからレコードを見つけるために どのインデックスを使用する事ができたかを示します。 注意: このフィールドはテーブルの順にまったく依存しません。これは、 possible_keys 内のいくつかのキーは、生成されたテーブル順での実行に使用でき ないことを意味します。 この項目が空なら、関連した インデックスは無いということです。この場合、あなたは WHERE 節を 調べることによって、クエリの性能を向上させることができるかもしれません。 もしそれがインデックスに適合したフィールドを参照しているならば。 仮にそうだとすると、適切なインデックスを作成し、 EXPLAIN でクエリを もう一度チェックしてみてください。 テーブルがどんなインデックスを持っているかみるには、SHOW INDEX FROM tbl_name とします。
    key
    key 項目は、 MySQL が使用すると実際に決めたキー(インデックス)を示します。 どのインデックスも選ばれなかったならば、インデックスは NULL です。 MySQL に possible_keys 項目にあるインデックスを使用するように 強制するにはクエリに USE KEY/IGNORE KEY を使用することができます。 「6.4.1 SELECT 構文」節参照. Also, running myisamchk --analyze ( 「4.4.6.1 myisamchk 起動構文」節参照) or ANALYZE TABLE ( 「4.5.2 ANALYZE TABLE Syntax」節参照) on the table will help the optimiser choose better indexes.
    key_len
    key_len 項目は、MySQL が使用すると決めたキーの長さを示します。 もし key が NULL なら、長さは NULL です。 注意: これはMySQL がマルチパートキーのいくつのパートを実際に使用 するかを示します。
    ref
    ref 項目は、テーブルからレコードを select するために、どのフィールドや 定数が key と共に使用されたかを示します。
    rows
    rows フィールドは、MySQL がクエリを実行するために検査する 必要があると考えているレコードの数を示します。
    Extra
    このフィールドは、MySQL がどのようにクエリを解決するかの追加情報 を含んでいます。ここで、このフィールドに現れ得る様々なテキスト文字列の説明 をします:
    Distinct
    MySQL will not continue searching for more rows for the current row combination after it has found the first matching row.
    Not exists
    MySQL はクエリの LEFT JOIN 最適化を行なうことができて、 LEFT JOIN 判定基準に適合する１つのレコードを見つけた後、前のレコード組 み合わせについてこのテーブルにそれ以上のレコードを検査しません。 Here is an example for this: 
    SELECT * FROM t1 LEFT JOIN t2 ON t1.id=t2.id WHERE t2.id IS NULL;
    Assume that t2.id is defined with NOT NULL. In this case MySQL will scan t1 and look up the rows in t2 through t1.id. If MySQL finds a matching row in t2, it knows that t2.id can never be NULL, and will not scan through the rest of the rows in t2 that has the same id. In other words, for each row in t1, MySQL only needs to do a single lookup in t2, independent of how many matching rows there are in t2.
    range checked for each record (index map: #)
    MySQL は使用すべき本当に良いインデックスを見つけられませんでし た。先行するテーブル内に各レコードの結合の代わりに、テーブルからレコード を取り出すためにどのインデックスを使用するかチェックを行ないます。これは とても速いというわけではありませんが、もちろんインデックス無しでの結合を 行なわなければならないよりは速いです。
    Using filesort
    MySQL は、ソート順でレコードを取り出す方法を見つけ出すため、余 計なパスの実行が必要です。ソートは、join type に一致する全てのレ コードを通して行なわれ、WHERE に適合する全てのレコードについて、 ソートキーとレコードへのポインタを格納します。それから、キーがソートされま す。最後にレコードはソートされた順に取り出されます。
    Using index
    フィールド情報は、実際のレコードから読み込む追加シークを行なうことはせず に、インデックスツリー内の情報だけを使用するテーブルから取り出されます。 テーブルについての使用される全てのフィールドが同じインデックスの一部であ る時にこれが行なわれます。
    Using temporary
    クエリを解決できるように、MySQL は、結果を保持するための一時テー ブルを作成する必要があります。これは通常 GROUP BY が行なわれたも のとは別のフィールド上で ORDER BY を行なう場合に発生します。
    Using where
    どのレコードが次のテーブルに対して適合するか、またはクライアントに送られ るかを制限するために、WHERE 節が使用されます。この情報がなくて、 テーブルが型 ALL か index であれば、クエリ内に何か間違った ものがあります(テーブルから全てのレコードを fetch/examine しようとしてい るのでなければ)。
    クエリを可能な限り速く得たい場合、Using filesort と Using temporary に注意すべきです。

    EXPLAIN 出力の rows フィールド内のすべての値を増やすことによ り、join がどのように良くなるかの良い表示を得ることができます。これは、 MySQL がクエリ実行の検査をする必要があるレコードのおおよその数を 知らせます。この数は max_join_size 変数でのクエリを制限する時にも使 用します。 「5.5.2 サーバーパラメーターのチューニング」節参照.

    以下の例は、EXPLAIN が提供する情報を元に、いかに JOIN が最適化 できるかの例です。

    以下のような EXPLAIN で検査する SELECT 構文があるとします： 

    EXPLAIN SELECT tt.TicketNumber, tt.TimeIn,
            tt.ProjectReference, tt.EstimatedShipDate,
            tt.ActualShipDate, tt.ClientID,
            tt.ServiceCodes, tt.RepetitiveID,
            tt.CurrentProcess, tt.CurrentDPPerson,
            tt.RecordVolume, tt.DPPrinted, et.COUNTRY,
            et_1.COUNTRY, do.CUSTNAME
        FROM tt, et, et AS et_1, do
        WHERE tt.SubmitTime IS NULL
            AND tt.ActualPC = et.EMPLOYID
            AND tt.AssignedPC = et_1.EMPLOYID
            AND tt.ClientID = do.CUSTNMBR;

    この例では、以下のように仮定します：

    • フィールドは以下のように定義されています：
      Table Column Column type
      tt ActualPC CHAR(10)
      tt AssignedPC CHAR(10)
      tt ClientID CHAR(10)
      et EMPLOYID CHAR(15)
      do CUSTNMBR CHAR(15)
    • テーブルは以下のインデックスを持ちます：
      Table Index
      tt ActualPC
      tt AssignedPC
      tt ClientID
      et EMPLOYID (primary key)
      do CUSTNMBR (primary key)
    • tt.ActualPC の値は、いちように分布して(配置されて)いません。

    最初、いかなる最適化も行われていない状態では、EXPLAIN 構文は 以下の情報を提示します： 

    table type possible_keys                key  key_len ref  rows  Extra
et    ALL  PRIMARY                      NULL NULL    NULL 74
do    ALL  PRIMARY                      NULL NULL    NULL 2135
et_1  ALL  PRIMARY                      NULL NULL    NULL 74
tt    ALL  AssignedPC,ClientID,ActualPC NULL NULL    NULL 3872
      range checked for each record (key map: 35)

    それぞれのテーブルで、type が ALL になっています。 これは MySQL が全てのテーブルを全結合することを示します！ それぞれのテーブル内の行数分から作った物が調べられるので、とても長い時間がかかり ます！ この場合、74 * 2135 * 74 * 3872 = 45,268,558,720 行調べることになります。 テーブルが肥大化したときにかかる時間を考えてください....

    一つ問題があります。(まだ) MySQL がフィールドのインデックスを効果的に 使用できていません。 この例の場合では、VARCHAR と CHAR は、それらが同じ長さで定義されて いれば、変わりがありません。 tt.ActualPC は CHAR(10) と定義されており、 et.EMPLOYID は CHAR(15) です。これらの長さは違います。

    この不釣り合いを修正するにあたり、ALTER TABLE を使って ActualPC の長さを 10 文字から 15 文字にします： 

    mysql> ALTER TABLE tt MODIFY ActualPC VARCHAR(15);

    これで tt.ActualPC and et.EMPLOYID は両方とも VARCHAR(15) になりました。 EXPLAIN 構文を実行し直すと、以下を提示します： 

    table type   possible_keys   key     key_len ref         rows    Extra
tt    ALL    AssignedPC,ClientID,ActualPC NULL NULL NULL 3872    Using where
do    ALL    PRIMARY         NULL    NULL    NULL        2135
      range checked for each record (key map: 1)
et_1  ALL    PRIMARY         NULL    NULL    NULL        74
      range checked for each record (key map: 1)
et    eq_ref PRIMARY         PRIMARY 15      tt.ActualPC 1

    まだ完全ではありませんが、よりよくなっています(rows 値の 生成量は 74 より小さくなります)。この場合、実行は数秒でしょう。

    A second alteration can be made to eliminate the column length mismatches for the tt.AssignedPC = et_1.EMPLOYID and tt.ClientID = do.CUSTNMBR comparisons: 

    mysql> ALTER TABLE tt MODIFY AssignedPC VARCHAR(15),
    ->                MODIFY ClientID   VARCHAR(15);

    これで EXPLAIN は以下を出力します： 

    table type   possible_keys   key      key_len ref           rows Extra
et    ALL    PRIMARY         NULL     NULL    NULL          74
tt    ref    AssignedPC,     ActualPC 15      et.EMPLOYID   52   Using where
             ClientID,
             ActualPC
et_1  eq_ref PRIMARY         PRIMARY  15      tt.AssignedPC 1
do    eq_ref PRIMARY         PRIMARY  15      tt.ClientID   1

    これは ``ほとんど'' 最良に近いです。

    残る問題は、デフォルトでは、MySQL は tt.ActualPC フィールド内の 値がまんべんなく分布していると想定しており、この tt テーブルの場合には 適合しません。 幸運にも、これを MySQL に教えるのはとても簡単です： 

    shell> myisamchk --analyze PATH_TO_MYSQL_DATABASE/tt
shell> mysqladmin refresh

    これで join は ``完璧'' です。 EXPLAIN は以下の結果を示します： 

    table type   possible_keys key     key_len ref           rows Extra
tt    ALL    AssignedPC    NULL    NULL    NULL          3872 Using where
             ClientID,
             ActualPC
et    eq_ref PRIMARY       PRIMARY 15      tt.ActualPC   1
et_1  eq_ref PRIMARY       PRIMARY 15      tt.AssignedPC 1
do    eq_ref PRIMARY       PRIMARY 15      tt.ClientID   1

    EXPLAIN の出力中の rows 項目は、 MySQL JOIN オプティマイ ザーによる、``推測'' です； クエリの最適化のために、この数値が実際に近いかどうかをチェックすべきです。 そうでなければ、SELECT ステートメントで STRAIGHT_JOIN を使用 し、FROM 節に異なる順でテーブルを並べることで、良いパフォーマンスを 得られます。

    5.2.2 Estimating Query Performance

    ほとんどの場合、ディスク・シークを数えることでだいたいのパフォーマンスを予測でき ます。 小さなテーブルでは、通常、1回のディスク・シークでレコードを見つけれるでしょう (インデックスがたぶんキャッシュされるので)。 大きなテーブルでは、 おおよその予測として、(B++ ツリーインデックスを使用している場合)、 log(row_count) / log(index_block_length / 3 * 2 / (index_length + data_pointer_length)) + 1 シーク、1レコードを見つけるのに必要となるでしょう。

    MySQL では、インデックス・ブロックは通常 1024 バイトで、 データ・ポインターは通常 4 バイトです。 これは、 インデックス長が 3 (medium integer) 、データが 500,000 レコードあるテーブルでは、 log(500,000)/log(1024/3*2/(3+4)) + 1 = 4 シークとなります。

    As the above index would require about 500,000 * 7 * 3/2 = 5.2M, (assuming that the index buffers are filled to 2/3, which is typical) you will probably have much of the index in memory and you will probably only need 1-2 calls to read data from the OS to find the row.

    書き込み時には、上の場合、新しいインデックスを書き込める場所を 探し出すのに、4 シークかかり、さらに、通常、インデックスを更新し、 レコードを書くのに 2 シーク必要です。

    Note that the above doesn't mean that your application will slowly degenerate by log N! As long as everything is cached by the OS or SQL server things will only go marginally slower while the table gets bigger. After the data gets too big to be cached, things will start to go much slower until your applications is only bound by disk-seeks (which increase by log N). To avoid this, increase the index cache as the data grows. 「5.5.2 サーバーパラメーターのチューニング」節参照.

    5.2.3 SELECT クエリの速度

    通常、遅い SELECT ... WHERE を速くするには、 まず最初にインデックスがあるかどうかをチェックします。 「5.4.3 MySQL はどのようにインデックスを使用するか？」節参照. 違うテーブルを参照する場合には、普通はインデックスをともなうべきです。 EXPLAIN コマンドを使用すれば、SELECT でどのインデックスが 使用されているか確認できます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.

    Some general tips:

    • To help MySQL optimize queries better, run myisamchk --analyze on a table after it has been loaded with relevant data. This updates a value for each index part that indicates the average number of rows that have the same value. (For unique indexes, this is always 1, of course.) MySQL will use this to decide which index to choose when you connect two tables with 'a non-constant expression'. You can check the result from the analyze run by doing SHOW INDEX FROM table_name and examining the Cardinality column.
    • インデックスとデータをインデックス順に従ってソートするには、 myisamchk --sort-index --sort-records=1 を使用します (もし １番目のインデックス順にソートするなら)。 If you have a unique index from which you want to read all records in order according to that index, this is a good way to make that faster. しかし、このソート方法は最適状態では書かれず、また大きなテーブルでは 多くの時間がかかることに注意してください！

    5.2.4 MySQL はどのように WHERE 節を最適化するか？

    WHERE の最適化は、WHERE がほとんど SELECT で使用されるため、 SELECT に置かれています。 しかし、同じ最適化は DELETE や UPDATE 文でも使用されます。

    このセクションの最適化の説明はまだ不十分です。 なぜなら、 MySQL はとても多くの最適化を行っており、 それら全てについての説明を書ける時間が、我々はとれません。

    MySQLによる最適化のいくつかを以下に示します:

    • 括弧の除去 (全ての不必要な括弧は削除されます): 
         ((a AND b) AND c OR (((a AND b) AND (c AND d))))
-> (a AND b AND c) OR (a AND b AND c AND d)
    • 定数の保持: 
         (a<b AND b=c) AND a=5
-> b>5 AND b=c AND a=5
    • 定数条件の除去 (定数保持のために必要とされます): 
         (B>=5 AND B=5) OR (B=6 AND 5=5) OR (B=7 AND 5=6)
-> B=5 OR B=6
    • インデックスに使用される全ての表現は一度だけ評価されます。
    • 一つのテーブル上の WHERE がない COCOUNT(*) は、 MyISAM and HEAP の場合は テーブルの情報から 直接取り出されます。これはまた 1つのテーブルだけで NOT NULL を 使用したときも同様です。
    • 不当な定数表現は早く検出されます。 MySQL は不可能な SELECT 構文を素早く見つけ、0 行を結果として返 します。
    • GROUP BY または group 関数 (COUNT(), MIN()...) を使用しない 場合は、 HAVING は WHERE とマージされます。
    • 各サブ結合についての速い WHERE 評価を得るために、また、可能な限り 早くレコードをスキップするために、各サブ結合についてより簡単な WHERE が構築されます。
    • 全ての定数テーブルをクエリー中の他のテーブルより先に読みます。 定数テーブルは次です:
      • 0 または 1 レコードのテーブル。
      • WHERE 節で UNIQUE インデックスや PRIMARY KEY が使用されたテ ーブルで、かつ、全てのインデックスが定数式で使用されていて、 かつ、インデックスのパートが NOT NULL で定義されているテーブル。
      以下のテーブルのように定数だけを使用するテーブル: 
      mysql> SELECT * FROM t WHERE primary_key=1;
mysql> SELECT * FROM t1,t2
    ->          WHERE t1.primary_key=1 AND t2.primary_key=t1.id;
    • テーブルを結合するために最良の結合の組合せを見つけます。全ての可能性を試して 。 ORDER BY または GROUP 内の全てのフィールドが同じテーブルの場合は、 このテーブルは結合時に最初に優先されます。
    • ORDER BY 節と GROUP BY 節がある場合、または ORDER BY か GROUP BY が結合キュー内の最初のテーブルではない他のテーブルからの項目を 含む場合、一時テーブルが生成されます。
    • もし SQL_SMALL_RESULT を使用するなら, MySQL はメモリー内の一時 テーブルを使用します
    • 各テーブルのインデックスはクエリされ、得られる行の 30% 未満の幅しかない最良のイ ンデックスが使用されます。 そのようなインデックスが見つけられない場合、素早いテーブルの走査 (quick table scan)が使用されます。
    • 同じように、MySQL はデータファイルを等しく調べはしないインデックスから レコードを読むことが可能です。もし全てのフィールドが数値型のインデックスなら、 インデックスツリーだけがクエリの解決に使用されます。
    • 各レコードが出力される前に、HAVING 節に適合するものをスキップします。

    以下はとても速いクエリの例です: 

    mysql> SELECT COUNT(*) FROM tbl_name;
mysql> SELECT MIN(key_part1),MAX(key_part1) FROM tbl_name;
mysql> SELECT MAX(key_part2) FROM tbl_name
    ->        WHERE key_part_1=constant;
mysql> SELECT ... FROM tbl_name
    ->        ORDER BY key_part1,key_part2,... LIMIT 10;
mysql> SELECT ... FROM tbl_name
    ->        ORDER BY key_part1 DESC,key_part2 DESC,... LIMIT 10;

    以下のクエリはインデックスツリーのみを使用します(インデックス化されているフィー ルドは数値型と仮定します)： 

    mysql> SELECT key_part1,key_part2 FROM tbl_name WHERE key_part1=val;
mysql> SELECT COUNT(*) FROM tbl_name
    ->        WHERE key_part1=val1 AND key_part2=val2;
mysql> SELECT key_part2 FROM tbl_name GROUP BY key_part1;

    以下のクエリは、ソートされた行の検索にインデックスを使用します： 

    mysql> SELECT ... FROM tbl_name
    ->            ORDER BY key_part1,key_part2,... ;
mysql> SELECT ... FROM tbl_name
    ->            ORDER BY key_part1 DESC,key_part2 DESC,... ;

    5.2.5 How MySQL Optimizes DISTINCT

    DISTINCT is converted to a GROUP BY on all columns, DISTINCT combined with ORDER BY will in many cases also need a temporary table.

    When combining LIMIT # with DISTINCT, MySQL will stop as soon as it finds # unique rows.

    If you don't use columns from all used tables, MySQL will stop the scanning of the not used tables as soon as it has found the first match. 

    SELECT DISTINCT t1.a FROM t1,t2 where t1.a=t2.a;

    In the case, assuming t1 is used before t2 (check with EXPLAIN), then MySQL will stop reading from t2 (for that particular row in t1) when the first row in t2 is found.

    5.2.6 MySQL はどのように LEFT JOIN と RIGHT JOIN を最適化するか？

    MySQL の A LEFT JOIN B は以下のように組みこまれています：

    • The table B is set to be dependent on table A and all tables that A is dependent on.
    • テーブル A が LEFT JOIN 条件中に使用される全てのテーブル （ただし B は除く）に依存すると、セットされます。
    • 全ての LEFT JOIN 条件が WHERE 節に移動されます。
    • All standard join optimizations are done, with the exception that a table is always read after all tables it is dependent on. If there is a circular dependence then MySQL will issue an error.
    • 全ての WHERE 節の最適化が行われます。
    • WHERE 節にマッチするレコードが A にあり、 LEFT JOIN 条件にマッチするレコードが B にない場合、 全てのフィールドが NULL にセットされた B のレコードが 作成されます。
    • If you use LEFT JOIN to find rows that don't exist in some table and you have the following test: column_name IS NULL in the WHERE part, where column_name is a column that is declared as NOT NULL, then MySQL will stop searching after more rows (for a particular key combination) after it has found one row that matches the LEFT JOIN condition.

    RIGHT JOIN is implemented analogously as LEFT JOIN.

    The table read order forced by LEFT JOIN and STRAIGHT JOIN will help the join optimizer (which calculates in which order tables should be joined) to do its work much more quickly, as there are fewer table permutations to check.

    Note that the above means that if you do a query of type: 

    SELECT * FROM a,b LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key)
         WHERE b.key=d.key

    MySQL will do a full scan on b as the LEFT JOIN will force it to be read before d.

    The fix in this case is to change the query to: 

    SELECT * FROM b,a LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key)
         WHERE b.key=d.key

    5.2.7 How MySQL Optimises ORDER BY

    In some cases MySQL can uses index to satisfy an ORDER BY or GROUP BY request without doing any extra sorting.

    The index can also be used even if the ORDER BY doesn't match the index exactly, as long as all the unused index parts and all the extra are ORDER BY columns are constants in the WHERE clause. The following queries will use the index to resolve the ORDER BY / GROUP BY part: 

    SELECT * FROM t1 ORDER BY key_part1,key_part2,...
SELECT * FROM t1 WHERE key_part1=constant ORDER BY key_part2
SELECT * FROM t1 WHERE key_part1=constant GROUP BY key_part2
SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 DESC
SELECT * FROM t1 WHERE key_part1=1 ORDER BY key_part1 DESC,key_part2 DESC

    Some cases where MySQL can not use indexes to resolve the ORDER BY: (Note that MySQL will still use indexes to find the rows that matches the WHERE clause):

    • You are doing an ORDER BY on different keys: SELECT * FROM t1 ORDER BY key1,key2
    • You are doing an ORDER BY using non-consecutive key parts. SELECT * FROM t1 WHERE key2=constant ORDER BY key_part2
    • You are mixing ASC and DESC. SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 ASC
    • The key used to fetch the rows are not the same one that is used to do the ORDER BY: SELECT * FROM t1 WHERE key2=constant ORDER BY key1
    • You are joining many tables and the columns you are doing an ORDER BY on are not all from the first not-const table that is used to retrieve rows (This is the first table in the EXPLAIN output which doesn't use a const row fetch method).
    • You have different ORDER BY and GROUP BY expressions.
    • The used table index is an index type that doesn't store rows in order. (Like the HASH index in HEAP tables).

    In the cases where MySQL have to sort the result, it uses the following algorithm:

    • Read all rows according to key or by table scanning. Rows that don't match the WHERE clause are skipped.
    • Store the sort-key in a buffer (of size sort_buffer).
    • When the buffer gets full, run a qsort on it and store the result in a temporary file. Save a pointer to the sorted block. (In the case where all rows fits into the sort buffer, no temporary file is created)
    • Repeat the above until all rows have been read.
    • Do a multi-merge of up to MERGEBUFF (7) regions to one block in another temporary file. Repeat until all blocks from the first file are in the second file.
    • Repeat the following until there is less than MERGEBUFF2 (15) blocks left.
    • On the last multi-merge, only the pointer to the row (last part of the sort-key) is written to a result file.
    • Now the code in `sql/records.cc' will be used to read through them in sorted order by using the row pointers in the result file. To optimise this, we read in a big block of row pointers, sort these and then we read the rows in the sorted order into a row buffer (record_rnd_buffer) .

    You can with EXPLAIN SELECT ... ORDER BY check if MySQL can use indexes to resolve the query. If you get Using filesort in the extra column, then MySQL can't use indexes to resolve the ORDER BY. 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.

    If you want to have a higher ORDER BY speed, you should first see if you can get MySQL to use indexes instead of having to do an extra sorting phase. If this is not possible, then you can do:

    • Increase the size of the sort_buffer variable.
    • Increase the size of the record_rnd_buffer variable.
    • Change tmpdir to point to a dedicated disk with lots of empty space. If you use MySQL 4.1 or later you can spread load between several physical disks by setting tmpdir to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion. Note: These paths should end up on different physical disks, not different partitions of the same disk.

    MySQL by default sorts all GROUP BY x,y[,...] queries as if you would have specified ORDER BY x,y[,...]. MySQL will optimise away any ORDER BY as above without any speed penalty. If you by in some cases don't want to have the result sorted you can specify ORDER BY NULL: 

    INSERT INTO foo SELECT a,COUNT(*) FROM bar GROUP BY a ORDER BY NULL;

    5.2.8 MySQL はどのように LIMIT を最適化するか？

    In some cases MySQL will handle the query differently when you are using LIMIT # and not using HAVING:

    • もし LIMIT を使用して限定した数だけ select を行うなら、 MySQL は、 ある場合、テーブルを全て走査するよりも、インデックスを使用しようとします。
    • もし LIMIT # を ORDER BY と共に使用するなら, MySQL は 最初の # 行を見つけたらすぐに、全テーブルのソートは行わずに、 ソートを終わらせます。
    • LIMIT # を DISTINCT と共に使用するなら, MySQL は # 個の一意なレコードを見つけた時点で終わります。
    • In some cases a GROUP BY can be resolved by reading the key in order (or do a sort on the key) and then calculate summaries until the key value changes. In this case LIMIT # will not calculate any unnecessary GROUP BYs.
    • MySQL は、最初の # 行をクライアントに送った後すぐに、 クエリを中断します。 (if you are not using SQL_CALC_FOUND_ROWS).
    • LIMIT 0 は常に素早く空の結果を返します。 これはクエリのチェックや結果として得られるフィールドの型を得るために利用できます。
    • 一時テーブルの大きさは、クエリを解決するためにどれぐらいのスペースがいるかを 計算するのに、LIMIT # を使用します。

    5.2.9 INSERT クエリの速度

    レコードを挿入する時間はおおよそ次からなります:

    • Connect: (3)
    • Sending query to server: (2)
    • Parsing query: (2)
    • Inserting record: (1 x size of record)
    • Inserting indexes: (1 x number of indexes)
    • Close: (1)

    ここで (数字) は比例時間です。これは、テーブルのオープンにかかる初期オーバーヘッ ド(これは同時に動作する各クエリ毎に1回行なわれます)は考慮されていません。

    テーブルのサイズはインデックスの挿入を log N で遅くします (B-tree)。

    INSERT を速くするいくつかの方法：

    • もし同じクライアントから多くのレコードを同時にインサートするなら、 複数の値が書ける INSERT 文を使用します。 これは個々に INSERT 文 を発行する場合に比べて、とても速くなります。 If you are adding data to non-empty table, you may tune up bulk_insert_buffer_size variable to make it even faster. 「4.5.6.4 SHOW VARIABLES」節参照.
    • もし違うクライアントから多くのレコードを同時にインサートするなら、 INSERT DELAYED 文の使用で、より速くなるでしょう。 「6.4.3 INSERT 構文」節参照.
    • MyISAM では、複数の SELECT が走っているテーブルに対して、 同時に、レコードを挿入できます。 ただしそのテーブルに対して レコードの削除がない場合に。
    • テキストファイルからテーブルにデータをいれる場合は、 LOAD DATA INFILE を 使用します。 これはたくさんの INSERT 文の発行に比べて通常 20倍 程度 速くなります 「6.4.9 LOAD DATA INFILE 構文」節参照.
    • テーブルが多くのインデックスを持っている場合、ある方法で、 LOAD DATA INFILE の実行を速くすることが可能です。 以下の手順で行います：
      1. Optionally create the table with CREATE TABLE. For example, using mysql or Perl-DBI.
      2. FLUSH TABLES の実行。 あるいは mysqladmin flush-tables コマンドの実行。
      3. myisamchk --keys-used=0 -rq /path/to/db/tbl_name の使用。 これは指定されたテーブルから全てのインデックスを削除します。
      4. そのテーブルに LOAD DATA INFILE を使用してデータを入れます. これはいかなるインデックスも更新しないでしょうし、そのため、速くもなるでしょう。
      5. If you are going to only read the table in the future, run myisampack on it to make it smaller. 「7.1.2.3 圧縮テーブルの特徴」節参照.
      6. myisamchk -r -q /path/to/db/tbl_name でインデックスを再構築. これは disk に書き込む前にインデックスをメモリに作成します。 これは多くのディスクシークを避けることが出来るのでとても速くなります。 でき上がったインデックスツリーは、バランスのよいものになります。
      7. FLUSH TABLES の実行。 あるいは mysqladmin flush-tables コマンドの実行。
      この手順は、将来の MySQL の LOAD DATA INFILE に組み込むかもしれません。
    • Note that LOAD DATA INFILE also does the above optimization if you insert into an empty table; the main difference with the above procedure is that you can let myisamchk allocate much more temporary memory for the index creation that you may want MySQL to allocate for every index recreation. Since MySQL 4.0 you can also use ALTER TABLE tbl_name DISABLE KEYS instead of myisamchk --keys-used=0 -rq /path/to/db/tbl_name and ALTER TABLE tbl_name ENABLE KEYS instead of myisamchk -r -q /path/to/db/tbl_name. This way you can also skip FLUSH TABLES steps.
    • You can speed up insertions that is done over multiple statements by locking your tables: 
      mysql> LOCK TABLES a WRITE;
mysql> INSERT INTO a VALUES (1,23),(2,34),(4,33);
mysql> INSERT INTO a VALUES (8,26),(6,29);
mysql> UNLOCK TABLES;
      主な速度差は、全ての INSERT 構文でインデックスバッファが一度だけディスク にフラッシュされることです。通常は INSERT 構文があるのと同じくらい多くの インデックスバッファフラッシュがあります。単一構文の全てのレコードは、ロック なしで挿入できます。 For transactional tables, you should use BEGIN/COMMIT instead of LOCK TABLES to get a speedup. ロックも複数接続テストの合計時間を低くしますが、いくつかのスレッドの最大 待ち時間は上がります(ロックを待っているから)。 例えば: 
      thread 1 does 1000 inserts
thread 2, 3, and 4 does 1 insert
thread 5 does 1000 inserts
      ロックを使用しない場合、2, 3 そして 4 は 1 と 5 の前に終ります。ロックを 使用する場合、2,3,4 は 1 や 5 の前に終わることはおそらくありませんが、合 計時間は約 40 % 速くなります。 INSERT, UPDATE , DELETE は、 MySQL ではとても速い ので、 1 行で約 5 つ以上、値を 挿入・更新 をする操作に対して、 ロックを追加すれば、全般的により良い性能が得られます。 とても多い insert を行なう場合、 他のスレッドにそのロックしたテーブルへのアクセスを与えるために 、 だいたい 1000 レコードごとに一度、UNLOCK TABLES した後に LOCK TABLES を行います。 これでもまだ良い性能が得られます。 もちろん LOAD DATA INFILE はとても速いです。

    LOAD DATA INFILE と INSERT を共に速くするためには、 キーバッファを増やします。 「5.5.2 サーバーパラメーターのチューニング」節参照.

    5.2.10 UPDATE クエリの速度

    UPDATE クエリは SELECT クエリのように最適化されますが、 書き込みのオーバーヘッドが加わります。 書き込み速度は、更新されるデータの大きさ、更新されるインデックス数に 依ります。 変更されないインデックスは更新されません。

    Also, another way to get fast updates is to delay updates and then do many updates in a row later. Doing many updates in a row is much quicker than doing one at a time if you lock the table.

    Note that, with dynamic record format, updating a record to a longer total length may split the record. So if you do this often, it is very important to OPTIMIZE TABLE sometimes. 「4.5.1 OPTIMIZE TABLE 構文」節参照.

    5.2.11 DELETE クエリの速度

    If you want to delete all rows in the table, you should use TRUNCATE TABLE table_name. 「6.4.7 TRUNCATE 構文」節参照.

    1レコードを削除する時間は、ちょうどインデックスの数に比例します。 より速くレコードを削除したいなら、インデックス・キャッシュを 増やします。 「5.5.2 サーバーパラメーターのチューニング」節参照.

    5.2.12 最適化に関するその他の助言

    Unsorted tips for faster systems:

    • コネクションオーバーヘッドを避けるために、データベースに対して、 逐次コネクションを落とさないように、常に接続を保ちます。 If you can't use persistent connections and you are doing a lot of new connections to the database, you may want to change the value of the thread_cache_size variable. 「5.5.2 サーバーパラメーターのチューニング」節参照.
    • あなたのクエリがテーブルのインデックスを使用しているか、いつもチェックします。 MySQL では EXPLAIN コマンドでこれが行えれます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.
    • MyISAM では、大量に変更されるようなテーブルに対して、 複雑な SELECT クエリを避けるように試みます。 これはテーブル・ロックの問題を避けるためです。
    • 新しい MyISAM テーブルでは、あるテーブルにレコードが挿入(削除は無しで) されている最中に、同時に、同じテーブルからデータを読むことが可能です。 これがあなたにとって重要項目であるなら、 レコードの削除の必要のない方法や、多くのレコードを削除した後に OPTIMIZE TABLE を実行することを、考慮すべきです。
    • Use ALTER TABLE ... ORDER BY expr1,expr2... if you mostly retrieve rows in expr1,expr2... order. By using this option after big changes to the table, you may be able to get higher performance.
    • In some cases it may make sense to introduce a column that is 'hashed' based on information from other columns. If this column is short and reasonably unique it may be much faster than a big index on many columns. In MySQL it's very easy to use this extra column: SELECT * FROM table_name WHERE hash=MD5(CONCAT(col1,col2)) AND col_1='constant' AND col_2='constant'
    • 多くの変更がなされるテーブルに対しては、全ての VARCHAR や BLOB フィールドを避けるように試みるべきです。 You will get dynamic row length as soon as you are using a single VARCHAR or BLOB column. 「7 MySQL テーブル型」節参照.
    • 通常、あるテーブルを違うテーブルに分けることは、レコードが大きくなる ために役立ちません。 レコードにアクセスする際、そのレコードの最初のバイトを見つけるための ディスク・シークが、一番かかります。 After finding the data most new disks can read the whole row fast enough for most applications. The only cases where it really matters to split up a table is if it's a dynamic row size table (see above) that you can change to a fixed row size, or if you very often need to scan the table and don't need most of the columns. 「7 MySQL テーブル型」節参照.
    • もし、多くのレコードからの情報を元にした計算(あるもののカウントとか)を しょっちゅう行う必要があるなら、新しいテーブルを用意し、逐次カウンターを 更新した方が多分良いでしょう。 UPDATE table SET count=count+1 WHERE index_column=constant の更新は とても速いです！ これは、MySQL MyISAM テーブルや ISAM テーブルのような テーブル・ロッキング(multiple readers / single writers)をもつ データベースを使う上で、本当に重要なことです。 This will also give better performance with most databases, as the row locking manager in this case will have less to do.
    • もしたくさんの大きなテーブルから統計を収集する必要があるなら、 全テーブルを走査する代わりに、サマリーテーブルを使用します。 Maintaining the summaries should be much faster than trying to do statistics 'live'. It's much faster to regenerate new summary tables from the logs when things change (depending on business decisions) than to have to change the running application!
    • If possible, one should classify reports as 'live' or 'statistical', where data needed for statistical reports are only generated based on summary tables that are generated from the actual data.
    • フィールドにはデフォルト値があるという事を利用して下さい。 値がデフォルトとは違う場合に限り、値を挿入します。 これは MySQL が必要とする分析を少なくし、インサートの速度が向上します。
    • ある場合では、BLOB にデータをパックして保存するのが便利です。 この場合、BLOB に入れた値を パック・アンパック するためのコードを あなたのアプリケーションに組み込まなくてはなりません。 しかしこれは、多くのアクセスを抑制するでしょう。 これは、静的(固定長)テーブル構造に適しないデータを持っている場合に 実用になります。
    • 通常、あなたは全てのデータを冗長の無いように(データベース理論で 第３正規形 , 3rd Normal Form , 3NF と呼ばれる) しようとするかもしれませんが、しかし、よりスピードを求める場合は、 重複やサマリーテーブルの作成をおそれてはいけません。
    • ストアド・プロシージャ や UDF (ユーザー定義関数) はよりパフォーマンスを得る ためにはよい方法かもしれません。 In this case you should, however, always have a way to do this some other (slower) way if you use some database that doesn't support this.
    • You can always gain something by caching queries/answers in your application and trying to do many inserts/updates at the same time. If your database supports lock tables (like MySQL and Oracle), this should help to ensure that the index cache is only flushed once after all updates.
    • データをすぐには書く必要がないとき、INSERT /*! DELAYED */ を使用します。 これは、一回のディスクへの書き込みで、多くのレコードがかかれるので、 速くなります。
    • SELECT がより重要な場合、INSERT /*! LOW_PRIORITY */ を使用します。
    • キューを無視して SELECT を優先的に行いたいときは SELECT /*! HIGH_PRIORITY */ を使用します。 これは、たとえ誰かが書き込みを待っていたとしても、その SELECT は 実行されます。
    • 複数行 INSERT 文の使用。 これは多くのレコードを一つの SQL コマンドで 挿入することが出来ます。 (多くの SQL サーバーがこれをサポートしています)
    • 大きなデータの読み込みには LOAD DATA INFILE を使用します。 This is faster than normal inserts and will be even faster when myisamchk is integrated in mysqld.
    • 一意の値を作るために、 AUTO_INCREMENT を使用します。
    • 動的テーブルフォーマットの使用時には、フラグメンテーションを避けるために、 OPTIMIZE TABLE を時々使用します。 「4.5.1 OPTIMIZE TABLE 構文」節参照.
    • 可能ならば HEAP テーブルをスピードアップのために使用します. 「7 MySQL テーブル型」節参照.
    • 通常の Web サーバーの設定ならば、イメージはファイルに保存すべきです。 データベースには、それらファイルの参照(パスとか)のみを入れます。 この主な理由は、通常の Web サーバーはデータベースよりもコンテンツを よりよくキャッシュしてくれるからです。 それでファイルを使用するなら、 速いシステムをより簡単に得ることができます。
    • 重要でないデータで、よくアクセスされる物は、メモリテーブルにいれます。 (like information about the last shown banner for users that don't have cookies).
    • Columns with identical information in different tables should be declared identical and have identical names. Before Version 3.23 you got slow joins otherwise. 名前は単純にしてください（customer テーブルでは customer_name の かわりに name を使うとか）。 他の SQL サーバーへの移植を考慮するなら、 名前は 18 文字より短くすべきです。
    • もし本当にハイ・スピードが必要なら、SQL サーバーがサポートしている物とは 違う、ローレベルのデータ保存のインターフェースに注目すべきです。 例えば、 MySQL MyISAM を直接アクセスすることは、 SQL インターフェースを介してアクセスするよりも、2〜5倍速くなるでしょう。 これを可能にするには、そのデータは、アプリケーションと同じマシン上になくてはなら ず、通常、一つのプロセスだけでアクセスされるべきです。 (なぜなら、外部ファイルロックは、とても遅いから)。 上の問題は、MySQL サーバー内の MyISAM のローレベルのコマンドの 導入で解決できるでしょう。 (これはよりよいパフォーマンスを得ることの出来る、 簡単な方法の一つです)。 By carefully designing the database interface, it should be quite easy to support this types of optimization.
    • 多くの場合、データベースからデータをアクセスする方が(接続を維持していれば)、 テキストファイルからデータをアクセスするよりも速いです。 なぜなら、 データベースはテキストファイルよりもコンパクトになり（数値データの場合）、 このため、ディスクアクセスが少なくなるからです。 また、行や項目を見つけるために、テキストファイルを解析する必要も省けます。
    • レプリケーションもスピードアップに使用できるでしょう。 「4.10 MySQL のレプリケーション (3.23.15以上)」節参照.
    • DELAY_KEY_WRITE=1 が定義されたテーブルは、インデックスの更新が速くなります。 これはそのインデックス・ファイルが閉じられるまでディスクに記録されないからです。 したがって、なにかが途中で mysqld をキルしてもテーブルが大丈夫なようにす るため、mysqld を起動する前には、myisamchk をそれらのテーブルに 対して実行すべきです。 As the key information can always be generated from the data, you should not lose anything by using DELAY_KEY_WRITE.

    5.3 Locking Issues

    5.3.1 MySQL はどのようにテーブルをロックするか

    付録に、異なるロックする方法に関する議論があります。 「E.4 Locking methods」節参照.

    MySQL の全てのロックはデッドロックフリーです。(except for InnoDB and BDB type tables.) これは、常にクエ リ開始時に一度ロックを必要とする全てを要求し、常に同じ順でテーブルをロッ クすることで管理されます。

    InnoDB type tables automatically acquire their row locks and BDB type tables their page locks during the processing of SQL statements, not at the start of the transaction.

    MySQL が使用する WRITE ロックは次のように働きます:

    • テーブル上にロックがない場合 write ロックを置きます。
    • そうでなければ write ロックキューにロックを置きます。

    MySQL の READ ロックは次のように動きます:

    • テーブル上に write ロックがない場合 read ロックを置きます。
    • そうでなければ read ロックキューにロックを置きます。

    ロックが解放されたとき、最初に write ロックキュー内のスレッドに、その後 read ロックキュー内のスレッドにロックを与えます。

    これは、同じテーブルで多くの更新をする場合、SELECT 構文は update がなくなるまで待たされることを意味します。

    同じテーブルで多くの INSERT と多くの SELECT を行う場合、これを解決 するには、他のテーブルに行を挿入して、たまに、その一時テーブルから全ての レコードをもう一方のテーブルに update します。

    これは次のコードで行えます: 

    mysql> LOCK TABLES real_table WRITE, insert_table WRITE;
mysql> INSERT INTO real_table SELECT * FROM insert_table;
mysql> TRUNCATE TABLE insert_table;
mysql> UNLOCK TABLES;

    特定の場合での検索を優先的に行いたい場合、 LOW_PRIORITY オプションと共に INSERT 、 UPDATE 、 DELETE 構文、または HIGH_PRIORITY オプションと共に SELECT 構文を使用できます。 また、同様の動作を得るために、 --low-priority-updates オプション と共に mysqld を開始することができます。

    SQL_BUFFER_RESULT の使用はさらにテーブル・ロックをより短くするために有効かもしれません。 「6.4.1 SELECT 構文」節参照.

    一つのキューだけを使用するように `mysys/thr_lock.c' 内のロックコードを変更 することもできます。この場合、いくつかのアプリケーションのために、 write ロックは read ロックと同じ優先順位にします。

    5.3.2 テーブル・ロッキングの問題

    MySQL のテーブル・ロッキングのコードはデッドロック・フリーです。

    MySQL はとても速いロックスピードを得るために、 (レコードのロックやフィールドのロックの代わりに) テーブルのロックを使用します。 (except InnoDB and BDB tables) 大きなテーブルには、 テーブルのロックはレコードのロックよりはるかに良いですが、 いくつかの落とし穴があります。

    BDB と InnoDB のテーブルでは、 LOCK TABLES を使用して 明示的にテーブルをロックするか、 ALTER TABLE のようなテーブル中のすべて のレコードを修正するコマンドを実行した場合にのみ、MySQLはテーブル・ロッキングを使用 します。これらのテーブル・タイプについては、 LOCK TABLES を全く使用 しないことを推奨します。 because InnoDB uses automatic row level locking and BDB uses page level locking to ensure transaction isolation.

    MySQL バージョン 3.23.7 以上では、 あるスレッドが MyISAM テーブルを読んでいる最中に、 同じテーブルにレコードを挿入する事ができます。 現在、これは挿入が行われる時に、テーブルのレコードを削除した後にホールがない場合にのみ 動作することに注意してください。すべてのホールが新しいデータで満たされた時に、 自動的に同時挿入が再び可能になります。

    テーブルのロックはたくさんのスレッドが同時にあるテーブルから読み出すのを可能にし ますが、もしあるスレッドがあるテーブルに対し書込み要求を出す場合、 それはまず最初に排他的なアクセスを得なければなりません. その更新の間、更新が完了するまで、この特定のテーブルにアクセスしようとする 他の全てのスレッドが待たされることになります。

    通常データベースの更新は SELECT よりも重要とされるため、 テーブルを更新する全てのスレッドが、テーブルから情報を検索するスレッドよりも 高い優先順位を持ちます。 これは ある特定のテーブルに対して、多くの重いクエリが発 行された場合に、 更新が不完全に終わらないことを確実にするためです。 (これは、 LOW_PRIORITY と共に更新を行うステートメントを用いるか、 HIGH_PRIORITY と共に SELECT ステートメントを用いることにより 変更が可能です。)

    MySQL バージョン 3.23.7 から、max_write_lock_count 変数が使用で きます。 これは、一つのテーブルに対して、指定された回数だけ INSERT が行われた後に、 SELECT を発行するようにします。

    テーブルロッキングは以下の場合にはあまり良くありません：

    • あるクライアントが実行に長い時間のかかる SELECT を発行。
    • その後に、他のクライアントが、使用されているテーブルに対し UPDATE を発行； このクライアントは先の SELECT が完了するまで待ちます
    • さらに他のクライアントが同じテーブルに対して SELECT 構文を発行； UPDATE は SELECT よりも高い優先度を持つので、 この SELECT は先の UPDATE が完了するまで待ちます。 これは一番最初の SELECT が 終了するまで待たされます！
    • スレッドが full disk のような待機状態になっている場合、 問題のテーブルにアクセスを行おうとした全てのスレッドもまた、 より多くのディスク・スペースが利用可能になるまで待機状態に入ります。

    この問題のいくつかの可能な解決は以下の通りです：

    • SELECT 構文を速く実行できるように試みます； これを行うにあたり、 いくつかのサマリーテーブルを作成しなければならないかもしれません.
    • mysqld を --low-priority-updates オプションで起動。 これは全てのあるテーブルを更新する構文に対して、 SELECT 構文よりも 低い優先度を与えます。 この場合、前述のシナリオ中の最後の SELECT 構文は INSERT 構文が完了する前に実行されます。
    • LOW_PRIORITY 属性指定を用いて、 INSERT,UPDATE,DELETE 構文に低い優先度を与えることも出来ます。
    • ある程度の数の WRITE ロックの後に READ ロックを与えるために、 max_write_lock_count を低い値にして mysqld を開始します。
    • SQL コマンドの SET LOW_PRIORITY_UPDATES=1 (ver. 4.0.3 未満では SET SQL_LOW_PRIORITY_UPDATES=1 ) を使用して、 ある特定のスレッドからの全ての更新を、低い優先度に指定する事ができます。 「5.5.6 SET 構文」節参照.
    • HIGH_PRIORITY 属性を用いて、特定の SELECT がとても重要であると 指定することが可能です。. 「6.4.1 SELECT 構文」節参照.
    • もし INSERT と SELECT をあわせて使用した場合に問題が起きた場合、 新しい MyISAM テーブルに切り替えます。 これは SELECT と INSERT を同時に行えます。
    • もし INSERT と SELECT 構文を主に混在させるのなら、 INSERT の DELAYED 属性指定はこの問題を解決させるでしょう。 「6.4.3 INSERT 構文」節参照.
    • もし SELECT と DELETE で問題があるなら、 DELETE の LIMIT オプションが助けになるでしょう。 「6.4.6 DELETE 構文」節参照.

    5.4 Optimizing Database Structure

    5.4.1 Design Choices

    MySQL は、レコードのデータとインデックスを別のファイルに保存します。 他の多くの(ほとんど全て)データベースでは、同じファイルにデータとインデックスを 混在させて保存します。 我々は、最近のシステムには、MySQL の選択の方が 良いと信じています。

    Another way to store the row data is to keep the information for each column in a separate area (examples are SDBM and Focus). This will cause a performance hit for every query that accesses more than one column. Because this degenerates so quickly when more than one column is accessed, we believe that this model is not good for general purpose databases.

    The more common case is that the index and data are stored together (like in Oracle/Sybase et al). In this case you will find the row information at the leaf page of the index. The good thing with this layout is that it, in many cases, depending on how well the index is cached, saves a disk read. The bad things with this layout are:

    • Table scanning is much slower because you have to read through the indexes to get at the data.
    • You can't use only the index table to retrieve data for a query.
    • You lose a lot of space, as you must duplicate indexes from the nodes (as you can't store the row in the nodes).
    • Deletes will degenerate the table over time (as indexes in nodes are usually not updated on delete).
    • It's harder to cache ONLY the index data.

    5.4.2 可能な限りデータを小さくする

    One of the most basic optimization is to get your data (and indexes) to take as little space on the disk (and in memory) as possible. This can give huge improvements because disk reads are faster and normally less main memory will be used. Indexing also takes less resources if done on smaller columns.

    MySQL supports a lot of different table types and row formats. Choosing the right table format may give you a big performance gain. 「7 MySQL テーブル型」節参照.

    以下に挙げるテクニックを使用すれば、テーブルでのパフォーマンスの向上、 保存領域の縮小化が可能でしょう：

    • 可能ならば、一番小さな型を使用します。 MySQL は ディスクとメモリーを節約する多くの型を持っています。
    • より小さな整数型を可能ならば使用します。 例えば、 MEDIUMINT は INT より良いでしょう。
    • 可能ならフィールドを NOT NULL に定義してください。これは全てをより速くし、 各フィールド毎に1ビットを節約します。 Note that if you really need NULL in your application you should definitely use it. Just avoid having it on all columns by default.
    • 可変長のフィールド (VARCHAR, TEXT, BLOB) を持たない場合は、 固定サイズレコード形式が使用されます。 これはかなり速いです。しかしあいにくいくらかの領域を浪費します。 「7.1.2 MyISAM Table Formats」節参照.
    • それぞれのテーブルは可能な限り短いプライマリ・インデックスを持つべきです。 これは１レコードを一意にし、効率的にします。
    • それぞれのテーブルについて、どのテーブルの形式を使用するかを 決めます。 「7 MySQL テーブル型」節参照.
    • 本当に必要な物にだけインデックスを作成します。 インデックスは検索には良いですが、より速く保存したい場合には良くありません。 もしテーブルをフィールドの組み合わせでサーチすることがほとんどであれば、 それらにインデックスを作成します。 最初のインデックスの部分は、もっとも 使用されるフィールドにすべきです。 If you are ALWAYS using many columns, you should use the column with more duplicates first to get better compression of the index.
    • もしインデックスが頭からの何文字かで一意性を持っているなら、この部分にだけ インデックスを張る方が良いでしょう。 MySQL は文字列フィールドの 一部分に対してのインデックスをサポートします。 短いインデックスは、ディスクスペースを節約するだけでなく、 インデックスのキャッシュに収まりやすくなることにより、ディスク・シークも少 なくなるので、速くなります。 「5.5.2 サーバーパラメーターのチューニング」節参照.
    • いくつかの状況下で、とてもよく走査されるテーブルを２つに分割することは、 利益になることがあります。 This is especially true if it is a dynamic format table and it is possible to use a smaller static format table that can be used to find the relevant rows when scanning the table.

    5.4.3 MySQL はどのようにインデックスを使用するか？

    Indexes are used to find rows with a specific value of one column fast. インデックスがない場合、MySQL は、そのレコードが見つかるまで、 最初のレコードからテーブルをなめていきます。 大きなテーブルでは多くの 手間がかかります。 もし問い合わせの中にインデックスを持ったフィールドが ある場合、MySQL は全てのデータをみることなく、データの途中の位置を速く 得ることができます。 もしあるテーブルが1000レコード持っていたとすると、 順番に頭からなめていくことに比べて、これは少なくとも100倍速いことに なります。 Note that if you need to access almost all 1000 rows it is faster to read sequentially because we then avoid disk seeks.

    全ての MySQL インデックス, PRIMARY, UNIQUE そして INDEX() は B tree に格納されます。 文字列は自動的に始めと終りの空白が圧縮されます。 「6.5.7 CREATE INDEX 構文」節参照.

    Indexes are used to:

    • WHERE節にマッチした行の素早い検索
    • join を実行したときの他のテーブルからの行の検索
    • Find the MAX() or MIN() value for a specific indexed column. This is optimized by a preprocessor that checks if you are using WHERE key_part_# = constant on all key parts < N. In this case MySQL will do a single key lookup and replace the MIN() expression with a constant. If all expressions are replaced with constants, the query will return at once: 
      SELECT MIN(key_part2),MAX(key_part2) FROM table_name where key_part1=10
    • テーブルをソートかグループ化する場合で、ソート(グループ化)が一番左(接頭部)の キーを使用して行われる場合(例えば ORDER BY key_part_1,key_part_2 )。 もし DESC 指定があれば、全てのキーは逆順に読まれます。 「5.2.7 How MySQL Optimises ORDER BY」節参照.
    • データファイルを参照することなく値を検索する場合。 もし使用する全てのフィールドが数値でかつ、一番左から(接頭部から)キーを形成する場 合、 値はインデックスツリーから検索され、これはとても速くなります。 
      SELECT key_part3 FROM table_name WHERE key_part1=1

    以下のような SELECT 文を発行したとします： 

    mysql> SELECT * FROM tbl_name WHERE col1=val1 AND col2=val2;

    もし col1 と col2 に複数フィールドインデックスが定義されている場合、 すぐに思ったとおりの結果が得られます。 If separate single-column indexes exist on col1 and col2, the optimizer tries to find the most restrictive index by deciding which index will find fewer rows and using that index to fetch the rows.

    もしテーブルが複数フィールドインデックスを持つなら、インデックスの接頭部一番左の 部分がレコードを見つけるための最適化に使用されます。例えば、3つのフィールド (col1,col2,col3) に対して一つのインデックスを持っていたとします。 すると、これは (col1), (col1,col2) , (col1,col2,col3) でインデックスがサーチされます。

    もし一番左に指定しているフィールドがインデックスを作成していないなら、 MySQL は部分的なインデックスを使用しません。

    以下のような SELECT 文を発行したとします： 

    mysql> SELECT * FROM tbl_name WHERE col1=val1;
mysql> SELECT * FROM tbl_name WHERE col2=val2;
mysql> SELECT * FROM tbl_name WHERE col2=val2 AND col3=val3;

    もしインデックスが (col1,col2,col3) にあるならば、 上に示した最初のクエリだけがインデックスを使用します。二番目三番目のクエリは インデックスを持つフィールドを発動しますが、 (col2) と (col2,col3) は、(col1,col2,col3) の 接頭部一番左に指定されていません。

    MySQL は、もし LIKE がワイルドカードから始まっていなくて、 ある種固定された文字で始まっているなら、 LIKE の評価にインデックスを使用します。 例えば、以下の SELECT 文はインデックスを使用します: 

    mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Patrick%";
mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Pat%_ck%";

    一つ目の文は、"Patrick" <= key_col < "Patricl" となるレコードだけ、考慮さ れます。 二つ目の文は、"Pat" <= key_col < "Pau" となるレコードだけ、考慮されます。

    以下の SELECT 文はインデックスを使用しません: 

    mysql> SELECT * FROM tbl_name WHERE key_col LIKE "%Patrick%";
mysql> SELECT * FROM tbl_name WHERE key_col LIKE other_col;

    最初の文は、LIKE がワイルドカード文字で始まっています。 二つ目の文は、LIKE が定数ではありません。

    MySQL 4.0 does another optimisation on LIKE. If you use ... LIKE "%string%" and string is longer than 3 characters, MySQL will use the Turbo Boyer-Moore algorithm to initialise the pattern for the string and then use this pattern to perform the search quicker.

    Searching using column_name IS NULL will use indexes if column_name is an index.

    MySQL は通常、一番少ないレコード数を見つけるインデックスを使用します。 インデックスは次に示す演算子を用いて比較できるフィールドに対して使用されます： =, >, >=, <, <=, BETWEEN そして 'something%' の様に頭にワイルドカードがない LIKE。

    WHERE 節内の全ての AND にかからないインデックスは、 全くクエリの最適化に使用されません。 In other words: To be able to use an index, a prefix of the index must be used in every AND group.

    以下の WHERE 節はインデックスを使用します： 

    ... WHERE index_part1=1 AND index_part2=2 AND other_column=3
... WHERE index=1 OR A=10 AND index=2      /* index = 1 OR index = 2 */
... WHERE index_part1='hello' AND index_part_3=5
          /* optimized like "index_part1='hello'" */
... WHERE index1=1 and index2=2 or index1=3 and index3=3;
          /* Can use index on index1 but not on index2 or index 3 */

    以下の WHERE 節はインデックスを使用しません： 

    ... WHERE index_part2=1 AND index_part3=2  /* index_part_1 is not used */
... WHERE index=1 OR A=10                  /* Index is not used in
                                                        both AND parts */
... WHERE index_part1=1 OR index_part2=10  /* No index spans all rows  */

    Note that in some cases MySQL will not use an index, even if one would be available. Some of the cases where this happens are:

    • If the use of the index would require MySQL to access more than 30% of the rows in the table. (In this case a table scan is probably much faster, as this will require us to do much fewer seeks.) Note that if such a query uses LIMIT to only retrieve part of the rows, MySQL will use an index anyway, as it can much more quickly find the few rows to return in the result.

    5.4.4 Column Indexes

    MySQL の全てのフィールドはインデックスを持つことができます。 適切なフィールドでのインデックスの使用は、SELECT の 性能を向上する最良の方法です。

    キーの最大数と最大インデックス長は storage engine 毎に定義されます。 「7 MySQL テーブル型」節参照。すべてのテーブルハンドラで少なくとも 16 個のキーと少な くとも合計 256 バイトのインデックス長を持つことができます。

    CHAR と VARCHAR フィールドには接頭部にインデックスを持つことが できます。フィールド全体をインデックス化するより、 これははるかに早く、少ないディスク容量でできます。

    CREATE TABLE 構文でフィールドにインデックスを作るには、 以下のようにします： 

    KEY index_name (col_name(length))

    以下の例は name フィールドの最初の10文字にインデックスを創り出します: 

    mysql> CREATE TABLE test (
    ->        name CHAR(200) NOT NULL,
    ->        KEY index_name (name(10)));

    BLOB と TEXT フィールドでは、そのフィールドの頭の部分に インデックスを張らなくてはなりません。 フィールドの全体にインデックスは張れません。

    MySQL バージョン 3.23.23 以降では、特殊な FULLTEXT イン デックスを生成することもできます。これは全文検索に使用されます。 MyISAM テーブル型だけが FULLTEXT インデックスをサポートしま す。これは CHAR, VARCHAR と TEXT フィールドだけに生成できます。イ ンデックスは常にフィールド全体に対して行なわれ、部分インデックスはサポート されません。詳細は 「6.8 MySQL Full-text Search」節.

    5.4.5 Multiple-Column Indexes

    MySQL は異なるフィールドのセットに一つのインデックスを持つことができます。 インデックスは最大15個のコラムまで許されます。 (CHAR と VARCHAR フィールドの接頭部をインデックスとして使用できます)

    複数フィールドインデックスは、 ソートされた配列(インデックス化されたフィールドの値が結合されている配列) を扱うことができます。

    インデックス化されたコラムに対して、既知の値を WHERE 節で指定した時、 たとえ他のフィールドの値を指定しなくとも、 MySQL は複数フィールドインデックスを使用します。

    以下のテーブルがあると仮定してください： 

    mysql> CREATE TABLE test (
    ->       id INT NOT NULL,
    ->       last_name CHAR(30) NOT NULL,
    ->       first_name CHAR(30) NOT NULL,
    ->       PRIMARY KEY (id),
    ->       INDEX name (last_name,first_name));

    name インデックスは、last_name と first_name にまたがるイン デックスです。 このインデックスは、last_name に対するクエリや、 name インデックスは以下のクエリで使われます： 

    mysql> SELECT * FROM test WHERE last_name="Widenius";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND first_name="Michael";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND (first_name="Michael" OR first_name="Monty");

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND first_name >="M" AND first_name < "N";

    しかし name インデックスは以下のクエリでは使用されません: 

    mysql> SELECT * FROM test WHERE first_name="Michael";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    OR first_name="Michael";

    MySQL がクエリの性能を上げるためにどうインデックスを使用しているか、 より詳しい情報はこちら： 「5.4.3 MySQL はどのようにインデックスを使用するか？」節.

    5.4.6 何故そんなに多くのテーブルをオープンするのか？

    mysqladmin status を実行すると、次のようなものが得られます: 

    Uptime: 426 Running threads: 1 Questions: 11082 Reloads: 1 Open tables: 12

    確かにたった6個しかテーブルがないのに、このような結果が出るので少々戸惑われるか もしれません。

    MySQL はマルチスレッドなので、同じテーブルで一度に多くのクエリを持て ます。 同じファイル上では2つスレッドはそれぞれ別の異なる状態を持つという 問題を最小化するため、テーブルは同時に動作する各スレッドにより個々に オープンされます。 これは少しメモリを食いますが、パフォーマンスは良くなります。 ISAM と MyISAM テーブルでは、データファイルのために 一つのファイル記述子を使用します。 インデックスファイル記述子は全てのスレッド間で共有されます。

    You can read more about this topic in the next section. 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節参照.

    5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？

    table_cache , max_connections , max_tmp_tables は サーバーが開いた状態にしておく事が出来るファイルの最大数に影響します。 もしこれらの変数のうちの一つ、あるいは複数を増加させるなら、 あなたのオペレーティング・システムの、1 プロセスあたりに開かれる ファイル・デスクリプタ の最大値を増やすことになるかもしれません。 多くのシステムではこの制限を増やすことが可能です。 これをどうやって行うかは、あなたの使用している OS のドキュメントを見てください。 制限値の変更方法は、システムによってまちまちだからです。

    table_cache は max_connections に関連します。 例えば 200 のコネクションを同時に開けるなら、少なくとも 200 * n の テーブル・キャッシュが必要です。 ここで n は join におけるテーブルの 最大数です。 You also need to reserve some extra file descriptors for temporary tables and files.

    Make sure that your operating system can handle the number of open file descriptors implied by the table_cache setting. If table_cache is set too high, MySQL may run out of file descriptors and refuse connections, fail to perform queries, and be very unreliable. You also have to take into account that the MyISAM storage engine needs two file descriptors for each unique open table. You can in increase the number of file descriptors available for MySQL with the --open-files-limit=# startup option. 「A.2.16 File Not Found」節参照.

    オープンテーブルのキャッシュは最大で table_cache まで大きくなります(デ フォルトは 64, mysqld のオプション -O table_cache=# で変更可能)。 Note that in MySQL may temporarly open even more tables to be able to execute queries.

    A not used table is closed and removed from the table cache under the following circumstances:

    • When the cache is full and a thread tries to open a table that is not in the cache.
    • When the cache contains more than table_cache entries and a thread is no longer using a table.
    • When someone executes mysqladmin refresh or mysqladmin flush-tables.
    • When someone executes a FLUSH TABLES statement.

    キャッシュがいっぱいになった場合、サーバーは以下の処置を取って キャッシュを使用できるように配置します：

    • 現在使われていないテーブルが解放されます。もっとも使用されていないテーブルからか ら順に。
    • もしキャッシュが一杯でテーブルを解放することが出来ず、さらに新しいテーブルの オープン要求がある場合、キャッシュは一時的な拡張を必要とします。
    • もしそのキャッシュが一時拡張に配置されていて、かつ、テーブルが使用状態から 未使用状態に移行した場合、そのテーブルは閉じられ、キャッシュから解放されます。

    テーブルは各同時アクセスに (再び) オープンされます。これは、同じテーブルで2つの スレッドが実行されている場合、または同じクエリで(AS で)テーブルを2回 アクセスする場合、テーブルは2回オープンする必要があることを意味します。 最初のテーブルのオープンは2つのファイル記述子を使用し、続くテーブルの各使用は 1つだけのファイル記述子を使用します。

    If you are opening a table with the HANDLER table_name OPEN statement, a dedicated table object is allocated for the thread. This table object is not shared by other threads an will not be closed until the thread calls HANDLER table_name CLOSE or the thread dies. 「6.4.2 HANDLER Syntax」節参照. When this happens, the table is put back in the table cache (if it isn't full).

    You can check if your table cache is too small by checking the mysqld variable Opened_tables. If this is quite big, even if you haven't done a lot of FLUSH TABLES, you should increase your table cache. 「4.5.6.3 SHOW STATUS」節参照.

    5.4.8 Drawbacks to Creating Large Numbers of Tables in the Same Database

    もしたくさんのファイルが一つのディレクトリにある場合、オープン、クローズ、 create 操作は遅くなるでしょう。 もし SELECT 文を多くのテーブルに対し 実行した場合、テーブルキャッシュが一杯ならば、このオーバーヘッドは多くなるでしょ う。 なぜなら、それぞれのテーブルにつきオープンし、クローズしなくてはならないからです。 このオーバーヘッドを緩和するには、テーブルキャッシュを大きくします。

    5.5 Optimizing the MySQL Server

    5.5.1 システム、コンパイル時、スタートパラメターのチューニング

    We start with the system level things since some of these decisions have to be made very early. In other cases a fast look at this part may suffice because it not that important for the big gains. However, it is always nice to have a feeling about how much one could gain by changing things at this level.

    使うべき OS はとても重要です！ 複数の CPU を持つマシンでは、 Solaris (なぜなら、Solaris のスレッドはとても素晴らしく動作するから)、 あるいは、Linux ( kernel 2.2 は良い SMP をサポートしているから) を 使用すべきです。 32bit マシンの Linux では、2G bytes のファイルサイズの 制限があります。 これは新しいファイルシステム (XFS/ReiserFS) のリリース時に なくなって欲しいものです。 If you have a desperate need for files bigger than 2G on Linux-intel 32 bit, you should get the LFS patch for the ext2 file system.

    Because we have not run MySQL in production on that many platforms, we advice you to test your intended platform before choosing it, if possible.

    Other tips:

    • 充分 RAM があるならば、全ての swap を外してもよいでしょう。 いくつかのシステムでは、たとえメモリーが空いていても、 swap を使用する場合があります。
    • 外部のロックを避けるため、--skip-external-locking (ver.4.0.3未満では --skip-locking) MySQL オプション を使用します。 Note that this will not impact MySQL's functionality as long as you only run one server. Just remember to take down the server (or lock relevant parts) before you run myisamchk. On some system this switch is mandatory because the external locking does not work in any case. MIT-pthread でコンパイルする時は --skip-external-locking (ver.4.0.3未満では --skip-locking) がデフォルトです。 これは全てのプラットフォームで MIT-pthread が flock() を完全にサポートし ていないためです。 It's also on default for Linux as Linux file locking are not yet safe. --skip-external-locking (ver.4.0.3未満では --skip-locking) が使用できないただ一つの状態は、 もしあなたが複数の MySQL サーバー (クライアントではない) を 同じデータに対して走らせている場合です。 You can still use LOCK TABLES/UNLOCK TABLES even if you are using --skip-external-locking (ver.4.0.3未満では --skip-locking)

    5.5.2 サーバーパラメーターのチューニング

    mysqld サーバーが使用している現在のバッファサイズを次で得ることができます: 

    shell> mysqld --help

    この結果、全ての mysqld オプションと次のようなコンフィグ可能変数のリスト を得られます。出力結果にはデフォルト値が含まれ、以下のように表示されます: 

    Possible variables for option --set-variable (-O) are:
back_log                 current value: 5
bdb_cache_size           current value: 1048540
binlog_cache_size        current value: 32768
connect_timeout          current value: 5
delayed_insert_timeout   current value: 300
delayed_insert_limit     current value: 100
delayed_queue_size       current value: 1000
flush_time               current value: 0
interactive_timeout      current value: 28800
join_buffer_size         current value: 131072
key_buffer_size          current value: 1048540
lower_case_table_names   current value: 0
long_query_time          current value: 10
max_allowed_packet       current value: 1048576
max_binlog_cache_size    current value: 4294967295
max_connections          current value: 100
max_connect_errors       current value: 10
max_delayed_threads      current value: 20
max_heap_table_size      current value: 16777216
max_join_size            current value: 4294967295
max_sort_length          current value: 1024
max_tmp_tables           current value: 32
max_write_lock_count     current value: 4294967295
myisam_sort_buffer_size  current value: 8388608
net_buffer_length        current value: 16384
net_retry_count          current value: 10
net_read_timeout         current value: 30
net_write_timeout        current value: 60
read_buffer_size         current value: 131072
record_rnd_buffer_size   current value: 131072
slow_launch_time         current value: 2
sort_buffer              current value: 2097116
table_cache              current value: 64
thread_concurrency       current value: 10
tmp_table_size           current value: 1048576
thread_stack             current value: 131072
wait_timeout             current value: 28800

    Please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own.

    もし mysqld サーバーを走らせているなら、以下のコマンドでも変数の値を見る ことができます: 

    shell> mysqladmin variables

    You can find a full description for all variables in the SHOW VARIABLES section in this manual. 「4.5.6.4 SHOW VARIABLES」節参照.

    You can also see some statistics from a running server by issuing the command SHOW STATUS. 「4.5.6.3 SHOW STATUS」節参照.

    MySQL はとてもスケーラブルなアルゴリズムを使用します。そのため 通常はとても少ないメモリで動作します。しかし MySQL に多くのメモリを 与えれば、より良い性能を得ることができます。

    When tuning a MySQL server, the two most important variables to use are key_buffer_size and table_cache. You should first feel confident that you have these right before trying to change any of the other variables.

    多くのメモリ(>=256M)と多くのテーブルを持っていて、適度のクライアント数で最大性能 を得たい場合、次のようなものを使用します: 

    shell> safe_mysqld -O key_buffer=64M -O table_cache=256 \
           -O sort_buffer=4M -O read_buffer_size=1M &

    If you have only 128M and only a few tables, but you still do a lot of sorting, you can use something like: 

    shell> safe_mysqld -O key_buffer=16M -O sort_buffer=1M

    多くの接続で少ないメモリしかない場合、次のようなものを使用します 

    shell> safe_mysqld -O key_buffer=512k -O sort_buffer=100k \
           -O read_buffer_size=100k &

    or even: 

    shell> safe_mysqld -O key_buffer=512k -O sort_buffer=16k \
           -O table_cache=32 -O read_buffer_size=8k -O net_buffer_length=1K &

    If you are doing a GROUP BY or ORDER BY on files that are much bigger than your available memory you should increase the value of record_rnd_buffer to speed up the reading of rows after the sorting is done.

    When you have installed MySQL, the `support-files' directory will contain some different `my.cnf' example files, `my-huge.cnf', `my-large.cnf', `my-medium.cnf', and `my-small.cnf', you can use as a base to optimize your system.

    もしとても多くの接続があり、mysqld が各接続に対して少ないメモリーで 動作するように設定されていれば、スワップの読み書きによるパフォーマンスの低下がお きます。 もちろん十分なメモリーがあれば、全ての接続にたいして mysqld のパフォーマ ンス良くなります。

    mysqld へのオプションを変更する場合、そのサーバのインスタンスにだけに 有効であることに注意して下さい。

    パラメータ変更の効果を見るには、このようにします: 

    shell> mysqld -O key_buffer=32m --help

    --help オプションは最後につけてください。 その他のオプションを --help の後につけると、そのオプションは反映されません。

    5.5.3 MySQL の速度に影響するコンパイルとリンク方法

    次のテストの多くは Linux 上で MySQL ベンチマークで行われました。 しかし、これらは他の OS についてもいくつかの指標を与えます。

    -static でのリンク時に最速の実行形式を得ます。

    Linux では、pgcc と -O3 でコンパイルした時に最速のコードを得られます。 このオプションで `sql_yacc.cc' をコンパイルすると、gcc/pgcc は 全ての関数をインラインにするために多くのメモリを必要とするので、200M のメモリが 必要です。 libstdc++ ライブラリの増加を避けるためには、 MySQL の configure 時に CXX=gcc も設定すべきです。 Note that with some versions of pgcc, the resulting code will only run on true Pentium processors, even if you use the compiler option that you want the resulting code to be working on all x586 type processors (like AMD).

    より良いコンパイラー、そしてコンパイラーのオプションは、10-30% の 速度の向上をもたらします。 これはあなた自身が MySQL をコンパイルする 時に重要なことです！

    我々は Cygnus CodeFusion と Fujitsu コンパイラーでもテストしましたが、 MySQL を最適化オプションでコンパイルするには、 どちらもまだ完全なバグ・フリーではありませんでした。

    When you compile MySQL you should only include support for the character sets that you are going to use. (Option --with-charset=xxx). The standard MySQL binary distributions are compiled with support for all character sets.

    Here is a list of some measurements that we have done:

    • pgcc を使用して -O6 で全てをコンパイルすると、 gcc 2.95.2 より、mysqld サーバーは 1% 速くなります。
    • Linux 上では、動的リンク(-static) 無し)の場合、結果は 13% 遅くなります。 Note that you still can use a dynamic linked MySQL library. It is only the server that is critical for performance.
    • If you strip your mysqld binary with strip libexec/mysqld, the resulting binary can be up to 4% faster.
    • (localhost への接続に) Unix ソケットの代わりに TCP/IP を使用すると、結果は 7.5% 遅くなります。 (localhost へ接続する場合、MySQL はデフォルトではソケット を使用します)。
    • If you connect using TCP/IP from another computer over a 100M Ethernet, things will be 8-11% slower.
    • When running our benchmark tests using secure connections (all data encrypted with internal SSL support) things were 55% slower.
    • --with-debug=full でコンパイルすると、ほとんどのクエリで 20% 遅くな りますが、いくつかのクエリは実質的にはもっと長くなります(MySQL ベ ンチマークでは 35% 遅くなりました)。 --with-debug を使用すると、15% だけ遅くなります。 By starting a mysqld version compiled with --with-debug=full with --skip-safemalloc the end result should be close to when configuring with --with-debug.
    • On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster than gcc 3.2
    • On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster in 32 bit mode than in 64 bit mode.
    • UltraSPARC で gcc 2.95.2 でオプション -mcpu=v8 -Wa,-xarch=v8plusa をつけてコンパイルすると 4% 良い性能が得られます。
    • シングルプロセッサの Solaris 2.5.1 では、MIT-pthreads は Solaris ネイティブスレ ッドより 8-12% 遅くなります。 With more load/CPUs the difference should get bigger.
    • --log-bin での実行は mysqld を 1% 遅くします。
    • Compiling on Linux-x86 using gcc without frame pointers -fomit-frame-pointer or -fomit-frame-pointer -ffixed-ebp makes mysqld 1-4% faster.

    The MySQL-Linux distribution provided by MySQL AB used to be compiled with pgcc, but we had to go back to regular gcc because of a bug in pgcc that would generate the code that does not run on AMD. We will continue using gcc until that bug is resolved. In the meantime, if you have a non-AMD machine, you can get a faster binary by compiling with pgcc. The standard MySQL Linux binary is linked statically to get it faster and more portable.

    5.5.4 MySQL はどのようにメモリを使用するのか？

    以下に mysqld サーバーがどのようにメモリーを使用するか、いくつか示します。 サーバーに与える変数名は、サーバーのメモリーの使用方に関連した名前となっています:

    • キーバッファ (変数 key_buffer) は全てのスレッドで共有され、 残りは必要時に割り当てられます。 「5.5.2 サーバーパラメーターのチューニング」節参照.
    • 各接続はいくつかのスレッド空間を使用します； スタック (64K, 変数 thread_stack), 接続バッファ(variable net_buffer_length), 結果バッファ(variable net_buffer_length)。接続バッファと結果バッファは必要となった時、 動的に最大 max_allowed_packet まで増えます。 クエリが走っている時、そのクエリの文字のコピーが割り当てられます。
    • 全てのスレッドは同じベースメモリを共有します。
    • 圧縮された ISAM / MyISAM だけが、memory mapped されます。 これは 4GB の 32bit メモリ空間は多くの大きなテーブルを扱うには小さいためです。 64bit アドレス空間を持つシステムがより普及すれば、我々は mmemory mapping を通常 にサポートします。
    • テーブルを越えて順次スキャンを行なう各要求は、読み込みバッファを割り当てます (変数 record_buffer)
    • When reading rows in 'random' order (for example after a sort) a random-read buffer is allocated to avoid disk seeks. (variable record_rnd_buffer).
    • 全ての結合は1パスで行なわれ、多くの結合は一時テーブルを使用せずに行なわ れます。多くの一時テーブルはメモリベース(HEAP)のテーブルです。大きなレコー ドサイズ (= 全フィールド長の合計) を持つ一時テーブルまたは、BLOB を含む テーブルはディスク上に置かれます。 MySQL バージョン 3.23.2 以前での問題は、HEAP テーブルが tmp_table_size のサイズを越えると、エラー The table tbl_name is full が出ることです。将来我々は、必要時にメモリ (HEAP) テーブルをディスクベー ス (MyISAM) テーブルに自動的に変更することにより、これを修正します。この 問題を回避するため、mysqld への tmp_table_size オプションま たはクライアント側で SQL オプション BIG_TABLES (ver.4.0.3未満では SQL_BIG_TABLES) で増加できます。 「5.5.6 SET 構文」節参照. MySQL バージョン 3.20 では、一時テーブルの最大サイズは recordbuffer*16 でした。そのため、このバージョンを使用していると、 recordbuffer を追加する必要があります。 mysqld を --big-tables で 開始することで、常に一時テーブルをディスク上に格納できます。しかしこれは 多くの複雑なクエリの速度に影響します。
    • ほとんどのリクエストは、0-2個の一時ファイルとわずかなソートバッファへの割り当て を行います。 「A.4.4 MySQL が一時ファイルを格納する場所」節参照.
    • パースと演算時に使用されるほとんど全てのメモリはローカルメモリストア内で行 なわれます。小さな項目に必要とされるメモリオーバーヘッドはなく、通常の遅 いメモリ割り当て/解放が回避されます。メモリは予期しない大きな文字列にだ け割り当てられます(これは malloc() と free() で行なわれます)。
    • 各インデックスファイルは一度オープンされ、データファイルは各同時実行 スレッド毎に一度オープンされます。各同時スレッドには、テーブル構造、 各フィールドの構造そして 3 * n のサイズのバッファが割り当てられます。 ( n は BLOB 型のフィールドの長さを含めない、一レコードの最大長です ) BLOB は 5 から 8 バイト + BLOB データの長さを使用します。 The ISAM/MyISAM table handlers will use one extra row buffer for internal usage.
    • BLOB を持つ各テーブルでは、より大きな BLOB の読み込みでバッファ は動的に拡大されます。テーブルのスキャンをする場合、割り当てられたバッファは最 も大きい BLOB と同じ大きさになります。
    • 全ての使用されているテーブルの storage engine はキャッシュ内に保存され、 FIFO として管理されます。 通常、キャッシュは 64 個のテーブルです。テーブルが 2 つの実行しているス レッドで同時に使用される場合、キャッシュ内にテーブルの 2 つのエントリが あります。 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節参照.
    • mysqladmin flush-tables は使用されていない全てのテーブルをクローズし、 使用されている全てのテーブルを、実行中スレッドが終った時にクローズするよ うにマークします。これは多くの使用メモリを解放するのに有効です。全てのロ グファイルもクローズと再オープンされます。

    mysqld 実行時、ps や他のプログラムは、それが多くのメモリ を使用していると報告するでしょう。これは異なったメモリアドレス上のスレッ ドスタックによって発生します。例えば、Solaris ps はスタック間の未使用メ モリを使用メモリとして計算します。'swap -s' で有効なスワップをチェックす ることでこれを確かめられます。我々は市販のメモリリーク検出プログラムで mysqld をテストしました。そのため、メモリリークは全くありません。

    5.5.5 How MySQL uses DNS

    When a new thread connects to mysqld, mysqld will span a new thread to handle the request. This thread will first check if the hostname is in the hostname cache. If not the thread will call gethostbyaddr_r() and gethostbyname_r() to resolve the hostname.

    If the operating system doesn't support the above thread-safe calls, the thread will lock a mutex and call gethostbyaddr() and gethostbyname() instead. Note that in this case no other thread can resolve other hostnames that is not in the hostname cache until the first thread is ready.

    You can disable DNS host lookup by starting mysqld with --skip-name-resolve. In this case you can however only use IP names in the MySQL privilege tables.

    If you have a very slow DNS and many hosts, you can get more performance by either disabling DNS lookop with --skip-name-resolve or by increasing the HOST_CACHE_SIZE define (default: 128) and recompile mysqld.

    You can disable the hostname cache with --skip-host-cache. You can clear the hostname cache with FLUSH HOSTS or mysqladmin flush-hosts.

    If you don't want to allow connections over TCP/IP, you can do this by starting mysqld with --skip-networking.

    5.5.6 SET 構文

    SET [GLOBAL | SESSION] sql_variable=expression, [[GLOBAL | SESSION] sql_variable=expression...]

    SET OPTION はサーバやクライアントの操作に影響する様々なオプションを設定します. 現在のセッションが終わるか,またはあなたが異なった値にオプションを設定するまで, 設定されたオプション値は残っています.

    SET sets various options that affect the operation of the server or your client.

    The following examples shows the different syntaxes one can use to set variables:

    In old MySQL versions we allowed the use of the SET OPTION syntax, but this syntax is now deprecated.

    In MySQL 4.0.3 we added the GLOBAL and SESSION options and access to most important startup variables.

    LOCAL can be used as a synonym for SESSION.

    If you set several variables on the same command line, the last used GLOBAL | SESSION mode is used. 

    SET sort_buffer_size=10000;
SET @@local.sort_buffer_size=10000;
SET GLOBAL sort_buffer_size=1000000, SESSION sort_buffer_size=1000000;
SET @@sort_buffer_size=1000000;
SET @@global.sort_buffer_size=1000000, @@local.sort_buffer_size=1000000;

    The @@variable_name syntax is supported to make MySQL syntax compatible with some other databases.

    The different system variables one can set are described in the system variable section of this manual. 「6.1.5 System Variables」節参照.

    If you are using SESSION (the default) the option you set remains in effect until the current session ends, or until you set the option to a different value. If you use GLOBAL, which require the SUPER privilege, the option is remembered and used for new connections until the server restarts. If you want to make an option permanent, you should set it in one of the MySQL option files. 「4.1.2 `my.cnf' オプションファイル」節参照.

    To avoid wrong usage MySQL will give an error if you use SET GLOBAL with a variable that can only be used with SET SESSION or if you are not using SET GLOBAL with a global variable.

    If you want to set a SESSION variable to the GLOBAL value or a GLOBAL value to the MySQL default value, you can set it to DEFAULT. 

    SET max_join_size=DEFAULT;

    This is identical to: 

    SET @@session.max_join_size=@@global.max_join_size;

    If you want to restrict the maximum value a startup option can be set to with the SET command, you can specify this by using the --maximum-variable-name command line option. 「4.1.1 mysqld コマンド行オプション」節参照.

    You can get a list of most variables with SHOW VARIABLES. 「4.5.6.4 SHOW VARIABLES」節参照. You can get the value for a specific value with the @@[global.|local.]variable_name syntax: 

    SHOW VARIABLES like "max_join_size";
SHOW GLOBAL VARIABLES like "max_join_size";
SELECT @@max_join_size, @@global.max_join_size;

    Here follows a description of the variables that uses a the variables that uses a non-standard SET syntax and some of the other variables. The other variable definitions can be found in the system variable section, among the startup options or in the description of SHOW VARIABLES. 「6.1.5 System Variables」節参照. 「4.1.1 mysqld コマンド行オプション」節参照. 「4.5.6.4 SHOW VARIABLES」節参照.

    CHARACTER SET character_set_name | DEFAULT
    これは指定されたマッピングに従って、すべての文字列をクライアントからクライアント にマップします. 現在、character_set_name に指定できるオプションは cp1251_koi8 だけですが, MySQL のソース中にある `sql/convert.cc' ファイルを編集することによって, 容易に新しいマッピングを加えることができます. 標準のマッピングに戻すには、 character_set_name に DEFAULT を指定します。 CHARACTER SET オプションを設定するための構文は、 他のオプションを設定する構文と異なっていることに注意してください.
    PASSWORD = PASSWORD('some password')
    現在のユーザのパスワードを設定します。いかなる非匿名のユーザも、 自分自身パスワードを変えることができます!
    PASSWORD FOR user = PASSWORD('some password')
    現在ログインしているホストの特定ユーザのパスワードを設定します。 mysql データベースにアクセスができるユーザーだけが実行できます。 ユーザは user@hostname 形式で与えなくてはなりません。 ここで user と hostname は、mysql.user テーブルの User, Host フィールドに登録されていなくてはなりません。 例えば、User と Host フィールドが 'bob' と '%.loc.gov' ならば、以下のようにします： 
    mysql> SET PASSWORD FOR bob@"%.loc.gov" = PASSWORD("newpass");
    Which is equivalent to: 
    mysql> UPDATE mysql.user SET password=PASSWORD("newpass")
    ->                   WHERE user="bob" AND host="%.loc.gov";
    SQL_AUTO_IS_NULL = 0 | 1
    1 (デフォルト) を設定すると、次のようにして、auto_increment レコー ドを持つテーブルで、最後に挿入されたレコードを見つけることができます: WHERE auto_increment_column IS NULL。これは、Access のようないくつ かの ODBC プログラムによって使用されます。
    AUTOCOMMIT= 0 | 1
    1 を設定すると、テーブルへのすべての変更はすぐに行なわれます。 複数コマンドトランザクションを開始するためには、BEGIN ステートメ ントを使用する必要があります。 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照。 0 を設定すると、そのトランザクションを許可/破棄するために、 COMMIT / ROLLBACK を使用する必要があります。 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照。 注意: 非 AUTOCOMMIT モードから AUTOCOMMIT モードに変更する時、 MySQL はすべてのオープントランザクションを自動的に COMMIT します。
    BIG_TABLES = 0 | 1 (ver.4.0.3未満では SQL_BIG_TABLES)
    0 の場合、全ての一時テーブルはメモリーではなくディスクに書き出されます。 これは少し遅くなりますが、多くの一時テーブルを必要とする大きな SELECT を 実行しても、The table tbl_name is full エラーが出なくなります。 新しい接続におけるこの値のデフォルト値は 1 (メモリーに一時テーブルを作る) です。
    SQL_BIG_SELECTS = 0 | 1
    1 の場合、とても時間のかかる SELECT が実行された場合、 MySQL はそれを中止します。 これはあまり芳しくない(間違った) WHERE 構文が発行されたときに役立ちます。 max_join_size 行以上を検討するような SELECT が 大きなクエリと定義されます。 新しい接続におけるこの値のデフォルト値は 0 です。 (全ての SELECT 構文を許します)
    SQL_BUFFER_RESULT = 0 | 1
    SQL_BUFFER_RESULT は一時ファイルに置かれる SELECT からの結果 を強制的に置きます。これは MySQL がテーブルロックを早く解放する手 助けをし、クライアントへ結果セットを送信するために長い時間が掛かる場合に役 立ちます。
    LOW_PRIORITY_UPDATES = 0 | 1
    1 の場合、全ての INSERT, UPDATE, DELETE, LOCK TABLE WRITE構文は、 対象となるテーブルを処理中の SELECT や LOCK TABLE READ がなくなるまで待ちます。 ver.4.0.3 未満では SQL_LOW_PRIORITY_UPDATES オプションになります.
    MAX_JOIN_SIZE = value | DEFAULT
    おそらく value よりも多いレコードの組合せを試験する必要があるような SELECT を許可しません。この値を設定することで、キーが使用されないで あろう SELECT と長い時間が掛かるであろう SELECT を捕捉できま す。これを DEFAULT 以外の値に設定すると、SQL_BIG_SELECTS フ ラグをリセットします。SQL_BIG_SELECTS フラグを再び設定すると、 SQL_MAX_JOIN_SIZE 変数は無視されます。-O max_join_size=# で mysqld を起動することで、この変数のデフォルト値を設定できます。T ver.4.0.3 未満では SQL_MAX_JOIN_SIZE オプションになります. Note that if the result of the query is already in the query cache, the above check will not be made. Instead, MySQL will send the result to the client. Since the query result is already computed and it will not burden the server to send the result to the client.
    QUERY_CACHE_TYPE = OFF | ON | DEMAND
    QUERY_CACHE_TYPE = 0 | 1 | 2
    Set query cache setting for this thread.
    Option Description
    0 or OFF Don't cache or retrieve results.
    1 or ON Cache all results except SELECT SQL_NO_CACHE ... queries.
    2 or DEMAND Cache only SELECT SQL_CACHE ... queries.
    SQL_SAFE_UPDATES = 0 | 1
    1 に設定すると、WHERE 節内でキーや LIMIT を使用しない で UPDATE または DELETE を行なおうとした場合に MySQL がアボートします。これは、手で SQL コマンドを生成する時の間 違った更新の捕捉を可能にします。
    SQL_SELECT_LIMIT = value | DEFAULT
    SELECT 構文から返されるレコードの最大値。 もし SELECT に LIMIT 節を使用している場合、LIMIT は SQL_SELECT_LIMIT の値より優先されます。 新しい接続におけるこの値の標準値は ``unlimited''. もしリミットを変えているならば、SQL_SELECT_LIMIT に DEFAULT を指定することにより、標準値に戻すことができます。
    SQL_LOG_OFF = 0 | 1
    この値が 1 の場合、もしクライアントが SUPER 権限 (version4.0.2以上。それ未満では PROCESS権限) を持っているならば、 このクライアントのログが行われません。 これは更新ログに影響しません！
    SQL_LOG_UPDATE = 0 | 1
    0 の場合、もしクライアントが SUPER 権限 (version4.0.2以上。それ未満では PROCESS権限) を持っているならば、 このクライアントの更新ログの記録は行われません。 これは通常のログには影響しません！
    SQL_QUOTE_SHOW_CREATE = 0 | 1
    If set to 1, SHOW CREATE TABLE will quote table and column names. This is on by default, for replication of tables with fancy column names to work. 「4.5.6.8 SHOW CREATE TABLE」節.
    TIMESTAMP = timestamp_value | DEFAULT
    クライアントに時間を設定します。 もしレコードのリストアに更新ログを使用する場合、オリジナルのタイムスタンプを得る ために使用します。 timestamp_value should be a UNIX Epoch timestamp, not a MySQL timestamp.
    LAST_INSERT_ID = #
    LAST_INSERT_ID() からの返り値を設定します。 テーブルを更新するコマンド中に LAST_INSERT_ID() を使用した場合、 これは更新ログに保存されます。
    INSERT_ID = #
    AUTO_INCREMENT 値を挿入する時、 INSERT , ALTER TABLE コマンドに従って使用される値をセットします。 これは更新ログによって使用されます。

    5.6 Disk の問題

    • 前に述べたディスクシークが大きなボトルネックです。 この問題は、データが効果的に キャッシングが不可能になるほど、大きくなり始めるときに、だんだん明白になってきま す。 For large databases, where you access data more or less randomly, you can be sure that you will need at least one disk seek to read and a couple of disk seeks to write things. この問題を少なくするには、diskシーク時間の少ないディスクを 使用します。
    • 利用できるディスクスピンドルの数を増やします(それによってディスクシーク のオーバーヘッドは縮小します)。 これは違うディスクにシンボリックリンクをはったり、ストライピングを行うことで 可能です。
      Using symbolic links
      これは通常のデータディレクトリから、違うディスクへ、 インデックスやデータファイルをシンボリック・リンクすることです。 これは シーク と リード を速くします。 (もしそのディスクが 他に使用されていなければ). 「5.6.1 シンボリックリンクの使用」節参照.
      Striping
      ストライピングは、複数のディスクに対して、まずデータの最初のブロックを 1番目の disk に書き、2番目のブロックを2つ目のdiskに書き、順次 N 番目 (N は disk の数) まで順に書いていきます。 これは、もしデータがストライプの サイズよりも小さければ、よりよいパフォーマンスを得ることが出来ます。 ストライピングは、OS や ストライプのサイズにとても依存していることに注意してくだ さい。そのため、あなたのアプリケーションのベンチマークがストライプサイズによって 変わるでしょう。 「5.1.5 Using Your Own Benchmarks」節参照. ストライピングのスピードの違いは、とても パラメターに依存しています。 Depending on how you set the striping parameters and number of disks you may get a difference in orders of magnitude. Note that you have to choose to optimize for random or sequential access.
    • 信頼性のため、あなたは RAID 0+1 (striping + mirroring) を使用したいと 思うかもしれません。 しかしこれは N 個のドライブのデータを収めるのに 2*N 個のドライブが必要となります。 これはもし資金があるならば一番よい方法でしょう！ しかし、能率的にそれを 取り扱うために、ボリューム・マネージメント・ソフトウェアに投資する必要が あってもよいです。
    • A good option is to have semi-important data (that can be regenerated) on RAID 0 disk while storing really important data (like host information and logs) on a RAID 0+1 or RAID N disk. RAID N can be a problem if you have many writes because of the time to update the parity bits.
    • データベースに使用しているファイルシステムの mount パラメターを変更しても 良いでしょう。 一つの簡単な方法としては、noatime オプションでファイルシステムを マウントします。 これは inode にある最後にアクセスした時間の更新を スキップします。 これでいくらか ディスクシークを避けることができるでしょう。
    • On Linux, you can get much more performance (up to 100% under load is not uncommon) by using hdparm to configure your disk's interface! The following should be quite good hdparm options for MySQL (and probably many other applications): 
      hdparm -m 16 -d 1
      Note that the performance/reliability when using the above depends on your hardware, so we strongly suggest that you test your system thoroughly after using hdparm! Please consult the hdparm man page for more information! If hdparm is not used wisely, filesystem corruption may result. Backup everything before experimenting!
    • On many operating systems you can mount the disks with the -o async option to set the filesystem to be updated asynchronously. If your computer is reasonably stable, this should give you more performance without sacrificing too much reliability. (This flag is on by default on Linux.)
    • If you don't need to know when a file was last accessed (which is not really useful on a database server), you can mount your filesystems with the -o noatime option.

    5.6.1 シンボリックリンクの使用

    テーブルとデータベースのファイルを MySQL のデータベースディレクトリーから 違う場所に移動し、 それに対してシンボリックリンクを張ることができます。例 えば、もっと空き容量のあるファイルシステムへデータベースを移すため、あるい はテーブルを異なるディスクに広げることでシステムのスピードを増加するために これを行ないたくなるでしょう。

    The recommended way to do this, is to just symlink databases to a different disk and only symlink tables as a last resort.

    5.6.1.1 Using Symbolic Links for Databases

    The way to symlink a database is to first create a directory on some disk where you have free space and then create a symlink to it from the MySQL database directory. 

    shell> mkdir /dr1/databases/test
shell> ln -s /dr1/databases/test mysqld-datadir

    MySQL は一つのディレクトリを複数のデータベースにリンクすることは サポートしていません。シンボリックリンクを持つデータベースディレクトリの複 製は、データベース間のシンボリックリンクを作成しなければ、正常に動作します。 MySQL データディレクトリに db1 データベースがあるとして、 db1 を指すシンボリックリンク db2 を作成します。 

    shell> cd /path/to/datadir
shell> ln -s db1 db2

    すると、db1 中の tbl_a テーブルは db2 の tbl_a テー ブルとして見えます。 もしあるスレッドが db1.tbl_a を更新し、他のスレッドが db2.tbl_a を 更新した場合、 問題が発生します。

    こういった使用をどうしてもしたい場合、`mysys/mf_format.c' を以下のように変 更します: 

    if (flag & 32 || (!lstat(to,&stat_buff) && S_ISLNK(stat_buff.st_mode)))

    to 

    if (1)

    On Windows you can use internal symbolic links to directories by compiling MySQL with -DUSE_SYMDIR. This allows you to put different databases on different disks. 「2.6.2.5 Windows 上で、異なるディスクにデータを分割する」節参照.

    5.6.1.2 Using Symbolic Links for Tables

    Before MySQL 4.0 you should not symlink tables, if you are not very careful with them. The problem is that if you run ALTER TABLE, REPAIR TABLE or OPTIMIZE TABLE on a symlinked table, the symlinks will be removed and replaced by the original files. This happens because the above command works by creating a temporary file in the database directory and when the command is complete, replace the original file with the temporary file.

    You should not symlink tables on systems that don't have a fully working realpath() call. (At least Linux and Solaris support realpath())

    In MySQL 4.0 symlinks are fully supported only for MyISAM tables. For other table types you will probably get strange problems when doing any of the above mentioned commands.

    The handling of symbolic links in MySQL 4.0 works the following way (this is mostly relevant only for MyISAM tables).

    • In the data directory you will always have the table definition file and the data and index files.
    • You can symlink the index file and the data file to different directories independently of the other.
    • The symlinking can be done from the operating system (if mysqld is not running) or with the INDEX/DATA DIRECTORY="path-to-dir" command in CREATE TABLE. 「6.5.3 CREATE TABLE 構文」節参照.
    • myisamchk will not replace a symlink with the data or index file but work directly on the file the symlink points to. Any temporary files will be created in the same directory where the data or index file is located.
    • When you drop a table that is using symlinks, both the symlink and the file the symlink points to are dropped. This is a good reason to why you should not run mysqld as root or allow persons to have write access to the MySQL database directories.
    • If you rename a table with ALTER TABLE RENAME and you don't move the table to another database, the symlinks in the database directory will be renamed to the new names and the data and index files will be renamed accordingly.
    • If you use ALTER TABLE RENAME to move a table to another database, the table will be moved to the other database directory and the old symlinks and the files they pointed to will be deleted. (In other words, the new table will not be symlinked.)
    • If you are not using symlinks, you should use the --skip-symlink option to mysqld to ensure that no one can drop or rename a file outside of the mysqld data directory.

    Things that are not yet supported:

    • ALTER TABLE ignores all INDEX/DATA DIRECTORY="path" options.
    • CREATE TABLE doesn't report if the table has symbolic links.
    • mysqldump doesn't include the symbolic link information in the output.
    • BACKUP TABLE and RESTORE TABLE don't respect symbolic links.

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Function_Index.html0100644000175100001560000015255310021471264017401 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - SQL command, type and function index Go to the first, previous, next, last section, table of contents.

    SQL command, type and function index

  • ! (logical NOT)
  • != (not equal)
  • "
  • % (modulo)
  • % (wildcard character)
  • & (bitwise AND)
  • && (logical AND)
  • () (parentheses)
  • (Control-Z) \z
  • * (multiplication)
  • + (addition)
  • - (subtraction)
  • - (unary minus)
  • -p option
  • -password option
  • .my.cnf file, .my.cnf file, .my.cnf file, .my.cnf file, .my.cnf file, .my.cnf file, .my.cnf file
  • .mysql_history file
  • .pid (process ID) file
  • / (division)
  • /etc/passwd
  • `/etc/passwd'
  • < (less than)
  • <<
  • << (left shift)
  • <= (less than or equal)
  • <=> (Equal to)
  • <> (not equal)
  • = (equal)
  • > (greater than)
  • >= (greater than or equal)
  • >> (right shift)
  • \" (double quote)
  • \' (single quote)
  • \0 (ASCII 0)
  • \\ (escape)
  • \b (backspace)
  • \n (newline)
  • \r (carriage return)
  • \t (tab)
  • \z (Control-Z) ASCII(26)
  • ^ (bitwise XOR)
  • _ (wildcard character)
  • `

    • A

  • ABS()
  • ACOS()
  • ADDDATE()
  • addition (+)
  • AES_DECRYPT()
  • AES_ENCRYPT()
  • alias
  • ALTER COLUMN
  • ALTER TABLE, ALTER TABLE, ALTER TABLE
  • ANALYZE TABLE
  • AND, bitwise
  • AND, logical
  • arithmetic functions
  • AS, AS
  • ASCII()
  • ASIN()
  • ATAN()
  • ATAN2()
  • AVG()

    • B

  • backspace (\b)
  • BACKUP TABLE
  • BEGIN
  • BENCHMARK()
  • BETWEEN ... AND
  • BIGINT
  • BIN()
  • BINARY
  • BIT
  • bit functions
  • BIT_AND()
  • BIT_COUNT
  • BIT_COUNT()
  • BIT_LENGTH()
  • BIT_OR
  • BIT_OR()
  • BLOB, BLOB
  • BOOL

    • C

  • carriage return (\r)
  • CASE
  • CAST
  • casts
  • CC environment variable
  • CC environment variable, CC environment variable
  • CCX environment variable
  • CEILING()
  • CFLAGS environment variable, CFLAGS environment variable
  • CHAR, CHAR
  • CHAR VARYING
  • CHAR()
  • CHAR_LENGTH()
  • CHARACTER
  • CHARACTER VARYING
  • CHARACTER_LENGTH()
  • CHECK TABLE
  • ChopBlanks DBI method
  • COALESCE()
  • command-line options
  • Comment syntax
  • COMMIT, COMMIT
  • comparison operators
  • CONCAT()
  • CONCAT_WS()
  • configure option, --with-charset
  • configure option, --with-extra-charsets
  • connect() DBI method
  • CONNECTION_ID()
  • control flow functions
  • CONV()
  • CONVERT
  • COS()
  • COT()
  • COUNT()
  • COUNT(DISTINCT)
  • CREATE DATABASE
  • CREATE FUNCTION
  • CREATE INDEX
  • CREATE TABLE
  • CROSS JOIN
  • CURDATE()
  • CURRENT_DATE
  • CURRENT_TIME
  • CURRENT_TIMESTAMP
  • CURRENT_USER()
  • CURTIME()
  • CXX environment variable
  • CXX environment variable, CXX environment variable, CXX environment variable
  • CXXFLAGS environment variable, CXXFLAGS environment variable, CXXFLAGS environment variable, CXXFLAGS environment variable

    • D

  • data_sources() DBI method
  • DATABASE()
  • DATE, DATE, DATE
  • date and time functions
  • DATE_ADD()
  • DATE_FORMAT()
  • DATE_SUB()
  • DATETIME, DATETIME
  • DAYNAME()
  • DAYOFMONTH()
  • DAYOFWEEK()
  • DAYOFYEAR()
  • DBI->connect()
  • DBI->data_sources()
  • DBI->disconnect
  • DBI->do()
  • DBI->execute
  • DBI->fetchall_arrayref
  • DBI->fetchrow_array
  • DBI->fetchrow_arrayref
  • DBI->fetchrow_hashref
  • DBI->finish
  • DBI->prepare()
  • DBI->quote
  • DBI->quote()
  • DBI->rows
  • DBI->trace, DBI->trace
  • DBI->{ChopBlanks}
  • DBI->{insertid}
  • DBI->{is_blob}
  • DBI->{is_key}
  • DBI->{is_not_null}
  • DBI->{is_num}
  • DBI->{is_pri_key}
  • DBI->{length}
  • DBI->{max_length}
  • DBI->{NAME}
  • DBI->{NULLABLE}
  • DBI->{NUM_OF_FIELDS}
  • DBI->{table}
  • DBI->{type}
  • DBI_TRACE environment variable, DBI_TRACE environment variable, DBI_TRACE environment variable
  • DBI_USER environment variable
  • DEC
  • DECIMAL
  • DECODE()
  • DEGREES()
  • DELAYED
  • DELETE
  • DES_DECRYPT()
  • DES_ENCRYPT()
  • DESC
  • DESCRIBE, DESCRIBE
  • disconnect DBI method
  • DISTINCT, DISTINCT, DISTINCT
  • division (/)
  • DO
  • do() DBI method
  • DOUBLE
  • DOUBLE PRECISION
  • double quote (\")
  • DROP DATABASE
  • DROP FUNCTION
  • DROP INDEX, DROP INDEX
  • DROP PRIMARY KEY
  • DROP TABLE
  • DUMPFILE

    • E

  • ELT()
  • ENCODE()
  • ENCRYPT()
  • ENUM, ENUM
  • environment variable, CC
  • Environment variable, CC
  • environment variable, CC
  • Environment variable, CCX
  • environment variable, CFLAGS
  • Environment variable, CFLAGS
  • Environment variable, CXX
  • environment variable, CXX
  • environment variable, CXX
  • environment variable, CXXFLAGS, environment variable, CXXFLAGS, environment variable, CXXFLAGS
  • Environment variable, CXXFLAGS
  • Environment variable, DBI_TRACE, Environment variable, DBI_TRACE, Environment variable, DBI_TRACE
  • Environment variable, DBI_USER
  • environment variable, HOME
  • Environment variable, HOME
  • environment variable, LD_RUN_PATH
  • Environment variable, LD_RUN_PATH, Environment variable, LD_RUN_PATH, Environment variable, LD_RUN_PATH
  • Environment variable, MYSQL_DEBUG, Environment variable, MYSQL_DEBUG
  • environment variable, MYSQL_DEBUG
  • Environment variable, MYSQL_HISTFILE
  • environment variable, MYSQL_HISTFILE
  • Environment variable, MYSQL_HOST
  • environment variable, MYSQL_HOST
  • Environment variable, MYSQL_PS1
  • environment variable, MYSQL_PWD, environment variable, MYSQL_PWD
  • Environment variable, MYSQL_PWD
  • environment variable, MYSQL_TCP_PORT, environment variable, MYSQL_TCP_PORT
  • environment variable, MYSQL_TCP_PORT
  • Environment variable, MYSQL_TCP_PORT
  • environment variable, MYSQL_UNIX_PORT, environment variable, MYSQL_UNIX_PORT
  • Environment variable, MYSQL_UNIX_PORT, Environment variable, MYSQL_UNIX_PORT
  • environment variable, MYSQL_UNIX_PORT
  • Environment variable, PATH
  • environment variable, PATH
  • Environment variable, TMPDIR, Environment variable, TMPDIR
  • Environment variable, TZ, Environment variable, TZ
  • Environment variable, UMASK, Environment variable, UMASK
  • Environment variable, UMASK_DIR, Environment variable, UMASK_DIR
  • environment variable, USER
  • Environment variable, USER
  • Environment variables, CXX
  • equal (=)
  • escape (\\)
  • execute DBI method
  • EXP()
  • EXPLAIN
  • EXPORT_SET()
  • EXTRACT(), EXTRACT()

    • F

  • fetchall_arrayref DBI method
  • fetchrow_array DBI method
  • fetchrow_arrayref DBI method
  • fetchrow_hashref DBI method
  • FIELD()
  • FILE
  • FIND_IN_SET()
  • finish DBI method
  • FLOAT, FLOAT
  • FLOAT(M,D)
  • FLOAT(precision), FLOAT(precision)
  • FLOOR()
  • FLUSH
  • FORCE INDEX, FORCE INDEX
  • FORMAT()
  • FOUND_ROWS()
  • FROM_DAYS()
  • FROM_UNIXTIME(), FROM_UNIXTIME()
  • functions, arithmetic
  • functions, bit
  • functions, control flow
  • functions, date and time
  • functions, GROUP BY
  • functions, mathematical
  • functions, miscellaneous
  • functions, string
  • functions, string comparison
  • Functions, user-defined

    • G

  • GET_LOCK()
  • GRANT
  • GRANT statement, GRANT statement
  • GRANTS
  • greater than (>)
  • greater than or equal (>=)
  • GREATEST()
  • GROUP BY functions

    • H

  • HANDLER
  • HEX()
  • hexadecimal values
  • HOME environment variable
  • HOME environment variable
  • host.frm, problems finding
  • HOUR()

    • I

  • identifiers, quoting
  • IF()
  • IFNULL()
  • IGNORE INDEX, IGNORE INDEX
  • IGNORE KEY, IGNORE KEY
  • IN
  • INET_ATON()
  • INET_NTOA()
  • INNER JOIN
  • INSERT, INSERT
  • INSERT ... SELECT
  • INSERT DELAYED
  • INSERT statement, grant privileges
  • INSERT()
  • insertid DBI method
  • INSTR()
  • INT
  • INTEGER
  • INTERVAL()
  • IS NOT NULL
  • IS NULL
  • IS NULL, and indexes
  • is_blob DBI method
  • IS_FREE_LOCK()
  • is_key DBI method
  • is_not_null DBI method
  • is_num DBI method
  • is_pri_key DBI method
  • ISNULL()
  • ISOLATION LEVEL

    • J

  • JOIN

    • K

  • KILL

    • L

  • LAST_INSERT_ID()
  • LAST_INSERT_ID([expr])
  • LCASE()
  • LD_RUN_PATH environment variable, LD_RUN_PATH environment variable, LD_RUN_PATH environment variable, LD_RUN_PATH environment variable
  • LEAST()
  • LEFT JOIN, LEFT JOIN
  • LEFT OUTER JOIN
  • LEFT()
  • length DBI method
  • LENGTH()
  • less than (<)
  • less than or equal (<=)
  • LIKE
  • LIKE, and indexes
  • LIKE, and wildcards
  • LIMIT, LIMIT
  • LN()
  • LOAD DATA INFILE, LOAD DATA INFILE
  • LOAD_FILE()
  • LOCATE(), LOCATE()
  • LOCK TABLES
  • LOG()
  • LOG10()
  • LOG2()
  • Logical operators
  • LONGBLOB
  • LONGTEXT
  • LOWER()
  • LPAD()
  • LTRIM()

    • M

  • MAKE_SET()
  • MASTER_POS_WAIT()
  • MATCH ... AGAINST()
  • mathematical functions
  • MAX()
  • max_length DBI method
  • MD5()
  • MEDIUMBLOB
  • MEDIUMINT
  • MEDIUMTEXT
  • MID()
  • MIN()
  • minus, unary (-)
  • MINUTE()
  • miscellaneous functions
  • MOD()
  • modulo (%)
  • MONTH()
  • MONTHNAME()
  • multiplication (*)
  • my_init()
  • my_ulonglong C type
  • my_ulonglong values, printing
  • MYSQL C type
  • mysql_affected_rows()
  • mysql_change_user()
  • mysql_character_set_name()
  • mysql_close()
  • mysql_connect()
  • mysql_create_db()
  • mysql_data_seek()
  • MYSQL_DEBUG environment variable, MYSQL_DEBUG environment variable
  • MYSQL_DEBUG environment variable
  • mysql_debug()
  • mysql_drop_db()
  • mysql_dump_debug_info()
  • mysql_eof()
  • mysql_errno()
  • mysql_error()
  • mysql_escape_string()
  • mysql_fetch_field()
  • mysql_fetch_field_direct()
  • mysql_fetch_fields()
  • mysql_fetch_lengths()
  • mysql_fetch_row()
  • MYSQL_FIELD C type
  • mysql_field_count(), mysql_field_count()
  • MYSQL_FIELD_OFFSET C type
  • mysql_field_seek()
  • mysql_field_tell()
  • mysql_free_result()
  • mysql_get_client_info()
  • mysql_get_host_info()
  • mysql_get_proto_info()
  • mysql_get_server_info()
  • mysql_get_server_version()
  • MYSQL_HISTFILE environment variable
  • MYSQL_HISTFILE environment variable
  • MYSQL_HOST environment variable
  • MYSQL_HOST environment variable
  • mysql_info(), mysql_info(), mysql_info(), mysql_info()
  • mysql_info()
  • mysql_init()
  • mysql_insert_id()
  • mysql_insert_id()
  • mysql_kill()
  • mysql_list_dbs()
  • mysql_list_fields()
  • mysql_list_processes()
  • mysql_list_tables()
  • mysql_num_fields()
  • mysql_num_rows()
  • mysql_options()
  • mysql_ping()
  • MYSQL_PS1 environment variable
  • MYSQL_PWD environment variable
  • MYSQL_PWD environment variable, MYSQL_PWD environment variable
  • mysql_query(), mysql_query()
  • mysql_real_connect()
  • mysql_real_escape_string()
  • mysql_real_escape_string()
  • mysql_real_query()
  • mysql_reload()
  • MYSQL_RES C type
  • MYSQL_ROW C type
  • mysql_row_seek()
  • mysql_row_tell()
  • mysql_select_db()
  • mysql_server_end()
  • mysql_server_init()
  • mysql_shutdown()
  • mysql_stat()
  • mysql_store_result(), mysql_store_result()
  • MYSQL_TCP_PORT environment variable, MYSQL_TCP_PORT environment variable
  • MYSQL_TCP_PORT environment variable, MYSQL_TCP_PORT environment variable
  • mysql_thread_end()
  • mysql_thread_id()
  • mysql_thread_init()
  • mysql_thread_safe()
  • MYSQL_UNIX_PORT environment variable, MYSQL_UNIX_PORT environment variable, MYSQL_UNIX_PORT environment variable
  • MYSQL_UNIX_PORT environment variable, MYSQL_UNIX_PORT environment variable
  • mysql_use_result()

    • N

  • NAME DBI method
  • NATIONAL CHAR
  • NATURAL LEFT JOIN
  • NATURAL LEFT OUTER JOIN
  • NATURAL RIGHT JOIN
  • NATURAL RIGHT OUTER JOIN
  • NCHAR
  • newline (\n)
  • NOT BETWEEN
  • not equal (!=)
  • not equal (<>)
  • NOT IN
  • NOT LIKE
  • NOT REGEXP
  • NOT, logical
  • NOW()
  • NUL
  • NULL, NULL
  • NULL value
  • NULLABLE DBI method
  • NULLIF()
  • NUM_OF_FIELDS DBI method
  • NUMERIC

    • O

  • OCT()
  • OCTET_LENGTH()
  • OLD_PASSWORD()
  • Operators, logical
  • OPTIMIZE TABLE
  • OR, bitwise
  • OR, logical
  • ORD()
  • ORDER BY

    • P

  • parentheses ( and )
  • PASSWORD(), PASSWORD(), PASSWORD(), PASSWORD()
  • PATH environment variable, PATH environment variable
  • PERIOD_ADD()
  • PERIOD_DIFF()
  • PI()
  • POSITION()
  • POW()
  • POWER()
  • prepare() DBI method
  • PRIMARY KEY, PRIMARY KEY
  • PROCESSLIST

    • Q

  • QUARTER()
  • QUOTE()
  • quote() DBI method
  • quoting of identifiers

    • R

  • RADIANS()
  • RAND()
  • REAL
  • REGEXP
  • RELEASE_LOCK()
  • RENAME TABLE
  • REPAIR TABLE
  • REPEAT()
  • REPLACE
  • REPLACE ... SELECT
  • REPLACE()
  • REQUIRE GRANT option
  • RESTORE TABLE
  • return (\r)
  • REVERSE()
  • REVOKE
  • RIGHT JOIN
  • RIGHT OUTER JOIN
  • RIGHT()
  • RLIKE
  • ROLLBACK, ROLLBACK
  • ROUND(), ROUND()
  • rows DBI method
  • RPAD()
  • RTRIM()

    • S

  • SEC_TO_TIME()
  • SECOND()
  • SELECT
  • SELECT INTO TABLE
  • SELECT speed
  • SELECT, optimizing
  • SESSION_USER()
  • SET
  • SET OPTION
  • SET PASSWORD statement
  • SET TRANSACTION
  • SHA()
  • SHA1()
  • SHOW COLUMNS
  • SHOW CREATE TABLE, SHOW CREATE TABLE
  • SHOW DATABASE INFO
  • SHOW DATABASES
  • SHOW FIELDS
  • SHOW GRANTS, SHOW GRANTS
  • SHOW INDEX
  • SHOW KEYS
  • SHOW MASTER LOGS
  • SHOW MASTER STATUS
  • SHOW PRIVILEGES
  • SHOW PROCESSLIST, SHOW PROCESSLIST
  • SHOW SLAVE STATUS
  • SHOW STATUS
  • SHOW TABLE STATUS
  • SHOW TABLE TYPES, SHOW TABLE TYPES
  • SHOW TABLES
  • SHOW VARIABLES
  • SHOW WARNINGS, SHOW WARNINGS
  • SIGN()
  • SIN()
  • single quote (\')
  • SMALLINT
  • SOUNDEX()
  • SOUNDS LIKE
  • SPACE()
  • SQL_CACHE
  • SQL_NO_CACHE
  • SQRT()
  • START TRANSACTION
  • statements, GRANT
  • statements, INSERT
  • STD()
  • STDDEV()
  • STRAIGHT_JOIN
  • STRCMP()
  • string comparison functions
  • string functions
  • SUBDATE()
  • SUBSTRING(), SUBSTRING()
  • SUBSTRING_INDEX()
  • subtraction (-)
  • SUM()
  • SYSDATE()
  • SYSTEM_USER()

    • T

  • tab (\t)
  • table DBI method
  • table_cache
  • TAN()
  • TEXT, TEXT
  • threads
  • TIME, TIME
  • TIME_FORMAT()
  • TIME_TO_SEC()
  • TIMESTAMP, TIMESTAMP
  • TINYBLOB
  • TINYINT
  • TINYTEXT
  • TMPDIR environment variable, TMPDIR environment variable
  • TO_DAYS()
  • trace DBI method, trace DBI method
  • TRIM()
  • TRUNCATE
  • TRUNCATE()
  • type DBI method
  • Types
  • TZ environment variable, TZ environment variable

    • U

  • UCASE()
  • UDF functions
  • ulimit
  • UMASK environment variable, UMASK environment variable
  • UMASK_DIR environment variable, UMASK_DIR environment variable
  • unary minus (-)
  • UNION, UNION
  • UNIQUE
  • UNIX_TIMESTAMP()
  • UNLOCK TABLES
  • UPDATE
  • UPPER()
  • USE
  • USE INDEX, USE INDEX
  • USE KEY, USE KEY
  • USER environment variable
  • USER environment variable
  • USER()
  • User-defined functions

    • V

  • VARCHAR, VARCHAR
  • VARIANCE()
  • VERSION()

    • W

  • WEEK()
  • WEEKDAY()
  • WHERE
  • Wildcard character (%)
  • Wildcard character (_)
  • without-server option

    • X

  • XOR, bitwise
  • XOR, logical

    • Y

  • YEAR, YEAR
  • YEAR()

  • | (bitwise OR)
  • || (logical OR)
  • ~

    • Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_GPL_license.html0100644000175100001560000004566510021471264016616 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - H GNU General Public License Go to the first, previous, next, last section, table of contents.

    H GNU General Public License

    Version 2, June 1991 

    Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA  02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

    H.1 Preamble

    The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

    When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

    To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

    For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

    We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

    Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

    Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

    The precise terms and conditions for copying, distribution and modification follow.

    H.2 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

    1. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The ``Program'', below, refers to any such program or work, and a ``work based on the Program'' means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term ``modification''.) Each licensee is addressed as ``you''. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
    2. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
    3. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
      1. You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
      2. You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
      3. If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
      These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
    4. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
      1. Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
      2. Accompany it with a written offer, valid for at least three years, to give any third-party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
      3. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
      The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
    5. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
    6. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
    7. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
    8. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
    9. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
    10. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and ``any later version'', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
    11. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

      9.4 NO WARRANTY

    12. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
    13. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

    9.5 END OF TERMS AND CONDITIONS

    H.3 How to Apply These Terms to Your New Programs

    If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

    To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the ``copyright'' line and a pointer to where the full notice is found. 

    one line to give the program's name and a brief idea of what it does.
Copyright (C) yyyy  name of author

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.

    Also add information on how to contact you by electronic and paper mail.

    If the program is interactive, make it output a short notice like this when it starts in an interactive mode: 

    Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

    The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

    You should also get your employer (if you work as a programmer) or your school, if any, to sign a ``copyright disclaimer'' for the program, if necessary. Here is a sample; alter the names: 

    Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989
Ty Coon, President of Vice

    This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Installing.html0100644000175100001560000104423010021471264016562 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 2 MySQL のインストール Go to the first, previous, next, last section, table of contents.

    2 MySQL のインストール

    この章では、どのようにして MySQL を得、インストールするのかをのべます:

    • MySQL を得ることができるサイトのリスト → 「2.2.1 MySQL を得る方法」節.
    • どのプラットフォームをサポートしているかは → 「2.2.5 MySQL がサポートする OS」節. Please note that not all supported systems are equally good for running MySQL on them. On some it is much more robust and efficient than others-see 「2.2.5 MySQL がサポートする OS」節 for details.
    • MySQL のいくつかのバージョンは、バイナリ、ソース両方の配布物があります。 最も新しい開発を見たいという人と、新しいコードをテストして我々を助けたいと いう人のために、現在のソースツリーへのアクセスも公開します。 どのバージョンを使用するのか、どのタイプを使用するかを決めるためには → 「2.2.6 使用すべき MySQL のバージョン」節. 迷った時はバイナリディストリビューションを使用してください。
    • バイナリとソースのインストールについては → 「2.2.10 Installing a MySQL Binary Distribution」節, と 「2.3 MySQL ソースディストリビューションのインストール」節. それぞれのセットには、あなたが出くわすかもしれない システムに特有の問題のセクションが含まれます。
    • インストール後に行うことの説明は → 「2.4 インストール後の設定とテスト」節. MySQL のインストールにおいて、バイナリまたはソース配布にかかわらず、 これらのプロシージャは適用します。

    2.1 Quick Standard Installation of MySQL

    2.1.1 Installing MySQL on Linux

    （訳注：もし RedHat 以外の Linux を使用しており、.rpm を、自分が使用している パッケージ管理システムの管理下におきたい場合、 alien : http://kitenet.net/programs/alien/ というツールを 使用します。これは RPM(Debian, Slackware) を自分が使用しているパッケージの形式に変換してくれます。）

    RPM を使用して MySQL をインストールすることを推奨します。 MySQL RPM は SuSE Linux 7.3 で作成していますが、 他の rpm と glibc をサポートしている Linux でも動作するでしょう。

    RPM file での問題, 例えば, ``Sorry, the host 'xxxx' could not be looked up'' に遭遇した場合には → 「2.6.1.1 Linux Notes for Binary Distributions」節.

    以下が使用するであろう RPM files です:

    • MySQL-server-VERSION.i386.rpm MySQL サーバー。 ただ単に他のマシン上で走っている MySQL サーバーに接続するだけなら、 これは不要でしょう。 Please note, that this package was called MySQL-VERSION.i386.rpm before MySQL 4.0.10.
    • MySQL-client-VERSION.i386.rpm MySQL クライアント標準プログラム。 このパッケージはほとんどの場合インストールすることになるでしょう。
    • MySQL-bench-VERSION.i386.rpm Tests and benchmarks. Requires Perl and msql-mysql-modules RPMs.
    • MySQL-devel-VERSION.i386.rpm 他の MySQL クライアント(perlモジュールのような)をコンパイルするのに必要な ライブラリーとインクルードファイルを含みます。
    • MySQL-shared-VERSION.i386.rpm This package contains the shared libraries (libmysqlclient.so*) which certain languages and applications need to dynamically load and use MySQL.
    • MySQL-embedded-VERSION.i386.rpm The embedded MySQL server library (MySQL 4.x and onwards only).
    • MySQL-VERSION.src.rpm 上記全てのソース。これは他のアーキテクチャ用に RPM を作成する場合にのみ必要でしょう。 (例えば Alpha や SPARC).

    To see all files in an RPM package, run: 

    shell> rpm -qpl MySQL-VERSION.i386.rpm

    インストールの最小の方法： 

    shell> rpm -i MySQL-server-VERSION.i386.rpm MySQL-client-VERSION.i386.rpm

    クライアントパッケージだけをインストール： 

    shell> rpm -i MySQL-client-VERSION.i386.rpm

    RPM はデータを `/var/lib/mysql' に保存します。 RPM は起動時にサーバーを立ちあげるように、`/etc/init.d/' に登録します。 (以前にインストールがされていて、前にインストールされた MySQL 起 動ファイルを何か変更している場合、それをコピーしておいた方がいいでしょう。 そうすればその変更を失うことはありません。)

    If you want to install the MySQL RPM on older Linux distributions that do not support init scripts in `/etc/init.d' (directly or via a symlink), you should create a symbolic link pointing to the old location before installing the RPM: 

    shell> cd /etc ; ln -s rc.d/init.d .

    However, all current major Linux distributions should already support this new directory layout as it is required for LSB (Linux Standard Base) compliance.

    RPM ファイルのインストール後は、mysqld デーモンが実行されていて、 MySQL の使用を開始することができます。 「2.4 インストール後の設定とテスト」節参照.

    うまくいかない場合、バイナリインストールの章でさらに情報を探すことができま す。 「2.2.10 Installing a MySQL Binary Distribution」節参照.

    2.1.2 Windows への MySQL のインストール

    Windows用の MySQLサーバ には，２つの配布形態があります。:

    1. バイナリ配布は，セットアッププログラムが含まれ，必要な全てのインストール作業を行い， あなたは直ぐにサーバをスタートさせることができます。
    2. The source distribution contains all the code and support files for building the executables using the VC++ 6.0 compiler. 「2.3.7 Windows Source Distribution」節参照.

    大雑把な言い方をすると，バイナリ配布を使用する方がいいでしょう。

    You will need the following:

    • A 32-bit Windows Operating System such as 9x, Me, NT, 2000, or XP. The NT family (NT, Windows 2000 and XP) permits running the MySQL server as a service. 「2.6.2.2 Starting MySQL on Windows NT, 2000 or XP」節参照. If you want to use tables bigger than 4G, you should install MySQL on an NTFS or newer filesystem. Don't forget to use MAX_ROWS and AVG_ROW_LENGTH when you create the table. 「6.5.3 CREATE TABLE 構文」節参照.
    • TCP/IP protocol support.
    • A copy of the MySQL binary or distribution for Windows, which can be downloaded from http://www.mysql.com/downloads/. Note: The distribution files are supplied with a zipped format and we recommend the use of an adequate FTP client with resume feature to avoid corruption of files during the download process.
    • A ZIP program to unpack the distribution file.
    • Enough space on the hard drive to unpack, install, and create the databases in accorandance with your requirements.
    • If you plan to connect to the MySQL server via ODBC, you will also need the MyODBC driver. 「8.3 MySQL ODBC サポート」節参照.

    2.1.2.1 Installing the Binaries

    1. If you are working on an NT/2000/XP server, logon as a user with administrator privileges.
    2. If you are doing an upgrade of an earlier MySQL installation, it is necessary to stop the server. If you are running the server as a service, use: 
      C:\> NET STOP MySQL
      Otherwise, use: 
      C:\mysql\bin> mysqladmin -u root shutdown
    3. On NT/2000/XP machines, if you want to change the server executable (e.g., -max or -nt), it is also necessary to remove the service: 
      C:\mysql\bin> mysqld-max-nt --remove
    4. Unzip the distribution file to a temporary directory.
    5. Run the `setup.exe' file to begin the installation process. If you want to install into another directory than the default `c:\mysql', use the Browse button to specify your preferred directory.
    6. Finish the install process.

    2.1.2.2 Preparing the Windows MySQL Environment

    Starting with MySQL 3.23.38, the Windows distribution includes both the normal and the MySQL-Max server binaries. Here is a list of the different MySQL servers you can use:

    Binary Description
    mysqld Compiled with full debugging and automatic memory allocation checking, symbolic links, InnoDB, and BDB tables.
    mysqld-opt Optimised binary with no support for transactional tables.
    mysqld-nt Optimised binary for NT/2000/XP with support for named pipes. You can run this version on Windows 9x/Me, but in this case no named pipes are created and you must have TCP/IP installed.
    mysqld-max Optimised binary with support for symbolic links, InnoDB and BDB tables.
    mysqld-max-nt Like mysqld-max, but compiled with support for named pipes.

    Starting from 3.23.50, named pipes are only enabled if one starts mysqld with --enable-named-pipe.

    All of the preceding binaries are optimised for the Pentium Pro processor but should work on any Intel processor >= i386.

    You will need to use an option file to specify your MySQL configuration under the following circumstances:

    • The installation or data directories are different from the default locations (`c:\mysql' and `c:\mysql\data').
    • You want to use one of these servers:
      • mysqld.exe
      • mysqld-max.exe
      • mysqld-max-nt.exe
    • You need to tune the server settings.

    Normally you can use the WinMySQLAdmin tool to edit the option file my.ini. In this case you don't have to worry about the following section.

    There are two option files with the same function: `my.cnf' and `my.ini'. However, to avoid confusion, it's best if you use only of one them. Both files are plain text. The `my.cnf' file, if used, should be created in the root directory of the C drive. The `my.ini' file, if used, should be created in the Windows system directory. (This directory is typically something like `C:\WINDOWS' or `C:\WINNT'. You can determine its exact location from the value of the windir environment variable.) MySQL looks first for the my.ini file, then for the `my.cnf' file.

    If your PC uses a boot loader where the C drive isn't the boot drive, your only option is to use the `my.ini' file. Also note that if you use the WinMySQLAdmin tool, it uses only the `my.ini' file. The `\mysql\bin' directory contains a help file with instructions for using this tool.

    Using notepad.exe, create the option file and edit the [mysqld] section to specify values for the basedir and datadir parameters: 

    [mysqld]
# set basedir to installation path, e.g., c:/mysql
basedir=the_install_path
# set datadir to location of data directory,
# e.g., c:/mysql/data or d:/mydata/data
datadir=the_data_path

    Note that Windows pathnames should be specified in option files using forward slashes rather than backslashes. If you do use backslashes, you must double them.

    If you would like to use a data directory different from the default of `c:\mysql\data', you must copy the entire contents of the `c:\mysql\data' directory to the new location.

    If you want to use the InnoDB transactional tables, you need to manually create two new directories to hold the InnoDB data and log files@-e.g., `c:\ibdata' and `c:\iblogs'. You will also need to add some extra lines to the option file. 「7.5.2 InnoDB 起動オプション」節参照.

    If you don't want to use InnoDB tables, add the skip-innodb option to the option file.

    Now you are ready to test starting the server.

    2.1.2.3 Starting the Server for the First Time

    Testing from a DOS command prompt is the best thing to do because the server displays status messages that appear in the DOS window. If something is wrong with your configuration, these messages will make it easier for you to identify and fix any problems.

    Make sure you are in the directory where the server is located, then enter this command: 

    C:\mysql\bin> mysqld-max --standalone

    You should see the following messages as the server starts up: 

    InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist:
InnoDB: a new database to be created!
InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200
InnoDB: Database physically writes the file full: wait...
InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280
InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280
InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created
InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: creating foreign key constraint system tables
InnoDB: foreign key constraint system tables created
011024 10:58:25  InnoDB: Started

    For further information about running MySQL on Windows, see 「2.6.2 Windows Notes」節.

    2.1.3 Installing MySQL on Mac OS X

    Beginning with MySQL 4.0.11, you can install MySQL on Mac OS X 10.2 ("Jaguar") using a Mac OS X PKG binary package instead of the binary tarball distribution. Please note that older versions of Mac OS X (e.g. 10.1.x) are not supported by this package!

    The package is located inside a disk image (.dmg) file, that you first need to mount by double-clicking its icon in the Finder. It should then mount the image and display its contents.

    NOTE: Before proceeding with the installation, please make sure that no other MySQL server is running!

    Please shut down all running MySQL instances before continuing by either using the MySQL Manager Application (on Mac OS X Server) or via mysqladmin shutdown on the command line.

    To actually install the MySQL PKG, double click on the package icon. This will launch the Mac OS Package Installer, which will guide you through the installation of MySQL.

    The Mac OS X PKG of MySQL will install itself into `/usr/local/mysql-<version>' and will also install a symbolic link `/usr/local/mysql', pointing to the new location. If a directory named `/usr/local/mysql' already exists, it will be renamed to `/usr/local/mysql.bak' first. Additionally, it will install the mysql grant tables by executing mysql_install_db after the installation.

    The installation layout is similar to the one of the binary distribution, all MySQL binaries are located in directory `/usr/local/mysql/bin'. The MySQL socket will be put into `/etc/mysql.sock' by default. 「2.2.7 インストールレイアウト」節参照.

    It requires a user account named mysql (which should exist by default on Mac OS X 10.2 and up).

    If you are running Mac OS X Server, you already have a version of MySQL installed:

    • Mac OS X Server 10.2-10.2.2 come with MySQL 3.23.51 installed
    • Mac OS X Server 10.2.3 and 10.2.4 ship with MySQL 3.23.53

    This manual section covers the installation of the official MySQL Mac OS X PKG only. Make sure to read Apple's help about installing MySQL (Run the "Help View" application, select "Mac OS X Server" help, and do a search for "MySQL" and read the item entitled "Installing MySQL").

    Especially note, that the pre-installed version of MySQL on Mac OS X Server is being started with the command safe_mysqld instead of mysqld_safe!

    If you previously used Marc Liyanage's MySQL packages for Mac OS X from http://www.entropy.ch, you can simply follow the update instructions for packages using the binary installation layout as given on his pages.

    If you are upgrading from Marc's version or from the Mac OS X Server version of MySQL to the official MySQL PKG, you also need to convert the existing MySQL privilege tables. 「2.5.2 バージョン 3.23 から バージョン 4.0 へのアップグレード」節参照.

    After the installation, you can start up MySQL by running the following commands in a terminal window. Please note that you need to have administrator privileges to perform this task! 

    shell> cd /usr/local/mysql
shell> sudo ./bin/mysqld_safe
(Enter your password)
(Press CTRL+Z)
shell> bg
(Press CTRL+D to exit the shell)

    You should now be able to connect to the MySQL server, e.g. by running `/usr/local/mysql/bin/mysql'.

    To enable the automatic startup of MySQL on bootup, you can download Marc Liyanage's MySQL StartupItem from the following location:

    http://www2.entropy.ch/download/mysql-startupitem.pkg.tar.gz

    We plan to add a StartupItem to the official MySQL PKG in the near future.

    Please note that installing a new MySQL PKG does not remove the directory of an older installation - unfortunately the Mac OS X Installer does not yet offer the functionality required to properly upgrade previously installed packages. After you have copied over the MySQL database files from the previous version and have successfully started the new version, you should consider removing the old installation files to save up disk space. Additionally, you should also remove older versions of the Package Receipt directories located in `/Library/Receipts/mysql-<version>.pkg'.

    2.2 General Installation Issues

    2.2.1 MySQL を得る方法

    現在のバージョンとダウンロードの指示についての情報は MySQL ウェブページ (http://www.mysql.com/) をチェックしてください。

    主なダウンロードミラーはここにあります: http://mirrors.sunsite.dk/mysql/. For a complete upto-date list of MySQL web/download mirrors, see http://www.mysql.com/downloads/mirrors.html. There you will also find information about becoming a MySQL mirror site and how to report a bad or out-of-date mirror.

    2.2.2 Verifying Package Integrity Using MD5 Checksums or GnuPG

    After you have downloaded the MySQL package that suits your needs and before you attempt to install it, you should make sure it is intact and has not been tampered with.

    MySQL AB offers two means of integrity checking: MD5 checksums and cryptographic signatures using GnuPG, the GNU Privacy Guard.

    2.2.3 Verifying the MD5 Checksum

    After you have downloaded the package, you should check, if the MD5 checksum matches the one provided on the MySQL download pages. Each package has an individual checksum, that you can verify with the following command: 

    shell> md5sum <package>

    Note, that not all operating systems support the md5sum command - on some it is simply called md5, others do not ship it at all. On Linux, it is part of the GNU Text Utilities package, which is available for a wide range of platforms. You can download the source code from http://www.gnu.org/software/textutils/ as well. If you have OpenSSL installed, you can also use the command openssl md5 <package> instead. A DOS/Windows implementation of the md5 command is available from http://www.fourmilab.ch/md5/.

    Example: 

    shell> md5sum mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz
155836a7ed8c93aee6728a827a6aa153
                mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz

    You should check, if the resulting checksum matches the one printed on the download page right below the respective package.

    Most mirror sites also offer a file named `MD5SUMS', which also includes the MD5 checksums for all files included in the `Downloads' directory. Please note however that it's very easy to modify this file and it's not a very reliable method! If in doubt, you should consult different mirror sites and compare the results.

    2.2.4 Signature Checking Using GnuPG

    A more reliable method of verifying the integrity of a package is using cryptographic signatures. MySQL AB uses the GNU Privacy Guard (GnuPG), an Open Source alternative to the very well-known Pretty Good Privacy (PGP) by Phil Zimmermann. See http://www.gnupg.org/ and http://www.openpgp.org/ for more information about OpenPGP/GnuPG and how to obtain and install GnuPG on your system. Most Linux distributions already ship with GnuPG installed by default.

    Beginning with MySQL 4.0.10 (February 2003), MySQL AB has started signing their downloadable packages with GnuPG. Cryptographic signatures are a much more reliable method of verifying the integrity and authenticity of a file.

    To verify the signature for a specific package, you first need to obtain a copy of MySQL AB's public GPG build key build@mysql.com. You can either cut and paste it directly from here, or obtain it from http://www.keyserver.net/. 

    Key ID:
pub  1024D/5072E1F5 2003-02-03
     MySQL Package signing key (www.mysql.com) <build@mysql.com>
Fingerprint: A4A9 4068 76FC BD3C 4567  70C8 8C71 8D3B 5072 E1F5

Public Key (ASCII-armored):

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBD4+owwRBAC14GIfUfCyEDSIePvEW3SAFUdJBtoQHH/nJKZyQT7h9bPlUWC3
RODjQReyCITRrdwyrKUGku2FmeVGwn2u2WmDMNABLnpprWPkBdCk96+OmSLN9brZ
fw2vOUgCmYv2hW0hyDHuvYlQA/BThQoADgj8AW6/0Lo7V1W9/8VuHP0gQwCgvzV3
BqOxRznNCRCRxAuAuVztHRcEAJooQK1+iSiunZMYD1WufeXfshc57S/+yeJkegNW
hxwR9pRWVArNYJdDRT+rf2RUe3vpquKNQU/hnEIUHJRQqYHo8gTxvxXNQc7fJYLV
K2HtkrPbP72vwsEKMYhhr0eKCbtLGfls9krjJ6sBgACyP/Vb7hiPwxh6rDZ7ITnE
kYpXBACmWpP8NJTkamEnPCia2ZoOHODANwpUkP43I7jsDmgtobZX9qnrAXw+uNDI
QJEXM6FSbi0LLtZciNlYsafwAPEOMDKpMqAK6IyisNtPvaLd8lH0bPAnWqcyefep
rv0sxxqUEMcM3o7wwgfN83POkDasDbs3pjwPhxvhz6//62zQJ7Q7TXlTUUwgUGFj
a2FnZSBzaWduaW5nIGtleSAod3d3Lm15c3FsLmNvbSkgPGJ1aWxkQG15c3FsLmNv
bT6IXQQTEQIAHQUCPj6jDAUJCWYBgAULBwoDBAMVAwIDFgIBAheAAAoJEIxxjTtQ
cuH1cY4AnilUwTXn8MatQOiG0a/bPxrvK/gCAJ4oinSNZRYTnblChwFaazt7PF3q
zIhMBBMRAgAMBQI+PqPRBYMJZgC7AAoJEElQ4SqycpHyJOEAn1mxHijft00bKXvu
cSo/pECUmppiAJ41M9MRVj5VcdH/KN/KjRtW6tHFPYhMBBMRAgAMBQI+QoIDBYMJ
YiKJAAoJELb1zU3GuiQ/lpEAoIhpp6BozKI8p6eaabzF5MlJH58pAKCu/ROofK8J
Eg2aLos+5zEYrB/LsrkCDQQ+PqMdEAgA7+GJfxbMdY4wslPnjH9rF4N2qfWsEN/l
xaZoJYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47gCvtgb6O1JHffOo2HfLmRDRi
Rjd1DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0Vhp3aFfWC4Ujfs3LU+hkAWzE
7zaD5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1BzELqX1DY7LwoPEb/O9Rkbf4fm
Le11EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfozBu74F47D8Ilbf5vSYHbuE5p
/1oIDznkg/p8kW+3FxuWrycciqFTcNz215yyX39LXFnlLzKUb/F5GwADBQf+Lwqq
a8CGrRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR1BeQauyPZbPDsDD9MZ1ZaSaf
anFvwFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55VjnSd1aQ9eQnUcXiL4cnBGoTbOW
I39EcyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQWg54tuUo0Ec8bsM8b3Ev42Lmu
QT5NdKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT27jWjJlMiJc+IWJ0mghkKHt92
6s/ymfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuwqp2H139pXGEkg0n6KdUOetdZ
Whe70YGNPw1yjWJT1IhMBBgRAgAMBQI+PqMdBQkJZgGAAAoJEIxxjTtQcuH17p4A
n3r1QpVC9yhnW2cSAjq+kr72GX0eAJ4295kl6NxYEuFApmr1+0uUq/SlsQ==
=YJkx
-----END PGP PUBLIC KEY BLOCK-----

    You can import this key into your public GPG keyring by using gpg --import. See the GPG documentation for more info on how to work with public keys.

    After you have downloaded and imported the public build key, now download your desired MySQL package and the corresponding signature, which is also available from the download page. The signature has the file name extension `.asc'. For example, the signature for `mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz' would be `mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz.asc'. Make sure that both files are stored in the same directory and then run the following command to verify the signature for this file: 

    shell> gpg --verify <package>.asc

Example:

shell> gpg --verify mysql-standard-4.0.10-gamma-pc-linux-i686.tar.gz.asc
gpg: Warning: using insecure memory!
gpg: Signature made Mon 03 Feb 2003 08:50:39 PM MET using DSA key ID 5072E1F5
gpg: Good signature from
     "MySQL Package signing key (www.mysql.com) <build@mysql.com>"

    The "Good signature" message indicates that everything is all right.

    For RPM packages, there is no separate signature - RPM packages actually have a built-in GPG signature and MD5 checksum. You can verify them by running the following command: 

    shell> rpm --checksig <package>.rpm

Example:

shell> rpm --checksig MySQL-server-4.0.10-0.i386.rpm
MySQL-server-4.0.10-0.i386.rpm: md5 gpg OK

    Note: If you are using RPM 4.1 and it complains about (GPG) NOT OK (MISSING KEYS: GPG#5072e1f5) (even though you have imported it into your GPG public keyring), you need to import the key into the RPM keyring first. RPM 4.1 does not use your GPG keyring (and GPG itself) anymore, but rather maintains its own keyring (because it's a system wide application and the GPG public keyring is user-specific file). To import the MySQL public key into the RPM keyring, please use the following command: 

    shell> rpm --import <pubkey>

Example:

shell> rpm --import mysql_pubkey.asc

    In case you notice that the MD5 checksum or GPG signatures do not match, first try to download the respective package one more time, maybe from another mirror site. If you repeatedly can not successfully verify the integrity of the package, please notify us about such incidents including the full package name and the download site you have been using at webmaster@mysql.com or build@mysql.com.

    2.2.5 MySQL がサポートする OS

    我々は GNU Autoconf を使用していますので、MySQL は POSIX スレッ ドと C++ コンパイラが動作する全ての新しいシステムに移植可能です。(クライ アントコードのコンパイルだけは C++ を必要としますが、スレッドは必要ではありません。) 我々は自身のソフトウェアを、最初に Sun Solaris (現在は 2.5 〜 2.7) 上と SuSE Linux Version 7.x で使用し開発します。

    多くの OS では、ネイティブスレッドは最新バージョ ンだけで動作することに注意してください。 MySQL は次の OS/スレッドパッケージの組み合わせで、コンパイルの 成功が報告されています。

    全てのプラットフォームが MySQL Server をちゃんと動作させるものではありません。 我々は以下のような評価基準に基づいて重要な要件を任せるに足るプラットフォームで あるかを判断しています。：

    • スレッドライブラリーの安定性。 プラットフォームが世間的にとてもよい評価を受けそれ以外が完全に動いたとしても、 MySQL が使用するスレッドライブラリーの動作が不安定ならば MySQL は安定して動作しないでしょう。
    • マルチプロセッサシステム上での SMP の優位性を引き出すための カーネルやスレッドライブラリの能力。 言い換えると、プロセスがスレッドを生成するときに、元のプロセスが動いていた CPU と異なる CPU 上でスレッドが動作することが可能であるべきです。
    • コンテキストスイッチングの多用を避け、頻繁なセマフォの取り合いによって 排他制御を行う場合のカーネル又はスレッドライブラリーのスレッド実行能力。 言い換えれば、CPUの切り替えに用いられるpthread_mutex_lock()の実装に 不安がある場合です。この場合は MySQL の実行をはなはだしく阻害します。 このことを考慮せずにいるとCPUを増設するほど MySQL の実行が遅くなる 事象を生じるでしょう。
    • 一般ファイルシステムの安定性とパフォーマンス
    • テーブルが大きい場合、大規模ファイルを完全に、そして効率よく扱うためのファ イルシステムの能力。
    • 使用プラットフォームに対する MySQL AB の経験。 使用しているプラットフォームについてよく知っていればプラットフォームに依存する 部分での最適化や改良をコンパイル時に行うことができます。 それから、MySQL の環境設定についてアドバイスも行えます。
    • 我々が内部的に行なう、コンフィグレーションと同様のテストのすべて。
    • The number of users that have successfully run MySQL on that platform in similar configurations. If this number is high, the chances of hitting some platform-specific surprises are much smaller.

    Based on the preceding criteria, the best platforms for running MySQL at this point are x86 with SuSE Linux 7.1, 2.4 kernel, and ReiserFS (or any similar Linux distribution) and SPARC with Solaris 2.7 or 2.8. FreeBSD comes third, but we really hope it will join the top club once the thread library is improved. We also hope that at some point we will be able to include all other platforms on which MySQL compiles, runs okay, but not quite with the same level of stability and performance, into the top category. This will require some effort on our part in cooperation with the developers of the OS/library components MySQL depends upon. If you are interested in making one of those components better, are in a position to influence their development, and need more detailed instructions on what MySQL needs to run better, send an e-mail to internals@lists.mysql.com.

    Please note that the preceding comparison is not to say that one OS is better or worse than the other in general. We are talking about choosing a particular OS for a dedicated purpose@-running MySQL, and compare platforms in that regard only. With this in mind, the result of this comparison would be different if we included more issues into it. And in some cases, the reason one OS is better than the other could simply be that we have put forth more effort into testing on and optimising for that particular platform. We are just stating our observations to help you decide on which platform to use MySQL on in your setup.

    2.2.6 使用すべき MySQL のバージョン

    make を行う前に決める事は、あなたが最新の開発リリースを使用するのか、 または最新の安定リリースを使用するのかです：

    • 通常、あなたが最初に MySQL を使い始める場合、またはバイナリ配布 がない他のシステムに MySQL を移植しようとする場合、 我々は安定リリース (現在は バージョン 3.23) の選択を 勧めます。注意: すべての MySQL リリースはそれぞれのリリー スの前に MySQL ベンチマークと広範囲なテストスイートでチェックされ ます。
    • そうでなくて、古いシステムで実行していてアップグレードしたいけれども、 開発版は試したくない場合は、あなたが使用している物と同じブランチ中の 最新のもの(あなたが使用している物より新しいバージョンの物)に アップグレードすべきです。 このバージョンでは、致命的なバグだけを修正し、 比較的安全で小さな変更を行っています。

    make 前の２番目の決定事項は、ソースディストリビューションとバイナリディ ストリビューションのどちらを使用するかです。多くの場合、バイナリがプラッ トフォーム用に存在していれば、おそらくバイナリディストリビューションを使 用すべきです。通常、それはソースディストリビューションよりも簡単にインス トールできます。

    次のケースでは、おそらくソースインストールの方が良いでしょう:

    • MySQL をどこか明示的な場所にインストールしたい場合(標準バイナリ ディストリビューションは、どこの場所でも ``実行準備'' ができていますが、もっ と柔軟にすることもできます)。
    • 異なるユーザの要求を満たすため、我々は２つのバイナリバージョンを提供してい ます; ひとつは、トランザクションテーブル処理なしでコンパイルされたもので、 もう一つは、トランザクション安全なテーブルのような、もっとも重要な拡張され たオプションで configure されたものです。両方のバージョンとも、同じソース ディストリビューションからコンパイルされます。すべてのネイティブ MySQL クライアントは両方の MySQL バージョンに接続できます。 拡張 MySQL バイナリディストリビューションは -max 接尾語が つけられていて、mysqld-max と同じオプションで configure されていま す。 「4.7.5 mysqld-max, An Extended mysqld Server」節参照. MySQL-Max RPM を使用したい場合は、最初に標準 MySQL RPM をイ ンストールすべきです。
    • mysqld を、標準バイナリディストリビューションには無いいくつかの拡 張機能付きで configure したい場合。使用できる代表的な拡張オプションは次 の通りです:
      • --with-innodb
      • --with-berkeley-db
      • --with-raid
      • --with-libwrap
      • --with-named-z-lib (This is done for some of the binaries)
      • --with-debug[=full]
    • デフォルトのバイナリディストリビューションは通常すべての文字セットをサポー トするようにコンパイルされていて、同じプロセッサファミリの多種のプロセッ サ上で動作します。 より速い MySQL サーバを得たい場合、必要な文字セットだけをサポー トするように再コンパイルでき、より良いコンパイラ(pgccのような)や、あなた のプロセッサ用により最適化されたコンパイラオプションを使用できます。
    • バグを発見して MySQL 開発チームにそれを報告する場合、バグを修正 するためにソースディストリビューションに適用する必要のあるパッチが、おそ らく得られるでしょう。
    • MySQL を作る C と C++ コードを読みたい(そして/または変更したい) 場合はソース配布を入手するべきです。ソースコードはいつでも究極のマニュア ルです。ソース配布はバイナリ配布よりも多くのテストと例も含んでいます。

    MySQL の命名法では、リリース番号は3つの数値とサフィックスからな ります。例えば、mysql-3.21.17-beta のようなリリース名は次のように 解釈されます:

    • 最初の数値(3)はファイル形式を表します。全てのバージョン 3 リリー スは同じファイルフォーマットを持ちます。
    • 2番目の数値(21)はリリースレベルです。通常は二つから選択します。一 つはリリース/安定ブランチで(現在は 23)、もう一つは開発ブランチです(現在は 4.0)。 通常は両方とも安定ですが、開発バージョンはきまぐれで、ドキュメントがなく、いくつかのシ ステムではコンパイルに失敗します。
    • 3番目の数値(17)はリリースレベル内のバージョン番号です。これは新し い配布の度に増加します。普通はあなたの選択したリリースレベルの最新バージョ ンを求めます。
    • サフィックス(beta)はリリースの安定レベルを表します:
      • alpha は、100% テストされていないいくつかの新しい大きなコードセク ションが存在することを示し、知られているバグは News 節に記述されています (通常はありません)。 「D MySQL Change History」節参照. 多くの alpha リリースには新しいコマ ンドと拡張もあります。 大きなコード変更を含む開発中のものは、alpha リリース上に現れます。しかし 全てリリース前にテストされます。それぞれの MySQL リリースには既知 のバグはありません。
      • beta は全ての新しいコードがテストされたことを意味します。大きな新 しいものは追加されません。知られているバグはありません。 alpha バージョンで、少なくとも一カ月間、致命的なバグが報告されなくて、古 いコマンドをより信頼できなくするような新しい機能を追加する計画がない時に、 alpha から beta にバージョンが変更されます。
      • gamma は beta がしばらくして、正しく動くように見えるものです。 小さな修正だけが追加されます。 これは多くの他の会社がリリースと呼ぶものです。
      • サフィックスがない場合は、多くの異なる場所で、プラットフォーム固有のバグ を除いてバグレポートなしでそのバージョンがしばらくの間動作していたことを 意味します。 致命的なバグ修正だけがリリースに適用されます。 これは我々が stable リリースと呼ぶものです。

    MySQL の全てのバージョンは、比較的安全に使用できることを確かめ るため、我々は標準テストとベンチマークを通して確認しています。標準テス トは以前に見つかった全てのバグをチェックするように拡張されるため、テスト スイートはより良く保持されます。

    全てのリリースは少なくても次のテストがされていることに注意してください:

    内部テストスイート
    これは顧客のための製品システムの一部です。多くのテーブルと何百というメガ バイトのデータを持っています。
    MySQL ベンチマークスイート
    これは一般的な範囲のクエリを実行します。これは、最適化の最新バッチが実際 にコードをより速く作れるかどうかを確認するテストでもあります。 「5.1.4 The MySQL Benchmark Suite」節参照.
    crash-me テスト
    これは、データベースがサポートしている機能と、その許容量と制限を決定しよ うとします。 「5.1.4 The MySQL Benchmark Suite」節参照.

    他のテストは我々の内部製品環境で最新の MySQL バージョンを我々が 少なくとも1つのマシンで使用することです。我々は動作のため 100ギガバイト 以上のデータを持ちます。

    2.2.7 インストールレイアウト

    この節では、バイナリとソース配布のインストールで生成されるディレクトリの デフォルトのレイアウトを説明します。

    バイナリ配布はアンパックすることによりインストールされ、インストール場所 はあなたが選択した場所(通常 `/usr/local/mysql')の中の次のディレクト リを選択し生成します:

    ディレクトリ ディレクトリの内容
    `bin' クライアントプログラム, mysqld サーバ
    `data' ログファイル, データベース
    `include' インクルード(ヘッダ)ファイル
    `lib' ライブラリ
    `scripts' mysql_install_db
    `share/mysql' エラーメッセージファイル
    `sql-bench' ベンチマーク

    ソース配布は configure しコンパイルした後にインストールされます。デフォ ルトではインストールステップは `/usr/local' 配下のファイルを次のサ ブディレクトリにインストールします:

    ディレクトリ ディレクトリの内容
    `bin' クライアントプログラムとスクリプト
    `include/mysql' インクルードファイル
    `info' Info 形式のドキュメント
    `lib/mysql' ライブラリ
    `libexec' mysqld サーバ
    `share/mysql' エラーメッセージファイル
    `sql-bench' ベンチマークと crash-me テスト
    `var' データベースとログファイル

    ソースインストールのレイアウトはバイナリインストールと次の点が異なります:

    • mysqld サーバは `bin' ではなく `libexec' ディレクトリにインストールされます。
    • データディレクトリは `data' ではなく `var' です。
    • mysql_install_db は `/usr/local/mysql/scripts' ではなく `/usr/local/bin' ディレクトリにインストールされます。
    • ヘッダーファイルのディレクトリは `include/mysql' で、 ライブラリのディレクトリは `lib/mysql' です。 `include' や `lib' ではありません。

    スクリプト `scripts/make_binary_distribution' を実行することにより、 コンパイルされたソースディストリビューションから、あなた自身のバイナリイン ストレーションを生成できます。

    2.2.8 アップデートがリリースされる方法と時

    MySQL は MySQL AB でかなり速く進化していて、我々はこれを他の MySQL ユーザに共有してもらいたいです。我々は、他の人が必要とし ていると思われるとても便利な機能を持った時に、リリースの作成を試みます。

    我々は、実装が簡単な機能を要求するユーザの手助けも試みます。我々は、我々 のライセンスユーザが求めるものにも注目し、特に我々の拡張 email サポート 顧客が求めるものに注目して、彼らの手助けを試みます。

    新しいリリースをダウンロードする必要はありません。News 節は、新しいリリー スが、あなたが本当に求める何かを持っているかどうかをあなたに教えます。 「D MySQL Change History」節参照.

    我々は MySQL の更新時は次のポリシーにしたがって行います：

    • それぞれのマイナーアップデートで、バージョン文字列中の最後の数値が増加し ます。主要な新機能や前のバージョンとのマイナーな非互換があった時には、バー ジョン文字列中の2番目の数値が増加します。ファイル形式が変更した時、最初 の数値が増加します。
    • 安定にテストされたリリースは年に約 1-2 回現れます。しかし小さなバグが見 つかった場合は、バグフィックスだけのリリースがリリースされます。
    • 作業中のリリースは約 1-8 週間毎に現れます。
    • いくつかのプラットフォームのためのバイナリ配布は我々によってメジャーリリー スから作られます。他の人が他のシステムのためにバイナリ配布を作りますが、 おそらく頻繁ではありません。
    • 通常、小さなバグを見つけて修正するとすぐに、有効なパッチを作ります。 They are posted to bugs@lists.mysql.com and will be added to the next release.
    • 危険ではないけれども困らされるバグには、MySQL ソースレポジトリに 変更を加え、次のリリースには修正されます。
    • 偶然、致命的なバグがリリース中にある場合、我々は新しいリリースを可能な限 りすぐに作ります。他の会社もそうしてもらいたいです。

    現在の安定リリースはバージョン 3.23 です; 我々はすでにバージョン 4.0 の開発に移行しています。 しかし、安定バージョンでもバグはまだ修正されます。 我々は、バグ修正と``行なわなければいけない''ことを無視するような、完全な 凍結を考えていません。``幾分かの凍結''とは、``ほとんど確実に既に動作して いるものに影響を与えない''小さなことを追加するかもしれないということを意 味します。

    MySQL uses a slightly different naming scheme from most other products. In general it's relatively safe to use any version that has been out for a couple of weeks without being replaced with a new version. 「2.2.6 使用すべき MySQL のバージョン」節参照.

    2.2.9 MySQL Binaries Compiled by MySQL AB

    サービスとして、我々 MySQL AB は MySQL のバイナリ配布を提供しています。 これらのコンパイルは MySQL AB 内部でおこなったり、我々にマシンの アクセスを提供してもらっている顧客のマシン上で行っています。

    これらの配布物は Build-tools/Do-compile で作成され (このスクリプトは scripts/make_binary_distribution を使用して ソースをコンパイルし tar.gz バイナリを作成します)、 以下のコンパイルオプションで調整されています。

    Binaries built on MySQL AB development systems:

    Linux 2.4.xx i386 with gcc 2.95.3
    CFLAGS="-O2 -mcpu=pentiumpro" CXX=gcc CXXFLAGS="-O2 -mcpu=pentiumpro -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static
    Linux 2.4.xx ia64 with ecc (Intel C++ Itanium Compiler 7.0)
    CC=ecc CFLAGS=-tpp1 CXX=ecc CXXFLAGS=-tpp1 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile
    Linux 2.4.xx alpha with ccc (Compaq C V6.2-505 / Compaq C++ V6.3-006)
    CC=ccc CFLAGS="-fast -arch generic" CXX=cxx CXXFLAGS="-fast -arch generic -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared --disable-shared
    Linux 2.2.xx sparc with egcs 1.1.2
    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared
    Linux 2.4.xx s390 with gcc 2.95.3
    CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static
    Sun Solaris 2.8 sparc with gcc 3.2
    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --with-named-curses-libs=-lcurses --disable-shared
    Sun Solaris 2.9 sparc with gcc 2.95.3
    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-curses-libs=-lcurses --disable-shared
    Sun Solaris 2.9 sparc with cc-5.0 (Sun Forte 5.0)
    CC=cc-5.0 CXX=CC ASFLAGS="-xarch=v9" CFLAGS="-Xa -xstrconst -mt -D_FORTEC_ -xarch=v9" CXXFLAGS="-noex -mt -D_FORTEC_ -xarch=v9" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --enable-thread-safe-client --disable-shared
    IBM AIX 4.3.2 ppc with gcc 3.2.1
    CFLAGS="-O2 -mcpu=powerpc -Wa,-many " CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared
    IBM AIX 5.1.0 ppc with gcc 3.2.1
    CFLAGS="-O2 -mcpu=powerpc -Wa,-many" CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --with-server-suffix="-pro" --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared --with-innodb
    HP-UX 10.20 pa-risc1.1 with gcc 3.1
    CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc CXXFLAGS="-DHPUX -I/opt/dce /include -felide-constructors -fno-exceptions -fno-rtti -O3 -fPIC" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-pthread --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC --disable-shared
    HP-UX 11.11 pa-risc2.0 with aCC (HP ANSI C++ B3910B A.03.33)
    CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared
    Apple Mac OS X 10.2 powerpc with gcc 3.1
    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared
    FreeBSD 4.7 i386 with gcc 2.95.4
    CFLAGS=-DHAVE_BROKEN_REALPATH ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared

    The following binaries are built on third-party systems kindly provided to MySQL AB by other users. Please note that these are only provided as a courtesy. Since MySQL AB does not have full control over these systems, we can only provide limited support for the binaries built on these systems.

    SCO Unix 3.2v5.0.6 i386 with gcc 2.95.3
    CFLAGS="-O3 -mpentium" LDFLAGS=-static CXX=gcc CXXFLAGS="-O3 -mpentium -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared
    Caldera Open Unix 8.0.0 i386 with CC 3.2
    CC=cc CFLAGS="-O" CXX=CC ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared
    Compaq Tru64 OSF/1 V5.1 732 alpha with cc/cxx (Compaq C V6.3-029i / DIGITAL C++ V6.1-027)
    CC="cc -pthread" CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all" CXX="cxx -pthread" CXXFLAGS="-O4 -ansi_alias -fast -inline speed -speculate all -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-prefix=/usr/local/mysql --with-named-thread-libs="-lpthread -lmach -lexc -lc" --disable-shared --with-mysqld-ldflags=-all-static
    SGI Irix 6.5 IP32 with gcc 3.0.1
    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared

    The following compile options have been used for binary packages MySQL AB used to provide in the past. These binaries are currently not being updated anymore, but the compile options are kept in here for reference purposes.

    Linux 2.2.x with x686 with gcc 2.95.2
    CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static --disable-shared --with-extra-charsets=complex
    SunOS 4.1.4 2 sun4c with gcc 2.7.2.1
    CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" ./configure --prefix=/usr/local/mysql --disable-shared --with-extra-charsets=complex --enable-assembler
    SunOS 5.5.1 (and above) sun4u with egcs 1.0.3a or 2.90.27 or gcc 2.95.2 and newer
    CC=gcc CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex --enable-assembler
    SunOS 5.6 i86pc with gcc 2.8.1
    CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex
    BSDI BSD/OS 3.1 i386 with gcc 2.7.2.1
    CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex
    BSDI BSD/OS 2.1 i386 with gcc 2.7.2
    CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex
    AIX 2 4 with gcc 2.7.2.2
    CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex

    上で示したオプション以外で最適化を施した方はだれでも、開発者向けの メーリングリストにポストできます。 internals@lists.mysql.com.

    RPM 配布では MySQL 3.22 を user-contributed としています。 3.22 をはじめ、いくつかの RPM パッケージは MySQL AB 製です。

    MySQL のデバッグバージョンをコンパイルしたい場合は、 --with-debug または --with-debug=full を上記の configure 行 に追加して、すべての -fomit-frame-pointer オプションを取り除いてく ださい。

    For the Windows distribution, please see 「2.1.2 Windows への MySQL のインストール」節.

    2.2.10 Installing a MySQL Binary Distribution

    See also 「2.1.2.1 Installing the Binaries」節, 「2.1.1 Installing MySQL on Linux」節, and 「8.4.7 Building Client Programs」節.

    MySQL の バイナリ配布プログラムをインストールする際は以下のツールが必要になります：

    • GNU gunzip。ソースを伸長するのに必要です。
    • ファイルアーカイバ tar。これもソースを展開するのに必要です。 GNU tarの動作は確認されています。Sun tarの使用には問題があります。

    Linux では別の形式、RPM-based(RPM Package Manager)配布も行われています。 「2.1.1 Installing MySQL on Linux」節参照.

    もしもこの問題にぶつかってしまった場合は mysqlbug を使用してください。 質問等は mysql@lists.mysql.com に送ってください。 問題点がバグに該当しなくても mysqlbug は情報を集めていますので解決の 手助けになることと思います。 mysqlbug を使用すれば問題の解決方法を得る 確率が増します。mysqlbug は解凍されたプログラムの `bin' 以下にあります。 「1.6.1.3 バグや問題を報告する方法」節参照.

    MySQL バイナリ配布プログラムのインストール及び 立ち上げまでに必要となる基本操作は以下の通りです。 

    shell> groupadd mysql
shell> useradd -g mysql mysql
shell> cd /usr/local
shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf -
shell> ln -s full-path-to-mysql-VERSION-OS mysql
shell> cd mysql
shell> scripts/mysql_install_db
shell> chown -R root  .
shell> chown -R mysql data
shell> chgrp -R mysql .
shell> bin/safe_mysqld --user=mysql &
or
shell> bin/mysqld_safe --user=mysql &
if you are running MySQL 4.x

    新しいユーザを追加するには bin/mysql_setpermission スクリプトを 使用できます。使用の際はDBIとMsql-Mysql-modulesの Perlモジュールをインストールする必要があります。

    より詳細な情報をここから示します。

    バイナリ配布のプログラムをインストールする際は以下に従ってください。 その後、 「2.4 インストール後の設定とテスト」節に進んでインストールの終了処理と動作試験を行ってください。

    1. バイナリ配布プログラムを解凍するためのディレクトリを用意してください。 そして、そこにバイナリ配布ファイルを置いてください。 以下の例では `/usr/local' にファイルを解凍し、`/usr/local/mysql' に MySQLをインストールします。（従って以下の例では操作するユーザが `/usr/local' に対して書き込み権限を持つことを前提としています。 もしも `/usr/local' への書き込みが禁じられている場合は rootとしてインストールを行う必要があります。
    2. プログラムの配布は以下のサイトから行ってください。 「2.2.1 MySQL を得る方法」節. MySQLのバイナリ配布は圧縮された tar 形式で行われており、 `mysql-VERSION-OS.tar.gz' のような形式の名前が付けられています。 ここで、VERSION はバージョン番号（例えば 3.21.15）を OS はプラットホームとなるOS（例えば pc-linux-gnu-i586）を示します。
    3. バイナリ配布ファイルに -max という表示があるものがありますが、 これはこのプログラムが transaction-safe 機能やその他の機能をサポート していることを示しています。 「4.7.5 mysqld-max, An Extended mysqld Server」節参照。 全てのバイナリプログラムは同じソースファイルからmakeされたものです。
    4. mysqldが動作するためのユーザとグループを作成してください。 
      shell> groupadd mysql
shell> useradd -g mysql mysql
      これらのコマンドは mysql グループと mysql ユーザを作成するものです。 useradd や groupadd というコマンドもありますが、 これらは使用プラットホームによって使い方が若干異なります。 また、adduser や addgroup と呼ばれる場合もあります。 mysql 以外のユーザやグループでも使用できます。
    5. インストール先のディレクトリを変更する場合は以下のようにします。 まずディレクトリを移動します。 
      shell> cd /usr/local
    6. 以下のように移動したディレクトリ上でプログラムの展開を行い インストールディレクトリを作成してください。 
      shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf -
shell> ln -s full-path-to-mysql-VERSION-OS mysql
      最初のコマンドで `mysql-VERSION-OS' という名前のディレクトリを作成します。 次のコマンドはそのディレクトリへのシンボリックリンクを作成し、 ユーザに単純な `/usr/local/mysql' という名前での利用を可能にします。
    7. 以下のようにインストールディレクトリへ移動します。 
      shell> cd mysql
      複数のファイルが mysql 以下のディレクトリに展開されているのが おわかりになると思います。 中でもインストールに重要な役目を果たすものは `bin' と `scripts' のサブディレクトリにあります。
      `bin'
      This directory contains client programs and the server You should add the full pathname of this directory to your PATH environment variable so that your shell finds the MySQL programs properly. 「F Environment Variables」節参照.
      `scripts'
      このディレクトリには mysql_install_db という mysql への アクセス管理を行うデータベースを初期化するためのスクリプトが置いてあります。
    8. mysqlaccessを使う必要があり、なおかつ、標準ディレクトリとは異なる場所に インストールを行いたい場合は、mysqlaccess が mysqlクライアントを 起動できるように環境設定を行う必要があります。 `bin/mysqlaccess'の18行目位にある以下のような行を変更してください。 
      $MYSQL     = '/usr/local/bin/mysql';    # path to mysql executable
      これを実際に mysql がインストールされているディレクトリに変更してください。 これをしないと mysqlaccess を使う際に Broken pipe エラーが発生します。
    9. 以下のようにすることによりアクセス管理データベースを作ることができます （初めてMySQLをインストールする時だけ必要）。 
      shell> scripts/mysql_install_db
      使用する MySQL のバージョンが 3.22.10 より古い場合はこの操作をする時に MySQL サーバが 立ち上がっている必要がありましたが、現在のバージョンでは必要ありません。
    10. Change ownership of binaries to root and ownership of the data directory to the user that you will run mysqld as: 
      shell> chown -R root  /usr/local/mysql/.
shell> chown -R mysql /usr/local/mysql/data
shell> chgrp -R mysql /usr/local/mysql/.
      最初のコマンドによって全てのファイルの owner 属性が root になります。 二行目のコマンドによってデータディレクトリ以下のファイル全ての owner 属性が mysql になります。 最後のコマンドによって全てのファイルの group 属性が mysql になります。
    11. PerlモジュールDBI、DBDのインストールが必要なら 「2.7 Perl Installation Comments」節の項をご覧下さい。
    12. MySQL を OS のブート時に自動的に起動したい場合は support-files/mysql.server を 貴方のシステムの的確な場所にコピーして使用できます。 より詳しい情報は support-files/mysql.server のスクリプト自体や 「2.4.3 MySQL の自動起動と自動停止」節 にあります。

    全てのファイルの展開とインストールが終了したら初期化と稼動試験を行います。

    以下のようにしてMySQLサーバを立ち上げることができます。 

    shell> bin/safe_mysqld --user=mysql &

    Now proceed to 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節, and 「2.4 インストール後の設定とテスト」節参照.

    2.3 MySQL ソースディストリビューションのインストール

    ソースインストールに取り掛かる前に、最初に我々のバイナリがあなたのプラット フォームに有効で、動作するかどうかをチェックしてください。我々は、我々のバ イナリが可能な限りのオプションで構築されていることを確認するために多くの努 力をしています。

    ソースから MySQL を作成しインストールするためには次のツールが必 要です:

    • GNU gunzip。配布の伸張のため。
    • 適正な tar。配布の展開のため。GNU tar は動くことが知られて います。Sun の tar は問題があることが知られています。
    • A working ANSI C++ compiler. gcc >= 2.95.2, egcs >= 1.0.2 or egcs 2.91.66, SGI C++, and SunPro C++ are some of the compilers that are known to work. libg++ is not needed when using gcc. gcc 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you only have gcc 2.7.x, you must upgrade your gcc to be able to compile MySQL. gcc 2.8.1 is also known to have problems on some platforms, so it should be avoided if a new compiler exists for the platform. MySQL 3.23.x のコンパイル時は、gcc >= 2.95.2 を推奨します。
    • 良い make プログラム。GNU make は常に推奨され、時々は必要 とされます。問題があれば GNU make 3.75 以上を試すことをお勧めしま す。

    -fno-exceptions オプションを解釈する gcc の最近のバージョ ンを使用している場合は、それを使用することがとても重要です。そう でなければ、ランダムにクラッシュするバイナリができあがるでしょう。また、 -fno-exceptions に加え、-felide-contructors と -fno-rtti を使用することをお奨めします。 疑いがある時は、次を行なってください: 

    
CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions \
       -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler \
       --with-mysqld-ldflags=-all-static

    多くのシステムで、これは速くて安定したバイナリを与えます。

    問題が起きたときは、mysql@lists.mysql.com に質問を投稿する時に mysqlbug を常に使用してください。問題がバグでないとして も、mysqlbug はあなたの問題を解決する助けになるであろうシステム情 報を収集します。mysqlbug を使用しないと、あなたの問題の解決を得る 可能性が小さくなります！ mysqlbug は、配布のアンパック後に `scripts' ディレクトリ内に見つけられます。 「1.6.1.3 バグや問題を報告する方法」節参照.

    2.3.1 素早いインストールの概要

    MySQL をソースからインストールするために行なわなければならない 基本的なコマンド: 

    shell> groupadd mysql
shell> useradd -g mysql mysql
shell> gunzip < mysql-VERSION.tar.gz | tar -xvf -
shell> cd mysql-VERSION
shell> ./configure --prefix=/usr/local/mysql
shell> make
shell> make install
shell> scripts/mysql_install_db
shell> chown -R root  /usr/local/mysql
shell> chown -R mysql /usr/local/mysql/var
shell> chgrp -R mysql /usr/local/mysql
shell> cp support-files/my-medium.cnf /etc/my.cnf
shell> /usr/local/mysql/bin/safe_mysqld --user=mysql &
or
shell> /usr/local/mysql/bin/mysqld_safe --user=mysql &
if you are running MySQL 4.x.

    InnoDB テーブルをサポートしたい場合は、/etc/my.cnf ファイルを編集し て、innodb_... で始まるパラメータの前の # 文字を削除すべきで す。 「4.1.2 `my.cnf' オプションファイル」節参照, and 「7.5.2 InnoDB 起動オプション」節.

    RPM ソースから開始する場合は： 

    shell> rpm --rebuild --clean MySQL-VERSION.src.rpm

    これはインストールできるRPMバイナリを作成します

    もし DBI と Msql-Mysql-modules Perl モジュールをインストールするなら、 bin/mysql_setpermission スクリプトが使用する新しいユーザーを 追加することができます。

    次にさらに詳細な説明を行ないます:

    ソース配布のインストールには、次のステップに従い、それから インストール 後の初期化とテストのために 「2.4 インストール後の設定とテスト」節 に進んでください。

    1. 配布をアンパックしたいディレクトリを選んで、そこに移ってください。
    2. 配布ファイルを 「2.2.1 MySQL を得る方法」節. にリストされたサイトの一つから得てください。
    3. MySQL で Berkeley DB テーブルの使用に興味がある場合、Berkeley DB ソースコー ドのパッチバージョンを入手する必要があります。処理の前に Berkeley DB テー ブルの章を読んでください。 「7.6 BDB or BerkeleyDB Tables」節参照. MySQL ソース配布は圧縮された tar アーカイブとして提供さ れ、`mysql-VERSION.tar.gz' のような名前を持ちます。ここで VERSION は 4.0.12 のような番号です。
    4. mysqld を実行するユーザーとグループを追加します: 
      shell> groupadd mysql
shell> useradd -g mysql mysql
      これらのコマンドは mysql グループと mysql ユーザを追加します。 useradd と groupadd 構文は、別のバージョンの UNIX 上では少し異なるでしょ う。adduser と addgroup と呼ばれることもあります。ユーザとグ ループは mysql の代わりに他の何かにすることもできます。
    5. カレントディレクトリに配布をアンパックしてください: 
      shell> gunzip < /path/to/mysql-VERSION.tar.gz | tar xvf -
      このコマンドは `mysql-VERSION' という名前のディレクトリを作成します。
    6. Change into the top-level directory of the unpacked distribution: 
      shell> cd mysql-VERSION
      注意: 現在のこのトップレベルディレクトリで MySQL の configure と build を行なう必要があります。別のディレクトリでは build できません。
    7. リリースを configure し、全てをコンパイルしてください: 
      shell> ./configure --prefix=/usr/local/mysql
shell> make
      configure の実行時、いくつかのオプションを指定できます。オプショ ンの一覧は ./configure --help を実行してください。 「2.3.3 典型的な configure オプション」節, さらに有用なオプションのいくつかに ついて議論しています。 configure が失敗して、援助を得るために mysql@lists.mysql.com にメー ルを送ろうとする場合、`config.log' から問題の解決の手助けにできると 考えられる行を含めてください。configure が異常終了する場合、 configure からの出力の最後の数行も含めてください。バグレポートは mysqlbug スクリプトを使用して投稿してください。 「1.6.1.3 バグや問題を報告する方法」節参照。 コンパイルが失敗する場合、いくらかのよくある問題での手助けのため、 「2.3.5 MySQL コンパイル時の問題」節 を参照してください。
    8. 全てをインストールしてください: 
      shell> make install
      このコマンドは root として実行する必要があります。
    9. MySQL 権限テーブルを生成してください(以前に MySQL をイ ンストールしていない時にだけ必要です): 
      shell> scripts/mysql_install_db
      注意: 3.22.10 より古い MySQL バージョンでは、 mysql_install_db 実行時に MySQL サーバが開始されましたが、 これはもはや真ではありません！
    10. バイナリのオーナーを root に、 データディレクトリの所有権を mysqld を実行するユーザに変更し てください: 
      shell> chown -R root  /usr/local/mysql
shell> chown -R mysql /usr/local/mysql/var
shell> chgrp -R mysql /usr/local/mysql
      最初のコマンドはファイルの owner 属性を root ユーザーに変更し、 2番目のコマンドは owner を mysql ユーザに変更し、 3番目のコマンドは group 属性を mysql グループに変更します。
    11. Perl DBI/DBD インタフェースのサポートをインストールしたい 場合、 「2.7 Perl Installation Comments」節 を見てください。
    12. MySQL をマシン起動時に自動的に開始したい場合、 support-files/mysql.server をシステムのスタートアップファイルがあ る場所にコピーしてください。さらなる情報は support-files/mysql.server スクリプト自身の中と、 「2.4.3 MySQL の自動起動と自動停止」節 に見つけられます。 「2.4.3 MySQL の自動起動と自動停止」節.

    全てがインストールされた後、配布の初期化とテストを行なうべきです。 

    shell> /usr/local/mysql/bin/safe_mysqld --user=mysql &

    コマンドがすぐに mysqld daemon ended エラーで失敗する場合、 `mysql-data-directory/'hostname'.err' ファイルになんらかの情報を 見つけることができます。 よくあることとして、すでに他の mysqld が 走っている場合などがあります。 「4.1.4 同一マシン上に複数の MySQL サーバーを走らせる」節参照.

    Now proceed to 「2.4 インストール後の設定とテスト」節.

    2.3.2 パッチの適用

    時々、パッチは、メーリング・リストに流されたり、または MySQL Web サイトのパッチエリア (http://www.mysql.com/downloads/patches.html) に置かれます。

    メーリング・リストからのパッチを適用するには、パッチが載っているメッセージを ファイルに保存して、あなたの MySQL ソース・ツリーの 一番上のディレクトリーに移動し、以下のようにコマンドを実行します： 

    shell> patch -p1 < patch-file-name
shell> rm config.cache
shell> make clean

    FTPサイトに置かれるパッチは、プレーンテキストファイルとして、 あるいは gzip で圧縮されたファイルとして頒布されます。 プレーンテキストのパッチの場合は、上に示したメーリングリストの パッチと同様に適用します。 圧縮されたパッチを適用するには、 MySQL ソース・ツリーの 一番上のディレクトリーに移動し、以下のようにコマンドを実行します： 

    shell> gunzip < patch-file-name.gz | patch -p1
shell> rm config.cache
shell> make clean

    それから通常のソースインストールの指示を ./configure ステップから 始めます。make install ステップ実行後、あなたの MySQL サー バを再起動します。

    make install を実行する前に、現在走っているサーバーを止める必要があるかもしれません。 ( mysqladmin shutdown で止めます ) いくつかのシステムでは、現在実行しているものを止めない限り、 新しいバージョンをインストールできないようになっています。

    2.3.3 典型的な configure オプション

    configure スクリプトは MySQL 配布をどのようにコンフィグ するかを制御するための多くの処理を提供します。典型的には、 configure コマンドラインにオプションを使用してこれを行ないます。 いくつかの環境変数を使用しても configure に影響を与えることができ ます。 「F Environment Variables」節参照. configure がサポートするオプションの一覧は、次のコマンドを 実行してください: 

    shell> ./configure --help

    一般的に使用される configure オプションのいくつかを以下に説明します:

    • MySQL クライアントライブラリとクライアントプログラムだけをコン パイルするには、--without-server オプションを使用してください: 
      shell> ./configure --without-server
      C++ コンパイラがなければ、mysql はコンパイルできません(これは C++ を要求するクライアントプログラムの一つです)。この場合、configure から C++ コンパイラをテストするコードを削除でます。それから ./configure を --without-server オプションつきで実行してく ださい。コンパイルステップは mysql の作成を試みますが、 `mysql.cc' についての警告は無視できます。(make が止まる場合、 エラーが発生しても残りの作成を継続するように make -k を試してくだ さい。)
    • 組み込み MySQL ライブラリ(libmysqld.a)を得たい場合は、 --with-embedded-server オプションを使用してください。(version 4.0以 上)
    • ログファイルとデータベースディレクトリを `/usr/local/var' 配下にお きたくない場合は、次の configure コマンドのうちのどれかを使用してく ださい: 
      shell> ./configure --prefix=/usr/local/mysql
shell> ./configure --prefix=/usr/local \
           --localstatedir=/usr/local/mysql/data
      最初のコマンドはインストールプレフィックスを変更し、デフォルトの `/usr/local' ではなく `/usr/local/mysql' 配下にインストールし ます。次のコマンドはデフォルトのインストールプレフィックスを保存しますが、 データベースディレクトリのデフォルト位置(通常は `/usr/local/var')を 上書きし、/usr/local/mysql/data に変更します。 MySQL をコンパイルした後でも、これらのオプションはオプションファイルで変更 できます 「4.1.2 `my.cnf' オプションファイル」節参照.
    • UNIX を使用していて、ソケットの位置をデフォルト位置(通常は `/tmp' または `/var/run')でなく他のどこかにしたい場合は、configure コマン ドを次のように使用します: 
      shell> ./configure --with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock
      ファイル名は絶対パスでなければなりません！ MySQL オプションファイルを使用することで、`mysql.sock' の場所をあとで 変更することもできます。 「A.4.5 MySQL ソケットファイル `/tmp/mysql.sock' を変更する方法、削除から守る方法」節参照.
    • 静的リンクされたプログラムをコンパイルしたい場合(例えば、バイナリ配布を 作成するため、もっと速くするため、いくつかの RedHat 配布での問題を回避す るため)は、次のように configure を実行します: 
      shell> ./configure --with-client-ldflags=-all-static \
           --with-mysqld-ldflags=-all-static
    • gcc を使用していて、libg++ や libstdc++ がインストー ルされていない場合、configure に gcc を C++ コンパイラとし て使用することを伝えてください: 
      shell> CC=gcc CXX=gcc ./configure
      gcc を C++ コンパイラとして使用する時、libg++ または libstdc++ のリンクは試みません。 This may be a good idea to do even if you have the above libraries installed, as some versions of these libraries have caused strange problems for MySQL users in the past. あなたが使用しているコンパイラによって、設定するいくつかの標準的な環境変数 があります:
      Compiler Recommended options
      gcc 2.7.2.1 CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors"
      egcs 1.0.3a CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti"
      gcc 2.95.2 CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti"
      pgcc 2.90.29 or newer CFLAGS="-O3 -mpentiumpro -mstack-align-double" CXX=gcc \ CXXFLAGS="-O3 -mpentiumpro -mstack-align-double -felide-constructors \ -fno-exceptions -fno-rtti"
      多くの場合、上述のオプションと次の configure 行オプションの使用によって、 最適な MySQL バイナリを得ることができます: 
      --prefix=/usr/local/mysql --enable-assembler \
--with-mysqld-ldflags=-all-static
      言い換えれば、すべての最近の gcc バージョン用には、完全な configure 行は次 のようなものになります: 
      CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \
-felide-constructors -fno-exceptions -fno-rtti" ./configure \
--prefix=/usr/local/mysql --enable-assembler \
--with-mysqld-ldflags=-all-static
      我々が MySQL Web サイト http://www.mysql.com/ 上で提供して いるバイナリは、完全に最適化されてコンパイルされ、多くのユーザに完全です。 「2.2.9 MySQL Binaries Compiled by MySQL AB」節参照。さらに速いバイナリを作成するために調整できることが いくつかありますが、これは上級ユーザ向けです。 「5.5.3 MySQL の速度に影響するコンパイルとリンク方法」節参照. コンパイラやリンカが共有ライブラリ `libmysqlclient.so.#' を生成でき ないというエラーになる場合、--disable-shared オプションを configure に与えることで、この問題を回避できます。この場合、 configure は共有ライブラリ `libmysqlclient.so.#' を作成しま せん。
    • 非 NULL 項目(すなわち、NULL が許されていない項目)に DEFAULT 項目値を使用しないように MySQL をコンフィグでき ます。これは、非 NULL 値を要求する全ての項目に値を明示的に指定し なければ、INSERT ステートメントはエラーを生成します。デフォルト値 の使用を抑えるには、次のように configure を実行します: 
      shell> CXXFLAGS=-DDONT_USE_DEFAULT_FIELDS ./configure
    • デフォルトでは、MySQL は ISO-8859-1 (Latin1) 文字セットを使用し ます。デフォルトセットを変更するには、--with-charset オプションを 使用します: 
      shell> ./configure --with-charset=CHARSET
      CHARSET は次のうちの一つです: big5, cp1251, cp1257, czech, danish, dec8, dos, euc_kr, gb2312, gbk, german1, hebrew, hp8, hungarian, koi8_ru, koi8_ukr, latin1, latin2, sjis, swe7, tis620, ujis, usa7, or win1251ukr. 「4.6.1 データとソートに使用されるキャラクター・セット」節参照. サーバとクライアント間で文字を変換したい場合は、 SET CHARACTER SET コマンドを調べるべきです。 「5.5.6 SET 構文」節参照. 警告: テーブルを生成した後に文字セットを変更する場合、 myisamchk -r -q --set-character-set=charset を全てのテーブルに実行する必要があります。 そうでないと、インデックスは正しくソートされません。(これは、MySQL のイ ンストール時、いくつかのテーブルの生成時、異なる文字セットを使用して MySQL の再コンフィグ時、そして再インストール時に発生します。) オプション --with-extra-charsets=LIST で、サーバ内に組み込むべき追加 文字セットを指定することができます。 ここで、LIST は空白で区切られた文字セットのリストです。 complex は動的にロードできないすべての文字を含み、all はバイ ナリにすべての文字セットを含みます。
    • デバッグコードつきで MySQL を構築するには、 --with-debug オプションを使用します: 
      shell> ./configure --with-debug
      これにより、いくつかのエラーを見つけられる安全なメモリ割り当てが含まれ、 何が発生しているかについての出力を提供します。 「E.1 MySQL server のデバッグ」節参照.
    • あなたのクライアントプログラムがスレッドを使用している場合、 MySQL クライアントライブラリを --enable-thread-safe-client configure オプションでスレッド安全用に コンパイルする必要があります。これは、スレッドアプリケーションがリンクす べき libmysqlclient_r ライブラリを生成します。 「8.4.8 スレッドクライアントを作る方法」節参照.
    • 固有のシステムに関係するオプションについては、この章より後のシステム固有 の節で見つけることができます。 「2.6 Operating System Specific Notes」節参照.

    2.3.4 開発ソースツリーからのインストール

    警告: 我々の新しいテストコードについて我々を手助けすることに興味 がある場合にだけ、この節を読むべきです。MySQL を得て、あなたのシ ステム上で実行したいだけの場合は、標準リリースディストリビューションを使 用すべきです(ソースまたはバイナリディストリビューション)。

    我々のもっとも新しい開発ソースツリーを得るには、次の手順に従ってください:

    1. Download BitKeeper from http://www.bitmover.com/cgi-bin/download.cgi. You will need Bitkeeper 3.0 or newer to access our repository.
    2. Follow the instructions to install it.
    3. After BitKeeper is installed, first go to the directory you want to work from, and then use one of the following commands to clone the MySQL version branch of your choice: To clone the 3.23 branch, use this command: 
      shell> bk clone bk://mysql.bkbits.net/mysql-3.23 mysql-3.23
      To clone the 4.0 branch, use this command: 
      shell> bk clone bk://mysql.bkbits.net/mysql-4.0 mysql-4.0
      To clone the 4.1 branch, use this command: 
      shell> bk clone bk://mysql.bkbits.net/mysql-4.1 mysql-4.1
      In the preceding examples the source tree will be set up in the `mysql-3.23/', `mysql-4.0/', or `mysql-4.1/' subdirectory of your current directory. If you are behind a firewall and can only initiate HTTP connections, you can also use BitKeeper via HTTP. If you are required to use a proxy server, simply set the environment variable http_proxy to point to your proxy: 
      shell> export http_proxy="http://your.proxy.server:8080/"
      Now, simply replace the bk:// with http:// when doing a clone. Example: 
      shell> bk clone http://mysql.bkbits.net/mysql-4.1 mysql-4.1
      The initial download of the source tree may take a while, depending on the speed of your connection - please be patient.
    4. You will need GNU make, autoconf 2.53 (or newer), automake 1.5, libtool 1.4, and m4 to run the next set of commands. Note that automake 1.7 or newer doesn't yet work. If you are using trying to configure MySQL 4.1 you will also need bison 1.75. Older versions of bison may report this error: sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded. Note: the maximum table size is not actually exceeded, the error is caused by bugs in these earlier bison versions. The typical command to do in a shell is: 
      cd mysql-4.0
bk -r get -Sq
aclocal; autoheader; autoconf; automake
(cd innobase ; aclocal; autoheader; autoconf; automake) # for InnoDB
(cd bdb/dist ; sh s_all ) # for Berkeley DB
./configure  # Add your favorite options here
make
      If you get some strange error during this stage, check that you really have libtool installed! A collection of our standard configure scripts is located in the `BUILD/' subdirectory. If you are lazy, you can use `BUILD/compile-pentium-debug'. To compile on a different architecture, modify the script by removing flags that are Pentium-specific.
    5. When the build is done, run make install. Be careful with this on a production machine; the command may overwrite your live release installation. If you have another installation of MySQL, we recommand that you run ./configure with different values for the prefix, with-tcp-port, and unix-socket-path options than those used for your production server.
    6. Play hard with your new installation and try to make the new features crash. Start by running make test. 「9.1.2 MySQL Test Suite」節参照.
    7. If you have gotten to the make stage and the distribution does not compile, please report it to bugs@lists.mysql.com. If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. However, if you execute aclocal and get a command not found error or a similar problem, do not report it. Instead, make sure all the necessary tools are installed and that your PATH variable is set correctly so that your shell can find them.
    8. After the initial bk clone operation to get the source tree, you should run bk pull periodically to get the updates.
    9. You can examine the change history for the tree with all the diffs by using bk sccstool. If you see some funny diffs or code that you have a question about, do not hesitate to send e-mail to internals@lists.mysql.com. Also, if you think you have a better idea on how to do something, send an e-mail to the same address with a patch. bk diffs will produce a patch for you after you have made changes to the source. If you do not have the time to code your idea, just send a description.
    10. BitKeeper has a nice help utility that you can access via bk helptool.
    11. Please note that any commits (bk ci or bk citool) will trigger the posting of a message with the changeset to our internals mailing list, as well as the usual openlogging.org submission with just the changeset comments. Generally, you wouldn't need to use commit (since the public tree will not allow bk push), but rather use the bk diffs method described previously.

    You can also browse changesets, comments and sourcecode online by browsing to e.g. http://mysql.bkbits.net:8080/mysql-4.1 For MySQL 4.1.

    The manual is in a separate tree which can be cloned with: 

    shell> bk clone bk://mysql.bkbits.net/mysqldoc mysqldoc

    2.3.5 MySQL コンパイル時の問題

    Solaris や Linux 上で gcc を使用した場合、一切警告無く 全ての MySQL プログラムがきれいに作れます。 他のシステムではインクルードファイルの違いから警告が出るかもしれません。 MIT-pthreads を使用した際の警告は 「2.3.6 MIT-pthreads に関して」節 を参照してください。 他の問題は、以下をチェックしてください。

    多くの問題の解決のために、再 configure が必要です。 あなたが再構成する必要があるならば、以下に気をつけてください：

    • もし configure を一度実行した後に実行するならば、 configure は 前に作った情報を利用します。この情報は `config.cache' に保存されます。 configure は起動時にこのファイルを探し、もし存在するならば、 その中の情報が正しい物として読み込みます。 これはあなたが再コンフィグするならば無効になります。
    • configure を実行するごとに、 make を実行してコンパイルしなければなりません。 しかし、最初に、前のビルドでできたオブジェクトを、消しておいてください。 なぜなら、違うコンフィグオプションにより生成されたからです。

    古いコンフィグやオブジェクトファイルの使用を防ぐため、 configure 前に以下のコマンドを実行してください： 

    shell> rm config.cache
shell> make clean

    こうするかわりに、make distclean としても構いません。

    以下に、 MySQL をコンパイルする際に起こりやすい問題をあげておきます：

    • `sql_yacc.cc' コンパイル時に、以下のようなエラーが出た場合、 メモリー、スワップが足りません： 
      Internal compiler error: program cc1plus got fatal signal 11
  or
Out of virtual memory
  or
Virtual memory exhausted
      この問題は、gcc がインライン展開で `sql_yacc.cc' をコンパイルするのに、 とても多くのメモリーを必要とするからです。 この場合、 configure を --with-low-memory オプション指定で実行します： 
      shell> ./configure --with-low-memory
      このオプションは、 gcc を使用しているなら -fno-inline オプションを コマンドラインに加え、gcc 以外ならば -O0 を加えます。 多くのメモリーとスワップを持っていない限りは、--with-low-memory オプションを使用すべきです。 この問題はけっこうなハードウェア構成でも起こることが知られています。 通常、 --with-low-memory オプションでこの問題は解決できます。
    • 標準では、configure は c++ という名前でコンパイラーを使用し、 GNU c++ は -lg++ を使ってリンクします。 もし gcc を使用しているならば、コンフィグ時に以下のような問題が出るかもしれません： 
      configure: error: installation or configuration problem:
C++ compiler cannot create executables.
      この問題は、g++, libg++ あるいは libstdc++ に関連したものです。 原因の一つとして考えられることは、 g++ を持っていないか、あるいは、 g++ はあっても libg++ か libstdc++ がないという事です。 `config.log' ファイルは c++ コンパイラが動作しなかった理由を記録しています！ この問題を解決するに当たり、あなたが持っている C++ コンパイラーの代わりに gcc を使用しても構いません。CXX 環境変数に "gcc -O3" としてみてください。 例えば： 
      shell> CXX="gcc -O3" ./configure
      これは gcc が g++ と同様に C++ ソースをコンパイルするので動きますが、 libg++ か libstdc++ が標準ではリンクされません。 他の解決方法は、もちろん、g++, libg++, libstdc++ をインストールすることです。 We would however like to recommend you to not use libg++ or libstdc++ with MySQL as this will only increase the binary size of mysqld without giving you any benefits. Some versions of these libraries have also caused strange problems for MySQL users in the past.
    • もし以下のエラーのどれかが起きた場合、 GNU make のバージョンを上げてください： 
      making all in mit-pthreads
make: Fatal error in reader: Makefile, line 18:
Badly formed macro assignment
  or
make: file `Makefile' line 18: Must be a separator (:
  or
pthread.h: No such file or directory
      Solaris と FreeBSD の make プログラムには問題があることが知られています。 GNU make Version 3.75 は動作確認されています。
    • もし C,C++ のためにフラグを与えたい場合、CFLAGS と CXXFLAGS 環境変数に フラグを追加してください。同様に、 CC と CXX にコンパイラー名を 与えることもできます。 例えば： 
      shell> CC=gcc
shell> CFLAGS=-O3
shell> CXX=gcc
shell> CXXFLAGS=-O3
shell> export CC CFLAGS CXX CXXFLAGS
      「2.2.9 MySQL Binaries Compiled by MySQL AB」節 にはフラグの定義がリストされています。 色々なシステム上で役に立つと思います。
    • 以下のようなエラーの場合、gcc コンパイラーをアップグレードしてください： 
      client/libmysql.c:273: parse error before `__attribute__'
      gcc 2.8.1 は動作することが確認されていますが、 gcc 2.95.2 以上をお勧めします。
    • mysqld コンパイル時に以下のようなエラーが出た場合、 configure が accept(), getsockname(), getpeername() の最後の引数を正しく検出していません： 
      cxx: Error: mysqld.cc, line 645: In this statement, the referenced
     type of the pointer value "&length" is "unsigned long", which
     is not compatible with "int".
new_sock = accept(sock, (struct sockaddr *)&cAddr, &length);
      これを修正するには、`config.h' ファイル(configure により作られる) を修正します。 いかのように： 
      /* Define as the base type of the last arg to accept */
#define SOCKET_SIZE_TYPE XXX
      XXX を size_t か int (あなたのオペレーティングシステムが依存している型)に変えます。 (configure すると毎回 `config.h' は作り直されるので、 この修正は configure する度に行わなければならないことに注意)
    • `sql_yacc.cc' ファイルは `sql_yacc.yy' から生成されます。 通常、 MySQL が既に生成されたコピーとともにあるので、 `sql_yacc.cc' ファイルを自分自身で作成することはありません。 しかし、以下のエラーの場合、再作成する必要があります： 
      "sql_yacc.yy", line xxx fatal: default action causes potential...
      これはあなたの yacc のバージョンが不十分であることを示しています。 bison (GNU 版 yacc) を代わりにインストールして使用する必要があります。
    • もし mysqld か MySQL クライアントをデバッグしたいなら、 configure を --with-debug オプション付きで実行します。 そしてコンパイルし、新しいクライアントライブラリーでクライアントをリンクします。 「E.2 Debugging a MySQL client」節参照.

    2.3.6 MIT-pthreads に関して

    このセクションではMIT-pthreadsを使っているさいに起こる問題についていくつか述べて います。

    Linux では、MIT-pthreads を使用してはならず、 LinuxThreads をインストールするべきです！ 「2.6.1 Linux Notes (All Linux Versions)」節参照.

    もしあなたのシステムが本来のスレッドのサポートを提供しなければ、あなたは、 MIT-pthreadsパッケージを使って、MySQL を構築する必要があります。 これにはほとんどのFreeBSDシステム、SunOS4.x,Solaris 2.4とそれ以前、ほかいくつか が含まれます。 「2.2.5 MySQL がサポートする OS」節参照.

    Note, that beginning with MySQL 4.0.2 MIT-pthreads are no longer part of the source distribution! If you require this package, you need to download it separately from http://www.mysql.com/Downloads/Contrib/pthreads-1_60_beta6-mysql.tar.gz

    After downloading, extract this source archive into the top level of the MySQL source directory. It will create a new subdirectory mit-pthreads.

    • ほとんどのシステム上では --with-mit-threads オプションで configure 実行することによって、 MIT-pthreadsが使われることを強制することができます。 
      shell> ./configure --with-mit-threads
      MIT-pthreadsを使う時、非ソースディレクトリで構築することはサポートされていませ ん。なぜなら、私たちはこのコードへ私たちの変更を最小にしたいからです。
    • MIT-pthreads が使われているかどうかチェックはサーバコードを configure するときに だけ行われます。もし、あなたが --without-server を使ってクライアントコードのみを ビルドすることを設定したならば、クライアントは MIT-othreads が使われているかいないか、 UNIXソケット接続がデフォルトで使われているのかわかりません。なぜなら UNIX ソケットは MIT-pthreads 下では動作しないからです。また、あなたはそのようなインスタンスでは -h または --host を使う必要があります。
    • MySQL が MIT-pthreads を使ってコンパイルされると、パフォーマンス上の問題のた めシステムロックはデフォルトでディスエーブルとされます。 --external-locking オプション を指定してサーバーに伝えることで、システムロックは使えるようになります。 This is only needed if you want to be able to run two MySQL servers against the same data files (not recommended).
    • ときどき(少なくともSolarisでは) pthread の bind() コマンドは何のエラーメッセージ なしにソケットへの bind に失敗することがあります。これは結果としてサーバーへの接続 失敗となります。たとえば、 
      shell> mysqladmin version
mysqladmin: connect to server at '' failed;
error: 'Can't connect to mysql server on localhost (146)'
      これを解決するために mysqld サーバーを終了して、再起動してください。こ れは私たちがサーバーダウンを強制して、すぐにリスタートさせようとしたときだけ起こ りました。
    • MIT-pthreads を使っていると、sleep() システムコールは SIGINT (break) では割り込みできません。 これは　mysqladmin --sleep を走らせているときにだけ 起こることがわかっています。 割り込みが発生してプロセスが停止する前に、あなたは終了させるための sleep() コールを待たなく てはなりません。
    • リンクしているとき(少なくともSolarisでは)、あなたはこのような warning メッセージ を受け取るでしょう。これらは無視してかまいません。 
      ld: warning: symbol `_iob' has differing sizes:
    (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4;
file /usr/lib/libc.so value=0x140);
    /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken
ld: warning: symbol `__iob' has differing sizes:
    (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4;
file /usr/lib/libc.so value=0x140);
    /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken
    • 他のいくつかの warnings もまた無視してかまいません。 
      implicit declaration of function `int strtoll(...)'
implicit declaration of function `int strtoul(...)'
    • 私たちはまだ MIT-pthread とともに動く readline を手に入れていません(これは必要では ないのですが、おそらく誰かには興味があるでしょう)。

    2.3.7 Windows Source Distribution

    You will need the following:

    Building MySQL

    1. Create a work directory (e.g., workdir).
    2. Unpack the source distribution in the aforementioned directory.
    3. Start the VC++ 6.0 compiler.
    4. In the File menu, select Open Workspace.
    5. Open the `mysql.dsw' workspace you find on the work directory.
    6. From the Build menu, select the Set Active Configuration menu.
    7. Click over the screen selecting mysqld - Win32 Debug and click OK.
    8. Press F7 to begin the build of the debug server, libs, and some client applications.
    9. When the compilation finishes, copy the libs and the executables to a separate directory.
    10. Compile the release versions that you want, in the same way.
    11. Create the directory for the MySQL stuff: e.g., `c:\mysql'
    12. From the workdir directory copy for the c:\mysql directory the following directories:
      • Data
      • Docs
      • Share
    13. Create the directory `c:\mysql\bin' and copy all the servers and clients that you compiled previously.
    14. If you want, also create the `lib' directory and copy the libs that you compiled previously.
    15. Do a clean using Visual Studio.

    Set up and start the server in the same way as for the binary Windows distribution. 「2.1.2.2 Preparing the Windows MySQL Environment」節参照.

    2.4 インストール後の設定とテスト

    初めて MySQLをインストールしたら(バイナリからでもソースからでもですが)、 サーバーを動作させるために、許可テーブルを初期化しなくてはなりません。 またマシンの起動時、停止時に、サーバーを自動で開始、停止することもできます。

    通常、許可テーブルのインストールとサーバーの開始は、 ソースディストリビューションなら以下のようにします： 

    shell> ./scripts/mysql_install_db
shell> cd mysql_installation_directory
shell> ./bin/safe_mysqld --user=mysql &

    バイナリディストリビューション(RPM または pkg パッケージではない)では次を 行ないます: 

    shell> cd mysql_installation_directory
shell> ./scripts/mysql_install_db
shell> ./bin/safe_mysqld --user=mysql &
or
shell> ./bin/mysqld_safe --user=mysql &
if you are running MySQL 4.x.

    これは、いくつかのデータベースを生成します。mysql データベースは全 てのデータベース権限を保持します。test データベースは MySQL をテストするために使用できます。そして、 mysql_install_db を実行したユーザの権限エントリと root ユー ザも生成します(パスワードはありません)。これは mysqld サーバの起動 も行ないます。

    mysql_install_db は古い権限テーブルを上書きしません。そのため、どの ような環境でも安全に実行できます。test データベースを持ちたくないな ら、mysqladmin -u root drop test で削除できます。

    テストは、MySQL のトップディレクトリーから簡単に実行できます。 バイナリ配布を使用する場合、これ(トップディレクトリ)は インストール先のディレクトリーになるでしょう(`/usr/local/mysql')。 ソース配布の場合、これは MySQL のソースディレクトリです。

    コマンドは本節といかに続く節で説明しますが、BINDIR は mysqladmin や safe_mysqld がインストールされたディレクトリを示します。 バイナリ配布を使用している場合、BINDIR はバイナリ配布の `bin' ディレクトリになります。 ソースからインストールした場合、BINDIR は、configure で特別指定しない限り、 `/usr/local/bin' です。 EXECDIR は mysqld サーバーのインストール先です。 バイナリ配布を使用している場合、これは BINDIR ディレクトリと同一になります。 ソースからインストールした場合、`/usr/local/libexec' です。

    テストについて以下に詳細に説明します:

    1. If necessary, start the mysqld server and set up the initial MySQL grant tables containing the privileges that determine how users are allowed to connect to the server. This is normally done with the mysql_install_db script: 
      shell> scripts/mysql_install_db
      通常、mysql_install_db の実行は初めて MySQL をインストール したあと一度だけ必要です。 すでにインストールされているものを アップグレードする際にはこの手順は飛ばせます。 （しかし、mysql_install_db は実に安全で、すでにテーブルが 存在している場合はいかなるテーブルも更新しません。したがって、 実行すべきかどうかわからない場合は、mysql_install_db を常に 走らせることができます） mysql_install_db は 6個のテーブルを作ります (user, db, host, tables_priv, columns_priv, func) mysql データベースに。 初期の権限状態についての説明は 「4.3.4 MySQL 権限許可の初期設定」節. これらの権限は MySQL root ユーザーに なんでもできるように許可し、そして、だれもが 'test' という名前か 'test_' ではじまる名前をもつ データベースを作成、使用できるように許可されています。 もし許可テーブルを設定していない場合、サーバーを起動時に以下のエラーが出ます： 
      mysqld: Can't find file: 'host.frm'
      バイナリ配布の MySQL では、もし MySQL を ./bin/safe_mysqld を実行しないで起動した場合に、このエラーがおきます! 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節. root で mysql_install_db を実行する必要があるとあなたは思うかもしれません。 しかし、 MySQL は root 以外のユーザーで起動できます。 データベースディレクトリがサーバーを起動したユーザに対して読み書きが許可されていれば良いのです。 MySQL を一般ユーザーで走らせる方法は 「A.3.2 一般ユーザで MySQL を動かす方法」節. もし mysql_install_db で問題が出たら、 「2.4.1 mysql_install_db 実行時の問題」節. を参照のこと。 mysql_install_db スクリプトを走らせるにはいくつか選択があります：
      • mysql_install_db を走らせる前に編集して、許可の初期状態を変更してもいいでしょう。 これは多くのマシンに同じ権限設定をして MySQL をインストールする際に 役立ちます。 この場合、いくつかの INSERT 構文を mysql.user と mysql.db テーブルにたいして追加するようにするだけですみます!
      • もしインストール後に許可を変更したい場合、 mysql -u root mysql で MySQL root ユーザーで接続して直接許可テーブルを変更する SQL 文を実行します。
      • すでに許可テーブルが作成された状態で、完全に許可テーブルを作成し直すことができます。 これはすでにインストールされたテーブルがある場合や、 mysql_install_db を編集した後にそう思うかもしれません。mysql_install_db.
      これらの選択については 「4.3.4 MySQL 権限許可の初期設定」節 からさらに情報が得られます。
    2. MySQL サーバーを以下のようにして起動します： 
      shell> cd mysql_installation_directory
shell> bin/safe_mysqld &
      サーバの起動に問題があれば、 「2.4.2 MySQL サーバー起動時の問題」節 を見てください。
    3. code{mysqladmin} でサーバーが走っているか確認します。 サーバーが立ち上がり接続を受け付けるか確認する簡単な方法を以下に示します： 
      shell> BINDIR/mysqladmin version
shell> BINDIR/mysqladmin variables
      例えば、mysqladmin version の出力はあなたのプラットフォームと MySQL のバージョンを出力します。 出力は以下の様にでます： 
      shell> BINDIR/mysqladmin version
mysqladmin  Ver 8.14 Distrib 3.23.32, for linux on i586
Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license.

Server version          3.23.32-debug
Protocol version        10
Connection              Localhost via Unix socket
TCP port                3306
UNIX socket             /tmp/mysql.sock
Uptime:                 16 sec

Threads: 1  Questions: 9  Slow queries: 0
Opens: 7  Flush tables: 2  Open tables: 0
Queries per second avg: 0.000
Memory in use: 132K  Max memory used: 16773K
      BINDIR/mysqladmin の使用方法は、--help オプションで起動することにより得られます。
    4. Verify that you can shut down the server: 
      shell> BINDIR/mysqladmin -u root shutdown
    5. サーバーをリスタートするには、safe_mysqld か mysqld を直接実行します。 例えば： 
      shell> BINDIR/safe_mysqld --log &
      safe_mysqld が失敗するなら、 MySQL のインストールディレクトリーから実行してみてください。 もしそれでも起動しないなら、 「2.4.2 MySQL サーバー起動時の問題」節 を参照のこと。
    6. いくつかの簡単なテストでサーバーが動いているか確認できます。 以下のようになります： 
      shell> BINDIR/mysqlshow
+-----------+
| Databases |
+-----------+
| mysql     |
+-----------+

shell> BINDIR/mysqlshow mysql
Database: mysql
+--------------+
|    Tables    |
+--------------+
| columns_priv |
| db           |
| func         |
| host         |
| tables_priv  |
| user         |
+--------------+

shell> BINDIR/mysql -e "SELECT host,db,user FROM db" mysql
+------+--------+------+
| host | db     | user |
+------+--------+------+
| %    | test   |      |
| %    | test_% |      |
+------+--------+------+
      他のプラットフォームで MySQL のパフォーマンスを比較するために `sql-bench' にベンチマークがあります。 `sql-bench/Results' ディレクトリには、他のデータベースやプラットフォームで ベンチを実行した結果があります。 全てのテストを実行するには、以下のようにします： 
      shell> cd sql-bench
shell> run-all-tests
      RPM バイナリ配布には `sql-bench' ディレクトリがありません。 (RPM のソース配布には含まれます) この場合、ベンチマークをインストールしなくてはなりません。 MySQL バージョン 3.22 のバイナリ配布から、 `mysql-bench-VERSION-i386.rpm' という名前で RPM パッケージを作っており、 これにはベンチマークのデータとコードが含まれます。 `tests' サブディレクトリでテストすることも可能です。 例えば、`auto_increment.tst' の実行は以下のようにします： 
      shell> BINDIR/mysql -vvf test < ./tests/auto_increment.tst
      The expected results are shown in the `./tests/auto_increment.res' file.

    2.4.1 mysql_install_db 実行時の問題

    mysql_install_db スクリプトの目的は、新しい MySQL 権限テー ブルを生成することです。他のデータには何も影響しません！ 既に MySQL 権限テー ブルをインストールしている場合は、何も行ないません！

    権限テーブルを再生成したい場合は、mysqld サーバが動作していれば、それを落 としてから、次のように行なってください: 

    mv mysql-data-directory/mysql mysql-data-directory/mysql-old
mysql_install_db

    この節では mysql_install_db を実行した際にでくわすかもしれない問題について述べます：

    mysql_install_db doesn't install the grant tables
    これは mysql_install_db が権限テーブルをインストールできなかった事のメッセージですが、 続いて以下のようにメッセージが出た場合： 
    starting mysqld daemon with databases from XXXXXX
mysql daemon ended
    この場合、注意深く log ファイルを調べてください！ エラーメッセージに出ている `XXXXXX' ディレクトリにログファイルがあり、 これに mysqld がなぜスタートしなかったか記されているはずです。 もし何が起こったかわからない場合、このログファイルを含んで mysqlbug を使用して バグレポートを投稿してください！ 「1.6.1.3 バグや問題を報告する方法」節参照.
    There is already a mysqld daemon running
    この場合、 mysql_install_db を実行する必要はありません。 mysql_install_db を実行するのは MySQL を初めてインストールした後、 たった一回だけです。
    Installing a second mysqld daemon doesn't work when one daemon is running
    これはすでに MySQL がインストールされており、 しかし新しいインストールを違うところに行おうとした場合に発生します。 (例えば、一度に二つのインストールを実行した場合など) 一般にこの問題は二つ目のサーバーを動いているサーバーと同じポート、ソケットを使用して起動しようとした場合に発生します。 この場合、Can't start server: Bind on TCP/IP port: Address already in use エラーメッセージか Can't start server : Bind on unix socket... エラーメッセージが出ます。 「4.1.3 同じマシンに多くのサーバをインストールする」節参照.
    You don't have write access to `/tmp'
    もしソケットファイルを標準の場所(`/tmp')に作成するための書き込み許可がないなら、 あるいは、一時ファイルを `/tmp' に作成できないなら、 mysql_install_db の実行時、あるいは mysqld の起動／使用時に エラーとなるでしょう。 違うディレクトリーにソケットファイルや一時ファイルを指定するには： 
    shell> TMPDIR=/some_tmp_dir/
shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysqld.sock
shell> export TMPDIR MYSQL_UNIX_PORT
    See 「A.4.5 MySQL ソケットファイル `/tmp/mysql.sock' を変更する方法、削除から守る方法」節. `some_tmp_dir' は書き込みが可能なディレクトリーを指定しなくてはなりません。 「F Environment Variables」節参照. この後、mysql_install_db を走らせ、サーバーを起動する事ができます： 
    shell> scripts/mysql_install_db
shell> BINDIR/safe_mysqld &
    mysqld crashes immediately
    もし RedHat バージョン 5.0 上で 2.0.7-5 より古い glibc を使用している場合、 全ての glibc パッチを当てなくてはなりません！ これに関しては MySQL メールのアーカイブに情報が多くあります。 http://lists.mysql.com/. Also, see 「2.6.1 Linux Notes (All Linux Versions)」節. mysqld を --skip-grant-tables 指定で起動することもできます。 そして以下のように mysql を使用して自分自身の手により許可を加えます： 
    shell> BINDIR/safe_mysqld --skip-grant-tables &
shell> BINDIR/mysql -u root mysql
    mysql から手動で mysql_install_db に書かれている SQL コマンドを実行します。 許可テーブルをサーバーに読み込ますためには、 mysqladmin flush-privileges か mysqladmin reload を実行します。

    2.4.2 MySQL サーバー起動時の問題

    トランザクションをサポートするテーブル(BDB, InnoDB)を使用しようとする場合、 最初に `my.cnf' ファイルを生成して、使用しようとするテーブル型の起動オプショ ンを設定すべきです。 「7 MySQL テーブル型」節参照.

    通常 mysqld サーバーの起動は、以下の三つの方法のうち一つで行います：

    mysqld デーモンの起動時に、デーモンはデータディレクトリにディレクトリを変えます。 ログファイルと pid (process ID) ファイルがこのディレクトリに書ける事、 そしてデータベースがこのディレクトリにある事を、デーモンは要求します。

    データディレクトリの場所は配布物のコンパイル時に指定されています。 mysqld があなたのシステム上にデータベースディレクトリを見つけれなかった場合、 サーバーは動きません。 mysqld を --help オプションで起動すれば mysqld の デフォルトのパスを知ることができますので、 サーバーが起動しない理由が違うパスを使用しているために起こっているかどうかがわかります。 パスが違う場合、mysqld のコマンドラインの引数に正しいパスを指定して、デフォルト値を 上書きすることが可能です。(これらオプションは safe_mysqld にも同様に使用できます)

    通常、MySQL がインストールされたディレクトリのベースディレクトリだけを mysqld に教えればいいはずです。 これは --basedir オプションを指定します。 --help オプションを使用すればパスの変更が確認できます。 (--help は必ず 最後に指定のこと) 　例えば： 

    shell> EXECDIR/mysqld --basedir=/usr/local --help

    パスの設定が思い通りに言ったことを確認したら、 --help オプションを外してサーバーを起動します。

    どの方法でサーバーを起動しても、もし起動に失敗すれば、ログファイルを確認してください。 なぜ失敗したか記録されています。ログファイルはデータベースディレクトリにあります。 (バイナリ配布の場合 `/usr/local/mysql/data' 、ソース配布の場合 `/usr/local/var'、 Windows では `\mysql\data\mysql.err' ) データベースディレクトリに `host_name.err' と `host_name.log' という ファイル (host_name はあなたのサーバー名) を探してください。 以下のようにしてそのファイルの最後の数行を確認します： 

    shell> tail host_name.err
shell> tail host_name.log

    ログファイル中に次のような何かを見つけた場合: 

    000729 14:50:10  bdb:  Recovery function for LSN 1 27595 failed
000729 14:50:10  bdb:  warning: ./test/t1.db: No such file or directory
000729 14:50:10  Can't init databases

    これは --bdb-recover 付きで mysqld が起動され、Berkeley DB がデータ ベースを復元しようとした時にログファイルに悪い何かを見つけたということを意 味します。継続を可能にするためには、古い Berkeley DB ログファイルをデータ ベースディレクトリから、あとで検査できる他の場所に移すべきです。ログファイ ルは `log.0000000001' (番号は時間の経つと増加します)と名付けられてい ます。

    BDB テーブルサポートで mysqld を実行していて、mysqld が起動時にコア ダンプする場合、BDB recover log にいくつかの問題の原因があり得ます。この場 合、mysqld を --bdb-no-recover で起動を試みることができます。 これで救える場合は、データディレクトリから全ての `log.*' ファイルを削 除し、そして mysqld を再び起動してみてください。

    以下のエラーの場合、他のプログラム（か他の mysqld サーバー）が mysqld が使用しようとしている TCP/IP ソケットを使っています： 

    Can't start server: Bind on TCP/IP port: Address already in use
  or
Can't start server : Bind on unix socket...

    他の mysqld サーバーが走っていないかを ps で確認します。 もし他のサーバーが起動していないなら、 telnet your-host-name tcp-ip-port-number コマンドを実行し、何回か RETURN キーをたたいてみてください。 もし、 telnet: Unable to connect to remote host: Connection refused のような エラーが出た場合、なにかが mysqld が使用しようとしているポートを既に使っています。 See 「2.4.1 mysql_install_db 実行時の問題」節 and 「4.1.4 同一マシン上に複数の MySQL サーバーを走らせる」節.

    もし mysqld がすでに走っている場合、以下のコマンドにてパスの設定を知ることができます： 

    shell> mysqladmin variables

    または 

    shell> mysqladmin -h 'your-host-name' variables

    If you get Errcode 13, which means Permission denied, when starting mysqld this means that you didn't have the right to read/create files in the MySQL database or log directory. In this case you should either start mysqld as the root user or change the permissions for the involved files and directories so that you have the right to use them.

    もし safe_mysqld がサーバーを起動しても接続できないようなら、 `/etc/hosts' ファイルに以下のような記述を持たせてください： 

    127.0.0.1       localhost

    この問題はスレッドライブラリーがなくて MySQL を MIT-pthreads を 使用するようにして作ったシステムにだけ起こります。

    mysqld を起動できない場合、問題を見つけるためにトレースファイルの作 成を試みることができます。 「E.1.2 Creating Trace Files」節参照.

    InnoDB テーブルを使用している場合、InnoDB 固有の起動オプションを参照してく ださい。 「7.5.2 InnoDB 起動オプション」節参照.

    BDB (Berkeley DB) テーブルを使用する場合は、BDB 固有の起動オプションに精通 すべきです。 「7.6.3 BDB startup options」節参照.

    2.4.3 MySQL の自動起動と自動停止

    mysql.server と safe_mysqld スクリプトは、システム起動時に自 動的にサーバを起動するために使用できます。mysql.server はサーバを停 止するためにも使用できます。

    mysql.server とスクリプトは start, stop 引数を指定することにより サーバーを起動、停止できます： 

    shell> mysql.server start
shell> mysql.server stop

    mysql.server は MySQL インストールディレクトリの `share/mysql' ディレクトリ、 または MySQL ソースツリーの `support-files' ディレクトリにあります。

    mysql.server はサーバーを起動時する前に MySQL がインストールされた ディレクトリにディレクトリを変え、safe_mysqld を起動します。 もし標準以外にインストールしているバイナリ配布を使用しているなら、 mysql.server を編集する必要があるかもしれません。 safe_mysqld を起動する前に正しいディレクトリに cd するように変更します。 safe_mysqld に他のオプションを与えるように mysql.server を変えても構いません。 他のユーザーで実行したい場合、この節の後で示すように、適切な user 行を `/etc/my.cnf' ファイルに追加してください。

    mysql.server stop はサーバーにシグナルを送ってサーバーを停止します。 You can also take down the server manually by executing mysqladmin shutdown.

    You need to add these start and stop commands to the appropriate places in your `/etc/rc*' files when you want to start up MySQL automatically on your server.

    On most current Linux distributions, it is sufficient to copy the file mysql.server into the `/etc/init.d' directory (or `/etc/rc.d/init.d' on older Red Hat systems). Afterwards, run the following command to enable the startup of MySQL on system bootup: 

    shell> chkconfig --add mysql.server

    As an alternative to the above, some operating systems also use `/etc/rc.local' or `/etc/init.d/boot.local' to start additional services on bootup. To start up MySQL using this method, you could append something like the following to it: 

    /bin/sh -c 'cd /usr/local/mysql ; ./bin/safe_mysqld --user=mysql &'

    グローバル設定ファイルである `/etc/my.cnf' に、 mysql.server の オプションを記述することも可能です。`/etc/my.cnf' ファイルは以下のような 記述になっています： 

    [mysqld]
datadir=/usr/local/mysql/var
socket=/var/tmp/mysql.sock
port=3306
user=mysql

[mysql_server]
basedir=/usr/local/mysql

    mysql.server スクリプトは次のオプションを理解します: datadir, basedir そして pid-file.

    次の表は、各起動スクリプトがオプションファイルからどのオプショングループを読み込むかを示しています:

    Script Option groups
    mysqld mysqld and server
    mysql.server mysql.server, mysqld, and server
    safe_mysqld mysql.server, mysqld, and server

    「4.1.2 `my.cnf' オプションファイル」節参照.

    2.5 MySQL のアップグレード/ダウングレード

    MySQL 形式とデータファイルは、MySQL が同じベースバージョ ンである限り、同じアーキテクチャ上の異なるバージョン間でいつでも移動でき ます。現在のベースバージョンは 3 です。MySQL の実行時に キャラクタ・セットが変更された場合(これはソート順も変更します)、全てのテーブル に myisamchk -r -q --set-character-set=charset を行なう必要があります。 そうしなければ、インデックスが正しい順になりません。

    もしあなたが神経質だったり新しいバージョンを恐れている場合、いつでもあな たの古い mysqld を mysqld-old-version-number のような何 かにリネームできます。もし新しい mysqld が予期せぬ何かを行った場 合、単純にそれをシャットダウンし、古い mysqld を再起動することが できます！

    アップグレード時には、もちろん、古いデータベースをバックアップもしておく べきです。

    アップグレード後、再コンパイルされたクライアントプログラムで、 Commands out sync や予期せぬコアダンプのような問題が起きる場合、 おそらく、プログラムのコンパイル時に古いヘッダやライブラリファイルを使用 したのでしょう。この場合、`mysql.h' ファイルと `libmysql.a' ラ イブラリが、新しい MySQL 配布からのものであるかどうかを確かめる ために、日付をチェックすべきです。もし違っていれば、プログラムを再コンパ イルしてください！

    もし新しい mysqld サーバーが起動できないとか、パスワード無しで 接続できないとか、いくつかの問題が発生した場合、以前のインストールでできた 古い `my.cnf' ファイルがあるかどうかを確認してください！ program-name --print-defaults で確認できます. もしこの出力が プログラムの名称以外の物を返した場合、有効になっている my.cnf ファイルが あります！

    新しいリリースの MySQL をインストールした場合に常に Msql-Mysql-modules を再構築、再インストールすることは いい考えです。すべての DBI スクリプトが MySQL の アップグレード後にコアダンプする兆候に気づいた場合は、特に そうしてください。

    2.5.1 Upgrading From Version 4.0 to Version 4.1

    In general what you have to do when upgrading to 4.1 from an earlier MySQL version:

    • Run the script mysql_fix_privilege_tables to generate the new password field that is needed for secure handling of passwords.

    The following is a more complete lists tell what you have to watch out for when upgrading to version 4.1;

    • Functions that return a DATE, DATETIME or TIME result is now fixed up when returned to the client. 
      mysql> SELECT cast("2001-1-1" as DATE)
    -> '2001-01-01'
    • All column and tables now have a character set, which shows up in SHOW CREATE TABLE and mysqldump. (MySQL 4.0.6 and above can read the new dump files, but not previous MySQL versions).
    • Timestamp is now returned as string of type 'YYYY-MM-DD HH:MM:DD'. If you want to have this as a number you should add +0 to the timestamp column. Different timestamp lengths are not supported.
    • If you are running multiple servers on the same windows machine, you should use a different --shared_memory_base_name option on all machines.

    Note that the table definition format (.frm) has changed slightly in 4.1. MySQL 4.0.11 can read the new .frm format but older version can not. If you need to go move tables from 4.1 to and earlier MySQL version you should use mysqldump. 「4.8.5 mysqldump, データベースとテーブルから、構造とデータをダンプ」節参照.

    2.5.2 バージョン 3.23 から バージョン 4.0 へのアップグレード

    In general what you have to do when upgrading to 4.0 from an earlier MySQL version:

    • Run the script mysql_fix_privilege_tables to add new privileges and features to the MySQL privilege tables.
    • Edit any MySQL startup scripts or configure files to not use any of the deprecated options listed below.
    • Convert your old ISAM files to MyISAM files with the command: mysql_convert_table_format database. Note that this should only be run if all tables in the given database is ISAM or MyISAM tables. If this is not the case you should run ALTER TABLE table_name TYPE=MyISAM on all ISAM tables.
    • Ensure that you don't have any MySQL clients that uses shared libraries (like the Perl Msql-Mysql-modules). If you have, you should recompile them as structures used in `libmysqlclient.so' have changed.

    MySQL 4.0 will work even if you don't do the above, but you will not be able to use the new security privileges that MySQL 4.0 and you may run into problems when upgrading later to MySQL 4.1 or newer. The ISAM file format still works in MySQL 4.0 but it's deprecated and will be disabled in MySQL 5.0.

    古いクライアントは、4.0 のサーバ と問題なく動作するはずです。

    Even if you do the above, you can still downgrade to MySQL 3.23.52 or newer if you run into problems with the MySQL 4.0 series. In this case you have to do a mysqldump of any tables using a full-text index and restore these in 3.23 (because 4.0 uses a new format for full-text index).

    次のリストは、バージョン 4.0 にアップグレードする際に気をつけなければなら ないことです;

    • MySQL 4.0 has a lot of new privileges in the mysql.user table. 「4.3.1 GRANT と REVOKE 構文」節参照. To get these new privileges to work, one must run the mysql_fix_privilege_tables script. Until this script is run all users have the SHOW DATABASES, CREATE TEMPORARY TABLES, and LOCK TABLES privileges. SUPER and EXECUTE privileges take their value from PROCESS. REPLICATION SLAVE and REPLICATION CLIENT take their values from FILE. If you have any scripts that creates new users, you may want to change them to use the new privileges. If you are not using GRANT commands in the scripts, this is a good time to change your scripts. In version 4.0.2 the option --safe-show-database is deprecated (and no longer does anything). 「4.2.3 セキュリティに関する mysqld の起動オプション」節参照. If you get access denied errors for new users in version 4.0.2, you should check if you need some of the new grants that you didn't need before. In particular, you will need REPLICATION SLAVE (instead of FILE) for new slaves.
    • The startup parameters myisam_max_extra_sort_file_size and myisam_max_extra_sort_file_size are now given in bytes (was megabytes before 4.0.3). External system locking of MyISAM/ISAM files is now turned off by default. One can turn this on by doing --external-locking. (For most users this is never needed).
    • The following startup variables/options have been renamed:
      From to.
      myisam_bulk_insert_tree_size bulk_insert_buffer_size
      query_cache_startup_type query_cache_type
      record_buffer read_buffer_size
      record_rnd_buffer read_rnd_buffer_size
      sort_buffer sort_buffer_size
      warnings log-warnings
      err-log --log-error (for mysqld_safe)
      The startup options record_buffer, sort_buffer and warnings will still work in MySQL 4.0 but are deprecated.
    • The following SQL variables have changed name.
      From To.
      SQL_BIG_TABLES BIG_TABLES
      SQL_LOW_PRIORITY_UPDATES LOW_PRIORITY_UPDATES
      SQL_MAX_JOIN_SIZE MAX_JOIN_SIZE
      SQL_QUERY_CACHE_TYPE QUERY_CACHE_TYPE
      The old names still work in MySQL 4.0 but are deprecated.
    • You have to use SET GLOBAL SQL_SLAVE_SKIP_COUNTER=# instead of SET SQL_SLAVE_SKIP_COUNTER=#.
    • Renamed mysqld startup options --skip-locking to --skip-external-locking and --enable-locking to --external-locking.
    • SHOW MASTER STATUS now returns an empty set if binary log is not enabled.
    • SHOW SLAVE STATUS now returns an empty set if slave is not initialised.
    • mysqld now has the option --temp-pool enabled by default as this gives better performance with some OS (Most notable Linux).
    • DOUBLE and FLOAT columns now honour the UNSIGNED flag on storage (before, UNSIGNED was ignored for these columns).
    • ORDER BY column DESC now always sorts NULL values first; in 3.23 this was not always consistent. Note: MySQL 4.0.11 restored the original behaviour.
    • SHOW INDEX has 2 columns more (Null and Index_type) than it had in 3.23.
    • CHECK, SIGNED, LOCALTIME and LOCALTIMESTAMP are now reserved words.
    • The result of all bitwise operators |, &, <<, >>, and ~ is now unsigned. This may cause problems if you are using them in a context where you want a signed result. 「6.3.5 Cast Functions」節参照.
    • Note: when you use subtraction between integer values where one is of type UNSIGNED, the result will be unsigned! In other words, before upgrading to MySQL 4.0, you should check your application for cases where you are subtracting a value from an unsigned entity and want a negative answer or subtracting an unsigned value from an integer column. You can disable this behaviour by using the --sql-mode=NO_UNSIGNED_SUBTRACTION option when starting mysqld. 「6.3.5 Cast Functions」節参照.
    • MATCH ... AGAINST (... IN BOOLEAN MODE) を使用するためには、 REPAIR TABLE table_name USE_FRM を実行してテーブルをリビルド する必要があります。 たとえ テーブルの型が MyISAM であったとしても。
    • LOCATE() と INSTR() はケース依存です。 もしいずれかの引数がバイナリ文字列ならば。Otherwise they are case-insensitive.
    • STRCMP() now uses the current character set when doing comparisons, which means that the default comparison behaviour now is case-insensitive.
    • HEX(string) は、与えられた `文字列' を、 16進数で表記しなおした `文字列' を返すようになりました。 もし、`数値'の16進表記を得たい場合は、 HEX() の引数は 数値にしなくてはなりません。 (訳注： 4.0ではこうなります. (EUC-JP) 
      mysql> select HEX("xyz"),HEX("あ"),HEX("16"),HEX(16);
+------------+-----------+-----------+---------+
| HEX("xyz") | HEX("あ") | HEX("16") | HEX(16) |
+------------+-----------+-----------+---------+
| 78797A     | A4A2      | 3136      | 10      |
+------------+-----------+-----------+---------+
      これが、3.23ではこうなっていました. 
      mysql> select HEX("xyz"),HEX("あ"),HEX("16"),HEX(16);
+------------+-----------+-----------+---------+
| HEX("xyz") | HEX("あ") | HEX("16") | HEX(16) |
+------------+-----------+-----------+---------+
| 0          | 0         | 10        | 10      |
+------------+-----------+-----------+---------+
      )
    • 3.23 では INSERT INTO ... SELECT は常に IGNORE が有効になっ ていました。4.0.1 では、IGNORE を記述しない場合、MySQL はエラーの場 合に停止します(そして、おそらくロールバックします)。
    • ！！！`safe_mysqld' は `mysqld_safe' に名前が変わりました！！！ For some time we will in our binary distributions include safe_mysqld as a symlink to mysqld_safe.
    • 古い C API 関数 mysql_drop_db, mysql_create_db, mysql_connect は、もう、サポートされなくなりました。 ただし、MySQL を CFLAGS=-DUSE_OLD_FUNCTIONS フラグでコンパイルすれば、まだ使うことはできます。 しかし、このフラグを使用する代わりに クライアントを新しい 4.0 API に変更する方が良いです。
    • MYSQL_FIELD 構造体では、 length と max_length が unsigned int から unsigned long に変更されました。 これを printf() 形式関数に使用する場合にいくつかの警告が出ること以 外は、問題は発生しません。
    • テーブルから全レコードを削除したくて、何レコードが削除されたかを気にしない 時には、TRUNCATE TABLE を使用すべきです。(なぜなら TRUNCATE TABLE は DELETE FROM table_name よりも速いからです)。
    • TRUNCATE TABLE や DROP DATABASE の実行時に、有効な LOCK TABLES やトランザクションがある場合、エラーになります。
    • BIGINT フィールドに値を格納する場合に整数を使用すべきです(MySQL 3.23 で行 なっていた文字列を使用する代わりに)。文字列でもまだ働きますが、整数の使用 の方がより効率的です。
    • SHOW OPEN TABLE のフォーマットが変更されました。
    • マルチスレッドのクライアントは、mysql_thread_init() と mysql_thread_end() を使用せねばなりません。 「8.4.8 スレッドクライアントを作る方法」節参照.
    • Perl DBD::mysql をコンパイルし直す場合は、 Msql-Mysql-modules version 1.2218 以上のものでなくてはなりません。 古い DBD モジュールは推奨されない drop_db() 呼び出しを使用している ためです。
    • RAND(seed) は、3.23 に比べて、より違ったランダムを返すようになりました。 これは RAND(seed) と RAND(seed+1) により違いがでるという事です。
    • The default type returned by IFNULL(A,B) is now set to be the more 'general' of the types of A and B. (The order is STRING, REAL or INTEGER).

    2.5.3 バージョン 3.22 から バージョン 3.23 へのアップグレード

    MySQL バージョン 3.23 は新しい MyISAM 型のテーブルと、 古い ISAM 型のテーブルをサポートします。 バージョン 3.23 を使用する際、古いテーブル(ISAM) を変換する必要はありません。 デフォルトでは、新しく作られるテーブルが MyISAM 型になります。 (これは mysqld を --default-table-type=isam オプションで 起動することにより、変更できます)。 ISAM テーブルを MyISAM に変更するには、 ALTER TABLE table_name TYPE=MyISAM を使用するか、mysql_convert_table_format perl スクリプトを使用します。

    バージョン 3.22 と バージョン 3.21 のクライアントは問題なく バージョン 3.23 サーバーで動作します。

    以下に、バージョン 3.23 にアップグレードするときに、注目する必要があるものを列挙します：

    • tis620 文字セットを使用しているすべてのテーブルを myisamchk -r または REPAIR TABLE で fix する必要があります。
    • シンボリックリンクされたデータベースに対し DROP DATABASE を行なう場 合は、リンクとオリジナルデータベースが削除されます。(3.22 では configure が readlink システムコールを検出しないため、これは起りません。)
    • OPTIMIZE TABLE は現在、MyISAM テーブルだけに動作します。他 のテーブル型については、ALTER TABLE を使用して、テーブルを最適化で きます。OPTIMIZE TABLE の間は、テーブルは他のスレッドからロックされ ます。
    • MySQL クライアント mysql は現在、デフォルトで --no-named-commands (-g) オプションで起動されます。このオプションは --enable-named-commands (-G) で無効にできます。これは、非互換問題を 引き起こす場合があります。たとえば、セミコロン無しの named command を使用 する SQL スクリプトです！ 長い形式のコマンドは行頭でまだ動作します。
    • Date functions that work on parts of dates (like MONTH()) will now return 0 for 0000-00-00 dates. (MySQL 3.22 returned NULL.)
    • german 文字ソート順を使用する場合、ソート順についていくつか変更され ているので、isamchk -r ですべてのテーブルを修復する必要があります！
    • IF のデフォルトの戻り値型は現在両方の引数に依存します。最初の引数だけではありません。
    • AUTO_INCREMENT は負数では働きません。 この理由は、負数は -1 から 0 へのラッピング時に問題を引き起こすためです。 MyISAM の AUTO_INCREMENT は現在、低レベルの部分で処理され、以 前よりとても速いです。MyISAM テーブルでは、テーブルからいくつかのレコード を削除したとしても、古い数値は再利用されません。
    • CASE, DELAYED, ELSE, END, FULLTEXT, INNER, RIGHT, WHEN は 予約語になりました。
    • FLOAT(X) は本当の浮動小数点型になりました。桁数固定の値ではありません。
    • DECIMAL(length,dec) 宣言時、length 引数はもはや符号や小数点の場所を含みません。
    • TIME 文字列は以下のフォーマットのいずれかでなければなりません： [[[DAYS] [H]H:]MM:]SS[.fraction] か [[[[[H]H]H]H]MM]SS[.fraction].
    • LIKE は、同一文字の比較 '=' ルールを使用して、 比較を行うようになりました。 もし古い比較方法にするならば、 MySQL を CXXFLAGS=-DLIKE_CMP_TOUPPER フラグでコンパイルします。
    • REGEXP は、通常の文字列(非 binary) では、ケース非依存になりました。
    • MyISAM テーブル(.MYI) の検査・修復には、CHECK TABLE を使用するか、myisamchk を使用します。 isamchk は ISAM(.ISM) テーブル用に使用します。
    • もし、バージョン 3.22 と バージョン 3.23 の間で互換性を持たせて mysqldump を行いたいならば、 --opt や --all オプションを mysqldump に指定してはいけません。
    • 全ての DATE_FORMAT() をチェックしてください。 各フォーマット文字の前には `%' 文字が必要になりました。 (MySQL 3.22 バージョン以降ではこの文法が許されます。)
    • mysql_fetch_fields_direct が関数になり (今まではマクロだったのが)、 MYSQL_FIELD 型ではなく MYSQL_FIELD ポインター型を返します。
    • mysql_num_fields() は、 MYSQL* object をもはや使うことができません。 (これは今、 MYSQL_RES* を引数に取る関数になりました)。 代わりに、 mysql_field_count() を使用すべきです。
    • MySQL バージョン 3.22 では, SELECT DISTINCT ... の出力は ほとんどいつもソートされました。 3.23 では, ソートを行った結果を得るには GROUP BY か ORDER BY を使用しなくてはなりません。
    • もし、一致するレコードが無かった場合、SUM() は 0 の代わりに NULL を返すようになりました。 これは ANSI SQL 準拠です。
    • NULL 値での AND や OR は現在 0 ではなく NULL を返します。 これは主に、NOT NULL = NULL として、AND/OR 式上で NOT を使用するクエリに影響します。LPAD() と RPAD() は 長さ引数よりも長い場合、結果文字列は短くなります。

    2.5.4 バージョン 3.21 から バージョン 3.22 へのアップグレード

    バージョン 3.21 と バージョン 3.22 の間には互換性に影響する変更はありません。

    DATE 型のフィールドを持たせて作成した新しいテーブルは、 日付の格納に新しい方法を使用することだけが、唯一の落とし穴です。 これらの新しいフィールドに古いバージョンの mysqld からアクセスすることはできません。

    MySQL バージョン 3.22 インストール後、新しいサーバを開始して、 mysql_fix_privilege_tables スクリプトを実行すべきです。これは GRANT コマンドを使用するために必要な権限を追加します。これを忘れ ると、ALTER TABLE 、CREATE INDEX、DROP INDEX を 使用しようとした時に Access denied になります。 MySQL root ユーザがパスワードを要求する場合、 mysql_fix_privilege_tables への引数としてそれを与えてください。

    C API インタフェース mysql_real_connect() は変更されました。この 関数を呼び出す古いクライアントプログラムを持っている場合は、新しい db 引数に 0 を置く(またはより速い接続のために db 要 素を送るようにクライアントをコーディングしなおす)必要があります。 mysql_real_connect() を呼び出す前に mysql_init() を呼ばなくてはなりません！ この変更は、MYSQL の構造体にオプションを保存するための 新しい mysql_options() 関数を有効にします。

    mysqld 変数 key_buffer は key_buffer_size に名前が 変わりました。しかし、まだ前の名前もスターとアップファイル中で使用できま す。

    2.5.5 バージョン 3.20 から バージョン 3.21 へのアップグレード

    既に バージョン 3.20.28 より前のバージョンが稼働していて、バージョン 3.21.x に変更したい場合は、 次を行なう必要があります:

    safe_mysqld --old-protocol で mysqld 3.21 サーバを起動すれ ば、バージョン 3.20 配布からのクライアントでそれを使用できます。この場合、新しいク ライアント関数 mysql_errno() はサーバのエラーは何も返さず、 CR_UNKNOWN_ERROR だけを返します (ただしクライアントのエラーについ ては働きます)。そして サーバは古い password() チェックを新しいものの代わ りに使用します。

    mysqld に --old-protocol オプションを使わない場合、 次の変更をする必要があります:

    • 全てのクライアントコードは再コンパイルする必要があります。ODBC を使用し ている場合は新しい MyODBC 2.x ドライバを入手する必要があります。
    • mysql.user テーブル内の password フィールドを CHAR(16) に変換するために、スクリプト scripts/add_long_password を実行する必要があります。
    • 全てのパスワードは mysql.user テーブル内に再配置する必要がありま す(31ビットパスワードの代わりに、62ビットを得るために)。
    • テーブル形式は変更されていないので、どのテーブルも変換する必要はありませ ん。

    MySQL バージョン 3.20.28 とそれ以降は、クライアントに影響を及ぼさずに、新 しい user テーブル形式を処理することができます。バージョン 3.20.28 より前の MySQL バージョンを持っている場合は、user テーブルを変換 すると、パスワードはその上ではもう働きません。安全のため、最初に少なくと も バージョン 3.20.28 にアップグレードし、それから バージョン 3.21.x に アップグレードすべきです。

    新しいクライアントコードは バージョン 3.20.x mysqld サーバで動作するので、 もし バージョン 3.21.x で問題があった場合は、クライアントをもう一度再コンパイルする必 要はなく、古い バージョン 3.20.x サーバを使用することができます。

    mysqld に --old-protocol オプションを使用しない場合、古い クライアントはエラーメッセージを発します: 

    ERROR: Protocol mismatch. Server Version = 10 Client Version = 9

    新しい Perl インタフェース DBI/DBD は古い mysqlperl インタフェースもサポートします。mysqlperl を使用する場合に行う必 要のある変更は、connect() 関数の引数の変更だけです。新しい引数は: host, database, user, password (user と password 引数の順番が変更されました)。 「8.2.2 The DBI Interface」節参照.

    次の変更は古いアプリケーションでのクエリに影響します:

    • HAVING は現在 ORDER BY 節より前になければいけません。
    • LOCATE() へのパラメータは交換されました。
    • 新しい予約語がいくつかあります。最も注意すべきは DATE, TIME そして TIMESTAMP です。

    2.5.6 他のアーキテクチャへのアップグレード

    もし、MySQL バージョン 3.23 を使用しているならば、 違うアーキテクチャのマシンに、.frm, .MYI,.MYD ファイルを コピーすることが出来ます。 ただし、両者間で、同じ浮動小数点のフォーマットをサポートしている場合に限ります。 (MySQL はどのようなバイト交換にも気をつけます)。

    現在 MySQL ISAM データファイルとインデックスファイル ( `*.ISD' と `*.ISM' ファイル) はアーキテクチャ依存で、 いくつかのケースでは OS 依存です。 アプリケーションを、現在のマシンとは異なるアーキテクチャ/OS を 持つ他のマシンに移したい場合は、単純にファイルを他のマシンにコピーするこ とでデータベースを移行しようとすべきではありません。mysqldump を 使用すべきです。

    デフォルトでは mysqldump は、完全な SQL ステートメントファイルを 生成します。それからそのファイルを他のマシンへ転送し、mysql クラ イアントへの入力として与えることができます。

    有効なオプションが何かを見るためには、mysqldump --help を試してく ださい。データを MySQL のより新しいバージョンに移す場合、速くコ ンパクトなダンプを得るために、より新しいバージョンで mysqldump --opt を使用すべきです。

    ２つのマシン間でデータベースを移動する最も簡単な (しかし最も速くはない) 方法は、データベースが置かれているマシン上で次のコマンドを実行することで す: 

    shell> mysqladmin -h 'other hostname' create db_name
shell> mysqldump --opt db_name \
        | mysql -h 'other hostname' db_name

    遅いネットワーク上でリモートマシンからデータベースをコピーしたい場合は、 次を使用できます: 

    shell> mysqladmin create db_name
shell> mysqldump -h 'other hostname' --opt --compress db_name \
        | mysql db_name

    You can also store the result in a file, then transfer the file to the target machine and load the file into the database there. For example, you can dump a database to a file on the source machine like this: 

    shell> mysqldump --quick db_name | gzip > db_name.contents.gz

    (The file created in this example is compressed.) データベースの中身を含んでいるファイルを、目的のマシンに転送して、次のコ マンドを実行してください: 

    shell> mysqladmin create db_name
shell> gunzip < db_name.contents.gz | mysql db_name

    データベース転送を実行するために、mysqldump と mysqlimport も使用できます。大きなテーブルでは、これは単純な mysqldump の使用 よりもとても速いです。次に示すコマンドでは、DUMPDIR は mysqldump からの出力を格納するために使用するディレクトリの完全な パス名を表わしています。

    まず、出力ファイルのためのディレクトリを作成して、データベースをダンプし ます: 

    shell> mkdir DUMPDIR
shell> mysqldump --tab=DUMPDIR db_name

    それから、DUMPDIR ディレクトリ内のファイルを目的のマシン上の対応 するディレクトリに転送し、MySQL にファイルをロードします: 

    shell> mysqladmin create db_name           # create database
shell> cat DUMPDIR/*.sql | mysql db_name   # create tables in database
shell> mysqlimport db_name DUMPDIR/*.txt   # load data into tables

    mysql データベースのコピーも忘れないでください。それは承認テーブ ル (user, db, host) が格納されるためです。 mysql データベースをその場所に置くまで、新しいマシン上では MySQL root ユーザとしてコマンドを実行する必要があります。

    新しいマシン上へ mysql データベースを導入した後、サーバが承認テー ブル情報を再ロードするために、mysqladmin flush-privileges を実行してください。

    2.6 Operating System Specific Notes

    2.6.1 Linux Notes (All Linux Versions)

    以下の注意は、glibc に関して、MySQL をあなた自身で作成す るシチュエーションだけに適用されます。Linux を x86 マシンで実行する場合、 多くの場合は我々のバイナリを使用した方が良いです。我々は glibc の 最良パッチバージョンと我々のバイナリをリンクします。我々は最良のコンパイラ オプションでそれを作成し、高負荷サーバについて適切になるように試みています。 以下のテキストを読んで、何をあなたがやるべきかについて迷った時は、あなたの 必要にかなうかどうかをみるために、我々のバイナリをまず試してください。そし て、我々のバイナリが十分でないとわかった後にだけ、あなた自身の作成について 考えてください。この場合、それについての評価します。そのため、次回にはより 良いバイナリを作成できます。典型的なユーザについて、そして、多くの同時接続 と 2G Bytes 制限を超えるテーブルを設定する場合でも、多くの場合、我々のバイナリ は最良の選択です。

    Linux では MySQL は LinuxThreads を使用します。 もし glibc2 を持たない古い Linux を使用している場合、 MySQL のコンパイルの前に、 LinuxThreads をインストールしなければなりません。 LinuxThreads は http://www.mysql.com/downloads/os-linux.html. から得ることが できます。

    注意: 我々は SMP システム上での Linux 2.2.14 と MySQL で奇妙な問 題を経験しました; SMP システムの場合、Linux 2.4 ASAP にアップグレードする ことをお勧めします！ これを行なうことで、あなたのシステムはより速くより安 定するでしょう！

    注意: 2.1.1 以前の glibc バージョンは pthread_mutex_timedwait 処理に致命的なバグがあります。これは INSERT DELAYED を行なう時に使用されます。glibc をアップグレードする 前に INSERT DELAYED は使用しないようにお奨めします。

    1000以上の同時接続を使用する予定であれば、LinuxThreads にいくつかの変更 をして、再コンパイルし、MySQL を新しい `libpthread.a' を使用するように再リ ンクする必要があります。`sysdeps/unix/sysv/linux/bits/local_lim.h' 内の PTHREAD_THREADS_MAX を 4096 に増加し、 `linuxthreads/internals.h' 中の STACK_SIZE を 256 KB に減少させてください。注意: STACK_SIZE がデフォルトの 2MB である 場合、MySQL は 600-1000 程度の接続で安定でなくなります。

    MySQL が十分なファイルをオープンまたは接続できないという問題を 得た場合、十分なファイルを操作するように構築された Linux を持っていない ということです。

    Linux 2.2 以降では、割り当てられたファイル記述子の数を次のようにしてチェッ クできます: 

    cat /proc/sys/fs/file-max
cat /proc/sys/fs/dquot-max
cat /proc/sys/fs/super-max

    16M 以上のメモリがある場合は、次のような何かを起動スクリプト(SuSE では `/etc/init.d/boot.local')に追加すべきです: 

    echo 65536 > /proc/sys/fs/file-max
echo 8192 > /proc/sys/fs/dquot-max
echo 1024 > /proc/sys/fs/super-max

    上記は、root でコマンドラインからも実行できますが、この場合、コンピュータ をリブートすると古い制限が使われます。

    You can also run the preceding commands from the command-line as root, but these settings will be lost the next time your computer reboots.

    Alternatively, you can set these parameters on bootup by using the sysctl tool, which is used by many Linux distributions (SuSE has added it as well, beginning with SuSE Linux 8.0). Just put the following values into a file named `/etc/sysctl.conf': 

    # Increase some values for MySQL
fs.file-max = 65536
fs.dquot-max = 8192
fs.super-max = 1024

    `/etc/my.cnf' にも追加すべきです: 

    [safe_mysqld]
open-files-limit=8192

    上記は MySQL に、最大 8192 接続/ファイルを生成することを許可します。

    The STACK_SIZE constant in LinuxThreads controls the spacing of thread stacks in the address space. It needs to be large enough so that there will be plenty of room for the stack of each individual thread, but small enough to keep the stack of some threads from running into the global mysqld data. Unfortunately, the Linux implementation of mmap(), as we have experimentally discovered, will successfully unmap an already mapped region if you ask it to map out an address already in use, zeroing out the data on the entire page, instead of returning an error. So, the safety of mysqld or any other threaded application depends on the "gentleman" behaviour of the code that creates threads. The user must take measures to make sure the number of running threads at any time is sufficiently low for thread stacks to stay away from the global heap. With mysqld, you should enforce this "gentleman" behaviour by setting a reasonable value for the max_connections variable.

    If you build MySQL yourself and do not want to mess with patching LinuxThreads, you should set max_connections to a value no higher than 500. It should be even less if you have a large key buffer, large heap tables, or some other things that make mysqld allocate a lot of memory, or if you are running a 2.2 kernel with a 2G patch. If you are using our binary or RPM version 3.23.25 or later, you can safely set max_connections at 1500, assuming no large key buffer or heap tables with lots of data. The more you reduce STACK_SIZE in LinuxThreads the more threads you can safely create. We recommend the values between 128K and 256K.

    多くの同時接続を使用したい場合は、fork 爆弾攻撃を避けようとして、子供の fork や複製について、プロセスにペナルティを課すという、バージョン 2.2 カー ネルの "機能" に悩まされるでしょう。これにより、あなたが並行クライアントの 数を増加するようには、MySQL がスケールしません。シングル CPU システムでは、 とても遅いスレッド生成で明らかにこれが見られます。これは、MySQL への接続に 長い時間(1分程度)が掛かり、それを切断するのにも長い時間掛かるということを 意味します。複数 CPU システムでは、クライアント数の増加に従って、クエリ速 度が徐々に落ちていくのが観測されました。問題の解決を見つけようとする処理の 中で、我々のユーザからカーネルパッチを受け取りました。我々はいくつかの限定 されたテストで、このパッチが MySQL のスケーラビリティを非常に改善した結果 を得ました。このパッチはここにあります http://www.mysql.com/Downloads/Patches/linux-fork.patch. We have now done rather extensive testing of this patch on both development and production systems. It has significantly improved MySQL performance without causing any problems and we now recommend it to our users who are still running high-load servers on 2.2 kernels. This issue has been fixed in the 2.4 kernel, so if you are not satisfied with the current performance of your system, rather than patching your 2.2 kernel, it might be easier to just upgrade to 2.4, which will also give you a nice SMP boost in addition to fixing this fairness bug.

    We have tested MySQL on the 2.4 kernel on a 2-CPU machine and found MySQL scales much better@-there was virtually no slowdown on queries throughput all the way up to 1000 clients, and the MySQL scaling factor (computed as the ratio of maximum throughput to the throughput with one client) was 180%. We have observed similar results on a 4-CPU system@-virtually no slowdown as the number of clients was increased up to 1000, and 300% scaling factor. So for a high-load SMP server we would definitely recommend the 2.4 kernel at this point. We have discovered that it is essential to run mysqld process with the highest possible priority on the 2.4 kernel to achieve maximum performance. This can be done by adding renice -20 $$ command to safe_mysqld. In our testing on a 4-CPU machine, increasing the priority gave 60% increase in throughput with 400 clients.

    We are currently also trying to collect more info on how well MySQL performs on 2.4 kernel on 4-way and 8-way systems. If you have access such a system and have done some benchmarks, please send a mail to docs@mysql.com with the results - we will include them in the manual.

    There is another issue that greatly hurts MySQL performance, especially on SMP systems. The implementation of mutex in LinuxThreads in glibc-2.1 is very bad for programs with many threads that only hold the mutex for a short time. On an SMP system, ironic as it is, if you link MySQL against unmodified LinuxThreads, removing processors from the machine improves MySQL performance in many cases. We have made a patch available for glibc 2.1.3 to correct this behaviour (http://www.mysql.com/Downloads/Linux/linuxthreads-2.1-patch).

    With glibc-2.2.2 MySQL version 3.23.36 will use the adaptive mutex, which is much better than even the patched one in glibc-2.1.3. Be warned, however, that under some conditions, the current mutex code in glibc-2.2.2 overspins, which hurts MySQL performance. The chance of this condition can be reduced by renicing mysqld process to the highest priority. We have also been able to correct the overspin behaviour with a patch, available at http://www.mysql.com/Downloads/Linux/linuxthreads-2.2.2.patch. It combines the correction of overspin, maximum number of threads, and stack spacing all in one. You will need to apply it in the linuxthreads directory with patch -p0 </tmp/linuxthreads-2.2.2.patch. We hope it will be included in some form in to the future releases of glibc-2.2. In any case, if you link against glibc-2.2.2 you still need to correct STACK_SIZE and PTHREAD_THREADS_MAX. We hope that the defaults will be corrected to some more acceptable values for high-load MySQL setup in the future, so that your own build can be reduced to ./configure; make; make install.

    We recommend that you use the above patches to build a special static version of libpthread.a and use it only for statically linking against MySQL. We know that the patches are safe for MySQL and significantly improve its performance, but we cannot say anything about other applications. If you link other applications against the patched version of the library, or build a patched shared version and install it on your system, you are doing it at your own risk with regard to other applications that depend on LinuxThreads.

    If you experience any strange problems during the installation of MySQL, or with some common utilties hanging, it is very likely that they are either library or compiler related. If this is the case, using our binary will resolve them.

    一つ知られている問題として、バイナリ配布を libc5 の古い Linux システム (RedHat 4.x , Slackware 3.6 以下, Debian 1.3 bo 以下など) で使用すると、ホスト名解決の致命的なエラーが出ます. 「2.6.1.1 Linux Notes for Binary Distributions」節参照.

    LinuxThreads を使用している場合、最低３つのプロセスが走ります。 これらは実スレッドで、一つは LinuxThreads マネージャーのために、 一つは接続のハンドルに、もうひとつはアラームとシグナルのハンドルです。

    注意: linux カーネルと linuxthread ライブラリはデフォルトでは 1024 スレッ ドだけ持つことができます。これはパッチを適用していないシステム上では MySQL への接続は最大 1021 だけであるということを意味します。ページ http://www.volano.com/linuxnotes.html はこの制限をどのように回避 するかの情報が含まれています。

    もし mysqld デーモンプロセスが ps などでみると死んでいるようであれば, 通常これは MySQL バグか、壊れたテーブルを持っています。 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

    Linux 上で、mysqld が SIGSEGV シグナルで死んだ時にコアダンプを得たい場合、 --core-file オプションを付けて mysqld を起動できます。注意: ulimit -c 1000000 を safe_mysqld に追加するか --core-file-size=1000000 をつけて safe_mysqld を起動して、 core file size を増加する必要があります。 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照.

    もし MySQL クライアントをリンクしようとして以下のエラーになった場合： 

    ld.so.1: ./my: fatal: libmysqlclient.so.4:
open failed: No such file or directory

    実行時には、以下のうちの一つの方法で問題を解決できます：

    • クライアントを以下のフラグで(-Lpathのかわりに)リンクします： -Wl,r/path-libmysqlclient.so.
    • libmysqclient.so を `/usr/lib' にコピーします
    • LD_RUN_PATH 環境変数を `libmysqlclient.so' が存在する場所に設定します。 (クライアントを実行する前に設定します)

    富士通コンパイラ (fcc / FCC) を使用している場合、MySQL のコンパイルにいくつかの問題があります。Linux ヘッダファイルはとても gcc 指向であるためです。

    次の configure 行は fcc/FCC で動作します: 

    CC=fcc CFLAGS="-O -K fast -K lib -K omitfp -Kpreex -D_GNU_SOURCE \
-DCONST=const -DNO_STRTOLL_PROTO" CXX=FCC CXXFLAGS="-O -K fast -K lib \
-K omitfp -K preex --no_exceptions --no_rtti -D_GNU_SOURCE -DCONST=const \
-Dalloca=__builtin_alloca -DNO_STRTOLL_PROTO \
'-D_EXTERN_INLINE=static __inline'" ./configure --prefix=/usr/local/mysql \
--enable-assembler --with-mysqld-ldflags=-all-static --disable-shared \
--with-low-memory

    2.6.1.1 Linux Notes for Binary Distributions

    MySQL は少なくとも Linux バージョン 2.0 を必要とします。

    Warning: We have reports from some MySQL users that they have got serious stability problems with MySQL with Linux kernel 2.2.14. If you are using this kernel you should upgrade to 2.2.19 (or newer) or to a 2.4 kernel. If you have a multi-cpu box, then you should seriously consider using 2.4 as this will give you a significant speed boost.

    バイナリリリースは -static でリンクされており、これはあなたのシステムが どのバージョンのライブラリーを使用しているか気にする必要がありません。 よって、LinuxThreads もこの場合必要ありません。 -static でリンクされたプログラムのサイズは ダイナミックリンクされたプログラムより大きくなりますが、少し(3-5%)速くなります。 しかし一つの問題として、このスタティックリンクされたプログラムでは、 ユーザー定義関数(UDF)が使用できないことです。 もし UDF を使用する(書く)場合(C, C++とかで)、自分自身で MySQL を ダイナミックリンクを使用してコンパイルしなくてはなりません。

    もし glibc2 ではなく libc ベースのシステムを使用しているなら、 このバイナリリリースではホスト名解決と getpwnam() にいくつか問題が出ます。 (これは glibc がホスト名解決と getpwent() にいくつかの外部ライブラリに 依存しているためで、たとえ -static リンクしても解決しません). この場合、mysql_install_db 実行時に以下のエラーが出るでしょう： 

    Sorry, the host 'xxxx' could not be looked up

    あるいは、--user オプションで mysqld を起動しようとしたとき、 以下のエラーが出る場合： 

    getpwnam: No such file or directory

    この問題は、以下のうちのどれかの方法で解決できます：

    • MySQL ソース配布を入手し( RPM か tar.gz )、代わりに インストールします。
    • mysql_install_db --force を実行します; これは mysql_install_db に かかれている resolveip テストを実行しません。 また許可テーブル内でホスト名が使えなくなっています； ホスト名でなく IP アドレスで登録します (localhost は除). もし --force を持っていないような古い MySQL を使用しているなら、 エディターで、resolveip テストを mysql_install から削除します。
    • mysqld を --user の代わりに su で起動。

    Linux-Intel binary と MySQL RPM リリースは、もっとも速くなるように 調整されています。我々はもっとも早く安定したコンパイラーを常に使用しています。

    MySQL Perl サポートは Perl 5.004_03 以上のバージョンを必要としま す。

    Linux 2.2 バージョンのいくつかでは、TCP/IP 上で mysqld サーバに多く の新しい接続を行なう時に、エラー Resource temporarily unavailable を得ることがあります。

    この問題は、Linux では TCP/IP ソケットをクローズする時と、それがシステムに よって実際に解放される間に遅延があるためです。TCP/IP スロットの数は有限な ので、TCP/IP 上で MySQL `test-connect' ベンチマークを実行し た時のように、短い時間にとても多くの新しい TCP/IP 接続が行なわれた場合に上 記エラーが得られます。

    我々はこの問題について、異なる Linux メーリングリストで何回かメールを受け ました。しかし、当然、我々はこれを解決することはできません。

    この問題の知られている'解決策'は、あなたのクライアント内で永続的な接続を使 用するか、データベースサーバとクライアントが同じマシン上で実行されている場 合にソケットを使用することだけです。我々は、将来、Linux 2.4 カーネ ルでこの問題が解決されることを希望します。

    2.6.1.2 Linux x86 Notes

    MySQL は libc 5.4.12 以上が必要です。libc 5.4.46 で動作します。 glibc 2.0.6 以上でも動作します。 glibc の RPM にはいくつか問題があり、アップデートをチェックしてください。 glibc 2.0.7-19 と 2.0.7-29 RPM で動作します。

    If you are using Red Hat 8.0 or a new glibc 2.2.x library you should start mysqld with the option --thread-stack=192K. If you don't do it mysqld will die in gethostbyaddr() because the new glibc library requires > 128K memory on stack for this call. This stack size is now the default on MySQL 4.0.10 and above.

    If you are using gcc 3.0 and above to compile MySQL, you must install the libstdc++v3 library before compiling MySQL; if you don't do this you will get an error about a missing __cxa_pure_virtual symbol during linking!

    古い Linux 配布物では、configure 時に以下のようなエラーが出るかもしれません： 

    Syntax error in sched.h. Change _P to __P in the /usr/include/sched.h file.
See the Installation chapter in the Reference Manual.

    これは _P マクロが一つのアンダースコアしか持っていないためで、 このエラーメッセージに示されたように対処してください。

    以下のようなワーニングは無視して構いません： 

    mysqld.cc -o objs-thread/mysqld.o
mysqld.cc: In function `void init_signals()':
mysqld.cc:315: warning: assignment of negative value `-1' to
`long unsigned int'
mysqld.cc: In function `void * signal_hand(void *)':
mysqld.cc:346: warning: assignment of negative value `-1' to
`long unsigned int'

    Debian GNU/Linux では、MySQL をマシンの起動時に立ちあげるためには、 以下のようにします： 

    shell> cp support-files/mysql.server /etc/init.d/mysql.server
shell> /usr/sbin/update-rc.d mysql.server defaults 99

    mysql.server スクリプトは MySQL をインストールした先の `share/mysql' directory にあります。 あるいは、MySQL のソースの中の `support-files' ディレクトリにあります。

    mysqld がつねにスタート時にコアをはく場合、 古い `/lib/libc.a' を使用しているかもしれません。 `sql/mysqld' を消去して、新しく make install してみてください。 これはいくつかの Slackware で報告された現象です。

    もし mysqld をリンクする場合に以下のようなエラーが出た場合、 `libg++.a' が正しくインストールされていません： 

    /usr/lib/libc.a(putc.o): In function `_IO_putc':
putc.o(.text+0x0): multiple definition of `_IO_putc'

    `libg++.a' の使用を避けるには、 configure を以下のようにします： 

    shell> CXX=gcc ./configure

    2.6.1.3 Linux SPARC Notes

    いくつかの埋め込み関数, readdir_r() が壊れます。 この顕れとして、SHOW DATABASES が常に空を返します。 これは configure 後、コンパイルする前に、 `config.h' から HAVE_READDIR_R を取り除くことで解決します。

    その他いくつかの問題は、あなたの Linux にパッチを当てる必要があります。 パッチは http://www.mysql.com/Downloads/patches/Linux-sparc-2.0.30.diff. にあります。 このパッチは、vger.rutgers.edu にある `sparclinux-2.0.30.tar.gz' 用です。 (これは正式の 2.0.30 とは違います。パッチを正式2.0.30に当てないように) そして LinuxThreads Version 0.6 かそれ以上にしなくてはなりません。

    2.6.1.4 Linux Alpha Notes

    MySQL Version 3.23.12 が、Linux-Alpha 上で最初にテストされたバージョンです。 もし MySQL を Linux-Alpha 上で使用したいと考えたなら、 このバージョンより新しいものを使用します。

    We have tested MySQL on Alpha with our benchmarks and test suite, and it appears to work nicely.

    We currently build the MySQL binary packages on SuSE Linux 7.0 for AXP, kernel 2.4.4-SMP, Compaq C compiler (V6.2-505) and Compaq C++ compiler (V6.3-006) on a Compaq DS20 machine with an Alpha EV6 processor.

    You can find the above compilers at http://www.support.compaq.com/alpha-tools/). By using these compilers, instead of gcc, we get about 9-14% better performance with MySQL.

    Note that until MySQL version 3.23.52 and 4.0.2 we optimised the binary for the current CPU only (by using the -fast compile option); this meant that you could only use our binaries if you had an Alpha EV6 processor.

    Starting with all following releases we added the -arch generic flag to our compile options, which makes sure the binary runs on all Alpha processors. We also compile statically to avoid library problems. 

    CC=ccc CFLAGS="-fast -arch generic" CXX=cxx \
CXXFLAGS="-fast -arch generic -noexceptions -nortti" \
./configure --prefix=/usr/local/mysql --disable-shared \
--with-extra-charsets=complex --enable-thread-safe-client \
--with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared

    If you want to use egcs the following configure line worked for us: 

    CFLAGS="-O3 -fomit-frame-pointer" CXX=gcc \
CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \
-fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \
--disable-shared

    Some known problems when running MySQL on Linux-Alpha:

    • Debugging threaded applications like MySQL will not work with gdb 4.18. You should download and use gdb 5.1 instead!
    • If you try linking mysqld statically when using gcc, the resulting image will core dump at start. In other words, don't use --with-mysqld-ldflags=-all-static with gcc.

    2.6.1.5 Linux PowerPC Notes

    MySQL は最新の glibc を使用した MkLinux で動作します。 (glibc 2.0.7 でテストしました).

    2.6.1.6 Linux MIPS Notes

    Qube2 (Linux Mips) 上で MySQL を動作させるには、 最新の glibc ライブラリでなくてはなりません (glibc-2.0.7-29C2 は動作することが分かっています)。 そして、 egcs C++ compiler (egcs-1.0.2-9, gcc 2.95.2 以上) を 使用しなくてはなりません。

    2.6.1.7 Linux IA64 Notes

    To get MySQL to compile on Linux IA64, we use the following compile line: Using gcc-2.96: 

    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \
CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \
-fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \
"--with-comment=Official MySQL binary" --with-extra-charsets=complex

    On IA64 the MySQL client binaries are using shared libraries. This means that if you install our binary distribution in some other place than `/usr/local/mysql' you need to either modify `/etc/ld.so.conf' or add the path to the directory where you have `libmysqlclient.so' to the LD_LIBRARY_PATH environment variable.

    「A.3.1 Problems When Linking with the MySQL Client Library」節参照.

    2.6.2 Windows Notes

    This section describes using MySQL on Windows. This information is also provided in the `README' file that comes with the MySQL Windows distribution. 「2.1.2 Windows への MySQL のインストール」節参照.

    2.6.2.1 Starting MySQL on Windows 95, 98 or Me

    MySQL は TCP/IP をクライアントからサーバーへの接続に使用します。 こうすればネットワーク上のどのマシンからでも MySQL サーバーに 接続できるようになります。 このため、MySQL を起動する前に、 あなたは TCP/IP をインストールしなくてはなりません。 これは Windows CD-ROM にあります。

    もし古い Win95 (for example OSR2) を使用しているなら、 これは古い Winsock パッケージを使用しているかもしれません！ MySQL は Winsock 2 を要求します！ 最新の Winsock は http://www.microsoft.com/ にあります。 Win98 はデフォルトで新しい Winsock 2 ライブラリですので、 これは Win98 には当てはまりません。

    mysqld サーバーを起動するには, MS-DOS を起動し、以下のように入力します： 

    C:\> C:\mysql\bin\mysqld

    これは mysqld をバックグラウンドで動かします。

    MySQL サーバーの kill には： 

    C:\> C:\mysql\bin\mysqladmin -u root shutdown

    This calls the MySQL administation utility as user `root', which is the default Administrator in the MySQL grant system. Please note that the MySQL grant system is wholly independent from any login users under Windows.

    注意: Win95 と Win98 は名前付パイプをサポートしていません。Win95 と Win98 では、Windows NT サーバホスト上で動いているリモートの MySQL への接続だけに、名前付パイプを使用できます。 (The MySQL server must also support named pipes, of course. For example, using mysqld-opt under NT/2000/XP will not allow named pipe connections. You should use either mysqld-nt or mysqld-max-nt.)

    mysqld が起動しない場合、`\mysql\data\mysql.err' ファイルがそ の問題の原因を示す何らかのメッセージをサーバが書き出していないかチェック してください。mysqld --standalone でサーバの起動を試みることもでき ます; この場合、問題の解決の助けになるであろう、いくつかの有用な情報が画 面上で得られます。

    最後の選択肢は mysqld を --standalone --debug 付きで起動す ることです。この場合、mysqld はログをファイル `C:\mysqld.trace' に書き出します。これには、mysqld が何故起動 しないかの理由が含まれます。 「E.1.2 Creating Trace Files」節参照.

    Use mysqld --help to display all the options that mysqld understands!

    2.6.2.2 Starting MySQL on Windows NT, 2000 or XP

    NT 4 上で TCP/IP を用いて MySQL を動作させるには、service pack 3(以上) が必須です！

    Normally you should install MySQL as a service on Windows NT/2000/XP. In case the server was already running, first stop it using the following command: 

    C:\mysql\bin> mysqladmin -u root shutdown

    This calls the MySQL administation utility as user `root', which is the default Administrator in the MySQL grant system. Please note that the MySQL grant system is wholly independent from any login users under Windows.

    Now install the server service: 

    C:\mysql\bin> mysqld-max-nt --install

    If any options are required, they must be specified as ``Start parameters'' in the Windows Services utility before you start the MySQL service.

    The Services utility (Windows Service Control Manager) can be found in the Windows Control Panel (under Administrative Tools on Windows 2000). It is advisable to close the Services utility while performing the --install or --remove operations, this prevents some odd errors.

    For information about which server binary to run, see 「2.1.2.2 Preparing the Windows MySQL Environment」節.

    Please note that from MySQL version 3.23.44, you have the choice of set up the service as Manual instead (if you don't wish the service to be started automatically during the boot process): 

    C:\mysql\bin> mysqld-max-nt --install-manual

    サービスは MySQL という名前で登録されます。 一度インストールしたら、 これは Services (コントロールパネルにある) を使用するか、NET START MySQL コマンドを使用するかして、 起動されなくてはなりません。

    Once running, mysqld-max-nt can be stopped using mysqladmin, from the Services utility, or by using the command NET STOP MySQL.

    When running as a service, the operating system will automatically stop the MySQL service on computer shutdown. In MySQL versions < 3.23.47, Windows only waited for a few seconds for the shutdown to complete, and killed the database server process if the time limit was exceeded (potentially causing problems). For instance, at the next startup the InnoDB storage engine had to do crash recovery. Starting from MySQL version 3.23.48, the Windows will wait longer for the MySQL server shutdown to complete. If you notice this is not enough for your intallation, it is safest to run the MySQL server not as a service, but from the Command prompt, and shut it down with mysqladmin shutdown.

    There is a problem that Windows NT (but not Windows 2000/XP) by default only waits 20 seconds for a service to shut down, and after that kills the service process. You can increase this default by opening the Registry Editor `\winnt\system32\regedt32.exe' and editing the value of WaitToKillServiceTimeout at `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control' in the Registry tree. Specify the new larger value in milliseconds, for example 120000 to have Windows NT wait upto 120 seconds.

    Please note that when run as a service, mysqld-max-nt has no access to a console and so no messages can be seen. Errors can be checked in `c:\mysql\data\mysql.err'.

    もし mysqld-max-nt をサービスとしてインストールする場合に 問題が発生した場合、フルパスで実行してみてください： 

    C:\> C:\mysql\bin\mysqld-max-nt --install

    If this doesn't work, you can get mysqld-max-nt to start properly by fixing the path in the registry!

    サービスとして mysqld-max-nt を起動したくないなら以下のようにします： 

    C:\> C:\mysql\bin\mysqld-max-nt --standalone

    or 

    C:\> C:\mysql\bin\mysqld --standalone --debug

    最新のバージョンでは、デバッグのトレースを `C:\mysqld.trace' に出します。 「E.1.2 Creating Trace Files」節参照.

    2.6.2.3 Windows 上で MySQL を実行

    MySQL supports TCP/IP on all Windows platforms and named pipes on NT/2000/XP. The default is to use named pipes for local connections on NT/2000/XP and TCP/IP for all other cases if the client has TCP/IP installed. The host name specifies which protocol is used:

    Host name Protocol
    NULL (none) On NT/2000/XP, try named pipes first; if that doesn't work, use TCP/IP. On 9x/Me, TCP/IP is used.
    . Named pipes
    localhost TCP/IP to current host
    hostname TCP/IP

    MySQL クライアントに named pipes を強制的に使用させるには、 --pipe オプションか、ホストに . を指定します。 そして、--socket オプションでパイプの名前を指定します。 In MySQL 4.1 you should use the --protocol=PIPE option.

    Note that starting from 3.23.50, named pipes are only enabled if mysqld is started with --enable-named-pipe. This is because some users have experienced problems shutting down the MySQL server when one uses named pipes.

    MySQL が動いているかどうかは、以下のようにして確認できます： 

    C:\> C:\mysql\bin\mysqlshow
C:\> C:\mysql\bin\mysqlshow -u root mysql
C:\> C:\mysql\bin\mysqladmin version status proc
C:\> C:\mysql\bin\mysql test

    If mysqld is slow to answer to connections on Windows 9x/Me, there is probably a problem with your DNS. In this case, start mysqld with --skip-name-resolve and use only localhost and IP numbers in the MySQL grant tables. You can also avoid DNS when connecting to a mysqld-nt MySQL server running on NT/2000/XP by using the --pipe argument to specify use of named pipes. This works for most MySQL clients.

    2つの MySQL コマンドラインツールがあります：
    Binary Description
    mysql ネイティブな Windows 用にコンパイルされている。非常に限られたコマンドライン編集機能しか持たない
    mysqlc Cygnus GNU コンパイラとライブラリを用いてコンパイルされている。GNU readline によるコマンドライン編集機能を持つ。

    もし mysqlc.exe を使用したいなら, `C:\mysql\lib\cygwinb19.dll' をあなたの Windows システムディレクトリ (`\windows\system' もしくは同様のパス)にコピーしなくてはなりません。

    Windows の MySQL の初期の権限は、ローカルの全てのユーザーに 対して、全てのデータベースで全ての権限がパスワードなしに与えられています。 MySQL を安全にするために、全てのユーザーにパスワードを 設定すべきです。また、mysql.user テーブルから Host='localhost' で User='' となっているレコードを 削除すべきです。

    root ユーザーにもパスワードを設定すべきです。次の例では、 すべての権限を持つ匿名ユーザを削除したあとに、 root ユーザパスワードを設定しています: 

    C:\> C:\mysql\bin\mysql mysql
mysql> DELETE FROM user WHERE Host='localhost' AND User='';
mysql> QUIT
C:\> C:\mysql\bin\mysqladmin reload
C:\> C:\mysql\bin\mysqladmin -u root password your_password

    パスワードを設定した後、もし mysqld サーバーを停止させるなら、 以下のようにします： 

    C:\> mysqladmin --user=root --password=your_password shutdown

    もしあなたが Windows 下で、古い MySQL バージョン 3.21 のシェアウェ アバージョンを使用しているなら、上記のコマンドは次のエラーで失敗します: parse error near 'SET password'。回避策は、現在の MySQL バージョンにアップグレードすることです。これもフリーです。

    現在の MySQL バージョンでは、GRANT と REVOKE コ マンドで、簡単に新しいユーザを追加でき、権限を変更することができます。 「4.3.1 GRANT と REVOKE 構文」節参照.

    2.6.2.4 SSH を利用してリモートの MySQL に Windows から接続

    以下は SSH を用いてリモートの MySQL サーバに安全に接続するための 方法について述べたものです。 (by David Carlson dcarlson@mplcomm.com):

    • Install an SSH client on your Windows machine. As a user, the best non-free one I've found is from SecureCRT from http://www.vandyke.com/. Another option is f-secure from http://www.f-secure.com/. You can also find some free ones on Google at http://directory.google.com/Top/Computers/Security/Products_and_Tools/Cryptography/SSH/Clients/Windows/.
    • Windows SSH クライアントを起動。 Set Host_Name = yourmysqlserver_URL_or_IP. Set userid=your_userid to log in to your server (probably not the same as your MySQL login/password.
    • Set up port forwarding. Either do a remote forward (Set local_port: 3306, remote_host: yourmysqlservername_or_ip, remote_port: 3306 ) or a local forward (Set port: 3306, host: localhost, remote port: 3306).
    • Save everything, otherwise you'll have to redo it the next time.
    • Log in to your server with SSH session you just created.
    • On your Windows machine, start some ODBC application (such as Access).
    • Create a new file in Windows and link to MySQL using the ODBC driver the same way you normally do, except type in localhost for the MySQL host server@-not yourmysqlservername.

    You should now have an ODBC connection to MySQL, encrypted using SSH.

    2.6.2.5 Windows 上で、異なるディスクにデータを分割する

    Windows 上では、3.23.16 以上のバージョンの MySQL ディストリビュー ション中の mysqld-max と mysql-max-nt サーバは、 -DUSE_SYMDIR オプション付きでコンパイルされています。これはデータ ベースに対するシンボリックリンクを追加することで異なるディスクにデータベー スを置くことを可能にします（Unix におけるシンボリック・リンクと同様の方法 で）。

    Windows 上では、宛先ディレクトリへのパスを持つファイルを作成し、 そのファイルを database.sym というファイル名で mysql_data ディレクトリ の中に保存することで、データベースへのシンボリックリンクを作成します。 Note that the symbolic link will only be used if the directory mysql_data_dir\database doesn't exist.

    例えば、MySQL データディレクトリが `C:\mysql\data' で、 `D:\data\foo' に置かれているデータベース foo を持ちたければ、 テキスト D:\data\foo\ を含む `C:\mysql\data\foo.sym' を作成す べきです。その後、データベース foo に作成されるすべてのテーブルは `D:\data\foo' に作成されるでしょう。

    Note that because of the speed penalty you get when opening every table, we have not enabled this by default even if you have compiled MySQL with support for this. To enable symlinks you should put in your `my.cnf' or `my.ini' file the following entry: 

    [mysqld]
use-symbolic-links

    In MySQL 4.0 we will enable symlinks by default. Then you should instead use the skip-symlink option if you want to disable this.

    2.6.2.6 Windows 上で MySQL クライアントをコンパイルする

    ソースファイル中で `mysql.h' をインクルードする前に `windows.h' を インクルードするべきです： 

    #if defined(_WIN32) || defined(_WIN64)
#include <windows.h>
#endif
#include <mysql.h>

    あなたのコードを、必要に応じて `libmysql.dll' 中でロードするための ラッパーである `libmysql.lib' ライブラリに動的にリンクすることも できますし、また `mysqlclient.lib' ライブラリを静的にリンクすることも できます。

    mysqlclient ライブラリはスレッド対応ライブラリとしてコンパイル されていますので、あなたのコードもマルチスレッド対応になるように コンパイルするべきことに注意してください。

    2.6.2.7 Windows 用 MySQL と Unix 用 MySQL の比較

    MySQL-Windows バージョンは現在それ自体とても安定した(stableな)状態で供給されています。 MySQL-win32 バージョンは すべての機能が UNIX バージョンの MySQL と対応しています。 ただし、下記のような例外があります。

    Win95 とスレッド
    Win95は、各々のスレッドの作成のためにメインメモリのおよそ200バイトをメモリリーク します。もしあなたが多くの接続をすれば、MySQL の各々の接続が新しい スレッドを作成するので、あなたはWin95では長時間、mysqld を実行させるべきではあり ません！ WindowsNT と Windows98 はこのバグを持ちません。
    並行読み出し
    MySQL は INSERT と SELECT を混ぜることを可能にするために pread() 及び pwrite() 関数コールに依存します。現時点では pread()/pwrite() をエミュレートするために Mutex を用いています。長期的な計画では、 ファイルレベルのインターフェースを仮想インターフェースで置き換えて いくつもりなので、さらに速度を上げるために Windows NT/2000/XP 上で readfile()/writefile() インターフェースを使うことができます。 現在の実装は、しかし MySQL が利用可能なファイル数の上限が 1024 に なっています。これは Unix では可能な数の並行スレッドを NT/2000/XP 上では 動作させることができないことを意味しています。
    ブロック読み込み
    MySQL はそれぞれの接続のためにブロック読み込みを使います。 これは以下の事柄を意味しています：
    • 接続は、Unix の MySQL で起こるように、8時間の後に自動的に接続が断 ち切られるわけではありません
    • もし接続が「ハングすれば」、MySQLを終了しないでそれを中断することは、不可能です。
    • mysqladmin kill は、スリープしている接続上では働かないはずです。
    • スリープ中の接続があるかぎり、mysqladmin shutdown は中断することができません。
    We plan to fix this problem when our Windows developers have figured out a nice workaround.
    DROP DATABASE
    複数のスレッドで使われているデータベースはDROPをすることができません。
    タスクマネージャーからの MySQL の終了
    Windows95では「Windowsの終了」やタスクマネージャから MySQL を終了することはできません。 mysqladmin shutdown で終了しなければなりません。
    大文字小文字を区別しない名前
    Windowsではファイルネームは大文字小文字が区別されません。 そのため、Windows用の MySQL では、テーブル名は大文字小文字が区別されません。 唯一の制限は、ステートメント(SQL文)中においては、データベースとテーブルの名前は 同じケース(大文字小文字)を使用して指定されなければならないという点です。 「6.1.3 名前のケース依存性」節参照.
    The `\' directory character
    Windows 95のパス名コンポーネントは、 `\' によって離されますが、その文字は同じく MySQL のエスケープ文字でもあります。もしあなたが LOAD DATA INFILE または SELECT ... INTO OUTFILE を使う場合には、`\' を二重に使わなくてはなりません。 
    mysql> LOAD DATA INFILE "C:\\tmp\\skr.txt" INTO TABLE skr;
mysql> SELECT * INTO OUTFILE 'C:\\tmp\\skr.txt' FROM skr;
    かわりに、UNIX でのファイルネーム形式 `/' で書く必要があります。 
    mysql> LOAD DATA INFILE "C:/tmp/skr.txt" INTO TABLE skr;
mysql> SELECT * INTO OUTFILE 'C:/tmp/skr.txt' FROM skr;
    Can't open named pipe エラー
    もしあなたが NT 上で最新の mysql-clients と MySQL 3.22 バージョン を使えば、あなたは、次のエラーを得ることになるはずです: 
    error 2017: can't open named pipe to host: . pipe...
    これは、MySQL のリリースバージョンがデフォルトで NT の 名前つきパイプを 使っているために起こっています。 新しい MySQL クライアントで --host=localhost オプションを用いるか、 以下の情報を含むオプションファイル `C:\my.cnf' を作成することで、このエラーを 回避することができます。 
    [client]
host = localhost
    Starting from 3.23.50, named pipes are only enabled if mysqld is started with --enable-named-pipe.
    Access denied for user error
    もしあなたが同じマシン上の MySQL サーバーにアクセスした時 Access denied for user: 'some-user@unknown' to database 'mysql' エラーを得るなら、これはあなたの MySQL があなた のマシンのホスト名を正しく解決できてないことを意味します。 これを修正するには、 以下の情報を持つファイル `\windows\hosts' を作成するべきです。 (注:Windows95,98には\Windowsフォルダ上にサンプルとして「lmhosts.sam」ファイルが 既にあるはずです) 
    127.0.0.1       localhost
    ALTER TABLE
    ALTER TABLE ステートメントの実行中、テーブルは他のスレッドが使用できないようロック されます。これは Windows が他のスレッドによって使用中のファイルを削除 できないという事実のためにしなければならないことです（私たちはこの 問題を回避するための方法を将来見出すかもしれません）。
    DROP TABLE on a table that is in use by a MERGE table will not work on Windows because the MERGE handler does the table mapping hidden from the upper layer of MySQL. Because Windows doesn't allow you to drop files that are open, you first must flush all MERGE tables (with FLUSH TABLES) or drop the MERGE table before dropping the table. We will fix this at the same time we introduce VIEWs.
    DATA DIRECTORY and INDEX DIRECTORY directives in CREATE TABLE is ignored on Windows, because Windows doesn't support symbolic links.

    Here are some open issues for anyone who might want to help us with the Windows release:

    • Make a single-user MYSQL.DLL server. This should include everything in a standard MySQL server, except thread creation. This will make MySQL much easier to use in applications that don't need a true client/server and don't need to access the server from other hosts.
    • MySQL のインストールされたもののための、素敵な開始・シャットダウン アイコンの追加。
    • NT上で mysqld をサービスとして --install フラグで登録するとき、 コマンドラインにデフォルトオプションも一緒に追加できると素敵です。 差し当たって、 回避策は代わりに `C:\my.cnf' ファイル内のパラメータをリストすることです。
    • タスクマネージャから mysqld を終了させることができればほんとうに親切でしょう。 今のところ、あなたは mysqladmin shutdown を使わなければなりません。
    • mysql のコマンドライン・ツールで使うために readline をWindowsに移植しませんか？
    • 標準の MySQL クライアント(mysql、mysqlshow、mysqladmin、および、mysqldump)のGUI バージョンがあればいいでしょうねぇ。
    • `net.c' 中のソケット読み出し・書き込み関数が割り込み不可だったら素敵 でした。これは Windows 上で mysqladmin kill を用いて、オープンなスレッドを kill することができるでしょう。
    • mysqld はデフォルトロケールではなく、常に「C」ロケールで起動します。私たちは、 ソート順に関して mysqld が現在のロケールを使用するようにしたいです。
    • Windows によって提供されている、より高速でスレッドセーフなインクリメント・ デクリメントメソッドを使うためのマクロの追加

    他の Windows 特有の事柄は MySQL-Windows ディストリビューションに同梱されている `README' ファイルで説明されています。

    2.6.3 Solaris Notes

    Solaris では MySQL ソースを展開するときトラブルが出るでしょう！ Solaris の tar は長い名前を扱えず、 MySQL を展開する場合、 以下のようなエラーになります： 

    x mysql-3.22.12-beta/bench/Results/ATIS-mysql_odbc-NT_4.0-cmp-db2,\
informix,ms-sql,mysql,oracle,solid,sybase, 0 bytes, 0 tape blocks
tar: directory checksum error

    この場合、GNU tar (gtar) を展開に使用してください。 コンパイルずみのものが以下にあります： http://www.mysql.com/downloads/os-solaris.html.

    Sun ネイティブスレッドは Solaris 2.5 以上で動きます。 バージョン 2.4 以下の場合、MySQL は時動的に MIT-pthreads を使用します 「2.3.6 MIT-pthreads に関して」節参照.

    もし、configure 時に、以下のエラーが出たなら： 

    checking for restartable system calls... configure: error can not run test
programs while cross compiling

    これはコンパイラーのインストールでなにかを間違っています! この場合、あなたは、より新しいバージョンへコンパイラーをアップグレードすべきです。 以下の行を config.cache ファイルに追加することによって、 この問題を解決してもかまいません： 

    ac_cv_sys_restartable_syscalls=${ac_cv_sys_restartable_syscalls='no'}

    もしあなたが SPARC の Solaris を使用しているなら、 gcc 2.95.2 を推奨します。 これは ttp://gcc.gnu.org/. で見つけれます。 egcs 1.1.1 と gcc 2.8.1 は SPARC 上では完全に動作しないことに注意！

    gcc 2.95.2 を使用した、推奨する configure は: 

    CC=gcc CFLAGS="-O3" \
CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \
./configure --prefix=/usr/local/mysql --with-low-memory --enable-assembler

    If you have an UltraSPARC, you can get 4% more performance by adding "-mcpu=v8 -Wa,-xarch=v8plusa" to CFLAGS and CXXFLAGS.

    If you have Sun's Forte 5.0 (or newer) compiler, you can run configure like this: 

    CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
CXX=CC CXXFLAGS="-noex -mt" \
./configure --prefix=/usr/local/mysql --enable-assembler

    You can create a 64 bit binary with: 

    CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
./configure --prefix=/usr/local/mysql --enable-assembler

    In the MySQL benchmarks, we got a 4% speedup on an UltraSPARC when using Forte 5.0 in 32 bit mode compared to using gcc 3.2 with -mcpu flags.

    If you create a 64 bit binary, it's 4 % slower than the 32 bit binary, but mysqld can instead handle more treads and memory.

    If you get a problem with fdatasync or sched_yield, you can fix this by adding LIBS=-lrt to the configure line

    The following paragraph is only relevant for older compilers than WorkShop 5.3:

    You may also have to edit the configure script to change this line: 

    #if !defined(__STDC__) || __STDC__ != 1

    to this: 

    #if !defined(__STDC__)

    もし -Xc オプションで __STDC__ を有効にした場合、 Sun compiler は Solaris の `pthread.h' ヘッダーファイルを使用して コンパイルすることができません。 これはサンのバグです(インクルードファイルかコンパイラーのバグ)

    もし mysqld を起動時に以下のエラーが出た場合、 マルチスレッドを外して(オプション -mt を指定) Sun compiler を使って MySQL をコンパイルし直してください： 

    libc internal error: _rmutex_unlock: rmutex not held

    -mt を CFLAGS と CXXFLAGS に加えます。

    If you are using the SFW version of gcc (which comes with Solaris 8), you must add `/opt/sfw/lib' to the environment variable LD_LIBRARY_PATH before running configure.

    If you are using the gcc available from sunfreeware.com, you may have many problems. You should recompile gcc and GNU binutils on the machine you will be running them from to avoid any problems.

    If you get the following error when compiling MySQL with gcc, it means that your gcc is not configured for your version of Solaris: 

    shell> gcc -O3 -g -O2 -DDBUG_OFF  -o thr_alarm ...
./thr_alarm.c: In function `signal_hand':
./thr_alarm.c:556: too many arguments to function `sigwait'

    The proper thing to do in this case is to get the newest version of gcc and compile it with your current gcc compiler! At least for Solaris 2.5, almost all binary versions of gcc have old, unusable include files that will break all programs that use threads (and possibly other programs)!

    Solaris は スタテックリンクのシステムライブラリーを用意していません (libpthreads and libdl)。 そのため、--static オプションで MySQL をコンパイルできません。 もしこれを試みた場合、以下のエラーになります： 

    ld: fatal: library -ldl: not found

or

undefined reference to `dlopen'

or

cannot find -lrt

    もし多くのプロセスが速く mysqld に接続を試みた場合、 MySQL ログに以下のようにエラーが出ます: 

    Error in accept: Protocol error

    サーバーを --set-variable back_log=50 オプションで起動すれば、この問題に対処できるでしょう。 Please note that --set-variable is deprecated since MySQL 4.0, just use --back_log=50 on its own. 「4.1.1 mysqld コマンド行オプション」節参照.

    もし自分の MySQL クライアントプログラムをリンクして 実行時に以下のようにエラーが出た場合： 

    ld.so.1: ./my: fatal: libmysqlclient.so.#:
open failed: No such file or directory

    これは以下のどれかで回避できます：

    • 以下のフラグでクライアントをリンクします(-Lpath の代わりに): -Wl,r/full-path-to-libmysqlclient.so.
    • Copy `libmysqclient.so' to `/usr/lib'.
    • Add the pathname of the directory where `libmysqlclient.so' is located to the LD_RUN_PATH environment variable before running your client.

    configure や MySQL が -lz のリンクを試み、あなたがそれを インストールしていないという問題がある場合は、２つの選択肢があります:

    • 圧縮通信プロトコルを使用できるようにしたい場合、ftp.gnu.org から zlib を 入手してインストールする必要があります。
    • --with-named-z-libs=no をつけて configure を行ないます。

    If you are using gcc and have problems with loading UDF functions into MySQL, try adding -lgcc to the link line for the UDF function.

    MySQL を自動的に開始させたい場合、 `support-files/mysql.server' を `/etc/init.d' にコピーし、 /etc/rc3.d/S99mysql.server という名前でシンボリックリンクを生成し てください。

    As Solaris doesn't support core files for setuid() applications, you can't get a core file from mysqld if you are using the --user option.

    2.6.3.1 Solaris 2.7/2.8 Notes

    通常、Solaris 2.6 のバイナリは Solaris 7 , 8 で使用できます。 ほとんどの Solaris 2.6 の問題も Solaris 7 , 8 に適用できます。

    注意: MySQL Version 3.23.4 以上では、新しいバージョンの Solaris を自動 検出し、以下の問題についての回避策を有効にします！

    Solaris 7 , 8 は、インクルードファイルにいくつかバグがあります。 gcc で以下のようなエラーが出た場合： 

    /usr/include/widec.h:42: warning: `getwc' redefined
/usr/include/wchar.h:326: warning: this is the location of the previous
definition

    以下のようにして回避します：

    /usr/include/widec.h を .../lib/gcc-lib/os/gcc-version/include にコピー 41 行目を変更: 

    変更前：
#if     !defined(lint) && !defined(__lint)

変更後：

#if     !defined(lint) && !defined(__lint) && !defined(getwc)

    代わりに、`/usr/include/widec.h' を直接変更してもかまいません。 どちらの方法にしても、ファイルを修正後は、`config.cache' を 消して configure を再実行しなくてはなりません！

    make 実行時に以下のようなエラーになった場合、configure が `curses.h' ファイルを検出できていません (これは /usr/include/widec.h の エラーのためにおきます): 

    In file included from mysql.cc:50:
/usr/include/term.h:1060: syntax error before `,'
/usr/include/term.h:1081: syntax error before `;'

    これを解決するには、以下のうち一つを行います：

    • Configure with CFLAGS=-DHAVE_CURSES_H CXXFLAGS=-DHAVE_CURSES_H ./configure.
    • 前述したとおり、`/usr/include/widec.h' を修正し、configure を再実行します。
    • #define HAVE_TERM 行を `config.h' ファイルから消し、 make を再実行します。

    クライアントプログラムのリンク時に、リンカが -lz を見つけられない という問題が発生した場合、問題はおそらく `libz.so' ファイルが `/usr/local/lib' にインストールされたことです。次の方法の一つでこれ を修正できます:

    • LD_LIBRARY_PATH に `/usr/local/lib' を追加
    • /lib から libz.so へのリンクを追加
    • Solaris 8 を使用している場合、Solaris 8 CD ディストリビューションからオ プションの zlib をインストール可能。
    • --with-named-z-libs=no オプション付きで MySQL を configure する。

    2.6.3.2 Solaris x86 Notes

    On Solaris 2.8 on x86, mysqld will core dump if you run 'strip' in. （訳注： GNU binutils を Sun 上で使用すると、CPU, version にかかわらず、 この現象に遭遇します。その場合は、/usr/ccs/bin/ の方を使います。）

    gcc か egcs を Solaris x86 で使用した場合、load 時にコアダンプする場合、 以下のように configure します: 

    CC=gcc CFLAGS="-O3 -fomit-frame-pointer -DHAVE_CURSES_H" \
CXX=gcc \
CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors -fno-exceptions \
-fno-rtti -DHAVE_CURSES_H" \
./configure --prefix=/usr/local/mysql

    これは libstdc++ ライブラリーと C++ の問題を回避します。

    もしこれが該当しない場合、デバッグモードでコンパイルして デバッグのトレースファイルを書き出すようにして起動するか、 gdb を使用して起動してください. 「E.1.3 Debugging mysqld under gdb」節参照.

    2.6.4 BSD Notes

    This section provides information for the various BSD flavours, as well as specific versions within those.

    2.6.4.1 FreeBSD Notes

    FreeBSD 3.x is recommended for running MySQL since the thread package is much more integrated.

    The easiest and therefore the preferred way to install is to use the mysql-server and mysql-client ports available on http://www.freebsd.org/.

    Using these gives you:

    • A working MySQL with all optimisations known to work on your version of FreeBSD enabled.
    • Automatic configuration and build.
    • Startup scripts installed in /usr/local/etc/rc.d.
    • Ability to see which files that are installed with pkg_info -L. And to remove them all with pkg_delete if you no longer want MySQL on that machine.

    It is recommended you use MIT-pthreads on FreeBSD 2.x and native threads on Versions 3 and up. It is possible to run with native threads on some late 2.2.x versions but you may encounter problems shutting down mysqld.

    The MySQL `Makefile's require GNU make (gmake) to work. If you want to compile MySQL you need to install GNU make first.

    Be sure to have your name resolver setup correct. Otherwise, you may experience resolver delays or failures when connecting to mysqld.

    Make sure that the localhost entry in the `/etc/hosts' file is correct (otherwise, you will have problems connecting to the database). The `/etc/hosts' file should start with a line: 

    127.0.0.1       localhost localhost.your.domain

    The recommended way to compile and install MySQL on FreeBSD with gcc (2.95.2 and up) is: 

    CC=gcc CFLAGS="-O2 -fno-strength-reduce" \
CXX=gcc CXXFLAGS="-O2 -fno-rtti -fno-exceptions -felide-constructors \
-fno-strength-reduce" \
./configure --prefix=/usr/local/mysql --enable-assembler
gmake
gmake install
./scripts/mysql_install_db
cd /usr/local/mysql
./bin/mysqld_safe &

    If you notice that configure will use MIT-pthreads, you should read the MIT-pthreads notes. 「2.3.6 MIT-pthreads に関して」節参照.

    If you get an error from make install that it can't find `/usr/include/pthreads', configure didn't detect that you need MIT-pthreads. This is fixed by executing these commands: 

    shell> rm config.cache
shell> ./configure --with-mit-threads

    FreeBSD is also known to have a very low default file handle limit. 「A.2.16 File Not Found」節参照. Uncomment the ulimit -n section in safe_mysqld or raise the limits for the mysqld user in /etc/login.conf (and rebuild it with cap_mkdb /etc/login.conf). Also be sure you set the appropriate class for this user in the password file if you are not using the default (use: chpass mysqld-user-name). 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照.

    If you have a lot of memory you should consider rebuilding the kernel to allow MySQL to take more than 512M of RAM. Take a look at option MAXDSIZ in the LINT config file for more info.

    If you get problems with the current date in MySQL, setting the TZ variable will probably help. 「F Environment Variables」節参照.

    To get a secure and stable system you should only use FreeBSD kernels that are marked -RELEASE.

    2.6.4.2 NetBSD notes

    To compile on NetBSD you need GNU make. Otherwise, the compile will crash when make tries to run lint on C++ files.

    2.6.4.3 OpenBSD 2.5 Notes

    On OpenBSD Version 2.5, you can compile MySQL with native threads with the following options: 

    CFLAGS=-pthread CXXFLAGS=-pthread ./configure --with-mit-threads=no

    2.6.4.4 OpenBSD 2.8 Notes

    Our users have reported that OpenBSD 2.8 has a threading bug which causes problems with MySQL. The OpenBSD Developers have fixed the problem, but as of January 25th, 2001, it's only available in the ``-current'' branch. The symptoms of this threading bug are: slow response, high load, high CPU usage, and crashes.

    If you get an error like Error in accept:: Bad file descriptor or error 9 when trying to open tables or directories, the problem is probably that you haven't allocated enough file descriptors for MySQL.

    In this case try starting safe_mysqld as root with the following options:

    --user=mysql --open-files-limit=2048

    2.6.4.5 BSD/OS Version 2.x Notes

    If you get the following error when compiling MySQL, your ulimit value for virtual memory is too low: 

    item_func.h: In method `Item_func_ge::Item_func_ge(const Item_func_ge &)':
item_func.h:28: virtual memory exhausted
make[2]: *** [item_func.o] Error 1

    Try using ulimit -v 80000 and run make again. If this doesn't work and you are using bash, try switching to csh or sh; some BSDI users have reported problems with bash and ulimit.

    If you are using gcc, you may also use have to use the --with-low-memory flag for configure to be able to compile `sql_yacc.cc'.

    If you get problems with the current date in MySQL, setting the TZ variable will probably help. 「F Environment Variables」節参照.

    2.6.4.6 BSD/OS Version 3.x Notes

    Upgrade to BSD/OS Version 3.1. If that is not possible, install BSDIpatch M300-038.

    Use the following command when configuring MySQL: 

    shell> env CXX=shlicc++ CC=shlicc2 \
       ./configure \
           --prefix=/usr/local/mysql \
           --localstatedir=/var/mysql \
           --without-perl \
           --with-unix-socket-path=/var/mysql/mysql.sock

    The following is also known to work: 

    shell> env CC=gcc CXX=gcc CXXFLAGS=-O3 \
       ./configure \
           --prefix=/usr/local/mysql \
           --with-unix-socket-path=/var/mysql/mysql.sock

    You can change the directory locations if you wish, or just use the defaults by not specifying any locations.

    If you have problems with performance under heavy load, try using the --skip-thread-priority option to mysqld! This will run all threads with the same priority; on BSDI Version 3.1, this gives better performance (at least until BSDI fixes their thread scheduler).

    If you get the error virtual memory exhausted while compiling, you should try using ulimit -v 80000 and run make again. If this doesn't work and you are using bash, try switching to csh or sh; some BSDI users have reported problems with bash and ulimit.

    2.6.4.7 BSD/OS Version 4.x Notes

    BSDI Version 4.x has some thread-related bugs. If you want to use MySQL on this, you should install all thread-related patches. At least M400-023 should be installed.

    On some BSDI Version 4.x systems, you may get problems with shared libraries. The symptom is that you can't execute any client programs, for example, mysqladmin. In this case you need to reconfigure not to use shared libraries with the --disable-shared option to configure.

    Some customers have had problems on BSDI 4.0.1 that the mysqld binary after a while can't open tables. This is because some library/system related bug causes mysqld to change current directory without asking for this!

    The fix is to either upgrade to 3.23.34 or after running configure remove the line #define HAVE_REALPATH from config.h before running make.

    Note that the above means that you can't symbolic link a database directories to another database directory or symbolic link a table to another database on BSDI! (Making a symbolic link to another disk is okay).

    2.6.5 Mac OS X Notes

    2.6.5.1 Mac OS X 10.x

    MySQL should work without any problems on Mac OS X 10.x (Darwin). You don't need the pthread patches for this OS!

    This also applies to Mac OS X 10.x Server. Compiling for the Server platform is the same as for the client version of Mac OS X. However please note that MySQL comes preinstalled on the Server!

    「2.1.3 Installing MySQL on Mac OS X」節参照.

    2.6.5.2 Mac OS X Server 1.2 (Rhapsody)

    Before trying to configure MySQL on Mac OS X server you must first install the pthread package from http://www.prnet.de/RegEx/mysql.html.

    Our binary for Mac OS X is compiled on Darwin 6.3 with the following configure line: 

    CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \
CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \
-fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \
--with-extra-charsets=complex --enable-thread-safe-client \
--enable-local-infile --disable-shared

    You might want to also add aliases to your shell's resource file to access mysql and mysqladmin from the command-line: 

    alias mysql '/usr/local/mysql/bin/mysql'
alias mysqladmin '/usr/local/mysql/bin/mysqladmin'

    Alternatively, you could simply add /usr/local/mysql/bin to your PATH environment variable, e.g. by adding the following to `$HOME/.tcshrc': 

    setenv PATH $PATH:/usr/local/bin

    2.6.6 Other Unix Notes

    2.6.6.1 HP-UX Notes for Binary Distributions

    Some of the binary distributions of MySQL for HP-UX are distributed as an HP depot file and as a tar file. To use the depot file you must be running at least HP-UX 10.x to have access to HP's software depot tools.

    The HP version of MySQL was compiled on an HP 9000/8xx server under HP-UX 10.20, and uses MIT-pthreads. It is known to work well under this configuration. MySQL Version 3.22.26 and newer can also be built with HP's native thread package.

    Other configurations that may work:

    • HP 9000/7xx running HP-UX 10.20+
    • HP 9000/8xx running HP-UX 10.30

    The following configurations almost definitely won't work:

    • HP 9000/7xx or 8xx running HP-UX 10.x where x < 2
    • HP 9000/7xx or 8xx running HP-UX 9.x

    To install the distribution, use one of the commands here, where /path/to/depot is the full pathname of the depot file:

    • To install everything, including the server, client and development tools: 
      shell> /usr/sbin/swinstall -s /path/to/depot mysql.full
    • To install only the server: 
      shell> /usr/sbin/swinstall -s /path/to/depot mysql.server
    • To install only the client package: 
      shell> /usr/sbin/swinstall -s /path/to/depot mysql.client
    • To install only the development tools: 
      shell> /usr/sbin/swinstall -s /path/to/depot mysql.developer

    The depot places binaries and libraries in `/opt/mysql' and data in `/var/opt/mysql'. The depot also creates the appropriate entries in `/etc/init.d' and `/etc/rc2.d' to start the server automatically at boot time. Obviously, this entails being root to install.

    To install the HP-UX tar.gz distribution, you must have a copy of GNU tar.

    2.6.6.2 HP-UX Version 10.20 Notes

    There are a couple of small problems when compiling MySQL on HP-UX. We recommend that you use gcc instead of the HP-UX native compiler, because gcc produces better code!

    We recommend using gcc 2.95 on HP-UX. Don't use high optimisation flags (like -O6) as this may not be safe on HP-UX.

    The following configure line should work with gcc 2.95: 

    CFLAGS="-I/opt/dce/include -fpic" \
CXXFLAGS="-I/opt/dce/include -felide-constructors -fno-exceptions \
-fno-rtti" CXX=gcc ./configure --with-pthread \
--with-named-thread-libs='-ldce' --prefix=/usr/local/mysql --disable-shared

    The following configure line should work with gcc 3.1: 

    CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc \
CXXFLAGS="-DHPUX -I/opt/dce/include -felide-constructors -fno-exceptions \
-fno-rtti -O3 -fPIC" ./configure --prefix=/usr/local/mysql \
--with-extra-charsets=complex --enable-thread-safe-client \
--enable-local-infile  --with-pthread \
--with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC
--disable-shared

    2.6.6.3 HP-UX Version 11.x Notes

    For HP-UX Version 11.x we recommend MySQL Version 3.23.15 or later.

    Because of some critical bugs in the standard HP-UX libraries, you should install the following patches before trying to run MySQL on HP-UX 11.0: 

    PHKL_22840 Streams cumulative
PHNE_22397 ARPA cumulative

    This will solve the problem of getting EWOULDBLOCK from recv() and EBADF from accept() in threaded applications.

    If you are using gcc 2.95.1 on an unpatched HP-UX 11.x system, you will get the error: 

    In file included from /usr/include/unistd.h:11,
                 from ../include/global.h:125,
                 from mysql_priv.h:15,
                 from item.cc:19:
/usr/include/sys/unistd.h:184: declaration of C function ...
/usr/include/sys/pthread.h:440: previous declaration ...
In file included from item.h:306,
                 from mysql_priv.h:158,
                 from item.cc:19:

    The problem is that HP-UX doesn't define pthreads_atfork() consistently. It has conflicting prototypes in `/usr/include/sys/unistd.h':184 and `/usr/include/sys/pthread.h':440 (details below).

    One solution is to copy `/usr/include/sys/unistd.h' into `mysql/include' and edit `unistd.h' and change it to match the definition in `pthread.h'. Here's the diff: 

    183,184c183,184
<      extern int pthread_atfork(void (*prepare)(), void (*parent)(),
<                                                void (*child)());
---
>      extern int pthread_atfork(void (*prepare)(void), void (*parent)(void),
>                                                void (*child)(void));

    After this, the following configure line should work: 

    CFLAGS="-fomit-frame-pointer -O3 -fpic" CXX=gcc \
CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti -O3" \
./configure --prefix=/usr/local/mysql --disable-shared

    If you are using MySQL 4.0.5 with the HP-UX compiler you can use: (tested with cc B.11.11.04): 

    CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure --with-extra-character-set=complex

    You can ignore any errors of the following type: 

    aCC: warning 901: unknown option: `-3': use +help for online documentation

    If you get the following error from configure 

    checking for cc option to accept ANSI C... no
configure: error: MySQL requires a ANSI C compiler (and a C++ compiler).
Try gcc. See the Installation chapter in the Reference Manual.

    Check that you don't have the path to the K&R compiler before the path to the HP-UX C and C++ compiler.

    Another reason for not beeing able to compile is that you didn't define the +DD64 flags above.

    2.6.6.4 IBM-AIX notes

    Automatic detection of xlC is missing from Autoconf, so a configure command something like this is needed when compiling MySQL (This example uses the IBM compiler): 

    export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
export CFLAGS="-I /usr/local/include"
export LDFLAGS="-L /usr/local/lib"
export CPPFLAGS=$CFLAGS
export CXXFLAGS=$CFLAGS

./configure --prefix=/usr/local \
		--localstatedir=/var/mysql \
		--sysconfdir=/etc/mysql \
		--sbindir='/usr/local/bin' \
		--libexecdir='/usr/local/bin' \
		--enable-thread-safe-client \
		--enable-large-files

    Above are the options used to compile the MySQL distribution that can be found at http://www-frec.bull.com/.

    If you change the -O3 to -O2 in the above configure line, you must also remove the -qstrict option (this is a limitation in the IBM C compiler).

    If you are using gcc or egcs to compile MySQL, you must use the -fno-exceptions flag, as the exception handling in gcc/egcs is not thread-safe! (This is tested with egcs 1.1.) There are also some known problems with IBM's assembler, which may cause it to generate bad code when used with gcc.

    We recommend the following configure line with egcs and gcc 2.95 on AIX: 

    CC="gcc -pipe -mcpu=power -Wa,-many" \
CXX="gcc -pipe -mcpu=power -Wa,-many" \
CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \
./configure --prefix=/usr/local/mysql --with-low-memory

    The -Wa,-many is necessary for the compile to be successful. IBM is aware of this problem but is in to hurry to fix it because of the workaround available. We don't know if the -fno-exceptions is required with gcc 2.95, but as MySQL doesn't use exceptions and the above option generates faster code, we recommend that you should always use this option with egcs / gcc.

    If you get a problem with assembler code try changing the -mcpu=xxx to match your CPU. Typically power2, power, or powerpc may need to be used, alternatively you might need to use 604 or 604e. I'm not positive but I would think using "power" would likely be safe most of the time, even on a power2 machine.

    If you don't know what your CPU is then do a "uname -m", this will give you back a string that looks like "000514676700", with a format of xxyyyyyymmss where xx and ss are always 0's, yyyyyy is a unique system id and mm is the id of the CPU Planar. A chart of these values can be found at http://publib.boulder.ibm.com/doc_link/en_US/a_doc_lib/cmds/aixcmds5/uname.htm. This will give you a machine type and a machine model you can use to determine what type of CPU you have.

    If you have problems with signals (MySQL dies unexpectedly under high load) you may have found an OS bug with threads and signals. In this case you can tell MySQL not to use signals by configuring with: 

    shell> CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
       CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
       -DDONT_USE_THR_ALARM" \
       ./configure --prefix=/usr/local/mysql --with-debug --with-low-memory

    This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are ``sleeping'' on a connection with mysqladmin kill or mysqladmin shutdown. Instead, the client will die when it issues its next command.

    On some versions of AIX, linking with libbind.a makes getservbyname core dump. This is an AIX bug and should be reported to IBM.

    For AIX 4.2.1 and gcc you have to do the following changes.

    After configuring, edit `config.h' and `include/my_config.h' and change the line that says 

    #define HAVE_SNPRINTF 1

    to 

    #undef HAVE_SNPRINTF

    And finally, in `mysqld.cc' you need to add a prototype for initgoups. 

    #ifdef _AIX41
extern "C" int initgroups(const char *,int);
#endif

    If you need to allocate a lot of memory to the mysqld process, it's not enough to just set 'ulimit -d unlimited'. You may also have to set in mysqld_safe something like: 

    export LDR_CNTRL='MAXDATA=0x80000000'

    You can find more about using a lot of memory at: http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/genprogc/lrg_prg_support.htm.

    2.6.6.5 SunOS 4 Notes

    On SunOS 4, MIT-pthreads is needed to compile MySQL, which in turn means you will need GNU make.

    Some SunOS 4 systems have problems with dynamic libraries and libtool. You can use the following configure line to avoid this problem: 

    shell> ./configure --disable-shared --with-mysqld-ldflags=-all-static

    When compiling readline, you may get warnings about duplicate defines. These may be ignored.

    When compiling mysqld, there will be some implicit declaration of function warnings. These may be ignored.

    2.6.6.6 Alpha-DEC-UNIX Notes (Tru64)

    If you are using egcs 1.1.2 on Digital Unix, you should upgrade to gcc 2.95.2, as egcs on DEC has some serious bugs!

    When compiling threaded programs under Digital Unix, the documentation recommends using the -pthread option for cc and cxx and the libraries -lmach -lexc (in addition to -lpthread). You should run configure something like this: 

    CC="cc -pthread" CXX="cxx -pthread -O" \
./configure --with-named-thread-libs="-lpthread -lmach -lexc -lc"

    When compiling mysqld, you may see a couple of warnings like this: 

    mysqld.cc: In function void handle_connections()':
mysqld.cc:626: passing long unsigned int *' as argument 3 of
accept(int,sockadddr *, int *)'

    You can safely ignore these warnings. They occur because configure can detect only errors, not warnings.

    If you start the server directly from the command-line, you may have problems with it dying when you log out. (When you log out, your outstanding processes receive a SIGHUP signal.) If so, try starting the server like this: 

    shell> nohup mysqld [options] &

    nohup causes the command following it to ignore any SIGHUP signal sent from the terminal. Alternatively, start the server by running safe_mysqld, which invokes mysqld using nohup for you. 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照.

    If you get a problem when compiling mysys/get_opt.c, just remove the line #define _NO_PROTO from the start of that file!

    If you are using Compac's CC compiler, the following configure line should work: 

    CC="cc -pthread"
CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed all -arch host"
CXX="cxx -pthread"
CXXFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed all -arch host \
-noexceptions -nortti"
export CC CFLAGS CXX CXXFLAGS
./configure \
--prefix=/usr/local/mysql \
--with-low-memory \
--enable-large-files \
--enable-shared=yes \
--with-named-thread-libs="-lpthread -lmach -lexc -lc"
gnumake

    If you get a problem with libtool, when compiling with shared libraries as above, when linking mysql, you should be able to get around this by issuing: 

    cd mysql
/bin/sh ../libtool --mode=link cxx -pthread  -O3 -DDBUG_OFF \
-O4 -ansi_alias -ansi_args -fast -inline speed \
-speculate all \ -arch host  -DUNDEF_HAVE_GETHOSTBYNAME_R \
-o mysql  mysql.o readline.o sql_string.o completion_hash.o \
../readline/libreadline.a -lcurses \
../libmysql/.libs/libmysqlclient.so  -lm
cd ..
gnumake
gnumake install
scripts/mysql_install_db

    2.6.6.7 Alpha-DEC-OSF/1 Notes

    If you have problems compiling and have DEC CC and gcc installed, try running configure like this: 

    CC=cc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 \
./configure --prefix=/usr/local/mysql

    If you get problems with the `c_asm.h' file, you can create and use a 'dummy' `c_asm.h' file with: 

    touch include/c_asm.h
CC=gcc CFLAGS=-I./include \
CXX=gcc CXXFLAGS=-O3 \
./configure --prefix=/usr/local/mysql

    Note that the following problems with the ld program can be fixed by downloading the latest DEC (Compaq) patch kit from: http://ftp.support.compaq.com/public/unix/.

    On OSF/1 V4.0D and compiler "DEC C V5.6-071 on Digital Unix V4.0 (Rev. 878)" the compiler had some strange behaviour (undefined asm symbols). /bin/ld also appears to be broken (problems with _exit undefined errors occuring while linking mysqld). On this system, we have managed to compile MySQL with the following configure line, after replacing /bin/ld with the version from OSF 4.0C: 

    CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql

    With the Digital compiler "C++ V6.1-029", the following should work: 

    CC=cc -pthread
CFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all \
       -arch host
CXX=cxx -pthread
CXXFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all \
          -arch host -noexceptions -nortti
export CC CFLAGS CXX CXXFLAGS
./configure --prefix=/usr/mysql/mysql --with-mysqld-ldflags=-all-static \
            --disable-shared --with-named-thread-libs="-lmach -lexc -lc"

    In some versions of OSF/1, the alloca() function is broken. Fix this by removing the line in `config.h' that defines 'HAVE_ALLOCA'.

    The alloca() function also may have an incorrect prototype in /usr/include/alloca.h. This warning resulting from this can be ignored.

    configure will use the following thread libraries automatically: --with-named-thread-libs="-lpthread -lmach -lexc -lc".

    When using gcc, you can also try running configure like this: 

    shell> CFLAGS=-D_PTHREAD_USE_D4 CXX=gcc CXXFLAGS=-O3 ./configure ...

    If you have problems with signals (MySQL dies unexpectedly under high load), you may have found an OS bug with threads and signals. In this case you can tell MySQL not to use signals by configuring with: 

    shell> CFLAGS=-DDONT_USE_THR_ALARM \
       CXXFLAGS=-DDONT_USE_THR_ALARM \
       ./configure ...

    This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are ``sleeping'' on a connection with mysqladmin kill or mysqladmin shutdown. Instead, the client will die when it issues its next command.

    With gcc 2.95.2, you will probably run into the following compile error: 

    sql_acl.cc:1456: Internal compiler error in `scan_region', at except.c:2566
Please submit a full bug report.

    To fix this you should change to the sql directory and do a ``cut and paste'' of the last gcc line, but change -O3 to -O0 (or add -O0 immediately after gcc if you don't have any -O option on your compile line). After this is done you can just change back to the top-level directly and run make again.

    2.6.6.8 SGI Irix Notes

    If you are using Irix Version 6.5.3 or newer mysqld will only be able to create threads if you run it as a user with CAP_SCHED_MGT privileges (like root) or give the mysqld server this privilege with the following shell command: 

    shell> chcap "CAP_SCHED_MGT+epi" /opt/mysql/libexec/mysqld

    You may have to undefine some things in `config.h' after running configure and before compiling.

    In some Irix implementations, the alloca() function is broken. If the mysqld server dies on some SELECT statements, remove the lines from `config.h' that define HAVE_ALLOC and HAVE_ALLOCA_H. If mysqladmin create doesn't work, remove the line from `config.h' that defines HAVE_READDIR_R. You may have to remove the HAVE_TERM_H line as well.

    SGI recommends that you install all of the patches on this page as a set: http://support.sgi.com/surfzone/patches/patchset/6.2_indigo.rps.html

    At the very minimum, you should install the latest kernel rollup, the latest rld rollup, and the latest libc rollup.

    You definitely need all the POSIX patches on this page, for pthreads support:

    http://support.sgi.com/surfzone/patches/patchset/6.2_posix.rps.html

    If you get the something like the following error when compiling `mysql.cc': 

    "/usr/include/curses.h", line 82: error(1084): invalid combination of type

    Type the following in the top-level directory of your MySQL source tree: 

    shell> extra/replace bool curses_bool < /usr/include/curses.h \
> include/curses.h
shell> make

    There have also been reports of scheduling problems. If only one thread is running, things go slow. Avoid this by starting another client. This may lead to a 2-to-10-fold increase in execution speed thereafter for the other thread. This is a poorly understood problem with Irix threads; you may have to improvise to find solutions until this can be fixed.

    If you are compiling with gcc, you can use the following configure command: 

    CC=gcc CXX=gcc CXXFLAGS=-O3 \
./configure --prefix=/usr/local/mysql --enable-thread-safe-client \
--with-named-thread-libs=-lpthread

    On Irix 6.5.11 with native Irix C and C++ compilers ver. 7.3.1.2, the following is reported to work 

    CC=cc CXX=CC CFLAGS='-O3 -n32 -TARG:platform=IP22 -I/usr/local/include \
-L/usr/local/lib' CXXFLAGS='-O3 -n32 -TARG:platform=IP22 \
-I/usr/local/include -L/usr/local/lib' ./configure \
--prefix=/usr/local/mysql --with-innodb --with-berkeley-db \
--with-libwrap=/usr/local \
--with-named-curses-libs=/usr/local/lib/libncurses.a

    2.6.6.9 Caldera (SCO) Notes

    The current port is tested only on a ``sco3.2v5.0.4'' and ``sco3.2v5.0.5'' system. There has also been a lot of progress on a port to ``sco 3.2v4.2''.

    For the moment the recommended compiler on OpenServer is gcc 2.95.2. With this you should be able to compile MySQL with just: 

    CC=gcc CXX=gcc ./configure ... (options)
    1. For OpenServer 5.0.X you need to use gcc-2.95.2p1 or newer from the Skunkware. http://www.caldera.com/skunkware/ and choose browser OpenServer packages or by ftp to ftp2.caldera.com in the pub/skunkware/osr5/devtools/gcc directory.
    2. You need the port of GCC 2.5.x for this product and the Development system. They are required on this version of Caldera (SCO) Unix. You cannot just use the GCC Dev system.
    3. You should get the FSU Pthreads package and install it first. This can be found at http://www.cs.wustl.edu/~schmidt/ACE_wrappers/FSU-threads.tar.gz. You can also get a precompiled package from http://www.mysql.com/Downloads/SCO/FSU-threads-3.5c.tar.gz.
    4. FSU Pthreads can be compiled with Caldera (SCO) Unix 4.2 with tcpip. Or OpenServer 3.0 or Open Desktop 3.0 (OS 3.0 ODT 3.0), with the Caldera (SCO) Development System installed using a good port of GCC 2.5.x ODT or OS 3.0 you will need a good port of GCC 2.5.x There are a lot of problems without a good port. The port for this product requires the SCO Unix Development system. Without it, you are missing the libraries and the linker that is needed.
    5. To build FSU Pthreads on your system, do the following:
      1. Run ./configure in the `threads/src' directory and select the SCO OpenServer option. This command copies `Makefile.SCO5' to `Makefile'.
      2. Run make.
      3. To install in the default `/usr/include' directory, login as root, then cd to the `thread/src' directory, and run make install.
    6. Remember to use GNU make when making MySQL.
    7. If you don't start safe_mysqld as root, you probably will get only the default 110 open files per process. mysqld will write a note about this in the log file.
    8. With SCO 3.2V5.0.5, you should use FSU Pthreads version 3.5c or newer. You should also use gcc 2.95.2 or newer! The following configure command should work: 
      shell> ./configure --prefix=/usr/local/mysql --disable-shared
    9. With SCO 3.2V4.2, you should use FSU Pthreads version 3.5c or newer. The following configure command should work: 
      shell> CFLAGS="-D_XOPEN_XPG4" CXX=gcc CXXFLAGS="-D_XOPEN_XPG4" \
       ./configure \
           --prefix=/usr/local/mysql \
           --with-named-thread-libs="-lgthreads -lsocket -lgen -lgthreads" \
           --with-named-curses-libs="-lcurses"
      You may get some problems with some include files. In this case, you can find new SCO-specific include files at http://www.mysql.com/Downloads/SCO/SCO-3.2v4.2-includes.tar.gz. You should unpack this file in the `include' directory of your MySQL source tree.

    Caldera (SCO) development notes:

    • MySQL should automatically detect FSU Pthreads and link mysqld with -lgthreads -lsocket -lgthreads.
    • The Caldera (SCO) development libraries are re-entrant in FSU Pthreads. Caldera claim sthat its libraries' functions are re-entrant, so they must be reentrant with FSU Pthreads. FSU Pthreads on OpenServer tries to use the SCO scheme to make re-entrant libraries.
    • FSU Pthreads (at least the version at http://www.mysql.com/) comes linked with GNU malloc. If you encounter problems with memory usage, make sure that `gmalloc.o' is included in `libgthreads.a' and `libgthreads.so'.
    • In FSU Pthreads, the following system calls are pthreads-aware: read(), write(), getmsg(), connect(), accept(), select(), and wait().
    • The CSSA-2001-SCO.35.2 (the patch is listed in custom as erg711905-dscr_remap security patch (version 2.0.0) breaks FSU threads and makes mysqld unstable. You have to remove this one if you want to run mysqld on an OpenServer 5.0.6 machine.

    If you want to install DBI on Caldera (SCO), you have to edit the `Makefile' in DBI-xxx and each subdirectory.

    Note that the following assumes gcc 2.95.2 or newer: 

    OLD:                                  NEW:
CC = cc                               CC = gcc
CCCDLFLAGS = -KPIC -W1,-Bexport       CCCDLFLAGS = -fpic
CCDLFLAGS = -wl,-Bexport              CCDLFLAGS =

LD = ld                               LD = gcc -G -fpic
LDDLFLAGS = -G -L/usr/local/lib       LDDLFLAGS = -L/usr/local/lib
LDFLAGS = -belf -L/usr/local/lib      LDFLAGS = -L/usr/local/lib

LD = ld                               LD = gcc -G -fpic
OPTIMISE = -Od                        OPTIMISE = -O1

OLD:
CCCFLAGS = -belf -dy -w0 -U M_XENIX -DPERL_SCO5 -I/usr/local/include

NEW:
CCFLAGS = -U M_XENIX -DPERL_SCO5 -I/usr/local/include

    This is because the Perl dynaloader will not load the DBI modules if they were compiled with icc or cc.

    Perl works best when compiled with cc.

    2.6.6.10 Caldera (SCO) Unixware Version 7.0 Notes

    You must use a version of MySQL at least as recent as Version 3.22.13 because that version fixes some portability problems under Unixware.

    We have been able to compile MySQL with the following configure command on Unixware Version 7.0.1: 

    CC=cc CXX=CC ./configure --prefix=/usr/local/mysql

    If you want to use gcc, you must use gcc 2.95.2 or newer.

    Caldera provides libsocket.so.2 at ftp://stage.caldera.com/pub/security/tools for pre-OSR506 security fixes. Also, the telnetd fix at ftp://stage.caldera.com/pub/security/openserver/CSSA-2001-SCO.10/ as both libsocket.so.2 and libresolv.so.1 with instructions for installing on pre-OSR506 systems.

    It's probably a good idea to install the above patches before trying to compile/use MySQL.

    2.6.7 OS/2 Notes

    MySQL uses quite a few open files. Because of this, you should add something like the following to your `CONFIG.SYS' file: 

    SET EMXOPT=-c -n -h1024

    If you don't do this, you will probably run into the following error: 

    File 'xxxx' not found (Errcode: 24)

    When using MySQL with OS/2 Warp 3, FixPack 29 or above is required. With OS/2 Warp 4, FixPack 4 or above is required. This is a requirement of the Pthreads library. MySQL must be installed in a partition that supports long filenames such as HPFS, FAT32, etc.

    The `INSTALL.CMD' script must be run from OS/2's own `CMD.EXE' and may not work with replacement shells such as `4OS2.EXE'.

    The `scripts/mysql-install-db' script has been renamed. It is now called `install.cmd' and is a REXX script, which will set up the default MySQL security settings and create the WorkPlace Shell icons for MySQL.

    Dynamic module support is compiled in but not fully tested. Dynamic modules should be compiled using the Pthreads run-time library. 

    gcc -Zdll -Zmt -Zcrtdll=pthrdrtl -I../include -I../regex -I.. \
    -o example udf_example.cc -L../lib -lmysqlclient udf_example.def
mv example.dll example.udf

    Note: Due to limitations in OS/2, UDF module name stems must not exceed 8 characters. Modules are stored in the `/mysql2/udf' directory; the safe-mysqld.cmd script will put this directory in the BEGINLIBPATH environment variable. When using UDF modules, specified extensions are ignored@-it is assumed to be `.udf'. For example, in Unix, the shared module might be named `example.so' and you would load a function from it like this: 

    mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "example.so";

    Is OS/2, the module would be named `example.udf', but you would not specify the module extension: 

    mysql> CREATE FUNCTION metaphon RETURNS STRING SONAME "example";

    2.6.8 BeOS Notes

    We are really interested in getting MySQL to work on BeOS, but unfortunately we don't have any person who knows BeOS or has time to do a port.

    We are interested in finding someone to do a port, and we will help them with any technical questions they may have while doing the port.

    We have previously talked with some BeOS developers that have said that MySQL is 80% ported to BeOS, but we haven't heard from them in a while.

    2.6.9 Novell NetWare Notes

    We are really interested in getting MySQL to work on NetWare, but unfortunately we don't have any person who knows NetWare or has time to do a port.

    We are interested in finding someone to do a port, and we will help them with any technical questions they may have while doing the port.

    2.7 Perl Installation Comments

    2.7.1 Installing Perl on Unix

    MySQLのPerlでの使用に関するサポートは DBI/DBDクライアントインターフェスの提供で行なわれます。 「8.2 MySQL Perl API」節参照. DBI/DBDはPerl5.004かそれ以上のバージョンが必要になります。 古いバージョンのPerlでは動きません。

    MySQL の Perl support にはここまでで既にインストールが済んでいる筈の MySQL のクライアントプログラミングサポートが必要となります。 もしも RPM ファイルからインストールをされているのならば クライアントプログラムはクライアントRPMにあるものの、 クライアントプログラミングサポートはデベロッパー RPM にあります。 まずデベロッパー RPM をインストールされたがどうかお確かめ下さい。

    バージョン3.22.8からは Perl support がメインの MySQL 配布ファイルとは別になっています。 もし Perl support が必要であれば http://www.mysql.com/downloads/api-dbi.html. からお取りください。

    Perl関係プログラムのの配布はtar形式圧縮ファイルとして行われており、 ファイル名が `MODULE-VERSION.tar.gz' の形式になっています。 ここで、MODULEはモジュール名称、VERSIONはバージョン番号を表しています。 Data-Dumper、DBI、及び、Msql-Mysql-modulesを入手してインストールしてください。 インストール手順は以下に示す通りです。なお、ここではData-Dumperのみの手順が示されていますが、 他のモジュールについても同様な手順でインストールできます。

    1. 以下のようにして作業ディレクトリで配布ファイルを伸長・展開してください。 
      shell> gunzip < Data-Dumper-VERSION.tar.gz | tar xvf -
      This command creates a directory named `Data-Dumper-VERSION'.
    2. 展開先のトップディレクトリーに移動します。 
      shell> cd Data-Dumper-VERSION
    3. コンパイル＆ビルドを行います。 
      shell> perl Makefile.PL
shell> make
shell> make test
shell> make install

    出来上がったモジュールの動作を確認するためにmake testのコマンドは重要になってきます。 このコマンドをMsql-Mysql-modulesをインストールしている時に使ってみてください。 MySQLサーバが動いていなければ失敗することになります。

    MySQLをバージョンアップした際に DBI が core ダンプした場合は 必ず Msql-Mysql-modules を再コンパイルしてインストールしなおしてください。 そうでなくても MySQL のバージョンを変更した場合は再コンパイルしたほうが賢明です。

    貴方のユーザ権限ではPerlのモジュールをインストールできない場合でも 以下の例のようにしてローカルディレクトリにモジュールをインストールできます。 

    http://www.iserver.com/support/contrib/perl5/modules.html

    Installing New Modules that Require Locally Installed Modules. という見出しの文書をご覧下さい。

    2.7.2 Installing ActiveState Perl on Windows

    DBDモジュールとActiveState Perlをインストールするには以下の手順で行います。

    • ActiveState Perlはこのサイトからダウンロードできます。 http://www.activestate.com/Products/ActivePerl/ and install it.
    • 先ず、DOSのシェルを立ち上げてください。
    • 必要であれば次のようにHTTP_proxy変数をセットしてください。 
      set HTTP_proxy=my.proxy.com:3128
    • 次のようにPPMプログラムを立ち上げます。 
      C:\> c:\perl\bin\ppm.pl
    • DBIがインストールされていなければインストールします。 
      ppm> install DBI
    • ここまで来たら次のようなコマンドを実行してください。 
      install \
ftp://ftp.de.uu.net/pub/CPAN/authors/id/JWIED/DBD-mysql-1.2212.x86.ppd

    以上でActiveState Perlのバージョン5.6がとりあえず動くことになります。

    もしも動作しない場合は次のように MyODBC ドライバーをインストールして ODBC経由でMySQLサーバに接続する必要があります。 

    use DBI;
$dbh= DBI->connect("DBI:ODBC:$dsn","$user","$password") ||
  die "Got error $DBI::errstr when connecting to $dsn\n";

    2.7.3 Installing the MySQL Perl Distribution on Windows

    MySQL Perlの配布パッケージにはDBI、DBD:MySQL、そして、DBD:ODBCが含まれています。

    • Windows 用 Perl の配布パッケージをこのサイトからダウンロードしてください。 http://www.mysql.com/downloads/os-win32.html.
    • C:で配布パッケージを解凍してください。`C:\PERL'に必要なファイルが現れます。
    • 次にコマンドパスに`C:\PERL\BIN'を追加してください。
    • ディレクトリ、`C:\PERL\BIN\MSWIN32-x86-thread' か `C:\PERL\BIN\MSWIN32-x86' もコマンドパスに追加してください。
    • perl -vと入力してperlの起動をチェックしてみましょう。

    2.7.4 Problems Using the Perl DBI/DBD Interface

    Perl が "`../mysql/mysql.so'を見つけられない" というメッセージを出した場合、 それは多分 Perl のシェアードライブラリ `libmysqlclient.so' を見つけることが出来ないのでしょう。

    これは以下のような方法で解決できます。

    • Msql-Mysql-modulesは通常、perl Makefile.PL とコンパイルされますが、 perl Makefile.PL -static -configとコンパイルしてください。
    • `libmysqlclient.so'をシェアードライブラリが置いてあるディレクトリにコピーしてください (通常は`/usr/lib'や`/lib'といったディレクトリになるはずです)。
    • Linux の場合は `/etc/ld.so.conf' ファイルを使って `libmysqlclient.so' のあるディレクトリを パスに追加することが出来ます。
    • `libmysqlclient.so'のあるディレクトリをLD_RUN_PATHに追加することによって そこへのパスが追加されます。

    DBD-mysql が次のようなエラーを発生する場合があります。 この原因の一つは gcc(又はgccでコンパイルされた古いバイナリ配布パッケージ)をお使いのケースです。 

    /usr/bin/perl: can't resolve symbol '__moddi3'
/usr/bin/perl: can't resolve symbol '__divdi3'

    `mysql.so' ライブラリをビルドする時に -L/usr/lib/gcc-lib/... -lgcc を リンクコマンドに追加してください(makeコマンド実行時の出力をチェックすれば確認できます。)。 オプション-Lで指定されるのはlibgcc.aのあるディレクトリになります。

    もう一つの原因はPerlとMySQLのどちからがgccでコンパイルされており、どちらかがそうでない場合です。 この場合はどちらもgccでコンパイルし、この不一致を解消すれば解決します。

    Msql-Mysql-modulesがテストで次のようなエラーを出した時、 

    t/00base............install_driver(mysql) failed:
Can't load '../blib/arch/auto/DBD/mysql/mysql.so' for module DBD::mysql:
../blib/arch/auto/DBD/mysql/mysql.so: undefined symbol:
uncompress at /usr/lib/perl5/5.00503/i586-linux/DynaLoader.pm line 169.

    これは、ファイル圧縮用ライブラリ -lz へのパスを追加すれば解決いたします。 `lib/DBD/mysql/Install.pm' に以下のような変更を行ってください。 

    $sysliblist .= " -lm";

to

$sysliblist .= " -lm -lz";

    After this, you must run 'make realclean' and then proceed with the installation from the beginning.

    このあと'make realclean'を実行し、最初からインストールをやり直す必要があります。

    Caldera (SCO) のようなダイナミックリンクが使用できないシステムで Perl モジュールを使用する際は DBIやDBD-mysqlをスタティックリンクしたバージョンのPerlを作成する必要があります。 DBDをスタティックにリンクするには、Perlのインストールディレクトリに DBIのプログラムを置きDBDをリンクし、インストールします。

    Caldera (SCO) では以下のような環境変数をセットする必要があります。 

    shell> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/progressive/lib
or
shell> LD_LIBRARY_PATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:\
/usr/progressive/lib:/usr/skunk/lib
shell> LIBPATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:\
/usr/progressive/lib:/usr/skunk/lib
shell> MANPATH=scohelp:/usr/man:/usr/local1/man:/usr/local/man:\
/usr/skunk/man:

    DBI をスタティックにリンクしたPerlを作成するためには、 先ず以下のコマンドを DBI がインストールされているディレクトリで実行してください。 

    shell> perl Makefile.PL -static -config
shell> make
shell> make install
shell> make perl

    次に新しいPerlをインストールします。 通常 make perl でインストールに必要なファイル類を作成しますが、 Caldera (SCO)の場合は make -f Makefile.aperl inst_perl MAP_TARGET=perl のように行う必要があります。

    次に、ここで作成された Perl で目的の DBD::mysql をスタティックにリンクされた Perl を作成するために使います。 Msql-Mysql-modules がインストールされたディレクトリで以下のようなコマンドを実行してください。 

    shell> perl Makefile.PL -static -config
shell> make
shell> make install
shell> make perl

    最後に、この新しいPerlプログラムをインストールしてください。 make perlで必要なコマンドを再確認することができます。

    Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Introduction.html0100644000175100001560000065071210021471264017146 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 1 概要 Go to the first, previous, next, last section, table of contents.

    1 概要

    MySQL (TM) ソフトウェアはとても高速で、マルチスレッド、マルチユーザの、頑丈な SQL (Structured Query Language)データベースサーバです。 MySQL Server は、大量に配備されるフトウェアへ組み込まれるときと同じように、 ミッションクリティカルで高負荷な生産システム用に意図されています。 MySQL は MySQL AB の商標です。

    MySQL ソフトウェア は デュアルライセンス です。 あなたは、MySQL を GNU GENERAL PUBLIC LICENSE (http://www.gnu.org/licenses/) にしたがって、 Open Source/Free Software として利用できます。 あるいは、GPL の条件が合わない場合には、 コマーシャルライセンスを MySQL AB から購入することも可能です。 「1.4 MySQL ライセンスとサポート」節参照.

    MySQL ウェブサイト (http://www.mysql.com/) には MySQL ソフトウェア についての最新情報があります。

    次のリストはマニュアルのなかで特に興味を引くいくつかの節を説明しています:

    重要:

    エラー(バグ)レポート、質問、コメントは メーリングリスト mysql@lists.mysql.com に送ってください。 「1.6.1.3 バグや問題を報告する方法」節参照。

    バグレポートを生成するためには mysqlbug スクリプトを使用すべきです。

    ソースディストリビューションでは、mysqlbug スクリプトは `scripts' ディレクトリ に見つけることができます。バイナリディストリビューションでは、mysqlbug は `bin' ディレクトリ(MySQL-server RPM パッケージでは `/usr/bin') に見つけることができます。

    MySQL Server のセキュリティバグを発見した場合は、 security@mysql.com に email を送ってください。

    1.1 このマニュアルについて

    これは MySQL のリファレンスマニュアルです; これは MySQL バージョン 4.0.12 について記述しています。 機能上の変更は、かならずそのバージョンを示されます。 そのため、MySQLソフトウェアの古いバージョンを使っていても、 このマニュアルは通用します。

    これはリファレンスマニュアルであるので、一般的な SQL やリレーショナルデータベース概念の説明書ではありません。

    MySQL Database Software は発展中なので、マニュアルは頻繁に更新されます。そのため、 オンラインで参照しない限り、このバージョンが期限切れである可能性があります。 このマニュアルの最新バージョンは http://www.mysql.com/documentation/ に多 様な形式で置いてあります。 このマニュアルは現在 HTML, PDF, Windows HLP バージョンがあります。

    プライマリドキュメントは Texinfo ファイルです。HTML バージョンは texi2html の変更されたバージョンで自動的に提供されます。プレーン テキストと Info バージョンは makeinfo で提供されます。PostScript バージョンは texi2dvi と divps を使用して提供されます。PDF バージョンは pdftex で提供されます。

    マニュアル内の情報を見つけるのがつらいなら、 検索可能なバージョン http://www.mysql.com/doc/ を 試せます。

    このマニュアルへの追加または修正に関連する提案がある場合には、それらを マニュアルチーム docs@mysql.com に 送ってください。

    このマニュアルは当初、David Axmark, Michael (Monty) Widenius によって書かれました。 現在は Michael (Monty) Widenius, Arjen Lentz, Paul DuBois によって維持されています。他の貢献者については 「C Credits」節 を参照してください。

    日本語訳は、以下の方々により行われました。 (ハンドル名だけ書きます。敬称略。翻訳サーバに登録した順 :) )：

    • とみたまさひろ
    • hama
    • dale
    • kippara
    • kenji
    • aoki
    • tok21108
    • こむら
    • tamori
    • ynakata
    • Ami
    • bfujii
    • Tomo-p
    • tanabe
    • takayuki.w
    • tomoyuki
    • piyo
    • toshibo

    このマニュアルの著作権(2003)は、スウェーデンの会社 MySQL ABが所有しています。 「1.4.2 Copyrights and Licenses Used by MySQL」節参照.

    1.1.1 このマニュアル中で使用されている表記

    このマニュアルは特定の印刷上の表記を使用しています:

    constant
    固定幅フォントは次のものに使用されます。コマンド名, オプション; SQL ステー トメント; データベース名, テーブル名, フィールド名; C と Perl コード; 環境変数。 例: ``mysqladmin がどのように動作するかを見るためには、 --help オプションをつけて起動してください。''
    `filename'
    引用符で括られた固定幅フォントはファイル名とパス名に使用されます。例: `` ディストリビューションは `/usr/local' ディレクトリ配下にインストールされます。''
    `c'
    引用符で括られた固定幅フォントは文字シーケンスを示すためにも使用されます。 例: ``ワイルドカードを指定するためには、`%' 文字を使用してください。''
    italic
    イタリックフォントは強調のために使用されます, このように。
    boldface
    ボールドフォントは table headings と、 特に強い強調を伝えるために使用されます。

    コマンドが特定のプログラムによって実行されることを意味することを表すときには、 コマンドと共に表示されるプロンプトによって、そのプログラムを表します。例えば、 shell> は、あなたのログインシェルから実行するコマンドを表し、 mysql> は mysql クライアントプログラムから実行するコマンドを表します:

    シェルコマンドは Bourne シェル構文で示されます。csh 形式のシェ ルを使用している場合は、わずかに変更してコマンドを発行する必要があるでしょ う。例えば、環境変数を設定してコマンドを実行するシーケンスは、Bourne シェ ル構文では次のようになります: 

    shell> VARNAME=value some_command

    csh では、次のようなシーケンスを実行してください: 

    shell> setenv VARNAME value
shell> some_command

    データベース名、テーブル名、フィールド名はコマンドの中で置換しなければいけない ことがよくあります。このような置換が必要なことを示すために、このマニュア ルは db_name、tbl_name、col_name を使用します。 例えば、次のような文を見た場合: 

    mysql> SELECT col_name FROM db_name.tbl_name;

    これは、同様の文を入力するためには、おそらく次のように、あな た自身のデータベース名, テーブル名, フィールド名を与えることを意味します: 

    mysql> SELECT author_name FROM biblio_db.author_list;

    SQL 文は大文字でも小文字でも記述できます。このマニュアルで は大文字で記述します。

    構文の説明中では、角括弧(`[' と `]')はオプションの単語や節であ ることを示すために使用されます。次の文、IF EXISTSはオプションです: 

    DROP TABLE [IF EXISTS] tbl_name

    構文要素がいくつかのものからなる場合、垂直バー(`|')で区切られます。 選択セットから一つのメンバを選ぶことができるときは、角括弧中に列挙され ます。(`[' と `]'): 

    TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)

    選択セットから一つのメンバを選ぶ必要があるときは、波括弧(`{' と `}')中に列挙されます: 

    {DESCRIBE | DESC} tbl_name {col_name | wild}

    1.2 MySQL とは何か

    MySQLは、もっとも有名な オープンソース SQLデータベースで、 MySQL AB によって開発、供給されています。MySQL AB は MySQL データベースに関わるサービスを提供するビジネスを構築する 営利会社です。 「1.3 MySQL AB とは何か」節参照.

    MySQL ウェブサイト(http://www.mysql.com/)は、MySQL と MySQL AB に ついての最新情報を提供しています。

    MySQL はデータベース管理システムです。
    データベースはデータの集まりで構成されています。絵画のギャラリーの単純な ショッピングリストや共通ネットワーク内での膨大な量の情報からもなり得ます。 コンピュータデータベースに格納されたデータの追加、アクセス、処理のために は、MySQL サーバのようなデータベース管理システムが必要です。コンピュー タは大量のデータの処理がたいへん得意なので、データベース管理システムは 単独で動作するユーティリティや他のアプリケーションの一部として、コンピュー タの中で中心的な役割を演じています。
    MySQL は関係データベース管理システムです。
    関係データベースはデータを大きな格納場所に全てのデータを置くのではなく、 別々のテーブル内に格納します。これは速度と柔軟性を追加します。要求された いくつかのテーブルからデータを結合することを可能とする関係を定義すること により、テーブルがリンクされます。MySQL の SQL 部分は "構造化問合せ 言語 (Structured Query Language)" を表しています。これは、データベー スのアクセスに使用される最も有名な標準言語です。
    MySQL ソフトウェアは オープンソース です。
    オープンソースの意味は誰でも使用し変更することができるということです。誰 でも MySQL ソフトウェアをインターネットからダウンロードし、無償で使 えます。その気があれば誰でも必要に応じてソースコードを調べ、 変更できます。MySQL ソフトウェア は GPL (GNU General Public License) http://www.gnu.org/licenses/ にしたがいます。これは、様々な状況でそ のソフトウェアで行えることと行えないことを定義しています。もし GPL を嫌だと感じていたり、MySQL を商用アプリケーションに組み込む必 要があるなら、商用ライセンス版を私たちから購入することができます。 「1.4.3 MySQL Licenses」節参照.
    何故 MySQL データベースサーバを使用するのか？
    MySQL Database Server はとても速く、信頼でき、簡単に使用できます。それがあなた が探しているものなら、試してみるべきです。MySQL Server は、私たちのユー ザと協力して開発されたとても実用的な機能がひとそろいあります。私たちのベ ンチマークページ上で、MySQL Server と他のいくつかのデータベース管理シ ステムの性能比較を見つけることができます。 「5.1.4 The MySQL Benchmark Suite」節参照. MySQL Server は、既存のソリューションよりも速く、とても大きなデータベー スを処理するために独自に開発され、そして、高い需要がある実運用環境で何年間もの使用に耐え てきました。不断の開発下で、MySQL Server は今日、 豊富でとても有用な機能セットを提供します。MySQL は、結合性、速 度、セキュリティでインターネット上でのデータベースアクセスに高く適合しま す。
    MySQL の技術機能。
    詳しい技術情報については、 「6 MySQL Language Reference」節。MySQL Database Software は、様々なバッ クエンドをサポートするマルチスレッド SQL サーバ、いくつかのクライアント プログラム、ライブラリ、管理ツール、プログラミングインタフェース(API)から成る クライアント／サーバシステムです。 また、MySQL サーバ をアプリケーションに リンクできるマルチスレッドライブラリとしても提供していて、これにより、 より小さく、速く、管理しやすい製品が作れます。
    MySQL は多くの貢献ソフトを持っています。
    おそらく、すでに MySQL Database Server をサポートする、あなたの好きなアプリケー ション／言語を見つけることができるでしょう。

    MySQL の公式な発音は ``My Ess Que Ell'' です(MY-SEQUEL ではあり ません)。 しかし MY-SEQUEL と発音する人を正すことは避けています。

    1.2.1 MySQL の歴史

    最初は、私たち自身の速くて低レベルな (ISAM) ルーチンを使用したテーブルへ 接続するために、 mSQL を使用するつもりでした。 しかし、いくつかのテストの後、私たちは mSQL は私たちが必要とするほど高速ではなく、柔軟でないという 結論に至りました。この結果、mSQL とほとんど同じ API インタフェー スをもつ、私たちのデータベースへの新しい SQL インタフェースに帰結しました。 この API はサードパーティコードの移植を簡単にするために選択されました。

    MySQL の名前の由来は完全には明らかではありません。私たちのベース ディレクトリと多くのライブラリとツールは接頭辞 ``my'' を 10 年以上も使っ ています。しかし、Monty の娘(何年か若い)も My という名前です。そのため、 この2つのどちらが MySQL に名前を与えたかは、私たちにとっても未だ 謎です。

    1.2.2 MySQL の主な機能

    MySQL Database Software の重要な特徴のいくつかを以下の項目に挙げます。 「1.5 MySQL 4.x はやわかり」節参照.

    内部と移植性
    • C と C++ で書かれています。広範な種類のコンパイラでテストされています。
    • 多くの種類のプラットフォームで動作します。 「2.2.5 MySQL がサポートする OS」節参照。
    • 可搬性のために GNU Automake, Autoconf, Libtool を使用しています。
    • C, C++, Ruby, Eiffel, Java, Perl, PHP, Python そして Tcl に対する API。 「8 MySQL APIs」節参照.
    • カーネルスレッドを使用する完全なマルチスレッド。これは可能ならば簡単に 複数の CPU を使用できることを意味します。
    • インデックス圧縮付きのとても速い B-tree ディスクテーブル。
    • とても速いスレッドベースのメモリ割り当てシステム。
    • 最適化された one-sweep multi-join を使用する高速な結合。
    • 一時テーブルとして使用されるメモリ内ハッシュテーブル。
    • SQL 関数は高度に最適化されたクラスライブラリを通して実装されていて、限界に 近いほど高速化されています。 普通、クエリの初期化の後に は、全くメモリ割り当てはありません。
    • MySQL は市販のメモリリーク検出製品 Purify と、 Valgrind とよばれる GNU のツール(http://developer.kde.org/~sewardj/) で テストされています。
    カラムの型
    • 多くのフィールド型: 1, 2, 3, 4, 8 バイト長の符号付き/符号無し整数, FLOAT, DOUBLE, CHAR, VARCHAR, TEXT, BLOB, DATE, TIME, DATETIME, TIMESTAMP, YEAR, SET, ENUM 型. 「6.2 フィールド型」節参照.
    • 固定長と可変長のレコード。
    • 全てのフィールドはデフォルト値をもちます。 テーブル項目のサブセットを挿入するた めに INSERT を使用でき、明示的に値が与えられていないフィールドはそのデ フォルト値が設定されます。
    コマンドと関数
    • クエリの SELECT と WHERE 節で全ての演算子と関数が使えます。例: 
      mysql> SELECT CONCAT(first_name, " ", last_name)
    -> FROM tbl_name
    -> WHERE income/dependents > 10000 AND age > 30;
    • SQLの GROUP BY と ORDER BY 節の完全なサポート。グループ関数 (COUNT(), COUNT(DISTINCT ...), COUNT(DISTINCT ...), AVG(), STD(), SUM(), MAX() and MIN() ) のサポート。
    • ANSI SQL と ODBC 構文で LEFT OUTER JOINとRIGHT OUTER JOIN が使えます。
    • SQL92 標準にあるようなテーブルとフィールドのエイリアス名。
    • DELETE, INSERT, REPLACE, UPDATE は 変更された(影響を受けた)行の数を返します。 サーバ接続時にフラグを設定することにより、代わりに適合したレコード数を返す ことも可能です。
    • MySQL 固有の SHOW コマンドはデータベース、テーブル、イン デックスについての情報を取出すために使用できます。EXPLAIN コマン ドはオプティマイザがどのようにクエリを解析するかを決定するために使用 できます。
    • 関数名はテーブル名やフィールド名と衝突しません。例えば ABS は正しいフィールド 名です。制限は、関数呼び出しに、関数名とそれに続く `(' の間に空白が 許されないことだけです。 「6.1.7 Is MySQL Picky About Reserved Words?」節参照.
    • 同一クエリ内に異なるデータベースからのテーブルを混在できます (バージョン 3.22)。
    セキュリティ
    • とても柔軟で安全な特権システムとパスワードシステム。 ホストベースの証明が可能です。 サーバに接続するときの全てのパスワードトラフィックは暗号化されているためパ スワードは安全です。
    拡張性と限界
    • 大きなデータベースの操作。私たちは、50,000,000 レコードを含むいくつかのデー タベースで MySQL を使用しています。そして、60,000 テーブル、約 5,000,000,000 レコードを MySQL Server を使用しているユーザを知っています。
    • テーブル毎に 32 個のインデックスを利用できます。各インデックスは 1 から 16 個 のフィールドまたはフィールドの一部からなります。最大インデックス長は 500 バイトです (これは MySQL Server のコンパイル時に変更できます)。インデックスは CHAR または VARCHAR フィールドの先頭部分を使用できます。
    接続性
    • クライアントは、TCP/IP ソケット、UNIX ソケット(UNIX)、名前つきパイプ(NT)を 使用して MySQL サーバと接続します。
    • Win32 の ODBC (Open-DataBase-Connectivity) (ソースつき)。全ての ODBC 2.5 関数と他の多く。あなたの MySQL サーバに接続するために、例え ば Access を使用できます。 「8.3 MySQL ODBC サポート」節参照.
    地域化
    • サーバは，クライアントに対し，多言語のエラーメッセージを提供することができます。 「4.6.2 Non-English Error Messages」節参照.
    • 異なるキャラクタセットの完全なサポート。ISO-8859-1 (Latin1), big5, ujis など。 例えば、スカンジナビア語文字 @ringaccent{a}, @"a そして @"o はテーブル名や フィールド名として許されます。
    • 全てのデータは 選択されたキャラクタセットの形式で保存されています。通常文字列フィールド の全ての比較はケース非依存です。
    • ソートは、MySQL サーバ起動時に、選択されたキャラクタセットに にしたがって行われます。(デフォルトは、スウェーデン語の方法)。 ソース内に新しいソート順序配列を追加することで、こ れは変更可能です。とても先進的なソートの例を見るには、Czech ソートコード を見てください。 MySQL Server は多くの種類のキャラクタセットをサポート し、コンパイル時や実行時に指定できます。
    クライアントとツール
    • myisamchk を含んでいます。これは、テーブル検査、最適化、修復のため のとても速いユーティリティです。 myisamchk のすべての機能は、SQLインタフェースからも使えます。 「4 データベース管理」節参照.
    • 全ての MySQL プログラムは --help と -? オプションでオンラインヘルプを呼び出せます。

    1.2.3 MySQL はどれくらい安定か？

    この節では、``MySQL Server はどれくらい安定か？'' と ``私はこのプロジェ クトの MySQL Server に依存できるか？'' という質問について回答します。

    私たちはここで、いくつかの問題を明らかにし、多くの人に関係すると思われるさ らに重要な質問のいくつかを回答することを試みます。この節は、メーリングリ スト(そこではとても活発にバグが報告されています)から取り込まれた情報が一 緒に置かれています。

    80年代初期からあるオリジナルのコードの中心部は、安定したコードの基礎とな っています。ISAMテーブル形式は、後方互換性が保たれています。TcX (MySQL AB の前身)では、MySQL は 1996 中頃から私たちのプロジ ェクトで何の問題もなく動いていました。MySQL Database Software が 広く公にリリースされたとき、私たちは、MySQL 内に ``テストされていないコード '' の部分があることに注意しました。これは、私たちとは異なる方法でクエリを 作成する新しいユーザによってすぐに見つけられました。新しい各リリースは、 (多くの新しい機能を持っているのに)前のものよりも問題は少なくなります。そ して次のリリースの一つを ``安定'' と呼ぶことができるように私たちは望んでい ます。

    MySQL Server の各リリースは実用的で、ユーザが ``グレイゾーン'' か らのコードの使用を開始するときにだけ問題があります。当然、外部のユーザは、 何がグレイゾーンかを知ることができません; この節で現在知られているこれら を示してみます。説明は MySQL Server の 3.23.x バージョンで扱われ ます。知られていて報告されているバグは全て最新のバージョンで修正されてい ます。バグ節に書かれているバグは除きます。それらは ``設計'' 関連のもので す。 「1.7.5 MySQLでの既知のエラーと欠けているデザイン」節参照.

    MySQL Server は複数の階層と様々な独立モジュールで書かれています。 これらのモジュールは、それぞれがどのようにテストされているかとともに次に 列挙されています:

    Replication -- Gamma
    レプリケーションを使用した大規模なサーバクラスタは製品として使用され良い 結果をもたらしています。拡張されたレプリケーション機能に対する取り組みは MySQL 4.x でも引き続き行われます。
    InnoDB tables -- Stable (3.23 では 3.23.49から)
    InnoDB storage engines は MySQL 3.23 ツリーでは version 3.23.49 から安定です。InnoDB は大規模で負荷の大きい製品システムで 使用されています。
    BDB tables -- Gamma
    Berkeley DBはとても安定したコードですが、未だに BDB トラン ザクションstorage engines インターフェースに対し MySQL Server で は改良を加えている途中であり、他のテーブルタイプと同等に扱われるまでには もう少し時間がかかりそうです。
    FULLTEXT -- Beta
    テキストの検索は動作しているように見えますが、まだ広く使用されていません。 重要な拡張を MySQL 4.0 で行っています。
    MyODBC 3.51 (uses ODBC SDK 3.51) -- Gamma
    だんだん広く使われるようになっています。アプリケーションに関係したり、 ODBCドライバーか、その下のデータベースサーバに関係ない問題が出ています。
    MyISAM テーブルの自動復旧 -- Gamma
    これは、MyISAM ストレージエンジンの新しいコードに対してだけです。 新しい MyISAM ストレージエンジンは、テーブルをオープンするとき、 前にそのテーブルが正しくクローズされたか調べ、正しくクローズされていない ときは自動的に検査と復旧を実行します。
    Bulk-insert -- Alpha
    MySQL 4.0 での MyISAM テーブルへ大量のレコードを高速に挿入 する新しい機能です。
    ロック -- ガンマ
    これはとてもシステムに依存しています。いくつかのシステムでは、これは、標 準 OS ロック (fcntl()) を使用するため大きな問題があります。これら の場合では、MySQL デーモンを --skip-external-locking フラグつきで 動かすべきです。知られている問題は、いくつかの Linux システムと NFS マウ ントされたファイルシステム使用時の SunOS です。

    MySQL AB は代金を支払った顧客のために 高サポートを提供しています。 しかし MySQL メーリングリストは通常、全ての一般的な質問に回答を提 供しています。バグは通常すぐにパッチで修正され、深刻なバグには、ほとんど いつも新しいリリースがあります。

    1.2.4 MySQLではどれだけテーブルを大きくできるの？

    MySQL Version 3.22では、最大テーブルサイズに 4Gバイトという制限が ありました。MySQL Version 3.23から採用された新しい MyISAM では、最大テーブルサイズは800万テラバイト( 2 ^ 63 バイト)に拡張されまし た。

    ただし、OSの側にも、ファイルサイズの制限が存在していることには注意して下 さい。いくつか例を示します：

    オペレーティングシステム ファイルサイズの制限
    Linux-Intel 32 bit 2Gバイト, 4Gバイト あるいはそれ以上, Linux のバージョンによる。
    Linux-Alpha 8Tバイト (?)
    Solaris 2.5.1 2Gバイト (パッチにより 4G に対応)
    Solaris 2.6 4Gバイト (フラグで変更可能)
    Solaris 2.7 Intel 4Gバイト
    Solaris 2.7 UltraSPARC 512Gバイト

    Linux 2.2 では、ext2ファイルシステム用のLFSパッチを適用することで、2G バ イト以上のテーブルを使用することができます。Linux 2.4ではReiserFS用の同 様のパッチが存在し、大きなファイルを扱うことができるようになります。(訳 注： Linux 2.4.1 以上では、最初から ReiserFS がカーネルのソースに組み込 まれていますし、2.4.16 以上では、ext3 もカーネルのソースに組み込まれまし た)

    以上からわかるように、MySQL の最大テーブルサイズはOSの制限によっ て決まることがほとんどです。

    デフォルトでは、MySQL の最大テーブルサイズは4Gに設定されています。 あるテーブルの最大テーブルサイズは、SHOW TABLE STATUS コマンドか、 myisamchk -dv table_name によって確認することができます。 「4.5.6 SHOW 構文」節参照.

    もしも4G 以上のテーブルが必要な場合には（加えて、OSがそれをサポートして いる場合には）、テーブルを作る際に、AVG_ROW_LENGTH と MAX_ROWS パラメータを設定することができます。 「6.5.3 CREATE TABLE 構文」節参照. テーブル作成後に、ALTER TABLE で変更することもできます。 「6.5.4 ALTER TABLE 構文」節参照

    読み込み専用の大きなテーブルが必要なときは、myisampackを使って複 数のテーブルを一つにまとめた上で圧縮することができます。myisampack は、テーブルの大きさをだいたい50%程度まで圧縮できます。結果として、より 大きなテーブルを作ることが可能となるでしょう。 「4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ」節参照.

    MyISAMデータファイルに対する、OSのファイル制限を回避するのに、 RAID オプションを使うこともできます。 「6.5.3 CREATE TABLE 構文」節参照.

    MERGE ライブラリ -- 同じ構造のテーブルをひとまとめに扱う機能を提 供します -- を使用するという解決法も考えられるでしょう。 「7.2 MERGE Tables (3.23.25以上)」節参照.

    1.2.5 2000 年対応

    MySQL Server 自身は 2000 年問題(Y2K)に対して何の問題も持っていま せん:

    • MySQL Server は UNIX 時間関数を使用し、2069 年まで日付には 何の問題もありません; 全ての2桁の年は 1970 から 2069 の範 囲にあると見なされます。これは、year フィールド内に 01 を 格納する場合、MySQL Server はそれを 2001 として扱うという ことを意味します。
    • 全ての MySQL 日付関数は一つのファイル `sql/time.cc' に格納さ れ、2000年安全であるようにとても注意深くコード化されています。
    • MySQL 3.22 以降のバージョンでは、新しい YEAR フィールド型 は 0 と 1901 から 2155 までの年を1バイトで格納でき、 2桁または4桁で表示できます。

    2000年安全でない方法で MySQL Server を使用するアプリケーションで は問題になります。例えば、多くの古いアプリケーションは4桁値ではなく2桁値 (これは曖昧です)を使用して年を格納し操作します。この問題は、00 ま たは 99 のような値を ``欠けている'' 値の表われとして使用するアプ リケーションによって作られます。

    あいにく、これらの問題を修正するのは困難です。様々なアプリケーションが様々 なプログラマによって書かれていて、その各々が慣習と日付操作関数の様々な組 み合わせを使用するからです。

    これは、MySQL Server が 2030 年までの日付に何の問題もないことを示 す簡単なテストです: 

    mysql> DROP TABLE IF EXISTS y2k;
Query OK, 0 rows affected (0.01 sec)

mysql> CREATE TABLE y2k (date DATE,
    ->                   date_time DATETIME,
    ->                   time_stamp TIMESTAMP);
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO y2k VALUES
    -> ("1998-12-31","1998-12-31 23:59:59",19981231235959),
    -> ("1999-01-01","1999-01-01 00:00:00",19990101000000),
    -> ("1999-09-09","1999-09-09 23:59:59",19990909235959),
    -> ("2000-01-01","2000-01-01 00:00:00",20000101000000),
    -> ("2000-02-28","2000-02-28 00:00:00",20000228000000),
    -> ("2000-02-29","2000-02-29 00:00:00",20000229000000),
    -> ("2000-03-01","2000-03-01 00:00:00",20000301000000),
    -> ("2000-12-31","2000-12-31 23:59:59",20001231235959),
    -> ("2001-01-01","2001-01-01 00:00:00",20010101000000),
    -> ("2004-12-31","2004-12-31 23:59:59",20041231235959),
    -> ("2005-01-01","2005-01-01 00:00:00",20050101000000),
    -> ("2030-01-01","2030-01-01 00:00:00",20300101000000),
    -> ("2050-01-01","2050-01-01 00:00:00",20500101000000);
Query OK, 13 rows affected (0.01 sec)
Records: 13  Duplicates: 0  Warnings: 0

mysql> SELECT * FROM y2k;
+------------+---------------------+----------------+
| date       | date_time           | time_stamp     |
+------------+---------------------+----------------+
| 1998-12-31 | 1998-12-31 23:59:59 | 19981231235959 |
| 1999-01-01 | 1999-01-01 00:00:00 | 19990101000000 |
| 1999-09-09 | 1999-09-09 23:59:59 | 19990909235959 |
| 2000-01-01 | 2000-01-01 00:00:00 | 20000101000000 |
| 2000-02-28 | 2000-02-28 00:00:00 | 20000228000000 |
| 2000-02-29 | 2000-02-29 00:00:00 | 20000229000000 |
| 2000-03-01 | 2000-03-01 00:00:00 | 20000301000000 |
| 2000-12-31 | 2000-12-31 23:59:59 | 20001231235959 |
| 2001-01-01 | 2001-01-01 00:00:00 | 20010101000000 |
| 2004-12-31 | 2004-12-31 23:59:59 | 20041231235959 |
| 2005-01-01 | 2005-01-01 00:00:00 | 20050101000000 |
| 2030-01-01 | 2030-01-01 00:00:00 | 20300101000000 |
| 2050-01-01 | 2050-01-01 00:00:00 | 00000000000000 |
+------------+---------------------+----------------+
13 rows in set (0.00 sec)

    これは、DATE と DATETIME 型は未来のいかなる日付において問 題のないことを示します (これら日付は 9999 年まで扱えます)

    TIMESTAMP 型は、時刻を保存しますが、2030-01-01 までです。

    TIMESTAMP は 32-bit マシンで(signed value)は 1970 から 2030 の範囲です。64-bit マシンでは、 2106 年(unsigned value)まで扱えれます。

    MySQL Server は 2000年対応ですが、曖昧でない入力を提供するのはあ なたの責任です。曖昧な日付の入力データ（2桁の年の値）の扱いについての MySQL Server の規則については 「6.2.2.1 西暦２０００年問題とデータ型」節 を参照してください。

    1.3 MySQL AB とは何か

    MySQL AB は、MySQL の創始者と主な開発者の会社です。

    MySQL AB は、最初は、David Axmark、Allan Larsson、Michael Monty Wideniusらによってスウェーデンに設立されました。

    MySQL サーバの開発者は、この会社に雇われています。わたしたちは、 世界中の1ダースものの国々の人によるバーチャルな組織です。わたしたちは、 毎日、広くネットを使って、互いに連絡しあい、また、ユーザや支援者やパート ナーと連絡しています。

    私たちは、MySQL の開発と私たちのデータベースを新しいユーザに広げるこ とに専念しています。MySQL AB はMySQLサーバソースコードの著 作権, MySQL logo の著作権, MySQL 商標権,このMySQL マニュアルの著 作権を所有します。 「1.2 MySQL とは何か」節参照.

    MySQLの核の価値は、わたしたちの MySQL と Open Source に対する献身を示しています。

    私たちは MySQL Database Software を次のようにしています。

    • 世界で一番良く、最も使用されるデータベース
    • 全てが有効で全てを与えられる
    • 簡単に使用できる
    • 速度と安全が残る限り改良を続ける
    • 使って楽しく、改良して楽しい
    • バグから解放される

    MySQL AB と MySQL AB の人々は次を行います。

    • オープンソース 哲学を進展させ、オープンソース コミュニティをサポートする
    • 良い市民になることを目指す
    • 私たちの価値と心を共有するより良いパートナー
    • メールで回答しサポートを提供する
    • 他とネットワークする仮想会社です
    • ソフトウェア特許に反対して作業します

    MySQL ウェブサイト(http://www.mysql.com/)は、MySQL と MySQL AB に ついての最新情報を提供しています。

    1.3.1 MySQL AB のビジネスモデル及びサポート

    私たちが最もよく受ける質問は:「どのようにして無料で配布して採算を 取っているのでしょうか？」というものです。それは、このようにしています。

    MySQL AB はサポート、サービス、商用ライセンス及びロイアリティで利 益をあげます。そして、私たちは製品開発とMySQLの事業を展開するため、 これらの収益を利用します。

    MySQL AB は創業以来、利益が増えています。2001年10月、私たちは有数のスカ ンジナビアの投資家および数少ないビジネスエンジェルからのベンチャー投資に 応じました。この投資は、私たちのビジネス・モデルを固め、持続的成長の基盤 を構築するために使用されます。

    1.3.1.1 サポート

    MySQL AB は、MySQL データ・ベースの設立者及び主な開発者に より管理・運営されます。開発者は顧客及びその他のユーザの要望・課題を連絡 をとり続けるためのサポートを提供することを約束します。私たちの全てのサポー トは有能な開発者によって提供されます。実際に複雑な質問は、MySQLサ ーバーの主要な著者である Michael Monty Widenius が答えます。 「1.4.1 Support Offered by MySQL AB」節参照.

    さらなる情報とサポートの依頼は、http://www.mysql.com/support/ か、 私たちの販売員 sales@mysql.com にご連絡ください。

    1.3.1.2 トレーニングと認定

    MySQL AB は MySQL と関連したトレーニングを世界的に提供しま す。私たちは、一般公募するコースと、あなたの会社のニーズに合せた特別な社内 研修の両方を提供します。MySQL トレーニング はさらに、私たちのパート ナーであるMySQL 認定 トレーニング・センター でも受講ができます。

    私たちのトレーニングの教材は、いくつかのデータベースの実例と資料・説明書、 そしてサンプルアプリケーションを使用します。また、教材は MySQL の 最新バージョンを反映するために常時更新されます。私たちの講師は、トレーニン グの質と教材の開発を保証するため、常に開発チームにサポートされます。これ は、さらにトレーニング中の質問には必ず回答できることを保証します。

    私たちのトレーニング講座に参加することにより、あなたの目標と MySQL アプリケーションを実現することができるでしょう。さらに以下のことができる でしょう:

    • 時間を節約します
    • アプリケーションの性能を改善します
    • 過剰なハードウェアの必要性を低減・解消させ、コストを削減します。
    • セキュリティを強化します。
    • 顧客をや同僚の満足度を増やします。
    • MySQL 認定試験 の準備になります。

    参加予定者あるいはトレーニング・パートナーとして私たちのトレーニングに興味 を持っている場合、http://www.mysql.com/training/のトレーニング課 にアクセスするか、あるいは training@mysql.com にメールで連絡を ください。

    MySQL 認定プログラム についての詳細な情報は ,http://www.mysql.com/certification/ を参照してください。

    1.3.1.3 コンサルティング

    MySQL AB と 認定パートナー は、全世界の MySQLサーバ のユーザとMySQLサーバを自身のソフトウェアに組み入れようとしている ユーザにコンサルティングサービスを提供します。

    わたしたちのコンサルタントは、データベースの設計と調整、効率のよい問合 せの作成、最適な性能のためのプラットホームの調整、移植の問題の解決、レ プリケーションの設定、頑強なトランザクションアプリケーションの作成とい つたことを助けます。

    わたしたちは、お客様がご自身のアプリケーションにMySQL Serverを組 み込むことを手助けし、大規模なアプリケーションを作ることを手助けします。

    私のコンサルタントは、あなたの開発チームと密接に協力して作業します。この ことは、わたしたちの専門サービスの品質を確実にします。コンサルティングの 割り当ては、2日間の強力開始期間から、何週間も何ヶ月にもわたるプロジェク トに広がります。わたしたちの専門意見は MySQLサーバ だけを含むので はなく、PHPやPerlやほかのスクリプティング言語とプログラミングにも広がっ ています。

    もし、わたしたちのコンサルティングサービスやコンサルティングパートナーに なることに興味をもったときは、私たちのコンサルティングセクションのWeb サ イト http://www.mysql.com/consulting/ を訪れるか、コンサルティン グスタッフ consulting@mysql.com に連絡してください。

    1.3.1.4 商用ライセンス

    MySQL データベースは、GNU General Public License (GPL) のもとでリリースされています。これは、MySQL ソフトウ ェアは GPL のもと、無償で使えることを意味します。 GPL の条 件項目(あなたのアプリケーションもまた GPL にしなければならない)に 束縛されたくないならば、MySQL AB から同じ製品の商用ライセンスを購 入しなければなりません； http://www.mysql.com/products/pricing.html。

    MySQL ソースコードの著作権は MySQL AB が所有するため、わた したちは デュアルライセンス を採用することができます。このことは、同 じ製品に GPL と商用ライセンスの両方があるということです。これはど うあろうと MySQL AB のオープンソースの遂行には影響しません。商用 ライセンスが必要なときは、 「1.4.3 MySQL Licenses」節 を参照してください。

    わたしたちは、MySQLサーバ に機能を追加するサードパーティーの オープンソースGPL ソフトウェアの商用ライセンスも販売しています。 よい例は、InnoDB トランザクション対応ストレージエンジンです。この エンジンは、ACIDが使え、低水準のロック、破壊からの回復、マルチバージョニ ング、外部キーが使えるといった特徴があります。 詳しくは 「7.5 InnoDB テーブル (3.23.6以上)」節参照 を 参照してください。

    1.3.1.5 パートナー

    MySQL AB は、トレーニングコース、コンサルティングとサポート、出版、 MySQL 関連製品の再販と販売に関する、全世界のパートナープログラム をもっています。 MySQL AB パートナーは、webサイト http://www.mysql.com/で公開され、製品を識別しビジネスを推進するた めの MySQL のトレードマークの特別バージョンを使う権利が得られます。

    もし、MySQL AB パートナーになることに興味をおもちならば、 partner@mysql.com に 電子メールを送ってください。

    MySQL の単語と MySQL のイルカのロゴは、MySQL ABのトレードマークです。 「1.4.4 MySQL AB Logos and Trademarks」節参照。

    このトレードマークは、 MySQL の創設者が何年にもわたって築いてきた 重要な価値の象徴です。

    1.3.1.6 広告

    MySQL のwebサイト (http://www.mysql.com/)は、開発者とユー ザの間では人気があります。2001年10月で、1千万ページビューがありました。 訪問者は、購入の決定者とソフトウェアとハードウェアの両方の推奨者のグルー プです。訪問者の12%は購入の決定を承認し、たった9%が購入決定に関わってい ませんでした。65%以上が、半年の間に何らかのオンラインビジネスの購入をし ていて、70%が数ヶ月の間に購入を計画していました。

    1.3.2 連絡先の情報

    MySQL のwebサイト(http://www.mysql.com/)にはMySQL と MySQL AB の最新の情報があります。

    報道サービスやわたしたちのニュースリリース (http://www.mysql.com/news/)に書かれていない質問は、 press@mysql.com に電子メールを送ってください。

    MySQL AB との間に有効なサポート契約があるならば、あなたは、 MySQL ソフトウェアの技術的な質問に対する正確な答えがタイムリーに 得られます。より詳しい情報は、 「1.4.1 Support Offered by MySQL AB」節.私たちのwebサイト、 http://www.mysql.com/support/ を見るか、sales@mysql.com にメールを送ってください。

    MySQL トレーニングについての情報は、 http://www.mysql.com/training/ のトレーニング節を訪れてください。 インターネットにアクセスできないときは、training@mysql.com の MySQL AB トレーニングスタッフに連絡してください。 「1.3.1.2 トレーニングと認定」節参照。

    MySQL 認定プログラム に関する情報は、 http://www.mysql.com/certification/を見てください。 「1.3.1.2 トレーニングと認定」節参照。

    コンサルティングに興味があるならば、 http://www.mysql.com/consulting/ のコンサルティング部門を見てくだ さい。インターネットにアクセスできないときは、 consulting@mysql.com の MySQL AB コンサルティングスタッ フに連絡してください。 「1.3.1.3 コンサルティング」節参照.

    商用ライセンスは、https://order.mysql.com/ でオンラインで購入でき ます。MySQL AB にどうやって購入のFAXを送るかの情報もあります。よ り詳しい情報はhttp://www.mysql.com/products/pricing.html にありま す。もし、ライセンスに関する質問があったり、大量のライセンスの見積もりが 必要なときは、webサイト(http://www.mysql.com/)の連絡用紙に記入す るか、licensing@mysql.com (ライセンスの質問用)に電子メールを送 るか、sales@mysql.com (セールスの見積もり用) に電子メールを送っ てください。 「1.4.3 MySQL Licenses」節参照.

    ビジネスで MySQL AB のパートナーに興味があるときは、 partner@mysql.com に電子メールを送ってください。 「1.3.1.5 パートナー」節参照.

    MySQL のトレードマークの考え方は、 hhttp://www.mysql.com/company/trademark.htmlを見るか、 trademark@mysql.com に電子メールを送ってください。 「1.4.4 MySQL AB Logos and Trademarks」節参照.

    もし、MySQL AB のジョブ選択 (http://www.mysql.com/company/jobs/)にある仕事に興味があるならば、 jobs@mysql.com に電子メールを送ってください。あなたのCV(履歴書) は添付しないで、プレーンテキストであなたの電子ールの最後につけてください。

    多くのユーザの間の一般的な議論は、適切なメーリングリストに注意してくだい。 「1.6.1 MySQL メーリングリスト」節参照.

    エラー(多くの場合はバグと呼ばれます)の報告、同じように質問やコメントは、 mysql@lists.mysql.com のメーリングリストに送ってください。 MySQLサーバ に要注意のセキュリティホールが見つかったときは、 security@mysql.com に電子メールを出してください。 「1.6.1.3 バグや問題を報告する方法」節参照.

    公開してよいベンチマークの結果があるときは、benchmarks@mysql.com に連絡してください。

    このマニュアルに対する追加や修正は、docs@mysql.com のマニュアル チームに連絡してください。

    MySQL のwebサイト(http://www.mysql.com/)に対する作業や内容 のコメントや質問は、webmaster@mysql.com に電子メールを出してく ださい。

    MySQL AB にはプライバシーポリシーがあります。それは、 http://www.mysql.com/company/privacy.html で読めます。このポリシ ーに関して質問があれば privacy@mysql.com に電子メールを送ってく ださい。

    その他の質問は、info@mysql.com に電子メールを送ってください。

    1.4 MySQL ライセンスとサポート

    (訳注： ライセンスの章については、正確さをきすため原文を併記しています。 訳文だけでなく原文に目を通してください。もし意味の取違いを見つけたなら、 takeshi@SoftAgency.co.jp に連絡してください。)

    このセクションでは、MySQLのサポートとライセンス規定について説明します。

    1.4.1 Support Offered by MySQL AB

    Technical support from MySQL AB means individualised answers to your unique problems direct from the software engineers who code the MySQL database engine.

    We try to take a broad and inclusive view of technical support. Almost any problem involving MySQL software is important to us if it's important to you. Typically customers seek help on how to get different commands and utilities to work, remove performance bottlenecks, restore crashed systems, understand operating system or networking impacts on MySQL, set up best practices for backup and recovery, utilise APIs, etc. Our support covers only the MySQL server and our own utilities, not third-party products that access the MySQL server, though we try to help with these where we can.

    Detailed information about our various support options is given at http://www.mysql.com/support/, where support contracts can also be ordered online. If you have restricted access to the Internet, contact our sales staff at sales@mysql.com.

    Technical support is like life insurance. You can live happily without it for years, but when your hour arrives it becomes critically important, yet it's too late to buy it! If you use MySQL Server for important applications and encounter sudden troubles, it might take too long to figure out all the answers yourself. You may need immediate access to the most experienced MySQL troubleshooters available, those employed by MySQL AB.

    1.4.2 Copyrights and Licenses Used by MySQL

    MySQL AB owns the copyright to the MySQL source code, the MySQL logos and trademarks and this manual. 「1.3 MySQL AB とは何か」節参照. Several different licenses are relevant to the MySQL distribution:

    1. All the MySQL-specific source in the server, the mysqlclient library and the client, as well as the GNU readline library is covered by the GNU General Public License. 「H GNU General Public License」節参照. The text of this license can also be found as the file `COPYING' in the distributions.
    2. The GNU getopt library is covered by the GNU Lesser General Public License. 「I GNU Lesser General Public License」節参照.
    3. Some parts of the source (the regexp library) are covered by a Berkeley-style copyright.
    4. Older versions of MySQL (3.22 and earlier) are subject to a more strict license (http://www.mysql.com/products/mypl.html). See the documentation of the specific version for information.
    5. The manual is currently not distributed under a GPL-style license. Use of the manual is subject to the following terms:
      • Conversion to other formats is allowed, but the actual content may not be altered or edited in any way.
      • You may create a printed copy for your own personal use.
      • For all other uses, such as selling printed copies or using (parts of) the manual in another publication, prior written agreement from MySQL AB is required.
      Please e-mail docs@mysql.com for more information or if you are interested in doing a translation.

    For information about how the MySQL licenses work in practice, please refer to 「1.4.3 MySQL Licenses」節. Also see 「1.4.4 MySQL AB Logos and Trademarks」節.

    1.4.3 MySQL Licenses

    The MySQL software is released under the GNU General Public License (GPL), which probably is the best known Open Source license. The formal terms of the GPL license can be found at http://www.gnu.org/licenses/. See also http://www.gnu.org/licenses/gpl-faq.html and http://www.gnu.org/philosophy/enforcing-gpl.html.

    Since the MySQL software is released under the GPL, it may often be used for free, but for certain uses you may want or need to buy commercial licenses from MySQL AB at https://order.mysql.com/. See http://www.mysql.com/products/licensing.html for more information.

    Older versions of MySQL (3.22 and earlier) are subject to a more strict license (http://www.mysql.com/products/mypl.html). See the documentation of the specific version for information. 古いバージョンの MySQL (3.22 とそれ以前) は より制限されたライセンスを有していることに気をつけて下さい (http://www.mysql.com/support/arrangements/mypl.html)。 より詳しくは、それぞれのバージョンに添付のドキュメントを御覧下さい。

    Please note that the use of the MySQL software under commercial license, GPL, or the old MySQL license does not automatically give you the right to use MySQL AB trademarks. 「1.4.4 MySQL AB Logos and Trademarks」節参照.

    1.4.3.1 Using the MySQL Software Under a Commercial License

    The GPL license is contagious in the sense that when a program is linked to a GPL program all the source code for all the parts of the resulting product must also be released under the GPL. Otherwise you break the license terms and forfeit your right to use the GPL program altogether and also risk damages.

    You need a commercial license:

    • When you link a program with any GPL code from the MySQL software and don't want the resulting product to be GPL, maybe because you want to build a commercial product or keep the added non-GPL code closed source for other reasons. When purchasing commercial licenses, you are not using the MySQL software under GPL even though it's the same code.
    • When you distribute a non-GPL application that only works with the MySQL software and ship it with the MySQL software. This type of solution is actually considered to be linking even if it's done over a network.
    • When you distribute copies of the MySQL software without providing the source code as required under the GPL license.
    • When you want to support the further development of the MySQL database even if you don't formally need a commercial license. Purchasing support directly from MySQL AB is another good way of contributing to the development of the MySQL software, with immediate advantages for you. 「1.4.1 Support Offered by MySQL AB」節参照.

    If you require a license, you will need one for each installation of the MySQL software. This covers any number of CPUs on a machine, and there is no artificial limit on the number of clients that connect to the server in any way.

    For commercial licenses, please visit our website at http://www.mysql.com/products/licensing.html. For support contracts, see http://www.mysql.com/support/. If you have special needs or you have restricted access to the Internet, please contact our sales staff at sales@mysql.com.

    1.4.3.2 Using the MySQL Software for Free Under GPL

    You can use the MySQL software for free under the GPL if you adhere to the conditions of the GPL. For more complete coverage of the common questions about the GPL see the generic FAQ from the Free Software Foundation at http://www.gnu.org/licenses/gpl-faq.html. Some common cases:

    • When you distribute both your own application as well as the MySQL source code under the GPL with your product.
    • When you distribute the MySQL source code bundled with other programs that are not linked to or dependent on the MySQL system for their functionality even if you sell the distribution commercially. This is called mere aggregation in the GPL license.
    • If you are not distributing any part of the MySQL system, you can use it for free.
    • When you are an Internet Service Provider (ISP), offering web hosting with MySQL servers for your customers. However, we do encourage people to use ISPs that have MySQL support, as this will give them the confidence that if they have some problem with the MySQL installation, their ISP will in fact have the resources to solve the problem for them. Note that even if an ISP does not have a commercial license for MySQL Server, they should at least give their customers read access to the source of the MySQL installation so that the customers can verify that it is patched correctly.
    • When you use the MySQL Database Software in conjunction with a web server, you do not need a commercial license (so long as it is not a product you distribute). This is true even if you run a commercial web server that uses MySQL Server, because you are not distributing any part of the MySQL system. However, in this case we would like you to purchase MySQL support because the MySQL software is helping your enterprise.

    If your use of MySQL database software does not require a commercial license, we encourage you to purchase support from MySQL AB anyway. This way you contribute toward MySQL development and also gain immediate advantages for yourself. 「1.4.1 Support Offered by MySQL AB」節参照.

    If you use the MySQL database software in a commercial context such that you profit by its use, we ask that you further the development of the MySQL software by purchasing some level of support. We feel that if the MySQL database helps your business, it is reasonable to ask that you help MySQL AB. (Otherwise, if you ask us support questions, you are not only using for free something into which we've put a lot a work, you're asking us to provide free support, too.)

    1.4.4 MySQL AB Logos and Trademarks

    Many users of the MySQL database want to display the MySQL AB dolphin logo on their web sites, books, or boxed products. We welcome and encourage this, although it should be noted that the word MySQL and the MySQL dolphin logo are trademarks of MySQL AB and may only be used as stated in our trademark policy at http://www.mysql.com/company/trademark.html.

    1.4.4.1 The Original MySQL Logo

    The MySQL dolphin logo was designed by the Finnish advertising agency Priority in 2001. The dolphin was chosen as a suitable symbol for the MySQL database since it is a smart, fast, and lean animal, effortlessly navigating oceans of data. We also happen to like dolphins.

    The original MySQL logo may only be used by representatives of MySQL AB and by those having a written agreement allowing them to do so.

    1.4.4.2 MySQL Logos that may be Used Without Written Permission

    We have designed a set of special Conditional Use logos that may be downloaded from our web site at http://www.mysql.com/press/logos.html and used on third-party web sites without written permission from MySQL AB. The use of these logos is not entirely unrestricted but, as the name implies, subject to our trademark policy that is also available on our web site. You should read through the trademark policy if you plan to use them. The requirements are basically:

    • Use the logo you need as displayed on the http://www.mysql.com/ site. You may scale it to fit your needs, but not change colours or design, or alter the graphics in any way.
    • Make it evident that you, and not MySQL AB, are the creator and owner of the site that displays the MySQL trademark.
    • Don't use the trademark in a way that is detrimental to MySQL AB or to the value of MySQL AB trademarks. We reserve the right to revoke the right to use the MySQL AB trademark.
    • If you use the trademark on a web site, make it clickable, leading directly to http://www.mysql.com/.
    • If you are using the MySQL database under GPL in an application, your application must be Open Source and be able to connect to a MySQL server.

    Contact us at trademark@mysql.com to inquire about special arrangements to fit your needs.

    1.4.4.3 When do you need a Written Permission to use MySQL Logos?

    In the following cases you need a written permission from MySQL AB before using MySQL logos:

    • When displaying any MySQL AB logo anywhere except on your web site.
    • When displaying any MySQL AB logo except the Conditional Use logos mentioned previously on web sites or elsewhere.

    Out of legal and commercial reasons we have to monitor the use of MySQL trademarks on products, books, etc. We will usually require a fee for displaying MySQL AB logos on commercial products, since we think it is reasonable that some of the revenue is returned to fund further development of the MySQL database.

    1.4.4.4 MySQL AB Partnership Logos

    MySQL partnership logos may only be used by companies and persons having a written partnership agreement with MySQL AB. Partnerships include certification as a MySQL trainer or consultant. Please see 「1.3.1.5 パートナー」節.

    1.4.4.5 Using the word MySQL in Printed Text or Presentations

    MySQL AB welcomes references to the MySQL database, but note that the word MySQL is a trademark of MySQL AB. Because of this, you should append the trademark symbol (TM) to the first or most prominent use of the word MySQL in a text and where appropriate, state that MySQL is a trademark of MySQL AB. Please refer to our trademark policy at http://www.mysql.com/company/trademark.html for details.

    1.4.4.6 Using the word MySQL in Company and Product Names

    Use of the word MySQL in product or company names or in Internet domain names is not allowed without written permission from MySQL AB.

    1.5 MySQL 4.x はやわかり

    MySQL ABが長い間約束してきて、ユーザからは長い間待ち続けられてき た、MySQLサーバ4.0が、http://www.mysql.com/からダウンロードできる ベータとして使えるようになりました。

    MySQLサーバ4.0の主要な新しい機能は、わたしたちのこれまでのビジネスとユー ザに前進のギアを入れ、ミッションクリティカルで、高負荷に耐えるデータベー スシステムとしてMySQLデータベースを拡張しています。

    1.5.1 段階を踏んだ公開

    MySQLは 4.0.6 からガンマ(gamma)とラベルづけられ、4.0.x は2ヶ月以上(最初の1月は アルファで、そしてベータ)、修正が困難な重要な問題も見つからないで使われていて、 実運用に使えます。

    少なくとも1ヶ月間重要なバグがなければ、MySQL 4.0 からガンマの接頭辞を取り 除きます。

    MySQLソフトウェアの新しい機能は、bk ソースツリーから利用できるMySQL 4.1 で追加され、2003年の最初の四半期にアルファリリースしようとされています。

    1.5.2 すぐに使う準備

    すべてのバイナリリリースは、検査したすべてのプラットフォームで、エラーな しで、私たちの広範囲のテストスイートに合格しています。MySQL 4.0は多くのユ ーザで検査され、いくつかの大きなサイトで運用に入っています。

    1.5.3 組み込み MySQL

    libmysqldでMySQL Serverは広範なアプリケーションにふさわしくなります。 組み込み MySQL サーバライブラリを使用することで、MySQL を色々なアプリケ ーション、電子機器(それらにデータベースが利用されていることなどはエンド ユーザが気にすることはない)に埋め込めます。組み込み MySQL は、 インターネットのアプリケーションや、キオスク、ハードウェア、ソフトウェア を組み合わせたもの、高パフォーマンスのインターネットサーバ、CD-ROMに全てが 収まっているデータベース、などの裏方での利用に最適です。

    多くのlibmysqldユーザは、MySQLのデュアルライセンスの恩恵をうけ ます。GPLに束縛されたくないユーザは、商用ライセンスでソフトウェアを使え るようになります。組み込みMySQLライブラリは通常のクライアントライブラリ と同じインタフェースを使っているので、便利で使いやすくなっています。 「8.4.9 libmysqld, the Embedded MySQL Server Library」節参照.

    1.5.4 MySQL 4.0 から使えるその他の機能

      バージョン 4.0 は、数カ所でMySQL Serverの速度を改善しま した。それは、一括INSERTや、圧縮されたインデクスの検索、 FULLTEXTインデクスの作成と、COUNT(DISTINCT)です。
    • InnoDBストレージエンジンが、MySQLサーバの標準の機能として、今回、 提示されました。これは、完全なトランザクションのサポートと レコードレベルのロックが含んでいます。
    • ドイツと、オーストリア、そしてスイスのユーザは、新しくlatin1_deが 使え、ドイツ語のソート順では、ドイツ語のウムラルトをドイツの電話 帳と同じ順にします。
    • ほかのデータベースシステムからMySQLサーバへ簡単に移行するための機能に (Oracleにある)TRUNCATE TABLEと、(Sybaseにある)自動的にキーを増や すIDENTITYがシノニムとして入りました。多くのユーザは、MySQLサーバ では長い間待たされてきた、標準SQLの機能であるUNION文が使えるよう になったことがわかり、うれしく思うでしょう。
    • 新しいユーザに対する機能を作成するときに、わたしたちの重要なユーザのコミ ュニティからの要望も忘れてはいません。複数のテーブルのDELETE文と UPDATE文が加わりました。テーブルの水準に(前のようにデータベースの 水準でなく)MyISAMにシンボリックリンクが使えるようになり、 Windowsではデフォルトでシンボリックリンクが使えるようになりました。これ で、わたしたちが拡張の要求を真剣に扱っていることがわかると願います。 SQL_CALC_FOUND_ROWSとFOUND_ROWS()機能が新しく追加されまし た。これは、句なしで返すために、LIMIT句を含むSELECT問合せで、行の数 を返します。

    1.5.5 将来の MySQL 4.x の機能

    つぎのMySQL Server 4.x リリースでは開発中の次の項目を予定しています。

    • MySQLサーバのミッションクリティカルで、高負荷のユーザは、レプリケーシ ョンシステムとオンラインバックアップシステムが追加されることに価値を見い だすでしょう。4.xの後のバージョンでは、フェールセーフなレプリケー ションが入るでしょう；4.0ですでにある、LOAD DATA FROM MASTERコマ ンドは、すぐにスレーブの設定を自動化するようになります。オンライン バックアップは、マスターを停止しないで新しいレプリケーションスレーブを 追加することを簡単にし、更新が多いシステムでは性能劣化がとても少なくなっ ています。
    • データベース管理者にとって便利な機能は、もうすぐmysqlのパラメータ (起動オプション)がサーバを停止しなくても設定できるようになることです。
    • MySQLサーバ4.0の拡張されたFULLTEXT検索の属性で、バイナリと自然言 語の検索ロジックで、大きなテキストの固まりにFULLTEXT索引が作れる ようになりました。最小ワード長を変更でき、また、どのような自然言語に対し てもストップワードを定義でき、これにより新しい種類のアプリケーションを MySQLサーバに作成できます。
    • MySQL 4.0 は、キーキャッシュを書き直すことで、問合せを繰り返すア プリケーションをさらに高速にできるようになりました。
    • 多くの開発者は、クライアントのMySQL コマンドヘルプをみて、うれしく思う でしょう。

    1.5.6 MySQL 4.1, 次の開発リリース

    MySQL Server 4.0 は、MySQL Server 4.1 の新しい機能の基礎となります。その 機能は、入れ子になった副問合せ(4.1)、ストアードプロシージャ (5.0)、MyISAM表の外部キーの一貫性のルール(5.0)で、多くのお客様か らのご要望の一覧のうちで上位となるものです

    これらの追加の後に、MySQLデータベースサーバの評論家は、MySQLデータベース 管理システムの欠点を指摘するよりも、より構想力が必要となるでしょう。すでに、長い 間知られている安定性、速度、使いやすさで、MySQLサーバは、切望して いる購入者の要求項目の一覧に適合するでしょう。

    1.6 MySQL についての情報源

    1.6.1 MySQL メーリングリスト

    この節では、MySQLメーリングリストを紹介し、どのように使うかのガイドライ ンを記述します。メーリングリストを購読すると、電子メールのメッセージで、 リストへ送られたすべてを受け取ります。あなたはリストに質問や回答を送るこ とができます。

    1.6.1.1 MySQL メーリングリスト

    メイン MySQL メーリングリストを購読するには、メッセージを電子メールアド レス mysql-subscribe@lists.mysql.com に送ってください。

    メイン MySQL メーリングリストの購読の中止は、メッセージを電子メールアド レス mysql-unsubscribe@lists.mysql.com に送ってください。

    メールの購読と購読の中止には、メッセージを送る先のアドレスだけが重要です。 メッセージのサブジェクトと本文は無視されます。

    もし、あなたのリプライアドレスがつかえないときは、アドレスを明示的に指定 できます。subscribe あるいは unsubscribe のあとにハイフンを付け、そのあ とにあなたのアドレスを記述します。ただし `@' 文字は `=' に置 き換えて書きます。例えば、 your_name@host.domain で購読したい場 合は、mysql-subscribe-your_name=host.domain@lists.mysql.com 宛に メッセージを送ります。

    mysql-subscribe@lists.mysql.com や mysql-unsubscribe@lists.mysql.com へのメールは ezmlm メーリングリストプロセッサによって自動的に処理されます。 ezmlm についての情報は ezml ウェブサイトを参考してください (http://www.ezmlm.org/)

    本メーリングリストへ投稿するには、mysql@lists.mysql.com にメッセージを送ります。 しかし、subscribe あるいは unsubscribe のメールを mysql@lists.mysql.com に送らないでください。 これらのアドレスへ送られたメールは、何千ものユーザに配送されてしまいます。

    あなたのローカルサイトが多くの mysql@lists.mysql.com の購読者を持て ます。この場合、ローカルのメーリングリストを作り、lists.mysql.com からの 一つのメッセージがそのサイトに送られ、ローカルなリストで複写されるように してください。この場合、ローカルの MySQL リストへの追加と削除は、 あなたのシステム管理者に問い合わせて下さい。

    あなたのメーラーでMySQL メーリングリストからのメールを 適切なメールボックスへ振り分けるには、 （振り分け用の）フィルタをメッセージヘッダを頼りに動作するよう設定して下さい。 その場合、List-ID: ヘッダか Delivered-To: ヘッダが 識別の役に立つことでしょう。

    次の MySQL メーリングリストがあります:

    announce-subscribe@lists.mysql.com announce
    これは MySQL と関連プログラムの新しいバージョンのアナウンスのためのリストです。 このリストの流量は少なく、私たちは全ての MySQL ユーザがこのMLに入るべきだと考えています。
    mysql-subscribe@lists.mysql.com mysql
    MySQL についての一般的な議論のための根幹のリストです。さらに専門的なリ ストで議論すべきものもあることに注意してください。間違ったリストに投稿 しても、答を得られないでしょう。
    mysql-digest-subscribe@lists.mysql.com mysql-digest
    ダイジェスト形式の mysql リストです。 このリストからは、一日分の全てのメッセージががまとめられた（ダイジェスト）形式で送られてきます。
    bugs-subscribe@lists.mysql.com bugs
    このリストには、完全で再現可能なバグレポートだけを、mysqlbug を使 用して投稿すべきです(Windows 上で実行している場合は、OS と MySQL バージョンの記述を含めるべきです)。 できれば投稿前にMySQL の最新の安定バージョンか開発バージョンを使用して 問題をテストしてください。 含められたテストケース上で、mysql test < script を使 用することで、誰もがバグを再現できるようにすべきです。このリストに投稿された全て のバグは、次の MySQL リリースで修正されるかドキュメント化されま す。小さなコードの変更だけですめば、私たちはこの問題を修正するパッチを投 稿します。
    bugs-digest-subscribe@lists.mysql.com bugs-digest
    ダイジェスト形式の bugs リストです。
    internals-subscribe@lists.mysql.com internals
    MySQL コード上で作業する人のためのリストです。 このリストでもMySQL 開発の議論とパッチの投稿が可能です。
    internals-digest-subscribe@lists.mysql.com internals-digest
    internals リストのダイジェスト版です。
    java-subscribe@lists.mysql.com java
    MySQL server と Java についての議論。 多くは JDBC ドライバ (MySQL Connector/J 含む) についてです。
    java-digest-subscribe@lists.mysql.com java-digest
    java リストのダイジェスト版です。
    win32-subscribe@lists.mysql.com win32
    Win95, Win98, NT, Win2000 のような Microsoft OS 上の MySQL software に関連するリストです。
    win32-digest-subscribe@lists.mysql.com win32-digest
    win32 リストのダイジェスト版です。
    myodbc-subscribe@lists.mysql.com myodbc
    ODBC で MySQL server への接続に関連する全て。
    myodbc-digest-subscribe@lists.mysql.com myodbc-digest
    myodbc リストのダイジェスト版です。
    mysqlcc-subscribe@lists.mysql.com mysqlcc
    MySQL MySQL Control Center graphical client 全般についてのリストです。
    mysqlcc-digest-subscribe@lists.mysql.com mysqlcc-digest
    mysqlcc リストのダイジェスト版です。
    plusplus-subscribe@lists.mysql.com plusplus
    MySQL の C++ API でのプログラミングについての全て。
    plusplus-digest-subscribe@lists.mysql.com plusplus-digest
    plusplus リストのダイジェスト版です。
    msql-mysql-modules-subscribe@lists.mysql.com msql-mysql-modules
    MySQL でサポートする Perl についてのリスト。msql-mysql-modules.
    msql-mysql-modules-digest-subscribe@lists.mysql.com msql-mysql-modules-digest
    msql-mysql-modules リストのダイジェスト版です。

    上述したのと同じ方法で全てのリストの購読または購読中止ができます。あなた の購読または購読中止のメッセージは、mysql ではなく適切なメーリングリス トに送ってください。例えば、myodbc リストを購読または購読中止するには、 myodbc-subscribe@lists.mysql.com または myodbc-unsubscribe@lists.mysql.com にメールを送ります。

    メーリングリストから有益な回答が得られない場合、MySQL ABに 有料のサポートを求めることもできます。有料サポートが必要な場合、 MySQL 開発チームに直接御連絡下さい( 「1.4.1 Support Offered by MySQL AB」節参照)。

    次の表は英語以外の MySQL メーリングリストを示します。注意: これら は MySQL AB によって運用されていません。そのため、私たちはそれらの 品質を保証できません。

    mysql-france-subscribe@yahoogroups.com フランス語メーリングリスト
    list@tinc.net 韓国語メーリングリスト
    このリストに subscribe mysql your@e-mail.address をメールしてください。
    mysql-de-request@lists.4t2.com ドイツ語メーリングリスト
    このリストに subscribe mysql-de your@e-mail.address をメールしてください。 これについては http://www.4t2.com/mysql で情報を見つけられます。
    mysql-br-request@listas.linkway.com.br ポルトガル語メーリングリスト
    このリストに subscribe mysql-br your@e-mail.address をメールしてください。
    mysql-alta@elistas.net スペイン語メーリングリスト
    このリストに subscribe mysql your@e-mail.address をメールしてください。

    1.6.1.2 質問またはバグ報告

    メーリングリストへ質問を尋ねる前に、以下の手順を踏んでください：

    • MySQL のオンラインマニュアルを調べることからはじめます：
      http://www.mysql.com/doc/
      私たちは、新しく見つかった問題の解決によってマニュアルを頻繁に更新する ことで、マニュアルを最新に保持しようとしています。 更新の付録(http://www.mysql.com/doc/en/News.html)は、新 しいバージョンがすであなたの問題の解決を含んでいる可能性が高い ので、とても有用です。
    • バグデータベース(http://bugs.mysql.com)で、バグがすでに 報告されているか、解決されているかを調べます。
    • MySQL メーリングリストアーカイブを検索します：
      http://lists.mysql.com/
    • http://www.mysql.com/ の全ての Web ページ(マニュアルも含む)を検索するために http://www.mysql.com/search/ も使用できます。

    ここで回答が見つけられない場合は、近くの MySQL 熟練者ととも に調べて下さい。まだあなたの質問の回答が見つけられなければ、先に進み、次 のセクションの mysql@lists.mysql.com へメールを送る方法についてを読んで ください。

    1.6.1.3 バグや問題を報告する方法

    良いバグレポートを書くのには忍耐が要りますが、それを最初に正しく行うと 私たちとあなたの時間を節約します。 バグについての完全なテストケースを含む良いレポートを書くと、次のリリー スでそのバグが修正される可能性がとても高くなります。 この節では、かなりの、または全く私たち の助けにならないことにあなたの時間を浪費しないように、あなたがレポートを 正しく書くことを手助けします。

    私たちは、バグレポートまた可能ならば全ての問題についてのレポートの作成に mysqlbug スクリプトを使用することを奨励します。mysqlbug は ソース配布内の `scripts' ディレクトリ、または、バイナリ配布では MySQL をインストールしたディレクトリ配下の `bin' ディレク トリにあります。mysqlbug を使用できない場合は、この節に挙 げられている全ての必要な情報を含めてください。

    mysqlbug スクリプトは、下記の多くの情報を自動的に見つけ出すことで、 レポートの作成を手助けします。しかし、重要な何かが足りない場合、あなたの メッセージにそれを含めてください。この節を慎重に読んで、ここで述べられ ている全ての情報がレポート中に含まれていることを確認してください。

    バグや問題を報告する通常の場所は、mysql@lists.mysql.com です。 バグを明確に示すテストケースを作ることができれば、 bugs@list.mysql.com リストにそれを投稿してください。注意: この リストには、完全で再現可能なバグ情報を mysqlbug スクリプトを使用 して投稿すべきです。 Windows 上で実行している場合は、OS と MySQL バージョンの記述を含めてください。できれば、投稿前に MySQL Server の最新の安定バージョンか開発バージョンを使用して問題をテ ストしてください。含められたテストケース上で、``mysql test < script'' を使 用することで、または、バグレポートに含められたシェル/Perlスクリプトを実 行することで、誰もがバグを再現できるようにすべきです。この bugs リストに投稿された全て のバグは、次の MySQL リリースで修正されるかドキュメント化されま す。 小さなコードの変更だけですめば、私たちはこの問題を修正するパッチの投 稿も行います。

    多すぎる情報を含むメッセージに答えることはできますが、少なすぎる情報を含 むものにはできないということを覚えていてください。しばしば人は事実を省い てしまいます。問題の原因をわかっていると思い、いくつかの細かいことを重大でない と見なしてしまうからです。良い原則は: 何かを言おうか迷ったときには、言っ てください。最初にあなたが十分な情報を含めなかったために、再び質問して 回答を待つことを強いられるより、数行をあなたのレポートに書く方が千倍速く て、迷惑ではありません。

    良くある間違いは、使用している MySQL 配布のバージョン番号を示さ ない、または MySQL server をインストールしたプラットフォームを(プラッ トフォームのバージョン番号を含めて)示さないことです。これはとても関連した 情報で、100 のバグレポートのうち 99 の場合、この情報がないと役に立ちませ ん。私たちは ``何故私では動作しないの？'' のような質問をとても良く受けま す。そして私たちは、要求された機能はその MySQL バージョンに実装さ れていない、または、レポート中に述べられているバグは新しい MySQL バージョンで既に修正されているであることを見つけます。ときどき、 エラーはプラットフォーム依存で、オペレーティングシステムとプラットフォー ムのバージョン番号を知らないことには、何も修正することはできません。

    問題に関連している場合は、コンパイラについての情報も与えることを忘れない でください。しばしば人はコンパイラのバグを見つけて、問題は MySQL に関連していると考えます。多くのコンパイラはいつも開発中 で、バージョンを上げることによってより良いバージョンになります。問題がコ ンパイラに依存しているかどうかを確定するには、どのコンパイラが使用されて いるかを知ることが必要です。全てのコンパイルの問題はバグレポートとみなさ れ、それに従って報告されるべきであることに注意してください。

    最も役に立つのは、問題の良い説明がバグレポートに含められることです。つま り、問題に導かれる全ての行ったことの例と、正確に記述された問題それ自身 です。良いバグレポートは、バグや問題を再現する方法を示す完全な例を含むも のです。 「E.1.6 Making a Test Case When You Experience Table Corruption」節参照.

    問題がエラーメッセージを与える場合、それをレポートに含めることはとても重 要です。私たちがプログラムを使用するアーカイブから何かを検索しようとする 場合、エラーメッセージはプログラムが与えたものと正確に一致する方が良いで す(大文字小文字でさえも残されるべきです)。どのようなエラーメッセージだったか を覚えるなんてことはしてはいけません；レポートに完全なメッセージをコピー して貼りつけてください。

    MyODBC での問題がある場合、MyODBC トレースファイルの生成を試みるべきです。 「8.3.7 Reporting Problems with MyODBC」節参照.

    あなたのレポートを読む多くの人が 80桁ディスプレイを使用しているというこ とを覚えておいて下さい。mysql コマンドラインツールを使用 してレポートまたはサンプルを生成するとき、そのようなディスプレイの有効幅を 超える出力(例えば、EXPLAIN SELECT 文; 後述のサンプル を見てください)には、--vertical オプション(または \G ステー トメント終端)を使用してください。

    次の情報をレポートに含めてください:

    • 使用している MySQL 配布のバージョン番号 (例えば MySQL バージョン 3.22.22)。どのバージョンを動かしているかは mysqladmin version の 実行でわかります。mysqladmin は MySQL のインストール ディレクトリ配下の `bin' ディレクトリにあります。
    • あなたが作業しているマシンのメーカーとモデル。
    • オペレーティングシステム名とバージョン。多くのオペレーティングシステムで は、UNIX コマンド uname -a の実行によってこの情報が得られます。
    • ときにはメモリ(実メモリと仮想メモリ)の量も関係します。疑わしければ、それを 含めてください。
    • MySQL software のソース配布を使用している場合は、使用したコンパイラの名 前とバージョン番号についての情報も必要です。バイナリ配布の場合は、配布名が 必要です。
    • 問題がコンパイル中に発生する場合、正確なエラーメッセージと、エラーが発生 したファイルの問題のコードの回りの数行も含めて下さい。
    • もし mysqld が死んだ場合は、mysqld がクラッシュしたクエリも レポートしてください。通常、これはロギングが有効にして mysqld を実行すること よって、見つけられます。 「E.1.5 Using Log Files to Find Cause of Errors in mysqld」節参照。
    • 何かのデータベーステーブルが問題に関連する場合は、 mysqldump --no-data db_name tbl_name1 tbl_name2 ... からの出力を含めて ください。これはデータベース内の任意のテーブルについての情報を得るとても 簡単で強力な方法で、私たちがあなたの状況に一致するものを生成する手助けにな ります。
    • SELECT 文での速度に関するバグや問題では、 EXPLAIN SELECT ... の出力と、少なくとも SELECT 文が 返す行の数を常に含めるべきです。誰かがあなたを助けられるように、 あなたの状況について、より多くの 情報を、より適切に与えてください。例え ば、次はとても良いバグレポートの例です（もちろん mysqlbug スクリプトで投 稿されてます）: mysql コマンド行ツール配下での実行例(注意: 出力幅がディスプレイ装 置の80桁を超える文には、\G 文終端子を使用し てください): 
      mysql> SHOW VARIABLES;
mysql> SHOW COLUMNS FROM ...\G
       <SHOW COLUMNS からの出力>
mysql> EXPLAIN SELECT ...\G
       <EXPLAIN からの出力>
mysql> FLUSH STATUS;
mysql> SELECT ...;
       <問い合わせを実行した時間を含んだSELECTの出力の短い版>
mysql> SHOW STATUS;
       <SHOW STATUS からの出力>
    • 問題やバグが MySQL 実行中に発生する場合、バグを再現する入力スク リプトが必要です。このスクリプトは必要なソースファイル全てを含めてください。 より精密なスクリプトはあなたのに似た状況を良く再現できます。 テストケースを再現可能にできる場合は、高い優先度で取り扱われるように、 bugs@lists.mysql.com にそれを送ってください。 もしスクリプトを提供することができなければ、少なくとも、 mysqladmin variables extended-status processlist の 出力結果をメールに含めてください。これはあなたのシステムの情報を 提供します。
    • 数行のテストケースを提供できない場合、またはテストテーブルがメーリングリ ストにメールするには大きすぎる(10行以上)場合、mysqldump を使用し てあなたのテーブルをダンプし、あなたの問題を説明した `README' ファ イルを作ってください。 tar と gzip または zip を使用して、ファイルの圧縮アー カイブを生成し、そのアーカイブを ftp を使用して ftp://support.mysql.com/pub/mysql/secret/ に転送してください。それか ら問題の短い説明を mysql@lists.mysql.com に送ってください。
    • MySQL server がクエリから異常な結果を与えると思う場合は、結果だけでな く、結果がどうなるべきかというあなたの意見と、あなたの意見の根拠を説明す る理由も含めてください。
    • 問題のサンプルを提供するときに、新しい名前にするよりも、実際の状況で存在す るのと同じ変数名やテーブル名等を使用した方が良いです。問題が変数やテーブ ルの名前に関連することがあります。おそらくこれはまれなケースですが、 後悔するよりも安全です。結局、実際に持っているあなたのサンプル 中の同じ状況を使用することは、あなたにとっても簡単で、私たちにとっても全ての 意味で良いことです。他の人に見せたくないデータである場合、 ftp を使用して ftp://support.mysql.com/pub/mysql/secret/ にデー タを転送することができます。データが本当に最高機密で私たちにさえ見せたくな い場合は、先に進んで、他の変数名等を使用してサンプルを作ってみてください。 しかしこれは最後の選択と思ってください。
    • 可能ならば、関連プログラムに与えられた全てのオプションを含めてください。 例えば、mysqld デーモン開始時に使用したオプションと MySQL クライアントプログラムの実行に使用したオプションを示してく ださい。 mysqld, mysql または configure スクリプト へのオプションはしばしば回答への鍵になり、とても関連しています。とに かくそれらを含めるというのは悪い考えではありません。Perl や PHP などの モジュールを使用している場合、それらのバージョン番号も含めてください。
    • 質問が権限システムに関連する場合、mysqlaccess の出力、 mysqladmin reload の出力、接続しようとしたときに得られた全てのエラー メッセージを含めてください。権限をテストするときは、まず mysqlaccess を実行してください。その後、mysqladmin reload version を実行し、最 後に問題が発生するプログラムでの接続を試みてください。mysqlaccess はMySQL インストールディレクトリ配下の `bin' ディレクトリ にあります。
    • バグに対するパッチがあるならば、当ててください。しかし、そ のパッチがすべて、私たちが求めているもので、あなたのパッチが修正するバグの テスト情報を提供しなくても、私たちがそれを使用するだろう と思わないでください。私たちはあなたのパッチに問題を見つけるかもしれません し、または、それを全く理解できないかもしれません。その場合はそれを使用で きません。 そのパッチに意味があることが正確に確かめられなければ、私たちはそれを使用し ません。テストケースは私たちにこの手助けをします。パッチが起りうる全ての状 況を扱うことを示してください。パッチが動作しない境界線のケース(それが稀 でも)を見つけた場合には、パッチは使用されないでしょう。
    • 何がバグか、なぜ発生するのか、何に依存しているのか、についての推測は通常 間違いです。MySQLチームでさえ、まずデバッガを使用してバグの実際の原因を見つけな ければ、そのことは推測できません。
    • メールメッセージ中に、あなたがリファレンスマニュアルとメールアーカイブを 調べたことを示してください。そうすれば、あなたの問題をあなた自身で 解決しようとしたことを他の人がわかります。
    • parse error が発生する場合、構文を厳密にチェックしてください。何 も間違いが見つけられなければ、多分、使用しているクエリを MySQL Server の現在のバージョンがサポートしていないということです。現 在のバージョンを使用していて、http://www.mysql.com/documentation/manual.php のマ ニュアルがあなたの使用しているクエリ構文を扱えない場合は、これは MySQL Server があなたのクエリをサポートしていないという意味です。この 場合、あなたの選択肢は、その構文をあなた自身で実装するか、 mysql-support@mysql.com に email で実装するように申し込むか です。 マニュアルではあなたの使用している構文が使えるのに対してMySQL の古いバージョンを使用している場合、文法が実装された時期について MySQL Server の変更履歴を調べてください。 「D MySQL Change History」節参照。この場合、よ り新しいバージョンの MySQL へのアップグレードを選択できます。
    • もしあなたのデータが壊れたり、または、ある特定の テーブルにアクセスするとき、エラーとなるなら、 まず最初に、テーブルを myisamchk か CHECK TABLE/REPAIR TABLE 文で検査し、修復を試みるべきです 「4 データベース管理」節参照.
    • もし、しばしばテーブルが壊れるようなら、いつ、なぜ起こるのかを 探し出してください。 この場合、`mysql-data-directory/'hostname'.err' ファイルに 何が起こっているのか含まれている場合があります。 「4.9.1 The Error Log」節参照. このファイルから関連する情報を抜きだしバグレポートに含めてください。 通常、 mysqld は更新の最中に kill されない限りは テーブルを絶対に破壊しません。もしなぜ mysqld が死ぬのか 見つけた場合は、私たちがあなたに問題解決のための修正を提供することが、 はるかに簡単になります。 「A.1 How to Determine What Is Causing Problems」節参照
    • 可能な場合、最新の MySQL Server バージョンをダウンロードして、これで問 題が解決されるかどうかをチェックしてください。全ての MySQL バー ジョンは徹底的にテストされていて、問題なしに動作するはずです。全てが可能な限り以前と 互換があるように作られていて、問題なく MySQL バージョンを切り替え ることができると私たちは信じています。 「2.2.6 使用すべき MySQL のバージョン」節参照。

    もしあなたがサポート顧客なら、より高い優先度で取り扱われるように、バグレポー トを mysql-support@mysql.com と、そして同様に、他の誰かが問題を経 験済み(そして、もしかしたら解決済み)かどうかを調べるために、適切なメーリン グリストにもクロスポストしてください。

    MyODBC のバグ報告上の情報については、 「8.3.4 MyODBC での問題をどのように報告すべきか？」節 を参照 してください。

    いくつかの一般的な問題の解決法のために 「A Problems and Common Errors」節 を参照してください。

    回答があなたに個人的に送られて、メーリングリストに送られていないときは、 あなたの問題の解決の手助けになった返事の恩恵を他の人にも与える ために、回答を要約し、その要約をメーリングリストに送信することが、良いエチケットです。

    1.6.1.4 メーリングリストで質問に答えるためのガイドライン

    あなたの回答が広く関心を持たれると考えられる場合、尋ねた人に個人的に直接 返事をする代わりに、メーリングリストに投稿したいと思うでしょう。元 の投稿者以外の人もそれから恩恵を受けられるように、十分に一般的な回答を作成 することを試みてください。メーリングリストに投稿する場合は、あなたの回答 が以前の回答と重複していないか確認して下さい。

    あなた返事の中で、質問の本質部分の要約を試みてください。質問全体を引用す ることを義務と感じないで下さい。

    HTML モードを ON にしたブラウザからメールメッセージを投稿しないでくださ い。多くのユーザはブラウザでメールを読んでいません。

    1.6.2 IRC (Internet Relay Chat) での MySQL コミュニティの支援

    いろいろなMySQLのメーリングリストに加え、IRC(Internet Relay Chat) に経験を積んだコミュニティの人がいます。次は、わたしたちが知っている、 現在のよい networks/channels です：

    • freenode (see http://www.freenode.net/ for servers)
      • #mysql 基本はMySQLの質問、しかしほかのデータベースやSQLの質問も歓迎されます。
      • #mysqlphp MySQL+PHP、人気の高い組み合わせ、の質問です。
    • EFnet (http://www.efnet.org/のサーバに関して。)
      • #mysql MySQL の質問

    IRCネットワークに接続するIRCクライアントソフトウェアを探して いるならば、X-Chat(http://www.xchat.org/)を見て ください。X-Chatは、Unixだけではなく、Windowsのプラットフォー ムでも使えます。

    1.7 MySQL はどのように標準互換か？

    この章では、MySQL がどのように ANSI SQL 標準に関係するかを説明し ます。MySQL Server は ANSI SQL 標準に対して多くの拡張を持ちます。そして、 ここでそれらが何か、またそれらの使用方法を見つけられるでしょう。また、 MySQL Server に足りない機能についての情報と、いくつかの違いを回避する方 法も見つけられるでしょう。

    わたしたちの目標は、どのように使ってもMySQL Serverの使いやすさを、正当な 理由なしで制限しないことです。可能性のあるすべての使い方に対する開発のリ ソースをもっていなくても、わたしたちは、新しい領域でMySQL Serverを使おう としている人たちに助けと提案を求めます。

    製品へのわたしたちのひとつの主な目標は、速度と信頼性を犠牲にしないで、ANSI 99適合性に向かって進み続けることです。ユーザの多くにとってMySQL Serverの 使いやすさが大きく増すときには、SQLに拡張を加えたり、SQLにない機能を追加 したりすることを恐れません。(MySQL Server 4.0の新しいHANDLERインタ フェースはこの戦略の例です。 「6.4.2 HANDLER Syntax」節参照.)

    激しいウェブ/ログの使い方とミッションクリティカルな24/7(訳注：24時間/日、 7日/週のことと考えられる)の使い方の両方を満 たすために、トランザクションと非トランザクションデータベースをサポートし 続けます。

    MySQL Serverは、小さなコンピュータシステムで、中規模なデータベース(1千万件 から1億件のレコード、またはひとつのテーブルあたり100Mバイト)で動作するとこ ろから設計し始めました。わたしたちはMySQL Serverがテラバイトのデータベース でも動作するように拡張し続けます。それと同じように、ハンドヘルド機器や組み 込み用途により適するように切りつめたMySQLバージョンをコンパイルできるように しています。MySQLサーバは設計が簡潔であるため、ソースツリーで競合しないでこ の両方の方向を採ることができます。

    いまは、リアルタイムのサポートやクラスタ化されたデータベースのサポートを(レプ リケーションサービスで多くのことがすでにできていても)目標に置いていません。

    ネイティブにXMLをサポートする必要はないと信じていますが、代わりにクライア ント側でXMLをサポートするようにわたしたちからユーザにお願いしようとしていま す。クライアント側で複雑さを取り扱うライブラリを開発するより、メインのサーバ のコードをできるかぎり「細身できれいに」しておくほうがよいと考えます。これが 前に述べた、サーバで速度と信頼性を犠牲にしない戦略の一部です。

    1.7.1 どの標準に MySQL はしたがうか？

    エントリレベルではSQL92です。ODBCのレベルは0-3.51です。

    ANSI SQL 99標準の全機能が使えるのが目標ですが、コードの速 度と品質には妥協しません。

    1.7.2 MySQLをANSIモードで実行する

    mysqldを-ansiオプションをつけて起動すると、 MySQL Serverは次のように振る舞います：

    • ||* ||はORではなく、文字列の連結です。
    • 関数名と`('の間にいくつでも空白を書けます。これは、すべての 関数名を予約語として取り扱います。
    • `"'は識別子の引用符(MySQL Serverで``'が引用符であるよう に)となり、文字列の引用符でなくなります。
    • REALは、DOUBLEの別名ではなく、FLOATの別名にな ります。
    • デフォルトのトランザクションの識別レベルは`code{SERIALIZABLE}となります。 「6.7.3 SET TRANSACTION 構文」節参照.
    • フィールドリストにないGROUP BYのなかで、フィールドや式が使えます。

    サーバをANSIモードで実行することは、次のオプションで開始することと同じです。 --sql-mode=REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES, IGNORE_SPACE,SERIALIZE,ONLY_FULL_GROUP_BY.

    1.7.3 MySQL の ANSI SQL92 に対する拡張

    MySQL Server は、他の SQL データベース内に見られないであろう、いくつか の拡張を含んでいます。それらを使用すると、コードは他の SQL サー バに移行できなくなるので注意してください。いくつかのケースでは、形式 /*! ... */ のコメントを使用することで、MySQL 拡張を含む 移行可能コードを書くことができます。この場合、MySQL Server はコメント 内のコードを実行しますが、ほかのSQLサーバはこれを無視します。例えば: 

    SELECT /*! STRAIGHT_JOIN */ col_name FROM table1,table2 WHERE ...

    '!' の後ろにバージョン番号を追加すると、文法は MySQL バー ジョンが使用されるバージョン番号と等しいか大きい場合にのみ実行されます: 

    CREATE /*!32302 TEMPORARY */ TABLE t (a int);

    上記は バージョン 3.23.02 かそれ以上の場合という意味で、そのとき MySQL Server は TEMPORARY キーワードを使用します。

    MySQL 拡張を以下に示します:

    • フィールド型 MEDIUMINT, SET, ENUM そして様々な BLOB と TEXT 型。
    • フィールド属性 AUTO_INCREMENT, BINARY, NULL, UNSIGNED そして ZEROFILL。
    • 全ての文字列比較はデフォルトでは大文字と小文字を区別しないで、現在の文字セット(デフォ ルトでは ISO-8859-1 Latin1)にしたがったソート順です。これを好まない場合は、 BINARY 属性であなたのフィールドを宣言すべきです。これは、MySQL サーバホストの上で使用される ASCII 順にしたがって比較されるようになり ます。
    • MySQL Server はデータベースを MySQL データディレクトリ 以下のディレクトリにマップし、 テーブルをデータベースディレクトリ以下のファイル名に マップします。 これはいくつかの意味を持ちます:
      • 大文字と小文字を区別するファイル名をもつ OS (多くのUNIXのような)上の MySQL Server では、 データベース名とテーブル名の大文字と小文字は区別されます。 「6.1.3 名前のケース依存性」節参照.
      • データベース名、テーブル名、インデックス名、フィールド名、別名は数字から始 めることができます(ただし、数字だけにすることはできません)。
      • テーブルのバックアップ、リネーム、移動、削除、コピーに標準システムコマン ドを使用できます。例えば、テーブルの名前を変えるには、テーブルに対応する `.MYD', `.MYI', `.frm' ファイルの名前を変えてください。
    • SQL 文では、 db_name.tbl_name 構文を使用して、違うデータベースのテーブルにアクセスできます。 いくつかのSQLサーバは同様の機能を提供しますが、これを User space と呼びます。 MySQL Server は以下のようなテーブルスペースをサポートしません: create table ralph.my_table...IN my_tablespace.
    • 数値フィールド上での LIKE が許されます。
    • SELECT 文内の INTO OUTFILE と STRAIGHT_JOIN の使用。 「6.4.1 SELECT 構文」節参照.
    • SELECT文でSQL_SMALL_RESULTオプションが使えます。
    • どのようにテーブルが結合されるかの詳細を得るための EXPLAIN SELECT。
    • インデックス名、フィールドの一部のインデックス、そして CREATE TABLE 文 内の INDEX または KEY の使用。 「6.5.3 CREATE TABLE 構文」節参照.
    • CREATE TABLE での TEMPORARY か IF NOT EXISTS の使用。
    • list 要素が一つ以上の COUNT(DISTINCT list) の使用。
    • ALTER TABLE 文内の CHANGE col_name, DROP col_name, DROP INDEX, IGNORE, RENAME の使用。 「6.5.4 ALTER TABLE 構文」節参照.
    • RENAME TABLE の使用。 「6.5.5 RENAME TABLE 構文」節参照。
    • ALTER TABLE 文内の複数の ADD, ALTER, DROP, CHANGE 節の使用。
    • キーワード IF EXISTS 付きの DROP TABLE の使用。
    • 複数のテーブルを一回の DROP TABLE で破棄できる
    • DELETE 文の LIMIT 節。
    • INSERT と REPLACE文の DELAYED 節。
    • INSERT, REPLACE, DELETE, UPDATE 文 の LOW_PRIORITY 節。
    • LOAD DATA INFILE の使用。多くの場合、この構文は ORACLE の LOAD DATA INFILE と互換があります。 「6.4.9 LOAD DATA INFILE 構文」節参照.
    • ANALYZE TABLEとCHECK TABLE、OPTIMIZE TABLE、 REPAIR TABLE 文。
    • SHOW 文。 「4.5.6 SHOW 構文」節参照.
    • `'' だけでなく `"' または `'' によって文字列を括ることが 可能。
    • エスケープ文字 `\' の使用。
    • SET 文。 「5.5.6 SET 構文」節参照.
    • GROUP BY 部に詮索されたすべてのフィールドを持つ必要はありません。 これにより、特別で、しかしきわめて普通の問合せの性能が向上します。 「6.3.6.3 Functions for Use with GROUP BY Clauses」節参照.
    • GROUP BY とともに ASC と DESC を記述できます。
    • ほかの SQL 環境から来たユーザに対し、より簡単にするため、MySQL Server は多くの関数に別名を用意しています。例えば、全ての文字列関数は ANSI SQL と ODBC 構文の両方があります。
    • MySQL Server は || と && 演算子を、C プログラミング言語 のように、論理和と論理積を意味すると理解します。MySQL では || と OR、&& と AND は同義語です。この良い構 文のため、MySQL Server は ANSI SQL の文字列結合演算子 || をサポー トしません。CONCAT() を代わりに使用してください。CONCAT() は任意の数の引数を使用できるので、|| 演算子の使用を MySQL Server に変換するのは簡単です。
    • CREATE DATABASE または DROP DATABASE. 「6.5.1 CREATE DATABASE 構文」節参照.
    • MOD() と同義の %。 N % M は MOD(N,M) と等価です。 % は C プログラマと PostgreSQL との互換のためにあります。
    • =, <>, <= ,<, >=,>, <<, >>, <=>, AND, OR, LIKE 演算子は、SELECT 文中で、FROM の左側のフィールドの比較に 使用されます。 例えば： 
      mysql> SELECT col1=1 AND col2=2 FROM tbl_name;
    • LAST_INSERT_ID() 関数。 「8.4.3.130 mysql_insert_id()」節参照.
    • REGEXP と NOT REGEXP 正規表現演算子
    • 1つまたは2以上の引数での CONCAT() または CHAR()。 MySQL Server では、これらの関数は任意の数の引数を取ることができます。
    • The BIT_COUNT(), CASE, ELT(), FROM_DAYS(), FORMAT(), IF(), PASSWORD(), ENCRYPT(), md5(), ENCODE(), DECODE(), PERIOD_ADD(), PERIOD_DIFF(), TO_DAYS(), WEEKDAY() 関数。
    • 文字列を切り落とすために TRIM() が使えます。ANSI SQL では、ひとつの 文字だけを取り除くことしかできません。
    • GROUP BY 関数 STD(), BIT_OR() そして BIT_AND()。
    • DELETE + INSERT の代わりの REPLACE の使用。 「6.4.8 REPLACE 構文」節参照.
    • FLUSH, RESET, DO 構文。
    • := で文内での変数の設定が可能: 
      SELECT @a:=SUM(total),@b=COUNT(*),@a/@b AS avg FROM test_table;
SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;

    1.7.4 MySQL と ANSI SQL92 との違い

    私たちは MySQL Server を ANSI SQL 標準と ODBC SQL 標準にしたがうように しようとしていますが、いくつかの場合、MySQL Server には違いがあります:

    • -- は空白が続く場合だけコメントになります。
    • VARCHAR フィールドでは、値が格納されるときに末尾の空白が削除されます。 「1.7.5 MySQLでの既知のエラーと欠けているデザイン」節参照。
    • いくつかの場合で、CHAR フィールドは黙って VARCHAR フィール ドに変更されます。 「6.5.3.1 暗黙のフィールド定義変更」節参照。
    • テーブルを削除するときに、テーブルについての権限は自動的には破棄されません。 テーブルの権限を破棄するには、明示的に REVOKE を発行する必 要があります。 「4.3.1 GRANT と REVOKE 構文」節参照.
    • NULL AND FALSE は FALSE ではなく NULL と評価されます。 この場合、多くの余計な条件を評価する必要があることは良いことではないと、 私たちは考えているからです。

    次の機能が MySQL Server の現在のバージョンにはありません。新しい拡張の 優先度については、次を参考にしてください http://www.mysql.com/doc/en/TODO.html. これはこのマニュアル中の TODO リストの最新バージョンです。 「1.8 MySQL and The Future (The TODO)」節参照.

    1.7.4.1 副問合せ

    バージョン 4.0 までの MySQL Server は、 INSERT ... SELECT ... と REPLACE ... SELECT ...の形式だけで 入れ子のクエリが使えます。しかし、ほかのところでもIN()が 使えます。副問合せは、4.1 の開発のツリーで実装中です。副問合せは、 4.1 の開発のツリーで開発されました。

    しかし多くの場合、副問合せを使わないクエリに書き直せます: 

    SELECT * FROM table1 WHERE id IN (SELECT id FROM table2);

    これは、次のように書き直せます: 

    SELECT table1.* FROM table1,table2 WHERE table1.id=table2.id;

    問合せ： 

    SELECT * FROM table1 WHERE id NOT IN (SELECT id FROM table2);
SELECT * FROM table1 WHERE NOT EXISTS (SELECT id FROM table2
                                       WHERE table1.id=table2.id);

    これは、次のように書き直せます： 

    SELECT table1.* FROM table1 LEFT JOIN table2 ON table1.id=table2.id
                                       WHERE table2.id IS NULL;

    さらに複雑な副問合せでは、副問合せを保持するために一時テーブルを作成で きます。しかし、この方法が使えない場合があります。この場合には、 DELETE 文でもっとも頻繁に遭遇します。DELETE 文 では、標準 SQL では（sub select の中を除いて）join が使え ません。副問合せが MySQL Server で使えるようになるまで、この状況には２ つの選択肢があります。

    最初の選択肢は、手続きプログラミング言語（Perl や PHP のような）を使用して、 SELECT クエリを発行して削除されるレコードのプライマリキーを獲得し、 それから DELETE 文（DELETE FROM ... WHERE ... IN (key1, key2, ...)）を組み立てるためにその値を使用することです。

    二番目の選択肢は、対話型 SQL を使用し、DELETE 文の集まり を、（標準 || オペレータの代わりに）MySQL 拡張 CONCAT() を使用して、自動的に組み立てることです。例えば: 

    SELECT CONCAT('DELETE FROM tab1 WHERE pkid = ', "'", tab1.pkid, "'", ';')
  FROM tab1, tab2
 WHERE tab1.col1 = tab2.col2;

    このクエリをスクリプトファイル中に置き、入力を mysql コマンドライン インタプリタに切替え、その出力を二番目のインタプリタインスタンスにパイプし ます: 

    shell> mysql --skip-column-names mydb < myscript.sql | mysql mydb

    MySQL Server 4.0 は複数のテーブルを削除できます。これで、ひとつの 表から多くの表であっても、情報に基づいて同時に行を削除できます。

    1.7.4.2 SELECT INTO TABLE

    MySQL Server は、まだ、Oracle の SQL 拡張： SELECT ... INTO TABLE ...がありません。 代わりに、MySQL Server は、ANSI SQL 構文の INSERT INTO ... SELECT ...が使え、 基本的に同じことができます。

    「6.4.3.1 INSERT ... SELECT 構文」節参照. 

    INSERT INTO tblTemp2 (fldID) SELECT tblTemp1.fldOrder_ID
       FROM tblTemp1 WHERE tblTemp1.fldOrder_ID > 100;

    代わりに、SELECT INTO OUTFILE... や CREATE TABLE ... SELECTが使えます。

    1.7.4.3 トランザクションと原子的な操作

    MySQL Server では、InnoDB と BDBTransactional table handlersで、トランザクションが使えます。 「7 MySQL テーブル型」節参照。 InnoDB が ACID 適合にします。

    しかし、MyISMといったMySQL Server のトランザクションでないテーブ ル種は、``Atomic Operations''(アトミック・オペレーション)と呼ばれ る、データ一貫性のほかの方式にしたがいます。 アトミック・オペレーション が同等かあるいはより良いパフォーマンスを提供するというのが、私たちの経験、 および考えです。MySQL Server では両方の方式があるため、ユーザは、アプリ ケーションで、アトミック・オペレーションの速度が必要か、トランザクション 機能が必要か、決定できます。この選択は、テーブルごとにできます。

    厳密に完全性を維持するには、MySQL Server の機能をどのように使用するので しょう？ そして、トランザクションの方式でこれらの機能をどのように比較す るのでしょう？

    1. トランザクションの方式では、もし、あなたのアプリケーションがきわどい状況 でCOMMIT の代わりに ROLLBACK の呼び出しに依存しているなら、 トランザクションはより便利でしょう。おまけに、トランザクションは、完了で きなかった更新や不整合を起こしたデータが、確実にデータベースに登録されな いようにできます。そのサーバには、自動的な rollback をする機会が与えられ、 あなたのデータは守られるでしょう。MySQL Server では、ほとんどの場合、更 新前の簡単なチェックを含ませたり、データベースの矛盾を検査して自動的に修 復したり、警告の表示を行ったりする簡単なスクリプトを実行したりすることで、 発生しうる問題を解決できます。MySQL ログを使ったり外部へログを追加したり することで、通常、データに不整合を起こさないで、テーブルを完全に修復でき ることに注意してください。
    2. しばしば、トランザクション的に欠陥のあるな更新は、原子的(アトミック)にな るように書き換えることができます。一般的に、トランザクションが解決するす べての一貫性の問題は、データベースが自動的にアボートしないことを保証する ことで、LOCK TABLE、または、原子的な更新で解決できます。これは、 トランザクション的なデータベースに共通の問題です。
    3. もしサーバがダウンすれば、たとえトランザクション的なシステムでもデータを 失います。異なるシステムが存在する違いは、単に、データを失ってもよい時間 幅がどれだけ小さいかにあります。100% 安全なシステムはなく、単に``十分に 安全''があるだけです。最高に安全なトランザクションデータベースと名声の高 いOracleでさえ、そのようなときには、ときどき、データを失います。 MySQL Server を安全にするには、バックアップを取ることと、更新ログを有効 にすることだけです。これで、あなたが他のトランザクションを持つデータベー スで行っているようないかなる場面での修復が可能です。もちろん、バックアッ プをとることは、どのデータベースを使用しているかに関わらず、常に良いこと です。@end enumerate トランザクションの方法は、長所と短所があります。多くのユーザとアプリケー ション開発者は、楽に、アボートが発生したときの問題に関してコードを書ける か、または書く必要があるかに依存します。しかし、原子的な操作の方式が初め てであっても、よりトランザクションに慣れていても、トランザクションを使わ ないテーブルが、高度に調整されたトランザクションテーブルに対して、最高 3 倍から 5 倍速いという長所 一貫性がいちばん重要な状況では、MySQL Server は、トランザクション水準を、 またはトランザクションを使わないテーブルでも高い信頼性と一貫性を提供します。 LOCK TABLEでテーブルをロックすると、一貫性の確認が済むまで、すべ ての更新は待たされます。(書き込みロックと対称に)読み出しロックだけを取得 するときは読み出しと挿入は、まだ、許されます。新しく挿入されたレコードは、 読み込みロックをもったクライアントからは、読み込みロックを解放するまで見 えません。INSERT DELAYED を使うと、挿入をローカルにある待ち行列に、 ロックを解放するまで、挿入が完了するまでクライアントを待たせることなく、 積むことができまます。 「6.4.4 INSERT DELAYED 構文」節参照. ここでいう``Atomic''(原子性)は、魔法ではありません。ある特定の更新が実行 している間は、ほかのユーザは阻まれることを確実にすることを意味し、自動的 なロールバック(あまり注意を払わないときにトランザクション的なテーブルで 起きえる)が起きえないことだけです。また MySQL Server は、汚染された読み 込みが起きないことを保証します。 次は、トランザクションでないテーブルでのいくつかのテクニックです。
      • Loops that need transactions normally can be coded with the help of LOCK TABLES, and you don't need cursors when you can update records on the fly.
      • To avoid using ROLLBACK, you can use the following strategy:
        1. Use LOCK TABLES ... to lock all the tables you want to access.
        2. Test conditions.
        3. Update if everything is okay.
        4. Use UNLOCK TABLES to release your locks.
        This is usually a much faster method than using transactions with possible ROLLBACKs, although not always. The only situation this solution doesn't handle is when someone kills the threads in the middle of an update. In this case, all locks will be released but some of the updates may not have been executed.
      • You can also use functions to update records in a single operation. You can get a very efficient application by using the following techniques:
        • Modify fields relative to their current value.
        • Update only those fields that actually have changed.
        For example, when we are doing updates to some customer information, we update only the customer data that has changed and test only that none of the changed data, or data that depends on the changed data, has changed compared to the original row. The test for changed data is done with the WHERE clause in the UPDATE statement. If the record wasn't updated, we give the client a message: "Some of the data you have changed has been changed by another user." Then we show the old row versus the new row in a window, so the user can decide which version of the customer record he should use. This gives us something that is similar to column locking but is actually even better because we only update some of the columns, using values that are relative to their current values. This means that typical UPDATE statements look something like these: 
        UPDATE tablename SET pay_back=pay_back+'relative change';

UPDATE customer
  SET
    customer_date='current_date',
    address='new address',
    phone='new phone',
    money_he_owes_us=money_he_owes_us+'new_money'
  WHERE
    customer_id=id AND address='old address' AND phone='old phone';
        As you can see, this is very efficient and works even if another client has changed the values in the pay_back or money_he_owes_us columns.
      • In many cases, users have wanted ROLLBACK and/or LOCK TABLES for the purpose of managing unique identifiers for some tables. This can be handled much more efficiently by using an AUTO_INCREMENT column and either the SQL function LAST_INSERT_ID() or the C API function mysql_insert_id(). 「8.4.3.130 mysql_insert_id()」節参照. You can generally code around row-level locking. Some situations really need it, but they are very few. InnoDB tables support row-level locking. With MyISAM, you can use a flag column in the table and do something like the following: 
        UPDATE tbl_name SET row_flag=1 WHERE id=ID;
        MySQL returns 1 for the number of affected rows if the row was found and row_flag wasn't already 1 in the original row. You can think of it as though MySQL Server changed the preceding query to: 
        UPDATE tbl_name SET row_flag=1 WHERE id=ID AND row_flag <> 1;

      1.7.4.4 ストアドプロシジャとトリガ

      ストアドプロシジャは、サーバ内でコンパイルでき格納できる SQL コマンドの 集まりです。一度これが行われると、クライアントはクエリ全体の再発行を保 持する必要がなく、ストアドプロシジャを参照できます。これはさらにより速い速度を提 供します。クエリは一度だけ解釈され、より少ないデータがサーバとクライアン ト間で送信されるからです。サーバ内に関数ライブラリを持つことによりレ ベルを上げることもできます。

      トリガは特別なイベントが発生したときに呼び出されるストアドプロシジャです。 例えば、トランザクションテーブルからレコードが削除されるたびにトリガされ、 それに対応する顧客を顧客テーブルから自動的に削除するという、 ストアドプロシジャをインストールすることができます。

      The planned update language will be able to handle stored procedures. Our aim is to have stored procedures implemented in MySQL Server around version 5.0. We are also looking at triggers.

      1.7.4.5 外部キー

      注意: SQL の外部キーはテーブルを結合するためには使用できませんが、指示の 完全性の検査のために良く使用されます(foreign key constraints)。 SELECT 文で複数 テーブルから結果を得たい場合、テーブルの結合によってこれを行います： 

      SELECT * FROM table1,table2 WHERE table1.id = table2.id;

      「6.4.1.1 JOIN 構文」節参照. 「3.5.6 Using Foreign Keys」節参照.

      In MySQL Server 3.23.44 and up, InnoDB tables support checking of foreign key constraints. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. For other table types, MySQL Server does parse the FOREIGN KEY syntax in CREATE TABLE commands, but without further action being taken.

      MySQL 内での FOREIGN KEY 構文は、他の SQL ベンダの CREATE TABLE コマンドとの互換のためだけに存在します; これは何も行 ないません。ON DELETE ... がない FOREIGN KEY 構文は、目的 の作成のために主に使われます。いくつかの ODBC アプリケーションは、自動的 に WHERE 節を提供するために、これを使用しますが、しかしこれは通常 簡単に無効にできます。FOREIGN KEY はときどき強制チェックとして使用さ れます。しかし、テーブルに正しい順で行が挿入される場合、このチェックは実 際には不要です。いくつかのアプリケーションがそれが存在することを要求する ため MySQL はこれらの節だけをサポートします（それが動作するかど うかに関わらず）。

      MySQL Server では、外部キーを持つテーブルからレコードを削除するときに適 切な DELETE 文をアプリケーションに追加することで、 ON DELETE ... が実装されていないという問題を回避できます。実際に は、これは速く(いくつかの場合はより速く)そして外部キーの使用よりもさらに 可搬性があります。

      In MySQL Server 4.0 you can use multi-table delete to delete rows from many tables with one command. 「6.4.6 DELETE 構文」節参照.

      In the near future we will extend the FOREIGN KEY implementation so that the information will be saved in the table specification file and may be retrieved by mysqldump and ODBC. At a later stage we will implement the foreign key constraints for applications that can't easily be coded to avoid them.

      Do keep in mind that foreign keys are often misused, which can cause severe problems. Even when used properly, it is not a magic solution for the referential integrity problem, although it does make things easier in some cases.

      Some advantages of foreign key enforcement:

      • Assuming proper design of the relations, foreign key constraints will make it more difficult for a programmer to introduce an inconsistency into the database.
      • Using cascading updates and deletes can simplify the client code.
      • Properly designed foreign key rules aid in documenting relations between tables.

      Disadvantages:

      • Mistakes, which are easy to make in designing key relations, can cause severe problems@-for example, circular rules, or the wrong combination of cascading deletes.
      • A properly written application will make sure internally that it is not violating referential integrity constraints before proceding with a query. Thus, additional checks on the database level will only slow down performance for such an application.
      • It is not uncommon for a DBA to make such a complex topology of relations that it becomes very difficult, and in some cases impossible, to back up or restore individual tables.

      1.7.4.6 ビュー

      It is planned to implement views in MySQL Server around version 5.0.

      Views are mostly useful for letting users access a set of relations as one table (in read-only mode). Many SQL databases don't allow one to update any rows in a view, but you have to do the updates in the separate tables.

      As MySQL Server is mostly used in applications and on web systems where the application writer has full control on the database usage, most of our users haven't regarded views to be very important. (At least no one has been interested enough in this to be prepared to finance the implementation of views.)

      One doesn't need views in MySQL Server to restrict access to columns, as MySQL Server has a very sophisticated privilege system. 「4.2 General Security Issues and the MySQL Access Privilege System」節参照.

      1.7.4.7 コメント開始としての `--'

      他のいくつかの SQL データベースは、`--' をコメントの開始のために使 用します。MySQL Server は `#' をコメント開始文字とします。 mysql コマンドラインツールが `--' で始まる全ての行を削除した としてもです。MySQL では C コメントスタイル /* これはコメ ント */ も使用できます。 「6.1.6 コメント 構文」節参照。

      MySQL Server バージョン 3.23.3 以上は `--' をサポートしません; この退化したコメントスタイルは、次のコードのように !payment! の payment の値を自動的に挿入するような何かを使用して自動的に生成される SQL クエリで多くの問題を引き起こすためです: 

      UPDATE tbl_name SET credit=credit-!payment!

      payment の値が負の場合に何が起きると思いますか？ 1--1 は正しい SQL なので、私たちは `--' をコメント開始と見なす ことはひどいことだと思います。

      しかし MySQL Server バージョン 3.23 では次を使用できます: 1-- これはコメント

      以降の説明では、バージョン 3.23 よりも前の MySQL を実行している場 合だけが対象です:

      テキストファイルの SQL プログラムが `--' コメントを含んでいる場合、 次を使用すべきです: 

      shell> replace " --" " #" < text-file-with-funny-comments.sql \
         | mysql database

      通常の次の代わりに: 

      shell> mysql database < text-file-with-funny-comments.sql

      次の方法でも、コマンドファイル中の `--' コメントを `#' コメン トに変更できます: 

      shell> replace " --" " #" -- text-file-with-funny-comments.sql

      それらは次のコマンドで戻してください: 

      shell> replace " #" " --" -- text-file-with-funny-comments.sql

      1.7.5 MySQLでの既知のエラーと欠けているデザイン

      1.7.5.1 新しいバージョンで修正されたバージョン3.23におけるエラー

      バージョン3.23でのエラーが、新しいバージョンで修正されました。 次のようなエラー・バグは、MySQL 3.23 では、修正されていませんでした。というのは、そうしたバグやエラーを直すことは、たくさんのコードの改変を伴うだろうからです。そしてこうした改変は、もっとひどい他のバグを生みかねません。そういうバグはまた、'not fatal'とか'bearable'にクラス分けされます。

      • 他のスレッドで、テーブルをロックしようとする一方で、マルティプル・テーブルで LOCK TABLE を実行し、同じコネクションで、マルティプル・テーブルのうち一つでDROP TABLE を実行する場合には、デットロックを受けることがあり得ます。ですが、これを解決するために、関連するスレッドのいずれかに、KILL を実行することができます。これは、4.0.12 における修正です。
      • テーブルの一つが空であるところで、SELECT MAX(key_column) FROM t1,t2,t3... を実行しても、NULL は返ってきません。それに代わって、フィールドの最大値を返します。これは、4.0.11における修正です。

      1.7.5.2 MySQL での既知のエラーと欠けているデザイン

      次のような問題は、既知の問題で、優先的に処理されるべき問題です。

      • BDBテーブル上の ANALYZE TABLE は、場合によっては、mysqld を再起動しなくては、テーブルを使用できなくするかもしれないものです。 これが起きた際には、MySQLのエラーファイルに、次のようなエラーが表示されるでしょう。 
        001207 22:07:56  bdb:  log_flush: LSN past current end-of-log
      • 完了していないマルチ・ステートメント処理を実行中の、BDB テーブルで、ALTER TABLE をexecuteしないでください。 （その処理は、恐らく無視されてしまうことでしょう。）
      • ANALYZE TABLE と OPTIMIZE TABLE と REPAIR TABLE は、 それに INSERT DELAYED を用いているテーブルに、問題を起こす原因になるかもしれないものです。
      • LOCK TABLE ... と FLUSH TABLES ... を行うことは、テーブル上で実行中のやりかけの処理がなくなることを、保証するものではありません。
      • BDBテーブルは、開くのが少し遅いです。 もしデーターベースの中に多くのBDBテーブルがあるならば、-A オプションを使っていたり、rehash を使っている場合には、データーベース上で mysql クライアントを使用するのには、時間がかかります。もしサイズの大きなテーブルを貯めこんでいるなら、これは特に気をつけなくてはいけないことです。
      • 今のところの複製プロトコルは、LOAD DATA INFILE や、一文字以上の改行文字を、取り扱えません。

      次の問題は、既知の問題ですが、期限内に解決されることでしょう。

      • 解決される一時的なテーブルを用いるクエリーで、RPAD 関数や右側にブランクを加えて終わる文字列関数を使う場合には、結果として得られる文字列は全て、RTRIM 化されてしまうことでしょう。これはクエリーの一例です: SELECT RPAD(t1.field1, 50, ' ') AS f2, RPAD(t2.field2, 50, ' ') AS f1 FROM table1 as t1 LEFT JOIN table2 AS t2 ON t1.record=t2.joinID ORDER BY t2.record; こうしたクエリーの使用をしても、結果として得られるフィールドの右側にブランクを得ることはできないでしょう、というのがこのバグの最終的な結果です。 上で挙げた動作というのは、MySQLの全てのバージョンにあることです。 これの原因は、最初に一時的なテーブルに用いられるHEAPテーブルが、VARCHARのカラムを取り扱うことができないことに起因します。 この動作は、4.1のリリースの一つで修正されることでしょう。
      • SET CHARACTER SET を使う場合には、データーベースやテーブルやフィールドの名前に、翻訳された文字を使うことはできません。
      • LIKE ... ESCAPE において、ESCAPE と一緒に _ や % を使うことはできません。
      • (+01.00, 1.00, 01.00),といった具合に、異なったフォーマットで記録された数値を持った DECIMAL カラムがある場合には、GROUP BY はそれぞれの値を異なった値と見なします。
      • WHERE 抜きで用いられる DELETE FROM merge_table は、テーブルのためのマッピングをクリアするだけです。マッピングされたテーブルにある全部を削除するわけではありません。
      • MIT-pthread を使用するとき、他のディレクトリでビルドできません。 これは MIT-pthread の変更を要求するため、私たちは、これを修正しそうにないです。 「2.3.6 MIT-pthreads に関して」節参照.
      • BLOB の値は、ORDER BY や ORDER BY や DISTINCT に用いる場合には、「信頼性」のないものになります。 これらの場合、 BLOB の比較の際には最初の max_sort_length バイト （デフォルト1024）だけが使用されます。 これは mysqld の -O max_sort_length オプションで変更可能です。 ほとんどの場合には、substringを用いて行います。 SELECT DISTINCT LEFT(blob,2048) FROM tbl_name といった具合に。
      • 計算は、BIGINT か DOUBLE でなされます。（両方とも、普通は６４ビットの長さです。）どちらを使うかというのは、計算結果を渡してくれる式によってしまいます。 bit関数は BIGINT の精度でなされ、IF と ELT() は BIGINT か DOUBLE の精度でなされ、その他は DOUBLE でなされるというのが、一般的なルールです。 One should try to avoid using unsigned long long values if they resolve to be bigger than 63 bits (9223372036854775807) for anything else than bit fields! MySQL Server 4.0 has better BIGINT handling than 3.23.
      • 全ての文字型のフィールド、BLOB と TEXT はのぞいて、は、 検索されるときに最後についているスペースを自動で取り除きます。 CHAR 型ではこれは OK で、この特徴は ANSI SQL92 に従っていると見なされるでしょう。 MySQL Server のバグは、 VARCHAR でも同様に行ってしまうことです。
      • 一つのテーブルには、 ENUM と SET のカラムは、255までしか使えません。
      • MIN() や MAX() や他の集計関数においては、MySQLは今のところ、その組み合わせの中での文字列の相対的な位置によるよりもむしろ、カラムの文字列の値によって、 ENUM と SET のカラムを比較しています。
      • mysqld_safe (旧 safe_mysqld ) は、mysqld からのメッセージの全てを、mysqld ログにリダイレクトします。 これにともなう問題のひとつは、ログを開いたり、再び開いたりするために、mysqladmin refresh を実行する場合には、stdout と stderr が、古いログにリダイレクトされたままだということです。広範囲にわたって --log を用いる場合には、 `'hostname'.log' の代わりに `'hostname'.err' に記録するために、mysqld_safe を編集すべきです。それで、古いものを削除し、m mysqladmin refresh を実行することで、古いログのためのスペースを簡単に再利用することができます。
      • UPDATE 文において、カラムは左から右へと更新されます。更新されたカラムを参照する場合には、元の値の代わりに、更新された値が渡されることでしょう。例を見てみましょう。 
        mysql> UPDATE tbl_name SET KEY=KEY+1,KEY=KEY+1;
        これは、KEY を 1 の代わりに 2 で更新します。
      • 同じクエリーにおいて、一時的なテーブルを、一回より多く使うことができません。例えば次のようなものは、実行できません。 
        mysql> SELECT * FROM temporary_table, temporary_table AS t2;
      • RENAME は、 TEMPORARY テーブルと一緒には、もしくは MERGE テーブルの中のテーブルと一緒には実行できません。
      • Optimizerは、テーブルの結合において hidden カラムが用いられるかどうかで、 DISTINCT を違ったふうに扱います。テーブル結合においては、hiddenカラムは、結果の一部として数えられます。（たとえカラムが表示されなくてもです。）一方で、普通のクエリーにおいては、hiddenカラムは DISTINCT 比較には加えられません。 DISTINCT を実行する際には、hiddenカラムを決して比較できないように、将来的には恐らく変えることでしょう。 これの実例は次のようなものです。 
        SELECT DISTINCT mp3id FROM band_downloads
       WHERE userid = 9 ORDER BY id DESC;
        そして 
        SELECT DISTINCT band_downloads.mp3id
       FROM band_downloads,band_mp3
       WHERE band_downloads.userid = 9
       AND band_mp3.id = band_downloads.mp3id
       ORDER BY band_downloads.id DESC;
        二番目のケースでは、MySQLサーバー3.23.xでは、リザルトセットでは二つの同じ列を渡してくるかもしれません。（というのも、隠れた id カラムは異なっているかもしれないからです。） これは、ORDER BYしたカラムを結果のところで指定しないようなクエリー、ANSI SQLでは認められていないことをしたクエリーのみについて起こることだとといことに、気をつけてください。
      • MySQLサーバーでは、トランザクションをサポートしていない種類のテーブルで動かすことが許されていて、それゆえに MySQL サーバーは、データをロールバックできません。そのため、MySQL サーバー上では、幾つかのことが、他の SQL サーバー上とは異なった風に、動作します。このことはまさに、MySQL サーバーが、SQL コマンドのために、ロールバックをする必要が決してないことを保証するためのものです。このことは、カラムの値がアプリケーションにおいて、チェックされねばならない際には、少し困りものかもしれません。ですがこのことは、素晴らしいスピードの増加を、実際に提供してくれることでしょう。そしてそれをしなければとても実現が難しかったであろうような、何らかの効率化を実現するのを、MySQLサーバーに許すようになるでしょう。 もし正しくない値をカラムにセットするなら、MySQLサーバーは、ロールバックをする代わりに、カラムの中に、可能で一番適切な値を記録させることでしょう。
        • 数値カラムにおける範囲の外で、値を記録しようとするなら、MySQLサーバーはその代わりに、そのカラムにおける最も小さいかもしくは最も大きな可能な値を記録することでしょう。
        • 数値カラムに、数値ではじまらない文字列を記録したい場合には、MySQLサーバーは、その中に０を記録することでしょう。
        • NULL の値をとらないカラムの中に NULL を記録したい場合には、MySQLサーバーは、０か’’（空の文字列）をその代わりにその中に記録するでしょう。（ですがこの動作は、-DDONT_USE_DEFAULT_FIELDSコンパイルオプションで、変えることが出来ます。）
        • MySQLサーバーは、 DATE と DATETIME のカラムに、いくつかの誤った日付（2000-02-31とか2000-02-00のような）の値を記録することができます。これは、日付を確認するというのは、SQLサーバーの仕事ではない、という考えから来ています。MySQLが日付を記録し、全く同じ日付に訂正できる場合には、MySQLはその日付を記録することでしょう。もしその日付が全く間違っている（日付を記録するサーバーの性能を越えている）ならば、それならば特別な日付の値0000-00-00が、カラムの中に記録されることでしょう。
        • もし ENUM カラムに、サポートされていない値をセットするならば、それはエラーの値である空の文字列、数値の０をセットするでしょう。
        • もし SET カラムに、サポートされていない値をセットするならば、その値は無視されるでしょう。
      • 空のセットを返すようなクエリー上で、 PROCEDURE を実行するならば、幾つかの場合には、 PROCEDURE はそのカラムを変えることはないでしょう。
      • MERGE 型のテーブルの作成する際には、強調されているテーブルの型に互換性があるかどうかは、チェックされません。
      • MySQLサーバーは、 NaN やダブル型の値の -Inf や Inf を、まだ扱えません。これらを使用することは、データをエクスポートしたりインポートしたりする際の問題の原因になるでしょう。中間的な解決として、 NaN を NULL に、 -Inf や Inf を各々の最小限の double 型のとりうる最大値に変更しなくてはなりません。
      • 負の数値における LIMIT は、大きな正の数値として扱われます。
      • もし MERGE テーブルにおいて用いられるテーブルに、 UNIQUE インデックスを先ず加えるために、 ALTER TABLE を用いるならば、さらに MERGE テーブル上で普通のインデックスを加えるために、 ALTER TABLE を用いるならば、そのテーブルの中ではユニークではなかった古いキーがあった場合には、キーの順番はテーブルごとに異なっていることでしょう。これは、 ALTER TABLE が、重複キーをなるべく速く検知できるようにするために、普通のキーの前に、 UNIQUE キーをおくからです。

      以下のものが、MySQLの以前のバージョンにおいて知られていたバグです。:

      • LOCK TABLES でロックされたような多くのテーブルの中の一つであるテーブルを、 DROP TABLE する場合には、hungスレッドが取得されます。
      • 以下のような場合には、コアdumpが取得されます:
        • 遅れたインサートハンドラーが、テーブルに対して未決定のinsertを有する場合。
        • WRITE をともなう LOCK table
        • FLUSH TABLES.
      • MySQLサーバー・バージョン3.23.2以前では、同じキー上の WHERE を有するキーを更新する UPDATE は、失敗するかもしれません。というのは、そのキーはレコードを検索するために、用いられ、全く同じ列が複数回にわたり見出されたかもしれないからです。: 
        UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100;
        代替手段は、次のように使うことです: 
        mysql> UPDATE tbl_name SET KEY=KEY+1 WHERE KEY+0 > 100;
        MySQLサーバーが、 WHERE 句の表現の中にあるインデックスを用いることはないでしょうから、これは動作します。
      • MySQL Server バージョン 3.23 より前では、全ての数値型で、少数部分が削られてしまいます。 これは、そのフィールドが何桁の小数部を持つか、定義しなければならなかった、と いうことです。 全ての結果は10進の数で正しく返ってきました。

      プラットホームに特有のバグについては、コンパイリングとポーティングについての節を参照してください。

      1.8 MySQL and The Future (The TODO)

      This section lists the features that we plan to implement in MySQL Server.

      もしあなたが優先順位に影響を及ぼしたければ、どうかライセンスかサポート登録して、 私たちにあなたがより速く欲しいものを言ってください。 「1.4 MySQL ライセンスとサポート」節参照.

      The plan is that we in the future will support the full ANSI SQL99 standard, but with a lot of useful extensions. The challenge is to do this without sacrificing the speed or compromising the code.

      1.8.1 Things That Should be in 4.0

      All done. We now only do bug fixes for MySQL 4.0. 「D.3 Changes in release 4.0.x (Gamma)」節参照. Development has shifted to 4.1 & 5.0

      1.8.2 Things That Should be in 4.1

      The following features are planned for inclusion into MySQL 4.1. For a list what is already done in MySQL 4.1, see 「D.2 Changes in release 4.1.x (Alpha)」節参照.

      • Stable OpenSSL support (MySQL 4.0 supports rudimentary, not 100% tested, support for OpenSSL).
      • Character set casts and syntax for handling multiple character sets.
      • Help for all commands from the client.
      • More testing of prepared statements and multiple characters sets for one table.

      1.8.3 Things That Should be in 5.0

      The following features are planned for inclusion into MySQL 5.0. Note that because we have many developers that are working on different projects, there will also be many additional features. There is also a small chance that some of these features will be added to MySQL 4.1. For a list what is already done in MySQL 4.1, see 「D.2 Changes in release 4.1.x (Alpha)」節参照.

      • Stored procedures.
      • Foreign keys support for all table types.
      • New text based table definition file format (`.frm' files) and a table cache for table definitions. This will enable us to do faster queries of table structures and do more efficient foreign key support.
      • SHOW COLUMNS FROM table_name (used by mysql client to allow expansions of column names) should not open the table, only the definition file. This will require less memory and be much faster.
      • Fail-safe replication.
      • Online backup with very low performance penalty. The online backup will make it easy to add a new replication slave without taking down the master.
      • ROLLUP and CUBE OLAP (Online Analytical Processing) grouping options for data warehousing applications.
      • Allow DELETE on MyISAM tables to use the record cache. To do this, we need to update the threads record cache when we update the `.MYD' file.
      • When using SET CHARACTER SET we should translate the whole query at once and not only strings. This will enable users to use the translated characters in database, table, and column names.
      • Resolving the issue of RENAME TABLE on a table used in an active MERGE table possibly corrupting the table.
      • Add options to the client/server protocol to get progress notes for long running commands.
      • Implement RENAME DATABASE. To make this safe for all storage engines, it should work as follows:
        • Create the new database.
        • For every table do a rename of the table to another database, as we do with the RENAME command.
        • Drop the old database.
      • Add true VARCHAR support (there is already support for this in MyISAM).
      • BIT 型を 1 bit 取るように最適化 （今 BIT は一文字とります）
      • New internal file interface change. This will make all file handling much more general and make it easier to add extensions like RAID. (the current implementation is a hack.)
      • Better in-memory (HEAP) tables:
        • Dynamic size rows.
        • Faster row handling (less copying)

      1.8.4 近い将来に完了せねばならないもの

      • Don't allow more than a defined number of threads to run MyISAM recover at the same time.
      • Change INSERT ... SELECT to optionally use concurrent inserts.
      • Return the original field types() when doing SELECT MIN(column) ... GROUP BY.
      • Multiple result sets.
      • Make it possible to specify long_query_time with a granularity in microseconds.
      • Link the myisampack code into the server.
      • Port of the MySQL code to QNX.
      • Port of the MySQL code to BeOS.
      • Port of the MySQL clients to LynxOS.
      • Add a temporary key buffer cache during INSERT/DELETE/UPDATE so that we can gracefully recover if the index file gets full.
      • もし他の disk に symlink されているテーブルに対して ALTER TABLE を 実行した場合、一時テーブルをこの disk に作成するようにする
      • Implement a DATE/DATETIME type that handles time zone information properly so that dealing with dates in different time zones is easier.
      • FreeBSD and MIT-pthreads; do sleeping threads take CPU time?
      • Check if locked threads take any CPU time.
      • Fix configure so that one can compile all libraries (like MyISAM) without threads.
      • Add an option to periodically flush key pages for tables with delayed keys if they haven't been used in a while.
      • キーの部分での JOIN を許す (最適化問題)
      • INSERT SQL_CONCURRENT and mysqld --concurrent-insert to do a concurrent insert at the end of the file if the file is read-locked.
      • サーバサイドのカーソル
      • Check if lockd works with modern Linux kernels; if not, we have to fix lockd! To test this, start mysqld with --enable-locking and run the different fork* test suits. They shouldn't give any errors if lockd works.
      • Allow SQL variables in LIMIT, like in LIMIT @a,@b.
      • Allow update of variables in UPDATE statements. For example: UPDATE TABLE foo SET @a=a+b,a=@a, b=@a+c.
      • Change when user variables are updated so that one can use them with GROUP BY, as in the following example: SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id.
      • Don't add automatic DEFAULT values to columns. Give an error when using an INSERT that doesn't contain a column that doesn't have a DEFAULT.
      • Fix `libmysql.c' to allow two mysql_query() commands in a row without reading results or give a nice error message when one does this.
      • なぜいくつかの FreeBSD システムで MIT-pthreads ctime() が動かないか検証。
      • TIMESTAMP と AUTO_INCREMENT フィールドを更新しないように、 IMAGE オプションを LOAD DATA INFILE に追加。
      • Added LOAD DATE INFILE ... UPDATE syntax.
        • For tables with primary keys, if the data contains the primary key, entries matching that primary key are updated from the remainder of the columns. However, columns missing from the incoming data feed are not touched.
        • For tables with primary keys that are missing some part of the key in the incoming data stream, or that have no primary key, the feed is treated as a LOAD DATA INFILE ... REPLACE INTO now.
      • Make LOAD DATA INFILE understand syntax like: 
        LOAD DATA INFILE 'file_name.txt' INTO TABLE tbl_name
     TEXT_FIELDS (text_field1, text_field2, text_field3)
     SET table_field1=CONCAT(text_field1, text_field2),
         table_field3=23
     IGNORE text_field3
        This can be used to skip over extra columns in the text file, or update columns based on expressions of the read data.
      • LOAD DATA INFILE 'file_name' INTO TABLE 'table_name' ERRORS TO err_table_name. This would cause any errors and warnings to be logged into the err_table_name table. That table would have a structure like: 
        line_number    - line number in datafile
error_message  - the error/warning message
and maybe
data_line      - the line from the datafile
      • mysql から自動的に Netscape に出力
      • LOCK DATABASES. (いろいろなオプション付きで)
      • Functions: ADD_TO_SET(value,set) and REMOVE_FROM_SET(value,set).
      • t1 JOIN t2 ON ... と t1 JOIN t2 USING ... の使用の追加。 現在、 LEFT JOIN のみが使用できます。
      • Many more variables for show status. Records reads and updates. Selects on 1 table and selects with joins. Mean number of tables in select. Number of ORDER BY and GROUP BY queries.
      • If you abort mysql in the middle of a query, you should open another connection and kill the old running query. Alternatively, an attempt should be made to detect this in the server.
      • Add a storage engine interface for table information so that you can use it as a system table. This would be a bit slow if you requested information about all tables, but very flexible. SHOW INFO FROM tbl_name for basic table information should be implemented.
      • Allow SELECT a FROM crash_me LEFT JOIN crash_me2 USING (a); in this case a is assumed to come from the crash_me table.
      • Oracle-like CONNECT BY PRIOR ... to search hierarchy structures.
      • mysqladmin copy database new-database; requires COPY command to be added to mysqld.
      • Processlist should show number of queries/threads.
      • SHOW HOSTS for printing information about the hostname cache.
      • DELETE and REPLACE options to the UPDATE statement (this will delete rows when one gets a duplicate key error while updating).
      • Change the format of DATETIME to store fractions of seconds.
      • Add all missing ANSI92 and ODBC 3.0 types.
      • Change table names from empty strings to NULL for calculated columns.
      • Don't use Item_copy_string on numerical values to avoid number->string->number conversion in case of: SELECT COUNT(*)*(id+0) FROM table_name GROUP BY id
      • Make it possible to use the new GNU regexp library instead of the current one (the GNU library should be much faster than the old one).
      • Change so that ALTER TABLE doesn't abort clients that execute INSERT DELAYED.
      • Fix so that when columns are referenced in an UPDATE clause, they contain the old values from before the update started.
      • Add simulation of pread()/pwrite() on Windows to enable concurrent inserts.
      • A logfile analyser that could parse out information about which tables are hit most often, how often multi-table joins are executed, etc. It should help users identify areas or table design that could be optimised to execute much more efficient queries.
      • Add SUM(DISTINCT).
      • Add ANY(), EVERY(), and SOME() group functions. In ANSI SQL these work only on boolean columns, but we can extend these to work on any columns/expressions by applying: value == 0 -> FALSE and value <> 0 -> TRUE.
      • Fix that the type for MAX(column) is the same as the column type: 
        mysql> CREATE TABLE t1 (a DATE);
mysql> INSERT INTO t1 VALUES (NOW());
mysql> CREATE TABLE t2 SELECT MAX(a) FROM t1;
mysql> SHOW COLUMNS FROM t2;
      • Come up with a nice syntax for a statement that will UPDATE the row if it exists and INSERT a new row if the row didn't exist (like REPLACE works with INSERT / DELETE).

      1.8.5 いつかは行うべきもの

      • Implement function: get_changed_tables(timeout,table1,table2,...).
      • Change reading through tables to use memmap when possible. Now only compressed tables use memmap.
      • Make the automatic timestamp code nicer. Add timestamps to the update log with SET TIMESTAMP=#;.
      • Use read/write mutex in some places to get more speed.
      • Full foreign key support in for MyISAM tables, probably after the implementation of stored procedures with triggers.
      • Simple views (first on one table, later on any expression).
      • Automatically close some tables if a table, temporary table, or temporary files gets error 23 (not enough open files).
      • When one finds a field=#, change all occurrences of field to #. Now this is only done for some simple cases.
      • Change all const expressions with calculated expressions if possible.
      • Optimise key = expression. At the moment only key = field or key = constant are optimised.
      • Join some of the copy functions for nicer code.
      • Change `sql_yacc.yy' to an inline parser to reduce its size and get better error messages (5 days).
      • Change the parser to use only one rule per different number of arguments in function.
      • Use of full calculation names in the order part (for ACCESS97).
      • MINUS, INTERSECT, and FULL OUTER JOIN. (Currently UNION [in 4.0] and LEFT OUTER JOIN are supported.)
      • SQL_OPTION MAX_SELECT_TIME=# to put a time limit on a query.
      • Make the update log write to a database.
      • Add to LIMIT to allow retrieval of data from the end of a result set.
      • Alarm around client connect/read/write functions.
      • Please note the changes to safe_mysqld: according to FSSTND (which Debian tries to follow) PID files should go into `/var/run/<progname>.pid' and log files into `/var/log'. It would be nice if you could put the "DATADIR" in the first declaration of "pidfile" and "log", so the placement of these files can be changed with a single statement.
      • Allow a client to request logging.
      • Add use of zlib() for gzip-ed files to LOAD DATA INFILE.
      • Fix sorting and grouping of BLOB columns (partly solved now).
      • Stored procedures. Triggers are also being looked at.
      • A simple (atomic) update language that can be used to write loops and such in the MySQL server.
      • Change to use semaphores when counting threads. One should first implement a semaphore library to MIT-pthreads.
      • Don't assign a new AUTO_INCREMENT value when one sets a column to 0. Use NULL instead.
      • Add full support for JOIN with parentheses.
      • As an alternative for one thread/connection manage a pool of threads to handle the queries.
      • Allow one to get more than one lock with GET_LOCK. When doing this, one must also handle the possible deadlocks this change will introduce.

      Time is given according to amount of work, not real time.

      1.8.6 行う予定のない物

      • Nothing; we aim toward full ANSI 92/ANSI 99 compliancy.

      1.9 MySQL と他のオープンソースデータベースの比較

      Our users have successfully run their own benchmarks against a number of Open Source and traditional database servers. We are aware of tests against Oracle server, DB/2 server, Microsoft SQL Server, and other commercial products. Due to legal reasons we are restricted from publishing some of those benchmarks in our reference manual.

      This section includes a comparison with mSQL for historical reasons and with PostgreSQL as it is also an Open Source database. If you have benchmark results that we can publish, please contact us at benchmarks@mysql.com.

      For comparative lists of all supported functions and types as well as measured operational limits of many different database systems, see the crash-me web page at http://www.mysql.com/information/crash-me.php.

      1.9.1 How MySQL Compares to mSQL

      Performance
      真の速度比較のためは、増加する MySQL ベンチマークスイートを見て下さい 「5.1.4 The MySQL Benchmark Suite」節参照. Because there is no thread creation overhead, a small parser, few features, and simple security, mSQL should be quicker at:
      • Tests that perform repeated connects and disconnects, running a very simple query during each connection.
      • INSERT operations into very simple tables with few columns and keys.
      • CREATE TABLE and DROP TABLE.
      • SELECT on something that isn't an index. (A table scan is very easy.)
      これらのオペレーションはとても単純なので、開始のオーバーヘッドが高くなる ときにそれらを良くするのは難しいです。接続が確立された後は MySQL はとても良い性能になります。 MySQL Server は mSQL や多くの他の SQL 実装よりとても速いです:
      • Complex SELECT operations.
      • 大きな結果を検索する場合。(MySQL はより良く, より速くそしてより安全 なプロトコルを持ちます)
      • 可変長文字列を持つテーブル。MySQL はさらに効率的な処理を持ち、 VARCHAR 上にインデックスを持つことができます。
      • Handling tables with many columns.
      • Handling tables with large record lengths.
      • SELECT with many expressions.
      • SELECT on large tables.
      • 同時に多くの接続を処理します。MySQL は完全なマルチスレッドです。 各接続はそれ自身のスレッドを持ちます。これは、それらが他を待つ必要がない ことを意味します(同じテーブルを変更するクエリが実行される場合を除く)。 mSQL では、全ての他の接続は、最初のもの - クエリが長いか短いかに 関わらず - が実行され、終わるまで待つ必要があります。その後次の接続が与 えられ、他の全ては再び待ちます。
      • Joins. mSQL can become pathologically slow if you change the order of tables in a SELECT. In the benchmark suite, a time more than 15,000 times slower than MySQL Server was seen. This is due to mSQL's lack of a join optimiser to order tables in the optimal order. However, if you put the tables in exactly the right order in mSQL2 and the WHERE is simple and uses index columns, the join will be relatively fast! 「5.1.4 The MySQL Benchmark Suite」節参照.
      • ORDER BY and GROUP BY.
      • DISTINCT.
      • TEXT または BLOB フィールドの使用。
      SQL Features
      • GROUP BY and HAVING. mSQL does not support GROUP BY at all. MySQL Server supports a full GROUP BY with both HAVING and the following functions: COUNT(), AVG(), MIN(), MAX(), SUM(), and STD(). COUNT(*) is optimised to return very quickly if the SELECT retrieves from one table, no other columns are retrieved, and there is no WHERE clause. MIN() and MAX() may take string arguments.
      • INSERT and UPDATE with calculations. MySQL Server can do calculations in an INSERT or UPDATE. For example: 
        mysql> UPDATE SET x=x*10+y WHERE x<20;
      • Aliasing. MySQL Server has column aliasing.
      • Qualifying column names. In MySQL Server, if a column name is unique among the tables used in a query, you do not have to use the full qualifier.
      • SELECT with functions. MySQL Server has many functions (too many to list here; see 「6.3 SELECT と WHERE 節で使用する関数」節).
      Disk Space Efficiency
      これは、テーブルをどのように小さくできるかです。 MySQL はとても精密な型を持ちます。とても小さい領域を使用するテーブルを作成でき るためです。MySQL データ型の有用な例は、3バイト長の MEDIUMINT です。10,000,000 レコードを持つ場合、1レコードあたり1バイトの節約でもと ても重要です。 mSQL2 は4つの型(char,text,int,real)しかないので、小さなテーブルを 得るのは難しいです。
      Stability
      これを客観的に判断するのは難しいです。MySQL の安定性については 「1.2.3 MySQL はどれくらい安定か？」節 を参照してください。 私たちには mSQL 安定性の経験がありません。そのため、私たちはこれにつ いては何も言えません。
      Price
      もう一つの重要な問題はもちろんライセンスです。MySQL は mSQL よりも柔軟なライセンスを持っています。そして mSQL よ りもより安いです。少なくとも、あなたが使用を選択した製品全てに、ライセン スまたは email サポートへの支払いを考慮することを覚えていて下さい。 MySQL を含めた製品を売る場合、もちろんこのライセンスの獲得が要求 されます。
      Perl Interfaces
      MySQL は基本的に mSQL と同じ perl インタフェースと、いくつかの追 加機能を持ちます。
      JDBC (Java)
      MySQL Server currently has a lot of different JDBC drivers:
      • MySQL Connector/J is a native Java driver. Version 3.x is released under dual licensing (GPL and commercial).
      • The Resin driver: this is a commercial JDBC driver released under open source. http://www.caucho.com/projects/jdbc-mysql/index.xtp
      • The gwe driver: a Java interface by GWE technologies (not supported anymore).
      • The jms driver: an improved gwe driver by Xiaokun Kelvin ZHU X.Zhu@brad.ac.uk (not supported anymore).
      • The twz driver: a type 4 JDBC driver by Terrence W. Zellers zellert@voicenet.com. This is commercial but is free for private and educational use (not supported anymore).
      The recommended driver is the mm driver. The Resin driver may also be good (at least the benchmarks look good), but we haven't received that much information about this yet. We know that mSQL has a JDBC driver, but we have too little experience with it to compare.
      開発の速度
      MySQL はとても小さい開発チームを持っていますが、私たちは C と C++ のコーディ ングをとても速く行います。スレッド、関数、 GROUP BY などはまだ mSQL には実装されていませんので、追いつくにはたくさんのことをしなければなりません。 この上でいくつかの見通しを得るために、去年の mSQL `HISTORY' ファ イルを見て、MySQL Reference Manual News 節と比較できます( 「D MySQL Change History」節)。 速く開発された多くのものが、かなり明白になります。
      ユーティリティプログラム
      mSQL と MySQL は多くの興味深いサードパーティツールを持っ ています。上位への移行 (mSQL -> MySQL) はとても簡単です。 MySQL は、ほとんど全ての興味深い mSQL アプリケーションを 持っています。 MySQL には、簡単な msql2mysql プログラムが用意されています。 これは、mSQL と MySQL の C API 関数のスペルの違いを修正するプログラムです。 たとえば、mysqlConnect()のインスタンスを変えるには、 mysql_connect(). mSQL から MySQL への変換は通常、数分使用するだけです。

      1.9.1.1 How to Convert mSQL Tools for MySQL

      According to our experience, it doesn't take long to convert tools such as msql-tcl and msqljava that use the mSQL C API so that they work with the MySQL C API.

      The conversion procedure is:

      1. シェルスクリプト msql2mysql をソースに実行します。バイナリプログラム replace が必要です。これは MySQL で配布されます。
      2. コンパイル。
      3. 全てのコンパイラエラーを修復します。

      MySQL と mSQL 間の C API の違い:

      • MySQL は MYSQL 構造体を接続型として使用します (mSQL は int を使用します)。
      • mysql_connect() は MYSQL 構造体へのポインタをパラメータとして使用します。そ れをグローバルに定義したり、その獲得に malloc() を使用するのは簡単です。 mysql_connect() ユーザ飛ばすワードを識別する二つのパラメータを取ります。 デフォルトで使うときにはNULL, NULLを指定します。
      • mysql_error() は MYSQL 構造体をパラメータとして使用します。古いコードを移 行する場合、あなたの古い msql_error() コードへパラメータを追加してください。
      • MySQLは全てのエラーについて、エラー番号とテキストのエラーメッセージを返します。 mSQLはテキストのエラーメッセージしか返しません。
      • Some incompatibilities exist as a result of MySQL supporting multiple connections to the server from the same process.

      1.9.1.2 How mSQL and MySQL Client/Server Communications Protocols Differ

      There are enough differences that it is impossible (or at least not easy) to support both.

      The most significant ways in which the MySQL protocol differs from the mSQL protocol are listed here:

      • メッセージバッファは多くの結果行を含めます。
      • クエリや結果が現在のバッファよりも大きい場合、サーバとクライアントの 制限(設定可能)まで、メッセージバッファは動的に増大されます。
      • 全てのパケットは、パケットの重複や見失いを見つけ出すために、番号づけさ れています。
      • 全ての項目は ASCII で送られ、項目の行と長さはパックされたバイナリコーディン グ(1, 2 または 3 バイト)で送られます。
      • MySQL はバッファされない結果で読み込み可能です(クライアント内に完全なセッ トを格納する必要がありません)。
      • 一つの書き込み/読み込みが 30 秒以上かかると、サーバは接続をクローズしま す。
      • 接続で 8 時間何も起きないと、サーバは接続をクローズします。

      1.9.1.3 How mSQL 2.0 SQL Syntax Differs from MySQL

      Column types

      MySQL Server
      Has the following additional types (among others; 「6.5.3 CREATE TABLE 構文」節):
      • ENUM type for one of a set of strings.
      • SET type for many of a set of strings.
      • BIGINT type for 64-bit integers.
      MySQL Server also supports the following additional type attributes:
      • UNSIGNED option for integer and floating-point columns.
      • ZEROFILL option for integer columns.
      • AUTO_INCREMENT option for integer columns that are a PRIMARY KEY. 「8.4.3.130 mysql_insert_id()」節参照.
      • DEFAULT value for all columns.
      mSQL2
      mSQL column types correspond to the MySQL types shown in the following table:
      mSQL type Corresponding MySQL type
      CHAR(len) CHAR(len)
      TEXT(len) TEXT(len). len is the maximal length. And LIKE works.
      INT INT. With many more options!
      REAL REAL. Or FLOAT. Both 4- and 8-byte versions are available.
      UINT INT UNSIGNED
      DATE DATE. Uses ANSI SQL format rather than mSQL's own format.
      TIME TIME
      MONEY DECIMAL(12,2). A fixed-point value with two decimals.

      Index Creation

      MySQL Server
      Indexes may be specified at table creation time with the CREATE TABLE statement.
      mSQL
      Indexes must be created after the table has been created, with separate CREATE INDEX statements.

      To Insert a Unique Identifier into a Table

      MySQL Server
      Use AUTO_INCREMENT as a column type specifier. 「8.4.3.130 mysql_insert_id()」節参照.
      mSQL
      Create a SEQUENCE on a table and select the _seq column.

      To Obtain a Unique Identifier for a Row

      MySQL Server
      Add a PRIMARY KEY or UNIQUE key to the table and use this. New in Version 3.23.11: If the PRIMARY or UNIQUE key consists of only one column and this is of type integer, one can also refer to it as _rowid.
      mSQL
      Use the _rowid column. Observe that _rowid may change over time depending on many factors.

      To Get the Time a Column Was Last Modified

      MySQL Server
      Add a TIMESTAMP column to the table. This column is automatically set to the current date and time for INSERT or UPDATE statements if you don't give the column a value or if you give it a NULL value.
      mSQL
      Use the _timestamp column.

      NULL Value Comparisons

      MySQL Server
      MySQL Server follows ANSI SQL, and a comparison with NULL is always NULL.
      mSQL
      In mSQL, NULL = NULL is TRUE. You must change =NULL to IS NULL and <>NULL to IS NOT NULL when porting old code from mSQL to MySQL Server.

      String Comparisons

      MySQL Server
      Normally, string comparisons are performed in case-independent fashion with the sort order determined by the current character set (ISO-8859-1 Latin1 by default). If you don't like this, declare your columns with the BINARY attribute, which causes comparisons to be done according to the ASCII order used on the MySQL server host.
      mSQL
      All string comparisons are performed in case-sensitive fashion with sorting in ASCII order.

      Case-insensitive Searching

      MySQL Server
      LIKE is a case-insensitive or case-sensitive operator, depending on the columns involved. If possible, MySQL uses indexes if the LIKE argument doesn't start with a wildcard character.
      mSQL
      Use CLIKE.

      Handling of Trailing Spaces

      MySQL Server
      Strips all spaces at the end of CHAR and VARCHAR columns. Use a TEXT column if this behaviour is not desired.
      mSQL
      Retains trailing space.

      WHERE Clauses

      MySQL Server
      MySQL correctly prioritises everything (AND is evaluated before OR). To get mSQL behaviour in MySQL Server, use parentheses (as shown in an example later in this section).
      mSQL
      Evaluates everything from left to right. This means that some logical calculations with more than three arguments cannot be expressed in any way. It also means you must change some queries when you upgrade to MySQL Server. You do this easily by adding parentheses. Suppose you have the following mSQL query: 
      mysql> SELECT * FROM table WHERE a=1 AND b=2 OR a=3 AND b=4;
      To make MySQL Server evaluate this the way that mSQL would, you must add parentheses: 
      mysql> SELECT * FROM table WHERE (a=1 AND (b=2 OR (a=3 AND (b=4))));

      Access Control

      MySQL Server
      Has tables to store grant (permission) options per user, host, and database. 「4.2.6 特権システムはどのように動くか？」節参照.
      mSQL
      Has a file `mSQL.acl' in which you can grant read/write privileges for users.

      1.9.2 How MySQL Compares to PostgreSQL

      When reading the following, please note that both products are continually evolving. We at MySQL AB and the PostgreSQL developers are both working on making our respective databases as good as possible, so we are both a serious alternative to any commercial database.

      The following comparison is made by us at MySQL AB. We have tried to be as accurate and fair as possible, but although we know MySQL Server thoroughly, we don't have a full knowledge of all PostgreSQL features, so we may have got some things wrong. We will, however, correct these when they come to our attention.

      We would first like to note that PostgreSQL and MySQL Server are both widely used products, but with different design goals, even if we are both striving toward ANSI SQL compliancy. This means that for some applications MySQL Server is more suited, while for others PostgreSQL is more suited. When choosing which database to use, you should first check if the database's feature set satisfies your application. If you need raw speed, MySQL Server is probably your best choice. If you need some of the extra features that only PostgreSQL can offer, you should use PostgreSQL.

      1.9.2.1 MySQL and PostgreSQL development strategies

      When adding things to MySQL Server we take pride to do an optimal, definite solution. The code should be so good that we shouldn't have any need to change it in the foreseeable future. We also do not like to sacrifice speed for features but instead will do our utmost to find a solution that will give maximal throughput. This means that development will take a little longer, but the end result will be well worth this. This kind of development is only possible because all server code are checked by one of a few (currently two) persons before it's included in the MySQL server.

      We at MySQL AB believe in frequent releases to be able to push out new features quickly to our users. Because of this we do a new small release about every three weeks, and a major branch every year. All releases are thoroughly tested with our testing tools on a lot of different platforms.

      PostgreSQL is based on a kernel with lots of contributors. In this setup it makes sense to prioritise adding a lot of new features, instead of implementing them optimally, because one can always optimise things later if there arises a need for this.

      Another big difference between MySQL Server and PostgreSQL is that nearly all of the code in the MySQL server is coded by developers that are employed by MySQL AB and are still working on the server code. The exceptions are the transaction engines and the regexp library.

      This is in sharp contrast to the PostgreSQL code, the majority of which is coded by a big group of people with different backgrounds. It was only recently that the PostgreSQL developers announced that their current developer group had finally had time to take a look at all the code in the current PostgreSQL release.

      Both of the aforementioned development methods have their own merits and drawbacks. We here at MySQL AB think, of course, that our model is better because our model gives better code consistency, more optimal and reusable code, and in our opinion, fewer bugs. Because we are the authors of the MySQL server code, we are better able to coordinate new features and releases.

      1.9.2.2 Featurewise Comparison of MySQL and PostgreSQL

      On the crash-me page (http://www.mysql.com/information/crash-me.php) you can find a list of those database constructs and limits that one can detect automatically with a program. Note, however, that a lot of the numerical limits may be changed with startup options for their respective databases. This web page is, however, extremely useful when you want to ensure that your applications work with many different databases or when you want to convert your application from one database to another.

      MySQL Server offers the following advantages over PostgreSQL:

      • MySQL Server is generally much faster than PostgreSQL. MySQL 4.0.1 also has a query cache that can boost up the query speed for mostly-read-only sites many times.
      • MySQL has a much larger user base than PostgreSQL. Therefore, the code is tested more and has historically proven more stable than PostgreSQL. MySQL Server is used more in production environments than PostgreSQL, mostly thanks to the fact that MySQL AB, formerly TCX DataKonsult AB, has provided top-quality commercial support for MySQL Server from the day it was released, whereas until recently PostgreSQL was unsupported.
      • MySQL Server works better on Windows than PostgreSQL does. MySQL Server runs as a native Windows application (a service on NT/2000/XP), while PostgreSQL is run under the Cygwin emulation. We have heard that PostgreSQL is not yet that stable on Windows but we haven't been able to verify this ourselves.
      • MySQL has more APIs to other languages and is supported by more existing programs than PostgreSQL. 「B Contributed Programs」節参照.
      • MySQL Server works on 24/7 heavy-duty systems. In most circumstances you never have to run any cleanups on MySQL Server. PostgreSQL doesn't yet support 24/7 systems because you have to run VACUUM once in a while to reclaim space from UPDATE and DELETE commands and to perform statistics analyses that are critical to get good performance with PostgreSQL. VACUUM is also needed after adding a lot of new rows to a table. On a busy system with lots of changes, VACUUM must be run very frequently, in the worst cases even many times a day. During the VACUUM run, which may take hours if the database is big, the database is, from a production standpoint, practically dead. Please note: in PostgreSQL version 7.2, basic vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new VACUUM FULL command does old-style vacuum by locking the table and shrinking the on-disk copy of the table.
      • MySQL replication has been thoroughly tested, and is used by sites like:
      • Included in the MySQL distribution are two different testing suites, `mysql-test-run' and crash-me (http://www.mysql.com/information/crash-me.php), as well as a benchmark suite. The test system is actively updated with code to test each new feature and almost all reproduceable bugs that have come to our attention. We test MySQL Server with these on a lot of platforms before every release. These tests are more sophisticated than anything we have seen from PostgreSQL, and they ensure that the MySQL Server is kept to a high standard.
      • There are far more books in print about MySQL Server than about PostgreSQL. O'Reilly, SAMS, Que, and New Riders are all major publishers with books about MySQL. All MySQL features are also documented in the MySQL online manual because when a new feature is implemented, the MySQL developers are required to document it before it's included in the source.
      • MySQL Server supports more of the standard ODBC functions than PostgreSQL.
      • MySQL Server has a much more sophisticated ALTER TABLE.
      • MySQL Server has support for tables without transactions for applications that need all the speed they can get. The tables may be memory-based, HEAP tables or disk based MyISAM. 「7 MySQL テーブル型」節参照.
      • MySQL Server has support for two different storage engines that support transactions, InnoDB, and BerkeleyDB. Because every transaction engine performs differently under different conditions, this gives the application writer more options to find an optimal solution for his or her setup, if need be per individual table. 「7 MySQL テーブル型」節参照.
      • MERGE tables gives you a unique way to instantly make a view over a set of identical tables and use these as one. This is perfect for systems where you have log files that you order, for example, by month. 「7.2 MERGE Tables (3.23.25以上)」節参照.
      • The option to compress read-only tables, but still have direct access to the rows in the table, gives you better performance by minimising disk reads. This is very useful when you are archiving things. 「4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ」節参照.
      • MySQL Server has internal support for full-text search. 「6.8 MySQL Full-text Search」節参照.
      • You can access many databases from the same connection (depending, of course, on your privileges).
      • MySQL Server is coded from the start to be multi-threaded, while PostgreSQL uses processes. Context switching and access to common storage areas is much faster between threads than between separate processes. This gives MySQL Server a big speed advantage in multi-user applications and also makes it easier for MySQL Server to take full advantage of symmetric multiprocessor (SMP) systems.
      • MySQL Server has a much more sophisticated privilege system than PostgreSQL. While PostgreSQL only supports INSERT, SELECT, and UPDATE/DELETE grants per user on a database or a table, MySQL Server allows you to define a full set of different privileges on the database, table, and column level. MySQL Server also allows you to specify the privilege on host and user combinations. 「4.3.1 GRANT と REVOKE 構文」節参照.
      • MySQL Server supports a compressed client/server protocol which improves performance over slow links.
      • MySQL Server employs a ``storage engine'' concept, and is the only relational database we know of built around this concept. This allows different low-level table types to be called from the SQL engine, and each table type can be optimised for different performance characteristics.
      • All MySQL table types (except InnoDB) are implemented as files (one table per file), which makes it really easy to back up, move, delete, and even symlink databases and tables, even when the server is down.
      • Tools to repair and optimise MyISAM tables (the most common MySQL table type). A repair tool is only needed when a physical corruption of a datafile happens, usually from a hardware failure. It allows a majority of the data to be recovered.
      • Upgrading MySQL Server is painless. When you are upgrading MySQL Server, you don't need to dump/restore your data, as you have to do with most PostgreSQL upgrades.

      Drawbacks with MySQL Server compared to PostgreSQL:

      • The transaction support in MySQL Server is not yet as well tested as PostgreSQL's system.
      • Because MySQL Server uses threads, which are not yet flawless on many OSes, one must either use binaries from http://www.mysql.com/downloads/, or carefully follow our instructions in 「2.3 MySQL ソースディストリビューションのインストール」節 to get an optimal binary that works in all cases.
      • Table locking, as used by the non-transactional MyISAM tables, is in many cases faster than page locks, row locks, or versioning. The drawback, however, is that if one doesn't take into account how table locks work, a single long-running query can block a table for updates for a long time. This can usually be avoided when designing the application. If not, one can always switch the trouble table to use one of the transactional table types. 「5.3.2 テーブル・ロッキングの問題」節参照.
      • With UDF (user-defined functions) one can extend MySQL Server with both normal SQL functions and aggregates, but this is not yet as easy or as flexible as in PostgreSQL. 「9.2 MySQL への新しい関数の追加」節参照.
      • Updates that run over multiple tables used to be harder to do in MySQL Server. However, this has been fixed in MySQL Server 4.0.2 with multi-table UPDATE and in MySQL Server 4.1 with subqueries. In MySQL Server 4.0 one can use multi-table deletes to delete from many tables at the same time. 「6.4.6 DELETE 構文」節参照.

      PostgreSQL currently offers the following advantages over MySQL Server:

      Note that because we know the MySQL road map, we have included in the following table the version when MySQL Server should support this feature. Unfortunately we couldn't do this for previous comparisons, because we don't know the PostgreSQL roadmap.

      Feature MySQL version
      Subqueries 4.1
      Foreign keys 5.0 (3.23 with InnoDB)
      Views 5.0
      Stored procedures 5.0
      Triggers 5.0
      Unions 4.0
      Full join 4.1
      Constraints 4.1 or 5.0
      Cursors 4.1 or 5.0
      R-trees 4.1 (for MyISAM tables)
      Inherited tables Not planned
      Extensible type system Not planned

      Other reasons someone may consider using PostgreSQL:

      • Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
      • One can speed up PostgreSQL by coding things as stored procedures.
      • For geographical data, R-trees make PostgreSQL better than MySQL Server. (note: MySQL version 4.1 has R-trees for MyISAM tables).
      • The PostgreSQL optimiser can do some optimisation that the current MySQL optimiser can't do. Most notable is doing joins when you don't have the proper keys in place and doing a join where you are using different keys combined with OR. The MySQL benchmark suite at http://www.mysql.com/information/benchmarks.html shows you what kind of constructs you should watch out for when using different databases.
      • PostgreSQL has a bigger team of developers that contribute to the server.

      Drawbacks with PostgreSQL compared to MySQL Server:

      • VACUUM makes PostgreSQL hard to use in a 24/7 environment.
      • Only transactional tables.
      • Much slower INSERT, DELETE, and UPDATE.

      For a complete list of drawbacks, you should also examine the first table in this section.

      1.9.2.3 Benchmarking MySQL and PostgreSQL

      The only Open Source benchmark that we know of that can be used to benchmark MySQL Server and PostgreSQL (and other databases) is our own. It can be found at http://www.mysql.com/information/benchmarks.html.

      We have many times asked the PostgreSQL developers and some PostgreSQL users to help us extend this benchmark to make it the definitive benchmark for databases, but unfortunately we haven't gotten any feedback for this.

      We, the MySQL developers, have, because of this, spent a lot of hours to get maximum performance from PostgreSQL for the benchmarks, but because we don't know PostgreSQL intimately, we are sure that there are things that we have missed. We have on the benchmark page documented exactly how we did run the benchmark so that it should be easy for anyone to repeat and verify our results.

      The benchmarks are usually run with and without the --fast option. When run with --fast we are trying to use every trick the server can do to get the code to execute as fast as possible. The idea is that the normal run should show how the server would work in a default setup and the --fast run shows how the server would do if the application developer would use extensions in the server to make his application run faster.

      When running with PostgreSQL and --fast we do a VACUUM after every major table UPDATE and DROP TABLE to make the database in perfect shape for the following SELECTs. The time for VACUUM is measured separately.

      When running with PostgreSQL 7.1.1 we could, however, not run with --fast because during the INSERT test, the postmaster (the PostgreSQL daemon) died and the database was so corrupted that it was impossible to restart postmaster. After this happened twice, we decided to postpone the --fast test until the next PostgreSQL release. The details about the machine we run the benchmark on can be found on the benchmark page.

      Before going to the other benchmarks we know of, we would like to give some background on benchmarks.

      It's very easy to write a test that shows any database to be the best database in the world, by just restricting the test to something the database is very good at and not testing anything that the database is not good at. If one, after doing this, summarises the result as a single figure, things are even easier.

      This would be like us measuring the speed of MySQL Server compared to PostgreSQL by looking at the summary time of the MySQL benchmarks on our web page. Based on this MySQL Server would be more than 40 times faster than PostgreSQL, something that is, of course, not true. We could make things even worse by just taking the test where PostgreSQL performs worst and claim that MySQL Server is more than 2000 times faster than PostgreSQL.

      The case is that MySQL does a lot of optimisations that PostgreSQL doesn't do. This is, of course, also true the other way around. An SQL optimiser is a very complex thing, and a company could spend years just making the optimiser faster and faster.

      When looking at the benchmark results you should look for things that you do in your application and just use these results to decide which database would be best suited for your application. The benchmark results also show things a particular database is not good at and should give you a notion about things to avoid and what you may have to do in other ways.

      We know of two benchmark tests that claim that PostgreSQL performs better than MySQL Server. These both where multi-user tests, a test that we here at MySQL AB haven't had time to write and include in the benchmark suite, mainly because it's a big task to do this in a manner that is fair to all databases.

      One is the benchmark paid for by Great Bridge, the company that for 16 months attempted to build a business based on PostgreSQL but now has ceased operations. This is probably the worst benchmark we have ever seen anyone conduct. This was not only tuned to only test what PostgreSQL is absolutely best at, but it was also totally unfair to every other database involved in the test.

      Note: We know that even some of the main PostgreSQL developers did not like the way Great Bridge conducted the benchmark, so we don't blame the PostgreSQL team for the way the benchmark was done.

      This benchmark has been condemned in a lot of postings and newsgroups, so here we will just briefly repeat some things that were wrong with it.

      • The tests were run with an expensive commercial tool that makes it impossible for an Open Source company like us to verify the benchmarks, or even check how the benchmarks were really done. The tool is not even a true benchmark tool, but an application/setup testing tool. To refer to this as a ``standard'' benchmark tool is to stretch the truth a long way.
      • Great Bridge admitted that they had optimised the PostgreSQL database (with VACUUM before the test) and tuned the startup for the tests, something they hadn't done for any of the other databases involved. They say ``This process optimises indexes and frees up disk space a bit. The optimised indexes boost performance by some margin.'' Our benchmarks clearly indicate that the difference in running a lot of selects on a database with and without VACUUM can easily differ by a factor of 10.
      • The test results were also strange. The AS3AP test documentation mentions that the test does ``selections, simple joins, projections, aggregates, one-tuple updates, and bulk updates.'' PostgreSQL is good at doing SELECTs and JOINs (especially after a VACUUM), but doesn't perform as well on INSERTs or UPDATEs. The benchmarks seem to indicate that only SELECTs were done (or very few updates). This could easily explain the good results for PostgreSQL in this test. The bad results for MySQL will be obvious a bit down in this document.
      • They did run the so-called benchmark from a Windows machine against a Linux machine over ODBC, a setup that no normal database user would ever do when running a heavy multi-user application. This tested more the ODBC driver and the Windows protocol used between the clients than the database itself.
      • When running the database against Oracle and MS-SQL (Great Bridge has indirectly indicated the databases they used in the test), they didn't use the native protocol but instead ODBC. Anyone that has ever used Oracle knows that all real applications use the native interface instead of ODBC. Doing a test through ODBC and claiming that the results had anything to do with using the database in a real-world situation can't be regarded as fair. They should have done two tests with and without ODBC to provide the right facts (after having gotten experts to tune all involved databases, of course).
      • They refer to the TPC-C tests, but they don't mention anywhere that the test they did was not a true TPC-C test and they were not even allowed to call it a TPC-C test. A TPC-C test can only be conducted by the rules approved by the TPC Council (http://www.tpc.org/). Great Bridge didn't do that. By doing this they have both violated the TPC trademark and miscredited their own benchmarks. The rules set by the TPC Council are very strict to ensure that no one can produce false results or make unprovable statements. Apparently Great Bridge wasn't interested in doing this.
      • After the first test, we contacted Great Bridge and mentioned to them some of the obvious mistakes they had done with MySQL Server:
        • Running with a debug version of our ODBC driver
        • Running on a Linux system that wasn't optimised for threads
        • Using an old MySQL version when there was a recommended newer one available
        • Not starting MySQL Server with the right options for heavy multi-user use (the default installation of MySQL Server is tuned for minimal resource use)
        Great Bridge did run a new test, with our optimised ODBC driver and with better startup options for MySQL Server, but refused to either use our updated glibc library or our standard binary (used by 80% of our users), which was statically linked with a fixed glibc library. According to what we know, Great Bridge did nothing to ensure that the other databases were set up correctly to run well in their test environment. We are sure, however, that they didn't contact Oracle or Microsoft to ask for their advice in this matter. ;)
      • The benchmark was paid for by Great Bridge, and they decided to publish only partial, chosen results (instead of publishing it all).

      Tim Perdue, a long-time PostgreSQL fan and a reluctant MySQL user, published a comparison on PHPbuilder (http://www.phpbuilder.com/columns/tim20001112.php3).

      When we became aware of the comparison, we phoned Tim Perdue about this because there were a lot of strange things in his results. For example, he claimed that MySQL Server had a problem with five users in his tests, when we know that there are users with similar machines as his that are using MySQL Server with 2000 simultaneous connections doing 400 queries per second. (In this case the limit was the web bandwidth, not the database.)

      It sounded like he was using a Linux kernel that either had some problems with many threads, such as kernels before 2.4, which had a problem with many threads on multi-CPU machines. We have documented in this manual how to fix this and Tim should be aware of this problem.

      The other possible problem could have been an old glibc library and that Tim didn't use a MySQL binary from our site, which is linked with a corrected glibc library, but had compiled a version of his own. In any of these cases, the symptom would have been exactly what Tim had measured.

      We asked Tim if we could get access to his data so that we could repeat the benchmark and if he could check the MySQL version on the machine to find out what was wrong and he promised to come back to us about this. He has not done that yet.

      Because of this we can't put any trust in this benchmark either. :(

      Over time things also change and the preceding benchmarks are not that relevant anymore. MySQL Server now has a couple of different storage engines with different speed/concurrency tradeoffs. 「7 MySQL テーブル型」節参照. It would be interesting to see how the above tests would run with the different transactional table types in MySQL Server. PostgreSQL has, of course, also got new features since the test was made. As these tests are not publicly available there is no way for us to know how the database would perform in the same tests today.

      Conclusion:

      The only benchmarks that exist today that anyone can download and run against MySQL Server and PostgreSQL are the MySQL benchmarks. We here at MySQL AB believe that Open Source databases should be tested with Open Source tools! This is the only way to ensure that no one does tests that nobody can reproduce and use this to claim that one database is better than another. Without knowing all the facts it's impossible to answer the claims of the tester.

      The thing we find strange is that every test we have seen about PostgreSQL, that is impossible to reproduce, claims that PostgreSQL is better in most cases while our tests, which anyone can reproduce, clearly show otherwise. With this we don't want to say that PostgreSQL isn't good at many things (it is!) or that it isn't faster than MySQL Server under certain conditions. We would just like to see a fair test where PostgreSQL performs very well, so that we could get some friendly competition going!

      For more information about our benchmark suite, see 「5.1.4 The MySQL Benchmark Suite」節.

      We are working on an even better benchmark suite, including multi-user tests, and a better documentation of what the individual tests really do and how to add more tests to the suite.

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_LGPL_license.html0100644000175100001560000006624010021471264016722 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - I GNU Lesser General Public License Go to the first, previous, next, last section, table of contents.

      I GNU Lesser General Public License

      Version 2.1, February 1999 

      Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place -- Suite 330, Boston, MA 02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL.  It also counts
as the successor of the GNU Library Public License, version 2, hence the
version number 2.1.]

      I.1 Preamble

      The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

      This license, the Lesser General Public License, applies to some specially designated software--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

      When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

      To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

      For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

      We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

      To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

      Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

      Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

      When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

      We call this license the Lesser General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

      For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

      In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

      Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

      The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a ``work based on the library'' and a ``work that uses the library''. The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

      I.2 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

      1. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called ``this License''). Each licensee is addressed as ``you''. A ``library'' means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The ``Library'', below, refers to any such software library or work which has been distributed under these terms. A ``work based on the Library'' means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term ``modification''.) ``Source code'' for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.
      2. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
      3. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
        1. The modified work must itself be a software library.
        2. You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.
        3. You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.
        4. If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)
        These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
      4. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
      5. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
      6. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a ``work that uses the Library''. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a ``work that uses the Library'' with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a ``work that uses the library''. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a ``work that uses the Library'' uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether they are linked directly with the Library itself.
      7. As an exception to the Sections above, you may also combine or link a ``work that uses the Library'' with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:
        1. Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable ``work that uses the Library'', as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)
        2. Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at runtime a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.
        3. Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.
        4. If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.
        5. Verify that the user has already received a copy of these materials or that you have already sent this user a copy.
        For an executable, the required form of the ``work that uses the Library'' must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.
      8. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:
        1. Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.
        2. Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
      9. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
      10. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.
      11. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.
      12. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
      13. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
      14. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and ``any later version'', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.
      15. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

        9.6 NO WARRANTY

      16. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
      17. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

      9.7 END OF TERMS AND CONDITIONS

      I.3 How to Apply These Terms to Your New Libraries

      If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License).

      To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the ``copyright'' line and a pointer to where the full notice is found. 

      one line to give the library's name and an idea of what it does.
Copyright (C) year  name of author

This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or (at
your option) any later version.

This library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307,
USA.

      Also add information on how to contact you by electronic and paper mail.

      You should also get your employer (if you work as a programmer) or your school, if any, to sign a ``copyright disclaimer'' for the library, if necessary. Here is a sample; alter the names: 

      Yoyodyne, Inc., hereby disclaims all copyright interest in the library
`Frob' (a library for tweaking knobs) written by James Random Hacker.

signature of Ty Coon, 1 April 1990
Ty Coon, President of Vice

      That's all there is to it!

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_MySQL_Database_Administration.html0100644000175100001560000175303010021471264022261 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 4 データベース管理 Go to the first, previous, next, last section, table of contents.

      4 データベース管理

      4.1 Configuring MySQL

      4.1.1 mysqld コマンド行オプション

      多くの場合、オプションファイルを通じて mysqld オプションを管理すべきです。 「4.1.2 `my.cnf' オプションファイル」節参照.

      mysqld と mysqld.server は mysqld と server グループからオプションを読み込みます。mysqld_safe は mysqld, server, mysqld_safe, safe_mysqld グ ループからオプションを読み込みます。組み込み MySQL サーバは通常 server, embedded, xxxxx_SERVER からオプションを読み 込みます。xxxxx はアプリケーション名です。

      mysqld は次のコマンド行オプションを受け付けます。 完全なリストについては mysqld --help を実行してください。

      --ansi
      MySQL 構文の代わりに ANSI SQL 構文を使用します。 「1.7.2 MySQLをANSIモードで実行する」節参照.
      -b, --basedir=path
      インストール先ディレクトリのパス。すべてのパスは通常ここからの相対パスで決 定されます。
      --big-tables
      ファイルにすべての一時セットを保存することにより、大きな結果セットを許しま す。これは、多くの 'table full' エラーを解決します。しかし、メモリ内テーブ ルでも十分なクエリは遅くなります。バージョン 3.23.2 からは、 MySQL は自動的にメモリを使用し、必要なときにディスクテーブルにス イッチすることによって、これを解決します。
      --bind-address=IP
      bind する IP アドレス。
      --console
      --log-error が指定されていても、エラーログメッセージを stderr/stdout に書き出します。Windows mysqld はこのオプションが使用され た場合はコンソールスクリーンをクローズしません。
      --character-sets-dir=path
      キャラクタ・セット ディレクトリ。 「4.6.1 データとソートに使用されるキャラクター・セット」節参照.
      --chroot=path
      起動時に mysqld デーモンを chroot 下に置きます。 MySQL 4.0 からの推奨されるセキュリティ手法です。 (MySQL 3.23 は 100% クローズな chroot jail を提供できません)。 これは LOAD DATA INFILE と SELECT ... INTO OUTFILE を制限します。
      --core-file
      mysqld が死んだ場合 core ファイルを書き出します。いくつかのシステム では、--core-file-size も safe_mysqld に記述する必要がありま す。 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照. 注意: Solaris のようないくつかのシステムでは、--user オプションも 使用すると core ファイルを得られません。
      -h, --datadir=path
      データベースルートのパス。
      --debug[...]=
      MySQL が --with-debug つきで configure された場合、このオ プション使用して、mysqld が何を行なっているかのトレースファイルを得 ることができます 「E.1.2 Creating Trace Files」節参照.
      --default-character-set=charset
      デフォルト のキャラクタ・セットの設定。 「4.6.1 データとソートに使用されるキャラクター・セット」節参照.
      --default-table-type=type
      テーブルのデフォルトテーブル型を設定する。 「7 MySQL テーブル型」節参照.
      --delay-key-write[= OFF | ON | ALL]
      MyISAM DELAYED KEYS が使用される方法。 「5.5.2 サーバーパラメーターのチューニング」節参照。
      --delay-key-write-for-all-tables; MySQL 4.0.3 では代わりに --delay-key-write=ALL を使用。
      任意の MyISAM テーブルについて書き込み間でキーバッファをフラッシュ しません。 「5.5.2 サーバーパラメーターのチューニング」節参照.
      --des-key-file=filename
      このファイルから DES_ENCRYPT() と DES_DECRYPT() で使用され るデフォルトキーを読み込みます。
      --enable-external-locking (4.0.3 から. それ以前のバージョンでは --enable-locking)
      システムロックを有効にします。注意: lockd() が完全に働かない(Linux のよう な)システムでこのオプションを使用した場合、mysqld が簡単にデッドロックしま す。
      --enable-named-pipe
      名前付きパイプのサポートを有効にします (NT/Win2000/XP のみ)。
      -T, --exit-info
      mysqld サーバをデバッグするために使用できる、様々なフラグのビットマスクで す; 何が行なわれるのか正確に知らない場合は、このオプションを使用すべきでは ありません！
      --flush
      各 SQL コマンド後にすべての変更をディスクにフラッシュします。通常 MySQL は各 SQL コマンドにすべての変更をディスクに書き出すだけで、 OS がディスクへの sync を処理します。 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.
      -?, --help
      短いへルプを表示して終了します。
      --init-file=file
      起動時にファイルから SQL コマンドを読み込みます。
      -L, --language=...
      与えられた言語のクライアントエラーメッセージ。フルパスで与えることもできます。 「4.6.2 Non-English Error Messages」節参照.
      -l, --log[=file]
      接続とクエリをファイルに記録します。 「4.9.2 The General Query Log」節参照.
      --log-bin=[file]
      データを変更するすべてのクエリをファイルに記録します。バックアップとレプ リケーションのために使用されます。 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照。
      --log-bin-index[=file]
      バイナリログファイル名のためのインデックスファイル。 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照。
      --log-error[=file]
      エラーと起動メッセージをこのファイルに記録します。 「4.9.1 The Error Log」節参照。
      --log-isam[=file]
      すべての ISAM/MyISAM 変更をファイルに記録します(ISAM/MyISAM のデバッグ時に のみ使用できます)。
      --log-slow-queries[=file]
      実行に long_query_time 秒以上掛かるすべてのクエリをファイルに記録し ます。 「4.9.5 The Slow Query Log (3.23.28以上)」節参照.
      --log-update[=file]
      更新を file.# に記録します。# は与えられなければ一意な番号で す。 「4.9.3 更新ログ」節参照.
      --log-long-format
      更新ログに拡張情報を記録します。--log-slow-queries を使用すると、イ ンデックスを使用しないクエリが slow query ログに記録されます。
      --low-priority-updates
      テーブル変更操作 (INSERT/DELETE/UPDATE) は SELECT よ りも低い優先度になります。あるクエリだけ優先度を低くするには、 {INSERT | REPLACE | UPDATE | DELETE} LOW_PRIORITY ... によって行 なわれます。また、ひとつのスレッドの優先度を変更するには、 SET LOW_PRIORITY_UPDATES=1 で行なわれます。 「5.3.2 テーブル・ロッキングの問題」節参照.
      --memlock
      メモリに mysqld プロセスをロックします。これはシステムが mlockall() システムコールをサポートしている時(Solaris のように)にだけ動作します。 これは、OS が mysqld をディスク上にスワップさせる問題がある場合の助けに なります。
      --myisam-recover [=option[,option...]]]
      ここで option は DEFAULT か BACKUP か FORCE か QUICK の組み合わせ. 3.23.26以上で有効. このオプションを使用すると、mysqld はオープン時にテーブルがクラッシュ したとマークされているかどうか、テーブルが適切にクローズされていないかどう かチェックします。(最後のオプションは --skip-external-locking (4.0.3より前のバージョンでは --skip-locking) で起動している 場合にだけ働きます)。この場合、mysqld はテーブル上でチェックを実 行します。テーブルが壊れている場合、mysqld はその修復を試みます。 次のオプションは修復の動作に影響します：
      Option Description
      DEFAULT --myisam-recover にオプションを与えないのと同じです。
      BACKUP データテーブルが修復中に変更された場合、 `table_name.MYD' データファイルのバックアップを `table_name-datetime.BAK' に保存します。
      FORCE .MYD ファイルからひとつより多くのレコードが失われている 場合でも修復を実行します。
      QUICK 削除ブロックがない場合にテーブル内のレコードをチェック しません。
      テーブルが自動的に修復される前に、MySQL はエラーログにこれについ てのメモを追加します。ユーザの介入なしで多くのことを修復したい場合は、オプ ション BACKUP,FORCE を使用すべきです。いくつかのレコードが削除され る場合でも、テーブルを強制的に修復しますが、古いデータファイルをバックアッ プとして保存するため、あとで何が起こったか検証できます。
      --pid-file=path
      safe_mysqld によって使用される pid ファイルのパス。
      -P, --port=...
      TCP/IP 接続で listen するポート番号。
      -o, --old-protocol
      とても古いクライアントとの互換のために、3.20 プロトコルを使用します。 「2.5.5 バージョン 3.20 から バージョン 3.21 へのアップグレード」節参照.
      --one-thread
      一つのスレッドだけを使用します(Linux 下でデバックするため)。 「E.1 MySQL server のデバッグ」節参照.
      -O, --set-variable var=option
      変数に値を与えます。--help は変数をリストします。すべての変数の完全 な詳細はこのマニュアルの SHOW VARIABLES 節で見られます。 「4.5.6.4 SHOW VARIABLES」節参照。サーバパラメータの調整についての節はこれらの最適化 方法の情報を含んでいます。 MySQL 4.0 からは --set-variable は推奨されないことに注意してください。 --var=option を使用してください。 「5.5.2 サーバーパラメーターのチューニング」節参照。 MySQL 4.0.2 では、--variable-name=option で直接変数を設定できます。 set-variable はオプションファイル中ではもはや必要ありません。 SET で設定できる起動オプションの最大値を制限したい場合は、 --maximum-variable-name コマンドラインオプションを使用することで 定義できます。 「5.5.6 SET 構文」節参照。 注意: 変数に値を設定する時、MySQL は自動的に与えられた範囲に収まるように 補正し、使用されるアルゴリズム用に合うように値を少し調整します。
      --safe-mode
      いくつかの最適化ステージをスキップします。
      --safe-show-database
      このオプションをつけると、SHOW DATABASES コマンドは、ユーザが何か の権限を持つデータベースだけを返します。 バージョン 4.0.2 からはこのオプションは推奨されず何もしません(デフォルト でこのオプションは有効です)。現在は SHOW DATABASES 権限を持つため です。 「4.3.1 GRANT と REVOKE 構文」節参照。
      --safe-user-create
      これが有効な場合、ユーザが mysql.user テーブルやこのテーブル内の 任意のフィールドについて INSERT 権限を持っていない場合、そのユー ザは GRANT コマンドで新しいユーザを作成できません。
      --skip-bdb
      BDB テーブルの使用を無効にします。これはメモリを節約し、いくつかのことを 高速化します。
      --skip-concurrent-insert
      同時に MyISAM テーブルに select と insert を行なう機能をオフにしま す。(この機能にバグを見つけたと考える場合にだけ使用します)。
      --skip-delay-key-write; MySQL 4.0.3 では代わりに --delay-key-write=OFF を使用
      すべてのテーブルに対し DELAY_KEY_WRITE オプションを無視します。 「5.5.2 サーバーパラメーターのチューニング」節参照.
      --skip-grant-tables
      このオプションは、サーバをすべての権限システムを使用しないようにします。これ は全員にすべてのデータベースへの完全アクセスを与えます！ (mysqladmin flush-privileges や mysqladmin reload を実行する ことで、権限テーブルを使用して起動するように実行中のサーバに伝えることがで きます。)
      --skip-host-cache
      より速いホスト名-IP解決のためのホスト名キャッシュを使用しません。代わりに すべての接続で DNS サーバへクエリします。 「5.5.5 How MySQL uses DNS」節参照.
      --skip-innodb
      Innodb テーブルの使用を無効にします。これはメモリとディスク領域の節約と いくつかのことを高速化します。
      --skip-external-locking (4.0.3から. 4.0.3より前では --skip-locking)
      システムロックを使用しません。isamchk または myisamchk を使 用するためには、サーバをシャットダウンする必要があります。 「1.2.3 MySQL はどれくらい安定か？」節参照。注意: MySQL バージョン 3.23 では、 REPAIR と CHECK を MyISAM テーブルの修復／チェックに 使用できます。
      --skip-name-resolve
      ホスト名を解決しません。権限テーブルのすべての Host フィールド値は IP 番号か localhost でなければなりません。 「5.5.5 How MySQL uses DNS」節参照.
      --skip-networking
      TCP/IP 接続の listen をまったく行ないません。mysqld との接続には Unix ソケット経由で行なう必要があります。このオプションはローカル要求だけ を許可するシステムでは、高く推奨されます。 「5.5.5 How MySQL uses DNS」節参照.
      --skip-new
      Don't use new, possible wrong routines.
      --skip-symlink
      データディレクトリ中のシンボリックリンクファイルが指すファイルを削除、リ ネームしません。
      --skip-safemalloc
      MySQL が --with-debug=full で configure されている場合、す べてのプログラムがすべてのメモリ割り当てとメモリ解放をオーバーラン用にチェッ クします。このチェックはとても遅いので、メモリチェックが不要な場合、このオ プションを使用することでこれを無効にできます。
      --skip-show-database
      SHOW DATABASES 権限を持っていないユーザに SHOW DATABASES コマンドを 許しません。 バージョン 4.0.2 からは、このオプションは必要ありません。現在、アクセス は SHOW DATABASES 権限で特別に与えられるためです。
      --skip-stack-trace
      スタックトレースを書き出しません。このオプションは、mysqld をデバッ ガ下で実行している時に有用です。 いくつかのシステムでは、core ファイルを得るためにこのオプションも使用す る必要があります。 「E.1 MySQL server のデバッグ」節参照。
      --skip-thread-priority
      より速いレスポンスタイム用のスレッド優先度の使用を無効にします。
      --socket=path
      デフォルト /tmp/mysql.sock の代わりに、ローカル接続用に使用されるソ ケットファイル。
      --sql-mode=option[,option[,option...]]
      オプションは次の任意の組合わせです: REAL_AS_FLOAT, PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, SERIALIZE, ONLY_FULL_GROUP_BY。リセットしたい場合は、空 ("") も指定できます。 上記オプションの全てを指定することで、--ansi の使用と同じになります。 このオプションで、必要とされる SQL モードだけを有効にできます。 「1.7.2 MySQLをANSIモードで実行する」節参照。
      --temp-pool
      Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. This is to work around a problem in the Linux kernel dealing with creating a bunch of new files with different names. With the old behaviour, Linux seems to 'leak' memory, as it's being allocated to the directory entry cache instead of the disk cache.
      --transaction-isolation= { READ-UNCOMMITTED | READ-COMMITTED | REPEATABLE-READ | SERIALIZABLE }
      トランザクション分離レベルのデフォルトを設定します。 「6.7.3 SET TRANSACTION 構文」節参照。
      -t, --tmpdir=path
      一時ファイル用のパス。デフォルトの /tmp ディレクトリが一時テーブル を保持するのに小さすぎるパーティション上にある場合に有用です。 MySQL 4.1 からは、このオプションはコロン :(Windows ではセミコロン ;)で区切られたいくつかのパスを受け付けます。これらはラウンドロビ ン方法で使用されます。
      -u, --user= [user_name | userid]
      ユーザ user_name か userid (数値) で mysqld デーモンを実行します。 このオプションは、mysqld を root で起動した時に 強制されます。 Starting from MySQL 3.23.56 and 4.0.12: To avoid a possible security hole where a user adds an --user=root option to some `my.cnf' file, mysqld will only use the first --user option specified and give a warning if there are multiple options. Note that `/etc/my.cnf' and `datadir/my.cnf' may override a command line option - therefore it is recommended to put this option in `/etc/my.cnf'.
      -V, --version
      バージョン情報を出力して終了します
      -W, --log-warnings (4.0.3 より前では --warnings)
      Aborted connection... のような警告を .err ファイルに出力します。 「A.2.9 Communication Errors / Aborted Connection」節参照.

      SET コマンドで実行中のサーバの多くの値を変更できます。 「5.5.6 SET 構文」節参照。

      4.1.2 `my.cnf' オプションファイル

      MySQL バージョン 3.22 のサーバー、クライアントともに、 オプションファイルからデフォルトの起動オプションを読み込むことができます。

      Unix では MySQL は以下のファイルからデフォルトオプションを読みます：

      ファイル名 意味
      /etc/my.cnf グローバルなオプション
      DATADIR/my.cnf サーバ固有オプション
      defaults-extra-file --defaults-extra-file=# で指定されたファイル
      ~/.my.cnf ユーザ固有オプション

      DATADIR は MySQL データディレクトリです (普通 バイナリディストリビューションでは `/usr/local/mysql/data' 、ソースディストリビューションでは `/usr/local/var'). このディレクトリはconfigure時に決定されており、 --datadir を mysqld 起動時に指定しても変更されません。 (サーバーはコマンドラインの引数を処理する前にオプションファイルを探します。 よって、--datadir 引数を指定してもオプションファイルを探す場所を指定することにはなりません。)

      Windows では MySQL は以下のファイルからデフォルトオプションを読みます：

      ファイル名 意味
      windows-system-directory\my.ini グローバルオプション
      C:\my.cnf グローバルオプション

      注意: Windows では \ の代わりに / で全てのパスを記述すべきで す。\ を使用する場合、\ は MySQL のエスケープ文字 なので、これを二重に記述する必要があります。

      MySQL は上記の表にかかれている順にオプションファイルを読みます。 もし複数オプションファイルがあった場合、後から読まれた設定が有効になります。 全てのオプションはコマンドラインの引数に上書きされます。 いくつかのオプションは環境変数に定義できます。 オプションファイルとコマンドラインの引数は環境変数を上書きします。 「F Environment Variables」節参照.

      次のプログラムはオプションファイルをサポートします： mysql, mysqladmin, mysqld, mysqld_safe, mysql.server, mysqldump, mysqlimport, mysqlshow, mysqlcheck, myisamchk, myisampack.

      オプションファイルには、プログラムがサポートしているコマンドラインの long オプション(例えば、-u ではなくて --user の方)を書くことができます。 プログラムを --help で起動すれば、設定可能な変数名が得られます。

      オプションファイルの書式は以下です：

      #comment
      コメントは `#' か `;' 文字で始めます。空の行は無視します。
      [group]
      グループ宣言。 group はオプションを定義するプログラムかグループの名前です。 この宣言の後、オプション か set-variable 行で、このグループにオプションを与えます。 このセクションの範囲は、他のグループ宣言の行が来るか、ファイルの最後に来るまでです。
      option
      これはコマンドラインの --option と等価です。
      option=value
      これはコマンドラインの --option=value と等価です。
      set-variable = variable=value
      これはコマンドラインの --set-variable variable=value と等価です。 これは mysqld 変数で使用される形式です。 MySQL 4.0 からは --set-variable は推奨されないことに注意してくだ さい。--variable=value を使用してください。

      client グループは、全ての MySQL クライアント(mysqldは除)に対してオプションを定義します。 これはサーバーに接続する際に使用するパスワードを指定できるグループです。 (この場合、オプションファイルは自分だけが読み書きできるようにしてください)

      オプションや値の善後にある全てのブランク文字は自動で取り除かれます。 値として、`\b',`\t', `\n', `\r', `\\', `\s' のエスケープシーケンスが使用できます。 (`\s' == blank).

      オプションファイル例： 

      [client]
port=3306
socket=/tmp/mysql.sock

[mysqld]
port=3306
socket=/tmp/mysql.sock
set-variable = key_buffer_size=16M
set-variable = max_allowed_packet=1M

[mysqldump]
quick

      ユーザーオプションファイル例： 

      [client]
# The following password will be sent to all standard MySQL clients
password=my_password

[mysql]
no-auto-rehash
set-variable = connect_timeout=2

[mysqlhotcopy]
interactive-timeout

      もしソース配布を持っているなら、 `my-xxxx.cnf' という名前のサンプルファイルを `support-files' ディレクトリに見ることができます。 もしバイナリ配布を使用しているなら、 `DIR/support-files' ディレクトリを探してください (ここで DIR は MySQL がインストールされたディレクトリのパス名で、 普通は `/usr/local/mysql')。 この `my-xxxx.cnf' ファイルを自分のディレクトリに `.my.cnf' という名前でコピーして使用できます。

      オプションファイルをサポートするすべての MySQL クライアントは次 のオプションをサポートします:

      Option Description
      --no-defaults オプションファイルを読み込まない。
      --print-defaults プログラム名と得られる全てのオプションを出力する。
      --defaults-file=full-path-to-default-file 与えられたコンフィグレーションファイルだけを使用する。
      --defaults-extra-file=full-path-to-default-file グローバルコンフィグレーションファイルの後、ユーザコンフィグレーションファイルの前にこのコンフィグレーションファイルを読み込む。

      注意: 上記のオプションはコマンドラインの先頭になければ働きません！ ただ し、--print-defualts は --defaults-xxx-file コマンドの直後 にも置けます。

      開発者向け情報：　オプションファイルの操作は全てのオプションをコマンドラインの 引数より先に処理するように簡単に埋め込まれています。 これはオプションを最後に処理するプログラムを複数立ちあげる場合に都合よく動きます。 もしオプションファイルを読み込む機能のない古いプログラムを使用しているなら、 たった二行だけ注意して書けばいいだけです。 この動作については MySQL クライアントプログラムのコードを参考にしてください。

      シェルスクリプト内では、`my_print_defaults' コマンドを使用して、コ ンフィグファイルを解析することができます: 

      
shell> my_print_defaults client mysql
--port=3306
--socket=/tmp/mysql.sock
--no-auto-rehash

      上記は、'client' と 'mysql' グループ用の全オプションを出力します。

      4.1.3 同じマシンに多くのサーバをインストールする

      同じマシン上で多くの異なる mysqld デーモン(サーバ)を動作させたい場 合があります。例えば、テスト用に MySQL の新しいバージョンを使用中の 古いバージョンと共に実行したい場合や、異なる mysqld サーバにそれを管理する 異なるユーザアクセスを与えたい場合などです。

      一つの方法は、新しいサーバを次のように異なるソケットとポートで起動すること です: 

      shell> MYSQL_UNIX_PORT=/tmp/mysqld-new.sock
shell> MYSQL_TCP_PORT=3307
shell> export MYSQL_UNIX_PORT MYSQL_TCP_PORT
shell> scripts/mysql_install_db
shell> bin/safe_mysqld &

      The environment variables appendix は mysqld に影響する他の環境変数の 一覧を含んでいます。 「F Environment Variables」節参照.

      The above is the quick and dirty way that one commonly uses for testing. The nice thing with this is that all connections you do in the above shell will automatically be directed to the new running server!

      If you need to do this more permanently, you should create an option file for each server. 「4.1.2 `my.cnf' オプションファイル」節参照. In your startup script that is executed at boot time you should specify for both servers:

      safe_mysqld --defaults-file=path-to-option-file

      少なくとも、次のオプションはサーバごとに異なるようにすべきです:

      • port=#
      • socket=path
      • pid-file=path

      次のオプションが使用される場合、異なるようにすべきです:

      • log=path
      • log-bin=path
      • log-update=path
      • log-isam=path
      • bdb-logdir=path
      • shared-memory-base-name (New in MySQL 4.1)

      さらに性能を求める場合、次も異なるように記述できます:

      • tmpdir=path
      • bdb-tmpdir=path

      「4.1.1 mysqld コマンド行オプション」節参照. Starting from MySQL 4.1, tmpdir can be set to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion. This feature can be used to spread load between several physical disks.

      バイナリの MySQL バージョン (.tar ファイル) をインストールして、 ./bin/safe_mysqld で起動する場合、多くの場合では、追加/変更する必要 のあるオプションは safe_mysqld への socket と port 引 数だけです。

      「4.1.4 同一マシン上に複数の MySQL サーバーを走らせる」節参照.

      4.1.4 同一マシン上に複数の MySQL サーバーを走らせる

      同じマシン上で複数のサーバーを走らせたい場合があります。 例えば、すでに存在しているサーバーはそのままにしておいて、新しい MySQL をテストしたい場合や、 あるいは、インターネットプロバイダーを営んでいて、MySQL をそれぞれの顧客用に提供したい場合など。

      複数のサーバーをたちあげる場合、簡単な方法として、 TCP/IP ポート、ソケットファイルを変えて、サーバーをコンパイルする方法があります。 「4.7.3 mysqld_multi, 複数の MySQL サーバーを管理するプログラム」節参照.

      そでに走っているサーバーがデフォルトのポート番号とソケットファイルで動作しているとします。 新しくサーバーを作るには、以下のように configure します： 

      shell> ./configure  --with-tcp-port=port_number \
             --with-unix-socket-path=file_name \
             --prefix=/usr/local/mysql-3.22.9

      port_number と file_name には、デフォルトのポート番号、 ソケットファイルとは違うものを指定します。 そして --prefix を、すでに走っている MySQL の インストール先とは違うディレクトリーに指定します。

      現在走っている MySQL サーバーが使用している ソケットとポートをチェックするには、以下のようにします： 

      shell> mysqladmin -h hostname --port=port_number variables

      Note that if you specify ``localhost'' as a hostname, mysqladmin will default to using Unix sockets instead of TCP/IP.

      In MySQL 4.1 you can also specify the protocol to use by using the --protocol=(TCP | SOCKET | PIPE | MEMORY) option.

      あなたが使用しているポートに MySQL サーバーが走っていれば、 これは変更可能な MySQL 変数を(ソケットファイルの名前も含んで)出力します。

      この場合、MySQL サーバーを再コンパイルする必要はありません。 safe_mysqld のオプションを指定してサーバーを起動すれば、 ポートとソケットを変更できます： 

      shell> /path/to/safe_mysqld --socket=file_name --port=port_number

      mysqld_multi can also take safe_mysqld (or mysqld) as an argument and pass the options from a configuration file to safe_mysqld and further to mysqld.

      もし、他のサーバーがロギングを行っているディレクトリと同じデータベースディレクトリを、 新しいサーバーで使用するのであれば、ログファイルの名前を指定すべきです。 ( safe_mysqld に --log , --log-update , --log-slow-queries を指定する) そうしないと、両方のサーバーが同じログファイルに書き込もうとするからです。

      Warning: 通常、二つサーバーに同じデータベースを操作させてはいけません！ もし使用している OS が fault-free system locking をサポートしていないと、 これは悲惨なことになるでしょう！

      もし二つ目のサーバーに違うデータベースディレクトリを使用させたい場合、 safe_mysqld に --datadir=path オプションを指定します。

      Note also that starting several MySQL servers (mysqlds) in different machines and letting them access one data directory over NFS is generally a bad idea! The problem is that the NFS will become the bottleneck with the speed. It is not meant for such use. And last but not least, you would still have to come up with a solution how to make sure that two or more mysqlds are not interfering with each other. At the moment there is no platform that would 100% reliable do the file locking (lockd daemon usually) in every situation. Yet there would be one more possible risk with NFS; it would make the work even more complicated for lockd daemon to handle. So make it easy for your self and forget about the idea. The working solution is to have one computer with an operating system that efficiently handles threads and have several CPUs in it.

      もし違うポートで走っている MySQL サーバーに、 これまた違うポートを使用するように作られたクライアントから接続したい場合、 以下のようにします：

      • クライアントを TCP/IP での接続 --host 'hostname' --port=port_numer か Unix ソケット経由での接続 [--host localhost] --socket=file_name オプションで起動します。
      • Start the client with --protocol=tcp to connect with TCP/IP and --protocol=socket to connect via a Unix socket.
      • C あるいは Perl プログラムの場合、MySQL サーバーのポートとソケットを与えることができます。
      • If your are using the Perl DBD::mysql module you can read the options from the MySQL option files. 「4.1.2 `my.cnf' オプションファイル」節参照. 
        $dsn = "DBI:mysql:test;mysql_read_default_group=client;
        mysql_read_default_file=/usr/local/mysql/data/my.cnf"
$dbh = DBI->connect($dsn, $user, $password);
      • MYSQL_UNIX_PORT と MYSQL_TCP_PORT 環境変数に Unix ソケットファイルと TCP/IP のポート番号とセットし、クライアントを立ちあげます。 もし、このポート番号やソケットファイルを常に使用するのであれば、 `.login' ファイルかなにかに環境変数をセットするように書いておけばよいでしょう。 「F Environment Variables」節参照.
      • あなたのホームディレクトリの `.my.cnf' ファイルに、 通常使用するポート番号とソケットファイルを書くこともできます。 「4.1.2 `my.cnf' オプションファイル」節参照.

      4.2 General Security Issues and the MySQL Access Privilege System

      MySQL has an advanced but non-standard security/privilege system. This section describes how it works.

      4.2.1 General Security Guidelines

      よくあるセキュリティの間違いを避けるために、インターネットに接続されたコン ピュータ上で MySQL を使用する誰もが、このセクションを読むべきです。

      ``セキュリティ'' の議論において、我々は、すべての該当するアタックタイプ (eavesdropping, altering, playback, Denial of Service) に対して、すべてのサー バホスト(MySQL サーバだけではなく)の完全な保護の必要性を強調しま す。We do not cover all aspects of availability and fault tolerance here.

      MySQL は、ユーザが実行しようとするすべての接続、クエリ、その他の オペレーションに対して、アクセス制御リスト(ACLs: Access Control Lists)セキュ リティを使用します。MySQL クライアントとサーバの間で SSL 暗号化接 続のサポートもいくつかあります。ここで議論されるコンセプトの多くは、 MySQL に特有のものではありません; 同じ一般的なアイデアはほとんど すべてのアプリケーションに適用します。

      MySQL 実行時、可能な限りいつでもこれらのガイドラインに従ってくだ さい:

      • (mysql root ユーザ以外の)誰にも mysql データベース内の user テーブルへのアクセスを与えないでください！ 暗号化されたパスワー ドは MySQL の本当のパスワードです。もしあなたが与えられたユーザに ついて user テーブルにリストされたパスワードを知ることができれば、 そのアカウントについてリストされたホストへアクセスすれば、あなたは簡単にそ のユーザとしてログインできます。
      • MySQL access privilege system の理解に努めるべきです。 GRANT と REVOKE コマンドは MySQL へのアクセスを制限するための物です。 必要以上の権限を誰にも与えないでください。 全てのホストに対して、何か出来るような許可を与えてはいけません。 Checklist:
        • mysql -u root を行ってみます。 パスワードを尋ねられること無しにサーバへの接続ができる場合、問題があります。 どのユーザでも(root でなくても)、MySQL サーバに完全な権限で接続で きます！ root パスワードの設定についての項目に特別な注意を払って MySQL インストール説明を見直してください。
        • SHOW GRANTS を使用し、だれがなんのアクセスを持つかチェックします。 必要ない権限を、REVOKE コマンドを使用して削除してください。
      • いかなる平文パスワードもデータベースに保存しないようにします。 あなたのコンピュータが妥協される時、新入者はパスワードの完全なリストを得て、 それらを使用できます。代わりに MD5(), SHA1() や 他の one-way hashing 関数を使用してください。 (SHA1()はバージョン4.0.2から。MD5()はバージョン3.23.2から。)
      • 辞書からパスワードを選んではいけません。 それらを破る プログラムがあるのです。 ``xfish98'' のようなパスワードは悪い例です。 これよりは ``duag98'' の方がよいでしょう。 これは "fish" を打つ際に、 キーを一つずつずらしたものです。 他の方法としては、 "Mhall" 、これは "Mary had a little lamb" という文の頭文字を羅列したものです。 これを知っている物には打ちやすいパスワードですが、知らない者にとっては、 類推することが難しいパスワードです。
      • ファイアーウォールを導入します。This protects you from at least 50% of all types of exploits in any software. MySQL をファイアーウォール で守られた方に置くか、DMZ (緩衝地帯, 非武装地帯) に置きます。 Checklist:
        • インターネットから nmap のようなツールを使用して、 あなたのマシンのポートをスキャンしてみます。 MySQL はデフォルトで 3306 番を使用しています。 このポートには信用できないホストからはアクセスできないようにすべきです。 MySQL ポートがオープンしているかどうかをチェックする他の簡単な方 法は、次のコマンドをいくつかのリモートマシンから試すことです。ここで server_host はあなたの MySQL サーバのホスト名です: 
          shell> telnet server_host 3306
          接続し、いくつかのゴミ文字が得られた場合、ポートはオープンして います。それをオープンしておく正当な理由が本当にない限り、ファイアーウォー ルやルータでクローズすべきです。telnet がハングしたり拒否されたり する場合、すべて OK です。ポートはブロックされています。
      • ユーザーから入力されたデータは信頼しないで下さい。 ユーザーは、Webのフォーム、URL、あるいはあなたのカスタムプログラムから 特定の文字を入れることが可能です。 もしユーザーがフォームに ; DROP ALL DATABASES ; のような文字を入力しても、 あなたのアプリケーションは安全ですか？ これは極端な例ですが、それらに対して準備しない場合、似たようなテクニックを 使用するハッカーの結果として、大きなセキュリティリークとデータ喪失が発生し 得ます。 数値データのチェックも忘れないでください。よくある間違いは文字列しか保護し ないことです。時々、人はデータベースが保護される必要のない公に有効なデータ だけを含んでいるかどうかを考えます。これは間違いです。少なくとも、 denial-of-service タイプのアタックはそのようなデータベースでも実行されます。 このタイプのアタックから保護するもっとも簡単な方法は、数値定数の回りにアポ ストロフィを使用することです: SELECT * FROM table WHERE ID=234 の代 わりに SELECT * FROM table WHERE ID='234'。 MySQL は自動的 にこの文字列を数値に変換し、そこからすべての非数値シンボルを取り除きます。 Checklist:
        • すべての Web アプリケーション:
          • あなたの WWW の全てのフォームに、`'' と `"' を入力することを試みてください。 もしなんらかの MySQL エラーがでたら、あなたのサイトを停止したほうが よいでしょう。
          • あなたの URL に %22 (`"'), %23 (`#') , %27 (`'') をつけてみて、動的URLを いろいろ変更して試してみてください。
          • 動的 URL のデータタイプを数値から上述の例の文字を含む文字列に修正してみて ください。アプリケーションはこれと似たようなアタックに対して安全であるべき です。
          • 数値フィールドに対して、文字、スペース、特殊文字の入力を試みてください。 アプリケーションは、それらを MySQL に送る前に取り除くか、 あるいはエラーを出すべきです。 検査しない値を MySQL に送ることは危険です。
          • MySQL にデータを送る前に、そのサイズをチェックします。
          • あなたのアプリケーションが、管理目的であなたが使用するのと異なるユーザ名を 使用してデータベースに接続することを考慮してください。必要以上のアクセス権 をアプリケーションに与えないで下さい。
        • Users of PHP:
          • Check out the addslashes() function. As of PHP 4.0.3, a mysql_escape_string() function is available that is based on the function of the same name in the MySQL C API.
        • Users of MySQL C API:
          • Check out the mysql_real_escape_string() API call.
        • Users of MySQL++:
          • Check out the escape and quote modifiers for query streams.
        • Users of Perl DBI:
          • Check out the quote() method or use placeholders.
        • Users of Java JDBC:
          • Use a PreparedStatement object and placeholders.
      • 生のデータ(暗号化されていないデータ)をインターネット越しに送ってはいけませ ん。このデータは、その情報をトラップして、どこかで再利用することに興味のあ る誰にでもアクセス可能です。もし送る必要があるなら、SSL のような暗号化され た通信を使用すべきです。MySQL はバージョン 4.0.0 から内部 SSL 接 続をサポートします。暗号化された(そして圧縮された)通信のトンネルを生成する ために、SSH ポートフォワーディングを使用することができます。
      • tcpdump と strings ユーティリティを使うことを学んで下さい. 以下のコマンドで、ほとんどの場合、暗号化されていない MySQL のデータが見えるでしょう： 
        shell> tcpdump -l -i eth0 -w - src or dst port 3306 | strings
        (この例は Linux のものです。他のシステムでは少し違うでしょう). 警告: データが見えなくても、実際に常に暗号化されているわけではありません。 高いセキュリティが必要なら、セキュリティエキスパートに相談すべきです。

      4.2.2 MySQL をクラッカーに対して安全にする方法

      MySQL サーバーに接続するときは、パスワードを使用すべきです。 パスワードはコネクション間で、べたテキストでは流れません。 しかし、暗号化アルゴリズムはそんなに強力なわけではありません。クライアント とサーバ間のトラフィックを sniff できれば、いくつかの試みで、賢いアタッカー はパスワードをクラックできます。クライアントとサーバ間の接続が信頼できない ネットワークを通るなら、通信を暗号化するために SSH トンネルを使用 すべきです。

      その他の全ての情報はテキストで転送され、 これは接続を覗くことが出来る人に読まれます。 もしこれを心配するなら、圧縮プロトコル(MySQL バージョン 3.22 以上)を 使用することが出来ます。より安全にしたい場合、 ssh をインストールすべきです。 オープンソースの ssh クライアントは http://www.openssh.org/ に、 商用の ssh クライアントは http://www.ssh.com/ に見ることができます。 これを使用すれば、MySQL サーバーと MySQL クライアント 間の TCP/IP コネクションは全て暗号化されます。

      If you are using MySQL 4.0, you can also use internal OpenSSL support. 「4.3.9 Using Secure Connections」節参照.

      MySQL システムを安全にするためには、次のことを考えるべきです:

      • 全ての MySQL ユーザにパスワードを使用すべきです。 other_user にパスワードが設定されていない場合、 誰でも mysql -u other_user db_name として簡単に他の人としてログインでき ることを覚えてください。これは全てのクライアント／サーバアプリケーション で一般的な振る舞いです。全てのユーザのパスワードは、 mysql_install_db スクリプトを実行前に編集することで、または MySQL root ユーザだけは次のようにして変更することができます。 
        shell> mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD('new_password')
    ->             WHERE user='root';
mysql> FLUSH PRIVILEGES;
      • MySQL デーモンを Unix の root ユーザーで実行しないでください。 FILE権限を持つ任意のユーザが root としてファイル(例えば、 ~root/.bashrc)を生成できるためとても危険です。これを防ぐために、 mysqld は、--user=root オプションで直接指定されない限り、 root としての実行を拒否します。 代わりに mysqld は権限を持たない一般ユーザとして実行できます。 より安全にするため、新しく Unix ユーザ mysql を追加することもできます。 mysqld を 他の Unix ユーザーで起動したとしても、 MySQL の user テーブルの root ユーザーの名前を変更する必要はありません。 なぜなら、 MySQL ユーザーの名前は Unix のユーザー名とはなんの関係もないからです。 root ユーザ名を変更する必要はありません。 mysqld を他の Unix ユーザで起動するためには、`/etc/my.cnf' オ プションファイルまたはサーバのデータディレクトリの `my.cnf' オプショ ンファイルの、[mysqld] グループにユーザ名を記述した user 行 を追加してください。たとえば: 
        [mysqld]
user=mysql
        これは、あなたが手動で起動したり safe_mysqld または mysql.server を使用して起動しても、指定されたユーザでサーバを起動さ せます。詳細は、 「A.3.2 一般ユーザで MySQL を動かす方法」節. を見てください。
      • Don't support symlinks to tables (this can be disabled with the --skip-symlink option). This is especially important if you run mysqld as root as anyone that has write access to the mysqld data directories could then delete any file in the system! 「5.6.1.2 Using Symbolic Links for Tables」節参照.
      • データベースディレクトリは mysqld を実行している Unix ユーザだけが 読み込み／書き込み可能なことをチェックしてください。
      • PROCESS 権限を全てのユーザに与えないでください。この許可がある人は誰でも mysqladmin processlist コマンドで実行されているクエリーの中身を見ることができます。 もし誰かが、UPDATE user SET password=PASSWORD('not_secure') クエリーを 実行していたとして、それが見えてしまいます。 mysqld は PROCESS 権限を持つユーザに対する特別な接続をリザーブします。 そのため、たとえ全ての通常接続が使われたとしても、MySQL root ユーザだけは、 ログインでき、いろいろチェックできます。
      • FILE 権限を全てのユーザに与えないでください。ユーザがこの権限を持つ場合、 mysqld デーモンを実行している Unix ユーザーの権限で ファイルシステム内のどこにでもファイルを書き込むことができます！ これを少し安全にするため、SELECT ... INTO OUTFILE で作成される全てのファイルは 全員が書き込み可能な状態で生成されますが、 既存のファイルを上書きすることができないようになっています。 FILE 権限はサーバーを走らせている Unix ユーザーがアクセスできる 全てのファイルを読むために使用されかもしれません。 いかなるファイルもカレントのデータベースに取りこめます。 例えば、 LOAD DATA を使用して `/etc/passwd' をテーブルに 取り込むと、SELECT でその内容が読めることになります。
      • あなたの DNS を信用しない場合、権限テーブル内にはホスト名の代わりに IP を使用すべきです。mysqld への --secure オプションは原理上はホスト名を安 全にします。どんな場合でも、ワイルドカードを含んだホスト名を、許可テーブルに登録する 事は本当に注意深くすべきです！
      • 一ユーザからの接続数を制限したい場合は、mysqld の max_user_connections 変数を設定することで、これを行なうことができま す。

      4.2.3 セキュリティに関する mysqld の起動オプション

      mysqld の次のオプションはセキュリティに影響します:

      --local-infile[=(0|1)]
      If one uses --local-infile=0 then one can't use LOAD DATA LOCAL INFILE.
      --safe-show-database
      With this option, the SHOW DATABASES command returns only those databases for which the user has some kind of privilege. From version 4.0.2 this option is deprecated and doesn't do anything (the option is enabled by default) as we now have the SHOW DATABASES privilege. 「4.3.1 GRANT と REVOKE 構文」節参照.
      --safe-user-create
      If this is enabled, an user can't create new users with the GRANT command, if the user doesn't have the INSERT privilege for the mysql.user table. If you want to give a user access to just create new users with those privileges that the user has right to grant, you should give the user the following privilege: 
      mysql> GRANT INSERT(user) ON mysql.user TO 'user'@'hostname';
      This will ensure that the user can't change any privilege columns directly, but has to use the GRANT command to give privileges to other users.
      --skip-grant-tables
      特権システムを全く使用しません。これは全員に全てのデータベースへの 完全なアクセス を与えます！ (mysqladmin flush-privileges か mysqladmin reload を実行することで、 起動しているサーバーは特権システムを使用するようになります。)
      --skip-name-resolve
      ホスト名を解析しません。権限テーブル中の全ての Hostフィールドは IP アドレスか localhost でなければなりません。
      --skip-networking
      ネットワーク (TCP/IP) 経由の接続を許可しません。mysqld への全ての接続は、 Unix ソケットで行われます。MIT-pthreads は Unix ソケットをサポートしない ため、このオプションは MIT-pthreads を使用するシステム上で MySQL 3.23.27 以前のバージョンを使用する場合は、うまく動きません。
      --skip-show-database
      Don't allow SHOW DATABASES command, unless the user has the SHOW DATABASES privilege. From version 4.0.2 you should no longer need this option, since access can now be granted specifically with the SHOW DATABASES privilege.

      4.2.4 Security issues with LOAD DATA LOCAL

      In MySQL 3.23.49 and MySQL 4.0.2, we added some new options to deal with possible security issues when it comes to LOAD DATA LOCAL.

      There are two possible problems with supporting this command:

      As the reading of the file is initiated from the server, one could theoretically create a patched MySQL server that could read any file on the client machine that the current user has read access to, when the client issues a query against the table.

      In a web environment where the clients are connecting from a web server, a user could use LOAD DATA LOCAL to read any files that the web server process has read access to (assuming a user could run any command against the SQL server).

      There are two separate fixes for this:

      If you don't configure MySQL with --enable-local-infile, then LOAD DATA LOCAL will be disabled by all clients, unless one calls mysql_options(... MYSQL_OPT_LOCAL_INFILE, 0) in the client. 「8.4.3.163 mysql_options()」節参照.

      For the mysql command-line client, LOAD DATA LOCAL can be enabled by specifying the option --local-infile[=1], or disabled with --local-infile=0.

      By default, all MySQL clients and libraries are compiled with --enable-local-infile, to be compatible with MySQL 3.23.48 and before.

      One can disable all LOAD DATA LOCAL commands in the MySQL server by starting mysqld with --local-infile=0.

      In the case that LOAD DATA LOCAL INFILE is disabled in the server or the client, you will get the error message (1148): 

      The used command is not allowed with this MySQL version

      4.2.5 特権システムの行うこと

      MySQL 特権システムの基本機能は、与えられたホストから接続する ユーザを認証すること、そしてデータベースに対する SELECT, INSERT, UPDATE, DELETE 等の権限を与えることです。

      拡張機能は匿名ユーザをもつ能力を含み、LOAD DATA INFILE のような MySQL 固有の機能を使用する許可を与えます。

      4.2.6 特権システムはどのように動くか？

      MySQL の特権システムは、全てのユーザーが与えられた許可の範囲内で動く事を保証します。 MySQL サーバーに接続するとき、本人の身元は、接続元のホスト と 接続に使用するユーザー名 によって確認されます。 このシステムは、あなたの身元とあなたが要求することが何か によって、権限を与えます。

      MySQL はあなたのホスト名とユーザー名の両方をあわせてチェックします。 これはインターネット上に同じ名前のユーザーがどこかにいるかもしれないということからそうしています。 例えば、office.com から接続してきた joe と、 elsewhere.com から接続してきた joe は同一人物である必要はありません。 MySQL はこの違うホストから接続してきた同名のユーザーを以下のようにして扱います： office.com から接続した joe にある許可をあたえ、 それとは違う許可を elsewhere.com から接続してきた joe に与えます。

      MySQL のアクセスコントロールは以下の二つからなります：

      • Stage 1: サーバーは接続許可があるかどうかをチェックします。
      • Stage 2: 接続許可後、サーバーはそれぞれのリクエストをチェックします。 あなたが要求してきた事柄を、あなたが実行できるかどうかをチェックします。 例えば、あるデータベースのテーブルの行の取り出しやテーブルの破棄をあなたが命令した場合、 サーバーは、あなたにそのテーブルに対する SELECT 権限があるのか、 データベースに対して DROP する許可が与えられているのか、を確認します。

      サーバーは mysql データベースの user, db, host ３つのテーブルから、 この２つのアクセス制限を決定します。 このテーブルのフィールドは以下のようになっています：

      Table name user db host
      Scope fields Host Host Host
      User Db Db
      Password User
      Privilege fields Select_priv Select_priv Select_priv
      Insert_priv Insert_priv Insert_priv
      Update_priv Update_priv Update_priv
      Delete_priv Delete_priv Delete_priv
      Index_priv Index_priv Index_priv
      Alter_priv Alter_priv Alter_priv
      Create_priv Create_priv Create_priv
      Drop_priv Drop_priv Drop_priv
      Grant_priv Grant_priv Grant_priv
      References_priv
      Reload_priv
      Shutdown_priv
      Process_priv
      File_priv

      　アクセスコントロールの第2段階(要求承認)のために、サーバーはこれら 3 つの テーブルによって決められた許可を基本としますが、もしテーブルに対する要求で あるならば、tables_priv と columns_priv テーブルを さらに調べます。これらのテーブルのフィールドは以下のようになっています：

      Table name tables_priv columns_priv
      Scope fields Host Host
      Db Db
      User User
      Table_name Table_name
      Column_name
      Privilege fields Table_priv Column_priv
      Column_priv
      Other fields Timestamp Timestamp
      Grantor

      　テーブルの各フィールドを分類すると、２種類にわかれます： 適用範囲を指定するフィールド(以下　スコープフィールド)と許可を定義するフィールド(以下　権限フィールド)です。

      　スコープフィールドは、権限テーブルの登録ごとに、その適用範囲を決めます。 例えば、 user テーブルの Host と User に 'thomas.loc.gov' と 'bob' が登録されている場合、 サーバーへの接続は ホスト thomas.loc.gov から来た 'bob' に許可されます。 同様に、db テーブルの Host, User, Db に 'thomas.loc.gov', 'bob', 'reports' が登録されていると、 ホスト thomas.loc.gov から来た bob に対し reports データベースへの接続が許されます。 tables_priv と columns_priv テーブルは、 テーブルか、テーブルとフィールドを対にしたスコープフィールドを含みます。

      　アクセスのチェックは、Host の値はケース非依存で比較されます。 User, Password, Db, Table_name の値はケース依存で比較されます。 Column_name の値は MySQL バージョン 3.22.12 以上ではケース非依存で比較されます。 (バージョン 3.22.11 までは ケース依存です)

      権限フィールドは、どのような操作が実行できるか、許可されているかを示します。 サーバーは権限テーブルの情報を、ユーザーの権限を得るために使用します。 このユーザーの権限を割り出す方法は 「4.2.10 Access Control, Stage 2: Request Verification」節 に述べておきます。

      スコープフィールドは文字で定義され、デフォルト値は空文字になっています：

      Field name Type Notes
      Host CHAR(60)
      User CHAR(16)
      Password CHAR(16)
      Db CHAR(64) (CHAR(60) for the tables_priv and columns_priv tables)
      Table_name CHAR(60)
      Column_name CHAR(60)

      user, db, host テーブルでは、 全ての権限フィールドは ENUM('N','Y') で定義されます。 この値は 'N' か 'Y' のどちらかで、デフォルト値は 'N' です。

      tables_priv と columns_priv テーブルでは、 権限フィールドは SET フィールドとして定義されます：

      Table name Field name Possible set elements
      tables_priv Table_priv 'Select', 'Insert', 'Update', 'Delete', 'Create', 'Drop', 'Grant', 'References', 'Index', 'Alter'
      tables_priv Column_priv 'Select', 'Insert', 'Update', 'References'
      columns_priv Column_priv 'Select', 'Insert', 'Update', 'References'

      サーバーは以下のように権限テーブルを使用します：

      • user テーブルのスコープフィールドは、接続要求を受け入れるか拒否するかを決定します。 許可された接続について、user テーブルで与えられたすべての権限は、ユー ザのグローバル(スーパーユーザ)権限を示します。この権限はサーバ上の すべての データベースに適用されます。 (訳注： 例えば、user テーブル の権限を 'Y' にした場合、 どんなに db テーブルや host テーブルで権限を 'N' にしたとしても 権限は 'Y' のままである。 つまり user テーブルの権限許可 'Y' が全てに反映されてしまうという事。 user テーブルには最低限の許可を与えるようにし、 db テーブルや host テーブルで、それぞれの権限を許可する方が無難。 )
      • db と host テーブルは一緒に使用されます：
        • db テーブルのスコープフィールドはどのホストからどのデータベースのアクセスできるかを決定します。 権限フィールドは、どういった操作ができるかを定義します。
        • host テーブルは、db テーブルの登録をいくつかのホストに与えたい時に、 db テーブルの拡張として使用されます。 例えば、ネットワーク上の限定したマシンからデータベースを使用したい場合、 db テーブルの Host の値は空にしておきます。 そして host テーブルにそれぞれのホストについての登録を行います。 この機構は、 「4.2.10 Access Control, Stage 2: Request Verification」節 で詳細に述べられています。
      • tables_priv と columns_priv テーブルは db テーブルに似ていますが、 それらはより細かく定義できます； データベースレベルではなく、テーブルとフィールドのレベルで与えます。

      管理者権限 (RELOAD, SHUTDOWN,など) は user テーブルにだけ定義するように。 これは、管理者操作はデータベースではなくサーバーへの操作であり、 他の許可テーブルにある必要がないからです。 またこうしておくと、管理者操作の許可は、user テーブルの定義だけを 見ればわかるようになります。

      FILE 操作の権限は user テーブルにだけ定義するように。 これは管理者操作ではありませんが、アクセスしているデータベースにかかわらず、 サーバー内のファイルを読み書きできるのです。

      mysqld サーバーは起動時にこれらのテーブルを読み込みます。 許可テーブルの変更を反映させる方法はこちらを参照のこと → 「4.3.3 いつ権限の変更が反映されるか」節

      これらのテーブルの登録を変更した場合、思ったとおりの権限状態になっている事を確認することはいいことです。 問題の解決には, 「4.2.11 何故 Access denied エラーになるのか」節. セキュリティに関するアドバイスは 「4.2.2 MySQL をクラッカーに対して安全にする方法」節.

      便利なツールとして mysqlaccess スクリプト( Yves Carlier 作)が MySQL の配布に含まれています。 mysqlaccess を --help オプションで起動するとヘルプが表示されます。 mysqlaccess は user,db and host テーブルだけしか 検査しません。テーブルレベルの権限、フィールドレベルの権限は調べません。

      4.2.7 MySQL が提供する権限

      権限の設定は mysql データベースの user, db, host, tables_priv, columns_priv で行います。 (mysql はデータベースの名前です) MySQL サーバーは、サーバーの起動時か 「4.3.3 いつ権限の変更が反映されるか」節 で説明されている方法により、 これらのテーブルから権限の設定を読み込みます。

      MySQL 4.0.2 が提供する権限の名称は, 本マニュアルでは以下の表の名称を用います。 この表の項目名がそれぞれの許可される権限とその説明に対応しています：

      Privilege Column Context
      ALTER Alter_priv tables
      DELETE Delete_priv tables
      INDEX Index_priv tables
      INSERT Insert_priv tables
      SELECT Select_priv tables
      UPDATE Update_priv tables
      CREATE Create_priv databases, tables, or indexes
      DROP Drop_priv databases or tables
      GRANT Grant_priv databases or tables
      REFERENCES References_priv databases or tables
      CREATE TEMPORARY TABLES Create_tmp_table_priv server administration
      EXECUTE Execute_priv server administration
      FILE File_priv file access on server
      LOCK TABLES Lock_tables_priv server administration
      PROCESS Process_priv server administration
      RELOAD Reload_priv server administration
      REPLICATION CLIENT Repl_client_priv server administration
      REPLICATION SLAVE Repl_slave_priv server administration
      SHOW DATABASES Show_db_priv server administration
      SHUTDOWN Shutdown_priv server administration
      SUPER Super_priv server administration

      SELECT, INSERT, UPDATE, DELETE の権限は、 存在しているデータベースのテーブルに対して許可されます。

      もしテーブルから行を取り出すだけなら、SELECT 構文を実行するためには SELECT 権限だけあればかまいません。 ただし、サーバーのどのデータベースにアクセスを許可されていない場合でも、 ある種の SELECT は実行することができます。 例えば、簡単な計算を mysql クライアントで行う場合です： 

      mysql> SELECT 1+1;
mysql> SELECT PI()*2;

      INDEX 権限はインデックスの作成と破棄(削除)を許可します。

      ALTER 権限は ALTER TABLE の実行を許可します。

      CREATE と DROP 権限は、新しいデータベースやテーブルの作成、 あるいは既に存在するデータベース、テーブルの破棄(削除)を許可します。

      注意： mysql データベースに登録されているユーザーに DROP 権限を与えると、 そのユーザーは MySQL のアクセス権限が格納されているデータベースを破棄できます！

      GRANT 権限は、あなたが他のユーザーに対して自分の権限を持たせる事を許可します。

      FILE 権限を与えると、LOAD DATA INFILE と SELECT ... INTO OUTFILE 構文を 使用して、サーバーのファイルを読み書きする事ができます。 この権限が与えられたユーザーは、MySQL サーバーを使用していかなるファイルも 読むことが出来ますし、MySQL サーバーが書き込めるディレクトリに誰もが読める 新しいファイルを作成することも出来ます。 そのユーザーはカレントのデータベースのディレクトリにあるいかなるファイルも 読むことができます。 しかし、既に存在しているファイルを変更することはできません。

      残りの権限はアドミン操作に関する許可で、mysqladmin コマンドを使用して実行します。 次の表に mysqladmin コマンドのどれが、どの権限に対応しているかを示します：

      Privilege Commands permitted to privilege holders
      RELOAD reload, refresh, flush-privileges, flush-hosts, flush-logs, and flush-tables
      SHUTDOWN shutdown
      PROCESS processlist
      SUPER kill

      reload コマンドはサーバーに権限の設定を再読込させるように伝えます。 refresh コマンドは全てのテーブルをフラッシュし、ログファイルを開き直します。 flush-privileges は reload と同義です。 その他の flush-* コマンドは refresh の動作とよく似ていますが、 適用範囲を絞っており、ちょっとした場合に有効です。 例えば、ログファイルだけをフラッシュしたい場合、 refresh を行うよりも flush-logs がいいです。

      shutdown コマンドは、サーバーをシャットダウンします。

      processlist コマンドはサーバーが実行しているスレッドの情報を表示します。 kill コマンドはサーバーのスレッドをkillします。 自分のスレッドは常に表示、killできますが、他人のスレッドを見るには PROCESS 権限が必要で、他人のスレッドをkillするには SUPER 権限が必要です。 「4.5.5 KILL 構文」節参照. (SUPER 権限は 4.0.2で追加されました)

      ある権限を欲しがるユーザーだけにその権限を許可するのはよい考えですが、 権限を与えるときには、特定の事項を熟知していなければなりません：

      • GRANT 権限を許可されたユーザーは、他のユーザーの権限を変える事ができます。 二人のユーザー間で違っている権限と grant 権限を入れ換えることができます。
      • ALTER 権限は、テーブル名の変更を行うことにより特権システムを破るために 使用されるかもしれません。
      • FILE 権限は、サーバー上にある全ての読み込み可能なファイルと カレントのデータベースのディレクトリにあるファイルを、 データベースのテーブルに取り込むことができ、 その内容は SELECT 文を使用することでアクセスできます。
      • SHUTDOWN 権限は、他のユーザーに対するサービスを、サーバーを 停止することによって、拒否するようにできます。
      • PROCESS 権限は実行されているクエリーをプレーンテキストで見ることに使えます。 パスワードの設定、変更のクエリーも含みます。
      • mysql データベースに対しての権限は、パスワードの変更や他の権限の変更に、使用されます。 (パスワードは暗号化されて登録されており、悪意のあるユーザーでも 単純に読むことはできません). mysql.user のパスワードフィールドにアクセスできれば、それを使用して MySQL サーバに与えられたユーザでログインすることができます。(十分 な権限があれば、同じユーザが別のものにパスワードを置き換えることもできます。 )

      以下は MySQL の特権システムで行うものではありません：

      • アクセスを拒否するユーザーを特定して設定することはできません。 完全に一致したユーザーからの接続を拒否できません。
      • データベース内のテーブルの作成、破棄の権限を持つが、 データベースそのものを作成、破棄できる、そのようなユーザーを設定できません。

      4.2.8 MySQL サーバーに接続

      MySQL クライアントプログラムは、共通の決まった引数を持ちます： 接続したいホスト名、接続ユーザー名、そしてパスワードです。 例えば、mysql コマンドは以下のような引数を持ちます (オプションの引数は `[' と `]' で囲まれている部分です) 

      shell> mysql [-h host_name] [-u user_name] [-pyour_pass]

      -h, -u, -p オプションは以下と等価です。 --host=host_name, --user=user_name, --password=your_pass -p とパスワードの間にはスペースがないことに注意

      注意: コマンドラインにパスワードを与えるのは安全ではありません！ システムに入っている如何なるユーザーも ps auxww のようなコマンドを 使用する事でパスワードを見付ける事ができます. 「4.1.2 `my.cnf' オプションファイル」節参照.

      mysql コマンドはコマンドラインに引数がなければ接続にデフォルト値を用います。

      • デフォルトのホスト名は localhost.
      • デフォルトのユーザー名は Unix のログイン名です。
      • -p が指定されていなければパスワードは与えられません

      Unix のログインユーザーが joe の場合、以下のコマンドは等価です： 

      shell> mysql -h localhost -u joe
shell> mysql -h localhost
shell> mysql -u joe
shell> mysql

      他の MySQL クライアントも同じように動作します。

      Unix システムでは、ある値をデフォルト値にして接続に使用することができます。 そうすることにより、毎回毎回コマンドラインに引数を与えなくてすむようになります：

      • 自分のホームディレクトリに `.my.cnf' を作り、そのファイルの中の [client] セクションに接続用のパラメターを記述できます。 その記述は以下のようになります： 
        [client]
host=host_name
user=user_name
password=your_pass
        「4.1.2 `my.cnf' オプションファイル」節参照.
      • 接続のパラメターに環境変数を使用することもできます。 ホスト名は MYSQL_HOST 環境変数を使用します。 MySQL のユーザー名は USER (これは Windows のみ) に設定された値を使用します。 パスワードは MYSQL_PWD 環境変数を見ますが、これは危険です。(次の節参照) 「F Environment Variables」節参照.

      4.2.9 Access Control, Stage 1: 接続の承認

      MySQL サーバーに接続すると、あなたがパスワード認証して接続していようがいまいが、 サーバーはあなたの身元により接続の許可拒否を行います。 もし身元が一致しない場合接続を拒否し、接続許可した場合、 サーバーは Stage 2 へと進み、要求を待ちます。

      身元は二つのものに基づいて確認されます：

      • あなたが接続しようとしているホスト
      • あなたの MySQL ユーザー名

      身元の確認は user テーブルのスコープフィールド (Host, User, Password) を使用して行います。 サーバーは user テーブルの登録に一致しているホスト名と ユーザー名に限り接続を許可し、その後、パスワードを要求します。

      user テーブルのスコープフィールドの登録は以下のようになります：

      • Host の値はホスト名か IP アドレスか 'localhost'(ローカルホスト) です。
      • Host、Db フィールドにはワイルドカード文字 `%' と `_' を使用できます。 If you wish to use for instance a `_' character as part of a database name, specify it as `\_' in the GRANT command.
      • Host に '%' を設定すると、全てのホストにマッチします。
      • 空の Host 値は、権限が host テーブル内の与えられたホスト名に 適合するエントリと AND されることを意味します。次の章にこれについての詳し い情報を見つけられます。
      • MySQL バージョン 3.23 では、IPアドレスが記述された Host 値には、何 ビットがネットワークアドレスに使用されるかを示すネットマスクを記述すること ができます。例えば: 
        mysql> GRANT ALL PRIVILEGES ON db.*
    -> TO david@'192.58.197.0/255.255.255.0';
        これは、次が真になる IP からの接続をすべて許可します: 
        user_ip & netmask = host_ip.
        上記の例では、192.58.197.0〜192.58.197.255 のすべての IP が MySQL サーバに接続できます。
      • ワイルドカード文字は User フィールドには設定できませんが、 User フィールドをブランク(空)にすることはできます。ブランクは全ての名前にマッチします。 これはユーザー名がない状態で接続してきたものに適用され、 クライアントがユーザー名を明記しない限り、匿名ユーザー(名前がブランク)として扱われます。 全てのアクセスのチェックにブランクのユーザー名が使用される事を意味します。 (that is, during Stage 2).
      • Password フィールドは空にできます。 これは、いかなるパスワードにもマッチするという意味ではなくて、 パスワードなして接続できるということになります。

      非ブランクの Password 値はパスワードを暗号化したものです。 MySQL はだれもが見れるようにパスワードを平文では保存しません。 接続を試みようとしているユーザーのパスワードも、(PASSWORD() 関数で) 暗号化されます。 それから、暗号化パスワードは、クライアント／サーバがパスワードが正しいかチェッ クする時に使用されます(This is done without the encrypted password ever traveling over the connection)。注意: MySQL では、暗号化パスワー ドが本当のパスワードです。そのため、それへのアクセスを誰にも与えるべきでは ありません！ 特に、一般ユーザにはmysql データベース内のテーブルの読 み取り権を与えないでください！ From version 4.1, MySQL employs a different password and login mechanism that is secure even if TCP/IP packets are sniffed and/or the mysql database is captured.

      以下の表は、接続要求に対して与える、 user テーブルの Host と User の設定例です：

      Host value User value Connections matched by entry
      'thomas.loc.gov' 'fred' fred, thomas.loc.gov から接続
      'thomas.loc.gov' '' thomas.loc.gov から接続してくる全てのユーザー
      '%' 'fred' fred, 全てのホストから接続
      '%' '' 全てのホストから接続してくる全ユーザー
      '%.loc.gov' 'fred' fred, loc.gov ドメイン内の全てのホストからの接続
      'x.y.%' 'fred' fred, x.y.net, x.y.com,x.y.edu, などからの接続. (あまり有効な使い方ではないです)
      '144.155.166.177' 'fred' fred, IP address が 144.155.166.177 のホストからの接続
      '144.155.166.%' 'fred' fred, 144.155.166 class C subnet 内の全てのホストからの接続
      '144.155.166.0/255.255.255.0' 'fred' 上の例と同じ

      Host に IP のワイルドカード(例えば '144.155.166.%' は サブネットの全てのホストにマッチ) を使用することができます。 が、この場合、 144.155.166.somewhere.com というホスト名で だれかが接続しようとしてくるかもしれません。 このような攻撃に対し、MySQL は数字やドットで始まるホスト名を拒否しています。 もし 1.2.foo.com のような名前のホストを持っている場合、 許可テーブルの Host には絶対にマッチしません。 IPアドレスのみ、IP のワイルドカードにマッチする事になります。

      サーバーに来る接続は、user テーブル内の登録に１つ以上 マッチするかもしれません。 例えば, thomas.loc.gov の fred からの接続は、上に示された 登録のうちのいくつかにマッチするでしょう。 サーバーは、複数の登録にマッチした場合、どのようにしてその中から 使用する登録を選ぶのでしょう？ サーバーは起動後に user テーブルをソートし、並び換えられた順に 登録を検索することにより、この問題を解決します。 最初にマッチした登録が使用されます。

      user テーブルが以下のようにソートされていた場合： 

      +-----------+----------+-
| Host      | User     | ...
+-----------+----------+-
| %         | root     | ...
| %         | jeffrey  | ...
| localhost | root     | ...
| localhost |          | ...
+-----------+----------+-

      サーバーがこのテーブルを読むと、Host に値が最も確実に特定できる ホストを指定しているエントリを、最初に参照します。 (Host 項の '%' は ``すべてのホスト'' を意味し、 ホスト名をはっきりと特定しているものではありません) Host の値が同じエントリがあった場合、もっとも明確に User の値が ユーザーを指定しているエントリを最初に参照します。 (User の値が空の場合、``だれでも'' を意味します) この結果、user テーブルは以下のようにソートされます： 

      +-----------+----------+-
| Host      | User     | ...
+-----------+----------+-
| localhost | root     | ...
| localhost |          | ...
| %         | jeffrey  | ...
| %         | root     | ...
+-----------+----------+-

      接続が試みられた場合、サーバーは並び換えられた登録を探し、最初に見つけたものを 使用します。 'localhost' の jeffrey からの接続は、まず最初に Host に localhost を設定しているエントリにマッチします。 ユーザー名が空のエントリは、ホスト名とユーザー名の両方を指定した接続にもマッチします。 ( '%'/'jeffrey' エントリもマッチします。が、これは最初にはマッチしません。)

      もう一例。user が以下の設定と仮定します： 

      +----------------+----------+-
| Host           | User     | ...
+----------------+----------+-
| %              | jeffrey  | ...
| thomas.loc.gov |          | ...
+----------------+----------+-

      これは次のようにソートされます： 

      +----------------+----------+-
| Host           | User     | ...
+----------------+----------+-
| thomas.loc.gov |          | ...
| %              | jeffrey  | ...
+----------------+----------+-

      thomas.loc.gov の jeffrey からの接続は、最初のエントリにマッチし、 whitehouse.gov の jeffrey からの接続は、二つ目のエントリにマッチします。

      よくある考え違いは、ユーザー名を与えて接続した場合、 サーバーが接続にマッチするものを探す際に、 そのユーザー名が指定されているルールが 最初に使用されるだろうと考えることです。これは正しくありません。 前の例でこれを示しましたが、thomas.loc.gov の jeffrey からの接続が 最初にマッチするのは、 User フィールドの値が 'jeffrey' に なっているエントリではなく、ユーザー名なし(＝だれでも) のエントリの方が 先にマッチします！

      もしサーバーへの接続がうまく行かない場合、 user テーブルを表示し、 マニュアルでソートしてみて、どのエントリに最初にマッチするか探してください。

      If connection was successful, but your privileges are not what you expected you may use CURRENT_USER() function (new in version 4.0.6) to see what user/host combination your connection actually matched. 「6.3.6.2 その他の関数」節参照.

      4.2.10 Access Control, Stage 2: Request Verification

      一度接続か確立されると、サーバーはステージ２に移ります。 このステージでは、サーバーはこの接続から来るそれぞれの要求が許可されて いるかどうかをチェックします。 チェックは実行しようとしている操作のタイプにより行います。 その操作が許可テーブルのどの権限フィールドに当てはまるかを見ます。 これら権限は user, db,host, tables_priv か columns_priv テーブルより導出されます。 権限テーブルは GRANT, REVOKE コマンドで操作します。 「4.3.1 GRANT と REVOKE 構文」節参照. (You may find it helpful to refer to 「4.2.6 特権システムはどのように動くか？」節, which lists the fields present in each of the grant tables.)

      user テーブルは全てに対して基本となる権限をユーザーに割り当てます。 たとえカレントのデータベースに許可を与えていなくても、user テーブルの設定方が有効になります。 例えば、user テーブルで DELETE を許可した場合、 サーバーにあるどんなデータベースの行も削除できるのです！ いうならば、user テーブルの権限はスーパーユーザーの権限と言ってもいいでしょう。 この権限はスーパーユーザー(サーバーやデーターベース管理者)のみに与えておく事が賢明です。 他のユーザーは、user テーブルの権限の設定を 'N' のままにしておくべきですし、 また、db テーブルと host テーブルを利用して、 データベースを指定した上でユーザーに権限を許可すべきです。

      db テーブルと host テーブルは特定のデータベースに対する権限許可を行います。 スコープフィールドの値は次のように記述されます:

      • ワイルドカード文字 `%' と `_' は Db テーブルと Host フィールドだけに使用できます。
      • '%' Host 値は ``あらゆるホスト'' を意味します。 db テーブルの Host に空を設定すると、``さらに host テーブルに許可情報を探しにいく'' となります。
      • '%' か 空値を Host テーブルに設定すると、それは ``あらゆるホスト'' となります。
      • '%' か 空値を host テーブルの Db フィールドに設定すると、 それは ``あらゆるデータベース'' となります。
      • User を空値にすると、匿名ユーザーにマッチします。

      サーバー起動時に、db テーブルと host テーブルはサーバーに読み込まれます。 (user テーブルもこの時に同時に読まれます) db テーブルは Host, Db, User のフィールドでソートされ、 host テーブルは Host, Db フィールドでソートされます。 user テーブルは、一番特定できるエントリを最初に、一番特定できないものを最後にソートします。 サーバーはソートされたものの中から、最初にマッチしたものを使用します。

      tables_priv と columns_priv テーブルは、 特定のテーブルとフィールドに対する権限を許可します。 スコープフィールドの値は、いかにそって記述されます：

      • ワイルドカード文字 `%' と `_' はどちらかのテーブルの Host フィールドに使用できます。
      • どちらかのテーブルの Host 値を '%' かブランクにすると、 ``any host.'' を意味します。
      • Db, Table_name, Column_name フィールドはどのテーブルにも ワイルドカードやブランクは使用できません。

      tables_priv と columns_priv テーブルは Host, Db, User フィールドで並び換えられます。 これは db テーブルのソートに似ていますが、 Host フィールドだけが ワイルドカードを含むので、ソートはより単純なものになります。

      この要求の承認は次のようにして行います。 もしアクセス承認を決定する部分のソースコードを理解できるなら、 ちょっと変わったアルゴリズムで承認の決定を行っている事に気づくでしょう。

      管理者の要求(SHUTDOWN, RELOAD, etc.)については、サーバーは user テーブルだけを参照します。(user テーブルだけが管理者権限のフィールドを持つ)。 エントリに許可登録されている操作は受け入れられ、それ以外は拒否されます。 例えば、mysqladmin shutdown を実行しようとしても、 user テーブルの SHUTDOWN 権限が許されていなければ実行できません。 この時、db と host テーブルはチェックされません。 (これらのテーブルには Shutdown_priv フィールドが無いからです)

      データベースへの要求 (INSERT, UPDATE, etc.) において、 サーバーはまず最初に、ユーザーのグローバルな権限(スーパーユーザー)を user の中から探しだします。 もし許可が与えられていれば、アクセスは成功します。

      user テーブルのグローバルな権限の設定が不十分であるなら、 サーバーはユーザーのデータベースに対する権限を db テーブルと host テーブルから決定します：

      1. サーバーは db テーブルの Host,Db,Userフィールドを参照します。 Host と User フィールドはユーザーの接続時のホスト名と MySQL ユーザー名にマッチします。 Db フィールドはユーザーがアクセスしたいデータベース名にマッチします。 Host と User にマッチするものが無かった場合、アクセスは拒否されます。
      2. db テーブル内の Host フィールドが空でないエントリにマッチした場合、 ユーザーの指定されているデータベースに対する権限が定義されます。
      3. Host フィールドが空値の db テーブルのエントリにマッチした場合、 どのホストがそのデータベースへアクセスできるかを host テーブルから探し出します。 この場合、host テーブル の Host, Db フィールドとマッチするものを探し出します。 host テーブルにエントリがなかった場合、アクセスは拒否されます。 もしマッチすると、ユーザーの特定データベースに対する権限は、 host テーブルと db テーブル両方にまたがった権限から割り出されます。 いうならば両方とも 'Y' である権限。 (この方法を使用すると、まず db テーブルのエントリに大まかな権限を設定しておき、 それから host テーブルのエントリを使用して、ホスト情報もとに権限を限定していくという事ができます)

      特定データベースに対する権限が db テーブルと host テーブルのエントリから決定された後、 サーバーはその割り出された権限に対し、user テーブルて設定されている権限を加えます。 この結果から得られた権限にマッチした要求は受け入れられます。 そうでなければ、サーバーはユーザーのテーブル、フィールドに対する許可を、 tables_priv と columns_priv 内に探します。 アクセスはこの結果により、許可、拒否されます。

      先のユーザーの権限が計算される方法の記述は、boolean 表記で示すならば、 以下のようになるでしょう： 

      global privileges
OR (database privileges AND host privileges)
OR table privileges
OR column privileges

      これは少し分かりにくいかもしれません。もしグローバルの user エントリ 権限許可が、リクエストされたオペレーションには不十分だと最初に分かった際、 サーバーがこれらの権限を database-, table-, column-固有の権限の 後に、なぜ、追加してしまうのか。 その理由は、リクエストが1個以上の権限を要求するだろうということです。 例えば、もしあなたが INSERT ... SELECT 構文を実行するなら、 あなたには INSERT と SELECT 権限が必要です。 あなたの権限が、 user テーブルエントリで一つの権限が許可され、 db テーブルで、そのほかの権限が許可されていたとします。 この場合、あなたは、そのリクエストを実行するために、必要な権限を持っています。 しかし、サーバーはどちらのテーブル、それ単体からでは、権限を得ることが出来ません。 権限は、両方のエントリーを合わせなくてはならないのです。

      host テーブルは ``安全な'' ホストのリストを維持するために使用できます。

      TcX では、host テーブルにはローカルネット上の全てのホストが登録されています。 これらのホストは全ての権限が許可されています。

      逆に host table で安全ではないホストを指定することもできます。 public.your.domain というマシンが安全ではない、公開されている場所にあるとします。 その場合以下のようにして、その公開マシン以外のネットワーク上のホストに対して、 アクセスを許可することができます： 

      +--------------------+----+-
| Host               | Db | ...
+--------------------+----+-
| public.your.domain | %  | ... (all privileges set to 'N')
| %.your.domain      | %  | ... (all privileges set to 'Y')
+--------------------+----+-

      権限のテーブル設定は、あなたの思い通りに許可が得られるのか、 常に(mysqlaccess等を使用して)チェックすべきです。

      4.2.11 何故 Access denied エラーになるのか

      もし、MySQL サーバーに接続しようとして Access denied エラーに 遭遇してしまったら、以下に記すことが問題の解決のための指標となるでしょう:

      • MySQL をインストールした後に、スクリプト mysql_install_db を実行して 許可テーブルを初期化しましたか？ していなければ実行してください。 「4.3.4 MySQL 権限許可の初期設定」節参照 権限許可のテーブルが初期化されているかを試すには以下のようにします： 
        shell> mysql -u root test
        The server should let you connect without error. You should also make sure you have a file `user.MYD' in the MySQL database directory. Ordinarily, this is `PATH/var/mysql/user.MYD', where PATH is the pathname to the MySQL installation root.
      • After a fresh installation, you should connect to the server and set up your users and their access permissions: 
        shell> mysql -u root mysql
        初期状態では、MySQL に root ユーザーをパスワードなしで登録しているので、 問題なく接続できるはずです。 しかしこれはセキュリティ上危険な状態なので、 他の MySQL ユーザーを登録している時に、 root のパスワードを設定しておいてください。 もし root で接続しようとして以下のエラーが出た場合： 
        Access denied for user: '@unknown' to database mysql
        これは user テーブルに、 User フィールド = root かつ mysqld がリゾルブできなかったホスト名で、クライアントが登録されていないからです。 この場合、 `/etc/hosts' ファイルあるいは `\windows\hosts' ファイルを編集して ホスト名を追加し、--skip-grant-tables オプションでサーバーをリスタートします。
      • 次のようなエラーが出た場合: 
        shell> mysqladmin -u root -pxxxx ver
Access denied for user: 'root@localhost' (Using password: YES)
        これは間違ったパスワードを使用したことを意味します。 「4.3.7 パスワードの設定法」節参照. root のパスワードを忘れた場合、mysqld を --skip-grant-tables で再起動して、パスワードを変更することができま す。 「A.4.2 忘れたパスワードをリセットする」節参照. パスワードを指定してないのに、上のエラーがでた場合は、my.ini ファイ ルに間違ったパスワードがあることを意味します。 「4.1.2 `my.cnf' オプションファイル」節参照. このオ プションファイルは、次のように --no-defaults オプションで回避できま す: 
        shell> mysqladmin --no-defaults -u root ver
      • もしバージョン 3.22.11 より前の MySQL から バージョン 3.22.11 以上にバージョンアップしたなら、 mysql_fix_privilege_tables スクリプトを実行しましたか？ 実行していないなら、このエラーになります。 許可テーブルの構造が MySQL バージョン 3.22.11 から変更され、 GRANT 構文が機能しています。
      • もしあなたの権限がセッションの途中で変更されたように思ったなら、それは スーパーユーザーが権限を変えたのかも知れません。許可テーブルの再読み込みは 新しいクライアントの接続から反映されますが、すでに接続している場合でも 「4.3.3 いつ権限の変更が反映されるか」節. に示す条件下では影響を受けます。
      • もしあなたのパスワードが働かないのであれば、 INSERT, UPDATE, SET PASSWORD 構文でパスワードを設定するとき PASSWORD() 関数を使用しなければならないことを思い出してください。 しかし PASSWORD() 関数は、GRANT ... INDENTIFIED BY 構文や mysqladmin password コマンドでは不要です。 「4.3.7 パスワードの設定法」節参照.
      • localhost はローカルのホスト名です。 もしクライアントがホストを指定せずに接続してきた場合、localhost がデフォルトで使用されます。 しかし、 MIT-pthreads を使用している場合、localhost への接続は失敗します。 (localhost への接続は、Unixソケットを使用しますが、 MySQL 3.23.27 未満では MIT-pthreads が ソケット接続をサポートしていないためです。) この問題が起きるシステムでは、サーバー名を指定するために --host オプションを使用すべきです。 これは TCP/IP 接続を使用して mysqld サーバーに接続します。 この場合、user テーブルに、サーバーの実ホスト名を登録しておかなくてはなりません。 (これはクライアントプログラムをサーバーと同じホスト上で動かしている場合真となります) 例えば、Using password: NO を含むエラーメッセージを得た場合、これは パスワードなしでログインしようとしたことを意味します。
      • mysql -u user_name db_name を使用してデータベースに接続しているときに Access denied エラーが発生した場合、user テーブルの設定違いが考えられます。 mysql -u root mysql を実行し、以下の SQL 文を試してください： 
        mysql> SELECT * FROM user;
        Host と User にあなたのコンピュータ名と MySQL ユーザー名にマッチする登録がなされていなければなりません。
      • Access denied エラーは、どのユーザーで接続してきたか、 どのホストから接続しようとしているか、パスワードを使用しているのかをメッセージに出力します。 通常、エラーになっているホスト名とユーザー名がマッチするエントリが user テーブルに一つはなければなりません。 For example if you get an error message that contains Using password: NO, this means that you tried to login without an password.
      • 他のホストから MySQL サーバーに接続を試みた時に以下のエラーが出た場合、 user テーブルにあなたがアクセスしているホストにマッチする行がありません： 
        Host ... is not allowed to connect to this MySQL server
        mysql コマンドをサーバーのホスト上で使用して、 user, db, host テーブルに接続しようとしている ユーザー名／ホスト名 を加えて、mysqladmin flush-privileges を 実行すれば解決できるでしょう。 もしサーバーが MySQL バージョン 3.22 ではなく、接続しようとしている ホストの IP もホスト名もわからない場合、 user テーブルの Host フィールドに '%' を設定し、 mysqld を --log オプションで再起動してください。 そしてクライアントホストから接続すれば、MySQL のログファイルに そのホストの情報が記録されているはずです。 それがわかれば、先に設定した user テーブルの Host フィールドの '%' を ログに記録されたホスト名に置き換えます。(しかしこれはシステムを危険にさらします) Linux 上でこのエラーの他の原因は、あなたの使用しているのと異なる glibc バー ジョンでコンパイルされた、バイナリ MySQL バージョンを使用している ことを意味します。この場合、あなたの OS/glibc をアップグレードするか、ソー ス MySQL バージョンをダウンロードしてコンパイルすべきです。ソース RPM は、通常コンパイルとインストールは簡単なので、これは大きな問題ではあり ません。
      • ホスト名で接続しようとしたのに、ホスト名が現れないか、ホスト名が IP でエラー メッセージが出る場合: 
        shell> mysqladmin -u root -pxxxx -h some-hostname ver
Access denied for user: 'root@' (Using password: YES)
        これは MySQL が IP をホスト名に解決しようとした時に何かエラーを得 たことを意味します。この場合、mysqladmin flush-hosts を実行して、内 部の DNS キャッシュをリセットできます。 「5.5.5 How MySQL uses DNS」節参照. いくつかの永久的な解決策は:
        • DNS サーバで何が間違っているのかを見つけ出し、それを修正する。
        • MySQL 権限テーブル中に、ホスト名の代わりに IP を記述する。
        • --skip-name-resolve で mysqld を起動する。
        • --skip-host-cache で mysqld を起動する。
        • 同じマシン上でサーバとクライアントを起動している場合、localhost に 接続する。
        • /etc/hosts にクライアントマシン名を書く。
      • mysql -u root test は動いたものの mysql -h your_hostname -u root test が Access denied を返した場合、 user テーブルに正しいホスト名が使用されていないと思われます。 user テーブルの Host フィールドにホスト名を確定できる形で指定していないか、 使用しているシステムのリゾルブが FQDN (or vice-versa) を返しているかだと思われます。 例えば、user テーブルに 'tcx' ホストの定義があったとして、 DNS が MySQL に 'tcx.subnet.se' をホスト名として返した場合、 これは動きません。 user テーブルの Host フィールドの値に、あなたのホストの IP 番号を加えてください。 (user テーブルの Host の値にワイルドカードを使用することができます。'tcx.%' のように。 しかしホスト名の値を `%' 文字で終わらせる設定は、安全ではなく、推奨されません)
      • もし mysql -u user_name test が動作し mysql -u user_name other_db_name が 動作しない場合は、db テーブルに other_db_name のエントリが 登録されていません。
      • mysql -u user_name db_name はサーバー上では動作するが、 mysql -u host_name -u user_name db_name がクライアントホスト上で動作しない場合、 user テーブルか db テーブルにクライアントホストの名前が登録されていません。
      • Access denied の原因がもし上記に当てはまらない場合は、 user テーブルから Host にワイルドカードを使用しているエントリを 全て消去してみてください。(`%' や `_' を含む値です) よくある間違いは、localhost に対して localhost と同じマシン上から の接続を許可すると考えて Host='%' と User='some user' を登録することです。 これは動きません。なぜなら、デフォルトの権限に Host='localhost' と User='' が含まれているからです。 Host の値が 'localhost' の場合、これは '%' よりも 具体的に指定されているので、localhost からの接続にはこちらの方が 使用されるのです！ 正しい指定の仕方は、二番目の登録として Host='localhost' と User='some_user' を追加するか、 あるいは、Host='localhost' と User='' を削除することです。
      • もし以下のエラーが出た場合 db か host テーブルに問題があるのかもしれません。： 
        Access to database denied
        もし db テーブルに Host フィールドが空の登録がある場合には、 host テーブル中に、db テーブルに登録されている ホストを明記した物が一つ以上あるかどうかを確認してください。 もし SELECT ... INTO OUTFILE や LOAD DATA INFILE SQL 文を 使用している時にこのエラーが出る場合、 user テーブルのあなたの登録に FILE 権限が 許可されていないと思われます。
      • クライアントプログラムは接続に際して、 設定ファイルで設定された値か環境変数の値を使用することに注意してください。 もしクライアントプログラムが誤った値を接続に使用しているようなら、 環境変数とホームディレクトリにある `.my.cnf' ファイルを確認してください。 もちろんシステムワイドの MySQL 設定ファイルも、パラメターが記述されていないか、 チェックしてみてください。 「4.1.2 `my.cnf' オプションファイル」節参照. もしクライアントをオプションなしで起動していて Access denied がでるなら、 オプションファイルに古いパスワードが書かれているか確認してください。 「4.1.2 `my.cnf' オプションファイル」節参照.
      • 権限テーブルを(INSERT または UPDATE ステートメントを使用して )直接変更する場合、あなたの変更は無視されたように見えます。サーバに権限テー ブルを再読み込みさせるために、FLUSH PRIVILEGES ステートメントの発行 か、mysqladmin flush-privileges コマンドの実行の必要があることを忘 れないでください。そうでないと、あなたの変更は次回のサーバ再起動まで効果が ありません。UPDATE コマンドで root パスワードを設定後、権限 をフラッシュするまでそれを指定する必要がありません。サーバはまだパスワード を変更したことを知らないからです！
      • Perl, PHP, Python, ODBC プログラムでアクセスの問題があった場合、 mysql -u user_name db_name または mysql -u user_name -pyour_pass db_name でサーバへの接続を試してください。mysql クライ アントを使用して接続できれば、アクセス権でなく、あなたのプログラムに問題が あります。(-p とパスワードの間に空白がないことに注意してください; パスワードを指定するのに、--password=your_pass 構文も使用できます。 単に -p オプションを使用すると、MySQL はパスワードの入力を 求めます。)
      • テストのために、mysqld デーモンを --skip-grant-tables オプショ ン付きで開始してください。MySQL 権限テーブルを変更し、あなたの変 更が望む効果があるかどうかのチェックに、mysqlaccess スクリプトを使 用できます。あなたの変更が満足できた時に、mysqladmin flush-privileges を実行し、mysqld サーバに新しい権限テーブルを使用 して開始するように伝えてください。注意: 権限テーブルのリロードは --skip-grant-tables オプションを上書きします。これは、サーバを落と して再起動することなしに、権限テーブルの使用を始めるようにサーバに伝えるこ とができます。
      • もし全て失敗するなら、mysqld デーモンをデバッグオプションで起動してください。 例えば、--debug=d,general,query。これはコネクションに試みたホストやユーザーの情報、 また実行したコマンドを表示します。 「E.1.2 Creating Trace Files」節参照.
      • もし MySQL の権限許可についてその他の問題が起こり、 メーリング・リストに問題をポストしなくてはいけないと感じれば、 いつも MySQL 許可テーブルのダンプを提供して下さい。 mysqldump mysql コマンドでダンプできます。 いつものように、 mysqlbug スクリプトでポストしてください。 「1.6.1.3 バグや問題を報告する方法」節参照. ときには、 mysqldump を実行するために、 mysqld を --skip-grant-tables オプションで実行しないと いけないかもしれません。

      4.3 MySQL User Account Management

      4.3.1 GRANT と REVOKE 構文

      GRANT priv_type [(column_list)] [, priv_type [(column_list)] ...]
    ON {tbl_name | * | *.* | db_name.*}
    TO user_name [IDENTIFIED BY [PASSWORD] 'password']
        [, user_name [IDENTIFIED BY 'password'] ...]
    [REQUIRE
        NONE |
    	[{SSL| X509}]
	[CIPHER cipher [AND]]
	[ISSUER issuer [AND]]
	[SUBJECT subject]]
    [WITH [GRANT OPTION | MAX_QUERIES_PER_HOUR # |
                          MAX_UPDATES_PER_HOUR # |
                          MAX_CONNECTIONS_PER_HOUR #]]

REVOKE priv_type [(column_list)] [, priv_type [(column_list)] ...]
    ON {tbl_name | * | *.* | db_name.*}
    FROM user_name [, user_name ...]

バージョン 4.0 以上:
    REQUIRE
    	[{SSL| X509}]
	[CIPHER cipher [AND]]
	[ISSUER issuer [AND]]
	[SUBJECT subject]

バージョン 4.0.2以上:
    MAX_QUERIES_PER_HOUR=# | MAX_UPDATES_PER_HOUR=# | MAX_CONNECTIONS_PER_HOUR=#

      GRANT は MySQL 3.22.11 以上で実装されています; 前の MySQL バージョンでは、GRANT ステートメントは何も行ないません。

      GRANT と REVOKE コマンドセットの主な目的は、システム管理者 がユーザを生成すること、MySQL ユーザに次の４つの権限レベルの権 利を与えたり取り消すことをできるようにすることです:

      Global レベル
      Global 権限は与えられたサーバ上の全てのデータベースに適用します。これらの権限は mysql.user テーブル内に格納されます。
      Database レベル
      Database 権限は与えられたデータベース内の全てのテーブルに適用します。こ れらの権限は mysql.db テーブルと mysql.host テーブル内に格納されます。
      Table レベル
      Table 権限は与えられたテーブル内の全てのフィールドに適用します。これらの権限は mysql.tables_priv テーブル内に格納されます。
      Column レベル
      Column 権限は与えられたテーブル内の一つのフィールドに適用します。これらの権限は mysql.columns_priv テーブル内に格納されます。

      If you give a grant for a users that doesn't exists, that user is created. For examples of how GRANT works, see 「4.3.5 新しいユーザを MySQL へ追加」節.

      GRANT と REVOKE ステートメントにおいて priv_type には 以下が指定できます:

      ALL [PRIVILEGES] Sets all simple privileges except WITH GRANT OPTION
      ALTER Allows usage of ALTER TABLE
      CREATE Allows usage of CREATE TABLE
      CREATE TEMPORARY TABLES Allows usage of CREATE TEMPORARY TABLE
      DELETE Allows usage of DELETE
      DROP Allows usage of DROP TABLE.
      EXECUTE Allows the user to run stored procedures (for MySQL 5.0)
      FILE Allows usage of SELECT ... INTO OUTFILE and LOAD DATA INFILE.
      INDEX Allows usage of CREATE INDEX and DROP INDEX
      INSERT Allows usage of INSERT
      LOCK TABLES Allows usage of LOCK TABLES on tables for which one has the SELECT privilege.
      PROCESS Allows usage of SHOW FULL PROCESSLIST
      REFERENCES For the future
      RELOAD Allows usage of FLUSH
      REPLICATION CLIENT Gives the right to the user to ask where the slaves/masters are.
      REPLICATION SLAVE Needed for the replication slaves (to read binlogs from master).
      SELECT Allows usage of SELECT
      SHOW DATABASES SHOW DATABASES shows all databases.
      SHUTDOWN Allows usage of mysqladmin shutdown
      SUPER Allows one connect (once) even if max_connections is reached and execute commands CHANGE MASTER, KILL thread, mysqladmin debug, PURGE MASTER LOGS and SET GLOBAL
      UPDATE Allows usage of UPDATE
      USAGE Synonym for ``no privileges.''
      GRANT OPTION Synonym for WITH GRANT OPTION

      USAGE は ``no privileges'' と同義です. これはなんの権限も持たないユーザーを作る場合に使用します.

      The privileges CREATE TEMPORARY TABLES, EXECUTE, LOCK TABLES, REPLICATION ..., SHOW DATABASES and SUPER are new for in version 4.0.2. To use these new privileges after upgrading to 4.0.2, you have to run the mysql_fix_privilege_tables script.

      In older MySQL versions(4.0.2未満), the PROCESS privilege gives the same rights as the new SUPER privilege.

      ユーザーから GRANT 権限を取り除くには、GRANT OPTION オプションの値に priv_type を指定します： 

      mysql> REVOKE GRANT OPTION ON ... FROM ...;

      テーブルに対する許可のために指定できる priv_type は次のフィールドだけです： SELECT,INSERT, UPDATE, DELETE, CREATE, DROP, GRANT OPTION, INDEX, ALTER.

      フィールドに対する許可のために指定できる priv_type は次のフィールドだけです (これは column_list 節を使用する場合に適用されます)： SELECT, INSERT, UPDATE.

      ON *.* を使用してグローバル権限を設定できます。 ON db_name.* を使用してデータベース権限を設定できます。ON * を 指定すると、現在のデータベースの権限を設定できます。 (警告： 現在のデータベースを持たない状態で ON * を指定した場合、 global 権限に影響します！)

      Please note: the `_' and `%' wildcards are allowed when specifying database names in GRANT commands. This means that if you wish to use for instance a `_' character as part of a database name, you should specify it as `\_' in the GRANT command, to prevent the user from being able to access additional databases matching the wildcard pattern, e.g., GRANT ... ON `foo\_bar`.* TO ....

      ユーザへの権利の供与を他のホストから適応するために、MySQL は user_name の値を user@host の形で書けるようにしています。 特殊文字(`%' のような)で user_name の値を指定したい場合、 ユーザやホスト名をクォートできます; (例えば 'test-user'@'test-hostname')。

      ホスト名にワイルドカードを使用できます。例えば、user@'%.loc.gov' は loc.gov ドメインの全てのホストの user を与え、 user@'144.155.166.%' は 144.155.166 クラスCサブネットの あらゆるホストの user となります。

      単に user と書くと user@"%" と同じです.

      MySQL doesn't support wildcards in user names. Anonymous users are defined by inserting entries with User='' into the mysql.user table or creating an user with an empty name with the GRANT command.

      注意： もし匿名ユーザーからの MySQL サーバーへの接続を 許す場合(デフォルトです)、全てのローカルユーザー username@localhost を加えるべきです。 なぜなら、匿名ユーザーは同じマシンから MySQL サーバーに入ろうとした場合に 使用されるからです！ (匿名ユーザーは mysql.user ユーザーテーブルに、 User='' として登録されています。)

      これを確認するには、以下のようにします： 

      mysql> SELECT Host,User FROM mysql.user WHERE User='';

      さしあたり, GRANT はホスト名、テーブル名、データベース名、フィールド名に 最大60文字まで使用できます。ユーザー名は最大16文字までです。

      テーブル/フィールドの権限は global(ユーザとデータベース)権限と GRANT 権限と OR されます。例えば、ユーザが mysql.user テーブル内の global SELECT 権限を持っている場合、 これはデータベースやテーブル/フィールドレベル内のエントリでは拒否できません。

      フィールドに対する権限は次のように計算できます: 

      global privileges
OR (database privileges AND host privileges)
OR table privileges
OR column privileges

      多くの場合、異なる権限レベルの一つでユーザに権利を与えるので、人生は通常 上述のようには複雑ではありません。 アクセス権限のチェックの詳細は→ 「4.2 General Security Issues and the MySQL Access Privilege System」節.

      ユーザとホスト名の組が存在しない場合、エントリは mysql.user テー ブルに追加され、DELETE コマンドで削除されるまでそこに残ります。 いうならば GRANT は user テーブルの登録を作りますが、 REVOKE はそれらを削除できません; そうするには DELETE を使用しなくてはなりません。

      MySQL バージョン 3.22.12 以上では、 新しいユーザーが作成された場合、あるいは、あなたがグローバルな権限を許可されている場合、 ユーザーのパスワードは IDENTIFIED BY 節を使用して設定できます。 すでにユーザーにパスワードがある場合、新しく設定されたパスワードに置き換えられます。

      If you don't want to send the password in clear text you can use the PASSWORD option followed by a scrambled password from SQL function PASSWORD() or the C API function make_scrambled_password(char *to, const char *password).

      警告： もし新しいユーザーを作っても IDENTIFIED BY 節を指定しなければ、 そのユーザーはノーパスワードです。 これは危険です。

      パスワードは SET PASSWORD コマンドでも設定できます。 「5.5.6 SET 構文」節参照.

      データベースに権限を付与 する場合、mysql.db テーブル内の エントリは必要な場合に生成されます。全てのデータベース権限が REVOKE で削除された時、このエントリは削除されます。

      ユーザがテーブルに何も権限を持っていない場合、テーブルの一覧要求時(例え ば、SHOW TABLES ステートメントで)には、テーブルは現れません。

      WITH GRANT OPTION 節は、他のユーザーに、自分が持っている権限を与えることができます。 GRANT 権限を他に与える場合は注意してください。 あなたと許可を与えるユーザーが違う権限を持っている場合、 与えられる権限の許可は、二つを合わせた物になります！

      MAX_QUERIES_PER_HOUR #, MAX_UPDATES_PER_HOUR # and MAX_CONNECTIONS_PER_HOUR # are new in MySQL version 4.0.2. These options limit the number of queries/updates and logins the user can do during one hour. If # is 0 (default), then this means that there are no limitations for that user. 「4.3.6 Limiting user resources」節参照. Note: to specify any of these options for an existing user without adding other additional privileges, use GRANT USAGE ... WITH MAX_....

      自分自身が持っていない権限を他のユーザーに与えることはできません； GRANT 権限はあなたが所有する権限の許可だけを与えることができます。

      Be aware that when you grant a user the GRANT privilege at a particular privilege level, any privileges the user already possesses (or is given in the future!) at that level are also grantable by that user. あなたがデータベースに対する INSERT 許可をあるユーザーに与えたと仮定します。 もし、データベースに対する SELECT 権限を与えたり、 WITH GRANT OPTION を行うと、ユーザーは SELECT 権限だけでなく INSERT も得ることになります。 もし UPDATE 権限をユーザーに与えると、そのユーザーは INSERT, SELECT, UPDATE が可能です。

      ALTER 権限を一般ユーザに与えるべきではありません。この場合 ユーザはテーブルをリネームでき、この方法で権限を回ることを試みることがで きます！

      注意：もし table/column 権限を一人のユーザーにだけ与えた場合、 MySQL は全てのユーザーに対してテーブルとフィールドの承認権限を検討します。 これは MySQL を少し遅くします。

      mysqld 開始時、全ての権限はメモリに読み込まれます。データベース、 テーブル、フィールド権限は一度効果を得ます。ユーザレベル権限はユーザ再接続時に 効果を得ます。 これらの許可テーブルを GRANT や REVOKE を使って変更しても サーバーにはすぐに反映されません。 もしこれらの許可テーブルを手動で変更した場合(INSERT, UPDATE, 等で変更した場合)、 FLUSH PRIVILEGES 構文を実行するか、mysqladmin flush-privileges を実行して サーバーに許可テーブルの再読み込みを行わせなくてはなりません。 「4.3.3 いつ権限の変更が反映されるか」節参照.

      The biggest differences between the ANSI SQL and MySQL versions of GRANT are:

      • In MySQL privileges are given for an username + hostname combination and not only for an username.
      • ANSI SQL はグローバルとデータベースレベル承認を持たず、ANSI SQL は MySQL がサポートする全ての権限をサポートしません。 MySQL doesn't support the ANSI SQL TRIGGER or UNDER privileges.
      • ANSI SQL privileges are structured in a hierarchal manner. If you remove an user, all privileges the user has granted are revoked. In MySQL the granted privileges are not automatically revoked, but you have to revoke these yourself if needed.
      • In MySQL, if you have the INSERT privilege on only some of the columns in a table, you can execute INSERT statements on the table; the columns for which you don't have the INSERT privilege will be set to their default values. ANSI SQL requires you to have the INSERT privilege on all columns.
      • ANSI SQL でテーブルを破棄する時、そのテーブルの全ての権限は破棄さ れます。ANSI SQL で権限を取り消す場合、この権限に基づいて承認され た全ての権限も取り消されます。MySQL では、全ての権限は明示的な REVOKE コマンドまたは MySQL 権限テーブルの操作によっての み破棄されます。

      For a description of using REQUIRE, see 「4.3.9 Using Secure Connections」節.

      4.3.2 MySQL ユーザ名とパスワード

      MySQL によって使用されるユーザー名とパスワードの使用のされ方と、 Unix, Windows で使用される方法とは、いくつか異なる点があります。

      • MySQL データベースのアクセス認証に使用するユーザー名は、 Unix のログインユーザやWindowsのユーザー名で行うことはありません(一致していません)。 利便性をはかるため、多くの MySQL クライアントは現在のログインしているユーザ名を MySQLのユーザー名としてログインを試みます。 しかしこれは -u か --user スイッチで変更できます。 これは、全てのユーザに対しパスワードを設定しておかないと、 全くデータベースを安全にできないことを意味します。 もしパスワードを全ユーザーに設定しておかないと、そのユーザー名で認証なしにサーバーに接続できます。
      • MySQL のユーザー名は 16文字まで(英数半角)使用できます。 Unixはだいたい8文字ですが。(8文字をこえるシステムもある)
      • MySQL ユーザーのパスワードは、Unix のパスワードと違います。 よって、それらのマシン上で Unix のログインパスワードと データベースのパスワードは同じにする必要はありません。
      • MySQL は Unix のログインパスワードとは全く違う、 独自の暗号化されたパスワードだけを使用します。 PASSWORD() と ENCRYPT() 関数の説明を参照 → 「6.3.6.2 その他の関数」節. 注意: パスワードが '暗号化' されて格納されていても、あなたの '暗号化' され たパスワードを知ることで、MySQL サーバに接続するのには十分です！ From version 4.1, MySQL employs a different password and login mechanism that is secure even if TCP/IP packets are sniffed and/or the mysql database is captured.

      MySQL ユーザーと彼らの権限は通常 GRANT コマンドで作成されます。 「4.3.1 GRANT と REVOKE 構文」節参照.

      MySQL サーバにコマンドラインクライアントでログインする時、 --password=your-password でパスワードを指定すべきです。 「4.2.8 MySQL サーバーに接続」節参照. 

      mysql --user=monty --password=guess database_name

      クライアントにパスワードをプロンプトして欲しければ、引数なしで --password を使用すべきです。 

      mysql --user=monty --password database_name

      または次の短い形式: 

      mysql -u monty -p database_name

      注意: 最後の例でのパスワードは 'database_name' では ありません。

      パスワードを供給するために -p オプションを使用したい場合、次のようなことを 行なうべきです: 

      mysql -u monty -pguess database_name

      いくつかのシステムでは、MySQL がパスワードをプロンプトするために 使用するライブラリ呼び出しは、自動的にパスワードを 8文字にカットします。内 部的に MySQL はパスワード長に何の制限もありません。

      4.3.3 いつ権限の変更が反映されるか

      mysqld の起動時、全ての許可テーブルはメモリーに読み込まれ、 この時点で有効になります。

      GRANT, REVOKE, SET PASSWORD を使用して許可テーブルを 変更した場合、直にサーバに通知されます。

      もし手動で許可テーブルを変更した場合(INSERT, UPDATE などで)、 FLUSH PRIVILEGES 構文か mysqladmin flush-privileges コマンド か mysqladmin reload コマンドを実行して、 サーバーに許可テーブルの読み込みを指示しなければなりません。 そうしなければ、サーバーを再起動させるまで、変更は反映されません。 権限テーブルを手で変更して、権限のリロードを忘れた場合、変更が何も行なわれ ないように見えるのがなぜかと不思議に思うでしょう！

      サーバーが許可テーブルの変更を通知した場合、既に接続している クライアントは、以下のような影響を受けます：

      • テーブルとフィールドの許可の変更は、次のクライアントの要求から反映されます。
      • データベースに対する許可の変更は次の USE db_name コマンド以降から 有効になります。
      • グローバル権限とパスワードの変更は、次のクライアントの接続時から反映されます。

      4.3.4 MySQL 権限許可の初期設定

      MySQL インストール後、scripts/mysql_install_db を 実行して権限のアクセス許可を初期化します。 「2.3.1 素早いインストールの概要」節参照. mysql_install_db スクリプトは mysqld サーバーを起動し、 以下のように権限を初期化してテーブルに登録します：

      • MySQL root ユーザーはスーパーユーザーとして登録され、 全ての操作ができます。 localhostからしか接続できません。 注意: root のパスワードの初期値は空です。 全ての人が パスワードなしで root になれ、全ての権限許可を得ることができます。
      • 'test' あるいは 'test_' で名前がはじまっているデータベースに対して、 匿名ユーザーでもなんでもできるように許可が与えられます。 これは ローカルホストからの全てのユーザーは パスワード無しで接続ができ、 匿名ユーザーとして扱われるということです。
      • その他の要求は拒否されます。例えば、一般ユーザーは mysqladmin shutdown や mysqladmin processlist を実行できません。

      注意: デフォルトの権限は Windows では違います。 「2.6.2.3 Windows 上で MySQL を実行」節参照.

      初期インストールの状態ではかなりアクセスが解放されているので、 インストール後最初にすることは、MySQL root ユーザーにパスワードを設定することです。 以下のようにします(パスワードは PASSWORD() 関数を使用することをお忘れなく)： 

      shell> mysql -u root mysql
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_password');

      If you know what you are doing, you can also directly manipulate the privilege tables: 

      shell> mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD('new_password')
    ->     WHERE user='root';
mysql> FLUSH PRIVILEGES;

      password をセットする他の方法として、mysqladmin コマンドも使用できます： 

      shell> mysqladmin -u root password new_password

      mysql データベースに書き込み／更新アクセスのあるユーザだけが他のユーザのパ スワードを変更できます。すべての通常のユーザ(匿名ユーザ以外)は、上記のコマ ンドか、または SET PASSWORD=PASSWORD('new password') で、自分のパス ワードだけを変更できます。

      もし最初の方法で user テーブルのパスワードを直接更新したなら、 サーバーに許可テーブルの再読み込みを行わせなければなりません(FLUSH PRIVILEGES を使用して)。

      一度 root のパスワードを設定したなら、root でサーバーに接続する場合は 常にパスワードを与えなければなりません。

      追加設定やテストをしているためパスワードを入れたくない場合、 root パスワードをブランクのままにしておこうと考えるかも知れませんが、 実稼働させる前には必ず設定してください。

      どのようにデフォルトの権限を設定しているか、scripts/mysql_install_db 見てみてください。 これは他のユーザーを設定するときに使えるでしょう。

      もし権限の初期状態を違うものにして初期化したいなら、 mysql_install_db を実行する前に編集してもよいでしょう。

      もしテーブルを完全に作り直したいなら、mysql データベースのディレクトリに存在する 全ての `*.frm', `*.MYI', `*.MYD' ファイルを削除します。 (このディレクトリーはデータベースディレクトリーの下に mysql という名前で存在します。 mysqld --help とすればデータベースのディレクトリーが表示されます。) そして好みの許可状態に mysql_install_db を編集してから実行します。

      注意: MySQL 3.22.10 以前のバージョンでは, `*.frm' ファイルを消してはいけません. もしうっかり消してしまった場合、 mysql_install_db を実行する前に、 MySQL 配布からコピーしなおさ なくてはなりません。

      4.3.5 新しいユーザを MySQL へ追加

      ユーザーは２つの違った方法で追加できます： GRANT 構文を使用して行う方法と、 MySQL の許可テーブルを直接操作する方法とです。 The preferred method is to use GRANT statements, because they are more concise and less error-prone. 「4.3.1 GRANT と REVOKE 構文」節参照.

      phpmyadmin のような、ユーザの作成と管理に使用できる contribute され たプログラムも多くあります。

      以下の例では、いかにして mysql クライアントを使用して新規にユーザーを登録するかを示します。 以下の例では、権限は前節で述べたデフォルト値になっているとします。 よって変更を行うためには、あなたは mysqld が走っているマシン上にログインしていなくてはなりませんし、 かつ、MySQL root ユーザーで接続していなければなりません。 さらに MySQL root ユーザーには mysql データベースに対して INSERT 権限を持ち、 RELOAD, PROCESS のアドミニストレーター権限を持っていなければなりません。 もし root ユーザーのパスワードを変えていたならば、 mysql コマンドにパスワード指定を与えなくてはなりません。

      You can add new users by issuing GRANT statements: 

      shell> mysql --user=root mysql
mysql> GRANT ALL PRIVILEGES ON *.* TO monty@localhost
    ->     IDENTIFIED BY 'some_pass' WITH GRANT OPTION;
mysql> GRANT ALL PRIVILEGES ON *.* TO monty@"%"
    ->     IDENTIFIED BY 'some_pass' WITH GRANT OPTION;
mysql> GRANT RELOAD,PROCESS ON *.* TO admin@localhost;
mysql> GRANT USAGE ON *.* TO dummy@localhost;

      これら GRANT 構文では3つの新しいユーザを作ります:

      monty
      どこからでもサーバーに接続できる完全なスーパーユーザ。 しかし、MySQL を使用する時にはパスワード 'some_pass' を 使用する必要があります。 monty@localhost と monty@"%" の両方に GRANT 構文を 発行しなくてはならない事に注意してください。 もし localhost からの許可をした登録がないと、localhost から接続した時、 mysql_install_db が自動で作成した localhost への匿名ユーザーが優先されます。 なぜなら、 Host フィールドの値が(ブランクやワールドカード以外に)明記されており、 許可登録が MySQL 内部でソートされる時に順番が上にソートされるからです。
      admin
      localhost からパスワードなしで接続できますが、reload, process の使用だけが許されます。 これは、mysqladmin reload, mysqladmin refresh, mysqladmin flush-* そして mysqladmin processlist コマンドの実行がこのユーザーに許可されます。 データベースへのアクセスは許可されていません。 しかしこれは後でテーブル GRANT 構文を発行すれば、 個々のデータベースへのアクセス権限が設定できます。
      dummy
      パスワードなしで localhost からのみ、接続できるユーザー。 グローバルな権限は全て 'N' に設定されます。 USAGE 権限は権限無しユーザーの設定を許可する事になります。 これは、特定データーベースに対しての許可を後から与える事を想定しています。

      同じアクセス許可を INSERT 構文を使用して直接設定できます。 サーバーに許可テーブルの再読み込みを指示します： 

      shell> mysql --user=root mysql
mysql> INSERT INTO user VALUES('localhost','monty',PASSWORD('some_pass'),
    ->          'Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
mysql> INSERT INTO user VALUES('%','monty',PASSWORD('some_pass'),
    ->          'Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
mysql> INSERT INTO user SET Host='localhost',User='admin',
    ->           Reload_priv='Y', Process_priv='Y';
mysql> INSERT INTO user (Host,User,Password)
    ->                  VALUES('localhost','dummy','');
mysql> FLUSH PRIVILEGES;

      MySQL のバージョンにより、上の 'Y' の数が違う事に注意してください。 (3.22.11 以前のバージョンでは項目数が少なくなります). admin ユーザーの登録で使用している INSERT の拡張は バージョン 3.22.11 以上で可能です。 (訳注: version 4.0 以上で openssl を使用する場合、この数が変わります)

      スーパーユーザーを定義するためには、user テーブルの許可フィールドを 'Y' にするだけでかまいません。 db や host テーブルに登録は必要無いのです。

      user テーブルの許可フィールドは最後の INSERT 文で(dummy ユーザーのために) は設定されていません。これらのフィールドはデフォルト値の 'N' になります。 これは GRANT USAGE が行うのと同じものです。

      以下は、localhost, server.domain, whitehouse.gov から接続が可能な custom ユーザーの追加例です。 custom ユーザーは bankaccount データーベースには localhost からの接続のみを許可され、 expenses データベースには whitehouse.gov からのみ接続が許可され、 customer データベースには全てのホストから接続できます。 custom ユーザーは、 stupid というパスワードを全てのホストで使用したいとします。

      このユーザーの許可を GRANT 構文で定義するには、以下のようにします： 

      shell> mysql --user=root mysql
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP
    ->     ON bankaccount.*
    ->     TO custom@localhost
    ->     IDENTIFIED BY 'stupid';
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP
    ->     ON expenses.*
    ->     TO custom@whitehouse.gov
    ->     IDENTIFIED BY 'stupid';
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP
    ->     ON customer.*
    ->     TO custom@'%'
    ->     IDENTIFIED BY 'stupid';

      The reason that we do to grant statements for the user 'custom' is that we want the give the user access to MySQL both from the local machine with Unix sockets and from the remote machine 'whitehouse.gov' over TCP/IP.

      許可テーブルを直接変更してこのユーザーの権限を設定するにはいかのようにします (FLUSH PRIVILEGES を最後に実行している事に注意)： 

      shell> mysql --user=root mysql
mysql> INSERT INTO user (Host,User,Password)
    -> VALUES('localhost','custom',PASSWORD('stupid'));
mysql> INSERT INTO user (Host,User,Password)
    -> VALUES('server.domain','custom',PASSWORD('stupid'));
mysql> INSERT INTO user (Host,User,Password)
    -> VALUES('whitehouse.gov','custom',PASSWORD('stupid'));
mysql> INSERT INTO db
    -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv,
    ->  Create_priv,Drop_priv)
    -> VALUES
    -> ('localhost','bankaccount','custom','Y','Y','Y','Y','Y','Y');
mysql> INSERT INTO db
    -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv,
    ->  Create_priv,Drop_priv)
    -> VALUES
    -> ('whitehouse.gov','expenses','custom','Y','Y','Y','Y','Y','Y');
mysql> INSERT INTO db
    -> (Host,Db,User,Select_priv,Insert_priv,Update_priv,Delete_priv,
    ->  Create_priv,Drop_priv)
    -> VALUES('%','customer','custom','Y','Y','Y','Y','Y','Y');
mysql> FLUSH PRIVILEGES;

      最初の３つの INSERT 文は、 custom ユーザーがそれぞれのホストから パスワードつきで接続できるように user テーブルに追加しています。 しかしここでは権限は１つも与えられていません(権限のデフォルト値は 'N' です)。 次の三つの INSERT 文は、bankaccount, expenses, customer データベースに対する該当ホストからのアクセス許可を custom ユーザーに与えるように、 db テーブルに追加しています。 許可テーブルが直接変更された場合、これらをサーバーに反映させるために、許可テーブルの 再読み込みを(FLUSH PRIVILEGESで) サーバーにつげなければなりません。

      もし、あるドメインの全てのマシンに接続を許可したい場合、 以下のように GRANT 構文を発行します： 

      mysql> GRANT ...
    ->     ON *.*
    ->     TO myusername@"%.mydomainname.com"
    ->     IDENTIFIED BY 'mypassword';

      許可テーブルを直接変更するには以下のようにします： 

      mysql> INSERT INTO user VALUES ('%.mydomainname.com', 'myusername',
    ->             PASSWORD('mypassword'),...);
mysql> FLUSH PRIVILEGES;

      4.3.6 Limiting user resources

      Starting from MySQL 4.0.2 one can limit certain resources per user.

      So far, the only available method of limiting usage of MySQL server resources has been setting the max_user_connections startup variable to a non-zero value. But this method is strictly global and does not allow for management of individual users, which could be of particular interest to Internet Service Providers.

      Therefore, management of three resources is introduced on the individual user level:

      • Number of all queries per hour: All commands that could be run by a user.
      • Number of all updates per hour: Any command that changes any table or database.
      • Number of connections made per hour: New connections opened per hour.

      A user in the aforementioned context is a single entry in the user table, which is uniquely identified by its user and host columns.

      All users are by default not limited in using the above resources, unless the limits are granted to them. These limits can be granted only via global GRANT (*.*), using this syntax: 

      GRANT ... WITH MAX_QUERIES_PER_HOUR N1
               MAX_UPDATES_PER_HOUR N2
               MAX_CONNECTIONS_PER_HOUR N3;

      One can specify any combination of the above resources. N1, N2 and N3 are integers and stands for count / hour.

      If user reaches any of the above limits withing one hour, his connection will be terminated or refused and the appropriate error message shall be issued.

      Current usage values for a particular user can be flushed (set to zero) by issuing a GRANT statement with any of the above clauses, including a GRANT statement with the current values.

      Also, current values for all users will be flushed if privileges are reloaded (in the server or using mysqladmin reload) or if the FLUSH USER_RESOURCES command is issued.

      The feature is enabled as soon as a single user is granted with any of the limiting GRANT clauses.

      As a prerequisite for enabling this feature, the user table in the mysql database must contain the additional columns, as defined in the table creation scripts mysql_install_db and mysql_install_db.sh in `scripts' subdirectory.

      4.3.7 パスワードの設定法

      多くの場合、ユーザ／パスワードを設定するために、GRANT を使用すべき です。以下は上級ユーザのためにだけあてはまります。 「4.3.1 GRANT と REVOKE 構文」節参照.

      前節の例で述べた、とても重要な基本原則： INSERT か UPDATE で空ではないパスワードを設定する場合、 暗号化するために PASSWORD() 関数を使用しなくてはなりません。 これは user テーブルはプレーンテキストでなく、暗号化されたパスワードであることを要求しているからです。 この原則を忘れてしまった場合、以下のようにしてパスワードをセットしてしまうかもしれません： 

      shell> mysql -u root mysql
mysql> INSERT INTO user (Host,User,Password)
    -> VALUES('%','jeffrey','biscuit');
mysql> FLUSH PRIVILEGES;

      これは user テーブルにプレーンテキストの 'biscuit' をパスワードとして登録してしまいます。 jeffrey ユーザーでこのパスワードを使用してサーバーに接続しようとすると、 mysql クライアントは暗号化したパスワードをサーバーに送ります。 サーバーは暗号化されたパスワード('biscuit' ではありません) と user テーブルに登録された値('biscuit') を比較します。 その結果、比較は失敗し、サーバーは接続を拒否します： 

      shell> mysql -u jeffrey -pbiscuit test
Access denied

      user テーブルに登録されるパスワードは暗号化されたものでなくてはなりません。 INSERT 構文は以下のようにして使用しなくてはなりません： 

      mysql> INSERT INTO user (Host,User,Password)
    -> VALUES('%','jeffrey',PASSWORD('biscuit'));

      SET PASSWORD 構文を使用する場合は、以下のように PASSWORD() 関数を使用しなくてはなりません： 

      mysql> SET PASSWORD FOR jeffrey@"%" = PASSWORD('biscuit');

      もし GRANT ... IDENTIFIED BY 構文や mysqladmin password コマンド でパスワードを設定した場合、PASSWORD() 関数は必要ありません。 両方とも、パスワードを暗号化してくれますので、 以下のように'biscuit'と与えます： 

      mysql> GRANT USAGE ON *.* TO jeffrey@"%" IDENTIFIED BY 'biscuit';

      or 

      shell> mysqladmin -u jeffrey password biscuit

      注意： PASSWORD() は UNIX のパスワードで使用されている暗号化と 違うことにも留意してください。 「4.3.2 MySQL ユーザ名とパスワード」節参照.

      4.3.8 パスワードを安全にする

      自分のパスワードを他人にさらけ出すのは勧められることではありません。 それぞれの方法に於ける危険度に応じ、以下に示す方法でクライアントプログラムに あなたのパスワードをあたえて走らせることができます：

      • 一般ユーザに mysql.user テーブルへのアクセスを与えてはいけません。 ユーザの暗号化されたパスワード知ることで、そのユーザとしてログインが可能に なります。パスワードは、使用される本当のパスワードを見ることができないよう に、スクランブルされているだけです(同じようなパスワードを他のアプリケーショ ンでたまたま使用する場合のため)。
      • -pyour_pass か --password=your_pass オプションをコマンドラインで使用します。 これは便利ですが安全ではありません。あなたのパスワードは (ps コマンドのような) システムの状態を見るコマンドにて見ることができます。 (MySQL クライアントは初期化過程においてコマンドラインの引数をゼロで上書きして 見せないようにしているのですが、瞬間ですが値が見えてしまうのです)
      • -p あるいは --password オプションを your_pass を与えないで使用します。 この場合、クライアントプログラムはターミナルを通じてパスワードの入力を促してきます: 
        shell> mysql -u user_name -p
Enter password: ********
        `*' 文字はパスワードを表しています。 これはコマンドラインにパスワードを指定するより安全です。他のユーザーには見えませんから。 しかしこのパスワードを毎回入れる方法は対話式のプログラムを実行する場合だけに使用できる手です。 もし非対話式のスクリプトからクライアントプログラムを起動したい場合、 パスワードを端末から入れる機会がありません。 On some systems, you may even find that the first line of your script is read and interpreted (incorrectly) as your password!
      • 設定ファイルにパスワードを書いておくこともできます。 例えば、自分のホームディレクトリーにある `.my.cnf' ファイルの [client] セクションに、以下のような形で書きます： 
        [client]
password=your_pass
        もし `.my.cnf' ファイルにパスワードを書いているなら、ファイルはグループや その他のユーザーが読み書きできないようにすべきです。ファイルのモードは 400 か 600 にします。 「4.1.2 `my.cnf' オプションファイル」節参照.
      • MYSQL_PWD 環境変数にパスワードを設定することもできます。しかしこの方法は きわめて危険であるので、使用すべきではありません。 ps のあるバージョンでは、実行中のプロセスの環境変数を表示するオプションがあります； もし MYSQL_PWD 環境変数にパスワードを設定していると全てべたで見れます。 このバージョンの ps を持っていないシステムだとしても、プロセスの環境変数を調べる 方法がないとはいえないので、この方法はあまりいい方法ではありません。 「F Environment Variables」節参照.

      まとめると、より安全な方法は、 パスワードプロンプトを返すクライアントプログラムを実行するか、 適切なパーミッションをかけた `.my.cnf' ファイルにパスワードを書くか です。

      4.3.9 Using Secure Connections

      4.3.9.1 Basics

      Beginning with version 4.0.0, MySQL has support for SSL encrypted connections. To understand how MySQL uses SSL, it's necessary to explain some basic SSL and X509 concepts. People who are already familiar with them can skip this part.

      By default, MySQL uses unencrypted connections between the client and the server. This means that someone could watch all your traffic and look at the data being sent or received. They could even change the data while it is in transit between client and server. Sometimes you need to move information over public networks in a secure fashion; in such cases, using an unencrypted connection is unacceptable.

      SSL is a protocol that uses different encryption algorithms to ensure that data received over a public network can be trusted. It has mechanisms to detect any change, loss or replay of data. SSL also incorporates algorithms to recognise and provide identity verification using the X509 standard.

      Encryption is the way to make any kind of data unreadable. In fact, today's practice requires many additional security elements from encryption algorithms. They should resist many kind of known attacks like just messing with the order of encrypted messages or replaying data twice.

      X509 is a standard that makes it possible to identify someone on the Internet. It is most commonly used in e-commerce applications. In basic terms, there should be some company (called a ``Certificate Authority'') that assigns electronic certificates to anyone who needs them. Certificates rely on asymmetric encryption algorithms that have two encryption keys (a public key and a secret key). A certificate owner can prove his identity by showing his certificate to other party. A certificate consists of its owner's public key. Any data encrypted with this public key can be decrypted only using the corresponding secret key, which is held by the owner of the certificate.

      MySQL doesn't use encrypted connections by default, because doing so would make the client/server protocol much slower. Any kind of additional functionality requires the computer to do additional work and encrypting data is a CPU-intensive operation that requires time and can delay MySQL main tasks. By default MySQL is tuned to be fast as possible.

      If you need more information about SSL, X509, or encryption, you should use your favourite Internet search engine and search for keywords in which you are interested.

      4.3.9.2 Requirements

      To get secure connections to work with MySQL you must do the following:

      1. OpenSSL ライブラリをインストール。 我々は openssl 0.9.6 でテストしました。 http://www.openssl.org/.
      2. --with-vio --with-openssl で MySQL をコンフィギャ.
      3. もしあなたが古い MySQL (4.0未満)をインストールしているなら、 mysql.user テーブルを update するべきです。 これは mysql_fix_privilege_tables スクリプトで可能です。 MySQL 4.0.0 以上ではこの作業が必要です。 ( 訳注: このスクリプトは、前のバージョンが 3.23 の場合、 mysql.user テーブル に ssl_type, ssl_cipher, x509_issuer, x509_subject フィールドを追加し、 mysql.* の全てのテーブルを ALTER TABLE .. TYPE=MyISAM で作成し直します。 実行前には、念のため、mysql データベースを mysqldump か 他の方法でバックアップしておきましょう。 )
      4. 実行中の mysqld が OpenSSL をサポートしている場合は、 SHOW VARIABLES LIKE 'have_openssl' が YES を返します。

      4.3.9.3 Setting Up SSL Certificates for MySQL

      Here is an example for setting up SSL certificates for MySQL: 

      DIR=`pwd`/openssl
PRIV=$DIR/private

mkdir $DIR $PRIV $DIR/newcerts
cp /usr/share/ssl/openssl.cnf $DIR
replace ./demoCA $DIR -- $DIR/openssl.cnf

# Create necessary files: $database, $serial and $new_certs_dir 
# directory (optional)

touch $DIR/index.txt
echo "01" > $DIR/serial

#
# Generation of Certificate Authority(CA)
#

openssl req -new -x509 -keyout $PRIV/cakey.pem -out $DIR/cacert.pem \
    -config $DIR/openssl.cnf

# Sample output:
# Using configuration from /home/monty/openssl/openssl.cnf
# Generating a 1024 bit RSA private key
# ................++++++
# .........++++++
# writing new private key to '/home/monty/openssl/private/cakey.pem'
# Enter PEM pass phrase:
# Verifying password - Enter PEM pass phrase:
# -----
# You are about to be asked to enter information that will be incorporated
# into your certificate request.
# What you are about to enter is what is called a Distinguished Name or a DN.
# There are quite a few fields but you can leave some blank
# For some fields there will be a default value,
# If you enter '.', the field will be left blank.
# -----
# Country Name (2 letter code) [AU]:FI
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB
# Organizational Unit Name (eg, section) []:
# Common Name (eg, YOUR name) []:MySQL admin
# Email Address []:

#
# Create server request and key
#
openssl req -new -keyout $DIR/server-key.pem -out \
    $DIR/server-req.pem -days 3600 -config $DIR/openssl.cnf

# Sample output:
# Using configuration from /home/monty/openssl/openssl.cnf
# Generating a 1024 bit RSA private key
# ..++++++
# ..........++++++
# writing new private key to '/home/monty/openssl/server-key.pem'
# Enter PEM pass phrase:
# Verifying password - Enter PEM pass phrase:
# -----
# You are about to be asked to enter information that will be incorporated
# into your certificate request.
# What you are about to enter is what is called a Distinguished Name or a DN.
# There are quite a few fields but you can leave some blank
# For some fields there will be a default value,
# If you enter '.', the field will be left blank.
# -----
# Country Name (2 letter code) [AU]:FI
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB
# Organizational Unit Name (eg, section) []:
# Common Name (eg, YOUR name) []:MySQL server
# Email Address []:
# 
# Please enter the following 'extra' attributes
# to be sent with your certificate request
# A challenge password []:
# An optional company name []:

#
# Remove the passphrase from the key (optional)
#

openssl rsa -in $DIR/server-key.pem -out $DIR/server-key.pem

#
# Sign server cert
#
openssl ca  -policy policy_anything -out $DIR/server-cert.pem \
    -config $DIR/openssl.cnf -infiles $DIR/server-req.pem

# Sample output:
# Using configuration from /home/monty/openssl/openssl.cnf
# Enter PEM pass phrase:
# Check that the request matches the signature
# Signature ok
# The Subjects Distinguished Name is as follows
# countryName           :PRINTABLE:'FI'
# organizationName      :PRINTABLE:'MySQL AB'
# commonName            :PRINTABLE:'MySQL admin'
# Certificate is to be certified until Sep 13 14:22:46 2003 GMT (365 days)
# Sign the certificate? [y/n]:y
# 
# 
# 1 out of 1 certificate requests certified, commit? [y/n]y
# Write out database with 1 new entries
# Data Base Updated

#
# Create client request and key
#
openssl req -new -keyout $DIR/client-key.pem -out \
    $DIR/client-req.pem -days 3600 -config $DIR/openssl.cnf

# Sample output:
# Using configuration from /home/monty/openssl/openssl.cnf
# Generating a 1024 bit RSA private key
# .....................................++++++
# .............................................++++++
# writing new private key to '/home/monty/openssl/client-key.pem'
# Enter PEM pass phrase:
# Verifying password - Enter PEM pass phrase:
# -----
# You are about to be asked to enter information that will be incorporated
# into your certificate request.
# What you are about to enter is what is called a Distinguished Name or a DN.
# There are quite a few fields but you can leave some blank
# For some fields there will be a default value,
# If you enter '.', the field will be left blank.
# -----
# Country Name (2 letter code) [AU]:FI
# State or Province Name (full name) [Some-State]:.
# Locality Name (eg, city) []:
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:MySQL AB
# Organizational Unit Name (eg, section) []:
# Common Name (eg, YOUR name) []:MySQL user
# Email Address []:
# 
# Please enter the following 'extra' attributes
# to be sent with your certificate request
# A challenge password []:
# An optional company name []:

#
# Remove a passphrase from the key (optional)
#
openssl rsa -in $DIR/client-key.pem -out $DIR/client-key.pem

#
# Sign client cert
#

openssl ca  -policy policy_anything -out $DIR/client-cert.pem \
    -config $DIR/openssl.cnf -infiles $DIR/client-req.pem

# Sample output:
# Using configuration from /home/monty/openssl/openssl.cnf
# Enter PEM pass phrase:
# Check that the request matches the signature
# Signature ok
# The Subjects Distinguished Name is as follows
# countryName           :PRINTABLE:'FI'
# organizationName      :PRINTABLE:'MySQL AB'
# commonName            :PRINTABLE:'MySQL user'
# Certificate is to be certified until Sep 13 16:45:17 2003 GMT (365 days)
# Sign the certificate? [y/n]:y
# 
# 
# 1 out of 1 certificate requests certified, commit? [y/n]y
# Write out database with 1 new entries
# Data Base Updated

#
# Create a my.cnf file that you can use to test the certificates
#

cnf=""
cnf="$cnf [client]"
cnf="$cnf ssl-ca=$DIR/cacert.pem"
cnf="$cnf ssl-cert=$DIR/client-cert.pem"
cnf="$cnf ssl-key=$DIR/client-key.pem"
cnf="$cnf [mysqld]"
cnf="$cnf ssl-ca=$DIR/cacert.pem"
cnf="$cnf ssl-cert=$DIR/server-cert.pem"
cnf="$cnf ssl-key=$DIR/server-key.pem"
echo $cnf | replace " " '
' > $DIR/my.cnf

#
# To test MySQL

mysqld --defaults-file=$DIR/my.cnf &

mysql --defaults-file=$DIR/my.cnf

      You can also test your setup by modifying the above `my.cnf' file to refer to the demo certificates in the mysql-source-dist/SSL direcory.

      4.3.9.4 GRANT オプション

      MySQL can check X509 certificate attributes in addition to the normal username/password scheme. All the usual options are still required (username, password, IP address mask, database/table name).

      There are different possibilities to limit connections:

      • SSL か X509 オプションが無い場合は、 もしユーザー名とパスワードが正しければ、 暗号化と非暗号化の全ての接続が許可されます。
      • REQUIRE SSL オプションは、サーバーに対して、 SSL 接続のみを許可します。 もし、非SSL接続を許可する ACL (アクセス・コントロール・リスト)の レコードが存在する場合、このオプションは除かれることに注意してください。 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret" REQUIRE SSL;
      • REQUIRE X509 は、クライアントが有効な証明書を持っていることを 意味しますが、しかし、 正確(的確,厳密)な certificate、issuer、subject を持っているかについては、 留意していません。 唯一の制限は、CA 証明書のシグネチャが正しいかを確かめることです。 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret" REQUIRE X509;
      • REQUIRE ISSUER issuer はコネクションをより制限します: クライアントは CA 局から発行される有効な X509 証明書を 持っていなければなりません。 X509 証明書を使う事は、常に 暗号化を暗に意味します。 そのため、SSL オプションはこの場合は必要ではありません。 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret"
    -> REQUIRE ISSUER "C=FI, ST=Some-State, L=Helsinki,
    "> O=MySQL Finland AB, CN=Tonu Samuel/Email=tonu@mysql.com";
      • REQUIRE SUBJECT "subject" はクライアントにたいして、 "subject" をサブジェクトに持つ、有効な X509 証明書を要求します。 もしクライアントが正当な certificate を持っていても "subject" が違うものであれば、コネクションは許可されません。 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret"
    -> REQUIRE SUBJECT "C=EE, ST=Some-State, L=Tallinn,
    "> O=MySQL demo client certificate,
    "> CN=Tonu Samuel/Email=tonu@mysql.com";
      • REQUIRE CIPHER "cipher" is needed to assure enough strong ciphers and keylengths will be used. SSL itself can be weak if old algorithms with short encryption keys are used. Using this option, we can ask for some exact cipher method to allow a connection. 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret"
    -> REQUIRE CIPHER "EDH-RSA-DES-CBC3-SHA";
        以下のようにして、これらのオプションは組み合わせることが可能です： The SUBJECT, ISSUER, and CIPHER options can be combined in the REQUIRE clause like this: 
        mysql> GRANT ALL PRIVILEGES ON test.* TO root@localhost
    -> IDENTIFIED BY "goodsecret"
    -> REQUIRE SUBJECT "C=EE, ST=Some-State, L=Tallinn,
    "> O=MySQL demo client certificate,
    "> CN=Tonu Samuel/Email=tonu@mysql.com"
    -> AND ISSUER "C=FI, ST=Some-State, L=Helsinki,
    "> O=MySQL Finland AB, CN=Tonu Samuel/Email=tonu@mysql.com"
    -> AND CIPHER "EDH-RSA-DES-CBC3-SHA";
        Starting from MySQL 4.0.4 the AND keyword is optional between REQUIRE options. オプションの指定順序はといません。 しかし同じオプションを二重に使用できません。 違うオプションのみが、組み合わせ可能です。

      4.4 Disaster Prevention and Recovery

      4.4.1 データベースのバックアップ

      MySQL テーブルはファイルとして格納されるため、バックアップを行 うのは簡単です。矛盾のないバックアップを得るためには、 FLUSH TABLES をおこなって、LOCK TABLES を関連するテーブルで行ってください。 「6.7.2 LOCK TABLES/UNLOCK TABLES 構文」節参照. 「4.5.3 FLUSH 構文」節参照. 読み込みロックだ けが必要なので、そのテーブルでデータベースディレクトリのファイルのコピー が行われている間も、他のスレッドはクエリを継続できます。 The FLUSH TABLE is needed to ensure that the all active index pages is written to disk before you start the backup.

      Starting from 3.23.56 and 4.0.12 BACKUP TABLE will not allow you to overwrite existing files as this would be a security risk.

      もし、テーブルを SQL レベルでバックアップしたいのであれば、SELECT INTO OUTFILE か BACKUP TABLE を使用できます。 「4.4.2 BACKUP TABLE 構文 (3.23.25以上)」節参照.

      他の方法は mysqldump プログラムか mysqlhotcopy スクリプト を使用することです。 「4.8.5 mysqldump, データベースとテーブルから、構造とデータをダンプ」節参照. 「4.8.6 mysqlhotcopy, Copying MySQL Databases and Tables」節参照.

      1. フルバックアップをとるには： 
        shell> mysqldump --tab=/path/to/some/dir --opt --all

or

shell> mysqlhotcopy database /path/to/some/dir
        You can also simply copy all table files (`*.frm', `*.MYD', and `*.MYI' files) as long as the server isn't updating anything. The script mysqlhotcopy does use this method.
      2. mysqld を止め、そして --log-update[=file_name] オプションをつけて起動します。 「4.9.3 更新ログ」節参照. ログファイルは、 mysqldump 実行後に行われたデータベースの変更を 複製するための情報を与えてくれます。

      もしリストアをしなければならない場合、まず最初に REPAIR TABLE か myisamchk -r を実行してテーブルの修復を試みてください。 ほとんどの場合、99.9% 修復はできるはずです。 もし myisamchk が失敗した場合、以下のようにします： (this will only work if you have started MySQL with --log-update, 「4.9.3 更新ログ」節参照):

      1. オリジナルの mysqldump バックアップデータをリストアします。
      2. 次のコマンドを実行して、バイナリログ内の更新を再実行します。 
        shell> mysqlbinlog hostname-bin.[0-9]* | mysql
        更新ログを使用する場合は、次のようにできます: 
        shell> ls -1 -t -r hostname.[0-9]* | xargs cat | mysql

      ls は、全ての更新ログファイルを正しい順で得るために行われます。

      SELECT * INTO OUTFILE 'file_name' FROM tbl_name での選択的バックアップと LOAD DATA FROM INFILE 'file_name' REPLACE ... でのリストアを行う こともできます。重複レコードを避けるためには、テーブル内に PRIMARY KEY か UNIQUE が必要です。REPLACE は、'重複インデックス' 衝突があった場合、 新しいレコードを挿入する時に古いレコードが新しいものに置き換えられることを意味します。

      If you get performance problems in making backups on your system, you can solve this by setting up replication and do the backups on the slave instead of on the master. 「4.10.1 Introduction」節参照.

      If you are using a Veritas filesystem, you can do:

      1. From a client (or Perl), execute: FLUSH TABLES WITH READ LOCK.
      2. From another shell, execute: mount vxfs snapshot.
      3. From the first client, execute: UNLOCK TABLES.
      4. Copy files from snapshot.
      5. Unmount snapshot.

      4.4.2 BACKUP TABLE 構文 (3.23.25以上)

      BACKUP TABLE tbl_name[,tbl_name...] TO '/path/to/backup/directory'

      Copies to the backup directory the minimum number of table files needed to restore the table, after flushing any buffered changes to disk. Currently works only for MyISAM tables. For MyISAM tables, copies `.frm' (definition) and `.MYD' (data) files. The index file can be rebuilt from those two.

      Before using this command, please see 「4.4.1 データベースのバックアップ」節.

      During the backup, a read lock will be held for each table, one at time, as they are being backed up. If you want to back up several tables as a snapshot, you must first issue LOCK TABLES obtaining a read lock for each table in the group.

      The command returns a table with the following columns:

      Column Value
      Table Table name
      Op Always ``backup''
      Msg_type One of status, error, info or warning.
      Msg_text The message.

      Note that BACKUP TABLE is only available in MySQL version 3.23.25 and later.

      4.4.3 RESTORE TABLE 構文 (3.23.25以上)

      RESTORE TABLE tbl_name[,tbl_name...] FROM '/path/to/backup/directory'

      Restores the table(s) from the backup that was made with BACKUP TABLE. Existing tables will not be overwritten; if you try to restore over an existing table, you will get an error. Restoring will take longer than backing up due to the need to rebuild the index. The more keys you have, the longer it will take. Just as BACKUP TABLE, RESTORE TABLE currently works only for MyISAM tables.

      The command returns a table with the following columns:

      Column Value
      Table Table name
      Op Always ``restore''
      Msg_type One of status, error, info or warning.
      Msg_text The message.

      4.4.4 CHECK TABLE 構文 (3.23.13以上)

      CHECK TABLE tbl_name[,tbl_name...] [option [option...]]

option = QUICK | FAST | MEDIUM | EXTENDED | CHANGED

      CHECK TABLE は MyISAM テーブル と InnoDB テーブルだけで動作します。 MyISAM テーブルでは、テーブル上で myisamchk -m table_name を 実行するのと同じことです。

      オプションを何も指定しない場合は MEDIUM が使用されます。

      テーブルのエラーチェックを行ないます。MyISAM テーブルではキー統計が 更新されます。 このコマンドは次のフィールドを持つテーブルを返します:

      Column Value
      Table テーブル名
      Op 常に ``check''
      Msg_type status, error, info, warning のうちの一つ。
      Msg_text メッセージ。

      注意: チェックされた各テーブルに対する情報の多くのレコードが得られます。 最後の１レコードは Msg_type status になり、通常は OK で あるべきです。OK や Table is already up to date が得られない場合は、 テーブルの修復を通常通り実行すべきです。 「4.4.6 テーブルのメンテナンス、クラッシュからの修復のための myisamchk 使用」節参照. Table is already up to date means that the table the given TYPE told MySQL that there wasn't any need to check the table.

      様々なチェックタイプは次の意味です:

      Type Meaning
      QUICK 間違ったリンクをチェックするレコードを走査しません。
      FAST 正しくクローズされなかったテーブルだけをチェックします。
      CHANGED 最後にチェックしてから変更されたテーブルと、正しくクローズされなかったテーブルだけをチェックします。
      MEDIUM 削除されたリンクが OK であることを確かめるためにレコードを走査します。これはレコードのキーチェックサムも計算し、キーの計算されたチェックサムをで、これを確かめます。
      EXTENDED 各レコードのすべてのキーを完全キー検索を行ないます。テーブルが 100% 正当なことを確実にしますが、長い時間が掛かります！

      動的なサイズの MyISAM テーブルについて、開始されたチェックは常に MEDIUM チェックを行ないます。清適サイズレコードでは、レコードはめっ たに壊れないので、QUICK と FAST ではレコードスキャンをスキッ プします。

      チェックオプションは次のように組み合わせられます: 

      CHECK TABLE test_table FAST QUICK;

      これは、テーブルが正しくクローズされなかったかどうかだけを素早くチェックし ます。

      Note: いくつかのケースでは CHECK TABLE はテーブルを変更し ます！ これはテーブルが '汚れている' か '正しくクローズされなかった' とマー クされているのに、CHECK TABLE がテーブル内に何も問題を発見しなかっ た場合に発生します。この場合、CHECK TABLE はテーブルを OK とマーク します。

      If a table is corrupted, then it's most likely that the problem is in the indexes and not in the data part. All of the above check types checks the indexes thoroughly and should thus find most errors.

      If you just want to check a table that you assume is okay, you should use no check options or the QUICK option. The latter should be used when you are in a hurry and can take the very small risk that QUICK didn't find an error in the datafile. (In most cases MySQL should find, under normal usage, any error in the data file. If this happens then the table will be marked as 'corrupted', in which case the table can't be used until it's repaired.)

      FAST and CHANGED are mostly intended to be used from a script (for example to be executed from cron) if you want to check your table from time to time. In most cases you FAST is to be prefered over CHANGED. (The only case when it isn't is when you suspect a bug you have found a bug in the MyISAM code.)

      EXTENDED is only to be used after you have run a normal check but still get strange errors from a table when MySQL tries to update a row or find a row by key (this is very unlikely if a normal check has succeeded!).

      Some things reported by check table, can't be corrected automatically:

      • Found row where the auto_increment column has the value 0. This means that you have in the table a row where the AUTO_INCREMENT index column contains the value 0. (It's possible to create a row where the AUTO_INCREMENT column is 0 by explicitly setting the column to 0 with an UPDATE statement) This isn't an error in itself, but could cause trouble if you decide to dump the table and restore it or do an ALTER TABLE on the table. In this case the AUTO_INCREMENT column will change value, according to the rules of AUTO_INCREMENT columns, which could cause problems like a duplicate key error. To get rid of the warning, just execute an UPDATE statement to set the column to some other value than 0.

      4.4.5 REPAIR TABLE 構文 (3.23.14以上)

      REPAIR TABLE tbl_name[,tbl_name...] [QUICK] [EXTENDED] [USE_FRM]

      REPAIR TABLE は MyISAM テーブルだけで動作します。テーブルに myisamchk -r table_name を実行することと同じです。

      Normally you should never have to run this command, but if disaster strikes you are very likely to get back all your data from a MyISAM table with REPAIR TABLE. If your tables get corrupted a lot you should try to find the reason for this! 「A.4.1 What To Do If MySQL Keeps Crashing」節参照. 「7.1.3 MyISAM table problems.」節参照.

      REPAIR TABLE はなんとかなる壊れたテーブルを修復します。コマンドは次 のフィールドを含む表を返します:

      Column Value
      Table テーブル名
      Op Always ``repair''
      Msg_type status, error, info, warning のどれか.
      Msg_text メッセージ

      注意: 修復された各テーブルの情報の多くのレコードを得ることがあります。最後 の１レコードは Msg_type status になり、通常は OK であるべき です。OK が得られなければ、myisamchk -o でテーブルの修復を試 みるべきです。REPAIR TABLE はまだ、myisamchk のオプションの 全てを持っていないからです。 In the near future, we will make it more flexible.

      QUICK が与えられた場合は、MySQL はインデックスツリー の REPAIR だけを試みます。

      If you use EXTENDED then MySQL will create the index row by row instead of creating one index at a time with sorting; this may be better than sorting on fixed-length keys if you have long CHAR keys that compress very well. This type of repair is like that done by myisamchk --safe-recover.

      As of MySQL 4.0.2, there is a USE_FRM mode for REPAIR. Use it if the `.MYI' file is missing or if its header is corrupted. In this mode MySQL will recreate the table, using information from the `.frm' file. This kind of repair cannot be done with myisamchk.

      4.4.6 テーブルのメンテナンス、クラッシュからの修復のための myisamchk 使用

      Starting with MySQL Version 3.23.13, you can check MyISAM tables with the CHECK TABLE command. 「4.4.4 CHECK TABLE 構文 (3.23.13以上)」節参照. You can repair tables with the REPAIR TABLE command. 「4.4.5 REPAIR TABLE 構文 (3.23.14以上)」節参照.

      MyISAM テーブル (.MYI and .MYD) の検査・修復には myisamchk を 使用します。 ISAM テーブル (.ISM and .ISD) の検査・修復には isamchk を 使用します。 「7 MySQL テーブル型」節参照.

      以下の文は myisamchk について述べていますが、isamchk にもすべて 当てはまります。

      myisamchk ユーティリティは、データベースのテーブルの情報を得たり、 チェックしたり、テーブルの修復や最適化に使用します。 以下のセクションでは、 myisamchk の起動方法(オプションの説明も含む)、 テーブルの保守スケジュールのたて方、 myisamchk の色々な機能の使い方を述べます。

      テーブルの修復と最適化のために、ほとんどの場合、 OPTIMIZE TABLES コマンドが使用できます。しかしこれは myisamchk に比べて、 遅くて確実でもありません。(fatal error発生時の場合)。これは その反面、使用方法が簡単でテーブルのフラッシュを気にかける必要がありません。 「4.5.1 OPTIMIZE TABLE 構文」節参照.

      Even that the repair in myisamchk is quite secure, it's always a good idea to make a backup before doing a repair (or anything that could make a lot of changes to a table)

      4.4.6.1 myisamchk 起動構文

      myisamchk は以下のようにして起動します: 

      shell> myisamchk [options] tbl_name

      options に、あなたが myisamchk にさせたいことを指定します。 その説明は後述します。(myisamchk --help と実行すれば、オプションの一覧が取れます)。 オプションがなければ、 myisamchk は単にテーブルを検査するだけです。 より多くの情報を得たい、あるいは、 myisamchk に誤り訂正の行動を 取らせる事については、後述します。

      tbl_name は検査/修復したいテーブル名です。 もしどこか違うディレクトリにあるデータベースに対して myisamchk を走らせたいなら、 myisamchk にはファイルがどこにあるかわからないので、 ファイルのパスを指定しなければなりません。 実際、 myisamchk はあなたが使用しているファイルがデータベースのディレクトリにある かどうかは考慮しません； ほかの場所にデータベーステーブルのファイルをコピーし、そのコピーしたファイルに対して 回復操作を実行することができます。

      myisamchk コマンドラインには、複数のテーブル名が指定できます。 また、インデックスファイル名(`.MYI' 接尾語のついたファイル)も指定でき、 さらに `*.MYI' とすれば、ディレクトリ内の全てのテーブルが指定できます。 例えば、現在のカレントディレクトリがデーターベースディレクトリならば、 そのディレクトリ内の全てのテーブルは、以下のようにして検査できます： 

      shell> myisamchk *.MYI

      データベースディレクトリに入っていない場合、 パスを指定することにより全てのテーブルが検査できます： 

      shell> myisamchk /path/to/database_dir/*.MYI

      MySQL データディレクトリのパスにワイルドカードを使用することにより、 データベースの全てのテーブルも検査できます： 

      shell> myisamchk /path/to/datadir/*/*.MYI

      The recommended way to quickly check all tables is: 

      myisamchk --silent --fast /path/to/datadir/*/*.MYI
isamchk --silent /path/to/datadir/*/*.ISM

      If you want to check all tables and repair all tables that are corrupted, you can use the following line: 

      myisamchk --silent --force --fast --update-state -O key_buffer=64M \
          -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M \
          /path/to/datadir/*/*.MYI
isamchk --silent --force -O key_buffer=64M -O sort_buffer=64M \
        -O read_buffer=1M -O write_buffer=1M /path/to/datadir/*/*.ISM

      The above assumes that you have more than 64 M free.

      Note that if you get an error like: 

      myisamchk: warning: 1 clients is using or hasn't closed the table properly

      This means that you are trying to check a table that has been updated by the another program (like the mysqld server) that hasn't yet closed the file or that has died without closing the file properly.

      If you mysqld is running, you must force a sync/close of all tables with FLUSH TABLES and ensure that no one is using the tables while you are running myisamchk. In MySQL Version 3.23 the easiest way to avoid this problem is to use CHECK TABLE instead of myisamchk to check tables.

      4.4.6.2 myisamchk の一般オプション

      myisamchk supports the following options.

      -# or --debug=debug_options
      デバッグログの出力。 debug_options はよく 'd:t:o,filename' とされます。
      -? or --help
      ヘルプを表示して終了。
      -O var=option, --set-variable var=option
      変数に値を入れます。 Please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own. 可能な変数とデフォルトの値は myisamchk --help で確認できます:
      Variable Value
      key_buffer_size 523264
      read_buffer_size 262136
      write_buffer_size 262136
      sort_buffer_size 2097144
      sort_key_blocks 16
      decode_bits 9
      sort_buffer_size is used when the keys are repaired by sorting keys, which is the normal case when you use --recover. key_buffer_size is used when you are checking the table with --extended-check or when the keys are repaired by inserting key row by row in to the table (like when doing normal inserts). Repairing through the key buffer is used in the following cases:
      • If you use --safe-recover.
      • If the temporary files needed to sort the keys would be more than twice as big as when creating the key file directly. This is often the case when you have big CHAR, VARCHAR or TEXT keys as the sort needs to store the whole keys during sorting. If you have lots of temporary space and you can force myisamchk to repair by sorting you can use the --sort-recover option.
      Reparing through the key buffer takes much less disk space than using sorting, but is also much slower. もし速い修復を望むなら、メモリの 1/4 を上記の変数にセットします。 You can set both variables to big values, as only one of the above buffers will be used at a time.
      -s or --silent
      静粛モード。 エラーのみを出力します。 二度 -s を指定すると(-ss)、myisamchk は ほとんど出力をしなくなります。
      -v or --verbose
      冗長モード。より多く情報を出力します。 -d と -e オプションと共に使用できます。 -v を複数指定すると(-vv, -vvv)、もっと出力が多くなります！
      -V or --version
      myisamchk バージョンを表示して終了。
      -w or, --wait
      Instead of giving an error if the table is locked, wait until the table is unlocked before continuing. Note that if you are running mysqld on the table with --skip-external-locking, the table can only be locked by another myisamchk command.

      4.4.6.3 myisamchk の検査オプション

      -c or --check
      テーブルのエラーをチェック。 これは myisamchk にオプションを 与えていない時のデフォルトです。
      -e or --extend-check
      テーブルを非常に徹底的に検査します。 (ただし多くのインデックスがある場合、 とても遅くなります。). 極端な場合にだけで必要とされます。 通常 myisamchk や myisamchk --medium-check は、 このオプションなしで全てのエラーを見つけるはずです。 多くのメモリがマシンにあるなら、--extended-check を使用する際には key_buffer_size の値を多く増やします。
      -F or --fast
      Check only tables that haven't been closed properly.
      -C or --check-only-changed
      Check only tables that have changed since the last check.
      -f or --force
      Restart myisamchk with -r (repair) on the table, if myisamchk finds any errors in the table.
      -i or --information
      検査されたテーブルの統計情報を表示。
      -m or --medium-check
      Faster than extended-check, but only finds 99.99% of all errors. Should, however, be good enough for most cases.
      -U or --update-state
      Store in the `.MYI' file when the table was checked and if the table crashed. This should be used to get full benefit of the --check-only-changed option, but you shouldn't use this option if the mysqld server is using the table and you are running mysqld with --skip-external-locking.
      -T or --read-only
      Don't mark table as checked. This is useful if you use myisamchk to check a table that is in use by some other application that doesn't use locking (like mysqld --skip-external-locking).

      4.4.6.4 myisamchk の修復オプション

      以下のオプションは myisamchk を -r か -o オプションで 実行した場合に使用できます:

      -D # or --data-file-length=#
      Max length of datafile (when re-creating datafile when it's 'full').
      -e or --extend-check
      Try to recover every possible row from the datafile. Normally this will also find a lot of garbage rows. Don't use this option if you are not totally desperate.
      -f or --force
      Overwrite old temporary files (table_name.TMD) instead of aborting.
      -k # or keys-used=#
      If you are using ISAM, tells the ISAM storage engine to update only the first # indexes. If you are using MyISAM, tells which keys to use, where each binary bit stands for one key (first key is bit 0). これはインサートを速くします！ 非アクティブになったインデックスは、myisamchk -r を使用すれば再びアクティ ブになります。
      -l or --no-symlinks
      修復時にシンボリックリンクを追いません。 通常、myisamchk はシンボリックリンクが指し示すテーブルも修復します。 This option doesn't exist in MySQL 4.0, as MySQL 4.0 will not remove symlinks during repair.
      -r or --recover
      Can fix almost anything except unique keys that aren't unique (which is an extremely unlikely error with ISAM/MyISAM tables). If you want to recover a table, this is the option to try first. Only if myisamchk reports that the table can't be recovered by -r, you should then try -o. (Note that in the unlikely case that -r fails, the datafile is still intact.) If you have lots of memory, you should increase the size of sort_buffer_size!
      -o or --safe-recover
      古い修復方法を使用します (reads through all rows in order and updates all index trees based on the found rows); これは -r よりも遅いですが、 -r が扱えないものも扱えます。 This recovery method also uses much less disk space than -r. Normally one should always first repair with -r, and only if this fails use -o. If you have lots of memory, you should increase the size of key_buffer_size!
      -n or --sort-recover
      Force myisamchk to use sorting to resolve the keys even if the temporary files should be very big.
      --character-sets-dir=...
      Directory where character sets are stored.
      --set-character-set=name
      Change the character set used by the index
      -t or --tmpdir=path
      一時ファイルを保存する先のパス。 もしセットされなければ、 myisamchk は TMPDIR 環境変数の値をこのパスとします。 Starting from MySQL 4.1, tmpdir can be set to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion.
      -q or --quick
      Faster repair by not modifying the datafile. One can give a second -q to force myisamchk to modify the original datafile in case of duplicate keys
      -u or --unpack
      myisampack でパックされたテーブルファイルをアンパックします。

      4.4.6.5 myisamchk の他のオプション

      Other actions that myisamchk can do, besides repair and check tables:

      -a or --analyze
      キーの分布(配置)を分析します。 This improves join performance by enabling the join optimiser to better choose in which order it should join the tables and which keys it should use: myisamchk --describe --verbose table_name' or using SHOW KEYS in MySQL.
      -d or --description
      テーブルに関するいくらかの情報を表示します
      -A or --set-auto-increment[=value]
      Force AUTO_INCREMENT to start at this or higher value. If no value is given, then sets the next AUTO_INCREMENT value to the highest used value for the auto key + 1.
      -S or --sort-index
      インデックスブロックのソート。 これは、アプリケーションでの ``read-next'' を速くします。
      -R or --sort-records=#
      インデックスに従ってソート。 これはあなたのデータをよりよく配置し、このインデックスへの SELECT, ORDER BY オペレーションを速くします。 (この操作の最初のソートは非常に遅くなるかもしれません！) テーブルのインデックスの番号をみつけるには SHOW INDEX を使用しますが、 これは myisamchk がテーブルのインデックスを見つけるのと同じ順序で行います。 インデックス番号は 1 から始まります。

      4.4.6.6 myisamchk メモリ使用

      myisamchk を走らす上でメモリーの配分は重要です。 myisamchk は -O オプションで定義した以上のメモリは使用しません。 とても大きなファイルのたいして myisamchk をかけたいなら、 メモリーをどれくらい使用するかを最初に決めなくてはなりません。 デフォルトは固定で約 3M だけを使用します。大きな値を使用することで、 myisamchk をより速く動作できます。 例えば、32MBytesのRAMがあるなら、以下のように指定できます (他のオプションも指定して): 

      shell> myisamchk -O sort=16M -O key=16M -O read=1M -O write=1M ...

      -O sort=16M の使用は多くの場合おそらく十分でしょう。

      しかし、myisamchk は TMPDIR 内に一時ファイルを使用します。 TMPDIR がメモリファイルシステムを指している場合は、簡単に out of memory エラーを得るでしょう。 If this happens, set TMPDIR to point at some directory with more space and restart myisamchk.

      When repairing, myisamchk will also need a lot of disk space:

      • Double the size of the record file (the original one and a copy). This space is not needed if one does a repair with --quick, as in this case only the index file will be re-created. This space is needed on the same disk as the original record file!
      • Space for the new index file that replaces the old one. The old index file is truncated at start, so one usually ignore this space. This space is needed on the same disk as the original index file!
      • When using --recover or --sort-recover (but not when using --safe-recover), you will need space for a sort buffer for: (largest_key + row_pointer_length)*number_of_rows * 2. You can check the length of the keys and the row_pointer_length with myisamchk -dv table. This space is allocated on the temporary disk (specified by TMPDIR or --tmpdir=#).

      If you have a problem with disk space during repair, you can try to use --safe-recover instead of --recover.

      4.4.6.7 Using myisamchk for Crash Recovery

      If you run mysqld with --skip-external-locking (which is the default on some systems, like Linux), you can't reliably use myisamchk to check a table when mysqld is using the same table. If you can be sure that no one is accessing the tables through mysqld while you run myisamchk, you only have to do mysqladmin flush-tables before you start checking the tables. If you can't guarantee the above, then you must take down mysqld while you check the tables. If you run myisamchk while mysqld is updating the tables, you may get a warning that a table is corrupt even if it isn't.

      If you are not using --skip-external-locking, you can use myisamchk to check tables at any time. While you do this, all clients that try to update the table will wait until myisamchk is ready before continuing.

      If you use myisamchk to repair or optimise tables, you must always ensure that the mysqld server is not using the table (this also applies if you are using --skip-external-locking). If you don't take down mysqld you should at least do a mysqladmin flush-tables before you run myisamchk. Your tables may be corrupted if the server and myisamchk access the tables simultaneously.

      This chapter describes how to check for and deal with data corruption in MySQL databases. If your tables get corrupted frequently you should try to find the reason for this! 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

      The MyISAM table section contains reason for why a table could be corrupted. 「7.1.3 MyISAM table problems.」節参照.

      When performing crash recovery, it is important to understand that each table tbl_name in a database corresponds to three files in the database directory:

      File Purpose
      `tbl_name.frm' Table definition (form) file
      `tbl_name.MYD' Datafile
      `tbl_name.MYI' Index file

      Each of these three file types is subject to corruption in various ways, but problems occur most often in datafiles and index files.

      myisamchk works by creating a copy of the `.MYD' (data) file row by row. It ends the repair stage by removing the old `.MYD' file and renaming the new file to the original file name. If you use --quick, myisamchk does not create a temporary `.MYD' file, but instead assumes that the `.MYD' file is correct and only generates a new index file without touching the `.MYD' file. This is safe, because myisamchk automatically detects if the `.MYD' file is corrupt and aborts the repair in this case. You can also give two --quick options to myisamchk. In this case, myisamchk does not abort on some errors (like duplicate key) but instead tries to resolve them by modifying the `.MYD' file. Normally the use of two --quick options is useful only if you have too little free disk space to perform a normal repair. In this case you should at least make a backup before running myisamchk.

      4.4.6.8 How to Check Tables for Errors

      To check a MyISAM table, use the following commands:

      myisamchk tbl_name
      This finds 99.99% of all errors. What it can't find is corruption that involves only the datafile (which is very unusual). If you want to check a table, you should normally run myisamchk without options or with either the -s or --silent option.
      myisamchk -m tbl_name
      This finds 99.999% of all errors. It checks first all index entries for errors and then it reads through all rows. It calculates a checksum for all keys in the rows and verifies that they checksum matches the checksum for the keys in the index tree.
      myisamchk -e tbl_name
      This does a complete and thorough check of all data (-e means ``extended check''). It does a check-read of every key for each row to verify that they indeed point to the correct row. This may take a long time on a big table with many keys. myisamchk will normally stop after the first error it finds. If you want to obtain more information, you can add the --verbose (-v) option. This causes myisamchk to keep going, up through a maximum of 20 errors. In normal usage, a simple myisamchk (with no arguments other than the table name) is sufficient.
      myisamchk -e -i tbl_name
      Like the previous command, but the -i option tells myisamchk to print some informational statistics, too.

      4.4.6.9 テーブルの修復方法

      In the following section we only talk about using myisamchk on MyISAM tables (extensions `.MYI' and `.MYD'). If you are using ISAM tables (extensions `.ISM' and `.ISD'), you should use isamchk instead.

      Starting with MySQL Version 3.23.14, you can repair MyISAM tables with the REPAIR TABLE command. 「4.4.5 REPAIR TABLE 構文 (3.23.14以上)」節参照.

      テーブル破壊の兆しとして、クエリが予期せず中断したり、以下のようなエラーが出たり します：

      • `tbl_name.frm' is locked against change
      • Can't find file `tbl_name.MYI' (Errcode: ###)
      • Unexpected end of file
      • Record file is crashed
      • Got error ### from table handler To get more information about the error you can run perror ###. Here is the most common errors that indicates a problem with the table: 
        shell> perror 126 127 132 134 135 136 141 144 145
126 = Index file is crashed / Wrong file format
127 = Record-file is crashed
132 = Old database file
134 = Record was already deleted (or record file crashed)
135 = No more room in record file
136 = No more room in index file
141 = Duplicate unique key or constraint on write or update
144 = Table is crashed and last repair failed
145 = Table was marked as crashed and should be repaired
        Note that error 135, no more room in record file, is not an error that can be fixed by a simple repair. In this case you have to do: 
        ALTER TABLE table MAX_ROWS=xxx AVG_ROW_LENGTH=yyy;

      この他の場合、あなたは自分のテーブルを修理しなければなりません。 myisamchk はほとんどの問題を見つけ出し修正します。

      修復過程は以下で記述する最大4つの段階を踏みます。 これを始める前に、あなたはデータベースディレクトリに cd して テーブルファイルのパーミッションを確認すべきです。 これらファイルは mysqld を実行している UNIX ユーザーが読み込み可能 であるようにしてください(検査のするのにあなたにファイルのアクセス権も必要)。 もしファイルの変更をする必要があるならば、ファイルへの書き込み許可も必要です。

      If you are using MySQL Version 3.23.16 and above, you can (and should) use the CHECK and REPAIR commands to check and repair MyISAM tables. 「4.4.4 CHECK TABLE 構文 (3.23.13以上)」節参照. 「4.4.5 REPAIR TABLE 構文 (3.23.14以上)」節参照.

      The manual section about table maintenance includes the options to isamchk/myisamchk. 「4.4.6 テーブルのメンテナンス、クラッシュからの修復のための myisamchk 使用」節参照.

      The following section is for the cases where the above command fails or if you want to use the extended features that isamchk/myisamchk provides.

      If you are going to repair a table from the command-line, you must first take down the mysqld server. Note that when you do mysqladmin shutdown on a remote server, the mysqld server will still be alive for a while after mysqladmin returns, until all queries are stopped and all keys have been flushed to disk.

      Stage 1: テーブルをチェックする

      myisamchk *.MYI (時間がかかってもよいなら myisamchk -e *.MYI) を実行します。 -s (silent) オプションは不要な情報の出力をおさえます。

      If the mysqld server is done you should use the --update option to tell myisamchk to mark the table as 'checked'.

      myisamchk がエラーを返した場合にだけ、テーブルを修復する必要があります。 この場合、Stage 2 へ進みます。

      チェック時に奇妙なエラー(out of memory エラーのような) が起きた場合、 あるいは myisamchk が落ちた場合、Stage 3 に進んでください。

      Stage 2: 簡単で安全な修復

      Note: If you want repairing to go much faster, you should add: -O sort_buffer=# -O key_buffer=# (where # is about 1/4 of the available memory) to all isamchk/myisamchk commands.

      まず最初に myisamchk -r -q tbl_name を試みてください (-r -q は ``quick recovery mode''の意)。 これはデータファイルに触れないでインデックスファイルの修理を試みます。 もしデータファイルが全てとデータファイル中の正しい場所での削除リンクポイントを 含んでいるなら、これは動作してテーブルを修復します。 成功後、次のテーブルの修復に進んでください。 失敗した場合は、以下の手順で試みてください：

      1. 続ける前にデータファイルをバックアップしてください。
      2. myisamchk -r tbl_name を使用します(-r は ``recovery mode''の意)。 これは不正なレコードと削除されたレコードをデータファイルから消去し、 インデックスファイル(.MYI)を再構築します。
      3. 上記が失敗した場合、myisamchk --safe-recover tbl_name を使用して下さい。 Safe recovery モードは古い方法を使用して修復します。 これは普通の修復モードでは行わない操作をいくつかもっています。(遅いですが)

      If you get weird errors when repairing (such as out of memory errors), or if myisamchk crashes, go to Stage 3.

      Stage 3: 難しい修復

      インデックスファイル(.MYI)の最初の 16K ブロックが破壊された場合、 または不正な情報を含む場合、またはインデックスファイルがない場合にだけ、 本修復段階を経ます。 この場合、新しいインデックスファイルファイルを作成する必要があります。 次のようにしてください:

      1. データファイルをどこか安全場所に移動します。
      2. 新しい(空の)データとインデックスファイルを作るために、 テーブルディスクリプタファイルを使用します： 
        shell> mysql db_name
mysql> SET AUTOCOMMIT=1;
mysql> TRUNCATE TABLE table_name;
mysql> quit
        If your SQL version doesn't have TRUNCATE TABLE, use DELETE FROM table_name instead.
      3. 古いデータファイルを新しく作ったデータファイルにコピーします。 (Don't just move the old file back onto the new file; you want to retain a copy in case something goes wrong.)

      Go back to Stage 2. myisamchk -r -q should work now. (This shouldn't be an endless loop.)

      As of MySQL 4.0.2 you can also use REPAIR ... USE_FRM which performs the whole procedure automatically.

      Stage 4: とても難しい修復

      これは、ディスクリプタファイル(.frm)もクラッシュした場合にだけ発生します。 これは発生することはありません。なぜならディスクリプタファイルは テーブルが生成された後に書かれることはないからです。

      1. ディスクリプタファイルをバックアップからリストアして、Stage 3 に戻ってください。 インデックスファイルのリストアもできます。そして Stage 2 に戻ってください。 後者の場合、myisamchk -r で開始すべきです。
      2. バックアップを持っていなくても、テーブルがどのように作成されたかを正確に知って いれば、他のデータベース内にテーブルのコピーを生成します。 新しいデータファイルを削除し、先ほど作ったデータベースの中の ディスクリプタファイルとインデックスファイルを、壊れたデータベース内に 移動します。これは新しいディスクリプタファイルとインデックスファイルを 与えることになりますが、データファイルはそのまま残っています。 Stage 2 に進み、インデックスファイルの修復を行ってください。

      4.4.6.10 テーブルの最適化

      断片化されたレコードの結合と、 レコードの削除と更新から生じる無駄なスペースの排除、 これら行うには、修復モード(recovery mode)で myisamchk を実行します： 

      shell> myisamchk -r tbl_name

      You can optimise a table in the same way using the SQL OPTIMIZE TABLE statement. OPTIMIZE TABLE does a repair of the table and a key analysis, and also sorts the index tree to give faster key lookups. There is also no possibility of unwanted interaction between a utility and the server, because the server does all the work when you use OPTIMIZE TABLE. 「4.5.1 OPTIMIZE TABLE 構文」節参照.

      myisamchk には、あなたがテーブルの性能を向上させるのに使用することができる 他の多くのオプションがあります:

      • -S, --sort-index
      • -R index_num, --sort-records=index_num
      • -a, --analyze

      For a full description of the option. 「4.4.6.1 myisamchk 起動構文」節参照.

      4.4.7 テーブルの保守体制の設定

      Starting with MySQL Version 3.23.13, you can check MyISAM tables with the CHECK TABLE command. 「4.4.4 CHECK TABLE 構文 (3.23.13以上)」節参照. You can repair tables with the REPAIR TABLE command. 「4.4.5 REPAIR TABLE 構文 (3.23.14以上)」節参照.

      問題が発生するまで待つより、定期的にテーブルを検査する方がよりよい考えです。 保守目的には、myisamchk -s でテーブルを検査するのがよいでしょう。 -s オプション(short for --silent) はサイレントモードなので、 エラーが起きた場合にだけメッセージを出力します。

      サーバーを開始するときにテーブルを検査するのもよい考えです。 例えば、更新最中にマシンがリブートされたなら、全てのテーブルに関して その影響がないか検査する必要があります。（これは``expected crashed table''です） リブート後にもし古い `.pid' ファイル(プロセスID) があるならば、 24時間以内に変更されたテーブルに対して myisamchk を走らせて検査させるよう に、 safe_mysqld にテストを追加しても構いません。 (`.pid' ファイルは mysqld 起動時に作られ、通常修了時に消されます。 スタート時に `.pid' ファイルが存在するなら mysqld が異常終了したこと を示します。)

      良いテストは、`.pid' ファイルの作成時間以降に変更された 全てのテーブルを検査するテストです。

      通常のシステム運用中にもテーブルを検査すべきです。 MySQL AB では、週に一度、 cron を使用して重要なテーブルを検査し ています。 `crontab' ファイルには以下のように記述します： 

      35 0 * * 0 /path/to/myisamchk --fast --silent /path/to/datadir/*/*.MYI

      これは壊れたテーブルの情報を出力しますので、必要とあらば検査、修復が行えるわけで す。

      予想外の事故で壊れたテーブル(ハードウェアのトラブルが原因で崩壊)を除き、 2,3年間、テーブルは壊れたことはありません(これは本当に本当です)。 ので、一週間に一度のチェックでも十分です。

      24時間以内に変更された全てのテーブルに対して、 myisamchk -s を毎晩実行する事を勧めます。 そうすれば、あなたは我々と同じぐらいに MySQL を 信頼することになります。

      Normally you don't need to maintain MySQL tables that much. If you are changing tables with dynamic size rows (tables with VARCHAR, BLOB or TEXT columns) or have tables with many deleted rows you may want to from time to time (once a month?) defragment/reclaim space from the tables.

      You can do this by using OPTIMIZE TABLE on the tables in question or if you can take the mysqld server down for a while do: 

      isamchk -r --silent --sort-index -O sort_buffer_size=16M */*.ISM
myisamchk -r --silent --sort-index  -O sort_buffer_size=16M */*.MYI

      4.4.8 テーブル情報取得

      テーブルから詳細/統計を得るためには、次の方法を使用します。後でさらに詳細な情 報をいくつか説明します。

      • myisamchk -d tbl_name myisamchk を ``describe mode'' で実行し、テーブルの説明記述を作ります。 --skip-external-locking (ver.4.0.3未満では--skip-locking) を指定して MySQL サーバーを起動した場合、 myisamchk は myisamchk 実行中に更新されたテーブルについてエラーを報告します. しかし myisamchk は describe mode ではテーブルを変えないので、 データを破壊する危険性はありません。
      • myisamchk -d -v tbl_name myisamchk がしていることに関する、より多くの情報を作り出すには、 -v をつけて冗長モードで走らせるようにします。
      • myisamchk -eis tbl_name テーブルから最も重要な情報だけを示します。 テーブル全体を読まなければならないので、遅いです。
      • myisamchk -eiv tbl_name -eis と似ているが、何を行っているかを表示します。

      myisamchk -d 出力の例: 

      MyISAM file:     company.MYI
Record format:   Fixed length
Data records:    1403698  Deleted blocks:         0
Recordlength:    226

table description:
Key Start Len Index   Type
1   2     8   unique  double
2   15    10  multip. text packed stripped
3   219   8   multip. double
4   63    10  multip. text packed stripped
5   167   2   multip. unsigned short
6   177   4   multip. unsigned long
7   155   4   multip. text
8   138   4   multip. unsigned long
9   177   4   multip. unsigned long
    193   1           text

      myisamchk -d -v 出力の例: 

      MyISAM file:         company
Record format:       Fixed length
File-version:        1
Creation time:       1999-10-30 12:12:51
Recover time:        1999-10-31 19:13:01
Status:              checked
Data records:           1403698  Deleted blocks:              0
Datafile parts:         1403698  Deleted data:                0
Datafilepointer (bytes):      3  Keyfile pointer (bytes):     3
Max datafile length: 3791650815  Max keyfile length: 4294967294
Recordlength:               226

table description:
Key Start Len Index   Type                  Rec/key     Root Blocksize
1   2     8   unique  double                      1 15845376      1024
2   15    10  multip. text packed stripped        2 25062400      1024
3   219   8   multip. double                     73 40907776      1024
4   63    10  multip. text packed stripped        5 48097280      1024
5   167   2   multip. unsigned short           4840 55200768      1024
6   177   4   multip. unsigned long            1346 65145856      1024
7   155   4   multip. text                     4995 75090944      1024
8   138   4   multip. unsigned long              87 85036032      1024
9   177   4   multip. unsigned long             178 96481280      1024
    193   1           text

      myisamchk -eis 出力の例: 

      Checking MyISAM file: company
Key:  1:  Keyblocks used:  97%  Packed:    0%  Max levels:  4
Key:  2:  Keyblocks used:  98%  Packed:   50%  Max levels:  4
Key:  3:  Keyblocks used:  97%  Packed:    0%  Max levels:  4
Key:  4:  Keyblocks used:  99%  Packed:   60%  Max levels:  3
Key:  5:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
Key:  6:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
Key:  7:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
Key:  8:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
Key:  9:  Keyblocks used:  98%  Packed:    0%  Max levels:  4
Total:    Keyblocks used:  98%  Packed:   17%

Records:          1403698    M.recordlength:     226
Packed:             0%
Recordspace used:     100%   Empty space:          0%
Blocks/Record:   1.00
Record blocks:    1403698    Delete blocks:        0
Recorddata:     317235748    Deleted data:         0
Lost space:             0    Linkdata:             0

User time 1626.51, System time 232.36
Maximum resident set size 0, Integral resident set size 0
Non physical pagefaults 0, Physical pagefaults 627, Swaps 0
Blocks in 0 out 0, Messages in 0 out 0, Signals 0
Voluntary context switches 639, Involuntary context switches 28966

      myisamchk -eiv 出力の例: 

      Checking MyISAM file: company
Data records: 1403698   Deleted blocks:       0
- check file-size
- check delete-chain
block_size 1024:
index  1:
index  2:
index  3:
index  4:
index  5:
index  6:
index  7:
index  8:
index  9:
No recordlinks
- check index reference
- check data record references index: 1
Key:  1:  Keyblocks used:  97%  Packed:    0%  Max levels:  4
- check data record references index: 2
Key:  2:  Keyblocks used:  98%  Packed:   50%  Max levels:  4
- check data record references index: 3
Key:  3:  Keyblocks used:  97%  Packed:    0%  Max levels:  4
- check data record references index: 4
Key:  4:  Keyblocks used:  99%  Packed:   60%  Max levels:  3
- check data record references index: 5
Key:  5:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
- check data record references index: 6
Key:  6:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
- check data record references index: 7
Key:  7:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
- check data record references index: 8
Key:  8:  Keyblocks used:  99%  Packed:    0%  Max levels:  3
- check data record references index: 9
Key:  9:  Keyblocks used:  98%  Packed:    0%  Max levels:  4
Total:    Keyblocks used:   9%  Packed:   17%

- check records and index references
[LOTS OF ROW NUMBERS DELETED]

Records:          1403698    M.recordlength:     226   Packed:             0%
Recordspace used:     100%   Empty space:          0%  Blocks/Record:   1.00
Record blocks:    1403698    Delete blocks:        0
Recorddata:     317235748    Deleted data:         0
Lost space:             0    Linkdata:             0

User time 1639.63, System time 251.61
Maximum resident set size 0, Integral resident set size 0
Non physical pagefaults 0, Physical pagefaults 10580, Swaps 0
Blocks in 4 out 0, Messages in 0 out 0, Signals 0
Voluntary context switches 10604, Involuntary context switches 122798

      上で使用されたテーブルのデータファイルサイズをここに示します: 

      -rw-rw-r--   1 monty    tcx     317235748 Jan 12 17:30 company.MYD
-rw-rw-r--   1 davida   tcx      96482304 Jan 12 18:35 company.MYM

      myisamchk が生成する情報の説明を以下に示します。 ``keyfile'' はインデックスファイルです。 ``Record'' と ``row'' は同義です。

      • ISAM file ISAM (index) ファイルの名前
      • Isam-version ISAM 形式のバージョン。現在は常に 2
      • Creation time データファイルが生成された時。
      • Recover time インデックス/データファイルが最後に再構築された時。
      • Data records テーブルのレコード数。
      • Deleted blocks 予約された領域をまだ持っている削除ブロック数。 このスペースを最小にするために自分のテーブルを最適化することができます。 「4.4.6.10 テーブルの最適化」節参照.
      • Data file: Parts 動的なレコード形式にいくつのデータブロックがあるかを表示します。 分割なしで最適化されたテーブルでは Data records と同じです。
      • Deleted data 改善されていない削除データのバイト数。 このスペースを最小にするために自分のテーブルを最適化することができます。 「4.4.6.10 テーブルの最適化」節参照.
      • Data file pointer データファイルポインタの大きさ(バイト数)。これは普通 2, 3, 4 または 5 バ イトです。多くのテーブルは 2 バイトで管理されますが、これはまだ MySQL から制御できません。固定テーブルではこれはレコードアドレ スです。動的テーブルではこれはバイトアドレスです。
      • Keyfile pointer データファイルポインタのバイト数。これは普通 1, 2 または 3 バイトです。 多くのテーブルは 2 バイトで管理されますが、これは MySQL では自動的に 計算されます。これは常にブロックアドレスです。
      • Max datafile length テーブルのデータファイル (.MYD ファイル) が獲得できる長さ (バイト数)。
      • Max keyfile length テーブルのキーファイル (.MYI ファイル) が獲得できる長さ (バイト数)。
      • Recordlength テーブルの各レコードが使用する領域の大きさ(バイト数)。
      • Record format 各テーブルのレコードの形式。この例では Fixed length を使用します。 他の値で可能な物は圧縮、パックします。
      • table description テーブル内の全てのキーのリスト。各キーについて、いくつかの低レベル情報が提供さ れます:
        • Key キー番号。
        • Start インデックス部が開始するレコード内の位置。
        • Len インデックス部の長さ。 パックされた数値では、これは常に項目の完全な長さになります。 文字型においては、文字型の項目の頭の部分にインデックスがつく事になりますので、 インデックス項目の最大長さよりもこの値は短くなるでしょう。
        • Index unique or multip. (multiple). このインデックス内では1つの値が複数 回存在し得ます。
        • Type このインデックス部が持つデータ型。 これは NISAM データ型で、 packed, stripped か empty オプションを持ちます。
        • Root ルートインデックスブロックのアドレス。
        • Blocksize 各インデックスブロックのサイズ。これはデフォルトでは 1024 ですが、コンパ イル時に変更できます。
        • Rec/key これはオプティマイザによって使用される統計値です。このキーの値ごとのレコー ド数を知らせます。ユニークキーは常に1の値を持ちます。これはテーブルがロードさ れた(または大きく変更された)後に myisamchk -a で更新されます。これ が全く更新されない場合はデフォルト値の 30 が与えられます。
      • 上の最初の例では、9番目のキーは2つの部分をもったマルチパートキーです。
      • Keyblocks used 使用されたキーブロックのパーセンテージ。このテーブルは myisamchk で再配置 されるため、値はとても高くなります (理論的な最大にとても近くなります)。
      • Packed MySQL は一般の接尾辞でキーのパックを試みます。これは CHAR/VARCHAR/DECIMAL キーでだけ使用できます。名前の ような長い文字列では、これは使用領域を顕著に減らします。上の三番目の例では4番目 のキーが10文字長で、領域の60%の減少を得ます。
      • Max levels このキーの Btree の深さ。長いキーを持つ大きなテーブルは高い値を得ます。
      • Records テーブルが持っているレコード数。
      • M.recordlength 平均のレコード長。固定テーブルでは、これは正確なレコード長となります。
      • Packed MySQL は文字列の最後から空白を除きます。これによって節約された パーセンテージを Packed は示します。
      • Recordspace used データファイルが使用されたパーセンテージ。
      • Empty space データファイルが使用されていないパーセンテージ。
      • Blocks/Record レコード毎のブロック数 (断片化レコードの構成数)。 これは固定形式テーブルでは常に1です。この値は可能な限 り 1.0 に留まります。これが大きすぎる場合は、myisamchk でテーブルを再配置 できます。 「4.4.6.10 テーブルの最適化」節参照.
      • Recordblocks 使用されたブロック (links) 数。固定型式ではこれはレコード数と同じです。
      • Deleteblocks 削除されたブロック (links) 数。
      • Recorddata データファイル中にある実際のユーザデータのバイト数。
      • Deleted data データファイル中にある削除された(unused)データのバイト数。
      • Lost space レコードがより短い長さに更新された場合、いくつかの領域が失われます。これ はそのような消失の全ての合計(バイト)です。
      • Linkdata 動的形式の使用時、ブロックはポインタ(4〜7バイト)にリンクされます。Linkdataは そのポインタの全ての合計です。

      テーブルが pack_isam で圧縮されているなら、myisamchk -d は それぞれのテーブルコラムに関する追加情報を出力します。 「4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ」節. を参照してください。 この情報例と説明記述の意味があります。

      4.5 Database Administration Language Reference

      4.5.1 OPTIMIZE TABLE 構文

      OPTIMIZE TABLE tbl_name[,tbl_name]...

      OPTIMIZE TABLEは、テーブルの大部分を削除したり、可変長となっているテーブ ル(VARCHAR、BLOBもしくはTEXTフィールドを持つテーブル)に多く の変更を加えた場合に使用すべきです。 削除されたレコードはリンクリストで維持され、次のINSERT操作は、古いレコー ド位置を再利用します。 未使用領域を再生するためにOPTIMIZE TABLEを使用することができます。

      今のところ、OPTIMIZE TABLE は MyISAM と BDB テーブ ル上でだけ動作します。BDB テーブルでは、OPTIMIZE TABLE が現 在 ANALYZE TABLE にマップされます。 「4.5.2 ANALYZE TABLE Syntax」節参照.

      --skip-new または --safe-mode で mysqld を起動するこ とで、他のテーブル型で OPTIMIZE TABLE を動作するようにできます。しかし、こ の場合 OPTIMIZE TABLE は ALTER TABLE にマップされるだけです。

      OPTIMIZE TABLE は次の方法で動作します:

      • テーブルが削除されているかレコードが分割する場合、テーブルを修復します。
      • インデックスページがソートされていない場合、ソートします。
      • 統計が更新されていない（そしてインデックスをソートすることで修復が行なわれ なかった）場合、それを更新します。

      MyISAM テーブルの OPTIMIZE TABLE はテーブル上で myisamchk --quick --check-changed-tables --sort-index --analyze を 実行することと同等です。

      注意: テーブルは OPTIMIZE TABLE 実行中はロックされます！

      4.5.2 ANALYZE TABLE Syntax

      ANALYZE TABLE tbl_name[,tbl_name...]

      Analyse and store the key distribution for the table. During the analysis, the table is locked with a read lock. This works on MyISAM and BDB tables.

      This is equivalent to running myisamchk -a on the table.

      MySQL uses the stored key distribution to decide in which order tables should be joined when one does a join on something else than a constant.

      The command returns a table with the following columns:

      Column Value
      Table Table name
      Op Always ``analyze''
      Msg_type One of status, error, info or warning.
      Msg_text The message.

      You can check the stored key distribution with the SHOW INDEX command. 「4.5.6.1 Retrieving information about Database, Tables, Columns, and Indexes」節参照.

      If the table hasn't changed since the last ANALYZE TABLE command, the table will not be analysed again.

      4.5.3 FLUSH 構文

      FLUSH flush_option [,flush_option] ...

      FLUSH コマンドで MySQL が使用している内部キャッシュの いくつかをきれいに消すことができます。 FLUSH を実行するには、 RELOAD 権限がなければなりません。

      flush_option には以下の内一つが指定できます：

      Option Description
      HOSTS ホストキャッシュテーブルを空にします。あなたのホストの IP アドレスを変えたり、Host ... is blocked というエラーメッセージが 出る場合はホストテーブルキャッシュを一度空にしなくてはなりません。 指定したホストに対して max_connect_errors 以上の接続エラーが出る場合、 MySQL は何か起きたと推定し、そのホストからのいかなる接続要求も 拒否します。ホストテーブルキャッシュの消去は、再び接続を許すようにします。 「A.2.4 Host '...' is blocked エラー」節参照. mysqld を -O max_connect_errors=999999999 開始し、 このエラーメッセージを回避できます
      DES_KEY_FILE Reloads the DES keys from the file that was specified with the --des-key-file option at server startup time.
      LOGS 標準のログファイルと更新ログファイルを 一度閉じて再び開きます。 もし更新ログファイルを拡張子無しで指定している場合、新しい更新ログファイルの 拡張子の番号は、一つ前のファイルより 1 増やした数になります。 ファイル名に拡張を使用した場合、MySQL は更新ログファイルを閉じて開きます。 「4.9.3 更新ログ」節参照. This is the same thing as sending the SIGHUP signal to the mysqld server.
      PRIVILEGES mysql データベースの許可テーブルから、権限情報を再読込します。
      QUERY CACHE Defragment the query cache to better utilise its memory. This command will not remove any queries from the cache, unlike RESET QUERY CACHE.
      TABLES 全ての開いているテーブルを閉じます。使用中のテーブルに も close を強制します。 This also flushes the query cache.
      [TABLE | TABLES] tbl_name [,tbl_name...] Flushes only the given tables.
      TABLES WITH READ LOCK 全ての開いているテーブルを閉じ、 UNLOCK TABLES を実行するまで全てのテーブルを read lock でロックします。 This is very convenient way to get backups if you have a filesystem, like Veritas,that can take snapshots in time.
      STATUS ほとんどのステータス変数を 0 にします。 This is something one should only use when debugging a query.
      USER_RESOURCES Resets all user resources to zero. This will enable blocked users to login again. 「4.3.6 Limiting user resources」節参照.

      上に示したコマンドは、mysqladmin を使用しても実行できます。 mysqladmin の引数はそれぞれ、flush-hosts, flush-logs, reload, flush-tables となります。

      Take also a look at the RESET command used with replication. 「4.5.4 RESET 構文」節参照.

      4.5.4 RESET 構文

      RESET reset_option [,reset_option] ...

      The RESET command is used to clear things. It also acts as an stronger version of the FLUSH command. 「4.5.3 FLUSH 構文」節参照.

      To execute RESET, you must have the RELOAD privilege.

      Option Description
      MASTER Deletes all binary logs listed in the index file, resetting the binlog index file to be empty. In pre-3.23.26 versions, FLUSH MASTER (Master)
      SLAVE Makes the slave forget its replication position in the master logs. In pre 3.23.26 versions the command was called FLUSH SLAVE(Slave)
      QUERY CACHE Removes all query results from the query cache.

      4.5.5 KILL 構文

      KILL thread_id

      thread_id には、mysqld に接続して走っているスレッドの ID を 空白で区切って指定します。 SHOW PROCESSLIST コマンドで走っているスレッドを知ることができ、 KILL thread_id コマンドでスレッドを KILL できます。

      If you have the PROCESS privilege, you can see all threads. If you have the SUPER privilege, you can kill all threads. Otherwise, you can only see and kill your own threads. (version 4.0.2未満では： もし PROCESS 権限があるなら、全てのスレッドを確認し、KILL 出来ます。 そうでなければ、自分のスレッドだけを確認し、KILL する事ができます。)

      mysqladmin processlist と mysqladmin kill をスレッドの 検査と KILL に使用できます。

      When you do a KILL, a thread-specific kill flag is set for the thread.

      In most cases it may take some time for the thread to die as the kill flag is only checked at specific intervals.

      • In SELECT, ORDER BY and GROUP BY loops, the flag is checked after reading a block of rows. If the kill flag is set, the statement is aborted.
      • When doing an ALTER TABLE the kill flag is checked before each block of rows are read from the original table. If the kill flag was set the command is aborted and the temporary table is deleted.
      • When doing an UPDATE or DELETE, the kill flag is checked after each block read and after each updated or deleted row. If the kill flag is set, the statement is aborted. Note that if you are not using transactions, the changes will not be rolled back!
      • GET_LOCK() will abort with NULL.
      • An INSERT DELAYED thread will quickly flush all rows it has in memory and die.
      • If the thread is in the table lock handler (state: Locked), the table lock will be quickly aborted.
      • If the thread is waiting for free disk space in a write call, the write is aborted with an disk full error message.

      4.5.6 SHOW 構文

         SHOW DATABASES [LIKE wild]
or SHOW [OPEN] TABLES [FROM db_name] [LIKE wild]
or SHOW [FULL] COLUMNS FROM tbl_name [FROM db_name] [LIKE wild]
or SHOW INDEX FROM tbl_name [FROM db_name]
or SHOW TABLE STATUS [FROM db_name] [LIKE wild]
or SHOW STATUS [LIKE wild]
or SHOW VARIABLES [LIKE wild]
or SHOW LOGS
or SHOW [FULL] PROCESSLIST
or SHOW GRANTS FOR user
or SHOW CREATE TABLE table_name
or SHOW MASTER STATUS
or SHOW MASTER LOGS
or SHOW SLAVE STATUS
or SHOW WARNINGS [LIMIT #]
or SHOW ERRORS [LIMIT #]
or SHOW TABLE TYPES

      SHOW はデータベース、テーブル、フィールド、サーバーについての情報を与えます。 LIKE wild が使用された場合、wild 文字列は通常の SQL ワイルドカード (`%' と `_') です。

      4.5.6.1 Retrieving information about Database, Tables, Columns, and Indexes

      tbl_name FROM db_name の代わりに、db_name.tbl_name が使用できます。 これら二つは同じです： 

      mysql> SHOW INDEX FROM mytable FROM mydb;
mysql> SHOW INDEX FROM mydb.mytable;

      SHOW DATABASES は MySQL サーバー上のデータベースを示します。 mysqlshow コマンドでも同じ情報が得られます。

      SHOW TABLES は指定されたデータベースのテーブルを一覧表示します。 mysqlshow db_name コマンドでも同じ情報が得られます。 In version 4.0.2 you will only see those databases for which you have some kind of privilege, if you don't have the global SHOW DATABASES privilege.

      Note: もしユーザーにテーブルに対する権限が無い場合、 テーブルは SHOW TABLES や mysqlshow db_name の要求で 表示されません。

      SHOW OPEN TABLES はテーブルキャッシュに現在オープン去れているテーブ ルを一覧表示します。 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節参照. Comment フィールドはテーブ ルが何回 cached と in_use になったかを知らせます。

      SHOW COLUMNS は与えられたテーブルのフィールドを表示します。 FULL オプションを指定した場合、各フィールドに持つ権限も得られます。 もしそのフィールドの型が、あなたが CREATE TABLE 構文実行時に与えたものと 違う場合は、 MySQL は、フィールドの型をときおり変更することが あることに注意してください。 「6.5.3.1 暗黙のフィールド定義変更」節参照.

      DESCRIBE 文は SHOW COLUMNS と似たような情報を提供します。 「6.6.2 DESCRIBE 構文 (フィールドについての情報を得る)」節参照.

      SHOW FIELDS は SHOW COLUMNS の別名として使用され、 SHOW KEYS は SHOW INDEX の別名として使用されます。 テーブルのフィールドやインデックスは mysqlshow db_name tbl_name か mysqlshow -k db_name tbl_name でも見れます。

      SHOW INDEX は ODBC でいう SQLStatistics に近い形式で、インデックスの情報を表示します。 以下の項目が返ります：

      Column 意味
      Table テーブル名
      Non_unique インデックスが重複を含まないなら 0
      Key_name インデックス名
      Seq_in_index インデックスの項目番号。1 から始まります。
      Column_name フィールド名。
      Collation どのようにこのフィールドがインデックス中で ソートされるか. MySQL ではこれは A (Ascending) か NULL (Not sorted) に なります。
      Cardinality インデックス中のユニークな値の数。 これは isamchk -a の実行で更新されます。
      Sub_part もしこのフィールドがインデックスに一部分だけ使用 している場合、そのインデックスに使用しているキャラクター数をしめす。 もしキー全 体がインデックスされているなら NULL 。
      Null Contains 'YES' if the column may contain NULL.
      Index_type Index method used.
      Comment Various remarks. For now, it tells in MySQL < 4.0.2 whether index is FULLTEXT or not.

      Note that as the Cardinality is counted based on statistics stored as integers, it's not necessarily accurate for small tables.

      The Null and Index_type columns were added in MySQL 4.0.2.

      4.5.6.2 SHOW TABLE STATUS

      SHOW TABLE STATUS [FROM db_name] [LIKE wild]

      SHOW TABLE STATUS (バージョン 3.23 の新機能) は SHOW STATUS のようですが、それぞれのテーブルについてより多くの情報を提供します。 mysqlshow --status db_name コマンドを実行しても同じものが得られます。 以下の項目が返ってきます：

      項目 意味
      Name テーブル名
      Type テーブルの種類. 「7 MySQL テーブル型」節参照.
      Row_format レコードの保存形式 (Fixed, Dynamic, or Compressed).
      Rows レコード数.
      Avg_row_length レコードの平均長.
      Data_length データファイルの大きさ.
      Max_data_length データファイルの最大長.
      Index_length インデックスファイルの大きさ.
      Data_free 割り当てられたが使用されていないバイト数.
      Auto_increment 次の autoincrement 値.
      Create_time テーブル作成時刻.
      Update_time 一番最後にデータファイルが更新された時刻.
      Check_time 一番最後にテーブルがチェックされた時刻.
      Create_options CREATE TABLE で使用された拡張オプション
      Comment テーブル作成時につけられたコメント (あるいは、なぜこの テーブルに MySQL がアクセスできないかのいくつかの情報).

      InnoDB tables will report the free space in the tablespace in the table comment.

      4.5.6.3 SHOW STATUS

      SHOW STATUS は mysqladmin extended-status と同様に、 サーバからのステータス情報を与えます。出力は次とは異なるかもしれません: 

      +--------------------------+------------+
| Variable_name            | Value      |
+--------------------------+------------+
| Aborted_clients          | 0          |
| Aborted_connects         | 0          |
| Bytes_received           | 155372598  |
| Bytes_sent               | 1176560426 |
| Connections              | 30023      |
| Created_tmp_disk_tables  | 0          |
| Created_tmp_tables       | 8340       |
| Created_tmp_files        | 60         |
| Delayed_insert_threads   | 0          |
| Delayed_writes           | 0          |
| Delayed_errors           | 0          |
| Flush_commands           | 1          |
| Handler_delete           | 462604     |
| Handler_read_first       | 105881     |
| Handler_read_key         | 27820558   |
| Handler_read_next        | 390681754  |
| Handler_read_prev        | 6022500    |
| Handler_read_rnd         | 30546748   |
| Handler_read_rnd_next    | 246216530  |
| Handler_update           | 16945404   |
| Handler_write            | 60356676   |
| Key_blocks_used          | 14955      |
| Key_read_requests        | 96854827   |
| Key_reads                | 162040     |
| Key_write_requests       | 7589728    |
| Key_writes               | 3813196    |
| Max_used_connections     | 0          |
| Not_flushed_key_blocks   | 0          |
| Not_flushed_delayed_rows | 0          |
| Open_tables              | 1          |
| Open_files               | 2          |
| Open_streams             | 0          |
| Opened_tables            | 44600      |
| Questions                | 2026873    |
| Select_full_join         | 0          |
| Select_full_range_join   | 0          |
| Select_range             | 99646      |
| Select_range_check       | 0          |
| Select_scan              | 30802      |
| Slave_running            | OFF        |
| Slave_open_temp_tables   | 0          |
| Slow_launch_threads      | 0          |
| Slow_queries             | 0          |
| Sort_merge_passes        | 30         |
| Sort_range               | 500        |
| Sort_rows                | 30296250   |
| Sort_scan                | 4650       |
| Table_locks_immediate    | 1920382    |
| Table_locks_waited       | 0          |
| Threads_cached           | 0          |
| Threads_created          | 30022      |
| Threads_connected        | 1          |
| Threads_running          | 1          |
| Uptime                   | 80380      |
+--------------------------+------------+

      上に示したステータス変数は以下に示すの意味を持ちます：

      Variable Meaning
      Aborted_clients クライアントが接続を閉じる前に死んでしまったために中断されたコネクション数。 「A.2.9 Communication Errors / Aborted Connection」節参照.
      Aborted_connects MySQL サーバーに接続を試みて失敗した数。 「A.2.9 Communication Errors / Aborted Connection」節参照.
      Bytes_received クライアントから受信したバイト数
      Bytes_sent クライアントに送信したバイト数
      Com_xxx Number of times each xxx command has been executed.
      Connections サーバーに接続を試みた数
      Created_tmp_disk_tables ステートメント実行中に暗黙のうちに作成されたメモり内にある一時テーブルの数
      Created_tmp_tables Number of implicit temporary tables in memory created while executing statements.
      Created_tmp_files How many temporary files mysqld has created.
      Delayed_insert_threads Number of delayed insert handler threads in use.
      Delayed_writes Number of rows written with INSERT DELAYED.
      Delayed_errors Number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key).
      Flush_commands FLUSH コマンドの実行回数
      Handler_commit Number of internal COMMIT commands.
      Handler_delete Number of times a row was deleted from a table.
      Handler_read_first Number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans, for example, SELECT col1 FROM foo, assuming that col1 is indexed.
      Handler_read_key Number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed.
      Handler_read_next Number of requests to read next row in key order. This will be incremented if you are querying an index column with a range constraint. This also will be incremented if you are doing an index scan.
      Handler_read_prev Number of requests to read previous row in key order. This is mainly used to optimise ORDER BY ... DESC.
      Handler_read_rnd Number of requests to read a row based on a fixed position. This will be high if you are doing a lot of queries that require sorting of the result.
      Handler_read_rnd_next Number of requests to read the next row in the datafile. This will be high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
      Handler_rollback Number of internal ROLLBACK commands.
      Handler_update Number of requests to update a row in a table.
      Handler_write Number of requests to insert a row in a table.
      Key_blocks_used The number of used blocks in the key cache.
      Key_read_requests The number of requests to read a key block from the cache.
      Key_reads The number of physical reads of a key block from disk.
      Key_write_requests The number of requests to write a key block to the cache.
      Key_writes The number of physical writes of a key block to disk.
      Max_used_connections The maximum number of connections in use simultaneously.
      Not_flushed_key_blocks Keys blocks in the key cache that has changed but hasn't yet been flushed to disk.
      Not_flushed_delayed_rows Number of rows waiting to be written in INSERT DELAY queues.
      Open_tables オープンされているテーブル数
      Open_files Number of files that are open.
      Open_streams Number of streams that are open (used mainly for logging).
      Opened_tables Number of tables that have been opened.
      Rpl_status Status of failsafe replication. (Not yet in use).
      Select_full_join Number of joins without keys (If this is 0, you should carefully check the index of your tables).
      Select_full_range_join Number of joins where we used a range search on reference table.
      Select_range Number of joins where we used ranges on the first table. (It's normally not critical even if this is big.)
      Select_scan Number of joins where we did a full scan of the first table.
      Select_range_check Number of joins without keys where we check for key usage after each row (If this is 0, you should carefully check the index of your tables).
      Questions サーバーに送られたクエリの数
      Slave_open_temp_tables Number of temporary tables currently open by the slave thread
      Slave_running Is ON if this is a slave that is connected to a master.
      Slow_launch_threads Number of threads that have taken more than slow_launch_time to create.
      Slow_queries long_query_time 以上に時間のかかったクエリの数. 「4.9.5 The Slow Query Log (3.23.28以上)」節参照.
      Sort_merge_passes Number of merges passes the sort algoritm have had to do. If this value is large you should consider increasing sort_buffer.
      Sort_range Number of sorts that where done with ranges.
      Sort_rows Number of sorted rows.
      Sort_scan Number of sorts that where done by scanning the table.
      ssl_xxx Variables used by SSL; Not yet implemented.
      Table_locks_immediate Number of times a table lock was acquired immediately. Available after 3.23.33.
      Table_locks_waited Number of times a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimise your queries, and then either split your table(s) or use replication. Available after 3.23.33.
      Threads_cached Number of threads in the thread cache.
      Threads_connected 現在開いている接続数
      Threads_created Number of threads created to handle connections.
      Threads_running スリープ状態になっていないスレッドの数
      Uptime サーバーが走っている秒数

      上についてのいくつかコメント：

      • もし Opened_tables が大きければ、 table_cache 変数が小さすぎる のでしょう。
      • もし Key_reads が大きければ、 key_buffer_size が少なすぎるでしょう。 キャッシュ ミス レート は Key_reads/Key_read_requests で計算できます。
      • If Handler_read_rnd is big, then you probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
      • If Threads_created is big, you may want to increase the thread_cache_size variable. The cache hit rate can be calculated with Threads_created/Connections.
      • If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size variable to get the temporary tables memory-based instead of disk based.

      4.5.6.4 SHOW VARIABLES

      SHOW [GLOBAL | SESSION] VARIABLES [LIKE wild]

      SHOW VARIABLES は MySQL システム変数のいくつかの値を示します。 mysqlshow variables コマンドでも同じ情報が得られます。 もし標準値が適さないなら、ほとんどの変数を mysqld 起動時に コマンドラインのオプションとして与えることにより、変更できます。 「4.1.1 mysqld コマンド行オプション」節参照.

      The options GLOBAL and SESSION are new in MySQL 4.0.3. With GLOBAL you will get the variables that will be used for new connections to MySQL. With SESSION you will get the values that are in effect for the current connection. If you are not using either option, SESSION is used.

      You can change most options with the SET command. 「5.5.6 SET 構文」節参照.

      出力は以下のようになりますが、フォーマットや数はいくぶん違うでしょう： 

      +---------------------------------+------------------------------+
| Variable_name                   | Value                        |
+---------------------------------+------------------------------|
| back_log                        | 50                           |
| basedir                         | /usr/local/mysql             |
| bdb_cache_size                  | 8388572                      |
| bdb_log_buffer_size             | 32768                        |
| bdb_home                        | /usr/local/mysql             |
| bdb_max_lock                    | 10000                        |
| bdb_logdir                      |                              |
| bdb_shared_data                 | OFF                          |
| bdb_tmpdir                      | /tmp/                        |
| bdb_version                     | Sleepycat Software: ...	 |
| binlog_cache_size               | 32768                        |
| bulk_insert_buffer_size         | 8388608                      |
| character_set                   | latin1                       |
| character_sets                  | latin1 big5 czech euc_kr	 |
| concurrent_insert               | ON                           |
| connect_timeout                 | 5                            |
| convert_character_set           |                              |
| datadir                         | /usr/local/mysql/data/       |
| delay_key_write                 | ON                           |
| delayed_insert_limit            | 100                          |
| delayed_insert_timeout          | 300                          |
| delayed_queue_size              | 1000                         |
| flush                           | OFF                          |
| flush_time                      | 0                            |
| ft_boolean_syntax               | + -><()~*:""&|               |
| ft_min_word_len                 | 4                            |
| ft_max_word_len                 | 254                          |
| ft_max_word_len_for_sort        | 20                           |
| ft_stopword_file                | (built-in)                   |
| have_bdb                        | YES                          |
| have_innodb                     | YES                          |
| have_isam                       | YES                          |
| have_raid                       | NO                           |
| have_symlink                    | DISABLED                     |
| have_openssl                    | YES                          |
| have_query_cache                | YES                          |
| init_file                       |                              |
| innodb_additional_mem_pool_size | 1048576                      |
| innodb_buffer_pool_size         | 8388608                      |
| innodb_data_file_path           | ibdata1:10M:autoextend       |
| innodb_data_home_dir            |                              |
| innodb_file_io_threads          | 4                            |
| innodb_force_recovery           | 0                            |
| innodb_thread_concurrency       | 8                            |
| innodb_flush_log_at_trx_commit  | 0                            |
| innodb_fast_shutdown            | ON                           |
| innodb_flush_method             |                              |
| innodb_lock_wait_timeout        | 50                           |
| innodb_log_arch_dir             |                              |
| innodb_log_archive              | OFF                          |
| innodb_log_buffer_size          | 1048576                      |
| innodb_log_file_size            | 5242880                      |
| innodb_log_files_in_group       | 2                            |
| innodb_log_group_home_dir       | ./                           |
| innodb_mirrored_log_groups      | 1                            |
| interactive_timeout             | 28800                        |
| join_buffer_size                | 131072                       |
| key_buffer_size                 | 16773120                     |
| language                        | /usr/local/mysql/share/...   |
| large_files_support             | ON                           |
| local_infile                    | ON                           |
| locked_in_memory                | OFF                          |
| log                             | OFF                          |
| log_update                      | OFF                          |
| log_bin                         | OFF                          |
| log_slave_updates               | OFF                          |
| log_slow_queries                | OFF                          |
| log_warnings                    | OFF                          |
| long_query_time                 | 10                           |
| low_priority_updates            | OFF                          |
| lower_case_table_names          | OFF                          |
| max_allowed_packet              | 1047552                      |
| max_binlog_cache_size           | 4294967295                   |
| max_binlog_size                 | 1073741824                   |
| max_connections                 | 100                          |
| max_connect_errors              | 10                           |
| max_delayed_threads             | 20                           |
| max_heap_table_size             | 16777216                     |
| max_join_size                   | 4294967295                   |
| max_sort_length                 | 1024                         |
| max_user_connections            | 0                            |
| max_tmp_tables                  | 32                           |
| max_write_lock_count            | 4294967295                   |
| myisam_max_extra_sort_file_size | 268435456                    |
| myisam_max_sort_file_size       | 2147483647                   |
| myisam_recover_options          | force                        |
| myisam_sort_buffer_size         | 8388608                      |
| net_buffer_length               | 16384                        |
| net_read_timeout                | 30                           |
| net_retry_count                 | 10                           |
| net_write_timeout               | 60                           |
| open_files_limit                | 0                            |
| pid_file                        | /usr/local/mysql/name.pid    |
| port                            | 3306                         |
| protocol_version                | 10                           |
| read_buffer_size                | 131072                       |
| read_rnd_buffer_size            | 262144                       |
| rpl_recovery_rank               | 0                            |
| query_cache_limit               | 1048576                      |
| query_cache_size                | 0                            |
| query_cache_type                | ON                           |
| safe_show_database              | OFF                          |
| server_id                       | 0                            |
| slave_net_timeout               | 3600                         |
| skip_external_locking           | ON                           |
| skip_networking                 | OFF                          |
| skip_show_database              | OFF                          |
| slow_launch_time                | 2                            |
| socket                          | /tmp/mysql.sock              |
| sort_buffer_size                | 2097116                      |
| sql_mode                        | 0                            |
| table_cache                     | 64                           |
| table_type                      | MYISAM                       |
| thread_cache_size               | 3                            |
| thread_stack                    | 131072                       |
| tx_isolation                    | READ-COMMITTED               |
| timezone                        | EEST                         |
| tmp_table_size                  | 33554432                     |
| tmpdir                          | /tmp/:/mnt/hd2/tmp/          |
| version                         | 4.0.4-beta                   |
| wait_timeout                    | 28800                        |
+---------------------------------+------------------------------+

      Each option is described here. Values for buffer sizes, lengths, and stack sizes are given in bytes. これらの値の後ろに `K' や `M' を追加すると、キロバイト、 メガバイトになります。 例えば、16M は16メガバイトを示します。大文字小文字の区別はなく、 16M と 16m は同じ意味になります。

      • ansi_mode. もし mysqld が --ansi オプションで起動されているなら、ON. 「1.7.2 MySQLをANSIモードで実行する」節参照.
      • back_log MySQL が持てる未解決の接続要求の数です。これは MySQL スレッドがものすごく多くの接続要求をとても短い時間に得た時に、働き ます。接続のチェックと新しいスレッドの開始はメインスレッドにすこし時間 (しかしほんのわずか)がかかります。back_log は、MySQL が瞬間的に新 しい要求への回答を停止する前に、この短い時間の間にスタックできる接続数です。 短い期間に多くの接続を期待する場合にだけ、これを増加する必要があります。 いいかえるなら、これは TCP/IP 接続の入力 listen キューのサイズです。 オペレーティングシステムはこのキューの大きさを制限しています。 UNIX システムコール listen(2) のマニュアルページに、さらに詳細があります。 この値を最大限にしたい場合、お使いのOSのドキュメントを見てください。 back_log をこのOSの制限値より多く取ってもは全く効果ありません。
      • basedir The value of the --basedir option.
      • bdb_cache_size The buffer that is allocated to cache index and rows for BDB tables. If you don't use BDB tables, you should start mysqld with --skip-bdb to not waste memory for this cache.
      • bdb_log_buffer_size The buffer that is allocated to cache index and rows for BDB tables. If you don't use BDB tables, you should set this to 0 or start mysqld with --skip-bdb to not waste memory for this cache.
      • bdb_home The value of the --bdb-home option.
      • bdb_max_lock The maximum number of locks (10,000 by default) you can have active on a BDB table. You should increase this if you get errors of type bdb: Lock table is out of available locks or Got error 12 from ... when you have do long transactions or when mysqld has to examine a lot of rows to calculate the query.
      • bdb_logdir The value of the --bdb-logdir option.
      • bdb_shared_data Is ON if you are using --bdb-shared-data.
      • bdb_tmpdir The value of the --bdb-tmpdir option.
      • binlog_cache_size. The size of the cache to hold the SQL statements for the binary log during a transaction. If you often use big, multi-statement transactions you can increase this to get more performance. 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照.
      • bulk_insert_buffer_size (was myisam_bulk_insert_tree_size) MyISAM uses special tree-like cache to make bulk inserts (that is, INSERT ... SELECT, INSERT ... VALUES (...), (...), ..., and LOAD DATA INFILE) faster. This variable limits the size of the cache tree in bytes per thread. Setting it to 0 will disable this optimisation. Note: this cache is only used when adding data to non-empty table. Default value is 8 MB.
      • character_set The default character set.
      • character_sets The supported character sets.
      • concurrent_inserts もし ON (これはデフォルトです) なら、MySQL は、 SELECT クエリが実行されている MyISAM テーブルに対して、 同時に INSERT が使用できるようにします。 このオプションは mysqld のオプションに --safe か --skip-new を 指定することで OFF にできます。
      • connect_timeout mysqld サーバーが接続パケットを待つ秒数。 (Bad handshake を返すま での秒数)
      • datadir The value of the --datadir option.
      • delay_key_write Option for MyISAM tables. Can have one of the following values:
        OFF All CREATE TABLE ... DELAYED_KEY_WRITES are ignored.
        ON (デフォルト) MySQL は CREATE TABLE 文の DELAY_KEY_WRITE オプションを尊重します。
        ALL 開かれている全てのテーブルが DELAY_KEY_WRITE オプション指定されて 作成されたものとして扱われる
        DELAY_KEY_WRITE オプションが有効な場合、テーブルのキーバッファは、 毎回のインデックスの更新にはフラッシュされず、ただテーブルが閉じられたときにだけ フラッシュされます。 これはキーの書き出しを速くしますが、もしこれを使用するなら、 全てのテーブルを myisamchk --fast --force で自動的に検査するようにすべき です。
      • delayed_insert_limit delayed_insert_limit 個のレコードを挿入した後、 INSERT DELAYED ハンドラーは待たされている SELECT 文がないかチェックします。 もしあるなら、 挿入を続ける前にそれらの実行を許します。
      • delayed_insert_timeout どれぐらい INSERT DELAYED スレッドが INSERT 文を待つべきか。
      • delayed_queue_size What size queue (in rows) should be allocated for handling INSERT DELAYED. If the queue becomes full, any client that does INSERT DELAYED will wait until there is room in the queue again.
      • flush This is ON if you have started MySQL with the --flush option.
      • flush_time これがもし、非ゼロにセットされたなら、毎 flush_time 秒ごとに 全てのテーブルが閉じられます。 (リソースの解放とDiskへのsyncのために) We only recommend this option on Windows 9x/Me, or on systems where you have very little resources.
      • ft_boolean_syntax List of operators supported by MATCH ... AGAINST(... IN BOOLEAN MODE). 「6.8 MySQL Full-text Search」節参照.
      • ft_min_word_len The minimum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable. (This option is new for MySQL 4.0.)
      • ft_max_word_len The maximum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable. (This option is new for MySQL 4.0.)
      • ft_max_word_len_for_sort The maximum length of the word in a FULLTEXT index to be used in fast index recreation method in REPAIR, CREATE INDEX, or ALTER TABLE. Longer words are inserted the slow way. The rule of the thumb is as follows: with ft_max_word_len_for_sort increasing, MySQL will create bigger temporary files (thus slowing the process down, due to disk I/O), and will put fewer keys in one sort block (again, decreasing the efficiency). When ft_max_word_len_for_sort is too small, instead, MySQL will insert a lot of words into index the slow way, but short words will be inserted very quickly.
      • ft_stopword_file The file to read the list of stopwords for fulltext search from. All the words from the file will be used, comments are not honored. By default, built-in list of stopwords is used (as defined in `myisam/ft_static.c'). Setting this parameter to an empty string ("") will disable stopword filtering. Note: FULLTEXT indexes must be rebuilt after changing this variable. (This option is new for MySQL 4.0.10)
      • have_innodb YES if mysqld supports InnoDB tables. DISABLED if --skip-innodb is used.
      • have_bdb YES if mysqld supports Berkeley DB tables. DISABLED if --skip-bdb is used.
      • have_raid YES if mysqld supports the RAID option.
      • have_openssl YES if mysqld supports SSL (encryption) on the client/server protocol.
      • init_file サーバー起動時に、--init-file オプションに与えたファイルの名前です。 このファイルには、サーバー起動時に実行したい SQL 文を書いておきます。
      • interactive_timeout The number of seconds the server waits for activity on an interactive connection before closing it. An interactive client is defined as a client that uses the CLIENT_INTERACTIVE option to mysql_real_connect(). See also wait_timeout.
      • join_buffer_size このバッファは(インデックス無しの)完全な結合に使用されます。それは2つの テーブル間の完全な結合ごとに1回割り当てられます。インデックスの追加がで きない時、より速い完全な結合を得るために、これを増加してください。通常、 速い結合を得る一番良い方法は、インデックスを追加することです。
      • key_buffer_size インデックス・ブロックはバッファされ、そして全てのスレッドに共有されます。 key_buffer_size はインデックス・ブロックのためのバッファ・サイズです。 Increase this to get better index handling (for all reads and multiple writes) to as much as you can afford; 64M on a 256M machine that mainly runs MySQL is quite common. If you, however, make this too big (for instance more than 50% of your total memory) your system may start to page and become extremely slow. Remember that because MySQL does not cache data reads, you will have to leave some room for the OS filesystem cache. You can check the performance of the key buffer by doing SHOW STATUS and examine the variables Key_read_requests, Key_reads, Key_write_requests, and Key_writes. The Key_reads/Key_read_request ratio should normally be < 0.01. The Key_write/Key_write_requests is usually near 1 if you are using mostly updates/deletes but may be much smaller if you tend to do updates that affect many at the same time or if you are using DELAY_KEY_WRITE. 「4.5.6 SHOW 構文」節参照. To get even more speed when writing many rows at the same time, use LOCK TABLES. 「6.7.2 LOCK TABLES/UNLOCK TABLES 構文」節参照.
      • language The language used for error messages.
      • large_file_support If mysqld was compiled with options for big file support.
      • locked_in_memory If mysqld was locked in memory with --memlock
      • log If logging of all queries is enabled.
      • log_update If the update log is enabled.
      • log_bin If the binary log is enabled.
      • log_slave_updates If the updates from the slave should be logged.
      • long_query_time もしあるクエリがこの値(秒)より時間がかかれば、Slow_queries カウンター が増やされます。 If you are using --log-slow-queries, the query will be logged to the slow query logfile. This value is measured in real time, not CPU time, so a query that may be under the threshold on a lightly loaded system may be above the threshold on a heavily loaded one. 「4.9.5 The Slow Query Log (3.23.28以上)」節参照.
      • lower_case_table_names If set to 1 table names are stored in lowercase on disk and table name comparisons will be case-insensitive. From version 4.0.2, this option also applies to database names. 「6.1.3 名前のケース依存性」節参照.
      • max_allowed_packet 一つのパケットの最大サイズ。メッセージバッファは net_buffer_length バイト に初期化されますが、 max_allowed_packetまで大きくすることができます。このデフォルト値は、 大きなパケット、間違ったパケットをを受けるには小さい値です。 大きな BLOB を使用している場合は、これを増加する必要があります。使用した い最大の BLOB と同じくらい大きくするべきです。 The protocol limits for max_allowed_packet is 16M in MySQL 3.23 and 1G in MySQL 4.0.
      • max_binlog_cache_size If a multi-statement transaction requires more than this amount of memory, one will get the error "Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage".
      • max_binlog_size バージョン 3.23.33 以降より有効. もしバイナリ(レプリケーション)ログファイルの大きさが、これに指定された数を 超えて書かれてしまった場合、ログファイルが自動でローテートされます。 1024<=max_binlog_size<=1GB までの 範囲の値しか与えれません。デフォルトは 1GB です。
      • max_connections 許される同時クライアントの数。これを増加する場合は、mysqld が持つファイ ルディスクリプタの数を増やす必要があるでしょう。 後述のファイルデスクリプターの制限の説明を参照のこと。 「A.2.5 Too many connections エラー」節参照.
      • max_connect_errors もしあるホストからの接続中断がこの値を以上になった場合、これ以後、 そのホストからの接続を拒絶します。FLUSH HOSTS コマンドで ホストの拒否を解除できます。
      • max_delayed_threads この値を超えて INSERT DELAYED を扱うスレッドを起動できません。 もし全ての INSERT DELAYED スレッドが使用されていて、さらに新しいテーブルに データを挿入しようとすると、そのレコードは DELAYED が与えられていない 場合と同様に挿入されます。
      • max_heap_table_size Don't allow creation of heap tables bigger than this.
      • max_join_size max_join_size より多いレコードを触るとエラーが返ります。長い時間をかけて 百万行を返すような WHERE なしの結合を作成するようなユーザを持って いる場合にこれを設定してください。
      • max_sort_length BLOB または TEXT 項目上でソートする時に使用するバイト数。 (最初の max_sort_length バイトだけがそれぞれの値で使用でき、残りは無視さ れます)
      • max_user_connections The maximum number of active connections for a single user (0 = no limit).
      • max_tmp_tables (このオプションはまだなにも行いません). クライアントが同時にオープンできるテーブル数の最大値。
      • max_write_lock_count After this many write locks, allow some read locks to run in between.
      • myisam_recover_options The value of the --myisam-recover option.
      • myisam_sort_buffer_size The buffer that is allocated when sorting the index when doing a REPAIR or when creating indexes with CREATE INDEX or ALTER TABLE.
      • myisam_max_extra_sort_file_size. If the temporary file used for fast index creation would be bigger than using the key cache by the amount specified here, then prefer the key cache method. This is mainly used to force long character keys in large tables to use the slower key cache method to create the index. Note that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version.
      • myisam_max_sort_file_size The maximum size of the temporary file MySQL is allowed to use while recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. If the file-size would be bigger than this, the index will be created through the key cache (which is slower). Note that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version.
      • net_buffer_length 通信バッファがクエリ間でこのサイズにリセットされます。これは通常は変更す べきではありませんが、とても小さなメモリしかない場合は、これを期待される クエリのサイズに設定してください。 ( これは、クライアントから送られてくるSQL文の長さ分あればいいでしょう。 もし構文がこの値をこえた場合、バッファは自動的に大きくなります。 ただし max_allowed_packet バイトまでです)
      • net_read_timeout Number of seconds to wait for more data from a connection before aborting the read. Note that when we don't expect data from a connection, the timeout is defined by write_timeout. See also slave_net_timeout.
      • net_retry_count If a read on a communication port is interrupted, retry this many times before giving up. This value should be quite high on FreeBSD as internal interrupts are sent to all threads.
      • net_write_timeout Number of seconds to wait for a block to be written to a connection before aborting the write.
      • open_files_limit If this is not 0, then mysqld will use this value to reserve file descriptors to use with setrlimit(). If this value is 0 then mysqld will reserve max_connections*5 or max_connections + table_cache*2 (whichever is larger) number of files. You should try increasing this if mysqld gives you the error 'Too many open files'.
      • pid_file The value of the --pid-file option.
      • port The value of the --port option.
      • protocol_version The protocol version used by the MySQL server.
      • read_buffer_size (ver. 4.0.3 未満では record_buffer) 順序スキャンを行う各スレッドが、スキャンするテーブル毎に、このサイズのバッ ファを割り当てます。多くの順序スキャンを行う場合は、これを増加させてくだ さい。
      • record_rnd_buffer_size When reading rows in sorted order after a sort, the rows are read through this buffer to avoid a disk seeks. Can improve ORDER BY by a lot if set to a high value. As this is a thread-specific variable, one should not set this big globally, but just change this when running some specific big queries.
      • query_cache_limit Don't cache results that are bigger than this. (Default 1M).
      • query_cache_size The memory allocated to store results from old queries. If this is 0, the query cache is disabled (default).
      • query_cache_type This may be set (only numeric) to
        Value Alias Comment
        0 OFF Don't cache or retrieve results.
        1 ON Cache all results except SELECT SQL_NO_CACHE ... queries.
        2 DEMAND Cache only SELECT SQL_CACHE ... queries.
      • safe_show_database Don't show databases for which the user doesn't have any database or table privileges. This can improve security if you're concerned about people being able to see what databases other users have. See also skip_show_database.
      • server_id The value of the --server-id option.
      • skip_locking Is OFF if mysqld uses external locking.
      • skip_networking Is ON if we only allow local (socket) connections.
      • skip_show_database This prevents people from doing SHOW DATABASES if they don't have the PROCESS privilege. This can improve security if you're concerned about people being able to see what databases other users have. See also safe_show_database.
      • slave_net_timeout Number of seconds to wait for more data from a master/slave connection before aborting the read.
      • slow_launch_time If creating the thread takes longer than this value (in seconds), the Slow_launch_threads counter will be incremented.
      • socket The Unix socket used by the server.
      • sort_buffer_size ソートを行う必要がある各スレッドがこのサイズのバッファを割り当てます。よ り速い ORDER BY または GROUP BY のためにはこれを増やしてく ださい。 「A.4.4 MySQL が一時ファイルを格納する場所」節参照.
      • table_cache 全てのスレッドについてのオープンテーブルの数。これを増加する場合は、 mysqld が要求するオープンファイルディスクリプタの数も 増加することに注意しないといけません。 You can check if you need to increase the table cache by checking the Opened_tables variable. 「4.5.6.3 SHOW STATUS」節参照. If this variable is big and you don't do FLUSH TABLES a lot (which just forces all tables to be closed and reopenend), then you should increase the value of this variable. For more information about the table cache, see 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節.
      • table_type The default table type.
      • thread_cache_size How many threads we should keep in a cache for reuse. When a client disconnects, the client's threads are put in the cache if there aren't more than thread_cache_size threads from before. All new threads are first taken from the cache, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. (Normally this doesn't give a notable performance improvement if you have a good thread implementation.) By examing the difference between the Connections and Threads_created status variables ( 「4.5.6.3 SHOW STATUS」節 for details) you can see how efficient thread cache is.
      • thread_concurrency On Solaris, mysqld will call thr_setconcurrency() with this value. thr_setconcurrency() permits the application to give the threads system a hint for the desired number of threads that should be run at the same time.
      • thread_stack 各スレッドのスタックの大きさ。crash-me によって検出される多く の制限がこれに依存します。デフォルトでは、通常のオペレーションに対して 十分とってあります。 「5.1.4 The MySQL Benchmark Suite」節参照.
      • timezone The timezone for the server.
      • tmp_table_size メモリー内の 一時テーブルがこの値を超えようとした場合、MySQL は 自動的に、これを、disk ベースの MyISAM テーブルに変換します。 多くの先進的な GROUP BY クエリを行う場合は、 この tmp_table_size を増加してください。
      • tmpdir The directory used for temporary files and temporary tables. Starting from MySQL 4.1, it can be set to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion. This feature can be used to spread load between several physical disks.
      • version The version number for the server.
      • wait_timeout インタラクティブではないアクティブなコネクションを 閉じるのに、にサーバーが待つ秒数。 On thread startup SESSION.WAIT_TIMEOUT is initialised from GLOBAL.WAIT_TIMEOUT or GLOBAL.INTERACTIVE_TIMEOUT depending on the type of client (as defined by the CLIENT_INTERACTIVE connect option). See also interactive_timeout.

      The manual section that describes tuning MySQL contains some information of how to tune the above variables. 「5.5.2 サーバーパラメーターのチューニング」節参照.

      4.5.6.5 SHOW LOGS

      SHOW LOGS shows you status information about existing log files. It currently only displays information about Berkeley DB log files.

      • File shows the full path to the log file
      • Type shows the type of the log file (BDB for Berkeley DB log files)
      • Status shows the status of the log file (FREE if the file can be removed, or IN USE if the file is needed by the transaction subsystem)

      4.5.6.6 SHOW PROCESSLIST

      SHOW [FULL] PROCESSLIST はどのスレッドが走っているかを表示します。 mysqlshow processlist コマンドでも同じ情報が得られます。 もし SUPER 権限があるなら、全てのスレッドがみれます。 しかし権限がないなら、自分のスレッドしか見れません。 「4.5.5 KILL 構文」節参照. (SUPERは4.0.2以上。4.0.2未満では PROCESS権限があるだけで全てのスレッドが見れた) FULL オプションを使用しない場合、各クエリの最初の100文字だけが表示 されます。

      Starting from 4.0.12, MySQL reports the hostname for TCP/IP connections as hostname:client_port to make it easier to find out which client is doing what.

      This command is very useful if you get the 'too many connections' error message and want to find out what's going on. MySQL reserves one extra connection for a client with the SUPER privilege to ensure that you should always be able to login and check the system (assuming you are not giving this privilege to all your users).

      Some states commonly seen in mysqladmin processlist

      • Checking table The thread is performing [automatic] checking of the table.
      • Closing tables Means that the thread is flushing the changed table data to disk and closing the used tables. This should be a fast operation. If not, then you should check that you don't have a full disk or that the disk is not in very heavy use.
      • Connect Out Slave connecting to master.
      • Copying to tmp table on disk The temporary result set was larger than tmp_table_size and the thread is now changing the in memory-based temporary table to a disk based one to save memory.
      • Creating tmp table The thread is creating a temporary table to hold a part of the result for the query.
      • deleting from main table When executing the first part of a multi-table delete and we are only deleting from the first table.
      • deleting from reference tables When executing the second part of a multi-table delete and we are deleting the matched rows from the other tables.
      • Flushing tables The thread is executing FLUSH TABLES and is waiting for all threads to close their tables.
      • Killed Someone has sent a kill to the thread and it should abort next time it checks the kill flag. The flag is checked in each major loop in MySQL, but in some cases it may still take a short time for the thread to die. If the thread is locked by some other thread, the kill will take affect as soon as the other thread releases it's lock.
      • Sending data The thread is processing rows for a SELECT statement and is also sending data to the client.
      • Sorting for group The thread is doing a sort to satsify a GROUP BY.
      • Sorting for order The thread is doing a sort to satsify a ORDER BY.
      • Opening tables This simply means that the thread is trying to open a table. This is should be very fast procedure, unless something prevents opening. For example an ALTER TABLE or a LOCK TABLE can prevent opening a table until the command is finished.
      • Removing duplicates The query was using SELECT DISTINCT in such a way that MySQL couldn't optimise that distinct away at an early stage. Because of this MySQL has to do an extra stage to remove all duplicated rows before sending the result to the client.
      • Reopen table The thread got a lock for the table, but noticed after getting the lock that the underlying table structure changed. It has freed the lock, closed the table and is now trying to reopen it.
      • Repair by sorting The repair code is using sorting to create indexes.
      • Repair with keycache The repair code is using creating keys one by one through the key cache. This is much slower than Repair by sorting.
      • Searching rows for update The thread is doing a first phase to find all matching rows before updating them. This has to be done if the UPDATE is changing the index that is used to find the involved rows.
      • Sleeping The thread is wating for the client to send a new command to it.
      • System lock The thread is waiting for getting to get a external system lock for the table. If you are not using multiple mysqld servers that are accessing the same tables, you can disable system locks with the --skip-external-locking option.
      • Upgrading lock The INSERT DELAYED handler is trying to get a lock for the table to insert rows.
      • Updating The thread is searching for rows to update and updating them.
      • User Lock The thread is waiting on a GET_LOCK().
      • Waiting for tables The thread got a notification that the underlying structure for a table has changed and it needs to reopen the table to get the new structure. To be able to reopen the table it must however wait until all other threads have closed the table in question. This notification happens if another thread has used FLUSH TABLES or one of the following commands on the table in question: FLUSH TABLES table_name, ALTER TABLE, RENAME TABLE, REPAIR TABLE, ANALYZE TABLE or OPTIMIZE TABLE.
      • waiting for handler insert The INSERT DELAYED handler has processed all inserts and are waiting to get new ones.

      Most states are very quick operations. If threads last in any of these states for many seconds, there may be a problem around that needs to be investigated.

      There are some other states that are not mentioned previously, but most of these are only useful to find bugs in mysqld.

      4.5.6.7 SHOW GRANTS

      SHOW GRANTS FOR user はユーザの許可を複製するために発行する必要があ る grant コマンドをリストします。 

      mysql> SHOW GRANTS FOR root@localhost;
+---------------------------------------------------------------------+
| Grants for root@localhost                                           |
+---------------------------------------------------------------------+
| GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' WITH GRANT OPTION |
+---------------------------------------------------------------------+

      To list grants for the current session one may use CURRENT_USER() function (new in version 4.0.6) to find out what user the session was authentificated as. 「6.3.6.2 その他の関数」節参照.

      4.5.6.8 SHOW CREATE TABLE

      Shows a CREATE TABLE statement that will create the given table: 

      mysql> SHOW CREATE TABLE t\G
*************************** 1. row ***************************
       Table: t
Create Table: CREATE TABLE t (
  id int(11) default NULL auto_increment,
  s char(60) default NULL,
  PRIMARY KEY (id)
) TYPE=MyISAM

      SHOW CREATE TABLE will quote table and column names according to SQL_QUOTE_SHOW_CREATE option. 「5.5.6 SET 構文」節.

      4.5.6.9 SHOW WARNINGS | ERRORS

      SHOW WARNINGS [LIMIT #]
SHOW ERRORS [LIMIT #]

      This command is implemented in MySQL 4.1.0.

      It shows the errors, warnings and notes that one got for the last command. The errors/warnings are reset for each new command that uses a table.

      The MySQL server sends back the total number of warnings and errors you got for the last commend; This can be retrieved by calling mysql_warning_count().

      Up to max_error_count messages are stored (Global and thread specific variable).

      You can retrieve the number of errors from @error_count and warnings from @warning_count.

      SHOW WARNINGS shows all errors, warnings and notes you got for the last command while SHOW ERRORS only shows you the errors. 

      mysql> DROP TABLE IF EXISTS no_such_table;
mysql> SHOW WARNINGS;

+-------+------+-------------------------------+
| Level | Code | Message                       |
+-------+------+-------------------------------+
| Note  | 1051 | Unknown table 'no_such_table' |
+-------+------+-------------------------------+

      4.5.6.10 SHOW TABLE TYPES

      SHOW TABLE TYPES

      This command is implemented in MySQL 4.1.0.

      SHOW TABLE TYPES shows you status information about the table types. This is particulary useful for checking if a table type is supported; or to see what is the default table type is. 

      mysql> SHOW TABLE TYPES;

+--------+---------+-----------------------------------------------------------+
| Type   | Support | Comment                                                   |
+--------+---------+-----------------------------------------------------------+
| MyISAM | DEFAULT | Default type from 3.23 with great performance             |
| HEAP   | YES     | Hash based, stored in memory, useful for temporary tables |
| MERGE  | YES     | Collection of identical MyISAM tables                     |
| ISAM   | YES     | Obsolete table type; Is replaced by MyISAM                |
| InnoDB | YES     | Supports transactions, row-level locking and foreign keys |
| BDB    | NO      | Supports transactions and page-level locking              |
+--------+---------+-----------------------------------------------------------+
6 rows in set (0.00 sec)

      The 'Support' option DEFAULT indicates whether the perticular table type is supported, and which is the default type. If the server is started with --default-table-type=InnoDB, then the InnoDB 'Support' field will have the value DEFAULT.

      4.5.6.11 SHOW PRIVILEGES

      SHOW PRIVILEGES

      This command is implemented in MySQL 4.1.0.

      SHOW PRIVILEGES shows the list of system privileges that the underlying MySQL server supports. 

      mysql> show privileges;
+------------+--------------------------+-------------------------------------------------------+
| Privilege  | Context                  | Comment                                               |
+------------+--------------------------+-------------------------------------------------------+
| Select     | Tables                   | To retrieve rows from table                           |
| Insert     | Tables                   | To insert data into tables                            |
| Update     | Tables                   | To update existing rows                               |
| Delete     | Tables                   | To delete existing rows                               |
| Index      | Tables                   | To create or drop indexes                             |
| Alter      | Tables                   | To alter the table                                    |
| Create     | Databases,Tables,Indexes | To create new databases and tables                    |
| Drop       | Databases,Tables         | To drop databases and tables                          |
| Grant      | Databases,Tables         | To give to other users those privileges you possess   |
| References | Databases,Tables         | To have references on tables                          |
| Reload     | Server Admin             | To reload or refresh tables, logs and privileges      |
| Shutdown   | Server Admin             | To shutdown the server                                |
| Process    | Server Admin             | To view the plain text of currently executing queries |
| File       | File access on server    | To read and write files on the server                 |
+------------+--------------------------+-------------------------------------------------------+
14 rows in set (0.00 sec)

      4.6 MySQL Localisation and International Usage

      4.6.1 データとソートに使用されるキャラクター・セット

      デフォルトでは、MySQL は スウェーデン語／フィンランド語に一致する ISO8859-1 (Latin1) キャラクター・セットをソートに使用します。これは USA と西 ヨーロッパに適したキャラクター・セットです。

      All standard MySQL binaries are compiled with --with-extra-charsets=complex. This will add code to all standard programs to be able to handle latin1 and all multi-byte character sets within the binary. Other character sets will be loaded from a character-set definition file when needed.

      キャラクター・セットは名前として許される文字と、ORDER BY と GROUP BY コマンドによってソートされる方法を決定します。 キャラクターセットは、名前として使用してもよい文字と SELECT 構文中の ORDER BY と GROUP BY コマンドを用いたソート方法を決定します。

      You can change the character set with the --default-character-set option when you start the server. The character sets available depend on the --with-charset=charset and --with-extra-charsets= list-of-charset | complex | all options to configure, and the character set configuration files listed in `SHAREDIR/charsets/Index'. 「2.3.3 典型的な configure オプション」節参照.

      もし MySQL が実行中にキャラクター・セットを変更するならば、 （これはソートの順番も変わります）、全てのテーブルに対して myisamchk -r -q --set-character-set=charset を実行しなくてはなりません。 インデックスがただしい順番で並んでいないかもしれないからです。

      クライアントが MySQL サーバに接続したとき、サーバは使用している デフォルトのキャラクター・セットをクライアントに送ります。 これを受け取ったクライアントは、キャラクター・セットを切り替えます。

      SQL クエリの文字列をエスケープする場合には、 mysql_real_escape_string() を 使用するべきです。 mysql_real_escape_string() は、最初のパラメタとして MySQL へのコネクション・ハンドルを与える以外は、 古い mysql_escape_string() 関数と同じです。

      もしクライアントがサーバがインストールされているところ(パス)とは違う パスでコンパイルされていて、 MySQL をコンフィギャしたユーザーが すべてのキャラクター・セットを MySQL バイナリに含めていない場合には、 どこに必要とされるキャラクター・セットの追加情報があるかを、クライアントに 教えなくてはなりません。もしサーバとクライアントが違うキャラクター・セットで動作し ているならば。

      これは MySQL オプションファイルに次のように記述することで可能です： 

      [client]
character-sets-dir=/usr/local/mysql/share/mysql/charsets

      ここで、パスはダイナミック MySQL キャラクター・セットが保存されている場所 です。

      クライアントに、キャラクター・セットを強制することも可能です： 

      [client]
default-character-set=character-set-name

      しかし通常はこれは不要です。

      4.6.1.1 German character set

      To get German sorting order, you should start mysqld with --default-character-set=latin1_de. This will give you the following characteristics.

      When sorting and comparing string's the following mapping is done on the strings before doing the comparison: 

      a  ->  ae
o  ->  oe
u  ->  ue
s  ->  ss

      All accented characters, are converted to their un-accented uppercase counterpart. All letters are converted to uppercase.

      When comparing strings with LIKE the one -> two character mapping is not done. All letters are converted to uppercase. Accent are removed from all letters except: , , , , and .

      4.6.2 Non-English Error Messages

      mysqld は次の言語でエラーメッセージを提供できます: チェコ語, デンマーク語, オランダ語, 英語(デフォルト), Estonia, フランス語, ドイツ語, ギリシャ語, ハンガリー語, イタリア語, 日本語, 韓国語, ノルウェー語, 新ノルウェー語,ポーランド語, ポルトガル語, スペイン語そしてスウェーデン語。

      ある言語で mysqld を開始するためには --language=lang また は -L lang スイッチの一つを使います: 

      shell> mysqld --language=swedish

      or: 

      shell> mysqld --language=/usr/local/share/swedish

      言語名は全て小文字であることに注意してください。

      言語ファイルは(デフォルトでは)次の場所にあります。 `mysql_base_dir/share/LANGUAGE/'.

      エラーメッセージファイルを更新したい場合は、 `errmsg.txt' ファイルを編集し、 `errmsg.sys' ファイルを作成するために以下のように実行します: 

      shell> comp_err errmsg.txt errmsg.sys

      もし MySQL を新しいものにアップグレードしたなら、以前修正した部分と同じ ところに、 新しい `errmsg.txt' ファイルに修正をほどこしてください。

      4.6.3 新しいキャラクター・セットの追加

      他のキャラクタ・セットを MySQL に追加するには、 以下の手順で行ないます。

      そのキャラクター・セットが、simple か complex かを決めます。 もしそのキャラクター・セットがソートを行なうために特別な文字参照の ルーチンを必要としなくて、マルチバイト文字のサポートも必要としないのであれば、 そのキャラクター・セットは simple です。 もしどちらかの特徴を必要とするのであれば、それは complex です。

      例えば、latin1 と danish は simple キャラクター・セットで、 big5 や czech は complex キャラクター・セットです。

      以下のセクションでは、あなたがキャラクター・セットに MYSET という名前を つけていると仮定します。

      For a simple character set do the following:

      1. MYSET を `sql/share/charsets/Index' ファイルの最後に追加。 一意な番号を与えます。
      2. `sql/share/charsets/MYSET.conf' ファイルを作成. (`sql/share/charsets/latin1.conf' をベースにしてよいでしょう). The syntax for the file very simple:
        • Comments start with a '#' character and proceed to the end of the line.
        • Words are separated by arbitrary amounts of whitespace.
        • When defining the character set, every word must be a number in hexadecimal format
        • The ctype array takes up the first 257 words. The to_lower[], to_upper[] and sort_order[] arrays take up 256 words each after that.
        「4.6.4 The Character Definition Arrays」節参照.
      3. Add the character set name to the CHARSETS_AVAILABLE and COMPILED_CHARSETS lists in configure.in.
      4. Reconfigure, recompile, and test.

      For a complex character set do the following:

      1. `strings/ctype-MYSET.c' ファイルを MySQL のソースディレクトリ以下 に作成します。
      2. MYSET を `sql/share/charsets/Index' ファイルの最後に追加。 一意な番号を与えます。
      3. 必要な定義されるものを調べるために、既存の `ctype-*.c' ファイルの一つを見てく ださい。このファイル中で使用する配列の名前は、 ctype_MYSET, to_lower_MYSET のようにしなければいけないことに注意し てください。 This corresponds to the arrays in the simple character set. 「4.6.4 The Character Definition Arrays」節参照. For a complex character set
      4. `ctype-*.c' ファイルの先頭付近に、以下のようなコメントを書きます： 
        /*
 * This comment is parsed by configure to create ctype.c,
 * so don't change it unless you know what you are doing.
 *
 * .configure. number_MYSET=MYNUMBER
 * .configure. strxfrm_multiply_MYSET=N
 * .configure. mbmaxlen_MYSET=N
 */
        configure プログラムは、MySQL ライブラリに自動的に キャラクター・セットを含めるために、このコメントを使用します。 The strxfrm_multiply and mbmaxlen lines will be explained in the following sections. Only include these if you need the string collating functions or the multi-byte character set functions, respectively.
      5. 以下の関数を作成しなくてはなりません：
        • my_strncoll_MYSET()
        • my_strcoll_MYSET()
        • my_strxfrm_MYSET()
        • my_like_range_MYSET()
        「4.6.5 String Collating Support」節参照.
      6. キャラクター・セット名を、configure.in 中の CHARSETS_AVAILABLE と COMPILED_CHARSETS に追加します。
      7. Reconfigure, recompile, and test.

      The file `sql/share/charsets/README' includes some more instructions.

      If you want to have the character set included in the MySQL distribution, mail a patch to internals@lists.mysql.com.

      4.6.4 The Character Definition Arrays

      to_lower[] と to_upper[] は、それぞれのキャラクターセットに於ける 大文字、小文字の対応を定義した、単純な配列です。 例えば： 

      to_lower['A'] should contain 'a'
to_upper['a'] should contain 'A'

      sort_order[] は文字がどのように比較され、ソートされるべきかのマップです。 本当に多くの(しかし全てのキャラクタセットではありません)セットでは、 これは to_upper[] と同じです (ケース非依存ソート)。 MySQL は sort_order[character] の値を元に文字をソートします。 MySQL will sort characters based on the value of sort_order[character]. For more complicated sorting rules, see the discussion of string collating below. 「4.6.5 String Collating Support」節参照.

      ctype[] は各文字を説明するビットの配列で、1かたまりのビット列が1文字を定 義します。 ( to_lower[], to_upper[],sort_order[]は、文字の値でインデッ クスされますが、 ctype[]は文字の値+1 でインデックスされます。

      これは EOF を操作するためにずいぶん前から使われているので、この方法を使用してい ます。) `m_ctype.h' に次のビットマスクの定義を見ることができます: 

      #define _U      01      /* Uppercase */
#define _L      02      /* Lowercase */
#define _N      04      /* Numeral (digit) */
#define _S      010     /* Spacing character */
#define _P      020     /* Punctuation */
#define _C      040     /* Control character */
#define _B      0100    /* Blank */
#define _X      0200    /* heXadecimal digit */

      それぞれの文字に対する ctype[] は、文字を確定するために ビット列と組になっていなければなりません。 たとえば、'A' は大文字定義 (_U) と 16進定義 (_X) 両方ともに 属するので、ctype['A'+1] は以下の値を含まなくてはなりません: 

      _U + _X = 01 + 0200 = 0201

      4.6.5 String Collating Support

      If the sorting rules for your language are too complex to be handled with the simple sort_order[] table, you need to use the string collating functions.

      Right now the best documentation on this is the character sets that are already implemented. Look at the big5, czech, gbk, sjis, and tis160 character sets for examples.

      You must specify the strxfrm_multiply_MYSET=N value in the special comment at the top of the file. N should be set to the maximum ratio the strings may grow during my_strxfrm_MYSET (it must be a positive integer).

      4.6.6 マルチバイト文字のサポート

      If your want to add support for a new character set that includes multi-byte characters, you need to use the multi-byte character functions.

      Right now the best documentation on this is the character sets that are already implemented. Look at the euc_kr, gb2312, gbk, sjis, and ujis character sets for examples. These are implemented in the `ctype-'charset'.c' files in the `strings' directory.

      You must specify the mbmaxlen_MYSET=N value in the special comment at the top of the source file. N should be set to the size in bytes of the largest character in the set.

      4.6.7 Problems With Character Sets

      If you try to use a character set that is not compiled into your binary, you can run into a couple of different problems:

      • Your program has a wrong path to where the character sets are stored. (Default `/usr/local/mysql/share/mysql/charsets'). This can be fixed by using the --character-sets-dir option to the program in question.
      • The character set is a multi-byte character set that can't be loaded dynamically. In this case you have to recompile the program with the support for the character set.
      • The character set is a dynamic character set, but you don't have a configure file for it. In this case you should install the configure file for the character set from a new MySQL distribution.
      • Your `Index' file doesn't contain the name for the character set. 
        ERROR 1105: File '/usr/local/share/mysql/charsets/?.conf' not found
(Errcode: 2)
        In this case you should either get a new Index file or add by hand the name of any missing character sets.

      For MyISAM tables, you can check the character set name and number for a table with myisamchk -dvv table_name.

      4.7 MySQL サーバー サイド の スクリプトとユーティリティ

      4.7.1 Overview of the Server-Side Scripts and Utilities

      All MySQL programs take many different options. However, every MySQL program provides a --help option that you can use to get a full description of the program's different options. For example, try mysql --help.

      You can override default options for all standard programs with an option file. 「4.1.2 `my.cnf' オプションファイル」節.

      The following list briefly describes the server-side MySQL programs:

      myisamchk
      Utility to describe, check, optimise, and repair MySQL tables. Because myisamchk has many functions, it is described in its own chapter. 「4 データベース管理」節参照.
      make_binary_distribution
      Makes a binary release of a compiled MySQL. This could be sent by FTP to `/pub/mysql/Incoming' on support.mysql.com for the convenience of other MySQL users.
      mysqlbug
      The MySQL bug report script. This script should always be used when filing a bug report to the MySQL list.
      mysqld
      The SQL daemon. This should always be running.
      mysql_install_db
      Creates the MySQL grant tables with default privileges. This is usually executed only once, when first installing MySQL on a system.

      4.7.2 safe_mysqld, The Wrapper Around mysqld

      Note that in MySQL 4.0 safe_mysqld was renamed to mysqld_safe.

      safe_mysqld is the recommended way to start a mysqld daemon on Unix. safe_mysqld adds some safety features such as restarting the server when an error occurs and logging run-time information to a log file.

      If you don't use --mysqld=# or --mysqld-version=# safe_mysqld will use an executable named mysqld-max if it exists. If not, safe_mysqld will start mysqld. This makes it very easy to test to use mysqld-max instead of mysqld; just copy mysqld-max to where you have mysqld and it will be used.

      Normally one should never edit the safe_mysqld script, but instead put the options to safe_mysqld in the [safe_mysqld] section in the `my.cnf' file. safe_mysqld will read all options from the [mysqld], [server] and [safe_mysqld] sections from the option files. 「4.1.2 `my.cnf' オプションファイル」節参照.

      Note that all options on the command-line to safe_mysqld are passed to mysqld. If you wants to use any options in safe_mysqld that mysqld doesn't support, you must specify these in the option file.

      Most of the options to safe_mysqld are the same as the options to mysqld. 「4.1.1 mysqld コマンド行オプション」節参照.

      safe_mysqld supports the following options:

      --basedir=path
      --core-file-size=#
      Size of the core file mysqld should be able to create. Passed to ulimit -c.
      --datadir=path
      --defaults-extra-file=path
      --defaults-file=path
      --err-log=path (this is marked obsolete in 4.0; Use --log-error instead)
      --log-error=path
      Write the error log to the above file. 「4.9.1 The Error Log」節参照.
      --ledir=path
      Path to mysqld
      --log=path
      --mysqld=mysqld-version
      Name of the mysqld version in the ledir directory you want to start.
      --mysqld-version=version
      Similar to --mysqld= but here you only give the suffix for mysqld. For example if you use --mysqld-version=max, safe_mysqld will start the ledir/mysqld-max version. If the argument to --mysqld-version is empty, ledir/mysqld will be used.
      --no-defaults
      --open-files-limit=#
      Number of files mysqld should be able to open. Passed to ulimit -n. Note that you need to start safe_mysqld as root for this to work properly!
      --pid-file=path
      --port=#
      --socket=path
      --timezone=#
      Set the timezone (the TZ) variable to the value of this parameter.
      --user=#

      The safe_mysqld script is written so that it normally is able to start a server that was installed from either a source or a binary version of MySQL, even if these install the server in slightly different locations. safe_mysqld expects one of these conditions to be true:

      • The server and databases can be found relative to the directory from which safe_mysqld is invoked. safe_mysqld looks under its working directory for `bin' and `data' directories (for binary distributions) or for `libexec' and `var' directories (for source distributions). This condition should be met if you execute safe_mysqld from your MySQL installation directory (for example, `/usr/local/mysql' for a binary distribution).
      • If the server and databases cannot be found relative to the working directory, safe_mysqld attempts to locate them by absolute pathnames. Typical locations are `/usr/local/libexec' and `/usr/local/var'. The actual locations are determined when the distribution was built from which safe_mysqld comes. They should be correct if MySQL was installed in a standard location.

      Because safe_mysqld will try to find the server and databases relative to its own working directory, you can install a binary distribution of MySQL anywhere, as long as you start safe_mysqld from the MySQL installation directory: 

      shell> cd mysql_installation_directory
shell> bin/safe_mysqld &

      If safe_mysqld fails, even when invoked from the MySQL installation directory, you can modify it to use the path to mysqld and the pathname options that are correct for your system. Note that if you upgrade MySQL in the future, your modified version of safe_mysqld will be overwritten, so you should make a copy of your edited version that you can reinstall.

      4.7.3 mysqld_multi, 複数の MySQL サーバーを管理するプログラム

      mysqld_multi is meant for managing several mysqld processes that listen for connections on different Unix sockets and TCP/IP ports. このプログラムは、`my.cnf' ファイル (もしくは、--config-file=... で与えられたファイル)の [mysqld#] (ここで # は 1から始まる数字) と命名されたセクションを探します。 This number is referred to in the following discussion as the option group number, or GNR. Group numbers distinquish option groups from one another and are used as arguments to mysqld_multi to specify which servers you want to start, stop, or obtain status for. Options listed in these groups should be the same as you would use in the usual [mysqld] group used for starting mysqld. (See, for example, 「2.4.3 MySQL の自動起動と自動停止」節.) However, for mysqld_multi, be sure that each group includes options for values such as the port, socket, etc., to be used for each individual mysqld process.

      mysqld_multi is invoked using the following syntax: 

      Usage: mysqld_multi [OPTIONS] {start|stop|report} [GNR,GNR,GNR...]
か     mysqld_multi [OPTIONS] {start|stop|report} [GNR-GNR,GNR,GNR-GNR,...]

      Each GNR represents an option group number. You can start, stop or report any GNR, or several of them at the same time. For an example of how you might set up an option file, use this command: 

      shell> mysqld_multi --example

      The GNR values in the list can be comma-separated or combined with a dash; in the latter case, all the GNRs between GNR1-GNR2 will be affected. GNR が引数に与えられなかった場合は、 全てのグループが、起動、停止、レポートされます。 GNR のリストには空白は許されません。スペースの後ろは無視されます。

      mysqld_multi は以下のオプションをサポートします:

      --config-file=...
      Alternative config file. Note: This will not affect this program's own options (group [mysqld_multi]), but only groups [mysqld#]. Without this option, everything will be searched from the ordinary `my.cnf' file.
      --example
      オプション例を表示.
      --help
      ヘルプを表示して終了
      --log=...
      ログファイル。フルパスで与えます。 もしファイルが存在している場合は、ログはファイルに追加されます。
      --mysqladmin=...
      サーバーの シャットダウン に使用する mysqladmin バイナリの指定
      --mysqld=...
      使用する mysqld バイナリの指定。 safe_mysqld をこのオプションに指定することも可能です。 指定されたオプションは mysqld に渡されます。 Just make sure you have mysqld in your environment variable PATH or fix safe_mysqld.
      --no-log
      ログをログファイルではなく標準出力に書きだします。 デフォルトでは、ログファイルに書き込むモードです。
      --password=...
      mysqladmin で使用するユーザーのパスワード.
      --tcp-ip
      Connect to the MySQL server(s) via the TCP/IP port instead of the Unix socket. This affects stopping and reporting. If a socket file is missing, the server may still be running, but can be accessed only via the TCP/IP port. By default, connections are made using the Unix socket.
      --user=...
      mysqladmin で使用する MySQL ユーザー.
      --version
      バージョンを表示して終了.

      Some notes about mysqld_multi:

      • Make sure that the MySQL user, who is stopping the mysqld services (e.g using the mysqladmin program) have the same password and username for all the data directories accessed (to the mysql database) And make sure that the user has the SHUTDOWN privilege! If you have many data directories and many different mysql databases with different passwords for the MySQL root user, you may want to create a common multi_admin user for each using the same password (see below). Example how to do it: 
        shell> mysql -u root -S /tmp/mysql.sock -proot_password -e
"GRANT SHUTDOWN ON *.* TO multi_admin@localhost IDENTIFIED BY 'multipass'"
        「4.2.6 特権システムはどのように動くか？」節参照. You will have to do the above for each mysqld running in each data directory, that you have (just change the socket, -S=...).
      • pid-file is very important, if you are using safe_mysqld to start mysqld (e.g., --mysqld=safe_mysqld) Every mysqld should have its own pid-file. The advantage using safe_mysqld instead of mysqld directly here is, that safe_mysqld ``guards'' every mysqld process and will restart it, if a mysqld process terminates due to a signal sent using kill -9, or for other reasons such as a segmentation fault (which MySQL should never do, of course ;). Please note that the safe_mysqld script may require that you start it from a certain place. This means that you may have to cd to a certain directory, before you start the mysqld_multi. If you have problems starting, please see the safe_mysqld script. Check especially the lines: 
        --------------------------------------------------------------------------
MY_PWD=`pwd` Check if we are starting this relative (for the binary
release) if test -d /data/mysql -a -f ./share/mysql/english/errmsg.sys
-a -x ./bin/mysqld
--------------------------------------------------------------------------
        「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照. The above test should be successful, or you may encounter problems.
      • Beware of the dangers starting multiple mysqlds in the same data directory. Use separate data directories, unless you know what you are doing!
      • The socket file and the TCP/IP port must be different for every mysqld.
      • The first and fifth mysqld group were intentionally left out from the example. You may have 'gaps' in the config file. This gives you more flexibility. The order in which the mysqlds are started or stopped depends on the order in which they appear in the config file.
      • When you want to refer to a certain group using GNR with this program, just use the number in the end of the group name. For example, the GNR for a group named [mysqld17] is 17.
      • You may want to use option --user for mysqld, but in order to do this you need to run the mysqld_multi script as the Unix root user. Having the option in the config file doesn't matter; you will just get a warning, if you are not the superuser and the mysqlds are started under your Unix account. Important: Make sure that the pid-file and the data directory are read+write(+execute for the latter one) accessible for that Unix user, who the specific mysqld process is started as. Do not use the Unix root account for this, unless you know what you are doing!
      • Most important: Make sure that you understand the meanings of the options that are passed to the mysqlds and why one would want to have separate mysqld processes. Starting multiple mysqlds in one data directory will not give you extra performance in a threaded system!

      「4.1.4 同一マシン上に複数の MySQL サーバーを走らせる」節参照.

      This is an example of the config file on behalf of mysqld_multi. 

      # This file should probably be in your home dir (~/.my.cnf) or /etc/my.cnf
# Version 2.1 by Jani Tolonen

[mysqld_multi]
mysqld     = /usr/local/bin/safe_mysqld
mysqladmin = /usr/local/bin/mysqladmin
user       = multi_admin
password   = multipass

[mysqld2]
socket     = /tmp/mysql.sock2
port       = 3307
pid-file   = /usr/local/mysql/var2/hostname.pid2
datadir    = /usr/local/mysql/var2
language   = /usr/local/share/mysql/english
user       = john

[mysqld3]
socket     = /tmp/mysql.sock3
port       = 3308
pid-file   = /usr/local/mysql/var3/hostname.pid3
datadir    = /usr/local/mysql/var3
language   = /usr/local/share/mysql/swedish
user       = monty

[mysqld4]
socket     = /tmp/mysql.sock4
port       = 3309
pid-file   = /usr/local/mysql/var4/hostname.pid4
datadir    = /usr/local/mysql/var4
language   = /usr/local/share/mysql/estonia
user       = tonu

[mysqld6]
socket     = /tmp/mysql.sock6
port       = 3311
pid-file   = /usr/local/mysql/var6/hostname.pid6
datadir    = /usr/local/mysql/var6
language   = /usr/local/share/mysql/japanese
user       = jani

      「4.1.2 `my.cnf' オプションファイル」節参照.

      4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ

      myisampack is used to compress MyISAM tables, and pack_isam is used to compress ISAM tables. Because ISAM tables are deprecated, we will only discuss myisampack here, but everything said about myisampack should also be true for pack_isam.

      myisampack はテーブル内の各項目を別々に圧縮するように働きます。展開のため の情報は、テーブルがオープンされた時にメモリに読まれます。これは、正確に1レコー ドだけを展開する必要があるような、個々のレコードへのアクセス時にとても良 い性能を与えます。MSDOS 上の Stacker 使用時のように、ディスクブロックは そんなに大きくありません。 通常、myisampack はデータファイルを 40〜70% にパックします。

      MySQL は圧縮されたテーブルでメモリマップ (mmap()) を使用します。 mmap() が働かない場合は、通常のファイルの読み書きを使用します。

      Please note the following:

      • パック後、テーブルは読み込み専用になります。 This is generally intended (such as when accessing packed tables on a CD). Also allowing writes to a packed table is on our TODO list but with low priority.
      • myisampack can also pack BLOB or TEXT columns. The older pack_isam (for ISAM tables) can not do this.

      myisampack is invoked like this: 

      shell> myisampack [options] filename ...

      それぞれのファイル名はインデックスファイル(`.MYI')の名前です。 もしデータディレクトリにカレントディレクトリを移動していないなら、 ファイルのパスを指定しなくてはなりません。`.MYI' 拡張子は 省略することが可能です。

      myisampack は以下のオプションをサポートします:

      -b, --backup
      tbl_name.OLD としてバックアップを作成します.
      -#, --debug=debug_options
      デバック出力。debug_options は 'd:t:o,filename'.
      -f, --force
      一時ファイルが存在していようが、サイズが大きくなろうが、強制的にテーブルを パックします。 myisampack はテーブルを圧縮している間、 一時ファイルを `tbl_name.TMD' という名前で作成します。 もし myisampack を途中で kill した場合、 `.TMD' ファイルが消されて いない事があります。通常、myisampack は `tbl_name.TMD' ファイルが 既に存在する場合はエラーで終了します。 --force を使用すると、 myisampack はそのような場合でもテーブルをパックします。
      -?, --help
      ヘルプメッセージを出力して終了。
      -j big_tbl_name, --join=big_tbl_name
      全てのテーブルをコマンドラインで指定した big_tbl_name 一つに まとめます。結合される全てのテーブル定義は同じでなければなりません (同じ項目名、同じ項目型、同じインデックス、等)
      -p #, --packlength=#
      Specify the record length storage size, in bytes. The value should be 1, 2, or 3. (myisampack stores all rows with length pointers of 1, 2, or 3 bytes. In most normal cases, myisampack can determine the right length value before it begins packing the file, but it may notice during the packing process that it could have used a shorter length. In this case, myisampack will print a note that the next time you pack the same file, you could use a shorter record length.)
      -s, --silent
      Silent mode. Write output only when errors occur.
      -t, --test
      Don't actually pack table, just test packing it.
      -T dir_name, --tmp_dir=dir_name
      Use the named directory as the location in which to write the temporary table.
      -v, --verbose
      Verbose mode. Write information about progress and packing result.
      -V, --version
      Display version information and exit.
      -w, --wait
      Wait and retry if table is in use. If the mysqld server was invoked with the --skip-external-locking option, it is not a good idea to invoke myisampack if the table might be updated during the packing process.

      The sequence of commands shown here illustrates a typical table compression session: 

      shell> ls -l station.*
-rw-rw-r--   1 monty    my         994128 Apr 17 19:00 station.MYD
-rw-rw-r--   1 monty    my          53248 Apr 17 19:00 station.MYI
-rw-rw-r--   1 monty    my           5767 Apr 17 19:00 station.frm

shell> myisamchk -dvv station

MyISAM file:     station
Isam-version:  2
Creation time: 1996-03-13 10:08:58
Recover time:  1997-02-02  3:06:43
Data records:              1192  Deleted blocks:              0
Datafile: Parts:           1192  Deleted data:                0
Datafile pointer (bytes):     2  Keyfile pointer (bytes):     2
Max datafile length:   54657023  Max keyfile length:   33554431
Recordlength:               834
Record format: Fixed length

table description:
Key Start Len Index   Type                       Root  Blocksize    Rec/key
1   2     4   unique  unsigned long              1024       1024          1
2   32    30  multip. text                      10240       1024          1

Field Start Length Type
1     1     1
2     2     4
3     6     4
4     10    1
5     11    20
6     31    1
7     32    30
8     62    35
9     97    35
10    132   35
11    167   4
12    171   16
13    187   35
14    222   4
15    226   16
16    242   20
17    262   20
18    282   20
19    302   30
20    332   4
21    336   4
22    340   1
23    341   8
24    349   8
25    357   8
26    365   2
27    367   2
28    369   4
29    373   4
30    377   1
31    378   2
32    380   8
33    388   4
34    392   4
35    396   4
36    400   4
37    404   1
38    405   4
39    409   4
40    413   4
41    417   4
42    421   4
43    425   4
44    429   20
45    449   30
46    479   1
47    480   1
48    481   79
49    560   79
50    639   79
51    718   79
52    797   8
53    805   1
54    806   1
55    807   20
56    827   4
57    831   4

shell> myisampack station.MYI
Compressing station.MYI: (1192 records)
- Calculating statistics

normal:     20  empty-space:      16  empty-zero:        12  empty-fill:  11
pre-space:   0  end-space:        12  table-lookups:      5  zero:         7
Original trees:  57  After join: 17
- Compressing file
87.14%

shell> ls -l station.*
-rw-rw-r--   1 monty    my         127874 Apr 17 19:00 station.MYD
-rw-rw-r--   1 monty    my          55296 Apr 17 19:04 station.MYI
-rw-rw-r--   1 monty    my           5767 Apr 17 19:00 station.frm

shell> myisamchk -dvv station

MyISAM file:     station
Isam-version:  2
Creation time: 1996-03-13 10:08:58
Recover time:  1997-04-17 19:04:26
Data records:              1192  Deleted blocks:              0
Datafile: Parts:           1192  Deleted data:                0
Datafilepointer (bytes):      3  Keyfile pointer (bytes):     1
Max datafile length:   16777215  Max keyfile length:     131071
Recordlength:               834
Record format: Compressed

table description:
Key Start Len Index   Type                       Root  Blocksize    Rec/key
1   2     4   unique  unsigned long             10240       1024          1
2   32    30  multip. text                      54272       1024          1

Field Start Length Type                         Huff tree  Bits
1     1     1      constant                             1     0
2     2     4      zerofill(1)                          2     9
3     6     4      no zeros, zerofill(1)                2     9
4     10    1                                           3     9
5     11    20     table-lookup                         4     0
6     31    1                                           3     9
7     32    30     no endspace, not_always              5     9
8     62    35     no endspace, not_always, no empty    6     9
9     97    35     no empty                             7     9
10    132   35     no endspace, not_always, no empty    6     9
11    167   4      zerofill(1)                          2     9
12    171   16     no endspace, not_always, no empty    5     9
13    187   35     no endspace, not_always, no empty    6     9
14    222   4      zerofill(1)                          2     9
15    226   16     no endspace, not_always, no empty    5     9
16    242   20     no endspace, not_always              8     9
17    262   20     no endspace, no empty                8     9
18    282   20     no endspace, no empty                5     9
19    302   30     no endspace, no empty                6     9
20    332   4      always zero                          2     9
21    336   4      always zero                          2     9
22    340   1                                           3     9
23    341   8      table-lookup                         9     0
24    349   8      table-lookup                        10     0
25    357   8      always zero                          2     9
26    365   2                                           2     9
27    367   2      no zeros, zerofill(1)                2     9
28    369   4      no zeros, zerofill(1)                2     9
29    373   4      table-lookup                        11     0
30    377   1                                           3     9
31    378   2      no zeros, zerofill(1)                2     9
32    380   8      no zeros                             2     9
33    388   4      always zero                          2     9
34    392   4      table-lookup                        12     0
35    396   4      no zeros, zerofill(1)               13     9
36    400   4      no zeros, zerofill(1)                2     9
37    404   1                                           2     9
38    405   4      no zeros                             2     9
39    409   4      always zero                          2     9
40    413   4      no zeros                             2     9
41    417   4      always zero                          2     9
42    421   4      no zeros                             2     9
43    425   4      always zero                          2     9
44    429   20     no empty                             3     9
45    449   30     no empty                             3     9
46    479   1                                          14     4
47    480   1                                          14     4
48    481   79     no endspace, no empty               15     9
49    560   79     no empty                             2     9
50    639   79     no empty                             2     9
51    718   79     no endspace                         16     9
52    797   8      no empty                             2     9
53    805   1                                          17     1
54    806   1                                           3     9
55    807   20     no empty                             3     9
56    827   4      no zeros, zerofill(2)                2     9
57    831   4      no zeros, zerofill(1)                2     9

      The information printed by myisampack is described here:

      normal
      The number of columns for which no extra packing is used.
      empty-space
      The number of columns containing values that are only spaces; these will occupy 1 bit.
      empty-zero
      The number of columns containing values that are only binary 0's; these will occupy 1 bit.
      empty-fill
      The number of integer columns that don't occupy the full byte range of their type; these are changed to a smaller type (for example, an INTEGER column may be changed to MEDIUMINT).
      pre-space
      The number of decimal columns that are stored with leading spaces. In this case, each value will contain a count for the number of leading spaces.
      end-space
      The number of columns that have a lot of trailing spaces. In this case, each value will contain a count for the number of trailing spaces.
      table-lookup
      The column had only a small number of different values, which were converted to an ENUM before Huffman compression.
      zero
      The number of columns for which all values are zero.
      Original trees
      The initial number of Huffman trees.
      After join
      The number of distinct Huffman trees left after joining trees to save some header space.

      After a table has been compressed, myisamchk -dvv prints additional information about each field:

      Type
      The field type may contain the following descriptors:
      constant
      All rows have the same value.
      no endspace
      Don't store endspace.
      no endspace, not_always
      Don't store endspace and don't do end space compression for all values.
      no endspace, no empty
      Don't store endspace. Don't store empty values.
      table-lookup
      The column was converted to an ENUM.
      zerofill(n)
      The most significant n bytes in the value are always 0 and are not stored.
      no zeros
      Don't store zeros.
      always zero
      0 values are stored in 1 bit.
      Huff tree
      The Huffman tree associated with the field.
      Bits
      The number of bits used in the Huffman tree.

      After you have run pack_isam/myisampack you must run isamchk/myisamchk to re-create the index. At this time you can also sort the index blocks and create statistics needed for the MySQL optimiser to work more efficiently: 

      myisamchk -rq --analyze --sort-index table_name.MYI
isamchk   -rq --analyze --sort-index table_name.ISM

      After you have installed the packed table into the MySQL database directory you should do mysqladmin flush-tables to force mysqld to start using the new table.

      If you want to unpack a packed table, you can do this with the --unpack option to isamchk or myisamchk.

      4.7.5 mysqld-max, An Extended mysqld Server

      mysqld-max is the MySQL server (mysqld) configured with the following configure options:

      Option Comment
      --with-server-suffix=-max Add a suffix to the mysqld version string.
      --with-innodb Support for InnoDB tables.
      --with-bdb Support for Berkeley DB (BDB) tables
      CFLAGS=-DUSE_SYMDIR Symbolic links support for Windows.

      You can find the MySQL-max binaries at http://www.mysql.com/downloads/mysql-max-3.23.html.

      The Windows MySQL binary distributions includes both the standard mysqld.exe binary and the mysqld-max.exe binary. http://www.mysql.com/downloads/mysql-3.23.html. 「2.1.2 Windows への MySQL のインストール」節参照.

      Note that as InnoDB and Berkeley DB are not available for all platforms, some of the Max binaries may not have support for both of these. You can check which table types are supported by doing the following query: 

      mysql> SHOW VARIABLES LIKE "have_%";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_bdb      | YES   |
| have_innodb   | NO    |
| have_isam     | YES   |
| have_raid     | NO    |
| have_openssl  | NO    |
+---------------+-------+

      The meaning of the values are:

      Value Meaning
      YES The option is activated and usable.
      NO MySQL is not compiled with support for this option.
      DISABLED The xxxx option is disabled because one started mysqld with --skip-xxxx or because one didn't start mysqld with all needed options to enable the option. In this case the hostname.err file should contain a reason for why the option is disabled.

      Note: To be able to create InnoDB tables you must edit your startup options to include at least the innodb_data_file_path option. 「7.5.2 InnoDB 起動オプション」節参照.

      To get better performance for BDB tables, you should add some configuration options for these too. 「7.6.3 BDB startup options」節参照.

      safe_mysqld will automatically try to start any mysqld binary with the -max suffix. This makes it very easy to test out a another mysqld binary in an existing installation. Just run configure with the options you want and then install the new mysqld binary as mysqld-max in the same directory where your old mysqld binary is. 「4.7.2 safe_mysqld, The Wrapper Around mysqld」節参照.

      The mysqld-max RPM uses the above mentioned safe_mysqld feature. It just installs the mysqld-max executable and safe_mysqld will automatically use this executable when safe_mysqld is restarted.

      The following table shows which table types our standard MySQL-Max binaries includes:

      System BDB InnoDB
      AIX 4.3 N Y
      HP-UX 11.0 N Y
      Linux-Alpha N Y
      Linux-Intel Y Y
      Linux-IA64 N Y
      Solaris-Intel N Y
      Solaris-SPARC Y Y
      Caldera (SCO) OSR5 Y Y
      UnixWare Y Y
      Windows/NT Y Y

      4.8 MySQL Client-Side Scripts and Utilities

      4.8.1 Overview of the Client-Side Scripts and Utilities

      All MySQL clients that communicate with the server using the mysqlclient library use the following environment variables:

      Name Description
      MYSQL_UNIX_PORT The default socket; used for connections to localhost
      MYSQL_TCP_PORT The default TCP/IP port
      MYSQL_PWD The default password
      MYSQL_DEBUG Debug-trace options when debugging
      TMPDIR The directory where temporary tables/files are created

      Use of MYSQL_PWD is insecure. 「4.2.8 MySQL サーバーに接続」節参照.

      The `mysql' client uses the file named in the MYSQL_HISTFILE environment variable to save the command-line history. The default value for the history file is `$HOME/.mysql_history', where $HOME is the value of the HOME environment variable. 「F Environment Variables」節参照.

      All MySQL programs take many different options. However, every MySQL program provides a --help option that you can use to get a full description of the program's different options. For example, try mysql --help.

      You can override default options for all standard client programs with an option file. 「4.1.2 `my.cnf' オプションファイル」節.

      The following list briefly describes the client-side MySQL programs:

      msql2mysql
      A shell script that converts mSQL programs to MySQL. It doesn't handle all cases, but it gives a good start when converting.
      mysqlaccess
      A script that checks the access privileges for a host, user, and database combination.
      mysqladmin
      Utility for performing administrative operations, such as creating or dropping databases, reloading the grant tables, flushing tables to disk, and reopening log files. mysqladmin can also be used to retrieve version, process, and status information from the server. 「4.8.3 mysqladmin, MySQL サーバーの管理」節参照.
      mysqldump
      Dumps a MySQL database into a file as SQL statements or as tab-separated text files. Enhanced freeware originally by Igor Romanenko. 「4.8.5 mysqldump, データベースとテーブルから、構造とデータをダンプ」節参照.
      mysqlimport
      Imports text files into their respective tables using LOAD DATA INFILE. 「4.8.7 mysqlimport, テキストファイルからデータを取り込む」節参照.
      mysqlshow
      Displays information about databases, tables, columns, and indexes.
      replace
      A utility program that is used by msql2mysql, but that has more general applicability as well. replace changes strings in place in files or on the standard input. Uses a finite state machine to match longer strings first. Can be used to swap strings. For example, this command swaps a and b in the given files: 
      shell> replace a b b a -- file1 file2 ...

      4.8.2 mysql, コマンドラインツール

      mysql はシンプルな SQL shell です(GNU readline を持っています). これは対話モードと、非対話モードを持っています。 対話モードで使用された場合、 クエリの結果は ASCII テーブルのフォーマットで与えられます。 非対話モードで使用された場合(例えばフィルターとして)、結果はタブ区切りの フォーマットで返ります。 (出力フォーマットはコマンドラインのオプションで変更できます) 以下のようにしてスクリプトを実行できます： 

      shell> mysql database < script.sql > output.tab

      もしクライアントでメモリー不足の問題が出た場合、--quick オプションを 使用します！ これは mysql に、結果セットを取得する際に、 mysql_store_result() ではなく mysql_use_result() を 使用させます。

      mysql の使用はとても簡単です： mysql database や mysql --user=user_name --password=your_password d atabase のようにしてはじめます。 SQL 文を入力し、一文を `;', `\g' or `\G' で終え、 RETURN/ENTER を押します。

      mysql は以下のオプションをサポートします：

      -?, --help
      help を表示して終了
      -A, --no-auto-rehash
      自動リハッシュをしない。 テーブルとフィールドの取得には 'rehash' を 使用しなくてはなりません。 これは mysql の起動を速くします。
      --prompt=...
      Set the mysql prompt to specified format.
      -b, --no-beep
      Turn off beep-on-error.
      -B, --batch
      結果をタブ区切り、１レコードは１行で出力します。 history ファイルは使用しません。
      --character-sets-dir=...
      Directory where character sets are located.
      -C, --compress
      サーバー・クライアント間の通信を圧縮します
      -#, --debug[=...]
      デバッグログ。 デフォルトは 'd:t:o,/tmp/mysql.trace'
      -D, --database=...
      使用するデータベース。 これは my.cnf ファイルが便利です
      --default-character-set=...
      Set the default character set.
      -e, --execute=...
      コマンドを実行して終了。 (Output like with --batch)
      -E, --vertical
      垂直にレコードを出力します。 このオプションを指定していなくても、 SQL 文を \G で終了した場合、同じように垂直に出力します。
      -f, --force
      SQL エラーがおきたとしても、処理を続けます
      -g, --no-named-commands
      Named commands are disabled. Use \* form only, or use named commands only in the beginning of a line ending with a semicolon (`;'). Since Version 10.9, the client now starts with this option enabled by default! With the -g option, long format commands will still work from the first line, however.
      -G, --enable-named-commands
      Named commands are enabled. Long format commands are allowed as well as shortened \* commands.
      -i, --ignore-space
      関数名の後ろについたスペースを無視します
      -h, --host=...
      指定したホストに接続します
      -H, --html
      結果を HTML フォーマットで返します
      -X, --xml
      Produce XML output.
      -L, --skip-line-numbers
      エラーの起きた行の番号を書きません。 これはエラーメッセージを含んだ結果を 比較する場合に便利です。
      --no-pager
      Disable pager and print to stdout. See interactive help (\h) also.
      --no-tee
      Disable outfile. See interactive help (\h) also.
      -n, --unbuffered
      それぞれのクエリ毎にバッファをフラッシュします
      -N, --skip-column-names
      結果に、フィールド名を書き出しません。
      -O, --set-variable var=option
      変数に値をセットします。 --help lists variables. Please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own.
      -o, --one-database
      デフォルトのデータベースのみ更新します。 これは update ログファイルを 使用して更新する場合、他のデータベースの更新を避けたい時に便利です。
      --pager[=...]
      Output type. Default is your ENV variable PAGER. Valid pagers are less, more, cat [> filename], etc. See interactive help (\h) also. This option does not work in batch mode. Pager works only in Unix.
      -p[password], --password[=...]
      サーバーに接続する際のパスワード。 もしパスワードがコマンドラインに 指定されていなかった場合、tty 上でパスワードが問い合わされます。 -p を使用する場合、このオプションとパスワードの間には スペースが不要だということに注意してください。
      -P port_num, --port=port_num
      接続に使用する TCP/IP ポート番号
      --protocol=(TCP | SOCKET | PIPE | MEMORY)
      To specify the connect protocol to use. New in MySQL 4.1.
      -q, --quick
      結果をキャッシュせず、一レコードづつ出力します。 これはもし出力を中止した場合、サーバーを遅くします。 ヒストリファイルは使用しません。
      -r, --raw
      エスケープ処理をしないで値を書き出します。 --batch とともに使用されます
      --reconnect
      If the connection is lost, automatically try to reconnect once to the server.
      -s, --silent
      静粛モード
      -S --socket=...
      接続に使用する ソケットファイル
      -t --table
      表の形式で出力します。 これは batch モード以外でのデフォルトです。
      -T, --debug-info
      Print some debug information at exit.
      --tee=...
      Append everything into outfile. See interactive help (\h) also. Does not work in batch mode.
      -u, --user=#
      ログインユーザー名
      -U, --safe-updates[=#], --i-am-a-dummy[=#]
      キーを使用する UPDATE and DELETE のみを行います。 これは後述します。 このオプションをもし my.cnf に書いている場合は、 --safe-updates=0 でこのオプションをリセットできます。
      -v, --verbose
      冗長出力。 (-v -v -v は表形式の出力を与える)
      -V, --version
      バージョンを表示して終了
      -w, --wait
      もし接続が落ちた場合、中断しないで、待って、再試行します。

      You can also set the following variables with -O or --set-variable; please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own:

      Variable Name Default Description
      connect_timeout 0 Number of seconds before timeout connection.
      max_allowed_packet 16777216 Max packetlength to send/receive from to server
      net_buffer_length 16384 Buffer for TCP/IP and socket communication
      select_limit 1000 Automatic limit for SELECT when using --i-am-a-dummy
      max_join_size 1000000 Automatic limit for rows in a join when using --i-am-a-dummy.

      If the mysql client loses connection to the server while sending it a query, it will immediately and automatically try to reconnect once to the server and send the query again. Note that even if it succeeds in reconnecting, as your first connection has ended, all your previous session objects are lost : temporary tables, user and session variables. Therefore, the above behaviour may be dangerous for you, like in this example where the server was shut down and restarted without you knowing it : 

      mysql> set @a=1;
Query OK, 0 rows affected (0.05 sec)

mysql> insert into t values(@a);
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    1
Current database: test

Query OK, 1 row affected (1.30 sec)

mysql> select * from t;
+------+
| a    |
+------+
| NULL |
+------+
1 row in set (0.05 sec)

      The @a user variable has been lost with the connection, and after the reconnection it is undefined. To protect from this risk, you can start the mysql client with the --disable-reconnect option.

      もしコマンドラインで 'help' と打った場合、mysql はサポートする コマンドを表示します： 

      mysql> help

MySQL commands:
help    (\h)    Display this text.
?       (\h)    Synonym for `help'.
clear   (\c)    Clear command.
connect (\r)    Reconnect to the server.
                Optional arguments are db and host.
edit    (\e)    Edit command with $EDITOR.
ego     (\G)    Send command to mysql server,
                display result vertically.
exit    (\q)    Exit mysql. Same as quit.
go      (\g)    Send command to mysql server.
nopager (\n)    Disable pager, print to stdout.
notee   (\t)    Don't write into outfile.
pager   (\P)    Set PAGER [to_pager].
                Print the query results via PAGER.
print   (\p)    Print current command.
prompt  (\R)    Change your mysql prompt.
quit    (\q)    Quit mysql.
rehash  (\#)    Rebuild completion hash.
source  (\.)    Execute a SQL script file.
                Takes a file name as an argument.
status  (\s)    Get status information from the server.
tee     (\T)    Set outfile [to_outfile].
                Append everything into given outfile.
use     (\u)    Use another database.
                Takes database name as argument.

      The pager command works only in Unix.

      status コマンドは、今使用している 接続とサーバーについての情報をいくつか表示します。 もし --safe-updates モードで使用している場合、 status は あなたのクエリに影響する mysql 変数の値を表示します。

      初心者に便利な起動オプション(MySQL バージョン 3.23.11 で導入されました)は、 --safe-updates あるいは --i-am-a-dummy です。 ( これは DELETE FROM table_name を WHERE 節を忘れて 実行しようとした場合のためにあります。) このオプションが使用されると、 mysql は接続時に MySQL サーバーに 以下のようなコマンドを送ります： 

      SET SQL_SAFE_UPDATES=1,SQL_SELECT_LIMIT=#select_limit#,
    SQL_MAX_JOIN_SIZE=#max_join_size#"

      ここで #select_limit# と #max_join_size# は変数で これらは mysql コマンドからセット可能です。 「5.5.6 SET 構文」節参照.

      この効果は：

      • もし WHERE 節でキーを使用していなければ、UPDATE や DELETE は許可されません。 しかし、 LIMIT を使用すれば UPDATE/DELETE を 強制実行できます： 
        UPDATE table_name SET not_key_column=# WHERE not_key_column=# LIMIT 1;
      • 全ての多きな結果は自動的に #select_limit# レコードまでに抑えられます。
      • 評価に #max_join_size 以上の行を必要とするであろう SELECT は 中断されます。

      Some useful hints about the mysql client:

      Some data is much more readable when displayed vertically, instead of the usual horizontal box type output. For example longer text, which includes new lines, is often much easier to be read with vertical output. 

      mysql> SELECT * FROM mails WHERE LENGTH(txt) < 300 lIMIT 300,1\G
*************************** 1. row ***************************
  msg_nro: 3068
     date: 2000-03-01 23:29:50
time_zone: +0200
mail_from: Monty
    reply: monty@no.spam.com
  mail_to: "Thimble Smith" <tim@no.spam.com>
      sbj: UTF-8
      txt: >>>>> "Thimble" == Thimble Smith writes:

Thimble> Hi.  I think this is a good idea.  Is anyone familiar with UTF-8
Thimble> or Unicode? Otherwise, I'll put this on my TODO list and see what
Thimble> happens.

Yes, please do that.

Regards,
Monty
     file: inbox-jani-1
     hash: 190402944
1 row in set (0.09 sec)

      For logging, you can use the tee option. The tee can be started with option --tee=..., or from the command-line interactively with command tee. All the data displayed on the screen will also be appended into a given file. This can be very useful for debugging purposes also. The tee can be disabled from the command-line with command notee. Executing tee again starts logging again. Without a parameter the previous file will be used. Note that tee will flush the results into the file after each command, just before the command-line appears again waiting for the next command.

      Browsing, or searching the results in the interactive mode in Unix less, more, or any other similar program, is now possible with option --pager[=...]. Without argument, mysql client will look for environment variable PAGER and set pager to that. pager can be started from the interactive command-line with command pager and disabled with command nopager. The command takes an argument optionally and the pager will be set to that. Command pager can be called without an argument, but this requires that the option --pager was used, or the pager will default to stdout. pager works only in Unix, since it uses the popen() function, which doesn't exist in Windows. In Windows, the tee option can be used instead, although it may not be as handy as pager can be in some situations.

      A few tips about pager:

      • You can use it to write to a file: 
        mysql> pager cat > /tmp/log.txt
        and the results will only go to a file. You can also pass any options for the programs that you want to use with the pager: 
        mysql> pager less -n -i -S
      • From the above do note the option '-S'. You may find it very useful when browsing the results; try the option with horizontal output (end commands with '\g', or ';') and with vertical output (end commands with '\G'). Sometimes a very wide result set is hard to be read from the screen, with option -S to less you can browse the results within the interactive less from left to right, preventing lines longer than your screen from being continued to the next line. This can make the result set much more readable. You can swith the mode between on and off within the interactive less with '-S'. See the 'h' for more help about less.
      • You can combine very complex ways to handle the results, for example the following would send the results to two files in two different directories, on two different hard-disks mounted on /dr1 and /dr2, yet let the results still be seen on the screen via less: 
        mysql> pager cat | tee /dr1/tmp/res.txt | \
tee /dr2/tmp/res2.txt | less -n -i -S

      You can also combine the two functions above; have the tee enabled, pager set to 'less' and you will be able to browse the results in unix 'less' and still have everything appended into a file the same time. The difference between Unix tee used with the pager and the mysql client in-built tee, is that the in-built tee works even if you don't have the Unix tee available. The in-built tee also logs everything that is printed on the screen, where the Unix tee used with pager doesn't log quite that much. Last, but not least, the interactive tee is more handy to switch on and off, when you want to log something into a file, but want to be able to turn the feature off sometimes.

      From MySQL version 4.0.2 it is possible to change the prompt in the mysql command-line client.

      You can use the following prompt options:
      Option Description
      \v mysqld version
      \d database in use
      \h host connected to
      \p port connected on
      \u username
      \U full username@host
      \\ `\'
      \n new line break
      \t tab
      \ space
      \_ space
      \R military hour time (0-23)
      \r standard hour time (1-12)
      \m minutes
      \y two digit year
      \Y four digit year
      \D full date format
      \s seconds
      \w day of the week in three letter format (Mon, Tue, ...)
      \P am/pm
      \o month in number format
      \O month in three letter format (Jan, Feb, ...)
      \c counter that counts up for each command you do

      `\' followed by any other letter just becomes that letter.

      You may set the prompt in the following places:

      Environment Variable
      You may set the MYSQL_PS1 environment variable to a prompt string. For example: 
      shell> export MYSQL_PS1="(\u@\h) [\d]> "
      `my.cnf'
      `.my.cnf'
      You may set the prompt option in any MySQL configuration file, in the mysql group. For example: 
      [mysql]
prompt=(\u@\h) [\d]>\_
      Command Line
      You may set the --prompt option on the command line to mysql. For example: 
      shell> mysql --prompt="(\u@\h) [\d]> "

(user@host) [database]>
      Interactively
      You may also use the prompt (or \R) command to change your prompt interactively. For example: 
      mysql> prompt (\u@\h) [\d]>\_
PROMPT set to '(\u@\h) [\d]>\_'
(user@host) [database]> 
(user@host) [database]> prompt
Returning to default PROMPT of mysql> 
mysql>

      4.8.3 mysqladmin, MySQL サーバーの管理

      管理オペレーションを実行するためのユーティリティ。シンタックスは: 

      shell> mysqladmin [OPTIONS] command [command-option] command ...

      mysqladmin --help によって、オプションの一覧を手にいれることができます。

      現在の mysqladmin は以下のコマンドをサポートします：

      create databasename
      新しいデータベースの作成
      drop databasename
      データベースとテーブルの全削除。
      extended-status
      サーバーから拡張ステータスを取得。
      flush-hosts
      キャッシュされている全ホストをフラッシュ。
      flush-logs
      全てのログをフラッシュ
      flush-tables
      全てのテーブルをフラッシュ
      flush-privileges
      許可テーブルの再読み込み (reload と同じ)
      kill id,id,...
      mysql スレッドの kill.
      password
      Set a new password. 古いパスワードを New-password に変更
      ping
      mysqld が生きているかチェック
      processlist
      現在活動中の mysql スレッドを表示
      reload
      権限テーブルの再読み込み
      refresh
      全テーブルをフラッシュし、ログファイルを一度閉じて開きます。
      shutdown
      サーバーをダウンさせます。
      slave-start
      Start slave replication thread.
      slave-stop
      Stop slave replication thread.
      status
      サーバーから短いステータスを得ます。
      variables
      変数の表示
      version
      サーバーからバージョンを得ます。

      全てのコマンドは、ユニークなプレフィックスで省略可能です。 例えば： 

      shell> mysqladmin proc stat
+----+-------+-----------+----+-------------+------+-------+------+
| Id | User  | Host      | db | Command     | Time | State | Info |
+----+-------+-----------+----+-------------+------+-------+------+
| 6  | monty | localhost |    | Processlist | 0    |       |      |
+----+-------+-----------+----+-------------+------+-------+------+
Uptime: 10077  Threads: 1  Questions: 9  Slow queries: 0
Opens: 6 Flush tables: 1  Open tables: 2
Memory in use: 1092K  Max memory used: 1116K

      The mysqladmin status command result has the following columns:

      Column Description
      Uptime MySQL サーバーの起動秒数
      Threads 稼働中のスレッド数 (clients).
      Questions mysqld が開始してからのクライアントからのクエリ数
      Slow queries long_query_time 秒より時間のかかったクエリの数 「4.9.5 The Slow Query Log (3.23.28以上)」節参照.
      Opens mysqld が開いたテーブル数
      Flush tables Number of flush ..., refresh, and reload commands.
      Open tables 現在開かれているテーブルの数
      Memory in use mysqld のコードによって直接割り当てられたメモリ (only available when MySQL is compiled with --with-debug=full).
      Max memory used mysqld のコードによって直接割り当てられる最大メモリー量 (only available when MySQL is compiled with --with-debug=full).

      If you do mysqladmin shutdown on a socket (in other words, on a the computer where mysqld is running), mysqladmin will wait until the MySQL pid-file is removed to ensure that the mysqld server has stopped properly.

      4.8.4 Using mysqlcheck for Table Maintenance and Crash Recovery

      Since MySQL version 3.23.38 you will be able to use a new checking and repairing tool for MyISAM tables. The difference to myisamchk is that mysqlcheck should be used when the mysqld server is running, where as myisamchk should be used when it is not. The benefit is that you no longer have to take the server down for checking or repairing your tables.

      mysqlcheck uses MySQL server commands CHECK, REPAIR, ANALYZE and OPTIMIZE in a convenient way for the user.

      There are three alternative ways to invoke mysqlcheck: 

      shell> mysqlcheck [OPTIONS] database [tables]
shell> mysqlcheck [OPTIONS] --databases DB1 [DB2 DB3...]
shell> mysqlcheck [OPTIONS] --all-databases

      So it can be used in a similar way as mysqldump when it comes to what databases and tables you want to choose.

      mysqlcheck does have a special feature compared to the other clients; the default behaviour, checking tables (-c), can be changed by renaming the binary. So if you want to have a tool that repairs tables by default, you should just copy mysqlcheck to your harddrive with a new name, mysqlrepair, or alternatively make a symbolic link to mysqlrepair and name the symbolic link as mysqlrepair. If you invoke mysqlrepair now, it will repair tables by default.

      The names that you can use to change mysqlcheck default behaviour are here: 

      mysqlrepair:   The default option will be -r
mysqlanalyze:  The default option will be -a
mysqloptimize: The default option will be -o

      The options available for mysqlcheck are listed here, please check what your version supports with mysqlcheck --help.

      -A, --all-databases
      Check all the databases. This will be same as --databases with all databases selected
      -1, --all-in-1
      Instead of making one query for each table, execute all queries in 1 query separately for each database. Table names will be in a comma separated list.
      -a, --analyze
      Analyse given tables.
      --auto-repair
      If a checked table is corrupted, automatically fix it. Repairing will be done after all tables have been checked, if corrupted ones were found.
      -#, --debug=...
      Output debug log. Often this is 'd:t:o,filename'
      --character-sets-dir=...
      Directory where character sets are
      -c, --check
      Check table for errors
      -C, --check-only-changed
      Check only tables that have changed since last check or haven't been closed properly.
      --compress
      Use compression in server/client protocol.
      -?, --help
      Display this help message and exit.
      -B, --databases
      To check several databases. Note the difference in usage; in this case no tables are given. All name arguments are regarded as database names.
      --default-character-set=...
      Set the default character set
      -F, --fast
      Check only tables that hasn't been closed properly
      -f, --force
      Continue even if we get an sql-error.
      -e, --extended
      If you are using this option with CHECK TABLE, it will ensure that the table is 100 percent consistent, but will take a long time. If you are using this option with REPAIR TABLE, it will run an extended repair on the table, which may not only take a long time to execute, but may produce a lot of garbage rows also!
      -h, --host=...
      Connect to host.
      -m, --medium-check
      Faster than extended-check, but only finds 99.99 percent of all errors. Should be good enough for most cases.
      -o, --optimize
      Optimise table
      -p, --password[=...]
      Password to use when connecting to server. If password is not given it's solicited on the tty.
      -P port_num, --port=port_num
      Port number to use for TCP/IP connections.
      --protocol=(TCP | SOCKET | PIPE | MEMORY)
      To specify the connect protocol to use. New in MySQL 4.1.
      -q, --quick
      If you are using this option with CHECK TABLE, it prevents the check from scanning the rows to check for wrong links. This is the fastest check. If you are using this option with REPAIR TABLE, it will try to repair only the index tree. This is the fastest repair method for a table.
      -r, --repair
      Can fix almost anything except unique keys that aren't unique.
      -s, --silent
      Print only error messages.
      -S, --socket=...
      Socket file to use for connection.
      --tables
      Overrides option --databases (-B).
      -u, --user=#
      User for login if not current user.
      -v, --verbose
      Print info about the various stages.
      -V, --version
      Output version information and exit.

      4.8.5 mysqldump, データベースとテーブルから、構造とデータをダンプ

      データベース、あるいは、バックアップ、他のSQLサーバー(MySQL サーバであ る必要はない)へのデータを移動を目的としたデータのまとまり、これらをダンプする ためのユーティリティ。ダンプは、テーブルの作成のための SQL 文を含みます。

      サーバでバックアップを行なう場合、mysqlhotcopy を代わりに使用するこ とを考慮すべきです。 「4.8.6 mysqlhotcopy, Copying MySQL Databases and Tables」節参照. 

      shell> mysqldump [OPTIONS] database [tables]
OR     mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
OR     mysqldump [OPTIONS] --all-databases [OPTIONS]

      もしテーブルを指定せず、--databases や --all-databases を 使用しなかったなら、データベースの全てのテーブルがダンプされます。

      mysqldump --help によって、オプションの一覧を手にいれることができます。

      もし mysqldump を --quick や --opt なしで実行するならば、 mysqldump は結果を表示する前に、結果をメモリに全てロードすることに 注意してください。 これは大きなデータベースをダンプする際に問題になるでしょう。

      Note that if you are using a new copy of the mysqldump program and you are going to do a dump that will be read into a very old MySQL server, you should not use the --opt or -e options.

      mysqldump は以下のオプションをサポートします：

      --add-locks
      Add LOCK TABLES before and UNLOCK TABLE after each table dump. (To get faster inserts into MySQL.)
      --add-drop-table
      Add a drop table before each create statement.
      -A, --all-databases
      Dump all the databases. This will be same as --databases with all databases selected.
      -a, --all
      Include all MySQL-specific create options.
      --allow-keywords
      Allow creation of column names that are keywords. This works by prefixing each column name with the table name.
      -c, --complete-insert
      Use complete insert statements (with column names).
      -C, --compress
      Compress all information between the client and the server if both support compression.
      -B, --databases
      To dump several databases. Note the difference in usage. In this case no tables are given. All name arguments are regarded as database names. USE db_name; will be included in the output before each new database.
      --delayed
      Insert rows with the INSERT DELAYED command.
      -e, --extended-insert
      Use the new multiline INSERT syntax. (Gives more compact and faster inserts statements.)
      -#, --debug[=option_string]
      Trace usage of the program (for debugging).
      --help
      Display a help message and exit.
      --fields-terminated-by=...
      --fields-enclosed-by=...
      --fields-optionally-enclosed-by=...
      --fields-escaped-by=...
      --lines-terminated-by=...
      These options are used with the -T option and have the same meaning as the corresponding clauses for LOAD DATA INFILE. 「6.4.9 LOAD DATA INFILE 構文」節参照.
      -F, --flush-logs
      Flush log file in the MySQL server before starting the dump.
      -f, --force,
      Continue even if we get a SQL error during a table dump.
      -h, --host=..
      Dump data from the MySQL server on the named host. The default host is localhost.
      -l, --lock-tables.
      Lock all tables before starting the dump. The tables are locked with READ LOCAL to allow concurrent inserts in the case of MyISAM tables. Please note that when dumping multiple databases, --lock-tables will lock tables for each database separately. So using this option will not guarantee your tables will be logically consistent between databases. Tables in different databases may be dumped in completely different states.
      -K, --disable-keys
      /*!40000 ALTER TABLE tb_name DISABLE KEYS */; and /*!40000 ALTER TABLE tb_name ENABLE KEYS */; will be put in the output. This will make loading the data into a MySQL 4.0 server faster as the indexes are created after all data are inserted.
      -n, --no-create-db
      CREATE DATABASE /*!32312 IF NOT EXISTS*/ db_name; will not be put in the output. The above line will be added otherwise, if a --databases or --all-databases option was given.
      -t, --no-create-info
      Don't write table creation information (the CREATE TABLE statement).
      -d, --no-data
      Don't write any row information for the table. This is very useful if you just want to get a dump of the structure for a table!
      --opt
      Same as --quick --add-drop-table --add-locks --extended-insert --lock-tables. Should give you the fastest possible dump for reading into a MySQL server.
      -pyour_pass, --password[=your_pass]
      The password to use when connecting to the server. If you specify no `=your_pass' part, mysqldump you will be prompted for a password.
      -P port_num, --port=port_num
      Port number to use for TCP/IP connections.
      --protocol=(TCP | SOCKET | PIPE | MEMORY)
      To specify the connect protocol to use. New in MySQL 4.1.
      -q, --quick
      Don't buffer query, dump directly to stdout. Uses mysql_use_result() to do this.
      -Q, --quote-names
      Quote table and column names within ``' characters.
      -r, --result-file=...
      Direct output to a given file. This option should be used in MSDOS, because it prevents new line `\n' from being converted to `\n\r' (new line + carriage return).
      --single-transaction
      This option issues a BEGIN SQL command before dumping data from server. It is mostly useful with InnoDB tables and READ_COMMITTED transaction isolation level, as in this mode it will dump the consistent state of the database at the time then BEGIN was issued without blocking any applications. When using this option you should keep in mind that only transactional tables will be dumped in a consistent state, e.g., any MyISAM or HEAP tables dumped while using this option may still change state. The --single-transaction option was added in version 4.0.2. This option is mutually exclusive with the --lock-tables option as LOCK TABLES already commits a previous transaction internally.
      -S /path/to/socket, --socket=/path/to/socket
      The socket file to use when connecting to localhost (which is the default host).
      --tables
      Overrides option --databases (-B).
      -T, --tab=path-to-some-directory
      Creates a table_name.sql file, that contains the SQL CREATE commands, and a table_name.txt file, that contains the data, for each give table. The format of the `.txt' file is made according to the --fields-xxx and --lines--xxx options. Note: This option only works if mysqldump is run on the same machine as the mysqld daemon, and the user/group that mysqld is running as (normally user mysql, group mysql) needs to have permission to create/write a file at the location you specify.
      -u user_name, --user=user_name
      The MySQL user name to use when connecting to the server. The default value is your Unix login name.
      -O var=option, --set-variable var=option
      Set the value of a variable. The possible variables are listed below. Please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own.
      -v, --verbose
      Verbose mode. Print out more information on what the program does.
      -V, --version
      Print version information and exit.
      -w, --where='where-condition'
      Dump only selected records. Note that quotes are mandatory:
      -X, --xml
      Dumps a database as well formed XML
      -x, --first-slave
      Locks all tables across all databases. 
      "--where=user='jimf'" "-wuserid>1" "-wuserid<1"
      -O net_buffer_length=#, where # < 16M
      When creating multi-row-insert statements (as with option --extended-insert or --opt), mysqldump will create rows up to net_buffer_length length. If you increase this variable, you should also ensure that the max_allowed_packet variable in the MySQL server is bigger than the net_buffer_length.

      The most normal use of mysqldump is probably for making a backup of whole databases. 「4.4.1 データベースのバックアップ」節参照. 

      mysqldump --opt database > backup-file.sql

      You can read this back into MySQL with: 

      mysql database < backup-file.sql

      or 

      mysql -e "source /patch-to-backup/backup-file.sql" database

      However, it's also very useful to populate another MySQL server with information from a database: 

      mysqldump --opt database | mysql --host=remote-host -C database

      It is possible to dump several databases with one command: 

      mysqldump --databases database1 [database2 ...] > my_databases.sql

      If all the databases are wanted, one can use: 

      mysqldump --all-databases > all_databases.sql

      4.8.6 mysqlhotcopy, Copying MySQL Databases and Tables

      mysqlhotcopy is a Perl script that uses LOCK TABLES, FLUSH TABLES and cp or scp to quickly make a backup of a database. It's the fastest way to make a backup of the database or single tables, but it can only be run on the same machine where the database directories are. 

      mysqlhotcopy db_name [/path/to/new_directory]

mysqlhotcopy db_name_1 ... db_name_n /path/to/new_directory

mysqlhotcopy db_name./regex/

      mysqlhotcopy supports the following options:

      -?, --help
      Display a help screen and exit
      -u, --user=#
      User for database login
      -p, --password=#
      Password to use when connecting to server
      -P, --port=#
      Port to use when connecting to local server
      -S, --socket=#
      Socket to use when connecting to local server
      --allowold
      Don't abort if target already exists (rename it _old)
      --keepold
      Don't delete previous (now renamed) target when done
      --noindices
      Don't include full index files in copy to make the backup smaller and faster The indexes can later be reconstructed with myisamchk -rq..
      --method=#
      Method for copy (cp or scp).
      -q, --quiet
      Be silent except for errors
      --debug
      Enable debug
      -n, --dryrun
      Report actions without doing them
      --regexp=#
      Copy all databases with names matching regexp
      --suffix=#
      Suffix for names of copied databases
      --checkpoint=#
      Insert checkpoint entry into specified db.table
      --flushlog
      Flush logs once all tables are locked.
      --tmpdir=#
      Temporary directory (instead of /tmp).

      You can use perldoc mysqlhotcopy to get more complete documentation for mysqlhotcopy.

      mysqlhotcopy reads the groups [client] and [mysqlhotcopy] from the option files.

      To be able to execute mysqlhotcopy you need write access to the backup directory, the SELECT privilege for the tables you are about to copy and the MySQL RELOAD privilege (to be able to execute FLUSH TABLES).

      4.8.7 mysqlimport, テキストファイルからデータを取り込む

      mysqlimport は、LOAD DATA INFILE SQL 構文を、 コマンドラインインターフェースで提供します。 mysqlimport のオプションのほとんどが、 LOAD DATA INFILE への同じオプションに対応します。 「6.4.9 LOAD DATA INFILE 構文」節参照.

      mysqlimport の実行は以下のようにします: 

      shell> mysqlimport [options] database textfile1 [textfile2 ...]

      mysqlimport は、コマンドラインの引数に与えられたファイル名の拡張子を取り、 拡張子を取った後の名前を、ファイルの内容を取り込むテーブルの名前とします。 例えば、`patient.txt', `patient.text', `patient' という ファイルは全て、patient とという名前のテーブルに取り込まれます。

      mysqlimport は以下のオプションをサポートします:

      -c, --columns=...
      This option takes a comma-separated list of field names as an argument. The field list is used to create a proper LOAD DATA INFILE command, which is then passed to MySQL. 「6.4.9 LOAD DATA INFILE 構文」節参照.
      -C, --compress
      クライアントとサーバーの両方が圧縮をサポートしているなら、 クライアント・サーバー間でやり取りされる全ての情報を圧縮します。
      -#, --debug[=option_string]
      プログラムのトレース(デバッグ)
      -d, --delete
      テキストファイルを取り込む前にテーブルを空にします。
      --fields-terminated-by=...
      --fields-enclosed-by=...
      --fields-optionally-enclosed-by=...
      --fields-escaped-by=...
      --lines-terminated-by=...
      これらのオプションは、LOAD DATA INFILE の対応する文節と同じ意味になります 「6.4.9 LOAD DATA INFILE 構文」節参照.
      -f, --force
      エラーを無視します。例えば、テキストファイルを取り込むテーブルがない場合、 残りのファイルの処理に移ります。 --force がなければ、 テーブルがなければ mysqlimport は終了します。
      --help
      ヘルプを表示して終了。
      -h host_name, --host=host_name
      名前を指定された MySQL サーバーにデータを取り入れます。 デフォルトでは localhost.
      -i, --ignore
      --replace オプションの説明を見てください。
      -l, --lock-tables
      それぞれのテキストファイルを処理する前に、書き込まれる 全てのテーブルをロックします。 これは確実に、すべてのテーブルをサーバ上で同期させます。
      -L, --local
      クライアントからの入力ファイルを読みます。 デフォルトでは、localhost に接続した場合、テキストファイルは サーバー上にあると仮定されます。(localhost はデフォルト値)
      -pyour_pass, --password[=your_pass]
      サーバーに接続するときに使用するパスワード。 もし `=your_pass' のところにパスワードを書かなければ、 mysqlimport はパスワードのためのプロンプトをだします。
      -P port_num, --port=port_num
      ホストに接続するための TCP/IP ポート番号。 (これは localhost を除くホストへの接続に使用します。 localhost へは、Unix ソケットを使用します。)
      --protocol=(TCP | SOCKET | PIPE | MEMORY)
      To specify the connect protocol to use. New in MySQL 4.1.
      -r, --replace
      --replace と --ignore オプションは、 入力されているレコードのユニークキーの値が、 既に存在しているレコードのユニークキーの値と同じ場合、 その入力されているデータの取り扱いを決定します。 もし --replace が指定されているなら、 既にあるレコードは新しく読まれたレコードに置き換えられます。 もし --ignore が指定されているなら、 入力された物は無視されます。 どちらのオプションも指定していない場合、 キーの値が重なっているとエラーを発し、 テキストファイルの残りの部分は無視されます。
      -s, --silent
      静粛モード。エラーだけ出力します。
      -S /path/to/socket, --socket=/path/to/socket
      localhost への接続時に使用するソケットファイルを指定します。
      -u user_name, --user=user_name
      サーバーの接続に使用する MySQL ユーザー名の指定。 デフォルトは、Unix のログイン名。
      -v, --verbose
      冗長モード。プログラムがしている事について多く出力します。
      -V, --version
      バージョンを表示して終了。

      Here is a sample run using mysqlimport: 

      $ mysql --version
mysql  Ver 9.33 Distrib 3.22.25, for pc-linux-gnu (i686)
$ uname -a
Linux xxx.com 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 i586 unknown
$ mysql -e 'CREATE TABLE imptest(id INT, n VARCHAR(30))' test
$ ed
a
100     Max Sydow
101     Count Dracula
.
w imptest.txt
32
q
$ od -c imptest.txt
0000000   1   0   0  \t   M   a   x       S   y   d   o   w  \n   1   0
0000020   1  \t   C   o   u   n   t       D   r   a   c   u   l   a  \n
0000040
$ mysqlimport --local test imptest.txt
test.imptest: Records: 2  Deleted: 0  Skipped: 0  Warnings: 0
$ mysql -e 'SELECT * FROM imptest' test
+------+---------------+
| id   | n             |
+------+---------------+
|  100 | Max Sydow     |
|  101 | Count Dracula |
+------+---------------+

      4.8.8 mysqlshow, Showing Databases, Tables, and Columns

      mysqlshow can be used to quickly look at which databases exist, their tables, and the table's columns.

      With the mysql program you can get the same information with the SHOW commands. 「4.5.6 SHOW 構文」節参照.

      mysqlshow is invoked like this: 

      shell> mysqlshow [OPTIONS] [database [table [column]]]
      • If no database is given, all matching databases are shown.
      • If no table is given, all matching tables in the database are shown.
      • If no column is given, all matching columns and column types in the table are shown.

      Note that in newer MySQL versions, you only see those database/tables/columns for which you have some privileges.

      If the last argument contains a shell or SQL wildcard (*, ?, % or _) then only what's matched by the wildcard is shown. If a database contains underscore(s), those should be escaped with backslash (some Unix shells will require two), in order to get tables / columns properly. '*' are converted into SQL '%' wildcard and '?' into SQL '_' wildcard. This may cause some confusion when you try to display the columns for a table with a _ as in this case mysqlshow only shows you the table names that match the pattern. This is easily fixed by adding an extra % last on the command-line (as a separate argument).

      4.8.9 mysql_config, Get compile options for compiling clients

      mysql_config provides you with useful information how to compile your MySQL client and connect it to MySQL.

      mysql_config supports the following options:

      --cflags
      Compiler flags to find include files
      --libs
      Libs and options required to link with the MySQL client library.
      --socket
      The default socket name, defined when configuring MySQL.
      --port
      The default port number, defined when configuring MySQL.
      --version
      Version number and version for the MySQL distribution
      --libmysqld-libs
      Libs and options required to link with the MySQL embedded server.

      If you execute mysql_config without any options it will print all options it supports plus the value of all options: 

      shell> mysql_config
sage: /usr/local/mysql/bin/mysql_config [OPTIONS]
Options:
        --cflags         [-I'/usr/local/mysql/include/mysql']
        --libs           [-L'/usr/local/mysql/lib/mysql' -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib -lssl -lcrypto]
        --socket         [/tmp/mysql.sock]
        --port           [3306]
        --version        [4.0.8-gamma]
        --libmysqld-libs [ -L'/usr/local/mysql/lib/mysql' -lmysqld -lpthread -lz -lcrypt -lnsl -lm  -lpthread  -lrt]

      You can use this to compile a MySQL client by as follows: 

      CFG=/usr/local/mysql/bin/mysql_config
sh -c "gcc -o progname `$CFG --cflags` progname.c `$CFG --libs`"

      4.8.10 perror, Explaining Error Codes

      For most system errors MySQL will, in addition to a internal text message, also print the system error code in one of the following styles: message ... (errno: #) or message ... (Errcode: #).

      You can find out what the error code means by either examining the documentation for your system or use the perror utility.

      perror prints a description for a system error code, or an MyISAM/ISAM storage engine (table handler) error code.

      perror is invoked like this: 

      shell> perror [OPTIONS] [ERRORCODE [ERRORCODE...]]

Example:

shell> perror 13 64
Error code  13:  Permission denied
Error code  64:  Machine is not on the network

      Note that the error messages are mostly system dependent!

      4.8.11 How to Run SQL Commands from a Text File

      The mysql client typically is used interactively, like this: 

      shell> mysql database

      However, it's also possible to put your SQL commands in a file and tell mysql to read its input from that file. To do so, create a text file `text_file' that contains the commands you wish to execute. Then invoke mysql as shown here: 

      shell> mysql database < text_file

      You can also start your text file with a USE db_name statement. In this case, it is unnecessary to specify the database name on the command line: 

      shell> mysql < text_file

      If you are already running mysql, you can execute a SQL script file using the source command: 

      mysql> source filename;

      For more information about batch mode, 「3.6 mysql のバッチモードでの使用」節.

      4.9 The MySQL Log Files

      MySQL has several different log files that can help you find out what's going on inside mysqld:

      Log file Description
      The error log Problems encountering starting, running or stopping mysqld.
      The isam log Logs all changes to the ISAM tables. Used only for debugging the isam code.
      The query log Established connections and executed queries.
      The update log Deprecated: Stores all statements that changes data
      The binary log Stores all statements that changes something. Used also for replication
      The slow log Stores all queries that took more than long_query_time to execute or didn't use indexes.

      All logs can be found in the mysqld data directory. You can force mysqld to reopen the log files (or in some cases switch to a new log) by executing FLUSH LOGS. 「4.5.3 FLUSH 構文」節参照.

      4.9.1 The Error Log

      The error log file contains information indicating when mysqld was started and stopped and also any critical errors found when running.

      If mysqld dies unexpectedly and mysqld_safe needs to restart mysqld, mysqld_safe will write a restarted mysqld row in this file. This log also holds a warning if mysqld notices a table that needs to be automatically checked or repaired.

      On some operating systems, the error log will contain a stack trace for where mysqld died. This can be used to find out where mysqld died. 「E.1.4 Using a Stack Trace」節参照.

      Beginning with MySQL 4.0.10 you can specify where mysqld stores the error log file with the option --log-error[=filename]. If no file name is given mysqld will use mysql-data-dir/'hostname'.err on Unix and `\mysql\data\mysql.err' on windows. If you execute flush logs the old file will be prefixed with --old and mysqld will create a new empty log file.

      In older MySQL versions the error log handling was done by mysqld_safe which redirected the error file to 'hostname'.err. One could change this file name with the option --err-log=filename.

      If you don't specify --log-error or if you use the --console option the errors will be written to stderr (the terminal).

      On windows the output is always done to the .err file if --console is not given.

      4.9.2 The General Query Log

      If you want to know what happens within mysqld, you should start it with --log[=file]. This will log all connections and queries to the log file (by default named `'hostname'.log'). This log can be very useful when you suspect an error in a client and want to know exactly what mysqld thought the client sent to it.

      Older versions of the mysql.server script (from MySQL 3.23.4 to 3.23.8) pass safe_mysqld a --log option (enable general query log). If you need better performance when you start using MySQL in a production environment, you can remove the --log option from mysql.server or change it to --log-bin. 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照.

      The entries in this log are written as mysqld receives the questions. This may be different from the order in which the statements are executed. This is in contrast to the update log and the binary log which are written after the query is executed, but before any locks are released.

      4.9.3 更新ログ

      Note: the update log is replaced by the binary log. 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照. With this you can do anything that you can do with the update log.

      --log-update=file_nameオプションを使用してmysqldを起動すると、 データを更新した全てのSQLコマンドをログファイルに書きます。 もし file_name が与えられなかった場合は、ホスト名がデフォルトで使用されます。 もし file_name にディレクトリパスが含まれなかった場合は、 このファイルはデータディレクトリに書かれます。 もし file_name が拡張を持たなかったなら、mysqld は file_name.### という形でログファイルを作成します。 このログファイルはデータディレクトリにかかれ、 その名前は file_name.### という形式の名前になっています。 ### は mysqladmin refresh か mysqladmin flush-logs を実行す る度に、 あるいは FLUSH LOGS 構文を実行したり、サーバーをリスタートする度に 自動的に増える数字です。

      Note: for the above scheme to work, you must not create your own files with the same filename as the update log + some extensions that may be regarded as a number, in the directory used by the update log!

      もし --log か -l オプションを使用した場合、ログファイルの名前は mysqld は全部のログを `hostname.log' に書き出します。 この場合、リスタートやりフレッシュを行っても新しくログファイルを作りません。 (一度クローズして再度オープンします。) In this case you can copy it (on Unix) by doing: 

      mv hostname.log hostname-old.log
mysqladmin flush-logs
cp hostname-old.log to-backup-directory
rm hostname-old.log

      更新ログは、実際に更新されたデータのステートメントだけを書くため、きびきびと動作 します。 WHERE を使用した UPDATE か DELETE で結果が得られなかった場合、 ログは書き出されません。 すでにセットされている値に、もう一度項目を更新するような UPDATE もスキッ プされます。

      The update logging is done immediately after a query completes but before any locks are released or any commit is done. This ensures that the log will be logged in the execution order.

      ログファイルの更新に従ってデータベースを更新したい場合は、次を行います (更新ログファイル名を `file_name.###' と仮定します): 

      shell> ls -1 -t -r file_name.[0-9]* | xargs cat | mysql

      ls は全てのログファイルを正しく並べるために使用しています。

      これは、クラッシュ後にバックアップした状態まで戻りたい、あるいは、 バックアップした後からクラッシュするまでの間のデータの更新を行いたい、 そんな場合に使えます。

      4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)

      The intention is that the binary log should replace the update log, so we recommend you to switch to this log format as soon as possible!

      The binary log contains all information that is available in the update log in a more efficient format. It also contains information about how long each query took that updated the database. It doesn't contain queries that don't modify any data. If you want to log all queries (for example to find a problem query) you should use the general query log. 「4.9.2 The General Query Log」節参照.

      バイナリログはマスターからスレーブにレプリケーションを行なうときにも 使用されます。 「4.10 MySQL のレプリケーション (3.23.15以上)」節参照.

      --log-bin[=file_name] オプションで mysqld が起動されると、 mysqld は全てのデータを更新する SQL コマンドをログファイルに書き出します。 もしファイル名がオプションに渡されなかった場合は、ホストマシンの名前に -bin がついた名前が、ファイル名として使用されます。 もしファイル名が指定されていても、パスが指定されていない場合には、 ログファイルはデータディレクトリに書かれます。

      もし --log-bin=filename.extension という形で ファイル名に拡張子を指定した場合、拡張子は取り除かれます。

      バイナリログファイル名のため、mysqld は数字をファイル名に付け加えます。 この数字はサーバー上で mysqladmin refresh, mysqladmin flush-logs, FLUSH LOGS を実行する度に増えていきます。 新しいバイナリログは max_binlog_size に達するまで自動的に作成されます。 RESET MASTER コマンドを使用すれば、書き込み中ではないバイナリログファイルを 全て消すことが可能です。 「4.5.4 RESET 構文」節参照.

      You can use the following options to mysqld to affect what is logged to the binary log:

      Option Description
      binlog-do-db=database_name Tells the master that it should log updates to the binary log if the current database (i.e. the one selected by USE) database is 'database_name'. All others databases which are not explicitly mentioned are ignored. Note that if you use this you should ensure that you only do updates in the current database. (Example: binlog-do-db=some_database)
      binlog-ignore-db=database_name Tells the master that updates where the current database (i.e. the one selected by USE) is 'database_name' should not be stored in the binary log. Note that if you use this you should ensure that you only do updates in the current database. (Example: binlog-ignore-db=some_database)

      To be able to know which different binary log files have been used, mysqld will also create a binary log index file that contains the name of all used binary log files. By default this has the same name as the binary log file, with the extension '.index'. You can change the name of the binary log index file with the --log-bin-index=[filename] option. You should not manually edit this file while mysqld is running; doing this would confuse mysqld.

      If you are using replication, you should not delete old binary log files until you are sure that no slave will ever need to use them. One way to do this is to do mysqladmin flush-logs once a day and then remove any logs that are more than 3 days old. You can remove them manually, or preferably using PURGE MASTER LOGS TO ( 「4.10.6 レプリケーションに関連する SQL コマンド」節参照) which will also safely update the binary log index file for you.

      You can examine the binary log file with the mysqlbinlog command. For example, you can update a MySQL server from the binary log as follows: 

      shell> mysqlbinlog log-file | mysql -h server_name

      You can also use the mysqlbinlog program to read the binary log directly from a remote MySQL server!

      mysqlbinlog --help will give you more information of how to use this program!

      If you are using BEGIN [WORK] or SET AUTOCOMMIT=0, you must use the MySQL binary log for backups instead of the old update log.

      The binary logging is done immediately after a query completes but before any locks are released or any commit is done. This ensures that the log will be logged in the execution order.

      Updates to non-transactional tables are stored in the binary log immediately after execution. For transactional tables such as BDB or InnoDB tables, all updates (UPDATE, DELETE or INSERT) that change tables are cached until a COMMIT command is sent to the server. At this point mysqld writes the whole transaction to the binary log before the COMMIT is executed. Every thread will, on start, allocate a buffer of binlog_cache_size to buffer queries. If a query is bigger than this, the thread will open a temporary file to store the transaction. The temporary file will be deleted when the thread ends.

      The max_binlog_cache_size (default 4G) can be used to restrict the total size used to cache a multi-query transaction. If a transaction is bigger than this it will fail and roll back.

      If you are using the update or binary log, concurrent inserts will be converted to normal inserts when using CREATE ... SELECT or INSERT ... SELECT. This is to ensure that you can recreate an exact copy of your tables by applying the log on a backup.

      4.9.5 The Slow Query Log (3.23.28以上)

      MySQL を --log-slow-queries[=file_name] オプションで起動すると、 mysqld は、 実行に long_query_time に指定された値以上に時間のかかった 全ての SQL コマンドをログに書き出します。 この時間には、最初のテーブルをロックするまでの時間は含まれていません。

      slow query log はクエリが実行され、全てのロックが解除された後に、 書き込まれます。 そのため、SQL 文が実行された順番とは違う順に 書かれるかもしれません。

      もしファイル名が指定されなかったら、ホスト名に -slow.log をつけた ファイル名が使用されます。 もしファイル名が指定されていてもパスが指定されなかったなら、 ログファイルはデータディレクトリに記録されます。

      slow query log は実行に時間のかかったクエリを見つけ出すのに使用することが 可能で、最適化に用いられます。 ログファイルが大きくなると、それが難しくなります。そこで、 mysqldumpslow コマンドを使用すれば、ログファイルの slow query の サマリ一覧を得ることが可能です。

      --log-long-format オプションを使用すれば、インデックスを使用しなかった クエリも記録します。 「4.1.1 mysqld コマンド行オプション」節参照.

      4.9.6 Log File Maintenance

      The MySQL Server can create a number of different log files, which make it easy to see what is going on. 「4.9 The MySQL Log Files」節参照. One must however regularly clean up these files, to ensure that the logs don't take up too much disk space.

      MySQL をログファイルとともに使用する場合、 あなたは、時々古いログファイルを リムーブ/バックアップし、 MySQL に新しいファイルにログを取るように指示したいと思うことでしょう。 「4.4.1 データベースのバックアップ」節参照.

      Linux (Red Hat) においては、mysql-log-rotate スクリプトを これに使用できます。 もし RPM ディストリビューションの MySQL を インストールしたなら、このスクリプトは自動でインストールされているはずです。 Note that you should be careful with this if you are using the log for replication!

      他のシステムでは、自分自身で短いスクリプトをインストールします。 cron でログファイルを扱うようにします。

      mysqladmin flush-logs コマンドか FLUSH LOGS SQL文で、 MySQL に新しいログファイルを使用させることが出来ます。 もしあなたが MySQL Version 3.21 を使用しているなら、 mysqladmin refresh を使用しなくてはなりません。

      上記のコマンドは、以下のように動作します：

      • If standard logging (--log) or slow query logging (--log-slow-queries) is used, closes and reopens the log file (`mysql.log' and ``hostname`-slow.log' as default).
      • もし更新ログ (--log-update) を使用しているなら、 更新ログを閉じ、新しいログファイルを開きます。そのさい、 ログファイルについている番号は増えます。

      もし更新ログだけを使用しているなら、あなたは、ログを flush するだけでよくて、 その時、バックアップのため古い更新ログファイルを移動します。 もし普通のログを使っていれば、あなたは以下のようにすることができます: 

      shell> cd mysql-data-directory
shell> mv mysql.log mysql.old
shell> mysqladmin flush-logs

      こうしておいて、`mysql.old' をバックアップし削除します。

      4.10 MySQL のレプリケーション (3.23.15以上)

      この章は MySQL の様々なレプリケーション機能を説明します。レプリケーション で有効なオプションのリファレンスとしても役立ちます。レプリケーションの紹介 と、その実装方法を学べます。終りの方には、いくつかの FAQ と問題の説明とそ の解決方法もあります。

      我々のウェブサイト http://www.mysql.com/ によく訪れ、この節の最新 版を読むようるように提案します。レプリケーションは絶えず改良されていて、 最新の情報でマニュアルを頻繁に更新します。

      4.10.1 Introduction

      一方通行レプリケーションは、堅牢さと速度の両方を増加させるために使用できま す。堅牢さについて、２つのシステムを持つことができ、マスターで問題が発生し た場合にバックアップに切り替えられます。速度の増加は、更新でないクエリの一 部をレプリカサーバに送ることで、成立します。もちろん、これは更新でないクエ リが多い時にだけ働くのですが、通常はそうなります。

      バージョン 3.23.15 から、MySQL はワンウェイ・レプリケーションを サポートしました。 1つのサーバーがマスターの役をつとめ，もう一方は、スレーブの役をつとめます。 1つのサーバーはマスターとして動くことも、他に対するスレーブとして動作することも 可能です。 マスターサーバーは update のバイナリログを保持しています( 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照.)。 また、インデックスファイルは、バイナリログのローテーションの切り出し記録を残すた めに保持されます。 スレーブは接続時に、マスタに対し更新の伝達が最後に成功してからやめた場所 を知らせ、更新を取り戻し、それからブロックし、マスタが新しい更新を通知す るのを待ちます。

      もしデータベースの複製を行なうなら、このデータベースに対する全ての更新は マスター上で行なわなくてはならないことに注意！

      レプリケーションを使用することのもう一つの恩恵は、マスターの代わりに、スレー ブでバックアップを行なうことで、システムのライブバックアップを取ることがで きるということです。 「4.4.1 データベースのバックアップ」節参照。

      4.10.2 レプリケーション実装概要

      MySQL レプリケーションは、サーバがデータベースへのすべての変更のトラックを バイナリログ ( 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照) に保持し、スレーブサーバがデータのコピー 上で同じクエリを実行できるように、マスターサーバのバイナリログから保存され たクエリを読み込むということを基本にします。

      バイナリログは単に固定点(バイナリロギングを有効にした瞬間)からの記録である ことを理解することがとても重要です。セットアップするすべてのスレー ブで、マスターからすべてのデータのコピーが必要です。マスター上でバイナリロ ギングを有効にした瞬間に存在していたように。 スレーブのデータがマスターに存在するデータと違う状態でスレーブを起動したならば、 バイナリログが開始されたときに、スレーブは失敗するでしょう。

      Please see the following table for an indication of master-slave compatibility between different versions. With regard to version 4.0, we recommend using same version on both sides.

      Master Master Master Master
      3.23.33 and up 4.0.0 4.0.1 4.0.3 and up
      Slave 3.23.33 and up yes no no no
      Slave 4.0.0 no yes no no
      Slave 4.0.1 yes no yes no
      Slave 4.0.3 and up yes no no yes

      Note: MySQL Version 4.0.2 is not recommended for replication.

      Starting from 4.0.0, one can use LOAD DATA FROM MASTER to set up a slave. Be aware that LOAD DATA FROM MASTER currently works only if all the tables on the master are MyISAM type, and will acquire a global read lock, so no writes are possible while the tables are being transferred from the master. This limitation is of a temporary nature, and is due to the fact that we have not yet implemented hot lock-free table backup. It will be removed in the future 4.0 branch versions once we implement hot backup enabling LOAD DATA FROM MASTER to work without blocking master updates.

      Due to the above limitation, we recommend that at this point you use LOAD DATA FROM MASTER only if the dataset on the master is relatively small, or if a prolonged read lock on the master is acceptable. While the actual speed of LOAD DATA FROM MASTER may vary from system to system, a good rule for a rough estimate of how long it is going to take is 1 second per 1 MB of the datafile. You will get close to the estimate if both master and slave are equivalent to 700 MHz Pentium, are connected through 100 MBit/s network, and your index file is about half the size of your data file. Of course, your mileage will vary from system to system, the above rule just gives you a rough order of magnitude estimate.

      一旦スレーブが適切に構成され、実行していれば、スレーブは単にマスターに接続して、 更新が処理されるのを待つでしょう。 もしマスターがなくなったり、または、スレーブがマスターとの接続性を失えば、 スレーブは再接続できるまで master-connect-retry 秒毎に接続を試み、 そして、更新の監視を再開します。

      各スレーブはそれが止まった場所のトラックを保持します。マスターサーバはいく つのスレーブが存在し、どれがいつ更新を行なったかについての知識はありません。

      次の節ではマスター／スレーブ設定過程を詳細に説明します。

      4.10.3 レプリケーションの設定方法

      以下は、現在の MySQL サーバ上に完全なレプリケーションを設定する方法の簡単 な記述です。あなたがすべてのデータベースのレプリケーションを行ないたくて、 事前にレプリケーションを設定していないと仮定します。以下に示すステップを完 了するためには、マスターサーバを少しシャットダウンすることが必要になります。

      上述の方法は、スレーブを設定するもっとも素直な方法ですが、それが唯一の方 法ではありません。たとえば、既にマスタのスナップショットを持っていて、マ スタがすでにサーバIDを設定して、バイナリログを有効にしている場合、マスタ をシャットダウンしたり更新をブロックすることなしに、スレーブを設定できま す。詳細については 「4.10.7 Replication FAQ」節. を参照してください。

      MySQL レプリケーションの達人(guru)になりたければ、学習し、熟考し、 「4.10.6 レプリケーションに関連する SQL コマンド」節 に記述されているすべてのコマンドを試すように提案 します。 「4.10.5 `my.cnf' 内のレプリケーションオプション」節 の my.cnf 内のレプリケーション 開始オプションにも精通すべきです。

      1. マスターとスレーブに、最新の MySQL (同じバージョン) をインストールします。 バージョン 3.23.29 以上を使用すること。 これより前のバージョンでは、バイナリログのフォーマットが違い、また、新しい バージョンで直っているバグも含まれます。 最新のバージョンで確かめるまでは、バグレポートを送らないでください。
      2. マスター上に、レプリケーション用の特別なユーザーを登録します。 このユーザーには FILE 権限(in MySQL versions older than 4.0.2)か REPLICATION SLAVE 権限(in newer MySQL versions)が必要です。 全てのスレーブからこのユーザーで接続できるようにします。 もしユーザーがレプリケーションのみ(推奨)を行なうなら、 他の権限は与える必要は有りません。 例えば、repl という名前のユーザー(マスターにアクセス可能なユーザー)を 作成するには、次のようにします： 
        mysql> GRANT FILE ON *.* TO repl@"%" IDENTIFIED BY '<password>'; # master < 4.0.2

        mysql> GRANT REPLICATION SLAVE ON *.* TO repl@"%" IDENTIFIED BY '<password>'; # master >= 4.0.2
        If you plan to use the LOAD TABLE FROM MASTER or LOAD DATA FROM MASTER commands (available starting from version 4.0.0), you will also need to grant the RELOAD and SUPER privileges on the master to the above user.
      3. If you are using MyISAM tables, flush all the tables and block write queries by executing FLUSH TABLES WITH READ LOCK command. 
        mysql> FLUSH TABLES WITH READ LOCK;
        and then take a snapshot of the data on your master server. (Unixでは) もっとも簡単な方法は tar を使用してデータディレクトリの アーカーブを作成することです。 正確なデータディレクトリの場所はインストール方法に依存します。 
        tar -cvf /tmp/mysql-snapshot.tar /path/to/data-dir
        Windows ユーザは WinZIP か似たソフトウェアを使用してデータディレクトリのアー カイブを作成することができます。 After or during the process of taking a snapshot, read the value of the current binary log name and the offset on the master: 
        mysql > SHOW MASTER STATUS;
+---------------+----------+--------------+-------------------------------+
| File          | Position | Binlog_do_db | Binlog_ignore_db              |
+---------------+----------+--------------+-------------------------------+
| mysql-bin.003 | 73       | test,bar     | foo,manual,sasha_likes_to_run |
+---------------+----------+--------------+-------------------------------+
1 row in set (0.06 sec)
        The File column shows the name of the log, while Position shows the offset. In the above example, the binary log value is mysql-bin.003 and the offset is 73. Record the values - you will need to use them later when you are setting up the slave. Once you have taken the snapshot and recorded the log name and offset, you can re-enable write activity on the master: 
        mysql> UNLOCK TABLES;
        If you are using InnoDB tables, ideally you should use the InnoDB Hot Backup tool that is available to those who purchase MySQL commercial licenses, support, or the backup tool itself. It will take a consistent snapshot without acquiring any locks on the master server, and record the log name and offset corresponding to the snapshot to be later used on the slave. More information about the tool is avaliable at http://www.innodb.com/hotbackup.html. Without the hot backup tool, the quickest way to take a snapshot of InnoDB tables is to shut the master server down and copy the data files, the logs, and the table definition files (.frm). To record the current log file name and offset, you should do the following before you shut down the server: 
        mysql> FLUSH TABLES WITH READ LOCK;
mysql> SHOW MASTER STATUS;
        And then record the log name and the offset from the output of SHOW MASTER STATUS as was shown earlier. Once you have recorded the log name and the offset, shut the server down without unlocking the tables to make sure it goes down with the snapshot corresponding to the current log file and offset: 
        shell> mysqladmin -uroot shutdown
        If the master has been previously running without log-bin enabled, the values of log name and position will be empty when you run SHOW MASTER STATUS. In that case, record empty string ('') for the log name, and 4 for the offset.
      4. Make sure that `my.cnf' on the master has log-bin if it is not there already and server-id=unique number in the [mysqld] section. If those options are not present, add them and restart the server. It is very important that the id of the slave is different from the id of the master. Think of server-id as something similar to the IP address - it uniquely identifies the server instance in the community of replication partners. 
        [mysqld]
log-bin
server-id=1
      5. マスター上の MySQL を再起動します。
      6. スレーブの my.cnf ファイルに、次を追加します： 
        server-id=<some unique number between 1 and 2^32-1 that is different from
 that of the master>
        システムに関連したものは <> 内の値で置き換えてあります。 server-id には、サーバーそれぞれで違う番号にしなくてはなりません。 (同じ複製のグループ内で)。 もし server-id を指定しなければ、 master-host が無い場合には 1 に なり、それ以外の場合には 2 に自動的になります。 マスターで server-id の記入漏れがあった場合、 マスターはスレーブからの接続を拒否します。 スレーブ上での記入漏れの場合には、スレーブはマスターへの接続を拒否します。 従って、server-id の省略はバイナリログのバックアップのためにだけ良 いことです。
      7. While the slave is running, make it forget about the old replication configuration if it has been replicating previously: 
        mysql> RESET SLAVE;
      8. スレーブのデータディレクトリにデータのスナップショットをコピーします。 ファイルとディレクトリのユーザーとパーミッションは確実に正しいものに してください。 これらのファイルに対して、 MySQL を実行している アカウントで、読み書きできるようにする必要があります。
      9. スレーブの再起動。
      10. Once the slave comes up, execute the following command: 
        mysql> CHANGE MASTER TO MASTER_HOST='<master host name>',
 MASTER_USER='<replication user name>',
 MASTER_PASSWORD='<replication password>',
 MASTER_LOG_FILE='<recorded log file name>',
 MASTER_LOG_POS=<recorded log offset>;
        replacing the values in <> with the actual values relevant to your system.
      11. Start the slave thread: 
        mysql> SLAVE START;

      上記を行なった後、スレーブはマスターに接続し、スナップショット以後の 更新をキャッチするはずです。

      もしスレーブに server-id をセットし忘れた場合、エラーログファイルに 次のようなエラーが出るでしょう： 

      Warning: one should set server_id to a non-0 value if master_host is set.
The server will not act as a slave.

      もしマスターにセットし忘れたなら、スレーブはマスターに接続できません。

      もし何かの理由でスレーブが複製できなかったなら、スレーブ上のエラーログ ファイルに、エラーメッセージが出るでしょう。

      一度スレーブがレプリケーションを始めたなら、 エラーログファイルと同じディレクトリに master.info ファイルを見ることができます。 master.info ファイルはスレーブに使用され、 これは、マスターのバイナリログのいくつまで処理したかを保持しています。 このファイルを消したり編集したりしては いけません。 (あなたがやろうとしていることが確実に分かるまでは)。 そういうやむを得ない場合には、 CHANGE MASTER TO コマンドの使用の方が良いです。

      Now that you have a snapshot, you can use it to set up other slaves. To do so, follow the slave portion of the procedure described above. You do not need to take another snapshot of the master.

      4.10.4 レプリケーション機能と既知の問題

      以下はサポートされていることとサポートされていないことの説明です:

      • レプリケーションは AUTO_INCREMENT, LAST_INSERT_ID, TIMESTAMP 値を正しく扱います。
      • 更新中の RAND() はうまく複製できません。 RAND() での更新を複製する場合は、RAND(some_non_rand_expr) を 使用してください。 例えば、UNIX_TIMESTAMP() を RAND() の引数に使用するとか。
      • マスターとスレーブは同じキャラクター・セット (--default-character-set) を使 用しなくてはなりません。 もし違った場合、スレーブ上で duplicate key errors が出るかもしれません。 これは、マスター上で一意のキーであったとしても、 違う キャラクター・セット ではそうとはみなされない事があるからです。
      • In 3.23, LOAD DATA INFILE will be handled properly as long as the file still resides on the master server at the time of update propagation. LOAD LOCAL DATA INFILE will be skipped. In 4.0, this limitation is not present - all forms of LOAD DATA INFILE are properly replicated.
      • ユーザー変数を使用したクエリは、(まだ) replication-safe ではありません。
      • FLUSH コマンドはバイナリログに記録されません。 もちろん、スレーブに複製されません。 これは FLUSH が通常は何もデータを変更しないからです。 しかし、仮に MySQL の権限データベースを複製していて、 GRANT 文ではなくて直接 MySQL 権限テーブルを変更した場合には、 権限を反映させるために、スレーブ上で FLUSH PRIVILEGES を行なわなくては なりません。
      • 3.23.29 以降の一時テーブルは正しく複製されます。ただし、スレーブサーバ(ス レーブスレッドではない)をシャットダウンした時に、いくつかの一時テーブルが オープンされていて、続く更新で使用される場合を除きます。この問題を扱うため に、スレーブをシャットダウンするには、SLAVE STOP を行ない、それから Slave_open_temp_tables 変数が 0 かどうかをチェックし、そして、 mysqladmin shutdown を発行してください。数値が 0 でない場合は、スレー ブスレッドを SLAVE START で再起動して、次回に幸運かどうかを見てくだ さい。 もっときれいな解決方法は、バージョン 4.0 まで待つ必要があります。それ以前 のバージョンの一時テーブルは正しく複製されません - アップグレードするか 一 時テーブルでのすべてのクエリの前にクライアント上で SET SQL_LOG_BIN=0 の実行をお勧めします。
      • MySQL は 1 つのマスターと複数のスレーブの構成のみをサポートします。 4.x では、何かが現在のマスターを故障させた場合に、自動的にマスターを変更す る voting アルゴリズムを追加するでしょう。また、異なるスレーブに select ク エリを送ることで、負荷分散を行なうための手助けとなるような 'エージェント' プロセスも導入するでしょう。
      • バージョン 3.23.26 から、log-slave-updates を有効にすることで、 マスターとスレーブの関係を輪っか状にすることが可能です。 しかし、多くのクエリは、この種のセットアップでは正しく動作しません。 違うシーケンス、違うサーバーで行なわれる更新によって引き起こる 潜在的な問題に対応するように、クライアントコードを注意して書かない限りは。 これは以下のようなセットアップを意味します： 
        A -> B -> C -> A
        このセットアップはテーブル間での更新に何も衝突が無い場合にのみ、動作します。 仮に A と C でデータを insert するとき、C にinsertするレコードのキーと 競合するようなレコードを A に insert してはいけません。 同じレコードを、２つのサーバーで更新すべきではありません。 もしそこで更新が適用される順番が重要なら。 ログのフォーマットは バージョン 3.23.36 で変更になりました。 3.23.36 以前のスレーブは、3.23.36 以上のログファイルを読むことができません。
      • もしスレーブ上でクエリがエラーになると、スレーブのスレッドは停止され、 .err ファイルにメッセージが現われます。 この場合、スレーブを手動で接続し、エラーの原因を修正し(例えば、テーブルが無いとか)、 その後、 SLAVE START SQLコマンドを実行します (このコマンドはバージョン 3.23.16 以上から)。 バージョン 3.23.15 までは、サーバーを再起動しなくてはなりません。
      • もしマスターへの接続が失われた場合、スレーブは直ちにリトライし、 それでも失敗した場合は、 master-connect-retry 秒毎（デフォルトでは 60秒）に リトライを繰り返します。 このため、マスターをシャットダウンして、しばらくあとに再起動することは安全 です。スレーブはネットワーク接続性の停止も処理できます。 However, the slave will notice the network outage only after receiving no data from the master for slave_net_timeout seconds. So if your outages are short, you may want to decrease slave_net_timeout ; see 「4.5.6.4 SHOW VARIABLES」節.
      • スレーブのシャットダウンも安全にできます。レプリケーションを止めた位置を 保存するようにしているからです。 きれいでないシャットダウンは問題を引き起こすでしょう。システムが落ちる前に もしディスクキャッシュがシンクされない場合には特に。 もしあなたが良い UPS を持っているならば、安全性を高めることができるでしょう。
      • もしマスターが非標準のポートを使用している場合、 my.cnf ファイルに master-port パラメターを書くことにより、 ポート番号を指定できます。
      • バージョン 3.23.15 では、すべてのテーブルとデータベースが複製されます。バー ジョン 3.23.16 からは my.cnf 内の replicate-do-db 命令でデー タベースのセットに、または replicate-ignore-db でデータベースのセッ トを除外して、複製を制限できます。注意: バージョン 3.23.23 になるまでは、 複製から除外されたデータベースで LOAD DATA INFILE を行なうと、正し く扱えないというバグがありました。
      • バージョン 3.23.16 から、マスター上で、SET SQL_LOG_BIN = 0 でレプリケーシ ョン(バイナリ) ログを止めることができます。 SET SQL_LOG_BIN = 1 で再びログを採取することができます。 これを行なう場合には、SUPER 権限(in MySQL 4.0.2 and above)か PROCESS 権限(in older MySQL versions) が必要です。
      • バージョン 3.23.19 から、何かがおかしくなって、残っている複製をクリーンナップし て、まったくの最初から開始したいときのために、 FLUSH MASTER と FLUSH SLAVE コマンドが用意されました。 バージョン 3.23.26 から、これらの名前を RESET MASTER と RESET SLAVE に変更しました。 互換性のために、古い FLUSH もまだ動作します。 （訳注： このコマンドは、bin log を 001 からに強制してしまうため、 場合によっては複製をおかしくすることも有る。使用には注意。）
      • バージョン 3.23.23 から、 CHANGE MASTER TO を使用して、 マスターを変更したりポジションを変更したりできるようになりました。
      • バージョン 3.23.23 から、 binlog-ignore-db を使用して、 バイナリログを取らないデータベースを指定できるようになりました。
      • バージョン 3.23.26 から、 replicate-rewrite-db を使用して、 マスター上のデータベースの名前を、スレーブ上では違う名前にするように、 スレーブに指示することができるようになりました。
      • バージョン 3.23.28 から、 スレーブが実行している最中に、 古いログを取り去るために、 PURGE MASTER LOGS TO 'log-name' が使用できます。 This will remove all old logs before, but not including 'log-name'.
      • Due to the non-transactional nature of MyISAM tables, it is possible to have a query that will only partially update a table and return an error code. This can happen, for example, on a multi-row insert that has one row violating a key constraint, or if a long update query is killed after updating some of the rows. If that happens on the master, the slave thread will exit and wait for the DBA to decide what to do about it unless the error code is legitimate and the query execution results in the same error code. If this error code validation behaviour is not desirable, some ( or all) errors could be masked out with slave-skip-errors option starting in Version 3.23.47.
      • While individual tables can be excluded from replication with replicate-do-table/replicate-ignore-table or replicate-wild-do-table/replicate-wild-ignore-table, there are currently some design deficiencies that in some rather rare cases produce unexpected results. The replication protocol does not inform the slave explicitly which tables are going to be modified by the query -- so the slave has to parse the query to know this. To avoid redundant parsing for queries that will end up actually being executed, table exclusion is currently implemented by sending the query to the standard MySQL parser, which will short-circuit the query and report success if it detects that the table should be ignored. In addition to several inefficiencies, this approach is also more bug prone, and there are two known bugs as of Version 3.23.49 -- because the parser automatically opens the table when parsing some queries the ignored table has to exist on the slave. The other bug is that if the ignored table gets partially updated, the slave thread will not notice that the table actually should have been ignored and will suspend the replication process. While the above bugs are conceptually very simple to fix, we have not yet found a way to do this without a significant code change that would compromise the stability status of 3.23 branch. There exists a workaround for both if in the rare case it happens to affect your application -- use slave-skip-errors.

      4.10.5 `my.cnf' 内のレプリケーションオプション

      レプリケーションを使用する場合は、我々は MySQL Version 3.23.33 以降を 推奨します。 これより古いバージョンでも動きますが、古い物はバグがあったり機能が無かったりします。 Some of the options mentioned here may not be available in your version if it is not the most recent one. For all options specific to the 4.0 branch, there is a note indicating so. Otherwise, if you discover that the option you are interested in is not available in your 3.23 version, and you really need it, please upgrade to the most recent 3.23 branch.

      Please be aware that 4.0 branch is still in alpha, so some things may not be working as smoothly as you would like. If you really would like to try the new features of 4.0, we recommend you do it in such a way that in case there is a problem your mission critical applications will not be disrupted.

      マスターとスレーブの両方に、 server-id オプションが必要です。 これは一意のレプリケーションid をセットします。 マスター、スレーブそれぞれのために、一意な値を、1 から 2^32-1 までの間から 選ばねばなりません。 例: server-id=3

      以下の表は、MASTER で使用できるオプションを示したものです:

      オプション 説明
      log-bin=filename Write to a binary update log to the specified location. Note that if you give it a parameter with an extension (for example, log-bin=/mysql/logs/replication.log ) versions up to 3.23.24 will not work right during replication if you do FLUSH LOGS . The problem is fixed in Version 3.23.25. If you are using this kind of log name, FLUSH LOGS will be ignored on binlog. log を clear するには、FLUSH MASTER の実行をします。 FLUSH SLAVE を全てのスレーブ上で実行することも忘れてはいけません。 バージョン 3.23.36 以上では、RESET MASTER と RESET SLAVE を使用す べきです。 You can use this option if you want to have a name which is independant of your hostname (could be useful in case you rename your host one day). （訳注： RESET はログを本当に全部消してしまうので、注意が必要。）
      log-bin-index=filename FLUSH LOGS コマンドの実行のためには、どのログが現在使用されているもので、 どれがローテートされたもので、どの順番なのか、ということを知る必要があります。 この情報はバイナリログ index ファイルに記述されます。 デフォルトでは ``hostname`.index' というファイルになります。 違う名前にしたい場合に、このオプションを使用します。 Example: log-bin-index=db.index
      sql-bin-update-same 設定されると、SQL_LOG_BIN に値を設定すると自動的に SQL_LOG_UPDATE を同じ値に設定します。逆も同様です。
      binlog-do-db=database_name 現在の(いうなれば USE で選択している)データベースが database_name の場合、 バイナリログに更新をログすべきことをマスターに伝えます。 他のすべてのデータベースは無視されます。 注意: これを使用する場合は、現在のデータベースでだけ更新を行なうことを 確実にすべきです。 Example: binlog-do-db=sales
      binlog-ignore-db=database_name 現在のデータベース(USEで選択しているデータベース) が database_name という名前であり、このデータベースの更新記録を バイナリログに格納すべきでないと、マスターに伝えます。 注意: これを使用する場合は、現在のデータベー スでだけ更新を行なうことを確実にすべきです。 Example: binlog-ignore-db=accounting

      次の表は SLAVE に使用できるオプションです:

      Option Description
      master-host=host マスタのホスト名か IP アドレス。 もし設定されていないと、スレーブはスタートしません。 Note that the setting of master-host will be ignored if there exists a valid `master.info' file. Probably a better name for this options would have been something like bootstrap-master-host, but it is too late to change now. Example: master-host=db-master.mycompany.com
      master-user=username スレーブスレッドがマスターに接続する時に自分を認証するためのユーザ。ユーザ は FILE 権限を持つ必要があります。マスターユーザが設定されない場合 は、test が適用されます。 The value in `master.info' will take precedence if it can be read. Example: master-user=scott
      master-password=password スレーブスレッドがマスターサーバに接続する時に認証するパスワード。設定され ない場合は、空のパスワードが適用されます。 The value in `master.info' will take precedence if it can be read. Example: master-password=tiger
      master-port=portnumber マスターが listen しているポート。設定されない場合は、MYSQL_PORT の コンパイル時の設定が適用されます。configure オプションで何もしてな ければ、これは 3306 です。 The value in `master.info' will take precedence if it can be read. Example: master-port=3306
      master-connect-retry=seconds マスターが落ちたり接続が失われた場合に、スレーブスレッドがマスターへの接続 を再試行するまでに休眠する秒数。デフォルトは 60。 Example: master-connect-retry=60
      master-ssl Available after 4.0.0. Turn SSL on for replication. Be warned that is this is a relatively new feature. Example: master-ssl
      master-ssl-key Available after 4.0.0. Master SSL keyfile name. Only applies if you have enabled master-ssl. Example: master-ssl-key=SSL/master-key.pem
      master-ssl-cert Available after 4.0.0. Master SSL certificate file name. Only applies if you have enabled master-ssl. Example: master-ssl-key=SSL/master-cert.pem
      master-info-file=filename 複製処理がマスターのどこまで行なったかを覚えておくファイルの場所。デフォル トはデータディレクトリの `master.info' です。 You should not need to change this. Example: master-info-file=master.info
      report-host バージョン 4.0.0 から。 スレーブ登録中にマスタに報告されるスレーブのホス ト名と IP 。これは SHOW SLAVE HOSTS の出力に表われます。スレーブ をマスタに登録したくない場合は、設定しないでください。注意: マスタがスレー ブ接続時のソケットの IP を単純に読むだけでは不十分です。NAT や他 のルーティングの問題で、マスタや他のホストからスレーブへの接続IPが正しく ないことがあります。 Example: report-host=slave1.mycompany.com
      report-port バージョン 4.0.0 から。スレーブ登録中にマスタに報告されるスレーブのポー ト。スレーブがデフォルトでないポートで listen する場合か、マスタか他のク ライアントからスレーブへの特殊なトンネルを持つ場合にだけ設定してください。 確かでなければ、このオプションを設定しないでください。
      replicate-do-table=db_name.table_name 指定されたテーブルに複製を制限することをスレーブスレッドに伝えます。一つ以 上のテーブルを指定するには、この命令を複数回(各テーブルに１回ずつ)使用しま す。 This will work for cross-database updates, in contrast to replicate-do-db. Example: replicate-do-table=some_db.some_table
      replicate-ignore-table=db_name.table_name 指定されたテーブルを複製しないことをスレーブスレッドに伝えます。 (even if any other tables may be update by the same command). 一つ以上の テーブルを無視するように指定するには、この命令を複数回(各テーブルに１回ず つ)使用します。これは replicate-ignore-db とは対照的に、データベー スをまたがった更新について動作します。 Example: replicate-ignore-table=db_name.some_table
      replicate-wild-do-table=db_name.table_name 指定されたワイルドカードパターンに適合するテーブルに複製を制限することをス レーブスレッドに伝えます。一つ以上のテーブルを指定するには、この命令を複数 回(各テーブルに１回ずつ)使用します。これはデータベースをまたがった更新につ いて動作します。 Example: replicate-wild-do-table=foo%.bar% は foo で始まるすべての データベースの bar で始まるテーブルだけに更新を複製します。 Note that if you do replicate-wild-do-table=foo%.% then the rule will be propagated to CREATE DATABASE and DROP DATABASE, i.e. these two statements will be replicated if the database name matches the database pattern ('foo%' here) (this magic is triggered by '%' being the table pattern).
      replicate-wild-ignore-table=db_name.table_name 与えられたワイルドカードパターンに適合するテーブルを複製しないことをスレー ブスレッドに伝えます。一つ以上のテーブルを無視するように指定するには、この 命令を複数回(各テーブルに１回ずつ)使用します。これはデータベースをまたがっ た更新について動作します。 Example: replicate-wild-ignore-table=foo%.bar% は foo で始まるすべての データベースの bar で始まるテーブルを更新しません。 Note that if you do replicate-wild-ignore-table=foo%.% then the rule will be propagated to CREATE DATABASE and DROP DATABASE, i.e. these two statements will not be replicated if the database name matches the database pattern ('foo%' here) (this magic is triggered by '%' being the table pattern).
      replicate-ignore-db=database_name Tells the slave thread to not replicate any command where the current database (i.e. the one selected by USE) is database_name. To specify more than one database to ignore, use the directive multiple times, once for each database. You should not use this directive if you are using cross table updates and you don't want these update to be replicated. The main reason for this ``just-check-the-current-database'' behaviour is that it's hard from the command alone to know if a query should be replicated or not ; for example if you are using multi-table-delete or multi-table-update commands in MySQL 4.x that go across multiple databases. It's also very fast to just check the current database, as this only has to be done once at connect time or when the database changes. If you need cross database updates to work, make sure you have 3.23.28 or later, and use replicate-wild-ignore-table=db_name.%. Example: replicate-ignore-db=some_db
      replicate-do-db=database_name Tells the slave thread to restrict replication to commands where the current database (i.e. the one selected by USE) is database_name. To specify more than one database, use the directive multiple times, once for each database. Note that this will not replicate cross-database queries such as UPDATE some_db.some_table SET foo='bar' while having selected a different or no database. If you need cross database updates to work, make sure you have 3.23.28 or later, and use replicate-wild-do-table=db_name.%. Example: replicate-do-db=some_db
      log-slave-updates スレーブスレッドからの更新をバイナリログに記録するように、スレーブに告げます。 デフォルトは Off です。 Of course, it requires that the slave be started with binary logging enabled (log-bin option). You have to use log-slave-updates to chain several slaves ; for example for the following setup to work 
      A -> B ->C
      (C is a slave of B which is a slave of A) you need to start B with the log-slave-updates option.
      replicate-rewrite-db=from_name->to_name Tells the slave to translate the current database (i.e. the one selected by USE) to to_name if it was from_name on the master. Only statements involving tables may be affected (CREATE DATABASE, DROP DATABASE won't), and only if from_name was the current database on the master. This will not work for cross-database updates. Example: replicate-rewrite-db=master_db_name->slave_db_name
      slave-skip-errors= [err_code1,err_code2,... | all] バージョン 3.23.47 以上。 与えられたエラーコードではレプリケーションを止めないように、 スレーブスレッドに告げます。 通常、レプリケーションはエラーに出会うと中止し、マニュアルでデータの矛盾を 解決する機会をユーザに与えます。 このオプションは、なぜエラーが発生したのかを完全に理解するまでは 使用してはいけません。 もしレプリケーションのセットアップ、クライアントプログラム、MySQL 自身に なにもバグがないのであれば、エラーで止まるはずはありません。 このオプションを見境なく使用すると、スレーブで期待に反してマスタとの同期が ずれ、なぜ問題が発生したかについての理解ができない結果になるでしょう。 エラーコードには、スレーブのログファイルに記録されているものや SHOW SLAVE STATUS で出力される、数字の番号を使用しなくてはなりません。 全てのエラーメッセージは、ソース配布に含まれる Docs/mysqld_error.txt にあります. とても推奨できない値である all を使用することもできます（ですがすべ きではありません）。これはすべてのエラーメッセージを無視し、keep barging along regardless. 言うまでもなく、これを使用する場合は、データの完全性に関 してなんの保証もできません。 Please do not complain if your data on the slave is not anywhere close to what it is on the master in this case -- you have been warned. Example: slave-skip-errors=1062,1053 or slave-skip-errors=all
      skip-slave-start 起動時にスレーブを開始しないようにスレーブサーバに伝えます。ユーザは後で SLAVE START で開始できます。
      slave_compressed_protocol=# If 1, then use compression on the slave/client protocol if both slave and master support this.
      slave_net_timeout=# 読み込みがアボートする前にマスターからデータを待つ秒数。

      4.10.6 レプリケーションに関連する SQL コマンド

      レプリケーションは SQL インタフェースを通じて制御できます。以下はコマンド のサマリです:

      Command Description
      SLAVE START スレーブスレッドを開始します。 As of MySQL 4.0.2, you can add IO_THREAD or SQL_THREAD options to the statement to start the I/O thread or the SQL thread. The I/O thread reads queries from the master server and stores them in the relay log. The SQL thread reads the relay log and executes the queries. (スレーブ)
      SLAVE STOP スレーブスレッドを停止します。 Like SLAVE START, this statement may be used with IO_THREAD and SQL_THREAD options. (スレーブ)
      SET SQL_LOG_BIN=0 ユーザが SUPER 権限(in MySQL 4.0.2 and above) PROCESS (in older MySQL versions) を持っている場合に 更新ログを無効にします。そうでなければ無視されます。(マスター)
      SET SQL_LOG_BIN=1 ユーザが SUPER 権限(in MySQL 4.0.2 and above)か PROCESS 権限(in older MySQL versions) を 持っている場合更新ロギングを再度有効にします。 そうでなければ無視されます。(マスター)
      SET GLOBAL SQL_SLAVE_SKIP_COUNTER=n マスターからの次の n イベントをスキップします。スレーブスレッ ドが実行していない場合にだけ正当です。そうでなければエラーになります。レプ リケーションの不調からの復旧に有用です。
      RESET MASTER インデックスファイルにリストされたすべてのバイナリログを削除し、 binlog インデックスファイルを空にリセットします。3.23.26 バージョンより前 では、FLUSH MASTER (Master)
      RESET SLAVE スレーブにマスターログのレプリケーション位置を忘れさせます。 3.23.26 バージョンより前ではこのコマンドは FLUSH SLAVE と呼ばれてい ました(Slave)
      LOAD TABLE tblname FROM MASTER マスターからスレーブにテーブルのコピーをダウンロードします。主に LOAD DATA FROM MASTER のデバッグ用に実装されていますが、but some ``gourmet'' users might find it useful for other things. 自分自身が並の "非ハッカー" タイプの ユーザー(並みのユーザー)であると思う場合は、使用しないでください。 Requires that the replication user which is used to connect to the master has RELOAD and SUPER privileges on the master. Please read the timeout notes in the description of LOAD DATA FROM MASTER below, they apply here too. (Slave)
      LOAD DATA FROM MASTER バージョン 4.0.0 から。 マスターのスナップショットを取り、スレーブにコピーします。 Requires that the replication user which is used to connect to the master has RELOAD and SUPER privileges on the master. スレーブが正しい位置からレプリケーションを開始するように、 MASTER_LOG_FILE と MASTER_LOG_POS の値を更新します。 Will honor table and database exclusion rules specified with replicate-* options. So far works only with MyISAM tables and acquires a global read lock on the master while taking the snapshot. In the future it is planned to make it work with InnoDB tables and to remove the need for global read lock using the non-blocking online backup feature. If you are loading big tables, you may have to increase the values of net_read_timeout and net_write_timeout on both your master and slave ; see 「4.5.6.4 SHOW VARIABLES」節. Note that LOAD DATA FROM MASTER does NOT copy any tables from the mysql database. This is to make it easy to have different users and privileges on the master and the slave.
      CHANGE MASTER TO master_def_list マスターパラメータを master_def_list に指定された値に変更し、 スレーブスレッドを再起動します。master_def_list はコンマで区切られ た master_def のリストです。master_def は次のうちの一つです : MASTER_HOST, MASTER_USER, MASTER_PASSWORD, MASTER_PORT, MASTER_CONNECT_RETRY, MASTER_LOG_FILE, MASTER_LOG_POS. For example: 
      CHANGE MASTER TO
  MASTER_HOST='master2.mycompany.com',
  MASTER_USER='replication',
  MASTER_PASSWORD='bigs3cret',
  MASTER_PORT=3306,
  MASTER_LOG_FILE='master2-bin.001',
  MASTER_LOG_POS=4;
      変更する必要のある値だけを指定する必要があります。省略した値は同じ値を維持 します。ホストまたはポートを変更した時を除きます。この場合、スレーブは異な るホストまたは異なるポートに接続しているのでマスターが異なっているとみなし ます。従って、古いログと位置の値はどこにも該当しません。そして、自動的に空 文字列と 0 にそれぞれリセットされます (開始値)。注意: スレーブを再起動する 場合、最後のマスターを覚えています。これが望ましくない場合、 `master.info' ファイルを再起動前に削除すべきです。すると、スレーブは my.cnf またはコマンドラインからそのマスターを読み込みます。 このコマンドは、マスタのスナップショットを持っていて、スナップショットに対 応するマスタ上のログとオフセットの記録がある場合に、スレーブをセットアップ するのに有用です。スナップショットからのリストア後にスレーブ上で、 CHANGE MASTER TO MASTER_LOG_FILE='log_name_on_master', MASTER_LOG_POS=log_offset_on_masterを実行できます。 (Slave)
      SHOW MASTER STATUS マスターの binlog のステータス情報を提供します。(Master)
      SHOW SLAVE HOSTS バージョン 4.0 からの機能。 Gives a listing of slaves currently registered with the master. (Master)
      SHOW SLAVE STATUS スレーブスレッドの基本的な パラメータのステータス情報を提供します。(Slave)
      SHOW MASTER LOGS バージョン 3.23.28 以降だけで有効です。 マスター上のバイナリログをリストします。 どれくらい行くべきかを見つけるためには、 このコマンドを PURGE MASTER LOGS TO よりも先に使用すべきです。 (Master)
      SHOW BINLOG EVENTS [ IN 'logname' ] [ FROM pos ] [ LIMIT [offset,] rows ] バージョン 4.0 からの機能。 binary update log 中のイベントを見せます。 基本的にはテストやデバッグで使用されます。 通常のクライアントからバイナリログを読む必要がある場合にも 使用することが可能です。 (Master)
      SHOW NEW MASTER FOR SLAVE WITH MASTER_LOG_FILE='logfile' AND MASTER_LOG_POS=pos AND MASTER_LOG_SEQ=log_seq AND MASTER_SERVER_ID=server_id バージョン 4.0 からの機能。 おそらく死んだ／無効になったマスタのスレーブが、同じマスタをレプリケーショ ンしていた他のスレーブからレプリケーションするようにスイッチすることが必 要な場合に、このコマンドが使用されます。コマンドは再計算されたレプリケー ション coordinates を返します (the slave's current binary log file + name and position within that file). この出力は続く CHANGE MASTER TO コマン ドで使用することができます。通常、ユーザはこのコマンドを実行する必要はあ りません。これは本来 fail-safe レプリケーションコードに内部使用に予約さ れています。この操作を記述するのにもっと直観的な方法を見つけた場合、この 文法は変更されるでしょう。
      PURGE MASTER LOGS TO 'logname' バージョン 3.23.28 からの機能。 index ファイルに書かれているログファイルのうち、 指定されたログよりも前のログファイルを全て消します。 index ファイルのリストからもエントリを消します。 そして、指定されたログを一番最初の物とします。 例えば： 
      PURGE MASTER LOGS TO 'mysql-bin.010'
      （訳注： このコマンドの場合、mysql-bin.001 〜 mysql-bin.009 までの ファイルは消され、mysql.index ファイルの中身は、mysql-bin.010 のみ、 記述される状態になるということ。） 削除しようとしているログの一つを現在読み込み中の実行中スレーブがある場合、 このコマンドは何も行なわず、エラーで失敗します。しかし、休眠中のスレーブが あり、それが読もうとしているログの一つをパージしてしまうと、スレーブは複製 できなくなります。このコマンドはスレーブが複製中には安全に実行できます - それらを停止する必要はありません。 最初に SHOW SLAVE STATUS で、どのログが on になっているか、すべての スレーブをチェックする必要があります。それからマスターで SHOW MASTER LOGS でログのリストを行ない、すべてのスレーブに共通の最も古いログ を見つけ(すべてのスレーブが最新の場合、リストの最後のログになります)、削除 しようとするすべてのログをバックアップし、目的のログをパージします。

      4.10.7 Replication FAQ

      Q: マスタが既に走っている状態で、マスタを止めないで、新しく スレーブを作るには、どのようにすればいいの?

      A: いくつか方法があります。 もしマスタのどこかの時点でのバックアップを取っていて、そして そのバックアップした時点に対応する バイナリログの名前と位置を記録しているのであれば、 ( SHOW MASTER STATUS で知ることが出来ます) 以下のようにします：

      • スレーブには一意の server id を割り当てます。
      • Execute CHANGE MASTER TO MASTER_HOST='master-host-name', MASTER_USER='master-user-name', MASTER_PASSWORD='master-pass', MASTER_LOG_FILE='recorded-log-name', MASTER_LOG_POS=recorded_log_pos
      • SLAVE START 実行

      もし現在のマスタのバックアップを取っていないのであれば、以下が素早く セットアップする方法です：

      • FLUSH TABLES WITH READ LOCK
      • gtar zcf /tmp/backup.tar.gz /var/lib/mysql (パスは環境にあわせて)
      • SHOW MASTER STATUS - 確実にこの出力をメモしておくように - 後で必要になります
      • UNLOCK TABLES

      Afterwards, follow the instructions for the case when you have a snapshot and have recorded the log name and offset. 同じスナップショットをいくつものスレーブをセットアップするために使用す ることができます。一度マスタのスナップショットを得れば、マスタのバイナ リログが無傷で残っている限り、何日でも場合によっては一月でも、待ってス レーブを設定することができます。理論的には待つ期間は無限にできます。２ つの現実的な制限があり、１つは古いログで一杯になるマスタのディスク容量 と、スレーブがキャッチアップするのに掛かる時間の大きさです。

      バージョン 4.0.0 以降では、LOAD DATA FROM MASTER も使用できます。 これは、スナップショットを取ってスレーブにリストアし、ログ名とオフセッ トをスレーブ上で一度に調整する便利なコマンドです。将来、LOAD DATA FROM MASTER はスレーブをセットアップする推奨方法になるでしょう。 しかし、このコマンドを使用する場合、読み込みロックが長い時間保持される こともあることに注意してください。まだ、我々がそうしたいほど効率よくは 実装されていません。大きなテーブルがある場合、現時点での推奨方法は、ま だ FLUSH TABLES WITH READ LOCK 実行後のローカル tar スナッ プショットです。

      Q: スレーブは常にマスターに接続していなければならないの?

      A: いいえ、その必要はありません。 スレーブを数時間でも数日でも止めたり落としたりしておき、 そのあと再接続して、更新を行ない、再度また、スレーブを落とすことが可能です。 So you can, for example, use master-slave setup over a dial-up link that is up only for short periods of time. The implications of that are that at any given time the slave is not guaranteed to be in sync with the master unless you take some special measures. In the future, we will have the option to block the master until at least one slave is in sync.

      Q: スレーブがキャッチアップするまで、マスタの更新をブロックする には？

      A: 次のコマンドを実行してください:

      • Master: FLUSH TABLES WITH READ LOCK
      • Master: SHOW MASTER STATUS - ログ名とオフセットを記録してください
      • Slave: SELECT MASTER_POS_WAIT('recorded_log_name', recorded_log_offset) select が復帰した時、スレーブはマスタと同期されています
      • Master: UNLOCK TABLES - これでマスタは更新を続けられます。

      Q: Why do I sometimes see more than one Binlog_Dump thread on the master after I have restarted the slave?

      A: Binlog_Dump is a continuous process that is handled by the server in the following way:

      • Catch up on the updates.
      • Once there are no more updates left, go into pthread_cond_wait(), from which we can be awakened either by an update or a kill.
      • On wake up, check the reason. If we are not supposed to die, continue the Binlog_dump loop.
      • If there is some fatal error, such as detecting a dead client, terminate the loop.

      So if the slave thread stops on the slave, the corresponding Binlog_Dump thread on the master will not notice it until after at least one update to the master (or a kill), which is needed to wake it up from pthread_cond_wait(). In the meantime, the slave could have opened another connection, which resulted in another Binlog_Dump thread.

      The above problem should not be present in Version 3.23.26 and later versions. In Version 3.23.26 we added server-id to each replication server, and now all the old zombie threads are killed on the master when a new replication thread connects from the same slave

      Q: replication log をどうやってローテートするの?

      A: バージョン 3.23.28 からでは、PURGE MASTER LOGS TO コマンド を使用するべきです。 実行前には、どのログが消せれるか確認し、場合によっては バックアップを取っておきます。 In earlier versions the process is much more painful, and cannot be safely done without stopping all the slaves in the case that you plan to re-use log names. You will need to stop the slave threads, edit the binary log index file, delete all the old logs, restart the master, start slave threads, and then remove the old log files.

      Q: How do I upgrade on a hot replication setup?

      A: If you are upgrading pre-3.23.26 versions, you should just lock the master tables, let the slave catch up, then run FLUSH MASTER on the master, and FLUSH SLAVE on the slave to reset the logs, then restart new versions of the master and the slave. Note that the slave can stay down for some time -- since the master is logging all the updates, the slave will be able to catch up once it is up and can connect.

      バージョン 3.23.26 以降では、レプリケーションプロトコルのロック (変更のための)を持ちます。 そのため、あなたはマスタとスレーブを on the fly で 新しい 3.23 バージョンにアップグレードできます。 そして、マスタとスレーブがバージョン 3.23.26 以上の場合においては、 マスタとスレーブが違うバージョンの MySQL でもかまいません。

      Q: What issues should I be aware of when setting up two-way replication?

      A: MySQL replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed (cross-server) update. In other words, it is possible for client A to make an update to co-master 1, and in the meantime, before it propagates to co-master 2, client B could make an update to co-master 2 that will make the update of client A work differently than it did on co-master 1. Thus when the update of client A will make it to co-master 2, it will produce tables that will be different from what you have on co-master 1, even after all the updates from co-master 2 have also propagated. So you should not co-chain two servers in a two-way replication relationship, unless you are sure that you updates can safely happen in any order, or unless you take care of mis-ordered updates somehow in the client code.

      You must also realise that two-way replication actually does not improve performance very much, if at all, as far as updates are concerned. Both servers need to do the same amount of updates each, as you would have one server do. The only difference is that there will be a little less lock contention, because the updates originating on another server will be serialised in one slave thread. This benefit, though, might be offset by network delays.

      Q: How can I use replication to improve performance of my system?

      A: You should set up one server as the master, and direct all writes to it, and configure as many slaves as you have the money and rackspace for, distributing the reads among the master and the slaves. You can also start the slaves with --skip-bdb, --low-priority-updates and --delay-key-write=ALL to get speed improvements for the slave. In this case the slave will use non-transactional MyISAM tables instead of BDB tables to get more speed.

      Q: What should I do to prepare my client code to use performance-enhancing replication?

      A: If the part of your code that is responsible for database access has been properly abstracted/modularised, converting it to run with the replicated setup should be very smooth and easy -- just change the implementation of your database access to read from some slave or the master, and to always write to the master. If your code does not have this level of abstraction, setting up a replicated system will give you an opportunity/motivation to it clean up. You should start by creating a wrapper library /module with the following functions:

      • safe_writer_connect()
      • safe_reader_connect()
      • safe_reader_query()
      • safe_writer_query()

      safe_ means that the function will take care of handling all the error conditions.

      You should then convert your client code to use the wrapper library. It may be a painful and scary process at first, but it will pay off in the long run. All applications that follow the above pattern will be able to take advantage of one-master/many slaves solution. The code will be a lot easier to maintain, and adding troubleshooting options will be trivial. You will just need to modify one or two functions, for example, to log how long each query took, or which query, among your many thousands, gave you an error. If you have written a lot of code already, you may want to automate the conversion task by using Monty's replace utility, which comes with the standard distribution of MySQL, or just write your own Perl script. Hopefully, your code follows some recognisable pattern. If not, then you are probably better off rewriting it anyway, or at least going through and manually beating it into a pattern.

      Note that, of course, you can use different names for the functions. What is important is having unified interface for connecting for reads, connecting for writes, doing a read, and doing a write.

      Q: When and how much can MySQL replication improve the performance of my system?

      A: MySQL replication is most beneficial for a system with frequent reads and not so frequent writes. In theory, by using a one master/many slaves setup you can scale by adding more slaves until you either run out of network bandwidth, or your update load grows to the point that the master cannot handle it.

      In order to determine how many slaves you can get before the added benefits begin to level out, and how much you can improve performance of your site, you need to know your query patterns, and empirically (by benchmarking) determine the relationship between the throughput on reads (reads per second, or max_reads) and on writes max_writes) on a typical master and a typical slave. The example here will show you a rather simplified calculation of what you can get with replication for our imagined system.

      Let's say our system load consists of 10% writes and 90% reads, and we have determined that max_reads = 1200 - 2 * max_writes, or in other words, our system can do 1200 reads per second with no writes, our average write is twice as slow as average read, and the relationship is linear. Let us suppose that our master and slave are of the same capacity, and we have N slaves and 1 master. Then we have for each server (master or slave):

      reads = 1200 - 2 * writes (from bencmarks)

      reads = 9* writes / (N + 1) (reads split, but writes go to all servers)

      9*writes/(N+1) + 2 * writes = 1200

      writes = 1200/(2 + 9/(N+1)

      So if N = 0, which means we have no replication, our system can handle 1200/11, about 109 writes per second (which means we will have 9 times as many reads due to the nature of our application).

      If N = 1, we can get up to 184 writes per second.

      If N = 8, we get up to 400.

      If N = 17, 480 writes.

      Eventually as N approaches infinity (and our budget negative infinity), we can get very close to 600 writes per second, increasing system throughput about 5.5 times. However, with only 8 servers, we increased it almost 4 times already.

      Note that our computations assumed infinite network bandwidth, and neglected several other factors that could turn out to be significant on your system. In many cases, you may not be able to make a computation similar to the one above that will accurately predict what will happen on your system if you add N replication slaves. However, answering the following questions should help you decided whether and how much, if at all, the replication will improve the performance of your system:

      • What is the read/write ratio on your system?
      • How much more write load can one server handle if you reduce the reads?
      • How many slaves do you have bandwidth for on your network?

      Q: 冗長性/高可用性を提供するようにレプリケーションを使用するには？

      A: 現在有効な機能で、マスターとスレーブ(またはいくつかのスレーブ 達)をセットアップする必要があります。マスターが生きているかどうかを監視し、 アプリケーションとマスターのスレーブに失敗時に変更を指示するスクリプトを書 きます。以下はいくつかの提案です:

      • CHANGE MASTER TO コマンドを使用して、スレーブにマスターを変更するよ うに通知します。
      • マスターの場所が通知されるアプリケーションを保持する良い方法は、マスターの エントリをダイナミック DNS によって持つことです。bind では nsupdate を使って DNS を動的に更新できます。
      • スレーブを log-bin オプション付きで log-slave-updates 無しで 実行すべきです。この方法で、STOP SLAVE; RESET MASTER、他のス レーブ上で CHANGE MASTER TO を実行すると、すぐにスレーブがマスター になるように準備ができます。 It will also help you catch spurious updates that may happen because of misconfiguration of the slave (ideally, you want to configure access rights so that no client can update the slave, except for the slave thread) combined with the bugs in your client programs (they should never update the slave directly).

      我々は現在自動マスター選択システムを MySQL に統合するように働いていますが、 準備ができるまでは、あなた自身のモニタリングツールを作成する必要があります。

      Q: How does the slave server keep track of where it is on the master?

      A: The slave uses a file in the the data directory defined by the master-info-file=filename path. This file holds all the information needed by the slave to request new updates. The file contains the following information:

      Line# Description
      1 Binary log file id
      2 Log file postion
      3 Host (master)
      4 Login user
      5 Login password
      6 Login port
      7 Interval, the length of time between reconnects

      4.10.8 Troubleshooting Replication

      If you have followed the instructions, and your replication setup is not working, first eliminate the user error factor by checking the following:

      • Is the master logging to the binary log? Check with SHOW MASTER STATUS. If it is, Position will be non-zero. If not, verify that you have given the master log-bin option and have set server-id.
      • Is the slave running? Check with SHOW SLAVE STATUS. The answer is found in Slave_running column. If not, verify slave options and check the error log for messages.
      • If the slave is running, did it establish connection with the master? Do SHOW PROCESSLIST, find the thread with system user value in User column and none in the Host column, and check the State column. If it says connecting to master, verify the privileges for the replication user on the master, master host name, your DNS setup, whether the master is actually running, whether it is reachable from the slave, and if all that seems okay, read the error logs.
      • If the slave was running, but then stopped, look at SHOW SLAVE STATUS output and check the error logs. It usually happens when some query that succeeded on the master fails on the slave. This should never happen if you have taken a proper snapshot of the master, and never modify the data on the slave outside of the slave thread. If it does, it is a bug, read below on how to report it.
      • If a query on that succeeded on the master refuses to run on the slave, and a full database resync ( the proper thing to do ) does not seem feasible, try the following:
        • First see if there is some stray record in the way. Understand how it got there, then delete it and run SLAVE START
        • If the above does not work or does not apply, try to understand if it would be safe to make the update manually ( if needed) and then ignore the next query from the master.
        • If you have decided you can skip the next query, do SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; SLAVE START; to skip a query that does not use AUTO_INCREMENT or LAST_INSERT_ID(), or SET GLOBAL SQL_SLAVE_SKIP_COUNTER=2; SLAVE START; otherwise. The reason queries that use AUTO_INCREMENT or LAST_INSERT_ID() are different is that they take two events in the binary log of the master.
        • If you are sure the slave started out perfectly in sync with the master, and no one has updated the tables involved outside of slave thread, report the bug, so you will not have to do the above tricks again.
      • Make sure you are not running into an old bug by upgrading to the most recent version.
      • If all else fails, read the error logs. If they are big, grep -i slave /path/to/your-log.err on the slave. There is no generic pattern to search for on the master, as the only errors it logs are general system errors -- if it can, it will send the error to the slave when things go wrong.

      When you have determined that there is no user error involved, and replication still either does not work at all or is unstable, it is time to start working on a bug report. We need to get as much info as possible from you to be able to track down the bug. Please do spend some time and effort preparing a good bug report. Ideally, we would like to have a test case in the format found in mysql-test/t/rpl* directory of the source tree. If you submit a test case like that, you can expect a patch within a day or two in most cases, although, of course, you mileage may vary depending on a number of factors.

      The second best option is to write a simple program with easily configurable connection arguments for the master and the slave that will demonstrate the problem on our systems. You can write one in Perl or in C, depending on which language you know better.

      If you have one of the above ways to demonstrate the bug, use mysqlbug to prepare a bug report and send it to bugs@lists.mysql.com. If you have a phantom -- a problem that does occur but you cannot duplicate "at will":

      • Verify that there is no user error involved. For example, if you update the slave outside of the slave thread, the data will be out of sync, and you can have unique key violations on updates, in which case the slave thread will stop and wait for you to clean up the tables manually to bring them in sync.
      • Run slave with log-slave-updates and log-bin -- this will keep a log of all updates on the slave.
      • Save all evidence before resetting the replication. If we have no or only sketchy information, it would take us a while to track down the problem. The evidence you should collect is:
        • All binary logs on the master
        • All binary log on the slave
        • The output of SHOW MASTER STATUS on the master at the time you have discovered the problem
        • The output of SHOW SLAVE STATUS on the master at the time you have discovered the problem
        • Error logs on the master and on the slave
      • Use mysqlbinlog to examine the binary logs. The following should be helpful to find the trouble query, for example: 
        mysqlbinlog -j pos_from_slave_status /path/to/log_from_slave_status | head

      Once you have collected the evidence on the phantom problem, try hard to isolate it into a separate test case first. Then report the problem to bugs@lists.mysql.com with as much info as possible.

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_News.html0100644000175100001560000111114110021471264015366 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - D MySQL Change History Go to the first, previous, next, last section, table of contents.

      D MySQL Change History

      This appendix lists the changes from version to version in the MySQL source code.

      We are now working actively on MySQL 4.1 & 5.0 and will only provide critical bug fixes for MySQL 4.0 and MySQL 3.23. We update this section as we add new features, so that everybody can follow the development.

      Our TODO section contains what further plans we have for 4.1 & 5.0. 「1.8 MySQL and The Future (The TODO)」節参照.

      新しい変更を MySQL に施すと同時に、マニュアルを変更することに注意してください。 もしマニュアルにかかれているのに MySQL download page (http://www.mysql.com/downloads/) に 新しいバージョンの MySQL が見つからない場合、そのバージョンはまだリリースされていません！

      D.1 Changes in release 5.0.0 (Development)

      Version 5.0 is for the moment only available on for MySQL developers. It will be publicly available as soon we are confident that the base for stored procedures is sound and working.

      The following changelog shows what is already done in the 5.0 tree:

      • Some support for stored procedures (ANSI SQL 99 style).
      • Added SELECT INTO list_of_vars, which can be of mixed, i.e., global and local type.

      D.2 Changes in release 4.1.x (Alpha)

      Version 4.1 of the MySQL server includes many enhancements and new features: This version is available from our public bk tree and will be available as a binary shortly

      • Subqueries: 
        SELECT * from t1 where t1.a=(SELECT t2.b FROM t2);

SELECT * from t1 where (1,2,3) in (SELECT a,b,c from t2);
      • Derived tables: 
        SELECT t1.a from t1, (select * from t2) t3 WHERE t1.a=t3.a;
      • INSERT ... ON DUPLICATE KEY UPDATE syntax. This allows you to UPDATE an existing row if existed from before. (REPLACE allows you to overwrite an existing row, which is a different thing).
      • Unicode (UTF8) support.
      • Character sets can be defined per column, table and database.
      • BTREE index on HEAP tables.
      • Support for GIS (Geometrical data).
      • SHOW WARNINGS; Shows warnings for the last command. 「4.5.6.9 SHOW WARNINGS | ERRORS」節参照.
      • Faster binary protocol used with prepared statements.
      • Multi-line queries: You can now issue several queries at once and then read the results in one go.
      • Create Table: CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table LIKE table.

      For a full list of changes, please refer to the changelog sections for each individual 4.1.x release.

      D.2.1 Changes in release 4.1.0

      • On Windows, we are now using shared memory to communicate between server and client when they are running on the same machine and you are connecting to localhost.
      • REPAIR of MyISAM tables now uses less temporary disk space when sorting char columns.
      • DATE/DATETIME checking is now a bit stricter then before to be able to automatically distinguish between date, datetime, and time with microseconds. For example, dates of type YYYYMMDD HHMMDD are not supported anymore; One must either have separators between each DATE/TIME part or not at all.
      • Server side help for all MySQL functions. One can now type help week in the mysql client and get help for the week() function.
      • Added new client function: mysql_get_server_version().
      • Fixed bug in libmysqlclient that fetched field defaults
      • Fixed bug in `mysql.cc' client when skipping comments
      • Added record_in_range() method to MERGE tables to be able to choose the right index when there are many to choose from.
      • Replication now works with RAND() and user variables @var.
      • Allow on to change mode for ANSI_QUOTES on the fly.
      • EXPLAIN SELECT now can be killed. 「4.5.5 KILL 構文」節参照.
      • REPAIR TABLE now can be killed. 「4.5.5 KILL 構文」節参照.
      • Allow one to specify empty key lists for USE|IGNORE|FORCE INDEX.
      • DROP TEMPORARY TABLE now only drops temporary tables and doesn't end transactions.
      • Added a support for UNION in derived tables
      • TIMESTAMP is now returned as string of type 'YYYY-MM-DD HH:MM:DD'.
      • New faster client/server protocol which supports prepared statements, bound parameters, and bound result columns, binary transfer of data, warnings.
      • Added database and real table name (in case of alias) to the MYSQL_FIELD structure.
      • Multi-line queries: You can now issue several queries at once and then read the results in one go.
      • In CREATE TABLE foo (a int not null primary key) the PRIMARY word is now optional.
      • In CREATE TABLE the attribute SERIAL is now an alias for BIGINT NOT NULL AUTO_INCREMENT UNIQUE.
      • SELECT ... FROM DUAL is an alias for SELECT .... (To be compatible with some other databases).
      • If one creates a too long CHAR/VARCHAR it's now automatically changed to TEXT or BLOB; One will get a warning in this case.
      • One can specify the different BLOB/TEXT types with the syntax BLOB(length) and TEXT(length). MySQL will automatically change it to one of the internal BLOB/TEXT types.
      • CHAR BYTE is an alias for CHAR BINARY.
      • VARCHARACTER is an alias for VARCHAR.
      • New operators integer MOD integer and integer DIV integer.
      • SERIAL DEFAULT VALUE added as an alias for AUTO_INCREMENT.
      • TRUE and FALSE added as alias for 1 and 0, respectively.
      • Aliases are now forced in derived tables, as per SQL-99.
      • Fixed SELECT .. LIMIT 0 to return proper row count for SQL_CALC_FOUND_ROWS.
      • One can specify many temporary directories to be used in a round-robin fashion with: --tmpdir=dirname1:dirname2:dirname3.
      • Subqueries: SELECT * from t1 where t1.a=(SELECT t2.b FROM t2).
      • Derived tables: 
        SELECT a.col1, b.col2
       FROM (SELECT MAX(col1) AS col1 FROM root_table) a,
       other_table b
       WHERE a.col1=b.col1;
      • Character sets to be defined per column, table and database.
      • Unicode (UTF8) support.
      • BTREE index on HEAP tables.
      • Faster embedded server (new internal communication protocol).
      • One can add a comment per column in CREATE TABLE.
      • SHOW FULL COLUMNS FROM table_name shows column comments.
      • ALTER DATABASE.
      • Support for GIS (Geometrical data).
      • SHOW [COUNT(*)] WARNINGS shows warnings from the last command.
      • One can specify a column type for a colum in CREATE TABLE ... SELECT by defining the column in the CREATE part. 
        CREATE TABLE foo (a tinyint not null) SELECT b+1 AS 'a' FROM bar;
      • expr SOUNDS LIKE expr same as SOUNDEX(expr)=SOUNDEX(expr).
      • VARIANCE(expr) returns the variance of expr
      • One can create a table from the existing table using CREATE [TEMPORARY] TABLE [IF NOT EXISTS] table (LIKE table). The table can be either normal or temporary.
      • New options --reconnect and disable-reconnect for the mysql client, to reconnect automatically or not if the connection is lost.

      D.3 Changes in release 4.0.x (Gamma)

      Version 4.0 of the MySQL server includes many enhancements and new features:

      For a full list of changes, please refer to the changelog sections for each individual 4.0.x release.

      D.3.1 Changes in release 4.0.12 (not released yet)

      Functionality added or changed:

      • `mysqld' no longer reads options from world-writeable config files.
      • Integer values between 9223372036854775807 and 9999999999999999999 are now regarded as unsigned longlongs, not as floats. This makes these values work similar to values between 10000000000000000000 and 18446744073709551615.
      • SHOW PROCESSLIST will now include the client TCP port after the hostname to make it easier to know from which client the request originated.

      Bugs fixed:

      • Fixed `mysqld' crash on extremely small values of sort_buffer variable.
      • INSERT INTO u SELECT ... FROM t was written too late to the binary log if t was very frequently updated during the execution of this query. This could cause a problem with mysqlbinlog or replication. The master must be upgraded, not the slave. (bug #136).
      • Fixed checking of random part of WHERE clause (bug #142).
      • Fixed a bug with multi-table updates with InnoDB tables. This bug occured as, in many cases, InnoDB tables can not be updated "on the fly", but offsets to the records have to be stored in a temporary table.
      • Added missing file `mysql_secure_installation' to the server RPM subpackage (bug #141).
      • Fixed MySQL (and `myisamchk') crash on artificially corrupted .MYI files.
      • Don't allow BACKUP TABLE to overwrite existing files.
      • Fixed a bug with multi-table UPDATEs when user had all privileges on the database where tables are located and there were any entries in tables_priv table, i.e. grant_option was true.
      • Fixed a bug that allowed a user with table or column grants on some table, TRUNCATE any table in the same database.
      • Fixed deadlock when doing LOCK TABLE followed by DROP TABLE in the same thread. In this case one could still kill the thread with KILL.
      • LOAD DATA LOCAL INFILE was not properly written to the binary log (hence not properly replicated). (bug #82).
      • RAND() entries were not read correctly by mysqlbinlog from the binary log which caused problems when restoring a table that was inserted with RAND(). INSERT INTO t1 VALUES(RAND()). In replication this worked ok.
      • SET SQL_LOG_BIN=0 was ignored for INSERT DELAYED queries. (bug #104).
      • SHOW SLAVE STATUS reported too old positions (columns Relay_Master_Log_File and Exec_master_log_pos) for the last executed statement from the master, if this statement was the COMMIT of a transaction. The master must be upgraded for that, not the slave. (bug #52).
      • LOAD DATA INFILE was not replicated by the slave if replicate_*_table was set on the slave. (bug #86).
      • After RESET SLAVE, the coordinates displayed by SHOW SLAVE STATUS looked un-reset (though they were, but only internally). (bug #70).
      • Fixed query cache invalidation on LOAD DATA.
      • Fixed memory leak on ANALYZE procedure with error.
      • Fixed a bug in handling CHAR(0) columns that could cause wrong results from the query.
      • Fixed rare bug with wrong initialization of AUTO_INCREMENT column, as a secondary column in a multi-column key ( 「3.5.9 Using AUTO_INCREMENT」節参照), when data was inserted with INSERT ... SELECT or LOAD DATA into an empty table.
      • On windows, STOP SLAVE didn't stop the slave until the slave got one new command from the master (this bug has been fixed for MySQL 4.0.11 by releasing updated 4.0.11a windows packages, which include this individual fix on top of the 4.0.11 sources). (bug #69).
      • Fixed a crash when no database was selected and LOAD DATA command was issued with full table name specified, including database prefix.
      • Fixed a crash when shutting down replication on some platforms (e.g. Mac OS X).
      • Fixed a portability bug with pthread_attr_getstacksize on HP-UX 10.20 (Patch was also included in 4.0.11a sources).
      • Fixed the bigint test to not fail on some platforms (e.g. HP-UX and Tru64) due to different return values of the atof() function.
      • Fixed the rpl_rotate_logs test to not fail on certain platforms (e.g. Mac OS X) due to a too long file name (changed slave-master-info.opt to .slave-mi).

      D.3.2 Changes in release 4.0.11 (20 Feb 2003)

      Functionality added or changed:

      • NULL is now sorted LAST if you use ORDER BY ... DESC (as it was before before MySQL 4.0.2). This is change was required to follow ANSI SQL 99. (The original change was because we thought that ANSI SQL 99 required NULL to be always sorted at the same position, but this was wrong).
      • Added START TRANSACTION (ANSI SQL-99 syntax) as alias for BEGIN. This is recommended to use instead of BEGIN to start a transaction.
      • Added OLD_PASSWORD() as a synonym for PASSWORD().
      • Allow keyword ALL in group functions.
      • Added support for some new INNER JOIN and JOIN syntaxes. For example, SELECT * FROM t1 INNER JOIN t2 didn't work before.

      Bugs fixed:

      • Fixed problem with multi-table-delete and InnoDB tables.
      • Fixed a problem with BLOB NOT NULL columns used with IS NULL.
      • Re-added missing pre- and post(un)install scripts to the Linux RPM packages (they were missing after the renaming of the server subpackage).
      • Fixed that table locks are not released with multi-table updates and deletes with InnoDB storage engine.
      • Fixed bug in updating BLOB columns with long strings.
      • Fixed integer-wraparound when giving big integer (>= 10 digits) to function that requires an unsigned argument, like CREATE TABLE (...) AUTO_INCREMENT=#.
      • MIN(key_column) could in some cases return NULL on a column with NULL and other values.
      • MIN(key_column) and MAX(key_column) could in some cases return wrong values when used in OUTER JOIN.
      • MIN(key_column) and MAX(key_column) could return wrong values if one of the tables was empty.
      • Fixed rare crash in compressed MyISAM tables with blobs.
      • Fixed bug in using aggregate functions as argument for INTERVAL, CASE, FIELD, CONCAT_WS, ELT and MAKE_SET functions.
      • When running with --lower-case-table-names (default on windows) and you had tables or databases with mixed case on disk, then executing SHOW TABLE STATUS followed with DROP DATABASE or DROP TABLE could fail with Errcode 13.

      D.3.3 Changes in release 4.0.10 (29 Jan 2003)

      Functionality added or changed:

      • Added option --log-error[=file_name] to mysqld_safe and mysqld. This option will force all error messages to be put in a log file if the option --console is not given. On Windows --log-error is enabled as default.
      • Changed some things from Warning: to Note: in the log files.
      • The mysqld server should now compile on Netware.
      • Added optimisation that if one does GROUP BY ... ORDER BY NULL then result is not sorted.
      • New command-line option for `mysqld' to replace/disable built-in stopword list, that is used in fulltext search. 「4.5.6.4 SHOW VARIABLES」節参照.
      • Changed default stack size from 64K to 192K; This fixes a core dump problem on RedHat 8.0 and other systems with a glibc that requires > 128K stack for gethostbyaddr() to resolve a hostname. You can fix this for earlier MySQL versions by starting mysqld with --thread-stack=192K.
      • Added mysql_waitpid to the binary distribution and the MySQL-client RPM subpackage (required for mysql-test-run).
      • Renamed the main MySQL RPM package to MySQL-server. When updating from an older version, MySQL-server.rpm will simply replace MySQL.rpm.
      • If a slave is configured with replicate_wild_do_table=db.% or replicate_wild_ignore_table=db.%, these rules will be applied to CREATE/DROP DATABASE too.
      • Added timeout value for MASTER_POS_WAIT().

      Bugs fixed:

      • Fixed initialization of the random seed for newly created threads to give a better rand() distribution from the first call.
      • Fixed a bug that caused mysqld to hang when a table was opened with the HANDLER command and then dropped without being closed.
      • Fixed bug in logging to binary log (which affects replication) a query that inserts a NULL in an auto_increment field and also uses LAST_INSERT_ID().
      • Fixed an unlikely bug that could cause a memory overrun when using ORDER BY constant_expression.
      • Fixed a table corruption in `myisamchk''s parallel repair mode.
      • Fixed bug in query cache invalidation on simple table renaming.
      • Fixed bug in mysqladmin --relative.
      • On some 64 bit systems, show status reported a strange number for Open_files and Open_streams.
      • Fixed wrong number of columns in EXPLAIN on empty table.
      • Fixed bug in LEFT JOIN that caused zero rows to be returned in the case the WHERE condition was evaluated as FALSE after reading const tables. (Unlikely condition).
      • FLUSH PRIVILEGES didn't correctly flush table/column privileges when mysql.tables_priv is empty.
      • Fixed bug in replication when using LOAD DATA INFILE one a file that updated and auto_increment field with NULL or 0. This bug only affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters). NOTE: If you have a slave that has replicated a file with generated auto_increment fields then the slave data is corrupted and you should reinitialise the affected tables from the master.
      • Fixed possible memory overrun when sending a blob > 16M to the client.
      • Fixed wrong error message when setting a NOT NULL field to an expression that returned NULL.
      • Fixed core dump bug in str LIKE "%other_str%" where str or other_str contained characters >= 128.
      • Fixed bug: When executing on master LOAD DATA and InnoDB failed with table full error the binary log was corrupted.

      D.3.4 Changes in release 4.0.9 (09 Jan 2003)

      Functionality added or changed:

      • OPTIMIZE TABLE will for MyISAM tables treat all NULL values as different when calculating cardinality. This helps in optimising joins between tables where one of the tables has a lot of NULL values in a indexed column: 
        SELECT * from t1,t2 where t1.a=t2.key_with_a_lot_of_null;
      • Added join operator FORCE INDEX (key_list). This acts likes USE INDEX (key_list) but with the addition that a table scan is assumed to be VERY expensive. One bad thing with this is that it makes FORCE a reserved word.
      • Reset internal row buffer in MyISAM after each query. This will reduce memory in the case you have a lot of big blobs in a table.

      Bugs fixed:

      • A security patch in 4.0.8 causes the mysqld server to die if the remote hostname can't be resolved. This is now fixed.
      • Fixed crash when replication big LOAD DATA INFILE statement that caused log rotation.

      D.3.5 Changes in release 4.0.8 (2003-01-07)

      Functionality added or changed:

      • Default max_packet_length for libmysqld.c is now 1024*1024*1024.
      • One can now specify max_allowed_packet in a file ready by mysql_options(MYSQL_READ_DEFAULT_FILE). for clients.
      • When sending a too big packet to the server with the not compressed protocol, the client now gets an error message instead of a lost connection.
      • We now send big queries/result rows in bigger hunks, which should give a small speed improvement.
      • Fixed some bugs with the compressed protocol for rows > 16M.
      • InnoDB tables now also supports ON UPDATE CASCADE in FOREIGN KEY constraints. See the InnoDB section in the manual for the InnoDB changelog.

      Bugs fixed:

      • Fixed bug in ALTER TABLE with BDB tables.
      • Fixed core dump bug in QUOTE() function.
      • Fixed a bug in handling communication packets bigger than 16M. Unfortunately this required a protocol change; If you upgrade the server to 4.0.8 and above and have clients that uses packets >= 255*255*255 bytes (=16581375) you must also upgrade your clients to at least 4.0.8. If you don't upgrade, the clients will hang when sending a big packet.
      • Fixed bug when sending blobs longer than 16M to client.
      • Fixed bug in GROUP BY when used on BLOB column with NULL values.
      • Fixed a bug in handling NULLs in CASE ... WHEN ...

      D.3.6 Changes in release 4.0.7 (2002-12-20)

      Functionality added or changed:

      • mysqlbug now also reports the compiler version used for building the binaries (if the compiler supports the option --version).

      Bugs fixed:

      • Fixed compilation problems on OpenUnix and HPUX 10.20.
      • Fixed some optimisation problems when compiling MySQL with -DBIG_TABLES on a 32 bit system.
      • mysql_drop_db() didn't check permissions properly so anyone could drop another users database. DROP DATABASE is checked properly.

      D.3.7 Changes in release 4.0.6 (2002-12-14: Gamma)

      Functionality added or changed:

      • Added syntax support for CHARACTER SET xxx and CHARSET=xxx table options (to be able to read table dumps from 4.1).
      • Fixed replication bug that caused the slave to loose its position in some cases when the replication log was rotated.
      • Fixed that a slave will restart from the start of a transaction if it's killed in the middle of one.
      • Moved the manual pages from `man' to `man/man1' in the binary distributions.
      • The default type returned by IFNULL(A,B) is now set to be the more 'general' of the types of A and B. (The order is STRING, REAL or INTEGER).
      • Moved the `mysql.server' startup script in the RPM packages from `/etc/rc.d/init.d/mysql' to `/etc/init.d/mysql' (which almost all current Linux distributions support for LSB compliance).
      • Added Qcache_lowmem_prunes status variable (number of queries that were deleted from cache because of low memory).
      • Fixed mysqlcheck so it can deal with table names containing dashes.
      • Bulk insert optimisation ( 「4.5.6.4 SHOW VARIABLES」節参照) is no longer used when inserting small (less than 100) number of rows.
      • Optimisation added for queries like SELECT ... FROM merge_table WHERE indexed_column=constant_expr.
      • Added functions LOCALTIME and LOCALTIMESTAMP as synonyms for NOW().
      • CEIL is now an alias for CEILING.
      • The CURRENT_USER() function can be used to get a user@host value as it was matched in the GRANT system. 「6.3.6.2 その他の関数」節参照.
      • Fixed CHECK constraints to be compatible with ANSI SQL. This made CHECK a reserved word. (Checking of CHECK constraints is still not implemented).
      • Added CAST(... as CHAR).
      • Added PostgreSQL compatible LIMIT syntax: SELECT ... LIMIT # OFFSET #
      • mysql_change_user() will now reset the connection to the state of a fresh connect (Ie, ROLLBACK any active transaction, close all temporary tables, reset all user variables etc..)

      Bugs fixed:

      • Fixed number of found rows returned in multi table updates
      • Make --lower-case-table-names default on Mac OS X as the file system is case sensitive.
      • Transactions in AUTOCOMMIT=0 mode didn't rotate binary log.
      • A fix for the bug in a SELECT with joined tables with ORDER BY and LIMIT clause when filesort had to be used. In that case LIMIT was applied to filesort of one of the tables, although it could not be. This fix solved problems with LEFT JOIN too.
      • mysql_server_init() now makes a copy of all arguments. This fixes a problem when using the embedded server in C# program.
      • Fixed buffer overrun in libmysqlclient library that allowed a malicious MySQL server to crash the client application.
      • Fixed security-related bug in mysql_change_user() handling. All users are strongly recommended to upgrade to version 4.0.6.
      • Fixed bug that prevented --chroot command-line option of mysqld from working.
      • Fixed bug in phrase operator "..." in boolean full-text search.
      • Fixed bug that caused OPTIMIZE TABLE to corrupt the table under some rare circumstances.
      • Part rewrite of multi-table-update to optimise it, make it safer and more bug free.
      • LOCK TABLES now works together with multi-table-update and multi-table-delete.
      • --replicate-do=xxx didn't work for UPDATE commands. (Bug introduced in 4.0.0)
      • Fixed shutdown problem on Mac OS X.
      • Major InnoDB bugs in REPLACE, AUTO_INCREMENT, INSERT INTO ... SELECT ... were fixed. See the InnoDB changelog in the InnoDB section of the manual.

      D.3.8 Changes in release 4.0.5 (2002-11-13)

      Functionality added or changed:

      • Port number was added to host name (if it is known) in SHOW PROCESSLIST command
      • Changed handling of last argument in WEEK() so that one can get week number according to the ISO 8601 specification. (Old code should still work).
      • Fixed that INSERT DELAYED threads doesn't hang on Waiting for INSERT when one sends a SIGHUP to mysqld.
      • Change that AND works according to SQL ANSI99 when it comes to NULL handling. In practice, this only affects queries where you do something like WHERE ... NOT (NULL AND 0).
      • mysqld will now resolve basedir to its full path (with realpath()). This enables one to use relative symlinks to the MySQL installation directory. This will however cause show variables to report different directories on systems where there is a symbolic link in the path.
      • Fixed that MySQL will not use index scan on index disabled with IGNORE INDEX or USE INDEX. to be ignored.
      • Added --use-frm option to mysqlcheck. When used with REPAIR, it gets the table structure from the .frm file, so the table can be repaired even if the .MYI header is corrupted.
      • Fixed bug in MAX() optimisation when used with JOIN and ON expressions.
      • Added support for reading of MySQL 4.1 table definition files.
      • BETWEEN behaviour changed ( 「6.3.1.2 比較演算子」節参照). Now datetime_col BETWEEN timestamp AND timestamp should work as expected.
      • One can create TEMPORARY MERGE tables now.
      • DELETE FROM myisam_table now shrinks not only the `.MYD' file but also the `.MYI' file.
      • When one uses the --open-files-limit=# option to mysqld_safe it's now passed on to mysqld.
      • Changed output from EXPLAIN from 'where used' to 'Using where' to make it more in line with other output.
      • Removed variable safe_show_database as it was not used anymore.
      • Updated source tree to be built using automake 1.5 and libtool 1.4.
      • Fixed an inadvertently changed option (--ignore-space) back to the original --ignore-spaces in mysqlclient. (Both syntaxes will work).
      • Don't require UPDATE privilege when using REPLACE.
      • Added support for DROP TEMPORARY TABLE ..., to be used to make replication safer.
      • When transactions are enabled, all commands that update temporary tables inside a BEGIN/COMMIT are now stored in the binary log on COMMIT and not stored if one does ROLLBACK. This fixes some problems with non-transactional temporary tables used inside transactions.
      • Allow braces in joins in all positions. Formerly, things like SELECT * FROM (t2 LEFT JOIN t3 USING (a)), t1 worked, but not SELECT * FROM t1, (t2 LEFT JOIN t3 USING (a)). Note that braces are simply removed, they do not change the way the join is executed.
      • InnoDB now supports also isolation levels READ UNCOMMITTED and READ COMMITTED. For a detailed InnoDB changelog, 「7.5.14 InnoDB Change History」節参照 in this manual.

      Bugs fixed:

      • Fixed bug in MAX() optimisation when used with JOIN and ON expressions.
      • Fixed that INSERT DELAY threads don't hang on Waiting for INSERT when one sends a SIGHUP to mysqld.
      • Fixed that MySQL will not use an index scan on an index that has been disabled with IGNORE INDEX or USE INDEX.
      • Corrected test for root user in mysqld_safe.
      • Fixed error message issued when storage engine cannot do CHECK or REPAIR.
      • Fixed rare core dump problem in complicated GROUP BY queries that didn't return any result.
      • Fixed mysqlshow to work properly with wildcarded database names and with database names that contain underscores.
      • Portability fixes to get MySQL to compile cleanly with Sun Forte 5.0.
      • Fixed MyISAM crash when using dynamic-row tables with huge numbers of packed fields.
      • Fixed query cache behaviour with BDB transactions.
      • Fixed possible floating point exception in MATCH relevance calculations.
      • Fixed bug in full-text search IN BOOLEAN MODE that made MATCH to return incorrect relevance value in some complex joins.
      • Fixed a bug that limited MyISAM key length to a value slightly less that 500. It is exactly 500 now.
      • Fixed that GROUP BY on columns that may have a NULL value doesn't always use disk based temporary tables.
      • The filename argument for the --des-key-file argument to mysqld is interpreted relative to the data directory if given as a relative pathname.
      • Removed a condition that temp table with index on column that can be NULL has to be MyISAM. This was okay for 3.23, but not needed in 4.*. This resulted in slowdown in many queries since 4.0.2.
      • Small code improvement in multi-table updates.
      • Fixed a newly introduced bug that caused ORDER BY ... LIMIT # to not return all rows.
      • Fixed a bug in multi-table deletes when outer join is used on an empty table, which gets first to be deleted.
      • Fixed a bug in multi-table updates when a single table is updated.
      • Fixed bug that caused REPAIR TABLE and myisamchk to corrupt FULLTEXT indexes.
      • Fixed bug with caching the mysql grant table database. Now queries in this database are not cached in the query cache.
      • Small fix in mysqld_safe for some shells.
      • Give error if a MyISAM MERGE table has more than 2 ^ 32 rows and MySQL was not compiled with -DBIG_TABLES.
      • Fixed some ORDER BY ... DESC problems with InnoDB tables.

      D.3.9 Changes in release 4.0.4 (2002-09-29)

      • Fixed bug where GRANT/REVOKE failed if hostname was given in non-matching case.
      • Don't give warning in LOAD DATA INFILE when setting a timestamp to a string value of '0'.
      • Fixed bug in myisamchk -R mode.
      • Fixed bug that caused mysqld to crash on REVOKE.
      • Fixed bug in ORDER BY when there is a constant in the SELECT statement.
      • One didn't get an error message if mysqld couldn't open the privilege tables.
      • SET PASSWORD FOR ... closed the connection in case of errors (bug from 4.0.3).
      • Increased max possible max_allowed_packet in mysqld to 1GB.
      • Fixed bug when doing a multi-line INSERT on a table with an AUTO_INCREMENT key which was not in the first part of the key.
      • Changed LOAD DATA INFILE to not recreate index if the table had rows from before.
      • Fixed overrun bug when calling AES_DECRYPT() with incorrect arguments.
      • --skip-ssl can now be used to disable SSL in the MySQL clients, even if one is using other SSL options in an option file or previously on the command line.
      • Fixed bug in MATCH ... AGAINST( ... IN BOOLEAN MODE) used with ORDER BY.
      • Added LOCK TABLES and CREATE TEMPORARY TABLES privilege on the database level. One must run the mysql_fix_privilege_tables script on old installations to activate these.
      • In SHOW TABLE ... STATUS, compressed tables sometimes showed up as dynamic.
      • SELECT @@[global|session].var_name didn't report global | session in the result column name.
      • Fixed problem in replication that FLUSH LOGS in a circular replication setup created an infinite number of binary log files. Now a rotate-binary-log command in the binary log will not cause slaves to rotate logs.
      • Removed STOP EVENT from binary log when doing FLUSH LOGS.
      • Disable the use of SHOW NEW MASTER FOR SLAVE as this needs to be completely changed in 4.1.
      • Fixed a bug with constant expression (e.g. field of a one-row table, or field from a table, referenced by a UNIQUE key) appeared in ORDER BY part of SELECT DISTINCT.
      • --log-binary=a.b.c now properly strips off .b.c.
      • FLUSH LOGS removed numerical extension for all future update logs.
      • GRANT ... REQUIRE didn't store the SSL information in the mysql.user table if SSL was not enabled in the server.
      • GRANT ... REQUIRE NONE can now be used to remove SSL information.
      • AND is now optional between REQUIRE options.
      • REQUIRE option was not properly saved, which could cause strange output in SHOW GRANTS.
      • Fixed that mysqld --help reports correct values for --datadir and --bind-address.
      • Fixed that one can drop UDFs that didn't exist when mysqld was started.
      • Fixed core dump problem with SHOW VARIABLES on some 64 bit systems (like Solaris sparc).
      • Fixed a bug in my_getopt; --set-variable syntax didn't work for those options that didn't have a valid variable in my_option struct. This affected at least default-table-type option.
      • Fixed a bug from 4.0.2 that caused REPAIR TABLE and myisamchk --recover to fail on tables with duplicates in a unique key.
      • Fixed a bug from 4.0.3 in calculating the default field type for some functions. This affected queries of type CREATE TABLE table_name SELECT expression(),...
      • Fixed bug in queries of type SELECT * FROM table-list GROUP BY ... and SELECT DISTINCT * FROM ....
      • Fixed bug with the --slow-log when logging an administrator command (like FLUSH TABLES).
      • Fixed a bug that OPTIMIZE of locked and modified table, reported table corruption.
      • Fixed a bug in my_getopt in handling of special prefixes (--skip-, --enable-). --skip-external-locking didn't work and the bug may have affected other similar options.
      • Fixed bug in checking for output file name of the tee option.
      • Added some more optimisation to use index for SELECT ... FROM many_tables .. ORDER BY key limit #
      • Fixed problem in SHOW OPEN TABLES when a user didn't have access permissions to one of the opened tables.

      D.3.10 Changes in release 4.0.3 (2002-08-26: Beta)

      • Fixed problem with configure ... --localstatedir=....
      • Cleaned up mysql.server script.
      • Fixed a bug in mysqladmin shutdown when pid file was modified while mysqladmin was still waiting for the previous one to disappear. This could happen during a very quick restart and caused mysqladmin to hang until shutdown_timeout seconds had passed.
      • Don't increment warnings when setting AUTO_INCREMENT columns to NULL in LOAD DATA INFILE.
      • Fixed all boolean type variables/options to work with the old syntax, e.g. all of these work: --lower-case-table-names, --lower-case-table-names=1, -O lower-case-table-names=1, --set-variable=lower-case-table-names=1
      • Fixed shutdown problem (SIGTERM signal handling) on Solaris. (Bug from 4.0.2).
      • SHOW MASTER STATUS now returns an empty set if binary log is not enabled.
      • SHOW SLAVE STATUS now returns an empty set if slave is not initialised.
      • Don't update MyISAM index file on update if not strictly necessary.
      • Fixed bug in SELECT DISTINCT ... FROM many_tables ORDER BY not-used-column.
      • Fixed a bug with BIGINTs and quoted strings.
      • Added QUOTE() function that performs SQL quoting to produce values that can be used as data values in queries.
      • Changed variable DELAY_KEY_WRITE to an enum to allow one set DELAY_KEY_WRITE for all tables without taking down the server.
      • Changed behaviour of IF(condition,column,NULL) so that it returns the value of the column type.
      • Made safe_mysqld a symlink to mysqld_safe in binary distribution.
      • Fixed security bug when having an empty database name in the user.db table.
      • Fixed some problems with CREATE TABLE ... SELECT function().
      • mysqld now has the option --temp-pool enabled by default as this gives better performance with some operating systems.
      • Fixed hang in CHANGE MASTER TO if the slave thread died very quickly.
      • Big cleanup in replication code (less logging, better error messages, etc..)
      • If the --code-file option is specified, the server calls setrlimit() to set the maximum allowed core file size to unlimited, so core files can be generated.
      • Fixed bug in query cache after temporary table creation.
      • Added --count=N (-c) option to mysqladmin, to make the program do only N iterations. To be used with --sleep (-i). Useful in scripts.
      • Fixed bug in multi-table UPDATE: when updating a table, do_select() became confused about reading records from a cache.
      • Fixed bug in multi-table UPDATE when several fields were referenced from a single table
      • Fixed bug in truncating nonexisting table.
      • Fixed bug in REVOKE that caused user resources to be randomly set.
      • Fixed bug in GRANT for the new CREATE TEMPORARY TABLE privilege.
      • Fixed bug in multi-table DELETE when tables are re-ordered in the table initialisation method and ref_lengths are of different sizes.
      • Fixed two bugs in SELECT DISTINCT with large tables.
      • Fixed bug in query cache initialisation with very small query cache size.
      • Allow DEFAULT with INSERT statement.
      • The startup parameters myisam_max_sort_file_size and myisam_max_extra_sort_file_size are now given in bytes, not megabytes.
      • External system locking of MyISAM/ISAM files is now turned off by default. One can turn this on with --external-locking. (For most users this is never needed).
      • Fixed core dump bug with INSERT ... SET db_name.table_name.colname=''.
      • Fixed client hangup bug when using some SQL commands with wrong syntax.
      • Fixed a timing bug in DROP DATABASE
      • New SET [GLOBAL | SESSION] syntax to change thread-specific and global server variables at runtime.
      • Added variable slave_compressed_protocol.
      • Renamed variable query_cache_startup_type to query_cache_type, myisam_bulk_insert_tree_size to bulk_insert_buffer_size, record_buffer to read_buffer_size and record_rnd_buffer to record_rnd_buffer_size.
      • Renamed some SQL variables, but old names will still work until 5.0. 「2.5.2 バージョン 3.23 から バージョン 4.0 へのアップグレード」節参照.
      • Renamed --skip-locking to --skip-external-locking.
      • Removed unused variable query_buffer_size.
      • Fixed a bug that made the pager option in the mysql client non-functional.
      • Added full AUTO_INCREMENT support to MERGE tables.
      • Extended LOG() function to accept an optional arbitrary base parameter. 「6.3.3.2 数学関数」節参照.
      • Added LOG2() function (useful for finding out how many bits a number would require for storage).
      • Added LN() natural logarithm function for compatibility with other databases. It is synonymous with LOG(X).

      D.3.11 Changes in release 4.0.2 (2002-07-01)

      • Cleaned up NULL handling for default values in DESCRIBE table_name.
      • Fixed truncate() to round up negative values to the nearest integer.
      • Changed --chroot=path option to execute chroot() immediately after all options have been parsed.
      • Don't allow database names that contain `\'.
      • lower_case_table_names now also affects database names.
      • Added XOR operator (logical and bitwise XOR) with ^ as a synonym for bitwise XOR.
      • Added function IS_FREE_LOCK("lock_name"). Based on code contributed by Hartmut Holzgraefe hartmut@six.de.
      • Removed mysql_ssl_clear() from C API, as it was not needed.
      • DECIMAL and NUMERIC types can now read exponential numbers.
      • Added SHA1() function to calculate 160 bit hash value as described in RFC 3174 (Secure Hash Algorithm). This function can be considered a cryptographically more secure equivalent of MD5(). 「6.3.6.2 その他の関数」節参照.
      • Added AES_ENCRYPT() and AES_DECRYPT() functions to perform encryption according to AES standard (Rijndael). 「6.3.6.2 その他の関数」節参照.
      • Added --single-transaction option to mysqldump, allowing a consistent dump of InnoDB tables. 「4.8.5 mysqldump, データベースとテーブルから、構造とデータをダンプ」節参照.
      • Fixed bug in innodb_log_group_home_dir in SHOW VARIABLES.
      • Fixed a bug in optimiser with merge tables when non-unique values are used in summing up (causing crashes).
      • Fixed a bug in optimiser when a range specified makes index grouping impossible (causing crashes).
      • Fixed a rare bug when FULLTEXT index is present and no tables are used.
      • Added privileges CREATE TEMPORARY TABLES, EXECUTE, LOCK TABLES, REPLICATION CLIENT, REPLICATION SLAVE, SHOW DATABASES and SUPER. To use these, you must have run the mysql_fix_privilege_tables script after upgrading.
      • Fixed query cache align data bug.
      • Fixed mutex bug in replication when reading from master fails.
      • Added missing mutex in TRUNCATE TABLE; This fixes some core dump/hangup problems when using TRUNCATE TABLE.
      • Fixed bug in multi-table DELETE when optimiser uses only indices.
      • Fixed that ALTER TABLE table_name RENAME new_table_name is as fast as RENAME TABLE.
      • Fixed bug in GROUP BY with two or more fields, where at least one field can contain NULL values.
      • Use Turbo Boyer-Moore algorithm to speed up LIKE "%keyword%" searches.
      • Fixed bug in DROP DATABASE with symlink.
      • Fixed crash in REPAIR ... USE_FRM.
      • Fixed bug in EXPLAIN with LIMIT offset != 0.
      • Fixed bug in phrase operator "..." in boolean full-text search.
      • Fixed bug that caused duplicated rows when using truncation operator * in boolean full-text search.
      • Fixed bug in truncation operator of boolean full-text search (wrong results when there are only +word*s in the query).
      • Fixed bug in boolean full-text search that caused a crash when an identical MATCH expression that did not use an index appeared twice.
      • Query cache is now automatically disabled in mysqldump.
      • Fixed problem on Windows 98 that made sending of results very slow.
      • Boolean full-text search weighting scheme changed to something more reasonable.
      • Fixed bug in boolean full-text search that caused MySQL to ignore queries of ft_min_word_len characters.
      • Boolean full-text search now supports ``phrase searches''.
      • New configure option --without-query-cache.
      • Memory allocation strategy for ``root memory'' changed. Block size now grows with number of allocated blocks.
      • INET_NTOA() now returns NULL if you give it an argument that is too large (greater than the value corresponding to 255.255.255.255).
      • Fix SQL_CALC_FOUND_ROWS to work with UNIONs. It will work only if the first SELECT has this option and if there is global LIMIT for the entire statement. For the moment, this requires using parentheses for individual SELECT queries within the statement.
      • Fixed bug in SQL_CALC_FOUND_ROWS and LIMIT.
      • Don't give an error for CREATE TABLE ...(... VARCHAR(0)).
      • Fixed SIGINT and SIGQUIT problems in `mysql.cc' on Linux with some glibc versions.
      • Fixed bug in `convert.cc', which is caused by having an incorrect net_store_length() linked in the CONVERT::store() method.
      • DOUBLE and FLOAT columns now honor the UNSIGNED flag on storage.
      • InnoDB now retains foreign key constraints through ALTER TABLE and CREATE/DROP INDEX.
      • InnoDB now allows foreign key constraints to be added through the ALTER TABLE syntax.
      • InnoDB tables can now be set to automatically grow in size (autoextend).
      • Added --ignore-lines=n option to mysqlimport. This has the same effect as the IGNORE n LINES clause for LOAD DATA.
      • Fixed bug in UNION with last offset being transposed to total result set.
      • REPAIR ... USE_FRM added.
      • Fixed that DEFAULT_SELECT_LIMIT is always imposed on UNION result set.
      • Fixed that some SELECT options can appear only in the first SELECT.
      • Fixed bug with LIMIT with UNION, where last select is in the braces.
      • Fixed that full-text works fine with UNION operations.
      • Fixed bug with indexless boolean full-text search.
      • Fixed bug that sometimes appeared when full-text search was used with ``const'' tables.
      • Fixed incorrect error value when doing a SELECT with an empty HEAP table.
      • Use ORDER BY column DESC now sorts NULL values first. (In other words, NULL values sort first in all cases, whether or not DESC is specified.). This is changed back in 4.0.10.
      • Fixed bug in WHERE key_name='constant' ORDER BY key_name DESC.
      • Fixed bug in SELECT DISTINCT ... ORDER BY DESC optimisation.
      • Fixed bug in ... HAVING 'GROUP_FUNCTION'(xxx) IS [NOT] NULL.
      • Fixed bug in truncation operator for boolean full-text search.
      • Allow value of --user=# option for mysqld to be specified as a numeric user ID.
      • Fixed a bug where SQL_CALC_ROWS returned an incorrect value when used with one table and ORDER BY and with InnoDB tables.
      • Fixed that SELECT 0 LIMIT 0 doesn't hang thread.
      • Fixed some problems with USE/IGNORE INDEX when using many keys with the same start column.
      • Don't use table scan with BerkeleyDB and InnoDB tables when we can use an index that covers the whole row.
      • Optimised InnoDB sort-buffer handling to take less memory.
      • Fixed bug in multi-table DELETE and InnoDB tables.
      • Fixed problem with TRUNCATE and InnoDB tables that produced the error Can't execute the given command because you have active locked tables or an active transaction.
      • Added NO_UNSIGNED_SUBTRACTION to the set of flags that may be specified with the --sql-mode option for mysqld. It disables unsigned arithmetic rules when it comes to subtraction. (This will make MySQL 4.0 behave more closely to 3.23 with UNSIGNED columns).
      • The result returned for all bit functions (|, <<, ...) is now of type unsigned integer.
      • Added detection of nan values in MyISAM to make it possible to repair tables with nan in float or double columns.
      • Fixed new bug in myisamchk where it didn't correctly update number of ``parts'' in the MyISAM index file.
      • Changed to use autoconf 2.52 (from autoconf 2.13).
      • Fixed optimisation problem where the MySQL Server was in ``preparing'' state for a long time when selecting from an empty table which had contained a lot of rows.
      • Fixed bug in complicated join with const tables. This fix also improves performance a bit when referring to another table from a const table.
      • First pre-version of multi-table UPDATE statement.
      • Fixed bug in multi-table DELETE.
      • Fixed bug in SELECT CONCAT(argument_list) ... GROUP BY 1.
      • INSERT ... SELECT did a full rollback in case of an error. Fixed so that we only roll back the last statement in the current transaction.
      • Fixed bug with empty expression for boolean full-text search.
      • Fixed core dump bug in updating full-text key from/to NULL.
      • ODBC compatibility: Added BIT_LENGTH() function.
      • Fixed core dump bug in GROUP BY BINARY column.
      • Added support for NULL keys in HEAP tables.
      • Use index for ORDER BY in queries of type: SELECT * FROM t WHERE key_part1=1 ORDER BY key_part1 DESC,key_part2 DESC
      • Fixed bug in FLUSH QUERY CACHE.
      • Added CAST() and CONVERT() functions. The CAST and CONVERT functions are nearly identical and mainly useful when you want to create a column with a specific type in a CREATE ... SELECT statement. For more information, read 「6.3.5 Cast Functions」節.
      • CREATE ... SELECT on DATE and TIME functions now create columns of the expected type.
      • Changed order in which keys are created in tables.
      • Added new columns Null and Index_type to SHOW INDEX output.
      • Added --no-beep and --prompt options to mysql command-line client.
      • New feature: management of user resources. 
        GRANT ... WITH MAX_QUERIES_PER_HOUR N1
               MAX_UPDATES_PER_HOUR N2
               MAX_CONNECTIONS_PER_HOUR N3;
        「4.3.6 Limiting user resources」節参照.
      • Added mysql_secure_installation to the `scripts/' directory.

      D.3.12 Changes in release 4.0.1 (2001-12-23)

      • Fixed bug when HANDLER was used with some unsupported table type.
      • mysqldump now puts ALTER TABLE tbl_name DISABLE KEYS and ALTER TABLE tbl_name ENABLE KEYS in the sql dump.
      • Added mysql_fix_extensions script.
      • Fixed stack overrun problem with LOAD DATA FROM MASTER on OSF/1.
      • Fixed shutdown problem on HP-UX.
      • Added DES_ENCRYPT() and DES_DECRYPT() functions.
      • Added FLUSH DES_KEY_FILE statement.
      • Added --des-key-file option to mysqld.
      • HEX(string) now returns the characters in string converted to hexadecimal.
      • Fixed problem with GRANT when using lower_case_table_names=1.
      • Changed SELECT ... IN SHARE MODE to SELECT ... LOCK IN SHARE MODE (as in MySQL 3.23).
      • A new query cache to cache results from identical SELECT queries.
      • Fixed core dump bug on 64-bit machines when it got an incorrect communication packet.
      • MATCH ... AGAINST(... IN BOOLEAN MODE) can now work without FULLTEXT index.
      • Fixed slave to replicate from 3.23 master.
      • Miscellaneous replication fixes/cleanup.
      • Got shutdown to work on Mac OS X.
      • Added `myisam/ft_dump' utility for low-level inspection of FULLTEXT indexes.
      • Fixed bug in DELETE ... WHERE ... MATCH ....
      • Added support for MATCH ... AGAINST(... IN BOOLEAN MODE). Note: you must rebuild your tables with ALTER TABLE tablename TYPE=MyISAM to be able to use boolean full-text search.
      • LOCATE() and INSTR() are now case-sensitive if either argument is a binary string.
      • Changed RAND() initialisation so that RAND(N) and RAND(N+1) are more distinct.
      • Fixed core dump bug in UPDATE ... ORDER BY.
      • Changed INSERT INTO ... SELECT to stop on errors by default.
      • Ignore DATA DIRECTORY and INDEX DIRECTORY directives on Windows.
      • Added boolean full-text search code. It should be considered early alpha.
      • Extended MODIFY and CHANGE in ALTER TABLE to accept the FIRST and AFTER keywords.
      • Indexes are now used with ORDER BY on a whole InnoDB table.

      D.3.13 Changes in release 4.0.0 (2001-10-16: Alpha)

      • Added --xml option to mysql for producing XML output.
      • Added full-text variables ft_min_word_len, ft_max_word_len, and ft_max_word_len_for_sort.
      • Added documentation for libmysqld, the embedded MySQL server library. Also added example programs (a mysql client and mysqltest test program) which use libmysqld.
      • Removed all Gemini hooks from MySQL server.
      • Removed my_thread_init() and my_thread_end() from `mysql_com.h', and added mysql_thread_init() and mysql_thread_end() to `mysql.h'.
      • Support for communication packets > 16M. In 4.0.1 we will extend MyISAM to be able to handle these.
      • Secure connections (with SSL).
      • Unsigned BIGINT constants now work. MIN() and MAX() now handle signed and unsigned BIGINT numbers correctly.
      • New character set latin1_de which provides correct German sorting.
      • STRCMP() now uses the current character set when doing comparisons, which means that the default comparison behaviour now is case-insensitive.
      • TRUNCATE TABLE and DELETE FROM tbl_name are now separate functions. One bonus is that DELETE FROM tbl_name now returns the number of deleted rows, rather than zero.
      • DROP DATABASE now executes a DROP TABLE on all tables in the database, which fixes a problem with InnoDB tables.
      • Added support for UNION.
      • Added support for multi-table DELETE operations.
      • A new HANDLER interface to MyISAM tables.
      • Added support for INSERT on MERGE tables. Patch from Benjamin Pflugmann.
      • Changed WEEK(#,0) to match the calendar in the USA.
      • COUNT(DISTINCT) is about 30% faster.
      • Speed up all internal list handling.
      • Speed up IS NULL, ISNULL() and some other internal primitives.
      • Full-text index creation now is much faster.
      • Tree-like cache to speed up bulk inserts and myisam_bulk_insert_tree_size variable.
      • Searching on packed (CHAR/VARCHAR) keys is now much faster.
      • Optimised queries of type: SELECT DISTINCT * from tbl_name ORDER by key_part1 LIMIT #.
      • SHOW CREATE TABLE now shows all table attributes.
      • ORDER BY ... DESC can now use keys.
      • LOAD DATA FROM MASTER ``automatically'' sets up a slave.
      • Renamed safe_mysqld to mysqld_safe to make this name more in line with other MySQL scripts/commands.
      • Added support for symbolic links to MyISAM tables. Symlink handling is now enabled by default for Windows.
      • Added SQL_CALC_FOUND_ROWS and FOUND_ROWS(). This makes it possible to know how many rows a query would have returned without a LIMIT clause.
      • Changed output format of SHOW OPEN TABLES.
      • Allow SELECT expression LIMIT ....
      • Added IDENTITY as a synonym for AUTO_INCREMENT (like Sybase).
      • Added ORDER BY syntax to UPDATE and DELETE.
      • SHOW INDEXES is now a synonym for SHOW INDEX.
      • Added ALTER TABLE tbl_name DISABLE KEYS and ALTER TABLE tbl_name ENABLE KEYS commands.
      • Allow use of IN as a synonym for FROM in SHOW commands.
      • Implemented ``repair by sort'' for FULLTEXT indexes. REPAIR TABLE, ALTER TABLE, and OPTIMIZE TABLE for tables with FULLTEXT indexes are now up to 100 times faster.
      • Allow ANSI SQL syntax X'hexadecimal-number'.
      • Cleaned up global lock handling for FLUSH TABLES WITH READ LOCK.
      • Fixed problem with DATETIME = constant in WHERE optimisation.
      • Added --master-data and --no-autocommit options to mysqldump. (Thanks to Brian Aker for this.)
      • Added script mysql_explain_log.sh to distribution. (Thanks to mobile.de).

      D.4 Changes in release 3.23.x (Stable)

      The 3.23 release has several major features that are not present in previous versions. We have added three new table types:

      MyISAM
      A new ISAM library which is tuned for SQL and supports large files.
      InnoDB
      A transaction-safe storage engine that supports row level locking, and many Oracle-like features.
      BerkeleyDB or BDB
      Uses the Berkeley DB library from Sleepycat Software to implement transaction-safe tables.

      Note that only MyISAM is available in the standard binary distribution.

      The 3.23 release also includes support for database replication between a master and many slaves, full-text indexing, and much more.

      All new features are being developed in the 4.x version. Only bug fixes and minor enhancements to existing features will be added to 3.23.

      The replication code and BerkeleyDB code is still not as tested and as the rest of the code, so we will probably need to do a couple of future releases of 3.23 with small fixes for this part of the code. As long as you don't use these features, you should be quite safe with MySQL 3.23!

      Note that the above doesn't mean that replication or Berkeley DB don't work. We have done a lot of testing of all code, including replication and BDB without finding any problems. It only means that not as many users use this code as the rest of the code and because of this we are not yet 100% confident in this code.

      D.4.1 Changes in release 3.23.57 (not released yet)

      • Give an error for empty table and column names.
      • Changed PROCEDURE ANALYSE() to report DATE instead of NEWDATE.
      • Changed PROCEDURE ANALYSE(#) to restrict number of values in enum to # also for string values.

      D.4.2 Changes in release 3.23.56 (13 Mar 2003)

      • Fixed `mysqld' crash on extremely small values of sort_buffer variable.
      • Fixed a bug in privilege system for GRANT UPDATE on column level.
      • Fixed a rare bug when using a date in HAVING with GROUP BY.
      • Fixed checking of random part of WHERE clause (Bug #142).
      • Fixed MySQL (and `myisamchk') crash on artificially corrupted .MYI files.
      • Security enhancement: `mysqld' no longer reads options from world-writeable config files.
      • Security enhancement: `mysqld' and `safe_mysqld' now only use the first --user option specified on the command line. (Normally this comes from `/etc/my.cnf')
      • Security enhancement: Don't allow BACKUP TABLE to overwrite existing files.
      • Fixed unlikely deadlock bug when one thread did a LOCK TABLE and another thread did a DROP TABLE. In this case one could do a KILL on one of the threads to resolve the deadlock.
      • LOAD DATA INFILE was not replicated by slave if replicate_*_table was set on the slave.
      • Fixed a bug in handling CHAR(0) columns that could cause wrong results from the query.
      • Fixed a bug in SHOW VARIABLES on 64-bit platforms. The bug was caused by wrong declaration of variable server_id.
      • The Comment column in SHOW TABLE STATUS now reports that it can contain NULL values (which is the case for a crashed `.frm' file).
      • Fixed the rpl_rotate_logs test to not fail on certain platforms (e.g. Mac OS X) due to a too long file name (changed slave-master-info.opt to .slave-mi).
      • Fixed a problem with BLOB NOT NULL columns used with IS NULL.
      • Fixed bug in MAX() optimization in MERGE tables.
      • Better RAND() initialization for new connections.
      • Fixed bug with connect timeout. This bug was manifested on OS's with poll() system call, which resulted in timeout the value specified as it was executed in both select() and poll().
      • Fixed bug in SELECT * FROM table WHERE datetime1 IS NULL OR datetime2 IS NULL.
      • Fixed bug in using aggregate functions as argument for INTERVAL, CASE, FIELD, CONCAT_WS, ELT and MAKE_SET functions.
      • When running with --lower-case-table-names (default on windows) and you had tables or databases with mixed case on disk, then executing SHOW TABLE STATUS followed with DROP DATABASE or DROP TABLE could fail with Errcode 13.
      • Fixed bug in logging to binary log (which affects replication) a query that inserts a NULL in an auto_increment field and also uses LAST_INSERT_ID().
      • Fixed bug in mysqladmin --relative.
      • On some 64 bit systems, show status reported a strange number for Open_files and Open_streams.

      D.4.3 Changes in release 3.23.55 (23 Jan 2003)

      • Fixed double free'd pointer bug in mysql_change_user() handling, that enabled a specially hacked version of MySQL client to crash mysqld. Note, that one needs to login to the server by using a valid user account to be able to exploit this bug.
      • Fixed bug with the --slow-log when logging an administrator command (like FLUSH TABLES).
      • Fixed bug in GROUP BY when used on BLOB column with NULL values.
      • Fixed a bug in handling NULLs in CASE ... WHEN ....
      • Bugfix for --chroot ( 「D.4.4 Changes in release 3.23.54 (2002-12-05)」節参照) is reverted. Unfortunately, there is no way to make it to work, without introducing backward-incompatible changes in `my.cnf'. Those who need --chroot functionality, should upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break backward-compatibility).
      • Make --lower-case-table-names default on Mac OS X as the file system is case insensitive.
      • Fixed a bug in `scripts/mysqld_safe.sh' in NOHUP_NICENESS testing.
      • Transactions in AUTOCOMMIT=0 mode didn't rotate binary log.
      • Fixed a bug in scripts/make_binary_distribution that resulted in a remaining @HOSTNAME@ variable instead of replacing it with the correct path to the hostname binary.
      • Fixed a very unlikely bug that could cause SHOW PROCESSLIST to core dump in pthread_mutex_unlock() if a new thread was connecting.
      • Forbid SLAVE STOP if the thread executing the query has locked tables. This removes a possible deadlock situation.

      D.4.4 Changes in release 3.23.54 (2002-12-05)

      • Fixed a bug, that allowed to crash mysqld with a specially crafted packet.
      • Fixed a rare crash (double free'd pointer) when altering a temporary table.
      • Fixed buffer overrun in libmysqlclient library that allowed malicious MySQL server to crash the client application.
      • Fixed security-related bug in mysql_change_user() handling. All users are strongly recommended to upgrade to the version 3.23.54.
      • Fixed bug that prevented --chroot command-line option of mysqld from working.
      • Fixed bug that made OPTIMIZE TABLE to corrupt the table under some rare circumstances.
      • Fixed mysqlcheck so it can deal with table names containing dashes.
      • Fixed shutdown problem on Mac OS X.
      • Fixed bug with comparing an indexed NULL field with <=> NULL.
      • Fixed bug that caused IGNORE INDEX and USE INDEX sometimes to be ignored.
      • Fixed rare core dump problem in complicated GROUP BY queries that didn't return any result.
      • Fixed a bug where MATCH ... AGAINST () >=0 was treated as if it was >.
      • Fixed core dump in SHOW PROCESSLIST when running with an active slave (unlikely timing bug).
      • Allow one to start multiple MySQL servers on windows (code backported from 4.0.2).
      • One can create TEMPORARY MERGE tables now.
      • Fixed that --core-file works on Linux (at least on kernel 2.4.18).
      • Fixed a problem with BDB and ALTER TABLE.
      • Fixed reference to freed memory when doing complicated GROUP BY ... ORDER BY queries. Symptom was that mysqld died in function send_fields.
      • Allocate heap rows in smaller blocks to get better memory usage.
      • Fixed memory allocation bug when storing BLOB values in internal temporary tables used for some (unlikely) GROUP BY queries.
      • Fixed a bug in key optimizing handling where the expression WHERE column_name = key_column_name was calculated as true for NULL values.
      • Fixed core dump bug when doing LEFT JOIN ... WHERE key_column=NULL.
      • Fixed MyISAM crash when using dynamic-row tables with huge numbers of packed fields.
      • Updated source tree to be built using automake 1.5 and libtool 1.4.

      D.4.5 Changes in release 3.23.53 (2002-10-09)

      • Fixed crash when SHOW INNODB STATUS was used and skip-innodb was defined.
      • Fixed possible memory corruption bug in binary log file handling when slave rotated the logs (only affected 3.23, not 4.0).
      • Fixed problem in LOCK TABLES on windows when one connects to a database that contains upper case letters.
      • Fixed that --skip-show-databases doesn't reset the --port option.
      • Small fix in safe_mysqld for some shells.
      • Fixed that FLUSH STATUS doesn't reset Delayed_insert_threads.
      • Fixed core dump bug when using the BINARY cast on a NULL value.
      • Fixed race condition when someone did a GRANT at the same time a new user logged in or did a USE DATABASE.
      • Fixed bug in ALTER TABLE and RENAME TABLE when running with -O lower_case_table_names=1 (typically on windows) when giving the table name in uppercase.
      • Fixed that -O lower_case_table_names=1 also converts database names to lower case.
      • Fixed unlikely core dump with SELECT ... ORDER BY ... LIMIT.
      • Changed AND/OR to report that they can return NULL. This fixes a bug in GROUP BY on AND/OR expressions that return NULL.
      • Fixed a bug that OPTIMIZE of locked and modified MyISAM table, reported table corruption.
      • Fixed a BDB-related ALTER TABLE bug with dropping a column and shutting down immediately thereafter.
      • Fixed problem with configure ... --localstatedir=....
      • Fixed problem with UNSIGNED BIGINT on AIX (again).
      • Fixed bug in pthread_mutex_trylock() on HPUX 11.0.
      • Multithreaded stress tests for InnoDB.

      D.4.6 Changes in release 3.23.52 (2002-08-14)

      • Wrap BEGIN/COMMIT around transaction in the binary log. This makes replication honour transactions.
      • Fixed security bug when having an empty database name in the user.db table.
      • Changed initialisation of RND() to make it less predicatable.
      • Fixed problem with GROUP BY on result with expression that created a BLOB field.
      • Fixed problem with GROUP BY on columns that have NULL values. To solve this we now create an MyISAM temporary table when doing a GROUP BY on a possible NULL item. From MySQL 4.0.5 we can use in memory HEAP tables for this case.
      • Fixed problem with privilege tables when downgrading from 4.0.2 to 3.23.
      • Fixed thread bug in SLAVE START, SLAVE STOP and automatic repair of MyISAM tables that could cause table cache to be corrupted.
      • Fixed possible thread related key-cache-corruption problem with OPTIMIZE TABLE and REPAIR TABLE.
      • Added name of 'administrator command' logs.
      • Fixed bug with creating an auto-increment value on second part of a UNIQUE() key where first part could contain NULL values.
      • Don't write slave-timeout reconnects to the error log.
      • Fixed bug with slave net read timeouting
      • Fixed a core-dump bug with MERGE tables and MAX() function.
      • Fixed bug in ALTER TABLE with BDB tables.
      • Fixed bug when logging LOAD DATA INFILE to binary log with no active database.
      • Fixed a bug in range optimiser (causing crashes).
      • Fixed possible problem in replication when doing DROP DATABASE on a database with InnoDB tables.
      • Fixed that mysql_info() returns 0 for 'Duplicates' when using INSERT DELAYED IGNORE.
      • Added -DHAVE_BROKEN_REALPATH to the Mac OS X (darwin) compile options in `configure.in' to fix a failure under high load.

      D.4.7 Changes in release 3.23.51 (2002-05-31)

      • Fix bug with closing tags missing slash for mysqldump XML output.
      • Remove end space from ENUM values. (This fixed a problem with SHOW CREATE TABLE.)
      • Fixed bug in CONCAT_WS() that cut the result.
      • Changed name of server variables Com_show_master_stat to Com_show_master_status and Com_show_slave_stat to Com_show_slave_status.
      • Changed handling of gethostbyname() to make the client library thread-safe even if gethostbyname_r doesn't exist.
      • Fixed core-dump problem when giving a wrong password string to GRANT.
      • Fixed bug in DROP DATABASE with symlinked directory.
      • Fixed optimisation problem with DATETIME and value outside DATETIME range.
      • Removed Sleepycat's BDB doc files from the source tree, as they're not needed (MySQL covers BDB in its own documentation).
      • Fixed MIT-pthreads to compile with glibc 2.2 (needed for make dist).
      • Fixed the FLOAT(X+1,X) is not converted to FLOAT(X+2,X). (This also affected DECIMAL, DOUBLE and REAL types)
      • Fixed the result from IF() is case in-sensitive if the second and third arguments are case sensitive.
      • Fixed core dump problem on OSF/1 in gethostbyname_r.
      • Fixed that underflowed decimal fields are not zero filled.
      • If we get an overflow when inserting '+11111' for DECIMAL(5,0) UNSIGNED columns, we will just drop the sign.
      • Fixed optimisation bug with ISNULL(expression_which_cannot_be_null) and ISNULL(constant_expression).
      • Fixed host lookup bug in the glibc library that we used with the 3.23.50 Linux-x86 binaries.

      D.4.8 Changes in release 3.23.50 (2002-04-21)

      • Fixed buffer overflow problem if someone specified a too long datadir parameter to mysqld
      • Add missing <row> tags for mysqldump XML output.
      • Fixed problem with crash-me and gcc 3.0.4.
      • Fixed that @@unknown_variable doesn't hang server.
      • Added @@VERSION as a synonym for VERSION().
      • SHOW VARIABLES LIKE 'xxx' is now case-insensitive.
      • Fixed timeout for GET_LOCK() on HP-UX with DCE threads.
      • Fixed memory allocation bug in the glibc library used to build Linux binaries, which caused mysqld to die in 'free()'.
      • Fixed SIGINT and SIGQUIT problems in mysql.
      • Fixed bug in character table converts when used with big ( > 64K) strings.
      • InnoDB now retains foreign key constraints through ALTER TABLE and CREATE/DROP INDEX.
      • InnoDB now allows foreign key constraints to be added through the ALTER TABLE syntax.
      • InnoDB tables can now be set to automatically grow in size (autoextend).
      • Our Linux RPMS and binaries are now compiled with gcc 3.0.4, which should make them a bit faster.
      • Fixed some buffer overflow problems when reading startup parameters.
      • Because of problems on shutdown we have now disabled named pipes on windows by default. One can enable named pipes by starting mysqld with --enable-named-pipe.
      • Fixed bug when using WHERE key_column = 'J' or key_column='j'.
      • Fixed core-dump bug when using --log-bin with LOAD DATA INFILE without an active database.
      • Fixed bug in RENAME TABLE when used with lower_case_table_names=1 (default on Windows).
      • Fixed unlikely core-dump bug when using DROP TABLE on a table that was in use by a thread that also used queries on only temporary tables.
      • Fixed problem with SHOW CREATE TABLE and PRIMARY KEY when using 32 indexes.
      • Fixed that one can use SET PASSWORD for the anonymous user.
      • Fixed core dump bug when reading client groups from option files using mysql_options().
      • Memory leak (16 bytes per every corrupted table) closed.
      • Fixed binary builds to use --enable-local-infile.
      • Update source to work with new version of bison.
      • Updated shell scripts to now agree with new POSIX standard.
      • Fixed bug where DATE_FORMAT() returned empty string when used with GROUP BY.

      D.4.9 Changes in release 3.23.49 (2002-02-16)

      • Don't give warning for a statement that is only a comment; this is needed for mysqldump --disable-keys to work.
      • Fixed unlikely caching bug when doing a join without keys. In this case the last used field for a table always returned NULL.
      • Added options to make LOAD DATA LOCAL INFILE more secure.
      • MySQL binary release 3.23.48 for Linux contained a new glibc library, which has serious problems under high load and RedHat 7.2. The 3.23.49 binary release doesn't have this problem.
      • Fixed shutdown problem on NT.

      D.4.10 Changes in release 3.23.48 (2002-02-07)

      • Added --xml option to mysqldump for producing XML output.
      • Changed to use autoconf 2.52 (from autoconf 2.13)
      • Fixed bug in complicated join with const tables.
      • Added internal safety checks for InnoDB.
      • Some InnoDB variables were always shown in SHOW VARIABLES as OFF on high-byte-first systems (like SPARC).
      • Fixed problem with one thread using an InnoDB table and another thread doing an ALTER TABLE on the same table. Before that, mysqld could crash with an assertion failure in `row0row.c', line 474.
      • Tuned the InnoDB SQL optimiser to favor index searches more often over table scans.
      • Fixed a performance problem with InnoDB tables when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries will now also generally run faster on all platforms.
      • If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog name and the offset InnoDB was able to recover to. This is useful, for example, when resynchronising a master and a slave database in replication.
      • Added better error messages to help in installation problems of InnoDB tables.
      • It is now possible to recover MySQL temporary tables that have become orphaned inside the InnoDB tablespace.
      • InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns.
      • Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld crash. Especially at risk was mysqldump, because it frequently calls SHOW CREATE TABLE.
      • If inserts to several tables containing an AUTO_INCREMENT column were wrapped inside one LOCK TABLES, InnoDB asserted in `lock0lock.c'.
      • In 3.23.47 we allowed several NULL values in a UNIQUE secondary index for an InnoDB table. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation.
      • SHOW GRANTS now shows REFERENCES instead of REFERENCE.

      D.4.11 Changes in release 3.23.47 (2001-12-27)

      • Fixed bug when using the following construct: SELECT ... WHERE key=@var_name OR key=@var_name2
      • Restrict InnoDB keys to 500 bytes.
      • InnoDB now supports NULL in keys.
      • Fixed shutdown problem on HP-UX. (Introduced in 3.23.46)
      • Fixed core dump bug in replication when using SELECT RELEASE_LOCK().
      • Added new command: DO expression,[expression]
      • Added slave-skip-errors option.
      • Added statistics variables for all MySQL commands. (SHOW STATUS is now much longer.)
      • Fixed default values for InnoDB tables.
      • Fixed that GROUP BY expr DESC works.
      • Fixed bug when using t1 LEFT JOIN t2 ON t2.key=constant.
      • mysql_config now also works with binary (relocated) distributions.

      D.4.12 Changes in release 3.23.46 (2001-11-29)

      • Fixed problem with aliased temporary table replication.
      • InnoDB and BDB tables will now use index when doing an ORDER BY on the whole table.
      • Fixed bug where one got an empty set instead of a DEADLOCK error when using BDB tables.
      • One can now kill ANALYZE, REPAIR, and OPTIMIZE TABLE when the thread is waiting to get a lock on the table.
      • Fixed race condition in ANALYZE TABLE.
      • Fixed bug when joining with caching (unlikely to happen).
      • Fixed race condition when using the binary log and INSERT DELAYED which could cause the binary log to have rows that were not yet written to MyISAM tables.
      • Changed caching of binary log to make replication slightly faster.
      • Fixed bug in replication on Mac OS X.

      D.4.13 Changes in release 3.23.45 (2001-11-22)

      • (UPDATE|DELETE) ...WHERE MATCH bugfix.
      • shutdown should now work on Darwin (Mac OS X).
      • Fixed core dump when repairing corrupted packed MyISAM files.
      • --core-file now works on Solaris.
      • Fix a bug which could cause InnoDB to complain if it cannot find free blocks from the buffer cache during recovery.
      • Fixed bug in InnoDB insert buffer B-tree handling that could cause crashes.
      • Fixed bug in InnoDB lock timeout handling.
      • Fixed core dump bug in ALTER TABLE on a TEMPORARY InnoDB table.
      • Fixed bug in OPTIMIZE TABLE that reset index cardinality if it was up to date.
      • Fixed problem with t1 LEFT_JOIN t2 ... WHERE t2.date_column IS NULL when date_column was declared as NOT NULL.
      • Fixed bug with BDB tables and keys on BLOB's.
      • Fixed bug in MERGE tables on OS with 32 bit file pointers.
      • Fixed bug in TIME_TO_SEC() when using negative values.

      D.4.14 Changes in release 3.23.44 (2001-10-31)

      • Fixed Rows_examined count in slow query log.
      • Fixed bug when using a reference to an AVG() column in HAVING.
      • Fixed that date functions that require correct dates, like DAYOFYEAR(column), will return NULL for 0000-00-00 dates.
      • Fixed bug in const-propagation when comparing columns of different types. (SELECT * FROM date_col="2001-01-01" and date_col=time_col)
      • Fixed bug that caused error message Can't write, because of unique constraint with some GROUP BY queries.
      • SJIS において、テーブル名、フィールド名をバッククオートで囲んだ場合の問題を修正
      • Fixed core dump when using CREATE ... FULLTEXT keys with other storage engines than MyISAM.
      • Add missing InnoDB variables to SHOW VARIABLES.
      • Foreign keys checking is now done for InnoDB tables.
      • Don't use signal() on Windows because this appears to not be 100% reliable.
      • Fixed bug when doing WHERE col_name=NULL on an indexed column that had NULL values.
      • Fixed bug when doing LEFT JOIN ... ON (column_name = constant) WHERE column_name = constant.
      • When using replications, aborted queries that contained % could cause a core dump.
      • TCP_NODELAY がいくつかのシステムで使用されていなかったのを修正(TCP 通信時の速度低下の問題).
      • Applied portability fixes for OS/2. (Patch by Yuri Dario.)

      The following changes are for InnoDB tables:

      • Add missing InnoDB variables to SHOW VARIABLES.
      • Foreign keys checking is now done for InnoDB tables.
      • DROP DATABASE now works also for InnoDB tables.
      • InnoDB now supports datafiles and raw disk partitions bigger than 4 GB on those operating systems that have big files.
      • InnoDB calculates better table cardinality estimates for the MySQL optimiser.
      • Accent characters in the default character set latin1 are ordered according to the MySQL ordering. Note: if you are using latin1 and have inserted characters whose code is greater than 127 into an indexed CHAR column, you should run CHECK TABLE on your table when you upgrade to 3.23.44, and drop and reimport the table if CHECK TABLE reports an error!
      • A new `my.cnf' parameter, innodb_thread_concurrency, helps in performance tuning in heavily concurrent environments.
      • A new `my.cnf' parameter, innodb_fast_shutdown, speeds up server shutdown.
      • A new `my.cnf' parameter, innodb_force_recovery, helps to save your data in case the disk image of the database becomes corrupt.
      • innodb_monitor has been improved and a new innodb_table_monitor added.
      • Increased maximum key length from 500 to 7000 bytes.
      • Fixed a bug in replication of AUTO_INCREMENT columns with multiple-line inserts.
      • Fixed a bug when the case of letters changes in an update of an indexed secondary column.
      • Fixed a hang when there are > 24 datafiles.
      • Fixed a crash when MAX(col) is selected from an empty table, and col is not the first column in a multi-column index.
      • Fixed a bug in purge which could cause crashes.

      D.4.15 Changes in release 3.23.43 (2001-10-04)

      • Fixed a bug in INSERT DELAYED and FLUSH TABLES introduced in 3.23.42.
      • Fixed unlikely bug, which returned non-matching rows, in SELECT with many tables and multi-column indexes and 'range' type.
      • Fixed an unlikely core dump bug when doing EXPLAIN SELECT when using many tables and ORDER BY.
      • Fixed bug in LOAD DATA FROM MASTER when using table with CHECKSUM=1.
      • Added unique error message when one gets a DEADLOCK during a transaction with BDB tables.
      • Fixed problem with BDB tables and UNIQUE columns defined as NULL.
      • Fixed problem with myisampack when using pre-space filled CHAR columns.
      • Applied patch from Yuri Dario for OS/2.
      • Fixed bug in --safe-user-create.

      D.4.16 Changes in release 3.23.42 (2001-09-08)

      • Fixed problem when using LOCK TABLES and BDB tables.
      • Fixed problem with REPAIR TABLE on MyISAM tables with row lengths in the range from 65517 to 65520 bytes.
      • Fixed rare hang when doing mysqladmin shutdown when there was a lot of activity in other threads.
      • Fixed problem with INSERT DELAYED where delay thread could be hanging on upgrading locks with no apparent reason.
      • Fixed problem with myisampack and BLOB.
      • Fixed problem when one edited `.MRG' tables by hand. (Patch from Benjamin Pflugmann).
      • Enforce that all tables in a MERGE table come from the same database.
      • Fixed bug with LOAD DATA INFILE and transactional tables.
      • Fix bug when using INSERT DELAYED with wrong column definition.
      • Fixed core dump during REPAIR of some particularly broken tables.
      • Fixed bug in InnoDB and AUTO_INCREMENT columns.
      • Fixed bug in InnoDB and RENAME TABLE columns.
      • Fixed critical bug in InnoDB and BLOB columns. If you have used BLOB columns larger than 8000 bytes in an InnoDB table, it is necessary to dump the table with mysqldump, drop it and restore it from the dump.
      • Applied large patch for OS/2 from Yuri Dario.
      • Fixed problem with InnoDB when one could get the error Can't execute the given command... even when no transaction was active.
      • Applied some minor fixes that concern Gemini.
      • Use real arithmetic operations even in integer context if not all arguments are integers. (Fixes uncommon bug in some integer contexts).
      • Don't force everything to lowercase on Windows. (To fix problem with Windows and ALTER TABLE). Now --lower_case_names also works on Unix.
      • Fixed that automatic rollback is done when thread end doesn't lock other threads.

      D.4.17 Changes in release 3.23.41 (2001-08-11)

      • Added --sql-mode=option[,option[,option]] option to mysqld. 「4.1.1 mysqld コマンド行オプション」節参照.
      • Fixed possible problem with shutdown on Solaris where the `.pid' file wasn't deleted.
      • InnoDB now supports < 4 GB rows. The former limit was 8000 bytes.
      • The doublewrite file flush method is used in InnoDB. It reduces the need for Unix fsync() calls to a fraction and improves performance on most Unix flavors.
      • You can now use the InnoDB Monitor to print a lot of InnoDB state information, including locks, to the standard output. This is useful in performance tuning.
      • Several bugs which could cause hangs in InnoDB have been fixed.
      • Split record_buffer to record_buffer and record_rnd_buffer. To make things compatible to previous MySQL versions, if record_rnd_buffer is not set, then it takes the value of record_buffer.
      • Fixed optimizing bug in ORDER BY where some ORDER BY parts where wrongly removed.
      • Fixed overflow bug with ALTER TABLE and MERGE tables.
      • Added prototypes for my_thread_init() and my_thread_end() to `mysql_com.h'
      • Added --safe-user-create option to mysqld.
      • Fixed bug in SELECT DISTINCT ... HAVING that caused error message Can't find record in #...

      D.4.18 Changes in release 3.23.40 (2001-07-22)

      • Fixed problem with --low-priority-updates and INSERT statements.
      • Fixed bug in slave thread when under some rare circumstances it could get 22 bytes ahead on the offset in the master.
      • Added slave_net_timeout for replication.
      • Fixed problem with UPDATE and BDB tables.
      • Fixed hard bug in BDB tables when using key parts.
      • Fixed problem when using GRANT FILE ON database.* ...; previously we added the DROP privilege for the database.
      • Fixed DELETE FROM tbl_name ... LIMIT 0 and UPDATE FROM tbl_name ... LIMIT 0, which acted as though the LIMIT clause was not present (they deleted or updated all selected rows).
      • CHECK TABLE now checks if an AUTO_INCREMENT column contains the value 0.
      • Sending a SIGHUP to mysqld will now only flush the logs, not reset the replication.
      • Fixed parser to allow floats of type 1.0e1 (no sign after e).
      • Option --force to myisamchk now also updates states.
      • Added option --warnings to mysqld. Now mysqld prints the error Aborted connection only if this option is used.
      • Fixed problem with SHOW CREATE TABLE when you didn't have a PRIMARY KEY.
      • Properly fixed the rename of innodb_unix_file_flush_method variable to innodb_flush_method.
      • Fixed bug when converting BIGINT UNSIGNED to DOUBLE. This caused a problem when doing comparisons with BIGINT values outside of the signed range.
      • Fixed bug in BDB tables when querying empty tables.
      • Fixed a bug when using COUNT(DISTINCT) with LEFT JOIN and there weren't any matching rows.
      • Removed all documentation referring to the GEMINI table type. GEMINI is not released under an Open Source license.

      D.4.19 Changes in release 3.23.39 (2001-06-12)

      • The AUTO_INCREMENT sequence wasn't reset when dropping and adding an AUTO_INCREMENT column.
      • CREATE ... SELECT now creates non-unique indexes delayed.
      • Fixed problem where LOCK TABLES tbl_name READ followed by FLUSH TABLES put an exclusive lock on the table.
      • REAL @variable values were represented with only 2 digits when converted to strings.
      • Fixed problem that client ``hung'' when LOAD TABLE FROM MASTER failed.
      • myisamchk --fast --force will no longer repair tables that only had the open count wrong.
      • Added functions to handle symbolic links to make life easier in 4.0.
      • We are now using the -lcma thread library on HP-UX 10.20 so that MySQL will be more stable on HP-UX.
      • Fixed problem with IF() and number of decimals in the result.
      • Fixed date-part extraction functions to work with dates where day and/or month is 0.
      • Extended argument length in option files from 256 to 512 chars.
      • Fixed problem with shutdown when INSERT DELAYED was waiting for a LOCK TABLE.
      • Fixed core dump bug in InnoDB when tablespace was full.
      • Fixed problem with MERGE tables and big tables (> 4G) when using ORDER BY.

      D.4.20 Changes in release 3.23.38 (2001-05-09)

      • Fixed a bug when SELECT from MERGE table sometimes results in incorrectly ordered rows.
      • Fixed a bug in REPLACE() when using the ujis character set.
      • Applied Sleepycat BDB patches 3.2.9.1 and 3.2.9.2.
      • Added --skip-stack-trace option to mysqld.
      • CREATE TEMPORARY now works with InnoDB tables.
      • InnoDB now promotes sub keys to whole keys.
      • Added option CONCURRENT to LOAD DATA.
      • Better error message when slave max_allowed_packet is too low to read a very long log event from the master.
      • Fixed bug when too many rows where removed when using SELECT DISTINCT ... HAVING.
      • SHOW CREATE TABLE now returns TEMPORARY for temporary tables.
      • Added Rows_examined to slow query log.
      • Fixed problems with function returning empty string when used together with a group function and a WHERE that didn't match any rows.
      • New program mysqlcheck.
      • Added database name to output for administrative commands like CHECK, REPAIR, OPTIMIZE.
      • Lots of portability fixes for InnoDB.
      • Changed optimizer so that queries like SELECT * FROM tbl_name,tbl_name2 ... ORDER BY key_part1 LIMIT # will use index on key_part1 instead of filesort.
      • Fixed bug when doing LOCK TABLE to_table WRITE,...; INSERT INTO to_table... SELECT ... when to_table was empty.
      • Fixed bug with LOCK TABLE and BDB tables.

      D.4.21 Changes in release 3.23.37 (2001-04-17)

      • Fixed a bug when using MATCH() in HAVING clause.
      • Fixed a bug when using HEAP tables with LIKE.
      • Added --mysql-version option to safe_mysqld
      • Changed INNOBASE to InnoDB (because the INNOBASE name was already used). All configure options and mysqld start options now use innodb instead of innobase. This means that before upgrading to this version, you have to change any configuration files where you have used innobase options!
      • Fixed bug when using indexes on CHAR(255) NULL columns.
      • Slave thread will now be started even if master-host is not set, as long as server-id is set and valid `master.info' is present.
      • Partial updates (terminated with kill) are now logged with a special error code to the binary log. Slave will refuse to execute them if the error code indicates the update was terminated abnormally, and will have to be recovered with SET SQL_SLAVE_SKIP_COUNTER=1; SLAVE START after a manual sanity check/correction of data integrity.
      • Fixed bug that erroneously logged a drop of internal temporary table on thread termination to the binary log -- this bug affected replication.
      • Fixed a bug in REGEXP on 64-bit machines.
      • UPDATE and DELETE with WHERE unique_key_part IS NULL didn't update/delete all rows.
      • Disabled INSERT DELAYED for tables that support transactions.
      • Fixed bug when using date functions on TEXT/BLOB column with wrong date format.
      • UDFs now also work on Windows. (Patch by Ralph Mason.)
      • Fixed bug in ALTER TABLE and LOAD DATA INFILE that disabled key-sorting. These commands should now be faster in most cases.
      • Fixed performance bug where reopened tables (tables that had been waiting for FLUSH or REPAIR) would not use indexes for the next query.
      • Fixed problem with ALTER TABLE to InnoDB tables on FreeBSD.
      • Added mysqld variables myisam_max_sort_file_size and myisam_max_extra_sort_file_size.
      • Initialise signals early to avoid problem with signals in InnoDB.
      • Applied patch for the tis620 character set to make comparisons case-independent and to fix a bug in LIKE for this character set. Note: All tables that uses the tis620 character set must be fixed with myisamchk -r or REPAIR TABLE !
      • Added --skip-safemalloc option to mysqld.

      D.4.22 Changes in release 3.23.36 (2001-03-27)

      • Fixed a bug that allowed use of database names containing a `.' character. This fixes a serious security issue when mysqld is run as root.
      • Fixed bug when thread creation failed (could happen when doing a lot of connections in a short time).
      • Fixed some problems with FLUSH TABLES and TEMPORARY tables. (Problem with freeing the key cache and error Can't reopen table....)
      • Fixed a problem in InnoDB with other character sets than latin1 and another problem when using many columns.
      • Fixed bug that caused a core dump when using a very complex query involving DISTINCT and summary functions.
      • Added SET TRANSACTION ISOLATION LEVEL ...
      • Added SELECT ... FOR UPDATE.
      • Fixed bug where the number of affected rows was not returned when MySQL was compiled without transaction support.
      • Fixed a bug in UPDATE where keys weren't always used to find the rows to be updated.
      • Fixed a bug in CONCAT_WS() where it returned incorrect results.
      • Changed CREATE ... SELECT and INSERT ... SELECT to not allow concurrent inserts as this could make the binary log hard to repeat. (Concurrent inserts are enabled if you are not using the binary or update log.)
      • Changed some macros to be able to use fast mutex with glibc 2.2.

      D.4.23 Changes in release 3.23.35 (2001-03-15)

      • Fixed newly introduced bug in ORDER BY.
      • Fixed wrong define CLIENT_TRANSACTIONS.
      • Fixed bug in SHOW VARIABLES when using INNOBASE tables.
      • Setting and using user variables in SELECT DISTINCT didn't work.
      • Tuned SHOW ANALYZE for small tables.
      • Fixed handling of arguments in the benchmark script run-all-tests.

      D.4.24 Changes in release 3.23.34a (2001-03-12)

      • Added extra files to the distribution to allow INNOBASE support to be compiled.

      D.4.25 Changes in release 3.23.34 (2001-03-10)

      • Added the INNOBASE storage engine and the BDB storage engine to the MySQL source distribution.
      • Updated the documentation about GEMINI tables.
      • Fixed a bug in INSERT DELAYED that caused threads to hang when inserting NULL into an AUTO_INCREMENT column.
      • Fixed a bug in CHECK TABLE / REPAIR TABLE that could cause a thread to hang.
      • REPLACE will not replace a row that conflicts with an AUTO_INCREMENT generated key.
      • mysqld now only sets CLIENT_TRANSACTIONS in mysql->server_capabilities if the server supports a transaction-safe storage engine.
      • Fixed LOAD DATA INFILE to allow numeric values to be read into ENUM and SET columns.
      • Improved error diagnostic for slave thread exit.
      • Fixed bug in ALTER TABLE ... ORDER BY.
      • Added max_user_connections variable to mysqld.
      • Limit query length for replication by max_allowed_packet, not the arbitrary limit of 4 MB.
      • Allow space around = in argument to --set-variable.
      • Fixed problem in automatic repair that could leave some threads in state Waiting for table.
      • SHOW CREATE TABLE now displays the UNION() for MERGE tables.
      • ALTER TABLE now remembers the old UNION() definition.
      • Fixed bug when replicating timestamps.
      • Fixed bug in bidirectional replication.
      • Fixed bug in the BDB storage engine that occurred when using an index on multi-part key where a key part may be NULL.
      • Fixed MAX() optimization on sub-key for BDB tables.
      • Fixed problem where garbage results were returned when using BDB tables and BLOB or TEXT fields when joining many tables.
      • Fixed a problem with BDB tables and TEXT columns.
      • Fixed bug when using a BLOB key where a const row wasn't found.
      • Fixed that mysqlbinlog writes the timestamp value for each query. This ensures that one gets same values for date functions like NOW() when using mysqlbinlog to pipe the queries to another server.
      • Allow --skip-gemini, --skip-bdb, and --skip-innodb options to be specified when invoking mysqld, even if these storage engines are not compiled in to mysqld.
      • One can now do GROUP BY ... DESC.
      • Fixed a deadlock in the SET code, when one ran SET @foo=bar, where bar is a column reference, an error was not properly generated.

      D.4.26 Changes in release 3.23.33 (2001-02-09)

      • Fixed DNS lookups not to use the same mutex as the hostname cache. This will enable known hosts to be quickly resolved even if a DNS lookup takes a long time.
      • Added --character-sets-dir option to myisampack.
      • Removed warnings when running REPAIR TABLE ... EXTENDED.
      • Fixed a bug that caused a core dump when using GROUP BY on an alias, where the alias was the same as an existing column name.
      • Added SEQUENCE() as an example UDF function.
      • Changed mysql_install_db to use BINARY for CHAR columns in the privilege tables.
      • Changed TRUNCATE tbl_name to TRUNCATE TABLE tbl_name to use the same syntax as Oracle. Until 4.0 we will also allow TRUNCATE tbl_name to not crash old code.
      • Fixed ``no found rows'' bug in MyISAM tables when a BLOB was first part of a multi-part key.
      • Fixed bug where CASE didn't work with GROUP BY.
      • Added --sort-recover option to myisamchk.
      • myisamchk -S and OPTIMIZE TABLE now work on Windows.
      • Fixed bug when using DISTINCT on results from functions that referred to a group function, like: 
        SELECT a, DISTINCT SEC_TO_TIME(SUM(a))
FROM tbl_name GROUP BY a, b;
      • Fixed buffer overrun in libmysqlclient library. Fixed bug in handling STOP event after ROTATE event in replication.
      • Fixed another buffer overrun in DROP DATABASE.
      • Added Table_locks_immediate and Table_locks_waited status variables.
      • Fixed bug in replication that broke slave server start with existing `master.info'. This fixes a bug introduced in 3.23.32.
      • Added SET SQL_SLAVE_SKIP_COUNTER=n command to recover from replication glitches without a full database copy.
      • Added max_binlog_size variable; the binary log will be rotated automatically when the size crosses the limit.
      • Added Last_error, Last_errno, and Slave_skip_counter variables to SHOW SLAVE STATUS.
      • Fixed bug in MASTER_POS_WAIT() function.
      • Execute core dump handler on SIGILL, and SIGBUS in addition to SIGSEGV.
      • On x86 Linux, print the current query and thread (connection) id, if available, in the core dump handler.
      • Fixed several timing bugs in the test suite.
      • Extended mysqltest to take care of the timing issues in the test suite.
      • ALTER TABLE can now be used to change the definition for a MERGE table.
      • Fixed creation of MERGE tables on Windows.
      • Portability fixes for OpenBSD and OS/2.
      • Added --temp-pool option to mysqld. Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. This is to work around a problem in the Linux kernel dealing with creating a bunch of new files with different names. With the old behaviour, Linux seems to "leak" memory, as it's being allocated to the directory entry cache instead of the disk cache.

      D.4.27 Changes in release 3.23.32 (2001-01-22; Stable)

      • Changed code to get around compiler bug in Compaq C++ on OSF/1, that broke BACKUP, RESTORE, CHECK, REPAIR, and ANALYZE TABLE.
      • Added option FULL to SHOW COLUMNS. Now we show the privilege list for the columns only if this option is given.
      • Fixed bug in SHOW LOGS when there weren't any BDB logs.
      • Fixed a timing problem in replication that could delay sending an update to the client until a new update was done.
      • Don't convert field names when using mysql_list_fields(). This is to keep this code compatible with SHOW FIELDS.
      • MERGE tables didn't work on Windows.
      • Fixed problem with SET PASSWORD=... on Windows.
      • Added missing `my_config.h' to RPM distribution.
      • TRIM("foo" from "foo") didn't return an empty string.
      • Added --with-version-suffix option to configure.
      • Fixed core dump when client aborted connection without mysql_close().
      • Fixed a bug in RESTORE TABLE when trying to restore from a non-existent directory.
      • Fixed a bug which caused a core dump on the slave when replicating SET PASSWORD.
      • Added MASTER_POS_WAIT().

      D.4.28 Changes in release 3.23.31 (2001-01-17)

      • The test suite now tests all reachable BDB interface code. During testing we found and fixed many errors in the interface code.
      • Using HAVING on an empty table could produce one result row when it shouldn't.
      • Fixed the MySQL RPM not to depend on Perl5 anymore.
      • Fixed some problems with HEAP tables on Windows.
      • SHOW TABLE STATUS didn't show correct average row length for tables larger than 4G.
      • CHECK TABLE ... EXTENDED didn't check row links for fixed size tables.
      • Added option MEDIUM to CHECK TABLE.
      • Fixed problem when using DECIMAL() keys on negative numbers.
      • HOUR() (and some other TIME functions) on a CHAR column always returned NULL.
      • Fixed security bug in something (please upgrade if you are using an earlier MySQL 3.23 version).
      • Fixed buffer overflow bug when writing a certain error message.
      • Added usage of setrlimit() on Linux to get -O --open-files-limit=# to work on Linux.
      • Added bdb_version variable to mysqld.
      • Fixed bug when using expression of type: 
        SELECT ... FROM t1 LEFT JOIN t2 ON (t1.a=t2.a) WHERE t1.a=t2.a
        In this case the test in the WHERE clause was wrongly optimized away.
      • Fixed bug in MyISAM when deleting keys with possible NULL values, but the first key-column was not a prefix-compressed text column.
      • Fixed mysql.server to read the [mysql.server] option file group rather than the [mysql_server] group.
      • Fixed safe_mysqld and mysql.server to also read the server option section.
      • Added Threads_created status variable to mysqld.

      D.4.29 Changes in release 3.23.30 (2001-01-04)

      • Added SHOW OPEN TABLES command.
      • Fixed that myisamdump works against old mysqld servers.
      • Fixed myisamchk -k# so that it works again.
      • Fixed a problem with replication when the binary log file went over 2G on 32-bit systems.
      • LOCK TABLES will now automatically start a new transaction.
      • Changed BDB tables to not use internal subtransactions and reuse open files to get more speed.
      • Added --mysqld=# option to safe_mysqld.
      • Allow hex constants in the --fields-*-by and --lines-terminated-by options to mysqldump and mysqlimport. By Paul DuBois.
      • Added --safe-show-database option to mysqld.
      • Added have_bdb, have_gemini, have_innobase, have_raid and have_openssl to SHOW VARIABLES to make it easy to test for supported extensions.
      • Added --open-files-limit option to mysqld.
      • Changed --open-files option to --open-files-limit in safe_mysqld.
      • Fixed a bug where some rows were not found with HEAP tables that had many keys.
      • Fixed that --bdb-no-sync works.
      • Changed --bdb-recover to --bdb-no-recover as recover should be on by default.
      • Changed the default number of BDB locks to 10000.
      • Fixed a bug from 3.23.29 when allocating the shared structure needed for BDB tables.
      • Changed mysqld_multi.sh to use configure variables. Patch by Christopher McCrory.
      • Added fixing of include files for Solaris 2.8.
      • Fixed bug with --skip-networking on Debian Linux.
      • Fixed problem that some temporary files where reported as having the name UNOPENED in error messages.
      • Fixed bug when running two simultaneous SHOW LOGS queries.

      D.4.30 Changes in release 3.23.29 (2000-12-16)

      • Configure updates for Tru64, large file support, and better TCP wrapper support. By Albert Chin-A-Young.
      • Fixed bug in <=> operator.
      • Fixed bug in REPLACE with BDB tables.
      • LPAD() and RPAD() will shorten the result string if it's longer than the length argument.
      • Added SHOW LOGS command.
      • Remove unused BDB logs on shutdown.
      • When creating a table, put PRIMARY keys first, followed by UNIQUE keys.
      • Fixed a bug in UPDATE involving multi-part keys where one specified all key parts both in the update and the WHERE part. In this case MySQL could try to update a record that didn't match the whole WHERE part.
      • Changed drop table to first drop the tables and then the `.frm' file.
      • Fixed a bug in the hostname cache which caused mysqld to report the hostname as '' in some error messages.
      • Fixed a bug with HEAP type tables; the variable max_heap_table_size wasn't used. Now either MAX_ROWS or max_heap_table_size can be used to limit the size of a HEAP type table.
      • Changed the default server-id to 1 for masters and 2 for slaves to make it easier to use the binary log.
      • Renamed bdb_lock_max variable to bdb_max_lock.
      • Added support for AUTO_INCREMENT on sub-fields for BDB tables.
      • Added ANALYZE of BDB tables.
      • In BDB tables, we now store the number of rows; this helps to optimise queries when we need an approximation of the number of rows.
      • If we get an error in a multi-row statement, we now only roll back the last statement, not the entire transaction.
      • If you do a ROLLBACK when you have updated a non-transactional table you will get an error as a warning.
      • Added --bdb-shared-data option to mysqld.
      • Added Slave_open_temp_tables status variable to mysqld
      • Added binlog_cache_size and max_binlog_cache_size variables to mysqld.
      • DROP TABLE, RENAME TABLE, CREATE INDEX and DROP INDEX are now transaction endpoints.
      • If you do a DROP DATABASE on a symbolically linked database, both the link and the original database is deleted.
      • Fixed DROP DATABASE to work on OS/2.
      • Fixed bug when doing a SELECT DISTINCT ... table1 LEFT JOIN table2 ... when table2 was empty.
      • Added --abort-slave-event-count and --disconnect-slave-event-count options to mysqld for debugging and testing of replication.
      • Fixed replication of temporary tables. Handles everything except slave server restart.
      • SHOW KEYS now shows whether key is FULLTEXT.
      • New script mysqld_multi. 「4.7.3 mysqld_multi, 複数の MySQL サーバーを管理するプログラム」節参照.
      • Added new script, mysql-multi.server.sh. Thanks to Tim Bunce Tim.Bunce@ig.co.uk for modifying mysql.server to easily handle hosts running many mysqld processes.
      • safe_mysqld, mysql.server, and mysql_install_db have been modified to use mysql_print_defaults instead of various hacks to read the `my.cnf' files. In addition, the handling of various paths has been made more consistent with how mysqld handles them by default.
      • Automatically remove Berkeley DB transaction logs that no longer are in use.
      • Fixed bug with several FULLTEXT indexes in one table.
      • Added a warning if number of rows changes on REPAIR/OPTIMIZE.
      • Applied patches for OS/2 by Yuri Dario.
      • FLUSH TABLES tbl_name didn't always flush the index tree to disk properly.
      • --bootstrap is now run in a separate thread. This fixes a problem that caused mysql_install_db to core dump on some Linux machines.
      • Changed mi_create() to use less stack space.
      • Fixed bug with optimiser trying to over-optimise MATCH() when used with UNIQUE key.
      • Changed crash-me and the MySQL benchmarks to also work with FrontBase.
      • Allow RESTRICT and CASCADE after DROP TABLE to make porting easier.
      • Reset status variable which could cause problem if one used --slow-log.
      • Added connect_timeout variable to mysql and mysqladmin.
      • Added connect-timeout as an alias for timeout for option files read by mysql_options().

      D.4.31 Changes in release 3.23.28 (2000-11-22; Gamma)

      • Added new options --pager[=...], --no-pager, --tee=... and --no-tee to the mysql client. The new corresponding interactive commands are pager, nopager, tee and notee. 「4.8.2 mysql, コマンドラインツール」節参照, mysql --help and the interactive help for more information.
      • Fixed crash when automatic repair of MyISAM table failed.
      • Fixed a major performance bug in the table locking code when one constantly had a lot of SELECT, UPDATE and INSERT statements running. The symptom was that the UPDATE and INSERT queries were locked for a long time while new SELECT statements were executed before the updates.
      • When reading options_files with mysql_options() the return-found-rows option was ignored.
      • One can now specify interactive-timeout in the option file that is read by mysql_options(). This makes it possible to force programs that run for a long time (like mysqlhotcopy) to use the interactive_timeout time instead of the wait_timeout time.
      • Added to the slow query log the time and the user name for each logged query. If you are using --log-long-format then also queries that do not use an index are logged, even if the query takes less than long_query_time seconds.
      • Fixed a problem in LEFT JOIN which caused all columns in a reference table to be NULL.
      • Fixed a problem when using NATURAL JOIN without keys.
      • Fixed a bug when using a multi-part keys where the first part was of type TEXT or BLOB.
      • DROP of temporary tables wasn't stored in the update/binary log.
      • Fixed a bug where SELECT DISTINCT * ... LIMIT # only returned one row.
      • Fixed a bug in the assembler code in strstr() for SPARC and cleaned up the `global.h' header file to avoid a problem with bad aliasing with the compiler submitted with RedHat 7.0. (Reported by Trond Eivind Glomsrd)
      • The --skip-networking option now works properly on NT.
      • Fixed a long outstanding bug in the ISAM tables when a row with a length of more than 65K was shortened by a single byte.
      • Fixed a bug in MyISAM when running multiple updating processes on the same table.
      • Allow one to use FLUSH TABLE tbl_name.
      • Added --replicate-ignore-table, --replicate-do-table, --replicate-wild-ignore-table, and --replicate-wild-do-table options to mysqld.
      • Changed all log files to use our own IO_CACHE mechanism instead of FILE to avoid OS problems when there are many files open.
      • Added --open-files and --timezone options to safe_mysqld.
      • Fixed a fatal bug in CREATE TEMPORARY TABLE ... SELECT ....
      • Fixed a problem with CREATE TABLE ... SELECT NULL.
      • Added variables large_file_support,net_read_timeout, net_write_timeout and query_buffer_size to SHOW VARIABLES.
      • Added status variables created_tmp_files and sort_merge_passes to SHOW STATUS.
      • Fixed a bug where we didn't allow an index name after the FOREIGN KEY definition.
      • Added TRUNCATE table_name as a synonym for DELETE FROM table_name.
      • Fixed a bug in a BDB key compare function when comparing part keys.
      • Added bdb_lock_max variable to mysqld.
      • Added more tests to the benchmark suite.
      • Fixed an overflow bug in the client code when using overly long database names.
      • mysql_connect() now aborts on Linux if the server doesn't answer in timeout seconds.
      • SLAVE START did not work if you started with --skip-slave-start and had not explicitly run CHANGE MASTER TO.
      • Fixed the output of SHOW MASTER STATUS to be consistent with SHOW SLAVE STATUS. (It now has no directory in the log name.)
      • Added PURGE MASTER LOGS TO.
      • Added SHOW MASTER LOGS.
      • Added --safemalloc-mem-limit option to mysqld to simulate memory shortage when compiled with the --with-debug=full option.
      • Fixed several core dumps in out-of-memory conditions.
      • SHOW SLAVE STATUS was using an uninitialised mutex if the slave had not been started yet.
      • Fixed bug in ELT() and MAKE_SET() when the query used a temporary table.
      • CHANGE MASTER TO without specifying MASTER_LOG_POS would set it to 0 instead of 4 and hit the magic number in the master binlog.
      • ALTER TABLE ... ORDER BY ... syntax added. This will create the new table with the rows in a specific order.

      D.4.32 Changes in release 3.23.27 (2000-10-24)

      • Fixed a bug where the automatic repair of MyISAM tables sometimes failed when the datafile was corrupt.
      • Fixed a bug in SHOW CREATE when using AUTO_INCREMENT columns.
      • Changed BDB tables to use new compare function in Berkeley DB 3.2.3.
      • You can now use Unix sockets with MIT-pthreads.
      • Added the latin5 (turkish) character set.
      • Small portability fixes.

      D.4.33 Changes in release 3.23.26 (2000-10-18)

      • Renamed FLUSH MASTER and FLUSH SLAVE to RESET MASTER and RESET SLAVE.
      • Fixed <> to work properly with NULL.
      • Fixed a problem with SUBSTRING_INDEX() and REPLACE(). (Patch by Alexander Igonitchev)
      • Fix CREATE TEMPORARY TABLE IF NOT EXISTS not to produce an error if the table exists.
      • If you don't create a PRIMARY KEY in a BDB table, a hidden PRIMARY KEY will be created.
      • Added read-only-key optimisation to BDB tables.
      • LEFT JOIN in some cases preferred a full table scan when there was no WHERE clause.
      • When using --log-slow-queries, don't count the time waiting for a lock.
      • Fixed bug in lock code on Windows which could cause the key cache to report that the key file was crashed even if it was okay.
      • Automatic repair of MyISAM tables if you start mysqld with --myisam-recover.
      • Removed the TYPE= keyword from CHECK and REPAIR. Allow CHECK options to be combined. (You can still use TYPE=, but this usage is deprecated.)
      • Fixed mutex bug in the binary replication log -- long update queries could be read only in part by the slave if it did it at the wrong time, which was not fatal, but resulted in a performance-degrading reconnect and a scary message in the error log.
      • Changed the format of the binary log -- added magic number, server version, binlog version. Added server id and query error code for each query event.
      • Replication thread from the slave now will kill all the stale threads from the same server.
      • Long replication user names were not being handled properly.
      • Added --replicate-rewrite-db option to mysqld.
      • Added --skip-slave-start option to mysqld.
      • Updates that generated an error code (such as INSERT INTO foo(some_key) values (1),(1)) erroneously terminated the slave thread.
      • Added optimization of queries where DISTINCT is only used on columns from some of the tables.
      • Allow floating-point numbers where there is no sign after the exponent (like 1e1).
      • SHOW GRANTS didn't always show all column grants.
      • Added --default-extra-file=# option to all MySQL clients.
      • Columns referenced in INSERT statements now are initialised properly.
      • UPDATE didn't always work when used with a range on a timestamp that was part of the key that was used to find rows.
      • Fixed a bug in FULLTEXT index when inserting a NULL column.
      • Changed to use mkstemp() instead of tempnam(). Based on a patch from John Jones.

      D.4.34 Changes in release 3.23.25 (2000-09-29)

      • Fixed that databasename works as second argument to mysqlhotcopy.
      • The values for the UMASK and UMASK_DIR environment variables now can be specified in octal by beginning the value with a zero.
      • Added RIGHT JOIN. This makes RIGHT a reserved word.
      • Added @@IDENTITY as a synonym for LAST_INSERT_ID(). (This is for MSSQL compatibility.)
      • Fixed a bug in myisamchk and REPAIR when using FULLTEXT index.
      • LOAD DATA INFILE now works with FIFOs. (Patch by Toni L. Harbaugh-Blackford.)
      • FLUSH LOGS broke replication if you specified a log name with an explicit extension as the value of the log-bin option.
      • Fixed a bug in MyISAM with packed multi-part keys.
      • Fixed crash when using CHECK TABLE on Windows.
      • Fixed a bug where FULLTEXT index always used the koi8_ukr character set.
      • Fixed privilege checking for CHECK TABLE.
      • The MyISAM repair/reindex code didn't use the --tmpdir option for its temporary files.
      • Added BACKUP TABLE and RESTORE TABLE.
      • Fixed core dump on CHANGE MASTER TO when the slave did not have the master to start with.
      • Fixed incorrect Time in the processlist for Connect of the slave thread.
      • The slave now logs when it connects to the master.
      • Fixed a core dump bug when doing FLUSH MASTER if you didn't specify a filename argument to --log-bin.
      • Added missing `ha_berkeley.x' files to the MySQL Windows distribution.
      • Fixed some mutex bugs in the log code that could cause thread blocks if new log files couldn't be created.
      • Added lock time and number of selected processed rows to slow query log.
      • Added --memlock option to mysqld to lock mysqld in memory on systems with the mlockall() call (like in Solaris).
      • HEAP tables didn't use keys properly. (Bug from 3.23.23.)
      • Added better support for MERGE tables (keys, mapping, creation, documentation...). 「7.2 MERGE Tables (3.23.25以上)」節参照.
      • Fixed bug in mysqldump from 3.23 which caused some CHAR columns not to be quoted.
      • Merged analyze, check, optimize and repair code.
      • OPTIMIZE TABLE is now mapped to REPAIR with statistics and sorting of the index tree. This means that for the moment it only works on MyISAM tables.
      • Added a pre-alloced block to root_malloc to get fewer mallocs.
      • Added a lot of new statistics variables.
      • Fixed ORDER BY bug with BDB tables.
      • Removed warning that mysqld couldn't remove the `.pid' file under Windows.
      • Changed --log-isam to log MyISAM tables instead of isam tables.
      • Fixed CHECK TABLE to work on Windows.
      • Added file mutexes to make pwrite() safe on Windows.

      D.4.35 Changes in release 3.23.24 (2000-09-08)

      • Added created_tmp_disk_tables variable to mysqld.
      • To make it possible to reliably dump and restore tables with TIMESTAMP(X) columns, MySQL now reports columns with X other than 14 or 8 to be strings.
      • Changed sort order for latin1 as it was before MySQL Version 3.23.23. Any table that was created or modified with 3.23.22 must be repaired if it has CHAR columns that may contain characters with ASCII values greater than 128!
      • Fixed small memory leak introduced from 3.23.22 when creating a temporary table.
      • Fixed problem with BDB tables and reading on a unique (not primary) key.
      • Restored the win1251 character set (it's now only marked deprecated).

      D.4.36 Changes in release 3.23.23 (2000-09-01)

      • Changed sort order for 'German'; all tables created with 'German' sortorder must be repaired with REPAIR TABLE or myisamchk before use!
      • Added --core-file option to mysqld to get a core file on Linux if mysqld dies on the SIGSEGV signal.
      • MySQL クライアントの mysql は、デフォルトで --no-named-commands (-g) オプションで起動されるようになった。 このオプションは --enable-named-commands (-G) で無効にできる。 これはある場合に非互換の問題を引き起こすでしょう。たとえば、セミコロンなしで named コマンドを使用している SQL スクリプトなど！ Long format commands still work from the first line.
      • Fixed a problem when using many pending DROP TABLE statements at the same time.
      • Optimizer didn't use keys properly when using LEFT JOIN on an empty table.
      • Added shorter help text when invoking mysqld with incorrect options.
      • Fixed non-fatal free() bug in mysqlimport.
      • Fixed bug in MyISAM index handling of DECIMAL/NUMERIC keys.
      • Fixed a bug in concurrent insert in MyISAM tables. In some contexts, usage of MIN(key_part) or MAX(key_part) returned an empty set.
      • Updated mysqlhotcopy to use the new FLUSH TABLES table_list syntax. Only tables which are being backed up are flushed now.
      • --enable-thread-safe-client の振る舞いを変更。 非スレッド (-lmysqlclient) とスレッド (-lmysqlclient_r) ライブラリ の両方が作成されるため。 今までスレッド化された -lmysqlclient をリンクしていた場合には、 今後、libmysqlclient_r のリンクが必要となる。
      • Added atomic RENAME TABLE command.
      • COUNT(DISTINCT ...) は NULL のエントリを数えない。
      • Changed ALTER TABLE, LOAD DATA INFILE on empty tables and INSERT ... SELECT ... on empty tables to create non-unique indexes in a separate batch with sorting. This will make the above calls much faster when you have many indexes.
      • ALTER TABLE now logs the first used insert_id correctly.
      • BLOB フィールドにデフォルト値を定義した場合にクラッシュしていたのを修正。
      • DATE_ADD/DATE_SUB が date でなく datetime を返していたバグを修正。
      • Fixed a problem with the thread cache which made some threads show up as ***DEAD*** in SHOW PROCESSLIST.
      • Fixed a lock in our thr_rwlock code, which could make selects that run at the same time as concurrent inserts crash. This only affects systems that don't have the pthread_rwlock_rdlock code.
      • When deleting rows with a non-unique key in a HEAP table, all rows weren't always deleted.
      • Fixed bug in range optimiser for HEAP tables for searches on a part index.
      • Fixed SELECT on part keys to work with BDB tables.
      • Fixed INSERT INTO bdb_table ... SELECT to work with BDB tables.
      • CHECK TABLE now updates key statistics for the table.
      • ANALYZE TABLE will now only update tables that have been changed since the last ANALYZE. Note that this is a new feature and tables will not be marked to be analysed until they are updated in any way with 3.23.23 or newer. For older tables, you have to do CHECK TABLE to update the key distribution.
      • Fixed some minor privilege problems with CHECK, ANALYZE, REPAIR and SHOW CREATE commands.
      • CHANGE MASTER TO コマンドの追加。
      • Added FAST, QUICK EXTENDED check types to CHECK TABLES.
      • Changed myisamchk so that --fast and --check-only-changed are also honored with --sort-index and --analyze.
      • LOAD TABLE FROM MASTER がインデックスを再構築している間にテーブルを ロックしなかったバグを修正。
      • もしデータベースがレプリケーション対象外の場合に LOAD DATA INFILE を 行うと、レプリケーションを壊していたのを修正。
      • More variables in SHOW SLAVE STATUS and SHOW MASTER STATUS.
      • SLAVE STOP now will not return until the slave thread actually exits.
      • MATCH 関数を利用した Full-text search と FULLTEXT インデックスの追加。 (MyISAM でのみ利用可能)。 これにより FULLTEXT が予約語になる。

      D.4.37 Changes in release 3.23.22 (2000-07-31)

      • Fixed that lex_hash.h is created properly for each MySQL distribution.
      • Fixed that MASTER and COLLECTION are not reserved words.
      • The log generated by --slow-query-log didn't contain the whole queries.
      • Fixed that open transactions in BDB tables are rolled back if the connection is closed unexpectedly.
      • Added workaround for a bug in gcc 2.96 (intel) and gcc 2.9 (IA64) in gen_lex_hash.c.
      • `my.cnf' ファイルで host= を使用した場合、 クライアントライブラリにメモリリークがあったのを修正した。
      • Optimized functions that manipulate the hours/minutes/seconds.
      • Fixed bug when comparing the result of DATE_ADD()/DATE_SUB() against a number.
      • Changed the meaning of -F, --fast for myisamchk. Added -C, --check-only-changed option to myisamchk.
      • Added ANALYZE tbl_name to update key statistics for tables.
      • Changed binary items 0x... to be regarded as integers by default.
      • Fix for SCO and SHOW PROCESSLIST.
      • Added auto-rehash on reconnect for the mysql client.
      • MyISAM の インデックスファイルが 64M bytes を超えれないバグを修正した。 3.23.21 でエンバグした。
      • SHOW MASTER STATUS と SHOW SLAVE STATUS の追加。

      D.4.38 Changes in release 3.23.21 (2000-07-05)

      • MySQL C API に mysql_character_set_name() 関数を追加。
      • Made the update log ASCII 0 safe.
      • mysql_config スクリプトの追加。
      • Fixed problem when using < or > with a char column that was only partly indexed.
      • One would get a core dump if the log file was not readable by the MySQL user.
      • mysqladmin を、API コールしていたかわりに、 CREATE DATABASE/DROP DATABASE コマンドを 使用するように変更した。
      • Fixed chown warning in safe_mysqld.
      • ORDER BY のバグを修正。 3.23.19 でエンバグした。
      • Only optimize the DELETE FROM tbl_name to do a drop+create of the table if we are in AUTOCOMMIT mode (needed for BDB tables).
      • Added extra checks to avoid index corruption when the ISAM/MyISAM index files get full during an INSERT/UPDATE.
      • myisamchk didn't correctly update row checksum when used with -ro (this only gave a warning in subsequent runs).
      • Fixed bug in REPAIR TABLE so that it works with tables without indexes.
      • Fixed buffer overrun in DROP DATABASE.
      • LOAD TABLE FROM MASTER is sufficiently bug-free to announce it as a feature.
      • MATCH と AGAINST が予約語になった。

      D.4.39 Changes in release 3.23.20

      • 3.23.19 のバグを修正した; DELETE FROM tbl_name が `.frm' ファイルを消してしまっていた。
      • Added SHOW CREATE TABLE.

      D.4.40 Changes in release 3.23.19

      • 全てのファイルのコピライトの変更。 サーバーとユーティリティのコードは GPL に, クライアントライブラリは LGPL に。
      • Fixed bug where all rows matching weren't updated on a MyISAM table when doing update based on key on a table with many keys and some key changed values.
      • The Linux MySQL RPM's and binaries are now statically linked with a linuxthread version that has faster mutex handling when used with MySQL.
      • ORDER BY can now use REF keys to find subsets of the rows that need to be sorted.
      • print_defaults の名前を my_print_defaults に変更。 名前の衝突をさけるため。
      • Fixed NULLIF() to work according to ANSI SQL99.
      • net_read_timeout と net_write_timeout を mysqld の起動時のパラメタとして追加。
      • Fixed bug that destroyed index when doing myisamchk --sort-records on a table with prefix compressed index.
      • pack_isam と myisampack を MySQL の標準配布に追加。
      • Added the syntax BEGIN WORK (the same as BEGIN).
      • Fixed core dump bug when using ORDER BY on a CONV() expression.
      • Added LOAD TABLE FROM MASTER
      • Added FLUSH MASTER and FLUSH SLAVE
      • Fixed big/little endian problem in the replication

      D.4.41 Changes in release 3.23.18 (2000-06-15)

      • Fixed a problem from 3.23.17 when choosing character set on the client side.
      • Added FLUSH TABLES WITH READ LOCK to make a global lock suitable for making a copy of MySQL datafiles.
      • CREATE TABLE ... SELECT ... PROCEDURE now works.
      • Internal temporary tables will now use compressed index when using GROUP BY on VARCHAR/CHAR columns.
      • Fixed a problem when locking the same table with both a READ and a WRITE lock.
      • Fixed problem with myisamchk and RAID tables.

      D.4.42 Changes in release 3.23.17

      • Fixed a bug in FIND_IN_SET() when the first argument was NULL.
      • Added table locks to Berkeley DB.
      • Fixed a bug with LEFT JOIN and ORDER BY where the first table had only one matching row.
      • Added 4 sample `my.cnf' example files in the `support-files' directory.
      • Fixed duplicated key problem when doing big GROUP BY operations. (This bug was probably introduced in 3.23.15.)
      • INNER JOIN の文法を ANSI SQL にマッチさせた.
      • NATURAL JOIN 構文を追加.
      • A lot of fixes in the BDB interface.
      • Added handling of --no-defaults and --defaults-file to safe_mysqld.sh and mysql_install_db.sh.
      • Fixed bug in reading compressed tables with many threads.
      • Fixed that USE INDEX works with PRIMARY keys.
      • Added BEGIN statement to start a transaction in AUTOCOMMIT mode.
      • シンボリックリンクを Windows 上でサポート.
      • Changed protocol to let client know if the server is in AUTOCOMMIT mode and if there is a pending transaction. If there is a pending transaction, the client library will give an error before reconnecting to the server to let the client know that the server did a rollback. The protocol is still backward-compatible with old clients.
      • KILL now works on a thread that is locked on a 'write' to a dead client.
      • Fixed memory leak in the replication slave thread.
      • Added new log-slave-updates option to mysqld, to allow daisy-chaining the slaves.
      • Fixed compile error on FreeBSD and other systems where pthread_t is not the same as int.
      • Fixed master shutdown aborting the slave thread.
      • Fixed a race condition in INSERT DELAYED code when doing ALTER TABLE.
      • Added deadlock detection sanity checks to INSERT DELAYED.

      D.4.43 Changes in release 3.23.16

      • Added SLAVE START and SLAVE STOP statements.
      • TYPE=QUICK オプションを CHECK と REPAIR に追加。
      • Fixed bug in REPAIR TABLE when the table was in use by other threads.
      • Added a thread cache to make it possible to debug MySQL with gdb when one does a lot of reconnects. This will also improve systems where you can't use persistent connections.
      • Berkeley DB インターフェースの多くを修正。
      • UPDATE IGNORE will not abort if an update results in a DUPLICATE_KEY error.
      • Put CREATE TEMPORARY TABLE commands in the update log.
      • Fixed bug in handling of masked IP numbers in the privilege tables.
      • Fixed bug with delay_key_write tables and CHECK TABLE.
      • Added replicate-do-db and replicate-ignore-db options to mysqld, to restrict which databases get replicated.
      • SQL_LOG_BIN オプションを追加。

      D.4.44 Changes in release 3.23.15 (2000-05-10; Beta)

      • To start mysqld as root one must now use the --user=root option.
      • Added interface to Berkeley DB. (This is not yet functional; play with it at your own risk!)
      • マスターとスレーブ間での複製機能を追加。
      • Fixed bug that other threads could steal a lock when a thread had a lock on a table and did a FLUSH TABLES command.
      • Added the slow_launch_time variable and the Slow_launch_threads status variable to mysqld. These can be examined with mysqladmin variables and mysqladmin extended-status.
      • Added functions INET_NTOA() and INET_ATON().
      • The default type of IF() now depends on the second and third arguments and not only on the second argument.
      • Fixed case when myisamchk could go into a loop when trying to repair a crashed table.
      • Don't write INSERT DELAYED to update log if SQL_LOG_UPDATE=0.
      • Fixed problem with REPLACE on HEAP tables.
      • Added possible character sets and time zone to SHOW VARIABLES output.
      • Fixed bug in locking code that could result in locking problems with concurrent inserts under high load.
      • Fixed a problem with DELETE of many rows on a table with compressed keys where MySQL scanned the index to find the rows.
      • Fixed problem with CHECK on table with deleted keyblocks.
      • Fixed a bug in reconnect (at the client side) where it didn't free memory properly in some contexts.
      • Fixed problems in update log when using LAST_INSERT_ID() to update a table with an AUTO_INCREMENT key.
      • Added NULLIF() function.
      • Fixed bug when using LOAD DATA INFILE on a table with BLOB/TEXT columns.
      • Optimised MyISAM to be faster when inserting keys in sorted order.
      • EXPLAIN SELECT ... now also prints out whether MySQL needs to create a temporary table or use file sorting when resolving the SELECT.
      • Added optimization to skip ORDER BY parts where the part is a constant expression in the WHERE part. Indexes can now be used even if the ORDER BY doesn't match the index exactly, as long as all the unused index parts and all the extra ORDER BY columns are constants in the WHERE clause. 「5.4.3 MySQL はどのようにインデックスを使用するか？」節参照.
      • UPDATE and DELETE on a whole unique key in the WHERE part are now faster than before.
      • Changed RAID_CHUNKSIZE to be in 1024-byte increments.
      • Fixed core dump in LOAD_FILE(NULL).

      D.4.45 Changes in release 3.23.14 (2000-04-10)

      • Added mysql_real_escape_string() function to the MySQL C API.
      • Fixed a bug in CONCAT() where one of the arguments was a function that returned a modified argument.
      • myisamchk の致命的なバグを修正した。 このバグはインデックスファイル中の ヘッダーを、テーブルをチェックしているだけなのにもかかわらず、更新していた。 This confused the mysqld daemon if it updated the same table at the same time. Now the status in the index file is only updated if one uses --update-state. With older myisamchk versions you shoul use --read-only when only checking tables, if there is the slightest chance that the mysqld server is working on the table at the same time!
      • Fixed that DROP TABLE is logged in the update log.
      • Fixed problem when searching on DECIMAL() key field where the column data contained leading zeros.
      • auto_increment が最初のキーでない場合の myisamchk のバグを修正。
      • Allow DATETIME in ISO8601 format: 2000-03-12T12:00:00
      • 動的キャラクタセット。 １個の mysqld バイナリで、多くの違う キャラクタセットを扱えるようになった。 (mysqld スタート時に指定できます).
      • REPAIR TABLE コマンドを追加。
      • mysql_thread_safe() C API 関数を追加。
      • UMASK_DIR 環境変数を追加。
      • CONNECTION_ID() 関数を追加
      • When using = on BLOB or VARCHAR BINARY keys, where only a part of the column was indexed, the whole column of the result row wasn't compared.
      • sjis キャラクターセットの ORDER BY の問題を修正
      • When running in ANSI mode, don't allow columns to be used that aren't in the GROUP BY part.

      D.4.46 Changes in release 3.23.13

      • Fixed problem when doing locks on the same table more than 2 times in the same LOCK TABLE command; this fixed the problem one got when running the test-ATIS test with --fast or --check-only-changed.
      • SQL_BUFFER_RESULT オプションを SELECT に追加
      • Removed end space from double/float numbers in results from temporary tables.
      • CHECK TABLE コマンドの追加。
      • Added changes for MyISAM in 3.23.12 that didn't get into the source distribution because of CVS problems.
      • Fixed bug so that mysqladmin shutdown will wait for the local server to close down.
      • Fixed a possible endless loop when calculating timestamp.
      • Added print_defaults program to the `.rpm' files. Removed mysqlbug from the client `.rpm' file.

      D.4.47 Changes in release 3.23.12 (07 Mar 2000)

      • Fixed bug in MyISAM involving REPLACE ... SELECT ... which could give a corrupted table.
      • Fixed bug in myisamchk where it incorrectly reset the AUTO_INCREMENT value.
      • Linux Alpha 用に多くのパッチを追加. MySQL now appears to be relatively stable on Alpha.
      • 重複したレコードを速く見つけるためのハッシュ化されたキーを使用するために、 HEAP 一時テーブル上の DISTINCT を変更した。 This mostly concerns queries of type SELECT DISTINCT ... GROUP BY .... This fixes a problem where not all duplicates were removed in queries of the above type. 新しく追加したコードは、とても速い。
      • MacOS X で MySQL をコンパイルできるようになるパッチの追加
      • オプション IF NOT EXISTS を CREATE DATABASE に追加.
      • 多くのデータベースを同時にダンプできるように、 --all-databases と --databases オプションを mysqldump に追加。
      • MyISAM 型テーブル中の圧縮した DECIMAL() インデックスのバグを修正した。
      • 0 を timestamp に保存したときのバグを修正した。
      • ローカルの接続で mysqladmin shutdown を実行した場合に、mysqladmin は 終了前に pidfile が無くなるまで待つようになった。
      • いくつかの COUNT(DISTINCT ...) クエリでコアを吐いたのを修正した。
      • Fixed that myisamchk works properly with RAID tables.
      • Fixed problem with LEFT JOIN and key_field IS NULL.
      • Fixed bug in net_clear() which could give the error Aborted connection in the MySQL clients.
      • Added options USE INDEX (key_list) and IGNORE INDEX (key_list) as parameters in SELECT.
      • DELETE and RENAME should now work on RAID tables.

      D.4.48 Changes in release 3.23.11

      • ALTER TABLEL tbl_name ADD (field_list) 文を許可した。
      • Fixed problem with optimiser that could sometimes use incorrect keys.
      • GRANT/REVOKE ALL PRIVILEGES が GRANT OPTION に影響しなかったのを修正。
      • Removed extra `)' from the output of SHOW GRANTS.
      • Fixed problem when storing numbers in timestamps.
      • Fix problem with timezones that have half hour offsets.
      • CREATE 文での UNIQUE INDEX の使用を許可。
      • mysqlhotcopy - ローカルの MySQL データベースをバックアップする ツール。 By Tim Bunce.
      • 新しい mysqlaccess. Thanks to Steve Harvey for this.
      • --i-am-a-dummy と --safe-updates オプションを mysql に追加。
      • select_limit と max_join_size 変数を mysql に追加。
      • SQL の変数を追加： SQL_MAX_JOIN_SIZE と SQL_SAFE_UPDATES.
      • Added READ LOCAL lock that doesn't lock the table for concurrent inserts. (This is used by mysqldump.)
      • Changed that LOCK TABLES ... READ doesn't anymore allow concurrent inserts.
      • オプション --skip-delay-key-write を mysqld に追加。
      • Fixed security problem in the protocol regarding password checking.
      • _rowid can now be used as an alias for an integer type unique indexed column.
      • Added back blocking of SIGPIPE when compiling with --thread-safe-clients to make things safe for old clients.

      D.4.49 Changes in release 3.23.10

      • Fixed bug in 3.23.9 where memory wasn't properly freed when using LOCK TABLES.

      D.4.50 Changes in release 3.23.9

      • Fixed problem that affected queries that did arithmetic on group functions.
      • Fixed problem with timestamps and INSERT DELAYED.
      • Fixed that date_col BETWEEN const_date AND const_date works.
      • Fixed problem when only changing a 0 to NULL in a table with BLOB/TEXT columns.
      • Fixed bug in range optimizer when using many key parts and or on the middle key parts: WHERE K1=1 and K3=2 and (K2=2 and K4=4 or K2=3 and K4=5)
      • source コマンドを mysql に追加。 これは mysql クライアント内 で、バッチファイルを読むことができる。 Original patch by Matthew Vanecek.
      • WITH GRANT OPTION オプションの致命的なバグを修正
      • Don't give an unnecessary GRANT error when using tables from many databases in the same query.
      • Added VIO wrapper (needed for SSL support; by Andrei Errapart and Tnu Samuel).
      • Fixed optimizer problem on SELECT when using many overlapping indexes. MySQL should now be able to choose keys even better when there are many keys to choose from.
      • Changed optimizer to prefer a range key instead of a ref key when the range key can uses more columns than the ref key (which only can use columns with =). For example, the following type of queries should now be faster: SELECT * from key_part_1=const and key_part_2 > const2
      • Fixed bug that a change of all VARCHAR columns to CHAR columns didn't change row type from dynamic to fixed.
      • Disabled floating-point exceptions for FreeBSD to fix core dump when doing SELECT FLOOR(POW(2,63)).
      • mysqld の起動オプション --delay-key-write を --delay-key-write-for-all-tables に変更
      • Added read-next-on-key to HEAP tables. This should fix all problems with HEAP tables when using non-UNIQUE keys.
      • 変数のデフォルトを表示するオプションをクライアントに追加
      • mysqld に --log-slow-queries を追加。 これは時間のかかった 全てのクエリを別のログファイルに記録する。どのくらい時間がかかったかが記される
      • WHERE key_column=RAND(...) を行ったときコアを吐くバグを修正
      • Fixed optimisation bug in SELECT ... LEFT JOIN ... key_col IS NULL, when key_col could contain NULL values.
      • Fixed problem with 8-bit characters as separators in LOAD DATA INFILE.

      D.4.51 Changes in release 3.23.8 (02 Jan 2000)

      • 8G より大きなインデックスファイルを扱った場合の問題を修正。
      • NetBSD 用の最新の mit-pthread のパッチを追加。
      • タイムゾーン < GMT - 11 の場合の問題を修正。
      • NISAM 中のパックされたキーの削除時のバグを修正。
      • いくつか ORDER BY ... DESC クエリを実行した際の ISAM の問題を修正。
      • Fixed bug when doing a join on a text key which didn't covert the whole key.
      • オプション --delay-key-write が delayed key writing を有効にしていなかったのを修正。
      • Fixed update of TEXT column which involved only case changes.
      • Fixed that INSERT DELAYED doesn't update timestamps that are given.
      • YEARWEEK() 関数の追加と、x, X, v, V オプションの DATE_FORMAT() への追加。
      • Fixed problem with MAX(indexed_column) and HEAP tables.
      • Fixed problem with BLOB NULL keys and LIKE "prefix%".
      • Fixed problem with MyISAM and fixed-length rows < 5 bytes.
      • Fixed problem that could cause MySQL to touch freed memory when doing very complicated GROUP BY queries.
      • Fixed core dump if you got a crashed table where an ENUM field value was too big.

      D.4.52 Changes in release 3.23.7 (10 Dec 1999)

      • Linux環境下において、pthread_mutex_timedwait の問題を避けるようにした。 この関数は INSERT DELAYED で使用されていた。 「2.6.1 Linux Notes (All Linux Versions)」節参照.
      • Fixed that one will get at 'disk full' error message if one gets disk full when doing sorting (instead of waiting until we got more disk space).
      • MyISAM で、キーが 250 文字を超えた場合のバグを修正。
      • MyISAM において、他のスレッドが読んでいるテーブルに対し、 他のスレッドが INSERT を同時に行うことができるようになった。
      • Added max_write_lock_count variable to mysqld to force a READ lock after a certain number of WRITE locks.
      • Inverted flag delay_key_write on show variables.
      • concurrency 変数を thread_concurrency に改名。
      • 以下の関数がマルチバイト・セーフになった： LOCATE(substr,str), POSITION(substr IN str), LOCATE(substr,str,pos), INSTR(str,substr), LEFT(str,len), RIGHT(str,len), SUBSTRING(str,pos,len), SUBSTRING(str FROM pos FOR len), MID(str,pos,len), SUBSTRING(str,pos), SUBSTRING(str FROM pos), SUBSTRING_INDEX(str,delim,count), RTRIM(str), TRIM([[BOTH | TRAILING] [remstr] FROM] str), REPLACE(str,from_str,to_str), REVERSE(str), INSERT(str,pos,len,newstr), LCASE(str), LOWER(str), UCASE(str) and UPPER(str); patch by Wei He.
      • Fix core dump when releasing a lock from a non-existent table.
      • Remove locks on tables before starting to remove duplicates.
      • FULL オプションを SHOW PROCESSLIST に追加。
      • --verbose オプションを mysqladmin に追加。
      • HEAP の MyISAM への自動変換時のバグを修正。
      • HEAP テーブルに対して、insert + delete + insert + scan table を行った際の バグを修正。
      • Alpha プラットフォーム上での、REPLACE() と LOAD DATA INFILE のバグを修正。
      • mysqld 変数に interactive_timeout を追加.
      • mysql_data_seek() の引数を ulong から ulonglong に 変更.

      D.4.53 Changes in release 3.23.6

      • mysqld に -O lower_case_table_names={0|1} オプションを追加。 これはテーブル名を強制的に小文字にします。
      • SELECT ... INTO DUMPFILE 追加。
      • mysqld に --ansi オプションを追加。 これはいくつかの関数を ANSI SQL 互換にします。
      • Temporary table names now start with #sql.
      • Added quoting of identifiers with ` (" in --ansi mode).
      • Changed to use snprintf() when printing floats to avoid some buffer overflows on FreeBSD.
      • FreeBSD 上で、FLOOR() をオーバーフローセーフにした。
      • --quote-names オプションを mysqldump に追加
      • Fixed bug that one could make a part of a PRIMARY KEY NOT NULL.
      • Fixed encrypt() to be thread-safe and not reuse buffer.
      • MyODBC の mysql_odbc_escape_string() 関数が、big5 をサポートした。
      • Rewrote the storage engine to use classes. This introduces a lot of new code, but will make table handling faster and better.
      • ユーザー定義変数のパッチ(Sashaによる)を追加。
      • Changed that FLOAT and DOUBLE (without any length modifiers) no longer are fixed decimal point numbers.
      • FLOAT(X) の意味を変更: X <=24 ならば、これは FLOAT と同じで、 24 < X <= 53 であるならば DOUBLE と同じになります。
      • DECIMAL(X) は DECIMAL(X,0) のエイリアスになりました。 また DECIMAL は DECIMAL(10,0) のエイリアスになりました。 The same goes for NUMERIC.
      • ROW_FORMAT={default | dynamic | fixed | compressed} オプションを CREATE_TABLE に追加.
      • DELETE FROM table_name が一時テーブルで動かなかった。
      • CHAR_LENGTH() 関数をマルチバイトセーフに変更
      • ORD(string) 関数の追加.

      D.4.54 Changes in release 3.23.5 (20 Oct 1999)

      • 新しいデータハンドリング中のいくつかの Y2K 問題を修正。
      • SELECT DISTINCT ... ORDER BY RAND() の問題を修正。
      • Sergei A. Golubchik による MyISAM のレベルでのテキストサーチのパッチを追加
      • キー無しでfull JOIN を使用した際のキャッシュオーバーフローの問題を修正。
      • いくつかの configure の問題を修正。
      • Some small changes to make parsing faster.
      • Adding a column after the last field with ALTER TABLE didn't work.
      • 2つのキー中でauto_incrementフィールドを使用したときの問題を修正。
      • MyISAM で auto_increment をサブパートとして使用できるようになった： CREATE TABLE foo (a INT NOT NULL AUTO_INCREMENT, b CHAR(5), PRIMARY KEY (b,a))
      • Fixed bug in MyISAM with packed char keys that could be NULL.
      • フィールド名を CREATE TABLE table_name SELECT ... 時にとした場合、動かなかった。
      • Allow use of NATIONAL and NCHAR when defining character columns. This is the same as not using BINARY.
      • NULL のフィールドを PRIMARY KEY ( UNIQUE キー) には 許さなくなった。
      • Clear LAST_INSERT_ID() if one uses this in ODBC: WHERE auto_increment_column IS NULL. This seems to fix some problems
      • WHERE auto_increment_column IS NULL を使用して最後にレコードが挿入された後に、 SET SQL_AUTO_IS_NULL=0|1 はサーチのハンドリングの on/off になった。
      • Added new variable concurrency to mysqld for Solaris.
      • --relative オプションを mysqladmin に追加。 これは extended-status で変更のモニターをする場合、より便利になった。
      • 空のテーブルに対して COUNT(DISTINCT...) を使用した際のバグを修正。
      • 中国語のキャラクターセット GBK を追加。
      • LOAD DATA INFILE を BLOB フィールドに使用した際の問題を修正。
      • 論理演算子 ~ (negation) を追加。
      • UDF 関数での問題を修正。

      D.4.55 Changes in release 3.23.4 (28 Sep 1999)

      • DATETIME 型を TIME フィールドに挿入するとき、'day' を 保存しようと試みなくなった。
      • low endian のマシンで float/double の保存の問題を修正。 (これは SUM() に影響する.)
      • TCP/IP 接続の connect timeout を追加。
      • インデックス上で、 NULL 値を持つかもしれないものに LIKE "%" した際の問題を修正。
      • REVOKE ALL PRIVILEGES が全ての権限を取り消していなかったのを修正。
      • オリジナルのテーブル名と同じ名前で一時テーブルを作れるようにした。
      • データベースへの権限をあるユーザーに与えた際、 そのユーザーは他のユーザーに権限を与えることが出来なかった。
      • 新コマンド： SHOW GRANTS FOR user (by Sinisa).
      • 新 date_add syntax: date/datetime + INTERVAL # interval_type. By Joshua Chamas.
      • LOAD DATA REPLACE の権限のチェックを修正。
      • Solaris 2.7 上での、壊れた include ファイルを自動修正。
      • big file system を検出する際のいくつかの configure の問題を修正。
      • REGEXP はケース非依存になった。もしバイナリ文字でない場合は。

      D.4.56 Changes in release 3.23.3

      • NetBSD 上での MIT-pthreads パッチを追加。
      • MyISAM 中の range bug を修正。
      • ORDER BY のデフォルトが再び ASC になった。
      • LIMIT を UPDATE に追加。
      • 新クライアント関数： mysql_change_user().
      • SHOW VARIABLES にキャラクターセットを追加。
      • --[whitespace] コメントをサポートした。
      • Allow INSERT into tbl_name VALUES (), that is, you may now specify an empty value list to insert a row in which each column is set to its default value.
      • Changed SUBSTRING(text FROM pos) to conform to ANSI SQL. (Before this construct returned the rightmost 'pos' characters).
      • いくつかのシステム上で GROUP BY をともなった SUM() は 0 を返すようになった。
      • SHOW TABLE STATUS の出力を変更。
      • DELAY_KEY_WRITE オプションを CREATE TABLE に追加。
      • AUTO_INCREMENT をいかなるキーの部分に使用できるようにした。
      • YEAR(NOW()) , YEAR(CURDATE()) の問題を修正。
      • Added CASE construct.
      • 新刊数 COALESCE().

      D.4.57 Changes in release 3.23.2 (1999-08-09)

      • Fixed range optimizer bug: SELECT * FROM table_name WHERE key_part1 >= const AND (key_part2 = const OR key_part2 = const). The bug was that some rows could be duplicated in the result.
      • Running myisamchk without -a updated the index distribution incorrectly.
      • SET SQL_LOW_PRIORITY_UPDATES=1 was causing a parse error.
      • WHERE 節に使用されているインデックスフィールドを更新できるようになった： UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100
      • Date handling should now be a bit faster.
      • Added handling of fuzzy dates (dates where day or month is 0), such as '1999-01-00'.
      • Fixed optimization of SELECT ... WHERE key_part1=const1 AND key_part_2=const2 AND key_part1=const4 AND key_part2=const4; indextype should be range instead of ref.
      • Linux Alpha 上で egcs 1.1.2 optimizer のバグ(BLOB 使用時)を修正。
      • Fixed problem with LOCK TABLES combined with DELETE FROM table.
      • MyISAM テーブルは NULL 値と BLOB/TEXT フィールドにキーを許すようになった。
      • 以下のJOINがより速くなった： SELECT ... FROM t1 LEFT JOIN t2 ON ... WHERE t2.not_null_column IS NULL.
      • ORDER BY and GROUP BY can be done on functions.
      • Changed handling of 'const_item' to allow handling of ORDER BY RAND().
      • WHERE key_column = function でインデックスが使用されるようになった。
      • 例えフィールドが全く同じにパックされていなくても、 WHERE key_column = column_name でインデックスが使用されるようになった。
      • WHERE column_name IS NULL でインデックスが使用されるようになった。
      • Changed heap tables to be stored in low_byte_first order (to make it easy to convert to MyISAM tables)
      • Automatic change of HEAP temporary tables to MyISAM tables in case of 'table is full' errors.
      • --init-file=file_name オプションを mysqld に追加。
      • Added COUNT(DISTINCT value, [value, ...]).
      • CREATE TEMPORARY TABLE now creates a temporary table, in its own namespace, that is automatically deleted if connection is dropped.
      • 新予約語 (CASE を要求): CASE, THEN, WHEN, ELSE and END.
      • 新関数 EXPORT_SET() , MD5().
      • GB2312 中国語キャラクターセットをサポート。

      D.4.58 Changes in release 3.23.1

      • いくつかのコンパイル問題を修正した。

      D.4.59 Changes in release 3.23.0 (1999-06-05; Alpha)

      • 多くの新しい特徴を備えた新しい storage engine ライブラリ( MyISAM )。 「7.1 MyISAM テーブル (3.23.0以上)」節参照.
      • メモリー内に HEAP テーブルを作成できるようになりました。 これは探索がとても速いです。
      • 大容量ファイルをサポートしているOS上で、大ファイル (63 bit) のサポート。
      • 新しい関数 LOAD_FILE(filename) 。 これはファイルの中身を文字列値として読みます。
      • 新しい演算子 <=> 。 これは、 = のように振る舞いますが、 もし両辺の引数が NULL なら、真を返します。 これはテーブル間の変更の比較に役立ちます。
      • ODBC 3.0 EXTRACT(interval FROM datetime) 関数の追加。
      • FLOAT(X) フィールドは、保存した値を丸めません。 これは検索されたときに 科学表記 (1.0 E+10) になるかもしれません。
      • REPLACE が前よりも速くなった。
      • LIKE 文字比較を = のよに振る舞うように変更； これは 'e' LIKE ''e' が真になるということです。 (if the line doesn't display correctly, the latter 'e' means a French 'e' with a dot above)
      • SHOW TABLE STATUS はテーブルについての情報を多く出すようになりました。
      • LIKE を SHOW STATUS コマンドに追加。
      • SHOW COLUMNS に Privileges 項目を追加。
      • SHOW INDEX に packed と comment 項目を追加。
      • テーブルへのコメントを追加。 ( CREATE TABLE ... COMMENT "xxx").
      • UNIQUE を次のように追加： CREATE TABLE table_name (col int not null UNIQUE)
      • 新 create 構文： CREATE TABLE table_name SELECT ...
      • 新 create 構文： CREATE TABLE IF NOT EXISTS ...
      • CHAR(0) フィールドの作成を許可した。
      • DATE_FORMAT() は、フォーマット文字の前に `%' が必要になった。
      • DELAYED が予約語になった。 (sorry about that :( ).
      • プロセジャーの例を追加： analyse, file: `sql_analyse.c'. これはクエリのデータについて説明します。 以下の様にしてみてください： 
        SELECT ... FROM ... WHERE ... PROCEDURE ANALYSE([max elements,[max memory]])
        この プロセジャーは、テーブルのデータをチェックしたい時に、とても役立ちます！
      • BINARY cast to force a string to be compared case sensitively.
      • --skip-show-database オプションを mysqld に追加。
      • BLOB/TEXT フィールドにおいて、 UPDATE された レコードをチェックできるようになりました。
      • INNER JOIN の追加。 注意: INNER は予約語になりました！
      • MySQL テーブルのホストにネットマスクをサポートした。 IP/NETMASK として、ネットマスクを指定できます。
      • If you compare a NOT NULL DATE/DATETIME column with IS NULL, this is changed to a compare against 0 to satisfy some ODBC applications. (By shreeve@uci.edu).
      • NULL IN (...) は 0 ではなく NULL を返します。 これは null_column NOT IN (...) が NULL 値にマッチしないのを確実にします。
      • TIME フィールド中に、浮動小数点の値を入れるのを修正。
      • Changed parsing of TIME strings to be more strict. Now the fractional second part is detected (and currently skipped). The following formats are supported:
        [[DAYS] [H]H:]MM:]SS[.fraction]
        [[[[[H]H]H]H]MM]SS[.fraction]
      • Detect (and ignore) second fraction part from DATETIME.
      • LOW_PRIORITY 属性を LOAD DATA INFILE に追加。
      • デフォルトのインデックス名を、フィールドの名前と同じケースにした。
      • デフォルトの接続数を 100 に変更。
      • LOAD DATA INFILE 時に、より大きなバッファを使用するようにした。
      • DECIMAL(x,y) は ANSI SQL に従って動作するようになった。
      • Added aggregate UDF functions. Thanks to Andreas F. Bobak bobak@relog.ch for this!
      • LAST_INSERT_ID() is now updated for INSERT INTO ... SELECT.
      • Some small changes to the join table optimizer to make some joins faster.
      • SELECT DISTINCT が凄く速くなった； これは MyISAM の新しい UNIQUE を使用します。 MySQL バージョン 3.22 と一つ違う点は、 DISTINCT の出力が ソートされないという事です。
      • 全ての C クライアント API が、共有ライブラリを柔軟に作成するため、 マクロから関数になりました。 このため、 mysql_num_fields() を MYSQL ととしてコールできず、この代わりに mysql_field_count() を 使用しなくてはなりません。
      • LIBEWRAP の追加; Patch by Henning P. Schmiedehausen.
      • Don't allow AUTO_INCREMENT for other than numerical columns.
      • AUTO_INCREMENT の使用は、フィールドを自動的に NOT NULL にします。
      • Show NULL as the default value for AUTO_INCREMENT columns.
      • SQL_BIG_RESULT の追加; SQL_SMALL_RESULT がデフォルトになりました。
      • Added a shared library RPM. This enhancement was contributed by David Fox (dsfox@cogsci.ucsd.edu).
      • --enable-large-files/--disable-large-files スイッチを configure に 追加。 See `configure.in' for some systems where this is automatically turned off because of broken implementations.
      • readline 4.0 にアップグレード
      • 新しい CREATE TABLE オプション： PACK_KEYS と CHECKSUM.
      • mysqld オプションに --default-table-type を追加。

      D.5 Changes in release 3.22.x (Old; discontinued)

      3.22 は 3.21 より早く、より安全なコードをもち、たくさんの新しい機能が盛り込まれています。 これらの変更を 3.21 に行わないのは、3.21 の安定度を保つためにはとても多くの変更が必要とされるからです。 これらの変更はメジャーバージョンの変更ではないので、簡単に障害もなく 3.22 にアップグレードができます。 「2.5.4 バージョン 3.21 から バージョン 3.22 へのアップグレード」節参照.

      3.22 は新しい DBD-mysql (1.20xx) ドライバーのみを新しい接続プロトコルに対して使用します！

      D.5.1 Changes in release 3.22.35

      • Fixed problem with STD().
      • Merged changes from the newest ISAM library from 3.23.
      • Fixed problem with INSERT DELAYED.
      • Fixed a bug core dump when using a LEFT JOIN/STRAIGHT_JOIN on a table with only one row.

      D.5.2 Changes in release 3.22.34

      • Fixed problem with GROUP BY on TINYBLOB columns; This caused bugzilla to not show rows in some queries.
      • Had to do total recompile of the Windows binary version as VC++ didn't compile all relevant files for 3.22.33 :(

      D.5.3 Changes in release 3.22.33

      • Fixed problems in Windows when locking tables with LOCK TABLE
      • Quicker kill of SELECT DISTINCT queries.

      D.5.4 Changes in release 3.22.32 (2000-02-14)

      • 数値を timestamps に保存する際の問題を修正した。
      • Fix problem with timezones that have half hour offsets.
      • mysqlhotcopy - ローカルの MySQL データベースをコピーする ツール. By Tim Bunce.
      • mysqlaccess が新しくなった. Thanks to Steve Harvey for this.
      • Fixed security problem in the protocol regarding password checking.
      • Fixed problem that affected queries that did arithmetic on GROUP functions.
      • Fixed a bug in the ISAM code when deleting rows on tables with packed indexes.

      D.5.5 Changes in release 3.22.31

      • Windows バージョンでのいくつかの小さなバグ修正

      D.5.6 Changes in release 3.22.30 (2000-01-12 stable)

      • Fixed optimizer problem on SELECT when using many overlapping indexes.
      • Disabled floating-point exceptions for FreeBSD to fix core dump when doing SELECT FLOOR(POW(2,63)).
      • Added print of default arguments options to all clients.
      • WITH GRANT OPTION オプションの致命的なバグを修正.
      • Fixed non-critical Y2K problem when writing short date to log files.

      D.5.7 Changes in release 3.22.29 (02 Jan 2000)

      • Upgraded the configure and include files to match the latest 3.23 version. This should increase portability and make it easier to build shared libraries.
      • NetBSD 用の最新の mit-pthread のパッチを追加。
      • タイムゾーン < GMT - 11 の場合の問題を修正。
      • NISAM 中のパックされたキーの削除時のバグを修正。
      • Fixed problem that could cause MySQL to touch freed memory when doing very complicated GROUP BY queries.
      • Fixed core dump if you got a crashed table where an ENUM field value was too big.
      • Added mysqlshutdown.exe and mysqlwatch.exe to the Windows distribution.
      • キーに対して ORDER BY を行ったときの問題を修正
      • Fixed that INSERT DELAYED doesn't update timestamps that are given.

      D.5.8 Changes in release 3.22.28 (20 Oct 1999)

      • Fixed problem with LEFT JOIN and COUNT() on a column which was declared NULL + and it had a DEFAULT value.
      • CONCAT() をある WHERE 節で使用した際にコア・ダンプする問題を修正した。
      • Fixed problem with AVG() and STD() with NULL values.

      D.5.9 Changes in release 3.22.27

      • `my_ctype.h' 中の、他のキャラクターセットのプロトタイプを修正。
      • configure 中の、大ファイルシステムを検出する部分の問題を修正。
      • 大きなBLOBフィールドをソートしたときのバグを修正。
      • ROUND() will now work on Windows.

      D.5.10 Changes in release 3.22.26 (16 Sep 1999)

      • 空の BLOB/TEXT フィールドを REVERSE() した際にコアダンプしたのを修正。
      • /*! */ バージョン番号 を拡張した
      • Changed SUBSTRING(text FROM pos) to conform to ANSI SQL. (Before this construct returned the rightmost pos characters.)
      • Fixed problem with LOCK TABLES combined with DELETE FROM table
      • INSERT ... SELECT が SQL_BIG_TABLES を使用していなかったのを修正。
      • SET SQL_LOW_PRIORITY_UPDATES=# が動いてなかった。
      • 許可を GRANT ... IDENTIFIED BY で変更しても直にパスワードが 反映されなかったのを修正。
      • 以下の最適化のバグを修正： SELECT * FROM table_name WHERE key_part1 >= const AND (key_part2 = const OR key_part2 = const)
      • Fixed bug in compression key handling in ISAM.

      D.5.11 Changes in release 3.22.25

      • インストール時の小さな問題を修正。

      D.5.12 Changes in release 3.22.24 (1999-07-05)

      • DATA は予約語でなくなった。
      • たった１レコードしかないテーブルの最適化のバグを修正。
      • LOCK TABLES table_name READ; FLUSH TABLES; を使用した際のバグ修正。
      • HP-UX のパッチを適用。
      • isamchk が Windows 上で動くようになった。
      • Changed `configure' to not use big file handling on Linux as this crashes some RedHat 6.0 systems

      D.5.13 Changes in release 3.22.23 (08 Jun 1999)

      • Autoconf 2.13, Automake 1.4, libtool 1.3.2 を使用するようにアップグレード。
      • Better support for SCO in configure.
      • Added option --defaults-file=### to option file handling to force use of only one specific option file.
      • MySQL バージョン 3.23 のキーワードを無視するように CREATE 構文を拡張した。
      • LOCK TABLES でロックされているテーブルに INSERT DELAYED を 使用した際の、デッドロックの問題を修正。
      • 他のスレッドにロックされているテーブルに DROP TABLE を使用した際の 問題を修正。
      • GRANT/REVOKE コマンドを update log に追加。
      • 新しいエラー項目を検出するように isamchk を修正。
      • NATURAL LEFT JOIN のバグを修正。

      D.5.14 Changes in release 3.22.22 (30 Apr 1999)

      • mysql_init() の後に直接 mysql_close() を読んだときの問題を修正。 (C API)
      • Better client error message when you can't open socket.
      • 新しいdelayed_insert スレッドが作成できなかったときの delayed_insert_thread 数の表示を修正。
      • CONCAT() の引数を多くした場合のバグを修正。
      • DEC 3.2 と SCO のパッチの追加。
      • NT のサービスとして MySQL をインストールした際の パスの問題を修正。
      • MySQL-Windows は VC++ 6.0 でコンパイルされるようになった。 (VC++ 5.0 のかわりに)
      • MySQL-Windows の新しいインストーラー

      D.5.15 Changes in release 3.22.21

      • テーブルが他のスレッドにロックされたときの、DELETE FROM TABLE の 問題を修正。
      • Fixed bug in LEFT JOIN involving empty tables.
      • mysql.db フィールドを char(32) から char(60) に変更。
      • MODIFY と DELAYED は予約語でなくなった。
      • TIME フィールドに日にちを入れようとしたときのバグを修正。
      • GRANT コマンドで新しい MySQL ユーザーを登録した後に Host '...' is not allowed to connect to this MySQL server となる問題を修正。
      • Linux 上で TCP_NODELAY を使用するように変更。 (これは TCP/IP 接続を速くします)

      D.5.16 Changes in release 3.22.20 (1999-03-18)

      • Fixed STD() for big tables when result should be 0.
      • いくつかのOS でupdate log が改行を入れていなかったのを修正。
      • INSERT DELAYED had some garbage at end in the update log.

      D.5.17 Changes in release 3.22.19 (1999-03-02)

      • mysql_install_db のバグ修正。 (from 3.22.17).
      • デフォルトのキーキャッシュを 8M に変更。
      • BLOB フィールドで一時テーブルが必要とされるクエリの問題を修正。

      D.5.18 Changes in release 3.22.18

      • Linux上で、3.22.17の致命的な問題の修正； shutdown 後、全ての スレッドが確実に死ななかった。
      • -O flush_time=# オプションを mysqld に追加。 This is mostly useful on Windows and tells how often MySQL should close all unused tables and flush all updated tables to disk.
      • VARCHAR フィールドと CHAR を比較した際にキーを効果的に 使用していなかったのを修正。

      D.5.19 Changes in release 3.22.17

      • --log-update を使用したときとデフォルトのデータベースを指定しないで 接続したときのコアダンプを修正した。
      • いくつかの configure と移植性の問題を修正した。
      • Using LEFT JOIN on tables that had circular dependencies caused mysqld to hang forever.

      D.5.20 Changes in release 3.22.16 (1999-02-07)

      • mysqladmin processlist could kill the server if a new user logged in.
      • DELETE FROM table_name WHERE key_column=column_name が マッチする行を1行も見つけれないのを修正
      • DATE_ADD(column, ...) が動かないのを修正
      • INSERT DELAYED could deadlock with status 'upgrading lock'
      • 2文字以上のソルトが使用できるように、ENCRYPT() を拡張。
      • longlong2str は以前よりかなり速くなった。Intel x86 用に このコードは最適化されたアセンブラで書き直した
      • ALTER TABLE に MODIFY キーワードを追加

      D.5.21 Changes in release 3.22.15

      • GRANT を IDENTIFIED BY と共に使用した際、権限情報がフラッシュされるまで 有効にならない
      • Name change of some variables in SHOW STATUS.
      • Fixed problem with ORDER BY with 'only index' optimization when there were multiple key definitions for a used column.
      • DATE and DATETIME columns are now up to 5 times faster than before.
      • INSERT DELAYED can be used to let the client do other things while the server inserts rows into a table.
      • もし2つの違うデータベースのテーブルを使用した場合、 LEFT JOIN USING (col1,col2) が動作しなかった
      • LOAD DATA LOCAL INFILE がファイルがないための理由で UNIX では動作しなかった
      • とても短い行(<4バイト)しかない VARCHAR/BLOB での問題の修正； error 127 がこの行を消去する場合に起きる可能性があった
      • Updating BLOB/TEXT through formulas didn't work for short (< 256 char) strings.
      • 新しいホスト上で GRANT を実行した場合、そのホストからの最初のコネクションで mysqld が死ぬ可能性があった
      • エイリアス名と同じ項目名を ORDER BY で使用する場合のバグを修正 name as an alias.
      • Added BENCHMARK(loop_count,expression) function to time expressions.

      D.5.22 Changes in release 3.22.14

      • シェルスクリプトからの起動のために、mysqld の引数がない場合を許可した。
      • Setting a TIMESTAMP column to NULL didn't record the timestamp value in the update log.
      • Fixed lock handler bug when one did INSERT INTO TABLE ... SELECT ... GROUP BY.
      • Added a patch for localtime_r() on Windows so that it will not crash anymore if your date is > 2039, but instead will return a time of all zero.
      • Names for user-defined functions are no longer case-sensitive.
      • Added escape of ^Z (ASCII 26) to \Z as ^Z doesn't work with pipes on Windows.
      • 将来の MySQL リリースのために、mysql_fix_privileges は、 UDF のサポートのために、新しい項目を mysql.func に追加する。 ( type enum ('function','aggregate') NOT NULL が追加された )

      D.5.23 Changes in release 3.22.13 (1998-12-17)

      • Saving NOW(), CURDATE() or CURTIME() directly in a column didn't work.
      • WHERE 節が無い場合、SELECT COUNT(*) ... LEFT JOIN ... が動かなかった
      • UnixWare 7.0.x で MySQL をコンフィグできるように `config.guess' を更新 UnixWare 7.0.x.
      • Changed the implementation of pthread_cond() on the Windows version. get_lock() now correctly times out on Windows!

      D.5.24 Changes in release 3.22.12 (1998-12-10)

      • WHERE 節で DATE_ADD() と DATE_SUB() を使用した際の問題を修正
      • GRANT ... TO user IDENTIFIED BY 'password' 構文でパスワードをセットできるようにした
      • 多くのテーブルを SELECT して GRANT を確認する際のバグを修正
      • RPM 配布での mysql_fix_privilege_tables ファイルの追加。 これはクライアントパッケージに含んだため、デフォルトでは起動されない。
      • SQL_SMALL_RESULT オプションを SELECT に追加。 これは強制的に速い一時テーブルを使用する。 結果が小さいとわかっている場合に使用すると有効。
      • 小数点をつけなくても実数が使用できるようにした
      • DATE_ADD/DATE_SUB() の結果、十分な日数を得られない場合、 日数を月の最大日にするようにした。
      • GRANT がカラムをケース非依存で比較していたのを修正
      • ある構文の組み合わせで ALTER TABLE が core をはくバグが `sql_list.h' にあったのでこれを修正
      • The hostname in user@hostname can now include `.' and `-' without quotes in the context of the GRANT, REVOKE and SET PASSWORD FOR ... statements.
      • 大きな一時ファイルを必要とするテーブルへの isamchk を修正

      D.5.25 Changes in release 3.22.11 (1998-11-25)

      • 重要: 3.22.11にアップグレードする場合、必ず mysql_fix_privilege_tables スクリプトを実行しなくてはなりません！ これは新しい GRANT システムのために実行します。 もしこれを行わなければ、ALTER TABLE や CREATE INDEX, DROP INDEX を 実行しようとすると Access denied になります。
      • テーブル、カラムごとにユーザーのアクセスに対して許可や拒否を設定できます
      • USER() を user@host を返すように変更
      • 他のユーザーの PASSWORD をセットする構文を変更
      • 新コマンド：FLUSH STATUS はほとんどのステータス変数をゼロにセットします
      • 新ステータス変数： aborted_threads, aborted_connects.
      • 新オプション： connection_timeout
      • ソートのサポート (by Pruet Boonma pruet@ds90.intanon.nectec.or.th).
      • スロバキア語と日本語のエラーメッセージ
      • Configuration and portability fixes.
      • Added option SET SQL_WARNINGS=1 to get a warning count also for simple inserts.
      • FreeBSD 上でシャットダウンするために、SIGQUIT のかわりに SIGTERM を使用します
      • mysql に オプション \G (print vertically) 追加
      • SELECT HIGH_PRIORITY ... killed mysqld.
      • IS NULL on a AUTO_INCREMENT column in a LEFT JOIN didn't work as expected.
      • New function MAKE_SET().

      D.5.26 Changes in release 3.22.10 (1998-11-05)

      • mysql_install_db は MySQL サーバーを起動しなくなりました! mysql_install_db を行った後に、safe_mysqld で mysqld を開始させる必要があります。 しかし MySQL の RPM パッケージはサーバーをたちあげるようにしています。
      • --bootstrap を mysqld に追加。mysql_install_db はこれを使用します。 この引数は RPM パッケージで MySQL のインストールを簡略化します。
      • +, - (sign and minus), *, /, %, ABS() and MOD() のコードを修正。 BIGINTで使用した場合の危険性を回避しました(64 bit safe).
      • ALTER TABLE が mysqld をクラッシュさせるバグを修正。
      • 重複したキー結果を得た場合、MySQLは常にその旨を報告するようになりました。 (以前のバージョンでは、INSERT の時にしかメッセージが出ませんでした)
      • New syntax: INSERT INTO table_name SET column=value,column=value, ...
      • `.err' ログファイルのログ記録に、time stamp をつけるようにしました。
      • MYSQL_INIT_COMMAND オプションを mysql_options() に追加。 (接続要求する場合に使用できる)
      • MYSQL_READ_DEFAULT_FILE と MYSQL_READ_DEFAULT_GROUP を mysql_options()に追加。 MySQL オプションファイルから以下のパラメーターを読み取る： port, socket, compress, password, pipe, timeout, user, init-command, host and database (訳注)オプションファイルのデフォルトは /etc/my.cnf , install_directory/share/mysql/my.cnf
      • UDF 構文に maybe_null を追加
      • Added option IGNORE to INSERT statements with many rows.
      • koi8 キャラクターをソートする場合の問題を修正。 koi8を使用しているユーザーは、CHAR や VARCHAR カラムを インデックスにしているテーブルに対して、必ず isamchk -rq を実行すること。
      • 新規スクリプト mysql_setpermission (Luuk de Boer 作) これは指定されたデータベースに対してアクセスを許可するユーザーを 簡単に登録してくれます。
      • Allow use of hexadecimal strings (0x...) when specifying a constant string (like in the column separators with LOAD DATA INFILE).
      • OS/2 に移植 (thanks to Antony T. Curtis antony.curtis@olcs.net).
      • SHOW STATUS での変数を増やしました。また、SHOW VARIABLES の ような出力フォーマットに変更しました。
      • extended-status コマンドを mysqladmin に追加。 これは新しいステイタス変数を表示します

      D.5.27 Changes in release 3.22.9

      • SET SQL_LOG_UPDATE=0 caused a lockup of the server.
      • New SQL command: FLUSH [ TABLES | HOSTS | LOGS | PRIVILEGES ] [, ...]
      • New SQL command: KILL thread_id .
      • AIX, DEC OSF1 4.x で MySQL を簡単にコンパイルできるように include ファイルを変更。
      • ALTER TABLE を使用して INT からサイズの小さい CHAR() に 変更する場合におきていた不具合を修正。
      • SELECT HIGH_PRIORITY 追加。 SELECT において、たとえ他の SELECT を待っているスレッドがあったとしても、 WRITE LOCK することができます。
      • Moved wild_compare to string class to be able to use LIKE on BLOB/TEXT columns with \0.
      • Added ESCAPE option to LIKE
      • mysqladmin debug において、より多くの出力が得られるようにした。
      • Windows において、--flush オプションをつけて mysqld を起動できるようになりました。 これはアップデートが終わった後ですべてのテーブルをディスクにフラッシュします。 このオプションにより NT/Win98 上ですごく安全に動かすことができますが、 とても 遅くなります。

      D.5.28 Changes in release 3.22.8

      • Czech character sets should now work much better. You must also install http://www.mysql.com/Downloads/Patches/czech-3.22.8-patch. This patch should also be installed if you are using a character set which uses my_strcoll()! The patch should always be safe to install (for any system), but as this patch changes ISAM internals it's not yet in the default distribution.
      • DATE_ADD() and DATE_SUB() didn't work with group functions.
      • mysql will now also try to reconnect on USE DATABASE commands.
      • Fix problem with ORDER BY and LEFT JOIN and const tables.
      • Fixed problem with ORDER BY if the first ORDER BY column was a key and the rest of the ORDER BY columns wasn't part of the key.
      • Fixed a big problem with OPTIMIZE TABLE.
      • MySQL clients on NT will now by default first try to connect with named pipes and after this with TCP/IP.
      • Fixed a problem with DROP TABLE and mysqladmin shutdown on Windows (a fatal bug from 3.22.6).
      • Fixed problems with TIME columns and negative strings.
      • Added an extra thread signal loop on shutdown to avoid some error messages from the client.
      • MySQL now uses the next available number as extension for the update log file.
      • Added patches for UNIXWARE 7.

      D.5.29 Changes in release 3.22.7 (1998-09: Beta)

      • Added LIMIT clause for the DELETE statement.
      • You can now use the /*! ... */ syntax to hide MySQL-specific keywords when you write portable code. MySQL will parse the code inside the comments as if the surrounding /*! and */ comment characters didn't exist.
      • OPTIMIZE TABLE tbl_name can now be used to reclaim disk space after many deletes. Currently, this uses ALTER TABLE to re-generate the table, but in the future it will use an integrated isamchk for more speed.
      • Upgraded libtool to get the configure more portable.
      • Fixed slow UPDATE and DELETE operations when using DATETIME or DATE keys.
      • Changed optimizer to make it better at deciding when to do a full join and when using keys.
      • You can now use mysqladmin proc to display information about your own threads. Only users with the PROCESS privilege can get information about all threads. (In 4.0.2 one needs the SUPER privilege for this.)
      • Added handling of formats YYMMDD, YYYYMMDD, YYMMDDHHMMSS for numbers when using DATETIME and TIMESTAMP types. (Formerly these formats only worked with strings.)
      • Added connect option CLIENT_IGNORE_SPACE to allow use of spaces after function names and before `(' (Powerbuilder requires this). This will make all function names reserved words.
      • Added the --log-long-format option to mysqld to enable timestamps and INSERT_ID's in the update log.
      • Added --where option to mysqldump (patch by Jim Faucette).
      • The lexical analyser now uses ``perfect hashing'' for faster parsing of SQL statements.

      D.5.30 Changes in release 3.22.6 (1998-07-11)

      • Faster mysqldump.
      • For the LOAD DATA INFILE statement, you can now use the new LOCAL keyword to read the file from the client. mysqlimport will automatically use LOCAL when importing with the TCP/IP protocol.
      • Fixed small optimize problem when updating keys.
      • Changed makefiles to support shared libraries.
      • MySQL-NT can now use named pipes, which means that you can now use MySQL-NT without having to install TCP/IP.

      D.5.31 Changes in release 3.22.5

      • All table lock handing is changed to avoid some very subtle deadlocks when using DROP TABLE, ALTER TABLE, DELETE FROM TABLE and mysqladmin flush-tables under heavy usage. Changed locking code to get better handling of locks of different types.
      • Updated DBI to 1.00 and DBD to 1.2.0.
      • Added a check that the error message file contains error messages suitable for the current version of mysqld. (To avoid errors if you accidentally try to use an old error message file.)
      • All count structures in the client (affected_rows(), insert_id(), ...) are now of type BIGINT to allow 64-bit values to be used. This required a minor change in the MySQL protocol which should affect only old clients when using tables with AUTO_INCREMENT values > 16M.
      • The return type of mysql_fetch_lengths() has changed from uint * to ulong *. This may give a warning for old clients but should work on most machines.
      • Change mysys and dbug libraries to allocate all thread variables in one struct. This makes it easier to make a threaded `libmysql.dll' library.
      • Use the result from gethostname() (instead of uname()) when constructing `.pid' file names.
      • New better compressed server/client protocol.
      • COUNT(), STD() and AVG() are extended to handle more than 4G rows.
      • You can now store values in the range -838:59:59 <= x <= 838:59:59 in a TIME column.
      • WARNING: INCOMPATIBLE CHANGE!! If you set a TIME column to too short a value, MySQL now assumes the value is given as: [[[D ]HH:]MM:]SS instead of HH[:MM[:SS]].
      • TIME_TO_SEC() and SEC_TO_TIME() can now handle negative times and hours up to 32767.
      • Added new option SET SQL_LOG_UPDATE={0|1} to allow users with the PROCESS privilege to bypass the update log. (Modified patch from Sergey A Mukhin violet@rosnet.net.)
      • Fixed fatal bug in LPAD().
      • Initialise line buffer in `mysql.cc' to make BLOB reading from pipes safer.
      • Added -O max_connect_errors=# option to mysqld. Connect errors are now reset for each correct connection.
      • Increased the default value of max_allowed_packet to 1M in mysqld.
      • Added --low-priority-updates option to mysqld, to give table-modifying operations (INSERT, REPLACE, UPDATE, DELETE) lower priority than retrievals. You can now use {INSERT | REPLACE | UPDATE | DELETE} LOW_PRIORITY ... You can also use SET SQL_LOW_PRIORITY_UPDATES={0|1} to change the priority for one thread. One side effect is that LOW_PRIORITY is now a reserved word. :(
      • Add support for INSERT INTO table ... VALUES(...),(...),(...), to allow inserting multiple rows with a single statement.
      • INSERT INTO tbl_name is now also cached when used with LOCK TABLES. (Previously only INSERT ... SELECT and LOAD DATA INFILE were cached.)
      • Allow GROUP BY functions with HAVING: 
        mysql> SELECT col FROM table GROUP BY col HAVING COUNT(*)>0;
      • mysqld will now ignore trailing `;' characters in queries. This is to make it easier to migrate from some other SQL servers that require the trailing `;'.
      • Fix for corrupted fixed-format output generated by SELECT INTO OUTFILE.
      • Warning: incompatible change! Added Oracle GREATEST() and LEAST() functions. You must now use these instead of the MAX() and MIN() functions to get the largest/smallest value from a list of values. These can now handle REAL, BIGINT and string (CHAR or VARCHAR) values.
      • Warning: incompatible change! DAYOFWEEK() had offset 0 for Sunday. Changed the offset to 1.
      • Give an error for queries that mix GROUP BY columns and fields when there is no GROUP BY specification.
      • Added --vertical option to mysql, for printing results in vertical mode.
      • Index-only optimization; some queries are now resolved using only indexes. Until MySQL 4.0, this works only for numeric columns. 「5.4.3 MySQL はどのようにインデックスを使用するか？」節参照.
      • Lots of new benchmarks.
      • A new C API chapter and lots of other improvements in the manual.

      D.5.32 Changes in release 3.22.4

      • Added --tmpdir option to mysqld, for specifying the location of the temporary file directory.
      • MySQL now automatically changes a query from an ODBC client: 
        SELECT ... FROM table WHERE auto_increment_column IS NULL
        to: 
        SELECT ... FROM table WHERE auto_increment_column == LAST_INSERT_ID()
        This allows some ODBC programs (Delphi, Access) to retrieve the newly inserted row to fetch the AUTO_INCREMENT id.
      • DROP TABLE now waits for all users to free a table before deleting it.
      • Fixed small memory leak in the new connect protocol.
      • New functions BIN(), OCT(), HEX() and CONV() for converting between different number bases.
      • Added function SUBSTRING() with 2 arguments.
      • If you created a table with a record length smaller than 5, you couldn't delete rows from the table.
      • Added optimization to remove const reference tables from ORDER BY and GROUP BY.
      • mysqld now automatically disables system locking on Linux and Windows, and for systems that use MIT-pthreads. You can force the use of locking with the --enable-external-locking option.
      • Added --console option to mysqld, to force a console window (for error messages) when using Windows.
      • Fixed table locks for Windows.
      • Allow `$' in identifiers.
      • Changed name of user-specific configuration file from `my.cnf' to `.my.cnf' (Unix only).
      • Added DATE_ADD() and DATE_SUB() functions.

      D.5.33 Changes in release 3.22.3

      • Fixed a lock problem (bug in MySQL Version 3.22.1) when closing temporary tables.
      • Added missing mysql_ping() to the client library.
      • Added --compress option to all MySQL clients.
      • Changed byte to char in `mysql.h' and `mysql_com.h'.

      D.5.34 Changes in release 3.22.2

      • Searching on multiple constant keys that matched more than 30% of the rows didn't always use the best possible key.
      • New functions <<, >>, RPAD() and LPAD().
      • You can now save default options (like passwords) in a configuration file (`my.cnf').
      • Lots of small changes to get ORDER BY to work when no records are found when using fields that are not in GROUP BY (MySQL extension).
      • Added --chroot option to mysqld, to start mysqld in a chroot environment (by Nikki Chumakov nikkic@cityline.ru).
      • Trailing spaces are now ignored when comparing case-sensitive strings; this should fix some problems with ODBC and flag 512!
      • Fixed a core-dump bug in the range optimizer.
      • Added --one-thread option to mysqld, for debugging with LinuxThreads (or glibc). (This replaces the -T32 flag)
      • Added DROP TABLE IF EXISTS to prevent an error from occurring if the table doesn't exist.
      • IF and EXISTS are now reserved words (they would have to be sooner or later).
      • Added lots of new options to mysqldump.
      • Server error messages are now in `mysqld_error.h'.
      • The server/client protocol now supports compression.
      • All bug fixes from MySQL Version 3.21.32.

      D.5.35 Changes in release 3.22.1 (1998-06-17)

      • Added new C API function mysql_ping().
      • Added new API functions mysql_init() and mysql_options(). You now MUST call mysql_init() before you call mysql_real_connect(). You don't have to call mysql_init() if you only use mysql_connect().
      • Added mysql_options(...,MYSQL_OPT_CONNECT_TIMEOUT,...) so you can set a timeout for connecting to a server.
      • Added --timeout option to mysqladmin, as a test of mysql_options().
      • Added AFTER column and FIRST options to ALTER TABLE ... ADD columns. This makes it possible to add a new column at some specific location within a row in an existing table.
      • WEEK() now takes an optional argument to allow handling of weeks when the week starts on Monday (some European countries). By default, WEEK() assumes the week starts on Sunday.
      • TIME columns weren't stored properly (bug in MySQL Version 3.22.0).
      • UPDATE now returns information about how many rows were matched and updated, and how many ``warnings'' occurred when doing the update.
      • Fixed incorrect result from FORMAT(-100,2).
      • ENUM and SET columns were compared in binary (case-sensitive) fashion; changed to be case-insensitive.

      D.5.36 Changes in release 3.22.0

      • New (backward-compatible) connect protocol that allows you to specify the database to use when connecting, to get much faster connections to a specific database. The mysql_real_connect() call is changed to: 
        mysql_real_connect(MYSQL *mysql, const char *host, const char *user,
                   const char *passwd, const char *db, uint port,
                   const char *unix_socket, uint client_flag)
      • Each connection is handled by its own thread, rather than by the master accept() thread. This fixes permanently the telnet bug that was a topic on the mail list some time ago.
      • All TCP/IP connections are now checked with backward-resolution of the hostname to get better security. mysqld now has a local hostname resolver cache so connections should actually be faster than before, even with this feature.
      • A site automatically will be blocked from future connections if someone repeatedly connects with an ``improper header'' (like when one uses telnet).
      • You can now refer to tables in different databases with references of the form tbl_name@db_name or db_name.tbl_name. This makes it possible to give a user read access to some tables and write access to others simply by keeping them in different databases!
      • Added --user option to mysqld, to allow it to run as another Unix user (if it is started as the Unix root user).
      • Added caching of users and access rights (for faster access rights checking)
      • Normal users (not anonymous ones) can change their password with mysqladmin password 'new_password'. This uses encrypted passwords that are not logged in the normal MySQL log!
      • All important string functions are now coded in assembler for x86 Linux machines. This gives a speedup of 10% in many cases.
      • For tables that have many columns, the column names are now hashed for much faster column name lookup (this will speed up some benchmark tests a lot!)
      • Some benchmarks are changed to get better individual timing. (Some loops were so short that a specific test took < 2 seconds. The loops have been changed to take about 20 seconds to make it easier to compare different databases. A test that took 1-2 seconds before now takes 11-24 seconds, which is much better)
      • Re-arranged SELECT code to handle some very specific queries involving group functions (like COUNT(*)) without a GROUP BY but with HAVING. The following now works: 
        mysql> SELECT COUNT(*) as C FROM table HAVING C > 1;
      • Changed the protocol for field functions to be faster and avoid some calls to malloc().
      • Added -T32 option to mysqld, for running all queries under the main thread. This makes it possible to debug mysqld under Linux with gdb!
      • Added optimization of not_null_column IS NULL (needed for some Access queries).
      • Allow STRAIGHT_JOIN to be used between two tables to force the optimizer to join them in a specific order.
      • String functions now return VARCHAR rather than CHAR and the column type is now VARCHAR for fields saved as VARCHAR. This should make the MyODBC driver better, but may break some old MySQL clients that don't handle FIELD_TYPE_VARCHAR the same way as FIELD_TYPE_CHAR.
      • CREATE INDEX and DROP INDEX are now implemented through ALTER TABLE. CREATE TABLE is still the recommended (fast) way to create indexes.
      • Added --set-variable option wait_timeout to mysqld.
      • Added time column to mysqladmin processlist to show how long a query has taken or how long a thread has slept.
      • Added lots of new variables to show variables and some new to show status.
      • Added new type YEAR. YEAR is stored in 1 byte with allowable values of 0, and 1901 to 2155.
      • Added new DATE type that is stored in 3 bytes rather than 4 bytes. All new tables are created with the new date type if you don't use the --old-protocol option to mysqld.
      • Fixed bug in record caches; for some queries, you could get Error from table handler: # on some operating systems.
      • Added --enable-assembler option to configure, for x86 machines (tested on Linux + gcc). This will enable assembler functions for the most important string functions for more speed!

      D.6 Changes in release 3.21.x

      Version 3.21 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only.

      D.6.1 Changes in release 3.21.33 (1998-07-11)

      • Fixed problem when sending SIGHUP to mysqld; mysqld core dumped when starting from boot on some systems.
      • Fixed problem with losing a little memory for some connections.
      • DELETE FROM tbl_name without a WHERE condition is now done the long way when you use LOCK TABLES or if the table is in use, to avoid race conditions.
      • INSERT INTO TABLE (timestamp_column) VALUES (NULL); didn't set timestamp.

      D.6.2 Changes in release 3.21.32

      • Fixed some possible race conditions when doing many reopen/close on the same tables under heavy load! This can happen if you execute mysqladmin refresh often. This could in some very rare cases corrupt the header of the index file and cause error 126 or 138.
      • Fixed fatal bug in refresh() when running with the --skip-external-locking option. There was a ``very small'' time gap after a mysqladmin refresh when a table could be corrupted if one thread updated a table while another thread did mysqladmin refresh and another thread started a new update ont the same table before the first thread had finished. A refresh (or --flush-tables) will now not return until all used tables are closed!
      • SELECT DISTINCT with a WHERE clause that didn't match any rows returned a row in some contexts (bug only in 3.21.31).
      • GROUP BY + ORDER BY returned one empty row when no rows where found.
      • Fixed a bug in the range optimizer that wrote Use_count: Wrong count for ... in the error log file.

      D.6.3 Changes in release 3.21.31 (1998-06-17)

      • Fixed a sign extension problem for the TINYINT type on Irix.
      • Fixed problem with LEFT("constant_string",function).
      • Fixed problem with FIND_IN_SET().
      • LEFT JOIN core dumped if the second table is used with a constant WHERE/ON expression that uniquely identifies one record.
      • Fixed problems with DATE_FORMAT() and incorrect dates. DATE_FORMAT() now ignores '%' to make it possible to extend it more easily in the future.

      D.6.4 Changes in release 3.21.30 (1998-05-11 stable)

      • mysql now returns an exit code > 0 if the query returned an error.
      • Saving of command-line history to file in mysql client. By Tommy Larsen tommy@mix.hive.no.
      • Fixed problem with empty lines that were ignored in `mysql.cc'.
      • Save the pid of the signal handler thread in the pid file instead of the pid of the main thread.
      • tommy@valley.ne.jp による日本語キャラクターセット(SJIS, UJIS)のサポート.
      • Changed safe_mysqld to redirect startup messages to 'hostname'.err instead of 'hostname'.log to reclaim file space on mysqladmin refresh.
      • ENUM always had the first entry as default value.
      • ALTER TABLE wrote two entries to the update log.
      • sql_acc() now closes the mysql grant tables after a reload to save table space and memory.
      • Changed LOAD DATA to use less memory with tables and BLOB columns.
      • Sorting on a function which made a division / 0 produced a wrong set in some cases.
      • Fixed SELECT problem with LEFT() when using the czech character set.
      • Fixed problem in isamchk; it couldn't repair a packed table in a very unusual case.
      • SELECT statements with & or | (bit functions) failed on columns with NULL values.
      • When comparing a field = field, where one of the fields was a part key, only the length of the part key was compared.

      D.6.5 Changes in release 3.21.29 (1998-04-10)

      • LOCK TABLES + DELETE from tbl_name never removed locks properly.
      • Fixed problem when grouping on an OR function.
      • Fixed permission problem with umask() and creating new databases.
      • Fixed permission problem on result file with SELECT ... INTO OUTFILE ...
      • Fixed problem in range optimizer (core dump) for a very complex query.
      • Fixed problem when using MIN(integer) or MAX(integer) in GROUP BY.
      • Fixed bug on Alpha when using integer keys. (Other keys worked on Alpha.)
      • Fixed bug in WEEK("XXXX-xx-01").

      D.6.6 Changes in release 3.21.28 (1998-04-01)

      • Fixed socket permission (clients couldn't connect to Unix socket on Linux).
      • Fixed bug in record caches; for some queries, you could get Error from table handler: # on some operating systems.

      D.6.7 Changes in release 3.21.27 (1998-03-28 gamma)

      • Added user level lock functions GET_LOCK(string,timeout), RELEASE_LOCK(string).
      • Added Opened_tables to show status.
      • Changed connect timeout to 3 seconds to make it somewhat harder for crackers to kill mysqld through telnet + TCP/IP.
      • Fixed bug in range optimizer when using WHERE key_part_1 >= something AND key_part_2 <= something_else.
      • Changed configure for detection of FreeBSD 3.0 9803xx and above
      • WHERE with string_col_key = constant_string didn't always find all rows if the column had many values differing only with characters of the same sort value (like e and 'e).
      • Strings keys looked up with 'ref' were not compared in case-sensitive fashion.
      • Added umask() to make log files non-readable for normal users.
      • Ignore users with old (8-byte) password on startup if not using --old-protocol option to mysqld.
      • SELECT which matched all key fields returned the values in the case of the matched values, not of the found values. (Minor problem.)

      D.6.8 Changes in release 3.21.26

      • FROM_DAYS(0) now returns "0000-00-00".
      • In DATE_FORMAT(), PM and AM were swapped for hours 00 and 12.
      • Extended the default maximum key size to 256.
      • Fixed bug when using BLOB/TEXT in GROUP BY with many tables.
      • An ENUM field that is not declared NOT NULL has NULL as the default value. (Previously, the default value was the first enumeration value.)
      • Fixed bug in the join optimizer code when using many part keys on the same key: INDEX (Organisation,Surname(35),Initials(35)).
      • Added some tests to the table order optimizer to get some cases with SELECT ... FROM many_tables much faster.
      • Added a retry loop around accept() to possibly fix some problems on some Linux machines.

      D.6.9 Changes in release 3.21.25

      • Changed typedef 'string' to typedef 'my_string' for better portability.
      • You can now kill threads that are waiting on a disk-full condition.
      • Fixed some problems with UDF functions.
      • Added long options to isamchk. Try isamchk --help.
      • Fixed a bug when using 8 bytes long (alpha); filesort() didn't work. Affects DISTINCT, ORDER BY and GROUP BY on 64-bit processors.

      D.6.10 Changes in release 3.21.24

      • Dynamic loadable functions. Based on source from Alexis Mikhailov.
      • You couldn't delete from a table if no one had done a SELECT on the table.
      • Fixed problem with range optimizer with many OR operators on key parts inside each other.
      • Recoded MIN() and MAX() to work properly with strings and HAVING.
      • Changed default umask value for new files from 0664 to 0660.
      • Fixed problem with LEFT JOIN and constant expressions in the ON part.
      • Added Italian error messages from brenno@dewinter.com.
      • configure now works better on OSF/1 (tested on 4.0D).
      • Added hooks to allow LIKE optimization with international character support.
      • Upgraded DBI to 0.93.

      D.6.11 Changes in release 3.21.23

      • The following symbols are now reserved words: TIME, DATE, TIMESTAMP, TEXT, BIT, ENUM, NO, ACTION, CHECK, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, STATUS, VARIABLES.
      • Setting a TIMESTAMP to NULL in LOAD DATA INFILE ... didn't set the current time for the TIMESTAMP.
      • Fix BETWEEN to recognise binary strings. Now BETWEEN is case-sensitive.
      • Added --skip-thread-priority option to mysqld, for systems where mysqld's thread scheduling doesn't work properly (BSDI 3.1).
      • Added ODBC functions DAYNAME() and MONTHNAME().
      • Added function TIME_FORMAT(). This works like DATE_FORMAT(), but takes a time string ('HH:MM:DD') as argument.
      • Fixed unlikely(?) key optimizer bug when using ORs of key parts inside ANDs.
      • Added variables command to mysqladmin.
      • A lot of small changes to the binary releases.
      • Fixed a bug in the new protocol from MySQL Version 3.21.20.
      • Changed ALTER TABLE to work with Windows (Windows can't rename open files). Also fixed a couple of small bugs in the Windows version.
      • All standard MySQL clients are now ported to MySQL-Windows.
      • MySQL can now be started as a service on NT.

      D.6.12 Changes in release 3.21.22

      • Starting with this version, all MySQL distributions will be configured, compiled and tested with crash-me and the benchmarks on the following platforms: SunOS 5.6 sun4u, SunOS 5.5.1 sun4u, SunOS 4.14 sun4c, SunOS 5.6 i86pc, Irix 6.3 mips5k, HP-UX 10.20 hppa, AIX 4.2.1 ppc, OSF/1 V4.0 alpha, FreeBSD 2.2.2 i86pc and BSDI 3.1 i386.
      • Fix COUNT(*) problems when the WHERE clause didn't match any records. (Bug from 3.21.17.)
      • Removed that NULL = NULL is true. Now you must use IS NULL or IS NOT NULL to test whether a value is NULL. (This is according to ANSI SQL but may break old applications that are ported from mSQL.) You can get the old behaviour by compiling with -DmSQL_COMPLIANT.
      • Fixed bug that core dumped when using many LEFT OUTER JOIN clauses.
      • Fixed bug in ORDER BY on string formula with possible NULL values.
      • Fixed problem in range optimizer when using <= on sub index.
      • Added functions DAYOFYEAR(), DAYOFMONTH(), MONTH(), YEAR(), WEEK(), QUARTER(), HOUR(), MINUTE(), SECOND() and FIND_IN_SET().
      • Added command SHOW VARIABLES.
      • Added support of ``long constant strings'' from ANSI SQL: 
        mysql> SELECT 'first ' 'second';       -> 'first second'
      • Upgraded mSQL-Mysql-modules to 1.1825.
      • Upgraded mysqlaccess to 2.02.
      • Fixed problem with Russian character set and LIKE.
      • Ported to OpenBSD 2.1.
      • New Dutch error messages.

      D.6.13 Changes in release 3.21.21a

      • Configure changes for some operating systems.

      D.6.14 Changes in release 3.21.21

      • Fixed optimizer bug when using WHERE data_field = date_field2 AND date_field2 = constant.
      • Added SHOW STATUS command.
      • Removed `manual.ps' from the source distribution to make it smaller.

      D.6.15 Changes in release 3.21.20

      • Changed the maximum table name and column name lengths from 32 to 64.
      • Aliases can now be of ``any'' length.
      • Fixed mysqladmin stat to return the right number of queries.
      • Changed protocol (downward compatible) to mark if a column has the AUTO_INCREMENT attribute or is a TIMESTAMP. This is needed for the new Java driver.
      • Added Hebrew sorting order by Zeev Suraski.
      • Solaris 2.6: Fixed configure bugs and increased maximum table size from 2G to 4G.

      D.6.16 Changes in release 3.21.19

      • Upgraded DBD to 1.1823. This version implements mysql_use_result in DBD-Mysql.
      • Benchmarks updated for empress (by Luuk).
      • Fixed a case of slow range searching.
      • Configure fixes (`Docs' directory).
      • Added function REVERSE() (by Zeev Suraski).

      D.6.17 Changes in release 3.21.18

      • Issue error message if client C functions are called in wrong order.
      • Added automatic reconnect to the `libmysql.c' library. If a write command fails, an automatic reconnect is done.
      • Small sort sets no longer use temporary files.
      • Upgraded DBI to 0.91.
      • Fixed a couple of problems with LEFT OUTER JOIN.
      • Added CROSS JOIN syntax. CROSS is now a reserved word.
      • Recoded yacc/bison stack allocation to be even safer and to allow MySQL to handle even bigger expressions.
      • Fixed a couple of problems with the update log.
      • ORDER BY was slow when used with key ranges.

      D.6.18 Changes in release 3.21.17 (1997-12-20)

      • Changed documentation string of --with-unix-socket-path to avoid confusion.
      • Added ODBC and ANSI SQL style LEFT OUTER JOIN.
      • The following are new reserved words: LEFT, NATURAL, USING.
      • The client library now uses the value of the environment variable MYSQL_HOST as the default host if it's defined.
      • SELECT col_name, SUM(expr) now returns NULL for col_name when there are matching rows.
      • Fixed problem with comparing binary strings and BLOBs with ASCII characters over 127.
      • Fixed lock problem: when freeing a read lock on a table with multiple read locks, a thread waiting for a write lock would have been given the lock. This shouldn't affect data integrity, but could possibly make mysqld restart if one thread was reading data that another thread modified.
      • LIMIT offset,count didn't work in INSERT ... SELECT.
      • Optimized key block caching. This will be quicker than the old algorithm when using bigger key caches.

      D.6.19 Changes in release 3.21.16 (1997-12-10 beta)

      • Added ODBC 2.0 & 3.0 functions POWER(), SPACE(), COT(), DEGREES(), RADIANS(), ROUND(2 arg) and TRUNCATE().
      • Warning: Incompatible change! LOCATE() parameters were swapped according to ODBC standard. Fixed.
      • Added function TIME_TO_SEC().
      • In some cases, default values were not used for NOT NULL fields.
      • Timestamp wasn't always updated properly in UPDATE SET ... statements.
      • Allow empty strings as default values for BLOB and TEXT, to be compatible with mysqldump.

      D.6.20 Changes in release 3.21.15 (1997-12-01)

      • Warning: Incompatible change! mysqlperl is now from Msql-Mysql-modules. This means that connect() now takes host, database, user, password arguments! The old version took host, database, password, user.
      • Allow DATE '1997-01-01', TIME '12:10:10' and TIMESTAMP '1997-01-01 12:10:10' formats required by ANSI SQL. Warning: Incompatible change! This has the unfortunate side-effect that you no longer can have columns named DATE, TIME or TIMESTAMP. :( Old columns can still be accessed through tablename.columnname!)
      • Changed Makefiles to hopefully work better with BSD systems. Also, `manual.dvi' is now included in the distribution to avoid having stupid make programs trying to rebuild it.
      • readline library upgraded to version 2.1.
      • A new sortorder german-1. That is a normal ISO-Latin1 with a german sort order.
      • Perl DBI/DBD is now included in the distribution. DBI is now the recommended way to connect to MySQL from Perl.
      • New portable benchmark suite with DBD, with test results from mSQL 2.0.3, MySQL, PostgreSQL 6.2.1 and Solid server 2.2.
      • crash-me is now included with the benchmarks; This is a Perl program designed to find as many limits as possible in a SQL server. Tested with mSQL, PostgreSQL, Solid and MySQL.
      • Fixed bug in range-optimizer that crashed MySQL on some queries.
      • Table and column name completion for mysql command line tool, by Zeev Suraski and Andi Gutmans.
      • Added new command REPLACE that works like INSERT but replaces conflicting records with the new record. REPLACE INTO TABLE ... SELECT ... works also.
      • Added new commands CREATE DATABASE db_name and DROP DATABASE db_name.
      • Added RENAME option to ALTER TABLE: ALTER TABLE name RENAME TO new_name.
      • make_binary_distribution now includes `libgcc.a' in `libmysqlclient.a'. This should make linking work for people who don't have gcc.
      • Changed net_write() to my_net_write() because of a name conflict with Sybase.
      • New function DAYOFWEEK() compatible with ODBC.
      • Stack checking and bison memory overrun checking to make MySQL safer with weird queries.

      D.6.21 Changes in release 3.21.14b

      • Fixed a couple of small configure problems on some platforms.

      D.6.22 Changes in release 3.21.14a (1997-11-12)

      • Ported to SCO Openserver 5.0.4 with FSU Pthreads.
      • HP-UX 10.20 should work.
      • Added new function DATE_FORMAT().
      • Added NOT IN.
      • Added automatic removal of 'ODBC function conversions': {fn now() }
      • Handle ODBC 2.50.3 option flags.
      • Fixed comparison of DATE and TIME values with NULL.
      • Changed language name from germany to german to be consistent with the other language names.
      • Fixed sorting problem on functions returning a FLOAT. Previously, the values were converted to INTs before sorting.
      • Fixed slow sorting when sorting on key field when using key_column=constant.
      • Sorting on calculated DOUBLE values sorted on integer results instead.
      • mysql no longer requires a database argument.
      • Changed the place where HAVING should be. According to ANSI, it should be after GROUP BY but before ORDER BY. MySQL Version 3.20 incorrectly had it last.
      • Added Sybase command USE DATABASE to start using another database.
      • Added automatic adjusting of number of connections and table cache size if the maximum number of files that can be opened is less than needed. This should fix that mysqld doesn't crash even if you haven't done a ulimit -n 256 before starting mysqld.
      • Added lots of limit checks to make it safer when running with too little memory or when doing weird queries.

      D.6.23 Changes in release 3.21.13

      • Added retry of interrupted reads and clearing of errno. This makes Linux systems much safer!
      • Fixed locking bug when using many aliases on the same table in the same SELECT.
      • Fixed bug with LIKE on number key.
      • New error message so you can check whether the connection was lost while the command was running or whether the connection was down from the start.
      • Added --table option to mysql to print in table format. Moved time and row information after query result. Added automatic reconnect of lost connections.
      • Added != as a synonym for <>.
      • Added function VERSION() to make easier logs.
      • New multi-user test `tests/fork_test.pl' to put some strain on the thread library.

      D.6.24 Changes in release 3.21.12

      • Fixed ftruncate() call in MIT-pthreads. This made isamchk destroy the `.ISM' files on (Free)BSD 2.x systems.
      • Fixed broken __P_ patch in MIT-pthreads.
      • Many memory overrun checks. All string functions now return NULL if the returned string should be longer than max_allowed_packet bytes.
      • Changed the name of the INTERVAL type to ENUM, because INTERVAL is used in ANSI SQL.
      • In some cases, doing a JOIN + GROUP + INTO OUTFILE, the result wasn't grouped.
      • LIKE with '_' as last character didn't work. Fixed.
      • Added extended ANSI SQL TRIM() function.
      • Added CURTIME().
      • Added ENCRYPT() function by Zeev Suraski.
      • Fixed better FOREIGN KEY syntax skipping. New reserved words: MATCH, FULL, PARTIAL.
      • mysqld now allows IP number and hostname for the --bind-address option.
      • Added SET CHARACTER SET cp1251_koi8 to enable conversions of data to and from the cp1251_koi8 character set.
      • Lots of changes for Windows 95 port. In theory, this version should now be easily portable to Windows 95.
      • Changed the CREATE COLUMN syntax of NOT NULL columns to be after the DEFAULT value, as specified in the ANSI SQL standard. This will make mysqldump with NOT NULL and default values incompatible with MySQL Version 3.20.
      • Added many function name aliases so the functions can be used with ODBC or ANSI SQL92 syntax.
      • Fixed syntax of ALTER TABLE tbl_name ALTER COLUMN col_name SET DEFAULT NULL.
      • Added CHAR and BIT as synonyms for CHAR(1).
      • Fixed core dump when updating as a user who has only SELECT privilege.
      • INSERT ... SELECT ... GROUP BY didn't work in some cases. An Invalid use of group function error occurred.
      • When using LIMIT, SELECT now always uses keys instead of record scan. This will give better performance on SELECT and a WHERE that matches many rows.
      • Added Russian error messages.

      D.6.25 Changes in release 3.21.11 (1997-10-16)

      • Configure changes.
      • MySQL now works with the new thread library on BSD/OS 3.0.
      • Added new group functions BIT_OR() and BIT_AND().
      • Added compatibility functions CHECK and REFERENCES. CHECK is now a reserved word.
      • Added ALL option to GRANT for better compatibility. (GRANT is still a dummy function.)
      • Added partly-translated Dutch error messages.
      • Fixed bug in ORDER BY and GROUP BY with NULL columns.
      • Added function LAST_INSERT_ID() SQL function to retrieve last AUTO_INCREMENT value. This is intended for clients to ODBC that can't use the mysql_insert_id() API function, but can be used by any client.
      • Added --flush-logs option to mysqladmin.
      • Added command STATUS to mysql.
      • Fixed problem with ORDER BY/GROUP BY because of bug in gcc.
      • Fixed problem with INSERT ... SELECT ... GROUP BY.

      D.6.26 Changes in release 3.21.10

      • New mysqlaccess.
      • CREATE now supports all ODBC types and the mSQL TEXT type. All ODBC 2.5 functions are also supported (added REPEAT). This provides better portability.
      • Added text types TINYTEXT, TEXT, MEDIUMTEXT and LONGTEXT. These are actually BLOBtypes, but all searching is done in case-insensitive fashion.
      • All old BLOB fields are now TEXT fields. This only changes that all searching on strings is done in case-sensitive fashion. You must do an ALTER TABLE and change the field type to BLOB if you want to have tests done in case-sensitive fashion.
      • Fixed some configure issues.
      • Made the locking code a bit safer. Fixed very unlikely deadlock situation.
      • Fixed a couple of bugs in the range optimizer. Now the new range benchmark test-select works.

      D.6.27 Changes in release 3.21.9 (1997-09-28)

      • Added --enable-unix-socket=pathname option to configure.
      • Fixed a couple of portability problems with include files.
      • Fixed bug in range calculation that could return empty set when searching on multiple key with only one entry (very rare).
      • Most things ported to FSU Pthreads, which should allow MySQL to run on Caldera (SCO). 「2.6.6.9 Caldera (SCO) Notes」節参照.

      D.6.28 Changes in release 3.21.8

      • Works now in Solaris 2.6.
      • Added handling of calculation of SUM() functions. For example, you can now use SUM(column)/COUNT(column).
      • Added handling of trigometric functions: PI(), ACOS(), ASIN(), ATAN(), COS(), SIN() and TAN().
      • New languages: norwegian, norwegian-ny and portuguese.
      • Fixed parameter bug in net_print() in `procedure.cc'.
      • Fixed a couple of memory leaks.
      • Now allow also the old SELECT ... INTO OUTFILE syntax.
      • Fixed bug with GROUP BY and SELECT on key with many values.
      • mysql_fetch_lengths() sometimes returned incorrect lengths when you used mysql_use_result(). This affected at least some cases of mysqldump --quick.
      • Fixed bug in optimization of WHERE const op field.
      • Fixed problem when sorting on NULL fields.
      • Fixed a couple of 64-bit (Alpha) problems.
      • Added --pid-file=# option to mysqld.
      • Added date formatting to FROM_UNIXTIME(), originally by Zeev Suraski.
      • Fixed bug in BETWEEN in range optimizer (did only test = of the first argument).
      • Added machine-dependent files for MIT-pthreads i386-SCO. There is probably more to do to get this to work on SCO 3.5.

      D.6.29 Changes in release 3.21.7

      • Changed `Makefile.am' to take advantage of Automake 1.2.
      • Added the beginnings of a benchmark suite.
      • Added more secure password handling.
      • Added new client function mysql_errno(), to get the error number of the error message. This makes error checking in the client much easier. This makes the new server incompatible with the 3.20.x server when running without --old-protocol. The client code is backward-compatible. More information can be found in the `README' file!
      • Fixed some problems when using very long, illegal names.

      D.6.30 Changes in release 3.21.6

      • Fixed more portability issues (incorrect sigwait and sigset defines).
      • configure should now be able to detect the last argument to accept().

      D.6.31 Changes in release 3.21.5

      • Should now work with FreeBSD 3.0 if used with `FreeBSD-3.0-libc_r-1.0.diff', which can be found at http://www.mysql.com/downloads/patches.html.
      • Added new -O tmp_table_size=# option to mysqld.
      • New function FROM_UNIXTIME(timestamp) which returns a date string in 'YYYY-MM-DD HH:MM:DD' format.
      • New function SEC_TO_TIME(seconds) which returns a string in 'HH:MM:SS' format.
      • New function SUBSTRING_INDEX(), originally by Zeev Suraski.

      D.6.32 Changes in release 3.21.4

      • Should now configure and compile on OSF/1 4.0 with the DEC compiler.
      • Configuration and compilation on BSD/OS 3.0 works, but due to some bugs in BSD/OS 3.0, mysqld doesn't work on it yet.
      • Configuration and compilation on FreeBSD 3.0 works, but I couldn't get pthread_create to work.

      D.6.33 Changes in release 3.21.3

      • Added reverse check lookup of hostnames to get better security.
      • Fixed some possible buffer overflows if filenames that are too long are used.
      • mysqld doesn't accept hostnames that start with digits followed by a '.', because the hostname may look like an IP number.
      • Added --skip-networking option to mysqld, to allow only socket connections. (This will not work with MIT-pthreads!)
      • Added check of too long table names for alias.
      • Added check if database name is okay.
      • Added check if too long table names.
      • Removed incorrect free() that killed the server on CREATE DATABASE or DROP DATABASE.
      • Changed some mysqld -O options to better names.
      • Added -O join_cache_size=# option to mysqld.
      • Added -O max_join_size=# option to mysqld, to be able to set a limit how big queries (in this case big = slow) one should be able to handle without specifying SET SQL_BIG_SELECTS=1. A # = is about 10 examined records. The default is ``unlimited''.
      • When comparing a TIME, DATE, DATETIME or TIMESTAMP column to a constant, the constant is converted to a time value before performing the comparison. This will make it easier to get ODBC (particularly Access97) to work with the above types. It should also make dates easier to use and the comparisons should be quicker than before.
      • Applied patch from Jochen Wiedmann that allows query() in mysqlperl to take a query with \0 in it.
      • Storing a timestamp with a 2-digit year (YYMMDD) didn't work.
      • Fix that timestamp wasn't automatically updated if set in an UPDATE clause.
      • Now the automatic timestamp field is the FIRST timestamp field.
      • SELECT * INTO OUTFILE, which didn't correctly if the outfile already existed.
      • mysql now shows the thread ID when starting or doing a reconnect.
      • Changed the default sort buffer size from 2M to 1M.

      D.6.34 Changes in release 3.21.2

      • The range optimizer is coded, but only 85% tested. It can be enabled with --new, but it crashes core a lot yet...
      • More portable. Should compile on AIX and alpha-digital. At least the isam library should be relatively 64-bit clean.
      • New isamchk which can detect and fix more problems.
      • New options for isamlog.
      • Using new version of Automake.
      • Many small portability changes (from the AIX and alpha-digital port) Better checking of pthread(s) library.
      • czech error messages by snajdr@pvt.net.
      • Decreased size of some buffers to get fewer problems on systems with little memory. Also added more checks to handle ``out of memory'' problems.
      • mysqladmin: you can now do mysqladmin kill 5,6,7,8 to kill multiple threads.
      • When the maximum connection limit is reached, one extra connection by a user with the process_acl privilege is granted.
      • Added -O backlog=# option to mysqld.
      • Increased maximum packet size from 512K to 1024K for client.
      • Almost all of the function code is now tested in the internal test suite.
      • ALTER TABLE now returns warnings from field conversions.
      • Port changed to 3306 (got it reserved from ISI).
      • Added a fix for Visual FoxBase so that any schema name from a table specification is automatically removed.
      • New function ASCII().
      • Removed function BETWEEN(a,b,c). Use the standard ANSI syntax instead: expr BETWEEN expr AND expr.
      • MySQL no longer has to use an extra temporary table when sorting on functions or SUM() functions.
      • Fixed bug that you couldn't use tbl_name.field_name in UPDATE.
      • Fixed SELECT DISTINCT when using 'hidden group'. For example: 
        mysql> SELECT DISTINCT MOD(some_field,10) FROM test
    ->        GROUP BY some_field;
        Note: some_field is normally in the SELECT part. ANSI SQL should require it.

      D.6.35 Changes in release 3.21.0

      • New reserved words used: INTERVAL, EXPLAIN, READ, WRITE, BINARY.
      • Added ODBC function CHAR(num,...).
      • New operator IN. This uses a binary search to find a match.
      • New command LOCK TABLES tbl_name [AS alias] {READ|WRITE} ...
      • Added --log-update option to mysqld, to get a log suitable for incremental updates.
      • New command EXPLAIN SELECT ... to get information about how the optimizer will do the join.
      • For easier client code, the client should no longer use FIELD_TYPE_TINY_BLOB, FIELD_TYPE_MEDIUM_BLOB, FIELD_TYPE_LONG_BLOB or FIELD_TYPE_VAR_STRING (as previously returned by mysql_list_fields). You should instead only use FIELD_TYPE_BLOB or FIELD_TYPE_STRING. If you want exact types, you should use the command SHOW FIELDS.
      • Added varbinary syntax: 0x###### which can be used as a string (default) or a number.
      • FIELD_TYPE_CHAR is renamed to FIELD_TYPE_TINY.
      • Changed all fields to C++ classes.
      • Removed FORM struct.
      • Fields with DEFAULT values no longer need to be NOT NULL.
      • New field types:
        ENUM
        A string which can take only a couple of defined values. The value is stored as a 1-3 byte number that is mapped automatically to a string. This is sorted according to string positions!
        SET
        A string which may have one or many string values separated with ','. The string is stored as a 1-, 2-, 3-, 4- or 8-byte number where each bit stands for a specific set member. This is sorted according to the unsigned value of the stored packed number.
      • Now all function calculation is done with double or long long. This will provide the full 64-bit range with bit functions and fix some conversions that previously could result in precision losses. One should avoid using unsigned long long columns with full 64-bit range (numbers bigger than 9223372036854775807) because calculations are done with signed long long.
      • ORDER BY will now put NULL field values first. GROUP BY will also work with NULL values.
      • Full WHERE with expressions.
      • New range optimizer that can resolve ranges when some keypart prefix is constant. Example: 
        mysql> SELECT * FROM tbl_name
    ->          WHERE key_part_1="customer"
    ->          AND key_part_2>=10 AND key_part_2<=10;

      D.7 Changes in release 3.20.x

      Version 3.20 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only.

      Changes from 3.20.18 to 3.20.32b are not documented here because the 3.21 release branched here. And the relevant changes are also documented as changes to the 3.21 version.

      D.7.1 Changes in release 3.20.18

      • Added -p# (remove # directories from path) to isamlog. All files are written with a relative path from the database directory Now mysqld shouldn't crash on shutdown when using the --log-isam option.
      • New mysqlperl version. It is now compatible with msqlperl-0.63.
      • New DBD module available.
      • Added group function STD() (standard deviation).
      • The mysqld server is now compiled by default without debugging information. This will make the daemon smaller and faster.
      • Now one usually only has to specify the --basedir option to mysqld. All other paths are relative in a normal installation.
      • BLOB columns sometimes contained garbage when used with a SELECT on more than one table and ORDER BY.
      • Fixed that calculations that are not in GROUP BY work as expected (ANSI SQL extension). Example: 
        mysql> SELECT id,id+1 FROM table GROUP BY id;
      • The test of using MYSQL_PWD was reversed. Now MYSQL_PWD is enabled as default in the default release.
      • Fixed conversion bug which caused mysqld to core dump with Arithmetic error on SPARC-386.
      • Added --unbuffered option to mysql, for new mysqlaccess.
      • When using overlapping (unnecessary) keys and join over many tables, the optimizer could get confused and return 0 records.

      D.7.2 Changes in release 3.20.17 (1997-04-13)

      • You can now use BLOB columns and the functions IS NULL and IS NOT NULL in the WHERE clause.
      • All communication packets and row buffers are now allocated dynamically on demand. The default value of max_allowed_packet is now 64K for the server and 512K for the client. This is mainly used to catch incorrect packets that could trash all memory. The server limit may be changed when it is started.
      • Changed stack usage to use less memory.
      • Changed safe_mysqld to check for running daemon.
      • The ELT() function is renamed to FIELD(). The new ELT() function returns a value based on an index: FIELD() is the inverse of ELT() Example: ELT(2,"A","B","C") returns "B". FIELD("B","A","B","C") returns 2.
      • COUNT(field), where field could have a NULL value, now works.
      • A couple of bugs fixed in SELECT ... GROUP BY.
      • Fixed memory overrun bug in WHERE with many unoptimizable brace levels.
      • Fixed some small bugs in the grant code.
      • If hostname isn't found by get_hostname, only the IP is checked. Previously, you got Access denied.
      • Inserts of timestamps with values didn't always work.
      • INSERT INTO ... SELECT ... WHERE could give the error Duplicated field.
      • Added some tests to safe_mysqld to make it ``safer''.
      • LIKE was case-sensitive in some places and case-insensitive in others. Now LIKE is always case-insensitive.
      • `mysql.cc': Allow '#' anywhere on the line.
      • New command SET SQL_SELECT_LIMIT=#. See the FAQ for more details.
      • New version of the mysqlaccess script.
      • Change FROM_DAYS() and WEEKDAY() to also take a full TIMESTAMP or DATETIME as argument. Before they only took a number of type YYYYMMDD or YYMMDD.
      • Added new function UNIX_TIMESTAMP(timestamp_column).

      D.7.3 Changes in release 3.20.16

      • More changes in MIT-pthreads to get them safer. Fixed also some link bugs at least in SunOS.
      • Changed mysqld to work around a bug in MIT-pthreads. This makes multiple small SELECT operations 20 times faster. Now lock_test.pl should work.
      • Added mysql_FetchHash(handle) to mysqlperl.
      • The mysqlbug script is now distributed built to allow for reporting bugs that appear during the build with it.
      • Changed `libmysql.c' to prefer getpwuid() instead of cuserid().
      • Fixed bug in SELECT optimizer when using many tables with the same column used as key to different tables.
      • Added new latin2 and Russian KOI8 character tables.
      • Added support for a dummy GRANT command to satisfy Powerbuilder.

      D.7.4 Changes in release 3.20.15

      • Fixed fatal bug packets out of order when using MIT-pthreads.
      • Removed possible loop when a thread waits for command from client and fcntl() fails. Thanks to Mike Bretz for finding this bug.
      • Changed alarm loop in `mysqld.cc' because shutdown didn't always succeed in Linux.
      • Removed use of termbits from `mysql.cc'. This conflicted with glibc 2.0.
      • Fixed some syntax errors for at least BSD and Linux.
      • Fixed bug when doing a SELECT as superuser without a database.
      • Fixed bug when doing SELECT with group calculation to outfile.

      D.7.5 Changes in release 3.20.14

      • If one gives -p or --password option to mysql without an argument, the user is solicited for the password from the tty.
      • Added default password from MYSQL_PWD (by Elmar Haneke).
      • Added command kill to mysqladmin to kill a specific MySQL thread.
      • Sometimes when doing a reconnect on a down connection this succeeded first on second try.
      • Fixed adding an AUTO_INCREMENT key with ALTER_TABLE.
      • AVG() gave too small value on some SELECTs with GROUP BY and ORDER BY.
      • Added new DATETIME type (by Giovanni Maruzzelli maruzz@matrice.it).
      • Fixed that defining DONT_USE_DEFAULT_FIELDS works.
      • Changed to use a thread to handle alarms instead of signals on Solaris to avoid race conditions.
      • Fixed default length of signed numbers. (George Harvey georgeh@pinacl.co.uk.)
      • Allow anything for CREATE INDEX.
      • Add prezeros when packing numbers to DATE, TIME and TIMESTAMP.
      • Fixed a bug in OR of multiple tables (gave empty set).
      • Added many patches to MIT-pthreads. This fixes at least one lookup bug.

      D.7.6 Changes in release 3.20.13

      • Added ANSI SQL94 DATE and TIME types.
      • Fixed bug in SELECT with AND-OR levels.
      • Added support for Slovenian characters. The `Contrib' directory contains source and instructions for adding other character sets.
      • Fixed bug with LIMIT and ORDER BY.
      • Allow ORDER BY and GROUP BY on items that aren't in the SELECT list. (Thanks to Wim Bonis bonis@kiss.de, for pointing this out.)
      • Allow setting of timestamp values in INSERT.
      • Fixed bug with SELECT ... WHERE ... = NULL.
      • Added changes for glibc 2.0. To get glibc to work, you should add the `gibc-2.0-sigwait-patch' before compiling glibc.
      • Fixed bug in ALTER TABLE when changing a NOT NULL field to allow NULL values.
      • Added some ANSI92 synonyms as field types to CREATE TABLE. CREATE TABLE now allows FLOAT(4) and FLOAT(8) to mean FLOAT and DOUBLE.
      • New utility program mysqlaccess by Yves.Carlier@rug.ac.be. This program shows the access rights for a specific user and the grant rows that determine this grant.
      • Added WHERE const op field (by bonis@kiss.de).

      D.7.7 Changes in release 3.20.11

      • When using SELECT ... INTO OUTFILE, all temporary tables are ISAM instead of HEAP to allow big dumps.
      • Changed date functions to be string functions. This fixed some ``funny'' side effects when sorting on dates.
      • Extended ALTER TABLE according to SQL92.
      • Some minor compatibility changes.
      • Added --port and --socket options to all utility programs and mysqld.
      • Fixed MIT-pthreads readdir_r(). Now mysqladmin create database and mysqladmin drop database should work.
      • Changed MIT-pthreads to use our tempnam(). This should fix the ``sort aborted'' bug.
      • Added sync of records count in sql_update. This fixed slow updates on first connection. (Thanks to Vaclav Bittner for the test.)

      D.7.8 Changes in release 3.20.10

      • New insert type: INSERT INTO ... SELECT ...
      • MEDIUMBLOB fixed.
      • Fixed bug in ALTER TABLE and BLOBs.
      • SELECT ... INTO OUTFILE now creates the file in the current database directory.
      • DROP TABLE now can take a list of tables.
      • Oracle synonym DESCRIBE (DESC).
      • Changes to make_binary_distribution.
      • Added some comments to installation instructions about configure's C++ link test.
      • Added --without-perl option to configure.
      • Lots of small portability changes.

      D.7.9 Changes in release 3.20.9 (1997-02-13)

      • ALTER TABLE didn't copy null bit. As a result, fields that were allowed to have NULL values were always NULL.
      • CREATE didn't take numbers as DEFAULT.
      • Some compatibility changes for SunOS.
      • Removed `config.cache' from old distribution.

      D.7.10 Changes in release 3.20.8

      • Fixed bug with ALTER TABLE and multi-part keys.

      D.7.11 Changes in release 3.20.7

      • New commands: ALTER TABLE, SELECT ... INTO OUTFILE and LOAD DATA INFILE.
      • New function: NOW().
      • Added new field File_priv to mysql/user table.
      • New script add_file_priv which adds the new field File_priv to the user table. This script must be executed if you want to use the new SELECT ... INTO and LOAD DATA INFILE ... commands with a version of MySQL earlier than 3.20.7.
      • Fixed bug in locking code, which made lock_test.pl test fail.
      • New files `NEW' and `BUGS'.
      • Changed `select_test.c' and `insert_test.c' to include `config.h'.
      • Added status command to mysqladmin for short logging.
      • Increased maximum number of keys to 16 and maximum number of key parts to 15.
      • Use of sub keys. A key may now be a prefix of a string field.
      • Added -k option to mysqlshow, to get key information for a table.
      • Added long options to mysqldump.

      D.7.12 Changes in release 3.20.6 (1997-01-31)

      • Portable to more systems because of MIT-pthreads, which will be used automatically if configure cannot find a -lpthreads library.
      • Added GNU-style long options to almost all programs. Test with program --help.
      • Some shared library support for Linux.
      • The FAQ is now in `.texi' format and is available in `.html', `.txt' and `.ps' formats.
      • Added new SQL function RAND([init]).
      • Changed sql_lex to handle \0 unquoted, but the client can't send the query through the C API, because it takes a str pointer. You must use mysql_real_query() to send the query.
      • Added API function mysql_get_client_info().
      • mysqld now uses the N_MAX_KEY_LENGTH from `nisam.h' as the maximum allowable key length.
      • The following now works: 
        mysql> SELECT filter_nr,filter_nr FROM filter ORDER BY filter_nr;
        Previously, this resulted in the error: Column: 'filter_nr' in order clause is ambiguous.
      • mysql now outputs '\0', '\t', '\n' and '\\' when encountering ASCII 0, tab, newline or '\' while writing tab-separated output. This is to allow printing of binary data in a portable format. To get the old behaviour, use -r (or --raw).
      • Added german error messages (60 of 80 error messages translated).
      • Added new API function mysql_fetch_lengths(MYSQL_RES *), which returns an array of column lengths (of type uint).
      • Fixed bug with IS NULL in WHERE clause.
      • Changed the optimizer a little to get better results when searching on a key part.
      • Added SELECT option STRAIGHT_JOIN to tell the optimizer that it should join tables in the given order.
      • Added support for comments starting with '--' in `mysql.cc' (Postgres syntax).
      • You can have SELECT expressions and table columns in a SELECT which are not used in the group part. This makes it efficient to implement lookups. The column that is used should be a constant for each group because the value is calculated only once for the first row that is found for a group. 
        mysql> SELECT id,lookup.text,SUM(*) FROM test,lookup
    ->        WHERE test.id=lookup.id GROUP BY id;
      • Fixed bug in SUM(function) (could cause a core dump).
      • Changed AUTO_INCREMENT placement in the SQL query: 
        INSERT INTO table (auto_field) VALUES (0);
        inserted 0, but it should insert an AUTO_INCREMENT value.
      • `mysqlshow.c': Added number of records in table. Had to change the client code a little to fix this.
      • mysql now allows doubled '' or "" within strings for embedded ' or ".
      • New math functions: EXP(), LOG(), SQRT(), ROUND(), CEILING().

      D.7.13 Changes in release 3.20.3

      • The configure source now compiles a thread-free client library -lmysqlclient. This is the only library that needs to be linked with client applications. When using the binary releases, you must link with -lmysql -lmysys -ldbug -lmystrings as before.
      • New readline library from bash-2.0.
      • LOTS of small changes to configure and makefiles (and related source).
      • It should now be possible to compile in another directory using VPATH. Tested with GNU Make 3.75.
      • safe_mysqld and mysql.server changed to be more compatible between the source and the binary releases.
      • LIMIT now takes one or two numeric arguments. If one argument is given, it indicates the maximum number of rows in a result. If two arguments are given, the first argument indicates the offset of the first row to return, the second is the maximum number of rows. With this it's easy to do a poor man's next page/previous page WWW application.
      • Changed name of SQL function FIELDS() to ELT(). Changed SQL function INTERVALL() to INTERVAL().
      • Made SHOW COLUMNS a synonym for SHOW FIELDS. Added compatibility syntax FRIEND KEY to CREATE TABLE. In MySQL, this creates a non-unique key on the given columns.
      • Added CREATE INDEX and DROP INDEX as compatibility functions. In MySQL, CREATE INDEX only checks if the index exists and issues an error if it doesn't exist. DROP INDEX always succeeds.
      • `mysqladmin.c': added client version to version information.
      • Fixed core dump bug in sql_acl (core on new connection).
      • Removed host, user and db tables from database test in the distribution.
      • FIELD_TYPE_CHAR can now be signed (-128 to 127) or unsigned (0 to 255) Previously, it was always unsigned.
      • Bug fixes in CONCAT() and WEEKDAY().
      • Changed a lot of source to get mysqld to be compiled with SunPro compiler.
      • SQL functions must now have a '(' immediately after the function name (no intervening space). For example, 'USER(' is regarded as beginning a function call, and 'USER (' is regarded as an identifier USER followed by a '(', not as a function call.

      D.7.14 Changes in release 3.20.0

      • The source distribution is done with configure and Automake. It will make porting much easier. The readline library is included in the distribution.
      • Separate client compilation: the client code should be very easy to compile on systems which don't have threads.
      • The old Perl interface code is automatically compiled and installed. Automatic compiling of DBD will follow when the new DBD code is ported.
      • Dynamic language support: mysqld can now be started with Swedish or English (default) error messages.
      • New functions: INSERT(), RTRIM(), LTRIM() and FORMAT().
      • mysqldump now works correctly for all field types (even AUTO_INCREMENT). The format for SHOW FIELDS FROM tbl_name is changed so the Type column contains information suitable for CREATE TABLE. In previous releases, some CREATE TABLE information had to be patched when re-creating tables.
      • Some parser bugs from 3.19.5 (BLOB and TIMESTAMP) are corrected. TIMESTAMP now returns different date information depending on its create length.
      • Changed parser to allow a database, table or field name to start with a number or '_'.
      • All old C code from Unireg changed to C++ and cleaned up. This makes the daemon a little smaller and easier to understand.
      • A lot of small bug fixes done.
      • New `INSTALL' files (not final version) and some information regarding porting.

      D.8 Changes in release 3.19.x

      Version 3.19 is quite old now, and should be avoided if possible. This information is kept here for historical purposes only.

      D.8.1 Changes in release 3.19.5

      • Some new functions, some more optimization on joins.
      • Should now compile clean on Linux (2.0.x).
      • Added functions DATABASE(), USER(), POW(), LOG10() (needed for ODBC).
      • In a WHERE with an ORDER BY on fields from only one table, the table is now preferred as first table in a multi-join.
      • HAVING and IS NULL or IS NOT NULL now works.
      • A group on one column and a sort on a group function (SUM(), AVG()...) didn't work together. Fixed.
      • mysqldump: Didn't send password to server.

      D.8.2 Changes in release 3.19.4

      • Fixed horrible locking bug when inserting in one thread and reading in another thread.
      • Fixed one-off decimal bug. 1.00 was output as 1.0.
      • Added attribute 'Locked' to process list as info if a query is locked by another query.
      • Fixed full magic timestamp. Timestamp length may now be 14, 12, 10, 8, 6, 4 or 2 bytes.
      • Sort on some numeric functions could sort incorrectly on last number.
      • IF(arg,syntax_error,syntax_error) crashed.
      • Added functions CEILING(), ROUND(), EXP(), LOG() and SQRT().
      • Enhanced BETWEEN to handle strings.

      D.8.3 Changes in release 3.19.3

      • Fixed SELECT with grouping on BLOB columns not to return incorrect BLOB info. Grouping, sorting and distinct on BLOB columns will not yet work as expected (probably it will group/sort by the first 7 characters in the BLOB). Grouping on formulas with a fixed string size (use MID() on a BLOB) should work.
      • When doing a full join (no direct keys) on multiple tables with BLOB fields, the BLOB was garbage on output.
      • Fixed DISTINCT with calculated columns.

      D.9 Changes in release 3.11

      MySQL バージョン 3.11 は、MySQL がネット上で公開された初めてのバージョンです

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Porting.html0100644000175100001560000011531110021471264016076 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - E 他のシステムへの移植について Go to the first, previous, next, last section, table of contents.

      E 他のシステムへの移植について

      This appendix will help you port MySQL to other operationg systems. Do check the list of currently supported operating systems first. 「2.2.5 MySQL がサポートする OS」節参照. If you have created a new port of MySQL, please let us know so that we can list it here and on our web site (http://www.mysql.com/), recommending it to other users.

      Note: If you create a new port of MySQL, you are free to copy and distribute it under the GPL license, but it does not make you a copyright holder of MySQL.

      移植先のシステムには POSIX 仕様のスレッドライブラリが必要となります。 我々は Solaris 2.5 では Sun PThreads (2.4以前でサポートされていたネイティブthreadは良くなかった)を、 Linux では Xavier Leroy, Xavier.Leroy@inria.fr による LinuxThreads を使っています。

      良いネイティブスレッドを持たない新種の Unix に移植する場合、 多分もっとも大変な作業は MIT-pthreads を導入する部分です。 `mit-pthreads/README' と http://www.humanfactor.com/pthreads/をご覧下さい。

      MySQL の配布ファイルには MIT の Provenzano's Pthreads パッチ済みバージョン (http://www.mit.edu:8001/people/proven/pthreads.htmlをご覧下さい。) が含まれています。 これは POSIX 仕様の Threads を持たない OS に使用可能と思われます。

      もう1つのユーザレベル thread パッケージ、FSU Pthreads も使用可能と思われます (http://www.informatik.hu-berlin.de/~mueller/pthreads.htmlをご覧下さい。)。 これはSCOへの移植に使用可能です。

      そういった問題に関するテストやサンプルのプログラムを作成する場合には `mysys' ディレクトリの `thr_lock.c' と `thr_alarm.c' 等のプログラムをご覧下さい。

      移植にはサーバー、クライアントともに C++ コンパイラを必要とします (ちなみに我々はgccを使っています。SPARCWorks(C++)は試しました。)。 Irix ccも使用できることが確かめられています。

      クライアントしか必要無い場合は./configure --without-serverとコンパイルしてください。

      サーバのみコンパイルする方法は今のところありません。必要性が生じるまでは今のままです。

      `Makefile' か コンフィギャスクリプトに何らかの変更をする必要が生じたなら Automake と Autoconf を使わなくてはいけません。 ちなみに、我々は automake-1.2 と autoconf-2.12 を使っています。

      変更の手順は全て基本的なファイルからやり直す必要があります。 

      /bin/rm */.deps/*.P
/bin/rm -f config.cache
aclocal
autoheader
aclocal
automake
autoconf
./configure --with-debug=full --prefix='your installation directory'

# 上記手順によって生成されるmakefileファイル群はGNU make 3.75以上
# (以下、gmakeと記述します。)を必要とします。
gmake clean all install init-db

      新しい移植で問題が発生すればデバッグの必要が生じる場合もあります。

      「E.1 MySQL server のデバッグ」節参照.

      Note: mysqldのデバッグを開始する前にmysys/thr_alarmとmysys/thr_clockが動くかどうかチェックしてください。これにより貴方のインストールしたthread環境の動作可能性が多少でもあるのかどうかを確かめることができます。

      E.1 MySQL server のデバッグ

      もしあなたが MySQL のとても新しいある機能を使っている場合、 --skip-new (これは全く新しい、潜在的に危険な機能を無効にします) または --safe-mode (これは問題を生じさせるかもしれない多くの最適化を無効にします) オプションで mysqld を実行させることができます。 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

      もし mysqld が起動しないようなら、 `my.cnf' が無いかチェックしてください。 `my.cnf' の引数は mysqld --print-defaults でチェックできます。 また mysqld --no-defaults ... で起動することにより、 `my.cnf' を無視することが可能です。

      もし mysqld が CPU や メモリー を食い始めたり、``ハング'' したりするなら、 mysqladmin processlist status を使用して誰かが多くの時間のかかる クエリを実行しているか確かめることが出来ます。 パフォーマンスの問題や新しいクライアントが接続できないときの問題と もしあなたが考えるなら、 いくつかのウインドウで mysqladmin -i10 processlist status を 実行するのはよい考えでしょう。

      mysqladmin debug コマンドは使用中のロック、使用しているメモり、 クエリの使用の情報を、mysql ログファイルにいくつかダンプします これはいくつかの問題解決に役立ちます。 このコマンドは、 MySQL を デバッグ可能でコンパイルしていなくても、いくつかの役立つ情報も提供します。

      いくつかのテーブルでだんだん遅くなる問題であるなら、 OPTIMIZE TABLE か myisamchk でテーブルを修復し、最適化を試みるべきです。 遅いクエリは、 EXPLAIN でもチェックできます。 「4 データベース管理」節参照. You should also check the slow queries with EXPLAIN.

      このマニュアルの OS 固有の問題 の節も読むべきです。 「2.6 Operating System Specific Notes」節参照.

      E.1.1 Compiling MySQL for Debugging

      もしあるとても特殊な問題があれば、あなたは、いつも MySQL を デバッグするよう試みることができます。 これを行うには、 MySQL を --with-debug オプションか --with-debug=full オプション付きで configure しなくてはなりません。 MySQL がデバッギングを有効にしてコンパイルされているかを 知るには、 mysqld --help とします。 もし --debug フラグが リストされていればデバッグが有効です。 mysqladmin ver も mysqld のバージョンをリストできます。 この場合は mysql ... --debug と、バージョン番号に表示されるでしょう。

      gcc か egcs の場合、推奨する configure のラインは： 

      CC=gcc CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors \
   -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql \
   --with-debug --with-extra-charsets=complex

      This will avoid problems with the libstdc++ library and with C++ exceptions (many compilers have problems with C++ exceptions in threaded code) and compile a MySQL version with support for all character sets.

      If you suspect a memory overrun error, you can configure MySQL with --with-debug=full, which will install a memory allocation (SAFEMALLOC) checker. Running with SAFEMALLOC is however quite slow, so if you get performance problems you should start mysqld with the --skip-safemalloc option. This will disable the memory overrun checks for each call to malloc and free.

      If mysqld stops crashing when you compile it with --with-debug, you have probably found a compiler bug or a timing bug within MySQL. In this case you can try to add -g to the CFLAGS and CXXFLAGS variables above and not use --with-debug. If mysqld now dies, you can at least attach to it with gdb or use gdb on the core file to find out what happened.

      MySQL をデバッグで configure すると、自動で多くの安全な検査関数が enable になります。 これは mysqld の状態をモニターできます。 もしそれら関数がなにか ``予期せぬこと'' を発見したら、それらを stderr に書き出します。 これは safe_mysqld が受け取って error ログに 書き出します！ このことはどういうことかというと、 MySQL に予期せぬことが 起きた場合、まず最初にすべきことは、 MySQL をデバッグ有効にして configure することです！ （次に、もちろん、 mysql@lists.mysql.com に メールを送り、help を聞くことです。 全てのバグレポート、MySQL のバージョンに 関連する質問は、 mysqlbug スクリプトを使用してください！）

      In the Windows MySQL distribution, mysqld.exe is by default compiled with support for trace files.

      E.1.2 Creating Trace Files

      If the mysqld server doesn't start or if you can cause the mysqld server to crash quickly, you can try to create a trace file to find the problem.

      To do this you have to have a mysqld that is compiled for debugging. You can check this by executing mysqld -V. If the version number ends with -debug, it's compiled with support for trace files.

      Start the mysqld server with a trace log in `/tmp/mysqld.trace' (or `C:\mysqld.trace' on Windows):

      mysqld --debug

      On Windows you should also use the --standalone flag to not start mysqld as a service:

      In a DOS window do: 

      mysqld --debug --standalone

      After this you can use the mysql.exe command-line tool in a second DOS window to reproduce the problem. You can take down the above mysqld server with mysqladmin shutdown.

      Note that the trace file will get very big! If you want to have a smaller trace file, you can use something like:

      mysqld --debug=d,info,error,query,general,where:O,/tmp/mysqld.trace

      which only prints information with the most interesting tags in `/tmp/mysqld.trace'.

      If you make a bug report about this, please only send the lines from the trace file to the appropriate mailing list where something seems to go wrong! If you can't locate the wrong place, you can ftp the trace file, together with a full bug report, to ftp://support.mysql.com/pub/mysql/secret/ so that a MySQL developer can take a look a this.

      The trace file is made with the DBUG package by Fred Fish. 「E.3 The DBUG Package」節参照.

      E.1.3 Debugging mysqld under gdb

      ほとんどのシステムでは、もし mysqld がクラッシュするなら、 gdb から mysqld を起動させて多くの情報を得ることが可能です。

      Linux 上でのいくつかの gdb バージョンでは、 mysqld スレッドのデバッグを可能にする場合、 run --one-thread を使用しなくてはなりません。 この場合、一度にただ一つのactiveなスレッドだけを持つことになります。 We recommend you to upgrade to gdb 5.1 ASAP as thread debugging works much better with this version!

      When running mysqld under gdb, you should disable the stack trace with --skip-stack-trace to be able to catch segfaults within gdb.

      It's very hard to debug MySQL under gdb if you do a lot of new connections the whole time as gdb doesn't free the memory for old threads. You can avoid this problem by starting mysqld with -O thread_cache_size= 'max_connections +1'. In most cases just using -O thread_cache_size=5' will help a lot!

      If you want to get a core dump on Linux if mysqld dies with a SIGSEGV signal, you can start mysqld with the --core-file option. This core file can be used to make a backtrace that may help you find out why mysqld died: 

      shell> gdb mysqld core
gdb>   backtrace full
gdb>   exit

      「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

      もし Linux 上で gdb 4.17.x を使用しているなら、 `.gdb' ファイルを いかにしたがって、カレントのディレクトリーにインストールすべきです： 

      set print sevenbit off
handle SIGUSR1 nostop noprint
handle SIGUSR2 nostop noprint
handle SIGWAITING nostop noprint
handle SIGLWP nostop noprint
handle SIGPIPE nostop
handle SIGALRM nostop
handle SIGHUP nostop
handle SIGTERM nostop noprint

      If you have problems debugging threads with gdb, you should download gdb 5.x and try this instead. The new gdb version has very improved thread handling!

      以下は mysqld のデバッグ例です： 

      shell> gdb /usr/local/libexec/mysqld
gdb> run
...
backtrace full # mysqld がクラッシュした際、これを行います

      上記の出力を、 mysqlbug で作成したメールに含み、 そして mysql@lists.mysql.com. に送ってください。

      もし mysqld がハングするなら、 strace や /usr/proc/bin/pstack のような システムツールを使用して mysqld がどこでハングしているか 調べることができます。 

      strace /tmp/log libexec/mysqld

      もし Perl DBI を使用しているなら、 trace メソッド、あるいはDBI_TRACE 環境変数で デバッグ情報を有効にできます。 「8.2.2 The DBI Interface」節参照.

      E.1.4 Using a Stack Trace

      On some operating systems, the error log will contain a stack trace if mysqld dies unexpectedly. You can use this to find out where (and maybe why) mysqld died. 「4.9.1 The Error Log」節参照. To get a stack trace, you must not compile mysqld with the -fomit-frame-pointer option to gcc. 「E.1.1 Compiling MySQL for Debugging」節参照.

      If the error file contains something like the following: 

      mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died
Attemping backtrace. You can use the following information to find out
where mysqld died.  If you see no messages after this, something went
terribly wrong
stack range sanity check, ok, backtrace follows
0x40077552
0x81281a0
0x8128f47
0x8127be0
0x8127995
0x8104947
0x80ff28f
0x810131b
0x80ee4bc
0x80c3c91
0x80c6b43
0x80c1fd9
0x80c1686

      you can find where mysqld died by doing the following:

      1. Copy the above numbers to a file, for example `mysqld.stack'.
      2. Make a symbol file for the mysqld server: 
        nm -n libexec/mysqld > /tmp/mysqld.sym
        Note that many MySQL binary distributions comes with the above file, named mysqld.sym.gz. In this case you must unpack this by doing: 
        gunzip < bin/mysqld.sym.gz > /tmp/mysqld.sym
      3. Execute resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack. This will print out where mysqld died. If this doesn't help you find out why mysqld died, you should make a bug report and include the output from the above commend with the bug report. Note however that in most cases it will not help us to just have a stack trace to find the reason for the problem. To be able to locate the bug or provide a workaround, we would in most cases need to know the query that killed mysqld and preferable a test case so that we can repeat the problem! 「1.6.1.3 バグや問題を報告する方法」節参照.

      E.1.5 Using Log Files to Find Cause of Errors in mysqld

      --logを使用してmysqldを起動する際は、事前にmyisamchk を使用して全てのテーブルをチェックするようにしてください。 「4 データベース管理」節参照.

      もし mysqld が死んだりハングしたりするなら、 mysqld を --log で起動すべきです。 再び mysqld が死んだら、 あなたはログファイル中の、 mysqld を kill するクエリをチェックします。

      If you are using --log without a file name, the log is stored in the database directory as 'hostname'.log In most cases it's the last query in the log file that killed mysqld, but if possible you should verify this by restarting mysqld and executing the found query from the mysql command-line tools. If this works, you should also test all complicated queries that didn't complete.

      mysqld が適切にインデックスを使用するのに時間がとてもかかる全ての SELECT 文を EXPLAIN で実行することを試みます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.

      You can find the queries that take a long time to execute by starting mysqld with --log-slow-queries. 「4.9.5 The Slow Query Log (3.23.28以上)」節参照.

      もしエラーログファイル(通常 `hostname.err' という名前)中に mysqld restarted という文があるなら、 mysqld を失敗させるクエリを見つけます。 もしこれが起きるなら、myisamchk ( 「4 データベース管理」節参照) で 全てのテーブルをチェックし、MySQL ログファイルにあるそのクエリをテストすべきです。 もしそのようなクエリをみつけたなら、まず最初に最新の MySQL にアップグレード してみてください。 もしそれでもだめで、かつ mysql メーリングリストの アーカイブにもなにも見つけることが出来なかったなら、 mysql@lists.mysql.com に バグレポートを出すべきです。 メーリングリストのアーカイブへのリンクは http://www.mysql.com/.

      If you have started mysqld with myisam-recover, MySQL will automatically check and try to repair MyISAM tables if they are marked as 'not closed properly' or 'crashed'. If this happens, MySQL will write an entry in the hostname.err file 'Warning: Checking table ...' which is followed by Warning: Repairing table if the table needs to be repaired. If you get a lot of these errors, without mysqld having died unexpectedly just before, then something is wrong and needs to be investigated further. 「4.1.1 mysqld コマンド行オプション」節参照.

      It's of course not a good sign if mysqld did died unexpectedly, but in this case one shouldn't investigate the Checking table... messages but instead try to find out why mysqld died.

      E.1.6 Making a Test Case When You Experience Table Corruption

      もし不正なテーブルをえたり、 mysqld が常にいくつかの update コマンドで 失敗するなら、以下のようにしてこのバグの再現をテストします：

      • Take down the MySQL daemon (with mysqladmin shutdown).
      • Make a backup of the tables (to guard against the very unlikely case that the repair will do something bad).
      • myisamchk -s database/*.MYI で全テーブルをチェック. myisamchk -r database/table.MYI で悪いテーブルを修正。
      • Make a second backup of the tables.
      • Remove (or move away) any old log files from the MySQL data directory if you need more space.
      • Start mysqld with --log-bin. 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照. If you want to find a query that crashes mysqld, you should use --log --log-bin.
      • 壊れたテーブルを得た時、mysqld server を停止。
      • バックアップをリストア
      • mysqld server を --log-bin なしで 起動。
      • Re-execute the commands with mysqlbinlog update-log-file | mysql. The update log is saved in the MySQL database directory with the name hostname-bin.#.
      • If the tables are corrupted again or you can get mysqld to die with the above command, you have found reproducible bug that should be easy to fix! FTP the tables and the binary log to ftp://support.mysql.com/pub/mysql/secret/ and send a mail to bugs@lists.mysql.com or (if you are a support customer) to support@mysql.com about the problem and the MySQL team will fix it as soon as possible.

      You can also use the script mysql_find_rows to just execute some of the update statements if you want to narrow down the problem.

      E.2 Debugging a MySQL client

      To be able to debug a MySQL client with the integrated debug package, you should configure MySQL with --with-debug or --with-debug=full. 「2.3.3 典型的な configure オプション」節参照.

      Before running a client, you should set the MYSQL_DEBUG environment variable: 

      shell> MYSQL_DEBUG=d:t:O,/tmp/client.trace
shell> export MYSQL_DEBUG

      This causes clients to generate a trace file in `/tmp/client.trace'.

      If you have problems with your own client code, you should attempt to connect to the server and run your query using a client that is known to work. Do this by running mysql in debugging mode (assuming you have compiled MySQL with debugging on): 

      shell> mysql --debug=d:t:O,/tmp/client.trace

      This will provide useful information in case you mail a bug report. 「1.6.1.3 バグや問題を報告する方法」節参照.

      If your client crashes at some 'legal' looking code, you should check that your `mysql.h' include file matches your mysql library file. A very common mistake is to use an old `mysql.h' file from an old MySQL installation with new MySQL library.

      E.3 The DBUG Package

      The MySQL server and most MySQL clients are compiled with the DBUG package originally made by Fred Fish. When one has configured MySQL for debugging, this package makes it possible to get a trace file of what the program is debugging. 「E.1.2 Creating Trace Files」節参照.

      One uses the debug package by invoking the program with the --debug="..." or the -#... option.

      Most MySQL programs has a default debug string that will be used if you don't specify an option to --debug. The default trace file is usually /tmp/programname.trace on Unix and \programname.trace on Windows.

      The debug control string is a sequence of colon separated fields as follows: 

      <field_1>:<field_2>:...:<field_N>

      Each field consists of a mandatory flag character followed by an optional "," and comma-separated list of modifiers: 

      flag[,modifier,modifier,...,modifier]

      The currently recognised flag characters are:

      Flag Description
      d Enable output from DBUG_<N> macros for the current state. May be followed by a list of keywords which selects output only for the DBUG macros with that keyword. An empty list of keywords implies output for all macros.
      D Delay after each debugger output line. The argument is the number of tenths of seconds to delay, subject to machine capabilities. That is, -#D,20 is delay two seconds.
      f Limit debugging and/or tracing, and profiling to the list of named functions. Note that a null list will disable all functions. The appropriate "d" or "t" flags must still be given, this flag only limits their actions if they are enabled.
      F Identify the source file name for each line of debug or trace output.
      i Identify the process with the pid or thread id for each line of debug or trace output.
      g Enable profiling. Create a file called 'dbugmon.out' containing information that can be used to profile the program. May be followed by a list of keywords that select profiling only for the functions in that list. A null list implies that all functions are considered.
      L Identify the source file line number for each line of debug or trace output.
      n Print the current function nesting depth for each line of debug or trace output.
      N Number each line of dbug output.
      o Redirect the debugger output stream to the specified file. The default output is stderr.
      O As O but the file is really flushed between each write. When needed the file is closed and reopened between each write.
      p Limit debugger actions to specified processes. A process must be identified with the DBUG_PROCESS macro and match one in the list for debugger actions to occur.
      P Print the current process name for each line of debug or trace output.
      r When pushing a new state, do not inherit the previous state's function nesting level. Useful when the output is to start at the left margin.
      S Do function _sanity(_file_,_line_) at each debugged function until _sanity() returns something that differs from 0. (Mostly used with safemalloc to find memory leaks)
      t Enable function call/exit trace lines. May be followed by a list (containing only one modifier) giving a numeric maximum trace level, beyond which no output will occur for either debugging or tracing macros. The default is a compile time option.

      Some examples of debug control strings which might appear on a shell command-line (the "-#" is typically used to introduce a control string to an application program) are: 

      -#d:t
-#d:f,main,subr1:F:L:t,20
-#d,input,output,files:n
-#d:t:i:O,\\mysqld.trace

      In MySQL, common tags to print (with the d option) are: enter,exit,error,warning,info and loop.

      E.4 Locking methods

      Currently MySQL only supports table locking for ISAM/MyISAM and HEAP tables, page-level locking for BDB tables and row-level locking for InnoDB tables. 「5.3.1 MySQL はどのようにテーブルをロックするか」節参照. With MyISAM tables one can freely mix INSERT and SELECT without locks, if the INSERTs are non-conflicting (i.e. whenever they append to the end of the table file rather than filling freespace from deleted rows/data).

      Starting in version 3.23.33, you can analyse the table lock contention on your system by checking Table_locks_waited and Table_locks_immediate environment variables.

      To decide if you want to use a table type with row-level locking, you will want to look at what the application does and what the select/update pattern of the data is.

      Pros for row locking:

      • Fewer lock conflicts when accessing different rows in many threads.
      • Fewer changes for rollbacks.
      • Makes it possible to lock a single row a long time.

      Cons:

      • Takes more memory than page level or table locks.
      • Is slower than page level or table locks when used on a big part of the table, because one has to do many more locks.
      • Is definitely much worse than other locks if you do often do GROUP BY on a large part of the data or if one has to often scan the whole table.
      • With higher level locks one can also more easily support locks of different types to tune the application as the lock overhead is less notable as for row level locks.

      Table locks are superior to page level / row level locks in the following cases:

      • Mostly reads
      • Read and updates on strict keys; this is where one updates or deletes a row that can be fetched with one key read: 
        UPDATE table_name SET column=value WHERE unique_key#
DELETE FROM table_name WHERE unique_key=#
      • SELECT combined with INSERT (and very few UPDATEs and DELETEs).
      • Many scans / GROUP BY on the whole table without any writers.

      Other options than row / page level locking:

      Versioning (like we use in MySQL for concurrent inserts) where you can have one writer at the same time as many readers. This means that the database/table supports different views for the data depending on when one started to access it. Other names for this are time travel, copy on write or copy on demand.

      Copy on demand is in many case much better than page or row level locking; the worst case does, however, use much more memory than when using normal locks.

      Instead of using row level locks one can use application level locks (like get_lock/release_lock in MySQL). This works of course only in well-behaved applications.

      In many cases one can do an educated guess which locking type is best for the application, but generally it's very hard to say that a given lock type is better than another; everything depends on the application and different part of the application may require different lock types.

      Here are some tips about locking in MySQL:

      Most web applications do lots of selects, very few deletes, updates mainly on keys, and inserts in some specific tables. The base MySQL setup is very well tuned for this.

      Concurrent users are not a problem if one doesn't mix updates with selects that need to examine many rows in the same table.

      If one mixes inserts and deletes on the same table then INSERT DELAYED may be of great help.

      One can also use LOCK TABLES to speed up things (many updates within a single lock is much faster than updates without locks). Splitting thing to different tables will also help.

      If you get speed problems with the table locks in MySQL, you may be able to solve these by converting some of your tables to InnoDB or BDB tables. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. 「7.6 BDB or BerkeleyDB Tables」節参照.

      The optimisation section in the manual covers a lot of different aspects of how to tune applications. 「5.2.12 最適化に関するその他の助言」節参照.

      E.5 Comments about RTS threads

      I have tried to use the RTS thread packages with MySQL but stumbled on the following problems:

      They use an old version of a lot of POSIX calls and it is very tedious to make wrappers for all functions. I am inclined to think that it would be easier to change the thread libraries to the newest POSIX specification.

      Some wrappers are already written. See `mysys/my_pthread.c' for more info.

      At least the following should be changed:

      pthread_get_specific should use one argument. sigwait should take two arguments. A lot of functions (at least pthread_cond_wait, pthread_cond_timedwait) should return the error code on error. Now they return -1 and set errno.

      Another problem is that user-level threads use the ALRM signal and this aborts a lot of functions (read, write, open...). MySQL should do a retry on interrupt on all of these but it is not that easy to verify it.

      The biggest unsolved problem is the following:

      To get thread-level alarms I changed `mysys/thr_alarm.c' to wait between alarms with pthread_cond_timedwait(), but this aborts with error EINTR. I tried to debug the thread library as to why this happens, but couldn't find any easy solution.

      If someone wants to try MySQL with RTS threads I suggest the following:

      • Change functions MySQL uses from the thread library to POSIX. This shouldn't take that long.
      • Compile all libraries with the -DHAVE_rts_threads.
      • Compile thr_alarm.
      • If there are some small differences in the implementation, they may be fixed by changing `my_pthread.h' and `my_pthread.c'.
      • Run thr_alarm. If it runs without any ``warning'', ``error'' or aborted messages, you are on the right track. Here is a successful run on Solaris: 
        Main thread: 1
Thread 0 (5) started
Thread: 5  Waiting
process_alarm
Thread 1 (6) started
Thread: 6  Waiting
process_alarm
process_alarm
thread_alarm
Thread: 6  Slept for 1 (1) sec
Thread: 6  Waiting
process_alarm
process_alarm
thread_alarm
Thread: 6  Slept for 2 (2) sec
Thread: 6  Simulation of no alarm needed
Thread: 6  Slept for 0 (3) sec
Thread: 6  Waiting
process_alarm
process_alarm
thread_alarm
Thread: 6  Slept for 4 (4) sec
Thread: 6  Waiting
process_alarm
thread_alarm
Thread: 5  Slept for 10 (10) sec
Thread: 5  Waiting
process_alarm
process_alarm
thread_alarm
Thread: 6  Slept for 5 (5) sec
Thread: 6  Waiting
process_alarm
process_alarm

...
thread_alarm
Thread: 5  Slept for 0 (1) sec
end

      E.6 スレッドパッケージ間の違いは何？

      MySQL は使用されるスレッドパッケージに非常に依存しています。 そのため、MySQL に良いプラットフォームを選択する時には、 スレッドパッケージが非常に重要です。

      少なくとも3つのタイプのスレッドパッケージがあります：

      • シングルプロセス内のユーザスレッド。 スレッド切替えはアラームで管理され、 スレッドライブラリはロックを伴う非スレッド安全関数のすべてを管理します。 動作中スレッドがデータを待つ必要がある場合、read, write そして select は、 通常、他のスレッドに切替えるスレッド固有の select で管理されます。 もしユーザ・スレッドパッケージが標準ライブラリ (FreeBSD と BSDI スレッド) に 統合されているなら、スレッドパッケージのオーバーヘッドは、全ての非安全コールを マップしなければならないスレッドパッケージ(MIT-スレッド, FSU-スレッド, RTS スレ ッド) よりも少なくなります。 他の環境(例えば SCO)では、全てのシステムコールはスレッド安全なので、 マッピングはとても簡単に行なわれます(SCO 上の FSU-スレッド)。 Downside: 全てのマップされるコールは少し時間がかかり、全ての状況を 処理可能にすることは、とても困難です。 通常、スレッドパッケージによって処理できないシステムコールがいくつかあります (MIT-スレッドとソケットのように)。 スレッドスケジューリングは常に最 適というわけではあ りません。
      • 別プロセスのユーザスレッド。 スレッド切替えはカーネルによって行なわれ、全てのデータはスレッド間で共有されます。 スレッドパッケージは、スレッ ド間のデータ共有を許可するために標準スレッドコール を管理します。 LinuxThreads はこの方法を使用しています。 Downside: 多くのプロセス。スレッド生成は遅いです。 もし一つのスレッドが死ぬと、残りは通常ハングして残り、再起動前に それら全て を kill する必要があります。スレッド切替えはいくらか高価(expensive)です。
      • カーネルスレッド。 スレッド切替えはスレッドライブラリかカーネルによって処理され、 とても速いです。 全ては一つのプロセス内で行なわれますが、 いくつかのシステムでは、ps が異なったスレッドを示します。 もし一つのスレッドがアボートした場合、プロセス全体がアボートします。 多くのシステムコールはスレッド安全で、オーバーヘッドはとても少ないです。 Solaris, HP-UX, AIX そして OSF1 がカーネルスレッドを持っています。

      いくつかのシステムでは、カーネルスレッドは、システムライブラリ内で、 ユーザレベルスレッドの統合によって管理されます。 この場合、スレッド切替えはスレッドライブラリによってだけ行なわれ、 カーネルは実際には 'thread aware' ではありません。

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Problems.html0100644000175100001560000024425710021471264016253 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - A Problems and Common Errors Go to the first, previous, next, last section, table of contents.

      A Problems and Common Errors

      This chapter lists some common problems and error messages that users have run into. You will learn how to figure out what the problem is, and what to do to solve it. You will also find proper solutions to some common problems.

      A.1 How to Determine What Is Causing Problems

      When you run into problems, the first thing you should do is to find out which program / piece of equipment is causing problems:

      • If you have one of the following symptoms, then it is probably a hardware (like memory, motherboard, CPU, or hard disk) or kernel problem:
        • The keyboard doesn't work. This can normally be checked by pressing Caps Lock. If the Caps Lock light doesn't change you have to replace your keyboard. (Before doing this, you should try to reboot your computer and check all cables to the keyboard.)
        • The mouse pointer doesn't move.
        • The machine doesn't answer to a remote machine's pings.
        • Different, unrelated programs don't behave correctly.
        • If your system rebooted unexpectedly (a faulty user level program should never be able to take down your system).
        In this case you should start by checking all your cables and run some diagnostic tool to check your hardware! You should also check if there are any patches, updates, or service packs for your operating system that could likely solve your problems. Check also that all your libraries (like glibc) are up to date. It's always good to use a machine with ECC memory to discover memory problems early!
      • If your keyboard is locked up, you may be able to fix this by logging into your machine from another machine and execute kbd_mode -a on it.
      • Please examine your system log file (/var/log/messages or similar) for reasons for your problems. If you think the problem is in MySQL then you should also examine MySQL's log files. 「4.9.3 更新ログ」節参照.
      • If you don't think you have hardware problems, you should try to find out which program is causing problems. Try using top, ps, taskmanager, or some similar program, to check which program is taking all CPU or is locking the machine.
      • Check with top, df, or a similar program if you are out of memory, disk space, open files, or some other critical resource.
      • If the problem is some runaway process, you can always try to kill it. If it doesn't want to die, there is probably a bug in the operating system.

      If after you have examined all other possibilities and you have concluded that it's the MySQL server or a MySQL client that is causing the problem, it's time to do a bug report for our mailing list or our support team. In the bug report, try to give a very detailed description of how the system is behaving and what you think is happening. You should also state why you think it's MySQL that is causing the problems. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you examine your system. Use the 'cut and paste' method for any output and/or error messages from programs and/or log files!

      Try to describe in detail which program is not working and all symptoms you see! We have in the past received many bug reports that just state "the system doesn't work". This doesn't provide us with any information about what could be the problem.

      If a program fails, it's always useful to know:

      • Has the program in question made a segmentation fault (core dumped)?
      • Is the program taking up the whole CPU? Check with top. Let the program run for a while, it may be evaluating something heavy.
      • If it's the mysqld server that is causing problems, can you do mysqladmin -u root ping or mysqladmin -u root processlist?
      • What does a client program say (try with mysql, for example) when you try to connect to the MySQL server? Does the client jam? Do you get any output from the program?

      When sending a bug report, you should of follow the outlines described in this manual. 「1.6.1.2 質問またはバグ報告」節参照.

      A.2 MySQL 使用時のよくあるいくつかのエラー

      This section lists some errors that users frequently get. You will find descriptions of the errors, and how to solve the problem here.

      A.2.1 Access denied エラー

      「4.2.11 何故 Access denied エラーになるのか」節参照. 「4.2.6 特権システムはどのように動くか？」節参照.

      A.2.2 MySQL server has gone away エラー

      このセクションは Lost connection to server during query エラーに関することもカバーします。

      MySQL server has gone away エラーのもっとも一般的な理由は、サーバ がタイムアウトで接続をクローズしたことです。デフォルトでは、何も起きない 場合、サーバは 8 時間後に接続をクローズします。 この時間は mysqld 起動時の wait_timeout 変数に与えることにより、変 更できます。

      Another common reason to receive the MySQL server has gone away error is because you have issued a ``close'' on your MySQL connection and then tried to run a query on the closed connection.

      mysqladmin version を実行することで MySQL が死んでいるかどうか、 また uptime はどれぐらいか、チェックできます。

      スクリプトの場合は、自動的に再接続するためにクライアントからクエリを再発 行する必要があります。

      この場合、通常これらのエラーコードを得ます: (OS 依存です):

      CR_SERVER_GONE_ERROR クライアントがサーバーに問い合わせを送る ことができなかった server.
      CR_SERVER_LOST クライアントがサーバーに書き込みを行ったときに はエラーは無かったけれども、問い合わせに対して完全に回答が返ってこない

      You will also get this error if someone has kills the running thread with kill #threadid#.

      You can check that the MySQL hasn't died by executing mysqladmin version and examining the uptime. If the problem is that mysqld crashed you should concentrate one finding the reason for the crash. You should in this case start by checking if issuing the query again will kill MySQL again. 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

      間違っているか大きすぎるクエリをサーバに送った場合にもこのエラーが発生し ます。mysqld が間違ったブロックを得た場合、クライアントの何かが間違った と見なし、接続をクローズします。大きなクエリが必要な場合、例えば大きな BLOB で働かせる場合は、mysqld をオプション -O max_query_size=# (デフォルト 1M) で起動することでクエリ制限を増加できます。拡張メモリ はオンデマンドで割り当てられます。そのため、mysqld は大きなクエリを発行し た時や大きな結果行を返す必要のある時だけ、多くのメモリを割り当てます！

      You will also get a lost connection if you are sending a packet >= 16M if your client is older than 4.0.8 and your server is 4.0.8 and above, or the other way around.

      If you want to make a bug report regarding this problem, be sure that you include the following information:

      • Include information if MySQL died or not. (You can find this in the hostname.err file. 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.
      • If a specific query kills mysqld and the involved tables where checked with CHECK TABLE before you did the query, can you do a test case for this? 「E.1.6 Making a Test Case When You Experience Table Corruption」節参照.
      • What is the value of the wait_timeout variable in the MySQL server ? mysqladmin variables gives you the value of this
      • Have you tried to run mysqld with --log and check if the issued query appears in the log ?

      「1.6.1.2 質問またはバグ報告」節参照.

      A.2.3 Can't connect to [local] MySQL server エラー

      UNIX 上の MySQL クライアントは mysqld サーバに2つの異なる方法で 接続できます: UNIX ソケット, これはファイルシステム上のファイル(デフォルト `/tmp/mysql.sock')を通して接続します。または TCP/IP, これはポート番 号を通して接続します。Unix ソケットは TCP/IP よりも速いですが、サーバと 同じコンピュータから接続する時しか使えません。UNIX ソケットは、ホスト名 を指定しない場合か、特別なホスト名 localhost を指定した場合に使用され ます。

      On Windows, if the mysqld server is running on 9x/Me, you can connect only via TCP/IP. If the server is running on NT/2000/XP and mysqld is started with --enable-named-pipe, you can also connect with named pipes. The name of the named pipe is MySQL. If you don't give a hostname when connecting to mysqld, a MySQL client will first try to connect to the named pipe, and if this doesn't work it will connect to the TCP/IP port. You can force the use of named pipes on Windows by using . as the hostname.

      (2002) Can't connect to ... エラーは、通常、MySQL サーバーが システム上に走っていないか、あなたが、間違ったソケットファイルや TCP/IP ポートを使用して mysqld に接続しようとする場合におきます。

      サーバー上に mysqld というプロセスが走っているか ( ps を使用して。 Windows の場合はタスクマネージャでみて) 確認することから開始してください！ 「2.4.2 MySQL サーバー起動時の問題」節参照.

      mysqld プロセスが走っているなら、違う接続を試すことでサーバーを 確認することができます（もちろん、ポート番号とソケットのパスはあなたが セットアップしたものとは違うでしょう）： 

      shell> mysqladmin version
shell> mysqladmin variables
shell> mysqladmin -h `hostname` version variables
shell> mysqladmin -h `hostname` --port=3306 version
shell> mysqladmin -h 'ip for your host' version
shell> mysqladmin --protocol=socket --socket=/tmp/mysql.sock version

      hostname コマンドはフォワードクオートでなくバッククオテーションで 囲んでいることに注意してください； これは ホスト名 (カレントのホスト名) を mysqladmin コマンドに与えます。

      Can't connect to local MySQL server エラーが起こりうる理由として：

      • mysqld is not running.
      • MIT-pthreads を使用するシステム上で実行している。 ネイティブスレッドを持たないシステム上で実行している場合 mysqld は MIT-pthreads パッケージを使用します。 「2.2.5 MySQL がサポートする OS」節参照. MIT-pthreads スレッドは UNIX ソケットをサポートしません。 そのため、サーバに接続する時は常にホスト名を与える必要があります。 サーバーへの接続をチェックするために、以下を試してください： 
        shell> mysqladmin -h `hostname` version
      • 誰かが mysqld が使用する UNIX ソケット を削除した (default `/tmp/mys qld.sock'). だれかが cron で MySQL ソケットを削除しているかもしれません。(例 えば `/tmp' ディレクトリから古いファイルを削除するようなクローンで)。 いつでも mysqladmin version を実行して mysqladmin が使用するソケットが本当に存在するかをチェックできます。 この場合の修正は、`mysqld.sock' を消さないように cron を変更するか、 またはソケットをどこか他の場所に移すことです。 「A.4.5 MySQL ソケットファイル `/tmp/mysql.sock' を変更する方法、削除から守る方法」節参照.
      • --socket=/path/to/socket オプションで mysqld サーバーを起動できます。 もしサーバーのソケットのパスを変えた場合、MySQL クライアントに、新しい パスを教えなければなりません。 「A.4.5 MySQL ソケットファイル `/tmp/mysql.sock' を変更する方法、削除から守る方法」節参照.
      • Linux を使用していてスレッドが一つ死んだとき（コアダンプした）。 この場合、他の mysqld スレッドをキルしなければなりません。 たとえば、mysql_zap スクリプトを、新しく MySQL サーバーを 起動する前に実行します。 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.
      • You may not have read and write privilege to either the directory that holds the socket file or privilege to the socket file itself. In this case you have to either change the privilege for the directory / file or restart mysqld so that it uses a directory that you can access.

      もし Can't connect to MySQL server on some_hostname エラーの場合, 何が問題なのかを見つけるために、以下の手順を踏みます：

      • もし telnet your-host-name tcp-ip-port-number を実行すると サーバーがアップするなら、 RETURN を何回かたたいてください。 もしこのポートで MySQL サーバーが走っているなら、 走っている MySQL サーバーのバージョンナンバーを含んだ レスポンスが得られるはずです。 もし telnet: Unable to connect to remote host: Connection refused のような エラーになったならば、このポートを使用しているサーバーはありません。
      • ローカルのマシンの mysqld デーモンに接続してみてください。 mysqldmin variables で、mysqld が使用するように指定された TCP/IP ポート(変数 port)をチェックしてください。
      • mysqld サーバーが --skip-networking オプションで起動されていないか 確認してください。

      A.2.4 Host '...' is blocked エラー

      以下のエラーの場合： 

      Host 'hostname' is blocked because of many connection errors.
Unblock with 'mysqladmin flush-hosts'

      これは mysqld が多くの 'hostname' ホストからの接続エラー(max _connect_errors) を受けた場合に発生します。 この max_connect_errors 大量発生後、mysqld は何か(クラッカーによる サーバーへのアタックなど)が起こったと判断し、このホストからの接続をいっさい拒否 するようにします。 これを解除するには、mysqladmin flush-hosts コマンドを実行します。

      デフォルトでは、10回の接続エラーが発生した場合に、mysqld はそのホストを拒 否します。 この値は以下のようにして簡単に変更できます： 

      shell> safe_mysqld -O max_connect_errors=10000 &

      もしこのエラーがあるホストに対して発生するならば、まず最初にそのホストからの TCP /IP 接続に不具合がないかチェックしてください。 もし TCP/IP 接続が動作していないようなら、 max_connect_errors 値を増やす ことはよくないことです！

      A.2.5 Too many connections エラー

      もし MySQL に接続しようとして Too many connections となった場合、 これは既に max_connections 分、クライアントから mysqld サーバーへの 接続が行われています。

      もしデフォルトの100よりも多い接続を必要とするならば、 max_connections 変数に多くの値を与えて、mysqld を リスタートしなくてはなりません。

      実際は、mysqld は (max_connections+1) 個のクライアントからの接続を 許しています。 最後の１個は、 SUPER 権限 (version4.0.2以上。未満は PROCESS 権限)を もつユーザーのために取ってあります。 By not giving this privilege to normal users (they shouldn't need this), an administrator with this privilege can log in and use SHOW PROCESSLIST to find out what could be wrong. 「4.5.6.6 SHOW PROCESSLIST」節参照.

      The maximum number of connects MySQL is depending on how good the thread library is on a given platform. Linux or Solaris should be able to support 500-1000 simultaneous connections, depending on how much RAM you have and what your clients are doing.

      A.2.6 Some non-transactional changed tables couldn't be rolled back エラー

      もし ROLLBACK を試みたときに Warning: Some non-transactional changed tables couldn't be rolled back エラー/警告が出た場合、これは、あなたが使用しているテーブルがトランザクションを サポートしていないということです。 これらの非トランザクションのテーブルは ROLLBACK によって、何の影響も受けません。

      The most typical case when this happens is when you have tried to create a table of a type that is not supported by your mysqld binary. If mysqld doesn't support a table type (or if the table type is disabled by a startup option) , it will instead create the table type with the table type that is most resembles to the one you requested, probably MyISAM.

      以下の SQL 文でテーブルの型をチェックできます:

      SHOW TABLE STATUS LIKE 'table_name'. 「4.5.6.2 SHOW TABLE STATUS」節参照.

      You can check the extensions your mysqld binary supports by doing:

      show variables like 'have_%'. 「4.5.6.4 SHOW VARIABLES」節参照.

      A.2.7 Out of memory エラー

      クエリを行って、次のエラーのようなものを得た場合: 

      mysql: Out of memory at line 42, 'malloc.c'
mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k)
ERROR 2008: MySQL client ran out of memory

      エラーは MySQL クライアント mysql に関係することに注意してください。 エラーの理由は単純で、クライアントが結果全体を格納するのに十分なメモリを持っ ていないことです。

      この問題を解決するにあたり、まず最初にクエリーが正しいか確認してください。 そのクエリーは大量の結果を返すものでしょうか？ もしそうなら、mysql --quick を使用してください。 これは結果を取り出すために mysql_use_result() を使用します。 これはクライアントのロード不足を補います(サーバーより多い領域は取れません)。

      A.2.8 Packet too large エラー

      MySQL クライアントが max_allowed_packet よりも大きなブロックを mysqld サーバーから得た時、Packet too large エラーを発します。

      In MySQL 3.23 the biggest possible packet is 16M (due to limits in the client/server protocol). In MySQL 4.0.1 and up, this is only limited by the amount on memory you have on your server (up to a theoretical maximum of 2G).

      A communication packet is a single SQL statement sent to the MySQL server or a single row that is sent to the client.

      MySQL クライアントや mysqld サーバーが max_allowed_packet バイトより 大きなパケットを受け取ったた場合、 Packet too large エラーを発して 接続を閉じます。 いくつかのクライアントでは、 Lost connection to MySQL server during query エラーも出すでしょう。

      クライアントとサーバーは、自身の max_allowed_packet 変数を持っています。 もし大きなパケットを扱いたい場合には、クライアントとサーバーの両方の max_allowed_packet 値を増やしてください。

      It's safe to increase this variable as memory is only allocated when needed; this variable is more a precaution to catch wrong packets between the client/server and also to ensure that you don't accidentally use big packets so that you run out of memory.

      If you are using the mysql client, you may specify a bigger buffer by starting the client with mysql --set-variable=max_allowed_packet=8M. Other clients have different methods to set this variable. Please note that --set-variable is deprecated since MySQL 4.0, just use --max-allowed-packet=8M instead.

      You can use the option file to set max_allowed_packet to a larger size in mysqld. For example, if you are expecting to store the full length of a MEDIUMBLOB into a table, you'll need to start the server with the set-variable=max_allowed_packet=16M option.

      A.2.9 Communication Errors / Aborted Connection

      MySQL 3.23.40 からは、mysqld を --warnings オプションで たち上げた時にだけ、Aborted connection エラーを出力することが可能です。

      もし以下のようなエラーがエラーログファイルに記録されていたら、 

      010301 14:38:23  Aborted connection 854 to db: 'users' user: 'josh'

      「4.9.1 The Error Log」節参照.

      これは以下が起きたことを示します：

      • クライアントプログラムが終了前に mysql_close() を呼び出さなかった。
      • クライアントが wait_timeout か interactive_timeout 以上、いかなるリクエストもしない状態だった。 「4.5.6.4 SHOW VARIABLES」節参照. 「4.5.6.4 SHOW VARIABLES」節参照.
      • クライアントプログラムが転送の途中にプログラムを終了した

      上記が起きたときには、サーバーは Aborted_clients 変数を増やします。

      サーバー変数 Aborted_connects は以下の時に増えます：

      • コネクションパケットが正しい情報を含んでいなかった時
      • ユーザーがデータベースに接続する権限を持たなかった時
      • あるユーザーが間違ったパスワードを使用した時
      • コネクションパケットを得る際に、 connect_timeout 秒以上 かかった時 「4.5.6.4 SHOW VARIABLES」節参照.

      Note that the above could indicate that someone is trying to break into your database!

      「4.5.6.4 SHOW VARIABLES」節参照.

      Other reasons for problems with Aborted clients / Aborted connections.

      • Usage of duplex Ethernet protocol, both half and full with Linux. Many Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file via ftp between these two machines. If a transfer goes in burst-pause-burst-pause ... mode then you are experiencing a Linux duplex syndrome. The only solution to this problem is switching off either half or full duplex mode on hubs and switches, and testing the results to decide on the best setting.
      • Some problem with the thread library that causes interrupts on reads.
      • Badly configured TCP/IP.
      • Faulty Ethernets or hubs or switches, cables ... This can be diagnosed properly only by replacing hardware.
      • max_allowed_packet is too small or queries require more memory than you have alloacated for mysqld. 「A.2.8 Packet too large エラー」節参照.

      A.2.10 The table is full エラー

      • このエラーは、古い MySQL バージョン(before 3.23.0)において、 メモリ内一時テーブルが tmp_table_size よりも大きくなっ た時に発生します。この問題を回避するために、mysqld のオプション -O tmp_table_size=# で増加、または、SQL オプション BIG_TABLES (ver.4.0.3未満では SQL_BIG_TABLES ) を問題のクエリの前に使用できます。 「5.5.6 SET 構文」節参照. You can also start mysqld with the --big-tables option. This is exactly the same as using BIG_TABLES for all queries. In MySQL Version 3.23, in-memory temporary tables will automatically be converted to a disk-based MyISAM table after the table size gets bigger than tmp_table_size.
      • You are using InnoDB tables and run out of room in the InnoDB tablespace. In this case the solution is to extend the InnoDB tablespace.
      • You are using ISAM or MyISAM tables on an OS that only supports files of 2G in size and you have hit this limit for the data or index file.
      • You are using MyISAM tables and the needed data or index size is bigger than what MySQL has allocated pointers for. (If you don't specify MAX_ROWS to CREATE TABLE MySQL will only allocate pointers to hold 4G of data). You can check the maximum data/index sizes by doing 
        SHOW TABLE STATUS FROM database LIKE 'table_name';
        or using myisamchk -dv database/table_name. If this is the problem, you can fix it by doing something like: 
        ALTER TABLE table_name MAX_ROWS=1000000000 AVG_ROW_LENGTH=nnn;
        You only have to specify AVG_ROW_LENGTH for tables with BLOB/TEXT fields as in this case MySQL can't optimise the space required based only on the number of rows.

      A.2.11 Can't create/write to file エラー

      If you get an error for some queries of type: 

      Can't create/write to file '\\sqla3fe_0.ism'.

      this means that MySQL can't create a temporary file for the result set in the given temporary directory. (The above error is a typical error message on Windows, and the Unix error message is similar.) The fix is to start mysqld with --tmpdir=path or to add to your option file: 

      [mysqld]
tmpdir=C:/temp

      assuming that the `c:\\temp' directory exists. 「4.1.2 `my.cnf' オプションファイル」節参照.

      Check also the error code that you get with perror. One reason may also be a disk full error; 

      shell> perror 28
Error code  28:  No space left on device

      A.2.12 Commands out of sync Error in Client

      Commands out of sync; you can't run this command now をクライアン トコード中で得た場合、クライアント関数を間違った順番で呼び出しました！

      これは例えば、mysql_use_result() を使用していて、mysql_free_result( ) を行う前に新しいクエリの実行を試みた場合に発生します。これはまた、データ を返す２つのクエリの実行を、間に mysql_use_result() や mysql_store_result() 無しで試みた場合にも発生します。

      A.2.13 Ignoring user エラー

      以下のエラーの場合：

      Found wrong password for user: 'some_user@some_host'; ignoring user

      これは mysqld の開始または 'reload' 時に user テーブル内に正しいパ スワードを持たないエントリを見つけたことを意味します。 これは単にエントリが許可システムに拒否されているだけです。

      起こり得ることとその解決:

      • 新しいバージョンの mysqld を、古いバージョン用の user テーブルで走 らせているのかもしれません。 mysqlshow mysql user を行うことによってこれを検証できます。 パスワードフィールドが 16 文字よりも短いかどうかをチェックしてください。 もしそうなら、これを修正するために、scripts/add_long_password スクリプト を実行してください。
      • ユーザーが古いパスワード(最大8文字) を使用していて、mysqld を --old -protocol オプションで起動していないのかもしれません。 新しいパスワードで user テーブル内のユーザを更新するか、--old-protocol 付きで mysqld を再起動してください。
      • user テーブルのパスワードを、PASSWORD() 関数を使用しないで登録した のかもしれません。 この場合、user テーブルのパスワードを、mysql を使用して更新します。 PASSWORD() 関数は以下のようにして使用します： 
        mysql> UPDATE user SET password=PASSWORD('your password')
    ->             WHERE user='XXX';

      A.2.14 Table 'xxx' doesn't exist エラー

      もし Table 'xxx' doesn't exist か Can't find file: 'xxx' (errno: 2) エラーが出た場合、使用しているデータベースに xxx という名前のテーブルが 見付からなかったことを示します

      データベースとテーブルの保存に、MySQL はディレクトリとファイルを使用し、 データベースとテーブルの名前はケース依存です! (Windows ではデータベースとテーブル名はケース非依存です。 クエリ中のテーブルに対する問い合わせは全て、同じケースで書かなくてはなりません！)

      SHOW TABLES を使用してデータベースのテーブルを確認できます. 「4.5.6 SHOW 構文」節参照.

      A.2.15 Can't initialize character set xxx エラー

      もし以下のようなエラーが出た場合： 

      MySQL Connection Failed: Can't initialize character set xxx

      これは次を意味します：

      • キャラクタ・セットがマルチバイトで、、クライアントがそのキャラクタ・セットを 持っていない場合 この場合、クライアントを --with-charset=xxx か --with-extra-charsets=xxx コンフィギャ・オプションで再コンパイルする必要があります。 「2.3.3 典型的な configure オプション」節参照. All standard MySQL binaries are compiled with --with-extra-character-sets=complex which will enable support for all multi-byte character sets. 「4.6.1 データとソートに使用されるキャラクター・セット」節参照.
      • そのキャラクタ・セットが単純なキャラクタ・セットで、それが mysqld に 組み込まれておらず、さらに 定義ファイルも特定の場所に存在しなかった場合。 この場合は以下のようにします：
        • クライアントをそのキャラクタ・セットをサポートするように再コンパイル。 「2.3.3 典型的な configure オプション」節参照.
        • クライアントに、そのキャラクタ・セットの定義ファイルがどこに存在するかを教える。 多くのクライアントは --character-sets-dir=path-to-charset-dir オプションを 持っています。
        • そのクライアントが定義ファイルを探しにいっているディレクトリに、 定義ファイルをコピーする。

      A.2.16 File Not Found

      ERROR '...' not found (Errcode: 23), Can't open file: ... (errno: 24) や errcode 23 errno 24 のエラーを MySQL から得た場合、 これは MySQL に十分なファイル記述子が割り当てられなかったことを意味します。 perror ユーティリティはさらに読みやすい形式のエラーメッセージを与えます: 

      shell> perror 23
File table overflow
shell> perror 24
Too many open files
shell> perror 11
Resource temporarily unavailable

      これは mysqld が多くのファイルを開こうとしたことに起因します。 mysqld に一度に開くファイル数を多く開かないようしたり、あるいは、 mysqld が扱えるファイル記述子の数を与えたりできます。

      mysqld が一度に開くファイルの数を少なくするには、-O table_cache=32 オプション(デフォルトは64)を safe_mysqld に与えることで可能です。 また、max_connections の値(デフォルトは90)を少なくするならば、 開くファイル数も少なくできます。

      To change the number of file descriptors available to mysqld, you can use the option --open-files-limit=# to safe_mysqld or -O open-files-limit=# to mysqld. 「4.5.6.4 SHOW VARIABLES」節参照. The easiest way to do that is to add the option to your option file. 「4.1.2 `my.cnf' オプションファイル」節参照. If you have an old mysqld version that doesn't support this, you can edit the safe_mysqld script. There is a commented-out line ulimit -n 256 in the script. You can remove the '#' character to uncomment this line, and change the number 256 to affect the number of file descriptors available to mysqld.

      ulimit と open-files-limit はオペレーティングシステムの 制限内でしかファイル記述子の数を指定できません。 There is also a 'hard' limit that can only be overrided if you start safe_mysqld or mysqld as root (Just remember that you need to also use the --user=.. option in this case). もし OS の制限以上にファイル記述子のオープン数を増やしたい場合、 お使いのオペレーティングシステムのドキュメントを見て対処してください。

      tcsh を使用している場合は ulimit は動かないことに注意してください！ tcsh は現在の制限をあなたが問い合わせても、違った値を報告するでしょう。 この場合、safe_mysqld は sh で起動すべきです！

      A.3 Installation Related Issues

      A.3.1 Problems When Linking with the MySQL Client Library

      If you are linking your program and you get errors for unreferenced symbols that start with mysql_, like the following: 

      /tmp/ccFKsdPa.o: In function `main':
/tmp/ccFKsdPa.o(.text+0xb): undefined reference to `mysql_init'
/tmp/ccFKsdPa.o(.text+0x31): undefined reference to `mysql_real_connect'
/tmp/ccFKsdPa.o(.text+0x57): undefined reference to `mysql_real_connect'
/tmp/ccFKsdPa.o(.text+0x69): undefined reference to `mysql_error'
/tmp/ccFKsdPa.o(.text+0x9a): undefined reference to `mysql_close'

      この場合には、-Lpath-to-the-mysql-library -lmysqlclient を、 リンクの 最後に 加えれば解決します。

      もし undefined reference エラーで uncompress や compress が定義されていないエラーを受けたならば、 -lz をリンク ラインの 最後に 加えて再リンクしてください！

      If you get undefined reference errors for functions that should exist on your system, like connect, check the man page for the function in question, for which libraries you should add to the link line!

      If you get undefined reference errors for functions that don't exist on your system, like the following: 

      mf_format.o(.text+0x201): undefined reference to `__lxstat'

      it usually means that your library is compiled on a system that is not 100% compatible with yours. In this case you should download the latest MySQL source distribution and compile this yourself. 「2.3 MySQL ソースディストリビューションのインストール」節参照.

      If you are trying to run a program and you then get errors for unreferenced symbols that start with mysql_ or that the mysqlclient library can't be found, this means that your system can't find the share `libmysqlclient.so' library.

      The fix for this is to tell your system to search after shared libraries where the library is located by one of the following methods:

      • LD_LIBRARY_PATH 環境変数に、`libmysqlclient.so' が存在する ディレクトリを加える。
      • LD_LIBRARY 環境変数に、`libmysqlclient.so' が存在する ディレクトリを加える。
      • Copy `libmysqlclient.so' to some place that is searched by your system, like `/lib', and update the shared library information by executing ldconfig.

      他の解決方法は、あなたのプログラムを -static フラグで static にリンクするか、 動的な MySQL ライブラリをリンク前に移動してから、リンクします。 二つ目の場合は、他のプログラムがそのダイナミックライブラリを使用していないか 注意してください！

      A.3.2 一般ユーザで MySQL を動かす方法

      mysqld (MySQL サーバ) はいかなるユーザーでも開始し実行することが できます。mysqld をユーザ user_name で実行するように変更するためには、 次を行なう必要があります:

      1. Stop the server if it's running (use mysqladmin shutdown).
      2. user_name が読み書きできるように、データベースディレクトリとその中のファ イルのパーミッションを変更します。(これは UNIX root ユーザーで実行する必 要があるでしょう)： 
        shell> chown -R user_name /path/to/mysql/datadir
        MySQL データベースディレクトリのディレクトリーやファイルがシンボリック リンクの場合、 これらリンクの先のディレクトリとファイルも変更します。chown -R はシンボリ ックリンク先を変更してくれません。
      3. ユーザ user_name でサーバを起動します。または MySQL 3.22 以降を 使用する場合は、mysqld を UNIX root で起動し --user=user_name スイッチを使用します。 mysqld は、接続を許可する前に、与えられた UNIX user user_name で実 行するように切り替えます。
      4. To start the server as the given user name automatically at system startup time, add a user line that specifies the user name to the [mysqld] group of the `/etc/my.cnf' option file or the `my.cnf' option file in the server's data directory. For example: 
        [mysqld]
user=user_name

      この時点で、あなたの mysqld プロセスは UNIX user user_name で正常 に動作します。

      一つのことは変わりません。それは権限許可テーブルです。デフォルト (パーミッションテーブルインストールスクリプトmysql_install_db実行後の権限) では、mysqlデータベースへのアクセスやデータベースの作成、破棄はユーザ MySQL user root だけです。 これを変更しないと、それはそのままです。 root 以外の UNIX userでログインしている時でも、あなたは MySQL root user としてアクセスは可能です - ただプログラムに -u root をクライアントプログラムにオプション指定するだけです。

      MySQL に root としてアクセスするには、 コマンドラインで -u root を使用するだけでいいことに注意してください。 UNIX root user や MySQL を走らせている UNIX ユーザーである必要は ないことに注意してください。 MySQL のアクセスパーミッションとMySQL のユーザは、 UNIX ユーザとは完全に別のものです。UNIX ユーザに関係するのは、クライアン トに -u オプションを使用しない場合だけです。この場合、クライアントは MySQL へのログインを、あなたの UNIX ログイン名で試みます。

      あなたの UNIX マシンそれ自身が安全でない場合は、少なくとも MySQL ア クセステーブルの MySQL root ユーザにはパスワードを設定すべきです。 どこかの誰かが mysql -u root db_name を行ない、彼が望むことの全てを実行で きてしまうからです。

      A.3.3 ファイルパーミッションの問題

      ファイルパーミッションの問題がある場合、 例えば、テーブルの生成時に mysql が次を出力する場合: 

      ERROR: Can't find file: 'path/with/filename.frm' (Errcode: 13)

      これは UMASK 環境変数が mysqld 起動時に間違ってセットされていると 考えられます。 デフォルトの umask は 0660 です. これは以下のようにして safe_mysqld 立ち上げ時に変更できます: 

      shell> UMASK=384  # = 600 in octal
shell> export UMASK
shell> /path/to/safe_mysqld &

      By default MySQL will create database and RAID directories with permission type 0700. You can modify this behaviour by setting the UMASK_DIR variable. If you set this, new directories are created with the combined UMASK and UMASK_DIR. For example, if you want to give group access to all new directories, you can do: 

      shell> UMASK_DIR=504  # = 770 in octal
shell> export UMASK_DIR
shell> /path/to/safe_mysqld &

      In MySQL Version 3.23.25 and above, MySQL assumes that the value for UMASK and UMASK_DIR is in octal if it starts with a zero.

      「F Environment Variables」節参照.

      A.4 Administration Related Issues

      A.4.1 What To Do If MySQL Keeps Crashing

      全ての MySQL バージョンはリリースの前に多くのプラットフォームで テストされます。 これは MySQL にいかなるバグもないということを 意味しますが、発見するのが困難で、わずかなバグがあるかもしれません。 もし問題があった場合、何がシステムをクラッシュしているかを見つけようとする事は、 問題を早く修正するためのより良い機会でもあります。

      まず最初に, その問題で mysqld デーモンが死ななければならないかどうかか, また はその問題がクライアントで処理しなければならないかどうかを調べるべきです。 mysqladmin version を実行することにより、 mysqld サーバーが どれぐらい稼働していたかわかります。 もし mysqld が死んでいたなら、 を実行することによってあるのかをチェックすることができます. mysqldが死んだなら、 その原因を `mysql-data-directory/`hostname`.err' で見つけれるかもしれません。 「4.9.1 The Error Log」節参照.

      Many crashes of MySQL are caused by corrupted index / data files. MySQL will update the data on disk, with the write() system call, after every SQL statement and before the client is notified about the result. (This is not true if you are running with delay_key_write, in which case only the data is written.) This means that the data is safe even if mysqld crashes, as the OS will ensure that the not flushed data is written to disk. You can force MySQL to sync everything to disk after every SQL command by starting mysqld with --flush.

      The above means that normally you shouldn't get corrupted tables unless:

      • Someone/something killed mysqld or the machine in the middle of an update.
      • You have found a bug in mysqld that caused it to die in the middle of an update.
      • Someone is manipulating the data/index files outside of mysqld without locking the table properly.
      • If you are running many mysqld servers on the same data on a system that doesn't support good filesystem locks (normally handled by the lockd daemon ) or if you are running multiple servers with --skip-external-locking
      • You have a crashed index/datafile that contains very wrong data that got mysqld confused.
      • You have found a bug in the data storage code. This isn't that likely, but it's at least possible. In this case you can try to change the file type to another storage engine by using ALTER TABLE on a repaired copy of the table!

      何かがクラッシュする理由を知るのは非常に難しいので、まず、他の人で動くも のがあなたでクラッシュするのかどうかをチェックしてください。次のことを行っ てください。

      • mysqld デーモンを mysqladmin shutdown で停止し, 全てのテーブルで myisamchk --silent --force */*.MYI を実行し、そして mysqld デーモ ンを再起動します. これはきれいな状態から開始することになります。 「4 データベース管理」節参照.
      • mysqld --log を使用し、ログの情報から特定のクエリがサーバーをキルしている かを見つけ出してください。 95% のバグは特定のクエリに関係があります！ 通常これは、 MySQL が再起動される前の、ログファイルの最後のクエリの一つ です。 「4.9.2 The General Query Log」節参照. If you can repeatadly kill MySQL with one of the queries, even when you have checked all tables just before doing the query, then you have been able to locate the bug and should do a bug report for this! 「1.6.1.3 バグや問題を報告する方法」節参照.
      • Try to make a test case that we can use to reproduce the problem. 「E.1.6 Making a Test Case When You Experience Table Corruption」節参照.
      • Try running the included mysql-test test and the MySQL benchmarks. 「9.1.2 MySQL Test Suite」節参照. They should test MySQL rather well. You can also add code that to the benchmarks to simulates your application! The benchmarks can be found in the `bench' directory in the source distribution or, for a binary distribution, in the `sql-bench' directory under your MySQL installation directory.
      • fork_test.pl と fork2_test.pl を試します。
      • デバッグ用に MySQL をコンフィグすると、何かが悪くなる場合にエラー を見つけ出すのがより簡単になります。configure に --with-debug オプションか --with-debug=full オプションを つけて MySQL を再コンフィグし、 再コンパイルしてください。 「E.1 MySQL server のデバッグ」節参照.
      • デバッグ用に MySQL をコンフィグすると、いくつかのエラーを検出で きる安全なメモリ割り当てを含めます。これは何が起きているかについての多く の出力も提供します。
      • あなたの OS の最新のパッチを適用しましたか？
      • --skip-external-locking (ver. 4.0.3未満では --skip-locking) オプションを mysqld に使用してください。いくつかのシステム上では、 lockd ロックマネージャは正しく動きません; --skip-external-locking (ver. 4.0.3未満では --skip-locking) オプションは mysqld に外部ロッキングを使用 しないように伝えます。(これは同じデータ上で2つの mysqld サーバを 動すことができず、myisamchk の使用時に注意しなければいけないことを 意味します。しかし、テストとしてこのオプションを試すことは指示できます。)
      • mysqld が動いているのに応答がないように見えた時 mysqladmin -u root processlist を試しましたか？ 時々 mysqld はそう思えても死んでいません。問題は全ての接続が使用中であ ることか、いくつかの内部ロック問題があることです。mysqladmin processlist は通常これらの場合でも接続を作ることができ、現在の接続数と それらの状態についての有用な情報を提供できます。
      • 別のウィンドウで、統計出力のためにコマンド mysqladmin -i 5 status や mysqladmin -i 5 -r status をクエリ中に行ってください。
      • 次を試してください:
        1. gdb (または他のデバッガ) から mysqld を開始してください。 「E.1.3 Debugging mysqld under gdb」節参照.
        2. あなたのテストスクリプトを実行してください。
        3. Print the backtrace and the local variables at the 3 lowest levels. In gdb you can do this with the following commands when mysqld has crashed inside gdb: 
          backtrace
info local
up
info local
up
info local
          With gdb you can also examine which threads exist with info threads and switch to a specific thread with thread #, where # is the thread id.
      • MySQL にクラッシュまたは間違った振る舞いをさせるあなたのアプリ ケーションのシミュレートを Perl スクリプトで試みてください。
      • または通常のバグレポートを送ってください。 「1.6.1.3 バグや問題を報告する方法」節参照。しかし通常 よりもさらに詳細にしてください。MySQL は多くの人のために働いて いるため、クラッシュはあなたのコンピュータだけに存在する何か(例えば、あ なたの特別なシステムライブラリに関連したエラー)から生じていると思われま す。
      • もし可変長のレコードを扱うテーブルで問題があった場合、 もし、BLOB/TEXT フィールドは使用しておらず、VARCHAR フィールド だけ使用しているなら、全ての VARCHAR フィールドを ALTER TABLE で CHAR に変更してみてください。 これは MySQL に固定長レコードを使用させるようにします。 固定長レコードは少し余分な領域をとりますが、よりエラーに対して 強くなります。 現在の可変長のレコードのコードは MySQL AB で少なくとも３年以上問題なく 使用されています。 しかし可変長のレコードはよりエラーの傾向があり、 上記の事柄を試すことは良いアイデアです！

      A.4.2 忘れたパスワードをリセットする

      If you never set a root password for MySQL, then the server will not require a password at all for connecting as root. It is recommended to always set a password for each user. 「4.2.2 MySQL をクラッカーに対して安全にする方法」節参照.

      もし MySQL の root ユーザーのパスワードを忘れた場合、 これを以下のようにして入れ直すことが可能です。

      1. mysqld サーバーを kill で落とす。 (kill -9 ではありません！) PID 番号は通常 MySQL データディレクトリに `.pid' ファイルに 書かれています： 
        shell> kill `cat /mysql-data-directory/hostname.pid`
        これを、 Unix root ユーザーか、MySQL サーバーを実行した ユーザーで行います。
      2. mysqld を --skip-grant-tables オプションで起動。
      3. mysqladmin password コマンドでパスワードを変更します。 
        shell> mysqladmin -u root password 'mynewpassword'
      4. Now you can either stop mysqld and restart it normally, or just load the privilege tables with: 
        shell> mysqladmin -h hostname flush-privileges
      5. After this, you should be able to connect using the new password.

      Alternatively, you can set the new password using the mysql client:

      1. Take down and restart mysqld with the --skip-grant-tables option as described above.
      2. Connect to the mysqld server with: 
        shell> mysql -u root mysql
      3. Issue the following commands in the mysql client: 
        mysql> UPDATE user SET Password=PASSWORD('mynewpassword')
    ->             WHERE User='root';
mysql> FLUSH PRIVILEGES;
      4. After this, you should be able to connect using the new password.
      5. You can now stop mysqld and restart it normally.

      A.4.3 MySQL はフルディスクをどのように扱うか？

      ディスクフルが起きた場合 MySQL は次のことを行います:

      • 現在の行を書くのに十分な領域があるかどうかを1分毎に1回チェックします。十 分なディスクがある場合は、何も起きなかったように継続します。
      • 6分毎にログファイルにディスクフルを警告するエントリを書き出します。

      この問題の場合、以下のようにします：

      • 継続するためには、全てのレコードを挿入するのに十分な領域を解放する必要が あります。
      • スレッドをアボートするためには、mysqladmin kill をスレッドに送る 必要があります。スレッドは次に(1分)ディスクをチェックした時にアボートし ます。
      • 他のスレッドが ``disk full'' が発生したテーブルで待たされることに注意して ください。多くの ``locked'' スレッドがある場合、disk full を待つ一つのスレッ ドを kill することで、他のスレッドの継続を許します。

      Exceptions to the above behaveour is when you use REPAIR or OPTIMIZE or when the indexes are created in a batch after an LOAD DATA INFILE or after an ALTER TABLE statement.

      All of the above commands may use big temporary files that left to themself would cause big problems for the rest of the system. If MySQL gets disk full while doing any of the above operations, it will remove the big temporary files and mark the table as crashed (except for ALTER TABLE, in which the old table will be left unchanged).

      A.4.4 MySQL が一時ファイルを格納する場所

      MySQL は一時ファイルを格納する場所として TMPDIR 環境変数の値を 使用します。TMPDIR を設定していなければ、MySQL はシステムのデフォルトを 使用します。通常は `/tmp' または `/usr/tmp' です。TMPDIR が 小さすぎる場合、safe_mysqld を編集して、十分な領域がある他のディレクトリ を指すように TMPDIR を設定すべきです！ --tmpdir オプションを mysqld に与えることで、一時ファイルディレク トリを指定することも可能です。

      MySQL は全ての一時ファイルを ``隠しファイル'' として生成します。 これは mysqld が終了した場合に、一時ファイルが削除されないことを確実にし ます。隠しファイルを使用する '悪い' 側面は、小さすぎる一時ディスクを一杯 にする大きな一時ファイルを見つけられないことです。

      ソート時 (ORDER BY または GROUP BY)、MySQL は通常一つまた は二つの一時ファイルを使用します。必要な最大のディスク容量は: 

      (length of what is sorted + sizeof(database pointer))
* number of matched rows
* 2

      sizeof(database_pointer) は通常４ですが、将来本当に大きなテーブル のために大きくなることもあります。

      いくつかの SELECT クエリは一時的な SQL テーブルも生成します。これらは隠 しファイルではなく、`SQL_*' という名前です。

      ALTER TABLE は一時テーブルをオリジナルテーブルと同じディレクトリ 内に生成します。

      If you use MySQL 4.1 or later you can spread load between several physical disks by setting --tmpdir to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion. Note: These paths should end up on different physical disks, not different partitions of the same disk.

      A.4.5 MySQL ソケットファイル `/tmp/mysql.sock' を変更する方法、削除から守る方法

      もし誰かに MySQL のソケットファイル `/tmp/mysql.sock' が消されるな ら、ほとんどの UNIX がそうであるように、 `/tmp' に sticky ビットをたてて 保護します。 root でログインして、以下のようにします： 

      shell> chmod +t /tmp

      これはファイルのオーナーとスーパーユーザー(root) のみが、 `/tmp' のファイルを消すことができます。

      sticky ビットが立っているか確認するには、 ls -ld /tmp を行います。 パーミッションの最後のビットが t ならば、セットされています。

      You can change the place where MySQL uses / puts the socket file the following ways:

      • Specify the path in a global or local option file. For example, put in /etc/my.cnf: 
        [client]
socket=path-for-socket-file

[mysqld]
socket=path-for-socket-file
        「4.1.2 `my.cnf' オプションファイル」節参照.
      • Specifying this on the command-line to safe_mysqld and most clients with the --socket=path-for-socket-file option.
      • この場合、 MYSQL_UNIX_PORT 環境変数に設定することにより可能です。
      • Defining the path with the configure option --with-unix-socket-path=path-for-socket-file. 「2.3.3 典型的な configure オプション」節参照.

      ソケットのテストをする場合、以下のようにします： 

      shell> mysqladmin --socket=/path/to/socket version

      A.4.6 Time Zone Problems

      もし SELECT NOW() があなたのローカル時間ではなく GMT を返すなら、 TZ 環境変数をローカルのTimezone に設定しなくてはなりません。 環境変数の設定は、サーバーを実行する前に行われなくてはなりません。 たとえば、safe_mysqld や mysql.server スクリプトで 行います。 「F Environment Variables」節参照.

      A.5 Query Related Issues

      A.5.1 検索時のケース依存

      デフォルトでは MySQL フィールドはケース非依存です (しかし、ケース非依 存にならないいくつかの文字セットはありますsuch as czech)。 これは、col_name LIKE 'a%' で検索した場合、A または a で始まる全てのフィールドを得ることを 意味します。検索をケース依存にしたいのなら、始まりをチェックするには INDEX(column, "A")=1 のようなことを、また、文字列全体が同じかどう かには STRCMP(column, "A") = 0 を使用してください。

      単純な比較操作 >=, >, =, <, <=、ソートそしてグループ化は、文字 ``sort val ue'' 上で行われます。同じソート値の文字 (like E, e and 'e)は同じ文字と して扱われます！

      In older MySQL versions LIKE comparisons where done on the uppercase value of each character (E == e but E <> 'e. In newer MySQL versions LIKE works just like the other comparison operators.

      あるフィールドをいつでもケース依存で扱いたい場合は、それを BINARY として宣言してください。 「6.5.3 CREATE TABLE 構文」節参照.

      big5 エンコーディングと呼ばれる中国語データを使用している場合は、全ての 文字項目を BINARY にしてください。これは、big5 エンコーディング文 字のソート順が ascii コードが基になっているため、機能します。

      A.5.2 DATE フィールド使用時の問題

      日付 DATE の形式は 'YYYY-MM-DD' です。ANSI SQL に従って実際には他 のは許されま せん。更新または SELECT 文中の WHERE 節内ではこの形式を使用すべきです。す なわち: 

      mysql> SELECT * FROM tbl_name WHERE date >= '1997-05-05';

      利便のため MySQL は、日付が数値の文脈で使用されると、日付を自動的に数 値に変換します。これにより、更新と TIMESTAMP, DATE または DATETIME フィールドでの WHERE 時に、わりと自由に日付を指定すること ができます。 (この記述を許すため、句読記号を日付のセパレーターとして使用します。 例えば、'1998-08-15' と '1998#08#15' は同一です.) もしろんセパレーターのない記述(例：'19980815')も日付として変換してくれま す。

      特別な日付 '0000-00-00' は '0000-00-00' として格納され取り出されま す。 MyODBC を通して '0000-00-00' 日付を使用する時、MyODBC 2 .50.12 以上では自動的に NULL に変換されます。ODBC はこの日付の種類を扱え ないためです。

      Because MySQL performs the conversions described above, the following statements work: 

      mysql> INSERT INTO tbl_name (idate) VALUES (19970505);
mysql> INSERT INTO tbl_name (idate) VALUES ('19970505');
mysql> INSERT INTO tbl_name (idate) VALUES ('97-05-05');
mysql> INSERT INTO tbl_name (idate) VALUES ('1997.05.05');
mysql> INSERT INTO tbl_name (idate) VALUES ('1997 05 05');
mysql> INSERT INTO tbl_name (idate) VALUES ('0000-00-00');

mysql> SELECT idate FROM tbl_name WHERE idate >= '1997-05-05';
mysql> SELECT idate FROM tbl_name WHERE idate >= 19970505;
mysql> SELECT MOD(idate,100) FROM tbl_name WHERE idate >= 19970505;
mysql> SELECT idate FROM tbl_name WHERE idate >= '19970505';

      次は動きません 

      mysql> SELECT idate FROM tbl_name WHERE STRCMP(idate,'19970505')=0;

      STRCMP() は文字列関数で、idate を文字に変換して、文字比較を行いま す。 '19970505' は日付には変換してくれず、日付の比較も行いません。

      MySQL は日付が正しいかどうかをチェックしないことに注意してください。 間違った日付(例えば '1998-2-31')を格納すると、その間違った日付が格 納されます。

      Because MySQL packs dates for storage, it can't store any given date as it would not fit onto the result buffer. The rules for accepting a date are:

      • If MySQL can store and retrieve a given date, the wrong date is accepted for DATE and DATETIME columns.
      • All days values between 0-31 are accepted for any date. This makes it very convenient for web applications where you ask year, month and day in 3 different fields.
      • The day or month field may be zero. This is convenient if you want to store a birthdate in a DATE column and you only know part of the date.

      If the date cannot be converted to any reasonable value, a 0 is stored in the DATE field, which will be retrieved as 0000-00-00. This is both a speed and convenience issue as we believe that the database's responsiblity is to retrieve the same date you stored (even if the data was not logically correct in all cases). We think it is up to the application to check the dates, and not the server.

      A.5.3 NULL 値での問題

      SQL の初心者のありがちな混乱は、NULL 値が空文字列 "" と同じ物だと 考えることです。これは正しくありません！ 例えば、次のステートメントは全く別の ものです: 

      mysql> INSERT INTO my_table (phone) VALUES (NULL);
mysql> INSERT INTO my_table (phone) VALUES ("");

      両方の文とも phone フィールドに値を挿入していますが、 初めのは NULL 値を挿入し、二番目のは空文字列を挿入しています。 初めのは ``電話番号を知らない'' と見なされ、二番目のは ``彼女は電話を 持っていない'' と見なされます。

      SQL では、 NULL は他の全ての値(たとえ NULL でも)と比較した時に、 常に偽になる値です。 NULL を含む式は、特に断りがなければ、常に NULL 値を生成します。次の項目は全て NULL を返します: 

      mysql> SELECT NULL,1+NULL,CONCAT('Invisible',NULL);

      NULL 値がセットされている項目を検索する場合、 =NULL テストを行わないでください。 これは expr = NULL が FALSE なので、なんの行も返しません。 例えば以下の例： 

      mysql> SELECT * FROM my_table WHERE phone = NULL;

      NULL 値を持つフィールドを検索したい場合は、IS NULL テストを使用し なくてはいけま せん。次は NULL 電話番号と空の電話番号を見つける方法を示しています: 

      mysql> SELECT * FROM my_table WHERE phone IS NULL;
mysql> SELECT * FROM my_table WHERE phone = "";

      Note that you can only add an index on a column that can have NULL values if you are using MySQL Version 3.23.2 or newer and are using the MyISAM or InnoDB table type. Version 3.23.2 以前の MySQL では、他の多くの SQL サーバのように、NULL 値を持つ インデックスフィールドを持てません。これらのフィールドは NOT NULL と宣言 しなくてはいけません。

      LOAD DATA INFILE でデータを読み込むときは、空のフィールドは '' で 更新されます。 項目を NULL 値にしたい場合は、テキストファイル中に \N を使用すべき です。 リテラルとしての 'NULL' 語が、ある状況下で使用されています。 「6.4.9 LOAD DATA INFILE 構文」節参照.

      When using ORDER BY, NULL values are presented first. In versions prior to 4.0.2, if you sort in descending order using DESC, NULL values are presented last. When using GROUP BY, all NULL values are regarded as equal.

      To help with NULL handling, you can use the IS NULL and IS NOT NULL operators and the IFNULL() function.

      ORDER BY 使用時, NULL 値は最初に提示されます. DESC を使用して降順にソートする時、NULL 値は最後になります。 GROUP BY 使用時, 全ての NULL 値は等しいと見なされます。

      NULL 処理を手助けするため、次の関数を使用できます: IS NULL, IS NOT NULL, IFNULL().

      いくつかの項目型では、NULL 値はハンドルとして扱われます。 もしテーブル内の最初の TIMESTAMP 項に NULL を挿入するなら、 現在の日付と時刻が挿入されます。もし AUTO_INCREMENT 項にNULL 値を 挿入するなら、 次のシーケンス番号が挿入されます。

      A.5.4 alias の問題

      GROUP BY, ORDER BY, HAVING 節において 項目を参照するに当たりエイリアスが使用できます。 エイリアスは項目としてより良い名称を与えるのに使用されます： 

      SELECT SQRT(a*b) as rt FROM table_name GROUP BY rt HAVING rt > 0;
SELECT id,COUNT(*) AS cnt FROM table_name GROUP BY id HAVING cnt > 0;
SELECT id AS "Customer identity" FROM table_name;

      ANSI SQL が WHERE 節内でエイリアスを参照することを 許可していないことに注意してください。これは WHERE が実行される時点で 項目の値がまだ決定されていないからです。例えば、以下のクエリは あやまり です： 

      SELECT id,COUNT(*) AS cnt FROM table_name WHERE cnt > 0 GROUP BY id;

      どの行が GROUP BY に含まれるかを決めるために WHERE 構文が 実行される一方で、 得られた結果のどの行を使うか確定するために HAVING が使用されます。

      A.5.5 Deleting Rows from Related Tables

      MySQL は現在 副問い合わせ は未サポート(バージョン4.1以上)です。また、 Version 4.0 以前では DELETE 構文で複数のテーブルを扱う事もサポートしていません。 したがって、２つのテーブルに関連するレコードを消すには、以下のようにして行います：

      1. いくつかの WHERE 条件を使用して、基本となるテーブルから行を SELECT
      2. 同じ条件下で、基本となるテーブルに含まれる行を DELETE
      3. DELETE FROM related_table WHERE related_column IN (selected_rows).

      related_column のクエリの合計文字数が、1,048,576 (デフォルトは max_ allowed_packet の値) をこえる場合、 それをいくつかに分割して、複数の DELETE 構文にしなくてはなりません。

      related_column がインデックスで、100-1000 のrelated_columnだけを消 す場合、よりはやく DELETE できます。 もし related_column がインデックスでない場合、その速度は IN 節の引 数の数に無関係になります。

      A.5.6 Solving Problems with No Matching Rows

      複雑なクエリーを行って、もしなんの結果も返さなければ、 そのクエリーの何が悪いかを見つけるため、以下の手続きを行います：

      1. EXPLAIN を使用してクエリーをテストし、明白な間違いを見つけます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.
      2. WHERE 節で使用されているフィールドだけを Select してみます
      3. 結果が返ってくるまで、一つ一つクエリーからテーブルを取り除いていきます。 テーブルが大きい場合、LIMIT 10 をクエリーで使用することは良くありません。
      4. 行にマッチすべきであろう項を SELECT してみます。 その場合、select するのは、上記で最後に取り除いたテーブルに対して行います。
      5. If you are comparing FLOAT or DOUBLE columns with numbers that have decimals, you can't use '='. This problem is common in most computer languages because floating-point values are not exact values. In most cases, changing the FLOAT to a DOUBLE will fix this. 「A.5.7 Problems with Floating-Point Comparison」節参照.
      6. もしなにも悪いところを見つけることができなかった場合、 小さなテストをつくって mysql test < query.sql を行ってみてください。 mysqldump --quick database tables > query.sql でテストファイルを作成でき ます。 このファイルをエディターで編集し、いくつかのinsert行を(多すぎるなら)消します。 そしてファイルの最後にselect構文を付け足します。 テストを行うには： 
        shell> mysqladmin create test2
shell> mysql test2 < query.sql
        mysqlbug を使用して mysql@lists.mysql.com にテストを投稿してくだ さい。

      A.5.7 Problems with Floating-Point Comparison

      floating-point numbers cause confusion sometimes, because these numbers are not stored as exact values inside computer architecture. What one can see on the screen usually is not the exact value of the number.

      Field types FLOAT, DOUBLE and DECIMAL are such. 

      CREATE TABLE t1 (i INT, d1 DECIMAL(9,2), d2 DECIMAL(9,2));
INSERT INTO t1 VALUES (1, 101.40, 21.40), (1, -80.00, 0.00),
(2, 0.00, 0.00), (2, -13.20, 0.00), (2, 59.60, 46.40),
(2, 30.40, 30.40), (3, 37.00, 7.40), (3, -29.60, 0.00),
(4, 60.00, 15.40), (4, -10.60, 0.00), (4, -34.00, 0.00),
(5, 33.00, 0.00), (5, -25.80, 0.00), (5, 0.00, 7.20),
(6, 0.00, 0.00), (6, -51.40, 0.00);

mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b
    -> FROM t1 GROUP BY i HAVING a <> b;
+------+--------+-------+
| i    | a      | b     |
+------+--------+-------+
|    1 |  21.40 | 21.40 |
|    2 |  76.80 | 76.80 |
|    3 |   7.40 |  7.40 |
|    4 |  15.40 | 15.40 |
|    5 |   7.20 |  7.20 |
|    6 | -51.40 |  0.00 |
+------+--------+-------+

      The result is correct. Although the first five records look like they shouldn't pass the comparison test, they may do so because the difference between the numbers show up around tenth decimal, or so depending on computer architecture.

      The problem cannot be solved by using ROUND() (or similar function), because the result is still a floating-point number. Example: 

      mysql> SELECT i, ROUND(SUM(d1), 2) AS a, ROUND(SUM(d2), 2) AS b
    -> FROM t1 GROUP BY i HAVING a <> b;
+------+--------+-------+
| i    | a      | b     |
+------+--------+-------+
|    1 |  21.40 | 21.40 |
|    2 |  76.80 | 76.80 |
|    3 |   7.40 |  7.40 |
|    4 |  15.40 | 15.40 |
|    5 |   7.20 |  7.20 |
|    6 | -51.40 |  0.00 |
+------+--------+-------+

      This is what the numbers in column 'a' look like: 

      mysql> SELECT i, ROUND(SUM(d1), 2)*1.0000000000000000 AS a,
    -> ROUND(SUM(d2), 2) AS b FROM t1 GROUP BY i HAVING a <> b;
+------+----------------------+-------+
| i    | a                    | b     |
+------+----------------------+-------+
|    1 |  21.3999999999999986 | 21.40 |
|    2 |  76.7999999999999972 | 76.80 |
|    3 |   7.4000000000000004 |  7.40 |
|    4 |  15.4000000000000004 | 15.40 |
|    5 |   7.2000000000000002 |  7.20 |
|    6 | -51.3999999999999986 |  0.00 |
+------+----------------------+-------+

      Depending on the computer architecture you may or may not see similar results. Each CPU may evaluate floating-point numbers differently. For example in some machines you may get 'right' results by multiplaying both arguments with 1, an example follows.

      WARNING: NEVER TRUST THIS METHOD IN YOUR APPLICATION, THIS IS AN EXAMPLE OF A WRONG METHOD!!! 

      mysql> SELECT i, ROUND(SUM(d1), 2)*1 AS a, ROUND(SUM(d2), 2)*1 AS b
    -> FROM t1 GROUP BY i HAVING a <> b;
+------+--------+------+
| i    | a      | b    |
+------+--------+------+
|    6 | -51.40 | 0.00 |
+------+--------+------+

      The reason why the above example seems to be working is that on the particular machine where the test was done, the CPU floating-point arithmetics happens to round the numbers to same, but there is no rule that any CPU should do so, so it cannot be trusted.

      The correct way to do floating-point number comparison is to first decide on what is the wanted tolerance between the numbers and then do the comparsion against the tolerance number. For example, if we agree on that floating-point numbers should be regarded the same, if they are same with precision of one of ten thousand (0.0001), the comparsion should be done like this: 

      mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
    -> GROUP BY i HAVING ABS(a - b) > 0.0001;
+------+--------+------+
| i    | a      | b    |
+------+--------+------+
|    6 | -51.40 | 0.00 |
+------+--------+------+
1 row in set (0.00 sec)

      And vice versa, if we wanted to get rows where the numbers are the same, the test would be: 

      mysql> SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
    -> GROUP BY i HAVING ABS(a - b) < 0.0001;
+------+-------+-------+
| i    | a     | b     |
+------+-------+-------+
|    1 | 21.40 | 21.40 |
|    2 | 76.80 | 76.80 |
|    3 |  7.40 |  7.40 |
|    4 | 15.40 | 15.40 |
|    5 |  7.20 |  7.20 |
+------+-------+-------+

      A.6 Table Definition Related Issues

      A.6.1 Problems with ALTER TABLE.

      ALTER TABLE changes a table to the current character set. If you get a duplicate key error during ALTER TABLE, then the cause is either that the new character sets maps two keys to the same value or that the table is corrupted, in which case you should run REPAIR TABLE on the table.

      もし ALTER TABLE が以下のようなエラーで死んだ場合： 

      Error on rename of './database/name.frm' to './database/B-a.frm' (Errcode: 17)

      これは以前の ALTER TABLE で MySQL がクラッシュしており、 `A-something' か `B-something' という名前の、誤った情報を流している 古いテーブルが存在しています。 この場合、MySQL データディレクトリに入り、A- や B- で始まる 名前を持つファイルを全て消します。 (消す代わりにどこかに移動しても構いません。)

      ALTER TABLE は以下のように動作します:

      • 変更要求のあった `A-xxx' という名前の新しいテーブルを作成。
      • 元のテーブル内の全ての行を `A-xxx' にコピー。
      • 元のテーブルを `B-xxx' に名称変更。
      • `A-xxx' は元のテーブル名に名称変更される。
      • `B-xxx' は消去される。

      もし名称変更の際に問題があると、MySQL は変更を取り消すように動きます。 致命的な問題が起きた場合(ありえませんが)、MySQL は元の古いテーブルを `B-xxx' という名前のままにしておきます。単にシステムレベルで名称変更すれば データは戻ります。

      A.6.2 テーブル中でフィールドの順序を入れ替える方法

      SQLの主な目的はデータフォーマットからアプリケーションを切り離してしまうことにあります。そのため、常に取り出したいデータの順序を常に指定する必要があります。例えば、次のような文: 

      SELECT col_name1, col_name2, col_name3 FROM tbl_name;

      これは、col_name1, col_name2, col_name3, の順序でデータを返します。ここで、 

      SELECT col_name1, col_name3, col_name2 FROM tbl_name;

      こうすると、col_name1, col_name3, col_name2, の順序でデータを返します。

      アプリケージョン内でSELECT *やそのテーブル内での位置に依存してしまうような 取り出し方はけっしてするべきではありません。 というのは取り出されるデータの順序が常に保障されるものではないからです。 単にフィールドの情報が変更されただけでアプリケーションがエラーが発生する可能性を有しているのです。

      にもかかわらずフィールドの順序を変えたい場合には次のような方法があります。

      1. 新しいテーブルを望んでいるフィールドの順序で作成します。
      2. INSERT INTO new_table SELECT fields-in-new_table-order FROM old_table. を実行します。
      3. old_tableをドロップするかリネームして下さい。
      4. ALTER TABLE new_table RENAME old_table. を実行します。

      You should never, in an application, use SELECT * and retrieve the columns based on their position, because the order and position in which columns are returned cannot may not remain the same (if you add/move/delete columns). A simple change to your database structure would then cause your application to fail. Of course SELECT * is quite suitable for testing queries.

      A.6.3 TEMPORARY TABLE 問題

      TEMPORARY TABLESを用いる処理における制限を以下に示します。

      • テンポラリーテーブルではHEAP, ISAM, MyISAM, MERGE, InnoDB の いづれかの型のみを持つことが可能です。
      • テンポラリーテーブルは一度のクエリで一回しか使用できません。例えば、次のようなものは動きません。 
        mysql> SELECT * FROM temporary_table, temporary_table AS t2;
      • ALTER TABLE org_name RENAME new_name は動作します。しかし、 TEMPORARYテーブルにRENAMEを使用することはできません。

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Reference.html0100644000175100001560000134613410021471264016364 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 6 MySQL Language Reference Go to the first, previous, next, last section, table of contents.

      6 MySQL Language Reference

      MySQL has a very complex, but intuitive and easy to learn SQL interface. This chapter describes the various commands, types, and functions you will need to know in order to use MySQL efficiently and effectively. This chapter also serves as a reference to all functionality included in MySQL. In order to use this chapter effectively, you may find it useful to refer to the various indexes.

      6.1 Language Structure

      6.1.1 文字列と数値をどのように書くか？

      この節は MySQL で文字列と数値を記述するさまざまな方法を説明します。 MySQL でのこれらの基本型の取り扱い時に、出会うであろうさまざまな ニュアンスと ``了解'' もカバーします。

      6.1.1.1 文字列

      文字列は文字の並びです。引用符(`'')または二重引用符(`"')で括ら れます(後者は ANSI モードで実行していない場合のみ)。 例： 

      'a string'
"another string"

      文字列中では、いくつかのシーケンスは特別な意味を持ちます。これらのシーケ ンスのそれぞれはエスケープ文字として知られるバックスラッシュ (`\')で始まります。MySQL は次のエスケープシーケンスを認識 します。

      \0
      ASCII 0 (NUL) 文字。
      \'
      引用符(`'')。
      \"
      二重引用符(`"')。
      \b
      バックスペース文字。
      \n
      改行文字。
      \r
      リターン文字。
      \t
      タブ文字。
      \z
      ASCII(26) (Control-Z)。この文字は、ASCII(26) が Windows では END-OF-FILE であるという問題を回避するために、コード化できます。(ASCII(26) は mysql database < filename を使用しようとする場合に問題になります)。
      \\
      バックスラッシュ(`\')文字。
      \%
      `%' 文字。これは `%' がワイルドカード文字として解釈される文脈 で、`%' そのものを検索するために使用されます。 「6.3.2.1 String Comparison Functions」節参照.
      \_
      _ 文字。これは `_' がワイルドカード文字として解釈される文脈 で、_ そのものを検索するために使用されます。 「6.3.2.1 String Comparison Functions」節参照.

      いくつかの文字列文脈で `\%' または `\_' を使用すると、これらは文 字列 `%' と `_' ではなく、`\%' と `\_' を返します。

      文字列中に引用符を含める方法はいくつかあります:

      • `'' で括られる文字列中の `'' は `''' として書くことができ ます。
      • `"' で括られる文字列中の `"' は `""' として書くことができ ます。
      • 引用符の前にエスケープ文字 (`\') を置くことができます。
      • `"' で括られた文字列中の `'' は特別扱いの必要はなく、二重にし たり、エスケープする必要はありません。同じように、`'' で括られた文 字列中の `"' は特別扱いの必要はありません。

      次の SELECT ステートメントは、クォートとエスケープがどのように働 くかを示します: 

      mysql> SELECT 'hello', '"hello"', '""hello""', 'hel''lo', '\'hello';
+-------+---------+-----------+--------+--------+
| hello | "hello" | ""hello"" | hel'lo | 'hello |
+-------+---------+-----------+--------+--------+

mysql> SELECT "hello", "'hello'", "''hello''", "hel""lo", "\"hello";
+-------+---------+-----------+--------+--------+
| hello | 'hello' | ''hello'' | hel"lo | "hello |
+-------+---------+-----------+--------+--------+

mysql> SELECT "This\nIs\nFour\nlines";
+--------------------+
| This
Is
Four
lines |
+--------------------+

      バイナリデータを BLOB フィールドに挿入したい場合、次の文字をエスケープ シーケンスで表す必要があります:

      NUL
      ASCII 0。`\0' (バックスラッシュと ASCII `0' 文字) に置き換える べきです。
      \
      ASCII 92, バックスラッシュ。`\\' と表記してください。
      '
      ASCII 39, 引用符。`\'' と表記してください。
      "
      ASCII 34, 二重引用符。`\"' と表記してください。

      C コードを書く場合、INSERT 節で文字をエスケープするために、C API 関数 mysql_real_escape_string() を使用できます。 「8.4.2 C API 関数概要」節参照. Perl では、DBI パッケージの quote メソッドを使 用して、特殊文字を適当なエスケープシーケンスに変換できます。 「8.2.2 The DBI Interface」節参照.

      上記の特殊文字のどれかを含む可能性のある全ての文字列について、エスケープ 関数を使用すべきです！

      Alternatively, many MySQL APIs provide some sort of placeholder capability that allows you to insert special markers into a query string, and then bind data values to them when you issue the query. In this case, the API takes case of escaping special characters in the values for you automatically.

      6.1.1.2 数値

      整数は数字の並びで表現されます。 浮動小数点は `.' で小数を分割します。 どちらの型も負数を表すために `-' を前につけます。

      正当な数値の例: 

      1221
0
-32

      有効な浮動小数点の例： 

      294.42
-32032.6809e+10
148.00

      整数が浮動小数点の文脈で使用されるかもしれません； この場合、浮動小数点に 変換されます。

      6.1.1.3 16進法の値

      MySQL は16進法の値をサポートします。 数値の文脈では、これらは整数(64ビット精度)のように振る舞います。 文字列の文脈では、hexの桁のそれぞれのペアが文字に変換された バイナリー文字のように振る舞います。 

      mysql> SELECT x'4D7953514C';
         -> MySQL
mysql> SELECT 0xa+0;
       -> 10
mysql> select 0x5061756c;
       -> Paul

      The x'hexstring' syntax (new in 4.0) is based on ANSI SQL and the 0x syntax is based on ODBC. 16進数表記は、ODBC において BLOB の値を与えるためにしばしば使用されます。 You can convert a string or a number to hexadecimal with the HEX() function.

      6.1.1.4 NULL 値

      NULL は ``no data'' を意味し、数値型の 0 や文字列型の空文 字列とは異なることに注意してください。 「A.5.3 NULL 値での問題」節参照.

      テキストファイルの読み込みや書き出し時に、NULL は \N で 表現されます。 (LOAD DATA INFILE, SELECT ... INTO OUTFILE). 「6.4.9 LOAD DATA INFILE 構文」節参照.

      6.1.2 データベース名、テーブル名、インデックス名、フィールド名、エイリアス名

      データベース名、テーブル名、インデックス名、フィールド名、エイリアス名は MySQL では全て同じ規則に基づきます:

      注意: 規則は MySQL 3.23.6 で変更されました。それは識別子(データベー ス名、テーブル名、フィールド名)の ``' でのクォートを導入した時です (ANSI モードで実行する場合は、" も識別子をクォートするために働きま す)。

      識別子 最大長 許される文字
      データベース 64 ディレクトリ名として許されるすべての文字。/, `\', `.' を除く。
      テーブル 64 ファイル名として許されるすべての文字。/ と . を除く。
      フィールド 64 すべての文字
      エイリアス 255 すべての文字

      注意: 上記に加え、識別子内には ASCII(0) と ASCII(255) を持てません。

      注意: 識別子が制限された単語であったり特殊文字を含む場合は、それを使用する 時には常に ` (バッククォート) でクォートする必要があります: 

      mysql> SELECT * FROM `select` WHERE `select`.id > 100;

      「6.1.7 Is MySQL Picky About Reserved Words?」節参照.

      MySQL 3.23.6 より前のバージョンでは、名前の規則は次に従います:

      • 名前は、現在の文字セットのアルファベットと数字文字から成り、`_' と `$' も含みます。デフォルト文字セットは ISO-8859-1 Latin1 ですが、 これは mysqld に --default-character-set オプションを 与えることで変更できます. (3.23.14 以上の場合のみ。 それ以前のバージョンでは MySQL 再コンパイルが必要) 「4.6.1 データとソートに使用されるキャラクター・セット」節参照.
      • 名前は、名前として正しい任意の文字で始めることができます。特に、名前は数 字で始めることができます(これは他の多くのシステムと異なります！)。しかし、 数字だけの名前にする事はできません。
      • 名前の中に `.' 文字を使用することはできません。フィールドを参照できるよう に形式を拡張するために使用されるためです(後述)。

      1e のような名前は使用しないことを勧めます。1e+1 のような式が あいまいだからです。これは、式 1e + 1 として、または数値 1e+1 として解釈されます。

      MySQL では次の形式のいずれかを使用してフィールドを参照できます:

      フィールドの参照方法 意味
      col_name クエリ中で使用されるテーブル内に存在している col_name という名前のフィールド
      tbl_name.col_name 現在のデータベースのテーブル tbl_name 内のフィールド col_name
      db_name.tbl_name.col_name データベース db_name のテーブル tbl_name 内のフィールド col_name。この形式は バージョン 3.22 以降で有効です。
      `column_name` キーワードであったり特殊文字を含むフィールド。

      参照が曖昧でないならば、ステートメント中のフィールド参照の前に tbl_name または db_name.tbl_name を記述する必要はありません。例えば、テー ブル t1 と t2 がそれぞれフィールド c を含み、t1 と t2 の両方を使用する SELECT ステートメントで c を取 り出すとします。この場合、c はステートメントで使用されるテーブル 間で唯一でないので曖昧です。そのため、t1.c または t2.c と 記述するこよによりどちらのテーブルを意味するかを示す必要があります。同様 に、データベース db1 のテーブル t とデータベース db2 のテーブル t から取り出す場合、これらのテーブル中の項 目は、db1.t.col_name と db2.t.col_name として参照する必要 があります。

      構文 .tbl_name は現在のデータベース内のテーブル tbl_name を意味します。この構文はいくつかの ODBC が `.' 文字をテーブル名の前 に置くために許されています。

      6.1.3 名前のケース依存性

      MySQL では、データベースとテーブルは、ディレクトリと そのディレクトリ中のファイルに対応します。そのため、下で動作するオペレー ティングシステムのケース依存性は、データベースとテーブル名のケース依存性を決定します。 データベース名とテーブル名は UNIX ではケース依存で、Windows ではケース非依 存です。One prominent exception here is Mac OS X, when the default HFS+ file system is being used. However Mac OS X also supports UFS volumes, those are case sensitive on Mac OS X just like they are on any Unix. 「1.7.3 MySQL の ANSI SQL92 に対する拡張」節参照.

      注意: Windows ではデータベース名とファイル名はケース非依存ですが、 同じクエリ内で、データベースやテーブルを異なるケースを使用して参照すべき ではありません。 以下のクエリは動きません。なぜなら my_table と MY_TABLE の両方を 参照しているからです： 

      mysql> SELECT * FROM my_table WHERE MY_TABLE.col=1;

      フィールド名とフィールドの別名は全ての場合でケース非依存です。

      テーブルの別名はケース依存です。 以下のクエリは動きません。なぜなら a と A のエイリアスを両方 参照しているからです： 

      mysql> SELECT col_name FROM tbl_name AS a
    ->                 WHERE a.col_name = 1 OR A.col_name = 2;

      テーブル名に使用されたケースを覚えておくことに問題があるなら、常にデータベー スとテーブルに小文字の名前をつけるというような、一貫した慣習を採用してくだ さい。

      この問題を回避する一つの方法は、mysqld を -O lower_case_table_names=1 をつけて起動することです。デフォルトではこのオプ ションは Windows では 1 で UNIX では 0 です。

      lower_case_table_names が 1 の場合、MySQL はディスク上のす べてのテーブル名を小文字に変換して検索します。 (From version 4.0.2, this option also applies to database names.) 注意: このオプションを変更し た場合、mysqld を起動する前に、最初に古いテーブル名を小文字に変換す ることが必要です。

      If you move MyISAM files from a Windows to a Unix disk, you may in some cases need to use the `mysql_fix_extensions' tool to fix-up the case of the file extensions in each specified database directory (lowercase `.frm', uppercase `.MYI' and `.MYD'). `mysql_fix_extensions' can be found in the `scripts' subdirectory.

      6.1.4 ユーザー変数

      MySQL は、@variablename 構文で接続固有の変数をサポー トします。変数名は現在の文字セットのアルファベットと数字、それに `_'、`$'、`.' 文字からなります。デフォルト文字セットは ISO-8859-1 Latin1 です。 これは mysqld に --default-character-set オプションを 与えることで変更できます. (3.23.14 以上の場合のみ。 それ以前のバージョンでは MySQL 再コンパイルが必要) 「4.6.1 データとソートに使用されるキャラクター・セット」節参照.

      変数は初期化する必要はありません。デフォルトでは NULL であり、整数 値、実数値、文字列値を格納できます。すべてのスレッド変数は、スレッドが終了 すると自動的に解放されます。

      SET 構文で変数を設定できます: 

      SET @variable= { integer expression | real expression | string expression }
[,@variable= ...].

      SET 構文で、式中で変数を設定することも可能です。 However, in this case the assignment operator is := rather than =, because = is reserved for comparisons in non-SET statements: 

      mysql> SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;
+----------------------+------+------+------+
| @t1:=(@t2:=1)+@t3:=4 | @t1  | @t2  | @t3  |
+----------------------+------+------+------+
|                    5 |    5 |    1 |    4 |
+----------------------+------+------+------+

      (我々は := 構文を使用する必要がありました。= は比較のために 予約されていたからです。)

      ユーザー変数は式が許される場所で使用できます。注意: これは現在、 SELECT ステートメントの LIMIT 節、LOAD DATA ステート メントの IGNORE number LINES 節のように、数値が明示的に要求される文 脈での使用を含みません。

      注意: SELECT ステートメントでは、それぞれの式はクライアン トに送られた時にだけ評価されます。これは、SELECT 部で設定された変数 を必要とする式を参照する HAVING, GROUP BY, ORDER BY 節ができないことを意味します。例えば、次のステートメントは期待通りには動作 しません: 

      mysql> SELECT (@aa:=id) AS a, (@aa+3) AS b FROM table_name HAVING b=5;

      この理由は、@aa が現在のレコードの値ではなく、前に受け取ったレコー ドの id の値になるからです。

      The rule is to never assign and use the same variable in the same statement.

      6.1.5 System Variables

      Starting from MySQL 4.0.3 we provide better access to a lot of system and connection variables. One can change most of them without having to take down the server.

      There are two kind of system variables: Thread-specific (or connection-specific) variables that are unique to the current connection and global variables that are used to configure global events. Global variables also are used to set up the initial values of the corresponding thread-specific variables for new connections.

      When mysqld starts, all global variables are initialised from command line arguments and option files. You can change the value with the SET GLOBAL command. When a new thread is created, the thread-specific variables are initialised from the global variables and they will not change even if you issue a new SET GLOBAL command.

      To set the value for a GLOBAL variable, you should use one of the following syntaxes: (Here we use sort_buffer_size as an example variable) 

      SET GLOBAL sort_buffer_size=value;
SET @@global.sort_buffer_size=value;

      To set the value for a SESSION variable, you can use one of the following syntaxes: 

      SET SESSION sort_buffer_size=value;
SET @@session.sort_buffer_size=value;
SET sort_buffer_size=value;

      If you don't specify GLOBAL or SESSION then SESSION is used. 「5.5.6 SET 構文」節参照.

      LOCAL is a synonym for SESSION.

      To retrieve the value for a GLOBAL variable you can use one of the following commands: 

      SELECT @@global.sort_buffer_size;
SHOW GLOBAL VARIABLES like 'sort_buffer_size';

      To retrieve the value for a SESSION variable you can use one of the following commands: 

      SELECT @@session.sort_buffer_size;
SHOW SESSION VARIABLES like 'sort_buffer_size';

      When you retrieve a variable value with the @@variable_name syntax and you don't specify GLOBAL or SESSION then MySQL will return the thread-specific (SESSION) value if it exists. If not, MySQL will return the global value.

      The reason for requiring GLOBAL for setting GLOBAL only variables but not for retrieving them is to ensure that we don't later run into problems if we later would introduce a thread-specific variable with the same name or remove a thread-specific variable. In this case, you could accidentally change the state for the server as a whole, rather than just for your own connection.

      The following is a full list of all variables that you change and retrieve and if you can use GLOBAL or SESSION with them.

      Variable name Value type Type
      autocommit bool SESSION
      big_tables bool SESSION
      binlog_cache_size num GLOBAL
      bulk_insert_buffer_size num GLOBAL | SESSION
      concurrent_insert bool GLOBAL
      connect_timeout num GLOBAL
      convert_character_set string SESSION
      delay_key_write OFF | ON | ALL GLOBAL
      delayed_insert_limit num GLOBAL
      delayed_insert_timeout num GLOBAL
      delayed_queue_size num GLOBAL
      error_count num LOCAL
      flush bool GLOBAL
      flush_time num GLOBAL
      foreign_key_checks bool SESSION
      identity num SESSION
      insert_id bool SESSION
      interactive_timeout num GLOBAL | SESSION
      join_buffer_size num GLOBAL | SESSION
      key_buffer_size num GLOBAL
      last_insert_id bool SESSION
      local_infile bool GLOBAL
      log_warnings bool GLOBAL
      long_query_time num GLOBAL | SESSION
      low_priority_updates bool GLOBAL | SESSION
      max_allowed_packet num GLOBAL | SESSION
      max_binlog_cache_size num GLOBAL
      max_binlog_size num GLOBAL
      max_connect_errors num GLOBAL
      max_connections num GLOBAL
      max_error_count num GLOBAL | SESSION
      max_delayed_threads num GLOBAL
      max_heap_table_size num GLOBAL | SESSION
      max_join_size num GLOBAL | SESSION
      max_sort_length num GLOBAL | SESSION
      max_tmp_tables num GLOBAL
      max_user_connections num GLOBAL
      max_write_lock_count num GLOBAL
      myisam_max_extra_sort_file_size num GLOBAL | SESSION
      myisam_max_sort_file_size num GLOBAL | SESSION
      myisam_sort_buffer_size num GLOBAL | SESSION
      net_buffer_length num GLOBAL | SESSION
      net_read_timeout num GLOBAL | SESSION
      net_retry_count num GLOBAL | SESSION
      net_write_timeout num GLOBAL | SESSION
      query_cache_limit num GLOBAL
      query_cache_size num GLOBAL
      query_cache_type enum GLOBAL
      read_buffer_size num GLOBAL | SESSION
      read_rnd_buffer_size num GLOBAL | SESSION
      rpl_recovery_rank num GLOBAL
      safe_show_database bool GLOBAL
      server_id num GLOBAL
      slave_compressed_protocol bool GLOBAL
      slave_net_timeout num GLOBAL
      slow_launch_time num GLOBAL
      sort_buffer_size num GLOBAL | SESSION
      sql_auto_is_null bool SESSION
      sql_big_selects bool SESSION
      sql_big_tables bool SESSION
      sql_buffer_result bool SESSION
      sql_log_binlog bool SESSION
      sql_log_off bool SESSION
      sql_log_update bool SESSION
      sql_low_priority_updates bool GLOBAL | SESSION
      sql_max_join_size num GLOBAL | SESSION
      sql_quote_show_create bool SESSION
      sql_safe_updates bool SESSION
      sql_select_limit bool SESSION
      sql_slave_skip_counter num GLOBAL
      sql_warnings bool SESSION
      table_cache num GLOBAL
      table_type enum GLOBAL | SESSION
      thread_cache_size num GLOBAL
      timestamp bool SESSION
      tmp_table_size enum GLOBAL | SESSION
      tx_isolation enum GLOBAL | SESSION
      version string GLOBAL
      wait_timeout num GLOBAL | SESSION
      warning_count num LOCAL
      unique_checks bool SESSION

      Variables that are marked with num can be given a numerical value. Variables that are marked with bool can be set to 0, 1, ON or OFF. Variables that are of type enum should normally be set to one of the available values for the variable, but can also be set to the number that correspond to the enum value. (The first enum value is 0).

      Here is a description of some of the variables:

      Variable Description
      identity Alias for last_insert_id (Sybase compatiblity)
      sql_low_priority_updates Alias for low_priority_updates
      sql_max_join_size Alias for max_join_size
      delay_key_write_for_all_tables If this and delay_key_write are set, then all new MyISAM tables that are opened will use delayed key writes.
      version Alias for VERSION() (Sybase (?) compatability)

      A description of the other variable definitions can be found in the startup options section, the description of SHOW VARIABLES and in the SET section. 「4.1.1 mysqld コマンド行オプション」節参照. 「4.5.6.4 SHOW VARIABLES」節参照. 「5.5.6 SET 構文」節参照.

      6.1.6 コメント 構文

      MySQL は # 行末まで , -- 行末まで そして /* 行中または複数行 */ コメント書式をサポートします: 

      mysql> SELECT 1+1;     # このコメントは行末まで続く
mysql> SELECT 1+1;     -- このコメントは行末まで続く
mysql> SELECT 1 /* これは行中コメント */ + 1;
mysql> SELECT 1+
/*
これは
複数行コメント
*/
1;

      -- コメントスタイルは -- の後ろに最低一つのスペースが 必要であることに注意！

      サーバーはコメント構文を理解しますが、 mysql クライアントが /* ... */ コメントを分析するにはいくつか制限があります：

      • シングルクウォートとダブルクオート文字は引用文字列のトークンの開始を 示します。たとえコメントの中であっても。 もしコメントの中でクオートが二つ目のクオートにマッチしなかった場合、 パーサーはコメントが終了していないと認識します。 mysql を対話モードで実行している場合、 プロンプトが mysql> から '> か "> に変わります。
      • セミコロンは SQL 構文の終了を示し、これに続く文字は次の構文の開始と なります。

      これらの制限は mysql を対話モードで実行している場合と、 mysql にファイルを読み込ませている場合 ( mysql < some-file ) の 両方で現れます。

      MySQL は ANSI SQL コメントの `--' をサポートしません。 「1.7.4.7 コメント開始としての `--'」節参照.

      6.1.7 Is MySQL Picky About Reserved Words?

      共通の問題は、フィールドの名前を、 TIMESTAMP とか GROUP とかの MySQL に埋め込まれているデータ型や関数名と同名にして、 テーブルを作った場合に起こります。 このようなことは行えます(例えば ABS はフィールド名にできます)。 しかし、関数として使用する場合、 この名前がフィールド名として使用されているなら、 関数名と `(' の間の空白は許されません。

      以下の語は MySQL に予約されています。 これらのほとんどは、 ANSI SQL92 によって、 テーブル、フィールド名としての使用は禁止されています。(例えば GROUP)。 またいくつかの語は MySQL が必要とし、 yacc パーサーで 使用しているので予約されています。

      Word Word Word
      ADD ALL ALTER
      ANALYZE AND AS
      ASC AUTO_INCREMENT BDB
      BEFORE BERKELEYDB BETWEEN
      BIGINT BINARY BLOB
      BOTH BTREE BY
      CASCADE CASE CHANGE
      CHAR CHARACTER CHECK
      COLLATE COLUMN COLUMNS
      CONSTRAINT CREATE CROSS
      CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP
      DATABASE DATABASES DAY_HOUR
      DAY_MINUTE DAY_SECOND DEC
      DECIMAL DEFAULT DELAYED
      DELETE DESC DESCRIBE
      DISTINCT DISTINCTROW DIV
      DOUBLE DROP ELSE
      ENCLOSED ERRORS ESCAPED
      EXISTS EXPLAIN FALSE
      FIELDS FLOAT FOR
      FORCE FOREIGN FROM
      FULLTEXT FUNCTION GRANT
      GROUP HASH HAVING
      HIGH_PRIORITY HOUR_MINUTE HOUR_SECOND
      IF IGNORE IN
      INDEX INFILE INNER
      INNODB INSERT INT
      INTEGER INTERVAL INTO
      IS JOIN KEY
      KEYS KILL LEADING
      LEFT LIKE LIMIT
      LINES LOAD LOCALTIME
      LOCALTIMESTAMP LOCK LONG
      LONGBLOB LONGTEXT LOW_PRIORITY
      MASTER_SERVER_ID MATCH MEDIUMBLOB
      MEDIUMINT MEDIUMTEXT MIDDLEINT
      MINUTE_SECOND MOD MRG_MYISAM
      NATURAL NOT NULL
      NUMERIC ON OPTIMIZE
      OPTION OPTIONALLY OR
      ORDER OUTER OUTFILE
      PRECISION PRIMARY PRIVILEGES
      PROCEDURE PURGE READ
      REAL REFERENCES REGEXP
      RENAME REPLACE REQUIRE
      RESTRICT RETURNS REVOKE
      RIGHT RLIKE RTREE
      SELECT SET SHOW
      SMALLINT SOME SONAME
      SPATIAL SQL_BIG_RESULT SQL_CALC_FOUND_ROWS
      SQL_SMALL_RESULT SSL STARTING
      STRAIGHT_JOIN STRIPED TABLE
      TABLES TERMINATED THEN
      TINYBLOB TINYINT TINYTEXT
      TO TRAILING TRUE
      TYPES UNION UNIQUE
      UNLOCK UNSIGNED UPDATE
      USAGE USE USER_RESOURCES
      USING VALUES VARBINARY
      VARCHAR VARCHARACTER VARYING
      WARNINGS WHEN WHERE
      WITH WRITE XOR
      YEAR_MONTH ZEROFILL

      The following symbols (from the table above) are disallowed by ANSI SQL but allowed by MySQL as column/table names. This is because some of these names are very natural names and a lot of people have already used them.

      • ACTION
      • BIT
      • DATE
      • ENUM
      • NO
      • TEXT
      • TIME
      • TIMESTAMP

      6.2 フィールド型

      MySQLは多くのフィールド型をサポートしており、それらは３つのカテゴリに グループ化されます: 数値型、日付及び時間型、そして文字列(文字)型。 この章ではまず、利用できる型の概要から始まり、それから各カテゴリの各フィールド 型の所要記憶容量の要約と、型の属性についてのより詳細な情報を提供します。 概要は意図的に簡潔にまとめています。値として指定できる書式のようなフィールド 型固有の付加情報は、詳細の説明部にて調べて下さい。

      MySQLでサポートされるフィールド型は以下に示す通りです。 後に続く文字の意味は説明のために使われます:

      M
      最大表示サイズを意味します。最大の表示桁数は 255.
      D
      浮動小数点数型に適用され、小数点以下の桁数を表します。 最大の値は 30 ですが、これは M-2 より大きくなってはいけません。

      中カッコ(`['及び`]')は型定義の一部であり、それがオプションであることを 表します。

      もしあるフィールドに ZEROFILL を指定した場合、 MySQL は自動で UNSIGNED 属性をそのフィールドに 追加します。

      Warning: you should be aware that when you use subtraction between integer values where one is of type UNSIGNED, the result will be unsigned! 「6.3.5 Cast Functions」節参照.

      TINYINT[(M)] [UNSIGNED] [ZEROFILL]
      とても小さい整数。符号つきの範囲は -128〜127。符号なしの範囲は 0〜255。
      BIT
      BOOL
      These are synonyms for TINYINT(1).
      SMALLINT[(M)] [UNSIGNED] [ZEROFILL]
      小さい整数。符号つきの範囲は -32768〜32767。 符号なしの範囲は 0〜65535。
      MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL]
      中間の整数。符号ありの範囲は -8388608〜8388607。 符号なしの範囲は 0〜16777215
      INT[(M)] [UNSIGNED] [ZEROFILL]
      通常の整数。符号ありの範囲は -2147483648〜2147483647。符号なしの範 囲は 0〜4294967295
      INTEGER[(M)] [UNSIGNED] [ZEROFILL]
      これは、INTの同義語です。
      BIGINT[(M)] [UNSIGNED] [ZEROFILL]
      大きい整数。 符号ありの範囲は -9223372036854775808〜9223372036854775807。 符号なしの範囲は 0〜18446744073709551615。 BIGINT フィールドについて意識すべきことのいくつか:
      • 全ての演算は符合付き BIGINT または DOUBLE で行われるため、 符合無しの 9223372036854775807 (63 bits) よりも大きな整数を ビット関数以外で使用すべきではありません！ それを行なうと、結果の最後の桁のいくつかは不正になるでしょう BIGINT を DOUBLE に変換する時の丸めエラーのためです。 MySQL 4.0 can handle BIGINT in the following cases:
        • Use integers to store big unsigned values in a BIGINT column.
        • In MIN(big_int_column) and MAX(big_int_column).
        • When using operators (+, -, *, etc.) where both operands are integers.
      • 文字列として格納することで BIGINT フィールドの正確な整数値を常に格 納することができます。この場合、double 表現を介在しません。
      • -、+及び*は、両方の引数がINTEGER値の時、 BIGINT演算を使うことに注意して下さい！ これは、２つの大きな整数の かけ算を行なう(又は整数を返す関数の結果が大きな整数である)時、 結果が9223372036854775807よりも大きい場合に予期しない結果を 受け取ることがあるということを意味しています。
      FLOAT(precision) [UNSIGNED] [ZEROFILL]
      浮動小数点数。Version 4.0 未満では符号なしにはできません。単精度浮動小数点数では precision が <=24 で、倍精度浮動小数点数では 25〜53 の間です。 これらの型は次で述べるFLOATやDOUBLE型に似ています。 FLOAT(X)は、FLOAT及びDOUBLE型に一致する同じ範囲を持っていま すが、 表示サイズや小数点以下桁数が定義されません。 MySQL バージョン 3.23 では、これは正しい浮動小数点です。前の MySQL バージョンでは, FLOAT(precision) は常に小数部は2桁で した。 注意: FLOAT の使用は、MySQL での全ての演算が double 精度で行 なわれるため、いくつかの予期しない問題が起こり得ます。 「A.5.6 Solving Problems with No Matching Rows」節参照. この構文は ODBC 互換です。
      FLOAT[(M,D)] [UNSIGNED] [ZEROFILL]
      小さい浮動小数点数。Version 4.0 未満では符号なしにはできません。 範囲は -3.402823466E+38〜-1.175494351E-38、 0、 1.175494351E-38〜3.402823466E+38です。 Version 4.0 以上では、If UNSIGNED is specified, negative values are disallowed. M は表示幅で D は小数部桁数です。引数が無いか引数が24以下の FLOAT は単精度浮動小数点数を意味します。
      DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL]
      通常の浮動小数点数。Version 4.0 未満では符号なしにはできません。 範囲は -1.7976931348623157E+308〜-2.2250738585072014E-308 、 0、2.2250738585072014E-308〜1.7976931348623157E+308です。 Version 4.0 以上では、If UNSIGNED is specified, negative values are disallowed. M は表示幅で D は小数部桁数です。引数が無いか DOUBLE か、 25 <= X <= 53 である FLOAT(X) は倍精度浮動小数点数を意味します。
      DOUBLE PRECISION[(M,D)] [UNSIGNED] [ZEROFILL]
      REAL[(M,D)] [UNSIGNED] [ZEROFILL]
      これらはDOUBLEの同義語です。
      DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL]
      パック無し浮動小数点数。Version 4.0 未満では符号なしにはできません。CHARフィールドのように振 舞います。`パック無し'は、数値が文字列として格納されることを意味し、数値のそれぞ れの桁、小数点、及び負数での`-'符号に１文字使用します。 Dが0の時、値は小数点や小数部を持ちません。DECIMAL値の最大範囲は DOUBLEと同じですが、実際の範囲はDECIMALフィールドに与えられたM 及びDの選択に強制されます。 Version 4.0 以上では、If UNSIGNED is specified, negative values are disallowed. D を省略した場合は 0 に設定されます。M を省略した場合は 10 に設定されます。 MySQL 3.22 以下では、 M 引数は符号や小数点を含みます。
      DEC[(M[,D])] [UNSIGNED] [ZEROFILL]
      NUMERIC[(M[,D])] [UNSIGNED] [ZEROFILL]
      DECIMALと同じ。
      DATE
      日付。サポートされる範囲は'1000-01-01'から'9999-12-31'まで。 MySQL は'YYYY-MM-DD'の書式でDATE値を表示しますが、DATE フィールドへの値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 「6.2.2.2 DATETIME, DATE, TIMESTAMP 型」節参照.
      DATETIME
      日付と時刻の組み合わせ。サポートされる範囲は'1000-01-01 00:00:00'〜 '9999-12-31 23:59:59'です。MySQLはDATETIME値を 'YYYY-MM-DD HH:MM:SS'という書式で表示しますが、DATETIMEフィールド への値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 「6.2.2.2 DATETIME, DATE, TIMESTAMP 型」節参照.
      TIMESTAMP[(M)]
      タイムスタンプ。範囲は'1970-01-01 00:00:00'〜2037年末までです。 MySQL はTIMESTAMP値をYYYYMMDDHHMMSS、YYMMDDHHMMSS、 YYYYMMDD又はYYMMDDという書式で表示し、それはMに14(もし くは誤ってそれ以上の値を指定した時)、12、8又は6のいずれが指 定されたかに依存します。しかしながらTIMESTAMPフィールドへの値の割当ては、 文字列もしくは数値のいずれかの使用が許されます。 TIMESTAMPフィールドは、最後に操作された時刻を自動的に設定するので、 INSERTやUPDATE操作の時刻を記録するのに役立ちます。 NULL値を与えることによっても、現在時刻を設定できます。 「6.2.2 日付と時間の型」節参照. TIMESTAMP は常に 4 バイトで格納されます。M 引数は TIMESTAMP フィールドがどのように表示されるかだけに影響します。 注意: X が 8 または 14 である TIMESTAMP(X) フィールドは数値として報 告されます。他の TIMESTAMP(X) フィールドは文字列として報告されます。 これは、これらの型を持ったテーブルを確実にダンプとリストアできるようにする ためです！ 「6.2.2.2 DATETIME, DATE, TIMESTAMP 型」節参照.
      TIME
      時間。範囲は'-838:59:59'〜'838:59:59'です。 MySQL はTIME値を'HH:MM:SS'という書式で表示しますが、TIME フィールドへの値の割当ては、文字列もしくは数値のいずれかの使用が許されます。 「6.2.2.3 TIME 型」節参照.
      YEAR[(2|4)]
      年。2桁または4桁形式(デフォルトは4桁)。許される値は、4桁形式では 1901〜2155, 0000 で、2桁形式(70〜69)では 1970〜2069 です。MySQL は YEAR 値を YYYY 形式で表示しますが、 YEAR フィールドへの値の割り当ては文字列と数字のどちらでも使用できま す。(YEAR は MySQL バージョン 3.22 以上での新しい型です。) 「6.2.2.4 YEAR 型」節参照.
      [NATIONAL] CHAR(M) [BINARY]
      固定長文字列で、格納時には必ず指定された長さまで右側に空白を埋めます。 Mの範囲は 0 から 255 文字です。 (MySQL Version 3.23 までは 1 から 255 です。) 後続の空白は値の取り出し時に削除され ます。BINARY キーワードが与えられない場合、CHAR 値のソートと 比較は、デフォルト文字セットに従ってケース非依存の方法で行なわれます。 NATIONAL CHAR (短い形式は NCHAR) は、ANSI SQL で、CHAR フィー ルドがデフォルト文字セットを使用することを定義する方法です。これは MySQL ではデフォルトです。 CHAR は CHARACTER の略記です。 MySQL は CHAR(0) 型のフィールドの生成を許します。これは主 に、実際にはもう値が使われていないフィールドが存在することに依存しているよ うないくつかの古いアプリケーションに対応する必要がある時に便利です。２つの 値だけを取ることができるフィールドを必要とする時にもとても良いことです: NOT NULL として定義されていない CHAR(0) は1ビットだけを占有 し、２つの値だけを取ることができます: NULL または ""。 「6.2.3.1 CHAR 型と VARCHAR 型」節参照.
      CHAR
      This is a synonym for CHAR(1).
      [NATIONAL] VARCHAR(M) [BINARY]
      可変長文字列。 注意: 後続の空白は格納時に削除されます(これは ANSI SQL 仕様と異なります)。 Mの範囲は 0 から 255 文字です。 (MySQL Version 4.0.2 未満では 1 から 255 です) BINARY キーワードが与えられない場合、ソートと比較はケースに依存しません。 「6.5.3.1 暗黙のフィールド定義変更」節参照. VARCHAR は CHARACTER VARYING の略記です。 「6.2.3.1 CHAR 型と VARCHAR 型」節参照.
      TINYBLOB
      TINYTEXT
      最大長 255 (2^8 - 1) 文字の TEXT/BLOB。 「6.5.3.1 暗黙のフィールド定義変更」節参照. 「6.2.3.2 BLOB と TEXT 型」節参照.
      BLOB
      TEXT
      最大長 65535 (2^16 - 1) 文字の TEXT/BLOB。 「6.5.3.1 暗黙のフィールド定義変更」節参照. 「6.2.3.2 BLOB と TEXT 型」節参照.
      MEDIUMBLOB
      MEDIUMTEXT
      最大長 16777215 (2^24 - 1) 文字の TEXT/BLOB。 「6.5.3.1 暗黙のフィールド定義変更」節参照. 「6.2.3.2 BLOB と TEXT 型」節参照.
      LONGBLOB
      LONGTEXT
      最大長 4294967295 (2^32 - 1) 文字の TEXT/BLOB。 「6.5.3.1 暗黙のフィールド定義変更」節参照。注意: サーバ／クライアントプロトコルと MyISAM テーブルは、通信パケット単位 / テーブルレコードで、現在 16M の制限 があるため、この型の範囲全体はまだ使用できません。 「6.2.3.2 BLOB と TEXT 型」節参照。
      ENUM('value1','value2',...)
      列挙。 対象となる文字列は、値を一つだけ持ち、値リスト'value1', 'value2',...(又は NULL)から選ばれます。ENUMは最大65535個の固有値を持つことができます 。 「6.2.3.3 ENUM 型」節参照.
      SET('value1','value2',...)
      組。 対象となる文字列は0以上の値を持ち、それぞれ値リスト'value1', 'value2',... から選ばれなければなりません。 SETは、最大 64個の要素を持つことができます。 「6.2.3.4 SET 型」節参照.

      6.2.1 数値型

      MySQL は ANSI/ISO SQL92 数値型をすべてサポートします。これらの型 は正確な数値データ型(NUMERIC, DECIMAL, INTEGER, SMALLINT)、近似数値型(FLOAT, REAL, DOUBLE PRECISION)を含みます。キーワード INT は INTEGER の同義語で、 DECは DECIMAL の同義語です。

      MySQL では NUMERIC と DECIMAL 型は、SQL92 標準で許 されているように同じ型として実装されています。これらは正確な精度を維持する ことが重要な値(例えば金銭データ)に使用されます。これらの型の一つのフィール ドを宣言する時、精度と大きさが指定できます(通常はそうします); 例えば: 

          salary DECIMAL(5,2)

      この例では、5 (precisoin) は値を格納する重要な数値の桁数を表 します。そして 2 (scale) は小数点に続いて格納される桁数を表 します。従って、この場合 salary フィールドに格納することができる値 の範囲は、-99.99 から 99.99 です。 (MySQL can actually store numbers up to 999.99 in this column because it doesn't have to store the sign for positive numbers)

      ANSI/ISO SQL92 では、構文 DECIMAL(p) は DECIMAL(p,0) と等しいです。同様に、 構文 DECIMAL は DECIMAL(p,0) と等しいです。ここで p の値の決定は実装に許されてます。DECIMAL/NUMERIC データ型のこ れらの異なる形式は、MySQL は現在サポートしていません。この型の主 な利益は精度と大きさの両方を明示的に制御する機能から引き出されるので、これ は通常深刻な問題ではありません。

      DECIMAL と NUMERIC 値は、値の小数の精度を維持するため、バイ ナリ浮動小数点数としてではなく、文字列として格納されます。1文字は値のそれ ぞれの桁(scale > 0 の場合)と `-' 記号(負数の場合)に使用されま す。scale が 0 の場合、DECIMAL と NUMERIC 値は小数点 と小数部を含みません。

      DECIMAL と NUMERIC 値の最大範囲は DOUBLE と同じです。 しかし DECIMAL や NUMERIC フィールドに与えられる実際の範囲は フィールドに与えられた precision と scale によって強制されま す。このフィールドに、指定された scale で許されるよりも多い桁の小数 部を持つ数値が割り当てられた場合、値はその scale に丸められます。 DECIMAL や NUMERIC フィールドに、指定された(またはデフォルト の) precision と scale で示された範囲を超えた大きさの値を割 り当てた時、MySQL はその範囲の対応する最大値を表す値を格納します。

      ANSI/ISO SQL92 標準に対する拡張として、上の表にリストしたように、 MySQL は整数型 TINYINT, MEDIUMINT, BIGINT も サポートします。MySQL によってサポートされる他の拡張として、オプ ションで、型の基本キーワードに続けて括弧内に指定する整数値の表示幅(例えば INT(4))があります。このオプションの幅指定は、フィールドに指定された 幅よりも少ない幅の値の表示の左側を埋めるために使用されます。しかしフィール ドに格納することができる値の範囲や、フィールドに指定された幅を超える幅の値 について表示される桁数は制約されません。オプションの拡張属性 ZEROFILL を指定して使用された場合、デフォルトの埋められる空白は 0 で置き換えられます。例えば、INT(5) ZEROFILL として宣言されたフィー ルドでは、値 4 は 0004 として取り出されます。注意: 整数フィー ルド内に表示幅よりも大きい値を格納する場合、MySQL が複雑な join のために一時テーブルを生成する時に、問題を体験するでしょう。この場合 MySQL はデータがオリジナルのフィールド幅に合っていることを信用す るためです。

      すべての整数型はオプションの(非標準)属性 UNSIGNED を持つことができ ます。符合無しの値はフィールド内に正の数だけを許可したくて、フィールドに対 して少し大きい数値の範囲が必要な時に使用できます。

      As of MySQL 4.0.2, floating-point types also can be UNSIGNED. As with integer types, this attribute prevents negative values from being stored in the column. Unlike the integer types, the upper range of column values remains the same.

      FLOAT 型は近似数データ型を表すために使用されます。ANSI/ISO SQL92 標 準は、FLOAT キーワードに続く括弧中にオプションの精度(指数の範囲では ない)の指定を許しています。MySQL 実装はこのオプションの精度指定も サポートしています。キーワード FLOAT が精度の指定無しでフィールド型 として使用された時は、MySQL は値を格納するために4バイトを使用しま す。FLOAT キーワードに続く括弧中に2つの数値を与える構文もサポートさ れます。このオプションでの、最初の数値は値に必要な容量をバイトで表します。 2番目の数値は、格納、表示される小数部の桁数を指定します(DECIMAL と NUMERIC と同様)。MySQL がフィールドに指定されたよりも大き い小数部の桁数を持つ数値をこのフィールドに格納する時、値の格納時に余計な桁 を取り除くように値が丸められます。

      REAL と DOUBLE PRECISION 型は精度指定を許しません。 ANSI/ISO SQL92 標準に対する拡張として、MySQL は DOUBLE を DOUBLE PRECISION 型の同義語として認識します。REAL の精度は DOUBLE PRECISION の指定よりも小さいことを要求する標準と異なり、 MySQL はどちらも8バイトの倍精度小数点の値として実装しています (非"ANSI モード"で実行した場合)。移植性を最大にするためには、近似数値 データ値の格納を要求するコードは、精度や小数部桁数の指定無しの FLOAT か DOUBLE PRECISION を使用すべきです。

      フィールドの型の値の許容範囲を超えた数値を代入しようとすると、MySQL は その値を許容範囲いっぱいに切り詰め、その結果を代わりに代入します。

      例えば、 INT フィールドの範囲は -2147483648 から 2147483647 です。 もし -9999999999 を INT フィールドに挿入しようとすると、値は範囲の 最低値に修正され、 -2147483648 が代わりに代入されます。同様に、 9999999999 の場合、 2147483647 が代わりに代入されます。

      そして、INT フィールドが符号無しの場合、フィールドの範囲の大きさは 同じですが、限界値は 0 と4294967296 になります。 もし -9999999999 と 9999999999 を代入しようとすると、 値は 0 と 4294967296 として代入されます。

      ALTER TABLE, LOAD DATA INFILE, UPDATE または multi-row INSERT 時、これらの変換は `警告' として得られます。

      Type Bytes From To
      TINYINT 1 -128 127
      SMALLINT 2 -32768 32767
      MEDIUMINT 3 -8388608 8388607
      INT 4 -2147483648 2147483647
      BIGINT 8 -9223372036854775808 9223372036854775807

      6.2.2 日付と時間の型

      日付と時間の型は DATETIME, DATE, TIMESTAMP, TIME, YEAR です. これらはそれぞれ値に適正な範囲があり、 ``zero'' はあなたが間違った値を指定した場合に用いられます。注意: MySQL は 確実に '厳密でない' 正しい日付の値、例えば 1999-11-31 を格納するこ とができます。この理由は、日付をチェックする処理の責任はアプリケーションに あり、SQL サーバにはないと考えているからです。日付を'速く'チェックするため に、MySQL は月が 0〜12 の範囲であるかと日が 0〜31 の範囲であるか だけをチェックします。上述の範囲は、MySQL が DATE または DATETIME フィールドに、日または月日が 0 である日付を格納できるため に定義されています。これは、正確な日付を知らない誕生日を登録する必要がある アプリケーションに非常に有用です。この場合、1999-00-00 や 1999-01-00 のような日付を単純に登録できます(もちろん、このような日 付を DATE_SUB() や DATE_ADD のような関数で使用して、正しい値 が返ることは期待できません)。

      これは、日付と時間型で作業する場合に、一般的に考慮しなければならないことです:

      • MySQLは、標準形式で与えられた日付や時間から値を抽出しますが、与えられた 多様な形式の値(例えば、指定された値を日付や時間型に割り当てたり、比較したり)を解 釈しようと試みます。 それでも、次節で述べる形式だけがサポートされます。 それは、正当な値が与えられることを期待し、他の形式の値を使用されるような事態が起 こると、どのような結果となるか予想できません。
      • MySQL はいくつかの形式に値を変えてくれますが、 常に年の部分と日にちの部分は左から与えられていると期待しています。 日付は 年-月-日 の順(例えば、'98-09-04')でなくてはなりません。 月-日-年 や 日-月-年 の様などこでも使われているような形であってはなりません。 (例えば、'09-04-98'や'04-09-98').
      • MySQL は、もし数値の文脈で日付と時間の型が使用されると、 自動的に日付と時間を数値に直します。逆も行います。
      • MySQL が範囲外の誤った値を日付と時間型として受け取った場合 (このセクションの最初をみてください)、その値は ``ゼロ'' に変換されます。 (例外は、範囲外のTIME値が適切なTIMEの範囲の限界値に切り詰められる ことです。) 以下に、それぞれの型の `ゼロ' の形式を示します：
        フィールドタイプ `ゼロ'値
        DATETIME '0000-00-00 00:00:00'
        DATE '0000-00-00'
        TIMESTAMP 00000000000000 (長さは表示サイズに依存し ます)
        TIME '00:00:00'
        YEAR 0000
      • `ゼロ'値は特別ですが、表に示された値を明示的に使用して、格納したり参照したりでき ます。 この値は、 '0' 又は 0 を使用することにより、より簡潔に書くこともで きます。
      • MyODBC 内で使用されている `ゼロ' の日付と時間は、 MyODBC 2.50.12 以上では自動的に NULL に変換されます。 これは ODBC がこれらの値を扱えないからです。

      6.2.2.1 西暦２０００年問題とデータ型

      MySQL 自体は2000年問題に対して安全です( 「1.2.5 2000 年対応」節参照)が、 MySQL に提示される入力値に関してはそうではありません。2桁の 年の入力は何世紀なのかわからないので全て曖昧です。このような値は MySQL が内部で年に4桁を使っていることから4桁の形式に変換されてしまいます。

      MySQL は曖昧な日付を DATETIME, DATE, TIMESTAMP および YEAR 型に関して、以下の ルールに従って解釈します。

      • 00-69 の範囲の年は 2000-2069 に変換。
      • 70-99 の範囲の年は 1970-1999 に変換。

      これらのルールはデータが何を意味しているかに対して妥当な推定を与えるに 過ぎないことに注意してください。この MySQL 発見的手法が正しい値を生成し ない場合は曖昧でない4桁の年を含む入力を与えるべきです。

      ORDER BY は2桁の YEAR/DATE/DATETIME 型を正しくソートされます。

      注意: MIN() と MAX() のようないくつかの関数は TIMESTAMP/DATE を数値に変換します。これは年が2桁のタイムスタンプはこれらの関数で正しく動作しな いことを意味します。この場合の修復は、TIMESTAMP/DATE を4桁の年の形 式に変換するか、MIN(DATE_ADD(timestamp,INTERVAL 0 DAYS)) のような何 かを使用することです。

      6.2.2.2 DATETIME, DATE, TIMESTAMP 型

      DATETIME, DATE, TIMESTAMP型はお互いに関連しています。このセ クションではそれらの特徴と、それぞれがどう同じでどう違うかを示します。

      DATETIME 型は日付と時刻の情報を含む値が必要な場合に使います。MySQL は DATETIME 値を 'YYYY-MM-DD HH:MM:SS' のフォーマットで取り出し、 表示します。 サポートされる範囲は '1000-01-01 00:00:00' から '9999-12-31 23:59:59' です。 (「サポートされる」とはさらに過去の値でも動くかも知れませんが保証の限りではない という意味です)

      DATE 型は時刻の部分なしで日付の値のみが必要な場合に使います。MySQL は DATE 値を'YYYY-MM-DD' のフォーマットで取り出し、表示します。サポ ートされる範囲は '1000-01-01' から '9999-12-31' です。

      TIMESTAMP タイプは INSERT や UPDATE 操作に自動的に 現在の日付と時刻をマークする場合に提供される型です。 もし複数の TIMESTAMP フィールドがある場合には最初 の一つだけが自動的に更新されます。

      最初の TIMESTAMP フィールドの自動更新は以下のいずれかの条件で起こります：

      • そのフィールドが明示的に INSERT または LOAD DATA INFILE 文で指定さ れていないとき。
      • そのフィールドが明示的に UPDATE 文で指定されず、かつ、他のフィールドの値 が変わった場合。 (もともとフィールドに入っていた値と同じ値に更新しようとする UPDATE 文は TIMESTAMP フィールドを更新しないことに注意。なぜならあるフィールドを現在 と同じ値に変えようとしても MySQL は効率のためにそれを無視するからです。)
      • 明示的に TIMESTAMP フィールドを NULL にした場合。

      最初以外の TIMESTAMP フィールドも現在の日付と時刻にすることができます。そ れらのフィールドをNULL または NOW() にすることです。

      どの TIMESTAMP フィールドも明示的に望む値をセットすることで現在の日時でな い値にすることができます。それは最初の TIMESTAMP フィールドについても同じ です。この特性は例えば TIMESTAMP フィールドをあるレコードが生成された時の 日時にし、その後その行が更新されても変化しないようにしたいというようなときに使え ます。

      • MySQL にレコードが生成されたときにそのフィールドをセットさせる。これで 現在日時に初期化される。
      • 以降の他のフィールドに対する更新時に TIMESTAMP フィールドをそれ自体が今持 っている値に明示的に更新する。

      一方、この手法は DATATIME フィールドを行生成時に NOW() で初期化し 、以降の更新時に それをほうっておくのと同じように簡単であるとわかるでしょう。

      TIMESTAMP の値は 1970 年の最初から 2037 年のどこかの時点ま での範囲で有効で、 1秒の時間分解能を持ちます。値は数値として表示されます。

      MySQL が TIMESTAMP 値を取り出したり表示するのに使うフォーマット は以下の表 に示すようにその表示サイズに依存します。「目一杯の」 TIMESTAMP フォーマッ トは14桁ですが、 TIMESTAMP フィールドはより短い表示サイズで生成することも できます：

      フィールド型 表示フォーマット
      TIMESTAMP(14) YYYYMMDDHHMMSS
      TIMESTAMP(12) YYMMDDHHMMSS
      TIMESTAMP(10) YYMMDDHHMM
      TIMESTAMP(8) YYYYMMDD
      TIMESTAMP(6) YYMMDD
      TIMESTAMP(4) YYMM
      TIMESTAMP(2) YY

      全ての TIMESTAMP フィールドは表示サイズに関係なく同じ格納サイズを持ちます。 もっとも一般的な表示サイズは 6 , 8 , 12 および 14 です。表示サイズはテーブル生成 時に任意の値に指定できますが、 0 および 14 以上の値は強制的に 14 になります。1 から 13 までの奇数のサイズは強制的に一つ大きい偶数になります。

      DATETIME, DATE, TIMESTAMP 値は以下の共通フォーマットセット のいずれかを使って指定できます：

      • 文字列で 'YYYY-MM-DD HH:MM:SS' か 'YY-MM-DD HH:MM:SS' の形式。 "柔軟な"書き方を許しています -- 日付や時刻の区切り文字として、いかなる句読記号 も使用できます。例えば、'98-12-31 11:30:45', '98.12.31 11+30+45', '98/12/31 11*30*45', '98@12@31 11^30^45' は等価です。
      • 文字列で 'YYYY-MM-DD' か 'YY-MM-DD' の形式。 これも"柔軟な"書き方ができます。 例えば, '98-12-31','98.12.31', '98/12/31', '98@12@31' は 等価です。
      • 文字列 'YYYYMMDDHHMMSS' または 'YYMMDDHHMMSS' フォーマット。 「緩やかな」文法が認められていて、句読記号は日付、時刻部分の区切り として使えます。例えば '98-12-31 11:30:45', '98.12.31 11+30+45', '98/12/31 11*:30*:45', '98@12@31 11^30^45' は全て等価です。
      • 文字列 'YYYY-MM-DD' または 'YY-MM-DD' フォーマット。 これも「緩やかな」文法が認められています。例えば '98-12-31', '98.12.31', '98/12/31', '98@12@31'は全て等価です。
      • 区切り文字なしの文字列 'YYYYMMDDHHMMSS' または 'YYMMDDHHMMSS' フォ ーマットで日時として意味のあるもの。 例えば '19970523091528' および '970523091528' は '1997-05-23 09:15:28' と解釈されます。しかし '971122129015' は無効で (時と分の部分がおかしい)、 '0000-00-00 00:00:00' になります。
      • 区切り文字なしの文字列 'YYYYMMDD' または 'YYMMDD' フォーマットで、 日付として意味のあるもの。 例えば '19970523' および '970523' は '1997-05-23' と解釈 されます。 しかし '971332' は無効で(月と日の部分がおかしい)、 '0000-00-00' になります。
      • YYYYMMDDHHMMSS または YYMMDDHHMMSS のフォーマットの数値で、日時と して意味のあるもの。例えば 19830905132800 および 830905132800 は '1983-09-05 13:28:00' と解釈されます。
      • YYYYMMDD または YYMDD のフォーマットの数値で日付として意味のある もの。 例えば 19830905 および 830905 は '1983-09-05' として解釈さ れます。
      • NOW() や CURRENT_DATE のように DATETIME , DATE , TIMESTAMP のコンテキストで アクセス可能な値を返す関数の結果。

      無効な DATETIME , DATE , TIMESTAMP の値は適切な「ゼロ」値に 変換されます('0000-00-00 00:00:00' , '0000-00-00' または 00000000000000 )。

      日時の部分に区切りを持つ文字列で指定される値で、月、日の値が10未満の場 合は2桁で指定しなくてもかまいません。 '1979-6-9' は '1979-06-09' と等価です。同様に時刻の部分に区切りを持つ文字列で指定される値で、時、分、秒が 10 未満の場合は2桁で指定しなくてもかまいません。 '1979-10-30 1:2:3' は '1979-10-30 01:02:03' と等価です。

      数値でしていされる値は 6, 8, 12 または 14 桁である必要があります。もしその数 値が 8 または 14 桁の長さの時はそれぞれ YYYYMMDD および YYYYMMDDHHMMSS フォーマットで、最初の 4 桁で年が与えられるものと仮定 されます。もしその数値が 6または12桁の長さの時は YYMMDD および YYMMDDHHMMSS フォーマットで最初の2桁で年が与えられるものと仮定されます。 これら以外の長さの数値はあとに 0 が追加されてこれらのうちのもっとも近い 長さのものと解釈されます。

      区切りなしの文字列で与えられる値はそれ自身の長さを使って解釈されます。 もし文字列が8または14文字ならば年は最初の4文字で与えられると仮定されま す。そうでなければ最初の2文字で与えられると仮定されます。文字列は左か ら右に年、月、日、時、分、秒と文字列中に表現されている分だけ順に解釈さ れます。つまり6文字以下の文字列は使ってはいけないということです。例え ば1999年3月を指定するつもりで '9903' を指定した場合、MySQL は「ゼロ」日付 をテーブルに挿入します。これは年と月の部分は 99 と 03 ですが日の部 分が欠けている(ゼロ)ために値が有効な日付でないために起こります。

      TIMESTAMP フィールドは有効な値を、表示サイズに関係なく指定された値を最高 精度の時間分解能で格納します。このことはいくつかの意味合いを持ちます。

      年の値が二桁で指定された場合、世紀の部分がないので曖昧な値となります。 MySQL は二桁の年の値を以下に示す規則にそって変換します：

      • 列の型がTIMESTAMP(4)であってもTIMESTAMP(2)であっても常に年月日を指定 すること。そうでなければ値は無効で0が格納されます。
      • もし短い形式の TIMESTAMP を ALTER TABLE を使って拡張しようとした場 合、拡張前には「隠れていた」情報が現れます。
      • 同様に TIMESTAMP フィールドを縮めた場合も、値が表示された時により少ない情 報しか現れないという点を除いて、情報は失われません。
      • TIMESTAMP 値は最高精度の時間分解能で格納されますが、内部的に格納され た値を直接操作できる関数は UNIX_TIMESTAMP() のみです。他の関数はフォーマ ットされて取り出された値について操作します。つまり、 HOUR() や SECOND() などの関数は TIMESTAMP 値の対応する部分がフォーマットされた 値で含まれないと使うことができません。例えば TIMESTAMP 列の HH の部分は 表示サイズが少なくとも10以上ないと表示されないので、それより短い TIMESTAMP 値 に HOUR() の操作を行っても無意味な値しか得られません。

      ある日付型を他の日付型のオブジェクトに拡張して指定することができます。 しかしそれは値の変化や情報の欠落を起こす可能性があります。

      • DATE の値を DATETIME か TIMESTAMP の物に与えた場合、 時刻の部分は '00:00:00' になります。これは DATE 値が 時刻の情報を持っていないからです。
      • DATETIME か TIMESTAMP の値を DATE の物に与えた場合、 時刻の部分は削られます。これは DATE 値が 時刻の情報を持っていないからです。
      • DATETIME, DATE, TIMESTAMP 値は同じフォーマットのセットを使 って表現できますが、どの型も同じ値の範囲を持っているわけではないことを覚えておい てください。例えば TIMESTAMP 値は 1970 年より前や 2037 年よ り後の値にはできません。つまり '1968-01-01' という値は DATETIME や DATE の値としては有効ですが TIMESTAMP の値としては無効で、 そのようなオブジェクトを指定した場合は 0 に変換されます。

      日付の値を指定するときの落とし穴に注意してください

      • 文字列として指定される値の柔軟なフォーマットに騙されないよう。例え ば '10:11:12' は `':'' を区切り文字とする時刻のように見えますが、日 付のコンテキストで使われるとこれは '2010-11-12' と解釈されます。 '10:45:15' は '45' が有効な月ではないので '0000-00-00' に 変換されます。
      • The MySQL server only performs basic checking on the validity of a date: days 00-31, months 00-12, years 1000-9999. Any date not within this range will revert to 0000-00-00. Please note that this still allows you to store invalid dates such as 2002-04-31. It allows web applications to store data from a form without further checking. To ensure a date is valid, perform a check in your application.
      • 2桁で表される年は世紀の部分が不明なので曖昧です。 MySQL は以下のルール で2桁の年を解釈します。
        • 00-69 の範囲にある年の値は 2000-2069 年とする。
        • 70-99 の範囲にある年の値は 1970-1999 年とする。

      6.2.2.3 TIME 型

      MySQL は TIME の値を 'HH:MM:SS' (時の部分が大きい場合は 'HHH:MM:SS') というフォーマットで扱い、また表示します。 (時の部分が大きい場合は 'HHH:MM:SS')。 TIME 値の範囲は '-838:59:59' から '838:59:59' の範囲です。 時の部分がこんなに大きいのは、TIME 型は一日すなわち24時間以内 の時刻を表現するのに用いられるだけではなく経過時間や二つの事象の間隔 (どちらも２４時間を越えたり、負の数になる場合もあります)を表現すること もあるからです。

      TIME 値は様々なフォーマットで指定可能です：

      • 文字列で 'D HH:MM:SS.fraction' というフォーマット。 (MySQLはまだこの fraction を time フィールドに保存できません)。 以下の ``柔軟な'' 文法が使用できます： HH:MM:SS.fraction, HH:MM:SS, HH:MM, D HH:MM:SS, D HH:MM, D HH または SS。 ここで、D は 0〜33 の間の日です。
      • 文字列で 'HHMMSS' というように区切りのないフォーマットで時刻として有効 なもの。例えば '101112' は '10:11:12' と解釈されますが '1097 12' は無効で(分の部分が無意味) '00:00:00' になります。
      • 数値で HHMMSS のフォーマットで時刻として有効なもの。 例えば 101112 は '10:11:12' と解釈されます。 次の別の形式も解釈できます: SS, MMSS,HHMMSS, HHMMSS.fraction。注意: MySQL はまだ fraction 部を保存でき ません。
      • 例えば CURRENT_TIME のように TIME のコンテキストで受け付けられる値 を返す関数の結果。

      文字列で時刻の各部の区切りを含む TIME の値については、時、分、秒が 10 以下の場合、２桁の数字を指定する必要はありません。'8:3:2' は '08:03:02' と同じです。

      「短い」 TIME 値を TIME フィールドとして指定する場合は要注意です。 コロンなしでは、MySQL はその値のもっとも右端の桁は秒を表すと仮定して解 釈します。 (MySQL は TIME の値を一日のうちの時刻としてより経過時間として 解釈します)。例えば '11:12','1112', 1112 が '11:12:00' (11時12分)を表しているつもりでいても、 MySQL はこれらを '00:11:12' (11分12秒)として解釈します。 同様に '12' および 12 は '00:00:12' と解釈します。

      TIME の範囲外にある値で値以外は正しいものは範囲の端の値の適当な方にクリッ プされます。例えば '-850:00:00' および '850:00:00' は それぞれ '-838:59:59' および '838:59:59' になります。

      無効な TIME 値は '00:00:00' に変換されます。 ここで '00:00:00' 自体は有効な TIME 値なので、 テーブル内に保存された'00:00:00'という値からそれがもとも と '00:00:00' と指定された値なのか無効なために変換された結果なのかを区 別する方法はないことに注意してください。

      6.2.2.4 YEAR 型

      YEAR 型は年を表現するのに使われる1バイトの値です。

      MySQL は YEAR の値を YYYY というフォーマットで扱い、 また表示します。範囲は 1901 から 2155 です。

      YEAR 型は様々なフォーマットで指定可能です：

      • '1901' から '2155' の範囲にある4桁の文字列
      • 1901 から 2155 の範囲にある4桁の数値。
      • '00' から '99' の範囲にある2桁の文字列。 '00' から '69' までおよび '70' から '99' までの範囲はそれぞれ 2000 から 2069 まで および 1970 から 1999 までの範囲の YEAR型に変換されます。
      • 1 から 99 の範囲にある2桁の数値。1 から 69 まで および 70 から 99 までの範囲は それぞれ 2001 から 2069 までおよび 1970 から 1999 まで の範囲の YEAR 型に変換されます。 2桁の数値の場合は2桁の文字列の場合と若干異なっている点に注意してください。 なぜなら0を数値として指定し、それを2000年として解釈させることができないからです。 その場合は文字列で '0' または '00' を指定しなければ なりません。そうでなければ数値0は無効なYEAR値を示す 0000 に変換されます。
      • 例えば NOW() のように YEAR コンテキストで受け入れられる値を返す関 数の結果。

      無効な YEAR 値は 0000 に変換されます。

      6.2.3 文字列型

      文字列型はCHAR, VARCHAR, BLOB, TEXT, ENUM, SET です。このセクションは、それらの型がどのように動作 するかと、要求されるサイズと、クエリ内での使用方法を説明します。

      Type Max.size Bytes
      TINYTEXT or TINYBLOB 2^8-1 255
      TEXT or BLOB 2^16-1 (64K-1) 65535
      MEDIUMTEXT or MEDIUMBLOB 2^24-1 (16M-1) 16777215
      LONGBLOB 2^32-1 (4G-1) 4294967295

      6.2.3.1 CHAR 型と VARCHAR 型

      CHAR 型と VARCHAR 型はよく似ていますが格納、取り出しの手順に違いが あります。

      CHAR フィールドの長さはテーブルを生成するときに宣言した長さに固定されます。 長さは 1 から 255 までの値を取ります。CHAR が格納されるときには指定された 長さになるように右側に空白が詰められます。CHAR の値が取り出された場合には 右側(後続)の空白は取り除かれます。

      VARCHAR フィールドの値は可変長文字列です。 VARCHAR フィールドは CHAR フィールド と同じく 1 から 255 までの長さに宣言できます。 (MySQL バージョン 3.23 では, CHAR の長さは 0 から 255 まで許され ています.) しかし CHAR 型と異なり VARCHAR 型の値は必要な文字数の分に 長さを記録する1 バイトを足した領域に格納されます。値には桁合わせのための空白はつ けられません。後続の空白は値の格納時に取り除かれます。(この空白の除去は ANSI SQL仕様とは違っています。)

      もし CHAR または VARCHAR フィールドに、フィールドの最大長を 越える長さの値を与えた場合は、適合するように切り詰められます。

      以下の表はこれらの二つのフィールド型の違いを、CHAR(4) および VARCHA R(4) に様々な文字列値を格納した結果を示すことで表しています。

      値 CHAR(4) 必要な格納域 @code {VARCHAR(4)} 必要な格納域
      '' ' ' 4 バイト '' 1 バイト
      'ab' 'ab ' 4 バイト 'ab' 3 バイト
      'abcd' 'abcd' 4 バイト 'abcd' 5 バイト
      'abcdefgh' 'abcd' 4 バイト 'abcd' 5 バイト

      CHAR(4) フィールドの後続の空白は取り出し時にとりのぞかれるので、CHAR(4)お よび VARCHAR(4) から取り出される値はどの場合でも同じです。

      CHAR および VARCHAR フィールドの値はテーブルの生成時に BINARY 属性が つけられない限り、大文字と小文字を区別しないでソート・比較されます。BINARY 属性は その列の値が大文字、小文字を区別して、MySQLサーバを実行しているマシンのASCII順に ソート・比較されることを意味します。 BINARY はフィールドがどのように格納されるか、どのように取り出される かには影響しません。

      BINARY 属性は「固定的」です。つまり、もし BINARY であると指定された フィールドが式の中にあると式全体が BINARY の値として比較されるのです。

      MySQL はテーブル生成時に何も断らずにCHAR または VARCHAR 型のフィールドを変更する事があります。 「6.5.3.1 暗黙のフィールド定義変更」節参照.

      6.2.3.2 BLOB と TEXT 型

      BLOB は大きなバイナリ型のオブジェクトで、可変長のデータを保持できます。 4 つの BLOB 型、すなわち TINYBLOB, BLOB, MEDIUMBLOB と LONGBLOB は保持できるデータの最大長が違うだけです。 「6.2.6 各フィールド型の所要容量」節参照.

      4 つの TEXT 型、すなわち TINYTEXT, TEXT, MEDIUMTEXT と LONGTEXT は 4 つの BLOB 型に対応し、同じ最大長と 格納条件を持っています。 TEXT と BLOB の違いは、 TEXT はケースに依存しないでソートと比較され、 BLOB はケースに依存して(文字コードで)比較されることだけです。 いうならば、TEXT は、ケースに依存しない BLOB です。

      もし BLOB や TEXT フィールドにそれらの最大長以上の値が与えられた 場合、その値はきっちり収まるように切り落とされます。

      ほとんどの点で、TEXT フィールドを VARCHAR の大きい物と見なすことが 出来ます。 同様に、BLOB フィールドは VARCHAR BINARY フィールドの大きくなった 物です。 違いは、

      • MySQL バージョン 3.23.2 以上では、BLOB と TEXT 項に インデックスを持つことが出来ます。それ以前のバージョンでは インデックスをもつことが出来ません。
      • VARCHAR フィールドで行っているようには、BLOB と TEXT フィー ルドの値の後ろについている連続した空白文字は切り落とされません。
      • BLOB と TEXT 項は DEFAULT 値を持つことが出来ません。

      MyODBC は BLOB を LONGVARBINARY として、 TEXT を LONGVARCHAR として定義します。

      BLOB と TEXT フィールドは極端に長いので、それらを使用する際には、 いくつかの困った事にでくわすかもしれません：

      • もし GROUP BY か ORDER BY を BLOB フィールドや TEXT フィールドで使用したいなら、フィールドの値を固定長のものに変換しなくてはなりま せん。標準的な方法は、 SUBSTRING 関数を使用することです。 たとえば： 
        mysql> SELECT comment FROM tbl_name,SUBSTRING(comment,20) AS substr
    ->                 ORDER BY substr;
        もしこれをしない場合、フィールドの最初の max_sort_length バイトが ソート時に使用されます。 max_sort_length のデフォルト値は 1024; この値は mysqld サーバー起動時に -O オプションを使用することで 変更できます。 フィールドの位置を指定することによってか、エイリアスを使用することによって、 BLOB や TEXT の値で group 化できます。 
        mysql> SELECT id,SUBSTRING(blob_col,1,100) FROM tbl_name GROUP BY 2;
mysql> SELECT id,SUBSTRING(blob_col,1,100) AS b FROM tbl_name GROUP BY b;
      • BLOB または TEXT オブジェクトの最大長はその型により決定されますが、 あなたがクライアントとサーバの間で実際に送ることができるは最大長は、 利用可能なメモリ量とコミュニケーションバッファのサイズによって決定されます。 メッセージバッファサイズを変えることができますが、その場合、サーバーとクライアン ト、両方共に変更しなければなりません。 「5.5.2 サーバーパラメーターのチューニング」節参照.

      それぞれの BLOB, TEXT フィールドは、一意のアロケートされたオブジェ クトによって、内部では表されることに注意してください.。 これはテーブルが開かれるときに一度だけアロケートされる他のフィールドとは対照的で す。

      6.2.3.3 ENUM 型

      ENUM はストリングオブジェクトで、 その値は、通常、テーブル作成時のフィールド定義で列挙された値の中から選ばれます。

      値はある状況下では 空文字 ("") か NULL を取ることがあります：

      • もし ENUM に無効な値 (列挙されている値の中に含まれない文字) を 代入した場合、 そのエラーになる文字の代わりに空文字が挿入されます。
      • もし ENUM が NULL と定義された場合, NULL はそのフィールドで 許可される値となり、デフォルト値が NULL になります。 もし ENUM が NOT NULL と定義されたならば、 デフォルト値は、 列挙リストの最初の値になります。

      列挙されたそれぞれの値はインデックスを持ちます：

      • 列挙リストの要素は 1 から付番されます。
      • 空文字エラーのインデックス値は 0 。 これは不正な ENUM 値が与えられているレコードを見つけるために 以下のような SELECT 構文が使用できることを意味します： 
        mysql> SELECT * FROM tbl_name WHERE enum_col=0;
      • NULL のインデックス値は NULL.

      たとえば、フィールドが ENUM("one", "two", "three") と定義されたなら、 以下に示す値をとります。 それぞれのインデックス値も示します。

      値 インデックス
      NULL NULL
      "" 0
      "one" 1
      "two" 2
      "three" 3

      列挙は最大 65535 個の要素まで可能です。

      Starting from 3.23.51 trailing spaces are automatically deleted from ENUM values when the table is created.

      ENUM フィールドに値を与える場合は大文字小文字は無関係です。 しかし、後でフィールドから検索される値は、大文字小文字をもちます。 これはテーブル作成時に与えられたリストの値です。

      もし ENUM を数値の文脈で検索した場合、そのメンバーを前から数えた 時の順番が数値で返ってきます。 たとえば、ENUM フィールドから次のようにして数値を取り出すことができ ます: 

      mysql> SELECT enum_col+0 FROM tbl_name;

      もし ENUM に数値を代入しようとした場合、その数値の位置にある メンバーが代入されます。 (しかし、これは LOAD DATA では働きません。これはすべての入力を文字 列として扱います。) It's not advisable to store numbers in an ENUM string because it will make things confusing.

      ENUM 値は列挙メンバがフィールド指定にリストされた順に従ってソートさ れます。(つまり、ENUM 値はインデックス値に従ってソートされます。) 例えば、ENUM("a", "b") ならば "a" が "b" の前にソートされ、 ENUM("b", "a") ならば "b" が "a" の前にソートされます。 空文字列は空ではない文字の前にソートされ、 NULL は他の列挙の前に並びます。 To prevent unexpected results, specify the ENUM list in alphabetical order. You can also use GROUP BY CONCAT(col) to make sure the column is sorted alphabetically rather than by index number.

      ENUM フィールドで指定可能な値のリストを全て取りたいならば、 次のようにします： SHOW COLUMNS FROM table_name LIKE enum_column_name そして二番目のフィールドの ENUM 定義を分析します。

      6.2.3.4 SET 型

      SET は文字型オブジェクトでゼロかそれ以上を値持ちます。 テーブル作成時には、それぞれの値はリストから選ばれるべきです。 SET 型のフィールドの値は、コンマ(`,') 区切りで並べられた複数のメンバーで構成されています。 これは、 SET メンバーの値中にコンマを含むことが出来ない、 ということです。

      例えば、 SET("one", "two") NOT NULL と指定されたフィールドは以下の値をとります： 

      ""
"one"
"two"
"one,two"

      SET は最大 64 個の異なったメンバーがもてます。

      Starting from 3.23.51 trailing spaces are automatically deleted from SET values when the table is created.

      MySQL は SET の値を数値として代入します。代入された 値の最下位のビットが最初のメンバーに対応します。もし SET 値を 数値の文脈で検索した場合、検索される値はフィールドの値に対応します。 たとえば、SET フィールドから次のようにして数値を取り出すことができ ます: 

      mysql> SELECT set_col+0 FROM tbl_name;

      もし数値が SET フィールドに代入された場合、 二進数で表される数値のビットによって、メンバーが決定されます。 SET("a","b","c","d") とフィールドが定義されたとします。 メンバーは以下の２進数の値を持ちます：

      SET member 10進数 ２進数値
      a 1 0001
      b 2 0010
      c 4 0100
      d 8 1000

      もしこのフィールドに 9 を与えた場合、これは２進数で 1001 ですから、 1 番目と 4 番目の SET メンバーである "a" と "d" が 選択され、結果、 "a,d" となります。

      1つ以上の SET 要素を含む値においては,あなたが値を挿入するとき,要素がどん な 順序で記載されているのかは重要ではありません. また,何回要素が与えられたのかは 重要ではありません. 後で値が検索されるとき, 値の中のそれぞれの要素は ただ一回だけ表れます。そのとき、テーブル作成時に与えられた順に要素は並びます。 例えば、フィールドが SET("a","b","c","d") と設定されていたなら、 "a,d", "d,a", "d,a,a,d,d" は検索されると "a,d" と なります。

      If you set a SET column to an unsupported value, the value will be ignored.

      SET 値は数値として代入されます。 NULL 値は非 NULL SET 値の前にソートされます。

      通常、LIKE か FIND_IN_SET() を使用して SET フィールド の SELECT を行います： 

      mysql> SELECT * FROM tbl_name WHERE set_col LIKE '%value%';
mysql> SELECT * FROM tbl_name WHERE FIND_IN_SET('value',set_col)>0;

      しかし、以下も動作します： 

      mysql> SELECT * FROM tbl_name WHERE set_col = 'val1,val2';
mysql> SELECT * FROM tbl_name WHERE set_col & 1;

      最初の文は完全一致するものを探します。 二つ目は第一番目のメンバーを含む値を探します。

      もし SET フィールドで設定可能なすべてのメンバーを知りたい場合： SHOW COLUMNS FROM table_name LIKE set_column_name とし、 ２番目にあらわされる SET 定義を分析します。

      6.2.4 正しいフィールド型の選択

      もっとも効率よく格納するには、全てにおいて一番正確な型を使用することです。 例えば、1-99999 の整数 には、MEDIUMINT UNSIGNED が最良の型です。

      良くある問題は、貨幣の値の正確な表現です。MySQL では DECIMAL 型を使用すべきです。これは文字列として格納し、正確さのロ スは発生しません。正確さが重要でない場合は DOUBLE 型でも十分良い です。

      高精度のため、常に BITINT に格納される固定小数点型に変換できます。 これは、全ての計算を整数で行なうようにし、結果だけを浮動小数点に変換して 戻します。

      6.2.5 他のデータベースエンジンのフィールド型の使用

      ほかのベンダーからSQLを簡単に書けれるように、 MySQL は以下の表に しめすフィールド型をサポートします。これらは、テーブルの定義を、 他のデータベースエンジンから MySQL に簡単に移行させてくれます：

      Other vendor type MySQL type
      BINARY(NUM) CHAR(NUM) BINARY
      CHAR VARYING(NUM) VARCHAR(NUM)
      FLOAT4 FLOAT
      FLOAT8 DOUBLE
      INT1 TINYINT
      INT2 SMALLINT
      INT3 MEDIUMINT
      INT4 INT
      INT8 BIGINT
      LONG VARBINARY MEDIUMBLOB
      LONG VARCHAR MEDIUMTEXT
      MIDDLEINT MEDIUMINT
      VARBINARY(NUM) VARCHAR(NUM) BINARY

      もし他のベンダーの型を使用してテーブルを作ろうとすると、 テーブル作成時のフィールドの型のマッピングが発生し、 DESCRIBE tbl_name 構文を発行します。 そして MySQL は、使用された型と等価な MySQL の型を用いて テーブルを構成したことを告げます。

      6.2.6 各フィールド型の所要容量

      MySQLがサポートする各フィールドタイプ毎の所要容量を、カテゴリ別に以下に 記述します。

      6.2.6.1 数値タイプの保存容量

      フィールドタイプ 所要容量
      TINYINT 1 byte
      SMALLINT 2 bytes
      MEDIUMINT 3 bytes
      INT 4 bytes
      INTEGER 4 bytes
      BIGINT 8 bytes
      FLOAT(X) X <= 24 の場合 4、25 <= X <= 53 の場合 8
      FLOAT 4 bytes
      DOUBLE 8 bytes
      DOUBLE PRECISION 8 bytes
      REAL 8 bytes
      DECIMAL(M,D) D > 0 の場合 M+2, D = 0 の場合 M+1 bytes (M < D の場合 D+2)
      NUMERIC(M,D) D > 0 の場合 M+2, D = 0 の場合 M+1 bytes (M < D の場合 D+2)

      6.2.6.2 日付と時間タイプの保存容量

      フィールドタイプ 所要容量
      DATE 3 bytes
      DATETIME 8 bytes
      TIMESTAMP 4 bytes
      TIME 3 bytes
      YEAR 1 byte

      6.2.6.3 文字列タイプの保存容量

      フィールドタイプ 所要容量
      CHAR(M) M bytes, 1 <= M <= 255
      VARCHAR(M) L+1 bytes, where L <= M and 1 <= M <= 255
      TINYBLOB, TINYTEXT L+1 bytes,where L < 2^8
      BLOB, TEXT L+2 bytes,where L < 2^16
      MEDIUMBLOB, MEDIUMTEXT L+3 bytes,where L < 2^24
      LONGBLOB, LONGTEXT L+4 bytes,where L < 2^32
      ENUM('value1','value2',...) 1 or 2 bytes, 列挙値の数に依存 (最大値は 65535 )
      SET('value1','value2',...) 1, 2, 3, 4 or 8 bytes, 要素の数に依存 (最大要素 64 )

      VARCHAR、BLOB、及びTEXT型は可変長型であり、所要容量は、フィ ールドのとり得る最大サイズというよりはむしろフィールド値の実際の長さに依存します (前の表でLと表しました)。 例えば、VARCHAR(10)フィールドは、最大10文字分の長さの文字列を保持すること が出来ます。実際の所要容量は、文字列の長さ(L)と、その長さを記録するための １バイトを加えます。文字列'abcd'においては、Lは４で、所要容量は５ バイトです。

      BLOBとTEXT型は、フィールド値の長さを記録するのに、１、２、３、又は ４バイト必要とし、型のとり得る最大の長さに依存します。 「6.2.3.2 BLOB と TEXT 型」節参照.

      テーブルが可変長フィールド型を含む場合、そのレコードフォーマットもまた可変長とな るでしょう。 テーブルが作成された時、MySQLは確かな条件の下、フィールドを可変長タイプ から固定長タイプへ変更し、副作用を起こすことに注意して下さい。 「6.5.3.1 暗黙のフィールド定義変更」節参照.

      ENUMオブジェクトのサイズは、異なる列挙値の数によって決められます。 列挙する数が255以内では、１バイトが使用されます。 列挙する数が65535以内では、２バイトが使用されます。 「6.2.3.3 ENUM 型」節参照.

      SETオブジェクトのサイズは、異なる要素の数によって決められます。 組のサイズをNとすると、オブジェクトは(N+7)/8バイトを占有し、 １、２、３、４又は８バイトに切上げられます。 １つのSETは、最大６４要素を持つことができます。 「6.2.3.4 SET 型」節参照.

      6.3 SELECT と WHERE 節で使用する関数

      SQL ステートメント中の select_expression または where_definition は後述の関数を使用した任意の式からなります。

      演算と関数を式の中で呼ぶ時、本ドキュメントに示しているもの以外の、 NULL を含む式は常に NULL 値を生成します

      注意: 関数名とそれに続く語句の間には、空白はありません。 これは関数の呼び出しと、関数と同名のテーブル(かフィールド)の参照を、 MySQL パーサが区別するのを助けます。

      mysqld に --ansi をつけて起動するか、 CLIENT_IGNORE_SPACE を mysql_connect() に使用すれば、 MySQL が関数名の後の空白を許すようになりますが、その場合、すべて の関数名が予約語になります。 「1.7.2 MySQLをANSIモードで実行する」節参照。

      次の例では、mysql プログラムの出力は短くなっています。つまり: 

      mysql> SELECT MOD(29,9);
1 rows in set (0.00 sec)

+-----------+
| mod(29,9) |
+-----------+
|         2 |
+-----------+

      これは次に変換されています: 

      mysql> SELECT MOD(29,9);
        -> 2

      6.3.1 Non-Type-Specific Operators and Functions

      The maximum size of a row in a MyISAM table is 65534 bytes. Each BLOB and TEXT column accounts for only 5-9 bytes towards this size.

      6.3.1.1 Parentheses

      ( ... )

      Use parentheses to force the order of evaluation in an expression. For example: 

      mysql> SELECT 1+2*3;
        -> 7
mysql> SELECT (1+2)*3;
        -> 9

      6.3.1.2 比較演算子

      1 (TRUE), 0 (FALSE) または NULL を返します。 これらの関数は数値と文字列の両方で働きます。 必要ならば、文字は自動的に数字に変換され、数字は文字に変換されます。 (Perlがおこなっているみたいに)

      MySQL は以下の規則で比較を行います：

      • どちらかまたは両方の引数が NULL の場合は、比較結果は NULL です。<=> 演算子を除きます。
      • 比較操作の両方の引数が文字列の場合、文字列として比較されます。
      • 両方の引数が整数の場合、整数として比較されます。
      • 16進数の値は、もし数値と比較されないのであれば、文字列として扱われます。
      • 引数の一方が TIMESTAMP または DATETIME フィールドで、他の引数が 定数の場合は、定数は比較前に timestamp に変換されます。これはより ODBC フレンドリにするためです。
      • 他の場合は全て浮動小数点(real)として比較されます。

      文字列の比較は、ケースに依存せず、標準のキャラクターセットに従って 行われます。(ISO-8859-1 Latin1 がデフォルトです。これは English です)

      以下は、比較のために文字が数値へ変換されている例です： 

      mysql> SELECT 1 > '6x';
         -> 0
mysql> SELECT 7 > '6x';
         -> 1
mysql> SELECT 0 > 'x6';
         -> 0
mysql> SELECT 0 = 'x6';
         -> 1
      =
      等しい: 
      mysql> SELECT 1 = 0;
        -> 0
mysql> SELECT '0' = 0;
        -> 1
mysql> SELECT '0.0' = 0;
        -> 1
mysql> SELECT '0.01' = 0;
        -> 0
mysql> SELECT '.01' = 0.01;
        -> 1
      <>
      !=
      等しくない: 
      mysql> SELECT '.01' <> '0.01';
        -> 1
mysql> SELECT .01 <> '0.01';
        -> 0
mysql> SELECT 'zapp' <> 'zappp';
        -> 1
      <=
      より小さいか等しい: 
      mysql> SELECT 0.1 <= 2;
        -> 1
      <
      より小さい: 
      mysql> SELECT 2 < 2;
        -> 0
      >=
      より大きいか等しい: 
      mysql> SELECT 2 >= 2;
        -> 1
      >
      より大きい: 
      mysql> SELECT 2 > 2;
        -> 0
      <=>
      等しい(NULL 安全): 
      mysql> SELECT 1 <=> 1, NULL <=> NULL, 1 <=> NULL;
        -> 1 1 0
      IS NULL
      IS NOT NULL
      値が NULL とであるかどうかのテスト: 
      mysql> SELECT 1 IS NULL, 0 IS NULL, NULL IS NULL;
        -> 0 0 1
mysql> SELECT 1 IS NOT NULL, 0 IS NOT NULL, NULL IS NOT NULL;
        -> 1 1 0
      To be able to work good with other programs, MySQL supports the following extra features when using IS NULL:
      • You can find the last inserted row with: 
        SELECT * FROM tbl_name WHERE auto_col IS NULL
        This can be disabled by setting SQL_AUTO_IS_NULL=0. 「5.5.6 SET 構文」節参照.
      • For NOT NULL DATE and DATETIME columns you can find the special date 0000-00-00 by using: 
        SELECT * FROM tbl_name WHERE date_column IS NULL
        This is needed to get some ODBC applications to work (as ODBC doesn't support a 0000-00-00 date)
      expr BETWEEN min AND max
      もし expr が min 以上、 max 以下なら 1を返します。 そうでないなら 0 を返します。 これは 全ての引数が同じ型ならば、(min <= expr AND expr <= max) と同じです。 Otherwise type conversion takes place, according to the rules above, but applied to all the three arguments. Note that before 4.0.5 arguments were converted to the type of expr instead. 
      mysql> SELECT 1 BETWEEN 2 AND 3;
        -> 0
mysql> SELECT 'b' BETWEEN 'a' AND 'c';
        -> 1
mysql> SELECT 2 BETWEEN 2 AND '3';
        -> 1
mysql> SELECT 2 BETWEEN 2 AND 'x-3';
        -> 0
      expr NOT BETWEEN min AND max
      Same as NOT (expr BETWEEN min AND max).
      expr IN (value,...)
      もし expr が IN リストにある値のどれかならば、1 を返します 。 そうでなければ 0 を返します。 もし全ての値が定数なら、すべての値が expr の型に従って評価され、 ソートされます。この検索にはバイナリサーチが使用されます。 これは IN リストに定数を与えた場合、IN が速くなることを意味します。 もし expr がケース依存の文字式なら、ケース依存のやり方で比較されます。 
      mysql> SELECT 2 IN (0,3,5,'wefwf');
        -> 0
mysql> SELECT 'wefwf' IN (0,3,5,'wefwf');
        -> 1
      From 4.1 (in line with the SQL-99 standard), IN returns NULL not only if the expression on the left hand side is NULL, but also if no match is found in the list and one of the expressions in the list is NULL.
      expr NOT IN (value,...)
      NOT (expr IN (value,...)) と同じ。
      ISNULL(expr)
      expr が NULL なら 1 を、そうでなければ 0 を返します 
      mysql> SELECT ISNULL(1+1);
        -> 0
mysql> SELECT ISNULL(1/0);
        -> 1
      NULL の値を = を使用して比較した場合は常に偽(false) となることに 注意してください！
      COALESCE(list)
      list 中の、最初に現れた 非-NULL 要素を返します。 
      mysql> SELECT COALESCE(NULL,1);
        -> 1
mysql> SELECT COALESCE(NULL,NULL,NULL);
        -> NULL
      INTERVAL(N,N1,N2,N3,...)
      もし N < N1 なら 0 を返します。 もし N < N2 なら 1 を返します。 全ての引数は整数として扱われます。 これは N1 < N2 < N3 < ... < Nnを正しく動作さ せるために 必要なことです。これはバイナリ検索が使用されます(速いです) 
      mysql> SELECT INTERVAL(23, 1, 15, 17, 30, 44, 200);
        -> 3
mysql> SELECT INTERVAL(10, 1, 10, 100, 1000);
        -> 2
mysql> SELECT INTERVAL(22, 23, 30, 44, 200);
        -> 0

      If you are comparing case-insensitive strings with any of the standard operators (=, <>..., but not LIKE) trailing whitespace (spaces, tabs and newlines) will be ignored. 

      mysql> SELECT "a" ="A \n";
        -> 1

      6.3.1.3 論理演算

      全ての論理関数は 1 (TRUE) か 0 (FALSE) か NULL を返します。 (unknown は多くの場合 FALSE と同じです)：

      NOT
      !
      論理否定。引数が 0 なら 1 を返し、そうでなければ 0 を返しま す。 例外: NOT NULL は NULL を返します: 
      mysql> SELECT NOT 1;
        -> 0
mysql> SELECT NOT NULL;
        -> NULL
mysql> SELECT ! (1+1);
        -> 0
mysql> SELECT ! 1+1;
        -> 1
      最後の例は 1 を返します。なぜなら、式の評価が (!1)+1 と同じだからです。
      AND
      &&
      論理積。 全ての引数が 非0 または 非NULL であれば 1 を返します。 引数のどれかが 0 ならば 0 を返します。 それ以外は NULL を返します。 
      mysql> SELECT 1 && 1;
        -> 1
mysql> SELECT 1 && 0;
        -> 0
mysql> SELECT 1 && NULL;
        -> NULL
mysql> SELECT 0 && NULL;
        -> 0
mysql> SELECT NULL && 0;
        -> 0
      Please note that MySQL versions prior to 4.0.5 stop evaluation when a NULL is encountered, rather than continuing the process to check for possible 0s. This means that in these versions, SELECT (NULL AND 0) returns NULL instead of 0. In 4.0.5 the code has been re-engineered so that the result will always be as prescribed by ANSI while still using the optimisation wherever possible.
      OR
      ||
      論理和。 Evaluates to 1 if any operand is non-zero, to NULL if any operand is NULL, otherwise 0 is returned. 
      mysql> SELECT 1 || 1;
        -> 1
mysql> SELECT 1 || 0;
        -> 1
mysql> SELECT 0 || 0;
        -> 0
mysql> SELECT 0 || NULL;
        -> NULL
mysql> SELECT 1 || NULL;
        -> 1
      XOR
      Logical XOR. Returns NULL if either operand is NULL. For non-NULL operands, evaluates to 1 if an odd number of operands is non-zero, otherwise 0 is returned. 
      mysql> SELECT 1 XOR 1;
        -> 0
mysql> SELECT 1 XOR 0;
        -> 1
mysql> SELECT 1 XOR NULL;
        -> NULL
mysql> SELECT 1 XOR 1 XOR 1;
        -> 1
      a XOR b is mathematically equal to (a AND (NOT b)) OR ((NOT a) and b). XOR was added in version 4.0.2.

      6.3.1.4 フロー制御関数

      IFNULL(expr1,expr2)
      expr1 が NULL でない場合は expr1 を、そうでなければ expr2 を返します。 IFNULL() はどの文脈で使用されたかにより数値か文字を返します: 
      mysql> SELECT IFNULL(1,0);
        -> 1
mysql> SELECT IFNULL(NULL,10);
        -> 10
mysql> SELECT IFNULL(1/0,10);
        -> 10
mysql> SELECT IFNULL(1/0,'yes');
        -> 'yes'
      In 4.0.6 and above the default result value of IFNULL(expr1,expr2) is the more 'general' of the two expressions, in the order STRING, REAL or INTEGER.The difference to earlier MySQL versions are mostly notable when you create a table based on expressions or MySQL has to internally store a value from IFNULL() in a temporary table. 
      CREATE TABLE foo SELECT IFNULL(1,"test") as test;
      In MySQL 4.0.6 the type for column 'test' is CHAR(4) while in earlier versions you would get BIGINT.
      NULLIF(expr1,expr2)
      expr1 = expr2 が真なら、NULL を返し、そうでなければ expr1 を返します。 これは CASE WHEN x = y THEN NULL ELSE x END と同じです: 
      mysql> SELECT NULLIF(1,1);
        -> NULL
mysql> SELECT NULLIF(1,2);
        -> 1
      注意: 引数が等しくない場合、expr1 は MySQL 内部では2回評価されます。
      IF(expr1,expr2,expr3)
      expr1 が真 (expr1 <> 0 and expr1 <> NULL) の場合 expr2 を返し、そうでなければ expr3 を返します。 IF() はどの文脈で使用されたかにより数値か文字を返します: 
      mysql> SELECT IF(1>2,2,3);
        -> 3
mysql> SELECT IF(1<2,'yes','no');
        -> 'yes'
mysql> SELECT IF(STRCMP('test','test1'),'no','yes');
        -> 'no'
      If expr2 or expr3 is explicitely NULL then the result type of the IF() function is the type of the not NULL column. (This behaviour is new in MySQL 4.0.3). expr1 は INTEGER として評価されます。これは浮動小数点を使用する 場合、比較演算も使用すべきであることを意味します: 
      mysql> SELECT IF(0.1,1,0);
        -> 0
mysql> SELECT IF(0.1<>0,1,0);
        -> 1
      上の最初の例では、 IF(0.1) は 0 を返します。なぜなら 0.1 は 整数値として変換され IF(0) になり、それをもとにしたテスト結果が 返るからです。 これはあなたの期待に添わないかもしれません。 二番目の場合、 比較は、元の浮動小数点値が非ゼロかどうかテストします。 比較結果は整数として使用されます。 IF() のデフォルトの戻り値型(一時テーブルに格納される時に問題となり ます)は MySQL バージョン 3.23 では次のように計算されます:
      Expression Return value
      expr2 または expr3 が文字列を返す 文字列
      expr2 または expr3 が浮動小数点値を返す 浮動小数点
      expr2 または expr3 が整数を返す 整数
      If expr2 and expr3 are strings, then the result is case-insensitive if both strings are case-insensitive. (Starting from 3.23.51)
      CASE value WHEN [compare-value] THEN result [WHEN [compare-value] THEN result ...] [ELSE result] END
      CASE WHEN [condition] THEN result [WHEN [condition] THEN result ...] [ELSE result] END
      最初の式は value=compare-value ならば result を返します。 二つ目の式では、最初の条件[condition] が真ならば、 result を返します。 もしマッチする result の値がなければ、 ELSE 以下の result が返ります。 もし ELSE 部分がなければ、 NULL が返ります: 
      mysql> SELECT CASE 1 WHEN 1 THEN "one"
           WHEN 2 THEN "two" ELSE "more" END;
       -> "one"
mysql> SELECT CASE WHEN 1>0 THEN "true" ELSE "false" END;
       -> "true"
mysql> SELECT CASE BINARY "B" WHEN "a" THEN 1 WHEN "b" THEN 2 END;
       -> NULL

      戻り値の型(INTEGER, DOUBLE, STRING)は最初に返される値 (最初の THEN の後の式)の型と同じです。

      6.3.2 文字列関数

      サーバー側のパラメター max_allowed_packet よりも結果の長さが大きい場合、 文字列関数は NULL を返します。 「5.5.2 サーバーパラメーターのチューニング」節参照.

      文字の位置を扱う関数においては、一番最初の位置は数字の 1 です。

      ASCII(str)
      str の左端の文字の ASCII コード値を返します。 str が空文字の場合は 0 を返します。 str が NULL の場合は NULL を返します: 
      mysql> SELECT ASCII('2');
        -> 50
mysql> SELECT ASCII(2);
        -> 50
mysql> SELECT ASCII('dx');
        -> 100
      See also the ORD() function.
      ORD(str)
      文字列 str の左端の文字がマルチバイト文字の場合、文字のASCII コード値を次 の形式で返すことにより、マルチバイト文字のコードを返します: ((first byte ASCII code)*256+(second byte ASCII code))[*256+third byte ASCII code...]. 左端の文字がマルチバイト文字でない場合は、ASCII() 関数と同じ値を返 します: 
      mysql> SELECT ORD('2');
        -> 50
      CONV(N,from_base,to_base)
      数字を、進数の違う数字に変換します。 数 N を from_base 進数から to_base 進数に 変換した場合の、文字表現を返します。 もし引数が NULL なら NULL を返します。 引数 N は整数として解釈されますが、整数か文字列で指定します。 最小の進数は 2 で、最大は 36 です。 to_base が負数なら、N は符号付きの数になります。 CONV は 64-bit 精度で動作します: 
      mysql> SELECT CONV("a",16,2);
        -> '1010'
mysql> SELECT CONV("6E",18,8);
        -> '172'
mysql> SELECT CONV(-17,10,-18);
        -> '-H'
mysql> SELECT CONV(10+"10"+'10'+0xa,10,10);
        -> '40'
      BIN(N)
      N を二進数にした値を返します。N は longlong 数値です。 これは CONV(N,10,2) と同じです。 N が NULL なら NULL を返します: 
      mysql> SELECT BIN(12);
        -> '1100'
      OCT(N)
      N の8進数値を表す文字列を返します。N は longlong 数値です。 これは CONV(N,10,8) と同じです。N が NULL の場合は NULL を返します: 
      mysql> SELECT OCT(12);
        -> '14'
      HEX(N_or_S)
      If N_OR_S is a number, returns a string representation of the hexadecimal value of N, ここで N は longlong(BIGINT) 数値です。これは CONV(N,10,16) と同じです。 If N_OR_S is a string, returns a hexadecimal string of N_OR_S where each character in N_OR_S is converted to 2 hexadecimal digits. This is the invers of the 0xff strings. 
      mysql> SELECT HEX(255);
        -> 'FF'
mysql> SELECT HEX("abc");
        -> 616263
mysql> SELECT 0x616263;
        -> "abc"
      CHAR(N,...)
      引数の ASCII コード値によって与えられた文字からなる文字列を返します。 NULL は飛ばされます: 
      mysql> SELECT CHAR(77,121,83,81,'76');
        -> 'MySQL'
mysql> SELECT CHAR(77,77.3,'77.3');
        -> 'MMM'
      CONCAT(str1,str2,...)
      引数を結合した結果を返します。引数が NULL なら NULL を返します. 2個以上の引数を必要とします。 数値の引数は等価の文字列形式に変換されます: 
      mysql> SELECT CONCAT('My', 'S', 'QL');
        -> 'MySQL'
mysql> SELECT CONCAT('My', NULL, 'QL');
        -> NULL
mysql> SELECT CONCAT(14.3);
        -> '14.3'
      CONCAT_WS(separator, str1, str2,...)
      CONCAT_WS() は区切り文字つき CONCAT (CONCAT With Separator) を意味 し、CONCAT() の特殊な形式です。最初の引数は、残りの引数の区切り文字 です。区切り文字は残りの引数と同じような文字列です。区切り文字が NULL の場合、結果は NULL になります。関数は区切り文字より後 の NULL と空文字列を飛ばします。区切り文字は結合される文字列の間に 追加されます: 
      mysql> SELECT CONCAT_WS(",","First name","Second name","Last Name");
       -> 'First name,Second name,Last Name'
mysql> SELECT CONCAT_WS(",","First name",NULL,"Last Name");
       -> 'First name,Last Name'
      LENGTH(str)
      OCTET_LENGTH(str)
      CHAR_LENGTH(str)
      CHARACTER_LENGTH(str)
      文字列 str の長さ: 
      mysql> SELECT LENGTH('text');
        -> 4
mysql> SELECT OCTET_LENGTH('text');
        -> 4
      注意: CHAR_LENGTH() と CHARACTER_LENGTH() については、マルチバイト文字は一度だけしかカウントされません。
      BIT_LENGTH(str)
      Returns the length of the string str in bits: 
      mysql> SELECT BIT_LENGTH('text');
        -> 32
      LOCATE(substr,str)
      POSITION(substr IN str)
      str 内にある substr 文字列の位置を返します。最初の位置は 1 です。 str 内に substr がない時は 0 を返します: 
      mysql> SELECT LOCATE('bar', 'foobarbar');
        -> 4
mysql> SELECT LOCATE('xbar', 'foobar');
        -> 0
      この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string.
      LOCATE(substr,str,pos)
      文字列 str 中に最初に顕れた substr 文字の位置を返します。 pos は検索を開始する位置です。 str に substr がなければ 0 を返します: 
      mysql> SELECT LOCATE('bar', 'foobarbar',5);
        -> 7
      この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string.
      INSTR(str,substr)
      文字列 str 内の最初の文字列 substr の位置を返します。 これは引数が入れ替わっていることをのぞいて、 2つの引数を与えた LOCATE と同じです: 
      mysql> SELECT INSTR('foobarbar', 'bar');
        -> 4
mysql> SELECT INSTR('xbar', 'foobar');
        -> 0
      この関数はマルチバイトでも安全です。 In MySQL 3.23 this function is case sensitive, while in 4.0 it's only case-sensitive if either argument is a binary string.
      LPAD(str,len,padstr)
      str の長さが len になるまで文字列 str の始めに padstr を埋めます。 str が len よりも長い場合は、len 文字に短くされます。 
      mysql> SELECT LPAD('hi',4,'??');
        -> '??hi'
      RPAD(str,len,padstr)
      str の長さが len になるまで文字列 str の終わりに padstr を埋めます。 str が len よりも長い場合は、len 文字に短くされます。 
      mysql> SELECT RPAD('hi',5,'?');
        -> 'hi???'
      LEFT(str,len)
      文字列 str の最初から len 個の文字を得ます: 
      mysql> SELECT LEFT('foobarbar', 5);
        -> 'fooba'
      この関数はマルチバイトでも安全です。
      RIGHT(str,len)
      文字列 str の最後から len 個の文字を得ます: 
      mysql> SELECT RIGHT('foobarbar', 4);
        -> 'rbar'
      この関数はマルチバイトでも安全です。
      SUBSTRING(str,pos,len)
      SUBSTRING(str FROM pos FOR len)
      MID(str,pos,len)
      str の pos 位置から len 文字数分の文字列を返します。 FROM の違いは ANSI SQL 92 構文です: 
      mysql> SELECT SUBSTRING('Quadratically',5,6);
        -> 'ratica'
      この関数はマルチバイトでも安全です。
      SUBSTRING(str,pos)
      SUBSTRING(str FROM pos)
      文字列 str の 位置 pos 以降の文字を返します: 
      mysql> SELECT SUBSTRING('Quadratically',5);
        -> 'ratically'
mysql> SELECT SUBSTRING('foobarbar' FROM 4);
        -> 'barbar'
      この関数はマルチバイトでも安全です。
      SUBSTRING_INDEX(str,delim,count)
      str から、区切り文字 delim が count 個現れた位置から前の 文字列を返します。count が正の場合は文字列は左から検索され、 count が負の場合は文字列は右から検索されます: 
      mysql> SELECT SUBSTRING_INDEX('www.mysql.com', '.', 2);
        -> 'www.mysql'
mysql> SELECT SUBSTRING_INDEX('www.mysql.com', '.', -2);
        -> 'mysql.com'
      この関数はマルチバイトでも安全です。
      LTRIM(str)
      文字列 str の最初から空白文字を削除します: 
      mysql> SELECT LTRIM('  barbar');
        -> 'barbar'
      RTRIM(str)
      文字列 str の最後から空白文字を削除します: 
      mysql> SELECT RTRIM('barbar   ');
        -> 'barbar'
      この関数はマルチバイトでも安全です。
      TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)
      全ての remstr プレフィックスまたはサフィックスを str から削除した 文字列を返します。BOTH, LEADING そして TRAILING が 使用されない場合、BOTH が適用されます。remstr が与えられないと、 空白が削除されます: 
      mysql> SELECT TRIM('  bar   ');
        -> 'bar'
mysql> SELECT TRIM(LEADING 'x' FROM 'xxxbarxxx');
        -> 'barxxx'
mysql> SELECT TRIM(BOTH 'x' FROM 'xxxbarxxx');
        -> 'bar'
mysql> SELECT TRIM(TRAILING 'xyz' FROM 'barxxyz');
        -> 'barx'
      This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string.
      SOUNDEX(str)
      str からの soundex 文字列を返します。発音が``大体同じ''２つの文字列 は同じ soundex 文字列を持ちます。``標準の'' soundex 文字列は4文字長ですが、 SOUNDEX() 関数は任意の長さの文字列を返します。SUBSTRING() を 結果に使用して、``標準の'' soundex 文字列を得ることができます。与えられた 文字列中の非アルファベット文字は無視されます。A-Z の半以外のすべての国際的 なアルファベット文字は母音とみなされます: 
      mysql> SELECT SOUNDEX('Hello');
        -> 'H400'
mysql> SELECT SOUNDEX('Quadratically');
        -> 'Q36324'
      SPACE(N)
      N 個の空白文字を返します: 
      mysql> SELECT SPACE(6);
        -> '      '
      REPLACE(str,from_str,to_str)
      文字列 str 内の全ての文字列 from_str を to_str に 置き換えます: 
      mysql> SELECT REPLACE('www.mysql.com', 'w', 'Ww');
        -> 'WwWwWw.mysql.com'
      この関数はマルチバイトでも安全です。
      REPEAT(str,count)
      str を count 回繰り返します。count <= 0 の場合は 空の文字列を返します。str または count が NULL または、LENGTH(str)*count > max_allowed_packet の場合は NULL を返します: 
      mysql> SELECT REPEAT('MySQL', 3);
        -> 'MySQLMySQLMySQL'
      REVERSE(str)
      文字列 str を反転します: 
      mysql> SELECT REVERSE('abc');
        -> 'cba'
      この関数はマルチバイトでも安全です。
      INSERT(str,pos,len,newstr)
      str 中の pos 位置から len 長の文字列を newstr で置き換えます。str 内の最初の位置は1です: 
      mysql> SELECT INSERT('Quadratic', 3, 4, 'What');
        -> 'QuWhattic'
      この関数はマルチバイトでも安全です。
      ELT(N,str1,str2,str3,...)
      N = 1 なら str1 を、N = 2 なら str2 を 返します。 N が 1 より小さい場合、または引数の数より大きい場合は NULL が返されます。 ELT() は FIELD() の逆です: 
      mysql> SELECT ELT(1, 'ej', 'Heja', 'hej', 'foo');
        -> 'ej'
mysql> SELECT ELT(4, 'ej', 'Heja', 'hej', 'foo');
        -> 'foo'
      FIELD(str,str1,str2,str3,...)
      str1, str2, str3, ... リスト内の str のインデ ックスを 返します。str が見つからなければ 0 を返します。 FIELD() は ELT() の逆です: 
      mysql> SELECT FIELD('ej', 'Hej', 'ej', 'Heja', 'hej', 'foo');
        -> 2
mysql> SELECT FIELD('fo', 'Hej', 'ej', 'Heja', 'hej', 'foo');
        -> 0
      FIND_IN_SET(str,strlist)
      str が strlist 中にあれば、値 1 から N を返します。 strlist は、それぞれの異なる値が ',' で分割された文字列です。最初の 引数が定数文字列で２番目が SET 型のフィールドの場合FIND_IN_SET は ビット演算を使用して最適化されます！ strlist が空文字なら 0 を返します。 どちらかの引数が NULL なら NULL を返します. この関数は最初の引数が ',' を含んだ場合、うまく動かないでしょう: 
      mysql> SELECT FIND_IN_SET('b','a,b,c,d');
        -> 2
      MAKE_SET(bits,str1,str2,...)
      bits に指定されたビットに対応する文字列のセットを返します。 (文字列が複数の場合、 `,' で区切られます) str1 が ビット 0 に対応し、str2 が ビット 1 に対応し、 str3 が ビット 2 に対応し... となります。 str1, str2, ... 中に含まれている NULL 文字は 結果には追加されません: 
      mysql> SELECT MAKE_SET(1,'a','b','c');
        -> 'a'
mysql> SELECT MAKE_SET(1 | 4,'hello','nice','world');
        -> 'hello,world'
mysql> SELECT MAKE_SET(0,'a','b','c');
        -> ''
      EXPORT_SET(bits,on,off,[separator,[number_of_bits]])
      'bits' に与えられた数値に対し、 全てのセットされているビットを 'on' で指定された文字で表し、 リセットされているビットを 'off' で指定された文字で表した文字列を返します。 それぞれの文字は 'separator' (デフォルト',') で示された文字で区切られ、 'number_of_bits' (default 64) に与えられた桁数だけのビットを表示します: 
      mysql> SELECT EXPORT_SET(5,'Y','N',',',4)
        -> Y,N,Y,N
      LCASE(str)
      LOWER(str)
      str を現在のキャラクターセットマッピング (デフォルト ISO-8859-1 Latin1) にしたがって小文字に変換します: 
      mysql> SELECT LCASE('QUADRATICALLY');
        -> 'quadratically'
      This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string.
      UCASE(str)
      UPPER(str)
      str を現在のキャラクターセットマッピング (デフォルト ISO-8859-1 Latin1) にしたがって大文字に変換します: 
      mysql> SELECT UCASE('Hej');
        -> 'HEJ'
      This function is multi-byte safe. In MySQL 3.23 this function is case insensitive, while in 4.0 it's only case insensitive if either argument is a binary string.
      LOAD_FILE(file_name)
      ファイルを読み込み、ファイルの中身を文字として返します。 ファイルは サーバー上になくてはならず、ファイルをフルパスで指定しなければなりません。 そして、 FILE 権限がなければなりません。 ファイルは全員に 読み込み可能でなければならず、そして、 max_allowed_packet より 小さいサイズでなければなりません。 このうちどれかの理由で、もしファイルが存在しないか読み込めない場合、 この関数は NULL を返します: 
      mysql> UPDATE tbl_name
           SET blob_column=LOAD_FILE("/tmp/picture")
           WHERE id=1;
      MySQL 3.23 を使用していない場合、あなたのアプリケーション内部でファ イルを読み込んで、ファイル情報でデータベースを更新するための INSERT ステートメントを生成する必要があります。これを行なう一つの方 法は、MySQL++ ライブラリを使用する場合、 http://www.mysql.com/documentation/mysql++/mysql++-examples.html で 見つけられます。
      QUOTE(str)
      Quotes a string to produce a result that can be used as a properly-escaped data value in a SQL statement. The string is returned surrounded by single quotes and with each instance of single quote (`''), backslash (`\'), ASCII NUL, and Control-Z preceded by a backslash. If the argument is NULL, the return value is the word ``NULL'' without surrounding single quotes. 
      mysql> SELECT QUOTE("Don't");
        -> 'Don\'t!'
mysql> SELECT QUOTE(NULL);
        -> NULL

      6.3.2.1 String Comparison Functions

      MySQL は必要とあらば数値を文字列に変換します。 逆も同様に行います： 

      mysql> SELECT 1+"1";
        -> 2
mysql> SELECT CONCAT(2,' test');
        -> '2 test'

      明示的に数値を文字列に変換したければ、CONCAT() に引数として渡して下 さい。

      文字列関数は引数としてバイナリ文字列が与えられると、結果の文字列もバイナリ 文字列になります。文字列に変換された数値はバイナリ文字列とみなされます。こ れは比較にだけ影響します。

      通常、比較される表現がケース依存でない場合、比較はケース非依存で行われます。

      expr LIKE pat [ESCAPE 'escape-char']
      SQL の簡単な正規表現比較です。1 (TRUE) または 0 (FALSE) を返します 。 LIKE には2つのワイルドカードがあります:
      Char Description
      % 任意の数の文字(0文字も含む)に適合します。
      _ 厳密に1つの文字に適合します。 
      mysql> SELECT 'David!' LIKE 'David_';
        -> 1
mysql> SELECT 'David!' LIKE '%D%v%';
        -> 1
      ワイルドカード文字のテストをするためには、エスケープ文字より先行しておこなって ください。 ESCAPE を指定しない場合は、文字 `\' が使われます:
      String Description
      \% 1つの % に適合します。
      \_ 1つの _ に適合します。 
      mysql> SELECT 'David!' LIKE 'David\_';
        -> 0
mysql> SELECT 'David_' LIKE 'David\_';
        -> 1
      違うエスケープ文字を指定するには、 ESCAPE 節を使用します: 
      mysql> SELECT 'David_' LIKE 'David|_' ESCAPE '|';
        -> 1
      次の２つのステートメントは、オペランドの一つがバイナリ文字列でなければ、文 字列比較がケース非依存であることを示しています: 
      mysql> SELECT 'abc' LIKE 'ABC';
        -> 1
mysql> SELECT 'abc' LIKE BINARY 'ABC';
        -> 0
      LIKE は数値表現でも許されます！ (これは MySQL の、ANSI SQL LIKE に対する拡張です) 注意： MySQL は文字列中に C のエスケープ文字を使用しているので(e.g., `\n'), LIKE の指定文字列として使用するには `\' を 二倍しなくてはなりません。 例えば、 `\n' を探すには、`\\n' と 記述します。 `\' を探すには、 `\\\\' (バックスラッシュは、 一つはパーサーに取り除かれ、パターンマッチが行われる際にもうひとつ 取り除かれ、一致を探すために残った一つのバックスラッシュが使用されます)
      expr NOT LIKE pat [ESCAPE 'escape-char']
      NOT (expr LIKE pat [ESCAPE 'escape-char']) と同じ
      expr SOUNDS LIKE expr
      Same as SOUNDEX(expr)=SOUNDEX(expr) (available only in version 4.1 or later).
      expr REGEXP pat
      expr RLIKE pat
      パターン pat に対し、文字式 expr のパターンマッチを行います。 パターン pat は正規表現の拡張が使用できます。 「G MySQL の正規表現」節参照. もし expr が pat にマッチするなら 1 を返し、 でなければ 0 を返します。 RLIKE は REGEXP と同義で、mSQL 互換を提供します。 注意: MySQL は C エスケープ構文を文字中に使用しており(\n)、 REGEXP 中で使用される '\' 文字はすべて、二重に書かなければ なりません。 MySQL 3.23.4 REGEXP は、普通の文字 (not binary) はケース非依存で す: 
      mysql> SELECT 'Monty!' REGEXP 'm%y%%';
        -> 0
mysql> SELECT 'Monty!' REGEXP '.*';
        -> 1
mysql> SELECT 'new*\n*line' REGEXP 'new\\*.\\*line';
        -> 1
mysql> SELECT "a" REGEXP "A", "a" REGEXP BINARY "A";
        -> 1  0
mysql> SELECT "a" REGEXP "^[a-d]";
        -> 1
      REGEXP and RLIKE は、文字の型を決定する場合、 カレントのキャラクターセットを使用します。 (ISO-8859-1 Latin1 がデフォルト)
      expr NOT REGEXP pat
      expr NOT RLIKE pat
      NOT (expr REGEXP pat) と同じ.
      STRCMP(expr1,expr2)
      STRCMP() 文字列が同じなら 0 を返します。そうでなければ、最初の引数がソート順で小 さければ -1 を返します。そうでなければ 1 を返します: 
      mysql> SELECT STRCMP('text', 'text2');
        -> -1
mysql> SELECT STRCMP('text2', 'text');
        -> 1
mysql> SELECT STRCMP('text', 'text');
        -> 0
      MATCH (col1,col2,...) AGAINST (expr)
      MATCH ... AGAINST() は全文検索に使用され、妥当性を返します。フィー ルド (col1,col2,...) 内のテキストとクエリ expr との間の類似 点を評価します。妥当性は正の浮動小数点数です。妥当性 0 は類似点なしを意味 します。MATCH ... AGAINST() が動作するためには、最初に FULLTEXT インデックスが作成する必要があります。 「6.5.3 CREATE TABLE 構文」節参照。 MATCH ... AGAINST() は MySQL 3.23.23 以上のバージョンで有 効です。 IN BOOLEAN MODE extension was added in version 4.0.1. 詳細と使用例は 「6.8 MySQL Full-text Search」節.

      6.3.2.2 Case-Sensitivity

      BINARY
      BINARY 演算子は、これ以降に続く文字をバイナリにキャストします。 これはたとえフィールドが BINARY や BLOB 定義でなくても、 ケース依存でフィールドを比較することが出来る簡単な方法です: 
      mysql> SELECT "a" = "A";
        -> 1
mysql> SELECT BINARY "a" = "A";
        -> 0
      BINARY string is a shorthand for CAST(string AS BINARY). 「6.3.5 Cast Functions」節参照. BINARY は MySQL 3.23.0 で登場しました。 注意: いくつかの文脈では、インデックスされたフィールドを BINARY に キャストした時、MySQL はインデックスを効率よく使用できません。

      BLOB をケース非依存で比較したい場合、比較を行なう前に BLOB を常に大文字に 変換します: 

      SELECT 'A' LIKE UPPER(blob_col) FROM table_name;

      より柔軟に文字列を比較するために、我々は間もなく異なる文字セット間のキャス トを導入する予定です。

      6.3.3 Numeric Functions

      6.3.3.1 算術演算

      普通の算術演算が有効です。 -, +, * は、二つの引数が正数ならば BIGINT (64bit精度) で計算されることに注意してください！ If one of the argument is an unsigned integer, and the other argument is also an integer, the result will be an unsigned integer. 「6.3.5 Cast Functions」節参照.

      +
      足し算: 
      mysql> SELECT 3+5;
        -> 8
      -
      引き算: 
      mysql> SELECT 3-5;
        -> -2
      *
      掛け算: 
      mysql> SELECT 3*5;
        -> 15
mysql> SELECT 18014398509481984*18014398509481984.0;
        -> 324518553658426726783156020576256.0
mysql> SELECT 18014398509481984*18014398509481984;
        -> 0
      最後の式の結果は不当です。なぜなら結果は BIGINT の 64 ビットを超えた整数だからです。
      /
      割り算: 
      mysql> SELECT 3/5;
        -> 0.60
      0 で割った場合、NULL になります。 
      mysql> SELECT 102/(1-1);
        -> NULL
      演算結果が整数になる場合にだけ、 BIGINT を用いて割り算は計算されます。

      6.3.3.2 数学関数

      すべての数学関数はエラーの場合 NULL を返します。

      -
      符号。引数の符号を変更します: 
      mysql> SELECT - 2;
        -> -2
      このオペレーターが BIGINT とともに使用された場合、 返り値は BIGINT であることに注意してください! これは -2^63 の値を 持つかもしれない整数を、 - で使用してはならないことを意味します！
      ABS(X)
      Returns the absolute value of X: 
      mysql> SELECT ABS(2);
        -> 2
mysql> SELECT ABS(-32);
        -> 32
      この関数は BIGINT 値とともに使用されると安全です。
      SIGN(X)
      X が負数、ゼロ、整数によって、 -1, 0 or 1 を 返します: 
      mysql> SELECT SIGN(-32);
        -> -1
mysql> SELECT SIGN(0);
        -> 0
mysql> SELECT SIGN(234);
        -> 1
      MOD(N,M)
      %
      剰余 ( C の % 演算子のような ). N を M で割ったときの余りが返ります: 
      mysql> SELECT MOD(234, 10);
        -> 4
mysql> SELECT 253 % 7;
        -> 1
mysql> SELECT MOD(29,9);
        -> 2
      この関数は BIGINT 値でも安全に使用できます。
      FLOOR(X)
      X より大きくならない整数のうち、最大の整数値を返します: 
      mysql> SELECT FLOOR(1.23);
        -> 1
mysql> SELECT FLOOR(-1.23);
        -> -2
      返り値は BIGINT に変換されていることに注意!
      CEILING(X)
      X より小さくならない整数のうち、最小の整数値を返します. 
      mysql> SELECT CEILING(1.23);
        -> 2
mysql> SELECT CEILING(-1.23);
        -> -1
      返り値は BIGINT に変換されていることに注意!
      ROUND(X)
      X を整数に丸めた値(四捨五入)を返します: 
      mysql> SELECT ROUND(-1.23);
        -> -1
mysql> SELECT ROUND(-1.58);
        -> -2
mysql> SELECT ROUND(1.58);
        -> 2
      引数が２つの整数間の半分時の ROUND() の振る舞いは、C ライブラリの実 装に依存します。いくつかは、近い偶数値、常に上、常に下、または常に０方向に 丸めます。丸めの種類の一つを必要とする場合は、TRUNCATE() または FLOOR() のようなはっきりと定義された関数を代わりに使用すべきです。
      ROUND(X,D)
      X を D で指定した少数桁に丸めた値(四捨五入)を返します。 もし D が 0 なら, 結果は小数点無しになるか 少数部分になるでしょう: 
      mysql> SELECT ROUND(1.298, 1);
        -> 1.3
mysql> SELECT ROUND(1.298, 0);
        -> 1
      EXP(X)
      指数関数 : e (自然対数の底) の X 乗: 
      mysql> SELECT EXP(2);
        -> 7.389056
mysql> SELECT EXP(-2);
        -> 0.135335
      LN(X)
      Returns the natural logarithm of X: 
      mysql> SELECT LN(2);
        -> 0.693147
mysql> SELECT LN(-2);
        -> NULL
      This function was added in MySQL version 4.0.3. It is synonymous with LOG(X) in MySQL.
      LOG(X)
      LOG(B,X)
      自然対数 X: If called with one parameter, this function returns the natural logarithm of X: 
      mysql> SELECT LOG(2);
        -> 0.693147
mysql> SELECT LOG(-2);
        -> NULL
      任意の底 B に対する X の対数を得たければ、公式 LOG(X)/LOG(B) を使用してください。 If called with two parameters, this function returns the logarithm of X for an arbitary base B: 
      mysql> SELECT LOG(2,65536);
        -> 16.000000
mysql> SELECT LOG(1,100);
        -> NULL
      The arbitrary base option was added in MySQL version 4.0.3. LOG(B,X) is equivalent to LOG(X)/LOG(B).
      LOG2(X)
      Returns the base-2 logarithm of X: 
      mysql> SELECT LOG2(65536);
        -> 16.000000
mysql> SELECT LOG2(-100);
        -> NULL
      LOG2() is useful for finding out how many bits a number would require for storage. This function was added in MySQL version 4.0.3. In earlier versions, you can use LOG(X)/LOG(2) instead.
      LOG10(X)
      常用対数(10を底とした対数) X: 
      mysql> SELECT LOG10(2);
        -> 0.301030
mysql> SELECT LOG10(100);
        -> 2.000000
mysql> SELECT LOG10(-100);
        -> NULL
      POW(X,Y)
      POWER(X,Y)
      X の Y 乗: 
      mysql> SELECT POW(2,2);
        -> 4.000000
mysql> SELECT POW(2,-2);
        -> 0.250000
      SQRT(X)
      X の非負の平方根を返します: 
      mysql> SELECT SQRT(4);
        -> 2.000000
mysql> SELECT SQRT(20);
        -> 4.472136
      PI()
      π の値を返します。デフォルトの表示桁数は 5 ですが、MySQL 内部で は π に完全な倍精度を使用します。 
      mysql> SELECT PI();
        -> 3.141593
mysql> SELECT PI()+0.000000000000000000;
        -> 3.141592653589793116
      COS(X)
      コサイン X。X はラジアン: 
      mysql> SELECT COS(PI());
        -> -1.000000
      SIN(X)
      サイン X。X はラジアン: 
      mysql> SELECT SIN(PI());
        -> 0.000000
      TAN(X)
      タンジェント X。X はラジアン: 
      mysql> SELECT TAN(PI()+1);
        -> 1.557408
      ACOS(X)
      X のアークコサインを返します。これはコサインが X である値で す。X が -1 から 1 の範囲にない場合は NULL を 返します: 
      mysql> SELECT ACOS(1);
        -> 0.000000
mysql> SELECT ACOS(1.0001);
        -> NULL
mysql> SELECT ACOS(0);
        -> 1.570796
      ASIN(X)
      X のアークサインを返します。これはサインが X である値です。 X が -1 から 1 の範囲にない場合は NULL を返し ます: 
      mysql> SELECT ASIN(0.2);
        -> 0.201358
mysql> SELECT ASIN('foo');
        -> 0.000000
      ATAN(X)
      X のアークタンジェントを返します。これはタンジェントが X で ある値です: 
      mysql> SELECT ATAN(2);
        -> 1.107149
mysql> SELECT ATAN(-2);
        -> -1.107149
      ATAN(Y,X)
      ATAN2(Y,X)
      ２つの変数 X と Y のアークタンジェントを返します。両方の引数 の符号が結果の象限を決定するために使用されることを除いて、Y / X の アークタンジェントの計算と同様です: 
      mysql> SELECT ATAN(-2,2);
        -> -0.785398
mysql> SELECT ATAN2(PI(),0);
        -> 1.570796
      COT(X)
      X のコタンジェントを返します: 
      mysql> SELECT COT(12);
        -> -1.57267341
mysql> SELECT COT(0);
        -> NULL
      RAND()
      RAND(N)
      0 から 1.0 間のランダムな浮動小数点数値を返します。 もし N に整数を与えた場合、シードとしてこの値が使用されます: 
      mysql> SELECT RAND();
        -> 0.9233482386203
mysql> SELECT RAND(20);
        -> 0.15888261251047
mysql> SELECT RAND(20);
        -> 0.15888261251047
mysql> SELECT RAND();
        -> 0.63553050033332
mysql> SELECT RAND();
        -> 0.70100469486881
      RAND() 値を持つフィールドは ORDER BY 節で使用できません。 ORDER BY はフィールドを複数回評価するためです。 しかし MySQL バージョン 3.23 では, 次が可能です: SELECT * FROM table_name ORDER BY RAND() これは SELECT * FROM table1,table2 WHERE a=b AND c<d ORDER BY RAND() LIMIT 1000 のセットからランダムなサンプルを得るのに便利です。 注意: WHERE 節の RAND() は WHERE が実行する度に再評価 されます。 RAND() is not meant to be a perfect random generator, but instead a fast way to generate ad hoc random numbers that will be portable between platforms for the same MySQL version.
      LEAST(X,Y,...)
      二つ以上の引数を取り、引数中、最小の値を返します。 引数は以下の規則に従って比較されます：
      • 値が INTEGER を使用しているなら、あるいは、全ての引数が 整数値ならば、整数として比較します。
      • 値が REAL として使用されているか、全ての引数が実数ならば、 実数として比較します。
      • いかなる引数もケース依存の文字ならば、引数はケース依存文字として比較されます。
      • そのほかの場合、引数はケース非依存文字として比較されます: 
      mysql> SELECT LEAST(2,0);
        -> 0
mysql> SELECT LEAST(34.0,3.0,5.0,767.0);
        -> 3.0
mysql> SELECT LEAST("B","A","C");
        -> "A"
      バージョン 3.22.5 以前の MySQL では、MIN() を LEAST の代 わりに使用できます。
      GREATEST(X,Y,...)
      二つ以上の引数を取り、引数中、最大の値を返します。 引数は LEAST の時と同じように比較されます。 
      mysql> SELECT GREATEST(2,0);
        -> 2
mysql> SELECT GREATEST(34.0,3.0,5.0,767.0);
        -> 767.0
mysql> SELECT GREATEST("B","A","C");
        -> "C"
      バージョン 3.22.5 以前の MySQL では、MAX() を GREATEST の 代わりに使用できます。
      DEGREES(X)
      引数 X をラジアンから度に変換して返します: 
      mysql> SELECT DEGREES(PI());
        -> 180.000000
      RADIANS(X)
      引数 X を度からラジアンに変換して返します: 
      mysql> SELECT RADIANS(90);
        -> 1.570796
      TRUNCATE(X,D)
      少数点以下 D 桁で X を切り捨てた値を返します。 D が 0 の場合、結果は小数部や微小部を持ちません: 
      mysql> SELECT TRUNCATE(1.223,1);
        -> 1.2
mysql> SELECT TRUNCATE(1.999,1);
        -> 1.9
mysql> SELECT TRUNCATE(1.999,0);
        -> 1
mysql> SELECT TRUNCATE(-1.999,1);
        -> -1.9
      Starting from MySQL 3.23.51 all numbers are rounded towards zero. If D is negative, then the whole part of the number is zeroed out: 
      mysql> SELECT TRUNCATE(122,-2);
       -> 100
      注意: コンピュータでは小数点数は正確な数値としては格納されず、double 値と して格納されます。次の結果によってだまされるでしょう: 
      mysql> SELECT TRUNCATE(10.28*100,0);
       -> 1027
      上記は 10.28 は実際には 10.2799999999999999 のようなものとして格納さえるた めに発生します。

      6.3.4 日付と時刻関数

      それぞれの型がもつ値の範囲と日と時間の値が記述される有効な形式については 「6.2.2 日付と時間の型」節.

      日付関数を使用する例: date_col が最新の30日である全てのレコードを選択します: 

      mysql> SELECT something FROM table
           WHERE TO_DAYS(NOW()) - TO_DAYS(date_col) <= 30;
      DAYOFWEEK(date)
      Returns the weekday index date の曜日を得ます (1 = 日曜日, 2 = 月曜日, ... 7 = 土曜日) これは ODBC 標準に従います: 
      mysql> SELECT DAYOFWEEK('1998-02-03');
        -> 3
      WEEKDAY(date)
      date の曜日を得ます (0 = 月曜日, 1 = 火曜日, ... 6 = 日曜日): 
      mysql> SELECT WEEKDAY('1998-02-03 22:23:00');
        -> 1
mysql> SELECT WEEKDAY('1997-11-05');
        -> 2
      DAYOFMONTH(date)
      月の日を返します (1 - 31): 
      mysql> SELECT DAYOFMONTH('1998-02-03');
        -> 3
      DAYOFYEAR(date)
      年の日を返します (1-366): 366: 
      mysql> SELECT DAYOFYEAR('1998-02-03');
        -> 34
      MONTH(date)
      月を返します (1 - 12): 
      mysql> SELECT MONTH('1998-02-03');
        -> 2
      DAYNAME(date)
      曜日の名前を返します: 
      mysql> SELECT DAYNAME("1998-02-05");
        -> 'Thursday'
      MONTHNAME(date)
      月の名前を返します: 
      mysql> SELECT MONTHNAME("1998-02-05");
        -> 'February'
      QUARTER(date)
      date についての年の四半期を返します。範囲は 1 から 4 です: 
      mysql> SELECT QUARTER('98-04-01');
        -> 2
      WEEK(date)
      WEEK(date,first)
      引数が一つの場合、date についての週を返します。範囲は 0 から 53 (そう、53週の最初というのもありえます)で、日曜日が週の 最初の日です。 引数が二つの形式の WEEK() は、週の開始を日曜日か月曜日か指定できます。 それぞれの場合の返り値は 0-53 か 1-52 です。 Here is a table for how the second arguments work:
      Value Meaning
      0 Week starts on Sunday and return value is in range 0-53
      1 Week starts on Monday and return value is in range 0-53
      2 Week starts on Sunday and return value is in range 1-53
      3 Week starts on Monday and return value is in range 1-53 (ISO 8601) 
      mysql> SELECT WEEK('1998-02-20');
        -> 7
mysql> SELECT WEEK('1998-02-20',0);
        -> 7
mysql> SELECT WEEK('1998-02-20',1);
        -> 8
mysql> SELECT WEEK('1998-12-31',1);
        -> 53
      Note: in Version 4.0, WEEK(#,0) was changed to match the calendar in the USA. Note that if a week is the last week of the previous year, MySQL will return 0 if you don't use 2 or 3 as the optional argument: 
      mysql> SELECT YEAR('2000-01-01'), WEEK('2000-01-01',0);
        -> 2000, 0
mysql> SELECT WEEK('2000-01-01',2);
        -> 52
      One could argue that MySQL should return 52 for the WEEK() function as the given date is actually the 52 second week of 1999. We decided to return 0 instead as we want the function to return 'the week number in the given year'. This makes the usage of the WEEK() function reliable when combined with other functions that extracts a date part from a date. If you would prefer to know the correct year-week, then you should use the 2 or 3 as the optional argument or use the YEARWEEK() function: 
      mysql> SELECT YEARWEEK('2000-01-01');
        -> 199952
mysql> SELECT MID(YEARWEEK('2000-01-01'),5,2);
        -> 52
      YEAR(date)
      年を返します (1000 - 9999): 
      mysql> SELECT YEAR('98-02-03');
        -> 1998
      YEARWEEK(date)
      YEARWEEK(date,first)
      データの年と週を返します。第2引数は WEEK() の第2引数とまったく同じ ように働きます。注意: 年の最初と最後の週では、年が date 引数内の年とは異な ることがあります！ 
      mysql> SELECT YEARWEEK('1987-01-01');
        -> 198653
      Note that the week number is different from what the WEEK() function would return (0) for optional arguments 0 or 1, as WEEK() then returns the week in the context of the given year.
      HOUR(time)
      時を返します (0 - 23): 
      mysql> SELECT HOUR('10:05:03');
        -> 10
      MINUTE(time)
      分を返します (0-59): 
      mysql> SELECT MINUTE('98-02-03 10:05:03');
        -> 5
      SECOND(time)
      秒を返します (0 to 59) 
      mysql> SELECT SECOND('10:05:03');
        -> 3
      PERIOD_ADD(P,N)
      N 月を期間 P (型 YYMM または YYYYMM) に追加 します。YYYYMM を返します。 注意: 期間引数 P は日付値では ありません。 
      mysql> SELECT PERIOD_ADD(9801,2);
        -> 199803
      PERIOD_DIFF(P1,P2)
      期間 P1 と P2 の差の月を返します。P1 と P2 は形 式 YYMM または YYYYMM です。 注意: 期間引数 P1 と P2 は日付値では ありません。 
      mysql> SELECT PERIOD_DIFF(9802,199703);
        -> 11
      DATE_ADD(date,INTERVAL expr type)
      DATE_SUB(date,INTERVAL expr type)
      ADDDATE(date,INTERVAL expr type)
      SUBDATE(date,INTERVAL expr type)
      これら関数は日付の演算に使用します。 これらは MySQL バージョン 3.22 の 新しい機能です。 ADDDATE() と SUBDATE() は DATE_ADD() , DATE_SUB() と同義です。 MySQL バージョン 3.23 では, + と - を DATE_ADD() , DATE_SUB() の代わりに使用できます. (See example below.) date には、DATETIME か DATE 型の値を指定します。 この値から演算が開始されます。 expr には、date から増減させる値を指定します。 expr が `-' から始まっていれば、負数を示します。 type はどれぐらいの期間かを示すキーワードです。 EXTRACT(type FROM date) 関数は、date から 'type' の部分を返します。 以下の表に、type と expr の関連を示します：
      type value Expected expr format
      SECOND SECONDS
      MINUTE MINUTES
      HOUR HOURS
      DAY DAYS
      MONTH MONTHS
      YEAR YEARS
      MINUTE_SECOND "MINUTES:SECONDS"
      HOUR_MINUTE "HOURS:MINUTES"
      DAY_HOUR "DAYS HOURS"
      YEAR_MONTH "YEARS-MONTHS"
      HOUR_SECOND "HOURS:MINUTES:SECONDS"
      DAY_MINUTE "DAYS HOURS:MINUTES"
      DAY_SECOND "DAYS HOURS:MINUTES:SECONDS"
      MySQL は、 expr フォーマット内のいかなる句読点区切りをも許します。 上の表中の区切り文字は提案する区切り文字です。 もし date 引数が DATE 値で、YEAR, MONTH, DAY の部分のみを含む 計算をするなら、結果は DATE 値が返ります。 それ以外なら DATETIME 値が返ります: 
      mysql> SELECT "1997-12-31 23:59:59" + INTERVAL 1 SECOND;
        -> 1998-01-01 00:00:00
mysql> SELECT INTERVAL 1 DAY + "1997-12-31";
        -> 1998-01-01
mysql> SELECT "1998-01-01" - INTERVAL 1 SECOND;
       -> 1997-12-31 23:59:59
mysql> SELECT DATE_ADD("1997-12-31 23:59:59",
    ->                 INTERVAL 1 SECOND);
        -> 1998-01-01 00:00:00
mysql> SELECT DATE_ADD("1997-12-31 23:59:59",
    ->                 INTERVAL 1 DAY);
        -> 1998-01-01 23:59:59
mysql> SELECT DATE_ADD("1997-12-31 23:59:59",
    ->                 INTERVAL "1:1" MINUTE_SECOND);
        -> 1998-01-01 00:01:00
mysql> SELECT DATE_SUB("1998-01-01 00:00:00",
    ->                 INTERVAL "1 1:1:1" DAY_SECOND);
        -> 1997-12-30 22:58:59
mysql> SELECT DATE_ADD("1998-01-01 00:00:00",
    ->                 INTERVAL "-1 10" DAY_HOUR);
        -> 1997-12-30 14:00:00
mysql> SELECT DATE_SUB("1998-01-02", INTERVAL 31 DAY);
        -> 1997-12-02
      もしあなたの指定する interval 値が短すぎるなら( type キーワードから 類推される値を含んでいない場合)、 MySQL は interval 値の一番 左の部分を指定し忘れたものだと仮定します。 例えば、もし type を DAY_SECOND に指定した場合、 expr の値は 日、時、分、秒 からなる物と期待されます。 ここであなたが "1:10" のような値を指定していたなら、 MySQL は、日、時 の部分が忘れ去られて、分、秒 が与えられたと 推定します。 つまり、 "1:10" DAY_SECOND は "1:10" MINUTE_SECOND で あると理解されるのです。 これは、MySQL が TIME 値を時刻ではなく経過時間の表現と解釈 する方法に類似しています。 注意: 時刻部を含む何かに対して、日付値の加算や減算を行なう場合、日付値は自 動的に日時値に変換されます: 
      mysql> SELECT DATE_ADD("1999-01-01", INTERVAL 1 DAY);
       -> 1999-01-02
mysql> SELECT DATE_ADD("1999-01-01", INTERVAL 1 HOUR);
       -> 1999-01-01 01:00:00
      もし、不正な値が使用されたなら、結果は NULL です. もし MONTH や YEAR_MONTH や YEAR を足し算して、 結果となる日付が新しい月の最大日よりも大きい日になるようなら、 その日は、新しい月の最大日に修正されます。 
      mysql> SELECT DATE_ADD('1998-01-30', Interval 1 month);
        -> 1998-02-28
      例のように、INTERVAL と type キーワードは ケース依存ではありません.
      EXTRACT(type FROM date)
      The EXTRACT() function uses the same kinds of interval type specifiers as DATE_ADD() or DATE_SUB(), but extracts parts from the date rather than performing date arithmetic. 
      mysql> SELECT EXTRACT(YEAR FROM "1999-07-02");
       -> 1999
mysql> SELECT EXTRACT(YEAR_MONTH FROM "1999-07-02 01:02:03");
       -> 199907
mysql> SELECT EXTRACT(DAY_MINUTE FROM "1999-07-02 01:02:03");
       -> 20102
      TO_DAYS(date)
      日付 date を与えると、0年からの日数を返します。 
      mysql> SELECT TO_DAYS(950501);
        -> 728779
mysql> SELECT TO_DAYS('1997-10-07');
        -> 729669
      TO_DAYS() はグレゴリオ歴の開始(1582)より前の値での使用を意図されて いません。歴が変更された時に失われた日を考慮に入れてないからです。
      FROM_DAYS(N)
      与えられた日数 N から DATE 値を返します: 
      mysql> SELECT FROM_DAYS(729669);
        -> '1997-10-07'
      FROM_DAYS() はグレゴリオ歴の開始(1582)より前の値での使用を意図され ていません。歴が変更された時に失われた日を考慮に入れてないからです。
      DATE_FORMAT(date,format)
      date 値を format 文字列に従って整形します。次の指定が format 文字列で使用できます:
      Specifier Description
      %M 月名 (January..December)
      %W 曜日 (Sunday..Saturday)
      %D 英語サフィックス付き月の日 (0th, 1st, 2nd, 3rd, etc.)
      %Y 4桁の年
      %y 2桁の年
      %X 週の年。週の最初の日は日曜日。4桁の数値。'%V' と共に使用されます
      %x 週の年。週の最初の日は月曜日。4桁の数値。'%v' と共に使用されます
      %a 省略された曜日名 (Sun..Sat)
      %d 月の日, 数値 (00..31)
      %e 月の日, 数値 (0..31)
      %m 月, 数値 (00..12)
      %c 月, 数値 (0..12)
      %b 省略された月名 (Jan..Dec)
      %j 年の日 (001..366)
      %H 時 (00..23)
      %k 時 (0..23)
      %h 時 (01..12)
      %I 時 (01..12)
      %l 時 (1..12)
      %i 分, 数値 (00..59)
      %r 時刻, 12時間 (hh:mm:ss [AP]M)
      %T 時刻, 24時間 (hh:mm:ss)
      %S 秒 (00..59)
      %s 秒 (00..59)
      %p AM or PM
      %w 週の日 (0=Sunday..6=Saturday)
      %U 週 (00..53), 週のはじまりを 日曜とした場合
      %u 週 (00..53), 週のはじまりを 月曜とした場合
      %V 週 (01..53), 週のはじまりは日曜日。'%X' と共に使用されます
      %v 週 (01..53), 週のはじまりは月曜日。'%x' と共に使用されます
      %% リテラル `%'。
      他の全ての文字は解釈されずに結果にコピーされます: 
      mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%W %M %Y');
        -> 'Saturday October 1997'
mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00', '%H:%i:%s');
        -> '22:23:00'
mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00',
                          '%D %y %a %d %m %b %j');
        -> '4th 97 Sat 04 10 Oct 277'
mysql> SELECT DATE_FORMAT('1997-10-04 22:23:00',
                          '%H %k %I %r %T %S %w');
        -> '22 22 10 10:23:00 PM 22:23:00 00 6'
mysql> SELECT DATE_FORMAT('1999-01-01', '%X %V');
        -> '1998 52'
      MySQL バージョン 3.23 では、 % 文字はフォーマット文字の前に必ず 必要とされます。 それより前のバージョンでは、 % 文字はオプションでした。 The reason the ranges for the month and day specifiers begin with zero is that MySQL allows incomplete dates such as '2004-00-00' to be stored as of MySQL 3.23.
      TIME_FORMAT(time,format)
      これは上記の DATE_FORMAT() のように使用されますが、 format オプションでは、時,分,秒だけを操作できます。 他のオプションは NULL or 0 を与えます。
      CURDATE()
      CURRENT_DATE
      今日の日付を返します。日付の形式は、CURDATE() が数値または文字列のどち らの文脈で使用されたかに依存して YYYYMMDD または 'YYYY-MM-DD' で返 されます: 
      mysql> SELECT CURDATE();
        -> '1997-12-15'
mysql> SELECT CURDATE() + 0;
        -> 19971215
      CURTIME()
      CURRENT_TIME
      現在の時刻を HHMMSS または 'HH:MM:SS' の形式で返します。こ れは CURTIME() が数値または文字列のどちらの文脈で使用されたかに依 存します: 
      mysql> SELECT CURTIME();
        -> '23:50:26'
mysql> SELECT CURTIME() + 0;
        -> 235026
      NOW()
      SYSDATE()
      CURRENT_TIMESTAMP
      現在の時刻を返します。数値または文字列のどちらの文脈で使用されたかに依存して YYYYMMDDHHMMSS または 'YYYY-MM-DD HH:MM:SS' 形式で返されます: 
      mysql> SELECT NOW();
        -> '1997-12-15 23:50:26'
mysql> SELECT NOW() + 0;
        -> 19971215235026
      Note that NOW() is only evaluated once per query, namely at the start of query execution. This means that multiple references to NOW() within a single query will always give the same time.
      UNIX_TIMESTAMP()
      UNIX_TIMESTAMP(date)
      引数なしで呼び出された場合は、UNIX timestamp (GMT '1970-01-01 00:00:00' からの秒数) です。If UNIX_TIMESTAMP() is called with a date argument, it returns the value of the argument as seconds since '1970-01-01 00:00:00' GMT. date はローカル時刻での DATE 文字列、DATETIME 文字列、TIMESTAMP, または YYMMDD または YYYYMMDD 形式の数値です: 
      mysql> SELECT UNIX_TIMESTAMP();
        -> 882226357
mysql> SELECT UNIX_TIMESTAMP('1997-10-04 22:23:00');
        -> 875996580
      UNIX_TIMESTAMP が TIMESTAMP フィールドに使用された場合、 この関数は、暗黙の ``文字から UNIX タイムスタンプ'' 変換をすることなく、 値を得ます。 If you pass an out-of-range date to UNIX_TIMESTAMP() it will return 0, but please note that only basic checking is performed (year 1970-2037, month 01-12, day 01-31). If you want to subtract UNIX_TIMESTAMP() columns, you may want to cast the result to signed integers. 「6.3.5 Cast Functions」節参照.
      FROM_UNIXTIME(unix_timestamp)
      文脈(数値/文字列)に依存して、'YYYY-MM-DD HH:MM:SS' または YYYYMMDDHHMMSS 形式の timestamp 文字列を返します: 
      mysql> SELECT FROM_UNIXTIME(875996580);
        -> '1997-10-04 22:23:00'
mysql> SELECT FROM_UNIXTIME(875996580) + 0;
        -> 19971004222300
      FROM_UNIXTIME(unix_timestamp,format)
      format に従って整形された UNIX timestamp 文字列を返します。 format は DATE_FORMAT() 関数のエントリに一覧されたのと同じ指 定子を含むことができます: 
      mysql> SELECT FROM_UNIXTIME(UNIX_TIMESTAMP(),
                            '%Y %D %M %h:%i:%s %x');
        -> '1997 23rd December 03:43:30 1997'
      SEC_TO_TIME(seconds)
      seconds 引数を時分秒に変換して返します。関数が文字列文脈または数値 文脈のどちらで使用されたかに依存して、'HH:MM:SS' または HHMMSS 形式で値を返します: 
      mysql> SELECT SEC_TO_TIME(2378);
        -> '00:39:38'
mysql> SELECT SEC_TO_TIME(2378) + 0;
        -> 3938
      TIME_TO_SEC(time)
      time を秒に変換します。 
      mysql> SELECT TIME_TO_SEC('22:23:00');
        -> 80580
mysql> SELECT TIME_TO_SEC('00:39:38');
        -> 2378

      6.3.5 Cast Functions

      The syntax of the CAST function is: 

      CAST(expression AS type)

or

CONVERT(expression,type)

      Where type is one of:

      • BINARY
      • CHAR (New in 4.0.6)
      • DATE
      • DATETIME
      • SIGNED {INTEGER}
      • TIME
      • UNSIGNED {INTEGER}

      CAST() is ANSI SQL99 syntax and CONVERT() is ODBC syntax.

      The cast function is mainly useful when you want to create a column with a specific type in a CREATE ... SELECT: 

      CREATE TABLE new_table SELECT CAST('2000-01-01' AS DATE);

      CAST(string AS BINARY is the same thing as BINARY string. CAST(expr AS CHAR threats expression to be a string with the default character set.

      To cast a string to a numeric value, you don't normally have to do anything; just use the string value as it would be a number: 

      mysql> SELECT 1+'1';
       -> 2

      If you use a number in string context the number will automatically be converted to a BINARY string. 

      mysql> SELECT CONCAT("hello you ",2);
       ->  "hello you 2"

      MySQL supports arithmetic with both signed and unsigned 64-bit values. If you are using an numerical operations (like +) and one of the operands are unsigned integer, then the result will be unsigned. You can override this by using the SIGNED and UNSIGNED cast operators, which will cast the operation to a signed or unsigned 64-bit integer, respectively. 

      mysql> SELECT CAST(1-2 AS UNSIGNED)
        -> 18446744073709551615
mysql> SELECT CAST(CAST(1-2 AS UNSIGNED) AS SIGNED);
        -> -1

      Note that if either operation is a floating-point value (In this context DECIMAL() is regarded as a floating-point value) the result will be a floating-point value and is not affected by the above rule. 

      mysql> SELECT CAST(1 AS UNSIGNED) -2.0
        -> -1.0

      If you are using a string in an arithmetic operation, this is converted to a floating-point number.

      The CAST() and CONVERT() functions were added in MySQL 4.0.2.

      The handing of unsigned values was changed in MySQL 4.0 to be able to support BIGINT values properly. If you have some code that you want to run in both MySQL 4.0 and 3.23 (in which case you probably can't use the CAST function), you can use the following trick to get a signed result when subtracting two unsigned integer columns: 

      SELECT (unsigned_column_1+0.0)-(unsigned_column_2+0.0);

      The idea is that the columns are converted to floating-point before doing the subtraction.

      If you get a problem with UNSIGNED columns in your old MySQL application when porting to MySQL 4.0, you can use the --sql-mode=NO_UNSIGNED_SUBTRACTION option when starting mysqld. Note however that as long as you use this, you will not be able to make efficient use of the UNSIGNED BIGINT column type.

      6.3.6 その他の関数

      6.3.6.1 ビット関数

      これらは最大 64 ビットの範囲を持ちます。MySQL は BIGINT (64-bit) 演算を使用するためです。

      |
      ビット演算 OR 
      mysql> SELECT 29 | 15;
        -> 31
      The result is an unsigned 64-bit integer.
      &
      ビット演算 AND 
      mysql> SELECT 29 & 15;
        -> 13
      The result is an unsigned 64-bit integer.
      ^
      Bitwise XOR 
      mysql> SELECT 1 ^ 1;
        -> 0
mysql> SELECT 1 ^ 0;
        -> 1
mysql> SELECT 11 ^ 3;
        -> 8
      The result is an unsigned 64-bit integer. XOR was added in version 4.0.2.
      <<
      左に longlong (BIGINT) number 分、ビットをシフトします: 
      mysql> SELECT 1 << 2;
        -> 4
      The result is an unsigned 64-bit integer.
      >>
      右に longlong (BIGINT) number 分、ビットをシフトします: 
      mysql> SELECT 4 >> 2;
        -> 1
      The result is an unsigned 64-bit integer.
      ~
      Invert all bits: 
      mysql> SELECT 5 & ~1;
        -> 4
      The result is an unsigned 64-bit integer.
      BIT_COUNT(N)
      引数 N がいくつビットを持っているか(２進数表記したときの１の数): 
      mysql> SELECT BIT_COUNT(29);
        -> 4

      6.3.6.2 その他の関数

      DATABASE()
      現在のデータベース名を返します 
      mysql> SELECT DATABASE();
        -> 'test'
      もしデータベースが選択されていないなら、DATABASE() は空文字を返します。
      USER()
      SYSTEM_USER()
      SESSION_USER()
      Returns the current MySQL user name: 
      mysql> SELECT USER();
        -> 'davida@localhost'
      MySQL バージョン 3.22.11 以降では、この関数はユーザー名とクライアントの ホスト名を含みます。 ユーザー名の部分だけ取り出すには次のようにします。 （これはホスト名が含まれていなくとも動くでしょう）： 
      mysql> SELECT substring_index(USER(),"@",1);
        -> 'davida'
      CURRENT_USER()
      Returns the user name, current session was authentificated as: 
      mysql> SELECT USER();
        -> 'davida@localhost'
mysql> SELECT * FROM mysql.user;
        -> ERROR 1044: Access denied for user: '@localhost' to database 'mysql'
mysql> SELECT CURRENT_USER();
        -> '@localhost'
      PASSWORD(str)
      OLD_PASSWORD(str)
      プレーンテキストのパスワード str からパスワード文字列を計算します。 これは user 許可テーブルの Password フィールドに、 暗号化された MySQL パスワードを保存する際に使用されます: 
      mysql> SELECT PASSWORD('badpwd');
        -> '7f84554057dd964b'
      PASSWORD() 暗号は不可逆です。 PASSWORD() は UNIX のパスワードが暗号化するのと同じ方法で 暗号化を行うわけではありません。 ENCRYPT() 参照。 注意: PASSWORD() 関数は MySQL サーバー内の認証システムで使用されます。 その関数をあなたの独自アプリケーションでは使用すべきではありません。 そうしたければ、代わりに MD5() や SHA1() を使用します。 Also see RFC-2195 for more information about handling passwords and authentication securely in your application.
      ENCRYPT(str[,salt])
      UNIX の crypt() システムコールで str を暗号化します。 salt は2文字の文字列です。 (MySQL バージョン 3.22.16 で, salt は2文字以上許されるようになり ました。) 
      mysql> SELECT ENCRYPT("hello");
        -> 'VxuFAJXVARROc'
      システムで crypt() が利用できない場合は ENCRYPT() は常に NULL を返します。 少なくともいくつかのシステムでは、 ENCRYPT() は str 文字中の最初の 8 文字以外は全て無視します。 これは crypt() システムコールの振る舞いによって決定づけられます。
      ENCODE(str,pass_str)
      パスワードとして pass_str を用いて str を暗号化します。結果 を復号化するには、DECODE()を使用します。 結果はバイナリ文字列で、長さは string と同じです。 フィールドにそれを保存したい場合は BLOB フィールド型を使用してください。
      DECODE(crypt_str,pass_str)
      暗号化された文字列 crypt_str をパスワードとして pass_str を 用いて復号化します。crypt_str は ENCODE() から返された文字列 であるべきです。
      MD5(string)
      文字列を MD5 128bit チェックサムした結果を返します。 値は 32 桁の 16進表示です。 例えばハッシュキーとして使用できるように: 
      mysql> SELECT MD5("testing");
        -> 'ae2b1fca515949e5d54fb22b8ed95575'
      これは "RSA Data Security, Inc. MD5 Message-Digest Algorithm".
      SHA1(string)
      SHA(string)
      Calculates an SHA1 160 bit checksum for the string, as described in RFC 3174 (Secure Hash Algorithm). The value is returned as a 40 digit hex number, or NULL in case the input argument was NULL. One of the possible uses for this function is as a hash key. You can also use it as cryptographically safe function for storing passwords. 
      mysql> SELECT SHA1("abc");
        -> 'a9993e364706816aba3e25717850c26c9cd0d89d'
      SHA1() was added in version 4.0.2, and can be considered a cryptographically more secure equivalent of MD5(). SHA() is synonym for SHA1().
      AES_ENCRYPT(string,key_string)
      AES_DECRYPT(string,key_string)
      These functions allow encryption/decryption of data using the official AES (Advanced Encryption Standard) algorithm, previously known as Rijndael. Encoding with 128 bit key length is used, but you can extend it up to 256 bit by patching the source. We chose 128 bits because it is much faster and it is usually secure enough. The input arguments may be any length. If either argument is NULL, the result of this function is also NULL. As AES is a block level algorithm, padding is used to encode uneven length strings and so the result string length may be calculated as 16*(trunc(string_length/16)+1). If AES_DECRYPT() detects invalid data or incorrect padding, it will return NULL. However, it is possible for AES_DECRYPT() to return a non-NULL value (possibly garbage) if the input data or the key was invalid. You can use the AES functions to store data in an encrypted form by modifying your queries: 
      INSERT INTO t VALUES (1,AES_ENCRYPT("text","password"));
      You can get even more security by avoiding transferring the key over the connection for each query, which can be accomplished by storing it in a server side variable at connection time: 
      SELECT @password:="my password";
INSERT INTO t VALUES (1,AES_ENCRYPT("text",@password));
      AES_ENCRYPT() and AES_DECRYPT() were added in version 4.0.2, and can be considered the most cryptographically secure encryption functions currently available in MySQL.
      DES_ENCRYPT(string_to_encrypt [, (key_number | key_string) ] )
      Encrypts the string with the given key using the Triple-DES algorithm. Note that this function only works if you have configured MySQL with SSL support. 「4.3.9 Using Secure Connections」節参照. The encryption key to use is chosen the following way:
      Argument Description
      Only one argument The first key from des-key-file is used.
      key number The given key (0-9) from the des-key-file is used.
      string The given key_string will be used to crypt string_to_encrypt.
      The return string will be a binary string where the first character will be CHAR(128 | key_number). The 128 is added to make it easier to recognise an encrypted key. If you use a string key, key_number will be 127. On error, this function returns NULL. The string length for the result will be new_length= org_length + (8-(org_length % 8))+1. The des-key-file has the following format: 
      key_number des_key_string
key_number des_key_string
      Each key_number must be a number in the range from 0 to 9. Lines in the file may be in any order. des_key_string is the string that will be used to encrypt the message. Between the number and the key there should be at least one space. The first key is the default key that will be used if you don't specify any key argument to DES_ENCRYPT() You can tell MySQL to read new key values from the key file with the FLUSH DES_KEY_FILE command. This requires the Reload_priv privilege. One benefit of having a set of default keys is that it gives applications a way to check for existence of encrypted column values, without giving the end user the right to decrypt those values. 
      mysql> SELECT customer_address FROM customer_table WHERE
       crypted_credit_card = DES_ENCRYPT("credit_card_number");
      DES_DECRYPT(string_to_decrypt [, key_string])
      Decrypts a string encrypted with DES_ENCRYPT(). Note that this function only works if you have configured MySQL with SSL support. 「4.3.9 Using Secure Connections」節参照. If no key_string argument is given, DES_DECRYPT() examines the first byte of the encrypted string to determine the DES key number that was used to encrypt the original string, then reads the key from the des-key-file to decrypt the message. For this to work the user must have the SUPER privilege. If you pass this function a key_string argument, that string is used as the key for decrypting the message. If the string_to_decrypt doesn't look like an encrypted string, MySQL will return the given string_to_decrypt. On error, this function returns NULL.
      LAST_INSERT_ID([expr])
      最後に AUTO_INCREMENT フィールドに挿入されて自動的に生成された値を返しま す。 「8.4.3.130 mysql_insert_id()」節参照. 
      mysql> SELECT LAST_INSERT_ID();
        -> 195
      最後の作成された ID はそれぞれのコネクション毎にサーバーに維持されます。 これは他のクライアントからは変更できないでしょう。 もし他の非マジック値をもつ AUTO_INCREMENT フィールド （値が NULL でも 0 でもないということ） を更新しても、これは 変更されません。 一つの INSERT 文で同時に多くのレコードを挿入する場合、 LAST_INSERT_ID() は最初に挿入されたレコードの値を返します。この理由 は、他のサーバに対して同じ INSERT を簡単に再現できるようにするため です。 If expr is given as an argument to LAST_INSERT_ID(), then the value of the argument is returned by the function, is set as the next value to be returned by LAST_INSERT_ID() and used as the next auto_increment value. これは シーケンス番号のシミュレーションに使用できます： 最初にテーブルを作成： 
      mysql> CREATE TABLE sequence (id int not null);
mysql> INSERT INTO sequence VALUES (0);
      そして以下のようにしてシーケンス番号を生成： 
      mysql> UPDATE sequence SET id=LAST_INSERT_ID(id+1);
      LAST_INSERT_ID() の呼び出し無しでシーケンス番号を生成することが可能 ですが、この方法でこの関数を使用するユーティリティは、ID 値が最後に自動的 に生成された値としてサーバに管理されます。MySQL 内の通常の任意の AUTO_INCREMENT 値を読み込んで新しい ID を取り出すことができます。例 えば、LAST_INSERT_ID() (引数無し) は新しい ID を返します。C API 関 数 mysql_insert_id() もこの値を得るために使用できます。 Note that as mysql_insert_id() is only updated after INSERT and UPDATE statements, so you can't use the C API function to retrieve the value for LAST_INSERT_ID(expr) after executing other SQL statements like SELECT or SET.
      FORMAT(X,D)
      '#,###,###.##' のような形式(小数部 X 桁)で数値 D を整形 します。 もし D が 0 なら, 結果にはいかなる 小数点も小数部も含まれません。 
      mysql> SELECT FORMAT(12332.123456, 4);
        -> '12,332.1235'
mysql> SELECT FORMAT(12332.1,4);
        -> '12,332.1000'
mysql> SELECT FORMAT(12332.2,0);
        -> '12,332'
      VERSION()
      MySQL サーバのバージョンを返します: 
      mysql> SELECT VERSION();
        -> '3.23.13-log'
      注意: バージョンが -log で終わる場合はロギングが有効であることを意 味します。
      CONNECTION_ID()
      接続の接続 ID (thread_id) を返します。すべての接続は接続自身の一意 な ID を持ちます: 
      mysql> SELECT CONNECTION_ID();
        -> 1
      GET_LOCK(str,timeout)
      timeout 秒のタイムアウトで、str と名付けられたロックの獲得を試み ます。ロックを獲得した場合は 1, タイムアウトの場合は 0, エラーの場 合(メ モリ不足やスレッドが mysqladmin kill で殺された場合など)は NULL が返ります。RELEASE_LOCK の実行、新しい GET_LOCK の実行、 スレッドの終了の場合に、ロックは解放されます。この関数はアプリケーション ロックやレコードロックのシミュレートのために使用できます。 これは、同じ名前のロックを行おうとする他のクライアントからのリクエストを ブロックします； 与えられた名前のロックに応じているクライアントは、 協調してロッキングを行うために、その文字列を使用できます: 
      mysql> SELECT GET_LOCK("lock1",10);
        -> 1
mysql> SELECT IS_FREE_LOCK("lock2");
        -> 1
mysql> SELECT GET_LOCK("lock2",10);
        -> 1
mysql> SELECT RELEASE_LOCK("lock2");
        -> 1
mysql> SELECT RELEASE_LOCK("lock1");
        -> NULL
      ２つ目の RELEASE_LOCK() は NULL を返します。 なぜなら、 "lock1" は、２つ目の GET_LOCK() の呼び出し時点で、 自動的に解放されるからです。
      RELEASE_LOCK(str)
      GET_LOCK で獲得したロック str を解放します。ロックが解 放された場合は 1, このスレッドによってロックされていない場合は 0 (この場合、ロックは解放されません), strが存在しない場合は NULL が返ります。 もし、 GET_LOCK() をコールして得られなかった場合、 あるいは、既に解放されている場合は、ロックは存在しないでしょう。 The DO statement is convinient to use with RELEASE_LOCK(). 「6.4.10 DO Syntax」節参照.
      IS_FREE_LOCK(str)
      Checks if the lock named str is free to use (i.e., not locked). Returns 1 if the lock is free (no one is using the lock), 0 if the lock is in use, and NULL on errors (like incorrect arguments).
      BENCHMARK(count,expr)
      BENCHMARK() 関数は expr で与えられた文を count 回 繰り返し実行します。 これは MySQL のその文の処理がどれぐらい 速いのか知るのに使用されるでしょう。 結果は常に 0 です。 想定している使用は、 mysql クライアントです。 あるクエリの実行時間を知るための使用です: 
      mysql> SELECT BENCHMARK(1000000,ENCODE("hello","goodbye"));
+----------------------------------------------+
| BENCHMARK(1000000,ENCODE("hello","goodbye")) |
+----------------------------------------------+
|                                            0 |
+----------------------------------------------+
1 row in set (4.74 sec)
      報告された時間は、クライアントでの経過時間です。 サーバー側の CPU 時間では ありません。BENCHMARK() を何回か実行して、サーバマシンの負荷の重さ を考慮して結果を解釈することを勧めます。
      INET_NTOA(expr)
      数値表現に対するネットワークアドレス(4 または 8 バイト) を返します: 
      mysql> SELECT INET_NTOA(3520061480);
       ->  "209.207.224.40"
      INET_ATON(expr)
      ネットワークアドレスに対する数値を表す整数を返します。アドレスは 4 または 8 バイトアドレスです: 
      mysql> SELECT INET_ATON("209.207.224.40");
       ->  3520061480
      生成された数値は常にネットワークバイトオーダです; たとえば、上記の数値は 209*255^3 + 207*255^2 + 224*255 +40 として計算されます。
      MASTER_POS_WAIT(log_name, log_pos)
      マスターログの指定された位置にスレーブが到達するまで(すなわち、スレーブが 読み込んで全て更新しおわるまで)ブロックします。 マスター情報が初期化されていないか引数が違う場合、NULL が返ります。 スレーブが動作していない場合、ブロックし、スレーブが起動し、指定位置にくるまで待ちます。 スレーブが既に指定位置を通り過ぎていた場合、即時復帰します。 If timeout (new in 4.0.10) is specified, will give up waiting when timeout seconds have elapsed. timeout must be greater than 0; a zero or negative timeout means no timeout. The return value is the number of log events it had to wait to get to the specified position, or NULL in case of error, or -1 if the timeout has been exceeded. This command is useful for control of master-slave synchronisation, but was originally written to facilitate replication testing.
      FOUND_ROWS()
      Returns the number of rows that the last SELECT SQL_CALC_FOUND_ROWS ... command would have returned, if it had not been restricted with LIMIT. 
      mysql> SELECT SQL_CALC_FOUND_ROWS * FROM tbl_name
       WHERE id > 100 LIMIT 10;
mysql> SELECT FOUND_ROWS();
      The second SELECT will return a number indicating how many rows the first SELECT would have returned had it been written without the LIMIT clause. Note that if you are using SELECT SQL_CALC_FOUND_ROWS ... MySQL has to calculate all rows in the result set. However, this is faster than if you would not use LIMIT, as the result set need not be sent to the client. SQL_CALC_FOUND_ROWS is available starting at MySQL version 4.0.0.

      6.3.6.3 Functions for Use with GROUP BY Clauses

      GROUP BY節を含まない文でグループ関数を使用すると 全てのレコードについてグループされたものとみなされます。

      COUNT(expr)
      Returns a count of the number of non-NULL values in the rows retrieved by a SELECT statement: SELECT文により選択されたレコードからNULLではないものの数を返します。 
      mysql> SELECT student.student_name,COUNT(*)
           FROM student,course
           WHERE student.student_id=course.student_id
           GROUP BY student_name;
      COUNT(*)はNULLを含むかどうかで選択されたレコードの数を返すだけです。 COUNT(*)は一つのテーブルから一つだけカラムが選択され、 尚且つWHERE節が使用されていない場合に最適化され、高速に動作します。 例えば以下のように使います。 
      mysql> SELECT COUNT(*) FROM student;
      COUNT(DISTINCT expr,[expr...])
      これはNULL値では無い値を持つデータの数を区別して返すことが出来ます。 
      mysql> SELECT COUNT(DISTINCT results) from student;
      複数の選択されたデータ群からNULLを含まないデータの総数算出が必要な場合、 MySQLでは必要な選択リストを与えることによって得ることが出来ます。 一方でANSIのSQLではその選択一つ一つについて COUNT(DISTINCT ...) を使う必要があります。
      AVG(expr)
      exprで得られる値の平均値を返します。 
      mysql> SELECT student_name, AVG(test_score)
           FROM student
           GROUP BY student_name;
      MIN(expr)
      MAX(expr)
      exprで得られる値の最大値、最小値を返します。 MIN()とMAX()の引数は文字列を取ることもできます。 この際は文字列の値の大小を比較し、最大と最小を返します。 「5.4.3 MySQL はどのようにインデックスを使用するか？」節. 
      mysql> SELECT student_name, MIN(test_score), MAX(test_score)
    ->        FROM student
    ->        GROUP BY student_name;
      In MIN(), MAX() and other aggregate functions, MySQL currently compares ENUM and SET columns by their string value rather than by the string's relative position in the set. This will be rectified.
      SUM(expr)
      exprで得られる値の総計を返します。 もしも得られるレコードが見つからない場合はNULLが返ってきます。
      VARIANCE(expr)
      Returns the standard variance of expr. This is an extension to ANSI SQL (available only in version 4.1 or later).
      STD(expr)
      STDDEV(expr)
      exprで得られる値の標準偏差を返します。 これはANSI SQLの格調になっています。 関数としてのSTDDEV()の形はOracleのものと互換性があります。
      BIT_OR(expr)
      exprで得られる値のビット和(OR)を返します。 計算は64-bit(BIGINT)の精度で行われます。
      BIT_AND(expr)
      exprで得られる値のビット積(AND)を返します。 計算は64-bit(BIGINT)の精度で行われます。

      MySQLのGROUP BYは拡張された使い方が可能です。 SELECTで使用したフィールド名や計算式をGROUP BYには使用しない、 という使い方が可能です。 このことはグループにはどんな値も使用可能ということを表しています。 データの並べ替えやグループ分けに適さない要素を排除することによって より良好なパフォーマンスを得ることが出来ます。 例えば、次のようなクエリでcustomer.nameについてのグループ分けをする必要はありません。 

      mysql> SELECT order.custid,customer.name,MAX(payments)
    ->        FROM order,customer
    ->        WHERE order.custid = customer.custid
    ->        GROUP BY order.custid;

      ANSI SQLではcustomer.nameをGROUP BYのところに追加する必要があります。 MySQLではANSIモードで動かしていない限り余計な記述の必要はありません。

      GROUP BYで省略するフィールドはグループ内でユニークでなくてはいけません。 もしそうでない場合は結果は予想もしないようなものになるでしょう。

      たとえユニークでは無くても特定のフィールドの値を得るために MIN()やMAX()を使用できるケースもあります。 次の例はsortフィールド中の最小値を持つレコードから 特定のcolumnの値を取り出します。 

      SUBSTR(MIN(CONCAT(RPAD(sort,6,' '),column)),7)

      「3.5.4 The Rows Holding the Group-wise Maximum of a Certain Field」節参照.

      MySQLの3.22以前のバージョンをお使いであるか、ANSI SQLに沿っての使用をされる場合は GROUP BYとORDER BY内に選択表現を記述してはいけません。 この制限を守った上で作業を進めるにはエイリアスを使用します。 

      mysql> SELECT id,FLOOR(value/100) AS val FROM tbl_name
    ->        GROUP BY id,val ORDER BY val;

      MySQLのバージョン3.23では次のようにも記述できます。 

      mysql> SELECT id,FLOOR(value/100) FROM tbl_name ORDER BY RAND();

      6.4 Data Manipulation: SELECT, INSERT, UPDATE, DELETE

      6.4.1 SELECT 構文

      SELECT [STRAIGHT_JOIN]
       [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT]
       [SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS] [HIGH_PRIORITY]
       [DISTINCT | DISTINCTROW | ALL]
    select_expression,...
    [INTO {OUTFILE | DUMPFILE} 'file_name' export_options]
    [FROM table_references
      [WHERE where_definition]
      [GROUP BY {unsigned_integer | col_name | formula} [ASC | DESC], ...]
      [HAVING where_definition]
      [ORDER BY {unsigned_integer | col_name | formula} [ASC | DESC] ,...]
      [LIMIT [offset,] rows | rows OFFSET offset]
      [PROCEDURE procedure_name(argument_list)]
      [FOR UPDATE | LOCK IN SHARE MODE]]

      SELECTは通常、1つまたは1つ以上のテーブルからレコードを検索して抽出 するのに使用されます。 select_expression は取り出したいフィールドを示します。 SELECTはまた、テーブルの参照なしに計算によって求められたレコードを 取り出すために使用されます。例: 

      mysql> SELECT 1 + 1;
         -> 2

      全てのキーワードの使用は、上記に示すような順序で正確に与えられる必要があります。 例えば、HAVING節は必ずGROUP BY節の後、ORDER BY節の前でなければなりません。

      • SELECTの表現では、ASによる別名の指定が可能です。別名は、 フィールド名の表現として使われ、ORDER BY及びHAVING節とともに使用することができます。 例: 
        mysql> SELECT CONCAT(last_name,', ',first_name) AS full_name
    FROM mytable ORDER BY full_name;
      • It is not allowed to use a column alias in a WHERE clause, because the column value may not yet be determined when the WHERE clause is executed. 「A.5.4 alias の問題」節参照.
      • FROM table_references節は、(例えば、選択するレコードにより、1つ又はそれ以上の) 結合するテーブルのリストを示します。 このリストはまた、LEFT OUTER JOIN参照を含むことがあります。 「6.4.1.1 JOIN 構文」節. を参照してください。 For each table specified, you may optionally specify an alias. 
        table_name [[AS] alias] [[USE INDEX (key_list)] | [IGNORE INDEX (key_list)] | FORCE INDEX (key_list)]]
        As of MySQL Version 3.23.12, you can give hints about which index MySQL should use when retrieving information from a table. This is useful if EXPLAIN shows that MySQL is using the wrong index from the list of possible indexes. By specifying USE INDEX (key_list), you can tell MySQL to use only one of the possible indexes to find rows in the table. The alternative syntax IGNORE INDEX (key_list) can be used to tell MySQL to not use some particular index. In MySQL 4.0.9 you can also use FORCE INDEX. This acts likes USE INDEX (key_list) but with the addition that a table scan is assumed to be VERY expensive. In other words a table scan will only be used if there is no way to use one of the given index to find rows in the table. USE/IGNORE/FORCE KEY are synonyms for USE/IGNORE/FORCE INDEX.
      • You can refer to a table as tbl_name (within the current database), or as dbname.tbl_name to explicitly specify a database. col_name、tbl_name.col_name、db_name.tbl_name.col_nameの ようにしてフィールドを表すことができます。 SELECTステートメント内での列の参照が曖昧でなければ、tbl_nameや db_name.tbl_nameのようなプリフィックスを詳細に記述する必要はありません。 より明示的なフィールドの指定形式をを必要とする曖昧な参照の例は、 「6.1.2 データベース名、テーブル名、インデックス名、フィールド名、エイリアス名」節を参照のこと。
      • テーブル参照は、tbl_name AS alias_name又はtbl_name alias_nameを 使って別名を使用することが可能です: 
        mysql> SELECT t1.name, t2.salary FROM employee AS t1, info AS t2
    ->        WHERE t1.name = t2.name;
mysql> SELECT t1.name, t2.salary FROM employee t1, info t2
    ->        WHERE t1.name = t2.name;
      • 出力用に選択されたフィールドは、ORDER BY節やGROUP BY節において、 フィールド名、フィールドのエイリアス名、又はフィールド番号にて指し示すことが できます。フィールド番号は1から始まります。 
        mysql> SELECT college, region, seed FROM tournament
    ->        ORDER BY region, seed;
mysql> SELECT college, region AS r, seed AS s FROM tournament
    ->        ORDER BY r, s;
mysql> SELECT college, region, seed FROM tournament
    ->        ORDER BY 2, 3;
        逆順で並べたい場合には、 ORDER BY 節の中で、あなたが並べたいと思っている フィールドの名前の後ろに、 DESC (descending) キーワードを 追加します。 デフォルトは昇順です； これは ASC キーワードを指定したことになります。
      • WHERE 節で MySQL がサポートする任意の関数を使用することが できます。 「6.3 SELECT と WHERE 節で使用する関数」節参照.
      • HAVING節は、select_expressionにおいてどのフィールドの名前や エイリアス名でも指し示すことができます。 これは最後に適用され、クライアントにアイテムが送られる直前に実行されるので、 最適化されません。 WHERE節で書くべきものにHAVINGを用いてはいけません。 例えば、次のように書いてはいけません: 
        mysql> SELECT col_name FROM tbl_name HAVING col_name > 0;
        その代わりに、次のように書いてください: 
        mysql> SELECT col_name FROM tbl_name WHERE col_name > 0;
        MySQL バージョン 3.22.5以降では、次のようにクエリを記述することができます: 
        mysql> SELECT user,MAX(salary) FROM users
           GROUP BY user HAVING MAX(salary)>10;
        MySQLの古いバージョンでは、この代わりに次のように記述できます: 
        mysql> SELECT user,MAX(salary) AS sum FROM users
           GROUP BY user HAVING sum>10;
      • The options DISTINCT, DISTINCTROW and ALL specify whether duplicate rows should be returned. The default is (ALL), all matching rows are returned. DISTINCT and DISTINCTROW are synonyms and specify that duplicate rows in the result set should be removed.
      • SQL_SMALL_RESULT, SQL_BIG_RESULT, SQL_BUFFER_RESULT, STRAIGHT_JOIN, HIGH_PRIORITY は ANSI SQL に対する MySQL 拡張です。
      • HIGH_PRIORITY は、テーブルの更新よりも SELECT を優先させます。 これは一度で完了する、とても速いクエリにのみ適用すべきです。 もしリードロックされているテーブルがあったとし、 たとえ update 文がこのテーブルの解除を待っていたとしても、 SELECT HIGH_PRIORITY クエリは実行されます。
      • SQL_BIG_RESULT は GROUP BY や DISTINCT と共に使用する 事ができ、結果セットが多くのレコードを持つことをオプティマイザに知らせます。 この場合、必要なら MySQL はディスクベースの一時テーブルを直接使用 します。MySQL はこの場合、GROUP BY 要素上のキーで一時テーブ ルを行なう代わりにソートを行なうことを選択します。
      • SQL_BUFFER_RESULT は結果を一時テーブルへ強制的に置きます。これは MySQL がテーブルロックを速く解放して、クライアントに結果セットを 送るために長い時間が掛かる場合の助けになります。
      • SQL_CALC_FOUND_ROWS (version 4.0.0 and up) tells MySQL to calculate how many rows there would be in the result set, disregarding any LIMIT clause. The number of rows can then be retrieved with SELECT FOUND_ROWS(). 「6.3.6.2 その他の関数」節参照. Please note that in versions prior to 4.1.0 this does not work with LIMIT 0, which is optimised to return instantly (resulting in a row count of 0). 「5.2.8 MySQL はどのように LIMIT を最適化するか？」節参照.
      • SQL_CACHE tells MySQL to store the query result in the query cache if you are using QUERY_CACHE_TYPE=2 (DEMAND). 「6.9 MySQL Query Cache (4.0.1以上)」節参照.
      • SQL_NO_CACHE tells MySQL to not allow the query result to be stored in the query cache. 「6.9 MySQL Query Cache (4.0.1以上)」節参照.
      • SQL_SMALL_RESULT (MySQL 固有のオプション) は GROUP BY か DISTINCT と共に使用する事ができ、 結果セットが小さくなることをオプティマイザに知らせます。この場合、 MySQL はソートする代わりに、速い一時テーブルを結果の保存のた めに使用します。 MySQL バージョン 3.23 では、これは通常必要ではありません。
      • GROUP BY を使用する場合、GROUP BY 内のすべてのフィールドを ORDER BY に記述したかのように、出力レコードは GROUP BY に従っ てソートされます。MySQL は、ASC と DESC を GROUP BY に記述できるように、GROUP BY を拡張しています: 
        SELECT a,COUNT(b) FROM test_table GROUP BY a DESC
      • MySQL は、GROUP BY 節に記述されていないフィールドを select できるように GROUP BY の使用を拡張しています。あなたのクエリ から期待した結果を得ない場合、GROUP BY の説明を読んでください。 「6.3.6.3 Functions for Use with GROUP BY Clauses」節参照.
      • STRAIGHT_JOINは、FROM節にて記述されたテーブルの順序に従って結合するよう、 オプティマイザに強制します。オプティマイザが、テーブルを最適な順序で結合しない 場合に、クエリのスピードアップのためにこれを使用することが可能です。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.
      • LIMIT 節は、 SELECT 構文で返されるレコード数を指定するのに 使用されます。 LIMIT は一つか二つの数字の引数を取ります。 引数が2つ与えられたならば、最初の引数は最初のレコードからのオフセットを示し、 2つめの引数は返すレコードの最大数を示します。 初めのレコードのオフセットは0です(1ではありません)。 To be compatible with PostgreSQL MySQL also supports the syntax: LIMIT # OFFSET #. 
        mysql> SELECT * FROM table LIMIT 5,10;  # 6〜15行目を返す
        To retrieve all rows from a certain offset upto the end of the result set, you can use -1 for the second parameter: 
        mysql> SELECT * FROM table LIMIT 95,-1; # Retrieve rows 96-last.
        もし引数が一つなら、返すべきレコードの最大行数を指定したことになります。 
        mysql> SELECT * FROM table LIMIT 5;     # 最初の5行を取り出す
        いいかえれば、LIMIT n は LIMIT 0,n と同じです。
      • SELECTの書式、SELECT ... INTO OUTFILE 'file_name'は、 選択されたレコードをファイルに書き込みます。 ファイルはサーバ機に作成され、既に存在するファイルであってはなりません (`/etc/passwd'のようなファイルの破壊を防止します)。 SELECT ... INTO OUTFILE は主に、サーバマシン上でとても速くテーブル をダンプすることを意図されています。サーバホストでない別のホスト上で結果ファ イルを生成したい場合は、SELECT ... INTO OUTFILE を使用できません。 この場合は代わりに、mysqldump --tab や mysql -e "SELECT ..." > outfile のようなクライアントプログラムを使用して、ファイルを生成す べきです。 SELECT ... INTO OUTFILEは、LOAD DATA INFILEの逆です。 export_optionsの構文は、LOAD DATA INFILEステートメントの一部で 使われるFIELDS節やLINES節と同じような構成です。 「6.4.9 LOAD DATA INFILE 構文」節参照. 結果として取り出されるテキストファイルでは、 以下に示す文字が ESCAPED BY 指定の文字によってエスケープされます：
        • ESCAPED BY 文字自身
        • FIELDS TERMINATED BY の最初の文字
        • LINES TERMINATED BY の最初の文字
        さらに、 ASCII 0 は、ESCAPED BY 0 (ASCII 48) にコンバートされます。 いかなる FIELDS TERMINATED BY, ESCAPED BY, LINES TERMINATED BY 指定されている文字も、エスケープしなければならない理由は、 テキストファイルを読み返せれるようにするためなのです。 ASCII 0 はいくつかのページャーでも見れるようにするために エスケープされるのです。 結果のファイルは SQL の文を含んでいないので、何もエスケープする必要はありません。 次は、多くの古いプログラムによって使用されるフォーマットでファイルを得る例 です。 
        SELECT a,b,a+b INTO OUTFILE "/tmp/result.text"
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
LINES TERMINATED BY "\n"
FROM test_table;
      • INTO OUTFILE の代わりに INTO DUMPFILE を使用すると、 MySQL はファイルに１レコードだけを書きます。フィールドや行の終端 とすべてのエスケープを含みません。これはファイル内に BLOB を格納したい場合 に便利です。
      • Note that any file created by INTO OUTFILE and INTO DUMPFILE is going to be writeable for all users! The reason is that the MySQL server can't create a file that is owned by anyone else than the user it's running as (you should never run mysqld as root), the file has to be world-writeable so that you can manipulate it.
      • ページ／レコードロックとともに ストレ-ジ・エンジン 上で FOR UPDATE を使 用すると、検査されるレコードは書き込みロックされます。

      6.4.1.1 JOIN 構文

      MySQLは、以下に示すSELECTステートメントにおけるJOIN構文をサポートします: 

      table_reference, table_reference
table_reference [CROSS] JOIN table_reference
table_reference INNER JOIN table_reference join_condition
table_reference STRAIGHT_JOIN table_reference
table_reference LEFT [OUTER] JOIN table_reference join_condition
table_reference LEFT [OUTER] JOIN table_reference
table_reference NATURAL [LEFT [OUTER]] JOIN table_reference
{ OJ table_reference LEFT OUTER JOIN table_reference ON conditional_expr }
table_reference RIGHT [OUTER] JOIN table_reference join_condition
table_reference RIGHT [OUTER] JOIN table_reference
table_reference NATURAL [RIGHT [OUTER]] JOIN table_reference

      Where table_reference is defined as: 

      table_name [[AS] alias] [[USE INDEX (key_list)] | [IGNORE INDEX (key_list)] | [FORCE INDEX (key_list)]]

      and join_condition is defined as: 

      ON conditional_expr |
USING (column_list)

      You should generally not have any conditions in the ON part that are used to restrict which rows you have in the result set (there are exceptions to this rule). If you want to restrict which rows should be in the result, you have to do this in the WHERE clause.

      注意: 3.23.17 より前のバージョンでは、INNER JOIN は join_condition を取りません！

      上に示す最後のLEFT OUTER JOIN構文は、ODBCとの互換性のためだけに存在します:

      • table referenceは、tbl_name AS alias_nameやtblname alias_nameに よる別名を指定することができます: 
        mysql> SELECT t1.name, t2.salary FROM employee AS t1, info AS t2
    ->        WHERE t1.name = t2.name;
      • INNER JOINと, (コンマ)は、同義語です。どちらも使用される テーブル間の直積をとります。通常はWHERE条件にて、テーブルがどのように リンクされるべきかを定義します。
      • ON条件節は、WHERE節で使用されるような条件文の書式です。
      • もし、LEFT JOIN の ON や USING において 右側のテーブルにマッチするレコードが無かった場合、 全てのフィールドがNULLである1つのレコードが、右側のテーブルとして使用されます。 この事実は、あるテーブルについて、他のテーブルに対応するレコードが存在しない レコードを探すということに利用できます: 
        mysql> SELECT table1.* FROM table1
    ->        LEFT JOIN table2 ON table1.id=table2.id
    ->        WHERE table2.id IS NULL;
        この例は、table1の内、idの値がtable2に存在しない全ての レコードを検索します。 (即ち、table2内のレコードと一致しないtable1の全てのレコード。) もちろん、この場合のtable2.idは、NOT NULLと定義されているもの と仮定します。 「5.2.6 MySQL はどのように LEFT JOIN と RIGHT JOIN を最適化するか？」節参照.
      • USING (column_list)節のフィールド名リストは、両方のテーブルに 存在しなければなりません。USING節が次のように: 
        A LEFT JOIN B USING (C1,C2,C3,...)
        定義されることは、ON式がこのように定義されるのと同義です: 
        A.C1=B.C1 AND A.C2=B.C2 AND A.C3=B.C3,...
      • 同じフィールド名を持つ2つのテーブルの NATURAL [LEFT] JOIN は、 USING 節を伴った INNER JOIN や LEFT JOIN と 同じとして定義されます。
      • INNER JOIN and , (comma) are semantically equivalent. Both do a full join between the tables used. Normally, you specify how the tables should be linked in the WHERE condition.
      • RIGHT JOIN works analogously as LEFT JOIN. To keep code portable across databases, it's recommended to use LEFT JOIN instead of RIGHT JOIN.
      • STRAIGHT_JOINは、右側のテーブルの前に、常に左側のテーブルを読むことを 除けば、JOINと全く同じことです。これは、結合オプティマイザが、不当な 順序でテーブルを出力するようなまれな事態に使用できます。
      • MySQL バージョン 3.23.12 から、テーブルから情報を取り出す時に、 MySQL がどのインデックスを使用すべきかというヒントを与えることが できるようになりました。これは、MySQL が間違ったインデックスを使 用していることを EXPLAIN が示す場合に有用です。USE INDEX (key_list) を指定することによって、テーブルからレコードを見つけるために、 指定されたインデックスの一つだけを使用するように MySQL に伝えるこ とができます。別の構文 IGNORE INDEX (key_list) は、MySQL に特定のインデックスを使用しないように伝えるために使用できます。 In MySQL 4.0.9 you can also use FORCE INDEX. This acts likes USE INDEX (key_list) but with the addition that a table scan is assumed to be VERY expensive. In other words a table scan will only be used if there is no way to use one of the given index to find rows in the table. USE/IGNORE KEY are synonyms for USE/IGNORE INDEX.

      例: 

      mysql> SELECT * FROM table1,table2 WHERE table1.id=table2.id;
mysql> SELECT * FROM table1 LEFT JOIN table2 ON table1.id=table2.id;
mysql> SELECT * FROM table1 LEFT JOIN table2 USING (id);
mysql> SELECT * FROM table1 LEFT JOIN table2 ON table1.id=table2.id
    ->          LEFT JOIN table3 ON table2.id=table3.id;
mysql> SELECT * FROM table1 USE INDEX (key1,key2)
    ->          WHERE key1=1 AND key2=2 AND key3=3;
mysql> SELECT * FROM table1 IGNORE INDEX (key3)
    ->          WHERE key1=1 AND key2=2 AND key3=3;

      「5.2.6 MySQL はどのように LEFT JOIN と RIGHT JOIN を最適化するか？」節参照.

      6.4.1.2 UNION Syntax

      SELECT ...
UNION [ALL]
SELECT ...
  [UNION
   SELECT ...]

      UNION is implemented in MySQL 4.0.0.

      UNION is used to combine the result from many SELECT statements into one result set.

      The columns listed in the select_expression portion of the SELECT should have the same type. The column names used in the first SELECT query will be used as the column names for the results returned.

      The SELECT commands are normal select commands, but with the following restrictions:

      • Only the last SELECT command can have INTO OUTFILE.

      If you don't use the keyword ALL for the UNION, all returned rows will be unique, as if you had done a DISTINCT for the total result set. If you specify ALL, then you will get all matching rows from all the used SELECT statements.

      If you want to use an ORDER BY for the total UNION result, you should use parentheses: 

      (SELECT a FROM table_name WHERE a=10 AND B=1 ORDER BY a LIMIT 10)
UNION
(SELECT a FROM table_name WHERE a=11 AND B=2 ORDER BY a LIMIT 10)
ORDER BY a;

      6.4.2 HANDLER Syntax

      HANDLER tbl_name OPEN [ AS alias ]
HANDLER tbl_name READ index_name { = | >= | <= | < } (value1,value2,...)
    [ WHERE ... ] [LIMIT ... ]
HANDLER tbl_name READ index_name { FIRST | NEXT | PREV | LAST }
    [ WHERE ... ] [LIMIT ... ]
HANDLER tbl_name READ { FIRST | NEXT }
    [ WHERE ... ] [LIMIT ... ]
HANDLER tbl_name CLOSE

      The HANDLER statement provides direct access to the MyISAM table storage engine interface.

      The first form of HANDLER statement opens a table, making it accessible via subsequent HANDLER ... READ statements. This table object is not shared by other threads and will not be closed until the thread calls HANDLER tbl_name CLOSE or the thread dies.

      The second form fetches one row (or more, specified by LIMIT clause) where the index specified complies to the condition and WHERE condition is met. If the index consists of several parts (spans over several columns) the values are specified in comma-separated list, providing values only for few first columns is possible.

      The third form fetches one row (or more, specified by LIMIT clause) from the table in index order, matching WHERE condition.

      The fourth form (without index specification) fetches one row (or more, specified by LIMIT clause) from the table in natural row order (as stored in datafile) matching WHERE condition. It is faster than HANDLER tbl_name READ index_name when a full table scan is desired.

      HANDLER ... CLOSE closes a table that was opened with HANDLER ... OPEN.

      HANDLER is a somewhat low-level statement. For example, it does not provide consistency. That is, HANDLER ... OPEN does NOT take a snapshot of the table, and does NOT lock the table. This means that after a HANDLER ... OPEN is issued, table data can be modified (by this or any other thread) and these modifications may appear only partially in HANDLER ... NEXT or HANDLER ... PREV scans.

      The reasons to use this interface instead of normal SQL are:

      • It's faster than SELECT because:
        • A designated storage engine is allocated for the thread in HANDLER OPEN.
        • There is less parsing involved.
        • No optimiser and no query checking overhead.
        • The used table doesn't have to be locked between two handler requests.
        • The handler interface doesn't have to provide a consistent look of the data (for example, dirty-reads are allowed), so the storage engine can do optimisations that SQL doesn't normally allow.
      • It makes it much easier to port applications that uses an ISAM like interface to MySQL.
      • It allows one to traverse a database in a manner that is not easy (in some case impossible) to do with SQL. The handler interface is more natural way to look at data when working with applications that provide an interactive user interfaces to the database.

      6.4.3 INSERT 構文

          INSERT [LOW_PRIORITY | DELAYED] [IGNORE]
        [INTO] tbl_name [(col_name,...)]
        VALUES ((expression | DEFAULT),...),(...),...
        [ ON DUPLICATE KEY UPDATE col_name=expression, ... ]
or  INSERT [LOW_PRIORITY | DELAYED] [IGNORE]
        [INTO] tbl_name [(col_name,...)]
        SELECT ...
or  INSERT [LOW_PRIORITY | DELAYED] [IGNORE]
        [INTO] tbl_name
        SET col_name=(expression | DEFAULT), ...
        [ ON DUPLICATE KEY UPDATE col_name=expression, ... ]

      INSERTは、既存のテーブルに新しいレコードを挿入します。 INSERT ... VALUES書式は、値の明示指定を基本としてレコードを挿入します。 INSERT ... SELECT書式は、他の表(複数可)から抽出したレコードを挿入します。 複数の値リストを用いるINSERT ... VALUES書式は、 MySQL バージョン 3.22.5以降でサポートされています。 col_name=expression構文は、 MySQL バージョン 3.22.10以降でサポートされています。

      tbl_nameは、レコードを挿入するテーブルです。フィールド名リストは、 後続の値定義ステートメントのフィールドを指し示します:

      • もしいかなるフィールドも INSERT ... VALUES や INSERT ... SELECT などで明示しなければ、全てのフィールドの値が VALUES() の中に与えられ なくてはなりません。テーブル内のフィールド順が不明な場合、 これを調べるためにDESCRIBE tbl_nameを使用して下さい。
      • テーブル内の一部のフィールドしか指定しない場合、指定されなかったフィールドには、 それぞれの初期値が指定されます。初期値の割当ては、 「6.5.3 CREATE TABLE 構文」節. で述べられています。 You can also use the keyword DEFAULT to set a column to its default value. (New in MySQL 4.0.3.) This makes it easier to write INSERT statements that assign values to all but a few columns, because it allows you to avoid writing an incomplete VALUES() list (a list that does not include a value for each column in the table). Otherwise, you would have to write out the list of column names corresponding to each value in the VALUES() list. MySQL always has a default value for all fields. This is something that is imposed on MySQL to be able to work with both transactional and not transactional tables. Our view is that checking of fields content should be done in the application and not in the database server.
      • expressionは、値リスト内で先頭に近い方のフィールドを参照しなければなりません。 例えば、次のように記述できます: 
        mysql> INSERT INTO tbl_name (col1,col2) VALUES(15,col1*2);
        しかし、次のようには記述できません: 
        mysql> INSERT INTO tbl_name (col1,col2) VALUES(col2*2,15);
      • キーワードLOW_PRIORITYを指定した場合、INSERTの実行はそのテー ブルから値を読み込むクライアントがいなくなるまで遅らされます。この場合、ク ライアントは insert 文が完了するまで待たされます。テーブルが頻繁に使用され る場合、長い時間かかります。これはクライアントを一度に継続させる INSERT DELAYED と対称的です。 「6.4.4 INSERT DELAYED 構文」節参照. Note that LOW_PRIORITY should normally not be used with MyISAM tables as this disables concurrent inserts. 「7.1 MyISAM テーブル (3.23.0以上)」節参照.
      • もし IGNORE キーワードを INSERT に 値とともに 与えるなら、 テーブル内の PRIMARY や UNIQUE キーにすでに存在する重複した ものは無視され、挿入されません。 多重行の値を含むレコードの INSERT にキーワード IGNORE を 指定しない場合、テーブルの PRIMARY キーや UNIQUE キーに 重複が起こる際に、挿入処理が異常終了します。 IGNORE を指定した場合、重複するキー値を持つレコードは挿入されません。 C API 関数 mysql_info() により、テーブルにいくつのレコードが挿入 されたかチェックすることができます。
      • If you specify ON DUPLICATE KEY UPDATE clause (new in MySQL 4.1.0), and a row is inserted that would cause a duplicate value in PRIMARY or UNIQUE key, an UPDATE of the old row is performed. For example, the command: 
        mysql> INSERT INTO table (a,b,c) VALUES (1,2,3)
   --> ON DUPLICATE KEY UPDATE c=c+1;
        in case of column a is declared as UNIQUE and already holds 1 once, would be identical to the 
        mysql> UPDATE table SET c=c+1 WHERE a=1;
        Note: that if column b is unique too, the UPDATE command would be written as 
        mysql> UPDATE table SET c=c+1 WHERE a=1 OR b=2 LIMIT 1;
        and if a=1 OR b=2 matches several rows, only one row will be updated! In general, one should try to avoid using ON DUPLICATE KEY clause on tables with multiple UNIQUE keys. When one uses ON DUPLICATE KEY UPDATE, the DELAYED option is ignored.
      • MySQLが、DONT_USE_DEFAULT_FIELDSオプションにより制限されていた 場合、NULL値を許さない全てのフィールドに明示的に値をしないと INSERTステートメントは、エラーを生成します。 「2.3.3 典型的な configure オプション」節参照.
      • mysql_insert_id 関数で AUTO_INCREMENT フィールドに使用された 値を見つけることができます。 「8.4.3.130 mysql_insert_id()」節参照.

      多重の値リストを持つ INSERT ... SELECT ... 又は INSERT ... VALUES() ステートメントを使用する場合、クエリーに関する情報を得るために C API関数 mysql_info() を使用することができます。 その情報の書式は以下に示す文字列のようになります: 

      Records: 100 Duplicates: 0 Warnings: 0

      Duplicatesは、既に存在するユニークインデックスの値と重複することにより、 挿入できなかったレコード数を表します。 Warningsは、挿入されたフィールドが何らかの疑わしい値であったという 数を表します。警告は、次のような条件の下で発生します:

      • NOT NULL定義されたフィールドへのNULLの挿入。フィールドには 初期値が設定されます。
      • 数値フィールドの範囲を超える値のセット。値は範囲内の限界値に補正されます。
      • 数値フィールドへの `10.34 a' のような値のセット。引きずっている ゴミは取り除かれ、残りの数値部分が挿入されます。 値が数値として判断できなかった場合、フィールドには 0 がセットされます。
      • CHAR、VARCHAR、VARCHAR、TEXT又はBLOB フィールドへの最大長を超える文字列の挿入。値はフィールドの最大長に切り捨てられます。
      • 日付又は時刻フィールドへのフィールド属性に反した挿入。その属性に適した ``ゼロ''値がセットされます。

      6.4.3.1 INSERT ... SELECT 構文

      INSERT [LOW_PRIORITY] [IGNORE] [INTO] tbl_name [(column list)] SELECT ...

      With INSERT ... SELECT statement you can quickly insert many rows into a table from one or many tables. 

      INSERT INTO tblTemp2 (fldID) SELECT tblTemp1.fldOrder_ID FROM tblTemp1 WHERE
tblTemp1.fldOrder_ID > 100;

      The following conditions hold for an INSERT ... SELECT statement:

      • The target table of the INSERT statement cannot appear in the FROM clause of the SELECT part of the query because it's forbidden in ANSI SQL to SELECT from the same table into which you are inserting. (The problem is that the SELECT possibly would find records that were inserted earlier during the same run. When using subquery clauses, the situation could easily be very confusing!)
      • AUTO_INCREMENT columns work as usual.
      • You can use the C API function mysql_info() to get information about the query. 「6.4.3 INSERT 構文」節参照.
      • To ensure that the update log/binary log can be used to re-create the original tables, MySQL will not allow concurrent inserts during INSERT ... SELECT.

      You can of course also use REPLACE instead of INSERT to overwrite old rows.

      6.4.4 INSERT DELAYED 構文

      INSERT DELAYED ...

      INSERT 構文の DELAYED オプションは MySQL 独自の オプションで、これは INSERT が完全に終了することを待てない クライアントを持つ場合に、とても役立ちます。 これは、ロギングのために MySQL を使用する時の一般的な問題で、完了 に長い時間がかかる SELECT ステートメントも定期的に実行できます。 DELAYED は MySQL 3.22.15 で導入されました。 これは ANSI SQL92 に対する MySQL 拡張です。

      INSERT DELAYED only works with ISAM and MyISAM tables. Note that as MyISAM tables supports concurrent SELECT and INSERT, if there is no free blocks in the middle of the datafile, you very seldom need to use INSERT DELAYED with MyISAM. 「7.1 MyISAM テーブル (3.23.0以上)」節参照.

      INSERT DELAYED を使用する時、クライアントは一度 ok となり、テーブル が他のスレッドで使用中でない時にレコードが挿入されます。

      INSERT DELAYED を使用して得られるほかの利益は、 多くのクライアントからの insert が同時に束ねられ、一つのブロックで 書かれることです。 これは多くの別々の insert を実行するより とても速くなります。

      現在、キューイングされたレコードは、それらがテーブルに代入されるまで メモリーに保持されているだけです。 これは、もし mysqld を 強引な方法 (kill -9) でキルしたり、 mysqld が予期せず 死んだ場合、キューイングされているレコードはディスクに書かれず失われます！

      DELAYED オプションを INSERT や REPLACE で使用する場合、 以下のことがおきます。 ここで ``スレッド'' とは INSERT DELAYED コマンドを受けたスレッドをさし、 ``ハンドラー'' とは特定のテーブルのための全ての INSERT DELAYED 構文を操作するスレッドを指します。

      • スレッドがあるテーブルに対し DELAYED 構文を実行するとき、 そのテーブルに対する全ての DELAYED 構文 を処理するためにハンドラースレッドが作成されます。 もしそのようなハンドラーが存在していない場合には。
      • そのスレッドは、そのハンドラーが DELAYED ロックを既に持っているか どうかをチェックします； もし持っていないなら、そうするように ハンドラーに告げます。 たとえ他のスレッドが READ か WRITE ロックをそのテーブルに 持っていたとしても、 DELAYED ロックを得ることができます。 しかし、そのハンドラーは全ての ALTER TABLE ロックか FLUSH TABLES を待ちます。 そのテーブル構造が最新であるのを 確実にするために。
      • スレッドは INSERT ステートメントを実行しますが、レコードをテーブル に書く代わりに、ハンドラスレッドによって管理されるキューに最後のレコードの コピーを置きます。文法エラーはスレッドによって通知され、クライアントプログ ラムに報告されます。
      • クライアントは結果行の重複数や AUTO_INCREMENT の値を 報告できません； それはサーバーから得ることができません。 なぜなら、 INSERT はインサートオペレーションが完全に終了する前に 返るからです。 もし C API を使用しているなら、 mysql_info() 関数は 同様の理由によりなにも返しません。
      • 更新ログは、レコードがそのテーブルに insert されたとき、そのハンドラースレッド によって更新されます。 複数レコードの挿入の場合、 更新ログは最初の行が 挿入されたときに更新されます。
      • それぞれの delayed_insert_limit レコードが書かれた後、そのハンドラーは いかなる SELECT 文もまだ延期されていないかを確認します。 もしそうなら、続ける前にこれらに対して実行を可能にします。
      • ハンドラーのキュー内にレコードがなくなったとき、テーブルはアンロックされます。 もし新しい INSERT DELAYED コマンドが delayed_insert_timeout 秒以内に 受け付けられなければ、ハンドラーは終了します。
      • もし、特定のハンドラーのキュー内に delayed_queue_size 以上のレコードが 既に延期されているならば、そのスレッドは、キューに余裕がある間待ちます。 これは mysqld サーバーが delayed されたキューに全ての メモリーを確実に使用しないようにするのに役立ちます。
      • そのハンドラースレッドは MySQL プロセスリストの Command 項 内に、 delayed_insert と共に表示されます。 これは FLUSH TABLES コマンドか KILL thread_id を実行することで、 kill できるでしょう。 しかし、これらは、終了する前に、キュー内の全てのレコードをテーブルに 保存しようとします。 この間、このスレッドは、他のスレッドから来たいかなる 新しい INSERT コマンドも受け付けません。 もし、この後に INSERT DELAYED コマンドを実行するなら、 新しいハンドラースレッドが作成されます。 上記のことは、もし INSERT DELAYED コマンドが既に走っているなら、 INSERT DELAYED コマンドは、普通の INSERT コマンドよりも高い 優先度を持つということです！ 他の update コマンドは INSERT DELAY キューが空になるまで、 あるいは誰かが KILL thread_id や FLUSH TABLES を実行して ハンドラーをキルするまで、 待たされます。
      • 以下のステータス変数は INSERT DELAYED コマンドについての情報を 与えます：
        Variable Meaning
        Delayed_insert_threads ハンドラースレッドの数
        Delayed_writes INSERT DELAYED で書かれるレコード数
        Not_flushed_delayed_rows 書き込みを待つレコード数
        これらの変数は SHOW STATUS 構文を発行したり mysqladmin extended-status コマンドを実行することで見れます.

      注意: INSERT DELAYED は、テーブルが使用中でない場合、通常の INSERT よりも遅くなります。INSERT DELAYED を使用する各テーブルにつ いて別のスレッドを操作するサーバの、追加のオーバーヘッドもあります。これは、 確実にそれを必要とする時にだけ INSERT DELAYED を使用すべきことを意 味します！

      6.4.5 UPDATE 構文

      UPDATE [LOW_PRIORITY] [IGNORE] tbl_name
    SET col_name1=expr1 [, col_name2=expr2 ...]
    [WHERE where_definition]
    [ORDER BY ...]
    [LIMIT rows]

or

UPDATE [LOW_PRIORITY] [IGNORE] tbl_name [, tbl_name ...]
    SET col_name1=expr1 [, col_name2=expr2 ...]
    [WHERE where_definition]

      UPDATE はテーブルに存在するレコードのフィールドを、新しい値に更新します。 SET 節はどのフィールドをどういった値にすべきかを示します。 WHERE 節が与えられた場合、更新すべきレコードを特定することになります。 それ以外は、全てのレコードを更新します。 ORDER BY 節が指定された場合、レコードは指定された順に更新されます。

      LOW_PRIORITY キーワードを指定した場合、UPDATE の実行は、 テーブルを読んでいるクライアントがなくなるまで、遅らされます。

      IGNORE キーワードを指定した場合は、update 文は、 update 中に二重キーのエラーを得たとしても、異常終了しません。 衝突を引き起こすレコードは更新されません。

      表記中の tbl_name からのフィールドをアクセスすると、UPDATE は現在のフィールド値を使用します。例えば、次のステートメントは age フィールドにその現在値より１大きい値を設定します: 

      mysql> UPDATE persondata SET age=age+1;

      UPDATE は左から右に評価されます。例えば、以下の文は age フィールド を 2倍にし、そのあと1増やします： 

      mysql> UPDATE persondata SET age=age*2, age=age+1;

      もしフィールドに現在もっている値を指定した場合、MySQL はそれを通知し、 値は更新しません。

      UPDATE は変更されたレコード数を返します。 MySQL バージョン 3.22 以上では、C API 関数 mysql_info() が マッチし更新されたレコード数を返します。また UPDATE 中に起きた ワーニングの数も返します。

      MySQL バージョン 3.23 では、 LIMIT # で指定した数だけレコードを 変更できます。

      Starting with MySQL Version 4.0.4, you can also perform UPDATE operations that cover multiple tables: 

      UPDATE items,month SET items.price=month.price
WHERE items.id=month.id;

      Note: you can not use ORDER BY or LIMIT with multi-table UPDATE.

      6.4.6 DELETE 構文

      DELETE [LOW_PRIORITY] [QUICK] FROM table_name
       [WHERE where_definition]
       [ORDER BY ...]
       [LIMIT rows]

or

DELETE [LOW_PRIORITY] [QUICK] table_name[.*] [, table_name[.*] ...]
       FROM table-references
       [WHERE where_definition]

or

DELETE [LOW_PRIORITY] [QUICK]
       FROM table_name[.*] [, table_name[.*] ...]
       USING table-references
       [WHERE where_definition]

      DELETEは、tbl_nameより、where_definitionにて与えられた条件 を満たすレコードを削除し、削除されたレコード数を返します。

      WHERE節を指定することなしにDELETEを発行した場合、全てのレコードが 削除されます。 もし AUTOCOMMIT モードでこの操作を実行するならば、これは TRUNCATE と同様に動作します。 「6.4.7 TRUNCATE 構文」節参照. MySQL 3.23では、DELETE は削除したレコード数を 0 で返します。

      もし全てのレコードを削除している時に、いくつのレコードが消され、いくつのレコード が スピードを犠牲にしているのか、本当に知りたいならば、 DELETE 構文を以下のように使用します： 

      mysql> DELETE FROM tbl_name WHERE 1>0;

      これは DELETE FROM tbl_name を WHERE 節なしで行うよりも、 とても遅いです。なぜなら一度で消そうとするからです。

      キーワードLOW_PRIORITYを指定した場合、そのテーブルを読んでいるクライアン トがいなくなるまでDELETEの実行は遅らせられます。

      削除されたレコードはリンクリストで維持され、次のINSERT操作は、古いレコー ド位置を再利用します。 ファイルをより小さくしたい場合は、OPTIMIZE TABLEステートメントかテーブル の再編成のためにmyisamchkユティリティを使用してください。 OPTIMIZE TABLEの方が簡単ですが、myisamchkの方が早く動作します。 「4.5.1 OPTIMIZE TABLE 構文」節参照.

      If you specify the word QUICK then the storage engine will not merge index leaves during delete, which may speed up certain kind of deletes.

      The first multi-table delete format is supported starting from MySQL 4.0.0. The second multi-table delete format is supported starting from MySQL 4.0.2.

      The idea is that only matching rows from the tables listed before the FROM or before the USING clause are deleted. The effect is that you can delete rows from many tables at the same time and also have additional tables that are used for searching.

      The .* after the table names is there just to be compatible with Access: 

      DELETE t1,t2 FROM t1,t2,t3 WHERE t1.id=t2.id AND t2.id=t3.id

or

DELETE FROM t1,t2 USING t1,t2,t3 WHERE t1.id=t2.id AND t2.id=t3.id

      In the above case we delete matching rows just from tables t1 and t2.

      If an ORDER BY clause is used (available from MySQL 4.0), the rows will be deleted in that order. This is really only useful in conjunction with LIMIT. For example: 

      DELETE FROM somelog
WHERE user = 'jcole'
ORDER BY timestamp
LIMIT 1

      This will delete the oldest entry (by timestamp) where the row matches the WHERE clause.

      MySQL-特化 DELETE の LIMIT rows オプションは サーバーに消す最大のレコード数をつげます。これは DELETE コマンドが あまりに多くの時間を取らないために使用されます。 LIMIT 値よりも affected row の数が少なくなるまで、 単純に DELETE コマンドを繰り返すだけです。

      From MySQL 4.0, you can specify multiple tables in the DELETE statement to delete rows from one table depending on a particular condition in multiple tables. However, you can not use ORDER BY or LIMIT in a multi-table DELETE.

      6.4.7 TRUNCATE 構文

      TRUNCATE TABLE table_name

      3.23 では、COMMIT ; DELETE FROM table_name と同じことです。 「6.4.6 DELETE 構文」節参照.

      TRUNCATE TABLE differs from DELETE FROM ... in the following ways:

      • Truncate はテーブルを破棄して再生成するように実装されています。これは多くのレコードを 削除する時により速くなります。
      • トランザクション安全ではありません; COMMIT が呼ばれたかのように TRUNCATE TABLE は自動的に現在のトランザクションを終了します。
      • 削除したレコード数を返しません。
      • テーブル定義ファイル `table_name.frm' が正しい限り、たとえ、データや インデックスファイルが汚れても、テーブルはこの方法で再生成できます。

      TRUNCATE は ORACLE SQL 拡張です。

      6.4.8 REPLACE 構文

          REPLACE [LOW_PRIORITY | DELAYED]
        [INTO] tbl_name [(col_name,...)]
        VALUES (expression,...),(...),...
or  REPLACE [LOW_PRIORITY | DELAYED]
        [INTO] tbl_name [(col_name,...)]
        SELECT ...
or  REPLACE [LOW_PRIORITY | DELAYED]
        [INTO] tbl_name
        SET col_name=expression, col_name=expression,...

      REPLACEは、テーブル中にある古いレコードの UNIQUE インデックスか PRIMARY KEY 上にある値が、新しいレコード と同じ場合に、新しいレコードを挿入する前に 古いレコードを削除するということを除けば、INSERTと全く同じように 動作します。 「6.4.3 INSERT 構文」節参照.

      In other words, you can't access the values of the old row from a REPLACE statement. In some old MySQL versions it appeared that you could do this, but that was a bug that has been corrected.

      To be able to use REPLACE you must have INSERT and DELETE privileges for the table.

      When you use a REPLACE command, mysql_affected_rows() will return 2 if the new row replaced an old row. This is because one row was inserted after the duplicate was deleted.

      This fact makes it easy to determine whether REPLACE added or replaced a row: check whether the affected-rows value is 1 (added) or 2 (replaced).

      Note that unless you use a UNIQUE index or PRIMARY KEY, using a REPLACE command makes no sense, since it would just do an INSERT.

      6.4.9 LOAD DATA INFILE 構文

      LOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE 'file_name.txt'
    [REPLACE | IGNORE]
    INTO TABLE tbl_name
    [FIELDS
        [TERMINATED BY '\t']
        [[OPTIONALLY] ENCLOSED BY '']
        [ESCAPED BY '\\' ]
    ]
    [LINES TERMINATED BY '\n']
    [IGNORE number LINES]
    [(col_name,...)]

      LOAD DATA INFILEステートメントは、テキストファイルからテーブルへと、 レコードを高速に読み込みます。 LOCAL キーワードが指定されれば、ファイルは クライアント・ホストから読み込まれます。 LOCALが指定されなければ、ファイルはサーバに位置する必要があります (LOCALは、MySQL バージョン 3.22.6以降で利用できます)。

      セキュリティ上の理由から、サーバからテキストファイルを読み出す時は、 ファイルがデータベースディレクトリに存在するか、 全てに読み込み権限がある必要があります。 また、サーバファイルで LOAD DATA INFILE を使用するには、 データベースの FILE 権限も持たなければなりません。 「4.2.7 MySQL が提供する権限」節参照.

      In MySQL 3.23.49 and MySQL 4.0.2 LOCAL will only work if you have not started mysqld with --local-infile=0 or if you have not enabled your client to support LOCAL. 「4.2.4 Security issues with LOAD DATA LOCAL」節参照.

      もし LOW_PRIORITY を指定した場合、LOAD DATA 構文は そのテーブルから他のクライアントが読み込みを行っている間、 遅らされます。

      If you specify the keyword CONCURRENT with a MyISAM table, then other threads can retrieve data from the table while LOAD DATA is executing. Using this option will of course affect the performance of LOAD DATA a bit even if no other thread is using the table at the same time.

      LOCAL 使用をすると、クライアント・ホストからサーバ・ホストへ ファイルの内容が転送される分、多少遅くなるでしょう。 いうならば、ローカルのファイルを読み込むのに、 FILE 権限は必要ないということです。

      If you are using MySQL before Version 3.23.24 you can't read from a FIFO with LOAD DATA INFILE. If you need to read from a FIFO (for example the output from gunzip), use LOAD DATA LOCAL INFILE instead.

      mysqlimportユティリティは、データファイルの読み込みに使用することができま す。; これは、サーバにLOAD DATA INFILEコマンドを送信することによって処理 を実現しています。 --localオプションは、mysqlimportに、クライアント・ホストからデータ ファイルを読み込ませます。 クライアントとサーバが圧縮プロトコルをサポートしていれば、低速なネットワークでよ り良いパフォーマンスを得るために、--compressオプションを指定することがで きます。

      サーバ・ホストにファイルを置く場合、サーバは、以下のルールを使用します:

      • 完全なパスでファイル名が与えられた場合、サーバはパス名をそのまま使用します。
      • １つ又は複数の構成要素から成る相対パスと共にファイル名が与えられた場合、サーバは 、サーバのデータディレクトリ以下からファイルを探します。
      • ファイル名だけが単に与えられた場合、サーバは、 カレントのデータベースディレクトリを探します。

      これらのルールは、ファイルが `myfile.txt' のように与えられれば データベースディレクトリからファイルが読み出され、 `./myfile.txt' のように与えられれば、現在選択しているデータベースのデータデ ィレクトリから ファイルが読み出されるという意味であることに注意して下さい。

      例えば、以下の LOAD DATA 文は、`data.txt' ファイルを db1 データベースディレクトリから読みます。 なぜなら、db1 は 現在選択されているデータベースだからです。 たとえ、db2 データベース のテーブルに、ファイルから読み込んだデータを挿入するとしても。：

      以下に示すような構文では、ファイルは db1 データベースディレクトリ から読まれます。db2 ではありません: 

      mysql> USE db1;
mysql> LOAD DATA INFILE "data.txt" INTO TABLE db2.my_table;

      REPLACE と IGNORE キーワードは、すでに存在するユニークキーに 重複しているレコードの入力に対する制御です。 REPLACE 指定の場合、同じユニークキーを持つ既存のレコードは新しいレコード で置き換えられます。 IGNORE 指定の場合、既存のレコードのユニークキーと重複するキーをもつ新しい レコードは飛ばされます。 もし、どちらも指定しなかった場合、重複したキーが 見つかった場合エラーが発生し、テキストファイルは無視されます。

      LOCAL キーワードを使用してデータをローカルからロードする場合、 サーバーは操作の途中で転送をとめる方法を知りません。 それでデフォルトの動作としては IGNORE が指定されたのと 同じになります。

      If you use LOAD DATA INFILE on an empty MyISAM table, all non-unique indexes are created in a separate batch (like in REPAIR). This normally makes LOAD DATA INFILE much faster when you have many indexes.

      LOAD DATA INFILEは、SELECT ... INTO OUTFILEの逆です。 「6.4.1 SELECT 構文」節参照. データベースからファイルへデータを書き込むには、SELECT ... INTO OUTFILEを 使用します。 ファイルからデータベースに読み戻すには、LOAD DATA INFILEを使用します。 FIELDSとLINES節の構文は両方のコマンドとも同じです。 どちらの節もオプションですが、両方を指定する場合は、FIELDSは、LINES より先に指定しなければなりません。

      FIELDS節を指定した場合、その段落(TERMINATED BY、[OPTIONALLY] ENCLOSED BY及びESCAPED BY)は、少なくとも１つを指定しなければならないこ とを除いて、それらもまたオプションとなります。

      FIELDS節を指定しなかった場合、初期値は以下のように記述したのと等価となり ます: 

      FIELDS TERMINATED BY '\t' ENCLOSED BY '' ESCAPED BY '\\'

      LINES節を指定しなかった場合、初期値は以下のように記述したのと等価となりま す: 

      LINES TERMINATED BY '\n'

      言い換えると、LOAD DATA INFILE の初期値は、出力へ書き込む際に以下のように 振舞います:

      • 改行をレコードの境界とみなす
      • タブ文字によってフィールドを区切る
      • クォート文字でフィールドを囲んでいないものとする
      • タブ文字や改行文字及び`\'の前に`\'があることにより、それらをフィールド 値の一部のリテラル文字であるとして処理する。

      逆に、LOAD DATA INFILEの初期値は、入力を読み込む際に以下のように振舞いま す:

      • フィールド間にタブ文字を書く
      • いずれのクォート文字でもフィールドを囲まない
      • `\'の使用により、フィールド値の中で使用するタブ文字や改行文字、`\'をエ スケープする
      • レコードの終りに改行文字を書く

      FIELDS ESCAPED BY '\\'と書いた場合、単一のバックスラッシュとして読み出さ れる値とするために、２つのバックスラッシュを指定しなければならないことに注意して 下さい。

      IGNORE number LINES オプションはファイルの先頭にあるレコードを無視するの に使用されます： 

      mysql> LOAD DATA INFILE "/tmp/file_name" INTO TABLE test IGNORE 1 LINES;

      データベースからファイルへデータを書き、それから後でそのファイルからデータベース へデータを読み戻すために、SELECT ... INTO OUTFILEと対にLOAD DATA IN FILEを使う場合、双方のフィールドとレコードの取扱いに関するオプションは、一致し なければなりません。さもなければ、LOAD DATA INFILEは適切にファイルを処理 しないでしょう。 フィールドをコンマで区切ってファイルへ書き出すために、SELECT ... INTO OUT FILEを使用するとすれば: 

      mysql> SELECT * INTO OUTFILE 'data.txt'
    ->          FIELDS TERMINATED BY ','
    ->          FROM ...;

      コンマ区切りファイルから読み戻すため、正しいステートメントはこうなるでしょう: 

      mysql> LOAD DATA INFILE 'data.txt' INTO TABLE table2
    ->           FIELDS TERMINATED BY ',';

      その代わりとして次に示すようなステートメントでファイルを読み込もうとしても、正し く動作しないでしょう。なぜなら、これは、LOAD DATA INFILEに対してフィール ドの間にタブを探すよう指示するからです: 

      mysql> LOAD DATA INFILE 'data.txt' INTO TABLE table2
    ->           FIELDS TERMINATED BY '\t';

      おそらく、それぞれの入力行は単一のフィールドとして処理されるでしょう。

      LOAD DATA INFILEは外部ソースからもファイルを読み出すことができます。 例えば、dBASEフォーマットのファイルは、フィールドをコンマで区切られ、ダブルクォ ーテーションで囲まれています。 レコードが改行文字で区切られているとしたら、次に示すフィールド及びレコードの取扱 オプションを指定したコマンドが、このようなファイルを読み込むのに使用できます。 

      mysql> LOAD DATA INFILE 'data.txt' INTO TABLE tbl_name
    ->           FIELDS TERMINATED BY ',' ENCLOSED BY '"'
    ->           LINES TERMINATED BY '\n';

      いくつかのフィールド及びレコードの取扱オプションに、空文字列('')を 指定することがあります。空でないなら、 FIELDS [OPTIONALLY] ENCLOSED BYとFIELDS ESCAPED BYの値は 単一の文字でなければなりません。 FIELDS TERMINATED BYとLINES TERMINATED BYは２つ以上の文字となるで しょう。

      例えば、リターン文字と改行文字のペアで区切られたレコードを書き込んだり、 このようなレコードを含んだファイルを読み込んだりするには、 LINES TERMINATED BY '\r\n'節を指定します。 

      CREATE TABLE jokes (a int not null auto_increment primary key, joke text
not null);
LOAD DATA INFILE "/tmp/jokes.txt" INTO TABLE jokes FIELDS TERMINATED BY ""
LINES TERMINATED BY "\n%%\n" (joke);

      FIELDS [OPTIONALLY] ENCLOSED BYは、フィールドの引用符を制御します。出力の 際(SELECT ... INTO OUTFILE)、OPTIONALLY語を省いたなら、全てのフィ ールドはENCLOSED BY文字で囲まれます。このような出力(フィールド区切りにコ ンマを使用)の例を次に示します: 

      "1","a string","100.20"
"2","a string containing a , comma","102.20"
"3","a string containing a \" quote","102.20"
"4","a string containing a \", quote and comma","102.20"

      OPTIONALLYを指定すれば、ENCLOSED BY文字は、 CHARフィールド とVARCHARフィールドのみ囲むのに使用されます: 

      1,"a string",100.20
2,"a string containing a , comma",102.20
3,"a string containing a \" quote",102.20
4,"a string containing a \", quote and comma",102.20

      フィールド値の中におけるENCLOSED BY文字の出現は、ESCAPED BY文字を その前に置くことによりエスケープされることに注意して下さい。ESCAPED BY値 に空を指定すると、LOAD DATA INFILEにより正しく読み込めない出力を生成する でしょう。例えば、このようにエスケープ文字を空にした場合、以下に示すような出力と なります。４行目の２つ目のフィールドに、(誤って)フィールドを区切るかのようなクォ ートに続くコンマを含んでいることに注視して下さい: 

      1,"a string",100.20
2,"a string containing a , comma",102.20
3,"a string containing a " quote",102.20
4,"a string containing a ", quote and comma",102.20

      入力において、ENCLOSED BY文字が指定されており、それがフィールド値の両端に 現れた場合、その文字は取り去られます。(これは、OPTIONALLYが指定されたかど うかに拘らず、当てはまります;OPTIONALLYは入力解析には効果がありません。) ESCAPED BY文字を前置きされたENCLOSED BY文字の出現は、現在のフィー ルド値の一部として処理されます。具体的には、あるフィールドがそれ自身、たEN CLOSED BY文字で始まっている場合、フィールドらの内部で発生する２重のENCLOS ED BY文字は、単一のENCLOSED BY文字として処理されます。 例えば、ENCLOSED BY '"'が指定されると、引用符は以下のように操作されます: 

      "The ""BIG"" boss"  -> The "BIG" boss
The "BIG" boss      -> The "BIG" boss
The ""BIG"" boss    -> The ""BIG"" boss

      FIELDS ESCAPED BYは、特殊文字をどのように書き込んだり読み込んだりするかを 制御します。 FIELDS ESCAPED BY文字が空でない場合、出力において次のような文字(文字列) のプリフィックスに使用されます:

      • FIELDS ESCAPED BY文字
      • FIELDS [OPTIONALLY] ENCLOSED BY文字
      • FIELDS TERMINATED BY値とLINES TERMINATED BY値の最初の文字
      • ASCII 0 (エスケープ文字の後に続いて実際に書かれる文字はASCII '0'で、'ゼロ 値'バイトではありません)

      FIELDS ESCAPED BY文字が空であれば、どの文字もエスケープされません。 特に、フィールド値が上に示した文字を含んでいるならば、エスケープ文字に空を指定す るのはあまり良い考えとは言えないでしょう。

      入力において、FIELDS ESCAPED BY文字が空でない場合、この文字の出現は取り去 られ、後続の文字はフィールド値の一部としてそのまま受け取られます。 例外は、エスケープされた`0'や`N'です (例えば、エスケープ文字が`\'である時の\0や\N)。 これらのシーケンスは、ASCII 0('ゼロ値'バイト) 、NULLとして処理されます。 code{NULL}操作の規則は下を参照して下さい。

      `\'-escape syntaxに関するこれ以外の情報は、 「6.1.1 文字列と数値をどのように書くか？」節参照。

      フィールドとレコード操作オプションが確実に相互作用する事例:

      • LINES TERMINATED BYが空文字列でFIELDS TERMINATED BYが空でない場合 、各レコードもまたFIELDS TERMINATED BYで終らせられます。
      • FIELDS TERMINATED BYとFIELDS ENCLOSED BY値が両方とも空('') の時、(区切られない)固定長行フォーマットが使用されます。 固定長行フォーマットでは、フィールド間に区切り文字列が使用されません。 その代わり、フィールド値は、フィールドの``表示''幅を使って書き込まれたり、読み込 まれます。 例えば、あるフィールドがINT(7)で定義されている場合、フィールドの値は7文字 の桁を使って書き込まれます。 入力においてフィールドは、７文字の読み込みにより得られます。 固定長行フォーマットはまた、NULL値の操作に好んで用いられます;下を参照のこ と。 注意: マルチバイト文字セットを使用している場合は固定長フォーマットは働きま せん。

      FIELDSとLINESオプションによるNULL値の多様な取扱い:

      • FIELDSとLINESの初期値のために、出力時にNULLは\Nとし て書き込まれ、入力時に\NはNULLとして読み込まれます(当然のことなが ら、ESCAPED BY文字は`\'とします)。
      • FIELDS ENCLOSED BYが空で無い時、定数NULLのフィールド値はNULL 値として読み込まれます(これは、文字列'NULL'として読み込まれるFIELD S ENCLOSED BY文字列で囲まれたNULLとは異なります)。
      • FIELDS ESCAPED BYが空の時、NULLはNULLとして書き込まれます。
      • 固定長行フォーマット(FIELDS TERMINATED BYとFIELDS ENCLOSED BYがい ずれも空の場合に起こります)において、NULLは、空白文字列として書き込まれま す。 これは、ファイル内では、NULL値と空白値の見分けがつかないということを示し ていることに注意して下さい。ファイルからデータを読み戻す時に両者を区別しなければ ならない場合、固定長行フォーマットは使用すべきではありません。

      LOAD DATA INFILEでサポートされないケース:

      • 固定長行(FIELDS TERMINATED BYとFIELDS ENCLOSED BYの両方が空)と BLOBフィールド。
      • あるセパレータを他と同じかもしくは他のプリフィックスとした場合、LOAD DATA INFILEは、正しい入力処理ができないでしょう。 例えば、以下のFIELDS節は問題の原因となります: 
        FIELDS TERMINATED BY '"' ENCLOSED BY '"'
      • FIELDS ESCAPED BYが空で、フィールド値に、FIELDS ENCLOSED BY値や LINES TERMINATED BY値の後にFIELDS TERMINATED BY値がくるようなものを含 む場合、フィールドや行の読み込みが早めに打ち切られてしまいます。 これは、LOAD DATA INFILEが、フィールドやレコードの終了位置を正しく決めら れないことにより発生します。

      次の例は、persondataテーブルの全てのフィールドを読み込みます: 

      mysql> LOAD DATA INFILE 'persondata.txt' INTO TABLE persondata;

      フィールドリストが指定されていませんから、LOAD DATA INFILEは、入力レコー ドがテーブルのそれぞれのフィールドを含むものと想定します。 FIELDSとLINESの初期値が使用されます。

      テーブルの一部のフィールドのみ読み込みたい場合、フィールドリストを指定します: 

      mysql> LOAD DATA INFILE 'persondata.txt'
    ->           INTO TABLE persondata (col1,col2,...);

      テーブル内のフィールド順と入力ファイルのフィールド順が異なる場合にも、My SQLにテーブルのフィールドと入力フィールドの対応を教えるために、フィールドリスト を指定しなければなりません。

      入力レコードのフィールド数の方が少ない場合、入力フィールド値が与えられないフィー ルドは、初期値が設定されます。 初期値の割当てについては、 「6.5.3 CREATE TABLE 構文」節. で述べられています。

      空のフィールド値は変換されます：

      • 文字型の場合、 フィールドの値は空文字にセットされます。
      • 数値型の場合、フィールドの値は 0 にセットされます。
      • 日付と時刻の型の場合、 フィールドの値は ``zero'' の意味する値がセットされます。 「6.2.2 日付と時間の型」節参照.

      Note that these are the same values that result if you assign an empty string explicitly to a string, numeric, or date or time type explicitly in an INSERT or UPDATE statement.

      TIMESTAMP フィールドは、フィールド値に NULL 値が指定されていた場合 もしくは、 フィールドリストが指定されている時に TIMESTAMP フィールドがそのリストから 除外されていた場合 (最初のTIMESTAMPフィールドのみ)、現在時刻が設定されるだけです。

      入力レコードのフィールド数の方が多い場合、余分なフィールドは無視され、警告の数が 増やされます。

      LOAD DATA INFILEは全ての入力を文字列と文字列とみなすことから、INSER TステートメントでできるようなENUMフィールドやSETフィールドへの数 値の指定はできません。全てのENUM及びSET値は文字列として与えられな ければいけません！

      LOAD DATA INFILEクエリの終了時、クエリの情報を得るためにC API関数my sql_info()を使用することができます。情報の書式は以下に示すようなものです: 

      Records: 1  Deleted: 0  Skipped: 0  Warnings: 0

      LOAD DATA INFILE が、入力レコードのフィールド数の過不足があった時にも 警告を引き起こす事を除けば、INSERT ステートメント ( 「6.4.3 INSERT 構文」節参照. ) により値が挿入される時に 警告が発生するのと同じ状況下で、警告が発生します。 警告はどこにも保存されません； 警告の数は全てうまくいった場合にだけ 使用できます。 もし警告を知りたい、その警告の理由を知りたいのなら、 一つ方法があります。 SELECT ... INTO OUTFILE を使用して 他のファイルに落とし、オリジナルのファイルと比べます。

      パイプからの読み込みで LOAD DATA の必要があれば、次のトリッ クを使用できます: 

      mkfifo /mysql/db/x/x
chmod 666 /mysql/db/x/x
cat < /dev/tcp/10.1.1.12/4711 > /nt/mysql/db/x/x
mysql -e "LOAD DATA INFILE 'x' INTO TABLE x" x

      If you are using a version of MySQL older than 3.23.25 you can only do the above with LOAD DATA LOCAL INFILE.

      INSERTと比較したLOAD DATA INFILEの効率やLOAD DATA INFILEの 高速化についてのより詳しい情報は、 「5.2.9 INSERT クエリの速度」節参照を参照のこと。

      6.4.10 DO Syntax

      DO expression, [expression, ...]

      Execute the expression but don't return any results. This is a shorthand of SELECT expression, expression, but has the advantage that it's slightly faster when you don't care about the result.

      This is mainly useful with functions that has side effects, like RELEASE_LOCK.

      6.5 Data Definition: CREATE, DROP, ALTER

      6.5.1 CREATE DATABASE 構文

      CREATE DATABASE [IF NOT EXISTS] db_name

      CREATE DATABASE は与えられた名前のデータベースを作ります。データベースの 名前として許される命名規則は、 「6.1.2 データベース名、テーブル名、インデックス名、フィールド名、エイリアス名」節に依ります。 もし、データベースがすでに存在しているにもかかわらず IF NOT EXISTS を 指定していなかったら、エラーが発生します。

      MySQLにおけるデータベースは、データベース内のテーブルに相当するファイル を含むディレクトリとして実装されます。初期作成後はデータベース内にテーブルは存在 せず、CREATE DATABASEステートメントは、MySQLデータディレクトリ下 にディレクトリを作成するだけです。

      mysqladminでもデータベースを作成することができます。 「4.8 MySQL Client-Side Scripts and Utilities」節参照.

      6.5.2 DROP DATABASE 構文

      DROP DATABASE [IF EXISTS] db_name

      DROP DATABASEは、データベース内の全てのテーブルと共にデータベースを破棄し ます。 シンボリックリンクされた DROP DATABASE を行なうと、リンクとオリジナ ルデータベースの両方が削除されます。 このコマンドの使用には万全の注意を払って下さい！

      DROP DATABASEは、データベースディレクトリから削除されたファイルの数を返し ます。それぞれのテーブルは`.MYD'ファイル／`.MYI'ファイル／`.frm' ファイルに相当することから、通常この値はテーブルの３倍の数となります。

      DROP DATABASE コマンドは与えられたデータベースディレクトリから、次 の拡張子のすべてのファイルを削除します:

      Ext Ext Ext Ext
      .BAK .DAT .HSH .ISD
      .ISM .ISM .MRG .MYD
      .MYI .db .frm

      2桁の数値のすべてのサブディレクトリ(RAID ディレクトリ)も削除されま す。

      MySQL 3.22以降では、データベースが存在しないことに起因するエラーを防ぐ ために、キーワード IF EXISTS を使用することができます。

      mysqladminでもデータベースを破棄することができます。 「4.8 MySQL Client-Side Scripts and Utilities」節参照.

      6.5.3 CREATE TABLE 構文

      CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name [(create_definition,...)]
[table_options] [select_statement]

or

CREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name LIKE old_table_name;

create_definition:
  col_name type [NOT NULL | NULL] [DEFAULT default_value] [AUTO_INCREMENT]
            [PRIMARY KEY] [reference_definition]
  or    PRIMARY KEY (index_col_name,...)
  or    KEY [index_name] (index_col_name,...)
  or    INDEX [index_name] (index_col_name,...)
  or    UNIQUE [INDEX] [index_name] (index_col_name,...)
  or    FULLTEXT [INDEX] [index_name] (index_col_name,...)
  or    [CONSTRAINT symbol] FOREIGN KEY [index_name] (index_col_name,...)
            [reference_definition]
  or    CHECK (expr)

type:
        TINYINT[(length)] [UNSIGNED] [ZEROFILL]
  or    SMALLINT[(length)] [UNSIGNED] [ZEROFILL]
  or    MEDIUMINT[(length)] [UNSIGNED] [ZEROFILL]
  or    INT[(length)] [UNSIGNED] [ZEROFILL]
  or    INTEGER[(length)] [UNSIGNED] [ZEROFILL]
  or    BIGINT[(length)] [UNSIGNED] [ZEROFILL]
  or    REAL[(length,decimals)] [UNSIGNED] [ZEROFILL]
  or    DOUBLE[(length,decimals)] [UNSIGNED] [ZEROFILL]
  or    FLOAT[(length,decimals)] [UNSIGNED] [ZEROFILL]
  or    DECIMAL(length,decimals) [UNSIGNED] [ZEROFILL]
  or    NUMERIC(length,decimals) [UNSIGNED] [ZEROFILL]
  or    CHAR(length) [BINARY]
  or    VARCHAR(length) [BINARY]
  or    DATE
  or    TIME
  or    TIMESTAMP
  or    DATETIME
  or    TINYBLOB
  or    BLOB
  or    MEDIUMBLOB
  or    LONGBLOB
  or    TINYTEXT
  or    TEXT
  or    MEDIUMTEXT
  or    LONGTEXT
  or    ENUM(value1,value2,value3,...)
  or    SET(value1,value2,value3,...)

index_col_name:
        col_name [(length)]

reference_definition:
        REFERENCES tbl_name [(index_col_name,...)]
                   [MATCH FULL | MATCH PARTIAL]
                   [ON DELETE reference_option]
                   [ON UPDATE reference_option]

reference_option:
        RESTRICT | CASCADE | SET NULL | NO ACTION | SET DEFAULT

table_options:
	TYPE = {BDB | HEAP | ISAM | InnoDB | MERGE | MRG_MYISAM | MYISAM }
or	AUTO_INCREMENT = #
or	AVG_ROW_LENGTH = #
or	CHECKSUM = {0 | 1}
or	COMMENT = "string"
or	MAX_ROWS = #
or	MIN_ROWS = #
or	PACK_KEYS = {0 | 1 | DEFAULT}
or	PASSWORD = "string"
or	DELAY_KEY_WRITE = {0 | 1}
or      ROW_FORMAT= { default | dynamic | fixed | compressed }
or	RAID_TYPE= {1 | STRIPED | RAID0 } RAID_CHUNKS=#  RAID_CHUNKSIZE=#
or	UNION = (table_name,[table_name...])
or	INSERT_METHOD= {NO | FIRST | LAST }
or      DATA DIRECTORY="absolute path to directory"
or      INDEX DIRECTORY="absolute path to directory"

select_statement:
	[IGNORE | REPLACE] SELECT ...  (Some legal select statement)

      CREATE TABLEはカレントデータベースに、与えられた名前のテーブルを 作成します。テーブルの名前として許される命名規則は、 「6.1.2 データベース名、テーブル名、インデックス名、フィールド名、エイリアス名」節参照に 依ります。 カレントデータベースが無い場合や、テーブルが既に存在している場合はエラーが 発生します。

      MySQL バージョン 3.22 以降ではテーブル名は db_name.tbl_name とい う形で与える事もできます。 これはカレントデータベースがあるかどうかにに関係なく動作します。

      MySQL バージョン 3.23 からは、テーブル作成時に TEMPORARY キーワー ドを使用することができます。 一時テーブルの名前はそれぞれの接続内に制限されます。 一時テーブルは、もし、コネクションが落ちた場合、自動で消去されます。 これは、二つの違う接続で、同じ名前の一時テーブルを 衝突することなく、使用できるという事です。 さらには、既に存在するテーブルと同名であっても、一時テーブルは使用できます。 (一時テーブルが削除されるまで、実在するテーブルは隠されます) From MySQL 4.0.2 one must have the CREATE TEMPORARY TABLES privilege to be able to create temporary tables.

      MySQL バージョン 3.23 以降では、 IF NOT EXISTS キーワードを使用 できます。 これは、もしテーブルが既に存在していた場合、エラーを発生させません。 テーブルの構造が一意かどうかまでは検査しないことに注意。

      In MySQL 4.1 you can use LIKE to create a table based on a table definition in another table. In MySQL 4.1 you can also specify the type for a generated column: 

      CREATE TABLE foo (a tinyint not null) SELECT b+1 AS 'a' FROM bar;

      それぞれのテーブルは、データベースディレクトリにおける以下の複数の ファイルで表されます。これは MyISAM 型 のテーブル場合：

      File Purpose
      tbl_name.frm Table definition (form) file
      tbl_name.MYD Datafile
      tbl_name.MYI Index file

      フィールドに対する種々の型属性の詳細は、 「6.2 フィールド型」節を参照のこと。

      • NULLもNOT NULLも指定されなかった場合、フィールドはNULLが指 定されたものとして扱われます。
      • 整数型のフィールドには付加属性AUTO_INCREMENTも指定することができます。 AUTO_INCREMENTのフィールドに値NULL又は0を挿入した場合、フィ ールドにはvalue+1の値がセットされます。valueは、そのテーブル内の当 該フィールドにおける現在の最大値です。 AUTO_INCREMENT は 1 からはじまります. 「8.4.3.130 mysql_insert_id()」節参照. 削除したレコードが、AUTO_INCREMENTフィールドの最大値を含んでいた場合、 その値は、ISAM と BDB テーブルでは、次に再利用されますが、 MyISAM と InnoDB テーブルでは再利用されません。 また、テーブル内の全てのレコードを DELETE FROM table_name (WHERE節 無しで) を AUTOCOMMIT モードで使用して削除した場合は、すべてのテーブル型で始めから採 番し直します。 注意: 1つのテーブルには1つしかAUTO_INCREMENTフィールドを指定でき ません。 また、インデックスを指定する必要があります。 MySQL 3.23 は auto_increment フィールドが正の数を持っている場合に だけ、正しく動作します。負の数の挿入はとても大きな正の数の挿入とみなされま す。これは、数値が正から負への 'wrap' over する時の精度の問題を回避するた めと、アクシデント的に 0 を含む auto_increment フィールドを得ることがない ことを確実にするために、行なわれます。 In MyISAM and BDB tables you can specify AUTO_INCREMENT secondary column in a multi-column key. 「3.5.9 Using AUTO_INCREMENT」節参照. MySQL をいくつかの ODBC アプリケーションと互換にするために、次の クエリで最後に挿入されたレコードを見つけることができます: 
        SELECT * FROM tbl_name WHERE auto_col IS NULL
      • CREATE TABLE automatically commits the current InnoDB transaction if MySQL binary logging is used.
      • TIMESTAMPフィールドにおけるNULL値は、他のフィールド属性と違った扱 われ方をします。定数NULLをTIMESTAMPフィールドに格納することはでき ません。NULL値の指定は現在時刻をセットすることを意味します。 TIMESTAMPフィールドがこのように振舞うので、通常はNULL属性や NOT NULL属性は適用できません。それらを指定しても無視されます。 一方、MySQLクライアントからは、より安易にTIMESTAMPフィールドを 利用でき、サーバもTIMESTAMPフィールドへのNULLの適用を報告しますが 、TIMESTAMPフィールドは実際にはNULL値を保存することはありません。 code{DESCRIBE tbl_name}を使用して、テーブル定義文を取得することにより、この現象 を確認することができます。 TIMESTAMPフィールドに0を指定することは、NULLを指定すること と等しくないことに注意してください。なぜなら、0はTIMESTAMPの値とし て不正であるからです。
      • A DEFAULT value has to be a constant, it cannot be a function or an expression. フィールドに対して DEFAULT 値が指定されない場合は MySQL が 自動的にそれを割り当てます。 フィールドが NULL を値として取り得る場合は、デフォルト値は NULL です。 フィールドが NOT NULL として宣言された場合は、デフォルト値はフィー ルド型に依存します:
        • AUTO_INCREMENT 定義された以外の数値型のフィールドに対しては、 初期値は0となります。 AUTO_INCREMENTフィールドでは、デフォルト値は次のシーケンス番号になります。
        • TIMESTAMP 型以外の日付型と時刻型のフィールドに対しては、 初期値はその型において適切な``ゼロ''値となります。 例外: フィールドがそのテーブル内で最初のTIMESTAMPフィールドである場合、初 期値は現在時刻になります。 「6.2.2 日付と時間の型」節参照.
        • ENUM 以外の文字列型のフィールドに対しては、初期値は空文字列となります。 ENUM では、デフォルト値は最初の列挙の値です。
        Default values must be constants. This means, for example, that you cannot set the default for a date column to be the value of a function such as NOW() or CURRENT_DATE.
      • KEYは、INDEXの同義語です。
      • MySQLでは、UNIQUEキーは固有値しか持つことができません。既に存在 するレコードとキーの値が重複するレコードを挿入しようとした場合、エラーが発生しま す。
      • PRIMARY KEY はユニーク KEY で、すべてのキーフィールドは NOT NULL として定義されなければならないという特別な制限を伴います。 MySQL ではキーは PRIMARY と名付けられます。テーブルは PRIMARY KEY を一つだけ持つことができます。PRIMARY KEY を持た ない場合に、アプリケーションがテーブル内の PRIMARY KEY を尋ねると、 MySQL は PRIMARY KEY として、NULL フィールドを持た ない最初の UNIQUE キーを返します。
      • PRIMARY KEYは複数フィールドインデックスとできます。しかしながら、1つのフ ィールド定義内ではPRIMARY KEY属性を用いて複合インデックスを定義することが できませんので、フィールド定義内における指定は、プライマリ・キーが単独フィールド の場合のみとして下さい。複合フィールドの場合は、 PRIMARY KEY(index_col_name,...)文を使用しなければなりません。
      • PRIMARY や UNIQUE キーが１つのフィールドだけからなり、その型が整数 の場合、それを _rowid としても参照することができます (バージョン 3.23.11 での新機能)。
      • インデックスに名前を割り当てない場合、一意な名前を付けるために、 index_col_name 内の最初のフィールド名に(_2, _3, ...)のような サフィックスを付加したものが割り当てられます。 テーブルが使用しているインデックス名は、 SHOW INDEX FROM tbl_nameにより確認することができます。 「4.5.6.1 Retrieving information about Database, Tables, Columns, and Indexes」節参照.
      • MyISAM テーブルのみが、NULL 値をもつフィールドに対して インデックスを持つことが出来ます。 その他のテーブル型の場合、フィールドを NOT NULL で定義しなくてはなりませ ん。
      • col_name(length)文を共に指定することで、CHARフィールド又は VARCHARフィールドの一部分だけをインデックスとして定義できます。 これによりインデックスファイルを適度に小さくすることができます。 「5.4.4 Column Indexes」節参照.
      • MyISAM テーブル型のみが、 BLOB と TEXT フィールド上に インデックスを持つことが出来ます。 BLOB と TEXT フィールドに インデックスを張る場合、常に、インデックスの長さを指定しなくてはなりません： 
        CREATE TABLE test (blob_col BLOB, INDEX(blob_col(10)));
      • TEXTフィールドやBLOBフィールドで ORDER BY や GROUP BY を使用すると、 最初のmax_sort_lengthバイトだけが使用されます。 「6.2.3.2 BLOB と TEXT 型」節参照.
      • MySQL バージョン 3.23.23 以降では、特殊な FULLTEXT インデックスも 生成できます。それらは全文検索に使用されます。MyISAM テーブル型 だけが FULLTEXT インデックスをサポートします。それらは CHAR, VARCHAR, TEXT フィールドからだけ生成できます。 インデックスは常にフィールド全体に起こります。部分インデックスは サポートされません。オペレーションの詳細は 「6.8 MySQL Full-text Search」節 を見てください。
      • In MySQL Version 3.23.44 or later, InnoDB tables support checking of foreign key constraints. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. Note that the FOREIGN KEY syntax in InnoDB is more restricted than the syntax presented above. InnoDB does not allow index_name to be specified, and the columns of the referenced table always have to be explicitly named. Starting from 4.0.8 InnoDB supports both ON DELETE and ON UPDATE actions on foreign keys. See the InnoDB manual section for the precise syntax. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. For other table types, MySQL Server does parse the FOREIGN KEY, CHECK, and REFERENCES syntax in CREATE TABLE commands, but without further action being taken. 「1.7.4.5 外部キー」節参照.
      • 全てのNULLフィールドは、1ビット余計に消費し、直近のバイトに丸められます。
      • レコードの最大長は、以下のようにして求められます: 
        レコードの長さ = 1
             + (フィールドの長さの合計)
             + (NULLフィールドの数 + 7)/8
             + (可変長フィールドの数)
      • table_options と SELECT オプションは、 MySQL 3.23 以上でのみ実装されます。 テーブル型は：
        Table type Description
        BDB または BerkeleyDB トランザクションセーフなテーブル 「7.6 BDB or BerkeleyDB Tables」節参照.
        HEAP このテーブルのデータは、メモリー内にのみ蓄えられる 「7.4 HEAP Tables (3.23.0以上)」節参照.
        ISAM オリジナルのテーブル 「7.3 ISAM Tables」節参照.
        InnoDB レコードロッキングを持ったトランザクション安全テーブル 「7.5 InnoDB テーブル (3.23.6以上)」節参照.
        MERGE 一つのテーブルとして使用される MyISAM テーブルの集まり 「7.2 MERGE Tables (3.23.25以上)」節参照.
        MRG_MyISAM An alias for MERGE tables
        MyISAM ISAM にかわる 新しい バイナリ互換のテーブル。 「7.1 MyISAM テーブル (3.23.0以上)」節参照.
        「7 MySQL テーブル型」節参照. テーブル型が指定され、特定の型が有効でない場合、MySQL は指定され たものに近いテーブル型を選択します。例えば、TYPE=BDB が指定されて、 MySQL のディストリビューションが BDB テーブルをサポートし ない場合、代わりにテーブルは MyISAM として生成されます。 その他のテーブルオプションを使って、テーブルの振る舞いを最適化します。 たいていの場合は、オプションを明示する必要がありません。 明示的に指定されなかった場合、オプションはすべてのテーブル型に作用します。
        Option Description
        AUTO_INCREMENT あなたがこのテーブルにセットしたい、次の AUTO_INCREMENT 値
        AVG_ROW_LENGTH テーブルに含まれるレコードの長さのおおよその平均値。 可変長のレコードを持つ大きなテーブルに対してのみ、これをセットします。
        CHECKSUM MySQL に全てのレコードをチェックさせたい場合、これを 1 にセットします。 (これは更新を遅くさせますが、不整合の生じたテーブルを見つけ出しやすくなります) (MyISAM)
        COMMENT テーブルの、60文字コメント
        MAX_ROWS あなたがテーブルに保存したいと考えている最大レコード数。
        MIN_ROWS あなたがテーブルに保存したいと考えている最低レコード数
        PACK_KEYS より小さいインデックスにしたいなら、これを 1 にします。 これは更新を遅くしますが、読み出しは速くなります (MyISAM, ISAM). Setting this to 0 will disable all packing of keys. Setting this to DEFAULT (MySQL 4.0) will tell the storage engine to only pack long CHAR/VARCHAR columns.
        PASSWORD .frm ファイルをパスワード付きで暗号化。 このオプションは、標準の MySQL バージョンではなにも行いません。
        DELAY_KEY_WRITE テーブルがクローズされるまでキーテーブルの更新を送らせたい場合、1に設定します(MyISAM)。
        ROW_FORMAT レコードがどのように格納されるかを定義します。現在 DYNAMIC と STATIC オプションが MyISAM テーブルのために使用できるだけです。
        MyISAM テーブルを使用するならば、MySQL は max_rows * avg_row_length の値を、テーブルがどのくらい大きくなるか の推定に使用します。 もし、上記のオプションをなにも指定しなかった場合、テーブルの最大サイズは 4G になります。(か、あなたの OS が 2G しかサポートしていなければ 2G まで) この理由は、大きなファイルを本当に必要としない場合は、インデックスをより小 さく、より速くするため、ポインタサイズを小さく保持するためです。 PACK_KEYS を使用しない場合、デフォルトは文字列だけをパックし、数値 はパックしません。PACK_KEYS=1 を使用するとさらに数値もパックされま す。 バイナリ数値キーをパックする時、MySQL はプレフィックス圧縮を使用 します。これは、同じ数値を多く持つ場合にだけこの大きな恩恵を得るということ を意味します。プレフィックス圧縮は、前のキーの何バイトが次のキーと同じであ るかを示すための余計な1バイトがすべてのキーに必要となることを意味します(注 意: レコードへのポインタは、圧縮の向上のため high-byte-first-order でキー の直後に格納されます)。これは、2つのレコードが同じキー多く持つ場合、後のす べての'同じ'キーは通常2バイト(レコードへのポインタを含む)だけを必要とする ということです。これを、通常のケースと比較してみてください。通常のケースは、 後のキーは'キーの格納サイズ' + ポインタサイズ(通常4)を必要とします。一方、 すべてのキーが全く異なっていると、キーが NULL 値を持つことができる キーではない場合では、キー毎に1バイトを消費します(この場合、パックされたキー の長さは、キーが NULL の時にマークのために使用されるのと同じバイト 数で格納されます)。
      • もし CREATE ステートメントの後に SELECT を指定するならば、 MySQL は、SELECT で返ってくる全ての項目を収めるために、 新しいフィールドを作成します。 例えば： 
        mysql> CREATE TABLE test (a INT NOT NULL AUTO_INCREMENT,
    ->        PRIMARY KEY (a), KEY(b))
    ->        TYPE=MyISAM SELECT b,c FROM test2;
        これは 3つのフィールド a, b, c を MyISAM テーブルに作成します。 SELECT ステートメントからのフィールドがテーブルの右側に追加され、上 書きされないことに注意してください。次の例を見てください: 
        mysql> SELECT * FROM foo;
+---+
| n |
+---+
| 1 |
+---+

mysql> CREATE TABLE bar (m INT) SELECT n FROM foo;
Query OK, 1 row affected (0.02 sec)
Records: 1  Duplicates: 0  Warnings: 0

mysql> SELECT * FROM bar;
+------+---+
| m    | n |
+------+---+
| NULL | 1 |
+------+---+
1 row in set (0.00 sec)
        テーブル foo の各レコードについて、foo からの値と新しいフィー ルドのデフォルト値を伴って bar のレコードが 挿入されます。 CREATE TABLE ... SELECT will not automatically create any indexes for you. This is done intentionally to make the command as flexible as possible. If you want to have indexes in the created table, you should specify these before the SELECT statement: 
        mysql> CREATE TABLE bar (UNIQUE (n)) SELECT n FROM foo;
        もしデータをテーブルにコピーしている最中にエラーが起きたなら、 このテーブルは自動的に消去されることに注意してください。 更新ログ／バイナリログはオリジナルテーブルを再生成するために使用できます。 MySQL は CREATE TABLE .... SELECT 中に並行しての挿入を許し ません。
      • RAID_TYPE オプションは、大規模ファイルをサポートしていない OS 上の 2G/4Gの制限を破る手助けをします。Note that this option is not recommended for filesystem that supports big files! また、RAID ディレクトリを別の物理 ディスクに置くことにより、IO ボトルネックからさらに速度を得ることができま す。RAID_TYPE は、MySQL を --with-raid でコンフィグ すれば、どんな OS 上でも働きます。現在、RAID_TYPE は STRIPED だけが許されています(1 と RAID0 はこれの別名 です)。 RAID_TYPE=STRIPED を MyISAM テーブルに指定すると、 MyISAM はデータベースディレクトリ中に 00, 01, 02 という名前の RAID_CHUNKS サブディレクトリを生成します。これらのディレクトリのそ れぞれに、MyISAM は table_name.MYD を生成します。データファ イルにデータが書き込まれる時、RAID ハンドラは最初の RAID_CHUNKSIZE *1024 バイトを最初のファイルに、次の RAID_CHUNKSIZE *1024 バイトを次のファイルにマップします。
      • UNION は同じテーブルの集まりを一つとして使用したい時に使用されます。 これは MERGE テーブルでだけ動作します。 「7.2 MERGE Tables (3.23.25以上)」節参照. 今のところ、MERGE テーブルをマップするテーブル上に SELECT, UPDATE, DELETE 権限を持つことが必要です。マップされたすべて のテーブルは MERGE テーブルとして、同じデータベース内にある必要があ ります。
      • If you want to insert data in a MERGE table, you have to specify with INSERT_METHOD into with table the row should be inserted. 「7.2 MERGE Tables (3.23.25以上)」節参照. This option was introduced in MySQL 4.0.0.
      • 生成されたテーブルでは、PRIMARY キーは最初に置かれ、次にすべての UNIQUE キー、それから通常のキーが続きます。これは MySQL オ プティマイザを助け、どのキーを使用するかの優先度付けを行ない、重なった UNIQUE キーをさらにすばやく検出します。
      • DATA DIRECTORY="directory" または INDEX DIRECTORY="directory" を使用することで、the storage engine が テーブルとインデックスファイルを置くべき場所を指定できます。--skip-symlink オプショ ンを使用しない時、これは MySQL 4.0 で MyISAM テーブルでだけ 動作します。 「5.6.1.2 Using Symbolic Links for Tables」節参照.

      6.5.3.1 暗黙のフィールド定義変更

      いくつかのケースにおいてMySQLは、CREATE TABLEステートメントで与 えられたフィールド定義を暗黙の内に変更します (これは ALTER TABLE で起きるかもしれません)

      • VARCHAR columns with a length less than four are changed to CHAR.
      • テーブル内にいくつかの可変長フィールドがある場合、結果的にレコード全体が可変長と なります。 その結果、テーブルがいくつかの可変長フィールド(VARCHAR、TEXT及び BLOB)を持つならば、3文字より大きいフィールド長の全てのCHARフィールドは、 VARCHARフィールドに変更されます。 このことは、フィールドの使用方法には影響しません。 MySQLでは、VARCHARは文字列を格納するための1つの手段に過ぎません。 MySQLは、スペース埋めのコンバージョンを行いますし、テーブル操作もより速 く行います。 「7 MySQL テーブル型」節参照.
      • TIMESTAMPフィールドの表示サイズは、2〜14の範囲の偶数でなければなりません。 表示サイズを0や14より大きく指定した場合、サイズは14に強制されます。1から13の範 囲の奇数の場合、大きい方の偶数値に強制されます。
      • TIMESTAMP フィールドには NULL を代入できません； NULL は 現在の日時をセットします。 NULL and NOT NULL 属性は通常の方法では適用されず、それらを 与えた場合は無視されます。 DESCRIBE tbl_name は常に TIMESTAMP フィールドに NULL 値が割 り当てられた事を告げます。
      • MySQL は他の SQL データベースの使用している型を MySQL 型に マップします。 「6.2.5 他のデータベースエンジンのフィールド型の使用」節参照.

      もし MySQL がフィールドの型をあなたが指定したものと違うものにしたかどう かを知りたい場合、テーブルの作成、alter 後に、 DESCRIBE tbl_name 構文 を発行します。

      myisampackを使用してテーブルを圧縮した場合、別のフィールド定義変更がある 程度起こることがあります。 「7.1.2.3 圧縮テーブルの特徴」節参照.

      6.5.4 ALTER TABLE 構文

      ALTER [IGNORE] TABLE tbl_name alter_spec [, alter_spec ...]

alter_specification:
        ADD [COLUMN] create_definition [FIRST | AFTER column_name ]
  or    ADD [COLUMN] (create_definition, create_definition,...)
  or    ADD INDEX [index_name] (index_col_name,...)
  or    ADD PRIMARY KEY (index_col_name,...)
  or    ADD UNIQUE [index_name] (index_col_name,...)
  or    ADD FULLTEXT [index_name] (index_col_name,...)
  or	ADD [CONSTRAINT symbol] FOREIGN KEY [index_name] (index_col_name,...)
            [reference_definition]
  or    ALTER [COLUMN] col_name {SET DEFAULT literal | DROP DEFAULT}
  or    CHANGE [COLUMN] old_col_name create_definition
               [FIRST | AFTER column_name]
  or    MODIFY [COLUMN] create_definition [FIRST | AFTER column_name]
  or    DROP [COLUMN] col_name
  or    DROP PRIMARY KEY
  or    DROP INDEX index_name
  or    DISABLE KEYS
  or    ENABLE KEYS
  or    RENAME [TO] new_tbl_name
  or    ORDER BY col
  or    table_options

      ALTER TABLEは、既存のテーブルの構造変更を可能にします。 例えば、フィールドの追加や削除、インデックスの作成や破棄、既存のフィールド属性の 変更、及びフィールドやテーブルそのものの名前の変更です。 また、テーブルのコメントやテーブルの型式を変更することも可能です。 「6.5.3 CREATE TABLE 構文」節参照.

      もし ALTER TABLE でフィールド定義を変えても DESCRIBE tbl_name が フィールドを変更していないと示すなら、これは MySQL が 「6.5.3.1 暗黙のフィールド定義変更」節. に述べている理由の一つで変更していない可能性が あります。 例えば、 VARCHAR フィールドを CHAR にしようとすると, MySQL はそのテーブルに他の可変長のフィールドがあるかぎり、 VARCHAR のままにしようとします。

      ALTER TABLEはオリジナルのテーブルの一時的なコピーを作成することにより動作 します。 コピーへの変更作業が完了すると、オリジナルのテーブルは削除され新しく 作られた方の名前が変更されます。これは全ての変更が自動的に新しいテーブルに 対して実施されることにより、誤った変更無しに完了します。 ALTER TABLEが実行されている間、オリジナルのテーブルは他の クライアントから読みだしが可能です。このテーブルへの更新や書き込みは、 新しいテーブルが準備完了となるまで遅らされます。

      注意: ALTER TABLE に RENAME 以外のオプションを使用する場合、 MySQL は常に一時テーブルを生成します。データが厳密にコピーする必 要がないとしてもです(フィールドの名前を変更する時など)。 We plan to fix this in the future, but as one doesn't normally do ALTER TABLE that often this isn't that high on our TODO. For MyISAM tables, you can speed up the index recreation part (which is the slowest part of the recreation process) by setting the myisam_sort_buffer_size variable to a high value.

      • ALTER TABLEを使うには、そのテーブルに ALTER, INSERT, CREATE 権限が必要です。
      • IGNOREはANSI SQL92に対するMySQLの拡張です。 これは、新しいテーブルのユニークキーで重複があった場合の動作を制御します。 IGNOREが指定されない場合、コピーは異常終了し、ロールバックされます。 IGNOREが指定された場合、ユニークキーの重複があったレコードに対し、最初の レコードだけを使用し、他は削除されます。
      • 1つのALTER TABLEステートメントの中で、ADD、ALTER、 DROP、それからCHANGE節の複合的な発行が可能です。 これは、ALTER TABLEステートメント毎に1つだけしかこれらの節を 許さないANSI SQL92に対するMySQLの拡張です。
      • CHANGE col_name、DROP col_name及びDROP INDEXはANSI SQL92に対するMySQLの拡張です。
      • MODIFY は Oracle の ALTER TABLE 拡張です。
      • オプション語COLUMNは蛇足であり、記述を省くことが可能です。
      • 他のオプション無しでALTER TABLE tbl_name RENAME TO new_nameを使用すると、 MySQLはtbl_nameに一致するテーブルの名前を単純に変更します。 テンポラリテーブルの作成は必要としません。 「6.5.5 RENAME TABLE 構文」節参照.
      • create_definitionは、CREATE TABLEにおけるADDやCHANGE と同じ構文を使用します。 「6.5.3 CREATE TABLE 構文」節参照.
      • CHANGE old_col_name create_definition節を使用することによりフィールドの名 前を変更することができます。 このようなことを行うためには、フィールドの旧名称と新名称、それからそのフィールド の現在の型を指定する必要があります。例えば、あるINTEGERフィールドを aからbに変更する場合、以下のように実行することができます: 
        mysql> ALTER TABLE t1 CHANGE a b INTEGER;
        もしフィールドの名前を変えることなく、型だけを変更したい場合であっても、 この CHANGE 構文は、たとえ同じ名前であっても、 ２つの名前を指定するよう要求します。 例: 
        mysql> ALTER TABLE t1 CHANGE b b BIGINT NOT NULL;
        しかし MySQL バージョン 3.22.16a からは, MODIFY を使用して、 名称変更をすることなくフィールドの型を変更することができます。 
        mysql> ALTER TABLE t1 MODIFY b BIGINT NOT NULL;
      • CHANGE や MODIFY を使用して、フィールドの一部にインデックス が存在するようなフィールドを短くしようとしても(例えば VARCHAR フィー ルドの最初の10文字上ににインデックスがある場合)、インデックスされた文字数 よりもフィールドを短くすることはできません。
      • CHANGE や MODIFY を用いてフィールドの型を変更する場合、 MySQLは可能な限り新しい型にデータをコンバートしようと試みます。
      • MySQL バージョン 3.22以降では、 FIRST又はADD ... AFTER col_nameを使用して、 テーブルのレコード内の指定した位置に、フィールドを追加すること ができます。 デフォルトでは、フィールドは(そのレコードの)最後に追加されます。 From MySQL Version 4.0.1, you can also use the FIRST and AFTER keywords in CHANGE or MODIFY.
      • ALTER COLUMNは、フィールドの新たな初期値を指定したり、フィールドの古い初 期値を削除したりします。 古い初期値が削除され、フィールドがNULLを許す場合、新たな初期値は NULLとなります。 NULLが許されない場合、 「6.5.3 CREATE TABLE 構文」節 で 説明されている通り、MySQL は初期値を割り当てます。 「6.5.3 CREATE TABLE 構文」節.
      • DROP INDEXは、インデックスを削除します。これはANSI SQL92に対する MySQL の拡張です。 「6.5.8 DROP INDEX 構文」節参照.
      • フィールドがテーブルから削除されると、そのフィールドが含まれているインデックスか らもそのフィールドが削除されます。 インデックスを構成する全てのフィールドが削除されると、そのインデックスも削除され ます。
      • テーブルが一つのフィールドだけを含む場合、フィールドは破棄できません。テー ブルを削除するつもりなら、DROP TABLE を代わりに使用してください。
      • DROP PRIMARY KEYは、プライマリ・インデックスを削除します。もしプライマリ インデックスが存在しなければ、そのテーブルの最初のUNIQUEインデックスが削 除されます。 (MySQLは、明示的にPRIMARY KEYが指定されなければ最初のUNIQU EキーをPRIMARY KEYとして扱います。) If you add a UNIQUE INDEX or PRIMARY KEY to a table, this is stored before any not UNIQUE index so that MySQL can detect duplicate keys as early as possible.
      • ORDER BY は指定した順のレコードで新しいテーブルを生成することができ ます。注意: 挿入と削除の後にはこの順序は保持されません。テーブルを、後で order をしたいフィールドの順にしておくと MySQL のソートがより簡単 になる場合があります。このオプションは、主に一定の順でレコードをクエリする つもりであることを知っているときに、主に有用です; テーブルに大きな変更をし た後にこのオプションを使用することで、より高い性能を得ることができるdしょ う。
      • ALTER TABLE を MyISAM テーブルに使用する場合、すべての非ユニー クインデックスは(REPAIR のような)別のバッチで生成されます。これは多 くのインデックスがある場合、ALTER TABLE をより速くします。
      • Since MySQL 4.0 the above feature can be activated explicitly. ALTER TABLE ... DISABLE KEYS makes MySQL to stop updating non-unique indexes for MyISAM table. ALTER TABLE ... ENABLE KEYS then should be used to recreate missing indexes. As MySQL does it with special algorithm which is much faster then inserting keys one by one, disabling keys could give a considerable speedup on bulk inserts.
      • C API関数mysql_info()により、どれだけのレコードがコピーされたか、(I GNOREが指定されている時は)どれだけのレコードがユニークキーの重複により削除され たかを調べることができます。
      • FOREIGN KEY、CHECK及びREFERENCES節は、 ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...) を サポートする InnoDB 型以外のテーブルでは実際には何もしません。 Note that InnoDB does not allow an index_name to be specified. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. 他のテーブルに対するこれらの構文は、互換性のためだけに用意されており、 他のSQLサーバからのコードの移植を容易にしたり、 参照情報と共にテーブルを作成するようなアプリケーションを動作 させることを目的としています。 「1.7.4 MySQL と ANSI SQL92 との違い」節参照.

      以下は、ALTER TABLEの使用例を表す例です。 次に示すように作成されたテーブルt1から始めます: 

      mysql> CREATE TABLE t1 (a INTEGER,b CHAR(10));

      テーブルt1の名前をt2に変更するには: 

      mysql> ALTER TABLE t1 RENAME t2;

      フィールド aを INTEGER から TINYINT NOT NULL に (名前は同じままで)変更し、 b を CHAR(10) から CHAR(20) に変更しつつ、 名前を b から cに変更するには: 

      mysql> ALTER TABLE t2 MODIFY a TINYINT NOT NULL, CHANGE b c CHAR(20);

      TIMESTAMPを追加し、名前をdとするには: 

      mysql> ALTER TABLE t2 ADD d TIMESTAMP;

      フィールドdにインデックスを追加し、フィールドaをプライマリ・キーと するには: 

      mysql> ALTER TABLE t2 ADD INDEX (d), ADD PRIMARY KEY (a);

      フィールドcを削除するには: 

      mysql> ALTER TABLE t2 DROP COLUMN c;

      To add a new AUTO_INCREMENT integer column named c: 

      mysql> ALTER TABLE t2 ADD c INT UNSIGNED NOT NULL AUTO_INCREMENT,
    ->       ADD INDEX (c);

      ここで我々が c をインデックス指定したのは、 AUTO_INCREMENT フィー ルドはインデックスであるべきだからで、 c を NOT NULL 指定しているのは インデックスフィールドは NULL にできないからです。

      AUTO_INCREMENT フィールドを追加した場合、フィールドの値は 自動的にシーケンス番号で埋められます。 最初のシーケンス番号は、ALTER TABLE 前に SET INSERT_ID=# を 実行するか、または AUTO_INCREMENT = # テーブルオプションを使用する ことで設定できます。 「5.5.6 SET 構文」節参照.

      MyISAM テーブルでは、AUTO_INCREMENT フィールドを変更しない場合、シー ケンス番号は影響を受けません。AUTO_INCREMENT フィールドを破棄し、そ れから別の AUTO_INCREMENT フィールドを追加した場合、番号は再度 1 か ら始まります。

      「A.6.1 Problems with ALTER TABLE.」節参照.

      6.5.5 RENAME TABLE 構文

      RENAME TABLE tbl_name TO new_tbl_name[, tbl_name2 TO new_tbl_name2,...]

      リネームは自動的に行なわれます。これは、他のスレッドはリネームが動作中はテー ブルのどこにもアクセスできないことを意味します。空のテーブルでテーブルを置 き換えることが可能です: 

      CREATE TABLE new_table (...);
RENAME TABLE old_table TO backup_table, new_table TO old_table;

      リネームは左から右に行なわれます。２つのテーブルの名前を交換したい場合には、 次のようにする必要があることを意味します: 

      RENAME TABLE old_table    TO backup_table,
             new_table    TO old_table,
             backup_table TO new_table;

      ２つのデータベースが同じディスク上にあれば、あるデータベースから他のデータ ベースにリネームすることも可能です: 

      RENAME TABLE current_database.table_name TO other_database.table_name;

      RENAME 実行時には、ロックされたテーブルや有効なトランザクションを持 つことはできません。元のテーブルで ALTER と DROP 権限を、新 しいテーブルで CREATE と INSERT 権限を持つことも必要です。

      MySQL が複数のテーブルのリネームで何らかのエラーに遭遇した場合、 リネームしたすべてのテーブルを逆にリネームし、すべてを元の状態に戻します。

      RENAME TABLE was added in MySQL 3.23.23.

      6.5.6 DROP TABLE Syntax

      DROP [TEMPORARY] TABLE [IF EXISTS] tbl_name [, tbl_name,...] [RESTRICT | CASCADE]

      DROP TABLEは、1つ又は1つ以上のテーブルを破棄します。テーブルの全てのデー タとテーブル定義は破棄されますので、このコマンドの使用は慎重に行ってくだ さい！

      MySQL バージョン 3.22以降では、テーブルが存在しないことに起因するエラー を防ぐために、キーワード IF EXISTS を使用することができます。 In 4.1 one gets a NOTE for all not existing tables when using IF EXISTS. 「4.5.6.9 SHOW WARNINGS | ERRORS」節参照. RESTRICT と CASCADE は移植を簡単にするために許されています。 しばらくはこれらは何も行ないません。 注意: DROP TABLE はトランザクション安全ではなく、自動的に すべてのアクティブトランザクションをコミットします。 (except if you are using 4.1 and the TEMPORARY key word. )

      Option TEMPORARY is ignored in 4.0. In 4.1 this option works as follows:

      • Only drops temporary tables.
      • It doesn't end a running transactions.
      • No access rights is checked.

      Using TEMPORARY is a good way to ensure that you don't accidently drop a real table.

      6.5.7 CREATE INDEX 構文

      CREATE [UNIQUE|FULLTEXT] INDEX index_name
       ON tbl_name (col_name[(length)],... )

      CREATE INDEX 構文は MySQL 3.22 より以前のバージョンではなにもし ません。 バージョン 3.22 以降で、CREATE INDEX はインデックスの作成のために ALTER TABLE を呼びだしています。 @xref{ALTER TABLE, , ALTER TABLE}.

      通常、テーブル内の全てのインデックスは CREATE TABLE で テーブルを作るときに一度に作成されます。 「6.5.3 CREATE TABLE 構文」節参照. CREATE INDEX は既に存在するテーブルに対し、インデックスを追加します。 CREATE INDEX allows you to add indexes to existing tables.

      フィールドを (col1,col2,...) として指定すると、複数フィールドインデックス を作成します。 インデックスの値は、与えられたフィールドの値を連結して、構成されます。

      CHAR と VARCHAR フィールドでは、インデックスはフィールドの一部分だ けを使用して 作成されます。これは col_name(length) 構文を使用します。 (BLOB と TEXT 節では length が必要です)。 最初の10文字をインデックスとして使用するには、この構文は以下のようにして使用しま す(name フィールドにインデックスを作ります)： 

      mysql> CREATE INDEX part_of_name ON customer (name(10));

      フィールドの一部分だけをインデックスに使用すれば、インデックスファイルをはるかに 小さくすることができます。 ほとんどの名前が最初の10文字において通常異なるので、 このインデックスは name フィールド全部を使用して創り出したインデックスに 比べて遅くなることはありません。また、多くのディスクスペースを節約でき、 INSERT を速くするのです！

      MySQL version 3.23.2 以上で MyISAM 型のテーブルを使用している 場合、NULL 値をもつフィールドや、 BLOB/TEXT フィールドに対して インデックスを張ることが可能です。

      MySQL がどのようにしてインデックスを使用するかは → 「5.4.3 MySQL はどのようにインデックスを使用するか？」節.

      FULLTEXT indexes can index only VARCHAR and TEXT columns, and only in MyISAM tables. FULLTEXT indexes are available in MySQL Version 3.23.23 and later. 「6.8 MySQL Full-text Search」節.

      6.5.8 DROP INDEX 構文

      DROP INDEX index_name ON tbl_name

      DROP INDEX は index_name という名前のインデックスをテーブル tbl_name から破棄します。 DROP INDEX は MySQL バージョン 3.22 より以前のバージョンではなに もしません。 3.22 以降で、DROP INDEX はインデックスの破棄のために ALTER TABLE を呼びだしています。 「6.5.4 ALTER TABLE 構文」節参照.

      6.6 Basic MySQL User Utility Commands

      6.6.1 USE 構文

      USE db_name

      USE db_name 構文は、 MySQL に db_name データベースを この後のクエリのデフォルトのデータベースにするように指示します。 指定されたデータベースは、セッションの最後まで、あるいは、他の USE 構文 が発行されるまで残ります： 

      mysql> USE db1;
mysql> SELECT count(*) FROM mytable;      # selects from db1.mytable
mysql> USE db2;
mysql> SELECT count(*) FROM mytable;      # selects from db2.mytable

      USE 構文で特定のデータベースをカレントにしても、 他のデータベースのテーブルからアクセスすることを妨げません。 以下は db1 データベースの author テーブルと、 db2 データベースの editor テーブルにアクセスする例です： 

      mysql> USE db1;
mysql> SELECT author_name,editor_name FROM author,db2.editor
    ->        WHERE author.editor_id = db2.editor.editor_id;

      USE 構文は Sybase の互換のために提供されています。

      6.6.2 DESCRIBE 構文 (フィールドについての情報を得る)

      {DESCRIBE | DESC} tbl_name [col_name | wild]

      DESCRIBE is a shortcut for SHOW COLUMNS FROM. 「4.5.6.1 Retrieving information about Database, Tables, Columns, and Indexes」節参照.

      DESCRIBE はフィールドについての情報を与えます。 col_name はフィールドはフィールド名または文字列です。 文字列は SQL `%',`_' ワイルドカードを含めます。 There is no need to enclose the string in quotes.

      もしフィールドの型があなたが CREATE TABLE 文で与えた物と違っているなら、 これは MySQL がフィールドの型を変更していることに注意してください。 「6.5.3.1 暗黙のフィールド定義変更」節参照.

      このコマンドは Oracle の互換のためにあります。

      SHOW 構文は似たような情報を提供します。 「4.5.6 SHOW 構文」節参照.

      6.7 MySQL Transactional and Locking Commands

      6.7.1 BEGIN/COMMIT/ROLLBACK 構文

      デフォルトでは MySQL は autocommit モードで動作します。こ れは、更新を実行するとすぐに MySQL が更新をディスクに格納すること を意味します。

      もし トランザクションセーフのテーブル(like BDB, InnoDB) を使用するなら, 以下のコマンドで MySQL を 非 autocommit モード状態にすることができます： 

      SET AUTOCOMMIT=0

      この後、ディスクに変更を格納するためには COMMIT を使用し、また、変 更を無視するためには ROLLBACK する必要があります。

      ある一連のステートメントのために AUTOCOMMIT モードからスイッチし たい場合は、START TRANSACTION か BEGIN または BEGIN WORK ステートメントを使用できます。 

      START TRANSACTION;
SELECT @A:=SUM(salary) FROM table1 WHERE type=1;
UPDATE table2 SET summmary=@A WHERE type=1;
COMMIT;

      START TRANSACTION was added to MySQL 4.0.11; This is the recommended way to start an ad-hoc transaction as this is ANSI SQL syntax. (訳注： 4.0.11より前では、BEGIN を使用します)

      注意: トランザクション安全テーブルを使用していない場合は、autocommit モードのステータスには依存せずに、変更はすぐに格納されます。

      If you do a ROLLBACK when you have updated a non-transactional table you will get an error (ER_WARNING_NOT_COMPLETE_ROLLBACK) as a warning. All transaction-safe tables will be restored but any non-transaction-safe table will not change.

      If you are using START TRANSACTION or SET AUTOCOMMIT=0, you should use the MySQL binary log for backups instead of the older update log. Transactions are stored in the binary log in one chunk, upon COMMIT, to ensure that transactions which are rolled back are not stored. 「4.9.4 The Binary Update Log バイナリ更新ログ (3.23.15以上)」節参照.

      The following commands automatically end a transaction (as if you had done a COMMIT before executing the command):

      Command Command Command
      ALTER TABLE BEGIN CREATE INDEX
      DROP DATABASE DROP TABLE RENAME TABLE
      TRUNCATE

      You can change the isolation level for transactions with SET TRANSACTION ISOLATION LEVEL .... 「6.7.3 SET TRANSACTION 構文」節参照.

      6.7.2 LOCK TABLES/UNLOCK TABLES 構文

      LOCK TABLES tbl_name [AS alias] {READ [LOCAL] | [LOW_PRIORITY] WRITE}
            [, tbl_name [AS alias] {READ [LOCAL] | [LOW_PRIORITY] WRITE} ...]
...
UNLOCK TABLES

      LOCK TABLES はカレントのスレッドのためにテーブルをロックします。 UNLOCK TABLES はこのスレッドの全てのロックを解除します。 カレントスレッドによってロックされた全てのテーブルは、 スレッドが他の LOCK TABLES を発行した場合やサーバーが接続を閉じた場合、 自動で解除されます。

      To use LOCK TABLES in MySQL 4.0.2 you need the global LOCK TABLES privilege and a SELECT privilege on the involved tables. In MySQL 3.23 you need to have SELECT, insert, DELETE and UPDATE privileges for the tables.

      The main reasons to use LOCK TABLES are for emulating transactions or getting more speed when updating tables. This is explained in more detail later.

      スレッドがテーブルに READ ロックを持つ場合、そのスレッド(と他の全てのスレ ッド)はテーブルからの読み込みだけができます。スレッドがテーブルに WRITE ロックを持つ場合、 このスレッドだけがテーブルの READ と WRITE ができます。 他のスレッドはブロックされます。

      READ LOCAL と READ の違いは、READ LOCAL は、ロックが 保持されている間にコンフリクトしない INSERT ステートメントを実行で きることです。ただし、これはロックを保持している間に MySQL の外で データベースファイルを操作しようとする場合は使用できません。

      When you use LOCK TABLES, you must lock all tables that you are going to use and you must use the same alias that you are going to use in your queries! If you are using a table multiple times in a query (with aliases), you must get a lock for each alias!

      WRITE ロックは普通、できる限り更新を行わせるため、 READ ロックよりも優先順位が高くなっています。 これはあるスレッドが READ ロックをかけ、それ以外のスレッドが WRITE を要求した場合、 READ は、WRITE スレッドがロックをし、それを解除 するまで待つということです。 LOW_PRIORITY WRITE を使用すれば、 WRITE ロックを待っているスレッドに READ ロックを得させることができ ます。 LOW_PRIORITY WRITE は READ ロックをしているスレッドが一つもないと わかっている場合に使用すべきです。

      LOCK TABLES works as follows:

      1. Sort all tables to be locked in a internally defined order (from the user standpoint the order is undefined).
      2. If a table is locked with a read and a write lock, put the write lock before the read lock.
      3. Lock one table at a time until the thread gets all locks.

      This policy ensures that table locking is deadlock free. There is however other things one needs to be aware of with this schema:

      If you are using a LOW_PRIORITY WRITE lock for a table, this means only that MySQL will wait for this particlar lock until there is no threads that wants a READ lock. When the thread has got the WRITE lock and is waiting to get the lock for the next table in the lock table list, all other threads will wait for the WRITE lock to be released. If this becomes a serious problem with your application, you should consider converting some of your tables to transactions safe tables.

      You can safely kill a thread that is waiting for a table lock with KILL. 「4.5.5 KILL 構文」節参照.

      INSERT DELAYED で使用しているいかなるテーブルも、ロックすべきではありませ ん。この場合 INSERT は別のスレッドで行なわれるからです。

      通常、全ての単一の UPDATE 構文においては、テーブルをロックする必要はあり ません； スレッドは、他のスレッドが現在実行している SQL 文に干渉することができません。 これらはテーブルをロックした方がよい、まれな場合です：

      • テーブルをまとめて多くの操作を実行しようとする場合、使用しようとしているテー ブルをロックするととても速くなります。もちろん、他のスレッドは READ ロッ クされたテーブルの更新はできませんし、他のスレッドは WRITE ロックされた テーブルを読むことはできません。 The reason some things are faster under LOCK TABLES is that MySQL will not flush the key cache for the locked tables until UNLOCK TABLES is called (normally the key cache is flushed after each SQL statement). This speeds up inserting/updateing/deletes on MyISAM tables.
      • MySQL のトランザクションをサポートしない the storage engine を使用 している場合、他のスレッドが SELECT,UPDATE の間に来ないことを 保証したいならば、LOCK TABLES を使用する必要があります。 次の例は安全のためには LOCK TABLES を必要とします： 
        mysql> LOCK TABLES trans READ, customer WRITE;
mysql> SELECT sum(value) FROM trans WHERE customer_id= some_id;
mysql> UPDATE customer SET total_value=sum_from_previous_statement
    ->        WHERE customer_id=some_id;
mysql> UNLOCK TABLES;
        LOCK TABLES を使用しない場合、SELECT の実行と UPDATE の 実行を行う間に、他のスレッドが新しい trans 行を挿入する隙ができます。

      インクリメント アップデイト (UPDATE customer SET value=value+new_value) または LAST_INSERT_ID() 関数の使用により、多くの場合 LOCK TABLES を回避 できます。

      いくつかの場合、ユーザレベルロック: GET_LOCK() と RELEASE_LOCK() の使用 によっても解決できます。これらのロックはサーバ内のハッシュテーブル内に保 持され、高速のため pthread_mutex_lock() で実装されました。 「6.3.6.2 その他の関数」節参照.

      ロックポリシーのさらなる情報については 「5.3.1 MySQL はどのようにテーブルをロックするか」節 を見てくださ い。

      You can lock all tables in all databases with read locks with the FLUSH TABLES WITH READ LOCK command. 「4.5.3 FLUSH 構文」節参照. This is very convenient way to get backups if you have a filesystem, like Veritas, that can take snapshots in time.

      NOTE: LOCK TABLES is not transaction-safe and will automatically commit any active transactions before attempting to lock the tables.

      6.7.3 SET TRANSACTION 構文

      SET [GLOBAL | SESSION] TRANSACTION ISOLATION LEVEL
{ READ UNCOMMITTED | READ COMMITTED | REPEATABLE READ | SERIALIZABLE }

      Sets the transaction isolation level for the global, whole session or the next transaction.

      The default behaviour is to set the isolation level for the next (not started) transaction. If you use the GLOBAL keyword, the statement sets the default transaction level globally for all new connections created from that point on. You will need the SUPER privilege to do this. Using the SESSION keyword sets the default transaction level for all future transactions performed on the current connection.

      You can set the default global isolation level for mysqld with --transaction-isolation=.... 「4.1.1 mysqld コマンド行オプション」節参照.

      6.8 MySQL Full-text Search

      As of Version 3.23.23, MySQL has support for full-text indexing and searching. Full-text indexes in MySQL are an index of type FULLTEXT. FULLTEXT indexes are used with MyISAM tables and can be created from CHAR, VARCHAR, or TEXT columns at CREATE TABLE time or added later with ALTER TABLE or CREATE INDEX. For large datasets, it will be much faster to load your data into a table that has no FULLTEXT index, then create the index with ALTER TABLE (or CREATE INDEX). Loading data into a table that already has a FULLTEXT index will be slower.

      Full-text searching is performed with the MATCH() function. 

      mysql> CREATE TABLE articles (
    ->   id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
    ->   title VARCHAR(200),
    ->   body TEXT,
    ->   FULLTEXT (title,body)
    -> );
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO articles VALUES
    -> (NULL,'MySQL Tutorial', 'DBMS stands for DataBase ...'),
    -> (NULL,'How To Use MySQL Efficiently', 'After you went through a ...'),
    -> (NULL,'Optimising MySQL','In this tutorial we will show ...'),
    -> (NULL,'1001 MySQL Tricks','1. Never run mysqld as root. 2. ...'),
    -> (NULL,'MySQL vs. YourSQL', 'In the following database comparison ...'),
    -> (NULL,'MySQL Security', 'When configured properly, MySQL ...');
Query OK, 6 rows affected (0.00 sec)
Records: 6  Duplicates: 0  Warnings: 0

mysql> SELECT * FROM articles
    ->          WHERE MATCH (title,body) AGAINST ('database');
+----+-------------------+------------------------------------------+
| id | title             | body                                     |
+----+-------------------+------------------------------------------+
|  5 | MySQL vs. YourSQL | In the following database comparison ... |
|  1 | MySQL Tutorial    | DBMS stands for DataBase ...             |
+----+-------------------+------------------------------------------+
2 rows in set (0.00 sec)

      The MATCH() function performs a natural language search for a string against a text collection (a set of one or more columns included in a FULLTEXT index). The search string is given as the argument to AGAINST(). The search is performed in case-insensitive fashion. For every row in the table, MATCH() returns a relevance value, that is, a similarity measure between the search string and the text in that row in the columns named in the MATCH() list.

      When MATCH() is used in a WHERE clause (see example above) the rows returned are automatically sorted with highest relevance first. Relevance values are non-negative floating-point numbers. Zero relevance means no similarity. Relevance is computed based on the number of words in the row, the number of unique words in that row, the total number of words in the collection, and the number of documents (rows) that contain a particular word.

      It is also possible to perform a boolean mode search. This is explained later in the section.

      The preceding example is a basic illustration showing how to use the MATCH() function. Rows are returned in order of decreasing relevance.

      The next example shows how to retrieve the relevance values explicitly. As neither WHERE nor ORDER BY clauses are present, returned rows are not ordered. 

      mysql> SELECT id,MATCH title,body AGAINST ('Tutorial') FROM articles;
+----+-----------------------------------------+
| id | MATCH (title,body) AGAINST ('Tutorial') |
+----+-----------------------------------------+
|  1 |                        0.64840710366884 |
|  2 |                                       0 |
|  3 |                        0.66266459031789 |
|  4 |                                       0 |
|  5 |                                       0 |
|  6 |                                       0 |
+----+-----------------------------------------+
6 rows in set (0.00 sec)

      The following example is more complex. The query returns the relevance and still sorts the rows in order of decreasing relevance. To achieve this result, you should specify MATCH() twice. This will cause no additional overhead, because the MySQL optimiser will notice that the two MATCH() calls are identical and invoke the full-text search code only once. 

      mysql> SELECT id, body, MATCH (title,body) AGAINST
    -> ('Security implications of running MySQL as root') AS score
    -> FROM articles WHERE MATCH (title,body) AGAINST
    -> ('Security implications of running MySQL as root');
+----+-------------------------------------+-----------------+
| id | body                                | score           |
+----+-------------------------------------+-----------------+
|  4 | 1. Never run mysqld as root. 2. ... | 1.5055546709332 |
|  6 | When configured properly, MySQL ... |   1.31140957288 |
+----+-------------------------------------+-----------------+
2 rows in set (0.00 sec)

      MySQL uses a very simple parser to split text into words. A ``word'' is any sequence of characters consisting of letters, digits, `'', and `_'. Any ``word'' that is present in the stopword list or is just too short (3 characters or less) is ignored.

      Every correct word in the collection and in the query is weighted according to its significance in the query or collection. This way, a word that is present in many documents will have lower weight (and may even have a zero weight), because it has lower semantic value in this particular collection. Otherwise, if the word is rare, it will receive a higher weight. The weights of the words are then combined to compute the relevance of the row.

      Such a technique works best with large collections (in fact, it was carefully tuned this way). For very small tables, word distribution does not reflect adequately their semantic value, and this model may sometimes produce bizarre results. 

      mysql> SELECT * FROM articles WHERE MATCH (title,body) AGAINST ('MySQL');
Empty set (0.00 sec)

      The search for the word MySQL produces no results in the above example, because that word is present in more than half the rows. As such, it is effectively treated as a stopword (that is, a word with zero semantic value). This is the most desirable behaviour -- a natural language query should not return every second row from a 1GB table.

      A word that matches half of rows in a table is less likely to locate relevant documents. In fact, it will most likely find plenty of irrelevant documents. We all know this happens far too often when we are trying to find something on the Internet with a search engine. It is with this reasoning that such rows have been assigned a low semantic value in this particular dataset.

      As of Version 4.0.1, MySQL can also perform boolean full-text searches using the IN BOOLEAN MODE modifier. 

      mysql> SELECT * FROM articles WHERE MATCH (title,body)
    ->     AGAINST ('+MySQL -YourSQL' IN BOOLEAN MODE);
+----+------------------------------+-------------------------------------+
| id | title                        | body                                |
+----+------------------------------+-------------------------------------+
|  1 | MySQL Tutorial               | DBMS stands for DataBase ...        |
|  2 | How To Use MySQL Efficiently | After you went through a ...        |
|  3 | Optimising MySQL             | In this tutorial we will show ...   |
|  4 | 1001 MySQL Tricks            | 1. Never run mysqld as root. 2. ... |
|  6 | MySQL Security               | When configured properly, MySQL ... |
+----+------------------------------+-------------------------------------+

      This query retrieved all the rows that contain the word MySQL (note: the 50% threshold is not used), but that do not contain the word YourSQL. Note that a boolean mode search does not automatically sort rows in order of decreasing relevance. You can see this from result of the preceding query, where the row with the highest relevance (the one that contains MySQL twice) is listed last, not first. A boolean full-text search can also work even without a FULLTEXT index, although it would be slow.

      The boolean full-text search capability supports the following operators:

      +
      A leading plus sign indicates that this word must be present in every row returned.
      -
      A leading minus sign indicates that this word must not be present in any row returned.
      By default (when neither plus nor minus is specified) the word is optional, but the rows that contain it will be rated higher. This mimicks the behaviour of MATCH() ... AGAINST() without the IN BOOLEAN MODE modifier.
      < >
      These two operators are used to change a word's contribution to the relevance value that is assigned to a row. The < operator decreases the contribution and the > operator increases it. See the example below.
      ( )
      Parentheses are used to group words into subexpressions.
      ~
      A leading tilde acts as a negation operator, causing the word's contribution to the row relevance to be negative. It's useful for marking noise words. A row that contains such a word will be rated lower than others, but will not be excluded altogether, as it would be with the - operator.
      *
      An asterisk is the truncation operator. Unlike the other operators, it should be appended to the word, not prepended.
      "
      The phrase, that is enclosed in double quotes ", matches only rows that contain this phrase literally, as it was typed.

      And here are some examples:

      apple banana
      find rows that contain at least one of these words.
      +apple +juice
      ... both words.
      +apple macintosh
      ... word ``apple'', but rank it higher if it also contain ``macintosh''.
      +apple -macintosh
      ... word ``apple'' but not ``macintosh''.
      +apple +(>pie <strudel)
      ... ``apple'' and ``pie'', or ``apple'' and ``strudel'' (in any order), but rank ``apple pie'' higher than ``apple strudel''.
      apple*
      ... ``apple'', ``apples'', ``applesauce'', and ``applet''.
      "some words"
      ... ``some words of wisdom'', but not ``some noise words''.

      6.8.1 Full-text Restrictions

      • All parameters to the MATCH() function must be columns from the same table that is part of the same FULLTEXT index, unless the MATCH() is IN BOOLEAN MODE.
      • The MATCH() column list must exactly match the column list in some FULLTEXT index definition for the table, unless this MATCH() is IN BOOLEAN MODE.
      • The argument to AGAINST() must be a constant string.

      6.8.2 Fine-tuning MySQL Full-text Search

      Unfortunately, full-text search has few user-tunable parameters yet, although adding some is very high on the TODO. If you have a MySQL source distribution ( 「2.3 MySQL ソースディストリビューションのインストール」節参照), you can exert more control over full-text searching behaviour.

      Note that full-text search was carefully tuned for the best searching effectiveness. Modifying the default behaviour will, in most cases, only make the search results worse. Do not alter the MySQL sources unless you know what you are doing!

      • The minimum length of words to be indexed is defined by the MySQL variable ft_min_word_len. 「4.5.6.4 SHOW VARIABLES」節参照. Change it to the value you prefer, and rebuild your FULLTEXT indexes. (This variable is only available from MySQL version 4.0.)
      • The stopword list can be loaded from file specified by ft_stopword_file variable. 「4.5.6.4 SHOW VARIABLES」節参照. Rebuild your FULLTEXT indexes after modifying the stopword list. (This variable is only available from MySQL version 4.0.10 and onwards)
      • The 50% threshold is determined by the particular weighting scheme chosen. To disable it, change the following line in `myisam/ftdefs.h': 
        #define GWS_IN_USE GWS_PROB
        To: 
        #define GWS_IN_USE GWS_FREQ
        Then recompile MySQL. There is no need to rebuild the indexes in this case. Note: by doing this you severely decrease MySQL's ability to provide adequate relevance values for the MATCH() function. If you really need to search for such common words, it would be better to search using IN BOOLEAN MODE instead, which does not observe the 50% threshold.
      • Sometimes the search engine maintainer would like to change the operators used for boolean full-text searches. These are defined by the ft_boolean_syntax variable. 「4.5.6.4 SHOW VARIABLES」節参照. Still, this variable is read-only, its value is set in `myisam/ft_static.c'.

      For those changes that require you to rebuild your FULLTEXT indexes, the easiest way to do so for a MyISAM table is to use the following statement, which rebuilds the index file: 

      mysql> REPAIR TABLE tbl_name QUICK;

      6.8.3 Full-text Search TODO

      • Make all operations with FULLTEXT index faster.
      • Proximity operators
      • Support for "always-index words". They could be any strings the user wants to treat as words, examples are "C++", "AS/400", "TCP/IP", etc.
      • Support for full-text search in MERGE tables.
      • Support for multi-byte charsets.
      • Make stopword list to depend of the language of the data.
      • Stemming (dependent of the language of the data, of course).
      • Generic user-suppliable UDF preparser.
      • Make the model more flexible (by adding some adjustable parameters to FULLTEXT in CREATE/ALTER TABLE).

      6.9 MySQL Query Cache (4.0.1以上)

      From version 4.0.1, MySQL server features a Query Cache. When in use, the query cache stores the text of a SELECT query together with the corresponding result that was sent to the client. If an identical query is later received, the server will retrieve the results from the query cache rather than parsing and executing the same query again.

      NOTE: The query cache does not return stale data. When data is modified, any relevant entries in the query cache are flushed.

      The query cache is extremely useful in an environment where (some) tables don't change very often and you have a lot of identical queries. This is a typical situation for many web servers that use a lot of dynamic content.

      Below is some performance data for the query cache. (These results were generated by running the MySQL benchmark suite on a Linux Alpha 2 x 500 MHz with 2GB RAM and a 64MB query cache):

      • If all of the queries you're performing are simple (such as selecting a row from a table with one row); but still differ so that the queries can not be cached, the overhead for having the query cache active is 13%. This could be regarded as the worst case scenario. However, in real life, queries are much more complicated than our simple example so the overhead is normally significantly lower.
      • Searches after one row in a one row table is 238% faster. This can be regarded as close to the minimum speedup to be expected for a query that is cached.
      • If you want to disable the query cache code set query_cache_size=0. By disabling the query cache code there is no noticeable overhead. (query cache can be excluded from code with help of configure option --without-query-cache)

      6.9.1 How The Query Cache Operates

      Queries are compared before parsing, thus 

      SELECT * FROM tbl_name

      and 

      Select * from tbl_name

      are regarded as different queries for query cache, so queries need to be exactly the same (byte for byte) to be seen as identical. In addition, a query may be seen as different if for instance one client is using a new communication protocol format or another character set than another client.

      Queries that uses different databases, uses different protocol versions or the uses different default character sets are considered different queries and cached separately.

      The cache does work for SELECT CALC_ROWS ... and SELECT FOUND_ROWS() ... type queries because the number of found rows is also stored in the cache.

      If query result was returned from query cache then status variable Com_select will not be increased, but Qcache_hits will be. 「6.9.4 Query Cache Status and Maintenance」節参照.

      If a table changes (INSERT, UPDATE, DELETE, TRUNCATE, ALTER or DROP TABLE|DATABASE), then all cached queries that used this table (possibly through a MRG_MyISAM table!) become invalid and are removed from the cache.

      Transactional InnoDB tables that have been changed will be invalidated when a COMMIT is performed.

      A query cannot be cached if it contains one of the functions:
      Function Function Function
      User-Defined Functions CONNECTION_ID FOUND_ROWS
      GET_LOCK RELEASE_LOCK LOAD_FILE
      MASTER_POS_WAIT NOW SYSDATE
      CURRENT_TIMESTAMP CURDATE CURRENT_DATE
      CURTIME CURRENT_TIME DATABASE
      ENCRYPT (with one parameter) LAST_INSERT_ID RAND
      UNIX_TIMESTAMP (without parameters) USER BENCHMARK

      Nor can a query be cached if it contains user variables, references the mysql system database, is of the form SELECT ... IN SHARE MODE, SELECT ... INTO OUTFILE ..., SELECT ... INTO DUMPFILE ... or of the form SELECT * FROM AUTOINCREMENT_FIELD IS NULL (to retrieve last insert id - ODBC work around).

      However, FOUND ROWS() will return the correct value, even if the preceding query was fetched from the cache.

      In case a query does not use any tables, or uses temporary tables, or if the user has a column privilege for any of the involved tables, that query will not be cached.

      Before a query is fetched from the query cache, MySQL will check that the user has SELECT privilege to all the involved databases and tables. If this is not the case, the cached result will not be used.

      6.9.2 Query Cache Configuration

      The query cache adds a few MySQL system variables for mysqld which may be set in a configuration file, on the command-line when starting mysqld.

      • query_cache_limit Don't cache results that are bigger than this. (Default 1M).
      • query_cache_size The amount of memory (specified in bytes) allocated to store results from old queries. If this is 0, the query cache is disabled (default).
      • query_cache_type This may be set (only numeric) to
        Option Description
        0 (OFF, don't cache or retrieve results)
        1 (ON, cache all results except SELECT SQL_NO_CACHE ... queries)
        2 (DEMAND, cache only SELECT SQL_CACHE ... queries)

      Inside a thread (connection), the behaviour of the query cache can be changed from the default. The syntax is as follows:

      QUERY_CACHE_TYPE = OFF | ON | DEMAND QUERY_CACHE_TYPE = 0 | 1 | 2

      Option Description
      0 or OFF Don't cache or retrieve results.
      1 or ON Cache all results except SELECT SQL_NO_CACHE ... queries.
      2 or DEMAND Cache only SELECT SQL_CACHE ... queries.

      6.9.3 Query Cache Options in SELECT

      There are two possible query cache related parameters that may be specified in a SELECT query:

      Option Description
      SQL_CACHE If QUERY_CACHE_TYPE is DEMAND, allow the query to be cached. If QUERY_CACHE_TYPE is ON, this is the default. If QUERY_CACHE_TYPE is OFF, do nothing.
      SQL_NO_CACHE Make this query non-cachable, don't allow this query to be stored in the cache.

      6.9.4 Query Cache Status and Maintenance

      With the FLUSH QUERY CACHE command you can defragment the query cache to better utilise its memory. This command will not remove any queries from the cache. FLUSH TABLES also flushes the query cache.

      The RESET QUERY CACHE command removes all query results from the query cache.

      You can check whether the query cache is present in your MySQL version: 

      mysql> SHOW VARIABLES LIKE 'have_query_cache';
+------------------+-------+
| Variable_name    | Value |
+------------------+-------+
| have_query_cache | YES   |
+------------------+-------+
1 row in set (0.00 sec)

      You can monitor query cache performance in SHOW STATUS:

      Variable Description
      Qcache_queries_in_cache Number of queries registered in the cache.
      Qcache_inserts Number of queries added to the cache.
      Qcache_hits Number of cache hits.
      Qcache_lowmem_prunes Number of queries that were deleted from cache because of low memory.
      Qcache_not_cached Number of non-cached queries (not cachable, or due to QUERY_CACHE_TYPE).
      Qcache_free_memory Amount of free memory for query cache.
      Qcache_free_blocks Number of free memory blocks in query cache.
      Qcache_total_blocks Total number of blocks in query cache.

      Total number of queries = Qcache_inserts + Qcache_hits + Qcache_not_cached.

      The query cache uses variable length blocks, so Qcache_total_blocks and Qcache_free_blocks may indicate query cache memory fragmentation. After FLUSH QUERY CACHE only a single (big) free block remains.

      Note: Every query needs a minimum of two blocks (one for the query text and one or more for the query results). Also, every table that is used by a query needs one block, but if two or more queries use same table only one block needs to be allocated.

      You can use the Qcache_lowmem_prunes status variable to tune the query cache size. It counts the number of queries that have been removed from the cache to free up memory for caching new queries. The query cache uses a least recently used (LRU) strategy to decide which queries to remove from the cache.

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Regexp.html0100644000175100001560000002036010021471264015705 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - G MySQL の正規表現 Go to the first, previous, next, last section, table of contents.

      G MySQL の正規表現

      A regular expression (regex) is a powerful way of specifying a complex search.

      MySQL は正規表現の regular Henry Spencers 実装を使用します。 そしてこれは POSIX 1003.2 に一致することが 目的です。MySQL は拡張 バージョンを使用します。

      これは詳細を省いた簡単なリファレンスです。 さらに正確な情報は Henry Spencers regex(7) マニュアルを見てください。 これはソース配布に含まれています。 「C Credits」節参照.

      正規表現は文字列の組み合わせて記述されます。 もっとも簡単な場合は、非特殊文字の一文字です。例えば、 regexp hello は hello と適合し、 他には適合しません。

      簡単でない正規表現は、1つの文字列以上に適合できるような、いくつかの 特殊な構成を使用します。例えば、regexp hello|word は 文字列 hello と文字列 word に適合します。

      そしてさらに複雑な例 regexp B[an]*s は、 文字列 Bananas, Baaaaas, Bs のどれか、 そして B で始まり a や n が 任意の数続き、s で終わるような他の文字列に適合します。

      正規表現では、次の特殊文字/構成が使用できます：

      ^
      文字列全体の始まり。 
      mysql> SELECT "fo\nfo" REGEXP "^fo$";           -> 0
mysql> SELECT "fofo" REGEXP "^fo";              -> 1
      $
      文字列全体の終り。 
      mysql> SELECT "fo\no" REGEXP "^fo\no$";         -> 1
mysql> SELECT "fo\no" REGEXP "^fo$";            -> 0
      .
      任意の文字 (改行含む)。 
      mysql> SELECT "fofo" REGEXP "^f.*";             -> 1
mysql> SELECT "fo\nfo" REGEXP "^f.*";           -> 1
      a*
      0個以上の文字 a の並び。 
      mysql> SELECT "Ban" REGEXP "^Ba*n";             -> 1
mysql> SELECT "Baaan" REGEXP "^Ba*n";           -> 1
mysql> SELECT "Bn" REGEXP "^Ba*n";              -> 1
      a+
      文字 a が 1個以上並ぶ。 
      mysql> SELECT "Ban" REGEXP "^Ba+n";             -> 1
mysql> SELECT "Bn" REGEXP "^Ba+n";              -> 0
      a?
      0 または 1個の文字 a。 
      mysql> SELECT "Bn" REGEXP "^Ba?n";              -> 1
mysql> SELECT "Ban" REGEXP "^Ba?n";             -> 1
mysql> SELECT "Baan" REGEXP "^Ba?n";            -> 0
      de|abc
      de か abc にマッチ。 
      mysql> SELECT "pi" REGEXP "pi|apa";             -> 1
mysql> SELECT "axe" REGEXP "pi|apa";            -> 0
mysql> SELECT "apa" REGEXP "pi|apa";            -> 1
mysql> SELECT "apa" REGEXP "^(pi|apa)$";        -> 1
mysql> SELECT "pi" REGEXP "^(pi|apa)$";         -> 1
mysql> SELECT "pix" REGEXP "^(pi|apa)$";        -> 0
      (abc)*
      文字列 abc の 0 回以上の並びにマッチ。 
      mysql> SELECT "pi" REGEXP "^(pi)*$";            -> 1
mysql> SELECT "pip" REGEXP "^(pi)*$";           -> 0
mysql> SELECT "pipi" REGEXP "^(pi)*$";          -> 1
      {1}
      {2,3}
      多くの発生に適合する regexp の記述する一般的な方法。 The is a more general way of writing regexps that match many occurrences of the previous atom.
      a*
      Can be written as a{0,}.
      a+
      Can be written as a{1,}.
      a?
      Can be written as a{0,1}.
      さらに正確には、1つの整数 i とコンマ無しを含む修飾が続くアトムは、 厳密にアトムに適合する i 回の並びに適合します。 整数 i とコンマを含む修飾が続くアトムは、 アトムに適合する i 回以上の並びに適合します。 整数 i と j を含む装飾が続くアトムは、 アトムに適 合する i 回から j 回までの並びに適合します。 両方の引数は 0 から RE_DUP_MAX (default 255) の間でなければなりません。 そして引数が2つある場合、2番目は1番目よりも大きいか同じでなければなりません。
      [a-dX]
      [^a-dX]
      a, b, c, d, X のどれかの文字 (^ を使用するとどれでもない文字) にマッチ。 ] 文字を含めるには、 [ のあとに続いてすぐに書く必要があります。 - 文字を含めるには最初か最後に書く必要があります。 [0-9] は任意 の10進数値に適合します。 [] ペア内部の定義された 意味を持たない全ての文字は、特殊な意味を持たず、それ自身にだけ適合します。 
      mysql> SELECT "aXbc" REGEXP "[a-dXYZ]";         -> 1
mysql> SELECT "aXbc" REGEXP "^[a-dXYZ]$";       -> 0
mysql> SELECT "aXbc" REGEXP "^[a-dXYZ]+$";      -> 1
mysql> SELECT "aXbc" REGEXP "^[^a-dXYZ]+$";     -> 0
mysql> SELECT "gheis" REGEXP "^[^a-dXYZ]+$";    -> 1
mysql> SELECT "gheisa" REGEXP "^[^a-dXYZ]+$";   -> 0
      [[.characters.]]
      照合要素(collating element)の文字の並び。 並びは括弧表現リストの一つの要素です。 複数文字の照合要素を含む括弧表現は一つ以上の文字に適合します。 例えば、照合並びが ch 照合要素を含む場合、 正規表現 [[.ch.]]*c は chchcc の最初の5文字に適合します。
      [=character_class=]
      同等のクラス。その一つと等しい全ての照合要素の文字の並びを表します。それ自身も含みます。 例えば、o と (+) が同等クラスのメンバである場合、 [[=o=]], [[=(+)=]], [[=(+)=]] は全て同義語です。 同等クラスは範囲の終了位置にはなりません。
      [:character_class:]
      括弧表現の内部で、[: と :] で括られた文字クラスの名前は、 そのクラスに属する全ての文字のリストを表します。標準文字クラス名は:
      Name Name Name
      alnum digit punct
      alpha graph space
      blank lower upper
      cntrl print xdigit
      これらは ctype(3) マニュアルページに記載されている文字クラスを表します。 ロケールが他のを提供することもあります。文字クラスは範囲の終了位置としては使えません。 
      mysql> SELECT "justalnums" REGEXP "[[:alnum:]]+";       -> 1
mysql> SELECT "!!" REGEXP "[[:alnum:]]+";               -> 0
      [[:<:]]
      [[:>:]]
      それぞれ、単語の始めと終りの空文字列に適合します。単語は、単語文字が前後 にない単語文字の並びとして定義されます。単語文字は alnum 文字 (ctype(3) で定義されます) と下線(underscore ； _)です。 
      mysql> SELECT "a word a" REGEXP "[[:<:]]word[[:>:]]";      -> 1
mysql> SELECT "a xword a" REGEXP "[[:<:]]word[[:>:]]";     -> 0

      mysql> SELECT "weeknights" REGEXP "^(wee|week)(knights|nights)$"; -> 1

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/Flags/0040775000175100001560000000000010007313173012675 5ustar takeshisamysql-4.00.12/Flags/czech-republic.png0100644000175100001560000000042110007313166016274 0ustar takeshisaPNG  IHDR nv:FrW故CI:4誰 久UU擻ｼ,%C=`箇LL緬 '集dPPz[輝糢CC悪穽TTsS卯瞎:;芝L[)"ojkb羊>?>>即 IENDB`mysql-4.00.12/Flags/brazil.png0100644000175100001560000000114210007313166014661 0ustar takeshisaPNG  IHDR nvPLTE梧Jc顋B啄9瑞O潔咲H件H綴窓Ai橙"醐井Q]萌 居оo:随9錘ュ駈桾.腫E蛋\葡W筆0竣(咋夥>件穴搏6情丈"乞\N童搏8恣`魅苦d髮碁苻PゅZ駈-邪灸zo鰤鬢件H直碪=摧_呆#醐 居f嵐+諮!乞罷9+施矩飫tEXtSoftwaregif2png 2.2.59勲IDATxg{Qu0z"zI$$: F潁{w-侶肱{"]MRwrU'L%DFs0=9Dq*_#S9|cZ-@?  vh穩XhUMjGL煌ao* }h晴<8拙t @`呷bYLACaf執2`L`!|槨6IBB諧jg?^5~r,o赳姥弃M 8-m J 90NIENDB`mysql-4.00.12/Flags/bulgaria.png0100644000175100001560000000024610007313166015170 0ustar takeshisaPNG  IHDR SwwPLTE3烟$tEXtSoftwaregif2png 2.2.59勲-IDATxc`@,.(6LJ(@QF5006分(IENDB`mysql-4.00.12/Flags/canada.png0100644000175100001560000000063210007313171014604 0ustar takeshisaPNG  IHDR nvPLTEUV迯軣鶴酥畔騅懿蓙88韶<<靫幃査ddHH**貔総津腮22騙摯裴ccrsVV黶疇ij ~~齠tt++靤吩で鴪荅OO靨尢QR蜑觴種様~%tEXtSoftwaregif2png 2.2.59勲IDATxc` !@F HAi@u~ L#G室鑓B,鴪\ 聒X 繁繁詈乏qcU` ekI`w"%解**鰔}’')&ah/$uD5)L4OX逾LIENDB`mysql-4.00.12/Flags/chile.png0100644000175100001560000000047110007313170014461 0ustar takeshisaPNG  IHDR nvrPLTE毬鞅懦播:3宙蓴,&6/琢韶 吾碌`[仔93案楚' >8ws埆紫策hb蒟鷂球(!ni剽蛻 fa 各a[浴瑜tEXtSoftwaregif2png 2.2.59勲`IDATx輓G EQ {o塑-@A燔0F匿"偐z#@千00q_ `舳D0c?^O=s?0硅5Ip2Mh?P70 IENDB`mysql-4.00.12/Flags/china.png0100644000175100001560000000041510007313170014455 0ustar takeshisaPNG  IHDR nvQPLTEK;}鮹Xw鏃L %8v *攀mktEXtSoftwaregif2png 2.2.59勲UIDATx;0#>Je4@杜!言 aB/WHTq6>Xn凄X将'jA>e'JEIENDB`mysql-4.00.12/Flags/croatia.png0100644000175100001560000000116410007313171015020 0ustar takeshisaPNG  IHDR nvGPLTE鰛6K】fgnm`aLF叛哦枝yzinn騅憫ﾝrr<俛TU貎身 *+韶Y[KLvx+競茘L 戟WW妓;;\*[\Ze)W)<%ツ 勒X5aj4,甜ab44t5[軈倉::貎栴瘁蟯関ZZzvt/1wpq腱р11貅G短G薇 蛭 螻劾)*[\`9j軻同-/)=Oe`}^_yCDTd))suu腑ヌJ軼奴kk ^_]BioofgkzuCy4貅純$tEXtSoftwaregif2png 2.2.59勲IDATxc` 跟Rz;riT`h冷]~6vEC"R#QLP)3[4梭 vPA(匪Y&)"Px霹虹鵬yHP`!-,-C握shfh..+祷Yy\q(6Lc寛FQ6皃6rHB@H@;E%YMg3 C悁3tHIENDB`mysql-4.00.12/Flags/great-britain.png0100644000175100001560000000151510007313165016131 0ustar takeshisaPNG  IHDR nvPLTEgbff 湖缶==5.態NNyz>7UO輔勘桍頑滷aa 狗淅 tu蕾雅鍛<倒゜++衍)"冗竚擲地-.惘草毯剤z{^_%巡茫/)窃wtEXtSoftwaregif2png 2.2.59勲cIDATxc` Jya 砺'sg U*回*忍:嗷" M杪\CP{@aP]`r9jO ec1-!泪揺!:wA璢AN;S塘ld~(=F>S`z6CFlr6$wk酎<IENDB`mysql-4.00.12/Flags/hungary.png0100644000175100001560000000024610007313171015053 0ustar takeshisaPNG  IHDR SwwPLTEWWFF-tEXtSoftwaregif2png 2.2.59勲-IDATxc`@牝(6LJ(@5F800 ;的h IENDB`mysql-4.00.12/Flags/iceland.png0100644000175100001560000000033110007313171014770 0ustar takeshisaPNG  IHDR Sww*PLTE耄怏鴻勃給樟血兎酘隙勃"tEXtSoftwaregif2png 2.2.59勲HIDATxc`@　ヽ;\C NIJ9IENDB`mysql-4.00.12/Flags/italy.png0100644000175100001560000000022610007313173014520 0ustar takeshisaPNG  IHDR SwwPLTE黻 顴FtEXtSoftwaregif2png 2.2.59勲IDATxc`@LJ@ 惰@`0*@:?^IENDB`mysql-4.00.12/Flags/japan.png0100644000175100001560000000056310007313166014475 0ustar takeshisaPNG  IHDR nvPLTEff==NN鑢杢rrvvXY艸``貍裳WX鰤淮**hhjk裴EFvv繞鰛榕UU闖靦嗅00lm軻瀞CDRS軈胎kk||OO駢摧蜑&6YtEXtSoftwaregif2png 2.2.59勲IDATxc` T+PPd滴_\t+Q T$^爾6lH $u(`AVE%, 0bQ$/ZXl@Q %g的@ l0B=俄8鼎E`EN┯IENDB`mysql-4.00.12/Flags/singapore.png0100644000175100001560000000061010007313173015362 0ustar takeshisaPNG  IHDR nvPLTEYZ,- @@>?艸 *+RS貊薯毫))gg MN觚固~~HH黴獰YYlm}}PP藪TT''罅” KK""蜑T~RtEXtSoftwaregif2png 2.2.59勲IDATxc` $EW;(R`鏑@S_B[Ci9 if &V C x9$DI> D孰%津0E愛6 4Pa着M=)F~q q^&vT` HLgdVIENDB`mysql-4.00.12/Flags/poland.png0100644000175100001560000000023510007313173014653 0ustar takeshisaPNG  IHDR SwwPLTE韶/]tEXtSoftwaregif2png 2.2.59勲'IDATxc`@,.(a0 &%誓l :*AX|IENDB`mysql-4.00.12/Flags/portugal.png0100644000175100001560000000114010007313167015232 0ustar takeshisaPNG  IHDR nvMPLTE?HXhd伉$祭焉聿YＹ;h/匪na"芝$M F/祟礒5+`氛牴' 拾聳XP(1戳浸俛.'青>4elOE浣&綺O睛謡c[妻3VP吠)a0wQ齋袙?dS簧 McRn篌6蓄砿)"乗{闃)N}s綏"ptEXtSoftwaregif2png 2.2.59勲IDATxc` a  @>sN d瞠mq)疼駟f2快菊 0C<[ > U7fG\K LScR2*靱uV63M的 .\[EU_26+6O yF ;3[)`1du KﾂP次9Rz 4x"登ラ欷z}@ IENDB`mysql-4.00.12/Flags/romania.png0100644000175100001560000000022610007313172015023 0ustar takeshisaPNG  IHDR SwwPLTE菊 utEXtSoftwaregif2png 2.2.59勲IDATxc`@LJ@惰@`0*@:U;鼎OIENDB`mysql-4.00.12/Flags/russia.png0100644000175100001560000000024610007313172014705 0ustar takeshisaPNG  IHDR SwwPLTE3菊猊rtEXtSoftwaregif2png 2.2.59勲-IDATxc`@,.(6( I (FQ00FM;徹(yIENDB`mysql-4.00.12/Flags/south-africa1.png0100644000175100001560000000120710007313167016047 0ustar takeshisaPNG  IHDR nvAPLTE蝟wwvvLF番幀孛__墻pp咀ii KKgS<< 限--梦幻 謾E? 卵6,笈罎と衄矧hh轢処循御TTF@%%H 罍}}ZZt誄`QQ664411莓**((艾##槙杢 癘痰罍=忠昼炸蛬悴癖喝kJtEXtSoftwaregif2png 2.2.59勲IDATxc` TTTd=e TTBM\T`QS' $,@T聴a'3D款;*Z/" <6]Wh>BqbxLP2ec_ @咆P訶eQP+$"狎・ 44「z9ＫD@]81C@糺辰$鞍Dq[b)2估qz(!IENDB`mysql-4.00.12/Flags/south-africa.png0100644000175100001560000000120710007313166015765 0ustar takeshisaPNG  IHDR nvAPLTE蝟wwvvLF番幀孛__墻pp咀ii KKgS<< 限--梦幻 謾E? 卵6,笈罎と衄矧hh轢処循御TTF@%%H 罍}}ZZt誄`QQ664411莓**((艾##槙杢 癘痰罍=忠昼炸蛬悴癖喝kJtEXtSoftwaregif2png 2.2.59勲IDATxc` TTTd=e TTBM\T`QS' $,@T聴a'3D款;*Z/" <6]Wh>BqbxLP2ec_ @咆P訶eQP+$"狎・ 44「z9ＫD@]81C@糺辰$鞍Dq[b)2估qz(!IENDB`mysql-4.00.12/Flags/south-korea.png0100644000175100001560000000125310007313165015641 0ustar takeshisaPNG  IHDR nvMPLTE迯韶 NN9騅慄播yyylnD> kkk eee髑5/ccc_cUUU迯KKKGGG汎EEECCC韶韲銕厮迪跛粐朽玻樛榴慓pk 蛍嶽佩們銓詑托捶査埼褪裴幹完旭::KujX{wTm鴻艾xxxvvvuNppp佻5ddd闖```yyZZZXXXVVV齠RRRPPPJJJFFF8DDD齠齣髑闖闕迯kW齠,烝6毫殼忻~孑嗷様hZkf侘&&裼鼕wtEXtSoftwaregif2png 2.2.59勲IDATxc` "8thTiR EQe*鮒%9慇 EVdA燭5w0-筺ha ,@/@ x A^購肇綸9444M**k$`U knEDd`*P[DO簍xdYA D_C檀 靦CR' 讒f馮#) G悵phd7戀あ(偖FRv@L#Y起y寤IENDB`mysql-4.00.12/Flags/spain.png0100644000175100001560000000025110007313167014511 0ustar takeshisaPNG  IHDR SwwPLTEHbtEXtSoftwaregif2png 2.2.59勲0IDATxc`@LJ(@FA 誓Q@ xCu3 榠IENDB`mysql-4.00.12/Flags/sweden.png0100644000175100001560000000032010007313170014653 0ustar takeshisaPNG  IHDR Sww!PLTE髏 髏 齠oV"tEXtSoftwaregif2png 2.2.59勲HIDATxc`@LJJJfiBJP@'iiP仞正j姜eiY`[ H`////Ks/ :-yE蒹_IENDB`mysql-4.00.12/Flags/switzerland.png0100644000175100001560000000035410007313166015750 0ustar takeshisaPNG  IHDR nv9PLTE鈿黹笏艸鰄枷 騫柯 闖裨"QtEXtSoftwaregif2png 2.2.59勲LIDATxc` 8+| 8XhHcS+夢Q昔陳<4&1 攝)Q@NrIENDB`mysql-4.00.12/Flags/taiwan.png0100644000175100001560000000061510007313166014665 0ustar takeshisaPNG  IHDR nvPLTE YS血踉ア 衿汾D>[V漫  VPIC`[~ E? A;  玖褥 +$ZT瀑_Y e`労 怙熨欅淨屋%kf.tEXtSoftwaregif2png 2.2.59勲{IDATxc`  @Bi│!C~q L4%-p)`怩孑cRa張@@WSyeI\ D p)51Qf剥Mn1NiTA`*P F=ASJm IENDB`mysql-4.00.12/Flags/belgium.png0100644000175100001560000000025610007313165015026 0ustar takeshisaPNG  IHDR SwwPLTE霾 猯=bKGDztEXtSoftwaregif2png 2.2.59勲IDATxc@ `QPP正,---cTJHS|\7e:IENDB`mysql-4.00.12/Flags/ukraine.png0100644000175100001560000000023510007313167015037 0ustar takeshisaPNG  IHDR SwwPLTE居決BStEXtSoftwaregif2png 2.2.59勲'IDATxc`@(@`0)fc`誓:sb1t\ IENDB`mysql-4.00.12/Flags/usa.png0100644000175100001560000000124710007313172014171 0ustar takeshisaPNG  IHDR nvDPLTE PJZU B;*#症LF4.VQ&HB郊aaRM "6/MG@:系//)2+IC`[$ E?\W 70NH XS 3,鑑NN22=7 欽RR PI +$ B<兎4-KEVP0)砿qq#QL" ,%[UC=徒 (!WQ堀]]?9VQ瞥##1*`Z$女#]XD>OI71) )"XR牧>>2+%TN篇BBUG$^Y紅jtEXtSoftwaregif2png 2.2.59勲IDATxWSPa(lXblXCP" M答閖nG臉s憐fgﾍ6Tq品qun8 jF;殤v29З)!}嚇QPZ7=]Tx/Tr欠襞 JhXsQ亅Hs/hc>$8r\駢AY閉u臚]聹あL夫-! ^(2q,D(e! bB耽我U(rIENDB`mysql-4.00.12/Flags/argentina.png0100644000175100001560000000044010007313167015347 0ustar takeshisaPNG  IHDR nvfPLTELX費蜆麌Og役譚>鯏鋏髱N居麝踴?齊脯L黎A鉗颪鯆麸范蝎鰺迥c*tEXtSoftwaregif2png 2.2.59勲SIDATxc` x、 /*FB|\(h $陳潰(`d腺@YG~QFa)n< ゅEPA A+ % V0IENDB`mysql-4.00.12/Flags/indonesia.png0100644000175100001560000000026310007313173015350 0ustar takeshisaPNG  IHDR 7v PLTE纓tEXtSoftwaregif2png 2.2.59勲tEXtCommentCreated with The GIMPd%nIDATxc`P0>Ck>0H8cfIENDB`mysql-4.00.12/Flags/latvia.png0100644000175100001560000000025110007313172014653 0ustar takeshisaPNG  IHDR SwwPLTEcccsskkbKGDaf}tEXtSoftwaregif2png 2.2.59勲 IDATxcHC IJ(@mP9/ d4z7rIENDB`mysql-4.00.12/Flags/yugoslavia.png0100644000175100001560000000026510007313170015561 0ustar takeshisaPNG  IHDR SwwPLTE%IENDB`mysql-4.00.12/Flags/mexico.png0100644000175100001560000000045010007313171014657 0ustar takeshisaPNG  IHDR nv]PLTEkksZ{k!s1!c巖麗{J9!J記B{9k1Z)Bc)9c1BZ)闖!FbbKGDr +tEXtSoftwaregif2png 2.2.59勲WIDATxc#@$`*倏A\@vaA< Ey%悌(`鏑MK l哄描読1AM \4zJfIENDB`mysql-4.00.12/Flags/norway.png0100644000175100001560000000052310007313165014716 0ustar takeshisaPNG  IHDR nviPLTE丙枌茄調挧殉習崢吸胴楡華     際-!.!."/"  1obKGD"]e\tEXtSoftwaregif2png 2.2.59勲vIDATx孅@0E&y%VmA g}vmΔ'rwR @ik櫑 m柎8XK8D蔓0 FEIa~! Yqd#g睇/}pcGo/]IENDB`mysql-4.00.12/Flags/philippines.png0100644000175100001560000000060110007313172015716 0ustar takeshisaPNG  IHDRu}cPLTE#]^"( 珎畿ｃ#_\蒲2U蕀覧頸獵腑bKGD k=tEXtSoftwaregif2png 2.2.59勲IDATx} S框&勢迦tε!鉉rI珱o2朞@A " BrA*H:``tZ籔&B7cqQs夏r mw-zl.%8v抗]eS _I,%伸U~>BJ_(!ggx2,爽PP_^$ E@wP>4 ZM置OOHAdX%俊BBft較MOKX-%wX貫s}!tEXtSoftwaregif2png 2.2.59勲IDATxc` LイXTそ**`*a綫T4=S*$W %紂j祗Ｇ捕ft)W OUO WB] #>v$+8@Vp拈:#AVo * h+-5$ AFh{AxA(bWRFH3^"2nxM76o2兢 TrIKIENDB`mysql-4.00.12/Flags/slovenia.png0100664000175100001560000000066307525213363015240 0ustar takeshisaPNG  IHDR nvPLTE瑁rY 93靺涸苺}3,c^遼赴%M"謳:3瀦術u輝碯 鈷搶S(酢=QFvO "]Xv;呈嫺=!C鯏鋏髱N居麝踴?齊脯L黎A鉗颪鯆麸范蝎鰺迥, @pH,rl:J!tJ]JX5ml指/*4茣zmn溥8\H(鬻;`,|q{z!   ■茜bcP慨ZU矯V構疑生H兎DA;mysql-4.00.12/Flags/argentina.txt0100644000175100001560000000000010007313167015372 0ustar takeshisamysql-4.00.12/Flags/australia.eps0100644000175100001560000001003010007313170015355 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage cf7b0e0808087cc6730808081084c4080808080808080808080808080808 3f5c0600000050005300000009603a000000000000000000000000000000 43b5b6b5b5b5a600b1b5b5b5b7b246b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 b1d2b73608087cc67308083dbcd3a5080808080808080809080808080808 8d3e612f00005000530000355e4285000000000000000001000000000000 bc3e82c0b5b5a600b1b5b5c17a43bfb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 096bd4cf7b0e7cc6731083d0d36108080808080808084d990c0808080808 0162753f5c06500053095f3c7b5b00000000000000004796040000000000 b5cd7e43b5b7a600b1b7b13e87ccb5b5b5b5b5b5b5b5c8ddb6b5b5b5b5b5 0c0c2bb5d3b8a3c6a2bcd3ae250c0c080808080808087bba170808080808 040424913e6478008061438f1e04040000000000000077b70f0000000000 b6b6bfbd3f85b000bc7d43c1bdb6b6b5b5b5b5b5b5b5d5e6b9b5b5b5b5b5 d5d5d5d5d5d5d2c6d3d5d5d5d5d5c9080808080808080d0d080808080808 4c4c4c4c4c4a3c00414a4c4c4c4c48000000000000000505000000000000 4c4c4c4c4c4a3c00414a4c4c4c4c52b5b5b5b5b5b5b5b6b6b5b5b5b5b5b5 d3d3d3d4d7d6d4c6d4d6d7d4d3d3c7080808080808080808080808080808 51515152545044004950555251514c000000000000000000000000000000 55555555545044004950555555555bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0a0a2fb9d2b19fc69db7d2b3290a0a080808080808080808080808080808 0202288f3a6374007c613e8e220202000000000000000000000000000000 b5b5c0b73b8aaf00bb823ebcbeb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0b74d6ce720b7cc6730e7bcfd46b0908080808080808080808080c080808 036b6f435703500053065c3f756201000000000000000000000004000000 b6cd7649b8b6a600b1b7b5437ecdb5b5b5b5b5b5b5b5b5b5b5b5b6b5b5b5 b9d2b12f08087cc673080836b7d2ab080808110808080808080eac520808 8f3a6328000050005300002f613e870000000a00000000000006a94d0000 b73a8abfb5b5a600b1b5b5c0823ebab5b5b5b8b5b5b5b5b5b5b6e2cab5b5 c7720b08080877bf6f0808080e7abd080819c757080808080819ae6f0808 3c57030000004d004f000000065b37000011c552000000000012ac6a0000 47b8b6b5b5b5a607b1b5b5b5b7b54ab5b5baeacbb5b5b5b5b5bae3d1b5b5 08080808080808080808080808080808081c9e50080808080f080a0a0808 0000000000000000000000000000000000149a4a00000000070002020000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5badec9b5b5b5b5b7b5b6b5b5b5 0808080808080808080808080808080808080808080808119a0b08080808 000000000000000000000000000000000000000000000009960300000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b7ddb6b5b5b5b5 0808080808080808080808080808080808080808080808080c0808080808 000000000000000000000000000000000000000000000000040000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b6b5b5b5b5b5 080808080808080c08080808080808080808080808080808080808080808 000000000000000400000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080809439144090808080808080808080808080808080808080808 0000000000013d8e3d010000000000000000000000000000000000000000 b5b5b5b5b5b5c5dbc5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080809b0f7b1090808080808080808080808081308080808080808 000000000001adf7af010000000000000000000000000c00000000000000 b5b5b5b5b5b5e3f7e4b5b5b5b5b5b5b5b5b5b5b5b5b5b8b5b5b5b5b5b5b5 08080808081c8eed8f1d08080808080808080808083ccc3a080808080808 0000000000158aed8c15000000000000000000000035cb34000000000000 b5b5b5b5b5bbdaf4dabbb5b5b5b5b5b5b5b5b5b5b5c3ebc3b5b5b5b5b5b5 0808080808082c1b2c08080808080808080808080827af26080808080808 0000000000002513250000000000000000000000001fac1e000000000000 b5b5b5b5b5b5bfbabfb5b5b5b5b5b5b5b5b5b5b5b5bde3bdb5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/australia.gif0100644000175100001560000000126110007313170015341 0ustar takeshisaGIF87a  PJ付JJHR|屍QU瑳a}罫AAx/(織RM頁投 t?CMG挽RU<<_ tkWRoO燕逕犀DD 錦BC圾傑D=|P =5ﾛ <5単c{/(赤ov 6/籍::^z+$ 股II{wa[矛a&wMπ<>:FrW故CI:4誰 久UU擻ｼ,%C=`箇LL緬 '集dPPz[輝糢CC悪穽TTsS卯瞎:;芝L[)"ojkb羊>?>>4*6#33gsn_SB0=(!"""7^hU :G [Lo色;%rQ嗷: Q--]V :9VKc硯JJ1$a/:>iMd齔M H 閲刊0L "Q稘PP俥AL@D@AIAXtKFD$p脊 @O!03猝3 %QSM4禀 &}zi-Y佳â5<\$S19a($?j]t/_D ;mysql-4.00.12/Flags/australia.txt0100644000175100001560000000000010007313170015401 0ustar takeshisamysql-4.00.12/Flags/austria.eps0100644000175100001560000001003010007313170015040 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7 575757575757575757575757575757575757575757575757575757575757 575757575757575757575757575757575757575757575757575757575757 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4 464646464646464646464646464646464646464646464646464646464646 474747474747474747474747474747474747474747474747474747474747 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/austria.gif0100644000175100001560000000020410007313170015020 0ustar takeshisaGIF87a FGWW, Q載mIR疝ь0r狆p,弄Bx陷m ,~$,2AE`JZ悸jrEo+翻3 i ;mysql-4.00.12/Flags/austria.txt0100644000175100001560000000000010007313170015064 0ustar takeshisamysql-4.00.12/Flags/belgium.eps0100644000175100001560000001131210007313165015024 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: belgium.ps %%Pages: 1 %%BoundingBox: 286 405 308 436 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 32 string def /gpicstr 32 string def /bpicstr 32 string def %%EndProlog %%Page: 1 1 gsave 286.94 405.64 translate 21.12 30.72 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 32 22 8 [ 32 0 0 -22 0 22 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000013f0fffffffffffffffffcc9c5c6 c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6d6d6d6dac90d 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000013f0ffffffffffff fffffcc9c5c6c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6 d6d6d6dac90d000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000013f0 fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000000000000000 10cadad6d6d6d6d6d6dac90d000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000 00000000000010cadad6d6d6d6d6d6dac90d000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6 c6000000000000000000000010cadad6d6d6d6d6d6dac90d000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000013f0fffffffffffffffffcc9c5c6 c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6d6d6d6dac90d 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000013f0ffffffffffff fffffcc9c5c6c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6 d6d6d6dac90d000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000013f0 fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000000000000000 10cadad6d6d6d6d6d6dac90d000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000 00000000000010cadad6d6d6d6d6d6dac90d000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6 c6000000000000000000000010cadad6d6d6d6d6d6dac90d000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000013f0fffffffffffffffffcc9c5c6 c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6d6d6d6dac90d 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000013f0ffffffffffff fffffcc9c5c6c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6 d6d6d6dac90d000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000013f0 fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000000000000000 10cadad6d6d6d6d6d6dac90d000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000 00000000000010cadad6d6d6d6d6d6dac90d000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6 c6000000000000000000000010cadad6d6d6d6d6d6dac90d000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000013f0fffffffffffffffffcc9c5c6 c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6d6d6d6dac90d 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000013f0ffffffffffff fffffcc9c5c6c6c6c6c6c6c6c6000000000000000000000010cadad6d6d6 d6d6d6dac90d000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000013f0 fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000000000000000 10cadad6d6d6d6d6d6dac90d000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6c60000000000 00000000000010cadad6d6d6d6d6d6dac90d000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000013f0fffffffffffffffffcc9c5c6c6c6c6c6c6c6 c6000000000000000000000010cadad6d6d6d6d6d6dac90d000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/belgium.gif0100644000175100001560000000026510007313165015007 0ustar takeshisaGIF89a 霾 , jI舜QFiu"kdΦ羣Y嚶2Chrl冑".ЪэV0,Rk w梅9FJ簸差u}-o&mt}zLe3;mysql-4.00.12/Flags/belgium.txt0100644000175100001560000000000010007313165015044 0ustar takeshisamysql-4.00.12/Flags/brazil.eps0100644000175100001560000001003010007313166014660 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000001eb8a41300000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5beebe5bab5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000164f1ffffe74f000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5d2fbfffff8ccb5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000001eb8fffffcfdffffa41300000000000000000000 b5b5b5b5b5b5b5b5b5b5beebfffffefeffffe5bab5b5b5b5b5b5b5b5b5b5 000000000000000000000000000003020000000000000000000000000000 00000000000000000163f0fea8451c1e4eb8ffe750000000000000000000 b5b5b5b5b5b5b5b5b5d2fbffe3c3b6b7c6e8fff8ccb5b5b5b5b5b5b5b5b5 0000000000000000000000015ac1ebe9b84a000000000000000000000000 000000000000001db7fffe6f18181818181889ffffa41300000000000000 b5b5b5b5b5b5b5beeaffffd1b5b5b5b5b5b5d9ffffe5bab5b5b5b5b5b5b5 000000000000000000000195efefefefefef7a0000000000000000000000 00000000000163f0ffffa61818181818181818c1ffffe750000000000000 b5b5b5b5b5b5d2fbffffe2b5b5b5b5b5b5b5b5ebfffff8ccb5b5b5b5b5b5 000000000000000000005cefefefefefefefef4100000000000000000000 000000001db7ffffffffd4b5bea7905c2b18185dffffffffa41300000000 b5b5b5b5beeaffffffffeee4e6e0d9c9bbb5b5cbffffffffe5bbb5b5b5b5 00000000000000000000c9f5f5f4f3f2f0efefa800000000000000000000 00000063f0fffffffffa422122395f8aae661d30ffffffffffe74f000000 b5b5b5d2fbfffffffffdc2b8b8bfcad7e2cdb7bdfffffffffff8ccb5b5b5 00000000000000000006eff0f0f0f2f3f4f2efd700000000000000000000 00000050e7fffffffffa1b1e181b1b1836909948ffffffffffdb3d000000 b5b5b5ccf8fffffffffeb6b7b5b6b6b5bed9dcc4fffffffffff5c7b5b5b5 00000000000000000005ecefefefefeff0f4f4d600000000000000000000 0000000013a5ffffffff481c18181f1818196fdefffffffd900a00000000 b5b5b5b5bbe5ffffffffc4b6b5b5b7b5b5b5cff2fffffffedfb8b5b5b5b5 00000000000000000000beefefefefefefeff2a600000000000000000000 00000000000050e7ffffb01823182218282e39d9ffffdb3d000000000000 b5b5b5b5b5b5ccf8ffffe6b5b8b5b8b5babcbff3fffff5c7b5b5b5b5b5b5 0000000000000000000051efefefefeff0f0ee3800000000000000000000 0000000000000013a5ffff8018181b18283a99fffd900a00000000000000 b5b5b5b5b5b5b5bbe5ffffd7b5b5b6b5babfdffffedfb8b5b5b5b5b5b5b5 000000000000000000000084efefefeff0ef690000000000000000000000 00000000000000000050e7ffba572b2d60c8ffdb3d000000000000000000 b5b5b5b5b5b5b5b5b5ccf8ffe9c9bbbcccedfff5c7b5b5b5b5b5b5b5b5b5 00000000000000000000000048aedcd9a539000000000000000000000000 0000000000000000000013a5fffffffffffd900a00000000000000000000 b5b5b5b5b5b5b5b5b5b5bbe5fffffffffffedfb8b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000050e7ffffdb3e000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5ccf8fffff5c7b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000013a5910b00000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5bbe5dfb8b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/brazil.gif0100644000175100001560000000122610007313166014645 0ustar takeshisaGIF87a 梧Jc顋B啄9瑞O潔咲H件H綴窓Ai橙"醐井Q]萌 居оo:随9錘ュ駈桾.腫E蛋\葡W筆0竣(咋夥>件穴搏6情丈"乞\N童搏8恣`魅苦d髮碁苻PゅZ駈-邪灸zo鰤鬢件H直碪=摧_呆#醐 居f嵐+諮!乞罷9+施矩, ;>R9:EE<6R#?!Y3=.*E#品Fｳ2辺 <張'C-+"TE>/玖0U1N5KS)%螟燹＼<0p pH$Y#HY2]EFKE &>dQJ盂.l ,ysR$qMHrbT7TNH)Hu凖P8ws埆紫策hb蒟鷂球(!ni剽蛻 fa 各a[浴瑜, @pH,ErLx丿T*dN@幽V[]V:扠U,瘻Q|K@M (>?A7G"S.\4J2, /h+ F0WTPVXdZgY&北6=f=[R踊&U毳>U^9Ua>!煖U樓LH ]OH閘錏8FHP3b0窄{7‥r)竜Pp!;!c,< 'E rG2>蒡&I3A<.壜aFNJTlR顔N&3 jSVZ的+Q^ 抒;mysql-4.00.12/Flags/croatia.txt0100644000175100001560000000000010007313172015040 0ustar takeshisamysql-4.00.12/Flags/czech-republic.gif0100644000175100001560000000037010007313166016260 0ustar takeshisaGIF87a 矚颯∇韶VP弗Sn菊1 TmVPィ 忌1, } di%Hl訃p,x; yUvD&鰰PBYir` ' z. |Ny聡 wpey{_aMb@,$Qh:丿管ZTv+r/x+_;;mysql-4.00.12/Flags/germany.txt0100644000175100001560000000000010007313171015057 0ustar takeshisamysql-4.00.12/Flags/great-britain.eps0100644000175100001560000001003010007313165016124 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage cfd85508080808080808080811e4c6c6d70808080808080808080967decd 2db24f000000000000000000099600009f0000000000000000000162ab20 2ec2cab5b5b5b5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5b5b5b5cfb520 ccc7dfa31b0808080808080811e4c6c6d7080808080808080825b4dbc6ce 1c057a9c1300000000000000099600009f00000000000000001ea8670127 1c057bdbbab5b5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5b5bdda670127 edd9c6cfd85508080808080811e4c6c6d70808080808080967decdc7dde9 e160012eb14f000000000000099600009f0000000000000162ab200373e3 e760012ec2cab5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5cfb5210374ec 2fc4e9ccc7dea31b0808080811e4c6c6d7080808080825b4dbc6ceedb423 28c2b21c057a9c1300000000099600009f00000000001ea8670129c2b21c c0e9b21c057adabab5b5b5b5b8970000aeb5b5b5b5b5bdd9670129c2e4bc 080b78edd9c6cfd85508080811e4c6c6d70808080967ddccc7dde8650908 000373e160012db14f000000099600009f0000000162aa200373e1600100 b5b6d4e760012dc1cab5b5b5b8970000aeb5b5b5b5cfb4200374eccfb5b5 0808082fc4e9ccc7dea31b0811e4c6c6d7080825b4dac6ceedb423080808 00000029c2b21d05799c1300099600009f00001ea8660129c2b21c000000 b5b5b5c0e9b21d057adabab5b8970000aeb5b5bdd9660129c2e4bdb5b5b5 080808080b78edd9c6cfd85511e4c6c6d70967ddccc7dde8650908080808 000000000473e161012db14f099600009f0162aa200474e1600100000000 b5b5b5b5b6d4e761012dc1cab8970000aeb5cfb4200475eccfb5b5b5b5b5 0e0e0e0e0e0e35c9eaccc8dfaae4c6c6deb4dcc7cfedb9290e0e0e0e0e0e 0606060606062ec7b31f0b7fa3960000a7aa6c072bc3b722060606060606 b7b7b7b7b7b7c2eab31f0b7fde970000b0db6c072bc3e6beb7b7b7b7b7b7 e4e4e4e4e4e4e4e4e5e5e5e5e5d9c6c6dde5e5e5e5e5e4e4e4e4e4e4e4e4 9a9a9a9a9a9a9a9a9b9b9a9a9b5e0000709b9a9a9b9b9a9a9a9a9a9a9a9a 9b9b9b9b9b9b9b9b9b9b9a9a9b5f0000719b9a9a9b9b9b9b9b9b9b9b9b9b c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 dbdbdbdbdbdbdbdfe9e8e6e6e8dbc6c6e0e8e6e6e8e9dddbdbdbdbdbdbdb 9f9f9f9f9f9f9fa3aea79f9fab6a00007eaa9f9fa8aea19f9f9f9f9f9f9f abababababababacafa8a0a0ac6b00007faba0a0a9afacababababababab 0808080808083ed2e6cac8e098e4c6c6dda3dec7cceac42f080808080808 00000000000037d1a0120a8b93960000a59c79051db3c228000000000000 b5b5b5b5b5b5c4eda0130a8ddb970000b0db7a051db3e9c0b5b5b5b5b5b5 08080808108af0d6c6d2d04411e4c6c6d70855d8cfc6d9ed780b08080808 000000000887dd4e003cb33d099600009f004fb12d0161e2730300000000 b5b5b5b5b7d9df4e003cccc5b8970000aeb5cac12d0161e7d4b6b5b5b5b5 0808083ed2e6cac8e091130811e4c6c6d708081aa3dec7cce9c42f080808 00000037d09f120a8b8c0b00099600009f0000139c79051db2c228000000 b5b5b5c4ec9f130b8dd9b8b5b8970000aeb5b5badb7a051db2e9c0b5b5b5 08108bf0d5c6d2d04408080811e4c6c6d70808080855d8cfc6d9ed780b08 000887dd4d003cb33e000000099600009f000000004fb12d0160e1730300 b5b7d9df4d003cccc5b5b5b5b8970000aeb5b5b5b5cac12d0160e7d4b6b5 3dd2e6cac8e191130808080811e4c6c6d708080808081ba3dec7cce9c42f 37d09f120b8c8c0b00000000099600009f0000000000139c7a051cb2c229 c4ec9f120b8dd9b8b5b5b5b5b8970000aeb5b5b5b5b5badb7a051cb2e9c0 f0d6c6d2d04408080808080811e4c6c6d70808080808080855d8cfc6d9ee dd4d003db43d000000000000099600009f000000000000004fb12e0160e3 df4d003dccc5b5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5cac22e0160e7 cac8e191130808080808080811e4c6c6d708080808080808081ba3dec7cb 120b8c8c0b00000000000000099600009f0000000000000000139c7a051a 120b8ed9b8b5b5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5b5badb7b051a d2d24408080808080808080811e4c6c6d70808080808080808080855dacf 3bb63e000000000000000000099600009f000000000000000000004fb32c 3bcdc5b5b5b5b5b5b5b5b5b5b8970000aeb5b5b5b5b5b5b5b5b5b5cac32c grestore showpage %%Trailer mysql-4.00.12/Flags/great-britain.gif0100644000175100001560000000225110007313165016110 0ustar takeshisaGIF87a gbff 湖缶==5.態NNyz>7UO輔勘桍頑滷aa 狗淅 tu蕾雅鍛<倒゜++衍)"冗竚擲地-.惘草毯剤z{^_%巡茫/)窃, Ha0Cd0ar紂#素w,68陰{$善F8n`h$E@)Cﾀ!2:t2&$D7釶 ,琉%%uh琉irSxsd~V& 節tgf*jV_P0,^z+> B0 7個QX ?7hE<6 thcMvl惷s(閙"\pbH@(溂B狄:\  ^d );|P u`ByF0URC)t]6 /!zJq' fg?讌C{檗@>hH$Z沈 7牋 }X4u &矚孃Cxs|T;mysql-4.00.12/Flags/great-britain.txt0100644000175100001560000000000010007313165016150 0ustar takeshisamysql-4.00.12/Flags/greece.eps0100644000175100001560000001003010007313171014623 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 1818181897f7a61818181818181818181818181818181818181818181818 b5b5b5b5daf7dfb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefeff4f7f4efefefefefefefefefefefefefefefefefefefefefefef 1818181897f7a61818181818181818181818181818181818181818181818 b5b5b5b5daf7dfb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefeff4f7f4efefefefefefefefefefefefefefefefefefefefefefef 1818181897f7a618181818bbc7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7 b5b5b5b5daf7dfb5b5b5b5e5e9e9e9e9e9e9e9e9e9e9e9e9e9e9e9e9e9e9 efefefeff4f7f4efefefeff5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5 1818181897f7a618181818e7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 b5b5b5b5daf7dfb5b5b5b5f2f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 efefefeff4f7f4efefefeff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 97979797cdf7d49797979777767676767676767676767676767676767676 dadadadaeaf7ecdadadadad1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1 f4f4f4f4f6f7f6f4f4f4f4f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2 f7f7f7f7f7f7f7f7f7f7f725181818181818181818181818181818181818 f7f7f7f7f7f7f7f7f7f7f7b9b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7f7f7f7f7f7f7f7f7f7f7efefefefefefefefefefefefefefefefefefef a6a6a6a6d4f7daa6a6a6a66a676767676767676767676767676767676767 dfdfdfdfedf7eedfdfdfdfcdcccccccccccccccccccccccccccccccccccc f4f4f4f4f6f7f6f4f4f4f4f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2 1818181897f7a618181818e7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 b5b5b5b5daf7dfb5b5b5b5f2f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 efefefeff4f7f4efefefeff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 1818181897f7a618181818c9d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6 b5b5b5b5daf7dfb5b5b5b5e9edededededededededededededededededed efefefeff4f7f4efefefeff6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6 1818181897f7a61818181818181818181818181818181818181818181818 b5b5b5b5daf7dfb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefeff4f7f4efefefefefefefefefefefefefefefefefefefefefefef 1818181897f7a61818181818181818181818181818181818181818181818 b5b5b5b5daf7dfb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefeff4f7f4efefefefefefefefefefefefefefefefefefefefefefef e7e7e7e7f0f7f1e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7 f2f2f2f2f5f7f5f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2f2 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 555555555555555555555555555555555555555555555555555555555555 c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7 f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 878787878787878787878787878787878787878787878787878787878787 d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6 f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6b6 e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4 f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef grestore showpage %%Trailer mysql-4.00.12/Flags/greece.gif0100644000175100001560000000043210007313171014606 0ustar takeshisaGIF87a 幎g役晧糸熹幇夛頤居v剪銀j嵐U泊負頼%刻梦髟苒秤暈w剪,  die&Tp,"楙s>恚 pHTEl:MejyHTE総z] 刮Dt!" |N,l93I*zf 8gb~" ぅΗ┤x"葦桶患々O" 従神疎習兎(北$!;mysql-4.00.12/Flags/greece.txt0100644000175100001560000000000010007313171014647 0ustar takeshisamysql-4.00.12/Flags/hungary.eps0100644000175100001560000001003010007313171015046 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7 575757575757575757575757575757575757575757575757575757575757 575757575757575757575757575757575757575757575757575757575757 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 464646464646464646464646464646464646464646464646464646464646 c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8 464646464646464646464646464646464646464646464646464646464646 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/hungary.gif0100644000175100001560000000021510007313171015030 0ustar takeshisaGIF87a WWFF, Z載mIR疝ь0r狆p,弄Rx陷m ,~d,2AaJZ悸"尖z逗0w+.:L^躔:.7CxG;mysql-4.00.12/Flags/hungary.txt0100644000175100001560000000000010007313171015072 0ustar takeshisamysql-4.00.12/Flags/iceland.eps0100644000175100001560000001003010007313171014770 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0e0e0e0e0e0e0e15eec6c6e40e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e 060606060606060ec60000cb060606060606060606060606060606060606 b7b7b7b7b7b7b7b9c70000d6b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7 ecececececececece6c6c6e9ecececececececececececececececececec c5c5c5c5c5c5c5c59f0000aec5c5c5c5c5c5c5c5c5c5c5c5c5c5c5c5c5c5 c6c6c6c6c6c6c6c6a00000afc6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 e6e6e6e6e6e6e6e6e9c6c6ebe6e6e6e6e6e6e6e6e6e6e6e6e6e6e6e6e6e6 cecececececececeae0000becececececececececececececececececece d7d7d7d7d7d7d7d7af0000c0d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080feec6c6e3080808080808080808080808080808080808 0000000000000008c60000cb000000000000000000000000000000000000 b5b5b5b5b5b5b5b7c70000d6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/iceland.gif0100644000175100001560000000030510007313171014752 0ustar takeshisaGIF87a 耄怏鴻勃給樟血兎酘隙勃, zI週]B&(vi惷3Ysw^o&cd >FsJeJ,h逗D.h8n$<.胯室|G~I(*20;mysql-4.00.12/Flags/iceland.txt0100644000175100001560000000000010007313171015014 0ustar takeshisamysql-4.00.12/Flags/indonesia.eps0100644000175100001560000000000010007313173015340 0ustar takeshisamysql-4.00.12/Flags/indonesia.gif0100644000175100001560000000020510007313173015325 0ustar takeshisaGIF89a !Created with The GIMP, E緑\_$fTz@碓苞n樹D欅%|鬆Rc b7Q;mysql-4.00.12/Flags/indonesia.txt0100644000175100001560000000000010007313173015370 0ustar takeshisamysql-4.00.12/Flags/ireland.eps0100644000175100001560000001003010007313167015014 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f8ffffffffffffffffffff b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7f4d6d6d6d6d6d6d6d6d6d6 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/ireland.gif0100644000175100001560000000023610007313167015001 0ustar takeshisaGIF87a  , k載-9I岨WThe揉`X衒^λヱ86,'l"Hbf 9Pv* *dQc鎗揉停尼軆lS鉐NPyvHxzcn ;mysql-4.00.12/Flags/ireland.txt0100644000175100001560000000000010007313167015040 0ustar takeshisamysql-4.00.12/Flags/island.eps0100644000175100001560000000000010007313170014636 0ustar takeshisamysql-4.00.12/Flags/island.txt0100644000175100001560000000000010007313170014666 0ustar takeshisamysql-4.00.12/Flags/israel.eps0100644000175100001560000001003010007313173014652 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0 f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4f4 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4 edededededededededededededededededededededededededededededed f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6f6 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7a5bef7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7dfe6f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f4f5f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f2ede4807aebedf3f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f5f4f1d4d2f3f4f6f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f3f3f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7c65e5296915755daf7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7e9cac6dbd9c8c7eef7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f5f2f1f4f4f2f1f6f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7809af7f78a90f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7d4dcf7f7d7d9f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f3f4f7f7f3f3f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f77d94f7f7868bf7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7d3daf7f7d6d7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f3f3f7f7f3f3f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7c15e508a835755d6f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7e7cac6d7d5c8c7edf7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f5f1f1f3f3f1f1f6f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f0837ef6f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f5d5d3f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f3f3f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7afc7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7e2e9f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f4f5f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2 e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7 f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef bcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbcbc e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5 f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 grestore showpage %%Trailer mysql-4.00.12/Flags/israel.gif0100644000175100001560000000056010007313173014637 0ustar takeshisaGIF87a 謫幎燥專R難晧}囀頤^呆瑣居鍋恣W費糀碪ミ鴣摧搏幇U泊丈暃恣夾齧大W避梦z呶梍逕弱P難~囀橙^包秤, @pH,rl:JbJZ悸総z逗0w+.zn止j!tN_暮J '# #uws "~u'JxsJs(%| &|t)|!宜梢請唾dg_独B$力佰厶了sH掣FA;mysql-4.00.12/Flags/israel.txt0100644000175100001560000000000010007313173014676 0ustar takeshisamysql-4.00.12/Flags/italy.eps0100644000175100001560000001003010007313173014515 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5b5b5b5b8f7f7f7f7f7f7f7f7f7e400000000000000000000 0000000000000000000cf7f7f7f7f7f7f7f7f7e400000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/italy.gif0100644000175100001560000000023610007313173014502 0ustar takeshisaGIF87a 黻 , k載M9I岨WThe揉`X衒^λヱ86,'l"Hbf 9Pv* *dQc鎗揉停尼軆lS鉐NPyvHxzcn ;mysql-4.00.12/Flags/italy.txt0100644000175100001560000000000010007313173014541 0ustar takeshisamysql-4.00.12/Flags/japan.eps0100644000175100001560000001003010007313166014466 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7edddd6d7dfeff7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7c17652557cccf7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7c27653557cccf7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f2d4c6c6c6c6c6c6d8f4f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7de4500000000000157e9f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7de4600000000000158e9f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f2ccc6c6c6c6c6c6c6c6d0f5f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7de1f000000000000000030eaf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7de1f000000000000000030eaf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7d4c6c6c6c6c6c6c6c6c6c6d9f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7430000000000000000000060f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7440000000000000000000060f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7ecc6c6c6c6c6c6c6c6c6c6c6c7f1f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7be000000000000000000000003d8f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7be000000000000000000000003d9f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7ddc6c6c6c6c6c6c6c6c6c6c6c6e2f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7720000000000000000000000008ff7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7720000000000000000000000008ff7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7d6c6c6c6c6c6c6c6c6c6c6c6c6dbf7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f74e0000000000000000000000006bf7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f74e0000000000000000000000006bf7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7d6c6c6c6c6c6c6c6c6c6c6c6c6dcf7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f74f0000000000000000000000006cf7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f74f0000000000000000000000006df7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7dec6c6c6c6c6c6c6c6c6c6c6c6e3f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f77600000000000000000000000093f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f77600000000000000000000000093f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7edc6c6c6c6c6c6c6c6c6c6c6c7f2f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7c6000000000000000000000005def7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7c6000000000000000000000005def7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7d6c6c6c6c6c6c6c6c6c6c6dcf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f74f000000000000000000006cf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f74f000000000000000000006df7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f4cec6c6c6c6c6c6c6c6d2f5f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7e52a00000000000000003deff7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7e52a00000000000000003deff7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f4d8c6c6c6c6c6c7dbf5f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7e7580200000000056aeff7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7e7590200000000056beff7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f0e1dadbe3f2f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7d389666890dcf7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7d389666890dcf7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 grestore showpage %%Trailer mysql-4.00.12/Flags/japan.gif0100644000175100001560000000054510007313166014456 0ustar takeshisaGIF87a ff==NN鑢杢rrvvXY艸``貍裳WX鰤淮**hhjk裴EFvv繞鰛榕UU闖靦嗅00lm軻瀞CDRS軈胎kk||OO駢摧蜑, @pH,rl:J!tJ]JXz8v|\2h環羨OzUo&NgP |t!+PyJt-Os(P*i"OhN#NMT  s桶U cY%葱H力DA;mysql-4.00.12/Flags/japan.txt0100644000175100001560000000000010007313166014512 0ustar takeshisamysql-4.00.12/Flags/kroatia.eps0100644000175100001560000000000010007313171015017 0ustar takeshisamysql-4.00.12/Flags/kroatia.txt0100644000175100001560000000000010007313171015047 0ustar takeshisamysql-4.00.12/Flags/latvia.eps0100644000175100001560000001131110007313172014655 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: latvia.ps %%Pages: 1 %%BoundingBox: 295 365 317 396 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 32 string def /gpicstr 32 string def /bpicstr 32 string def %%EndProlog %%Page: 1 1 gsave 295.44 365.64 translate 21.12 30.72 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 32 22 8 [ 32 0 0 -22 0 22 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000009494949494949494949494949494949494949494949494 949494949494940000101010101010101010101010101010101010101010 101010101010101010000018181818181818181818181818181818181818 181818181818181818181800009494949494949494949494949494949494 949494949494949494949494940000101010101010101010101010101010 101010101010101010101010101010000018181818181818181818181818 181818181818181818181818181818181800009494949494949494949494 949494949494949494949494949494949494940000101010101010101010 101010101010101010101010101010101010101010000018181818181818 181818181818181818181818181818181818181818181800009494949494 949494949494949494949494949494949494949494949494940000101010 101010101010101010101010101010101010101010101010101010000018 181818181818181818181818181818181818181818181818181818181800 009494949494949494949494949494949494949494949494949494949494 940000101010101010101010101010101010101010101010101010101010 101010000018181818181818181818181818181818181818181818181818 181818181800009494949494949494949494949494949494949494949494 949494949494940000101010101010101010101010101010101010101010 101010101010101010000018181818181818181818181818181818181818 181818181818181818181800009494949494949494949494949494949494 949494949494949494949494940000101010101010101010101010101010 101010101010101010101010101010000018181818181818181818181818 181818181818181818181818181818181800009494949494949494949494 949494949494949494949494949494949494940000101010101010101010 101010101010101010101010101010101010101010000018181818181818 18181818181818181818181818181818181818181818180000ffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffff0000ffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffff0000ff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffff00 00ffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ff0000ffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffff0000ffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffff0000ffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffff0000ffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffff0000ffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffff0000ffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffff0000ffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffff0000ffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffff00009494949494949494949494 949494949494949494949494949494949494940000101010101010101010 101010101010101010101010101010101010101010000018181818181818 181818181818181818181818181818181818181818181800009494949494 949494949494949494949494949494949494949494949494940000101010 101010101010101010101010101010101010101010101010101010000018 181818181818181818181818181818181818181818181818181818181800 009494949494949494949494949494949494949494949494949494949494 940000101010101010101010101010101010101010101010101010101010 101010000018181818181818181818181818181818181818181818181818 181818181800009494949494949494949494949494949494949494949494 949494949494940000101010101010101010101010101010101010101010 101010101010101010000018181818181818181818181818181818181818 181818181818181818181800009494949494949494949494949494949494 949494949494949494949494940000101010101010101010101010101010 101010101010101010101010101010000018181818181818181818181818 181818181818181818181818181818181800009494949494949494949494 949494949494949494949494949494949494940000101010101010101010 101010101010101010101010101010101010101010000018181818181818 181818181818181818181818181818181818181818181800009494949494 949494949494949494949494949494949494949494949494940000101010 101010101010101010101010101010101010101010101010101010000018 181818181818181818181818181818181818181818181818181818181800 009494949494949494949494949494949494949494949494949494949494 940000101010101010101010101010101010101010101010101010101010 101010000018181818181818181818181818181818181818181818181818 181818181800000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/latvia.gif0100644000175100001560000000016510007313172014640 0ustar takeshisaGIF89a cccsskk, Bh載MIR疝ь0r貴htmxN+z钁%fSて. 瀧:;mysql-4.00.12/Flags/latvia.txt0100644000175100001560000000000010007313172014676 0ustar takeshisamysql-4.00.12/Flags/mexico.eps0100644000175100001560000001131110007313171014660 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: mexico.ps %%Pages: 1 %%BoundingBox: 286 405 308 436 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 32 string def /gpicstr 32 string def /bpicstr 32 string def %%EndProlog %%Page: 1 1 gsave 286.94 405.64 translate 21.12 30.72 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 32 22 8 [ 32 0 0 -22 0 22 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000ffffffffffffffffffffc6c6c6 c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00 000000000000000000000000000000000000000000ffffffffffffffffff ff00000000000000000000000000000000000000000000ffffffffffffff ffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffff ffffffffff00000000000000000000000000000000000000000000ffffff ffffffffffffff00000000000000000000000000000000000000000000ff ffffffffffffffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5 b5ffffffffffffffffffff00000000000000000000000000000000000000 000000ffffffffffffffffffff0000000000000000000000000000000000 0000000000ffffffffffffffffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5 b5b5b5b5b5b5b5ffffffffffffffffffff00000000000000000000000000 000000000000000000ffffffffffffffffffff0000000000000000000000 0000000000000000000000ffffffffffffffffffffc6c6c6c6c6c6c6c6c6 c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00000000000000 000000000000000000000000000000ffffffffffffffffffff0000000000 0000000000000000000000000000000000ffffffffffffffffffffc6c6c6 c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00 000000000000000000000000000000000000000000ffffffffffffffffff ff00000000000000000000000000000000000000000000ffffffffff94ff ffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffff 42ffffffff00000000000000000000000000000000000000000000ffffff ffff00ffffffff00000000000000000000000000000000000000000000ff ffff6b427b5affffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5 b5ffffff6b183929ffffff00000000000000000000000000000000000000 000000ffffff73000000ffffff0000000000000000000000000000000000 0000000000ffffff319c397b6bffffc6c6c6c6c6c6c6c6c6c60000b5b5b5 b5b5b5b5b5b5b5ffffff9c42213931ffff00000000000000000000000000 000000000000000000ffffff0000000000ffff0000000000000000000000 0000000000000000000000ffff8c6b39945a63ffffc6c6c6c6c6c6c6c6c6 c60000b5b5b5b5b5b5b5b5b5b5ffff8431184a2931ffff00000000000000 000000000000000000000000000000ffff840000001010ffff0000000000 0000000000000000000000000000000000ffff00ff94637b94ffffc6c6c6 c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffff5aff4a294a94ffff00 000000000000000000000000000000000000000000ffff10ff00000094ff ff00000000000000000000000000000000000000000000ff21ff1810efef b518ffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ff73ff6b7b 9cefad84ff00000000000000000000000000000000000000000000ff00ff 000800efa500ff00000000000000000000000000000000000000000000ff ff21ff9494ff21ffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5 b5ffff73ff4242ff63ffff00000000000000000000000000000000000000 000000ffff00ff0000ff00ffff0000000000000000000000000000000000 0000000000ffffff2121d621ffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5 b5b5b5b5b5b5b5ffffff6373de63ffffff00000000000000000000000000 000000000000000000ffffff0000ce00ffffff0000000000000000000000 0000000000000000000000ffffffffffffffffffffc6c6c6c6c6c6c6c6c6 c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00000000000000 000000000000000000000000000000ffffffffffffffffffff0000000000 0000000000000000000000000000000000ffffffffffffffffffffc6c6c6 c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00 000000000000000000000000000000000000000000ffffffffffffffffff ff00000000000000000000000000000000000000000000ffffffffffffff ffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5b5ffffffffff ffffffffff00000000000000000000000000000000000000000000ffffff ffffffffffffff00000000000000000000000000000000000000000000ff ffffffffffffffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5b5b5b5b5b5b5 b5ffffffffffffffffffff00000000000000000000000000000000000000 000000ffffffffffffffffffff0000000000000000000000000000000000 0000000000ffffffffffffffffffffc6c6c6c6c6c6c6c6c6c60000b5b5b5 b5b5b5b5b5b5b5ffffffffffffffffffff00000000000000000000000000 000000000000000000ffffffffffffffffffff0000000000000000000000 0000000000000000000000ffffffffffffffffffffc6c6c6c6c6c6c6c6c6 c60000b5b5b5b5b5b5b5b5b5b5ffffffffffffffffffff00000000000000 000000000000000000000000000000ffffffffffffffffffff0000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/mexico.gif0100644000175100001560000000041510007313171014641 0ustar takeshisaGIF89a kksZ{k!s1!c巖麗{J9!J記B{9k1Z)Bc)9c1BZ)闖, 'di趾p&牢妃ot抔.后h U%鼇|FycP 2妓痔grs0 薹ti""/o.  }>- Xsj.]=B. 5t[QhPYaV~-(梢%!;mysql-4.00.12/Flags/mexico.txt0100644000175100001560000000000010007313171014701 0ustar takeshisamysql-4.00.12/Flags/netherlands.eps0100644000175100001560000001003010007313173015702 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7d7 575757575757575757575757575757575757575757575757575757575757 575757575757575757575757575757575757575757575757575757575757 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c4c 464646464646464646464646464646464646464646464646464646464646 c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8c8 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 080808080808080808080808080808080808080808080808080808080808 000000000000000000000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/netherlands.gif0100644000175100001560000000021510007313173015664 0ustar takeshisaGIF87a LF盤WW菊, Z載IR疝ь$1r狆p,弄Rx陷m ,~d,2AE`JZ悸b尖z逗0w+.:L^躔:.7CxG;mysql-4.00.12/Flags/netherlands.txt0100644000175100001560000000000010007313173015726 0ustar takeshisamysql-4.00.12/Flags/norway.eps0100644000175100001560000001131110007313165014716 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: norway.ps %%Pages: 1 %%BoundingBox: 286 405 308 436 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 32 string def /gpicstr 32 string def /bpicstr 32 string def %%EndProlog %%Page: 1 1 gsave 286.94 405.64 translate 21.12 30.72 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 32 22 8 [ 32 0 0 -22 0 22 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6 c6c6c6c6c6c6c600000000000000000018b50604ac170000000000000000 00000000000000000000000000000000000011dbbabad611000000000000 00000000000000000000000000c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6 c6c6c6c6c6c6c6c6c6c6c6c6c600000000000000000018b50604ac170000 00000000000000000000000000000000000000000000000011dbbabad611 00000000000000000000000000000000000000c6c6c6c6c6c6c5d1c40b08 bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c600000000000000000018b5 0604ac170000000000000000000000000000000000000000000000000000 11dbbabad61100000000000000000000000000000000000000c6c6c6c6c6 c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c60000000000 0000000018b50604ac170000000000000000000000000000000000000000 00000000000011dbbabad611000000000000000000000000000000000000 00c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 c600000000000000000018b50604ac170000000000000000000000000000 00000000000000000000000011dbbabad611000000000000000000000000 00000000000000c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6 c6c6c6c6c6c6c600000000000000000018b50604ac170000000000000000 00000000000000000000000000000000000011dbbabad611000000000000 00000000000000000000000000c5c5c5c5c5c5c4d0c40b08bdd1c4c5c5c5 c5c5c5c5c5c5c5c5c5c5c5c5c500000000000000000014b50604ac130000 0000000000000000000000000000000000000000000000000ddbbabad60d 00000000000000000000000000000000000000d1d1d1d1d1d1d0dccb0b08 c4ddd0d1d1d1d1d1d1d1d1d1d1d1d1d1d1d1d10000171717171717172ebd 0604b42d1717171717171717171717171717171717000010101010101010 21debabad92110101010101010101010101010101010100000c3c3c3c3c3 c3c3caa00a089acac3c3c3c3c3c3c3c3c3c3c3c3c3c3c3c3c30000b2b2b2 b2b2b2b2ba9b020096bab2b2b2b2b2b2b2b2b2b2b2b2b2b2b2b2b20000d8 d8d8d8d8d8d8dbdeb6b5dcdbd8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d800 000b0b0b0b0b0b0b0b090808090b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b 0b0000060606060606060602000002060606060606060606060606060606 0606060000babababababababab6b5b5b6bababababababababababababa bababababa00000909090909090909080808080909090909090909090909 090909090909090000050505050505050401000001040505050505050505 0505050505050505050000b9b9b9b9b9b9b9b9b5b5b5b5b9b9b9b9b9b9b9 b9b9b9b9b9b9b9b9b9b9b90000c0c0c0c0c0c0c0c69d0a0898c6c0c0c0c0 c0c0c0c0c0c0c0c0c0c0c0c0c00000b2b2b2b2b2b2b2b998020093b9b2b2 b2b2b2b2b2b2b2b2b2b2b2b2b2b2b20000dadadadadadadadcdeb6b5dcdc dadadadadadadadadadadadadadadadada0000d2d2d2d2d2d2d1ddcb0b08 c4ded1d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d20000181818181818182fbd 0604b42e1818181818181818181818181818181818000011111111111111 22debabad92211111111111111111111111111111111110000c5c5c5c5c5 c5c4d0c40b08bdd1c4c5c5c5c5c5c5c5c5c5c5c5c5c5c5c5c50000000000 0000000014b50604ac130000000000000000000000000000000000000000 0000000000000ddbbabad60d000000000000000000000000000000000000 00c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 c600000000000000000018b50604ac170000000000000000000000000000 00000000000000000000000011dbbabad611000000000000000000000000 00000000000000c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6 c6c6c6c6c6c6c600000000000000000018b50604ac170000000000000000 00000000000000000000000000000000000011dbbabad611000000000000 00000000000000000000000000c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6 c6c6c6c6c6c6c6c6c6c6c6c6c600000000000000000018b50604ac170000 00000000000000000000000000000000000000000000000011dbbabad611 00000000000000000000000000000000000000c6c6c6c6c6c6c5d1c40b08 bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c600000000000000000018b5 0604ac170000000000000000000000000000000000000000000000000000 11dbbabad61100000000000000000000000000000000000000c6c6c6c6c6 c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c60000000000 0000000018b50604ac170000000000000000000000000000000000000000 00000000000011dbbabad611000000000000000000000000000000000000 00c6c6c6c6c6c6c5d1c40b08bdd2c5c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 c600000000000000000018b50604ac170000000000000000000000000000 00000000000000000000000011dbbabad611000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/norway.gif0100644000175100001560000000064010007313165014677 0ustar takeshisaGIF89a 丙枌茄調挧殉習崢吸胴楡華     際-!.!."/"  , @pH,r &巻Zk^針u R_q=jΤ}Ey~!\!BPB  ウB 桶B係 浩膳B兎 芭賄B嘖壙渺BqJlf|Xxcz跋Ju齦n逧髦洵;mysql-4.00.12/Flags/norway.txt0100644000175100001560000000000010007313165014737 0ustar takeshisamysql-4.00.12/Flags/philippines.eps0100644000175100001560000001011710007313172015724 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: philippines.ps %%Pages: 1 %%BoundingBox: 287 406 307 435 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 287.9 406.6 translate 19.2 28.8 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage a62301080808080808080808080808080808080808080808080808080808 a31f00000000000000000000000000000000000000000000000000000000 e3bcb3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 fce05f010108080808080808080808080808080808080808080808080808 ffdf5c000000000000000000000000000000000000000000000000000000 fdf0ceb3b3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f9fefba62301080808080808080808080808080808080808080808080808 f5f8f6a31f00000000000000000000000000000000000000000000000000 cd32ade3bcb3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f9fdfbfce05f010108080808080808080808080808080808080808080808 f5f7f6ffdf5c000000000000000000000000000000000000000000000000 cd55adfdf0ceb3b3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7f7f7f7fcfca62301080808080808080808080808080808080808080808 f7f6f8f7ffffa31f00000000000000000000000000000000000000000000 f9f0fff9fdfde3bcb3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7f7f7f7faf9fce05f010108080808080808080808080808080808080808 f7f7f7f7f9f5ffdf5c000000000000000000000000000000000000000000 f9f9fef9e8cdfdf0ceb3b3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7f7f9f7f9fbf7fafaa62301080808080808080808080808080808080808 f7f7f5f7f5f2f7f9f9a31f00000000000000000000000000000000000000 f9f9cdfecd8dfee8e8e3bcb3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7fafbfbfbfdf9fdfbfce05f010108080808080808080808080808080808 f7f9f2f6f2f7f5f7f6ffdf5c000000000000000000000000000000000000 f9e88dad8d55cd55adfdf0ceb3b3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 f7f7fafefffffffbf7f7fcfca62301050505050505050505050505050505 f7f7f9f8fefefef2f7f7ffffa31f00000000000000000000000000000000 f9fee8320303038dfefefdfde3bcb3b8b8b8b8b8b8b8b8b8b8b8b8b8b8b8 f7fbfbfffffffffdfbf9f7fbfde05f131313131313131313131313131313 f6f6f2fefefefef7f2f5f7f2f7df5c000000000000000000000000000000 f0ad8d03030303558dcdf98d55f0ceababababababababababababababab f7fbfbfffffffffdfbf9f7fbfdf4d9b9b9b9b9b9b9b9b9b9b9b9b9b9b9b9 f6f2f2fefefefef7f2f5f7f2f7e05d000000000000000000000000000000 f08d8d03030303558dcdf98d55da5e0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d f7f7f7fefffffffbf7f7fcf7e7cbc6cacacacacacacacacacacacacacaca f7f7f6f8fefefef2f8f7fff6a52200000000000000000000000000000000 f9fef0320303038dfffefdf0a42800000000000000000000000000000000 f7f7fbfbfbfdf9fdf9fcf4d9c4c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f7f6f2f2f2f7f5f7f5ffe05d000000000000000000000000000000000000 f9f08d8d8d55cd55cdfdda5e000000000000000000000000000000000000 f7f7f9f7f9fbf7fafae7ccc3c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f7f6f5f7f5f2f7f9f9a51f00000000000000000000000000000000000000 f9f0cdfecd8dfee8e8a42300000000000000000000000000000000000000 f7f7f7f7faf9f7f4d9c3c3c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f7f7f7f7f9f5f8e05d000000000000000000000000000000000000000000 f9f9fef9e8cdffda5e000000000000000000000000000000000000000000 f7f7f7f7f7fce7ccc3c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f7f6f7f7f8ffa51f00000000000000000000000000000000000000000000 f9f0f9f9fffda42300000000000000000000000000000000000000000000 f9fdfbfcf4d9c4c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f5f7f6ffe05d000000000000000000000000000000000000000000000000 cd55adfdda5e000000000000000000000000000000000000000000000000 f9fdfbe7ccc3c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f5f7f6a51f00000000000000000000000000000000000000000000000000 cd55ada42300000000000000000000000000000000000000000000000000 fcf4d9c3c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 ffe05d000000000000000000000000000000000000000000000000000000 fdda5e000000000000000000000000000000000000000000000000000000 e7ccc3c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 a51f00000000000000000000000000000000000000000000000000000000 a41f00000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/philippines.gif0100644000175100001560000000046210007313172015704 0ustar takeshisaGIF89a#]^"( 珎畿ｃ#_\蒲2U蕀覧頸獵腑, 0GihB涜j,_%rn^添8]y8 Pp4柾L5/KA(&hR|-*ID渟桴x T.e-|~eNnpr■ぅDe4elOE浣&綺O睛謡c[妻3VP吠)a0wQ齋袙?dS簧 McRn篌6蓄砿)"乗{闃)N}s綏, +X@+Q7 D _'S?艸 *+RS貊薯毫))gg MN觚固~~HH黴獰YYlm}}PP藪TT''罅” KK""蜑, @pH,E 丿4*\$ 0JO皀\B4搾0FU PwT'K")J JvP`2+#,K`.JB&橋 兄悉B0疎団兎B'碧麺力壁佯墹孩碗掉'桍憚默矣倥耄蓍H鈿FA;mysql-4.00.12/Flags/singapore.txt0100644000175100001560000000000010007313173015406 0ustar takeshisamysql-4.00.12/Flags/south-africa.eps0100644000175100001560000001003010007313166015762 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 0000001fb8e6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5bde6a3140000000000000000000000000000000000000000000000 0000001fb8a4140000000000000000000000000000000000000000000000 000000000169e9d6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5d1df5100000000000000000000000000000000000000000000 000000000169d85100000000000000000000000000000000000000000000 00000000000023bde6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5bee8a3140000000000000000000000000000000000000000 00000000000023bda3140000000000000000000000000000000000000000 080000000000000370ebd6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b7b5b5b5b5b5b5b6d3df5100000000000000000000000000000000000000 000000000000000370da5100000000000000000000000000000000000000 db480000000000000028c3e6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f5cab5b5b5b5b5b5b5c0e9a3140000000000000000000000000000000000 00000000000000000028c3a3140000000000000000000000000000000000 4bddac1d0000000000000477edd6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 4bdde7bdb5b5b5b5b5b5b6d5e05100000000000000000000000000000000 000000000000000000000477dc5100000000000000000000000000000000 000982eb74050000000000002dc8e6d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8 000982f4d7b6b5b5b5b5b5b5c1eaa45a5a5a5a5a5a5a5a5a5a5a5a5a5a5a 0000000000000000000000002dc8a45a5a5a5a5a5a5a5a5a5a5a5a5a5a5a 00000025b8d23d00000000000005769f9f9f9f9f9f9f9f9f9f9f9f9f9f9f 00000025b8f2c7b5b5b5b5b5b5b6d5e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0 0000000000000000000000000005769f9f9f9f9f9f9f9f9f9f9f9f9f9f9f 000000000054e19f15000000000000000000000000000000000000000000 000000000054e2e3bbb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 0000000000000c8ae9670100000000000000000000000000000000000000 0000000000000c8af6d3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000159ee1530000000000000000000000000000000000000000 000000000000159ef6cdb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000268e88b0c000000000000000000000000000000000000000000 000000000268ecdeb9b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 00000034cac22c0000000000000b89b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3 00000034caedc2b5b5b5b5b5b5b8dae5e5e5e5e5e5e5e5e5e5e5e5e5e5e5 000000000000000000000000000b89b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3 001195e760010000000000003cd4944c4c4c4c4c4c4c4c4c4c4c4c4c4c4c 001195f6d1b5b5b5b5b5b5b5c5ed90464646464646464646464646464646 0000000000000000000000003cd5dcc8c8c8c8c8c8c8c8c8c8c8c8c8c8c8 5fe79812000000000000098ad64508080808080808080808080808080808 5fe8e1bab5b5b5b5b5b5b7dad63f00000000000000000000000000000000 00000000000000000000098aecc6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 cd360000000000000036cf93130808080808080808080808080808080808 f1c5b5b5b5b5b5b5b5c4eb900c0000000000000000000000000000000000 00000000000000000036d1dcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 030000000000000783d54508080808080808080808080808080808080808 b6b5b5b5b5b5b5b7d8d63f00000000000000000000000000000000000000 000000000000000783ebc6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 00000000000031cb94140808080808080808080808080808080808080808 b5b5b5b5b5b5c2ea910c0000000000000000000000000000000000000000 00000000000031ccdcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 00000000057dd44608080808080808080808080808080808080808080808 b5b5b5b5b6d6d64000000000000000000000000000000000000000000000 00000000057deac6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0000002ac795140808080808080808080808080808080808080808080808 b5b5b5c0ea920c0000000000000000000000000000000000000000000000 0000002ac7dcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/south-africa.gif0100644000175100001560000000121210007313166015742 0ustar takeshisaGIF87a 蝟wwvvLF番幀孛__墻pp咀ii KKgS<< 限--梦幻 謾E? 卵6,笈罎と衄矧hh轢処循御TTF@%%H 罍}}ZZt誄`QQ664411莓**((艾##槙杢 癘痰罍=忠昼炸蛬悴癖喝, $6`H#dLU4E>] c5BSbΣWe\2閏'%I/.G壞嶐;a[:痰邃7_=g結Y8j踉3^"1-@獨3T榧#y.prＧ )-@`漸ニ,H窺C`t)豊DI4&[OhPh(E[,煩顔S)0V0廸;mysql-4.00.12/Flags/south-africa.txt0100644000175100001560000000000010007313166016006 0ustar takeshisamysql-4.00.12/Flags/south-africa1.eps0100644000175100001560000001003010007313167016044 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 0000001fb8e6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5bde6a3140000000000000000000000000000000000000000000000 0000001fb8a4140000000000000000000000000000000000000000000000 000000000169e9d6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5d1df5100000000000000000000000000000000000000000000 000000000169d85100000000000000000000000000000000000000000000 00000000000023bde6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b5b5b5b5b5b5bee8a3140000000000000000000000000000000000000000 00000000000023bda3140000000000000000000000000000000000000000 080000000000000370ebd6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 b7b5b5b5b5b5b5b6d3df5100000000000000000000000000000000000000 000000000000000370da5100000000000000000000000000000000000000 db480000000000000028c3e6cac6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 f5cab5b5b5b5b5b5b5c0e9a3140000000000000000000000000000000000 00000000000000000028c3a3140000000000000000000000000000000000 4bddac1d0000000000000477edd6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 4bdde7bdb5b5b5b5b5b5b6d5e05100000000000000000000000000000000 000000000000000000000477dc5100000000000000000000000000000000 000982eb74050000000000002dc8e6d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8 000982f4d7b6b5b5b5b5b5b5c1eaa45a5a5a5a5a5a5a5a5a5a5a5a5a5a5a 0000000000000000000000002dc8a45a5a5a5a5a5a5a5a5a5a5a5a5a5a5a 00000025b8d23d00000000000005769f9f9f9f9f9f9f9f9f9f9f9f9f9f9f 00000025b8f2c7b5b5b5b5b5b5b6d5e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0 0000000000000000000000000005769f9f9f9f9f9f9f9f9f9f9f9f9f9f9f 000000000054e19f15000000000000000000000000000000000000000000 000000000054e2e3bbb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 0000000000000c8ae9670100000000000000000000000000000000000000 0000000000000c8af6d3b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000000159ee1530000000000000000000000000000000000000000 000000000000159ef6cdb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 000000000268e88b0c000000000000000000000000000000000000000000 000000000268ecdeb9b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 000000000000000000000000000000000000000000000000000000000000 00000034cac22c0000000000000b89b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3 00000034caedc2b5b5b5b5b5b5b8dae5e5e5e5e5e5e5e5e5e5e5e5e5e5e5 000000000000000000000000000b89b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3 001195e760010000000000003cd4944c4c4c4c4c4c4c4c4c4c4c4c4c4c4c 001195f6d1b5b5b5b5b5b5b5c5ed90464646464646464646464646464646 0000000000000000000000003cd5dcc8c8c8c8c8c8c8c8c8c8c8c8c8c8c8 5fe79812000000000000098ad64508080808080808080808080808080808 5fe8e1bab5b5b5b5b5b5b7dad63f00000000000000000000000000000000 00000000000000000000098aecc6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 cd360000000000000036cf93130808080808080808080808080808080808 f1c5b5b5b5b5b5b5b5c4eb900c0000000000000000000000000000000000 00000000000000000036d1dcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 030000000000000783d54508080808080808080808080808080808080808 b6b5b5b5b5b5b5b7d8d63f00000000000000000000000000000000000000 000000000000000783ebc6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 00000000000031cb94140808080808080808080808080808080808080808 b5b5b5b5b5b5c2ea910c0000000000000000000000000000000000000000 00000000000031ccdcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 00000000057dd44608080808080808080808080808080808080808080808 b5b5b5b5b6d6d64000000000000000000000000000000000000000000000 00000000057deac6b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0000002ac795140808080808080808080808080808080808080808080808 b5b5b5c0ea920c0000000000000000000000000000000000000000000000 0000002ac7dcb8b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/south-africa1.gif0100644000175100001560000000121210007313167016024 0ustar takeshisaGIF87a 蝟wwvvLF番幀孛__墻pp咀ii KKgS<< 限--梦幻 謾E? 卵6,笈罎と衄矧hh轢処循御TTF@%%H 罍}}ZZt誄`QQ664411莓**((艾##槙杢 癘痰罍=忠昼炸蛬悴癖喝, $6`H#dLU4E>] c5BSbΣWe\2閏'%I/.G壞嶐;a[:痰邃7_=g結Y8j踉3^"1-@獨3T榧#y.prＧ )-@`漸ニ,H窺C`t)豊DI4&[OhPh(E[,煩顔S)0V0廸;mysql-4.00.12/Flags/south-africa1.txt0100644000175100001560000000000010007313167016070 0ustar takeshisamysql-4.00.12/Flags/south-korea.eps0100644000175100001560000001003010007313165015635 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7eff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f5f7f7f7f7f7f7 f7f7f7f7f7f7eff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f5f7f7f7f7f7f7 f7f7f7f7f7f7eff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f5f7f7f7f7f7f7 f7f7f7f7f7985ad7f7f7f7f7f7f7f7f7f7f7f7f7f7f7c255d3f7f7f7f7f7 f7f7f7f7f7985ad7f7f7f7f7f7f7f7f7f7f7f7f7f7f7c255d3f7f7f7f7f7 f7f7f7f7f7985ad7f7f7f7f7f7f7f7f7f7f7f7f7f7f7c255d3f7f7f7f7f7 f7f7f7f7d6434363f7f7f7f7f7f7f7f7f7f7f7f7f7f0474476f6f7f7f7f7 f7f7f7f7d6434363f7f7f7f7f7f7f7f7f7f7f7f7f7f0474476f6f7f7f7f7 f7f7f7f7d6434363f7f7f7f7f7f7f7f7f7f7f7f7f7f0474476f6f7f7f7f7 f7f7f7f7584345e4f7f7f7f7f7f6f1f1f7f7f7f7f7f7ba5a4391f7f7f7f7 f7f7f7f7584345e4f7f7f7f7f7f4d7d9f5f7f7f7f7f7ba5a4391f7f7f7f7 f7f7f7f7584345e4f7f7f7f7f7f4d8d9f5f7f7f7f7f7ba5a4391f7f7f7f7 f7f7f7f7d65ab0f7f7f7f7f5decac6c6cbe0f6f7f7f7f76570dcf7f7f7f7 f7f7f7f7d65ab0f7f7f7f7ef791300001884f3f7f7f7f76570dcf7f7f7f7 f7f7f7f7d65ab0f7f7f7f7ef791300001885f3f7f7f7f76570dcf7f7f7f7 f7f7f7f7f7f3f7f7f7f7f5d2c6c6c6c6c6c6d6f7f7f7f7ecf4f7f7f7f7f7 f7f7f7f7f7f3f7f7f7f7ed3a0000000000004ef4f7f7f7ecf4f7f7f7f7f7 f7f7f7f7f7f3f7f7f7f7ed3a0000000000004ef4f7f7f7ecf4f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7d9c6c6c6c6c6c6c6c6e3f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f76c00000000000000008ff7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f76e00000000000000008ff7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7eebbc6c6c6c6bc68548ecef7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7ee0a000000000000000026f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f41600000000095a6d3526f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7c8b1c6c6c6c53908080875f5f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7c600000000000000000001eaf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7ea140000000187b5b5b54eeaf7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7c75fc6c6c66a080808082cf4f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7c500000000000000000000e7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7ea6300000058b5b5b5b593e8f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7ed114b6b36080808080838f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7ed0900000000000000001df7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f4b7755789b5b5b5b5b5a9f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f76b080808080808080884f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f76600000000000000007ef7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7d0b5b5b5b5b5b5b5b5d5f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7eef6f7f7f7ea3508080808080844f1f7f7f7ecedf7f7f7f7f7 f7f7f7f7f7eef6f7f7f7e92f0000000000003ef1f7f7f7ecedf7f7f7f7f7 f7f7f7f7f7eef6f7f7f7f3c1b5b5b5b5b5b5c6f5f7f7f7ecedf7f7f7f7f7 f7f7f7f7cd569af7f7f7f7eb70140808187bf0f7f7f7f76b60d6f7f7f7f7 f7f7f7f7cd569af7f7f7f7ea6b0c00001177f0f7f7f7f76b60d6f7f7f7f7 f7f7f7f7cd569af7f7f7f7f4d2b8b5b5b9d5f5f7f7f7f76b60d6f7f7f7f7 f7f7f7f7604b52dff7f7f7f7f7f1d0d2f3f7f7f7f7f7b4794787f7f7f7f7 f7f7f7f7604b52dff7f7f7f7f7f1cfd1f3f7f7f7f7f7b4794787f7f7f7f7 f7f7f7f7604b52dff7f7f7f7f7f5ecedf6f7f7f7f7f7b4794787f7f7f7f7 f7f7f7f7e0504563f7f7f7f7f7f7f7f7f7f7f7f7f7f14a4678f5f7f7f7f7 f7f7f7f7e0504563f7f7f7f7f7f7f7f7f7f7f7f7f7f14a4678f5f7f7f7f7 f7f7f7f7e0504563f7f7f7f7f7f7f7f7f7f7f7f7f7f14a4678f5f7f7f7f7 f7f7f7f7f79c64ddf7f7f7f7f7f7f7f7f7f7f7f7f7f7d060d8f7f7f7f7f7 f7f7f7f7f79c64ddf7f7f7f7f7f7f7f7f7f7f7f7f7f7d060d8f7f7f7f7f7 f7f7f7f7f79c64ddf7f7f7f7f7f7f7f7f7f7f7f7f7f7d060d8f7f7f7f7f7 f7f7f7f7f7f7f4f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f4f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f4f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 grestore showpage %%Trailer mysql-4.00.12/Flags/south-korea.gif0100644000175100001560000000122710007313165015623 0ustar takeshisaGIF87a 迯韶 NN9騅慄播yyylnD> kkk eee髑5/ccc_cUUU迯KKKGGG汎EEECCC韶韲銕厮迪跛粐朽玻樛榴慓pk 蛍嶽佩們銓詑托捶査埼褪裴幹完旭::KujX{wTm鴻艾xxxvvvuNppp佻5ddd闖```yyZZZXXXVVV齠RRRPPPJJJFFF8DDD齠齣髑闖闕迯kW齠,烝6毫殼忻~孑嗷様hZkf侘&&裼, X^[?Pf1i.!!#ZF XQ!'A 23P!.P7MO;; KSH*\8黙;&"Ｃ 樛C0k@Jm裘g(G51Z`a~ h湾9A/K=Ol(RDs XP汰p_1R##,C#N\T[1&$) T∧TtrトEx0)U '+T6a抒X]k(;mysql-4.00.12/Flags/south-korea.txt0100644000175100001560000000000010007313165015661 0ustar takeshisamysql-4.00.12/Flags/spain.eps0100644000175100001560000001003010007313167014510 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7 040404040404040404040404040404040404040404040404040404040404 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff fdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfdfd 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 fcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfcfc f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/spain.gif0100644000175100001560000000021210007313167014467 0ustar takeshisaGIF87a , W載MIR疝ьhl*D,tm琶|pH 0,'(V∪z逗0wT3^dNw$;mysql-4.00.12/Flags/spain.txt0100644000175100001560000000000010007313167014534 0ustar takeshisamysql-4.00.12/Flags/sweden.eps0100644000175100001560000001003010007313170014655 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0e0e0e0e0e0e0e16fffffff10e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e0e 060606060606060efffffff0060606060606060606060606060606060606 b1b1b1b1b1b1b1ab0000000ab1b1b1b1b1b1b1b1b1b1b1b1b1b1b1b1b1b1 fefefefefefefefefffffffffefefefefefefefefefefefefefefefefefe fefefefefefefefefffffffffefefefefefefefefefefefefefefefefefe 010101010101010100000000010101010101010101010101010101010101 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 f3f3f3f3f3f3f3f3fffffffef3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 f3f3f3f3f3f3f3f3fffffffef3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 080808080808080800000000080808080808080808080808080808080808 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 0808080808080810fffffff1080808080808080808080808080808080808 0000000000000008fffffff0000000000000000000000000000000000000 b5b5b5b5b5b5b5af0000000bb5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 grestore showpage %%Trailer mysql-4.00.12/Flags/sweden.gif0100644000175100001560000000030110007313170014633 0ustar takeshisaGIF87a 髏 髏 齠, vIU-'Dz 煎瓷# s[1."[惑r bD$^t(憺zxL.毎Grh斯/{Nw9BdR粡;Gwy|x~F7;mysql-4.00.12/Flags/sweden.txt0100644000175100001560000000000010007313170014701 0ustar takeshisamysql-4.00.12/Flags/switzerland.eps0100644000175100001560000001003010007313166015743 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c7c7c7c7c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000404040400000000000000000000000000 000000000000000000000000000404040400000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c8c8c8cbf7f7f7f4c8c8c8c8c6c6c6c6c6c6c6c6c6 00000000000000000008080817f7f7f7e708080807000000000000000000 00000000000000000008080817f7f7f7e708080807000000000000000000 c6c6c6c6c6c6c6c6c9f7f7f7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 c6c6c6c6c6c6c6c6c9f7f7f7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 c6c6c6c6c6c6c6c6c9f7f7f7f7f7f7f7f7f7f7f7f3c6c6c6c6c6c6c6c6c6 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 00000000000000000cf7f7f7f7f7f7f7f7f7f7f7e3000000000000000000 c6c6c6c6c6c6c6c6c8f5f5f5f5f7f7f7f7f5f5f5f1c6c6c6c6c6c6c6c6c6 00000000000000000beeeeeeeff7f7f7f6eeeeeeda000000000000000000 00000000000000000cefefefeff7f7f7f6efefefdb000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f7f7f7f4c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000ff7f7f7e700000000000000000000000000 00000000000000000000000010f7f7f7e700000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c9f5f5f5f2c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000000000000feaeaeada00000000000000000000000000 0000000000000000000000000febebebdb00000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/switzerland.gif0100644000175100001560000000035510007313166015732 0ustar takeshisaGIF87a 鈿黹笏艸鰄枷 騫柯 闖裨, r di%〓l訃*弩{J篁YB$a$B`kA-8 堙c&]5`|}秩1:qN] 7Qe4JOL5P5s,9:d($!;mysql-4.00.12/Flags/switzerland.txt0100644000175100001560000000000010007313166015767 0ustar takeshisamysql-4.00.12/Flags/taiwan.eps0100644000175100001560000001003010007313166014660 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 080808080808081108080808080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000900000000000000000000000000000000000000000000 b5b5b5b5b5b5b5b7b5b5b5b5b5b5aa000000000000000000000000000000 0808080808490e9e11450808080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000043069a0a3f0000000000000000000000000000000000000000 b5b5b5b5b5c7b7deb8c6b5b5b5b5aa000000000000000000000000000000 0808080e14658bb28d59170c080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000060c6087b089530f04000000000000000000000000000000000000 b5b5b5b7b8cfd9e4dacbb9b6b5b5aa000000000000000000000000000000 0808080baba1f7f7f7a0a009080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 00000003a89ef7f7f79d9c00000000000000000000000000000000000000 b5b5b5b6e2dff7f7f7dfdfb5b5b5aa000000000000000000000000000000 0808082b5becf7f7f7e06025080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000002456ecf7f7f7df5b1e000000000000000000000000000000000000 b5b5b5bfccf4f7f7f7f1cdbdb5b5aa000000000000000000000000000000 0808082556eaf7f7f7de5a20080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000001e50eaf7f7f7dd5418000000000000000000000000000000000000 b5b5b5bdcaf3f7f7f7f0ccbcb5b5aa000000000000000000000000000000 0808080bb099f7f7f799a509080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 00000004ad96f7f7f795a201000000000000000000000000000000000000 b5b5b5b6e3ddf7f7f7dde0b5b5b5aa000000000000000000000000000000 0808080d0e6b82b2855f100b080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000507667eb081590903000000000000000000000000000000000000 b5b5b5b6b7d0d7e4d7cdb7b6b5b5aa000000000000000000000000000000 0808080808440c970f410808080813c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 00000000003e0493073b0000000000000000000000000000000000000000 b5b5b5b5b5c6b6dcb7c5b5b5b5b5aa000000000000000000000000000000 0e0e0e0e0e0e0e150e0e0e0e0e0e19c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000700000000000000000000000000000000000000000000 b0b0b0b0b0b0b0b2b0b0b0b0b0b0a6000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 010101010101010101010101010101000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/taiwan.gif0100644000175100001560000000057110007313166014647 0ustar takeshisaGIF87a  YS血踉ア 衿汾D>[V漫  VPIC`[~ E? A;  玖褥 +$ZT瀑_Y e`労 怙熨欅淨屋%kf, @pH,Er0tJ ZqaF珸UIs0額gcAp v.-5{|Tq5#Rq'0/ q63,&+qJ  ^!況!原 b2疎団読%B米麺穫乖飯墻忤p孳}槿H矣DA;mysql-4.00.12/Flags/taiwan.txt0100644000175100001560000000000010007313166014704 0ustar takeshisamysql-4.00.12/Flags/turkey.eps0100644000175100001560000001011210007313170014714 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: turkey.ps %%Pages: 1 %%BoundingBox: 287 406 307 435 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 287.9 406.6 translate 19.2 28.8 scale 0.5 0.5 translate 90 rotate -0.5 -0.5 translate 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c4c6c7c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000007020000000000000000000000000000000000 000000000000000000000007020000000000000000000000000000000000 c6c6c6c6c6c6c6c4c9dce2d7c9c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000106d8953100000000000000000000000000000000000 0000000000000000106e8954100000000000000000000000000000000000 c6c6c6c6c6c6c4d3f0e9d1c7c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000043d3aa3807000000000000000000000000000000000000 0000000000000043d4aa3807000000000000000000000000000000000000 c6c6c6c6c6c4d1f9e2c4c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 00000000000038fa89000000000000000000000000000000000000000000 00000000000038fa89000000000000000000000000000000000000000000 c6c6c6c6c6c7f0f0c6c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000007d3d300000000000000000000000000000000000000000000 000000000007d4d400000000000000000000000000000000000000000000 c6c6c6c6c4d1f9dcc4c6c6c6c6c4d3cdccc6c6c6c6c6c6c6c6c6c6c6c6c6 000000000038fa6d00000000000043271c02000000000000000000000000 000000000038fa6e00000000000043271c02000000000000000000000000 c6c6c6c6c4dcf9d7c4c6c6c6c6cde9f9d3c4c6c6c6c6c6c6c6c6c6c6c6c6 00000000006dfa53000000000027aafa4300000000000000000000000000 00000000006efa54000000000027aafa4300000000000000000000000000 c6c6c6c6c4dcf9d7c4c6c6c6c6cde9f0d7c6c6c6c6c6c6c6c6c6c6c6c6c6 00000000006dfa53000000000027aad35300000000000000000000000000 00000000006efa54000000000027aad45400000000000000000000000000 c6c6c6c6c4d3f9dcc4c6c6c6c6c4d3cdc9c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000043fa6d00000000000043271002000000000000000000000000 000000000043fa6e00000000000043271002000000000000000000000000 c6c6c6c6c6c7f0f0c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000007d3d302000000000000000000000000000000000000000000 000000000007d4d402000000000000000000000000000000000000000000 c6c6c6c6c6c4d1f9e2c4c4c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 00000000000038fa89000000000000000000000000000000000000000000 00000000000038fa89000000000000000000000000000000000000000000 c6c6c6c6c6c6c4d3f0e9d1c7c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000043d3aa3809000000000000000000000000000000000000 0000000000000043d4aa3809000000000000000000000000000000000000 c6c6c6c6c6c6c6c4c9dce2d7c9c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 0000000000000000106d8953100000000000000000000000000000000000 0000000000000000106e8954100000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c4c6c7c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000007020000000000000000000000000000000000 000000000000000000000007020000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/turkey.gif0100644000175100001560000000025110007313170014675 0ustar takeshisaGIF89aSTmn靦奘 ''88CC薨,^I8詬;.axZ_#<盟^388[ 6bD*竄1h9N! H0I=Y8玩l`WL(Z;mysql-4.00.12/Flags/turkey.txt0100644000175100001560000000000010007313170014737 0ustar takeshisamysql-4.00.12/Flags/ukraine.eps0100644000175100001560000001003010007313167015034 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 181818181818181818181818181818181818181818181818181818181818 b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5b5 efefefefefefefefefefefefefefefefefefefefefefefefefefefefefef 1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7b7 e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8e8 fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 010101010101010101010101010101010101010101010101010101010101 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/ukraine.gif0100644000175100001560000000020410007313167015014 0ustar takeshisaGIF87a 居決, Q載-IR疝ьd0r貴"x陷 pH,rl:櫨t P(vKr溏4,~僕3z i ;mysql-4.00.12/Flags/ukraine.txt0100644000175100001560000000000010007313167015060 0ustar takeshisamysql-4.00.12/Flags/usa.eps0100644000175100001560000001003010007313172014162 0ustar takeshisa%!PS-Adobe-2.0 EPSF-2.0 %%Creator: pnmtops %%Title: noname.ps %%Pages: 1 %%BoundingBox: 291 371 320 391 %%EndComments /readstring { currentfile exch readhexstring pop } bind def /rpicstr 30 string def /gpicstr 30 string def /bpicstr 30 string def %%EndProlog %%Page: 1 1 gsave 291.6 371.4 translate 28.8 19.2 scale 30 20 8 [ 30 0 0 -20 0 20 ] { rpicstr readstring } { gpicstr readstring } { bpicstr readstring } true 3 colorimage 182608340a122c08300e0e31082b1ec6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 111f002d020a25002907062a00240b000000000000000000000000000000 b9bdb5c1b6b8bfb5c0b7b7c0b5bfad000000000000000000000000000000 1a2422331d182b243117183223291fdcdcdcdcdcdcdcdcdcdcdcdcdcdcdc 121d1a2c1610241c2a0f112b1c2211717171717171717171717171717171 babdbcc1bbb9bfbdc0b9b9c0bdbeb4717171717171717171717171717171 0a134413301e134513262813451316f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 020b3e0c29170b3f0c1f210c3f0c0ff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 b5b8c5b8c0bbb8c6b8bdbeb8c6b8b9f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 28360e54101b430e4e1212500e4029c9c9c9c9c9c9c9c9c9c9c9c9c9c9c9 212f064e08133d06480b0a49063a17101010101010101010101010101010 bec2b7cab7bac5b7c8b8b8c9b7c5b1101010101010101010101010101010 080e580a3f250b5b0a30340a5b0c14d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9 00065302391e035603292d02550406616161616161616161616161616161 b5b7cbb6c4bdb6ccb6c0c1b6ccb6b0616161616161616161616161616161 2a3d085c0b1b4c0856110f5808492cf7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 233700570313460051090753004325f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 bec4b5ccb6bac8b5cab7b7cbb5c7bff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 080c5d084425096008323708600913cccccccccccccccccccccccccccccc 000458003e1e015b002b30005a01021f1f1f1f1f1f1f1f1f1f1f1f1f1f1f b5b6cdb5c5bdb5cdb5c1c2b5cdb5ac1f1f1f1f1f1f1f1f1f1f1f1f1f1f1f 293f085e0a1a4e0858100e5a084b29d6d6d6d6d6d6d6d6d6d6d6d6d6d6d6 22390059021348005308065500451b525252525252525252525252525252 bec4b5cdb6bac8b5cbb7b7ccb5c7b5525252525252525252525252525252 080c58094222095b083034085a0a16f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 000452013b1b015500292e0055020ff7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 b5b6cbb5c5bcb5ccb5c0c1b5ccb5b9f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 23370e500d19440e4b12114c0e4224cfcfcfcfcfcfcfcfcfcfcfcfcfcfcf 1b31064a05113e06450a0946063c132f2f2f2f2f2f2f2f2f2f2f2f2f2f2f bcc2b7c9b6bac5b7c7b8b8c8b7c5b22f2f2f2f2f2f2f2f2f2f2f2f2f2f2f 4f504857484d524856494956485155d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3 494a425142474d4250434351424c47424242424242424242424242424242 c9c9c7cbc7c8cac7cbc7c7cbc7c9c1424242424242424242424242424242 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2d2 3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e 3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e3e d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0d0 323232323232323232323232323232323232323232323232323232323232 323232323232323232323232323232323232323232323232323232323232 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5 4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e 4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e cdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd 232323232323232323232323232323232323232323232323232323232323 232323232323232323232323232323232323232323232323232323232323 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7 d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9d9 5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d 5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d5d c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 grestore showpage %%Trailer mysql-4.00.12/Flags/usa.gif0100644000175100001560000000133310007313172014146 0ustar takeshisaGIF87a  PJZU B;*#症LF4.VQ&HB郊aaRM "6/MG@:系//)2+IC`[$ E?\W 70NH XS 3,鑑NN22=7 欽RR PI +$ B<兎4-KEVP0)砿qq#QL" ,%[UC=徒 (!WQ堀]]?9VQ瞥##1*`Z$女#]XD>OI71) )"XR牧>>2+%TN篇BBUG$^Y, B '=^H'A2dT'9%D&HH陰/PN ! 8cC(SG 8DRpb` 詑@驕I2;hX粉SA[8p矗B? MySQL Reference Manual for version 4.0.12. - 7 MySQL テーブル型 Go to the first, previous, next, last section, table of contents.

      7 MySQL テーブル型

      MySQL Version 3.23.6では、ISAM、HEAP そして MyISAMの 三つの基本的なテーブル形式を使うことができます。もっと新しいバージョンで は、コンパイルする方法によってInnoDB や BDB といった形式も サポートしています。

      新しいテーブルを作成する際にどのテーブル形式を使用するか指定すればよろしい わけですが、無指定の場合は通常 MyISAM になります。

      MySQL will always create a `.frm' file to hold the table and column definitions. The table's index and data will be stored in one or more other files, depending on the table type.

      If you try to use a table type that is not compiled-in or activated, MySQL will instead create a table of type MyISAM. This behaviour is convenient when you want to copy tables between MySQL servers that support different table types. (Perhaps your master server supports transactional storage engines for increased safety, while the slave servers use only non-transactional storage engines for greater speed.)

      This automatic change of table types can be confusing for new MySQL users. We plan to fix this by introducing warnings in the new client-server protocol in version 4.1 and generating a warning when a table type is automatically changed.

      ALTER TABLE 文を使用すれば、テーブルを違う形式に変更できます。 「6.5.4 ALTER TABLE 構文」節参照.

      MySQL では、二つの違う種類のテーブルをサポートしていることに注意してください。 一つはトランザクションセーフのテーブル(BDB, InnoDB)、 もう一つはトランザクションを持たないテーブル (HEAP, ISAM, MERGE, and MyISAM).

      トランザクションセーフのテーブル(Transaction Safe Tables) の利点は(TST):

      • Safer. Even if MySQL crashes or you get hardware problems, you can get your data back, either by automatic recovery or from a backup the transaction log.
      • You can combine many statements and accept these all in one go with the COMMIT command.
      • You can execute ROLLBACK to ignore your changes (if you are not running in auto-commit mode).
      • If an update fails, all your changes will be restored. (With NTST tables all changes that have taken place are permanent)
      • Can provide better concurrency if the table gets many updates concurrently with reads.

      Note that to use InnoDB tables you have to use at least the innodb_data_file_path startup option. 「7.5.2 InnoDB 起動オプション」節参照.

      非トランザクションセーフ(Not Transaction Safe Tables)のテーブルの利点は(NTST):

      • Much faster as there is no transaction overhead.
      • Will use less disk space as there is no overhead of transactions.
      • Will use less memory to do updates.

      You can combine TST and NTST tables in the same statements to get the best of both worlds.

      7.1 MyISAM テーブル (3.23.0以上)

      MyISAM は、MySQL Version 3.23 でのデフォルトのテーブル形式です． これは ISAM コードを基にし、多くの便利な拡張機能を持っています。

      インデックスは .MYI (MYIndex) 拡張子のつくファイルに保存され、 データは、 .MYD (MYData) 拡張子のつくファイルに保存されます。 myisamchk ユーティリティを使用して、 MyISAM テーブルの 検査・修復が可能です。 「4.4.6.7 Using myisamchk for Crash Recovery」節参照. myisampack コマンドを使用して、MyISAM を圧縮して 小さくすることが可能です 「4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ」節参照.

      The following is new in MyISAM:

      • There is a flag in the MyISAM file that indicates whether the table was closed correctly. If mysqld is started with --myisam-recover, MyISAM tables will automatically be checked and/or repaired on open if the table wasn't closed properly.
      • You can INSERT new rows in a table that doesn't have free blocks in the middle of the datafile, at the same time other threads are reading from the table (concurrent insert). An free block can come from an update of a dynamic length row with much data to a row with less data or when deleting rows. When all free blocks are used up, all future inserts will be concurrent again.
      • 大ファイル (63 bit) のサポート。 ただし、filesystems/operating systems が大ファイルをサポートしている場合。
      • 全データは、下位バイトが先にかかれます。 これは、データを、マシン・OS 非依存にしました。 The only requirement is that the machine uses two's-complement signed integers (as every machine for the last 20 years has) and IEEE floating-point format (also totally dominant among mainstream machines). The only area of machines that may not support binary compatibility are embedded systems (because they sometimes have peculiar processors). There is no big speed penalty in storing data low byte first; the bytes in a table row is normally unaligned and it doesn't take that much more power to read an unaligned byte in order than in reverse order. The actual fetch-column-value code is also not time critical compared to other code.
      • 全数値キーは高位バイトが先に書かれます。 これはインデックスの圧縮率を 良くします。
      • Internal handling of one AUTO_INCREMENT column. MyISAM will automatically update this on INSERT/UPDATE. The AUTO_INCREMENT value can be reset with myisamchk. This will make AUTO_INCREMENT columns faster (at least 10%) and old numbers will not be reused as with the old ISAM. Note that when an AUTO_INCREMENT is defined on the end of a multi-part-key the old behaviour is still present.
      • When inserted in sorted order (as when you are using an AUTO_INCREMENT column) the key tree will be split so that the high node only contains one key. This will improve the space utilisation in the key tree.
      • BLOB と TEXT フィールドにインデックスが張れます
      • NULL 値をインデックスの張られたフィールドに許します． This takes 0-1 bytes/key.
      • 現在、キーの最大長はデフォルトで 500 バイトです。 (再コンパイルで 変更可能). In cases of keys longer than 250 bytes, a bigger key block size than the default of 1024 bytes is used for this key.
      • 1テーブルあたりの最大のキーの数は 32個 がデフォルトです. これは myisamchk を再コンパイル無しに、64個まで増やすことが出来ます.
      • myisamchk を --update-state オプションで実行すると、 myisamchk はテーブルにチェックをおこなったマークをつけます。 myisamchk --fast は、このマークが無いテーブルだけをチェックします。
      • myisamchk -a stores statistics for key parts (and not only for whole keys as in ISAM).
      • Dynamic size rows will now be much less fragmented when mixing deletes with updates and inserts. This is done by automatically combining adjacent deleted blocks and by extending blocks if the next block is deleted.
      • myisampack は BLOB と VARCHAR フィールドをパックすることが 可能です。
      • You can use put the datafile and index file on different directories to get more speed (with the DATA/INDEX DIRECTORY="path" option to CREATE TABLE). 「6.5.3 CREATE TABLE 構文」節参照.

      MyISAM also supports the following things, which MySQL will be able to use in the near future:

      • 真の VARCHAR 型のサポート; a VARCHAR column starts with a length stored in 2 bytes.
      • Tables with VARCHAR may have fixed or dynamic record length.
      • VARCHAR and CHAR may be up to 64K. All key segments have their own language definition. This will enable MySQL to have different language definitions per column.
      • A hashed computed index can be used for UNIQUE. This will allow you to have UNIQUE on any combination of columns in a table. (You can't search on a UNIQUE computed index, however.)

      Note that index files are usually much smaller with MyISAM than with ISAM. This means that MyISAM will normally use less system resources than ISAM, but will need more CPU time when inserting data into a compressed index.

      mysqld に与える以下のオプションは、 MyISAM テーブルの振る舞いを変更できます. 「4.5.6.4 SHOW VARIABLES」節参照.

      Option Description
      --myisam-recover=# 壊れたテーブルを自動でリカバリ.
      -O myisam_sort_buffer_size=# リカバリに使用されるバッファ
      --delay-key-write=ALL Don't flush key buffers between writes for any MyISAM table
      -O myisam_max_extra_sort_file_size=# Used to help MySQL to decide when to use the slow but safe key cache index create method. Note that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version.
      -O myisam_max_sort_file_size=# Don't use the fast sort index method to created index if the temporary file would get bigger than this. Note that this parameter is given in megabytes before 4.0.3 and in bytes starting from this version.
      -O bulk_insert_buffer_size=# Size of tree cache used in bulk insert optimisation. Note that this is a limit per thread!

      automatic recovery は mysqld を --myisam-recover=# オプション (3.23.26以上) で起動したときに有効になります. 「4.1.1 mysqld コマンド行オプション」節参照. On open, the table is checked if it's marked as crashed or if the open count variable for the table is not 0 and you are running with --skip-external-locking.(4.0.3以前では --skip-locking) 上のどれかに当てはまる場合、以下を行ないます。

      • テーブルはエラーのためにチェックされます.
      • もしエラーが見つかったなら、そのテーブルの fast repair (sort はするけれども データファイルの再構築は行なわない) を行ないます.
      • もし修復がデータファイルのエラーのために失敗したら (例えば duplicate key error)、 再びリペアを試みますが、この時は、データファイルを再構築します.
      • もしリペアが失敗したら、さらにもう一度、古い修復方法(ソート無しに、 レコード単位に書く)で、修復を試みます。 この方法は、いかなるタイプのエラーでも、少ないディスクで修復可能です。

      If the recover wouldn't be able to recover all rows from a previous completed statement and you didn't specify FORCE as an option to myisam-recover, then the automatic repair will abort with an error message in the error file: 

      Error: Couldn't repair table: test.g00pages

      この FORCE を使用した場合には、エラーメッセージは以下のようになります： 

      Warning: Found 344 of 354 rows when repairing ./test/g00pages

      もしあなたが自動修復を BACKUP で実行しているなら、 あなたは、データベースのディレクトリから `tablename-datetime.BAK' のようなファイルを自動的にバックアップ メディアに移動する cron スクリプトを作るべきです。

      「4.1.1 mysqld コマンド行オプション」節参照.

      7.1.1 Space Needed for Keys

      MySQL can support different index types, but the normal type is ISAM or MyISAM. これらは B-tree index を使用します。インデックスファイルのサイズは、 (key_length+4)/0.67 でおおざっぱに計算できます。 (This is for the worst case when all keys are inserted in sorted order and we don't have any compressed keys.)

      文字インデックスは圧縮されます。 If the first index part is a string, it will also be prefix compressed. Space compression makes the index file smaller than the above figures if the string column has a lot of trailing space or is a VARCHAR column that is not always used to the full length. Prefix compression is used on keys that start with a string. Prefix compression helps if there are many strings with an identical prefix.

      In MyISAM tables, you can also prefix compress numbers by specifying PACK_KEYS=1 when you create the table. This helps when you have many integer keys that have an identical prefix when the numbers are stored high-byte first.

      7.1.2 MyISAM Table Formats

      MyISAM supports 3 different table types. Two of them are chosen automatically depending on the type of columns you are using. The third, compressed tables, can only be created with the myisampack tool.

      When you CREATE or ALTER a table you can for tables that doesn't have BLOBs force the table format to DYNAMIC or FIXED with the ROW_FORMAT=# table option. In the future you will be able to compress/decompress tables by specifying ROW_FORMAT=compressed | default to ALTER TABLE. 「6.5.3 CREATE TABLE 構文」節参照.

      7.1.2.1 Static (Fixed-length) Table Characteristics

      This is the default format. It's used when the table contains no VARCHAR, BLOB, or TEXT columns.

      このフォーマットは、最も単純、かつ、安全なフォーマットです。 これは, Disk 上に作られるテーブルの中で、最も速いフォーマットでもあります。 これはディスク上のデータを見つけやすいからです。 When looking up something with an index and static format it is very simple. Just multiply the row number by the row length.

      Also, when scanning a table it is very easy to read a constant number of records with each disk read.

      The security is evidenced if your computer crashes when writing to a fixed-size MyISAM file, in which case myisamchk can easily figure out where each row starts and ends. So it can usually reclaim all records except the partially written one. Note that in MySQL all indexes can always be reconstructed:

      • 全ての CHAR, NUMERIC, DECIMAL フィールドは、そのフィールド 長に足りない部分にはスペースが埋められます。
      • とても速い
      • キャッシュしやすい。
      • クラッシュの後再構築しやすい。なぜならレコードが固定された位置に割り当てられてい るから。
      • Doesn't have to be reorganised (with myisamchk) unless a huge number of records are deleted and you want to return free disk space to the operating system.
      • 通常、動的テーブルよりも多くのディスク容量が必要。

      7.1.2.2 Dynamic Table Characteristics

      This format is used if the table contains any VARCHAR, BLOB, or TEXT columns or if the table was created with ROW_FORMAT=dynamic.

      この形式は少し複雑です。 なぜならそれぞれのレコードが、レコードがどのぐらいの 長さを持っているかを記録するヘッダーを持っているからです。 One record can also end up at more than one location when it is made longer at an update.

      OPTIMIZE table か myisamchk を使用して、テーブルの フラグメンテーションを修正することが可能です。 If you have static data that you access/change a lot in the same table as some VARCHAR or BLOB columns, it might be a good idea to move the dynamic columns to other tables just to avoid fragmentation:

      • 全ての文字フィールドが動的になります（ただし4byteより短い物は除きます）
      • それぞれのレコードの先頭には、フィールドの状態を表すビット・マップがきます。 このビットは、どの文字型フィールドが空文字('')なのか、 どの数値フィールドがゼロなのかを示します。 (これはフィールドの値が NULL 値とは違います)。 もし、文字型フィールドの文字列の長さ(後に続く空白は取り除かれる)が ゼロ で あったり、あるいは、数値フィールドの値が ゼロ であった場合は、 そのフィールドはビット・マップにマークされ、値はディスクには保存されません。 空文字ではない場合は、文字列のバイト数がビット・マップに記録され、 文字列自身がフィールドに保存されます。
      • 通常、固定長のテーブルよりも少ないディスク容量ですみます
      • それぞれのレコードは、要求されただけのスペースを使用します。 もしあるレコードが大きくなると、要求された分、それを多くの断片に分けます。 この結果、レコードのフラグメンテーションが発生します。
      • If you update a row with information that extends the row length, the row will be fragmented. In this case, you may have to run myisamchk -r from time to time to get better performance. Use myisamchk -ei tbl_name for some statistics.
      • Not as easy to reconstruct after a crash, because a record may be fragmented into many pieces and a link (fragment) may be missing.
      • 期待されるレコードの長さは： 
        3
+ (フィールド数 + 7) / 8
+ (char フィールドの数)
+ 数値フィールドをパックしたサイズ
+ 文字の長さ
+ (NULL フィールドの数 + 7) / 8
        There is a penalty of 6 bytes for each link. A dynamic record is linked whenever an update causes an enlargement of the record. Each new link will be at least 20 bytes, so the next enlargement will probably go in the same link. If not, there will be another link. You may check how many links there are with myisamchk -ed. All links may be removed with myisamchk -r.

      7.1.2.3 圧縮テーブルの特徴

      これは、myisampack ツール (pack_isam は ISAM テーブル用)に

      • 全ての MySQL ディストリビューション ( MySQL が GPL になる以前の物も含) は、 myisampack で圧縮されたテーブルを読むことが可能です。
      • 圧縮テーブルはディスクスペースを節約します。 これは disk usage を少なくするので、遅いディスク(CD-ROM など)にはとても好都合です。
      • それぞれのレコード別に圧縮されます(アクセスのオーバーヘッドがとても少ない)。 レコードのヘッダは固定で(1-3 Bytes)、テーブル中の最大の大きさのレコードに依存します。 Each column is compressed differently. Some of the compression types are:
        • There is usually a different Huffman table for each column.
        • Suffix space compression.
        • Prefix space compression.
        • Numbers with value 0 are stored using 1 bit.
        • もし整数型のフィールドが小さな値に収まっているならば、 そのフィードは、できる限り小さなフィールド型に保存されます。 例えば、BIGINT フィールド(8bytes)の値全てが 0 から 255 に 収まっていれば、TINYINT フィールド (1 byte) に保存されます。
        • If a column has only a small set of possible values, the column type is converted to ENUM.
        • A column may use a combination of the above compressions.
      • 固定長、可変長のレコードを扱うことができます
      • myisamchk で、伸長できます。

      7.1.3 MyISAM table problems.

      The file format that MySQL uses to store data has been extensively tested, but there are always circumstances that may cause database tables to become corrupted.

      7.1.3.1 壊れた MyISAM テーブル

      いくら MyISAM テーブルがとても信頼できるとは言え(SQL文を返す前に テーブルへの変更を全て書き出す)、 以下のような事が起きた場合には、テーブルが壊れるかもしれません：

      • mysqld プロセスが書き込み途中で kill された
      • コンピュータの不意のシャットダウン(例えば電源断)
      • ハードウェアのエラー
      • 稼働中のテーブルに対して外部プログラム(myisamchkのような)を使用
      • MySQL か MyISAM コードのソフトウェアのバグ

      壊れたテーブルの、典型的な症状は：

      • そのテーブルからデータを選択中に Incorrect key file for table: '...'. Try to repair it エラーが出る
      • クエリがテーブル内のレコードを見つけれなかったり、 不完全なデータを返したり。

      CHECK TABLE 命令を使用して、テーブルが OK か否かを 確かめることができます。 「4.4.4 CHECK TABLE 構文 (3.23.13以上)」節参照.

      REPAIR TABLE で不正なテーブルを修復することが可能です. 「4.4.5 REPAIR TABLE 構文 (3.23.14以上)」節参照. mysqld が動作していないときに、 myisamchk コマンドを使用して テーブルを修復することも可能です。 myisamchk syntax.

      もし多くの不整合がテーブルに起きたならば、 その理由を探すべきです！ 「A.4.1 What To Do If MySQL Keeps Crashing」節参照.

      In this case the most important thing to know is if the table got corrupted if the mysqld died (one can easily verify this by checking if there is a recent row restarted mysqld in the mysqld error file). If this isn't the case, then you should try to make a test case of this. 「E.1.6 Making a Test Case When You Experience Table Corruption」節参照.

      7.1.3.2 Clients is using or hasn't closed the table properly

      Each MyISAM `.MYI' file has in the header a counter that can be used to check if a table has been closed properly.

      If you get the following warning from CHECK TABLE or myisamchk: 

      # clients is using or hasn't closed the table properly

      this means that this counter has come out of sync. This doesn't mean that the table is corrupted, but means that you should at least do a check on the table to verify that it's okay.

      The counter works as follows:

      • The first time a table is updated in MySQL, a counter in the header of the index files is incremented.
      • The counter is not changed during further updates.
      • When the last instance of a table is closed (because of a FLUSH or because there isn't room in the table cache) the counter is decremented if the table has been updated at any point.
      • When you repair the table or check the table and it was okay, the counter is reset to 0.
      • To avoid problems with interaction with other processes that may do a check on the table, the counter is not decremented on close if it was 0.

      In other words, the only ways this can go out of sync are:

      • The MyISAM tables are copied without a LOCK and FLUSH TABLES.
      • MySQL has crashed between an update and the final close. (Note that the table may still be okay, as MySQL always issues writes for everything between each statement.)
      • Someone has done a myisamchk --recover or myisamchk --update-stateon a table that was in use by mysqld.
      • Many mysqld servers are using the table and one has done a REPAIR or CHECK of the table while it was in use by another server. In this setup the CHECK is safe to do (even if you will get the warning from other servers), but REPAIR should be avoided as it currently replaces the datafile with a new one, which is not signaled to the other servers.

      7.2 MERGE Tables (3.23.25以上)

      MERGE tables are new in MySQL Version 3.23.25. The code is still in gamma, but should be resonable stable.

      MERGE テーブルは(MRG_MyISAM テーブルとしても知られています) 同一の MyISAM をひとまとめにして使用することができるテーブルです。 そのテーブルの集合体に対しては、SELECT, DELETE, UPDATE のみが可能です。 もし MERGE テーブルを DROP すると、MERGE の 定義だけが破棄されます。

      Note that DELETE FROM merge_table used without a WHERE will only clear the mapping for the table, not delete everything in the mapped tables. (We plan to fix this in 4.1).

      'identical tables' とは、全てのテーブルが同一のフィールド構造とキーの 情報を有するという意味で使用しています。 You can't merge tables in which the columns are packed differently, doesn't have exactly the same columns, or have the keys in different order. However, some of the tables can be compressed with myisampack. 「4.7.4 myisampack, MySQL の圧縮された読み込み専用テーブルジェネレータ」節参照.

      MERGE テーブルを作成すると、.frm テーブル定義ファイルと .MRG テーブルリストファイルが作成されます。 .MRG はインデックスファイル (.MYI ファイル) の リスト(これらは一つとして扱われる)だけが含まれます。 全ての使用されるテーブルは、同じデータベース内に 存在しなければなりません(MERGEテーブルも同様)。

      For the moment, you need to have SELECT, UPDATE, and DELETE privileges on the tables you map to a MERGE table.

      MERGE テーブルは以下の問題の解決を助けます:

      • ログテーブルの管理を安易にします。 For example, you can put data from different months into separate files, compress some of them with myisampack, and then create a MERGE to use these as one.
      • より速く。 You can split a big read-only table based on some criteria and then put the different table part on different disks. A MERGE table on this could be much faster than using the big table. (You can, of course, also use a RAID to get the same kind of benefits.)
      • Do more efficient searches. If you know exactly what you are looking after, you can search in just one of the split tables for some queries and use a MERGE table for others. You can even have many different MERGE tables active, with possible overlapping files.
      • More efficient repairs. It's easier to repair the individual files that are mapped to a MERGE file than trying to repair a really big file.
      • Instant mapping of many files as one. A MERGE table uses the index of the individual tables. It doesn't need to maintain an index of its one. This makes MERGE table collections VERY fast to make or remap. Note that you must specify the key definitions when you create a MERGE table!.
      • If you have a set of tables that you join to a big table on demand or batch, you should instead create a MERGE table on them on demand. This is much faster and will save a lot of disk space.
      • Go around the file-size limit for the operating system.
      • You can create an alias/synonym for a table by just using MERGE over one table. There shouldn't be any really notable performance impacts of doing this (only a couple of indirect calls and memcpy() calls for each read).

      MERGE の欠点は：

      • MERGE には、同一構造の MyISAM テーブルしか使用できません。
      • ver.4.0.3未満では AUTO_INCREMENT フィールドは、INSERT 時に、自動で更新されません。
      • REPLACE は動作しません。
      • MERGE テーブルはより多くのファイル・デスクリプタを使用します。 If you are using a MERGE table that maps over 10 tables and 10 users are using this, you are using 10*10 + 10 file descriptors. (10 datafiles for 10 users and 10 shared index files.)
      • キーの読み込みが遅い。 When you do a read on a key, the MERGE storage engine will need to issue a read on all underlying tables to check which one most closely matches the given key. If you then do a "read-next" then the MERGE storage engine will need to search the read buffers to find the next key. Only when one key buffer is used up, the storage engine will need to read the next key block. This makes MERGE keys much slower on eq_ref searches, but not much slower on ref searches. 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.
      • You can't do DROP TABLE, ALTER TABLE, DELETE FROM table_name without a WHERE clause, REPAIR TABLE, TRUNCATE TABLE, OPTIMIZE TABLE, or ANALYZE TABLE on any of the table that is mapped by a MERGE table that is "open". If you do this, the MERGE table may still refer to the original table and you will get unexpected results. The easiest way to get around this deficiency is to issue the FLUSH TABLES command, ensuring no MERGE tables remain "open".

      MERGE テーブルを作るときは、UNION(list-of-tables) に、 どのテーブルを一つのようにして扱うかを指定する必要があります。 Optionally you can specify with INSERT_METHOD if you want insert for the MERGE table to happen in the first or last table in the UNION list. もし INSERT_METHOD や NO を指定しなかったなら、 MERGE テーブルに対する全ての INSERT コマンドはエラーになります。

      The following example shows you how to use MERGE tables: 

      CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20));
CREATE TABLE t2 (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20));
INSERT INTO t1 (message) VALUES ("Testing"),("table"),("t1");
INSERT INTO t2 (message) VALUES ("Testing"),("table"),("t2");
CREATE TABLE total (a INT AUTO_INCREMENT PRIMARY KEY, message CHAR(20))
             TYPE=MERGE UNION=(t1,t2) INSERT_METHOD=LAST;

      直接、手動で `.MRG' ファイルを作ることも可能です： 

      shell> cd /mysql-data-directory/current-database
shell> ls -1 t1.MYI t2.MYI > total.MRG
shell> mysqladmin flush-tables

      Now you can do things like: 

      mysql> SELECT * FROM total;
+---+---------+
| a | message |
+---+---------+
| 1 | Testing |
| 2 | table   |
| 3 | t1      |
| 1 | Testing |
| 2 | table   |
| 3 | t2      |
+---+---------+

      Note that the a column, though declared as PRIMARY KEY, is not really unique, as MERGE table cannot enforce uniqueness over a set of underlying MyISAM tables.

      To remap a MERGE table you can do one of the following:

      • DROP the table and re-create it
      • Use ALTER TABLE table_name UNION(...)
      • Change the `.MRG' file and issue a FLUSH TABLE on the MERGE table and all underlying tables to force the storage engine to read the new definition file.

      7.2.1 MERGE Table Problems

      The following are the known problems with MERGE tables:

      • A MERGE table cannot maintain UNIQUE constraints over the whole table. When you do INSERT, the data goes into the first or last table (according to INSERT_METHOD=xxx) and this MyISAM table ensures that the data are unique, but it knows nothing about others MyISAM tables.
      • DELETE FROM merge_table used without a WHERE will only clear the mapping for the table, not delete everything in the mapped tables.
      • RENAME TABLE on a table used in an active MERGE table may corrupt the table. This will be fixed in MySQL 4.0.x.
      • Creation of a table of type MERGE doesn't check if the underlying tables are of compatible types. If you use MERGE tables in this fashion, you are very likely to run into strange problems.
      • If you use ALTER TABLE to first add an UNIQUE index to a table used in a MERGE table and then use ALTER TABLE to add a normal index on the MERGE table, the key order will be different for the tables if there was an old non-unique key in the table. This is because ALTER TABLE puts UNIQUE keys before normal keys to be able to detect duplicate keys as early as possible.
      • The range optimiser can't yet use MERGE table efficiently and may sometimes produce non-optimal joins. This will be fixed in MySQL 4.0.x.
      • DROP TABLE on a table that is in use by a MERGE table will not work on Windows because the MERGE storage engine does the table mapping hidden from the upper layer of MySQL. Because Windows doesn't allow you to drop files that are open, you first must flush all MERGE tables (with FLUSH TABLES) or drop the MERGE table before dropping the table. We will fix this at the same time we introduce VIEWs.

      7.3 ISAM Tables

      You can also use the deprecated ISAM table type. This will disappear rather soon (probably in MySQL 5.0) because MyISAM is a better implementation of the same thing. ISAM uses a B-tree index. The index is stored in a file with the `.ISM' extension, and the data is stored in a file with the `.ISD' extension. You can check/repair ISAM tables with the isamchk utility. 「4.4.6.7 Using myisamchk for Crash Recovery」節参照.

      ISAM has the following features/properties:

      • Compressed and fixed-length keys
      • Fixed and dynamic record length
      • 16 keys with 16 key parts/key
      • Max key length 256 (default)
      • Data is stored in machine format; this is fast, but is machine/OS dependent.

      Most of the things true for MyISAM tables are also true for ISAM tables. 「7.1 MyISAM テーブル (3.23.0以上)」節参照. The major differences compared to MyISAM tables are:

      • ISAM tables are not binary portable across OS/Platforms.
      • Can't handle tables > 4G.
      • Only support prefix compression on strings.
      • Smaller key limits.
      • Dynamic tables get more fragmented.
      • Tables are compressed with pack_isam rather than with myisampack.

      If you want to convert an ISAM table to a MyISAM table so that you can use utilities such as mysqlcheck, use an ALTER TABLE statement: 

      mysql> ALTER TABLE tbl_name TYPE = MYISAM;

      The embedded MySQL versions doesn't support ISAM tables.

      7.4 HEAP Tables (3.23.0以上)

      HEAP テーブルは hashed index を使用し、メモリ内に保存されます。 これはとても速くなりますが、もし MySQL がクラッシュする時にはその内容が 全て失われます。 HEAP はテンポラリのテーブルとしてはとても便利です！

      MySQL 内部 HEAP テーブルは、100% ダイナッミック・ハッシングを 使用しています（オーバーフローエリア無しに）。 There is no extra space needed for free lists. HEAP tables also don't have problems with delete + inserts, which normally is common with hashed tables: 

      mysql> CREATE TABLE test TYPE=HEAP SELECT ip,SUM(downloads) AS down
    ->                   FROM log_table GROUP BY ip;
mysql> SELECT COUNT(ip),AVG(down) FROM test;
mysql> DROP TABLE test;

      Here are some things you should consider when you use HEAP tables:

      • You should always use specify MAX_ROWS in the CREATE statement to ensure that you accidentally do not use all memory.
      • Indexes will only be used with = and <=> (but are VERY fast).
      • HEAP tables can only use whole keys to search for a row; compare this to MyISAM tables where any prefix of the key can be used to find rows.
      • HEAP テーブルは 固定長のレコードです。
      • HEAP は BLOB/TEXT 型をサポートしません。
      • HEAP は AUTO_INCREMENT フィールドをサポートしません。
      • MySQL 4.0.2 以前では、HEAP は NULL が許されているフィールドにインデックスを張れません。
      • HEAP テーブルに、一意ではないキーを持たせることが可能です。 (this isn't common for hashed tables).
      • HEAP テーブルは全てのクライアントに共有されます (他のテーブルと同じように)
      • You can't search for the next entry in order (that is, to use the index to do an ORDER BY).
      • Data for HEAP tables are allocated in small blocks. The tables are 100% dynamic (on inserting). No overflow areas and no extra key space are needed. Deleted rows are put in a linked list and are reused when you insert new data into the table.
      • You need enough extra memory for all HEAP tables that you want to use at the same time.
      • メモリを解放するには, DELETE FROM heap_table, TRUNCATE heap_table , DROP TABLE heap_table を実行すべきです.
      • MySQL cannot find out approximately how many rows there are between two values (this is used by the range optimiser to decide which index to use). This may affect some queries if you change a MyISAM table to a HEAP table.
      • To ensure that you accidentally don't do anything foolish, you can't create HEAP tables bigger than max_heap_table_size.

      HEAP テーブル内の１レコードに必要とされるメモリは： 

      SUM_OVER_ALL_KEYS(max_length_of_key + sizeof(char*) * 2)
+ ALIGN(length_of_row+1, sizeof(char*))

      sizeof(char*) is 4 on 32-bit machines and 8 on 64-bit machines.

      7.5 InnoDB テーブル (3.23.6以上)

      7.5.1 InnoDB テーブル 概要

      InnoDB provides MySQL with a transaction-safe (ACID compliant) storage engine with commit, rollback, and crash recovery capabilities. InnoDB does locking on row level and also provides an Oracle-style consistent non-locking read in SELECTs. These features increase multiuser concurrency and performance. There is no need for lock escalation in InnoDB, because row level locks in InnoDB fit in very small space. InnoDB テーブルは MySQL のテーブルタイプの中では初めて、 FOREIGN KEY 制約 をサポートします。

      InnoDB has been designed for maximum performance when processing large data volumes. Its CPU efficiency is probably not matched by any other disk-based relational database engine.

      Technically, InnoDB is a complete database backend placed under MySQL. InnoDB has its own buffer pool for caching data and indexes in main memory. InnoDB stores its tables and indexes in a tablespace, which may consist of several files. This is different from, for example, MyISAM tables where each table is stored as a separate file. InnoDB tables can be of any size also on those operating systems where file-size is limited to 2 GB.

      最新の InnoDB についての情報は http://www.innodb.com/. The most up-to-date version of the InnoDB manual is always placed there, and you can also order commercial licenses and support for InnoDB.

      InnoDB is currently (October 2001) used in production at several large database sites requiring high performance. The famous Internet news site Slashdot.org runs on InnoDB. Mytrix, Inc. stores over 1 TB of data in InnoDB, and another site handles an average load of 800 inserts/updates per second in InnoDB.

      InnoDB は バージョン 3.23.34a から、 MySQL のソース配布に含まれるようになり、 そして、MySQL-max バイナリで有効になりました。 For Windows the -Max binaries are contained in the standard distribution.

      If you have downloaded a binary version of MySQL that includes support for InnoDB, simply follow the instructions of the MySQL manual for installing a binary version of MySQL. If you already have MySQL-3.23 installed, then the simplest way to install MySQL -Max is to replace the server executable `mysqld' with the corresponding executable in the -Max distribution. MySQL and MySQL -Max differ only in the server executable. 「2.2.10 Installing a MySQL Binary Distribution」節参照.

      InnoDB をサポートするように MySQL をコンパイルするには、MySQL-3.23.34a 以上をダウンロードし、 --with-innodb オプションで MySQL を configure します。 「2.3 MySQL ソースディストリビューションのインストール」節参照. 

      cd /path/to/source/of/mysql-3.23.37
./configure --with-innodb

      InnoDB を使用するためには、`my.cnf' か `my.ini' ファイルに InnoDB 起動オプションを指定しなくてはなりません。 必要最低限の変更は、 [mysqld] セクションに以下のラインを加えることです 

      innodb_data_file_path=ibdata:30M

      but to get good performance it is best that you specify options as recommended. 「7.5.2 InnoDB 起動オプション」節参照.

      InnoDB is distributed under the GNU GPL License Version 2 (of June 1991). In the source distribution of MySQL, InnoDB appears as a subdirectory.

      7.5.2 InnoDB 起動オプション

      MySQL-3.23.37 から、オプションの接頭語が innobase_... から innodb_... に変わりました！

      MySQL-Max-3.23 で InnoDB テーブルを使用するためには、 設定ファイル `my.cnf' (Windows では `my.ini') の [mysqld] セクションに設定をしなくてはなりません。 「4.1.2 `my.cnf' オプションファイル」節参照.

      + At the minimum, in 3.23 you must specify innodb_data_file_path + where you specify the names and the sizes of datafiles. If you do + not mention innodb_data_home_dir in `my.cnf' the default + is to create these files to the datadir of MySQL. + If you specify innodb_data_home_dir as an empty string, + then you can give absolute paths to your data files in + innodb_data_file_path. In MySQL-4.0 you do not need to specify even innodb_data_file_path: the default for it is to create + an auto-extending 10 MB file `ibdata1' to the datadir of MySQL. (In MySQL-4.0.0 and 4.0.1 the datafile is 64 MB and not auto-extending.) + If you don't want to use InnoDB tables, you can add the + skip-innodb option to your MySQL option file. +

      ver.3.23 では、InnoDB を使用するために唯一必要なパラメタは データファイルの大きさを指定する innodb_data_file_path です。 If you do not mention innodb_data_home_dir in `my.cnf' the default is to create these files to the datadir of MySQL. If you specify innodb_data_home_dir as an empty string, then you can give absolute paths to your data files in innodb_data_file_path. In MySQL-4.0 you do not need to specify even innodb_data_file_path: the default for it is to create an auto-extending 10 MB file `ibdata1' to the datadir of MySQL. (In MySQL-4.0.0 and 4.0.1 the datafile is 64 MB and not auto-extending.)

      If you don't want to use InnoDB tables, you can add the skip-innodb option to your MySQL option file.

      他のオプションはよりよいパフォーマンスを得たい場合に設定します。

      Starting from versions 3.23.50 and 4.0.2 InnoDB allows the last datafile on the innodb_data_file_path line to be specified as auto-extending. The syntax for innodb_data_file_path is then the following: 

      pathtodatafile:sizespecification;pathtodatafile:sizespecification;...
...  ;pathtodatafile:sizespecification[:autoextend[:max:sizespecification]]

      If you specify the last datafile with the autoextend option, InnoDB will extend the last datafile if it runs out of free space in the tablespace. The increment is 8 MB at a time. An example: 

      innodb_data_home_dir =
innodb_data_file_path = /ibdata/ibdata1:100M:autoextend

      instructs InnoDB to create just a single datafile whose initial size is 100 MB and which is extended in 8 MB blocks when space runs out. If the disk becomes full you may want to add another data file to another disk, for example. Then you have to look the size of `ibdata1', round the size downward to the closest multiple of 1024 * 1024 bytes (= 1 MB), and specify the rounded size of `ibdata1' explicitly in innodb_data_file_path. After that you can add another datafile: 

      innodb_data_home_dir =
innodb_data_file_path = /ibdata/ibdata1:988M;/disk2/ibdata2:50M:autoextend

      Be cautious on filesystems where the maximum file-size is 2 GB! InnoDB is not aware of the OS maximum file-size. On those filesystems you might want to specify the max size for the datafile: 

      innodb_data_home_dir =
innodb_data_file_path = /ibdata/ibdata1:100M:autoextend:max:2000M

      A simple `my.cnf' example. Suppose you have a computer with 128 MB RAM and one hard disk. Below is an example of possible configuration parameters in `my.cnf' or `my.ini' for InnoDB. We assume you are running MySQL-Max-3.23.50 or later, or MySQL-4.0.2 or later. This example suits most users, both on Unix and Windows, who do not want to distribute InnoDB datafiles and log files on several disks. This creates an auto-extending data file `ibdata1' and two InnoDB log files `ib_logfile0' and `ib_logfile1' to the datadir of MySQL (typically `/mysql/data'). Also the small archived InnoDB log file `ib_arch_log_0000000000' ends up in the datadir. 

      [mysqld]
# You can write your other MySQL server options here
# ...
#                                  Data file(s) must be able to
#                                  hold your data and indexes.
#                                  Make sure you have enough
#                                  free disk space.
innodb_data_file_path = ibdata1:10M:autoextend
#                                  Set buffer pool size to
#                                  50 - 80 % of your computer's
#                                  memory
set-variable = innodb_buffer_pool_size=70M
set-variable = innodb_additional_mem_pool_size=10M
#                                  Set the log file size to about
#                                  25 % of the buffer pool size
set-variable = innodb_log_file_size=20M
set-variable = innodb_log_buffer_size=8M
#                                  Set ..flush_log_at_trx_commit
#                                  to 0 if you can afford losing
#                                  some last transactions 
innodb_flush_log_at_trx_commit=1

      Check that the MySQL server has the rights to create files in datadir.

      Note that datafiles must be < 2G in some file systems! The combined size of the log files must be < 4G. The combined size of datafiles must be >= 10 MB.

      When you for the first time create an InnoDB database, it is best that you start the MySQL server from the command prompt. Then InnoDB will print the information about the database creation to the screen, and you see what is happening. See below next section what the printout should look like. For example, in Windows you can start `mysqld-max.exe' with: 

      your-path-to-mysqld>mysqld-max --console

      Where to put `my.cnf' or `my.ini' in Windows? The rules for Windows are the following:

      • Only one of `my.cnf' or `my.ini' should be created.
      • The `my.cnf' file should be placed in the root directory of the drive `C:'.
      • The `my.ini' file should be placed in the WINDIR directory, e.g, `C:\WINDOWS' or `C:\WINNT'. You can use the SET command of MS-DOS to print the value of WINDIR.
      • If your PC uses a boot loader where the `C:' drive is not the boot drive, then your only option is to use the `my.ini' file.

      Where to specify options in Unix? On Unix `mysqld' reads options from the following files, if they exist, in the following order:

      • `/etc/my.cnf' Global options.
      • `COMPILATION_DATADIR/my.cnf' Server-specific options.
      • `defaults-extra-file' The file specified with --defaults-extra-file=....
      • `~/.my.cnf' User-specific options.

      `COMPILATION_DATADIR' is the MySQL data directory which was specified as a ./configure option when `mysqld' was compiled (typically `/usr/local/mysql/data' for a binary installation or `/usr/local/var' for a source installation).

      If you are not sure from where `mysqld' reads its `my.cnf' or `my.ini', you can give the path as the first command-line option to the server: mysqld --defaults-file=your_path_to_my_cnf.

      InnoDB forms the directory path to a datafile by textually catenating innodb_data_home_dir to a datafile name or path in innodb_data_file_path, adding a possible slash or backslash in between if needed. If the keyword innodb_data_home_dir is not mentioned in `my.cnf' at all, the default for it is the 'dot' directory `./' which means the datadir of MySQL.

      An advanced `my.cnf' example. あなたの機械が Linux で 512M の RAM と 20GB のハードディスクだと仮定します。 (ディレクトリパスは `/', `/dr2', `/dr3') 以下はその場合の `my.cnf' の InnoDB パラメターの例です.

      Note that InnoDB does not create directories: you have to create them yourself. Use the Unix or MS-DOS mkdir command to create the data and log group home directories. 

      [mysqld]
# You can write your other MySQL server options here
# ...
innodb_data_home_dir =
#                                  Data files must be able to
#                                  hold your data and indexes
innodb_data_file_path = /ibdata/ibdata1:2000M;/dr2/ibdata/ibdata2:2000M:autoextend
#                                  Set buffer pool size to
#                                  50 - 80 % of your computer's
#                                  memory, but make sure on Linux
#                                  x86 total memory usage is
#                                  < 2 GB
set-variable = innodb_buffer_pool_size=1G
set-variable = innodb_additional_mem_pool_size=20M
innodb_log_group_home_dir = /dr3/iblogs
#                                  .._log_arch_dir must be the same
#                                  as .._log_group_home_dir
innodb_log_arch_dir = /dr3/iblogs
set-variable = innodb_log_files_in_group=3
#                                  Set the log file size to about
#                                  15 % of the buffer pool size
set-variable = innodb_log_file_size=150M
set-variable = innodb_log_buffer_size=8M
#                                  Set ..flush_log_at_trx_commit to
#                                  0 if you can afford losing
#                                  some last transactions 
innodb_flush_log_at_trx_commit=1
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50
#innodb_flush_method=fdatasync
#innodb_fast_shutdown=1
#set-variable = innodb_thread_concurrency=5

      Note that we have placed the two datafiles on different disks. InnoDB will fill the tablespace formed by the datafiles from bottom up. In some cases it will improve the performance of the database if all data is not placed on the same physical disk. Putting log files on a different disk from data is very often beneficial for performance. You can also use raw disk partitions (raw devices) as datafiles. In some Unixes they speed up I/O. See the manual section on InnoDB file space management about how to specify them in `my.cnf'.

      Warning: on Linux x86 you must be careful you do not set memory usage too high. glibc will allow the process heap to grow over thread stacks, which will crash your server. It is a risk if the value of 

      innodb_buffer_pool_size + key_buffer +
max_connections * (sort_buffer + read_buffer_size) + max_connections * 2 MB

      is close to 2 GB or exceeds 2 GB. Each thread will use a stack (often 2 MB, but in MySQL AB binaries only 256 kB) and in the worst case also sort_buffer + read_buffer_size additional memory.

      How to tune other `mysqld' server parameters? Typical values which suit most users are: 

      skip-locking
set-variable = max_connections=200
set-variable = read_buffer_size=1M
set-variable = sort_buffer=1M
#                                  Set key_buffer to 5 - 50%
#                                  of your RAM depending on how
#                                  much you use MyISAM tables, but
#                                  keep key_buffer + InnoDB
#                                  buffer pool size < 80% of
#                                  your RAM
set-variable = key_buffer=...

      Note that some parameters are given using the numeric `my.cnf' parameter format: set-variable = innodb... = 123, others (string and boolean parameters) with another format: innodb_... = ... .

      The meanings of the configuration parameters are the following:

      Option Description
      innodb_data_home_dir 全ての InnoDB データファイルの、共通トップディレクトリのパス。 If you do not mentioned this option in `my.cnf' the default is the datadir of MySQL. You can specify this also as an empty string, in which case you can use absolute file paths in innodb_data_file_path.
      innodb_data_file_path 単一のデータファイル(individual data files)のパスとそのサイズ。 (訳注： innodb は保存すべきデータをいくつかのファイルに分割して書き込みます。 この 'individual data files' は、その、実際にデータを保存している 個々のファイルの事を指しています。) それぞれのデータファイルへのフルパスは、innodb_data_home_dir で指定された パスと連結されることで求められます。 ファイルサイズは メガバイト で与えられ、上記のように 'M' がサイズの後にきます。 ファイルサイズは 4000M より大きくしてはいけません。 ほとんどのオペレーティングシステムでは 2000M より大きなファイルを扱えません。 InnoDB は 'G' の省略形も認識します。 1G は 1024M になります。 バージョン 3.23.44 からは、オペーレーティングシステムが large ファイルを扱えるのであれば、4GB 以上の指定が可能です。 いくつかのオペレーティングシステムは一つのファイルは 2GB 未満の 制約があります。 データファイルのサイズの合計は、少なくとも、10MB 以上必要です。
      innodb_mirrored_log_groups データベースのために維持しておくログのグループのコピーの数。 現在、これは 1 しかセットできません。
      innodb_log_group_home_dir InnoDB ログファイルのディレクトリのパス。
      innodb_log_files_in_group log group 内の、ログファイルの数。 InnoDB はログファイルを、ローテートするやり方で書きます。 3 が推奨値です。
      innodb_log_file_size log group 内の、各ログファイルの大きさ(Mega bytes)。 Sensible values range from 1M to 1/nth of the size of the buffer pool specified below, where n is the number of log files in the group. The bigger the value, the less checkpoint flush activity is needed in the buffer pool, saving disk I/O. But bigger log files also mean that recovery will be slower in case of a crash. The combined size of log files must be < 4 GB on 32-bit computers.
      innodb_log_buffer_size InnoDB が、disk上のログファイルにログを書き出すために使用する、 バッファのサイズ。 Sensible values range from 1M to 8M. A big log buffer allows large transactions to run without a need to write the log to disk until the transaction commit. Thus, if you have big transactions, making the log buffer big will save disk I/O.
      innodb_flush_log_at_trx_commit Normally this is set to 1, meaning that at a transaction commit the log is flushed to disk, and the modifications made by the transaction become permanent, and survive a database crash. If you are willing to compromise this safety, and you are running small transactions, you may set this to 0 to reduce disk I/O to the logs.
      innodb_log_arch_dir The directory where fully written log files would be archived if we used log archiving. ＊現在のところ、これには、 innodb_log_group_home_dir と同じ値をセットしなくてはなりません。＊
      innodb_log_archive This value should currently be set to 0. As recovery from a backup is done by MySQL using its own log files, there is currently no need to archive InnoDB log files.
      innodb_buffer_pool_size InnoDB がデータやテーブルのインデックスををキャッシュするために使用する メモリのサイズ。 大きな値をセットすると、テーブルのデータへのアクセスに必要なディスク i/o が少なくなります。 データベースサーバ専用のマシンでは、このパラメタを物理メモリの 80% まで セットしてもかまいません。 物理メモリの競合がオペレーティングシステムのページングの原因に なるかもしれないので、あまりに大きすぎる値は与えないように。
      innodb_additional_mem_pool_size Size of a memory pool InnoDB uses to store data dictionary information and other internal data structures. A sensible value for this might be 2M, but the more tables you have in your application the more you will need to allocate here. If InnoDB runs out of memory in this pool, it will start to allocate memory from the operating system, and write warning messages to the MySQL error log.
      innodb_file_io_threads Number of file I/O threads in InnoDB. Normally, this should be 4, but on Windows disk I/O may benefit from a larger number.
      innodb_lock_wait_timeout Timeout in seconds an InnoDB transaction may wait for a lock before being rolled back. InnoDB は自動的にトランザクションのデッド・ロックがテーブルに起きた事 を感知し、そのトランザクションをロール・バックします。 If you use LOCK TABLES command, or other transaction-safe storage engines than InnoDB in the same transaction, then a deadlock may arise which InnoDB cannot notice. In cases like this the timeout is useful to resolve the situation.
      innodb_flush_method (3.23.40 以上からの機能.) The default value for this is fdatasync. Another option is O_DSYNC.

      7.5.3 InnoDB テーブルの保存先の作成

      あなたが MySQL を既にインストールしており、`my.cnf' には InnoDB configuration パラメタが記述されていると仮定します。 MySQL を起動する前に、 あなたが指定している InnoDB データファイルとログファイルを保存する ディレクトリが存在するか、 そして、それらのディレクトリのパーミッションが正しいかを 確認するべきです。 InnoDB はディレクトリを自動では作成できません。ファイルのみです。 データとログファイルを保存するために十分なディスクの空きがあるかも チェックしてください。

      MySQL を起動すると、InnoDB は data file と log file を作成します。 InnoDB は以下のようなメッセージを出力します： 

      ~/mysqlm/sql > mysqld
InnoDB: The first specified datafile /home/heikki/data/ibdata1
did not exist:
InnoDB: a new database to be created!
InnoDB: Setting file /home/heikki/data/ibdata1 size to 134217728
InnoDB: Database physically writes the file full: wait...
InnoDB: datafile /home/heikki/data/ibdata2 did not exist:
new to be created
InnoDB: Setting file /home/heikki/data/ibdata2 size to 262144000
InnoDB: Database physically writes the file full: wait...
InnoDB: Log file /home/heikki/data/logs/ib_logfile0 did not exist:
new to be created
InnoDB: Setting log file /home/heikki/data/logs/ib_logfile0 size to 5242880
InnoDB: Log file /home/heikki/data/logs/ib_logfile1 did not exist:
new to be created
InnoDB: Setting log file /home/heikki/data/logs/ib_logfile1 size to 5242880
InnoDB: Log file /home/heikki/data/logs/ib_logfile2 did not exist:
new to be created
InnoDB: Setting log file /home/heikki/data/logs/ib_logfile2 size to 5242880
InnoDB: Started
mysqld: ready for connections

      新しく InnoDB データベースが、これで作成されました。 mysql のような MySQL クライアントを使用して、MySQL サーバに 接続することが可能です。 `mysqladmin shutdown' で MySQL をシャットダウンしたときには、 InnoDB は以下のようなメッセージを出力します： 

      010321 18:33:34  mysqld: Normal shutdown
010321 18:33:34  mysqld: Shutdown Complete
InnoDB: Starting shutdown...
InnoDB: Shutdown completed

      You can now look at the datafiles and logs directories and you will see the files created. ログディレクトリには、`ib_arch_log_0000000000' という名前の、 小さなファイルが含まれているはずです。 That file resulted from the database creation, after which InnoDB switched off log archiving. MySQL が次回に起動したとき、出力は次のようになります： 

      ~/mysqlm/sql > mysqld
InnoDB: Started
mysqld: ready for connections

      7.5.3.1 InnoDB データベース作成に失敗した場合

      If InnoDB prints an operating system error in a file operation, usually the problem is one of the following:

      • You did not create InnoDB data or log directories.
      • `mysqld' does not have the rights to create files in those directories.
      • `mysqld' does not read the right `my.cnf' or `my.ini' file, and consequently does not see the options you specified.
      • The disk is full or a disk quota is exceeded.
      • You have created a subdirectory whose name is equal to a datafile you specified.
      • There is a syntax error in innodb_data_home_dir or innodb_data_file_path.

      もし InnoDB database 作成時になにか問題が起きたならば、 InnoDB によって作成された全てのファイルを削除すべきです。 This means all datafiles, all log files, the small archived log file, and in the case you already did create some InnoDB tables, delete also the corresponding `.frm' files for these tables from the MySQL database directories. Then you can try the InnoDB database creation again.

      7.5.4 InnoDB テーブルの作成

      mysql test として MySQL クライアントを実行したとします。 InnoDB 形式のテーブルを作成するためには、あなたは SQL コマンドの テーブル作成文に、TYPE = InnoDB を指定しなくてはなりません。 

      CREATE TABLE CUSTOMER (A INT, B CHAR (20), INDEX (A)) TYPE = InnoDB;

      この SQL コマンドは、`my.cnf' で定義された InnoDB のテーブル空間に存在する データファイル内に、一つのテーブルと、一つのインデックス (A フィールドに張られた)を作成します。 MySQL は `CUSTOMER.frm' ファイルを MuSQL データベースディレクトリ `test' に作成します。 内部では、InnoDB は、InnoDB 自身のデータディレクトリをもち、 そこに 'test/CUSTOMER' テーブルのエントリを追加します。 よって、MySQL 内の違うデータベース内に、同じ CUSTOMER という 名前を持つテーブルを作成することが可能で、もちろんこの名前は、 InnoDB 内でも他とは衝突しません。

      MySQL の table status コマンドを使用して、TYPE = InnoDB で作成した テーブル全てに対して、InnoDB のテーブル空間の未使用量が どれくらいあるかを出すことができます。 テーブル空間の未使用領域の総量は、SHOW で出力された テーブルの comment セクションに現われます。 例： 

      SHOW TABLE STATUS FROM test LIKE 'CUSTOMER'

      SHOW を使用して得られた InnoDB のテーブルの情報は概算です； それらは SQL オプティマイゼイションで使用されます。 ただし、テーブルとインデックスに割り当てられているサイズ(bytes)は正確です。

      7.5.4.1 MyISAM テーブルを InnoDB テーブルに変換

      InnoDB does not have a special optimization for separate index creation. Therefore it does not pay to export and import the table and create indexes afterwards. 素早くテーブルを InnoDB に変換する方法は、 InnoDB に直接 insert することです。 テーブルの変換には、ALTER TABLE ... TYPE=INNODB を使用するか、 空の InnoDB テーブルを作成してデータを INSERT INTO ... SELECT * FROM ... でインサートします。

      insert 時においては、大きなテーブルの場合は、いくつかにテーブルを 分割して行うとよいでしょう： 

      INSERT INTO newtable SELECT * FROM oldtable
   WHERE yourkey > something AND yourkey <= somethingelse;

      全てのデータが挿入できたら、テーブル名を変更します。

      大きなテーブルを変換している間は、InnoDB のバッファプールサイズを 大きくすることで、disk I/O を軽減できます。 ただし、物理メモリの 80% 以上をバッファに割り当てないように。 InnoDB log ファイルのサイズもログのバッファも大きく取るべきです。

      確実に、テーブル空間より大きくならないようにします； InnoDB テーブルは MyISAM テーブルよりも多くの disk を使用します。 もし ALTER TABLE が取っている領域よりも超えた場合には、 ロール・バックが開始されます。 これは ディスク・バウンドのために (大きなファイルならば) 数時間かかるかもしれません。 インサートする場合には、InnoDB は インサート・バッファ を使用します。 これはセカンダリ・インデックス・レコードをインデックスに一度にマージ させるために使用されます。 このため多くの disk I/O が節約されます。 ロール・バックにおいては、インサートで使用されるようなメカニズムは無く、 ロール・バックは、インサートの 約30倍、時間がかかります。

      このような手に負えないロール・バックのばあい、 もし、価値のあるデータがあなたの InnoDB データベース内に一つもなければ、 データベースのプロセスをキルして全ての InnoDB データファイルとログファイルを 消去し、全ての InnoDB テーブルの `.frm' ファイルを消し、 そしてもう一度試みる方が良いでしょう。 とてつもなく多くの disk I/O が完了するのを待つよりも。

      7.5.4.2 外部キー制約 (Foreign Key Constraints) (3.23.44以上)

      InnoDB バージョン 3.23.43b 以上では foreign key constraints を持ちます. InnoDB is the first MySQL table type which allows you to define foreign key constraints to guard the integrity of your data.

      The syntax of a foreign key constraint definition in InnoDB: 

      [CONSTRAINT symbol] FOREIGN KEY (index_col_name, ...)
                  REFERENCES table_name (index_col_name, ...)
                  [ON DELETE {CASCADE | SET NULL | NO ACTION
                              | RESTRICT}]
                  [ON UPDATE {CASCADE | SET NULL | NO ACTION
                              | RESTRICT}]

      Both tables have to be InnoDB type and there must be an index where the foreign key and the referenced key are listed as the FIRST columns. InnoDB does not auto-create indexes on foreign keys or referenced keys: you have to create them explicitly.

      Corresponding columns in the foreign key and the referenced key must have similar internal data types inside InnoDB so that they can be compared without a type conversion. The size and the signedness of integer types has to be the same. The length of string types need not be the same. If you specify a SET NULL action, make sure you have not declared the columns in the child table NOT NULL.

      If MySQL gives the error number 1005 from a CREATE TABLE statement, and the error message string refers to errno 150, then the table creation failed because a foreign key constraint was not correctly formed. Similarly, if an ALTER TABLE fails and it refers to errno 150, that means a foreign key definition would be incorrectly formed for the altered table.

      Starting from version 3.23.50 you can also associate the ON DELETE CASCADE or ON DELETE SET NULL clause with the foreign key constraint. Starting from version 4.0.8 you can use also similar ON UPDATE actions.

      If ON DELETE CASCADE is specified, and a row in the parent table is deleted, then InnoDB automatically deletes also all those rows in the child table whose foreign key values are equal to the referenced key value in the parent row. If ON DELETE SET NULL is specified, the child rows are automatically updated so that the columns in the foreign key are set to the SQL NULL value.

      Starting from version 3.23.50, InnoDB does not check foreign key constraints on those foreign key or referenced key values which contain a NULL column.

      Starting from version 3.23.50 the InnoDB parser allows you to use backquotes (`) around table and column names in the FOREIGN KEY ... REFERENCES ... clause but the InnoDB parser is not yet aware of the option lower_case_table_names you can specify in `my.cnf'.

      例: 

      CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id)) TYPE=INNODB;
CREATE TABLE child(id INT, parent_id INT, INDEX par_ind (parent_id),
             FOREIGN KEY (parent_id) REFERENCES parent(id)
             ON DELETE SET NULL
) TYPE=INNODB;

      (訳注： 両方のテーブルとも、InnoDB でなくてはなりません。 さらに foreign key と the referenced key に指定される項目は、 インデックス中の定義の中では、最初の項目として、 指定されていなければなりません。 上記の例では、FOREIGN KEY で指定されている V, U は、 インデックスの最初の項目に指定されています。)

      Starting from version 3.23.50 InnoDB allows you to add a new foreign key constraint to a table through 

      ALTER TABLE yourtablename
ADD [CONSTRAINT symbol] FOREIGN KEY (...) REFERENCES anothertablename(...)
[on_delete_and_on_update_actions]

      Remember to create the required indexes first, though. In InnoDB versions < 3.23.50 ALTER TABLE or CREATE INDEX should not be used in connection with tables which have foreign key constraints or which are referenced in foreign key constraints: Any ALTER TABLE removes all foreign key constrainst defined for the table. You should not use ALTER TABLE to the referenced table either, but use DROP TABLE and CREATE TABLE to modify the schema. When MySQL does an ALTER TABLE it may internally use RENAME TABLE, and that will confuse the foreign key costraints which refer to the table. A CREATE INDEX statement is in MySQL processed as an ALTER TABLE, and these restrictions apply also to it.

      When doing foreign key checks InnoDB sets shared row level locks on child or parent records it has to look at. InnoDB checks foreign key constraints immediately: the check is not deferred to transaction commit.

      InnoDB allows you to drop any table even though that would break the foreign key constraints which reference the table. When you drop a table the constraints which were defined in its create statement are also dropped.

      If you re-create a table which was dropped, it has to have a definition which conforms to the foreign key constraints referencing it. It must have the right column names and types, and it must have indexes on the referenced keys, as stated above. If these are not satisfied, MySQL returns error number 1005 and refers to errno 150 in the error message string.

      Starting from version 3.23.50 InnoDB returns the foreign key definitions of a table when you call 

      SHOW CREATE TABLE yourtablename

      Then also `mysqldump' produces correct definitions of tables to the dump file, and does not forget about the foreign keys.

      You can also list the foreign key constraints for a table T with 

      SHOW TABLE STATUS FROM yourdatabasename LIKE 'T'

      The foreign key constraints are listed in the table comment of the output.

      7.5.5 InnoDB データとログの追加と削除

      バージョン 3.23.50以上の3.23, 4.0.2以上では InnoDB の最後のデータファイルを autoextend に指定することが可能です。 それ未満のバージョンでは、データファイルを追加することで テーブルの空間を大きくすることが可能です。 テーブルの空間を大きくするためには、新しいデータファイルを追加します。 これを行なうには、MySQL サーバーを一度シャットダウンし、 `my.cnf' ファイルを編集して新しいデータファイルを innodb_data_file_path に追加し、MySQL サーバを起動します。

      今のところ、データファイルを InnoDB から削除することはできません。 データベースのサイズを小さくするには、 一度 mysqldump でテーブルをダンプし、 新しくデータベースを作成し、ダンプしたテーブルを取り込みます。

      もし InnoDB のログファイルのサイズを変更したいならば、 MySQL サーバを停止しなくてはなりません(エラー無しで確実に止まるようにしてください)。 なにかシャットダウン時に問題があった場合には、 古いログファイルを安全な場所にコピーし、 データベースの修復をしましょう。 そして、古いログファイルを log ファイルのディレクトリから消去し、 `my.cnf' ファイルを編集した後、MySQL サーバを起動します。 InnoDB は 新しいログファイルを作成したことを告げるでしょう。

      7.5.6 InnoDB データベースのバックアップと修復

      The key to safe database management is taking regular backups.

      InnoDB Hot Backup is an online backup tool you can use to backup your InnoDB database while it is running. InnoDB Hot Backup does not require you to shut down your database and it does not set any locks or disturb your normal database processing. InnoDB Hot Backup is a non-free additional tool which is not included in the standard MySQL distribution. See the InnoDB Hot Backup homepage http://www.innodb.com/hotbackup.html for detailed information and screenshots.

      If you are able to shut down your MySQL server, then to take a 'binary' backup of your database you have to do the following:

      • MySQL を停止。エラー無しで確実に止まるように。
      • 全てのデータファイルを安全な場所にコピー。
      • 全ての InnoDB ログファイルを安全な場所にコピー。
      • `my.cnf' 設定ファイルを安全な場所にコピー。
      • InnoDB テーブルの `.frm' ファイルを安全な場所にコピー。

      上のバイナリバックアップに加えて、`mysqldump' で通常のテーブルの ダンプも取るべきです。 この理由は、バイナリファイルはあなたの知らないところで おかしくなっているかもしれないからです。 テキストファイルのダンプされたテーブルは人間が読むことができ、 そしてバイナリファイルよりもずっと簡素です。 ダンプされたファイルからテーブルのおかしくなった箇所を見つけるのは容易で、 そして、致命的なデータの不正を少なくするチャンスでもあります。

      データベースのバイナリバックアップと同時に、ダンプを取ることは、 よい考えです。 全テーブルを現在の状況と矛盾無くダンプするためには、全てのクライアントを データベースからシャット・アウトするべきです。 Then you can take the binary backup, and you will then have a consistent snapshot of your database in two formats.

      To be able to recover your InnoDB database to the present from the binary backup described above, you have to run your MySQL database with the general logging and log archiving of MySQL switched on. Here by the general logging we mean the logging mechanism of the MySQL server which is independent of InnoDB logs.

      MySQL サーバプロセスのクラッシュからのリカバリを行なうには、 MySQL をリスタートすることがただ一つの方法です。 InnoDB は自動で ログ をチェックし、データベースの roll-forward を 行ないます。 InnoDB は、クラッシュ時にコッミトされていないトランザクションを 自動的にロールバックします。 リカバリの間、InnoDB は以下のような出力をします： 

      ~/mysqlm/sql > mysqld
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 13674004
InnoDB: Doing recovery: scanned up to log sequence number 0 13739520
InnoDB: Doing recovery: scanned up to log sequence number 0 13805056
InnoDB: Doing recovery: scanned up to log sequence number 0 13870592
InnoDB: Doing recovery: scanned up to log sequence number 0 13936128
...
InnoDB: Doing recovery: scanned up to log sequence number 0 20555264
InnoDB: Doing recovery: scanned up to log sequence number 0 20620800
InnoDB: Doing recovery: scanned up to log sequence number 0 20664692
InnoDB: 1 uncommitted transaction(s) which must be rolled back
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx no 16745
InnoDB: Rolling back of trx no 16745 completed
InnoDB: Rollback of uncommitted transactions completed
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Apply batch completed
InnoDB: Started
mysqld: ready for connections

      If your database gets corrupted or your disk fails, you have to do the recovery from a backup. In the case of corruption, you should first find a backup which is not corrupted. From a backup do the recovery from the general log files of MySQL according to instructions in the MySQL manual.

      7.5.6.1 Checkpoints

      InnoDB は fuzzy checkpoint と呼ばれる チェックポイントのメカニズムを持っています。 InnoDB will flush modified database pages from the buffer pool in small batches, there is no need to flush the buffer pool in one single batch, which would in practice stop processing of user SQL statements for a while.

      クラッシュ・リカバリ時には、InnoDB はログファイルに書かれた チェックポイント・ラベルを見ます。 データベースのディスク・イメージ上にそのラベルが反映させられる前に、 それはデータベースの全ての変更を知っています。 It knows that all modifications to the database before the label are already present on the disk image of the database. Then InnoDB scans the log files forward from the place of the checkpoint applying the logged modifications to the database.

      InnoDB はログファイルを循環して使用します。 全てのコミットされた変更分(変更だから当然バッファプール内のデータベースのページとディスク上のイメージが違う)は、InnoDB がリカバリを実行しなければならない時に、ログファイルに存在しなければなりません。(でなければリカバリを行なうことができません。) これは、InnoDB がログファイルを循環的に再利用しようとした時に、ディスク上のデータベースページのイメージに、既にログファイルに記録されていた変更分が含まれていなければならないということです。 言い換えれば、InnoDB はチェックポイントを作成しなければならず、そしてこれは変更されたデータベースのページをディスクにフラッシュすることをしばしば引き起こすことになります。 InnoDB writes to the log files in a circular fashion. All committed modifications which make the database pages in the buffer pool different from the images on disk must be available in the log files in case InnoDB has to do a recovery. This means that when InnoDB starts to reuse a log file in the circular fashion, it has to make sure that the database page images on disk already contain the modifications logged in the log file InnoDB is going to reuse. In other words, InnoDB has to make a checkpoint and often this involves flushing of modified database pages to disk.

      上に述べた事柄は、なぜログファイルをとても大きく作成することが チェックポイント作成において disk I/O を減らすことになるのかの理由です。 The above explains why making your log files very big may save disk I/O in checkpointing. It can make sense to set the total size of the log files as big as the buffer pool or even bigger. The drawback in big log files is that crash recovery can last longer because there will be more log to apply to the database.

      7.5.7 InnoDB データベースを他の機械に移動する

      InnoDB データとログファイルは、 もし、その機械の浮動小数点数のフォーマットが同じであれば、 全プラットフォームでバイナリ互換を持ちます。 InnoDB は、単純に、関連ファイルを全てコピーすることで移動可能です。 (関連ファイルは前節で述べられています)　

      InnoDB データベースは、全てのファイルを単純にコピーするだけで、 移動が可能です。 ファイルは、前述のデータベースのバックアップの節で 述べたものです。 もし浮動小数点数のフォーマットが違う機械であったとしても、 テーブルに FLOAT や DOUBLE の型を使用していないのであれば、 手順は同じです： すなわち単にファイルをコピーするだけです。 もし浮動小数点数のフォーマットが違う機械で、テーブルに 浮動小数点数を保存している場合は、 `mysqldump' と `mysqlimport' コマンドを使用して テーブルを移動しなくてはなりません。

      A performance tip is to switch off auto-commit mode when you import data into your database, assuming your tablespace has enough space for the big rollback segment the big import transaction will generate. Do the commit only after importing a whole table or a segment of a table.

      7.5.8 InnoDB Transaction Model

      In the InnoDB transaction model the goal has been to combine the best properties of a multi-versioning database to traditional two-phase locking. InnoDB does locking on row level and runs queries by default as non-locking consistent reads, in the style of Oracle. The lock table in InnoDB is stored so space-efficiently that lock escalation is not needed: typically several users are allowed to lock every row in the database, or any random subset of the rows, without InnoDB running out of memory.

      In InnoDB all user activity happens inside transactions. もし、autocommit mode が MySQL で使用されているなら、 それぞれの SQL 文は単一の transaction となります。 MySQL always starts a new connection with the autocommit mode switched on.

      もし autocommit mode が SET AUTOCOMMIT = 0 で off にされたなら、 ユーザーは常にトランザクションが可能な状態となります。 もし SQL の COMMIT or ROLLBACK 文を実行すると、 現在のトランザクションは完結し、新しいトランザクションが開始します。 どちらの文も全ての InnoDB のロック(カレントのトランザクションに セットされたロック)を外します。 A COMMIT means that the changes made in the current transaction are made permanent and become visible to other users. A ROLLBACK, on the other hand, cancels all modifications made by the current transaction.

      If the connection has AUTOCOMMIT = 1, then the user can still perform a multi-statement transaction by starting it with BEGIN and ending it with COMMIT or ROLLBACK.

      In terms of the SQL-1992 transaction isolation levels, the InnoDB default is REPEATABLE READ. Starting from version 4.0.5, InnoDB offers all 4 different transaction isolation levels described by the SQL-1992 standard. You can set the default isolation level for all connections in the [mysqld] section of `my.cnf': 

      transaction-isolation = {READ-UNCOMMITTED | READ-COMMITTED
                         | REPEATABLE-READ | SERIALIZABLE}

      A user can change the isolation level of a single session or all new incoming connections with the 

      SET [SESSION | GLOBAL] TRANSACTION ISOLATION LEVEL
                       {READ UNCOMMITTED | READ COMMITTED
                        | REPEATABLE READ | SERIALIZABLE}

      SQL statement. Note that there are no hyphens in level names in the SQL syntax. If you specify the keyword GLOBAL in the above statement, it will determine the initial isolation level of new incoming connections, but will not change the isolation level of old connections. Any user is free to change the isolation level of his session, even in the middle of a transaction. In versions < 3.23.50 SET TRANSACTION had no effect on InnoDB tables. In versions < 4.0.5 only REPEATABLE READ and SERIALIZABLE were available.

      You can query the global and session transaction isolation levels with: 

      SELECT @@global.tx_isolation;
SELECT @@tx_isolation;

      In row level locking InnoDB uses so-called next-key locking. That means that besides index records, InnoDB can also lock the 'gap' before an index record to block insertions by other users immediately before the index record. A next-key lock means a lock which locks an index record and the gap before it. A gap lock means a lock which only locks a gap before some index record.

      A detailed description of each isolation level in InnoDB:

      • READ UNCOMMITTED This is also called 'dirty read': non-locking SELECTs are performed so that we do not look at a possible earlier version of a record; thus they are not 'consistent' reads under this isolation level; otherwise this level works like READ COMMITTED.
      • READ COMMITTED Somewhat Oracle-like isolation level. All SELECT ... FOR UPDATE and SELECT ... LOCK IN SHARE MODE statements only lock the index records, NOT the gaps before them, and thus allow free inserting of new records next to locked records. UPDATE and DELETE which use a unique index with a unique search condition, only lock the index record found, not the gap before it. But still in range type UPDATE and DELETE InnoDB must set next-key or gap locks and block insertions by other users to the gaps covered by the range. This is necessary since 'phantom rows' have to be blocked for MySQL replication and recovery to work. Consistent reads behave like in Oracle: each consistent read, even within the same transaction, sets and reads its own fresh snapshot.
      • REPEATABLE READ This is the default isolation level of InnoDB. SELECT ... FOR UPDATE, SELECT ... LOCK IN SHARE MODE, UPDATE, and DELETE which use a unique index with a unique search condition, only lock the index record found, not the gap before it. Otherwise these operations employ next-key locking, locking the index range scanned with next-key or gap locks, and block new insertions by other users. In consistent reads there is an important difference from the previous isolation level: in this level all consistent reads within the same transaction read the same snapshot established by the first read. This convention means that if you issue several plain SELECTs within the same transaction, these SELECTs are consistent also with respect to each other.
      • SERIALIZABLE This level is like the previous one, but all plain SELECTs are implicitly converted to SELECT ... LOCK IN SHARE MODE.

      7.5.8.1 Consistent Read

      A consistent read means that InnoDB uses its multi-versioning to present to a query a snapshot of the database at a point in time. The query will see the changes made by exactly those transactions that committed before that point of time, and no changes made by later or uncommitted transactions. The exception to this rule is that the query will see the changes made by the transaction itself which issues the query.

      If you are running with the default REPEATABLE READ isolation level, then all consistent reads within the same transaction read the snapshot established by the first such read in that transaction. You can get a fresher snapshot for your queries by committing the current transaction and after that issuing new queries.

      Consistent read is the default mode in which InnoDB processes SELECT statements in READ COMMITTED and REPEATABLE READ isolation levels. A consistent read does not set any locks on the tables it accesses, and therefore other users are free to modify those tables at the same time a consistent read is being performed on the table.

      7.5.8.2 Locking Reads

      consistent read は、いくつかの状況下では好都合ではありません。

      あなたが新しいレコードを CHILD テーブルに加えたいとします。 この child はすでに PARENT テーブルにある parent を 確実に持っているものとします。

      そしてあなたが PARENT テーブルを読むために、consistent read を 使用するとします。そのテーブル内に、たしかに、その child の parent を 見たとします。

      この場合、その child のレコードを安全に CHILD テーブルに 追加することが可能でしょうか？

      答えは No 。 なぜなら、あなたが気がつかない内に、 他のユーザーがその parent のレコードを PARENT テーブルから 消してしまうかも知れないからです。

      この解決として、SELECT を locking mode で動作させる方法が あります。 LOCK IN SHARE MODE. 

      SELECT * FROM PARENT WHERE NAME = 'Jones' LOCK IN SHARE MODE;

      Performing a read in share mode means that we read the latest available data, and set a shared mode lock on the rows we read. If the latest data belongs to a yet uncommitted transaction of another user, we will wait until that transaction commits. A shared mode lock prevents others from updating or deleting the row we have read. After we see that the above query returns the parent 'Jones', we can safely add his child to table CHILD, and commit our transaction. This example shows how to implement referential integrity in your application code.

      Let us look at another example: we have an integer counter field in a table CHILD_CODES which we use to assign a unique identifier to each child we add to table CHILD. Obviously, using a consistent read or a shared mode read to read the present value of the counter is not a good idea, since then two users of the database may see the same value for the counter, and we will get a duplicate key error when we add the two children with the same identifier to the table.

      In this case there are two good ways to implement the reading and incrementing of the counter: (1) update the counter first by incrementing it by 1 and only after that read it, or (2) read the counter first with a lock mode FOR UPDATE, and increment after that: 

      SELECT COUNTER_FIELD FROM CHILD_CODES FOR UPDATE;
UPDATE CHILD_CODES SET COUNTER_FIELD = COUNTER_FIELD + 1;

      A SELECT ... FOR UPDATE will read the latest available data setting exclusive locks on each row it reads. Thus it sets the same locks a searched SQL UPDATE would set on the rows.

      7.5.8.3 Next-key Locking: Avoiding the Phantom Problem

      row level のロッキングにおいては、InnoDB は next-key locking と呼ばれる アルゴリズムを使用します。 InnoDB does the row level locking so that when it searches or scans an index of a table, it sets shared or exclusive locks on the index records in encounters. Thus the row level locks are more precisely called index record locks.

      The locks InnoDB sets on index records also affect the 'gap' before that index record. If a user has a shared or exclusive lock on record R in an index, then another user cannot insert a new index record immediately before R in the index order. This locking of gaps is done to prevent the so-called phantom problem. Suppose I want to read and lock all children with identifier bigger than 100 from table CHILD, and update some field in the selected rows. 

      SELECT * FROM CHILD WHERE ID > 100 FOR UPDATE;

      CHILD テーブルの ID フィールドにインデックスが 張られているとします。 Our query will scan that index starting from the first record where ID is bigger than 100. Now, if the locks set on the index records would not lock out inserts made in the gaps, a new child might meanwhile be inserted to the table. If now I in my transaction execute 

      SELECT * FROM CHILD WHERE ID > 100 FOR UPDATE;

      again, I will see a new child in the result set the query returns. This is against the isolation principle of transactions: a transaction should be able to run so that the data it has read does not change during the transaction. If we regard a set of rows as a data item, then the new 'phantom' child would break this isolation principle.

      When InnoDB scans an index it can also lock the gap after the last record in the index. Just that happens in the previous example: the locks set by InnoDB will prevent any insert to the table where ID would be bigger than 100.

      You can use next-key locking to implement a uniqueness check in your application: if you read your data in share mode and do not see a duplicate for a row you are going to insert, then you can safely insert your row and know that the next-key lock set on the successor of your row during the read will prevent anyone meanwhile inserting a duplicate for your row. Thus the next-key locking allows you to 'lock' the non-existence of something in your table.

      7.5.8.4 Locks Set by Different SQL Statements in InnoDB

      • SELECT ... FROM ... : this is a consistent read, reading a snapshot of the database and setting no locks.
      • SELECT ... FROM ... LOCK IN SHARE MODE : sets shared next-key locks on all index records the read encounters.
      • SELECT ... FROM ... FOR UPDATE : sets exclusive next-key locks on all index records the read encounters.
      • INSERT INTO ... VALUES (...) : sets an exclusive lock on the inserted row; note that this lock is not a next-key lock and does not prevent other users from inserting to the gap before the inserted row. If a duplicate key error occurs, sets a shared lock on the duplicate index record.
      • INSERT INTO T SELECT ... FROM S WHERE ... sets an exclusive (non-next-key) lock on each row inserted into T. Does the search on S as a consistent read, but sets shared next-key locks on S if the MySQL logging is on. InnoDB has to set locks in the latter case because in roll-forward recovery from a backup every SQL statement has to be executed in exactly the same way as it was done originally.
      • CREATE TABLE ... SELECT ... performs the SELECT as a consistent read or with shared locks, like in the previous item.
      • REPLACE is done like an insert if there is no collision on a unique key. Otherwise, an exclusive next-key lock is placed on the row which has to be updated.
      • UPDATE ... SET ... WHERE ... : sets an exclusive next-key lock on every record the search encounters.
      • DELETE FROM ... WHERE ... : sets an exclusive next-key lock on every record the search encounters.
      • If a FOREIGN KEY constraint is defined on a table, any insert, update, or delete which requires checking of the constraint condition sets shared record level locks on the records it looks at to check the constraint. Also in the case where the constraint fails, InnoDB sets these locks.
      • LOCK TABLES ... : sets table locks. In the implementation the MySQL layer of code sets these locks. The automatic deadlock detection of InnoDB cannot detect deadlocks where such table locks are involved: see the following section. Also, since MySQL does know about row level locks, it is possible that you get a table lock on a table where another user currently has row level locks. But that does not put transaction integerity into danger. 「7.5.13 InnoDB テーブルの制限」節参照.

      7.5.8.5 How to cope with deadlocks?

      Deadlocks are a classic problem in transactional databases, but they are not dangerous, unless they are so frequent that you cannot run certain transactions at all. Normally you have to write your applications so that they are always prepared to re-issue a transaction if it gets rolled back because of a deadlock.

      InnoDB uses automatic row level locking. You can get deadlocks even in the case of transactions which just insert or delete a single row. That is because these operations are not really 'atomic': they automatically set locks on the (possibly several) index records of the row inserted/deleted.

      You can cope with deadlocks and reduce the number of them with the following tricks:

      • Use SHOW INNODB STATUS in MySQL versions >= 3.23.52 and >= 4.0.3 to determine the cause of the latest deadlock. That can help you to tune your application to avoid deadlocks.
      • Always be prepared to re-issue a transaction if it fails in a deadlock. Deadlocks are not dangerous. Just try again.
      • Commit your transactions often. Small transactions are less prone to collide.
      • If you are using locking reads SELECT ... FOR UPDATE or ... LOCK IN SHARE MODE, try using a lower isolation level READ COMMITTED.
      • Access your tables and rows in a fixed order. Then transactions will form nice queues, and do not deadlock.
      • Add good indexes to your tables. Then your queries need to scan less index records and consequently set less locks. Use EXPLAIN SELECT to determine that MySQL picks appropriate indexes for your queries.
      • Use less locking: if you can afford a SELECT to return data from an old snapshot, do not add the clause FOR UPDATE or LOCK IN SHARE MODE to it. Using READ COMMITTED isolation level is good here, because each consistent read within the same transaction reads from its own fresh snapshot.
      • If nothing helps, serialize your transactions with table level locks: LOCK TABLES t1 WRITE, t2 READ, ... ; [do something with tables t1 and t2 here]; UNLOCK TABLES. Table level locks make you transactions to queue nicely, and deadlocks are avoided. Note that LOCK TABLES implicitly starts a transaction, just like the command BEGIN, and UNLOCK TABLES implicitly ends the transaction in a COMMIT.
      • Another solution to serialize transactions is to create an auxiliary 'semaphore' table where there is just a single row. Each transaction updates that row before accessing other tables. In that way all transactions happen in a serial fashion. Note that then also the InnoDB instant deadlock detection algorithm works, because the serializing lock is a row level lock. In MySQL table level locks we have to resort to the timeout method to resolve a deadlock.

      7.5.8.6 Deadlock Detection and Rollback

      InnoDB automatically detects a deadlock of transactions and rolls back a transaction or transactions to prevent the deadlock. Starting from version 4.0.5, InnoDB will try to pick small transactions to roll back. The size of a transaction is determined by the number of rows it has inserted, updated, or deleted. Previous to 4.0.5, InnoDB always rolled back the transaction whose lock request was the last one to build a deadlock, that is, a cycle in the waits-for graph of transactions.

      InnoDB cannot detect deadlocks where a lock set by a MySQL LOCK TABLES statement is involved, or if a lock set in another storage engine than InnoDB is involved. You have to resolve these situations using innodb_lock_wait_timeout set in `my.cnf'.

      When InnoDB performs a complete rollback of a transaction, all the locks of the transaction are released. However, if just a single SQL statement is rolled back as a result of an error, some of the locks set by the SQL statement may be preserved. This is because InnoDB stores row locks in a format where it cannot afterwards know which was set by which SQL statement.

      7.5.8.7 An Example of How the Consistent Read Works in InnoDB

      Suppose you are running on the default REPEATABLE READ isolation level. When you issue a consistent read, that is, an ordinary SELECT statement, InnoDB will give your transaction a timepoint according to which your query sees the database. Thus, if transaction B deletes a row and commits after your timepoint was assigned, then you will not see the row deleted. Similarly with inserts and updates.

      You can advance your timepoint by committing your transaction and then doing another SELECT.

      This is called multi-versioned concurrency control. 

                        User A                 User B

              SET AUTOCOMMIT=0;      SET AUTOCOMMIT=0;
time
|             SELECT * FROM t;
|             empty set
|                                    INSERT INTO t VALUES (1, 2);
|
v             SELECT * FROM t;
              empty set
                                     COMMIT;

              SELECT * FROM t;
              empty set;

              COMMIT;

              SELECT * FROM t;
              ---------------------
              |    1    |    2    |
              ---------------------

      Thus user A sees the row inserted by B only when B has committed the insert, and A has committed his own transaction so that the timepoint is advanced past the commit of B.

      If you want to see the ``freshest'' state of the database, you should use a locking read: 

      SELECT * FROM t LOCK IN SHARE MODE;

      7.5.8.8 パフォーマンス・チューニング Tips

      1. もし Unix `top' や Windows `Task Manager' が CPU 使用率を 70% 未満に 表示している場合、おそらく、disk アクセスに処理が取られています。 とても多くのトランザクションのコミットを作成しているか、 バッファプールが小さいのでしょう。 バッファプールを大きくすれば良くなりますが、しかし、バッファプールは 物理メモリの 80% より大きくしないように。

      2. Wrap several modifications into one transaction. InnoDB must flush the log to disk at each transaction commit, if that transaction made modifications to the database. Since the rotation speed of a disk is typically at most 167 revolutions/second, that constrains the number of commits to the same 167/second if the disk does not fool the operating system.

      3. If you can afford the loss of some latest committed transactions, you can set the `my.cnf' parameter innodb_flush_log_at_trx_commit to zero. InnoDB tries to flush the log anyway once in a second, though the flush is not guaranteed.

      4. Make your log files big, even as big as the buffer pool. When InnoDB has written the log files full, it has to write the modified contents of the buffer pool to disk in a checkpoint. Small log files will cause many unnecessary disk writes. The drawback in big log files is that recovery time will be longer.

      5. Also the log buffer should be quite big, say 8 MB.

      6. (Relevant from 3.23.39 up.) Linux や　Unix のいくつかのバージョンでは、disk のファイルのフラッシュに Unix fdatasync や それに似た方法を使用しますが、 これは驚くほど遅いです。 InnoDB のデフォルトの方法は、fdatasync 関数を使用します。 もしデータベースの書き込みのパフォーマンスに満足しない場合には、 `my.cnf' ファイルで innodb_flush_method を O_DSYNC に セットしてもかまいません。しかし O_DSYNC はほとんどのシステムでは 遅いようです。

      7. InnoDB にデータを流し込む場合には、 MySQL の設定が autocommit=1 になっていないようにします。 それぞれの全ての insert が log をディスクにフラッシュすることを要求するからです。 取り込む SQL の最初に 

      SET AUTOCOMMIT=0;

      を追加し、最後に 

      COMMIT;

      を書きます。

      もし `mysqldump' を --opt オプションで使用しているなら、 上記のように SET AUTOCOMMIT=0; ... COMMIT; でダンプファイルを囲まないでも、 早く InnoDB テーブルにダンプを取り込むことが可能です。

      8. 大量のinsertの大きなロールバックに気をつけなさい； InnoDB は insert の時には、disk I/O を少なくするために insert buffer を 使用します。しかし、ロールバックには同じような機構は使用されません。 ロールバック時のディスク・バウンドは、対応するinsertに比べて 30倍の 時間がかかります。 データベースのプロセスを kill することは、何の解決にもなりません。 なぜなら、データベースがスタートアップした時、 再びロールバックが開始されるからです。 制御しきれないロールバックから免れる方法は、 バッファプールを増やすか(こうすればロールバックは CPU-bound でおさまり、速く終わります)、 InnoDB 全体を消し去ってしまうかしかありません。

      9. Beware also of other big disk-bound operations. Use DROP TABLE or TRUNCATE (from MySQL-4.0 up) to empty a table, not DELETE FROM yourtable.

      10. もしたくさんのレコードをインサートする必要があるならば、 サーバーとクライアントのコミュニケーションのオーバーヘッドを軽減するために、 マルチライン INSERT を使用します： 

      INSERT INTO yourtable VALUES (1, 2), (5, 5);

      この方法は InnoDB だけではなく、他のテーブル型にインサートする時も使用できます。

      7.5.8.9 InnoDB モニタ

      バージョン 3.23.41 から、InnoDB は InnoDB Monitor を含むようになりました。 これは InnoDB 内部の状態を表示するものです。 このスイッチを on にすると、MySQL サーバは 15 秒毎に標準出力にデータを出力するようになります。 (note: the MySQL client will not print anything) このデータはパフォーマンス・チューニングに便利です。

      On Windows you must start mysqld-max from a MS-DOS prompt with the --standalone --console options to direct the output to the MS-DOS prompt window.

      There is a separate innodb_lock_monitor which prints the same information as innodb_monitor plus information on locks set by each transaction.

      The printed information includes data on:

      • table and record locks held by each active transaction,
      • lock waits of a transactions,
      • semaphore waits of threads,
      • pending file I/O requests,
      • buffer pool statistics, and
      • purge and insert buffer merge activity of the main thread of InnoDB.

      InnoDB モニタは、以下の SQL コマンドでスタートできます： 

      CREATE TABLE innodb_monitor(a int) type = innodb;

      停止は： 

      DROP TABLE innodb_monitor;

      CREATE TABLE 文は、MySQL SQL パーサーを通して InnoDB エンジンにアクセスするためだけに使用されているにすぎません： 作成されたテーブルは InnoDB モニタとは関係しません。 もし、モニタ実行中にデータベースを停止し、そのあと、 モニタを再び起動したいなら、 あなたはモニタを起動するための新しい CREATE TABLE 文を 実行する前に、前に作ったテーブルを破棄しなくてはなりません。 この構文は将来のリリースで変わるかもしれません。

      InnoDB モニタ の出力サンプル: 

      ================================
010809 18:45:06 INNODB MONITOR OUTPUT
================================
--------------------------
LOCKS HELD BY TRANSACTIONS
--------------------------
LOCK INFO:
Number of locks in the record hash table 1294
LOCKS FOR TRANSACTION ID 0 579342744
TABLE LOCK table test/mytable trx id 0 582333343 lock_mode IX

RECORD LOCKS space id 0 page no 12758 n bits 104 table test/mytable index
PRIMARY trx id 0 582333343 lock_mode X
Record lock, heap no 2 PHYSICAL RECORD: n_fields 74; 1-byte offs FALSE;
info bits 0
 0: len 4; hex 0001a801; asc ;; 1: len 6; hex 000022b5b39f; asc ";;
 2: len 7; hex 000002001e03ec; asc ;; 3: len 4; hex 00000001;
...
-----------------------------------------------
CURRENT SEMAPHORES RESERVED AND SEMAPHORE WAITS
-----------------------------------------------
SYNC INFO:
Sorry, cannot give mutex list info in non-debug version!
Sorry, cannot give rw-lock list info in non-debug version!
-----------------------------------------------------
SYNC ARRAY INFO: reservation count 6041054, signal count 2913432
4a239430 waited for by thread 49627477 op. S-LOCK file NOT KNOWN line 0
Mut ex 0 sp 5530989 r 62038708 sys 2155035;
rws 0 8257574 8025336; rwx 0 1121090 1848344
-----------------------------------------------------
CURRENT PENDING FILE I/O'S
--------------------------
Pending normal aio reads:
Reserved slot, messages 40157658 4a4a40b8
Reserved slot, messages 40157658 4a477e28
...
Reserved slot, messages 40157658 4a4424a8
Reserved slot, messages 40157658 4a39ea38
Total of 36 reserved aio slots
Pending aio writes:
Total of 0 reserved aio slots
Pending insert buffer aio reads:
Total of 0 reserved aio slots
Pending log writes or reads:
Reserved slot, messages 40158c98 40157f98
Total of 1 reserved aio slots
Pending synchronous reads or writes:
Total of 0 reserved aio slots
-----------
BUFFER POOL
-----------
LRU list length 8034
Free list length 0
Flush list length 999
Buffer pool size in pages 8192
Pending reads 39
Pending writes: LRU 0, flush list 0, single page 0
Pages read 31383918, created 51310, written 2985115
----------------------------
END OF INNODB MONITOR OUTPUT
============================
010809 18:45:22 InnoDB starts purge
010809 18:45:22 InnoDB purged 0 pages

      出力に関するいくつかの注釈:

      • もし LOCKS HELD BY TRANSACTIONS セクションにロック待ちが レポートされているなら、あなたのアプリケーションがロックの競合を 起こしています。 出力はトランザクションのデッドロックの理由をたどるための 手助けになります。
      • SYNC INFO セクションは予約されたセマフォを報告します。 ただし、もし `univ.i' ファイルの UNIV_SYNC_DEBUG を有効にして、InnoDB をコンパイルしているならば。
      • Section SYNC ARRAY INFO reports threads waiting for a semaphore and statistics on how many times threads have needed a spin or a wait on a mutex or a rw-lock semaphore. A big number of threads waiting for semaphores may be a result of disk I/O, or contention problems inside InnoDB. Contention can be due to heavy parallelism of queries, or problems in operating system thread scheduling.
      • CURRENT PENDING FILE I/O'S セクションは、 延期された ファイル I/O リクエストの一覧をだします。 A large number of these indicates that the workload is disk I/O -bound.
      • BUFFER POOL セクションは、ページの読み込みと書き出しの統計情報を 与えます。 You can calculate from these numbers how many datafile I/Os your queries are currently doing.

      7.5.9 Implementation of Multi-versioning

      InnoDB は multiversioned database なので、テーブル空間中のレコードの 古いバージョン情報が保持されなくてはなりません。 This information is stored in a data structure we call a rollback segment after an analogous data structure in Oracle.

      InnoDB は内部では、データベースに保存されているそれぞれのレコードに対して 2 つのフィールドを付加しています。 A 6-byte field tells the transaction identifier for the last transaction which inserted or updated the row. Also a deletion is internally treated as an update where a special bit in the row is set to mark it as deleted. それぞれのレコードには、roll pointer と呼ばれる 7-byte のフィールドも含みます。 The roll pointer points to an undo log record written to the rollback segment. If the row was updated, then the undo log record contains the information necessary to rebuild the content of the row before it was updated.

      InnoDB uses the information in the rollback segment to perform the undo operations needed in a transaction rollback. It also uses the information to build earlier versions of a row for a consistent read.

      ロールバック セグメント の中の Undo log は、 insert と update の undo log に分けれれます。 Insert undo log は、トランザクションのロールバックの時にだけ必要とされ、 その トランザクション が コミット するやいなやすぐに破棄されます。 Update undo logs are used also in consistent reads, and they can be discarded only after there is no transaction present for which InnoDB has assigned a snapshot that in a consistent read could need the information in the update undo log to build an earlier version of a database row.

      You must remember to commit your transactions regularly, also those transactions which only issue consistent reads. Otherwise InnoDB cannot discard data from the update undo logs, and the rollback segment may grow too big, filling up your tablespace.

      The physical size of an undo log record in the rollback segment is typically smaller than the corresponding inserted or updated row. You can use this information to calculate the space need for your rollback segment.

      In our multi-versioning scheme a row is not physically removed from the database immediately when you delete it with an SQL statement. Only when InnoDB can discard the update undo log record written for the deletion, it can also physically remove the corresponding row and its index records from the database. This removal operation is called a purge, and it is quite fast, usually taking the same order of time as the SQL statement which did the deletion.

      7.5.10 テーブルとインデックスの構造

      MySQL は、テーブルの data dictionary 情報を、 データベース ディレクトリ内の、 `.frm' ファイルに保存します。 しかし、InnoDB タイプの全てのテーブルは、 InnoDB の内部のデータ・ディクショナリを (InnoDBの)テーブル空間に持っています。 MySQL がテーブルやデータベースを破棄する時は、 `.frm' ファイル と それに対応する InnoDB のデータ・ディクショナリ 内のエントリが消去されます。 これは、`.frm' ファイルを移動するだけでは InnoDB テーブルを違うデータベースに移動することができない理由であり、 また、MySQL 3.23.43 以下のバージョンで、InnoDB 型のテーブルでは DROP DATABASE が動作しなかった理由でもあります。

      Every InnoDB table has a special index called the clustered index where the data of the rows is stored. If you define a PRIMARY KEY on your table, then the index of the primary key will be the clustered index.

      もしテーブルにプライマリ・キーを定義しなかった場合には、 InnoDB は内部ではクラスタド・インデックス(clustered index)を作成します。 そこでは、InnoDB がそのテーブルのレコードに割り当てた row id をもとに レコードが整理されます。 row id は 6-byte のフィールドで、新しいレコードが挿入されると単純に 数が増加していきます。 ということで、row id のよって整理されているレコードは、 物理的にインサートされた順になっています。

      Accessing a row through the clustered index is fast, because the row data will be on the same page where the index search leads us. In many databases the data is traditionally stored on a different page from the index record. If a table is large, the clustered index architecture often saves a disk I/O when compared to the traditional solution.

      The records in non-clustered indexes (we also call them secondary indexes), in InnoDB contain the primary key value for the row. InnoDB uses this primary key value to search for the row from the clustered index. Note that if the primary key is long, the secondary indexes will use more space.

      7.5.10.1 Physical Structure of an Index

      InnoDB の全てのインデックスは B-Tree で、インデックスのレコードは、 ツリーの リーフ ページ (原文 leaf page. ブロックと言い換える or not?) に保存されます。 インデックス ページの デフォルトの大きさは 16kB です。 新しいレコードがインサートされた時、InnoDB はページの 1/16 を、 将来のインデックスレコードの insert や update に備えて free に しようとします。

      If index records are inserted in a sequential (ascending or descending) order, the resulting index pages will be about 15/16 full. If records are inserted in a random order, then the pages will be 1/2 - 15/16 full. If the fillfactor of an index page drops below 1/2, InnoDB will try to contract the index tree to free the page.

      7.5.10.2 Insert Buffering

      プライマリ・キーが一意で、新しいレコードがそのプライマリー・キーの 並びの順番で insert されるというのは、 データベースのアプリケーションではよくある事です。 この場合は、clustered index に対するインサートはディスクからの ランダム リードを要求しません。

      これに対して、secondary indexes は通常 非ユニーク で、 secondary indexes に対するインサートされる順番はばらばらです。 This would cause a lot of random disk I/O's without a special mechanism used in InnoDB.

      If an index record should be inserted to a non-unique secondary index, InnoDB checks if the secondary index page is already in the buffer pool. If that is the case, InnoDB will do the insertion directly to the index page. But, if the index page is not found from the buffer pool, InnoDB inserts the record to a special insert buffer structure. The insert buffer is kept so small that it entirely fits in the buffer pool, and insertions can be made to it very fast.

      The insert buffer is periodically merged to the secondary index trees in the database. Often we can merge several insertions on the same page in of the index tree, and hence save disk I/Os. It has been measured that the insert buffer can speed up insertions to a table up to 15 times.

      7.5.10.3 Adaptive Hash Indexes

      If a database fits almost entirely in main memory, then the fastest way to perform queries on it is to use hash indexes. InnoDB has an automatic mechanism which monitors index searches made to the indexes defined for a table, and if InnoDB notices that queries could benefit from building of a hash index, such an index is automatically built.

      But note that the hash index is always built based on an existing B-tree index on the table. InnoDB can build a hash index on a prefix of any length of the key defined for the B-tree, depending on what search pattern InnoDB observes on the B-tree index. A hash index can be partial: it is not required that the whole B-tree index is cached in the buffer pool. InnoDB will build hash indexes on demand to those pages of the index which are often accessed.

      In a sense, through the adaptive hash index mechanism InnoDB adapts itself to ample main memory, coming closer to the architecture of main memory databases.

      7.5.10.4 Physical Record Structure

      • InnoDB 中のそれぞれのインデックス レコードは、6 bytes のヘッダを含みます。 The header is used to link consecutive records together, and also in the row level locking.
      • Records in the clustered index contain fields for all user-defined columns. 1つの 6-byte フィールドが transaction id のために存在し、 1つの 7-byte フィールドが roll pointer のために存在します。
      • If the user has not defined a primary key for a table, then each clustered index record contains also a 6-byte row id field.
      • Each secondary index record contains also all the fields defined for the clustered index key.
      • A record contains also a pointer to each field of the record. If the total length of the fields in a record is < 128 bytes, then the pointer is 1 byte, else 2 bytes.

      7.5.10.5 How an Auto-increment Column Works in InnoDB

      データベースがスタートアップした後、ユーザーが auto-increment が定義されているテーブル T に対して 初めて、insert を行なう時、 もしユーザーが auto-increment のフィールドに明示的に値を与えなければ、 InnoDB は SELECT MAX(auto-inc-column) FROM T を実行し、そして その結果得た値に１を加えた数を、 そのフィールドと テーブルの auto-increment counter に与えます。 これをもって、テーブル T の auto-increment counter が 初期化されたと言います。

      InnoDB follows the same procedure in initializing the auto-increment counter for a freshly created table.

      もしユーザーが auto-increment のフィールドに 0 をインサートしたなら、 InnoDB はそれを、値が与えられなかったものとして扱うことに 注意してください。

      auto-increment counter が初期化された後、 もしユーザーがauto-increment のフィールドに明示的に値を与えてレコードを insert すれば、その値が現在の auto-increment counter より大きければ auto-increment counter はその値にセットされます。 もしユーザーが値を明示して与えなければ、InnODB は auto-increment counter を １つ増やし、そしてその値をフィールドの値としてセットします。

      The auto-increment mechanism, when assigning values from the counter, bypasses locking and transaction handling. Therefore you may also get gaps in the number sequence if you roll back transactions which have got numbers from the counter.

      The behaviour of auto-increment is not defined if a user gives a negative value to the column or if the value becomes bigger than the maximum integer that can be stored in the specified integer type.

      7.5.11 File Space Management and Disk I/O

      7.5.11.1 Disk I/O

      ディスク I/O では、InnoDB は非同期 I/O を使用します. On Windows NT it uses the native asynchronous I/O provided by the operating system. On Unix, InnoDB uses simulated asynchronous I/O built into InnoDB: InnoDB creates a number of I/O threads to take care of I/O operations, such as read-ahead. In a future version we will add support for simulated aio on Windows NT and native aio on those versions of Unix which have one.

      On Windows NT InnoDB uses non-buffered I/O. That means that the disk pages InnoDB reads or writes are not buffered in the operating system file cache. This saves some memory bandwidth.

      Starting from 3.23.41 InnoDB uses a novel file flush technique called doublewrite. It adds safety to crash recovery after an operating system crash or a power outage, and improves performance on most Unix flavors by reducing the need for fsync operations.

      Doublewrite means that InnoDB before writing pages to a datafile first writes them to a contiguous tablespace area called the doublewrite buffer. Only after the write and the flush to the doublewrite buffer has completed, InnoDB writes the pages to their proper positions in the datafile. If the operating system crashes in the middle of a page write, InnoDB will in recovery find a good copy of the page from the doublewrite buffer.

      3.23.41 からは、データファイルにロー・ディスク(raw disk)パーティションが 使用できますが、これはまだテスト段階です。 新しいデータファイルを作成するとき、 innodb_data_file_path に指定するデータファイルのサイズのすぐ後に、 newraw キーワードを付加すれば実現されます。 パーティションのサイズは、指定したサイズ以上(>=) でなければなりません。 InnoDB の 1M は、1024 x 1024 bytes を示します。 現実のディスク製品の表記では、1000 000 bytes を 1MB と表示することに 注意してください。 

      innodb_data_file_path=hdd1:5Gnewraw;hdd2:2Gnewraw

      設定を記述してデータベースを再起動した後は、 あなたはキーワードを raw に書き換えなければなりません。 書き換えを忘れると、InnoDB はそのパーティションを新規に上書きしてしまいます！ 

      innodb_data_file_path=hdd1:5Graw;hdd2:2Graw

      By using a raw disk you can on some Unixes perform unbuffered I/O.

      There are two read-ahead heuristics in InnoDB: sequential read-ahead and random read-ahead. In sequential read-ahead InnoDB notices that the access pattern to a segment in the tablespace is sequential. Then InnoDB will post in advance a batch of reads of database pages to the I/O system. In random read-ahead InnoDB notices that some area in a tablespace seems to be in the process of being fully read into the buffer pool. Then InnoDB posts the remaining reads to the I/O system.

      7.5.11.2 File Space Management

      設定ファイルに記述したデータファイルを InnoDB のテーブル空間を作ります。 データファイルは単純に連結されてテーブル空間になります。 striping は使用されません。 Currently you cannot directly instruct where the space is allocated for your tables, except by using the following fact: from a newly created tablespace InnoDB will allocate space starting from the low end.

      テーブル空間は、デフォルトサイズが 16kB の データベース ページから成ります。 それらページは 64個までの連続する部分にグループ化されます。 その、テーブル空間内の 'まとまり' は、InnoDB では セグメント と呼ばれます。 The pages are grouped into extents of 64 consecutive pages. The 'files' inside a tablespace are called segments in InnoDB. The name of the rollback segment is somewhat misleading because it actually contains many segments in the tablespace.

      InnoDB 中のそれぞれのインデックスには、2つのセグメントが割り当てられます； 一つは B-tree の 非リーフ ノードに、もう一つは リーフのノードに。 The idea here is to achieve better sequentiality for the leaf nodes, which contain the data.

      テーブル空間内であるセグメントが大きくなった場合、 InnoDB は 最初の 32 ページを個々に割り当てます。 そののち、InnoDB は全領域をそのセグメントに割り当はじめます。 InnoDB はデータがより良く連続することを確実にするために、 領域を 4つまで、一度に大きなセグメントに追加することが出来ます。 When a segment grows inside the tablespace, InnoDB allocates the first 32 pages to it individually. After that InnoDB starts to allocate whole extents to the segment. InnoDB can add to a large segment up to 4 extents at a time to ensure good sequentiality of data.

      テーブル空間内のいくつかのページには、他のページのビットマップが含まれ、 その結果、InnoDB テーブル空間内の数個の領域は、全てをセグメントに 割り当てることができず、個々のページ毎に割り当てられます。 Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an InnoDB tablespace cannot be allocated to segments as a whole, but only as individual pages.

      テーブル空間の available free space を知るためにあなたが SHOW TABLE STATUS FROM ... LIKE ... クエリを実行した時、 InnoDB は、 テーブル空間内の、確実に使用できるフリーな領域の合計をレポートします。 InnoDB は、clean-up と他の内部的な使用目的のために、常にいくつかの領域を リザーブします。 これらのリザーブされた領域は free space には含まれません。

      When you delete data from a table, InnoDB will contract the corresponding B-tree indexes. It depends on the pattern of deletes if that frees individual pages or extents to the tablespace, so that the freed space is available for other users. Dropping a table or deleting all rows from it is guaranteed to release the space to other users, but remember that deleted rows can be physically removed only in a purge operation after they are no longer needed in transaction rollback or consistent read.

      7.5.11.3 テーブルのデフラグメント

      If there are random insertions or deletions in the indexes of a table, the indexes may become fragmented. By fragmentation we mean that the physical ordering of the index pages on the disk is not close to the alphabetical ordering of the records on the pages, or that there are many unused pages in the 64-page blocks which were allocated to the index.

      定期的に mysqldump を使用してテーブルをテキストファイルにダンプし、 テーブルを削除し、ダンプファイルからテーブルを作り直す事を行なうことで、 インデックスの走査を速くすることが可能です。 デフラグメントを行なう他の方法は、テーブルのタイプを ALTER で 一度 MyISAM にし、再び InnoDB に変更することです。 Note that a MyISAM table must fit in a single file on your operating system.

      If the insertions to and index are always ascending and records are deleted only from the end, then the file space management algorithm of InnoDB guarantees that fragmentation in the index will not occur.

      7.5.12 エラー ハンドリング

      The error handling in InnoDB is not always the same as specified in the ANSI SQL standards. According to the ANSI standard, any error during an SQL statement should cause the rollback of that statement. InnoDB sometimes rolls back only part of the statement, or the whole transaction. The following list specifies the error handling of InnoDB.

      • もしテーブルスペース中のファイルの空間を使いきれば、 MySQL 'Table is full' エラーとなり、 InnoDB は SQL 文をロール・バックします。
      • トランザクションのデッドロックやロック待ちのタイムアウトの場合は、 InnoDB はトランザクション全てをロール・バックします。
      • A duplicate key error only rolls back the insert of that particular row, even in a statement like INSERT INTO ... SELECT .... This will probably change so that the SQL statement will be rolled back if you have not specified the IGNORE option in your statement.
      • 'row too long' エラーは、その SQL 文をロール・バックします。
      • Other errors are mostly detected by the MySQL layer of code, and they roll back the corresponding SQL statement.

      7.5.13 InnoDB テーブルの制限

      • Warning: MySQL システムテーブルを MyISAM から InnoDB テーブルに 変換してはいけません！ これはサポートされていません； もし変換してしまうと、バックアップから前のシステムテーブルを復旧させるか あるいは mysql_install_db スクリプトを使用して システムテーブルを再構築しない限り、MySQL は起動できません。
      • SHOW TABLE STATUS は、 InnoDB テーブルに関する統計を正確に返しません (ただしテーブルが使用している物理サイズは正確)。 The row count is only a rough estimate used in SQL optimisation.
      • フィールドの先頭部分にユニークなインデックスを作成しようとすると、 エラーになります： 
        CREATE TABLE T (A CHAR(20), B INT, UNIQUE (A(5))) TYPE = InnoDB;
        もし、フィールドの先頭部分に、非ユニークインデックスを作成しようとすると、 InnoDB は そのフィールドの全体にインデックスを張ります。
      • INSERT DELAYED は InnoDB テーブルではサポートされていません。
      • MySQL LOCK TABLES オペレーションは、 InnoDB のロー・レベル・ロック (row level lock) を感知しません。 これは、たとえ他のユーザーによるトランザクション(row lovel lock をしている)が あるテーブルに存在していたとしても、 あなたが同じテーブルに対して、テーブル・ロックをかけれるということです。 Thus your operations on the table may have to wait if they collide with these locks of other users. Also a deadlock is possible. However, this does not endanger transaction integrity, because the row level locks set by InnoDB will always take care of the integrity. Also, a table lock prevents other transactions from acquiring more row level locks (in a conflicting lock mode) on the table.
      • BLOB や TEXT フィールドにインデックスを張ることができません。
      • 1つのテーブルには 1000個 以上のフィールドを持つことができません。
      • DELETE FROM TABLE does not regenerate the table but instead deletes all rows, one by one, which is not that fast. In future versions of MySQL you can use TRUNCATE which is fast.
      • InnoDB のデフォルトのデータベースのページサイズは 16kB です。 コンパイルし直すことで、これは 8kB から　64kB まで変更可能です。 The maximun row length is slightly less than half of a database page in versions <= 3.23.40 of InnoDB. バージョン 3.23.41 からは、 BLOB と TEXT フィールドは 4GB 未満まで許されます。 1 レコードの最大容量も 4GB 未満までです。 InnoDB does not store fields whose size is <= 128 bytes on separate pages. After InnoDB has modified the row by storing long fields on separate pages, the remaining length of the row must be less than half a database page. The maximun key length is 7000 bytes.
      • いくつかのオペレーティングシステムでは、 データファイルは < 2GB となります。 The combined size of log files must be < 4 GB.
      • テーブル空間のサイズの最大値は 40億 データベース ページです。 これは 1つのテーブルの最大のサイズでもあります。 テーブル空間の最低限のサイズは 10MB です。

      7.5.14 InnoDB Change History

      7.5.14.1 MySQL/InnoDB-4.1.0, April x, 2003

      • InnoDB now supports up to 64 GB of buffer pool memory in a Windows 32-bit Intel computer. This is possible because InnoDB can use the AWE extension of Windows to address memory over the 4 GB limit of a 32-bit process. A new startup variable innodb_buffer_pool_awe_mem_mb enables AWE and sets the size of the buffer pool in megabytes.
      • Reduced the size of buffer headers and the lock table. InnoDB uses 2 % less memory.

      7.5.14.2 MySQL/InnoDB-3.23.56, March xx, 2003

      • Fixed a major bug in InnoDB query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good.

      7.5.14.3 MySQL/InnoDB-4.0.12, March xx, 2003

      • In crash recovery InnoDB now prints the progress in percents of a transaction rollback.

      7.5.14.4 MySQL/InnoDB-4.0.11, February 25, 2003

      • Fixed a bug introduced in 4.0.10: SELECT ... FROM ... ORDER BY ... DESC could hang in an infinite loop.
      • An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication.

      7.5.14.5 MySQL/InnoDB-4.0.10, February 4, 2003

      • In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed.
      • Increased SHOW INNODB STATUS max printed length to 200 kB.
      • Fixed a major bug in InnoDB query optimization: queries of type SELECT ... WHERE indexcolumn < x and SELECT ... WHERE indexcolumn > x could cause a table scan even if the selectivity would have been very good.
      • Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field().
      • Fixed a bug: using InnoDB HANDLER commands on a fresh handle crashed mysqld in ha_innobase::change_active_index().
      • Fixed a bug: if MySQL estimated a query in the middle of a SELECT statement, InnoDB could hang on the adaptive hash index latch in btr0sea.c.
      • Fixed a bug: InnoDB could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert.
      • Fixed a bug: some file system snapshot tool in Windows 2000 could cause an InnoDB file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes InnoDB now retries the write 100 times at 1 second intervals.
      • Fixed a bug: REPLACE INTO t1 SELECT ... did not work if t1 has an auto-inc column.
      • An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication.

      7.5.14.6 MySQL/InnoDB-3.23.55, January 24, 2003

      • In INSERT INTO t1 SELECT ... FROM t2 WHERE ... MySQL previously set a table level read lock on t2. This lock is now removed.
      • Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail in log scan.
      • Fixed a bug: index cursor restoration could theoretically fail.
      • Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads.
      • Fixed a bug: purge could cause a hang in a BLOB table where the primary key index tree was of height 1. Symptom: semaphore waits caused by an X-latch set in btr_free_externally_stored_field().
      • Fixed a bug: if MySQL estimated a query in the middle of a SELECT statement, InnoDB could hang on the adaptive hash index latch in btr0sea.c.
      • Fixed a bug: InnoDB could report table corruption and assert in page_dir_find_owner_slot() if an adaptive hash index search coincided with purge or an insert.
      • Fixed a bug: some file system snapshot tool in Windows 2000 could cause an InnoDB file write to fail with error 33 ERROR_LOCK_VIOLATION. In synchronous writes InnoDB now retries the write 100 times at 1 second intervals.
      • An outstanding bug: SET FOREIGN_KEY_CHECKS=0 is not replicated properly in the MySQL replication. The fix will appear in 4.0.11 and will probably not be backported to 3.23.
      • Fixed bug in InnoDB page0cur.c in function page_cur_search_with_match which caused InnoDB to remain on the same page forever. This bug is evident only in tables with more than one page.

      7.5.14.7 MySQL/InnoDB-4.0.9, January 14, 2003

      • Removed the warning message: 'InnoDB: Out of memory in additional memory pool.'
      • Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail.
      • Fixed a bug: index cursor restoration could theoretically fail.

      7.5.14.8 MySQL/InnoDB-4.0.8, January 7, 2003

      • InnoDB now supports also FOREIGN KEY (...) REFERENCES ...(...) [ON UPDATE CASCADE | ON UPDATE SET NULL | ON UPDATE RESTRICT | ON UPDATE NO ACTION].
      • Tables and indexes now reserve 4 % less space in the tablespace. Also existing tables reserve less space. By upgrading to 4.0.8 you will see more free space in "InnoDB free" in SHOW TABLE STATUS.
      • Fixed bugs: updating the PRIMARY KEY of a row would generate a foreign key error on all FOREIGN KEYs which referenced secondary keys of the row to be updated. Also, if a referencing FOREIGN KEY constraint only referenced the first columns in an index, and there were more columns in that index, updating the additional columns generated a foreign key error.
      • Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes.
      • Fixed a bug: removed superfluous error 149 and 150 printouts from the .err log when a locking SELECT caused a deadlock or a lock wait timeout.
      • Fixed a bug: an assertion in btr0sea.c, in function btr_search_info_update_slow could theoretically fail in a race of 3 threads.
      • Fixed a bug: one could not switch a session transaction isolation level back to REPEATABLE READ after setting it to something else.

      7.5.14.9 MySQL/InnoDB-4.0.7, December 26, 2002

      • InnoDB in 4.0.7 is essentially the same as in 4.0.6.

      7.5.14.10 MySQL/InnoDB-4.0.6, December 19, 2002

      • Since innodb_log_arch_dir has no relevance under MySQL, there is no need to specify it any more in my.cnf.
      • LOAD DATA INFILE in AUTOCOMMIT=1 mode no longer does implicit commits for each 1 MB of written binlog.
      • Fixed a bug introduced in 4.0.4: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump.
      • Fixed two bugs introduced in 4.0.4: in AUTO_INCREMENT, REPLACE could cause the counter to be left 1 too low. A deadlock or a lock wait timeout could cause the same problem.
      • Fixed a bug: TRUNCATE on a TEMPORARY table crashed InnoDB.
      • Fixed a bug introduced in 4.0.5: if binlogging was not switched on, INSERT INTO ... SELECT ... or CREATE TABLE ... SELECT ... could cause InnoDB to hang on a semaphore created in btr0sea.c, line 128. Workaround: switch binlogging on.
      • Fixed a bug: in replication issuing SLAVE STOP in the middle of a multi-statement transaction could cause that SLAVE START would only perform a part of the transaction. A similar error could occur if the slave crashed and was restarted.

      7.5.14.11 MySQL/InnoDB-3.23.54, December 12, 2002

      • Fixed a bug: the InnoDB range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch already in the root. This could cause unnecessary table scans in SQL queries.
      • Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL.
      • Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes.
      • Fixed a bug: if a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, InnoDB could erroneously return the NEXT record.
      • Fixed a bug introduced in 3.23.53: LOCK TABLES ... READ LOCAL should not set row locks on the rows read. This caused deadlocks and lock wait timeouts in mysqldump.
      • Fixed a bug: if an index contains some column twice, and that column is updated, the table will become corrupt. From now on InnoDB prevents creation of such indexes.

      7.5.14.12 MySQL/InnoDB-4.0.5, November 18, 2002

      • InnoDB now supports also transaction isolation levels READ COMMITTED and READ UNCOMMITTED. READ COMMITTED more closely emulates Oracle and makes porting of applications from Oracle to MySQL easier.
      • Deadlock resolution is now selective: we try to pick as victims transactions with less modified or inserted rows.
      • FOREIGN KEY definitions are now aware of the lower_case_table_names setting in my.cnf.
      • SHOW CREATE TABLE does not output the database name to a FOREIGN KEY definition if the referred table is in the same database as the table.
      • InnoDB does a consistency check to most index pages before writing them to a data file.
      • If you set innodb_force_recovery > 0, InnoDB tries to jump over corrupt index records and pages when doing SELECT * FROM table. This helps in dumping.
      • InnoDB now again uses asynchronous unbuffered i/o in Windows 2000 and XP; only unbuffered simulated async i/o in NT, 95/98/ME.
      • Fixed a bug: the InnoDB range estimator greatly exaggerated the size of a short index range if the paths to the endpoints of the range in the index tree happened to branch already in the root. This could cause unnecessary table scans in SQL queries. The fix will also be backported to 3.23.54.
      • Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: InnoDB startup could take very long or even crash on some Win 95/98/ME computers.
      • Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks.
      • Fixed a bug: if SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, InnoDB would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621.
      • Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes.
      • Fixed a potential bug in 4.0.4: InnoDB now does ORDER BY ... DESC like MyISAM.
      • Fixed a bug: DROP TABLE could cause crash or a hang if there was a rollback concurrently running on the table. The fix will only be backported to 3.23 if this appears a real problem for users.
      • Fixed a bug: ORDER BY could fail if you had not created a primary key to a table, but had defined several indexes of which at least one was a UNIQUE index with all its columns declared as NOT NULL.
      • Fixed a bug: a lock wait timeout in connection with ON DELETE CASCADE could cause corruption in indexes.
      • Fixed a bug: if a SELECT was done with a unique key from a primary index, and the search matched to a delete-marked record, InnoDB could return the NEXT record.
      • Outstanding bugs: in 4.0.4 two bugs were introduced to AUTO_INCREMENT. REPLACE can cause the counter to be left 1 too low. A deadlock or a lock wait timeout can cause the same problem. These will be fixed in 4.0.6.

      7.5.14.13 MySQL/InnoDB-3.23.53, October 9, 2002

      • We again use unbuffered disk i/o to data files in Windows. Win XP and Win 2000 read performance seems to be very poor with normal i/o.
      • Tuned range estimator so that index range scans are preferred over full index scans.
      • Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery.
      • Fixed a bug present in 3.23.52, 4.0.3, 4.0.4: InnoDB startup could take very long or even crash on some Win 95/98/ME computers.
      • Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge.
      • Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310.
      • Fixed a bug: the AUTO-INC lock was held to the end of the transaction if it was granted after a lock wait. This could cause unnecessary deadlocks.
      • Fixed a bug: if you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innobase.cc.
      • Fixed a bug: if SHOW INNODB STATUS, innodb_monitor, or innodb_lock_monitor had to print several hundred transactions in one report, and the output became truncated, InnoDB would hang, printing to the error log many waits for a mutex created at srv0srv.c, line 1621.
      • Fixed a bug: SHOW INNODB STATUS on Unix always reported average file read size as 0 bytes.

      7.5.14.14 MySQL/InnoDB-4.0.4, October 2, 2002

      • We again use unbuffered disk i/o in Windows. Win XP and Win 2000 read performance seems to be very poor with normal i/o.
      • Increased the max key length of InnoDB tables from 500 to 1024 bytes.
      • Increased the table comment field in SHOW TABLE STATUS so that up to 16000 characters of foreign key definitions can be printed there.
      • The auto-increment counter is no longer incremented if an insert of a row immediately fails in an error.
      • Allow dropping and creating a table even if innodb_force_recovery is set. One can use this to drop a table which would cause a crash in rollback or purge, or if a failed table import causes a runaway rollback in recovery.
      • Fixed a bug: Using ORDER BY primarykey DESC in 4.0.3 causes an assertion failure in btr0pcur.c, line 203.
      • Fixed a bug: fast shutdown (which is the default) sometimes was slowed down by purge and insert buffer merge.
      • Fixed a bug: doing a big SELECT from a table where no rows were visible in a consistent read could cause a very long (> 600 seconds) semaphore wait in btr0cur.c line 310.
      • Fixed a bug: if the MySQL query cache was used, it did not get invalidated by a modification done by ON DELETE CASCADE or ...SET NULL.
      • Fixed a bug: if you created a temporary table inside LOCK TABLES, and used that temporary table, that caused an assertion failure in ha_innodb.cc.
      • Fixed a bug: if you set innodb_flush_log_at_trx_commit to 1, SHOW VARIABLES would show its value as 16 million.

      7.5.14.15 MySQL/InnoDB-4.0.3, August 28, 2002

      • Removed unnecessary deadlocks when inserts have to wait for a locking read, update, or delete to release its next-key lock.
      • The MySQL HANDLER SQL commands now work also for InnoDB type tables. InnoDB does the HANDLER reads always as consistent reads. HANDLER is a direct access path to read individual indexes of tables. In some cases HANDLER can be used as a substitute of server-side cursors.
      • Fixed a bug in 4.0.2: even a simple insert could crash the AIX version.
      • Fixed a bug: if you used in a table name characters whose code is > 127, in DROP TABLE InnoDB could assert on line 155 of pars0sym.c.
      • Compilation from source now provides a working version both on HP-UX-11 and HP-UX-10.20. The source of 4.0.2 worked only on 11, and the source of 3.23.52 only on 10.20.
      • Fixed a bug: if compiled on 64-bit Solaris, InnoDB produced a bus error at startup.

      7.5.14.16 MySQL/InnoDB-3.23.52, August 16, 2002

      • The feature set of 3.23 will be frozen from this version on. New features will go the 4.0 branch, and only bug fixes will be made to the 3.23 branch.
      • Many CPU-bound join queries now run faster. On Windows also many other CPU-bound queries run faster.
      • A new SQL command SHOW INNODB STATUS returns the output of the InnoDB Monitor to the client. The InnoDB Monitor now prints detailed info on the latest detected deadlock.
      • InnoDB made the SQL query optimizer to avoid too much index-only range scans and choose full table scans instead. This is now fixed.
      • "BEGIN" and "COMMIT" are now added in the binlog around transactions. The MySQL replication now respects transaction borders: a user will no longer see half transactions in replication slaves.
      • A replication slave now prints in crash recovery the last master binlog position it was able to recover to.
      • A new setting innodb_flush_log_at_trx_commit=2 makes InnoDB to write the log to the operating system file cache at each commit. This is almost as fast as the setting innodb_flush_log_at_trx_commit=0, and the setting 2 also has the nice feature that in a crash where the operating system does not crash, no committed transaction is lost. If the operating system crashes or there is a power outage, then the setting 2 is no safer than the setting 0.
      • Added checksum fields to log blocks.
      • SET FOREIGN_KEY_CHECKS=0 helps in importing tables in an arbitrary order which does not respect the foreign key rules.
      • SET UNIQUE_CHECKS=0 speeds up table imports into InnoDB if you have UNIQUE constraints on secondary indexes.
      • SHOW TABLE STATUS now lists also possible ON DELETE CASCADE or ON DELETE SET NULL in the comment field of the table.
      • When CHECK TABLE is run on any InnoDB type table, it now checks also the adaptive hash index for all tables.
      • If you defined ON DELETE CASCADE or SET NULL and updated the referenced key in the parent row, InnoDB deleted or updated the child row. This is now changed to conform to SQL-92: you get the error 'Cannot delete parent row'.
      • Improved the auto-increment algorithm: now the first insert or SHOW TABLE STATUS initializes the auto-inc counter for the table. This removes almost all surprising deadlocks caused by SHOW TABLE STATUS.
      • Aligned some buffers used in reading and writing to data files. This allows using unbuffered raw devices as data files in Linux.
      • Fixed a bug: If you updated the primary key of a table so that only the case of characters changed, that could cause assertion failures, mostly in page0page.ic line 515.
      • Fixed a bug: If you delete or update a row referenced in a foreign key constraint and the foreign key check has to wait for a lock, then the check may report an erroneous result. This affects also the ON DELETE... operation.
      • Fixed a bug: A deadlock or a lock wait timeout error in InnoDB causes InnoDB to roll back the whole transaction, but MySQL could still write the earlier SQL statements to the binlog, even though InnoDB rolled them back. This could, for example, cause replicated databases to get out-of-sync.
      • Fixed a bug: If the database happened to crash in the middle of a commit, then the recovery might leak tablespace pages.
      • Fixed a bug: If you specified a non-latin1 character set in my.cnf, then, in contrary to what is stated in the manual, in a foreign key constraint a string type column had to have the same length specification in the referencing table and the referenced table.
      • Fixed a bug: DROP TABLE or DROP DATABASE could fail if there simultaneously was a CREATE TABLE running.
      • Fixed a bug: If you configured the buffer pool bigger than 2 GB in a 32-bit computer, InnoDB would assert in buf0buf.ic line 214.
      • Fixed a bug: on 64-bit computers updating rows which contained the SQL NULL in some column could cause the undo log and the ordinary log to become corrupt.
      • Fixed a bug: innodb_log_monitor caused a hang if it suppressed lock prints for a page.
      • Fixed a bug: in the HP-UX-10.20 version mutexes would leak and cause race conditions and crashes in any part of InnoDB code.
      • Fixed a bug: if you ran in the AUTOCOMMIT mode, executed a SELECT, and immediately after that a RENAME TABLE, then RENAME would fail and MySQL would complain about error 1192.
      • Fixed a bug: if compiled on 64-bit Solaris, InnoDB produced a bus error at startup.

      7.5.14.17 MySQL/InnoDB-4.0.2, July 10, 2002

      • InnoDB is essentially the same as InnoDB-3.23.51.
      • If no innodb_data_file_path is specified, InnoDB at the database creation now creates a 10 MB auto-extending data file ibdata1 to the datadir of MySQL. In 4.0.1 the file was 64 MB and not auto-extending.

      7.5.14.18 MySQL/InnoDB-3.23.51, June 12, 2002

      • Fixed a bug: a join could result in a seg fault in copying of a BLOB or TEXT column if some of the BLOB or TEXT columns in the table contained SQL NULL values.
      • Fixed a bug: if you added self-referential foreign key constraints with ON DELETE CASCADE to tables and a row deletion caused InnoDB to attempt the deletion of the same row twice because of a cascading delete, then you got an assertion failure.
      • Fixed a bug: if you use MySQL 'user level locks' and close a connection, then InnoDB may assert in ha_innobase.cc, line 302.

      7.5.14.19 MySQL/InnoDB-3.23.50, April 23, 2002

      • InnoDB now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup.
      • Made several changes to facilitate the use of the InnoDB Hot Backup tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks.
      • If you want to run the InnoDB Hot Backup tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35.
      • The log scan phase in crash recovery will now run much faster.
      • Starting from this server version, the hot backup tool truncates unused ends in the backup InnoDB data files.
      • To allow the hot backup tool to work, on Windows we no longer use unbuffered i/o or native async i/o; instead we use the same simulated async i/o as on Unix.
      • You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys.
      • FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX.
      • We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example.
      • SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions.
      • You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...).
      • FOREIGN KEY definitions now allow backquotes around table and column names.
      • MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then InnoDB obeys its default locking strategy which is REPEATABLE READ.
      • SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has already been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS.
      • Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150.

      7.5.14.20 MySQL/InnoDB-3.23.49, February 17, 2002

      • Fixed a bug: if you called DROP DATABASE for a database on which there simultaneously were running queries, the MySQL server could crash or hang. Crashes fixed, but a full fix has to wait some changes in the MySQL layer of code.
      • Fixed a bug: on Windows one had to put the database name in lower case for DROP DATABASE to work. Fixed in 3.23.49: case no longer matters on Windows. On Unix the database name remains case-sensitive.
      • Fixed a bug: if one defined a non-latin1 character set as the default character set, then definition of foreign key constraints could fail in an assertion failure in dict0crea.c, reporting an internal error 17.

      7.5.14.21 MySQL/InnoDB-3.23.48, February 9, 2002

      • Tuned the SQL optimizer to favor more often index searches over table scans.
      • Fixed a performance problem when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries will now also generally run faster on all platforms.
      • If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog file name and the position in that file (= byte offset) InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication.
      • Added better error messages to help in installation problems.
      • One can now recover also MySQL temporary tables which have become orphaned inside the InnoDB tablespace.
      • InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns.
      • Fixed a bug: calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE.
      • Fixed a bug: if on Unix you did an ALTER TABLE to an InnoDB table and simultaneously did queries to it, mysqld could crash with an assertion failure in row0row.c, line 474.
      • Fixed a bug: if inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c.
      • In 3.23.47 we allowed several NULLS in a UNIQUE secondary index. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation.
      • Fixed a bug: on Sparc and other high-endian processors SHOW VARIABLES showed innodb_flush_log_at_trx_commit and other boolean-valued startup parameters always OFF even if they were switched on.
      • Fixed a bug: if you ran mysqld-max-nt as a service on Windows NT/2000, the service shutdown did not always wait long enough for the InnoDB shutdown to finish.

      7.5.14.22 MySQL/InnoDB-3.23.47, December 28, 2001

      • Recovery happens now faster, especially in a lightly loaded system, because background checkpointing has been made more frequent.
      • InnoDB allows now several similar key values in a UNIQUE secondary index if those values contain SQL NULLs. Thus the convention is now the same as in MyISAM tables.
      • InnoDB gives a better row count estimate for a table which contains BLOBs.
      • In a FOREIGN KEY constraint InnoDB is now case-insensitive to column names, and in Windows also to table names.
      • InnoDB allows a FOREIGN KEY column of CHAR type to refer to a column of VARCHAR type, and vice versa. MySQL silently changes the type of some columns between CHAR and VARCHAR, and these silent changes do not hinder FOREIGN KEY declaration any more.
      • Recovery has been made more resilient to corruption of log files.
      • Unnecessary statistics calculation has been removed from queries which generate a temporary table. Some ORDER BY and DISTINCT queries will now run much faster.
      • MySQL now knows that the table scan of an InnoDB table is done through the primary key. This will save a sort in some ORDER BY queries.
      • The maximum key length of InnoDB tables is again restricted to 500 bytes. The MySQL interpreter is not able to handle longer keys.
      • The default value of innodb_lock_wait_timeout was changed from infinite to 50 seconds, the default value of innodb_file_io_threads from 9 to 4.

      7.5.14.23 MySQL/InnoDB-4.0.1, December 23, 2001

      • InnoDB is the same as in 3.23.47.
      • In 4.0.0 the MySQL interpreter did not know the syntax LOCK IN SHARE MODE. This has been fixed.
      • In 4.0.0 multi-table delete did not work for transactional tables. This has been fixed.

      7.5.14.24 MySQL/InnoDB-3.23.46, November 30, 2001

      • This is the same as 3.23.45.

      7.5.14.25 MySQL/InnoDB-3.23.45, November 23, 2001

      • This is a bugfix release.
      • In versions 3.23.42-.44 when creating a table on Windows you have to use lower case letters in the database name to be able to access the table. Fixed in 3.23.45.
      • InnoDB now flushes stdout and stderr every 10 seconds: if these are redirected to files, the file contents can be better viewed with an editor.
      • Fixed an assertion failure in .44, in trx0trx.c, line 178 when you drop a table which has the .frm file but does not exist inside InnoDB.
      • Fixed a bug in the insert buffer. The insert buffer tree could get into an inconsistent state, causing a crash, and also crashing the recovery. This bug could appear especially in large table imports or alterations.
      • Fixed a bug in recovery: InnoDB could go into an infinite loop constantly printing a warning message that it cannot find free blocks from the buffer pool.
      • Fixed a bug: when you created a temporary table of the InnoDB type, and then used ALTER TABLE to it, the MySQL server could crash.
      • Prevented creation of MySQL system tables 'mysql.user', 'mysql.host', or 'mysql.db', in the InnoDB type.
      • Fixed a bug which can cause an assertion failure in 3.23.44 in srv0srv.c, line 1728.

      7.5.14.26 MySQL/InnoDB-3.23.44, November 2, 2001

      • You can define foreign key constraints on InnoDB tables. An example: FOREIGN KEY (col1) REFERENCES table2(col2).
      • You can create > 4 GB data files in those file systems that allow it.
      • Improved InnoDB monitors, including a new innodb_table_monitor which allows you to print the contents of the InnoDB internal data dictionary.
      • DROP DATABASE will now work also for InnoDB tables.
      • Accent characters in the default character set latin1 will be ordered according to the MySQL ordering.<br> NOTE: if you are using latin1 and have inserted characters whose code is > 127 to an indexed CHAR column, you should run CHECK TABLE on your table when you upgrade to 3.23.43, and drop and reimport the table if CHECK TABLE reports an error!
      • InnoDB will calculate better table cardinality estimates.
      • Change in deadlock resolution: in .43 a deadlock rolls back only the SQL statement, in .44 it will roll back the whole transaction.
      • Deadlock, lock wait timeout, and foreign key constraint violations (no parent row, child rows exist) now return native MySQL error codes 1213, 1205, 1216, 1217, respectively.
      • A new my.cnf parameter innodb_thread_concurrency helps in performance tuning in high concurrency environments.
      • A new my.cnf option innodb_force_recovery will help you in dumping tables from a corrupted database.
      • A new my.cnf option innodb_fast_shutdown will speed up shutdown. Normally InnoDB does a full purge and an insert buffer merge at shutdown.
      • Raised maximum key length to 7000 bytes from a previous limit of 500 bytes.
      • Fixed a bug in replication of auto-inc columns with multiline inserts.
      • Fixed a bug when the case of letters changes in an update of an indexed secondary column.
      • Fixed a hang when there are > 24 data files.
      • Fixed a crash when MAX(col) is selected from an empty table, and col is a not the first column in a multi-column index.
      • Fixed a bug in purge which could cause crashes.

      7.5.14.27 MySQL/InnoDB-3.23.43, October 4, 2001

      • This is essentially the same as InnoDB-3.23.42.

      7.5.14.28 MySQL/InnoDB-3.23.42, September 9, 2001

      • Fixed a bug which corrupted the table if the primary key of a > 8000-byte row was updated.
      • There are now 3 types of InnoDB Monitors: innodb_monitor, innodb_lock_monitor, and innodb_tablespace_monitor. innodb_monitor now prints also buffer pool hit rate and the total number of rows inserted, updated, deleted, read.
      • Fixed a bug in RENAME TABLE.
      • Fixed a bug in replication with an auto-increment column.

      7.5.14.29 MySQL/InnoDB-3.23.41, August 13, 2001

      • Support for < 4 GB rows. The previous limit was 8000 bytes.
      • Use the doublewrite file flush method.
      • Raw disk partitions supported as data files.
      • InnoDB Monitor.
      • Several hang bugs fixed and an ORDER BY bug ('Sort aborted') fixed.

      7.5.14.30 MySQL/InnoDB-3.23.40, July 16, 2001

      • Only a few rare bugs fixed.

      7.5.14.31 MySQL/InnoDB-3.23.39, June 13, 2001

      • CHECK TABLE now works for InnoDB tables.
      • A new my.cnf parameter innodb_unix_file_flush_method introduced. It can be used to tune disk write performance.
      • An auto-increment column now gets new values past the transaction mechanism. This saves CPU time and eliminates transaction deadlocks in new value assignment.
      • Several bug fixes, most notably the rollback bug in 3.23.38.

      7.5.14.32 MySQL/InnoDB-3.23.38, May 12, 2001

      • The new syntax SELECT ... LOCK IN SHARE MODE is introduced.
      • InnoDB now calls fsync after every disk write and calculates a checksum for every database page it writes or reads, which will reveal disk defects.
      • Several bug fixes.

      7.5.15 InnoDB Contact Information

      Contact information of Innobase Oy, producer of the InnoDB engine. Web site: http://www.innodb.com/. E-mail: Heikki.Tuuri@innodb.com 

      phone: 358-9-6969 3250 (office) 358-40-5617367 (mobile)
Innobase Oy Inc.
World Trade Center Helsinki
Aleksanterinkatu 17
P.O.Box 800
00101 Helsinki
Finland

      7.6 BDB or BerkeleyDB Tables

      7.6.1 Overview of BDB Tables

      BerkeleyDB, available at http://www.sleepycat.com/ has provided MySQL with a transactional storage engine. Support for this storage engine is included in the MySQL source distribution starting from version 3.23.34 and is activated in the MySQL-Max binary. This storage engine is typically called BDB for short.

      BDB tables may have a greater chance of surviving crashes and are also capable of COMMIT and ROLLBACK operations on transactions. The MySQL source distribution comes with a BDB distribution that has a couple of small patches to make it work more smoothly with MySQL. You can't use a non-patched BDB version with MySQL.

      We at MySQL AB are working in close cooperation with Sleepycat to keep the quality of the MySQL/BDB interface high.

      When it comes to supporting BDB tables, we are committed to help our users to locate the problem and help creating a reproducible test case for any problems involving BDB tables. Any such test case will be forwarded to Sleepycat who in turn will help us find and fix the problem. As this is a two-stage operation, any problems with BDB tables may take a little longer for us to fix than for other storage engines. However, as the BerkeleyDB code itself has been used by many other applications than MySQL, we don't envision any big problems with this. 「1.4.1 Support Offered by MySQL AB」節参照.

      7.6.2 Installing BDB

      If you have downloaded a binary version of MySQL that includes support for BerkeleyDB, simply follow the instructions for installing a binary version of MySQL. 「2.2.10 Installing a MySQL Binary Distribution」節参照. 「4.7.5 mysqld-max, An Extended mysqld Server」節参照.

      To compile MySQL with Berkeley DB support, download MySQL Version 3.23.34 or newer and configure MySQL with the --with-berkeley-db option. 「2.3 MySQL ソースディストリビューションのインストール」節参照. 

      cd /path/to/source/of/mysql-3.23.34
./configure --with-berkeley-db

      Please refer to the manual provided with the BDB distribution for more updated information.

      Even though Berkeley DB is in itself very tested and reliable, the MySQL interface is still considered beta quality. We are actively improving and optimising it to get it stable very soon.

      7.6.3 BDB startup options

      If you are running with AUTOCOMMIT=0 then your changes in BDB tables will not be updated until you execute COMMIT. Instead of commit you can execute ROLLBACK to forget your changes. 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照.

      If you are running with AUTOCOMMIT=1 (the default), your changes will be committed immediately. You can start an extended transaction with the BEGIN WORK SQL command, after which your changes will not be committed until you execute COMMIT (or decide to ROLLBACK the changes).

      The following options to mysqld can be used to change the behaviour of BDB tables:

      Option Description
      --bdb-home=directory Base directory for BDB tables. This should be the same directory you use for --datadir.
      --bdb-lock-detect=# Berkeley lock detect. One of (DEFAULT, OLDEST, RANDOM, or YOUNGEST).
      --bdb-logdir=directory Berkeley DB log file directory.
      --bdb-no-sync Don't synchronously flush logs.
      --bdb-no-recover Don't start Berkeley DB in recover mode.
      --bdb-shared-data Start Berkeley DB in multi-process mode (Don't use DB_PRIVATE when initialising Berkeley DB)
      --bdb-tmpdir=directory Berkeley DB temporary file directory.
      --skip-bdb Disable usage of BDB tables.
      -O bdb_max_lock=1000 Set the maximum number of locks possible. 「4.5.6.4 SHOW VARIABLES」節参照.

      If you use --skip-bdb, MySQL will not initialise the Berkeley DB library and this will save a lot of memory. Of course, you cannot use BDB tables if you are using this option. If you try to create a BDB table, MySQL will instead create a MyISAM table.

      Normally you should start mysqld without --bdb-no-recover if you intend to use BDB tables. This may, however, give you problems when you try to start mysqld if the BDB log files are corrupted. 「2.4.2 MySQL サーバー起動時の問題」節参照.

      With bdb_max_lock you can specify the maximum number of locks (10000 by default) you can have active on a BDB table. You should increase this if you get errors of type bdb: Lock table is out of available locks or Got error 12 from ... when you have do long transactions or when mysqld has to examine a lot of rows to calculate the query.

      You may also want to change binlog_cache_size and max_binlog_cache_size if you are using big multi-line transactions. 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照.

      7.6.4 Characteristics of BDB tables:

      • To be able to rollback transactions, the BDB storage engine maintains log files. For maximum performance you should place these on another disk than your databases by using the --bdb-logdir option.
      • MySQL performs a checkpoint each time a new BDB log file is started, and removes any log files that are not needed for current transactions. One can also run FLUSH LOGS at any time to checkpoint the Berkeley DB tables. For disaster recovery, one should use table backups plus MySQL's binary log. 「4.4.1 データベースのバックアップ」節参照. Warning: If you delete old log files that are in use, BDB will not be able to do recovery at all and you may lose data if something goes wrong.
      • MySQL requires a PRIMARY KEY in each BDB table to be able to refer to previously read rows. If you don't create one, MySQL will create an maintain a hidden PRIMARY KEY for you. The hidden key has a length of 5 bytes and is incremented for each insert attempt.
      • If all columns you access in a BDB table are part of the same index or part of the primary key, then MySQL can execute the query without having to access the actual row. In a MyISAM table the above holds only if the columns are part of the same index.
      • The PRIMARY KEY will be faster than any other key, as the PRIMARY KEY is stored together with the row data. As the other keys are stored as the key data + the PRIMARY KEY, it's important to keep the PRIMARY KEY as short as possible to save disk and get better speed.
      • LOCK TABLES works on BDB tables as with other tables. If you don't use LOCK TABLE, MySQL will issue an internal multiple-write lock on the table to ensure that the table will be properly locked if another thread issues a table lock.
      • Internal locking in BDB tables is done on page level.
      • SELECT COUNT(*) FROM table_name is slow as BDB tables doesn't maintain a count of the number of rows in the table.
      • Sequential scanning is slower than with MyISAM tables as the data in BDB tables stored in B-trees and not in a separate datafile.
      • The application must always be prepared to handle cases where any change of a BDB table may make an automatic rollback and any read may fail with a deadlock error.
      • Keys are not prefix or suffix-compressed like keys in MyISAM tables. In other words, the key information will take a little more space in BDB tables compared to MyISAM tables.
      • There are often holes in the BDB table to allow you to insert new rows in the middle of the key tree. This makes BDB tables somewhat larger than MyISAM tables.
      • The optimiser needs to know an approximation of the number of rows in the table. MySQL solves this by counting inserts and maintaining this in a separate segment in each BDB table. If you don't issue a lot of DELETE or ROLLBACK statements, this number should be accurate enough for the MySQL optimiser, but as MySQL only stores the number on close, it may be incorrect if MySQL dies unexpectedly. It should not be fatal even if this number is not 100% correct. One can update the number of rows by executing ANALYZE TABLE or OPTIMIZE TABLE. 「4.5.2 ANALYZE TABLE Syntax」節参照 . 「4.5.1 OPTIMIZE TABLE 構文」節参照.
      • If you get full disk with a BDB table, you will get an error (probably error 28) and the transaction should roll back. This is in contrast with MyISAM and ISAM tables where mysqld will wait for enough free disk before continuing.

      7.6.5 Things we need to fix for BDB in the near future:

      • It's very slow to open many BDB tables at the same time. If you are going to use BDB tables, you should not have a very big table cache (like >256) and you should use --no-auto-rehash with the mysql client. We plan to partly fix this in 4.0.
      • SHOW TABLE STATUS doesn't yet provide that much information for BDB tables.
      • Optimise performance.
      • Change to not use page locks at all when we are scanning tables.

      7.6.6 Operating systems supported by BDB

      Currently we know that the BDB storage engine works with the following operating systems:

      • Linux 2.x Intel
      • Solaris SPARC
      • Caldera (SCO) OpenServer
      • Caldera (SCO) UnixWare 7.0.1

      It doesn't work with the following operating systems:

      • Linux 2.x Alpha
      • Max OS X

      Note: The above list is not complete; we will update it as we receive more information.

      If you build MySQL with support for BDB tables and get the following error in the log file when you start mysqld: 

      bdb: architecture lacks fast mutexes: applications cannot be threaded
Can't init dtabases

      This means that BDB tables are not supported for your architecture. In this case you must rebuild MySQL without BDB table support.

      7.6.7 Restrictions on BDB Tables

      Here follows the restrictions you have when using BDB tables:

      • BDB tables store in the `.db' file the path to the file as it was created. (This was done to be able to detect locks in a multi-user environment that supports symlinks). The effect of this is that BDB tables are not movable between directories!
      • When taking backups of BDB tables, you have to either use mysqldump or take a backup of all table_name.db files and the BDB log files. The BDB log files are the files in the base data directory named log.XXXXXXXXXX (ten digits); The BDB storage engine stores unfinished transactions in the log files and requires these logs to be present when mysqld starts.

      7.6.8 Errors That May Occur When Using BDB Tables

      • If you get the following error in the hostname.err log when starting mysqld: 
        bdb:  Ignoring log file: .../log.XXXXXXXXXX: unsupported log version #
        it means that the new BDB version doesn't support the old log file format. In this case you have to delete all BDB logs from your database directory (the files with names that have the format log.XXXXXXXXXX) and restart mysqld. We would also recommend you to do a mysqldump --opt of your old BDB tables, delete the old tables, and restore the dump.
      • If you are not running in auto-commit mode and delete a table that is referenced in another transaction, you may get the following error messages in your MySQL error log: 
        001119 23:43:56  bdb:  Missing log fileid entry
001119 23:43:56  bdb:  txn_abort: Log undo failed for LSN:
                       1 3644744: Invalid
        This is not fatal but we don't recommend that you delete tables if you are not in auto-commit mode, until this problem is fixed (the fix is not trivial).

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_Tutorial.html0100644000175100001560000026641710021471264016275 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 3 Tutorial Introduction Go to the first, previous, next, last section, table of contents.

      3 Tutorial Introduction

      この章では、 mysql クライアントプログラムの使用の仕方と 単純なデータベースの作成と使用の仕方を例題としてとり上げます。 mysql (``terminal monitor'' や ``monitor'' として参照されます)は MySQL サーバーに接続できる対話モードのプログラムで、 クエリの実行や結果の表示が可能です。 mysql はバッチモードも可能です： クエリをまずファイルに書いておき、 そしてそのファイルを mysql に実行させます。 どちらの方法でも mysql はこの章の説明でカバーされます。

      mysql の提供するオプションを見るには、 --help オプションを 実行します： 

      shell> mysql --help

      この章では mysql が既にあなたのマシンにインストールされているものとし、 また MySQL サーバーに接続可能であるとします。 もしそうでないなら、 あなたの MySQL 管理者に連絡を取ってください。 (もしあなた自身が管理者なら、このマニュアルの他のセクションを参照してください。)

      本章ではデータベース設定の全体のプロセス、データベースの使用について述べます。 もしあなたが既に存在しているデータベースにアクセスする事だけに興味があるなら、 この章のデータベース、テーブルの作成方法の説明を読み飛ばしてもかまいません。

      この章が本質的にはチュートリアルであるので、多くの詳細は、かならず違う章にあります。 ここに書かれている事柄で、 さらに詳しい情報についてはマニュアルの適切なセクションを調べて下さい。

      3.1 サーバーへの接続と切断

      サーバーに mysql コマンドから接続するためには、通常、 MySQL ユーザ名、パスワードを指定する必要があるでしょう。 もしあなたがログインしている以外のマシンの上でサーバーが走っていれば、 あなたは、ホスト名を明示する必要があるでしょう。 まずあなたの管理者に問い合わせて、あなたが使うべき接続のためのパラメーターを見つけ出して下さい。 (すなわち、どのようなホスト、ユーザー名とパスワードを使うべきなのか。) 適切なパラメーターを知っていれば、あなたは、以下のようにして接続できます： 

      shell> mysql -h host -u user -p
Enter password: ********

      ******** とかかれている部分にはあなたのパスワードを入れます； mysql が Enter password: プロンプトを出したときに。

      きちんと動けば、いくつかの情報と mysql> プロンプトが現れます： 

      shell> mysql -h host -u user -p
Enter password: ********
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 459 to server version: 3.22.20a-log

Type 'help' for help.

mysql>

      このプロンプトは mysql がコマンド入力を待っている状態を示します。

      いくつかの MySQL インストレーションでは、ローカルホストで 実行されているサーバーに、ユーザーに``匿名''(名前無し)の接続を許しています。 もしあなたのマシンがこの場合に当てはまるなら、mysql をオプション無しで 起動すべきです： 

      shell> mysql

      接続が成功した後、 mysql> プロンプトで、QUIT とタイプすれば いつでも接続を切ることができます： 

      mysql> QUIT
Bye

      Control-D で切断してもかまいません。

      以下のセクションでのほとんどの例では、あなたがサーバーに接続しているものと しています。その場合は mysql> プロンプトによって、それを示しています。

      3.2 Entering Queries

      前のセクションで述べたように、あなたがサーバーとつながっていることを確かめて下さい。 この状態ではまだどんなデータベースも選択していない状態です。しかしそれはかまいません。 ここでは、テーブルの作成やデータの入力、取り出しよりも、 いかにクエリを発行するかに重点を置きます。 このセクションでは、あなた自身を mysql の動きに慣れさせるために、 あなたがやってみることができるであろう、いくつかのクエリを使用して、 コマンド入力の基本的な原則を述べます。

      サーバーのバージョン、今日の日付をサーバーに問い合わせる、単純なコマンド がここにあります。 以下のように mysql> プロンプトの後に入力し RETURN キーを押してみてください： 

      mysql> SELECT VERSION(), CURRENT_DATE;
+--------------+--------------+
| VERSION()    | CURRENT_DATE |
+--------------+--------------+
| 3.22.20a-log | 1999-03-19   |
+--------------+--------------+
1 row in set (0.01 sec)
mysql>

      このクエリは、mysql のいくつかの事を説明しています：

      • 通常、コマンドは、セミコロンで終わる SQL ステートメントから、構成されます。 (セミコロンが必要とされないいくつかの例外があります。 以前に述べた QUIT はそのうちの一つです。後で他も出てきます。)
      • コマンドを発行すると、mysql はそれをサーバーに送り、結果を表示します。 その後、 mysql> プロンプトを出し、他のコマンドが受け付けれる状態であると 示します。
      • mysql はクエリの結果を表にして出します。 最初の行は項目のラベル名です。 その下の行に、クエリの結果が続きます。 通常、項目のラベル名はデータベースのテーブルから あなたが取り出したフィールド名になります。 テーブルのフィールド名以外の式を あなたが検索したのなら(ちょうど例のように)、mysql は与えられた式自身を 項目のラベル名として表示します。
      • mysql は何レコード(rows)返ってきたかを示し、実行にどれくらいの時間が かかったかも示します。 これはおおざっぱなサーバーのパフォーマンスを示します。 これらの値は wall clock time (CPU や マシンタイムではなく) を使用しており、さらに、 サーバーの負荷、およびネットワーク待ち時間といった要因にも影響されるので、 不正確です。 (この章の他の例題においては ``rows in set'' の行は省きます。)

      キーワードは、いかなる大文字小文字でも記述できます。 以下に示すクエリは同じです： 

      mysql> SELECT VERSION(), CURRENT_DATE;
mysql> select version(), current_date;
mysql> SeLeCt vErSiOn(), current_DATE;

      以下のクエリは、mysql を簡単な計算機として使用した例です： 

      mysql> SELECT SIN(PI()/4), (4+1)*5;
+-------------+---------+
| SIN(PI()/4) | (4+1)*5 |
+-------------+---------+
|    0.707107 |      25 |
+-------------+---------+

      今までは見てきたたコマンドは、比較的短い、一行のの文です。 あなたは一行に複数、文を書くことが出来ます。 それぞれの文の終わりにはセミコロンを付けます： 

      mysql> SELECT VERSION(); SELECT NOW();
+--------------+
| VERSION()    |
+--------------+
| 3.22.20a-log |
+--------------+

+---------------------+
| NOW()               |
+---------------------+
| 1999-03-19 00:15:33 |
+---------------------+

      コマンドは一行にかく必要もありません。 複数行にわたる長いコマンドでも問題ありません。 mysql はセミコロンで、一文の終わりと見なします。 その行の最後を文の最後とは 見なしません。 （いうなれば、mysql は自由な入力を許し、セミコロンが現れるまでは それらの入力された行を実行しません）

      複数行にまたがった文の例です： 

      mysql> SELECT
    -> USER()
    -> ,
    -> CURRENT_DATE;
+--------------------+--------------+
| USER()             | CURRENT_DATE |
+--------------------+--------------+
| joesmith@localhost | 1999-03-18   |
+--------------------+--------------+

      この例では、複数にまたがるクエリにおいて、最初の行の入力のあと、 いかにプロンプトが mysql> から -> に変わるかを示しています。 これは mysql が、まだ文が終わっておらず、残りの部分の入力を待っている ことを示します。プロンプトは役立つフィードバックを提供してくれるあなたの友 人です。そのフィードバックを使用すると、mysql が何を待っているのか にいつも気が付くでしょう。

      入力中にコマンドの実行を取りやめようと思った場合、 \c でこれをキャンセルできます： 

      mysql> SELECT
    -> USER()
    -> \c
mysql>

      ここでもプロンプトに注意してください。\c のタイプ後に mysql> に戻っています。mysql が新しいコマンドの準備ができた ことを示すフィードバックを提供しています。

      次のテーブルはあなたが目にするであろう各プロンプトと、それらが意味する mysql がどの状態にあるかについての要約です:

      プロンプト 意味
      mysql> 新しいコマンドの待状態
      -> 複数行にまたがるコマンドの、次の行の入力を待っている状態。
      '> シングルクオート (`'') で始められた文字の、次の行の入力を待っている状態。
      "> ダブルクオート (`"') で始められた文字の、次の行の入力を待っている状態。

      あなたが文をセミコロンで終わらすことを忘れて実行した場合に、 複数行の入力待ちが起こります。 この場合、 mysql は 次の入力を待ちます： 

      mysql> SELECT USER()
    ->

      If this happens to you (you think you've entered a statement but the only response is a -> prompt), most likely mysql is waiting for the semicolon. If you don't notice what the prompt is telling you, you might sit there for a while before realising what you need to do. Enter a semicolon to complete the statement, and mysql will execute it: 

      mysql> SELECT USER()
    -> ;
+--------------------+
| USER()             |
+--------------------+
| joesmith@localhost |
+--------------------+

      The '> and "> prompts occur during string collection. In MySQL, you can write strings surrounded by either `'' or `"' characters (for example, 'hello' or "goodbye"), and mysql lets you enter strings that span multiple lines. When you see a '> or "> prompt, it means that you've entered a line containing a string that begins with a `'' or `"' quote character, but have not yet entered the matching quote that terminates the string. That's fine if you really are entering a multiple-line string, but how likely is that? Not very. More often, the '> and "> prompts indicate that you've inadvertantly left out a quote character. For example: 

      mysql> SELECT * FROM my_table WHERE name = "Smith AND age < 30;
    ">

      If you enter this SELECT statement, then press Enter and wait for the result, nothing will happen. Instead of wondering why this query takes so long, notice the clue provided by the "> prompt. It tells you that mysql expects to see the rest of an unterminated string. (Do you see the error in the statement? The string "Smith is missing the second quote.)

      At this point, what do you do? The simplest thing is to cancel the command. However, you cannot just type \c in this case, because mysql interprets it as part of the string that it is collecting! Instead, enter the closing quote character (so mysql knows you've finished the string), then type \c: 

      mysql> SELECT * FROM my_table WHERE name = "Smith AND age < 30;
    "> "\c
mysql>

      The prompt changes back to mysql>, indicating that mysql is ready for a new command.

      It's important to know what the '> and "> prompts signify, because if you mistakenly enter an unterminated string, any further lines you type will appear to be ignored by mysql@-including a line containing QUIT! This can be quite confusing, especially if you don't know that you need to supply the terminating quote before you can cancel the current command.

      3.3 Creating and Using a Database

      Now that you know how to enter commands, it's time to access a database.

      Suppose you have several pets in your home (your menagerie) and you'd like to keep track of various types of information about them. You can do so by creating tables to hold your data and loading them with the desired information. Then you can answer different sorts of questions about your animals by retrieving data from the tables. This section shows you how to:

      • Create a database
      • Create a table
      • Load data into the table
      • Retrieve data from the table in various ways
      • Use multiple tables

      The menagerie database will be simple (deliberately), but it is not difficult to think of real-world situations in which a similar type of database might be used. For example, a database like this could be used by a farmer to keep track of livestock, or by a veterinarian to keep track of patient records. A menagerie distribution containing some of the queries and sample data used in the following sections can be obtained from the MySQL web site. It's available in either compressed tar format (http://www.mysql.com/Downloads/Contrib/Examples/menagerie.tar.gz) or Zip format (http://www.mysql.com/Downloads/Contrib/Examples/menagerie.zip).

      Use the SHOW statement to find out what databases currently exist on the server: 

      mysql> SHOW DATABASES;
+----------+
| Database |
+----------+
| mysql    |
| test     |
| tmp      |
+----------+

      The list of databases is probably different on your machine, but the mysql and test databases are likely to be among them. The mysql database is required because it describes user access privileges. The test database is often provided as a workspace for users to try things out.

      Note that you may not see all databases if you don't have the SHOW DATABASES privilege. 「4.3.1 GRANT と REVOKE 構文」節参照.

      If the test database exists, try to access it: 

      mysql> USE test
Database changed

      Note that USE, like QUIT, does not require a semicolon. (You can terminate such statements with a semicolon if you like; it does no harm.) The USE statement is special in another way, too: it must be given on a single line.

      You can use the test database (if you have access to it) for the examples that follow, but anything you create in that database can be removed by anyone else with access to it. For this reason, you should probably ask your MySQL administrator for permission to use a database of your own. Suppose you want to call yours menagerie. The administrator needs to execute a command like this: 

      mysql> GRANT ALL ON menagerie.* TO your_mysql_name;

      where your_mysql_name is the MySQL user name assigned to you.

      3.3.1 Creating and Selecting a Database

      If the administrator creates your database for you when setting up your permissions, you can begin using it. Otherwise, you need to create it yourself: 

      mysql> CREATE DATABASE menagerie;

      Under Unix, database names are case-sensitive (unlike SQL keywords), so you must always refer to your database as menagerie, not as Menagerie, MENAGERIE, or some other variant. This is also true for table names. (Under Windows, this restriction does not apply, although you must refer to databases and tables using the same lettercase throughout a given query.)

      Creating a database does not select it for use; you must do that explicitly. To make menagerie the current database, use this command: 

      mysql> USE menagerie
Database changed

      Your database needs to be created only once, but you must select it for use each time you begin a mysql session. You can do this by issuing a USE statement as shown above. Alternatively, you can select the database on the command-line when you invoke mysql. Just specify its name after any connection parameters that you might need to provide. For example: 

      shell> mysql -h host -u user -p menagerie
Enter password: ********

      Note that menagerie is not your password on the command just shown. If you want to supply your password on the command-line after the -p option, you must do so with no intervening space (for example, as -pmypassword, not as -p mypassword). However, putting your password on the command-line is not recommended, because doing so exposes it to snooping by other users logged in on your machine.

      3.3.2 テーブルの作成

      データベースを作成することは容易ですが、作成しただけでは中身はからっぽです。 例えば SHOW TABLES を実行してみると以下のようになるでしょう: 

      mysql> SHOW TABLES;
Empty set (0.00 sec)

      難しいのはデータベースの構造をどうするかを決定することです。 どんなテーブルが必要で、その中にどんな要素を入れるかです。

      まずそれぞれのペットに関するレコードを含んだテーブルが必要でしょう。 これは pet テーブルとしましょう。 そしてその中には、最低でもそれぞれの動物の名前は入れる必要があるでしょう。 名前だけではあまり面白くないのでその他の情報も入れることにしましょう。例えば、もし家族の２人以上がペットを買っているならば、飼い主の名前も入れたくなるでしょう。 またその他にもペットの種類や性別など、いくつかの基本的な情報も入れたくなるかもしれません。

      年齢はどうでしょうか？ 確かにいいかもしれませんが、データベースに蓄積するにはあまり良くないものです。 年齢は時とともに変化します。つまりその都度レコードを更新する必要があるということです。 これに代わるデータとして適切なのは、例えば誕生日です。 そうしておいて年齢が必要なときは今日の日付と誕生日から計算すればよいのです。 MySQL には日付を算術演算する関数がありますので、難しいことはありません。 年齢ではなくて誕生日を記録しておくことには他のメリットもあります。

      • ペットの誕生日が近づいてきたことを知らせてくれる目的にもこのデータベースは使えることになります。 （下らないと思う人は、仕事上の付き合いの関係で、 顧客データベースから誕生日のお祝いメッセージを送らないといけない顧客を割り出す仕事を想定してみてください。）
      • 今日の日付以外に、関係する日付からも年齢の計算が出来ます。 例えば、もしペットが死亡した日をデータベースに入れておけば、 そのペットが何歳で死んだのかも簡単に計算することが出来ます。

      その他にも pet テーブルに加えるべき有用な情報はいろいろあるでしょう。 しかしとりあえずはこの辺で十分としましょう。名前、飼い主、種類、性別、誕生日、そして死亡日です。

      CREATE TABLE 文を使ってテーブルのレイアウトを指定しましょう： 

      mysql> CREATE TABLE pet (name VARCHAR(20), owner VARCHAR(20),
    -> species VARCHAR(20), sex CHAR(1), birth DATE, death DATE);

      name, owner,そしてspecies フィールドには VARCHAR を用いた方がよいでしょう。なぜならこれらの値の長さは変化するからです。 これらのフィールドの長さは全て同じである必要もなく、20文字である必要もありません。 1から255の間でもっともリーズナブルな値を選べばよいでしょう。 （長さの選択を誤ってあとで文字数が足らなくなったとしても、 MySQLは ALTER TABLE で長さを変えることができます）

      動物の性別を表す値にはいくつかのタイプが考えられます。 "m" と "f" 、あるいは"male" と "female" なども考えられるでしょう。 ここでは最も簡単に、一文字の "m" と "f" で表すことにしましょう。

      birth と death のフィールドには、明らかに DATE データ型を用いるべきでしょう。

      テーブルを作ってみると、SHOW TABLES で何らかの出力が得られるはずです： 

      mysql> SHOW TABLES;
+---------------------+
| Tables in menagerie |
+---------------------+
| pet                 |
+---------------------+

      テーブルが期待したとおりに作成されたかどうかをチェックするために、 DESCRIBE 文を使います： 

      mysql> DESCRIBE pet;
+---------+-------------+------+-----+---------+-------+
| Field   | Type        | Null | Key | Default | Extra |
+---------+-------------+------+-----+---------+-------+
| name    | varchar(20) | YES  |     | NULL    |       |
| owner   | varchar(20) | YES  |     | NULL    |       |
| species | varchar(20) | YES  |     | NULL    |       |
| sex     | char(1)     | YES  |     | NULL    |       |
| birth   | date        | YES  |     | NULL    |       |
| death   | date        | YES  |     | NULL    |       |
+---------+-------------+------+-----+---------+-------+

      DESCRIBE 文はいつでも、 例えばテーブルの列の名前やそのタイプを忘れてしまったときにも使うことが出来ます。

      3.3.3 ファイルからデータをテーブルへ取り込む

      テーブルを作ったら、中にデータを入れる必要があります。 このとき LOAD DATA 文とINSERT 文を用いると便利です。

      例えばあなたのペットに関する記録が以下のようになっていたとします。 （MySQLにおける日付の表記が 'YYYY-MM-DD' の形式になっていることに注意してください。 あなたが慣れている形式とは異なるかもしれません）

      name owner species sex birth death
      Fluffy Harold cat f 1993-02-04
      Claws Gwen cat m 1994-03-17
      Buffy Harold dog f 1989-05-13
      Fang Benny dog m 1990-08-27
      Bowser Diane dog m 1998-08-31 1995-07-29
      Chirpy Gwen bird f 1998-09-11
      Whistler Gwen bird 1997-12-09
      Slim Benny snake m 1996-04-29

      もし空のテーブルから作り始めるのなら、 一行に一つのペットのデータを記述したテキストファイルを作っておいて、 先に挙げた命令で中身を読み込ませると楽です。

      そのファイルを `pet.txt' とします。 各レコードを一行ずつ書き、各項目はタブで区切ります。 項目の順番は CREATE TABLE 文で定義したときと同じ順番とします。 項目が空のときは（例えばペットがまだ生きている場合、死亡日欄は空白です） NULL を用いることが出来ます。ファイル中では \N を用います。 例えば鳥の Whistler のレコードは以下のようになります。（項目の間の空白はタブ１個です）:

      name owner species sex birth death
      Whistler Gwen bird \N 1997-12-09 \N

      このファイル `pet.txt' をテーブル pet に読み込むには、以下のコマンドを用います： 

      mysql> LOAD DATA LOCAL INFILE "pet.txt" INTO TABLE pet;

      もし必要であれば、項目の区切りや行末の符号を LOAD DATA 文で明示的に定めることが出来ます。 デフォルトでは区切りはタブ、行末はラインフィードです。 これにより `pet.txt' を適切に読み込むことが出来ます。

      また新しい複数のレコードを１個づつ追加したいときは INSERT が便利です。 それぞれの項を CREATE TABLE で定義したときと同じ順番で入力するだけで追加できます。 例えばDianeが新しくハムスターをもらってきてPuffballと名づけました。 INSERT を用いて以下のようにレコードを追加することが出来ます： 

      mysql> INSERT INTO pet
    -> VALUES ('Puffball','Diane','hamster','f','1999-03-30',NULL);

      文字列や日付を引用符号で括っていることに注意してください。 また INSERT を用いて空白の項を入力するときには NULL を直接挿入することができます。 LOAD DATA を使っているときとは違って \N は使えません。

      この例から、初めにレコードを INSERT 文で入力するのは、 LOAD DATA 文を用いるよりも相当多くのタイピングを要してしまうことがわかると思います。

      3.3.4 Retrieving Information from a Table

      The SELECT statement is used to pull information from a table. The general form of the statement is: 

      SELECT what_to_select
FROM which_table
WHERE conditions_to_satisfy

      what_to_select indicates what you want to see. This can be a list of columns, or * to indicate ``all columns.'' which_table indicates the table from which you want to retrieve data. The WHERE clause is optional. If it's present, conditions_to_satisfy specifies conditions that rows must satisfy to qualify for retrieval.

      3.3.4.1 Selecting All Data

      The simplest form of SELECT retrieves everything from a table: 

      mysql> SELECT * FROM pet;
+----------+--------+---------+------+------------+------------+
| name     | owner  | species | sex  | birth      | death      |
+----------+--------+---------+------+------------+------------+
| Fluffy   | Harold | cat     | f    | 1993-02-04 | NULL       |
| Claws    | Gwen   | cat     | m    | 1994-03-17 | NULL       |
| Buffy    | Harold | dog     | f    | 1989-05-13 | NULL       |
| Fang     | Benny  | dog     | m    | 1990-08-27 | NULL       |
| Bowser   | Diane  | dog     | m    | 1998-08-31 | 1995-07-29 |
| Chirpy   | Gwen   | bird    | f    | 1998-09-11 | NULL       |
| Whistler | Gwen   | bird    | NULL | 1997-12-09 | NULL       |
| Slim     | Benny  | snake   | m    | 1996-04-29 | NULL       |
| Puffball | Diane  | hamster | f    | 1999-03-30 | NULL       |
+----------+--------+---------+------+------------+------------+

      This form of SELECT is useful if you want to review your entire table, for instance, after you've just loaded it with your initial dataset. As it happens, the output just shown reveals an error in your datafile: Bowser appears to have been born after he died! Consulting your original pedigree papers, you find that the correct birth year is 1989, not 1998.

      There are least a couple of ways to fix this:

      • Edit the file `pet.txt' to correct the error, then empty the table and reload it using DELETE and LOAD DATA: 
        mysql> SET AUTOCOMMIT=1;  # Used for quick re-create of the table
mysql> DELETE FROM pet;
mysql> LOAD DATA LOCAL INFILE "pet.txt" INTO TABLE pet;
        However, if you do this, you must also re-enter the record for Puffball.
      • Fix only the erroneous record with an UPDATE statement: 
        mysql> UPDATE pet SET birth = "1989-08-31" WHERE name = "Bowser";

      As shown above, it is easy to retrieve an entire table. But typically you don't want to do that, particularly when the table becomes large. Instead, you're usually more interested in answering a particular question, in which case you specify some constraints on the information you want. Let's look at some selection queries in terms of questions about your pets that they answer.

      3.3.4.2 Selecting Particular Rows

      You can select only particular rows from your table. For example, if you want to verify the change that you made to Bowser's birth date, select Bowser's record like this: 

      mysql> SELECT * FROM pet WHERE name = "Bowser";
+--------+-------+---------+------+------------+------------+
| name   | owner | species | sex  | birth      | death      |
+--------+-------+---------+------+------------+------------+
| Bowser | Diane | dog     | m    | 1989-08-31 | 1995-07-29 |
+--------+-------+---------+------+------------+------------+

      The output confirms that the year is correctly recorded now as 1989, not 1998.

      String comparisons are normally case-insensitive, so you can specify the name as "bowser", "BOWSER", etc. The query result will be the same.

      You can specify conditions on any column, not just name. For example, if you want to know which animals were born after 1998, test the birth column: 

      mysql> SELECT * FROM pet WHERE birth >= "1998-1-1";
+----------+-------+---------+------+------------+-------+
| name     | owner | species | sex  | birth      | death |
+----------+-------+---------+------+------------+-------+
| Chirpy   | Gwen  | bird    | f    | 1998-09-11 | NULL  |
| Puffball | Diane | hamster | f    | 1999-03-30 | NULL  |
+----------+-------+---------+------+------------+-------+

      You can combine conditions, for example, to locate female dogs: 

      mysql> SELECT * FROM pet WHERE species = "dog" AND sex = "f";
+-------+--------+---------+------+------------+-------+
| name  | owner  | species | sex  | birth      | death |
+-------+--------+---------+------+------------+-------+
| Buffy | Harold | dog     | f    | 1989-05-13 | NULL  |
+-------+--------+---------+------+------------+-------+

      The preceding query uses the AND logical operator. There is also an OR operator: 

      mysql> SELECT * FROM pet WHERE species = "snake" OR species = "bird";
+----------+-------+---------+------+------------+-------+
| name     | owner | species | sex  | birth      | death |
+----------+-------+---------+------+------------+-------+
| Chirpy   | Gwen  | bird    | f    | 1998-09-11 | NULL  |
| Whistler | Gwen  | bird    | NULL | 1997-12-09 | NULL  |
| Slim     | Benny | snake   | m    | 1996-04-29 | NULL  |
+----------+-------+---------+------+------------+-------+

      AND and OR may be intermixed. If you do that, it's a good idea to use parentheses to indicate how conditions should be grouped: 

      mysql> SELECT * FROM pet WHERE (species = "cat" AND sex = "m")
    -> OR (species = "dog" AND sex = "f");
+-------+--------+---------+------+------------+-------+
| name  | owner  | species | sex  | birth      | death |
+-------+--------+---------+------+------------+-------+
| Claws | Gwen   | cat     | m    | 1994-03-17 | NULL  |
| Buffy | Harold | dog     | f    | 1989-05-13 | NULL  |
+-------+--------+---------+------+------------+-------+

      3.3.4.3 Selecting Particular Columns

      If you don't want to see entire rows from your table, just name the columns in which you're interested, separated by commas. For example, if you want to know when your animals were born, select the name and birth columns: 

      mysql> SELECT name, birth FROM pet;
+----------+------------+
| name     | birth      |
+----------+------------+
| Fluffy   | 1993-02-04 |
| Claws    | 1994-03-17 |
| Buffy    | 1989-05-13 |
| Fang     | 1990-08-27 |
| Bowser   | 1989-08-31 |
| Chirpy   | 1998-09-11 |
| Whistler | 1997-12-09 |
| Slim     | 1996-04-29 |
| Puffball | 1999-03-30 |
+----------+------------+

      To find out who owns pets, use this query: 

      mysql> SELECT owner FROM pet;
+--------+
| owner  |
+--------+
| Harold |
| Gwen   |
| Harold |
| Benny  |
| Diane  |
| Gwen   |
| Gwen   |
| Benny  |
| Diane  |
+--------+

      However, notice that the query simply retrieves the owner field from each record, and some of them appear more than once. To minimise the output, retrieve each unique output record just once by adding the keyword DISTINCT: 

      mysql> SELECT DISTINCT owner FROM pet;
+--------+
| owner  |
+--------+
| Benny  |
| Diane  |
| Gwen   |
| Harold |
+--------+

      You can use a WHERE clause to combine row selection with column selection. For example, to get birth dates for dogs and cats only, use this query: 

      mysql> SELECT name, species, birth FROM pet
    -> WHERE species = "dog" OR species = "cat";
+--------+---------+------------+
| name   | species | birth      |
+--------+---------+------------+
| Fluffy | cat     | 1993-02-04 |
| Claws  | cat     | 1994-03-17 |
| Buffy  | dog     | 1989-05-13 |
| Fang   | dog     | 1990-08-27 |
| Bowser | dog     | 1989-08-31 |
+--------+---------+------------+

      3.3.4.4 Sorting Rows

      You may have noticed in the preceding examples that the result rows are displayed in no particular order. However, it's often easier to examine query output when the rows are sorted in some meaningful way. To sort a result, use an ORDER BY clause.

      Here are animal birthdays, sorted by date: 

      mysql> SELECT name, birth FROM pet ORDER BY birth;
+----------+------------+
| name     | birth      |
+----------+------------+
| Buffy    | 1989-05-13 |
| Bowser   | 1989-08-31 |
| Fang     | 1990-08-27 |
| Fluffy   | 1993-02-04 |
| Claws    | 1994-03-17 |
| Slim     | 1996-04-29 |
| Whistler | 1997-12-09 |
| Chirpy   | 1998-09-11 |
| Puffball | 1999-03-30 |
+----------+------------+

      On character type columns, sorting@-like all other comparison operations@-is normally performed in a case-insensitive fashion. This means that the order will be undefined for columns that are identical except for their case. You can force a case-sensitive sort by using the BINARY cast: ORDER BY BINARY(field).

      To sort in reverse order, add the DESC (descending) keyword to the name of the column you are sorting by: 

      mysql> SELECT name, birth FROM pet ORDER BY birth DESC;
+----------+------------+
| name     | birth      |
+----------+------------+
| Puffball | 1999-03-30 |
| Chirpy   | 1998-09-11 |
| Whistler | 1997-12-09 |
| Slim     | 1996-04-29 |
| Claws    | 1994-03-17 |
| Fluffy   | 1993-02-04 |
| Fang     | 1990-08-27 |
| Bowser   | 1989-08-31 |
| Buffy    | 1989-05-13 |
+----------+------------+

      You can sort on multiple columns. For example, to sort by type of animal, then by birth date within animal type with youngest animals first, use the following query: 

      mysql> SELECT name, species, birth FROM pet ORDER BY species, birth DESC;
+----------+---------+------------+
| name     | species | birth      |
+----------+---------+------------+
| Chirpy   | bird    | 1998-09-11 |
| Whistler | bird    | 1997-12-09 |
| Claws    | cat     | 1994-03-17 |
| Fluffy   | cat     | 1993-02-04 |
| Fang     | dog     | 1990-08-27 |
| Bowser   | dog     | 1989-08-31 |
| Buffy    | dog     | 1989-05-13 |
| Puffball | hamster | 1999-03-30 |
| Slim     | snake   | 1996-04-29 |
+----------+---------+------------+

      Note that the DESC keyword applies only to the column name immediately preceding it (birth); species values are still sorted in ascending order.

      3.3.4.5 日付の計算

      MySQL はいくつかの日付の計算を行う関数を提供します。 例えば、年の計算や日付の部分を取り出したり。

      To determine how many years old each of your pets is, compute the difference in the year part of the current date and the birth date, then subtract one if the current date occurs earlier in the calendar year than the birth date. The following query shows, for each pet, the birth date, the current date, and the age in years. 

      mysql> SELECT name, birth, CURRENT_DATE,
    -> (YEAR(CURRENT_DATE)-YEAR(birth))
    -> - (RIGHT(CURRENT_DATE,5)<RIGHT(birth,5))
    -> AS age
    -> FROM pet;
+----------+------------+--------------+------+
| name     | birth      | CURRENT_DATE | age  |
+----------+------------+--------------+------+
| Fluffy   | 1993-02-04 | 2001-08-29   |    8 |
| Claws    | 1994-03-17 | 2001-08-29   |    7 |
| Buffy    | 1989-05-13 | 2001-08-29   |   12 |
| Fang     | 1990-08-27 | 2001-08-29   |   11 |
| Bowser   | 1989-08-31 | 2001-08-29   |   11 |
| Chirpy   | 1998-09-11 | 2001-08-29   |    2 |
| Whistler | 1997-12-09 | 2001-08-29   |    3 |
| Slim     | 1996-04-29 | 2001-08-29   |    5 |
| Puffball | 1999-03-30 | 2001-08-29   |    2 |
+----------+------------+--------------+------+

      Here, YEAR() pulls out the year part of a date and RIGHT() pulls off the rightmost five characters that represent the MM-DD (calendar year) part of the date. The part of the expression that compares the MM-DD values evaluates to 1 or 0, which adjusts the year difference down a year if CURRENT_DATE occurs earlier in the year than birth. The full expression is somewhat ungainly, so an alias (age) is used to make the output column label more meaningful.

      The query works, but the result could be scanned more easily if the rows were presented in some order. This can be done by adding an ORDER BY name clause to sort the output by name: 

      mysql> SELECT name, birth, CURRENT_DATE,
    -> (YEAR(CURRENT_DATE)-YEAR(birth))
    -> - (RIGHT(CURRENT_DATE,5)<RIGHT(birth,5))
    -> AS age
    -> FROM pet ORDER BY name;
+----------+------------+--------------+------+
| name     | birth      | CURRENT_DATE | age  |
+----------+------------+--------------+------+
| Bowser   | 1989-08-31 | 2001-08-29   |   11 |
| Buffy    | 1989-05-13 | 2001-08-29   |   12 |
| Chirpy   | 1998-09-11 | 2001-08-29   |    2 |
| Claws    | 1994-03-17 | 2001-08-29   |    7 |
| Fang     | 1990-08-27 | 2001-08-29   |   11 |
| Fluffy   | 1993-02-04 | 2001-08-29   |    8 |
| Puffball | 1999-03-30 | 2001-08-29   |    2 |
| Slim     | 1996-04-29 | 2001-08-29   |    5 |
| Whistler | 1997-12-09 | 2001-08-29   |    3 |
+----------+------------+--------------+------+

      To sort the output by age rather than name, just use a different ORDER BY clause: 

      mysql> SELECT name, birth, CURRENT_DATE,
    -> (YEAR(CURRENT_DATE)-YEAR(birth))
    -> - (RIGHT(CURRENT_DATE,5)<RIGHT(birth,5))
    -> AS age
    -> FROM pet ORDER BY age;
+----------+------------+--------------+------+
| name     | birth      | CURRENT_DATE | age  |
+----------+------------+--------------+------+
| Chirpy   | 1998-09-11 | 2001-08-29   |    2 |
| Puffball | 1999-03-30 | 2001-08-29   |    2 |
| Whistler | 1997-12-09 | 2001-08-29   |    3 |
| Slim     | 1996-04-29 | 2001-08-29   |    5 |
| Claws    | 1994-03-17 | 2001-08-29   |    7 |
| Fluffy   | 1993-02-04 | 2001-08-29   |    8 |
| Fang     | 1990-08-27 | 2001-08-29   |   11 |
| Bowser   | 1989-08-31 | 2001-08-29   |   11 |
| Buffy    | 1989-05-13 | 2001-08-29   |   12 |
+----------+------------+--------------+------+

      似たクエリが、既に死んでしまった動物の、死んだ時点の年齢を調べるのにも 使用できます。 どの動物が死んでいるかどうかは、death 値が NULL か どうかで判断します。 これらの値が 非NULL ならば、 death と birth の差の計算を行います： 

      mysql> SELECT name, birth, death,
    -> (YEAR(death)-YEAR(birth)) - (RIGHT(death,5)<RIGHT(birth,5))
    -> AS age
    -> FROM pet WHERE death IS NOT NULL ORDER BY age;
+--------+------------+------------+------+
| name   | birth      | death      | age  |
+--------+------------+------------+------+
| Bowser | 1989-08-31 | 1995-07-29 |    5 |
+--------+------------+------------+------+

      このクエリでは、 death <> NULL ではなく death IS NOT NULL を 使用します。 なぜなら、 NULL は特別な値だからです。 これは後で解説します。 「3.3.4.6 NULL 値の振る舞い」節参照.

      もしあなたが翌月誕生日の動物を知りたいとします。 この種の計算では、 年と日が関係ありません。 birth フィールドの月だけを単に 取り出したくなるでしょう。 MySQL は日付の部分を取り出すいくつかの関数を 提供します。 YEAR(), MONTH(), DAYOFMONTH() など。 ここでは MONTH() がいいでしょう。 これがどのように動くか確かめるには、 birth と MONTH(birth) の両方を表示させるクエリを実行してみます： 

      mysql> SELECT name, birth, MONTH(birth) FROM pet;
+----------+------------+--------------+
| name     | birth      | MONTH(birth) |
+----------+------------+--------------+
| Fluffy   | 1993-02-04 |            2 |
| Claws    | 1994-03-17 |            3 |
| Buffy    | 1989-05-13 |            5 |
| Fang     | 1990-08-27 |            8 |
| Bowser   | 1989-08-31 |            8 |
| Chirpy   | 1998-09-11 |            9 |
| Whistler | 1997-12-09 |           12 |
| Slim     | 1996-04-29 |            4 |
| Puffball | 1999-03-30 |            3 |
+----------+------------+--------------+

      来月誕生日を迎える動物を見つけるのは簡単です。 現在4月だとします。 すると、5月生まれの動物を探します： 

      mysql> SELECT name, birth FROM pet WHERE MONTH(birth) = 5;
+-------+------------+
| name  | birth      |
+-------+------------+
| Buffy | 1989-05-13 |
+-------+------------+

      もし現在が12月なら、ちょっと困るかもしれません。 月の数字 (12) に 1 を足して 13 月生まれの動物を探すわけにはいきません。 かわりに1月生まれの 動物を探します。

      現在が何月なのかを気にすることなく、動作するクエリを書くことが可能です。 この方法では、あなたは月の数字をクエリに使用することがありません。 DATE_ADD() 関数は与えた日付からある時間を足すことが可能です。 もし現時点 NOW() の値に 1ヶ月 足し、 MONTH() で月の 部分を取り出し、その結果を、誕生月を調べるために使用します： 

      mysql> SELECT name, birth FROM pet
    -> WHERE MONTH(birth) = MONTH(DATE_ADD(NOW(), INTERVAL 1 MONTH));

      同じことができる別の方法として、剰余関数 を使用した結果に 1 を足す方法があります。 (もし今月が12月なら、剰余関数 (MOD) を使用した結果は 0 になります)： 

      mysql> SELECT name, birth FROM pet
    -> WHERE MONTH(birth) = MOD(MONTH(NOW()), 12) + 1;

      Note that MONTH returns a number between 1 and 12. And MOD(something,12) returns a number between 0 and 11. So the addition has to be after the MOD(), otherwise we would go from November (11) to January (1).

      3.3.4.6 NULL 値の振る舞い

      あなたがそれに慣れるまでは、NULL 値には驚くかもしれません。 概念的に、NULL 値は ``値無し'' か ``未知な値'' を意味し、 他の値よりもいくぶん異なって扱われます。 NULL の評価の際には、数値の比較演算子 =, <, <> を 使用することは出来ません。 あなた自身これをデモするために、以下のようにしてみてください： 

      mysql> SELECT 1 = NULL, 1 <> NULL, 1 < NULL, 1 > NULL;
+----------+-----------+----------+----------+
| 1 = NULL | 1 <> NULL | 1 < NULL | 1 > NULL |
+----------+-----------+----------+----------+
|     NULL |      NULL |     NULL |     NULL |
+----------+-----------+----------+----------+

      確実にこれらの比較からいかなる意味がある結果も受け取りません。 この代わりに、 IS NULL , IS NOT NULL 演算子を使用します： 

      mysql> SELECT 1 IS NULL, 1 IS NOT NULL;
+-----------+---------------+
| 1 IS NULL | 1 IS NOT NULL |
+-----------+---------------+
|         0 |             1 |
+-----------+---------------+

      MySQL では, 0 や NULL は false（偽） で、それ以外全てが true（真）です。 The default truth value from a boolean operation is 1.

      この NULL の特別な扱いはなぜなのか。 前のセクションを見てください。 どの動物がもはや生きていないことを決定づけるためには、 death <> NULL ではなく death IS NOT NULL の使用が 必要とされるのです。

      Two NULL values are regarded as equal in a GROUP BY.

      When doing an ORDER BY, NULL values are presented first if you do ORDER BY ... ASC and last if you do ORDER BY ... DESC.

      Note that between MySQL 4.0.2 - 4.0.10, NULL values incorrectly were always sorted first regardless of the sort direction.

      3.3.4.7 パターン・マッチ

      MySQL は標準SQLのパターン・マッチを提供します。 また、拡張された正規表現を基にした形式のパターン・マッチ、 これは vi, grep , sed など UNIX のユーティリティに 使用されている物と似ていますが、これも提供します。

      SQL パターン・マッチは、 `_' でいかなる１文字とも一致し、 `%' であらゆる0こ以上の文字列に一致します。 MySQL では、デフォルトで SQL パターンはケース非依存です。 いくつか例を以下に示します。 SQLパターンを使用する場合、 = や != を使用しないように注意してください。 LIKE か NOT LIKE を代わりに使用します。

      `b' から始まる名前を見つけるには: 

      mysql> SELECT * FROM pet WHERE name LIKE "b%";
+--------+--------+---------+------+------------+------------+
| name   | owner  | species | sex  | birth      | death      |
+--------+--------+---------+------+------------+------------+
| Buffy  | Harold | dog     | f    | 1989-05-13 | NULL       |
| Bowser | Diane  | dog     | m    | 1989-08-31 | 1995-07-29 |
+--------+--------+---------+------+------------+------------+

      `fy' で終わる名前を見つけるには: 

      mysql> SELECT * FROM pet WHERE name LIKE "%fy";
+--------+--------+---------+------+------------+-------+
| name   | owner  | species | sex  | birth      | death |
+--------+--------+---------+------+------------+-------+
| Fluffy | Harold | cat     | f    | 1993-02-04 | NULL  |
| Buffy  | Harold | dog     | f    | 1989-05-13 | NULL  |
+--------+--------+---------+------+------------+-------+

      `w' を含む名前を見つけるには: 

      mysql> SELECT * FROM pet WHERE name LIKE "%w%";
+----------+-------+---------+------+------------+------------+
| name     | owner | species | sex  | birth      | death      |
+----------+-------+---------+------+------------+------------+
| Claws    | Gwen  | cat     | m    | 1994-03-17 | NULL       |
| Bowser   | Diane | dog     | m    | 1989-08-31 | 1995-07-29 |
| Whistler | Gwen  | bird    | NULL | 1997-12-09 | NULL       |
+----------+-------+---------+------+------------+------------+

      5文字の名前を見つけるには, `_' パターン文字を使用して： 

      mysql> SELECT * FROM pet WHERE name LIKE "_____";
+-------+--------+---------+------+------------+-------+
| name  | owner  | species | sex  | birth      | death |
+-------+--------+---------+------+------------+-------+
| Claws | Gwen   | cat     | m    | 1994-03-17 | NULL  |
| Buffy | Harold | dog     | f    | 1989-05-13 | NULL  |
+-------+--------+---------+------+------------+-------+

      MySQL では他のパターン・マッチの形も提供されます。正規表現の拡張を使用して。 これらのパターン・マッチをテストする際には、REGEXP と NOT REGEXP 演算子（あるいはRLIKE, NOT RLIKE 演算子。これらは同義です） を使用します。

      拡張正規表現のいくつかの特徴：

      • `.' はいかなる一文字とも一致します。
      • `[...]' は、かっこ内にある文字と一致します。 例えば、`[abc]' は `a', `b' あるいは `c' にマッチします。 文字を範囲指定する場合にはダッシュを使用します。 `[a-z]' はいかなる 小文字のアルファベット文字にも一致し、 `[0-9]' はいかなる数字にも 一致します。
      • `*' は、先に指定されている文字 0 個以上にマッチします。 例えば、`x*' は 文字 `x' がいくつも連続している物にマッチし、 `[0-9]*' はいかなる数値ともマッチし、 `.*' はあらゆる文字列に 一致します。
      • パターンは、テストされた値の中のどこかにある場合、マッチします。 (SQL patterns match only if they match the entire value.)
      • 値のはじめ、あるいは終わりに位置を指定してマッチさせたい場合は、 パターンの初めにマッチさせる場合は `^' を使用し、 パターンの終わりにマッチさせる場合は `$' を使用します。 (これらはアンカーと呼ばれます)

      以下は拡張された正規表現がどう動くかの例です。 上に示した LIKE のクエリは REGEXP で以下のように書き換えれます：

      `b' で始まる名前をみつけるには、`^' で名前の頭にマッチさせ、 かつ `[bB]' として、大文字小文字にもマッチさせます： 

      mysql> SELECT * FROM pet WHERE name REGEXP "^b";
+--------+--------+---------+------+------------+------------+
| name   | owner  | species | sex  | birth      | death      |
+--------+--------+---------+------+------------+------------+
| Buffy  | Harold | dog     | f    | 1989-05-13 | NULL       |
| Bowser | Diane  | dog     | m    | 1989-08-31 | 1995-07-29 |
+--------+--------+---------+------+------------+------------+

      Prior to MySQL Version 3.23.4, REGEXP is case-sensitive, and the previous query will return no rows. To match either lowercase or uppercase `b', use this query instead: 

      mysql> SELECT * FROM pet WHERE name REGEXP "^[bB]";

      From MySQL 3.23.4 on, to force a REGEXP comparison to be case-sensitive, use the BINARY keyword to make one of the strings a binary string. This query will match only lowercase `b' at the beginning of a name: 

      mysql> SELECT * FROM pet WHERE name REGEXP BINARY "^b";

      To find names ending with `fy', use `$' to match the end of the name: 

      mysql> SELECT * FROM pet WHERE name REGEXP "fy$";
+--------+--------+---------+------+------------+-------+
| name   | owner  | species | sex  | birth      | death |
+--------+--------+---------+------+------------+-------+
| Fluffy | Harold | cat     | f    | 1993-02-04 | NULL  |
| Buffy  | Harold | dog     | f    | 1989-05-13 | NULL  |
+--------+--------+---------+------+------------+-------+

      To find names containing a lowercase or uppercase `w', use this query: 

      mysql> SELECT * FROM pet WHERE name REGEXP "w";
+----------+-------+---------+------+------------+------------+
| name     | owner | species | sex  | birth      | death      |
+----------+-------+---------+------+------------+------------+
| Claws    | Gwen  | cat     | m    | 1994-03-17 | NULL       |
| Bowser   | Diane | dog     | m    | 1989-08-31 | 1995-07-29 |
| Whistler | Gwen  | bird    | NULL | 1997-12-09 | NULL       |
+----------+-------+---------+------+------------+------------+

      正規表現はもし値中のどこかにでもあればマッチするため、 SQL パターンのように、パターンの前後にワイルドカードを書く必要はありません。

      5文字の名前を見つけるには、`^' と `$' を使用して名前の初めと終わりに マッチさせ、その間に `.' を5個入れます： 

      mysql> SELECT * FROM pet WHERE name REGEXP "^.....$";
+-------+--------+---------+------+------------+-------+
| name  | owner  | species | sex  | birth      | death |
+-------+--------+---------+------+------------+-------+
| Claws | Gwen   | cat     | m    | 1994-03-17 | NULL  |
| Buffy | Harold | dog     | f    | 1989-05-13 | NULL  |
+-------+--------+---------+------+------------+-------+

      前のクエリは `{n}' ``n回繰り返し'' オペレーターで 書換え可能です。 

      mysql> SELECT * FROM pet WHERE name REGEXP "^.{5}$";
+-------+--------+---------+------+------------+-------+
| name  | owner  | species | sex  | birth      | death |
+-------+--------+---------+------+------------+-------+
| Claws | Gwen   | cat     | m    | 1994-03-17 | NULL  |
| Buffy | Harold | dog     | f    | 1989-05-13 | NULL  |
+-------+--------+---------+------+------------+-------+

      3.3.4.8 Counting Rows

      Databases are often used to answer the question, ``How often does a certain type of data occur in a table?'' For example, you might want to know how many pets you have, or how many pets each owner has, or you might want to perform various kinds of censuses on your animals.

      Counting the total number of animals you have is the same question as ``How many rows are in the pet table?'' because there is one record per pet. The COUNT() function counts the number of non-NULL results, so the query to count your animals looks like this: 

      mysql> SELECT COUNT(*) FROM pet;
+----------+
| COUNT(*) |
+----------+
|        9 |
+----------+

      Earlier, you retrieved the names of the people who owned pets. You can use COUNT() if you want to find out how many pets each owner has: 

      mysql> SELECT owner, COUNT(*) FROM pet GROUP BY owner;
+--------+----------+
| owner  | COUNT(*) |
+--------+----------+
| Benny  |        2 |
| Diane  |        2 |
| Gwen   |        3 |
| Harold |        2 |
+--------+----------+

      Note the use of GROUP BY to group together all records for each owner. Without it, all you get is an error message: 

      mysql> SELECT owner, COUNT(owner) FROM pet;
ERROR 1140 at line 1: Mixing of GROUP columns (MIN(),MAX(),COUNT()...)
with no GROUP columns is illegal if there is no GROUP BY clause

      COUNT() and GROUP BY are useful for characterising your data in various ways. The following examples show different ways to perform animal census operations.

      Number of animals per species: 

      mysql> SELECT species, COUNT(*) FROM pet GROUP BY species;
+---------+----------+
| species | COUNT(*) |
+---------+----------+
| bird    |        2 |
| cat     |        2 |
| dog     |        3 |
| hamster |        1 |
| snake   |        1 |
+---------+----------+

      Number of animals per sex: 

      mysql> SELECT sex, COUNT(*) FROM pet GROUP BY sex;
+------+----------+
| sex  | COUNT(*) |
+------+----------+
| NULL |        1 |
| f    |        4 |
| m    |        4 |
+------+----------+

      (In this output, NULL indicates sex unknown.)

      Number of animals per combination of species and sex: 

      mysql> SELECT species, sex, COUNT(*) FROM pet GROUP BY species, sex;
+---------+------+----------+
| species | sex  | COUNT(*) |
+---------+------+----------+
| bird    | NULL |        1 |
| bird    | f    |        1 |
| cat     | f    |        1 |
| cat     | m    |        1 |
| dog     | f    |        1 |
| dog     | m    |        2 |
| hamster | f    |        1 |
| snake   | m    |        1 |
+---------+------+----------+

      You need not retrieve an entire table when you use COUNT(). For example, the previous query, when performed just on dogs and cats, looks like this: 

      mysql> SELECT species, sex, COUNT(*) FROM pet
    -> WHERE species = "dog" OR species = "cat"
    -> GROUP BY species, sex;
+---------+------+----------+
| species | sex  | COUNT(*) |
+---------+------+----------+
| cat     | f    |        1 |
| cat     | m    |        1 |
| dog     | f    |        1 |
| dog     | m    |        2 |
+---------+------+----------+

      Or, if you wanted the number of animals per sex only for known-sex animals: 

      mysql> SELECT species, sex, COUNT(*) FROM pet
    -> WHERE sex IS NOT NULL
    -> GROUP BY species, sex;
+---------+------+----------+
| species | sex  | COUNT(*) |
+---------+------+----------+
| bird    | f    |        1 |
| cat     | f    |        1 |
| cat     | m    |        1 |
| dog     | f    |        1 |
| dog     | m    |        2 |
| hamster | f    |        1 |
| snake   | m    |        1 |
+---------+------+----------+

      3.3.4.9 Using More Than one Table

      The pet table keeps track of which pets you have. If you want to record other information about them, such as events in their lives like visits to the vet or when litters are born, you need another table. What should this table look like? It needs:

      • To contain the pet name so you know which animal each event pertains to.
      • A date so you know when the event occurred.
      • A field to describe the event.
      • An event type field, if you want to be able to categorise events.

      Given these considerations, the CREATE TABLE statement for the event table might look like this: 

      mysql> CREATE TABLE event (name VARCHAR(20), date DATE,
    -> type VARCHAR(15), remark VARCHAR(255));

      As with the pet table, it's easiest to load the initial records by creating a tab-delimited text file containing the information:

      name date type remark
      Fluffy 1995-05-15 litter 4 kittens, 3 female, 1 male
      Buffy 1993-06-23 litter 5 puppies, 2 female, 3 male
      Buffy 1994-06-19 litter 3 puppies, 3 female
      Chirpy 1999-03-21 vet needed beak straightened
      Slim 1997-08-03 vet broken rib
      Bowser 1991-10-12 kennel
      Fang 1991-10-12 kennel
      Fang 1998-08-28 birthday Gave him a new chew toy
      Claws 1998-03-17 birthday Gave him a new flea collar
      Whistler 1998-12-09 birthday First birthday

      Load the records like this: 

      mysql> LOAD DATA LOCAL INFILE "event.txt" INTO TABLE event;

      Based on what you've learned from the queries you've run on the pet table, you should be able to perform retrievals on the records in the event table; the principles are the same. But when is the event table by itself insufficient to answer questions you might ask?

      Suppose you want to find out the ages of each pet when they had their litters. The event table indicates when this occurred, but to calculate the age of the mother, you need her birth date. Because that is stored in the pet table, you need both tables for the query: 

      mysql> SELECT pet.name,
    -> (TO_DAYS(date) - TO_DAYS(birth))/365 AS age,
    -> remark
    -> FROM pet, event
    -> WHERE pet.name = event.name AND type = "litter";
+--------+------+-----------------------------+
| name   | age  | remark                      |
+--------+------+-----------------------------+
| Fluffy | 2.27 | 4 kittens, 3 female, 1 male |
| Buffy  | 4.12 | 5 puppies, 2 female, 3 male |
| Buffy  | 5.10 | 3 puppies, 3 female         |
+--------+------+-----------------------------+

      There are several things to note about this query:

      • The FROM clause lists two tables because the query needs to pull information from both of them.
      • When combining (joining) information from multiple tables, you need to specify how records in one table can be matched to records in the other. This is easy because they both have a name column. The query uses WHERE clause to match up records in the two tables based on the name values.
      • Because the name column occurs in both tables, you must be specific about which table you mean when referring to the column. This is done by prepending the table name to the column name.

      You need not have two different tables to perform a join. Sometimes it is useful to join a table to itself, if you want to compare records in a table to other records in that same table. For example, to find breeding pairs among your pets, you can join the pet table with itself to pair up males and females of like species: 

      mysql> SELECT p1.name, p1.sex, p2.name, p2.sex, p1.species
    -> FROM pet AS p1, pet AS p2
    -> WHERE p1.species = p2.species AND p1.sex = "f" AND p2.sex = "m";
+--------+------+--------+------+---------+
| name   | sex  | name   | sex  | species |
+--------+------+--------+------+---------+
| Fluffy | f    | Claws  | m    | cat     |
| Buffy  | f    | Fang   | m    | dog     |
| Buffy  | f    | Bowser | m    | dog     |
+--------+------+--------+------+---------+

      In this query, we specify aliases for the table name in order to refer to the columns and keep straight which instance of the table each column reference is associated with.

      3.4 データベースとテーブルの情報を得る

      データベースやテーブルの名前が何であったか、あるいはテーブルの構造はどうであったか、 (なんというフィールドがあったのか)忘れてしまった場合。 MySQL ではいくつかのデータベースとテーブルの情報を提供する文を通じて この問題を処理します。

      あなたは既に SHOW DATABASES を知っているはずで, これはサーバーが 管理するデーターベースの一覧を表示します。 現在選択しているデータベースが 何であるかを知るには、DATABASE() 関数を使用します： 

      mysql> SELECT DATABASE();
+------------+
| DATABASE() |
+------------+
| menagerie  |
+------------+

      もしデータベースをまだ何も選択していなければ、結果はブランクです。

      データベースに含まれるテーブルを見つけるには(たとえば、あなたがテーブル名を 知らない場合)、このコマンドを使用します： 

      mysql> SHOW TABLES;
+---------------------+
| Tables in menagerie |
+---------------------+
| event               |
| pet                 |
+---------------------+

      もしテーブルの構造を知りたいなら、DESCRIBE コマンドが便利です； これはテーブルのそれぞれのフィールドについての情報を表示します。 

      mysql> DESCRIBE pet;
+---------+-------------+------+-----+---------+-------+
| Field   | Type        | Null | Key | Default | Extra |
+---------+-------------+------+-----+---------+-------+
| name    | varchar(20) | YES  |     | NULL    |       |
| owner   | varchar(20) | YES  |     | NULL    |       |
| species | varchar(20) | YES  |     | NULL    |       |
| sex     | char(1)     | YES  |     | NULL    |       |
| birth   | date        | YES  |     | NULL    |       |
| death   | date        | YES  |     | NULL    |       |
+---------+-------------+------+-----+---------+-------+

      Field はフィールド名を示し、Type はフィールドのデータ型、 Null はこのフィールドが Null 値を含むかを示し、 Key はこのフィールドがインデックス化されているかを示し、 Default はフィールドのデフォルトの値を示します。

      もしテーブルにインデックスを持っているなら、 SHOW INDEX FROM tbl_name がそれらの情報を示します。

      3.5 一般的なクエリー例

      以下は、MySQLの一般的な問題を解決するための例です。

      Some of the examples use the table shop to hold the price of each article (item number) for certain traders (dealers). 各業者に対して各商品の価格が1つ決められているとし、(article, dealer)をレコードの主キーとします。

      Start the command-line tool mysql and select a database: 

      mysql your-database-name

      （MySQLのインストールを通常通り行った場合は、'test'データベースをお使いいただけます。）

      以下のSQL文でサンプル テーブルを作成します。 

      CREATE TABLE shop (
 article INT(4) UNSIGNED ZEROFILL DEFAULT '0000' NOT NULL,
 dealer  CHAR(20)                 DEFAULT ''     NOT NULL,
 price   DOUBLE(16,2)             DEFAULT '0.00' NOT NULL,
 PRIMARY KEY(article, dealer));

INSERT INTO shop VALUES
(1,'A',3.45),(1,'B',3.99),(2,'A',10.99),(3,'B',1.45),(3,'C',1.69),
(3,'D',1.25),(4,'D',19.95);

      サンプル データを表示します。 

      mysql> SELECT * FROM shop;

+---------+--------+-------+
| article | dealer | price |
+---------+--------+-------+
|    0001 | A      |  3.45 |
|    0001 | B      |  3.99 |
|    0002 | A      | 10.99 |
|    0003 | B      |  1.45 |
|    0003 | C      |  1.69 |
|    0003 | D      |  1.25 |
|    0004 | D      | 19.95 |
+---------+--------+-------+

      3.5.1 カラムの最大値

      ”articleカラムの最大値は？” 

      SELECT MAX(article) AS article FROM shop

+---------+
| article |
+---------+
|       4 |
+---------+

      3.5.2 特定のカラムの最大値を含んだ行

      ”最も高い価格の商品の番号と、業者、価格を求める。”

      ANSI SQL（MySQLではVersion4.1から）では、副問い合わせを使用することで簡単に求められます。 

      SELECT article, dealer, price
FROM   shop
WHERE  price=(SELECT MAX(price) FROM shop)

      MySQL4.1以前では、以下の2つのステップで求めます。

      1. SELECT構文でテーブルから最大値を取得します。
      2. 1で求めた値をに使用して、実際のクエリーをコンパイルします。 
        SELECT article, dealer, price
FROM   shop
WHERE  price=19.95

      その他には全ての行をpriceカラムをもとに降順で並び替え、 MySQL特有 LIMIT 節を使用して最初の行のみを取得する方法があります。 

      SELECT article, dealer, price
FROM   shop
ORDER BY price DESC
LIMIT 1

      注意：一番高い商品が複数存在する場合は（例えば、19.95ドルの商品が複数ある場合）、LIMIT 節はそのうちの1つの商品しか表示しません。

      3.5.3 カラムのグループごとの最大値

      ”商品ごとの価格の最大値は？” 

      SELECT article, MAX(price) AS price
FROM   shop
GROUP BY article

+---------+-------+
| article | price |
+---------+-------+
|    0001 |  3.99 |
|    0002 | 10.99 |
|    0003 |  1.69 |
|    0004 | 19.95 |
+---------+-------+

      3.5.4 The Rows Holding the Group-wise Maximum of a Certain Field

      ``For each article, find the dealer(s) with the most expensive price.''

      In ANSI SQL (and MySQL Version 4.1 or greater), I'd do it with a subquery like this: 

      SELECT article, dealer, price
FROM   shop s1
WHERE  price=(SELECT MAX(s2.price)
              FROM shop s2
              WHERE s1.article = s2.article);

      In MySQL versions prior to 4.1 it's best do it in several steps:

      1. Get the list of (article,maxprice).
      2. For each article get the corresponding rows that have the stored maximum price.

      This can easily be done with a temporary table: 

      CREATE TEMPORARY TABLE tmp (
        article INT(4) UNSIGNED ZEROFILL DEFAULT '0000' NOT NULL,
        price   DOUBLE(16,2)             DEFAULT '0.00' NOT NULL);

LOCK TABLES shop read;

INSERT INTO tmp SELECT article, MAX(price) FROM shop GROUP BY article;

SELECT shop.article, dealer, shop.price FROM shop, tmp
WHERE shop.article=tmp.article AND shop.price=tmp.price;

UNLOCK TABLES;

DROP TABLE tmp;

      If you don't use a TEMPORARY table, you must also lock the 'tmp' table.

      ``Can it be done with a single query?''

      Yes, but only by using a quite inefficient trick that I call the ``MAX-CONCAT trick'': 

      SELECT article,
       SUBSTRING( MAX( CONCAT(LPAD(price,6,'0'),dealer) ), 7) AS dealer,
  0.00+LEFT(      MAX( CONCAT(LPAD(price,6,'0'),dealer) ), 6) AS price
FROM   shop
GROUP BY article;

+---------+--------+-------+
| article | dealer | price |
+---------+--------+-------+
|    0001 | B      |  3.99 |
|    0002 | A      | 10.99 |
|    0003 | C      |  1.69 |
|    0004 | D      | 19.95 |
+---------+--------+-------+

      The last example can, of course, be made a bit more efficient by doing the splitting of the concatenated column in the client.

      3.5.5 ユーザー変数の使用

      MySQLのユーザー変数を使用すると、クライアントの一時変数に格納せずに結果を 記憶できます。 「6.1.4 ユーザー変数」節参照。

      例えば、商品の価格の最大値と最小値を求めるには、以下のSELECT構文を実行します。 

      mysql> SELECT @min_price:=MIN(price),@max_price:=MAX(price) FROM shop;
mysql> SELECT * FROM shop WHERE price=@min_price OR price=@max_price;
+---------+--------+-------+
| article | dealer | price |
+---------+--------+-------+
|    0003 | D      |  1.25 |
|    0004 | D      | 19.95 |
+---------+--------+-------+

      3.5.6 Using Foreign Keys

      In MySQL 3.23.44 and up, InnoDB tables supports checking of foreign key constraints. 「7.5 InnoDB テーブル (3.23.6以上)」節参照. See also 「1.7.4.5 外部キー」節.

      You don't actually need foreign keys to join 2 tables. The only thing MySQL currently doesn't do (in table types other than InnoDB), is CHECK to make sure that the keys you use really exist in the table(s) you're referencing and it doesn't automatically delete rows from a table with a foreign key definition. If you use your keys like normal, it'll work just fine: 

      CREATE TABLE person (
    id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT,
    name CHAR(60) NOT NULL,
    PRIMARY KEY (id)
);

CREATE TABLE shirt (
    id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT,
    style ENUM('t-shirt', 'polo', 'dress') NOT NULL,
    color ENUM('red', 'blue', 'orange', 'white', 'black') NOT NULL,
    owner SMALLINT UNSIGNED NOT NULL REFERENCES person(id),
    PRIMARY KEY (id)
);

INSERT INTO person VALUES (NULL, 'Antonio Paz');

INSERT INTO shirt VALUES
(NULL, 'polo', 'blue', LAST_INSERT_ID()),
(NULL, 'dress', 'white', LAST_INSERT_ID()),
(NULL, 't-shirt', 'blue', LAST_INSERT_ID());

INSERT INTO person VALUES (NULL, 'Lilliana Angelovska');

INSERT INTO shirt VALUES
(NULL, 'dress', 'orange', LAST_INSERT_ID()),
(NULL, 'polo', 'red', LAST_INSERT_ID()),
(NULL, 'dress', 'blue', LAST_INSERT_ID()),
(NULL, 't-shirt', 'white', LAST_INSERT_ID());

SELECT * FROM person;
+----+---------------------+
| id | name                |
+----+---------------------+
|  1 | Antonio Paz         |
|  2 | Lilliana Angelovska |
+----+---------------------+

SELECT * FROM shirt;
+----+---------+--------+-------+
| id | style   | color  | owner |
+----+---------+--------+-------+
|  1 | polo    | blue   |     1 |
|  2 | dress   | white  |     1 |
|  3 | t-shirt | blue   |     1 |
|  4 | dress   | orange |     2 |
|  5 | polo    | red    |     2 |
|  6 | dress   | blue   |     2 |
|  7 | t-shirt | white  |     2 |
+----+---------+--------+-------+

SELECT s.* FROM person p, shirt s
 WHERE p.name LIKE 'Lilliana%'
   AND s.owner = p.id
   AND s.color <> 'white';

+----+-------+--------+-------+
| id | style | color  | owner |
+----+-------+--------+-------+
|  4 | dress | orange |     2 |
|  5 | polo  | red    |     2 |
|  6 | dress | blue   |     2 |
+----+-------+--------+-------+

      3.5.7 Searching on Two Keys

      MySQL doesn't yet optimize when you search on two different keys combined with OR (searching on one key with different OR parts is optimized quite well): 

      SELECT field1_index, field2_index FROM test_table WHERE field1_index = '1'
OR  field2_index = '1'

      The reason is that we haven't yet had time to come up with an efficient way to handle this in the general case. (The AND handling is, in comparison, now completely general and works very well.)

      For the moment you can solve this very efficiently by using a TEMPORARY table. This type of optimization is also very good if you are using very complicated queries where the SQL server does the optimizations in the wrong order. 

      CREATE TEMPORARY TABLE tmp
SELECT field1_index, field2_index FROM test_table WHERE field1_index = '1';
INSERT INTO tmp
SELECT field1_index, field2_index FROM test_table WHERE field2_index = '1';
SELECT * from tmp;
DROP TABLE tmp;

      The above way to solve this query is in effect a UNION of two queries. 「6.4.1.2 UNION Syntax」節参照.

      3.5.8 Calculating Visits Per Day

      The following shows an idea of how you can use the bit group functions to calculate the number of days per month a user has visited a web page. 

      CREATE TABLE t1 (year YEAR(4), month INT(2) UNSIGNED ZEROFILL,
             day INT(2) UNSIGNED ZEROFILL);
INSERT INTO t1 VALUES(2000,1,1),(2000,1,20),(2000,1,30),(2000,2,2),
            (2000,2,23),(2000,2,23);
SELECT year,month,BIT_COUNT(BIT_OR(1<<day)) AS days FROM t1
       GROUP BY year,month;

Which returns:

+------+-------+------+
| year | month | days |
+------+-------+------+
| 2000 |    01 |    3 |
| 2000 |    02 |    2 |
+------+-------+------+

      The above calculates how many different days was used for a given year/month combination, with automatic removal of duplicate entries.

      3.5.9 Using AUTO_INCREMENT

      The AUTO_INCREMENT attribute can be used to generate a unique identity for new rows: 

      CREATE TABLE animals (
             id MEDIUMINT NOT NULL AUTO_INCREMENT,
             name CHAR(30) NOT NULL,
             PRIMARY KEY (id)
             );
INSERT INTO animals (name) VALUES ("dog"),("cat"),("penguin"),
                                  ("lax"),("whale");
SELECT * FROM animals;

Which returns:

+----+---------+
| id | name    |
+----+---------+
|  1 | dog     |
|  2 | cat     |
|  3 | penguin |
|  4 | lax     |
|  5 | whale   |
+----+---------+

      You can retrieve the used AUTO_INCREMENT key with the LAST_INSERT_ID() SQL function or the mysql_insert_id() API function. Note: for a multi-row insert, LAST_INSERT_ID()/mysql_insert_id() will actually return the AUTO_INCREMENT key from the first inserted row. This allows multi-row inserts to be reproduced on other servers.

      For MyISAM and BDB tables you can specify AUTO_INCREMENT on secondary column in a multi-column key. In this case the generated value for the autoincrement column is calculated as MAX(auto_increment_column)+1) WHERE prefix=given-prefix. This is useful when you want to put data into ordered groups. 

      CREATE TABLE animals (
             grp ENUM('fish','mammal','bird') NOT NULL,
             id MEDIUMINT NOT NULL AUTO_INCREMENT,
             name CHAR(30) NOT NULL,
             PRIMARY KEY (grp,id)
             );
INSERT INTO animals (grp,name) VALUES("mammal","dog"),("mammal","cat"),
                  ("bird","penguin"),("fish","lax"),("mammal","whale");
SELECT * FROM animals ORDER BY grp,id;

Which returns:

+--------+----+---------+
| grp    | id | name    |
+--------+----+---------+
| fish   |  1 | lax     |
| mammal |  1 | dog     |
| mammal |  2 | cat     |
| mammal |  3 | whale   |
| bird   |  1 | penguin |
+--------+----+---------+

      Note that in this case, the AUTO_INCREMENT value will be reused if you delete the row with the biggest AUTO_INCREMENT value in any group.

      3.6 mysql のバッチモードでの使用

      前のセクションでは、mysql を対話モードで使用し、クエリの入力と 結果を表示しました。 mysql はバッチモードでも実行可能です。 これを行うには、あなたが実行したいコマンドをファイルに書いておき、 そのファイルから入力を読み込むようにして mysql を実行します： 

      shell> mysql < batch-file

      If you are running mysql under windows and have some special characters in the file that causes problems, you can do: 

      dos> mysql -e "source batch-file"

      もし接続パラメターを指定する必要がある場合は、以下のようになるでしょう： 

      shell> mysql -h host -u user -p < batch-file
Enter password: ********

      この方法で mysql を使用するとき、あなたはスクリプトファイルを 作成し、それを実行することになるでしょう。

      If you want the script to continue even if you have errors, you should use the --force command-line option.

      なぜスクリプトを使用するのか？ それには以下の理由があります：

      • もし繰り返しクエリを実行する場合(毎日とか毎週とか)、スクリプトを書くことで、 その実行の度にあなたがコマンドをタイプすることを省くことが可能です。
      • もし既にあるクエリに似た新しいクエリを書く場合、それらをコピーし スクリプトファイルを編集できます。
      • バッチモードはクエリの開発中や複数にまたがるコマンドには役に立ちます。 もしコマンドが間違っていたとしても全てを打ち直す必要がありません。 エラーを修正するためにスクリプトを編集し、再び mysql に実行させます。
      • もし多くの出力を出すようなクエリの場合、ページャーを使用して出力を見ることが 出来ます。 出力がスクロールして画面から見えなくなるよりいいでしょう： 
        shell> mysql < batch-file | more
      • あなたはより処理を行うために、結果をファイルに書き出すことが可能です： 
        shell> mysql < batch-file > mysql.out
      • あなたは、他人へのあなたのスクリプトを配布することができます。これにより、ほかの人たちも コマンドを実行することができます。
      • いくつかの状況では、対話モードでは使用に耐えません。 たとえば、クエリを cron ジョブとして実行する場合。 この場合、バッチモードでなければなりません。
      • 端末が正しく扱えない文字を mysql コマンドに渡す場合。 たとえば、EUC-JP, Shift_JIS の漢字文字などは、端末や環境によっては直接入力できない場合もあるでしょう。 あるいは、文字コードの違う MySQL サーバーにデータを転送するときなども。

      mysql をバッチモードで使用するか、対話モードで使用するかで、 デフォルトの出力形式が変わります。 例えば、 SELECT DISTINCT species FROM pet の 出力は対話モードでは次のようになります： 

      +---------+
| species |
+---------+
| bird    |
| cat     |
| dog     |
| hamster |
| snake   |
+---------+

      しかし、バッチモードでは： 

      species
bird
cat
dog
hamster
snake

      もしバッチモードでも対話モードのような出力を得たい場合には、mysql -t とします。 出力中に、実行したコマンドを表示させるならば、mysql -vvv とします。

      You can also use scripts in the mysql command-line prompt by using the source command: 

      mysql> source filename;

      3.7 Queries from Twin Project

      At Analytikerna and Lentus, we have been doing the systems and field work for a big research project. This project is a collaboration between the Institute of Environmental Medicine at Karolinska Institutet Stockholm and the Section on Clinical Research in Aging and Psychology at the University of Southern California.

      The project involves a screening part where all twins in Sweden older than 65 years are interviewed by telephone. Twins who meet certain criteria are passed on to the next stage. In this latter stage, twins who want to participate are visited by a doctor/nurse team. Some of the examinations include physical and neuropsychological examination, laboratory testing, neuroimaging, psychological status assessment, and family history collection. In addition, data are collected on medical and environmental risk factors.

      More information about Twin studies can be found at: http://www.imm.ki.se/TWIN/TWINUKW.HTM

      The latter part of the project is administered with a web interface written using Perl and MySQL.

      Each night all data from the interviews are moved into a MySQL database.

      3.7.1 Find all Non-distributed Twins

      The following query is used to determine who goes into the second part of the project: 

      SELECT
        CONCAT(p1.id, p1.tvab) + 0 AS tvid,
        CONCAT(p1.christian_name, " ", p1.surname) AS Name,
        p1.postal_code AS Code,
        p1.city AS City,
        pg.abrev AS Area,
        IF(td.participation = "Aborted", "A", " ") AS A,
        p1.dead AS dead1,
        l.event AS event1,
        td.suspect AS tsuspect1,
        id.suspect AS isuspect1,
        td.severe AS tsevere1,
        id.severe AS isevere1,
        p2.dead AS dead2,
        l2.event AS event2,
        h2.nurse AS nurse2,
        h2.doctor AS doctor2,
        td2.suspect AS tsuspect2,
        id2.suspect AS isuspect2,
        td2.severe AS tsevere2,
        id2.severe AS isevere2,
        l.finish_date
FROM
        twin_project AS tp
        /* For Twin 1 */
        LEFT JOIN twin_data AS td ON tp.id = td.id
                  AND tp.tvab = td.tvab
        LEFT JOIN informant_data AS id ON tp.id = id.id
                  AND tp.tvab = id.tvab
        LEFT JOIN harmony AS h ON tp.id = h.id
                  AND tp.tvab = h.tvab
        LEFT JOIN lentus AS l ON tp.id = l.id
                  AND tp.tvab = l.tvab
        /* For Twin 2 */
        LEFT JOIN twin_data AS td2 ON p2.id = td2.id
                  AND p2.tvab = td2.tvab
        LEFT JOIN informant_data AS id2 ON p2.id = id2.id
                  AND p2.tvab = id2.tvab
        LEFT JOIN harmony AS h2 ON p2.id = h2.id
                  AND p2.tvab = h2.tvab
        LEFT JOIN lentus AS l2 ON p2.id = l2.id
                  AND p2.tvab = l2.tvab,
        person_data AS p1,
        person_data AS p2,
        postal_groups AS pg
WHERE
        /* p1 gets main twin and p2 gets his/her twin. */
        /* ptvab is a field inverted from tvab */
        p1.id = tp.id AND p1.tvab = tp.tvab AND
        p2.id = p1.id AND p2.ptvab = p1.tvab AND
        /* Just the sceening survey */
        tp.survey_no = 5 AND
        /* Skip if partner died before 65 but allow emigration (dead=9) */
        (p2.dead = 0 OR p2.dead = 9 OR
         (p2.dead = 1 AND
          (p2.death_date = 0 OR
           (((TO_DAYS(p2.death_date) - TO_DAYS(p2.birthday)) / 365)
            >= 65))))
        AND
        (
        /* Twin is suspect */
        (td.future_contact = 'Yes' AND td.suspect = 2) OR
        /* Twin is suspect - Informant is Blessed */
        (td.future_contact = 'Yes' AND td.suspect = 1
                                   AND id.suspect = 1) OR
        /* No twin - Informant is Blessed */
        (ISNULL(td.suspect) AND id.suspect = 1
                            AND id.future_contact = 'Yes') OR
        /* Twin broken off - Informant is Blessed */
        (td.participation = 'Aborted'
         AND id.suspect = 1 AND id.future_contact = 'Yes') OR
        /* Twin broken off - No inform - Have partner */
        (td.participation = 'Aborted' AND ISNULL(id.suspect)
                                      AND p2.dead = 0))
        AND
        l.event = 'Finished'
        /* Get at area code */
        AND SUBSTRING(p1.postal_code, 1, 2) = pg.code
        /* Not already distributed */
        AND (h.nurse IS NULL OR h.nurse=00 OR h.doctor=00)
        /* Has not refused or been aborted */
        AND NOT (h.status = 'Refused' OR h.status = 'Aborted'
        OR h.status = 'Died' OR h.status = 'Other')
ORDER BY
        tvid;

      Some explanations:

      CONCAT(p1.id, p1.tvab) + 0 AS tvid
      We want to sort on the concatenated id and tvab in numerical order. Adding 0 to the result causes MySQL to treat the result as a number.
      column id
      This identifies a pair of twins. It is a key in all tables.
      column tvab
      This identifies a twin in a pair. It has a value of 1 or 2.
      column ptvab
      This is an inverse of tvab. When tvab is 1 this is 2, and vice versa. It exists to save typing and to make it easier for MySQL to optimize the query.

      This query demonstrates, among other things, how to do lookups on a table from the same table with a join (p1 and p2). In the example, this is used to check whether a twin's partner died before the age of 65. If so, the row is not returned.

      All of the above exist in all tables with twin-related information. We have a key on both id,tvab (all tables), and id,ptvab (person_data) to make queries faster.

      On our production machine (A 200MHz UltraSPARC), this query returns about 150-200 rows and takes less than one second.

      The current number of records in the tables used above:
      Table Rows
      person_data 71074
      lentus 5291
      twin_project 5286
      twin_data 2012
      informant_data 663
      harmony 381
      postal_groups 100

      3.7.2 Show a Table on Twin Pair Status

      Each interview ends with a status code called event. The query shown here is used to display a table over all twin pairs combined by event. This indicates in how many pairs both twins are finished, in how many pairs one twin is finished and the other refused, and so on. 

      SELECT
        t1.event,
        t2.event,
        COUNT(*)
FROM
        lentus AS t1,
        lentus AS t2,
        twin_project AS tp
WHERE
        /* We are looking at one pair at a time */
        t1.id = tp.id
        AND t1.tvab=tp.tvab
        AND t1.id = t2.id
        /* Just the sceening survey */
        AND tp.survey_no = 5
        /* This makes each pair only appear once */
        AND t1.tvab='1' AND t2.tvab='2'
GROUP BY
        t1.event, t2.event;

      3.8 Using MySQL with Apache

      There are programs that let you authenticate your users from a MySQL database and also let you log your log files into a MySQL table.

      You can change the Apache logging format to be easily readable by MySQL by putting the following into the Apache configuration file: 

      LogFormat \
        "\"%h\",%{%Y%m%d%H%M%S}t,%>s,\"%b\",\"%{Content-Type}o\",  \
        \"%U\",\"%{Referer}i\",\"%{User-Agent}i\""

      In MySQL you can do something like this: 

      LOAD DATA INFILE '/local/access_log' INTO TABLE table_name
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' ESCAPED BY '\\'

      Go to the first, previous, next, last section, table of contents. mysql-4.00.12/manual.ja_toc.html0100644000175100001560000033105010021471264015241 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - Table of Contents

      MySQL Reference Manual for version 4.0.12.

      This document was generated on 4 March 2004 using the texi2html translator version 1.52 (extended by davida@detron.se).

      mysql-4.00.12/reservedwords.texi0100644000175100001560000001024310007312726015430 0ustar takeshisa@c START_OF_RESERVED_WORDS @c Reserved word list updated Fri Mar 14 13:55:29 2003 by arjen. @c Data from MySQL version 4.1.0-alpha @c BitKeeper ChangeSet 1.1515 (03/03/11 16:32:17) @c To regenerate, use Support/update-reserved-words.pl @multitable @columnfractions .33 .33 .34 @item @strong{Word} @tab @strong{Word} @tab @strong{Word} @item @code{ADD} @tab @code{ALL} @tab @code{ALTER} @item @code{ANALYZE} @tab @code{AND} @tab @code{AS} @item @code{ASC} @tab @code{AUTO_INCREMENT} @tab @code{BDB} @item @code{BEFORE} @tab @code{BERKELEYDB} @tab @code{BETWEEN} @item @code{BIGINT} @tab @code{BINARY} @tab @code{BLOB} @item @code{BOTH} @tab @code{BTREE} @tab @code{BY} @item @code{CASCADE} @tab @code{CASE} @tab @code{CHANGE} @item @code{CHAR} @tab @code{CHARACTER} @tab @code{CHECK} @item @code{COLLATE} @tab @code{COLUMN} @tab @code{COLUMNS} @item @code{CONSTRAINT} @tab @code{CREATE} @tab @code{CROSS} @item @code{CURRENT_DATE} @tab @code{CURRENT_TIME} @tab @code{CURRENT_TIMESTAMP} @item @code{DATABASE} @tab @code{DATABASES} @tab @code{DAY_HOUR} @item @code{DAY_MINUTE} @tab @code{DAY_SECOND} @tab @code{DEC} @item @code{DECIMAL} @tab @code{DEFAULT} @tab @code{DELAYED} @item @code{DELETE} @tab @code{DESC} @tab @code{DESCRIBE} @item @code{DISTINCT} @tab @code{DISTINCTROW} @tab @code{DIV} @item @code{DOUBLE} @tab @code{DROP} @tab @code{ELSE} @item @code{ENCLOSED} @tab @code{ERRORS} @tab @code{ESCAPED} @item @code{EXISTS} @tab @code{EXPLAIN} @tab @code{FALSE} @item @code{FIELDS} @tab @code{FLOAT} @tab @code{FOR} @item @code{FORCE} @tab @code{FOREIGN} @tab @code{FROM} @item @code{FULLTEXT} @tab @code{FUNCTION} @tab @code{GRANT} @item @code{GROUP} @tab @code{HASH} @tab @code{HAVING} @item @code{HIGH_PRIORITY} @tab @code{HOUR_MINUTE} @tab @code{HOUR_SECOND} @item @code{IF} @tab @code{IGNORE} @tab @code{IN} @item @code{INDEX} @tab @code{INFILE} @tab @code{INNER} @item @code{INNODB} @tab @code{INSERT} @tab @code{INT} @item @code{INTEGER} @tab @code{INTERVAL} @tab @code{INTO} @item @code{IS} @tab @code{JOIN} @tab @code{KEY} @item @code{KEYS} @tab @code{KILL} @tab @code{LEADING} @item @code{LEFT} @tab @code{LIKE} @tab @code{LIMIT} @item @code{LINES} @tab @code{LOAD} @tab @code{LOCALTIME} @item @code{LOCALTIMESTAMP} @tab @code{LOCK} @tab @code{LONG} @item @code{LONGBLOB} @tab @code{LONGTEXT} @tab @code{LOW_PRIORITY} @item @code{MASTER_SERVER_ID} @tab @code{MATCH} @tab @code{MEDIUMBLOB} @item @code{MEDIUMINT} @tab @code{MEDIUMTEXT} @tab @code{MIDDLEINT} @item @code{MINUTE_SECOND} @tab @code{MOD} @tab @code{MRG_MYISAM} @item @code{NATURAL} @tab @code{NOT} @tab @code{NULL} @item @code{NUMERIC} @tab @code{ON} @tab @code{OPTIMIZE} @item @code{OPTION} @tab @code{OPTIONALLY} @tab @code{OR} @item @code{ORDER} @tab @code{OUTER} @tab @code{OUTFILE} @item @code{PRECISION} @tab @code{PRIMARY} @tab @code{PRIVILEGES} @item @code{PROCEDURE} @tab @code{PURGE} @tab @code{READ} @item @code{REAL} @tab @code{REFERENCES} @tab @code{REGEXP} @item @code{RENAME} @tab @code{REPLACE} @tab @code{REQUIRE} @item @code{RESTRICT} @tab @code{RETURNS} @tab @code{REVOKE} @item @code{RIGHT} @tab @code{RLIKE} @tab @code{RTREE} @item @code{SELECT} @tab @code{SET} @tab @code{SHOW} @item @code{SMALLINT} @tab @code{SOME} @tab @code{SONAME} @item @code{SPATIAL} @tab @code{SQL_BIG_RESULT} @tab @code{SQL_CALC_FOUND_ROWS} @item @code{SQL_SMALL_RESULT} @tab @code{SSL} @tab @code{STARTING} @item @code{STRAIGHT_JOIN} @tab @code{STRIPED} @tab @code{TABLE} @item @code{TABLES} @tab @code{TERMINATED} @tab @code{THEN} @item @code{TINYBLOB} @tab @code{TINYINT} @tab @code{TINYTEXT} @item @code{TO} @tab @code{TRAILING} @tab @code{TRUE} @item @code{TYPES} @tab @code{UNION} @tab @code{UNIQUE} @item @code{UNLOCK} @tab @code{UNSIGNED} @tab @code{UPDATE} @item @code{USAGE} @tab @code{USE} @tab @code{USER_RESOURCES} @item @code{USING} @tab @code{VALUES} @tab @code{VARBINARY} @item @code{VARCHAR} @tab @code{VARCHARACTER} @tab @code{VARYING} @item @code{WARNINGS} @tab @code{WHEN} @tab @code{WHERE} @item @code{WITH} @tab @code{WRITE} @tab @code{XOR} @item @code{YEAR_MONTH} @tab @code{ZEROFILL} @tab @end multitable @c END_OF_RESERVED_WORDS mysql-4.00.12/manual.ja.texi.tar.gz0100644000175100001560000272521610021471257015624 0ustar takeshisarF@ZsE肄+jwEma!q賀D\g5嗽L紐>1砥Z~!,?パ#.懋齔sV> b!酲~5b;_vaTUfefe~Y欹-9-h~OKkKS7?嶢厰阪柢*O襴-a鋲嵳[Z7>o棆yc綰(qmG{Q5姉YO!Oi鵬n>秀1U]婆kfc s  柞ネV惆i依tF9囹T決/6mjyJV陌TUkkOn|乙.7ml撩)>eatFf')n+/8薈4oli拂z蛙f)Cs, L5rlwョ]lnW{aぇt濶e9v,=文FN炳l *Y涌4hk爺8碓殘- M1gn筺U卸]36: -Jc #-b2絹Y卯i8S+0t!i1-犧+lPゅ/Z*-Yf啜9h2$3 h笞z6P召SP4[`*E/Pl"um\_V-f5%ERJe7唔L]-L[V"鋤,割g{Y牧^qutoQSq2ZsI,gf6Y%BF1ち 0)lT1I}KLRAe･vQ{=C?Dm$螳6談iPK0 4!dP0*｢4瞶嬌&"蚋調>i$y勣e;DOR9 ME(4L祢>PEH石t:tv c丁 shuM戸1]&溲臘 C6\"UL&4yWd4d92巽6-A_1屋腰23逑'k5L丁g?StY2=V迎C[9-竊CLQ蘭3-￣ZyP曁t5Di噫 >[!|>o@<#/銕ビw埃:濔k肋gm]Yo膀{Y廴}O薫箝--Z:ZlV(E,b$ 估 l辭" Cu\ y> ):%-@\-答Nﾑ璽VMRKIL X`,,V!T1, nRA%4大4IH壯h楹稚 E懌`欺l;} t 讌a;<波!“Vs`D=DWH!`cH%Ubl,;3K棗鎗,y2=勒6DJTCD8f[倭oIzBC蛛):EeDMehL7MoC!`Puf;顆 rN.cGqP#^ｭB防)廟&Qe, G-(a仇3_碗GC'MA蜑m炯杣{事5wv{YyBbV^mJ割G,rK^罕の|4Fd> !c清eJQQcrU董屎g"滞価CC,番d/<}D-]U 梺kkwd|C*h*zy~c#H!vuがu~eb"XsSbOpPF,撰3,NhNmb,#RK0:HbNCP $,f２QX対%Xi_J@[弊筥iv絲lx"g|L x0%@D轢kwcJqtr嗇W 8/]J琅,~,ж.@陵V'I~?猖85j鮠P5CeO宏4x融臀 {泙〃}x>|&JKfA!羹5H化唸W'|H~D条"5ツ &S#]W|R癰攣憔;vmG7砂鎧 k*8Ny 藜瓲M+秦 {P縵qp_盂d薩!d機 rh'2 9h!A嫂FQZ忌a&HK;N滉_B ~-飭>i菰V1[w'o~',|訥綛蘋=~2X5汳ez!幻緝肬zПW=j7IT胼U ? a~725,$/bsK便7#vcr嶢釋JX-[,RFJ完.1!q':v$\]勝 ﾙzE9{8Wu^C[NllSＫ 勇 麈PAYW_vq8b帑該朞{#hA~ 瑪 迚善?Gi3c痙Dirm167nbp{i篦`7箙y06荅H/QPL粛貞{w暘貫bZfO"Hk0&TH没BP#H>U=!烱(A*X!DI邁.!3> 8 )D妻aNm蜘4?廴~S[N屯Vjb麺K5ﾌ$.彳\kd{n^~N=q{ xZk=秦kNL^隍Xg`m,h$p)a+8}繩!@wwxj=蛬@2<2uaS'E-+淒Gg*`m=c[[56商)l,R=D耐樵鷽>B}7"同5 i騙*$蚓kvsQ^6渠23J竊3h`' et#荒XX7~4閊y"禰s&尚\框@<(K6l詒鬘H芽"_4$O掎荻;橋31 辱?k%*z5B]> 3H_W* 畠蒿zp嘩鮗荳,W倚 $lzVE[TQ2J斗, |bWw,|:XB諳bUXU`skg櫪cbpL硫0v掾RK9LgET*cy艨T1O玉QM~~bG緒碌Ke Z|'墾`{KMｑ=^<|{u0VVib 亮n.ne#拈sFjG匳|p_~bKm_@W{}k &'塢w篥_z]a~I滝d[[謠3庇nil|y >T押路Q;z褊 LoMt8umP而q{xn矜r*_05灘.+^TG')wN陥 ]{Y\xCV^&/+z+6緋>Iゅ% &烽EYD%tq:慴工#cp‥ﾎ =T,GEVh榲MjFB儉A^vzDb*B載N躰?焚勧xcc腦9z褓dxx碍d%,j8vN17>鶺h王7m(v.鴾K鮠_n,Pw痍p處$Za1表 罍$ 縣まq44棔9~阿Z)[T番6 бgi釐w!@0%j$0%Xu@3X硅-nJp樫&(~}й4碼"-;<)v>琺e掴wC-T?W>授倉W宀gn6框_ktB5M*]仆幽z擯藾vK3蕈w寥:f屯 饂ZB闃j?鞅^ 3}=k紋rHn-儂V~==n\2iY+f8cYT#陬bbd==qn≪` sDn5~t渾x&R@[%Z NTG曖az/P7&冐kBqv)R伏(uYB.@侯蚌Ａ+.g.N#魖f逐Al*|N拳冂Ra aq讖3QB;E0]掖%R6繼戮令倣_Tb9粛 2Yj#魅枠 s綱羶E虹LbtA|19'-t\`.;m1O)(D&榮U 栖.Exa哉#V檜v.{5伴t!匙肆袖2>拱~XヒsH@倫;菻v諱uus3PLh"2爺ccIZN $:昃!e怕?s'okz)VEs (Qt*b30t1~qIMD~晋 g髄徳羝[G=[VRl/I;qmr}2nn漉Cx|5jr遖!際5.AP7]>%誡S>-E<＄*|=!cs}jф/=-bdD/h*9O(qN+uFo+E " 容P"~$岌Hya Y{gpbe~煢aTC茜I=豐炳l!C 何h琵F5AF5砒r"!賄k1Qc4d＋7Zfk c\va~F H肺mJ3aQ壞DBz]x喃m-@!r&5 * l^ 禎T8*~/HA |G {}_w醂gEs,NO･C7)| %A +1{PD6@]E>[s4c  1湛寅& 0 {, =柆(i_z圓A鉥濛~To@舒 q`Ag *45L狒耕~鐐])&王?u=,JG $+Faz::圏!杞on肬VgBy0]s[E~|!aB騒青9※p"瞶)/@髮_dZy鳳J^d媛#%%d&q7bf 9旬WR2EHKw>}巛9OM\R Eо憮S63n髦DNR7:08d ?Lszy E”K)&H鼾寞t椅ed-!+n7 !Ufo>nyVzU8鉛1 c>=;0a孵貰HlTqG 繞幗1+N5wut洞~5E\JZX] 樗]V言x|{c`浩紳 OI ↑},Af靠!耳@M^Z6" ？4px[eB跚j=y嫺3豁ァ控4|裼jhmW|@咯F5?iNgm>株N+q樺[Z[`駸vJ|公ｿ椥1\タc去仍gUQcﾗ~湯LK?w9b$響8誹逵$i|tでlw張Z9igNd gt蹊+k *PP,笈Gh0,屯?_/NH枉g$q ﾇc83rlI*r)i辮4箸腿f7 yBJn^Ea}^%;>{mfN燈獨`eVP転qOg=; W7pc< r<[!7,hr]Ehf]勇WdRg惑 \.c児nZqR6BД)bpEw4p 肉]~J?剔j.Z誡 O+itぴ#漾8}JpJ%>檄Q(mH,瀋0埒U氈ラ=up<丞d~>gTjn$$q滷:紐E} {uu6% ,ei kh G鵁{<K~HLX3VTeSj榿X籀曄n帥:k螽D釖"Q簿\Z撩1虫b,gb[;0蟆MDQtM)頬Υ;島]pV20SeQ蜊.7幸"BU``4Shd Cn庸a(R績@E橙#<92o:+B sr+NW[rt'\P81A .泌 eWZ接bXB`' 23qM~梟cC[$\U&r纎f頒Pv墨ちベ) ~#*kB LPh9gWPK&G 嗚兢 Z !L?m(!鰭(矜恣>>-婁]`6'$!労D怨闊/7 踪<,B

      @Vq=0dq韻")$&1"6弑枝P8LJ .白苙aMj/箴r iq輦2+$(Ejwq)^IN箔0L池3髞壗m5昃\fh*粘:=+.MnrFIDD$サ礙f赴 V&7亶9N%N@L4 `Iqn縢- ^Y(f棉Jo-5R`~S e伎 M8驗笞/z%,妁 `2G津 fu{-CY.5-ijt.0近 (tL ZE} 騨;@Emfy,OwY8Zit籖oR24u舳c辷b&pq_*&(k1yhp`t/Ur$闃固.>c 段Y8舎_2<6k蜿沛飛}ギ糸{[体XZ壓粕qgr紂zLeJ].崇DbQ(7拗@矜{醜_P2 ;$T豚]FLAQ*薤M4Y艾"y凛C慈&R&) DS#Xqq9h9p嗇$ 頓m[)]!kgI;TL.c 3Ej:|(H咒gq古⊆^vi蝴6cPU~M5alDｫba ?DZ謌')歐i創u,軼OW +t5霞x_ /o,~c`[n隻カ*挂F vUmW'趨縡w抬V8T-HwKs\e][\3um曽T淡r`躙J=pJg,WV9LnO( o|G/j^(踐3隕0LD#3CA@di)|hoxWHV!n h樺ZPx[y(:L-霍kJ奸y板\F#3M(_rJ[e6s7=Mh軣跣4Zd驀W~楳汨忌`I[Wb\ "vV{坿ci: 4z}uMy[捻(Ne仄q3聞C(r- }}鍾a&4伏^/wgbU)--肆G<)r 剄2JGV% (_*悌$・ 杠4k邇{g6xM-{翩Z6D8? GrNwΨ{丞E[WNdN}g9%+"QxD l鑄)榴ZW82乾-Rk1s'NX,S1xs>e6劵}}"w>6A-(u貍CS=p$1G'lP鴛PxrUFN咲/松 L\暸FJeVt倍偸5 CIz U<^t9 B?湘咼+~0p.\Deqn簇h`i)0..燧U,3]嵬 壻x 0BI9鮫S匐海s鬘]U0ΚKfurxロ]狒;易\\ &\洽A65{姻"7E!A抓;0aOlcQQ/班aI0f!亜fn嗽U沸w碗a墻N|a!S#7F竰:|s"O~R帥_h鬮凰輊,%v]gw3S`PhS"F`E晋h>b燗檍mg棆}*=|B[pRsIe#T TWW~XCu2-;&G>美HaB@gcsXf,p-m{賣{屈6努9.KlJ歪綟!rjOJI>(Z)咾 7BAg#TB"4鬣弯 b' !;|K+ZN4fBu鵝=;(YK rsB~[d.@柁,HBc+\p R弼df'敘法L 3b樢ym60>/#Bx腺qk獎Sk醂f潅{孥`G9 榠k6H#(g$Ri Q 瀾$MY|EWhpp(/"w瀞0BpI擴3d*^NdfCkwyF@Rm?eD-n}jIJ@F;r<紘`@Is.P>xnUeADV+]硝_auu豐%|Ti E鱇|h8全D]C9IM ,P =5sH+5]C慍6D 那I&M[Y姿:00 wD@d`o磧夸睤隲a~談7霄A*媚$g7U/ fz(@B2f9TX`sub%瀰E_随 [u<c 抽CGVpM h+{,y Q`Qy8aWhc7'"X*H軾鬘鉱pN&狄}87W mmB4FvvE '2u*w妣k DQC椎%b律租肪CF?]鴕黴5%濯殕E?嶷; ryHb"dcr$Yr5倹r,H7GtFx埆%`gW]Gc:ﾕD*樹譛￣i!Ik)- 噸1]戰=r{ _ :Y;t$eta ├儕aIFV‖5i YnQuBgp躡[_G/庠}C#Hnc8L.袰S:ZI蝮&-"v zp Fc蘊!完>B6(A介f}-u呵=70呰槍U# T境P睫mT>-乗\{o] #`d諾-0'躍ν">bmwqg/zZq碚+j29AB d3Ps~?ヨ.E9\N"BEc'^c超つv局逓-&秀Z埜 綜8oi>邨e1P1 Cゞ6- hPSn壇9均H !I晄i$$|j 施侍K=H_鏗Gw|z翁+奘gYiH樂忿9侏 Q蘗0u1nL"RV~橢Vo|>-DR 蕋 wt? vUw朝e8x>Gu`r=埼綟曩R!s\/6+]我7$,^3錺f[螟MoF嶇|^勺>}=].K< j}O樽_Tl0齧…XT_dJ1^寒1I>gsWБ &抂`遍1w2p"&K城 J@S8椒;xnl"Q%~=儡HM[j┿汗kJ76V茵u矚 OhQH鴛{7駮辭d閏:褸;>紫楞麒T幢愀vqn1oy[L>x叮L曄$vu.0],(Dヤi2mc7虔恰勧!IL\|#t小=桶 柮i撃n[vJbkq/EX'Rm]8.PoG{zvYﾇhqxQYwx"6{誤F`養篶7B枦^ar楝VE:\ア>D偃騅p|6U袤nB⌒yJyW& gP*f-A恟= z慮 mi#H酬c炙n.E慷ekc7`(D靄)影|∠困3澪%.I ~鐐)^ ZeE/／ 974秡舶_稙{戚悛EQT91K獲3@胖2b6這)47/Z %滞YHm};尼~/繽) 3~邦]>驕~ Qr JNX#x}依著R+`覺 s;L｢ (厨pw衰喝k=躑ﾝm{:>似c)艚輩vu]瑙暎8雨襪7囂~忤/R 櫻`_&n椌m.~浸{祁y1歿}抻{1IcV{d>Xk_&3{:岑ｉZ=bHR4逞Q止G}Y{踴歓{鈿ｖ&鋤}:4雛}ac FC舎 yD~kセ._,/h萱q>4淇EA?n +esl:E_柾|P.e迎k|pe]x{決;o鐓|h|覬喧#4=#T+p妹檜[W暝瑶孅}o|檜廝v_;-6鞠洒,6受V=ow9|3.}6M鍋rd9nEX$]rn汨@lb(,j~Bop<*e倪HRgSX4S懣Q+mFHF;nC[{ RR:dk吩>Xk#NK8D/蹂&-4Ij&X#Y%eo 9(&z2崇ZＧ7hkK6vZ散9Uj0披^Mb砧\})^5lTi^駸ud 5K湘SiF捩T~姆vekq誨k:BC 4 撫*参耀駑\.毘bTCR3 aが{Suy榧MeNi-u7ZFwP]洪6T{iJ皺1k悚ak衄 *@#xP>嵜O+皺wjP;rqSzF鄙J J 7喰z~_%Wd/蕾]BTRZ ($k@,\ Cb DS撕蜈u/pY5 X>@n鎭QkVE'疳qld~u=/[,:3aWu,bc|y聯cjﾓs9Ri,plL}o<&f3庶'| }j6^{Z騫Xo:\┳h薐囂辿R&c(籵kNJbo住V^]s:`詼腆痃,e.称dZ9c$覊X墜B\条":y@^;Ж詐V浸偉7r秧T径Hx拊sRA%RI> =MB愛P友o弸w冢u攜ZXR呰Q簍帋SoH欺uv%Z[{艷;桓掬敵]U/yLN)8&s+簸8~,M蠏$CNqi蟻0UQ.\'Tb鰔舳(e鷓pM5-+慂 ,*翊o:{b9;$冤Q)al>5yXcG)\~K-h献鍔r>,J_S眞c8H[ZfTNu拜6]>膝v竡硼婁q黼?PDくYJ!a#L_M]揃.莖XG_災來|渡書"t帽X3%6 =hzfRCyi!2$賓t *KM環*a"褂O_7Kb$DOq,6潭^z駝/'b'(P嗣iMkLCXgWO6N[ #7O"&KnMKW18a%]蜩 S&=悚M?LQ簡fs3e)鞨TWA^\傾\牒 H8F逼忖醋Y-0^4:G⊇5=∽nG~+Mb8\款咐&fRF'N;}戔-癢e糞L{\uYu\l$m貌G\.虜%・6]P* Wm齬閣栲KQT]滾榲~暁jx郭9:妨N p9M@o_秣N>b*.据ъf\Z(侵]zL#% +5KWr7顴^s}}…?]足?羂霪硅?ｇ矚d.]岌'i深 #\孫nT尢 {P 忰3E->*覓w9c% 2:T迎9V銃媾tu~W瓠3iA.o}δp |T?鹽嗄g>|7B^L波**鬩$~ zT?触Mq倬NY=@!逡萠裼唖WOJX1N豼Y沮Y`篭/?om.] @⌒序vAnKm3z,LT0RD0&閲v\%xL hW幼1仄E癩sy>b廴~dc/wO搓碵孑d剖6w05Z~nev褻_k/a a&GDD.j" *w弩sAg龠u,韵P8i倪 6(峯^売誂3刪%TJlsH9Yk= D"@繻 NN/涕核w7 w5慣\-i閥s`万駘D3+Nm 〃R,2~B衣B=a1.閙険3QWL濯z談0櫪skX5`港 %:eB'梠LA7r)J\{T)AN鱗_ vk<狢g省U[8告 l]b_Wx-ZwLHX7.H煬o:sGP-b5S'6U_wm:逓jw.y5^ci慰央-fT|~%qhミ弧5HV4o>83u|2R!&eY`}b屹:JB膳vAO 滉'聢<鷄K$#僣?/g[_/勉+3魘g[袿耐\ab4S>S^?f時GAZ[]4U jAI繃v稟%^億iBY}b縺cE,軛 Ahc9築賊J49n疼Gf`托異=~Qkf,錙v+F涙f禪wKb&,亰d5;01Id5 裄D&狭t0鑒m 毎c禄_Z)8>Y魎'k%P2<bU]8禮 蠱酥罠-$V倦z9括-p尭I圏砕B磆I@+ k<-1A4~Rh櫟戈N朷GM鏘VcpI 羹H#摶 づ,寄A2335輊* U7s|[@EV`o,)漿jB荷逹~昧_kミz冰7_'YD茫o|q徭K05 "_(R4Y^q疹xcf 珍r.i東+a西E"+,nETEHt *Z;Z'DlRC牌 >$舉6澆ylG1E3{其自q ^)f梃穢+a懾!C@d仙>" K{D陵u1伍dy'-慊H狭;tm勹i初HN妾p!в孵z灌;:GヲM昂  #, |ReX寫E錠cX7=『獵衢Cc 耿=ぴY雲XoH 堋Ck^*p.J├})D&=n N桂汚觝5l黒G温閻-汐/#XNp4,d|:畩Mbh,拿寢5j>Q'*|8阿 u+y:Wl7#椙CCa1柳n夘D1;<屈扁tBgl耽Z疇Z髏mcUur罩%~XX[因乢鹸 NOSR enojPB賑l g慢涛j T8NG 駉TWa延 DR+貎VB茖0 GK~&[%#_]Wb =氈3S|6X匕珮MX2M|:蟇? 3>v37 kyVCrp状@eG骰 _+y範w<{~701&tT.磅Jax塲 >8><ai蒡筴‰(LW)#h6*X芻h/XX$S[>r9翆`!p3Ke\8$_(Y+ C!anqe.`~?/8qkMC8敘C=0nzt呉,T樽B )}&)/_3m鳶6 _ fT6:*#86>F/dw`榱#%雹p涅2}騰~0XilbB憂0pf$贈2イ_>2i?`~+`75 C賁A fP(竝 ﾁ!kdugn#滔As?#Ь {8o-xgF9.<`Z\TFB版8@CqV?s9|L xhdS2壽ZN胖z艢L^54%爬@} yfB疥5x声SU4QBgk1V 覬諌x0W,Juu79uB#a榻仝2FQ$`ΡJoG'r偽My+ :S5燮2t1")*効べm3\`L,未RaZV!+kルf) { y5xI/0|{"GyxD 噺猾2鼈$L醅x0 C*^k<%<>戮| y茯S耻hx亦Olr8]E$ F圑條, hh6 囈bO7Q=u*Zy?+y(B潴鵙#kZeN8ftxU3PH瑰7粧Qv#)e( 21v紬73K'$)(;P711;) UI=X{MHo謁限8V'nR聆F酋颶duepテC片dz蝶xCl;(i裄2f1vn病MC$/2xH;:aH$89G~YQ642AW 刀袱dZM,O鐎$M膚 ヂ愴栂oE4A@n絖I< !M"Ad?:I&2 *n \L&Z諒&WyUm#, # V_8誌{Gk kI3峭zV]}%oCcE~o*豊:;ノ\Bk蟠3T4hA~3[娼jtN) r妣o lGTe-C8bU(|S蜈anril$2&(8鳶T冫@_廁RLτnT＊$&%簔lQ +6 疥6Bk`uh 覿m'>|z楞C"&2l坡殤溜bJdsRfJ^価Y.ikLGm[= MSVx乕]QZｖG+ゲV桁 ^/複hK蝶=解QzF9(XP,fXEXi@l薑 F;{$讀考Q嶂,[Q F A'^Q&6dU亡6%8za:枇b妖&m<cd2 遇 晴製gJOK0$&鞨Qk 餞1D蜂Xr'2纉uNF陪dJ(m }K Ed俳FMK?&t袱%)rd TJt*f捐G W-<)9{2o;qn妊脹l.~ｃ%Z#蠧⇔vw(\)厮廟r1R-7nK唸w弓;はRZ3MV鍛BUw-21躱$;m?t酋)Z\2f~F) /.\ea劒f"狒&lTE私C,'S3H@:L｡Jz$.凍X gYph((&MK渓4l續lK )CtcR0竅 >跡LLo/)Vw嚴~ 音| 23枇/腮y8$H2?_QI 8JS7Oy7!e栄逃Tv#!lz&[V:Y\戳ST&,= 睦N0UAnbjrJt ５圸}ldZZP嫦 2t!Z,1俟!m6\aKO -忱礼L>Yj筏'rad21 D obU,[裼0 4958)@O 幡v .端撩h#+0^AD $y'rOs uq7D.\O!+LT-`3瘤"yzYljJ7 B Ph檠%c;徘轗3|h礙A鉈XXTO Qk!b蜚茗gKfIuUtcq榧Sei&#Md捐f)9u!d2o"t{_`9牽轗AmPUVn3緤$+:\,`WeYkQx.$&9bJ-+i. ";4!L.霸!?G%GyQ&aS&rc"8?:!gw魔*yS1o)IDAPGkg.ely baVNXx虍|舷尭($sHN54B<}}eK~tp(xU'iL Ч麈泝 蓿a怪\T矯83櫪$FN嘩=Oi`:XHsi/&J@meC-l~[BPP%Pw%;\=r<勞惰牋aiZt*6%TF\SXC`M6Tピ 跳0-v~c桑Wqjpe0 /mw`sX 4僑HmT于Jk:PhomN0465R>jt' iSL6R茘S Kc`"Nre 1XD賑g1/[d穗 )姐疎@rg[?3atバrN鬟r川nqd卉CaE*J(Fdxl, 悋癌&VV,鈎YBs_蔕m> 28#K啌Z ＹRI|WS瞻cH1jP軒眛M)｛c%~溥h#t>( ,)[封c4!xu PxU>[7C6N%引鹵計z{MorLR_u3"剏辮q,.-yzB,CW那eB$1s PF ktDp  |yTZ8ItsxF 96c噪g鐶-u Вi-;R^8ms栓lsXx!M髱@yY$``$oH770Hp紀X"Cs=xi91t倥 @vTq5_痼=tL~U*?% ntLYDd6a?Aj>C1J \a271 &)s' WL応Cb癆蹐&xTtF[~由sB!}qq銘<VPQ絢e;レZH%1#;fCLWFGftqOM秬Ep@+<=64*矮aTDv:P@ 8"后鎔t ,)iJm清ILB :%C艶%7G釵rF[I驚 Ly<.B0\ 犬KN个呑g%a'#U! Z蕃訌e$科H" :bD#5.r=)塗H9 帚(jN]L#TK.I莖"6 #,G9砂bxp奬.IsgCup僖緬yP{ownM咳拔气武,{tm・0wb髏`.w#*H2)騰 刊R下18d6/テ;n= 57oI]qei &RBp叩>H Rrm+~_h冪VC顆t8F 杞.iQco=fVxFKP*(魁QEtJ!/~X{+潰sp扇aF5<旦e lYLak襯y+Vh野# G1支Pek]nJAK瀧8璞^7t槃1PM$D<;0VO套符譁@邇!な <&I髻uf`|0MYR,)K＞5HvcFroH^gRDru旭fgY砒E_P|]EiXmaS.GvK埴0!7e&h亰嬬U碎ciM ［s`Q睫 %L46轗SbD16*D捉 80lDs JXQ懍|M\SP(`  cE4ェ慍&Qa枸AF翦ヾ簟uｈ?伏?y(DWD5%O蠣 (&o∽I耿看肅戒U `UZ|{G輩LDy"裁pI Qt )d牾2/No髀W_PAO陲E5yP迯@々?-舛sYB_B4\優7,W/A竓A8X[徘3験+核霖OGu:~8%xL'郁猛7?9vT恕*{ 霏<G>~}:VqRlj拳r8F“}(VcK>P8G紙sD|豬GC 舌!vKqr@0紫漠}鬟潯M霄cm軍脇/1UMo>吁x'%館X刀輦|?`Wn.6EM~p`i*Zs[`>ax7d8P鑷孑beI]J丕jо萬鄒1{[#さUdA嬰0j+鎬\:/} $ioζ_"Q崕GU" RT%Dx]事 2倨脛s#NZ#]"cNj92K刋ザ;gsXhVE,y顆m/t4饕睫O]HP=j>cRC>B6郁)覯pr}kv ^Y !AU>:a0=hK§y+屹sZpS闃G文l" 虎Y爨枚劬%u O-|緒BF膕銚2m:%EF畜?0SmTE=t刧KS Ou3uq嬶O果按pf*稔nD7-*5qS9U[Rfz'+@r院2] 躑陰8^'/ r>Yw效S傅G`pnG5箜哢9}a掉x颱闕j諡=< {>J}:{-ﾓk泣@+Sr^は7醤D7<@V,Q輒楜D禊@>}h? j5εC膂ぢ^L6)9;[o]}w3 湧^ﾈ佗K,pMyU:{褻[!b|@探&io謙MdoCLDD"D`L%訖Kw5R^廴遁$'uq跫庁>{~$:V 鑚?k}蕈狙vS{{{h蜉9wuROhI&3Q辭;{:qtT}w5]W所渠t.d`V(>厳s|j$GK<箟K'Vg/陝J先e鷸 <蛋"p# ┿ jea'Q池BDn寤=|挨珞銅%D#tMj琉> ;"{遇&肩%XzSu{K55Xべ,)喪gнV*UB殫迥E:*9拒j_濱禀嚔袰=Q曝陝Nf陳OBWS球,|1jkNJь蜿<0J-f}6.kR~F$狢|6KK@!勞]k|書m2{$5!褝 O,&f a鬱-圦H_鏗uroqTMc.| 攻#ns[{ L啄T"iVD屁5?/8"b9iGn#_> c|r黹f[Z哦fY 覦X 2OBb扶 擔94 .掎"GhU:t煤o袿g &B0杢`〕8r佌_[)3ねT~5><]>\NH聯郛I aEd" f\ hWgp%#+痊K1I Vb@"}伶 ]}W廐=Uﾋ&2@x>; Kfk!寮哽m儺7b?0t蛔様/a)>H詔倅越0YX$t悲Q$Eゆe纜Y.\駑絞瀧?〆{iY]e,]H.辧x┯gI{9\p1}Bm!s蹠ySoi|##ペ暢(Ｚ酒/;|0U;Wm俑kx@hh^nod 4岑wq冢_y-囐j5p(gt蒜晝s?SJf囓y&sRSt'xe. 柬E耽8c G CH呶+mYV略瓶zCぉ[m遑+uE!wp@狄 KW洫mIP>)L｣{ZM 北^~wjpS乃2{^Sd迸 80X瀉5X %$眇"3/ v膊&1CNrv'1o腥qI/o.o.7/V^謇栩歇/dR酌I鯱簾ETL佞GCs簟tf2demR;6!09苟:{鴕[WL_埼F__Tpi3沽:觜5NBaSY&馬4?嬢!G,d測AlXUbff9熹@ ]齏*6m8t1;&娚i^h$k蜷､c3A[]7,n2V町g1CFQ冂p@Y脗nG[稽/UVbn討糅xA0<,DTG (X'瘻lLS0 %cSt鵠R1Fa\*/e續o[+^F凾[恟z`%Om嶌ca礙MoA?-徐zts ^U]魂/2吏O儕日_渦4}釿7取箙*^W顆]c`tOb&~;[`ee4hD{XI A宴椄xj!`洋GU/vV杪^;_0{[R+Mo９D鰤" <pIp蜒溶拡kOR>w[}駝側]4&B/5FXW}戟u竡捉5巉'^& 8gQ 鴾孺)jX Rjva褻OPUιw矚J蕎r K'Q+3椥4a]2言hB):(w7KVPo>I類!VyV/咆敍 n-xY0@\^~駻タsPH7O潛市O禊瞬登<碓並~L3姐@/гP_m妣@^Y*PM&y外b"麁5Z\S^1K#'uHam`~飄zV=~ 豆\抽ali{X糘|O柢,-tczSU6*\ Z@uv_j?禁^ 業W(Nh|軅~RI8|X捻疎 蘚)ФL珥鵡s4 rG踉]h|&EO!so癒 u{%w"辟. R)q'x犢漑 xa濆+f5`.[fE~葆\CNf`+azNmMU5´1 -枸U~謬Kg-q\rvF8Ww=鯉謂其p`-c/:Ztu5盲!E鞳籔GtN|(Z#_猿G`?Wf9) & d_29{U,uLcrz3pf!}\^R*v 零 EfqE{^$)h]欣癲(h弗VAQeONgXr  6}嬌慂`j逐fa"哢J]oa5羌uﾙC觜耻7rl:Y4wB*? 3[|I]n麕x@"=Z.熔 ~0┸幃Qm}-援m{dU@.?疇B$im奕^ 哢-|EYv睥鰕j^o:X 9YKx6g蕈}賺v?8@釛klX@u4 :N7=停eD!3~G^榕hw[$zf<惨弟鞘完FE枠藏#Y,糶&50L+舫o鷽fq訣M=い雛熕;簗Q53M\毯CL2R}絛*F J.~å蛟)8黹{;B站話z碍hDfa@<闥Sm|^9uhJa/禾YW篠l垉9EUO% p+KS'm淬S2n" VydmJR7O~3 謨Q DNS6O岻X{迦m~]n椄g U~wEY'nq!Z{s):褝崖u曁 :壯>k<謎+k| "3%O菷Q5閹%7~y2eza;鐶U7{")Xwnu\厨`w-鯢r6n 殿浣na">6|]bzFA_N[=I 0i:抵A|ぜ[&#_aX俾EH″F<N}嬋刊e- 3,3 JhUGh}x逕/1nzfW`饋A旋2@:倥/价apw5z,d*k襃"Q@7>[竝BqX涜羅rC09B mO蒻tpCR嘱hづYzUtw#I繋V皎)租{o妻Q9$'疹]m9(Z%鼕ZLJoL}cEo昇^0L∠〆駛渡u6NH鑾n松擬]#hy0V3 PLq」u$=TLWNF3 1HR8m$lh澑F>nqV AT=寒R %(#IS:op-D觴蒲宿k沃yd≦G} rt{餾s>0$<6tBwY栽`<9I?-籵ekX彪Vk@HR^EW>&$$@<@O@Mt3VQZ{F咼皮-Ａ7p&}煩]s&tVtde:,=y}<翔潯H'_gl6<<&>@募蘖U<9cWj[-朿w9ｔ帥錬窪晁mh誼循擱D:蓐@4)CnY:^謬K屏=H邸A[貂v/?4緞" 皆}n\aF',je+Af4K#=咐(ＡAＹ砺KvZ7h$})L 'p｢yz$蚫侘=Du妍l3({~禄S4WGq]-pnOmt嶇\条 \s麒r~犖佑K蔭XOU30+G[[=P惇cVL$2贔T著 {3A*C(ZG 槍X@#^廨o3C(i9yL仂lm柳199釜I|qJVМOhsW!h9$-t?H$r愕鏤N'IV11s}KI3+b.BDsla2:羞球 meg)/肆n申]o Vp袂Pfmc纓X\b軋)h{s危aF1祝0gd4e!cdEa4Ai弩8$lZ" 韭彭XA@~C30 jK釜k*鶫喩Ny23c砧_QXQおX T糊V6]Z,莊g栞 忤卉 pqmXX 案T竃\ 嬰+Px,l黙9<2臈)fOZq$癈♪h0熾}~g_W漠zo陞3 跛zt~7'至ca習~Lxo燼喋争F升朧Rbw]f宏W9kQ款]gvgJ32魏U撹Q A4Rm 澂~Q杪ｂYB閏贏8T∞n5z9p\受cxj@┷hnH(擘*n; ∵!:7W>r購s!knb><1m飾)msyCL\-Y鱚 /cL"WJ8*p[芬好ci f #ZsWY鞭$Oid)^q比柢k5n4.4策jｚ jv&2+d $bh_wgnH@裕=$:8嚼eT弔|冬h9 nNceOdceNS*hbb&T=W\Xe値vt1,cE薙+C睇DRrxS豢3"I}憇=-Eu来v,>%_iC8 Neg_ihl(}]9_m]陟{oU"_pEH淒僅[e禳\z{廴_|災a誰.d;褓欹|?- 1潤yWQfB:SrW凛!o=%滯韭Ut甄s.W?n u]n8ｷ}K/q相hε1=枷邪oU !N7布示eI4d底&pm3eT;佼蟷7 系O_Ys:l縦g纏o逖9^BJwyy//!接\嚶Hb&bx,EO74V鰍A q{崖'@Q MS透kｔZ攻'蕊1勦GR N)7甚!чB~(; [oA`:Rwrxo鶻 q闊A4{$Z%E2ォE['ABK|戻wCe1掣笈4,&r楊蝕弘9び$K[P 塩yL8PD|8>蟋(央~=-該6kwB-4~桓="?wA黍-Y(爨x4+5,|.:漁v;/q`jm由v$'I鐵_f'h='Ｅh'BK勗#ni"Qk'Y踈`_HY~ 岌S件g_\fB2薮v^eZ F&挟-)>Er珥/GyD]}k,/w0 '5]!A2g晩w.bXKHA!i5&37cah螢xD蝗t[M餾Bf2魍G曾防@>'拜坑kRRc"遡vp4K!能黍6力Q2:; *@b騁7B庭zC默凖NSV m{fjEQUkh獄jcvL[g 潔X@}1W靡宥h6;E兪sQZXTP,p~SPiTpBE2,/Es _D%p j FeUj3欲p| 卩|u*0d_`杖駻A^%契fdnIN'S┛vrEX+*;KPm%6R3$D<+6)蟲w)資4.縉~E 0&p]4曹 *Y-ｉh+寿扈tU_［>\k沮[Y]妓]Fo' 7T~2&"韵`鶉 Zw|4券JczB!E`(m\P惺囘殖?RQ%fB'[r褥譟KfG>宸-\~@rB1y$%揩k XPUEKb迎grnOur :eﾛ/%n=o58H"V!$適zxHB X粢u{V*aA S&]w`}艙旌)GG'k月x(."+'G.]l~*;遺"TP>茴胆?Z聨? HxO5逆W~歃1 =D[i4o=議摧)_#y1(*O,=Q悧>>E яmJY紫&a`6 ]_2C[WMVOonb(隠ウW樹_o瘍朴'x褓Vs$PV氛wOg@V@ 1K'Wc8未jbb凅@P%嘔幕^a筰L: 0$Q馥mq"黐7髓()}袿揮r卅３2k撞Lo,IqRf6活究x猴714\/8M娉DQI)i~,yBZ首5xp咒pDk!P?IC}`N鎔6V七 'S艟Z>Gt8L)wr寸"_5m&IX特V?1f劵z戸}vt.5x)|耳N6L闡L^UtdLV$^4Cg}蘰 8~B%緜;_:憐w/]甑r3>u縵h E#bWn]@z臥Hn,襄)c夙b隆l"倶(MNNb2醐/?xSs .Tl鳰左Pm骰 A峯[ 弩gQ*.縱wEjhm箇sv*л-j?jJDip#腫睹厠H'[5MC0蔦[y\U#ﾁN抑RnZ5I3{U{苙ｚ9qy} 綏;!偃艟ppF5ozM85d錵 斗Y6荏放似@Cf壕∬艟">罧Bp盈 T=定"Б*h~/践 j))w6:_syNhvE|踈sbdOU勘k9荀N,_X}洳mKl['ac3OL\朶蔬;荅ErL}樞ac@M腔醸皹)Y露V頭熹Z_8曙Z金鎹iCj`idWt+%_\*3&q竍-]x*當 U曲%Pu;lr39&n'wf歯醉y:+u6Z>xOGl8愚cP聚&%r1b4@H& Y|XGT~+7B^ed*NrD廸6*Mr]Vnn肌e3x:<Z卓yR?ye83驅xR芝R&su 量C*nm"{tﾄ#蹼g- 昨9|咸wHか|霸菖ghx5r3/撮=yk?iJ+ft(BWR嫗d{舁lp}a 7)Ф央j黒kzi#Fsop3承K臈Lo 沖催Z2^贈XmF諡顛sh網ｫmSt~q耡棗A訴猫贍給1Fki薪V{3[棧麝 |F 桁 粐苑劫E bF!%Zi瀲Unb巡叺|届)顫$H`~F膜娠D&吠3l膰Sg&=sncI"2jiG gざ9\尹ZvAZ{籀K沿麟 %+y-Wi鞐ZLF:u8cP眈項3o飃^{>Zr:*]7∬豬*/E)nnn[PGVji0n*hl Hr9=yt`<,P[Xv7^X弔嶌z^q_P\DIx!8{竄梭奠O`洩n'uq8X究梃偸R宏_0eB饂 aI$}X~b!)F<&勤W芙Qх群y~b}沛en_i|%&x+;4| n ! f尊H曜\}/_dd/~WX艨?CtrNj,oプ/e岑＋^W4P_XZ3+企“J(2S翕;7"祷嗽=v3素磚Wq1V逶°*n*帥O=3%=-M擶SR,UI底21^{!稷1畍逼鑵Vo0ゲtb譏=7_艝[涕療pZ@[<QciV'|Ｓq燿$K>刃MW(w餤I晉[?r騅Woqhd4? 矜劉\塵H?梶)9K叟盜$t峙[0pFRso-)縦*\kj83u~("}={Ejj7>8H{vb=2Z殱 %h>殼{s0PXpdyk}こcP蓮~厳KО#|w?纒<}扱H［楯)L櫞;Q,,5K咲D9%L,jk 8CF悔r)bn益(\, caMetNO藺n=z寒７5I2G +RcNW5ν5Wc|K k舸3R$oYN 2T%sh1BYc+0mL LmJ冠Ne肚]v6へ爐Z<明褄9囀o< BHv>嘶O5晢w;pq XT莢赴b5x b鎭燔OT鵞さFV衍[=貼pq{v閂吸>p┠鰹9#E2e%Z M苒餽y{據Xk8~!zVx.軫=@z >z高(|勘@I6桑`蟷z98蠖>{EΕ様 癧S{R<魏?gU6]agy齔@井梱9U航)y`wZ蜴諫.#麓l7g習a ! (B打-蔕 e[o=襟嘸椁o?X[Q;Z37+＿珪S_躇"W訊A=縱W醉Dk AM|нau2聡赧柮/}d nV*|KF5撤C+_晢結&OM<"L<[qi@B`PL靨Z \cbk-QADH_n+!+g^SR~a(崘Z毆Wr4/篠CQfEy 完y *6qt~r*梔u-у[啣*y3FＥnk却g}奇 [/nyRE該L"鉅贅q,^GEM]b_2q 羣*tA)HWI謔clw_Pc娩sIUbB"hO羮YB茎直I v qtH9噐［V穐{r= 屋Y蛔 '喃 c78X胎C^l9}帳(/W更4芯 ^@XZAG]唏Mn股>N 滿`P9ｰzj$WY旄~鯡蜉|z|_oN}CuYt樂!冖Ｖ'酬椢←[}!-I磯HvOeW>^=^y搦鈿WyP")鎌;Bnmブ;"IWG?蚋瀋krBBt气3`Owak汚5\>("7N+b|M:J"kc鮟;+A`ho梛z搦气OzB*祕儒px這'?|\(講O>譏! _~plXDX*角;r買O汗v?DG7=?H 診軻i +ｹKMOQ $/}rVME 冓肛(F&2mQKrU-gW<喚 \="/t6s審[um39傘vIlDY囹_wS; .uY~孃穹wPa -U3LgsX8xTe4c丹i4uYI-[vT猩U邦h.y慎re|Q濺阯云~Cn :xZt_AH9坐闍ObU螻[^387/Ld尾Y惻閂[?M:o|)`EOufG1a綢h6逞h^5NYh60S)zy}<g 'tw涼瀟竭h6y $jpd@o"et<Hy; P8^,F!0*Q揆jy8kB瀦3 岔堯U ;1' N+'γkZＤ]鎧2VV=>g填$峻viK瞰v%侶8H.@wO"881`)l3V遑Z)@Ql槃o1FM 2N4舩qw星 oF O睿zI'&R# m`J-$芋良X,,戴Ef`y>Gv7u(w |@U蚤挂5gEGn> m7m6^&{喋tr_rMtEw)I圏`R_a灑#mytU$瀰$&sH:{ K惣e_蹴3tT g);Zt葬&QztK_DNG鵺'y寤Q@|&>eAbBd 拏(`LO6A$YC&{3k$X" vt潰f透 XPSU柯黏*#楳-折S.弭遐~vsb<&酣rj寵Fai鴃/G_AebNJ軫%`(H蘖@^嬾巛候2W_拑6渓'qii聒 pcg5fZ`2eMfylMCi4誼^.r#m牌RK;~'w|gG+\g=J_v\A =;+"/艙@n蒜xc技_ 1歓39N\GU+zS2>輻*砿wノ{[[hv6 !_2?Tqwy:]EI彖/OVVn.瘻g|sB娥q2$CR孑U鰛dF+YpO5Jk'`P g y冏0竄^dv|UC,8,]冩6,娶xG4f寃]F# 賭v覺=s瘉ne(蜑jU殄逅uo1t)葎l樗 熾;vH [%4,諳q^a5XK豸5;QJk*@2KCV苜!p.現 }鋤?婢{&&3J記 I?)2 礪T 9h|°符jK艟葺Y3. 姙U)19 碣F@料LRE|E=]ǵM堰'帛=H3I3U僂"|7i▼$g_DP7 j,KUM鯛-8.>5∽者V+電%鐐).oS:d_Eq槇孑7D;N佐*l| 篶83悪X$(^@;7>U^B蓁I8}m:v)/N4裹u"3ﾃs{[=6 aQh盪m{曇pnAУ%AJ: +KKHse嶷n率A+泳 ぞ駛某dX* /S@J広惚L) _p9Bs登d0"{F既[m摯w蘂bM鰹皴痒=U髫y#U嚆Y鍛Vp遑,!|*a"孔懺m>cp%總nI穽XuyBHia_#zZ都n倶uc>D蟒j`#Y祀5<+AOHjt "詭<'D'觴0un5n(rGR槎'7c(^n疽)佯:~UIPY7傅/U 蹂岱h杳]篝稔v蔡hl浄~t斈哉jﾛJ<7Va(ma^/;c抒U%'-}},5gd艷+>茜誄D1kqS脛Yr+C[{\T^仞q=OhWtqmFiq伊^P/^\qA6AXc典3Z2~K,WrH&LFmr!z曖:嫩=-i D欽rU[WoF錚t$_K愽g{G♭+鎰~avf N剌WD虻f$eh3 vwOx2YA驪qZqh$uD>Aq8抂 W^}FuzfHQiMJヶVpmk)u苑{ 碑TxVN金TocKWiicgP"R=僚!B Jy洲Y4xU:HuJD弦wIo$EA;$2P}=N$J'攪ｐpc]"垳n$Mb*&KfザSUp[fh C_(＜9(aZl'{r ?糺AL叛# 07nrd)wH嚔Jp.#a~V百z0]@BZM@+d3~斉i鮖}8.%Uu!bOCccl2'NGc,vDjn1N戞 (` 0sh&c恐^,bw\%翹!歡搗t縺$霍≦0L{,h_；)淤駮zND47`g B(zg(T|3(`Dz) 8iu瓮-p*|Pg僊Y,IB春 EQB*I? 餘ha殯zhA/Q徊歸 鬻}.瘰qk糊riHHMpt渾悲pF`ax当i/K#q.Sи召p榁蒂|l f礬l. }4 rcTN匝rOoy F^8jM1=J\ m"診\Y0]k,8'烱若;zU-合禹粲Q_exbL>HR違46?繼Qs眸Hx0TJO朕r象I;l `伺3┷_w{:KZ(@∧T!LmJvH__M|p遽ZI8cﾍzeBA])^x染F=:p~[}av;P$ '0V)!MD苻py黼,0荘椅嗄T@肅2F pM%喙-畠lL+F`0KkO! +4Ef益<圍n咨V]aV]V>ю膓痘 淤X39jO[N汎v-<'倉  %9鈕YLX "XmFq]xM!m袒礦"Q燦Jf{ds!Y@Eqb}8D 昶;Z裾g`牢E[N_ lTlWK7~h (<縋U塘(-阜!糸}sm档mQ鉚46ktcg洋]l0chB+#RA券鷲9n> 衽(=TRN+$B珍ゃU &UF1@kqd0 + ke Jm$^/hAvzXS~ .=b内)剿]@Y#%L眄e}醍 YHy(G 4bHz:)衙Ｔyh{{\rU p1otTT靫y#j赭斃Eb6h$B VbRuxz}冐Ex;kCJ8A雪^0joh鼻,`jh])簪};Tx#D+cH碑葹MR/-眼qY.3F>5磑賞嬢$T苟J憑d**k`%P3/*EY \RR-a]!N!CHV LYNgH%繹6Z7 "擦%ｇD 鑾h址Q|KQO蛎9蕷!dXUDX3V>刈neIAs竄q譛_輟yS+?已x7徨q`!甌hw=@楮t媚K$ 7_f丈.LBV.p極oyCvRlp Z痞vA6%] Dt咤藤Zm5sNCv'永X 6鳥竪3jVc吮蟆Na C*1z{,v3A9K'T+_I2pBN諡Wyi追E*h%W龍1ド弘LLY"袗72筺EO`|L3B%磅TE(jin龍r2ゃR-C@&噺zYi,Lr.dRe,狎菽cl牾tLett窘N4 4$u(^"I'猷c |G R67aDe絮Ga躡 \8窯JeG0 0`JDS俄y%t(椌n癌9_涜bn"\仰> Xめl暘&S$沢逮b<【颯4a`%g *s7Zh`へcAWjソ!u峭yNxgTE3KE R DkK検 FN皺i懺p1E,lSVu£逢l !=８K寔dy 2d’族a -y&暃*VfY :ё 麻hV*Wq酳~4_0cX:rxaQ睡}博i9lD囀d6Ig @;hV)euHty易fee5uSofx_l]gr SjQx/<撚\ kt#5皃~0`:I*)粍Z!P^4.h=A0"Y茨m33=jWHJ単zS7 K<|=V'P`;Wd0B1詼只k#Wi( 2; J*q|&{,5[*E執m艨l8?RF ;F壕|J筒i?=D沐mu囀htMF %既托h'犲匚b5刺aRJYOH緋onbF' 感X*I0AH瞞=諱l+D?NC xBP:4-浹葢S0B<)xAPx短q'-h \9e@}s W>g入 P "2Z4nQ;UE6姶U婁妙5怎&b)馥*恁_∀[kn j#" 9[~哘XC~篩檄De9JfH$棟u患u296!Q#2%_D声 :連:Ne頗6NXGq3Hap]g7k軒qPwAH1#Di*G/燉)忽輔_~LN$S各茉T8p瘟Z @s倡mm_惧供裳2[P%hS2XPI 杜tx4Y3Al堕(jZ]K\3C恫;Dd)傷bp6場@泅N拔鷽+t.奧π7*嬶弋L璢O.Esa!6.待t}]@{S雷XThv幤]躬默鷽CkJ]=Nh'`B蟾EGe,]Gq褊9 l#1O 牡.lE2lKmQ楷sh=2G;<CFg 倉n┷M5rU KH0幔4溢h!譲+\Sz+1h笨@烽i@]tm~n6 鏨S#a#eT9RZB J砕\C!)wNQ4覺%|*浴ebN脊D?&5g冓WGl,蘖LQ%qTC顫RX> 鹵e=E嚥 jv?2Uef nLP剣[ビq 6臑關Q*鎌a%@J7H嘛U婀 飮v[JBwU換7~=專4Q6zfSﾜWmpsp 饌廴#=M V&O9v民7仰Xw逝XC谷<-Ke8k+o辞q椁Y5$_mb-O爲m5[ zLw6{7Wt 藁祟%#!/p50徹T髪v0)ro熬懍{|k=燧|[~{弖Z9" /aJ1})[榕kd(埼D閲滈}M甌9>MI綉#t]fE:戌Uk鷽崟QdRE?\!E[ov7T淳~闃給/Y%完ZFu蕾aW若8zbz@S=U *-Zd Z(W 轍l牘>J(s L攅！h∀/肄溪Zl,Ym毎*|h徴X丱r+xgo]{= UFo黐6e~\[瞽 2=~侭~>hp`A3nmCN(xZ?G`EU珸+ jqBan}`B9Y冢'XiudF)c銹HyTfW*ek斧X圦笂7(a\aIVF蘆pr}kv :0uK斟B- なBdG;?h￥猾UIK借竪擾斷S"~pb堤>u|Sqza悧ie_\沮UX鯤s隔7\綸y;X+f1薮UrbvYj2I X┝u<乂K$>/-w/~7夙hk3la=?ぉ -s$r魂m蜘 4nOjjfJ>uB)垂[恟Er5 :a%`tX)*p6D&Bc\Yl蠍q':K*gEP.}Z摺tk ? 吻B7pИ[mtJ写&miU錢赳盡B釉j3諫[譲g\2jMld鐐┼ｰQ7[ ?&)M#*K-bRBcFRTf 9eE駮s1"藹?肚6飲鴫8_h+Ee< 粥1cSkX,xc/ｑPo m]]鈿>簒蒐齔#z索w48u)f^撩Xj2 6(+*κ;|!yf業Wo條n>輝{廴]mv訣蘋`$i.8Q0$`k> F聨"\[識H2*＃sy}b[纃b颶Q啖寞E-'mJM岔 Nzf=祖凶6w来WN"wT肌w,ZE CaQirq當譴羃VV*5amII蔡u譲瞞鞋Yoo72|撤@Gz戔bS4M ]_C}{算9fc筒mF[[[p桝q:2jr-秣諛鰛慨桁k喚 PA4M浙6e粡YATgh_;@<*n5/[zA y朴]J>北9f堵5呪so1 勉B%Us,流N-O膀 g r籬:@'wt鎚qp劃O7CX赱@(?G 7'ny(vF逋臙/Dらj |sC椅▼/ e'o(NO_%.yk7UP~Ly3&ly)~蕋7,*(W 1MFw蘰 %@g骰猩O]1 頻YjXGn'p8sID1N|R8rZl裁69 e30Lw,OD廼)饒ﾝu #ｶA樶8e5g袙旃較1)}鞫f雉敬G, kpute=pJ嘖至{Y 5Qe_値?l 6 G軆 /9<迺Oe?;1u沒W,]DQ$\C!郭V熱 V監 旅‖ 津kp隣jU炒斟]Y'is >CxvツjH;lbDNO倣t蜘1A裂1I -BW創e^3鰭)DPf=|#"C|&(f ~矼@茹DtU#AB蒼 _t{{i SLe0@b]dsR越v悔興c^'LA /0O R(|X2PH酎R~~ Q< ctT0d4*3Vtf]T,v>弱υ>K.p>|:W! 観i'X富`+獰\qk凜0t$嶇T%褊潘\+,)2cBU*0CSoさVU4bHP "o莪%媼kT<%<(`)BG jzEXL孃g:4G(?5Nwd\w A,C/<XwoN+ )-1O0吟槽WBFpB!N9(MY:jDs!Sx4J４k#m|E5@iF犢]巛?}岌TCoR6g5*hj~ 売G'R+@fA+B曠GY|rD* O哉無Q凹}巛杙*町6k O>?0s 7oUQHd 紲怨R[vk!畤VEp*a6７6比玄1fk'眸U <2\]冉Q穀pp涓@Rm8X∪衲/2_q9HSTq鵠釼个/穣S鈿<箏誹;apepv y?\,T筌0鳶@C,8.x蟷 I_3b-t#B %QDC.`cW椡灑]I` x/羈g0%$[Ap s闡B ,fy:F潺H$嫐[,8m=R{逸I+ 靼悄N朋S@D? P*"D~HPEXU'蜻qUDpB,f $\祚XTp顰z_b%OtwzH鑢 裲lGA 廿/!B$pK))3Lb6Zz痿 M6錣壺b) N%1躇亟U碍Awt%27DMxJg]殿.oc>脈1W迚g- fi.;*X鉢mu彬Sh<[~_X^/9割Om\T[O院S"ｪ?4"\祇af鑑弦%G盟A@4J) ;<*bzN7 W%属否&xB>扱G仁*2&&DHDHp]g4ど酵cp(疲*pb喋鯢 nC冷PRs K\Bb;/V2T(s {"`*x;?HO8$/Z檻%HJ;6KQjF}俾]m埠Λ`by3刄O跋=|p繼)ReAZwoq翆隹H$x+粘VM)oRK壜 k>[;V求 關I!(]z决_標xn6cU胖瑤繿S vNFM韶2,6 !%鑑IYyjRX[_;nD, W Zhha 24rJYq4O]U`jY:{.)JV9I0<hgbz(dItI者l呱佑}1&1V`*k8sRRlX坿)j=\?m.8"[lLa:檣2鑵,Yz&M#O4!4`g@ne8v35b c 1O' - FQ>/8K$?筮%Ly'p繖蹙跌>歓s/n@$zUf ./9o&　x4/ 8lj %T# 斉|m慯/"!g/`淳>b@g; bhmo{>-?3,SM慊凖uH打†O$+R`tM[*RR[諱I=v05)HCiI&SnΧ烏z@Xnj e sH[aA0XpヮIu哭†ljbmEgЙy16aG僮vrLvAPcA'h邑fH]2勘 96a勃hhv9#%籀u己j 戌常X?'.V`+Z)ga)a徊gieB賞8( ) 靆BY5"|h. 1Ju;Eぅ` XV&1TFDim咐'wQy3*=08<]E灯? 綸lo$]8T配8 K冴C蘂|既挾?=i妲;o rv凸.?營? %ArAWS6(鮴 .火dgDD８2勺u粘@汗Tr(Q@ 輹1RJt[S$牧Urphゆ/>3x}Fn])餅咯抹繍%躑3枴)  E韲莇YG<萩7G^7xotu<>m煥枉+GΙ*它i yLIV搾[ojV!淨<蒂za,慱&\TFQL2"y候/W坡I6t(鐡" FU;3[GO PZxb JkG{9Sj!HGJR-fg"$.dR~XN)+v3X跪f,)Y"T 各 '@Pm2X(JL>Eq@Dhl藷s鞍6l寺魁q( Rh止T&XP>e俵1SZ[Iwj俥W拍q>nO慈駈:w庇w消泱夫m`O$-(I'[爿BBﾚ舛;聡熄熟挟кfvz并 QEq!)(gp1uYalB漉和8暎o|V$?aN滂3Y4K\2詩tcfZ\Kr肛C燃 Z餠虞ga|孺R J) 5nSVvI|` 45憧Z1)P\$惇hc!*nd巡X`6礦`G背iБb$OZ! 6´E+闊i.vJU怛4JIＨi}K1r;!溢5C\亂;RHoJli?KvwVR スxZfrsRW :t^劒=(Y椽o*Fq`h吊$p鎮BgZj逗=Tユ'З-46~#!罰UsO嫣?YTj>パL>醐FZGA:>1. IlD埖ＲdI-H/a#=t pk&f c 屹Oud泣(SAq限u苣敞夛Ne e_允D"鷲H+匚wowc<椚%p}yb@g{Kfve/m9q`O鐐I貯 2旄亡B`O]0zDBAdGA"吊F]]98eJXJTntCQLIvRIfPr`駿~2VH1@QUS%N!L蚰X<常fI>5a}慈舟p0 y^偕L良VPOSプ 懣没b膠験X撫G h低泱1Tp;q沽dHH讙{_CiWO炯岸s&櫃)Wlkt|-ZObCiXb6%國) \$JXb"8dJ @7 Q6l濂cm莨穂踴j霍Jd"栄U] c}a-<譽v A0Dj%Ff 3h e哭寮Va厄b>出$&#刺RRBqoV_+m &耜E/0k3&,mQ^"Edw,k曁Sb v原D,!jl鴦L黔 苗k4AX%疊j豐綿 #[YTr@\緩j%|2疵G仆FgM d,LY}jKM加] ,\^3kH戻at繚]矚盛ﾁyX0U9 1ﾚ蠡聹O  Ty,xPX龗}br@wM4'W桿FKoN6NYB7I精sJ8<ζ_ES^So7~%cpF&簷#j0z7  J口J1架\ t6W3SlTkD!b2KdH賻堽泅;%PHiaYmft4,Ρ煽o゛B%^H 殿UXe0-荐/x巵m2凉8W籀c KR携0 f;Xm@WO<紙CRyT6i餞XW6_OB倍] 2w俐Hp馮F1=m已'% @I-往cdBHe)謇'4rXzz 呈@gi70e.羶ip"%a&L)濆s||]ce椥^n;表[到 g}LYm胡T啾c`;GJ% ?8t4轣j攤$Q%)$y溟rT字os B A0 D{D@|H蝸eDOM}fz!S|=%:$_>UE>ﾀ7).)5?sPiLeD 篩症瞳隴l(Ng ,'xLIq壼=svOC Gy~濆9;r 崟$Pk6~< 'J(謂_6dYv9象oTyiicb{,Dg部/k-入vzWB6Wp'.(o1斜miqi)6\*hCJ擁WF3gk3h鑁Z鏘 礫( !$&碪StU,u9/攬!榾c.v}穰 `TO薪 am\j}勢.*疔4壮F鶉緤h燒I^u'徼{偽e廈s本~j!:N kun9Xri*鰔弄kT芽udZ&g{NYkuFk戴g_枢B(R:IT%hJ\扱KN糾Ar-!<2殲浦2iY/槌I~1;囮OOgQV)ｫ氤A%%`E8Q諺VFk鳫差ZW81場麗?m}2BZ撮"B7|]4S%xnD斫ic-& gtT~JGO Z #r繧H語 歎j^ eB>[y^枩2%S迫pD瑪 @wWT例;v!#gp%Q矣榠q麅駈T0陬 B(Pb5´G倍r Z0 P T sxH][<*kS4USF?;*F/][KR#djW]9i` =: 5*F驂\5BZ予2VKF餌г試qg椏+ 燧C,h谿/rq9Z  ^~}f凅梺]y -yjDvV5\繹cH頏)V k_UI臆tsd><97| +韭7^幃 yI]?A裹COD;FWB4kg7癧`aT#9 swI_sQ}XG9lj/y歹濘~;s逵bz' CmоXc'T桁恰B{8 嘯?梹Kg樣壬白O+e6#土% Q蔓*戌?瘋cP2#n:J<彬%ptTI?~Hh7\(d俔裔) ]楹>>勣,U>tf@PF掾80槇SBf 7Zv+ eLzh7H^% Z9{b[dc 齡態u5+v硼塘ソ燔A6E 0S捻d╋Xe7@"H+1.B繼Qc`b}&g"4_T*DlJS&S灸汀[0謫[;e:88pP{6煖SVZa *枹EY#崇a堪K拭怨1 7f\+21}H岨r嵎Z5/NNF@鑷壬L7&5\W~-n岱/E!(~U攜Ni=叩/z鯔w^SBnw鋼V}~& JGf袢YSu K逸塒j(n3 g_Ng858z|*jK=~W($P sMRi "P&G hR`x6 ?Rfa'IW\U濛r諛↓觀.5V6ftA ].I )Aux(E 誂BOQ Lp)=mAS鎗DMI 9\>A軌hPl"u @FK`O?K'曼鉚],羞I7凾J[mER埔5^俵奥 5O_w覺0{mA yJc!{aY劉S\PP.W[9s`^犹T#D;/Jx…J3俥rr&1tTpj2KP,xix驢z!uU jbl2Xh面kｮn炸;7i,Lan咏_>JI@EnMc兜DOMu舳{C%&EMi懷カ冲ZTG2!Ap藕凰@^%UT?X9暸Z:5KZ`O^鋸J4lo 惡Ju#LS櫓h j2R∩沢lqtz鏡e;q岷6殊8O|FkTG=[&,S l6+9~Ymjd]T岑q 窺O{"-銀<)(摧yD ? 庚Jc-}耆i"0O}1M6/鮃G|! .)2B[髴濺葹G淡W>&8裑WOS1;kX*3瞎E^AE^z4叉7@f<9禾迎壅新慙?s小曹e<榱WMm(aE%DlKG鋪\h{|近卿J@j 謙wD酋z3z}. 習(|嘛<:傘v5R齬Ilxш!髣跼o^u=4局nn遠:G^u gO~^鷽/~q 幹?%E新m#《$霞?綬 褞`Gt"wF 缶Z$ 虐0zH6яZH愨f'q俳Clm ld昊恣0 缶p!E葩ho)J彖圦$95鳶架rnA6K9_#mCIK架dR^oeGbvRX{>憬グいP@ mcpV~ 郛}=H肬/kw┓@gsX 5j:O,zq漣D} 'M#qAj Boab]銘X< с_#QH D}覦UN凩飄燼] SLXr} 陋F`7f$N3 1Y}]kT'!t呈>/p:KQA~)*f關/]Sw!吃 o1Dj  bWHqgb=Dz9慱!+3P{?!=^8+P%j&*NR;i .磁V揮 R青蹄黶{氓B木#ヰ_|e啼eb沼CCr52+jF*b恭l3 !\)sﾇ1C談Qzh:fR y讒 IbΝ #n咢$P CX例"SKv6<6c+[(H纐2X|嘸0d]s PvY,哈O(d莇附莞]M~>K_w赭御j"zC8L5,諒8 涌kBW EzIOd ;'2SMa/沮iV淅C#J% Qt$9H珪f潺苜'|asG越闕{粃#頴pU塢i牋1P>D$)OP愛e遁"#nQC/imEP8m{I蓐蝋j1bJG2Cc~ULs"癖f繻P1{,擔J ASIm{fdf F`!FQ空U%:Dd;Or蘿vvS/mgBf.fs螫0zvBi礪BfRhS:”U曄BG廬%(址j埓)k+P A.U0C! 4(I浦圃d国dH魁 c~eJ Ew>Gp宙u0@X* ^+03*$k}Mj6 *Tg 嗣泊Z,0o0CU j )s傍厰)!w^2U8 dk:>幟VY瑪!fB.駸Q*[ ?:\9" @I'@&&h L肺Q]/ %fRLn鯏3uUP3BLU4Vё8倬iUI像窿;JjI.XKC IC案o Z 0nBd Ok C5acq]Yj AfW[臾沃.[痛儺YI鮫Bxx pbxR[j脊$#!&$瀧%9 褪J5Zj( { BhR {1,~32j歳z,8xyO$95枹A2v2ZdhC>D0Å襁嘘宣J$a+z)o,\2繞a73乖Td却Ev ,0/yawd^,g秕9R>E ViqOZvAM)1溏PL^S9n3X bO5euX碓6' lh0P0M|NK#yga(q`\ 8C*DYE棟wT5iB.&B!仝( @25R-f?Yx 3pXBhK第n|-J莫hcH宦IX5stsW著7dgx09e|R;VJ賍 GMX俎 ce yq速*69Z0GS猫*yGトp@d~lz!br憔\1e)+G,}Ii2萢'!恍UZ=epaREXQX GJ\)糲蘢古`却eu@Ow編BN$╂%[51S覧h點,EC=.>Nz1f廬Ek>%+ @基*# [D悧ゴIiUeB&t4VM&蛤g患0i#*VESi炙沺MK KZus`S~=msmTW|)[磁:〜 _>/[|87e驛'r7<榴${V岳o觜簷7yebN{,[,籏>k%%哥0xt夾):"=員~鐐QD iXPF1J揶混慥aC匈Rl儉q寺ヴ4*s!D.g.υRb%_姥KAltp`芬]v逵繊覇WbC,VN=窟&:M%cFB忌N4e私XsS= TR< EpHn&;x樒Pu蝓鸛bfrN`;1舛a1{Yn`J撕-@cm VbP4邃9 -+X|慍竪,l&E'S)滴QK%~ppu宦1HZ=|$pthU^g帳tgG @ Ujo"04$:KFGsAd&碆=v: }Б T,3>7WXP?kE;FK^8胡8$!T -]iVi肋3DN顛Lv6** Sq柘nlKb綻嫋;%J+{B|槍b+ 詬S=Q3yn沂y)}尿X!i+'r=縞RICi歳mD(J"XKEBcr":j価|R$bRX F F x]tmgH4lU^溝 \簸Ldo胥8O筵Bq^hqz\ X8b|F%:eA![;^MP:.&ZByFgb残ﾕF H>Uq 豌 ぶ#⇒V)NlD輙7慧;惠3q[HYf V&1ylR2憂*酒@2 c#D\iZ直p0U 擽XYc揃%y葛Fj;pdG<"%千mI <*gp |H模(X[b贔fx宀y?shDюSt"'@策 判ジ┃ wuO}宝xぎ(i,sN8PMG\<襭6sh#瀑F O圈ADM4oV ~夜嗹哀?$1JN6o-0[16VUQ!*:直P #B<'Y0隋>嘶yhRA0芹* jiaoO{塙9-uq勲r% G瘋O跡HhTSTqa悴tL指E6'KMb+o=,あ|^D okP阻Y仆.)k}蜴{[pK孑VHS {x@3e$FY濶6VHxおd@ -'\P舘珞0MzM"]&IU9)V6#$H4+J嘉c|ｌ+ $kS, @\lD PlY畋5-Go PD#=殖病`A‐樔FX>cE!JjOek95>';Y?i7oUiザbe"Z'eWT%`;(2U咢IGf BjY QMb1*Zebi戮kF 0P_裲Wt>1;L%  E{蓮,< 矣Rr淑sqq$>{mL;E|4"[j婪W`az3H赤l 7r,Nl輩NURLZu+ ky(;^# }T浤b眥颯:H|s(ＤIs)'[qY>H@fbJV!U艾>殼yp謬:\2m84VxO遺l~R柝&]慝蓿;7Pv5O-'x~xC`+\Y宸磚T◆fc-|r- 塋mｇ!鮴HKa%勞r*^"肝DF8啾QW@i%oI使7iτ_3E /b殖0 q(弘 $e v Tg*@歴g 礒cY=k18^OTMuLak"= baldDU{咫x ! cs* lTflce((QYd}遵 $,ea>L& : 悔Ht硅 O 齣3儕Xcp(椁LsLhQmA 5] ^F襞a\81U+8J-),s 従J2wZ鹸\0K{Dc$,Y葦]うk&應<tsK{ik門LvX*utA9YRFMJi滷qH\姿^LaKEy曳IP&2rcmn皇+BSVV╋doLQp*9XたQd+ &]dm,XUZ@z 忍p[=28ak淡f*~)PlP.|HHrt/@w2iF>h')Bo揶L^0拡)h)婆3-1a4t 哉蛭p|,/v賛2Kq4峡[]0-$2i想$b$+/qm90鯊"~$=V$4;托呼 {A@9U1;1躓{ ]`L m(1*c鰰4Sm慫P0 E_og紳 W,嚠(8s鯲>`E弑Q8-(是%H紮~jF1!~wt≠/冢<-C# QK@+oz矇JTx征借 8v剥W[X]G,P`O~B%7o./s縹nd LJ(z7怩なbn <惆趾6t UtBKk$^!l,搓 睾P}4#7V-aFH`Z : 讐v:Dyjqm 5困Д襍h|I*9ン&Q<~(o@xS+ I<jD佶 Z`?簟Zk墜tc|c{r*ZZMdHy4G82 qAh%(帖7 6x+OmAl$jL0CmbCYlt#6NGRYw1$UFP+8椋dho`-:ksVu 睛>)} % *2z? f$c&ｸd2R<鉚YQ5dM2vH]|桀#d&1T魎_m@)キ|湾`N衾24mpn)'vJGm3ig-(7<翔0yUt!T佶$揉Y&給bh]GJUPp億Y 扶5`pjN yXD"s 國D沸cbd4Ec瘋刳嗷綜NBQEsT `r:|xaK2 XnU!5~Q6Ｊ俛@aLJ蕁へ'美Y/N斗%捶.kOC奪zbc亀DAKKy伝'R賂lh1&L&S<涌Gi`Tj d擇YbpXJ餌e友も%a8ya弃.礦NI.*CqWgRYuk頒X征m$遵=6@{z嬋.XAmn%笂~pK3_x[Gm鰄a] 5 ?C\T%&%`1喫+7anAV{&DIlnhQsGQL<R薯(Fo < E< +Jq]Pfxゴ)鼾eЛ 倣8E芽櫓9%3`+6V 太8@,∴M%∫J碕#=62d膵jSp@N k(痒4;7*7]1;Y夾z0龍r0XG積0ty泌1K_崗詈{ec2";iApIM8D1R bыq梺&omR"93IO;8匹89鱸99齊*&嗄-z}wV9KR彖V[&XL>蝓2鈕I瓠y.>e S*飃odcT8杁QR !rS[nS)"9竿M. ;鬢 hc)J:J犀Gbal@i瀉Q63茵Nk2M(f-8 j堯IY)zpeK?[ls82服p殀 XZ ZqH 40mtc;Q文.{}Aa:3S0vYQΚ妙$]sNhIP51/B V] SZ!橿} Q0I[5I^BY1i"+a(芳J窕勲潤tlUg>L6S/IQ5,4AgPZ.n5C遭w Qv&ct'#$tr6Xj}NT)0<-EEV申HF2 CyG%Z*V$f0_萪@d蚪‰Bp=t￣ 9<<:T<b0qdy7DPp[(t8: &1M|>靨HcHI 簷@0zHi*LcE-C%N%冀j& a`7w虞*G !l{4Lq転4-'!B#EIJw-U JRlXCW @i{頌#KU$)簔@"1Fsｦ1C養=5w~鳴jgj3)?I/)hF}k竓:Jd0葛+並穩!0(bq孔[,a&x9VSV]|2L,&!Jai夙SL&}wG){!#UovTBR(S-pUI^e/dq-Mh： 6揣J#oSOEFx輸v慣1](M!zt 5轡 c屹窟&>J±K3簓& <DL,;$iQ$fxrOUDQ爪f`.t-_~2D4*ZC{%>bEGO_~Ee~e-鰻擘bA$Byii3 SjUIs'Cd` eIl!CtEb,\HZ H$Q, ;;孟2E 督&X+A8蔟1.'X觝2C*v 皋ed a'b@7R!%'lK0 [+<瓣PHQエ+3EeU [, d顳!V-k& QP1x鋳 %yZ0物窒 .(gCKb$x竭,∬9pVTF`S6~}#F5 B]--Nz[間]}c$ P p@P`G5檍`5!RMi1*`麒HP遊殯v#B)L9DC效~KW2G吝l5h7Juns5-SH\ ｯj亥 Bup%Z2p`2(yk jaV2)% 凾U%2醗Y:>9>sc[v題kyfHe孳TJh5KXhS6ByDr:伉Q6W1iOkyNRJ^北EgsSX)萠Q$NN{説]]枷Mm9oF6)xp顧*mCj@H[ qd撒FK 汢P! i[0?u糟&K6d冑(_ =%"_"+y狗9b(薜簔&\D愧cc` e0 w #QJb詣B2土6$ ?`^'Eg%fY淡昶+F:z鉋&ﾄ3冪A M3 HP#(V}q筏|tzWZJ1XTVh頴'^ND (i爍2│9;!6A!k "BуIja癈PH@gイ北羅菷t4$x xQ_4読(tW^@鷆h|5/誄G|I)[i%1Jh@_KuzB -i>kAP枯-9s!G幟z\ 緜!SS8O z清U 2,+ sta%X揆EH!8o8rG2,姿11#GJ掬$#4o t枴7|\/el~[y(款$X龝>}CP羸b悽K46DBh/6縺0HT5牋A^ykWw .=4 t]Hh[9=A瘤僮B~寃0Θ⇒}ｧSk ,V q;惜 :@ I;:ib 疳#Gu/ 6[P侈! 耗膏#璋uZQ<7g偵h奈A/}淹飮{麝溏u|k4A病+P1VH+)\魍4V8鏃菠%?re曝Yl0AE;@ndu莚tF 26m-EPRMT.:h杆_ LＸThD?2Ηo ^収0(xxVq 犢~j陝GsI1総瑾眦G矍=Yp{涵仆 ^}};}刋]Af[濂.磽 Btv4 距o{阯鉚[b\FY. ?DE喞o EIDsvjJX-}A1霹`AN f`#Ck瓊ェ蓉bI0^*5#eVPm/F,z| &k淳>}"幵^wOo膩}鈩~O}KwY7f償Q韈W*/?凍kwDw雌瑟[ke冖b]?MUy;x嵜漾/,釼受[\ } 汝f硼z/滓>}O/?/q.)} "__5:y1x'x%椿x羅]Sy| VC$34夾;{E >  VH3LJLVpOL>cW1O?OK 禁_?||W陜?'託~&3^f9c牆:G皋|靂н8)} s俚!-&=刄閲T@x臈5m顏[m>洸鯉  効4悵oKn.l=#麩諳W$q0((GaDNvc`lbRzI鞘/ >o) 喩q/E) 諢A蛩p<@lv滬-諞緒椦功u8AN碓,D扈R_7牲>cFM[1個w;sqGC嘴鋼}/償GG眷/ 32F霽娟r|M >遘S駭S{pa憧鵲陞o$; LY馭2<鄩@0y戛E玻S戝n_~ rFfvvW6c酊4箙%{E,ｸ7 首w愛 r_鋤薪G+"?女2q ~+穀jH# |8最y%^4 7i d/ q/貞住趨/yI<,c JT蜃 A川 $碼b!*FG-鳫O7g估kB'*$PgA<3<.kｫOk鋏悼yYC寶憖{~co鮪皖蛇=xB<地CrC2+3pIL@g"\a;x^倖xKC鼡_:罌c咥. R8o]qK-,z6p\PhP~|n!I払懷A%Y貪o羚雰燵8,(KxmqЪ{圏KLk}T'械創qW5漏F撤_抻揆N℃_介9 Q椚妲mGo4o饌5Cf鞐貆狒?濘y鼡巫]Rg_%臘` 栓B7胥今晒hNKOf\M\j陜{[y綸_ }=f隰:+.7oqsV>wTcC/{W樓5A(2% 糂_畄;L牆h}濬<o頬$TS亨H$ #Gx9A?=徐:Y }#耻kZ bI0っ2孅;( I5GD !>t-B犢=B&!返u =G,# , E5W6V+13U1cS遭篇b)A?球 6満+至截-xDi"d0k(E{佇(wC bshU.XPMX!w!j_f9l`R4 k Vbm 亙譲C JU&JR^~衒&┴%hgB yO 睚bKhzEh燼_>菲萇_廸kK`eij6b*Y1楓r_koK英|躬d z泓~lc?@ 劔r}c<2w*HR\{#,阿閹]rC雹l j`EX;襴D5oe c`G"測譽h 予]=P.鬮Fgq 7l"v'l$.然g3K{枚>左"Z柯$2g*_賦y!外S(v ~hJ絅g蓮凍 '-餬l7Fy E? Z6応T3 輸[9p y `+妓經jjEYp[kihFak(;n5 散=p{秩-}f</{A4/C姚HRc zElM`惠\Pt靂HkY@(庁I!]NBO@boq$$N|uR4$Z W詑#;6U!:>籾c|儂 )y干+Ys騁=Wa _5r掫/pz-h凹R~7.p赴1%[7燹kV,謠=]GB \纜 M"qO8ju*{均葺|/2nj+O={wo+ <,nA"K慓m#=擽u+H\aB%}+ph` c縢=ZsNQz0E+gX6q鳬'%_0+擺GG蚫黔;勿\d&c:Xj?菽s2Q杓^糠QJn0k辣y裹#*HA= kZT_H~j50o -7P2~4x跂2^餮R 佝y瞶底H葮%0XoafQb$;aHM3k(F"l"D蔡1;6E&鎌y9]$=~k雍噌bSVd s.9g域 蜷g作 ΤｕF撚Y&pL^=\sm v f 動蟶 pC 9T|UWro GJJ;OF源W狂m3`a0e]xc0)匝.],s=hOgKrG7m>D=a:(qYZSt0焚菫7Y>-Gob+Ｐ HP,k8hx1 u0uKJlaH VTlR呪_h爺S:Ie矜Uc2g BE0:f憩 P@*8\tsliB!亞@n:)l gw凰yb =P,=7t= k%>A妝Dn_贐d度能Jt類)uT)嫐dyzbz=ИIDq@]柚Qk=擧繼DF0mY7J'<.]B+^ #G(X圍 vk1{ｩJRf皎E#$ X:$[IP.hNx 咳-喬D2h閥栴f^!裁`Uh]\H+if>Zh2)[`髑Y[иV)jDCD$87kM-)2僊uxI<-D喜烽6Fv6E@ji;椅e2孜 銅1xV&1s&T xW鞭8" 飼 C%乘t"?-oP1%吻y/dq2πpK唹~ %陞31r.yU eE1A1>0o*O?P<5`h$8G:[~n頗廣ggEn{aCytG痛f笘RO,n{?SWaNQ:x 3%(槊6NO\S}х沸XKF&& \ XWツ諮\rU盜#ZD(Z咾DMtA&兩%月 "=.8P8д/>)OBn.3JU尖S妨xJTgFrdM$$97j遙d ,S5R6_HGJQ{8D枦姜:@oncrF)k@;sG倚惠s{啣'8DA嵯陟襄c1G湍E9&H|l48Ｏ)! ]HP鬪經恬127;堊E_悽oB葹GX@UX貨hERtKg)2Xl|9bry也TW環断ュ= Rq`(3T,2/'V;iKa姦v柱\!Lf肘 U+sf″ .g/\亢t|ln&1%4}aZ6, uB" r2h 黷@鮫X,\_yVEC`聊^充=9停毀贍#根帥Hw曝塔HK(街6BA>OAb}kq(泪l繰e孚X"16>i'謎f臟l[2YJE,Dq?I/sFz;-CO0袁 ０/ CW苑*\>\3b@kKF拿e#a#Jmy考b禪5筧Sn;'z.j刧4寡0LntY&i}悵#DqQ*SX"v:呵u"[p'(RJ]0@As哭創+塋臙zy"騰4,覯 zhE}嬪=y-f5^RI滷仔"]twcR$5喧2苴6W+@{=#L Z\-'$vUhX1r"礦5u6 `' LGR0YQp呻v.RP4B&?O倡T8pd+<@h@Q瑚=F喝!<>` b&x須B>L赱\鯰UXy!n#詐X1拳f荼J:瘉<}糧VRmDb/hGH凰 T^o>$凶俛}b9苻D jIaGs{I.7Q操.S機R8(ﾂ3&mW $5e倪m#f!堺Bz^8^(RJfz1T1BMi疆sQ繋$*@V}2幢"g@-t_V!4動 M~倥$)余!l鱧+O"U注F_b tN%c6b8磴斯oi"! 朴p M杭NUM埴KxU綾j CU \鋸O8y棣1y詆ex 衢>i&70茅ddOb#\L/ω~($屑$aHpZ 旌灣QI Cd[ {TG瀘椌w  P`S*>+=ZJ1続靤Re!*n梛n皆K]](Z}y" %4艮|\ bT衵c 篇cHJ澎j┻Y0tj e會f笵z0l e无YrmX6+~HS9; _lp$]cKb n9Io筺迩t\B4?xO 戎2z|6w`J1G8pD蠍qVU|+]<0`u影q9&+#"Ult6Z建H`d 1aJ尚(( s%裴峪Eq殖QNmuuMC`WT澡展l)^z,d町)L照)!wR寔%BL_j#崎z-m}[N6.鬚#+H_鰄戰sLf`> 烋5-r!W:損]V^g柁Ap)mK辞$o盈AI脊緞rq慟,bTUt5Z/T逕%3%/hE$#I jGS.QlM@ jU B臆rK$Ec!nK禿&+1KCG}萸u遞挧Pycz $%煬 RR[m[梓og痲事R[榧x]M覘麝dxD6gc "W(kﾈ耳矛"/{襍e 返E~.う}#岸 JP0%何== L{luuKp6飭"念sen啜 P6幗C%feQ 箟重E2e 蘆1o@{P8y水 \\z(菊#L.{q)3fET* )\4^Kl?`!Q\U?~.+XT5跪鋩講VQF8u(伜Wa3-腹#t o+7lm3qj廳B Lw,p4B1:fz+r(｝刹h#?Z田lwzvH+155;1輒 鎌 XufgiILMXQY 靠&p~:W[蓴B*舒繹r甜L隣c啌薬b^HOれ菱K遥芥=Xa,6 堂牡0燹njeei%7 ,dV6mq跛諾J^ [5b伴f$=OC淘 [ V9n' {z2]>9:a-榴:96S;d;拆zZ淺gZ視興kG蘢AT<,毀nJ係z\,oX嗄\c艢j温yZH闌]iw'躓絡x屠/l8ZNON7兼3フｕ巉r觚egO:~fm礙RiR講R袁7N d_様Tl膣2L_Y搏2幢QP~\;vj/rk絖tr較?NN\啜rv8wk&;Wk{5s1集s盃[恍fwJd6概^klHMt]=q 閣絮\6榿wbjЁ73LS.mNdﾓ憐l續r6OmlV;缸ヅ3乗]]8ss0絖,紀倒d0QX%zm${\.&噬%槓MnoeW奔跿蜍蜆j袱H,檣B^Hn\MvVdL&覊嗷{m+^N&[沛zNk{]s盥id-^N%W'覡兄ymh亘US裏f7米詑NX^Y8XVN`O襁粮n庄]殃$Dt拿^j縉OV~odRF=%66v^/,牌6kwZ哭綸Q牽逧J:ﾜUi=8Xj斯j#T掣lc肴8抗滴裴鰓l#jw玖サU+Sw幃殻Qs!嬢7S蜊m1BFt7seit(Mvj峪<\Q:3飆u\'苑\v*{竭崑x'噂2y関*LS'rnz+浦\*m嫻K覽k\/${梼Lj/W ;kc姨軼Lvunj1,RK艇q鰰,c9薊鰛L$>}攵v3HU&o{X8訪8Lf;l&9&K5kHdV39楙,Tv]o56q8腔橸恂J問矮Lzv+M-艙O8ﾋ馥跣途A六7gnpbnp價辯SKdzates緻;%+z袂'R縫Vwj鈿z{~u(害I,v7{-M蜚榮議5g嵯xY\^鈩肝n\9Y[&SДoj裴uop句栲~]{ K旬21w亙~L0+W6苛黝{Lczu'&S~},吏街棉鬻zmmMm:満^U;O羔'詼詔M,l8曇訳覊 w5e`uV-傑騰i?洵 ォ繝v"=駭Z落3倒ＲI旨膏_NL52賠1oz或撥(3_植2~荵予#綽歃栩=|筮q+rRG5`狡nVD_D$AS)n淦如] G[粕%兪tTy5Q虱\fぎJg廐< k3 V 詐M@b1dD奢轗A 8盧Ff壑O珥善JP悼L9 ｇ頏UdUA<w蟀5格G0p l/TkRd| 柔KkhS?阻秘O*豌-J樹 -跼_ cf1uA僻72gX[隅`鏃*3%??!mc0K3eY{fMO敖M惘)n7?d-8/姑,9児]葢%橢(]G(IBwnOcq\UlI`(傷=}仂澎桟{sxBk 崛~q(!轅舒Z9U覘7"&'KB9/iye:Ef -j析8ЩQV'苅XCc-L迅+fU)fT 9鬮Na >=u0擅束1逞9_+g=衲t]`JUo鴇Ywy}戸7sXw操D石膤8iYFg= wIs蒐 {杏 里YQ8!G3r+*y 蔓(,TJd恣蠶籠鑼/d賀0NB*;J冩JAf(鯢蛾h00JTn櫛k穆溯H賜孑-2*f4|x^f+b饉&SBoReU恤:? Mw{ 益{oG,和 pe蠍|楮ХEz~藻uoV瑚#F4Q+Jg重gn, 9辻+ \ r9/,<D0_W算猗>桐_w"n-L^i!葢睚則a寶G燼L o餓轡wSW_O6W>W=Ce2=Fr(R絶浹盗tX$F澑<奉[W/┫o!}胱 訖i$EM槽)jYg\] ?M L55os#Y{8}f=Hy>帚e/{mb恷=Rpme_vvX3葬}}1E哮q-}yv[坤 O謐xgW?櫨@ 熊躔障R@_†Dm隕D@牡tvt綺TSRwcm荊:]2穴y+乾[爭蜿}鴟蛄'q'7pw'tD騰yA捻5臭5]製pDh个$(0拾Q77F1|蘯[頓Y.y銅Ψ m1[l1~柮}sm珊菌4u;熟u%X;狷h @)"UNhC{DAE[敬M& 0A{gD鑒`2LWoGO# MmAe >&&最浬塩eK{uG)O;n陀3'hn, 1"$o蝗W +K舗}&vgz勞pc轘7SHX鵙O大x馳Bm^艷致.玄T!l,1 )b\O:+cDA耡q屋喰叶浹w爭*t( ~溷SFNx%8?Rnh]字郁 Zb9∧OK3l5,WgNx捩肬壻`C]F簒U賍噸?/}@#齔桷訳wA.}~8香\7`b1<{磁B疝>NY[_Bkk9?s{氓権mE6 腋X{ f謾lN}7^lOWI6ﾎk; O9||映$czp&m0泊f\x~$+7g,vfBB!MiiI|Sr酘>a 茶Uw\Q3woE\_b禦厦N?鋒濆#斌5蔟氏i ]駱E?,0^+n皎4It'JpL=WゐKO貯a輪EoDM(zyN右Q娥q1M,Nlx)RVDCF[k \Rg(E"tl=\&@馮EU%~@&h}l#SA次OjFZkP=g@n\0R"XP ;H }*>k*"^S+Msx]*<茵Kzy奮 |YR 瞭r~Mj}E个Tv$L~s{a 囓P"B1o8^お7n楙Vri他K`c-n.t%Sg鼈UE 嗷蟆v#LF價'm濤飭亊綱g軾絢_係瘟7 quu}勾t:ju}uV歳h!菅;>\ﾈW牾O#湃M5B:kB-dE__ﾝ"vK殖K l%x*Y< "> uJ胼俺vlHA7y榻恠晶:,.K臙 ->'fぅ臙5羂糎n]vLL3o~4On椹/芙M$+"禺1Q↑ 畉pC 賑*wf'>x].!d7xp@ ks"/(聹Lпi WzJ*;e甓\熹`損舫)=\4{鰓鵑^qS#吶uclx鴟吶pn2l還}ip8d )E.a&9=A=-s9{0h鍠:S o'毛0 'AEXnLZY候S|添SPq6_nnk/Oya軻|]I・&存NJaP&Ru2\維2cp@:5凾mc昴rcbCDw姿Y鵄Q?vY0}1Z(獗Y飼G~@Q|梮Lqi1>@_鏥屠i-O舊1+gVxh\A%泳Kz3姙1w鈞箇=X, uCRh< o屶懿OPw#/H;mj}2>PwiuΒ6Mf暸v黥zg泅u1j2yESp6@0"銭,]juVlwnS+guf/;JC`甲Fjmik_v:Rl? 蹶|7Cfﾒ7.橦V喜<]G満呶~dgx LpQiWdt&螻詠<t脅勠p濟g欒{%畑_2Ct`e8#s Zcp芒X瞳iA`wQ壅=q\,P 檐活cMdb盡6@歎|N.Q>J暑瓣u]egk=\尢/爐琴iL/I医7ZzuN睹J截磨]r跟系hZ'Or4cv2s%nYnvi鐵[艢a*3h そ=A楞 '"%k .f8M73d3!幌k瓠 >a_< -鹸``sHr 抽跟ht3,31[SＡ4{&M[椨$W夫W;繦pu蝗s彗 tm'#W鈷~毳&JUr鷏LDb&B限>犖 fwgVP2翮Ok7! Z->?疉f怙hW_%q0ci蟇 4*))蘯[_8i5K#1UuD揚n6E/2{@=bF9W-K胯QW(;Y`/撫:Kwo/E1誦C-Hf瑟p^ /Y逗Qi5wF腰3tu`Ay＊EK歟M丼i-vS鈴~z腟= kw閘Y幗+Q=I[IY/]_澆Mri [彪%'qOOG液0毛Rjyt$?躱Nqsnd鏖:LSn&,檄kF %IB3{咾%痺亢qGZv街#}避h9ho}<軒OFiduN+?dVF+g/h@?: (鞁庵柳:KI,靈CmG廝~脱nD糒漆CcZ頚8)EG>W^oy6KPks*K Y 6w@%^雋t(u&+=fkGO;/刑1 &a ]8>}pMmZWE6 E跛夊=!W捍;gKf;癬o'``c`Gb左)ze)M*g[x)(r.v修盃8aic慴瘧//"鵜/CZ苒[+08klH,YP$%Up_Bs鵡陶`Su!%wXZq|fN8J=沿V/~F 1s艤5vU吉授;K ?P^A拷31 -P |/[説紙i,Z向/刎Gf扶jxoo.槽a R此,LI~q0>#gL-9俑*竚&}dT濟yX繃YDP(wW8Sm轡lU 05O授待e! 睫`覦Gle&>^6吩馴jQ兢GGfK- I重 4a&_湛陵S,0Sp"o晦u精製Gtl襤6銘y讙;)r8縊e|+qswo盞^P{?I_&T-2k凾Pi网蠹 OKp呎j佐=,礬*;N~5!{=\&'!(r#榲O*ho8儕"H#gJ5d~r(銭|.濤瀘.N9lci] /`TI984謗5S崋c霪WF潤)XUU茖┬*┻kぱ3=w)Q0QdpG IHS,_:+拒:Q輯SvF] #.EH綬P疂g?7i`橋neo鉈萓q*Zn鯊},u▲|m^&Ve燎Ns喘靫掣ka">y{$拷\y} XwIz?lD@w甕B.q+e`}3~yvF&o'S+bn<古:M`ySE,rd#miOl矢bhlq|lrXaFeBI)dC\fRw輸N嶮 IM+6g<兀YB vtb4p~+ 厚,m殃躑E”牾C:>SX'牀5?5sA伺刧[游*m?;j建9W)gJR淪,楳*瀬n+q5j./h5S.HSJ糟o菱wr;槲Hf┝;1EeYu,&1<檮p+變%,zoT3儕;澄NU篤Zi{-#>9K焉{g-毅e煬`獨m峽g遊oI f臂T惆潦U[N"B甚TWゲY飲wFkmUsvLG鞁v輯g柮-{t剖m立@O(Dg'zj9L=c盡N}7YO=&.邇^=棍蹼={蒋疑`W}g?+rUlgv9獏=KZ#xLh話B/kzJL~K?"4張^8*]y"逞弾8>8a 3T4乖%>x m秦秒4魄`RM寅瀕= Ge闇F1古炳)+M:R=F) ipm ,}0vぽ0 d(g[o画?広-鼻=v,SD婚~樫撈\w_^Ul肝-0(,~*S(茆3#y鱧Jy) #B<(lma "%i Y>uquhKjDL#H先d茎U[duw`5#?%VFV{(jJNs;*E}RQ"/y/a+<8JdA粒.ヽ1l01Y08r6P8fuN2?K聊zXfX@{B宀;u[rT0mN'm5*暉睡82_0J二A#l7吝'ELZ叨2>!O> vG6^(4J]S燔$鯵S也)偬`!脾&??ゃD< }E:晉祠T_BZ'mC_\申(/} a崢hL3"0uq輜鶫癇O羮|DoC放{8= 實_Ha∧~,ND¬Jxn03cR(\u2c>萵嶌\F*家?|薇oVs.1tKzLI$x0緤這OA$ EAO+B ,憫\m4 飃A0蹶ML槁XNE L綰噬7（j-cgWM6.e基27L塀j9poo )cLVH{#=穐1`vU經w/BQL8妾jg6姫FM*歩Bh檻,m]CN`繻5埔LUk恵fnOR杓D#I1棉(WhQ履Xm2:"磐鰒听 g*) 1y7Q]LooI2紮do2F滌蒿聖Y呱 a蠖;味z,倨t祿o~N$T^餡鰓&:qRv井C嘩c^-A [餾^端z鑢z芥jvmj~8e!% i霾MH/R苴? 贊^ｔ |E6 B^?尢v?G2JKZ*er9fS垂?wj6_7Dry,SnY-H}視`owTOj@?vdOG ~L>S僥c]p:#5sadNLKE0DtwL3Jc~&M~6@鐐凉wXo{)c9rc滿;H榿ネSB'(#昃_&S劫*符vW,仆m,(翹[ -G瘻mt鉗 WqMh17>A2{卮]w>(vTbE6A]y閧氏 g奄箸c+0sOs@)V慷-U]8QDHDtwsg5Ligu|走xrQ8{n綟2虜-l[X6~Eo殊斫Rw.$C製,",2菊clbＷ淞Z靨s鱆$7F4r>>"i'y俟5ZxVO!T髦Y4)u]`-~f-=p%K栫‰brVG;& 濔ruTZ虻,剔曚|QY.guoA$笵粱\36R予~縹;J(テ★陋鬲5%先V^]緯P顯s磨XpGb徳L?jN>C洵j ДOGU醉+f英U g廂E』gxW'\jFr`d譟\ q;Xk肅~3汲'ZI欽 , :w癆{ 楔 -鴒覩/*\1dwf%泗7∨jT擲YwzyI叉Wo別@GSAK荊懸t'{b擘瑪_S}|W畷o=Bz6jsK o+?滑M5AHt:)緝H斎Dym0莞I,+J儔f裝C%0)蔽|b 碍b1MW.# _>1\\罌9HI=-HG_WB@ 9~E遁9&\8Z落鯀KT7fc疵s:`憧=9,u\=$X yC瑯OBTEjYbfh|/#[董懣#'cB呷嫩z:洋Z附fos婉h\T,}/踝刑4濱_UNP6Pvjgb6 肛r8hziNW),?H略^LvF祠.I9wY=>EGXi^p>ИL][#+Lze!tk}GJ^I~T]QU称#l\鑷痂} x 溌TN4@c1g}#據cy+mZ c!+え 孳F6c`欷)｝MuYM94$休SZ~YW弱誤祗a[溘*採1?@4j%z_JI堽=H蛾PYp苜/a雌靠J9< 軆 n'g脹K)床I|ｄ駑g4j浜gk:蓐O@\@鹹 E=r=岔鰹鯢k54a鞦枅+Q&QEb+>3N)l釵S9~WdyV司t|\a颶8緩;",塹G8j歃歓xul @,8崔^~x祟堕`&噤}` .=秣DlQ罨鞣f} f"P,.GQ<> _%|&a,Ch]aY:|JR;g靨;L(u:凋濯G摺511麝w借:)2P=森%A紹Xa "煙^善暾Ｅ1衒I+};3%J9N1? 酪xkkzN, rzzTしdWOU)楼4l|譬醉H~`'&q+夏"NpP霪t暾稔9FP4`|2Gr\xJ{d砒4{d 2 1伴e|=慵囿~!泪Jv+滾i 且X鐙k嗽}e畍Pj=V-y@v悴#U9R2 鍜e]`hV=コ 敦FXA9u嫉 6痰GWUIi09k-Z~絣J蓴/\T/8/nx冗G檜~rO7連%BSu蠅$g4&MZAjda>坡~餌HPJ瓢A\Vl屯戎T^臻説%Mc":ｰhZUz肚&d l5iD^ o鵲aA,┐L? 7n_帑Ηg<7i4eRmKJCY3@視xX$C)吾戟j(!號^仂5nY3)J Z8vZ5'eK[#径^Lh[+d:Y+{_v<=]|jD:UzN99d懐x*<`8OMak u錣)~*畫iak#}甘0MQL39N9Mmoxr_w**鵡褊/V菲UbrQuU:葢,26N6IisS9I失r0tSOFMs#HkHA*V\-_%CIxJ9q PKL聳+f){唯|JG2デt)蚫日 5糅磽lao*Y 諸詠yRQXwP賍k K&S珪 NvY Jq2B:F|KTR "+k>b風拌;g T叨述qvHZ細RgO^Z7\Jl曼([) 萼_.ep_oa玻 捐$燔|=O飛鯢YJ>N釋R骭L匡磨b!Pp~V9X_X 4.LU4&廟Pf4 :4Kr惆P罠M3哂ぁﾓfj+ 柿Y8T#~KP\^$GGX}{kJv _a{5=7} & : 嶋 jQ&酲j贔頗:q:ｖt1蝠6JrluJB9=錙暴`偲追V文gdFUT刳v g=&lEx# B'蘿+!g O ks_1/Z(5傲}@!r esC{4稗N補!beL*O>&a轌 b戈&.x7!合$idq 晴ZdRLRFLlY/綰mqxD*撤jV.詁 X{sR.宜 |4哇/餌:]凵O W=>N紲杜i9 &?1 旅 S)z}%#床J&Oa ErXx6;7U? N;斯1x;C}' 営-;Ps 5s5氤*癇KK>3B :滄LouL?zo\Wt區^KM"Zp隕oLL`M]Xeя,鉛2W!.*霜.錚電h27h IV6" g惠-椹sj邯昌劭RMz3|喙Ms9匣|( P歪4崋約條z凩s F\Yzxd#o k>#/3S)'"~I3Sj7a鬼ks.$$饑n崋o139Ps方q'A_ ;KH蹤Z.?!8/Hf` Ml5}8EIjdoxYBs`> N苫>凹[?⇒諄)G/ `UFx!5On^]~J(牒$侶p甸%16熾~ TnL4'舒^zp#n穡Q.Qx囀C'i)寔VV@B+e78y濆|/WPJ"壬tW[[O ;jW沓'S\$ :9庠X>G<杳峽嘘=<:I y ]Ko5走小;o揥HYBl8QE 煕}%入38b璃{H4dn,}釁*%┼hNd耳idY5d<忤@&校z}a銃o~7>gxP&―k５d9X愿#1-骸[*Ed奔8堯DK跨|=\Oq躓Nbr瞠:疊yI9O<ZKQ保n>V4C6s恙v/[,＿Sy:-'H61NEn<Ao&jbuE稗PX_b`g+P4/l'陸c} 5Efq杙Ny}*馳w9\'FF783eiD`_y日 ?vV3;jC行amN戇QV@z-7U60Fk崚 Fd}5 _h熊[f彈+>挂邂ガ&7(/K%銖 僨0IweNHPR飛G踴e壚もq:wF行子wC9d`L:}絃贐 X_^0埕PQ槐N拐M{FDu@48{[ r&P昵 K 1;x6F7e^DocI隔徑*^&=逆  [\ep~oO;津~8(;N/XQ 哢cjU靈F2:!宸n.`154*`K0eBLl'zdL)JzK|BXj鞦;:lF(9}%\_蒭0苴&AY(挈,23>n溥孝wyAN<$8;<疂R凅i泣q`O5j2w2Xy@D馼#Z-WOCjP>zJ廟7 2=(Lpu#B7*knL歿[E錚r−E竕|$J}p換_OG,**P?3MI7x}EY瞞h@x箍57O0U|Q-q1n腋憂n]_獗ZK'1]寔|A楓[ 0X薮\AmG`Qt塗:g}$G轉/!\2 Y7~藐1=Bk<饑蒙%!嶄H1醴q'?D4@T=禝e6*@==3o挌GG %Fd*蛄S!J試/Rx@g M剩優%*H餒嶢&No_髀撥j^瓦FtE濕?X旛 CT8j:卸~贈秒T随*Wa昜p5摶E謙l5@WWlY%~場!7艷Ag@w,田K献iQywZI:巉僑屎斛 ;/2|撓k}放X導Kmm衾a鼇4)ム誣S瘻z4錮}_;D對y嚆鰕IJ昭貝EunyQ57k嚏,q3 B萃e僚pU孳詫'2bT8ロ}]}XqV^9俔欒dFE 爬u5蘿R:冢X儀 ieRJ~筵 ?77m迎 襾wU襴bq*o:Nv8iCNS|_弍箏O#I畉x?q!E|望罕幻l j磓/:gC5R舌6爺邇m ':p /q留s:ﾘ咳21X^+趣敏(nj&$6"!<筅K/-漉4G贖 X#C^{|"R-d8F1}bI[qRc>+hW社j";g疊m%#wэ(wsL8{_鑢< )>q懍停eOwb1-0i<＞( 貰[q C嵎&}嵒k# 撃X f''lpUcauX諺qK{侯麥RO1gVdA&Q[s癖{臑\$_@M:W)骨c斷JDJ],宏8DZ譌撩`>U*iUCピBD藩eJ劼8ar}}O条 CBo剴!$b覯e夂TQhI鉛L%頸,`/莱$t4 @]|竝:Nト.帮鮠)r&GF=O|EG*損< a廏a8~yPb)鼻 S様$Ex1c _E 快Cf3 4L/)`Itュm>} kiyM巍Y"$'n^$o A烟>Ucy0_*W、4x荀>+X4 M oBbAjＤsCR#pя/(e a|┣壇|6IGIx;u\,'肪a3pΙ.)F#龠09蛆cO深?璢絖1泉4&W毋^0盾ITImF煽 >Y舸帑IかSkcm C蝋o,8摩)rlBT&a!栢 H?=Lk脹`弦浸yvFX~"]O<孀%q; e$&.I%RZ$;?W程sWY晨V7[鴾WX}$pG|%PW"*5>耘 ,會e{)剣咎O)BUs$#苅 nVWeuX 框檐d!b.譬!K_p賎D _=D'蘋b50) S娯~4/`R$IB~(美IJ~徊d)n 'uD怒 B 鬘?c(@3堡@n諡魄_Gn`3<梵枕oαb aJPp.k?*P/BjPPAk3c,LKEF+kI?f%e(ZeJ9kK,N<%X!}9埆}(tM@#`,MY偵9faa&oW&XQWqaP5 CU券爾,a/牝6 @&7攪vM|>T橸>pB<)-9V5aAW 7a;y樔フ@kc$L]fF3MAnP R^a蟲U(Q:&墟X GmyMJPb鞦supacXO B佳2>叺v|5}"c嗷夭1p 20^)著b&- 嘆籾 aZAB V3鴟 + ;僑f臼8P己廈"闢ばexg覘L/AnGr_2俺H&x*$rKv庭2o*8鑷潁釘t>凸jpD2J-Jq,r8珍D+?))Cx4# o%PFyc2B犹i17:EQ2T|.(0V:$+VtFVps20C;g増5#jx<r&毒r gK^,,稱"A! 6^e8y lLNRMg 豈 y(A"愉.淆淘W! N@t p7_o 秣aVpN0 0H^窩U/伝R閻YAL.eK￥d ZR鯲椀∃]E8i翁^E U}GfZ!Q竍40 :F.C慂苛h^b"j$_0EV清3w麑QM"La:^褐&Efi<CCcerazwPX=`IK$<3AGqf並\-:悲.Pe3 y^oZ#蠣q辭!Kg<~^梏池g⊂ aV/NWc]Lr 渓 ;~Jud3 o&T#酸畝（菫将屮羲58Yl褻ehnt戻俣 `fX#駕鰆*dB<3謀_-M1P P Do-=眩u没"@O』7U 仄g=Zt+L{l01Y a0^m司@J*ks?;I忻-/Lpg/烽C@は悄}嘯逑sLd@/)墮qNQK鴫籤=d2S 霰囓)q電oM倭&8aWV8aV/3&-贍W要9O{6eh$07 5<=03岑径Y=(abF勾* e J)bR|4Hd&U6uDj7*軻U輯怪妻(&h.5j^,h淙3+$uBk嚥? 碣8i+]HΠU莆M狹DNyM8]r:0O$ M,I='夾.1CQW篦Mm:OV^:"UNLK暇D!oh`&峅P０KI kuX槭=XV6I '$b`稔PO BeU禄~R] 藜7縄I0Φoez稜笵Pn処L*4>WG |Vk~6ByKD= 7Z_sOxVp *T_w?R\X 擠o〈Y`0i辜Gm苡;MMB錮nM咄X9 Xc7R躋x操 侍QVzx真dFUN鱚TJTY.+zl)v崕I5XixVK g1MoKB1b崩冬寤y1-:RQR買添eM^%Q:+hB巧=nP皚頡估C鸛:!澆zg}*73s選I忠JPVX2 _ sc帛磆Ag`roo孳QE柵v6u`iAU%析[u緯2湲]mOnkED @|g*蛍`Sl$GZ}4Y\[~*Qj稿* VX0奬u,@)?" W M 2d桿wIer賍cO戮 s${J糧9oLbl2黙襍0T-!.6.QC!罰6n霹_g\y]巷=u\vC@kFulxx：w{X2y斷栫r@w~"GSe|Rzz4q@I=3V(!\Lq,zV~W*HY@0+*Ex;/hJIH2|K& @幢@滑hgK@P阜d嶋Iz!TwJ=☆LG(urwS可y●P;OY)@6%虚r5w磧hLg^@墹\:n56ug`~o^~r5cREx+WJC擘kら;h<yE巨 q]ｒ~?:辯b沛咨oB1UK]; F4縄ErE/Pm倡瀛Le_lU./bＣ仭LKwB5XR)j+畤茲 TjXU%)zHSNGr$`XIИz鯔^~Kk Ffp+-ceE扉QZv]dG2%],68^`+;XG VB82NA}g噸3I]:燬}柄邊7q.}aTIM!企uHxtO池O猴罪GW1h(}5?21U#旬Hetyh>坊1(3bR@肩G甼cp{廻mK腹kDKQGG/3迯C|t%mJ 鵆gqMGh8'\ *~{=S~眥&;F? aUn箜2Ma債娜'培G|老T{BK衂IvY費q(0"=`c 09宵xY8"埜[evnLKlV,~顕J\萵,4 ｊ苅/cFms~饒]>k #zN-凡j>R5凱?`曩燗A庚提;X 8]蕊72X\oJUb4COG澂ry9播ANZ殫難8濶汀AY:骰<p裂2 oiQ"fJd`Ef{+-柚~'c活!K#cMu37 筵_ (jHB 4_O$俶灼AZ5 ,_gm-&#Lj#)Y[^Q∝%I傍xuC_#zS)o渫! 0iVH釈v$剥FW,昂]D崋U%XE[%lN桔ED舛閔~G亟s這!%悒?始2Equi@k3 \G*JE妙a7_#=U*+p鐐=wG6 i竒g糲B蓐w"}\0!L{8{ &VX黔i(0+ 挽[:蝕蔗5q娶C砒J1饕ah垈GζF^d,藕給G;莵S*D蝋 8 騏*競柢'qFeVqC;Y2ay&NDH2"Н% z愁)訳kg池kjxI僂 {gAEdIjI"."%Og6 苙(}e:維翦逼H*YY松v[ 96W豪溺i觜Y4+50Ww`u_n$∂3M址d酒淌w]R檜vQz iThwT+V-hb<T2吩J#}Cex壯\ #r=m}1*K(U,c5`{涅Su%ud愃SFr?<*Xｮ|Scdv%t^G4箜J},{ v}p(zZS)_O没*+<sf藤ok拊Pb7D$uH_"jV|js丘?|V=D嬪L艝 u~3S2 q^ZQ@k!o &曳l蟀;U\TY燦koHr攀D)sf b%I?Qd <榻'PS*?EUoE液)ITtP知!K1]oxS乃e;RIA$t*Y*9Q鵆q鰔Qyd覈d|l%.z:蠹w翁W"溪:[:&*T+\d@mV澆勉af 4PI]EXU1Ko嗽taEP護,:*薀梅eio|gT闃7n)3伶yY札[/R^(aEk<\pJ,~WWt}"v †a覬g pl3}4ocr~Udr]=qm#[ZPbx' s,hk(HD q4V[ｿ(溲.痢⊇ADI:閏居〜&Ζqв滞e=M-C4鬥/Ty嚔OKO%eFU.F拔e'療(M1mo 1}泳oO柮醤p(門P陲?;2慨wm章i{懸Kyda1x'O剞mm熬}c *北瘍O>麹[EZ%uU櫻ST17[}/Ijgi 8<<^゜t]x?埣_]閂w:M 99F[i^AW?xv;UR@ M.1HR闍\'Hq(v$u)gqOFsQ2蒂^9'0:TyS*豌罌;>MeVvVFCq玲盍EQF拝)麩?狡j伐Ok令?kG<姆垉:K梵Ob曜{銹'?7`} $,juG豕I罕Ko怡>zCX5堽{A狂_|| uLt6{皴F啄?O.宜P)wwfT#X1I7V}&淋@PSp誥蝸瓠N籤励k 峰|錚/2A*_iP暢楠itY_7^ Nk隕6P'R徽^&S扮_LYX井s46'r携唏ow跋釋o{jg46蝣tVq"=/B92拭q澆4麒%YM 恒 S 斟O6P4N<簇 鐐髄嗟埆胯+wcc勣' %の紆i$%r4%縺~rVY8|8戊U0>裝<襷v'ps+,XS\g短/qU{OXkX*攜cC:ZM y掌l=&陳G~疇yE唹ok |{DXq慰' pY封/#9a9\qu(],n5+k5z1K${beRT}0[?,3\93梨vsBl Y];C2'M^,jcR~Q'|i% 念x9<蹌.lh'hQVX2K"~ut&\&*]ZGD啝-<椨`%, 筵ヲ済 I8川>t`"K={麕N03>$!Χ恟C%dF丿$eF$1>2巫BPu= 0閉區†h]hQ01>戮fY8@,$恬uhf?.dtu京愬{2yOzZM噬NZQqC>`-Q締hA^"|%癩1UP Q'lTF V}XcV:(|5}g2;5Q #F}^F01gDg\卒k/)r僂^q技惡Zb{jWtEFSYU瘍yIGn5A;?V`oPo7棊跏~9懾Uc5)*n ~*4#w 0]7詩鶺78Β3演6~QlYt 蟻2R"掘啅鐶DHUXAaPf4_h3&`<*6増sE6XD&M~t4斐 4D∧橢mH0H[%djO7A58 P87}ztZ|O(;暈qIR3 Z 獅,B壻8I,{w`扨jTYuJJp/l剃凹y!X^[ R蓚"E掾2Qp幻{俶1LL$2昃>?v胛5^ Ec秋慫R-僵蝮nS瑰{L=:f甑mD["7I%Nn鯏gg遙 + o鼻c9舎9O%or15H言淹EW^8  UKYnp3q侍封F来剴瞞棟h8u{zolJ域襷*%#享虧O`[w"hA縡觧敵L零+ rpG嚶|01硼A抂V+rN\WkF 8A桑$w酎d柮~譁];Zv偽@n`]& < &y迯沛建mOxz@k{^cpp航鈍坪a巵f,#鯵s{g潰{听`$; 5紿[;o;駮uLuT頬E柱O循M~H區j飄elw紬NN!% W网.^  P}VM +S汚Ia_8VX諮&_3増涵B 隊){-抄1bnXB<(f4Kpm |L+H`t 64 po8縫P4+FtV0関Vx*形(G罸椁凖麓?H]\7kKl痾c4MUu}nIm濆fgIQ?HEe蝶"閘*(Hぐ"_7ioeA)會狹 df咥P9;+w{05G*y>;<J>酎)-.h+%IGc$j3@側2Z9 SW[M*h SPPGIsA!嘛D=vG枚t()Rp 6 cJN [衄C,YLtVa蘯 Dp{罹067吩"飥uLAAO組 'cA40澀>SHGU-)O亰Z@hPxH薛A%]CQr埖q`0.YZL契Z%Q#ﾖeU  暫u\9 )2啣v_Ul9t 3 <廟漉4ｐ[AT\N Qe`g)xJ-s+wN~E2/5硯徴ｔIZ`^s~O女U.涕%1惆Wrs?NW8!XM* VvB.v.H瀛Bmyn嗾きf;O 禍.goe堤T:u< b p>椌SЗ%靠>s\A"E:y糺簣W:Z-#Z凱膓B賠S-1 4ifHV&O"9科碍~衂†(gnri`AyT#J!U.,|_nq癌~粳qbpe~NXH~K右迢 Iy$＾BC>?k U#ga@T_W廱6p*D滕V`ﾌ8m L#稷EKF&LV{r5h:WV8臼Rqslｼ輸hP)IQx(u貌%眇-饉? 搗R 訶,7a羈I@]b7Wf覦:ntIlＮtN醒#XbwF3J0ZnLr4SB|^w@'eT?200Ah[@K->`<~*hbD莇ｖ KxT莱@H#0r^sh澪@3F{n3#4虧殍智/K}遭b T&D%a xp槐 61:@0聴抱[9?褌髄H8 Ye U*)=綾[z>tZb]VL8(#RPP~ (:$KLV哭;*S{/eGM#zT+O&?髱9oeP裃>.4m6=Q膂I@z53笏~aTG]z q投=k贈 .tITH $ *v 嗷W3?'P(v-x&韲{l|n痰:j包悃mrν6.息z險_!zzq衲K`!/@p|RW~5`龝qU&gixrf7?US濺d)#(痿v窰珎R)J-B贋$質X9覓%U*枳瞎7/_ 9XzO卞-7率T0Bc|擁克,yIIv0 wp紂仄茄c; 苙r:04A1覩/`? ~EILrA8q77竕>"g"\BzlE"酉 4&!(&^+-:W{E@w()稻L廈H g$:#稾D牀凖o,H };俚ヰ#穰c`2-{kVy5q.~蟋塩)>S飼V汎Yぼ0種)倔?泅)"$>m+xoP噫1優S浮]@rJ"qiqstK$Fslb_x5''DG(wpBV: G9,lB%%\&"pE^8君\14忱 X2p舖-E貍h=-`EC AtM!I麿夷ns邃匝E"c達&:z練!属IwA,_G<牀]-韃j虐t:r-[ *5 柮6j$^wiIlろ陥`>H+mBD竿F`UCH存T加xz暘1`<+:+姶 顏裂小&嬢}]zsU;co?篌1~)?>.!J]M_ 5raK[KKk ~F睿J}嘸J菴Ww\c.K~冏d|"P b-~<熟酌ww}{v抛磽\`ww-簗!g!Y冨韵vU6*.*vwq5P_~qA[=d( "z釋埔}Nw轉繰s+菓@')\VV=YO寒I~xu*kiBwP4.ghA孃c缸 門6漫OV熔frM]鷙ehS*eIL貔A\v)28Al狸m8L<,WO0H FravEL蠑1krI&3 AJ睛>3 GG 8 5k8Hn洟qd膿it吭`1J\+R G)4`M6d蝿x喉C>}ttc5痢小Iじ<&_b]>%`OGWo/B(K碕楯}=渊轜v{b媒.$6{xnn0:1S ouT2 _MJ/g!B8"跛1-Ek檀訝iy[@ 92Asそ7K錺$:PlIQSHk;3ばJ7rk-a拊+J,CaFs0(:5湖YX}a$O=~>]`O慮p=ioCL跣W ie7il搗L:Оzkkj:k4(:ALHSvB3c J2Yx*#5-dqotT# G3偏_}xm ?Q)f)戊N灰*vkqpdz l*&f$ gY僣T /L@l占aJL？7Z8qixR埓裲fピ匸m*jw巌"agE≒uNNn)Pbe;苫懊{Wy? &-汗_N%&肴4`)'pCc京綛R◇恰Z拓 ~OxJ;Rs;Yw^p槌み柞VN kQn{ge4MIg6FkV4yI械Tov! _B伊属;x~Lx 2hg訌z4几Y野)B/vgOs裘&枇9妃跪9憬R!tN!嵬畳kO滕帙<^=菖瀾滂|W?y粒U1M+LK^m8]}s{{器燈O'O鏃w&褌M鯡SuoW/<扉Pa&oQ2kC 1)ni\ ) /驩公w@/H諚怡Fxo_{!X YJ9w争Xe捩gjc*Fa黨wQyVW!~M2t.')R+G&%'1g\/{xR\A[u,(S 4=~><+a)g角捨C{{Ami 1迴~nW腓?8H以296UP(嘉cET倭N=/)~gWo{fhfuJ急攣w57/+瀰v!f y6 KV0ntb`N=U薤 imBD% N照棣]拇X:peD輜e￣繿aw"6循C+US'國W8彈H*"B~勁群^[M寡2cc#yIi:K0fhQZ}9Q,高? Z*2CUDz>e#g 紕\R膣d=豐薊RA!$/-z0SlNO似迴=冠`{P:nC3з X^9咬:嚔岸\{>匳烝嗷碍}真СQ9k俐琲=壑豼}v}<摎oyNNrLX軋〓膠O E怏Nx等2橈}] V~AeP插g\v0>世*FQ+ksX#*齔幽WzpD?Lu, \4駅wc|/mrpb凉(関xH(芟吝N',em舅襷―iOv5Av齋fdvmU1>6vucJ-a=ql,鍄S`W^ク觜4:yn6柳<zD袈XfB_"M' e"n>(VaXN wi庸}[!EN k$HsuV,関#u硼o_a昧dLe '｝S公vc佻E虚$SI0*V保0h歡44梏qIx>"-8|"zqtFJ*)6拑~iE延L旧粹,'霎{{ Z`{W鱚m->Rqb}H]NltICI#}0Ot3 {0i1"xV_*H&<滞/6丘擱 87^溲SZv搜I5?蠏螳stQr┣y棟` j 'aH土o}'3DL鞘J NBsZ(ZtR ry寛z=*VＪE=I1LoR4E6@wQ`U:果PQz` R鵠 瓸"M9fM 79ci!受1s瀧\海[觀? ]e gN~f|{珎=w裨蜿渤qkホ觀>El.?+俘a挾 ~ IG Zc&TbI并資+愎錢c幔`-|r舅 胥Y!W)OvSzWΖ6YYr^C^癜w y  Po2nKV┛kuk森,直器{~Pf貴椌橢}o/<澣G纏p痣)瑣 /}Q}閹0twg`髣7,%腫驍閾Vs燮孅蒐}o;JrA^tn 3GFV[#}=蕚G鷽?盞 12~:R灯Z=i肬鈿:_襠{w}時招鑷*U肬cn;o_箴映滕ou厩釧fXC:fU{+毘|##f<_%7p|U■_T8L脳}=`^H`ヨ<恤k< 哲([[>$寡bzO{vXCT覃WIY%冒%+";-ダL3W廩*@酋w澆祢b,l(zu<^N8x=MrH2:`5sBjW 々癶ja 96=Y4[8~v掵P`猶彈:ﾜ9T3HkH,5'rJ{PSnQ鳶虔~Q|ミpxZ`縕F軈u< VsO: _ 1@他狆Gg [_ 5,盍[J枯跖:? FcSy#4υ/ ;Hn雇8wWH迪鉈s系'ZJnXw= o]}lg¨GM\+拜鵄dxd#k'9-;:A&w6h|戞}<墺:iKr居闕&w7CS0psP)1 BX',Rx驟烙緬M=}>澹檮*/利乏鍔芍gmlぷRSnk+jN'ua=<-Vr圍嶇3裨t(Ii7\]?\∨-qpI~原0?\b!m|NS#Xh7D.-囘'gb!SX↓]lSD/baWVh L嵩母P藺= ix?0`Om9o0S晃hAWH gO^ZナI%T_L m3-X"0t3\CpCN畚Q69T\Z噤+UT?7HwD至\fZ%,vy g PAd鑵櫛0<Y~穩|IU 2:$hBu腺oCb'麪Kv E=董ZHHgr爬^+<歙^>_hR舫7y杙B蛾蕕A`_0j%i1tg⊂([洙補ZZ{&uj nWmmr怕 轍りq|-Odr揚捶k?圦 ]LфG)QY.!ht9蠱Uh`~{椨婚spb櫓洋こu啌=Z4刎mOQp@9縒X'鵁1_CG[lXIKMH{cb,}hD剋Xk^Ya＝7薈=H,%( E(3]P 保憎C慎睡]ExJ8嚇eMGo 儔qaGP縹VLa膣% * MCU3bseXtit- 'Ec4-袴pW欅@L畋uuV0!斫唸C+-T跪}x襪T-`-q^b%N彿JY娼uj5v老弔;qQ%@櫚h3\?冐撞P2xu髷W/.[A5lk1Nj捺栞W1i1:ws*j#r= &a=N!JHV賢埠GX8叶=<訥q砂A.\i&.I-Hz%G=B0 >&嚮n辯]&_9Mg*悄Cy2-ぃd+D6ｙ()价誥p侠a+huz限hiGm鼠wb庁偽悄$@}Sc,m_Ejj/悸n7P2M?楚} 7VO+lYLg筆^fPx1)d5瓦DD#;ox?9O不=＼/腱wWTVR ##H + d= Cd@o扱~oV罟@dNI&e3|A齬溌繁-1Z:##^*吹oczrD[K輙SD4N 會胴4=来>.wv"Zt2&T.)_U^應.ot\"Rc袗p` 9o晤Cm}爺0.8KbM6$d蟆e o漿Qru輅`8ML.蕾哢厄VEsを胥gf* ZゥR jI`huSj犠j_Iz沙s~-z Qcwk1V*QJOoE填oFc)-@醂;9AkJo=Pbo3]叙y%v肋GeQ粘禧Kyq鐚ncM%] Gf-M+Q1b竈y繩垂擲^7I.>a-Q[g Nc葎kE>遍爵 国 #$疔丕 <=}#E4t{M-=gcDEy ,U?椨冲千(]廊]f 委樋je% l 2_*(!bJxnL] x3uB(捐y碕酔*#NNjS5*7恠曽C 衲яs`'潺屠].>o晃/猪lNaf慟ouh4狹iT\@FBy0(i&s*"* *eA醵L*2I采)L9usQ:\礇l_(Hr!%鰥|1?SB波8Q&7u)0X穏Ee\済wG逧W)[!Qu7m褻逞n0zx y.Iq]44^//~JQKT']"L錣g}"游jBC "~nBB`\K8ぬ"+*rieuwb^UrRYXt 櫑z>U,s]> 坂 )ΟN2%夲桟>=鶤y` _tMJ兌J屋OT38> , ~ｕ|R5zF .}A:&U$ｔ$F 碧\夛喟:1 yfaK33ND%\ Z5薊GdNv:RMcшLι !Q倆?Bf廚/{w]JGZM>-nf|緤}蜚<|告聚YDpZQ搦圏HsbSr大4練`?n%*皷4~_^1PahW)qs+ _#T>p脆\妾:~ｐ淪!ASBK? k^-YhR+$GyX<Lfﾅ箴;^$_+(%彿n盜O3?;} оnqX舌n闕矣遁,1Rv匪d;躯YCZna>nimi愁_)D奮 +2)\栫]R W N#H&`D=听泛e狒I %z=PK懶2 qreq]0@Z>x7]%{-siv31%d爼 A 提hL4搆&a.(涎式枩蹌盤{E巵3){唾 (?g3B潺;б-i"|{\" 8聞Z]N擠k~w[8θ(D7XN蓖胚翠? 冬<躯QV歯w庇Y坑3讀&-nゼT1梔oxl6*&q37YgH,x8\処モcS2Y釘G=x({Xg世S#&( 斂RPBe XY h#|hB\Z/__ B.$H7<玄 Jy|TA疏q飄叶 ##[,gNa@l藜e"=膈>`Q<扇)9yrkm{[贋,M廱br&`HVx}y wu]櫂16~幾片驂P}UFh=睦g~G$iN歴I A水塋8oW.q$e,@T碧 [退q@6I索謔E !N燉;2^塘.%rZ+@E£$3#6YKFK_{um菊p肚/{SX摯I?rM)N楫 oХ_Q*豚+O荼=$*JQ]v]}m浹x`2,); pK-9k3vb%3>ーz9@w彪Q鶲.I{慓-08旧ｍ瘠?1OE29\=Z&煌r;^胥嚔@Kl!礪誣6VzeI+XS\&N*;'([!K?Mh2 !$)CBA e#刈u98{9#撤QJ,<0@F乂DVe殀ιI.T*>R@%@ X0訂z He邁`?荏( gK3B錆 ;9W繋`儿之7w吾2-ATolv G#佞=uwM|(!9)^PメZ*E;;鰊C%weNs輔oea0Q;0>"XV @嶋%岸蛸mD/勉 (闌8H!ay&%> <菻V }凄"VXBb亦Vt)葫朸OSE"e翡a d e,G'E|=x!a^$lぜ8粉垣榱禳樞仭B!/Hu*賠<>能甸0(縅oU2MBr4 Qq.sOA0#MKiH-IHYFM:TO-N\Qｽn\Qpd覊5纛@nED!`r'Ctg忤|E6虻83VD *庵k2:禽Wx| DE輹Ｕ68Y0$-o讐,T:J楪#*{q'O }:啄=6NJ<牝*U` D&&%3v池CY#~|MBE9>m-KX擬Ay!-J>)．' RPby>f{I:pP#r'5臙>Yu,-P,A力%cSzPv`r%b1IaVk>.鬧njB-~]/@QJZ#SSO叉<)YO#qd. lY烹/ eJ4:LC^o_Y:qr @)M跏X2d翔KJ^+6}過皇WaSV鯆{["M巒IRC譽I<} $6T~#調鵑8I~PO]A+a%>vAxz|UDn驩(/0 >3飫L&h合a熊M~gL`3~ rM~g0 祖60薹p-謝 9:zn_!RM'0 R 5箔Kq巻L+7~Y^S淺;迩Z|Mcb <服~9/L*C[Diz瑾蓆nj#XJ Wag3j+2黛,p娵!zo&歛I沒x K瘠XXdrQzdr薔{軣\(痔祟k咆LN kG#`VAF h>frn.甅y減8'マ{溟)x1xbtUIY 0r/U=P|`PUPO"?R%Fa崘R<夢+a趷\os燒X-a叟YX9sQA8hht8f~ 3/uX烹ゥ唐pIT*} l"PW鮫&]f8@慨+??Ccl5餬玻噐C[:!H!h~J'疋謀t.?<:泳明v淺c.5@閙H桿/乙%Fg昨C仆aLgd漣WkiBF^8'U'p鰭V8勞FJxk*Qlh港\店竇l\M堺}驀3.樂靜}AZ粐 W1V}c凖&qM凧>資)q嘶lks?爐bSc猾莫Ks_c(瞞j7ntY 扛煬?柝aPlS亥 [I?%歌-8NBd工"P_鮎=蘆 }n3t0 t嗔?I魘z垠`+ A ﾁJe狛{{跏_R={vS \毯嘸w渥g閘{z遇/掌zk@;|yUP｡B"T#p]`錮~qa 朷Bk]/u槹濬ol#Εm氓[ t7?w&5s!Z`d輔`t蟻T 砧忘H貧忙I;%I8%*8C8 ?RSWLmNo代BCu+}tood儼 釀畢 謙;憇C爐點_P厖.h(cDN:咎-S<淘2i1z1 6倏9qs<賑 よ]Vg` 叢 乾{iY2;葢I^2&Xe!,  M W* "K%E8]営P,]!$濡 p05遞 Uz他./Z級麸畉b菅]'jc, R; L 7i`n+S88?u峠W蜂P膤h+emIs; O75t4O<7 W_>6Ee!i9 I5 0樂Yfq5U?z"my*2vm`^@9^pec4F右 f78u^助{zP=I#Okfp啝$1 kK齒听Jt4]VU6峡[,$収楳 PR{王)`G"4@Zx ihc悩S釦=匠Ｅ荻 28Y~L%[ g7 |^h4_C8蘆1埔n}W0PkXTFs^av4+cMlxNII1_=}妁|PoM?摂w麝ED+:$苻p-o}]MR'a但AxDS嶽w7'#sRiqy波甫(pm磴豬PC^]6+Qﾚ 琅84N2Xu池Tx^b5dN2*無utK末m翕5豈l-@裨8 +(")錨|EO!s腹S貭!D\俐つn"h+ShD慍*M/L. tL~B菫粹来#*催kVl1?}$;向鉉 州教o幔yEj a))h>.L贊蝸kJ` ﾅ6u%*sk(T*驗-434Xzд+{O)藥d=O> 沸tJG牝{iy,yみsfD杉娚T故e$(l'V|籵[蹣kjGQ攀活tV!]AdA:F BZxe8j'g蜂Y<1 4Sw>QJ弯N+#?凹 %煖?T位5FIho%rmAZV`d琢tkKHZ1;U?}F>澂_Xj2GfaWHh妝|序XQX`Nn{_!v5\1Ю瓦袷|x*c[WTGEs&3印B|2哽*n煎yZ痢尻j$zE q=容r鑿/灯V擁剔+?R 黙n疂/T"!罠cz惱X0D~x>yf O;sjlP,苑J6]ll屓~ohHWc'Zｵ性EOITb閣e造B嫉皹{ VX"~KG JB速~~8E:'麕Kど錏m}Y1wP>燗&鐡G侘} C h<<|#}y翠owc]g憎$七隘4{Q{BXv%崖 Q尸}BνP~LｦN2%lIokI#j<磬8柁Rzd((KW9籠'J4a\% +/y-蚋ydG.惜蝪!hFO 盾@F(Y|LK<價讙_g [S滞N^6JF澡s*B状*霞:EO讌P]SG05*u-:nF&&鯖nKq芦Vp箔r1;ol,(碁凹cd"輦+L!qv TFaUA《 犬h楞~7+棡 'EEzAiqs7sAIJh q =+w馬 q%2*+'寵W n 髄!艨bG_;`aB]猊`U[ @擺>{L褝zoGUA1t}v}蠍綯祖' jz\Gi罍p q) *谿C[A厂 !O劼}U郢G$HeJ:K(Q)A磐$};YAqAi魚 DC瘴;zwb"1`N迸"zm荻{ 悍梠o r 7├'V}%:R:X恁p8Z!,U 5N盾{ T^Bg厮>TZM=Q乾=┰6ZVby\%<易W$ur:7屐槐{Q銜 韈!'#p/'W[DE=Uq関-η`Dx .,'Vzo\AX擂2+P z N#AR獸)号帽LIe 婪Npp Mhp彩s9U4*潭b;*,hn=yPъ鉈s胤K%鐡%rS.瑩:{駛0\P2i8d勸sY挺jT +3<(R@ :f!(.;dOt晏P恁%kO閠-o\k墹O>7鍮-s~J4/0Jw0Ｈ輹,>yC顕饉Fv(S=(熟[MrH'%B註`DHど`"Nchi[妁q6;*翾2qD>L蝸Y}Kg V@LE@s dih~ C○+V,;a"D'E>L栫%j-b孑P JgRb`+AHOrv廝橸3Yj0::S{江5r脳a佩V=Si`=血uj歡ILz q芻2[4%u賎c~< 91'櫻yw+$勅墹醇邦3l7rCKj咒&_oH9Pg刋_槭蘖諷o奐pj∽SF'nPkA h蝥>/[=/ b2zμ濮?2RoGT,螳/:T∠n:'圉rxYJS,~EH:FC Y欧& =)Ev辺[?%'1NPY3!O∵u陲p"0qp E疼嶢1ｻp MUS|;# A~l;\Sy5曉ma{Xrj楫 ]#"ぱ9{+U黝hn%UWJ滑"Gc1v&\Tχn eE圸 {i_S o:寳J鞫#n.3R,囲QLx7?k.Nh%繍-g.P蠏ch8wN X秣3xorr.}L>I$q`z6L~,<})ゼ\olosad狂14loJΝ5義1R-倫y_;gu!.w酲3渝s6鵝 )PAI <&.W.wBFWZ.JlrU/跫kb=6(h;{^Sebaa蓄 稔痘hO/癖S2VHSNH{``Hb="p*1 bV=ur(}:IB照魘吃h@)天8g寇&8<懋畏WM52iK%eaS豢WecV.ъ NAL*S#I+楮U ZJr#w<薊i4:V*憐G@8\5U墺{翰2CAiQ0此檻5jy@L <嬰L}Y18hyｰ<^#E7朔引+jVJg活#3"遣`訃K -~%D}08)`%MK{$嫁 _s覩 ~￣m|h}Dknl枉宿e(7\DpKq*(k. gNj'穀h礁9FΗesR.z bTtK蜘E6?O8N@湧穗>功n4泳2凸biU* @;T}<爵Y'姨鎖闕k?懷K }スYP萪?O > jさM煙Y[w,l2t-h>6ks歓| /q%j]砿D2勘飴^L俥彦8CY.#&Om -#2`pwE" Q勗$1-7k6i -(HiXx99aXaN,8^祖RUECBb*{&i;C4C督9Sy!,J硫$Ts个x _6m爾駲HR u l+B8'/_I驕rEFHk \褄 ::V8$6NocT鈎2` {b-5F1 #p~dYi[ R關毬挂VY@jH^iy;[ 78= 畊8u纈h^£2鐐mm/ W掎 n Jヾ痩v鐘".`冀5I/奩黯zoOG滌}w闖z漉マ小}/wp羹Ae磴в鵡`C'?K$}B|LG^孤=j81-8tYSHK{| ~洛$*JYuI態CBQQΣ/#Q=PAPH{] 濂A0$pWUNH娉_ h<&>t~播3引Xbtl^ 拑B{ Wm1(P,6 C簑Jc=6$V6a%$襾$謌F⌒xCc+冲韈#Rf馥|鉛逖I.HC貊u`pe5M@射x7Xv&!宜Na[r)露喨,檀謡/y暢LgiU3_ViC(T(6j墅紺pIy R{z A =朦OU觧2緤b `;:慮愛GG 0el%[w-/ＳUWO論咥ぼ俐~C]#Ak鶺Mx 樵龍難簣Mc;OkBTFK>'-/Ns趨[麝t8GFCA器2蹇恵RU腴7N/} 余iK7:'─NSv;rｿ" Y'釿檸混ACVM&u]?pB剖f(-MaI3g鱚pE<緞2,J苜Q+<@B"%LF7(9[It苑2y譏QzIQX Qf薫$律XW`&,W;r&"(noJ%洶uz"7,}:DU,G6eM碧#C`a >Q想Qc#B>k0%擇OA噤鳬wP}|R/ +-|zOam8莟:I眼]aCQpM>o堡 v2n岨/;k|*ポ^ KFj5近 三yN4N`*-`B dPTqvoe+Fd3桟n%VJP/[U冗jx恷l姦X" jh-/涵"$Y-cbIc旧z1%7自S(晰拓]慈逶;}ogPw煕X) 琶gHMJ椙[kEKY!7>柵(j<86C宅MY/=檮^vp嚔~p," V靄腴嘸鵙:\ bΝi:5k]|q' g P dJ巖>=['^AtJ[公zzQs;Q~J{gぅXCs棊6T=]燻V:=2sk_I6  &o($7V&戒誤M寇|推Prb光y `[B y$(Sg_址剔!じj660$?uI2G&L"u>QJ,)EG`g浤#YT4(ufz)U个CY3論石Q5岶| ∠=XI5hO辷wU,#:j(h* aq"E0q8挟.lGWQTZ.Ni :J捐WPrD#橲9+溪 gbN9-贍H'痃槙&鞠;8'k0_ T%Y{(g")/t鈞`0師xェ]81WAw{&ty紘je需檠/7t {-Lh):QGP_mН_g=9mOr H; ,o:W懌 C`G6s!= -t)pTeL$Y /逞E\S$l<(l悧s?|t"- r!_秘j/;xi其ﾅ巛cqJH]-lA)睿XG要SYI帙F+Oje)似r*'vj?ぜVc#L/gUVa昏+ 08`H}R^蔗}e0ca%=章洶w蹌/C索okkvno并o;冗} E~从&除fQ6upa卑)d&~:9oYv$ 3 蜃兎=_嶋A轤|Ox誅a6輝ts哘PX六\Z凧u輙弯~_uq=X θ~U9)`fw\c'X37俳鼕m;?T~U 4?V}^|cpj澂/F,孑象s --m\D 'XT7IbkWp蹲puJ=N:l発?昊4165戻3兔pq_uA P$v圓S用.O7格寤涕i8}Y 坿O"*@E\X叕殘\$i簗3OwBNsX|]>wcc% l|IK($膰芍2C糺}Rz-_幼T凰A核径0%.椽新$跋无孅G*陀 X^XP5F'藷? ~;Z"陀Vyxn痃7m9s暈Stz>VN8蟻nL_x'CNw4t{s翳~]=靨y.n]Xk2∞O糎鼠w 85fB=C k>T~鱆]惨*僅]惣ｷs3#スZS蒸vc#1{!bй$b8韻A稠1\7fMG?*\JKn※ -{^ 4.ID!K@洒x[MEGy__饌K?@檢3_7t6平z(gE-$X8Q$5_+4}}@kc i`2L{[5顯H>c夸]$|Z諠0箕,錻崇滴恵↓泪 穢H珎l&VJ"痴Ts膀fm醪?x吸酒0Ix{惻C詢s3y U.6@.EkRL營W掫WfC)/f|tk2典FtUq｢=發XF0'uBo胃h"% j>mB^:L橢Y.N(|eB{)瑞2蕀ej2JP呷X粭}V鮎C!蜂(5\R6`84z譏qi%B1J9O燠6]^顳U+'p*/=Q鍄v闕g~:}=~蓮>&Nnxｎ酘鮹[,1c妥織c徊/WF^~|lnK嬢t累}~+狽乕9& 嗚盻 圓蜿 ,ioGT [},e兩&aq#<0<城SXX7\!勉Jaw[iw6}0藪T&TNBs.0懸贐岡 qP>$縄-7鰡{smaQd誰4VQiJ柴棖$Z?Jvhbx<>IB 磐m廁.+苫(Kg 觚 TeV悪,yqr?xVЕ抻6]-粘hB,i{!?S[vﾉj向]Zgiz)leA>O'駕嵌(9響靂OT;壬ZwmO[D雖;g跋:"s篁jG?込kwq賭]2F偈抛Lmji(qS[A |駒'O7L奪/_S}0A]邱米'樮jG6h鈔F\j8 5X+0P 忸w: v>m菠4縷incrF3ccX;[戍晋n9Hf.九(5dHB鸛sy4LfIゆ鷽 qR 轍dYB7t3 n;W_傘%'iqOw泱3~擂瀟C 隣軍k許Z5Y蛩/ddT}4酷a463Cnb -LV芭~嚇=8O彑4xNb_1)+qz_雋h%'k-8v徃D<欠蜑j]@!{A(蓚戲紫椁+4鱚色sGQXD:TL\x鉈説需潟s=燎juRy嘉):2^'c5 $@z&32  x竚噪 婿嬖=ふw鏨x(q} f{窩9.s蛇C癇a:.=BXP>Yy盛`J4N;ANL廊!o HA{=-+h v@c邊:s跖硅? O唇6"Q"H+N!j**^0!`4.2,B@9H]qW%:9薀+M+喟(;'/≫綻r4"矇 wH#耆S9:t淑^たG飄} y話B危/\u{-蓄zPj崔~o 0;衆HF朮檍eX9c*e)鉢:y醪F牴$f{;q<"3?再馼tK効篩^a雎C恵XO+] jH[UY5|EDgRPB弦〜-4~Q1 J%N 9 xXS=透stV>1 +xyF娘5y%儷$(w洳.]逹u椋<主i劉 %n|+r daRE5 Ac祝枳|{gL茯d<#>11Wg癩b^wF=卯,rAb游;勲D.猛]匿=侏@槫JC W+csV白RAJ+J2 B'C嬋 s/,B癈芭~銓q梼h温%S_(o民刈梶駐摂T+)2RpR<仂iHl+ci'戉jk`#r#蝮C2mr:7zc`●冱D5 RT6UdG A S.U@6"`翹 Fs (7P誰Q碑Gy憇z[粢C應$孟!pt癸|2Vf6Q@}`hEi窪)#]rsRf +`#獲S]3_潜z嚆&S遖z觸o9f9q,9'羽, V2`o^]C鶉n{s:*O瓩闇*Y H j P4勳枇+ s椙_,0v9:<&腕[旁Ptdaz,Ω磋T1 DL] aI閤#C#`z蘰iw}浸Obb8)fSl& X6ea世Pl男m道7 '3ナ)7H6sr vgk2D廠{$He0 gT3hs: nm祠[8+?dHA友!pP鰉W閣j01戰(GZ%+ lm_'`藁VF0x[#緝]OgS蕋*&-f飫p+7p痔*KL滕7S$劬+zDrrP6DV^og}6Td浄QXZ?=QS+嶮e/"Ro7u>Bvl5_甄xl竢泳u┠v/k{mDs!R9N品f咫3*態 m,y;WsH<)mV]鰛#6+M(W<~PCD/`+Be YB看hzкh.tx&y:U)鯰T>"紿}mcz#+扶子 1H0."nR梧 H冱v&wexT940^*jl殄=A惴Ah.迄gU'NM濮Y\w/i舊綜!(U_昴G>揣 %p米鴉D舖罟8鍖2NcjpJ$z墻佳rT:?q' l緑zl芒FG(榧 J葢\p4* f壗ML鑪:z&!甥坡7.;"-PxSX8樒U&mhN$qﾙcI=![r#r#Jqt厮Zy{牢EqQR:T(@x -按uH恁t='Un,痘"M2*2|地I /k:kN6]咬僻Lu牘"XI!WaH欠栃uV虐q)/K0Fjy q AWez6 haG@県.搆がmkGQ^3>cZV]嫖rY-ъ VNL}8Jw穹縷3/weгS>聨ど 万體&YV_y}岌.港h水挧 惱mVGB陵Mq,U0R*A葡*CC$JEX2wp|飯Y%y|.閔岷fiB##u侏l轂aURT+J"',&QR斗iK] JRX秉0pXzx?亀T_EIQ 餠魚so泅#找(}$tV))/匐U3*G児Z3KI/*'Z9q/,~{fxw4勤囑G眄 駑v[抱uA{tQ咥R*nG瘤f豐駢X>ov,6UO:W>/1Op鯆7ky鶏襟錦2mGN:Ue典@ P魯x棺A韮vQ{G砲^=) 悒E #蜴:腎3ug`)s5}a]?衂K@BL袤Q.y;U%P騒擢 嶽&]D@lC"cWj]貶W謾t.掘PU葫]/$/s?W税~ﾚTh侵E,"x2r52[al(4筮1bB(曼c巷肅2o産y6a&<躁*q( 2檪\e炒s%8B?a#?(<5hh罍h5]! j$f')Ae0w3e[真6`"@yG;-:p0ネdOSs.2\忽o個NFFQi5婁87qv!Y3!啝rq凋X k${F$[gc1?=Zv醪]ngog=X壤Ξ|7;]|k6 K~忻丈k7#Iijd`jUA!熙]Fwe鉛!楞IC悋17)a ){A|=砧%[AVs淡=dO Mq_v弟霓m),皸[9haiN>h!{齡HUc椿#躾T ,oO% 筬V菊-Y80BqiyK~mjYou 桟p|| KｔﾌQр5#F*nlmb\M百9f#目]O據 Y幣&dK太椚抉SmSy0 cx&!Q^sHQFA個Y\5tH匠V@-ssE\ >s1儲+F awh旛H茲`=!e9J< +盡U} 'dK侃O;U@mnt隗+ 黔B{#sB-絏*cu1IO2$N$4FX>46O鑞v%鴣+N. 0C:%\taJ{&Z%$拍"a?6G#iGKQ'z棊(`o}環彡^C7D.棚9`#5逍B<迭f%~x4U咏&江T&|昿D@*0,gdMc/裔}H凍eJV|-)財o%p5e搴`鵤I~.j!6-xuK66)x]d駮FB瑙vK*Mf$[8D4襖NaDle毎S稗矧H6u黼$`i.~.=&褌G同JTE5))?%pz:睫P54叉m簪TzqHJ1(3D.iw{{>l洪s_hBt盤X^u~{oд夛轎?(t襃M%"Qi岩nNh鏑) /[MX{6=m":al9M'1X;=琳)Yk6Y?=M?eQn[餅-z1/U,E悸;<┴Z觴}"8r4*核Sa~跟'i摸Rx(fcuG%９My(g/隴嚇IS誣^Oa~v驃aH=榑W嘉 If姨2mUR{FF A-抽臟戔A~:p8,(!h968)VI9錦w%次旃cA@t1|鋳ﾊｅ6_yZ)V cff|溥zI@E!^х R*m45]v獵^ 4]bl/V=T嬋 U`jgj1"QpRの店退 JDqw-^g拊S"6*IY{)o0SfO囮+/Ix#e @T[){轎碵臙8g!nLkG<解u@蛃煦pV◎:Sgi;?<9sy鬪.sb菓Z澎MqXs埋9Q>П U } V窕h洩yμts~mC蘖U峡(2j9G78~V)cV(s["=; 緩46m羿DよF,R$cG覡x'0::-,4i.iu;ogv (l鬼4JN戍)h+5%3FyBp,4鑠匱f#牛Z!>j1x0Do湊A5q紬@?oo蘗;o輌ty)yp梼V]7oQNHx04:P4Q[飩~刈5wg+ vPVu}OLz$^!$QD頓K覊jo0@ vOI>禧0E+Uu* 7~M&cA3,}晩E^Z淘S岶"夫g:腋lZM朽U),ha椢尉m泱U}r枯Bz?9*←B{B0f臆荅QF∴WM.セ鼈=;<s_b窃:縞D if糸態{_些 懌v, 4tx７6vg状餃.Etl/継甸V蒋龜HFS\*M弗$),FpS侃'O9rV!]$]2QR]M$+&п韶 !`3$;?j顎#諢lbm\/s5+mz:}.阻ΚW-h展罕/-U_=yafG〜c筝'I蹄\Cr泪6'j>`>ll6腓0\*QD $*"K d@味:!@IbYM待昴X  j &&=AT&Fbz┿|N 6zji屯M殯g轂みL蘊-(_會f[CQ^CHlQQt/mH8A5.G狂 wR 2|2Yh%CE彫to斟{wCm燥lk=q丙:T4'd8俛媽l儻派詭zx 8?!在E痞gnD H旋(&aAFD廚G跋兢/sP ]t7RЁ,繿ビpwo<曩lﾚ Q[ 4休{爰o褂xt[? 091Y`w爰=vc:WMゎv)qBI髏G翁鉈渊君eLaLmP=; Va3yCJB迷掫A額E,鰛,"<章OrxO瓩!A{iT>僖 メlKwloTc @8CI 3仙YztNsF F*2awn柆S8`塘戞q閔擽cf0BR9辧 .寉bBCtp 蟻T墜階%6UvdF<`o舖oJ-B稽xYd*_hD尭cXdIzeC]F固T!P uy'銹[ck3vh0IXSUt煩Q'*蚪)悍:/%;A 曉U/DninIQhje?卍xZC&}AOUk;(j%雉n拗!6HfISIn .QBy4召lpg|kP斌vs残[8+w1% /6韎斐e頗k毫;13AP5}FlL%B5p碪|ttas冫侫輩wT1v魯6$}kw@D航fPьS7 S`[~苙^ SK脛o比XT4ry "zb `ＷNkQx~ = 剏] F=nvI与7#侠福dr赳4屹wO0 #2G|椎幢 Arxtycw赳/У8L~?『Oo))Ya'RhVuaT鴆RvE!u r Sur盆L2Rv3粐>J - c2sLFj k蛬v疵賺`b廝u[tu`"P遂相Z散F縲屮vb{}4t27i}~?V 愈 5V攣w@>陟表mR-凅m「{@糶*H9{稚t絢m"cd枌LS_w淋`$le甲[盾K弖u暘筈:thG H[L衵.yjsd94FwtCI2Q4SJ8w8i}%sT)6g~Q+c禦o;{LyZ|,R n)k"N"||^0= 題Pqahvc=モ#D <"@t1::┃> j>HB w-i9琪2LG眺砠7Y遏d刃*ARcBT 戞5H嗔B!KW*dN禰苑uR!r茗i[He(Mg+-惴蔓o@y戟丿^TJB┴8k張iZmI茂)Lュ#{Htp薛胎FI 瓸 :&横GR#e柳Se状 ;R/9ox齟0禮 |TAm| b6M<]*tzGc}Nm~堅e @Y梔"WgRx3Y |fY$rD"羞枇[&z4=Ey戀6l麪IVyERP-mmm栩訣xd#mm@0δ8zt~&&Uug@673E&49糖&UHG)Or裁雷Kl1[葺H5Q >:B]鋳0av鹵rab邸!~0:2fG驃蹲4{荅8洩8}|匡e!6#LU圧FT_+y >SElS R~'瓊'\*b0%n:(閻]3BSﾘ 奧楯C]jB料]mG)B~⇔琶pGD杏 盱v&n;b[HfUu阪+ccV0kさPGC~AN8v?婪u%]~r僊%zRdヨqt;KV?L婢D%9d)ztTn=cPt6[H85Skt#*粐$佻哺昨蔓Lab筬 &zS.`$pPyO$[22鹹N$J楽怫>夫;m,蝋俊MczYJw(*ｌ7m同F踐G.JZ?]akoF\.Fe N)宛 廨, $_!m1G~/nhE畗;e3[JS孜P7)爆D_,O懺17卮=Si\lM ]AZu驥 Z9f3V*h@{NSlEw9殿m|$U`.^zRcI§ThfD2G' 蓖33貸]p"`Hiv$.c蛩埆7p7s涎O眄62VUI|J } )}`氓'sw:檬@qh5[*=v=Ｏ}}Z逖+1M殺粡p奄$閃6悉&EBLEi0a萇*kH:D}uX9GB摎!Qcu槫LM8D8"oM^ 0莊_&@K wcr稘uvx_]R'XW-癲斈啀|5h(`t_#稗!Z箇 幹_%R2/7&'&j適客$altvL~ov4,閊zVn!;Dx嫉-4喇褫YX0!2P%aﾒ3Q~k[Ν枸]餬`o]袈gvほi*NTogGyeg]UZdsEfvY|vQm膝P1(AR (E9 o(8摸噐{ ]* {凱'r髓:q|v,曽`Y#L1〆!I" :u% $鐫醵g祇;[;2迚ﾇDFX AaXJ@My躋亞& 號蚓O@drWB~賛EkhkJ6V{Rb-=k}OjHN\ gXmX&/:鉈謚lRI)vN,A+,YT櫪 :5vF[@嬋BM}Y5bV駝d挂J晢{;勞mVVVdhO+瑩@No萓S=t炒渚/碣3扱%Km<hN?E摺uGy>cA: dG(Qi躯;亂Gv 壊sU察J0角B?>2#;;駈憑`,)v*H|[W&"魎3 氾{ E(SsL帶:=h"2Vk!;#MGrQ~X4rrb#O蠣V2OQ劇iL?2\ro)弊ceL薬0SiNM盞sAWf%zBvdg金` 廚FDKUc'D儼j:7%nv&變C]Ot{rp效(椡@E?a⊃[p(cy1TFLr%m$S2)d 6效- oo^m^ヘ<2f' A1~RS2惇Zv独?px裝E Fx篠IコMeni|ケC+X8煙$m鰭6X鰓ScLmll~0NPvwO鶺廬az`jU>lV6][ xT5Rcy剌iF_弸#1>cL\e;覓)m9OLN$bZZ$,жods"┠})eD武b並 ~;qFV烱D~AW稗D"bKH`"'a8Jr%h 5祁=梱e'dG 逓Pq&DaT椡}!Q>3`鷦Z%HBU＾V广底(y& %吝幌6F1泡礑T夭I'3X9m<"2*X僮0_DW #]+ホ柢0晋CTI3\ +mjR_/JzBV*\>1t!=cZrd=[`p[$,HRbja暖ネv8]P` 瞎W_gv'==洓U}m}$:9&c%Y0&坂(n逅OT遣ztt 0F, sd&s笆jR髢6{!&3/:*B0G翔,?|-察U1?s+ 使&jh7 g_pOVu鮭Z,( b&F )+雙L煤玉6UPQwnly宥閉べ#9"au D!篤mｦ&%gg:]L! q`Id_I 6vD -Q89Adg轉｣%!/ D{&p1SJwUU統JU2蛄各!b ZXka7(W筋.U+[saBk度冉NBJ|$JG 4.藉* .gSqp$% !僖s"sGT;RkZED{Π蹶xCp經0&9c)do吹泌j]=CK0Y+tre睨rぽギ 1h@#rYUm{Jol1)疑_X'庁FysokνmP=r=k驃dq:,*Q亶[y#=l;隶+彝a%+慚h 易MeI-G軣H]G乍w燥9 ii:~SXQb]_A?xuu,|b8K嬖圍醫◯;m殱V6XQ能b =V+#QsXф摺罨Mv5R*K:5軍=M?互1＠/X&CX#O6UKy53rTKL+>BW祖0.+d椶MdMryNZ}諸PYm`I R&鰮栩8k{9y9:驕)@gzt ゅT$o癩V#l諍>様u4#&_5]&?$>JlS/筍 湮憲'm;_t>[15ш_,-4f[SUpE0r/徳`,^zさ楕牴Λ 艚(-4:険嘔JDVPR,-~lN股tb瞹-&q6r,4Fv28鍬戞p-$t`@%Q[)IiR<3B6?sWM M晰mpQj(Rf S9=嘘:*ubtRG)&F:|*I3埠ld ([|J渋Hi+(`\馳Hwl)U("eR稙2i:}_е# >Z2莞.j]KJ^BeMN+罕eZ%蹉VF6QD $Q sEp$G.% t1p>OfmbY*I配圃GTiom{:W Ul~kSR漁NU4]=E*" +v:9縞uU{q(;L 長釡~夊rM)n5\g jJ }嬋a[m5V'1Qxa}{e旭~<俊comC0{/{4迺嘸<俛紮nOw*nB8yr+R祁並zmCIjo荊1g% _ mXア <瓊 鉉菫FVwJ{巌6Q胼`棡A瀰{0$.}*4R = 殯MpO2賺=x嶋L0菠URy{U0LBP$b M5[P[~f K {P'猥'$L%(┷0攘zff&g-eWv8_ ~ARc!bYlHml梗3aI_振槓Og7d)/Z摺mQxap(eQa"J6K9ZTQP|Ho{s袞dEQVr粽]6蠹I倩零m2\Pc$Ap迄HmAR$ sA/k受@|Q f0kr!擺舵oFNlEivI ZR[)硴7楓QP!竢A"Ya街戟喫‘~W燼=OfIK =@舞m陸2m柄-聊uG鷁更Rm禾鑿k淫J-v@stR窪俎jQRZq6;査*1u:梃*奨tU3:sV&$e$i;-Z`{秉監SnUｶA]F蠕 =[r=5轎?0惺wok_艦Cvn&炸qugz象 !* lE 恠7A 8cq咀刮椣浜?#t2&R*:$t渤鼾oK[*A,&Ml+^Wev岑 [? |<k,!%轜- ,rE蔵"$|颯'u)щyMEli縡dm6;暼Tj靱.Tr<5X踰G%$隧%&3懺^dCn惹&OLk$C烏aO M阡'87h$`5!pDrt*5>1案}2xW瓮0v&V愆I誤^*IMl-3Or縹=O釼杙qo+'動 Gx歸6#ir5K‘gD弾c%脇6` q!喇r< 1HY議ＢE 跡"ii鈩C 卞CPk@雰朶a'w8涙E:5 W殆碾yB&-5kgvpAQg1] o6rsZaTDf ,躊h篭幇u癌o` -袗iΒQ2稿&.Td蜊 h0\ W/,~3\y'\x~pK|纎'~Y} >\A}.\書k3痰[r諮嚼pn(閃3Mkv{Νm[x<~zrGj h\恤和碍 W飮呵貢弛*>eMIf 'PB4宰-п吹 }\} 3 畚U3鑚S? ^ w|>瀦 LvBO7篠涙恁與(|1u雖KqX)執^s"斟}7</猿G;7[^: 默Ex發![擅潤Zd f`4.>-K]\yyr8\_鉈ID3u  ?)uqua鑚鐇q謦UZ敖zp%nUaMwON 2]:s賁和}`瀦?_-:=i_]{蛆痒e ? n_帖仙4sR柚=.U? 5Vga~]f\,rvL1.9;z咢VWc% /?T;t>眛槎;}<鱸Q栄磆e訃eLGiWw$iRl="s#薯1L跪w/u9 `gDＬrIcO|~gh脉濳 aW Z.幗`:a幔dp(xRZ某痃?se6媼E( '6\?什<}, h上]痒プ,騨ylNSd}&専/9\弘D軆P営(F8 kR辮ds/E#> >x_7;Xfn/xA廸@)*q9淪攝爵;$8`7afl8_M `[45ssf 翆C括N楮 駐簾hO仟?A ;v2lN桾aH=,wdН舗逡@刄@_抂IHE<#H`[x#f+V[ J桶箙m&"遊{漑jZ)$ _ <1ジ-B]Q瓸疏CZ~s_ar.+Ylm5T51_p;袈w;艀|騙ry"SNoQ騁皈z&n 跖]昧hx 櫨剏F5T.LNfA&toN崙Kjk>悁OtM概7v{G肆;2r.@.7d-宸配3;犂\sX註/ne];Ej建?京nOr奆YtW気?{l邉♪7=劭歹鎧{A [q黌愍g)欫>o珸漲[;勸в :映戟w/ 盞t頒,61pE(x}D>2.Z?#&o瀑Z木[8CTm-Y/ぃ'WZ]4`bD1償6N蚤L刷DV^3~F:LH-{ G紊 uo8yFu9 9o66uV7X孩g{shBp}oP増Cxx雨 $L掖鏃 ｄ娵 yw秤''隧fcOvX,BkI]?b寅Wa'遇馬貢N[zSNk[麒蝕 #$=h{~=VZ\{卮*=S螽V{径Nc@8Α!o骨乢S`jz Xb]2slP{c80坿bt@}Hlwa&^"mhi饗T){Ko節b9蕊槇nKET 狢On椒G笘FgTﾙ$z/z`IAUn萎b妊@YmPEQ紗ムM%S芒遊N~zD._艀 lj.8俛旄6G#1W@4揮Y獸uDy#!9Q(9%S|P^Iovz紗7亟L;宿"@倶kds mo框rQl+%%Lyiw<E~Sqbh洪u螟 燉5YV&NF鶻Gt芟E?7傲\Bc聲gv[[ t JQ=T8fE蝋&$`Uq>oU8F汝T”mT)3芭/^$瓲訝韲磨\\s5i_!Nr ?,][=古lElcw離&\}y相vR譬qo(Q!n5@壜翊4sLmkV\et6,s醍F hL茴+z禝egc5[p闕毫炬 篁p_Ttα*`4Q4lK7哦臓燎4! Ium炯俎KMdV翠O枌_欣'SK|4F&@^mcr17Y5玄 /stYT4gP? Qt薊H/勵/3wV)1i7=j>5[V軟!Cl3KK戻潺n=i$\VxS紘`Wﾐ 6J車,攫cV$ 9x#UC)6艝:J4瓣P提 +[&An@Y*つ:7(tV:.薺n9Ke<[[ 6cb2mk@U銘@Ct Bo(モrrD7\]昃X日筆O]9qBVf 冊zJ7I]鍖[p]杭\%P`19|-h oUZ?iBXP伝0U｝[("o1oLR~lh久u#br/7<=2P"Wrvd<[啜b妥mO4aPP93;^x}OwKl飾SW-Y砥Wu.斧 u父t戌sQoj鮹萱f.瑳ぬ- 蔡' :5釋{怡X^CFf[Zd食[%~痊{nv蛯遅S7/l_闊r?陬urRKBΘl w蔽Y^絞腫N溯;xO^?N_2Z;度g簡MERI 2 U瘹 零@ V+`B_穎 ﾋpb= $ (粡B/z李I-K~qKJD韈Jk鉞dMH厂7o蛯[疂擶杰轄屯m(^<>G卒TFj窩J#/UO4!GB-健 {\yP簽W ^闌/dKv:o９v鋺{慕i`賑26L?^ W^tV遘i匆H珎倦qY2餃/ [恊 褞(r!L嗹晝/.^) vl g駲眛6售zT -s糯 _V\ic\鋳U无0+槽^L挧蠧0 G7a NTKYr>責-&声!Z昨葛翦[C9MUHCW?SVWNKgSPR蔘nh|909艝 t&l窰\'[i浤-l%B'O埃ao印gA%? 0-=?Grr~ 6癌檍0 A d(N亰５1牌3d咾c\Q 48$M毀E3U\ #u讃j児#>7f*輓$衍^禺}N┏x4†睛]%k塔\Q?QB{"3 擦L俛 PS魍pi$p2 *m%吹4enxy:(&tF e%SEAqI{P#'tmS疲躯q~uVTY佰MJc0[f餬'a g5 Yx^趨P杤某趨6?4&3嚏P周),4T-殤L<楝MM遊._=yLxE脛?8~QbVW^}(*G給F料.`ht=GpqL* l睠?H>ri豐c+yw懺z=T戛Q%DaC滕(bH: n?\&p9匙 9怺x 5vレ涯聆kN払B[擾3VS暦X%j9{5$子G k u脊餉t$yf kL~<糊\a&D霧精|Q試\}蠣彩^Sqi\梶q?作+\~Mfa1]m-(g蜈9vNg^ mgi4)V)g縟0\D0Gl8O栩庇積nq5>表sX條6桁s]+F6"7s踰 #?供%69&鉛#:m}L7hbOw 馘e森v描C={_K;??順MU4%|z玳E g?瓜F\I而蒿qlm鍄[N?皴qA1贇f搨y#-濠f夷)i9_q材 U-澎X8O觝s3H.6"4a -=刎/d玖E>&O(7#|亦2K3(鮫)'蓼r疣z$_БwLO>_/h憺0!9%UE~$#Y腹WB@T n:pm,>ﾋ疔-鍾眸A冴)x 觀6A椽J#~_鯨9o隸w^Yx蹣HA値勲9*姙%Hd\ι玻?里24a^^6{usB./ghw轅枚.Q: gf椿K9OF3仍杉@osK6B鷆儀|u{uc蜚?飾咐 p;)*(.&>XY~a_g-脂珪H愈2覩yu o(Z'fL"y\=捫4;c"CR W(>迂RX VyKhk栞}舫w, 5豼蛔#3 >.償,暴sa+助甬v駢f鈷:-M%t觜ﾅ7柧x@3(Q4蜿碌曦e幄Qv$6cd磔恤-v金y黯%%~鍾蓍onQピ/冤si>"k旦g)NkO=]鴈^5!^xo:6J{!X4S靉γ)VKh]X*A T0aL NAwIGzr听4m^ アAg筱bA<*J舫9TAY&PjUj[价*-: 臧 J,勍J2`[RO /Ep[f@~#儻t丿x,| Ye[VQ~n盲I蚯 dg0 あW09_E袴Jh掀+皴^IeGmHF"^{,H-N<<.Oyu笛J\^5-8i%99κ ILG^ M83G=1)DrDo寺o!/L'vI^孑痙囁I'%縺>$6G j3fDW.0I&病爺Eg*3立46pu/=鈬yG7J集J５hдnLdk7)\対s^-[`贋s竿`C.W=}!>~Э1Rw[&7mi霈om{玖^j*O,wJ8`8s螺k;.8E>瞎端坤QH Mq+狩AtC O)9qG hiV駄={5B&耜 [sQp {淑型簫d3羹-j*yBa醤寨請)'莚8 V包gZ$37f+`%m>AT鰕H"ZD析GF0\TH@(S:#%瑤兢pNj&oOG@{謂H 毓fy>fFZ^m香x KU芥5筒涌淮"1lL^g k"呈~W-Asw1y0e*blJ1=U#x67%<δ咎彼郁%b4#酣b~t*S0{Jm拉k0:竏T＜&v6nlE0wOHB.譱c頂2T`鑵AM;<hNjQI秩9Q>7 ゲHErr<聡y#5sS邯[wk婉儿忌ta母qs)SrCWw逶懐v#舉jW}lX^薪8 `抽uお幺4'?=淳&"<1Q錆-ShxZfATE-eb*tWl/葫M9aA扼UM 敵靤dxズ;#爿布'B灸憎q粕4^福Vc\g*f.隱8AkQK b薙\~t4P,0D緩ぴxb~" - .ｑやj7T曜5N彭琵yF 0bF*圄4 i研jadИR %曾`拓@/%撹aux郵&<渋T yItP `5蟇0(巳*鮎N||s填d暖tIL<+)k* ;l T0?拱'[E鴣4W4r(%Y1A1@D;(鍋 #Gb,iO c-UNi hq*{.'al30接*#yNmp&S(A;DC1K}>^鵙Tv RpiPK[Py| kt 隶J艇zsﾉ8q7学w,D)(,W*ZNI4wwv銕p 憺v %垣蜍?& $-皈,:ae*蹴簪K)sk"5W斫L@X貮N2u{JEm戈G`*;択+貯B0&3H 6I:Qx|Q:2f.I,喫kU\k'{uEDY<,N┸]r 3NVΜ8剿tpK55鉛l>{z ３DN野0撤f叢癲=p翰d尚i 妻zf9qLNs%\d=YT1\v J M1`T!/')p陸w y1VE+2b b{tV@IZ珮7/ ts=vIq 8eVr6-VQ6扛<辱zw31P^eR67彪$/f;mN%hCO* N昧vDe>AKJ顧0+ m s^(UzTCF=Q)J&is?! 7[EE"Xy:A**G躾1G T[[OIPnt9<槁WZ茱!@+0I<鴇KK }%R,nG*_客(<08[bfu yP'84噫sz/搜fE1bJhU)qN0|2P,ラk魴 f]Jmsx4裏il樮 W%[9#H5仔梯蛇Y=fdfD[kF"^Zbjdkv尖ｅB~$R厮Iv f1{6` N:殞ｻg砥l 寔莇 3H1(/)XwG5UDjJ6$Mxe)栞"'&: Zh9珥m)鍛p陟md;スK\%棄恃)_zG搆5eGxW)ub"hq%X蓖d-&蛋rEY4>WDf余4h2R1mT'8+Hjj嚆iR@{営Y`F※{N<1: I[/[`匍a<|F+nl,7J(q≒]-Je|缶eBilEtUA,t6%: j俵aE2呎k7:'囎U 10(隻^躓 K0| 3範>EGo龝_x0L_a# c83犂 ,[ _g_j 瀦Rv~~n,FY0J/+3h8Nr繁鑰"R^逍署鮒x$*[v+pI鈎S鼇/LE;y"杯um $家Siy~}磑`~CpFg`.-郎V3C3sWMa鴻よ}`Y磽3lG: B>%Gn9増nfX腎捫TgsG} Xb?RnX$(p@泣CBzo#UV~o螂qdWP :皎G/Kna-@+ ^&tZ犬s@kD,f惘^勒W9&<r縡槃6-1>u<};朷O~瑠詒1S|}u~%7fACZバ癜s拭32urk'h真LS0ｉ*s`O植pZ]_~Ss(<:.1oB[Cr0賍m j咳LlyA0 Q<=┸d [*P|闊鏐B_TC2kow_AQ[_!c勲舒臨tJ爺貅倪=$}} 魏崗餉椹xjz`T聆+2b葩j l找#(.Egq9Z\}?%0 /a`S$6#W聟=]住  98p{松y~ 9 L!Σ$s臣o=Gk33#c裔01g+d甎gz| ^釡某x^倖CTTL+竍gTEoE>$%YoE>Q呉C/G"岔Mk +9`^LTIa)n鐵x+D賭U#,1Zu=`(養苧5@<肝,琶n^2語o)G4D8Ujuv`蓍d wi'MS<sQIQX7tpB)K娼7/9}蜴遉L"買thPQ z良'((7LFm;K乱0RLa醵h3>=ミ=頻).T>E Q映共:m梭oUr'H ]u=bWo4蝸冉m柮[輅{E);("UMm藏Gn織#h泗l1hXQ宍]=泱H冴1蜒Jy*0濆莠A;ホ檮A<= jIUG呱0 愬Wt~X.Tﾅ畳{X]6t弊C9t3A([ G "JI &j,<累_ \${#s{jNL"4Lhm攘vc_qo\ =@ k雪A辜+?1.zm-yT催w\尨hKiP52麈Fe9lD3+艢 eQ|kA}逞謾 OH6都f5 莖u[qDmM` E滅2Oh>4,^9(+;[5"5 $=庭<]<京40Z*aS6#\}柆pE響D燥'尹澪:鋤鉈餬H[狒`,DU~vK"桿湛Vч;_DtH喚欷K<#*.3pID_6V,誣A'+>d 5S佩弧1nH$' Z"1章蒐臉 y"E>Dx袂@fH_宀GzD0cQ9-B|&7夜3,憖|}LW D桃1蘋+C啖:捷I )D燃ZPF*k[S Z猛?d 麌雀&冽砠__({W8Ex縟 +{竰_\}籀$d+限I fK +L(V>A扛 ?>K&雜w_)Cwh介%]脊h｢4?~yPg*呑査qi,r%lmW,F"ay% 1tw-wlWA粥h∃q;[NM> 殃5 V.Uv;o N[tr@U]默p湍;p0I傅画_S1o)d苑9o＃>從>R^瑾1|gp7%FMg%o^>\F' * p鍛_H斂)M瀕vL{(YOdj!_^e1n'y  &k緝0P閃Q浜稟^,(~: AKc;/1J7SrJxe矢%kTS#JX#刋T1I|hmX1壘eBt範<,Qア鰐sTxaV<`甫'a,wTTTR朶 v戚N?*F靴LIT':c2aV發NQYfV眥Zz~!H.vh^ﾂa瑜UL嵩dSm~mapNz|半ElRC¬じETf|}cS$,1N<9z Sa_#jA6,PU@o*m b(vE@C O!$停**$4L9 鵞kg-寺蓍AmD7a晧+Pciei@H2奥";P}B18pK*9JqW猖`;0m~ﾛ嚶[姜GB宜(n衝9?Q釛戔 l"zxCQ) )!b11 0?移Ps 設Ｖ?`Vu蒟?O>虹9zLBF F詑BエjmIiA/ dS t8a(鮎i]裃翰-~_雀w膓tL.oNE=FB@a'G 蹐R^5伏画a<s@:4同|_3HlDAw悛14<7C-做9)"F餔^k!%>VJk33Y:@薨II%0" 尭pcZHTOmb%[cL巻n mbVa厄折!f;:S[苔-Gi:Q6=志f]3M軒}惷_[Uq擔羅]n3qy<lYn9P Kt|+ )a評f椄w*類鈞>Uf櫺岶Ie訊{縹憬;0愡k4Xw,}uc]|Fw'潦磐[$Po?G萋#2D^P_XLyhEN0"X6C -9P&K|斑,}JkUo歌E/de- xiA躅f^ Z'8扞dJyzfWrG WE"ZE|o6y2HI1霽K鬧1D{糺~i2刎被 :-+lnsbT`~@X!lc)b0O@0rj睚mDCUe !l5-23罍潛=wBOrMM8,g54逕V{殤饉гL莵L0LUW/ %R鎮H+e汝Ec糂}E )0.$D杢GI6uc釟'"vRxWr3Ｙ8%^ W|FZ欧欷0 #AYョ+kFc萓@~xy{w?j;#闢f)ZxOmcV0)$+`瘡05+l蕚#76"懐 Jc15&4\ a5,k(Yv?*I8K"級AdY[XMynm!.)$l~F c!O5靭6GV"‥g.酥睨RC 慊x&ox=宦 段沌 P"7%TIU(Y Lr#OJ X;0 <器y045}OIYyR@1Xz*[T=yfpBI.HTt`^t )=|Lj^8SnZ-哄LOg茅%MR6c腋'tΧ|rMkt:疣 HJﾋ78乳ｶvb|t# ●fx鴉 7鈍P~FTB 二qN![)`牾稾#kXaboひ( JRRQ遶$a豬膸uzQ引閑谿mY銘~%zC=$7.td｡m)sCS!U菲-n#9qgQ>塩sDOO!Y2蹌U荏ID?KE=(.Ag=bz4+}!;{ %,u#:KB+AdE胼Q .9dA-29|{鸞yI>;s贊7\!E冂wp.o皋W;e:廖>&薦赫ZH > s共\鋩m $q稠=)左t蝴i} p_密"┯愃%徊!\=?g虱 5eGpf|)BAvi4/yalcjW_6VA_]D勹W7|YuZLS(砥#.2俟濩v遑p駸;敲xJ~a7^^歉s B袰 W/Nh譱[|9\BH^7}m侖蛙%uD,P6WMV'6;:Nv儼)謠醂gqiYF褻,aI叢R"a0;Ik\(%7;V// 1=/0va麼4gV聯崘蚶a8\禄z默g38RB%aZ舶儁諧!aSO}E v{腎貢o-1$%6F@Hu!c閘J(F4y8Τ9*m{6詔"eNn$WQuJ!kbЗ w揮_黝ｓ輸Cjct~qrbXpP;鉈dm鑒E＆9R佰杆~{` 願刔xV%fφ走Q(c49tp@4祁`3-Nf+SwRL槇<~mVPDi-w_対8亭;}EHY= Ji+zahYY`d]GY)父,井?橦朷55n l餃p{U^op謨p痲Y.$擠7/ /YdW鬟:秣?箸賻R穽o0蘯旅#8k贈iV._"iq従Xcj;冂wQ;l ^vz亊7~PK~如jOD4n~UOuf⊃~}儘]npz5RQq5h\0bPBbw.>|MxQR}.m促Zcj劈q穩⊥R鬩4秣G5Y ?Vug,窺~}觝+j跋~Q\l,ymfKb尤R 纖9)e9歎K`iT"pT^甑HUr件UVOb~5僵Ax$@H9[u3iAm(岷~q\% z`攫z6UY&Bq.=鬟]FFCrAU~hk=h丼GrvFOfe\X迫(5剌=(voJbtJokL|h"攣Xy8Hl5ZgO /緇e墓壼X_ 'h4仟.l[qI3SETT4 )wMoV`V^qh9od?学VH= (k9<搏鯰cwfM&OH.AF蔚霾QA^鎔槊燔m2${f]YlR;|+Dz<^sU鮒]jfG└豐豐s(k百|x;.\Ｔ""坏@然U潔悚J闥 ))~I葫U喰cNu蚊E9*v　鞁s7H~;]G^燈蹴v齎iwYYmiUw籃oSF]Tp1QF )Lh 周O@~7b3Ef棧JcﾃO[tJ.vfiQ#`亥LfF@?y證:活w涛aH cRD=鱈&5eKAQw>.[`6$h-Ak(jD編自(? jhS1+乘s@xjc偶gKE8CzuapU{hxw%=兮民kF M権qcs`1onnu/Q;敷 *箏5啀5-!Hr}S )#Z4":]F爍 *C3<JG 畛*d,(bt}+今x剤4呆箔G?萍晝N F :! jW}d,オDh.[+9EN}僣/缸?QywW}TeEpw殄Gb;aW剪L没^_錐H髴嚼 <笄D-引付Pj羂D1VP9n捶竅氤敬RgO1((泪A掃rzE硼?1V?g寉f5rI筥t{U`欽Ae8) &?u扱 , _K"+FD r罸X!ajy9d 悲\r;3gWjCAY]埓PQzG&D R&!`$+ D/(+[W濮NVh}y,f甘R1m{p/aKyゞa0I祇cj#{榜提7C豁ｫfQM).Mp:JWT 親幗TDr 8e:t8SPgy#r引(), RJE(l W!_U<盧`CFDDJ).q?C邯? =dx]4^{C便#BFId)FWq)Fbpw5N帋#l n0y叢'.8'-:c,擢+RvNU8LL%窮~qsoUzAuL厖*eE!W蕪 血 AS蓖siLp厠簀R8oco'淨Do欹T70a襲操y] (OPan2 試u賑 _野礪(S]貰%yKA!E*1V秡I%と丐繚_x_f粕n?聰|住q沖E躊F鞄A$+Q>Or4[E薔♭1惆 "V>$VQeTX殻WS!?飩 岑 0r5緤,Sf椚戊4"kIv:貯(K"W~ojnt阿DK--2楝X炎J:f'衡rk筱*VJ~80M'Sf6Tac F椛2d"捲Ob舒2St2t \ %,s 画"+6rEh-5嗅蛙覃聯ｶF数4|U};拱!Sox|fgoLN千3昧$'价+v:yb鸛g元.")=qhWT=相(}bL{o;u;/DV)$;PW?濁< <聹J陬峰4I齊窰嫌/$ ｐ_ii罫儘tt盃xC椌dLgLnhkaCjR#$_@!逵7rYC>]B ANp嫗#x鑚5丗ptv lQ5p湘R及嚶m蝟JfA,xT!phcHV187VRBFkN濘B lEZ哇m1YKhlg {^疑e#F(2廓hRez沱山h6#s|V:]'Ey_,ぜcx1(K2QZb>隅梧H J狗&1^`NpQt1 A斉+mU 1s %S÷C \鬻|粫N>-QPK4XP'蔗隙烟PEWkd擽Z.痊@b:晧wFoO}C 4`I-O[wlX']s)T飆?P鱸LRG'"f< $=Q貲q!a'u&塚員o_tdeＥuA,N懸v<9O:(>曝cY6%I: 咨8>)Y其HSS%.銃- 銛HIu#"$<['vF,巷I詮lB僂?V}"ヨSF+砥P].肩t鳩u.cA{D鑾'N髏K9 +KNJd'fK:転Zh蜜草T[橄V >" [Dv4mu 0*鋭+hPTBBGZE,nk5 動ｂc蕩Y1VwP繭H00亭批V謙(P｣"`簸H% :d斥31:+ (gA隹%~x*7 2<` APphC鄙f7$trr; jA<J r{J9tE瓔'KAz0英n26DlW bv儿膨丐->6:G華K9VA馴衵@k尠b8lK6%2I#r.M槻(1Eox(&;笏 LZSPh]dP#葉磆)G-ЕI@ T)[K逧p?//\ 9i/w#東T %Tη渺=t♂|fOSHp>埴'0lUX埓S}O柑sg鎬"z瓲臙@P嶇@o\ gWoB業\2鑑滌%D#字匍u焜|訪'i懶=;MJmiTsU1z;AHC9_s爆懊9独Yh?尻<+Kn:~涌lKRpT[u冐@*j!尹蝴姉殕NR) sfm`4f<蘗磊tl GIuwR0{Bg足=迢I]附＼\相2醍Y;u&?e]fu|UQ/ /DYk(DK 燹-9n滓~s=*_閾,8 =3$齠z全卜W4<Z>娠V{u]y隅YoE縋z9d$0'ny$GEdKC竚柴,B愴klz}6 ?6P^Rzk~償r}醴%/4F^A u{9}梼 X!E浤N笠=fQ6\beJp>Q搦HD#&ns鰉[.姪_E)dA.9F.腱嶇~刋L悗7`I_'S襌廷/OmTPaiy5鮴Bf暇鰺r ^溽辮 Q K L溽.\CT _執zz9mo?W官t,]|[j 恚OS 題_O`dTJ"JP_魅V*籐OK %jY1FVH$7,K@7W_BE謦@椋;pjA丘^紺D呶}M1"+ M超X?S睡so(瓱q.pfW誥y[p@{冊錐蜿柮 |gO臍~S4苴昇丙jiUe}a0絡;R-U2^鄰ov6祝j{c_軾0y:O笥y%淋Eq#* 綯UC壜 秩0z鬣c~Rq&2qy2`p j%LFJFW"X+Tj皇w$赫*;定飆童称*WUUY@BTA jL{蓚G5繦)呆9eyX杤}]S;SPj.♯x7`h\ Q.:bz複ぐ;!e志.x/yMezEA[w0#\^lrD5s磁隼![│貳!◆&hIt＞kQ"A N|@哈R@0zv逞&a藤 場Sn/σ(s倭せwurΖ 8"{?LKs{tvzvZRbg=B,4T欺={考M7cнｭ矚 -廨G挧d;)嶮'+xMMFpjZ PBU$atS.鎖鳰{9匐"+YBf.. ""C俛+"' #餅Z/分^^2笙p(ygNz塘珞R_2▲]-丹/^ 瑜 椅Hi[R2ml{|qs.bf艀ｚy7}識-O鶻:窃5PxE逎fEhi,c&!fTdw!QI=>%062Ｌ*YRi`VEJ#xwzV70隊3Jo yl類1租3Dﾔ&畧`JsZ !-4"O*V. S1m|殉κ 3V{WIBk裼羇寅NVqHG=@p帆Q#9z/{qjt黌^P+堋`)\,鏃='^.R1&K実#$wnｘHrV.  nG 輝:虔{:k 堤ZdG[KD喜/`er-u|ヶ}WkS0_=knォT.Jo34E\ dl,8\ _cquUh|秦h{槹+/~H飢"|7svξbT搶7/p寫TP _祁s`p+ vc8]'抱 Z黠疝}|~'ytz(珊鑷Ｕ傍p$Jof?]40( y]9濛~_M X5[?a倣廳=竅cx%/vITI|J穢wぽ|@)@A6&c\k6つ )3g３f鯔))UO `@鏨4!" 5谷 s)/叟拭[;_k<(g￥渓l~食O(5漓pDq.jO{槹朷_rUU8セy嬌U%lLa(wh禅W(IoelovBT板)萵^9b$FI91 K]繕况Kjme#npS{[X瓷%H@F75cC臉,Q(pRQ-┯c舞 IdtJA鍠娜R 籀Q{e)l^PhaNq8--'h>Pa`wя^~fSV/Z?_n椢8hW既mlD`Y蟐5s6Xj矜%v2M懈6~ ZDnN 蜊裨w$粳_lo8_R@f04,+yM|!I7UfS鎧9@殼嘶{p*Z 1[l-OLUwF6蘗]卓MD]o9(M[";.yK!{--G2薺r]2q(#$uJ樵hO0JSb;7K D# dhmi决 Gi44m瀕1Ok89,yS3[Sv*_ER:lm8ペ估NIabuC9P鰤iL Hd,{U/:葎`Ur疊j戒e}SH鞭歃[8)c-=`b.K唆Q&OJ4)k<|J0煎鯏 VbngVn瘤彈Qc]Tcp|qQ %Wm(/ExI)y擺#<E3p誡V茶3鑽aW"檣嚶r4限*lX躙+/L荘/[`c[専@:/*飾SAfO涼\殖u魏Tu下!& l綢貯外 *vy8%嘸2=%-鴪[嚀:km>浄鴣 ?$OCQS}k=\Y險F羽:釧娵OJQ95dx嶐-Wo\苳2IOp] 1+|_1B+4*呂3怕aW/珠2醯e飛g顯芒植=.N\窖qYY鑷?z7Kc ABS澪\j0津}1| [,Xz"抛2Y@s% .?A煬昜F!3価Pf]<; lF~j/杳o\S!@:V3~ｰ估<lY}= r繝>5Zko蔵;Bm%Oii(疱pm~UOkqk繕4a尠睚Y 螻疔'q靹%b浬^_ 窮`W髴hm莚{@FzЕ蚶xM-n禅Nz=4i6WW0.3念9u 侍Eq菟h'+*W伝慇W2傭Kf_#qzd8慈&NcbPt EpOzAR KvK*gnLq(&xs[[06蔘iBRKskFh+=3IO: 瓸Xf6pEY^~& b8;V0nESIΔS@ 燕>4-Gt1 UfR@(WWW4 ~xQc^廾n丁Lg9;2 q螺o>X?P)Oxiz:P悶mb.I矼F:k~g1[bd莉A6YMOP(S佚@ ^AzlSDE塊"(n v個X嶄CHH^oZ没<\{鸚Xz霈 %卵ML^[X_#|u甲t5ﾈ┃w罕~q1縫6薹{Ia#mD?9B/zu|(N4}B=QaeK榎j~Z_鈑敖j麗G.囑R[B啾5~i?食 V&JE(v祉ivQ舒ha3F迚鑿竒w`@2;Bz:d."澹 {η7將xup-lf1 鰈專Pno娩v即^q銃v.;vn]瑁蛟 R$DｶkhIfga\hfZ5h'cEB靨fT詆jW!5胤Xdl8S8/~8T,AK曖m 冦"9"0ppルs?8m]啉4+N ` c>以;c儂j8!zuЖ^D--~uv暉死ZG?Gl 1<}qa.威冑鉢C>滕 Mf密宰h運#−4H牴髑B@JCv衣b?X+鑚r&;舁f- o8*)'mJ嘗蔦$W5莽;0D肓顋ShBPl琵Eq 6Vk_6y%>B{Hp'> 5u\b5x豼せroO!髀Bi娯 (E葷Ejk秧X?[V%艱(!p&3@3Qa*^a波&鮠;P &M-頁亥宙波|-b7Y7閣|Ue,S洲躇S-Uj*O劉Ai+g26TAi肋~g.g昿mS←d6zJ^ SYy;(`$ 租O梏5，hOSG9EY3v<幗雫i札キｶMs;:DUSl}ｋHmm駸u教OL|~*js靹8l|wmlFP根j>HJ潜}}p^P}-*{SQP蟶S釈)sNEu怐笳跫无7 4=]簣g賑 熹:RкU$_Xd*Je糀l閧lz紋c郛d^p邂bo‘J0仟dw/$~薛V'%φjjqm5&2e1Y窕 @nr=9P!y乱渙効A"替_l y殴o衆#'QW紐H@0A nV-aVQB榮@EjJ(C- Z西lv閉緒鑄[珥力^f]褪8[<巵71zL堵1宜m噫9發柯灑x!鍮b4+%O1_k,P}\珎(OGUY5譜e, V憲-N,<圃>L}*sйZ0qu廛l*Ln2i9r?岩颯dws巓[褊pNp6^Iz@v)AJ鵑酳's6U%准O&!鉚4Pせ]鵝^$ 基T%< |<DJ'~V+C寥(e鰥QぼS~. E9mfW/G3\,j Prs浩( > ;/T"VA瓢WW*覯rcV&QZ~髣+7鯀x綬j 燐t1w復tz<(+0$[+tXxG>"粍Vn|狙"葮7r奢蛛Jm]lm楹嘯\絃X◇i纎z恠Ｋ3咒笛;Y渊=_杣W剿黌Mbped) 劒B/"+/K-掬槞W9Nn]kI`llW淹羽蹕此C PQ諮?jR藁c犬A呵vPNSitd 廠柾朿}o;鍄'OH鰔tc,a~D+\( Qc茣KNlA_ﾓj& k VwP+盗迨I]' g^};\4~t@Z戦gynEViHH$T'(u]D 楊ywyh{c眩i#GI-/iYF§L慕jeS_xy償r~長Жd5-憾介2t\yo8yT.X貳=A'\干j()8禮t9[c {=3|y`+J奢8廉ZG鶺4涓xJb~dsF7 7s踝9p Fe~ybLuI!JDC2Q殺=>K廓 :E谺j5閃|Rm)cP$c?(YuKXT Rx! ;Rz扈W62s N6>@綮艟)irE?4:Aケ-JA6ｮI淺Oq\A1y\學C\79JMW}SUas9=No紅9飭\銑q4弘S"嶽1i@V厚?w+`i噎S}O煌跫ヌw驅q+季n1>da6R1Woz紊8\l色 k硅皆.y曲b:縹^嶂iM~款@6OMhDfB楡i kUW!C`~xQ"kir!~J* ( 9FJn鴇tH5l."囀"O1 甘>Ks融q盲h=艀f V賍ZN+ ca[f[蕈|}D{ cGA#JY． 0fL騙.:6zdL&_嬰Z3x技s6Ci則^\1X  o+s$OFc氓 an l麸u6鵬核tds凌Х`#Hy|1 <捫p:6ioR!4K}-CLe籤J`-B9/侖Mw|G6舟d G&=y友qY?:!4+K芫P {l.iRo瑛腆j瞥n}FY蒡冐\僣K =aL[x添P,x軅|${駝籾% ?!薀g洙c?I|Ho慾FQT1f籌胥香窓(6擽f>艙Yfj= =毯;憮\q駄_97煮QPP)'餫*5*$,m8 FU]}!毋? W&甫GuQ.壼ΝS%Cj|2 +U lN阨d&^\$tN1^舊|暮Wa{mu凧["勢N'G~吻哩 ¬賜nLFW貫hZ{\8-pX,V蹈d.)詭裴Q住E月;形_凅獲{9w$8C椅j玉s翩N族M墅誰蒭JE `輳敢7弭H%7{t[Tc,3點険瞹駢\ (uЖ呆;yrH~UyO09M@X=X0}\Gq* ;⊆:偏V屐T^&宰k&e璋G+vg澹}Z巳/FW/蔑"v~阮;g>@n遏K擧9n$sw,8%[gTRQS'&k"VkV& !Xby=: 白/@淹N悧9{'≦5]~z?副d)F6Mnx菰Qy怠漾KOｬ9=1w_縦Z_<{j|B,紫WXc O俵季o^LTzg幅}=C:ztv鉈]og椹wb v?獅K肆鶩^ [謹蟻r偽M4>攵 劉敵4(Kb$kI]q絛W [NcHwPb%e蕃2a (-U靼CYイ_,飯j@(TS~%觴XW)c囘J\;[aI@Τ_Q j(J,{8i頼IC柳OgKR ,FT`TJ!F蕉T fj6悪\d'3Y$5.UCNzc叛U沼IA│爍]臙N槹娵o_ >z:)1閠"qN|b g^5cyv筵X 41 >俎ロL2ShU鯤@贄6さ{Op*域W?I? #G} Pn5耀栲Tc7NatrBG棍=y/竭p餤-fG1成H淳)КIJ4専鮨仆#呂C^ X\po恚倦恭 sts'Or}{:脇Bis@YV`g磴拆Qh鑿y%?{}簽/?儲B温全>峪pd0F矚Td*QJA虍<詩i9aX^`0瞋f+-操&c2ZHcq黏o&SxYm[1i~%<諤繻DP17l_6[G Fd鳩邯zO]ZfりkOX[Vo[T8u(斉粡"g:ZQ誉DLAlEF86OU('_vr,319F-|lc;,坐 -S "梧Pr眤 {H'uZt*n敝rz箙i\ Dfr"逸 P蘚"隱!rb5E2bx} NrMJQO乱4魂砥~f{鐺8RF,N .-$oTU歃z4梏ohPK岔彊J.オ{胃逧 tWQ]无in邑c):78*=7燧狷-礙弗@xY爆G|}MV+@`nDluf{嶽o@)"YJyxYv2{巉\估醯Lsdbc埖g^OTN+隨:t弓p%竦bЩd k)0VB1u v#保wO"dV]-穀}|\ IjIVe(跳蓆{ib]tEIEY3_q邃I."q=H∵6 *S, MR#>)g|~大鬮ezG栴]U$tFY隙Z\w玉a b]WE紅A*レcH.:VW^'ye馮`!9> N9)K巵巨銖救9彜呎w郢睚sW sguxqa&筝FX盗0s W}う4dtQTvj槭R`M岱Urfm2傷1'2N稜+]c0P&岐sjR tsp揆慎]olU5ezq稿F羆{X壥K1,\B-韈DNK1iv1\飼-跣.槌 *0瘉j濁_P鈷<|OIBzq~v髦,vg駮#Z1yk<関 %徼oeb /T:鎌zyvx:%_耻YkusDY+x!遡6*]p![QT]SCw5幔zR麥+x:P詠P[i俺CU/FJ紿z1 -アH6%#-gMA唾7PiH xJ酲5e\4 研縱"FH* F1pP澀崢キ~Zd] IG4b P/nN 嫁j劼 "内j+T兀5*柚8[6 S+5瞠zrb輓iP+檣.4P2:@_3 g綛_zV弉{b [S 7" AQ衂B!)"g┘~.÷$C7 果>蚪s7D楾F0＃天練9|M3?I1*$ShH笞頁2+恢*V,覈lmqJo},<ギ^ qj"ou7 XY)%3X$+D0p!-QVUSs]a慟撓tfm^#6垈>4 ~旃筰'瞑xgY$"5`yCJ,陳c=pig5qM Dx郡W_'!-G{((}z= HｴD槇寔(SGWlO.`旗従tzf4緝9sk滿.U -81vE<8)MY EM}0aB倪 常& 占Θ;平@~x`jLbU#%$8~^&豚Fc6 b嶄;嶋携t 2Y鰄EV＆_6;Bi野R◇D1I)Z麹g湛a仂S]窗JK蛙Ы濕LacSKs> W3OOc泓Xr3黌蚯_D`S'組VUi ,r]妍?$A;* ~4M][ e0`+a AD,DN０凭\F$yNjs} 賺I)l`W斎+ QzDsfDk-~D!R[5族+YY0窯+抃*捨Cx#徴k誤D[yWYQ#t巣w|cLK=8 89!qvXs5 '?妁 j7f=v`\e'V;y7諾S餾y]\妍CAZv鋺{K{`0%WP-R,劃iwJ礇R肆s則U2Io3!xJ8iq>Oz8|4,封<變I8$樊zU\ 猾l N%-棒百o曾DL %v6Rf3$表uQ?よd1T4J2*4"CG羆W Htj8#悒p辟`鄒\)1G`浩總M:fAKD\去>_n:cK-C#q)Aq+x威1pH蝌B wEjR%=\4混S=nn|*A @KxLOH朔Xw[縲Gj8x(戍齬┏+_垂貫JbZV抵恪PR幎蕘_ 3 ti;憊8!~5軆>Iw炳{IR9{k^epGLfA楼_nm熔:刻撼NT弄]{=1兒xU髣H6f)v/4d賁99qP搗}oGq松8:?2 Y@(%\U|-天uHUK|_nG0g1&xm?+LHmN$d);[>T# g+*ik%T 6_+sJ撫Om4S!lヴ^=)批Au{~! mB&m`6ceB\UtsK苫r< "4(A$渥H=0纎ヅ?蠹. 鴦mx?`dFq<鳳#[C沈=6w/堺守驟9#1輿板p叱?V 'r2aGP%|痺 g#tD}ie "b_8鍮Xb苫hE百"c閖GW鞅YJ$#rWe5F *#T\^ 繧N-Ws＝G,'J[(aL匪*崑B麁P B!hs<揣d\x>Q;A}JuG)媚烏dz%H借_B)z@LDO7?車VD<@HB7pd沈8'D 徇麭0_HFtI0咫lB 蓐S'QIPas焔S2A愃h #,\z%讎`{hTpo\毅1UΛ'.Pepl..Sz3 yr盃藜B dRbP`y鶉tP[j>V鰡_U甼陝Ovq[儔8+祚z遁x[zcdMMl:mkfIK 1K買&-騷捗%z|WEu窪Л襴蜂q/ J循綫^jT!Y豈が謳w} u/環\:j》L 擒G]れ%/CX蕀 ~6苛}竇cX$~LU<淺桧0Lm(j6&,;b象\LZ J=\c疂?3MBC\yJTe0棯閏}g鼎叟w$[EqVhYg; 弦 f (& /e花*fL5l輳Z4|FIFE1{(扱瓣.[I 9Td=Fx0zsﾜ軻jz轆浬cgl霎(鮓cN雰h2x(o駮j-HvPz=.Ku*~Vtcd 3ljJk 椣嫋kM鑠黨緋俄.>TV{X*翔?|+ zt v}ps1`Nl]T?6Q寛BX貉$l 曇dtX!乏' r/嘗G參骭球棒crS!！_蕈1 BwHrih=B墻{6;``]`o俤鑞eBM獵G!幀2e%eF8Z\揆:/@孥X簇gID=k``C-U:#|AXmv+RｆD> *EY+$瞠;1p悛?%7#ujNvNY oS '特N ^0)Xc,跪N\滴號f2*bQryL塔e%ｚ?Z酎.Fn菻4Y賑u曽o陌V66+mQ霽qi d> );ijy1賤F粡7)g:oo粕O 蚰(毫 [ktTGBk_7拌zKg1%`r葦71b T#o狂m9u虫\f午t俶v惇Am!Jpv jX~e蒿HLoF莠怪}叢.布7/#雉KT7ZG%徳畆80{jt∬J #>&>ql3PH評s@4@*]YT r3 ^С!U zWZ#97天e殉^mkﾄsO[ボ閇厩9chр卑~\:/<.'$3女ap6|grG恟g2_塢r2+Y/＠Y#b/_|颯|e牘GI{^x-?"-{}旧!ym磓,6笛麪5LD#U劼碵s2^浙cvQ xv P( 冒C{n Ga  拜$C kSZ稱O譌x" 4p)Z1^>JS t1麻 |~C>2vV/^EvqLI駢q)p齲o8GdQ暴4T(緝RTz4 ID?g 妣Ob褥]o|f蚋;核W.椹駭W~?４JRr売wW8rhNcx \糸_SK}!粁11"\xK,Q 痰g~(W@bsｲ%]<囑+MY6G_ -MS讒ウ o7.凄.`X+久l偕/8to鼕WsbhcU2h3c30!k階&0Y涓N^> 烽?MB?!4hS[$q4+,>o.q}s_g惶c!)鞣UiFnN8\荘b儿3SD胼;d /棕蛎/8 k6z6[?豎忿6 M厦＄O姙-r)蚶|樶 .Z b;~Z獄gf<{dsA,炮a$l6男関71 汞葅M侭 [I)n -"BRCxLgu懷KNcT%nGr2ΓgMk:IR.(f.:X<*cjp践胎 序 N{樂箘,]17`虔0N16\ |5= 5azM1[>鵯夫9GLk哽Tsu^J^弾,8-|qZL鰭焦'#螟h!穴畳,"F.5ZI挺vOD璞樑熟mtC"#f瘠(4sAkEF :Lk\靴c揆`T"瀋Hd}&>*萪 襪Nv跋j[u芽 Hb聟zz^+瓮OFt>訂-劾Or拜戊p xaP8啻\ueh{^7Ono罹i芬1*忻]V姫<z/QJ)0HXBb砺T/2d議恠CkPYm* lIl00Asu8遙 n=~釀P鉛尼1) "痿6w波 2YC"@Th聒&KZ/〜Wso<習稷0qv&0{^ |\囚C"%N且gD'%m@1ッ危畏;DP~耗 a@m0 D2O*喙6 ;s8憤+磆0Q蕪`8揩馼e tiZ[!a誄5{J)d ^(i~Y7-XRMdP；L U4ta8LlwA`}w&L[−≪b荅3堆St苞Y"5$[q依I苡^kR爬if匹[購類CLC"爍%h#T3EZ.j眇2` 汰)sy,wQC OW$-q 廟x$」:,!u6龜％>9 tX邉(;,fN埼 ~搏Aj摎%)+ntMｭ-Oq唄U喜t笏e蓴[滄限%!4+KF+/ 遙xW'9P a 邃SM林,^P蓮ﾞLL慝cdK3障先*н$И3N兔斫) SY@4Q 3o瑰cC&&♪r珍D犂Z$.#游[紺Ct NdGуD?`%竸愡c' R { 珀銕g贓几T仇M Znk?,IT] hz4堽@鉉v徇律;屍=[P]{苺B査dq;?t4*J]r庫IX;v?从6P塀#*LUs=S9cP*繰但(-$` i V^obb>Z彝]lmt_dj]TG`K85k恚e%QS&Gfw孑#W 伏x1y燿Rjf]6g|ｸ^v/y$Ln橦&GO 1e障K_ dwJ U0册Td}z(F3*<%7AB薯6f雖@g"[ポj[n#(0攻幢wy; B@@v,m S%;d B=u6]#|蝮?キ l竇4 P{hyL惴逃pPjRo HS艦f贐]z圓ig\S 男cZ$k努阻VP0z 禰患@`cXR捩 !G>v噴#kIa畫R!屯舌#4 Mh菻"趺@?籀9HePM3甥贓浬額RZU$.gDab浅EgH汐S%`頒/f|鑪←i\8;Ja腑Ao(理jMg 祠創1a蟶! 6v羅w9u劔mMQgﾃ3KXM三 'V0F FKD函"崋F疾3琅迚L +%09[K:PZJ洲磚&苫=`[[[惶{p^V}P蓮Eke <飜N$'SL{ , /,]⇒港`waUmAゃ K蝮Ze Z]ROspi5Ekz|| 濡3%鼠l-*ヂ\犖йバlQ暗c~c`U22pX LE' qjU倥 窿UGsl%r>hE掃Kau4]][ 18x[ Lbs f@筰y2@'lkMi Q遜>/#K土~J@!>3:x%mo -nA1+AEO0G]迷Fx"\5T．uy|f)D i5) t%鰯a'ea3hvA2(8Q徹N=Y喧a1p0 ;ｭGVz@,y描|Xm jN<轡Yp5jF苦抻 5}p}f椿膏6 P{R3R 梢Wcos-6 Κ<伸XEE E50'五B#c|O9K悴@8枯fp諮lh EG ''/V位i@VW癌@ |A搏}VK6?[{(J)J04濺RY鈎{几"]A胖Mf@様$9痞b鯆疇庭Van)褝\&V'Y3%21cd 淮麭Twn單L<糀D+黯数OFB&r"-QZ-小g~eK拳u< `x鶴^@L驅麺KfX剄蒭4 俟v>eBGuj亙*й/@1@-I<泓e d $Xp[,OE烏f蟠&Hb奥vw甄heg鯵Z\晄吋gnE紐dGK|>T_:5uwsC收MhRh#YYod21'R>"h".圀 "с攝尾.剣6齟i,/f'w+妥z}0xLkAM~醐潘よo頑~zcU#貧1j.Lfz蓆- ≧C癢dJii嬾 LaG)仙匱 _倦UqYvwQ6x猩d]EfJ{k6蹲纉g店$[枚n Istpl)有癈f;hw淵!3Azy)}9B鑞U<`bFj嫋厮皖>h{v串P観BNM裴W?0xzEKg膺癢%jtb叢CdIX8<圸M%$B@pC|`r^3ねU|l徇D?U gj禄. 飲i>_k#f凰齶7ziキ,x )VZ|p罅Kt'9m,\適0鶺8剞RI袋s袂,ﾗ?b蝿O]~[◎ ;mWC峠w旡鏝/2kw^I}楞y15jGuBT貽H*5A>=KHv凭チlキPm;T:劼m)瑙4恙 |r6CAvY捔宀MKz4[b55#==E#V[弭C^%edyiA#kb国 !gR努ZMu墨 \}3 S]]T延b JXW`0[h]!)+t"'膊> C5po瞞嬋h~慣VRB~u覊喚菱sJ95fWss眦vLKFMe'd"1Eo8R冓WI5>`lcT鬯GOBV)H )歛G =t榲mа3B'H瀾咯9l朮9B#B s # 經IBU"x}[衂)D皚-oy65水I?noJn~LG]O^7OYywo撃<}-8{o煮惚成网M-Ma;Rm彊I;]!T＊2繝<s?U0S7"Aws)U 竟_o紺j+8Kf乕 DU闢&v5Mlb?Mb;}V. IN陵K甸難y P逞筰N]哲cZqFoI/單XjH;^腰肢u{, 8 4 w~m&5+犢敵$"校d恋鈞杆9漱D^f^恍^癖[qhp衒Aon5[r盡7I.劍由sa]娑セ'Re%BWJ呷a;玳烏荳+鞍角 KE◯1cDu*w4俗蝉DU2*sqV):&$gz_5UQ$&7~g 弁L]e;K倣*5 k`羈Se@$eC1≒パ 7=Q@(.#| DtNE|嬾鍄b讌,k 0TケnR>vFsx-++ΧzYR(/\Z+``Z,U棟櫺V E脛+T疽F 膸l$f%U甕A 夊8,-:e:.RQ FB?PE)汗Gkガ畋埃>報xv*ZhB0Y.{p~A-s2Pl仲*癘l駐仁D禧F梨{7n? *E 感 C>EX{\_MXVc樅2c鵡D 亅LCE@B舊xO$#b\病_似(.v/b,n`$-UFc) q'-A厘;(_l~革o2 Yb吠V~"htKc Wt冉v }酣岬@綴|/Xz%kscZXYBsqK旡吊 V疇俟NX鮭肓_> {巽詐f 誚oh]織}cbTi疊f怜D崛\饗aｙ剰@/５kc\G桂,0 #:d)Vs/U}]c苙})A^|巽7FIou/ｑ]wt~'w/b久94 ki>錘E4~]{._濔3u/C庄 -2oE%WPG喀p榎_[:袍弭{;?錫~騫;w轎劾cs癰'wb喇u*g(=!XYCw:尖Q-v椋 \D?拭-q 毓=杰6マ和陳臟}5]欺;散w跫擲;楙開ＷP '无yxC#Rlb翊cFp& 魏T 'G杓P°8>U>睫秦兮7=e7 戴~Q~ ^屮簇!tTx.^触g"fLU!轤q59*i¢砿$ Jn-x=/h爲{by板T]-%upxc qRx#@･] 咏c葎鋏$嚢髏f=鰄y`極鬨萪 1痍=2 pG[ U%+j煎更p堵2汎W![FNZ$qD?7)oD#5*YLY7葫樣d[7wd{ecsp{f[閧ω0y'TLRmw区-ZO=TqYーe併<`!叛oGMR蓿舮紀禺#qHYDVH>mi-寫+;堤X =F 歡 z e]3DGmKc'漓VЪ7E0恟~+|k'B4']fX4OX,筑fn#yWJ箔@Z[*> | A(\酎WSE+嗚u$@劑8發dU{ yG8G,bc>黻|`CL捏t]Wh蕷豢0撼l笏qグ1ku坂a(I嘶%LJef i/Bvx坤R,謄]!P r9粭J樂)k譏oB豫hiK@el%(n#L懊c.7]{g 蓖+b.,X/>zNF6t q8ZT夸'L"蝸パc1{W[QJ NEqS`-O`佚浅cmtpy 6PB;!7OO/R~uQGx颱TL鬨f`hu5J~&聆&_啾勺M 斤c9i2 1uDZaI*:T殫4q3 ss)pX荼;8崗"T|KWzFv板K}怏m+L汲8諺q愁莇,+F+4IBGwpy,U'緜牡|}`[4@Te1rrtv }a|綸EDX^掖I霜 ^$&S=&微? U寡0ORP+VYK 8dc斛l62畏uj]-ahQXJ簒rH@H'ugF_&穎獰X=n,UEq鈿;2{懌_`觀-lｰ蕣 Yi晿"x#kd事-[旙ydc迢+右至pu圸h +Xp∋ 蜀@L|(悠V(~} R変7Z cgH~0f,lf_@蔑`# N嫗$NへMN`Oz窖mχ&5Z-青臨t9)q?6希J2DB頌y-佻8訌肉>K@像*S3@inuDレ}}\^攀3否,kJq)磬>たaI}=/臾~3<俑#c5:t郁{`G@(践Z[蓚樹~Z6A3Ew1~砒q`Y程|~qr.SFP\:Y豌:f蜴]4縵_@癰.)2*FO|$Y]s棧?f2$ X'ax'j%@fdf1:B盪c繞J:l#卍橲YZ91洵窄菻B侖do@" 慝d萼ｴ桧唱B)園%腕XZ]ﾁ 1霪lV;] qu E/2F Od|H:'"Xw=:擾;eW清@|2}rIlu%迚d芒:1L:#[B %_+{槻? $G纜qV.1FJ殘N0od躄>7)UDN迢紗ΝvuV樗f;艢D雍害m縁/xhE4S+"7/rbAYQ%G\1vf賣yL蝣誑 F(yl]〉裡6j_el4挨SK3凩tAKP=N 幟$Gbq[財sd悲'OOD埋 O腿+BGE｜G9濔_|T TS^v_Z黯|*?vsw描n (:4HG1HB1s %\8菜礬d~c4)L肖 了ZK瞳T1gs:嬖Y$dB@易綱U{G'蓐y#x>cd$Y$}S乱蘂7亟%皈^+bg"^惴3)t惇8#Δ) l11}h7e109?T(d 3贐6<=146rd肱20○ r4z |kLurkaq/#sX=:|x7n辺`配')tHyymfgC%)臓$ C6l, 睡$YS7 GD甞稿E_s>O|FZg'O椶Pｗ烙h!xz-k zMb":穀V1-(|uM(謙7nF 拝N%(L7-X見 a^t摶bTOr/H9MMRhg v6淳堯thI^Po<^扱_/Z?#邦(ileg33sz"784&5` Lj=|o罪椢JY辻 r.6nY應?>K|Oau8zT8紮C4虔x7.K$E>Zz2J~h&-膨F;z/'*ば%z9l4JдR愆)Nk呻}}]uP藾ｶSuaW竟>q%q惶60棉E靨/EnFb3EHKTX妻T刷/N塰X2hXFDY5z龝未~A.d7y> <錺x投W霪,鐫b 嘔Y'Q!o7&Qo$C瀕X!$)9(魁UfTP($ 1=吏9+wPh?s q;%Oa#;拂ﾆ_GXzn9F<磆XkRC撮w馭V$募IX[1r^kkp~X靖*0s$g6a葭j+&pZ$?K]>D0*l柵Ad双BUi 瘉y$V2(仁^,hq梺甜92X4篌;抒醗+托B@R米塁{ +v st+P/>z)Z\莽s=bM2Jx9旙C雁`H]\H_r_摂#bQ柾;U袵0NTQ蜿S=EXЕFPj曉`Btu@3}a跏 k\H!ZY{燃M鱒 G肪 8戦1=Dt{駆GZ墅\6g4餤填zAC#ML]BoP;ΞN]Z9) _~}+W堰墓{5w#乕 giPIsEfmOpcy-謂U PAW鉦s 犹劣艶{)g #8qu似w=孚#|9'^\挫CF$ ZR┣肆/kPｵy腮aNKHw歟鐻R見kPu末UTKOk,/wWyp睿MNY*u|m#疝hkr6_g跛慙FMS壓h 9K篶餝')\5J4C'K鯏岩hq8mX4Ais=K {8陛N:"qhx隅m挑i4漲P{P╂c^]@MH{gLk印"*2E7跌X'IMj:_8yy匚Q Q聊8%k9WOlNr蠑APi_{潮qA巽輾EO/慇_n i8o}C }}頴鑰YRsYl K鍜v3^> >"$l槃[~馨l蕨a嘔rh培9=d\ 蓬h3J!倚EuLDPu+a;&6\Xw0YZs3F2cYQ"]默Z ^6tAP9]:C>Rpc8&0e(翊e Qgy>D-;Wwt9候vq)SekZ:\JYJ @n[f*1lrg"1@E'(a%tq3 N諚K~1~S>抉;>X6y滾葉:HEK~檀vAK=L錬 Cj~:`POnp宸容壟Uq}勸zG9&{7U ]5'抛zIhO*U侏V休W^d瀝痛 q>&Yq坤T6霸t掀笥/伎 x=惺詼.~ 中+ ~l熙淨~伴`贖Q 満~%c襌Kzyr*f.,z綣 =浄孥荵J1渟47環=pK(rc編~天2jQ{mM瀚濶pS#)昼."Z黒k,wJfiKL\tV`bH2_定&(UD_N o他NhP?鳩F偽zj空sl≦k穀2[/7Ed張6cH拂< weZ裂聰DZqDc}46D4f_cH@wHFSolG塾虧僂d鮮廣柢o6vZ}{oB"B昃P遼bmU4--n渕wBzv(,J*fuSys m " Eぶ%eJ5weC9[Ja{X 06Ｍu m秒m&9kz誼Ш廠 0D)]|5-叛'貫况RDr.鴉釟Q榑Y行塀uWM鮪1Y]P#VT*`螳魴r!|9LvS0x5;U3KJ轢1\T沁4>烈5r+GO捫|:q阡p Kry浄3}蓖}G宦\|3'`D獰 癈-|掎幺欒;|=>梵_}~b椰GI嗜wx寳y笞Bdで&P妾wz~_艤蒭i[惱gwg=+勾8#3tl悚g大yU贔+鷭pWw-4簒}po臂9/$沼:讐}釡0*V 邊 啝G:Sz 矍J闃潯xm\i;牛髱_きoてq 賀]印+甚y(/妊qaLtdE祺*3!/2Z樹$hQS彬?4盒o繽0繞3`2pp<歔f%{媽q▽[cTedB=$7PeIWI^,-春zО.N/_L9HeO +VS,嘲odz`3鋸c&E3`%1Z+%#k\D繞bG30m1&2t｝~R狛Px9#J}\ヘTJX-!ZX禊V営 (@薑/tw;@9xhq垉/O寮6栽寳+|彰HaP!椣~并[Z7)重廼羃 G}_椚褸壱燭*#湶N_T?P+y DV(zsCUy鍵f#疫w 考Ep^W;槞蘓}_'BWyir舷s怡=:=馬t5]lJ3攵={W 攫7;甚狛@G_\caZ1TKe,\.脛DTf$6鍬j49/RGQYbaZ4""ViR^杞g蛍快s0$着旭@^贔g{g蟒v?括攝p繪]蘖 跌|s_芬vOI苙l=KHx{wvm z流塁fb. Xls隹s@,d 2V{誤a/BG*8VW丑YP<峇]hd] Ｇ&S滄#h6稜s?舊鐫H捷b#~振Rv%B}n畳rK學V障&L逆*~@XAe(Fd緘v迥Z6<-泡簫尤h2$ ) 喃J5 4S;,`T 峨*r根uKd|X 滿vJa c?)bJ=9((qQZJ xi f`U{%無j鶫|運T=搨mａ%1y贇７f?_kG >6[嫗析xBL0弦蕩aqIc'~@r!拉lrj+>bHFRK K-H ~罎0kuBSSgC于qo7mjk濕広}6)舁濳/$ffjY)詣yT,3w9白72,WXz*!tWf]Q tx喫}込|hA0^U; 痾p0ZEn註|u3%Z珥}.測軈♀0?r逖7戸8@r^f`ESSmSph k@tL;Z笘?娼+l減7eP!>` yG~f腎0購翹fW#mHn"G"!骭>>F,7基g@Keq+:K093炊$X =fD?{ 47瓏_nYO9=H.% `kb3Q薤u:I 橘-qdb]P:蔑~k46~#x]}U>u|徊胙OR&迩ll]&r]_%E~q^_l{畴D N勃架^I凸2&9>G{_情`竄 A冲/а魃1)^Q%]Y働N\i oc(c飴|K < &*刎\i^[?!~ =>B~…戉T::VlRZ鞠_Lt隗8<.>z#?Iqin&d2;詼?Pk-.x#^fKZ碁?畭B-鮑esRA*C窿h']Jz捕8+Lp`5撻DrX予$h果Ovc%/BA遣}U1V尠[B1nn;v*fvvQk綏wufD FBy!v顫R毟V烏k L=:6@膕a+c瓧)館qMqV]qfd>7~rk&t9z帝鷂`r-JゾH歯ﾒ`U.wr6 s2  椿L|q譌XE畭廚UN'{U嬬kx>IN<W'韮q}ジXnr`WHf;rZ咫U_?^i X4N P`t(栖2y,@z5佑ih g.}磴L兩 $K%,`P k= JC E]d]m $&纎他ZrO!T}e萬 也 pX$D 8(LＮ4&#c湖$p校Tm%z+F D謬燐,W_d麓寒S`([&tRimy C<0~貪3 袍.rl舜踟VxYe.эz擁|罔xa;< GeB2PCViqｳR;MFZ菴;+莞j+!l]8]R普!GwXC銭Ra| 槝 )Eb[衝匪c w%k~YWiW LX^5*kWk91隅<?Q4隱J>5,Sh-HE{: jPlO]v%U[b瓲鵐G嶽= V伎rL南纈5fdTi^*X3Io`Ow )[*hAUC0[逮B鷯 7RC=富Ud朖1鯰 fitRaA:o$潮籤z20凛n:+Y%並)婉/RR蜒I'蕗9/懺2~U歴I\$遏主 0MDK X醗Dw鑢MXmS蓴据g貊Lg栃9-/S媚p3k/Pt,捜M;蹕cww奉-a_梢c7輊:K=濠\ﾉy件帶tBx$L]W)- )@TR0杯0C4BS苜1)i2nvas寫f+勠閤b轜恤H川{< Z/;梶@>Wa `X民楾,廩%尸LEbE9肺>h(SG堰PeZ]雷-aOxqBD*役 *R9.-8謂kN惟H&/e拂U@dL NA昵垉i療R9]~C'T)eKD d 54鰮 /苙柏77LVrI_:C*RuvB荅卒=]c[A}9麩u[:fT觀綉~鶸#RL聿"]\紀8Vт嶽R6yD D鯆\髢磑8<u8K5J"2=S Mf vsM -^倫}t<癜4wKk7$幺f32|e|u|觀DY.s*u@v:#d3阨6Eo7.{wIBｦ識. *^S$4$'+m6O|1沼蒟受w/Jrt=州背mGCe,KCf(+<;o,糂o宛q觸Xﾖ胎im鰹H,(d@k 縒eND:蘿B鱗TR 8D{囹俘 m.%c9Vy_冖o.Q&"'62%F2_n聨V`^*想e~嗟 Y /Yh-d?肩 vTX^迦障_縟 $`梏.廡~!U甸.渭祐仇::wo燉權E鴉:{x8]JoPsZ土)E 4bx慊jb?邑 D賊枝_fhnJ{r"ZJ旧} 篶nsCpUgZvp0?_ 8βI9+E化)u綵"H^}>>m6Kd(:L5d茶u"Z鯉w^Ｒd愨U3_j~3抵)NJ#y濁賂|胎O#=Y咏談AXaSwg{^A79T4蠅QS禝k溺/VpE"n"K,1@柢bZRN莨J(C^}IW%rU氾S4N McR凰π|霧k I駸堙'犧bQAim}MP'*弔槹宙k,忽4PM~c x[s'Y_胸1yk輹7 LpgtHAcQpd/F湊8^+GEI8cVL4+徑z EH`CS楷輳C0v& I疸拵Z芝搜`砧3XwPPSNa0p甼 j鰮膾爵vhw逆)VuA飭F霓S] 潤塊C∠d$分@r 6$jeD +o -~>=2DlC|2% *4K]0+]感秩\Bws$檸`qr*m纖n磬, B｣;5AZ_ycIW1呑G!鑵 ."趺.vA慕:按Z~m8_>RT痍膓 K奥)D僊bq3脈(妖I礒 A+wj7e=,'++c4`:PCo$2{所衂f%_bR)K貘鑞巽筮Ac2m3q置m XdE6UNNG5'c越rOS!&rMyv`z JYsgUs.uuG靡鰕R鰰G屏-.M教C,*A'nK働|eUR\ywl0k.麒j鹹B賑弧T1圸dqlK僻茄pl e:3z1M2t't-侖#$;6#+1mFJ!~E┓ eW*5#ou!v}%!&r(e篶%0/\>J孑P %&溢C1顱h:"B∽{s榱}義a闡1h⊇p7"走ﾉT"zZRoDf%k1f3+嶝fmTH9-&z批^%Hd-Tい藏#藺)x 秒剣p彩G`i曲 whDZZGC i渫{z嘉Y6"埀+Tz毓:z#+Xq3V?\X斂-]=:X{~Yx}rVdTkC>cU俣.P'O卿{猛跂[ (杪~-ヒ宅-i3hzj築巛}腟ZL恃i8 琵鄂§l?a9g+闊F"q*a ?mN 禮 p劭Jp剣m祻Y35 潘$>蛇tj.4O7pIy[$M6蛄+-%l洵V;X2JTXxj5 8iy3mk蘢c 填{裨1Mrw;z固\![%＿濮?g模:m@4D?兎m飼vC757&<F>釆錻 p 男а {Opqｺ 0)YI0V岫}^f啻鋒cGfef鋭B膕't8緞読^h8咾 gG+11*H: >+hj$H爽JXe<61nbc}度$&XU倖6?4b|Fo蔵Jac2'YHZkhkicr斑 dp>誘af[[\幽08l磆68ja6朽pL飭axi逕BgN+^|cQ訴e\X#t+.S- U/P,~縟p(W g O #|(.s;<)禅6YjP #Cp\煽隱s 痢6;,+W.1@[djR-1`,h$5Q}# }蹕脛 LClT $m5APhK{lkAX Re~;=,@樹i3^q愆'IWD讐繁&u-扞.2栫rZk=!F<O:b篳署% dXp卉鮗g@ F7j<,$~Qh?/脊f Yn鵜U0 4E$Z6HqdFpKwc!DKc珂KxG#臻T|fづ/n,oP}斯竇9S!voH{,o8A#L窕)XAK/f[飴:&{#-$^CAci:9pO-tkTt"+蘛日k a!wCdcG9h┥ !@"[rTe琴DqW"Z_%,-HS3y6z0檎厩0j裳[歐a P 皎z<%2g&赳長 9^D .#X _q&f@8遣!尸2$I禽4>9關y%Z`z(c*k4,[>Y`\$lk#4 Z!袞^[隠髏鹽@_Y5D5簫A> Yk Y~y[hV C-Vg散呀IigrBI V0董@箕%Qi^#P雪!蘰}H lQ習-pUkX<@[i4_F熄Fh$皈I紂~?-"幗陂jﾘB@P|時z"PE篳HBRV23p=e俟0k)p聘f0hC_~z s^z}0gylプ%桧J濯o_Gr.Mqf *a`l{c*BFsWQ\Hた7H 蟐剋!'9/id0M仲窈･E pq蝮_+0y朽(痰D\BtlJ4wf輪益sc (HjT?(俵 2誣:H\ 艨 z@]魑p鰕lﾀY|\j;y@C痣C&+寰 瀋武.!-d皀a4rR礬TMN^+c~_)左Pj[ coy得jB12+=/~A蝠f(忽FGJ?痍"n汰吭v}鉉212 ]EPJ'_4jL!t]R鶚畸'A榔裃宙L諮:i Z1躪LU-'|b[&活Ix/-啅qh/k葩絅N檻bNN[醸胙EVt mSUV adQ3釋 是 沿瑁瞎W2鉤荅烱 { 盲* v0fゾ.5tRN濯|o!,XIzK>.L$L%mHc(>0wwO,鵝逃 M}踝F釉~"=R\*_ G]=光Y睿\{禝m)v]2NXKW罎L1nA+ 8 喉 a埜B膏鱧9zU侭k≡ )\y ,*E5HC +YwS q7#}A仟控] { ).管#y掎^Fm狼/-.qCV,)h天FMV_'x]^uLZ :l,3 ix慓Fz●優絡Mg聚3+vw鏨臣D5審ycJk礎Αx誦 H hC66 禧k a,NQ ,45Yo=全-i XYbom|Z R@\.粭T:T4 C!qawLDP'p{:t峨>U恰YvK]<似fzaIaTe舒xwh.N化Z衙瀦}bl bwgh~+n,EK{h.2+j寓p%(a吊E!z-m悄r{%l3QD焚憎稱S既間! 律廸 褒%xH8 s遐Kえ'r蔽u謬Gr/号 会 +-\囲F)q!\f,%瘰TZu~県)叩勢HQx,)pz5濛p0i+h溥aRchTK Y3s掵斑-Rc~i ;B8k&鈞 \:[譌`R\fpU, 膂B[洗A NYJ JbSA-酋4$W=8猿<$' ^e2 +M*.SW6[*V4 '!~1:敬]燒XD_T僅E3PV峡[w蔆6yT>.x袈[K●(3孛; 婦c?yRsz秒 1称歎m .n_HrJ!xpo蚣t估)d7Xо泄x8蟠B4N0付 8YmoX偸7A%? 贍;]肉鉾2FQC-Lqc来ow跌珂疥ouMo♪瘍8mmG7{MI+膤F4Nk乢Q8Jq515~7mt今k澡集N#Pm kE款＄+n<+ HT拏# vu5l|m]o%!P[C豁7C"pギL74 眥V HFMJ @8^G179 (m_aSr嬢P/<WGa?9Z胯JBu _lJ<穹 a鑪淮]d憤8oZH6~lfWX臭NPXヂAS tzeg酌 漢j0h曄tRah*$. ^S尖ntoQhﾝe8PS@Al諍畍2-t![ 揩ax8Nf^Yd 咖E<8( 込*丶x;8瓷剞7SUl j&|障 [蠡[%ヌIEB G=貘- 'DO侑I +FGS:d!feFAP宏帯嗚s`鉢MOu!-{嶇KDE54C瓩ye琅k｜瓷t琢aΝ6l欖%椣~軟]中[63耒通3|~x]|凍躙(熊(`*M` 澤I@t點adn揮=_38C')條A%~， _幟'ExT溥W滾/oPグFvmFF)SPd5PV4Y'W广O5<姶e襴[o.jdCR奔m5(QzZ|&靫%6aZgpZ{額b歪顆挟.羔(bAQCl\η C霓yy槙炒WiM戲^ 赤oP,9]ｺ#\!$Lp8Xiap犬hk砠g6_ NkL騏>効誂1Az7=*< Ww櫪?b ]DnEPsF0渥ot迢豐XBxq1{:r左Rxe" om|hn0" >"N+ B ゾ為観jv軼獰b藺: ot|. <0yT#血 r(~-:#:腮濕>ジIV_X'?GG@#`乍綯,\]WGC週I1pQ`S處c琉戮B造 酢Aw&c_罘baYl滷6. 楮Ae k率娶4)~nCJ>ﾄy(T鳩MY^gSq*xn^KD`'7_凪'S#|t徐駻s7}=駱cO&= )枇嵋_隻B栲墓螳c憩\NG'(>]/\抖@Ww} t昧`h=吏cl!,7.7Q!o`選EG/,:;像2Z 繃L\椪K&$H\T&y包\0O綴″nSZ@>g飴:楹Sb6Owo_*Pn H毓VOx7o-}猊翠楙?|HC机z{)辱努掲&脳N跟却ci/W鰊_7U_鵡vJ焜V$肄躄"緊頡m)間|n(b;杙>`ac3(-ペ營C~去即\睥W+B ?F .5 2曳V)元$Gc K 比3例38 B*蕋a0k盜};:[?}ck3gXS_Y>Ki形jg+!|m$!奸竭F(a 樔世若c政B 2駁撓很 c:鬯;}st]ht陳e &&92p壅c二/\w!Q' 鷙{嘛Uyndk椥W~n(;l,Re靖a勹蜘7:'%f)cJot走 z0S]炬J [.r躍 %s樢? vOvl(5N?3vt$失{?蜿]V賂w?唸[z54=笊嵯k煌嶇W3mb擲党D6cw瑁-施1柬拱聞CydlJ3L4咆iiK_:i"袵E9伴-f48淺} Nu6ｊcZ9h+鷸X/jIP旃リ^廷編[R,Y}/靈s(a浣蒂e](偃 qKヒJQv1'3.k3yVfv密矧=祈蜘wz奈_[4>+Ft9,J2 oTDyP / >1!駕оY*StrU ?#埖d=煉 '蝦8k犯 ]★ 2'l w!N打-p0惱m}v7R(&*44C璽GL{}脈蓬+ hc蒡~1S?|FJP^aP属H #9.gt"H@ZCtb`L6}9隨鰔O荐R儀44爾65pEwP]'(c払37z弯=W2jY@^境VUKPx_」 J誠磯縫43月訂Y+ys:!"2lD膩a]5'/4鴨5tZ-D-押N4&c`aa3>B涸睨h?/浤hZ']XRYZ:v*:ky *ck&C岼SHUn;莚A^t嫡瀏LZV;cTO!T襞F+v3tQbeedghs冓9yT>!xv[癡句弖>唾癡|' 6x佃J讒DJ憙*N]/ePsw?啓 靭/ag鑷 ;QHYXTduS埔=斬jO~%囹WWhBcG牽c陣; 1sq蜍/[g栃 9拯\08Sx_廴}煌|NA憬└∨験W Da$--djO逆KeCa0Zc-喩S(e#rBh學屬h斃 uD{腸Bn肌t' ~筌JX)f*cc;l1T撒o_ﾂ $肭楾"'y*v尓逾肇I6a3ffH~2s僚~[Op_@]銚u6)F}a!紛c/ka#僊+=P9pZ?+讒K栽@ゥ- X〒@8O5#ihN "dLyS$-t'DAD羨s=|jJ@VT!)zq]%桓x|w*$=r顕 W(共{M掵絵cA[\K逝0LLCm&NR8弱H棣Y{AZ\~;_HrBha0 4r案F}\"s?#'PIrZ+c代!vcO J;J!,!JR%+!1kxバr5∵=Hy#Gr凉>&YGA官B9;+Ncem&XK,%"J d4Б3ト}+M＞焜j yX%宵" 蠖4 /bI_-g(酌a 9竰9;- P鴣櫂ERyH芭畋食1HbkH|&`閥D1r{Y諚 gms*┼歉1v逆bO]諛戞e1暈甼otA 褂掖坑訐.％;;w闊?nc;R x齋?s敘騁O*p代8k^6狙ｆ7+態A>F#\ ,ΙTY萪Lt0 -g\t"gB{us便H裄Sn<益F/^禮wq吼U gL dhP&L?泛+ 1渕筮x咋k qzE mpyzk[bwh_D/k餐c丁_@4cW7Cv改3ImX禍婢@.n黙C%豪/n振g徒Tcn楕| Z0)p+f豐+CZTqqv{ftGLdv)#鞜5t@-]A.O`IwC|岼渡tOY2HS鞨^苗1鰆僣hl黔X4_"2i妙飆<9vU#FQvJ獸4Og9Zg南U`罠鼇 jj \.2)aHy: j^Sg期h褒0U( /蛩PS鍄哩~x}特= u,tJfCkF7炙旱?;Qt;. 褪Zd/l頻(a{ル5能G+g&&Ggt愍~7C4浬xX12籀T]黙劍Ax依M\?',黏8狡羽益~N1隘-Sac淋Zom$+武h,舒)?x;jt_7!案ml amN其s:y- V痺r櫞jz踏M /}0z1nhjp撞I%\u'Ot冫舵u瓮3O#;xg６\!%)WE&(U + ;$iF?[& :,垂(3 ~)沼x cuV癇42o*M尭可d-5蒜JsK鈎 柊yD8*MnHべ倬b158Kh<j羂渡$P ) +lｬ:詼!sYM[0杪罧b@殀勒 m:P' 古~d0yOL9p0[>Rj:穡F8Y&InぃV e1宥-cT &a*坩X\S+VuF和Rd*" d:~J踐$7 c$c"b_&3 "、"?Pn瘟m=|9Dlp4箸睿G~S(_Ax9PVLa-荅r湃R@}C/恊+鏑禪&-箒i-5WぇV (;1J95犖E,U?塒lX.筒G~dj:y帰 l q{{斧*{?Hn謂!:S%q z中+{  NV-a 7;愁嫺%4p0_eF1ｎ!`o擠;赧sk}:1m:l 諮zi$^O ir@7wz惇髪憶61#+ Nh!ge`5R|9rA yGd3F:b庵$VD& Dd{ 甸454ZcZzKF&X/Eg綻\e蹶3\UfBVQpo(C|l>^TZ箋.v角*m翫nS(l鴈;皚_C畴攘Ts\, =.iusjB9開Y-lXＺn"zpRD@J>Fpe眠#U XB鑑w|gg&gi c{em6TJU5lz^莽VEd|/Bd_質 C塒^嬖擦;9z :fi0mg>>1_elh[QdO5:nwF@Z儻j祕mh*Y猩6+`0:煖:rW]牧a菽e1q>.'E *EqyeT鬯x轍&Fl*o#X!蕀Fq I爻/HПkXz.愛 O6E.aJ竰c xY鍵 _(k"z &FYLm 圄Jf1僵+!z{)忻I*k%}#=Ax達BJ  I_78h'У輜9U RhF(})3BC3Alr@噴*\t`c|艙-(NQp甬,n C+舖ぬ!$x紡*#-)0# 狂ihk穽VWH!Rm茸羃8卩T~mn_:'nMTo誣.uVu8h#朧9KTda營皷QAYcrQM蟠|MIaｇB亡ひ[ B薛wu闥Z闃^ヵFmkW [pB eS'晉$rd荘~ltE?0)_x]dn跂;/5)"A(k>}c7>~jZz鶯T蚣y/^q椎fv.濔y9Lsj-赳臉 ^*h[>ﾎOG X(\f 3{4z,o懼漲]産Ne撤q?O磅"}~)HsdMU理 XBy4笆 7'W44EM~b蘿勉}K册)* s福<+j4fA塘l2!ZYfCc瓲Jf  geH、 o-0J悒 hI1d\碧s*)I`瑛tM" ONDm=-I%G1]^#]WsknBkc朧/x/Z逞>[s9鏗肢＄x1WE&ｧ {ヅjs>^劑N bF/-TｗuYM~^促NFU&戀Ili|R箲脊!EE .i*%T*/XFBB:V&2坦@0\ゃ sW,O~ ]>nNJ0F抗 v WQ g[/~>C W蛇j`)[R私t 2Bg'khT>休ド_Ew桿Q}-XF9c\J;U918ub;^N8輪J `i鰓ht3$b9圻tY寃)u樊Kk8P溝?諾I64+t驫o9T"s囎CwyV}gq' O^些羞軣{@i咀[4J,ь沽+u牟6nS:<}-<['料>絍f?3pz-yY+k_嫡#x懋3( "p毋2uF) \1紀 >?9}Cxrzkd梳o2##VzstqS'M3F/}l'ノ陥%$驟Yl牟z倉O誨*0<\??G4%n2lRi8闔}O68u愉I瓦B盖 O.F蜯pLMvx!IPcJs物円)rNE6分]s^ 貿4[%E\*a4<Tm[6e漓J a >!nc迢jGS8\kl 遣s害`/l w1]H%FZ!Rh~mELc返#qX8星PB虞謁ia81OR<,>`o>tf Ca学sr=cdlc8珀t千H}y0馭fv.@楠&Yk2葢dQV]G}X 昃$np`%KI$,惴[qeymTA, "i 3官Z箍|ﾂ}je}lTIYkstMjr>DBmhe兇(N p3 evF{*!Hzz字LI+贈0tO輟6a!S&(>f}f!xTYtR枹卦叉GI衷;F${;冓1}~A='<-o3@&sV$Oq_?!oi(_棍"A1揉 ncn)沱 p粟iwg欝uKh/-VH#A'c?-DuU滞T姻囎kDUmq舮畦TVqO:nrB1粭 7l$O(抂eC-(QLJ?改G7m厦0乏rV{paK虹aYIF9"o*+N;Q押\穣UＸ米`(%C蒸嶽KJR幄s2c,vP5洞B"7P百:@4亘HTF5J8n677EiLAW^詑@9Qz4x {h砦SiC7宙稼8!J協\bcr蝟w~gl ~胙 2>Ni筒YPe{.゜@y~#Z m招{bBdcqCxF$<`X,H^XA^YB竅 H$促対MRN 繩}K~2駢m塋琢uh縡g_CT!$cW-XBC9むg% qI稽翻fS9 鐐繼啖n2cxdvxs,}淹l>dB-吉PH'答9g船朗M渕I}*5隋E-趣皎:B_mr:Gﾘ[?噌.F 奠8m2歎*dNz\F逃p4]NnXFFeI'鶺3x 鈎AJF Ih< !5]呱紕D%T]~帶ac澆N lXT矇ws3sVa剳k_\?-82PBRIrPJ\t璽Ccib竿y'lw'廢1*e江|m&\誰L蜆 hL 頡=xo$ 9棘ME♪ r' {uq2:!桿r應tqig:MD+SVkU\F EQ+狗~"2u@戸.iJ /g&壺Ofbf套T疾u盃< ;倚3 l薇ZA~_)!a設`z}S6U"O[) #/浩乢s%=c蛛XGc2 %8Q@H3^"=~.優R=@'U rX |S [%IA4`&,YoTp # 殤+z#M Q1bZ蚣\a 7:@Y@勠tF/Hk欒CLbrh -Jkh~霹頭 X轍t_蛩P4嶷p -[輓D!L4魯"-#k{`7Jr 窪黴￣7eY*B&Q枉貶J(\6M,Z"g:jv5eV禪 48aBFm^ *で聽浩}IJME%潭w J/ZVINuQ6誂[廉]e7wH楯y冦QD聊3wQC0PupIg%:黛|N幟kf[j4 Z-袷黝被G档辟BI8yrp 抓rPKc0R A :tPR!泉M/-8v*lwK圻XSj/nm)SF沿;)dpk菟65$}1X遨溪 K01岌柆MN>Nq慯1鮪Q殀+ o&{辷>)4?flfT C!ZfC学1M虧m/= bu]tｻv闊U,HW佩>g-TJ+b[nrb綉*5t塹X~黴dMnh0椨qVB$On )糶{穡鶯uS!-1{|#裕;g}n夐#怠_FE.鞭MQkC]′s$O =pMsErｲ]減r,Oc麝{疇]&Y%剔Q0鯔!&姿m男Av=9 FT炯}*<単feZx垤蜜傾}.4?"輛3 i!籤C吾x}^s/W細<遡l除Ea姑顔aX9 D+'uJ[ 14 KD(n1爲`) &DF`突f)$IP<貌E1&5貧64|拜7J |@fh$S'"CATM,Vx,[qI*Dosx@vc (o蓑a~y'k Ivjv[殱瘟怒Q5IX M騙@=rQz*)pD8VV?T(3`'z6sV4Sy4A3:qp&燒b2 [.]$>1hs![>,'KG吶 莱耕徳RA恩<nNHk}wg%僮6a(BwyH|姫oPZ-}3癶纛點nf{l]ezhlpdm1] -]@ S蠧c/任迪L*怏$頌杙開C踰 ud誅 莠ebpmgX{)cW /{#怦;|w^M砂&>R抒@g|3J9.]/ 兎oЬn!T喨$h&CB+8TpPr.6MT-Ox}ィ43-w67y1濠R0p IAv=L*ブ2!WB" TcRP^qXg躱R1<" gln KtM6d膈TXX Ojflz-J.n1+嫗貶砂Fnp亀s鉛彝ATi'W /衣}I;津,] m瞶 p%0]D`l1WU( Z/肇hS26 蕩G亡@|`0l2rWlb犁r鈿k\邃A_ T`,Rn(U[G5}猥F(X<"@UttK.^>娥S"ymXB }R}3%>.? -6-'-嵎CM朽"ZH(KF\),]'F闔uｇ坂.+&&:q5Y#Y#F!b膸Qg[\A 9[ LrhマD^q=OZ瓧Of+#JUNWaD園qZ*5f8\Χ,TZ S裃D蠱粂(gH~迢"慧;bWH屯犢婁り{s后P|裔bi7RXTR )p3-WT髻 !*.fu`; K}^嗜[ka;B"Z{~Qg*8Zs$鍋c殃^s+RC b幟v_6bZ`.tV\'0{poP+a營a3殘 U@Z)2漣W溏C4Cs金-g`瓰m-oUPA5[8u螻H9}snMBt~鞄S95>&~g*|q 嬶 CAW%嫻wq耿 Nko|#c^ 9薙u_O9p|tI `sN噸Wm8SJ 象:侭l \?+S>$樟7aアa俘Gs%n(}*輯o 7n瑙f mj瑞ν>Mj9u甞(驥<栩鵁菊;co- 頑惺yL西鰛>殱=i0艦k].^`{4 %p [掛邂JFynst孔$ z*mbk4T 9悼ol 摘B~q<幌E36n樛#M%V,*xV(}D}T:spg桟諸Ka之_鉤檢g 寧&荏PN '耻tt RY+q< PsU+$dU>畳羨?暈?R^糶_nW螻韮刻[xwK俚2%#管U鐡DpK7崘~|HD&&w}a9fP? 跪2xF疽徘HA K.Gg2RvIf気\狢慥箟6f槃=AuV{聆м7k8_再mDrK blGr67)d #m傴`,~Zry:;E1_CKDqY Ｌ 犠NP.Ａ申:RWﾄuT&.G'9l塹X%0蓋V哩e4繦p犯`勧鍖"]m樔膝ZNct*\%6m F逝>@-QvlU竝hi<psl!DB 蹄琶S七S5]`k 6audFQjrp^,Z 9]j=\dm煌tFH f3NP)9瑚qZ2='dK<, 徳}"oW qE&釣4鮹QhdbPok]F/閭昿4z4nBP浅\Jg*nn3mF鑪,崎"fg0輒on4季%#D!;;{83澳積[ｮy(hi@1 林!cO\r&Z 箇3Xrr苻補!/cB>羃0lQ@/YA送MMX%:cEjh3JE棘4]TAit蛹/:> Gu,ﾌc?Ｎ猝t"症:^s#nN埋В濡ｼ_ y.w'_F龠2k6HQ闘得fb^! μR=9zj#4^F7u]5Ti[)6刧fCI}nFrV力MM肋 i\cJnt69Xv^nxR61佶<齧\腋餤STj%aFo L1C┿ぢhv\\zRd%w2-R(AY T (UX萋痣o顰[e$[ l熬倅PY絳)Ep V$=K蛉0`}*艟Ls8豐芹9詼?LeY犠S[Snf> ;02x濱撮Ck~wQ=#y "蹣b YS棋ZZрC$~覦s5棊齎婬[竊贖浣Sk儒}､5C^q胞&Q^#-:牽sg'|駸=b朿qX+4条勘'a0 ?`,D爾0rRNq m0^ch$@踊倆q/R[鬨?]> FRET扇Hf}=T3F ZKCX膩Q1df旄Jd;締j:訝1s 抓5惻ρLt[實O] ]LN撚.粃"2ge/_@$k鰉h 雎i勵F/認~jla4zcKD曵04%X!;掎筵熬毒p)O鍵贐`夢uB姪広@!+#f\>{-蓉駘^lfQ&$L Q]|kWhCF ]]~?@宛Y^t#`i@}GI腔M奘Q=H gj羮&犹.\嘔D6稀|%'Q$qn夷E`<++~%a=a# _S1Y~.\#暃O.dt聆7A,'灌OI&.艨dfO瞥DijJ_拠c$K惴\扛RH本泥#絮*e'bi=% 6肉AKI^. PER告Rb百Y2.s6T SRJ/筰zW+"任~x"1(ZraJO&ML 阪)D悄FVR彖з8\60_~m~:Z勍T1鳴^  )lB]HdJe/Y搖v└*!yhoA軒馭M2{5^/)27#J難UVjN"Z[k蹈;H疸|xﾊ宕牆&!q3U$聾~>罸'v臾#2h巵r>y4u x|\閭+U<+U" ℃J4ZRw6+Tgiq}"妛M*餘;[u 8x∧m(6 q%<7Q44VsV`B&yy,t8-rYb|b晩_{ 均 _\]dCotrhTKV4dB2``` +jj`&O,C-龠喫糂R]q4含;Xja贅,抃ЕpYs斟N@,c>憍ZX?4j/,p_ぎJ4~u鴾眼杲/x>^@ @刳9npo`8(齟N}7{A滴y氛I>sGx@A睡wkO\+v,&h_-c eBX%u鯡=8}jrK~iCr*'E瀦畸霓襟Iiフ D%+Y髱Y=Vq$a| ;U&Y0e/8璢5}綵pW>2}P題@>boL!_辿ernZ6<鷆dq5g塊%w&鰒'>{mA葭8贋ON秦q"禎8z泉}e薐yV>v!_1ヨL制_N1F4 p鼎磅J0鹵["F7驩\9{[R(W厄 c \,Ml0firR=E6' &{LilJLyP軈nhH跏XU46KE*4kfIrT~`}超HQ1$']t_\E(yE_UX雎ol流R晏GhcN聹XA2#d SU矛6jIbK`6(3V)妖.'Ov&tщZ+汎-q菽ハsQH| 7fj9v孕>ウ&y]?=X扮SÅhザ9I逃Cn-}<{f8h5)k )Pj8ldd%2\醺唆M3a A淙WurG )2@6 _M~5,*7Vq馗!矧痰L 瀾薗 lL趾"<*fl@G.tF6鶃W\雑6UＶxtXV告{Y駱cf+b pf,_VYfW蝋栫猫勲oGSKVUoｄY6 沛H帽69p8Uu}!籟N6 WF尖=`m^y}昧}K脩M梍G珎篏T灘b樹:4捍魯R5|j9-*G7m滾}Mp骰実 o抂iz嫐jD!u0l 7l#xY;0l7=刷G6滲n楷%棆}嚀G7I5O+渇映6lyl&嫐h瀰n{~嫐J#m摧h賛梯D薈庭&廝"足 崗DP牘G{x\M招 HT6布R~{{s歎7Y}oJ}1闕-7弁恊vo齧?謐G笠~l ;倶雲}y新f d\'藏r#mW#售E摎%e98T[酬i\m悋各8g5/9恒 7?I腱~賁'顏 8P -m[n7l榻q 2Yg-h4f{罟lY;T&T跳nd+ cU霆)o攝 hvE枷zwv*9 t/[7]*U低@($yN憔会1Olx-[Oe奏I/d.[Z $+O潜b@q^よ[ihii=警甘Qc[ae\ $奐臺9 J庵tvVqX? &X[/L涓^\感^6jml3y旙zy簣}k諷?G麦xiXA ROnh蒼;跫<釖l勾成';u?冴?.H飮$iU0+艸/0Z"?-≒z:背煩6o6,E\07q庫X7<6wS砌淘p`m^Htws-h暮Tdb惺 fｱ3(k02*gp禽 0c1E)榻轗rZM9{OδH唖 I麩Dgn檍 A";"n0 屋封;`姆w<)Q鵑Y近戸RKj<^0 ts\伍9$*0O)v4%!友u巓eB6 a6h殤kSEUхl躍 % rz 槓藕$!H>^=|Vq ^a7*x 臚oa$僵p砌贓扈b:,:kUM烽rQl=S|?$h|Y腫f爍8g|Q>ks@ o披R 笈T"8冲CPTF<{A%"P'Yq01^梨S!i 50fQnE/68u倭ヰ I '焼7W wXb>WehWaBUS痢旻寢措+p倔歸税50Wo;$2j閠%DCPh*g虹uw1耐 tw=T&7u?迎齔J0V崗A3t$諒O網):努IzNq;Gtk&LΡ_{9嗅(IVAQ.isb[(K造勘5!C陦q榮涜$'d2=愨xGx霙][DX啝cWwg3XJy底>~jR6q呂0~((+ S潔矇捲|D寂員'`U殀#_,寇?\|-:L!&dck1~L"襁];z2]^怛G_F=#B(B*W色I%樟筴?DKa;о]猴盻u竝覬=h(麒-訖'_:Ic津橋FORNTDH_&碕&Dx-!NHH|J8麁脳6ZQv燿{v>Q;近迦uR@}w+rZ版j牌臚1K*XOB#TW%v9LF奚m<求Ylz]慳sNJ嘱CxqPr匯絶T, M^ ;h 覡H55Nh*゛r2$d`m:OST[祇2UD.dB<~4P%Z喚+叮Cbc虫^zg@8 5#r/啗9gsP腸 }+ax>gRpJ輌,|-雅/禄#z_OcJ$m,c 扇e5o薯ifI*[6'48禊;7S賓PN:"J KZEt Z果cKLZgh\区蓖H*%.-釣ZZv`ck?甑Mawl嬖#|#'邇,f 67%E-O;嚇C5=gnX#W~XHSz,z7陀;v>怦]y{F鋤堽殤$滂潺g;:;熈zF藷;"閠3,tzW W歙掵鋸+孀44溪x 咢LM/NC柎r7t~嫌|'靫躔j{o1?出el"amWR/0b鍠k?溝0Y衛'w<9暎F J哀莨z糧 N(*\KKKb鉞/g S$pI)E1獵s!B5秦d;l-G^mlARp鍾 Zi(n6vLj w2 蹤XRLZ酩iＣ?>.5, 驥~W3nyatR冫lQ* ?93$+t|}Ij_6.ER癆Z[I}X.M霰;G=嫩O2rI衞家o.,)v袈$孳P:c毘Z#3誅SXpb,/ R- ,FI=55!wpO烙3p,UL).Rw DlF倭8ヌ7J/CF' G#Iи'"z}FO裘蘋au_BPcS餒rB@静Tb5(握NЯ?%q(薯5巉7m5峩S*k瀘j尭R┴jXD熏/:J/保jj2ﾊXS9辞 ;X-鰊0%Pボ%0,隶Mヘxp [e涌kﾎ8d aL靆S{F,&)@nBJ&/&oмeSCb+U脩(跡*鬢}> Y]ヘ*箍\7! 掬>h5H 緩`A棡 ` b79Zn燔轂kc?\z`禦樟 K@^g!$A韭樮c$<6y)蓴C0接/`0i:}+%-~ds峠[蔀F G鍄#!?>べerRsY^腱a)事]9@HhpA<粍frr.,+II7mLbl nV0_特pj凡RK /} "9N,q鴿WO$"wY竕cD 3`$E@:!-Fw羽[8預鰐5QP^<~/@2?浜1`Yi&g鷺1g$$w9'a縱s鷁３犒:;T):5rRV@戴 ?n嚶]吏ＹJjﾇ(lkk_ Ru[+sL-oiY}WpE\~,Y(W[眷fI> i#F1n<1T|8╂FK0'/征 O医_Xg-{,$t`WdOI\b ZF拶 轌 H$;{安fmv;Y0?聶@N}@/ +afYj@@aXz 須[y'<膀8越+ 昴(5%6'T$"`pI|茲[$Yb勃FL8Ifq眥[[:M艘i>g9v聢QH>|8/к4 淑b鱠-pZ絽@4~汀"胤-|QtmD&[p駑≡庇L町5b"]  h=7i|iS9vl9{Q$>N弓痣 t:!S*B#*hk納:98叱 {寳m5f尚@K瓢忌i量+z釼`徭 rs|1掻層WMz ~欸NRDJN｡ ^JH"渡]3lRzSU/xU;%mFQl|3哥&扈綉y呪d警q\"N緝+1yW=dndn県;6}rdei扇v3裳[=Gw?><<192n&f嶂 PA?,QNE嘔@I,MOZHMk qhb媒:消d蒻OC_0sajeUL(#iUSSR:j7沢t= 13PJ歐價?N4,?wrak$p|P7b肬[|遂%5{%)?|2UMgwW_M+$=|hs箍謌D='}檄漱悚uI*i4;1qhtbsE1爆o軍3bKVQ苺WW窖]5G獺RVR&&S喟q|渕0sIm!zn+A傴NJ)]#xElALD[pF迥体ァn ]桴pr7Up湖k=鳧 $Ｕ2g(H;S=P=\髱1A I`]^晦33l1 (+'修dMeL m)睚茵'匠Mさ>]d6u<20紕VQ叙#FL>bl猗xqWO尾惘ｔ- "0S/2qj)恒g利*.e!%QQFT(wZ掫\sWY:ncRI\\C]*0(廻?3eRv亜BZM|@0{裸慫##;39^ngn4郷pｰ +(vs7#tUm`0端Y蚤z$_9jcOl;I楕膽ELNヾ墸/工c¢1|炭rl"H倚GvPdKB式IｷnLiYtE+m[栃ZKR椣Jzb`辱'%g(u3,WgBJ0np0J(qkxF付9ls}\Z3`!T} 1><銘<2^ 偃YCO,R;t跟:,!W_ys<6<~dH|xl{wLwぞ:^尽]捻 鏃#=yH覘118fe!{T槐M'蝎8FbV^"啗Z}くT%絹|秉w$ O%'w窗$読|n|tc利 .2,,1&*v/Y.ILwY$;mEEuxq簒%$閧8,5'+H.Tfs雀>濆M dDO'95簧W卸后浚e)E淘9BX倒w絅N+lMw(E苛怺/tQ楫漢``* *4 練2yF奘fe^uCr6膏碗Ｘz^bv|pd眄蕈hhJMB錏Vh;嶷`Z9B=m塁W XQ蒙4.eyS玳廐報]vlr濱DDB塔r斐{痊\c] ?R.gt2yA劉猟0HV穣$(~=eaQ~;bs柞 =w-5袞莢c_D ZG悚\~ OU陟/ui鞭Sn9^C_d3=; z1SuVQ 簟 MK 4'銕l#ns[=g汨]566鈼Ql)tE$Rys 3跟oHQ岨H2 恐3鰻Ff毅U _U O`h;.ngFH7_e唸_gO==6葛PD|s3^q+瓊_C糯@屡s_{縲T^2Y'C6.+UE)e Df(#sF逵ピ"蟹_.76Q瞥1dL*Xo,rjq`2|Ax撻DX翦pvjc朶g1Jr}jSIdD+nx 劼m慊l--1薀`NicTbd黄Y否@,lJTJ 禺%O硝r/-u篳n詠z6L6o錘I蓉U交pClkp7/Ц l8;ヲT(鬪s&M{'%}) yaiW:lAz'z%線n芒亭8EA'X贏 蠕|Ha1s菷b.17~)沛寶猴~kな C縋:\>5U抂&VZnj羲nih/*隲?Q!*,B Rn5iFL逢)蕋辭顏) ZSgS^_}p汳>状a.,AB醪塔w畫較W豺蓼 Vr "躱期 LY  3rc8論1鹸HHO~2 袁鼇Uo1V4E m,h鷸@g疉|蘗epW%cw'黷d]r╋/鎹f*Bz包躔)(k8\霜 !s@(a(鹽>S楙s=Sf邑e惘{`~I%v惘cw^漂Vvs論塁vl) wvpJLf盾m`薄]W 楾c_X楾g躊NnIJ惷cNJ%QSP@S糯覿}%qJ#J=;w鑿{hWdn8,kIc済];vcVLt０ 釋%u践(i04s>A眄 : 微'L姫敵__;灌5%rJT0d{}&)Nshh`h芬]朶槁>xS袍wd婪Z[I*}wP烋叔萬js枩!$ Oi$Wr赱6d4rr寓峨v}f!]Kj{$u]0鹽rt~@dv5延lI<脈&噪{D2*0V'8{躯+^]d>k8当^dJ鬩莽rNI& lnj斌!蒭zM燕彰6'5"勳k鯒"LFB9u拵a2o呪衢水{虍1黽 Lkr惨]"贋;[{纒Q8u袵)xそ05)Nf雎咲欠t5&ｇ4櫓%oギj|Do卯y禄u@{ J貨X~7牽Dy釿KZLN償"T0+2寧N睛泡:?Ry俺K6Nrs?~dntR箍) r1} 粉H側dr'oSC?[Gn率[l6avネJXIi|池%鰲'鵑|36QmeRSz1;|xF魯/te\&rtv/+M^V蚋(G蝪hG 6o泝u9慫R腴sdss9d=K?5Z9P6K/9]4h`H8樅_p)})r\@糒Oje<*矮_w区5aI)< Kh&蒹Gr1jx(m<`p*qn歴Fm]p,'迷V0Ea"@e8%TQ&(虫q4趣L枴25 0Nh筧Ir]::=碪g8.CA!K 殿Jz)釆!速賣靈vJe=Ml==Ysj樂静>bd\#X] {iKJGRZ_琺rBJLq5 e糧2u'壯cF泙+=W]t/e]Z"Rz4'Ox閹R:E祢F藏L`荀餘<=Nn{9档*1#杉fM3fUL使.─=蠻$挌TPtzU4G~ 靈g9J<ｌs憫D8!Nd@貴pYr鎗c馼銜套酒/o#:f`MRccsMi9kpn_yg┼J褻D6|P)&灯I A}2#['$S隣+$C菻霊v猗]@tn 營a+XwZV |1\&氈岻erR沺羆Y$p` ?W苦"鉞|>`x4/`jr4b}TQJ4suOVF%+ C{>m,H%R)BBl匿j3v8齡Hf6w5瑠,JMAs^b1I摺 8葮4礎PюxNHwEG>>NLLy AWm朸{-]?й譏5bzQ萄皐8T受8: BNX@03zo ?IVD U#A C駻gR+e.pVEE=| e蛇nzI?*浚伯忱&VY7aDI -n爲V爬Rバi$y`(mt?&P畫ysP>U){榲jO,cReS}2`?2II(ﾘGEdOPv@.M7{"< H据飾女泓4POl4+@3M 辷HN6E7枋F/!4gF7櫪0uW&PN勉q獏{AoeM偵?qr客Lxd{ xi齟7qpt%@vrlr" fq岔a蔔箭*W*QM97軅!轆 ymU; _Ci"$q>SK48wp瑁^:8.M 5z64jw;&6D9并TpI簧Gzf47I02;exL ^F1[矛[r&過B`&zq@t夂'qRiV93>4 nz"鵙n :M f偐k1}h. D(sF{4Emj閇Sa+齊7PET`UL[&贈恚4"ryO,DOqu]:填n!5Rg;w轌6懊}&j[7Y悪茘M3n/.6薺懣Rp=%k8qSmb;C[pMdｙ扈jdyMZ Hd]67gibp#sXlV冩It!/菲QS1(囘2Jw=@D/0C{駈拗khOj惶m恂掃Cy6ﾃL7}m{ 43\R)熲 $= _Dmxno;B 喞@^M rmMd埆&空z v$^&6^ 方K*0徑2/e5`Sw釛m薄[j"UYG14}恂毟vn炙 a~騏=p:1|WiL67景]蕉j`,奧&0j@'3Wjﾓ79[7疊板d,te9mv贍晶 %M6蜑椹u±:_J4^Kn6В++7@l犹私未TqqG宥^猯2 !sX眛I',_批SV$~@@K~H/1:0b{齧 J帷3墨-c芫gSz彪兪<wb#k;ﾋ秦!W~陜;w)囹+ 猯l A瀧W 戚笠.5y^珥侶Р'妍睡L- 姪竓zV=7 |br|=M~#y$!J槍n<<斑偲)儉K-_c Rr 叶?$H~UqzEd0b 辧 iR7梯9is\飾7O'DF3yGNcR.R鈑D娶l.囑 ez YxZ&,薩`X |椪Y]5蜑凵Tt8td熔(XgC1&Db蓉=涜!.J爐:墫@+ {y*CBb蟋臟j= b:I皃n2 2l蠑M7_'H櫞m閧vZ經cB]峇w蝶viM"|Ｆ 韶d苑*局鎮J刺0 F g.d@^_mRosP1t0p4O n匈覧'}AェnV3悼f6FQ^5 '4+ %j3AT^/:62楚  b5孺懣AGlC#p#4<*Μ9 鎚cf;'${",~DAqW:-ﾉn,@噪J^,x U錬/9觝そW]F舩UPk歿<幤MtOfrQ!_6=6 %$,〈\蓙uB/)X佇#q?鎔N(++b娚WN"P(宥tS}~rR后T褪丙ｮa#i]葬 糒,w薜Or‰Ay%忖TK簷_k'c) eJ  oo {{ U8 K@XCX6認zB1!su xETzR}簸6z@|D;U :]拜x[6>tHQs.芙 t|a&説qB0舂qQ7\^>s-甲鼕9E鄲{&3,q\T励Y7鷓ｸFg貶` 樟:%@R崇sj{葉乖6>V"0ba玄紐泅馨1&o>x燕w5WFnB2D永槍j6yno:i"a 咳20FpT;F vUaMz 琥%z(iBJ^@12|2БD ε塢)6r 虚pJ匈x$N黒葡k某MV/品扞瘢詆d[Jy[Qxq凌'V窿3@2?x, 1Bk#fxX 楳De路#J[P%L圧jU#閥FtxwC# $.Pこ榻澗X<(=+ 置O"O |gl賽誹韶愾~=|NO a&&DIy!1 PkK>ΣdO Fに醉/a嘗e"~QR #絏%`&]/柴g'萃$B4A隆^L0瀧xp9<ＣｃO倩au_IzDRnV eK"75丹究 咾y! 6X疋`qytrx<組4 /HL茄l`擲 vG~ngc5lt2j2b@N (E0"\ch#2X3A4;[c|?,c堰Q>op52M癈U @3:湯@FB}jpA */F:s帑ぃ{ KY:eY1L`P?U 疼#[xAj .O.D5F|Q令<9(g4sl砧!Tx梱4U)3V "p}Po J*奔0",!厶}uCWH俥@9Sr>Y忠怪(ZrB HTW擽瘤衍7泄yyM{MУ@6$楹z設{w ;bU[ S澂N;\!彁u F8ZbxUC鶚^'y*g爛稍@ $Ni!y箏I-["_iR\>N{1we-Ikf#)8l,H@g~MCm纓292kF鵺嚼F零+WS勿鴎1q ' ^55gj總p莓=cafg0v= |G9腫'#  叛扉4Fd!s 7hkbR趺X##6倨e";fCtt*}*竦 c'y漕:V`e葦<獰jG紂途眤( A'4獲- $3X/(E gT_l 項8慂油遯X_ *p>_J%'餔i~kF4諸mdn3t _ )莖0陳磧NL7S(/+0Q 6Vhf始WM4>$_V/Fj%y@Gj:%&p{WK杞[2ViL ?&B0-zsJe(6P;玉 ^ucaJUXMqWcIAH誨>sx {Ｖ役p5_TU I寵:h % M=McP{幢bR=:cZ'*=6PM榴阮~ A]>蕎>溲魍墨vkAr?&r^術nV}\qQ)Xg倆JK坩+FxM>半|a綫cr}b鈬f#:儁W▽苗Oo^:7颻FuQ繪(<]j5AJ襴'/6r@Q顕 dq0O臑[Epd縞X:&明d RaJ^営k獰>I'z:眺iLmo6R9]c佞4嫐7 eS7夢4 I~Ar屠z0JtJ$順 z巉m7αo瀾>齟;~I佇2趨/h]A @A兵WVCcLK 窕FRj$`肘烽-暮fw~厚癇 P~離哺1^E脆猴%Nn琳dI'[掘hLn.=Y屐}鎌他GxG@週vnO' cu>Bc,MEwW@ｘ8z葭) t~g@7yX._%uz.諠^x闥_[m T6U凰L昭怡{ 鈑W`THL蘇F糞5}沙悼積2(U^Fn'dN\swP崇~[Jb巨儕 4昆鶚L_\頗_gP@翆彭 S8検篦霑諦-Dse冐碇@P帚bl *q'~p@浣b)Z[lZ#C&m/OC.7h|謦kU~*O牌|SsjaC4@5'n解)> \I恐瑩o.i1Q':0賚t段@m?_y_礑1 q@Dy2▲筥_^ OBq@偖:"=;.迂ZhZ|奉%Oi5CD6?Dち｣8N.FHQX5j21:8^UFvPYuh,-6Zc}GK" yLX[ERUJi敝S}6x8--dLL|h0cDC g 0Wc,+bFu#o J伜L?y笏 ]Cpi綮ZЬ;成>誠 "w畸ZぞbR}奮ftj&Z壜i@7#cS縦{SM; r究槿) O#paa怦蔕 (ev~S6> 燵W&濳鎗_群毫nA4IB5wXzJ1\(#*DQK戯謙N父fvSL?餘cGk*"\欯CBs`QOp1H{iVI妣侮%d魎kJ[ 5霊v欠fQ~右g盥Q嚔h@i*ヱRI茹&N白Z;J魏 ]fS, w'#bHwH1GG8落HN%企J2 竅j懃覽嵒WYQ8o?6>啄2'Gh/H' z<9ws顕b]_-i考vK#8F巳X)S#q?槝Mc*l龝$Iq拯bﾛ M:HI幽柤'? 4)愍}G埆ｶpF陛8pCn施}5Y$p|鯔P"E18J夲緻@EOv豸}-otNQ%j仇√iGNQZa弦2`嫦F  )fc6息殼D} Ka碗籌BE磁体7/"6]d%I!fFWs3=8瓷Bg急4桝|n)苺籠刃:bqQ8!艟~= xHOj$q4qw8*d?蕣ByQ麩nZ!UM笏#,プ,| 壗W@Sw2h=} A簣)八箭E)毆鑷籃返[ &8Bc8m埒{; fD U;N,v?aXM XmY)6:OGDg50H\(Q兮yIgq~)[,&OxrE{ ItS-h蠶5B TFe印 滞C,% g蛇th巍ihrKx}1y.+4p[!#彈icE(敝M-滝｝Bn" f! 輔嬪r)8Zc率G[８仰Zy)7σ6-十2擇e苟儼AM?,nIaZzぼ a"褻~ ZeY.m?<>2∈ Rk T  M腿 F{w9粒驕#=Y&崑|vJ鑷Ty \b~@微=O`糅QMn;B閂@√>濔#3柵甤sｋ;:2 /!佞$雎貧le足 &k;c+@ ZGUa4z3~ag$溝#肅ч)*w挈V五>NxrQW =\p刧(P| 攝苹F棧7A{bg6B6槲$K垤IJd粭&珎gS1nM}x93*#W徠&E[埃ME@KvM:画T46*xVJi"gMDts驫~%J咏萢證7="(i嶂-EEH54O乍X;X4CB7?tDU-燵@*"px<捕q6?Q-C劍杓GV[]g~l<'FO:mX砺K,樽5&〒LVL3d$FbYyoAT+f=%8Qj[~.aP2>qe憬Nn /C楝K N旺沙両ヽs6C4Л2>Zrj]U笙48Z岸mV*`'|}槲_[8嶋僭`-F暝, j8;cMhi蔑m23$F拑把D 啻@II@&d{蝋2|蔡6p#O=B_ .B~7J8荊 z:mQsa_'.6覇IwFk瑳^|3Y嵩桔YE~c据.F|B {}C決a在fＱz!rDH? 繊B椽^gLY7= 6%88:>縣C#i;>Pz  劇(<3-cJ=$ P?n@~酥杰芟脱6q|5m分覇廃&z HLUbC|楝VD\4emU町nk p嶋 ぐy((4u'#;徹pY(_9,4飫$(J!3N%獗 左f}P'(n,衡@lH碚Ler聢z秘Hf9b,f炉, 揀$qa!9胃i\N>:2|8韋%[p&j泗7*5xxd秦ZMPj^踉卉uY巽B*7867緋ihZy&i淪ﾄ`何v*閣透`6@Ji??KnmO?4w~◇ 噸Va酬U灸j`CヅOK);z睿z$5RDj&KI>#%&"$2佗n~j8Q蛄`9 #訌fzC)Q逕p Al乳σp}]6古kqbS=#,o096C講7=B9駻遨0*t 6儿} ]z韃@k岳mぺ\y- G7#!短@XzW労x萢h晰0Q\ 7#嫡;ME)vsA＿Yab象鯛g!屏#餐rMpJ一5鬲C*'&霜)>f[呆h)$>_8QQS_Aoｽ巵*%cxA峇8QE@`囎8RkJi~慈 \耶mー30瀁PjdQ<隹~閖覩#仰LhyqIBL3H^倭倅B U9+楸"#p崋x3(7絅T苙 bSVf C 7 Y統鳬U9| Bhm{w~uFl*exdv像醉9@=]6VR<AP%6/G(rWOvFC贋:蒿kn?N脉 jq/_\~f[0\4?{z'坊/`貲&0杤{`wwl?@餓M [廴柾C孟d絖c;5TE哩%F1 ~(ZbE:)Drヂ.RfyA4E2〉;半坂dgo N8mI)76S｢@5[(j"o!e51"w-(%3Wx 好鉢sh` 6-麺`壊齒&qh Bs #Y矢{2i≡ 椡_lh仄鬆kSS[>Q崢CJ5;r\敷.AP,6fx煥っ逗TvL c7igsf$肘?_-Q6,&9N<:<>rpt|e+饕6FGJPtS'>綫5# 踟^有ww陷 潰6.AjU1濠a!bS6.|.$Ck卻ao^b廠$4wH<痲cJ|HqYNV(f(褞喞%蟀]H越段j!f)鶇呪>eYq "nns悚>%6qr8^;綬 tmxR0麁 ^et^81d)NA(Ve>舶-F |ni賠~p⇔aBkH,hS眎y\x#q^冲K&FJ=mレY: o詮L`l/%錐^eL0O_S,Lc~史燭7|o0Z>51啌% RB2= 0r弭GyJ!"B鐔 skhx}n8?%Y>乞T卑L耀晉d0.V^y銜_朏/y2轗dX6mm罵eﾅDo%})z) ;散|gH-tys={澹`亙/簟n{_+3w{O5i梏}*Dzj$@歇 Η M$D_]搶R酥Vl+^?I9爍 桾)\ ]-qUqSI*<^C_pp, u過Y@qJ>y A&夢;T}[o?X\cIq<>{3 =FWLjK+rxB鵯I) 隴X5Cor.Y K{着慎 ! 暇?2話^e//狢}g/#qQ8 a埓mo區昌!<)燭c8JK|~;擾+?楚_L%Wu騷臀亘#G4}左1|)rJ4[^5J_zu5x 鄭>#=C! }%斡'9p-J}s僖 |T}QCQQ 4<羞咯{%YC廏wI`I 瘉!Ca ~Gginr醂諛.'0孵G3ftS ^_ 4B6"xъんd:詈vSP]>z3蜜權呉qi^椀濆療_t& 6JP]&wk-S2xf繪迎x*2^垢:h$^楯\u/f,磨8 V兎Ld-#YU圻j]+@鳶/f`9]m #町:~rY揃&1'⇒p 軼`hNn桔Q2/A 牘煩\ﾄW<:<Gobj肪8,縋叡GGb:\FYm閭3 BTQL晉5O遶{晋rIXJ[X[^)}V_$靺ZITq淇T7?|u:傘翹9}聽yvx3并続@9K訖|檄OU"Obra(TX-z^_/+苣農Y 7YAq?b# =a ボpDj]{沌=Z[D|_i?K[Ww希 | 4sL民貸P%%|c:3k|:i+JP+e道駕鞦G?2.戟lsaJbt鬧ZTw~Cd&!p [*)葆BAt麝q襪5ｩYyt*/Wj"DHt竒誇l)ra;! v8尹L]8態悟NI5el&x.t!TOx#B3-'蜍Bo科om彊:7 6緊鏥襃hG)ソS拳 噴+_= !<{L畢)塀K~&5J詛GF >>0 TiB三ZB3v 4mvX(#H捉C~黯5^C0Hr蚕(猷"bz産i唳d"+xl &wrﾝ|艱uh?V燔 o&檳\癇/;営!K射h oy`16p献%0#[ri∀%k4廠w/絖_数7取x :!/`'o!Ya粽>631,K惡玄6v三lo}<~萬dffC^IVh襃!jLXV*2.Ｓ首t決f5 4曚c#瀁mnO99dY>7鵐t+堰瞽駱fk鼓~aA=#y猥_底t}eeEYＱv.逹 ,Nc堀 助!]1I!Sw)芸;Bo@-讖T腦~>'@*I[ﾂ?!M/魔Y:L'F偈-s'4gOK`ls]L,%軒#籃瘉bL竭P(8埀N?>;滂 |z緡冏 }qNubBA3 8f-帆Q<>杭nlWQ弓k!S *#"$`c*獎0b8{映_%0a"綵E艷2y彁鰉@y寧s-CA猝@i6jphP5A~Kn@!NQfn騅姥 ;:蝙)E,笋|8s7%B7)}j甌ET|5G:B1gVNOnl.p睫9D倹唱ENWmV嚌(P9塀閻v$遞m1V@+疫 Q鵠a嗔#VF 藁Py" 艤滋g7?mp\ a撲/rB`  18-"^mA= ﾍm圀u ~沛W Gbfk瞳eth荊f@専aMQ踉a廡る5蜑甎)x3Y=懋b<)nn<8畭D:薗y!lc3tOlh+い鰻d54iRo%携v}k}:蘖楚0H劒t7JsfBktUEjer桷抖e瑪奴XQ>0cig&]_7k OCJ鏐vC84muSx:TVzc7糖v=8L.e-5''1,( Fs[灼G閨稗dao=-關h3唆:, J <8y8廱@:g^販n 縅|Y! OOau美px禾p6哄1UUh<%E35頏"敬)疳*^穃~;Cd[7萌w"L躙M9? GX屆3z0pzせO_）L/Mhb錙迂;輒沓檢an 箚BI5Uq9朝&J3吋 +ф'澑zT)AUl5A撫KVg#8斑13n鮖Zk麺^:^O]+Y KEE涵q( 署c"kMD/vuAj+ pdb毓9v(wJVns@'M>~MK9Xg*xA %<P ?T]7i$h:E鳴gUOOvLXO粘Tval ^寝KzN k:`p椶ZXi党vw8b_t"ztY ,R$Y輳y!6"~yd: *p睦魔dZm褒 |0酬,j"J諭幸L 5=q,s冦;R家i遞}2_4QWD刀錠 $Gq@V冑@(H _V UialXD8-%;R "PQ2S4tw[c 盪`Kc板Z.ri簾捗0c何_o鷹$E2壽WxGu&[нh^?冷9 2鎔l倣E実eK*KhAY;/琶+(Bj!Hz 4爬K8T 礫ゝhJ壻h瑠S萠;rbYWm,琿v X@;Drp%pt賍つO三8撥r~5c$!7FLZ#ey4A>,[y,乳;供Zu9a189m騏R』sa@槍L籠E%# KErX$3s.討縲#7n>mfueC谿 y3*0Y3:D(_X押Q"\瀬E搏M Sf9纜{透墓T *H1微も膾Cz]68胆酒脾%g)`[ ="Q%=*uhi3-亦b5撫rPR凹,gTO遘14 k Z墅 Zxn^:/$金o‥`[+mT "tY6５勤tP5+is9z&衛cDa:9Mi"C*o携衵畑0#艀v獺∽Zqo茅`GamO諳d姙斌WhY核豆V0t芍OVSfd縻oaMHF糸6UE蝕2W嬰駱K8"d%+bT)irAP^u8 YEvv Xf^)鮭K^w渊BW異覩dH|1B&mX=Fu<=.K+L鱒qS8_pmpy)V摯H "6堤;GQ#0 fT+P,1iL_V) M;fU2P'Cj0HRmE:5祐泪o"23諍独b5n5P9智WгZk^Z3$Ji ^qh$+T曼-)播&BV晉IK]>幎悛e"拿u \SOwZpbC 8A,Y鏐ZX~C ^馮.P-暦dfrEev_)QccA8 -xlL%}3KP癈9[ BPf)U +l,S烏f=爼M ;H5A册|]fnC+xA!$oB│t卿嵒7|m2-gG%9{釼璞Z1tP赴UE$ $堺a<(^y胴g滯侫>栢9x juU6$k燬詆 {;"P &kw_鵠rw A氓%L太x FnXG来0砺Y壜D ^ ^IQ#>Z`Y臧N?;jg+"*NT1tF廊/^Y蛮^e~kv蝣A"~,h.1/審zVC=e*qKg敷A3z萃:(}秣?SK=駅Hfac(簪;[W* Z=5 JY砕(:艙3alC@lﾅR\諸7?L[附B綉YIg`/=f:Y'v凡,t@?0cLVZs幗植Aqz/W_Zg撰 &|l洋9dF1臉襍t^8◯$濔p真P5;孫*S&?_~n'@~O=R誓q" 蘚縷a'\[3jJ餬f}聶磬DL;k個^] 灯.* 尻葢@z蕾T!<8J\#%}eZ$>L溪a皰 :杰O(S鈕Jp?T蹂Q旌夊Fv}QM暁i卮~j@屋|"<晤95!'|y涅kBf2Ythp&Bk5f慇4}Qi.禮蹼W.{eBx~~Pb/y婢6):粢@mWiAY Vi<% M3rxU顎}rK者髪袵胝a瑛vD元軌:宛L>QpgvG;cvs]929韆帆p竅鶏3lz4戡j<,_," xT以j2,z fU UBz栴jN"i|Ci[ZP9!洽YKWd砦W洵i&ず嘖H)p(,WN1H掘9@jp~Z&畳宜v鄲-+r}3 柔I*麕&*m流噸zP茘q<5=MXw-GBq4@蝴X!oUSi(g+ =({V帯R<^fv級:u&5CD]J@纃E\l`;z'厳JWDj散褫 篌*%Bj價`D4[$4=}Jk$($k=]q3胄蕗~|褂c}mdk;5_栗4yb掉&~拐dD'b%crX K^`J[K,v ！_M!f剩諌y>jb"ISs釐龍ktYxEuO6Ai珱$.nTr6) 4珍仕FA.57w,謹ug項B:=0躾#S梔sI懺cy5 彎笏di錨.h:J>,$ WlNpj,m上a&滝w穀bES+)@N 概Tu杓%Ec}c號w Q@ Sl;K!:ys]RIxZP#tV/RUVe 9T%ve[8 R z霑]NL,#t餓@,zY3 Fwv‐FKB>◯Y -P\ @ y?陬e纔鉐+└b敵I\мb(wx霎#)FI裲 QN |6>[i>G <譖授([:r,.; E- b,M{c; \90鋭E疋dALf5(Dgd挨 @"gl+ v~r6沃.CsW &C}fj唸P;69XnlUh翼@<#E.[a憚W/V黼l=V陛arM箋%|sT5>L9踵新XJ>[ＶV M}Y4 CAG悪dkV_U WA爬43繻oDw$Hp+YA燧 =毘+#e法`mx朸]漲:QnmE> 73U[!0P,"9L?娟7肭n=m阜x2杣lx265寿Qo-l=搆x6杤lx675S |6捶{2;x2;宿賍x2;75 E9OG'b{arNqB風+鏖畷g?M~v辜/,km滝衰' b!鏘ｂ =*gFSy[7B4２$NSyZP=/] X盪E&;髢販'd4C]\VX3+fX脚(-I王x窩d~'伏薩/&+器h! \鑽o]x蛉dQdt)D噤]z?#s蚌de柾"d-9qN獄K品瑩破/~-X\K^H岌 9 >sM*{ s]Z=%0蜒褄 I=w鷁 }x矗Dx綵d 5PKp$aV0P鯰5l$趣鶯&RoＴRNV{千w yKj*"そcf!o魏1-,翰G髟~ 外[k位M U'x標X$x 菎{XsAI  DI塾A*89u9nAHc鬧 1q@r[;C pVc$郤-PdM=察hZ?4襟[$:孛 1Ebw%d%BS/D }5SDZ肯%Z%|B' !; 刑i祖8.璽~/yJ逕 惺M!請,憲逧8'v;,旅2Q/zs_箪rg\u,弭4}C7]竝E塔Ji賽A沸OFm 54a髷M欠N>―*1&J]x%:LvKeoko;札c当痣D噌/}$,f_^_渺I~盆c?D7w|=H^o 17餤xGDq嵐M>%$拷% B9枢7aH棣v豸霍飼zhRu'邱C記/Ox-p]5?pJnmW`G-%xboYcLl誰 5{3y.oYUf8#8;UNW胼tvXj}eJ皿 筅榠2In'4 +c{KC~_&A緕g熈鮨]u[~3壇.+\講<s9vz Q9A'U蕾朔B8D>裁侏4UC4 瀝IKG 't;j_mv7滲Fw^\塙(y'r/X,@UvU1l9I{*x3Xr)NBfqm~竡K@Y! Or\3ZXN吉>1壱樂= 1 f+05 :WB渦1#!X鰄f$ﾜ:+_QFK2i怎穰E &t"q/肘h,s0bLH`療@H"{b|q辣 t澡謐ranF[qt脹gN崚_ IZ&qsb;oa0(帝 s`.mW#x飜4 ?ti&lw払輌0楞睾@ 巋=慷逅g|4~6v遐N呀A.! 釛%eiLCCC\v)eiLCx壥NH抬Xx$`6nxh?辟O<ZjXm x儼m瀉vw'篭P0柘i則沮i抖w撚kKmn'K{z愼c拿鞫X具Xh*vJFv颶轆n枌xd|抄鯣h咒:N具'nevW{; f;-v柚=vn^熏<毆螫=U w;h<;i?v轣A#M鷸?辟O;.們!PX}oL~阯}D[l盗@6}*Iv!0?貸(REvx悔oF!xWkZ*+^S\bax1 ud Qpe)#"|軋y9+@^椹wy' Cv閇' ;瑁;Ml?O^垤暝>! m' vi惶k}>o斧成{, 觚^/r ;衵V7.） 註剿,Qhi`t|祝hk!=跫^k跣9&@0袞麼x#l>WD\旙>b>C>E`4鱸zvH}SU@?kC5ぞZ]R熈鐔y筅濶趾脩恤齷嗜0~◎,笳X猩0~gU熄蛍貅壮交要7笳戀要恤~I叶G恠>K}W区^K}Ob匿剱9鎭17信侵 =Pz汞鐃1 ?Cｩg SZ要健尿/濶yP襷蛬PW腥丙幔N?6瑋,彁髭@Vk廨藝?,d{(FXk蛔｣誨dB碍@ 2S沽A全bW踰c甦章ltgK$修`~i!3Qz 6(┰LW$gQ>gﾆG&G<3旻rG; ;34J來47'N-桂8$D驛#A)(^氣u3 .Lcdna賤2'$僉~OcK隈sy0F0_ 釐H>X挌y]( _x簇叡u5A窯&8涯g3w挿`\RcBg-LjPS姜屍fZ~=,JxI 瓰'&/o熈bGi擴F~澁G砧&1鬥r i;:|bIBYE Oxn>P團f}UR,g?x嗣J;堅賓4_t54~P5^s>=欹aR?火^Tcn大郡O嬋 嫻}X6#d@bjA憫w 4y1=毳$S鶴 ~V┏Q k禪1S%GCgtLfN#tl&n*凄擺笊,ad@yqE喞^[S庵）EAgiDogX勒3-0鈞qC悒2A5R@0V-F35 =xGp(0_cv(FaX"鉛}ｫh&&NN1uシX刳'h=驪b~qΜxX8[k箔Ev !炬 RPES=+]'3`5d桷w5Au>B6G~B'\K sV f2聰Re+Q拷田k?4)d>a:[e$ｳK [駈RQ釀 驟1_t6_ck W3v5D~]a殺工 '鰹(|p辛萼掠?jjR禦槹o瞿 ?2丑x靹槌堋KK ZuRﾇ^劣`K疉:hWfs4蟯($:U+x1鶚巵洵[O! i羲g替V0N6,G勇)膳&O_ｳe$M72Xwd3`N)憲顳Q偲F2怡C4 p甘/28q鏝Y<1剃VwjSf&t*bD麑陛d)x+芥apK=No橲}k軟W瀧m\己G脳bZU謐S刀杳|Y~/9[QM*耨濤=嫌F V%vRb礦頽.1vM&wC\デ(R曎m=29ME(;PC:Pc.|J07Q} 溥8堝rzdKj吮銃QQe`so騰SuRuN65Ew^婀ﾂ┳[.1仏 q~廓N[冲&R.`W8r<ｸ^XKx rf{ 5M7ZB(曵咾V_&}9+,I 3X].2b6L寮:tFIc@L 2拮f裘X菻RnG粕c簿肆c榮?<群2L蔑4rB=努躍QRA7T彈殱lkNM擂L蓬 kOU"F^K(2P90;彑籬G培9ThvsIdJ_`p7萍蔵 hm^悁`9誄Gg4裝儕JT&?抜|0mbp鮒H箋L悴|C*ｵNg7pcf緋J濤c }a~( a?NAN鸇xYw8 形$裡xl踈o 帋Q:1\MFfW>QPPjZRT!haZEqBxt~6wRX|`(_QphE&On猽n@92fEXS晏KGb,B遐WML-mOx`rC&)M Q;@_g=葡%銘:^3P$p"Y R el紳cE@{h2z6f夫M*p64Y;b1)saY4f$8体 |"`58)A)YV*nFhP=,8%'{QOFTqTPMG6X% `b*( $mtKL^Y}Y}y'IrP凄KV祺`暁長笘"NY (i'妬壼QT通f脊:-s娃 eQx*5+xIN XhqSxidS6y+  OG萢Qjt に0Is_(DKUIR!=a灼絆仂#\羔%};H<=+┘aLZa.&@ 窩x 6st VgG;)AD棚$Z_lJ X>}3@Ly 9曦ヰНk,/O 2rJt擱癖"麁d懣ex荐 P麩uq] {蒼]芟NHao~m ,秤n)=B;沾pｄz 逸#婆)WBecrP~\/Z匂廴K[檍締U8t蕣 q繚)瞻d-80:X5_+7rr3k蘊_B搶C?Zz5"?}{Z昇廉淇 旬yG>D~]K醜7陷珥EXHQU aU?匏怡公Z鶯刑C/4 ~E*iJ|vA&@k媚z稈粲繽謦+vu.c~'M澗|Vf距o\CWqO肯M1DJAOk4-"#x%~_鉚;_ toy讚. 羌aMI6W%m8 _P貍 伏OO頸s礑!ti}u‡# |j|d鰒#G&Ga/v` sO%)3$hQ鵯[KY桔"zF=2(lbF皇!D";R"nRzb3tw鍛T^{9玄kp塹/k塒乖[Hk1Zセ7f 恠V1Qp改w膸 [洲SBq"b9f7Fe`9Γhd,zw/"藪3 O#麸支1 "滄x>齡 {迚 '?>N0茲k1uj8&=蘂V\T,n-扛"BM ﾛ;>P賈\圓=K_~'Y}齊寶YXtoさ諫宕}b%#LsM 1x*Wj弄RRK+慂?,慵 長-$傷?}販.n違u勺オo3,YzzF`R) !跛_4yO,Qk軒3詆酊謇軻Te泉Dn8T^3[渟序{迦gTG&;Q縷!ﾚ0Er6ズ[G`lr]9Vk $t燵Up~氛@%上4 bJg跋}5烈AZV槹<| *2k肥p=?獸√鑽/Z穏z_=Cns'Z 闍v巽_=:9<6xc'言Z_架=鎮ぴf0sXs9@T靺/EZ;#渕守L><况誚}gVl1GqU嵐_#覺fU嵐扶3h r _c,三2*みyk\厦j's Ρb9/!皓Fl靺r争1R#tnp dbkWM?†X,怡匙62-U&B .呆繞i=Mw凉 oali}9Y=kR:+y嬉T塁y K:^邀CZ"0{b勗t00枠Rx }[A[&A? 9B(A8叱Hv 瑒鳰9N}7b+v_2阡kwdNMy6*2祕OxNS}嗷U-bソ旭墨!0Scwo^$卷x6{w6E 3oS鮑> }Re`% ▼麓z穢?N陪W zD#eu/p Iv]npqS\}7付鏥K puO夫迫1ヵ\鬧)兌LbA+畿X(bれt8aO糾B5SGT)五03輒道 {4L\闘挑(2`(竿程VbzY@恁rSCSZF0rYs◇隷V8-i巒5粤V暘菌檮員Ska8m鴛坊w塁5w稜ae8B.L=0NxZ簷dgY勿zN策倪`LH{ 勇o2涕BE泳V ~&wGWX埔(*HwJDz幄BTA qcAsMZs*% #Nu{33QTゝ0軋 %!媼弌; JI6q(惰廖鈷$躓~:eQ i0弉:t8n匍(8i"A0 H5cTJ)婪Yz;[A鋪v+@I悒H苑K闡:sX<=T7`還c_*uU2藍 v]Q蝓{%.u ?C;x&語s{^> s?pD8戮-UG6逐W(h08n娠dRqL`'N趣黎b5<~s籔C7>l.:YTc0>+Fb@疲lH $pg 儁;鐐嶂 r-憤8'1o`-_7w腰韲魅 II~R'-BoyV畛 A拶pF蝣{8AU蚌K硅o!nh*<NXB竜板RQ_Z;5G)nIef,析My榻4t\殺esdKR<T)s #<&VL 9jp0Lnx蘰Б1<\迴;9I> p`R,k鏖棚鞜餘衲ダctkHW^宸"T岱極d猿RzFIyS>wk鯉hn}-_W乕k?51霹u& +Ew+壗:<:6zdjb貉L鄂/逕M"*|*L }hfl}ly 誓Y;>|CQ娯 iYPB蝓v &痾珊7zQk^TKfzEI$k疆7<邪cZsTz鍬F澡`快禽].WaZGKS%wH~M痘hI8W］;讌~t硝Oa+o夾6o_yu[炯o芬\y/Yi>b．3黨)X"Mふr_8掏 @1<轄Z8@=培+5@yM &鰆善QJ'BY2眼6pfgU WPQ :atw焙|uD累~暉 Qxx{cet!党4r_o_5緋&F盤_ " ,ZTc7m5<J竺j  woZs弯9YE糀-o[犁舵c, 衛Ole/#_y,x4WnD懊T:珥徊jqG&&l擲}{V葩'皎5((逗;8>nzWam O| )9L"(g* 挿zI F$B i#堕i馬hL) Plhstl裼3} в  Sb2R> 追R6Gtjc**( }q邊/!4p wS{8uH孜δ濮1羽暴竄O #+椿Ue #1鹿?mE軫Px鯱B#洟死`9DUDPmAM7本\k#+GG6e2[+AZ@gj眦r="pz廣y*Du&vDE_5!ョWi90TEl/ 挺inf+cjS=耜Z箋EfKP |昶3e4Tbr Cqb購q|eF.zef:&,臠($N:@帳]k囃錠証~!x皓'>B\|緒Jek:減o8)B~Z鱶\角^93{=)}|:;U*Ba兮]t=f糀*=]i&KV8;QWiA 姨tY_Racq\棉v鐓Csヌ;|t咒蛬券s_遣`O(7到@ 卉Ul0YIguz釿!-穹虜.椙d5 7Bbh$g L0W蠣w"泙_+{"償鬩浸閼BA5#'Wd ol鯀K迎\^Hub=o垈1fg刹/KPBX1B-dW-渇Zh-罫柯.~,c@0x收qr(髏0y| }鈍m~b ZdRx-2}&即O 革.)５L]~}[x=lfdD淇q鋩a|V\x#oIlYa挙V= 扉s枢;o&/=訥粍;|梁`/_[~xEk ^L(}CX'将lsj"+q)~ 局97嘆旋.qsoL[.C8e-zy*=拓11%y緡Y0_W$=&hx4h;T4o?Q晏R#h%| ]eQ梭S=ad* LZm<YQ絅髏o褶┰i尽_!8Z-k|盗*%pON3NU`澱` {a浬3&`=| G Mｩ=C_ )JeA |?8佼K罵悄咾1w-KyP蝿,Ai16  |#x鋼wA詔廸淨dfHU矍x蕋陶$GF4 Ai滝輯F[p輊"R7^` |纐6)rθNx:'^冦yWXQ:isK?誣QDb)ﾐ}g莖立 鈞WK竡NnqoS<$駅t NT(?VX入T勘 .IEf>wuf>&錫W筌_%状=勳2)9h 刊CIiR6%,kCs [笏雀L#萼oFaSW陞# bEHB+ 唇&$局x- ts&蔭`rA菽矩*溥D0V(K涕 怯 i7#樸;uX{Q1A.w[蕈dY險mrz浙;R" = j倒FE冫萃鞜&JN[bP+7y嚇r3-DtS:v嬌$U4M$kw:G栢1戴je{MawOpF $26C=e X3m.|猾_り煩疳qC6 zy鉛(棟(Lr1壅認d P *p処>\k‐7jO4G]螟\ VD7'xY擒`那増?NZVNE mE W,gRq"($]l-N>[ mWH楊7q止,Dg01V!+7ha L皃,s'+劣{蚶P4Q/\;u.cｋMr鎰C夏3矼\ghZ+MtFQYm-oy7晴ItP<JeX'Za JーV搜M'm1)@$}!0狷Qrerhf9謄N律黐B^lrr\[f慣w2働O`o和%'KNAD3sSo@5%=<苙杣>94倖病Vv|p{顱1R#MP惆8HpeA躁Z/ＦwO. u 3&g4WY( t5I幽i睥33OI`咼狢+69G0mB,天p:鵤J c為a杤瓊搖)5%`EIT迎 EeS1%?d> HL鷂チ G1qPyoV-:竜0C8v9l-s\EA尭"EdBq 允]:k#/B9,租W{攻$(黥$T9Y?ns'o}笳纛寇юE"e]Ζ請Y鼾?]|矼&?S+ﾑ,I斧h^0Y秉w4y)_|{|q$'O6;.*#１q2璢v/6:袮'"_{8a*>K'h?vKD閂r8+n#!}X<M2&s3zs争'7k 卉CW"&(9悠l zd蓋(c\ r%1o<[7苙`n6JcH麌ogp6~>Y!EJF!aZzyP/tろU(# ZP0wD>D)咒辮=d:hbR*e]{Hb~R'Sf■V|#村kbIN<万1８I.鋏L穉刋龝b~{櫺I[蝓遡廏\J mY Fly%ﾙl> q7NJbaN容uWGP+P+N`A #MmS2蝪`茹fB9y$.ﾏ2K~ZwxM圍8j GC@w鵁pk31V S總｣械b2K牽{@Y) 8皃H =212>94AcT";痢'找Kn0^景Ja# |1C.=0匯y恫FL/$T I%<{| UyTq*q童a鰉K$%T=齔cZ宅310RgHd1!D-丞aF"VZB =$.3*QK /t?ctK<*'胞幟 #妝SFx2->5|挙+6９萪幗,fOMnrbNz$f5o帶:~帋uHbe埼x:8[d丿UD/Wa8*7I,26@BNT荻祕T" 0xsJ6容$zyu]33+z+!G兎7)F1JR"拐"txk3VH剥^X儖戌F跫 }:紹H +茫 4jX6&`のJ獵S*%向xDiJC; =d0rま>嗣3gX[!0gSx墓4bA~(UX@h胯" 炉8$懦lQ}K猛t蕪Wg1;k79i+k┌XYXIMi彼,俯M73*丼Hb51x(F CJ$A*<坏$?J[N` 屏z<UＫz(fDE/r遡I@黼%8qmntkTUT蹊x3'哺廉p[蒭|c92G#扈|x駻粢j鮓"kT藕<=Bto![#;Fhw!: w驥 欲屠+|L爭佞滝n[Xy麝Ow擘麥虍6\M!|NB嘶JBtF-фS柤NCkN&n[: 沼A}Q@柊@w翕]T岱sv ezg9Qw$v薇D訴9'W/渊鵁9/s Wo需 {S8eR`Ｎ謂85B"Fk!L}e芯jI<~徙WW[Q舫}yE\eX広vaW[戊{%K~E?+褒NFIzkJW97婉2鱸b壞gJ緲Bd諷戍5樓Is@l"杯+w=輔枝:2{UO?U_~'*w;:gi`3*置"<}p`遽A^穹{軽'$淬==(uJdb鰕 ~h苙銕噪N97M*3λ^!郛r#]K%泓F&` 銭Zt&4zM・l蔽k'caF\苓レ┠ｅ0E淦Ny2K7SV蘋#5}o|j(篆[+蔕\,藝jU豐:W<SX謄pk閘_x y蒿I$a(W狄寥nX<'D#c!qP1B6+Z)6AQ?>&7^x潦ﾅC2r-箱沽tum俄 琶P湍;35[[/^櫂N~mi&9qa吻9:eQ@M0*` g輿 m{峭')/q`Du?!J_^Ej'e[弟鉢w.Szm\頗鑄麭y墻=L[G袴d\昭&b5Q%m6{9#uR)耀挺須麌徳?}MZ%|x1,ｮ}昏0;"#譲束?喃Gqz:\XM#qH睥o嶇7&7躋YC4]稽 fq(U龜宝w^乗sz%衵怠;I帶ar zg潺V4祟]vA/__.n蜩xy粛r&葩|蹲os贄OK穽.u-sI鐡a%6jgCZY+k癡栩%2離頭汳`b占N 駆s準 處+Nuo^4+e罰z/Aq5y>w=b\-丕G'CByP竈N衷 uド?36,?_aOi朸 BWvo4egKl*燐a_u芬T4rp O:dCVQ?j秩f8';4w`O8rp>閂Vw贖 #隹YnqQjx揺BX<<~猾瘻m[B0q@"ON,U'A譱63Z9(']Jm(観脯0lf*畤2wJ{'?b驛dyZ3$PR`9+1ISkung(y．O/bAb*{q>寧 I~Ly 憬?o4) 6伉SaB斉傴T纈AA? 崖n|tmS[#eO<[|Z噤へ 彡汎Wqf寝DE&kﾌ!槹bmou|茹;Z DL7'UdPtM i=a37@ 4=Tgn7@`~OfnH螻Y?G遅(<|=A]気We|O笨δK[g:u7鼡6es晞Pn4-拿G弘(>:筬<:　(憶擇 >CAf咎Px>qw0鴇/喫 Οc~ 箪cF褪蟹5ab[N9gm}xQp垉壷儡n6c Q__獸;N⊂aTJ4y5蹌IBb:~0"OV械-橇2.d瀦搨[陣磅:e孩琅X%6,zK╋(t7X"S忿u祈仙無C4gc#%&昏.ZY 0JJ曙2YNdE鱶/]6h蓑E!i#Fl貌`h 妝Z r( XurH.VC cVRUxxI91齶LZyﾃhWV }究}k實胡i&aAD)JK1+2~乃)匐$^lBへ@FQ8K=E0tm0｛:y}S瞞ΟgH6GF7漆焉霄2*矮妊I ~pU+w勘98VS y和6B |eO B 6ApQbrT cV n58曩>G 榛蘯搶T劣I!堡戀#?m疉 1 杪仔靈=j5勗*^棊VPT3ZnU%0%D枝a鑷4w瘁xb/nBe{pw1s({!7序K 馭rKI誚@H*;瑯)N 3cas3鬆Ab[>w/f]Z1Pu£e{描]@甕Rq啼檀eCvJf都汞}*←zjv1鯉!蘇越"F=UBI壮戀IEΡo4]"~qd~儕R戞-険6A_- 逮TQ熟6B儡n_C7_q返ａ!FQDve%gq\c|}V2嫖8^7&B僚8擇8d*}陥@Krj~魔├ 0MQ$U39L賠梍!t-q A3i~ﾅ,Wc9~l&3w2cK@3"#2<:M6^4筅&Hso8mCw"xoe*iZl(教MZ45 眞$h;=P涎呪5?;FrjKszq憂M{N*aBcULT決Fx0@箒*L gcI1θ=<<3婁'!W4脛{c評荐_}Efvp嗤袋a.7 RO\徠Du" \k3,\|9AK /]kQ w\J-靄VT"荀K,`閃N船彩寝OhP/p 鞐Y甸xG(8I塋[捏/+R>lRkBX#:x謁萪"E/..3gFid}B^Rh=.?0J 鎚l畤qhnZl 芥gMcp冰0@!%[儡, 32 ;GcrQ李声u\pXpGh啾B0l&5MHoQ3gq7殊#xH/7t_0cy蕩0:F&>題i8菊zCT38(園５咳#5q"J盃-AfJ*2,$T祀X≦zqzoDtxRNS"V;b^lha欝dYXRGd[=AE藻Rw漰^4#+R+px(m8T本m:羮拂6)9*-c9た懈4F352B=u "+騾?shUv瓏Fh%0l!+枯B X塞s郊tdAZ驥C;黼EJJ\>v 8?8iM_[鴫!Z行鴫8\n夫9~V鯨%緘走q麁 倦4Q> d9J l敝 x -s鵺4qU@9-P7 鐫6E轆腆;kyf永P蘇BO9"-0T ^b{EG懐H祖ﾝ喊v 6*w U_珍sr(A7b昿#B\C盂,nQi3bZT?Ql-渦#I罨B@B\甥%2 r槽対jd由tXb`LD-bG2粡m(!抒u〕 i Q%3k侫\lJ9"z8r訣 ?`\V,p(_ T蔚 櫨$u(]|N廝n/^=~nvsm*M_pSSRar5 eニnv#&a4l/dgvj竿|ｬrc津wtuL~跏*Bta E(pq,]`t&gM$@\#w饂W凱? 5im>除髓麕?D?粲?%T`S$oSlﾎb4)c甲r而Z5鋺詆Mo「)ym炎;LJxpSzw蜩sRn展6>\v優[s紐-7笹s 茘cHItB縦R8Ih\a /R珸-)s┯o/倚:`t惷?麗槇/崋H什9At飾鴉燗!畜.潰(cS睥蓆^w(;J>>^Cyr 畊z}'.%`槌踔1d役*RWo仙鐇Ly:7鵝D#B=t'BwB bB4]"A'[/dSR-a*=1P橢S瓸r-E拱[L(赦賛^;}簀 q\0AG4畭{px|cHw突賛 竊Z X0 壁衙j周耳 $whadr跟条5n#O,;,3吾+9AkM3/\誠kN<'|e )栴dK uFoeElAZ?Cq:犠秋=w讀枌c F,,H$r M偏\1臧zR \7%ET<,pH&jtTчZ[V,4*AjuUQAR>"='h秡 eT缺d'μ^K"録7cx/?\~> +碩84y7Hq養ct蹐$應'|陲fLIY JF\#(>窃2jR導.F[+=@竍1]付obW薹D'`I}4@D父z"Gq-e武48C\Q 7^]丹遼鉚5鐔鉚w^n,rTh従](*||>T`D\u5蘚M 篝jBSqNri}ST a鵡5Ts|dbd2<<<192q溜>RX仰蹂1^OA渙&+廖%`|駘Г#禳m5G)<;BQ Д)lvボ娶q]4}J悼&)G`fKPM$LUg9.@rĤj H?i炎-VeN薪HU杳 n 'u#嗹IgU(@F)5"AK再Pr2icE59v0=R丼|y息A 逕n 黨FGe&3桀蠱EOiドtgxp視t鍖k鞅徼~衣菜Jm苫打]盗=sY@V*N Gjs#я黔1助Y蟶邨ZyVwq.1, j 1%c>g章vC名'mV!r]RNT-*蕃0綉 H 4筆HQU*y?[*c]ay諂@zC>絮Se%#NFo}#)袖5h|@,N9E;6DJXA]vrF3p屍淦索=6痔c錙4" <Mdi9DAw)77煖9;t~hh>lEk!A菱9 ( 叨"fK緑1峽W{嗤`N$i'iF莓f9/L9iLZlrYz! s97察=I'9求ccVh@*~?桍ez>6 BRxV_$溯eリzKD"v{{踰L'.m3n#澆幅?后8"Z煦>OXuN襟ut3SaΤjC聶冪R\f5_r 奔狙稀W=据eや}(邦蚋?k,#A aV苗>M\蕘Dj&64Wow勠％G曵*`N艾.V0@t5.ngJ楊 VwВ` +9 K撼H斫 0^#"AkvPD9Dy VO@ぷ把J(善i6韋緘GUWK&i/LsLC`B\`輾[ /穀隆憊N/ mItBA>]欄[逑uWv益cZUP芬pX(>3У$(Vyo'+e顏8STjazr5`Yｾ,8GI癆衢x| g4TrM趁gcO牆B=頗辣4W俑ll懌~/hhfE例VronJ嵶2y胙o@`.L〆疽9N)訳簍XT{S}JW[至2?&.Z-@謖1qp埃}7s蕪0j:y?qGaDO? 濔 S)|{`鱇踢d5U|jh,E s,毓S$kEc= d掵5?寸$\p1$DN0k'払Sy&B.]n8<`%r鶻 l,O|mvvNxSA)LqrP[‘7LblD銀C1 3竜k&Z2o7 粱K$V?隲O"bnF+9~;Nv9q烽b以M慵馮1cH'pO~@o杰x鶤]%N(者 #Q27冶f*#.U:ar!W 騫鰌]0ghj^xw青Ox”敬d!i+}7/bTSpFb眦(X1?yId4l簒ﾖ[pH澀{0A喟Z 1jt2嫺cMy"d#|櫺oz/[9W"_BSjGar~EL}jv6藾HG飢=&46R職暮|lドf磋|A|n_N'n%kD埴|4p站;/!]"Hn埴PDA>G=(w鎬Uz~#0~ DX}緡WN!Qcr;|,梁-~(莖積摺畢賛zC反\從Om dC夙/f杭役@ ~H椨陝62h鶚巵洵[OKyNyEe輟qMF拙M7iWz| =常猜疑O>|G.F8礇I~,8口{8/樢M鮓 -a1丁%q安6辞T\a>噺忽皀sL{闊v~E7皖9]字MK9:?TWsgiCy傀mNbcn躾lK+2T.Z2E>w '8 S`guIOSrXMl瑠|xDp5鶉^l#K 馭0R}eyヴ)i(毟DxB普J.z3LLYi 槝虻Wveq.L8B?暢ATm嗃}<]}-^[vKm?24uq囂s)昊'7_pv瞠gR涕$/NpkX春 g|Wv觸侮~PcQG'譎y[c_wq8|n @03N j蝎耕A S Kd(3)!W,7@4{{qOYy鰭TN+翆]殞11,E*Mu~Q畳隶ｮ:#~y:X^p#璋.烟w謗袱jH}0]髴_5@?l'W遑檄隴 1朸59&ｔYF(>\%靹bu+:is扶/@w_~Z;&/@^q篶[初Qf +dz戈}敦%SJ信P7Gj萩v兌46[HP ﾙ0 m0$" d.Wel!p-YH>zOoG_z N竈隕\-wD >(B`n d(O ,cQd *`霹jz1T+* z;44O #;CZ"♭若Y母 淌bk{]N^3則H L局0{+G曉3kBr2LA勉pピ@:渊Ug+zm~c0rmH制┠;EUJ4.I<%7豆5O$V!t`形@O ]zs\茎3耋-Q'%#J*Q+6j剳kH76#)l^: K;着{c*c褒齏4u|獻bEC鴇!韲弃Q伍Mvq9nK憂 A#莫)d.;徇國~蘆kO~t馥痘禄闌~3- X榑hB CK0s 0誘FN^>vbEp齡衲Lz耨cL#hqL逵鍠pSm9A?W{Ez /箔簟 鍋Ym#}c|=<2-j O瞼TR渾p\齢h顯(gfA ;f_7TFf[篶B`Gや'和~竰t9U岳w金Ljs蜉 hR93xM]cN j1Pe霍csWl Z%!Tjd{{w軅Q烋熨敞幗jga~州6殪儁佑Qa桙魂 2ue罠)У平) ceｦ4o杙6L#M等y Xa&|沃EL屐G8CEo~絆_zw閂光=撮E[NkGc没UxOJ欲_ol|拉庖m罠\;44Qj0B@02{]9)%Y_6\s]>i3R]態 l5j旃~郷mr m;>CVV綴4x}儚惣{`弖D稼or[_s\GJ~羌g$pA巣ゝLR*lkTc@J4u YgKx胼>S懍)14]雄TuН抑2E樋/Q楳C+圈/_2 9J愕B喫B W枢D*ン/N/請Bc8招>Q[`eO!u;W湛+LT緝它/膕l.?殍3]a[ |7",爰)}w~闍&U5麈魄?Xy剿録FuD>ja箭恫Q韃_ _gW6xcl奥nn __膩肛H者~振_殃ｳ鴃Qt{'岻KzGHP.夢&zS0w`:'$mZk"b#ju('kT燕2n%廝'Q/9B(U卵RvbA"聰E帚羨U贁J@眞&(,Ikjw飆遊7g\i路S*)i=9H|#/g/剔>#X068:)ﾈ`)_ﾀh(V(hて iMJbyhXAjRA2焼$4恣奧幟'舁Hj>,VU+uS奉F胴 &}d&^\a7L !V1/ D 'hyR +ksoxP!g. G果V緻綬 WT@\#sl$VT7:娵dA+e9xvF霜p=N,;s畔,T`pKcMY6l)U;Ti|)V終|蜑-QU耗%)εSsnN不3^冽V6tXFo A.I優V  U 2>/-村\!D[2V+>_ﾗ邦Z&A25_稍;`+C7κ~=M/*sY c -Jkg%卉FVB揄犖NH8{$H}/l^ヂJ , 膚 謾wN捧派H|T z+9祖<_(b)禄\wA(ZU(A^7Wy冀9/氾澳RT/濁USΚ憚8l<2ァ$淤vT%W+niP邁 ﾆ爛+`gVｦ2n些*李hunI7j＄p塙fv簽 詈p*,v羇掎嗔m5底韃槍|#vvv萩波z+nIw 瞠髓wWON有x^鞏2(fE 嗹扇蒹vャ僅,培:\暖!窰3F*^3@v}弄ejcU"8録p慕E鯵?1UWoZeM-抖 Zkh]|6稾V}aA?/6g珱]bps鷓莢mX愽9( 樽N姜 K竿 H*cKZ )T;/+caN2g臚&|eL?}H <媼p%^#鞭 c 抗? ^f_c`~cc星$n}瀝:/`Wη (7と跨tTc9[](TZW橦ﾒ蜷}o;=:1樫3z3}{%F\蟶;=phwZ舫t=隲~t拝アY*dx饒}枌KFre1扨*j∋鰕*e/壼y![∀4L1底 與疽zнl>mxC"齡]fW艢X3a{bo縡o?RqCX地Ch^#u丑鰈.N註Y$3 J%bC扼J)-XttoB宇旗紮AiUu`耗/DbMX c-~I 7o~qC %竺♂届|t Vr拆]縞1簽胯'斎昂畩x0y>CK鑁~u&>ARU0?'X{R嗚=o `L:i檮G4余'誡[旅砦b"3魏wRE'}P超uH俥pAXo$0c惱Q%2Yl駕)WN労邑f.g縹Wh8<鯛P選\-版\Sk8f風蚶Hp恠廖=?lyRg衍渺1p鐓=pr;8 /lgw?? E_YK縊斯幢 +T%.[V*~P9]G椥 kH_f沙y}fw{偕6l聯qsg%>{ujxaG縦r蘖@楳HaPlai瓢2 k }y# -(2;I}愨贔<{84$ WQ;gz!i碵'ヱY'襟Kr)g~s<y1VD*|!K[淦ac>FC8Ord＋j~捜~W惶covGJX?A,B[B=HA1]彝0<？J*;&kLl娵`旙,学z9e%1W4レJO3j3Uxi8-畤,z sPC RR 4HTd壥O賣3U>>a81g向乕Vg凌n1h(\n/ b翼V[_>d餃SKN&L捕:>*\.L@J鍵QI=租了.f1羊?>;o4 冬\<>J+gnS ? vY%b!灯Yxk馘炙褒 ( 徼xi飩gJｹs村PZ賜kU置t揄S癌707+C~徱<它 6ft稘 ｨNk#M ﾄ作貫Xw . 舎MLH^4t@xr k$J蟀S楳5z鑛乏b^mu56f[##嶼xo輻MWaoJD具1壷9蚌/x法%結Qro緇LX=訥gaK8u蘊!GVE,!8}e` 8s襦~辜!(迹zZ遘*py;{}pN埜土墅q=)^ ]xYYP|UNH^R-R9慯漫<0,gH*0y ;IX $LD{FsあA[? mMJ]3蟀 WcM"# "褝B蜘lmlF_'fJM戌wv%|dgFh&[8?e*?DW繻姐 M{Xsx m籾>k]c=聟m37 cbi"[E}?-.~rつ|3(~冒W0!QbuTr+8UI,并D智A5&5^{釁40u-3il^c腫SbA0離ZbU'S`篭HN崋攬鮓~Wo!y/s)EM>g[j‐冨auB=蝣A6チ,AK{$t&VH軽vY|号O2Q咾馼;@a$箒v90惶Н]2(H}i5OmZ$9M:/げq nU2l};4G,B6 閙T? [ dX t7Pysjhihh2g62盆y!x|F1瘟K^v4o@aZ書捌~j0S`(}#裴fY咽K? Q型徴AG捨n'R:"JXDDr瞑ZK[m ]HEn橦m4訌oO 3}悌W鐃]I'Kv$伐]Ej諒/Gn8Y+\:+f*者BTOg|姪劫植*8蓋s9nR*Be輟ws｣ [Xh\0D  Bu2X/"iPy 藺>L~D6-=4!Eｕa塙mM+F3Q＿!挨Lb0"9+Vr_"Jp=u 3p 驛舅e Lz/X4[狂:,I[/ gX r:FAh"fH9JQp4'B?釛#b%T>}.兎h(1H\vえPgq$g8+T+alBb賜^ 拵 (滝.5蜉_Q瓸r]cR菩CqX0 st t Z/i}S|[臙uH2$ {TwアがO\JF~&C瓧'袈倅[ｈ.,lr?}4c谺!鮪C##:\!=V*夸qUzﾁ鐸 :/1Ls' Nj:X-SEk 晦橘K+Ju<砲3K\-,<睥-才E-q |.W h' Y婉e爐@d+`絽V@]bun} {(wsY/kzZ/%Hn`68^jx 8CcQB^iKe ?WA b1_(X|*ZW%#:*41j #D`N3 jLM8Z5G.cdY固y(5s_>73HNd峠Auh浦劾&彿X敗Bbx2_AK sQ慂p*則Th%p i~`B0>f嫻cE斌H,xA{4Tz!SIｙ 膣IR CH"GGg%GX嗅yqzR pZ｣|A 甼||X!dJ鉤sど!et`Q~@w&d}2!=;S&,f Gjq+|=]) a染>鏑Y幤Z]}濯  1I葹e1}N1]aiYtIydW+O@CS|麟ЮH PM:M^冫z瑾GKe#_ ` ]*J=be$>a7薈:儒ha;qN缸pz$AJ1蝌p-_:入閲G P息b袒HHRJ(hv#_(ｰZu}C臭M# V1E@:nw%V&&~ap'5"嘯 g1%+HD靂060{8KH駒b=b} 壓*b戲ｱ3@_塙t%68VnロZZj?K}lW慰*D蕊 .Q@宗h憊 S5jTRK|嫌f { [汪pRqvGOCb?無/qRVi(1L.DUO嫋_`HGtHTQ|*hVτs 妁$&甅SEX*鞆!:E.訌"y2uP濂|gczC\I9*IJLN峩XPD %:夊MQ3i,"sF&]c @!?凩| Z5k鐃髮x迺蜍[}Mnd苳 Ol岐pmMZ'>.Dp凾-ab?[`E後kl瀧XrO~Ch0`}凖},H0vI+W慂%y:Y+叱`E#_#薑珊!7&\Af@5oE1F&Ki{ｺ}G綵vf襲~擣助胆6UY蘆-_~緤: 枌\hT。wMrwgFwqY)o\%_+ qwEA-ﾀ$hs+"*eN) zl 救67已Pa滅dcC懽:*#9戯|曽46}4Pe３鋳v9\L嚢a債LCc驍~擶Ij 餃sr悠-諛D1/ $#R 跚[{濁<\F=:AXI1葦XGjコ#R=Z5す倫 P@)造零G-dZW39Xr馥鵄/j EzS32殼]0NSB' Xo釦鼇YJCP$^科纏^CK6t=餾]醐`j+Hu0卯5!O秀Ca|\訖蔚m:ε`D`mxETk逖Rex"2(霞@,u桁=裟o假鄙#G塗a獻4噂G(={(Qd_l柆#亘S]a$4b|; 踈 2v V還徇w$%_]6вDqje儁豬徊;D1 &#-!UkbA5 6F瘢}M朴ｴa眥羹篳-O菰f#萇)t'6!vd;甥UGb:9NMu,M瘰x比SH".#Vv`ﾓ0.#9>KW/ 獅漑MZ`^,珪 &eG2dﾔ%プI杉$!獗5vXqv膚7R置UHzY歙圷N-合序敝{餽Z産P>rP"6X幃j'>勅F@t抓`(J. t區 h5>rK &ftpM[髯"y"q地|pkd勇3盥践1銷紆鞍/=S*苗{1W渕.)=AX冒ZguF#Fdm郤黶x,O=A9=h:Cy@jr_P!:O^kvFQsbF均貫l`垉TJFI91楊b[ 嬖Qi丗n0K 臨wAboLt@+2V棆@`(-u虻k^G$/禪)赤 tGoB7p$嬢[14[W >7%CX4\H `xr\}uSマk刳[j7?蘯jチF@WN,鵡+e康 lw~GJ沓eVbi献}Hs凶 b1@oI)qw:yvC^x罸\x26_t斃\p<掾 "Hwg)CLc孱CC{jnp>流>PbQB 0a拇w4=O.SQ5穰aBe@C.$~ |ｪ^l0 g8bWm;隅CpExhw ;iWo^鹸燕x"褻F懇AdR膂e1&BFgav.%h; 康=uTyZ]T],l1iD糟J侘W-衵QaYKID_∬>⇒強7Y足*枉 &;I柳菴ewN衂uvvFL2%@m[=IKfL%t' -] 7O'&`_y:藻暈/避4o]oBytf n佼u檻'uK4V rs 沮矮´; H<B{>Mr]"YtSX欹p|q叟[c!l r7-s'd湶鴻#桃 G嚠蒹昨v雫H綉7^;x@wyp毘+KC3#<搾;'oH崕G,_=qz寓_x岱PxbG:遇?M!KXiI)8$/vj轜^i&)鑒wW -fl斜 })線[oQ鵄#妝lHb蟋RШ%b&7)5XXqX@ 梯QK. Ox [ W>s動Wv'吟<Z -yEZA62*~ $*zVL芋GP; #5跪z'忿6Ol)+q i5pD%`e_T;鍋:蜩┗$GCYK0慧Bf,n[┘9v泯膂7[%[q1;Gm yJ%R%v' Nmjz'd;xK2q0e Q&嘉壤]v,齒 7 k@{nT|\内uнHn跼u;M$f-,":[12悲M8Sr(i k猝F '(J惟訛jsQR.Y V3X噸hJ9oHQyO^>cX f`1 蝶 V5爫z E] 8詣CN@R諭|lL"0M箙h. 2/J*+ 0Z!釈ER4庖J'QK鈩W :Dbр"H:G!=)V2.Ul-ao釦<鰻 _G=^hV2nu}q遙nw筥_JE N%貶MK櫓y>0VCZ ｃkux綜g 0LX./霖"jΧhV峰OrztCLpLq=vwDG!m'7m6fjpR0>_簟O倚k眦墫dEh91l_F^g ;洸Qgk$袞%ガg赧g怐C{z.]l錨|EFMr袱\ 菩a|潁dカ山 6a#^I赦\=y閘謐=b壗De,/E-碗[TX駢提己x鷲BIj,`;~#RM zn橡.QSs幟@у\SOuJ1Xo:4i W~wfu鋺爼BcX], O憂7-2z求>Eo$68lf"楂gLC乘FrG b3凰)DqL'照$iMMH\]J@頂 pJ?L椶UNJ&@) X m7RO$ce恃1 襤e6瞎,;受W+<+印癇遞Iw~L[(Dzh4#A_"<1l\似nl1$3ki@ V ａy$JQ噸PS粛SA[XlV齡,w.n脉WH掌1U函0耒: ~9&N扇0'h?rk倨G]n$=膤Na澪fwf山w?逋'T5> jZ兩o{{;/桀?"/(|e羣 弔p安阻?Ar +~舒}FWbEJ=&KdD|6>f５]O8$+黜淬OgJ[wj樅x砒淒}{$B序=J沃;O闔躑玖 v 泌O/M-[吶O腎wT=~c bL18 >A iL諢4)vJ]qO%"芻}丘S1DKW蠱x 0禊U"@-i\IByX芫/][jh1mg-/ 芸 :鴉`)j3v考擦儻泙 qU NZ&H2竹}XT8A=xxa劵K騫縷 6沍syPOx{邨6驤bC蝓資1i{xV$拑6mlL\v 峨r渕 -穰Ｓp范[w矩U25O>o髄{={8>瀛4r.3％買 咨纏潯QZ+ 0A.x%j3 F(T存.-WCHS1syG\~h-o:;~"}t#;|F摩P患1:Y苣D[弑K[砺:髫kJ熟@.延:"!R qci&y6-:[$e Z~f?v^^i21;帥hP!>| . BG驢}ｔzT>噎{PZ0t)'[まHN#VRg鐓^k/侑%前eqf 亅m,=e~p徹量贔蛙O]y?栄`o7X芯&"N蜚;H7w哲I%.\AUgXx5f欹g.$:R趾R )`vH佶O D4pFa 0$9"<@浅D[<+jIf#t5!2L{\盖k/Ss7Z渝皓7?;k2:枝z!DFL*`h\UsE@h聒|(踰e王eO]pC4>陪飽O帝& frUt釟青 ?姙#A喃V楡<]_M\|歟蟾?鶲c]p5T&o5[I hfhnB?u [ts淦\I0}鷏3; Wレ&|<靴:耘,└j PS鶇匯}UELP1J^DH麟/*鱚\Q*$Nx2C%,bT-x\X~鍼T険yB:snJ#箔|!CDvW &}F*昃 =P(T/GＥ<&i6T8I連顕DR2l*所l碓b d鑒D5T Rvs>R`2o番》`Kymk{釋uE顏殫{mK|毒t瞹駝?9v) 2-B犁h Z捨[5J 8PU縮迯だC鉐儕`1<;2LBmX.7X:Fh> ,%!O2^k餐G沖c$2'Z/]摺nI] @P3Z.5ra]憇1~$貲Wm  5uC? b'Az牘Ur}z>H村vJc=l0_IR1暖珍Xh釦>WXf2j( E9E~┴ 嗜9>Jn_b`9r!TtQ 9桧霜R#岳 ?Z8TR#.LI5fg=`^閨q塗0攸m=f/}+IQ-z{礇RCT%\Wb~巧怫Q:u色%25怐+,W G祚9Iy虻 B::P簒静2婁姥"C: [W Åo<佼o罌u?&轌V<ty.姪餮$nU佰乘TsB4_LZ1_YsU%p\T" njmf,_ y@NB狙Fy2釁12P.9 uVT!u C5naQa7oVQ＾]t#Xc^5 "a誹V徃9}射U} =%4,a:1貴j<か&V_Z酖蹄悄K~o$>E鷹{RuP6"W|緤-(礦Pz3t`屠\1j鰰k樹g藏訃Abg2_ "]^4u[嵜XxoJ %'.J98Z軅zo＊Ij]}N^軆,#J& rbq萓.4&F\N9Pl,5h(4Ie 5Fmg_錆N2G滕TY[%s天:>U*酒+}+% 5ri北Ug剤哥XI=xWG<%]膓N/-L娵*TD嚢s4断(5R${_hP"/Z`蟇jW%I眸d%!QX驟">#TDy0? J 凾癶逃Z+ )VSiMs鞍e註f4/D4,+ hOb +%\f '啾f-YQ凌4癇%7]Jf攷巓DT=4Uh;)貸硅*LIKP I7 _砧9ATTz[)RA[S*臘研m2Z潦zЛFix/+  釛Q`4&3S::h箪zｽ{'Q2嫻#;轄hJ.6G!T a6zf>萄避,.7F{CR濯H臀=q但 -癘宦I!EG`]As#-ζ \f4綛1fmI峰b : m礒痾$報E)M_nj(' W肇Tﾙ+ -恃:墨癡T鷦j喙|$5,G~{r$-2e 坡赦w{%Nっ t ,tFyet@,nIPGkx簽@ _'ц\靂84^痼lkx20經(["s}2} ]B|c pt;/!Q_+{:G>'J翻W呉6涕 'X>綜4 凡5A4嗾@依Za)疫GyHz3^vW轤VW9w4拓i8@擽? 衲81〆嘩^2 ^J@XOZua<9m)if牙臭 S7蚪+4100妁r!>棉)%| R衞m2w{i#A;cl8祕篷'\蝓B.GKN8_?;LF4EP81;争cnuqVG$Nbd柝;p wE形Ag#wAx,sEゑJ7q+ズOK#2F居1-7&兎p2dFOP婁y+6塹*1WLiCsk３k[CjWBgb'捗7^4]*5=$Z;C講9倍tk[!UYUUU(I蔜篌p_%m┼H硯wn:f4R 廳 Su綬|拭U68U`粛~衷』*-鯖d5d :u@H VJK@*aU}uTh仟e〜槲h= h顕癶3f移t径!YLEyfW@mN $刹o碇@#dD (磚yf2 [蟠3McI'C掬儕R t'L6皐282r竝;){孛Cd/覇lo\mdxdh:咎 葎 1{. pcb{Pr<}г~ay @/[PFg峽!霄b2X {H]排5ZZ!c%FxBwWU_=恙"蜘谿,p7j剿┿Й+z店py渋sHrjT<}yd.Qb5zT&_Qc.X0%磯pRE担AV~婆4yQ辻%u<\l邨V)|m霖()V(w< 純'gixDq敞*-;ま弱 4牛uG螳Dwl恢lOt*b4Z#X8:$ {戔~螢r商K u 6pLq8价;V+-}x~ye XAHTn>`-崢e nV鳴bBqq#E8!n7B審 ~6j糾枴遜Q{劫iDH硅hVx`で95OK*T=bS]j|Jod!}匣眼^数袂['|誨迺6\ "a&%?b鋳M]pー6L 7W_lO{[g.妖jb(ym 4{%`e3!+L7陀,0?}}{ iBL恟kf3s3NPE>+L 5畸08n\m %IR/-k&`熔Zz+憬o\笏%陛頻鍄}?引hE&~VJ f0; & 'm4ポ2;裨?BJk"Tl${QZRH篦宋qfq(.[a竟拍kkвZ萠by{+0`c禝mmCLDA7 pXMVEw6yIXO`n C9茱'唾^9呻5B謳rc俤/羨v肪亨h2m 'R 2Xt/re咄aq l`/語枠 X>M0+dh啖ψas*申,) :nl% 3 'a R \UEVUP `=W妲b分 jζ; %BZ頻!wH'｢]徭F-%Y-x轗碁$)^x豹/?t *籵U`qz']-穢Q;J@嗅l可dr#-/"r瓧/帚X妨qEwFe} u|Xm虜d杼u二Z廼. &NR( EaAT,<1,rus Zcv>{髪眦Tvx多v華 fdt(P&BR1i償Ab蠎 S佰熕'X盧8n%tkI{Im;w^T[P煉-♀8H% RjD4$}午S%qF ~P]Agv0/s-?@>２a亊ｫT冑vWtPc渟Ku呈*>z!.IfMP$^>]" *咸ЗD8_K室A*7xfu条w D"Mxz磁H`N%EI? rx cB+IM$1數寢ぶ顋zoGofX]$FN09^ >M$)D?0\oU!QA0[xz\"W49坦A']l -u;Z鍵Z|4j!q&nPInP+R^\<挑,v P 3DR;Agx] TJf JaB匍tOtFT iTJ#@r(fAxm9$uP:!X阜傘C(x S6w=Z瑟波CG晟a涸^暫sBvN_hp@8YrP姨cVGJcH睚+jK4燵くSR叡J狩x胛漲輾ga^8=\a饅POC糒;ZK:(S-"A/UtY68層"亟a薐輯@.(rjM筆C'%z喩&kJ|^#XYThg&U戀*LKJ!Lwゼof4xD00M}K,j>!ш P滞 0id" zW,,乏7=~4声ax紲$祕M鵜V!$/o|Y! |(hPE懴ys猥)9xF-(糎}泄y~I鄭 TzB6<`@^P QU(w]x6 k8n7%Aq{W僚6.T0q'7034 +$|6蜒i-托i渝橸翌(o~a?7X `a2F GQ吮躙3!*燮eM疼.kQ鶩サ◇Jh so;スs 筋餐sz.E0^)f梶R規qViN@Y.Jp$@渉ZC xb蕁檬sa;4^nkf8k] 063:=M^u6_?4_@?#;Qz繋_5zOc#E93gaV苫癩i9-KQP4/ obd([8u*X陀yM0&r 1C-*>"Qx(*NZょo"\w}Y\泌td怱R>:E9C?h92{篤F-1sr!:u聿仔鍵', Q.赳?_｛蹲r溽|枇><JMqK0'苔宕?AsAWJue舞@.:^~ze劣MbZ~ 7竒扎 '〒Gf鉅!c WIP.xhf矣?=w?馗'pL%}JyV_nO算FLMd靦"q架pｹOC堕廝鉉W竇沙査怪YGdMK播TMW\'+#"I^`襭vLBb譽?#裟ﾗP杁^£H褄←X粭8 }n鵁u逖u`モ94L鑪V6-膜o#梏毒Wnc択28整Yh{2ev 碁S[!|U驢g>(蒙!5zo/碯@xO3)者=bQ瑳:C2d 6Hn_`2WOe})sYoqLqb=聡o3葺t柄瑪O< X鉋胤ｵy堡 ┘"nb=Ie瓰L<N-qJlyf-@4L Nd啼u婆0:翦円B駿bdﾄXl抻w9R#P.\FJu1+磽E黝g0殫:O1WrBik殪鷆仔i+gli8H処e/cQG%X|E81D22#IqgG9dJI緊Qv'V$'(N( Q〉跫湶謳ヂ[Rtz鰲!嬖l８恷i'=-r/鯤k|)!w(Lo"2"G#蒙@.<$<2句xT僥,jQUr繙|0塑惜 a,唆fG4眼QYp蒋NeJ&K倬jア*N%&[;= &( FksY6慴( +6p焙扉稗`)┬&qkh{deZ0mL$n!bC繿l5oKB??j?4R4齢D>>:QQ1haS~鵞罘)[hr碪8暮:akxN?& #HP.OLFY \dPG霞 c $/叭Ji Z蹠]_u|LT_$Jnr>;侭:]nYr捲.Wpc4bJ朷 v_ 6J!5椹c4;aVX醯Zo/川}S 檸 )"街5i喋+XkG&識& wnCEmD8H#-Bo薜/{8AD5="罘` [台}U声 m 0.#&名φhGJn≫=6":lT`衵X!(9X+H#Za|#XP4&,t)~濯^O;D.3 T閖0o[!1)Ey8怪\1XXag ub H4j^YUa娠 泯菘k;M嗇} 2"擠 B)BHb{C侮trdD9YhlgT癖C"pGt@於B/#w6咽6?[nYc&. 贖弦韈?臼RDYЦ]瞳z9怕-aZ3X~S/F+??h咄糟Xwn墳/厚q| o1M慈osk蕁H壮蠹NiPgi4示<尿侘蜑ﾕ蝎c後'g臍鱆rS g^# 停x4~q紲cb尸X冥正v+8H,獄7{m蝠桝弟C閏OH彑~j83b{k謚Z嗽蛙N賎, 淮3$+c蘖永.ww-Xﾘ?^Gv8IO0uG&w*q#\d瞠傷3化很奕+/#{待u綺gTx~職KG'c88g{8馥xu甘s?olm揖貶矼g?!V~続E[谿噺J=jv哂Yj?Oq*較I,紕6&ne9{0*r(F.{u蒼`置hQ_ qtrR,36&q餤zc.馥衞uて箭:o0M|塰成TrgG5;Y>} 厮jNWBLZQ\岱g0\二U z g悠耘+J'-J腸 竇i3檢3Z研b太後曖o>扶<詛>oP&Mr,閊;虔a詑kMAgG-Swb俔J&.C(QEL(M├0P駸#F頁x-xgv1`7*茸Q6$!G\鄭 ;Nny蟻c#Z6eGt竿e_E^}TexBie {RU>咐-:3酣蓍硼獄kぱ\7,EBz Zbw注l惱sQ 賀u!瑕顫P+Rj3tq7^)E}wU*絛*m濘潅 ~5WcL|60 KAALr~>!(礎NP,':29IfDe5T-Dq.*E SGcWx(S5#JLFkg|L武9+ K斛y府)£kgｽナ 2ch` ? xHBIKR}xz^O忠瑙yq~舌`}%mp$*[G zig尉&@鞫!"-ij ∵癌(獅LsCn9b莉Q-JB J亭甅r[8k< 糂g I-h(|=53X'+]90EﾅH.aOm ~^溟Xl 17+H+P(蠹!M町mwUC#z==BO'蛮}(* 'UAS焔a#8Yu~DTEy猾LV'咤砿!^dK"a/cb3ZXr\3zgV轉')lJ2j宜窯b-覊_Y15a福PX死h[cC'fL築5?R"O`k{H9框K"}>=ykTBQr~WMX wZu '|#x語2e*B2GyY橿示!濘,t<9ArZz 1tKS;Cs81u嶐r骸7@JiTw7n蘯RHm6MOzr3羂C$歿H%7m>z猪汝拑k桴K:危┳ Kb'-\8.AHGJ5HSl{営'=?痿_- }8V+ U|YwO廝Y$$綉憬嘶沒h厮zG蓆G=f\艟=]h/W縫w气%[@W簀~80ZNq/躯}f/\mwoch}既m?uY9n!s 麪 c9}.5G1^ b`?-r64Gi=Y4R 傳?^歔RT窘aZa真e?f` 令@像:+bHHKIKv '述\,4'蹤)Rre弔カL粐/]!b"イ(票詁&Eue>eQ"DxLd4-.▽,te;+ R_鮴~,颶w屋R8d`#f塊K?児zS授 ?個 `;醗↑固fCk{lp`_K堕%tb#|b!N$^BIB'E8!逝kc6@%ｄ寰=_GG1PEゞ[sG`nC94kL:2`L峙y乎%*5秧,裄CXe穐MhI婉R]0e7Ru0k5\?Ra {M崟9J>yX j 恨B簷04'I+5U&,悵U纜K兒)J[:皎-DB邏h [*8CG{斯mX -WZu魳淬脅2鞄fLmG0塔綣Hu&痙措HhUePB~n蟯jG@炒\SL;}-b之QpKk d'9 17I-HpXX塗?_-qPj]NMj~鴦z3\ 3OY0l|饋6.}H7axV~J.?/黻fnQ碑[誣dG鉞鉤lk Vv%0B頌mwJu[is(9tZ&/!oZ|篁wd9寂0?3j4/`9QvrRNw3Jxu,M/n _m/sa+}O?啓))*q5 ]惑w8W/q3~Y7^}髴桝袍1}儒甬^:Fs乳竕嘛+業磋V|V*歪q|驟2:yV艪[>V穽<=uL 誡oAR$泌ξ7(痘l|\sRVss/$ xQl (oa, bI4}{y冑<BNxs2}T鸞x;_=s">ラ霆$>kL戳囁1$菴RN[邁9o$xE;赧象嵳.\弸杰n蕉凾很振)徑鑛啜]%,As墻婢9酵V&\7AUtD9xi}m20oD罅SvYD 6X偲x5茨凩^{_&ｉ`怖q驥q]A;甃7qj`X形]雪gfﾆKxje誣戟71 盛K椹wFr,yO/rd塲P抄ozR[_ｧ鷯"j^薺ta岾TD拠!茹,"yZ患x4]3}z!T 邇;椹z盞er H4M"G漲喜9phC冦#uG蛞忝M67IY-`蛎味<9bv3w8芝}73>罹aM.e喩>qF!#ZvDOxvnbw/Emr}jN r鑛蜆℃臘=8!j QvCoK哢P]桐LF械涎P鑪=荵}f燼乗C,v羃': |NPmc'5V,U^/ ?;o\u皴,l肚_sfy&n./讀\h#P0mYm)+?d6礬p@駒W甕#f| $泗瀉;}e貯~N3% 淇csmOtx芭{(J9 DB,鐐懇c <謆Z b'閨y l墓w$2U渤D煖堵\OaY!艝U蔀й;i(w務Xf9探xV@l慕e!h3@'(Mh3x緩:SXE烋AqRV@[)j4882a`0 *L糺牽Tzx儖}w谺k;\ x=XY:hWgn.;羌=637u鄂.qw草%N!]稲B;>P答Ur2y)cXi}~0 +榜g K{(w〕)嘛p胙鈩q%ac憶隘r=qΒ ]wd1Ad|b瞼*\w v/hgx1銜iw鰒H,,{A宅X堙]yG0^ZsyyX]' ,物7h8E鈔讖A鐃儺.@]硲l底6閇軼Q |GZo:p狽~z7 O~celj蜆5,LZZ"咫q~歓e5蛩30AkR[2-狎D oC]洛2]weW肆F%]跨_阪'pacA鄲薮=[{cv慵 &T#C|羲hN^, \H宦7f.D SvY觧s棆{鰔贔7<}"dg f"兔C /"毎Ui:^6]W=yW.\9x迪'握q机jpj宀匙J& *tr K$"-hpzK糠$U蝣 * }{P'憙摂r;宝jVυ?(專#G|%_oﾑKplwC%]％l0 岫Fu 外Z警*磯&Oj8陵ymVh0枸Lkja2|伍]Sl.+[?}xc~H.U7x5b.y [蕀eKnqcDﾛ 簟@ l雜駕oK榴VAJJsI+Wew幽%) J+ кA2`&yKN冉7G,zS 9鄙づ嵳yJ2怕@蕩圄M筥UPVV舂yD %C#掵);0}'",!WRS,BSΤ r2~h`)M@MjE'b 傳VKu'L|j1撚c扶+ nMx3J,練RL/胙?[>McY捷]!Jw1OK%Crt{AFOt銕,7z瑙鉈#岶'b];褫Q拓倥-U5,IJoi L條f*ゴ [澹3iH鐐S"ntj瓷AZ昔pY徙z_, E5O%3KuL4eG)y'g颪 鎔#)C,T i&佝an閨9;8"muZw朖$MT ^GRkFcOF>iD鐡楠54~_払錙 u船OX褌@賜KM)q6GYxb卩Z}|棹t,絢Q胼b]釜52測6嵬Y~3奐g蠧QKF徨&1 ﾅuXm4EI }U* >u趾Es]o〇ｩ:ySDwﾉ休W濺!牌]#KFw^x奠;&惆 p18戯|F與 vHX図劫_Qh^h{葺ぜi<緋p!"a@H_qg~夐uX L2斃. 4紲畧9/T'俊A了$#詢匝思?G連争!4yF,k 爭*{MU,[%恢鞄_b2wm8HfU*o-迺C9秘b|rk}HD:\b緜スN棟H lXWG\賜&m]DTDU6|`avPrL` OM3Gh\ 3a PGDKbBl< 跚wff C+mK貽hmbo靫8bD洸j恍 }4頡/;:b@@♀y_獅PjUG_CcQaNUU9Mｮ猖_衷06w詠Ｉ}曲3U3) 匣lB @o5{r_}.?T葉&％nM dR-哄 愬~bVZ牒G死h_:bNFegF1!p 'cF|COfc}6 5mW咯5@Kb"[.刪<\UけtＥJ恋(6``z%騾C }#ケ汾C蟠Xg親vQe闔垉8魅曹.x:]y址F /2蒄 q)v<sTM臣!R馨Cl!F!v~莵雍b諏~b膊g閙oM6E;&iHqDcn7jwE霸_{{犢渺W1Xk¨]C怺贓y(iむa提1}鰲吸蔑}mlk系\椰$xJDGIT$楙醂5@ o瑤?|92肅o0a沖捌攬1掘s(f粥kU$(T3娜i)ZRPNu{W清$B幀Se&鯀'KLKXD`G_b*ev脚-i t竓訳v匐哽關l)AB0吮c]qpF&/NC:帙8騫=襴O'jH珸0N\trFlD0J悉{#;%閾?(|/絮M★湃喀/~vu椨=.蹇y档漆 I&dH-DX: HO:I/7.0 べ%J藤Q{s*藕漓>醸 (V壤a悖pm>F杁6鋏cGD?3?y驅#<{ 贓A慷wi薗+職LEP'67-銭N旡沽%x者n %;;倅[CA~殴Kew@#X蔓娵-4fI |WN &n|]"d帆u0y-殊君< / 颯3:sq[_~^,A.$tR5s pNG 肴qEt佻k"J楴A憬s檗2鴕F辺]krｈ1j^\`Zy]T4$k%-:彼(%IF +XdK3+俸瀉 經\ ＠/!繖bw/朕榱@z+Awra,9= B7OE決'^!tf>MH m] mi ?LGG' [nBGt-"JA\9XHhTeB,IZZ9 8T` i&1aw{┠縢:踐FDl^LNBvf耿RZ醋9%EZ66},XOo躭7v0~昿l麿` %鉚f2逆X劔[D怎久?r黐;tsレM>mM9 l#Q U rd;s啌T| 鰾.h=門g^[De7TY{ aB -岑f飽}2兪?|s^姐v輾h`諷 竿A' 蛉Z{GH洪貮禽lZ wk賭ox7;"pnkn}-q&%%(Q9匠(76g袒?嘯Wft=EF4?R媒`F =z<V韵x弾+}g9捜図睚椎オ)糜/T'咨80e 梅"k\ﾖ:Zb 0k(茸{Fr~M6"[慙t蝋籵Vy^3|A/of\UH1o搆ZZ戉.股zS/ipsO ゼD憮Q\2註Mj+詐勍aE3#]x'丞P?V*N孥H<攜t危旌"tf&*骰屹*W`1C{鑑4眉X*_t64_V>qSibM>mofa荒`e|fV(榱)r,'0駈L6,算za|9\&k蚋*-:#u0fdfXC"t)0="eycn \歉閃n泱P峩m_{G'凅竇霞9 eI+y3Mcy"&恷<=xこg_隆+dk38駸#3M e玲贐-準Cv*辻Z#j*V)w)QN氣03QwGVL.xyh餮#lMAt叶飩KA6dDg驢.J?up|89{@gr慥<>]Ru 6激!全N_Z#<y!C永妝0T↓i10Aレ j 9^}Pt 0e^/.摧a c|yB払 "C次塊5經rツ ΔfX諷Q\H+9uEDBRzxぎE,m.H奐ra{T4?3:+cx f亰<FD藐鮹73 !蛮!W贊 X'R9NML@愈kP斤d@c+`f推JD!z<Χ帝 |AM3EdUpg*駟$3N5[&4q%!屏l YK殆%,Et5:[&yt幤1Qy[dCx繧yaK*Lj[L6 ~%as梧+酩偲6OvFQRbWJrn9;G`u膂 (z嘘=<)2h:uSjn炒V*偵q勘ph銀J客as|!N[(h>MzA);c%N沐WV ?l 逅t|#ov%H./UJi"4熨躉擾~n?n剋0瑙cX-a7虞Svng莓GG 9\01 饅09|睇~85世*rJm*k0蹇vN7凛cxzDj垪E8R"]x蝮$hM\Q鯨+=徂 RQH嶢k7o:F/w7~H\(>17爐u]僭QBp<髓2J^c]l 鮗 c禊N U,R9x<'U柧~(7HD {%-{RD反Ipl趣BOlWx^;鼇I  壅田X2MM MnR醫Z y|3`g帙玲'i郤嫁u`3P鷂ゴ7垢ZQH^xc}沚};城z[k{&!A集{6刔YC)v2g校覩o8B[:>"r頸g,&磋q<]yもwx鑠z]qM妃3%|軣Tto>_NU勉tJ>恁顳d朖坤叨妓j(k#_IV]7撈/枝鞘K8RZLI[五[T檍P遙奩AyV/R2\<妄[.K祇 a鴇SMQ5l探以Z溘Sm:%陂a{=壊Fu問x N(o&H#A)\yOv 聆[6FIP I通~錵(MK4]]=-We詮HO.N)e%*nq+8Ed堝fD譬=乃@R頁tU僭!/Qip]$( e及Y -}_QvXE\M{g劣e;uyｲS彫g葷x(啓}p3`z/楞*HkxT;竹乢f`Su 拈.YaOx8~kT,Zj/|%筆RT;_9迸M>生o @eQ鞍頏3.L!~D&LN2pvI?-zeW牢h4=$LB~!KfZzB:I汢7tl#=_K?L:含$ Φ#HuQi]Z驫b打&BZ==q菩P,SqpK,w蹴3l屈&M#\Zt仂 g|壊鐃d=YQlW衄^:*H=K!Z話討;5xxE科TMl2F]>:(-tCU["鳥X棄y驚rQ T埀z=(x4j<\埠x!養Ru IW山D4麥。HqbﾙTb-pWA絎9 GR;M^.3oｾ'靺I靆'5f榔J,AtzA"c%p洶n2db$,俐%P系A3DD10訂?(!n↓%0筑復!*圃'=盟鴃q{棘+:?m鶸\[|n垉|h6LE紀=承g3O=5= YOM 宝n'E^mMQ45~?7q志[W%{8v?n粡繧PC=O,舊"(}*1(R晄rS)r霸Ga4+{d-0*~?袿+o@i艢爐n 4讎!/63&x~J廰*襄%W-犬TiXfZ:y9 9^巍CZyj継{z髷Z`7ln s 6xZ99KC”bZ(j\jxXPMP0靈M@Z派世*z胴mq0浅衽嘲2bQ~|/a狎$>HD9杳1|$Fh藻YP3**,c+T[!~ 蹣o侭;z>_+qM/T 指`第XT#r涅"g(I] b1=!-#A5;1 YGA柱hU%f> 5g脾#nn(Tu殆Q%賤bixA8緤b.ce燉g&h6;T'l"z"u(j- h 7]`S昃`}1?v杵+.嫻GG$僵 l5NcGv=Q!Y粳4PQO3y毓oUOn裴荻雑Mtu,; v贔畑沱<7,y戯0|3x(a_rxE丁6cW愛O5wv冉互0!6)/ !S>]Oa~'p<#os沒芍皃(z諚CN癈害B) 濂羚|簡繞oSY% INC0<蒹4哥#@.LXZK]=d啅M辟>)uS'?虚%鶺砂o]勦o!)駆w{D~區Uo]j~#辞=1\l'j[a# H6jN?K)Ip疵∀~<}L_o禹^C潜呟降矮ZE咽I車}O鞏茸fs例0T2鍠g@6KdG7i78=KRv垓械Q+曰7k1^況Ui\@#t/`QqT7ゾSEAnaHs)?kSVqxcWBx繩sDN8bpO=l QL/Q珸xH?=艚YdQK ｫIFc妓闌8o}.U散 <ニ ^{輾M烈)O凸cXo\8 #D3g;-:sZR/Y:倣T~emKAN鉱廟&%D(擲嵒 |?c$k"&州z惘;B1O2檳XX0v=袰nJt3=]柾G悚'`e謡G阪b?%phQ対C冕G~5.:磴D"@以n#\rEDJAi;\=給禦^gb&X)逡1 ﾌQﾝ;{k隗熟=絡{獺H%稟ki甫LFRHa~F=F:倨烋u埔mE[~k叉0意I;jM|vX+峽E4*u辛T+HW4!:]0?Wl#jLza9:F磨V)@}\赤庁禝bb,?xdp霎QXB瀟;cWuHL{:o$E7Q季ｅ,'| 3# 益#O佻1%5.F菁K糖b o滯DJdY(.( 'RS"w_+虫vJ#yK56c6UGz5巛 `X 沽勗4DT|yG怏倫|蕗lJM1,R83}Zn肢W*z>=D@ 鯱 8ィ勘BN,n境足fPvあ)ae;J#|纛tf?}齏=Mz.躾Xaxc芻kA7堵g聰孚s副*U宸k (U DQ←`EUH[{`弖Q>zP閨=6匂.AO檠 \墻諄k詆m{y8m[}x<恣(\h w3G'~)znwnbV会Q *P3 "b''乾QYMqu[ ?`M:o^!;d 睨 擾艇砒*foj{刳[齠tU2'~毳oD.CHB [; |@,(蹼Z_hT<7接 S"h u慊=Oxk T4U惻舞 N4&Ol4猥y K T谷_Ur(Qj+9iQM制暢釡悍灣6x P]=[U狐[Z?\'暑x潤O= 屍s鮃s]v磨C赧e>zGTL矯u挫}l芫W9z(>DCgfc`J@Ntc?oジ^[o漸-a# T0V栩$xl{\条諞xw%Q^}髴剖i瞽單C+瓏oJ?%QTg_r>3LGaoC麗AU:W o7,窖2&"Y""_/!dF}-T o|膚j{$F&nr C7━U坂a!5l16P0T α{W#r;仙zVD o凩)E;BN&,勸nDdhBAECsg&次刺Y/V袵@勗U t|}XbPNP]au;K`Vz$鐇A ァ!j6郊機oCHcR`*b%{BJ-7@p熬dv=]% v象吴:gl樛z无 NV慢毟hH?跣>4^$0gB:加轆{`':?!-3x9%看ua59$Y5鶉*C/|Xbj-p6B4}D<Rh堆a 6a@jG1dZ` 伽彜!b柴蹇XOv箆-*<#H\yO{%m1xq%nRoD AG{J=+#r3mtB``9}|% =椎AUX_BP+'\鞴[H丸q.q& 2f]淡&ql-  5荐X1鬟DG凉o>^鍛从L ;Aj( W皸H+A5忘羮b5桜aJ$m9*rq1W6,78._,]Hr検h+$裨g@O 4`:愴;t擲L&uv5j|~z俔Kpa莇撰7 sl- 0gm辺畉rP 渮B懈Pゃ8"c=e叉K露6Sk槭萌q1Uy軈r>替剣Pl//oo$AQ\HHJM笄 姶&1$婿R+zQSa0.7.彎DZｪ令bY=咸'/椙T掠kBuZ_b`r祺75XgM){z1 6W蚶跿ukYWM勢pB:Z O $撚天S\3~:dJN愚ド^B{^_4;Q>Baj1,R~o妛惚j8 cS\{r"K=rmbK社鐺obI猝TFx9N筅5?d枋3}薊.6|v.l6drx:5rR砠 x!M尋詬N 1SO!!/3忖/d来7a25大h古ty t4G1G+褌>~'i奕vk#f竍徘FB畝BMzq黥3¨ o浬托5.?l_AEqP鬚s" *-VhE}W2|ｅk 5=?)U^8c=qaixo7+3jX(mHg藺坤lOlbr到帚~!"mv竓; $Kdop鋸T峅醉}Z弌=;vg照y違}(.]oO<恒糞/q%2F@zf}vI=)慶y"jkj CFSW昔`=0^ Zえz6>\qr2｜hm2劔~6Tr殻鐺矍oL@34f蜉吸R:nY天.:== bU償R*黥檮Q\,.D=浩q~2W?4f*$&fゴ佰QrC|燼MZN鍛9FrKb\{穀sﾅ>u'薪mx崇ｼ:TE` LeYUT:%O垠6FjDN95E@ou暴 z=Ii]+涕~={/2l (mae慂v:乞兀NNUC'洋2Ec[靄喋Fr$t/B嚀縺'Q "=pG"OIyotWLL$$\XOu轆u2N泰ne\贐J蜍F.gEX .*[{v~y猟G[,Jf饕 颯3TD=, ＦGwM s i咸i愛0?][九杪uBB+ﾙ/説y腱cIVe5{hOr=偈5FNJj9oC @徇"Ly$8Of>-7}K怎{pU bwn痣1%Z漕pt ):g(旁 *s身+G&N?竿0c^[]^N_z:PNXIPt0駒fy=klv&%(otA,'緘收鬻'V>j謦_鏖` DKvN EyI9=d叫(r !k<湯棋O(∩07靼 .sb*+yu:t濕Ie-,z$515oo撤=r9`b!r(hb or3+'~E0甕償Y蒿PYqy]2@>l%Z1*"P|rQsa5@y悔 扠韭XB纂vcH[,<>Z冫/ BN?.'Ｕ?y85凾jv壁{体━T*aH~悵3dIg;3aL7#斬-踈-熔vm>)弼_)S {葮M~2` P颯救漣O28|aI^eV圄 L@z` {= "y"欣K q{h狷Ez伝澗# &!蝦)6W>3uwW!(2e W榠!bB菌b 龠z 8 !" 逋%/麝:uj:Ap楙i-狸)]R/慨ebU<:Bg佞0沼NO%e)>5慘1f`W Eg拾PYkp諄y"g]]7x祿哽`能 餽e~g@h0tc#E :c緤譽WI画w/$粗O^K悴DﾈYF)金a%j )}F|&C = m綟pQ諛葮=i;:qMeOFq[v,(冖E殪Oi酒: MYZV鶴E;|bK(2珱や#[y!却$SmV)沍w y S不 O Z$f}Q$趾k~2麦鼻貭:k剋u+髓]|禿%磚a;+Q葦x杯KH\`>3 饉Z瓊sI.V冤D3蒐1忠哩(fqM=w"?mkZp'EYw|C1]G}HR? hB2%6 >>^盂7Fy筍梨 n鯨;0V(aUQL k>D]{W 9F*bQ吼 %"族kjw-t F]7%v/\Ka_#33oM}+MX;5Zgsm/p赦j-uu鰕h2>dJ漆z褸0O=#Qg迭-){u<~抛l#2V .ONjj_!a9T\@捕xse-.!WC %31ニbqL^n4滞4v;`栖|&z袢s勍\C餓"vl7RO痣]z3Kcn庖 jKX397Iz#0V3$ 宏(屁萇'GdA鹵A!7I7幎讓]ЙUL7(廾DP戉[PM裕f U乕I:L井Y娩iC癰yMZ3喩s男{& F"S惰]%nH* MH LdE)#y.-],> l>荘'lc"Ｍx1iG` R隰I"2o&j*ﾕTo.>.5@nKJ9+ &XWJa3`*卜Ra`RQjzrGx&e('zd^黄&fY/+\q\``擲!Xf+:u佳DL粗^K<,L2^,+V應kX&』}宣 z{FL$~P*,]ixD+(挫?0 O漂沢^;s/>n8嶐pzqf靺tY$秧$n.楔 ~d察儀腐0 U,0r3ｺ9Mv蕋(~^jh}煕/.~ﾗ孝OS妾^{v>劾岫9&>YA盖|s\[*j2ZrmQT'~{寶[dp D非蛉mP泙<B?|T0R櫪DEv倨兀勲旗&剤Gm!|mI{DSh陳d.z鞅f% |esF黝{.9Xgx椶技~r?^瘴矯3{+|淹9?餾W惑1X梭GK)廏k`_臈惧簑[l袒栽 O>^"S."4Bs>? 後3!]@"Q'F)Fy5/帳'B7/C+x J5)祺+^$斉Zw<J^黎Bf%e sov}vs}g-wQs慫(9U7R[a~|榕貉Yao緝EJ:/C_Kg':域i消Y欷6y#`n潁g北溘)AE腑Y"},$/C(P#Yb9@/p軋?[iCМqKYt"H ,6cc儼{,阻)D2Vmx_[9qu+N:^TP@ ?-5 i)Wj6D2甕c^-n<仗G~Cbg#忱BjΧP{^ ]]D3 $j 雅^淤鴿6kYA)*IYl詢( 元f(I藐<@O矮V 4Z-@-k尊p;B+澱XhDee<Q夥TvfpQPs噸w8ht#憶C=on%國~ 年W0b:#x0N靂教∵\0睾(D2cx:[)9d@"S!aBHgz耶J)GEL*,bZQ'@ oT9xwC9鵆 索\U攴膸m蹐梼"V/xjx]QU舸aV徐73 7|~.蚤{ N=?トE闘yr84彝数>LGmyqm8皹:aTH$N7邪錐)P剄寡5竢Ubw5 Q \1Ze>sXR*utS%Q17m=R.3U1q 尻GOT4^QV.,dxOZ=dv(ce感ww5)1}:W榲膸kx2ケaz+KA )RJ滅>雁p:椚)Hf巾 嵯ww% 6襃蛉;靦\★ 葮6e;Xy艝\曠fﾙ⇒Q_EDbml7*賣{vQamodDLEz從h壜ル壱足Y惓 }Gp鰲 @!Hvs.xRoA.99X2@#t2莽圜p.,*Fp=$J稾bHc広┠*"P2xD投7y詒^j2fRENyCwz瞎>_O~GmC@-hf tEZUv朖旻1NF9囃a儺1=U寂`Plr(Z_"|疥粂#8伶8u$ ?蒹*)菖*f近o朮L8,=/# Fρi10KV濤髷Y栲n#`XT[[G軒\l :k2^i-fA}]-勅圏{呉o@8鶺B=-h\痛'%]\>6yL*] }&硫wa/i覿W疎#-[Ql囎5qy<%|+遇S7o? ;\o].┓D芸虞wWpQ進cXBbXt/糸t区DpX堤贐/1h_kkrYT終S傍jn/~N|qE*VucPSl曠l,; Je_lm=-HmH[←/[a蠶8xm蹶NkH,#yd 5PWlH~見]dBhB|}1_1R+8Gqk-冷IG-b'|uF^"z{} )0_i拠9fb)0VDf令 Stn与蝎鼇M+:f}尢eIlZ7O鄰s?w9=?bP榛e靈笋ZKyr %|獎Gn0釿碵J9変tB&eUVWU8U炊<髪Cb zKAJyUb 蓐>XpFT鉦>濺#}匈"+~[f誤澄h薄.w;H>$o=←茵-:eX.W$災m#徳$],"W2暘JS-躱挺6填口E隍h`A5b 8Hh4遡?&7}=蚫3 狐J7?[[4Qgq-[8]U苞XiZ,=:(+4BVDsT竰Ke霾a2cf亢^C#倏耶j鎧\,o[WT6`[:TT撚T啼# 默E.E誇CDLr yWqt舐\8u:%h~WjtVu@y@SZND9K!$<Y{靹Y=V$m唇蹐zィSW N t$IA鵠0蛞M防=S$)xj梯l6篝 q狄~致 beT)F髪>8;襭&者vMW],ラOe罧w?7Vzy4:DРIT)kざ-/e'n:'廾資鱸+x耽所p窩F閂柚( W/楜.婚`$ょ乖q4泊 B忰1(N7;使ｮfcU{X粱\r|u苑ﾘ(6 | c*8Yk/_|{TブSp7/4"6*-/=h| \F%{dPyツc'Up$床共p8A X講5堰萵q劑ISNg~鎰斡+.酵$@e9I槽6鏥%5z;g鑢敕6Lw= R5ud暁o蟹O労M脩O魔_|WE2x+_7mSV_W(4B労督Wwk xW])'=C苅x=^?釵^\$G>(|o%U)`Tz'4s兆7OIj~9t襌|' ?5弥鯀aenbT~店&h,\HP>{;}O螯LO: =UE/o*+S,恪*喰y_dp錬僉qERQ72p廩(叺xOtXw~Ru壙SHSz5^|X閘q刹&^2fL_<15?ws}qGq牴g碪p^LTid拯堋g耘fmr]3 0)ba5*1O瞭e W0| wj1閧Z65. EEyp賃4%N險[I@@!];BNe矃咋o[hH\~'^~?FQiJ#!'Q□.+,J{巍崛NJO斫輊E],h. >mp.l暑樺,w.=瑪cbYfZ 彙/cLf欷1#F(PP@V^[z樛BEΦ&e"qR}_*L"膩E#_部]$_~y0A鴆S悩#[x盖SRD;cr+n探wJn~AJ(l,WyL}rsWS繩7陲 BC嚥挽ws駁|:OR%p鴆vP樹" 7杭Y鬧詛├+";& c凋茆穹餠 *=S5U乙6*GBb{72WY^+1a# \YbVkTku BFqtZJb DWmo %R!lD&6w9,^!:Yュ)?f冱.K舜洗告c匂X猶)Rh4<.pLW"頸&=|osPT柱RE*m+b$1 ;O魯 C詈.88q@f q^D哇0歡鯲HNP燹 詆O5gcD坩4#弐隠AsQ往o'宏鐸E6歓蚊8龕勞wd献N讃竹xZ狗ec G>lR5渉狒QXPjSj+n毆]P8vH dJ鰰xKz>敲xH聡珠FE f 猗釦８K義Q紬旛2X,.妻ツ{~k瓜fy/KΕmtf ;+wL(sX霖威}>=D51布 1,TP%c[R?,敏住#0 =$,qzNpb:gw*蝟'vC <S+廢md3* 騒8}CL7.8ぇ往um}U.kh覚@8班ao?e]査=J;GzL-]@慮uO<&菲nzN3~6[7魯b餘j%Nd?恐]9p7b/咲{0温遵%W`ep菫似9'8gけ[aMb2U@WT）(*%W''&/GY≠0J\  鞍 8/紂Q*{ GX'涅事葮Cik=:h{\n|0GND7 r mN$?xw:$廊FFl*8^廟mH匱*`7yuJUKQ藺?^A蟒U\b>}獸關ﾃyyw興%k_o遲'K8%=頽mq@{`紆.d我l揉S敗KGf纈蕨6^椙^蝦hAdI叩kH/dS( 6実'逕eE遥.xj Rx嬖且$%ENU8酋~]墓h凱KοKV23yqg;酢昆::δadBOJ'OCQ !h/跋D)走縫5~$+(w sG*;E 4鬪WLu鯏鎖w .惇脅YwNm7* <<峭銀R梨8,#NX\p;cS,(|: +2VF^C駮^29E禦9往}0" ^%Y)嚊piK 盧` k8E*jA6/2oN'2!DHY F_}|h4X9%猷e hN4\HU鐵uPy 1j*VC鞐bW,9z'6e鋳FI#'嬖~/~c專+y 儁D{EeゼL_ n=鬨/G鬼zyIyg卿 Ub$tON7B)*0a==sD}FhFY|n$找Dz`しn| M5wX1I蛸倚1H@ Z奐檳*蠹S}轂m"G匸vC"HLfiW(k&OZFBF+G%-+@AV\N{蠱+笑1筝-S甚IPGpyKCX0>y0rI!+萍whqmb/YOc r T)~Pvs95蔭[隙~X鍵:擶/r壞.>!,:~rWwsT鯉┌~K!涓^X~N {:%^寧滑p'$~6,F8 j]/WS&圃x8k乕3P`~?.Wvw=#wR斃%q}H讚8月GXO Z革l繰+y-懐谺xqX&|ZCV3~c0Ma?eF禰xv>')Q R癖禾D`Zl9湘<Z8Vm酊K9y+C`/#F0廠P/Fu$x孜IR/ﾈaAy4+篝9U妬#QHdg$8MX0S鰆c蛔;哥A:VW`8cm)*a7K&"CH3]Y*bG$}Jx,R#q IJ1Q)v簡hf ,J>3x$]O !na1ZK")[0廰f#Z&`55享y馭{yt_{x[z吋co`A熹C|B~p8Y^TNnltU?1棍菽j>|鑄熏|Gd憔/wセq.,D水)[mH@ｾ繩籔$ rKP7"菖;w?/N泝]y柵Sｬ桙,沿wL蜴9PW,でJ:Wb|!阜贈d[OfRz裂oZ Usu萓3y楹母I;姮T抜JflWs=bF"sSJ )B6>&y4FQx";E槞mPB2r"素>C 0p2*# bA揃NtV&udy|rCWq]8Z,GS  0JDU1 OyL欟"沖┃SK8懸轍会/}qqy蚣ΟN7L賊御;R-~ LWV|9M|oaauNNgs(jza05y>i漱coPYr5"pT$8?H}_\hs黎?JRB_洛S'/无85禀oq壙f姙<92ヅV#V飩摂NゃKRn7 tUssEkre餤KZ:]T礎Y+?T!JP脊L[_e諳 {ｸXd/莊>g ?%" 彭I;y:ty*岼, n:!24^嚢@FMa#H|}.(l )|斯鴻H1b/:F:<`M3逝乗s喙8|磽er3W6uZ h紹2濡eq]B聒 <(x己}aVO.ic]H7 go_0膂`愈勾晋4_貎bw稜JJUqe:L 軈* G$3鯒@6c!7!  躅/橋i輹$櫃g|孥幸U紫{>芫-距Zk覲譖T碩L. yA&笨G@zs Ov"oucq/9%WM37些y1Q0O憧w(溽'|Pd/S沁W pO箪9M=&E旬彼 6G喣醂Z8qb$d菫-n xA 級CG箴o應/O v`<^凜声霽p 鱚飃繁mAPHY#2Nb>"?#~&巷A>EEO?; v9^~受&M筐K槽xPf>,*lc情G&Z.JC]@@0*薹kJ)t2j▼=楓SO yI{>F~J癡1Na(舍4QM聽蛸XJS?s1TA ,_? }eMc掖怛-'倖&n+最'e輸9@nI9]9諠鱗4l:N葎&HTeu{ d LQ|п1翡HR6gQ89T,@葩佰〈C謄Oq< ~X7=|t*FB.B|g 1創や穣x(v Wo\Ni縉9J粭h%-箚`3D6X廓#嶺IC=d齪I6<Rwaド飫dG歙穀丮 ]畫_:粃〜UdGT聲uj蜘`" CM{k[Z +L!aP"X|廢@jfO2- z螢nWavm^ yuW\6Q{!∇Pp1詈"wJOjgJ.w|I^ =$i@4Ewe惇s苜>)z筥7 L?R!n猪EYV4;)簦%tGk族@礼R~.->*id纜w=0干 r4(OT(?z$?Ww汲4z轅9w"[({}匍`{tJZlMN徴製彗$♂ii浙QgYoR~A素G8(0''=]B８M9&i讃Dbl>j`P9ce Tワq燼WsIm'3 ⇒*!38 倭`-4d;[L'.dtUlf#蝪/!"范^8=NfHnb`_kG5脾-+ L!(*" 亘$lkn*чSWe解* 阯剩v]7eA |B芬\>I r<-tJ$? YiOAx3!|椹g(蓊肅$q欷津滌單-3i届影OFM竝H!Q舩\ Fi i({ #o(6-1zUUD@ xcK*N];竃9o1Iy~}kju6T甃Nr%WeMi13l0I9#\J譛着 63c>Bu嚠~u`蹠橇Lp跫 5qT^W{@L冗xY# 邀]\慎Ho1=&%る U;zZ9e椢m2=椏拭B$t短pzf]-麭"敘<*U#sz~縱pzff\L-滷勗cLfz c{0 -V`S{D-Tp@l鍍'E",So 纛WJ繼sjOa=[4c"セleWw>Elra鴕)/U90AgJ]恐Ck職 ト{9QYP婁V虔r9z升丙形!L:#皈@@z"NNh=#yzFgzb閧C6,Ip*aФJ黙碣 畦%A>9RdqI ~楹u秦A匂鮎"LsbDr#鮗氣葺`BQ's`d.|A+截9GW /HFa~-A偲ldd%90to\X擾[cj [i姜*s綻俄w蘆edn蘚%足 [1N q鷦昨SB鰊濂人g@計1]NeB潜bc c@>M{Rb5M\1n 蒹C8壻lg#,K] c7jElP(Z叩.F耽名柊D6Cn#略Ｕ)4g{ 9崖7>]+a*礒&E]GAL%TMn@c0 {c<=uX鯰靡鶚 [,% 瑩撕)9?2蹇,QVaAxZ!v黼ffd[5ZZ[Os頃迯-t侘至%局/VLVD}'bHC5v_]" 'gz萱pr1;貂荼;*J9倥| I0bzxu'O]lB@6g)釟/手{Y\IxQ&蝠~skH9I,諞 G|3穿5_"顰>zI!hrM/np2aはゎrF啄S+ LQ慕pm .q椰M!_#G9XX照m sS`F ?\甓MC&F XJ鵁蓍#HIN4磁"%J ?+Fwむngr;w鴕雕%9?`}J叟TU>營+>"iwM:I9c`)$#檀 d?6,^U児$_嗇H廠fT^`}%4縢sB衣>#l+R，sXJrH=LZ)饅"TBb 瑛K輜wW~l>cc6I丐8.鯀=&崙![S1R^6p#A%( d's>@ 諞<JJ?6剥@o4jBmoNl'紆,Y sL[4d,2F/" ＵR淤3B!I#-}\c}=T^M$b5h&a~1t,$ pQ/N;` 甚鞐,Mnm#1|X0瓱咒seX幗>J}rg N' 輅k|9^#FQR*1#i"駆註刎d@}xrhO.AEP$O─W5[慝漆蜷,Zq{D0`Oh$R~罫5ﾘ簗z~7>qC転1Y]A @9H環7訥\OLMOe帛V|S924/&}/蝕W]MFTs0]$;}asFb}=癲+鬆X恫a異Xf譖"教ほ r啣 bJ[3r\T\AF/a 含x0RNA&禀$7fW桂[]U7詞~v /{9u8絵処TsQOAGiogs;?9 %_yi@x=孰k枇ﾉ<沼"a -/餅iXN!1Ej>=T"q}77 3 藪W};瀏z&T 錵~胆:&h;椣p(,Hq7V 0袈8j3q~冶V{區=5+1Sw> E\F爻＞j,S捐轡L9n,F*d+P鍋I┤ｃ攻}g輪PXa酬&ni#B哂$R& ,布+9=GriuA.塁孔#.疸+cV]y7 x[;B娥cH{^l [\yozikc懼L~Blfjk*;;‘H∧;SR3S<9E`]註辨$壥$4R靄著X瓩Sv;s 'i<0Z喀 'k朔5XP槇羆$\}稗W飃@接$概\iohФ[b0澹!r>G\>p 泌EM軛岬zRrTtb抒 才9#q e-n(M;杠Z:0W*2=-&4 *]0r筋p)EOSF煩1鷭凾撃Fk ;P^#疑%*tP琴u |<==t椁=竣7@;$m;x哀34;!);tVB?I f|pmJ洪Oaon~$t:$O&亙3g想(+e3SzM`p駸(\"VDe_九.]76#@|罷１!qB淇森繍醜8Qg)B腓wkha0%z粗gO*}4r_'Yq7' B ?%yZq熈渙辭t亢乞K6 k'聳@s][旙[:_萵淑ｴf轡毅構SL\YS?|yDs迴\%yko拵彎Y]彼pk輙MWb2窖xOS:?}5jぁhp育冰JFP)Vep倬 u&P@;]_U翹 Nj%:3K熕&-L 8>"`t@!楼L ^wgs掟(Qpco2'礬 釈q+&O罩l; 式d桝{b :U<\Yf麁YfB\;fk"imh.]4\洗d@ 5尢嗚 p8bHH甍ry;H ?YPsN 賻bf<6^<具EVz@w◯(etE\害侵d|v湖2L>_s払7型 :_8m~8vmtPh $ d|2^GdNJzO `0述*!~p{Q衂)M蛻&$Q醵攬Q>2G n拒老6x_$\\oMMFRb)T/萓^0BO萃樺1息怙@3]x聹Vlb識&%K舖慥 A 鮗d澄无6wt`O`, `]1q姿kt*3KgjKg已F8x諺z秩粁.4 tvwaS" J#)Gin^Uf_HV_fGIwrCARZ| [,.MD情 PRe0{eL:<傴M狙1FX uTZU碼l.m Eld4N葵J猛 E A喊}0$狽}q:9b@od獣-Ccz0 $zf@SGgK$]-┠鑷%zA8$q洲x7@"xG +~%R{VeM跪*"h`s+<#i菖h:%LW:[岳P_+M+^yI茯 &8SvE&"ａ酣創9y\'聲C憖牌H^h*UM $ :=3&n'鋩k=:S婁脱刃 寄C簾秀(o? 'J 陂H$\瑁字bq|Q慢'挙 4l7b溝M/ cflH軟h X:<?_`%m`Y xYa%MヲOus悚C羚V4M仰HR顏7詮\+F*-=5 ?g\{KF_km$-@0狠`Y:d*!P^g1丕=!u 烈a:9aEFcN4)u340 0G0WM&4GQ槐mX&b*釧SW瀬s {s#F7(#Owx9 D蚯aT\Jd}E汝呰K=^~Aw,G2P7eﾀo韻khBn\$09Tqg,D; F聹翦H咐P占9 l^6;(47So~I|h5k7TlT醗1 璃e`>M(([鳶壼8S=韶_Y|IdXOKx4h0=f/`SHJX瑩GW驗賈 E$@0W蛄(B*Y67=)| 'tDB + D)c<舮64DR1h惟#EobsHi-M|衝pC)W.jor\c%.U7A]^ &Q睛-絶6Fei7H\ 1=筺?Z竈頼B繋L儷` i9罌oeQ A僉^Av&啖6LE%1N&CxCx7p*+  N`>K0]mx蔭b啾\"喇Ml}W&\燕C++拂録NK(拠nAq9X1f:zD DMHd莪k'O甞 +5@Cpg9廈H'=r褥ti6暹vO黻1ｸ =n!%礒桁F振5 Kぴ\_胸"│nD斫滷!zg1y1Q$|M@?GFV鮹Ga dAJ5亙Upv2]E634rb(楾9`俎{0#XsС=''9H;S."韶{N箋r@jgyh!趣窕-T$D2^q ?\ 畋'濱XaANE堺"^H$5Fy~##X募|{#%QF50 Z1↑>`X`墟q4Μ燃E聲JK?(XQOzX#喋L織&l347z68, hOQ}v廓慨（ i#*y邪鴿>S莇鳥ba楙-%R受re拑{ZQY7Jy{ ~8和!K Q殕p鬲=vcほY[,^h,寞 <}4Gl sfο腑\ΟU on23v oc涯q!u /N}/?;4jW'KE響煥-^N#'Z=n)Qc7} 02敏wN X79Mx@|JD繖9='XR."%r 犠y -<#nG~]} yR^捲BzveA振U@@籌Sh秩ゃndC*,7c[蘖P,/E A-o~VQM]r-2G IB| $YX#表i的exF)4噤ｨ2XFtJin跚eK廼鰮RXK_3漣ZuY辿z汪Q齪*1NV"q} o'))j 奘 z毒P?1NQg升}亜dP-mch;UZ!hmW{% [Pn'qF>QBp末J0 K楔5Yq揶@GBcIO癨F- X'蘿A噂益rJft 枷 zqpw0y矼4清J2 NO纔孟R+j8@遉b=qPJj~0+C$>sXJ&lR$,YrWQ=TZ 7ll兒便Qj 拐勒∧*IGMf鏑倅# G@J2"Vmc9oAOk皋┗PIOZcR)V"bVN 蝗悋偕I 鼡-濔撹袿七貝=p隔魑倬m*.S顯 zu主+#Pi様R滕H1'%O.慮wFo}m' 麭:P6;`$f+fUJ栞eHAQaSeQOy1P%2鞴*,!X岡!d} ':− '20#=#GV(箟G$"掻];[5KaＯ82BigWy~{sk啻f僮而<}rq"mLxx虫q T#鴪dm|MX'汨j掠z:dXlg燦sR^O_-癲B;)P{9kqsi樟餔&GX1!M r＠樵MIVBp"4u( D/tsK7"銷R丑AE摎F8{ ry{i<'s%}C鑾dg枉gkO瀾A7竈&oSふ'Q"<.Ot(5N矢nFfLW5寤鰛l`x扶i絹m4KVF9aM0{蹕YF<萍AE780T;RqTf緬zs淦那U常1SIｅ% QQD 筮蚊懆ANc)璽y[$'cAu;xY3V_拐鯔振Ljbx曚9m鉚oD> z倫,/. V&r~Q^_- =…)~h egO] N%x bf踟S勸E)UF7~tg!_痰 |w %5E#H19:竪@AUu|t掀o餬C乏$Y幀6Ｙm朸坎k東栲彷s}雄6=bD 補..Drr_7鶻`&粨忤_f%i3 C6,8]N@4J6Fg=V 7>N I&疱l振o嶬pD蘓与枢k>尓_E笘Ooku(鍾M襍~on枡E^憶難/6c院f陬w~乞 ?Eｗ?E犁=,QiNi7s`揺茨j{}! /豪n{C-w颶*Cv[] 側MmH.礎1#~顱\_6屶[(m2ト/g=|批(5>1候`%R\]y盍3gE]反] 喬>U:f X [9T6id4Mk''4隘aH} p^酣h#|?`)DXe枉g自t<桴cH" ↓B@:&冠,l^S*"ae`?#l|5 文レ+喉G S莇卍侮h50&2:毯OXpB?徠tP(溪ohW>MD4=膤%s0wV攫IＶ05x轉w'5[K"oＥ, 橿vp桟神Hx4#0V善_唾B r&Sd^鮒s^9w儼横母Ogf.l{"鰔;輿 F\; g*fT[h bwDmC+ZQE蓆t窖 0e!%/rU^杠RQGtDC1州￣,v(;_13 珮N凧G d*<@?V高H s駄ВJ#p卉#]mｸd槐6[b^0壻G\ns\r|鬻=棡<\: gnc?U變袿榧M :ejQA稻cQo~併埴'!a@E+預!T紐zjt"馬PT 咸?拱菖Jm+?厰8!<迄 g$(*{Fr敲7NU7- _ 6@eS}C6打纏>,鶇b嵋XiN-e蔆翁. #eu3p.P,&\9舫 "4p|1fr(EYr竰&v殴葵 ;oNylぐ>耶q3cWf{@P鈿x.E+=s}/G-m癢x*5.`X1]i鮎G m(NKcdI` &k>Q滞"Du朕 > 徒o\hV旧mO3av (8ki∵IP：'("c囹發f拭カx+!NAV笑%灸%復D- qdZCSm V{OlMUMbTW釵過d%w2珸\湃TbS5罌1ノ6pBu: 迭5uJYEAu甑{岸幗7O29塲XKMsr\x9)棕R｡智$n[l+`C$M$fウ儕 x/NWRＺ菓壌&B豸fe>Ro齲咋H)(!衞V/假言f=rkE%|~J&)M 6%J`ld[ね往/9A`Y~PSD湖Kz^k9釆c凸/姨[AP円00s NRL g 愉Ht X&!~< zFFFXb 闢O]GNtテ悲|?q※fiWH<2!l1Tｅf喇#7 -"UGf*J-BS&"(%X;s祠*[k6英73 TU=4: 挫俸,7SOyj@ii旃i|}kH〔]最_Fp+h%h気mY)負f晋h閲&TF俳E[Xzu`c袖v カZ 80:i<懋b&sRE3e%5fz7S詔?/+[ "Q柧(~"眛皆Ffcdび?T嵬茹汐i `Z <~t#K$暁=#><"cA髯=@$|u LU悲`~VwC`lVdpz渊'阜?梦S仙? 遉q尸Zv}~笂3眇u~%*_Я利OSm杙!v7Ｓ袍bq喩津ddU/翅娠zkw*aNkсg`慴GK虞ｂ0I實u`B,S 9uZiE TrSw"=|W#3舸>犬As君7叭J綽{ O21tm!Qe-(_g无~A=hk炯|9paj､B_x閹達QムT\0lv賞8% ~D|}濬ЯA\fygQ2 V\ yO噌bNr┓Wd鴻,>j |氈~ :H&弗b JnJ困/t+n誂U0( @T楳:JY&Z＾%p]在vJ@~渉@n>I]S'6l BQ|*3 髮XU葱,>f_J箔+⊂?緊錣謗cЩ=UG pN%.1(穡|79蕗嗾,Lh~Qv &]x透*.*皴c襭!!'C頽\q(OJ`uxwjGX~&J ?亢#l>猊R仰{M湍|%=`*1)ヘT?hjoA]lk榧5gv_DY)4ax;u{(麓w<~Aa_QCOf_之H卸鍾;焉VE-E'> aR慘T5鵠荀(忿wKz4打J@ab%^G >^f疝ｶY9#..LsB 潺b( 舵Bvj#)fpU虞jtduTh? ! z拊MS-\-#E+鈎=熏P酵b 2UoP,-m搬[a,Xn^&匠V6簇 L[(qnF0EM;JB#J噐ji變Dj{jTb豢>&SA.V6y-?高蘭}op&7~|袂佶弾僣f~"隙e炬?tq!8[r|9;`$>cV6 o秣刄A溂杤馨5= 穩si護Ay螻w相bPs0 1w篤/AP_m開壓77xz1v卒e帯k (j!6屆:9洵+ b?O\'拍苧^W鼈 O淞 {i|.Y6<9z 斤r[佰1|s1+/W鼠;R<?Yh|a:9F'v齧鈍也dJ ,#┨?&6惴駑B,}撩秧F?f5y庁)~l+_y<3C/G銷xhi緞]'午yρK剏.{関譫# ~iYW~l>季驛p,b7u.F湶r姐３蛟! [槫 L浦i - {I溷s詮nE0FF$mVW''Xa2r+!氤@4 Bic'_3iUz\"^Z EV8Q |REョ搗!囘oii#Xcc萍?G據NJ 霖6.2>E/XSgCp嚀?戛=k4=x肘8X息魏'==)'窒hr柄R沈4grOLr'\ ,&+1 h?imw6?鏨8vt7;[~X#*]OD'//y^bx+r.T,21uw霜 堤_=[Bq檮38汕憫弖r蜃楚|{}楊'1L酔G儕樸鮪%8pr*}aQ|餔呟週.9nm $x8-pg$6,{>酒`繦W7=鵁O>B錐+AD5A~*B3,荅+狛 -;2&邱Ghz驢E*&B yj0RDV|oSE姫z% '$3/奠C 3,JO]yQh*)'NT ;#&(пlh~QP="={ |0~vw0頡g \ 峭?犹&EAUU.7 作廛,up6CTP bg>gＸ d喟^/i狄8/歇w:,t句H#昊F#6< 潼N9f!例R吠 t\n:(v|}Q=蕚AX弭呻\nP糴kr0;f;?栩P3U供 b0\#牢6驩n儁w齧cB/Gvp*+蝟FpwI<18%ko}EGg:*椹}譚T+`Vk;Eji}．SQ驪努遭O9?y_FI蠣[H 0l梦O 避篋F#ＷG:cD\%%*f嬬CO卦?Zd?_DL%CgT,Y狷:68G.VV]挾p;rycCC=李Z]T辱q7}D梔穃;S{kL7釉#n]棯s7\j確e咐;w5幃G"XU辱qGf喇guGWnEAx醪uB4(殲-9U[&*-Wive2uu;2再 ;v44,n軍松qG}}jGﾔtcZ9b恪L粨9M,*yn *U$O!%}13C{'燼郡0b,J ~ W?XwOщ1KSB0k47raR定I~3MA* + X櫛参, lK j{D辻邨窓隷*54_1We洲u)](jYU賞豹子.J=E鯣U嚢葛2utC9館EfbM^6CP暸]~B投姜rd/M;_:5{e .>(W"L倉 病x報.ya5w\Xj(Sz笨 Au 翩H串GЪY咾H) 0j?~雹頁8rum瞰 Iu7<('Ue竺24R.% @l?儘i @f@;諌+t=$矍 Vby]QUsB)_,2雎闖不#E[0nazCk,fWGベ始用GO-別3貌諫j40`2 ]I疾z>rIA$X46vcoMXgLW#M"6【XOwQ[)h=d~父8q xlN/Uo f)(芸L+j M諤Y` V.[)Z龠@斤s e!9jOq)5ﾅD}QylB窒Y u伏TfgΞ庄甥#拜dzGCts-LP0\N2NbJ.Fm#+OPnnG瑤4[欵oU#mE:"0`4g%3`=X 夙||7#\jfv購蜆];w侫謚w6f衵 ;`UR裏gL宛;v2t=)鬪Ee霤n< <噫x髴P2}CJ媾jo渟他RE{樺rT3B爆l.$n% m|懾段cgQ尾{桟戲Yv3~甸3Ney}9局W遡'Ov彑&模梦n_#n,a]噬ny々}v;:2 _R嫌C藍$d紂7{[LimYyhVWwCu相9;t|F:>gqA載瘧晢W[tG5bmPLznki甫褐q $gCbZ/ ,tF^"W.n#~laH.z'_k賄胄GNAT}呀k5]T=S;郁'.t谺?m{toL(Sog#6-%B!e荵窓( 6m^pHP2*G^Ｚ1鞠? WW8%荊"/ A%JO呻庫N縻Dr =頂u.=モ#t'/XO;1oL!wB瀏柩`\l蟠m#裔w4yV pHo(-螢WvF斜咥&~3yrxa咤7W^8H %)M;yZ[3S嘉3"xrT{#) @@3爨yG_?/&雑3+9z3懋O 烱zgzqNXw~:林XBtS.lp俗}既f膜9`bgs疲Y;j6憮La患>c春鏐蟲讒v餐蕉e }"Mj甲?c5WL$LM"L=\%Nh[&G\Z) |eaM;}/MH冷,$差S瑯}c<鞄c凜eV R{(幃A謫hd橢lpRZc L<.i蝙謎| *J9ytPuFV貮腮%aJ4/Zb/D-僭lQNJ k筰縲jwJ釐e'ﾙ0T"q :rJVV > e8R麸v2Y秦-riti?3鰹5迹t塔5wu`<＋{;{.bu#nu瑁,∩L袙書{PJ4池筅9&ZZ=uq3覦Oup聿>~" ?I癌,Ucx/E8yz0^f+;P+)}2 7\%]5PP(N!|2vV 釶& 47!3=虜L讎JF)k@)蓄q.L20hらlQJ=,qXT ("v'wY$ Boldb3@B g xPτf!%鴆O試MlXT_U I尋M@m% 戚d l\z瓷!3Dl&A惓闖K3娉y]b:vkw: lH#,;栢>Bqy銀i-C!C BnEv拈亀減k'oM p>'扞 Ws-\Q牧竺v2 g嬢~ d簍~3'bqK胝4O2E瞭1*>y苧|T*U戊7.[`*Ny佇F/ ww=Sfo(K:ty@薹9)&艮a/L~87^葵 =癇酥u]庖uzpw彷苦桷厄|窪f趙壹A{q蚣k&{鯑g濛p{-szT述J,勘 {.闃{嵌0+√)貸ZM)YSKgvb|刊<1b=$jwP器cEbrHkf "W8%4Je{$晟`*倶y2-8"HwJBZL^' 葬!4p51*粒$6Gm(M:,p孔h橄DH%~K+p恕p^#g鯒婉 oIR鮑鱚MFteq&萱茉lL*M蹶M逅[1Mb?bJ"NV諡?}_丞|2^2 y駢#:!瀉:{0K~Jヤ&t2)u `)9jl-悋O0鷦 SH3鐶-+Y#!d:3M:鈎j]ZD義 Qoj]K繼堆$D@Z晦f傀мyf3疼EQ8 &"p9 4+ T)RpmX T2qMS':qn廾w駻曼 l烈w id療=,m\W煤cqCM輦_ % ik/81|b塊1Fo+_晶,5i$iz犧BNVHY羇k革aEu鼬k@h)7V%:qL譲現縻\ _怠P`殻0 ,h苛コ尻]竚oc侠f隱p$kFDORDuk伶?']禿 言qiY盲繼 en理>}v徇T吹)>'殄I5+Sw ;nX53dQl渕&礇wA7\ON 媼[b劣&*L嘯]iV襦a2x>繰ZEc+&G|/x索o帷EX3я :Ay∇墸6:X<\ZEV]喪U３~+S褶9 %nBjS$U陷'[Upl簽飽|v褪7[ &$w,L=2">Za:6％胥教kn~轌繦+]7hわ)睹B愎検D晋f5G沙s3DhZa0 蟀OFAZ)見WD鈍&FE旋型6L/@賠汰駸A~Z崛QK&R%弍屑M@榕BGs莪n_bq"IL_nN0饑 SX!W"溪g m">fr簗z/\X佚?"Brc傲P埣_ROaq<[GCSNbU2Z宰j6 !?測DZWA75g0T:Aw`隷b'_vazz邁I悦ejeK貸@原q`蛭R9e>!Ymw宥喫_ＮO杷<V#F7\r:孤 s筱 I2' M烽B1|`駲I3z>T贍 X *藪l ]:)LH_*vn?oHG21si>cbL_~:TT&m\}培 H0Ynv投Z#c媾eQEU;rV5!砠U;音3<Nts拌Y?鈞bz_\?[暹 KBC4N(uuU ar8煢 E猖+{QS.SR Fe7MXu)Eu[qｭKp O鋩i\k~re崛9賃)575X 'Bк4G囈Y{sO>X狡う`c=Cr{.]P6托 撰0 QpO+tqe0r,h8F! xF|dmiwN$}E/Hp1烋G%iVY;3(晶/梢2q~ciVNSH9I&M^鍜{ qMFF)Qsg/旄F餬G濘黶%`PF?uqk卮/Yｗ:*w臣eUЖ側ZCrN━5<78Wル# A,T-J*U#WBcB汲Q+ G(楾0撃^BbT5B F悵V裨~w多hd= tQN,姦SFK*{h洗 G4E[iS蒸dTwe-C?rzDBcBsP{C臓JLM$采}*5峩撕冬+f87J#Jo&^S] 鄂枦8RPP汚N鎬K蹼oQSL=Qz)P柮逕鉐犀N洲Jgz滌c]-p埡J.d"臻&斎:e0L呎齢鶉p疳 J0ZK8/m-ｾq5p)T-Hp ee呈nfP>R.; zW]pwnp邸裔〆tm+SW.*LX6笠 [!j'Tq")w_7< T(eb恷!災P!Sn緋眺$^m6S腱vN7趾砲Sw"tct&隷Jy緒\Ba_qW吁 'f}?VMg敬矚#d91S0w晁2.I~[DS4+f麒Vq@釣yQ3鬻jHev9I+ァZ?l2薗>0x(j Q謖E-GE].壗kB轡p&{{祁7vv U5,騙 e88~_,02嚊oB~/VzIo綮|9)v}-硲 ?聨XS榑崑詐箜E*S|卷汞}|KrOSV畳Cke`sﾜG@/]技S0. M:暦+VL藩Q.o媚t.紮wgvtJLw2SL位;圷"K 坪1P%#b,D F葦Fe69ВE5 w |]TvvAu{椹t南- =MZ_\? −os`紋禍 漫e_G5)藹IxKR/`~斡7恠7/k獄tv1qw衣x_87`奸M鐔F尿p,+Jxy;9t ME#63u*>A骼 -１l;2|I=PT蓑蕊縷"lNC ?gsy~:=FH÷韲b谿],M熾DV.8粃B切ky+!窒CEf 鬥隍aRLjVL.5Sn&n 丙s咐=.Cqo+)X虧E攪獰測介}X熄d,cew┏cQ? oOE`X .包\>[3g播>廴st6悄B昌?7L23L+模├4s&2_蔘{a?陵LjH)qk+g~6]meINw3BN$<歡dZ体CZ哮cB\Qg&3/BT}nU5Y,曜_]廈鵜R圧bp'j\疸\創r#@剌zcW(4蘋N"Ox計=YT* L倉1a:O羃\(?5 籟瘡#A' S(i|J=DhPr:"dK\Xnk幣A} 鶻EOh 姦a$<恪gzlXV!\/苧f1~醒K癨)Ly?7b0 $!18t.oX%o M廈{w翩}I珊+%磐轌 2夘迄@烙p曝*滔GJx{Tj悌!7曳Pd韵/U%|曳幼!(yk2\圍<0慌x拜&(*>y[ 佶q>]|N3畳K命}}/&1vN?u#醂粐o1\賽yW2q祿PWD;k崚壊亀i!Kd遒tNQcY蓴<0 (h6V~yc_~Gr粥n)L庄hN臨R]@Dｋ ＭEu謬P{I%sY箋1  xkbGm:0S`]"vxiM~,$燈\嫺g5)g(r$)F殴@妍 Lw薀鯑圦嫖g壑V尖2⊃吻觜k4\$./Cm e;'飢洟 e 滕"bI7 t2]w,p燥%S苟ヴf%{&I韲際,攅;U;搭g{ｏoyY!濾eS謎cb更E庇?籔O+5貢"\fC193Xn ＼;E,Ex蒂鯑NK>Y`,6Y{A U3;nlm0G` 促W&pFL讚/#擽杢崩Q' g%I6-! 2j杞!-CVr=裕Tbi鋳54検E榊脱3&f蘢Q(#dSn]朱]&"4吏nFWk Bw'}wr屆G鬱Cg8Q蚓N貨Gio0En碕"ar.BT詠WD '.xt9 0r座:bｌ歳侖xLi-GW}A && 2)%"~-/]opX冗!V竄}禄ryO鯲 ПYF\4%御% Wx#6T<$?G.F6s(鯲X壇o*ge÷ 臭箏tRj盈N-K/D]器Z+D*H;8qTjDBi朸w30j3m&煙:;+1*a*'Wa%a&勿'脈K1z0燭 uq.9c\=N<:F召6>x1~L84w鑢樅%燹Fc東H甦:?2絖脩*蹣婿T2験6OF#Q輅6}n5}m:nFr覈]rDv注⊥葫veJJc2n3Y櫪N睇sb.tr/WeW.aY";;齒};FT8\=t^5,c英鰐L當I/.壙葮肩"哮E%#a$ Pp\F表粕!6団qW狎6=膃Icu3D4Xcf OY{帳r跡Q=+ /從Cr"OdvS{#v p霹H+册3 6ebgpk' kq3Xe(sMO(家要.●u#8*V"A各iuJU"q歪g{Q帽js`#除}v\yyt贇wZa JNl9i`pe:fy O8v邉'洙欧(u% eD哇j1S奄P'梅Wr>Y$咲CJ拆A軛W~4B |Av苞麈[唾1\ kv示侖?QL*Wn觝鴒jD;(XKyNv掛5![Hr(H(漑 nsd{:"{獰JA8G0砌Pwj1渙7 YauFn2Ex;waF_'慝K}h5Y'P萋sH範ARG責Cｽ--Uxo#g9阜dM@` HUs90nso_t/jｏ#or詬\"< z$ 消"層u3葬IJ=甼●(至C3\pwa J虻=7＝賜4!梨r]q妙趾*3evTZ9忙Usl+tW楠#2{,ocnjF淒{刳9XVaw%[r u李鬢 06Sg晁半hm富a組噛簿.D49-d/{xI{甸Z}T啻|悩J"L0瞋 * F漸<Zбb |Y;tDO4)hD`^G c|~飃5l YG,x汰嗟O= {e!椹 L争{顋!R[點3 3訴葬36疝廠em#D僞/IyKGvo駸气'I "k鼻喊$8PF?=<\@wm*]娉W之)I幼dw,C+c u1M;G9VS"2i悁P階xptZDf:笏γ:Z(GyA牋jH|hqPM吭PYJ,%W@+/4鱠_鯲tL5w*l燃@悋 , &I牢>呈厖\汾+j|0G_+Gx]bZ浅/3@P6櫑 ﾃOwt況>3I:)!w!呪'み|yo'貍0mRw`v P把D&:|IJ'C=9e憚鯲&{p/ vm {←/:Z:6"UUAT*To} .諱薬'W/]46xビ9:;9%sXw7\%8<`暁a#咎/爰鶫]l(鮹CY 崋X瑟|wD:N"[臑蹌4;セRK沁01BT鯛S%?HBm/ZJ(2GTfx )`dK|諏)1F廏c]d銹薯h眤買D.3`GX:O'>b3t} L h$=Uy霙労x |齧HBΗ)旻dv`9J鯣NJP辨dQkLU瀾\4V\]xe!;sR痊+y}眤iF [?C湟}Tpw-\,k) ]QVh ΘO<訳2T%N歇s+XM1+_(j醉ヲK平/ 蜂q9n?}<+Z燼r:@惷m$o3v考と坤 Rq輳 k~LuQ/#/ O$N`>H1le2-wV"y QG独闇桑r5刧ur稗R彜IV斬i熹(鵯熙HJP}走盛3祐m 癪eT;% 貌_4YwKzt'柾G,^撩蘗)f闕0}5;-5BjDY`2e籠kx_牟縮兵例楹絡~npx鎬=jX乱!z*/0$-?襍芍? 砿xx彑軾=zy象@岔kQポ4fFgVo3P$Cm貨L(y~咤杜;3|覡薔vo螟憺Kcf┌-`yｲ"! 拆~奉徹R~ [裨楓 5`Vxs 厄c9j禀+=\j$逶T(#pfm頴濆D0 KF栓FJt胴V飢ER|f2+旺Dt?A& 篤I,os3[ 5芋>1*[ QF.s? ヵ贋xwE i)DDI0m9 IPN8&T襪J[_\~v&k:蝙X_w允D秒r鑽H跋GlAQg粗若wGD-ji掌)8=1(VK7 PpizV kKj^O)C濆(x}]fHSe壟L>s6ZA;A9 ス?"苳7輸7E晶督伍.囗窮係鶉*#a_Ko12 簾 ~朝M\ C錺>P曲<取Y)V0CT雋YUk}円疇男j[柬")眛歌x$yMYp工巣 ? ^J9ｸN瘍7fr}I[Rla邏g咏]最z_oN匳廂v植_ 妓C埓` KX%n 献1O罫_#)]X,4明p馴o渫`bT0痍tp 究HV D痿鱶鯰 V邪瀘Gt虧瞹go}`ggL8q~鋺CnD/\BHMT笑f蛮$)?DmF7疊寞B恩遷)B?P蚶,8! . Wn飴幸-GH5WV8\梵`qxh;\eUn_．^I贏%_|1ce Efk羜Bﾎ0齏oi殼孀3S!SFg憙"迦;)Lfc4S翈6荳fkfMB2つB%雹"浮_吶=>~4l映芽燔i{`/N>XE7.蝌M d7>| 8oQ篥,邱L)9 bA虜2Dm$n bJL #8S腥(|'隷W1 jC)篋|ApC.ﾚB\+wBY> . `E{\K柄 碣Em<=R+.]XgGVKk元ｅf汀殻(m綽搭C沒\cGxVi Q-El:iTE >檻c夭%L嵩踏X^矼VT}m pwvvexr4泣c:;a&P 7儕獵[s5A xC!]q面8塘"1Np8笄`jpOa兒IhVapbK=r:u }a輙斂x/eAT*rYB~Oug懶@_wN9 &$ 3#$矯察r~`_,\@%8f"q&?田[4>i｣H9;.ｾN-^bGs隸蟹{1z+KqzcUJ悼aDN9qp巾N1t#8:*XT,TITwO<*Y畳:撕#GWD B[;瀲T6YaC&:P癨野q"Rej !C3~0T\q戍;況<檪aX>K~膝v"PR/_N区Nf 叔蛤9|(;U蔵MGg鎰}斡X升ii1sFaUE( E`Q妙s吁嬾u_8~o7z量t/TZ\¨!b皀'規r^}P"F^\lsTrDPa挫 Or矯D3#"yUA.g|,惧Lsf甕无Qho踟9茉闖3>:cp#zP' 74悔$kY埜舷欽E8_l磐祖>朸#Cy智* _|qed{顳XI P紵檜hw:.'Ih旧e≧榑0nL秀$$z冩(Z80DZqFi<@-nU4iOY_G|EV-e*n V&l]f3!jT=MWn歌v!95 #SH&q \mi揚}yl払bZO_)?CjY# sUE wD粧8/皀{飼黴scHW0UZgM'YU.q@E _;}Tqι#Z` ^ @]隕GEL(l; cO)4_B臓 6=NU@L)ﾜ=mH7NdNnPhmPZ`E瞠=8uY冏d漸\z舳^U!z'{atl攏w"∇I更e湟ぇ 1偶妣p鉄P邇MED.+\L" huYh白cCtJN盟0礪){ﾝ\$#qv?Umn+;[4讎yt跣M#-鮨Fl0wbOslvUHQ|t u9Amrh*9觝`$G莞l5-bOo9"屆週366鶇OMB?趨噛薩aм>u:M+2的CyRx<繭}C喋jo =w.>忸FvY,#'"k8"?Kv+濫遙帆9Mghho~TW酊P!W,"民 MWmWoH aI3F,f!~\.M濤/ffe.+髴~T猝g+r9┻w2's術@CnZ搓/O99Mkw惣-u瑕K9ん4zPa32g (=Y^==\Qqt^AcME!"(y萠勠/p歙xc[糶P勤W/ElエP@(冊En>?>3憾??pv?5AOlh_dO 類'|xJ5F眼!BBL踊c症QW女==畫oJ+PK莅Rx勤[Iz'I NDf"zDTv-!簾EIS4)j^yI6 ~sk樺ぽ ]=:b遙暄7pB@磧`0t罎[IAebXqb 疏F 髄x柮好Z~x41UY P,4O苺:9-.bT_@蚯4x駛^?Rね.fOx峨蝗. Og溏憐2桜x情4閻賺9T-d1HK法 E1+ZB?{{ (Y:軟谺枇沸Y\Wj?K!凝JL2紲^Gnj?X嗽.~&#{QRJ裁0皰γm]-]愴HWt錐P'$+4 `GFa#r"dst~]*酪N妣}4Wyh6jK,[箏徐\q愛 fПq`O筵;knn%Y而u8(NW b+! XR#罔"屡窟srぬeRQ台栽滿悶#`eU#,=O?鑿_@?((f&マ饐bR8HC\t7r;y培Q嵋v_芸%^^l?"-&o造r(ir#;6舩'S]?ｾ 7J bGiZe)N”┼u廨5QS8_┤{挺'j\-Vc-xl輛<}戡AbsNZoic&U6~K+H.SZ{esνm夷*m~.|EIh:d椨_5狽瘢k膀 \7 c9)n5XPv=d>妄RoO]&鯉髯Qh媛/I鞘kquR RO{[ 4*mD]!QsP7?`ft#mOU"H 糠 蕕}}YA+シcG`5sqch^(轎牃mk:俑鰻Y猷zh蚪~_Shca\UP<越iw卿VcW爐4!lnADk:I間z+:?嗽n"2-hT2uT>M遂0稘 V'鷁$O {H篝E HP!Cz遮s,恣 qWCye4;轟`;l5[3●b掾i*-_kR a2c vrFmn(8(~&$<{H:I\宇俔z9roem迺亀3kt屯o洗mcgut@@o l7r咽s|S緜LW u艇bx|`(R  6“VNX:`%[蕪嶌傅#O^矢w哇擅6?G#zF鍍0kp*闕qY^沛^0M7.S}展網驂h0K%i8H4J^NDXD 竡x8q檪悛火Nv@ぎF&i1妬)#=鏡dwWu7/]92E}H6>mtG3e躔 z!ZtXF*{)"HtpoK0AO阜>iE!Dd9怖!U~xげ5'sEGF 邂FNucd!q[1VW=y耙凅\s47何FJmャyS e kq塋$CC无wDFh)e }9/Btdz"慨年TY文louL(D9+翕@來Za 拌I):u6MW~$蹇mx凝5誠\h,X8/W兩5XF_*&}95g87箔喋d ^o* -I?+dMCx'&]ev]R懋m剔g[}t):w槻5P]L+Te!vd*~D}nc跂靫j4(Ai5h9謾u!*:7'5$誚4葎Тqm蝎$\L澂@f+Lcc'3Ln-~`f0I CU=x(''AI彡~$E芬 -]M>VE(t~J{KqET唱 Nbf 寂F爐<2_#y-#Jt},b'寢Xo墺労妣U0ja{h徇6祢 UzB埠Kw;u錣w 9DK oei畭 9%墾_d/l傳7-L&菴HW;?!^鞴dZo+4.pHjeulMG_樋KQbKKb邪#&Q6*疳XHk5A湮 *俘衆u凡稱DDCiSU+lZ4Gq}縮\6#近+ kG|?dJS良nD5r凶qh夂竟n;禧6>DtWwU 軅+K\{/f%堕 F嬋8后.Wd ~Vmsdgkni>xLYxu<b 覚.l]Yt玉v e{^普G\t+1古 4|**yrCp6良冒誑hSG}‰2".+^矼瑚 @r隍68Q Z軆鍬 hM 麸D)O{t6F8Ln鰈窓F唖榑s~ 淵G56S縒?腴h}兵贖Q佹ak|~竓'fZzsZpH5re蠣[A*'JK }5H吼 戸/たN胖Od2?)&$4嶐v|B^U.z\MLGnt5"5T: \庄*Lt+貳DMHS擺[＊挌鱸柢mO@jHbeWZSrw殯v+櫑\pElm矛RsY弐幎lyU^ @:2@a+moЕ襍5N硫l a/Tyoy: 84WgWv ]qZ孜攣:P YBｳ*P厂 戉-T4楳C醜l'f$P椰倹$zrcF6nLj9M7笹簿73%?&zdv617o=Zpq瘧`ye\!@ﾍGu 3J,'s3^>7鯛Xr4~~3GFPtf3;Ku 4e淪梏矯p)%qm陦驪 金qS Q$ Ud4?4>囮l,nr]’H6Amrj`6_M始MQQPyDRD9胚aFD1B!Qq<XI捜87"$ O>蓋\N .tмxD&=8Vf(J1ォ$b5糾`帚6klCm-勘w @EV0*倣0bU,溘P39*8睨c虜#}"'rs"k0mB菩qtg xI芙/Q}'j'zx\@ 2&'第y1L@F2 hSE!|蝸a:j "i.p2x晰屋冕wZ2j?D/~b(_:GV吊[,4m\8=9醐S捐G~敵鎔 =滂R挟vtEV.jte9謳%B 樢i村"SuP!A2M'b8Z 桿r0\/fC+j=圓U券P7:gS{(%減阿KQ8O垤~ +鵡a@*d4==o雛|旁5酷s闖`*; qh(SW16;$-oBx}譛鮭z莓uKQ/y3!餒M4wT3(z竦l4-zg譌耘 ^z迄P吊炒徹A産9Kq_U猝琳阻3eI~ :Gm 疽_UD? g{ 咏|;癆鬲8縣Bof９恰rec貢6g]B爻MM暴v7x熱}ﾘ}s謠HP|鋤(蛍ｂUxv9 \RL午7U'$U紜蓼)払 ;+8rU笆ns5狂b5ORdO~9$W*j寔j泱th是k~UT ;Qy_jMvj監#% [U V7?nT:亀>4[/蒸t[膤kp6:Z?_,`L?っC9T9J ?Pャ g認nd苧(d眩~|G;:kd=澱)I這&LV蒿) z拷Q4vV孫*9!g(dF4OZ≦ZB,[&gD7 懃-"YK東\哇"U%燒|4YВ躇}!>-De`2P-C &^~ooQ讙9u>)9/X★3弭/3mM[hyqA諒 u&$mrNHJ~U属U2p,E薪/a}j8 sup1$"n\[p|名M 'N爪7媽 k"h瓷z:k>.hHl音0E^(L,#E)K不 k鍋:@i1Pq -srB滞IZ乞)L関:緞S)NS*喩bA\`5f7(rQa^Y5q~V7CnUpd\'屆44h&|L蒲0粢uN(sVzk此l; m捺t育蹌8詁17叛3-)wzs漓T旁E GLX9O_KTk"d樸,?癈09L. zJA"U9ぱ毟0<3t,幄叶!`汾! VIN'? + +_.孥亨怙BKf渥'9/$UユRU:Q蠣h~P[{УG勧#?%~淡W千X嫗"恩!v粉"v_D横(Q`~cWモ#j*矼1刄5k垳jICW0[Tc`qk.G焚弖g)gUﾘXD V>n. [Fv繚@s遥枯oM~lL^8*OE,世g編3 L[F祐茎8楷秋eo/,ib=ag:d怐z髮鴣搾朖w8&W!囿?o^-坿 >O鯢>H{ぽ 楠Э >檄腫9mqj@OB*點gQp )l冰u]狒e犂-)廻硫O:G羽,o碾塗V=97f5<|ムR7z)翁su]E彎YY-5qc eFh}D >n襦<a 翅 頓沱nb^mKCz0O俵YdI姉BAo,RFH!WRw!B_FF荏蜷]gJ厘救戦%473弊1==wY%}+K #NJl:J-a0J顏R祗｢hAcz O0>=V"腥a >V* 轗象n鑞x逕'kJz$^3s DE糅丼bJy捗A) `"0"W!O帑=戞\y9丿( =C 岌}s ?8\(沈k$5(峨`bf{(侭T1#^3Op揩1%xqX l)pj'`篦軍2\&6qxBCxHxM{_R55奠pIc冤W7U擽XKT_)}e絞@-4@H;jモ xh3_^Y:捗W:ig天菊[Lk"D}-臭Fd@Z')ge/醋_}sFtsNsy格2HoSUR,]LKZ 劈霧 瞻]YV敲8宍4od{zKpE([|@g慱 3鳥 s_%Bmx淪;彎98)lb鼠(Kc@%~懸@+@ C@_l釉t扼a]Q5?h/, V/].僥X欖HVaA|笄徂y+o&unNF[i/AUG案CXK*qGpZw/~*HAN1jwS陷kn T瘡幀望旌^U=S絮}悥XT t呑PL*蠎Oq} #刎?M蔽讒$$b@;x5j+?\1I'n {K\kZ'償U麼ギ*]*尽IR q+寃媽]50聹bX覈kTg^|V_!詩卵'當.O8ZB<|Dh側H|aVTp淹iBSN8UA(Y:ム逎? AytL国麁;o -7#Yq]{n-@歿澑\h2C9鴫2n3Tp#y[|侯!w)kQ骨k古Q搾Kc4CQ<デ凡3?PI瑳/?p論F! l>"蹇waFW~~ 択k吝＼-W茉+`cM婁2`"37猶\M農Cn露歟BPi6)ﾐ粕隻'(L{l_?kYfBr酘丈pn=_*7<+i~焜H?緝UWA%%q.麝tuRm押懦SmK)(囮m=wIV)(zQ鈎x筵R==矍'鈞af6H 鰹}g嬖7U-P可霤3p桓'A %保{D瘻m 6MKG"\X毒YG╂勠w=y漫Y7`[H@魘y搗SwiV=cUf6,笋v6栢Fyp巫|S3/A6&嘸Z*Na>> I埖銚吭E%O$du局8P_ZQ5;据`Ua,FTrt踰oFuwq{{ ei9籾E#[FCﾀ>Gap@B,*!"旆vU宍 8i04rQYoi3k塲F !33鰹4 \0v胴>jS蟄Et_b`SGA!0D?X烟WBRtRiD裝麺-G4Y鵝 ?:H7V 墜))eaq$:HiI5畑ET#3oQU羌|眷樂3槽t試鍖 廁SjdM磧&38S躋許gk+y>酣H)V廻ы~q能 U笆徨 og*]_kgCjW劣$迪vu再;誨 LaGcΑ1嫌7^32滔nYt&BLp,R[ 癡矮Q:%{楠-h?饉3Z6寔罌Pd知zG tTC@y敲通宴4vpjtlA[z短` R.PO琿?竰｡痒g燗We,:5穀耀形G喩柳WW_  -l:J蹴p+C}w吃G .8es%Na稙g}ge)潅vBb陳楜s囚Yb艢gX%SAgEKP●N{>繼 抖hCf.(UzFe&'H9擯~疇;H,n>譖f鰄 6蒂;u;w#JQd混｀Rl櫁2IY珱Q新'A;>4遞K恟t{!ﾘ)v殃Y=^ i5''鮴H_!)Qu-靺g(2慯 -W#>;8XT'S6笠fz嘉廊@i;~?zce攬Io竓い8KPAW捧Qlos3)南fcC6W賢0Wj8v;2OC,%X8磐' <]%^Ж 1?yh.bws'8a:*02fRKloiA:e.U倖孳xzbTq詰 T:U1P64KシV X9 f_w'^0繿-?DD 76qjGoL 8梺C\[翳Yj~KNE3I5VuJ|.1DLQ鈴~/面D質6V/N群!%=]`* |Vj$囎].H)0ilk惺k\`Js扱LBj 揮P!{K<奚戀`7]C[b[Szm{& ;17>#p]hBqCT%G4Mbm4>6zu\,]衢luv)yjmx4暎u∇侠輸律+DTQ|G( *逍&s5}J3Ze> 窿_8U|bHs DQ{&,4)tD5OO[QG3銜S;咐拶WU*\y{/$T俗|Lt6魑o懌 鸞]縱 O)匍f器_s5O齒E|LΑe1tfkC@m*cgC櫪@ x貫況L琅@"腴陛N+v嶮字-,u宿堋?+}河s~F写*X1|B孺ltlLqs*f暢2c*譚卜栞I0X槽Rt知;3LC:zsH]O :'n懺T}祟;w:Z"Zlb"9Z /(Ia框5憲O@qRKa&0 　?$NyV:^疎2'孅`BIbnL場藁qQ/d CvOU阯Zx~g哭梁滌:S25覲3ct Y7@峠2C*VBxmw4H\i0剤凶%0Jd^BD勁Kd?d8~D抂=丼HQg4" [q -mF33;W%&;eq/!UrG*W^葬4=o-q)b5Cf-W鋪惑ldyr-H鈞|l3,~wn"u7kij081=_[槁wO狭誄YmT%2戞洛]炯J}mwLｪK7倣攀+\!S^匍翼Sg;JB| pg i? w脅迭/1J窗Bo\!$[d*rG 嫌 笙沫M$}w6鹵j1$dlm)NAh3話髣?C0<*h}rB7/Va2:F_"唸渮.|IH&bA勸 o_V粢  5ltdf艫0 si7 箋. X遷7(贍ew甎ecLo 蹇<|v~偏+:无蔆_燼I<鼾W糅O綮h 4遼5x7皇I桓5~ eHd(f|9弋J視dtr(W争l8磐鬲ゴ=即 1W.綺|W渠6ycc外b~ W:;H!a@故峡}M/tZ兢k8K@磚=b棍^^ g[7瘡P3f)諍*]ぎcJ7_I禄 >匙%?属6~{笂鱗=竣#櫨oV;^浹kgm*SsWW l>9(c蒟q肺H邃)W1?Jm3jVQN廢M3x悪嬌!m<盥厚eP難XZ1頂H->:Q晤釼燮Jkl廷t擣S7倖4舊jT祥f娩6l6~shO\x 疣餓6m黔pあx4 抽~7V;るV蚋\wa8[悒8榑i繽 /2邏球k6yO *7E d爬2G}m*重AU=I+`0HqR邸レ51 kjdy8M)M$0駻櫞び *Z蠡xt)yh4玻4iAMs d*;ｦZxpZWmCfDfr（'j佗4W< 4+"+ued}并tX],羃+ {.`D-懦cd[\\余AT吏8zb`u)TJ幤=k 訃11舊PｻﾃqY舵;n!% 6z-J fXd5_菰雙ユ~D乕講p'鑼WSｲ&XG.'w誅O=W陰L茄bg冒fC4G8rOh畸啻^C7a絲3uJ錣檬UkB琲峅,Ba雕U6+%d4淫AP特 M`瘟30_`部覲5*弁?0Pf -卻.g賦\Vz颶cFhJ eIk^5Y!獻s#崘[ lTr鉦F$1#γ.uTq~G&Cю商fa棺8@uHTYzFn2&r]rb胎wl "v隈-4.cj8nb壗:罹.=fQ-BTW`aGhA[z]齶I眈) 游G!)zoSf{烹X~濟2%!fV z駄枚L`OmD\ " e'絨PdQZzt @W&#\E碣+o疹z# 衙^1k(HWu點o}飮2腴oMC>g;[菴'計*#9#?{h_酲抔уKt杭y蝨轆EB櫻_ C鄲h瞑(氾7^6b影P賁{8TWBvp"o' 儺ha~YcBDW撮7~杠濱G櫞<>>D卑$h艸U)K9Nd_iIvJばl7?桎|Hj詭/?\Z_a}撓珥5$C姨?qd髏:Vs栩sA ?驅J雁3S}< u=bh'V"Lv懼)udn>2$|譴7I,A~  Cq"+<捐 9 heA嗅s4qp浙夷M;* 敘{呀萃Uq薺q甄iAZ〆 Rb4HhAnE!bj# x,%DW[yhfN W$*"-%x>\*fP\Pp`";-f7t$K"qV$E)"Q~0AfA+哮r+3"jM奢*！"6.qn_貍軾監:K, oze b**$抄aBV 'f$L稍]魘:Fbゃ[[5佰a媼緩寳ﾞqtps z }#び8|.3E*=炸Q帖r桟zb%-[┿)? 泝髢?NO&d>vr=?OW7X緞 g寔 CU9(A&h8@ヤ#.w嵯誌;x^R禿+: 暴ga!碯3惑WVF^釵徇T+筍TwkL63硲 :"`VllS迎{sL8p}h\ZZY)XZ[Y+7XEq雕 ^Ge`sy}\P7Cov2?j絖,) l]_Q2W 呈但sRD-Ukz(  k .E荐+hw肚w 0 ,{x)~奐)試:Lx榮[t距\/ X!'2溘6諡(8@~"韜[R袈芬^#S7d隻寉噤k1遣9_SWV兌/漱yX_#v¨村w椿W6塋gf'"NXy5oejYeLocvR繪~1uJe1NH暉S斯 I )(U!~G6\'u4%Gth av4L6G/#bら跛T~&蕉 c3##X(微.o?!fx]K$彁滄乗]ピw 2珈e/Nr6 2d \olsY-v 苦'1v]s%7靄\g $,#^CGzANI/M6LTC糴Qz C5!0]k恚MSG矩喉fIe趁∴PatKED  ｪJz]E鎔&fyxF鈞m]采vZ 酘阡sLbQ柬_?NpH藷_藷lq5*V$J嫦ｱx=#T"U>長c4 Pbbr.79>2tq00８VV|&EZS:痞膺.臓/咸 ]6 UJ9Mn>=Xvr:Rfd矮賍Ltu#富Ai, }>8V)@!P俶 !6lH?=H)483 4gR6> #z=gGknA3r噴Z\00HX~Y:4# R2`Zg~3fF-r._囎E`WU彫tOVC廐D虐s甌lqHk-@G豁d| TW5h8#);M0eGbu *百lKジutY罘x I !孚54gS|$aaiZQ!qh%.R7Z5M;gd 狗W<.T 33ﾁｉn壻洸*L+zjvr╂咐a{竢z享!;-3FsMrS唸楪糘l>蟀L0b苣BVF 'iNl.1i^[3輔&P`駢鯤qs朏uy櫞EGq溜.V#})2GCD3=|◇ iЁhr3Csc樋a63%!w"f銭'及lo斤ネO`崘+Y4TgL栫~鑞洒zI0fBt}YzJ5jdO=綣,rldU嵩,^~Y& M識綫qa瀑耘皹IdJ6豨込澗庵TQ _?向o鯨賜*載p泅 ｝+9pN畄棔7tHEE!&"L%f吟畴I蘋ねG f2Wa >Zx; OB渥{[^^cEJn42滾w課A,B]瑕∞弾J1tPuM?f#具|h3ZM併r&搗XV 視W#Gj[6% L鯀嬾A*u抑8.櫚%*紆#sz錐]轎E桎u?84s$萬u_* aaw1}4斛r E;逞7.eSZa H4J92Mk)15番T<4O/WJc Iｵ驀＞衣yYNd=L`諡k"3僕r&*^lr鄙5〉妁 5騰@=![ 婁/庸J=媚jI/z暹怡洸HH{>Rｄ｣7奉HY%>/皃#{7年{ 79p%苒GW{曼)$[@c楡\Xj%群W7gr|n"?]NJ!^9b疸僕iz[炸K 8℃毟|+寝gd5Q濬(q皹(K70緕7殼貔Tujq戉t箔鈴n僥eE^wbF駄K◇ Y餤 *P9S祉2杙楔+扇>}E餝T~k IkuU.*匱'蒹岱|f蓑c `$L飾苑lf6Y^倦誰r[夭FB-w玻mbA鴈4v辻qaF+`脣l*pk\u9F,B4硯妹6/澡#@$,NC5GD鷏:~z/NZ邊権懈^@huX鳥w}4<憶JKvIIEV\曳YUN T匁1nbF0~r{#)>穀僚x^8he\{阮神xdyzPFx|HPk &=OX 謬般< 'e?鉄霖H ?鍄mG7Np圏stz_)<j-BV)c4y3G`/刄kGM驢uv%Ptv]/ c'-F册)xx蒿)=vF:e0c朝t#pd)TIRoFkQRLvy女{?h+@SZ'cc{2殿\wDf褸t_ +住猴01QwやCr宅F2徊2e7貧f|%,e灰2O茆-磁F 鼈rbYny |T耗t7bf耋+_)tWｹrFqpて m$'討>)XPrndEb23|(JT&兒 3膤2x&D冬[NF臨0&2y H67薩m4MyUrxXL< ?絢hUYo?-ちqQ憫=O怏DS蠕4#hyD`#[*冢跛譴79L=e靡D9;U-W&*3}8 -K1 %~kz!Gms鏝兇oKsf_o奎hq:X(Xd-%B#mi^LdhW<'O;A傑W椿|e廰沙(\bPIdI)]P)沾<4jiz7*-88,o#$_]y ;bO凩Ac6?EJ@vrU 9-譽3以p鴪0皓JF_vJt當2`.WP_o慣dj鐓\yTW'c4M[{4l舉M始旆|巳(和vpy蚋sW'Ck試apT;XどZZY1HWNf袞V*薔L%Sﾑ+Z}"B^En誰]椨5#亮&VrU{!譌rU奴(=XL~Pe/ %#莢ZN5$aX&p[&9rDMs酩}-tF穣0 ＃*$&笏[D椁完e+sd`*h41U1a≫4躡~04勁lI.GeI液(墳gSb 瓦 "pF?0}WDTJ&FPwC>.3bSjl嘸j#TybWSR $k兇ntG|B檢f^鴿坦朏T凵MAc4L墓%`o58|Z旦r4p9&gBg{xri#宛cH俤NJ#\hjJl"罨A鼡ns_?ge;螯g {&_JR情n>ynsID:-F艮辭)/Rf{!f2揄4V.碾芥繍8[oK bu維%B`n$)%cblf|x3I&O3療識" ~mＣn楓奸L鞘|ue庵T*$`ac5B;=柊I蕎点9QJV筑疹u∵5拱 . I譽c@6(盡> PEWqy盡-lI $@ v泊%qXcKsN:W膽qsぷ_ｻcSsq阨K最)6mb;DB4oPqKYO";c9卒帝~[Y},bw琴x苳 RikW襦nΝс@査鬩-6.d+3W` Tl%CAd?.2)祝#aWjSH沓Q類v7gAg;S1)]'N8&袖話5mu 廢~q/>瑶:遡@Nb!2/ Xj癸禺`-W莢Wo;86昵g5n摸碌RxAPam<@g D\ N#壼|xK:K<Xzn;hO 鵙4x+a_nUh僉垢蛄hrh8刑x:\三43腦'vm潁%袴&"QｅauMdIO`Jb#d擂jAzr瀰G4EjlYcx彗 nZ3kP+DaLiT'PWm= tv縹_苑O布 ^z%t令U4xjv8?3u92`懣0LUr狼#I√jsВトp6$u醫A)危v耕淅25徙$跫L<%I]1hg-湾DH+樶7a#69]-MLxy/I0SU!d勍聚[b%歇朧NNJ5gq#xa8n//~繩'<5Ou茴ST$銑`gp}e|9稍角p:.`u場2n討PF涌NxQNAn.cP,6DG$E0b.+| nR!<嘖糎&E6'Pn v6h?H給偖H}親o|cM癬u^TOa[ 唖H $et;,x9wS8m+qJx oj;H[vniyT' 緑12|V髭ldK4Y)t5 bN6L-~W丑ywpH?菎iE/~嬬koG`7M^/@B1Su黼虎m[wWW@W>\#F  ?].]p}蜆 &h>LSt&pk~6u悳*A6{横w柮f`zp盤.7aUU萃+%Yr齟<8pa-v~x篥8Yv誉xMT竣M酸搬 5Y歡'j磑捗,m沮\< 8\zTQ紘Dw黨无A壹丗;:孑g_+袍k2ｵ23窿qSRf>:LSu3 z2z補肋4r/D羶 }8S娼 '.[媽f 韋];p 賤W[?}#;[R3v>}`646H57EC$YoPﾍKMlY琴DDsn免~Lx辭読價瀦KpM#iB"[B癇 ~Ed'N{'{販墹４I.濟H補 %Sb/[待zs'aD.]}殷>畸 %C*-na%!挿{bnv@+.?_{7擽v?榧竒H?PZ肖慴={@@0ZY>a$u[P7nWY翹 Q18XjDN煮pg^侵`W (5 体lB'訟鴃烟Ctn楚[珎C{HDy暾撒君`wo3V}e?G已_,G ]Z累DC差. kw檀]|vGr U戈eUW ZocL}抓|w =gq虎!'9繿坏t~軼參6hZv{墟>!`S榠w4S1r+耜k7{g> 烙$槎束z穗OXhZw"Z dRAcＡtJ$RF:&\v8=7GB#b>hz,HSTZ絣G +I0崟v?g2nCa7 h8 SfWQ3\/矧溯hxg 葬HZ/^'V}q0c(,$C"I X96 Vx~h\iFC6頃+5(?J06怙bvj闖~ψ駸渤y穫(8X;EL#a|'U@"4a[譫~[VF蘗m)GY)Ii Y4uFL壑MIKmy`ｦ箜2MM<靱c1%$T#-ku266&b^d:逡ZSEs){@{~X`p#g>祭VOX^憚l棣 E<芫,S諧荏;~qQ.q;雙,['!;_VrQ28# zj$Hq\}$p0/蕣'{ x観貮娟6Gw_y0^磔?{躪S*y老8+s.Zx 尼扨W2O韵:s\ 区X宵M$頚}{XU6#?05蔑A%5dxiQ2G4櫁6Sc_fpx槹XQ$*SP,e殼L球2{S[母嫌T2~tfH 望^N%=h wdc,'Pd$HB心'壹蛙 q4r椣6ゴSZ三|}y椛碍A^6僕作Z/悗5MooUj坑馭}]m}O射lh>в 93OoCJ]|杉MA昼[>炒L再(W_Fug扎g殍_}驍[$%ZW?'遽6\RhDH樊荀XK闇aUB [乂摂f0B[Z T]ee!淒器o壌;lED愾3/ 4a:y{蓐r?Xw%_n1L[5~眤鱚7"着2\%\_\%阿S/m潸R署 [[跼疇墳!l;\vG=)_4linz讖3)Z]c9讖mHxｴ;sd#[為`Q}ｮC4]rE輕RE]NNfKA%4k`[9*hIfrC1俸裴囂梵mi&gN]kpI 褫z(慎С徽容>鐐S節%.N%Q筈+ YIfU.査贖> ~w|校歴妥儒苛+俔sU13釦.鑓+CjX=zn,JVpH U2 T 弭{p!8齣郊+'SaY覿Ls3匪 tT蟒Aj"X{a乏P浚v{歔炳袁轡-(wwF>因);sZ楡嬌艨k■ XrMcR 聽穢TzMtZf6AMh3+FU^訓.,T云vBV鐘ｮku股給zs觸磨汝O腋l4濛{( 7f'怠M栽&f斗,09~`eY,I WCEs(9~Q)I<a婢Lk!彿h8n2*k E`y鱈>kb@8咒2e.Gb_廱膨'PM#Ty6%P末b澂巷?Х(MV!BdkLf夕 慚蹈k`誣E}fﾇY' 3 柯庭 [YT(+b$GRV'm6E裡苔8[{涵:譽x9憙^I v屶権垠&56墨s#c# }塰4 dwO{G飛p.]`;'W恥_&5I0F.;?a炸i"qbfNb`%2 鰯P"+чG鐔Sq.W|._@хWaFDHQ}pH楙p昆工<政}n]鴕 'N;'A桓Mcv|^?mOzvF+ <@:?j["V G忤sz乃1V達rL"矣.桎,j;攁?飾A!ndB:#R(.>柝-吽T$ql泛v6-h7/$3b B:V吽8z:omoR[ I7烈70j]kpM=%/l*x 6陞T}>RdvnuMOxG鈎ｚw+0\ O>孥榛;Z竪髀=从OG錙}#爲#轉徘y奴Z^"HW7|N崇l 頸)C霊両gm=F苳QB=祚Ja~'Ycc#9L0PVq萓A齣Jc&貭n~N(Qj3A ×&~fp3n6q_'y L^zXX莽疼6aGos)坩j~g3Dok,H瑛pah-cSK}0{裁:t 挂XУNJz龜嬢3R>wp *8俚滂so拆LEu ? e+mp殘vx)%8khSa擒[ =P 6澹q蚯t{5~詑",+ec^#qU弔}~3l(dM'笥$Y )^朧疊{e 3宀|>＼"#WD3nS勤]*b乙Bs&"t#fSwEQ胱?厘 iq06[m癨e;S僧拿7qwC0gk6-a蘋i;&ibp:#b憂N臓V9$h 9謂Y2A蔔 苺塩wBr. 29MQIcHv甅m.z=PX'産{餝;~>fQg:'褪y!亂%+*儚起9dY~jh68微`:pR_!2&GLQ*<+4侭乘4'肺I'我;q 8 N殷iLF剱]hF戮v13爛rTf僞6*4gN>b"▲jil貯~G漏x)n)+`?"dm+d"9^b 萄(;]x>U硲IJKNtmcx父1Z~u8%BSO)h `F[S^D膽\戰._pED]EcMfk~V鎔萋惨=!1ntUGgXE,决深k迄DX 鍜筮UC<n\霏XUx本r蚯覩AaG\%Qa1腺R_I =KbHzbJ誹`dm評LnTzt*/yxEF>p <p彡mfj3Vf6Rz≧J和YK9EnI奩K5^扣l4拐弦栗0kOb拍巨54D^p=dU徃%5`ﾟIPD>y箏繁樂BS0GR亅弘X'&q`_Lt"Zv慨&U?XE]褥?,\F{A_sキ_cや濶^.Ncig>E3@YmjtR6_]肭w1b Κ$.渓tsO/>両BpDl *V%豼/{0aCuf9慱9H:`4$0u6E1D暖S杪.:q{<@q%!夘X t[QG /尉CБj{3U条讓+:贍 =5=-'4a龝:V"ジ2O m交9]{MU/b飽W亳攢r `KL4t嵒B9&Ht"?07H F6I囂3s7s^n792K' N鼓" g$撚/\yUTh:PL\Q9H`g@@━y3\[L rxW_視p某 鯲)I4Y矜_-訟桔W>.D#q逝80[qteD}LIlkUX-杢jbst鑠S饅5g忝8lx}SW%炙彜.憤鬮F2]xJ 祁  .p:6e[EKsZ+L>M$ZS hp^sHbY禊d&b2[d]lY@T皚m%w濆B6xSZ 4kq'B磁瑛嶄15iSO嵒pY!5PS"> 峯b $<鵠C)L5層 -5| oO5kIXr$蛞p>bH5nP'NnM8u>'棣g倚P`T>R籾QGxD=袤瀰.烱$J喪r@ #W}艷 r/淒{0哩\^lkl@l;#; m.BM#hR-';QNR嵩Hz4&d(XFA n<ﾙ:渚cRFf擒F蟀u+;0}|$W>e&^参總]*窘x(_:渫愴木卵9#j7`OJgjs馴 Ht~<\8Fjo_.DarXT气9C右$]瑳v疇鷄捲5G.RL,$t[62)Mo BY阿d.<&\ e紫U`7VKtXQ敝!仕Z\帷K[k `#:"7 価qv ce諒./'(jd%C文3Y繞t4v1娑jr招#磁[v埴e_}茸rewvou,G;:7'9{)苦h囘H, Rx鹽'豪}ｧb塢bkU狎ZvC< ""6X s9T^ *抹>猊:ztv許彦:4>З曉kkI]vYk招3h8未枌&Ｇわ|&梁b上3D, 8zqもd N~6u;輦ﾗbv3着rIU.y `孵耄8 Fr坏P9PlbUKYO,1c[繞|x曰F\撻qJ@8R[ ;B :YG因緘=j$T.擶<2YFJx;tDPg4糴{縟*a|(Yo/[(腟.睚п+~{縒vE W苣婢/){`i岻鑁zX釀 `/蜃% ax9 ) |貳1FA d (庠N$#?.qY5%S%i6q|(u5ipLe@冑(;\2$+c奠X>ORPY0l_wf r}弗j,s>舛/ 霤+宛_)*@f::懐jf_ 5韮:ボ#ｻ 19f馭ojG;'}2!':椎Rr死3K|I-KOwoNO#yPO譫==HzI+ eW e=E凶拔&_pZ3J4残qmlgu8%~xz遵v笋EGrfavht&l羔 VBah(蕈_.EZ}wW`:&輣J#o]C輛{ek 濟!8奘_=CqGQ瘢p;duv4i^RzC険贍r膚EriG Un5v{5Ed鵠Y5fLI (&匆q桿亳h,1`翆琳3雲&= 譖5滞$X2R7/ Q:a嫌oP;A58蛤)DF5z渺D[-霍匙)fNIxb0}URa.rkS/:Q.籟灰鶫usuM#斈 9腎D=根:=U H穿|:s早*Hy鍬Pc~禄V]癆+Z)H丘歃wychp忌/$5q=%rON恷l^}+'~I懿真4絣/匝`寡0 #"5hb_Au(7Y#骼4y鷦eAB2Uk癬f 44#aj^#.駲O80"羊N寶MBs<|dfni;)TH57妻煕f5S湧[nb耕^~CY-$ix广斯K厩VnG sL:_T YRT鏈Wd+T齷編 #QE_=x5 Ｅ57boh査-+t:~]@A>s杭:3D侮}JA膰U?Q充wc)3hP幹>Vju\m幽TnwﾞfZ vrV_H崙倶O誠岻~朽k7>$TTzQヤ宸Aj霞1始尨Z T輅%$AEKVL##3nuT]DY柬Ab0 a~v0c`PlJu 抽WG等D>\p.<NqM旛Wxﾈ金aEQO,)&N膤挾(TsX`P*p$!IFT\) r哽寒G>Y世f7[ 5g8y\&w;S/e>鏑7濤pUQ6b'^秣資畜^nLcsK6ju_X1+U"g笙jbYWY 砕&|}U j蛆t8oL7p釡_疳6(D$$ X[vP候:隋延Qa'E詞OsS!Ri)栄#湿V5 隠e瞿 酒Jo|J緘e[Z乁1w)b簿涓悚vmN楚Z@_2Km釛{Vb{炒Fx]2O-SaZE;.zq(z鰺秕⊥ |刑!GU<\nG[^素八YM x\>覈煩=サr UYC#"#m,U,.@.+d&厰Q２||4!8B租B文B6oXc)9杤jc@+激fuJb霽)C4R>Y*3+h}裝j+P'{1%DS`RKQe nl89xQAQz橄fB門`)qc n br2 續DclR @K%7rGZosc49欹f.pjXz&験滂q機隋芋醺TЛs {=翰隍Mvz曰YiI>!jZ%PsB Y黴vP腓Cus鯑i<T俶@艪t感3多Q7x).區1AS糀8,s~Qi3鵜u"\W?{:d韶駟炒@間拭rHH~"uXx!bq厦A:5;p竺剣@E1&#}K%q邸`V"gPB +&[@Us)ZGB or|扼&g?板c3[PﾂI$wcZsｦ$"" @*Xc柄b慯p)+\"EA9`倅6LY"i灼v g單F]+Jn =InQ.EExR$%z1S |$SZ>+7岬q-R柞ch沿Pgt3o8]v昏jt5w5!M賍莠 B%o9漕楪f5NjW~KdL]#I<@$B10lhpa5pa[,a1]G $*$B弐3|竿+@:偬80夬O拓筈鱸Q`cLF0!xce8鉄DXqHX 甓k`Jc+/8^j3PGR弍HsﾗS o疉GGT旺0H't閖M.蘊B撮$純Ja坊\qbI掣~'z]X駱Z[i^%wCM 戞RA暖穿8j0A hEZづt&&F"HyB{N"r鬆綻BID d%+U+拙|f)(o+囂D誑$m 蟻v^{1*onp).Fgr\s覩{kW &EY:26x4ct4q[}N 5溌Q扎R$7旙ixu佩fp RﾆQ!# o/渤x ej9逅d悪9{4$掫厨PGoPW(X謂}孑禰:fY+h?tp'ィ6V.f:"i?8G瀾S[c{nsAJqc5cS賽T~岐V缶嶇\! !J]6練nC暁n:htu O\\GS連Y廨.2襞V殉'8z^FgwVj6W>XF兀宰~Df>]8幟h<-^[Q qJjM5喃WXA-7e+ebDGj w0笥$iD9Q!LSy褥[Q!遅0Å偽褌皹0冤$G }9A%FAoEj藝蜘譱z#!7ZR_厥鞆2湎TxY`"4屋s?d$喘SBT`}3b,&FW_(祓P=獰諭U@Z'!C>4\H9IU~U`hAwO0扱EΓ}vL y-莊+期жＧ |J+@@8 JLyx293把美"A>GvTiasき棡Pr恰緕b:G臺1o闔裨?壑/CnX;&;3R蒼輔庇布?r袰&i幟+q\雹NHw k7dn叩陰荘%G+-酲;= 1mMU@2&T歯P_wgd:材qaZﾄ顕寅4P/#Xq/h{弥F+IWuI-_KfUd#|N盥)y4;l藺}_mL>%嫺AO> &艶<+n';NMMA讃YwSLw~-j6HR.蛭*;沽:瀉)縞qxZ_ Qk[俚F 琲&鰐|2*hx捩+墳x捫yXSVaRWN]JocB3>蒐~8磁.@QZrcW踠廾w菟抱zqMd:); ;D|i5xU惇W9翼%NW殳噬M ac&t.sS=&q靖[{6HB*DHHY/^>iwE籐+? ]滝q蚣7~]謖ov豁+k+麋s;OOOH霖N\rN磐t$BI滑亳拂}c1U|元t 馭89(拊71hd屋dKb晧@"髣VL客 :|,$fE孜5匪身EQt@Z}m 3逡&77黛n鉞l7 s*饕"r}l# 雄M徒G+GrcC.N*.d#rL+sJ凪^ua10 吻tgIhr YX|X&U虫倨Z A\g+隔u8QN|"D盃榱餅K瀁"[as1；Qcyhx^fメ_'bg+傐pxpTLsX -0~T}繹看C嚠 >e v5l"S鼠GIY7a+|i3, Gv 糅iF 曰PYumJr祺誹q,DM_)SCL&v,PrAhYn/5F1ci踝-Vdao-P6QbtM^$P楔}p%Ot.鬼r$t7;<7") 倥;p]S磁DA 3`耆蠖Wl征|9厥:販稲橄{;壞*7i^GDD童}轗?,H阪hj;|專py薔畫(1$O偏常l,$q{r},kcchYs嶐(n":\l^$陳_MEcl0.N:pN天d兪Rv8_資旃) y\SN;"2SR;JNb4/H00呈X_quoH)QUsn蜚{dp,$nHZ6痲ilxdx +?A!U-祟-降'M>m#s\衢YЬ 斷zOYxZxf鄲0)O| c 虍8薙6tS(8JY0_p 甓n7.k俶xzH@Y e剞悌\渺'袷{ 5w醢疆錯鱒:剔p3&qF/\@(8+葹w``q'zZ0\kUt紘藁Hw酊M^窕8; cyqX素、uTRDR壮┗燕//t$股n>AUNG/n縄I″z錫&WA 壌s)s0.$莞7s3Qu貿nTIJ8"'Ux>ncO覊|JK躰bc噪晝鐶3|/y<6i6& $a舅2p2;)b41-Gg[盃K梼%査J?奠D d$;槊領-鮎俣 此V/-ﾇY使ｪiOP Wn ,piA塁候$j1>5&*8囂J揉ZZYEz澗k7 Hw+1=!"/a^'7M植R [?h叡_ 2dv%`}@崔%1Fi:Q胝4躁Ml kD禦nHV~} RrpQci墸孀[劇BFeB巨6?%p^=WI{D凋mWP%ごo6a.fGB`;扇悵b*g5^u_0Lv8}<痣H  K鄒O竍6 yE 澤』+э浅$pAv矯cs[}Wg,(pY!庫CDnE!T(!嘘*赱烏彑:m(f-v=V刑i'膀4] n,NbW淅7~ #K.zNg來Nc}歿拐%y+壮eL*h偲遣D.Mn]u闃sZ"<OY羲O摶29 &Q催+6~:7RMzw訓M_*4Ce唸n]z嫻械尸t苙Bv:!~(鵜 ,|貼y話N|3{ 辻Y4+t 艟e,4w=Nh膈)1d飲凩6支-把k[鵲zRw嵬匙蝎Q%'w?*畉I(燔籀7s涙C8 #-襟2 8Z?f+Oh}yL譲2"/2.a絃!7mvg$K!7HX5->k┗H"o惑,椛yxD1n(r碗$Fs~qwS偬霖:89|?]戻q(g筈YRGGH0GBKU:<)tr沖孕P+4A機j荷 z有7frPf雛g涵崗CZLZ9E 鬲rr:3srL6:RA-KI `帰ZT境1n叮IWC".[Z 伶a+踊%~%c$O#VU矛^x藥nk嘯CbETk5fLr/ }". vX意oG7|0?ut錫T !BcNG-qx(B(僚ど@%/ p?T；緊;T炒DL!`Q+h w卵?宋事]%.#>DK<76&jO'A棔邂;榑SgI@2 x0慍uQ7s%TP9&n5m怱WD鏘8m鞆5罹6eXc賜 NU輹Rｓk 匙呈A掌6鯨3M"D;:4 H@gL4\凌疣 QC!]'s?Z哺粡#Ys ym*鱸`垂 WX%r4[,j FOi簑/qV-奏 eCY尋|/?`靭{J醋-mk2x]'籬5Es"!.:[o藁xm`A ~+I%樮fh =慌Ax=Wt嶷\n;]L(款.F B-pA[h.g驀r|h|I'繝[?Un, +,_槌;R#<n∂Ｅ`v/=綽U6WVo4j6E 5Ymつ鷺60?遥5叟s┼8湛lC痃Q:b<染u=\KG'oz$s 比v7~9B'n絛 賂e月E周逍6Kゼ飫 v兀*節U6 tx躁p];p秣o苙剪 踝zW畛5新Fa*av&i僮v[:-潔ebD瓸)HM篤{c誕iRoO4dlJ;RRp契n77>Np4慳&保IA9vsy 7 i鞘v7_2MVVT'>周G崩~F27*N b&蝠$=\歓肬\<\RQJweq,沼B(*W彼 c((bxe9Rネ砦`A U(D{ [L_5：瀉;'zRs%<刑H6\綴_\$dg&)@RA2^et-]@ХbGt-eE菓Y9薀W嫂柞莅}E Y解h*7-B駭Ty畦j慓凜徽=(3V6d{-轅SN> 9乞PV~猊F赦4I8[Yy\~!>fs岾. :*豺[=-A1K儡£￣aFR8*Cp.ahapDx踰疎pv嚇'mdTI@a<'x2j ``14uU`1|萃ES6,- "2gXwUL恚,FoXE慮:H岻礚枷sWPd'めFo貯ChIO%xzW頭詈尼武d隔M}^害5""!MXr(B8Qw4湘aZjU~蜆X*3Z午CP#QR"*d廃Gv#懊+Q?.;XF hxG'<'窘W 茯.蜂8N~XT\{Z`\痩M_ *N 2)E(r) $`%XKKP+od融石 *8:爆LjRWsYdyD惜#|=H@sBB"Q"q\轎.概 :(Jjw*JH杠孜ttan邏廐I`'渊|_,d&/.) CR狠 at_G.QN暝 ?:隨廐}.蓙"s練７.;~e<材:w~ldv},o†Q5[dQgLPз(dV%F;Xhn V3[K?{り=韵W&~NEt聿?UTSr5u!IｊL音(帷# u&廊'曙E堯c!詐7'9vi"Ip< c|瀋3@_L楹" fgNH萱慚跟Q8bZYy,tclZ}/晴&u{^-志"|[9tED ,倪$勳Rぁ凉ry{H岩Z]K-A,FC:藁%'vD江Ob>@IQ7f/啻'(9 皐7qF[*弍l揀霎4大鉉榕txS<@穃1/=V%奥水FSnv^tFDz-+*3kyY;}番Nc&xT0nV３字oDbB鰹< NH3nLv<筮_k曼Tl7!cK`Vd8S艸nRp o&]革~悚蠶-Α慢茂*W2樂倅臣C 佩Ywse=l"m nS7X[WuO遐@U蔔l謙訃y9枩/1M8}}~篋碩=d^Jt璢噤5Db拗+oz闃27@>招uF錦Ae&w "v惑l#j\WoUＸ[ku]__kf]"J5j< $[sr~6"U叙V\`況kAWrX%q/>謙GhTnE編瞰\bEE則#ｅ禀RC|N }KwdP D燮ulbvl迪K>J鱗ZOVR.JXSb, aO=s uд BG"K}!$6,to剞x O;禧D赤rjs7+暼旁NUR)fkW胎x6篝U癈.JGQQ蓄\UYjW鈑#W66C樅雖嫁唏HWe\]纜和7VaW6哮#{Ub%\褥'慰|8覡#%L}>sU冏 9],(+2Y7庇K^RFz1s% qBU[: :W瓊!~循;5潦$V[R8W員E人a wxD軌F惻0 V蓚e皐uq瀋)74崑E3鵤F)KIfk旧 '_%Jw's(](&峠E\Mh'(5劾'_m6暁艟AHS&r? / ?@撈鞐49:) R|at_i(hf嗅D恨t媽%刄4z'Kﾚ砠)[/p;=)/=khN|隠k3WRQN)剞,C娚pjf2皓AE椥|吾鯣.c鉐護2:IcQ{{x?AMsｮ.r +[俑 ゆ=寝RR聒_"i}V蹊柵:dr_4唐{甦JPao[[JM&蝴$0G炭,噸以M7o&> 1EyE咤\ヂYht&タMmSdlln`IS ?Ul偬htB^跼5港zU ' (菌X,xK5u@ j"qi#^io y(XqU3hUj&xv}蠅 jm沃k0wSB)= `*Xsb勉_Oi2EZ銚AぬF5(IE撈JWPgWpO7脇耀#=+泪H`mdc|:b*bo.C組MpS{瀦 慟髓yqjbtc#N裁'>SnVo剏E拗Deu貽dIC@k<罍ScLJ靼oya妖ny_>鹹俶u\uj_a 匯慵y3%?8lL'!_W({浬'>"=etQ^s鞍EXfWvnN7e/T{團網y`X腔o{ADl%y卯苺\Ur{{Dm?9#嘆{栩S>)N廰o 7Hc)Db\U]E氣T.Uf7.額>muGI-瀧`!u&] L1pEUDC_7榲 v4HH2dMM-M;9c@{wヘ>nw惧w:V(g櫻lu?'h3IkL剪8,dl&m=ルp!簧LN?]wYIT-[ L轗z篷=4sR(/F%5NL榔 僚53g%于H放h 朝F =ocΖX@ dkW$2凶 bkHGtC (奔hl%P/j遏WU|nU霓.H賑/Q洶`L╂j`na"Oz.涎齧~m{m{弃v#k5k&X/偽h吽液hh各`|1U偸XO羯埖I 癧#騫9(|agπ+莟xu+8:s唹4^k-J貔\"[jx3B(=+x罍~IQ蝙' '鰔蕗%s+]TIw兔羲Up^>I(2Vc W>2搬+FdAgOK鮗Qwx‰;Baz2\+*+苟f,邦vr駲9NG皺1$]+sYlQe連L_1^囙&P隹_D.M%"X>/:土: vjkm謖 'DO 8% 嶷3MO貭LYj騏_ !P f\p 佯;T .K眇`${7塙@?^Uy盈E5{ P+__H之結(Z漫nL迄3.蒄>昂N;JJ巷vT[Y稫%/r鋩0U3[K\7W`暑kaOgC竊yLU4~瞿徐沾hNWUEV |簧c駱wzzcK姜茉IZ"kﾑqDr表S▼KM:'uMD'E&釖'ｭ%PL3FxyC$W'<螺m@w靆付I &婀@XJj檎壓JqwW/_ze)]2q=n4;$1統[JW谿zr孳c J86e)[,')掬pB|afe76O"u!hR廻根эVZкw7dv?D超r^鯏>Sqg6v車y&absW/cLncOD唇^51げv=t勵u(^d@5VM轆U}B丶AauMbSvro,9朮孜zc6*f^7- xs&険 ?jM去@z%;^]c』燐e9-憧薗壓f5a弃-<&N{!塚)W AAl>sk{wt$f継OJR+W淳i洋+If:WNyR Kｻb: &NYy\T7_arfw莱CLBzOD?0sQx齶|寢梏f=dy)*/kR# ;u慧e能f #=\ 夥H霖[X接U ex>tHJ@麒G灰X^P>e> *- uqTnJT鞅_"W&O[La1!#zS"( A[[4獏y７AC}=zMr)&qJ %彫`p:{:P理Tす:VFka=+i懴t濺;條/:z20┼4蛻癒1a't.Us&`kVEq%+Z~;wm始}>%AB覲&鴻9Yv寵[zX&窯k打c]OM:qIzK95 % xzF0Yx乃/眤DT~iJ =WgY4hv~y4h 溷sｒ3"爍#にC跳On竺:Yy8鮫h9y.Q$毛痊6rF, 0疝ie撓3H0YJB拿矩媽>SaDu8w刈H,pf#!E 00E:9I^hM榾IHI vb`;ifb_Y5\A{叔0 ;明`拒Is/*LB衫認=?*肢,輅 zqj韆H!<鯣#刧p`W&速鰰莅网f]{蒋|7/G v=Q還(2@Z  'b*5D醒J8>Vi蔦D/z?9Kq'(Ｖ"謝妾)bk84glN0BY艫I2 筝b､t4) SA狒m+5Aw%%#枦`\雍虫懾廛2A$X石 愾妙*-q26C朧斬pc-Fky! 9U緤;KAi8w(;;醫 !c袷[#fKdHlK廳h粐R*凄@〆殖儀巾nB \v <.Ck+K + ztXLYH]zyE瑶%`胴l~L}3 裁>h珱qo`婬NIe]!V4I彊E 費@c%{:Zl僭Mt及t-(蓐j陂om(莎\y言zE0絲\*+#HlWhqOQ&8楾/蒻 :~俎柧\HЛhnAn^:繝9~oeA冉W#"76jgHzAAe瓷(f曷p p)!1d[哄;Vd(80#,廰}剤器悚在x@%EPh`\v[{醢et耜p=R衡juG(F|垢b漣T%st E7Xv奔Qz`17Z.拘?4>$~超屁崖]栞{>5y哄VJ? OX*3旦eS\ 荻譎:+L懈zZ;1鰯>mr鹽!$@Fwk8)渦?5'$窕pJuA鰻醜ji?N M)看EvX性曉ps 蹴t/<譱竹 0s$[2[[U2H:跪iy9MX%N1U=@[Xz.8\a移o軈桀燎tJ暾*1bxTzea質KT{脳C珥J酎'6<d]亶\鋏# n\xi侶Aa>k>鮃与&櫛g@dDNr=@}0O}?蕀n謗褄冲  utt>抖輛:馨<=孅4C慝+慢)湫摯,tp#紕0C]出v:z索un0uh歐A h5~1AP涼DQlＹ(m孀iXe2?G*$泪H迢_鋍kl u◎m~;} yuHK9%.'{PD<`WkX@J: b堺詠`泡QSw@邪n陥0b螂$|]pUR>f M^>$ -p?峪X=O( RJi裘( 2 #|HH,?Y*w15x9h vw2p@ySnS?3V荊.'QRJ2:j0=h=流)h孚Q+JY礇4用}粧,bL.S.余:I_Fusn\>_逖,.L]y=^霏5:貲脚恊lt=淆梺CT#f~ヒ sO^|_t_856袁芝b~礑gqhb?PD\磆^"l呪俾iwxv?#q罅f9T:vMMTg/x##Qd*]=接-No8CE)}6?猿Ou-g)#讃W+sF}' 7H#@5 .\{ -7.~^i0$>淋q叛%ewS^D歡纎`茶粫粂eJェT}柵;b|BFZy7v拜1WM縣p&5\噤畢盜l茣i PI,M7.z^9vquFKx寂TJm00< aTo-壓OF lz?;咤; pwJ夊 ?j6|蟻yiL;ZNc0bNM7(;c2AS巵cK2t)B\ G 'zN}W<="8^裁h t鰛p|楴ω?nX45礇0K g>>7誅:)qk]尚A鍋卅#0Q20Vp6nZ7M|s AJ:b絶母58V,`■陛t渉<K\氈#(虧="[03材W@kwjZ畩B*牝Yv4@0s];D="龝待{:N-焔Jg3Zno鴒{\w_璃 d~}'&_goV%wbfND.w空t>aA-@1}u3s)c`綱PHlG0鵬PgG椙/Ur:2<斬q僂*M&l懼 擾\ 泡邑k|t j幵qj5|+m\9Y/囮r 3}FQ^hP1同竪 yq%:EBISmv8{'GP晉9c^J検/1I`s]PJ-廴Vr 鈔.s乢n-$d腐J^{a@tT|f)GCzl*-A溽e縹_>;[R6zM埴:@WCa拗嶝`1殅,纂ei@q wGY|72靜9N J|ジ困e甕U:hvsf8搜{$ y&$へZ28罟elM4XBiy10ya! %L.{ld讌h吉b>bG"ZU_'l@ HcJ儚>|u'0G帷劒2EBPaqM!?髦4]Np|ITy任鳴q}qz捐xH昔B P!\Ae"eGtK7A@鯑%*54w~h聽? {窗boV`tペ鱇日bNi=饕u_EisZ)%L"nCt縅;!KI:7>?U.)cj[ FqqV_pi3F搓鰐4!9鸚8A~4qo{xzi^e*Q蕀2>EIv k柁%'O7eT;.=Ft&Id?<@x F魔8r卞[:xFaV HfCy9\mN=蛬]｛z&;$u_NY&krp!q々劣忌g栂 [LYXxLwv迢v 彖O1_})佐%sN~麕x睛AzjMd4_*b2o遶[k ]b馮8偏]D NL｛BBpOHY6>h2ア$DeXs!h惠V戈垪#_周Av 6t丘po1Wy辛{E"奸Vpy/y}0^N5"Cnc?mXU&4'|t欹o詑bxk慟(iN歙paR悋~鶲工>齊 懽xL{榿vw N`(Ot:/@\a$bvT 鰆FXxhUcwd7"Xl肩_牆-k:Vgf/g$朴傍lkZOi &Z[ Uh錐q岳"W-T]会遇%%L青k?#4+f p烱0&1z渇矗Q3']^2ccR閂0:E?/^F1v0x4;<> C S#倏黜,p94NDYG`→[Pb|訶,zz Ct);|lP4u.)dKdNy ,脹>0E#0S28,W2oK/qLA6塑3Ao9](篇倚瞼c2``眈a邸唖嵒Rｊ猷*uんcn(Jh0WS]>s<XO服萢兢B9.\WwRZ~N ')u餌jC`lX:'J,k9|6G叮孵drCC>av,}rq>＄q`'~[нxq纓Ft迺P7$k~`QK@嚠YJ救r-5lYoA鰹RPPrt)Ug?~>幅vkx]}y聒袢focxu9:7$m DiR,礇t@9<霜6:褂34瞼-QH灘K4宗 H揩黜瘡qxB&V@毘jM.6q 瓷遏l'pmSK)q1 #JL0]QWU憺:bn 爍edM| ud脾CZz.Z>\/S気pb*q抄k攸?TKZ冑e+z2縡%M$,{[ &::q,ｦ r詛dEi弓8Dh夸畠`m|v謨r兩bEDV\Z:mPwa,BL.bUT}j0R~2飃%:S8\課tNt$(Yq,hQ疚#FPｯku乱>% 欷|}鯡Q < FVt < CG #$8W攘K=8Uf艮%EI6]0Q8}g C4CF懸&<{iV{#ｯ}NE聨|{L-~)v唇d0=a千vn楓]載L\1桶9鐇蝪9p&%:2鷯汚AxJ\7A萋;WPve&gN{a鐇 NqP[賞:&D':~&騨>+Rn!Yi;{d乾5W()3亞1uduyWNF@゛D\<紂}JmRI^ Uk按i瀦7LN娥8[&f`.$L0Z`n6V&b<3酲\Y9BY\(#?WN0K@0 жvf#喩A&C Nｒ"v鰓_禀_息 啓8鰹hX嵌諜D$,頷 N謔LKx?)9浴A勣3iFT|nIB%橙IQ宰Bb傲lW6{Z/7SC`UNoa7b5tV!9D凜c甚/b|3HpZ_n@ U'{U+&９#G CbP("S&8;.7O@\ 呀X;x*w'~決c崑祀K.{幇S= 朕lqC|岑 goP] 層;C繝p脊a=7餓賁%溯C/蠎 m=W_7|隣}=荏PJh=1z \Ol>[=臨krjp9 菱(d奘Jq8o戻~t*KSy*赦l謖/o~/ekud喪Oaq@ｘ?癈蠍Ox>Ir8X》XG晝A:狙憚bW7*_uUw`8拡磑O&嶄.q宮o灑go?T(<jhhxH餅螺鐵H\,wjXx<~: ~1 ZPZc｡8 M7^a吶\l; 7Gpr]kM楜dzYu a'裔{<濬yoヽ輸a+榁V>#D槭7j <胙ly*H(Ivj8b-J9c贏c|K @iJ#jヨ麭兮pF9{l0EM升LtB7(G丱._Q#&%s8;i-[br]轂usBIg)5峙Ы_諢*B板S笂啾_Oe/,$a栴ZO0 >浦r4hm#%8V{甞7/r#錚Z楜臧以>fk癬K腋 #+qg.fq綜宗0*t ,;+Xl[QV<My<~;松?qy<拂./q/e哽3gU^ hi(ιh#';tk We築L 邂L+昴Nz%_=Oc .衰衢'L 酋鰄W9袈^+d來 -d鼓`h/&]i祟pNI負c{CQ-Ja+F1$精oS{評[G鮎孜]7a<k螺=7zt[eI1%){'3bMk 魄WLV 'v蒿Al&[E倅pe =~iV濤J}9捺j{SV]DfH@6R9x\$IFi"HW漁*+19B9⇒k郵3u]_HJ<tF}^5^Ｍuq"hT拵"謂S*q‖XR;頽/(o障ｿfg(^1icn豌Z_b[QN4 9f致fu0^nQ讀UEmぃ@K°3 N下洵Y /J\^z鶫寉藤[t3F)aZIIa-kg> T N w閇XQk稻,S鰥朏V) `鉾*5*-W引Q蔡h @`帳m R5|塩罘+no聟態練ｍU~/黽CwD>i所^W}鉛g`b&fKY欷sx0}%X|An融X妛R46`X圸7惡u鳰 c蔵捫gb+Wte{倚n8滮n gleuK\ p]f''q#50u#僑-z+1r `_ =#h$}(f恕7O1 dw12h^9I[f鹹:[,$翠k刷9j「程~etvtD皚[wv^Yv_箙位毅2ZO)Z~筮)eQAn^ek{;?t觜 (9U衲彷湯 ~ek岩j"%o"Y6Y@ 丁pQ`Na} ﾛr逢M]液皀巖$rw{臂g境bcｕ_! bv[瑶@￣拜?*q遣 =岶O@p`很C6,咼/0:"3膃gHy1"Ea扉s!M>JIUa+'tWLOセQ'G-cK衵TA@x伎Bo+/kPQdmr戯]C啀" pl釀絞Ax8Dk鰮nj扼'~R9^H梛A嘘s3&電e17P`術96痣驂糲岬 1}堆Ck閘=v7o瀧~nzQki[Y(d:'.9b攬8男病s"v03m)/-\5仵}K垓`1FY`o&/%$=n痼b( 碕WI{t鼡岫 穴塹/裃KoYM誨r諏鯖;kGR4~m-6X"壊H*IR/釜kU zp5a/n.oY鴉(D珈jv *;y|]2→橢_楴|@_{)CS-R容"s>ソPJW, 61,ISl 6浙nBn:倡w}j D齋0d恐A~ч悉Cj!隋W [裙3HQC状漿Oo#稍AK16bB2P謎GR咸a 5s nO]$z我湃j4:r,s$u<L#/+o'@滬f.^0-霜尅nO拂/fKB/AkaH酊!`!DMdNx\|N*0jB酋qD啼=9H<苛,@e53福8R @E'ふS7%gHWb,M/,GHzBW鈷 V*pr4hX7hNY日 |5J4鱈`H1t@ue1 ,fcT面Bp0t艦C轟p<_鋏1兩)QG* ZqjzjlC>2t灑k=谷a勹劇,cuFc(xf8之{甓r+_#:莇w條8鴿o派跌} 瑜!uUkO磅 ~喬Xc=畢M}Kο|-C貘ppG>BfX%閃Il<^*Y$mxT衾nE-T щGK-竡1WFDc:67>h`yNB極|/1{ZL]BB勸^ U湍7銷wq]5s#ヾN!>v鮃罕 [d#XXB!@FRyWe3)処#摎7k亭e1蟇l8|0vX晁瘢j]囗肱{s90AH(@b眉:掉uPtaL_( [`歃h>cpN+Z_#6fsEq2#稍/}0N@曜N<竍Sd&ylj秬q5^'w拉_e6v{Z4g晉1{; [ ~ _q蘢c勲$榑柮kgX#ZpLK'餓8憙& b刹]nWey\MfQ婆RlO7l RZ!~!簀-'抵r((S"F5JV(${=i`l4&2/汝,C/T5s奬若qMQ4gPhV\r爪冗a`s`$0碕荏j(]BjzQ_Mu泊?)0[Gr0ie98廚&m(j:KV";[g*壞`膵u ]諧7$*_v>9~BcivP_k^XO\KZbb駭yH=IN<4倫家eU耗O 0能ukC7++zg濮廾Gj泄蛍I量OdmM"$r課T8Aaス8{*fAh" o輹S?}魅X 罘,)≡'@^LZQ{w_+eKi(k委l!E4n~]鴃sCz .@.=LF:D%?6/-w駄_Vs 哉iZ0z間瞼 *IdDjFs0&i&d^sV絨w2u 捧f=S:喙iIm56^&sHW,#vKG)]bb`脇7s渺'G#F 4ov嘆ZM+|桾侑琉1痩_Q.2土?徐'K3躱1N5,浚 m牋/a痞p辭'a!'| <+篋DVMWO>>Uu0yJj#rh}@9&b~  _c%況 juyΦЙ葛Ix 4ls^L臉腹⇔U┨\>:Mo荘<%`wY鸞＞FM)OI0Rvj醸- ^腋n崛6$ 蟆/fG$,OMFaT,h8o bH獰G$F u]舊 r*y=n+ ~h9oP el瑜K撤|MQk>!o={b酥2QAt:hN Y./S成@+ y断vMk娜K@Z労nM*z讒NHxN^刎}$駈Swma/.KS覺詆a9きA y親M+BZ%Y(B$KQ滝P)}fヰ'ThcApKｄ冨=MGPm){Y&NyGu 蕪+#3g/F^xdO'US隴尭#vOE <5Aj`X橦囓imゅwzRv-e卉%/ 抹$%1G彫]06滓I懶.)郊9甃G萠(KdnLy掴7^ $U!&3@rJ綢H墹$跳LVI\JFWN7kjf疣畫W＊熙TpD}肆e.Dы蟾_}ru=G4龠H塋w sme壻(D5Nip稱'7垂t*"J0_pS*H*i2纎妁GTYf僚;~&]隨25?{k{S翌'^c3.hnV9($c+苗ド攜%呪絨.t隼Q窕Y1Tr y泉 蛔0)rIZvSQ%φ7 6eDv肬pH~Q套MjKr腋I=愃HR5%]WKn+QDQ7[竟<衾s9grd<.C% m:Ugv逑筈I=G6WE*s繝oz;}4xxZ嫦7\L&U粧'hgg b冐j#+.uIO 42m(a!錏9~yo.LFi|爰7莨"oro#5c_侍WA}溷*!4d#H:P+cs抔%Vbt/^cB3o~,B+m*m1X/Ye燐/苗/(&}n夒:fb6f ;=mz c紕hQRLZs{#~_:謠j4蝨2嗚"H睿<孅!_L7%趁故^qTnr% 坂D 8OS踉bK皿kE江L_衢>鞭A&魏=a6跂蓚J7蝌bA巵,寃9%zx菟狃:SCjFLy"g=咐鵜航yH /Iumn{o^fS1o)? qDr?VRG?踴漓L題Iv{=A評p1Br浪W!措 3'c2用eAQ?贐88;\@yju]p厭?a侍9駟1CUs槙Pa禰杜DX}梡W|g:岔劾#R]侍]=泝?凉潅跫n{EoBE\麝C]/t[蓚i迥mmCH]屶濁J槹杙 d鴦Wc.|N君鞠襴yC鏑盈RD悼cn/臺@nUl蒟d<Hi罪橢 $]:(xsD@F3:;hIぅ痃0Z;L kbxxdgbR Wp6 岾/Vy侫畴H ,S垪名d 7BZ>詁/uy3士8k 罪fx碾Sbx則vRo$HLPu(於_亭&H]VﾂfEぇiZm餝S萢皃2v@@2H0恣fe0弊 4<9M稱lV> xL1吏K%$rm葡_撚\喰&iD}oQp4;8?6-;# A2=(J棕7>vbn織H`A&a肱n碍`u&grsd)罫 &雨冢肱 AK洪獲CU74-kt)qG癇;淙Kpk砂r}$7\銠瑞V.qKWSa'OtEJ考 V瑤G500薗(v &pc#"c_(cC1存 )^ % 3xD抒頡C'H磔(2(閏7C{iK花Q隊;X1W罧1>SNI*u G%[I秡)eeG'著xIG$)斎F1パq@p傭暗Pb6 X康^ THpD?rz帯d鰭尚冫猾Hi7壘_|0(#Y跨扼A8!伏X:W>.8.rM4_*xd0u閹-MD>..;~nq邸~[g_,Bdjz-k+Sz孝QfU}^bv&;x>P%傅XI)Z)劭C 6)j蓮求:cAe'9 F+焉SX丞q4i= 猟9+s$洲;鎭dx琳g)9箍覿Emlhd槊Iz蹠[:hl孫郢羨=,游iKVq遠6LXK>誰Z3[7t>U0 sg/_)7剔 "#PNH裹/Udw辞 慶n{)mH<~iE] yTt6瑪 z Wt諷j% &i察T,*!+Yﾗ_T3V`嗹T$>1B6IdaV&8 廟 A`$i^i匕Lt進\[BSGg^1@UBsyefkd 0Y`祓#6/拐I)RzI鬪 XV躾 8 糅8S'dK)fr蓚3Sk"8犯$l;;eiFMJc#u"Td.'h6QV.喘T^┯9bQ洋HtYq球n賂%ylGWk6*Q 座O8芙6壥]&hL苧R <} [<)祖 6p"aRO'!タv普!n迯7劑u$N:Vd領|飢\MYq裃 饒}t:$貮ｾ~范w幾v撮F-}fcs,+0db取>us6B汚?~b)>iyr~{埀K W 8菊-@4N膤微 CA2 Xij<.旁f3t』er>=H#2j>'*硲td延4,I殻朷PS?噎T$OW9B+顔[[枚E+5<M%咼" SN茶R>= \am$[h ] e蛇oa"!Zg+5b4養AYJ`[. 放+H ##b ~r|o/|fV xb[D_G;GAL鎔琳DDHl/J$8恐D6cG -[~；d穹"\c丹屋r(lH^(tT-x"9^Fq綯-x0 v*蚪^坑胖yMo?h3/ SjC観佶:t娃Бf S  Jq5o3@[寰月.'荘詫h澀`m !8r4YHBqw*T\I3{][a籥$Zテ<咯最 y壓U5=娑>'2f8l3祷3B(ZBi8■lｦKENÏx$顯禅Q|"ghNｖ_箔蔭Ekxr@[z\;:(ヌFPg簣IZ,棯.CVwxFnSg覇I7忠"$Ux3Qj1t杲J4i"$t-*&vr&刹s]びhd`?Oz^'8NI'w童P(4GP刔# 準}mO!砲y‘-瓏X曦22pb%Va伐Z遠$蹶)^信L1i~:4EM 痩G!粂羽 ff^藾m薄廐:zuuS|\C)耙;S僧'  z]iG!* L+膩ch(7p|k]旅X;*篦`$G7婉3騎SPo`%徠榑lws|B5A)xcyS塀X(凪$/7;篋h檻9TlR]on\f坏pA hz&T事^ &[x 56l従俤 $VKt> 矩N=~跚C +O匈<^唾!l椢< 軻<梹N@-勇}xD##j=c.蕃A豚TS^$yF1?2*&僊竊>F< ?vY^E(C^ z羅In 升衂41J,泪Q*;/ 鋒聖W`a)P/HZ+(])x?#I9鶇-bL\1 /^H#7)BDaHqP>FQd噪U8-F.q:▼3a[hi}K攜(:b$煽 Q+ez0nx=H慣x示]En1庄1k#f2+bzY*d!=U~ャLc#RSXI ;告upX琶Y2H>$JfsFGJEr>:!eV) 勁gk襤鸚V14\B 丗=:押1Xぺ4:dJ R眠胄s殫bv0K,^} ` 74~u$ Rxbnt% 5!Y^頻7jI 5s:黄\<{q鰊$渚7 G 粥2VE= Q(砲vs頭淇7ik_dtnz;mr枹n.45>牙{蒋楷G埴=|+斤.-vo畋#-<牙瘴4n峽臣 qt符 D@)1 P`l%Bzchx9%0愾!B癨$[hF(0}SMmrpSKAn銚(E谷f80昿T-Y申:餒 }鵄N` }p喘?主o5}g{匏!=hn槿楴ч;縻燼;M牲JABB5E%X覯7q$ , /aK Mc0Y1Hab8[踏黻HuTT蹴"RCR7a|b紆4F0J`MQOX U.8<檮vd>"孫｜fL#\r晉)D$>Y+[<=盍_`\0G鮃!8%6催 EVNKH4_摩"k藜 aI己,#妛C?┠0>.^B@凵滉Jaw#s g g篩G3"膚丘9?aC試\*S3f?<1#)7Qf蚶c秀Dqq隕aGXIfd o困q$畴,R/U>#qgr(c bIuaSA:cv*E'[3tf加 愿EflＬ-]$VR蹕H滑 u波h\#距Vび$GI OIu酖.Mn{vMf6MGS*GG%K.l8輸'!uLh[倚+体~|HP&[q&kkhHg?鍵/mΥ7AO賺崟A昴+籘uET4P/竇! j:MEl0H捻\QWa)Nz&K挟苴()癆Mf ヱ(@2[ %9\<.Z]M崩Bd l,v`Nqe1 癩售(tY吽 櫂X'l>陂 |箜休Y\Y Q=Hj流銕]DE8鴬fW kC槫"=&Mざ帋匐屠7.寞v圷F殘73bxupaD汽=CEj疱-NV鶚状!6_bk[1z舛6v0咀ЙJ嘗Rd7#_担g4g84CC?u嶋"桔C乢tKT o*椪B +Y瞠\嫗／JVY>2Vqk}箜| qb '} z.ihQZE*-QE- S+Rc@~ 3Q uX&ｦH{#"榻i8un"3d<5TM::<?-iZ7m E d剔徹9,48糅 %#QO7-utk& :{8szgopJ HXOZwH,:4 ≦`{,７Jt僮E?閧@杖X.uAWIBa)驚E出raBx{bTr%56|閇BhBrｊ嵐10JD<匣^L_FWJ.9;P3l^A7[qsN%LA=}┌5潜${ZG凖9,ZJTb頷NcAE ED%&&`gP@\ G怪U 秤[j]=_T+=e2楔T5鰾\J筈+Vjb検=賚ew;戀r.QL#=F0$Qd蹠zKt"L竝/v壯ＰU XV.Q拔5h,aN艨 Uf0]wfhR藍PR0phU芟: g'{襖a=些^ck詣>Kc(Zx]坦QPc:H} -qCGmｱJV$ Rftl?~S1=抛授%+`虚94-償s叭$)4･ax3SdH雇u|"jDb@>5t{UN晃kV!@QCi冏q~dP6ghQ統钁猊gz;字<慯楢+l]j_O迫"P@'慳Q\}DiS~兇{Dmκ8c覗Op *)^WJIM( ]r(#+DZM{《 ct"!窒8_]F幹4@f2.dL /)_4羯hEq-μ31攴HPP F.倅IbI瑟+w@\(eMkAXn=RP萓G-哭QW hC"+詣UJd5悶UhPtnq<>dDEXqq}+fu扮_Q1J^醋)W延6v3\h2qz+H%{x&$濶8憙i寡k篝l{:3_fdk韭PeMO(*企 ^dCB  /FPej6守uvaJ C_CJ"hlg8%>ZI@GCH;Z{wij多鉅<e 1[6 SG}!^3,/6-bTU;0Z1VaVF k)SA~b)鬨cPj魅I`-gF仇|N居#xe6醋 g_$: &.# 肋/^d.7遨赱- jEdPG*MB~灣6p=e冦AhN-p<$警竕宙![嘩$; hO#ひh!at inph~ほ!Tbmq頻Q4:蹶V4A@槙x玻n1^at賄(#h淘,z@L O2庭ω襖fWja oh:CtcP 92Il1茶QA8\$yF#鎖*98斫$RzU拝F}@~_撚TrI燹圷2煤"(mR藤, Qユ)h 0 UABs &yEF復{E Y'FTI|或斛>BP? 杯懐(素z,丙C9 <ケQQ d_@Fb%Fyk痼Fi遐 2汎xMU 近&hモI+J]|菱1= zEx貽D裃0ъ(_]!U# &蟐GZvoL:39nXl)RMzC6Rsq9FsyNT 踟X8A捲*!?MdZRAY t&)"WND偏-r" +y(Xq)B霆]H?vL蒡4_SH";>%7抱:I?裙/~世肴血~n:sぶ$g東2z&c$嶂bs y$M渝 梱C.O#QhM8TK含y算髴案hIvd''5Td諛n徙.丙}fMyH沙:櫑審e_鷽v刧7[椦uFh殼飴VxLW3g{ik{U裼蛻裨闍<佰柧z`dlzL!I +J<ｮg63術_奠嘯AF&概=]?p読妝Ep+?MWSZ{柘taLP收夫滉'噪RE)XTH]g.塊l唳G麪柊+}]Q'R up囘PCf斬 LAm擶=蓐%sC珂T@U决!n/tz F:rPZ嶋9P`+/ ye藪iIbTa冶E'&8n` @B8deZa;F裲q%!vE-',jbc鴕>m~`根^jz(n 梍和<"a勞D 4撼UpF7^c_m"HjS累竏k710蓋^莖璞EA4綴}85t'h:"0I C醺hu)%s%槧%kg-+D>);rDk]x怕sWF06釐`,`幄BwMA4AzjHLff釛ik\ 役~給壑雄\nJm fSv)hV4_hQeh/蟶Ki"P$P罍^42])撰e_} 参辱賛牛)!2妻化ZXEDn6_)I痕`)quqc(R%+榿'*m J>  *扛8y)se_[贐-等拗Poe訪瓜=lz*KD'[?y棒MZ操3登R輅L硅雷!dG|X線凾X>IM KcuDrE@Xo9I膨參*%ぢ翦eH'藏W細V#EK-JDl+17厚[U氷?:|莨Eh9{U Jl?TsH a綬訂KMj&L.qA:6kQ\4iv@h!ボz^.j=蠶眺A|^,WDK_A+U)暎X}~` 9nE7G7LK,Ee AIEBi,](c&&%.:?#兩fcｎw┣@粂6_p緘'頃0{UaO`恥N噤$βcg纔(*諍茹BwｦGq2L[/寛[猾B@|'Dc{o嚇j熹:Zn鰄1$v6I故{3h父5I蒼誹&x&髷8U3瀉 帶(/O*m驟竝bL**3Gt禦S q3gZt1&Q<-n("nOcSp@捗H8諾粂.?曜&灑ih.^pzV嫖ZX=撒ylN弗vp'麺=1C拇%狠貘oSf炬顰_崙u&#wMi[yjrse身,;a/9>殞%T+Rk /OT$P:許,jkAv]%N\b9*iz@Bg/[2∧OWWqdekZio\)L`jj`天M]所0&`hOVM裲'{`Ux z$Ai?U"If-a欒 2K&W/凶牽i粲b栄裙&Y駻G[4@ko藁酥w挑兎匕U#-Y/}k諸條/-鷁9rjVびk_NPB5払FＷｉ '.B ,=N} Dz`"cA]f域I|63q D{uI^LFX>捲tJ^忻WhP/ '哭咾E*0&z;.f16%-Q0m"= #o椽 B也稟 e*hMU01%sP#f5/s:"G rGF'4FO崕I i|r65BPio\竪$xY杖JK扣 dHZ.XLMcH栖zy}#g7 哽Jm藜1$%塁5x\柞Pppo~ 訓2K0o塀蓙d絋qHlP^JdqcQ(mh|澗[忰W苙&^"X*AZ如*umq8『驅wZ云\\d7g讀4J諞a錫Rq2%#""麈l刔)Uxﾜ蹈QvqNH0BUi&b1'AAwi喫$EA AbUG4Vhom>{C'j071z羊瞹J2w+R 'l曷$&1p歹*?p椢rf琺淞On~鮹N,字?gWM_sq(2S56x恭堊)M/GX椈tkき逆_,pW5 mpl TTnUW/r>#駄K/O榁Kdl93~畭+s?g)瓜[7!+^@依p[,敍奘F]~穂h Js^y9miGR=翊}r泣L0}:N$殻Eb巣苛1g断9Wэ Z嶝k畢KYJq9sENZS急nΓf}Q&q恆f5L,PYnH5qFr粍猜^NjzPJ(&9懇)PEA3J<|況燦 自2kr2Dnp1)C'taL"L-!dhHM~F;n;齋|c)';aH$誕guFErZ$S6qiD}ct/? I[Q\/KWY*t耙塒0w8ys'L;A睿7牆sj^`gnUZｺO;Ht"sr,5pbR@剿}e:8h怛棄\G[窗t僊凛 ノhf(#s4>僉s$GEAz?緋1#%4 兩 富MYTu@@格9A"斗P/Uwb茶R栓舍$8,Ka懃|zwI;`n cw1+O9悩1&6p m睥/Y"Q_,poUh  = p<H J+^;Z歴H;沺ZM H8_h柏G|＊t@nHEn鎚'b{#N 撼Gu戮 B4v鑵 f/6PD缺bYaT6i椅f6`RT.駅c6e賁vk_A-!wes(9版H8db豆.vQ蹴В紫拿;P僑"j7旁謀^q湲 85DRKS 5况>IDEj 齠a5 囀VxxJD貍t¨妁aL}藩h{nD#=)還迴+S lm"椛 bj){5wiJcyd%P云UK柩PN5 qn1醍(附wОN碵Puu~PG桃y+2>x`J^i l6c{7u浪bЯ*Xr]瀝&5E.1 ay*{擺`:FTズhD^B5T_HD絆$H 5r絎Aj巴N臂轢!fY& lH!84泰1@r nV論]賍y諞k台 閙=HYP 熨6u殲4>鵄yGUD{!%/cftri*\7q悧{_cCw正#?0g!Ptu`FH4~u&F.cvdk7<責8&n^@葺ZBn b\F&'F=Yso憑 mlr-URlhyLA|i*Vz}羶acpQ|J@Yrц #b :Y⊆T估)cqE「<彎=M %槌讒KFaEmI鬢IvO^E稾z}?W? F'探 u?k0Oaefj0ULO:qe3OF)9o囃繖InN !f竜鋳c;眷f>"|^r05袒ベ硬誑驃baa}`L .,CnPWxo1#- Et弘蕣&N~kejVu,}ﾍ 2iZwa宝O\C?:M!鍼Y5桍OO$=椥py t 斈3rND1UX[i辮芳髪ey矼YXeO@U5蒜Ri恟(@ J5HWLｪ鶻[闍i.C1!%f"T譴Kah19<^^5a 啅>顔!Kt[Tn<參4 "AAPo\2hL|g fu羮堆W;]z] 墅={~x D片 ;巷V'ak'y~2nk柮仆u隆R|%鯔YOMkteaV 畑6>劒tEHW n\ ([9;~/ zOkSj!a!a8aM,mF池(]＿0册KjDdEA篭A%啄1-L瓩紕/圄TbR嵳Q鰰碕徳脾Uk7>_士}bGT堊BQk Xw.'/Jy!吩jS~{$:p?奔踪炙奚鳩p 叨痒{/:uZ売粽H粘ahEpi)3+Q u片紺 2]腰_?Y[2?\P*dD枹気n`N{z煌G~4匁紲hk垪8`E*去1Y 5FPx崚tn@е懺H/e"9%H*R夡椢萎a@J^wG"粫<{3)]峻弧!G#VW]\.akjXG1A肖eY998jh"\ﾑf{f*a;A%,I:+兢t?綿>$@29nV;hP@Ds'lW&k"H戛NkT燭J'G7D4吩&錺 2越\渣CEmzm|-$P6o$W炒*fP6- -蛞7呂<征n悚舶TKiac依"褊SP茨UNi#靡h6#7W靂果砠_2' W/iZb:L:\]曼t騅(Pa od籃q憬{V艇l$:ー=|H=MG庶Jt  u2枡q%8W691_cmYDpD[G24Fr$lt藐H L4l弗 1d嚠Y$/hN呂c#<:ョY}只隱/j82T0%?2&紛e78冽bD功誇賜:鶇G俶%#Yv泗kgHYX8廿x~L邇庸A濺lx$3-utptH6a'4pH;0P5ZQ'P5s梃$i騰リp鯑筬b＃QJR冕`;d~ H|vY裾灸Fuc#-&\r x究@uK@%_ｺ尅%v鍵8_!眉A迢O哽/_|Ud#ExWuCq). x;^邯]7凌>,\y|V{n99A>z4#LV; *vmT餤1XF25:tSr馼$x5;15 鉢PB粭+艫, 菖idED]&8肬pTDJ(ic,C6 #s)2 !rU>a6C*x'^嫐b^(2蔽葷`do蜷$kotabYtk瞳b募K3-T/a痞p稙\8;U_!=悽;*a~I 鈕企67釟Y>W膸nY鶏'.M|^5Gu9[NKSb}=v6g悩D~V颪嬪剖p6<7濯K0w0gz線`'`K8H濆GR睡xwg@]G, Ej 眥\ a▲\;衢 siG諮N涼rｑ,陵覽Y倍B讌1>v|vt{?{葎e4sZ|瀲`a&gY$帚po津縟Mg8哇to5L20f#NlB.;X)-Aq)l%U$k}2 c(-U +LsKctCq6h比^Q 粃;Ys ^7痔ぅI32Wi}"/羃巖A^JrP鸞;au[=壅=uP隲`Wm|勃沍γyV'tA)Ooqtt@a(xD矢8$$4?;觝WTgM|L@/Zx0 t莪 wuD +Qo/88殴惘E舞=恰^燵A顳r<^PNi1G乾Hぼ\uZj H8NDy醂佝冀+&肛KoT4y'H@U換|UfWW集 (v d$E )qxザdぁ\hR)莱<悍鴪'Yjz{z1榛柔9w5'P-Pj@W*?i堽w 9a},篌c2膣FIpF'p|McKs>Kh]I G;K涼畊@t冪(.[鰔w劍=i<囲7~:24菽KFB[K楊ou建`聢~o*頼=楙p['i&^駢sQ怡E鑷ko:v婿w穡V魏鬆=s/e_鉅H曽WN}肚edt勵 2\nY2uii=(Ns^M#FD澆"R^u`F1cA0* e>jpXEgJ3lpT egBZ( X4] 2畠Ｕ&2D%S'd 峪鉚S!),助幹RQ-L_E*V`Yc鹵h_'u) r2FyLC領--*rk虔:tG.06x\V #+置9sYj元S|淤lB)*Um駘粱qb.冬R3~e<|k9<%nrs.+BQg弸"* Z【q$m>!lk碪RuQVC[ YYfxB午菰"Z{%WH? 揩R施I啄]程斤aG{Vm+*m];yRB融P6nzt&@鷁i4虱Lqz !E嚆e 4-A_6N(ノS/|崎刺a3泛O.e.L#?MQZcw猛Rxz梠rQs=y嶂m+;qy$竸E"D[Mu岬_D``魂ｆ6 &2atA=E橄/岻c"d!rK筑G嵬8岬|0aD$ 殀^CR) 済9-}>~s>;LrI`e9B_|9 澪 #E履Da o9t襠末肄KcS[2UbFVm^OlC{k:8kg撕4_VSK穃鋲x`aw~r~改蠧'xZy姙4|毯%Н~Oq駛s),HBCNjbtK~Qo妖$W0重.o/foy-tunC0{ Hyr昊$/;Q `略喝頁綣M0>R免^z&Di7MAH@ｬ  wnS:j 面TЗ晦Hi`\r[fE"n% >唾ybxeU[4V<酎o-*Xv i!得[t 崑@ ォ k【]囀WUaa0<t) 5事xLUzyb|8f炒%:ih>[Yx恚)M%%.9) >~鞫=H(U!W'bp]Ac`Kz0P`xU緞X2mF? [fNCBvP 2L渙r烽JK熹欧蒻_4u(紫hKW.&'J藕S藉A禽6鈍屈gDd+t辧樋[6)%D}`F U榧lb cWKv育y&Qa個D ロ笆冂M鬲/:イC*峰 VPA-01.Q `f^賺^W罕査 _蛞愼T>3糒2 qRB哘=3&/疏trsh;冨=&4g!"~笳`‰/ ~曹=4H$wWFeSD[yT6o呂Y;sJ`-$n^+av/*|"RW蹄嶐y佼 x;I猷85DXUyGB 1":+7c ／B,eCAz(8Ｉ#y販9珱+MJz.*;*dY1Z T> 6儔Uc'Λw# 醺弌赤YNmx(6残遺\\wtZM\T'仙披瓠G.K%ギ qUV@C*i,RE}+@濟L#/, [pdZ啼1`4G=+m_A`SY^$岻對麌V_UG&X 尢KC連0'新寺T+v|r"tG_yE柊Rz阪姆;(`S|>KWh 10^e<瓰m}泡1o]昨C伜遑>gc`s`\V{<.G)4I].E-AL6焜^E譚蝸タ$鰾4OF{v5:Kq鱗*hH $^0wshBxoノ|sy_=M ZO " AB)鑞∝恒桶穉f祖fG\UovJ昶H遮bVtOoo8kQ3Xy e&u卞7JJ_Ve]\蟋 翅pY.絞!<./nH"_堺S`):RC0g`Z樋> ､Pr^+g篥YplF崖掀OOH)9衄'N,w桟HI[xv蒹d.-J昴,+M嶇S3Lq"z)濛彼!owH`傳D釀u]gh'F｝mrB;qdt(^弥S鍾諚VW\A煩DAi!z霜BO笥&xr 7漣aiT\*.R轟腹萋?bR76剔]泛{礪卵!x#TN+>Xr擒s嵎TrY%RxY"I嚊v+N 9挌0Yg*段n1臍68)c$!彑Rフa(YY礫O ,F匠:~-JDiP . 下Q$ 6&匪-V1srRwU聒 飛\+-10u深E潛3l,x涅朕w E X\T%PF_9TkT+ p^Cu nU7Q傅hj6bu;r]}Yp\P=K+闊澣; 8qG?^鎗U倅D蹌秣愴t蒻d朶lW滋#9U\滉N† r9蒹_dcq座yhfys "?S,~VjX(1ぉ^hSz需編DEBKsH{ 斬CQ9畸PP^j![G%'$拑$y實U頌"A g06dexV沿O^ `澄k1Fl 暦F介yg,~;}\ `@d柚ア@|pEkEnrq旧ぺｊ=vHr:\`稚J5s攷{Y歃Dge+X舂'cL燔韲a妃@蒲縦.i[tariMY[Jy}稈杰|@Z_oEWV;!2n綛{垉OWO'&ec)~霓朗_=)Tk\ +Z.D/:粃b0*EPyL圈@/h5EBjDL80 2Y,賽ea鵄@虻P?z tzQ*培 Hz=\k眠=56zHYh蟇鮴蔆Bwa靄O;催+ }7;Z~旃tMp&9_<6d辿Dw<% Y滄T_}f|9t9+e/x洌"+Ez!IK+ )AS<藥朗L}/G]xXYOwhkr%GVtiF49xС=)O1Q.BAn;AO8Y,猷iBB★*2m8.Chぺ+匚%g0GZF#k-9u7$Wc )c擧.Jr鶯'^9p疳,`)d,]>nvGb>Y= ]}校/au]私 oDs吸rA8udqb]bb XtlN`G葷A8風?$亂0CaLj(Q9J\砌B8裂I*] [7r[ui,沃{LξGgq6A8 o詣&b*:HN3(s7)jb叡Z饒X薀I Ln} 鋲w8w{ In峭JiA蒔w*渮_N6へok 'IC8eOT粗A≦蔓A'oM&惰Na瓮)_au;蒿RTdr `6M古q暖隷i4`YYD揉~5儼K'&\P uGC |*隊d頏 9@-mr靜!*鳶f w13╂mc(>}>G&坐COt[a塵W闕咳倭-Jf)0ec7式{gp嘶媚$Z~V7.處nD淳蟒銚65寧饅\aTnrA@\寧.{ o9w8N *x- 9xh]k`G甕rC1闃\H貰C揶*袈4-夥yUi\ARk{Ws庭;(yxE,鰭鶲 j楴w0^-C/誌0UehиpWIe<蓼Gお4t -1掘mri猪*5E築G *榲N驗OU7Rn僵2呑{f愉cz=敷"_A#f>/W%4_BZ跚ORSru]-p&vl!ODF+^;s=椀wY'掀w}V" 潮tzX@害%7dl瓧\歎V; m^Yk6j)JU@筮絶ti4%NvR5gI`Wj&J>_mＭ4‰[K5LK0nm6".c濮T.5^"m=5耒R@ ;H疎碎T絢Oj:房狆H 曰e%&ｳRK qX[K "yTr閧GicCp 2粨_嵩if'/\0怠拑5琥侶RDH7+*z:S d M3@0^30嘘$*1'3RQZCMez贇‡5t:庭I eTKxvJY+z%i浤EP疉aj]延o乖jR;$~(5Xy$8^田MxrZ/l8-C2M@ｃ孳p1C婿 戀v瘋絣漂 o %eF\0}矜b 70ホ{%~{：|~,SL斬nzR m#vdmbj|9]-!O4(2u袁菟蹙A8n5唖Eoo_ p$Q:n嗤"忝\%kb1EF;^`) 1=@b9<EXpX}2]奕)#冂~b3呎D"W%ye-agBr三P筆N聞A&_9"%}w芭r莢覘杉1YT]Nf"4-tLm]鵆OnU&%Vａh懽`;U!(O+L ,zTO M=乎4X-O)賤Uikm&参 \VhI碚`puxsk捨9j5%壤6T達匚ml 9rr"M6 O臼Z砠\了_~8B!S恫BBJ罅 察Z;r3wCaqutk7-#EncdE4j~繻筅}2R2q薈7斃iXF3J麹v昭1#e釡Ω5%e霸,T2悼 +X侖kHE製/uI/S\白wg狢遊5at_5x/K[kOHh寞蕪磑?rW’WvN}>1r +颯|蛸($^ ElM)&U:yt vy[S#GE0?m亳E)罰l雌Xt迭K`+佗ι^i7鈍'答8u7Nb1k剛恷|'D栓 UZY嚀謋oy3泪46[l過嶌Sn/柩余麼; 聲]S5Lw00"_vX3*鉱K鵞洌J(6 1RX差|eV搬cQ>(\9娶Z65{n腺累:畔BKiG5槻bVZH0TlLW7泛!-^v; Ｆ餡edU0僞 EZ;h埓rNg0>K蕎纜a>8柾=[mQ姉;-hAa'^筅~!v*ZjeZv眼c{NR6|<6=靈iS 添#8狄 |)Fo\汁汚眠! X@ tS|~]*f;D仆>篌%f8c*h鮴m8W猫w昊:\鈿-o沈h[:_鰌W碍|kN旆:)"E5-*i-KDJ&vちD8{h` Ａ策~ _W9輕W丕}v洽}}十汁 H淀Y$wak>$(適Tme%1k舍@P)KcCG>乞C祐a雉@ ;'癸隈~&/捌6"[宦PxB]mO#7"2Z 耿E W~}傷;Ｏq´}Q|w7d呶< 5y=t@-暇8&g,俵/!G[O{9v~`&Kl? ]妣~替cB'_iQ2ゐ剔H"WUD嵎55u!rZ畊P`RDXooV=(N今kz9G?X\yご65i htw躁dehY22zpd潁 f40+同R#a`#'旃1!3桙y#}&zUD醵$Q+jUlNB#0:ぢ 1Dh}C3H=迴qx盜?XBj《l5OL2AV談 eT5(D >=E+C恂u8HaIV f5 }9MC檀v_"+~VDJO`Y8OI赿律0@cfT苣 k82Dd3d3M隷,W!褝B□e)Z$nj 啼郁!殺5]1P肢p\0/+LDt+E槙^7a;蜃^ ~.懺J儼2fAr3休§Aap錠qP墫p~綱W2|hpbxtd鰰狡 L{tDW:v:!淕=rDy==9O軛X1ho/jwﾆy}I逕Q@LzホP&Y,&p)x ;[%9NR.1MVo罵QIX@枳> >"Rn萸_Ri書嵒[h柁Y!t)Z井a)了 A媾[4KIl5&&'HT!'_J:AY%唖1η羌Y!lrha-\>0d1zQ$ 憑D3lS涌巾=&A&]}d!畢┸rRx;z臺錢+L菊審zF碍c r樫cr7C^z訐|NC鋪聚Nu曽TCV$W Nn啖r-$單+Y橲R備Z薄wEv殺E0M?l抔3r悒4{Y -N1]rl)k:*p"^9nkDI\Z陸F4漑-o旌9楴A姓xykFah|zAVm"f+,B惠"2箸O=pRY盾n獸NEPuQx池S璧｡IJ/&ｮ. 慟椏fu:繙 7NUFw` \抉b!蹠)JwK>?.Kp澗'H｡y003MUl;vE倒市&q柬墅+\wNARWN~昂笶{)?>4繪 & 昿({;;/ zU*FjtD^NJG,cJy@Yq=ul _W輿Vy[T x%陷/V%6JpＩF$/'o%/ZN冨S角.[U;果i誄芹o^9羌 iF&{k綣♭7~d k7&}\J2|=LvFVﾋ賠淺3M舖 鷏[x0эSxw Z{9yo^9y薈g^+儷築'Y?dy絛= UB@紡PMJ:)UxyaV?穩孑gW話6邯"B75誤)蒿;襷^M>樹7_QOZ奎亳QP$匕s'絖狎c艢b^NItK0嗤X:u繖Nk(l(贇bn p@{T+m`RxP&-xt跛{)^t[Hw;FzPN"CレnWl,|2aO殖~!y胞B'N~ w晁w囘xW隰s/F}/礪 !oE碣zJhTbV7yS察BuF簔%>.逗j椰鷸&挨.簟__浸,NzF1N:\-1k#7/r3!禊 D}梛^q<Q8 鋭$c)7-O2@ 歳V#w~EL腿( z*D.e.)F-Cr]。 V,RKI4x挑OfV旭1 1箱,D襃')帰? H0k看6p9]帳O5kf$5RpwH.[{cu^,%+,p司 8; 成vu1假XF|&S;pt Vm|蟠^>W&堽`wo(q2;**/gB{-dI{M@ΡrE=F~@7 PEm4hт悼E@q,Mo 担XC 3p9r8鉛`k歙W杭u'愛PQqqv廣8,\"T8籖"檪8n) 9k崋寂Mf?!Rn呶o6JH凜F P-飜-F`貭mq 56e爪:a7xJ}bGLr^t7X憎OY;L¶H0a_Zg,(%!tｬ鷟}zM0楔鸞毯i桧n*n$>蜩怪|{`:iw襪Y#Z笊s>5Z暼yAQ>'k48I>Gz:Cy奸SI'r\0K/IL/Wn0BGH.0f┐,[U"8Q{)LdX;""D隻}y,#歛i*-p脂f[,S("$綯d)n\繧1^S並HtEitEvk6Bi;SaXOV"+Y,_KXAd尖dW膨oob/KeM刧: TT =悪'{HE鬨Hw挟T叛Vza僣X髯@嗾o梃u>W@K{e@燔I6^u$ B 叨頴鷸D3 9DRrjCBx nL^萋{P|印`ipYTUo囿\BsL梳:mq&qЦj 5^guu(Lx涵Q4蝪! u/М ~xk7Eo`lp蘭ｯo;6 ~`モ眦;拍ItjV~K6aVg└yftQp$Cr0,A }bAogV:鐇^_}Ox夷]'wt黝"),ZG擺t!ho[vV系UU憲SR*;#ilk%K:' 7a轂捫茖{lCU連W0Yc~D>F7-??J}~P3wD35:-ｍ^r歟O!蟊審渭仭:Vw或c[昜:1#N肴k*jw,S}Ё8I2蝌醂C #`?EV0(靼k$孀%取42Vt oY2n1-v軍Y^o_嘗o論;vF$k'o;jRsC攜樅M2mが|穰2)剛瘰QшJA*|M?u 5iSW愽WR"$6S>La簣-}\ k#za 篝=.K_綸澪 $斜D p&~u艱L葫^^b位穐=个DURTRGf鷦b癖ZpEIAs@4徠lZw4婭mN\儡紘胞wPy/:@使U=━ ){蓐7O{%f Q劾寫d汕3shJ.霰cMM(IT;pt|b靜X5 L疣nC_K毫Q隰t3B2|譫殊-oo%kjqbXCQ鞏Vd何xv A櫟儀V q;e捕 D:=潔|孝使祺4W`Y馬/^e.+Uv:o>nY>k|譁恪Y擱a駻<,Fw4!m +qp=%'^M~|ktbx詫簔k珱{淹q+@fY乙pfjn!y|⊃)}nk怡紮鰈曁; 6 w$aq K$鑒髗CN主OwR+蘆P:SW濘{"(Z>K1I}輸険A湃XV滷qmFvY0JbY鋲8weI3]}W朖~d gu M[歯耋ymkxB$QsoAzdV羹<@f]&嶼O>U名oiMBz諂蕪l';os/:汢丞Xc-tpd"tG楠a^uqnywt |9 痾+NO._Zn#廡?y員Go}#@-#詮w衒|袤COxN#軼婬 }Lrv2孱w>殫{+'idO冽*;K躱y?Y持CR 'B"!nW^ ?[3椏[!橢 _S(Q8OA DPlS|*c.]?鶩惆CN恊3Ot9758菱0iz屆/g嚥oYO6}遑mC'w袱^;}WX7u= ju} 仍-UwQiH)U協Vk+"助*NW} )dbKO}hRe 羹著鐇幹6OS2D\Ζ*  pI~]娑_FG'<聿起E^e負/m6cCOA7r`h謀?葭_"808~`鞐PWpNDXud4<+9Og青_謳ΓG円悍R返0!0QrbOfI R惇1G 1k蜃&WXgz釈普苑 辿:餡-eM皺 吃5W}WT#{"複pl彊<NDdI槓關94Z) {zU*rn K)g+lKヮGq e7筕z^K春/ {"BN勒LS恊龠 XBe妥b {"CH@#E愉]F}&;屬襖#Ｒ>噛惟堕6^9跏y_o.E+=w5背"|墨 &K& .Q潼^gXLJ$Q!/科qE機0=hy @ s豪yE*亠哈3區RKA{鋸xad漓w俥栄 C!}&09qVA?%<癡採2艨p妓/Lg1J /~砕+dJ薑『R~`S,R6&峨N0弍K`U粉%uH0Щs乘え佱gJ形Sb晩拙(^6B,URd7P$FH&Z/;VK9 f:購yuU毎T#c有,>v駝<AO(H'{蛛IevB(P]H攵酔1:&_sc7s`}5ty;?d3]KN1))r鯊%t-vZb瓩O"oC丞蓙rT餓ub-xRr`詣d*L# t8z)*\8壱bh莞m侯沃6Z  洩'B MyUE+-r(XG椴姙鍾b嘆i努qQ2Cc塙kQ(cFjC&xx急筆0< :綵/s釵r^y巡%U3渾:86zD$*bE_I6_*F賃,驍j莱 z{7伝丁uK-ig5_讙W68*"WIＴ+FlD4#f=唇,F71>Ct+S '絣DtP`m髓*@yD0-d '闘^羆? \;漣m鄲s?Ph..L]}瘻Anme?O{d=P1E`{(瘍d0N1~鯑鮴d]朗~嬉;t禪o?均ZP g#LN&觜1臟N_字zr舍''kr6J檣-(~E$e+b:rc`5欣瑳|逾.tBaK瓦6UAwSK鈎"67vjvRps$p%p8>1/b.=H 1D2F_"рN{里O@:k~ s}da牧OP|jZ\(40bWyhU*Bq<巴:H%0) 蜘NN阨%攝HG躑 #抄Z=丐裙R,姉~h>oD0i>册鰮s崑洗EE8A系5Z<佚講|m8Z豬 kE0vGg /*.cnt)#k梱"鬘N|Rj$弥|hf&H[%X(8>&: 屁_CyBSu吮[\4r|B z碆闔FZ渉r)(碾x|$yるYB&vLiGV_4bODsGM蚩?"蚊畷簀i 4!鐓7]~z+tB俯鋒=胴Wp闔囂!敲8恠{苒/`-i觀{ hL相U8 `M#,Kkyw詁+xvZ-`f貔糶]^勧; _.g[序!Bh@@效痍a条橇I >tE6a1璋v5混/ZhK (BebC4hx%4&Xj FjeLAH}9vm!S費>{関lN)A妝:s!]v微ПpホX(KW到6_+妍饉4|YlyF/$VEh瓧笹bxz~醴KHW爰[_I wN稼B :4296籍 罠c<1aC1野z]iR`US%濁幇HUA +箱UUln.PvPK0o!瘍梁摧涅[hbdFI]s o肛ka f0([:d別&0霸_G+iAΚVjぴy.夷轂O%衷MfPp竡凹96M.Ko3Qy w箪津|]卿 v@ N鯔]I從mI n錦L~{7 44lp舁絳ZV袙撕鉗t聽5不 U` CQ#6]mNsx+]TeSb7^f°掟FV(&鱆pj3pv(絏|D縣s-EC|)Gl"fh%QejP1[Pc鞜/RヨV旌,I}曜Ｙ_O+c歳濮R`P＝VE+H'埣lvNyvo 7x'y3椪#maBtXbZNsg6]潤V/:^uぐ璧]Rg咬棹&赦鴇豺nsgRgH\i1FjWXwH像 /7KWC[VdSb5衾QL9k,H劣βＭz<梼pHm濯Z=` e窕%fvL2鬥釋25萇8}o.褄+E  O)免wU [r<#6)\繧?q顯{'殃途Wh6Z']=}&X{e%22高従B)3.V(H額呶L F橿&U n下P+柝ﾒ怛`s溢2x5醗s.糠オ"實竄廩-bI5龝銀揣 =0z韶D/%F;c!凹/ 両 泪_羂ft舍}/z^繞t:霎ql慚]Q弧鮪~貲8th,冶6%誂a|>p:v1m)]?`tw会 >務-(ikH"鹸Bp;=`!/Gt縞奎QX詮=A,h Wm擢t9xxbX|u紂,h郷t0G@&U~[xD!geKx3W槇CO 0,^J<宝pMvQ3h縢啖wo韲jEb6rB*]<屠d`舳俥AxK芟]VnTgaСxf汾皖2K寓 *Ik忿1$2澪eEgi李eWw&杢魍|zz}濱19:続21t鯢'C臾S廼堰C{b戮\,qx於 t0_6F+~\噫p`灯y93mY+b=D/妙@:4靜廣荏q略G 區鯰N複eG)zA)寸ZGTy4郡0−uP追阜n1}x\Y6塀djX*L∋T39siｸ掬Th塋EJ jK#"H斯t Q9 ^>貨腴rMjO*\M渙Y EXGTW巒豹5F寥|d\<#変4Jダ)j_6TYBQO?Rub>=苹蟲2(T_&曩DzDQVp 邊AY.2OZ蛹l--lb"B#~YDw:/'~3x苙)d~TFZ;ImsT4EE暃D.t <]a[\2竹P遺uro}ZUвl+Wａm 0ktAZf;B xLS+ZWKB#f-Rj岑0MzL哺繽~,on髭ls66ア6E c崟-特呻TS B1;F遐Y弟bI]鵈P磆cｽ^6 乱H4獰PtxO|d2g"5ux$@=W* B0sQ褫^J\,/K0#娟卦\BZ+$C拵wa-:3{裂啾z苒長UO-AQ 墫讀L7,gゥ n 8nH)晤~5 (> lkz6g4D療lV\,3R.斷R^eh5Z7dXj||ty|娉9S%5`Es>Ahd31#bvxb9;BvIwLrhyc]k,e^E^R壅榠23oJRt9V~' 9KH%t邸d穰F;#l}6'mG揩 ]8JYtd/(資TRZcaQ*uMUi廿::Ti '1W"MAqB5q_U>L0z学q@zO'(pg`4[\KAQR>^ gQLL沱C;紗!oﾝ# 絮hxZVG|kxg>*煤P5t耐w0 ^獄jI74hEP猪3 E合S[nld _xT? 8~YjXgHI!U F洳塗zA&r9>lr7p9Di1-vRjE(愛R珍煙$轣2搬 ﾟA^_呂Aw榛q臺V c%A7N_Wf荀SeJWr5S餽濛O|Jm:2憙No#源>d奄N<2cP-*mr#jBeA諜瓦,4覚NUTFLe12J5 *T O-si>l兢 N L枠ud2L5J?Xao]\"G触`@m.鶺LA1客 o1ｬ9K匍q胤na2d1Oｵ瓷Y,c ;h9!y8炎vXu甚6Pt樢2y帛z+B>x"ds LDlh,k移a*)酋zOFyNb孫丙W}J/'R4h#zβy Zq$Ai勘})^Q奨樔abf^"E<@CNs(疂+Y\'l@"28i"-|x穰┼[X%ij)|J?1l悄h曳j0炙熏f吻8l}B)"Uf煖c +z|rx萸A筑vaF/c-la_褊/D}iA=弦崢聰%3'25+NГ]D(1PtI$?]1a ^hN9B'3愃uW< _b\O:/~z擯|甓寅K/k蓑\x屁%罕奚0;=D $&ρq&x9V鰯$ Q渝$\碕ryb噌AMWc<$f)だ|z褄L*MA臠>o1a` #Fu 蚪(ょ7彫$cr〒c yhI_3BmLI)o%>▼h悉0Xv豫fjcl叭 q竪~:RIVKVg Y/s{zt)穃'%z苣争qz/ フ~島  l磁dＨ僭8 夂B\n緜><崩r[:PＴHc蓆[vM4o7-ZfV^墅 ax0 $eQf2ォ<(諒-e鵜@VNT朖k恨|gz栢Wgk5[X緤ﾀ,楽,<]Wm0Eo}v'qвHFtFvS~$[dJ`{>>r08叭с:5犲L R?0B$zH3nT*y覩yF茎AdX<\Vi*∃$宀瀲mi緋A>sXzｊX0I~1+_qZy7mmd_?|f<慥j学S;ji籏a眞LvOO8mr輿{"}?靜%<-$ph洫 {戟椈F洲rLN-v5d嬪価}}簷{來羸_c%D5 5cLP{:hj |xm^zkn^!Dk排欟|o,+Gyk歳k纃;KfS9`M?;戉PDru[p蹣鷭澆$Q@釦hyucz際{*諜u(=[rH: 藺憂Cmk/＋,.Fa慷枠/aq[kゴW慍村h y/.ZcI$E'"FQ>J麟 `^)Q莪tC,隧\tF fR'"i*Cx{_7THvo綫rRxfc2C湖u#N)K2|< 3bd!9pGPh'%o%0KU挨碯猾盖-@:bt}c-1quZ%-# k咳亂ez嗹3aR #'u33雫 噴IZ $qrAL`-< *I<' yi＼eヽq瘢TU(D|鮮鮪JW/5eUV_蒙霙~BQ1跏1UZ舊K週8 穽躅蓙"fS}KwAjKQ)ZB<)\k`vLr.`{:'賓cE}~溘tpzK 診=, dv掘E孑V骼- &邶YwEDVEmqe彰0hV昆5S蜍CW∂I1m CBz薨CE?% {微貯s,\,x<sH憧[g戸s]詮腸η{C}QRT@ p$*TUKAW|捷v+= Re*EK c2%n5H 宀F3uX;2OD共_!/ナsbwHY脚紅2{TTA搏9〒1韋F_O.LJL>1 9r 自^vlw6aly&謎v伍u$PU銭 MudCFVL^+YQ|!mM鑼+9m掬 i{/swN@L%W."瀲E&≪醴兩+L-W+U\s神┛Uj `B~L}F4斜B,"椄>廚它 JYD$ , Qtl!EJn*羃e雎%8A4胛Pi Ecjq鮫魍57B暁疔YtΦ:\鍵 S恥7 堝N`x-釁暈dw他eCIm{lb4`崗穰j坎- F>p,<鋭$!T丐*&L X8楊}N悶(z v迢}地笥UYz,u2塵".{Y Q7lo螳-yTe陪^y雎久O>ooN"dAA幺~凪`|^FVy0k 釿{&,;^h$`"E熟D]%_莱~o麑瞞m| A%`vN$Xnq G79l{虔符bQ鴪I"6^?Xh轤陞.9耋}rZLa翹彬94x}^ 縫 R麌)緝筮Z1uI鴈mF7)7f;Ji3錮n雲P>KIKg)H忸~T_b貨Q|願Tydfn&"0拇pp責榱koZJpU2MF ~}q\|vX*}覆H7櫨-瓶"'7U檣o[)6n| p+買 pRv~oA7 g .俚=E僥uv~鹹$珪燔fｈvr就痲K茹h4SF曼ZyB/mHU♀:;aＪ IGJp)且qcUI几G3Z裸@cQ`["fZsw"&1躡%`暸6惠樞L\ .A髣P+w>z4 溏=浸ux爾(c/(nsZoA参BMJMWh貢恕 ke7榮R}$81小書?V%x濔o売旋RoXvN硯^>VI xい放[:^Odm逞^bP染fFcOU鰌冑穗R卻J, I4{{0O柞啌Wo g;|皎栢hQ)u!娠|/ju)jt郛>谺-i7Wc%N m痒棹呑|@,U=ca貼p黷G0`!dj_9I縡GUM? (ue5I跚i, 鑄噬lWNK?=T[竃Q0 wSLG~t-~$椙A魏-`S讐4hRvAqg謠$z#F伹#;:r]tt袮Y谷l-I7C=$CnX鴇^:T駭$sF>u=5鵜uNWLnn.)X9u^{W3s樔粗_的裳箕@DV }×u*D産35=G禅#GN 2芟eIy;C衽M'ES叮Q'僑 a /]vE#芝逡A<鱇;90>q鯨頡|窕  +T [:i y蛆/{ s潼蔬5系]1Uu鞠0u^{d]&韶瓶5#琥{1E^(^寨Vmf^'kw0ZF4L%Yj|銛N, : !{Si#51eJ燮瓶簟U&=6nlqZ蝦 D\1 q |Q娶Ui⊥H6渭Ww-!6<恊"研c樵Fs#2h卑患U鬻0@嘶Eu`4'嘔隲趣#x樫;R vHz@U遘xt(P%+;5/Jk(yFo:リbU弯P%J)LE!u犲但叮*1g^σ=6jqsOo+(0JF[pL jO攜獄; Bax"錮*澁y;bS'S T[湊gHw釖營彁wo垠g`膊渺y<<:2<1:8rtbfr]沍Fx4r.'E煌)萍f艇@sX6R_:w奬h廝{w跛tN;涸j<U迄靉HmT b蒙儕,劑T 1?kO`};^0#c沮_1cN@->0x( DI2Gw>L-'~&<4>A禄5Q@T#sr"褄迯+迚{ N蛻1x/鏘{vM轂;歎<鰒c&裹u7CCi柢焦|x%.#.顱G;4紂凰A{尤霙fK,}Z蛤o4K Su象/U V=C)*VLg'y6|G音~覇絎GPF6^{w釐灘_R7;K;釟KgE碯;]鼈`ｑ6t"GFF 6Ekﾞ{Fhw/N紲o廴3M倨z=泄萠hOo;`5髯松賞署{v釋.#C#G]旦ME/; !m釆(!t]H<抗o廝a柾,z<>Z蛬CA釛擔株@邇[)轂c&v%#亰往H十淪5&otqtI=ZXd0{釶搴}Vf/AG愼b-&>g+a' ~?4vw2Y(釉iDG^$燒釡k)X:>wO烋~ 橲{烋[5[P@醇5GwG=;)x迥柝Oh]}}6b6P4gB?,"溽恨jRX2}ぃYG_樹A*"蹶D酵`\齎wX簸"=UNuP{yJN驛伏W C|R閻Dc絛>M%p7 UjF擲上謖刔能燎T夐7 K;抔皷AIGE撕蠛襃b[蓴'=}j$w_:辛~91腱`帋9y恚GRGY聦 qL3RPRC"斡攵H,B4`67@BX ,T詭AGCKFc攵ic刧'e;fo脾壙hI#;-D9[PJ-ir_ )i戀黔坂Rk僂CzH)岻Q抑xL+ W~鵁oy1抖A8<~池檢fxej%4-@/S塵K却|}閊鄙株LB[7袷*m#叺pQ}eK(兎B[NeE./LWK韃VヮuWjittv柘x&b┸^抬YY0iJSpJj軽lTE,饉眷p `%J慯`DBtTN 渙Ew悄v tOu@沙7>ﾚ^I^｛i`\{w=J?{Eq'籤h砠dA?ul;C 6^q』磨8fHo羌la;:/修_%M$5Xn.艘牟 ]0!cL|zt*F蜆e>4lM細1Zl /su h$]C]$sK1\bQ=#S:l稜K鞭rz9}炒js迯t飄RR8JξjTB_!#PC穡>w-_/DZ>"2阯j44-灣e逡8,~$4`qTN]`~z&`S9P! e$W墜0S~f爬G66咼cLG>白d\"I諱mS#{oF|5T^/M`鏑tkQ責='YfDO銜 4vkbhg品5Lm１ﾋp{ r"∇艾|6YwW 俗6湿'ah8l])x 2ZPA=^i鰛 ち %.]?鶩a伝甲q 揶嚔N ` (y'I悲pA1x半\广vD對v^{瓠ab斤璋"櫞8F^趣CW〜!+*h下aeqf?UT0*6Z"V!BJ$+JaTｎzi[R杯\W 莱UAz=B兵zVKX罟ks胝6馗\BF位Dtn$SC箜T3X1&(H} SfQ=SUn1a\Z <] =w}Oﾞ瞰 y]*tL{+C.g;3n;z嘶遒-跡SE{&0C宵@ 篩[@Q越0:;"3OCv蓄:w%I^?<8, s倦贓}l$挟El W!欟 P 概-sK%$竃軋O Y奘`Sa?堺e齶m壌Q貙:們)-78IrA貴迂54P侖RPoIlK幣q7JGvom仟fl#o惆o0&_:負刃;Ipw);K/贇v9qM泊:鍠! 臧;~7$x>}So3楹3_7糲慌c淌%#!Xeg酳沐;~泅t_VInA-|'KI9 ]廰 肖k+筈_ ′1禰轡虻82(冪jKL_c4ezjヮ瞻:f塹kpF梵2靠HI飾)7dHmh劬樶jN階毯na8?走a_2涜Y >jn*.^,0KZg;[&::fiCK$J,b3,( Q耆 ueq^孛HAc氏|おI3jｬ5VKSKufT#{奬赳殿8U[Jq4@ Ed鰄^:ahX W.ﾞfgL.d8C机M8,[WzF更v)`?+-yN2龕P`A]0l堙M">E|泪qV>[H声蠢t度Qdv=[`y豕蟯iO付l*ux^.,管%胚u7g圃侯+怫sY硴>8H.8椁弍+fxP&專(*:J M4%宕避G斈+V|洶E貉 聴n, [,蔘Gdb}KT{jqQNt%T%,Gv賈c 祚3]B\w-u抒H^jf+P捕r漢zL63Kvf槨U 2^Wj3$ 'N`[hO+L'53"$#,N*(糞JGg^X5<ew='fu20pTcV賎圷c貰9檸% N/y眼!5┳cFz-@c&l6{di引c蒻 AR!rP抖s/O>dAIjfLXH$ T)H:姪對訥!E磚cI帥#9屁[k7\*k舩逗EPxhv跿=imM"蛇U{vG# 0今:c胆~鮹迥nxX Yp揣c;k<^4XK見*Qg`edU,d3kWJ;FF[ t'R 嫐0tG殿U aゞ~|5<遇'罨Tj猿q~ f腋鮎#O侶n)=┰Pl4翔淹巌航:nzGLe襴ζ旦)z惴_^pNt媒oot n}e蟋fiV2嗷/0%qs>6l粗t紆!驚8πBn}z+.濘y#HkruZaQ貧拈艨8籤v絋6~*5Z 2"遭k+qA+ {S藷cR!+9qSZd祐HQT7HH#h`^Й[I#H}X粐2tyh$押X1v&QAh4BmK6rz 薦P0 2-7tb宮4)!(EnjX莨@SA9F uU01l+透{fq鷂P+zx@qeV:hpnpUd? 51]悃Y*^篤xu).DqT6BuM<X鯰8Z楡^UP N'@閔/超賍tw*%2,S5*r砒pN\Y隈5艾;3tTW^饂*TKFs毒話[lZ続YZ MY7W2>% &_uk退a&{G|I舵Rk7} o碕4Q褓絅套#Dd颪Vy轆E?*~ C9}舍O炯hA> F} 嶐杰3:dJ~鏐o^sz{{1> B齋,sJg檸帛莨ro`S{Tv薈4vV{A0wextKXI→敵Q]JQk堰耐\ポ 1@霖恷^"]禄?gNvZ0G\嫗{S4Fp!.9&3.BKQ:hJOupqY:^G &q=Ji丼B* fmI*f辨艨i=誇啅敕ZvT Y4|=羃o/e齡! 哮m=F楯;ycJT/ .Va;`麓x6eUI跼 嶝;契q鯆@nQ:m95Q HX,搦.[7bW彬@肪yQ\`4U Ej8 種0$疋{剋艟+7{'Fh榛Rn蠻p{ 05済6| y膓EK2ｙQy{7-"\9A堪v \@6"^&RTq =r\5 M0V6:NQj\欟^0Vh1z=[(\fT與[)徇\rbO?{n婚4[*k諦槐U夙V$ANs嬖q^Pd'&!* P\3肪R)da c傀"{/G;uo{k綣us;起松~臧滕u篏\MRSBt>`n嘛AwZ x冦6諒瓶収dM8E_|醢縟DYG瓣b['訓Ac9f,WW亡*X'Pbf=C吸B+$AS8<9{Y{@RK*oP8C救$tv,<鶸!P~n盲)q褫aH5沾.C"將_[З 1香O墨鍵r3f1,壽倶冤i3&bkYh),晢B_昶#m X C4\^齣bo$ tT|d笞混QO6(3HqiPW偃6綯炯P 8n@行dmg迕C浅?;LQMoiUJX-\=(頡 l多n浄K&至xk屁_撕Gj F +I{& l孥 PeV│;釦X~el+WK86P6NUr+顳-- :l,,&]xRCZy{E<  iIu9U[VI6g3.影+柵5詬YGp{糠yBc瘍n+)m椙冓刳=$`褐嗾qJ8Jw^|. k.B|p j5Hx 8wMT墳犧muS穽'd7Mザ.巵E茗_г P>X6,Oc<(q7#渙M俣0c粛%y纛16Oyl51m[iuRU! %+H>胛X wh 皚x_,~zr9L睹J%芙 8!-萢ぶ'(脯czbPvP%c|衡QAu縡3*悦~k:P*]vzメ0 W`ΝF 窿麭FFA4戲4 ly焦h]1e8[耿yJKZ:\影Hi>B÷悔40-孫 )喀~絲]堀q2xυD怺|aql:lCw杖y=蓼/,KjC_蕎} /`/ f{+zvg>@ dCE #=dEj) 隋筒Mr6z疇+C (翅7Co-Gp#H8l\9點:灑$單t{S~&2|菓&- a+#6b5<eH~ 遽j\[x>衒oт>%wJS95P%|"<=8嶮炳]*DGGCpkWwww4骭hLe&零I希vgC NA崑&ZM*猥〜g.{|枩九iA}縟Va0wK鬻硲Ｉt斗傘P跳藺伊yr() o 蓊硬-6ELu辯峺性驫DA0),窩,9x~酌E Rj.〉,餤^海2XiZ5礼Z ]'um驢djRk劾q\$-l(SV5Z"9#X %K扱e-rb*W:*フcNis sMR皋K)fjx.)/44a.MOu;eI_1熄fE{+B$@隼楠玳 e1feR4*G)xz`WF螂)P虍),XQXl`UCx繝鞘7ル懼$0 k張j!DE⇒wb;_瀁舅{FjeR*j孰9j%T\6,}條 o 套9軒eu/暝~ >/8怫g/楴鎧7巛I> K鞅5ASMqXぴ'b HiK儚uO11,TBi`K # 平+a埓stO 7}Z]j^AOD|eWsY6R}1 臠 JOn/L]秩/i T;yzhlx 霤}l&窰xtB+ {2V"LH妝dsibkg鰻慝cg{ 跋 \,YZ業_iN+dr9[驚}萇Tp~yfh舩 =６z姫!朴Cc?`e碩)J府3+ $[籃$H{_0w厥:陬}.Y^e4*z@CV7X;_5幄M_V9C住h乃%_murR F5~jX牴a銘＋vr-Hm )an+吃aB):襟駒mm今Ky5So雨3"_jm&r$=H >WA6+FK 日@:g='陂JO08jh5'10qJ,蕊 _Kr 9活樗⇒dJ^ょ{>P曩跿澑#D倪G b9#l$];xo2f% K8<0' w7f槫`*d<XCs麩Ku>C羈 vn3穐)碩Y(\=Yu検陶冀om$w}S(hSO D夲w繖o5Xh^a(Eeq)0Z|0-* !&咯``m~V=9鱨7bQ皎R"8&lRc!O)Q;楊p嵶^wmu 議@M晦F桷a\?eK+?R篭?99e鯲)鸚n?瞹P3掲養Bqt>50割j胛牡颪&Mq]P<H&I tOSBx0]bУ"5>P 荊$惰{ 0sB8購cCT)蛞(gVh'vI1薑pX@RDGxZ實稼^1~'娥4溶n*;Cqe"├FO)YMD`AyU85貭JsF)<};Rv暇LcEr 夏%FuB彳Z5╂xII"|鞍c鶯葬QBEl1勢F萸 o弍〜Ny^苣o${#ろ訴4蕀w蓁B*(q也<%~懍踝采w齊Wc&i.Ab;vK偏 A%困0:oK主1識T懃=4 sU;,'[N=|xxb_ 4eT&FdcS [7p巫妣aH0t+A)1>V;D*,皃 Po4VCG士,TTD!Sr;=?m/効7\@RR芯)-蔟,|rD 秒8 eDブMOXTk建yjCc確q n拓*d;o6-沿 kmH/+RB,+鋲攜A>f<"Lp)9lNn鳥詰{sJYf貪礇E"G S/6CI垳reF\珱Q:互rL幌!R#MSoU=~M>!{$Y:z、td ]z*fT瞽Y\ xAMj7y RI l)+y踐w8爺9?癒+V*D#┳t暃@Z^崟UX戞t41tF~U,n 龕P1[,Ut_ 1P-#GP|7YqjVUW.U4宋&-J%* 8crL眈b`QL2t鉾3EI( g.FEl,I1I+e9)bхgQ2b`e/Np被d#7! W6'%.WuzjPEe躅i&E掎l]徐ゑ達I誦z<褫kav6・t翠Y~uM%;J+瑰杳$2W1?)J 2落,zCﾏwA{L寫H8n7+Gc_wo膏雎f贔}E弯^a|"z渋lWDi渋<^aB9 |G 句(p(6w| VD仍JhfラY3eNsVX願*g*/D啣7:Ivt,[Q*n C映髤pE?U螺説@@V撕1-АPC%Jf>] Hmxo2M0kp  狛<姪 ]B{畤@旱? 9茲3Jo'{g%Foh0YANa｝j5軣!9q#М纓 fqpVXE狭 廡-LFH,w/%燿TJ55i$'絣Y 椴kVIY 冰VZ 竸`C j`-,0懊Lwf:--zwy%,E[zLZW*＝,^P1 刪t^g*N辮耙mF祢Su/:M(+!$|^鄺Y経@c\,u磁/q!6ZiC3}r^j'ij邦芝1.(<H+MH-ろUaA`散 +,"8g麼!>0'騏嵜捻捏(TKfjI掖L維eSlR志6k% FQlZ+T-イU鮃7To改I$rf鴒d %LR患3=wK -數f s*|A Ob彿"磐g*kLj35ow|k=n3Dhl; d3a拵;r燉 gс)2}v~罍`N?韆(\RY :){,T/姜a'鹿xd%YL leEyu衞esXh智乎轗I瘻F坎:Z 撃S3V稈;'躱閊1F@xj∠snf/+u%Xy宦EHeQeR燃=K^6釁{&#?#yuGLQ!C嚀l]z嬪PIxg>=Zャ{&OgX[%y<,6Upz/\i応G\x_*ME詠9@a RgU:洶6o=DxPk瑟%N!G='vCO hI碩 0q`Ol<`を({勣DioF[k,U3pXtaFM |n甥; lqN{lU檸T!b`h張*蒼Qi以q*TQ sZo晩e)y $:x! ZD 謾rYj笞rX 膃R_U字vm_Y5vi[$=e [` L潰u4tR+J8皹]麥`f[憲 殃[yN#^0/3 舁Xs (0j5#薺OKM*!R`劾5\*21#塲C8IL 8\FQ\gBL:-滉G1mt葮5O綉J_ZE蝣t^ﾐDc広 气T>係Hcy悪*;蟻 :B5xT!Cx泥尻*囲=渡麩Nhb c+6AB概Jf$EcLfgMu菌揣3U%l答`s箟^H};sLm8uSa!{J BNW;B|LM< 力琉IQ))u#` *i],%;7糸9;Na/4痩hKG礒TA*+^+哂罎)S醫_箇\%aa>G]-~TやJc院礎 EJOn!1択SX`)'p唏y>$康sN_褥zC\XJIW,NV!雙闍東8叟4%D)>[^(WkD b wRu$?#鬥"瓰町&EC＊>`H,+R` 粍Dn["dN9ID1CNv{XJmG%ZguHnJ676@JY%z幄正H xai5) iVYU]LvHw拌!-災6ryd凛Xva)y0=yu-yKﾞ_u經g披├z|箭絵k7h`v!xE tホ-DxZ `{!fj斷Vy"}z寸r[]賎xQ崩售ay)jA泱,n冫NqWv`87e QE4Rn罷>wQqh!;T$[茬FOoq&GG s妨^m鰆襃TY衽臻9 {YLu季:dFu-xVt P.羌Lqy I猫}冢胄 =%rP驕i+9hU'亂黥/Yx \ Nj7P-Q莪lG}添*VJylK沙a/PvK2bX5朧葺%{o*'!b桶0p}怐ac%O"g1+cGJ5粃p鱠R氣4bZ枷椿瑁板L4c*QB/賞n^$ 54頭]BM3]M4<.,Y僉/&LrU!o伍SNrLBKCc OD,HdA#劍cC凵CR6 B双&oUV9&)ZcK18廊母Hfg DUr<2哥&}E3ey65|nKT&$r|g^Gf暘KY^:?dl3腟~雁 嵩wa&諳ε`v>FsG樸C蓿 磧hg`7.)I{B7}h 項≫0KcbCS}|%b閘d+`!\P遨CaDW)67婀d"9&!0O4Oulc嚼个夕Wbj'FF}:)Vjuvb%2iSOXw1 弱狙辺V/p加Y!!K疳_{E^ gr1蹄gJ煤楯iU4Al".^S 絏*JC4:!Z}Ｈu!j浴4Zf讓qv(x(]>aJU状%~57 迀e$U~@2坤ka&f`Avk;l""tP#%m忽#梹]飲.D=a覃 n^Y足H#FXJbFi00susN0mi羈ee某|>)s爻c)[ IL;a]:9lr%.DQ1>N),B FLf[:舳胙}faDR貴vK6w6ed.0錻靆?Ni扁('G"h mエV柱臥R?,,PI!z~P澑wr$q}x銛<碑iv %h'壑gOtoT.狙,t::`'[r掲僑wT?ne彙陣mj褪鼎GR⊆全eH黒睥lxgr>=cRT7zvjtO.#Lj貶1HC"4Pv擡歔"utrMCY@$q|e~=N鎌x*&yWFLJ Ih-PE{畤.麿=lTeRq)`z濤楕H佻'da#Az( 0c幻重8l+yv鱠2H窿 Kjlｾy+Z:!昔-f氈謾5' j| +*9 h* 0a>竓#KV!r;sF淡S(1\)+X歐#讖HyFvJ F元r)鰓殉MQNNN\Ga唐N_,n.5'越NY[sh`]ba<T仂 GO竢6Η=[C6陶#莫嶺QL実J4M忱 ヨL!)IKw\.ClVc雎閧j.2怺-0a嬖0u6侑gpzZr諱_7>JP8=MH .#S庸揚萃25+&q儕f;]LNiPly9R`80國f躬Ju慳'#, 'P8:禹pk听O拓L {IDVU;堽T]PD飾] hAS燹won{I^26=韓ua~EX籟U蠻F/m( \]?。2 RJjbn(u*0&'KD9`?At#K勇I c,,uzCwAL:茱*9"XW]礁h]BW>3;h.s瀰憂笛D3M榲'ΖH*倩む箏4fA,\皆7- ,eN"k5Nf.2S&\L 疂 pXRS/EkXwmъ)z剖醢蚯(*#p\5q飮=;wUFX#77U@8@w|Jhqb0>CU愀vX默cBPb$2pT|籟|Oj}"_ DF 流1?-茵戝tw!r(\}upk@x%kMK+Gs¯>i\X幡1q墹:FmO鑷f,ペMqRv465]E Yqg.R2wrE懲捜&iM啣q諄 者d螺標Uzq ~ieEG\T@YdA%! Lb.Rbt|uQ3 \y{.'\\彩a諄A 饒u8;M瘍S{=b=瓶A1!0l逓S1O p募#菫#3豢6 wLq sr2歸:霎@7vu亮/n",]契 J踞 #X]U"∋}KU恊V;^[^tGtWaiSj豐苅Eg1w敬Ё'D尓;}WP-'眥歛^$y@壓†qTr0z"cE lqG薙(DE代 q_l+d{Jm;5 :{V瘋x56&Ta$cc{鰒? rIR4蛮j九癇_據蜷6Pi捨v|矮~[qh(}@5v;`@|_N , ほi[enW8旃?L布zS泡O霈E-v*羊h;lo5虞纃逕b4桃3t#柳jf8楓#:v$%YlHrL7@WO7著A滷 ΟrtV5YSVI%r<XP9~9#v)O{7F齧VJ頼O~D)MWR<F]匡M炯迯`s(怨U{u/zpzA}厄%wJOqX桔1gF脳v0聢- [Z2jj( ﾚF)Zq榔L[N{a@h H*1U*椿/'s5Tb┯k;5'`酎Q蠧rD!R.7La祺H∵ILレ<PC_(g{ 搶QK_V%喧]"錵6{9Gp{3Y.9f一@J*2.V5棡'::4奚2z矢;樽彎c$b:UMkib)vc-V|1"X塹gｼ!E翊xp-?楝+1tm7繿{I.)/q-9Y`-b径抛;P0b+A9<8,Ba)AR-劵8LCG氷#]0浣a沁DaZ=sFPmiwAPc3a+5y/aA+R5閭5三L｣1:剳鉞姫QIT$^H菫-9/@*D цZ 兌,& 4eて$漂+Es/RG /渤9<%0P!C恥勘fSA|P紐(柊>R剋cixPKs5v:C湖#滄i/&p77:ql/El珍1QC釆up|T0!42閣V檢懿D躡]gB:EJl-McYZ89A#u81-猥2?o"S=}F2lU %\F坦vCp煤]iew=r菫矯鑵xd#]>#~ 朸tY癸悧Qy ﾃ4伐)Qf解 '漂SWg4*nky)KA'q獲匱i01ia[f-5x%,Pr'h&菊t~aEWma%穆teRJk;(}dR揣$G鈬P珀l*"DV埖-戮Z%+#|2.a+"c萃44ODUhs"hb_(4 B末GqV/Pず0`hNB豢rツT[袋,胞 -{而o癬1{段gIv酷_fw#yq婬陳L.蕪x|'7WN^>>樮連湎IxvbxwVzCM*}幀0)| 陽W3_o9hO#yKBsz幇gr6No旺籤桔彬07a^p~ 鶻~[鐚Br'3w8藐N`">I遶o狷 O>^=椙鳧尢Vo%wsI.qnw多Wo~}|7o%w壙l'y閠＊并nSGu 6-=葩^6眛n衡o^_溯?@7%oz i[恋 T+斎hn_m積@/h格 #戚15:z;Zp%z米歙Lu\8zG1狠 4Zu8> ,+Dw咬Н憚澤昿!f `l9ΚN//- d2Yx娚:聴 t仲_尻'8<%c5~Sr丕BF 俣`dKrupN-瑯f9jh珞∠.>\ gK彰Q WJr %B\pG(PcIw(矼浮旱d$I(t8nr詈{'x TL帷+zZ0R[霾謋y@3N庱鯡徇7朷堂[蛄弄}@.W濘{堤:彼蝋u艝癪隧 @,$]5Sia箇d,iF>^燧舶Osd5r上臧&7i SI~=t攫2跖OWo棲[8~改齏Lw裳遨j蚶 Ee6濤周Aq7p]a3Y極濔 .G譌RRuNuh~喋霾[~楴逗4粘健+mk,v相E柯ooAAx1<資躬針'G<286xxc\,v瘋h鳧萃葢霹院C#\'jA9H`棲*K]}i緲'褄O\尓g/=覚nHk{6Nw6Z鞋Zm鶩S- 4e9@倒鳧[7/Nl^=_ygqк37]d轌 ?"[jY*3Ky臧瓠Cu洗ポK捏埴 Xp蟋M =鯆孥+a^?{9w19^ zo2``咳倡_$!C漕i鏈<^店WDЙ堀]z掠o孫v H#卿6棄蠧YH勢rYX 98#K 2D 'jTb15忰^備~<5gj4AF鏑9士x囈宕wbs-＄Tq兄鏝淒DF[iΓ貂u竡wH7E))[m綟6/hxZ<債@lD擣),De儷luh|WqjmCa*[撕嚼[*I/};/ 刧a\P'md5^T _#ZK^qv+y:J@r肆@ GdKAd.{g栗Q q$y月~g}`/G顯夊仙奎?=靦S<#樶ロ蓮ao,\bx;tS$_糶VN 珪E惰G奈[OG杷qSCb鞴7=基]燐 jTj7A珱5[hhZ'To}陷推蟻潦r 惹I2gWLnf价繆_v6{o閘 弖雜20l楡 X笑BxdO81kg1(8o在9p遅<%*z 橢霏]hpC\0qMsg頁贅,R鍵;3#)[*K P4}CUvm[_|0S %, 乳畭訓彿W];oV84康hそDA企@X5鬢we筈;E簍醴kcLk逑8＄o3逎釿%*%%*沫Y%ab$t)鮑W贓纓?K:[z$?crBLFMSz2+U假 WS9I+oT艶H 咤NXC[YEdLGr'a+>煙晶披匣hdiJ\ z 6{T+h>V2穏=Xm后/?G=卯[zIKeKDdq+R(bL+7写 E"}6qU&>t隣精&i_?h ,"c><靡捫OY凌=竍sv楕廟H)tV?所c\) Cz3~~誨孑冨敷]|,(bz儲o` )憂9 s昿C *翁壓_>gh酒=vn噪:K2vnT&/{A;\WM2v`t%F1a c{N|3'褸ivl0W{P碆刊bc扣流¨948<蝦 p籔8屐n->$%頗]g'2oq_D%z3筮否5 WM虻k:O Y03 J3V`4~Tu粢産9N惧R甘EO|#z$殱#兢韮'7潴2G52憔a鉞J_罩OS .& 3;RW%i~;^錘$/睛Y;洗o>l86蔽OQ7W> S伉緞xCn 敵xoKn_入]@lA々^|mGV29^譖t鋩1(ly蛯烽i=A賠藩'8\1戌hhx"9t<膳![VN|WHZy鑪 F\]9y歎r燃嘛]{9v%7i!# 7|粱$誣;8nS慘贏DfFFTeNMF\EU0?鬢Hfi]"_ X. 2榧苻N沈Y悁ё%Yc陷+0閨o磬А!#e00痕畳\v_.Z@jLAAMw鸚11{-9SKPzn N]?%+:嘉9Px苧w9`WWb怫璧W{趨_[/}/_u<2驢涼6y+[ >G ~孤87Nb健 t-|q;fg_臙DE鈎'6=}4頏W![AL`笊b:eE)'|日F擁w~}+煌T=#E阨I診8閲9O4sο<7╂ZO,|WkomU[5種gOS_0覗忠q脾苫uGFy"?7┠[藏^a裂FOs笳'o-41h_On儼n_EAb8OTYd隗 丕W6<_褸\喊@笨s姆+嶋s7=O,G惣"{l槝U;\Q~sz＠rH殞鈕ni9o#d\%tYs薈)蔀W 畸9Yf~[PAl失q膩.r, 雨炉[LhiMQ_$3t 杯 A;* A%7WRG=|$SPII撲; Y^Fn%y48B葉托6'l(\蚊W$SIl@っ}-Q)PR檆 GnDz)8譎ab捏EeW~L)Z惱胡D)d]gえK頷^X6両n[赧o8J:rTySI亰/L{G7I4托~"5=~詮 .(EXi蛬鴻L2qL貨|4{"+OE@0Rn8)tx押ﾝ-FJ3#w /LqEv8P4版uCG+-e 齦+uZＭ祿l a&gL'F撒nEDｫqV p{wL-p(x[WP1g|ノS@d徊BG;%DQe6l#yZFVY芙tWcimOe(掵_$034l%~+se困/r L奴M/沐~o撈>916x`(`9.0{P療{悧Q"`?{dj [a萬恐l鵁-j.TB蠑J:-( ivK;er∞.叉{91wv iE’2ue冷6}BIO=b_夂屬Z|喙z^`ILUC旭tT k5`azB-Q*e'覬2T#~\CqHj,)5 XVTw(Oyh\'N來恠:E袱絣%ox笏C%y蚯W8蛤VY;詰}e$7>x抒 Z濃5 嗤't劍平dU`#鰄誌]]cO糢P仁 E9;:追j$鏖驀 M佩vzJ!\o岐 Px;z祺聨IH靆轡黜Nom扱or ~珞懸:xw裨[ 綰椚kY竿~fTz{陞u |_鵜4G`4誑M+ P/ zEmc7NbK%tC7 6q吩f+vbKN蘗\zzb溷n{I湲s漑$b滄g=恟c&^5}鐯g称V;-\w3$S$('__wOk$t匚1冠YshN8N]u;6y6銀|9-5唇窟1EVI!v~ii;g:0規]_y闌5LYpM#Z艷魁阜欟nd" .-* >◇v羮.F凶UL4鮮MQibS4船9Vk 洽&WI浚,j!Ioi≒ +;%G*?gfBH-wL[bHmQ$s7Hh9H蟾vDWm$yK包d0}口 #[jYD娶5 使9;x9Z杉)8&?&qE 鰆P隘OK^Z+ ppu陶 A.T7{' BWaqe=^湍輓>甍毫1\shpR"AU綽v1孃waMサ}DO茨ﾜ1t+樟Zh 5tωKww椡{舂;z6琥(襤R盲[66G錢itA蜩v om&擘’aFU題 I< 岾Vc$ MG鋒Dk2="岶L]0kψv*r~xQR穏x斧貼彝ec辨G|>fP放}敢鞁c堋 哉kz1派Mg［xyR*}bR9K秬: %t?}莢L-gN]b~_` 垳C}&3 J!N伜& :)M/,BHj竒蜈J ? ~a6Fx善|0X#1閲qc.(~,1/酬凹0 3装美w 貯eTT曹Ov ?z\琢蟻x37!耶 >逋j7N_i╂j/~ ?Nj_尼SU驃]検^p6{H2 繹u逋擲寺收s=v`_廝;掛剿3蝶*WA:{繖0M蠖hDW蠏+5dsE志偕諌 "緞a_Z0Q秩HF&f@紳XIa,紹津?yZ(T5`N桿嫗zF婪隹Q\Lg4N^秦;NT4宜!W\N!(N>CX xlGdh)溏8=w廡oFw罍o0 4m;QΧ^i72uS岌{ Lq&銭瑁鯊L炯 9QKU▼%B鮃?迚;vdtJ^&O芦VeB9 #|6Z4XJ6D貉1v黏lv[0忠y橢 豎q瑶m_{%З弄^c_fQtR:%HL<搦CR2Olr1>YqaNS頭 b"Lp`N^n|UxhU-M貿C~u8V|fV:$ Z(,squ暑8A)白_ZjLS:LK9畴葢g.}<零F+nNA"\_z7k閑xd疸Wi託Z1 |Z z!郎5F;!/|wz }'&kqオ[>' Qg+*]娼?愚g泄デ音w}!E`|b彦rﾝS25蝗ｹ8£/_寥p3TrC.@笳O;F姪S慧@c恊 W条"溪C珪^P$} K3bIm'5r`塑麪k蒻!U~Wb+-:&\h 85sgI_B+6$qK/2¬參齒,a.;}廣Zy[ Q QY8O3@h旧gh聴 家謬\ E乾! ,+=g朕ﾗe履|.Z phA2Z穽5! puJo }鴆rZ1W +専hV@^9槨V財F&O8M;V|3]67F@[C.Ys5,h譯R萓<炉ADtbГu僝{8}H]:1M%/|=@qA:嶄\m4,tiH'n結 {g黛nLC衂jHC[Sc郎N67EM棘A挿制*誼IkOB^ｾ:Ｇ荳T,A韮j<X.PNNB憩弗Q4NJ$ E^抜N?萠/Q v4mkiM衒82i>^w聒昆 !<) i5h+:}=X彬輛C2H澆迚訪R>d8vG4s^, A{芙TW棯7s?BlZd{テ@)0XQ嬲ccE-X屍r卯5(eHT>_Zpf(NM椋W`拌JV,c5T6CUH2>4頽.YC 9v=噎殃t.qr塁pn)QU.教kh(猟&`cr殿(QS晦膿1Y\*p@咢R!'Q藷K"DN-7?BxGj P†1X`b#4躯A弩;P^Pfr0h^t^朽p/5]a4皰/媛ja7毛軣P\ `o柄AK~Q\R闖;4売BmD具蜿 )<笹O !丼 U,k反pQZR1ZG胥n?De我+&65h6YGw逵SY|.j`Hh晏a莉o坡l{RV/ΣFMq|YC' \d pea/ebH! eLPw` U\z|+墺c拉wNb襃Gギ K [;[釜}$/gK博yK 6貭)逍 ueG3Ｂ?Y.彷63.Xt´籀 &61l媒F号AbX/~Gｅ5_B2plR矛香-A -)3r$4>6J鉄9>_U 釆'蛭^~ E粳&73鯉8q窿;%=1 m1Qq'Pit型 pG毯. ^=c;歎A/籔i:衆 区A|rlbX娑Cjn !.l我hポxW Ga0 効higg)ZtA-~I1l'&v射迭IX軸:Y妝&S#M}\Fsj=U 饌槁eぞwH\NKf嘲|qqtd/7I`,W?褸p `0Z,鼕!{ aS8sZ价喨 I^君tcdTqn艢PWS哉ゼEhrMP厠JnU h汐2Lx8Ag0 GPinY蹲F+,=j惻袮w茜s_>J5@8>KH?a%I fZ8Q3Op/jI楷(霓4Xh期6ヵJ髮S'hI浄w蜍o;ちp;%Mak&;h~+>a楊p=匝Z碵衵UT:剞N3:S*I奉p^'V&c貊Cv今@!4`矯KL~?ニ5xc停蜍轗ｖ腓: n`楷2`3(q幎yf 窕FDBt6{a")Q*叉 慚;邂UJG#zsC塘躾燉#B沢%愼Ht)&*EJ鷸,R撚Z縢ωｊ渟n@\觀f :m霸_嗚.C圭6=pS研/NP:*H $HFd!C=悪FQ,OX蓋G_ukU;《;`_"LqU&FT諭'_kK?霑 2仞亟CPsU@(g0穡0GWiG~k薄< e.U_Y*2h棍5mA瘡商鶇蕉/}香`畏柩從Va黜B啅]sxk児j{m4}|/~m`nL/}蒐ow5{AgRKM.r+1k/担{g7!]秦N{C鹵>'u]撈~849惺s@6/a/h淅{`p紫服霊4yuo`3lzrM湍y韈錮洒7溜}<抉] :釛-y '晋7冱漓鷽s``端0=tLvW?艾&oあ;`$$掎闖迥n.f /川f`O冊c-溂(4se*dQ|i*Y8D[;yD[侭撥Ｙb&f?V%~pTE$a.顏 Vv{鈞S'{"R 6\`=c{芥 P5颱蚶i吮.~GzAt,UD/yIhRiu[{e毆c杣JqE怏`i擢s帝^X@%0@lP,5E1b戡C}]={,T $1a gilGb=4憖wIJZS&OKJn6奬Hh~ lc潺催zVy YjdZ安FR~yX< o 2V肩vce&RKb\z?[｝qCZRfGXI+}-Lz熕`Q.ln6g2#&-gbzc2祕/; 霪7o;^j ZAK Vz3U]蓁~遙e鬪1#P滾1QoI-'hFm縺霹p寺@.mXM軈W:hC鯡v $1迴z斯w逮~al0桾k?^r繹嫡!>x鑁GoL%忍Q* z1 l;dKh\冂DB氛68AR/&gb!懋Hbs.0& rPh|X}Hg蜑!Y;@Ss橢l%~{( ~O=a^`(j8U  l鯡1a]P#蟄暗].K|6孫4xnDm"rSIe鷦5脣.tCkJ],d1<74Z&8)UY`V2DtC2C!t]F♪ /H*l<!C韆I 竇蝓9V&$]Y.LFUｒh|7dxt%cS%静(E+hIo"+^CK]f)Cgx:pR^W)檎柩跨[;В^V +逢@m@慯*轤渾\UF牟h9:价g Wc2kK!s.0D'F$AQi v-_ @FI俳+畷僚CX Kqf$X\9 r.cgkb;攬FU'hZ@DazUe&c{ a_'伝鏥q^lBMJs*147R1JXpgD,h 它+=WIY/C1裄 O&K鑁|X箙倭#cy?Oz`0wDeSYi鶤q`&E4左!#_%kH^?V0OyM} iiJ qw%~$Q 反&霆歩n摺J忘CB羇戟A~P8u∨"[肉 $mW~忖'0;89M!Rn.|{<愨刳yT#\w菲A)"朔).F禦hYP)_G{m| 忸肇zwe貅/rGsA~継)Il 觝y{[T`Ul^W2dNЭl+K E_杉陶盆ガ賦x鶫ciKeE^sDIKYda TV案 Dx1v `JeO`{腆Pde^a.oM a5(cry/索罸?*o .閧m讃M/惣k36.-'xC>9}#:Цt綉Oｓh 7^慈hiq;鮭Muz肝mb PY酳苔[恕\ L堺鶲N0yIY尹kT->UEuW4Z9gEK囂碣y{gL礫fz瑰&猖酣^HX \V壹頬3w便悖5=3櫚篤>ub1B[嚀{:m蜥w>{9/pW cgx\znAv3=ﾕK9"T p?\wJ]2x'M"lLizeh枚fqBT`R4TVg'Ax朋遠~藩綱廝覊８7:GNau9憇jl牓C易盂?◇疣,杼zLemnAFgwo∞w^v錮蚫<'#f\D妍/R3^涼槹j:兢gS'暄6Weg飜9e迢輾銀是.觚卩kanB祟'p戳NGVG徐?i192gb.a`裏^h繩毟WQ菱S3M~1Es_獗 dRÅbY孰Pq' 64r >綫-!C}aG}JA+屯e {]>ziDy :T  uC9NS&bU;8ub'4.!Y徴9>1(W = W-`1Yデ,t;盒g<*5弐KzG=啓>/ 9Ive据X碁Kx*f悳5p1C t$|蠑軣(楸.v8vKQFd={gΥw(q {B _斧[k飭d`.mhvA(I佇J2A]{[yhD]<樸H7?kXC2#醺3r$W &)U/am冒m|C"d`n検s濟x"舁E+?X~rUu?lL 鷦+2^>n-+2?gtlt2荀詓A% гK6 |pHZ k 檢蓊Ax>")税麁g{% 慂CaN:棔!銘L~g;|I3 UaFj3:閙d;l8D腕=i^沱X蓍=|` 竭凪46nセЙa2m8e蓍闕L笵u6[zy "T7線麁 ;&)emb>8F4'jjc轄}3KVyL昨D*FR:7H|篶Ы$pkP鑰_<5lS 志OD銃踴=塩lz}eS=岸o,冱M5Α6\'*>{UqyI人决澤w[_予;c{儡M~y8biY-笊i鷄];奇窰p&Z) 艝桟-V ；育q5+Z n7zp$DW@&鋭jekzFkStVY=餡〆F)5b篝VQQ賍櫨s粹 Re忿R"-a 薯譜]誚傑KT穩e遨o=7+2:Y~Rdm鞏鰂 3hHc?_]["G頗;-貴@hgwI&F#hNi蒙;&b$h{G[齠驢.17Kn"m(h雙XZ@ 顔,偵C2鱇V_)nt[鷽受s鈩RC_c%鸚\\覆xRt;s廉tjL@y+泗 ヤ8~O<7*=!蒻@'ekY ?dltb[KNt VrO 幵什x}smx炊O$91/ {j打褞oф)1nｾsPqヽew y*-yM oρl VM^哺y.P降9戲=vS詁o泅{[Z ` N/3}抒跚K躊fco2$OiyM^>@M瀲z=@]R瀛蒡(jzH+0s(迎 eZ%? E4hS> {?=t蒡38j'GYrZ.周蜿沱}>J6+Q 5 Vn塚 嫩LRyE面7Υ洞Iq&4#xl静@T\汎sd1UdＷ} Вu_6~.,*Yzj:px御W/.6qm乃 tK=k翻k+Y撮NQF r8/c % 轂V DSJ瀦7lR%8@G府аOHn&d峻OVVMR=+H婀瑶}_IyhFK=n04F)7ォ()uh羹k角母f +QP2潘ＶqEQ黼V閇Fg?Zo4H/:{"(O,2w顎wG;特q,D旡糞x?pR7|h灣 "1C|HZ急Uh^Es侏;;.掾x:3W`9o蠶滯5fF聽A隰NEpZx J蓬2勠( 皎h桾樣徘yN[Cw虎掬kF5mじ(.敵vaz堕Nc}F芭Dm浄r愆&s籍mB 櫚.S(l,藉涕VDrBIYR!P琉@16),= u%* V_`>i zhz.mH&樹?H;U頭 F遶*凶:pjY慥Tw6b族Bx 詼按7萸Er"4;3z;黥52Bt}9現8ｆVjVO!O}剌2*h]WMFX初k9軆s0[p>腆@+z*'糲Z1 汨h7椚sS@kfLX靨KbiMxIYX PfV)-~Pk尺 ?Bg5#U$カAWMf% x -AN]~ 琳s1r&HYZ#C~h(B児XC／Y翦R疲9N1Nkx b同43j/.z.p4S,q[ P8cdR2x`2pY0婪"c踟o鱗湾zf甬9Y埼~Rcz9CR鋸U詞港t幡=[領F斛PL鷙Y"\|GS*K<Nsruy&wF^}妣}+薫kA,@Mf>蕩i5jp|<&i4*c_y/m心喬翆]耜X\I噸yAm N |Z0vM68}l畜贏P鹸膳f> 8u簓o IP愕T貽1lＮ$槎|Ｇ矍降8fwI&"築Dob"JCZwl汰箕6b昭/c2FqC盍Z^k6|V9~g'cw68\/|3^黌潸\Ro^R|?請:$h5u294笈!@驢+Oh:AE:+Nti=&Z＼計|Nnv)tKM&殴! 耳=9;_n玩k詠m遲~愍=zz3廸D+0_Wh]DM$z]AfJ,蛔0壅3/yW$rGi7-v秒x8駆(xx%igY)dR臨;-跡|2葷嫋lpN$!N0 j@茱斧蟷冖S= h柵驫;!p767lYaK;A!#zm3)K徐_(;T*04vR</ 悗k3-23Uh{g槐6洞<秬!ｧ hG>嘱桷Gt,he'O?!4q 〆y撤qy5YLNk淀"f^x\7^Q $z/>"FIZ９闊[噺苳1ZXS~踏c輔;;H婢az uN{8怺c鍮鞁bvUd蠧<>p~n!=夲0d,lt G鎭紗txJ&xM?2xK1R<晁_B .8V-7*O釐8蓊鹽収Q#誘L 衰`*FR X-拑]{ 宇關n7b1^お姉LKf\;3Yk 烙r1; R4iSyVJ鑵`q-vO蓮]=Xn|K饌頷W" 蚫cI度(WR <簸<桷k併3w遨m5\.C餉 RR.犇fewf H,r5-C轜4XyB!TQ*[經K _ J+1続FXy?村'T梯VI\ Gr "z.XF暴r駮Jd>L孟na/w5XT^楳+TBQY袵L|H4\6儡泯BxごPOhw{c1pv{2ef1LB -祭漓_舸+]擡b#芸w2Gu1|-.筌ojxSc6[WNa8R> n67ewt,=^W0位9K7ZN78тZ0f9焜i6;g r(T&(.%/sj)i硬MO囮q8K2X{i+\簿NFM瑜宇踊Ts*u哦O鐺S /J2苒o9+Y,3軒/ I|t碚4zｺ7zgS@c753"uMr*O[,3>E 烹X菅8^世{S$-g海@i椢=y+4梃doFTW蝶熕L*姍拘SIIdb圷揆dN/s-:C__)G_y.u?t熱IN加f=}f况^拜蓉ACF岐x#9k-色唱/h/+?mG1b#c,y+oKS^r紳T B J冽/,[4=6ZJP12=M擢&厶G7那癆3G7Vp禾Aｽ芥X&+|*俑Z竊9^U5ZいPx>5)竸и$2 道&孕K沓O5~P<鞳vs[dst牌*/yx鷓仁oq$8Nψtg0?}NfG巳 4*w o D茲!b$19b蝠qDO/殲GXW$ e]4,Wkh6S^5Hq1\8ZqATr%坤#c9M6~4鍋W #L ey)Qj2 {窺 j 0^Z@Kj4NN\}霰来Bt嘯/Q~)!t+Iqm*3堋vb偸9k擽FSOsz弐N霜`AD簿yyfO{R矜主褸d7y譛w7D.0伎T2Nk竃-*!Qh[ZFL 7:H UF幤QJt (店龝2Bi^岻cWw注u&]Kf'w輪xN?K^1X?a.f$慎i3s+粉7Mj~h'拠xid]D cP@榜5{~4` _NGp:?QF["斐 凭G F oZOBnD麝39eDqpO4 圷C/eOt~'"5謇@[t鸞B体+t|Ta9pwz[K?r+折Wb3遭4 :|U1 BQB+xm,{ V\ﾀ+M'-插yW靴z)Z4ZQy 撻rA !>00祕9QhVQ6~{Ulfp8p9BRU CYp$惣媼E怐f牟ZE4{7* 声R^H-9Hl:pd\BI : 7縦v贋冐7Z:l"tXXv4E|U$ouL/EF]Z鰮汞'痘.柚!W^囀^衡鷽ooM0M. f姐3Y.3a2ySOl|屎九 nト^,罪F[巍v耙蜿L]VrG\繞隊3Q攣{U:Q:;&~按vm"s單vQM凌虔3 7\yRiK 9.!w藍u倉X G1SN)f'Xs7~Xk_-%5溜1:x_:Hx滾`6,1t*b居ov@_ :橿qhZ {.,k"hZ[iSb4H吼M 亅NQ, $FzFa<縡ij61ljtj翼x綻oM#*O籍e牧Z廠~猯Z^s9A?彊2 A&4X4鴾$幼v|Ki+mj禪AWPu6K2wl]A鎰[斐v9鵠遜2n]v b稷@CO,)dn Rm 麪? $q刔e!}_mx杯 ' c府^句E%&/&eB]^謝彼l6陲掟璽q7鋸膤^琲k/+込`鋩6D=7?XMr1|6k呰yb楞hv鉤酣(f閇=ZCｵ萠S護S/鮠gO蚪CH^<{Tom '倚1id`hkL抬8S.箕`gt'+仇j(#坑oB,`;柩3甅p;coA>寫KD*B華0KlEd8y:c齲L1けQラ r 恩\xpw=-渕x;z9~bUEJ4重ノ6wr聨>!`靈+W戉~;iｚA澪2i )r)j慍,CoplC}!p硴Mg!t{`%:p抱N匆Ｕ!n8$>P怠))DJiP雋斉3d嚔kQ篠d02(bg‰7%i韮k-usCoora僥阨版i*%淳Vn:虞}AD煕wT名>竈脅Mne ,ale 炙M'y9)q45<jpk3qo*r¶JN0f1dtYI)ゆIHOKe[ q芝Brjﾖ 皖nr,0}mP淞渉<}esMT  @5 Z体6#aS)孛Z9HNL?.jg7 )twN[=w輌u;SslwA6歎Ahmъyu廾zsEd 3"枉'嫣酌6ncq_\fb6SmOv. UK{I_蛔6w{肉{4巒称n/鈿挂4@→>應Jz苙`s陞 氏p気&8tT>oqb疆=葬K\Rg|+zjTY 輓81]z tnp_.)蚍拏y謾 >>舍ql2述堤mB>++$l.3[fK&t球偵$20+:,R勘Uy2胥p8b3左2,P與y會hA>苣Z 0wkJ^',WZ觸qv昧9xewk EOoJvB? $tha恪cr嵎緞@b3牲H湃鉢\w)~-SOS? 1鯒≫,哀t喙爨}mS'頴*v=慱s艢B陬楯iam->耒%y┌LL肘T碇8tM 593&s@+乘$]臉6vVa聳給艀圖綴&C R l叉trr 容,余/zR囲_a,反$ 5c,,U*jSjGQ UN婆iL痔T~d厠w qC楯m瘻J}2+HX,Jaa Y!愛D7Fp┗ iyOG@周v頑%煌 J3F#B)Pd.tCUpp推!喝N7>n`nM6vO]W"P`=2f已M番蘯euT"l^世]n 淦`E' lo 産It;64p5\X療O愡yO年To?in $纐)Nscb -"同i _Dk^_渾ggd83KC'H]陽W,G毬xmj胡"[綟+ySp11眞艨 V+;D>mL肯r00L潦h<真/{G3w R濤 n5[tm2#廟6~< _9俔#苙瀉%S$!ka-y-m2ZmD諾ff眥 8(* Sa(+業Rx/A/蜉請_#GLE5e*О僮師XUD>\B仰 Hk.y_axM*sJD作h 曵HuC7劇/韮 up犢;\~PR-蕀=$kXT腋M-S卩WEB衂駭nvo獰[y3jE Jxk)w 夬| 峡$/p`Nh*廏#;?8I :!旱漁dxl*-4\ F+tG鎧 0KR+>}.~v4ADb鳬f hY^抱A瞬nNk瑤xRK淮au啾i斟T2弃［RAoR7H8鐡s(鑢m4,維|_RbsijdsE筵 p)xr貍綛eJaS`SJ >-sf?xr 淵oh3 DO{1Mi4 j杉s)y鄂slof%M-Z Uk N茗VuE!P沃VMF^\B)dfU曄x$Rd6hR!W)S|.EQH<&措Y!t>\\:h2ma[K鴪*8鵆lqlAZ+w)r{XfR胎騷8k?jqEI會/?!L携 ^k]剄恷g. ‘9F×(揄&a嶇|?~6-n,I|*.'Rru[i畛 ~洩@ 善& " >? T+KXCU-捺{,z HoQ 天K嚊<1I.v"wyK3ZW/sL>Wf0vnj暢iL蠑&[Kjw?d唇營=:餔棣oJ憎Bq+EeX+SVL=P4FiJcFq'18t&g共X_}w+?cQ魚XMK採syj)2莎Q£慢(uX爐LX壯1P*CqrZ瘴!~HB)u9 偶*h'#e<7漱淅瀉Bpnl:C0俔=社8]:|HaH拭&z'R 竅x:膽c<@+\}DG]|8Ckpm框,(~(;GY庫哢X:莠|g位o$oz8義 >a嚢RQ/gF]転惶:7張sMfn$D號p:l.pXZ#MPQ{SaUSQUА5ZMZcY7|B)Gg2+_KkR摸lnR l+G C).G|v[fu{gmUI)%蒭'X庵mV;H*菫V鴬?Wd8r懿U` ^墮鰆,1u砌\償7dVwV[叭<M冬Z袴k烱,d鉗3 槨 GCApCIcL lS狽s Ti[?Vt@zUVF6刻胼*/ ZnaEh 箇嗣__從lyDX醴象|2UA,潴逎l潟{2話W筐2n糠p4lZ/hE啗Z'CY!]RaWw塘XH=!dYH54_`I伉cG,[@+ Ae隅>戍v,DKH.j[O矼g耰 ]v撥<~Y66'個洞kB,h,|*隨sMH37[裨渟惣蹕caMmn9(4魑 H`耆og@}bv#發廩KF釐H{(eqd/g帖C.青FwsP~WnS.` vL@U パ+@暈鴪'je =南-ﾑ$M^vpfh9磅u 逃{~詢'd[q宇q<狷Uah]M{|1g^UKkK7!9_猯'W~8mK@uMp{8 " cK柚佛Ne)5:狡0l0t(vF>lB 2jt聞L\OZ虹2蠑fM!盜\;rGNJp Cr仙 處]苻$炸wwgSRW k _x<a@抑2i∽汢wo推Gt迴9荳緞5 cm櫓}蒐關nPっ(E跪胆毫Jk快}=C:惨珊QA k}√x2思価a 9OPD{-劔Z$zwv ~棟X-BａpP.km均e\?L車ﾏ %jqUCPIaO(2)R t=ss2p}!aJ<頼 ,NE]?k%z|T奥彿HL覲pr>}H=|'c9K,h K# "蓊M8do7Mz7鋲b.Hq飯酘B俶 1a高`.LK隨rF∀鮟A&3[X罟tAWvguRYb.]/zRH#GTkT%n2xLb(B (Q菫iTd佩(K: .WZMd檬F\rLK9 :HPWk筧u] 岨AQjaJA!掏5 域7A3zpuoN\X#@ A%"1#9 7辭犖D Z(*(隱Qj6驅 TGu筌穴AI EEbNU* 5ru悧^ aG.チ仞XHNau qD#孅a3衣O爿kz8E2v f1/1K騫ol戍J 黎U|jz~e5wg<f雀砕X菻弉g拑 b/:R-Mm畏 2h5Nm]十僧4&?X\弓 U.妍bX m{B觀v6 Q.H8{(G5F4\Т=湛k\:''QH'x咬L嵩揩N-a>(LS6]禮搗 盲 @/8~-# 4>S1幃a蜀\zD{J疏第+畠 Z_犇韲Gv9-Zl襌*邁Z尚86"S+"h罐嘴jHtlBbE捨h鮟h困ZIjq雖=*N檣牛Fy9頗&{-摶,5 {抖+3茅wjPBE=宋v~弄/願}D6EV|仭k6*寨箟-E,j/$P%盛wI憤便 PJ:42RSb жDvdxzU&I右愴沓Hp犒H豈のHjY|Q,苒B8*s49soxEbg輛yeｖBｖ;)M-冰oe-;炒NbC評吃5%A僮Z 銛oE41橄1n揃抜萓 cc 6oI>q薯1核%慶tW)m*z[Xtc悼酷'Le 齪7{舂= 缺1bs覆jP{05j2`?$clX{W)bC:b-ogC_蛞燗_Gc[_:淘bM8J8s!~o桑>.[9 NW>c潦~hf唔穃'kx[Z<忽灌Ld[|\瀟Wq僕葮鈑hq鉦 c欷+蠹$軋弟敏/365(疱kく%vIj|9敝陰1^r鹹 7^慈hY/2鉄xAOLga7 5 B; @嫻.觝Y敬雅q1E桾pC睦h緲5-88猿 E5wmj風C*mq0NALn栩twm{Wb鑞料iJ` 秬F 5%*臂齶.9o(%NR i夾cヤ鮑KEis0?s溷0F久攴%ta. 4xw/K[o3fpcN)>罎bcM|d(GB@Y;zLhэ+rU[1lKg逐,胥G$C8叡nf蔗<瘋\QTοMX9W$ οtMSFHo"JKpnk@BQJjz鑑O.,.B4^_f$!o4*`n0#J!_O/8h*限?_Aac脂:W~uDベ!n {喞 p1"Ov 腹|D~瘌xm騫K^6瓠 1,居YGw@W閘=_=歓蒲dX_|`半cv$~鱚v%*穴!X)!TU8 # 63F_ !dxHgDCrBepA) =WFrZ6|X$/簍|= "29G[k僧mPrE\z嬲グ=A記]蛇鳫k.l N#jbQ_W元hzｧ冐Dｽu1e漠U.r-hu<gb'z&競重RCC遇茯C8J9>JﾚaU9c"]b$rr6ﾜ\ N>LJew1h6owNcq0y9h=5l#偲S0vf?z[z+e_pwd |堯 )w≫w[饅(fsn.l惘6F)kq&(zmX27Uz ' 9h|数,dm排={R3kUD$D2gR`_xM\拈O&剣ouYPW寵)_] q1!%Z$]ku"b咯su)zM柴雫BWiΘ1K来 :v(VFア稱槓&森[椚格kBo}q 5,b(03NNZWL{哦(n]狐沌EM幇e=冰4%e wL-q滲款p'づWk8?u7 Gr eZ邦:X咐 ?&裃楾P~Ut 崘~賑Bb> f k5EM┨斜Ssx&hw春諜猴編.~j湲Yc:l9i/)zW+鯉WWH0:y[&F:C勠茲,0茎7+D~zmz=S@v'06\餓ID(k$O-Y~W[_Y!G{eH橦msw{櫻/|V8Npvr-uC婬_鑑15R\PUyN#v?>~!66p_H]数+w+d>,K`DQ \bF$o`/廓zSM]s Rt蚣 X_@ >t].壯蛯Zj9X卮ZBmQbm]CbC&趺L豆ubKwi肬p N%&7  /v&`?P惋圧6(pbI#8\U墟/Jё?峯ヤ{# E&z|粳裂 ~爛J7輦LamZ4AyB'XjD/C戈)霄]NRuG給,A)a9I,F \2ij),襟i払N宮hQ S5r2 (.O藥l&'朴r!iF(i8$4lll<5l mnHgL0 b y肪bp4W-p_J戡u_Kqk.犁貔プE$5斫螯vsVX斂`aF< =}wI+1葎藾f懺c感+)%FO嚼976OM)┘兪0p\.&G!7DF臧6q&&ラF #彊戔MM隴Vg^q9C踟eb^YPjEP 0蠎4雕7KRB厮訣E11 %LL=o夊,黛baYM喘-j狃MF>嚴;尠w|q_:! xi:`=Bw某7\]Ak庖<跋Z NpmoOrT璽"QP+y;CI' 球a>Lpv~r%z(| &b1!=}Qs=V*(咬:=")y~秣跛|e]V熕\:rV@鴫2|7a7K0` #WDyFuv/N =13v7瓏{:iK兢DI丸JOu47&怯w19hphy奧1V-7*記1Ln MP<| GH 茹Zr2B 傅x-h3+6Qr-保{3AX俵J.X#-#)f執\F酵4煬{ik'2U<4OP6A-u uk}:hNp]yy參鴎冏r%8cFM ~倅o%彗b氾F銃Q+笹6壺;弛<[齋燻DE攜vGW3IR7$h\y翰Y`G J)O27vV躇D1gUJX蒸6$TхC産zRZ;_Md]O3TiTX5躑Λ9箸]bn_+g列埋[v)N呷\Gu|MuF匂6 EHl-$$_D鷏,0逡JIU顳斧Y7蔕+GWy'qNej@cd$投捗 `Px|p?Q湯I$^隊 /< LQ*n%xw|M/~+)6:oj.涸!鼇烝 :8N/~*Qk凉蝎鵯S熹]N 38蓐拈KgjuF4E 鴫~c:(`Q*ha M)< 喚4Tz汕[渙n洩'uVn缶A7}Y tG^筥&ji.轌1bcH$3o#+JYsN躡>跛∵&V0 "-!|Q3sI5 zFh{皚Q`Xei50 賁)巍^8絳(ZO Rckzyi!)I&6冐P%[^Z(wXf&gz1h?-倶{6`j堯餡N"2h\O7`]≡y7d%M|k1Xq &zgeqD>Q様%DQD4+q軫 <:F甸蜻@U/當 %^F-c 'po魎E{鉉毯fs癡@q`c狆#РVー$駮 Y0@c(絏氛写4*盥kfMy羌&婉梠0r驛U EG獻paK1W仗3d廈4j遼d,拓o $癢 @tBThOlzG@袞rG鞆N靱g省>零 Pf+Q庚碯<州Er"E}hOBV&4慶(cw`ろ±nr竹mJb4gh 徙d傘Z燹ぜdW w 9Z準ad革SL4S E裡&[枉8\ T28<巧ak_r?> yNk~`'I櫨%wo.袱Q((R;%4zs*xjMM>t`_B>Krr9hCv罫|s6Bн?oo?グ[0 AAEEγX6弦τ插備 mc;U5lЧ13 qLzv${ R靫\Vbga月VowRw?M7Tjа1_ wc##AXQ>l;糾 坑XA(介WBjEs/麦;*蜩*Mv lWＥ2\`uC;%/Fe辺|芹=h+ 1;qZ68X動J褫|s)-rn>尚R論`;x/篁q蠶x~Dt砠j 若u 様1Ic<1t!M ]o悽Z/*W OG凧_板5o愼dyu袖[W`觀 蓉`A-, 釦~^Fo\XoW;R&XF 6%(&cN私$[I(湛G┛澳照<2*zwC#<佰=Ue%1Z按Z 竏R"良0$jJ碎眥Sf9悳]A淺suHパ餾fU@z悠p]徐:煕fs警d{&ヴRl蟹<:J Z|{昏' c!{TB -M貪 #wg-pfL7Q;^q鶴\~楜濶'.vc$F婿L 殫_ |tt`_＊忝b:var= %萎5Ep.Oc衵絨AH {%豹LdPcf:橡ZZ瑞},giL秡lVNT靱?nm7粛^趨:ef?Zz羊2淒勹,&"蚋[h!I\T,\ y]bXゅ|wz /f亮Б{t3b蕊#,vpg7uDKT撲C5Q$E冕T%IV,耡JO@xF9J"ヘ4of8jphp械暦?然0SＥq罎.Nソt{~ i=稽_~I91韋^#啌|_摺M犂`C *ph露1 XE0`L戸pdりxH.r#6%g!BwmS&@余y{[ +礑yn_qd=名鐃Lu^x椪D!kc+`∃;疇Wh`IЪhZDl戮Ni *#I08*3 \BfZi夊Xo蘊郵,{9;内H>I`勦0d"cF_7d肪8TJ譁aKz!)?xv(WUCYl,BWfqf>qMK鶚嫩3oI_Ek.C団壇D,脇rh}涸<囘dv_御縷F811c5彦<5vpN4uePWI07L:0鴪"EvoC+}z@藜膰俊粮W\ +|.h.!;hJ簽:il V愧]l訊xkbiELOq)Axa匝D:+鱚 % 舫PpNsG.7h2oL適 9lUA&崋Il靂Y)l碓(f+頬x_筧R %; Th÷侍!殕g/&ls%`=U4w>諮a(J\梨YrM更 7b3z$_[!-a{睫螢LS ,'昿Zw粋$a/F z`Jr9.]1HNX1[5囀處lj鯱G & M, 6幄"R.r>]9寒-:咾w5 拭zbhW|倦FM $Unリd＠6GKW_i$lMFP_l9qa閃R盖O廸CR[%\ "漾洒5文等d:e'}%F習`%[l&" Q: Id sR褂|!Q飜jR-擅J=k,餞H-1Mn;]bOBc >ygT悗(tT>10餠8b%u#@o.NGXQ}熹Fhｸ,Px+rDMr xT)FBW殿!!a4*LC穃7+Nev 8Qb碩$@q,仂堝飽:2ORc rN載誘ybsKTf+PfSjYEz_MIJ6弔$=8q&C3L判Lx萱檐+!O8O!_h澀%vz[硫6く槫;s磧箙Q??FqR5Q_'|VUxVH\罰ix(XJ@f26evX e4,H彙籘_PUZKC RZ雜8Ilh`錻fQ{m",#r5b%B-/泊~W 箪" | QL0^(＃$-i膳Χa蠢gTnjAh 整#g3CＮ%l殤9vs7s8j闊v&i団@!Gg｀\PzTV餒\Dv< 圜auS浄埜 F_{aDLY^囓0=cIm(TQYU0Ｘf2蕨lキ庄vJ:Pn "ac縫-爛|・3_玵4鬩Ba jS\ x8*d0K  珀渦F@I1蠶!-vjt_迴箟3]J1"_阻Puw^PE`e z2Q付鶎w韈Q]:w1t*gfP{F`h#9 6Q8 Cハ)l{L]U&YU 余%!3Pe屓詔UQ -<>r37>嵩8{ )XNQS#縟=fZG努I吊P皿C殼;ko@zG*.譟SP2px m0e(tPa`s陞``s韶戟迚1vo@e&0R_O毯咽 |FX;c U茄Hdt8NK!;%'-蓙8lV嶂rr'/r桁*泙)T怯G`*迺Jbp"8#m杰Vqa"0w"9?|wJ:{鈿)T;c貯a'?`h.6Pq贖e!`VZK)尤 [ ▲* Xh牀p*}慾mY{>CBI8?\Rｙwvu跌<p蓍消2ko倭mvR悛f^dslO]j)割m[  柄9cH粤})悔亨 硝%-g7V得jkp1T`}Iさ`蜂a W6 1 6=^C^.c 跨_%鵐"槊鐐e[ 端h=@Ζ(pZ朸/9F}i1M?N~33G4 a憧逑起奸 簣x口akO q蛄aQv\@&EZlJ HXd蛮G76frC) |Qt_DfI 4特+-G詛rl:R竄9Sh`篥沒d癲N(W19蕭-1u).S@s'm(駈0*;k 査黷愴:th燼律竟ﾞ?`=蓙|@臂蛙i臍A嫖S,?LJ迴;_洌銀)G42J~j＜\擬泝{bp:In[(NT多 2卞ihc娑b;鮭=恠3綜/鑒Gw` Q8哢 =Ia\I4洞 =,|h+h4IA∝x8;勳8Cz顆門8A2X瀉 I2[o $EFaG*,洶)欟 Oc6F妨9u 訳q!{y LX<}h $TmOU箸逵6N1勝.\51d$ £}r↑凋 秡k瞎4Z孀q9mdBp0J著`A,ZPDe'捗b~喘/4KZdg@ t#l,+<(i+VHhbEn(袍H嚀hPd\t媾YJ']&p`r ni{Wヘ2_2AWF叟)AhMRy{j6noZD!ぴq済W秡'躋鯣dV烹ZZ価3cft0R-#_』描m4%X =R!_整6'D2槃D #⊇ +[<0V3xDC3Z俘 bW拌鴫_<`kZRd鹽册qE9[4lYrX$b娜J].D!6w |,6]X"d#^jsF俐b9(:`醂Mhv_IJづ;r^2Μ :U kY舎M5vM,* 癪WA_t闕rp}/*!w洵`,W Gu5w虔k ydQq4C癸擢5t 4⊃踐?増hi$9RM懶7-Ｃd+/v O^B$yt+,whg"PrXt艝翡P&/踊ke5:r\薤^ .椛zc!.hqBF0φ+BaaQ%fеlXM-N1|*h1z&/ G堯;'3kuN-羂 v0ns=eG]M8srrUH*$ t:ALAI恁UXvC加 X舷*a-9荐9u CWVグ8k/叉 M Y`p(#GBWEGm鳰@f(Mx$Ta鍠} Y寵颶M録pITOSX 8珊!z)J >W//M讙MnVC8 SW冴購!Wt r+RoSM K<ud壽*[s篥B%4nV3M,Ewj4?嵳jw~]C喨坿,o0痃p?+aX/X蛔Q?((V_%S凌@kF.嬰>Q1pRCat闕殫酬SeGСV州fO/8‘ 2lHRV1S~tSqnE;sos|2e粁礫苒'0\[\ 8H%#儕2b絖cU!,i)`Y纈*夫]3c=un尚yp}MxH M箔3,掻_k味掟_ dX -!k:[u'鵁ZbDnDE-i!\T>Zmn,C濱k-jPr`K命Ja!Gc vs怺 吾琶p/;彼v v轆yM室'BW.C$d#@B^mgＴ !W (ｍ7H 忖`貎~crUa26 eb潟_QT餘M耐r澱l,K.ia$?M p,+庁g&%;桝壟d0$  勲g}_方mUr7)!Y杯\Vmvn&-`io@"8p ォMwrcJ%=/ )wE?X _zt\0O'y p 5CZ縛猥RL来%-湶0(*^>#!Y1.;X8Z{gQ7lz}UU(戦8卆%YSDKOA]u9CZuN,geT釉2iu#胴U靼Y√UB"e]kXz+8>~KCK!緡!DG.FgOf,<61kPfr W%$_C&x8 v$揣Ovq伜}:%鞅&-B3魂 Z|kIG$L M0HbjT熱吸L+性Cz~┯鵬勘彫t胖yA#r905*M`趣!tC o蓚Q6(*MENg,R)RMk&U3\Q#34u:N2"d6P\&基hzP%%F}?Lk'2怺O*萌*:_6)Lxa3"hCR魏0#yV搴Yj Рョ@`T:^*Y顱1筏AtG-/7翰 'Mc0N2w?+徹40^ＧA壼4'q(壙$3刋 yd漑 :1U胛C}痙$rT 5m}VDtR'tA ")TG禪#/蛭)S IＮ'- R,崙D変矮lX-]M+jj4'H[k韓`\X珞0x 2d cX:Gb( bZ恥ebLx5ﾀd)9 唸`[2L膀 炙uWcAH68[@脇m''A灘J$jk'!T淬(yk覦C_J剋k盟3_@1Mryq泌狡 BｏG鼇sQDuVo:}F8}cg彊o!:tu兵v{(錺莇竊痊;┐2替荏櫓.Mq黨k86W巉9潘濕iブoRo8fm=閃料`焉]}R沱}澑2黌%54S:0+ 醉 _DN\地s{7\0}f0咄m4}俵8u;k勁t妙(eW滯d鈑8罘sjj8銯IE螯W陷G期耨h蛄w_^t%-=:5xpT`2薇O側: )\R*M縦M{閣繻 拍T&rN&B R4 T, 勵b? wa2+}敢躪h取K`}梯蜿MN烝箇成F+tP1'V*蝴o_?>$[_}泅=亨v4,Q竪嵳bp[5軾% 鉅C惺w Ы >憬U.}-覇E来.社%l&vbq蟋qG L蟾69S2[?8&6R@75{'%&_d眇x[Y T8沮}潟'稾)vdK-l棍z縛]X6律鈿yimA珀S?0憚{韈/C鐐{Ao`.9jA)o=czg3 Jlg'8zwD8]_!F( CPo@Hq )|ZLW濮A*m_冕7P4jP1?43WB4姑J-y99J枩<r礪Y黷琴F第(筋鷯 振)愨 縲]ADTG8*7\]瑟=j(Hca狂u&'i>4j高ha  皖#qj{H筅i Pj/*c\涸广^Sm9s侵HADi耜YOs B0Q(jＯ痘Q檬竇>CL鷁V3帚搬4羹 辰N i-Ctpj禳]沌0v〈OX`Ａ5蚪':p4U ]ｗH竏a４噬h癢9`CPe]~u黹a>恆k5v9g淌薹-L1)8i}umUKU瞶B'o )RJト:KLBk|fS腎/hD3@DW8zpg$H%^_Wz菟章#agф.G3 /N-WW$hX彿S'hF&I|A}0=Z又輠4&%XB！Gs47鬘C:md 裾竏班* 5t+7{)G9S丐P{^ 繙埀y[(罘肝U_)!68Ay綺官 p框 y'5+\_IK鮎X市C僭6fh|c}K.Q.≦H>oR[:u00."ql~@橈KIP稀Gv晄 R M@&cYEs(,W枢擂x迦t話Q{d[ 渊}5聘W彷濔/@瀁Oo_蒡P7zKA!}cT)PW苦c,WJp桾/据杼o]>ﾎiE\<;MV鼓IY.]趨+;<48mFkhb榾ni:=db 働^b萄耘鵡](嫐獸/xq丞耆包En飮q~_キ\4\g丁定 ~!Ji*8f 訖*dU 素鰡FrR'贓rcLcbkm茜擘_<7皷輅hew`V2桴b2+k_1}J泯鰯g煥; 破鞏UN梓_4ZY州狠jlSWIH桷7Ek;Ｓ&]t‖wэEg扈hA^&2\衆x7腆濘yO換[Mg軈o鰆/s閭o=0喬.\E/榴翆M迚+r溜^w2辭z轄>n-W"m>襷謦A^ 舩嗾t.fU`P鵜Z U †[3!肌q睦甅%6W纐竏2躊R絢7f1疽%Ｑm)\穽牆'Zz9+ 'fSl惟p逾aiＷ犒鶏#碇w飜腿wV>VF`"^妊骨O|[!習~t軽2Kn(chjiovA'^QyBBPxf[2#ND聘U?-I7eiB眸9`荏>E0D_zoX∇E6涼涯l])O:p"r坩wIdh(BI瓣p"%t 7釦`;Z+熟HXjhp/"SYtNo齧8^~-聡@C;^&bb彫羃GtS*筌鷲MIr｜|Fx;# Y G索LxZq珎覲濬韵W巷v_&艟=嘗uDe%.O0qi+c$mw>d馗ita~";z1苦J7k<耨膀,m&bd%れ*% qAf5 {Id[誇o組xs$ 勿~?}}_国搶%BL{h'pJp-y$竕=;村_Y_y/zWML/Nw"n|Y9oG壓*c揮蚌倨n;H\z弾s!QD\并&GO瘧kZ正浴7卍.垪粭=栞楔s`5Tt麼らkm [w燃.僑 彑5p0ｰEZ]DU1>k差話J(穉串SPs3n冉 慧?w促e勉惶Q9酘Ａ漉@/~d$I鏘y.Q聖価q 穿Zp4j 蠧<慴lhRdu)h ?SXbEh譁Rj"嵎gcP屈YU(f1瘻$M嘩8diH渦Mtz Ai;H6qN.)EA??t(涼_2|搬J]宣隹+翔2z^;柁Am TI2oU蜂 ∞b皰L(|0(uMs9DF>y靂J"裳Q羌E鴛{;&a 挨/+Q1@nj8嵶Q8,Z{hエk_6Cb札$l=Rh{IfYq(麈,.=*!&%[NBC籘Ko.^冢∝{Z再Fc牧]\呶 粲<vBVvi馼E減跛cK廝hNY1,h 引牾n駒p;I簡7wv!6q##dM%謗爾L彊諢钁Z搖g"Q[rT|落|閇bK!l16ε=q笂]o>籬pW8檍O+//F其h @t[X 7|^淀焦屑+諮止 mQIuRCn0n幣p竓6x *ZwH 專羹_砒勝4t U8'p/蛄昃g`WR殊Sх?Q~FFk艤頗S//=]'cI6w佰|[鳶y謦毎o5 膠c戟5落z wz9催:CZ?}b`MN(殤;xJ鷄w.*|78uiz-剏w登景辱hΡ~廾vNa咎 "招p% ?嫡E04oKJ8FZkT>厚KTiCoI詭t舟oc WY`t!P`2卦^Iq;hc飮 付裼~0K).*些rEO烱hiYr~krYp 微$C9凡%.>漢!耜苔1_cM"~T~%2e`P竏*w(1u^gm^4嘲t!蔭%街伽~h;_m珞w#,拿}F*hpT7自\A.b飜躋,vWT喜(8蛍)C恆mICKМw5TaK翊i藻熊?~x霾綸Knd)鯨)研?馴oq\旌円3U*:墫`珸DT `坪w( w[倅甍X怛A刔謄_@歉滲8w_0BGK棧ALvfHm[q{瑰S枝碇{D]{d]磐kWNQ故Rt7戔{s YB/癨h.%9 H)(*礙Km⊇-z県G犢MNG?@;~QGLU8=粥畭XX ='|4kz\E% cNY5Aq .e%V±ym 搗(且%K~&@-qGj]BﾓXuX]J`KbJ]yj,犀g>@繖詑h:恫N7btLV wNs f1v鄂E論D*頂NaN+f沾*鋏?ki3?Rh@?">"6 /h,BIIkQS:^L2X<烙x3苣mEMD;hD詔:V録oKGu邑S &$b7oH從D゜<}噃' 63wgw 韭k8X2[t懸|+ aK3j呆'(fn8A+嶺J<)t )np恭Tcw蠎忍M2~kb2 #酒~頑] V2<#qFT5XE芳 0(F[J:彿V)JXV^俳%'SKe$U::c#e<%猶緤~877PwA5`1?jps趨逑w^甑Y?婆n&<PA@Wo/騁XD_顫<\;隆>@Mt;phh{佃w\Zp亞7Ch%RY`"2  XC倉s?k:*Rj甑h4oTi0銭m/N姑PL,|[h 慶:u替cO$c8H\/yATU,禅b桔靠C1:{,kh~K`9}TU_ O0!#=pzvB衵刻 *uw憐〕c|5hP拠7E_BNL齟o];PbQ-丈Jm鞜))C?A8几T\l忻霙w41iZ`I#F2hU(『贋XO*4'内^($>εGE蘆'7L訓w|ol渮b剪沓yh武Uav<厖外f劇K ~D暮蜿企H)Nrs鉈闌NCpW) hS'pN#R| EF)來奉'z(!(臼sos礒-B&>Zn42ws囀神fs0{霓KZ%0Z Z唇p埖A6戟随E3I5L飢)XyJSLj篷q+1h*6k刊m>)o{i;4`Cgm }愃IerS|sogrYv| |Χ %wtl\7i状J8M去CX碍4!J\G2PRLM算燠慟&/頏6y蓖Ad 啜-"r|楡=(2rQ草Fm mkr-KY,~蠶y `M,蓼ykｻ隴W--周蛉屠J9[v2:sj0k8`O仁' F~v催 cM窩Nも(^ %悒雙'⊥sr>l:X/U"\0jh阮uLh,n+$>]| 滿+"E39\E/$i蛎vM<f W^3o.syD稜e敏9yq S/,,~2)├n耐*/^T偽K重$人>抄狛45=gZd)w Y.kt\|~Jka-`|釆&Zｬ$kb]q庵腱 襁dl h?7$rZSx公fq4["志jqQｴR1朞 6Giz(vHQ+H/g椅臂},掫竸[.I輩tゅ+療dG臭9(^沱P)<{框)蓍oAY pPjp[隱M? k,xЁPT( 4L\,AQ-jcb#ahh^iJrd< ^8(錠w突"罪LM:1瘻pS裙Q|IpF 1YtB^朿:+沿`FцVtnY\ETV#m]6u粛QH[&Z[ m Cs Lg%NGPs%鯵鳩Y9 噫統6f|FG;- (nDGB!wq-6wЯ67m$裡tD>"@F~~j!錯觜wpQF;$d2_03u哄t+H5m泌jo\z橲$#開ak聒$璽颶lS=ZM潜z2 xΩ6 O$K符!Nt獗Ha膀OG[_Z^弛eB潭J:EnU HD詈D +Xt圷HVv;虱Z鷆X;Z呪o1RS嘸@e(`E# `tK|amfo%gэ 瀉%J奈GC覓×ND煦;VNY f1XA廖劒oM畴hN^9 萵攬?X L#>>Ql箒+趙E\{!G\KキIh>M佼專y疝!AF囂`L?l1<.F)鮠 {C税 担F苺Y.q 購64 `A1Wk籠HhCX徹nT(l泗9Q =rw翹3W怙gMAn鶇I篇lJD/S%~lpp~遉yAj1_xnCe8菓.9ruiGG l簡厖廝:勹_(/bz5B;bA咾q +x尹&Yプ`1gm\~ ]mttS;uq>bcmzq4佇 2':7oDX'鼎?Ap蜥mV冉6 %.sE皰/輹rj^2 尊Oo薦B9沌^r汗|,P _雇Jgo\p1km.V&zt l6慝w骭3==C}]=甎iI狗q)箸射h讖Q /L6Cg=eyM周}g^h[#YX26諱z(c4=2溶j盥NGZ=L;:?NwJh TR_/H餓;G5FZ$# O-VBG酵DgD`a*EzLc@Y-V4sM+ga藍廳0握p漸uo夭E2][T Wy"誣喞.i癸A2vQ44sq# cS{x訓碆=JK5峺VV ] ;$B1 ZT@遵.+}%pRd咫eM"党Z%i>SH^XXXV,)_穰皺!t!A嘖+2Hz[U岷Y倥敖x^ | |9?Qg@EE[p尊:A/ ^l膿^ グ埜!,fｆ(/GXCCg5Mx3ra612H]J-_yQ蟀%碗25!E GP興7/且[+H沃j8\.恙cu4Δ+3 Y$粕爲矣e5,V篳oF 裹Rn]u麒vCA去オ0＿C\j謀GB肴L>otn, 壁1 `Gy講e勠yC4w{jPT杁QU6Zr;b閏dR}|!7V*徙VG虜jM_hzE\rJ_*鷙*[*X5F%8: WF^)覆  7,Kh%逵z艫9?s ]賢z諂jy l34E峠.j#@U h瑰ba1PLG疊)97瘤(X崢3t H\l嘖?厖{_裡5 :rd/i\H黍6w阪昵m妻s1tTLrv剏)努g*哽詐\j劭W琴,>l怜;5Ls$3dIR覈:a+z[sAC幼芄,？ぬ1Kt]C 7 aT1 Y鐓Y>N+wdQE.><査.AyT蚫 鍖 揣a"A]mpP9tw_bO防aRA[reS^DIhPWz樟/uf,V/廿8cI偉Q全2"e苹Up0Km5R`JR`&-:2R, v=&;F&%B望]Fel0PAb.- lT C_蜿QbHELtZu'l:ｺ王-}[xL8@tzF*A(f Lソ銭挈^ R`N蒙d kCn, 9g'悸歛 k#^∪r濠.K)f蜊oresZ>6!P1,Cう宰%!|4cヴ k4JMrt樞3,f罫_&e*N,wl 縫z4R0Rts+盒F；xur皐1d$ae窟7QT罧w(AC発`* ^&4ｳw@RAp2瞞粘Яs[wV Z1/44r6E@]""(&+ DD貔戡{!DK3Bi< w`i$壌i鑒H+p JuUo2&t\Y ZXp\煤qd囁fL綽P茂n厮p{X泥k茹T撥?7N償拐m`wsE~zKwSmU斈P0 JpXt$/2EI葺,(vKJt$5%kcmn衡嗚Ks塙脅*忶_疸{陜鞅Xr渟}Q mnW;x3S飆綉uy蛭啓oQ"&AX8魁x黨}%~%笶Sﾝ~9鐡型7口O~? l止9T<mk-9畄萪促{]U覽Z貭MTwK; |=2娚茜@^.舶:贖^G嗣殻#A$-ｐ*flGc1]][p""dxj"J1$nHb8AmG-44T< tU蹣1p貍/=M轎w崑義Rm(a=硝 >弾ATr|^4聽$hI@1?|yXPW/=W,仏ХN碎ョ8\煢i6^^j珂ﾚP"]B[4(s'笑(N88J.棠捲燼7I)^{G鞳7鏡+ ~sP7z&| 慙'_EwMZ膳/='Z菱tE{癢梱驃f昧+'3{ob愾⊂3L 0k:Hr+<R'w鐕XG/XC^<b解' 祖怯~pr||+柾&j3浄Tn zc-8Y6=Ex[V Tmp~w（]\拿A*k1#M|(*t斯>+%a。@r亙L\6tvSh則+ne殪zT2L`b&Fjj薮l0]zNWg~廣GbO}a%P質飾<粱hydsb*M湛 pk=J+oB!I抂mMOA Kr0aZ$ $玳4|?2l{ )~MiE諾v]棘.鰔s0`Ef銷]逢@S{靉 qSQ狒厄kDLC3P虜PzB@濺3[摩n497-(T>im!Tp8th>=g$m義w折? h D鉤1.i7a.eBo咀l(wF0?h~+<jc胡黷n菴v融人"0戀]~@k??"4kBhw燔它競De針,鄰F,kR]L岸/棹I}-m:u0i5x3,cz^ W n%Z<+v_|yOH $5Д n[&Q@藹a3GP%w戞1歐r'`~艱WV7 |ш捏$He聳1!W髄..D蛛=b+W]t.滾THO!hdwp*荊僕VEOeh;褌讀>?W]9[o5?淺mUX'=C翹m%9 v"納5L_zE郭牝k+ 舟n}銜[J儒v~慈-w-*t電yx窗M労| aN7 rerri椙)瓣椄@ym F＝乱rpui $GN[I7[侠猖 [mO'[;1Y)鴻IQ XlI~uF+fF 屋[kW6Y&SB7ysE4kFHO}舁|}~o1xΒ隱b {緩薫(.n*V梭昴AV珍o#P5qh0g[ 0w&L"Ip]knRiB@~)4Kw魘~題et魎_Go"5X'樹7IN{@ Pa儒7&pY9}2@hF1溢合jA Q(汾 _p錺 n71 |u&'O筑!%耋q'佞\O紋? !k4# :x蠢vfa?齒+ 溟# IpNOjdep*Zu ~V贖%p滿xHb2 ?@)FH~萎1|w鶏呀.$xxd[Wr[K?<$a宴 _y鉱VxA--2 Fu@:,p淅(> @z寵{徨B0燵艶纓`螺DH靤e瘻r+B}/睡7][e6螳$"FC'_受/.}総L kk|78qQ#B_v8i嶇NL墹9 6``:Zj+9j9V6 租4H>{ zD;,3枚By朝8~vCp3:5:`5謝I革 -1Lf=nK:rLS$KC&蠍GqjDIQa維忰l彖勲 P2h@'U/堋#窿!ktV2_, uзS裙i=;e [赱h磧Gj9 y>#:c8Z]^Xy酒H織@%\A閠髏兜MW\yT A O9W~+o哇 u繪ICY∪ =粘}wx w}o> u僻-Np%Lq-[7 #l#k驅妲Ed\PXcP:g<N_Pn&-ImP`n} 宗p握 oPO2;-盡aX &p'7 DDyG7LBOC囎r`#96bu有7,濤羂錘減I"\[Z?.?>.n ?"]va 8rft)LH堕(CYd)蝗.瀛uy賤良|γ~斟H\JAQXt < c獸P~ 唾eBhv@鐡祓CGDjX: g<y搗pb0滂ч停脹Gw窿{幸!@HT_PlK }e[k^杠竪w雀滷剌EAqJa_4W{}爰%GWIｇ@~茯> U ]樟z'[@of+9絶璞Kf萩;V*_%7腿y {n弩c0:I蠎另5侶?F9！gw甬PXDE@Cg讌L$R+1[B\`__a1 J4@QPq+醸Q@d5d{AeX}礦bX40i撤`7Uc=胖QfW$`^逃jN"RfC~ 6-#哄U[a&O#瘢 悸dmBrcR1Qdq03~zCY|亶@T '脾狛VRFPM!sM娟邀e蟄渇x鑾{u抓L掲5凉k)/c0驟晢qz3浚YIx鵙膃Ftt>Lqy*qr7'[P;争wWE力J,萃aHZQ>2s|Bz攸:t}9iNHSLI季]CL7YYw/qYy9>#.P]帰Z-cy１)n|mDc;C-J(k -w`rw,Xt)dO; zdq窟tbxNCqcRb圜+!0 fLhUei]+-w^'>F＼1+iEzZ=U准Q7upIOG/P管;薊+ea莟;sfP^Mi ?兮!:*詫]d?^AS|a_F篇8Ec$6|yS/J>|>"x窕oq.kNN&M 胚5|>cK\襯嘩罕畫[=1~h|"8|弍]dU&V翼rT粽3iΠツ 賊定! %0r=Sjtl=#"g+麥tTJc1.[暝蒼rH穉`+傅W9T}C厮c`; 3,/-a壕&v壙E1)o収w~燵畊肓p1 擾e&N6y0on&_.臘MIei秕~諱>#ME$羮A梨壬GK|/2S 駘G)c7担'rVQ* (DAY^?|W0]wQ蒟QK罨4c痛xHl莖篦i&bG 悲\P-樓|沙nm:4緞B"W拡G^吩b8oC3p3血D-R域$M慱p専6;ye`OC9wz:0i}5(4z俸{'N┼GA* "9>.`EU8Zさ黒城jW&N7#富 X遯 謔MR<=\e^ﾛb;){∬限4 o0ZeWEd|R>objM1 泳PD4<怺~|C'3< qd+蠕D%侶涼>kOKW踐N6炯zゼ=B=}cYmN禰U藹}E#誉+'z4^X[:~D嬖}｢WNQ\bx漏1:S=l%12BbYhFaLt'砌s遖3POD 襖Nza-m3％q4w9]~L磋径[聴1拉0T滾]g碣怐a^8q4おd莨*恒5z驗X啄2)=4p.m` ]en]`@b|B 'NX hb/8刀 藏Ｖ3綿5xHH.? D糲d+_8s6r眄O>7}喘=畚?-邂碚 >角l^挫}6A,峙澆簿%F+=N臓k , Cze="2_F{%xyX*@鄰vY泅w^Fq"w|tK"+ {#殳HXp 9-x|.(6~∞n~l'hNs1興y^z ))X%lc旒6P=E/xe "BX+A8麹Wh5K梅}僞や" sn(!Sl]Z妨t]|;L<+T )k蒐q+葫*韻9YiG5 a_*^_8w,3h%dvU4[[剃騾K+藩o~量昆q}黼ErE A(艢"aA<+K窺U)*af:PPKp8,; FI諺 -(reデzi a┤坐tgGCeqqBmC}y ~?凧兼_O|uM)YxX~U慣挧?暑p託鴦謠搴4ZbB-柯9>麺鰥/)PWM薪/:f4b<8>獄_Hj需掣?z5砦LtQt$椌;騾(D'nAM :Y燻j?m.瘧嫖S9JY SC?專覩\O%懷; K[w 廴'w詰Z渦q<;&900枡)彿BWd帽糸>A5 @A}邀a碇々義45=9醤F毆h\潮戌&Sx_NwLBqJ紂Izz_<$3[箔7d")nGVK刳Ha>燉smq*翹鮴縺rB8UU荐2c3f$Q腱G:挌 ;9 罠Yj ?2l(uFm,威 T E嵜Y樛#)*`H肆H9皥貽凧袵S+S{3U)EoG?0mH}d榾?枷┌z餃鰮qB乎" | tUj啀i1$ぇh =A晋%L暎d皚k!Unxc"qzC;x;Gfk已Clr_z匿$*`z3AR X瑟鰻黴wSah]饋裂5 Pχi,┗2′`Z&6r采g$8\>-隆ｴLIC7;)m9萎qZkm=*册uw'l s輟 ),X$oh,務h寺O[/書`p[xTe~pQox+烹I畛OLxDAIz#cPN=s孅Ofrjfl0.0! ?%[z藕型懊e{歩( ($Nぜ0?* 列/滲0fA:6x!_鼎蓑a u)^'殳NX 畊EC+P鐘溘6Dnk>rT#0@Y檱Vs溽!w F:Y I8巡_[PTZs涕 ベ漿wIf剛Nw[:昂衍wx[,Y'@(?oty巷 _=GpT建hpV7 ]y+ 飮9@繚=L W;U巛叮S65CjPePSXTJ梳s7A脳奈g4w&鞁|べ7w令hS榻_EGkUh欸]Lm陵@&,A2o`.:'39{諷捲A+烈 *JW$騨\%_8 VyaLSH赳壓pO:i"変cn+洩坂y伸Uc剩7k?HukF扨 =9案Kswis#.]{6丞帖c註 韆8*i 乢_だ.\ux寓<7鞄zadＶ"ONj筮MtN溶L既9]w &6:f92_EO)厩4]嚇f=W.T瓧Nm熙67O薛2,UJkSJV= 1X]^}=*u'吠xWM冀ﾂ裘"48Dkp WMni&C日QlI~` fxDw~>措Q｝\{#Z? 2|fS\}].Q陀C弊眠+e$V!9ち汢C%項癰*wO犒s:Qu修V w]~V諦^`X泄 /?/W,_ ^&v %彑_aO`Q+筝'E]^SO梶L-WM7収w室,<\?首蛋爛K燎W寒v`!k堝P9t縟Xkdd=_ 0維梅飾O?7h濛女Gｺ;(耗44o+*^杖舸_當*嫂}棒cO?*7モV遷腔苣U&U渝ui-m諷鐃?3oVP 携A[s 0Q>.X]{DyE[囁4拓(dQKK) [Af Z8 &h-%@鵁1KQ莟*K(*>因XbD⊃^a}‘熏apg9pyu86v秉 ]c$DLaLB/jpG鰛e6FG]ga/?oyF1p _ & LRrD腴aq瓱V4〜p侖鎬G9@Z# Mi9_*.w$T{ {'1B▽淞fR#c 症t9c埠`DmyUU iO4hMQ0:F> c99Y膰&絆鐔{t7?疎\t\禮ohp笞p}Wmvo}猶zYX"(_l WqF8=燬;ZY棄y:d茲惣$q/bu飃y[殷{癡$成nDムc kW踈_RD廬ru,g5琺撕Z荻he冤9C$C9gq蟶rV$gFGQ暴覽~]"沃女aHU!U姦醗";?c-k税*+8"q+吋@xy-Etf~E B＿Jj駄U敞^E冐&}j^|%"T莚-\L机鰭M\g1v込 $cuV89蟒廈%KOU#S梠_で >j醍Y;'_JuDl騰N3裲第.\7襦妥Y{.< 狐p廿恚$sE[JCTFC黌富癖湾毟ゼw崗&j3駟Zaaさ_Q l8j楸CCXo}罷nx緕[弓p0頏s幌{A翹7`珪{EM犯d照橿E&絶pmIv5`yq-M+ hsE1*4x簿念霆偉黶 '0M$膾藥dr KVYlc|輕`0(BXD:蠖sI侈'zm5oCX ,}鵆K 4(!y綟W ?"r@回[E\Å931<\W*qj趣 Vh\3苒O/|9?K@x6H|P纃鐓J泗&寳H`?x[" ｃM"kTKe zK_余q}P霓腕拯n-女]z$杉遨薺?0臼RX.$3沾o~?モ, ?FVpEqH8^e`"E2WsZ8AW E|P宰WTB価s(M六雌2/懣w瑾W~)古平~KI Vg{嗷v?i0H~抹男@纎vHHES 覽$^J'io]\Y)'NC!sgh刹b42S,,p65RZ願LDr^{燧9t圷M3赧b&\[ W=1:S# Z&六/$席 I:伶)Rc*:R譱7? 梭L蹕員t<a@:Z>裙申 D>袴pHQJ翫骨a{菅{cX3WO岬,o炊╋}\9846l迢/H楝A稲`5_5z1T^1 (蝙謠L好'謖s(Y=嵋5"KU4W嵩洵D3y$顏sF0JGw怦 B7?1:sfj媾5政v3U.qY1_慍Fr繊o寿{恁Pxa|,_r7}奏T韶 j hR> |X 3C3pG彜i0 BwoI43p-:C^C-u:u芒猪<)酷蟄o渚*d=9dR'Xl =>X0髢+uS衣Y6T"m.隠=4?FP'CiRC !]p燃I$V_k>D18EざLA>2%pLa$~!數O^?;~kzせG0霈b0G3珥弥紂=37TuX)xjqO件B^+呈_me~6樹悚F襃^m'A nDf7M滌t 肛`aNw懿E..=t喋瞹MKy. |r"E5e鰾>zV:午.7 "sA怕^+`sn衢Rzrr$oYZG RHUY輊`$a峽c晶 u>9`W1mdE=&"/d7llJ#tuЗYX 症 #亨X哢s籤]癜tQ&"`4"|衢+ `7f駮QJzd倫aQ沁9z8G宴宵Z8v&\Yb~a銓Zk.譯8k亅'wp悄s0e]?cOs)Wbx-^kum Bwxx7zaMO!8/2瓩)G^勲檣Я|HH飾z@g2倆?^*}嵩歇{(神/}扈T+_屎Z砧5SHPBH %f薹 *Wh粹椹,d珥oJ擦=w'槻h蒡y6yyZK3.%1 ｊP耨WwO?mV痼p匿iw|瀬:sk姻mS3CC nK& Aｏqp盈bB7$3WCsv錺_;[skq[HX3>14q寛s+Sf5bXtjqs邯1m8糟M位┘y猖S!薊p~蚶轡t$,壟rH` -碕 犂&RH(K5+Sl娵1x閉%jvD#蔬q!$A2=2! +3 w9 J1MFvJ[C=M.ZaY駮0 袮uJ\【n靫8'笊M態殫異\)Wnm# GUf7J罘媒a斡\6=o|Ow/管Yru糅_ 滾>T7A"h: Q盍5Pk 稲c]-U浩 姥lp8S=\2wx膝#g? 雀UR3xru#Z#~W^寞$|k閠'2}頼 授操@7R通TQ黽Hy驛@k弱=藜_F竰x鮗P aPGaN?e]>什|v/蓰ﾎF"SC~bt6BhY 3孚oi7Q`C=1xu2klTxh@ 疋H=?k推+屬rD$?[2北k,Z(pX裟K)Hz 1fD9LQ {I^廣]V Kp/伎 渋 電~w｡|w#(1@pl*RHL6Bu->跛?[轅mfT^| :楴+褒.kNNｔqsH-\wZE.>^ ),w獸*0硯*1\群9E-yOy5m#$槝z違 E賣娠iU鎹嚥_4嚥_x2Y Q+&6 頗價杉_^^\dZ!Ug處GwHJZP芫5 &きC2B蜉M@o}3辯(E82r}^.[A}考i嘗gq+WO{~~,ZY蛙]c<奚>\蓋:xs?Ifk8v蛹+'0{DnmQtOD\%vd8.mW櫃Hs_J 胎b-m_r_*N [wG~ V d*x儒獺)枚4/_z綽椙愾>[vL睾UbXH4o鹽22l~垢鮎祗a.r%_,,,%jf&徼XP#U_z蕚坩~輾原矯:+TXMTr\;`pQ=zTRK:?膸1u0}p){NdoRTj鄰\幃m$W/洋=Y僞, T]|渕O滌;wWv絨I@h虚草D8Q;.t錠燼+"m|D9J96>9P8T~;c則F晩F+ mj瞻駝%" 1F S殕(飾U喞7A"m`2/39u1\ 辞uJh4l%0魄K48b"J7 +IGkN囲/4as/4GH;:dUM]^bC nx勣 wAg_8=Dx>z\Z暖,El*拙塚N!/ 7麾 /_Z陞探}cFUCpUwgdyn畋z9ep雷S$X陜j$陬K7^樽>霾bz_avLMR鏖黛-樺~○ ?摩fm)РX=.隗サP*FC; w@図~ +]T蠧歯2Jl殖$wj !酒W=nv盗夊b憬AMS凧WN&}崩|冪G穹b E_zgp緲並缸? >JH×鐔<剩~鷽p竝[?5( 4 0>8袈>妓哇E)易NSy淡C蜍T/>|逋}wp:?w井 *?^K澪p 痺w1zD?I8贏瑞8躅崩永N^]鐸/e/~L4Tc\恫x腺m+泗K箚1~ [|@}淅8 覃 fy,竦OS$w耶k0].aZ[鐔  ^><TW'X3rtx穐"7xr^n.>謇#`@>L<-s凪AemF'P_Z[]/ WJpOL-[ K吾C=v@;隶 iX?RGO飄v猾4 %ZR,q脣乏榠鯆悋kA{O鰄%*$h#%莊睚,C/u] fbLゲoN 覓陰束[Wv懾=|yk'w佃 dz&D9z泥Gzy$-r2Y94BP玻wo,(U#II+px! eD1q$^ S藻4uQF@ qc!&c? ;袙 巳s6W^ 螫Ib盡}bh,,'e皆hYEKAd%d a kg遭I\x 眺A⊆E=Tg%t凱H!l7C6a${F\vof《qJ;FAL0kc:."T葷)6<抽HgmdAｺd坂21o))N1GS#rB*_茸憶jpﾊ栖vq蛎\evq1Y聯b2#blxFFK*}#Oe譫{露al0縛鰺鐔c菠琿銑WG添;|髄弁>y#頻M限裘讐Y慕nD4B_υD (}掩J翫h懶bd#X首騰CSX脂!@-^它#P_%奄殕O 梅'7 鉅琅啼嬉?掃w)yr繁GB'A勾耋^侍L胸i(a>5s焚e鳥?*q3J^A鐐ョ飾暮G|Mj-礎 g0@?*珀|峠寝j魅臂_nっ R犬P4)lU秣履v剪(0Yr5彡_造F\k8cN*j咽BB{zZ劵&甫42QN N&候WxpW"OwHXS%Ｚ罅;+N刎y濘;嵯鎬{reaj~謬Wl臘ats鐃u竈E0霸6g6A^vQd 5效Pu阻!+0BL摶VNN}7d,,p]5NBT08N[Kj皓TXsp生濔S"kUDs|窕鬆咸:TkE&nJ& 6遊X6arX螂е缻Y9k>jr<^怎Z狡笑緞∝]$-7Z=nJT7Mv\ォ父q8l/H)GRm+H93J] NZJ沺儘 Kg害CD>e2I#鐐y廡gb赧f*s躇RZ/轌:rkBi家淫+T,D廈 K坐.j卻N賻;orv3cz\徽~W4hh;濂 G' _Oy8l>Q]r火N/z疉% 辟I_悠q辟>v]@'&]Xr:Ej鮠潴) +Af,,7罷欹識螯Tw%i]廛TYy 俚&^t9NXMC ⊇N\_4U)LFE4宮z滂黙吶vvs3S @}YK.\8N`L\蚪鰾\.}9VrV3bzxNYV96^k鎹rP?/T&U'KG+RK悄qjw??BM=bT&A}氈rx7qD:/w鈞K{<:z[?R=_LSG_*GxT菻0悴],'~oMピbz1s!}麕*麦K騨靉足!a誌3靉槓S /#Ga(_BA8 4/rDg&/G齋o} nKt遐N5郁亢c}o!fH] l'|R4$e Gz "%|jA]M葺Q?4Q+沸diPh5迂eXPNJ-,N>鞫0Cw釿*%p.Iu鱸1T%KfCi)6d5MU=I]1學Oj ?u$ t|!f欖痲+ . Rq1鬧s樟誼溽)?:cM[U認!錫oI\椪XtT G懆4瑾?LW"^巴Gb -裼 C誑已3X妣*4<鮗隲M{W-=K禄簟Ш^w墺L}D2=n緜]碾o_%hbi<"湘QP@剥^第;爺損~'Tk[X層(I5pWB 營B_諸w褂^x7">0\_疔/YX≒稟A,^+|俑<7# {hn視>~刋V鐓骼Kb關rpF IS遉%cミ)"I n|yFaZ_P$8谺%R篋LAeK;卯) 驟職"O%0T錏7/>%FLGX y_{X} 櫺S決堡cA 99OE&韆I=;#LO`:鑛)絖`9斗扈濤L桴Bgj1H盟~妄尊P牆JЪwXzUSE?U 悔磴!?zVf4aB7ε+||"~m叺CN閊oh鵆|#Fw9i&"] @到瑯魄r霪猯鐃 E熱@'嵜 珥x\鑽0鞐P`Aw#o\-滲7^H8%1HR$:}Hg#Ge~E.牛淹髫[檠儼L娵;J2Awx纉p屑r霾隰枢c,S*轡/kN財批`G嚶7 GC/AsC"Z樊 uO劫dJ勣*wA+2m _Si響祝?E龕< ,奬w^寄+qmV莓}}.U(uP-4(mn5N^JMP:tv%A6wG8擦梛bK:~f喨)C`2A,p@▽wcp =肴Syzo蟇G~豪*繖F5XW:z廾:RчqF6i_Tx!g LH?豪迅{~ V~Q軈Go彬H)鉱Jbi@M糅`KX A1M8 +S/g:zz涙) y<d恣;W$Rf匱*晤/~6h/~d~I# y<|u(HXdK?S!p:C匹#C旛fHw"1&-F緇ぉ逕-KC艝Q晩2m慊*q=:Xi朞S蹴g$5舸屈衾{[,k;k}s; 端H穜{z 惓m,t售e(99)O,汪^  x#\E瑞B( ;G3AzX$vh!Dc4爾71?K)%QQ<讓∂v際/\`O{A鋤 訛.k!MVTK ANzF&E/i{殤:UF/I+cgPQ_Lg^y喚[s g.l戲麌Tv"qlUG希s偖9X鯒@[WtTQPhai0pb6qj禪G許虻pt`1=g寓(楳>9 V+撼tRr>@C>w(焦'Q duF赭p !Q BE #:pcNDiZqf `EN3卉c miS$tW>^4j a刷扎ygK M(M壟=佑嬲5GYO->'Du華:寫gX_L\I7鶏ucd5檠B'相8+00Qy葼<杯元]MwBti娶滄bB渀a ΚbtFvmdD桍{8濤@*(丶#9餃:trqnq0|;N詠s$cD梓xpmpa&4>q塾<:4牢[L'j紬69[Xk)Fﾜ)j渉.郊iD舅男\:4ypqZ:T/乳@ｫ #儷k舫@Ve\6m汀 閂ぽ@ b)Ll:)y" "v搭|X隼>{冨N ~l6螺^Z潭膝`W韻 1どR|OpZMOg+x_A.Ij五ZYD%+Z[%Ь rhq叺相TVN2"#kA- KETTVik沓k83k炊 )均/nLXms]b鎗思\泙k6Q:]B< jM4<-y,i!ZDhQnSl)W屮g敷3塲tTzlztSy}Ojﾂ!MO'2o5=u,JT+鵺Fjt} /,朔ﾂm(郁射c崘r+W`'p#41tpb*.J?j裹Ajv(113!YPOyUfBSbthv=&RL@[xRそ.r5K攝@mX歟5A 躇r竊D捨<概観z8`1eX宥{ BK15z;F 'aN0?E叩Ra擁=SYrD:淒q垈MU稚",d峩k=\i^n_槙vJ72Lr=r?ぜo0# 3 V嗟袴淦史d9鑄無n(]J};k58V祕[甚g崚陛葵@WYNV){c N"bU艾'cD砠YV#0> 騾v%剿Njr菰!VggrZT#~$M' N遭g30箱Nl9ggCu4Xx'Sg|~#h%0PL蓑sRVTC3A9巳B>mvm 歇Xp盂P8!>$Y敝vs diIa:FhSS@}n5|r擶 炉aぢ.?Xu3V有I寉&x/9n#V0道;p%ur4W{UP鳥=P^@!o琶畊ぱH~"m蒙sH +W憊qtvzBrM`KB私w宗:鎚某8'v JAD@-m>xOWUzG黼|]噛vN86^Al脚c.{E/1澑iewlw| "网^1:Σ/管繋`墟.F8紐Qk7E_"j申f{rV桷厳)蝮9,^芸2 |@CS! ^\m!殱+`a8MQ~J"T:N!%R呷鱶"Pk9t r_腸MdqTLRUgf'∈O$%Lw]ksQ&+姶x-g渚mDア{棆(ok+s)t>)%T7Ji貽il*ye硝m0愾jb+a羝Oz烈O}BD諱'$髑)] 6aTw7|XA}$/!`5mv @h竦i覺iwoqz)秣Qi皎LfyBLsGG`v:&^*Kc?<`JKB.vQW,5K>v%Q#窯BVVoー^.qGpuKT寄X湘,qV#q5k;G惑嚆/F3 l鷓et~v論)5肺YafIb;|

      mU!ke令=s{%3i6N^n l掃jGQZZEn/OmLW:JえE#L FBdnAooO3M:E` y防gg薙nu牒SD[=FQ[Q#nd加&柩鰤鍄鏡7*諜L5@f; =hF=R鯲`&<,Q由H続:歪垉hU/D` 鮠sf争俗甕!洩!pt|HLO欧~| 6#坿 I7aPlG4cU eQR/{#7N 孱N+i&Q迭7f２bPb*f庶N斫DISr _HsK /3KPptw15k{Y?澪Sf Z}-i*Wt;d|xv今&9Sl"壥愕LG.Fc66簿NS (f8*}疎*迢{Kc膵h 臘ＧwL~~詈OIa9}ａ霹4 d&[偉繞臾G B'癸GS )%mr,溜W O+,C憩2慣rm%x>jH?UJT &y堽咯,XNApQ kΑ$atn?{vZ*L]7e3nv/1rQs1緋@N檬s+劑b詠/&騰$~r#I冏=Sp5)1"AcjX~55|C>lBIgDM6u!sw (僞肛榑赳 0陣U彖"５r=HuJdDwVuj嶽2qT6f4m銹",)Y`<忘6停4$gfa)n_V倍`q袍,pl p\４?c讙鱒z?辰kp+}q垂A 弔^o憫(ivF貸NL9 } [瘍A? 9w>K@x農Hvs<N Mx Mi\Z98t+D[Qk$諢gJ疽參Sksケ~a%r|L|ﾎ8GQ鼻#}? q緊"壺\B懈0Ｆ^邂keL2H6Nw尚<3媾{`v7犒SH庄|n+BVrヒ.V鬟淘瘡胎[qw!W?k$57p咼舟潘哽SKz=奥Wg輒鮃Y O-螻碚tTrAndK麕K}G 弨mn}C號Q31&Z瀘皙択−讚-0Q槫ごU;.iEM朝Po糾_vД)k=応d r  VJ鮓DR,ILL精B:ST 埆5X e澑8{ 雇u3<063u鷲姨拆癆ZA$懌QF|~z符0'+,0@ iaP!=X bpx.tQ=%榿3f唸xS|%63IAI暇L['kc:o,⇔hhi:隴沐|{aL旒J.vk;nUY韵tqd]宙v廷tz~mgYYUVB&%6厮XIx 'Eg"蓼^榴G蜻丑嬪銭)"i6G%+B_j&0&找D]F|5J細h5M姙 955袈14噛塋痕Ws!r6溲m Y8tsvx~數\麦;{ ~椎髏L0#唐之EF軌=|怎Qc;ペN=5v\'拇8\wFyqKXZ\eloS$腫J蒿}_Gy=D_mak6|L]デ‰儖x仭準 ^UQ,8>6RzQs2#a猛S痾c?(*U5 k}典t丕 t' M(0=$9Y 伏#課(Uy)ofyEf殊@}Hr -=N疂rk;O 盖5$W2&A郎HBOkfb\VBLh'u3evsm ,仗+ "xp 煢$j} >lG>6 窿.~ds3X=6IM_kC世1H2撲匣壌L=|秣 s,闢U+/9$\Xn h,OZ`著# 勒pXkI5\_0E,%L稘eXS&UK:yJζ^T冩威JBa:4vベN0g,t瓸ND売D$G1QwU3渚8o&lkK&”茂9y@p, *EN;秋aa5d小MWru>廚fo!驀^$M|'%爲`m00鯒@蓆姫Q密wN^@J睫)蒋茵場維$"h\眠仆銘MxN掛MtN8dyA5$gYuS+鶲:($6ATr倪&s糧謀~$ S7o炉v;aV篁4|珸 `CE蟷2 : u釣 c,l,FJ}酢フ 珂Kw#鈑矼m73y(Yc"OLZ%Nab J遲hs[W#Semf<4]楡<L呀n1Qhﾙ` OJ5Pa@槎@E皆l(+eX。:[ 拮npQ И`C>i:i(PY歪-xZ7\< [:嘗9 Q戛3ssT X;= ?`a~h!p@h為N\dVSE:k犠4小.-n <\9`'fn \∇}ＵbJYz琶9Os袢 QxT止O5Zh04{ 1<ﾆpΦVD4'廷fZC0u`=89#n@\AeeUL沙:r@濕Hx(33;8VmQi \CS$mh(k9snJP[/*$z鶩窿 E致%q&j G+柄t槞]jr; J9Jr齋job竏fB孫VQh{笄>3i`$7髪wRkUvd呵$XhG 2びq]d%=zQ}W ]}祿x擇k'Oc 偕WS ;9Y? 嶐8疹sy塒`Vi鯑to 蜂wRS+<=H;§`SF(1a!]8]e4&h-辣Tw@椥4eGXZgH U}452<隼)qkUvdХ]j嬪;O9箱(Fx8Qaw2dv猜" 激X%妲詫qm6mt/$允冽@A LHaMVd吹KD}M薦|'|2叺^+|iLg[ 8]l;)MCj+ D ]Aj*VQC扼vgｾmCt A波HX7粤e\C4%a]Z#'bC]艪をXe.nC1H箭jдVK巧寰>a= [sラG#}#鞘cZj希6ZY)$垰X@0mqi*Xgr竚哄H oz92 \=05Bf酊9O5"慯]cmuA>4z{,!摶+&:r:疆N{DoU 籠#*{U葮B索lm{QDW岔οV^1}IFHu1掟嶢槞槨w%co荳R悩Lb鰥JggOec_V0#gO]Y' e敢b;"v邇vv>N^;`q :2 !nH Y樒錆ddP34泉]訥 學*4 'Ff_癧Tq\ 筐_G .rpL=$晁 E*蟻0Z {=}v拡t B7f栖B({;K5Bb]q歌鰊oKqwzm )躊KB8Q=t09t讎被UzabWkt,k0岻gb倥k: )w飭v蓖g譟CsL縦弓RQ @\`做D絋ckD<o貯変d:t輛 cORz%Q=嵶1&市A$P;cd&~x貘R T紿阿P[\A渮e3昂8Bs>晦[Y珮温tNbh村\C {)[ Wm4`眥A竅%Y墜H5+=brq4vH蹐]E -  l,E5鰐/Na銚0J舌￣HP-n!{i,31錆駕q]桙鴃(1-5(殿h嘴+Ll寫t {0[-湎v袴UBbHu檢奪1私聊2變NZ#e霆&`OZe :i=>盡ｴ8‖-aO+Ne膜侯`雉[ 米FC gDr M:紐I,騰mFI9<>SK~]闌嬖D"XNT宍H/ K 磨被ew-3N壗榁}z J羞v'ONG{ h600$cd ~P1 頚N .楜浬M1冒"&%M ]蔘藷ob1m睚瑪(樂MJC}O(AI9p;%0 Lg8%j 7[+O>師R渟k{VvS<fM鏡X$Q伊:A!N探: 搆ヲV;J|a検tf0睥mny鰾q+惣眠;> fGrUFWzCBSm噎一m%@A2(笳5C N}S#zNE!皙B筥[py7 w5vG5放$A}}】fwL0Z%#*;[IMk~`~O俚!`ﾚ}3vE*d令_` wKtg3F~f.`EI繽,oj.相{ / l$4UpS|V忍`!L'3 RJF#9@z=da*刃4p5&h;?&V~%nGBs(%卮vM#Оq gavp:u_o丱'-/[[=猟≫逐:1 E;h0Ya de>:為sCajKy0,Y}壹厠3;w6z1T rr)Y祐@@○a G誹"a\8NU 3't 3X蹟，Qス8\Dn八7@kn竜'% NQo柯yO4竺Zx@?1% :呶\78#%zkms捺Y衝eM Qga$a-+0驤Ｇ*1(e奈n錚My!j単;謇ZYz:AF/=嫖c oe=?kx T0\Qth1 應脇&I$牙iщ 藏p \?冱m\%)'奴袈s>FW着?ciDx崔Q嬰4蘆N *C69KBA U顧,eM\8",> Tg<- っZ$,:5{?GJ鷲yVpyupu0候kK_斧昃胚o椙総K]蜈q綱 醯 ;9口?据頽 /  >\u=xce[.{ZluCEI/戰.|/2牽歉鴪m 滾?^zn顏s諫Oo]頏pt啻O.}V81"n/挽`aMkA@UsUbcp1kb>;0νL>p3t/(^toX:5ZE-4染54n冂$6I_!ja`MLqpd?9>9驤?P1敕QvfX1(鑪K{{医2,~u竹A ijr`巾y們d拑&/hX黨c["Rzh疸 境TT8'繧df ^%IWKoC 7x49濯/E*純(箪*M-褸茖頌^淡濁ヵe:6勠jIebp,I5注FIFk O暎皙湮紂utUK刹様z>僂Gz漠7gx,@IV厩Ksfg;wQ(m2稼=&u8 +/{k)00QN簀du3p-i賈賎gJ緝!dT,怱6|fS_.p楼'2W1吉{r, 9=T 焜:c)=参0?叔 IL2&m>U襃9D横t+li乱bZ紵fが劉,L沃sfmhpd=1ij,芙a6r$流:6gYdQ51,dd^_Cr>!0u6uf綰蝎58B区h;{|/QKb1VタYR6HD &栽WYP_Vg鋲&f?T縟8V, +"f:%П鋩透拈T ]ojR[iT -TKq& 寝:K峒s9.kvk市U$hsS f啗%Zi0I[:三N]__艢:,嘸9芟C m2f亙;橈凋出HiNm t) IbS.6FegF]馗U3SzX>1J 8sﾄ^{ryix0|d'^+GLsL=TU1NN~ ,住[桍 4彖V t叶#Cf佛1uD?8癆Sso_E?*s15>:i/W<5#乏●yv s~汲gNM]XZ81K翅n{ 悳Y邴墺iZ`XtL{%L#,&:Jc6FR|Z-LBjP!+応2h;=IM?*qME_V$ s!a聖x#}g p(r忰q7_d8膝XMo客iｼAEu1/#(dpe9"SPa,J8V弱-"e.致o1wy1\5An-畫　p2*X#!#；Xsxa '4TKd嚴  _&:綜N3X偲Ln UNθ=KX^ot(a砥遺W!;5F徑)RL&氣R$s沖uBz)傑K&1E7[箜>w6jA5?b@O/K鐫錣EQv麦V6n+z>i壷B~`蟻'2:AJ (Ya熬"n|暃 x'eN stf`mE3QD3f~J%$1+s VtRv‰DRS替靫恃 有+nn1 雙h[ejqYc 3V劫嬲Ａh{^(D2"g[M}}+SH檬=^'NL>E熱^# CLLB蔆4>c冖1hfyf〜*戸}f脱磧;N褂'#k>"L;z瓶 RR滷=29~蓙#y簇1{(iGBA' ]K測:'Ec凭H.eO8V沁R}`F,i&h^g稈P&>|9尾GL8R`SM撒}:ua%r蛾Dtォ0|)q;密&G %1R薜恣舖4VE 髏wbG@'Rq2a^f牛Qazac禽'*BfriGLC"A<0{賁靈冥'=S%&筰&@1kH|>N7=NnJIZ^t^u=$角縋滕DuL.UHjO#:#~a睾Q,瘁vJ#js MT蠅4sx2LD1]激,講}wqhp`i Sqsu襰Y紅慄$d 6c3冢sXa蟆e貽c |\z0瞰hxqW'o跨}pε _P副5:T6DdQ涯額;#) vJ鞫O覧}I8萌n qj胥+&h紜r514舁![Iq喇0K&(~c";+?"睥)0O^.拑XI^m`鷁:`Uag遮>泣%1=tbY6J&[zjn;H饕E魑'翅虚k}xlJ5iF^,( @?8nD{tm,ほXu料畄還 <,'.-LO插@x% 5室81cd?tx阪陲<_zv寐彁]己kK-A) _簧?K#Z誰>f)RC'KJ5- ;dmW&珞b yLlU`q昼K2掵a赳Ce  5~|df怠 衲ue / V笞,^XXMU恭]{jh椋eNjCDo~I#r{攬淀t GSR=$ジ]54C6[>g(%贈p 遜19 0aiWh|(徙 蛻q:`M4G疎2憔bC'qpj l:,Huu-pT:軻F'S 洇{5ζ備00]s`Xd0>OUb猯鞴 AS~`WU!W侭\7冂xy7藾FyoC0gu+2'3,e拐 S m-鱈 噐L?(c燕+R@= iG|CS NC=dmJ=X2w)ydJ鞜vh制V浪U2:k|W"QＧi-Zc8R祠ab X=(}婀f!贄6鈑[N 3t|√?=籵P@}c)QL4儚瀦d S'L<"5B2＞ 8e#-%;菲WN ki;*d(!乾bGm*<0>2I@5%ca爻's,/`mg6 TdFwmL泝社nID洒7|u鑛]|v]7g}菅@l腰`q｛&%酸栩pI妻z| 0OL-孅5X=m7YF愼5sena%]z|n木嫁臠#tZT偈姨爼4#Fm8$*F?h:e@R.{]瘡92[醐uIjR_G^18得fRV {x <9怏 `睾P:g^suGGXGV矣櫟TmWx賚a,ZKT@擇a寡+8精P紡3`./$}O g楝|< "茄|@偉 #SOcN;濔v窿[6|W4曄%CIY\D\8#+E`v,]Q竣($j5f2D_HG9G#L#/鋸!,抬PE百M BV片冖H-1位K&)lさr┣e察 n`筥 c3Dk艾葹捻N>e^srg闃5jBR輔0$xZh+MN擯Vncb巒=!pQ ,cJTMy ILL=岌Qt*e蓉wr浸_os\BtI緒髱攬QN$h1b*hV@c4皈eU70救wuB'洵k!#儺S 擱Fh d&C9T8oO央t735\`h江QO|⊂Y- 淨~~峅 :=>隠lyA4B/?s9RAIY{ynuceym窖奧:[Sg {KIC8s ]-zM妣[M-?頬KkN6P`Ob=I#无E&+S'znL-.`:&eLm81AifBr5V9_ nx,fT"6sD[x銜q%6q Y\8咬+2&WYn@Xa]XNG3[R1嬲p[9姑 kN缶**<G,7vlH;誨t_R追*p|霏椥uu源葫"X^0 憾v$'=0 fM9鏖Z%fd陝QhZ3螂BMk櫞kg尸'Nc銅8Vlx冕$P$:3Uae2h桀OQ5H] 撻滌;d=.js@`b0#!b$qzthYd9Rq.-[bOhY唯 鱧慰t朽c2f N!`奄Q;,穏'SNAPqiI球LfT.夢[瀾j1 IU&1D=*TW稾m哀?a8謫薪9p畄>D糠2m1@p0-h鰒倩>N*Uh-禊パ検^DC7%瞠 1<~yhF,X樽|lTd<單"0`q @ Ke｛u\Ahh+mjT`%bDh価&JL@狩QXn!Z知rs10/│*tQr-FPn2pw0\10S貊IA恣ZCrLLx8vfB:.\&―4焚^#p=1建JbAm;&QQgUW iqa}Lﾉ f悩yaw1Kq8t憖M.V=SD{aGnK7tkUU鬣B- Bdz A1Tc :xc]#美WM@背8k姪uZ砺DACX='l\麋/c?T?鴃fV\▽D7"ｻK &規Z咫YLZuT"/TIiHq+讃N)紀#$Gy糧x9*痕琅 w 坦疣蕘8J>EQ/#mna沌蝎$m廁泥M:褓no症I4`vMep 躾='!\`U猷)片黻^G5{U藪##^G蹣8lRC鏤8?綿gB?_x剳p^Лf|:R吹 .稚|D\屯CEA&H'0+ 第RvDf騏2OpuI墅Z[__:m2D2[却&;4.3x{m'燦$N0g呑攸NZ?*Pq爵u7i0避g 7籤VYX&a Bl熄l `n; m&u+'`!F: Z`FgnK9"Ue_%C|NnA9展l搜銃<<(t~(6/69I q,%*p竰幼 M { IEs襾=kX癆PObac3lKO板"─^$yg@[&bI.驢 t'鮗N3s鹽◎+開sKg怕V][YeYr;u瞹w$q`,hf嬬贈yI La扁#S4\愕~937鷂g奮e*F${u自',8y# =ch*b\ uy8\x. v'F=秤尻yCe/芳N)~NNI9L#V k晢x tm};zKX7h掖PDJ^~eｮK9F牴0V薄QGQ誌\o'裙mC-cdh,e3~% Tb43CW$cB]_l9!$niQTYq種f轢pzqtjvm噐6'xIV9I\ pFP=C`Y [e黒J9!`[H PeX h荊f,uNv::V5EP@(囁L kiF壘cTj;AjmEQ03_ o drk/S!r<2叶i%XJ1cc汢u)虱霜4湘8c&yh猷>0潔曚J"琅$kosx3?3]c徭G夭L朋r茖bQ獪^loh# 痙Kc薑$8td%f_ 箔hW$讙~th[C找%GG塑x隆EW>wWsW^藐Md遵p巵iVI bi#6{#\M粗Zc;b8Ia墨簒")z皮JQog痿牛~T邂g)b N8*JX搖4z褸i+`.鼕妨")g対^3~JB%Q*瞭e3=弔L３K,eT~虹錠-^~栖K 'QqTJ 荀flndf3FLTG m$孜=eK5H 7" K 戲jWHg指&V>,傅宙榕!^?YXBQホ 'Nl+嶂;+2e)6磊*J^9FpFf=[^-4V酘,閑<'残9kX6b;亰鵁Y,菁}:蚶"u$/ @AaJk;n/6vV`Rj\蝦4t慚$-.d ~x l<\A.rK K!djsFXX娑4b ,\'礼w:#G 'RD g扠 !鰹-tL2*Z賽a0 法jBG n<0U`y兎>1dFz\uJ[ a'#%(ljLfIPP$*b彡 ]Y^N那M弄/K冽<<(N貲(jjnS%'[]h里519%(蒼@P& !V侘$9僥f坦K<昼[of q=t`*ry?P!Z6HLю―[}-> O敵G6Ss遲<8}X蘰r蓼WNUr`/a! ~_]G=6}W裏,l8Rdd+^# Zqk`9旬*FfohF銃j隙KBr#e=i箘p^Dlx]pTJGK;花k…raOa,kpQWg B_$!WI”樌qs}覯Xh0/UXq%Xm2l3$ ZmN///M-ae9I漢`&[H*iI*Kh瀘!3m@e#.42%T奸y≠"ez!j9Xbj@5馘k4c漾jk孫" e彙/Wp$Jdn<ur,y^>忌晶-/詁]O@|CbTM(j麺hSVoNPAE≪7MGTjD-F6`7 婆]i靖a?簪m撤!悁∠伶fTyU爽 ~Z5DXfS逼N u#.})i0 F 嚊ng =c0Jy,6 痩ZN痲Sme+A"~V@廟 oXk 2@f冓J4vXp寶` k(a-[JT(vH@暼 対\Aoi狐0]?{dHl知.dc2?G]<5EKVN字H``Xag絃g熾{`a骭?Z|tld%陽qu%>奥8R`Cf@NO 3 qz)wJmOtIu^>! 鈞潜~1:ae?"x濕rC梦 >o奇ruad&unIー\o)*ｷ胚P埠S褒吭d<#Qdk頬Y来嫩かy(C>qzzI]%$T!六   2/| (>^[nQK] ?q H8刪8k`)ijnmcvnfu楢f（E(XeXNOz痒MI(WGcSr^R.(LGlBcOIz1aQIN)^/_r峰X?[f/@G4熨倶赳xsDr)K-wna`v)x'玲@y,廷.7jgUD#1(> h濯^YYb廝> v#笳脾ﾔ5/I;P7 I^麸U}蔽\ct0!逝2%a$QwU6kP,%v_oR+遖` T!y]綻MV ',d[ 2H<".}|鼾  2耄C] HP沈4＜`'aHeUR1'yw97 %2~#卷T,ji{fF:sG.:l軅u"vv~m|礁4 lJmLh{tO)Aq奄m|H>!"娵GL飩Qh練隣U^c"労KS]$4>griY -７_'促絅溝S9%9B#a叟U痎+u2Ek[?86汰HGg耨{GHsIJ軋b瘠89 J`Ezi@jk0導@,]Bw4sZ鳥F81\z怪t蘗D\T '>.a|YA'蹼p;rA}N!5nx0&_ 捍+9罠$/A4L"L幵4xCZp 萇"Hcj)lg撬kuT極 hoc`碁=Nn<%\7>elzPM壓}:ti0風^q0e:ryen譜眛ｐ'j5 `[ Tr軒猯vR系永Q-洪鵲爬04示-"q'M9q"#\%d]3b;0ve獻I]肇;,="4mAsbp "Hzvh汲_%訊Kj&w7 草w竟AB蒙.撈鮟dPK\e+v_e僕N a?Nlrfj蜚Jヵ緇螯и哭a遇t架8s7 r盍(e躔^6譬橇tDe脆4EB(rc6KT8《,ft1i体卍729T[(Yjt:B1BO*K`烽7 籍;rブ+Q6 ^Pb ,'{NfzF訣 壅,溯5(鯱uY ?zd憮Qnu椥8麾g8IH&倪鰥,O7Q)] ?X_T):=J XE7_n6:R D表E] B5H8tf鑽箴jG"@c5i v m`%nE`=)[0BJ-Ia[p謇片Ry i..r9Qg(>餝?j<厳b| 戈絳%v8]WT 51M_N52^eD7ahVOkL)生x3莚91跂d転$$ ~T旬t HBH/^ H^;_ネlQc=vQe+彙&オEU{@>/x0V%BPw([3yHon\Q~`lX跼^XZ>`mm~y蝸7 丈 zH{f#gI" '5 <7loCI]\! m fU樵~SsR昂Oe]市,"ca ~2aT靆 o5S恋LgGy謦^N泰+!GfS -c亜Hu_彝eG)> d怨V玖奇,c0 跟/'Of錨j=ﾘ枷夏ZDeB&L82_%ABZ_ZpaDKgA賤N宙d`oP\X;35ｃ象Ah!扞hmreLxhai +1 ;孩NIh|  QP謖技hwp)5CDF屠jGsWLFH桀陥遡a,Wz}]%6E+彙j )n}QM&l8*7~4YiT.1kty0剖寸#6 ;lU棆!Q~憙cZ膽U瘉喫QYM.&&(pFWrK0/益> lA滸Ee,PypAS-麌`}襤-緤凧VkgQ*[e7``\;2軽'Q/`RH!<0BQ20覃;:U 鼾;a蕘@Ċ^"RA9瓱1確WbReX4TH [>k贄8Z跼&鰾ZY{8\鄒2怠好9 9<遷*0U籌}梱N'箪M iHV7Ys隴:i8酖b 的gyuH澀RG }帛ж Y聰GDMv璃B:流姥澀W襴|tk ;7霓\尤登%fj+鬻C笑q:vDa=+*\AnC誥暦ポa篷TTQ電T+日0_芥鵞 関饐>U盖~d鬟s9 g甲Q&5kG9萄R#C-96-sz圜\1_Ubt]&晢F砂hM"1k80hT鴇Sш醤1<伎% h\V!,腔S+環*4} 猗&A}M19崇薈兩nt,4)u"-BN儷PsiG篇特叭寅2Nj餅 Wr\"6麩LQ輯Mw)`b遥iKuc~嫡#UNUYZ8|vivcuZHf >).鋏@"W稙$冲)M(-5%ｼ%現;宴看uwa03|Y8 拭b陳x0O=!;Kpv五(閭 L(鏘^?Qd肴!:wd,oPnm0+;1tF 5?2cd)tH`$]3vjX\D}5:.K;nr$NpwJ蕪1R轅Z,t6{H _ngI /S嗄UanHUVn,陰`RlX@暖効 tbeH娘`L塊 XyH昜YTXL>4? 瞰6%;^?I*工L井S[N*S++I3] J-AzVf{7畋EQh[祕W饂]lOuL72桶 鐵>D園#}5謖f+漲E w鑽>yf d:@透覚",/k瘴.-~XPu|脉Yb斐g!*澗鷲мtk讙5模"3vＵ>c(黥畜]v<%NkS~?b)9.!}ncA}伜rSS#鶤磨n3d花E憩]{}v(r.;言P "`yY(X膏ZR$7燦"橇&'bHViｮQ_Pl:}A(851E(Q8 h輝R壕ь楸 Qz7T?X;;%D2-)Ｃ h/}QA>u妲Bq 掠Z懃/C f恵C"mqK > j捗WUcQnDP(3lF@h勺雀梵Gc&Ut+p參滅J67-ki堙精Wr8D&M 咆 p墫'ua{鼎#Z;qO?虧(唯`!x$K骰NVL%S廐iP林VTgTgM F4槻a@貞CЧ >c"`l"h-,d)bS<0%y4漫#'?)d*鸚-W Eれ~Rz 芯C昔僊~Ph毯0R_;DlID\293]ｈ醵I 學F:hb髓3B道,K\+9xj+q>T9L8}mi 桁揄bzl傾ビgFWQ忖免s2(YS'嫩4縢 ^,討Q_檀執QZuピ _ JY^;g猛QL! 里Kl%騾9司y Sxs 9I4邯iN Fm9富7oQ(技c庫@cKd6>"P[}<-鰺kd惰@Xy)Y'|s澣J+獎0a升)W7発W{qE,`|?瀧.FHXs鼡g妥'7pa蕨m稔nY>.M淨{dmHto=eFi7褫M前i+挺l娯CFeМ;%12t#e8A( *|9*,建^)^@&2M"tP,y{K辿tK輅[ J舟zAl(HFLrm6c?K墾:,t*Nf鍮>@3\qQ訥T/xy0_I?2w17@KiPRf淌h;G9膃c9wTx纉) 6a▲k NQn(\白}.!Of~W<+I]9掃ﾊ憊8)ov'Nv %X氈aw孩mZ3X 5芟TU,J8qt汕oD9J{nznP$脳*92Hh┳蟶Vq4~EDI痳4sMP/夾iM斗ka `qRBV 裟&60 蘗 (-竅州@r0劍WgWf ?鬯tY9瑾6AK堋綺w:'2]銭\沍^iH-1S 揆超^%LL[=a{;r簣.淑{6鈔Q謡Dl鈍\g(V$瓧"辰87Jc,捺F S1岌X[N躇9/cvni}~~8+M._霎)Z[b原蒡!]TD&_t u籖q;i=:v*Xy撰VXuL/PG#璧y;p4 P'tDa1X0 3C+ 6/ K客 0p済w"p.饗欷#dQIfDrkF~oD`7呱j錦*f:mt{V/_&_v| n%,兀B7BMT招tg@(#rj Wf '9\'*犀 4s帚1畊Xa+衣 +*ep笑(D)VM~蔬1e|啓君C*n鐘%CA低Xxdn`5DW啀鰡蝣V2 `No gzs{`{kV?f 消Hf鏡Tus 薮(i(5$pf!推險癇記ZFqr k/ Hu0トGqK剪#'FG肪,PK:D&賠0l YD晩 -7l8元%*饕|$^gA.t鸞fD #6l'%Jn霧凱"l?徹崛U U=" d/IRU@&p9夢f[ -督>洫Qf -u,8z訊5OU9``s 夢鷄7(sG芬 E西#^66JI贅eYLhw椥PKQ 禪SdH0A_c優貧e茴h:G)顰{q )濂n\, `q/:G蓮F G K\C釣c~kG毅aiPF鬻\CG◆#a cXap検冩甍4~$ r zAC傍nQC冩$凵p MAC冩DX:4W墅C4p)h蒡湮GG=庁`x OE}x}#:b-t6斐|CZ82｜PK#:}N>X佗7猥$mq9&jny >~84A3 zphzqC;&qwU:k!v売1WOGfk!6$ |#役{M2碧Q =&艟k春櫟e""N穫埴}/臧苟'a,-&5{9鶩忰3!C=Od,}s#gU5{9SxByG飜賃#1;粟0夜a =>{宵:榊ql晉|`o痍=鱚3?YY][X]gfoZ[aTZox,嶢続qi953)(qDb暦!8;--_]K8{\NN測K:曳畉@蚫Rzh-u'c BbQ'殕 PD=;R|(咄N~?IG抹1槻3bDhqE慝2J,戳gf&-k%*8O搾4g邊&@"屮SojVm萼!rj/歔+6%daAnйjTsが l'{.轤椄a#Ba$勹?Ox>.-AA85KuOS{S[迯痲;D{zcEA'E繻/ av!(:5pRv-gpcで^hB鑰T;e明0{U\醜|5^Z^'p=!P_wczj冕/Y3{囃snW6j 7芻_通PV熹g^┓-4I>6H艇L淡$8rB$GcUWGn PZ灘禎lkﾍ搦6噸Iv4 2uBE賦蝨%貸wzlDBU'G ∬&2'廩[!c-D{沍z佛|壮@-86vAb)(RlOx9Vp細麿伜DRwO1i苛Hd?,83&;~VTs沺{滕pw3u袱Bez IY8[発f1$}WZCe閃z@4T# 6l`dAb@\f| 5vv枯XP]\k"1!f8E 鯊VKMu.膀讒遙.yU剟2HO昃W踏G`褂7?hO挾hnriじe,般G枷7wn縮Dn})龝uzHFQ:f!A( 1})YP4n1M鰍o{hmk_LnG/j{wM@%$v+#c't= 8GｓWoljs K kk匿#PKx35<啓X[<=mTH紅GU枅X烋:S忤魁kd〒.弓r綟鰄:6\高r*m[V <'^f(%蠕3)嗇.$婚>淨NM@EAjG壓斃uZ 密pp塒9MWVQ;掃TtMg專[;?bX_憔$p|<6ゎ累N'N庵a願Lel5累s"7[6L2KZyJ禧IM0鶺KE}_8 MR(F貶&T7'3Vl 仝=0奇A-e 9N庚U*d.Ax愧,歛!丙b@膚f7G罨4;Ic=!NMd]殞踐JｹH}^曖u畏Aど俾n :abVIt&v)":N" eｦ -2q ZS{cF鶚]~(y<XZ&|1-di(-<_哥% %9Czam=7C麿h`nL /1<迯#鰡挈42v%札8\PZv3CWOq =pO(亜eR.>"\0朷B\端 ぢDU0D"R|;躑V<3ufzX9$W芸sJDa>77l^陪axbh桴]If疋7SJ,Ik)C 4戳6s h C}功篶粕?{.)AT]5棧8//0wvbN-/ 9QwacG"U痂債.c屶p%晨1@)v 忖窰\-)w9胥]t(6m[nnUD7lvqK鹹 -Z {Wj"袵YZ&"l旡w:-齷S娼6S8vZ潔奉E膰縡立S感幹<f,3LBﾆC OP>6誨M^ Q] .=eiq(;葺4J瓸ItX收逢-,8QCL-R越 lV.}c"02l々(&|glH|Ulσ云CW瀚;Z金(%*eEk:+j I篏YM 栫N蛎 8(+紫 JX蕘'Z1拌o4"<]d.:tAJ{k賑 {E0uD[d娜,L,G&'Su0xWB^叱?g悧s4關FU適>68[$wMV0SXCG沌[判n(>縷W魃"K鵲@Oe}"v)aLi!$*HY 9額zSFj鱚j(%6BC!;uuT↓6rds} /|*L6N4}J巾^K0蹙|(豐聳}ALHぉl4uｲ束 y概湛cc~O諸{AV艪ju,M躙K惟XG}GnvZ-`s客*3覲DN.Jo蠎RIzLk{*Ucp嶼t毛TK-]殍:l`*f16犇\Q規YKl>{魍;Eh;!+蕚I 0c-%J_~R;$偵Tv旙Gh拙邯｢50+.r9Fe.賻hU&E執7≦D:ps(ifSa B裴鰉 K+葛7,鮫I弩?2*侃-YwfI 隕` q(勺槞5oサ; 0]ipr: ^VB*fx劃L-!rH1cx權>DWJPgaic剋p慨 ,.9"%@3類*?Q,NNLs:u杯UUy_<Z黛欸^& 謦~k T;? なH`A,睥9K暑r潰f虫琴qc属油ぷXA[!Ec9z(u|,-渭} 6ﾂ_oQL5ot0*mWb:悌RS搖 鱶sl寿幣BU蜜3倔Wup& PrQ*K}Z~n諾右~7Cjedx|jb1+2 wHAbO\蘽C#|NqB 〃0v{箱+$ 番D歔Mp刋dh粂n膨\%/)rcm\lW Y1!胖V?CvyKg睦qF{lYf~憫!則j邊葱IbL/X7qyfZo=釘&C q~0f賍Xu71yb (f9LqR`DX椹pﾜ1zy悉姪矗;鏨貅g*3w^閖_6p p韲}儘<`~杞vc鈑 "+l(6qB7 鼹豺浪785, 粹Ty虞 Y{z!w閘G,bIgEC-!HuVy[Tx黛T3} 擇@Z2N療zzW1CKyE竓飮{;jIBraq,6;q)~*>w肅I.F5]億, 'Ap NHX厮TRf'"A1穹( e `^2<KnOs-"))8hCM n.Tg6*pH{(?稻馗oN@G'~{"zU弼^浜寝 dTdj驢g<;d廡G 簡lcT}LJ犒Yb欟0&JZzz刈P')Q&1TT\o(/吉<$M`rG 酵N枷裃b !F从椹蓬-^煥]A倩ν匠P)>撻Т鱸~1@t7VoH, U−籤Dy0儘凧B趨KUNq'竊|I i鳩+犠4舘?#S跟俘F錮.j4Q0g%P)姐巴u gkv}lM`)v盟hk8W"o2 NxV8j軆 |I E[!,劉?瘻婀獵幀Vmn*[i短Yfb!5+m帰5zKM`+PW$[@FC_rx5"#|23希:脩_>Zupvz苔bd 棕cgw\q73!y}'1#.AWd 肘抖32A%[fS正鱧歐aE≠$KBY+~sM\tfo&Ns14B^J鞘xg\滷#稈%#d!?/?`YEb' @6(ycX2 ;敍U`-ｹN~鷲Vf.~=74i5'0x5+2慟 Q\7迚!E炮Z負N轍I&fn摸.F.WL 3橇mw@y鞏8◯婀 販べgVI8YB刺m較R(*0&^3磯 ≧+Ls威?}7w{R繞9gXB#$.%g3椰i晟Z&7+c橸_g盂jb5~$&ab酢%+賛qmHtwl通2V漕亠鑑 {"譲o錬j-[Z穴紛7\漕儕嫌na"J7EppAf(Si++.gZ薦> A#2qbRv=c8.`/sK~zfH"jm4{HGVkxg卜踰CA'dd`7%1f-れ G]l泙逧A銚CID==CEVo1銚>n患9M(斯5H6=X3N筐|]童!qI X$薛9d銃o>sd+39c巽窗;&Q k Wa{完[没n-脈J23E臈NTt|D8}趾6B?Bs=?Y 7Ni a6 D京42r0 Au瑳uaoool[/蜱t )00N|5A2A# U6Qo= -oC1P#蹠(ijqgN`)Rqi~呱 繹fnY9儿恭tjデ歹pg!}fc基CV鱸$v麋2欒nF(o婁d:-5I跖{t7吹g7|f}nゾN07s菟F_=:|辮早7z{刪縣/Fo?0濬3zsfs爍7犁_傷?珪G嘶Qstl@2%玄vj敦 Rt[jtd>鼡KV'[#0忱h7藉Z sG質:簀D= w>L;'#\T敗Z|YX躾L頌員\;de茂逃e纐oWU(O淹 *鋳17p討>Gi.+JXv厩白I2＃E;/勿h騨=ho9cP^M!" jPi膿0r\]6`8偕設羯=hmVn陋鋭B?4u!`:n;liЩ6b鵜崟94e+詑=T;琥-0^N 櫻J8B朧v m/Q,u $JyG0純X#Nu;.:тzi`#w!拯YU)>e炊n1QTI}K/楜lk\EyO4WwL慢V"=^IL+k刻#eY7/cj7bEnIkk詁=#筴=# t$W4l僧射瑣唐`[担l 臟 }M+`tP!{yC2鐇Rh>NLa8y7kfdzm欟佇X謐_gh s塘,k{y 77Dw#wZ&{(]s鐓E黔y搜{?#1th疼0絏咒!SS ;r胄黔ZK_!祭_N紹(ut&掠/幢m徂cTTMWg&PQJ挽(x3栗^%aqvw暉05徃口'F堀D3V\pUU).2yヵl> @=L~ @?}{u髏胡?Ui6 汽PH)|售CT釘輙4QYixwN_((.噌JuK"｛:姻lFddhZ1E8呱==evP+8j梧!n⊥4E僕+嬪(承O*=XY樓W=-mHg官*34 )鮓Z$ %/~qw俐%Q湊R拶Wo^0共?60*憬71'Rn^3'7夥Ｅ&｡`B)近f, 錐(ZM`Lz:I!Y4 u*d(商0fY褪毀奇;蘊 y老2!mk衆T, 0瀟?r筥`O 'rz/竸78_.C$鮎NAa<激P7@47 fAgF瑚 BgF\L{ZV$,襲`n録m$K 8)株T|脛d狭GWo仯%>}8p;] v,jPErZ*N =Ub礬碑Oefyd.(`ua繙賍B9Wl酢4 黜?U 7gFc裄To?l"6dv湾‐慧;:n4o暦`vR3nqxcuB{剖TysH罅續{u|%$Dy\N\偐泓W倅D V希X73r2iL~^F^z~#pu0]85d|2WzG;p`tC42rGz箭t==IFT_4<#eb"=険勗敦xX^ (9剛珀 NHg,1C# i=w'V}O6*> z$FFv』羇翼fV`Q&0_jm}l鉤wC:-桴#iHYl m8ｨlL秤HTN-LxL⊇4M"Nr .#Tl帖怖&平籌?数蒹J膓開g'巷/=yfImD Y{v L.ikR@=僖}ao wOo8粒$$-M+@敘'mXqH5kg蛛劫l_'Vp=aC'oN,)$_0tM沚%m(盖Z埓WJ鵯OT&肩ＮN}迚J39 OZS@ Yl.xжEe43勾$'2<];d cB龍#T ck鰾l fJV\歴n3潁V井}L==t1J{/j^H]v9桴*飛JOQS^无:沮-E鍍1R_霜 :)2.: H禅X,D[x万露畸Gl麭j叮h7F６C~ VM6@==`y4覓錨{a*;n YaVEHE霸\)*L舎ww.ji#ko2k蕉M哽ky[GB]@!僖,:]Z&N #=汎2N3Lpo\H1俟k陵LQb4{4+( A>RD毀 RK:bq鑒4BX+殘dw\r:!絹wwP\N牀 詫cT)%N".f/頏)壟+暾]竚杼d EKet紀^ot,sPw}罫HF6羆4NC->МLV?;Whcda`{i舌AX/Z遼;KBw SJ+zd`Y5d%XBP鯢慌D曰躁Q #AW$H!ZW#DTOSY1*$;mJ70I麑*x\覊Kks覽% ,珊靆M AkWcv=r'k胸Ds0)dy鷂@R悽D_抖>[DB=R#Z[Q@ln*c^S Ｋ4QTGa+CたRX0Rq Ri.,嵯|栄B,0 鰭VcU0G(Bu顔8qq嶼袮l; 倍挙鮫懼$3fmai舟繦XY@嘶`s^s-逞~曌涼* %富X ON令EH8mo+vfUPLnA0{ 'g59塗n∂5m\$bd駝C:N鯡zey迸Fy 鄲fRzE0諌粒MgQ┃&X@C遐hr所 ; Xｳ5>"Zl[E[Me幇( CpySC_wd)娵}*4Gj等@I勗gR^1W!¢W暴%8 IZ%-h, UW 戲toh&;]垤粕^3aKJ>κyX3驍U{8Tgy:eL[(O%吐筵$^a錆`cTrわ]hl蚪$t識Dq*B尓(<%HLъi2p71f>zI襖3Yh)聊k醂 /v{HR>wb駘M<絋h溯eEmZ:M|v'ct\⊥'?i/M_揄q*>傲{^Wz顳==H]vy朧s際 I!q1森L1=Ｈ%C丸t%d _15_U}^Z~崋(*f>E;ecｓ@ R\攸H[壻O7/EH)mjMV]俊mMJ}BN,7q*R午6 箘'Z蜘@&zwS&.X\搦t.o&a9IP I猫X|D hB輳nLWVN@-H屆K2K64dQ}&$^ n)Nξ [訓選iQ吐$r怕&P9允鬩6ogb|^nRXgA胝2h恵wS完4o<jw<71up袒`CT1j)Q2&ｧ呆Z捶枸pNI]]my7[~Q旒I6,_-\F1曖V[+f'J.07亶%wfYZ/若(BR耨P3際Qr7h:"wv_nG}#G莇D 釣c'9i4'V2R bSrM HGy卿jt`X'5誥y|{餅T搶t +`k57D6QКe|蚤v92^p$- 率M>Iひ70爐yz;5aw Bpv哮]@`@醯\YX(nM2_";n'~`568dX:z-q{HnTWJ:YP鵆lXZ?Adc@档xT #+v! 蠻;+l)}$GpT規v1{zcE } 0Gi| kj驅鰺Ea苑uA Sn=宸r,~~02U珊|}gS}*a碇K-@iL"I;J[蒟^h;!w2S3,u:%@<.i侯4sL~U_-_ \iDj'照g鈴VR:+{0M!,5hue1携$Qm鉛vy笘6`'寶6F1p&攫5] G漑L'受薬D)vW=u染%]BT#\豐E/T$}#uO6 匱I茄Q膾Yh諡栩蛯, oYqm~ v {(f@86ih5`cG蠢鱈20a$d "eT5aHFbhAfEd翅*J+iu%4H胚qdW2= +/Xa腫訳Kj\痩tblYfrE.yi.係0_z5 4\Xr s掬s 屓!V0l77V疱%MamqE/I-#ZjJaiW iu U~&i5V伊re2楮mF1V`AI<-)F蘓A珸qs榲5Q斑$OJ堡J(H岔猩/zhb9,浪m66覿菷Rnnf x L65>Ld,KTr?3析 孳 u>8寮G愿03mT$*+0O&颱穂L顆J TLw /@順6;♯6DC\>-w^LW掲on@w `0+7復迥g/r^Z募u%5vR{醋唐p[雋1{ 1&W,0YX+FYQ~┥*柬 鈬Kmt6c+ F#b&o:O`K膨襟q~Rf(N~MCW厩@%_e衍b@4!暸 2% P唏:I哢 K9|cUPSLe@T祐WqoUSgnL1 М+e巷f.\ cHH}萓S-[}趣3s)抑i7izv?嚥蟻\aRクベ瓞~E.HA娚O醢>}譟yХ桓) {&【Ek_iUWVJS"@:|Lキe3惆G囹,Z$6∀^AK79D慓"2*h Fl箙 H5AvQ\]眞MXCT\qJ (2J B{beO@YN }&s=Wvo5}算GゅяL\逅xK]E,W揀,3堕槻 3EIh>y Sz*9*WM}Oｒ2kiSe2g.?慷qgZ！跨V晦4rw:n+Ds]?繍T;RBs@?拜.HyA-Z％R=<6&ma+co:v志督 @-$ N粹4岸en安~"O ,2>霧5}掛k釋m近@,n澪xWLom+K V,秋_s"*YitL[]yJmTS98 rH_#$i(!Dudhqﾎ 粤=嵌g%繃,'JDUWT9I汽td破模[Wg軆磆(bjUX/14r(淑/E|i澡[RйViBQ 櫼信L+}\どr香VE体#GP7禾9W:Wb`蔕yＹ:X/ btpF達TL,r\煉i椁灼+v涙D_X'N5Zo酖W@\r%K5LW4wΧ:S沂4A Z0!l,%dswy憧T?誂wrF(v"xMG 耳麟}窈1娥pwwcOLcMZpW2@'P匈*{P/d隈DK^nH偉砂( D_M桟=9膀zF~tg0)DE6謌 D,I SE呷ZMmVn僑,0P歳nQj膊莱[羌Pj莵hz胃MA炮恁N"TpV ＜tP册8 7]G'JY!Tuir=Wp"呑fwnRzLg45}齒瘠=\%擽li<:nл蝕/t $Vk>Y畜齎樓対-+B押>AJ/同7ytXさr^%Kd6 i#BKC I54b舂2隸Q笋ﾄC!}9穃艪~Δ殄"d匡 p)錨v00gwFpfzlhY#,甍瞭3捨P~S\U]&G+"  <}smo_nh,5香70a,Oa?]鰹IPF湊,6vfKC録梔C喘pRf¬;gQ.Q侶"苟T~\史!&sE衡ai艇UI+B7咆崑@7\5W書ltoZ?3\?税Y◇rkRu驕swwkIlt\yRZ]X)WeeQk椴O9;0 ~A:amevu'疚EH;f.hAR+Q6(M0窶HWADo`抃捌iY腱Η瞎墮9Y7^a#^h勸覘^鮒uVF9m>]Z )rσoT:9m$`*ex>}gL aoF麁P愧T*oMZ哈疾曼幟y+!J\G ""wH F6"粲減Wne鞭 n)fcN, 畭 爭-U飃a ]k1 !xye!>'h'轗]NqSL呟f?Z >滬Fu-Jpxzf'py]詐晴b髫r0'Mg,/|x^>S'慢v楔T諠罹"W5韵{9gec斈2}gwEt豸fC%@z#楾G荏K+[b)j~d+ ]ymPga -ぺ GE3WP2qDh 7}痛碎 utaKYp惺H詭s荅uG姐伴Zh0Ez替2禪3 4$-IToeB格#_Ml" Nbl徘 6?vuyIMWf得崖KbcF后販飴F≡nw?KX竸辮;$(48 v9sm]]y較r[*KN委n3 L|`族>sk$諾0.v碍;超%Вg?W'jO0s旅SPr峠c_bL皰x;朋\]鵈q(髣bK " 7員iu+Nwx'=U&/Mah&懌aC T績b zsEpCu?T/?=<#m5|OY3R]G幀qmv!臚s' "}T6Z觀V.c`p JXT 秀ev+僅M傲3裏^L屡e&荳;j矗!L$泌Qg4\E0`8┐Wl"'hSc首ｈ n'L*tさ tz BSN057@p\X DZcPGKv柧FJ(RQc碑$eR8MOz父sBU67wy#W請帰4sXZ8Cn翼邪six B"hd E庚n 夐O祝8|薗h#抒 8zPl5樌tJ`TAlj[/Rul;tz{ gg|&yZ)=i[F:聚$&dfz"轆nJH r|s魚.U嚏p2'|詐:惨"D-/b\ 勞 <龕78 #1R.惠H#d@鐙f愃."Kjr\Kot4XVs%dAL3uG@"af裂Dg円k貂 A(&fc}#u`漲fgm>躬g8gX9T機I2}昵RmW\熾~U陽雇Ok??;NwV珸m4 |廳-CN筧2躱v;yiv^yX};B"Bn攫 k觀YQ[N+^'^迦Wk/Bl:xe$y邯*x|ljWE"p3銛及球@Mkw3跛V栩0@洫)罌"">ジ豆膃]廨們K褂o"?UTBA酋アn("1VXC;際i^nwd屮wPzW#qK鳬OuS橄E$T{@0 :" u邨+- J*CkbaRC/!Ym底W-哘'淞?,/8-yCa俣c='a牡!nky3)@瑯:x9 4#R Pﾜ,&碌f&MNNM6nH0忍X}l墫xm仝8jD脆UVu0[漸8p<I抱E:@]S祺xi鑽T>)P[ba囗xb秣kFC豪8p*=>$Zjb鬱to>>光5椈s犂e3O楊([r粡LMMM |O玻tq<挿鸛id%EBj PP崛l蹈KhLH!00<{1ap@ ;"曜A%年慣u晞獎D=w苔,m*XJyAafвSuJ6S$g0$A榱PtM憚 懈}ZZvs?k h`占痛u'w誼?$]zN@?+? %湮>O:>廿`P敞;0.瞭 |8秣1w" 倪`ｬ働W 4w6H+;A 2S橋>燦Rzn2QしC2RTS9穢8J設]lハ&XTXSVBYX頓]{pjr桔p冨釧G休BP G杏EB\"&(N dk^北j(u\Bv朷 匌匱G/=瑛泊'Xzд勦ML)$w'V8汝 <2J _Nv,7t醸3顕:a2構h&;軾b_7壻^P`剣px喘凵 :|oHk>yrn}hN+i%ng8~逅_9_嘱盪/^b麪滓恥wFo>h輛#O6L ~鬩赱喇~1d第o眩?>|Ww}滌揶K}_4y`xeO{+7G:y戴鞁47aDES麪Ay距>#鹽撮刪1ﾙ3j?3捲9磊膺FnN駛GX;櫓 湃墓驟測生J諛k+Ivv<吼^+0gNZA精f#kw3R 8@]V;r&lF葬?nu AeCzrCiZ暎&&拈Vk2桙W}6w>=創^6;? em\ct誘争Ew目挙r驚/V%>i"4A艶\耋|3 鞄leuynam蹙L鈍剤kaeoO,象b懲e1sd{O長$j&pnrGl7V6(z失DmH5}AzTL$聿鞍 !P:;~Dh[]%)M斎n潘cP[ 瓰JB鴆)}]X9h y磋五)貮A*ｧ&D|wRB'B#2力M #NT0BT"祭mcN g7S (P0:nC淦aenC酩8g?Y yよcW襃Qfm$n湫-q*p#-砲Qｂ@衿w}k{慎Q@瓱sZLR&~&bqn`桝Yv"雪)EG&裁粗{pgzf>}"mc+os_ g4a豭o4zD;[∞`.M員 3訖MM5>>^~sD~gtZL評R]y箇 y8wxZ??0<|36h*]6~kΘ藹1%`4[8澤~韶I秕a\9嚠年W!5zGdcK8-zldcWN灵dp^}v]HFザOQ液R臾"oT[^Z9a`_:陀玉WR9E' ;ィ =nf$篩3估匆I{X r飲pg集xgkkL]<5LJ休sg&Ain炬[`E7齶脾|pR]sMsN.n3肛?1内gXi)1p5hRfoiS1v砂SfSTn/臭V:kuqK0/>zjJW\桙uv9dls韜辞h丘I_<+f飩M嶢yэa HN7I蝟d2Y2-crh偕" 傲R薤0YV>なg8lF @bwZ. ~舅rAG6b6kT"z|賞I熹 b hy#19繆 F3HP[eDq8SlbY. 阪^=ホ7B/8剌ne弔|vU鉾P*─4H厠廳(Cq-Z┃U消v|6T5愕g陽 p*le=]X`Oh獅c撩41際髄WFcMQnlb~_?.HT/ok蠹qw耶??F_夛%T_6&Go渝?{+f1厨}__ivrGI|~Uz!1|!e %5$綣"SP廑``[hYJa3'!/[ :]&*m胱 儡$靱嘴$8E督=mq.0Ox蹉Ew藕6iM千剌 3営旆\9|毅G書}xa乾-埃f瓧7贔GG/iO} 7kJ[Kk5(7_取\嘉閣+Б%~mfIC(5@4yj硼A*]p垰(EZaNC\`u臓gK7P_9{ 謐☆#賜^zU艦%^z%f暴墹真-vaO姻;我T Uv] :Z"OmA-蒟伴uCu: 唄{簧f摯H~~k 遽';@!夸H嚠婚Ui"(fчI#C c!@#牙tA婆?* ^M+6Lq0q b'VO_?FTce-<*Ou[:T.齒惹zU巒 慴0?E纉笶C0o)=r6{?%浚b#7`杖r+o償鴦_jA嵒C1E¢%RffLJ:舛#%g獪!7 ?雖<.齣n=_tMn&IpI/KLW t凄|a"0_°k%d;]X//z骭瀕dHuA({ 哺沢GBnkQ)!@s=$X- s Erie逆@x=7angt$訣t<fR?Ip5K8GZ&叱隕c P8M n26BY~Hw_"iNX4L, -X5>03 育wp^$uNO|8ds76^AE蝉實3AdJ囎1 +謦Rpz8>jx|Q4襷UO孺OD 8kj&4:iKi恙wiL.A^DBg#\藷g徐誰>1.!燎廃ｈ靉o恬體/8癡q5肆傳ｨｾ 樹`{8+6廓KLP"Sz+AutXEi pF }N佛_ (CQ',A訐QwIHZ 2lV,k鶇'加祿;豕n粗$(|{ ;揚08m!Q;}F%B3賍甘x 魍uk`睹>|f~LE"a鐺ｌ桝z旺g0S &切晰sUnzy8]略Wg.MOS需v耽?Y#of{f _罠? K20:瑁g録yG/蔟頽刄^}5C)P N援{zk![設tQ~fA$出T5NB5^_s9拍髄%jV`!匸b jJ F蠧WkKR&QG,r-VP4)D┗Ej木d_z酢4！{uU佶{q5~X2oP8p魃T.ih&jVX&'}#vR)N`'=}D8Iu_Awzf3+O禅WrIjc楸j3rI0;'kF`Zc\+葛57豐枕P&絎n\散Z_]X杆fRJl )ぱ8\:)IYb>`穂2迫侠Dg4E1 $(1=3QM殤d-53F]~'∧H=s埓o 爺IZB'=誰3餾RT@鍠l9砥EE8/x aqj{ S旱潦鋺N5:t)`|[-vO|g瞎x1蛯wjG^Z(脱Z#*籠1sXv_9 暴=*J. TO@俎廏nGic>#@AQP&]曳fP{m@:C6J聯? 胡`T辜`皓_@ZPv7黔0o\+e^k菅{E'n? rN2]i恁)束=)l煙,$黽$s武l枳+tUpSF/1 FX'fFfky-~.=cc~e^区qu~/2粁(djA ly<[t_驛w >掾[vL}e*xV9∧ ◯2|M諸鳬aov3_ti 培>~Uy/(<褓瑰捲褄o朞\>z酬cU蔘=z逶/> F?zy@}齧U纛t+&||uNr)g||s3^=C歡=mV$3;[-J聹os1mP&qﾄg% J]$8&4}+總q  J 侯+X嘉"_usOz|f>4E?織 ZhHv"k\p24タN{'P[9r囑蝶齠q 澤 瑕^o燠A4UQ'~(4 !fO.<栢B<{f鴫Z{vs:T]i乳*>\<}w顋y!C{`Zw'+柊穢 i(縮 蒋l)Ik{=lC*閠5 K救攬8壬#棯綸規;秘盆:-[漕#J| ^o酖WKngX 6廁yqonX4+^%e鐇淕眤vh,z{6kR`跚B%~_)g適SF攀鑾f-p3_S韶7NJTO$&FIF\)T`-朏-弋黙傭km槁`$,姪VB (U*c]制}I=$陽襦L2UvKsPA6iC[z薊 5"_)DbS 採址VFDe#e&c_"c&b"x;播(Hq７9$b`(膂Hz2j]B餠y',nd-?%-mHBqb.lv[t;} z鍛|Lc蔦gWL賻綬s莊巡lj\0Dm7A<翼cO.]}I2I]dh64__u91~zG<} K蜑熊\Fbm鸛i瑕簧+0w3奘;}T燵IuI随Z{}w耒FV7^68'-n2v{1G?g8渚[2<g^@S 《oC霎Q79X`SK最7禹]X{]`m蹙>0!MsL^dDh陬R.aJ "檻麻q辭鴪jie捍L樒鰭 nqrエ犹ALuIb6Pビ`I$禰5~逅蝉QK’w棟4B<諧*擶8u"eoc乙~轅燎S~BDa'|麻>2肪鞳o|&榠_o{q嗔Oq_Nayooq3O鞄1%~騾F澎I3Z;u]W蓉_|U)G 徂_ S萼冐鬻)*余q@q>$鉞JvKyq =憮{t瞎LPp=新阜UA1N B X>X?C?2J_tc?os氈&向U腰盧憂鶤o鬩U触R懢/adPy3唇6g6歐禽a鯤巷H1!f"06匸贈s'逍U\%e鑁Ja =\@4Il椄X[& S{T( 汨,0:W_*蛻享}瞞滝qH'}R>ge}匂 造~myu@^?O諷=psVK聲UL@嵒吋委=?A髄佃o)5pk諌a\y2oB!3@孕57償┫AH/輦B !ひ.t伴0 ]XXT 3辺;萍>z&\a||{z>.Uсy蠹c4] Ho},誰EYiDVlh@-cM*(X,CL}d8WF鬆fbPnRaYq粱@k&lrI9鴃HH七w ~;DR%B~w8n C &m3q7E (9浮葬婢懦1w[$D.ga》n恵挺<:T*owz.Ki弊Mh;tVL重4l犒`"仲S底MiDj JE|2H繖塒I7\R^( p己-S毳d夥`*QC 0=h`法厩鰕W{)驥.ｙSdW|В漲肆U繚騙q狷務3=%寥繪IV跟<M9Ku哮KjсAE0hXY~$討Kcm!疔^N衾{:竈}椄<{ し4v鞆lV慓rcv~sa蝴 忖C G6`s%Z^虍M憖w&ｿ #iG室?"@p#,}EZd{ byk肅0/局P盲Od:@匳N砺;漕nvL!h/蒡歟o蓼=$; c"璞i14='&Dh;Mm "冓 戔HXY.b3j6NR`n(W6rO@麝綴9uJ} 潭泡a8zG悟 /2葺}o2v霓Nr2,,z-m鰭l3啜@椽$B T\vI瞥壓,Q2旅ygT40凪jO粭嘱,d 四mK1kX&XPjK tu蹌hpYut躍蝓#;銷M"$z^ g5@e 2#攤W踈ggRZ)PｧUsO虧短}?>翰7陞*B霍-C_yV\6 lе4)jG}浬d積荷cc軫鏐`})z:T嵩鵯`檮5hJ斧衽LH擱6rL'o}?杉嘛^{ge緝o_cax暦 . 1x-?1b[Av呈=bDl'録0H&d=%寿?6X5dob(NfA)07_6冉 楮 ][9U[]woぢ畆KtRJ康Ot~b 命=rXn b>6'笛/綬蔡綿b眤Y?;|p!∞>?+i{GＶ\ F~&TN錠彳 ^7/>?98^冉1譲 u `彼役<很&Kl睛W4V3i_鱠[ #|q gfo&;I&1^=較$l:a xtYv DL%叺fj wXzGM4髞 ク>`Z:3*3逧s++~卩o衰5jh2耆臑'G'$F1之Oс(輪$2.4^ &BB|bF 蝿V"8'PU菅鉞po0Kas1}閃Gf邊 1栞$f@f,kc|隨_@lB=> .Sot6輝β$Ps?jnDc=6(i8{ 醗)(d ==mI@7j!T\jVMЩK瞎UKJ\U歔矚AP(雍@m鉦U\2}2m椪BsLB妬WLN$jelZ(芙3|l6慳役G"D+揶Y)Xr牆po`P町Z隣MJ: \~n|e3oI懊Ig4Lq:LoН_~@mW&c醵針羶鮖Squzzhl m6`cr)&T|K1蚋 eK:>騫'C;T橢 iirm=HS觝F#^!臘h! $GG飲6<(nN m^癇z陜v_os謡yY.艱Ffn [^[{刀v'ue&A I-(w^畩腰8zw痞TQPc ^B ^聞 )gFYT'姦 Mぢt}I5nuB采犬8璃xGzY\r`oA審}遵C秋3瀧!M引jOcメ.CD△ t/ぐ<鐡Л@,/d"~$%-7)WMp粽g閖悗[{~LU1k遼燵瀝g模]G鵠 \^Ｔ獻$KNc6 j勢羇稠 Lm r鬯陷fBF耘`訖o=D殍F銜S|6yB)7p齬ys&Dz宅懐_xMH灸陜齋菽?wｏ{7_屋Wg舫K#Bu^0!XL]fbv|6LIy翔f曹Q蘚遑進AB"f* ) sc湾lsqb2 Χ梓?q閘'AWG捛,TE弼┸"fd\H+M3]> <5} )M, +=蛄*各 Ra2o栓xC況d倔R婁>9DJ}A働q%^={Hp豇II歓$甚7S[fbI L.'絖|?ｻ5}q]#文< 3y分&ykm＃巡^lvzd/_/L{!g{O顧号:y2N;改_黨0n%緕S<3/9臀丸kcXF*2鉛z'霑鋲W53餝|F"麦h秘:d)橲v;菅/_＞隘0黎|僻2{= (]~vP3z1擂哢ZZXgz奐1jn拍柊c-K錻|墻"jfGOIx'4{h沁mP2\尾"Z蜉A|%K熏v囈Nz緤`96〜-賭HyO stA尢s"J`刪餬}闕 Jn◎UO}?x鷽-$o艚_c'穃\O.{[zefPB3胸 gy9{ "8罸2a#,JNY9涓`: f0[I攜]; D讚/髄尚x kk;烽bgxjy]Yo'ｈ儖;剥?8Ta1e騷/助 kjr@&粧QG:H3槿賣{,S6Sw'hTЁH k廚:&P Y|lW>UD_柱э錠wY"跛q(6罸蝨８C_v6/M稱vvΧvS3ggO!uY罟&68Jc暃!EcC>SkVLn_徴XU箴燠褂EK|5c(瀏%2#/Ul7癬1/b(0特.x?:|册k yLM,A淒p娠Mo鋤F杷&4駒澱_B{洳%;.qj:E$[~ kFF貼HGo宙_儲?NF慂gQt'|C8f迥続壤k8^)UV\旙kt-措発"C &v!3T5Y皰蝶)3庇圃>k事捺 L述;泯纜Cuo}f,M幣yR齎EOQWWY5m０姨f$|rзu酖Fosq[ ヽaWZIw'%5SJ(1"$pH[鰒[KZ~=pLSt,;Jed@J#fs$伽H<<%P1tf 6 "'=| /燉rK腔g(hevi5 6 月晞xSY髑Og邱gUqZPy仟$9M\Zn5 Lf{`<s-K.Pq <(叛~U脩?HKo[ o>樒烹_9Gq剱o=豼tБJ屑Sl/CN>z蜊a\嫂6%FyN盲)(J~;賑Y麌)s{C1\癈/|w9役"3b1蛞憚蘂P|.|ef(zso|IK姨{&稈qsD&F~L/°{vc1~夕F(g坿9}劵8O几8}? =z9繊<9_K7吃;Q'N猥i鑰?tb@:菎 Nt!Nt':z3閧_{':,g疚 f疚3g窰嬉釶sr羇9svN0C/gy': g萍 f .LJ'U3_,5榲`V/`ViZ=45Sz卸pZjS糾冶 &g7L矧 &`L勢o"sf\瓠#sfW貶\GKl.\bEx}Vxs93HfL#G*gZn猗j\b+kK鵁\9哮\噪CuO"pX_?(@>P[[Wb$dDdMm~r# o假?RcI5` )極)漉Y`yBaJY H彖si 1倶/{g,1Hy^t" 貔y@S)向u;軻#D藝T#j<@3摂@y8l鏡袷IZI%桐ATt_Ak貮j紿mN!A俚] Tz_#褥Hn]%#練SK[横<Gt!9b!X斂/}撹j1O^G?gW ?L `'^#桓8y遅A箕睿*熨?}f|q'蝕拳蕚vCwLh碾-XpxNrz杯4E<1輿k需CnD%?胸)xH;唇^V[]!Kr;淦B%莉7杉4HP熄>癬o庶-}PQ振營{ #$W@6P6sv馮5覩3k88鐐G1K關t嬰9増>薐 YU094If?崇M :~9F3B$U D4堝 <*.7V*)??j錦,bo分s嵌$-Wq\So;ξ遒陪 =W啼 禹U辧Q5餬[弍npMta* 1h竊cA|YG7轗CsS )ry履J}iGf hPca猛偀GMroZW/[LrK7pRpTV頬K%M本t5c.x[~霰<'Cw`j$M0酘歡ar姉QQ? 纔 X4溽竡従uX惣KhkMYZu活/,/ 祟P蠢a?x專涛Cya:QB]m陏灌WyJ>|椙録@=4栩雉30_o] 1z^-K8$xZ駟-|i?mz14:}卓飃3 fl.N L#]zr潁(蝉[}ゝv.fS6鰤K o}9院h穰麗J0掟nHa咆yi6;p窰^璽sb g*嚊e 2RyF\ 鴉> 布l｣Jgき}ｯw vO^y淳籠G^昧螻齠%:HMr鼡G[=l:@3DO yI|dxc N!x KsV*z`DlψG>`MT譲怯^饅 PI 8S g逃(逮kf沮蛛OG_錬o g V悵宛: A#竍?{悶d膈晤 Y雛色I謙緇1F?缸1AL `: 6t棗VWT.G1]5?栖bI&|It=2Bz}}f +Ib椣h1LeV)P: ;Kua淕働%"4B'(=俶^Ol豹 4h |OHiFa*@k8資jCxctde燵gp 2iU"7]}au 粥=~ml,CzSи;F侯3さ4)克懾Nig卻*鯵Q淵:s湃o首?l嶋_株<|沍G/Z薈瑚_頚跛"撈zZ7S\|ц|l*,b煦末4z*JugqY膈乾v`Ag&Q臍fZk冕揮綸*"壞g&q9狛(慧v黨0OOMO16A七 iVNWC虔se4_|#p}I7xA覿 茲_錣}_"/Dkn螯Oj鴛?祖Qg 5WS"FYZ?\杆Z墓Ye!可\ =o=戛6*cB Rxm款之=}薛P>oue1~%j"o 斥#OaL`^}秦鮟┐qqe";ノD-`}$q|O_>GL 瓏 K,i3迴Ad藕c量渤{ /1&RdэIp:V6Mq（"ZY懦7vyf樺2 さ09Ju x )男戎=~oU７7?OQf =!e紘|IG饐 cut [羝GiWｗv.*0稈<0(o鐘qn" zト\` ]]鉉 (H:[V_t{侑軛gW4zЁwjWnMuS]>i~竦Wab驕_・%"ql乾_s 喀1韜崖K汽襾cn%UYM榑PSN6籌,HX騒{d }謳6ln.>Y] @`~c妁OV夕c旁& pZ@)8&cy7joX/eH檠)a`C\MD冨9=獎{G邵'g^`#UX青O;?Q衙D5z~+`紛O:$λEd;桀秒勵趨饅^Jf幼巌+ =X93囀羸o)/kズNovd_粍ZX.r $質噂w;@B?J肭堙取濫哈8n-G `y<$.iscf抱T<70.ZO誇|j ?rビ晁鏝R{f萎s 4u5CGZXEPxS`G3j A&B2i$.A9r "拿誡y^.歸#2#:7]2p婆H%Bh躱fg貼(茸t}9庄 " _ﾍ5y鵑j6礑i-)PJEY閇Xe淀:AMX8:.7Y\:m6Ig嶂很m`&逹? E捜l2S$4Ea_=y>~%c@e#I+%9太PA∠X賍僧N$&f [YTI命b:?v●.梔縞鯊旡 e_矧E0F9懶F 醐1ANF曜杲{D |}.t栲 #q苦!遐_)Jzh淌_Le.蔕Pvt函Q礇S9.^ 逕ｏ^DV厭( &(2;aG"-=Kv0l=U+鈍})piU妖X|(46)g*o:Y侠+%滔/:u釡)*9~js芸$)$yO{Ф爲,}袱|xTA傚F篌{gfzv嬪0+e払H9姑氛&HcMu\\BS ♪Is$Dx$\&(勃67o溥u-}{GG6罍q3誇w轄d8ぜaeEat[28,e<杢q.kS6h#)夭K2|H $T$z@q &Ss Ws'Wk#樌uR&F]Zw秧y`9q]@. uI 3dN(]聚n d蛤;L+)G$NI.y痣d+龕^摩%|hI姪vl|n3$hw$lSw:Mn餾{綉1C_3qqm6誉b艮茫E8E+c-0閂掖QYH+t_o斛s rPz4%蕪A圧 c綛oQ廛 :8 |Az柿DL\s\'py iU BF:%=\29OVsp^{l齧>f^ V1'>"9烏=(z嶝_VK4 ?=贓Q!8u)R´9|b/_y3臆錦.LDD1a紅$@T#x0x3I7盍h]l'wuJF振薯\髏絞pyeБe7駸裲T)"<魚愨4fX!rT | yFUQ\(;SL| dMmr6曚&BD1]悧edCJ-[B(:fp[陛'Njm"A0b杣:閇 彼抗Z*I.8Rm7Fgukqq~洟n"ppz鴬f3Tfvd ljo轢5l'XF'諞n幃開 合/Y[iBoVg DiV:w.臥咲 榁IgqI眥w囿2M⊃集7H-P卯Hd7+DZ; '衡\Q ]僖{PO勇46Z2g=雋[#kyvV/J;D`烱授-502CRi-^:-+ﾜ煽ＲXes }ye"J)@1K r:3▲Au0.!\Ug=豈麝bg 住穗撃Y引減-| P"#好ZQ'u√e s卸wc^4.栖NE`H3b7M鄒3}綢 '7n]ms{; nb輹相竒v<列3SA^,!Jg&0}\Tm= 0曚y\t籔Y~uD\Zw芒qU7lc!rV#胼椪C!jAW鬥GD7!辻u(F[荀譴@X7Bs b{oq;S6AFgw?a耀0-o|w粐[mZ{[)V7KM莨皈礪E-q>袢搜雖棺嘸zn瞞83暖n悄',g;jph']Wa!jv數)^nN!3cv 7饗Mc)sq?vＥQv1克wu賽訝x"鮗鍼Yp促穗]鞆/\J7X擂d3#.bnyqev諚戰 P徴{`;聴9(蝠{F髫\艸/椣鮹蜘kau国K心偶/2Yk s軋|.m%2囚*l ^tyAЁg;}隕鳩-]汢/W @Chl`9]Z) $Z#k r脇杙陸啄f姑nёNX D]ﾎQj4&YYi~ (r1MO,.yU]BM綱%閹 昧{囑冓31RPh/M N/叡g#報Fｾ3諞4j}扁b> +/2'罍>Z3#瞽w(I9Q##rS(Use2}#5約L=^:星命5命俎 cMJO>],e寞勤5qClЪ{^} {)錮`^藐'"uGS(N#鈩cm埣h|f翔蔑?涌曠ON 6H]4d0!+w MJ1:#恨$m鯲Q犹nOuK7f1;乱%y透4?艾:l+~N輩N唱K]5T蓊~H 0鵑[&収$夛蝨rq"%#1Q 81貳b/si]k2`9kM{乍l.j)"1遅閏/(碍y zs7obW掣X-h閤莊X[ 株w%]1xSN檮g麩X[鯲R;0/8Nb\3怒v硼!凌/7杣yi??来0[6>fC3象|旙mc[<-zg6】:>!'艦眉粢3 澂亠}D$>囑P%o"1jX?e3n!0岫9R7泳s:匸l"sK03%逓w慱2q4l鵣*&AkSz'aeEF1Mツ&! d g9OY.y6G1瓩3$&c楳!RImi sbつzLnS渕1F@跫S仝Rm]tAゅR=OノJT肌P?qxx|E@壱Ix\~vR&;温vZS[F'9LBp瀝7医 鬥X-A冲o$4VF>)nycu4L#兎X>azG靨VJ羅N ke'\F#倶A^P+MZ,9pr7`/=W鱸猴~R <.0vn)>  s舛Ih6l,l$最N-".O &困S`Jsy_-桂|svSy)E${AS!yHMR lTdhv*>FI7s暫考gX 彰拯%k)滔v:2〉o.蛟8mixjKM&]j涵43k`"醂f近哭+WHENun菰%& (槫羆f1M 簓┓A]3&;騙衞dTS勦卸p煙貫(P#eu"A^4.揶uX-3Dq\j~ Gmルg$yu窕x畊旙N}u速噎%蘋 P棋rqkzt彖[)6;f愃e7-)Q=fFAN&6(EM噸鼡Fd'(r* 4-:uz翦.um 7 |縵X/W∴7p傷2[HGCD$ .)甘0k0#w[ 7f經ゐ`O揶征V|^wW2纂'1exWxi苗XZX/pc(X[T Jt sR干羶D#j|Y (OUz 0[|丱j)l9欣`極cE5D9W爼0ti9WA?7抽9&&}DnZsS8hqZm% H仔fRi9] 烝d^BL\Xx#EWi`鰊J5&mLu-ΧnH8 長4O臟}ugvN}5 S fw`X%*`V 鐃ddE置G6NJq3S~Qhd茖k亶無匳M伐飮p鰔D=\誄>6p:pFtu＠FBYsyp&~ }@P袢v)@甦U_h0C HF ``fjj5y4Qpk齦[+ u{Ｘ ^]sV{|\s呵Z▲休Cv舶J&9|7S8(_Ava` 屐-"&彙薀~#-k渣/O?(鉅秕r}ls`,G^:X68[n:{-'u a^0?瑾6b立lFR5Z廴徘疽@5;膂≡#]NSzq 8S={6{=Wb6V帶俔9怏yK }67;斧0(V{jゼ%-.Y&N*bu"Hy3l{9QN淵喩*AP!@Afl碍$返M1*&_ jR\[.景*TfDg譌bNsYiEY"s(Ue3C=4_+nD#;*ZnNs,`f"o52Of耗 z錦/] 3'Ep萍 猥蔗 xCg.^8繊C猥龠∞Np9亞'8z?iM3'M3l&c &善'謙?gN0gX=L3zXgb3炎歪 fb鳴?g6boc?)ocO04`Wi\=TSzXbL,<9艶H"飜誕#y3 a,,<9羂HLｂ淑-'8E93＄ir|)x= 6p=c嵒$辮y7寇Pk&d輟5~2劬 Mえia滲wmEh蝸赤嶐V%鎰umYb-5迭Av 9- 麦a{ c^-r*!Q沸lヮZ gK.| 2e7髦l8NW階PyDI*]rzj")苒+8耜T@)U 真,1_z/TQ7沁@D@Z貝]/B塚jx7T"QY%C<捻(Q=}a*: Q0"慰頭循理bH82w殺H\MNLP2c''(髭3貳=KB$弉gw`k 悒ac^&WlM路;紗釖)AWcqd{i*nl76afVv8=I@ 胃[E*$m|[ 芭]粧!FA弁:FH,O`y #< 7IX\]{サc鉈餡Y埔F`m羈It頚號汕${)~2B3-|Z2Dr!M恃藷,G)[i羸-Av\6搏xwY原^zB謂u払у S30ne‡2W\罵^QAn;o!%蛻gW擔 Hvg$&怛mePN~囑c3Q.Zes 帥覗&n蛯T萩 漉Lw瘢`N>區廃IrM\i7kkx凋s)M店0bvQ7)}欟蝙 Mzj:Vl,}D鰹籵 5eR豼6lCKL固SJQwZdk槙:B_M.deFJZa8i俐决ｌ-J&b(萓@S8>!甒x$\76(:B%8%gV>dOvYf4[勾榲磁xh\S~運h藺跏!佰怠鰈dv>##ivQqa七C 6!uΣZA@X_\&lmi=}g埋>&1@goe袗媒pj?設 襁冬Qf.=梅_f.朋rUn,^+$GT焚v;=P`{q2h[W婬_Zぜ=Kz慧g切 I&lfH礼:mnJ括|_h玉u&M-I碆仰M>hW4O<框M% C14旦E&-/ELT釡LW8J23柳 nOWp 謙'FI屬 榴:1RNE竭觜b#sA$+fw=5UE2fEaw奕:@eFm8N燐`Y?G`-G _K(!蚕}府~yy>xw 3 #ﾟ蠡^G `#懴 U抜 H (:孟SO]{#vvi}7z晁gh訟Dt|饌{Dl衷wQCYPzG坎Vx9\$2n利aJ#9CFv9bZ@I,K_$鑛#^c;4y_%*>q'((Dn zns&oJ抬J$? 櫪@!F|e / e&荒?_=yN髱2qU刻票&xa P籵+:~QAayJHﾋ氏壺Q&7jgws%(9壼go'`i *7QWq6.2^.-Y3r忙({予2牴cMi栗Q$!?ヘhz想m@碩給`iyセH'(CY1s(-r@E:>[T衞,M堡|`5i椒N6\玄f頡>;YfρnUw|iGXwi\oHm=/ 駲 %(mH 6}j嘛賁W.%'XgV薪AN嵬x 惆HG顧T]-h吠;際t#6 jbX0%e!zE65hx|*^n旙$/%瑙O>g遜 D6"/e[ $W9*h略!浄禅醯拡7- fY4`V3]H"".@徘q^蛇悉4[;恒s$_c|L'運r4取8DZeoS中ぐi給 cN.臓船b$ Lam鵜ZFtIHT展７$M3>wZ宕蕋k%ヨqE _c4`hX'Ε 羽Y;JovvsJ#xV簿0叨d淙鰄SXwLMu仔WVTQu0r録#f3W1=u髞k_3当kt凉z{Vkf(+_癒T' Wk6Egl]'2^3F傘0Saqyi[pyc屓a嶼催劫%'3妬幤哭v/>e7Gt/"S,~3幵@AXK┻(C鍵貘":;m`gQ<郷o"?*軣(OJD銛~0儚Y!?+ffk5XH9緬^%~e?a>霰c9Q C5QFELAo' q穢矜!禁 oOmB-注0f0.XLmxP}.\%sq迚-"3bF-J/RdAhf:楹rj[ =_ulmm1 雁tk,r遡攴I療:Fm{*：VV{  сI%奪#燠Wb訣Lf&Cc寸SVtZb'$ cokI8hUV7蜊V"昏UC9nOo%}h']:綉贅晃7hgИGgΚgrj^8型UFLI|nt遮橲]oT6fj道fgks嫋9""7<呈mJo日hNO#V,np.km誰TPD"胛叫JCS*JJv2 珪;n'ポ5e5rv怕留8NE/[pLA5惨VC*|U3\-fWa /7絛ADBH 4@"s'兌浜酎u于Y]Z路閠3\P頏-[eOtu:0謡eЫA+{x盧%3ulRg嘗欣kc)Ne V◎[:cJU3F8ht茴o陌-腓=惢l8g坪fO['('jaCヌ& *rL嘗Zz%,(况tckXoW6-HH嶢T0 祐|膏nW##G怺唐rA>*IJS W(『XH垜xsg背$婿齪亳}:4gぐbPP$( =BLoN(3Xwrk7|nn;ujI^c};:a-"q30)?nfDLbﾞ賺&M利萼2LXsb=f*<#]YP\q8s9莽崎u9XX439"54(~Z8u #bvb悁U^K2,+ nOQ}tOe,-嬰1q|g7tj熨蠡3 k1y;黨R|9;Pj殉 r5Ky}*次*7=# #fs,H_skh9粃6By\G滄A~)Tl]_ cQxYfI塊 |哮f&雌倩】%有.W;h{Sr球$繆fF籌m4ndC-s&1?瘴6;0d*}qu]96X \G.r8WlN8tR!m=i0ex,失R'f0au6&4b^a佶@B,澪 '{50?4Vp j*5]{Y枠<8Ez Φ4d蔔2!sU^9Ho錦@鞠I!軸m,`n W:C9lI>  P+d眦'CL7抖ZC:s淇V躙Dd(!eE5Q#"02Ii<-V泱rErDAED[W Q?@wk=腑,煦掲ZARm蔚"qe鶫.t-s佰@瓦B;9n6 I%i@`% H yね鬮壅硴6Yi&G孱1qu!l/L,?e4VftcnY S/\_]XXS領蚋,o,PMjrU馨艮47皿〜ZF駱P@0+Wo NKsK|錚)V[Ya椄Cz B.H8k`avaoV$gY投P~cs娩^xьHXl~繹xJ'?溶l閊'g檪gp∫m]0Tq^答4d 斯s鬆M流? !h諭S_2bDM zS朿y恍g+ 8U^轉|3s:mB+捐Y]VOa[秕n辜Ppm3#(VX_JcOLw&榁QtFR)^n5)P∀%*kdΓ傴金?.A霈2 mi鸚JIay)瑛Vk接先d+悒椴^胃7  2l6脂  l慚i7c82GDUV 2$;半^r"Hh"蒿旙r&2pL?藤#/\1 VmT捕c2rR&] K1&`瑩:Lp*==螺翳.=r & rdxrbN7KX豕N hhIJv>番#単袷+P>i_ >LB,WB癡V2>U[杼^>'m洵+gS罕臍g-n~灰 &H(ma6+% _Z濠瞭峩8{C扞硅譲mUhH.N=w1 VGJd[b硬座$q羆[r lH ^x垂2!+}流-釛g}2?Kz.|% 継K拵MEtp湿 潔_遅:gu什z廉\igkk*~8/5C (嗄>2tS4nhGuPv擯c\Hvuc: 1@`嚥%脯楓9i y.*<○江4 6h櫛PpFMZ純棒<GW',l)bo2  G?8'yD紵qeW!][*),gNt&Ψtmm#^5[>PLx<42孔hyL&U':&1bRE凪+浸d|e(}7(馼aY喝 3追E'c?AyhZlM } u┨Y2bぷp;東Ow,e)孑B~Ji莎乏詁5oYp:U;mdpj藩'#=依b0t,匸}9SU [Ikk仟瀛硴{4機眥輒v13F哀sdB ぇ&[x kwDS鐫XW@Mt' #$屶襖堤避ZI/征,kn:aSJI衫)Z絲个騷s[,mln{5lw$L蕈L=5;6o` >>*x]Zp$@8t貳~ t{JZ茗裏%8倶;C}饗,[痴讒]Mw}嘸Sfl'ae蚪<;0wuEcn励OH)\P?┼c/H+-j櫺g9H,:@tz)2;e,騁[!52[3:Bd%&yf(:@&iR*U灑E陝坎} m0>l并TH@&cJNI#√)0Sc蠡&s<~褞‘蕕系=5e晰n&1(SK bQtN!b2彁]晏g PE >~EkZ`A電I嘆7i+；梠bm讐/HXdtBZ熏Tm |[環J%$歃|徑n0萍Jr oC莪黷 L飢鱠b囮8聖紹1QKiEQdwt羝,jgfo,4/ ,{f}f# す"dpO  \M(n憂欧辧n R-4 ~<霙*x餌岱櫁u}"O?J害膸失P讃?pK14 cp)[N暉蹂誦KX5;{3LW(FB*,wOU*&$23醇cPT 亀_9[燻4/b-$$f;$.建L`7抻儻TiEx3Sq Ye CV #_管TsKLy詬KY-炮X頑R$)"\wk79t@YhrId-#G8兵H俐 tPkKu襠ｾdOёa K12[MqyUDgo`,灯!, <{+[d兇(Y#o^ ?-UCS枹^P"DdRuPEBN鷲'ﾙv峭 Eb A縁迭m9G杣&2争yCEZ.l.寢IM 軟YyJ冄O肢教5曖\|3袿!UKj9k ,dP栴.SNU%5]+|e`~訐鳫gSk比BD;刹褒~G|6m"n突:c]sf^捍萬z磑`ヂ葯*t) 陸s~Y5s檜EW>儘A展呱r :2箇 '!} H8sku6`O~Dvw~P>gQ} d>逃Hj#SFhY阮詬槎J抑 7蟠2#o^G雁A?m^WW巣H]雍Ne2\畚_]W)<FH+籏邸 xz=慥粹B籌窮&vl1D^Qcv ~EyPq-%^n怒早5c~i⊃Hv,k&WO2K<敍"櫻\^AV &@J.~` 価 *e3OVX未IZ+xacs7zaa=%蹕cCZ1s+J崑6也婿~!L Ku~%aF慱7R+mb"oJzCB:`e,.咲V?!lutzt謳樔I[V諱GY\(Qo.S2}2s(痔XjzT鯔(g B庸1}n?油.*J)XBsH JBjhr@駒^6浅 t9R坏9$p Yd.=i7Kks貌]貢M?,8ag柬Ad_ ?}$*TT\s@3艮T{ｳ√cVa劍嗇K)!};R 衛Hb蚪y}$C霰Р邁OC=lTf裲$-;{勤94>wDg夫K霊H;zw髴J}@L^?t?S$'pch6oの栞a[s84G \&mnb災jnn媚袵PYo~e>n真蚶wNq#ugｴwjrS持瞬0時y,駁}b鈕{Rf壥 紊[%*敲顧j)&nT+齠#X陀-A^蝌s.]bmX惴唆Z[^G>脾惘s~ 恣驥稾E孜fD反u__ I3潅]-0.eGer嚥x-U遏[Z]Г挿GUaRKw塰皷K 籟MAy4e( pOgN鶴罸pyF@霙v髯 !gn%_FX8f@K858mH壜羽SA['w穩Dj6j洲%E)q付〉t軅~墳`Y届q扎{粟R|xH(N ~w044# ^0筆Tы%^＜}VUP&2CMI林媚gE.#培\Or鶴e違a!4Af街#J{(A2'1o綫Cr.坩^):TWk恚¨]Q＊嚀 o實5[u邸`~/B2學u霾ZL咒E4柏宋sz!Y= N,X豌i: e'WEcA9%'XF蕷｜E MtAc,L.U1:A*@L典K ∬`nW誄偕 @%g~崖oY齣^n]]DH8jC#)U艤Nc溢2悁~}RN3款f;MRukqq~~8蚌m邊iN&>劭nm&u3c6RЪ霆X┿/^_;g>竍$O 3[`"`竢nn\nWT蟄z@JT7ab!E$Z<饉BgDr.z､3o[蛙D幻8RZ恂Y1黥!MS ,沃Md=MD7|W Ex dh'hV2 U廛贇])8}0 hSBr溌與Kp2\_mDPp*-籬^L買Rk,Y^遖1UjHNJ@4KIV+∽g(a`60莎nt\擔2}T(prC0甅榛M~ｚdy|$`勣/~Ih伴 Whd!$r||L布UL~V･aE鯢h"暗uM論'FZd1!H`z箇R`58%J[AvLcO :[y耀r鍍廉BTr町m_OEce輯fN[=%罧CY,佯 =哥賄Z! s墻jA;奏 Liu *先媽MF 9od}1R-qq7[P\捩@片3b''b>2!*習`T-<[j=fR秘90[ 喘餉D))|黠遺sbD:5;越4h'bU*-$K俣%vM[NO爺?R沛:T^#$忠圀%>圍Qdj&糜Er悩陶 w,C|$=&am$ 廊9噺z雎5\-柚 BB-#\{epc>w#J& 凹D>FN';侯g( >q 0銅B~vu$舛JVHZbW|<ku|H K儕zv-Kb丙>dkSk 7芫觀V&#隻6_/ L_gT}蛹掖:}q)E7虎[&E\ -~9Q鐶愛@\Jl#+I-6r鈍I2qsE8}鑽迺 4q9ad~n.,G?\ 3婆} H倬eS^%77R4ねxM ]礪tjx惨V~COW4+u7貰$佩羲願W岳zW+ПLj唖すdwsN4mGw降蕁`亠>c;+蕘/ね>E(OLa$)5@'*3羶TY+OH逑7Bpgz[s笳団s觴'%02茸D =滴凜縉* :w瘡鼇^>?i3j d iヨ|h)Wr3K|L`瀞又sJ%K▲s,5筮JeuZw8冫dQa4hqu*^8! fg*v琵嶐 ru:s罍u_NO欒dKC9M8X~Dk*zq繊C'8願:}CЫC/f,<槇wd(<9鵝H>L#^ K輪截C柊癇3M6?輛8kSx3.cuDI$葭N) z&}!hJ?連Obss-5#竅V┃E9ユxQ杙}$Q忻Fa-ラ=bb淦9b>b&礼aJぞfH--LC逞l7l,摧Zx\懿癩nX La4QNH7;;^赴濺%齲暸DD｡ч棣] 累q=gp開 >h6 M;[I\!5恃y8M儁8Wn\~頴K!CW$08H6o>瀰ON |fU(fd3lg傳klVA稀ft3 sm7'Ig稔XU?1nﾔ0碣l他z/RY|) G\Y$O〈}鉈xmevu4$M帰QDJT卿澪d7Ny@:dK(@5{0I汳0W ;E2 鳥可|v E)r售f癰;&@l"\2}R=]Ov+計_E9Sufz^.圻乾"B%*tZ 4@H2域) y+E続"m9^E w-a\疂'D;mA琴1諄'QMp}檠 ] uuw=FhIq  YX7B噸q陂 aE鷲vZKd$FHvZ檎S&Dk騒QﾋX 5"ZL'O\5{凧wd>Ny_楚 臼 5q\r:+Wt−ょE4s'眸tk章纒萪A[困 J[Ν i(peケz[6vhT3?仙#MY_t密j+&\B>螻\Enyr5 `[ qN< bzo |( E梛Hj^GK餌Q]):}看#bJzakvq oqΙ3p冖[u4$Q$.@[KV4?俑gEI/.# L6?mZJ{m経+HOp1}澂『V傾成tg凧讚5m友Hfn! l! ┨?Q#m)_a衷ilFz@E毳覺┼橸q(n$Z(ペO5逋DFh#`tCyvV]jKngVYKz枉Ywhf,Z鋪GY,峡^.S(i2Q 4$s_|Kf邯紮 廟1エ納笋k呪 rI2`頭x#H麓圄皈qdT咸'nL?o紕散#>Y倡 dM'w *jP=CFBk]yD}SDs$A$%Q拙\gvqR略3Q mq'jQ塚e x窗^OqTk<模<」z+6<<巳(?婉湧Y[IbiyUz狒u]@N?%\h$FB瓷9３ v冠R!判6FTM98! 暑w]s%W廰'zx悗肛,`Za 惆V孟闇JSL8*R[X[>p蘗]*L0\)?寃啀臺2e菲?5<]-JKwUhs,Pg爵ty,Wr}j@XRS&0UW[Y盤,哉裏GnQ!( v灣Y]EA1"~?Gゎp*j~:@<怦"DPIkK[M5y613=晋P..O泡功iS]AM仭D;aげVC|Hn K27qeH=x$n4C?5歪jV菽zTh|d&!pF畊^ SCC(]i/ w'Jp鈞nvgddbA2(mz尊YS<:' 7?t)Xo.蒟n1FA{y参pP幗}熊'rjn&\Ц攵陛:8~uT酳{檪oz(Hlq3聶 *覧贈1\B-7a D|0hcZxQ%n 8xtj,暎u-?]CJa4~塩f}W砺歳o06ts粒(|!" 川Y+Pn 0Ftr}N@TFmY^"X〒崗gY:%] 侈Qj;#&4Q?晄磚)遡?:j35!T"g Sq[mnih9L#シ1D'虔GM`6ERT&品HK [AJE2,=9^骭3+=v)ho鉚.蔡Xo8CXｬ^[aJ綢T`1GYQh4uW-HP諛f89檳NJrb彜 q[/l7假$hsy 4W:m ざ柁興f鹿6r35@``jeQ +嚴悪*F珎^ 忌Ck68{:,}04.&2=O9AYrcs%#~p児$UｬZ嶐VPe t,lqdNd,cvcw2O&¶Cd'.;l#=i嘲7_a&oE685ィ鑢nwpc光髣]巻iFa/qFy椛 q%荵?ぁ#W弍g|}鴬[L鳰N帳% X\6-飲|h鴨 ?{;!ql8WaA*h擬%8dPK .|91茅貪9講7rC+Uyd踉隋#&8竜u1X87]焔H&84`5V;uB欹X$2g5%w絃4_鍋?矛6 s)Pip z*^J Q釘bmp膠;CQR S> Z歉dq6CvG 昊護=賊癬c*+H(i +{M垢t團,w1 M％#T[霑kzdza8mm巵 ct爿塊O/U$_o鍛qm}<嗾C4ァsS黷hs)& 5rq峩e.P砧苦_OU_' Ol囂LI覃nZ|v牧‰耀a姿RH9Vh3uIx!;5+l./aVEbnY1b8rGvmQJ(BCwvt桙/瞻9GUぉL/N/>Q<8Y>2埀{嶂("\B\(6GIR1t`詬PVMA騫}Mn2*hq:8蒿 竄Kgvm .* [第f\笑懦鄒0$Te&| ?9<蛻e PRz@a陀1畸ZC@qJH:kV7 >確0'mlyA ><ｘ岬"5}{{sr!-hOV46MfM' 偈jj<苪醺常Cm#H<8P犲;F,X懼庄b^ #G9(r1j W菰@g0gz&*k嘶m済RFY崖X#E08 鑼 hg準簿x]; 腰帯qv* QYYb!癇rRI:L退6筌 \%Z侠WC宛LZ廼,oWUZI&抱&upg豌|紳弾gCOY(7鬟Et裔R?e媾,v刔HO_ly\h U\z%慧V費D^>' @G9p}j;Z> ,揉<92囿R┴q$ l{^引6JslDe_1NV^ Uqj8Bcg,03G進捲sDubi4}dWlxO 踪愡H俛8NxZ)igeﾙ Q+Wx贍雲C咤Rg讖5h|spS^徇┘&SKR21B蘯悶-%鄭b)\━t鰍n*C+'8WzTgA^Z6kil4+OSo`x華#)箱Lqi!a Wh)%- OYb=O;mgS!JU +~C>: 5:H0?8虔TS?mj殴S.m)h感)K1 Tlk隶O0 ME_G*c!1 H48{茵!GZ歙)[J~W庁N/薬xaWlP8-udE,)!桾f#k愀;eu.?80Db-S J0?灼zDO\E歹J坎r7EqP筧 $T9岬+YNt,殃N0  也n7桐敵惴3k齠)pj粭Rk' ~集Mj浸TmRiQ衿WJt尭a&Uu:E37k|'q~]m犠 福*V4趣貫aA 櫨-圃o,)A'8b\gT m]か\b}0;!m L][X+Mm01,靖亶▲段Go 9Hqd$bgXQg2.Ed+N4記麸Bcq@H34r%mX~Nk5R1{SK(}3&#QYRNeMY>5忤ｙW 志~膜 >D,<8Sm堆+7gG\J驤r宀襃j% 壁bpl5+Oべ^]]: X|b葆B馥aN覿+iFΡlc$=鴎sy:"1Mp DKR匠 ^q~r\洗UXuc{`yox偖 eHj=k>萪3`Aeo悖{ehXv$侠J$Ig襪6dN粗O,],H届p從z zE[ 矍割,GF NQVt6h:bL8> K鯣b&C0- +妹-e腋$eCm= qh33宦 2ap"JQ*寃@1sNUz\:b琬堀8gy燬綜鑒b*\骨O::;^zR┗嵐冓Tz&i6蠅?5翅萄ek俐強m佼領\9濆y嚔\v+\W-c>LQc^d ".eE&#瓜D坿c>\捏廷玻Yz|,3┘` {簽hP柄4鷯5A癆Fg8;/E栴>x驢;弖_戛87葢_xnD鴟w蒂y雌,L舁［s气('fc3択<}x`R_nn0タ|K舂+7eg@3 5k(詢G臺桶1櫃K^靤aho\y％4xｓ?杉/7o@乖k]WuX*FTj濳躓┥☆鑑荒yWaQ;8!!6;躾滌裂9柑0&8mb喟& め笆担_;?2(噺I+W>3::67燿SzDj燗?%Zs隘{Bkd瘋炭r窩?[/wn酒塾/,W壱ly狛b\iN_肺;玄`&y/ 穃k髮4貔0i5e馮蛍Q湾z繿Cu炯e;_E龠Oxs譎閭Qx nO疥|棋=愨愍7馭;/穰?S6W6哭p:歉vG td\?$([檮=W權~V糧酷0x:Hc棋|韃霤/:wbH;yvG[L6^T釧[I映P:_Gj眦^R3QIN 侭砧緯7:/8}遠 - '?b-泳wn莵} \JuU-/Kg.);t黐稽un頗e :z紹蒂qW訊pノK0"?みi仄OS睾[ /w`lo<持>齎 X+0g:;7%=7厚<^_Z'派2Q%|,L6忻c舂 U甕>>Mclqx_~ ?"4W濘 譚k[?vnj: 尤zs.謀K\FHs-榲tSY0:gP l-星MG8@;葆a~栫ax|`Y'^P '致~戴h \} +>z(5壬"k[籵要~- ^樹 b+y臚 _慈_鎗wo, M*Se`!zW\7朽PC嫌: 7r Fm y嘘c&29;A-]%%r?[js麓rO(t〕tD$l膰mХ:]Lm l疹俳盂u$k v黐on S権xq0~o~s轤/W^{.F又D Qg彗U|o#aS wUO1g睾蛭┸o‖(|b j孕S悠oK(>7_-K\v96 +! __}B $f\,>勲_\$晋"9F4R d~$ФP}CH^sPbpju溂gs顫螯I N)}r8 g忽酷W徊?y譎x蜍榑;/儒/p" 霓WV罌xx ~恪囘C悍 Hxq"舶H;/_ot擬ю埃RgX轆yK!吏 8.QB h.腫,橄qpw/峭吃W衙X^? \+尋wDt<id.0L 飜q伝4K2g98`_@材Y ﾏ.?~osB WびZ葹圦轉@. H4c禊`cB^&X7^m_.Qg: 樗U yc_筍y%雀釼囀?Cざ:d?c謳^hqo誠\s{.循{|n郷B奧迯Gg:n@啗D6S:首s_ぱ|朷畭) (,<,舂%曾⇒e曄/w^7?B9e6Rj*2& 5謄s;;vv明厩(z踏cY;大w郤6酬>9Z憺~ v姉ulo%俐]7Sn,fKSハk⇔3zuuj励麟黷酷#h/xU:俺u/*[,*淤古Lyxm&Zw+C愽;)\ WcER;饕[? E+侖t淹v臟\xX3ZU&WXVF?[!w\{uO?C魘o)-A~ #冊(k =TL+%RmjGW#+軒慕 Qo#{]Sv P徘煌L:V`Q5Tdabv%h\eEtiY$2_ g0"l)>*#蕷7ee_K[?野n殳4桝s怡|q肚S琲瓲3IMw{欖"執r藜;$t泌WP`di a(@]褄閠EL7hE:賍yk蔵\hR1"ks'xs{)94Th叔z>恚bB♪%KiLht算%鳧鐚:Z;匐活;ptbC諚8w浚r禹s謐鋒~M鷦Jx樶酷W~獪嶢鑰K,[2窈潜疉鱆 { ?~?<~| x\K0E!^/`懣2O騙J,Q苳w閣J][粲v!Y}g劉X'IA9 ｗE->I&〒F UW,キj縒6h!Rt``0=o弗 ]TY5R"N\ 7v\R"JS渤5倫/ゲmCf/G姚拾隷圸欸'dA襖+ S鰭餃!I冖szF4d輝vW悠 舟"2^b+69y7黙YPZ°s&]柔w!%\@dVHOq同M:[A邯Vc=e-忙御 L%:簫前=%i狠FかcYB&冊[,Z3lW為PL.@4nnaandqり F'4Vl9"Pe茣Eea@珠 [W=(垰rG鼡6A徴讖w鼎oD~鵐s/頗A声 埠倅きc8|n腟~禹俔{1^9-qC~*[n>u袤墨x濮w%;7}氣霹q?@材唖謦?uv梟a竅H); s疸|URU3)[喞D質mu?a[a}^xfyh跂_L営國Tm0{m峺NC:w黎s{藷%WvA歔(ζx l4w^(is艷%Y寳CO 鰄l斤|拆1nｻ噂s!頁gc"KBvO'窒>e翌L3\ovwUI黌a*zI}LLXno-A9*斃)*E甸 $.?(B HQSZFyWzEk(%O jU匁 8RuOP^7L s7┘QFZk#r蓚;Y頽Q:hUo ]~)!6]50\f++Y/>|:||=x`zP−;$K遘;J&0t1kWZFa NCnf":0TP )a 祀},FPL仰+9驫s!^f&ZJV>8KASw@9Fr葎PWblj負固xCzS鰆稔{j96v`&qIh掙(P)N%"鰄玩ＷOO#郛-h%櫁TX>iN8EHf賭pJ#慇逖!"$)Im叟 ja控mp.P礁暝-!<e%e|byf8Z]'5LtoBu+Exhu稿)]猷5+: 5vmP%^,[.prR1 1 O8K!K坑舂_[ ^\序!:;7uW;_'〃呈b<丗cq]齔R石^_iA[艪●XX(f餃s~%ﾂ6ViC&"`WO]!}"<-TjOGf e９"(/$^^85f&yTF kE＾謁西仇R}笛益1t^衛%顰令孛OgけE鱶XDo綰LkcVH土4"=4e9航z|"鞏>|!-!BlU \:R.yR蛾2,. l~DMH0%bS 1R N5∃w%知nvjsG)T}P;8衂tB4縒l咀X_Cc鋰ZVI叺<(e<匡gH<2舂o?-; 磐Kck8S1!G7L\_JR,Pu7u酢悍c|iHf{9[-雰屶氷O.v8_Eu齊.拆Zf箱r YkDY!8D鮒儡JYh%kG(Di賽3\Dt袍Vg仄<;杤翦Z甫Z"{|Tx|>pqI{o獗VVrh}:;申s]Ju鰊Dp譎v~輕x晤鰥:|惺$o妹0 n"ンS-繖9Njж"P峰[*Q弉C`n\n@靫p媛V飆#ｲΨI YfjPi栢rB-]vq~0^ ],+"g***me)客火?拆 Y>bu}ny+D~W諍倍(|+6g:^R`Ws]磚/a阨 =>r楕[ΧIC2=点ut *uM `xN膣]W!RM#ざrW$* 璢[Bfs(礬耳E5*瞥z{FZィx/7亰澱盪tJEC&Y7~+cs\駄Pq`~uA賊映H[m3LSa 点5XtTJQ)g￥NN採皖鯣C_?3駈3c僭釧##K|硲>D>(;瑳 %咳cKY?T×*+o/=[>*==LDu>m80i1}儔A)r囁C4唄蜀RＦJf), Z8\雎´V0Z2賀=PBtvBj嵳驅ﾃO=W淙音1w}=2J時tg噪3]廉F H?菰$ ~;z:sfW"_…霞^耕估'^ p@+ u)!Y揮爬o獏異tzQZP\Q毛 i .-0o)`dU pBpD97'暖DJKp =`:_価h緊RqldXP洽Cz Sj硝tXF?L宮Ihr;K?#=o8776鱆}oP阨#b`jyP{/jCqb札GL+?&珩58v e}|黯zuB浙/f{kF_;"崢[懺_W rut1<>t;Of&n s S_5X籟Vf!B u*庶Dd"`B|&擣Lm!ipe,pY2H!┐ぬ#!,B'OjUr痙v[K.n_3ﾓ携A8j瘋K7r冲.(-HIl棹x3N h+A舖@{H ZG6(QM┫$n_j粭Z孕h詰t"n簍+ 迎參[.{h>p,j@8S舒@;R%i`rM]qｦkn)`nZxQlqsR1R瞰:;T蜉 抜8 v鑄 Myh#DM4-!T{虫@N/析a刎rfnr)劫T2`^>l赴恭/N賦QF#廴v酒E!HB蒂y襷H/6ie@LlLU{tM];浅ys}+DIw1+硫謀 Z濁驟ざ蜊#;)}e3&\O!7G W=r8'R `j翊r武U塀Lr ZEITZ肚_|H Bm c*靤rr瘁Yghn \{q:"榑%\3_{藻#~F9o*|wr匣=狙５a絵6P7isP粘G迪d,碯[[ZN&Yh9csPQIBkWH 霞2c{"d佶W:L躙UK朮剞eSqA5摺O^K 6\W0E)"g(2 勣"O{Ez踐v躓jo拿 O例-}* 畧Yc"ыT+{冱IYU^y-嚴k榴*aSm;k2rMun濆vj/vFE+B? 剱t;Q:> `m ! Ｘ)m,ZP.q(躅OB6ｲc&KQk粫務4晴7M犹jDMt*g6"從ZkjN魴坤奧|J= :uTT鏡$_hY36媛N繧Ev}hcw甚u&J~vhh系彰 綵BェMO是,n ]X蟲Mun%AJplGZ&/*泝aNb愼7`ja併。(v;赳&!Cq j鯀恁"|,3' CySfUdZ(Tq8<Ve ^札8珞簿\(7{X波{i彡i!& MXKI88jD俤扁 %]\N税:,C龍ngvq豎箏}=覊Gc02Q&rdO#)Z@jT =l"+祗%LYlb's+ YT-S址xwt//堕emA逃]da>}Y}-@:_>fR鮭P"%R綬ylぺN)f62NEx9|r77(%誂匕/匂π,QJ.^R 簔B=z鎧iL}5v ~网D 'xq-R(0BrmTtd,cQ>eZ坩Ea`6DAb喞%4罷b:c痴w飭2}2YKZ孱3TEM皆詞)移兄[:'62$鮒cr抻j}4琩G .= 執;,rt9FC Cdv/昏Avn V殘p7j"-8秧齠}琺\k Ec蚪`gMU辿U_堂vQ憇rug(IbA濔5_lqW=Gs3稘rdpmQ_-x$ 渇澀P {5{-Mns粛 Me脚h-I蟀q3Q蒔d窟"iaa\>\`QL;3G溝怩etLk*aG勗n~]qs8壇!l~由aWj菜Nee轤<  6hq箟嶄c 菟tH頓 m*dA8A∬L53JIRr威<~l#r2Z}z1\QI(藍X^К\!A 3 ｈ嘩Z#@w&'!@犖 ay`!\Kz]lXr^0Z&臭z~祢X氈OV頑sk 9c<辛%uXhQ所\@r`&'nH凅[E^zbzU%ド@s-;ZblU矣l８u芳K卸Rb衝ksq-f@必NBZ3iZ?瞶-,Ｅ測宝 0汨0]!)zh睾ポeKzWnJgRaKR3.(z4cipNh<,\b#OH-fe0?1*6猝N &yx;{(魄yI_m? Srfえｪ NR臚wUL#hR 蠕}齶[@8Rb+0K_F鶺jc.NVM'MViO7<ﾌ荷煌[T`2獗莫4m2DJOC恆`<{wHMouM(p彪鷂#bXG]o凱6えY%紜 D:?;oP7厰Hi*=%9;{)S%P}8記] 2:g2?j64ｩGZS6;gf3W)%.9暴俣対BOR攘f帽`)FQ"ruZ37次]NAa坂X疥Ms$I[往夾lRRWt+Ncc轍Nn貰L4r;'4司汕[[]du]粟++Π21`:@\{rf FN/o2pt鬪= ﾍrjW于淤:f&勢,^E%lDp汳t胥uC袙bEztP=(~(4g$u"F "ZYr4x吊T秤SIZ/r$>S禀mV%"]b$.X9nIp#-1p2ddjd`J|fCy胄xO%"菌 V{ M:>Q竿駈o++PE天+ii4T┃F@qM\f蕭≪@R#~ZwZD△g);aihxN k Z L簔r杞F6%ef\[&O&膃 贇]Ob#jH=ik]5-2yBl區.G^2hTSt1FA 搭FMR'變7)U蜍!虹eV崑cD綯iiT把Su 繩 OI1Wc!\秣5"vBD`$EW"?(QU'K&vOVJ# C@晞U*6Dy&$滂,帖V&-Z f4ND滑N @ ^YJ邃P'% t[lC坿$貊K焚R-b9'賭田頂鎬+IQ8U TQBlRQ%谿#-N[*T/"nwgQPP昜5v$玳/g成ザ;7#A22|!,@Y 餤E|'移2->4\_r$OUb%i\λ*9eHKBG9]鬮勉滋2廴w,6桾lO@6@et`4*$7噬¶t>$&=$UCSza*P賊@^駱p陝!%L宅 |壇sR菊汰k=棠\@A[搭l2翡徐7/榕t9\-y芫 &8bnmoi遽虧r:66swv驕惚E $掛?A\\j8嗤3ve2:sN).-B`}稱? 辞H l鬪m:^8 ャ裃)C唸邊+R s嶼_[闢[aVoS~戦lym＿呼d_w君駿iL 主v_檣c鉅鋌+~壟\& 漾F5~} 諚mz 檄u臑cLOM 7p槽D$莱+:>~^B[嫩週`c4 I"{jJ:菽 繧椽c毯4*wtfZz哉篦瞽沢la莉eUmLM-&in ~3纖(奐-{{Po釉椎h釉悳赳賁槐jkxatc喬丱阨h:gr~jvtOk>O|^X*X芝争nsii儼]={ むJ l9D粗d麺sfn9]tskw[w簗てS2c宮}S:gfcw;GHsvPLｏ.TC(E%蛾痺刔z$\篤! 因,1MlNO慘C,J-'謇映6$%K國@,--[u7$*u2,D_G a%nA4ZA榊d ' 梹fwN(8qxmmC3$m(=5-. 5)c#M1Teb(o田 D芋:E \Od^甄l(]5KQ5mTN猫x馘W$\R#Т%SzGVv"T]~豼):`%|# KFQZnL1H4BiJ6tcZko虹櫺K}3f疋у4圍hy .u剣!so%絋Pj奕摯XwY,EJ\G蔀*W#2^} o_~蕾Q4Mv-B&FEfE&|皖.冗!6闘c HFDZ@z8;季YYETV惺f燮=pn暮hhj甄o周ZF?iltt~_惺u饕7色逆wP臍貨s7湍39}A尖趨s5T]!絡IJTV~/:勲情N&麹B9╂ >2Z供塙熏0K躾\D?+ 'W冕xK卜Got~t蜃_b蠢v榛V7&酉An|t輙W?定/M-舂4ux4蕘}[x dДN檐1Ty鯰/|g[T:$餽Fu@;7/]醸g遉v-逮?jS){K]:晁_~絆;:]:jy羇y(ペP?巛)ewz6?輳!|6 }$2EQ\\Ng臺x5o&_S8h黶ONoc_=忸Qa庠Jy覗A-T%"1iwx示wr|6綟衙孫碌攝?Xn 溶g恥J^W38Xv^vN1桓l0匿^ 醐?;>w」V覽t僥泛kc4gp艷gp雖Eax5V訪KGg蘋p ]L醵{.uz菴!蠏簑辞7L掲2嗣V_悳EKq;bg毀*HvzI'笊♭h瞭keQ ,[ヮJ0晩,USV霊S R}}xw耐幅~T7-zZY寞曼AQE?纐l9書贊FR=bx己h_E@iXaH%７ mQ#矢)"TIpF&Z|K y#-d~i4wpKi@滲sqY'内zoi&鉅+ `叛w^&>h;k'}cX# ^z?Ysz涌.:諫Q亊hE~"^cOs_た評3v^児k`mRc塢1>W\X]* 敢錙爐繚de&Z衆K躬驂w~亶=F革.O[T-C}3J峙厶飢zZY_R嗇V苴簓?T靼K?{_4薯dLs?TDp麕W~燈TLTEvP2lGPl :nnLH(f%WVI;遠PwaqBS禅S&_喙o是/樽g-[舂:竟afM?ec鐐O!]s0栴mXhM=詛?&T7塹G|迢/周kV/o楙xeW.杖&f0鷺PSLe:Tx斑u5y\鈑(歙R喘V6I'靫O連';捧,-ys@YplTВ5,憺#夊5$LQ<債j4ｕU}つR-3~mcP[&*,忰(}0{p殖凛+~}k/xZYbp胤 喪t膈yN/3oU?H7H/upkRy h]-x鰾萓SO}擘]糀悒Ro)C喇jhn痲z攴u;=Ii:;燧,四繪^xK? V+?dbA T]_Q9eavs櫪榮oz_u捗\募*GaqK;zfC2E"r倏}濮韭x 艟sq|QW9~34(_Creレ}c咸K@\麁O轄%(Nr cfr e6Fs÷r瘴cp悖ﾁ荊$]E 1h+袗/mA<２綟r }@鍛EJJ>x蔆p>$奮536F_赧? 5*瘉庄臼甕E!`Mij 22x #SHcJ甸櫪I*VO彑"櫞藥CJヱT造XW1|WB)Jhl t t#7h"KxZ(mq剋 d/N j斬 V-座5聲aB>85M蕗∽X文* BSsXN $shshRk ｲOj_m`枕*ρE}B 4o"濆ZL@]D走{:;Nq0幾兵凋y<6从A#i狷僣P2eAnUUv04麒3|頒g)膠珞muua9[。煎1tatu(ЩB899奨>a笂%-*00:Za4FwKU譫DKsZ[mH\;們u h椒+ "FBあ菘イam%P邵t- jx子4兢 D柔Nk(`DXY,( ]9UV;jdN@( 瞎Jぉ^暇j.EH-y靼(cIB`SS+漂dA 堪鮒[Fu純榎trYp揺Cq8z*C9#|7u銜┃;g tGVPVfz楡pR9&k祷PFL&$59{_均F]┘BU'[ aQ栃&xyI-1b03 駐EM|6 ,點pRldrRpq-綰Hd厖[ #SGFCia="- iθO Wm `髻vKarM P#^=%"呟q\年[9HW_a$>2 -I,O73g*gfi,!N4CC澹fn筵冤p*h┳Zq辺`^]V,誨$:5 甲5iu9+&l_\痢3d,XwZGz是M@Ct:9IsSe g'J鵐rxxf=Q> 'J纖航 NL q姉e}后pb單溝d8ph4悼rQ N氓6/膝Ba奴善畢=dv ¢@ 9_! hvlC:jjEE>.AV治 W枳>会I u1~zRi7i{繋'x穩U湮 RnBdZq$<ux Z^eF^k9$凰GK,F紀iB$χ畠c.oj 2hk$).延E夢9X_L1l粧J|痣VT*CI蘰 粥%BpＧG艨冠 [D dI旡#UrIfn V -Nd.'wQg我H1E "鶉 )Y0袴51T#G静YX.ｰ Bgfs i0qJZ 慰揶`Xt沢pe屋元MF+:"D態5B~\YURt駐Uj(*"ancSsA>>]j43検GKMEi媛H膃C醢>Jl*g>K 4鎔}d駲euv_HR/N cu0n&P(dLXm IsdvU2a.a|檀lk9pLK菽;%e拜 還XJEFoVO碼柱c"}稽gd 2*6礙I!#;4a3'\薫IuIB2+bRS"qS駲VY莱4x骨典^ge'.憮r=;M-7'CK"齏\=fL 鄭#bOg+7衄Z"Aj欹 牲Mfv$9H=Qp1~[n/)眇 友86eCAX%(:fw ―O閃 俶zd{kw{wR|再vO)!dzi(Ezt.L H3ET k堵04F5u`GU&粐q6>V lk>E!+"艨$=  3kWDI2I0+}屏/{xA OI""5Yl8B裴spKG@XH.h"9鎰#k7ZG丙 h{Dr7 xHtH-<"sDG5usM'5_O,&辧hAn現科k赴澣*)啣/8t?Ejw`S6 ,lu-VA994陥L& SdE周 dFb,`BupD8|=糊c5都tb%WjＮ`DCUQW踪 X尨 1Aov2(O!瞠FBl畆wkc再Iv 麌jC篦%X _LR膺VΝ.鳰挈|z+I-(T(xV也_4,[Tgm.W!$}ノ8%∵Q喫< &lP0拇)Z,隰栄-`Bc丿VuTFP|柧@B0hбA\'盈v)Lsi1姻&a&!FDZi殿股vm暑mw\*T!d=Gi}'q/wf(ls~a'gAO&< Rw椋4;^R#$+XgW"B;jJ&澹I^}2 u杏m4FU⌒^[ U蒜gl,全r)$煦TM{繹VV=@ujΜ:GaSy8}-6xx 5{cPH6sJC髫 截 I $U_b匙J飯I壱洋皇_e0>rFP?iS]V滄}bEk1^SLjUＩ, ﾑ& Ο4o}3袒1gT~VMk#KpK10⊆$Nblbx1=+麺O(&ｭtv b8領+Lゲr疚phaH1繙Xn}k ]<>_gsSyh輟0; cpp vx|8;戳lX S/`txl4_>B \虍劔韆問Dqｼ|Gw聿Krx4N袵B=0+Y彙秤OO'raDM砅飽^1疔咄簑ga`n0咸ZUV瑣|Pi]∀驕哄4tAdΡ07;S. %+ @s /1UЛ魘YW=9UN這KOCI荀0U/腕MN單qoaDX.=YulzW詫a+32M9)>`azg;W',`#pp1s!sT0L8U8.'0杵{.TY84kpSa@pAp& S#r._\X-跿$ 棕-.HX軣9-[gmZ葮o陷畊)aN !=T漬siX/P髑9\Xkh pJ售)sinB(Z苣p40uXBlu畔C9:a0t5~Tv/t鉈(l邸"+L8>R ;5 k["P[U聯??]g歡I+椦4+ 8gLPG濳&/t9|m咳oこ k 6+ b" b吮ず簀\LA顆X=t>蓬3 }禮1u{ l8屎鮴G6 m D濤3g猪dAU_Sd)dQqd$H'@fs6( hpI攅f:PR柄.\A8R:? {<樞klRGk 3戦L姐蝿1 $lE=Yg槎2Y懲*mdY$VhV gs摘Kx:驕 4)jА$x蜷0y|圧Zc%光 1ekl即b收5 X$HQ#QcM汾NqFhbLLbV )悩Zikc0CdO46嬪z匠KC~2〇\mCp丙 h#G古)GD#Jf|!-~*с&>x忤Qｇ痲o騨l垠rw佑F.|C4Q1iO&iTIb3j<^'唖M^L6mz 甘*Y瞬C簿L瓰<K落儔4dLK6鵯 ?~2Cl,.1&MtQ$眷K #4@B $A; 盞w(6t(?/58G}t/F傳w`夐]A0 NWX戒仍 )+=;R \w Msν`w&gZ$w y+<%q銚'%WG%^s$rfm牲]9狭.~DL.|j6ei岳;雨tKJ|Q慾^Y燥L萸"#r&~善BjyUE倒mJEyBw寝斧Q X]\臘1CA KC8v{w 4nK肖cp]|'j/|'貼<EQ英$rO0$R悋f2S d5BF| > ^惑} Kr~BjOkU^gl罷療 0宇J4)殖7櫑.C64f輛M(=W{H8V!*Xma_4Ym=穐GfdY&RwsIi]n讓  J匳pj突J |PU&#L<5ZS]Hm,^\u0~.X]I樺a^ Z2:荘Yr蜂p笋{BYy穩,&Gk+- .)T+2C3焔<:塔uP 1-!& 6F!QkW"紿I)] T'⊆5c y_P _ap-腆ZzHY,z|:lz,j?$ J{_狽]88>;m~pD勵欒l註DX勤拗>谿l62F沛 !y0Mt仰"AnFq>区] G GAO&z戰|[k さノ習乃莎R1-n|+*IへJ82WF髟!SR嶬界!V= 70] .弯#懆%, a%誠J EvjTf諤*Z8rY<`h 帆+gR顆兆[#Hxu-∵X+vH&6uY赭#K52==D!"&}kA6 笛2voj}uWzHd t0F.6#sC&6唯 &kCwkx9 Q格@競9彌棠0a}躋 &豪Hd?raS Gbc 斈873`oO@y B輊+XSIT:;}u冠ズ左JlA搨倶zb/SFX^M/S槝u5OYWwtIyZ膓{閣x彦= :uRE|R弁QCL&Pwvs1詞;弍0靤buy9r]衿@ V彈\*>AIAX:"u|-Y(e 0[J[Xc,疫Eh^B蝪 ,I9.箸BWJBL);n-lV)92 I[69mv}sS3ajgM(静A -y:羂塚 `ul=u69 S)Rv睨u9*8唱z\ケIQ+jOE猶tfg: 箸w狂k+G處@L$.5uzゎC$ 2jq袵 3c^i}$vU}W;w[O ov咄oDYEw[\邪f圖8`7jA @G妲?剣圦QCA7rbmlMBm Im6E-`淅c s 楴6npz袒秤cP晉(5i!鋼3`錣%傲o>Lv隧(Rd郢D 8,~]0/眷A \Z[SZ$蝉\?6o榕>opoh賞th狗wII匳 黛 z草,Dv#麾5F辯菘A┝=鯊*h＋4亳2yu,fK3o2qq2夢塾K 槫 A$?g?g. y(K容89:i瞳ゥL)2 W ` "釈髓2"sLscx#6mSo@S/`2][\r qip&J5概FOAGbm=_&&'F7t5(&ε蘚額WU0IJ;o皸>蛛CbBJJfj4p申ID)池pn1Y又;h}窃l`6餌?(`p`衣>&`4t3Ko窃zxm繪G2/gFS違l垈KT\6JcyoEL瀾gL^P@I=洌皴3塩b/'OQe1 H\B!p0墅,g:3藻Y (Zw能Μ5"H.06bQI >昧(Uёm>#佝A0wOk:'倅9AY 撤e88g贏zxF聟m"惰F非u R0+K誦告房T栃皋e'bTLF岾N)E y_O靤Z九`厮W枳恥 & ZhkJ,O1"\碕Fj泄 MOV2(>Nb39=Qzl|L範9鉈ZcO5桎f(n待.rl w|兢Q 殟mhI(暾吭q价7l iZ?mE=Y!憖Q$f慧5# 'Wep6B7!D-Zぶ刎fK娉H$253sz7U`e ,VZf:~? 牧pS@V掠@支W&^[D鵜Z|!E_`#{_脇^,-PhM H(;`Uρ1團[AEF鼾ST,榎2Q蓬~ﾉ 獻bFG~n+W_s#hX碗啗6.0垣x=!UH國F-夭吩0算v=jv N r賦s=emdTPn1E[V{I'W j^D\Q 4x,t藉Ut>E錐7岻5蘭V=48$Id{!給端1t ﾜＦO+繩uしd91毋8bBcI坊egYh隠9M况6徊P索d<4 e憐婚 ed(3芭:_bw,zvMWLW羇7]Y;]Y;]};1f冐2匙te"s魂23戃te]2)3\$9嚶~邁印Y2Vs3卑eo"wd弦殆]1R{M^Es魏綱鈑. 虹w]ζ礎K邁玳s~邁瑟s盜始]&!7wYoLiIoLtw ;Yx7>迷~3落~ fe0 ?f3鑓fR}F3蘭qw繭n39> 梹2 hF3@昂f.* qp咳4桂|P7t襲j訓v5f-j 茗DびS貧4s;R士 &縅MA-9瑁X2 :8r櫃ux^n膓w膩餝4f4m1:6:滓蓙#眇c7{d~"|dlCC^8F+ +カ竣e-os0'bK6攸l<[J>M听ZDM琺h+,/疉c筍HuG9~各VVx O*NN茆T-'s霓V ^%+穢宰畏幎lPc~ie8ぷjq'l鑞td Å4賽0f@l+膿pN>ONE'qKeCzｏj7U}/D^K猛錙f7w t!鍠cI5>^=rgS't *d1idKt_ǒj方Lp臣灼+?梳_HFht孑圄 ]\9Rf*k鈷v存躯zrc@{%瓱倹dIE4rB8pRO*輯+UQ OF+nkkV]B8I咨*:I#s 湲h,}'K}^3瓶OGg2PYi6EE"7膿' <j#32WrObaυ1h婆eif3=wﾟ*-#(WL7G+Z稾薑*TVWT{dlShe-Mv}]l=d#uK//磆@ 0SF＜w窩6=陲4?58z^c^ D$h*弘nA雋)N阮 (j邉]}eB%kpr9展緒@攀4=QA^]KG饗'L,<刧4RN娉f}_ocx奮av:(鑒D=πVqf'査oG=杯e _ g 3OC;nBd戊{浬Hk1'鐇q"SgケlE3O劈fo駄鱶3y(臥4悴[k5,0 Uan笏/f/2[u,巵垣l4' S OW`幤kg'M= ]e逧nCP%vX),B+h9!9/奥/Uk> F.c4倥84rai2aa罍z-尋8s7維:>擔x+j=.r:aW2(6Xy&0O駄\〃 ?=.p各$XR j鍮ｫiZ{?er餃.貽%q%m+kU鼪 RWddx &#b:f\枡zWX>嗚*洲&5x泊x縫V{七>.w];Ro塚/pK 5;>Id}=CEdv-0@釜{8臣U_YK)|胎bS TPV蹶S婿'瞻U:ゃt@>19{d(:>3M3\x{M 臂[rOUjh^剄m6nSX=.W "YR'*Kubl袤+剪F~]鷲s母}S断皀O:髻fn=嵯Kd JsR[ShWｕD蓄@L',SP搆g)Bx畤~7=ｄ6zA[6廛5V*廊AM嶐+51QW"黜a1Rv祈$@^V撓髷りy簷7*_貔iY< 詰毳U(\G;媚UI吽En杆Vla 9沂%)oPkc轅+-2rn|S*|輜БV檪vsnQ.淕HYY默t竦kl kO\鶚Ff^Cc三峪~疚Uhw{S1t>%?聖&治]踐筏繼O綮盡D北 N-_NQnPF#厨XE9]j7Wz挨bPza>襄~{?0W7頼o+ 背莨c蝿#薄=?7傴_98WD眥皹2P >i+lW zp3 `蘰 薄x茵 逾 嵳/弐<60HD|m}0?j覊;c Px2咳CcG覇賊赧w`!1| U0^niG80逡Q %#蛋 f3/7j~~A&如"槐 <堙$_*LLB槍|q掠4]<髯Wno贊*{gK噬s滴碪需檗CnC澱3s^sO''穐bqktぴKi0w茸lr楠zfWf~[i[ 'G G^妝庚Rsq竄^鰭村濾問待tge趨ty~亠NE陵 ssTo燿O雄M"\如USO,k=7qbq4準 ?/誕85P/M&R 龠 椙d雨錢航!( > tn^C~s3且'塗苛oqz|r\VH1>gpg)g'd.tu}T韋)xk埓737^*S,饂j.L;w0M=逾Gc性~dnf[丕Q'KGGKG.領fJSyh uj軻J0.zYHbizx/r娯咄G3>-M昼<6W/驩~8逐w,~?OO=2 x(/d0儺9澱\&KOOJ滯&K>U;2*BМXW !'z綺O簗1謌扠L憤i-次O翡州=U(-Lu?y[wh411Y:0| 2 捜滴r岨獏9xMx^疽[*皓jW栗榠3踉T> )6f >];}\GI震"<鞦碭祈 >0Wg'耻F,3+袋Owu簗~uPu_9脣ex燵^EｘV;貂3(N毋"y?7L.JI] ~e|髏迷"0洟cQv貨d]4xGX電n[3謫C弆B1`壼鯖y|n v-4~Di`+y.>1za埼Gk.Lw2<燼tfvj \e`w8q/&關?' sJTk断櫺|!7'採民腿4|ux欽朕臾q(~87s懣b48ipw窄*?s苙?s苙?s苙?s苙?s苙潯單?@$mysql-4.00.12/manual.ja.dvi.gz0100644000175100001560000461010610021471310014627 0ustar takeshisarF@manual.ja.dvi p[uDW-CG38H!?~8%! 0tm烱冥WNhl7`刺CqR3idia,eW.e-;[< d9{%'8I$Y詛tsHvW仗E囚nf0tlj楽羣謎傾@wP9;M-~蓍羽 !CTKcp苒3;u!e|A4;bwdv7\鰓[>cQFl$猊覡HES#cw鋺vj&奢G @_sv[&>pbcDa 侍MвE}3[+VTNEu% /HeBv厨[vD'咏;煙胴;0狛-R祓瓜_t= 沿dw耽湿d&嶬 6\rTgH8h UびS+>ﾐ|_6g_t:fF_j^d8}椈1HeWXt_>娯b:W,| RSzj3x} 2j;g3mDk間,N`虚 UE+# `V`i 4C襠oA[3F;R;RWHn!S厦=>__T&)躊iP ,CHQD] XUOw(@s叩L>L ^軅o,5,星XﾗUH慅t駭2!g~絏E:$夂tpR幌?_ 告握XB]Z 綮 ~.`轅u 顱5逝b7jkM+[b5\J54 y4l\Y6入_a6-<b^K4 "Z*U渓6ht稠DAM`K h}jM)*PkVLMxT 'shxF嶺>賤袒pjjBPV斡X{_u~幃@文| ^:*P`辜崇qd湿[Nk:`"X[V-WR烱_!}OZ胞秩Tp8 7fiu(= "顰<@.傀xieR盃,0n.[韻R<}:c"vB_弛厚2甑 =K!-亶看粗 !~[f>Mw {.rz`]SeuhpNG~VkvIb85<<~" 8跋43{W仏 43L7$VE'Ywc#愼F鞨V^OS48r_<餮iW1藜拝S]D它VMcy4}2bco&b 'F墜dLCE]GKmG`'$7@)@z痛'!PET6H63}n ) 岼斛5.-膸~&俗N"~a+B\UoNv+mJE7fZ2゛!Ur1bZWsgr獵 ;*谿Q竓mM. O4LiK!k Y7 ^ 洒O7: 懈VlP[HrV;rxjY#'vU!庸Av(/g159*'UOMvO|uIJ`q昌芥s5X:#&劣穀挾f6Okqox ylBtU枡d塊/&U 9/ 9qL@'9鄭lX軅W後NL修w `1羸HbsO]0aiHL'/\ ,;H{,xb4溝G3:ptc$侃xq腹哽列Y晨I\5$憔FNuR.瑁(!0懴 HM4~i$W賣ve%9茶Lk-f3KR%WdeG6&7O0 -fBJg'xJ`|s>x@嚼苒Y唯9> 3e LbB 3~b9C+;\JQ@Q,Ekf鯉.D促oAh< GM$DdD iK%J絞 _1鰉$/s q熬) 轟)DFUGNO1RTn1Pr8G \D`Y/j\%SE=+1V下g"x}I柚d,L>7#kX&L処(譌Lp藾〉 D\-県篥,qc椈_C+@OJO]&|p樛] eFH(h{X$.\EzH#w酲p.ozjc枠e_9Fb% ^ D亳_K服々]dJC )eu0官鹸55ZJ魃]KLX黠&bd牙LRM6]jD]TP偐IVfS;.m`hjtI ψ酳莇c,(貅<'nB++K&H4u7z錘 G4=AY4/l+7'nH{ r4窖yqaq;適uHnW直M4歛$.2DR|N>非)l_s1|_{5blWMk僅@FMU妥 G1(越kI萠}h灼D@#u5E N閾XA m&2M&:櫨磅D&簧[鱚⊂J :KO鬮奐R{Q漬F'ガ|HX犖 痢Rャir3;fKUTwG1}[CAm]癢+u%xpK1J<nxmoUxjR 8Er~劬 Jm]$O|爛v4.,傅:$W<:隋逓dCッ袰s:C黽U}飯M,/plo Gx偃 \ ylrY>FsmNW2但L ^QMu綛釋)0/ PSMo$ 瀚6緻84郵萱#T罔r銷醫q.挑;lrA:&}l?抽YC楴MKY7>C,樒)靡8I鉐★&yR談l弯R<拗 負寤oハLD4壞C耽Tk1&≪啗pI飴jXHJkV~79#2gC|HBy壺B=F|_8YZxkSs秡YS.l[墜 欝>f++H".睥5.1)K1 CfC)P'HzNzO9斬啗{^煕髏胙{\  ヌ#妹BEsj2WB rF笄9(LkKdD浸RD\騨@sh擾ws萬o梗e滸yvtWr{x;jK畳p&箏怖7qZ2] 'ZA竏`V俑脹3(Ih!9いN戊U2@; P W`N俥埣; ARBDt(.%es昶ZbClb\lV!K< 鏗X壕8]74UC_;U;t#37/7AX%;4D>@6- 岡s「D砧関Yq隲 |W溜7sGSJu!椽@N!u`Y_麋沐{w憩ki2y<勤qT%咤t)ic 漑蹼鮫x3vVS1[0!IpSv8丞Z,累靺 hw隙A呵c6-Dm@蕋y尾`PB",+S:>M粽殃鉐縁"0h冊?k6Bm'p商39hDG2~・@"椌gN#舖9N6{O-Kz譎B fC語;j!FX楷D睛vcIPC"P&v[v *ほ+9A稟Emcv Dy棠46RsA 咒IIд!e ltk婆w-@nVYYISH4f檜z?j技>-zs[鋤ZiKZ檜Ba\G70K繊%L!6dd J&<P釆籍!)iCBkz禄I~`{k7ftw=sN#轤ici_修|Y L爲甅'/)劇lZ~罸\朧 G梦T8O51w+2[vU$D]1巖*曵 *|Uw醉Ν亳 :YRCy^詣耨 鋭$gUG4j?32X{#磨y貉Uz=w:\輌5*Z^pM$# z[l微zL>a.EpZ ,@.a'W`俊{O揃sV疏]?N糒rJ6潛 x"~%黐悲Hv誨u;Tyg尹nZJQ7A僻n.zk苹c^y Gid }W7aD 5楞誤\G}_omB_l>vy"r|O弊3}@H?6冷TYb:府HFdMWW#m~upEZ鼈2i?x)-::jｕUZ7.9vJ$6dY| 化fY今A\9~XvGNq診$駟a 陌t5峨@4\3sN=3箘#K"Tr黒[些wVCSD9{iX- Z涵 $ $TJXKeYp +&*nA[#hx%X[y険S?+ v<4K!{< Hk"黹5‥A8-n7#V瓧,'=箪 A`P樊n普@ｺl$瘰Tq厳疇>o7R諷j^Iﾌ痘 eO+HT@TT"t D怪$#]99H:riUp ;P氏2P|蜃氤I)WZ!麭廬I恭.y詛{)[>i\捺癪S琵翦sn祷\ D]R蒋zz\:Bg7阨M }I-鵼x砿Y 憔vk8"9`u 望7kIJ.G♂'嘆l$hw.Vk債\qr現堕tq&sr H<算S3idc[-CTo_dEt5W 5wE耽u2;4霤&f<0=:0$bQ吠=>C|lH嘱^9赱D28吠C{s 味4"V2yWVALmB!渣nz2yC菌2>2ZF2 =瘁X$c織U="D~0A6虹]袤門e符Qb>茘  kH3nBmP\]Y }tycu:z)y eh3{gzcR莠mS扎~n]^L1GrcE`rHk3p/N.hU晦"j彗M7-E:QVQ凖gy#I>_E鑣E>/CV9N<9EaJ誹cLNxI)u} >蓮N]E!g,T .sdv("TD*{U-^A6X}捶.署78IVdjCYVKVyd垓 tL拈dX)Noj/JszAwF逶OZ,f縫eVTp$PEp1>脱!9 ; "?K寡鐶=:}旃[2rH"賠z"JK洫#rRZ~ }斃Vg9vq]/避垪D%7P530+ｼoeclG陞;gYr`>櫞 h2 J烙t9綫l盡Z\f%d[Ze$k呵6ぎト改_Cd粋8?| ^ミ R黷(瀉4xrB9to2i,O \~\C去躋 ]保 挧n#|jzB鋳(D|Z]Ql v7Fa}R遷W袴:鷆サIsooBqLI; +%zdr=｝$CNZ'H逹勁繩KGi#*(擬K肌C)8 J%h欷垤62gn(J*榕 K-!LOYhg<\vuI ~/YEwm5blA6F]U|zb}雨gIo 黎V<跤)~牘("扈]<p{{>d_Pｩ葦Xコw8挈Ey79田*|J/MF0 T2PjrMwSs 励V[疱mc#有(B <]假sK}uJ]gw3鱸補X6酪j專"755獏2  '[=l/c~.]Y 瀧\ /苹塊對d,BkeO,L梁hv k8M^K>>z断e/餓~◆i勦損mQ株寧1d_何\U;Y(r@/?痲j"諤$IDo2XN''!"y(v&P彙++n)巖8木>MqsGG;6IGFjd椄M唄d杼Rv8Ib+@JWf 1W帝Q '雷>y.5 .吶褻Z%at)lXV@ynJ@B翳@&H来擽!黶Gk4v疱F)- Rvh'UA匡%圧避_裸6!U璢蚕W悩E椹@\Oh驃\幌l軻 $L芭^JtL][SXfQP2vP\d鎖u`薦Tj損rSjZO阪"bBv舸lf^r,djO)5籀>N),MD!I9 e网o/改戳a=O`鉦BAS'gSB9C竹S壅 %mxS/^jwC;R&vf麝7U照九j>g4L R紘}ZFrD5J 循敢'[uu4戮GA):G'ab2'tSj[i`〔!`BoK$@Lφ#MCo W-"[D~zx?u~o4鮪敦Ov9`$%"P`%)#粒Ｕ< 5e弁$9L%{'3愀洲o<xnL熾d-<}蠏 泳c哇nrX?`&&GYU2笵gC|d{%]3 Ue#GV耨E岶^ kYN5,667O贇紋i0ep暈hd(]YH}T]篆[G☆#u誹憬.d9驚鞴 <1俥1G8SvN#)g?jF5U(皥t:Bp2c !YFf@v/oYn昭G(>N_TQ泰u冫l萩O鍠珀k砦C椹_ョD-R袱鸞XV&`*W魯=瓐jXd[dv恃Tj"[ TX=:"鑒8WＥ2#0g列iprNL3?{WWu鬱]mhB!b, 准5v%j?d @'蛉]]cJ4Pb)H擇Li> i)we0CK濆少-扶嫋LV_潁;s=l婁(%Sv述膚雎 !\E r@熨v?倆冪5UmK/R褸a旙 Ph|u@瓮7%fHi濂G5^-臨5Q% s 緯&#:肪_[|FF)梠O6(ヱ{B踴骰}@I韋gK)坤;R\L#泅7^eTUVn舵4恢~]M?ybr%`2歛8T 5[tﾘ%!'vM0K哽b^l}e[U\_#ECF12k院Q成jm*飛+絣椣r;H拒岡~o)B/,k~屍":d[>ev\}n bi入Z8ZO,俎/L役g鐐3鏐>P如)W避蜊:']U躁|Jf q譏f{AJW躯9:-b5s 9V@(&3E0e#[gT3尠OQU7,:避價&q懆m cr$旛N~D[m繹儁萇Au1皮澪L粭#JOю絖_$醂T襤7m4 fZl*汞u+嫁}1OQ0x"Kw)[N 2!\MC_EgB -唏;M+摧4蛆y V|瑛?5A\ G*dP`'靜`難,,^-9ah  hcVm疇aKwa VSZD貌fcnS'妨.!*h ~nxvLI!e+犢I#dXQ+'救#rl峡Yi涸:^J9E深skrDw7則>Vケ茜e{滴`黸=^侫p媾GBE爬曦寝d接専SEN :6j鈷I彝權&X|x遘22lx&"8i~Pd踴遘%c!)UJl. 璢@[N)m!晁壅fwi*管+}rv竚1;]宗}剥W爭壺Y9l錐[ S盆Ou*E@y&5C俵Zj踟蟀rxqI&L齋`Dsc`_誦*J叡+63PBeb'_W'nu Oi"CE^L斥 6h戟%<避gS踞/檗Aswc躯bbzd&N 0蚣/CCUg+ぶ-х2梛d^5]Hd>y{w%ｰ-IVC臍5鮗0嫡Ff!aX戻齢果^!屎ﾐCcJg餝笠辞8x\[ ) Q[9++繿13輯q7綜;%@Ku?&!墨&p~h T/6ｵb`T1牲?WO"uGzk]+LA瘰 V， tu]I|N*9>U LA_<D D`AbgsWvq8曦穰育煤咯t6翩sd巓zh@:kT 衡hlSW|.柵腆[_諳&R|z*\rO鹹`&n稽z蛛R(7U&'"koQ8u(+)}O@E#P蔬8uX`/*& ReO@rk9tw=貉#p崛Q t=WfzRR6i6e8抖-宛NZR*A&MxRF7湮.@i3L&r夫ko申E{_y[ZC}RQjE忖-ﾑ; ~{wp}俥阪 z% WzLFSXz O]evO_?X8"[惜ズBJC半P2 , dn5uWh(oZ單XSw9襭u漣YO ;g砧▽E-^"}9$%вgTn5b}W_oQ G4Jew$-3薨k離S y+>0} 檳Wal 釁逾筆2Yo0As@s<JP鍄DMvP6O鐸 eBR4Gtнvd.uf肴p4:@=卒lh|2|n6労89NnhiT?*枠距刔!鬻76誡v愁@(JJ5m g{;G單^,5s洗舖3lrwxH登]*|2dFJP>= z飩腦o!h "W3哉痙2~N`h ty浦kz"#螳_Wq UA?P=r(P,i笵Sxp"pV鉛d8箇yJ 轍H 5Nせ}:業'95Max靭 筅I1&@詿ill-nXG}'賁似c沒Typ k Ha4aRNl5 Ж_QHO4后+HD3Rxg┼賂閔\M乞=操KIvPz`~ t_8倡嗔>7P2衒DSI3J裏,fKT@袞荷算 YG{G7O9 d,+xNy咢?&G. 8uak嵳縢B1G_jo.mxkc5lOl/%]&xBISr喊W#=K/ g^Z鉾rm.下趺3)VZYU>w督M,蛄悲!==>,fAbz齶d Mjd ~v-"l匚P憶蘋砒ts+<掌κJ穡q@泥C])E0T感I;.ペSJ~Lu裟z )9F4pk5Ql>N(厖飩~i３ 濫ヽ7^q?虜ww<{kt| &ΒP: ww貢;K{&Od窰SN~a@zf$ｰ#x"V;% w垉3lC0%Tkt鍛ゎッ軅楓n+凝KwwK綺K!w @i\ |^#諷W,'!K:xUpWQlM蹐4AP2搬]-a貍(蘭#:I,狽;c0"smrめl^O:  S s{状orDL H3j*<cW)-u-,cCR 8K墅"膜p=OS-惠JO叫D8N=Um髪u#hU\o$?e),-澂諂+麺p{t}`^０嘔h.w#a荏%a}丱粉,}NdEWLl=}ｌA RW t缶聖Av[f?)f9`辞.#"5p5t$][I#,:xﾇ|lP5V|鎧飽賦}meV|_gc7/$1Y=痩*H5},懶=2癶)F bs 蹼王Lc恒$d畩K( GB杁;x7式S5u~P>蛯8bU示Bz6 0LlBl3wQ冲?椁LS- 5駿肺 迪傭 陀~Dh _n呈d所9lTSQ]竚]< 帥Z`掛渝\j38yS了Jt#y Tx檀b衿?Y)U#lv:匚l 叺肆裁r〇?Yz6畷俛#MuJ>8@欧hA<騁壻廓hnhED[F-^勃l簸D:fwZv'7 P地C擦<7"7Sggr'fh厰LO奎*k=栖kMぁ))9X様${cv湘M||=%售RGh挌e3懍齊媽B鬻! g 撒aaELI7K(:gC矢賚dm[Wr或nfb2JQT硅N$y:J~(SrH9柾j`J"杙3*洙 [K^]| DB籃,u3qrt2R 掏a~c"@.W;下?ZO"x7@Ot@黻j?[ )+b-p-fX^o1d% S懆|+SIWln蔵cql;5SUジ7k'h條ゃ貽伽 3Y豸p“cＫ2卓F_ #逸V秕栓8,>bE,PaFKf).eqBxM飃PK +T SAh憑澂lxs>B>O<_]p9s裕惶P麳",5.蟋h:距;~Jry藺 ]y*,筬|!儌_憂 拂w*w^`CEbd5"Y倉EZEf鷄姶聾h癶E 舒3d字 +._Gr巴囚~s"|x.d剛c'k*D2eKk｣:閇5$Pe清器]cik,G#i嬶zf;PL P4痲p(b8Ai*S束<:濬wf舂%蹼冓練~w菅沛溏z7j縞q児*e%O_IK|%UOgv 35L `.dhW収砂?}FVFSsOｷ1L^M唱&F稠FWDj0(確wZ~P5}s線jO無-4b{ia?M$kfdEE\s僅)j/NWs>詼痔y:r靈B_^1eKn2XS蛭徐0mNH腑CH颱?服 x▲o$7lo靖問嶷芙7~葹硬*聖|\罸艟pkzM_5}EV@$_K竈*1BR$V fxmSdRP低x?!2ym&椙 ^慢Mx-預?M~hA4Z$: И冫x4Z$ h勘ySh~L軍! 閔v6>遊$<瀑 %,f6Ev/3竡|~[Z関VＩ _汾r}vWQ凡Js{78痞9'8/|)N8}4+V拳L-蔬j~雌P4a 馗鏥 7+ZgjS b 9蒻J柁-:ltzi＆1Q咄O4'ap<+|瘟s郛QG,n@[5伎xmT筏 |FKA` }HAQH Iw`+ 9 or椙9`>fp$A涙nZP*OTQpL∨Nubm誦ML{qU=鍜 DV-E9`G｣療3r烙#f l2j~愈 c<zFw殼QWBpxv><V.Fg}W'%r髄* oQ画8,麼珠ne5t轍 A鄙GM- twBm {:瓧gLcMcxYz.5A/r* ^[2`￣u4"u~V[ lr竺xC鈑4W渕}o┳u洲w隰%3潺gW⇒go鮎S咫參/<<#y \S;6蘓]l職v#-t}F!毳cb4蛭^Cn2隋優h69i 且癌毬WKq\ :S佐#咨N擁1蘖R^d=視g_該/bpZ!cA]$ xMI鴆4vo{rg B= 臼縛!ndD$W]7犯~３ g.!22/hoU>WFof 票2c^]\膈g韆[b` }@!J紲F弐{ 2祝鴨A苴1PH<юCa0* T{.:HJN諦xKaゆ3!鞍Dd$1臉"q 福f`HSR#n/5煬*%PK宗L偲#`S.@郛 ( 椛尊}偲r=Q$慊B盞A"J&粤8M J紆 \ zYoWcC#L@/W x_CCE;/$D遨/ YdC AT >vqNrH|$q ~ ,'k!g汀11臼I)繼$|g亦rr/_NO&+NN&vx~H矼L & 鯤P:i+ソ+ 温_.K{yih/a^6}clB]& Mぐ]ご$*i>oeBg_Yd/RJ{.`" 担遮卮麓~褊7曳歩E頼,2?$$*' /[0NR聴捷J-G <朔迴3RwVJu(刃澆PL_禺,r逼&i?'),[悴R}-剃栢>HezQ3e2ZI牙&!薀iV}Q.!6`"=^Ztg1!6e`A,7W,o'ia"!}@8 ,uI=V=suN#[L噪F'酷 fL婚7*"`売L &+樅M拿X佶"#Jゲ:12ΟJJ&挈f 2E,e+Oh<"異R(}cmY#h*@δ8$p6Y94瘡^ j==d)br)赧徒u; 7P@\疔_~ }N噴/wwqo]|抄 ┤ [gZW腿c1T{MX←=^薛f >0e0zv+3o3 櫁Ｄr;感`RV7U#S@曄z捉g疸囓>nz]xqlW阮n(Q_Uo\終Om-鑑H票PS53i Sc =}yqk渺R`!蚰dpq孥MfJY2t`>\Fz0d6L^ 孑6_v蔬C澀Fq犠 s>4抄6j6^Ma[uj'bq[椌Q&BC?7=蕃q9o`9mei{宛_}$J庄}祿 洫SOhz&GE[;kj}7b#Z9I LIjl笥Un6#鱧gq0`-MnqOm┗i%Wo:)ZiT{X j飲icPbI努願Ａ~ZHX彊徘(O)>N5>>Z>t~j9噫U,贖& i]a芸\糖LcD 鉈掃L樸槽嫣vZQhд>)CK-[k父TrO-期g@?=s例h┘W~F鼡迂夫 @ 1z闃ayhe*槧ur[Y_?LG?$1e;|畩*蒔h2gz8];M8NbT G,絹fvA"[G誉t激'c榿#h 0笏裔!XGNn^E^M\o1ｯ黷a|UCI髟澳uV糶袍-条2h]@{`;莚c{o`g_oc@_f|fc昿H{I篌q^ 抬cdGawUL[!ml3[腑g笨DBt權め原Sq^^'鍾I}7霞FG%~Sxm洒 韈E$h啗衡t=儲 cj~x【剩@;J4關,nNV[{\;Rhw5T竿(cSAZQe±/m1J(42MTm,Uo購M澑8ΘFZZr"艾)fHG:q2G@!逅G%AS~h┿P液螟,?9ex]覯#&湿稈O類u@駈*% 榴n蹉n\gCP;bF翻4#x啼8Y尖礒"艱OH)V亢r槞-奏kbK遒(*/c$筏=;鹸u(A4]散AdmX存4z`= ?堯f珈5( 勗&p》/Q=r?0ch8)1Fa犬FZ.&4BI&ty娃dO聰復rFlL鼾/淀 JﾔQhi?!Jsb?L`侭3J坏"I43v9|b溝)( %LEj=果8_叢屹5#>aS1p竕D ■[v創sAeK寵{XF2$kﾏT襷-K8z軈nベO"!紐,+, ru" 恰畧∫nNJ典6E83 cEj!EB6FS稽(剴DhM柳廣"2Zo@Z瓣刎 inNNN6h !'Yax薩CKLMM`犬p=M^tYm閉挑j[&Z8'L1J 捻dA5燵孰X逢^3%+\2i周馨Bvr轄*s顴&Ll栄叭d衒n!5-lsF1*K> k F)ny6 b F}@I鰉【>KQ9７$_а恕X! ?ﾏ G {aAsbB_:eE*`秬糸,4+>9i(W# 0EM:G嚮磔巻J eY% $Z5D頭ZGo爐;x.tl9-盲qｅd樋/A t鴿">3`w9w43y?MaC辯肖敞閤]JW o自c?鈩髫c裝菖 o^Pt'" i""oP觸V潼繖:<5柎L1!ZY矦S悪j4JE醯*n:,Q]'nU 9E潴y@-~u江sP罵{(ワz]鐡[TmQ["才jU}xn4O梔c9oA`U@台鑢A MC%nRnl^W yb [哀9K.)p芋 {Jp{mIa 嫺'yDgI ostv@)k|A敵p牴ML醉Q"cvZ弟|kxx\紛sg]t貅 \(?K漢鉚掫ZT^E5BB Uo有J*?Uye[oTv@威:KuF_g6&q回dFZT=稔bvHOD銀"(1`{O@鸚$ 6(vx號^{Oei燬/w疎7[p~yE3Br?yi亶OJAoz誌プ[<4N+Ij啓馴aJ5ク{5^RxI罫賛\s=[6/@+BRY &[W[<}碾oJJWO /ch瀉J卒 /R~(j4儔k@JIt誰"A勸nB T!RV*)o r 蛉g}[伐cg!T# )R H-\)*q +箜J0o&eH5 T*~5#ItG6_ 3沓 / *:D%/ Ck/&*(1SMds埃O猷 7K&Rヌ榮*N\+tZ?5M傑蟆e\ F*rN栽v笘mED淵!T菲i)X.ぶ Wg3e2fdl -z|1JeμYF3翠D.|'連ANv|"!i-W%_7nBT鯵')/*$N,d褐K介QlUr洶 s*d甎LVW筵 Y+UU痼>Ke瓱L@FZ}粐M_]b}:Gr/司.J>-嗣<]}'_R囲」4r譬樣S3K鮪e%]b塙/(椢赳 C}!(履rJ<EU 擴!貞\v?_Y鬨eO#EyU挙*P39yUeU嬶!(ZFvY帽Q^U}aNx%?>鮨%(！>Nf)%T&t<膕s(！i2ri*湫/Gg屋koF:艟醉81盃 (礫rF砿GOMalIW{餝"(*0Ht［s撕Ut-; c @椰*UQTtR{5*?#鷓)(g*%蚕[撕zNN=惇(u**'{鈴9ъ圦(苦z_h|]2"gdroAnG_≧sk#眈c芻 t9Ko/xDX(v)椹8_~D4@ 2p/t8c-+rh@袈t:$cBM齦ODD4驟A 9DDDV 歸qtmy驅bCy鶺ODfd浩mpu? ^#F{冏r} D へ[R桟@v伯&H差A椋H)x('勵x,潘(X\R]RG券t$-FV綟#lG劔$M摸0<=f醤e;*jMQ,蓊Q81a蜃g5!9*jaEI ji剣濬 ?I]kD揀[抑D}PTG嗇P北治&萃Wp.H煮3vM傲Eq$I%БA\$I%晞7M~g0洫Et龍ib/KcA1v7導)Rd\疋 :(tM?*F %ib蜃Mi％\loP`B;d?_to1A"縹d.@"h>7m(b>惱凄x>D(｛)`FV\扛,zfy@`$畍5lJw/dj2aLA為B.1A~8.^<莖yQ9]庖>[8<=q[C啄TpM^-_杰acl 俤E.xS:[ua#KsｬR;.9`_B{吭膽=E)@;&\%2/RF3|歔>;diQD $EH] 鯱Ed v]2]W皿.^7:9+M寄G鰮lv^N*6XfF`RU, UcJCI**歿/T WDS瀧MD[*浴=obて9僧-9^教Nx'W$%2$ x^n_E"圄yH12k~AiHO瀉/蔟~ =L夂O_;z=XqHbQu  0t]8Z牾8DlD)zClエQEWq/梁AD 鎮!bu '"Xm&粘ｂqTqf=CF9]C HP%#m!:[z6資p藝俎] q:>噎-+2}-[Y}歡／/BS/0sb^"lQ令S?隠F星5犯 .8x尢`ypRxx*oJ Z',eT,*b!賭Pe巧X'|jY房g+IU'*"V,m5NT Ep.XPxTDTXRKZjHbYCJ 售 Q$:YW艸'tA鈎n5of.hHg旦:苟搏D7*搏D7* +>TDY.8P>" 鰍@%萍べWぬiH捗S&PCRLy )E36酎DRn*y窕NqbIAx,P嗾z幵'+ｴZfvW2.X1L槫S3蘇m_158jQC#WV~ 筅4bf^Y 況訖<錐sHn~蔘Oky蠅兌煦I9r$'廱 |{i7失 {п9H;Sgx{"f胆`$AJ-'ygbH3g!{h/余nRZW^@"-v',綯#=13L\]/5;E?∽@5崘F^6<#v潮c95~6~彭+wr肭Lv[X]gxDn =NF鑓蜘D!JtM癘^捨'芰碌痲@,J\7& 驤DKYg&KZ=`2$qm|}'o]pJC|W甃杤壬3pE固d廊絡雄耄}融齋荼煤 d(mu 裕54揃5}蝪V_ EyS ,2rfxx tVV兎hkl{皹xxva1AV_F演咸慰l丘H"[ts於殀JdV由諚K鐵mR架"BV~[!KzO!u;舮raRf念8.BA/轎l&拍tjx[i!}勉} 圉jJ*護=C'e%'b冗jvZa坪侖y+蓁>`xC府[&W_謳sOixsO失M#UwiT;S{>x5H/Aq鴟5pDbv涙~RI頤DZh$#=xw跛オOYpo$I@4N慱w鷹VN(f撫 wN5*e[LuF'"qR>過彳>hoZLｑ6h吹AxZi']雀mAs4j;=q9jxgNW快<<薫 彈ex, Z^ 7恍V_G疸Xn_cLC6]p[ 4`^ρPmv4D{L& 檜既f浤043坎殷2[醇g)?致yO:訌8m81>Ywd稿&*qp7Z擁 過QAi7Q"蠡p7.X{Μ2g5 kXtT洞}~9|S*)叙'S)侭挈|au_@C3A#Y(H=4瑠Vu50吠L!t0 vAhn5vLｒT#m厦>痩F$1;6Yv4oDg|7"a済-隋\搨Co1!寺'q@斫AV轎Jm&A 皀@G1)!gqlQ撃寡~>q溌晦W0L>E< NG') KC蠡em afF>+5eJk6A`kヘ瞋 lf(-^?T|VY` ^謌)i @侍+D幢{蚩% ]|_嫩vUuxmo懍桴椌=d7E旱XjV媛3l%#3; 韶`lk!釜FT槲B3.f匍l:H+}Rm^票R深a 尸|E+xy樮 譽6`-?VZ'豬蹠$d?{r|1Z8%1_$g皎iy OOTLcilF Y佻4頬nn腔V'$HYA-b嶴n曷Ul酉|!6n2 orlxx qt?^U#4c;jj懃"K VlK`鋏 R|ui;牝川a/ +s pQGGn} 83p鶏}r/. 8 i0es `9 t4_4dk)4xz.e7 ^>MPB9d dJaH),欸駟}V/l8[_?K~fk,M認痲dEonLg0+4mA*P験９K&~+YGI8=$媼sC1RZ' 鸞Y2;?'J{赱n霹r徙哩邦f働M靺je$y尸m=evcZ枌:kA-gLVfnm図y1)F器8l6轍+瓊盥厨|z:KAらC7GO*  I^ 'x\}C6TStQIu4tp?|xc32k漾I ST r鶴m{D;u G;a咨*G`kToH xi^C-Nk朧f[1R.懴_ zq3fm^牽00'Vq裄,:mN鐵胼l.M5墸弭mq9y)>3狭~b6lV=c麁塗uf罟芻fF&,顆往vq*Usg胯轤鶇h1轗Lえ{j _P代o+*7$\m}珎ooxv獰査m:$943u72a+ q%Hpcl紮Wq擬暢纉・P聖濤y$G9”勞2>8\X武{x購]w膺Z陛裼 W'*/=@珸u[xZ>[{ W>8彌GsX;5葉頬6}j2N鈿|圦季# / 閲~6F\+i#l+`咳 R据.s希)jGA[C*0iDz aE栽側塞ktj<糸^ a鶺 $咒Z要DU_b1MtlHy&@dI$o=粍頗/oIr0,`7*O'獨L6媼斛 jd i rO$^"3G{L團Q-}B廣x;孺z悛佃X{7YRC\0g DtpOX)&l-噺 iw*M鴃襤Tp{Rdh隸 NGJXp)e{P.ｬX> m[患]R z竍佝Y漠忻&r燒 Yr据-5_iOEQ#iiXDeHsw惱 ZQe[t n推")aX12I:-'/E@83'{}N@N~[L&uWP,燔WBz 輪2S"蝶zp=h7# 'f狽Z]?!*汰`r{紙]Tv4EV0 !\?5gl ]a#n4U62?2U釖30C8G}◇~JE疱tr&>@x@_Yn:qRk*5T'(曼Tl坡9Y%!%─鰊I_潼渝PO'$YL?)U)湟tbifTVH1 亨HJG`Ｋ枚nyj@!_dL9,,3XSy-韭 廂e倏nzx(~GXe 03a)l楞恋05f3 $油=.u~{e若^c|3c慵j$Ceb2U,瓶 鋤g}~(か1lWX}X=.CIgYl£eU盃XK灌w爵|Vi彬o=nWG% ~Hi唯B{拈w8d&wE厂"7 39c橈8 贊)_[m&j)餅UC 陦?∇gpZIGPRa@BKo1EHg}$l+=@籔n3SS84J W@nDd Q'm 厩 [-Ga=p ^ 脩) $+と鰯AZ蒜腋;`a 鬩~\rbW退y|[樋渡V sh艶F禍#椽0胞MZv i1脅>ス橈J篦¬選DhJ良TY1Z(x; 6礎hh]P@>+_伜dW:ZuT}rblj糾cmyhP0O[ﾁsX讌@o必hヰ@O94SIxGImx ヤb{n録鵜r繻[cs"n K0tE|iUyθJ,\^^V輕羯nPo屠c1R#gV q =з@R/3E2べ,7迚t遘#O'8qI|\)*箪laKLu 3)o~=!堅H`0*H$>kb<蔀=棄MX{S&6bun致EIPQXTa遮N^+潦HA.) * XU%J=R{林-EO l1(ljJP#w;B8:d"QwVKq`2感嚼a ^5[こ4s=#b8;2A櫛K0脆爭mZ ,愁tGXDz|KhfA`Ｋ.5Z#M""瑟g b%-m*Ak!寡g雅<`}J" g4/\M帖|Ty{a+f)~j樣尋z△D氛逼:$gGG鯢UltP2W-K6l]Yw,Ri7$ .Rz凋Y{o嶢拶hg}<羲俄椦l4lBw鉚a幎&sqVU3,b~v溘 s泰6醪+誑d`OsM颶$z.H)^后ォ3L飛 ML3)%W#暃};X@匳s{~'晋M晏. 周笆t薜篝8Ly亀}A§=P%T 志藏6fa] 7Qポ^PZpd<`托'pu,f溷証&!!4Kp_Sh/)b |Uб()L"] ZDM燬E~壅 VL[ylHna>#AshX帚朔鏑s2VZi鸛^I缸;&I{DJ.W ゆr歟mw埋黄G\v0a"YN _4h)沒j2gi02EB謌wJ<L-朔[_43.@/;Q][4S鍋' /EJ2ト面&bn拉v尤閥曳@zQ\L[LNhmM 妲磊冦^"PgXkb=!w9S晟W4c8!毯~@ Rko#NIH^5%濤57wЦ曵pWk0nf~{%Qpl|#zs隅4-濂^Fdd2烏魅I?[籟推鯤F桙0Y2胎2L槝rN BU!窶蕕 々?i階C~\m夾B4n&K凝櫻 3"h埓rI9daeY@;Y I6q纏I神{I撓e:C鴎nV]{浩<<稿{!V)JX園:Uy潘]琿l6Oi($T踵4JQ%~6AI鴕D8蠕贊d嘉丼JiBmV玄]5Z[葦6j,再硝- j&h阿蒹bk(?gz洸 旡晢跣@ruW8T8=X$k骼>ッ}_&H鏐bGXo/GO剳平q$&濺6 ZG7h暦X16wA[_酲Xp=吭GA] UHr}>o-綮#F!*B'nP~f/譟 "轍k>xm-X# n8f還"V ^hn3G?uX GO:Mc{Z*'x苛4(G伜E%Vo滅0]|j?Vjy#3YZ8o[36云rw4嶌f8J冂}FB/h?]%f^/Y.@pox)>Jzl"湮c.IV兵_A曦鷄 xe8XZ麺#須7_rs=p頁bwえPpuJY雛 %弔W_^2:{H果GK"截 2鼬/C!治:8t=WSfh祿 !a"xlb .0KOh/Comi7-r@6~hgq8En0Yx",U耐I3>(宕(*3 2O\0陛KM3Ot|o綻!hb鼇m_疔0F~$5粗E/絨ga;T1;.qs{gWpUrN@e Gﾂ月Q*t B4更L秣-lUg2G陥厰b具p.;gP4tw fcAt -朞S/E.&籟奇!L綴X,V4n鍄{eN8'mk,H|鎮 LW"|穽C鷦L[!X呟p>Rn芋vi~妨?鰮,f食;ﾅt蒜y'>溷:_W Y!犁 0N韃|dUQ%v5J弋<飾|(sSWH.ml/~`Z<^"*MN9胯漫賍じ)C4N%W;,Og/.e'3G33#羊[Z0ke0yxκ*VMW6q3T幎>Z航G 師f;畴lczp0運 S{/>yS~蹙雒hPrY瑟 意4泰#o|踈\馳-'Q完癆Xp (pd<.P,0 7桟,'wvhd'=Hh#鈍烙兩uWD47「"A駅\公７,r3Kh:. RS>~b( 蔀~IlS''4#{>Zk{>乖J<ｹ川b1泡NiMjhP3儒M瞑_jHk湶F閼M齲k2Wr+唳k) ?4Q脳}鳩c弟_*W1(dM鉄桶sk%I+;b+PeO :;;嘆mS蕾$仔~髓B&+Nu鞄 介hMmf~嵩",on%@*Wxsr&_d&3s Z臿ehpX磋 汞d薯Iskx顴g&vt8=6n]rd卉疊poX)i P%fHDdr/]跳vデRu(.<+DNsB0]7o柿zYkr2=ZG?c眷狙虜汀UOSuвj$N=i@j$gBQ捨t8勸ﾙDG渠hdXKゃ)^r8\#8 w篁c8$l:{誂>9(?@ 0[敵w畭}824.Pp]r[(?8眄%梗go雜P3[\(vuF/Dg/=La#$m笹CYf/ЦBK Hp.M7d8gq: BSM"W駸;焔a髱nTa{?'J葬･w rWZ :EW酌"k惇(F_;%彫k[QNWnf'dK)*護Aワ皖覡^x;~ Pf#hF||/-" )C酳l9A闃8r d?#T${sg龝>PYJpq悖Z逗瓮X[}$汝3"w笞EB[X起甓 f~Ψ]kq]t_%)痴Tt}uDPTc i 椦y>{mG3@_>L)0頴n7%3@3z-Zn~dJZ穀yK4%}A8 Pw&-/C[ 'X戊殼Gaha 1yQ6@SЧji!zG Hyr&^職0cI,X~vk2g陌兵@!,D[趨 N' -)|,8v6FblY彡7}0{ AZ!E )dベ u4k}|1 鷯'xHH7OZiz\j3Xk+8R} ^;}\Y%h(;#;6tX 閠y渺fL;hBG抃Oij 壟< x&`TX3ｉ >R+8憬U亀ξ&AI1l[Zc;pｫ^zUdvQ{辯tX}湫f哄沮 3韋,$d駒嘗K蠑軾ON≠8'zX圧S%&2K"g3變(/~R3%踟7葬rVpj濕k ┥.7 Qu鈩laF7mXPY~a-C8瞎[EqTXQ -F{T醤Yuwv0I抗sN 峭s,ВD5緜hh)>T駘e4Kw@四i?c3whFWc5滅S=5Zo]婿R盜X&@1b[ 7#;k)#_(@;r4!_4rss截YLk歯MBPK)KO,乎oln3Y~乳WHQ,5_EI囓C#+@ jJ王2 bmqU Q@_陬,瓜!!)u 蟯蕭 fGbY(dn)畧J`,qM 'm鋸' 葢-lSnogqs.瑁`"i'>o`;:曉曜+>_摸5{_jhK=-5皎I亊yC!v^ 4Yj 蠻VN|艶q]娶о_GOvp|拿mL  TA+aJu槙髢 o;L[,~Ig,u材阪UIcJ栄 &=N\ CI d'n&t妬臂扛Qeウ*愉F\r￣w駿l呆tE/粥y釧?ylr[tQNK4d碩Gf&F ?&*^予bK壅x う;7亶鼬(z負恪u牒'p髄u%HPM斤"I/q*餌5, 歿H\t珪厂|-+Y`惰)}vM5SQT$akp`囹1w湍r"t/eNdxB禀.Q)Zgb 苞p琉.6IC琴J)5踏糎1Vl#v穃SPy瘍 8v0"Y;a. l餉粲骭鐸諡p{瓧!&Z詳3濂-箇[健kj齋if, 1t鼠?+*"CEIdhi)啖M|V!!Zv浙N響C GK呪F@ぁ#Ay|3$[-乃+絶]X縞dkmTe1R]E?Qp鋲\x;{ I)忿v:T$H>ΒjRTde&敏CE u"L(歴Xq&pM8Rm-lFN8┴yo鏗I寄I着"ぺ 'Kncp"jR3瑠vP瓧W@a w18擡 SSxu]V 煦w`C檮e夏y録NYPh遑eP2MX槿~峩O新EMZdgFへ,aJF,Q-*Yl~K`P9c_箘IH韋!萌cg6K]衵>Yg皖cR2d2揩*ΟU陜 _$!53愁c埠)sQpVD FU %\f?<t膺%IxL._ hq_:k$h7Z沛}召DlZe&攤cq乙邦臂ck8-&:O]-@P=C7,OU),7SvL1utD1肩 '||爾%'漢Z微k4C)BN3!K;&O,l ;y朿 lZlHP授|]煕ctea{2 v)rs佻Y i"ITAd筥凌%]*n:FJ_8IIP >+6)'v祐劣黄W|@IPZPU u{J<7tB轟m=16,59鉚訃yyy0x|lv5 \ ]F3IA@h/ v(@Eqn0hHa:N圓 苡=_:a 濕'FUR6X[[[7-股p翦L:`棹Egg >愈wD ml/ MxW纒J錦|Bf^魍Mk*#Us}嫐YG伴"eJo J鏐@&GI^寿8vk#Gr]n*'ssp){83H] p\yw7P XVdVv][+^琴ZKJvNoH'MS.7山N眩0@Ii h!L qR:!3莞8@dz{zaH@孕ら)J=D'@ *[刳e孤j菁zsi栗&甅XbZO`Nf'>Ws[/I00C5薦P黻>4i<VV w蹶:0JIo交3p*XpS+@QFy；吭}~D`NT;(v嬾oG6H;;Κ/&4"7lY裃#:奏6{ТzH9犬rL:]架森_廩歯a q 須#a酖Lcvv~:@YX鄒^5$?](_壙w\？!KXlRiG9O浬 νf}拇扛_!mVI(E~砺%zj7&&=HI住m伍<|*:VR5虫iM*&m*-Ν{螫&+%喟<`佻酩簫1肭hB蓑_*b潛WAm腫=貳K;選5?=8}xa:?;k麺MdgP<($I\31]u麈*j <-=似A2幣ZE漏,'?HmP緋ｭW |Q[F%ECU3- "8_,陸3JB2Y~*枡宰釼'E陋hIh圓[bdA.BnF 轄7IA8m8iVUIE )f贇{W娯d R%娟C?AbZ2i6xZv@e:nxYs膝Y1^S;7pc窓R` ]7它.,周E~<價PCづzDp%u%{a!U/$c%JLB渙I@,殺~Fe盆D=e甅*St|NG\/CTr讙 TT椰c=o 2m#i~A噺)9{怏k~挧A兮')FQ=班3tsn{R EZ{=Hごm0)j正3VQG #黎樫~$yHuI》k襯q=f姑7霄 ll"zx奴'feiG:2>鴣МyJ4たたqpX痢,0& Jxuvz残5蓆Y護4{y 3X+/並aCL=NLv(''>齡Y愛FG[Tp}*y膤齔2jnLk'*塘W眷<葆.XT)]6%7亞-｝.bm b M腦a*O.`s [s !FHe=JU!mnpeV=aYMFk贋蛟r0G&s4V瓷G9%9qH彑e?Sb莉腥'4y I閖l］洋$T))}kg o/;']01∋莓j歳2 0K$:4:T w筒o鞜BW, g\i~ 圃>D偏 NJ :☆ s*fHGh搏?:dQw傷B偐Kg梳&#nB2_胛\g#w臧蠅鰈w'@Woq%glr=鉄TL9丙mU繁粢[tUw?+讎a&n {?l.盒寧p隧L郎r梔櫺飜s叱K取nOD PL辟e^i~7A[2K馬a崇8fq {<' s1] n 8vr%wv*i#F条.'[A[蠏-rn+z担rf敦:耆F!{@wXX Pg;}6NkfH6 P=9埼+[iRB(疏<倣Cxm-0樗株q:5ViY輛_m辮*.rL尅r,29 =^\{屠nhdr+?~En9Rypm6-@%qH酒 7蚪 櫉流~?弄~^g^yeg#;贊?{ :珍RLVR!%(p≒-追rh%Y左S框bB怙耆畩8 l装 RhtC筥tD*q墓qFYG雁甅9J B,1dck`"縉_@/ymF;-[劬v -( 4 "LZ[舛YgNPBSk!Kg# |):B噪2stk1}綽0d>c3櫻瀏6h<惚ueG WQc8O__kD 8#[劇cCw^T 鎬;1餠藺 L_ ,'6j物?!i哺' /M r\:zM莽%9血 ?J誂&o麟 'J~l狐`Bw2;戲∨X室4s&O磽d嵎 `Xf $gAH[辱!/+XC卻J蜃冢?u傅\Bvt噪$""3$3 蒙5t覡擅Bu+tbA乙0bSp$0h'(qR:椚yYsQt)W燭EvV7KK&2 a:mPN] &?V時~hо tDo(& l煤ec9R0hHMm 鐓/AT"燮粋常=}PzU.q?/Z%y|6"ρ-湿N侯h+%zi/訌q(D$bKZ楼T ik6[CH唆齧寨E抔DkE`|"9忠艪 膠{8x妾a+首:uA鴒菩C瀋XbHH’IphWMw淳PTT榁;9yV\kUmi ~B掠吏鶯久gPSi`g4y包w搆j('v鮗 栫,:jx幻|;%+m杣亅叩5譖^>襟髻煬)i6mc削-|<B-#tkC^#f,Y崎V[k0:E彗`0飄5*$怺8w嬢c粕~tM;lP孛`壬w`f4c t0,Z9&wo喇g粢禹wOO.LO}M6{頸M+hY;}~R~j|aP~i椶|[Y>1li'v惧巫8]_]L7}Z醗Si赳禁儘h>Y_D@c_a蹇i@"H]HＯO~h仲k\>弟*T?1 #U\I隶Jh@c ,*? UQ++T !0`!e(,#p崎$&_}[8zBjBN=UAPA}Bj! Bj'LI蒟#孰%葬U]け囀}?穩8n D);K5'St正?b2bPb 銅, 話V/孥&耀C` ;%eGBR`彩Bd普NP檪iS LmQ変b舗｣Mw#Sw) Pt⊆沱蕈廷'k9ΒO傍@DvcP.~q棘揄2)BЗ\ !h飛C,SHOo eU J'rZFヾwl }o.S旧,!%5o?p9-冊o)★鋒樫A(巣<&"ADv蟹ひuE侃2"G!邉SIV'F ooI埆牙+= C*jSTx_p晃WCo 躅惚f ^P2_z HGk\酔# #dkv~~BA_&t} hC 捉wa'#o 熹5*r^音+m,fiAが`5頂dKkisY*TごAs亭z掟u+4|)FdDUw3k醉N蒜叡箔h7\n|蕨S+t鈩N?f陂t--朿S啌拇y}SwBsYhj ~KQU]Spy`;$<┓t蝕EJpk~ K39&EgC8%ZQコ ~ax誼*@)TOMCy%X渭Z］p , $ =u賽{pO,ZmH修 +xX剽-C3vp| 冠{: N[整9DgT,iMqhN覡Keo~>Z+r6D痴lA)Z藩笞Sg湧UNv/D疔2t4L液iI&U^sFo棗 7ZO 觀n;笑)狂N%LRJL"EaR+`1 $二RIL硬箚bkEUc-澗!*'dVj+6&v凰\#6{]Pd3r收6-5(s档 耒}爰UN[ /YM菠kQ孩醫/)壤鮪&o&^no 1收\8i;qL垣jiS{*b!9OzILa軍xJUM }f)B坤;KGT兜`.v WH咥朽PM4＆_:2t*#py4)!P.Q'SQn)N汁ut,Vq繩裂@T4襁CA}冲Or)&C1t>. >LUwAnX_q濳X#wfL O"賑A4'd)qe;o嶮R剖p#sf9{:GM4B凸褸)+鎖綰s|缸f&EgqQ9%J∩J篌g鴿蟄/@漾孜^磁e阿 %欲[m"U気Y;u猴:G楳PL2Ozk'7 牽L敘0zWw@"鏈1f\{eD;S1k豸Sj蔵(`<)=",p麒6q隶pKXoM8 (n//寶 a8LL}9垰<梯.ひ郊#簽袱5c聖WRX 搖+?*rXfd/PQ油y#錙(&岷r麗(Pq7Pb待k]{p\uv彳66/=l媛d-iW^WkJ]] Ady4&!\.{{H&i(m4@:%MdRmgC@ MSS =|歿 I{陜;燎鈴勢$n.A剤\tj 孺m拵F*=%'np jj@\}N+y*∵埼D*>6EiC躅鯲IQ = Kk單鋏x5糟n倬a魁8=~卩凵6]2&!|.l蚓KqJ娠塢淌2!Ar+YU沿f痊褞|w#Ffヌ栲&%W9Ma淀w樺$茯S`怖C~qt墺0(ko2t勦^Yg`o9,7kI)WdK2 #J` B苛h?唯g茗`.]5然(u!E`e俵:H08跳Y愕;S;Z榛e0yo儘FQAp若E~Gar{z :潜藜呑Wm+R修:[JP`#鎭蒹}p$W 帙1ZT鵲o0q4zY3aOyx H遉*臣bm渡#I倹蚕ZTG瑚=~4t#s6慫WoSu痛q0aCq鬩歸yPf椶  8G饅?D#)6jz:N決tsr9宏FE+om覡"6ﾎ剤ncALs=J{xn迅W>H\rH}裙>Y蕃塰[ rF W吉傍.木FuiDLRl鴟灸嫣G5<r;[X~`J陷pA臟診wB=陋鴛.vtMIp}goz飭QZ #座 bKc\掌@H.T慟XH!4s-觜GDx抹L/\e&!z 0U&W5@4Y^ Ue;w桜Alﾉ"yF4=徊Ky-%Oh?KzUo#|]vCЕr\q晞~摘熟1Y^S'R [&菊\亳`)/ q7N+巉悌OZG p (遶q薨v1wl?aF巌P. <,-ob4%<槇Q渡鴻活:]Q換*癧 U 燵Y* ]賦勹TxA＃yJ,OOJЫ30:jt;7dhk^否弄聰@ 粍nXN4f3ry冊i剳_廻3#瞹弩|j2^j祚 穰_玉侖<'0$]頭EeQSW \Ｐ∞q{[0!X<鴣c¨&z*3*-r#Q☆麦vaK倖92嘖 kwp%C螳Nvuqd寇d$W'03よf0f Oi02yiC1.K @唄_ z>iU忰冉`63<w足@+VN朱S*鋒<潴vyc Qp3ox#'^p7bA思饉 梍nya'_物y;)B/J溪月Fvb5gA0=Zyj3宰┗k'B4R4譽u8-!\5uB遞|韭r,C vc宮5並VA{膺j|叨o7\1sp $8tr,拗{_g$1Ct鑛＞僑杉\U%Tj@!TS0\来x篏>?墜肉v Q>b1墨N6陥圸dRG毋@\簀 ]y 1AYfcR柤{q4?-a~(jI>eF_+W\>h酩|+0管TI愐QzK0`KiRCzYQ"3zEt(XaM\Z^y稗~q)墳}婆nA穉*塡}fゃM.U1羂 kb蜒爵-urV;o.Y\it琴γp瀞V田Z6TbuR|G%my氏]嫦夐[ト肛醍Dy0iB訖F函M綴/P;h麋D躱xKG3KJ>#荀營)|a羈U曙VN+驫川[1徽'Ne%l嵎+ ^<蒸~:<)鞏DJ/9Mv\嘶{賍o項 ltw倅'准矚^F7S浣Q鹸o(K@l'r柳{=隶殉W|e)S1Z揚+*=湿w;Ph0Su5z*痞浦G斜4腰-I% 汢@軫awzn○DMxo&(~┐把@Aej[k'Wxz蝦}$漱t_Z M\v-wLf5阪CYGb;[,瘠JI&~9$+xp}yh)E嶽X8糯謐W)F`OP @纉:)~WJC t仍恍r9羌)(Z7吻BnMcs'J|~)L!k霏sFF&E`5ts$x<'|5Ouyvy^id{dG|0mh]U,DT!Z8儲妬 椈;.!sW3bR|O"=KkQ*SOk;d\3{_F>~<;~陦i>'vf123Z:#L亶瑶}-XpXg太X{*l愉Ak倒跏<惰杙{ U=|g > 9逎E}JLyKg+c箝 B!跏w?]) t/ 錏&9=袖U]jaA08鷦僥#7^眛卻AO\^l&硝靨z.粧;W蛋z-Y#{T)嚊lWuVJz尺L5Ds}nV4u'Cb<3{qZ jtsU6qFy~x(TfmZ沼O,説 ∀髄] 轗~Js192t褝忘ylMwg岻UNX|天E*iG )po,度oGLX_BzrCB<|&5LF)U痘k"d納閘]莟Cl0'@p~+Q熾V< $L#y|"FE9D榠團\XS94椡絳 稠2暄@Xt~K+筬tR4]mesip綢.O= <]e＾(~k^8感aqW球 haX詰C良H撹ZΥ+nW-^+6r<祇k癢rP免苡鏝ピnFpc$Ywq;pHF∩驤++)l胖Zvr j7s2pCp5Qimn aML硯GnIu邱=V傑`m\IQ沌 @涙z籠 g+iZWBKa6\C勳#f]坊Vt;RR o0]\w緬bjK ALCj"U0ev縣GlE竹"嫖 聚k鼓=L_YX殀 .'a遉bxf0釆q']r'└ w爿握rO:ta$s泛4Syed^{hQW蹕Sx=yvC 5z莱 實)S葭n巫i?: Wgm釐;y黻凋;讎}8y冬f.nfnfElwm @C豸不4V粧_YW*B4jB, O#H;v 菎]r:^/2*3]~(n?"JW2D比>%殊続JxVs[}Y┷}.X漕捧wa膚茯v*撩[5庶=VG貰洪NQ RdvDv:硴YY53*%M!均rTDect-呻BKY8dn2ZpoJ}%{{L{E]7:aF_2減蝴$曝Iz,<詳 Lv∃%痃Q雎@[洟纎" zR=叡 G2 d/ 剿 v章%1:yつ復Ez; 荼饉n|\K7=巳K)i X愛BIJ豈fM6nX薔1*>Ccx3e晴TZ>et 囃G&宕2kIk)3ij^#u 橘B惘GNi>PR岼^H`0XfMf)p*j#w\3iOon`;gZLp&Bn {_,ay鞴rmV)v追W< u脣w共'pLigd @俳1'ｅ&BM#X娃,=楔yw8>s6h皀b6-f5Z)5雄6^pw職譱' ;b1уI30]F冫|pMXR> 匹轂tV.:n-jd^c!|1Yヘ1&髯K斉芙=B+M惘<^ｉ葭 M尸艤I7z題49Zqd弘=成 `XL[+s>34}J'"</3貭LVOE|G<,Rh:51BP;Lt4155-f+C秉Oe4H]FRyz_iT6Д v?,1lVj崋P*T- "$)Lmge hv吽S7g-榊$~\P:muZt`9"W;>mn6餐#8iadeR眺z衒*y3`&貲)B'4A_Z臑?i\c貎Nr箍c0\(藐i`u) #9IMLdp旛"YS[.>> Lr鯊産臭uFz芯%Fb .6兒n挟"~R(帙 瓔r3B烙dxq珂9~5U 禝P"ビ0^(a[wgf"eg 0%-H.$'0tF5G殪rG巍焦i逵?m_&WY%TuH""<紂 蟒;琳V] $TwUwWRKSMピ6LKw3y澀88e\y"36 (8g[U殕囮>#I{纜g??'?M蕩q悸H,堂蝡sdHqhNncP8jMG`L6 移JｐI%Y(fg+up^±\q@`gQL#問jY巉uKlS\Kh=R0 +;b1iXl數K原R@玖_R||C*gr~}KJ承(V鮹u=蹉 @嘩/跪1M綣s9}踏t檠 KA栧匳~9{b E∩S+" 裟\8 0績L瓰蟋IwPuY\SuS0"j |bDd*H5Of"制y|`腕,2DB:FES苟 畚娃H1 RKXt^LG^甌"c?=~Nn|(3DNkp|Dx~!廐L寃]K銑mrZ@N譁慫y勍f?wGG0罧K潮Bc穽 Uo<+閹eo?京<^3L[\B畠偏K7<Ue 迴Uomd(;=#I竡2´洶撥縹基n[如P_2$c 2b7-p啗Hﾕt,QXp鱧.猊[y魃H游0鴦JDG2<0Z!會D$,}纃JCNKpP'弦>M{@_[.4 oj!#9f |fr0Ek> os5#Yd&征I輅` PV;W秬壞`d[5fZieM4j Yu畛Kuj:Z SJY (fYhIgI&U; } Wap9S4<戊Ex4=o及< 萵iD}?眥{Rj]_L偬v2BoOGl.G]!呆K4"S[l9d)X#&礪^:W弄~WZJ.v2@;貔' jX6G +"c$'g46)鯲W`f7rL冩 ya9bI瓦生0傴靨"3XL菫eS @&vQ 鶤\"\O沈.?;Kncy=咋%i0 i1BQM<5'n0D*[y俑s-t桙6HｳA2K G凾WOp\iP艀鴿鑾~B`f.Q7L癩e'燮樓"1>嬪h2嚊{`p}銓*臚9喪'X(P+ i$V$i`IfrFJK>t'#N3 ;O`+qh($lYA02oWNs村R:I B>傭佳r峙驃┛4Pa告}駁}UXVVNN ?責墳^'0\雀*/$Hfmo 攅F毓)浹拯m1 wbn?;OVg賍h^5vmm販逆{5}fFHS瘻<9w*滸V)R$e%鯣S/]醢f26莪檮さk詳P;5 u: lFaOE其MFPUS魯懆ycgV 咯C )投W1#Q赴T竺D!&'Zlda>h8瓦{儔OAIE&)靦%x莢;k9Q呉UMvx#G>f(Bq舐{EQu*2,7m刳< 9fc.O%0 vgvu,W3AhJ媽'^BFd B("O"=$o@0(relY$}|O;遐#T刀k凄1q碓n佑m`21F,@.7[;29A捕鴿s[+uxD挙)j悛E= ^N(QMW*Z粛n! x}~9IA RT鵈8)FGFL抒3qi偵^_3%q檪 -V_V0ple {迫f1:)k6即G@蛻|* c鰺6N2>_c3y鎰偲p) B;0>桿;w纐陬~Q繙}.^瞹8-9 祕+1L\tE11 PzP64岫朗]nXM*b疵&w>W洩3N古HV瑁#%Zb*D塚_ lhUFR粧G)斑[&jb9~肺ET@ G笂uno9{惻~OsD4UN6s9x頽擢,V 2_ y4A}uS);档]q舁 瞠蘊9e)vq:K櫂肯~He倚J_50n探m,*""bI"5c:(2n 綸韃.]豌+%$fi.yh\当Q*kX十'X)| qB)cwG7;KQ#D(s:5(DZ(J$d苗f4)&Sbw交Q埔_ 梶D覘x+H^2 T贐'鄂0&Ou%弩q帋6 威g.諜Ik6%Ad)MBh0,椙i2y霑ヾuﾄPw掻h擘d@6v8'偲lX Q{6bwhR_#hHV鳧彼C北\覆襤Dq1-━2:秋+j黎AZLB -N$B :=r4kCaR,bxh g 6\i勣`|V7~@KJ* LQ:廣z? x腸vp抓窿fc3>}L8BS勗"鹹)NaU[)MX彳%\賄D9$DL :嗄遂<1隕腿~蟐?貞S蒸2俤譽ef電f晨%伝渕I#_}?(話+歌i 懌=@;#\fDu啀X^纐孩=)弑a3血`知=LP$svw糖旛悗歙投O.V%EU=9榴+ p SN8 C@棲Lriq( r0a+[DN8Q ОqmVlL~|恟lZFfM=@3o]b)rbK凹雅523}6 8\ xSSt4`Xl)/莊,整露Z+M蝟Э給OZI?咆品賈w1揆H`B0.70簀4L$綜Wh q(+dhVT 籤L頑{1g*%#}壤O}Cb#dKjP1]H@i`暁T( 7紀2yzt,c 叡 W?Wa)X~4呂$4OモYd6S"俯#P翼 30 崑麋e^#[Igcd*F笂D葫cI変J'Ymb&1e>P?5 ` fLH*$ ; ++q3|Bt"PNn4R8e_YpVg猯I$_/L +!_+bkM@Kpy%R%愴 TN6澆U&eO擶藉&U躔濬;乗> pqqPL)vt*6Gv>%G(UW混Z帰Ydl"R} 5;nX%n,1')R5'19&8o /|W"6rxT|^dxC~e-)n積L殻 ^{9蟶yyax生'!z\ Z4w m*_<"|sJ 偸b]b磅B&iiG])哂]:u ^;歡Wbk/>竜0)$,=#uGI360_:JC慮閉1棋QG<o\6b7w&鵐R敵`&,E@純|S.>8/+iи裨X&m%骼#3Q觜OMT数{T2褪糶|S麭m改[AdK+○|Q[-W又)渕n)H瓊P奸RL }wヨF,&oM_ `.~txv寶懾>"約^*(2'IaB -_D*i2^'{XHJw|#坊d'4$'y?CD燮*x/mcoTXva SyヮNW *-A性j47e疆/I3鵜鰉@?;erJ  &蕘*jCv伸Pb`R寂2b借kAV%kZZKG0LM效l付[<> Scﾗ^諡:7X`cK]2^\}檪Y!zH7E輔bjN)o閼)w好`k}j CmJ]酵(m>)uHNu~t:cWMT;亭!WCgYyky騅Z Uo/]-V qRg )q:z+宜VRiPJ]yx;`嫂Fii钁["i)lyM8gy乂[吾{mQ{ =8lIJ;1id癨{t雨簡瀬i霓XO3}QAgс!t}L>2覊u7Q1Z?k>册n悒桁z~9py&UL2uq'Jt-mV左殴靆 kR a$!^#E丁汕陞6y4Ｓu`s餞4wi検U弘吠.jC?4L)$玳r"X mJ\cモ^ 圭&7p#n5藍&S朸P("0'MZ軍'徭\%ノ1簿n'I/ 6!i(`晢\m#* RSv\勒VWaVM恤@ngYゑ]o"謹Z槞n<K墸v{l;oliY:;p醸F\ Uk,ч靠傳\[s?H; )8\7=t翔FU\rAJ廷_vvZ#6jBa+ＤtaIFuv:b升竟s5X梱岑ġj7rOn,tvics(bXihp罌營lq肯l廁,x> 3zlvDJZM襾sCc} zp*威kJ殀窺lKp w*茉;助)lVuq} 6 繩:?хQ]8/v猴Zxx7p0恆f:t+鼾Ej'$EcA弖居Q$Xh@H%系t6.倚Tp@!m槐3{_Hv禀A -]r_緒)Fy湊繽 zI2夊h陜鐚彊? $+W珂并)婀鷯-査sgcl,囚~wKt=簍 E罔淹d HSP@Yru_tRj":gD，goeHy0鐃e cyTy#(Z宀溂驟/2奇敵+We;[ 鎖+,儒6.BHCx$0鈿GH鐶N蛤k^~Gm 0 r>渟Ww瞶hs9#l K8膸Q *E靈alkM藜 Q7v闘|@N寨)挾{鉅Wow]読mN{mhA享Rp釟dp/[hqDk\r概L凾咀\mjR墸z諭j@誰YeUR畭L}S匏HkkHd# }&J廣Mﾙ*L[j:J@R-"x仰GpT*b駐u0cXx籠1卍c'lbQ\'69f*mu''%`PSZ麻Z4(w抔U2T/∴&-=K[w8Xpnk TPqj5.蚤npR`9w F捨硝Y苅g> u殍C呑/>蛋Lag{疉7i恚i\俛pzT?KCTt川w|五&9埔`炎/芋:kSFj或Ht_'/B-吼C#Jz\67颯\FC| ZHXmR┓稜{縛_ J[e,#+~F({菸D3i9BWYc,&G'=6磁{Tペt.@7ipqRRDnfW哨狆x*J%族y;親%嵜-AK6#A罹/uY+,m播/tD0(P$~0:B"費;;s H~^W浴"ざ.HM&q{Gz災w險}{}今 L台uL`昼PtwQ70貝3vCOu4棗j52<:忖*籍qw酵Hg%v~ jt齪A韋2-pxv怛F榎zqgYX{丈 撻 魴z官x区|PCwZl鏝!7r=.xt5j(8~9@G|x;SA1Bサou&,94蟻KO枹%dx_(*>k7谿 hi黌 k邏s州\7zCH昿v;J[/僑=s4a獣6 9a0~棯宮F8pz嶺%<'^> [ 9~遼.nkE6XwQ孑WC夘dd)$櫺F颶剋=W-Q栲|q7 ;;{Gt G t'S|52舗rpk箔]p >O(R]%塞很0x曝)嘗qPAA竒7KxDv4I 0MJ2fB~ZUx憑Ax 齡6!>_侃yO'uj壼GW唖\xHLx鼎^ 篶W,,痔PVしAJsBNgliG|{RN0d儼8(ESL9T礇N 50亶鏗&j0t01#eoU -E ~j_w j 2 9卒讓S -@Ol X$nйkR Cf6C_1*?":.# $L故rBwX 呪7e\7*6mmwcBq{-H佰ia稲L\-!JHh hoj的Ь(|0B]`mﾅJ Y鮭 cokSuI&BH+$St63i$L]龠N pm誦k橋nB)"u+mthlF ＊- 巓 !bfUF@9p H!P)r=D|e頻Se!{@7kS;'BXU=MVD(hS0K^味Jm`24ur能@E=^亜z0?d/;$T8通&(`牌9 ^ .o9梱0敏C 的A%諡s歎XCq柊3gF#OjA條s[Yd{'貘_tm#5躍.w1mI`4`t0\U膏Q心M"xc覲65a2IO苗9魚V-sbaB劃[aF}{HHWpy}浸wo且5kn %諫j>pasv8辨.& lWb[q:痕N9寅c8 &[B\C疽Ju%求 [lC40G鍼多藍_&干4T哘苛)'$=瓶嚴c?;Is v0 )=胎只D/.pT=課k88Diw5gs7sSQm,{遺猊:]'R<逑防簣30祠W%Y 3(zM)R國a1;t2|蟆 扎L|2m逕]櫛諫|0０譌z慓:wvr霓s wwj鮭\72TaSLMD?/+Qc評V`椪YI{#p0h砿劃ZmNiHCSf,7qX笛M橿壅}^s介-V;A＃支贐#l27彪5AQn>w.h粲Q.GdbPRo,\[>wX}#KAak堅FY:dO{<浚&W4J4Z麕(])5掴佐~^?sRPL痣旡i?裃.yXW3Z;]V(y+二.･2饐I濳 (yu[M *];u,N愵6ncep>而畭V典捻 NB摂_#") 9c7'Eb=1並SZUjdG炎鞴晟#v 書]階XB%N&{(Q\旒v b6^77鰉62|31Zﾋ 罕15|蓼O,K@E`P TWaAsp\&KF:蕊5閊 7g 迩rх]tu\ZRL83Is交qL@$RtCx叭iY;M" ^G_蟯}zFiop3召ly6aC,bu労+C3 X>h(*\gh D2%堆j鑛y&U@8_ a_躾.XGKNt詛fxRr!BnZ#"譽p.儘=+8茱?x}+t億Dcp_i戟Ｈ~adZ6"=MWg4 :h&Gｸ5MShvL#鎮弯狷Cuqq }7PjZT櫃66晞tσzEtneG鎔&P膳h扱`蜍cY![g`0~\軈鯨yE柿曖X{h:&x4B2& a K 罪壌(5 /K‐X"~6Ho潔K罷lF2 疝&hQoU!G濠眼 /o9QK総;yS2gc 彊6Vg;GX~;`ND+o9,qv R7l,+!7 d戚W談bj &Qhn"nz忘'6u┳”跼P7hS釖p趣盜F*m;lwH>woCk,nｒ~d$} 毘,7沐8A5ip^]a簧} Qbゎ塵^pgd{樓nScc{/\A齎u|+弘@k>枢0~L暴隴}L鬼d0_消vwvLー/pfT61qa'ZaJ'{q^切3坩KZ>. I1鎬Z( 膠謚 vXV愆u;g|Mpf*Qz?$E_峭:m衡f郎se"I7ag疆7gP+z*_Xv螻.\mn3^wYnu?O燦 !q^urκ9l吻iZq亶cXJL-B@$_ 1R埖@F W:`7>?*Mt窺嬌ES,ef\kTg|c]t庸-a-3剃u鄂Q m|g遏#\  `C"鋒y5蜿nU陌>[K`剃b3┼J=Er6縛2}=8<{>&mrtAe3IQ5^埠'[q鵯9E鴿CH<孀囚竒?my朸=(恒QT艝h$c8公T&痘=ь'8M"鴕"治B躍p鞜 \表衡|SJ?NKG'V叮 1@At AXYWU9.智H嶌#R Y相UYL4"$%7 鞴3C佳O[aT@aCE-pvT よ梅Ts,Y~ 雖2a∬] m銀l'粱j臟+Z pf9融YY0Q{IK6qBlB奎u読[UaPI磊~2h :!/G囑諾i#w21N+doa?ＡO喨皿}Ｑ(|壞漆Lj湊+_;r\'2爐.9.8ZjN8~ :J*s|SK邉[q?}臭逼2qJ&x鰌.-%X滸Z鯣YN呰-']P3 \lj BvIA/涵LLSU F}L萠Z修穴Nв{忱UMwViび+H@r-紅 縺%=t{G訛u.蟒 "Z* x陋;T'約IN_[溏+A埠.lI,f5ｿXs4 =H,剣 G?qmGw6mQｦ量販NRv P{'Vl60販驩}5yjヱ\^ LU)燐/I子JO屬覇NuV;NlZ∝ctkgy]e$H芫k z.-x靈城|Z}6rgFR4,詼#^'MU!擢PCkカeH諍2s75.=W5\JkFb/#~ pXl&oy+{償8皷 AmYx%D 褪c鉅材\]G甅*$vWA x@#'6垣傲.-掟%比:rh2幢p榮u1$s[!$x 0m/V=~嚢7覈棧lN 醜8彗^fr贇<+$+K3@8G"粁Z溪0TgtN[Q;SQ`>'x^Q扉%#t0Oγ4=~s嘱]'OV[Xv{Ha瓢_L泡(6K直Z8czLGl(mEsV%(瞿幺釿\&wV蛤Q瑣mez硴?*s.iH 3;l &U}嵶K役fSI).靤^Rmjn蕾2L<вM杪肬CD>75Y P≠梅 Aq3{'ぢ/.D03\惶腰*S5c[}氏]2a涸罰T/`鮨K緬8)=寵"c=X!xa+JEtu絶 /k)r8@~著>] 6)m O法`由[0Q 謙uW)p孤(]S脹s<Z纉K 焔$v"7J9 u uE郤Jggχ,ic(vQ2駮{リq;Io"莉!!uxNv,5_q(fち亂PA圀(5恡j3涛Q7k%tHs輿{凪Z@rz僑3&e J\'_t3lEspRl-^a~N孀:Dd@婉棋?51 煉//KS可A6ld. d 鞴a"釼F認)ug_]<!SZ2邏N"Z甌0XMs絞z 7Vj琅 R iC7a1X~^WO~笶"j'mD鎗'&J e弐#a ]9-当qtU盍S廐}ﾜ∩WAAvC5)[t x@Ze恷8 鶯5AlaL~v4餞Bx-3'f某Kfmy羶訛F./< {遮.&X[甬地$g莓w/1&mE:3L?R^Rn-RCAjb*茫呑 VT>z=陦tE`Ka苳埴sb痍!.8.Qn3qp#"!ec箭xgY T腟狄JX\@N!pJу頓縅|>Qe~n謡kx =笙甄J06h< -訣<爾務!u-xTy迚,8昶布N|*Sp9冠Bug>0M6ы_諸d叉SY-~{Yc>-X^B_麼%柱{HE扨u愉&瀘7{k豊 K91c听,V.Q._/!a_w檍AT+~uB L+簒@`拇gZQX R80YZ|{s%僭9ZE$H%Y%n箱vuwO濱!):($s購t)m|Wy;xL#;DF0"sC\cW%3丱-n9%`m讚mWELkFNo剞43xq7*^y遮7b桁站O再瑞,y7]E\BF式レi1KL}A 3:限CGP~#v瓦u(嶷/ wB^}P/h9 ^=yZ{i,祁SKc#ラ領Hw# *Zwq嘖gp霍eЪZl!4類.V v7鰯CdXXI$M-v&?D0N~2j?3%hl+w縦us (Y 禍xMw> cw喜ImRt@0 x6斛蔵YI-1c+*驩YI[)Qd#6埆貎i E右l陳+Y=姆th杉5毳{c崕bK^P|m[GD9m#I"さUh 泥 f\o_aBW:n6ﾅJK|qe*溢;K|V道ogqiS鬪VB9.sz6%:K&(JLWStbASfzy范La<#洳a泱=i]RQ端o蹠<{;7;]驪>ihT5Bf"墓0?B#jn+Q榲詒SjX*[2wf拔hXfgT;q*8='re孥U消盃L()挽賤!cRrm籾z2=,t件HrLI*j橇hsPeZ\b{岷糾nXGQK娯C 7:rkk伏ekL+采dS甲h{|eZE.t3BSRN:[5財B? uk*0辺m/8<譎s猪Kqq=m$鱧s$O(x oef:Cv侈F棹[j BtZ`B 詐l 刀NZ薈售nZ!/t{(IpwZW~巽<9td"AV1ﾆ*彁WX[K云S]`IU別fy:鴇Lzt2S鞏~}藕 R 脯%@'皇罰gK右e卻*>a枋Rbhj.N'{Hg瀲.ヰrg耙^t9YDP〇R,TMs`^pJ~) x*'09bt8g陽#,'CLPb;貲?gU+ 鑼S4 憮4e妾携澄ul硼\"{W["2L6黻椚ZcU笆 KtRLΓ>リn 0字[EV)P^*穣7Pb卯a悚qeA隨m&磚痕\#薬%\ ｢9杣\轌LDc ?yRSB怺WBrlQ痂60F車Pg&P捧WL煮R xx < 瀛f 0ji9PZΑ,/|凪{k惻 "砲g戛k麿.恰BbT好 禀筵+ 襷tvn阿^E2'N榔.r縷u7f[F-*MX驤[9J&jc\mZVhj2πj7g--L6DomVg拓If \u+Q{LtEb瑪交鐚磁X[c=^I鑵Ar5h遑zxu($9$liS迥O JF倣2Y*v4/y♪@Z罍4(v {豎看*U粭*'Q9*laDe~P蝿F/)E&饗耒)zo f=}70\na!pd吽cn'[I8aM壘#z;ok爲畚S ' hTM&-滯&d6燒0 1 8-蝋<x崔 Jszょ@ 鬆@$IFU/VzsU弁>o$C$ぃ套Ho種;ケP6E%+GO4Z徘∵:TL圓kKXK;KR#碧Rf變]婬cZ a}纔o?Y2 X@9$56MH~虁+`46DqxN.EG(N+W9n壑L(6CF#L lD6牡/J置ml 妲M*uro0怛4:M豢(yb_ /Le3clh"pZX=9*uOni聒13R&dK乙p瞳､vZ;]鍾6f$rFd霸\0F,j鄒_zH惓k8uZ{O.觚噪c0/pdfv= RO;2(po樽V@糾t.n圦*w )F7%@1}4'Sh`B,皚s3D嶝;奉+O/79討煤iwD亳誓f p5t癘ZK.(3x*自棚[]pgP kW ID(]P.#g完篋Cs9A2凩縞r+z;Q[I4adJg!6 薬Xfzn>=If32ss0|瑶弩r咀Ey]X煌m俑趣桑8=匍 ~k療96C.⊥+dO鐃"癡qEpZ\&F='"Lu6gUIUq街v鉋跛LV蓬=<慕j2ZQo+Y$腐?U邉RW于e5u3u Qy{胼/SAAb?1.恆"u3%(5nぺ廱蜑(0%C>VbR0,姆DC憩T)"^5荵dns0Z怕 s&DSVR`錫J+E{Hge\ Nhj/L.UuCR詣当h≪}-i瑰升[Ju k<9zRh傅xppI栩首_#虞*貪'IcG$B蔭CbTV惘Q撚^(d7Grz覇A\VKE憮um 咄h6s`報>i鱒?{厦?g? C3,Z+R's=+ @ DGk# #L郊rJ}Mc @眠g圸& Su3\PH066 >av@vmugAHm}my 椢^\\0瑪k;┫L盛~*T榕)}謳n Oy琢{>廉(?mKqhUg@mK椌啄C鶺YR kn嬶K8'/$d $`bL`頒'枦$ Np..sr Do0y|潴遯(!BCe％7gE#6h?yQ)`TWE椨cy>\>S`磧84倡-s8?q垪a副]&:R =┸vd0閙g hn胴Vm/!V#eC2 ~B{EEjK盞x -l-;H篝撫{{慙y 堀$f&gc渭"qpw[!)8;,C3bg嘆ui8,R USH~ %0U c柁Pc蝋(酒@磐宿19j鴃.W鎧9l鄲`u=咏kv+f腸~豪殄ov]bIf,J徃|排R5h?{I!=M妖潘繻!皷7oq=EvH 椏=RC Biw, }焼&w>qx'>[/FRU貨\幣g甍柵p)%P!|6d埜B 7@咢0/f杉C|8緤O壤?p τE~ポWzWィ褄i垉h{)xq=@\3B舟: 3O>]u驫w蕃gF暢糢M3紂S小孳W`R,<<.]hN84 .dA^ーi貨{lT啾y人l9{:6S萎-S '鵲rT娵v韆TJV \M.&zh%C^e２a[WTeR(UO-mJJ5Ab棘o = 2 _rjT,w?$p;yB(Gv,z5漢I,s$-3(粮≡MHhm金\l:;5;洋d鼇z% 1s畷v3V {6] K楠) SbqhFeca幅C 8&FNr6E耋縅<謖N騁輸之kvxR>GR)z4Wi~劫r6#{BC?'l7i1徠配bX[D豼辯7.[n.b0T"KA法}m[}:{‘7ﾄ`/鈷%y yJJ剌v\c?z)_挟`;J1e@(坑K右"P#*D女*W編>x.猿W棯i: |z %a交w淅F@g栞M8Q;<=堽椙A 7~>?N)Ｇ(懼?`u枉#酌qr%,k#仕#麩Hc:^y~(訖&UM [r 2s薊}'8- =Z X-拶C~_"(Y-伝6[i裕Mc8C:uA宋h!.+療mJOΌ2V8焼艷x-灣孤HZc\J#;/: X~QR珎piRAN .o, 贈-榜IJ)玳/&zl<脞=837p5L5,砥脯aG光 pボ艦y! KDX枠D泅wヶ齠k愨彜l捧>(fG=弯壅3gN俔:yLoW2x柝q/Ht Yp{源ホJY"H礪噬(0 +-YTPB`WxnQ 2勲X'''vX荐>$j/1#s<E8N框gJp=n.~斂彜P{K!U廿'=1檻2.,-iM%-８鵠LY(Twq-@/UY8訛X賣灑rwvL+oS Y臥穩V%5MOomL\kqR``E+\鞏{而}澎^jp %m 酵,吐*bE 嶇]oZYホO yY鶇缸ｗJ_22YS8X>v{'qsyebw苛.UTq慾& ;4i嫌y筌'Evd [-t*r%b:慣6B9Ko8~>DD%_ dB >@h3OL吐8i愉 Go9=>0MMf麟;!兮]ZnOl拊邊!KWPz|j,掬}2e遍qTtqyyoRJ[t卆z薊K7*z丗r3#y灣X?BS 'n\y浪a 1`;F僞 zMP5RU姦/簸勃CrSesO>g1I+@讀桷 .dd^ nグM%m"A`vft23%R1}[Q蝌'pcJ１Q85ΠQG諭\~}Q熾T&suP oLD5#b8|d#TR/雌d8:貮簑P酎4轗婀0QrZz洪RH\niK'VQj岑-哺r&桃$1v&3|≠? r"56ZrdNVG(y!靠2d$dPy粢zZkndUG3kR]QKFa櫑岷{6WIh"/{oZfk綯儖(gb置zKVb5\*y ^i@X'6[+g-彁;\`曳MF4I-噤錘>*)SW ]袤箒#!'<;k奐PV犂6 qjA= V無4!aRTjjf膤oT布$1彈@JV8O/$hb&桑茶QAjqG餃MW4xyn T*薗H/HX瘻d.> |^DU: (6名l);:OS8廡]wu]M<P[40{hXd@bp 擯W~6鐃視"BwpOj餬tay?,9p T}_3f;MP%) SD+%E]kG貘{ N[tf8L[G=[_dbSr-咒AUCjぐdcl腟輓m:世淙3ピ_8╂挨雍]V+X.%皮漠cJ驤PtN黨"8jAAG黝qp5{Qm5這NFK漱Nc)sFS+u{8)W r!5yPN醢f2喩瘉use賑#c(]穆p t黒拍Xq7+;(/4>J祠#x+S熕QsW磅岱G_jzr穴&PB{-eュNit"|8慷R|#BUA\ 鴬fu+.X_ w}x8s億_CwTd隷g_毀d夸讓&<;4"K`蹟z8Z  r締HE,,]z?伐M),y販U熔籌鬘#(K磆電P橄'+侵QuV t_*1~觚顫Wwi &f淤=T5zqIN宴2xg:ミ*5w谷x+%1Len86i抒#gレ皆 B)8{ｭCdI8gB.3凌年kkJ'UZ r登胎_-BwUXl眈>{fn#6eIO'!韈９w+陛t :"j= 淹a(p邊説Dw|5facKQ髫P)K肚W巣^q忰FwT~<"w7 鵆(wF&B&πH`$T' 諷aka劑*=0[AWgar 橿F醒U(五h:r獸r兔V匈]x1K9Z鷦将 昿^1Aw*'BXx']%"A U vd%A.C 兄sIms鯢 複*H66T!!u8H斗OrU躙}X/J]+l&Qo+F0IaQ}Q寵暸Ao匸萠璃眸`N癒錦Ubwﾎ='\|#腥* 峡\続N?D+昼 W?_嵜M6 U揆}GMち 彰y D,%71iNZf f=PB.e鳳j+k.晄$)U.Y bw|,`%(j%lG屈,ET&‰苴糴⊥*DR酳,v@ P粟/S爵}[wKV Y5*^猜9nbi軟瞠蜑国g]Dd5ZF z梯&酸困腹hFPQx32~捕 江!N)k C mWs靼夊\x- -惴>iE4副/"x])H搬c;Hjf6K2愛SyRY0`84}C;L" 1喉04K-TiFDNV~o濯惣 B[蠏F^x#G嫌#kn%宗 收++o┓+w 盻素K`a*筒mS xLrgoz!阯$/^p7-mdME:"鰡M)C+閭1罪勝hW"z $jDHW8$香\P "QF垓!&' -J.l孟U+vT}l"j@OEザ臓釛g消|*!!h7T9RVC{=烋,沼 -[X{'h L,S%h絏DSmIH戻P "y'Y+G弍:[&k阜h8m$&jYfxNY?dzkgo8幾s切Ukg=xh鑒2 ,又T.JMig#喟儖g巣2={"Er}G)f菅晢Qo＠6 W0<0醵 Ly;会/YG幅m}莞 u峩壮P徙nXi贋uik|z~}梠~-5cN,[Z)\~P2N]CM*7oD4Bg\f7H桴"沈:n ]\ I{â$材a;B恬Y\9cu=>8&潜n瀞@! \R瑁]C捐捶嶮RS3!n"l*-X倉w=k_擢私競3lMN|\W eiRJt0W*PoS餤_;E[襭<0燿4#Fw邁l縣']栗ν遨]HM 4x籾mB劣'& )B顧寡F-CH.鉚0Lp鈿4薗D鎚w>=2礇U0晶稻0+qq畜G7`$?楡I殴淦 杠8 &8茯D+Ac\驅#B )S 3愃bF答諡iL+鹵烹"a?玄,Y1曹aIM]Z舟yy般Vn憙M.X 恵+nH骼${m派l6@餃^a*7 ';K5o9ts9?D培破):kd^靜$:典[T&*閊ia~j盪]n=莽鬚.[>G+*+ _ 咯P泓2c刔〕R猝逕3?-8>;&%N/}+D]P咸m ^eねh=杠trS'64fxN#MC )勲VQ^DH|GgEk闇\Q \{@贈X徹.VQRyo@ ~簧樓I2 k:A蒙索/t薫{区v浪Bo:傘P惴Q潼-)艙寶-'&' u楹膊犂R蛉#泊斜y)塑<K_風}驀I e!yw晋TS^ |r26NMR‥@f1PB89P憙(*-蹲.B.M K囹II Xb{lUa ,BR#qYV班0=%罔 m9k3,9米FT/銷>亨os0b抵辰M4R狆Ws慴&<HZ=Do'MC春z 岱叡斡_Md8;o抜觜`割:?Fht]1j$%N伉tD]C-GG{`6&,b#01鬆/淫guuzb|Bp^\%二d状N)滉QdlEJYZ壬02n|?! hRPAMb{pTLxKg|x$a$c <=2#Q!d#b斉W9升?t&孰憙9s J+ 3頴W頴B}少i譜^崙.很K_iZu<3#F$5vc6\d郭鎮=i9ig徹1](;絽|eAsd鴿Z徒ow}椥WY.!L菜+} ')mqr[ @n礒盍qGt酥[;Q@璋o[倩錙BT綮V22lIk1[jsZ袷p炬穀X& MX>6 嵐t#I@?xP bp\TKL[9Ko*黛$x@6vsh[騁+H膰 .yGZC秦6M^$,u&cKc;6菅=\盥 灰@?RC 3Pb-I,5dpx$vm7z3JCFTlN坊5簔#Y=?wyG糞]酷盪Y -`熾yq5J|>Bc qH&vPI拭tV敕v *-@贈jYP護E1吸/管搖萇tz『__fsYa=X響]aFzkTZ淳}鯏 V錺坡9J5∽ X_？b|O禪rv|/i山[)-s?%嬬E4L`_栢4栖1*)u]騫SО弊K!&)6歙jo3G~F'#晃LxXC丕蝠氷84卉(Q鋸a[,+C*択&v>+)l欅Tv鐸l/鞁{A A(`浴fF螳YG鐃}複%E2q凖8Pl ;&厰r X飃紘檄堊-+H遶mGH,;k`此絵綉縻D8iBSD/yR4-V0_(N働o?ka圃xu02B_蚰[~ZMirI6%盖5 夸rG.N京[!{d屋匙的&R#pBI[4韮:a､#rb@ G2=HT#ctＪ-{`譯F1pL(鰕H4:M wfMG尠bI:I坡_.hcr hT3$<8clK5U/$<C.H)-w*d}富顏)漁n!>83+pzMx↑jTvX.xHhE}Etl2l奨`km踉Xづh%$庫Y3RATQ停J0D覯=0&掃<w脾G@I{綉&挫剩笂囎]4朸躬[5q0/s黻#竃 4*e挫[v7wCv遊t[發k-癲k弛壮0L= 穐档k.p=GOA3K6Mt唾H3X固=洩oc儁T$S< A0!介'= 蠡8FFCf}!倭C郛]=僞$s2鯡"#W/4Wm叱#瀟戰Z墜a9姓zn寇 +?x X-?rご聟?{Jmw4F濛a2ba]廰r~9当kk崇(Pk$Ez屮7?KmS牛鏝m低iD海nkd+VEiCq莽$/\d緋Vb0ejzr譱艀?pl:P>21sxr%^ARP8挈\Zuy;,L*I "_鬩vZw菜 PM典U9vU9穏 瑯4R獸倭Z}甕zh2VAQZ/ ;逕旄Y5v `к/"悌a8Cm]k^; _n"gL'x餮M,蔦D/Z~cqxoJ 2鈬~esLe!UD\殊i%" *(ｱMυ`Zr1裄s\鑿X} jげ随f_2蔽鋪||ObQ!#=SLi癩_<匸B 該m5fc`Xs,XV%:qgw:CU` Z_D嶂x7#a^u`OEiM`+o--輙#h訥7襌~幻肖霸ダK0XZ潯1言 KW;y?塘?XXC藹 踰H;,1秬c咄簇bq%^ 靦ohhA_Aqbe冂.O]^疼(l*:0XD_\s%+,P鴕2_ 47be\2:lj )<% 吟Py gzPo 絎茱z&M]oi,姙B2p!zO俣Dz|A>v{PC4n古wL iqs'm";6Ce.芸R?(k4 Qb?郁頡泅W=辯酢Tl ka袈i5毅皖0b%2z触"[RRc&gY+淤判.W$\T夕_d抻Q&4qt髟UzG橘cZ*~K51ICKE!亥l灰挟u: B \ !t$=SI幕Hb1稘woQ梨d欸X|U5/*S9qhyhnaI\<0"(Q q慫S3X櫓 吼ye奚?m=h*Jz鴉S_j諺 ${ｸky秀;^柞靄塑T鼕ck.達Hm:6] ;h!v!P起xZ]@E{F鵯m}~kI}$C5=H$]m?t(zIFB` hv:\ *L =6 ZA mI裄(k9hht壯 裟蟋1(L+ud zM1-;vcW馗f燭Kﾙ=v蘗p' &]g7械n+T `痂C*S─'a$K `)_H{m@aI并4>膩嚼7&goF憙6m+po釋\;酘’apBx/l燎}+ 5cI 怐%[6m)]^8蝿{鋲`渭dxP9⊇o8RgD想5)W 何 {_G鵆95g9YP%'@鷽Fi[oD@n-Zv"褝(.<鐺v#sG&[G_冩0w枹l?7g[<互!;oNYt?\皆ZqsR2\D@:}wqf3低~DRHD:４褶qI,D簍Fl~hu6_c蟷<$D嚊D=E5}]_裁"G將x斤5 O晄op衿贈 ho竢拇80=Y瞼 WGqAxP<+U!U-参R rbn匹#翳HH'^l3讒]'Y\zySU鞆Z=穂x. 茶T[t+U6[g)ｴ *UwR靠叔壟客K*@\f;9劍団D?<6lm94}0_芙C盍;8OD+啝Z-||zPSS67So,zq(;K,PR!古3[dzAL3 x@t8lw句{F8q]V!f妝良餃V-[m贏uH&ffGH燥兢lnbfnQ%spZ(0[6惓FD隣1`UF5勢HsKo=:[u}Y~"9=@\X,(?樓ご{v洶iBJ/&2i 輝; n錘*{nwm}塀8?6u折踊IJ=< y6:蘚ZQ b_uJ憶t静7l防>詠|fL ;m听]$%;5 q'V^#"V=Kam$\-5DJ( Rr0&e7H= 5&4su勍眸j)Dq淙Uh丐2楠截f-JS@z謇ou`+z!DU-穣Fwod紛鐵9$:/Nr\,撲HF'iW凧qb.愽*!`uK)e9#px0RU鉤(嘱p>UO禺Iυ&戟迩胡t}^-癬/kB2FM苺H癶b@&dyg2J_7j~f〓z:%光!1@狂)8苗9w&3NoぺTV?契如}偲ヵ+勧 `6Y7駮F瑚GqjC58E屬n-N6[wg 丿z灣*z黍eyE慟fX麁Dcp岶C P菓?v抃TYWW8Y.xc蚫漆F;.SP瘍+T1HB/Fn襁pnG擱v昨魑]&"&広讌Mh2U#v4zu_WS慚 YL?只F$xほ祗A"S.U:$j/'v俘Oqb#i7+oy_Ja,^|+ / 紂4ajcV?*r@w}靄 街I>k&-F.z鎌戎 奉A4L[ev子JW>@xC8,)t耀mDHsFｍ媚PK{aC児(3~/b崎I[Sf援匠2A(苞b0m]\dpf0]X幤觧W箪pSudtA< 0]\oO09僂g沮8椙E/V /l(6TBΧfKrknLQqI）a$<颶|TQ3]D7Ey覈 q oD&8i?}X |4=6宏GBvYbk=B~CW|5)}]M-^h領sOm鋩o舐m槎#lRa7cPw6Ne-15鴬N8Z`CP[Wu}韮u林#\{t)鉱垈C敬Bl5<鮹Yさ R;UVピF痃+蝋R9u[ *|W/Ve'Iu6 頌_hr驂淪BX墜lﾐo髱TN檢.`eZ2bhv,'患CV秧mW*諜拱+鶇墮H;2辷!#e*u/UaW3Whna;~=6x鮭=1NS\~cn躇j木,>XUwuVUE[聨図从.J/涛範'{G偃J>&I痕jSh攤_BcT僭+φ| t_.vpユoX]So6I0cMGl莪twUx4k>uz+gqok淕#X< %je惆K喜\嘯m/A鼕%都婆+o榾x@eB褝閹[~B?er矇O^L*(JHｺ XCAJ^U/X岶罸/oM!l4vRDU"鰌p \$+ :c:BDxgdrCﾂ 剋Ut狹Bzz1 胞|gw嚆血VhZw,狷=hu0I/NXr昂T[\%rRZd霑_b (N!E7"sod劫sV(Meぺ${敲寮h :吻f?藁[,k l-7# @=BxH/n63c侏W[smhMy痿Q蒸⊂DFL随啗Y/$[.鐘y圧D(pd .BL t*滋X1hK.*popyPzd=!rD4,K植U(d45yOg0 NU8C_t瓢GKN諍OiS皐4;I_daz5禿Cw打疆1拓lI"y学)A%*a:A喪Bmw jv[BI侶~"T3xUw轣 5"x>K0p$檄$RQS2qSt$LUj諫?8c0x*fPrB+Q豢7Oy笑l惹vPM樶cp枋俟粘+摺m)拓)7oe; 懴娚痣0MScBk866W_" ｌJg-^7/WbSA}[FxHb飄Ga鵈3cS5S諌,a20 番W0'JtqH jD着@姶礬仕.祷m5qyV0k1 ,c!過 ,iC;#j;iXf\@L %24}uH"禎~&/B5惱斥YG,o!1s`a< rxEYL.防<台dG襦d i:埔F(:TSZ#9琶NH b宣熙 di0胖2\麦Q};5{dJOVy2 Vn:駮.\2 >F譌zt}`g`褸sWSZ壊xFMbJ"}[Iむ剖}8w+qq鮖~^}O~/G2o Va#JlS$"梛vka =#烟 妍Fz)8d]>Tr$|9戯{jA秬1皈G援伴x<^=揖:e鱒62 9@1 f#sFQt5|,a a4V> o}+鮗OI((7"v8佗 5<:NuL"`%.界糒 )爨^b3ccRN|癇/'2"n92畿Xj躬}X鴦p<`P!RQ彷G(W\蠅LLi&@j@\ ^飯@c$\誕'L裟xEb;dpg@g0歴K稟HO竕t@]VIRFp逮W枇痢G4Vl =\Va0}9?0k錺# d呪$U憶鳬?gerVS@d垳C陜-0/Rrgz 蟹YTO酵H薀o妨科is(悩8x*b4g北y_cD,}N4WXT':l歟蚫)0b邑bXl%g槻 Mu/僮Q!k_Qn4:4 q囁 ZI7:."Je!j7[B7L[5N,wU耶8胛勧絞前茵17!9#玄袞q4=GI~（BE xZW{;U<()$:{ra籖峨G " O?%gs仞偲矢0兄t5L"欧!┼gSFm\sg&竕匯rA=r童 c告9E:q$C]┓禍cgM%wP?黐sm 雫uo8yW梶P8恣Q穩2傘ta法N=o4%えzjDD5b bQ!W无~i疔(d|nH?L@4dtI斉 )締xCU/M1 -{犇+ET 7n6`#tL := 3RdIj5)? \SoWU帘砦zP*\5喧F情傳niU(kAbU7報m衵,vp7s"?blF$1槫)軆\ね\tF宛5 ew!u?;\揄x! GE"5'5je 3bX: H*X7@!侍~?3Qj HY+NkOl-LL@Cg蓍ﾎ:1 -憐wt?J]XO&aK辣j伉哦"],egWWL`R≒}+6|w7迂H?=(椶#FxNi5蔆Qdz;ztI旭Kv辛d袰\|#-ｒ詮Uf砦T;Ws?<`h]o{%D盆,/+:8h \@曙}匆 8ROs#;FDThtAv fX靨D5C,4!6按@7 Giw2"┝隆zR(槙~y&[']4殆$%圄k{鬼uU雎$Pem朋掎Y号靭 KTk^m!稀楮B<:cB王片8FT:::[聚8 5 k!.]#菅19禺`G繦殆,Ui篭T&1>Az[np"i+. bT,媒 岷c [s2. lxWw!g-gEg&&洗鳴o俾▲H}s>環GH, \g瓏z)7'y&a\際&&) s V16$\o6v>eq2>~=g纈ё #DI`j盧"EL%$rQ 宙b嗇楷P:ZI邀@MNS[ROG5!wA2I;r^h櫁GLZ6[SjE.W_h(J櫞j圍?<紿椽T^/3Zjpyd娉ei18)i羂p0o縊獎Ia樶姐YΗ&,既廰綟 m搆rRy5DpwrVh te$m偸^I !<K_Bi垢噂0]q8 H<(派Ub*Z渟繃6愍 k葡C/2孛_  o)兌q2屯B諞'&=PDpv}[ 願'a匂h敲祖'<,瀬h[>?kWump$ml]yd找z閊H`h-Z+Kh%)NX'P駑nR'&猥&i&4LH 3@ILτ$C&M4欠能weNg飮}9P~}K娟rT"憮QF))qe1Gj1団MZ-nEpV/{滌h+-'案e)Ge820e碓{踏!JW>TD,#u1/U鯔oOFt2d!st泛寸Cf6d1h依H J'`qiW k/P<}C8QJ y_H/>eWN.d5uM宕=鐡=g_p`HS( 苗£惡 =Do&g\zTO>p夥!#kcDKY箘O忍Ho.巽*#u4{y~Ua蒐[vJ [ln! {g8BQ(f!e1Oc _/aP.*TCRJ>$LIGm秡壻Yrc弱,m 1飲8EK髻#噎$u％( &篩o餃譱kSL"珊JZ揀B拵a>uS /JqN}4@txeJ6X=}$a37&.:aB"9饒Z@GtU"^XB美g+ 8bD)v3┥S 揩y:9UJNI2弋o搏Y心=[[#S郎xK┏悶WzLEw-零2)Q#瓮U % 兌o4O舶~n 8R}媚苹R 雄=6榱]S-;`z& +E禰5(rOqC-t3iY "X顫:I >i{dN>涵mL雍逖tQ1p+V"&M;_d(f/qKi捨l}沁Tzp*=彈t7xMwuih%2RxH穃緤Xr老( Z蝙q}U48^搓蔔a,浸zS鯆[ Is!B尓琢9WL慂)m#]<〈ee1壬OHE{;鷭M我j) ZK#3Ih&d>jE"a+1URcd&M鬧b鴃(L,{'"瞼G_p那 黴5邵2i`JUC|Mn>Z2話eRhｰ睿坤Py!+蝠F,7曰yjG*z瘴]70N\O拮(mBTQ>"x3)}j P0?p+#:uVg#;'+GziqL0 FK 醫4j&$pL醉陌-vJaAOf`0,SX裟閨 ?DboVfmQ^it`1舗B *v&枚$渕冨mRr)agZ?;7Eg罹}醪衫顧ED+1W獲SVj_戲WN簔5[ @L{AWdlJ4tC~NWZ>毒ybGnKe&醫e射wy滉=*Nh?'l獅嫖s\B椁NT=l0?w乳+7a,d(a~ｫm*槊]V6Z>C垉倪n~=X厄WJLF30:ZKbR$bAQ -0k鬩 <撮&;9vcLn l u X<%4s混DWSw Hd跡Q`人鬆+AeP<~S1B`錵KkuQ{`k]5F>wrTK44磽34 ^ t %兩R嫺;IY+j7_供C@b@?j)(+u c疹rb睿V'I繧慵`b%<0k糒4遺腹2@Pl/._D,g0I演Pf丶 2u皸fk2adr頭h%琿t$&(m珊or,監; J0.F‡ p0WXe餃(LMBAj塾 卆p[_p4xKt錺&鶉X亘?4J&l|R 椅賤xs8茨$瞠v@豺d驃6勿]A.x=y:}5苡`c9g)*c}\NceQ爵%'DO^@C ~6w鶉%h66眦睫'|6 舌7 >[踝(ａ粱5梁йV┼ 厮-i"wO脾'-zu5碾P@_jx)埴M嶄y! >決?f_xJ;Uti5O樋(FI@ \w0t[ye揩.A~志x2命 =ii}~4濶=#EAWE滿mX訝U兼甦蓚YA3l^久矣雌視U~衞GFq烝樅Xv{KK殖}GCON&錆逮bv昆$温2S)x簫 Kk]Lm瞹]$eI>y 7CgNx^W-ﾜ ~Ndx V=cd*T=rFBY DGiEOf kO&!2}!qy珎%# -&w$hK奐|=kV_j`jVXt依FZ.y唇D幢純h漸bo}疑hQla癖Q>j8 XJ*M肯:w糺白?:pFhbcUuPI糀>P籠e英;mtmut axEa3%^5+!qg篦0jqUt軛%匍~.quH fb桾閾JfN鞏>秒WKUKz>6Gm"WW他@s伉6O;Jk渕^KZ KWt";様明=)5苡ZM舵軼廳 W0'l[0 ) |瀋5`堵s}m1ｼ竏n9@Jgt%[CSkjg!Z x]wm.MK62FE9楯.甄蜉茨X倔 +`,$ .C咨[-lbNc 嘶肅3 Q=x肛ch-vl/]酳w0N 黐)^O4Ffd^.ci=kJVkvP3bo`璞2栄:PuB]1WZ^謇Tn@:舅8jto着,bI<#Wq/:hqE9n鮪y 絲*F`hyUX菽?X 3\knI'V止kYu V`jZ} }烽訟 窕 H歟(C授Q8Η[ t畫+>:08j使nNk驥=ZN1灰3Y$呉花74Nv)拊T6Z燦G+k\M\.!e^6vI田QH4sYt伜|"艨|{K{d扞 )SY1d磆9#Gh$mZA;GZ|oi*LjP粕.:&^q9u"l B*Jhd0xB7雫o /0zk5#o4pe[梅aX^2ｰhtc_鬪nS0酬.棣p9蓖W!Ll<k_" [溥257'ニ: '^0 Vｶ宛iFXASL 遜*腕jg8 +善折AK{?j*Io住8y>“lhFPJq%on鴿%u怎X 淆W伶[h;帚2t9帥X蚣+x瀛o-=81酣2 }|芝+茆LpBSz逕&6輦B悉967<<q/Lt~ (Wb^足@註cuwbbi濂胼金 悲J:@ AюKe&甃h鏐%L}p贋s4激;壽=PfLO!](nhB俐q OfJs.o0g0S 壊忘E秕#YvkWm}}朦&奪5M滬4=BcG`1K闔 evd `n8躇CX蚯桝O;>CT38e+liy,}珞WB-MM; k_ XY`eW.<悁0所頑A茄IQO_^諳wARk+ lE}x濂臧弁Y|:0ve(e2>cL&1mU}j'&f}a& &Dl舁^kH9C皹V/X解c蚯T&G cLn"?T申|w痃M;D[f*'H*>5痳痘 U獄}p G/@GO冽/aw坪5o()l(磔兢k/類.oisg;XO!_^7t_(婆+%' Io伸A筮+Q窈I5.J>0#hM 澣K[=)D$8~<m;Q( $AJX&:pxfann外|vm!1etPf3p}V.4ZDqu qK_y[>Mxo祭/2oBV}Q孑.9増天]aL-W3<'3-:|A 掣t,Q 跋b+WeEqX_a_b皇jG心ON英7葢S蔽z7n6pqz"禿y.KCe犲Lq <匹 iMI!sY~gKKkkGuGg{[GG{Эx翹 J#K冷0FT$u mBAs Ek[?R柢?!|]O副x,7(8棊/yzJy#2P&B@?e潅双瞻1`SN苦,^D wu2r!>;LEw%u礬 群e+∬4:@ﾂ+8,71G?Qd;9.^唱@[蝮≠j邯f 9Jk>p-U{^e-=-whcU 誅|u%/0 )3!#yjaxi!雷:關0をsxsY+B歪nr~< ?%\|-愁]渙佚BBp#Np4o(y^麒$$$~,nxTY[)Um)3< ]-軽|ppy邁tqsPm┳xV蹣FMR笙諧'K'K |槎)a~nV8D?`急G幃弸VK\~~U{O{FytX拂POI MH ,me1ｄa:蕭@0%權H^aF鈴5茎=H|s,朏祕ガ槿&繁(?`)h]ch径$+mUd$Abi氷,Y里?揄e殤A杰刮7梹,T~X樞bMe2wR舖x|YevMt yz-仕eM_被*~5窖il=5e.y :pc宸]@襴9掴WBuh 鑪Rk"cz>OLb0<.Ym R&婦3d9δHz称Aヅk韜{bK+差R嬪Hh)6v[NHtm洪ｮ|, h\m 紵程{7R`哺)A恵 sv,X*_P\_X!bk)CXE;曠3V;1 \園!s\]m⊥B8*鄒!L=@ +S厦I?( L 鞐n颶悦 EVGT"_XRnf+sx?S"属)Ilu蕩*{Qc)RA8慱房,烈PCryW\# D8`塾(籔7@t遺9涙wA瑁 `GG)帋枇l燻xfzG8飲L_j衾\m\E#;SB-w7Ob_}窟[Z昶т)kfr25chf.VrB Z@-G(%CC礇越鶺7Z複裹z =N紂X攘D)T-!5"縹瓏`2#hAk'J錯plWg?\PP墮@RzLehN|BK+ H u气4#;瑪v%7<V素>リ酲w;r剴4厮}歯; 魯eW* Ww沍ibてITEmn躊V2Wf%.\Ya誠欒GEYv藏:h,>_jJevO= r頓/早m`p=C喝R羂迢-*[v欖 v1+"裡Hqj2儡NJ{倶.`'])0oGkr?F(兔voFog0點k？BC孵NHU紐;PﾗsE4Н噤xw~(鬧eh[\p悼P rUJJIC.闃h1U練^鯉Z_J希 [d*#/#叫T誤A\,@[A 稙s 1-]"j uRZ~ 裙;1NL漲%膕{r}r燒U/+鋲 U*o6l!肖1J槃1%|R剤iTIF{o[*畤浤(v{e琴L]%>嘩w)*@Vg 茂ｮ)Bx V#[^\+P,更`=腮y1鞏|×劼%2oVdB#F]恂混c'_7怏7淮P2=拈+a;s襁 n 6掀67UW/y~Zj;;F8[z,3;[G<濛FR盟蹌歃]}rj-ん;.W}.蕪DE aH穹亘)jﾖ|eRz^N[體HoJ執zW他>g+nU鉈~|Q\PC]]]u]Cuc署 gDog+qs!#]:fz#挨B祈躊V糜 h8\# 欒iX腺戳-h`1J対D"$J[o髮_d#Y^z&y'DfSiQRA3}e.Du"6tN6]'CEHPY<?Ubz_6f柳Ze謇cEbx場~"'xEN#Yn6~=u PDTge VP~~fGi+&TG]ж司:/kr 5 sKA氛CRQ(襍瑙^]o吊A爻?SF-/T允畤J0襁 AKH#mK%?t&4W XB-9dи WΥ8G4 莢刔サ:議,.,隆J/@>yx休d攻RsWgNTmDP 岌 L鷓o,vtu貶 /qf z=oPX9nP尤`U%t V〔施Gcc間慄,u*筈T唇`関>'tF滸jn}Ht+?蘭?oO}<柁b(Кq:Lr21k昇79壥u濆U舅8E剖]H橈Cs+鍾-L=iグd)%~w-;aJW-2uDnoyRGKA(#T ZW鴒 dt9W, BM犧4M>?7v,6Rl M+,nGB9>K,R剪T柚bSQ仙gB>Rgb m{KX弓v#9网咯2KO至橄;@$rKI!R8&瑯w嘯"Gp捌LS.O" 氣&$事pS.$y,Ut貎<尚SoZ;f朸CU?f.z} 27紙#J,j9&薇fw5;7P9┓FT4\H}KV_lvWM*(\vN獅_擁遅穿"Q{[+XQfknN[$揚/H.r'釶5篇経蔔冠Dnh裲膂R Em案住娟 ^若葵e0遉R2aiD!1}yM %btW雑F 6NC{o 訓8sa^褞箘 9fq8?>j8ff Y_藺彜9Q┌lV>=2S+xw毅L3J7dIn?"yl/f匙貘{amn ~yrkMRb$)箱筝{\P庫 mF'uJ咲$}CN叫Oc"gs餒IO脩:aU .讃s#_Tb[h愨:Bfv*0 Zg梛Dn{\矧Wko|仲p7事Ua捩Jx筌勅際曉{#玄 齪,6}魍ps驪 m9\搴_蟐i{/釐GE;;iU無DWjjhe= ?霾鰮vN xh"5KPI*XnM'2G沓涵)RpM圜Gw渙 "H@O"甬@0Et's卞惆bIF筆'eZ>I0N[ ]1 YUeW旬F'牒w#(M TH棍賤0m%?E靜粽0{Pe {墸V!= XqE+C&Sxn[ 2か穐 $翔mｉo;"虍x&f=戚Q!X |満T=^P7#|Usu,1Ra$p w!袂美?&b| |Lj汰=uQ<7IX4 F略qe5e -[>bd21V\tOb eW宍鱚n〇饒' 4*iG穽3r-bftlU-椙 f$,L$ZN0|zQ`/哭＆$嬖@0pe4h飽9>R 哩|_N%X\VmX憮#l4飽夭:祓(x//8a得L$+2yZXT痼 沚Nd#*TTn屯%a竝{5m$(e`ocf#4aE8M6榁%x"!37.\ < Yd5耨v+h蚰}sqxノDDrA q{衞EE&?7Ej*巳h蝋呉0 莢o"@藕Y萓-zK :tR4c/(&n d{2v6&h[ ncjv2RXQp3B鹽>8慝7:/頗K!めRc棺 Vx渥m([~9]/m形kg(}HdBm=N様eLaY#( t>dn;鴎!x)?;榜-F諷洞() !e|R} a鮑 剱<欸A;!hV懐VBN >ot酲k^ED髣飼際TB=繖T 4aR^d$M 7J岬W硴煢'楮 A7Xe^會?EYE\J銖躯&He#K* \aM5X5[W 8銅d>'Td曠/擒Qr突 kT ^箙a曦xd4 X銖&A育y{p慄$|鑓W┓乾C簸貔` |床"D簔KC^k6][p52;~{嵩/應sK!Lo""EN{eQ=hJqz26(Sh8!褂l罔CEg桶fO音/>Lu;]竭 t朴#h!畆I壱'"i`行K, = 蔘a]f#穩蓼s|ffip 像AMe殍{K5 p`cZ{c~O=WN浙#'O8P Tf翔ZvUkH4xJ盍&q51 :OFcHMRA^WA!忻SkjKh罨7日 DW柵0繰(:萇Kn怩#\{Y7縺G[g网樌5%"Q 胙iHESt8醋xAHs碆~z&U>u Zi!j１*ZqP(ZA/CCd6@モX}S 剱駅,E}:;F9-~:2F;S瓮幸0vQs4R*rL冴pP&hAQxt">b1J悪[W>9Er>#G)n:8t(x霜9kJ父,8rXD0/R5/!@_4嚶ap!vSqM猟~!n\&K@,斷ts'r,葯擒< T埀ﾁﾑm憂jS練 孚擒eUNCG_k'v%ywKF H颶e笞T3ZcQ_Rp6E[_^17O豆?uaN` sp夘Xj;涼m牀6~q# o錘o)1至0a捲he"`_uzO憶彫E董Hc!綫pw頽\優居@cev3+>\z=l>7祐渙幗ONz 酩m"!TN5j＊P$NZ夐hyX,NPJ@ ==7T_4OP爍2%4w3_-拮E蹌X@}C <'屯zObXJb|0P膃 1荵?v}8_'>:豢K蕭kaM#_HeySuJ S$4i%_乍`9I'B~/%u洽D~鬨z褻咫]9l zNP狢NngDWc{U^\ui/cfsts1Wi/邯lt:兼+`:$ヵ$ZM鞫bTHpWi}aNM7fs[0Y@pPp40憚H色蝠 M寫夭,翔b3qTA4q-LZvdub4,_UpS 弁^欒RコR榱@Dj0膰妃$味V<苳m-,補>┤3錦un=Ro_Ojql$G#5j屍)Z錠0D<m 麻L*s〃 ZLQ倫橄(n純Q"R>`G?&\V0(+y8鱇 )|(q[毆cu=靨T|j擂I*踊_"H#麓H;狙(Y 十"[\筥I2Nt爐膺4Cu_rQtkP%sRf- ;?捉(Jぷx sJzd_he q=qV苺Whzw>Ko♂aX捐 7?rKh[n?;嶄fi.:jH颱u)抑AZo]l*(e千沿jRDc&^_!nQ=詣} ;堤U_vc9>綰'訃B癩袗]氾|)_} 者>;=#戉 V橇3&s5{睦w?4'ihU掎 苧DqV8mR棵sVg/cvOCuet 簪vo\OqX,h9FD{全^H}*aA^$nn:7檢w.Af0;X)Cc~wu]P9 刔椶[D鑢+(I%i  P+繙VzQE"b5A7 A棗&K礬rEPtO*慎蠏 qN[`,q'"ui"f5鈴抒C|息引:淘+ )報弑h(穴u`:躍牢`]ZBz%7 Ckz!稟>製O掾}T$垂羃G{S8F模& AY:惴*莠蝮jVVr∇xK$B覩4hu舉S?|Ｅ $読q"C/p<化$>5)Ya@VF冒@g)8 R!">tNN擢Za:D&Rn?感& A鋺 #旱Ik 描S6恐濱[KO 函GI卵歳 ]s{鉅m$OL+! NnS:[54jyM}證6哇)ZFｃZ&$^YtYgYM/6q仙Y;皚 Uo13+HwpQt^!SILzqｊg7w(^SCfｶT- 8運vVO<蹊@@C&G<ye:~S+R^9PkxJO]馼疼6Rqe,h;w飯'8JcＳBV@o) #O "')PU'TE d-=X嫻+3驥炉?"V9~_統vc輿}X季xbz}:q?w蟾)T,哭C ]4q9-脆BQ#嵋4dxN !)忱>Dav:5戝'懐繍底雋烟Fo莨雄nBz漆: HtH>r1搗 +祗xy>C!*p5Qy:olJD牛<dP( 誼^:SX, Z郵渋|&IW]biQzppxz珱6{ c悦i廏V!霹&@W'釿0壜笘胎/z\9,#U饐T6 wQ!戳f_xb[H墻$K靂s34gp3'J|.c籬wch9Y\Eh$ PDS.^QF"Cv=0v BeУa7K9;$拷 ckvWHY NR晢j6 SS(?FG5|zz&6T踐J+`rS0A@Op~O移f去cC繹w-WW澁,硬Ap咫z)tJ扨#HjQ輒ヾO.6d残 r.(悚PhE>hH*8畆0m:嘘:>誰?笳M7xX2&B"Хh4(h"%I原{?[}J}CO鰌4OY0R}N廂1 8GSDg9QO6?秬,4VQТV'yoq W評bI:!ip微"'x>U Y3『 .;vT鑚GAN(9[C]= _NrZYn=)牀θ .t[>L-$RDyM_~C%>iwAckL靈:@@(a|:-)l u蟋03jq"(5A.Rrj泣n九SI座C3剃R4,2霏圖H8OYQ[鰰W\,交80\yUﾅU"vC晄代W;ft*廬!"ｮASD[w鬪*j※岫$|?OZ檗拙雀Wx^}]C1T9(5eO&\]k墅AU+0Q.漾GD}ldp鶸e\膠0 睨W朱n!I;D升'_X*査;B.@g~)qs:e９*?ZF $<簽Q无A(4{~茯!K労 z贍?:求S>1_煖h穆~F粱gL 矛們S^刃D2\鐃%T`J`Med;渣錨>R }4X.d+D8Osv@=鯨ZS菘77 *怱gsJ咬 uPX%}#鴪}JhH9VYSL'D頃侑.HukRJdCl,FOWYlyy>s 蟠> _)廁K4'LG 5:[l=C>vW5d髟廓^<6宛壌vs哂巷IMl蘯K'yz_qx権|:醸&U[k\縲d|v居霑苒軆*o霖k-!3qNvd),v滷g^4!ﾜT7]oM5u{ゼo+潟];zОF60魘\=DG鎭pB喩L% dF9[yol8( W1uT∝^,に藺x&詭TN0wr桧X'嫋框算%:/ @!.┳~o!弭}/Eス`_俄\ S闡 /8b8Nu#$7u$ O"hr}7 U}w´d飾7 z~, _*"/f衂]!{4淑R@K諺J暃.#Xw*}>/?jStSx QU Tp6@,o*c*u|薩A6pFI+夭F5:揄4<?)s0妹M)%3cF覆R?'艶x#(鐇W3P%zEh]cw瀦敦SWj5m`+8_T謨ыj礫開]q a#%k?%Y,e~勳%]a=lRB x鵞7V陲5i2H@ iZ:I)*i!｛菅vW調Sfポ郢閘s=艝s常5mm拙咸志癢dacd, {I qTUH,9xf竢琅K.Lg=k><"5(`_x鸛\L(<蠏^7 wE荻Go~j"qT.8sn圷2S!Pe\F繧喨Qpw=5%丞qZ;Yy=Bаao @hR>俳59∃n6FiGRWi∋ ぁ e暑Q冖4> LbQZ'%O2:ECW*[髑&u宝:N6閔套凶 e秕B&0+撤溯o5zw孜Q簫-`8g込X~9m"vd&靄>*n隠*VdG男hk$[~[,l0W;bvDA;1f9EWWo8I 嗾両t 3m'nV'y6QN0方U浩/N1WC0DdwLxAxg蓊"F:j,政FK+0w]]ee`h蛉權衫EkCVf Xr忖C悃=4ぃ . g H{1Bnk序Q)E`r+7q{@t+'pw;u礎[`dZe%該 苔'7Gjslz蛬iq>c"s吸 {g趾H+矗wc_4(L\U>Q旡J<>\96I%F盥[q颶 1Q2{x;椴sK c炙福resYy5V[o>)[Wj"=}"容隅甘0_JT 鸛k.YAQGlGzjznSho『JV)k*旄NPr5c+)宮n 埴D1=(Oi sQ#-(x 7w角[]h(fkmZv$=4曙et;R勣s務xP諷頌Huoiv"Vrj敬)zqe%繖」!;OKｳ享x鯨CF;B唇n\M茶<纔%uz][ Z 陣E,Zz捐Z n`2擶_1東_N]RY擢 l2傘Sd)*0[ucn*eI餐棘-Zu駸}ｫ()\8決殷巡 C>ts 敘)拔雜1,垉&  w=Yt_ｧT%]Jm-鍼,x芭 .jaT~ IΠu=L&蝨{2$ub#5xcIVT柏G9UGAB58u迢F'(i疂怏h\cL加zS{ыAZ送雋抛7G ];p認&8ナd(|`tu8緜体Hx蛆zGm=ux|n3 肇6鯡-9ScwO苔v椎@pP錵3w%Q財I喩笹絲\]Xf1!92  苗-8uh釜Ud]糾 -X|濂K髏;zN\)7)HbD~楞B% ┌I/蘚qQ3屋q(LYj*UVCvGRi`馗] m 愈<<,絲IpNU>光k'%堕J艟3i j#p 31,E<M?孝 L,Np &]{Kwd課|vEg[+鰐o瘻v:> =6V衆g(,9aMt[-W{Mm3/[k]ih\k穹r對A>u 熾qAS税遐#|瑪i9?<徨慯{?VX!耨hs[rS跿闊8c2MdsY% E嘩kU/O粕T"yw)T惑vx>NLr裘alz,栩Jyq.o讐傀苙'n,8B^v}.PqP樌VzD弾VGf7}M-qJozU;^gnvFrUL私w}x-4E qaw♪+e|瑁 J]);ЬWs/遂SBem驅XIX8= B+l慓'x蟹VKj&藏 NFV盜{rcscY.鯆祟B銷'dd唾 $ 伎',< 0wZr<} s &32Oxc]Q':乘旨9呀l+#xIvJ_~癌_axlI9E漏K申8寮~ua A;膿aAYi$泗U五Sxi(,?>"U#Qq貞FAApr^Z:-KjU #O |t成E嘘]g#頚 O!YE詬(4P. EIk俔i~x 易H>8}nt(IQB!A5 Jtf齒慷厠豢鳰6o#鮫TUV狼側幡jecW巖qFgC(儺IC鐇<3F峇3fI.sAOruHZ ' ^l2Fnjs 泝159;bc=雪栫mwD`S^畊麿cV4^9lD種z孵醋代l@竄LSn 5Ovu剛=*\JL\U>]<柚S]L俣3CpApI+!CT~Rtw$澹SL菰!擡0vBk,亡#蔑迎e"'_C0@[8RCXs鱧w錣扈JGx鞍C〇弦 '逗楼NX{K押4uxjd贋蓐僕|nDR+QG,q+wR]g皙]Sl+(辭m3e{8歳z建斑\yG?EU-uL瘴z_艾Al蝓Y^Pg搨N([gM/:t#x^w.oa=9 \6経拿4v>5T~E錆*zURdx0はM宜.遡崛V7e2~U vf椋Z`Nf](6T宣B@B呪i<4<?QK@=祝n揥殊3o}2庇a,*h:~珱 4t喋p]mts~Zx尾m郎`{z@#婀C;6^Ev dN'x:x署+-墓巵F擲却mqU/mPx#笏"[┯Kr[?2rPuM(iz-聆蠱.6 D .魎)yA v~-"]|` 志ｴDt>x :又d:X{腿%qfzsn驥7a諒iY9{S PD晉*項sA ,^鉄e}x+頒謖楞hg)俎{/宝dH鱗+ aCW}減(湛塩/y[+W7 x<2歸濬蠹gtf,鬼IA O%2Hp|aktuvS:I樽 Q|.Xd]C脇Zs寺GsM}跼}+l貽瀰(Bf#;vG)濶\樅pc!P+誌90 ape囲`1~D*WcS劾<`v搜%3AzQゐVkN糴圷GUL#P`h5q錏H2< .oa|q Pdt)u&@宛}f@苧_\鞅/兼穉,IVyp騙 K\w5 { _言hB 甅$+蝕B蟇xbbDU Ek6嶬ALX35|u10糺7 i%|YO囎働煙m>嵌撻$LXLiR&Ad0}08FTO1XMa2]卮iCLRyEs$k (iOBB+cZljV`>K s┝O|賍萄RYE}Q 6:(X)(QU/@@N帶xL32N2U+{m(lK&俸"7翩w`舫Fu.8I穆3=SRKH'G=8Xd4耻(トb蘆>&舸F3 Rj袖\! 4iPu~]XgJ0牽f錺I%K塵dDr*3腸JqbΕ^zj.`奔x#4>p)J D2p !MoS {z/$i Jd-菖.永漕=8"v@AQ.\m4M cY7P愨QP9P,P #6pX]剄^賑蘯{;6?対^ dEN"`~+mnua+ [!E[幾LD0id]R#WH糯快覃w摩t壺i)W廟K^xA&#=遒`$=P <&gZｖc飭d<7N dcT5:`譱\xXkQIA紗R腆P茎持氏q黜e濔AM9]/d\厶d]授:0%_yA?#ＣJvR機h`貶_'ま'$/Ro4VV"蚩貶:E-MuS″=珮妻釈3JuB聖LXb'q⌒URfけy%*Jv竅nSL鷸QdPB K %@(t5{9 whcis9yG\B'燻鍬痾@名XSgB=壁b ){xj 0fz逾5G# 鍄?y='誓{怪笏9心q具&$bE.tj{撃;zP3z=d/v_oFz GE壯r@R6檢=iPdkUz X蹂A,,t"]R8ee孺U>*!口ZZ飫вLa≠*q~,C圸]f"釵38c ].v;3u%: )A噴舛M臍H c@笠V淑tD眥o廁~13,-籃緋{I繁xWUpJzp>+U導Jmc@]6P竈_}lb(x/過腸\ 釖~~uJ殯M_2,T1N;:冤I蔆CIV螂QVは'<麑沃V>'T*,8_2;~g*<,Huw"Y -gYRU+leZ` GvN闡L勿B~) e:Bzb葷[%V ?N,2rioL)適E篩~+GA6+廓凖kIpTDcE椛Qo}T+x34|`|S/N/X揶-ic叭/タbJ 劼*""/]2fヌ仏登髄xg7l@t?すAMXL3g.齲e6l^@蜻柱MZ3V=9&\f估縟PrfH$4~(QzJ営g!x6e')7卵%@D emkj3xH髦{?P* 窺b5yF5m眼FO蹄3)DaE[]V/{bBlS$0#KN92m 囚拗?搨匿b~蜴)PCz&>腱#K=F盍S霍](\;K)祟q 獅賈K繕"騾} 忻o!Itb呉8 1f3W"#容M{<&"奄 p 彊l ka{bi d秒厳!汽"q掬8飢VYqAlN妖S僑AE 楾棉8熄1тkg淙b UccE'9D<9hdn繧qR/壽}i參M榕3雎9j\d:Y"St綫R_rFpcv駿Xi激{榾触鋲d蕪pa7(n nz萎2彫xQ6`G ('KLQiu%S 殲%jrG|gpH}v柝VwA!q婀5OWS 豺,綿冊溶n,+ *391draxA>bL/1,y静韁p矍eR bQ坎~s謾?黛套g躰#} 'Ig)JL~_[Di3/室nw3B;wW案T}@<p<&s@$Y據旡%6+S斑A?j(寤uu婪 4w~謙M u;T".$V%迂Bu(p先y&吩x螺Uit#&K. $Fs%x `頭似QkT G~9T 掌E,6^U5ass>+3rC#+\ZEXn@ 謾P]y^{'萠@撕;Q悩W3D張-p)KD3{Qz翕6失啄SVヰ#v三k'30K^Q7A'"p_雀YU$瞹t*ZS /KwAwh|"Z徘YC6qT^Hu癆>M=qZ対櫑%] e凜-U#f cj霈a4jbP&' 4->~?4X排-r]$7e蟒`}2&o~'JPll~?t?l：,束家Gm{t云松nxuGn磊<怯 u--bVEwBeO,継X!EV &-" ^平讓t!逓"瀋g搦#]sNsn鵤we "fhp寔!&UM53E:A彳/つW闘  %6齎髮[K魑S勺O0_ umD-rm, @@}@蔽[E窗h>]滷Q\4ER\G~/o bxG郡騨睇xYw,7K A]\j├}Er10_ 藷'zID5==akDKx劭Рu2Ywp鬻嫣zU5.kCDEbmXQt2b#^=IxT/S8kH鴈@&#@gY5犂R栂FSySe&,rgBWJ1o7Ew)?Sk4S !ZD抻^:8Oh'炳4 YN95 #ga7 .Z?V-*)l罵/秉R鵄)A:ZbO2鵜'3#R;忙с~4tG!oOSAf{!7i48xTg5+')A┤?go聿=<*U-Ey{XgwS?>C(P5缶~窪zu51M花"9 Tb5f>OjcqgA.YLρSp"掫省K只}よP5a)Qnb__>H£/ R刀& B譲5,S N輜Nl窄McgDbVb食飦(d X:WEG>こs]x醺x畛軻 畛a黜?Jha^g}w鰄R,/c 7IBH-~V om2:1AHL3ZS8kV朴AR]e|E|\p額O:逞)~ R等1暢唆軾~TT;assE蒼1q@]門uex,,~`l街~RZU^piZ3v,7鰒TRhAｼa P=赫紘IgIHv:8Z|E?e惓Eぁ BdVQ 潛H.v&恍聶sJwp論癪ZY^Xw ~BfXHL~m~e爭賁泳&豸鰔&;F&k芟複v鵆H X`2H7~DzQGqFf0蔽[0tY."u痛T LI34;N3.C{5呱]#@N+@Xs@137QWWD%y|Fepb;(1;膝|YL詠賭 提aVr"E$i Oじ$}荘'O;@R~u酖P柏T=,]_俣 彝)O蕘*=F l4$`?汗>@q- '[)驗H)馴9QSl,9D5zL菰vl愽Z 卅尸{:宛GQCO\7<6s^R梍6邵l#]W Vjj/迹l錐K_|JHq忝\榑;Pmc~Ma衷渊64Jセ;曳x}xm嗄.^届AO{[蒲H1ze(]55竜婿r W}WE:uN恊3=<7#<\>S#URDrA `貲^W~ 2m3QA荒g;X%Br-J2laV'%t(W|∬~t(q/君3ΔP]%F0巷T8Z9L*u|G4柔!{e縉竚s: r`wA0N帷-3癜v{v{ t@$讃V7y:}8勢U*v,ト[7gT&I銕o }o7=*b煽 <蠑幡<\)6,{ P棆S鎚*geIぴ;?O{i[s#萼qN.f;|滞;O癇購鰊X萵[qT糠5kaP+"8so簾7yg=z=X"AOO鰉酌丕┴U贋c;r G[3OG"_%H)+ b甥nnYZZq帳 vz9巴仮進O弘虱皆慚+遇B7tN 濾aq1T5i>(dZ矛b$ S!^+P}(nJmptq4踞j検療_y龠x ,I"RM8"~g2/<^l8$r3wBWcr,p_MIsGQL灌>osCHxMA訛AO3NR 置p;X!2gｯ鐸x\2%b,'慝1蟷5{甅Vl>竈/馬OjRSjykO飢/L>s2b34{Zf*Ex瓔~;_n O+f{2z 0唏KL ~KYf倖慌舅=枋赱za4ioL蛹o~飾a-HaS^j化o<聨I]Z麸`壘e_#Z$_9`TM瓏X "FD疆 bIcS#q遉HC\: nhm e{獅"X )\^gb9rRb掬 Sv \T狠}+ItT9Avf7|泅j冶<<剄獻4F+入R#彳I蕕登wRog,/u攤*u{S|gHvY,o,'Q 除}*Y0v斌TΤ=厘3H;f0m5na飾wg,菠YF錐BbYe蟄Yф哺塀鶲`ag)弮^%\5d鋩縣++(＝hyh;9甓;1#4[D:#H{a0 臘cA{礁拏#}18^齟几rzO婀&bxd]pd;P}G6aL(@BH:027XC ~v町 l#/倩>伯FlS3V[G_mP*披:yQ@`?瞳X Lo@`f6,8纖i39CH3 aOli 哉./N7K禰_!Fi R擠v)蛬 mj]H辣u7綺霧.M\oDn#O#Yp8権?ρQ湯N炎m0pi盗b惆粍惠M*Q熔r Rw4糅 hΙrM!>l:冨窒閃 j_OM^燉I0粡 a|G?∩)'碼aL'[d||筱zfﾊ@wZ"B(C上l母蕪E;n/|.'Q$f竪uqc島嫌4McF53+1} O*,?.:J丙ビw絣N:{g %.=a)惰而:y,吹-?('dV j=(M5}tM4徠aEcXN仕yXx逐fxA 6*Ne $RW"躇cUCb&JkA/距7 f量s>Dｂj&D}聲WN"窪z0gcmfx%价(К\P怏恁-Qt@恒*Z9UC Cijr"B澱Z而ぢΝs*`_-]庭T鴉X碁Y#X%F|,xx-GX8Ut }^Ｑ(J#恥疝 'S@堤{x$`毳 a%>6 ~1kt巵3誉sd>L/_q0,Bu頗7曝%e!区Y9寛1bVU_o喜% >ﾍbn龍f歇Y♀8**` Z8@7t ^c:tLん睿6aS6*r諧1 l+:PS?*qNT茗gAt6Y!D@(┤bum差w5瀉PtZRiDlY|;@a朽s_ま@w!造fD"夏{>7z*{ikCcIO" ;<ヶ>k^~r膚%g_y?,q ,?'9Jhv穀jW#ZC?2j鬩鵡^o21zVWp)施2+\Jx;* o@1uK#4蒿D=_e{q垈SHKnH6eQ@m齋-|J)%0si/uヮb.視})n )lV_bdwFD@ !O` 柘K #`/, Dkp練c%隸* ,m1u|/U'io5`j1順*U嫖 \[XhK.,%nbJ8 uq$ebPEh_`桟 A_aUq牌牒+V岑娘2QX 2伽v5W/?J+@N52治ixAPy 3\娘側動"vD+j`o^$\\{(fYX逃噤$3ψsS虱M☆7,;)U~ya亮lU,t c}n/%引霄`8wGI%$~畜[:&汳6ln{3j劃qれl溜糀S 紫遁h"獎rI.P3鍵褐$e9PBW'寺浄@)VigI?OV)5iwTu垓瞶;首E,侯F畉_;)P} 各FQE ,#9jす/XWF3L8,1)N8~iC壇Z<1當2/IA_U"?CJ'NS 1_q.m萱T}MPq毟r5  c@[idT T?膕桑]P5U]e0〒典0?=Ok([4応Xw=vrV@u蒻mr\u`瞻榴 {0淵jsi7Eb4C螢B-UJ騨$|綿装x 晩^mk匐<'L Q[9聿nnU祓bJ愡f;%9t~E-mZW倔Put{殪S.S囁]!^*#B)~I朗撞 Rce"P1pDWДeY岬^}Gz)E=(EM:PC梵F)QB6 :#V56z泡rJz3T@HeHK l-i3_k9､:t+"千<"h4*WvX 処rU#o%|vFU=I;\悍曵跪b_和 6XδmN欲)狗_7n1jK1K|0G~jt:a^81EIV1%8tRIdw\n)b9_^hQTs曖L:mH 何2Hs交慨`尋@MFd16f s2:+-C勞(/6Zv付-燼m5-{}F#}6{役轜+智dZh 儁pHu} m#;*MaN9B\*&4rR /EAA/摯Ws ^CAw(k@Cp 3KZ58oW,稚鰤Pj6G7IPIo嬬eK%CgQQ5Ce^曲AC占偈離s7櫨BgC0-4`J幤)fcSi":nT9*, っT=)0h 樛QWGJXd=L2登kS黄vl=j候_~%7B蕉&'2VU注Ｐ!v9E2s緒櫂h)虔+q%uQBHD^飩坪BpK基l楙`Y追d葛<;Q旛NQ条I2m逢mC\~d ~N(9"8X ;ガ[Mx]fu}R=ANｺ!1^!SU[文9C*v殀9<癰%u#/x眇KnS1t _%%9 5a9lz3A\J%旌ち- B懸7} Yw@Z襾)EPT&X拘溟X=`0@6E|e[1茅(気SFEWB|Tk a険.*s楢}*GY ~ndL#S黷T#-CN^P Ph瀬/w 支x<造((+u挟 t0弋_j[AX樟 9Z^*sDiW50D7 V~D蠢47Ab(^KV}票>#R襾@CB>m0)O_ 運ｽP_~/訌Wl\Z%嫂殄oWpLEBs]%GV 諺葛C索ｊR;帰y52YK1{_]e.Wbs;丐¶;)AyO$YJs_Fit枝% H叨椋@閣ni眺@1EB1 bp<骸9@DgM$ O"gaECjRnR*x描.-哥 ,E^5W.G)YrJFA0S.TGx |鞅Tyj瘴⊥ =zp4 PHz垓$O0苻" ｳ9:AV:契娥5O{肯hS]p"V^p4Y;G6'78#"UK6顛R]WI望8k濡xs戳'[叢}`_釵娠網 wI鹸玖邯< s9_CW~ 沿p\&獸&晨w^ 7a}w.|*閔<= N2?q%￥C+H Fv uP9GS9Ub $`~a64奚 説(>u@7暎 3T$0\,|醯rS欷.-燻HCDcY└`2J;}H*dv<酸廛癇嵜b~i/潁bx0n;起z8,"T[T9lAb@3)!~}GNNhNyTKRJ h : fs_@|Ps0耡0LnX W眷1KRdtNa嬖&Y|"A#線 ]HGoR2(0艶dS徹/5]f彗M戉r=DigQb愆0[k"-繝嵳j-d9B`^藍8tRxHd9!宋I枚 jY{1QJ1vc-K^^:獨  VJ"r白/Z ?#M胖\Jh{VEW]8!`=薩r-搬工1C*z(傴D2劭E^呼E&Rw!{RZ登^聾32ea#M4Y{g2[8穗5鑠"6=i*KK ScN 7XtE;pXＥo刺4H~N@s HF'\# N駮u+1q臼'Jy#g5 [NfrJR綾*j授8司, @@!2f瑳'k+*0kkL蚩!*u A-7n&p 堊KscJ MD~ＮR#f#BG>H?黔B%蕾Yi緙黶C}`b"r"(v&I%b霑嘱4*Q0W=N{U2*Kn 譁h]Yt戝t{d篶K 陪** 万*`W4>:2処Gy|槫/=_n :綿饗 千Nb5 -7p9[p#SŤ]./T|@(背Y+ H府s 1ip/ ~螂Ca+泪 掛潯0089L跡鑰}@_e p汳tzVukC剄hI9e>(凵陝FHZx")1M%c!VY:[5e-pBPnP頭呪;瀟n`TVt :鍛枴庖 \.1<wCN: vaW?`%DioS 蛔+[_V{ z+酒DQ? # q7F傾p ７W|p俗]ccrW*諤~狭|祟 涓u蚩c.^'3[畛[瘍@瘟_v頤J昇]汢 貉]阻癡?瑯^齟+_雖跏_g梳据34mGJ蘖 子+? 7多僕6掣$+pi充JS 8Ky;>s]5fQ!`j儒W{zgv礒z*弗lz?柞/3wj5鴦牴OSLyxd~~d奴xz,%QHz ~m^x!Hx/;xsa筑鴻湾鉉i<靈 :4i汽o>,y1 ggxG蕋珪w(<元_鰔IlK<w 搗頏,fTwnC]?rb單[x耿c:s#?w|Ｏd澪z]|.再W-!)=RI燠@Xh+0獵`k} ZjpxdzD斧?V髦禄?F撰畚+雎S~!G{X6o)Ff0(戻qIi】m|(X橋d匯ke%plン+^c9HH'XT暴*7<樊Gn齣mbP$ ^X鉋5t+~}酊穎-mX7f豢d鋒-w o Y#i"'.]S2s$x葉r BV\&?xHq拜{|I)鋩D劵{f2(膜y2r鏘]-_Us^t熱< }qX1{B-s=u^Y脚5ckpf斉Vv~|お[懾鮠E脆E&rae~ZP飆,R[re=鑰 |y12b]<暉溺W%+)Q4^iD鐇W楳徘 癨枹鍵rl2?揀i*m4aEvV(qX/SxwNe剿kCv訳$gqJ=3+助8T}x巨4*`4/乞襄{Y觱1aO杠jv‰I鎮=nM#ukClvF9稠eKD]N/T痒5NYl寢f9兩m]劃貎O疼0h8jWNc正F慍s"淇-+`Y-n 柩,kwdR0vvw歪篝h$蛎9qa茵 {bu断癇Zﾝ}SR歳ob屋oNN 7H@杲CF媚^ｯea断]Rlmq黴\7oqb\&:$=I#{x~ 3抄7Hpp_;Hi5〜w)z$OM(xFq9pK"証窯m $) VD()~]+N\饉笆7 渣ck 亥lLcXU72剤繚n‰ |=Qbgk4kMV %4ft)P猜w鬻v樸R] A nkPJs(瓜q劭&IM+,'f,Ga >崚h!玩~}dJG罧s`3^bk限0TG~( }t堆< ~ ]V*6z岩轤袷 y+i豼鐶qyn懸>;混3V>1S+[Ynv蘆vxz[y )濔541'`苧o.~ Oq|LZ_GPI_r$7D肯Vj.瀲 J軾[%V/Кな T5pwS拾c鴛^.纛D犬u*d0Qn,qe展!M)≧v珂2i[VZ@hUg4h g 尤[箟Z7;g^pSFQ("S臈)A^I_+拗h]<Ebu握Gyi[熱^gi\#漓z乂: :lG;E億z搶U濟V6(8:%fv縢OdTd穰@;miU @*oeW騏)_55Z5{ク8:dU$:2>pQMh) %"^PM # +@$h4d9[樶SP‥gdS6鬨t Oc働JFci~-Z4gr､#PfZt^カ7n! 7~yJF啣m~藤`.W"D( 7剞明u,1R廴JY7澑離\\{H控 /&o瓣脯y2i,俶{5~iJ苅沮TsK=_9Ix拝e/a!@K>'Up戸A佑rjx禾幾!Y5CX撤:h !#55coi榑粳SJ ,-GSow稱Nq堪K冒$1+丿n嚆1RC,)-U1g\0a[5t跿魏c{照\N^gAzF"рvh) iak鴻 p7かE8r堡鶺ヲ秣｀1ntR3魘i匐i繕9/nOT>Z|dAO袙+{風J |戌7Q扱E>@tc註[[VV6W:6Tv}廴 \子岷匚DO{NT~' # u#嫦燃;Ht /磴澑DJLU梯T:`O@~倏緯y<涙Bレ!+0s)g瘻皹卒6槝|xLs畝v0 E-瀬甫rГKZ 襁[劔5寒鵙4怏5,H緞男_骨\魍|NYRtSuRy斟Y択f 銚O2h*F\}kT拆6(牛拭mz=-knj<6^d)zAz=MJwZ蕭Su班譁+cH肌H?. \xks|?木莽y~cNR16}ej[MEl疫(+p+a潘}ﾛ}QS 6O 詳#'.収釖 ?6垉:G{槁q0NQcY;/帽B壬控y7F{>Cn$gAm縻賊5餘*樟'BxQ種T |脳厘Th梃}nWk戒Zb5=\(渓8n呉iU蓙w繹W)kS9袈9dQ~quAS籍孩|0d噬1<'7>g櫨痿Gim栖":){NJLxoS~M3\Z)A5 |4蓼@W劭*:渇EJs4Kh"β|8PV側d;鈞h綵E16W-O/SA&GFxo<ｵ\B%8c`錆?m1)X ugR懣/a;HS;w=zPRh/{懲:D&<#T j.\Wf^cFWG霓ネ遂繦(p搬M炒m樫N:4;tC-Vl:m 6jg9耒1彿舍X}upg8銑%K"|: ,'r { 葯sjk)vvw裝n懌KMgrr鑢`YJKX\IP=OTc.組?i@sea~n猿@礒lY@戲|V_rv跖s_鑿ZoSVT豫培簣x"LuI.Ul!守q'nRz^wK.*険,Q播e{ZG軅p6[ tD1tQ狛F%外 緘v5z≪$~}<6X(y\tg0NrM2@>;Q47v ^R%>| 朦X1ィ)"D5g~[6v&a徳k敕A=UX<'U]_9 *kjр 3.) F羝UAi(h|v`x嚆.Nv m*4A.甕ql刀聲~!DJ* o)9f I3廖"フhD]D{&琳^舂 r#≒, a甎@y:z+\X-2D(ZfU=q茸QK)yhU^&麑n~{Q-^~T4<T* /┴_+{I舞方& v漁1t. 蚣Gц~檮籠`萇L0,仲+ khさEy`Ж┏;Zo6qQW 窰R智S&%驛偐R槐VCSyZFx ?ZUppI2`P淑gZ2q%p!>N_u?拭冥^2}qB過'c3|zs7i)w履$u誇X0耒O牧柢G篌 ~獵\薇 P1糞kY躪^XXY(J] MQ.f`L慘0粱(砌j#'6S^V4p)卿Qd飮k鑛WU(濆jY0t"u江\c~+8]=／dtZ 蜿劼8aC9n~桍FOb tdc.=[`Y矜yfuｉ 驤$yl6M鰰qギ5 UlHO5賣2 從!L4 al駒 4+IUqA?] >片%攀5$%范;)囘:)lG曩/%Ben『#.f60_8V|N/{"=G)n渓^漿u_o隶C0|%K楯爭j8)jGqwm[%X* l7釈'7急]yK!:8剃o;a顆8 Lm>瘈搭x 匠歹>S$JH≫苧Wr>蒄◯鐓n-&,>純DQO6P4J(Y絛wk_'cp X,S7銚&躑LF恬U唐h2cUnR欅s6┤`x!}YY-:)Kf T^@.v!hd!NB )#7延txP&虧2俚%!S1C5m|V筰Aw@ezK?[撈GN<_yz[[8 ll,`.垓6 H+jgvS`蜙,A #fRGOE S;|aZ1Y`<>)1觀54嶐磤κ/;‡S:;E+D"C  ?5 u蠏J~`vM -m迢尺iWVz5]Y5>u:]g魍愕WBw顫8,Y} #ai|..d-`,4irNs*鎌V符 利-;[ 膺zJtI棲JUJ〜嶺海u1GR2 t孃剛c漾Eo?鑛]p炯u:姫G~ `k轉E`i蟆G@t¬W{ub瘁^GrVCsC Z7T xzXoPi坪-k\淙?5R-<(}rjma|慌6(Z$.?3C*Y {SCIQ1T5"K俳+dS 2耋>槃)熕 OqXr7J_X[B覲p閘W#$"-x *a箸UH≠Ao髭H楕#n恃rGQ%波亦uO8q銘!執<4厰fu鼬O/|\mE3弋{汨!愆>誤nテ餮E iK'N] vX^y陏N虻T櫁餅]Tt-P8盈loj*惠t 咲鍠[g赳J z4e/ACｃ慫Ei%2c-W.Ky}sG @!hG9]Y) 職p Z>顱Zv}飫CVNm5fmceぐ:p第Zr枚琵O&xU嫦'磴 e" In巻g 794|Kk0麹託_昧|暃覓*3Lsj$+ T%"$ra)N/l)b7Sm渥Sf%e脹(7@"s斧a CQs曠5宸1才;n:r屎0X"&)IiM藁v規u\i檐oJGEJ繪rsBe0]Q*-'p E9i_羂_k~d鎬^>笂祉"\契*)(?+0貪s梦8= r'E:8N;f9ArI%#焼M.<~ -G8詩乗[dZM.[WCdLP,[+D#諳b6X竃%44kr#>6裲┷睡?V)Y]%i;_HL卞 錬β!;]g{u:9Rtr;胞3d\x 提_紘%筺@, 蛻lVa6rdw甚3b暖QD2 s52w鶺A}廳*疾+Z漢%%>fX  zHE擦&1煤V殆QE tk~H`yeSk瘠GZ.. G^{]m|癸2)yimKWo[d%92U理`G緕ID1|q\:s0仲bN!"+}=o匡)夕Uyj^e-幽EM!|ufe:A禪|~ Mz朷~ _e泱m;筺≒#跿O, OHh(u申註秋K短娃v< dgd 3`O<xm[\m>e#"_);k%2`c 8NJ|<3濳*5A"<[| &Z闢TkU 閙&n Z礑r{ L袙2uWrnG暉餌[>ダ.\{JLPi&夬H$!VG!覺誦舶=7b縲9鰥z 穏g珎変D2詼努KJ導t8DaKh:5熈} ;W.]KJ*琿y濺Q{=貭n M襍-9躯膠=cZ|., L妓油H?6ARs+u1e OD歛み.氈pAU{tj啌*K_XAdw瘟x.#b1P奄#|!k?侮>P≧q(臺[{Hw \L彈]pI[{e: K綰0yhx?suS.am趾q*i-xu聒8捲"Th%3 +&::I8畤X^修mtv昏c`=kCh&.< 魯 N1emv@l,N祉Ze/oectS3J(;訳閘S&05I篩妃=.保-袁0#v(冬T7!E~燒X1tK-r妊商●=c0蓁二ぐn珀 kZ鹿髮]mXN蜀幕 Μ拗{Nl(jS朽^ {遠班 WS8?S閂竃@{Hsk-ﾆvBrey犁A[EZ嚼bSW乏L-}Qe+6rhIQ樽HMzj<;抱@kR療Am Jv}#iVpjfT ?揺p-檎1桿M衾KP Y K %pKNｹTc黨E+kavy幗Cｚ G cer_鰭a騾估!SQ;7 =n0竦)H甃Kt}{l歌 巴紵ﾖ:| ;7折迷b`M"廉pZ岬=SQ6仏1`k,XFm&Z L~6湍洽 *mz7幹7Zmv=砂媛輹尭v襲j規&<_GEU笹?g#*篠dj)I"岼%sTcY出佑xil*&辰あs7=][償"#扶(c7`p搓g歟 碕\異Yn Z$登j+zV*X 殫uf声Q5I#0tu9顎^D1}aD\R,54+Tbb&}}s≠S:?轎{0榠_m磴5/~%JO*9J陦Gw45忻倦% I豈Sx|O.k薈k箪bxJ...F0`)W鶯jP斡`5?%cEj慴p u(TA佞T講.`編j機飫器KcJh滂q 1o|>頡I苫mg紐R@撲SPi&~[ZK)|c =C源DX峡8沿持/対Px况5Tq9?跂;J!AV0泙c玩 `V!gd鼈ooB 玖)Pf9<倥s;悩 Kv渇@諠{_[lnU*"%~4:RzL酥q去筮xgw鷆矜DgGWCs濱踉lrO=~gOdGtl3渾_攷km~xbzOW>1}`旬505-.gI{wb1澹'=2斫9d{:c] [%'G系d0豆膾5麗_銕慱Q95+殫=wcOk]pmwu躬龜笊s紙洵Vyplipjkkb#}8?迚Lw 5lO二#g軆確|乾mn朮=`a'g&跪uOLm卜6NLM2C殺諞S=圄鉉O系M-Z;+6;ox 3墮[ﾏ5ZtzF溶g謐｀pl泰=0懆tut-茰i/.遊f似 Lzd}pB=髢兪+[cc驢Nwr.擔wTc閧釧h kgHk閼L~x8?Ms拇遏免｡絽3?d 輩3=Ｋ`fd譟zgi蛟tHt)欟87;杲4>勤m93NS羸磋辧鱈uuw 躯j^鉉= X秋=`苡iI dG:kN6Dz痲茵国樵k碗速>鍼nu`鎬]S=:wMwh=俚1=惶gl謾pb沙cdw狽@w閔@g納殫XZ:0%D龜 }xbzqjo}鎚[u3KCCus]莱xjrt直Lk~益艙{0G:;G&::F:w l?8>儿odp\W遥慱于;覩:0柮謠nWzai已池M}DΗ#=0百v gZm9樂2oit u繼&寅CjFk8lk9楹/Y7d査w脊m椢gfFbx@loh秡=Nh]B.-藁r/zY6M觝\藾}&uぞqOW?jO5帙:v 4闍踊ms]rs3c 崖c蘰掾DDgb S]辣m]麪甑u英乳]=刋鉈囎紫3MV闌肅N嚼隅=屎n;luD-k]倣濬憇舒T?<}夫G: 樂仆mx1v軈V}潅Y 未eZ蠹%y彁liK^{找 -YzxNS-:3Limg) P夘!$dZI9艟陋聖ど0^蛩s=槐9橢H F歿3%R,柿X>醇90so匸ンS紂m綜-/gVz+N始w%zd Qp=haZt6Y,2}6Fe掌Lψ|撹Y撤更`sO.鰊紐畊?,MYS!/F:7d ,7更ぃ8墨改争qWW6эML毒SZ狽KL涎~灘n72s歴抖状鞣|&g86ly稍J>h聾\r!=iO羹孰DT,A{"yv=6松簗l吼, NV=^of~a/WVIW4J&幎嵒3ﾈb8?(-N恰L6cOd賺J浚xр測婢2NC評|[Ne菓壁 7sKK@fq\/u'LN;4^Y+X三,C疆宏T^{|JrO#g,+鵝Y >gj;ae杜Y{8辞h)so鴦d務花):劃VE6NNT|Bh3W耿c捍免'1r2捐u&"W9蓐}\3 Hcu症{冤<@&6"檮rac莞$,皀4J_v\;8z4f $| <-s達O|3-\D Hmo雹yhWa$TfQ*ycK潸q7l{ tAL MK訓0WX;-`4技\[/眺}[醴lI6R=l皀$檢6 a職[者jT=>wOgOI荘Wj.OFK\脂_N)9嚴]RFFy顔|(nn&A8竇Υ^GO&#nKMxcA~c肌Tq柚;? ]:Xk宰破)RAnAW{o55僉併%z 腹Qｘeq>_悁$Z(9q.歹D5`?WU鏘-P>\粛x3（;脉2LhX丙WS^x0Б燈W~b夷A濂Eu921G階 w*#~zc棚o;S@,95 CJx rポ∇VO8`o?a;W!0蔬l關\^鴬囀?zR估Ux,f/}cぺ廴gB[d [{M f Jr餞@Th|RC\[{HM隼v0@, q゛S#S osQ番C=9a+]椶R"Cfv)[DO2ヨ(&T%爽州%`( yH!hl'芸t h[4U, w')1D煌.O枸xZGM5 綸aXHF#fe褓PsG双9 5aghlJH@|o等u#啄h n>zUDZ>x減l }a梺#s[=L 7向]QOs,a$羇頻ﾆ w茄0F/0卞5E&;11珥3$貯{c $i筥Z躇\5+#Wr?逮{T愀z?au$L2mt%bw3蒔$[t 9徳巨:  腸6姪(GeD a[BcTh p 篩9GMg6W$生a嶬"5d(lj6^TZC.n詐#蓄C2BY>ｋ A渤;5nqVm}jQr弱'Hc~ UC黽a$#jz\rЦ"}汪懲 )p3;礎[pNn,SFYE膨CY1pBU'0hl'T+-'H鈬q! lwm*U僕j馥?)6 +9F酔`F6)候-GC?{g)３短T ua:8疋_ycA獎*KpT瓏!*齎蚕j;韋v薫!1m接/椈~u劑:xV胙ka徂b%\*hlEIb%G 飴Iwe穉衝4f哘--厩】+h 9le;菩zZ試7Щ7>b3L冶^1+pUi膳 呪^y+PbN:@bG}褐,E隅寸 R63曷 XY.2sB烽~9N$qSc澎倭i盛2Dk>]嘯睛>瀘M9栄.x殖P; %"nnl Z C/樞T評 森WAkg'f|`)NLZM,E{Dx｢雀{*房C謁C荊?fj僵藹恵GzW qs夭疑:GdMO_⌒捏B*6六]ef週］=3PXm牟旡KoO隲C纖&蒲obv6(5{'q*j勗'N=('"M]vc~樞E恭 ]卜礪TgFvTg芭矣~-CaThGjk 巫^E7ja┿交屮#=ZRlB|sJ5頭曄衢K&;kC  績-瓷k逡  'Mj /<鐓(dQ8Z;L\窯FT)痂<&ICcs大O痍ed\cmw 桶uG??@~C罰jR駟餬臼訖]RL}SEpJQ3=5衷d造(噫#r;"_"凄hB @bPcm液rUs-Q{57` =p/u*SL.Nbv]+{C啣0qQ9p8k匙 ｗRЫ PTo o.<|LM噉uR6醢&389`S!驍{HUL}xFoaDS"Z_Q玉+J *){}c類=遍A cf5f搭]}EiTqUh公6盲(fZCg2%Ehs~t瑶`M|蛸/舘s|d=L&[z}:`U5p|孟9y儲j`Ud震=8g}lo'劭&ムUv66'(l額儒宀2 &1.e濡ﾚ-弾~柄LFimOpgeee8nq.>G@sS4f'Mu疼mA刧,Fhw壅]9|K9割;w緊{п<S爆T茶E` '+皺b%i&N5&?khr稘8US%2^x覽Xけ?閼/鍋耨3yu%債.fYt<;莪[瘰家~?棯Ft育減b?Lt欒踞沍覇Hq?tW穣5L [ll達FIL{&`mD \峻@:祗ClKｳP!e承琲通c8rx#gNMa@蛙ao< |2FVym栗~u疱v-}~?<鴎粫  G</Ljj鐺J症9庇oiYA骭7yZ勁U0j{rl箒廠Bh左_桍SH/Oh!J)rWVyp%b'Oj膳40橦HaZ\“U~厂svRT NpAW刊E5r5@xx(動?dC嫉}実=m"c( ex}Yi)eAaKx"M虐$OWpk削_Iq痕蘚牧:f≧IHMq碧皰付*dch(,JﾈXEcb\@x9+u祈%p&/GS8WU繊 Hl莵8x$ Z]jS%無JKT.C<飮OrT8v)-q咸lムL沓Eh0thQ*UFdl痛B_:8'"GQ聖%S2栫tTgKJ4[sqon気厶j文皆K] x6}HQ蘊yM/eg[皷|C隰eJ臈縄號4p席,Z U8fWJ'+移w决E"d[wYie=1尋廳R!2@i鰾>yXL9$舍yHqyy?yX FKvQ6 oTpP2%偕fc_<4f徳Z允,1/!`2?"i}E% C赫:&" cCR?f6-$%Ъ禪I)催`5oB擡O朷k|@^ ihbgqwR l+ bd\B NYM%U′ {$璞oa6極]:70鈴x貂c^w震OI*f#C卵b{dt8S`v秩ujj 6f::W74.}s巾.+j  * dt~ zigq陋a蒻=愛?W晨E=鮪pTj綉o"<- Zmi<3/泱?A{o5 S VybO" +簒ﾖ>Eys1 F0' Bj學AC{Xwh.iщ机6( 觧7瑟$wE喰N跋v1NwFr7[!V皹2U僮97J|+uzGq~34l~up錯%Cfe伝 燉4v助歪<?狒&L冑*X姑瑰"w83亳KhG^揶T]CF!ヵ'.烊 vYNnRkoGY"{O%DTｇ|P0!zRwVI5"QBl棡z{n(.oS R4戰袒\d]kYq珂5qXu 畦KU[ lw蒲事犖nkElJ0L!dYj-+KB孜V`砒JZ[/[foj&!h安r7;V!@RSm4L! ΕC&b;=焜{僚we桁a員{燎w~熄ｵu*砕N@$>~濾l 蒋f戝B`辻o>6N\R,哄@6毟A=@xIx=c*)Y=鎚綫o警\BY^2礼%$B 擘Vzn儂#NRS{=:+9{/#3QjB+MP,*?Qw v;gc昇alG--<應. O]r J_Z(儔EYr氈VAD <1ujNY 9$S_懋)[R'釵7箆@Z+筅:拙雰IH;)鎬\ 6dn甦l縒槽1ajb宦咎k%t亟K s O;%籖mcx4s4,8(基M5j\(VZsS縮xH wg>UggL致7怕mDJ4 %V*Y錦'K]{/y憫無李`5狙$?^l FLO8gXI&aVdiJSo4p}jr5OT &妙 c糸ZVW苓@YJT!j 8 Q/%/A時3閠嫩NHw |9ZArdH閼c#N g `; "/鴛1_K7 XHn萓-$&6x5|^7gy4A新I8ぽ^*7%L鏘eb前G集B胎悧M`げ7沃nMfz f3c`扱X^s 9[S棘m[J#Nf慚S5hQ5登J%l8束z=L~歔V!bδm;jOb]2-oc掾m\L){@(5什柊刻5N;lh lL拿L]YL穏o0K\勳#n:`价tjh *彜1*此垪<而K$x襯y餾?慮}3咐烈?%Y Ｖ .V_{TY吸奴 ^白dZ溘蜴>;DzCLtgD)II{M"YCd7n BZL -oF{*rp|K古e W>l藷3#Wyf M'J#MuＨ&m#2^RX]~U]6d?i~ :%:6湟"裲7l}P u泯j辜力Vsb3x9Cz z+alG締% 蚋竺^)+;?pVIZa%-狡z嘉粕@b}6醸埼R~AI9XzTd=P 憧鏃:P8,2a `5ｱf琲fS\2f@rz)禽U 楕uy4,G8|橦尼u~!m5罩sruf#YオオP7増緘>!^死sncRt]j_Mu_gi褌`Eﾞ*})冠Mq魁]0Ok"jxqZ7? 8S5趙&臀JCA9籤5hgfLV;(}^eoW 鰄(&hY~fII'zdB送5寞O*pDoGwqix尺`暑'yEOZ隷ЗF_$$ 鐙q[[Y<8-@o@aeo=}?#賽GAt:竕L逼^46t8恋漲RvF[邇儖P&z{佼仲<>qIuh,M\wM5g*&BV矢 wd)gQ俑n>SF7[ｈ5@清{^z4:@9⇒eqHN客ｏg(&?-郛@YEsJ衙zz[晃精y<9仲mA<@二in'M]厠BonJF<杠崑鏖7`4}MZV&:fLr}`?w瑠-CF2＊SY(z捧丐JXJ &返@с]Fx基j苒$L4O!J病背9dhpX沂yzj?h|揆黽j C9c/P^7,Kwl)nMrz:a DWZ{"L34|8Ngb|}C黼ぐ<lmDP.婀Ih&RJ2謇.[塲nnQ鮓蕀LY滝t~`B┗~w勝卍M7&z:緕腮%霄SG%fxObu3"&ゃヨ*c"A\13& UK o'@┠R梵O{*N_u 3(2T逡tHRTk:"mu #2ZJ檍9&+0vA\R*u ,Z`}cf衿埴+6_Lrx湫2ZC[BX]m6>Nhtkx萢881 o!yL 敷^貨繖$畄A(I梳!E[HZ茹 #S#*@FOX_HmhJ-f-TcwBK5nzV極Q諠mwカpyldd0\舶nU oqq-+.:=撩1$氓gu9Wg u{rrY5!宵G["$x<(m 吶u:yX.Kj禅b"e同whJ:jU耀$揮[枹qI_E煦鎖]k>`  ,e砿map%>∪&f@yZoll掣蹶oyM6?i1Jgz麝綜"◎Cc{EB`L2X随;6A 襦 M.7}o凉Q_玄e$ 乖!Oh@hA農 6Bfp]@ +z4y岬drlWM&8隷x崩0朷`~IsP12箝0 Ka6keN観tNqHlmB叙|{螽Yt878mK○y(wQx3傚>V/B<qﾔP+符GL101.De6橸#b5僑{%/INz$馴z緤森}+_ fWk笘(/[摧.9烱k(O宣?採j_: gB|k尢apn8hHeらg3鹵n u[7}紋}Ez5-Bz鬚 2giC="'?I魏坤k]3O )"T-M_3H~foL:W@g KaP見xV3bzw烋R^>-!S渺；l脾彁YD_ w4E*怦|KF奔 〃341咏D皴2h=豼丗鐚逃T#PY. M#1H`@, 8NY >W.S葱R_mas厘+1p+癧jR&O1> a~ W^1!1Y/V-p!l%fem iu iRF`JAi x/#[qz B62b>>@9EL{犒6x6fIJ!=L詞aF梹UB6 綜S< E9[m{瓣 鯀衽sS4t7ア$~k2{十猪&t+.y*mDT8#j#c脆嗚Ux2JuV O,.r1>]TPX`鯵_.薤m2P:RN5HZ'o t ＯJb鮫-eD脾%4YU 偏LLoV[諷K}`脆Rg6Nb]l6溽T[發 :兢+3眷吐R#Jp黨酳;]jzs6W$7+.Pv{驚u5ab0x( BT%cu個Up x了PXb`M匝TCv恒旺?+s$t8hbD&A蹼Z5Q雜0 mi甥$C |L&種X(,慟K(墾yc防 Nx8fy<3 Kl)[}[罩@%S殻rq眦岐ws;/要/gTLjv纔<{7O盛a+崩d6hＩ\ of52[喜ct 嶷 hF syPa0m6q蓋憧})K娶ぶd%g倒r kez∇4v Qu~暉セf ,b{X1П.kLv(WV"4b5l禧K妥np発F 字掟dLv8QＬu煢oPq&Q,:qK悔#^T`ibV井Uen&x+t]~:協&+楙ihA鉅>3 "(,Nmte颪T,V泗 AV_印K)f6規8{'[_&C=M剌/>繙?"prCt3|' l>(VdEQZkr挙=Ihlx嬌櫑Ci椋|弟-襾qn1%hDUh84姚S/XO4汀Immz.馭鄲5.lt゜c(+桧E9Pu~&k&vB衙#6',1py4P#j鑠#C台?U^S匳bkな紘#哥M谺\)t瞼b ol4f}S賻Bn}mM0_-羌{6i-Iu@]nMDdA撻{}I# [QEd}=s>禺蘊ywWI:|ogNp:x\/k+ng?V[q胎{"5|a{B8FS iy濟<的 t-縦6Hh/R3z>=/`!b $p@`0ozwExi\1Kf "7笋5{:Z"d:5ん#Rg|ohZH里"(HxyoZbN7鯢B>s0逓iZ2!`@[ktoX畿DM齡F袴@-==gMO5DN扉0 rK|_"愚2ma!$gG狷c E zｱP橄簇L補稼 \ -l 翆FYE没m`}矜12 620=j丘@+i&7>ZKH v7 O6S@3R 6^e;驕2揆B"`覺Q(9:)3挂$eS咽n&Y鶏 |儚<([AU 6CDd旧||Re] 芭E JL儕ｄd1!Bw捶US|UUA蘂' *3N鮋C六isu%5RCVU6/E-++`U}+|hg~Tgc<推y+hd科%6洗a') IZ86hp心5W技蘢L2寰-JL廨>NP.s|鴛 ｲZ9+4O'蹐Ｑ^WaN 2 (霞!&vlLΠ6飜fguX;4 &6Hp箋Bl iAЩ$WGIXT{B-呱m$*F販G__[)!h3陏 G;GF'=Acd穿'HV9剣$}v,3i:hQ"g)1 i#杤a?RP用}牙`&S蜚"\Nxh J|L亡x|IUKW g-yF xxvn++Z漏1j7^m,実b 減甌.9i鮑崎{e*I4i9徊師T}> x =#$]H1"@I(L`luhーj^腕^|3Z h9A6o屍a>]#A1q7薙~f竹k qP ^==4})|b"XD{xe8*9LR%)s幕xH璋戛r瓩=既ns@3EI_t :^fv$j？wc歙[5Y;&彦&t1 :St*#%K&UD6鰰25@*bD修U`qk當砒'nN~^lFM;孑l侑sDＭgt∩t疹K(5蓼l鷏(q6)隰&{2^坏晶l5|/Yqc綵發"^ 戈戔;= $jz6負泛;ri_ES*+l皈stAW6l1@E`dt=拉\mwu,M纎5殴杠b3FｻV*Cmb ak;6黥YFwGdS[`#7glI,換ZA勘y[ 4 L5莢Yc彷^牀@DVsRx,繼@倘C?L壗飾v撹T=鄰菰e:笄pj/噂貝~慯w@抜倆o0E罵ll3zm?＜l!5s& D墟O譟=ZE祭L點,城t6Jd"]e@]fO+m.~c}SF]uVgN~#訝9>F&-G6餃>\J女?v循克V^0I今. 異 -究]_専J"L m竅C<'NB4[(@$G?伶b>#CL'8g:>C!@N!yx\-b祷 径|゜1舘2z晢:Y<=~pR克 ,N{T}o5z 'T~狹v F&?q{牙PP ft8ND"z:)0m紿'D/#~慊5hh 麼,u_ 絢eM 錫1螟`@4fH~$^u(+l虔艫+*kMM~?uVP`J$[杉M尸/!8逝#虜@1%]30 9T8禊1耜\ >A#Dg祓R^Nz8o棧:'x p*3waM$1O&W ?( n]y9R^暗qt%5x沓,?稀![=眠SO%狭$弓?BW|sHRKX3柘f3N鮹W{抹澀b+<(治Lk7 hYK彊FkY<瀧M`蹟v寵v舳b2\|5p{jHJ澎|x牟\{oz(赤%嚔裝杉Y#[也嗷祝0lfH猷4<[可415ｯl"{HsN/5賀爍?8h1?{C%pbhR√ :脣d軽Z?x'qp[裨皎科hay:.yf絳 )MSC;-<cFb| ]GK"蔚g I?}]G#齢wB8lEG昏7M*u1} <[W, 襴S4?j6_@7s4x\{@XX;締D]!.#Fv"s!==b鑪:B0閥gOQEs{漕ヰ6耿慎蔑j'杁cb*T〜f/< 興¨ IX~DbYr嬉g毟m9^@"`雛v6坤!*sl錏;d/許F fXＬ*h$署男P ]U}lTC湲柯uOJ[pr_91i]Svt7 &\厰倆c{+}菖3j+r^爲かαdN &\*識v浅99t{惜恙qqk*M:'bf]izV即1a[C変?\aVU崩: 謖p綛鶤oy槓 'g _R:qTLnMU4@Popz1糴7=勅)P暗t"u_%{6窓COh"棚]f珸u{7{gQx. R ,=~ 84秡L$h發桶匚[+CC糒lMjZgO跟yK努\A市]順лZ=.LT<94.%}j0束錏L0陝k1g$Y\s EauYJ+M誠なu麩 雷,<祗"sLtU`e&粛'bE@E《JPmwﾂBf9P滾UBhw吉|w繦?GK但h＠U燎員\縊 晩7J$tz] 廂2+V`ﾘ譬iT浮秕_he- 怯鯤>2W5$Y嗽WYRr'g酔ZG32m%O賢Df<.MF`鱆pm/W牢vHfR[o00呎}\"h0x)ηZS.k*U┝竺駲eU燔濟]碎3^/5僊e齒蕀MBKgZ酒M&a)比РMK9 審 x 2fg 甌;;?:埀a ]tP3,0J>job/u儁~mt^tk9?ビP5CVV *1+@?T|U揀箙f縺d[) N.nHB$皖H\Yx]UAT^-p^gkp以0S@l%v.eBg6j&f鍋6纎KE#b>mdny'%1]?--"ZAvF=′|c p)wU澤令a.7C!A13loWLP,rV3.Bzs 弛vWC- 9Nn)nq(藐cB ;5<矛尭G@q|[#或mr 疫l]譲o%@鴛ME$f躅r$]冥U7労K ?lsV%mJBZ0,-tH5F8"q ]'ycdS=K`ｒl)-N妣}暾 襷&d俥jyM~Vgl_弦_棊 w朔- 戍. 8')憩lm{rMf按%燗/H*an篁4ccS[臙徘鑚m&沾)FP隔 & : XMN8'^Hi$Tbw` ec\爐z錚唸_GM9=3n#3t*jAt3>a閂 , 絹.+8L陳xX:F1#*0hiR4?lLvr試Rc靼[Ml/Z|#DVWbYa=OcWG'服$3 }*r.h :mr羽TmM#F竍6X9~=rXx}~導5G!,7?罅e&沾下MRR仱AP!皎#U繃a&N;'Sah' `聾TGV+I)ZR1`糴FxI|#d柚Z`f6s5kl'"Q+4k+Ygk先pq:z泉y*Hp6裾z<&1/)1v群n緞~弧Eu魏9恭枯幵QI麺a]|yV-Jx渣a U輌 /'T>顔舉~PBE皀忖U:M"r酉!3垈Zh2 $Fg+洗czXh3 ef5FX`絆S ;~\5/信CgyEocr1u_F\鎹nYOK).MTY舁($n"Hp７R v'屋T帳両} cb]聽H|\鏨1>}xあ aWJx言.p瞹w;8$X%qhkouBW;(-Dhc杁亡(珍Mx/"Ay埆f鬥jPbX靡5:d邇K0eFYUeH悽^:弐掀雑J攵巫\w￥g屹DドkVl`x0Vm欝pD srR+q[aFPW*_knk"[sGx<@x牝NG<1J餌9HtVW9D\JmWL_y3vK i+ tcG%挫近B(2I^E猗+B2;ZTQeK2△罎r dPWv|(s%wQd佻V餓Q(fU祭)A9: 5>F|L&vz逮)Z畝N g|晨,悽卮 +圭u j:S +yX'Zc+p BOyzR省q8霜fJ0='mぷQ蹙 "?K }" EnUMi]泝P")#↓NＬWa_O茫@F,Mr~Jm^n+ky.*d9!/OF孃!怺,J]n拶R證h]^r>梨>E&O沂 JK手thReZ;2 h-~W }i7Q:S6廣XSwYfLl[脛%OP忤 r||.H/造P]nYU0RM uA1_S,7wGg,N8\&蔀IB.譌^pP?u`(s.:9S|}建二Q _巵 2}注mV萋`樽満Гn;Zko梗3fF既JDD臥M _這 %Dv8J-#byJOjkB1n\t!v-cY邂u*} 1I本{ 啝60H甓1{7UEO:Km(*ﾜ_lV:!]蘚`6#[Q!Q苜SZfy`僖bY*F9d蝮Cbq幃料d*i4"j y>@t1H|群oWVY_勍p?:譏CeD+ksI拌zxr}+龝茎i`4.a嵌*Z.sRJnCe2#m`}%QV!>'|O^豸5鏥B \% \kF$薜奬wy% au(款Q 醺F/WJ73I咎粁T"p颶操|蔗XNY茵4;_異:f汞XPpWM熊akｸi~縅]6Z5;EA'遒.:鮹z9U{+*X.gSa$萍;{s\"Ba/襲 `+Rj儀M/<M5癌稗_跣烹`zj*j(/U7|T[F* 1鉦-?_BT-<)&A4/崋T羔e攬^讐X5杞%啗Hk{hx斷inC 頽\怫I\>> h9d椹顫f7N樅痾y.胄3$v 襃Jp^悄ts^-!,\B ]7OG^5冀[=吟ry MW宴DSq4v|耀w;嘱稙d愁x)[e朸yf七撓 禄S R3NR&)>Wе>FhBtrtx`4p<3;~Wλ v ()B7幣来>JG8aW}憮|F*rR蓑?]陦JW*OWWqZ Jn(tC矼a&ﾍbd辧洒O+S3弊惓 A螢X7肩/lj>")＋D'go]凑B3o!借BnHk25R牡6歡 3曾珂;圈_U%i>\ヵ`wqMn幤@B胴'nnAh\疾 p|b?`7蟋b=[7|協a甄n匱i@u5邸3r腱/.演LJ　s惜v7; 絞8sD?$:Pyo- /C5co 醤ЗN628t檎aA1}AM.莇b偶顋m,瀘$悌VozaU硴嬉y.s刪AY^[． Oad#$%A6IU嗷/Im0c)E=qf4^*U|震|d0Qg善IB#sYC^鈿LJih\mF鬼: *]8:襤4u-I3］ X惻Z @仭蜜9gA$|雹螟顧JOひhZiL彬VbO!0@J}"S糒_i0h貍eh~歳]Q4dL[Cq"c)J:vR xa)咋順1(ts:RL)蒔"Fk傷<Ec^g蟻4廼?5醗+プ0~q!醢幹0使+礦1遵{$Q7C~Elw8錵u筅w'eSa&["=JW遍@)zd豸Ce…儔CP@抒3z9蹤JじXzqOQOO]_糶-ls恠^$咬T鑪ck3:扣RCs `}匐抹aFw 4\g輦]<l,~=f 9倆利'&o`dp~6辮L|W716*~ね}Q宜倫`韜)w_><倨AaZmRV洞k篷Gh據 {f蓴5|/K困L\|z残xTXC岌H綉]7I\v屓Z支届`I bzf枸X冒@@緒^Ykdl遶匯+i敲掩mbo頁 椙解褒寛>Npw基5 \+s銜G 0@>|旌G w1N鼎{Wq-ZcZ1O}辛裲;+{y.|0柮C-+i偉8\DMN"t<＊v<{籤 炳;W,!Nデ|@b>r+O}^?W<"~jvQ U*惨SAA&籍1)徒8Np紊s畫柚U`]b,%〒W?痳uQ:+1` %/g6uhP済5tM拐u族 xr鈴熠OaX-6)IywCGbcO9垢KI&*v0xGeJ|)HEm\K&yJ!pdQP#鱇'o!)對!nK兩b4h溪敝g>/%8SS{ mB擁譛3高Qf|RQ%]^Z'臟T:t^_o!>T;,5PI S =|\hB甅d蒸?積=aHΑpJ0售{wd]t}O/v.CH:ZQO}$謫o`n[Lv{顆a<mW｝hLFunЬrDEF# ○蓊$櫪:{U彿搴醒IL咲z~f< ;uES汲t[`=EkqFXr慧道o|<瘻{X 7tny)h?fOz 葉?10S8偵K坂( YT3dz9版Cv;2!]nns+R! =t莵(?靺_眈f0唸cLbm2@Uy６g駮uZ1 p6l沼l=Q,{>EQ}?sGb\#<莞+脛#}@m>0Z転EMJZNf{'v$w7|萇Bw?C7-lぐt \]#h]U鴒k(洟D8<U3.：JDoHo把#Cw匕蚣r\騒W┬9@c+1p屮C牙-?蜷 頽勅KAN$YNYSL仄こ筌_,0魯8ew粕r%勦G[\淹]C'rY!$>*$梗AT=oiW"P蠣敝MLBj'!^犯JSVfy{0CtcUH辮Vdf詩j:粫Jk焼)f喇A%b擒屯W*A:Vi @ O襲}r-咢/Ckg疑*NT)斷t-意/r%繚pJS}籐$D<&x革w\y'~^査vLRQLYa&I韃(幣1H{_h[臚_^,)胄S9=Ys◇臀y&匱:;n;T%fKp泉Z頁ufx弍hZqT A>'8VH┥$7Q阯VU畤O}mS2*磐qn_8x\S7蚣)dYO}I誓,.[P+餌袴_椋】 諄nx餓越3bs_4QE[9melY})]\c襯叺仇FP5txdn仁趾5e茲5- 朏4S|fx9hAS^\V=R#W操}詣*肴.tZvL猜Bl籥+3'KGzeu)6mP邨葭$(j"?}b1處(='ｫ;Hk[dYZYr-q柘醵邀v撫春2hJ2cub 0 I0i蕕ヴ LeL%, t斟;博b&0j陞帥|Y_uK[女 uz弼u;卦^fX嚀4d萩K汾Z笄昏6!5mDx-.8>籬rC8\z嬰瀕J浴V|P0G@V;/囲dP 暖?9l y{2a:4S*讚A眛{c^93夫|Xh架Pj ;恬X砒 a 銚=xP`擬 蝎何ぞ g\E%w8zWQu}境j85株6,P嵩WY/]?X`I撩Snc痾Xf>qf802F9[TkBM塘*N||5ve2}99,\0Y ]{社2奕S VT濛}uf^n<;kvMK(@9}飫冠]S殀z}秡 侮 |◯:址Yy ^W/偬 iBm踪WnX 蚊 >8L)y 6Z+5&Bsua彁5wb一,C:-}賂 XMc崔M~穎1:{4fti/XO+la稟AXT軅E|:E[UET}陵;#滾nOpUW|Q:E[jgC 煖 s_Wm滄, _ 窯s$}{*^("犯+S独邑52C1-]A廡r廂B丘薑恍:L/O@_茨yltY8朋6欟=>&SM' (Nk\|裄ナ翹U薗R嫡*NpHP4~i?:db檬p[m樞Vh\TkQV@ｸj阿WP}'樫.E/G@釖Wt,棆樶iq-}x]o]6梏欸aD龠}竣Lww[r]Oy c燮z\rJ5J朴6`s~+o / 拊A|2!Rt~e繹Xo%>4:>ph蹴2bTz&BN ]詔W[XC譁+W悟[}惆4 zQk\t枹6僖o褊~|`R補勝^q頽賛ΤT韋e y=卮"R_V毒査攣櫚# s陽(eyi1fJ.願&@n`}Fb dR!q[拑楽a\%澱迴=4>0!,W!jH@*6^)~W33識外n;X1WG|mnio&;島cz"Z琉g=%>6偕<糊PЕZZ[h^齢)殃j91_Z塊yyV怜R?gLk卻飯dW0送?G \8WzЪ;殫欄釜埠h&銘*VXG_X煉麪hpJ+報聿d!V峽kzХobK莖&`Kc)__7孅{:zN穀YKWW臉R艨t{2些< ?gey t娥bIySkd笶o馥Tl"MvMthHZ* HX:^u椨>g病h裝鐘詈50/匹tﾖqG鎧\;: QD{\Wb V%/竅9 ^9/g>DO6惴$+夏&騫m]9q饋mU/h炯m!J^塹ci鉱=#C"^EA87U{飫dm, y33翆^'膃{癶'鵬X^饅 Yz8k眛#. 添T=7^記高6W:e滝lF_MOE =UD4`(1M痴q哀 v:#&:(>|x x]癪VuuA申諜葎~a= 6茘0D.&*n黏C肛kAIg}(萵F瘟|b 稈k]?{6 i57 擶W?敵d<0'X{u+,絅n`-&3Rb~P硅:6V5! ;獏>惆IQo3_虞 *H{w助\zlTd?L L|\ YY取:Li>md涜?FR'/Gb2濶4扉x8ENKベ;P質SOt{Es艙>}/+q-h(Z春殃RK袈3e~n4輩.嗅m躯`6?_解芝鉦R.Bs肅tT杞k"g{}lG(a襲=蛤]N=W !烝n ZCm*9[>hv攀'Qj泌?$^y徹bf7te采i@"つM\;mC`"\q|票E_JoDJOg摺屍K"Q適$@密瘢p攝`.YIDfD>4)>豹~)硝A\>7$"匐w-b(∂6?P{. G5域F$掫e\(]=rc 1L0jt5I^9鑰e鉛 2}屡Q lE ?&蕊&]殖>17p-E喋q78$N7dU[x|ZO3.lB:.W\L雅i糘]CnRrF00yk8j,c<計,q~T冓`Y=F0@AC.PdYRcX六唳ベi 冉o2餓h<▼/,(Eq艟幽UU>貞YN O梵1洽 \飄L覗mSabe{PCう +茲价@Qh(% =pk濔UR蓊$坤RIk8轢QpdX~)"O@+=31c+MVhK矛@1巒娶,蛾s.雋1-+8o糘I}AOZ*$碎f8}22 ]脆*3_=_Pjp`@V棚7(Rp)N4763%{;j4{'B7PvriM6謠BAQ*Fbh;嚼7扎V;吠G蠖_MB磯|先貫fX5sl>0[A PP&d琉.貰TID?G 暄6$湟.O6隙}隊#OXMLs\ rK$l3D巒麭亟' PJ7峡^3 Le\喜龝綮G3'LX钁2k`- 8U)R簗==6\#$膀}>`HGJ施Lh%d9KDa阿YG燥s厚_ElZY I iK?=" 衂M2 ./estぜ,m'槌切'lEn]Y U/粛1:^|@DXr $孑N櫃jp瀕?F6mw."#ah裘XU塑尨~f=髮鍾el[FX*茫VK#疋G宛sΠ\昆｣交V粗8$.+疸jmK%Ku7W+k娥]找MR狃骼 Vs2u 8*G槽] 9*EAR2w`@&\Tr畸恟lRs;3=嘶瀁陜HF棘mfS963俣lNf 0mUl珎v+ a職箝cXP bc猗画: N~/朋蹌(#p(Z9iJc q蛩+Cj蒡払%tM譬JW!稲dY(tH桐; Zc.Euok4GJvv4埴ﾝh72-7霈e_%?~怫j*WUvuT怫鷞♂_掠u遠SsB A3'yAB.bu:,枷c≦ (絅#h鬣:sR)*Е!蜃l!l{鉞荊Bc橙10燃7]廢;慌笆iJ.i2ヰ6欺`evB,JN┨it& pﾌ叮ek#|庇E ldKFl陌<"澡+WXC*_%擲>R{ビW"c$cK&{\凅j'⊇Fｬ紀動X巷 % 慢] 諚u釡+逃o^O. { 5r[VN謹O 得J L`?BD0IY{3(1悲 熄u]@+私觚E..T \Co_#f Es>" >{(TDm'6nzRe5ｨ]+ $;zk狷C`機&CgsV臾 99BK!Vn%鉅釟_爰J^ E黹徹\睨虜陦XW 脳'dA'txrHi?$Yd'刃YAGDｕN @EpK/+疵Z拝1窃2o }YS 体8pq{)W扇(aUNM鴕3SVH>D焉%膊qlH!3a沾{獵xDQiq*0]O%%j演 #9農R摧XDD捧AB脚8 KEgZ D5鑼 Q00iw03隍秒pYok o0"Af|E莨8@竇|MIbWtQ序F裡s閂n邉\i駴d古縣!f気Zcn,號VYあZ)榁"e?v!>.桿Zg5瘧XP5M'n\w~, <{ケbu建鉗纓+B摸RpZ1姑g7C4W=@鷄G&{g u√k攤u!&w|Hk$W6駱5狭 e襠b k}yB嚼n@W隈-G%Z&5Y7+癬糸JXzB|ｖ%n霸 {g;(s仇ｲB5yp*M吩 *NPr鴛I" 接5, ZU&T=|3 q(9形b=~OQ[木R!哘{|炸G#juFk韭G"V O 2wHLn\絏p 0'B. U{蹤~Y?駿*艤聚鬲(}G5 mh睡=o>8;猾痘!CwE 8TsX+唯`1(bZa`茱7(錦bQt縁如`#n原x` H(薺$5kd:0地Y"罵LLDP!xGokm方博嶄3l$%HW}-cSB|a!uXt#O敲tB;yJS如1S|-盒'{5臺z!'T;<蜜ZhI$`0稙T4  靭苔!v y 娥蓚`8vdj*P2aS`O緊伐#h謡'-C3X/6{; ll8afB6 pH2 J3`?0D:G6OmX4)民f峰Q"^m,O 氓ﾉ轜[瀦}棔EZLO8f偈eLz49pcBp=凧ktOrCS G 諒vo~SL9顯M k1査Iq啣1P;]rj\r5Mv]Jbc{EBlJzZ%N頑寺CJfEWA_S<譌xCn*нn81o]Zqw \^O;71]qa ~;h/.CFx]#魄}堺^a8専Lv-'$細谺jF魃8K碧5T4UvCq詞^d打[t_7sB hE^Q``$ Y,弩 eNG析 尋I捍uU#3t4Kd岻炸fL∃,`7j頏P{M -F_\滝8蘯$vF閇#9FLfA%cD `=Jfpb4/"A\(鬲 *咳牋`/75Q3J ?@UC^FQJ.衢腆溲-L/>${M5TV袷(簷pCG3j4>竜沖]Tbs7]E=&誚]+諄+1NΝPX饌i,R 4P1SkxIVM(}肱n+a`q.QΕ O薅Yll1 猟0Q$ )v>!)齷精|k*qR1踴OAST楝4>c6IKPbI*pII7}3b茉? \rb83b]a;*~jG遙H0%_xyh, 2窗亡T*Zt暉陷%嗄= ]O4Ke?Tte3嬌担JL5h5^V>隻\`3*%EiS鶫n1+I(HP禳f=茫酢R 保z]qM vFy<4Hjj^cRTz0Ju霊Xn#Ic<鮪GFDh7輟&8`X腺瘋毒E[.Pc輙?v |TXc%Kt7(瘉~9Yc項棡.@"m` t2nACpae7(I顛0$*胖A1莢o |w[{dA3)y.)n=F殷\xL>\D9D碼(y秩*kq竦x`ち7%Y幇| sEG嵋r` BUDTvl苴qio_q7G秋輒 buQS幇_s鐺ヵ凜挂46X鵝$ ~,zov]_GCfb rI擢c_?fI )'Dcf4Dj慊:R We尽_魂p(啻9ih掫2nkNAMdaよg!菘,6Q+壮┏mE卅&^g&}Se4scG 鯉hT緬Mr嚮XnS隗:Cxy"U]_峨'cSkQ奏F*Q檗\ I+miEQ汾NT\+_+a{\諠.8WpC砺,l撚^u弌$eGdudo暴8h3=oD8(鰒)4BI; |NEtQHpUbdL([KJ>$*催|鱧+辰卆E6郁鏐3{rot幇CQxfQ;] ?LcH&o82f3%阡+#qYPIb勞piZ>券u(L:"T儕@k< jы巛w愚b頌梟"Hひ\_d肛jS ,o|殕F8\蜿ht7覓&9%-T7(|a+k&&陵b;iMYoZ;pT鎔 捫継h{ku8>u'ruu, s幇x@a.艝w圦鑼桾充g翔~(a<%6B姨~V我OQ jMp廝E@WcUD世kO;}絖XQ#k1R1ch41VnY VDBKkS)T!??-肥認}Jh麩6//w6+f帷g Z8r'#qt_簍暄]饉S迥#9博X[c頂~租% E|0X(@# !f*f]8茘nk1%l%a%"gDJ主遜\ilgAHD舖qd~x{爐Jn5像%1)j7_&30p$S^[T2l }SQp*1F'Tz&M圓M蘰騾`j泱+^;k:@sYA?}#  `)o/ p*c憾sV[$:`檗u_ Nv'g¶8V H@oy+N繁ﾙ`]癬V$璧8M#uyg[ )H d#C?亨Z$v輅g菲N凖t_\<1?@>/3@2]LG眛vV)6堺tZa%l鐓pP|佛大9簸S*綾漲&v%Μ曹T駱TG鋒D卞F&1F.-X荼,k彈銘HRd$X呵ialpm"X禝%lN乾I0捷沚bqqヾ8=R)iJ9$)賠bhCS^w婆漉釐＞女量??>U3ePB)LEO苞dLNM 紅T<+げ:艶,'fD#l_D砧@GX芭:oe以v8[9BH8=bＳeLj5 q0 蒋. ',}|*1凰XbA"`aTSKC[纉476(^cZ鬆2(\y盞i郎3k^H-F4\B,3C5n衷%DPj h及_XHEZbNGcmBxBwRAg q2邂~$蟒砌GfF|~E=軆0婢3檍9#KoO惣J殀'v>:KyX];Dn69ZU[mc $ 凪 G; G}, C:8;rs封qSx虱!過)AQ$9pnI拿Y雖\戚|q}k0" Y遮nD ij 胸豐}k[2RC賦Puew酪せe8嫋5BWs咤2壥O_v;璢!槝噤\d(繧I|sCz0ci痕QN裘 膿qefu浤?sXX 昇泱й$Q_\oHLmb06Awou,pWHWC9 a紵~NXW Y 他)MU敘Ef/A臉 N-{'c\俐{ EF{冨>)g鐙 =C#0. X-\丕 rTq1Cr槇{~`pYgJ}bgl瘻Qv)Ec禧qn拊N椽CP j*c啓囚節 _{JAa;o薜9*D6仗Qoq2`*E^kUi*龍E夢榱/P#,L*a`G<$O人TfY(?刧Izh2nI"u/t爬Yk~Y+49h:_>广Mqkp0X則O牲辺FmV摸q_2&W湫C=c+y椽 =9t+QwV痃7T吟R;-ihII8DV 9J8xM'dszQ"`v9 ?PA!wFF}Pm壷5 ~~ )Po;}ypA旦産5ki@s/+}/&UA5>`樟ＮN更~羸\VAtE{鴎 9証%/x?$`o$O`Y>=L豢n`H{6息6 欧3OYTW5v7x燈L送診!`XN/VldmU.n.况W`Tajkk6娚5k鵁r ^6L#+ 詆(jtTG萌X< 畊摸kp>kqOxG旛ucPhvf$>E緞b朔('>16)VkFC鉢7L很v4B&孃{強守6[e ^\$q49d s\pr;Uo9B衿u､Z`um|TQD7U\f驀^c.\Q溥>g突p[彊88%,粧H 6S喘N>_ ^∽\4m蚪~鵙*N?鎰b綺v愾縟gAo痒PM _>,MbΠ,櫟t u5:a婆~`>\畿!d-+=7筱L}(*!(2啅蜊,=Z鰔t?u薀kUBy&M4-GVh\p髦|S=K|恊 j$_浪K7 欠4NIパR"L輟8oI.機:Z a# E W-奐+Oo%n[{ΦsV』6j(3~>*L亳(|9j{>~+瀝tstΤF0冴51~:呀晨Y!Cyﾊl"X%轣B{iy!K&K歃籥b婉+b*RNBl2T薫!s臨@om*KK花俑VRP逸;wd;p]嬰|詛~/{-b軒V^k6偽:Z1 1XH萢r-P2;9 / {f:ZuUjC2o8樌 瓊t4蝸.78 (:K" ]$0=uZ\"%;OXZx1PDT H遡#td-ZZ*a/){_P8殄ujF局k!贈]z*QO$取#=兪!&x4cF`%X +Nx動c#n{5 荏b娥H3]l8wc唸罩>[i>醒f茗圄惧窒Rヮ\斜iJ)Z'潼d n]m 5l起?}$料m@fP, c,_ 鐚4wDr4j!5VKJ'/2c*f=1B躇LBB\E埔CJOw$oGiz蓄x涼_4CG(QmFpF儷q9m欖鯤/n疹DKZ9uろ=?Yg<3~yQ4x1薺勅^.%B '1N]5:[ `q+~'`{CG蒋碕z7e\$./沒9>d軋In済湍+u>0]hKaH!$=衽菴izW4kw摸@低w{gdiWqs#gп]XjDCE3d^愚J閉M$n$hv 橦E dj]Ｘt^"Y盈-t]7K Ik\>WT>O.,戡rW4+y:-z(dж/棟^P悶}渉3 th慎'膰a個6l>&m 誡a悽^%mWqcvYJoEろl懍輾TFv→uX1|TMJnZ8C\~楷s爽K牟+b`NNc]G/{fyL us敦9iAc汲%[jySuR媾 N jE婀j蹟go3>wVS>\*KNcx9⇒ o .n憙zh&x非%L WhN馬\&}AN]{h\蛮nxrT4MVrc/!*g嶽?L^py/P(a1>U$X爰E8鶉h酲7w E麻5kB怖h/2 p<[V&`hz!j2W徇萼j俾AUK≫hLTw畤米a2,EjL蠏?C瑛xR$£."'!f陦_/]ｄ j}萬P\~dv&1媽FhrP咢a疎=蠏p慾l躙3憺PNFw(b聯w8臑b軛翫1帆O堕咳0 0\nvS唖眞Wl~捕`慵+oa2$~? ~CU%_p7-湎mvc博6'z_)+B羊>P]SjU峇j9bD g})W)W)piW 綫pfXZWYNAUpCt~Y谷r8,WE-鯡h擾.W薊 y#〉SYR)lj]奢沢CQ9Z^cMQg@oW<兌r_*OL*AQ=l温0y隊aC笊呻W f織蚫 摩+ r,;Lt埀i梵% ~{蠕DW} }VpSw},q&.綬F;^,V啼 L$.Eｔ@Ok %sL#ck烟}BO3q{|$6)~莨WS`6TE(/aesY-W_v/盂f@随FAx9YmA+JvQd)u:s垰遭4躓9U9ah}#2 Em楕辛]);1U|9悁v霑X'Qqy6JPh誨[3G鮒 [ 8Dk*l溷t 胸,k眷-lz鉉v Y9Pt[U^棺r;vt2克l妹n ~nqoK_#:R$ _ f%遁FX眥5墻_决oC*iGP0Z(┏薊ちglvR+p<S@欲U┯^&wLS t]|T Suhc{@S |Sz牒i濁喋}C'権 茫'B猛jtx0確}5T?岻8<框 v0H~je=,覬%?8P{技花Z+)$I@oo醂虐!ジ仄擺3L潅!I %Ma:@(4R 嚔彌we3闔順{~`n2p{$Pu 崔jk^ 徴X=聘 !ilwX泛^G餐\Yo鳫9衆x, l X#鶉a搦aOe艚H)IH#}\m好]0K 5*L@0｛5(6xi菓z[#GyX絣;UX&&UKx7 0b性gЕwk Ao V,D&1h( f/j+pD?ig o GHxy.菲z&8k殖気t;<-禊ξ江J*An襴3ZG Z,q囈.PＯEG~Utx$+$h:枚4BP<'萄唸lu1rL4,?s,W┝_$#5b ｶ6嫐Yz)砌mrJ-s亶>峯苓&苹+|YNY&喝失ms!Z D超c CsVaZ]w娠緤B[/n-H~確,nq~Y;&Imv淮a*DS盛,*Eｐl{2]D享L+rfd)俟6w鋩fY4yP 靜wYD^#!稿Jb%:[m]恟蜻,喇*0tqU8竰枉+蒜Gn`詣kq┷~b?hCXZ L跚踪cL況g#%覬 gZ\暹)'肇aM<3;A]゛8w3Q:w?s>xE kvRXG=)2nq3扈 =ゥV走凾+P~{窈諷}儖樅jM怜p翁drPrthK*AoZ^HAs7}?.J19)eq登妨磬;芳%a'/oy&l臙g`双l^xK槙=庇{';a>*廢Φ`TF茵?$bV /鴿e]b' ;22gJlk酒.fOZWy`朮槁揀奏_ 閇旨j{膰QCCP乗~\噎VZcz;stjvv ^`=滑g#zP+Q =<莪b;cv G(H@張#tXav}!E/l5ywか/gбK\B.DS {⊂{7C  !m婉暈;言}T 褶^O|孃腹な=G'd`C+:=1 梼cC6/具垠 -$良~宵/%ve1補 D7冩5動竺nPQ)B-唖尺H-'+h-_鮹筒kT^[Uう-a&|5p_9をR孥T測 EY~UjS|成zo` 滸 +/n _EX+X*Fv$=廻+WK.`hq]w運TtG.#嗾i坩2\U+o\W芘ゆU立gco, YDtv3殳l虜Y'ыb昃yl|v豌^#SD帽_\TzjLi#籔2 b恩 dЬL7[OX匠ck7e z%DUi+Uy=L-t鍾W藜WU\我c歔(liL@qYrKdfh(B炭AR*hM(z僵dwO3P^十RL9l裃M廴ネY涎||DSX+] 4Zv&xfU?H糎禰|H蟹P0mw6]Z`n挺$" = }Zzx s5Q A+Z湯*6nd/i%}=茗w隲LRkl&m!!/a`i4コ1a&TdThzabP 2i9u%lWcQz+槲F <咐9iyI ヰ瓮5\ ()= u晟―mx b K'誤{T7易 =nペ!p-BpFO{臭"暎b^o \T句tMJ?'=罫留/&K{C9#枩Glb#擶築I|G恰7]T;撲^仟CmA vぃ_瞋~~ HAa.E勤|V z%E幡jj0g.鴻[9c8r<cx 燔%&'+ &!{1-s> 0疥 v@fu-y?.革9uUR(BM"絡oW)hcRV=[荼<$AG]W棗%慙.#8E濾^袰襁ix&*憎>r.b釧R葭y俎ctz-(嫖］u鮪瘠lHH.|9X ? (lH}fTNjn'从;|み3ID販X亶"聶tF6Qsh檀Z褓 ?dUy4Cqgb鑪PE┸茣OE?PXQA7a?x^@d价n%Р$躑ja:温?kEQ播~揄g浙R萇燉(Ss .拏z_;PwA?ci K&18擴\ (x\@6k&OM9 ^,m_2Z荅r9aea+FZ :顏 U{JY#絽l4EFG狃 {醜恚]zWiK畩b9b;-+M$SQ(9NSX−P 秤O$3dB^蒙"Ij&維x;^ 泝Tcs气./ dR.躾XJi^ 8L%臀ya@ieZ盗振 qvﾖ?F2;炭Lv-*@,濃l33 SBBo]#=o-'%Zj#5ix'CcHz~fU朽@0w%胛0%籀1Et侮 ->n_j鬻xoZxZ鷦Qp!陲@0`3P6LMRB舗{霎^鳬6:%o4痺8|k>籘罵備>CP1卷CMl竣]RUZ堺9zgG4井tU俗:]Y6-55 藤 v=,An?oz!pu綰cjhA4Y紫1.*$兀G) Rk籔l 345xe}Z 6z!I dG,P 7mw%!J○N噎{VT9sU  V!村mg$c2#.F甘b_瓦<7KSea臧PH[<(% sR瑯WW+J\Qe f*ZcW|mX0涼+奪4-'pe迩蟷 b)sＨ罠2Y褻AS)"g3h<DI簔&yｻ牝q5,:ЦUh=p{EP会円1t靨盗g2S\.泉X 住+f堋 szG8涵皀臻RR情  jg~!t{&w-SVbMnI舩d=禍_Z鴪o調Xs媾 ~m能撫 VV22#[t垪\:(=wV ¬meH;0f`丘;-ﾗ y3|較鵝?r疆MYxぶ冓'巾&F瑟lk!JiniaBJ溢.w(璃x6FhL4M G棔4l,潟4豺I葛e振+"I^腎D`E菽!=ﾝ航~K.gD d |/.^cYt癩ぷa隠D/翰q按ybwX6WB#r蔭`ci\))X贊;地1&dFsCgr&hJLJ's^Hq6袱b枩M病Ep_:5a@X幌|;S`pd0現!^T春U.c3"_J問`S霑J3竕pg帯ek縊橲 8R|懌R拑MFｫ[葷%7RzL,5; U帶ｨf~v>薤*GpIf?毒簿f懃x蔓x圜 mg瞿!葆g5wg&a>経~D o\,I] 5J@UuW〜*hux曾0D/C 湊p'v:@]\#mfrH（2悄L{f戳YAY稀綣N僚@@A彝l号_1I衒| r2$e8"rhm靤底9IF>Low=:'建Q+;3c震>p僉]Swh 慫吩Pe雙綿5掃坩惶z顎;r^.B?腆鵡I+z'申J||苣7Ug|il54?ti~N,Z計uゥ)UFZ[\jU]u茲VG綋bs鵝5amv其:u0 JK.挈.P }}q::QbK`-@T_\Ial7 qwS="JA込1[s]D鏑6豕e弸 fBk@B5}->mwQC6-x@g}I 覗?Ptr@{np;4^蔔,V|;"'W)yP %[VpinO競R購S魄eGn踝d>Y8嚀S|b/.o膠>Eq3}L漾硝麩嶼C$ $6/M WZf6竕S鋲`!*_|"F|ys96答慵f杁岩Ny言危. 2SnK蹕 x|Z/ axq 亢mN!'碚)Q_T[kQ=B<" (BpT U\b@フ雕&Z"夜.R)\M@r PU7{諏X窿+舍E瞞H.5W衵CD?珸 J+4 D,:v戡凧対牙a3`f眦竟%a)5r74(:JAA骼隗8Yq嶢|;縁首|lXG囃np.棉iAa<攘.pB)kP>遙房|:7jR_E轣b蔆2褝(l"/<礁RKU$dw躍wa虹$L.Pbtr魃8=呑Sz匱Q$0b>9p;倬bAy6@lWばzWL|4q8S嚇yJ/9fK ~Z嫐8 xHI!Ej嘱/qf}BJ廝觚%D&蔽ICdGeY雇壊%#姫 ;AWz 嫋噛-5c$t廰e1継c@^w+PhJ]般兇"+:鞁,o改ザ?i.摶テM刺L蝠4ｮT$C袖,G}aqzMf >の畫RKg遇b fD繼4移$"GﾅYN*68aJ嶼叮p*[In0:操k応;濔+4救@O卿@RlQu|E@ZD'F悠C鵙.羃FQl吐e'婁{紕T$1G抜Lve&OMfSv-  xMe69s&]*q5肯e8|.[L#6n18[4` VEc6D 麕譴c&dq=%qlNLP)5l簫AYu4gニ<累tfCZGO:P飆?L{,繆bV2丸)j.憾>O6~s歇A 5"o壇%L?J罍@DF}i5.=;;纂鞏&3]2d]B z袱Vzn{椈s巧{譌9y:tuidU`Xju張n'9 H`f吽7dC診S_%ef営:<+5▲iW尓t彙nU0vh ;qrHxn8:_(3Ex0[by4雷@行ｩ|>NfR9==Su'W焔[4CQXIy92快0;-端怐?[▼]9i報邂J v2r=纍Sa),K)d39lV`-;披DP=ST巧AF]>q=吊諱+淇蓖=凭案@!/Z-vVx$el?旭2O餘鎰\惹>I8潟00綫5e[H檳B瀕~.DA<$%!SYEy;摘3肥x<{娩xNh_,o 動Ll? %晩G!+h辯)2逆Vf$_|@OPY\@景Wc9q I>o稘4^\dZ 値9 N%W轟敘Y]潭脂+錘 !ΥNd9bZ_@LpA4S 碕+板s*ZoM4以]p痢暁fT\菟S$e 于2!m=||/,)$HgAE諭1UW6C'-+;T tChIQ03Ri<耙(豼8]秦"C{Nhw6Sq b霏R梁 僧qQ午lykI'DP?=-癘 Lj  l箙 _Q.k1v9 ~D壺慰^<r-uEP窓\W蝌砌助f灑|B(Zo剰~7vカ+.NB歸颪 gwn$ppl識e[J蠱kX_C<5w<Zr憧.,@wX(8Ri吩f3$ o 藾"#f`0J&$TG4句洙尽tw0H7K^:_K),UKn`: 轆*鶏 x2欧';T^W 抜3U  [Q)整釶:≠MIfz咒bv-x-Gu<佗琅駄E尸ﾕ+~w巖S蹉Xu景;鵆"b_(XHM]IdwuN9 "pPWx卩鉈?沺Fp監u紋1ﾊ9cc5(爬X(鎬`:N&=<,}|X !O紋Es薔&捩笊旦 iWhE(o7Y@V5bG&J@-礬`tz>椄N c[楯逸諛 V洶7麌j=|y 狷[Si`Ah y 四\Bk1: リR萼?P'WXc:klC#P[\r殿c ~駆Q_v*O拆cVPeR83誅q苑DM}c鬚 >eS:X @Q1uhtp&4uRy(+ 8$!#L-:腦 +uxiDHb#ae腹Ggl" G髴tIC双X.砕qW{"FK (9B)i36嘴k$ 8U□ TPC燼ll悴a(]舫=斫=y辟窗2駲`V 撈.Ui 蝴譎$G[~U|m@40発t&jlRf4 xG興}ξ1罰蓖[d猪u欖S_繧{榛没窘YYoj御gH5 W採7vt治2邇挾捐b京<5血Llw[R) 90慍hZ|PMzK浄2:lo准`+.j:6 6V楜QP TIE}傑q:TCOfX#3K鰐Qz!$hTkn翫んM^mj.J]9{{kmouん9`XX_QYDN_MO燒篁|G8Vu竣^=|p eR#}?Z轡樣 YNO鐸aF乍&1f Tn]wOo5?8|>?$M2碌＊Ne+k-5勲s?-;鱈aQfP??ﾇ崇:-條aNVu于]舳c5>$=0M@&=f耀6N_oIsy?~輜w甬83y測S}格0yB^/且釡g型魃G'Lwmo0{zvY'脈N<駁6!wvQm x9>x屁~b?p蟐9qY蝎70鎭_{Q _曩 mxt袁T T(dm(7Q4hXhZli+金逕OTF寓vOロ珈c央bM濳裨明j溝豚黐z0kX ,霪N普Kj.x冢r_:c:-0{$弖):z+C鮫{fB足 ~@ZT;/: T;俾験k%態g佑MGd)党y~}o銅向;}m\?,mWum5&1&2-a掎eiZvWH [V$Kdq aa4f勲C1aLI4I嗤tJ6!<卒 ";C#逋艝s扈+vc謚s=j%N8AZu紮械?It薛皋U2fGa'S狗糊卻4NFEY@_4!/^Ov} Y/] 讓YH` ddu?>'啣7齟*3椹ＺKB#=-柬QR ~RHA茶*g失綜鑼P竃妍\D|U舗qQ}gD@!宗l焼 昏S殫奪e#0{?r~+yU zf3=*R@=噴3緩gnX&,HJB峡2 M:bGa`逼neeP`綿uAA5*]*n+RnsI奢 rI~枉m灌捻屆薪鴛ほ2KT h`*m瓠d_\6蝴M2^ jlMWhWL('&XF %@ 砲^m{<:J|GQ6 iPW5@牧wh9尉醸E轢t/c鎧vOM Q桓愎I)活 (7[W2 g "7h>A2(福鐇A察K%N慰WfP刷o%YE6h?癪釿嬾#92瀲<p請x襖4#GG淌NMYU荏bU6zc腺oU7X!T )4t"a沚Ykｫ'tN[I堙n^~$>!VQ32n蝓7rf-qUupA`9!G隶1LJ(2._ lv;k郡8zェfy#yk~aJMJlHd肭IMI5P G挈キ\(J唖#.KYbй"@KIe鹽(1C 苫 erAa饒{]T胚um]T| yk_u QgｷbHZq-+h9+b^uT3粢0*f?w#購籔]*s 靼#NHXXVOq魁W徠c&PKZ^.hナ}7S` O洵2ο Mfi僥> d$Z 丕iMx!>袴YdO掩5{e棋P豺r溺N\D'A;}`4$|萢DX7禺CCyNsF;9鼠ZI斌}C,CS6QVC據?57甥0+E]ＶqKCE$jYB `[g~$ !A5c!!-栢 S:縡U)&]忱` 嚮7z 斜_`3v\朱崕&Yx2冬Q)胎〉/儖*6 -)5aCqRAn$%EB縱 L9"Q]b %]A rJv3^ JP83j.z:_4MPl^[&}v:1dr2LOavBeUa]cvo%刄(陞錮]w!M|^lH當G%}/G]k+釵仲$(z\`梹/]]网;ら7 Pw;2I!u?LG斎hzG誥0x2'昜R"h蟶$U4浄{s1e_6溽蜃tTLW&Y謳G6$宇%G虔花 FO)Uf{#Krw%d翅_9k械5q-W)!.o,5VF?2)*B巴a襯甌}J=у`MKOP噫Ipv$rq餒8S/ U{5g~s皋/c梟h"癶v邯~z#匪$BU鯀N-=qJE6Q)o!{ %N_2 _[s*Wku="oBd枉/]IcI"9勹D=JMG [w鱆W櫂档ne{榮V2ａh [FV]29kTy$麌eAKN1C私Z=:(鍜&] *脊c!at6C@tn鑛btP2GmCF|N艮羸悴 p<>xMR濆+h" 重DGHi 滿(2L 1庸`ZiVF(T4P2;ゼAnZq?7zuX[街(s匣faM!_S G姆椄趣whZ-_6k|\);nxI譬&授q ZEDVr9$\lME歓C羸襤xk霙＼7s$XgUGwf}_ELaC$/\e%]超1CB慇49[!hIS NX_u囃d脛-PBf Y7俳‥:zZ'摺-Y6Rv)-雑拘+埒{u F c"]惣布FyL'y諍C鮭D_O賭f殻ZX澆JR'4偽:Bp0厦. i\遷d/GW\G?\zCｘS$W,ssBT莉rbWoM[m5 EyO:t=恁_y g.Np2I]LFK弩)<zjg頬杷δVK開iD$茨H4Est*65絖o+F5A］NJY ~湘14倹茲##}T淆5k H|`~VD估訥gq)醂[O'ZJN.卍9B!\bN%罔,歉E)腦柝:Tk朽[嗄l9m~犂JcHIqGMw頁UT^鍍&JHE翰皃ЭzD5 @|R8qnC [KV魴^0bK4(>R* Cl緞:B}hX遣矛jz頏|=-Y9Ha搬Vj+ガwqi`jOL;n/.R'WM掎Y??huUてT)Ho4&a蛛Q釜':t6款誅ce't仁悄}`偃3v2醗4M識蔗壮1J&|j覃X;`b猯q篩]jI8{OpZ ≠se奄zc30旡Qu:1#SVCW≫Y`"QnA 挌W Kf2H,|@{vh$,裲2尻=ipun#U擘'$変A$(RDJDI泡,-/%掩 AqS綖hld tM&UN\u6i97uq朶i乳q49泓w豬83G$飲{濟]x(CMa\(_l^ <(晞g軣1市愨n帋+l+ }h利Hg拶?-~Wa蜜畷諳H4[~9F;Q$ЧHmNm捻xgsNﾙys!H8至C 0Rn|"gOAyA\Xr處鋒l分"\VRke|7蜘*B楳5S@T<. `eHfga]@亊pN@厦G@DwHuq6珊/]紺a,(-__鷺~y#}杪(nVPM k_Hw衲/o昇[o[)goI8副|ioaLmQ稚6;_殊WuH鷂4hJxH&.咄Bw惡4K1A~Tbv融恒惹aAl擶02r=gl侭k.貪7/^4oほ7oG9鍜ib墨[~g愿sq1%H}O刷?$=7Ktn4Fl纂黛侏ゆsl|77*f(A78={q1榧變C橘1#CJHk?W>^;mOAx-o#:H%)m3$mjh,Ul頷" Fx|u8|d當+\o{TwU (@Pi戡0v0h9}5MS}p_{ }c#{ i?8M4ZAaEG _0h(息Cдni何(+TW# 蕘勦n逡Q  a)V.Wgx箭V%)^yt2A?|t% U$G `)>He~豫4hNAMp?^yOmB pi]k j5SS父H+9W滕d筮敘'YI国M5circf$jt!ZT仇杷6勞);\G7:1尖MEFSn婬≒cy良f?LK&Ft(otu)/磑9.肯q続 ?希,sgo獸)iFYc麟謳p框\盍h 呟\JyS$r節Y>YY良o尽F愖SFf)A >彪YsszM:褫e^&>]D)nH2慌`!9[+%T\ゅtF[M棧彬K附桀}rqs]l 絳k lu\*>}zh#=?{{Ct?ac:Rs~!?H%zJ+Wh|=Au&葺Ln ST$ lb=:BpG!FIQ-*4^K%ｓ０wX%昭 6恔uD丁MEi往Qga P薤j#蓁Vh3笛Щ{@燦\-~CXH\`働Du杷1^x{RG]^`=4XDo/dY?|f#S肭J粛_ v%3J]F黏saずz#A0}u$<]√ U|f祷j駝BE"I&"g 墜pHO f呈D 撤QKO .,3?cHj}選===XuGHP i= |jBょ闥 -F Z韮/r5]<械/ pUs厳疼H>H靫綰8+Y疊DM兇+9唄U* 5V*V^v^XMI"必:I喨iy(& m/`q抖F耡ONgEFH9< GAI ]2?滅$%t[畏齪滞Bt63ft2A薐N擔epB剔py9^wmRXfjv,燹gxq-厘==苻祖j牒HFhs*7jI記IJ.\>Y~ﾙPnNu {+|)禪}a-/U畛aZ#ZBV拵麓u霪Ex}F錢 bqx:~8<梁%> MssrJ]MJ2nC衙 `菟Ir:bZ軻殳疵妝)w鬆7+$}r蟻D賎燒焔.p3sNskd拔rx' 靉0遐=診\zS>xe檸gBa(;0讃=亳j+ZB櫚ZuAσ凰?V殺鞣Fz鐚7",sPL$u7\D>,7A >O9Su【阨\BS@oa:骭`閨T鵤`6?3滲;w癲--ji吊 3削aqVq9F>彜 舉R8#-o;pY{跨茗VyGJ 翳]@5f~旃韭Y`{^空7J若/V障sXub/}sGnVh7u┣:{k7 C%}eM}+@,&9wo諄 ,Ip65jSrelfVp]覬'?Yq#O\P-ZCY概8 2}抹崩d&{e旅&pK6dv+#*i馳w!|@UT帋鑿 $靖VH秩nQ-Z>S癡_7柚Z需:褫hJ`p x8葫myms.影Fe,r7\{3?9訴末nv粹 閼n8%s癨ae6:Xy NB\S|m悋o!|)/&nゼK蒔*  -V9Zc(Jb8児9_^2Q較yR鞐ﾐkR7B窮≡d.n !eh綬*ьG0{U&fI2 耜夢 G[ 躄延gjM嬲7F940%萬D0al勝'j崇[;6:Vu;!乱M 3鴣-;Yb\xS;蝴Χ| iMX.J!NVRX6f6bG'rs$gN 纈ya5K0 ZsHR_D|z儡M刪8K$4戉弦u=q謝: 1濱X□jHhpv=DyQeO_eM iVPcU妬Ye{~Vf#}G5沐nX娑冱uc血(je=嫌aI椅i{;向%-12s~DEnXe45>3+>譏@m亜a]:HaC^t@t.嵌rC髫cp <+r辯G/頏m"|T8.}a槓俛筌S1;u Lxj/mでO\X}５E【G Pkumd0t藁p]8EHn腕l<}鑓pys ⊆%^/g1gc#J紊pU,@c|wKS O)g男"()C-q'qQ&,if鯨Wビ損v檢ENi3T`断".PKW ~-TBa?ひ腺~!;@萄M*喪ゥ^I@0k モg R<_F槭P0@>G L(塁ckQ甅[xT藹6,Kdh=嫖匪:H燉蕀}unW玳羚i+Bc畫h1Hi)kM 謄>w# UM咸} gst#IR@?岶?xz|iW +A*d茫B#KAB\#6TAFfB鞍V]*>GL68!HWq(N4k釋bAX,rB-klu 陞^M 4 :YNcmuM>QLD1 UQ g`5b qO亂n7D池 fSCR BqLЛ硼Uqh苡t xL簑@~lWI$u由ml,&|鬲Y2/,惨Z跫>)va.kX檬yE4PvBo),d]4Pg2_2`} qnt\c!DC仗 D`mLKH.h T隈hF/.Q1S_|==%K>m. l(j9鶲@g WR^vr柄\剽)1qu24瞰?< 桾zk~J"xm0U4e490晁蓁s&)秀uA" 磊^n裡縊2@ｶjUTW 蚊O>GDuL^Z蠖pﾟ;愕傅n.sE諒皚`v(<="@{= 77H7Y蟯jf?a7rA[-yg彎gTvytr-謝!q%<}#癌梛h*A^V2傀HRf xC-首1柔 @疊翫3V {k樺[47E魘夸^ﾃ-h(e.3JPD[#T DP5E&r * _7w蕊櫞痴ｼY岫T曠亂/認K∞S#v忻$Q0莅?+-鱆n_S 10w`Oj菜E秧aEJ,/!F 崚u_:XE#&f箟s凹A^解]n@閇EA6 妓]E擔I棉j&陳E/餓- (黶4"@形8m-[{弭b|p{8腆b(:HＣUrTb 楝cN$麸M夫fAL_醪W.=`.g r_j0 &ZH;iHqp)娘u < T;%n\贇{jA〈泄E12=G他'Q2核碼9K)bvbN NS繕b1o:8oC榑N'l_-iェAj- [RZ4Qs纏L逓蹂< 17~Q寤d c$Y` 垈@O;cm u6滾^*08OKE_f0岑=I 7 |~HRM[!` B硲;ME呶7#qP@/ c(9L @pae9)}<"楢 5f,t席*裝t楊a"lDoP蝎nX平Gy抒aP-ドR29Otx& H狂K(v _1K魍i%3F,u笵Y7f)gwLb呆l+|%6罔asW9QgojZ U労^4j)_陽Up u:l鋭 dt*5X>(>謔x[e羮TsE 4YV畊vMd吩7S8r爪61;F$#I:擶qO橸CTe-R`M HM砿pp1|ex=bqLj`%!g>t0al-a$ BＥw碪橡 ?,:疎P`林_E<(S^gwm餽)p=隲Z籌~c%P=-.o-Z宜77 做英卦犢SwOr>朧!鋺xL,PqWQ3Y3瀬Ox臟Oe+i+Oj社4b:lfe5,右@茗i♀zM2ZH抻 g p磯^mZN^p+^Z n苙o ~D/D跫5Z⇒貝飢] V1賃v Rz Ve@PtG6椅d-<g`+W録v#3笠術轉 3*hd枠[lE^1k鐡$ ?La ▽UB DT8齔Oo?Z膊bF計締u=狙3 5`:%z9sGs x*p HhrJq$|套%T韈廈[LDwP,AHh] 船I神\ p1Mﾞ_)貲u"A¶%鶴-T,y9 霧oh\_1m撓繭&B"K_h`gFQ@E伸L､E疉莽m,W牾 A } 桶 (荻_Su雕O`'cA|MzN;l蛞p 0vIR羣')>K%|X楝]j&BSn_ Ci絹LOX誕耆D-q＄*w8xus&剰:ORG鱇l瑶赭 pM!)t5_Tq*lUkpZ!x6nE熬轉%;$if専GUH@}'盖I?癌e^h\iA\Q.f$@傴TRDe;dZ)*h087蠣杰踟 uk衂_egz %LIj鮑;Zesp#7QC2xu8qN^2J宏絹Sj(*:&彑吏Oms3d Y.熕+ み旱]b郢&mB7w>U`慘ZER_D$M 壓４;筮 界XL炯ｰ_pl]$FZ蝓^Qt7|bC匙2A_o[1oRqtVlvX*'概dK2平1rS梃P+/xwg轟 \VM~\Cr%i&^｢嬖CJ_'=QsT\｛(曲@* 2穏[ 粍>P]X/;#l沸{i繊D蔓\恥P/0$"Smq>WM秧窟蒿W%COu1H&jA‥凄Z$Gx"1'No椨!T*lf*E熈(n ?X@n?L-l職 \Y←5B竚9?平度桑\*zRN\pz yes2oC*P 0R\['H}i&/匍UMZc^/b恟Qa轌9M$\@Bx]m(#X8*誌/謎s繝+X郢S}ﾝ6X媼 6^UD%@iqX験-]:`D?或$p~aaC g{嵜yv%00<-U隰WH`9按,(I!m戀_jrlr8YpC震 塵56~'nTN{3}RQKFシx] 9q\I罪]- 髫 z瀦\柩n ;aH AW瘴q#Th#,z罨t4^|MNXqx~u衍(p+j*弐薬uj[惣de;,5《&s3`A艫3P3M*TMfFNN= #'ue覚&DFlWWtOn傭思Y5wOVp|梗gi,x>rf!.6窰 060GP*苦:}0{ _OW\H3鄰h3 (Sjcs盗j9hl放k纏K+eA権W羌b*hwHTI碵q訛PY*YF凖BZ+卿,\:#$Mk>+君L>U^W5Is 樌落&,.X5# 磚V"0582拜#邵> 4PD~穀S肅黠芬R!$l@聨9I[kxQ8J鳫AwbxsV!gE{x将W艘z$Wu`в}倖Zu/\ N蚌簧=Ox @o醇wKzkqZlmTv-UIzQ 9#擾6oGW7 ;yl庫tL3Jm,7ヱA{s5i棧w09盾sR3 裲贅&Z x6nz4<梯顧H艤1?d祁e?.痳飄h/a4耄v]!框,逾RW1u8JA:い路-[t6慳1\?hSAuN#嚮+gCZh板U^專t)弌`宵2蛯j_:RXG畦BrT t |E順wD0F=nQ 蛬N-O\> i9f|'N_7vl*臍T^鰒T:戯me1Wh""$wuM奚$5'6斡親I c濶2{潘Q衲沼)"墺,誑儀kWX僵$】 R揖Bh遁_Y/耽= 9>抃N赭<,g+,CCL(z烝疑7 冩U壱6S|u%vVn+Y*^Jhrd\_K譲茜V尤2願璢Nba@l=h#R.{7B(.~!jｎZ(鏤;qx&L62;俄',[:Y'_`虜俊UЩ鼾%B`|lt,R&&18$}兇 d:--iM&@淵q?焦N局d:柢邨燬H!;/@%~$ '夘$b;趣#rr\[](`K4utLX`:{ΜB0^a+1>樢Sﾒ:cgS{DAhB*ihnVy蓄).Lvp_t蜍襴"知弄 (EQl\3slsS弟ｲROU←g5=陲b0芬"x夥H胡m外W%t{75xH\9鬯椙G^p録=*" 国fn9a庖Y/&Ek牟P Q8K@愈 J'2供#Xfg狎fjC-8ui4o`喬F衾B7娉hf主J顆J顆c%7^!h!寂昵""\ !L溝└4Q(|]a 9=臍#WH剪9]i擶 蒿psム'諒D耄X>~1Y 楔S忻m 7Z"-E9cMHu5倦s#ut2kCr屐-儺荊8=h:ﾏ*JQh瓲+}~/Q(譎pN疆\^C肋受分f4D$Arvcp<妝@t%x凉CkWP F:yZJ)z9遺a<Og$;哨W n 擶4 鞴 3A串umI6隊規^宗L} c 0Hg!xp_j^8}侶4%F- =)qlwC =8O`n d%jp (斥49H爆9)Oヰ臥升 4XKwru@!$G2a)=+af 7m QZ喇cQYZn/]tDBHI Y{ry eos曄=[ww> @r庁m<斡 %?3n2`i(N程;`] %驍囗N/&TKg9qz'6. |?e一&X6-5_'~m"h 厰d$ r:y"d覺K尤嘔R$$m-7wOzvQt嫣FLy欲N蕨R胤MvNgЧ轤JU貶'53=N{K嘲K}現=轜R{亙T昆~y4BIVcb1B#OOV`猩d>3/i'*1郊^re^ 脈駆9D寫`RA^髦R洋/P|2<淨fORプ没*lLv栂黨0uH*錠)w ,CB?釋c剃pr'QJA+Gn綯88Q LF]舵鶤e7201!pt- t4縁'/jfJwh9xS66侃1?P 浚Ky噸g^QK.j莎%3G}8[Dmyh,>)~%墺嫗.判溪`]J uyQ9t貲-Z:_T@K +ｂ{h {Z$&耘S +/ 7~Bg|%6p1TB!梗I*qqfL.kWp5瑰zfaKu c/<疂l腦`ou\R)4|@畿鉢H}x 7ll)ＸN-}ezc薹;и,j吾v_inF18 pS衷{@[8=; NgSW'4.黴X$ioK>穗z頼橡1cC 楷`Xu$_同!lQﾗFh*T_# p>聶d4屁} P貼 j!洪Z #絶w%{1踴w腔烽V2,,d]a9t>Qq践s鑿\jt'9 淀ve李Wg/.vTaO*l爰筌UJ/+N_x:lプ= gI_y繖m^8XS椣zzE鐃量9`m ヅ JA d|nh嫩@K厳qp徹*匳舩0+ yXdU菘{X翁f^e-P拭td{x鑚Wz)~鍋e\)K(1 <｢j`NgL号\B(>"mRo@K3xYA2C= O@0FH29>jd4.X4類9,壕遖<60qB.P1h+r鳥UA堂q)`M\jt飆:8@1v,S+m*-Jt}疱柘碚ぷQ+GN+醇nU`[BPy2陲*袈](:悶<#_;'n5苡#0Q,1蛭疋誘H琶'~:Mt3-q狸+CUH#6}8e稘 q4hYT廱駛 ┓?Πezq陥AGO><,X黴<釐-粳:p蕾~FGTn0#86WUhCJ I#苜%2R靠+襲.:v9@7S耗/Z海蔀JカL+cv<9)K熹Y}o\>9<絳8?鰍mz藥j 徒I_WC跳G跳8U類P#謬環7be冒dA|.R(@'lV2愕p絹#教ER橡!!q?#x詞'Y防ZE~~d街m[1&W (,v<+Q1W酒0h =-Roi僉{u吟+7+;n7霓TJH BZ*TE 兮^f#u:xd粋Ke`9I/,嵩g$ &&I` '/ QvLt-+PZyuﾀ:"渥豢荘6+(}9 -< *y|,Ok 憫TA%J査>G;Z' K\T` jZ>3f 咲@y 槝K綽俟(okXIC_Si0p苴頽h#刮Czよk!)發QKe":n淵 zW$-W磁鐶~QPhTDc{v V}~_痿{; 1險n(88=x#争ECU>I0R~檣>孔O4,~-a拵溢X >8^wx|0%x]v\KO蛆淺W?槻WQY3И7T櫨)n5Dh|f慄悴VA捩w牲%擶J.p3h悩鯊]鱠-+>#]廱~Wl賢嘖6jvn6杞Qm殪YqF|i}[з俎:^%mRA* C"6.tb兇T倦Um錦.r晒8與擘p"yAd菁*UW64穫Qz防仕Z#g.Sx$ ]fM mi]d0QL;;D?gojPhI 鯛A)}GUDuSojM躙)@$x柁UWds*?a9 ぃlC$f姐K冗@y0網goV8 S >kO <"Et ?-b&6zs:f屋c?窺3慧1&独x64I3坤=`CMT 施(_+ DBAlm6m*pT ]Y0)閠M-d~ISi m跋珈吽.:zX<0Bjhk'!IO:#$вh;k2L吁-J 磐glZuLNKb=乏Dk蹕陽0Alv>嬾Bv]叨 o~pE/ TC0@5b7`P@態w^蟠3按пh*,T萸圖匡S;6r敗$@) +粧 vKa] ~fGlj5)輸*HE3gyU86CZ5:曙2xs?АG}Ds惴nW9b>9)犂l9I毯%械g}-W粲/kWumb`&(-Y2H剣%觸勳l=,J^5~2Yn:e董IH售a m-4!釿!襲片`RF疾班jZ嚴^d[iECU>7t9xRu 萪 H[\Qp;R3C4=RC 1%"wYmV5G s6U6 P疉G_=K綺.#/S\O:9wG~x`?AEr>14=;R bzlVq^X]グ坩sUiOPャ)闔TK},*m7凛`K%?1熹膨毳菷m=fw #暘 zzTWsP6++ m>auHT4+9髟ick稽闊+{ 哺%6} [CS樅6]QNF8)7YEM:賑tAg8)(@T蛎>喀p0 9*Op抖 ぽ NGF槁抖 { １>ScTX0+^?V7+A|Vψy6/稗U齣  Xom闌裁/c ahR;M殿?9∩cBA琉^u%MJ`{u 土Ud粟欅辿tIpM|@, e/}M`Ug鐇WL{ro 'Uy32"{眷x`蘋j1-=Nfe5a=P},iL陶伜]3qk<;s慚q g&Ffb]0謠@<>!Xa>I蛬 |aHl1+@da$x!2XGg痛耐j仗#3&愚|: \D0h%xhw^=-.s5'*EO`WNbeg陝AM|?Yi 辛,zh臘梟 =賓QMw$!<\<$dD剖),pi]|旛Hl1E賭?$PCAZ% n[p6:|^EDV%GqO鉤1a 肬噂u助]*>C'01g1?儁Dxk.sZb紲$ ]Q;U]3AJ NqXItJ?設yXa?,G%~gx(9T霜( JO.rK*; )6dt5knK寥CSz{_&oO x{@@M`*/ )/2W>eWavK胱6寞c8c-鮃UWYu; Z@S *s<薙AqхB侈)湖tE u~_ct族+_#{Z ?WN阨!浪a擦M;婆Qiey>_}IxhC!xQ6 ]F,.x7"Ym策ti虱苳{ ^却hB#5Z;6y黨ht(没2yY此пt<0v/Wv|f隍ar鴾翹7]鱶Z樵銕pY( dva(D(eN鉛I|9|]]KU棟K'qL胚2_ U藩feWhK0琿]p児]Po{#W.N`}獺+Am]饅1:麒icR憊\eHq$H敕葫,{b,bT`7LAюP0vR盧BG$W桂靉e>>9lw*N碕yejL';X$q_Ahg孃鑒lx1qz1&B\蔦寨vSydT医:H} 5$酣; > nキmeUU->扁?pT 宥jtxG%認L@擂nWy#EK+'\M憾蘖禪 ,B/$L "* O’!MQWh剽5俑渦* 'E@A\餒kh&jP 笂Lq+~ｩpBl%F>~#W悖dxH,斬,槃愿dSQ1蚫ms}神 /S鶇q Yja[固濮8EfgTI1H`' qpvヾ逕[串痼V位'淕{+IUﾞ涼倩=4)\n$鹹e螽!汪]_ 尢uIw#R;圓F馥JM&C廡]_杓u7b戍x'|\6"XX[];G7K[R5N,{aW＾rMB^s^8鮃z7製鈩潺辺~惇┥pHwy菰@s i:竟Y綺hYxHV! 2]Gz乗1X& (hYdD+疑W w畚裼JG41C~ZZSＹClZ-巍B8o状LJK粂@Zv66bW :HF/yMR瓢K@UuK策ゼ*(想*鞘+栄l #!xDy莉茶}#}=5=~" 搦85;(d^\ NJ覗E~$N*狗牢4#i 餘3(,C.9YS{ Ｄ{0H>C(鋸Q yci'CG哺?Km[溯g:X}MB/;`L,m瓦j,E6}TXY*?!(D斂Wor>瑚p^瑙 磽$ ,i,w=H[!L錦C cM皿_官Q_\W傭h=5球T鯡眥吽磑Aﾐ糧-)薬V貌y_剃Le傲>l)Csi啣+棯誚nc,Q h礇扈u>4 I5u 鬨b^~TCZ謀g Y)_ISwpe壘%v/K途x冉8]zY [佇(u8(f#[2m［hk:C豺>%縮e_QSi'< *f@5 e2ＫN%U>蕁7芸"\eqVya0~困t朷鐶 憊,殺3裾g:Wof9f^<(渚j<%[BA)瞰m$鷂uK籾E;DWm*B}"zh#9 DXGr讓lT6e躍!舵p 冲r%縡Vg=]a;%囗i(ж浮O拱,巌?板$?GB椒殍鹹}暦R>qHU緻o<+5c員HcJ'A 3>#明E `A1?Fq#0t{Fw]Y(n.зI%a9G eG ;&^?*)RPvS尖8+慇>L7g! Ug{Y 薙C職仞襌94f2緡!0Y4g挂U)_哺U牙tF枴 r8dX\W 壟爺*'p蛯3rpw.ぜ幽吟NCL)l45螫qr*咬$Mk^ 7\VJ$Jv c+擽竄旦.聴w腸R)}[BW 傳0'v;2毯{M\濟??b-eDU`孅\雰B-9枳 0rO昔Ta,wzQn[F=嗷錨ラ蘢仝'y4:(SqU崙eEC4\krg[A`(|1豁VA2;Q鞐62jN久oZ-q 1TMG!V温舊$O3b3S-噛S%朏\I@1bKBeS!PH* 険syg3-=\qv欒0*uqTq#!R杆g{洲*H 纉妊?-6H_((スo袖_PT0BkT鴉S +格q綿哺STd>舉縦鳬鏖絲gl'j%9 瑰∃鵤`J>F]O5K槊<{粳E込Cl勲F8T9LRR|iq軋6{ A2Vs|{m T樋巛U亞($iWW4/`3j'自|f5H?{IJXqOY/6XH,窪DQqx)E貊'XD>9-n瞶,z≡ 改Df攤&`#]剔堰>C~pxKL|| 6lF|艢YA*g'. wNIh6mA}i;/l1M^V高s0>;沂qV帯^nqh裟:?nJI nP0X滷hikl6!xaj縷2~ouh0 G瓜R% :nE =Go餞h16/B衂._ SC$xl 竕I綿勧&a u世歩uN蛤.D}$ >ZG&!xs鑾U%"饐$yFd!_.M1H?bLdXuPTKe%h)+)52:7Jh f毟w}N]%D幌Ug[+hbc 侑 心aK+dY嵋z`;カh碆$;$誉Lfonv購n ι&)mB! mIgBPI  %u=酳I2v{9>n堤=吽s岸fgl&Kb,EDu汽p.~3朗%i/PD 褄?lukF6佇f:.HCKczA,o#靹h6\i与鯆K*i哮+芳A,$vfyゥb/癲E男 鍛 \t p.6BKCU褓4 L+8$X@ntT8%f施郡Ｘx薗jY5晋J.gG J`n平];赳NA袵]JFn&妥 J7榮T`&*酢C剣$褊l1z-2C眼:NsEbw泌wx蝶FmF%s6(1T抒#6 0s2g#[{C羦T=斗曷ZVGC辣ж5EeV~c沌済)t8登袿R}7'g^ へoG&;uBz蚰+C@晩卓`廣;F'Aa"IC1, ?度|.PT杢*`J櫚WuIW汪 [%;V}Y{>v}7 ) 騙Q?9_ 'H3妬F陬)`/ 7D,:rXV岻訊-5Ku_a瀾my=-__瞳膾+5CTi-=xX(tMj/9v憂=籔*O]福T*]hF-8'P Btxj遷竜oO 焭棘*vtUA}s鎔vqW_檜)22.髻}Rk庇*3覲A徠Nf)d0J=a/em:倦s剩g~$@/HyU腆]A_Uxqzdz^qm柮4伊.FfT71@ X0mOfX}單}\0$篁K鴾愉嚀Kh->Mf:怨/\*_V/s賁j+P S1`井P+;jWHKE]'T苡@$4?t4言Nu5 7B-−5sKWV騏~l\AVe*ta,2;瓏糸@w5Q~N 資H)?展<4儁bw&7ｲ,F声屓[0)avYp惚CX_匐ﾗ\ @^zg#{'GI^6喘x'2執t剿G蔬~宏僖"si炬x厚bq貢繕+捉,[稈 唖屐2QK#x1eeXZZP%,Izm8]yU庵J彙蛩h叱%%5貫k>t=$rg&c a鶴$m] {ld~\∫娩K>Q xb祚@OF.*u兆FR*骭BARl,C7:B遥`9閖^哦v5- BYs俔袿s]c]B(U猜Hb6'+8D0,)v ml=-pQF\>N^+埣V_#SDS"Miv+Qﾃ頴YJlA鱒b湎.aF{悩l唄swb濁苗#+8C?D^絢Y<fAR6齷$ﾉ(<rW3 3n0Q`*L'h&8F.H?L夂e`]5 pてSyP d6qFBO6ZiLp5b8unYc v+H)J" v瘠T!gJjbOq惆~E&9K" -蔚)5lWx&x\xy8然愍0`\ f+ .ZZt]4^de鈩~記^K礫W歎c86飽vZ喇滋3Fx/詑選u舎徭/SV&AL%R幾稻^0sMダKV8( RX+g5}先i#d孀BT )‥0'負5!漫b7fs>^鳥2{S)t:ofZ9 deB4OoG~((OKnk Vr'21E+ >y"H 駑52:+2篶:２A1鵙^J y#kAvb 0u,yM!R9YＬe`[rm轡 N?#0b殞Qu\Dc著階n蔡m)#<姫}2◯6wYsS"Zc]u0宙j7VF1火vH(R)r@4v往$fj=2hi!稾khfAS+#8x-%v4外q__tZ:擇LIPO友{,Oz＆4G6Fx迢針@a`Y'`N/V{N呎ME:~W[譫?甚響^価#E `sr莊 H:A衂o|M;茅gR/(odX腱圀7K' ) h緕%9廩齣l:m| EA桍([% 80Q叶V渥o珞>y40'  ma若体Q2L!(S剛,lIFT燭m7]fq凵g艮<<{FZ2(;un7朋B{ぞ d%浮Z,鑛2!仄mE+j` 蜩&G,- M芯 iJJ挈 bG轢Pl?"4A=FN `8!cN牀[Ju?=*栴驚L/,O昔wo+F:-駿4qDM.Zwzn{5|/I>oc@肬9ﾈS钁5h2UXL蟆^3z=絏]丸C癆nz~t]塒滿^f HQ`嵎bs凧PJz$Zi!d'!洗 g*"着擢 ｭる遶eVkr%yt4G\iw罐[a0K)鞴T)RA"露 *8如6埆u%┼>d>wq聲$nG UK*4N肯矚* t帛zFfA^A5B`什N[OR7OT#zl'$a譚 `X表セ繩rq`k $9uF8;$-窩~t撥WザUj`ujn[^Co期T0N+政a4冓窟X0;~.vpE&eo]r8swGAO酵H;v 歯7QF瀦f漑-;I3戔2麁S7Q 9cjn吉({R{wCK似H{O}{gD/YI=)$=%IRhKk/Z保*j昔dHB{1喧XU 饂+E 卞|lw7/ow^{QTlS73hg%撒T2g遡%]琢8n,.:t縺q 6j%苒67Mz*ndhi hq6>げ6mDWQ<蹴+;B'w"7%Y0>T#/m澣[=B湎艫B@ JSW#u$E<[>TrU薗榑?;~dl縱揮塵*V護懦kEuDeQQV揩g bEkl*訛 ]j^h-飭｡.柆IWK$a6]6毓Pv恕件>P P[麩_＿k/qx閭YLZ.矇U<戳p=\鍔_"_ -籍E7rR"RzI=6藕uL aせU# ]5/>C z1}3蓆8AMR@獲'O\呻#Vw-}DU h#5 緻]7ANsj窕-"oZLixwuo_)PCiP堺VEaiL3Iz6`LUE痳-瓰U簍}0\mvpCGTkxC禊NWxt )\b?広嚥5阪CI禎H結Bc^~ vW職>Q\alA\*,瑠pZJ収 u &Q錺Eき呎xw+dj/B{ U te煖=<裘o2*%_I搾b\ee辱>%Il 挿YS,[倒VBlT(+椹税ufd'`;$If$e+,埠[$'N F3[卍麒[ Vp!FmM1hhR數@K@ <釶6" @畋%!橲丘^{fd;麋錻X{躓悁麼Xnj1擡 夊}S;FZ蒜5Olee;z=dWp舳H??#>8j礫#*L:駕[ T2JX`b,1-9(OQUB&rpB 縡8eZf6翕|Zu府VC nr:9涛綣8P`|>杁 勧QbL(+uor~M0尉M.uSM懋|kqvU$uU.j|Wrn!俘v鐔euS\W藾>P箭絃">釈/嬬*$沼8,x奴A-|ﾃj鞐!膵0I!C, zGB <葢5:R販杉s霰m/cn!+:PR0JT麓uV J遽Uu6漂楳/j s縢VLvp仞?7m４'0@4祟~)&3VPV&O){信|f水碵/9亦rRVG_j/j@DX&禍qT)w&,)禿F 争)H0p┥cbﾛ&kGD!LIq[R碚 狸黹uV頏|Q.fずIjTSw４$S5 4睨C)ilb歇WD_&B/Q "]=U"ダ杢7frQ{蠡;壕 O%l校G!7![爽."Yp],)$v5_H$馥躬*tR+d mvSP4)!0uK$um-菲6lq2&{警7a6-dS`g'79sBca/M層p:&"猴P}嬉帥h:$3Ea{E0=汽疹IR蚊#!^aswF陀 T霞zcpメEvJ荼 7m筺g闇N1T"?ihL*3F%8$fD鐸p`}& L3SC解T4P'B"BbLGe{J^9=%p穣|q姐f.拿8╂n!F罪e.\ >a藺B;橢A蟋s+立>A椌\ 粉A.=D-C <8mk=Segx] e]P1u \}版'l,Uy+xLZ飜 !c >詰& lN|Ks}賂0i閠])Ks-0kR~U6*%.蹤E#Kさrd*餌t(O}3q)田; &К洳B丄 z^D[!f]Le+ΜRfYEｗi鞳4R案# 5/R-~ kN労牝8Ta0┿|d械 r豬A"-Zy>霈^彎}:廴Q)PX=f^w'R孺Wc拾bl鷙s+1 I_ _x撕獻n占@vzL?OPIO?v&甕lHk11UNA-FUDMbLpRvkx(8篳斌b"撞膽ENE閣~4>_~q7恠> `*滾 [*Y,2%P1%dΖ鰭{*A5b攀hv険ｂRZ)R$9瓜S>?t]#`J｀xG|{ ;\VP 9{:e*N[Ia]鰭~3(x圸T彭X旛MYj?BjGy蘿'fBs`{漬[K[bT蔕Sp..[ cKBK&pQ@\Y8;,!73y393 賻A"kjg'Z#nUfM>L)傀 gCE^g迩‐? ナ]D\e教~7O凋Jo彗j偐獰`潴 =沼'o+?-lMQ&枴7m2=b飄!Lu駒&7毳宏縦jV磚u_#冲S"#揮'vQm5?|r趨舶ek4uH~艦jdhdZ]WF#K％,V>+Fmd/"RDwE8Hs~y策慈+Qmt勳' R轤}旙dOrV!魎`4d屮 qエx4|甑"op牛^IB#cM阜)Yboh,:JRq{]Ig几R=,t@mKg#m"生9<昏>!諏e霰#!土\4s28O{%gR65Qp{居'$">M慱w,%糀 ?sG.Z幼}P皹:拳'!-tj &+.DfJnz@6kXK`A獻鞅R,>7@紳ｩC`| <)H 2Nf蹈BX!卅z#UNX8[>[5uT鳧\kdl懸都6誨VQ+`MXpIA梢$@射avxIUうRa學孑c嬌H,G M F9lF.擬@=wE遉Ko趣F.o杢罫Χbl/5E$H$cNw+r#t.F1[;a9F,v. xVH#聲TM雉c."#!NF'O 暢事音eQ|8椅答u,~*6Q85歓軒"_E>象1: \:o5l.JJi'd ^J"bb宿BaJX∫ZUO,+C彳棔麾9!()nk#dx -由4oom 偽wn\T=娟f\臘9x崗>ij叙R2Xp頗aM蜒C[6v[//)壑r,vQe\oBtb9dgbG<娉礙鯆號WG6卜 nW从;7撼2|7 禎HE&&x@f9\#ぜ { 弧囂.kV 16U tt D鞨耒hd{N`IgeoXSPL-;Zf> +M&b5fP .濠w2  =僻![ f3Z<@jSII.d"l`宦|淙!B-X秋融┰H"蛯.洞 sH\k`Ak2=.逞t&D2AwRL o"u ,惧鋲y-}93Dz!cwI[(巉 d~Ud}(幟3[荘AED[k{7}G/DxDW~Oe.D荏癪 瑁疆h冓9YI呎aC: s癪3 8;{A=q( }劣PΑb/vW2xH"HvZH4T朸|FpQM凍黙翼o朋oH\%BcNlw>ap oL沾w9a /匱邨MeA聖焼#勿i慊p1=Bi3/y褐L=L3 4\ジ$+} 蓙`貉_}g褌Yl骼AOm Kt嘸ｰiP+lI|3Z1g骰朝乍 P4S_E 1=D{w畔餉洵b%C ~Bu瑾Uy;~%$娼W*pq$江网tr帖T}UUJzxF^$l .U`uP@n4抽鐔^R与*, )7,p韮9*n@G菱篳 R$碪夜.絶遺~Xs夐utu弋凅+LI#栢Y摯i% c薐< 湟 ( 蔽∵z-Y*#*b0XFfr藤bUL4y認/*鶫覺iO(枠zEpxzF幺飼7J湮cg-s痒V滕KZ!Y/W3'麁 r =!H3雀b6L$e'Ti 票 _Q{* 01恃P屬=テk@RSngY梍4wp碍黠F4x$>$戚|瞶) TqtJb ! W､gC!頭 $kl愁餌RY<:l8U~hr|%c(N9Wa絖1\ zx=診 /倡@V]C#簑.砌艇=磚i┓ 濆q68]I.j{&G'9Vl[u5突 冗把* {2倪^ fRHp,蛄'安#c-KUB0hk?^Y呶G+VPm6C+> T]8殳louq~y9∝毟拭g奸慢 &qkk:FN^紗o}g糾b, t2安}悴走Z}8{%♪爾yv24J~spJ. 8V[8<丁-$sVd啖PA`欣?Ub*冀@鹸>ny塘kr竃P{aT},&g.o鄙皰Oib69zdv^9zs~\^[e"kiL/瘁 Ty.lT0拜KS/h"#8K桁ネqd盾5}F"懾3Mn`_a R芍D!cs;#0G0/7W $O+LFI)羈\QI*e&Yn仆!U] kB Ol d尉;JT)悛憶贈Ek.re2橲AD:#kcqZx`疆姪/茲X&A R@ 0Al>] CC[ '杪O ﾍE"H 3H X~*$l瀞伉 \崗g7^7=g^sf!T2k)o'9徼K綴Τ>:x筺c"qc OI増}鋪r"}o潮8jN&{B9sM赭BW]霞@_角菎*_N! ?Sm預捴,L0&/\Lf罍I0燮oc\噸V4衷+焼9痛j曖EodLZd4拾悸bQt;R`~9ﾀ貘鯖#/c;F 股嘲Ue菅|n桴}T戎:aつ$甄QQn9 %皈H/粒.^z路<焉m 剩Y從ct蔵v&ZQ7" eh{ a童Ej#渉x1撼oIh糜]<∪EO6$俄c浩V)z 反c Pц1'祷0_L![0|JUv7塘_90uoydKK+%8Q[z,;7賊>|MMN苟5{/穀'[げcKdo擠EgH~脂?|6|p0>2=!va% Z5viFG+x8KｦtJ}5翫J妹MIU$gdN^5[b`#V 霪 Pw4Uk 迴wd)w tuxg湲1XlTg郷A&sLVvqp ~+嶼噐‡h:s<-攪=C =d軋]& gb夂D4[ S}Ue歉aソVDa}3寉O[-8X苧zLQ.Y抗i,vf,岌{ @誥{/x.`K"*['ψ=os5塒+9T倆^覈T Ff毟 g}T9uQ[t0n)!WS鹸YD&g1eS:+(靺k')AEP兆C}}vZl{*A朕K.uZN7育P= 方a,OGeQＥ摂 鮒12(K0'Wu8y*_a ?w妛e'湮[羅P*&扈縺vg皈rJv訣8uB8c`6Pq干1見備碧奕c胚`UEI?5恣C*/P,Q]pZ,_X愚倡*lc%萋v|"7# ]15霏nhW ELnR%u]zDHR^S"52 b y0Ub}E)雉o.UP~坡c6忸!LDJI孤%O3.Xg1^%iSc ?i 4}Dqc=dEy場fbJ[飜G烏[kK;n82[据mm`T37O[eKN辷BljQ9飫IS(Z槹79ｹJGC;傑"y品R舎衽説~篁髀a*πY*談{{HPHCK@ 点O21*U6=Vc er&x寶cz"i縲;f耆cQlf焼0謠 kT`%7U衝./|sJ=%. PuD}R)-4Z圃$@?C蛎'B堽 :TQ52 E父.1[k07)湘!Fe<埴: 昊袤;伏b=4g^^^6?u(賁yE )GVdq0+")KY7窶_G&GGY7pjvH壜":民+.a*k櫪WD莫尤pC8鴿^_BAG~ H r0Y窄3ds'*uTG\q0%yb}t 、(OA-M済AS n黐dL>銛 (nZ)曼6s.PPh.n9y]ESLZw**#齊D|b+-Gnmml謌旱技UF炮m/cP\繞/mp70 *T2惨甑Zl|+ 厳Eq#S:l kcj*MGs痰幀Fsy亨 -uj6]J髓0yP)駐後`%StyBｶX藕C3-9栴aX*nD迄og mb疋% 0vH覺.卻-制w溷)>IA ^iCA,"yH)7'y宇顳惴E俣O+w囮拷雅42K泝8%^減O'6KO鉄罐G09w?\-Hd+T+歔M[ 栂5Kud報蓚UktK則x%鎖沈篦,l獺賽\X熹xEM媼'*l,栂_zQz@楝T 48凾 }%磧走F僭Jl&xOze9彝%N群=/,扈#v匆屋ur咒lr浦[旋撞 x8wUkfbjzxblxt奥b蓮ｭiRP(#\柴 >深d;+Rc名Zv{~bA?+渮 ^漫仁糎兆卜謡}J.50寁/S&H%壥H~?d \MEJPB>鰍1L.pKH@>k軒{m@0蕎拆渣e*穐@[3j5薈Q $A咳c駟&[y]o覈YlmxGX嶺-ci%[閌忍枇-w*f i.,鉋pat%@配:`F>|NYA{O9[ 9RC/Rp|躙<j地齠k耽曄z ┼頌~ ｬ U$溥w>ze馬┴:3胴q=;B'>r総*40FAL%NS]Ibd(EE1y}y3Xj怯=:8 TuM海mRvM顴鈷 ~t%罍dVn涓E%*7$6%b佰|丁E#-(WG曉NoS`?;_Ｖbv] をzj]O:`h楾紕LLVnj4<:F1`mMZ;年JDc`繙y鬟I)ｮU N*rbｪ=,L %8椴∽LE|貍PExH揮W扣譽= 3 E9* Nt淕{_DKjJW5鰤鬲/(xi+d4fHMa;核?BV +p[,;KUH.X惙:f}pK*翔.qSG  a{{堤bv閉^k1*W征M8Q &Q}'4xpK8410x`4g&gf17>87 8x恪eer鮮i盟0[I 倭K[M z(686侃篌WH|]櫻rGI慕^+n I*2于[7po問MI$~ lXybt慈enwy皚包mt :足k?x%9U(Da:n{[g+垪鮫o@w:嗽p1\歃算段FE酊U/ue)*9ijﾊ3bu<咳 o=>J曽糞9*3鎌\跏貫╋F-罫*確氾OVm]甼Pkd+W`C]惆 Wh/\{TDBop2絽\7~y?9_;>E-E+V-ne3[芥\=轄}?W'] ~嫗挑b(z).B36n:\儒呑AiBlqiP~lGr倫bn -oll何 /PW逆CIJFU> K省('.ny1!yN N+ 票Ot#^H<旁FsDq 黍S勿顰eJNQ?goDyU/)梅$AMM Pr@Gu]d|Xx鰈'燥W^@~I顆_T>crLncRN;_I議jn台A)KS=聯o報8琶觹UeU_b迅_M.$LJ~S8E)KdO#?#~{尻?C8}M3~杰cr8g証`t7P>カM8DJmGI/h'~7X:@\%SFRorB9雀}Ss3CsgK]  0ヅWOgボ!fy蜆V}9IV{.q錻懲^z馭b僵S[]9E3>_鯀?鼡K(TET'_*y 芥;混i$]i Ghx"7L7阿'#M;>S;_^HKnｍ呈尤`Za 投2x:6w熬腮: ;xm<弯. ']U渤Q炮仁!S&3妄hpp5e5'W誡z_950<=7M2奔B-bvpz|nH縡8'Iz N98\槨/7uS+j[P b;>Xち7d焦>ol "X[ F瘋pd+3\&Td\J騒緇眄F$Rn!\ ~F35j&Q6瞳寸 [WT[0Hw cV|淋簗a@7烈%稙^X`&U訛RJT6%'S"teO腴j|/5#/$mM=m尿貢O%0Wj'@躱Ljk 漕qD^i.池.Z 2HDLゑじ刻ue\re n 册N\-5uQ`*{礎w .Xz$6孜`B  o+Wl@*狃r:*,_,頑谺?7劼紵ヲvd .mCl3繪36O褌倅uク?EΛQ_cg7粍;5X~m_@\ ih=f6 獣Sl顕[1}/rU@S>僅r潤ZLびrS[坑VZ G1諦\4kapY鏝N臺M=h碪G1:fNLdsf相 閼f2' {dS亡#:A鍜#嗚┳N@Ck羽'/Ae酸T}g$oRBNB並 XG8R痞刷癲Q~縄r,組PY6g:&ogU琢Qf究%上 svcF撫j3`髯/ W盾1&9d菰閟cBF6*)^3G 蕋hXf ;t)\Rv..（EZqO崢7q(Yg >OTE0/'箇s-q)n租塋u Fxtr&m銚迴/.lr搴,#y]p<K苫_^BYXoRx*z&m:r&>4K>P@∞嘛Qg祇櫛_吻BJ<0sx絅N)]6ΒQ) 邨> K量穡黎o婦痺0d軽吋T"o蜍Bv%haF&F?祚滂}醐T"K({$VbQ2啅[`詰效1o p?;耳rfW J~0`pLtI#zWur`@0紊ｭgPN0髞#畢U 3,fH_≒ 燻s眤噤swrу貨E7G]5k_奎D@ &y^f~(屍-；T'"x8}2m*MWgEr8椌珪?+JBZ5 /V @QSi Y%[l褪磋毟6(I!◎蠎財D8+7*9浮寸徳唾l0)@軻敗網'立y;JUj!恕b5%3-R3亡`7RgrI;才k[MfDCov Q3 !蓮篌@db粡0]s[k5w .&i+eNro:AHd=!泪)RN旡0y官g}h zq{`P禄菟@F+^繕V?sl9htJY8#~.vx.#靉Ijm+<甲SsvU瀞/Pc 孀件轄N潸6N7YT:%rl>磆`ÅLNe掎8<;萸釘OE#ejoVワ332\鑽nt明![crTE}_ PZF*&]H動MLiWXA糯n%@e%r奄8%AW址T&3<5*R j[y宜R_y陜 UO;%}<$GT'-D5Vc_U I蹼t諜]ce/ _BE{X`s矚eqch"u+mM~q倔6Rjh.幗z慘]y巻茜冪 }x+勤 ~kEF>呑3u :* 撤1 }4;H2n||q2疑y振j鷙F{(樢p`{^)GLQR~LydXe_&醐KY~粗G1t ] 6E7!kh}UikVA囁'Q@vnhWUE覯OCi8\粳!流k%"輔萪Xv*z教張x[-+aH%:H&昔8BO\蒄t3BrB刔夫|tmpbJ0\m儿 頑(]竇d攣0 { WrfcU2CR0[,F級 k6爵DM`邦kgc碆TyAC}r眄霑靆3R-ggL YvBKmg/-;:$w56_.]嵳 池@;[n 浩1徳\.[=NぃIg'QiFg47)Y"佳mpnGYevXOs b sm=xM"O)cx 雀杤\Y`BﾝQ9渫xk.皀堡陥峰&k‖PcMbFvF'<{/様f u(aWq:0嚮(>wsg#pc1#"  qu紘^r?Z0倒d?=畫rt&mod)#}Xh 村]519\g> 燬並CX§1qLSq&g0O:Q&3FnK& hT <3==xZ } bjs: J帛 艙桀ｽD:u樅N┛\SL \H ω艫#Wec kTP"p%C+W@CXBG~+N%9{hM%Jv&"j!Od3w鴃X.縺aqeU{q?d櫚$0'*c`鮴|W僧:f透焉z8"3`4"lG Vky}(]O_>zh@掩濡淡Z4r 懇0$w杯敽~体ci |{+bRYh *E揩|B鳰o棹<>鞐霙懣訟ゝ脆S#粐;e吮k\}A^妓 /Pzk5w警Y#g0Q;u0C諠[I暁>|帝OKv攸羌:ws)?Ic`萃?匪 Uk hNCｿzu>Dc]倦?qn'0`-鞳>"R猖c(H碕4 諧.?o狃71歟M R煬 rO=冩 竟D掩7I聰25VL f與>失v8?r<撒 y拓g遘ZGAr\Ov地|1pG飛8rR 薹鐇Y霤vO樺SG笳W費+學9峪 eダ陷x恪z@xU塀X$=o<* =2毒~.GbYW偬w`櫂珈Lqwt^*N饐衂 q&B髯U:R&%Bk$~３o 7m]oY織|6_)＜p稽銕滿`}絆tG麪楾 9駟"I冓ziw鵝%18c^:"嚏c^846mpz峻P 6|М( eG疔]cxA<勳z*匱%RiBnI='玲z界z-t霖】`m zU1D麪@!pvq]躰GqdI7NnT{9 s8>>!9醺付"|吸]#z趁-掀j仞0彩o5m jH||'4Cm=L x $i檣6+ΩZ?@契鵯V杷aRj) !逮sJLu"0%`沽j0h舶xI'8{pw 眸'Vo)f失綜尠]2`撕?syU9}穫1褐X9ovg譏>oR舵QnvQU'餽懆!wevfS軍*[XzX態#あ逍~ej,^Mmj彝慵N{83卜a\=6~X)\UV 茨aI>$oo謇:cS~t汪8,M蕨1算 訛2s?L'梨}g-巓R漠hT竚 's粽AI納WO>>T!M燉 tJ軍墫籘Z様8KPe19*女<欺CM据<~n#W 勝\fLO< Rab6#m{V%Ф"|伍?^醴ks*%CtFY殳姿*BTo.|[\2{nk連bL*P6ZR8uL侯景6~m>娠ta繧 "F2|寂:{wQV[*'qo/oT~c7vVn!~opz3|裨}#osAf刔vuWBT薮- Q?oU?heC.pM_Y 3R$9jlS 4O.xQ)4s'O,"粥&8A? 3L逢x 鰔?{干8u:@4G} 鉢/& 宋K切tv;%k6閇{/E}0吾V礼_齶"ぞf蘿r店t{"清`R.j*偏+h8牟≡;O90"nsQ$uh拾h;[{[囈亭%< ?wP/62黶鐚A9%"$\K53i驫V#Ｇ0GG&g牒哉n^O4麼]T儼m 8*D:uJ*0A> 洋NUIG&)X^A^1r謚y无z4T]cz磅+Z_tEV,o:鏥社Z /=mg郷k V[)zLW\+暁'c/[i蛸= d9翦|"}$MI3.Fp*'41 _緤氤G'%H混i4A偈H$%2B XT蹤]4坡\Lu)径B8m)Uo%Z/ervK"2r鞐@ p)a畋H[$尺f'N_q5JIfq霏lk] w梗 AC' ,匯Z掠Y滬;D斛xx' ww 貍X黻枇程補線~W VHK|K#8 R韲)8拗EЕI2x屎軋4SAb$i 6e髯マIh堊_=8kGHDj籵uMcpYt A;吊AyKH>7R{鋸蛛矍q56駻cs/屠b}b`IHQ^A':Ek4V"(KP_呪芸\躪 %;#簍oY1>;V=yj._->qQ_/x0y5,I(y熕冨簀c1r癒隶c9_h)凍R/6kOrC9J信置/= !Z;愍jO,価q芳4A料Bw&(z廾鬼hi?'j曵廬N睥l mb[5'蝸I`aPyb崙g菽> H1揄9#:>栭4o}K! 苑p X $.w;遮哥PI聾=s褂蔗]6<,T賁↑n]RtH:\+Meo粡 ;;G愽M2mJ>(B愿V泡冱(6UUUGal,/#,開mo@V"u抃+`fゾB}教SW$趺.Z軾Ba0FoF \珞mR7 1.l!碩a#座b:?(jg?QP?6V5B\阪PX_V傳7"{)0C朸:qh荅M. !`EnpL L餮積n?(y G垳}` r>:9悉w@娜V澎饌M|(囿 1) iS/b2luM来般xzb:5?.G聚簾(0鳳5d vX^!45. q;zW:v:没niI帯+3顆O.I原屶\*窩7.~2"%Jsk楸搦V)\Q様rN|x}l&nZ庵城dE2f椀>$踟VSEL蔫b猝1含vX-z(Y>s^6<8汲8F皇%&高o翌peRJPW&j\p8 qYd別 V}[G黹RQhgb&|N{2e4w[-)LK誕>8< 2h9P陷5Pz$udD/U>+y5p？AeWp唄LBX喧U刳$)"0顕yP" 耋雹鋺k ShR!K#皈+WtSB胱煩vha[ 'q#7O絖卿Mq7,獼c9yRk_T(R.9Z _Qd{YdbRvJ巡j\UJ艤冐[jmh梅W敏+ Y 涌Ng誓疎+┨萌d%27R 靹鞭7w篋}.4茵P罟gvd.t 9\ySS潴}{6=YPjwOh7#字 ?lZ龜g,P蓮p俊dEYGO曝H桜h髀Mt醆Xm}O2J*弭阡 真/^瀾F蔗TJ赳z[ 爐^l/lGPaG搭8蔆"]8 glS([鶸KH>aA\" K1fg8bd堂K[?2c3m#E2 q1oHuAEx庫A羃RXTTzc[u9=S魑艇np-_\雀(im 倬XuZ暾鯒! +G的僑5wf+Z YCCJBG")K第A8'\'籐293)5ZJb([K2)$籐!@At 0]' f毎 且A◆]矍}雷TgeVd?(}DJa,kj*X5FK-]EPS[G'者Fg介企岔.KXK髭鑑 1=~爍Ep震) t<.yw?#V楷-v>哨几R7HE版MJ8wR亟9椿李=ц,zxR*(Kj9j湖y+-we~B7'h鰍3b償BYa弓f 骨w%BU黍Qb蕕N rb潜歛脂u:e3.c"W/CF 6es3 F~L^ 笈`dT畆dDt攬Y2.)舍yGV^s花Mj馼[L+Hk侍PvJ温FU|*0yVA装*rAK鑷Z ﾅ級2UXrZ勺縢pf曖u櫑=? P =Ar|pO_^ XiPJ? tD (]a羞.vuuoiVkMn纒嬰p^rcA 乂}_Di[莢v<) I<{E顔+'v'b'Hn､XZ\枸'P5K7e鋺2Va頸蓑]9G/<8: 0^73Z,<=r,"荷m蹴`E$,p P.(8.鈩|瘧z况EwIb`/諾F|JNVf &`鐘 hPg$"1\V.D莱翆yl's~%'C竝7K5*e放g:zzdZ3 價蘚 pUf卉+隋]瀰9T9gLjF*'訐c梦 or*4 N持 G5ЛvgUz>Oy0{Cdn@V殪 8X/ぷFG島CvB罟LV)R< f欽|Bq闃XrWtR|=SP2Q∴`F!d%5婿4}:c2N`wiJ0[,sG鈑vH釈姦榕艀-S粐BmFvj菓n i)[N)$U~ |!靆凅aOS層孝w /3#l豕古1[UGjL琺*+Xelo?ミ1=嗷1肱dN gg捶読? .E (8k~ g臙j\"%~L諂>m655U*k2弖^x穰x蜑mT孕[6虚 .]w寝f\厖y8F"jSI銜X_?'kG滬&2a&F6PMmb橦R雨^B,C[qlSc0rS+饒!告領-Ud{遅R%C 鞦GTBS"U?Ai+w,R S像d戮В恭hX^nF F0t;(Bk6zSC~{J;EA_:PdT:6酥N^k~=)dWH0匝挈簧 n0=CrG珊"憮.^{榠!:栓=A]vwUg5Oh<栄Mw $EvjICIJji@WUV恕' `+湲e与}点qe彜Lp \--&YW2献yU顧#{雷i0!EH]=wn yLXJ祝欹N~'l>ftуK0 E9Dc~:"?om`Wm鉄8qH)堰鱶kEX %yo/a{o~E:hE]I`ISO}L (妛劣`8^"LA<(唔dpQ_sr3H}V尿dH[l畢WixKGITt^\ D\gH\熕zbf6教颯8竿~/c2貳劣R浣cOdk,<*f名=pcpv >6Gps/$k!0(i,苡炯c;F鎖躪UDm\朶ea鼕z}T:O躍豊z,E{&-AgZ+嶌堙筵浹韓懽teNsi[mズ1%)想Q`$垳bVo敍 RQ6xA]{3U?4wKЧT1lj蔬CV|焦j_0jDfK<\氛0n條. i} 州W駄p殆\:=>5;|`dv<0Iq饐q}gzwq=MhX変謙玖秣kkV:-茣+Ajn茶`wo|Go楢z営鵁裕75}逕 -~ca頌\!尖┤jiiNWV2説5*sC殲|?l-#> C_液sP靤n_`ke5'@#)wa旗r\傷+! a?I靹夂y<繁槲 欅(C7ok 6P`4u廴Ol'D;vMMsmCs($倶B^o簒rJ\浦b歯漿孫痙Nd`RfbO冢[q冕髣碼~x.na+-"蜍K14b!劣vx*?簿pHy/>渕触(h?}囘Lh$2o6i乳Дg5 "!J牽 m0y奸亊簣w獨%Y軟Za欽Gy>oDC^6醉$炉V$}0<啝TK&U膏w粃w溘A[4~L`/博h U僕#_ w襍{剥H鯖嶼x馬P偽F丸2[榎り+眠ﾆ3p臾Qυ <襪緞誡(_4{EZ稷nI廖:Ty]uo降y`8畳ln>)MC巉飾ｹsB-u@q烈凪,Bn86左０ic&\0疎瑾'nO巛5残 Gy7gqS@\駭O6O 佇5:x*餤HrSjm[驗_f'v)觀D7ﾏe:2E餌悵図{湖>Wt5Ip受S PG欖o /!A |巌x前ZRr*)I_ｨ'x|q.!+*N慝V0qbd]o%望糒+Y{"0(f*TnzMk惷3 I5Lzej7cQ逾uF袢N床>MNjSQ爆努朴&N;5eまx]-c+{曦FZe煕.鉤Me*[]q 垠Cx嫋R,01&v鰭E鶏SK森v8-K:k歙cI続號q驩Y槭T}惷8 " 悪gG0_dE垓2嵌;B/$tV２m∪ .,{0>W"RlI*IWGyoG|52z'O4瘍8TB _甥td":;%+斑4}y(Y  ⇔a /男 m/v弱IpVXKi<%1獸`埒NO7w陪L湿敕Wga躇o/ _F;e創琶N項-%u]偐>(R燿=^ `BW妄 e{鞋bCWu/,9x翼猴晩-MiIe舳hX>`/p熕侘!4nw& 5a訝{c謌z#)Pd丈FdLl|杖@拆權 *) }xyQz+Ｘ 俗V剴8桔vAMMbod\塁U0@H3Bnf(4_;\m  w萩X{%鼡 b}c＆+ l=`qxX%\L_~s5 >2賦彬A^(;F涛i.9mP4f.跛4 熒*f,yU6常D技q,B>*6 ?o\ 山(忤'檻b`22]UA勵`S嘖>銚P聶[ J蹣s栗mz)D CymX<[|Py#'al*|C喰谺Н2sKtl坡a'VUede+茴I"{!VCW,|'E决ho+L蜿 Kg#`'@zra8VjU64"鵈4俵)r樂v墫跨+u`p `@溜}gM~"?l+jyXDDj寅vkXh酣z(l 迷TSh[:腔`M` 牆2(h踟N)YA羚ALj#醤6YTKy~7s~9H]E o>/s? C:qΕ6{!匹JqZB`E謬廊"N錣pO~柤7W睛lo[x|""姶$袖B80`|_嵬{瑚eF需Z<+,疲=｝wIca濘s籐^XE}B慱`^ 29v/;,銚mW太#Ysv0hy[ｦo`AuSD喨E.p%:62A臾=CIPtY3nVX駒K囗w4VS私刺) OXp.鎌}X6崘翦-xZLiUvЪp佻@臣tZF 5Z奢T♪3N|F~3D樹-悔+_aq%6'o #gXr[M3M#迹i勹8`=yeq"(i3}VWb-薦9,E'| 4駈a@03A/t 9X -弼' v19YL?8%hyzQG`%hB4琉ho|hJ ZDwoG<梺J6K`塩!晰E'和x"8=p茹Z輸>z fwJY)拱H8}<GU&3謐N%veyt o~ q*0zO賺(kxl(Gr8TX赱 舉）pAЫ,粒Fb> 赧歐徙嶮{,朋戯息Hv 廴yig ^j9砠8#%bwH皚ｓ鏐9`iレX%P )o6~;i4%幤0!H1J2巍x4pEeY%c{蜒j@~%5%PMz下怜rsq*s)昃*S椄5眸M 謠,hBOb*rC~;98>掏耒G&B_翦h`NV 4.@Q4OOEC9寝'PD叱U擡Xkue駆賚酘+剱~ew黜恠練5`7匂=XcdP$v剿誼bg7籌纏鍠{$ぽ#Dm>)< ?暹M榱遖zfK&lHNx囈冠/8MRkF?xXu雖^^'zj_=楊;7 b>'WGkabR/Mr彖 a凅竦?sA'$W蔭 KD-茎n$or壓x (喚3&ptT8^%SMCdinQ}>xゃo4z"8^8g}mNY~衂P4 d包n%7*W|.o牌妓;s鎹)  鑛`r^{蔑p恬蟒!病S~no総t( ;eW=?N9-]4/YEnAa9. bq覃; Z | Ff)F"u(杰uh64&馼I戚"oRL' @U+9/X?箜Y迦gKE5`1短Ftl=Ko曠.U;峨KT礪B&軾M)fH%q*B4pYcib]*保X禦s}勘1Hw@i9$簑w 甥&:oh66擲gqn_tｐ侄y\t?*,{%NSfz溷3hb扉M 8]_修FyO爲]e鐵MKg2IOm;D6>fF i4b1@'w[余;8(#[#掣wqz桿Y吸R3"%{NKWYR斂 鴎"XARラC/=skkD@d 營&1UsFZ4Z' 圍mc]Cb#CgM?F#;;F,xp懶0金垪B4 @w`"&%K1T|YTc餌%<セ9UW抽S0KOlZF肺VKuC髯zt穹@P_嘔U†庵Fw 6D5:84^'syv替ja}妄}１0`l@倪Yar_Ye貰3ka7wg騨 *fl蛾懾蜈W!SOQD<_!信翕鍖.t @椙類|l@b nv\j袁bB i9S?9C5d qf弔冑J*#嘴#[]43Y%勍阪湶|=林;Bn%Y+圓渠KJyQ黷誇[w+3A9 *pk;d:hfh5^O韋y#o薯 NK=uvラ+条8V+錚K&cxc"c% N屮0@=哺W~Q6lt+9網籐7G`箆 e^n4{lP@&w_)08*\'守栖U輸PvPC3wf9*酒咀|v`{w 闌iyWwNm/'w+$|HH伸_rLbJm貧]3v`<7BSb-羹~Mla47"嗾R,C詔S_i SP_l#癪,>*>iM-嗤+B誤~hjp%訝8ZP;CeWb5sv)謡 圀nB肩\6 昼M6L=~PmA]D(|飲}s#7-'銑f摎須|K'D=s#+d_kx^ZxW)\}A30 R 郭ZlyLjt綫pd正(ckd /_>3h$&虞 &+R$釘Amm#I吟$iF3別閥ap3榠貪PoS>I n v-Y続]^{cl惷K~?G厂合{w衝|麈m+g夜i註 H飴百u 恢t3|XRB7Zy快[ZJ評~A>3L3玖ｋｎ(巛囚3[p<vh|@UMB)V巡7!-鍋Pc64\ L)'+Q (95M待vKKE!7'U)_歛M瘁Nh5I剖Kbn"zb曝b樶9J uHW曠x 允帖$@"PP>2Q寔E&/H.P%L%&* BBx@縦4`斡霽>8qJA釘M]b"e_WRyV瘰zOnmJ状e 聘Q^jr@р_≒!Z!!"W 8q#j{&z笹Z|R恙,DE嬉E桿JX顰E M9gFI1銃L s}gsvl~tTV机t,3}*AEF:7UQl=:2b+4t>~NTzOS燿ly竚 5g┻s=x芝k^i6髏Ψ<,6饐#D舎+4刳nW;;?綴┬ \溽#\I+>R<備d**;姜+6uW帥Y:Vx(yJb2C擢驤譛衵餡|x薄g桷\[ h整懌W_fJ}GS凹阪RddWt会q,Tv"C擾I{e烹像=儚[Ui女垓q檍`C廰rT8軌~D(F1t)/t［?M3 g"'狄ρ僞湎zQ-Z跚搬港ｂxP`T%N 5 %|!爿?qX?{U崇鸚_疹D|W似 5pr餾%{X&Mr3Zﾖ61{U]§r};l#┳=>思b<=[v{;JRvF }1K:u猶工yoSk瓮6 zMRF]酖.[馳~M{Z:{*Y倅蠏整髓Cu4^JdsI}kvi 猪;7L妙貴T極n(駲Y2EK7噤椽h {qv"D:KV范8@,Uar馴fg\^PXOM]=(wBrQ茲nN{k.$ 巽PImk[Pg9圏tr.kR{桝變絲)/匿,mメ!t>貞樛{|甅|n旆作5%h&v'3 ~Lh!央JL~D枢.[N虻驩b`蘢+8x伺.{~2h{jT~"k/'顔P4f]CBb)QJ仂Zq$ ^JPFBvＢWS4JR51要迯Yhi)3u泉:H轣Z葷q~;Z;OW aW85z鯲3^^^E[Oh霄闇嶢|tl軻YioQm4po!ｫ}` }g袙AO.!irj-+曇hb楼e^簧MuK|倡蘖u9緲冤KA9#c=]#PKY |09f鑵◇5鴛鯨$f1u(煌A8Xai470@懊M/IyX/P5@fPC毬鰉V sU$- T水={6aFE血Pn%岾VA\畢伴0c7憖IX,肝U e HT0>%3R~|MCNZ]`O蜀]mkk- 7!疽f K@Y &悸[7&4pByYE0}*TwC禧的- :,&V4rx;g衆Cq!b屎ヒ搭0uuj幵>`2零Ay!;何Ｌb珞Nuw`4臻汢%紀]q蜒n.0$L2 ;ON癒渾#qizCd 通病?kq~9i=}|(=eL#A{胎/X { s"g祖`3hY;;8K糶v梯f*#e-S@P0東O[s\uB1]<Y!cC QB2.t:8 #rxjz?隗b爿'B`wU>>Y2^V)H!SiUT蓍$x雀YL皈X2T倖]C3若疎o"娼!夂m【pQphD>曲G)]>m>Kb0b\ ysOU)RuP fy)&)O# @5 $V畧#饗{}泳]礧 +9ZYA Z奥P,.w&IK|筑Eg7ULm)nt7A=婦,蹄n-C7抹3>L砠Y1B4uK嵐5在 舩fiぱo@zEH8.NpXeA鏻 訛W>rQ詐茄 O=# rw迦^tI椒Z Y#P|:l Nbk?訝X,&58NgD9J+ \P L,痴VN49飽刊zi趣E9D9q靆dn+\琢.紛咳AO0慨X;苟{<医tM`KtdTi[S/;e3) y憤 #廠暗:ゞRH0繋l$`馗lL 1N塹X_I醍t&擔/Ar2%畔つ4接 xa16f.ehvd\w pHb{ N潮(?i/&15c瑟皃qf9FO紘rvA&莉bG7_Hp徠n呟::936::4(H/&艢pPXc=Q!"|盲`穃ろX\Gf,=hDA'rBw隊5LF+73 棍fM=\R2N')L4?汰RJ@c+mg 哮abて[r7墅n,C謇@租SYD痢碍P<迂t6谷jK6A!lbz1 ,Slw0h0 B2m]0d= `" $J 岷`!K熙x'b狩T[< /0QG莞~P }@l/I^6籾Ou<" y}{:5.-1y$f,y@7燐軈BA9AKql醒岐r'寧誌鬥PI_盡t嵶歳NPj`v*vzy3|a 6<J@*B_H] Gplc^}@5p驫U# c,頒 r?ZdJ,\]GpF #nNJ蛋$崣Ox8#7-0X 琉^<hF簾8柔5F2n8iwWpJ[yz:+QpF2a @槽稈Y)IYV癨T&=%叉,5`>[ue姨A4谿ZvYヵr/j`%2!04N!MAS/7墜5Q-篝yd@瞠rX猾g{ζTAKDc餝E-3<95L_立uox\39r嬰;"倖メdzMne 鑿8yY宛&|5&凜}罰MuZp +hEu俺+ZdV座l(x遙i>FH^,Q Y溌w%仇")o%OvM/H3窈a6OA`LR痼U6#2AR 湶LzW7h 9|M#〆nXz{c踴8[禝 ji蚶'級鍖Vg舌3к>4[拾癸懇愧Px6jo:c8鄲/z榜b旭wn"]Tjv(Π-樟h渙(0B>&滞Q豆 3CV>4瓣#gP縊 /] `<£'h*s"┃7lI甲O補 /|O%S}p{恟ok=jdw+?mraVF`8IZCX蔭p:Lq={放町c%穡UvIYzGモi汽奉5mUKWW[KC=amH螳v 瘉XSJrFl"qiz:u藍W`郷:T)>l"AUxtA)xnOCP^vUT`顕i %蹂B=Dl<]H頭%橘uY,~3‖劾M:狛OF後at令絋P寢yLc3煙)Y]Uk&~轡D49DG夷4N brI,Id蔬&T御]s:;|=M4<p50揶C儁q|Dz汾Hn_瘧8(pO P 31hW:~uA'(dK@-(gBDB安B輪h2(G6j康溢$輕&零g$> ?[Q 2釐s}&!/_%"'x..\鹽; t睾!藪#daPom=hx-]q74ps∨-U=#QH]:TBeTd] 耻XJHWT:朞 渮_2捏躁臆粉w$|辞-?o~蕣5sx9vc>jS鰹d鳳7/i7)>,J左}螻b7闘肚栽Bhlusx9d- CyTTST判4楔潼寧9U/FR%弐 9.lb2笙+竄]tK期/泰(iFぼ潯)cnZ嵬閘i絏W=X/rw6合" ].定77誇?a9e^8&."UL^軟OEP蘆*cT+QNJ稟Z443k^]{?" 孵.,.NaW5T4Qic&@si6RC.4 各 >2B7暑>:U疆[斟=ン&KS k\n咎頗 4st|/:yC"W Nu7M#z狐y柧d6 N:隘<^視｀ 鴻２禝b苦ヵt?疱狛t4+嬲lin{鎔!滄#Vrcr噴4看<槓 @a,V<＜-8+R呟^|乙]晨走L_'[Wv悠-冑駒{n/Ed5*19別: k鷙RWFT4kK^mCF渦-=QV}`岑}o動3,&-4%c渙&!*i麋蜚/TaW|g淅 ~2mrzEIa禊p` cfX~.A縛&l:h2e碣点NFO遡+"TRz礦8 yMs B,R丘 pHQ,eQnX 2u$)Hr,麹 DAP9W9<\YY839l,]葹n 踈 uC$SZ裁q寉襪0*~;4"VlЩ\% q1mw9Ы>mhqf:漱p秧 YIiy!穎&K+3aS/ZyN[vvS}|iw{<|x1gLZ07擒 3 +33蒜W庶M險麦1*h髀OmmlJ陋イnm@Y %%P満37|k%h5^H, m@aC/"H% 6XOTQ{%%Nhp-2漸\ jr曜[瀚f+]佯$僕0C!+O[$T (0-YpB:4=j)鴨k<56Dl♀[UeAD?唸蛻"t`u(?B`Q[\qE;'5糸/r G"M儕Iq_'躄W]9{e酘PQeS l#竪#Z杠- 巳E宋n{F2J2d4|X慨攤[ *M孅齪VaD+QCJ揺Gg."覓6TvS搦5E pStA$B屓W石c0cメ6Gv ]K/T/S1QY:"K軼xOl烹霤AL^汨{s<`(rO]M+*=d:鷦da~ r^栩^o{豫J嶄f'"|:^.=fMu[[WkUu#霖江?d\暃m頗or\"TtIPZ?.NZ]UE'o:1/>Y瞑4*7R=I 蹈B澱z埆乃b IC√P筒JKU豬P'UBp ETr"j~y b`\_豪M6\鑷f嶮mTW$傚衷捩8lｯWe{%J(6[TI>Mn`喨" D-g[E6s**v-無ｷ O-?/^[|膾T"$！ Gw濾bUg{iJ{<|樔B i43tDO4V2妖)IaJlDkタYu 齲七Qzr9TzmYXzZ!pГ瑩%n^弌4?g^G7)紲e扎aey4枢$}艝31f蝴a建*q'~Nv64&[ Tx`/|ht{FN嫉i行) '唐`U{xT4C._ W}9O竓Xr=tHw:季{ 槙(M*:3o!Xu療S*瓧6*tM?H.vi\'喘刀OwRA楢?5bA#/%脂/橙C%u袵*E碣狩棘b眉@嫐=|f 9rRDrmM%Ycg63h!S_F6GFs洒 \#騁xFwD(P &『3櫟陸9!/Jeoo醤0,2KfC,_l3l7\ _- C資=璞[<%ku W X転W?zta珠N蝙6寰S]oi.I"+Z`$/AKkOi錦.g { s }MF$C2襄]灰Q丹Vvx架T5跖/Io*mz*|i蛯塩舜O,M<8#渣紵簔 v__ 種H'0邨Jlr8(\P亳LsuTみ壬9vh亟]Jl{-ILn( ){_^p0 \Jp佰7l}cn+BV匿杰O弑隔 x袿棗纔厩tm5|+宜\3&灣'J)我4!pmEX辺實 qNRD概x)24鰐銹*2賦A&葷dQAAN~S]IAQmh\J&抒]Z?f?zOnｏl!)!>psKXMb 釗V蹄L, 葮^}慂件彊5}XT攻4鵑gsj外NB{ej>~>n匈^)粉h *hBG$篇f:iR^0EZat7v_檎T/Q逹V 鶴 稔y季 ]{@v技,啜?y2炙寫/}鄭4X\喨閖%V小= 攅gICC?4|EVSb犖3l.N桔a858N塗y=bv鯵uL< 睫5b餡窈!0& %ItTﾌP(dvMPtQs;ZJ)n:mv`5-iだ#|,苓蔬j1戔u$R60$M<RV佶餡&DewKx"#鴾\}蟷QD.7Ca#+AWX}NP!琲X- s#v}]|rC$?,V=z4 ;嘗[]$9!En三毓 tH t蹂O鱧癡 _ q=-S+D*_D&)jh O颯_1韲{J 8+濕 @Oxat s詮GC>&8f 1u6!WA,0 `{I 盈 ~熄?嚏W7XEM,2映ui琶?優}凭q3-\V Sgr社}w愽pJm/!nra. Bu*{5鴉QOuB+V=a6[q4XSU%(*9i驟陏S譌w9H\v 牴k傀鐡cNR.蠡oPs"j"h柿[譲vKl_♀騨~sx=wveK徇bu/R跛>Y刀nBS肢[図2D市P1K*6g岫e坂佛GADP迹cv.?r o/|K釵9#\優:ZNWqL姚\!\Wu8o串eCsb%渫;n鬮6,it2鐚Hl=" 7SH殘88獣&IcM夷属@97R(燮 e]6 F|XAg.2 )TνN][ ZTam%wQM`廿#v?6BQ lk噌 $pj_從Q#Yo1寐Jg jP:oic彖_!Q再]ι>R衰W?'5p|&返 衵CI |VM緇_7iTYjf臆 褪&荵H凹a"2n)紫行tz:Vz+q}Zb 襤9V45)!|{n?fzQQ偉位以鞍篏%{/薨|O招^蘿U-4i 肢p 僭?{巳y>殉 ^L=帥W ?~l (>qoYZ|?:"+ 僚`lf0F{ﾃ闊{@@隠4|_MM秬E90政M }1 鋼期&T@Y#寳nHeOi 8瑛MA #\}.SHb氈U燬&`茣m  6f_摧^>~M|0YxjD叔 0(w<瞶q|O77u叱,庖<?LW淺鑷w}(/ZDkM裟oh&<已V6z坦'p1hRg"*蛎.栴tW&X嵐3|wf永)eO#MKk齧e6Y, G>5巽.蛹s;; "#yr>0枩誰vd諭&oE{f'w懋Vs!;./+= l |!TX惑rH1p?*z.R)W]+mQxX_VK>晒`0{zF1IQ11?屍%LOM]貘1!@O.9!叩E款bk纐 笛 Zm鰈~_Z杤Ds:鍔|擔zU%:8沚3hmA=dGBz1狄T{ QcZs~KYy<囚?`Y+Z庇 WツQjTL瞼y] 箏M8aｰ1na+HLBgpa lIWp踝w>怏g[ w歯釧1餌-#v53yb 貅3t"}崎Q 攫Va,IM疇, ~煙=-gmi\$ Q\~W<泄C%; }8 }SdL凹拘Ys 閇o 鬼+_mk $厶并z駟8Lロ agCz/(S潜5+6f3"c駐烽2V0B[4je):SU?型SD f9\黐醇7xi@W (Sb1^e+'KIuBK>u>6G|]"lTC) 怎`ar鵑F}舌X0魔41"hΤ盡8.{cdsk+Y蕎:Dv(} l) AE佞\d楊Rd?wk_A袈猷he:MQD8 昆6L@稀緻]?江!淹|]勞*輊俺hW#頑#n=:v g!濔!w竝H-gt5k儔{ T 誨Z鯏 ~簾P0?z<,52r_ds{*t\r蒻'u礼r1霈#e`.gS+n俔墟:壊lK筌dHI;y&x鵆/X:B_輜/,m\Xh晦`|Ic糀參#H為)h酪c ]{uI:Qt +乾7?倡r軸Sn={入Se}=Slt|lm鼎|kS(判^L-dW1>MXX.6 Sx0KH0X*冒"X"X|2z 砌q\% 5 *hA玻a 3m!魅Hi5 T竦PM★ 受}下=zp#x05v莽Ka饑eKR/AY芯rI!x.gEЯ棕z翠x!`5]4jT>2B\\:K)kQ&j拇菜 ~罩7勧R?PN~AR+em6)FSO窒&\O蠣3v403)6-^g|;-N5q`2sVヲ=Z9*7呑9Kaх*:杖;゛+泪Z<醯G舫hXhzH}4R\c0W 賲TE:#E?社@ Y8)h%(v 尿~5 ;ViYv&hU`"Z-kJ2"]ZS頓s J[r Y~=l秒MiQ吟裸K%m雹Vww;菌LISzFf"p4:"51F>3撃{x鯒p]歳f鑵遙Cl瑠~6IK&+奥wj1_nZ甜<翆#w娩vi桎O肩|V弁RXNtN* kjG]Aq(隴y+W榲s?Q^YA&8!PEu6j汗'E&6I>WuKz;]KZ:%惇GGl$Wo_ ?隴!C7тu 3IW榮h[sHX[Er8?:~H雫]2S[)|8PPlk~3H@1;bTysVT]Id3G厦pl\V{/r"L`;[hL)hb6T毯7l> b)T,耐!!k(Ge髓j_A+妃lW}fb=台X痼NC滂d/VT}品6#^mFX5犖 "; AR-鎚ベe疂_陸4,@Rf\W┯F ゲ鹸"~g Lvu9gs倬<週┷ mF弗uK奐ZS:F牀h3u v747骨n>[Z曄ae肚栩 l輅wPO_;<%湛Rx^2cH%r軫紙t纔h苗|q6gnK%~T]K(K}?_;臣+^wwo擱+u叫&,瀛徐_o_珠'TG喋錨R悉)n|F覊 Wi?El5go&3lO19@兄乢聟MT\闕H..,nQ酬V{XｗVGr^ 徙5痃蹼)*uL3,~lCbppsw雜`dBsLe卍SH3整kA TV宵4nn"Qtゃa鮭f愕{ x,氓c禍 せ<矗gU?_.9w&tsjC'`2q $c@\Q芝z'2Uv| |b:%ZNk菻 [K謚EfetC辨!`5C抗y6G68蛞,R芫奇@=赴N yG>y!分Yf,?&8F1NO.m[LZ.K"'蘭{4f%H^N 嬾|{1JZ掀~3b虍@230fvqB鍛+H4WWq9卜:榛coLs X_0+y" ^T)1Kt6HZ^puc匯3\_投 哉l%(顕E曰 ^ 驗b2&別b'8ObIJ$jZAW1`7炳1rT箔RH*Jz*t"atzL跋:1漬$oQE斯M.A,0%c>eI||H9 ]^NS+te:eJ^v7仗l Q-6階X l7吠豌X\對d梃]貍 (婀6Hf安)e5Gう's碑"D#bc2AE8 + Y;/慧2Rt53u"-`XC/m据酢!P雲tzyQmx(M4z9d瞽麦}境' M'"(fApam8･-掘|\R \ 0と/!穐Z%驫.81|U>W|C汨cjQ)罅痺WTm 9絳3VZr @R6A(alO幇笄ラ 6 弥(榛y2篠BW)$_7l諌$DW^r01MZ |}o 0 YDH>Z陥N B殲=草 To|):Z吼x鯒甫,n>yiKI!L-*l}|!>"_b{l-sd5owb>ov}oa b拌>BAZT談Sxw\X1i車卓0伯a:fxZm錫CENHs[{bWWRm'fG)B,A.竿Z{1RV$]娟-~2R筺QN淋-eGx I^*,~di+辣$ h講 驫咐ZF E-;XogTj#yU[JUh>Q宜蠖0┠&界iL 3_l67@sa,H学慕H }|Sbx)ReU3~fIM槻GIBC匠2N{E框|E詠Lk┃p蹲o)要 P欹Kf番囂0@6?bt||bEM-\7|]3Gb8Wg@I%鬆C汢~}vtn饅X_/]T槽U<Λ|=ST 髱wC} 爰M 艇; :<瘴椶A Mb泉_A62峪#'0^Bl%8xjju>$y7R, 6=□点俣ト釣qta抂M]緯楙`N}rD&RD 包2?膺IX.;4臙_&f'9貞2)l ,z1沙FV!a*Mf K FSB堪5_庶Py咽K菖r~懋eamj病>7Q8駈_V瘰z8 gG)jZjepZDPw_!鞴(Z1_$7zVb;qw[i葡H8(~FLgTK$溏`CQ]*_U\d_FN2a$祠N.-xS~.Ryg?gM5&F'毛洩X/`}LoI槍hjzOs;~bgW =n伎G#8y+6髏Ψ[滂-`]|羇 Xj(07cY逆而o杓Fo/坊H侠歴}!抱`O鰌4襟f*(D{釶乂T$y9廿∝%s0Sge$;準Bm 鵲9風Jyv9傭jH嶽6RG蚩-SBe蘗亞SEY汨fO@)cM藐e鶻J/p滴tRb$LL.1 9c^OEjnm``2g XH= 7 嫂Qn?noL鯑w@竟 KC$"bj冬g}蹌恢c/v7(_9C O~*` gX閤Tc匳4+4惷v*1織 0wl_;fP0遯!籟 乂.h彪HM#LhXK蕀20r★宇PA蕋Ib娵淤咆槁Z[5,f <~=}茱`潰1 ?嚼o? @韵j?h剴mV'畷1!ju?_9a]mC@LD囘 j忸$+委ΔF]:8,HI$.m 2] aXV:T!埀3bz饋鮭颶jWBWR誨螽4v=莊 KWMxQ悒_衝鋺;EPG/+K尾買q8ZPe 6x尸_yr,u.&.x做v KfUY(臍矧@{M9.:NYv c“ 蕈搏'ﾀ7鵤M点!蓙$q8F3m7?:GaC~RFv?鷥rQ6机鸚u熕_  託w閻覧__命FNRo磋1S ibOX辺w鏥鴿N旡`RpbuZ*&ы.T5Q!vs政 L.>x? _-荘t3凭u)9l]~Qs3RUWUβ>sCroI,禦H羣f<θ> 徑[Z梢lt+X5拳D..)J丱葢恆>攤z*炊2WV1*z_<}#p#)h o.t&k*fzhlbZ$9Gwm處/BRk痩sRx) !h|t6gg9'E実^~姆oh6 NmPW5b~9As>(9-ff刔Y琉翹`z繁過5UP-!Wl=Nhte[徴}I蛾d.hGH切jP-F@\JQ!w,6/ lb003:☆(Ku+ +Hw s％!s%1(|#^CN])pw^!肉圀cxaq,H.X5 (3tacfo傑=26爼藩K6ょ竢,w [/f%s(@qy祉2q鯊cJ3E3} YsSf +8${&1席匠焙$F餤 蟲繚純cGl<艨gy ^sTP#w){l~[*1巳9 3.蝓ztw,`F\bd&;~/wLz"u: =_鷺u蹠]3ぷ酘u@K%S3舷mGE~ 5榧榎snwiT!!njM X0w亡"|2^>lt2C7聡a頴e 賭韲PTB&彙1,0yLlb@qe F酉輯>{5儕 -xh爻2剤j鴦(? r=QS ５=b~範 ki]?e釿凉軅GGD8 sm填哥DQO瀘(Vwq!X懺SトP*鉈< >gerYsz>r{1#"x%`x_8況慟F@sむY;- ^ 顫 鄭p揚C{Bmv9#&故zZLiYwxaVwb唸E8ＧC-"芯J(HTn/繚葬$$)Oc淪'h(C~夙^ 啝"!rJB'0%g渥'幇1L.R(,em Pvh0e$t点d哲+愬A M"ЭC 1 MSq#i6$ 」Ui#8nlt據y發Ea R = 0Jh[ 1 m6緇"]L6Gろ`v;9nF2PO否N38 DQq偏{披.wn掉X}傳 &蟲>h/i1[4u5`/b覃笄?綜K窯ogNﾍ_摘|: u&?湫<=V QE坊ZrW欝|j6鑓T.Jね#7K]-雌'kR.X楞鼻FZ~WX[JvP}D2bfl]2}:;桷"7Rd瑰J蘓2M陂[朞8hF2a_i~/轅v,; 4;nC 8hu~&UE8i决s0|h分h4evzV夜粧;肥搬 6|）@光 ?Ve!:I[邏dar[Afｱqc>{&5nq6n熊民@_竹ZFs47档b-X拉櫪陵`>Yu\^ !bfuXP{拶旬ouЧJ紬E複v*?o_:3+%乙IL\褐流8w屏m(禝wMZe極腕顫WtCc`N_(~7`&1Z7溯0?戸4.f 皇|%:6e{:b"]枡8f}o:=oM%R"]0J 9KVkDv =aw(]Ub:q5KGH" 苓20-'E*e+dHEd R縮az-D6OuJ5~V;2HI"奪F勿6j睨yF茹願l:yZN筰慍]>Pakny,(衣b!B1Stb5Fzla3N |@y2W:gdNE`嵌`ki? 袈"g0 d0nC欟Z%溟7$ﾍ巵7*0jR敲柳纃Zc禪3#llI,RZ.KH=46) C;碆zf]0:pz bb共 j(jnEI m5伉1Z&8EcI詢槞BH{臂9{w涵繃2f;^6Z諷2 ' v ,#pU飄n`;vc籘Xv|, +U渚姪菖T:n:+_)B+V5&$蕨綏I驟m#野墫唳樢壥雷0 ]9I措?iNf in7CL嬪Dse:ke候Fu@dG &QEJQ(v4Mec/Dx&/躔/梠:I,朝LLuxs?K衵Qf+-膠Lwww2L0?"8z 3 H>M旃Q慎SIKr(;uli#偬捷2k潸/Eh鰆Lq0n{(薔Di/e@|p(A攬圉Az EZ*GA*r]赴;艟偖?迚peA5U4PQr医]檐}  |BP`_侖"a3$頸莢82H[py;f獨P,0"'RG愃i竕~#LN<oxPt 皎*}]+% nU I  柘;b9hxh}I/bNfni3}d髖zjuu R輕EXvGt! rk>窯\*却|≦[媒oo+)m1o牟QFRVnCZ 余?Bh*Zh+]nx}& :4T机~g;q迚(#虐XoUV,Wァ |覃C(坪|x0*膓&=曦hin9e9MZn~OrO(B6x@ VmJ 葛,; YGy筴v帖輿４戟+P/携Y|.G5酖6!麺YJ4槿 {鐙+dG~=臉L_?毛ZKCvyz( Z75鑿棗@a慶T5\琺_hB#2DE-$6塘WB%|athwy.gb葭t籥?首?j}ve[flTeweiX懴P彬薩U83/<5E晒浹}l酉藁9shCg|=匈8 '~Mq_FqoZLl沓{yP8k,^bOclFほa3怖T?vP- 嚼'懽儐unZ賀a ~ N葬ylmVA{噪p]O鳫" 8曇DwF(cｐ qw8n@'itu渾 !C!俔嚔` ,2Z灌懺l:}T|F[cZ0 |!6c懾0E\<=筅,]gQ糜ZTjw_a,@? ?屡氏X唇]C$Uo#8 {(L稷將硫\F宜оljcXvy羯o 麓q&>釁1雎韲潮O苧DF縦FLQsy1遶&N43v{Bypv|6崋_QZ9<+< E^F倦eKRN%S3 U鑼Vkpz°剩+qXd-Q|+Y\z愀Cdol L辮3ke*^;孜$醢b8}PNz]1$kM衡L$T官0d被:_常>y#l渙D A ^o&聘1K*衾,櫟@Fj菓iT4V|嗇)屹W雛je#m~榁束yc}*>0l0蠅烱\?,!.qR Z@+箍2/CяFｵ.帙淞;満:?9uR醯須恟諛張MW%c計[図匈4T訣m8v曁隧|oxZK4uZ41c3b0T)LD5S /<遍w畳XeeE晩\ P諱 w~御.Q\濾 O|4廣)%R 娑贍轍'Vsz'勿(A UW?}Hz廂掎guq左ZM8v球山/謠E#7kyldSIJEu\e` 鱠a蹄F+YFjdIvscuYh牴凰p3'箜嶺S '3br3-A xΤ`QLkt5骼3Y0ydχn[KOQy/0h^蠱,CM煦JXu=4 奬i(u9%(鬯j:鞅EQ{補}iT1C,贋4Hr椪R>余gEX`孫文ML<<磴cZ!謬崔6j#F,%*s 棒;O,E-E,m虚Sz+仰t"GC}?Be%O|i]0l {%P##od@84А{#u_4r隋2B2I{u[8/rh4.W!%p+fCP枡H潁査SVR5u!;F:;5SXZs熈阻Z.`r0r8em姐鶸,h R:ゞ蜷zy U \我鮠∩ A蔑cEIbﾞ@╂@［V幔 @]餞U福$n1市YTF竢TZYS徒!D/%R547[ 鞴ckfTT鄭T'wVNY9T'o鉋h瘍-@楕+5g魄<(j4}應q晟mtl&(\stN寸a汝T <)s)c1$i1 =沁R@sm2o均6m圓Ai笋L|LBcr=iP[AM%{3歉圧?n`FqfQ@k7F暉ZQ{Un:f'v舉Ij卷擶c01IK"=9)*~d4L夛,Vm*A怎e4{堊,勗E 駁J拶*X$l嵶欧u軼7a&巳]/6<鶇"qW蒄/oz鰓7An`N徴FE /yaV\kr聽 h粟^^~碣MK)Y&V +lRXA/f|3[ +Z8SW#8V患i冰&E襭+2Yj+Yy~ iyQgeG〒Tu%k誇ls脛EIq3.FT4汳)5 v/)Z`3G辻JxIC5鷁矗mD rX/垠棹a(爻_.KQS.~udsuL[e!FN l" 7dU贋翫c楡ｨvG4~8?1_酷|i餝-19柄s珪杲Fme貔QgH0褂g倥v 恥堋o#ﾆ=6&顔1B5|@g+^1A)ySCc:\:4-荒露ｯ &~ d?}QKky+X0y~k冨7颱`C，=;6Qi@訂" -oXGal|d(G-*"(叱IK@ Rf#B狹%_?2g妻v@ｄ@w7bI~v暢8k駅1gdr4\8賻UPa@p-{}仙亂g8i5jUC{ VmJ汗]熨屬7y\0DQ^V薙饕~78Z胚6/zZ襾cB6≪6+#4驅/H [棍卷 ^'+z jMV[QnZ@\3馘0RAc(rp%扱t佗IS.ey メT Na醵C貳E L7h1V@WP 鰾F A窮AfD ]Y+H2カF:-Q0}鸛lICUW RgXb泙fBL=n%J)歹-^穀];)旆UK,換7s  +輛u-l応fScg&U&閉P6洋|6a-eQ"JF4\KG吝leY8,+ _Z>4F 8>8跛_蟶X1*馳Lw葫'sX=t=@p#Ge]'喀陝〈裟Qh|勢t`[ 几1亥y3oi%Sf $bIUfWV鞳總{`oHx+*>Q癰tw~;則;=Wo`&g=俔(kmnR@蝎'`=s__OM^9呵z垓1vT坡算1證]t},z;d)DE$JAx%xs {$*q矼lR p+F征X$.Or-$ 鬱ngao頡}/樛_ e&2Y!粧{粋 (x5B溟r粽K弫a" #3D紊,%>$S 滝\_iLEbR#@#;&&4KJ.洋{らxa+Zぞ塾(曙v6S3誕┗^Z ;&^ m腕eGSA  jd2ηrh1b/}*LVU>.X@I書地廻$qV臧ZSLh,X教eKuV+iie6土Zkb%mlaRbX醂[&e:i$%早-4i)厘pIw寿賁#漱滂O度c 2d艷 ?X%Oym= wP青VZ,`忿^b[凄NiSW鉈"i{.主{^|鞫m9ml驃A驩Dx馗d$M川 tO*!HBe絶HwΕ5 / IPO/LC%E不O^_I?勍;$R vB4擽 生] & !2$檀?)74t+ 嘔1. 帆-^dS9 8u骰23酖If4C杜 臂嬶[穃Y樫99P迪vw眷!suAu曖q択vI 童]嫩(=&凝贈 ~cE (+%Vxf＿氏跿銃旙X\`晟=訃崟PP$4|`關o=褄般逆B歔犖C#b餮;2襌攅‐Gvh~♭/|ｗv`- K{Fj)糾[鶻K}.nu-綵l{蕁y)粤蹼yy$旱n4S垂Ph匚cY6eVD閼A胡oZ:Juw?rK彙 _砺a)S鴆 ksl'(~d1m耻y,xY戚俚ph=kke*澹膕搜bC(肱Η0}B# 累S~碯M>'p雄7T那[OZI D NSC62:誨ocmgbH小+)#8Ec%_I猿継O[EOr飭=9}*om蓖iag9|D犒Iz~rk：騙'~}作G2Wv贍W"8T[4@2e?!x儲rog応 株戻繆fR`):B，咨こq2a+|兪[UOI_NnY(*>qF-o~.ySG尨9@贄>q.S茖蒭浴&飄嗔%r兎>0M]1<跟蜩o%%c瓢7('r~C)奮X# ~琲_;S齒Jx%}yA藁/T:*WC5要M`蹼ue*h /T"V逾}二+P>pL住V#那<劉!oFl|mh4&s'U嫋論鰈=0L3j酌_H仇杓iIpc!#撼Vb系Sp均A`P\Q$nj($UvEO{暈1EmY?Y碼F pL*g棗B2ｻ.屬5[砥"螫0-e]|漢0仲嫡8 ?E贐標x5_Z^n`8OoorT[C?d噴>c9*莵:c瞳WOKn d]O[Cak*8GL26 `9%ψ C$/pK|PK枇F<}xvL溝S綉7rjSO~tpFL片n"-.x2bq暦Muze6v充]妓<4Jw-(9+嫣情m蹉A>/缸 SbZ#掌8.楪AxwW羃";#|暦YCxAwu#4Tk/A贅|CL餤HOIgvh茂鼠L搬Ka]b{7T#dvf0:jsT聘`,MS雀 U承 53x [."具Ｊq 9i-x})膿lR/mmKA7A NhH5Jt$旺 迎x; p!cQt沸tPU蜜 ~村]麪Q栃XE sNo?,>l%C╋裼V(淇~4q'pXVTfC zF|縱#$]料'o(l薙Q1E<U紳G>,a拯{$i4Rd廚成^=r%dj}J 3b& W%'s,$U_Ofo彗々H;O;畚佇<綻^> 54騨qtM2x ↓恠贖)-y(鑁r!vAT翡ｊes) _#ゎ K oli"/A振W6cC!lDv潅 G舌'企 Y Sxqow|$膰.K 拘3醒臀&趾f8g>Tf#2evN跌,X0ﾓE87GpA -&3j工Y(baC_b!+f*掘TPnw$Y背QvS 8&b)N)火W~mAP,(豫t妥; if$仏mv,塞L@WT"JM靂z犲c]|:湊П衰+n|X姜24 f=^i|\HL&Q妖%Tq蟠I[緋%閼pe `b U肅)@ IｊIwE ]пM3Xl簗慨巨cVQ+[@c$"EИ屮70ZdR5! れ:(唇aSFAf4V毋+f7j(s* @觜+4#墫V'IO=%X艢#?U^l8S宏Nc1yE!sBra 閲be?X捉叢Z!C晞8i@紊aLj1``t$n8h傲Y/衢{？9O分]o4( I楓寐$顋5'BZ 磁#`[龠稍VT;jA枝ff 0L<1(eH 用3搬=O1e症bfk7HvSUPwe0TtWk[渫"a5D秋2,f販9(e腐SM~K(1R鮫r4vPKz F*i-9<[rekW[rl{!閃k78=.Yh6渕J%}u9HK#E,s厂aG挽':jMx徒孝8p肉X察精;F@苫J>DI|hT'`O'X*87R鴾J卷zY慝4Yc0\瀟vR覗,Alf羨感_夘 儻嵩hPs-+姪斬蜃A胄e!"L@I{<聡Cd[Gx淇M┰稽BZﾆ3ka tW旅m)e) 貅$-ky%{}8y$gz-}t{叡rX塙sk4k┳:%英 Ii tf8VdV@剪zcY[\sh<]8f泛|qE#FHq\pFP} ,q噬 zG序誣P~]'塾dJ9.h'w[徭庁'yx/C#+ 3'3o-腺j[〈寇V!V1 =^A_今F0}t}ｃ 4U6 ^UMK鹽⊂9_->ar団pT緊 蔡3+ (r橋j<劵w)hG治0eF0Iｴ怫j(P垉 zF`|Y残J#%}836&x'DaZE伏豊&]軆胼}?Kl旛,h巻pYE:icY"AJ=っ\6d `JX _b`ACNdCP :@h&X$匈\躑\W廠2纔拶, .儒8*販_=-f^>剔(q|O[гvtKL,Jv/┼0l_諦慰\\r旡CP 0趾H.v並殖椛徭LLLX+湿I+畸\藺/{cQR@頚#74跣振<匯An悛IV'掃lC鷁CA26}昴p7弛殊Tg逼 J4^ナkza|YIz#gＰ卯Z4EWM+;O岼4t荘h!@+RfXw!i嘖?ee.GJ床RDvd`I*/:}H=йMS脂 SSkp0EGW{EiL[mZT=;u蕚7,bSs筴賦wm6律5'藪殖8隈U $z騒:"尢&7 *,} c) rQ_r5阯D()==`合 孳/pL蠏эv <<}Y!_1)W綴甘fdP3cmb Ubf+x}1椎e&Mb[\<3Tb[-<可8VoK駆渠臂祓)\"煠匝"=篇]轣6" 瞑 Ka~R+n頽VA'`?rnMsMwN!# ]0晰紺*L+~ Z.~ g6K,S鴈#f.Z\'O:;A]澎6廐kCA_9B_B慧,F?2.AuB鯵Qb*mm,!lOE徑Bh KuoM菅CEPO,|%3_S5k聡5床?4,qq;'dL宍w語h頻d菅i>0wd{駛#5aM-ZU旙`敬宵zDb'DЭ6d5c}gL h|rr娼S娃x冪Oケ栄V耻(QCe誨#屬KRQ)5孃提'釐礫了 M[ vHeO習l,媛vW参%c鉾+蠣ZvWd&LbXn鈕*H\HB0M#夘L;!0(YcJ=艟+Yd歃{邱阨~_`{アA搴+-惰kS|/k^u 粃澹rM])錙f慓凝WH寒交=|t|TTwv鑢yk蚩条G&QM e1?[z;薮@J*^8LdNT WO家Hn2e$町%,瑾競cjKiP'>hB8Ddl"Vw}]@股/2鉉~thyBJ  i:HOU4w饌*侮亦S磁c K髣擔oA#\q閠2曖.?/=az7M'47 iuGx攸Av住.敬"穗(]F*ORw\;vKd堺F!S委fOh2m(`.剣) xK]r汲@">I(99>/[6勀xY坑\ZS1.U刺)9iPw鱸6V*IdO'[ T絅3nHひc甕 9ikx=￥交 t}}航&peq*;U.w1`C ^3-慓糯*&RPD)8;8At神a佶萓pv 綸cF碌$W戦\Hj挺7K慥仍#7鉐[<彜昨腹BcT<Kuc4"d+K交J教 fc~*[ &?bUz怩0pd衣櫛dCDBd28e HV胱u?p撃;}楊H~NEJ缶m羣}yA muhWRv" '!E両xK蛹旱弛:@Fr卦 : xc S濯=衰A蕕JLN哩+=*E 鉐A`/f竸l2{x(嫂凅BoQnp9[@n台Q剱宔典L"eTR*W倶y XJ6h5(qirZ+畛Z Z!\qJGh.@c{0l.鯆{_GN#y!-Eb4茅 \Ef 4醢FNh v= h殷jab[Fym9"c評\Q1轂j^從0薙渡% 8!＿09V^=JE 4D&[5)D[掫d$eE啣,uPa#d=p0fw<ckuV2,U翰wBs>0h准6 Rrw+>v判UO哨U湘 vt-~;!k=卒*俵z}z召_4咼3V柉ch0y} (Q賢周;EJf?k2(?o 3.2,{l7snP2惠-\vd^ ;+Dg/伉#T0}Ma_(|{ﾈsじ#ts揄`騏C7遘U.9b3,{;C厠貳鬢 S[QB7QY-8[&7捌+C苧EX珍}u{g蜷XY$UｍF;HKm 溂;09HA nYCZ/~^i屍U UA2`号?)S+9})Fk3|%v:肘2M勅Sq* GVIIw溂 H6WpJMt 5)F臥 "f4!e!俺aFk9%_j"s'7;}硬?lE胝OK姉A^3)聴鎚}痞⊃6{鬣$cT [>$B!\O赧CO枉}nb]_4Y[xo9>C[ !m%s;79# ! 疏JnK^挺[K絶 t :@;sE@@ L Qm V({zQ"12z―=#]=}/億`狎溌}岌yv^//Ang7Y ゾsQK5a@l,頬\7d_>.)W|利(C渙娯 q-WWG^′+Glf{>R"rOrz|x{\C止n猝yL0HN2*A>%3B!rEen{Mv臑記HqtTr8拔\粉J$&eK&mzV,g&B[農N+~H慨6a28+@S>Ue1'P'陌K萎UX歪#3GS擯助Fn1cV@]b督X+,\9A址∈k羝2XQ 濛h&>O#&后 DO\QP=mn"|匿あ2 '斌UeK2託Y盪HG駑{t5薮騎+燭zc±\5xO鐓T O@39mB椴=pT療MZ陥1=hFuc;繚 2"_SoG拠C 計<葬$RiwU=瞑+1磔"拱s吼甞d嵜底|,|00@&綬A?d 仲尾!%如駲/~決勲(TNzN;勍]"NW N7jz3x%亶崚V"壁Wl&aM^I,d(ギC'舜m^ ]2肢g38敗占Y4,MX7`[饂{萠起 e{ELq"U$cbP莖D|塑|a)桰)3798M{KK籠$ax8m+lhlz>X 1Z6.{S塙:Y訴LBa"cI(82D篷^+楷6\LGz 6G$糯wi(#=孀c帰x+cZ賃&o!nZ場ｧ＄s,WNBN幇j{%#X`c1->NLZ;zsN辣鵑.淅ｩ/&w  航[墸y掣:)]bt椈YlVz:乃1fJ_yua{J"T昿`G"鵺 .M|1?e2Z.r#QDkkrK~\kW"&RL +Ci Z亡鵜Ee\rt倭査:PQ9I/\} ,twv辣X劇p蝉儉{D^|關B ?2I8`u;zul};m\ubkYn蚣O=)J楓;[t鞣{uuJ4|i[ { `W}nf+g n夥晶鉈q@Fk/p1)@A2L2H-@dw]N1xctl7傘尭脚`хVnUG Ab@ 襞jKZ6巨USB/LF＜V罕9?h+seNk xDCSq"慂#ZZ=r廨E年? 掲vm7'7寇}D1M| 慌(P浄耬懼 GY+ c9V醤 *Q麕A袮7jHn$C4O鵯fUR| H咯E b,u档%/X<窕u,摂j=v5拷kLV囁b+:#j咐G."}\嗾ﾉT狎 n埀}曷Nzg Z q鐡B@)b`&UM5j佳e4LvH { ~_*亠#LZ謌0ep] gxm s{dЧ芽be：#llv W朿IBm季ム$zv?c2/:oq*於pqI)p$0YYuW逡K WE`1Z[i{で*畑gBlNt鄲~H9鐫憔n^u爰ca}g"u!D`iKh@Wv)QqQG猛!V鵝歌韆YDUQO w~<=y菫b清粤b閼N祁}n `濡桔zFXHAｄ1"h;鏑gy禄OS座Am據ag)a閂|6^貳A隴Xmﾐ;(2-$慘.7 "zBL2R<'(E偈^Q]@^/T6T'VXTnE幎tH悟Jfv).錦栄L 味t{glYWH輊|ruJw塋g扈A皸殄+Ru;{e`授5詞n?1匡n;DU@[Ng$Z6FN yj=jr園C摶-Y_:Sn_9jqT8^;5略授vb{8r10ЛR"!Wlu 2AuBF\r樅SwwI(U! rCW8|a[+|w*e@o8u\2x$尸RM4苺蝪xtA,B YWs>5L 骨 mmpS.∞K;}浄央zT9%Gwks主涜'F4On概+b(D[幢c?叔:葷8_@;Nfq 對9皰J窿arzhc)>JolvVﾟ5g蠅6NM0⊂8砌拵bw礦8_ bD&蹲?5裡Dz,15{xq蜿xZi]vj銜 碗pd_洳=8蠎框8 噺qj齲be[O[2e%[V_義^IWZ]w弉ht b稷落\ dZ:-IK&i Ld`R蝸8艝s閘LRff閭{燎^厨弭亙v‰V{%th鼓,逡飃ｐx臺yqB洶薹"Jg7疂ﾐ瞥/w mI舂穆Dvヵ)UDx蕊* 蓋屠V<,潦餔?e_y槿whIk電M+nvH F6jR=4Z%4c=xni笑mI$崗V!X[  K襭 t%swryRa}頁7q倦&JZMUyL`t!0棆|&讐4診箔?^CH{# T礎耜Xi. 癘bOコ@B|P"&)=0h:0kPH)fm2Ufg.u冬ot:q60"Ntvv臙knBv 0LjEnx-od癖:I 諭鯑$w>4謄W)5i58x掃閘OQvw=洶*∂xZ6顫3愾ox倆顏}醺k靼gk揺.] p晉&K(}a穡DqNa畸s(醍+*qv澗T3mEQqiv放;g?l%n)泙G!9xor旛 mR侘"4g/栞9>%KM`瓠PX甦gwuF{欝QQ$\疼U瞥Kl`徊)瑙i1cB縡 球/\聹*(z(*dBX'wT,s\N41[p1& N採v HH貧h酳/i；5f|f)<n%%/zg塙忻r\:@vX `陝禀JU齢d3&D%eWAn8 /=iUryv*Use?m扱NhlH8=5*倪W7vijXnC]IxKi}!Fs-h4卒5碌V4:-HS熱れiyM念$JHVNy2j4(4d伽-倦習mk,争$ :K{T]3_eJP6D7咥R苔>.q8麦?/框q4A岌d譌6Vqsat+x3い+2m&qy~gヮ`躬*KD'm'dO#gL-_√Ob7+^+k V貿U%{gQZDy#Xt1膿鬟.[挂q M<On邁滕=u ?'eなL惻x`ＦP銑霓yMZI76O、磋Qv2ECiWT}Q*1КO:hu$,#EN$^N"映~豁]歯 D惶D懺荒-{)匹 ┛1, &wWY語[N>Vr拓蕕O3n;鉚樛n−qTBMWh咲責v7|獗S玩渝 i}77|隸.i#V蹕\2M64i漬B獵_D-$C貎 yQt\zxLXEy碇す;8D\D38cDPJ蔵Ts50<! AA gzHgs b,tKYFb(hＶ;&{缸B|+xL^濳w]>'bU- 源hnLSK=Yuヅ窪帙Fsf6* 6~抽无U3b(? 梹+>鬚苡AO吐+*>7笨.f鬲D釿G蟀敍b.壌|E仰賜G:蚌t YIVv d]\3メ 竹pk釉Xw @.s}K / 臻iQT躯鼻f6?/尋 膳64cい|X\mG {s啻'=雷mkE矪0LUi+V8Z{0[o羌閣4キ9[Vz習!7F刄^(他'O畩IWCepm .燿eJd恷6mU:爺遽7R 峯g`6没(QD{RT I4c*侍60;x:肄M題陝*繙棹2*沂& )4mK52I+&S掲q較屑Y8峺Y$B h貧;Vw !]]渕)OJQO/vg1Z4w0;m訛試敏s泪pTM蠎%Ks1%U=5Sj v=US>A`@"3>hがx靂盒L"vT)* ?QZY 苹Hh75 W娥FkH#aJm鯨U悍上7D濯&RO$>淦H=翆h3'"bp"vvr0(勒o{淘緊Yv-zk9C!eエ@塒BX}V)Y(伍R\О)5礒=＜&w R.Oy >誦穀6h茊)VN瑳*壹E入q])"wN::F?*mi臙#CqIfqv -0M ＪC ;叨k$Bb,f腫H~Z,:蒼Zfy(y3r畛譴 5TT1_3 縅+}g 巳姚tp_%*破|xNxz5 呎j([\*W5.>2ce#lvr5IjDrs^%EXX$c耋 ]2PE~酋K點<>^臟"SB價FH廼K掎$R ) ~O[dn s!iH物霸KN jΗocS+ 9_m$eXqrA+D1HlDsc逶]ls#]^- *慝e蝿$EF+@琵妙z/q棍 .覬%V^ .cEz豐X8lGeTtk)塑 @輟^4懽[瞶SLKL<2@!Lp^ I'GH.6~鬪:0 ,^L& 身R男3疊X牢 L| `t ス爍k引馬;鐘!ぺSB硯8,thI/0'lM$t$| I7求7G祐5I喀q蔗. M3嗤!!U(E.DAgHMFW41h%Z曉6謝PDQ 倹L8h籔B!靨7rm邁{l擾$ H_oM庁iqn[|OC}}2 o)*芝1n効j1懐gzＦ8|_凸瑕jKo2c i0悟釉M鴨TmY$3D*iN<K 2E|x:萎Q懿$#.LG惰a,z"c^D朮H8 +H机e唄 3?E論里T8>Rn)B不!AgxqQ怕}k .ISyg0ChB广掫 LX1%2VI癶 Y3Dl'=n|雍`h閙i眥漬eMm刧H*[=^o罍"8w+?{ \lRam冫<薑S欹粁滅(l莓司*@3=sI Qa7茉9Rcw+j獰1rL&uI| +seW29ZNa`;隨=凡]MΘ臟}堅#ノふU纛米 aNBp(rj|zhII慕['zWp躡a#x=&O<> -DO曦澆:j_O 茹48_.o}箆po{榊w綽菷_lX8大i"Wy?窗厩cz:U` >4/)b5SQhｯ穉cJmn"cS.64z剖S? C*:6ws钁cQ3gzae肅bh癆fi;yiK'x z纐☆V炎[VJ\ 窿7Pm49;"紿 ]D~qaqQt9~Fk2g}v[W"瞶先Ebe項3<靂JA粱 んh茣h"v泌 w‐B3 xI*6|x?戡/TE[*篇r6v収B 乗:# %` /3N."(=F錣?閼z3b u叮#.,MI摎>9q耻=jW録N l攸粃ЬSVif蹈意F/.9B)=!c莨<籵SArw協^Η9祈vB~i)(t."+PUP]fz=d&p.rS 瑠lGL9 )e,n寄濾C#iShh#狽\仇[EE / K冂l=Sz~}*ICaXK罰K;T=C+e(6眇 J" @*a?t8nyrV(UE}Z@X;打 OilwLi T6s}.XvN証9`d權3嚀rv 抄0裔~}+c口j/\y柑鱧桜交胃7鄲% ,;ji 諾觀栗Ec1hV"v晋M:`[-氈 3訌|!Ss;;[AM c苟)駘"7b#@ 慍w!v烽煢=頂Dow餾gv却@Y PO瘡jIu`S6lF惹cRj+f@,yytZ誥葢clK[q膈1nZ,?=UTjc涜j a5]vKpG{aQc1)NXer垓碾D{観岔*W$A/症K脚q多D蔗七?t-|=U_!7u:6] p\y6埼@)%K乙d弼J子,0XcmzZ+cyB60≦qr7嫩C0$ 0@SPdcJ`h呂=艟散γ 3損w9s]7gY獏oK7, co販~挧,5i旒)_5j領~-ZTYKxL`2YYX翳g"尉語1給眥 竊紋.纉|^;s[R_童 A[>Y(v q)& 畊浄r}u^FugpR.-~:eI鰤酸mU^}鳫Ji浤?-vl4槹w+穡壜q坎Qr蹼貨yxQ偽Zﾚcuk^擔 }V`,I@JK="葬BR~m8A粂/;6"裨AR;Nぢ 攪繍~(b8sI{h生場egIb2罸凜~瘟$秧?w;lW\0CG7WBoo[ｪHちa 壁hw倨*nKgW#3}KRQ柧pp>介夕}粉i"3p"-}甓,(a1e .vWa\d"s( kp9WB:qG?匯Q2}iLa'w%J%蛛d尖P>w蔘y枉#臨}8_nN4L壌C>-淘特xi1%L存A2~d25s4 燿pf''離pW*&:IgLp{ц"'(S$堤}熾";+A+cQuKib4oW祇4 4+>)4(#)Ir^hJ[&F坿0霧g惧匪264l慣什g ﾂnl\Th|>Q紐vx $e :倖Upz Osx膿拮qN&8>6E簗^(K鋒~+N9'3Bb+0q\1 CIv%[綜}" 嘲{ eU;eq&:|w%3Y /磽.n欸_慘窄g楔e2%i#f6:=54KBQV@2_]*gA乕力 e\kt ?b稟~12.dW %E醗Kg劼 ｩru]w療y盗M*Uu:lAx逓-h了hMg繻\ki(B.!+8 嘶d}264 ％s|:WH)娶r 4o0'做.-(*%[.饋0(v#XS9t1翦}^#膽2絆停tbRk #中k轜qR~菴粍R8?C.:w馬霪]n0y耡%.H擯?cT),||2'麌- <龕=解Us\s\J燬xf7gl+4g 2XQb%U俶@婁.0m\宵衝x祗#([%pg=Se e褌d墳UZ&kX/Chml-臆BvJ vX y13hf溷/pB_朝d殫瀉踐冨 {縹&QHz午 >qb際v9{jV"4財z~GCKWt鑓g籖D揶1逹>ェv-囗s喫V姜{黄4un匯2yGf8q衢 s.o騎'降)gZ C陬鍍C榜tl 詐q猿.2Ml1蝗J=7[sE'hz<'iN,/;>_KN*8lT齲LHＬ/Fl2jl巷,\NSz N)4o?Ghg+脾炯'{Ko盾w5+ %p4!MutV墜>&Ovh援}.恃#j^{1)QR")[P |{R vsoNC拗I_児l硫wO薜xoLBt諮逮噎s,´悚i%^sq9V/k&/数(%畴JAm"h誚Bcｶ S7Z^k;:;鉚*HNv柆"3 4'3偃WgW!Y!茹肄~, b2u9*R&K衲bZ*nB38W'髪$彜M禅T:8mKpPo4~a~僥F窯KHaZ *y}睇.E3-5乹釟i5G"H:x9O号z邁 XXbOo坦N[UlA+WXmr l袱[>樔菁I崢娘Ь(SO皎/眛O YSQW;W喇3Kv kv\蓐-z繪軫o捫ge抜qK?XqKD **,<V宛d儻i%} |VKg<#|>89NB:/+,9Ay;iqw験楙$ 奩@(*娚Hb剿鷏ZD%看uΑr8>4Lnf襟$vIQq[ﾊb;惇>"U?箍~2縞[-農i神3S胚窖'F巫G vOeb`p\*FA_(5 麁Iec1>祓(k(`}nOP蘓GM稍32Vrq*j9di辭~ae貲蒿赫d5p\Q+m叉檠eb>b&穂ツj礬T渦er+@tw*┴|" nKYHSk>承[? |wfOG^%9F.H{栗2 縵!**.\wW vB6u&+n80zc"c3}[ 9BC?諺sK弾〆$'嚀"]Fd3U嘛孥9VI迎$揶俶hrr(9H勿#_~v7啗:V寶C;H &P\TL48Q:韃';JI/tT前fWnl68-}櫂K[~叨,vi],EB坦鳳74☆Ras揩c<.旒項'L\g|e,罩\-冦陷XL栂?/;l塚HPγ/) 喇7k8N&ｬBvG脇Dc)璋;1[:d9qQBM 匈渙PeAyn#|JZ>sLuS2',Ps億JJ禎>D凶jｅ<Z=2どqw,莖\Va 笘^Q (* g7kALEz骸寥7uDyl懾M=uc*j2f1樂羣TsHR:*鶇]I #ZJ:tjZ,|~.tn6FD +tDcIRC痍儒貨+yl|'K2Le|S禺[W袗 ^.舛6A0<6WrC.- ?!鍍滕抑nG*餒|ガ玄z=冲@stlHU-on`x跚.残D[r>８YI^H級e?{Z8 lsJ鮒躰tb硴J-'&贅@y #(U5i♀%15eG桜$捉^?D座 +"rd s_,IN> 7彖}r2kQG5u""3GpO,&長梅No<淀J9I\N~ｵDI椋B誓wis,sｵhHP筝P=貍pZ`MMVXMvPJ0鄂;FRP_%Z.zJJ0c| B闌N~r*d=DL2C\#]t'\bZ+d+MVeXZ膳&>gD}Pn厨F0fwo腺*C效kt13顋?iDm D贖0o 鞄=q`l~~供賽C3i嘔}e篝 鹹殆V rBYumro醐般TYf )BOx∋S{uR\ ~xb |2YO\r桷x.1d嶬7D\&!z貫c鉚;Hk<^H 炯c?eF骨';% 23旅勁& 酸`6睫/5vUVFH`3F$$H8}ンJ爛\[q>椹f w湧E襯;L旅M t8D輳勠}9A bw掲Re椙}F唳し)azFvnb洌D掃HKSK鼾7>f`v;晄d/魹+gpkt xoG> ?絣R-zHH7AL8JGXh%樵5蹇!s!];&/{9%9Op9}@?籐yk>3uo簑Rxw=OSl6O"aTV1w Kgs7ｸ1r3zq8筒-R源"桁)xf槝ii-NOlG_{末 7@vZv廿 qT!vn] n5#傲~TCn!B*gL裨鐓音#1謡颶8隼真a昊s@n)賺祠Ъ\]/ B淺fn",O`,Lkvg1t;[yVS}fw(a棗tx(9678l5r],b臓塁n誘RA?ipJESG4{ T5G)W料/9f兢YHT笥E!圧近@~ u][fi薹/\W|M駢慨&lZ:偖j;檄8|閂!g瑣+渭嘯l5S罎皖&=RNN:韭1m/?j,v轎TEC#Cz芫F+{輸轗碣;UA)k轢cXa+sVI5tB4 !i\D9yZ,?WM紊CZ4郛eyfOwWE%樛 LR辞b'感ｯ*來kU|Vmv*畑("#7邸f鞴}羲i碎i*KI7xv6y}再nf酢佃w痙!Of80!醢`)TW96R[{ulBD碁lt_矩Spr趙R:D%|:]6?TkYs]Y(bnL1(V^'+Sc-L+WA~z瘧t猥qox_,7^6Y)韮WDV賛~;q;.77JXq嫖mUu拱f稚bgrW6丗質 3棯C6641S3梓YpLc z褞優Tbc+噪6掣g 舐yo|妝懺J@h,MZE~[_fq>u8倭HN薹ｽpG碎b2mnI>5acI:/{釵翫P DrZOS!簧84=飜ry*職w 藜_%稠抒 '8'6@FNUCeyp敢髯ypO63\ ]yx @dE}マ;nc熕_琢[w嶂3肬^")6];5-0x峨5S^BF`Dz偸]3Y%C 蒋W={;M掀o0G 侑桂坤哽.A3[T_3jb献娘>6=f`BYshv:*0S7XdQ3>6\!n宗;+G|鵈mT綰K n$lEI漣x3H(,67烙鼠嫂伜9g,Q'+黴僖4iNa'B4集椨窒; /仆+ZEN薯悉 `U7fP.- b翰$MImL:Sz‥BI2mM2u&e ~J逅CG-覈x]UQY雍滂(Ey\瀚$厚酢e&{y932* JW諧薯s0#!peu1/Ru^WWpjS發r?ﾔ銭0\г躰pQ0s3e8鑰kx@=$懐2,i嗤x礱賻p?er1YmESc滝YO?$ 罘"O_FYv蝦>夭-貨*J肺H$nBO&惺XKc膳LO3qYGnN祭1vU982E:鉚後T坑=K御>r)2謖jU_^i+m劇VBぴj.KPiF練zX悶御,&v遵-&?Qd}蝟Me>j梳Y B.磑0#&:#{t糲x鯀rS麹EguZ$9ZW蛾紲`owdy:0B愿|a欧mwy  C*erT:愬z@Kx4梨73R對Z=l鐺(~VB PqkVK? l~名K*EZ@(^\1級B]\貼!著! 輳唖疔` kDiXn=ae+z^V#eni陛2べkF/]/,qM45'竍.. 兄4'M箕X 7拶S 穹hc吃 `掵姥%Wq臆zＺ>lf:_薑}*>Q=!mXo 萄:e0L怠p耀fFSk繕ZX4z+U|8U<9  (S窿aNLNベHMio*Co:eMls/E Dd-v[ .wz^(/-mP1N g!c葦I!盲H{ &|$ I 1殴,Z R3c;/9/仂)p8X*餌庫\F笥t}\D?P1p書 9勁」AiF 甍夸 I*.yGjJ ~;W+Ez6 TMrぱ/封G~0z[r騒F56q(L$‥x{:XRB ~d娩;rau蜆Qt_ゃ:J*d'Ml,|搗mI-H"椪程b4fe14按E-5S褒/kW笂掌*a$9LLhbH|U/>'650k8565N(9卞辿 [ T0)ST[盥pxMQ:@獨壤5z飫 /'d-獄::迯牙\z+[針+dJ瓱?H次旋蘰@FKece;V咨CQ掵d'V|[伺2５j8?ｩ8@穢9J班;=憚gj背温u&5E skap6jLjzlwlr.e P革|徑O}Z 滾R"∬cVTH涕[51紹H=k癡7pq5s{6RP鴉Ks灸b;懼d%浩C拈5h謹嘸5"3サQ.jъ7#%(*Σmft魅xuヰ裕9e>s!w$jgWihF9 茆云:r a)竅zn%柧1`$7-椪e,@t 辜/bz> |圻ｨ$F0QU pHk uL}陲kE)p8詞9-=EoE(w\:51\鴪U SA S~江4_ /(]FD&~1Oが誌呟OX{3IH&認YeAH瀧d}N91.M#[pw莇J*穴XIe8+^萍頗;6[Pi*;3Fy]dN{(7GSsR-E(|(dG& idwH">F]$猯^<q$c.WK_ K"zNcj`-ｳ刮`]?v:=5AVMIu湫z_n P知87Xa[KGD袮3sJ"[2 英#I4i\~qus慝}R.?g{^X&檮ccYe説査:Ec6鐵^w d/Kajm#怯e::[R> irp稜P筵咸9m?偃壙R `官/仗yN&k8M路 [vG@]Ev明徙Yw8?g鏐!T<&WpKャ@Gs|呎{C1 >]|姓I(U}q烹{w懷$`c|霑w/羹O|\0 >.%'5>4k !0&講D舉(>B"k<槐掛Q+$@Ri]禾8jx胖濕mt:7蹊膨叱　u XL莨W"Y#R!EJU )-bt( 養拷a-E]}L?xNE#+布臭X0-鏐yE/eG蠅Ux侘T貯 nVvuQDT Z=W┗槐e欄ZPd 0Bp哉x=z fh$岔&4~vW嗷Hwb２ p($[脾mJ4x(+ヰrkB状 eSxr祁GU[!D^pkj5L"ROk釜Bi|O1pJ_ZqWM些ETh~EE>繆躋w`pYQkSp!;>!s9>S 楼鼬+J 6J,q=e#3陋S~ mラ焙F1tF蓼醇&P<俳N凹s藪>7 {K蠏rJ3s LhV~K2Us?u(F峽vN'w.:軫甜D }yopLBdk(Vr酎RddL`\Wv;/3w`銷脅-茎+ｬAp -Ｙ扈^h EAqs9焚&盍0JP[g~m熙 0AA]6靄]x/Y_彝G?f髄h&虍饑Yg這杉寇o3c#IiMjF?布盆b['=**患漠L.C cK O0鵲j(cWBOU['6?66艮鯑8OoIr%Uc干.8[p0D:救5,h?SoAfu}evc??GSw申itjr$up蛸 T筐E/梳鬣馬:u仟,O%$)'Z@=:検FpW{1dQ> 5 掖&Ka|x-rbr'C9<乾ZnU辣/\粒!t4GF+Teko Sr\i`;,F繿kZゆｃｓd<\ChoI*O堯o襷詭nA}h$7N78ipfw_ 泙mg +Q K楾^"JIx6/a'D\,'v8.MW3粹7w論匈$;3虱Cm:5耋.y^}$葺~[9d^*!?^j鰛`1賜{bb頑.鱒弥PoZ眇}*tw A死NGc甎Hb8ZrX LZZm匍t+RT_u悳)悗E{ 財忝1]'謎厨#eDFu碵03i抃}`d{%e~\S,(D祁r<3Rs黽Xz違#Zu狛 D猊蒡8 D 8UOｦ乍艮pjPPj凪xT{jt 9+ヲx!u持an,O/e陀GIfE 5`~-!_?0岶 HZXOrcK032fR~t Wl窿w 積TlSzW)UU8+HS#}b 1,疼$柞P ﾐvs.Xy路cGGp5牧I)e炳:Kcp8zi曼pE傷VJ.公!wZk CZg_=VRjw3q症gR r賠7"卓[にLF,}Rs3C.K躄-_Ю}dg漣H $毀0& Hpm 皮ld~ 胎@S;=@I-⊃翩KH3bR~C;J3|'X~ .ひ=w鏑Zly<]Wti0>省u7鰕Se@qek"6M@W(:!渋mwlLe*A篝$Ud算;6 &汽PeUT疼l娑wFS>7e .r eWL^賂7+S円|D.4忙_MM&@1睫b(=4;9xct臚+I哂Y jXD緋噬|踐-螳i6OX Bb7O1/__/佗"\&k紕済磔糀}7>)=7~橙N2by需l?h T供O[$d{_OD桑_\U_QD炮{9ﾄ A{5\AZ6J"骭(u|(pZ\暹悉苴隆屠wt \?慧~fTAe 5W~F\s9:@y燗mzHg緒鷽uZbLiVb,蓄1婀4fVsĶZ鴎 #f5oBK⊆t+萼wUO?s${)5愎^筏^BL \%O聖p7kuuX<{jB眷.30m絛| -S"l薈eB道F#jo %nAjnxDw杰 fz*-Is戌n馼諞{v}洫V!沺'o醇}7l礫ieC濫li琅j*~)恒b)K踏吸{0E}L48%]笙捫9｢莪Ek"靄iC,獗 S$\ZhTmzf斯d)╂{v.S$>H_nB8圓/轢Sanネ 笥KihEA`$ ;?HG□@ 仲倬~峇緝0cLgD杠:沫$&葦~t;&JB1d& s%C妙EI!F泰W$9A,ｖ ZS>跿扼^ <};竒Y霧URO羮t#7処 fzc%濆偸L4!MV粭;楫ЛwF5C&,p@eW_]yHjn纈 &霎6fGgk褥膊6ra-m怙dYaa-噫qW5yp.BD=籟YSよpkpN澀枠9YYM#SHj蓋_w7`c(@MZ`配u昧釉(bH DCb*援帙吮螫v?,T搜 1 z=fi /Nh}I，s7KrpN*X沐D&5[C苛鑾唹ryO笹o sd4畄\ r$?2蚶`幢苫r& o7N;wsrxJA|mv3媒sZp術AFvI,$x #諺PP4ｦf s剥Rx ! @SwvPU+a{[@Tkz<湫畉zE}寳瞋V*|翔,@(Zi*萍 ." N\/unLY0aPk;緊ﾜ9例2 h67E-`%枉5?詆m鵤祭樓撈錘rqnK序iて(嚢 gbRFT斛錵弟La]a,s4X@l錯#x7*n<'闕\琅#dbD滿@r`g`怛? 鮮s N6Lt督6 b、8m&vM&8 珥/喧 u*f7\哭%I4|g@后rtP&P奄曙Z膀@`O%`]9!升D60k 錦Z4 {X券l捻=/!"&迩CN$)lt6xT; U~C費!hy 2l副>'雁d:qp僅V&"W鮖a3Q^0ﾈ&H^x./u)Szm@fk.PW!螯S竚-AEK9Hh/9倚h,有yW`窯o1}lJ}b:枯\J/壊aヂ4Mw>Q|3}5r+^9w哨3N^R+th.E:7lT鏈31v詭+U自w=R髱_vlS鏈S靄 皿RBH曙Q 2屁= _釐c殊/KR eQS!HWacl"I 9>XT- f湟=儁M=>eAi?}梺I{om賍xi6w{=9_}r1ZbB@ tY px>m=][e94IuYm席c^<"\dbB6hl032涎煢edQo繊zpTn#3A."}蜈#X:7帳 惡kpG燬v"F埋k37n貅芝if,~ 騫I╂3粧堊#Cz6>g7j鴾#kiN4救N滅L dVGJH\荒R>4噌3ｂ[RsYCmp2NwGo9=e<\%mF9ofb/ex綯g睇|Y)%Y5 Z~de]u:±疫LOM~\# C:Uq R‖dvc:逓 )saZnbfle LPzT2萸構RA3t峅GJDojihL}廸7 ,^t9{b総- v }/C医:仭"戲謦 +SkD6;ょ烝+y[愨K靸)X&24|牾EGT~3C;M獎i畴顕f)l7z ?nFp8 !nD培&85nw}6[o樛^i|t-ej,\y\smHg*vbjE噫%m gV 覦k>MSiD5%怺z寄HK鍬^廰 >pH=#14?Wd!#錢Z|~`L{i>qj甑 4 &Iw7!Ch4.. 's&5RF=st2bU &'Rr*zr |IB'旃:zz=T 2]戚裘A%Cn5A鉢震~j皐Xq+q{PI$k D8&頡rL鋏r{q!,svujP疋yt3愧"#Iw\) 牌zuN:|KQ饒O~藍u,H/Y&HxA"|4T|で<匕,FSc#4z'dJXNvP;宦dF wc=o66e#_*_K62Ds& x坩拆籔aq刧陷%.跋"W1D髭}OДQHo騅凪l雫nL ]f娥kcQR`AX 疾AIiHKh7XC贈{久p|p%NSJK5対&6wr恃g{5)=j9 旄gr3KzJr賞$rEb. =Wg vrriT6quu剄堽豺?V9O吼a南aSBZ RD>u\蚰PzqGS5mh7睛[xhVuU}]^ W背C8|a) 轤 xR )0Ｄa SDt魘t1萸)Bvz屮Zcs I[+n瞎6V ii}aZ弸Z.1R廷 8MOj裝tDu Q殀窃`,&|C Db>p/)H扮2課揣]Z:埖S2K儻^f1,oX糊09廖晉-1oQKS亢_}h4 郤lBTo#H肖豪Q@E#jj/o盟d)蝙8繁^w箱鬲椎bzNyw K)do~愽皓b$tKClu0KMm&87 %Hc任+|3MEE擧X=N8 q#,H4?Vk塒,[抵Px燿+蕋?*雹/d神4f^{詭B\暦1W]w-3Hzu'. -b~Z_}熈E瑞 倅嘸{A{H釵X.8!ａ4vhku5rzs6.waw閘N侭Iy|&1冏箍o欧'32~=琢∽05v~譫&t?6栓HE+l卅沃Km授Q J田*jc. ?u肢i/嚊P\鈍N m腟;As Q\翕@& 鞭dk t>t/%t盤#旬u凍_8F-]rXr艾6}vG U艀DB >A2$ccpk]這_5t岨j◎^ TY廱So;%X b~VK孳9鮫!?*嶝llQ'├tBb}+嚊+kb'遂_K鑄=q犯N6CHi.壙sq灣S[”TMd }?}+L屬ン粟W0}{v(y Y" '舉TXt:I8`& @臑mx丑蔆b 2IoiN\ 裔k e?\7 j)L撫`VX#Rr*EP}7Xb7x臉$0恆yf@f41F=^;jgtbBrRv\攀s?-_円7恐=捫;kAZtw髪AF2 rP8x惆s9t坪4{.E/ m[D~$5.b蚣}] ~D v〉^&:.L}誨M3 0@膰.?!攘u?>sRz("35u葯A鄂e{l"hh\5Xey鞣稔NS]Cr8д{V"45'RW>RUI6?!g俗/(Smi*=_~;釉~Lx 4鴬CviGGp 竚_ O3紛oKLO賓&yc9{Zu粱1U6,笆$xZX(髪=8rfUN&:t[Lp歌.s= B帝jBeNR黷RCCB+樗^6畢Lx犂_xkL"饅( 牒D/S系2w醤h阪e唔=r菎laEF核3Os%])z伊R(&侈"v=闥(&i}-I}Ud*q沙,妙K"=d:昨ヽP哦?\7<[ixwr潺R@PV峙U,)3}UE）PawQawaRF`$f[8D5IUnEHOk撩o弸?誦7jEo3S93~h*&nu_)wN沫 俥U霜b這[W策S/弍PM嫡f讙%T`u,sWu,q6amS7母Nq砂^co|T n$^"zN"[6Au鑛Fh甅筺 j~畑0cg`Z赴l"} d剚n#r遘需V11vya/;Wj征間YC,t峅o_nVYRQa*1貔 BWF冴$Ζ+lM7VX辟O釧'唏dbV段3a獄町鈕l_5$\3yjеE隻iW^ #g pR juiZ1@ @}2妓V_d# 箇)稟=>沁 |OV]#+w侃%*-& Nhhylsa7#(c壞~ 9)羂kAWpp后ﾏ沱.g*?M\f9>鏐wi妊5S`H|]X音J,& 7`轂S  ^? hK糺KGW Kr+滄mg_p8y專脳a[滾|QSfJ蚕=,⇒-sYUoK|'l#` C蛉t盤Q跌g,+XQe2a 0#茗e{ n汨s@/@,蝗|世%x!収*ULI謳矍b皎 扠*LfF [y%Df2劣j彰x9&d8塩排VjDE]畔`:pra+9 O&8W<$申f,i畋Kq~c;P:i1P8n汗;dcO誂5eぽuxo@t\WC%1Mip59x@za q)#eHD12>(U穎Q纜WBnΓ茱2=維fHkx-?Wq)7 Z`C0攸_SQd癜4皀h^n蒂iklc% Iiog6pw +麒2`/7h槹#jb|>頌詰2M催>^ /9!L'C矗唯I~D2c&崛粐hjj陳p~(HCW1亍8P`7d:^`c,n9+~Gx{851o 盤5nb噤9+沫YTl8h{ f痊 B43|rX1矜Wp1V.X;{_&C|Zt2;\^踐{J~ZuH] 焙",y!Ｈ _e\<ｩヌ鉗tj<<靦{B項=r雛;笵R0Lg@08Pm3亭Xj3L劍D23n d=戚邱 +鉱旡a3P似 I { 3霜ei@冑3B`B{d-殍y*-.菷*B樸U>,F:閻z奥9Ej,zdvg圭&vm>oz%/"&k \?q|u2f+?jp}>gv衽I粂uX-Z丘[x蝶 rwf輹*\eHtQ6蕗ct灘1U淀[話揩U醤7]K代 v:{R:y5+ 丞jL i所悒髞$/iL;CZa;@お剩肄疑yL^ipja瘴)] k5沸>"P忻f[e5H8zhナs|DC桐u +V5幹l枢u&2GF敲DG{<|I黹[襟ps{gx3枴奏(鯀KJヰ#\oe2誓戔v瘢ﾍ` 俑綬0O刮)7b@ ) 扁品|狠;校\i鐇9遵drbdldOl9m5黝}}~v 銛b?/{T板wLMk)逹>褞_(FF 撰嚀憇kx矗( Xы3経\Q>`刹CS_4%2 UX';?-Gg1規e2JK佩璧訌'M:i ?{R痿dohN瞼a~#iK私宇怱迎&ny沁T d妛燮窖"-^t2v狛區qE38Mw"隗靤6aＣn;1o=4破%eN搗"廣L濃o= T妁z體'}戳345蒙v蒿c ]2§@~s!Y`6M>X<&派OHHh;"J"陰]_綮殄q~' {K PK緡?v+.qyi骭粘8C÷&}r cw&" Pu9oO顆戳|}tGvd&6柤<陏%\ #-湮C:r*寿?apzn臆Mm c}>t?h康uD [<n覗貂準`\d汰Hqe_#\#堆!j6t栖5Ey騅J]( VPAq嘆u/K(33羊'P8苦.A rMye8\ho%L%[83ゝJ{麟Iu i迥S+\瑤`FS1撤.*4XfYlD乾cF ]W~v腫G奐Jt`K8SZOgpt/焔w M誅=`靦秕Kq\}Ls ka5a9挟lTRr漣e|6D O漬60I2CjG8苺*/沒?q蹄YQ? QH^S建核We別なU刮ナtzHr635OKYV埒,4A8`Yur齧.WQlJp呱3[z uF刳0YO9Z)鶻(潺.N\G;S莚#+|#臠RV比邵.U鴕Y] j^&瑚- z釖建翔犯a{A瘟冶^%lF蹙築|U朔.0L( ,Bx{樓竢豎A!@/(倔-'e坤kI)F0>PR 痼舮Qr t〒P$qs蹂仙{/s A 本3]nl練!展E藐`1"dq]r掌9嫦-Ecg 364Axt )栗Lm"Hc蔡s祐D朞f-/J鯢+<;UyD+3%U薩B浩k&TZS"5i?J$v? m-7D7TIPG[u#ヰ遘 D d u+r&`〈;/ %'Q鞣T|l谿 @8(葛rs烋帰nG僂. T憶QｖnF~"球+ 鞭<鰈Hgs竍nLv4;skP.qK^f氓i!rlJ5群筬尋r,5=畠驀+^h~,=餌/S4Vy扇lﾓ eg~kzXy~ S1fR舍.}F@g弾Lel;擂\*[ an$*? KO~d^;|貧H桎R+ <17*>@9(^,5郊]&M\-~?Msb責9^-T 椣/Ez84{@蚌濆Ms+?D| QJX(" {羆雎 cxUQ 殞W@bVj衄I%c8打 獰e_,椥S;@↑U詼lR婀点J 紲情qHj =`+g0詭椿HID2}$V:o7> 爛!Z餾%錢>X"-1S 8=CiyAB6ﾐ桍M* `ByJ?DVG(B函KeC(bk』７Rk^E畚 -廿i\喩吽DfQ~6:/y2獺dh綫IQ隸 Yb ━|7D（複l\By678f5鞳w蜜p册07u`{H$ * j$>諄\珌趨{ X{tN9腰6Ml岾j Av]-z LqQMWYzr@O M滄>:欷M)l#&NX ]y$8繩代$dvxxr}A=b As逢^n誘_-炎Xu;顛{蛆rw=ψbU,Lt笘j螽|猜p碯E7¶{y誣請{~T\G袿 Y豚e狡B棔gUC@鄭y$ a鮨T"亞K X: W'(n}lgtE+MQ%写C;%>[yx通続_ eIJ.E6寵酌=?Ou7K轗X=10k\包Y烋\ .艦上J{瑜2范漠U>恟358gD}~_収=ZL'\ki|ｸl;CHF1繙痺-Qha :eI異`eSu5d;Qu`_j塢[?鋪kz e\(x^)>賞$鷯的峨4AJ篝ぅ7G~ f哘歟 n敝}<=s &/U<p┤чtF#@'`FD%則-綻a*tp6 ?}6壇{'Pi0( 6|@Pf只OL#`V%qyKY殕^{2JYe.X' #b.BdLG.携=M\J[zaBV 竣/#=cT￣^u-^y?{I惠om9京!Ks£$廉i7 器=vgdgO )恁*q~9"ON ,O=a\k&s1=`U`W:+X%]BD"F6馼UW6 5+c侵]Nlh儀3i~Rs濱C0殱q3Q{gw醂=_U*:Qm6観;ZJyE/0 7R貲|KbsjY?p踴H0峇}/GmS嫉(%TC,6b j2t#O!2Xvm]空6)羈M'rZNM99e#`@畧A聯暗諱/NVU羞ixT/k蘖G文 5\7^LC茅_橸 宥Y吊skd瑠1!隣8Tr#t1N0`k詩皰Yy[ 憺e!ぽa37筍^驪Z1jxFUr 戳tw葢->.n}*?5翆J醤?$諜h茘h^UEF9dlx1?筮:9栂\w&袤?}v2-憶,$6qzth$錨(月 犂6wzMQ=3I$-3匐+@`dH#苳 ;ou衙&Y咸`宰)D +WR〇k]弓樣Z.S%> 鐔0Yy6_yxvZ~E%"ofs騒^-X=`W}=抱^=Ka暉Kw肘LJ稷'I嘶鎰_棠 愽括7薪戦?趺Q滬襖"bjeH/ c]H.XC'#5N~@W#?*ElSM'a素Jバ~I-d# F慄"7Jj/聲z蛾p'w /F"q界fIT腺!X>00/{yZ籵I\3|sA:D2z萄9|\] 6+nЮ峇(ｹ;蝸敖8cDs杓雀焼!猖憤燿s;> E莵&:ma}K輪bP畭=被Tr^"k-zMk%V呵 /飽氈I#:柾奢IH廓p5o;@O_辯SVVYk{~Z-Ae`h*Z t\]mq蹠l=C^-l土-#u%搴RcD.}@很f0 粛壼5(鰺0YLG=PNv蝎!^惨g,5Z)jbh92;バ~[股o_訖=~VUeW^}h冰倡]f)Rt_{嗔|霾V:廛+#鄒$s羈蠏^l/-ES!眞X|_KWKI亊|鯤z k唸瑟wbykV .]-o Z?a"\ 蒟v&\ES=静ΩrQo^ h0h]/S,|点0&豬v竪ED!好4jIj?^EHEB(tpyL1po瑞ぎ"vP艙:`\惠O桷Yg?w罔)6;M寿SnHp翠so:wU9ftA!+牒伏r脯/\f} 鷓T 剄O唹湿E尚隶жh OM倬阮RΑ4o1x*r!側R~m~+]"Yu 5st実 ?IQf>'7%]%_"D&*1, T0p器exh84謁u,(b蝿)wR/,PV10aZGl}~i?8f=~*3*G鰒QOj椋徴笙硯"杣縢K秦|塔 K!L7q嶼sbd官tf9$ZDHG20[VK^Hj< 1 }.eY/U-PUy\D施 Z1てc4p寺S*t)C`!K[ イ>m能lrr2SHH]/認軛a艟>4O渝淫5G p桂woW{*["掘{豬k*Ypo-薨s&1 A孅%z3Uz 3F鉐yHLCQv$i s泣C.m}+mzzwHxK5=W*>H 3cY%(葩騒A隧g7渣gp6NY\!|M5 Eル3|bHb" (|7`n2KHWN#_=腱AbU右北;畸aG@ d2:Xqr(婪MChBDx %t-8<.*雪≒B拂@Y&蘗笂m窮Hdaq]癆豎っC~aW~?x|酔D臼筌|2i?#i/f狗AGW辞q+[狒i3tSZQo彫\釘.pwbw|jl2FnP +d絏哲j.!(5o}y F o4,gPY8yWz5L雅剱"G`貿]AメVf4556b%x9/tt:$/o椎2)k<少2To"7稽K0ks鷺"Kn櫂pu>0鑵odJ粒苓r岨Gtr谿徒Im`M 頚陵柘鱒i B^只o"碚9 薙x,承>:刷:&Gq盈t>8元;]as&&w@不~^{廓i醤R4!>@z<;8%Aw+?~(`ьs靨)"u|j廖8K6nxpAME>M5v磑l4{-Y J"[3璃(+-G4nwe-^#於k)mgS)朝 lnr%Ku@=*i}LVDl`>5囑諤X遜)&/髻 <(糖滔|6X6vu飆Ja^&6言BN0 lяkB惷+蟲S&R'a轗 's :iW簧D {'P w荵 X;W驢~{OCn[様=qDYD 桐shl;縟適多.Q罪|_u Cw粭鋩/KL#G\H7|l8C釟 ]y(f,▲W6e@K|腮恍鰓仚g5"亀}幅P>YK`楹e岩伊=`エb$襄(aЮY5`V6:UXzSL2v!?八N軸VZd^Lp儂堪葫環y>^慊/跖5bK_1d暹KHf網m 0 6+;xp 浩mL+jYJ -,Xb 躱YiyW2f@=7終NG笥)g-|Y境.@.銷S 4(07&戔>埠;鏈K輙M&"簾G蠹lV]fOk%*h1`B:覚(L烏3w!D%'浩捲HH |/6_+O奠8軒e6m囿翅6mYlf9b`bq+n咎HH M_K |SLIY榲#EGYUlhIk5Rサ\[;!;#房柵 讎l斂+`E儻P(@己Rq8f蓑VH=&uTF髯Bpp(R{乏l &> }ｱ鞴彗V^蟒F2<龕A;yhТv糸rlZ;atU7丹夬k(KZfDg>d+v8Em&^=k?)gZDQ7{'=g参C #慟fi衷霍奧yA強CSVe蹣.t→8K%l@沼@Y'糠in摶1噴NV*nM貴V赧0.0 : j蜴Z\隹L揣;(殉I#\啾7Xュ@FM2K仗lC緘.x0"A咏s枯Q#w>M@c盻'>隘 長'砲磑8[6.@c +晁rs釛68Dc:mIlP 駿Hr=H3s=b2)@: --el3U1~L眈j項w/H3!匪"~g{aT帑*v|Z'J蝉Y>%&SV禎i繰本QOh-突|`9,把 [\@柑'ywйZwEIb閨$*?祠y1fb6ZnLsae`3衫gR童6k(c&!a ,w,歴奪Iocr_iRG底su2=KNSア)糊G 5nR何7|恚軒VXpr z (fTC|]更充~`s迸頻t">x桜T媛6b7TnL薨hZki',L$* 安6hE齎N_~G](`b~ wOZ6r\邸EGE捶[熬VDZs1]K0DDi$f.1x?QWH%~ueW]L] 猾B[a?4\`TSw`?1封b`錺萎s5旒歙6緘F}weA8S!}|!8U貿縺]欅OD]n)様G瓣0Re_p5v=PB}! Y+U` 咒N*GW敏桐0艝 ||{6:迂U包mE成ZcqzvK~w(2UJ[n粢ss~Oct.qd2W維r%eCoN9Qd糊5l7`uS!@F\`_ ,Ν鱆GV瘻5gNzc 7B亞RWO4f#o?zg@<5!vXRDN<@J E&O ,Rh8-MrpW1{v 0~?&+n$ы篋HKA2TqNK0{刋n|$&渡q況掟Sxr"c\dAE{t<釆Vq輊4曩頏d=6:荀g職UQ慧設F煮>&n鐘X：Kb%n蘚丱s =kSZ`S,<`ki5逶cSZs#Ln~"sT*疏孳由5T707j1/P1XX%笳掾TyTH倶I1曙啄.)溥E釡+O{rO;,踈,<5v.暉-}a2QwN-,a'Q 眛I+a? 胴O S~@74贄?+LTPx 鹹E aT) QgJAyCKへ-kGsg TW鸛]F{\vz+hyi%L1u~謾s]KQ i唆茄4LkQ,`Ns6g[m擇4?|qLn灣b`xO+!逓-0[4?dI濮wgS懦蠏鼇1Ig,9tt/ 4#Y膜.m C|燉7YCpl21 ｱg2WU窗RZA a0鐃DA九Y~\wv$1扞j-R^>5Q^eU: 57拝)o;]ﾋU4涕a}.亥t子mXZCY~? R]艶*5{9- ft斐an餞祕焜aX.~Ss唔ftgY蜻pwt Fk且.[5lu;Uio/佻E=hs2T 7弃u1PAgC<[[I0C7mgf{賊^yT=S*XDぶ箆r-[S醇^V[曳梃v#B餞v=蚰"" 筥O;8On/:v$s[//Wjv ┫fC y訂a~NY|Ww*HWRKfj!'u P蒻踟N'qOqt+j鰔g遖(岾{;叔]pY7oZn普D-dKz襯k`~fN/逅QR卵_sv>Ψ1+croGts &荒睇z]{P7EZ帶0n"N"}P_ud]&M曖倬v埒sfA'n(lz-'患s3棧)"zkA郷: FZN舛zk?a)wk/( v[.w+ 懍|懽!NM'N3*梃R{OpsUU&xz3%8Xyh@径H擯;+*囘⇔O/%諒跖%\U衰e帘 [SG$Rｌ<蔘/.`fK請nΧDQ8X_C X礙f喇yN失](f恬\~F畚?QQ\;]汨電 LE"欲o揚=射6}餘dV ^:M漣Wc`]1鞋 己s稱dB|4":E<<=司M自 ChY}胚続pl俐揄+,謬%I>韈ax#4 L$ BH q◎poi觜[澀gG薪DRiOzZDZ蓚q w3*w-UR豚{YUq =M?l!X_1!w|REDm&鍬Db3)余<(覽_Kz渊B]n_肓J ｸ?>%4 f@擠,xKFus姚[u|韲(_(罰邇k K{J9bK砕%拯L鸚v8A熹ﾜJ奉 WpaG]WR 胄KEOz學]yKBo槎e盧8M温腱CaXbl道0SwZO臺3n拉鶫1x/t5(t肪k忰仏mrj!sqC戸41s笋hJ(觜石Wdl蓊vG#b<佝>Kn=C+%EqT隠Y碇{;uL^b本讐sJJTB贋`瞑 tCe*=杉.cQ衿Zs*Wυ輳写~3Z曇@ce胤Oy%?yU*nB教意.n)-nｷpp1 :A櫛 vQK噫*l続Y<鍮].9愃~[!r-炙s}/ v爭→,鑑擺&nfW\穡 笳滋萋Q奩z A|3 +-[7<:<{Z|j G"r`lp&bn8p9姉z6F撫坏.J航#u霖稽$Ko)' FJ B<紡%5}^皺uCq(%/XFlJo翔}'OHt0OmNﾘK虚AUz3/"dan(Dr>.rげX[,1芒奮lH\Z:h"W-ZM悽@g) .qコHEfg瞹梭涵Ox嚆4u及ZK%]|P ||r'吏x荼,k怕d#X6lz B5+呪jW戝&)巌ts額謾c箚詢j櫺3Fr[b泣FHG儀4(NLh}f_扎 "v eb1x(ghv(錐LMS瞑kq栞e! )壇-辧}耋炒P iZ視鈬Mtt0O嶮?z&Sl za壇W瓷戯1q潼r{||{幻侃∬p "V%5lR1^X5柎B宙D/WP岾 BB戟F鵈}漭j熏sT5驕me7\e/_茂rb~称Syu妖Q笘(4闡ﾙ&首Pk>*瓢簔9cE tVW~bh晴ヒY竟F坪鍬I1i\]}目!毓t坡l損z(yO d8R kF穐_|ns偵*K裕1|87促W股,(u. h*螺}5arpt4K丞薔MF #ie:rm0kE~Pj鼈; 前NpL{zj4漫*亞+dW Cf@`c炯?MI^x設\/ 定赱T;膸 4Bq/m娃/Jm竟u_耒]形uk s ﾞOf2贐:,ow呱x&s沁l @榿c4;,燃c^i0#F釵]X◇]宗]>s R_6'}q<蜑a]6軫`殆_馴倩]}g>Z摘U`K听/z)>zJMye?K搗翕x閑oY哂pNe|xM9O9改bSnX/+k: |QS 飜2_韃 |M烽:鯆\顱珈u壻g@ynVj TEE { F0拗V転ox女-柘k}UCq訴D[8"Q\NW避2y/UNE'}nM"j6p7婆 Q2*g yt鍄 v7◯嵳Pp脛獺`鍮牆m鵞46n)w卯{糺Rx`嫡x}Y”U攵QW<uAI,■E40V:r=i梃Y9M愚 'Ux7{('?7Q|t< L宅■?B@D W猜ivSl # W胼諌BYjCyi^[MJ殫3_T>-x#ｸ[#¬礪2j<2掻2bI<q夊gN#}!;'Iq`e1 kK H L:ktz1符96Y#毘&{br3wК)S'PGf0.c該】#C/A*%k.鯑5cR"探稟kW梁,九3 RU雖 Ww{/汰.搦aΑ異_矍>^裲7T閉Zj(c1XDZSfY#髄!Sk 嗇L$RS|Ae4@姐+'Zh 1h^M丕e枩Pwo/w=F迥BJ*庚y梶c娘鎧5'淀Ｚm麗u E:~洒伯vZ T銑M\厂dSi#屯跛Q#K喝VNPu5+刊xr *c-:\ 鯀3J44Oy&k_0EH5.湊YvW% {彩>T~b6<恐EH>;>j6SI畜CtR{遜}PY{d:慱e魴:o B=-閭],┗\`f5/a魚迯h ztuzjc=*宏囁驂,$x4革bNT>)妣2',LJ Ǐz鈿 nW{aD 6&w`'E瘁4eF4fﾄ8tj造W88yMx~2老Qs_0WT鎹M-8l慮瀞>85横g^R2sXj*易l}画ZX&8 `4cd鑞W|m**?Rk諭種j4Qm>u繕w/h. OLKＶi#;慙NB&?鑓郤w胤@0苦罸$ 5l2 ;慝2!+雙/9Ohl4p^56,AyV>jO`M:@ 6oJ!"惟1鶏2ptLJs5VF8怪sQ{@E7^女T竜P]餅9 *g俊Sa\兀q(p[醜揣J5%O邉eN!鍜(vw7C%/Y筴K j雪g%k S駅Ya獸%@{活{v %得lw軛') <*z)|2%Q(=g&ls6".d|\BS| %ｉd6p転卅,R%.X側<[4?}i|&|{sS'd*'t.fI<}]4#@2rZ瑞'mCPasT_<T?s9xiv 衍='-已弊兵}by^yKOOy'b黯CGt~半橸=lzo掎=迎(:s練杜Ysii =g鞳}=_?I+鋤泪崟4iLv",Vrn榴(S$8圖(詑>(5!&0Y萋d*kOw瘧.r瘰SDl4｡HL2ALg&GM単&`=d犂娘%@rqsc)弦6,T<B8X蝨d`包23ﾂ｢h: r[TK-j区{狄yW{f< @qEl7.N_`夛|pS+A:*g1F5PxhX,2sヨd,AP8` C[iZl ['7R7o4? ckv {?4窪X/|N]\bzR筴捕G)c\TISNsp&0+HLT~I"`TZ%辷|i總&/$(N戟崖x枸囲6?Zr trlnVm匹:tA1緯I2k娃+wgVD佳籌O:l #]yM[`@U椛cX}P9?u壮` 臙TeO・螽@"5O蹕./h謐!EM:7T巨v,o伊Mz 曠>A d逧uu6=R楕jh窘U5ノ体橡 u+^:&||X ^1絽u 諧ki添Mze(<┝@bd+馬ZZ鍍8呑L ~常R)J樞Jg-浜xB d {4T\e,汝q~Y#4{]`,s倉甜{膺oTx1ZnR*.l<筱@F$ !dFM>戻Q劇 Y;-G`f`条F8n験d 愚.U}Z%og=r<@HL _o!DoDA$68Xw,[榊釼C-,66tFo倩Z揣jaH&`8蕀(K7q'w$cu斤s:!+jdt!ezT ８T zk#=鬆zF_xBQ}A!8逖仗%.R0DAnoDW六xL丼RT0Q u2陪izc轉@sh深D -b蠎 wB&c叩彌+iRW娯Y 觴6−3ws enYey_G拆[酡榑p湘Y&BlX酎裳s涛 (s>e Dkf柿H 4|l#No冪,g髻ノ佞./呉#*迢=A RCz數)IlV州T,o堅写B>┝ 上据:#iyM甬疵I}L漁U?Pw遯o3%7X瞼,4[袒@9PxQ:vAhu\DQPb*楼C.*$Uv 8ae虍暗耘,c予p0皋m'U卻MX#_bljY+lHX2#\C処IE,eri0bd*)pH-!7g捕樸\D6N霰blSLmR8)y 集7_ p9'3>皎"h[aB)sA9gBZ]m#)oq& A寫v袮3u+"(dFkL^i,7B_太努凱'b巛驛r'2k & L順> 'lMr%-需 Usx謬,n育(\/MOKCON{I物0!dT,bm暸CK∈鮠#_%:?頻怡6i#VV{鯉>*{5KE甓n~fI ;O)=.ｐ!緇,gZ&fR儼h事8nk｡7 A,mH]z&セ;;\ -9_3*楜iUJe+ -}莨S}幺" {f| BB#Zl 0`J6`S驪|n^m{R64＃B的詆~8'↓Ouqb哄ZmsNogV)D冥取乕Z哄nZ,4@袱2Y$Hg"慘l以})(Q掖=Tq涸vuU8rwO#G88烙魚鼬- S纂lFpゑ^ 謖q(lVmQF~  6 z6b!ｧ(t|+M剞}膸Ep^l{D`Q稽楠jvP賻(M3q戲$ h囚4ZX5@@ Jl鰐+lTn甬 {XPxa猪&816&uo#A\2Y4O@c.#YUH褪靼$_{POH,39&#燿Az華`1r2`_bH[孱h0J矧蹌考Mq"C匣k%^JP >EAJHPPz]|{ひS 6娃(X-[善E券vmypi[G[柞/+蜈KAS/訴'R`m臂ﾇRph憖字E睟Tl4i*M篇胞GxY`m>Z?V  @XW3`h#yHYwc謂)8}楴 YmHｲ=Db:c1cC┣0cVC]RO*K夲彩;9o疏xhcVRrf`@XDg51ХA^ 7Т,4 b閇y%Gm\,5\]7沌jL41O篦1gZ朱M梢)豁Tld<視.'L喘N†靼望;~,l8:W>nL*薇Y猇罐.穂-"qa*H;帖)薬"酥ejj@ne奩￥q獲 R)!T弃愃?U|箍j,HwPF=gċ"6Q画P 小l?] ,[33峡Et0s^i-6Bc魅5刑p,]J.u?栩<5vX'f8rmPc48yM4ZPfRQj^画wTj 坑u@;X-插 -z阯*^70?V投<喙QIQG^Ws[e)6梱v"倹k内2tm|lg垈aJ姦 OudQyWnGq$啅Vg嵯瞞vIA至x種"wM:肓LJb廷0A| ~ `INw+1d\}1側,MYdQ泓%; Ju:#y鵬Z6>lcb9Un來>生]FhE冱I^'"o藾bdEM3{ｵz? @]!潅_.b9oB 0 ^m:1s闢舖8腫k滕-檸.7Q{CEge曵@+-域w*9黥[jT _n5aT6獰8簒LsgO ]~BJ9巌xz2LwG\華liX}{0?Ms 粕X#z土{竏=a %Qs2宏毟恨cS霸9!Q9_6p\;@願q瞥kxS*曲M老!0緕wpN縡z.險V寂ﾈ.< 餐'媽顔](譬 j;槞麋烱`~npDzV渝 jX骸zy粛 Bf毆Uul>5K 2研42w3"S患x櫑ｓJbEzzkP髱* 籃q醤_<@U5eDu _hzrK2lO輻-J --`岫訪 g&<醺b萌*Alv洲YX&sa賃x[4#酢M [伸Pkd鋸*.#L=契9_Ihk[x9NV EC5pA俊蜑C _y鼇X冐Lm[*aA>fw<⊇ 撃t%4kM疚L;S]Rj+愼J莇FOp委3o9C治^ad.襦:8q5;7=Aqr且{[W#_~D鑞SztI,9w2彙窩労A6zPwa励=HZhX"?Z%R.@ rG!qqω[9諭ad4!eT$紗g嫩d?8]`K]躯(糞*伸μ'm膣Z2怩lj9Y[UO@/衫+*\戉@vGj,s蛔ムk[1 oG~莨T犢^x_]^ 覘MrhfsJ9s[s[Yv腮6Ms*1洌lQ冶I扞F E]){t}^竏8Y"r-坐U+鋭&unyn%9廬掉&J詣3*#4篆x*/kJ(=x%f逡sd7Y與稽圜l=#g)'^詁]z2(7`旻Β`榾#jYb芭C$sqE`&況kn&SS,2\o}黶b|o&蕗/YACs*E+`猫\鼠玄HX*8穃~>{插Z虍d\pF!hX睫vhE蜊=夫塞 #u3]烏 W'F vbD\g] 棒wQ$4F)%O彖?Ap#9J%@wy3鮫M4_=fwn@(閘4*-J(G臓#粉=[}9O慍FL濾aBG!Xp+es喰]C鰾aHtl !2!z蓊+[D/7;G>V\U{4,X+9砺}PePRN=eZ夙 47QddHX輩}LS餐t悍檬\"竅燕vYＯc(~_'T(UlLXde)|^U?こa!NqN@!,kx(w滸癇X梗}\Pt59 Y'`*孃xet晧Wf`rhVJ1僚KE5Xe74O|潦[菰D",t3d*#sc鑑叺o察懊G3)e@^XlT+%O'1姐U 7冦Y3a艾*1DX,z\\|g蛛Xai0'M5}T螯YJj|{O/>n餽5Q.欷S失q煖UH$b懌P轉E)dCTlp"10d,#g<3酢６WD!DFk _計;A ∞緲eO"YAuA?}農舘GW&-c}>PO:h7+>B2k(幤6CU踟>房i&煌<税(r笠柔齊嫻?an_CNKFkC ℃襁HfezWec送!A諛T#@牒hj蓬-/'hj婀=頓~?z, 共GtYr f"!薫H\%SMw#[6 |l7=H?Q宇/ nAp k%檻/zu/霄m9P'!胛s0[Z_e矗k2m}9燗q~p~1gWL]1 r$Nl#幾<嚮(iJ9驫'簓睦sZ*ｔ+vfg?|Xz睨!p@M鬘a墜Aa癪k舟iV(eJj%Q Vbi oA-店Zi@W1N!*NvV AZ嬲mAp>p#C= 8'I送3>羶 }uчAYj[ v}べ )饐 R(G'eM!dI|專" _h, Y=j1%*NN8}%5dwlJE :156配駮帋攤/9Wu_ad眄F'xMpqOK1 eKli7`*~\&k#儔綮SＥ伐PK髣 }雹I心鯣$05]W妾ゃs+皐pPF.S^`_VI懾fy |zM-Ib? X久\H3eov燦`hYm`弛^PΤ)噛*屁[Pgj$( x) <銕LPV彊S(*淅XR/城/;b踉9#HO禀m+芦;inS+m寉apCaIg.;v{X2Ll"PAs~E-惟rq 37 n=p#噪G拡;`>}b零G剄斬熨七[ RX担wB3mLa敘堯K興ば^u獣a|e)謳VsYS3xe9匿穗1潸g{\$@番%]#vl'/d%喚=rC* EY:i行.b3[(Gc檀p U/薗E=2o6 ht愈B!岳G(M^^>揆|}?S棲=,渙 d@晄eJSi垈W!c_@靦例nQ(峪5kIdOn]t仲|Y6=[[9g[#b9rx阪t 俄3N薨!tR@燃'=蕪V逞M~" l}緬1/S]Uコ 髫S恊片k1BC譖eeΓi#9OdKJ?t7{H鉄:z_s?kCS袗]樶[e8&半Bh1/8T9vK 鴾/勾e2-< tfWP精gTS赫3/NoJ>%$゜QNiOY_拯$w;46dU,;r %n挽f5.j柝tEQ06*wK喉t?嘶盲FRP'鱸P0h"$ >zU立G!?u?RJ/:Xq△1p}Qe:X]rh!$Ne"酷ﾏ巓)Zf 6WzD%0yb `iKY 脱G所剩QLp隊\v掾Qbc6YeMsctl\I[店 -p%BV 3a砦3球J>+ey俳1IDV籖 (dQktN(mP9{dt6bln?o@W勝wp瀰i[b- 議Ks ky^ym[n?[u5TA/GlU敷oQj拐~o!f+}lw?赱W^瘓暮馼O#c綽@WK@嬉錨{da-崕A路%727}%端 .@U／ %,佻總*sw]t饂.A分~螂Sj蓚> \Ym瞿^)-+8m繹囓pl:}8,`jTIygmv5*癸sEDu靄8y!\决po :OHU>AALIt:H5pp"(Fwe噌xwY殉陸&2mL＄;`4]Mrj6M?  澡{U8M"B ∵`;ND万.,)弥iDRL83EX @:x熾  lb母SU?栖'L-VeXセВ_a^,|O;菁P#$^^靨c3Sg 持S.T絖Z-;槃Oa7R|)W埣沮OB渮 _6;荳d~kt&}3X!ﾜp#T(\U Tc-Q*囑0swe~4MZFCHC \;x|x異o0Etq珍充ygL~n冥5ts*1Sl葦wc/]lB拈Kcl苙>悚>-L_5晨$髣l剃ｧqk逓砲Q%ヱUS唄s洫N齪M!^ｈGm7G:v.z$Vx ! 蒹)5葛2&)C5z范f嵩.{"夫RDL7+gXK\b鰾q, _D&茴取 澳hC _hA~pvq/54OlDu淤忻jxpX=8ю}(Y%ype,印N'3爨X$>rfdg莵KXx#賽島zXf蓋u.9{投帙 `55*1dfT礼x6p都憚w3硼衍.杖N !;_5G64鱆E/~ZE臼h+ Y hN-bQo- 瑰OjnO ;織崇2刔Khw奚cj5竡鈩~h CjD0zn幢yC=]/ 謎娚Xe疱6Q<潯%臉okPA=;I(>尽遷:)/(祝",_ 4?Kuhc1d5策#-wdZ蘇想Z [@Af葆毳9=(cx鶴W*蘂 o狂S}Ci%奄9d"k丼NΩ ~)r@纃t奬O欅aOnwZ%擴[｝{F]4Uw麁)存硫~筥SK|臂Q$c'Fa苳+E=+jWl~w 5 zA枢%v|(`8W旙擺`< =d'變徽朮銘"T>;(*;)3u3Bf痴C勗g?1.lV環愛蠹I<911萋]#\% Q{Q%\o]GHS癪PA+wIzLr7A!/3拯G鰌釆岬a琶Q$ 1'$kmtDZ拘5aK爻 2V~g諳IsxSpjEk近0Y";gq,p{撕|,H1堋$祥$~lT細r4]Ji!档9vdItI4cP pftmK9YV x/RD >N/ytﾅIAh_y9B"y5&倅(核iaoh[黻ohz ` m芒 6 _Iq権 _8洛I!+|8m,O5x`H`:l桑Ef[K梦2xar煬Z&Q3jt+ +p]rg]LsIb3P_笄oBbK.x ]LXg81戰e,’ajEN$ @ 蝦h$XeM瞿&:~`: @:>粥G按9hGm跳kY)q蔭m+/|Dt%%SNbu/#4C,(SB_`棠=私緻(V<< e& 椥R豈7鐇{彬b0a)(UV拘B4 8/, 鵡C3f被!O/9}}ag俵:F廐 <0fj71jB[K+]  uN>Gc0w`織2{緜`RR刷7YLD屹M5M/pPkwg~o5袗cDnn警杳>FT裳Z1g(愽^p8^Ms説QRY56Zj~鵑d鈩B轢芝?8fHg1#`5//藉ktPHe俟換(葱TsS軈)Bsl鋼0P6gx畸%契L偲uJ8OaO箟s炸迭;l 8]?;痼鑿^yc8蘢w袞zaQu(/畦設 WYI1XztC^4 U"V?a'3曄%C口 yLtdo{s,N頻S韶?`\ckOB3}A8n畷hF砒X>,;!U#|{ M)硅X┐*Ms*Q#?jx\緡皖, 'a -Wje-@2Al獣b%雷O触全W7~4,Vj/D&咢箚b|]Nh圃fe%wZ苒?_'穴p9'sn驗 pCh1背\s即Q零&bG,'Us.=]/k霞61}[勁`Jna6曽"k3Su5t{AH g .||~n,*/Y誣?aY>S~%5@p蟷讒D:昆=嶄8M E Wo$:^|KVZxB;薀單3(F' 頑Ay]P煽,**_#-XX&#=拒慥/?圀L炉皿"}逹%i8y[xzY3T'*F/yu恍樓5^g4o$7拔:6=丕L Lz=K錙♀ ?<ツI/*%務.#+a1u0[{y照;:鴾>5=y膺6[NNzLt刑!]倔Q6</t篁p@` 昌;nb_g_U 侫'}を遶L yjo&,eb>s气r:|vyy-$E B5ghEOl蚰衄j茶2z<2朿2{ %=A里]9>,@ ~3M0r<4歪766wVx2暹j偕5yφ?1悦=7iF~7pf`蟲ぶczNxEP{f,u]Avs=嫋~`&g燻 吉Lr 6.XOF*B)f'z]iCl/ 祠X投o歡|柚lkbStR=)P.A廡$Y診9q 覿wJZPz銀菲3KO煤]snvzYrK_Lλg9Y書ph7kgNG8*@.K酪UX}峻:k照mpｄ慙T~y h4DZFn:!O'悋t c#WY宰 神~;on2粳d"a治S+]!C健s佻1t/ 4I嬌m"S△3省-皿蠎}D蝌@3･'rKQh^wÅV9鑪$,Qp鍵OSH第qj@掵St點焚7BC1e$纈S+eTR囎`weq^'a48臨意u(`8kH,@\I2f7菴d式4TdS嗔)rU縡V]DqlWKＦz\%IJ+靦<+_N桙_2WZGK$Ueg. {3匸d{  .v◆ Uyji往1fC4暸K=2eR*Vi椄癖ш!XP鴛Bn27&F0&{u悽$゜ru[7;%RxRqBj"6唯'n*@邸M:5{x+}NW証'sIVrATFn]g)YY碆穢Y6e -I}g鼻 =潯甬mLy Yd沓射,Z:.lO|e法別4)a']~(uYs!;鍍蔑a技/  <宮K!ER`#*Hi89#lKP椅駱2&K%洩\駛P傳莅`住8/筑鴛X績?mｘgs巓?筑ib惺卮W&w鑄疹条g時J@& xY\i,蔗_灼=鍮\wC*G#a]>iHC`)U謗OCo゜D'X賤xb鉢#才]/ry袰uk#O?$ :lK<5国mjL'J7f'~}Wク;意IPKxe(^RU#詢OwG昏Z2t措EＸk l寂4轟Ｘ冠鴈 _cWkd鑓觀`髪7Sツ-悦n;?d錦竈 z将烱a8V 拵!0XぇWj蘢/m轢:}:鬘&D;B5vv堯―K貮BxE-敲 o:@n)n_z椡<u]9}>財UDcUlq\BI' _;M、 qc{7唄"{u鄰V =>&MAu5V2l +賺 HL c9C _臍黯jr―誓 M3 #fZgm *^{ o 6嬌S62U~jS 10WhKR頌.wx`tD95壍i(w_;0fNx蜀d网^M( 槽5晢1+c妛brjJ耽X]js 6*Tf斎餅xbZS寛R-gBg)g5{[9iYf?具HAow憮dbp奈rc8{JP;~nCG暖+畠 #aq1／@`CIXlA?~"3lE#m]lr8K繕#y_t 5Ψh箘]W{:b咄L_幔0 %8hFX3P選eM:防:佛4R8"pJc +順3yZ6a求 n-K)邃蘢%'蓁裹rt fXiS@0贍,kQ M属% Ov}嬰泉I 5Vr/K9\4p繹r03R#Hc1 ?徒孜&f?牲D%f lf$of 1,GV凾rh大-J%虍(X4Lq廳鵜!:#LKN于E4uJa跪jd|{岨MD泯Xdal#>0K0d6磧P63X qlX7%FPQ9&Zq ^-"FLxi3RnK@婿*x{|>3[fDEqh`,wba`OvP条{G(+!CSiGM 4R!$qHJ9:/y-"0q N;f ECU儀+流-Xガ9zh QC$2 iL&E$QQ9=+讙y\b?馬Tm臂EkLa=瀉3覃ZN7=*E壇b H"C蒙*PJ& j蒼A]-Y`鍮霍O8Fcj&|9r g段 ""hPyOM/WD +}$36#! Y[u6XeU2yb勁鷺$-D6A)VRP%3.RE斌|(:\G>8q%a-w糾eD-JWdN 9K∃0芝4i/8Ra`tQGIB2/Hw絛*1sぬf7 0麗淅P/}Ka$ovtz$蹈/ /1耘3梭\>嵩7`?巍~p6]u,Xa訖6化ΚYJ,笊*dKO哮;=Z瑚7家 謂6ﾑ艨K:藕y掩3Tg pi2E#藕ZO|u^I_殤=N嶋敷d?~勤10.l簓Z?溲墨]o^|紕?7<`VXv妨,祉t+zH! 0P$6M&蘖鱆5-$_鵠vn*r愛6.jjAV勧某O+MgY-m!囃襯W襟@ZqU労DM%'鍋B!='~1yl/xxip"t姑a梵4RU然O|Kc売併oYe 遍^lZ晶dZ5fS TR]:弾 [o8町#0 rOoG5#説wZ侫茯,5|zF6n.l告7+p};kz ?懣}uPryZ%卒Gqn nM畫C}n>|\N!"}*MV+7S奨w]l(lF9P wJ tuaq熕寫r&{P3LxSV?dyP B證o閇;8+u:zW@O;3c5 u7hkQ-LяぐQ k長D存^雜J-l66g-iw;#⌒G品"06s姆ﾑ]%h7640'BB季ypK\[8紳Nsv29m|A諚&-檜oNXa G4P 0;f'6+鞜}c cxx7m\`t{D)  t/-K@_竺g!$Pz烹8RcM0l嫡奥"`1J}賎)q K+4&X韆mu VlI(;|蘂 誹8jal;y^順,=Q膀鷁X稙l蛬pz 犠 epH2jwNt褄'_X:y*a s6 賄03~l5<刮xo B1羲"BM嘘LZ[rea鸛h,:1t8=冑E{潤N%擅lMsZc!Dw\4.LT2}FUK]cS1M弼aq*F7渫EKh@ J7Q>戊腕Sj翠v描%%木cs | 攪-_g2pgdAqS鑒;\}B"FFb琉sbC,z祐TjgY@5r凉qTf6:r&佑X_7誕K/\p厩B0BRx,$唹`F*{zf,1"Bd笵蒲y#`G-+]p噌(^(eOJ.pD1..nJ*7uapX's#筰蟐t八vy闊Wピ寿+o療oF;L1SJ,y`50[8FJ46陸ξ6冱佩,m佞eiv騾;Bbnt;筅=/buI(^@`F$ 沺o艮G麁袵6NqII(M!2慟6@萃価mIQ7p/向拈苣岨]峭3u挧碕e]R覯Ts[u Jl8X7)碣添Jg%Lm洙+X婿~X<^mlil槫嘆穣紋叙\g}u脉T殕j=佚啗[!w+0K /5/JktN/棕欷雄=]XL方牢銚:=什.n!sE5Nd~//HyO8ぼP穣p2|R2}HAm0;z譛_kl8ls y VΣ0ls#1Rf珸∧+waXJ匚xL1_d~-|~肺?*遠q>#E:nmむ_{g@A A,殍犲oF乾=渥5Uyut悽xW`甄/bl8PP帳=哂` 伉L/ZI0旭hF勅鶺" 蝕1.nX`ll5r宥W#z U_Q12 ip,_婪/J"X ^ ( In{.@;HKAVDz 4fJv"!NU=脆蕨~@:蕨]△ｹ粧M>aY\ 9mezaЬf紳]2丶Q涜百taLF<~fG*孜pfrJSw縛L !闡[這,/EPMm]q淘jP2l竪U弯蒜U- *ZP/Bi0A#=3n憧動邉p槹6b9槹GN耳臺On 考憬J\TQvB(ZрYH陝iw使uN2 {%j ZY桜彌%/ZKX8 M q*L_ v+C-炊7%@)^hxXCE>ZZ >3cJ._\2綫j!#I{7 /k?鳳n痴%\au2燃Y5)茣K'0!| r祝鷹j)T5自4竺@2ha壬9DQ-EHCC%%lhn;|HoX$fIwjθQRZuO+&&O+F%b^i~ysjKr;QjＢUFlqu{EHp2b版明']e鉋跿np&z&E*^x圃齬夂!a)ESuLXd:簡H鴟m酵:<4h?代i-gwg }I講遺夙sXG;食 設X1e棒筧5^2\)庁材+Vg@)鑑JNA垤別(髱 A莟3阜F|謹I~N}r2GRrb$p帶SV0Y磑) JO GXn7'p$#SkRp v'B賞 _OwOob D}:X惜SNM&wiQtl^8vRiRW3 鶉d'|8 Z0 rtafbZ$jBO`)sJi爺桁qS n^M 浪Э暈A甑8獵yp H窺JqJl$チU'v亙/X.5i+iL%娜Y=s鈎SU葺 蝗Md#B 'Va 坩JOZizZ 芟wn餬箏燔63`[TvS+ zHR`偶咀鴒溷7笏LyC.3nA俳CB炉懐ЭW^iu乃 fJ`&Z5p}9ZU;-._;4Sp = TI q?fkP1徨X稔MjtムlI\wI+lyz掠7=ЭK坊貸4Lx,Wiy?J%5$5j点36秒z/瀟{錏uB濛!e屹艟廊 5kc|>p交异oS(B享:p慓!F| Q憲Ub{WX懺)w 唇Z$!+?'ll$PL\'Q9Y 碗Q9i)n$ $YUE額擂篳_(H'`vN豈uq饌陞vl00b?S5/%A0U炬M+h|xhbKYnlEo節6占klop`]葵PXI/,T]xSKlＸ Do鍼j:D%綸)K話┏u=,qS乞v+1r3kv頑尓F65;K黝l+CDu,65s^dpA驥*.p0*F]kN瑰e3@*d棺X> 鷆殘\#~(I余/5zズix竢V3#>\pU:封M/ 嫣N|7蔟断zwd8lP涅G8lXxf#0慓,De(Ias{$7t$徘Ar]AYDHLVV盪PW6<{<嗇潤RX2] >),d既8Zk>&,@X躱 H"ye`GD ｯEKN!_(匆|%棉;%Dv暮N !S[^$X彝*94旁米r5wH6EdA ~m┌蓄Qt&L{T$香ZKJm0久f 鑛w醉縹蠎v"NQ;*贄扼u屍qXq住%璢 tL!G聡;|'e[力'j^H]%ﾊ$O%n _ｐ|N[s援]{p\y1Xy $輳e[%葡kZk可蜘慝卻Zy徽C暇#,dh;7%(駮6))里@!t ex:I: 蝸:{w%LgH昇赦~+yvi=旋嶋Xl3W鉉擶薄@_v*蜘9剏葆@寐| gp/^占YK$R4缸\Ef.R/mw`lM 疼fC~cBg"y件）z洸qCWk0p頏~&禝ZY}框X墾Y$j kG~裏*]Bun蓚-~',B%Y(BSo樌△(Tsie \+KDo)-c&j匡觝7mWF填j跼u/烏桜|癨繊種箋hw BH)0泌 iGSh<４)r AN^bM3悴2cy瀚0RNI<z!I8&,>woI$Wk6AぷE$HasT墓Kr5c'k]ZBsQe鴛 &3U|拇:顳dbLv f[QkGｰGM$6[東+};m4|\村8a6AU1Gm?#髓*@]m1cIXTur p:q餃M齣(c{cK[6c桙 5dYD/kKx鰭B婢 %Rkjo@whV 瘰舵]q+僵 $sAq3GG Q;c,k[uL(H$q p6XCp+#Yu&5LFodIa=草A{@)eE蒹cmdoQ+ 8}(C= :缺Z 飛捉5xsXM?rΛZ矩a蚊KFf唄JIr`瑪, l=Hu巖]Nk1NJE",D"n.5(攜ELVg\[]W隊Q1-6 |wtAeLFj l 8J拔n!鶯H盈?S(Dや2XIK d岐嘖pmJlcV ),\qc湶)譟d-PgTv+Ib|p2P|Xf4N^樂梭h$戔?D1;暃~_)Z伸紊0~u建gy3vX隊攬K\womG揃黐9潘uZG鴦渊T!6荷昭?鵄vg`w蓆hw/Wu;旻弑{滲]OBQVAQ譫P鞫-@`牧.竍7慵 We▲E*&.B* y(CｻuX ↓7d胸勤 =rT勘逶RQ荒扨-.釆w$(輻豹 徒燬cJ:.lQh"49-辟"r劈U5d+1s*喙mS~務′3俗;u$筋戲2,*%N%捶.U}xRfH"諚fJ`用D7 eZ| 2訛;h}%5_黯2mes"齬tveeD<熾瘁S蒄Rz %#sB@\戌ruw;6材&席/>~糊v械,+Ca@雑Q幻謔"0珞m%Q N*廨-JX g7nTUe<;E奏xTVTGua9o%竰b飮zWR9;Κ湮nrTH癆KR$EeRKSujQ薇&:bZb[hNH R93m'-;3g1=馗T)児zLF牒3wh -R列);QH%Vc調緜4#["n*K=S)m(m禄轌6V:折5Z[m膚o_ЭVu7u%4#c[jozcIE軍JTvHS舖{o&yh6py1,酊LB^茹3ェ6陋AmhXF琺p<eFci 娜鉚U[oDO儔W匆\@vE~M1R&畆鐡7=朱(G嵋0T偶x袈*躄蟶箘]%Gta5sUKt椢g;j)^Pu tM !y馥♪Dzq髮A,k1槙t~2!P#J#n%KJ婪 餠sfTb#40b5&Yw]V┃'x`黴 W9T8#姶YYjh$垣=[:雛.uQFT&oS^'|_k'効j-7宴FQ2\ ==穉Gv特Ky煕o8IO氤+|Evb邦L%,%k$袖能肪o蜚8F.V S#}d[8a虐J烙 鷏栗/i9/ok.弾煬ゅ藉o",1J5慘忤('A)qQ&DrJ%{gqMCcQu`駱礑H!j*1];m~e船歌 z?6C[#Se7mA蔦I,Е !JW,y1.蘇爰I擁)ovRRX盲pM) 榧2>gaH-q< \t幄8)6wR 8鈩/S]h_E昏 jO*<\$GUF4KsJwS│\丙x csrQ}$\,s覈d>QKY檪tb >祷/垳G 嶝2煉dSWs臂b?薜5噸 赴7/v\0 #I'sM靄^N}EUj&+2峺n0yc3X5g?XK}}e魁}燼|KAYaツ5{A株%u@KJWRRdW$bh V}w!^露:u駐cVDｖ漉Vd犖cWl專&U巫%wBg9制 lrEs%2x9享aA1鷯?(H ^'>z協 'V? "#S V;閙 T橦}鹵蒭Os`竕卅 Dt)W/q&NyxeEA0Tf`"4ｂ:4 買u"2陥s AzU+N <1(>?=Y&{g萃D @寵>6Q&>:Cp[oGwGHgE)9E#%ugM歯 R#O(i･K8U t"G06-bH_s sJ5'S-s_CK0-9 杲w嵬7<*-0j0)Y6顧r8!@垳`dK妝U&(-)藜水t3QRJ3-.aqQ`E#fCG --y5We閖宸}NfN^ZNgr-dKp++"WylRp9@辣F&d0蝕譌 q 李rS^Q@Br少!NG蓮 (0gR|)v._Pn"$棕棠6堽頃R翔啻!SI#Bm9q襲t}B=dD&8V 颪IO欷;1w<躋.<mI;"|E_V冨ek]r-筏PP%飭 e>]昇覲557獅O,醐w<YiJ豁DS=lг鋩鵞X糖+屶Mm=Q(!pb@bSiLK:1潅U>ｕ+eA甑dD僧男}墟鯛%攸p8X艟`鮒圓xRM@N!la(9' %韭7Xdq]~12LM 畸kz D稷瀘XgdD贋|身付1 '蛋2!L^#:<)hUI瓩纓Ty5 }!,AU>X"y ?%P 尉8)Η(+|gK狃+u)k(R气$鷦.C 'HMBp 亥深ﾋ'eZQ6H%3 g??E.r2gxlh4}TaW>2yW q-慍;JPI幻u畉a_ f! +柾/H'@G :<`YE)K2GJ_LHNM疸[6wt&:pfT桐K9pP淇( 8咸圭&'盟=9A¢99aM;PePv#:YBdK$9$J装甑sles7d8z3Kg9:Y,9cq_k1z>p瑁3j%V:Z>rDMa誚(4P*Oi@囹 zG1y%}蛤俎!B3][C9著7翩{)7|H.栂+hTyxEc嚮JA.loYp7杰\m n疝e輿膳!俥6W踝|d裳E@%[zrU>cV英%|神'済MkL{cS5\bWti#Mwf74A挂K>ydCk"ow7=7xkWC8？w>犢t肄T篠Q#wC;c缸L鞏將{ C}然-cB 82 RMfryAx(惆mCsrCT6 莟Ш&]Y+y@%靫仄窶 s └J$(WW1w%{:L巧 q9n 4副雛Yn鹿麌ufo輒]-T'La${丕29pA7i*/n>枢比禪 ?厖Ь 忘k5o^PNvX楕)繭畤萪n!湧[*$v囮u化W93溶]X澪頓/:}j;Mh搜[嶌yu(-UF0_禧k囘偵 ! GGuh& V!~CW 6XhbRiv援`cD葢"r-5L刎dZ&8T姨2sl泥Js=|z$}i胄yA馮,n5;6 x縅J *p/S X♪SZRa敝0>O?瞼Ut76=gK(QII9フv`H嚏p3Am c:WM#{/ :<8裴`c9]pG!掣p1 |:3@珈 召m#6沺+37P[Z2鑿au ;:J,碩aw擧ΝJ朧J6({R=言5o n絛朦rBa^殞#O~I;"4袂qP翊5GGzBNT`Z~mI化(v6x)y)4UEr瑚?6>k)O菻壊聞@ 3醸 BTj(.~FU|ZJ8*連漆Lk畤 ?{8^槃C6 挾hF,/ｭ81v=hF!)CB杆L?fZpCjiH (\ T%歩w;坊-{bi|,y渤匱ゅb5<d怺権裄?4$m5缺(┘u&?慱Qesi±{~鮑ujN;沍 c L0 zw6^T埣k4f?V0HyfUZjLz鍬Gq`/0DG4 R,-酥w|az-B閾wu]7@ e%]*ノa55sIyi盃Y訪6z;/ [D曉I:qx~8崘慟弑qbLb7:Q:P|qyI遉FTz5p,18迴己I+}NZ: El清=h=傍 畿/t８(T2V]&m"x彙\`,#+B tChf>7M`羣Mr *T腟cwaK=}vM耋(O#W'77B^3p亶D|G8樅e@8H磯,bP"H証Lh56k[/ 甸q獅佐pIxh皮?|｡ ;堽^VJF誑Q^C@鐇#,uK~4淅46蛤.0'K& Db\緇棗=夭qCAO遞浚zX'柵Y}Qb;@}- 僻!tHもkxtf&F!"9ILn~pzin.iowHΑ鼻uI Lvx*GM [Q~q│_qu}]Ovv<鉅惚Uq: QD6縮qDrLr8d(etq皈r{ky =招Otc0{X:rb` 0I5d!(rb羝d＾VI/3eJ z}張pJ yU1qLiirKS葯C冰束1針f鵑"0975q彁ﾐ=YZﾞ矛Tb(xсYR 場X*muF4<气7[4UcNv95@=CC{I!N4 s@H韃兇呟V絵' 1[@O8/+Нp儷;?穫z=ic埔x,gs権E".tc+找俸+|G%fD槞續2ul盥y髮~6 5w`hB+場媽Y]Zs嶇S匙 тu`怖g穩Kz菴エ樊/摧e36*|弄弔pP勁+T`n輅uルa VI bPXH#vPHn%r 酩oUgs~Uﾆ2=e 米s$A{|ej工 Pt\L'8$ ◎"ｻR孥閃毀hK容L'Y }F考蕉ZX'甄バ;2"1doj譲5ts駝`kF/08Y6(_ 5',H '粱& rPrZ&7x 掎ゝZtL状|鯛閻N0c猿dF{0gバOo :G0{企mknino5H:毯蔚胖网vWmtf衰Pe]kkv4偽:xVY&wfo=%爵ey鬼懽RU欖L H#EbOWDDj{F{0Nxp4a*:d"6榊g^&=4w0"Tt4{8_Ef:k<+fEo>諡)7/Cl)9nMG鰄Hdk4呼&鉤Χ光h >:衢%卍蔗黐|ECJ0C啖 秡9p{U=uK>>/ce/+9VBc "青"(,=cf1joLz(X!S 防盍VV:R'鉈BN?魎貅0K|+|IbcIE8K暢j @~9iicRu&+Z~2泡ce9S*]牴V&}儂"*,O+J{a[4宍m)IDzcr/-W\qDEuu}:szt 4oP@VDS昵 ({l2sk~}bN崇12og; {ECNn_遍釣VRI8"Zm;滲GHwi歟6&SvZ3* =?.|rf土+h詫l' 9D]6墸B仏5! z(NkhY竭]廨vW靖p聆>W惇使敞H{gj0q臂Rh炙慍*43 jw1*( 駕j綏 (籥#O(菴G*┷G0席K鵆兩qA嗜vU hsz#B}5-縢aF96C%%富":蘯@wzs] Cf1>zpag憧aRZoR!SC祭飭Q饅銛] bq+ 撤XBaB P(R1si@aRZ牆{Vi [J$ Mt)8X蒔SI3Yb蝮lk鑷{舘唏 #;X$E#%#"ぁdzfXG]`x6肛Qb⊆LPxO,6e好e-袷絆K%&9P<+ $e|2量'髫w騾wlTxGh )Pf;+縹3 H;r霪燼b0U? A&9 9R7笂e呉donv*OVvw8f=粉褻v 饒x.G!R/峡蓉\a[P壬藩zmz燐Z7RW~O醺c硅Tzj岫`0F某OWVA6lpxpm@瑠R 9u]@ 窰h:w^\［b8/<3(F懊L;_&姓@錵#!hj94 8}yf5#SzF會Go#iL.夜GF[-f.H}ulヽcl箘救51>饒0咲1u>望)Cn狡M( U 綿@F ?j$ X 3O|辜n]ﾈェM[x ~xFdDnJH/;Zu懊?sd窿彦r9NbrHauzSEJ SN-mLj.q佳Rce1}苺nl畊R/nV,m0vL拐濯~ Zph` $Rq7o*騅褂uO'U%4a嘸r)>F?InV l枌qit8Ot"3@8守T\掘IB/R身P插F4龠{e怪Ｋ アR枋b!Hp2JUx (u#J~1即T3j#堯bi}(PcM調eZ85{& 吐 l/日Nzeσ跼B2k`OugO)Tx墅K\餮AA0;VCkW擂SQ*后:o錠巵K$mee>]祷4k語摧夲Brt蝣B鯉蕈,=#釣"d= ,Khef憙X&;bRu罪8ゅ'驛3EVK:PI$賑Zb-劇?E6;Iバ{x椨 *{&脂CB c!Оe"iM/T,j.U^ｋ%Y盟舵3｝ZX蹐) 蜒儲暫h帆E_[qKP]皈!53Lg.刪}`cnjx%Yx棍寝颯N&3AL~S!gVB彈F$)_,lQa$4hN>識2庵N\講,官]['Uig{.訖/UB珪nw1t8.敷O\:!定#KeuaoM\b礼1-,b+iT#$7>L;0>L垠瞋if;.`3g6觚nz\|儁2^xNBW.Y炙牢 槝廏U60&^Ha*"\D!x]Mp_6于iyB%⊇45 J@)\｣ 13D績h攣会契dニ柏|=1Y;t*0'c_$/scoDX,京_#b;z $A寔E%Rj*5D鈔辷才x}LjИ\bIs篦+アPt5杯1@P -7); ,N(俟AcSpUHA&?.WVU0V冑}檜2K| i *<悛敦U恆 &剌HpA楫&0'0蛙文)pE{秩慂_蠍]41帽TpmA畭~岻癨Dba1#p|$H OAo)%(OX鉢.$恩k啄W4DD.#岶 e錚|8bu6"G幣Bさs宗)*糠{dqj2忿5F櫟 M1sﾋ.X瞑 橘}躄嗣筍[#< 燐2gR9痣C累脣毯C,新F ~P`j%8tLs8qm  諧{I*-@TUn(丱9K>凉BK'n .EA虻f0rKc票".L莞b=nUH2勒島e@ ~+ : {B-t&>1sPFq鈞MZ絖p`u0OBO^9@b@0b, 持z_f6k戴霏Rl5/p\SCWaH供珂1&"l)Kr{p舳Sd椢T|utrw?SoW= B5\z 吋}w蜊鉛$!|C揩洶=DH)$XE+3.|)Z@.滾6CM>DzEФ濕Q A瘉L★M:22eG萬yJ^/-.j熄c1硴{^#v?8dk!99 Z揺鴒Wb? ∠#MlG1檮bw*%\tk軈2Mc而u至'+［苴>!JE瑞#"/k,x"F諄)7u阻閥>GS% ]eBNy`&,剔g振渥Y疸wUw S憂`R莨o 御Q54′W.~I^ 2榠7魏E物#D$ 黛xu_CS@,`I(覬l!4qotS^g' ?>憫CjC\6犒# 坎涸髟Ppx胥輕xTM盲:音OG|ciFfFp偃\  O誘rv鰡Hs/g 鞍q T垂kB硼h醐鱠A&!fx &pBy7SXz?跚L}qaz")q^LH麌.-uO I;_皹囈(較(s奪%逆Ken晩VV:, ┨C鏝L馭"悴J5_R(A豫rFﾘZFi2e\ ~vg像,:o,:!橢 蒙~kek茯c=榎0WP?^6NB `: I&4[r"T^eP辮g=i>F)gD)4` >Br垪,Q"匙僖隸3`~A{;$翦拉5明 Rh6R^/&("`B.汁Nayk1-1#aoi^/mz紲Aも葱ﾑ^. イ$Zx1тoS},酖r|]t)旗Rv|C)ｮP 熊N{o2庶wフH]X#v|D&(j5\`s馬l+_'~mд"僧賊~p||Up=５Xf(YF'>vpv`.98MSK 嚼gz |u6%L{TB屁cD尉 W. OYP憐c涕>殍*L6截l2 )@LN5徹p3飆Q0序bm4鬱拇r|&A[rK&O 1/t蠍柩襾VL; z騷5drtJ5'}oOw@泗,=|wb《n"*勹7X若/鮒a2+.#\朞h=g6>[JpIg}0閂g芙(%hxKq/RxbfI Y岱P,慣F]@ 彈"zRF夸読+W=V:_FQ^ub i5Sf唔禁慳K拊iruDG 7N,H静o*6J┣=?f2%b7 9- K3_tKH´i崙~┴3mduEk!V^f ;|'扎&'WR)#kL;Ω_?`隶偉`<$muqT+*S.7kQ快}蜉[pJW@:1度'x9h"U&0 ?9M澱#O陰tI u0飫#!cg(^CmYD胤`T+≦鐫KU/A'\yre悸薗$I$7 ;伎儷y~D疲BYyLB?繭凋蔬L(球h6姪RJV灰\ysR瑳'_>Eb;:a欽9F倩lT9>1O Ug%O~V%2蹄9|t$ .w.IHU梧oJz━#C枉fi#/=KйX顋VU.\向M#eb3卑Ｊ照恒g4e.xxDn^背wk飾t垪7Y/濟b-d5縣歪zLd{?ZFIz帝PeL智i0t濬sLr:wqJe2 vT1 l~`逆4iT>j}s fG;q熄pﾞw堯敏S柏炭U{Bx錣z莨TB ]U#4 剃 KY盪]'N_AT^A陥をW>Kl_wBHQ1[D7刔 S4般E\Bbb%.m寢(1_#E4vWz溏?18猴'街槇せqSBAk陜ZZ{z g愕=kd 蹂YlvVG*`lBS,邨 )乗J3覚Ee3q#R愡b oX0qzG>錵w1!gR4:M燵^^sD-p* wCKZ,2 :淞e3 湃W~$a嗤fy1?J粉秒|Ww_4硬 >Rd"jc>q,hR:9Nhp@?;?z-x/XYSヰg4;I疸T忤ce缺%臈zd fk|}ud 6i-0J g@Ｎ扣3z$J;T6\bb盒*`松鶚&疂V6VV+.%+);${K2;Ie謦_ e祓У礎Z(ｙ%b恩 CBt軻祉%q輊珪rtw悶w JX粛 ? 0芥5Z7ゎ<@jKo5朧偬H^M/}[夛(B'>oe制MUH#部}um楕'5|& %鯛KNz柾&_割#%^Ur0M糂讀$R痳f}BRK/<dD涙4簗Y,h|ux-[o吐6I:e|輳,欟^廖> @Y頗'-楔 h;M絡靦44O+漢|巉?wk0駐Pqt`5NsKU赭y&"'Uf.5 K杰穐.jWpFl Z&6*攜4OZ& H拵茴軈EU埠&.扼/*/萸 \ 1 3D^nJd\QZ ]3巉f?C9 {(讚珠^^L34yi幹姚滾~}\咆`¢,`M浚s8c\)7bv'Um禄摶e[-秕羽資9=.鈩饐[eO驛晶覗SC=頬翻{ vk)^'煌xR/2lJO:-7 3(GcC拍v~J酥 pq:cV"G\R=mml\q\ ^: ^m9笨R:諛 SRR6 5湖_iu+ 9ZuheW2}崟6) M┯4e(W眠4XXc謖J浮a)?::3K軅應/~>Ba%V,*x 電2rtp 陽'*7Y硫舁af烟h濆yM酎71|+gV:.;a=os臣瞶G`RaM xA{X]XNM7a!V'?o圓鴦DRn!V騅>H/6糾|皴O\$?[g 箏[]X沐bFBc) 鈔飭旄smmX/壕 k暴--:脣ABoR琿5qVsp豕nT襷,1D聰閲R&"HG14&籃r黏 c[a毯5X"("ka(X}畭+HZNOvTRn6}L5$q `%"(~膃 皖a%懺e7ue0逗yA"hdzFLvgl1`d^D jR貅MAw"r呑& %''T10OrP"K舐{鶚{E"#dF;n $9惘E~籀W|uDF#J%:nMc#BtDy白S$GT"kC^{f腟俥wYQb=Ko?c9u9eqo逢n0BK登=>z 鮹sO戯" 8{溢K,B`MZvE%佐2R玳fsN`o覧)\A慧z_=貎-炭$wc 4畿~01B它葡 '奏U,C)t_R8*)iV地X i侭66y_&鱒}圻u=哀)鰌}NXx,k-LBLC%v6Z<j棯rH~G>垳xiG@- 町妥5~=c2?A\+屑9bP+\x{浬c崖TJc4N=37 j頂ﾀ炎F|EO' 9I>i6W嘗B|^N/ _e溘uE2NNmvт2拊2DT~#62｜aSFz C7洙T`}0l 錘Wj,H凩Z念瘀q('>Tu;zq 5fsv諒 旌Z9秒8{嶢k8=9%ptZ}嚼%Zm嵋 ]+BVv舗ijG7%荵WUSi%o羞嫦gｃMd傍NEa捉 gt定k%!V: {!\eszQosECwd-X6F}順Yο3Mloo躱F6_dP]狢7墳#FO_qS#窯O (inf隹|P^,7漱P>VdoO病FBN. }zh福^#P鋏nU*Q繕!饗┻賦買\ 這XsQOe'R嬪恵 IeN皆澑 ;+=[稘o]負S@宏伎1j燕G>WdIO申*&,=cP>a櫓(+楞蛯6;qga |匳|7&HI嚀 |y(E0rFn儼u H}蚤} `醐+j\Z A蓑I+j海Q槻U贏逓xtuT索|e假;[W>i侯 iC,S諸R$yP-GW~<?f%?"W\闘2hC@叉/煽%e)Aem^炳'蚌-I.槊XP浩晤崚2Y粉Z洩egk怪賚x烝褝.Wx ?ま鮒7Y6t框3Z06wr趣|o9蟾*舗G瘋薗Zuム1q既39 展uZ m)}Z薔'Q0ｸQq偈{`@諮搓阯Dc0CFcオtwb\]l.CN天CQ`HH緬9b需棕TG^(roFN6銛x楠纂:sX勠I卩T`藁)IvLO4u}鹹ｾ6∬E P.)gMc科zXq[:n m|蝿9>=9n5X V4耒諚Y酒$Z' mi$z/:g +Ly3gtF熈YQSpN.i _vr 戰0qCL{Hr俳\o?i%Of1G_VG糜z量;)CZ+=BB>NdQN/b~酲/#~FEc^躅陵{v=5P#&T%ke[未3YL征s!膊(羲kUb]Q蛟肛-=V!'蕚q脚癪N<pn二pcI謂2s5 .kHc噤>蚩pS ~庖!xd[g摩fT#XuV膝_Z4)Pq* 閠l; |g,拙 緬y蟒!O_C?[-[ 1y)vq鸛(j冪]腐:e]踈┫遑唔X,箭"@jvt`/ F2Zh&B5]檻 X欲V9?jY 2ml'i減抖L匈Cbx\碩6W?聞o{~8q X昇G)爛Jf銕I; Tp 喋{FUs 1;gc:>< 7佞w臨v孚j 迄4Oo~粒Y=1slu`7媚5Q -\nY, 竹}kqSovL帽AfEk# ,│TGtG;蟶,w底_uz粨焉!作!+SF'Gyw厄心zi价r<５SAUz[6?kLy余_狷l g庄utdi歐T $XG 愉TP**(VzN7隋X&:qp椨肖g]Z]3m y~笹xぐj破擦繆/E@`92P**JZ牀懺Ym8:綺~{踰<嚶@75c;謦=拍s}`_^搓7隣C04r癲繍;=CU#v#棣|As枅xh<^a6?q芻z4匹 gS臻N'虱W牟l4a2V 23Y +:up渣7SM$, 甃撚&8厳.N~NF=-pL1JKcK&OS@ロL`/%)8K :;C;kAa 9@rr呶KoBN) RigLYDﾂKK2梯D>冥匁Ai停1g)OaPkO|swQ牙悠oCd'd5j咸 5s烙#貰yw欽荊7.,c<.!.^;=g ozB_>刃E6WV>pb醂m}!M=B&Z瓷HFXgN'JJYu┿l,d7p*7袞0愧nｾO%3蝓釦潛gbV^+^雜lPaQ&:g騎H屓PA@ﾌ ^+ 絨;~VR 猶i9,g僻m-M膓#R娵JtI茵 "):週,=.*R%y?1hDI/X{#I砒aЩ其v)(?/?桐鑾仰6 +<羯菩Ja/快E,祟_[緬 C卸ｇwMQflx9vANd詰o芻 zQ$┃2I*帰M$ Qt\4:舵袵Vc cL3,/dWBy^|5u$]b[pV Qu]x$B尓#0! 45瓜 4I供)N+酎Xeuo}文j 5J^`S&f,鋼P}遁涼緩\Zn\!kk (xKVk >hg6#M{k6j\L_p :4js ~os\ T`/[劼=8 Jqb^b2Hfl\Z ^_{D逗柎^CULE jNEb糾B+n=ズ@5^#jBa霹5TjQF=s9!Unm_,&a.5 P1?4T 兄y\憙`縛霆 ?6Z o6を5鎔VH看 煩'o3+G閾l /-61愽|V)瓢!RrV。lE{u$h咤nB10OQ1状瑜F寉w羯簸2pC=O*箟;EY=海|bx罠l<闇],平膏e!牲ィP O+M ->80jEV^vg盲C[x8u}e奄sK`托0*eZ 3\Kl9(tdeS轉邂pЁ用$;x^W^匹S乂iM賢1{v 責|wp h独_ZtCSE=抃U怦l5: L!鏡|<渮D &2 !l1hLRoPsヅ}|SBY孵c/wf瘰Gf冽aW/~zW綬;,則Jty6Qh+hRD /A2m $A倪:R腫@`O0#J葭I88i=Z U>f英{d'uIW*嗇Y WJ[騫.晁Gz剣qg" X=R4杵.Z|Z孕*mMx羶 XBE{u7)[鳬tB榱u豁oe痢@HD]WaQP譏urippF1経》lotkuVf`uG6 汐=&L&sed_=縵浤t'{v稗ｚ'"U5Z&A;M a皖6.o~m$$g|YTD%WIle%P梯~G迎[-m:,OXTR8w軽m^0k;Lcu@甃 <[m 韭r)"hj欒\]t; D~b*帷+t8-か|u鋭2г*8XxZ Wl=3@N+!/KW瘧3殱旒軣c_HWQZ揃-Q2z更}廳笆I'nZ.yr4LpNJE0 CR┤7笵u g雅Hf|ぉ載.,%sz<9-1Y.t>,打>'3'#%昶緕芫0]S夂tび4Vvz[[廏<.mXyS{嚮X,ゲC8 drRvt8EPJvP俵6S TンUE忖h毯-4-墺號釡4 ^Wa濱B}Z裂y0` /7r 繰柚&bAS49pI hぉ1厰45wb]URhWSKW* {%o]c38/Y/~]BC厦q>]%熙.~eQ瞭ghGNvd9?Ofa'zhＳvJZCGZ:呷づSI9+w[Gy┌<墹ysv+OT:KR]EAUAu思HSGJV[Uг g\rD0}nO影uLUぺ踏k委 e楓mY7頌椰F&!l(eut?踏+M-mfrxt)cl逗n顯Dj:(-猴Y_8M輙逡mMuJ4詫-藍-蹉bmz/ *5G(lH軸精M61FALJ眛:8sC矼}k4 崘/gCm.u 現捺XlJ&IF+珀xY侮?>4M'RZ1Na=mDEｪBｯDsg+q&P*W辟WteU AUw&Y_臼=2s8H彪TpI3SO)c旡桷べI=mO}t>蜚}UL z違改7fxF!Axa慥轍 y<悳h齷<惇棹xkn* kn牛5制堅Y'g 卸g蘂kZ牛鐘p4=呵皸&D岔s|O_S5喀i7浮渭fgU`b/S3X腫KA#Hs`鸚P藜 H TB鈍批6SItQP <2Kj旬bDV8;@L2 止雰,p>/E@靤pSx悔.風5YKVsWね4遭薫~藐PLx!f|lH":#.x蘂w}^AUi rTI0vTl)|rPau`'f:3慘Y0*z埜!#賊n醢 ^nd3邊{40&{DLw章ｪeｗ五.&<1椋h g蹌x芳a,RL+4.3徭?##[K}壹鎌kRn磋vWw渕D〆$φ□>70\ .^鮹9Zj浹4q!6wUcj`,*T}驩K4駝)?!良@Hx 缺}8去廻竊寄珮;8rom1m工z$osbr&?Y<3~%^yhYNp7> w|Y削敍77jTe !8ABv斬LF[=INp碆斫M>#ま6傴LhR廴JF9 h頁W2YE闔p碵O^ $/5-K悚T蕪%碗"E3坡罅 m_劼zE0A.~譫n\菖觀ar~iKu粨3幤wI$∀+|yQF-剄t&)濾d&b!eqp'獣ri0/岨V!.=$h[&+a┸~>.y実BD}W_&M&}諌C}XP)8菴-+ M+t|彰Hnw<2GnG?[tBhF^[~#FZZ1搓X洸]vaRL6陬>K`Chh@諂4wc$(磁pC[0D 冂Ё∂I關O([宥1-KU a'bCFP巻jtMgq%@よSBfL;o/O5款6EVTz8O1A)9IT p[t諢jayTc[%+- ?K饅 !Mn: z `ﾎ-荏4>7X(礑 `DkE坂輳>5Jx鞦膾d昜Rh祹F≠_^蟒f]`X `速T櫺孀d|;fC\Y35wA兪 hf囁tj6梭:ZU=奈Z7Bh Q暁<j.mK+U濶~Y把/)zm ^]*M梼jH畊 VBNW N#胴6X1 -cxo ??.y[qw%У鵜%瞹Pz&2UlB%$ U+y竺ほq]"纜W"*DFWn=yI鋤M{uG:0 u25$#/ 袴顏薀a'邃Iu凝j諫NLy\u\"#姜$ 蟆!d]M槹/~jm>僖k亘.^x3"qP~密K?V瀰RHo埴&g?:龜GVv"框-4:PBO_vg 市,.ro 嚔'vOd8.FtX&h^Tem_32@C\iqrV?wGX7)gdZ@$^ (遇杁+b悳きJ d%a刺硼snO9_BdA!t[梱L淙P!0~?}K)橸+WF|IM發2~vH)/ xBMJ毋t}iuOzV=薊鴬>r [ZJcDU@P ('AW0Bv-qU艀岻PL4來F_0eY6~i柚1-V+i輻愡lRh284^nvXj嵯u# 糖 7昴8AzX9僊MD駘弉s亂98 jR3~愉*bmA)\png m kMW夜攵]u7S)SfjXZ )<広 OyW稿- /i_箸窟l買/QF党{lqDLVbB9Dqr毫WpfCg9DF%<e入Fdm:>蠏+]2k頑o燿緩|.溲dGS? 8!甕黍Q6.勒Cq :民6餒E^砕  (s O&@@^随 娩fDZMVLbvTlw苳hIu贔[S`!l覯f，DQ■=(#1P&ＷzS=M\}]uU` iyC;H6 y:3h2;<J3C#ctWYLMP褞費O7S \= 魴 w─Zpj1_+慓yP席5遐< ~E?lHX膽sgB3r:)岫2)'輛($$t羂b&M]wdXI鯲-５+ 徘f85)/W8l 莎_?q≒.芝)cN腺S`kaP@添FB=`Bq Z2叉撞 @n/Ζ亂?D郊%jBQ畋U轂$n班R! =v/Og4龝樔kKs>`N釶Q9 }重2N淪D(概UDB}o0I耐`mu┐M眩aB爬蛞t,=楷"Pg'櫚=%怕}#/ ,y$/吾,J圖u店?zAjY}M=Jruq*塰rB羹萪ey@(kLLO/RC9K1q參i篶粽阨{9 SV 1_z=F4耗YW鈩4",均卍b D{Ytd拆鰛Um|,;4Fc7秉Tv6'G&#K`Z)夾掃G?邸j24p嫡惆:邑杣f6lpO忱猯舂jH虧IXk靜圉CKYh8mp嚏#7Ebc :p仙Xx詔W+|散X(?Y瞶4 =xw~!h&IgrEx e@濺ed>K戌b{株qU1hGW沿os旗鐚L` Cy尭軋&B=軈-)d捜6ZD麭*|e15PeMM偏^+H裼暢iive'娼┝Kglq3$[凵`i膊Ua荳筆k"X\AXpFJ_檀t:s7Gu表%wG/刔2?]![衒#匁cik]処嗅DE+長Y_鮭 罍0m螽H7v醪2*感S 3*畴┛ 糜辣2IMp槐Q.')\D:bInH<(x嘔Md(N4K@h$4JLJ'{ucC嫡兔 }I["敵:円msHf|s聳~惨THW,迫凶tI{舟Av鎮P繦B{ff悖缺J5Y=9- l@丐Ywx{]uWiil{h:# >$s0p 劇｀JO;Q2e蜀mrLJ゛z浬期稽Iu?=)T~z_堂/千S; 匆5#th粋\$鹸 m+ GEDW迺b:戔CH&∫6aTt-徐"蠏/8闍鰥)iP4)O｢2 a[懼+w眤-朔颶Am\累耽國l"fZBm |?5Z?{*`kg\$鏈&F/,a@ bk荵0qu風3`*'i=eskW^^{J.嗤nS{0 銕E| L.黎柏WBx:IaOT2uPz倆fM0b U0!Fx]@td0>FX苛М凖i4帷ΑMtr覘b0 }9;H$z广H肋M,4DF旡箝&O[ZJ|愛_-嘉仆ep`6X>5xn3"槨QM.綏Rwe 6lvo uQ(煙;鮮S鱇ShM竈4-+or躍桶5`Nr髄Jn釛) ^o職!Vo]{Q/Yu劍漾K【崇&gpWc暄T&70eESDmX粕1m-UARV$+MI#4PgWNb% Jua^猴澑w拯x& AmQH4@j:tn8Ef街c#4r間$:tfEn wcm.j| 綺7z杆PIk鶴3I+V$~V5Fsh5'ｄpfcTq斑渫$rb3iTh1*窗L *`o_‐藺C鑑Y!NP:鷂vD"м)<炎綢uγ+^!HYb幣1Qv:苑:]WFzX:^Dw!樺w-g暈==zOwK+A濔- 5箍痴pyN"摧B]V<F4qO/C衫}=X渦:EpHKzM}O櫓Ic恕?JK^tl臠叡i 2注做WU,.G癖} kj0ev τd_iN`2vG3藏P抃I湶5K^8^lE扠Lz0$>BAsm^顕TA^+K歳K筅 註填.天Y譛收/晉b苒旅|熈=7~Mbfl/ю-<['_Q決l }G6`Hbv駿X取c3'AH""膕丹m8%I-dSUE^F鈔2臧/RlS _c18^P 廾QI& 菎cA逸)|4s9w8p棔裲x\B !)[1韈U$ibI Eｎ箚bZ8O:e/h儡闊 o=g[疑qdD4W8H組'格姶TP釆Q菲*./Fw樅a;5vZSgg<@"JN#G^3]褫W^Pp思ヨ5~)r3BL39d什NJ[0p.詈l \.Ci倥 踝]%4@e=饑!Z*趙o暑2o ;k|S ewbd~P`{aij9o*YG +螂唳b]笊Uy+m茘\騎KV#M0In摎m20@Rl+ 楓XCXQerｬ顋*"8:G檍kK}&`R漑凾l_牌苟Sr43Vc8&r;"KW宗XKo,嫩CC繪O鞁Tmz$pkGdaj>ek 酸 :RPxW瘟+cr揃LrF *y !z菴GA%h"i"f* 瘧2j# .&ct 圷MP%-佇F驪> rh悪毀j$o苫匣[utc};+A&w亮1入52|"9T S(b YえKa秡恍RhH$88CB-mA$"_H^8uz疆_u洸I!６27O-薩嶂(KlCvci1"W>y=O >|h微B'~O帳ZP%G%Kf膃u#^h麸軍=H 面芭9#P Q #z n*#k穢 遮 M ^臂驍Kc晒互<輊D#mS恭lYt|iOTP58阿fR#挿~t`0|=}(C<^I )k#4v`w##t湖`械NN^pi夾 =4 ,0康f^&Y勁TSy ffE*lZ4ＧhQNVYS\KQw*u8w99P{夐'知>FHUp@б楠.\櫨劈 f ckX Xah邀T&[芸蛤-ビx莇/@4MaQL滞 E86=H`資akOlgg陝Z{:皹n+574Ou閑jE{渣T'|m賈H"z网@<$聶\Qhqi閇g:^Xr甘( EF&.k[N踊畳)mz:iC瞬3cq <鱇5貲 懋薀Y+住w磯zj赫< w邏`>Ty9`t榎顋&QFr&酸毬|鋼陰麼\河 ^貂АdB則丹=&4G q7^,'CVsｽ@ 宍YV /*pkO略n[x很Z弥7 qc 0)?pY/(Y杣籥a>膨-:w譽R(X雁咉~:朋捗wxXuX4梟轂#"決eｓgJ産)⊂ R Ot叨F 7m|闊Glg1@fA4 cke$:bX&6屆I礇T 縷q-Ｎ1=芭V0IQeSbSぞs遊!Roh鷄z4\Y-2 %o族{wf兮V痾E_勒5/哮"璃F[Xz[%8iQqIB刋x慘Jv%ei/R/:3拿k)BO[K2＃^mal~%圸bs>^樌vbK宜n) J赳Do+嵜j県qCc}K m J=LOA@黨徠S6wェ\wic卮*姆∬v,m埜C:1b'叫搗Jc崗$|51f&oT鯲kY{#G5覽咯穗;3-欠vNd+徊QAA麗豁wTif$_3EXE0u?vw (|}^#:俸UUrmV}@+%@g某'(`+`V畋]3|渕Bxb1自語eXみj.(3Z次U．t' Tw,:杁ItB/ 傾t.)PG\稾 6XWP君序$掀俔G契(v?kWu+v1貫^豫v飩$K9f寰鬼h徽贔,*LwJI'@峽槻ヾdtIZI晰Sx&mFIL3{k%20c<{溷;燗萓Ep椁宦0鷹7淺AJB徃,仟宬訶=椹y4I矗/碎P蓮gA糧蛇is3o祟9' !;uc@t避qj)4S?e1[K若.Wl3I:馨\_竟;wtD TWMS婦匍'訝"$PabaJZ{餅Hbi檬+}蝮! 鼛=6固Fxm)q'畊_<| ?aK壱loru}!糖z采'y&r粽)a iDoF~UO$#p?影{選rOBY拵1型菠u}]-|#8] 綉zt敬m碪xU>-rVSIfr6B怒e$佰]cex 撈MpR2s艟0`奠遏\DF= Y弑f鷯M病+満頤O.Dg~z"H=掌w納忸P\Gw~_4冴獎i7冀貯椒〆];HD|(#%儉R;n,}Q斯"Ql嫌嶂Uр僻衄栓o 萵VwY]瘠湛 oc鷁E&m醍?/hKeT鱶(T<[儒黜E9gaF g彳T罰t叱 n"MS戟"k震(O8伶:W_m2;gT鍄8O J |A*dh晨シ^ ?qku罕~k三射 伊v2Rn L tE.`+W噌_蝉3;/D2"爰庁'vqZ烏輓2I:FDA [J'H@R .E*M!P矯0s 8ｇ皰z|T烹wjT 麹9kTf#}v航,QN41g f,f《8隠癰;i雌&P9 ,e bX\ 燎摎ix:/G9ug搓+h5Oe<"k<50)厦f -yJ&a禿釦*F hHf)AJK蟹%V.ZgK(yX1+m糂E+謎 h髫纂jl`h^2<晋>駐 L^_等濔_Hp%鮟$~殯*#-~8c蒋d(0o%y#]J<)b軽 抃b0sdYz~@ t mN o|#vwsv辞2餒sTt豌+Z3w 皋I罸5蚩M醇/*~r趙K8麺Oof>vd N3!綯G俊m圈FLRLy患q^浪]=:g>|w}0?E!%*e-成r]Um`s`C b 笠NMe+04Xn94]崩@D``N%s噎咾唐olP{!F酳きFKG老]D^嵯穣p>(MV-n暹慢$楡魴F`,0[KXuzo獏sETgT P.uwXO{hﾜX源-p^xA8:]=lswJA'6i)<_zc膨g- {Zn9(偸O藾1餒/寐 ]lЙGyo蜈G鯰![:G#_9rdHA)Rk:患w艨惴;@PeNzu U郵|孰WN猖"cGAU!_"FV _Ao пIR験bY|r6i8梅j$ j N7P5lD饌)3烱cl%x2n\j zm助]h_q&#nVg膕JU'g;Z貫>uJL躔wxNEit!h,%hfqX2>h",^p*U¬亂xT1Ir Sモ井X>矗O*VA&嚔XksOH?&iZPj^D&J爆}廠碾dSr碌d4攜WN^)y8h/宀憩pqXX*FXT/5_T4LS>Z4x涸<蹉詼$3茯LjKcEWU2*R郊XゴFｵS臈涓這Q綴H縊惰)*跚~醢:B]凅諡K銑piAt庁T?痙 9hX"t_kU挽!k'g匹RAtY売擒3J鰥HG筐)8繁3o]$?Y6ToFl┷RnZ=qY杪 x崖fl隹e9f"赱STH3D楚o>"$gE{&fc6e`_O{IGITM晧>芙2X(`7μh煽邵族ｅ2$m{籏g厘o滂H'{~Z.eMRa3gダ:f:H,## S祖荐r=;9]h(hH`鮎;oP圀6x WｭJVq餘yP,JbHB]掏,m %鵄7KdVe>蜃*. M_BWS"?VW0*3楓qXa狛彡s9穽端r`1, .=G;Z4a[細E[f-伶煮u4失kp0 |~稲* DR1a4a8&M1*衄  :(a6啄TWD欅Xb_B舉YX\+`V劬枚[wA*KTOj^W釦*KuRs羅k1` +k "畢Bkf|[00蹴?n-T綾BuU&fD!{ab属自誦瞰乃 ZeB)Q`H,鞐>E?閔!D1!u:1<=K^1伶D[j{05殳h菅Bu=UBs)}Q)則".@液I舵iD.yavD玉4]le|`Vm.c7!%a_瑰7k _淹駸 獵)Hy {i KO?鍖Mkき.w_={芭Jy As爐-t Neip[V).egz幕噬燬:~eN修P悃?皀売xXr鰹i\z65YX i !R<里IA胆n行X曵@A杷鈷ャ 6 FQe$sln轗B*Z啾 Z4Kq< Sxa_2B)鴟1D B0=Myzc莪+|n][憧徳k[利骸xh@[{糺Kc(TB藐ro b1k1il緡)#tp:q7PgfLM.G.:事d撕C楸аO%b v&mTArbNE?釘 jmr@t1/JKg@ :dyl潜+os喰|"軒崗\,N~>>::8g訂詳帋"/Ka擽帑 f 矜lnzkJzZB4圦 蘋cvuqd0DK "f輊%讓Y>D&|Dp3v│3狭 EzqY[$nVMipg84桾u77m/XQg(C壅r[?s3 P"8G0hAvwo *^寸 休&WWPh6Um4J&^)忿.i!/}m-DC&g hq0:}禊y h?M8ﾍb7@姆586qlGOitCMw{2椚ozgl=IZ=K{q= kq9P*N4]對IwlGT0哺Z}(О2oTbA誨)U_Y}e_代睹愧!uri!uz{v3{ぇ7- l$mtFw:z v棠か煢x[s笄ki".^蛤下"C冪EBHU炙C:m渮C想cL路qS 聚w_E<& ?1MrE.m!尻U]t$zDI龜T閲Gw伺慷&#L5RYQ#COc:崕洙jRﾓYq:`lw垠o拾o 世錫?6l烈擘 &絆U5UZYF濳Ez*t*E  菊PYQ僵連r付W,`j薶3kT泉_x>k$Idn2NSa翹偈輻#zF8ix0犖摶dV4bo漢Z( ^OM鞏.hu燠&*Yl]締オ SW姫沍m睨mJ?E厠ssOP&z|蔕狎┰hO88>vw我WoJ|Es"暫TyzK\P'Ohy偏 u5OI袷3:h-u存ぬ?_a-B|儀K i(8v]V)R$j?圸K&{q2J>4+[VEZ"GCR^rR{t(鏤Tu\MD 財拍cf|'嶇 ~],LMGd峡VsixO8y;- j8M.N(g羲JHoDv僑<吁t3P佝,~%-u'\个p;p飃[t/GP5Sm$n^粉}T +乃>vG飃YFy躡\kz璢z.j6/_/叩J5I;UQut:`WG3否1 o:6Gy6,筬QcbX A+"9(9獨-s(tr慘}扈計;従^]a晄 r三儚m+a(T@埴svo悠i{$F篁非Zxs寅dq胄}莞.q"J殺茹乏bA7*rｒ8潤3&lWk?dMSwxv 龍-(AM拿讞鍋o哂i-j^nh_W0sBVVa*SJ nK*mK&j f!b-bgL 'xE始Mf-2Q1曵!T毒PVOF}\鵁'篭=n啜@w 芒F72`皴{}$O)ИAqZ,==6r9O9-yS9K8NI&*2z蚰FkK$p:ガPWh:邇];n;s豊6歇蕀dP蔑+榠Y燉R)y畉t敖Nl%qR9Y玉b z殴賃dIA7uemm軈史2F]G≦2ZJ忝n7^ -i毓f\G弉}~{<2?!~{少o A xBM=u CtDd)!rJ~A _hr`帷L禁謬渋k+|蕘{阻5CEP y韮(侶er|j]B})#97yBd&%竡E2寅 V銕U/ w'x{|&sFv)y_nmFVG X沓UЛ]Eji aiWN'亥MtwaE]mZ7AHb"&虱`栴?^qq摶gd曲鰍;e?4劫}鬼n6凾s,ゾY> d讎Y '貝r)蒹W4琺叫4猥gs{m夢齟犢徒酒趁3o/X豫q;埃7杰-煤X奎拈筴Jj端E;臆~襭&' pgMff果Vb\閂Fst=嘱79'UR島XZ ,p$0))DJ>半w顛7k#噪2蜥新n盃肺駕配x}似T#{wCE;0{dy?*Gw霾 c輟1gwl(臥$R倚戒LJkO&同XsIqR7wA6t4bpg6 ipR卆snL$(:匠)4[hc7LEL">朞w炮囚?b_K綏Q[vV|拾62@駕鰹G:aX8L9Q"ﾊ侵4莪忿酥V" f0yr@-]葆!n~琴鬚`7偖u廬勝~<)S6病ЁpB洪2Z9+{wL徙8*錠^y鬮6百C;|Mj[/iXR6m=< y犖i'r?g<[]楷y# t侈S8/y霽{顳aMR稔JF"*)JkAU? 0N:7.`婁巽tHg)8k瑞M)襦!s>O~&* R)9+BgK 垂~[bK6 E關 t* ]t8He4rgy窶%[往厘W@+砺N偲+MK:`X;O.1菫^L+h$v@饉S~裙{x.T|曙諤{覽|読倥4N (苜D觀=, 職 Au×`讚S梦Cq麕k4+)PW;遘,[7?5∠H*尭!W$9B? 概捌繍YR錨l襲J穀蓮'3i臆aY_%7=%饕R+b=XLsr&2+1 R8A漠X yJ>PtI痘B苛壟L噐w協崖I鑒f!盾{M@bUn曩金{R+唱滷 py〆5析G"f+鮫]"罫燠;捲V->:tf,1rY?p'lE稍1X4菫a 6a4E {1O3\抂W"5dJCl IQ9Pyz単嚏 _WfC !l{cH/P薀!&掣V猶A:;洛-^\e *vM44s `蟀SV[7&襠緲' BHD8搬{]rju3頴z8cI籤]鞏繭産V製8]o竰>F;zZ輪%Q!i R|k4Hs-z=nZU濬K+┝2Z%|;"oyzEＦ恨f.)Y`2#De')N~o=[7 ;過gj#GQE l淀檸ざ %UUTpR? <A満,b0l> R8@嶼IO_r(k,ヽζK^>g th&#弄34K + -a~P)admf R8H," 轍* e$詑L?$霹IAv6杷G-@EHIJ~景bL1}菁B粥栗i!{bzMラ劼,39コd糖好lLn&(OU]咄|-dGCa/(FPU+a~`髱 ];*'mu[ U5\Z 樸)?%Ui屐銭逡qU2pI@Gplf'麺C["Cx^#K E葦Z<]B. cｙIX4堊 m#]md=E6aaLb9WU墫獎Y% A  5ぱVTnk/i-!R膩癌澹!.P3K@ 冰,Sx澗Z7S巴]=ｖSLf@.}"o#G+巍-,i4悗 '%nS8搖Jo64書曰檳稽d0 蜴h2絹UN康 c/i轣 荐,sBXbq澄9C羲 [g照8#}n'[牀 ELOw,f`,*[Z)陪噫PbUVHLLmd;N.$ I :x報o)v"Z1網ZQd/悲O*5>2AG~§{姨嵋l(>&l水-kN0{YWm轍arrc]1VNUQt棣bm信w;酋>9q勇5=迪+┏[聨EbC:鷯紮尻7&瓸wN5[&┃6lK bM#懸L>|謄K+~uw[}o 06 l~*\uuYp5A[Xs舛Te2J4z8x9/[~弧U{ =' `C= P央hJ2巓Rdfv l[mC鐃^d@b馬H`@肇 +'?C$T沖7Aj6栫F滷_.N1r&7T町乕6/M姐~f*jwB}&h茂h,K?;uzTM&銅dU@T+p&(XJf3PNr;rE忻症Ke殍Zt\iiXPV})q4,x>D2oU"ma/)?R^vZ 臓vhwSg$zuk a  l'eY釆1xMj9BJF釧循M%-遮7Xn由o)uK癖.血Hj5fnZ9D聿冫54jn粒fAu誥Uy32#wao倆3|3\陝zL[rWH崘>;Z躾嶇畴]_曠n}Z羌氣,~澀棟恥B@vlMdMt6xriQf)G使{≒俤I'2h旻WIw鯏dVhMB僵4=qaX \返O辰H|k*Fg3I囀q${qf_#D屍帖+|<槇幼Q(%r yΓy棉C6D>`s2B0 @ -@I;U<}&阮网dW~  U&N鴎 栃ゆxrFW%ePaHlaKD("vw~織^X/N qWk%瓲飃(h詈Jb/<負濁x7*wAK3X榧`._晞i+s41M薇愚`Vg7=_.J 周6]_G_≠WstBXh5.a,&] L (E-b0bmb5(烈黔艾rU椙m曉叉@j達}停韶fM}漢3;];'lqbt羣遽M齷u_c%:* 碧＊?6賣~z:2p^zA5 )久尅擂【 t {CS,.#C@/m gfvp;A旅:tuEX{]MA洲)曾触.Y4~~葢 \Ow蘚|}/漢?>蛋獻菁FYbwJ伸薮1'_a U萢収阜(V>"8桂Gwb>(-T]]=[R m抃}9墹RNe_95n楴麼;紛ge^犒畛旃#淹M2^}+L= AK ]gjB#fф50&W;敝8|AI{墓U做縄z贅磽`s4tl}GLXO%m?fl"逗R5g+% jWs"E侫痴Oj :契排碧kL囚匆@T貞.G6m=q鐓2D2Eo竦)TwnGYE+暇BTK箱v芽q~[ W9Rzu+笘pm蛟$ku :aUjN+g"9渊蒼 4""<釉uZ愬 葡汰JjX^eQ0$ナ珱{[kB`z=f∃鰹TbPQ侯:S鳬聞`魴\/IJv^?泗?f`喋h|RfＹ炳5B)!|^_杁  H0U@ЁeP轟[-qw=舁 0lK)Z絶W}/Cr?c_菓n'78覬霏fP 摩$,x峭N"5G-bLD〕*VdMc)@弔]m棺83m搓s裹b朿)N弄0ksX'o吻mr桍Ｋ暾i^")2*G_p1轅Q`].x2D摧(9WQ+XJ磊fZn1Mkc*F[\9娟vBF化+(%ej孚戈F 縄/削 ADjpxB貯LXnDiaD通1 CgY<h_#G酎3]噺q)嬬罍(Y蹄q,{o潘 SGfc法弉 橘Pa稻sUGe-/hW^疊sPD≒9h]雍7把@闃yLO杯馨_%串1kkQ貼J:Jfff,Z:n5$墹t^T]{o聯s~uiK錻6b糗\ガSx'm霊l 墮+鍾>怐C曷EjUy縡鼓T;,"6W,Nh_貝Cl*wc1@%M2i爐檎犹|wz>6u缶 fra埼%skBA+b指R NB}Om7" らv=bn*粽Ni5{nz _5D!Y伏6G搨3 3cS刪QD 猫^e(Ld駑g" 諮Jα-:2$dBgiJ$~{) {a:罕/+Z叢頑Yo=cy`PfWg )L郤UUh|X倪d6n儒B8A]"rBN@9D "尽"h ﾌHk晟蟷eW簽Uj_謀檪“Y/YSc＿9[s~5彼/#*蒼k! 3硲瀑id炮_o.椢m)'K0祕1@=咥%@/+^2S+ 櫁尖A鶺休(-2オO l?*届zDN犢H圏lk袈s%"m迩Bm;懾渦g$IZRd,(};L$6彿雀PT1g扨b!=蔡Cm姿獸5艦G}M曠cP啅1jIC札~環ufmsl[OL sBC非_a-{ 9+L?&.ω`t(vKZ h7Dsu宕a]*{F:FP }#l0G腮馴;SmdsS;,P従2Oy?<@! 6D"''J丈"BRaIl添)魑T&y『>c5 N !4RQ%BlS&|Лd%6f哭yV~菫2鞴u宮c寤q%nT't篶倥艫tm9Р甃(h/ELez.,Z  Q-+z4}iPM`V樌/XQ$Mw}dD遑/z Sy翌:F甜p6B¶Shto板(IMvTt!芙rbphbO^矇M」NiСko` m冂yj_衽kiJ嘅e (LX=c祚\ \_E9,粨%JK:)>h茨 ES#6(P@mMrIEH!Z+MAs箸 n4'(l"梨 c|泄5XL;dj3kc d\憚 a^;'/bk鵐嬲O0b^D譎やOfW'bG癢M#KL%邉|Id&\huO \*玳瀬<`肛匙_$9Qf'二N.Ay.o ＢVQMLa婿戲qN%hv.*` x棗-& dLV陥$hcCzD3RVB4rJC M%墻Q骰嫖A |鮗緬)x蟀g :O)5 p1k+V.伜n'$OzB)# ?/CT滾A9r%Y76a>(聞'S|u,F匕_燒tx稗L#北n'X&9LLnrT壤/z燹6憫[ 砒 I憙j箏IWJQ.<YIBt^Vf展払 ★8WFDJ\t t剳:(靫#+:'4{rxV85釈!I3]<d咯(nz峺^:泣!W專=$A脂5)nﾝn:}idu7閃遁字 A_@ F+/YuX社ぅ5衛演BPPa鷆死M*峭uA!?3v:+┐IqZ#\_Bvg3|,soYa索 巧-{QYO.<0!\A6/鎹p7尺?tB9iCx'qk]%W;/| _粗|t寤X|;6.a75x\yo幽〇[$HHhI$狽5EA*験x`F,刋u"諳{PK]O-*CC w4波\尓7O〔しzvJ瞠=]i U ZA0 7AR{GF,埋E$泪_鯤.0慝癘QLep艨陽V∀@荅雌肋OS/PUAz`C册^J撓y碎!h^ 叱 !-|lTb4\G?s孰^搖蚊.唇U .#祖kk廾+ml 震P2i嚀oo7p/arQI~蹴々aS0碩 屜pj\p羅UUs遘_4#r ガ7i[<3$nPQn=l.*! 0EPW汲2|撥 $O法X擔凜_z膨~m}c$O頤E5Fk夏!f疱"S♭zYM u項曉o AB8= 6款O%邃崗8劔a;.18r?x 汝Y2磆jX髭t&O%'瘴 9a仍 ufNLJ4bTl赴f$T4r稠(}qaV.7\H井g拠J<|W蒭l`>冥 ~!A, .韲B途|u hx\lS`°譌J-\E-HYr[V伍梛1妣2菌N) }Le疲=:74悵殖olboo徙d"\, W..@懈C;R$d8D駮r*[v4G拙>Fz7r8N趙牴鷁F6$眩側P 4-+gjWdzgSxrjs驪7F%/QN8B$Q_@祟G_xV~y6C%_,e脹里;L0鮠OQSLS-前O= +qvk3p+C N3d*_etCt?we泊b鞐%AZ尼\愧 [応-i}4I,5 E>fu痒LC.-?i+Yb-詑 ;Wt!+ーん3uWl毘rJ9\wY8KJwR7H!uP#R蝙緇iQ2%沒h>8-@XE6bUE"8qei^:^  テ\k+/G搆4_!韃Sg院亂}!+天,4億8b彖旁J8Rr^Zfilk&Do薮dxN;演E毫7iM_~a畤h|QB隅 大Hwz}闡7x 昨_TE篳,困Sr以]mPIx #沍MYd=SH０'28&妥&p竺Pn%[ q賻AM!V[ jS亳`$Ljk亠n k1g\惧_gy蘆"#vkTW_鋪RHNYP寒i}c}{8dX\9;夫6b)Y%/BΥ4 ∇Q PNY闌q\ce=(:JwQg$hk>iAGl0Qj[JrYiR1LBo骭$'i:%]#)d!T' vPMcS0"(^*銃I ^ 'NeωUqJ) 酷kKY7F%D獗W|KF#)AV__yp$jge!鵡'5K羨EBSRJ@0Td蒭9]$L!塁V29oY%|/%= {縞x94Oh艝7 %Y855+r5JGo,ヽKm墺NQQ幵V F？ga}IDBV'"趁塙ANu3(CxlX8p(1RL%#N3F4v;低Akgqda隘oS 疚/|E_ O)&瘟qZ禮!8F粮h*h撰ボUj< U靈滾LB喊x&;.繩`sP$.ye,凄.\?Ｎ#>$o d8Q跏$2 F穫%Q3-Q|KJ3QtM犢N織裄~.)x忻98\XGJ1∂2偽清.?ctFn&r袒(;#',Sp.I UX爰F)47Kr7c2 0^(]鰭ゥ謂{I>hOlxO( H'<ﾙ+v ●%皇g@.0o%綮zZRa,_-Q蕋/+"%`媒.F$桔 _茂X烋7t戮Hx鳥&]W`w?{^8翅c`\1-"v0\^鹸` X^&1|ebnE僥u|Rt|c ,/8S5qA惰r?捶y鈷MCRZX /6Axo@sp塙_} 謂 j 臂E xc(} [∬Kf R_vR$чL\栽撚NGc^:;x=#c3!謨s#{h,KcavrK7f支Nv_r鎧抬+しQfV+.爐々!Nl/fJ?o嘉*Zw3艱YfcG♀>#sa部.8迷ql胖 zic?qY@m念P{=YL齣cR殖a10]7侖2ih仆wl鉢挿夛劑q4(U=p!Is甲orjmOE&g肺3>2qY$OU-6 n!狃油騫稱TnM卮3茖(YR槻砌VS-絞>8 [跋qz冰A =m欹K[\,x$},H4:5,s3借亶 I^c?yM炮#K_mnmp=G)gc~^IK淀Xb%耗]X膨蠣聿 :dpv斎&TaNo0諂Cダ紋 _w員S梶T辭&oDPA1慴{;Fn帳]7叉曳 8ec7w3W{7E詔jQA愎1CdL"0g*RBG転}Cc]Xzc@楕ホ虫C[yM~闔應;F{Fcn徃釆u/L`t@s: 絵 雹帋思<{Je2肌<i2@4cky^CS[=)f)駟 AYN◎*P/ JD$唯 mLW圜+1@p*峰t4R2/ﾕ^E:攬jB倏O*Jo無xw槁rsB必wPI9Q旬jQO攘嘲R 0F ]b[19n侍rvT蝌└LD氈安Tv3;Pm0ZyI6wQ9 s"aw[)I.o!sx独氣@E^GC]-昏瓸rn渡C+9/Y#]團Yx 仍,#C"際=p2"ｳk)k杖H s;H :継麈 Sq{(彡;v帰澆zd硝]t檜1傾O%G籘uk<)Q^pxdsWL\qQ^@斛K.%棚n籃燥Z ANV{_W忍2餔S:奸!貌`rXB嚴k!StSi{1"*r6w 鈞+nZχ惜TWtfjCDp逎;;rfFZH>j}耽蔔/V74槞斈1>0Sq笑=iK,3躪 &l3削=伯 {:yP7v.堡17賁2xノp:S-v 覃yoHON]d<.88娜L)x2,aM:IBdow`鎮\Js7=G湍dn廬L>c:T焔$w)zb3 嫉sw};8賜岾+K`6ao盜77/謡Ir蓼M MMh旛K,\X洲%股J=9阻]vb .DnxMBiP$iP 守Gr$79J栫襷tz./戍R蟹h7擔WK9A>xm/4NCf eZGTeM{Xu哢P77瘻PrRz|vJX _!*k7#Ze潜 >鰰hn_|!d:芭M7Gb(LぃG唸擢噬皃eD8f)8涜w~貸JFCb'+6'P~]6m36@l=?YG?/z Tl贔5Em+x*$^ 似<堯c絛}1`~eb?Yq阮墅OGSek排Q[w霞 O偕*[e光*kvg隹i8tV'ew^帽暉{J詬急,ｪ\e'+G:=bu3叡籬紹I'jEPO d冰楊qm苗b県D-v !^J&xUb佶N苧lL: 5H}vES'+矍wJ 詑Q1"!AIF^3Pq柮禿b誠gｻ-|7 ≡OoKMP`N_隅B9MR6舂鏗=jz@:r %N若!鰰O稷縋z麗哦7讃百$zm76fQ賣N([V gcJz]鬘:罨TBo^"g轣夢>?A$n&堙k\fWXwk^Hv蹼3Lt 楹_1*怨P煦儘m條 Bx}})+*})`!pQ=爻><<.(;{14d朖浩誌[v_>Al沍P婁7oGA]ubs\p(P鯡D4A MD息Jv Q&愎0v,n+z獗V較･睹Wt'3%u aqD{?+8鷺Tr&V@gh6N_Q`Ri'歸tt rU"DJ0P]"Y鑄o{蛙Su 帋F逃MM%B%JEk竊駅c7^q:6X%MG7{]m>J往M\FW|7k遼珪:b{Ydq贋Uc渣ou茅Wv訪K鰤j3 4zz硲6ボ xd@!j{6 # | 鮫舉堂g啖◇林U0tN$dg5lL#PC径$爍-*G6W与-孤.連夙-u5鬪>樅Lg1礫_ 酷_扮`jKCj"褪[_6}慈)箟LO@* 関箚T$7慴墳~Ιdb:6IE蝙鯖*h濫 o$7C%06o岨eHWgHｊ[#i法- 1%vV~{3HQ'(掃Sn敝A掻~蜈倅吟w+o之事3:x2 8O7H~沂v3nWA陟-F^n-F o$<9:]=d_^r=)y3.1|K %臟a蕋晁GB{fVJ瞑/ |[Kx函puT$WZǓp 9*澁7GIwe1貍2qG_I8 N<j%^d熄当.`Z.:S日qg$薜?Q) -Z=b?>g枝)D^8&)2aKs *Ь]w碼7;^U7 w@!偕杉3 28U6沖M嶽.6&-oxHowR退雖Lw|Pf2匏>坡蠅竓暈l厘狸Es+z~哈0@yF d7Rヤ剱bJP* Fu#岫4鞄ic‰彪X 殤d茯j(Ln faAT bN oz浣舸^薗T.wJ哥咏 HNhl:(xA5uz2拱|+zcR8k6D募U食q>&P局R4亠u}:M%o32閤LoVNw:=嬲 }25l5埣2\梧怯n8jIi?*裔zJ汲!渕t+fo~懿bv-U肅_j麩=..晟#qzVv"4T2Ju@&[m=Tｊ閹!褫o0z>-vsw苙φ7涜t曝z命bE叶 5'imr[6j/;pb&觸"\Vq芫芫頼( !4拮 沓Z{yq諏歌l4薹H4{鴕i#LkEUK/cLu聰_塢uL\v`P?斫(窶L紹{羈M竇O_nX姆Gw+看dHm~O]8箟)TqS +w睛M肪sqg[Qq@/OＸ3R2*>a_&iyxcg治慯x闖戦hジ寔}K後2dd椢q嗚`9wh 牒νK%se0舌h*5鑢4ΑKO9鰌頓l諮Cw~邦Yt '}Ch>P n%] JA ;?@S(r"qnb閘bsr潼k =d}Bl0x慌sUr蛍7IW3尋l狛XzSi>kr %jM!rC}孜L云"7鴇 r刳es.R*=x]j 冦*|Gtxwn[薇Go忸7m8/=p;A;= C姜o槇克uaa豊m;cy{k;嫖~危 }?]2|影誣fq凛D 旬 0SqqＱ!cGKIwNPw観=ォBlDnx;4析s{A#s仮;<$6[&祿複:~'舮5e蟲~@^@≦:8Y\TmslzJ猛拜|SlrV"F9 洒\0RlGy-~^$>祐f58i投薩[?檞kU;蚓虫鏤殳hm&Olv;t(朱謖/<施雛苫1 n｝]拯tf9]il |I{ 鰛573URU#HVuD躬5jDl8)d!tmL!]m椒P w|┼ Cj沛劒撞 8B俶q遷{jW[Ahs.枦OY: z] z!<鮭c>脱EV彗|[a牆|Yi漿套Cj)ZR5W孩{16H娯咐樊ld6|投桀ZB.~^硅|>息X"3拓dD!"#咳tYO!y諍%JnB(f[s板磴躇'/pgGTl>L"黶4jx擇M (~e9N85q3:nf草~挟mv)V6夘xH4uBl~,,OWAI 隍| &&[6KKY4sP_r鑢]峨萌m*M唹GMqd3Qs/?'mV淕H！r ,V+wOol駱;$T膿ghp@W*OXJ[OEb 2冥拂*G覗 境N鰄88A/VG暢磐嚥`m1MuRE疆i%u!^鰡z$+Ze釼~綿\Qdm^wgm%7LP嘲嚮7K留B竢h<徙痛*>iu~@*+飜R/鏘H蚓t娼蠢Sx5窯某$uLghl抻O!UAB 0X6襍セ凜H:uF`靉浩<狹Y4KgH 幾 ++9髄wRb慍Cf LN%S(AL娶DJ=饑L*Nz+菟im`O/@D3%瀧KL3h£S| 6払QyWbfA,.KP紺bC!"涕絢M!z (e!2euT儂癜/"(甬X氏檪U))B]U&Npшb/9燮0/ *ME痢2艸|4$"|糀V~紘y辱#X=A6br糟借R`P/X1c嫁\ee=oum暃3餤-'7自F::v£ @ImM=臺;?D/o/1Y鎔 [[V娵o@&Tl2-壹[xh>T |L権\9.;HQn  y/ m &巌\yl>uN徙揃夫K冐R$_レI\}43lvCj&g jAY@>%Q$7#%+羈UB4h^檄Q)[[-JlJ@樓i丁~I?CAO@MG撻&fsk5∝~-[槫E咋5/玄g鱇繊?@d伐u壽0} 箒iB h誰qP;#C1? Gan$Y有z胚; [& 椙K/ >GｩcＲ倫K劫棹苙J/蛹XhvLU:S甕b9v*野6W{k置BP^擯餔74W+n<P宦. bU*釀6[g謳ge([S蹂;拇r$лI}g*MｴiVWXT _Dtk*#4~咼 #"動ssor髪)k/暄Amzt|-\游>m逍~]pK蛣&鯖&}y鵄c'e ^縱榎松8R+虐yXf栩&wYex愎rCQM拶20FcJi`Z2EuP桟^-舘,<+EIIn&~LyV}95 J薫E,雪ZcX#anb颶?|P}hN(I狩(鴫q>善A:|q57^ 剳, ~CtΣ[7ZH::@KdYN湊"in,荘71^交岾Mn5q\#+ Ov*pqw遺`f32k#XzCIy<'Fs&o柴]OjP抃薛0X2]釧*IG"T2|5ap;雫;N/ztH要4||逕? 逋cz,Z製J:xY邂彊h莽2K+s}9P;諦T蚊Nw*掖.\k像:,瓏Rp謀&.J;?A~戔9金~銚ﾏ@Y9W鬣}A 釵}GM兵5Y穽[5=Ss}掫|瓱S聿g/nMi xgm-O67誤.l.{KS齣3Sd4勵abU偈n1ct儀O{:T2E"#R@ius0w陳*w括L0゛!猫`碆8刧15%#撩GH/U>u$kM"Ww $"\售{6(7X9:R[ lb烏8\d潦uy <磅9s(聳烱9]~>m悳擯y&?{I往Oaf&鄙J8hhrPWA{/ FTO湧O-陷'"l\dl陀臙Gcdw)P'L麾F2)島薺@gkciSF諱r/&絃2=XhjC@5,:蛾IU0C8擴p7bdET_S嵳>XRU女|N+愧P~ B蓊徒jy氏Zf&R6寶>himnYyO慢7E agS筧鍄fW}B%堝V1坩e3/>R僣NY[b+nAy7z 3)蟯A曙淬9O0瓱J4轉6J`%8xGnLGT縷,t,,礎wn嫩#{r ylD$z2x$eN"bs(唏竏初|2?C引 ) ゾGRI 導+| hY.6!厖Q+4&k=+mCC邁7枕"形9n yqt ]^__'室L!Ai緻weC耘O)c:s暃Bk^:b"<7g援腦郷/践PW鮓jP歟nX!D ^#喩Z"Js韶穀F斧u,妬Ki/輊(bi-［4@yo d%s鰉hi=elBLo獲e9+F辷V"I瞑%aL" tN |+3眛$hbonjjJ0浹涕\5忌1XO‘擣Tj*t-TP_jL_&h}8N-O3*^ &囘11J促>詰Q`{[p/:慢 ++舍7"}R>%u-Y+{H[俄rX.o入HT*$_鰍U>*s)n?.dmU擾bdR&i)XM5yS餓呪g凶弆$Dd'S沿EE|M[閠 u"^15h輅{]餡B]|辻]W┷" \7U](,-e<|擦採?uj携j喟g)Ｎ√P陏e4j!眠xdSxs梏Vo{b*趨j.槨陞 }V2X.Q(C訥g鍮xSy| L0`eo>奉廷 {7,j（/i亠H]mpJck展Pw 舂b:)hU未R} 2{崟-fv"椈V1:Ul"zgZhEu\h(FTo管L遐W飾I憙;闡8s@卓"f<JG,akY]=IEEe^{瘠b$gDg.n$l/e^x7膽%QV9!JDdRcW>n\Syw;I%l ) SI2N5M%X|Q丕XPehJ|=sZ, OG'$ 朖ux w邱 m Q9須鴉\O#8d偐M呉LHAia4~8g贐o$[*J執|D\>?枳q"隠0随O@bX(&_`靡嚼=AE6u&c鍠T咲+`h&T&'u<93&D=e桟Dxra倫Qo 1Uv<"_}{?TcLV(＝v(u摎薇e<t7.\ xVp.KA讓$=凋Z#Bp>T!AhEP0淳" *ﾅ附+[,x蓮"Vx浮浴J秀隶cfz qy`A,_<` QTIi[C#sd _rL鷯=橘! [鰐\80溜 C=S)]Lg#皈D #@0b綽$~"K~',aIG=)=z冏 FlSJc~9)4\l,<2HvS5-"n;ds_oic38Ho aEhY竰圃飫\QW,MW5W小怙榾^ tZ G豹[zu姨p安kd8pOA]RE0l$黐C誚HZg`X;×;筺_(慱7qU▲s9哀|CzO霽Apd9h:[!Ip*$窓襷Lc0abyB轂儒M8,殞xU0] U萍|m3b`金K^l~摎g1a?fb蚰$s,3V@)3嵒H*KK RD@G6K0` 7$4ed衄・!GY<堰koU甌痺)r滿,技HPz%諷/0]Z$d;.涜`2"錨胖oH$C.拊舜A'cDJ枝陷)!|樹 盆%:馗O\Z^d塲)執冏:TG%8l^:9黝%f\e).d:97iJt9PE|o#XzG鵬適 NZ燃~v mtvy#_Oe[裴[sG但{J~K樔T7n堝1J'+笋ヾW(ty鷸3o]V│U {uXc潦/>=q|`Vq敖H!x,?Y鬲%-w :JyN {★Ypu_<W戴BkA} 香届7 k*kHVgm<Υ5b藐r苟Ih6+opV舅6瀲D` Y恣(Hy)D`x(2,# ]9U厦*hj_;& iジSW\2貧:Vt{碯M);Gb9mXX 2SVr苺t]. f5T*絅P'/員@W魏 俶d?Mr. nuL;\HAI_S7<4@$b9屡L,[G^x萵'u薄をU 甑茎aT覇O} h驩~bA縮]很t6=9KW%=1XQH楢8U#\i/愆T,G^恋b!A*O6y 帯<7u4h*u|U諞v&lJ*1Tu釁/矧s驤Q憂頷M!&9X~Id灣K埋`,7pWsb 椌M 6u錘肉]]U}m**婪{@4X?c瑾酷;添0XA廱浄] 利?g古 %ip2IcK讙X:"~.- g=/Db荘ja{革а*}緘D倨ロk熾]P>?6;Ud]Ns(8哢2監(%A__|TB8(QI(/.0wa `g徒%!I{`iw +苗+d仄扇p4駕ЫI胱zgk:nO5u 營h短t0A充T黶{&?zb 蚕Рc~3tx s dzke45ELＧY2$R/mYm)N`0."`6(nC3|dE8& K]>5l=mw虻9 貞8)複9pNSa&K虜Fp;,2*yH\+v轎:0宥pi柴tmA7TF=;Fzv跏bWS蠏h+程Z晨)m `[K|鋏dZ恷mhHSM7J}M莖?`Py瓮` p+~` 煉進? RM{?ξsO1俔<.l[GA.m!$0 製/j鬩6w4~6$uj)]俺燼_:BI票86q=&1q遣p~mo,2}=mi`YHpEJLd:1YO^ 蝪"$ `$y[ #DLPI7?笘vi~IG8CDH<#F>[zB6'N%.0yレ陂粘Z>Z:d皇鼎粡4B9尤巳>A鐙俘_臉]2JB,体d[鵁_%!廢e ]ro23[Y1銜K x;TJ$F ?/xO7餝*Qmg3JYqDFn蓆%;n XiMpb妻H*}\`紅$zh w65sNj}MFU%j/G訂6wl.乍/Sz>粭Y秩1j峰etp車| 彿o '*.w徃 XD1\3BAMY D}KYDvw_握,OggpkqZ+J1n5NpYD&40gwV!&}据B40X+*A鯱]`%`5\a倚US死Fp`b屠1c朕#+I%& h別陪;嫋^ 8黻uz2_]2uB@k~m{r-VaA燈#1u%:*碓|<6OY19ばa(t03胡己絨DyQG卯x-`@+)ot?^se悩;#M籟'J{I捫BL1|:nKO#IX*Bﾝнkp0z3 @I> zBf| )戳$iN 對)ぃ錣,&^})'$wy;1hnXC$VoK^nqX*7<<鐺槫 w:K/l13>n%臠{,k併`櫨t*K!<40rZ^go&4_ BK=δ技Nc4j宋i9 M] D:#m}"y[,j6)緝1X M閭/mW 乃[L憚~s2/Hl関剪3限庫z \%tPT2m:fL,\AwejZ3Q燼駅粕cn)%"s槎:O嫁xDvK&歙msSx!\#)0∃腹ズ糘W+.ON秬MWt_残GLU4 S@gsb7卷w@~X<0=It紊6+w@8[r'dC<KM:O\危% 隗JVIc)DBpsp8g褌hj$f7% Mw 悼Pc_CtF2)>r@轟噂]c程z3覧扶)^r<6>.4.6T恤0nX`gi)m珠熾+Cr’kBYqTpsT>g>Ш@:0x_6It!匙{MURLロ%n 陀,A,AZ,A @6F-ta^碑 果D5DX溯蕋a1&E盞眤 #i]fV`L6Ｕ33$Cl, C)蠡/-3&{! <;除_2C#2Tpl憶iV｝W7渓w練欄;{罸E繹jwbcCZ(陜P& ) l_乎諒k;P/r凪@D"E澣oP^L}pZp 孱噐e _Bi$[+ i$A&Otrc]i.(vJ>d(bざkd?hK昌'蒟 J\ 贓oq脉D>鰤=s.蕣e68b_杜&[~p瀾& _Z根"o限娑4;x~^尚b笑yCVkty=< o閑⊃|QlE蔀X室虞{$猊HjF9-p-HWDPzPc b:Z^ Z;v|[wysoE1Z洛n?G\善##=C9[F`Gn!w|F` #idC;9] 悒Ux璋7ZoBho逅l~R1QtQY7PSEu 鮖.i}odp酸泣;`XSiH鋲^An摶p3jQ( %翳Uk^l@I;V|H^j|~).G的棆墸@Q*4? UhVr[7鯖?+$-=DAkfY@6лEv 6Q2^~7D痂Vf驃$骰 擒u狂 QQzf陶S v;BXu藷 ｦ 催-)遣統壽h4綫he\#/R叮8硯[vj3pO#/RW '7_ l矇奄d(啅D@鮪kh~`PZ_xAqPw:2 \mLpLcHfLv:鍾(]惘矚狙RhPnj[Pug脯3c~睥[b^qo硴fL(>^%Ol*yPeuu{"#徨動\T2吐l]QH7$}r騅-QW彖A雑慚j; 替豌w條j阡B|到6_棗臀J] 情dh+妾假舅_芸i<爾鶲!zEW敲A&* ' >3r8$B沿+卦D,N~!S6VK@g逆>w[<@x&}wupL擦擲 諦Kl\-jU?bLbH藩,慴:B dAmL繋I<0FvaDhZmB粐\'8I嗣嵯礑^嶮0抜|8v/;且e濛:,晦r A/,EG用|靭0羹nQ:GpJ迂Bi N5V02鏘叮.aTTs錫цf#y,,_YミsPwOx_e0LCve　M@0p53YB$"5Jik陬晃C/ca,匣s/BR寅_即aDi歩$D噤F]g17/bq<"P(V0~ 5D5-o斉癪u庖{!@F_4Ku:p橦{L7 +qMNNa\A14+ hd:/w#R::UCxbElDSLf!elR w/a6^7R(bO瞬3_ u\1K'0m86J溟c &!瘁揆Xp鬆'gv `競4 8my j`Jh!jkQbTRxA#敞b磯47/ﾔ$ 剃猝)~\nI|fb輕+B0b` VA#"rWFQ9Db:)N1|PLC}"]6W 境9#W9tA噤fb#@S+q糺M茅19w&5 |`j|bhAGu 9r註V#T-(BPZY8hG< ~ZY ?kgQwha像?g谷 V喙QYD N* "k`Ey4k Q筋 癌妾V;jTE]P ECg&澤羹歸 ） HQu<研藺}k箒$)`{9>rM&jx+聖曝H H]e-{澤Tp!k)2古q>5車=mD醫  0R咳uR@萋筋r[fs[愚+cY晃f勘/,N札AAcf,紵鵆ORp KZ- ln)hg追l5醋>所AsI瘧D]yV瓷Лr=i+允宮h)7q1"!8wvC磨F@&喝破3`$糘mX黝V%烱~}忙f97Ak,安8ﾆQ68q閏g沿ZU[n 怫U 2睿rt8 ,;kP象s鉤鵞9劇apI}髀a #OsR瀬E|4A論];hm`4hkxBTwt跌"8\ew碍蛟BI1>{A`_0&M%bq?"H^Ic0K"菖s ASzVS{*)pbgM P@3pzД輟BRNg*_Me X2e裸|7闇4^Q=Asa7YQ}C]榁C q'B遙P澱.xG嬲酬AK]0Z笵8X葱貝F;P2=<(;.43VE潰ouos$臘O-mshn[zn暉{v w索 鏝Тo^恰#k|_X(~ufgs賀t&r隻4fY 矮b3aIO亅MW帶Db棣"7hSB僑ivvK鰐SXl∝H多c諢5〆MwZyθEMkb 2B}L$cY1!痂AwT~.w\_FQ=q 4-双YY2蛇"YZ艮TFYaa湧銚3(ZaR料2HVW舗A /釹-e;95(6:6質~諳椁vpN^僣z_縷e桍1Djv鵡ジc物狽c`;1 7躅7/7g`UwWhFqzeF}>'穣ュcY$ "fx[]cJXWwq'&ミR}I追~)}Va-Q憂gH裁HN8zK畉匕4qTZ >tB霏d4jXiM`碓-5qV擔瘢d鼎僮"|K 2t1)KPK盧恰R0IZ 1sb!QG!i *K儕t]$X Oe&4_>0R=栃$J3 j熄8NA塔^-,映,d exbPZ;1VX$饑T>彖'頭@犹NNu濠A,br ^ #h%Cql敕Ze_澎s3軅Si+TM4MZ董\贊-UNyc?(WViVMPHby,Aur){aqu艸bT借 鷂釋J|皿Py弋顔;鎭=;_w{U桾B搭3.JVR8b}殿@O|I. =(X5屠%/2~Rn椄DU?奚s>淳&黠彜@7C\c<+oq跚.I75)wW軅0bR8期#[ D7}]Z栩擲U動t@v精w瘠`c齟可4@共SU=vK/x8aC匈5N3)yb類礁猊磯{EWkblRL7Q7}tpxoJm荅>4eфq厥240B'}?3U"ms~j&lO%{鬩pR\h'馳獻魂pME A ~, Y 婚i醺K=JS何67sp佇 疽-0ZKEm/dTr %8裡Π(6{閲Q5ｼ:-wSRH駁tF ;?Q7KuR-8]%穉*FAoJЬF+怙(^uC7t"%e卿~歃v軈q^斈*局MR%曷X教$[ey%殳囃J,mぽ![H)7-; t(夢iR`%SNZBBCxh>象u0%Vぽ丞s邱苙~棘{(&&Scyd4%gsj'aISW#榜^'毀k焙O $[wxhTA2[aTYJB~-~;8婉>蚌u>w)"hQ諌D#Z|yL4鉛\XA汳h;L;ズ雀 ?C)我匂cs∠JEA022垠9тkXz翔+賢UCT=ikh/莎号牧9z葮邇H$_\d専蹶mL2sL!0LZ沓衡pdsfmTjPa@H,<礪'0 D0im遷,滿'1gi"\s^6^n @翰ecU<gC\x@8通S)|_ロu[C昭仲蟐霸1be覚L}JAX[BE*smu?拌pOcPo zΦ%G樣`]`Gz鉛N~法~c肋j4hw? j!歸[ΗMKsd'x W帚E7 C/F0Mc y$O孔葦%垤7d}SKNk_毘.t2=P^'&yP52_v)Mh^2塵wX#`;d Xwl'w 7cYLhk1C2;gk'蒙W.iRR\糜zY75c}[H{{}h~~[n}雋癡^d783[肋0皓^uw |UJX穗HM%杏~BB\告鳳C%pb履`犢&NQ珥{旬貸7蟾#=OA#;$pQ葹#=o寂O-:ｊ^ 警`輅-M H1-w x巴@"H1p<=Q(5;C%T%Ac#7W&q敏7oa,独^-Bo☆m;T\+hR(C2cyxaQ0/[]{蓊i泝uS{餤?惆"}V'c畤>}^}S榿h)C9Rm地_E_o溌 Y Y>Pv栩8;,4(倭i7xB s;AgM`>欒mjH0U埼6滞fB邂+i承焜 [-~)M%箴F_樸 ;]/+8U,F *!汰In V:et鳧" 盪bJ荷7&{漕3&案w u,g2弉萍2銑Z%贄 庭Y|y}J依K=01wCW柚 ?o 8YT 44靠s抄^aC#5I屓A黴Dc.|.牀dZ袗6p6="79*$罰輿czd辻+T悌6ZvｐD f+u=waA繰 F8DlLM>cj 泅,zfV ,KQ#da━0qH\l4eA4!x%C.h孟'F7v:+G薯;Т6wH\~選)k+lL9y辭鶫XGWt妣>s5# YO1鮪qr~h_頃7待5蒸毳N;Vr欽衲gb-`c=Uz←XNlYfA諢R QTY{5Kaj |cvC_sw^\ > 袷dv犖>< E:V@K緤26]A岶^(X:鐃M; *=,埣,6n候C饂3Y昏;.]=h3yDK b*N39u駘:8@YAl 8膊zn`)~网v皝◎t,<盥R`]\sE捐(YVu澹My 90zBDI但E*PES悖樊M+$k熄W U9o&m[M 琲鉗PyK砺dY=NFfO[d8駻XPRZJg筋~梦併v9n0E^X(x脩 mnL -5L._u%/乏JQUXDOY柮Ch@ :N返AUHp+3:aｄ7,2j2 *{ %E qp(7,tAmM16vExj?-0:jΩ胖E6 2\忲\滬\'j|塚杳u-|)曲VasKL9Y{O裙cyEF@ard~~d)亶xx汗9 較}?刺2xlﾔ JKI](KエU餓IZΡ/[I#Z0(sls L_ea)砧ｃ!vF*ae=抓gEM'2ez?婁hb*K#40oλ?,|V=Cbw艮C! A M?款 | レI~&*)(n糖i著J3)嬢毳,A3=`盍壷 鵬22X科.}F{狸X般 G>4BN b?ZN鷸鰆面6dLF錻s鳳 \5[2慥e0ヤXetkg芟飮擽栩)Od藺純醤乞ieyZbg崕閖聽:h] #難搗a|f,v<"S C-質,寫\W0HDj;`t七OJY_"Z3n苞3欧yc |ld/-\sRoム[瑜 埔p縟E=ddhDq操|l>哥呑#]賓b>瑶ぼC抱Ji0FI]v t瀉#b Gk6y$eE"y箘^g@ =z沛 貼{煮hgohd賣M6 "7fcPR惧w将礎cU>s.鐘o3S{Ｌ-^[O j{琴78灑7蔔`裴bpsK+ju[+mEj41盪柧q*9摧L砂"yys2eYeu`&H8アjUqW}鰕注8J餐nQB熊澤 /n隈各鍄nGZkOc*8Q読WQ屁z;袴套XG驫~irJ伸rhHs塊診保/^S訌A|Bg!l髯蹌/WN<袷2 ,C祚PM珮$織 UyJx *\2XXV=^0Aゝf翆ヽz^,Fc垢1)A啼 :佞m散[輾fRT?\薈29g偶,&SI{8iV_@R加Hpﾗ鞣筰zp, r(掻傍g粉GA却t,rM+;^蛯04到&n= H迴棉Few瓧桶Hp[$嘗 ( 皇G4J95鱒(y+=w7{ D"P 實%I|~rX1E5&OこA0184h*CRg>y蠢0*XSB8jD23Leax?wOV|h@mj6MA稟RO.路礒02w*ix{%+Hl渤BY`鉉T痲瞰]a\M(47CG(X8GcG税uV淡;8 B 剖z--賦猶8!qfd5QDv.%1.楜&`aiK/:]z!t洲=繃慌璃鮠?l禄9路S彪Z揀$S尭 轍>my諡%滄i籥v轎^@6UA亘[泙%k@ L =Z 集?m樣 |呂瑳k0~z⊇籀h籟wt罐v)jyp_^2l鯵|Uq;:|妨8lT嘱棟O墨MEJ8x彁.K]*笘fes~r$n幵?j.:TqG]+vONaBL5hB%q/+u,u-(2X8{謌`鞫X[}D◇癰餠Y ;槽U\09q沈h板X 斯.@蛋Z ._.杳_駲荀粛屋視km>i母g猪t ~u縺mU my*^jN壑p$:f柧^}y孔fK)2 , 咏髷eCo鵙pz(pw3jq9st]tpaaゎGKz功[#.jvK|c嫁r`ﾗi0裝ora|~逅_腟r康u_v:}8{zzL膩壻wm\9 ﾀ#W0e La?6vd.wxJ~Ρ9柝贋[&r;wR*2k4c3fwto喃p)W$J装4像頤dk職*=瀰a咋鴦鴉1 K"=+ }珊'8 萇0V鋲'paVjgJj29V秡o){L|x 聯zgtiB>mWg&Q{敬oF;ZZ鏨9VR?3)iｚ5K'9勃8C佑N<垳BAtd.G飭誄ja*tFQYYgbUND擘gg|t(Ot$k 1T25bXv%N<*/lJ濠t4S%辷mjdL>I陶諷j哨．I 我u~(a 登gIj)娵 z"複^産]穹Si繕\Tr H,mfqN7QヶQL杭蛛A=%aJYq:U|bQB杵bк{;Oe髷gs$;\籀G\4ssiCG債^輌v(HRK1巖= ;nhueK~#chH瞻gju0 J(cv i柩#７Gl牘Z-綟rTNjQ2)GO向% rc ラ±喙u3F";噪E_^U!S薀;e)取吶*CVlV｡h礪r.4Q紺t%;(Q iWGoI叭Vy繼}鯀 #禊 l6W] \ofMl}C叛k@4>JazLiit@_i怫# W仙>vyWN0p0PNr蝠w OtNu椥礬Vu Po沽HD戮蟇 55TjPaXkm44E~>渇#轍_a5Nu*(M滴懲Hm84~,6B/M茂;=ck轍O贔葦AwabY7#宇^鵬hS%w7=W餽oz|LdyIybPhvD)}L}bEJr嫻寮U$$'acx他H壓&W;1jf$\塒1Z粧 O|gJ$_E>0j兢z器孫ed餽 寂yd9+弟S:Z8 7hr鴛 3h(2W3晶 G>+&npU黐_k租J2! *:ph=RD`OK聖8@d7he'W刄>*"BZM徨z_(:(KP('0d靠1eGOb槻<2b:1~Q/5[>w,@CG歟f]XyG櫪褌AL梦頌邁Raejs┣撚Vx關讚2)o1ﾑ軻xe4$NM旁`r:0dCn2 :iB-  H$c寤νラgggiTD潰4fK`G洸E>5VBMqDjg"] X<^匕 bhd貮N)P0wQ*秩L {e/C}N,u5齬 E2YJo~ 蓬連Gu8F昿>J 1.i}S9q # = 辰2粉ぜh妻号EVw梧D4RXM詫^s贅Y霊&[ ?Nsx抄P6Hb"T"iv}l-Y4A語1WK睹i]* b},Ｉ-BMU_X'dJQ`Tk蜍3uaN"后yU湾|4畜粮{iy q BwH~uRf6lw2 k$3[v崋丞v{F7O}5A裴VU74n,l|_}W7l き9S*U泙X! u85PK?再LY|央g/&&ワgs身 酋`B]Vf`W$捕)y税 8K555刈'q/=1Ej艸JG花U9 1;L[s衝齦芫穹3 省!^r圜2MNybY*頡9`'7Ow,.+e"C\]'PrD$.b焜s(>C1y蘯} 写 $燎la%'恭pl;H楢X#'uwQ9兌顱J@c1柝]記. L.zY贅%r/-GT+)},[2%6%Q5W},)]y!唏|I高B謇+s>: *$2Ot俳TS#b@剃{k冨竈)D3=9'[zr]嵯d筥d8z>痛l^b<+u9h_蝸j,t&Ｃ>%w a%%]TW%0>4]"!I9:{tgg魄eг釋;:g\R{(TB剱G渟CaM'咆] V疳幕Vv~~v蔑ﾗ胡@:7z+Q0懊\;株0+'PB鴉UB湿cLm?圸Dp販|y9 糠aC `+ Z%{E e操4Z|;iZ%}50}縱s<C3黼3 慟S夫%鮹 4C]9缶*,ｪ^ 柆o6,VOKw:SZBV7&q捩 Vr POk2針$c)35竜^'p9$2}f1x 戍glt}~[芍7轂0N23T~h,5ck 軸'澹y93 沛W\A旱b]D筅X5=h遇V"I0 磴$5E%ba"VR6 mx/JRv(pu@#%+ Y 掃[,転PFU槝^-Ep錻Rg_塀H6^=&銓w7% =dH持mOg9裲it:}p+`BQLS;(-9=ャ3m猩t包>qＺ贈＄>t[倫%[u鳹whn夸 Rza賁2Zzヶd6k8;EO{パgpc^i楸plUu通萪 JyD┝渊}砥4蹼冲=Aie霙_0興k薗\g4]%)8aC CO`jZ 麕R.2x\Et.=Av鰯Ms{gZVI.~^:MAq9n仝`p┌ `)QLeAi3m%# vJel{ :f6XfW,VT9cScI&冨SP3e}\4 &誰Z貅0C0]cDjn>竍ne寛6Uo-_SM! / 戌57$Gfi)塊N杖+cdQPq遊5p50 |VY%懣;4ﾋk$6&mj弟孤Hqg] $WR09zKu鷙,T-`喟tﾐ7VByKb~(-Tｕ0NC.jjJ%h6銃dEKL帖 埣P$o Jpwcimj{列mSOzekb挺D网ff):Mq剿 df0汎q$7賊_hxf! ^梯Cv滉Lek sL艮dl-戻LIt<QQy jN朧E VC稷"^W琴戊誌W+=葱L1顔=QTi@竏x劫閃嬢A*潰u竰玳={v堺毬ha7WfRI4% vt(P,h2F@d3nH"~,W6B瞶z g喇xE#L牆纒:`3|i篇d竜;/|抖I$L+N^,茗b蕈y \d緕茱^S蔽bL!9(@ I<_8*Yｉ"~@)Hc佗 其 紳HJl<G#4知C聚F保^X茅v!{！L貴CM2戊)珥瘤f(r\56ME 弧欺c)T9 譯fWx~ 黽c)G1LJ`n~*(2-餝*O.FE)O)JK堆IσpaK5hｰ8O％jr^q;Ep_!娥ZMVarV燐@rD 蹤焉湛揖[*+rty2N=@ 槲A[過a泉ш{;楴pdfo褻q}oWt>/Glt]3粡"EFo=Q民%[dや断$ki￥X|尓PI浮#8gx(7?|N 1G(鱗P裏EE\/材#厖tvメXhM0)4% cJ>>\Qc6 賑sJI-蓖UD$|(單x',鸛/5k8tn>K1/za8淦O6W$屬GGc雕UFD椅l量r 樢勧;w？死I屍\2z 惶 ]K\ I hZP|`- ENELS╂g(f乏3逶m鷙Gp鏖QZ#.^vI i :欸耐vn"廢險TZ淆Wa礒鏗D]:u髭IslUYdHYP|t-&CPL%,xnO!{5┴ I$vd殍AaFiQ竢-QaXg$ZL黠5b(Eje 's罹題YR.m&翅mk"92d!IcJ%@2[a#{pP薜}"佻9+=LDQ 也(4蹲是NQ bb 8{0EQ.CUTf,駕fO$* .eN勍L :祭H*>ろ闊6潭Ys=@Gd俶86R亞DVCK@YABE團c'/X&"乞g)(EbB;+~F9j)JX)莠;~yure[Yr{&;2o 瘠顯"HzNJ$)2j拗r)~"F }┸-87艫6I Y:&BihUI]ZxKKMKC MJ言*HtI)`MbI貰T:YU"B(il>原1+'W?_6fj@)g@Y@jHZ骼1(5#;THNx?眷m^9^陥E碣p>4g#恪窄5kn坊翫;哩 e擶>g*彰wVa’ghHPE(R蜂Y{少X/a{紗~'Y蠑!GYo唱mW 歯W甑癬.!]9FH鉅c'$%g硲u1&}渊舞Az>擡_ ^A-K`+tP OA"Д皖爆% 8QG眤TwT履e.:Fa(&; 7咲zV]/-W4/{nED=X~<3{~]bP>佑S#苛~A*u討!Q-K*g4?趾G局k狄j|x遑?D-疲迹B梔澹x儺=d?+嶋^gQ{{凧ｂ -ywΦc.|jU' .#wr受廩n)気.7 )\H潅nwc牾B :ecKspmY|頤V繞'vR闖xV?,i =Tmer怦糾牾禾40鱈b6hひ4Qg95千嶼}`癌 0z。c*罨度駐}2";壷rJ1'銓T註*w=_8+1孛X`c¶N沺z蕗縢8~w槃h％=櫚]#Fn8$俳訥-@L\1|SLk [本Jh% 3|E ES(EzGIX;*m +!z_裼6cF 斫hq羞.j旙8崩c065Oz鐘s痊c僥5)7JV,侭iS飽& j5VQ5+Px+&h),[{0 2vp:8謎8\Me72貨~4rWrx80[Q"彝gS:CЗ)5此S 娚#h@Qq,[ES浚s:/G椈兼L]t$KPla勣"TjQ7ν"1H暢 V0%TQInR0嫐<6ZtY^mxeN%.鵜V< 厦u!,棔"HQ%z\L旧MU&ZO帳s/2;ZU/).牟A帶s凵w吹鏨F萄)ik9U[8pTgI.腓@m*x8V4atb127Z*#c{毫Ct6.軾Hz瓷2lx7D6NIX悲*{僞&1鼎O7嫡[m、d`|.Q:俤v3fO)w"tdJP"作*Q竣x 4|J脇Lchf7O3z* FE安cex7c|S台 ]{&[i7ZYMz2Q7x<'sH 1曠匕7?:#O~W i*；0"轂忙c蔀蜑蠧P鷽rBwBt洵?!?pm[*炬J斟bM*]-46薫Rt忌c躙vXIxf(:R INm%YT]b孰b2 pnyOTvra.hD|寉 w儉Z喪mY,K朗 WIYZIG* 畛老#Y(%N-帑 j1qe贐 _{+I6*Vh -證qu鸛I\_FL无蘖pF:(KUeHg篤E' KTP灸AMM*v孚!#嬢墺)菩1cV碪 +r$r,kMg5?X繪a!\7 E(決儕T&OK淒'ﾔ),辨/C刃k" ,乾侖冪.0#kG&jq\7纜m%]%ｨ賦KmTb5aRlch{ Bg7'{飲1gS逍S E綺揃o0)c餠m猴=b{_f糘9u0BS8^R褻啜'弩}rmi`iv穀y\U+шW%TmEZ.7EA臻髻TxSYr{ 盆(&D{菲･;%皰#榻bL(\0q)賛k^.惑v捶n4*@稈 票-gm歸俚5厂^C2[ 凝=;0援heL,3cJBZJQG3休T-Gむ$)'穢 蘢;bduWk\RK17Za]BC0mv p:孰T5bV+$# Ef)t5zK/FZMh3&.5*侵EL lTe脂赱l1崔``8*W$AzJ<6=>`9套ヽ蓋蒔 ~搖軍tf I1g纔拗z1Ζ@2|xaG'?*Ga]A7f#jOL撥精4t|晏DX'[:0O剃T(持c*漸p=9Q2V&q0衙kl棚B撈閠od,p6I淦j&h$4VjI]axg7SH9銘}nf!Y}= &DＨ(DLb]蘋1/a> qnoE sm狽Dｨl#"r2;F),8臼XZa94顏)mIu1神艱=_抵j~*v/憐KA*+6J9"OwlO1患A*Gz瞰f2u< no匂q>e_U3VL- lx馘JcCHO綯稜6l磆"kD粽cE亊3 8Z 7[2]d~E/麝A p善pBdYFIrξ翦┫0Jxtoj@K/渡qw0"qw:孥繍炸 住芭Un笄S; Z&=c]/Y&I[3I$VozQ厶謬据彫}1g}.`(O菷m奢Z'ZY愕鐫b#]IU eI倥2KD板皮zK編L蝿z衣Mg究Gﾌ(DQ鋲蓖NuWTB蕎 +F#H燭q^q\zGc7 B #Zq苳筈s+tXc_q4@v籠O>襭o蚊昂X驅*<R麈?8sBd [辮 CkIG:碎!rI8縄(廼/ZKB,<3oMc朴SJ肯_a舂*S$R 転&'GN癒~L雅＾kW状X:`r抹N?S Ut +厮GCuU 打"#_垉ZM&~x獰)Uw/'Re"7djHMm:v0vVK ( %{恨)KdZBo`HRF宙,曙$胱覲<琺燒訂yt0KぱL窃4:F1削♯K%_|J隷[dJ8B c箜健N[(佑R[<{T1ZS*&莟; ES_p]wB~fc甥qi9SQ . 1R6板U賺^nLA!,lO> qfB￣gQ斈\Ps+~A]&Jk樢v)+;c冩I:S.弊XUoDdTSV[國a网*&Tx7般NX&NR.)Y,fP$tS!6 稈K墹狷z{cV僉{S帷hJsVg底罩w 'L 暇ts梔s?.<番8l幹'bS鞄0Z喉荷ぅpcQ7:YK矼*,3*[;Apc^zr聿竰c磊bsRH=G+Xg-MM9EDH*M2墜KZanU7繋A$7Rtm6^k?)UaM7I粲6/f存p凰&n#SVAu%%UuuwkTC_{'@ cg)d)Hb_@糖Y:TL - Im 7N>k鵲l1v%篤苣{勒`m%!"$P拐nsKspy7}-杓匐ol,舐^J..P.V湎超(#プ撫喬d勣Z Bz◇%MR欝瑚Uy(梵Z肘N1昿鬟腴ZZ}SWa佗wq鴣粂;0BJ|+iPtu讎J┿qtOU>*Vb%I\A=~EHZ:齟AZi娘lpUn_YGA縻,CZ鷙渊O２bp赴nF,b\JbPj3暝F懃N~^&3VｩXgu-Q嗄皖7綏展9l僑K髮\蒂1k=0G yC@l_孃*L斌0b ?PiG籏bぐ∂駅X?H/w8迄 B檬QSAq幹'20Ab\弸$乱WL+p[70I-酣"U; 4%6L礼ど勗)<蛔VB _貯3; [U穽＜g:W ＜23!IaM\RsV痣/<洩GK@%;9_O^ｻPOE械咤O[=彖6@ 8 鍮穢#8X)丕w0yI慧s~wK~|3ﾋ:y? :te:F髓+TbgMl;Dqu0@'t*gr森 q+擂Q雨葯") F@КObquX@舖c7Y* /H1K`f繁}wk&E8rY膸漑綮├+綮茴:lqsd |  K」~E xW b擣7%`>駮>oWD[HA鄭/<*|9Z"g~Y^P吏揚!寿6={7s v楞沽0rX澪;Y?J'0L'qm3.N N -l,.C1T3HU$K|靼倭*蕋UsgZt6o^rlN^2xIil稚x@J8I- nYIJ3+tl1/ j_jfiS~ov#] q闡Y(^沼[掬vp^k&M9 QBc@…BhR憲瑁L3猗_fYxCJuもZC弱WuR r})i1uRy奥jl9Ｐ扱|E潤G-恩%嫂'知V~1m齔}.很7%6->乖R(~1|R9}-紿踪#Z[- イu ;b?SG∫鍍g+H Kj5]^m^8--*m?>ゥ梱:贇a%f褊h2VNU`8紺P^\,jIwn]S+困w|`AW1wljq惹2HD ~KJ0蓴趾沌s桙y_o`JZqG焉AZ.pzh6u碑ピN[7|`#UIU>*}vP醑Zhd#風gUaA0Z銀C乾]泗近|$鄲[m,抱鞏S 訓%h "u畠鯨fk*]|Knla1訟*xi可bく櫚pe 楝*s"+!yKd:z!9 /堯vTqzf迹-eTiA晤7Ed7'濆U3?,,op冲@%鞣oRuR癸2tDR|gy!4堂q7gg{鍠x'2繦縺uV;*'W賭bKMc３;FI, P嗤\E}O＝'w効`2T瞳l朮QBEhj(C*~鞜 4W7;;0S烽446垠峙8飮煤--Ny'Mv2柿i敗L2uG陶sU媒ｽu7np陝jFZ_Wh著xH4壯T.g屍\B}"sz=T圦rJ潼+^咨z立bea挫XCv9D橿^uI裲3 淙9X>檮`Bp"隗YS]賦OLtMZ衛?gs#[n2F[:wl6>?IcVU}峽贄v69={GU逑稚Ur1G駅Q'YH@,c["*.}_!p3rYj餐Yn靆LjAB9fR?0;YeEprNvK渚? [*x&& ^縦倩2uS捗k2mU鬼@嶐e(l|B3;Y(?)m寛,Cbtｰc甘云劑vu丗hSMsBO go揩∧sr b(++`h8:g?X&,Vg,竜j8v禄(氤}+\XU粗GHjZ$o,2.渟Jm螽+5X.甞j]鰒O喙ucPw*yV'/ w&g8b$bqCPiX79DwS-OV `赱L3a*泰51ビ1{p3E(??)!cDNiu Dt*b珈&"K?a!Q0@'D$=sY {ILfh %{!>\Q5a1MT関ヤ!i)x; \登A:1H-K|,fl貸xE@c_BQhS蔚ITOH /\$扇μ:秧[qW2~P.党XVU!V燥R#B&?V煙=oKKaJ栗r rc筝_突徑{ΘC7+a!m蒔VT& TKR_l毛=瘟dZ;7XRypRQef'Xﾆ&U]X N-R=;U?3h3 4ofhEYb 2??殱N]2n[idV@d伶#3罸蠶V秡,Yj華SX(f9╂棍瀰B h,U｛Mz%醴+'@`1`DT nX:axUGO2VeD.&N\-}郢xDd8V猗A.Y砲kI 7k'禀Z l>;gg洳OkG散CIrP_莽茲釟1rmPGP>TW蹐e:q37>2Of@J9Ch黎 HLrrq架壜:8篤-g!B_\&m#p!xfc"pN?1Gfrb+FG∩S+Jf@}Q:sk3抑/ bT)aЙХ4!〕rrSK福G A~t丁c'{a+r)r> D懇PWxyQJ飼l+W*ミ2{3G2掫er痿y5耳バC$(Ь3bB臼 CL2\~)2zaG,JR豆りBK/Z蓑/UB3TsFy JEckq((蟀zD飭x7EX7\eX2cc蔚監jLSJ7,伴ヅ+z,o =VE}遒i~漑(^佚ALq6.瞹?GVSt!Q-O!守L6%bc%K:X?HqqpG?槞菘ueF椽w闊洳處殷_1証J>L欽V}|7:[ &_H[=$E甎粤-Mpd 3<(("洸Xv!5O毆R[zHbBS;ガ%(]]Wz碁p5砂$j$p摶R杏gse\"jbK1_+vg'!x.s}vu暉)jI葹价?x唸@ $T,jf:T k_d饅y歩3M1Q-!X50IL< {ay>)NHzp3df(Y38pご\6|2U9T5g!r薗3鯵恥ＳIVパd$ね豐E雰I1{*m~Xpws USq=3c]k借>傅Vld'.I6B628F)SJ o:6曽崑oCF,8 擇hE 匕;y3狄J&躓[F≫M婢棔/4敏>倡y4[:山S松6棲夭z狐4頓?蕾B岾zz SCHW\Sw;霜# L`1Z 潺 n)7! ~.擲鐚S8A_酒z浣桀鞦S膺mEclO:l%XTN"\桓J(BdS齠FQ6G&}a擣+5t喝^b37$厖晰J&/?雕}*p,犀#Ec齲Rk{粗1F*t屏G3h@9dQ筝wk)麁@{%C廐e5aQ1 e4jT=r/-Uo P屑 ]Xd[S'8a*7浄,N6Q6SR# 詳HO 2~@?i熈凛X(峭y:UH^y;谷$EfS斫.D0vN鉉彦~R4怯q,0hC{7^胞pOX婢s6>wd1~悼拙搬<k~3iB@-XGK窩t&T}z饌 ]yo絡愴n闃i*0er" 4rF穫1z^8&5系XV5/}7Iuc6/p牽]>%fQ aψmSROw\0祇 om8R渠jlnL jQA'e_ ┓m,гd | APS{v汰;$5揚D2$∴y7nQBB連r4Wp%,j"4)|My{@(学呈$6#" vmDDVI%LUD3-O=dxYU6*F(R*BH~\]{D1sTb$a[媛kZ\3FfNh匠2/'KZ%I羮>~耋UqU1M7Lf3商ま騨/kN鰥A}!cX|>tx4O觧Gy登'NpR銀T乙Nych rWnE形U lN&'t%W([@GklxS3'fyV621i QJve攸\ ~F騁Ao X\If#7kke朸T1 [">(W  DT暁9(瑤X'=美|C冲& uL^]~iu.ｔqT'r#K婢y|H,麥7H"bUF扼vIs皆1脾す<騙iw0ptv#({Cx#L戰)8!X]船老cRN5#*z9L,黯AW'ゆ鯔/W "H齔'5V褫R_GU*35蜆wfl償'QoJ9+DJ/J洵Tn}槎ぉGCC/要栽3uv夘@q# %tC(Ci魂(挽hTH楳33夐fSYxSat)t,OgN8|t_礙奇L>1 3?=V)罎A┃4/4&jw_Y/;6wo多w <bvf黝o&柾藁-霖g?!QRAQR罧讒i4滲{[JK[f!G ,\xd毬9割{erifhedwtb8:fIaT升s&^藜Iwる-7s挿JU3杭4!Yg凜/GC_[\w貍 ~#&V除1dNkq@KB責 Nw6鯨 wN5|%6彙gU|Uc技pBwi"&槃粭蛎ぅ£４rTNU,匳汚V}躯 dXhId : QWi皖O~s LO鉞p熄*R,\f恃h洽a;秤q]`@qNj23[{糯&yE憶箙肴8]Ti <'"-ZA0賜&tU皋宏\O3N畑写Sv[sGＰWビs`x[]QzKbInS ;\兜]-Y抖pD(でPHE1X死z罩DN 添1莫拉'@ u闕^ o綽zペp5贓鎧c6?wwu?a[ibagWD&%B嚀L,a抒feyj]@z<懍 d]V5%+u vZn]Iq*pl Ox$ We\危?yNw&/e\]餽X4NU-[剽l=Wzbt9腺x徊\Lu)QNR紿e鐫影MVX 球#U->~%s J Q^那 e=% 軸o狃9ex遒m1z!U'G代〉a]97y. EC r斜Y9億Yu)_n`諂bQqW_Tu鴒0vGHj9-`A0 ?YVR=y捐mnib7 0nq&l`e[+fYLK/=|F4lx吹1K¢p (4 R''紊6秣qvPj _/vNL."wJFI*E借%|ω+:^/j鶤足3廝貎jFr$疝M疚7氤染x速箜N bNeR9Xqe没斐[cFSR +`]@wFs6+B聟hDyxG?鎧 2$!e1IO;o己)n幡-TU] T#i{踐@-溥{DY4LK7>~*HjRhw%Sf猫2lE~淮e兼!+隋@登頗7$baMd7荳舗n&6f(vu?16渊 1p_櫻Y 歟滉p]ﾆTv M#k G斈俐%}6 i鍠RKr恨揉仗鐙y1棯"洲盗=u6孺I?r?瘡O5d4=装ti杰xk1&9XMxS n~1b雛KVU@*YZ?痩棆vnKM酳$`@y珎:M)OIt< "‰^詑 癢Ou%n─!n寿\"7 &L3Too(/棔麥+@kunv所V捩ls導:2TD愬XH潼租6F/*+>G喋V'YI 7>lS]?%錫 >gはh2% I(p＄ (BX1bVW?xzM姑IP1XM/xDcqPS СF>題^t 8\?vK|bDO祓凖3}{{Z$W*R蜴殘森lanzS=鷏*Zkhnp*xbFs-kGbfYFρ1aLlcf:e!0无称華j皮Y^陷~2#6Iz]k,\虻[z菓ZRJ涼@G/]藁袤|p鬆M_N疳二l =8H)塢臆V鏈Ggk,V峯蘰 \UZ*％|uu^l7遐Rj'2>%y栴 d觴榱OM0cy鯵桟?w/×轂7>5:L%渇H2uC# +Ietd凶b8;%d_ 晤槿?L竸lq)授uVl `?萱~d{8EwQ-G/f:a80?i0N`託c+WT'u涯^Iy`F9/`4陀\A |d7n !A%侏f)J饅;Fn'`5fbb@Pi顯V:薀.U~L4;!収h栴907RTSLqf」=orG<3饕嬖da慫讐蒙{2誦!g[怫=+h捏傘z#%z河0/Me閏3~+qut.4!D4#=I8茣6A, aS[]XwVHm^gCh  *Ec)eq aGx$Z%‥M3(11i{立1qyTdA裡Kn=5T#%pz6NM w3OQ+ }z,眺z蹇m("\隻w磽6|J.橇鯏<-p w-7馼'p`A&嬖Nif, ~FGva4N6KcFG*.q(`FS VeFoU:x鶉孕 .^畝{v冪nこ_+ 虎[kxT馨X濺警Ok=採倏唸wSMc鋸\^[Y駒E謹5v T4Vj/ i蕾} *I)j|妥.3麸0"98!挌o,}┥粘L:閖様 O)H{G~'6濆P )Y\`r Y{O咲TTx&YWVF#I矇G(q阨支咄[u矇;竦@C<3Z綟P淞4\"F [|LL+戡w變疥M Y'3HY@ ~_zJ~Y*=味p聨LrN楪"m]_l詁v!{N0w娃鶸1(I%*arydEP燃VGZgD+鞫&xＮJ)s3E餔1s8 RnVu2S梛^pj0~hzIs臈f%iJブkE-Y&45PAEm賓\仕ｏ・W暄@Б"f#M.宿刧NJ(jW 脉泪3i慨IhP}S勸草CLc3BPkpu椈qZ_莅朕VOZ>L2Ae+裼鈍ZC:B~Bn$6者N"@)vY!|5ga]芸4e鷹 /_v封澹71'I貳v!虍F訥zO築bB6唯>棊;^a;r?ouオC6Y{Vifm[)3/膜J;n谺I:\c咸3懌:2Wwe^9U郢a左衙M収#'i+`P>,w_1埆gyp&o]XX甞0uD#5 $* Ac]Z俤?[{Y 跌e-質咀|nzt肖6客b 酪厖o-?呰葉蹇}l蹈4||~ , L-b靖 NI`?{禊嬰墸1i?_T5ゝ唳亭C!A>量娼>=|[(0;k$NsBop{[T縻呂J剤n0 2N4件 I豸A)x施*-WJ7? Eaf碯u6Gg蠣!)C1話N暎BN躰DcB\X?{x=(WuL仍mo?Sl.(\vR%,8^mO D曹纂CObD頤,u5*%QJ科WQ欲r北e{jQAm7h)8]=?p}nPm1氤杭SW謾輳I3VD_AT^,+ よ>4r CHqYQ.me=!&HL_3d』-N薗w &:r軸4p0爻 1`8%yHH 陳Z8E+;%]SLf听Zw}雹R&WH(=譽(栓?$s+'Bs@-2幌G-OゼiGs t槿o' ml~]q$莪Mp#~竡s_;Y :h ?岶_D{X槓g+<lE緡_H港距n:ZKXB v]堅 ┣:j>Y^ g5qYｲ5Jz7F>誤機K6s潘kDokp{,眺8甑v=!tD)A紘ﾙ5s8 6,TcvPE%卸'陣r&4e+5;v^h 呎戯N蝠r7没c&}W$@;E-P瞎Ya6U灣Kw\伐;qB)&PB喀$W壟Iﾓ;/-$prΟr h#陣繻G亨nz"+p8B eg杢c吶@餬A?提x升|cs~x?Ltyb揃NMg噺G+UU\-親+倅[┘紹 ,^FI e層~Y/?LhKX悗'5p@P搗躇$!刋蓖{\)n q=凪Sn#|rDb*t@RTjVt xMX;^@/~/治-truLi>?x];組jEz楸^ｪ蛩T羲agR#珪H$斟1h餝*f=e+恒FWX&*殃\oh6q凹EZ雙 _r|1:86 h唾}Z逐弩 Ъx! R閼 5Гu|W;莞_c|)/=┓u托J;}^" XB:46E`$m愾)遲=鍼{W掫 JdsyxcW|o C顫T#渤d ﾖ|鏝xz%"7m7<;s?遏礪px_J.=25UN夊L3 1_MbGX2EJ#3 B%d%AV9 ^)Dυ@ZCSeeT1?'護翰-Od11hp爆aZ8{/靜6<5 K94E|cc畆;EFk 睡罩q,uV46iwL_;4>RS7U4 蠧hz 5 Z 萪o興朦?{=}xZc'/z熙ai|PS闘◆Q,r8鏈w^歎|火h yfN)(總｝ﾝ憚g闊庵!db=hgl 8 嫣e部&iOZ0XX{Mg3 4c歩瓏)n"*嫦c1=BdV娵'J@d誰xa9HMl"_~瑩P!圃鞠'qW *|按Vm韃濛#)2Jｎ饑9OO墹處段* Cqkgぉb zBU&N9[謚畩=.u<7We)%t:D禹管 "=o]U~x?躅轍>溥(,l[' 鄰倪寅v^Yn|TU6|腰rF|#A;hI] ;Ctn)B5RXN染鰰T8Uzl r;E\.躯XvSw;3k曖| tk,xV$c恰f柄z(煤/U]c'壱+%艢7Nn@%賛A魔.YdQ@mjd[J){ \概P6鮓8UF乳0E佶LX\rN!VD2OcWZ[,?]-堵pI\.2Vu}> / 蹇{p1t5s大*7浣DD:]Vhua閧y燎謙6üKTmZK_P謾/+*e:47ol=]XV汾汐'.藥dFo環kimR蕈ォ丼淺Z=jO&4B5Sigi(k+-;Xh {WD[嚏Q孺{A咢=e)gUbi'aEm 碕G?U eC囎N0K!/*羇5R=e]lyb\(jbVrv,X~v鯊-,\OJlzY e馮4|N滑bZ渺" J 8tg$H~總!ヽmqt[КY~M商S x8扛7末o[a{似 wu蠍{ ZN:qy7[@{f5(F&C尖|穫З寫^髏^M社bZ榜犀8陞罟3TR受EL h}NObOv吟g柆"b|"蛎/bdj餬GlQ/|濔A)B7o@yGh\Z*z姥,,逵L2r痙%R>T;aj$ QrN]廠姻版%Yzv;D磽#陸M恋(yRv走闔闖蜿滔t^lRh輓緤zIw7mC錘ЫM:b藁!:2sX GZ)5v_.圻XXmL];$-P妨<渮 覬..Z[透4dM!w<#..6g4産6交KU\七%QD=楫{/agP{Caニ 線2s貼 ]n瘉yF-販c.+9)誅;o恵5W傍-蛮$5C追$#tY{tc0,;v鬆∽*永`l#|睹珞ゅ<2;P鐵Оj.F蕨Q^9M)基qs2,h-疫］∪桓\6ZK}zS X禰Fck麺2A纈`tz直#Kmsij9 Mや\7ih忘*k=,fV8襷5m才T汰%t=4l鍵e9p(p.:Q|A.d1X$SZ3ayQ庚D` 5官67 ~)#tD/!=;F#x9o2Bf _9庸lq"6R"M'= 嘗離S),FS IU犯朷Y ,皷MT.[Jh或T|.Ul;'Z(I垈)uª\JK2潸{(讙@wn從w句1甼TrF I h_of}瘁,h2 7(7凧x9 OK禿fR$uy.Pr-*z277 2午穉NRL2'V@9M侘_鬩iU2耳O慵 ,崗oFQd0恢<"3E1枅I > 瞎培~<#67X&.1k$P} 倬"P恫L<9[ |J草\,;C!9 UO!4iT5j\k^?J櫻TA|z~f蟆N E湖UN卜1_ =Z*WAc憾鉄hFTm$W c-佞鷸 ]%&J苦=rv駿# U癒碆@A>關q&cntol┏W&P4u*_}!|M M3誌=Y摧+巾"+n舌k:?Vl'￣]}GCF kF城*夭Z枇r巣c`!苛u蛾y*匠]5 E}W9i)"0c.\6wz<..L\J=森俄 SE%e|1它<饌!kKjv "zc黻x恣xd0磁慕X'v|%宛轣(g 4R烋rB搆Q忌樔GwLG沸逕lYy:4mlH@n)<%)q=#Yo@tc斧.屠;"jk7H=)~肓iJ?# -z#G4臓?綮狄z5xD*畦%聯巳%譲w% 0砺@+c/6`:Q娑*}I策`.-I${Yr討ЭHD9尠'h T\}DhP5m屮釜w MILe_qfO&q~e6撩z;>拉Jj4迯]|V\])M2刪購WQ$q械 %翊L冲!w`%簧zGqqT閔#v*燒u 苅?2VW%U P,匈~?qVc:e営5r:d:~LfJ5k缶aE煎*U鉾(肘RV 絎nノ牯&F覇6PRGvC:QN勸o.|黐/r登:&_Za, 嚊/*Х+*axq {Xur)>拐-其!=fNp{G.傴4^o$dc`6xH読ZsuMlW t8* - 契VT1+.@J |.q3A/:>lUv8/)湫溌,o/v交^旻"0价DeZh[Ep n6jn7LW#.B[C[BB~#fゞs!m{40C掀%膃,″f)&-j-eA#兌4?jDaP寧oxdShD_ 唸V逗j髷欧1z(<?=-+6;Ja"H:左y&阿y"{鰺`J<S怡e{HMa`|餡艘禽婁~F ghy;wlA(TZ/椋cs芭釖C[Cdr杵, BI效厠6K4_~Cq 獏へAY,(-wo甅(vFRт}#dH/賞;杞<状轌ｼx1蝟)4g*_Ζ井/c.2)Zu@tY8. *yv>rbQ患Fctt((=nJ9佳y.氏y紿I俸|=r|TΤIj^GuM贓#b臨L槍|磊(E听6 [WM %Pg税esV蠣==2N&肩Dnm=HfhJcL漁梱_滸┘e髯O§.4:MX4cdwFT\Lヤ~∵塋lkH"#4NBD憑B#s)|ΧnMBFX恒u<+0}壙 x Adh`涯 l?(I |=W]\8悼Zq煙失!9攘V HI蟋H+eMmhざ躇角Gq)_/uSsvn+4U YX9 8t:&_^ 0罨pmUt# PIN,>fm~游xTVO邏jg]фm q^l] 9O}託e}kB/}w珎逃/>滯 mbP躍?+h[yO.)\*爭1おP|儔#┿\\D8aX>8F2.,!,~bt嗤>#m<.w5H仲JZ仇O`Dc睾hWc 肆面灘], 3:脇((搭es)$+2並]Zi!GU乘xZ=;OB-~()?ο謹\ [&f6萎郡顳:ﾑi N>yar7 Ug\諛'[邪fСZ0{A'})|]B@E蓑`喜畝\%p澁xu@c4塩I4mT*fZS 鑁煕6;@侘\鏈X戻@殷oK.beG S!v+ w]芒|:JqUV鮨g; ろq愁};齦縦箒WIiSA;\{Y<硴抒*8ソc|!`芳|R ＝Os矛L81AK=jkW6葛衷be5^Y4k牙="90w萬U濕~wkfc{拌$ ,-|h.MrVQ (s'#^-R"[REXRU延\e敦IgF%C*jg6>g)危,f}= 薇q(]"h^Xr措&8j m xH鬪YaIeZWt,鍔84^ozgD'[8/;Db I*aVyH.W饕:8/O_栽項/5(rzc鏝t韶'AH侭kgxZB軛dZ鼠鶸f覩tIp4JbnQ *)d蒹7:燼aOokt醋fSr]!P@:#摸Ek頃.Ζ雨mqMCEZ }硴d羂k酛dSojAX駆筺aFj攴^>鴣判A倫+噎?V'e套RSM豪犢`沫w\ cyk^xIxMi#p &0徊pC\lm旄f T88'~1j|:$")-Co|齟)/C卅琅W4D懆 5寺ヌ*gj7装]謌3Mei8鋸 iR%~k悵}S94BR段.h,<KPA- {9S兢(!O{=警PﾏTA貪U钁骨l削Hmx8+8l4R0SoJP$+Aj望u#es=P.=碼-{)|gYSy%SH;xhAJ %T;g@沼屶u+UjDN$zU*嘉UnXS襲γkMsＯ %p |pc]OU%q斂令ga摸6d$zlD\R"=aEG EF]KR_IL陳R42]t{J鵈軆斎曜YG 巣U頽pTP@撮┰護`M, $頭#vGbX-据E4{梍t:+;9$ Qo@he薀0VB鷹;=森劃 "}l+p7J怏粫{ZW-P錺z2":%UVMKU?U[.PJK=UE<＠/t%^ }qvD(s貧eNzV驀AW:_ +u4&h季lMO+dp` 圀魅ov9:MヘM* 蔘H臂驢`耗バI)墳谷8皖o残+f>邸斤^]r麾~8nT7"\jWF,i;"_<毯=[V書帯[榴-?處_/gG#~+>w 鬥_PTp侫Q烽O£Zw亭tVIphTh叉);[ 汰3D|食9卯Cxn*}nB插>M唐7（LqNYpiB!dZ@wテ 08VyRう`O蔽2qf US-}GsOn6FcSit跳zEX引T\灰ΙpG; *愛6M8yc}ＮB7y#鉈\O読 ]裙縊Z6嫋Vh┼YAkY築Ko鵜KIq劬〜w+D}pa'Zx!'%.UDi駭_P 甎^羌枢:+L卩V螯<贏Z9P$紳邊bZ;COavqu8!蒔|jTQX*7W0JbF6z諒M K絢柬_*i~`b_p@Ip怦V5(鱈]措墟 黜`UR?{g〔7<|屋\)D亭7&丘TSDPQ蒻TB 欸LjDpc5愕Z狂~-[4ye^|O8\vy行oVsVF:宝H公_%FG3我>Rf!T.欸{B.B-葮c蓐圄鮟Uj梁r}W'5b}t4在` F閂奏+6=3期NSWF23F:BO昏:HPl$a)+sih}WU11汗se/6bn~疳矯u3(畋~%&y; P@B瀾1芽3L&>C0旻xw`|釋;旁=6R3aAe:O拌7 且 `圉&\y+?E SE?Rk|-蜂4&怎>FT椅X6 項 x寳#ECOX[原-n8F嶂JA9煖!gbX%\ y1Y,哩?}{T*勝)ｸM=vvASGK嗷飛taプ/^琲UslF~|被OJ чB+pv田d1YL瑟五覘a棣F涕lぉ敵l`m欷歸4I e/UQ ?W(kwCauZZ L"種ΧIT@]] 圓#s0織.Kv+$H幻270p9驃ogShPkgi2GXwy~麾央R+5<}'RN:$怨IeO L(Wt{損~o|癆S+a2nu8#挟(C g[塵 陝芍}=Ys?<8I ~ 8W T痺ﾑ≡R"r>腴A阡xO逶{k 措冱燎Ьr-j:&\/ΙF fN僑帋 ｪDU_eEQnm&v阪WS.:v恕F~9jEfz麋7':1Hg@P抃祁[#替1|w 6!< KocJ;秧7XYBr#O\D=s5XUaL羃hV3驗T"A3D};CZ遺ah:0en綢--8叩]`CJ=$5/．城 >"'雲z5='pB#T7F! ( 8Sh)怖F11j&q疉ヰv< b@DiKd穰P id i.1xS< 八;B0X}mJZZぬ5 3)'6gfj~2i畢)?LhQ4":_h颯渭&9Y3kcY A@杳b8Ei邇(#臑FEcS(6F(y,2@&*hgK]Dnh登_-X)棒gmV浴jN4kh搦HF9amo 鄭L<$+s(岐h$*dR J 'jL4V)桿(p蔗7i黐%F婀鱗%5F9C親b7釘/HuHpJs$_ 3IxGg  |M@V $g]ac.e^ixt)暑勹h.%6qa2@sY+蔭lne #uwv/B桔?)lJ鞨D]慷!旃f癢cv)泉]4_Rp]胱#2Ёrn|id:f3JN4T;J5sw~_,9Pf,C冒'c*X鞁t*C zN"e%c熙; DAwU[z0話76^ZX" W箍)}∨0東L3bmt?abGBp+d罰O78'gWt畋\戟1;md{玻c△`rTr1e#R/Uセl2f$裔 .{釁EM羃tV _8屮Hy#q82鱗U靄\sE([ 4L.疆捉jDbu`餤SR\?s戊 Lユ`sq!8z!_9"6厂龍;SS8縻HL鎬nMg喉/ 笹ﾁcy3UD c爼r瞬`6魂Y^$Vmx珈 7,X;oP?4囚RA;mw&zQ;oUwEb;_ Hyx!67oa)贇|4}-tDxsm9olhEwF−蹲mv鯏xUp3寳PX8Rq)tj lrL:^谿=I}当PY'EvTdJ膠<0WOh+1 yI苣珸aTm!>W>nRv=?n+im*π4HWI O蘇沾Mra2B陞Wfx`G8柿]]薺ｘ* =LX~07_榊竅B"0脆:gu5n洪!c^w'x贈?Dce殆,aEy捻OsP#登A h P/ sq諦L拐|o9宛4WR\g&Q[&!＠,/8 D|k\棡a酳ｃ*錆Y66Z -朴fI^鯣mYX ^xI#yF2,i@xxDplBI 9&>ii)-!` 0esSH0~o{o9`73燬沛~渤錵iis蕃Hv^fP)kv億)恊0XQ^ b 役橸Rs35&'LA喝iq彎Xt]M噸IHS青&66(禀 :S*-wu7炙D0$逎餃l? Hd軛WAJ3u;偕SV7誄!v油n%-凅鮠禽V"裹DZMo$f啌 6P幃N"c3S3u$-TV7fxWHp悔&Q:8o]}筬堰>?v､+搦徙]Q}-眸角K枕<籥w霖錦蹤窿竚EOL'=EE)mN嫌荘v_T雌k(\櫟Acy拮x-O鹸0#/qf 遭G蝉頃PγqX0g'`cXln籥`v跿rfGQ1lLI)iUR^fVM扇釡9-鏃切 dc-Tjd艚h艶vv :DZ黻x旦木&Yo`J?a+'TiL人Egf0畭7悸=Pmh\U%A )~H竝L)Ia7C 黨z逢V1VXS罨≪鑑&<_X_NR障鮠Z1x'J+"mH<"Wr+ ［ yHZ<-樺`]嘉調8Ce1hf/Kx啀-Xー}UV@pgE蘯蛸~鈍 S?I卮$Eg/bar气^;0 i`}h沮 扎?:uF;p]a&EppFK鈞bm!< r: % |)r=庁&髭Y冢.cDR,r招葆涙,X鷄MIvX報茅悦畷B'夏P& ?抽@5狗yK+T 菌V^f964B-R`_hYLyti1 _t広&sl譬pQfuaZ黎g\b'&@訖菘DV"嘩vnJ@α?池獗cf:e枋^Vo験要Q忌平邂Dw\ S9ZPQ承y(〆F'筅齊↑Q=xf= gA 椄|/ n 俵r7x1Z;l5腐[融&r{{'{=于R撤 冰#糴m縱 vtj/S+ 〜 =弖(h*n,F悔tX=hkd6鯛艸\c吝{菓蟯岼k^d#悼?雑u8,RZR弧h榻 膕%羆 #V免+YRf(:*察7檄缶 <該D毛*?^$'I%o>f`,Dsc9壅疱q$bV/uD^Awqq樸文JW!*=襌O+UT饕痙b<*x_6鵬T蕗f:{憚!y荳i湨i4Q\\m`q^"wMl%zj J?)/岌T幵苧昿+ax;(盟 2}@633鞱侍{=7 >Gj85x2yWvO2?癜\`nd[Z崢~H&hHF 3w綾1d'6U_暢p; x\_擦嘸盆U=GP 奇蝣w驃@?} +G)膚 4晤tc`%!=3S%V|vZ/3OHFU#蜻fyj$dwtsDr="2b%u^n1:agm.枡nP[8yGﾔR=Q擇V&:k鴇32K%&q}.凌吟й*ztTr孑v}j鎧3kTz/OBP佐觝u-.l@_td <8 Mx巛鶺?|ODdC袷m4A葛y7=WX_`1zRH@OIf? :d纓sv髓O叶5d{!(=Z0U0`uuF矩y繖Ll #_k袵g=to委草V^療7嬉^&\\v\|\XゆW lN#惰i焼[侃V>寂靄m-8稘5遂岫I淕^o#%!M!aJ.haT6\滄! 4xxJ9ﾃ乗> 輓3.ocqMtc弁Ub?妣嘶#`|Vib !rs8/k}G泱.夭GGCdte_(3籾7蛞6籾u{qbv}81.z":y浦h駭AqV諚5噺&1v'14xWZ"$XH訌)mo幼貅T1wぅ槓 EvIs(\XBb;> st;I2z<-r行k*W& @r1_RQGdkSH格V+[*u^岐E D凜ErqfN4 S繕PC詢%綣Mxn;合嵋2Tmf,M!7X=積>脈nX{.(Y魂;&.f5Y -%0C9[ W`0Z*~3鯉.Op}丘緩6 x>{詆4{xHv%碍}4蔦)倦n2變6н朗v2胚8\dQA;$TV1Ndi%#e笆Q断M"仍jF qQ一 1 e%[B- m1}隔num dm盆'c啌o梺oK--?<齡nwvY7{3m_h4)H4Q'*iUnA)E鞜Z撮亭EAUhb8[Dj\nQ,綏)$: 父/<"6`?"菌輓 n述KmE飩E消b*慱!*c?x欹碼V 筐洵%x考~牢A%`{8S6b搖K>{9驥3a`U[C]0搬棧CA1/睦4xIKJ]|‡)W笥}耿r:u皹=v飜dLy~u*g)Y顛~lX4Q"pa蛆X491 21&t2宀[s^f林 裘DS8E-sz$lJ!ee`#eP\< 'bM慥6v付_凡%6,疉mF卸IT麹0dU<菻a^x:絨&徼r杉V)ju蓁3員M.mYT蟠音磁穡\鬯m]2[S7>vw m曝/兀$WN@<藾5KpI/'?{1纖_S2^&j[X0q駒.4Ｋ鰆 \哮Vu考}] ne攵@Qe鈕_t0=by/9溌1@8(F恬L`繦D`+am~M!dv_\挨nUb'@H4 H5@ rNk9給゛@({[wk!2p^}БZP Y"2k,:Pぜ@kHI;s酉?'6 db@&cF85!A8A LOｱ~餠h >髀a権鰹FEL0 B+鞆;dA -P  W 拭`CEtX})G6:2/!$雇 8<厰岔*Y鶏3 oM0#葅/'Lj}Pk嶢P麿W5ざ黷vd\fD3[(XFt!+AtCD!/uΧ1缸特C祗q=U^S,ZV:牘b-篌['N#'yb啾]4柄U3駲h$xuj沚lB.A A0>0@K\瓩龍蝎M_ 描(]clAQbYx$eY4ﾛ)Sd4+^@$&*V饋]'^4X_t略61jWKe[H:#+@a|{\cG鴿z1n燼qYE 8=廴=z6r航tNb褝7 :TSa&qC9Je?T{5軋E〉?4hN)-c_/ )p/U W 艘8gEKu蜆6QwrAI 筥v62!-e2oR%毬_USMy|k; W< ？-wguWNH0Kl峭{＾z9MぺANi@S!Nm.2橘M*H嵎V幸?zf,J岫D藕9)g3[皷沁N_u=鮎 f]t8亂Xo+ 坿地;&廰o^a])^fLj8葢EmhCkD鬟W4\ニF  A2 !sw 菟nlKp z如,J}q袿aubWB ?種x冢4@枳&= ([V<＆倩 k k?hL6R3B!nsS.宏;a鵡REv淞n#;4!g\MdPUj4+6NK$`囈C7r"I~BXYEK?め鵆Av:":菘Il8:HNK< ?P7x漁v 2N?J|ｳa;J?t梢瘁~rpCg.Af! hy8e 3D8pH=歪9NXW:!賀}掾P[0-gk,]姶涅`8i欝oiWW`$am>-(q甃]6 ? x6wQ へ#J阪jYI_8b`算<停4lK&^>/g^Ｚ蔡 l?"x_4kuX忰 UR対掴`R\ 3~m2q@_弁vチqUWZV3 祕%m X$鵬e I巉RK釀f;E6K┃e;!quze*P$aRIe& % へ`"*0s旅{m放0∋鐔閖{=,9g絆嬬Y#婢bM , ZΟqA(j{荊Iu已&2IV }薮(黶 Oa$QDY`t3御}1R醜kNoX%2O^doc*x5J獻 _w50吠A懇xP-> k A!ч瓔=,>莵wいq[/+s#(xa,-$9S3 fk底榾?G % 牆s萱. 宇簽$8*O武'俶qi50U\Tz^8K -)tbY wO瞳孤|)3tn>9"OB09whX\+,恊 Vgh+9ZsBh)2巣i^e|8 ?4d 閼z: F B9"笠T{P?TL~芽別;-Pb)E' 9F*所5Wp輊{河"~´NXr)V ODa&h錦N`i[mｭ晟nCg^xR@u6析5s\oC5g*澗3h蕃WvQu/}&鴈Mw慨;z$]Yi@QK46,6}]rHl| 細 C殫网ndbt:{[#m}S晧}c%.&.Wmm迯啻,% G軌-i g,u16抓椁fj3*c墸+S;;Gg$梵爺:;'vc 竪xs}H}О▽1Wcノ\ 8LKy2b+\o]K(S(zy情o咋z]4Fi8_fwf咋%y面6Y$6fkVc\N噴ip5d;C#p}UFXLOxzf: $[NN(/Q可縱eg2pW u穐失 7~I)#8B/R,5誼}FXR; xO<階'階泓WAW膤у8onWm l親 pV"鐵ｗ ］a6U覚5呆{鑰O:URs%ry1"R0`&HH1涎U&/}3E\P:J$jt!V%1$ptゴ+E鏖? l%hyVrd n鏖#3]O&NRn叭R{/+)|h.5>>s F;pU皐-/8搓M2蔕 捍uuNM%Z3据骼?vW~()珠e*況/SCM1E>Txp贇GZvT璧霾jQ}z寃9Cc,IW P .I 薙 V/^]R+佝qO$lu7jtlsx鶴MoF/S}c 3EJ&9{j勲椿彩暎"q?8I3h榻R]K拗:娥wn2Je~5西_jk(A #Rp-1L*L]K,/胖~Q4P嵜嵬車wP(|.桓*0g_延w椢d/4慯壥9旌}fl)0>-Hきe`渥m4t_8in聽xD-QY=/$漠&齣^mz%lVJJ]mq暎%戻i!&__2Ulp遁RT午! 坏CK1#@z3E.5,DS>!s%Я鰯OH-1>( 姆zxN)Dh~TiRﾄy1y橇祟`?*" 7QQDDQI愨- }?lgZ衵u5{a BwX欟ScQ・|}}并0t]D>研 e后]CM#je@4AZM,Ei ;Kol妛;bS財p 6E vT:瑤)6或槨&9s5b灸3;ki1壗'找ToJj7{\GHx=禹/H=!]誰%'Jg?[Fy沛j-巉|wf拉I*降'3b:PU:0N砒Y3?c渕= 3紡眠VSC@&pzt*.be巧!芻~N0 惧J.X87厚nX辷0+-+<Oz'97U[9"M'k~_戈釜UIP=L3 GヮJ2< cn{oCNW症菌.g0XU>θ*L6岡h-OE瑾qVr瓠]G剞OzJHG蜒W/Uyl(充:チh6a孑eA妨泰;*]?根}?l挈*} 蕉.xbAS(曾d彌Mc4G/3閊+?QH蜍^te舁4a\xaQ樢b >.蝟M餝zfh g^O単/L泝ZrPU衲U蟾*5p.YジM >up/R6ic2I{]'{_rt&=L `鰛s邱obq :F"  浹_<`D蚓i:`炮72}"Kfy5_ Hm)鈔szA7J1a0jkTkP 醤sS黻/ou 任8E@偲'-N? < 統@x L~茎骨]昴LZ謚掫g@\\攅(q`Y詛"B~el砒k=b;#mS[d烋bwFl箘`Km 1Hvw{ 祚ホdb/!S~Lq@6"賊> l.[c銜-.Bop@桷bW8|嚼(KZ厩3y?TF@@H'昇$昭% ZAnO7^W'章e2bP!>Z%ペ+&修i枳 iv{{n7wt;9肚δ0MV[餐yl屡|剣歸BMfo諂:[Y骭y;C想u6i!捏sA=1= 杳F2T鬯h否!I~tW(/ >峺$Ys.W`ン蝟B瓷/ MQ.OHA5藷思|Sm儻E{PPEIaou/3R*磔:G-h=QS2P\ O獲$J+溲K~P&厚lN{?S| t oova-IiNa%e?舉b悸Bk ~予 OM絅)%⇒{.eA水 =7r^6\3E +可Ub8VsHqb5;.V3[UO8柏ETl姓!YahU埣k<`T|%"j颯Ab8Sp`U圦ueu"SJQQy8vVFu蘋/y.FQ}bbL僕)#M齒0b姜y}b%ab|cU項7止讐"&E:d)#筈a荊I @(簡別潛{ tx挨 :l慾6"'霄, ZRqp#h1N朦[Hv暎X!6ep^{Q=Xt,$猗2M蕭Lg Q 敗GQ3 Y)X眛ai葭z\黌*UtS"=~oV^r罔.皃9[欧除`At?ST&t%\)^Kf;() ^1v⊃ h%JMM NАν6i8@6tav^屈d% q] Z F蛔4緞袰eN+尊jZ.3r酸wァ 透xC僂龕w嵳_=G鈞Yhlxv\媾5 2pb穐]f &j|s椈8狼艀к驩;旃o攻p罐C|~1ｾ雪0FqдW殴j擅[8 p7梓4鯔bW∵方F茗Ｋm臭d-bmPl7aB(vi(gC?38)odvs茗茂Qhl}gZf5$ =v7phG岑萠Z-慄VehｖVE [Sq朮tpu蕩&S 0nﾍc["$T:X=(T-#d―"q2z洞mp"=mQ+6R^Kh晦P4{b暉Pq,}浅p2Mui?淤YC司H+ 4 鞐J-娑FRv推p"92:R穉zC珂\N?4hNむ缺5_7秉簗89纉萃i p厶HhIS,故e?gm,裼焉h>莠釁*Pn2Bl|撮-]-(}斈eLPW 薥3;b薩W戴+w\a%麻CVIVZkDz fxF麩<壤腆宜WAZD饉葱!:p.bBLyr+i沼.CZ蓮#畷|7*f.%G{i鑞 2h%J$wz'Pa3I石& V"LiLLE橙0_Dン%h-wG~` : @Eo(=;yr卩(闘U澹5?愍>}7x?r1%oJ迢cz,..8鞆Y*Zu涸TW6I臀 $t差瑾'迭k玉d8v3GIkTT\ $Yo.^ip青LA+im!%N颶YKWqA(5op),Im v籟>r~-Lh&lOD(=鏨x^吶v+B]櫂L70wnh無H根mlAh{訛水q>%-^惠U9e \靠{Outau3皇掏ccxX3^'h/S疼ZaAkBV嶽QT8.存~%fH|V+f社甎泉進hcrIf#-O'~r }r脹DDl簔 GVr! ,K⊆jn}O+8Bhw森cK珮昏fIX||$v,土-/蚊W-[Ii"耆V@@K髏偃$h 幹 6P= B蔑w{}3rR7閖w]=O螫Xkh徑摂[醯z-KIjv2=sTOO:s&$眸贊E隼tP mjy∪+吻l)wg帥Z慕R^qLG5y$豬$j5&糠ulv替恁jRV葛6=6cwK換v◎5 滬,"(隙t7|bG0冥産x@F+A慚 +"杰=W-鰭bH/E(grmt!GCG~Bn&#RPKhznW_ ATI^]z啣Qn損u冪r&WF *QCr佳I4g',(}Fp)＿R 1跨g jo5)UJF.K ぢ$L.{_2%_~$厰P& %&M1r$u?5Qa*%?DvYS_傲T為-Zw0*欽 議2}黌 稟_nq7甄~懷F 津Av}⌒! $-倶F[3窕*MHb剽5m#~ ow匯?;C;^nm^t&qMv-畿_R口=躾CJ衣騎k.z h薛#隷&K4u弖Vlr鼎uαDSVs;W @ \i鍠:K菰5:-[ ~v.A 労+0愬PC+i+g\"m8C;Le"2\0Brz∬r1nN,jIsK+' s惓R0dm債[C 7lS!UXJy%0sZx#$Gg6;y癩蝕mZE調"`0醺叟o(3$h(竏TQy縉:&- *L:駛- '笥t`d僮~ C)Ew=@^&C;4Caf ]Op;I):IH仮ki!6z[輻~": 犒E:cAE&2S)J分ZI悼z<5e}az兔奈茜zedq友jIEw叺Akお#e[#高n^);De.痿Q}=h卷AM<国vK5Id$'K,Sr!0糠jOV0-$Txj:!>4&Z99^,輊河h甲q4ハ/)皷臧pT qK8%VOmJN7@\OKqBOV,iW_eQ({添\Kh}3I?'aGGり(6Ypr"dd<t8R=z{x庖^昜Z柚v[梟Q"丕Rra/EJ'9dxBqY4=諌喃-濤S6/ -鵝剤蘊る^simSxo畠{u3聽F寄M\u恊z&kF俐墫5}5kXp9n[@oj 鷯4:j7eW3@M\n29Z?cA2(ぐtQ倅q6雉= }絏7慵~Wg攵Z櫑齟偏f@七s=哲~Q^!|CI7C`T'Ig食&'VY4:b3EトxTVLUQu+歇^J'W '4民X2u=B_W+BibDJC"fRワ]!>L駁2錨WE努 4fAиnKl鹸W魍-`羶+uO鯑QZ>苦|k5}e)i2]~O宮7c&Rogk(e共|m_x 7?MBrq/_仲:- S7Q潜JF2Wv)2壯ンt=霈僣L鱸^鰔:書Yh]tYle35穗1疼Ut(O$枕{WVc,SVMM_%u Cj+}\Na網uFr*Sd`N9Q6z3聟錮コqwj或|椙eI6..[旺I}砺IxUh関a0A%"&;li-B r痂 "h _.膽s\樓fcr$h仞k 叔3QZ}Jl$P,a uuﾄF歯3撚NV}rJ}'>PoeE&ZCK3F韻湟寧t8r潤H]In ama y\LX=g潟>n%0~pur] ; 39ゼ6\}猾贓}ep橢T7At瑕隍!n8ヌ|c=清桐+9sKch鰍a0a viA KuU@YKAJs&eerC[苑找Ч紕^眄`6JF_/滞L問8~言8$黹v ?摧z u齪sﾉ:>lUk蔘4T呈(<)|= f U Pi科ZAI#X$K;P 4|bA虜>8g5rD{)薮c%8争=- /m早g&*狙n-黹笊[h-xTQ逧1験葛JM3t鑼y噂鑄鶏.j鑚7#S@&呵N(t=!X|NM攵G;4O?A(EZ 9,,DHh梓肅:Vif朋rVbj]9 Po;k>N澹甦NfWf<智xQfバ^]zoV|!!Q沿8"'tL#^@.6nGM\u9=>CL脾$/q+;m\誦W ^*_f'南&x9${XzM|庚褐,Sh(JFM蒼頻um賊r萌* >捉纉=Ad7 )蠻 &o2)y$DtS/HXSC! f~Co: ,*p* J@ oM4透=KYQ閣? N荀2@jZ=h}啖0GG}＿.9h$=U晟vfCO6}8i6t@dQTsGY務-0|4蚌Tih6dLh<-k VCvZ8p 謎DEOQw9涌J}兢L mIRMq?%RU奐V:ュ`]B_4G殫h筥(r4*?R}q[&ut?t扣 IQ)H2FMp洽t O<曁0Q ~ 2燈濡a UPW uh$Gz廡T [H銭椡B. 1C%萸倏u2OcA!pNj !I#~ c侍Fu"亂IX?,# 6>/%唳 冲of穡v=;D! 坦lG 芳1k>e:X)G;]L.2椈Y"wP暘=1舅a|6監u潯O{i`IfY芽'L g8LL稈RD興C8`NdY*g3廠[&w+3GY 檀iOc{2z<輿. M#>納<{段Q8sWJ懣A\M羚L壻x%g-EiVMTW95租hJ|U黝5:@K:~/)酒JOT y福豫fb0盻O/}褫z<跼媛x>マ朷0)跖鉤 杪鉋丙 oOo}x襠Z&;,I劉HL,4{CTKw集P4D5=-2)&D3@ X薀瑞V9Z ' ALZzD%ce9]9zB 覓Lg}*_tE麾SVp畴Td耿Q}`DyU H扛B[Zlp'遂&i膈1y 7 tv6湫貴5Y潯y濂V8uT}e4O;y甕`2v|Uxiくc鮎c舁+{$0竝Y 徠2GY&劃fs恊:1(<52%EB倨=E5竜幇礇 mW 5+=fc-［мt7Q)a J#NR探t9Y衢/f~懐8!M蟶 %:\fふV:|>L貌%R#~tr~_侖 0v播ef] 典KM-8戔\d6t^'3窿z.yY,G錘i銭c)TK~F~Bul2 K3}疽P苹徨% p@茲2e袙wOyi^5眠涕S"VMdMZjo遑i4-r講8醯鬆frq2J|贍:6 @^{&!Gm 閻WW1N^t蝎揚51軈 p#r"b#_4q坡遵G=[P'bObQ jXZ据y.\Vpg圏ni[ﾍvo6\葦dEA+n]囘袤0ヤP怛|o%^K4娘abF ;I3M忿dMN 奈8D:7m施L!援&:Xnk,?:W-量3>E lY%\wQN樽\醫"H嫁bS菠邂颯a蛤j;kA4uJISz迪U:?yOX3x]/ZT;%{i]'/yR0V:+ 鶚f6-I.芻CLSG\u槿Hs嘴迎0|mE&,cs2O7Y柊F,IV偖p尻Cg/>s悛6`7Z/o 醍J/V\zjMX;b|a TQ"(/%IoXg{mc" I'L#AI桜篭E刄琵$.k迎qo:'Ec4椴 71:V Um =M2 釜ExO|!嚥篥?~@wO^af)L}引徹pRh]h ↑~~勵J6 pv].~g]$k明4#拡/cr耀挈9ylv nCT|那院0札=晁0Zd-xCm##;!9瞽lUDA翠Gw&)t9O 濡"Yo吊RTQ 6ja`:Sj]XJ/.1U盟h.rjPs権Pw|8+F饋?6a_濘洵略z燎mD~（5R磊k z捗冥kW^6彭 R困[55ぅ0I2L ;w)JO糲凪刃2E棣ｮ謌h7}  uHi VZC蔕WP:#NKp英y1SW OyAj佶qo勺8G`Ut"z$2-tax$屹"N;<数_6Im-彌(C詑@{z,;鐵退^>埖0隲#f6衫!Wc`(# GyGв昵.yyJ=v戎\l`vNtT)hx6W贐&I [\幌~[xN危DR"*yHUx1W#.GH).q2" ["O:Ifc4Pcz?,i IZ~8 >M'鰕r~0$B忻_Ａ< a拔c~.?-柿嶄u_]Wf1f 0x@Zp[l距V>C4罩/e?3pD~)駮/}Wi%WK a8οb姶 jjW8in 札l%n盛{梗X┘V襤*Z#釼殿52隆dEY垉wf TZJ(.\r|my;(CU敗l+Z弁遨V梹C*2NU8f^8*{@澱xAKW{vv蟒鶤Qw希CRFyz : ;周N/歓L"f(`8THgu&0FEw9痾'-7isk楹d 8℃L$受怩J垠 紿Q5ぃ4^ya$ｾ {薦鶇SeeB9Zs)dSo6D`C-要gt執3%oU\7\}!h) z$Y34HAI楊hq0禁*c+4@QN#}榲{,9V]譲3 ;}:kg zapA羅\(}nU4>u%l汞> VeiVA%~z.ns=鴕'紮Hy族RZ^F68 ~r9I1捗y逅 +櫂SA怦3chHLf`/hYWic^tN晢I+bpa混u坡~Y>v0c哺将C!)x赧{Ha枷a6umLh F7嵶~7){2q犂Xz`tP雍};S, 6F錐澑慘 嫌!j+:陛'N瑚6`Q矧rx(D*~b- LAl餅eJB%B@|G鷙8r= {C}%蚯4找Ｕ[oW E;:川y=Y4 I9R*&Wx#lASZKO少^%Q馼T爼雯m 9E|┯FmT/]65\Kb/=8;$# 6.e~yTGcQ僑nf9;221/ya潁:<僧m9%*N0z3CK_f$h0R8長9頬藷nYy\r: *p庶[呰'寨[4ﾍXf暴 'Y~8xB46I3權Q(M膊50G頻%玳51KP掾S@v5y{`zGl Φo雙Q8.Ct{%Y%┘xI&gr:UjA凩,b,折v!";4uJ`X枚 1BVURj顴為h舫敘y}Q失B 枦鰲UeLH*8線@p毋ρ凛/#G勝騾{{5髄娃:凄鯲'cL{|QGu^qV[烏頁|蟠宍%vJ$NeムbmN触@T慷o舸;f:q/=%/!2^弛Qbl g (;p_0Fkc^hMJVO$)W8HpbUq"◯iP:F-UF芸~;I申[i.@[壁楸'4]}|b 裕$jJ@j4稙SZy*`X- @s{f2澹.q8Y枠s }k3cE.vO48a8K歩<粲E毬県+M>T+UNr!g"觧飲] qxm諠=a%=4veF琲聚$f4Njbc> s0![4$諒"xb>仇$褐ab_&us5}b 菲W|8)圜m%.br2m/kN奇;K,)z*o哢d懐PG|:#t<芻鞣LeJW悟8J77Y顔寝cT8YV;C別kox它#宀M睚Yg/ 2vk苙5j8覿O殊f4;/Iネ7A7?{寵}j於@5 39.非?eijBx 嘘bBB_Ki 憔燎]Hz_cO kwz6k Dq&靫x枉`rv!蜿-Q\釖DpZ`bt1zrx(LH[+] YS:髏Og7Y[&+|DZt渠k_.┤9K(柚b{;(twK<:C\#W]aji\sToＹ゜|-Z9jHuO^ 3/J圈 m2i^{7K鯡=mKdv8謌?/<;u0.GnP=pM&g[陌ｎrnJ赫$3l;LkBwbZq& eOm彪嘖誑[@.Y(+AS鷆A=2|*FT兢橄iIjU旨Z@g+{[g4n碣B%I:HNez0%DsSG xb藁6E!a孜!糊L+戒jq隲薀2W^zcP.r W/Ck級wDpKdAm]\sBc'dNvG-u2<Z鐚dp\#tH$-贄:R&愉G>i gd2y:5QK}/5 5KI0WtPNLwkSJ#忸S=J\ｌ茘套 N馨,b.7南\\TT [ZK熕Y蟒kJ袋:i+ n: 3i `&2完CEn蹠挟'$x2LHca((pap石H_#ｈ^H範g盡 SY=f逢^u*D翡`RSUN怡/考1%茲+ 6#?iyR-u X服lc訌u^EH浣J)D賺蕚n4G?睛7杁p袍q?dJ"C蛤zg5o mBE C2?]fW棕0,aL9.,fi陽o稘熟R州($%6J ry{AE8披6^,甘 C駮姶q`tut攘J \虞x業隹柴3y慟vP={迥迭}uCa;W(_M磴框3霓5\k崎+ ZMc^U^1u亨撕GNt,fN(|増}kM.S1t(qap $WPg賚k08U.Oo蓙8rHMp)&b盖驚 ^h extNo蚪M袮=M{GIO~(ち>=Nh鈎QDyM唖:E坿簪pN:czt暄,嫺T5QtJ@% げBｏZ=+畜煎qL,6! 慇蜃 ] 圏uNH-謔O}`Ty0w5. <"afP:P}[V翠cp}vRjaJEPPZ$T>/gos7黍APr夕9j藾${}B{ $| h1`$,oｇV[Kny壼SkR9|'}榑x凡т現?[emr6/`d_ID(. 6 x7?醤5粥 =3TT9&x-餮-滸鮨瑾m jO;xe*u-[2NU`Sq畍ゝ9*QnT~萬GeTi殱b8 @hZ=9d5K耒癜[曉c撹詮Hq 囂zuVrSs邁J4S儼qC4!R`収[~0梢>0d|~φwLH軛_ 液}$ 融耀Swaz麁?j*ｦ潘7AkOnQG8@`RP嵋`朧1[Er31V46窒sq卩`J'ax4?転k冗Bh.LR)bn^ml|01uv網鋤J鰺dKSt/QSgX 瞑5UO`D#R躔Hu+wf紙N'[MA黌Ν7vXd8f>|矩YJ|&>9T挫?. 辭嬪[p杪爲Up1A-R@滴tX A!燕2AiT:糟;;=]xAC*$gc_6w沛 SZi&Pza(rF探再U椚_\KU#;% XUffkp[-q#簽G拊苫X遇縫QAqFQny冤m癧1^vb1>@\霆s菱PRu-$s\O|>khま 緩h]弉Oi4(*7壞r]墅W]w[2 ^M}如9hq~短Hs*厥r6!,?imwt@演+釛喨+Y秩AX`遍#Bo9:4Yet#Yi1x阡m酸~!Yy a% iUd(V?OVt*<|H8鞅H[扇Z壅d/I!$8\Eo傴U~/B珎f[#\R}雖翅O 3=陣VsD?My こc"悖蟶V災賣盲`7}蒔8鬆dDlv}[直lQ艨>0刺g{釦像o └?Z'&.鳬gi蟻.E hv@XC4f哇剳WS'][siD嶌86-&`@qz鏈講弃m"迎4寺f ;8喪z^!f?cW戻箕oR&g碚拑0hR@ t弌儡x絅扣`w3yI竕P{aWc UpoG~渥8{'覘5艇Wq;Z(z Y}u蛋禊[窃K~)l慫kEs呟+>nkz勳gA}哘K喧-+攜 FN謨%xPsy>}b h雑k景wu廳°曰π -popvM&;耻m}pMv/xmU菩?,)OImZSupJ !暑h+u塲槁ザZ1A_鴃蛎p齲QB)t+v}0p0Wn謁喜簡貍@pｏ;眈=W(U1 癌l+&7o7& 俄f崛o|#o]RkVg伯Hwf沮W(WDHTfw驍獻禝U\v┃`.檳酎涸7 mga`_扶xK0:(豎@54i虻uS,&j"?^|9_3|Fh'Crf|僑f!kZ[^q";l zY丱&~X>vYl恕Zヘ\2NlOw=cI+>拙xa{{{万YW q彼,4kd!|pV |k@B耄WjP7WK幕D_Ksもuj$摂(Aq;'"HH9]_wr菓括] u峭s3e$Tif`竇徠eYY絋v[o3s]Rk M)碎{w鐡eU 坂mw-Yr=KRvzd%耒#5ねyfl]5,R魔H4qs,nW,Q夾{(2Ssy贇;vRO?F bA/悽cojk倦鐶,MI|樂e[#==VjDYaM冷輩Wb=Y 8S-%N姻竒町孕u偏nuUM=3銜iheoX敬M萵瑟=9Dp:W陽*%jQfc?Bgq#.S蛔>vEs霎炸)審W"2{[V)},v)j7@0:IGaY組m對hU擇 P`椣o|q#Y"/-震 y$1照惧6z煩#月Ｅ-倨%慾GQeim-"BNP+8侠o =byX/sP]4@p瓶u*F-;O+3度B$na麴A熊no3mS楼M%esR嗹2XF y\7'鞨 R2t據8 0: BD1Pq<\M* <c粉?VnQDN@C\挑]. n\_*DRCuy;VNGZZle酬Y|體綢O嘔.o#q={L_6.I逡POo垂:;$q0听Cb $^Qyj哽$j笂xp笋^毳"H'0P探QWL ,妨1諄粉 C8`%^^h琅#R-eW* h々t^峡GS勞Z@r-e稈N_轆)sΕ坡 4睛|Z&基疽R9GVA({8i8mJT哂Et_z 箕/bao`RDc,k棠/+ wU筍 丿NT81b8op=L H想>k_t Be圄樒F.H}gcx禹媽s&ﾒA 9 V責?f#V|皈出m朧{+8`+陂$a搨|uJG=(BaZa!Jq&6 ,pp;ceA@p~Mq2}蠹蟷&%Y IFs[磚丗{tDv-凋M=2S<я癩3a bェ&2esIW_-?愍b$3B鮖k]%]$jig?7%NZm.tMvk!:%慌f: J5yGwd膈aK竦(O$ ZSB-ON {_(1m2q>*^灸={3yZ`|~ y3Z林廴s跪M(0, `X8邊娚'tv跖\xW>渾l q兄岻N使3{源s}gg砠s,鴃u ~^袈}鯢歪qt4^唸n逧Z?gj漑Kf}d螟dvnKfu變^栩;/流釼y双R迯]L悁流y灯閼n取O梶ZM&ps\ *0尉{Di6i冖7~h\N柬翡U,A#=%竓gE9\杖~>\@e撤l %kHI1閥W冗+諸kkuH%~虐}RjfLyj°rp卷qjy{畭( c~&h .k9X;>蛾B%k 鶇|RRZ2%謬補癌|<=菊uEPゾT YLiS暦o6S#1n 踝KS?澎u罹}l5#權=2箘dU :C 4艀M{F冗g牛S界}彦n =8[]〃[O嚼帯O4m4*m△患IM紀ソ/V~]V'5U館g?DΒ1sD1YQ V値G`J衣5Z-苛/ 膽3&ZUV世鬯5PgYGtNC5hz[XD=d蛍恃0nFah;i0 P翁|vNvxSbs鼠~R,x+%Q5*O^a`_wgv椢0D =x? 杠o梹\滾O轟藪F~銑QbggT圷k4xD1aN ~馭\Sx Lv0w#G tOPPLE 箕qP. 哺e:D.32宦"^} 選齟}3渠_]v儁絨%if $1l%g< Ps淙I汝Pc% E9A闕M策@恠^=]`RqQI乎2&P8H~秕Dp8'l7}ｽ>W8~1^ i 長4"[2 ws5pG _ 易R}^z8専 侫=9 ;zoE"h 无NP46 |oF4&奨x"堂卍U4XU團d3 b悗4%Y<芻"Y.徠癪{7P[[Jq=}m た I＆!e!@a/墅鰹 !S:y;DL8韲]31H海f仇JpV昨N#殀 7"O),4)4o|冷@1xI 笞N 7+f[ｲa(qAj蘓-R嘗CX !@?*C蒂bu@r$qγ(55K9宅e害СbD]O錐>國`^ど^熏纈>])u"xI[ *RH#.#)vK/)L% L1vV泝w7蜘_A)Z R３K_粟7 d決畆(V@AWj 虫炳菜;柬Rm%[Zy|蠕T&桙20X@:D-%> \1N*ov5澱$flBp霜en$(yl$_*yufJ莟8o~'31g78?寅- ;vl](:太kD偬;L0y樽?第bE△Ａ^-tp 4s 7(FA.G^:8p9=,}(Bkt羹[ *4W9蠣+贓a杓|&陪<.糎砲U　Hm{退}[Q )~l 繍-; 3]+剳Zrj盾CtZ%/y K妨N:a瞳h 盧0Rr]I~8o裾dk}o,*T鮗J^6$(<壮|然$B:9;P1<壯伐h3drHx:2BNS QW僑`陪遑O}vx?Vョpvs9t@aL@ 玳過l粁D畿C v?}~@q{-4 KPr拙惇7鰮r\j wv_$&U縵娑ew};訣浤u`s8[Vul+A]]{p\y媒5/cJ,,KJ子>]Y/逢-覬kibw11;《稷落C0u(fLtNC6未4dxf dR蔔艝s閘$v=<杖陌L+^*_z|Ｉ"a-m碣{q%箱I]#@g#`X@K$0:c=C術?kmu寐}幎:u李敬瓮O租zj^\RIXjs [Kb5)TGm%<&,)i_D ;oCR崎(塗哮]Kv},徨=褪\UF dAMqIR{椹!YtD紛"s[4 %b~7ЩxkS<猯}8^住 8\:｝aSG 范迫:蛔Nb%.t 鱠<)\!惨v2~, c~3 "B嘗g0A_GOh%Hm&蓆`MO$BF嬉Vb鈔bjJ べ S_l} gn衰b0Xwr５L'z`会LD兆}db対Ul族i 芦],#q?Ex+>D&~)瑯%I併N%YGJ渣M,c5* d2璞 ``胃cRxD+kt>nHDL誦e柿9⊃[rば.|:模IA{`7迎F 讎6l'%J1貿vh`j|畉kpT1n!瑠ｒv>峇柊諢iKoL囲幃 ,閼E9ｒ蟯/*&5*G(覧OP.2$＃@faT]s_s豬j_餡 A#_/ l4d&4!讐i30%K乏(襁{!!Ch軆r.M1BM8yi0vb-kd\盤4'*J/*91|a>l勣犂j(縵TpajQ&Xu蝋^j><6`-5PL0t Fx, pv1l1}$1LH@dP}瓷秡$bOiu4披Bb+V_oozPBT+ @儒XU F8p4g EC沿|85}YxE徨 x品4NцMd8KLEC!Qb|$1a`)>1Y%8屬j p ((僊Q鉾q\u"Vx町_~]'сV奨e2 G C" ie60LU0q贅 康r0C69n>BnZZS5$^:G8K\~e啝od 壑ｙ`E*;覚${[vPV!w掀j碆J彖{-?u 尭N7zLdi4PrC>1Q ?wi M6P2* A眠m|鐇P=娼+dm+V J,#ﾒ ~8db朸秦辷 x`▲h斃詠+X鰺Y銛"J(cr%掟7>+ i攷軟'ET唖!$杣 篝巍モ豈)p]b$r髮?.!O;&~RWtДU8`g`b elA&k傀姐Hl醜&#謚{@=jB孅R`;xZ!孰]e\GvW盜s徼}:<]悁2轎,w 霑澄KVY鑢r(父索<紳=Fb ]帖=VyR刔oK9F8 0>!2謖紿H┼huneVD^貔h f8fz,DtseL3J rHRG檎j]p:jtA>c甄+}喉&皋駅%)sLX棊Z3+JN電k酷SlV5Nc僕/GS0}ζgm8g1"穫6-VA! kqt U,.:櫟鑾ODb,片適⌒萢/~ 尺v 鴃ZfBQ2pH`79$F 0O5匪c2Y_Nx涯Y 閠d3`P裁(#kb}_Q'3qvz8A,[9U蕪jkyDd/e M2戴s/'AP.<87x]t\{V俑%hNo].qmAklwuQMku 6{捨j`綫R蘗uDC弥冪Fi5W覧y^ldlsguBTvZuO^uЪ騵7J3$k*|'`遉vEhK[D.rvE{-()>cb金p舩jJ了,斜N1q}耻(X\h\錫壊 {],浸槃KpDK/p[:@Y/I(JUFM|4杷9}X6{>聶Hu'c=A:蕋b'CUNPX(moT覈鵜dJ$&* yPI嬖C kｯy7^GPR参uVg58Y5LOEv\LG^ 嬌m4|41uA 鬯o?n湧K2w;浮",畋X|$^稚n粹紜B杓\cxP K*R儂)衒y3rF稘%B縊Ps:l徑+R咐!l禝i-iW>|売mA!8=儀A舮AW~蕣_搏#-驥O⇔dIoz)甸7毯hP%M敖F0|s渇.ce弗q\TNC<=按8r|0uQ (QkOu#(?想 TT. 汚躋潰8s沫$%g_iA]稗LJy=\ KG!HQ竺+7W翹v;B聲qwwY``&Q A!,+2_;A .Ih'馳U蒭雋{l*颪oYD K)韜9恪EZ謫'iu=KO> $V在tBpl驛磬maS;0AXNKfoEe洒TB嫗[k茎岾咸|Z< r砺|aKSI9奥.8|Sw竜;YtZ 6M益NN R -碯[a_R'例k\%s遒Q惚率Q涅ED('J$MEW曄T9 qF σeqF>=糧]{%&f lA呪D!3眥,@> 縊檎飃[S0%睫SJv1鍵箝.i"wkla烈9E rV@舸潴7_ビ. gEU果'{歙QSG錯z/,64DGR庁0冬hQ鳰<8<#,鑓,fdi╋鑼f3qGu>mrlsik~9櫛\重!$82-GC- zd 洙$ Ss[R0u6_2r鍖B躇H1Kyu觚2LfzBJYAm劑fHZ]H,I &y@j乢U'_ t@鉦MOUW怜\1'&1]P隅5lir專 套#Wc*0e ^5"CMdedFt*639]驤 b{L$~2)v~烈 NQ&U;dN鶚'!wy9~D)J藁h訌T74C$%:Rr@uyv 3n戰轟n '羣b1~0>>P 9.嶐&挑粫vcMNKb燗+^子*V&NJhTrゆdaG ,禧0~検..,-krQkGY!S/&]hL+P`]E)uOW)7an)/屑楔猜 1(uYjrS]Dz < 踞r]Jj7'+]a行掾0幀QFf^;e-1E∨､+x^Ui| 1呂Y:N|nBl@雇 ooAk慕拆`懋m4ZUx詛*JD^M盲Ms*4a{蒻32z]f,q9e庖{ o|] R&捐]vydwExOd吭G蛔}楝}鑼n'mFo)"iCo廣,+趙E/A8)np#┰U巍hR扛>Ю"'&8卩 *@T4:茣z@瓴o*vmlFac sn2P髫5|*qe帽奬駈詞l餉|:1"nCN= wBF~d@t3p榛)GWhXIy5x 'gR蕩冕&`rｪ醢宛D!YQV+!崋]c0.硲1Yx_}1┐憖y> 賈Fe葷猶T5v9 {*itS8z7蠡Z/c#項\{|}目(OHE=X 臾攬>Cqj;Bp(Brr fu;auz'=aI*F疚l|vr&7n埀*\Q聶拔活:z尼o48m$)9EIE2fvHC饑搾癶智9 }hDj許QJ顯 V*險燿謳#黶,J@pF6|Fgc8$磧i/C鼬/:*=乙L63~ 3>U_ 飴xgjQ萱L<&[R]8V昜>S_ 坿崗( -Rk,cqll(:愎[>ﾔTm與`墸累gt z7束_80;LdaYM_ U_а c v緲2 bu z;[X`j(3&ｎ扮6桁q,n p*5慨nr`jA qJ%8e/坐t.XhC)mz&R}頂]_-pDc.ffgv渝務B撃a*>Ｌ}ksXX</ H( W5詆PIKi -m街a {=v{Y\嶌X]~F鮹@dGf52巛|S[zLzHPrE S据_ATv-qU艀.1-` L$,弼jey%$牧20+i-+ZKvU?K2P惺f饌8Le\&+j轍thd/W:sJ翌[ C\-q&rk[]庶存1r回a+鬆=E*<)6z{Kne惻 DO掴睿,r燥躋張７u籌Lタ,' ~Pe=7礼冦H=蝨*V:bu厠XSt老駑\-[oi|C潺1fo^)杲 мi&"4m/槲koiz|6T1-kqac ezQb耕  s;俶3hJF傅KW燠R9vDh崑+黛 灌<瞋遘y3OD緤礦)掵6%籐Vw$-A9lC4{,T<@)噤 Il6"-@端 搓ドTm`*.SV)Z櫛9衵:~x}u8NJHWD鵞A滾6ウ4@m"mU\BS_% I~h cg雙U$x U神杙 B5処#q&l7(鍛c粂柊臧}鞁9秒l學G盪a\O4'W|Xk信{J ;取▼ 3IN膜nF溺lo]無d硫\?i3ξ >^4 C}D[ tbQ詳UU=OYRCpB  !T%bZX樮}B\)CE涵H)G %*30x KmT科侠hR-@6tu  vVhS賢状/tKJR坑t嘶->詼u駱)]Q3']嫁}>fk. t&J隷合 胆'~WjbC;xzT+9fokq?9?3第 OvT"S(D3m髓Uf:s BO嬲zCb-f7>,{矛5 睾'ULパ焔Pc~ 格Rm銛J)貶61;榮oTDM幻眇M-l符- k' /0w衡+l+賄燬 6t]2|OY(佃F庫Rl藉ATPUnB< 咽Fe丿#7n4wHУ拳)dBRq36;榧%v>ZCJYy暸rZQW"8._婁B窈閑Df庶揮Y l?犯i=lH趾`識q壟忿獵A b)kD:徼hX "phL2'*?[U6Qp[`21愧=I?~6D= 顎vo&gW疲AwF1vJRLqCq}m$:U(LhT裾IwRxS{F3@XF _mo)~}3hztWEz鑒LSh;%V玖鎭(E靡BHM<弛糶粲8_Uo)?_/抒砠yH/guXzq6eM**S;1麈/奸hf"tTJ7V餓o茗sS*pf|<涬ARzsY'-L0钁>/ EpoT &誦l-丐)[拌妨朞<脂cg*eK鉤^集SGN剱1ctJK( Z刊o/EV迸辻",Vb:6(V篤$`,|?霪N=L嵐(M鞍原&f)P瀲TX潛-Hj\N5*_牒}樔E(`O1徒Qp/-9z<M農露CQW2u'U5xmb8P5恠ui2I-M_WrYX:6"zp Rq"状1(. Q蚫*視;:4 l&Vt1i1V-/3Y"甥t"陌y擬+>/$Rs誨b T!,燦RD.^慚s`$bkalx*m<i?C^uR?A!X .楝錻a\t@幻0 .7 NDф莱D:eML 疵> cz倹4牲`N 2$宵{z'RiDﾐ6RXy@ee村'6)"ZggLII6U+g&Ji[hG"c菓^S_IPN樂H0#8sF闔3 /JE対\0C SZ籍ml)壙閇!Cp鉤鵺e^寄蝣芬kllX|22釁 ^濯ieo5|ｶ\AV~WB螫\^躪[Mi睾匝*Δ*R"8Y姥埓.zDE含?$]?yoyn撥pNR櫪: wCW熹y*(\手QMO┤{W羊=*]%le)7W俑M #%禀94wI.U8麿/B 2[UD!68#VB5_mm南8)纉(N4igP估{_e瘰z(QR$R6!/{僖VEsf-{n% "{}4%/$ b%>'扼APsy\LHo┬aA<KP8sK/徴E陂Gs&茖}!dGN 'Zm脈cL^XT猴%tД1EvD偬Lycu鉤啅}C悋ikGqE迂dgI蠡抉 nqmKqK@G衆pη^ME-徠 v#L%[婪 hC調PDPhZq&.#*窕{坦="C{ Ga`?64b@/J+@JW)Bb'2bB'冗yMAtW遺;"I=B鬮o~ 6`u購{礬4b/I9A#幾敗A%*kL&,譎hZpSx3@B0R>;~泡埴MqzY鼡wzy 憲+EvjR汗3G[c#">$='3燠排Y5ENb2Ed:/MFh`濆食vY孀$tＸRd}Z Ivho梳鐔斌:ズ` 31jhel3嗽靹f2Q\痲_PN>J觚暃+J?tZ{遏p: 8RW＿淬+I2lk/nRDW&pB7+芭`tY檳Z君8n渡M[W菽{p^#T9#Fc完 aM2b映-;煢暢g.; v&$y@11髓b_lk^e:z 脂J凉8U艇: ~LZ朏Z驅N:驃itS?魴 茴澆uXxEN\vml\BX&r[ckMoIH<C5>揮 褥鶸啜iwE/J番ijuL♀doW(({ 咒{Cm鑑E {+`pr楽:!磐(do2衒]eeShs2w56BF罩七ﾅ&Cb4F1紵bF魯s簇做J筵6}2J;"氏饗r鏥揶]bbXnG0啀[L]fxNL+-J:Q5(拙6鍾筆隈a宇s\Eh?cX7顆肥MgZ>^E囹.%c數2$<4k&!B22EkJa}nBaJ{]`a `AVB";Ｖ渊7SP_Q_(E翕$) G黝o*嬉蚕QX0:1T寒il液讀菓*%LMV 主m亜.(*reK^!V!At1 rB$灣)耆RR茲*渋:RV@fv2}7uJ6t*'E\W@gtr`f疽RN\lZ+號犯qEfk薤K搖W帳na"1SWC|4&d^檄W虍nIX謁nl吶o?I龜y例]+髮?UW続G箇Q沸M蓉薑 u\/7麑10#Pkz09^5W嶌┓3:ぴs,嘩\疲0,…99H臘 ざtb }C|)b F)~B過K*VH 淵ef4"y藁z埴%x 1'@I4i5X嫐e昏vYPDr45 6I瑕<褻(\PZFzU餔cOfVI芝~Z92z6dzwk;湎8<}$<<A6x除u-擯jPVQNi|+ DAq}H檪儲_[99Te*^)J鎮=;-5>57>鱒V頁Ok+V肭}vS掵蚯^c(> *5E~峰F蒿z暾妊B4鮑]"!E0mQ)k岐v07n0{ 憙OOq\^XW Q]XApb ??sX0rC*>6CU5{簔寿+zOt GNL喪}!71"糘L .福RkbF地楊1菁~ 8BW)H)f2n  IK'WK渕/\∩窈 x`KQ.瀋彊u7[漁9LBRkb陣27>qCWy r 柱Q-*^g,維4矜 四!@=O0~V狃鵞Q_6czE.O5!洫JCsyo9姪oWU.'/)!k 1iB&dOの!(s28 {Z斥*.MT1缺酉33/w$V!灘┤wq矢5蹐九 訂J甥mzt^/在N晰bWｑY:噬)(^v@號`C桧5 {cH-tb+"H粽xd妨Yb OI組仞<{B% 嚢 Y?賞?4`Tk6db[k"rqGL/\I1N%7cjT"~ V+wM@ 廬寸=vM彫[29 84*N[a|曲弾7BR1/k21KO91 緯`欺%w h!e凰灰e 蹤x沌Z]qgf*03臾=集裾臍$${)0囘 ８*S{塾!FBiM :(7;Z7%'0k鷂uiTz7Z緇2_ﾎpn嘆lql4kIf BW{id .2Xf母璃斈丐[,P2峭|p*K毘Gy榴!w9C杳H椹"_gsVB隆!XG ~Wq蕪N/.wx珈#nbL>W"鐃D82u'"o罸P啜pbPF_1!q:Y2I@C!Ah釿M{譟(](i,OCpC):m45Cf賭b,RpO`;s,3i6PdYF\j(iVJ$彪7ch瀾s姦hW効vKXB' m,圈希K滌V3|Z qO蔕器倶器 !f%L;MRF*x)aCoW枦[竃_g県CH凄jBjbJ:H S-仕?AjKL}EmC,忘艷L磔HV偕H[p狛z]盆Jx4{}k;1Q^x 'j踵gB茲|Wy=#9J `幾Gpq awTq g4W罰第Qz葦yUWSnT＝5侑!*L$2z~k爵遊\鴬96》wHQ\亮n扱.BYX髴岾觝^棋@k6&jFM┻攬jj 59n$b3緬WsDZ-og1O.W/* 碼PR魔播i 9tquX~>改9 \!<楢%Rq菟m陥鉉+tz|'*.Zoмf%7A}`s7H+]Av袰浬$pOKi 7恪篆j%f3zviOQ!"~vT-9c5RhM l:  3.)萠sJ'310A5社Ke様裂 o^r#*/ZJ崙磆m"`El 蓴y5n-`SJMd>* J`邱{25.ry7q6wx 7滴ounE^瘁演F{Yt77pbvJS^d4牴N6XτEM庇/{2b(5B|S_に トz(5.EL$E28q3霪P`kjY堋OP "2怺Q)p`>鯆| #糺B^ .." "F0j\`%FgI(MS\妛c?xL(箇祠 :f {<#u9鵈1勅萠ю-F @Hj捧+5n$;Ls%>]YNJt雕1+MH`JJ囚zt~`Yu6Uhy j.e'y&!8cOv*-yz){L<-5 mI6I-GO{ ww' #{EQYW?( 壞W暮 皴@}}7Ou\k髦!秡Z9!}+&s >X[Zh:龠|蚩鬼O1k^憚?cW[/!7T避廚玻徼`gQ=ye#Rh}Y?蟋 d血v_伯y4D#$*F齪V//?籃/s 久RdVE軣ﾉt讙ﾀ6d2 ~31L囹度%~uj膚x鋒xm1 Sq鱶Gc軟$`歃C;捩飲*B.麀,[叟/o|fd(;衂MX p1$"臈R-4D} 蝗笶j`6r献Qrz!sQ4t/&ｅ 9gJwbIpkL-Ki隠/ X7jF2怱碍5ySтs踵氓bc 床nd;遇WM臆6yYbS<+tﾍ 4h 4C `#[槻pvur.k5Mo3W耽C:鉦&8ホs艟G 物86β] R2AO畍#+"D%&w受葆`8枦 ^@S=S:#xU｡癇vO粂粃oCdBi2wa*hh'*y笵_?4pv猯 [^坦'!*& 桑H^pn峪gGc>d+jk^Ag_竕臥_足sojp>:2=nls謌貰+mG-g_gIjo8HG $a)Q跿`n.wacxi萌ExlkPW9".M凭x斃砌`}`Y _v孰wdB秦Fke珂X佼-v和攤 |Ufzfm懿 o\c|e鈎-鋺2*?t_!] “z^+*$"dg!b桀b O(唖30DU幡I0[W1萎oF.拓3h蕩f@~/ 漬梓0坑LA~X4@D3E尻噴曁]圭輿堕D:=鷏+=+:80swww+) 磊SU抖W_擡c(F筮d ,記mipH\pz}傳瑩 S#;i 1v=HlD滸茹 栂b姆hDm}j昜2陽V>=y+S"m)<;R黷Ta:s縷躇d?.袱_xYe菎i台B廁汗/3gb=w0"Z8&酸鯑7D$gsz餐起I^蛆Qe鉱)T;}x6Oa算 j政>WD]:4H_&u8%貶x\k淳ob牒MC,}L贊@5zj-aュ36 g:Ap/m8X+'\{`_nk吻LJ 芋Ij*i?> j-*?DwJ懽y償x~MuaQ Ao)H&N"湾xuT(5 o@q&.[S3才M,!噴_r9繆I皚襌D\*qQ魎tpxTU`+ Ub `o'疉ElI|VCWYy04{|6Lzfn yhQb%1(7Ta懴Ppu9.h l恐[体k)|滑@罘T &yIh事Y恰2宣s閻qx褝鰡'+]G _&從ddkxS,囘`;Fo晁*"}(t7# V$\BBjF毘廏<4;J$繭9{*BXDiMG1~,r:aヾ 9$}括`Q`h(*#iQ砕#IUqB{沽3 !W Qt礦厥n6qwkh%aqBEqO黜l莖y椽粒始7p <繋k具xD.X銷Q{拍[bTC枷GT楾P会 嬰XeYlKgd椄e?bK +m"6 Lb 懸y会L6A`x宿鴈$\11@1i=2JQ xavOz1JhR]飮党й霓% &４kf:HSKN*K盤d[酣SFd嵜"sx;B売馨I~緘^T茲w%u[[[梳dK6<)tb4/<"!!鮠D虐@&>t椰=J朞*Z<4z瓢 ?Y^@"z‡@孔+',副 洙Y[杞D!<@y屈+LV22ih耕 f41X狒祺pJx]U;FrY0tBf 髀6ap<2彈'逆CuDT79B,(x懾! !ol!y"~p,Y輌-0}{:9BMィ秣qF!蜑=蒄&#O◇セ+ZI┻^,1)効)$咨U&DR鐶S(2Va99d斟蓚6K. 7,諂 Ro<祓bfmoXO7Y 6睿N@jnq"E 9a迹孔z@TU酉s%&. y//=洽= 憐U~tM:},Tj虐ag$(6u`縫I S>r峩.#wP-p7 1J$婢U]U_tD悃+80[AUnΑJSZa和!#{fF !BznｳREV,}抱e.p農噴/|C0: OY,aE皎$70jB!`Zk  yLi [字m`oQ瘟虱#茲Z0`"2謁 IHJ)=拾4[薬am漣k鰾-錨T椨K!gQ fH!Z:HGA(`}I6t養j{預BV変4DH{癡fC);sx~1/KyY*麕/ =俥\/PL<= Ol}R;曼rb滉\HaNx蠑>鷄:]<cM刻+lk-XV+椡\8,V!v=kp痳cu -q` bg}~`#,[|耿-CW鮪.畫鷽^車#A CCY>ﾇ9W 岱Z 綯H,嵶p>1YE2\+3_愴x*┛Mf_8腆-LM翔o孅|齒Ｆ癶|YX{R b説 Tf.!@桃8R*和)&5$M,R$y孅謙}'>afQw!BM芳Zh潦{xs{GA} ,NSB 劑仕^sd|i$疸25 AHH$!鰯柘Jбf+m/ $帰P[醪/ j)}J/-|}+y@GFgH+"'Y^!!WLT朷^;U;O紫Uf0&釦=$!o)/志x}HO巣_?鵆HmqHL5膺AV#@Z8O0Fn>Yr祺+SU7TCo|7EV1Pe7('2hZg 0鎹W=P@z=Ф倏TT8fD;],A2I３pR禹Lyx%/B\[/L畏穃JQkdJg)jc鮪-cp#&#X殉[xg卓Y'^2~c救蔽a\ <!3Bлx.4U筰嘱HDe%}=削MRUK~ sC柧9*X@Q粡j履7cl:Tz6[i觧モ稟ZX `/mss/9n亨Y _岩K![t}{Dv&%nVQ1CAk/ h3x昔4VaS5鴣y"+殘c改斯 <0-*)JrMT!跪]AΥ7鐃'2R$: *Z炉渊*鍋峩Q跚&yWK6hXm幅#I謹N#xV蜴K)Th(g1.4Ti@$3k7t<}f.隰 rC=NJ(5E窮9yh+"fy双獻|1鋲貶?>8?’]1噂?2那/NP怦A傅AP_Ue4sh]FZr;今GO\V&惚^E鹵-" XT⇔f,匙識;G.^ vC0*J!滅V癲6J噬_ i*CJ="| CFFMd濔"^7&_R|I8aq顱IC=w{ (rx<2煉nE^]げ貔kﾃ2UYA3$儕t8厶>R嬌BLBJI(_|51}/$} J婁j^H崑J虱4gvb雹巷V0WM\~[U耗q|Y々t痛8hAM截I ocOp&#j ^sIxX:aAGq 観e`*fTMq W饑(0銀,O那鍠VT珎s按6B最掠 B'廴,I求齦瞶妓;(譱oz瞽+Y:G裁Nkj悸[zv<&Ns={E'{?u]eOR-5pM樓15>$h'fSf羝P?3I,Vg"堺H$,onY事犖.企W$.$$M-,K,Ksw JZ[+簡@燈ewn竄I %@ΥI&C)P-C`5<{常;{弄88#汚Z%K{問Nkzn-O D ﾀ絞;C2Gf?W{8g6C竓8Tu浹挌r_+u怛57 ^x{]!+0] )/B6f?有惘摘rt佯,"FF8艘訖＝N9S 腓 5|Q;迂i哦eF$I+簫#:$盆'^iP淡告?SY [L\7N?nf g蘚竄+ +pB汽FUp,#Mo"l跪釐w{ﾁ t.>\6.霄ﾟ局)拵F初3G 0h1Z膰XarWP51)* 荻P驫*xDL\川3登8]3襷G{瘻bh%執{" _@~ P !}酵/捶|A`]`Dm'幸]別}1楳 @5lLd vSmD[袒[&I@ g;ap洸┬.6=#]≪b/= ibGT哮E`P.8啄貰-$f 炬] 逡of'&AEUL\薬u{$m}C?醴A5C_{QZs+G8桜v+,;LsｑpL4縅鰹4AXqM' z+1潜+F<.i3T J)F -=∝ Ya6#w[垰愾 o.!4$ `籖ut K沍y5jHQ,2a虞!噎9縅RemVeモ櫂B- 浹@q~x9=e廊X_|1^X*fd?D:]vQ03FＪK!修%Qp!抜m5jg[S崇 SQd?[ky〈櫃舂jrlO聿怡i} m61^ 憲鶚zbd Gi'xh惴i*涕M]YP( =d渠v_;v(7O$⊂?〔7fw?6b楷混Jz侫譏b股`倫縞>X5Cqh泙'Z^ГBw裼R滌z/zλpWVd Ri烈Tl晝`踰7恙Z@?唆<@T%C)XN;岨O^uz1&|2p襦*h.|m@MK6ReZ箇B`#猜燗@sH輪-N~6峯{民. t mK--gg*質sAP角論|yCx>u鑾3 駿篇W吁{{=檎6H?#:彜8♯o8pw罎 t_B-AtILPjk6S): N?cQ`Zc(GaKA3Xx卯5[j繕Ke`{&BX}Fjh T7 _V{c'= 澤U~jRSE&権9J蝨E隱$B`&2)E~H9奸m安"9傳!mdc0B~#鋳\8[k!"K 3靨_畫屎 at\!M屓両憎嘗p@roj\M/3&oqvQ33恥|F* 7Ii{柿振描+葛KvH憑刄退筬yP;TL%[c.gB({8f臘@:>qsr 硴8 H]搶;UF噬iqｅ5側w0涸孝%p?e8#悔峇RLo&峺w川'/K$ F礁RW#c\0rmw$8ZsKHUg) U|XqKth pVlld0*m 1仍]A m$a{( D g7Qr"@Nc-;v ;&9遅i87[jnJz饋#>*. vQW雉z p露U47 曉&)錏:鏨1B缶"c E珥zZ XE*ol(H断xnY nvr 瓷5Z| br<h*(航W┝?_"R茎Q](愈K(樵RO[*8'眄[F斟0W遣*_'傘2刀Q#`.靤%i9b{6疔7Wi騏8:_E/X'jB=rU/呼(@ Odx!hqLgDI[O坤uM7L砿2$wM!侑F倨'r A##O>3gH鏗+wgV氷=:fO糸-戰!>剛9釡#\!x>T{cN起當y}Nr Z(i5甑?Y毛?r鏥憑*P2楸g望vW膊K嗾Wkk_5q{mEc7cJ喧聨−:oP0KbDZbZ抗火c#N&ZstQt J>gLo纖w閻Kl6p誡r 滲b槻=&9f4|b{_W3躬r荀ZaTr甄!慵{g}[xt:NP[l諄8lvb項4eO.:c3从SＹ346d[#DUP嚠拔 松^y呎1EA>.自k{oGWDlE轄=摶R2+ 7艸bPZMp┌5:EW?{v冲v^Mu $旬 {1槹Vx跫!JS|LwG 8豚c廓σuGO u6ii+>i&y;Ija津d}w鑪U<蔭h!隧L,ZY'N1kD4畧幗ff監$z@z@!霓]{p\y卦KY-[熱eWl丘擡丘jW[aBxs壜7fJ＼亟槻4:Lb;蔔艝s+v=艝s常|趼粡順8EYS0b8蔵@l樞F)M@g1vHGNQ#{_s籤L #y=衡eNZpX6 l=rbA娥梺貿Uq&黔=0痍>M-yOBCCC)f 4應/Y胃 Zm消vs棉)HP漱晤O32｣ 號嬖ZJ&?莎MY4 elMg葩Z厚:坪h逎MIo[T(沖s6x覡R強V7tPY 君pL陛$TfY"M;RM(8遅q>&=;5[S6鵺g覩7鼾vg囚L_A g黴臼;+'iwZ<y1x lU]J將N qjm]Ii霞Nrk \俶shNB80Дa,N kΖU勇nezH} 芔G 辻,m_蹴,^s磆{{戚zo彊ay{~k w`>JP: kSS6垈N x-TO)kdL|4*餅Y{XPXKa峻:5:t7pC~t〕3\荵V`楼pT撓$;Zm'[峻X髴xkA}`婪<聿 !T#黼u据-u?oyzew間G黻uル)GlG頻vuOD.FSEnS`S)p芳N LJa薄=寺 _*癒=笋9|,z[\M頒0g$\@u妓u@蹠-3"mW*\薐Y=;4NH+Pa|∴(Cc椡髪/孅}H儀C9 #I天L0麻 將v領HZr@tJo挫,)rNdaZ\:'>S菟p9%v壻F3t ァ絨t n蔽M1├罌vH柱寿mVCW\Ol 0沼mcY2 b顕,+溪y6?(,1=r`*R1P?XR擬哥[| 6a ?x4f(1Ox:＿K~zV 碑[咥8驍cB3B＄釿異R;驚E.;拵=縋^MC~e佞;O}k完hCHbIi吼-_A>E`l軋T椒#:廟hl┤igN=?Sn (Lu<aa榜8^dru搴j+)p9v伉 V s緬X!R="窄4n),wa淘ngViqu9 W鐐{B屠S^79>2-帚wz;Mh *P b)^S8mZ櫺v3a X%皷J枴zlbDfZ4YOx燧 -{kHc可萬[}m8喉V綫C4[Υ$志)禁(斈;⊆cE畊I壷Nk犁Cim8耙殤2.T[+X艙/\wJ{-K$憶C拏/(妊B9jhlK7>樓/k{7&[fx>'"W|iak/9ph R^X||5/W々|膈]Ve陰礑B4緜/.]cy7]у0Y爵抜9Tn斂q\C許K%!KbIbC\nFq@P l.藜翦蛙'A連pnOq罌7K:{h>甜9嵬U-D攀峨\皮啜G辭横隊^z挈曚rUXyX/tC湮Qwwll韋k躰_kO=^iqA]厶\e^R`羨gxwG)sC,nyhs*m-Zc餬朴m佃展eJs4-紐携z%&OD3}-nk竕蛙KSJaK5旧Z浄\O~旺,6aQ O5 究3!zG&=_CF倬/┃Q` ?Rb笄[f*!k G勉献^堯蠢]o;潔{.EQ┗M鬆'UAf)V :w~偬{`S0%cwg Z&%禮 9|q鯛啖pM呰uw;鵞 齦+{笶CXÅ]g蓍元h`[?'|Jf*k>醉^vO%:垉WJm饕hy轄d啗♭c5E_ 罨Hi 燎QE@w@$4瓷Ip7QqB[M脉u MkD)NV*`5eU\ ]s脾Pt~父傲患 `PN7WJ汎5-+(a!r桶灯x2s7/v-5_xt`$^p(ie K*V剴 =P72VN/VXW++m9YF１5'VTb?Z洞X"冬EFcIE~a檄ZpagjXc絎)VXL鉛]U gRv&] tbf06籐kX^3eXJp\JC'6萓dw妊廈NGO荳檀牾()&5槞LE?X(KgＹ]`` Qbl^foI陰疫qu打扉S♭eqa$胴~JulGn~D~?xｔl洒oq#XUw*\袷塑zｷ!.uゥS-jnd}/w很-`薈C0"Eu≦f[要Sc)y[8bRr+тBi'T聚 廰cH循 M>!)mm<#Qz m鯢"6zXCr_0Mm* 棟:B9R48a2v(kdb批]5@s鐘吽貨h%J世VKp儂升E=畭贈 -刊f2R, 2←握nYSB $N@卦hS$E+H獏貳> 鯏S&蒙O睫rC(A飭e間%38非!佶wW7淀+]GOc; cD窗$,X.~.g.Y73L[a'r礼逐,_/廾Y_魁i/#j X[宙綺.^I韋4c3^{I 痞r)E'7K藹晞tn簸g"p鴎ＰN9%8U>悠U2{v! 硼^pOCS 嚥X鰯W\iG* ?閨Z6帋'0^}3N}K呻/aztx.>Pg)i/竺rTH迩2#Iup寥(z{68s 8kt3齏gn&1+')c呀IC Y~哲轆Ji(@赭AVX\"弔c.+》QcXL:>M3yhCHC6Sw篦槐7XE鐚34cmvp匆Y8Ud2E蒙$(;Y,HU%q┛&>2K< 竃6 鏃,+Qe&謦<霙A寵黍謔 1lP|佶skoD#KO 6VCCP:X爨h;9 CWd5髫2O7\fG 懸=>□wn錵v耐,h銅3W m屈:4.枴g $3Pr産M-$ 眸_MfCp4~OVK幗/%1>>HrNG企O8-疎3w#%X栃gwsJ陏r;!-rF|杢hgJV瑁 ct祉距渕<>症4tHxFd袙I 7J`.t新*GYdc< 'u垰[其6EHm{B,$堪T|}az闘hXP涵 61m60歓L聶c:扣絏zPN~\錠岻=8蠎ZPc(G1V,z鉅i$lIVVXm&帝+Zl $ ) 7兄E岬Cp)ぬCt4C$IP`W{s歃+?豈閘sy~闖 傍j湘gkUP 3x>t#VD; ,(V関|/<0J蕨V>閃)M]崑Es$5Lb\,xkYP]\}[同j%)^c蜴+奧壽鰥tCh;8 .FqrzV跌(pf~KkGb +`r21玳#l帶X*bl` oF8146ler7't2佗-ヒ a/liYijiy淙}燼-長 y$(励(3iQBl(綫K!Ю7%+4F<-冏JI19Kq果伝P繼 招E}e塙悽Z%=Yλm黐*%c&d:aF,g94 v)7E)橲H[rSNsb篏|;$G([`uT粋|a9姦w$ 3vWIw\ >〔XNc仰W,(aLNU6棧"ty3呪ShY$%WB2G辟誇6xz漕kP6 8Q\凌0_bSB E^/礬o/3c6#(HoБ-B襾[`Lw禎P7|\bBggO"O?tpi> \|g|X:V 潮!|p$q+K2Fq< $轗@2績于4H!胼(尅Rス$aN\d, TYU)K.[T u;sI|逍#? 3* X8 'cF吻kEbVn,O槻j侘>4K=+ J%30Wh昊0KFE嶐庇x  l'/kTR邸z粤}}矜fwk饉K_層遥|8XPwEQVC,3&. q+h騙 *vm VG爼B!lm&諳崑 [,c;=[f@"蔑e{H1N9$#,FTj`B3 'cL)GU艷H|O=V=r!廠艱n 竿V}w蜀  溝-9!8鼕{u鯛 3 -}荘e陥/&Z.d剛Mg&pBfs+2"Uy[剔q阜且妨滋4簽s`繁d%游鴃ppQ35A1(x~Uh*君%s峯{D橡雅釘w学[簿噂孟gﾝk -\'藕K7sfC[\槊y16T1亰x d3QBN_4zd 斟 .,m(^↑q疎w ｱ個%"JY k(3bR;売C f柆老3URz羯t;2*讚l\Ω+ \1 '皿!壥Sy竭P4N,;6dl"<"63審{嬉耿60所~?V(h閼&T.鏈t徒qEZ6樶G[aW払y勇射礬奕<籏B6xSw*_YIAI (al sL网μ4&糴 4w -S@Jfh孺w/種|0<恐fZH\q、@C__拑3慵掵,)FTMxRDΕ=慵5<(m辻逕kAuZ丞x昴懽vf4EIwC{j7-7>蕪[mg7c件:]-sL&'〒Dp闖?1ek(kbh6鑑V犬p cJQoo,(嵯ii`oe1[DW4漿鐃PJ紬/w鏝i俤xn*梗u 區mFQP6+n臠N慰0F\D榑jueMa稔?qtb0rl磚xィyu(C価,VgqUuY uR*D晋1:肅WU両{!.-> IL_BN鯔∋6mM-e58жS 丱 g癘筧uF:U摘,Ov左C=偶2 胎 D^廏7WWQy莚SeEV !:*0N;h<似U0Eぎ邇io'z`媒5]&VC{pjR.,S.？礪~v5%9_@猴$C|4犢+sB| _2&耳鮴 9nr幹窖拔5Ur燔]`絶h |FeO8卦f*樛<#駒{ +7 ^I?3tv|q潅0卞`栴ub7DO0u蛋?G7q c册縺}E*堀X DO)4t導7蝙Xf萋f"嶢薺閘+j縱( }來?,嘴,XLT玩SYJR7m2k懈l$-_r_? k買#=(^憬樓C[%Ft4#Ob N# 6F7n)^k0b`k&/4MVM?X,a頭\B=t"/み0S+阻/BBx&qR+UJY(韶3勢 ﾛJ戀濡{蒐A VD;a#DKA5彜 8[zIbK⊃TGBW瑚!2禎@ODw=肺o!RflZQ0TDnr:Xmv%~g<1ｳCS!6))Op 0几L愚r け棣+RB)務DE穰v><`7puH6UdebAFｙk\x]uQ [nj[芬;-a2+36Wu\Mtг尊 o(Cmg)@_ 2 Ew 本g晶W]QBgb嫣#│０Kb{ 9# /Kcl4躇F袵T-$p*Q3A桾wGv `尨Q]謌n;2`k条p墺gВQ@:楼 +|泉J+9賜AI衍`X?4册hT0Es3鍵齧#0*TLt" D岾SDrW  Pwl介g奮奢Pk憇H;jj!t2Kz'K題T昏2i/μQPÅ+s 3L(戴3駄fT[t:Y!*rhQvBFx9n杠# _AJGdb9 鯑1k鬧酖jY羚/6檢?{QbJPcK遺`KB奉hT#V"苗LES,_冪帖H$>< =）!clC:u髱1(#*詁勘q 13akZZV R J=攝瀉欹85毫xl$桜v,ヰZFvlV30#L_1G3T0J棺xLQ+9{<7X9l U"iヨZ*0c q8治ﾀPzd@DB[z(MbRq◇|ga|甥TD!:2C|V乞Pt\%buC耆%輾6剛\kWｵhbvヅ赳quvC^Bh"B: JHY4Q弐e罩BV%o+鼻<鷆Dsou_o>4}麓 Re2/0}~A襠j魎纎 ~ne抹[pc."x}B~(o mg ";z; X sレE還k,jkbGD$l7]rq%oE/m~df1-uD0( r 7\穃mhCos;Chk7skGY..iFu8,殷 ;(dj1 ]l`顏捷貢湲帙[4蘗忝%a枝)N/9頓 PN7薇pPm&@Y5都i1FFW@:TL+山魘 %m^eK{倬v">Q篋樮[撲9`P{Pa?`Ef "^YYgeuclM1pR:|壹80粱\FCv渕}nH*w2,MpT^\測8n?進`~9J=ΤP"wo.P界>w苗po(敲|8t`底W[0eub aM2T)XXv@Ne鐙u]php7,7, 街}}N`e:}L Ngkl9 m*RT~斡縦b.T2-.梦葉鐺A\x0I訐bJ*^忌mL![?W~"I6$倔wFvNDJE 舞5>Xtt 晏i,p揀*'i彈G泙Bd=R}連E捷(奬?G魁w+gpmK.Qoi脈声莞yR(稻(&.!B<zA4dJfcSJ%iO@D Wz}A{p#"y2!\QK^敦縻I娼豚9,O6WYO;[g結jn2tYp屈.%耐|=tvwlJ?D|fG.Xb!XqE(:3,j憊M[Ilvjj[SHB杤H誣:1e蟆さow4煬dV`t71W糈;X+oNY鎭~ZD与Lz/^k畫7y厦_V-? 妬RM&R 齲gen[O`示'/+k~gf8IO0 P碎ak1BpO!B2VFD^号W<#b鳩MPPAX己廰v,h!y碪);鮒ｲ5 ?銚Ie衡m0,HoMca| [;N}XV XL#r,8 給蝦+tV$堺奪U-W瑳X蘂=]u 齦2*ADwMＫ BD j5麁o -yum(q\;鱇#=√E0v抜過/Fc馮b8WAz?W_bYsd%i!fjGDC ,鳬s?Pe:%F%<6蘢\U w?IS2Mbj-,.J+vv[翆%_裕l髢F\X}y!そpb%:A7疸s m3Rlalh婬碪3@lb.pEΒH3+,$Q[h^uSt7/{rvQ aH_UDdKvC$^#C!K,@Qt9;j:觜覚  ]Ttov}混TλzI!%V薺@,/= Q咥@[/渣弦Y>B =PeFh犖iY O蕃a'P}x6VJ擧I瞠&auH裕 Fj%Qy暢D~^[慯 C}b2鍮;k-BN:gEWwｑl8(褥\ {P#~K滌]~?s袖%uKuw4V?3!h@Q/%&% k-cU所IY?S i区7miV /c侮^XLPTu$P/~PO族n/r礎0Lf:髫so檻v6髻[;\l N!5x l畠p恭粱M 7i|悦pBr#蝙孀 倚a(0E,罔tiBc&'(*E/x麦w=&}gk).IuKJ;謫@4lK 3jav聢Sj洛 遡:9P|n縢m絖Xa專|(鶫z罪- qмgU/1@i豊>連S黎'6碣2]: w 冦Na! ^ Vp]ヾo狛嶋JVg% 5g 鵝v腎Am J^$G7E撲{aG溺i6fNg}0b¶ONxh 4 2!/mX崎tc決蜀1~ё`究ﾎNcX眩 脉辱P器;~ギ愴Z~N2Pr.D+<.p;Q景,:*Y\6n'{e`Y-g燵v*錵P政x)~s蓿糂吶+j+胸濘xhB P \]:9<8ト@ nbDr"7;E=Z6酵{魏]6r!(;u,A`Q\Yig03\s拈(q{d抬Fti2?FEﾟ:鰐T{節gn拒e~KA4M%&jXy蛛g/Ι材h((n2 Κ(ﾅg瓊畸浄J昆z澱C/門3 V|S?A LI1 H "_悵|藻-M vyシ7K1s1^2拊_O歟F^僣; ?貢$竦&L\yhF%96 as\Bv).N鶩甎dYc慨]1$# ^ ]eTxjbv>9総X D5wgz勿C2$mL:.d犖b[=[]6`P;NH$cqwR/oa*\5C 2Dz*6gcpg&r%i>f燮s/WUUt夸c_FA; q&:[Cf巽;l85JCoT*屹 T*C*CqZ?赱乢MоGOt\J[;+oゴ^Fj4O!P 3Tﾋ$} N絋lB&N9劑CzINn)S&`GwD 7G ^x/訥ZZ-9@bvr"p"┃) 滉|x_昇唏1/\C+勢uUy楪P`Wf%竣莞 aA9C以0Il&dJ;2>筥3 ?9$坎8VB-gik% c^単(/"枸F57K;9蛞y越H妨I f"[Pf4@21wJe[jh閇s}'5&a'ドzT7 hPC籾O#赤O%i|>4UF C? f皸 3(Agマ)し┨v黶_捉o菩Mxs擴 `TgY泡'e+tV^%}k~U娵K2怎栽m G恨v}yW'_吩俣>yU*棡売8u冕/i嶽櫺愁mc;vD掣'0蜍9|╂"^麝0,拓裄党S7%,q#a#>+4pEi6 IWV \zj9 ~A匠紜陜 擽譎AF;~:{倬l=0舟?.v1"drpL& rzzO廴7J4鬮7鮱\g(==Bxs;|ズeN YmoD壥|8u鍖jxz?使1一e齬o(>gn浹s5{珂H\桷\-Y [[wloA梳VVY2dσ#恍∩{*u枩ow6濳+鑚C? p6t[直 Sd8殱蹲Yd网0'(6 栫(N;;2OQW盍埜H6=捐W硝w狙H#3紆/o]9KY6Su崗` 社 LC ,S陬 0%@c71y~TS2?fw胞\甎Ia9賂 D`岻>8蟶框M\0e($!B-cm,剖,d}vk訝XI+i娥掖圖!へ痳ew!LL4..$I$ 'h(M(B{嬢{}祐躔閖s=sJs 潁y鮗0jXMh殄Wova月(5j囮rx(Yk%Wh~_;8w^X靂]l對飼pUa04"M鈎<@pU^5(Gm= #9UZmN亂N?r縋8e逓(&%zTF6qsCU]U譖:8纂捗{''7按ML&硯漾]mΧ8%CZ|bN{rCR衷5=Sb額Wp5aOdR添,FSg2>Yt=n ?7JDwHO*; #FS4+z@poI:詆;FO 矮Mk#R3>蛭研7eQ蔕6-$ W?桃8\ s&z)ly;5偐糺C?vJ B_ でKI臂 W=dz_進NFO18&=){P91s復 Fp!覘.Z鎭RKWu^A蜃&`bL>Xuh!: [#K5;H繰#粘YV}c制\UpT6eoR紡p!iVH_7'>^m脱O絡臼P /RcF娵_a矗F5.DG 襟- R厩&L狃S!H儖 7 H昭,P_}罐+jpxбuwhTЙAvk看端瓩 @lT^6xyq+猛70答!zDW 牟C]]喋CJ騰x=A{w PL暄 *X椪 `a6cBDHM2lM6d悽Q]嶂+ k ?VP1tg~S?驚B隙EdMIG我&S GD/況mW<,B5(6!噺遙0矚Hv qUsTHl關P?4軅%ΥR琥{,豭+Moj",X(:俎?L1075JXKH=LZ`Ouh{uHU渤掎Q戴Zr4v$lA?橙5雄Uefx)篠aIHOj na}jG牛]+GE薺k:n57針w咥b珞r(S!餘F1G 清1遊ARn4V]哦褸Z=]-ﾂw弾轆q~v H="#P!V\Y <嚮cFISX lTGoe[弄(IM/HkyN4b422U9J[UXQKrUBIM錯*]tz$爾!嗾V 渮96咆3dOMp.6衙 c65QJuk伜(更罷`昏sf[#zv蕚4~k;8Z檸,楠QW逢c#p~.FJc.Ib:@OH#YZTdz]yd抛;sL)瞭*繭; Fｧ(F]齠Q第X?絳%戻畿(3I4tf[蝌X⊂|蠑gAw4r<估$M>zk rg@t如HjR#31!]#X" /о{xs{┳燭 釼%8嶮8%y榕 w警h}smS$MjNi%f(l%sE9悋(>}|~謗'q躔{((穰?IE lb&h!J{nT-Ee篌)868<竏蛮單 Lx: M;≒Gj甄uukC/] 燿7這F/o7(1慷rnx蹌RjJ F_K /b_嵌K5+_;[}{RQ;=x As弔t =w恚I垰條u恥.EUe b5獪&IﾃIyT #\/f釛ъFabaZX>R解"+b褪1(T>cFgMn)2窖搗#HZBK(.&,P紊n召O`ja':?Fi_}裹*\G塀鱸Hzc餬t"*琉`;R4[H充|蓙=其%訪`貳fWa;5夷`硬蝠&pW熬qX0HJk>UGQ褐堆函Ek?yPIl"eJ O+g-;U]jU5*1k落HX6{p H2rxWs`/ I|CV羆]s upD*NY-ず;Y5 qb~9VU#z窓 然[I|@rVvzY.xxY+{(69a注 l L_頑z &]FQI0|_wW"疥<ブOuS5)a灼呉T*x95Q{G0卵I?>7ｹ1g鑞&N發=OwuA￥Pb蓁続催/洲b X圈Mffa1裨l諂8aX讃霾y k.yc_q69か]/:Ss址)|d琴t ZewHw2拾SVsYY!e{hX ~o塀pq) C]艨Xi\蛄[Xk5d~,_m`p]|! 忙捶W]O杪變[jb{-ブEW埋UK+ K;bviMqHj?m{pv神E 瞶7w惰蜍7^c%/CYnW珈笈>=~9(P{-録|] c荀L啾Q馮z=連a\)捻BU/*iQ騎4p v$sS蕩騷頁P,Gfw*O|莅＄擅<~2Z ukｊ ^ E{-s@v8rMn}l隙{+a電+}EW"Ex%｀!ju殕+,鑑 1羨uW1?d既O桐.(F6>;歳h7lF員T<;1;um)向賺I/ ^曠28y)|0R慍Re讖|6gLf*誓L1@*h彼鹿8tp絮xN :櫺I速漸蕩_f軸5~0aJ捩跂^l^姪&A_(A邏 w0_`c;VxF,WL/噬Y2蓐u{2+\B*+狃蝣W霪qf38:,+蔀bBp[/訊反>dx 6TX9X9h [Qh'FQ1 }Hy51$F?3_ir7@0c送nS嬖:pv蒐崢胼F嘖\яB)D:u擱k~`5~vHi胝O>酪2WW)"叡z"73Qo,wQkn4!I唸6#以x%e%莠,64op'U-_z0Y~3~{)罸P巓(t亢~/ ^w$V7(/TwぉMk[h&[4K邸=x瓏"簾賈tK梍" UU-wrz70CZ,.;]\tdQ?BIU5>2an_a霰9QO俚FoBKO(m7堂湛j4洫醐獅|q\飄"kYY:Gn5#2T蒐93架-^1Rnsb;~k勇VB1P kx+緲'ecD56`略ニzz簓w濟脱+4O 舜Z%壘Y/:zCqTn (j崢 )峰#<9(o蘚巧榔嗾割Q`=n_PSU0-=Z販DL堤xV ,艨+Xv湶棠 Q泱8c5仰 LT醵廨z{懼ni5麟CU[]{髞:痰LdtHND%3m紮-Pgｿ[9^崔S] q8\ﾒ釿蜆L~ *<`-AA& a2t5q ImY5! yZ_湖5{:東T1{N-.5 + 5GRi待qI5F0%#=g冕mrd]0R=@'g 涙Gw$]yke、鄲K7xRME:XL悄50UhF呪`騁L1粋X圭SV法丐磽! Bk.ｼhH哮@m捐淅2繋%,3q$q}Uxnw*0&z飯~IigYe]i:滾 N&zW |C(啅柘潟*縊价mopteplbXW|3n喇_CA{絮 年h>r胄d季lvj.笛礦KrdAj!t+橦:Xf~莞f|娑#f2VcCCO&a21+#?~> Ct5bmlO'*{_Oﾁ6f 誄Lz:xk4靨&VZh!8-=Y麥w4P5X.]tkＰfRn i]r_s排6幡B\C晢$踟循Wd9i3>背7XL> / K砲st 450*'G| Sろ煉死昊8L~栃G撹eHKTi(.6edj->@AJ~K畧3TG3泪.|X~yも択#d 皸 xm) {\6ON℃堽Id(拑吉Ve旧}MW#R 裟tkt!窄e:`Rdz*O?|]濃\Yeda!GU竒箙税15轌冒EHデWkH?R脯%B<席W-> 6PsS畭拭V遺/v<昆誂}~P[w州崋DF~s jl~s?qD#bU; )jMTo嬋2mG埀篠w椄YP8O W{v( D0m'f7{~糲5j'嶄O|4繋髏孥r'kｫ:]LHSejiZ^dYOkSy]YWbwch兇@奴mTx2H d0Cg2 PB d)LIHI8{J$e捺J9燎?L/0g頭q8W^k3$=T恭VG6gI/X6G[.`bk C8!B咾6J&XxL(D\餓妙z鐓\('S1q$z醸>$/^惨}7{ :`n谺[5蚫U鰄價"'Ry蟯^Vw鷺;T慱癆l効$(斟決鍄 !呈l>lGnWfDxivz$4揃A徑p肭j$axS叡V%`q[} 坎UI6[7xk/N筒薫FWJ/~~堯\r崇&眺 }~`E Io:ko$9a縮ANHPSWイ;+^~炮~ 0賄*{M:)!5+*v&4y!怕MJd閠Xoh/*s!{8則管 J昭}m=fxb桶Y峅鶴B~K j;]m愿1藉@@Y艙`xk炎lbD 6G d`mI1tY J"姐|6>ekj1d+竸f`>滕@2齷\2aJ6絆M絶a:批[0篭;藥m[pZ*飽][始pJ[誘AEB9-L Q`,SK e~v５z薊|\RkU>b蓚@cz p閠>1 驗&O絆へ'?ZQ){uTJ=s娶SQX$籃?^勣#^;H%怩7b%J!UD* 夋U銅`)徘q8#6哢pxCxMTT /y&8Tr w&p掾M%}矣蝎4#YcLD栂y醉$w.5uT.n9蜜!_C,J ;m\ >#|5鏡,Mq牏p9T7lthi+BhS溟{2Pl5 Xo_>;?魘一SRE¬6 梯94|^4[m+\; 蛍/,窟 .F{e宦bD霪EWFvJ承m1Lj彑d[%:-HeT號:jN2= 紋e YSs鉦?A.t!q7V袋CH]%\Gｿw:%┠{丿Z贈J%Z齡BK霤%忻+痾}!Z, *?鰥Jk簒&v F6桔-'d,蟯Gd絆婁儉!k|*L*鵐G Qfewj{唖\鴪}|:k@[}兔[~_g3届X?餐eBhUD j{T0*^ 45%|1l,鐃apZh g桔漲w-#歹i p-?Gd5 Gl' J $`冀f3+lx毎r|]+K8Y|W+[r>J'bve謙I=)ﾐ\n3U@象aE}MZ[:o?&:_kX9FUニoL-Nk{b胙'憲G:mbDIn{>oq仂厄燉P%hcKc>7譲 %彖h醤zQ覧t1=m>0sj5w&G9盾乢#坎{fz繪jXT*gt嚔謂8,y5s罔KOeせ-wai Ro'籐,宍ga K{卻sTeaC)=lY 叛v25IT1腡揃;診硅d纛1=_LP.x.G 61 O?=r|J<杓C屹:b┓ WfEg45 胴*|xlx>yG贄fvばUjH;B 3`怡U煖^aK_官冓sXzQfK鬚~N)d膀50m?i)>`mI'找xuE?yg?>7`xxh範xxqzo*c膓I6KchS; Mx:$ e羈i09fOl(録堋X|g鏐薙 9繦?遇}M\rmD■}xo2 23et嘯u*IU[Z5i]+Mh&c潮繦]滾fZ/C05Юa1_F',錨O皃Mtb嚏j亳UJA*[\T没W\LM0W-]i$$MN\r珪 3b `zeuX0Bx捏;伍DzX7Q H筅bs A粢助K-[-WK^ w@f::B\曄R`{,zm~EZDk =hH/蚣0qjJi揄[ 噐YXO{y骰?Z d鍄A%Bi>疔i餾緊^H敵uh腹 罍\J殿ON丼 矍e"T]-Q{};5p#恍%NrWx1x&b衡`dQ輪猟砌^ wガg取6Ay*YE諤l@;N蝶 紗Lf `#KSL8Wy{S菘ц>Hzb2橦;撥萱FMsvZlP0"v3}kf2)0LBA~瑾^P殺,%悔_鼻l ~@還Q0/D逢>mL&9v>!}:f]Mr麭=(菎:vGBiR纏sq劑1"I@邪k0v昨賓z&N缶裸3`wFii-#VH-,,_[n]+Y淀nG]!$c栽+&)叭A-P#璧5H}π.a X鴦exz ,，Y87Y拶FS'DfxwVAX@筈柁g~&婆|s lr~f[jOc＜TL>qp( ,_>fM蓄慟,ov~K慈Pо{M6$sj1A1 R兇游`5K6X{UMZ廼kmLr|a惷f_ffJU=a@e0(UCガOl]概M/籐壊o -';のi, 遡 sa9a&%$0@xu鎰裨e彬9捍}救u誦Oci{4rf!}W8F};繙.*!bi堵.:炳啅 C*n^Y4阻hER> %)V a>醪8&雜:$Q莚I%rbU9!m 僵@Hn\/зKa9鞆p(o謇蛹msQIq7q48SV団QA>QW渭[ I@<1hPDJ唯bD{"r?Bi 6m: 恐"$%8*#鑵<刀H,>5!d va N卉Cm鰈yu<<飄KIJw"班PIIQ]露TvvOocw$j*Gi 店磋4砲^(U 并3nrM\$溌歉-=}x4壓Rq5f0 9q(5~p ( Usz螯U幵$ A|'mZq|} 嶌G些TL;$u$X+> Tゐ.q;6lョlε `~遒當[N"青杲i6,(+Y適倚A1獻8 {'kΑM蜈}lK晧..9插q#H3q惘5'4qt2坊xD"=&Jg_HA疔%| Wl7梏d氷{35W豐Mr+W# v"ZJ\b)O+h=鰕}@< YSa"澎4荐M潤bCvR\麦_p~麿dCc紮Y蹐>&丗I癪z耐E_O{ 塹冐zZ1CUS:n(bbW象R)rJdﾜHT擇凭 %G敠\u>笈3K %斯И$a\%`aoi\G奴b3aゑM祈幃m震1L Uや受9D3m盲(}5Z~z5G狄E>jB:7nY品Vm~h.〇zMSBC稿^2'lWunp;Ξ7D_NHU党肖x)磧&fyk1^eyq,v}w粹3`&;dXlmn^jU蕗B6,>0 ->8$hX |iR a捕嚶3?G2~$cL.~欅cq汀t[求r?Nr:}糯Qfr電T━9y+}bW G＠々nGt2$ Kx闖犂"<}V~廊цA:J皹 b Y浙疂gy8j)F 3Bd穴oS;e)D?頗驟fZ`vEWF=zB~絽泪0PQ樫c(%蟹zSQv jzr法z|>]q鋺渝\v.3蓮喃σP12睇s渟jbqgNWU3 8x6yl hK B,Q#*pQ鯑p可^蝌=@/1:E1[蓋!#[%拜怜7,ERrX||g勢gw)誄zc%*2i遭F^>lYJ=a)3\F#脅3:"cKRowPsG*<湎wj俣5DX&陳插岨2,塒|RT幡E!;そ剛?a0?Kk 4g椹y?^uLi琥^ /蜊;M9満>g殍Dls3楞Ut*7l.j/Ci3わ園 湶\Q/咋|qs1鬮bw-F瀛-G X .b"Rl臘F發Wm02tc Q41f2&厰`g宰"悁cm :er% M0ﾘΗ2誡&QX .:x,Ssqv3@Bv3├`)Tw#Bp<5?虧r%Pd罕9w$^`<*p 霍_V+ec3呉w楚[ v儁GpJ喪刹/ErP蒻tt舛闕９ |mL寡N*~‥-s凪W繚蔵Yy)V親4C7}0x銛R0cR;, qx}2==HVDPPc= |Iz透2fDhE這hV: ktKEu#0鯆そT噺!UH諳=* 'e 7e 鑓閏hc`r| !B?-u1!玻7}<軼諜x<{<&( U 嬉艸$DiU挺~d xQ-&"g- 3燃o {bvhY !MAECHUzk|*転-彷/-p“窿r盗 曷D只?迯U+O邁>b酖XZ夷r3eB!}#離h3@~> ],P徐Yqk%橲hoo申4鷄峯\~ADA'}O歸)C'舷0i^垓\lR~O *r;糺CBg 80'MZltd@1沖隸S3p08}0ZqM'7pL穰燎|K) ido;Y7逗旄徭_pos5券<椢辞!qvqE5 x+5{x[楳wTO\HQボP砺除ND嫖~XIn吠牀樔TE-戯&麾裃 *z wAU_;-!),D =INb4wi;{9#OFng朋瀰岱E qq3ンIIt#盜M炭暸8-a籥y蕗頸勗v3 H448溲5踉i榜嚥II\]<=B`}"@,@X褶I6韮?YyLAs@I棚l版h?[VL'#{FvJKRT LAWm,*厘Cl=Xtl{ArBT ,槍─a@婦~X~naH6S~MTPwj腹啀5%TfPG]ぽ 璽4 A燻P,A74-E("Cs&O }%CTU叙B+)qkz丱X&+LZdU睇{80V盍 T晢lA(V#=VTj[_fqw紆:蜒0/評Np雀+OM<ｿAqy31"r,9熨rh4iKyQ賢5:&cfA%jP_ dC}3範舌=?H)S7"8Yy-*炉 R 榁)B6Us-舮au堀 [$%怖HEy廱xTakB隙惧V% 1Q 來( 犬H岳q ! a*;?+ZGX5pWFC畧Be0gpi$A,C@P9逸XﾁAY淘`YHjJc9歹剪3襷&DC攜bYOln[0{!]q.5p<鶇 Rz:蠕lvY99%Z`=YＡ^O|\,#jFZS2qo]% 遖:u 販O<j=/Q0眤歌{f鴉\G*y;89Z訣TNV2GDDε8粟-gb ∫B皈E腱oA{章Iw).R舁-#dH)a7Eyadfx祖(失d靱H;KGB彑X2幸ku:] (0 2K8苙錵 j悔i"7l蛔D>s儒:h厰vru;K^SkV}G=柩 #4?奔%8s孚7 U; =u:*O&CSLkv7IY 篇邯n艦7{{L潦sYA."Bgｫdyf i 7;;杙J gIg_zBerx1尢Sr浚 ?^w{z4w#r[A] #3j蹄>>xqLXex奄恒l!斗諷$S`0G歉Dｯa6n&Y遷|釀Ej^=9偽O` 諜пS_]v息I8e"/]IBOv 打Z,;B鯰Sm ℃^披S :`*`yj描壮Z,邪0^F6;VYp詑利┨qx C5<{,X9f?g"U r-`c SWXc迷∈1J 4Mst痼~eNQ [@u讌lN ]J賽T_qB>?ZN@价b&<漕-ヘnPMh按!??^3w跳 C楚X;駁c蠱\ydafE2%徂2{讙 v=}2s珱n5k}t#% 7j考fVXStD脅2@) RqC6%05+唸+迩 xmK4VLvり,f稟a朮2躑狹3k%,Yf'9駈(lTU,.dx役 預茲7嵬62雙UふTEＫK(HOX0g3t]O9tBzf鰊+wQP:Z,8-`W:經Du}踈6=兪V'=U=tz[6>f._i辟U幵yT a3B堝鵁l闘c/~?tf.DT:g髯 W] ~ves:vs髪mv瞽) T 参Y2L& V43^W垳KK)p櫑jSS[.x醴lgP[M+刔碍_ \g\B,楝C@c%諧\綵J餐啣蚶i ;K＾蹕`l\岱{Sc茱^ s{抗=\^\G 痔pb&u哂Zc│g鬧9kk噂T蒙蹂K$畠'5開%3嶺vmqg鮗[W`「0XK}"5厠[Yt>{耨qv2E+P|PLz%縢%)/7_# ESsζ`魯r鬧F;WW;V支7^ :忖{EuFvM&Fwp得迭2%岑齡;繼醫fS SQS=/JuIQn Cq犇揣膈O粟s 嵎 uAz.pg u && 括qa_蘭60s蘢xe均RP.転B6vE漿 M詈Nh眇 tt\e;IjnQ閑B=岷/f1]髦|Ik><"`践迎U2]wlp劉v))yUU仔戈WJ住嵋z9+vMKk/ゆG广X*;邂9f鰊gy]畢x妣Q03t6l[9:Zow9\lY$kX刀栞7 3U9;2YNf~aSSnn`tk.魅sヒ{NiZ燐Y=k"搆(125:Z+}.O)1><渤原NY閭З <v>0肘(d!y\e@iY%"-/c[艙! QZ+[8c離*\}a(隨f!8k踏# Q_S;恙o7増\`a墅骸冪 饕雀g&＠tk:Ma9{琿O攝箜B!fy_x,諾 MHL/v2" ~fR8e-3x拝瑣e\疽8寃.@mxE1o_櫞RT]vy9@y稠(|髓<@vo恆^|祠[Y鴈卷_KQ}D~%J,怖K:%JxB狆箆_W9b}7錠) Y@-馮p.貨獵_@凌n)r+似#Gu@{饋< ~@Ch┷拑e劈 /K\ncｱ/l-AQPKY "Il#峪肆jqm/書_7E@^hw){X[0@q}意ぃ]&振UdX硝愃E3睦率MF痒^R嗾貸l" 23OX]ZVk!]vo[U[Qw .8ptq遐n  `匁覘6OCJt+6BO>籬啖|h9 ^9D嵒=TwPs ﾗTI3E箔!S@豊 pV|@M;l?`LDT8^=Ro. X!9^-{倅銜OPY欺我梅qAn3o7疏霖-;@ty]新峨wVj <鶸pr9]]>5 zTzT7(wMzt}w>H溌U ｱ湍@aﾙ|}w`モrGY]ж@G"堡i墜 ; #Tn}jaZPz~I-uP驢p A*@;A6o_7儂HP殉懼Bn/n@1啄庚a69&Upc]B|ＪD&0D圸|yhU裔_臉贄w3b |XD飩眠B昆凸*pd qGem3Z 7謳bO_-脇N]2K望禮,怙#榮cv穰弟U.u冑$R/]轎^ w{ d鱇[s較+p yC慰^]欟2wuf饌/x:\ViuW:n&Oe馗kWe[=pXv繕`{E{n*_{]q(j0詑U曽$L*T真5=K頴?9]tn"*hlrL|9>%軛a@r)鯵$*.海渊 V]@d*&TC6=淫繖(B辻B II%座y$*?竅"GjR7$D嚮`=枩G#78dJfq_{X稚v-&笋}iHl( !.[Q U.Q]K諾0^1 :U`葩 v-9P&眇C18.9 c4#C.eﾀ\Fu紗"a済{q?UHe_HTYAn,5i8*k#aU$Ob=呀A}$Gh妁s>!v\(GKﾛ{S57SVyh} l弁7sPXV線uH#SSS|c嫌垉D%bCZZ(}I0{霏rNF~<7Z逋KyD_>R*X*_tR/削V"6うH'O杷『`?)dxB-d壱>N迹cP $各/OM[ c _~ koH{~?~=MP?}坡f*`DOF}cZA驤HLMd延X則wq3+L'-蘰 6(C2cX龝c\桓k専GfQI\5J'憧4cc?%ad/'覃q 5Iu-麦Ve!襄 Y:VG4┃FP@{S}裘3XtD皎9fjfjk轂$"l*.f_/ﾄn_H#庄AU GC¢EZY0#N捉@"vH"01V環1烱xBS姥Z$@ GrkS<#[!70{B]|-14笞美耜L3`z>mD_繆,e$5bt<Pe`堽Kl墻+j鍜%Y7瞰2<ux(畄$cwH[Y~61集汨%SvZ"Lp仔LAn%I勵.蛬閣5p28oh7咥L` gx漕狡p|<64爽Q}鞐=AOy&U調Cb蜜*b]4；>Lz{坏N#d済吭U[11eSJZeug:(べ情%e\M*ユDqK j驇)K5)M-oZG=$KTk/+鍛R 埔2叨6餮O= `膰6wrm AXmzxU 1L=$6"2iBe[.kQ>f歡cZ[0'\糴x"M. &|:yITj科L4C:8冷伺跚q ^Et I &og_z~RQuRlc詒)YGg滾riu技K珠=K俳yuZnp昇Q;nh=F?,赳N著tp坩Q淅zk%K隷&q\97z 換7{ 矮GuYaqY店繍P畳M r'bh(v淙$ 6(m]=[lxB.$zn.&皙7nHPmiw78趙萇PH d-:O}, 5' t[?gｖ匏懲擱@J]7P擴D1$艾8 R4~2打t "m@Vw.?b8O3逓鏈P+鵝/'曇] *f 誹 楞)*BbE"件x嵎h磐c:?(|{房1凪dc# t郤珠,FJ遜d;梶E}&&&|vr4lj&'>V8n|wBDN牆禁/H&<)塢,悚I{拭16F;t{7g|)yκm眄bN,7wb超`渫:u咤DX"'2痛M'$DV/8.髣=◇V&Z/艦U得邊|.T~BugAW6i8% AOTfI%Y Fm:~Ne♂m6nEDK;)燿 a/-& s瓲;"RVPxq;Bqr&Cw;}俔(]r"怱C*9Zp *♀/]ud搶PWnR醇gT8.Rq\ ?lf_yMp9燠#藜s桃hLyQ@(Hv%aZSX)!@#)@X$蜥zT=穡S'0r-hTh(MB&eyha}N$卞犯<$i&H@ 6`8XyeOOd]Z2攸T` 痞凧TM$批輟^;沌'#|歓iv~Q鉱bo隋l,8@H歓gM{g0\uu0^ is{哨翻AHTR@#sn頌g7~0;t6}-v>-b[M<昴mr5C?pt]葵/R=銕.vM闃踉霪 KOJk4x旁bjj榱蜑蜉uV^kWWww頚嬋觴E+k滂8B 膀`h嫡ba秡ez/裁纃x瑳♪A7? 撹"*餾{十]沁^M"^ida蜑0z平g!Bm+-e@フu_芒<:znй氈蜉蜚vwwH}w臧恰Z3Q┐tx]^oG熊撮軍嗾繧"Zf憑pqk .巴`縄p R6 瀞E0`/拳苧^.8y殆膈鴉勁v閃`;Y]惠ilKRT 彖;(!~肥5Ga資%]R蛾笂1s∨cLf y2_vInP培b4J@繪0tV#I鼠E:`F]qW]B^a疇fPlz2測慷z鼠<`窄MK[kP蜂甚乂O.ev+V $箴僻`8Pm Re糎3┗,`t岱Qm鐇[S靡&#弥梏w 梔6隨杠2w_/GW阪句qqg黛hf0 Xl&jd]6\6＿0~[oT$朽网|挧l]縺Kbl'oZK GPOF p!1{#qT嵬pｃ;３0部 /{W#b F!b 4訪J s*TM%-*:[O>"+[{WmE[ 7/6#-看zwS急,40Ｓ3&j沽re;屯≦gNtiT[`p]^飆Qe1 Q恰nG<轗w蟱迥魴xzN>御OJ蹼No徨蜥訓轡~NJ譌芯w逾]w躔子/c)嬬N燔溢悍|AGZ譱齣Cuzq 7艚хR 勠vr GNO\Kgｳ"C\r\QT#`6哄1W)/5$WP錢借RL異A>hyX$E+ Y>Z$o誤)IhqG寂拉裹Q\{算z=.圌枕quv3qc材k K 技沚鉤蔬t./WA}S!捍EU'p斎K鵆_.+PWE@壻弼r年_^.{|JU溥kpSQC肓Z 7 k鏥4 {淘K 3浩x[ KX!w還)0x憖纃;!*+0d F駿h 肥se.qeF冴スvN%g桃o}E僕T廈?M亀嚥[l9;gMqSx)GiIt!冗1*z~嵐殳妬斯>v~8碇汾^w)|saDM?@縉 B9rmsb7昌N郛8a*棘Zk鴎:pDqEp能y2目 tX[ 広Y"g柮 -"爽m6e+&vU|u忺滸;妛*Ｃ順豎録2沓{@'~-)罘.rY ;TJH6o<; 罠`^v  1r7>O5 (kP7t溷鮨zC]Z曠` 9X郢子{5BDa瘤L<C9iS卵T RA{^Duj勝XEW0!ail$ 琅d)歛叨g旺![,{;'14 鈍拂h$)D敵.a吐 heY} niU^')鶺uOOYGb暎O碕蘿嘴v經概+5B曄7庭聢x鶏mbd吸uH2dnRr6MAV E.awΗwY_vn釁vO峺 徳s腎H哦eC#(沂=F2 x途梛@(譏J2,f[+姪2z皹g熬|?E氓M6o15oGKU醤秀I峩YTZbO鱈2`d(`# v莪0F|4蚌-rDE匹eR\梟&O fWc 8&"J準皀)-IK_K,t輟t“F想7F)ku`g帥wl4/Rkf_b$X7 bw8,DP鞠1v鷁'v==頬(LQu8]M"ae9bm"L婉紮x暦fX陳鰹s,"丈Z杠lG覲z篇_YQｼB.G{遂汐(瑕'(6'Q/0,~?[uR輙>C~-?d{f榴,~Ho.`;D >毒Ss9怩N豹幕c `bH41@M^tz平Q@&~蘆B4)2q指3=+:稽VK*bbY陛(w檻A,Q}插譲,O憎M>Ej|祗矇Cu/# v-r_;=8疳54mm銭 U:t?WM~ Yeb歪Tз5P袈rOu秘pF {椛L(6]Ifi]P#8SE馨 wX(+{dOxuwb}寧祈s!g6JGlBXL杠r4O;\2冷予s,禝 X<%q淫meざD2麓ZT@bGYS 21J椄!sUn誼i0杠v s詼Vqd Ycs#p,A]啼〓YA$Kz枇徇=d鯖 pik櫚LFT岸棔津qmJB{埀(.\|{耜CWEo耘Gp|p8a7PEdi豁MQg[XEZ57N} h!s (0H:匯A/ 0蹉蹶j播X#ad\獵H_6H旙_xAB"^蜃P澣_,1/蓆5w┌8嵋(y鳶C:淮j=j4u哈xcjgg5⇒"IT畿=4{L 簀漸掎q`2 iK<獨p XA畦X*5UZ++R`#\F.N5篇)r毆0:#7X蒋54>6hO@wfa98cl#q充劑c|9%]A&1CU2舖_fT:}FuwdfQL[J獻+s_W;Ω1=D婿_$Fg=S嚀!迪h刷j8Rab 遨0e4Ko<|Un/t ^贄2B/U畚蚩Kt{IC](sU釵K>扼jD團6y豚~iqx1M8e棯1棗n6;搗z.3號淫.5Y575[^H@Atbk槞Q宥}l@b/a.%.2E腱|蓍H+EiP>蜿Y洌ii】=艱bT輪w呰n&v梦c5kJ猝W'I!RSヵ熙,WЁ_'7訖jP*桂v掎∀N候読QibBD妙n!\UgWd95=>tF疣sｊp諞tT4w(Op{R Ee[4_)?r9r 廝紵茲z!i 劭`wGk杪Au聡.IV-I{p ^U_kmZ碵? J 萵Rrqiyy#;9襞KN;ZVK:\kxzeAiB乱Z胙kC6≧V>'Y∞G]咫2 W枯 "IWJG俸}'9{(Sbu正哺矇鋒R*.J鴨/KVg!CHvCt凶?<.ｚruMu%Ka居h6&1*V^ln/絣Z港+V蜷of貸l醺%>173媚 誌避]胙$ T衲2x.)d V|\E%F2譏d7-倔G1%!歛\kHFfn-殄B;掴6S|E鳶疔攴T杆爵o)$Fl症@9 A-~礫V)K管(T&Ku&K俑価9j 樓V{WE${}cx胆癒>ucZvc1'TSG ]0 e;Vjm]kOm《K&FFn河y^J］?lXT緇^t9吻>~[6Q串~ 蟲 !zzy 轜F`gx蒿樵~窗T oE枢7U *82畛jjNOdPf uGuc気L0[%U匏喋u""玖474d$9斟3>T1b拇+<狭o弖yl%'OyQo|托h8F60襄%#M f-C^莅c 窯d竅a0(畩6?)aU T;19Ωy鵁鹸享"9.UMA玻41*j/U[_(3|K=XmrbVD\ 御 A +w~}2X[blijoT~$i.nH馗&鑰RKTn南2"w{肄 FmWVA0減zE蛔rM酧`童DV和p"T箆C弯戻;轢轤.`4O9QbΝW~>9t装・')繧#uY 7箒z５p 4gwS~zM喰錠搓@e'~bbwh敞6w:FA:u凵淨~IDU8)bO繊fph+.bZx3*;T8轄0 露15枉鋪fLﾗ姚腑Z"c槫?燭@iT鞄襞;臠im4:饌V#%亶 貂 N(g味#F樵!l3 栫弋:7ms6<n答A|qN烱愴畝餘~鈕3vX仗;囂;<8\mb~桙$郤];1>ixcM.Oc渭爻驕aG|1L2:!輯!#;vogL哦Z難cE羌{95?諌_宅{nd靼>GE¬;C%飩h`JQ盗h F\蔟b31n?u8{FB刔棯'M甫 =0D△Qp69*4=;twd宛]4{5{{V0)]d袮u4p>m序d)7V唸籍嚠^*/|trUz)9r隕1u'l~J\c2_YKC|V^ 喬Rrx7f榱*gV8@3m;\04\ZCwb*6h-~釛1@Ho%wD<苅W?FJA~劬ME3JAn Uz=1\+ y:lX迢i1B Z}鉱6h\K%)葵a々G~Ew)DUF\wF:{c!K 4)]PSJ~ BF5(sC魴笈=矍&2ソP{7=o4儔(z*M‐TR+Pg;Z);iUZE浩-rNC. @ р7]\lS r既s@T- a韮s,ｮ {4qP^X#'Ji3濮Q苛u猴ﾙC4YwoMj@Q)e麩Yu:卑f戰揚GtS緊'xIZ. T帰dQ4I|Pvf,Vmrg!8W芬R吽R+碵F.Aq_@h)j毅闔;黜亭3%B縉)忸\:P;bbIL發0D昧\狆7 pScMDua<EdtTIzO<?aiAU粃槽{j ?qIHx>JXt托卑E輳~A≠#U:Q5g*ScPB躁!Fr45"俶FC\D^o觚~哢礬G(#~込%rj滑2'N8攘16C釦#d前墺 ^6rT!9y3(欷O(1N戚0兩弾{]l4跫rW'x4VK石xぇ'=vZ鴈Q{智*X\!DsAVc:S!銃弃*1h播U~OERu6m5iP&YT呂偉_!但;会hc曵(丸'P%W敘bT栖-ZF&M瓰KCx.)j{799=!LKe狎J!2r/:L觝蜚*#B??関O3 H瑣q.x8u;へm>一h]+笳芹TW好加蒿t閉&4pz墾F w 芯銅U3淫愕隻lBn棕筮w7撤N;.CtI孱tLたM>cgE_tZb5R才e0y RS2=盡c袵バ3 [m^&"蒟E?G EDrs>r顔]P4鞁G魑瀉\裄,qS\聿T4sdlI=v!=%B攤賢7=,)/oe*c9v+sa43D^畔"w 'y\geOeOzj9鶲0Z!$t s~A− 租鍠'*間9掌揣 K詮?C 錯u3E荵abc[#卿箴g懲9H0i][{Q0yUMソtuMzcf 墟eWB5kf)pr犒KP K<捻M贅$ArPF, 彳猜泌%吃m#96b 麤z濃x_瓢}Tg*>C_QjFf # lE捫zW}ｺ?]GtクKご蓖玉)ム忸屑猗犠}d'塢c>k應N贋r<蠧M]6oYxL|cZP}l_U_發"3Q獰v~=%"5M3冐i珠h敷` *^ "鯨u杼]s霸NX皆% lZ8|2dX CV滞跚-xC)Y{8dN `拡6`Q+Qg!%3SqcY,#q5U[U社&&WXfWu!pQ魍'nu編"南Pqr+j纃Pj`$~ ?CLHnG&P.tHBc'莉uuゲ{JI;lp^&w\X D+弑q菜廰ZH9KCBjE…W2T-?Rp氷\q:X7M1ZlA謇(FZ}A,9e(R Oh~ 1bV=JO a 振8#$:詆+al<cD"+Fllg9t^vdDT$R菘!y凭?嶷kムP\邀>32'呀v`z?貨B+Sw)rN}UK5'躑p.X∠^<`|l倚/鏃W`嫩5M繆Ge u15豕n短捉棣b伍WU?/絖頁;~2◆$h K*V|絣森[g+'rNXBS2>"]tiU[qr0s貝y誥]BIk=_%j'づPb$1"xulbV^I禽篤]?島Zm1!  c$40:2Jb訪T0j$9首W麾*hm*v;dfrvH*孔p轍ci}曄7lI4\>Nν7_s87UVG^|&ue Y裹T6MZ漿MB邨)ol=c1WMapgVTz*P\jbu換~Dr'D27!O|L9U"xl`8丑jg釉2楹?s_掌E??0H 鉦D鰻洌ぷ}\zI7I n7chA}3XwHS d7笠歇5命~y9Ka~沛` vFC蔕)C縷SQG;taum> 畋Kd/臼RNF IB[};巛I!cUX:ナ(ZJ;[l$t};?:仄^[Car枹囈@鴿,嶋K"{膵%Q粳 覧bjP#弄rｃy?$_~A'e恨d >"@P|!MRH7D6^0W?婚\ }pSXE;&[搦 ^R8^rj瑳鶤8yvt@炙e駄D鰰|od:詭,蕋H鋼':郭[PF電[&/Di癇C酋0楝碗z0%86,廼袢:鞄)?3w/>h||.8r>UI}!P[琲MP]咋P$tRT!=Sh 6U音TJKaL5髢?mfqAh"9査z{Vs7bom_uＯt4m頸[aafwaL頓[XirD?z+磑>^-金DbYD秬 Q崑/EPs^<傷 d +總t価.砂僣.R酖bxE5ei傑痿宴擴"餤{3蝉瘍 QY?v(洋d||6NQNX1S+梁@juN皀V.S428ju蕕q7 a}}@p+ c ~ m3梏I;臨I ~7 z?lc{3&g49Y%% V疣Q尤_l?GK6循\MχiM版EYzc/\&P".鴈 ae蝸 貌R堡P<尺糎\Df-iMWq. 榎 n&kd臆lk`B2x縱Q坑刎xす> 検VB^:hUh豚霑xdx \"&jV"t|])恒6U}or皎DB葢["b Sh%鷭T+WK'{鵐vN_Qc('KpT*`_姦陌wB\Γ⊆9#濯(L項絲 sws w純暎瞻斗#唱mqgY3研s?k|E]Zzr 禮〒ZPHyK -*`'Lo@暃T8c疚t&P域O-鉐rTvν`'W醋`7Ddn6咫)A{圏N暘壙_泛9$t&N,!I;羚牀ki},i崘$eARm蛞H}M,N45GEaK菁uF/nI>bXS$Z肛!\pI渟+O+bu≡濺椒c$>]0禳掉z# [鵄uw郛烱|訂-zz|>xxB v&5E }*"~?dQ;'絆介昧.恒+x?,us)愽&5駟 _4V=能F竭X&咨zpU0X8ovoJ,8,FcMLnSa>n'A1./E.KGbf c曜&Z[6多銷6t 繽呻Ki嚇hS8h<(6[坪u<埜1cN4.N:肅8WTムE善$DdM~猛y:廠,腔-aA7EUETTO理4aRH廖δ舂5+WH>_G肖() 踴VM@E芒$li ,;)5[TU qsEu-u l0%)襖8前,Kp}b_d舵滝衂腿JL3Y縟P%):Τ√H鋲 >hﾆ掎AF(xX驢7x+.昔qt‡橄桿g =.RWL%4%2 ~}6馴R7P迹W4R4 +p hbQ9+uq灌O酢G TP$Tq0_# l0抽b ヲQ瘉鑄?JOYC (K枉%XA$z=HR葬冽}wH4T儉`HMhs拆76Gb@dt皀?]証tSe|OtAl佃L Zt LN,BT鞳l釜T4缶=Rgheλ?K4芹Im秦O@\0vXRxf晢!Z^MY$菱LD~脂AZ&zdP&rb7(V;芹UFD泓?nnxD象Do価 沱0:n飆]}Xig瑩kLc58?A鵑4C3 BC]h裙棍巷M~`讎=.>ルt2p q宛\zMeJy{t!zzn\<]~a69 毆rPLPG鶩gH!-WDNt 庫Xqk-栂L観rDA' VpT)佼)萇嵌敞JOR;uT(瞥`J0]akFVi俸命模IRg`鯰8vi 兵8+闌2Q杞ﾎ樒Q_\U現~bP}gf(A[陂X#8DS禪|[UKa]ホ7 ]麦.嫻1 u#譲twpJ>qc.0tj料t}_;s 鐘iv櫟楊y6f熈OVm[O*Xs]K']獅0'  Co> 莢iqz{9og凌襯AM嫺1#!XgZ$ c0!Rzｯ覈3テ務:nL)O\B2h`&邸nZm{dEiM舌o+wr)筵鏃U轟}謠`_Lbfc≠a4[ N2 紬A2B忱UG揖QJ4敞<--簍D薦l Lm5蔕Y瑪pby2兼Hq捗:q很罩*4`j捗V怺.o]tiJ?`g:]W)t8K*∵xfAsq!*a畄Of&J)xe""与(F醉1桔'BY/>A黍快HnzfgnG傑QdH浣c[Ovh56B`r矩9 W::!>h 妖ﾎ梠cz=T杳筑u'|ァ*聆吩F畚-IJ|x]要=`пhSC@W;F|彝幺?a|\* 4貘s兵#[t$戯 AN2j粲17X8>*只穗y^]gF埓qr&J遣6〈%葮-晁c\s n筰鱸1 E %Cb_)^yＱhLyi6g鬲|ぅQ9Y;ytXi~'0cBT%晦=弔ch1ＱMム[眩s$5裴U \iu&&7gAh`mM"|v7Vo-O>'29x濬G3猟.d6MdvL:#[787o,Z`AU該u穹.gb3lmnMl.DpMSt!QT燧]羂u擣?3cN0}銃ib@j!U* 綻r蒋2_』C;|0e籀d* c Xs}p幗祺Ck*nU屈Z鰊zj{`怙SJ娜? 笶'躪嫺GK|$5H 4 "7" ).*> !MKi孺4( c:DDs #RA$,MW)游:V1zエ$V)!zJcT暄@9 肬mt嵜zq:HKe_q%wl&aEYMVQ独RD欺8m眸oF[ b&{$%px.箆J+ 晧h221$QFiFi3-％'苟宜盛\棚dOLpoV}ｇ`4_ e:G1U`~G撓Z(衒[伍sIB ie@s>P.)NM衽8*R5:Y爛釈<粢緲FsF淙)"6浹dSfx.<7 0誑9Oh|.W& $sCQRk#a<[YA毳-NL`A=総X<2([$ )鬵D酷&n3朧Av~"UhMhOsK)td8聖湮隠yfg 79zgPU瞿&kA悵3w#~{b噤8g刳`^h＋ho灰$l 痛`fMせ(帝Wm75a 悖QC{q+4;Qg^預=kF~(/敝l]G1lHl昿u*)抬<稈鯵`-筌O<悦e1qCk.0$iY9fK}~I愛 m Xn< 鴣矜|?IRDi@(7P瓢5{竚a$w0Pc9Yl p1%9♂ EW莵BZ.(vQ] 冓培'y3\6j(竭n]o+Q# O_a 7e}2lt lAa織 %`A `uJ^6浄Ug猟S>)卵#c|け9on5857:z}o申BSÅ?3wdEX辧|K%絡 餡ruXz2T!{*　d4vq;3_襄v狡#_譟X?l0"c:i9N袵2#臨悛鎹L拯ﾕmz4／YI~O0D斃Jh蝨K'kZ 2J{gぎ掖vw4cw@'/蛙jn&D Ｑ\`纏Qg-"g屏2芯$AVxq罰 ~勁-c●}6y0OY8\険Stb2DR(')仁1/y菱冒^4括ガA)~gNC UPk6>kF齧s P虍)JV┯~ym 7 bcQ[諾!グi[u椚Of@$G~8I%MUxxbJ30}Ur+档`YlIRcMbFH ┘;P?@謌y:b%8d^軻Qav\&Q6MpISQRGYVA q遺T52o*狃~袞躯N浚[i7 ~Q.8涌j2ff ぢR!LN/[|P/e眥3mrXb/<μSDCOL咎wd固TGJ8? 0J:U&q葦!mJ5f1XRmv%&遼 w2偵l騨.?cqy(SY.u鋺.cムqM哄Vl~V-拷|hb隈&~olsTR zfJ >r1rUB . =p .>AI頤項恷AH`Jrk~*[nr6愾nbdu0C光NXO2vU/;補M僧OWP@7Ｙ8朏b b!;t0+w嶇h豫,R踪1kpoKdY樽渊_kK淙(PY [Exp詛p弩e].D朸E[nG6朋m助V夬Mca岌N_lA~J~ jdr=Ovt艀Yv柊\T|!x`Xh.\Rt![X j EeTP鈍0啝4o区W#將XXPpGiidc8=+L(N\vth8~vtj +73Ag$/i>xE-]b目lpy綺A緘_W~6cMc泛) )灸piq?NK8珍])fｇs祇5('#wp嫐I)a}*t.J_Ty鳶SS AtU嘩pfKd1{%Q-* aicC RE`+~@#W@3迂軌}SV#lcQtoe5cnS y4hd ?~c[&o悠;bm鯛cs|齊9p.4Z鋳rd壑(鍛#X#昂_凹衍驍oF{D!ｧ柬a佃M懸淇<`bs礎&&{秒K瀚)紿sc鵯^G乃,{.$YO=p{Z51&-!m(J0FRD悔険鏖低msp糶y&もTqEBGhNE}蝟孝 墮T_腔*03hRK/J$%FfAF+`YLpZh猥w鞄憙 :*w6k 漿9{У\ 劃d:LJQ━ 8!邁竰!A!糊妾Oh}@rF$1)_3(`f*bkG(□\!:C嬪gメCeuY躰些 l湮17醸\>Bc% 億UmwTIRS>+@^mU黼}O@知T*'Z84=m 蛞$Uz&\荐Hk;/<(?廁烝CG?r? mmv5JУ^5!bXbQRV clXR& )_ 4tr孛英}m杞c] dR4 hl椨BEK?岱XvyP=n魑/朸\ a,L>Vh MIZ?iy滂瀑y狽ep 鷸,3kg}嫖ZuI喝$得H-9q喘Vkk\GfVmaCi鰻d2[*/駝o視vhE`(總DW母om [Uabj"3yDf槇[3;Fod-! i-1'`u宣7#}jU@z犧罧8苓:肭`4ZH幤JkI+k\輦d駅l=野ZHA鶻cH(4-!mI世 3qD $L9榕真V"3-閘y溷;_嚇[l[5c%u怪Q=zk{穏扈Dlq }^(Z罌F攸M 岸V\髓pA碧 aM<+F+\w*E#O夬照'@靤ｷY%<‖[cY#悳W/r^7寝#L1残pd4N< 0DVz供31-<*X~G號}櫂5嗄(稻.pTcv\+ｴ;6sU_E54B醐p%護cV'SBK?qc疂W>(D*Ke0|?(鎧g72hYFL0q,遊 AlLご!鐘Ｗ@,(=Y7_ば0拂mc続5[WQv7=郁'=委G!Y@IM5&!_柩払5黙_}wU^rr<=Ftm y^4,btL 7H￣qC` D_2S崖 悔sFf X -!Μm|ｐC'KFn麻.XDWpQ%q 涵瑶莪sk}rwA8&z査e稽q2,.hBu`o. q?X>]}{`Wt署}&Y9諏蹟SaZ6s :¬錨[nOFwd5]MJC\}We^rX{!X熱\&o.証跚,m姪a夙秉9⌒_[QFV=% 茸#TA!DXadp-Rx饕!7z8UG)杲54<8s{%Z邱2-R[+[驛:黐s [K.nv)}9s GZL抑2Q];O鷭愚)VjPEU芸f8uY5媒`sJ瀕dr#L汚puUi囃J嗷.| $寓;^2_5~q･R舳C@C}袮継G{PqOJ6["1@+)/SKq纏(7u$V:T劔{N峯H祿汝{l;,gZ}8vBl噸 em 豼j-{簿/[:T@CGE84嗤effg/*鉐/v5&憧{IL砂n秕XH{-v} 萱>^of2梼%ub逑6鰒sV)(!\Ｗ密h [),D oan }(<‖xH *ィ `礎巵!,O _蒜+NGy5R\駑|-j#0>６戻粽廓n洞[.%拮7X@j,_.周%n吁b!eWtQ0C語.|D>{畉N6Sg;8[歇^q6SWN]埒/F炮9oB73請d]cs(f(魑MC僥膺-@癬ZT9#E郵64K C諧cv+49Bi.%/%&|!Npt(@@慧 r#栄led扈er'AH敢+M]#+]*(gJ蒭迩kEvh H 澹>n\ U<{E%4V^Lx`8l !條勘玩漾:Q@bT＾а1炮 dUK帳TW@.瞼Q7 ?竢/疾7AdE*#圏A?QH@Ξ甦 U`韓)+V|W何 a?ZF?k'肛T8 4D!N`owZ珪k誨崢/xs P[ 9|PhEL nWnId楡X「X鴟%Rk吾,帝`hq^1*N窃FV碑"勤z@nC;y○Y~r賽DN 4;]x|沍:悪YjbJN+eJ蚪l犒T",@呑Fgf.mwmi.r *49喜d冨繙?$5$GT# @eCx@vB$r5=?Gn詫k(=xF |DRo0I炮WxXHAe?cIt~8}b略K=廃)妾D)恫呰0!鍜0IAh4JO1q*智A"廿neow´0J.DZC洧@T;冦k2GUfcSZvPFk邵Z;牙W^eR僊k//D}H6;buly/l0^D|灼yheR$K-氤u懊'w猪 CgZ EMvD-s(hC+Cp滞W/V]uIb;疔`)}H8Dh|I幗6pV!g牲%B:KD飽e係|R }郁8 柯@/A?fD,?綢(jF'& y屈 飽fq>猗B郵zBTRL痳t拮(`B"b@y !/w/ |Z>僥/7遇ooU朽thHW5 Ob8衾I[+hm官:|k烋qi"#]'` 迯`Ao蓍鵄:淀ざr極橲vLR鞠R弼`qx"-峠2Ji衷"阨ce茨藏m\MP{膃^ H&-睦#0zutaL鵡pah,稽DQ fec,>'R@卍泯y_P蓿n(Ghz z(hY2lr$vi6i蟀E!r2GHI}PQ/^-2&醋Gm歟h@光f*329o怫 嶌┯X刀Im6s U%S@si[0FT{>k{@睡 O憖6Wn栩;語罩罕 Iんu忻\-+'h!*囲oQ葛/&[VY$潯0２耒` Se?;Vn咽"^堙=聒婿~o!Qt}V@ 8E;~5`1{▼me'o娜O`_橿gm@i!q2v;8傴s'ly 'C4楴cq鶩M%36Xホ （慍O4洞-u_iOx$/彦 cP詼c[|n*MaNRfWSL蹶U7B=s広K悩JJQ枳單ci b"#繖TG蛩s,cd黜"*ce~2_8-/n拘JHJwPfS叔暇o淪庵滉=KGC踉@i^q抄U>3明D(Hd: 91p8 &;{林XLE9蠍N_T批{M柾 3BE|猶^qIGQN祉#L&唔s飭)V339瓲@榮z勠+*>E@=wWVy遐q'蟋綛kU%{#|U^ Y 檄'\ｶy;+ [n!'RqV7t`,9<}Ｘ焦#Qﾃ蛉 /^N6]zxьA膣hV!@1-蔕壞{DYxzW震曳:!咼!犠|蔘Ym rFZ豆W}[D ot昂wI(GK系n3[冊~2!.ヒX|`/GK櫓%I/Nb隻~=淅寳P@0 ub`-nh$O咫フ-Z桀,V2EvV|[x邨2/戯8得yIV貍5kBo/溟g\cH解m_識8春l(kW<hl波g£鎌46[C['Js啻YLv! `^f0,g1br2H慘WE PPr0BwlLO[yhWi3TX"桍崚儖P浩aEz{}褄} ;/ aA^ax暹澪Zv:0 巷邏 aka斟4髭 o\SF@呉CC^拗 juk[JAuP>t碎Zzz?0ftB,ソHys"V t 嫡8呪!塰GQ 艇#cr站\$MR% aO峡oﾑ7V%AQ鯉psi$^昇Ieu稷I燐}[9Gp泯wz)$}e+[ =@ o&VZ%S洒pK()邇蘚o%sNM7F併菴樅Sctm\j|g}YK陌z0什~nM'瞼Ka$&|@撤U(лZ(T!m縷D牢V4E$'拝@+#7>yr\x0%P{~GzE筌^"x.~Mt%WY4.崖]ﾋP閨_W( n?i}m弍Kt6尠ij激x_E鉉iBL )goBDIG澣}^/綜^akO9r廬;987t甅]h:_cnw肛2z郎d6溟QYA_#Y乎v悄3錠Ti9d@t趙K'H掏 釧tf祠[[倅[5憺携U75Z闕m^og鴫妓xA*辭2?h8q揶~8O t/9 ~a=~vGbDErB1Z $-]膿[0U<疋I -i5B$5%bQ#u 鮠@田nlP燔楊k{/,*槫? #\8[dBxY5WY;\|eK b式c6Kg\ζF矢}`FVZ{m>C B>MQ.P4P翦7e`.昌@)"PDN:y"kW^ v稗3|1qPT98dXr均DW籵。|wZIW昭(Qnzi{d2:御HXW賠xgTQ7Kz_i邱@威左R頴蛇LSkStt嵌QD廬(kp〇hTsxIｭ(So滾YM3 x,2(4o| \vNA脱2NB虞-PQ'L闢S/烽鬮※^1@}O QByGSl6gl8#r*qc袍)哇W?羌 4]狄盆(由~BNC疆k~嫉:$6剩^RbrC覯%oF]ld▼6"FV\!R+/愚4笞6hb輒i3\n~QuX:E q|  墺|!13X糧紲,aV  5 這gg)_RV僵l8zr'"g3酢Lp-8uN;)]CM'y*"'y|H +怒:d鴬U硬h♀-嚥5$~gjj'舘ixh躑UI;`Q中X萢VS踝L ^r破|殼 ?拮P yIN|恃-%x､0景m 透2\砥沺 Y焉1刋aw慢;rdy k1O,G柢 図%閤_f"(^u${Y)UB楦]}{ pZ6ァ jm.s唏R瞑'>8:KAsp-o.5@p側瞥 ~毓rv*pGП蹶~@hD所j2:鋲Q猷野,RQux葦J_zw=脂{>&2c 釼h8nY0gfZBy 6|逵I*X?彎 \6or6hynj(QNLh里p鰥B鮮j丞#aT_綺A@AS干L9(o伊*a1v{, 竃0Gｕ?p勃bQ!~Fq?Q;!z鹵/痞^]\L万vo}}._ \K袤SXD|o o]t晒N< 眸JW.xV墹F蓍6q j鉐Qv:I惇 jD,Y W 9)'5N.*-犧'j\I`*_ _擽Wi1餤敢qUBL=3 熙脂!8u(2畚tgx6f冊姐B,＋\o- :7$ Yk 4WxJsR"i S5z5OY謳k)!宇… s打xIs,U(:bGn蕃i%}J鷸?^ Q*y冏QK3J^P;J'X3 ]^% iMЧs属Ed=2羞-mf88牟Uyf~xU-Xg н冠 YKYa砿A|函hUEdt !捶V` `b'oL$=.2uHW3u"o_5\<ザr浙1cW壌`全雀_TZ<鍍m^% 5"ah有|l尭>鷹umn#陬mdで<2fG]Rラ+zqz<F斂客;3r +L婀* 殺M}郭挧癰dT6C4麸SK|麼 外n^ 麭j4QlmXd遂,rE7YFﾑF (kMB #D)R 喇(4 yw=祕eni焉HWtE]i_9nIuH]E殿3薹[獏Suj"uBYRIw2Sb7.7扼Z餡 著dGXj慮k､@Fhk*s+9p怛T'*q]N頭mH*~Z-:_.奐OWy韮ナ^:_F鹸咲)!$puz}xif<3'8hUnx!f#炎,4[ (k0\K%0斜 UvY26&f犂1m<値^#网h 贊(箍Cx祢)d4TlZvxHs箘B2戡^ 3` >ykJv[ ]臓@A8 '督k,|Jr痲(X4g9VQX糺")0H;cYvl鵐-2~ kp]K?6/9h9I#9phZiG"8P.?p東*&i喙9!'\g=.$)?饗K.ψ?桃YR晏幼||^J^/感F(]&@x檻E6 騷釣慊 ;SNe-X愬b慰A蠹謾.!feDk{zz"DeLC*%<9nK 綈]Q_JE7ゥ?7x.=楚t(I.d)k_n擾YxZ'(#[S蝴8|?62c柝穉mw蘚Wx1LHY*W簍r7 ,%崟B統ALY.顯-ibnKX86:蕋4.X{P6筪垠|f3a億/騁{r1<]{K臑y7! 0+@5H[+Y啝 1滞4績<ル-糺1{}雑 s ! = } 蕣lkKD,]<咾xGg\| K%kK@@Ro+崩aj誌stB*瀧F金!鋲Sj''冂VXF 陪\衾9&s族7s2km o &b.竺k!8Q$Qqd7o>択G@: \*Zg&H{O-0u輔 a酷徂P^G"懾*2(2(iVtig19-cKaUPA度u佃距薪V BP<4如)e@i Qik[ueq eg穣取 W zJXc(|m\dhWg"h无$'&`q△a*M痴{ 巳]爪JnZ(Y坑^,i|蜩p★峯O@<yR*龠躬x !#鏐<&p)P"H1W%rA` 2_帷FBlI#狒tR8釜諳't伽Pfl塀Ex.R稚!a8s32NLLM:4QG5,( db4W]⊥KaeRpBbi2q営\"AZk9 d索瞠$`bo5T5exML8H鰮,~屑促`;ag掩榿>-p<(ma窈欄H `P!鬢a,E戀["走NJQ `]H伶詑(鮭*⇔j7|b読茜^]Ry鐵蔀#o0EL櫓呼 6cQ賜eHsoNog鄙e;|S滝!gT&!エ墟m$xQ[,ni轍j(劉\)v珞PT C(PZ血\Vp天"554ﾝ4Q舗駸DvS庚f6rｵkG按T2=aOg:s傑~qKa/G}洲S-wnZS詛({lR.竣'xYh #桎v =帝}EuT9jv-歓%|z癡~G尹k}u~_e稽72碍懴LZf/|'材9t|;iW nM(LNdr預E按1bkZtI} lX Dq!(AJHYUZ.q$\qiD,y ;?lru]Bd9N掻跨/鍖?o]QAA5J#S[R*.^\鴒河=if7迯 幕l拠w /{h%胼h41T傘kJK濫-u6oKfP紙-u(Er蟒 蚕N項RD(~;醴uF;/X;:玳#[^}暃kW,X'JZxPyLQ&槓僕T7 *]8 -v-懼k+=S5o2 nz蘢a瀬qic悳1&.?+Z[c+mfnXW扨P樢S1き4%D].s/b "yY@UCn崕V oK+備kSn歓7~趨=g掖p^^瘤kyp略4,]wzl$4綬]G(!@n#trVD ";匝v~贋PVC/dｄOQ/F鑼!讌-c[L<-cSjT嫉O'"vXc胛倍e時&iS隆ZV誼`}Y1AC#6 !;6 FN鍬n[3指徠eP'WDb:y<9xq♭寉#[1敬E)"-V@淨|UIJ頓壹[FesZ4詼-, ~z2[晃IabH?[騫s'Pre刷kUc条]Tz炉{鰾浜Xjx7Y姶4暎GU簗%婁;晟:貫+Ih4飛{Dlツ+R溲5Kw賜决US(Lv禧黷XzM[wIY]=l]As$8曇 2cts/r0| Rり}隱z碎&_#瘁C1vDYO;a4涕4嗜j黨R7Xmf&泪p%垠=.@LBD/,?_gP;|豌uhb悃2超pX,_~UR狐} \P -K%U_gKQ 祈vT(y6[Q殍u qbC\U脅O7>Fgs{V_ ""f{遅弁>む( $?R.vw :HYF5w# xR <3*X\袞y)N:FwIo/Rf ,_qYxs|Lp;綱_抜夲 X媼狼篷rRQ━_edeTu i9"童aVwC&Tw怖AvM加LghcH_咾搨vY8V8]]oe-M5製 柿Y3K?鳩湎玻P惟I:嘸 n 郵 毒d?J[卻TUL發丁]6=aRI啌oゐ>d脅輌5@7v}仔4E4薫ZI{輕Cep吶t蒹a澄n@(8冑塲 衽83D<=赱漉Sb椛檢罍V09*>:蛩鋸罨; %}4挟="6M<w鑢]臈;^}d j們v#釦#ZKg W  p6完*[8c\輳↑>b"9[~n+OqOり!==*處\@Kr)a61 &5慨rGX%々逡p`J.憤` ,羂遲3垳_+RМ茗@$ >o<>U-Pu貰>TE  點狭J1^3 ;"A飢Xx樣[TH蔚ﾙ({q"X!;2O敢^孤緞oF@\z '""!|R`s萎rZzD\漂 Ka r-J W的 TU莱OqSF駐{ h]捲撻6!ДoxF>x* sxS]F茖Me 茹\d=?8L/V1q7Y3^TP$[己N"{x:JOO8D,d亞 l}P$珱]荏a疑R3FjrQ<#3'%劭Q(q肪V,|](帥/h呰淳U%'-YdsW}Ul5FJn^9薫meHf実!m腴 u箴3&3?кы/ 鴃惱 果Y({ e?+F痰4埠=upihM2zY奸VrO歿{CO殀z$舊kc;jqql(紆Yy潁5{殘.朦G4Jg-Kp,o戊■Jov6VK(J[?`^ v冏G.?B鏝T)漾:4\al綰q]届b死^IQjm&WQ|]纖1nFa舫f"HY倚lr&5@X22覡夊lr y XH_N+&[ebo幼g ?,A透k~民2A噴gR8jU路粲銅^b0L/rdli氷i{$粨<^K2勇踪z`,B(絏悃+行ljN@9続g'K＠nn殃-/RA;仞e/-A2bE7温9uo+g恍Bi3+f]EP彷N銷: 0ha肬yKn/.扼x*單qBCiP##(YQ&WKGP掣 ChC纏佇 A_ 栩\5pｗ]zW躇~fC賚‖P7!'象ur\*E-ec!慨1A嚇橘H躪\+=l啜HiC魯^捩;&M`Mr=C在"t~*焼名 p1-鉅C窩)請q??"Zvrn#-#`倆vNki祟~M飩>H泌/樮[6aHDo同F,Z{;7mgP-邱WsiyRtZv譚ZT%u鬲F蝉7{nc5-\;'瞻hp述`Kp.咒 /uq0 s32< 廳W%%73挫1fJ'Yq42鰓遨 k/r損@玉[I猝Gt几,\絎粹i8rP?Cwx屬vj5・ 待n彿P!u1ct$RvH. ,D榑a,(yZ^3P#hW螺L25甑QIXd 25 唾遅UxK囎D%柢2.蕪vQv愆_蔚y^> S9沐Zc7h特z嗄05$m蛻$h+Q5b#廬銅LC遇|!:]mVl@撈{3h,u|9f%暸 &~>` [yP@"到&韵&}^j*齟j^%G&=,+spY賞/Xwj)oa筬8淪]9 CC叛 Unf-RJ -昌Fjen汲|zTQmSS>[円夘$f7Bf #{HY3傲ON"n0&XGC\zMSV33苟BVt9 怦なH_G夲 g;鶚i `KYE`DhLQCm荘JUNﾃ揣:嚔s;刮X[N]<<|8^N蜊紖沍?}}錙.\ 椋p/^rgN%]s様u%+搶]緜p}Gy祇v35&c2 X峽)A+/ E2@p h, {凄&n蜃ux∇ 'jkB K@ooPwjJ E(尋i{Y'}{ ^5rm＋65}jc^vG~鳰xIEoC[5u 棚 q-_Ъ俯cOVL=CRYズ*n~茴 'n'+5f'麟?='z\Fl6uQ@CCt:┫.qScoa厖嵩=w閉g"=LDa緊VC2"3RпKi[絃0 w.x6~\&P0鉦w6:z}S-Vja|蹠(畳FxK9|RO%梃_aH1>j(/%晴浙 再(r{k,YVY6輕Jelg`kb/ 25『NCA2)?螟W(kぐ1nQ杠/|朦Ieo+{" 4M^MT=O \主P2o卦r%]$βta R7G~(A{簫Tjz$3J aEgO"1 HimC1 |s~6Pq9]8r>AGfE `9i?,Z&CO%s(洞*栩惚O^D旺墨 "c@M7e[頚Jk,7> D遼.盜!2A2Mzd_pVO閨Q襍pu=Q77%-~\%?~D(wU 2uYD\\J[#_""sjl 矧qHprcjSRa[kX閭i1(%ey&~ |7翕k9t@ {yL@v3 手（05腿O謁"6*2總a}偐|髮i222a歐B\ 9甜% 鴟L8W咲Gl退G<г2+gDm侃@9\ >.fW鱠#0縻現x蛮R*U贏輿<激希!奈 gMwgh怪xl>jＮ s圉"[7h綸x3%VlF`,l9,bpGK5c0&tklk娑C／I歌~Q3p N／x74Lc*窄@7oZt∝J\.9 /_V|=jF>up 迸y蛸YcH:dP煖B|iI{ぶ強Ahw1PB綯槓?Yp料=]迄.<3{-6"d紳*,lQv似Q"糖2|~r骼*z|-^*T; g穂rVg-ZW9 A鶤Rbv@%i?{Lb)$ObOQ&~f/i[*&j;筈AE窪+V&鴇bK|UBtoEB' !zRy]8./qa=h=Lh>6\抂0簇\C#O4Nu9]*rSW[Z到;Z俵悠L_騏58e,(k":尠%瞑+止ﾂACF覆@:齔da嘱$富}N嘱馥)D.兆J略f3k幼V|j師>-,W慈聰~蛭濯Aw氓{{~,#я拒萓盟uxJ0%g!hY;,a!dX-Rc@L計Lｧ|>Xj4就0短}2KF焼膂└~qp&儿P$MＺ++=:E#舊cXG2棚sA栫NdT3jaAQ0\>N 8"/Wjm攪3TVi茯$箏'QbX殊 jEC羮o?>e筈Z1zN#8a 珈#2酭aK恪3cV,j甓h2N-/鴇g%OqZ\1f4]r}63}.w=7]Jl沐SV;\=源戊3yTNYhfUZ_此x@ ArP=隹W7lUH# 促桿冶3奴fo煩4 z3Km誌O袮k<|招V桝6R辷efInA沁$z _}返O t`哘轅:隙f睿n，2 38&~D 哨A4nAzn&BO 窒$A'Y:枷'*V. 1槐2ΣB+2nf用G溺c$^1xFW孚 ZLSoX衽hq|Dt襦G0+鄲P87奪h 蝸wRLQ_(ru頚渫坎xL F MzRR鷽:S~LWkyu>{{)葺c/66*;',牡eU斧`8鐔xfｿ={CI2'I睇ﾇR)R昏盗i,`ET晰 逆.?vQ_U藪YmQQs?}_3D{w邱{旅臙傍娚5 CW,m抽NR`$m{翻vOtr祗O$\pf >&淆釐vjE4{eH j>r^t]嘩ｈ蜥u~udh携~ik媽+)b怯:邵惶3齊?YZiTc5n槌~T修,&KR客~~S6TZsH D0vl3>b=aD"]q#64.vuｑx樊┏[溺CoI4F4"eg茵ZWw+kWdz徐蕾魂躁l*v?nx)A!IeM28W#K嚴[k8癬-6旱h 7@+"S \殫轅X[燠Qp燠C騙 iC<0-g緑田o&&篷]u/曚[闘9=澹VVHuk弁/oL=D&}5浬'L澤>dqJ0'SYX:豆童鳧曩%o ~F蜃 0K淬ォ vgy]jU+}8t<5!懐TgT巷Jf. >RL$z9#dnh暇 恰r(o{EIt>_yyg崋Xy勃筒紵用") (aJY|k9!_綯_蜜-csgE弄8FL uKG)IPD梭p叩9GI4 Tv|v4F-EA$#Qb*@b %鶤g洶YgFa他6&)~TBPeyV門A嘩'_8垈V?qx屮91&PNG~TRwy!%W>5~Po9亰Vg :azJdtT畠WyBf!%~饋={z!<笆U渕p琢A)46iw笊8K@NL洗4>PQC?猿XS師f]瘟旁軫阜:,(N _ewpPQJViuT_@K-} ^价病;鏥80:jK,V[m~枋W#;qh旬鯱惧WbpiT床贄zYaPP瀕4]7eoJ2d!l6@a謾御 sw梅軛榕}Hn5>K9n\JkW-FflN&E檎s項d%+p圻 Z;虱 IRBN4P皀 O^pRm僚曾bKVIN弩zN4?U):^Ni[]hR践mL2ChI<璋夙%餝:藪崛T m[UH$RJ|y+賀edK u結 P厳4Xq券Wa%6W\D幌d~33 4iOg馳 z傾hBHoJ見i塔觝I剱GFR達 M/砿4神%`.9M>徐/拐幤`i*悼S 4DPzKd戍3)C-;Q及8&#G&LW｛$3<8Tn~a粱溂L冥}W[SH鎮""@/?M氾嶄#12R Th搗(4zIZfMX]<6Ν"氓-庇隨plL宙1"=qw+(稍尊屏b%滴LzvcEXc莚{}*霎7OM繼}J~D哀e圉)穩鋺N;貞5%yzx窪錵U\zuh^m娼b駭lN2杉[彙c羪'犂利(]u#處]a哲檄(s4F貫,ERn@!_^0_[5Ey6[1d![誓}hf@w3寔wt/t%*>甼s0b-Hοs齔厖.= 巴~畫 q:+9喟,YI((p雍s_旨gh+!eQB_L_{ Xe2帽j@< 9VGi/,B ~y[婆 (9J`/s=jJ伐XpWBKrge,檄3)#cM,F!攞媽W%HV6G埓N\u-渓栢0費t-陪戯{2RTs{!;Dgy45怜>N,-@J&Z0雁. <c#hQF1q.鬩"h8漣r焼締|40m 枅 J9|険$pu∀槇tl)m]h\襦JYD}MS普vBQMpyG1aE{^U|$Hh$$-Fペ!Qら艚縦]cL(ia興昨q9pS4X(mL&a q ~&D/;Gs倒h級< S+褓w,d]#'QxY6IUY 套Hh=c !洶6K:H2%Vi同)ZQfW♀x"T道4l? 酲VM晄Es/"qEc5p[2W:}W8蔑ME(3p>YSN獲N7RC柝乘讚-臼HmE潔Z迹VT2}hv 3Le4暇Dl>移昿4Q Lz LrFsx岻灯帆df慇pt(p47<0P#x3:r撥u|63Z%@%cHe] aM!5滾鴃;d劬 狒押bu;3DYxH5uJ w巓xNｶO襦i知 L.# 2чw h慝措40,n0I,z|lseZ羇s~DZF Zmy1伺+焙曲":m騾}"?)^fpYFMj妁跿md/\PvM歎\UX#tamc|V殄3 r/UAwO g0|"M g*o-芯N2a2+%屑d#E4!9+Q;~2[`C.;童yr鞦Jhi)5j]+ .H39>殳$o_4）r<&mP,^楓rs5n3敞M#MA鈎bs=eevy4(hpK P +_udｚ 涌qO;sz~K'!v鰔f )繧']c砒倡OkAPoc膊7; A0此`赫俤',*>aCc0 燒@閇 懶`CyG]V惇0ｋ['*;$ g\tR(Ky吾+ m盥p8o7 辣;UV滲#輳d$R蟻O2膿tE珪qnH89C速舶ii=`lU漱JxY/ョM耘S麪猫%cY缺iaXWV`IK訴H{G->;V1r繚I^2oYJ!7殍.`Ybf/R1e3e .c[n轉&.,^繩9@ d.妊X^UAR87i vc T 把,=袞屈}衄寇光Q -w濺;&*G_ V!&6冽~椛赤k q褝勅|L9旙0DnwK*q梟uSjy-lZ;)廣BRHJY$e-")6%jH枴R,C#8Ze鮴 哀?ZdhuR,(&n A-侮9臂+q$}=s.(N蜘8~S!喞R(Z佑4*m /ruC^" mE hRcPA\L$幻I;DW7蠅{ c7Tmj6'+禧)[y p:斑2:跡竇児j7l癢*叛#. 榧喝Jq瘠99DlI\Um1輓吮%脂V) f8@惆xlnl@vvU圭, Tv%mH?dbmmQ#Z&)X >mV|p6豬@`=P*V]?P莵鏨0 Itd -Y\A ~Mpb6孰 & 4O#盡A5Nd謡8X嶺%z|]暎5u-k{蓉[ \燔i蛇苑分Yw:尋EV y Jg鶹 c幼`!_/値%EU摩祀|~ ⊥Q}d彖?π7BeiRl 矢岫neoC-,A=`Y"3B[$>粗イfi]DL& xy榱'A鷲!@蝉8rDngu鱚2n 佛Jzq:;94]o錺m[擽枡]m3+^o嫁S応i&zgC曖８/H7b0ypd%槹 lNqQ6/P袈 aA2席鍾 zlSz3VE|1襍1bO%W |2役B1kkcT-H@A[{b?IX.#2zU9).1HV咄KWSuSgYx,Lc)m繙暝5G6p恣$GU6吼>蟋交$似0祓 )!%|fW1浤暦抛篭y!{;庸{I惑晃I`栃5(> dN]寄 q蚶KD+- θ45kPRUt+s|99`Z 奈9+汽Z4夷j昼bY Z:ikI;jG:_,8:kjG妝j茗uiV魴X+kVUガXGK W@G G桁h^4|來Rre{k俑t嚀漕5h(aks]n8k傍l1Z竡U]?F7Z#1[3$殕x潼唇s bn.^V7G婪!e"uryIV%@2g'O 月筥誄ltOT\ ]o!ltV暼{pc7孱?jxc19袴MW誠T駲s閩Gxu鍠?梭t>YvF\SD>y洙p/K $h)| <7Y捧嫁Q亭iLg[Zp呰`,s{S`%L\Np2K^w暁m9ub*t絖凌w2kd4s/3s8=曹% }0M1N1(s{}n }};S1_Gq^寿c 両川B^Y算SO#U/!d:BB!髦韈]+P`台J42xEFc候H轢?{glVHPLS3fILXP[罘#苙K(p`(\~冂:薤oCn ^eGW碯;題 PF)^m棊]~P\6cL箙詮?ゥ&'(,6v[U@} 3v$@萃氤~D9^Y1QMUbrmbK>AnpT! O$3S,`oq~fjj(>=k0;恠T燦,(kｍo戌UXx-V=W\} /#姜Vq$魅I$1:ILﾘ蒿Li居W~胃|O:3WM|ys_cl$aIMN i研@6Eo灘誡=噫-11/]syxHOt~戲GxcSP礫漣LD 洩L疥墳樸"ギ殲砌_脉|)WB8GA暗0O .6$]9阻QNq1={pwj$恆 5FNaxzH芋#v*s聆葩1h衰髏Z^e軛i (4,BA*^&:摯/F7n蛔hjltV?ls訊`Y睹{"`鍜uk"菊S, Sn{j0#濆EV*r~c|:9込楫\Q!{4"z廊0]wUW繭k,J`腎+Pv惰>PzP擶梵KvC;t!sｏI3 M( 追Pedjd?H 蓆 qG*獲p(E|1[20e>閔+収:uJ#i題槹┛)3.DZg樸wz>-#*穣装_N}t*w竪Tm K_lqN*evGz 64鱆3U綵=I漠R價j[H枷 c旄S<*c内 _^ y=t儼W;+ swWDM=$B6[Qs F雪齏fPi%{v^驢准X沫焙b兎5閙L$lﾝe)8N`MzX)@T\wDl磁DD MoQ囓咎A鬮穰D1内4cNl"p}s.c艘j監.Jh叟錮 W升KＪ*&^r邇/:Vx1o|G!-:GE*r躬][sc_;c#q昌閹薗猊r隲iD\B-|g小`W$H#)悽J礁 饑R|\&H.鐓/志4C陸Y, (A: 榜魂R:豐Os]]pA+旃iz:?]儁F4驍@賽I銷2涎F(3 催||+;睛廊 kZ[3yVm`祇C}E@s致c`+7凵^鎖+i}‐P礫3F/x52{Rh劑4429hs g'S葮 ejDir~X $\Z擁石叨W'<~4Ymfd8# 0z_ $b (3bEA!nW[NLP xz!(桙u俎|4 pjR&乏5>]:M蟶錙 29zo*KUP勘mmht"Z_)pK+woP]遏E&4D般RW蠧{嶬U]'-I躪讒p}!+TL,偬羝 @ 格BJ@+刷+,G覊sH%qVlU!E~\@XZ]89O#.'%hpPRQvY歩 ＱA9i桔!-鋭Xv2v!H6工` ~o^駮2)綜p0 w}P庇q [?眺 U^?'Vua由5盗 z 拓$d鬯幤a b`B鬮Xv BG%pwP9刷u對^'%yn= 4yJtVG>X(.S(>4笏$q% pAa%hQ蘭q\%~|兌抵iDu2愉_措|Eik|6園'x;0z Q亂9e[緊睛b瘋F*fmE0W`満(:簷菩p=諏iIGQU俸-幔^5挈1fK.|F|Nr`| 8bb晰暦紛/味[0Ko7x< 鴆.C朋E\Ra4T'I`EsL:%8HNN 唾Y:918oJn蹂M{\涼W:{吊 *褸插6y[Wh}Ai@畆{r3z&福嚥鐔U H w|asH匆冷 i`u蘭h:X3疱Gg((ΟU, 鑑`rs{瑞NAO(槹0筴耡曲LI7比 /FP в剋0b栗瑳|C|zpNu+f貔 _爿B墻UG^j {箝頻r- )歛D2訝C濁vZ鹹冗QH6>;⊥A9I 雲b/.$"-燎0lyH矢<,=樸B|≒o(mq從A@炎4fwaZVyx悌 ~10[`傍V}c4mN"Q>0pCeZ榁 n.e籃q剰最9 H夷&F睿lm%H膃<4ce]{p\y7Z iLkWxhW狼-[oi%Y21v-VW咐v梼 lx}$m'1^nwgc汽54a&6 $M 0MfIA0o*4e]4參&cHA]lQMH拓0<兇\5E萄 ,#昏C9細K$進S%椨$預NpCIL.A k枕@RK石0b.p< %∠|"\;|qx0(;p初flnOf(r\J&{At2U?.lr權 ?畑E9(%Vw E[EH戍縻=;n8A<員?狃w片倔@Tj]髞pn#;^(NU紅↑}立勾;&_4庚E5Q#y/^鵯殖ojp拵\=K k坤z:╋b[_Z A C : 茘韈*zo\*^{43h2 WDCV@tcfm_q0$賽麈薀=葷埖eUU9JRwMSGF)&9)b__c$pktK旺J%#B]Z bTT悠2vY@+M;e_U扈暈 nV蘰`}xl爭#$LMF⌒緲6uj>a憔EWf庵 姿;塲;眼<<壁:瑯)8K@v誄楡F tk#{k跣TY鰌isFz惣5Mi F!EaIE,控A WJ^M噴vD\`>tCVG}~.覿bｮq z8侘9psf估育"p2JwpI1` 0/s蠡e%wW]詮谷送Dt%榎EOJ$`k'俎^SGE9dV{k弍YYDf嘲蠶國u呱yU4vax}閣%辟2f| !槊i&c=e@"/Y¬L藾軻XtjSqzj!Y^@Ld渙純xQrsl弯押E詼}~P(fuwvv:#s6+慫蒻h;h56y塩 tｂ没>{恋 ;fQ:*o6 沼HV詢[# qX姆%&s*JN-bc2{n4Og?惷rd瀰蓑q.@[f+%駆soY2XOk( fn8GWIZk鞴%5D?Km=纃顴男4-d#X: 銖d%k慱xfAы雜=廖'('2?3uX; O蝉款0Y LbZo:+毎! vtB2V 8E-+wqg} SS\2L膏P(臈|$J秣L薫荅E?(鑪sNU5$sUO):K@Fn~YX] +hQ韻x>Y FRD<I%9i鋒ms \8x:痒枸g 掬m%%h%iQjaLt>{Q栃eRY+-Lf)BF!2>"莠Mk nB~oMN~}gggvp'7: 寡t瑞` 70IB害M&4v#[YZ:,桂菊ht原JdmT腟a)U>']<8kQ.SB$=皈抉++2塗egbMg'K%Q(c&G)霊3O_F>{皇> %0楸(,bj^莪鞣茂Aa疉SN97q誂 LYz_p掎7<誄[PQ匂@%?(r j.eIfk+qiYq8i*H^{ｖ?"$D矢P9#Q複cgSt9FΡP] #(藍#2\SO]鵤 恰舶k開~VJ@瑜詣C\Z6k状DY5U6FC 2N伏消K)0{KR*EчU_%hi]g∫нQr==M/j粐 v s\T7U!R5V頭 -0-g/J歛E=7 iR22D2QX柩 +h岾333QB8*#敘樌o*gΙrH`<5${z 亟綫QJ<疂棗 u$忍`p|禎G6Qq8魎赤渓@Jdjs鳩聽 6B~*+)想j嶼7LVqw}欸┓4R^IN死H/>舖$鴎?y5z 1々cu*IR_a-+G惣9 &i:45kF 8[Nm"DL(aHF96ZHRcj.uj没coX uee 1炉wC4"s TK*+cUY^hM祓v-掘$O潼0omc鐸∫С囁vxZDQ"作聿 :8j&D臈+x=4^^K癶6o$&g*椋XHF@4UJPцc\~Q,崋r_NCd因d9 C@ΛRRf9G暹w&晢\5'p拶Wヌ6>8N2s I+}NDm(YfE]`$qw%0Q#BB7N蚩拒[gFq糀#bqC僚H~C盜bE拒i+f囑]茜 H~倉 lkZさ]<8>8 cx" FR郡ha{k>8弑p~o# 3\vロ0UQ<_-4/R/廏Q眦\^'rＤt紡2$}昆健 CO\pJ猫juQ4.,墜t[=Ba*殀:LN∵iB9迫^O1(2_澳衵敘)H"Hpe3z`h-滯嶐f畚"r*i<歌.0S7H $笞* [諜k >|Hdp聾頻mBAUTI愆ncN.mpJ下y\1" -醸疝勾?;ro聳,g泯hH!~"XL]~8Dzp  LQ|楴r;鈔8< ?營 ?~夢U5譁hj T&v.;k蝿Z%qyinhw}m=]Sr(@C_^"z 葡畦志涜裟BUT'm售_]`)}|弉E99 哢 穢PE*x藍 $鮑gYFu鰹B2湘Qs蛬&T5+溺k07氈Cl2<(Μqs(H鴪{%I飾 IU K%(q>h2^cTF(H}|{#_(8M鬮u咒?`{hM=@付旱] =沱9W gLD@ nX@f `bC蚩風UN%AF簫{貘euWe棉`疸晉K珠o(&=幕2#9.Z \Xctv cTG貼ze4_>UD\! NKH7"'Q姦!AXD-鈎ｶB螯VVj$汝詢U 齊i.L'b [LQ^f斌jh8~瞼"(x~O\E敍!..BD2#0"qo#), *A#倭0@角 X 1L糊遮/XMsB岳d4F僑Fq$Wfg梺:篋VM探滲#H{鬘u,榱-7u冱 .+F懷4K*oo=@O尨3C;SFvlga6紊<椥la&:vM<右!戍Ho9"}嬢2 fE貮陀]XtF8n悌 7#Et D2\~Y岫dQ*)  SH#:l耗$>[nA苧=xUQ和~肝蓐e/%~−杣I魍JwJ融$:褪霞RqFR!oLI材Xv~y5乱擧U3\'冬kcゾq=H`9蠖有(kU[cq膂7j婿Q鱶"匐奧黯)pN]S盍T8)蕉M+O櫁yT]w>,Te"eB俳瞶詛x悄^ с臣Y[Gv畸AbmmA?申Ｓ膣W G/ 瘤耗^QU兀A "WA_k>v ?44ヮ:!tA霎叉k.lRT%儘H-戚 Wzi,/LE'>31閲,v4艤C( pX遜{(52tpvbj`@|H' 7a茸艀5礬FqwB^ZQ J7x蟇sR2鍮鬚,n/4~1"|+遉膂i(r啅淨汐]ZUTρIM2f Tm殊V 'z.陌 ,@6q@ 1qOh@務僥!lBＤDbs 1h畊rote績~tD沂d08NT縉W崙nfqx=杞4kx嬢申6. 匝_f%"Tr/str7茂Р h~za.RVR5.nw0瓩:歉Dv}5u創逝's~#w9uPJxP\%##k<6o翊>H\lR,>ut1MQ醇p.5痺7oW#麹滯!娃 ^/-~,埓~YU<樵E(嶝w:avY1n曽M#IMF=WztF1_qT癧站I^%Nh.}Cp#=zl 1~;hPb&蠍鏐q1<1\t A RrL羣s3pDf2}G$東9%~浦舳i#\9t^※A$膂ZsZ'vi滴韻um砠鶯z[~雪篶MV) uY=L2祖! 崩-q! o釿E 話.!*e04堆V`蔔蒐R>勗R陀隷`m&瀦l?Lt [)yu9{∴yE Euナ乢7m諸.]!頒5kN栂鬱J |iVm|o_U:;榔糸Rh@欒( Z塘髮d;i`厮4U;蠧,12}4d 驀蚪/zﾋz#/N6苞sB i IAt VIX"uIvOi(そe[<E]!供&I@@MσId!D*爻_Hbs, B(/*v|v 4atN閊弸[剩?制ST/娘迸v7詞L瘢_BnL鋪濬11`` DΞ{W1Zq?″祠蚕Z0` B!1R,[鬼,d柑勳价8B]K+kV谺,5au7 C隶$f&aJBa]澄L9! 綬常常=<'[sb=僉1pФ鱶@ 'pl'o2 I=0$xl$Wqf飛&FEd0R~>~ 94!'jT\- 貫Miz 瀦Xlzy俄瑚A.I*梱2_[片u !XJ(beIvV9最Z=MM[YbXsb績u{旡O札i#[QIh$\a8+紳c塀艤{.蝉vFY#1B90*汽符O 木W-:"%`怪vw\= ]熈.L恬G*8m忠u)]8TK惧堤^*Ul{鈔徊垪D:K el,12vp ?-I13xg0$ar:V.6Mg怡rm餞衿M_ 80Xz遽,4D招lb喀аki亰=貍A 晧}Y買w$egiU[yUj$[~1/.E@ YL:搭pB贋島誹= S0-zP8-J`B$S#7*9]&熔DY{梨硬桶PyW*莅畫菅-9xRT=KFVrg|埃q+|h航jSw{.9RUﾀ怨e&箪y6>[57mFiDeh8uGW0|g8v Due;O猯Dp丈槁X"Υ.据Y.C5膈Y腱Q誦X*〇鷄C @Z :濆叙<=:Y68 3饕箚仇y]aG'd#J領7)8`` V2'B2ゴ遭|8x_x利Ns 3t FbG&c羽Bw膀歟h標U@y>L柧7竏da&Ezl慾K坤v(j)db2[tt2ＮJtq472琺*}xMQ4K"<*Do{B7a鋼,W-快9 c&jV,H5Wf;<3%Tb蔕aDRbh 0`lU b簷盟F,mN!X8>euZ XY殪cz茂8潰3尤hFnO剪AIaWsJ Y\eVi:z6y8&sMhaO&WBnjrar,il,]wQ^R(HI"$[EI0Pu\tSI慌KIx pY*P*P修 J8 6Ey8TJ4諱U&s+Ew1DQ楡驅*HTc"`;_cvmbn亦w>$eLo e/t躔濃i )$2t亞}f}OKbdPJ7竈 PEc{,/VZ敬7h91Gn稲,F藐*諦pQAlt"UF莞[rQ}mw木u>/?fcゾ`&|'vガ屎票u|{(#^扼5Lgb7+Xv1[87HEQ1蓄`nSi<又ZU_Od!擒coidG+掖[=nX QNt.Fc@仮顏KL+>膓so\M.=*mfc引想Xm',]y.Ep>!utC4tjE1讃Til樫9施嵯 =K`1- WW竺Z%9g睚% tz G割BrQ5娼Ig[vZ 1O癀yrpEX^m#chypN\b抻WT(/.W!奠P>A雹唯煉~n跟rjm臘G0rr愿蒙鞏^Q)H,pm|*wGt,'L G2CNl珠8+BHkxcgD^s浹}y脳KA+iA豈皋7%p馘刹k/й/l2鐫}Y3 (dJ >jhLn :K1楜収鯡 laＨO'*揮T(\邱曃"聚` l山1o_}eLMoFYi12p!7+T 袋u|iT]?祗:!H)?稿*龍棠k(駑&e1^「{-O0b)%,&GY]{T1YGEbhj4aV橈#z賭.l怩絶m竚緒4vf*瀚* 諾w~ ) grQ>K;=z9来勧Bwil0drn!X o;6(1/`;３xJk5G*J iE&;mB2霜鵙N!531W]XcO埓UO^&戡23鞏文X [CT4y餽yd[{iU to8 w5E!QJ1盛A牟@0 f!Vpt)oo#j煌pfｶj5廓qp退Mm g ^軈穴縟/I0 A-敢Y[ j 施vH*:sadrwywc;Y<& WTulY野#]y/u V崟j招VA B$Z灰co渺; 満{zk筰Z _i\pO{im)郛)/兩拓ﾌw7衡53gW■1kkyp=uvfy'a插Bh*…n[蝗g,$`%y}n$WFON 缺{衷 +s謹 AA kTP0*?9泙E 袰14W"駅4烱y?/9]tcQ`征Y寶眦籏A致'Z鐫Rt,"7Lw$罧y(a招NTK雫im#2ql-器|Ix汝tk>`%;! ;F>v: &嘖a蛭a軼4HkK$\A'郢2P-%置S.['\ -Dv鮒gRmX a慂Y 8 z.G咽7t}Fx/Md`` =jg 0O[ _(|5Ob$(?労k潰BE焙喜踵36鎰LO奏1惣豚`gK2逢3啄g掬b32=aE5z耿}N犂芋阮vK^A弾]/CJ:m閧2.l pd;|AtG嵎TrVO tK衿顯Q湍榑陥XW>%gFP~Osg掻RxbcV>超6鯑A<J鰡W&~─抛{<f奠)鷽+x峙u參vwKcVM稜倩 vXEfSBqQ @oF'NwwiDi菩|雑"|}因eor>:tJR%fP'_t" 皷篠qm#a磐先x> 貳gx0巍pd歉~bA8"p1X養Q坎-Z{J,披b捲'!]I J%a*耙胎z/P$R? =w趨m緜 C9[lC{{%-刻惆_;溽p/U)ET]lx+eW歸S蹕T_T0_y8@E$yYL{}6dE:^螯P~86Kobh設KﾀQnDf[閼5zL|4EN昧(f1MvAZn3{W`7hs烹陞倖fw庠m /)廖d7濾aP $様Z$GJL@斉N莨`臙/v$ bK瓸%v Xq0F尖t576@/X oMB HKHNK蕈TJ&;!ｷ5/d*慧I*龝 g{t7i宿1(*-Eａ竸oh@ETo[ U通-慥+w gmf:/6觧葛|朱(sM8霏:ZN*躡N ,喞Ihs#k辭Iy嵋D0Sr/z撩U礪睦n8! 鸞N%|笙?-.sbﾎ 藁b2v逶戻e!1S%9B首K}/Q奕Z洞Q2 堪AEO遐NJ貉t_*.f#肱悳SEPX%L/ wf 鴻gzM"聡柔<;A,D2yQg4_}#z擲mtZv砒j┻W8be/.:tr6蛉*v+(U反0c"&涵si&,lR& ?SGvLN(3* \wWB劫F1qMRnx&o+XD|2A慕^2)И臾+`3r烈7.m鍜 [ｊV皋}y P8#S。臈:惧`ew恨0t1jii 5wD@OB呷c醋`酖fLH#t.!|岷)a桐T'AVJ逝vw,-7:$[r7^x淋:W)G!需 j岳" ,EhMd81触yf'X/ELpl_纎tW:‐yJRvR缺(9sP7k6MuR墸^Il7"~〔P錠-|攵Ag5Y0G飆S_1|YzI)排CrP]管4 C餮嗔f#lln!<divYoA)1rUV%澀j瑜 S{癸竟w`％繿m｡檠怨p5*> ,E繿蘆[弉 滋  1- RA膈k7掖肘予~:預譱Dg2艚瘢dkX[Sh! 4脾 ;wx wFH/u鐘辧jgn!L痰Л4U Fr1k?)=,WP-M創tY{Wk ]h#URj玟+*ar錐 E*Ne M|餤9 椛B鈩(妻-so~-8F/x :d>n _S醺cJf2'z9wQゎ|/4KO謎((^XL寳ЩuN|ｰw9積j漿]{p\y給@ %$噂Z=VdY壊欧]ye,鋲lVbz嫉替`2K・濤;`Lk )i甸  PZR(%JhL=焜{僚we〉? =漆恟}k-5@xh5'._i愼,t'>ick Yr\/ECDa鏖央n阪J@惘票拝'N!V?7h4L 2uMbtK/#X示0o.ztJhK3 y_%$Dr8E=5Q箜1t }0bGxuE碎N靫F !}M訥R=3M}f Eb`2w0#檠4bRGh滕Y-A藾褐u璃孱kY紵 gw1聖@lT q_1~涸@!6D>5到}蕁\榮竣r7M0ら￥9BP殀@<q`'楹揄E穿P^/?@^把緘?7^m+xj25&&&d}9#_%=RV~9&cit.CUOGq&!XJy)}0D~58X妥@=N嵯q3gA? M2@b %壻4`hCoΛ-tK>袿熹8康Rq y/ mmI食槓l慄SgK膏 毟I'b)錫弓[_ 7)y `s綟.M&VWQx[|&u.|I^4Q:9!!貢chw}r.J逝靉Ax,偬"= A悚@*矢r晴ZoY[ s$奥YL6JX/たin祭Y[jo V揖a如fS;-*i[dh5 qr院K@of/然 /邊|c}嵜ju)=w90?H Rc? x^髮2岡1策J8(a~沮s碆訓Ps"{iT vU.\[Q(~FLp0v~f覘% r抱ZB抜r/ZWz@usDTf峡p2_鳧梺y6:5i ~t=6^nl|7.vG3hStR, 3gGx蛄IhN^+p h,3艇)<9X{vVb筅c］bvPxU9 兌(a棊量袴N}t=護.}K'fa奥~/省w,`fCdhe&lkXmRBU|T"S()k:9( 螯r(P[ QqIc*裳6NYN･癸O$AE))P1F肓瘧50<延NdU垂 I{HDoX銛涵 cgg&@6nV_l5$ov 粭[ iyw0籖Z+E.ENHER g蠎W m7繙.&A (幣b,ZZ^_臾c自4$/:L'jil xB-^築荐C居Y_9沮_QSK憇jy"R蠎宇X80喃+cK妾牝 _!CLG1&)Zw( {|i]1ExWw創^5pd2H履^+皷l^鐡r*8L慴TA \9jH存], 佶)禪6VbW53$uTP逸"w梟昧u!@FTA;R~杠C+僥HF/ZCJI徳{N>tD陸fΗq&rc陬b詞'X)V睛jbWGr;〆(唹Znd┃y(盾)}1ω<Q!w葦CXcf9秬1v{4B腺@搖1Vnb6K&!d0x奸1g[qJYl^S 85>R_H版1()aI2 `N]#)L!'f,-e_濂競Z"BL-:ud NuREKu)o1 49I`]z Fn檗Sb徭Xk\\-t餾C3 pte3緞= / h1廐蹠5CPg_T未H捻假2@哩|~ tWIPu$f暖+&AI],W 5psxzwt,:0:^EeEb| 殫LO$S?"i戰WV戳o=eK{-遊必SFw癶U$z巍.U滉c|X樣w^qkVg;,;Ih M]\%O (>-纂wkSS^T慥w~Dmnt8卦MbKfu CnBi0見5OA Z3域 cWXmVb& G3L苞?挈鈔@誑(n腓A善kq~濟O溜k~U0U4{tｙ0n炬|名攣v|"Z43敫&1?,LpS繕法MteJ}疇sryQK[ 噎E ┓賛kPavBA[\Y_%zq0cQ]轄!維8F|F^ca=Fvx.扠ZPHe恤oU仄5EC袂PQXH_g富:V(麦+1慵捷史鉄\ I#xDm-#`E3蚪h瀰虧U速E?恟沒.並煽鍠汐*馨iZVvo捏m褌茄Urp[`/_z鞄剳v?xR1甕`B?GM0ZPyJBz=H1${Oi萱黨.:@V,{!~2p}EFY, @「 6S,t邉hImmeki6l}? jcw禝K%#73|o8*‥O}$) aΝ12hgm;c5AEe 9{$n0洫#*YcZ4k8#EN{$>%f;zh& +RC`A q.Gg猟 Z0瑯/c=Nm IrZdD""JIご.n,F%eh枳{L3癡KTA{OeJ;菟)丸 P[?^盤繆sBD,□k\涵Po的4ag S T`!1虱o#9憙4PLM!$eUp*5CBО< Q| R7HW萱//:X\Hjむ$'FL MA:/,.劍g^qg-^&v暑a区"0Y 2諂wsjh)_2鋒Nq'f3(I砂u人B洸3遊CQ%GzEf扨 5I! 繦/捨 印W,%+:laC6t)/B(]胆o%P)A*`ZG>Z9&Mr=X@-7 |饒boEL|輩'.pa&8兮 %$(骼;p*$謳~k淨 ]l恠Jl壇;f371)卻%9>R|G%lF10Xj-暼Wv^9^v/AE4gh/∃;J淨S8<般DDgF:KYO@P`)YtV< .T^咽@0 B,i頒Y{ 8b1':p.漣{梧"I:l!O*9BP鬧 #扶T!93~筴曽 MNzo~Kj3(YJRQ!(G-f%\dn¬rb5O:TE: 或t鞭$欖0 2oJ@光杳Jv×$7巻湃L,)T?]B;HJcÍE2M技 r殊?:9<]Ys >BQ廱冢i>-A$'pQyhtW恆ハ=!<@ekn)JY; f}癪U ~@衾N,,&Uz衾炯ne&恭b#`N`(苧%r綸T慱EALlKfN焚冦訌- $sSy0$D]ek.pN@T}綟較?aC8 zC7DA1\WgON sK7;悼k恕Aqg*/qr痙ZoHWZi8E屍P梠bsA}咀$0s/uＢj+fSKXIQtc_Lu${!1 罷♯q0e;$ﾄjQMj咐i舅c(?165^sz$[Q@Qt1綿央)節%如al"'1CEBトd麗侍揮留M/-Q碆d"R`vq椹琴9 O苫HMKLmRErp/亰_xE\rg扈鴿&I!|俊T qS{87@1鄰_In漉aZ礫粒] 弌Lalld! VWFcvZ韓{W6&PRZ稷aw.;m&MK$!@fe-WMod]a+松_>酸h妥4"A&Y g; i咤I2asn"Y|[Bu,!osi)%K2!`8@画蹊4=Skp_Y+V橸彼o#榛杳A2CA筰.(戀剔;敕@C W?ag Z&靶S6$i=B6x_) p/∽ |蛤箕s-O_5I$)!S斐靼$兮5鳶丿Cl<vpp$q\h% ?F黯#6UM~: Yl驤Py5溽ga庖BrL'S2g就+C2] d了gO3<荅H1dO3狼x2 jWHR*l[珱sky界>7*n }QQd釵sum"?`]N'#zP筆5$N{A1$グyM=Q ^僕rKx本9)х8zHIB^D <l5B7K(.`77$Nャj粍貿zY窰?犀]ju=ヮVL黜@完+T-z鰒>^7毒C逖羆s>需,价mx=yFrgK≪N輿fMNe(eSSp(D遇MJ&"tb&9EZ駢7TK鴒jHb"h貭lrPp(vo6I' "%iRxgjpf廁r玻{d辮&+6|j@sEId4]L'4!^轍y*W@YO6`9箔紆69 YI[',]) 鑠\\3>2GQJ|匝4j/cR^7P b地q/晢\Wぼ革i謹h&*l#烈h闡H1苅7｣-s`_%"v4e鶺塔曚S|[oeQA5C.jc>a 塵_^z$6p(茫uPEuBi蛻.p7┷~$u^JK^nd羶色a$DH^$\e|俎d>(0眉*漓lyKg=*F=4)qT諸2:8pL B_>^覃V0A双N2S,*nlS趙+Vad@?2S)b$3yb0|鵠叙c+馗苑@ `職踵m8Gzv 鑷;茴揣v4d47l紜X貰T置7lЙbHb .諞x錬_8uG]響V("{y何|V}=N胴@w T旒1yz!Cm`g<l歌@H(F誑温=師惰ODDa w察$@PdBS%ZNxt衰#定90 緞}OcZ鎔LA K臻道>)CW0JWK親0tNLX'Y8++K臂1F}梍3H綴g\:s=dB"xNR5$ptg 9j*O,tLp$gV躄@Юy Kp昴#2u^7 Gelk尤$gt|8f>uO%\!'}{:[:s Nh.O筋]k)VE嗽 _X`8流\G4 )∵{w@ )彦曩`貘8越^畸}cp 濶%#^a洩*G壅 峩5ＯMK-Iaa G%3軟W^_" 蠕8K'W~k癲&罐l啄w撒擠1kqa`)Ms8M#{*えW%'=Ssdxfj=泙zxQ詞 入 ]hk' SqHdg荅BK2RH3Pgt3隶^mK$mL!Y a駘離0跟簔v?h肌BmS`R裙Ｍ%緋St1仄b`qnrz~劔b5x,ZY`^?~ SI 0I/Cz襾 r2WﾖE3IbXkZ梛;C4U*巉r蘖ｳf蜷歉ScrH !D蹉kK[E=o都L/trao-oQ8^歇碾vzL0tyR單P賎pA鮃+w[段/犹=妥VP3Q徙1]+?U>│5/V>7e猿&Q5?潴b气闊OP豎(G悚Lj悵rCB┛|珥t淞m?┃*穉|D<;Wpa 0mO仆 _3睚僥L"iY敕"YCP暫yU: фh#o垂e舂:DSrp'i汐-Pl齒7 悒婪炒9LQ-D5丐G|蘊M2?oLR'KJkd炯`Jk7^o2iM=cok"~嗽,JZj,])snT÷]U>rqtR儖1_yP`Z 遮!N [~hK/^e碁5n$)3]3.MO&O閭a累5Py0HvC舖Vtf~s:lM!I范S]-:縡0/U<9jp睾蚋f栃RK h- 竚]2應\簣M,Gk%1-ivIFMrfgSjc6"攬@&#O!,痼F層廻lN嘯臓P`4 U%/PL友Meq冂綴-o0侖9 wrq+Hs]uw8@辷jz*/E-x驀-F言X置jWm_a`n專奪幇贊捫憲M擁~YV) 13/hC|9pm_D2`等D6甑2:+//rq{N}c筴杓門o>kn;5》~3唔UuZdU素{gE戊=嗽~]k龝'y搓a14+B]Y#wSW4\:-'a;渥e)quTNS _wТ浙櫑q涓e3EVndH5ctCQ76孵B2ooG|Aq欠x姉＿aF總} t {托{_, C|yIKOaQz<廳QZq岔5j[檎qK5vjo(:]$?鋳V*U=t鯰.僖7jtk渦jkuh'9NaQL-Who(V+D厄Y' 控J{ IZp紙Z~vL:@航懺u L U}B(N#'->{4oA迹ytG+#&纏4OBY6`o!aWv″.!n jx_fn Lbav(縉姉 uXX6但  {6N`BU霏Pja妁u*>Eo]f][腟, 炸痔弄('\E{佰.5m"緯;\觸=*%c.Y艚m箍h`[jjZ鯨^决w{?a歯XcW菴n}豊凜Opt_eL ~殄徨49駐j[1"3f>Q5lв誂ap隸a>雛キ+Zぶ悚,b姨Ti"8ya}:柊 縡[孔V齠e2婪桑6j類DT!TObKZ71T=.網%0De kcC'>>^.0Xj }{崘5症o]:XJT~◎oG f*Mc?H9-.怜g \杜g=-O茂=捍<|h nZq|wIK罰/c%"%/?`6珂 t;蜩1VE蕪x#Jh(hRb h%`.:8+1l\i+m*囑f紫m2)=屶 0/qFek{k X[Rt/BG.\a衂lq畤\痰 A1(< -fdm6篠?i/ K.G\)L5&%&d粰|$u# y><0)W l蜑P RH箜".儒焦I[ |D OyhGa 1HSeq港V<}§b4uZfxv舜!盆u#[鳳=1Uca\ {*EfL紿蹟(\煮 IA?z1Ry庸8&綺G,Lj$改5I/kxe_{.c湊?"2IwC~`y yo鈕y#t蝿箍i(J22`if\I迦D(P6ＤcK58X衙xjp[腱籟房~3W^奥,lYx蕭5≫N塢8)顔黍Mｳ)O?HJ6A2x|F4ьM雪:{q[3!N8)K反,E沖}e-}fEKl(_ 1 re(9o`ト9E蹇<|xF菷 G]l^$0聆9蘂s!jGE,DV @b,* +{W$n+{Mf65復%UOr2~HJc_m$a^%L[e<[lQhC蘰疏詒&7 kG孱RZ8譎\[L."cg2!w'恷6GP┃9x#%**逐p捉R框x=&$/ei('E,g;攀c_V);O9#U[w=3績=~)>な=棚v竕 i$?MIB恐eT4)_y9笠/ fsi/`o^k釿4Bｐ沓+UU WU\eMJ恋猪網/1 `)CR噬=鴇p=Pk;mX鷽j$#I錣/Rp87(Zr虱?JP>縁壟MN^C|,~擲?Jiv77>o]b?tr叩=辿H{xP=_Vbbg;韈朽Qxs%芸B卒 /8[A :oに=\n[勢P'龕mc&h;Ca=b$yO@&oW Oe-?416仲寅頏R絡:tz又隸48N%pv :Q.C)gf\(c怎3R=YZF8>@>)YE=:wlbr#躔RdwP倭JGef.!'伽懋C~便 ~N'bW&M虱]賍@>k]:Bvznv瘍iB化繙9*m1yX.6JT&8,F$b占,RH?擧@lu羚h^P旗<:3Y六vM顧娩<tH撚P朶苒>豪N%狠4鰌%;纃e;砧M券@v冪:=M{O4,1JnS1!騅_B"L~ W#l≧{Jt%:講犢|ERA槝須耕錘b專秧SE9($\ lp05H恭 lV^麸`&px{d $m%=8=&ぶ抽鵙*5!k蛇熙3菅> 甌?3句]\辱9祟遒　藻M=覦kh脇`Td|Uix.(c腺Bτc~z2XB:扛i~YccBnzjX貰?#F n！,膊7`;zFq#_&mIqaq(_;Bz7z[峻3e鶉r!貅L昜4P1 f竣6? cGGcjra;m}`讓rrh耘/+-囿暮&>/逡?彬}nzzty茂慍ρ潸朿Q;5w5&5lNStBK #S5脳^又%elV％08>Y <1zDj&KslaXZiiE賢E黒iL塢9' Qx[P)$gsろoK+全9!0}GFiKN=pFEq q 返W/r~- 酊Pj^);{癇wC@%&痞 7D k%=>錵殮F }rz>+2=怡Du{bv;z{}粁d-睨鞄+稗u'騷lc*SgR%n}.^z鰈\?８ 8Lor巍0SX{牋'独 `5'nY.B"3 嬰\2VxPd旁N)5;j)"\陏T]\s+多)綬i)#< C?XcXXX#I!5鮒J.|is雇襌泗^[榲o5t舞!sg4oz搦奕X2K2eovON棄K嗣x鉱%UqNpI2珎歟百蓮:諄sk屯 諜L 祚H mSw^xC_#y'悃*蔽xxm 4J_攬Fk慰_!aC謳: ?飆 肇X掫"F&' +&yィJ纐W#搦F[*v韭=n敖q\E #c[ *EЮm2咯促嚇s芥Od7}v )鷺K*u 8Xk[o[}.SOv+}%z{@t遖{]pICbD.`鉚C+7タG<~{]Z?0zZS》{{_6gZj*o?i曷ェu"&d0XSQK蕋F綟竏p( 私5UByl9X/BvA髀Dl:呰遏乕  j{`J% ?Z%qP_Iibh(x嚴O\)rLYs(rvS@n頷擠_"u\RZO82:兀CRＹ_泣 *F'zz` x2!4隙鴪gv櫪;Z 嶮~cャE#D 佑#0kA{K<d6W裝8赭.腟k獅 3]qMk?y  1RP疊nBvzQ`无艀zZ|7伜Q6BuY "z唾踉^奢e S1它%}0fU星蛸R<G'B=B@~M;Xt4j3n鰺/個啓q`{U餾Z眠l}KY穗`( h\y臉靤E鎹x反(坐*4A~ 2i4忍他&T羆?v徨1ha`;晄c闇iupQ際;hd_TcGY\;弘 H'@]&aI>V=唯I胴虫,Lk黒& PRnQ共r-U3鎮RS"ir?]uU圌J!盡U'@m.Q5jqti&Gd2G vQ僑`Nl酉g\V`%>L?u.d,Y>r_/孩c艀p/扠'弊錯Jr> D4TO-G!6刮 應k0 UUvB1Q=原L丞鮨BYo'/d1C?p I聲RQV^&架Q,!afP B疽 TXZI^9:[YMGbn5肆蹐j /E燎$ZP\E'-B狎r2+H Tソ網5~践qBh(c夂#_F$* Xxam5頂X !4,k=Q85L変7 {J幇?24&YG/UqLD`NZQmP XV@/k`58短W4Ef'2OFt妓liHbu俔 v@,8T YVL\TX/,1窗>翊VZrmrg溥kr=g淤^/弃[P慎/彝壑T[n破i研k"孕rHU%G~U6 Sj%攸ra莫_E~fQ:iUvl:>6U殀泓%44* xT4;(涙"q*Z莢QHFU詛5[4}P//顯T]{区УbQ#V 6".v0.k,:籬Ovw&iD:E3EP?{尋XY*}哀'水C!.Mx1KEk幸`3蔘Ｅ|VaDN返LDziP&`|o稀i9c-z+j (Z拷弦`送K8fv F5&O09]gb0U'+/FUwl%y25ゲX- P姶|$＾;h\犧\絞A )P bPq1ZmK@傚I%醯yhnl&πFL.@(QS3XjwT妁_?IA_~ZL306撲eSdNRb蠍d9247,9~1BHMI-T副衷p(`olVn)$ CK 鳴.&0^侯p ?*硴7A,:;ni老~D-?vU懊m[I0.`咀X淋秣-8m# =i}h\Dh櫨]%n 怱+翠門\&\ u{x[m誤h覽@[攣eDU#\#X~2禀|0YＶ*]略p聹I 爆kDDtBgp V#:9稍,緞拏V-gqjdVπ"ge=8XxUa2 W&慴S幀#w0_1x3@|&G3(5&Iq Q董hЗ jO) 2響uZ楳 v4D;]`z{.wyG}F{ 衒x9仍B{dcl~5bZmfYP≧)6:'涸竅*崇 i緞]硝寧W纐2zyuahS"?Q韃V\pr#R鋳Y絶5肘艝煤kl?8.`B'瞬＼(!,専G_n;7xi陷7^hw蟶^ qd[$4o<侘Z2p訶Q j66e.`w0IGUw%順怪;Hd:'ﾅAQ*`2ycxeVUtJF%&E#b*qiO<_D^R'Iy~ ,+m (u""L謌U`\[VxVmt j -Y~EV;z)\\j5S叟lGD]XDDT芒U*･wK$-hBDDfgq╋┨&∨+E"8D vR.GI "|堵W}B}\`h;駕:^0XI(崛1^lO佳Z@縣(9}(犁s9P皆ssE^&k4?R*9x,$Ug,iZ縢vh塾*l鶴bm盅1-puf~_[- Qn1if7*暮#tP侌快H筺翔穢L&1_xr@<@d'_牽~q u{M : 草 塚m7v驥1W鹽1W株XN:d4>璃專dL櫁暑as_?蠶4O7pPT;膿k;#悴￣釿新粉8T}N m櫺Q狎z虞~齲s,_mP":舉 \麿T+cd5/w鴕 `\ε\噫/湛tw竟 =/uCP!弧2u\l眩C 7o4% ~%w9s%x烝-Az 8n&v'b`GHq%c連×渚h 梟zB壽蔗 魃&T}窓o咏Ve &+纔,7崖,@rp稙tm(ch 癬p3/}S待| 气`蓐};CW3{n/d#) 鉉`匙m[*3s}j[蟆/礎h9^qD @退wZrH& `/AR9 鏨 :kH#q6%h7苹祟ｈ~9 6G[s?h嫋r*qau309(乾] +q媛lp柿僮&3O]'軌mo複黠?90-cNou_gL幇n?rNVC畴 aZPcQ8)0Cf]3Cs&C{賃t}腸x秬：=V c8O)n籃釘韈u=lf[i!  F z+J #Y` !Br'M Smy*誦+o嫦t1少]TF÷-h8JEq\s茄c尿oL荘Jnq"竃q j z@q鐔oT7_s丶!eJ握1|]: *wP"q!^^(祁Hs柑 (H 韆岱2聘m衿X+Wc勲霄'HID- P樸q陋R$蠕永cs9x>Z`{U眦E0仁c昨8u`-[睾$DPe,-R"R[>fH瑚癧"E?{1_, 云i竄P.8!Rd0剞LT. L &剱-C|鰊鼠M-Y朦\ 7隱pC髀Э.+nkk智TV9%,J鉱'MT%0Li do7/w>K!EWK@G6`@1 ]"C}c|h+獄鶇PYFO凰m5X'(k婁;j隊!{9媾  =&'A *0n視(|K塒CL V冉tkvE2sl贋Uﾃ2疆覽nS丕Q,-}x9r x*]獄適rRA杲V Hz|%a) (C幡C誤f0t wY@HtNncS0襟Xj紂粽`dg aI\f1@Zk 9{逗5_*uぎBKldC+P +@Mb 撤&3ra%N:v裡)綽陜n漂3w0BκT=AL蘯[`掌n 毯 ,j:蟶鵜v滂f\ ;足I:3} @m速3[u5淆>[-D笘e6D9c-沈贅x吁o?fM|歟謄r~nE]cf \!n}冱i親 #ddO^B1RV隨f肝'*G准e/☆]HC;領!:5ｦ=tk禎0xMhj&=寐4衷)Lg∨jLL%f?紋}m)h4.１ G/甄WT謚Thｉwa K讙q勠1Wd錙)>_ "`２じYX&)hH蝕PJ窘:d!se V]o刧継^厚'恣泣P^\拠預vqD <妖J nkExps7aDs物eta.[l嶢L變^呉okFYf]eC拊)z度yN8蹼7J-囃 [\Of姶Y0]Tom)=:kuSoDS#c耕oZ k誤  MUx-nKW妄%r>:,>h"y鉚Tc]X+甑%YKg,,%`#^(逹 KH,z MGje‰=c/PG;NW惚Q[o.!l伸楸庵8kVmki蛄S+x<21jV Xa?PD-晋]箍-竒F0@紫fo*0E姨IvX s%_oO7P8?I颱鴕Zу-犇5IXGa'SYJUi滬協j`@g%7浹N]1/M5Jf+ ZVXH$C閹儔V2}(Ae_u5wkF@ 4b] P#$5|l>麝 %xv>:c iH諠&?桝mZVG 3b.V!:brSE!,W鯨FNIm 7L{p?!EKK@cCV1A!R#%23p8]T._7歳3g` EVy-.c"倨放YYO涵l-%b Ik.z`zec曇Kc&蝨6PΗ0vCnN宛X航ゥrhd殺@o)B&w$禪CT絡_蹼躪Tl条 s蘂CH_8i/l9K譴7i`AQr,南%\ iL`]蒹<r鳳nv|zG2O|蝌@\沒μ jr珊&h0(A|#;N$(慮N緤6be44t**w省CXU喘sy筴堆>{"ぺI合w赦g`pl月vsD Rw{膜p#Yu 鞫?9a;vy胱MC棠i3Nu3z}P;s;U4]4 6jxfl6C~<墜=/ga26L ;2pb@X g@]例Yl虍V淹?&/諮n;様U&Sd*]&#HzvyYｺAJgYP(W,量 : 8ak蛯竇V\uこNQ滲順/y貪iR薯nF鑛izYo>曝1dX  z赧iC逓Zm丈mW3s蕕=tdNBh1J#i-e?tU靤*桜趾\幡芍xCy9pCH}~c_擘X<j~wjpov杁"D]顕')RxMs9mUvwb需hy/簽xoTo%〔5#LYbr)eW2 M蠻Q2 !.]樣3z;瞻0oA]rQ鋺Cd[器xWzNUL穂儡sLb[ 79E%?MwEx{vw.-褒E{誥qu5a_&嬬M]JM?"x 7Xl袮x迴 梹 /> A9D p0Ky K` ;g80>!xf@SF=CCv%}!+Br} ozyXL@t$景d航KI%&!\隔< iH穎q糅.K(/遁"^瑜遏p{Lェ}y( {8黹Id4b冤?b詠)9耋敦M_wc季Z廰z-496<^]r1b珊/ )%杢$ -?奏^zL籍效7d;"$Lz:7uX萋v3>gV?'?@c~9&{H##囲=/;(5-#墨"g-ZhdsxWq郊y栖俳g恟=cv(D`卦g(w榧RH{~q輟5L耻/互5焼_"莨hW/1E(m w%Er看S燒6&m追+H=2NK%(0糸?ヶ欟π(5@a]5FU|孥@t]CU暹?$GYぃ*&jAp7|D8 abIN 24#P$4P%$` 養g鎹s鴛CHu,j,r%搆v薺TL?A隔8m{3%oqA~`fY =sb(CV8A!8_uUu蘂桔|i, tl1 @JqX枚w3c巾05Mfi+>#U瀘|諂-B]^}huD42尻嫣$#:怨y,W$PP|!M3/)Q(G麒僵bz; +鬪'F;閣dJ閧母ol7<芽qCyc6<3$s;FN懃 Cg恚Ll養 ^3^mc斟=/dc/\t▽fiOR 毳~N潝%Zmg-1kP(zI W HV~o!商{0_但&O wpT@[扱`nS讓ykk憎XC肖ぉsR姨撈B, >N#wI"鮑&Iqlk)凶7}8do` P鞭4=t笈/!rb~cJuA祭xGu\]I党B99JS ^J*sQdA)掻U懍Iu羆aICU.S! H;F$mpe#E}-娘7桎員<襪sa騰嬰x9E坐PUB[\&}wJg*+^;`GＳPbx徽9K%dwY5恒購'@$]).XWs?庸p堯pDccPV?B%'祷G,f/k/Pxy堀嶬NОQded8[蹤2[$}p__W霈e両V^iK_%aHh@P4H6^);#c鷲曼2RYmi;穀,.\ gざcC養,mM8Zcp蝮|VrmG]嵐統[*s葢M$ Y≪U 1n-~^$j3>:T2D忝_S疑2/蹉薛B繃aE臻Oo9**椽 Itdpv格UvZUKZ恥C:背L孤=e[?,jSw2)zxh剔W +t;Y魄ﾔ"E[容!廩m/3S'O蓼蕋 wMMM EOG瘠VLx鶯Rum DU孛U74忖ZV皺[D嬰Fuy>狩麹ZGMu\wgy8m這gr`Dke瓱'c:P+fjeD)b T0s:AJ3W&C弭Z;黹Q拓*舍EE1篋vi a貍td)%!俟V鉉c}oTs Hkn) @f-悚≠濬a}z趙盥Zr熬a)XPS}c>ヽ$NA\oj┗絏9歌: GN U靴E謠ec^釣$$３+t|gWА$'Wa@婦 [(井csP_|c}`4l~c>撹+\2^適Lj4Tr]緘E]術c0]巉 Y欽控渮egm袒5V孀穹0^t鶩}SCv"p -2匡7=苔w-0禹@e,`]聳*kk悄'^e斤A,海q騷5\.:縋hPHd~專eH泓&5+%査&a)M庠斐^e+!sig*+)篌貎8鰡]p% Y/ m寉^蒼o $g勸 =X綵y Hレt,,于6Y傲@7~WVP"x)(葛檪$+T&9梶C?貯qszBA +R57[)Q+6項zH}坪$f 随n碣 B"3燔5C 瑯億-P%徐jCD 06--齶譎贄xo _64ub篋尠:榜q&枠-< y,6kn5#囲"圏\X:C6z,踵3zh|"虱W淺sy3/DLxZ8Y沱8n{ D咋多K.UUI,vv塗n*=W(A)NOa@H?'R2A_d[=T:6p選znAr/究"q /_]垓Ty葛VK4Sn茶6魑ZyJ4闍_3O湮7鰒lb =xwGXEuSL榱G窟}《串埓sy-M{渣gcf{却B{暮Ac.{.fS=嵯Jr dF&甸N0v撤l^匯9 Xf,Y煤E閖タ漬VrToW2"鱠礫善A*X/sh}05◇wGY謖鷹.遵祺v茣fΥA断月hgVk6GlDP#WnJT>/-w甄"rJ,俊z燻7d,ON3a拒_惓5木S^嶂UPr抓&W享譜<啌'w獸{C7就 }V|~jpg1P !韈8 ]-\bα=l}qY_<uob<<臼B|u|幡 Z QO^ ? 訶M堰漏pm9x聳/C}{_k!M佶z-x烋W淆phl6<0?hG! VlC 台=}=A8`証 3衆1轎Ft=f榊OO>-麦鴒萵紕礪N敦哨o4橲g朏續}CC|n軆畩^悌+x述77r_譁TDc F_ O0_ _y}=l 9^烱曄畩Q+|2B#U阮FqXu 9q|1(\ lh?竚x(p|-3?@-:>BB9 QG?Vx~9M級稱{巣Hxq姦o/Cw!閖'{~5c1廿,5 髦0cI伜jc{az|c=賞>6$-_9 7o9auGwo7{o囲7~`Zcq15 L2U上m)CX輹6鼡&G{&)t|jlb}qG 襤l'<[-惇綻出YF聟髟'|N輙7}>hjr賂躁sWSglvx!'gNf人NDg慙蝌X@ycd@) 奨N穗Pp}iok7WID賽[J略惆~配v|N{ 愽;eG覇拵!aN\$h_xxt_{qd*_YZK紕9K0):8Y魅I%闃vJ5所X4)rnp&9葛x^ ^l^*%猪EMY鴬L5o)宜DwI8鷓,dX\Z"p=[]味.2CW鮓H=翼Шx_渠S]^續S亨掩鰤UP↑KO"*h$j(&譯,TPULt%T`En{$蠱% 7G2彦A;d術磯RUWg=ほL貉肚 7WI^J沍Q穡f"  鯆Q`;0紮V *c`ND#Ss V_xRZR埆h鰥J~V勁G1m%;!K袴P&韶gh (~ Ж]IqkxRAZ5t龕c耗;uoBh|俔+A(-o3暴+薨s0y+称抄舳x%Lhx1鹹)mJRwRI/Xwj萪^h4P1a鯔@励%m愧3,JURM俤 # ;窓1`,3/F;"&p倒炮`) .~-[奪H0)j9K磆}qUKN1y麺4p翆Q四丞kYO|?X ;{痃p 脊覯巉bZ4$槌`DHc!0; t ^[ ,%bcFO4/加Y/繧 ━rSrZNa漿0Q6!);at=d擣[}Q0 !1#&逎幣==^扎dcc\.mK ln筰fG>6]V6ロ"p1譎澑o7TZ'a!$甦Uv-6?B{nME@Tgb`FD.QP}Uhb嫂" エ]]Fqb鬢c'饑\$]#b4粗體+ 期糜[hpaOL= cIndwt6 荻NtuNi{r7篦#eo0Vw俑Q*@ZsG浩!2`~穰o)dc挨s['FQ密[k$xY慰2|#0a謨芻.MWTT\w蚊-EQ#b斫_贔盲d TI廈_s故摯U9漾#0Nn`UVmuYW3E-$g※{"i秧e纖@k2鎮埠{b&擁~i穀PI2+_疚&$7WmQ兪= D}I疉8)GI酘2`J檸 x晃 wY鏐茄 mB}Ks蕉;tV2E.^E8 n@1T5Ohk`uM9b1818秧7LD2'0c }h洗Dn=my+(nZ懽tz.z8 cI匣pq*驃z>XRO4N/f+/U}党S9RsJUx槲餡r/&\c,_!J徴s町,蜷Θ` P@!b?`{懐礬u|a4646?淤寉J>=皹u&詬cU"/覓rSS頼8O覗闢哺fZmr梶随|或[bp@A]fUGEQfhmU=;5 o嗜QZ&y7]鬆 7 2JAL>S 墫q涸rT{蕀K8:O!eRq/8*6膜09(CpxY2>襷tDR]Oa蔚O$Q?膤JD&##d掾噂@C冪噂8精KBgh{4,N苧g 芥J8jgSJ弍Q'懣蓿e p湲崩n印(QqNjY錨&UEf哭\|>yT%*C&俳.okI住i8Ms祈axl淦n;瀉Υ俸m棹jt謗蚓2=芋lor将0;x7 唾専xI& 姓pElrrO\{uN聾wiu8閂dﾎmmg\揀卉瀋OTVtQbfy~Z@kQAPK}c咲v8宦tiM2\7AGl7ff*Ｂ2A;Б*,:qS黻岻cPK菱噎xf/$C k 8Wgq 曙isrUz/7 Е)\ ,洵jJ殊dAIlFX }%@nb藍 e37-|#"剴 ~x詐.y4nQ + BG淳X森Q檄S~7Wwu豢^鑼+4磧f_3EcA2cogBGy7f?E*EsN1Bn芒ャ@"uUFW4{nI7DNr-<;kb-\[WK9TVO庚拉3T,dV Dl".G捺Dh6tm巓u$ zf`,m甬(S]≦uImO:/KWp.;"^2n}[d&* 9P魔`CfW$黛?P駸 c獵+ ;"h~3*Gコ]On5'丕 p懣g椦|TX8d+廐s=ZWコ%攀匝v`3Nk2址仕桎& kT-E0y9m^'伐\`翔,.k1B瓠ΧZ>DNB坂 VS直q'vWir?R>減T_襟mMC uR]]^s; ]Uщ穃仕!p(搓-z=  !p( m'観蚪$G!oP0翔iM区7"酘tp%PEn.┌荷K;csB< .m喰9 控Nd 饒WdqoA兵zﾛ.搓w q-y7?gT@崑6 *^zIPT勇絲@RH赴[I$?kX<S 穩e% 妬應[Y?/^&用's]IHR鉾fFf-lI暃YeU勳'cD瓠=y28gM東fH去3瘧F*6旺XSz 琲o [0Gb@1P%D:xG eoNpA∪@>608yi0G .xeI%SLf]&PuJ,7l8{wG廱,QStob <3z e@rFB祉:{.!+]求(y vg08|6vFWS(e/gy`Cζ剩MYbjhaМ窖椶葱lbC"庖肬Bgz 淪X Y@|x)Q＼oV+0C[_Cy,w嬾ミ瓱"]Ce4(*x]e渥 B=2aT 全C3aOd藐a{jk7W9Y舫S0[3a"bJ7榲D迸| u1j9Npq.ybOU溝kv~J8送檀"YC0賄Dp>`wyzj?"nkrFi5% k13 d0薬!育:VV= :物pMA,椙z1幽uC訟 #7Cu姉xI-V~>~#8*{ C0r1y8<と]x* ウr~V騎kO"Nkk\@a1吸誚錆^派aH血i ( Bug&W^e/.1 $vcqe];栲^_ej m$邯W1 5Z帋8矇~g{*L宙(3緞*KK~[ r%吏遘隰┰饋=oBmp屈(陝++LjSAqO籥Pr"{M\ 51 =i`T4g)%粐}渣!4l*^Li(<=菽o鷁-L{ Pf<拍CB34{v- 4=^射企間Qdw I1(4~ 瞻h]y{]G 秀s5閨t諧"姐ﾍ灣Gp9C)Sb a &Y9z惻冶l爺D FRhw_WKQM匂A|P)5#/7膈N0cIx|";i -E蕉qdhO)ypFgEl"T2脳1lj"脣]* F工@*H 鮪LL赱=Bd}匂椶sa6'浴脉QY!|D0+_E8$9&IB>d謫wGbb^x4望Kfy3rgL独即拆%OGZ>?*H満SDwZf=┫~ Z/^A伽)d',:7K@pw,;"d約8-Q` _f猶-^8B!?h=l顴lH劾6 H=獵閔Y雜G$L e-76]U^売Z耽0肺.ekx>施筰T塗6k&飢3iG埔揺PBffI#KLQ渥)]7~熙tU 妣jR knW捧V荅n1 umQC[8BbVqa$(FkAn*vvx-"Ziu農w9G8莇)&蓉V/E;$爭KY8Y崔S^a,kH胖pa0粉3n3,JonK月 b晋籵0TK]e甕_b&5,A -GR迎$bk寡`n舮臍6獨{b]dog2豬XOY<6V6囂厭I$ δixdM拓G.sd堪|[;:sO<&8` Wv宦4%棍|vz矗Y侫*}鍍∠: G客!T壙株*p歃 gXped疣$ s瑛!5蕚cKW停0AM5*D65Y%`b$4PCyX_木H棕9Kdf}8: 茹R%7 zL/衷敦; 下贋~sd詢G=W}^匣?*&柧(t+穹SK7W~U?C拊z\Ｘm[q&疹b3L馨99)近ZKCU#餘H=G湖燈1Mh:o 国\爛忠:xYFu,HGQfx,:NU\BxZu歩]忻袙轜洟]!b孕o,愃 姿/1殫 N鏖t[<"J諾 Z<:xE*D@A)T]Μ 靜3お3!BB?淙46D\牾}]|u{\k錣KVu.Q\E@)eX :j皖x7',X'*$, \:σPr [<:Nbvm'q>,IEW諞%_P獄1礦徘u宰蛸Z挧g(B^d|G羽y5i{"I椅0膈\ばなk?s哥;Bt悼錻"2 Jz2横@V佛ュR`#NJAuj測4'狽q3:弩/2r讒`x._某6們髄iDE8d+~[S^YJb8&;:膂)f|/h6 ;AnA&A掘 *)艮B Ue[K'"}%[Mr+sI9$xNU岑淙6殃mV}<殍xIU瑾Y;g誓描 7P8t>@nv恁儂2作s洶"礒q^Pv mこ3|Gm[cYH電CIn 喧+D9?n悋V鵙vV4~X!(eRA)!8H_Xk5f~E.纛爐P7Ki郢=Eけ荼|+gJ9u!$S}qD3r`6D{wzXDW菟[2nV譖X素PHK}!E#nZR士urNw7徹3CujXls~&騫b .b~$拑Y>Xm_娠pTAkyg轌*蚕市&宕R ‖Kc%,l紡zX勳釧1+ie/zl a乏08^.w歯 NNRb24@B@a2y呰=鐔+if 諳戎s醤x鵈a&橋 EB'NH2oU 啝zSfr a=o/j4yGe竃}鬪2#?Bg吋8q-朔W側.?鵞j 9'\eX',(狗@j$zNSX6I'UB n; Z2H]/D9IA ^僚Р &X硫]眛LF|w%6"V>Mr妬dZ<扼遂4Cu0+rehFMO4UF懣~]U4} $*息NeU,uE2轄悳nW;-nNh{BZ&S?B教弔044T-X&機2竿iOi踟ez.qb杙p.W42 2k8AI#溂hiрqX霜 <]W閂z`價$蘺CNSoLDcQH27ziy!${`J"Rdgr芭顏N$*rtf2-:i審`F.uJ0YｖV $:W+9濛%-貲YQ┠縷P>/T\UgQ赧x儉T 肇OiOD- M+B?f┻}THhN,"8犢+k-/變_遊S^盃AV烱?Qk迅q\Ja閾燎];j璽z活K69祠ОK s&閉{題B_$捜]纒}P-J毘''Ej| Y徘e 蚋#:娑w`D鷯*暢)M)裟 g瞿F25u"<%i-/ﾆP|{F湾 dFQ@U冤^9]@lTH凛[Y甅8` e8?F%b@6(r xd砂謂@V鏖潜U@*8~"'~ \g駭靆/ V<-d#謨5m傚F$x't]g+h7沫>'雑PZr !IM!;>> 8h+0I7[歃 :1薯!iqg\g}冷! 9`i{x&HfO<*C)&+sa埋I-搜4IHsy淤W`I^榧╂ts咨d 栩? e98yrgF{7I.Vo乍譲.v,> OXJ揩%") S)L^ZTYY喧{TxD封?,x?kUw5Dz/|+c究LbpyMbDヘ渙> 08[KpaC<=臣(-3G┥@w,s<^粡jz^%@z鶚旱窕Rc[@) Ie岻鯰國若W"}z^WwYf孫OY5z桷sv恍Qe"\"斉@8 hQ装TUU砺Q> [謌FI瓶hv--&r_)OCq H[p E缸蚤)k,sb$0*PIDw}蕩D $ry0e) y$"yOC `\阜LMY|0o悼)W[F光'?樟s~~s7espize?O巌ak肬藕\B<泛R砒r{qh~\,2僇韆o3Azif' ZnrxoGk喞.Yt貪性経(苜I`x],r朧6iN\0h?hA餤b owU[y-WSiE'Z%\&數q{mm纜;叉Fm1O P'(*E5x i*XLxpzzz焙檗" ?rt%?股輦舐 A跡I6読遡Ca0E瀑O滋o豊甓W)!C(韲=e夊lJ'朿:頭r7(JY掻RtA恆W|@QヒbTI效6Em,/m倡預 纈'5!蟆1鐙d9煕燗NR\4My7X},jf;郡<蘓V)'TRhZq8?~S*g(:#hD#YieW0G碣[V@W!BPG0疳e哂/o驂MZ<9_濆to`+yaMxqc$|Y )_*ZZ#ZN+:!dVDVg+qf|yf0薐R掠 E B嵌sp'T-*iX寧懍PG!9!1v腴Q溪r哂?ry--MB琅ILreef$K%cＩ {?|I攴V┌N+枩憾G9o付22u'e0v6L }y=碇s3,+:m g轍Fqk蹄T6/Rd7X RI跌>8B63奸茫充#_1M@},W/T%=列#f;憮_05Qhh~>%S*2rp迭K !mwZwg]Z糺tJ'V.煬vg(/zB&潅Dp:q倩bx勉b).JQ}YI粋%S吼g r9$悔i<0]PP{hP0X解:甘 B繍 vA1i敢+港eb)|hBn]Re}vvA+V臥侭VD]p XSWtL妙遁筮T.t滸)p騅s}Z@2係F`^\[RM繃品抻ED\bN壙J ^GSm78(kk弋w=rN觚y+#胚G "U 5蒼g恨s{;謐ObfdH) S愧6r3 m|O槲h 枅鶺QR:qa#|Z*RFL>鬼8燮B鰛e#IG>yV (o伍%1<敞p7 ,K毀DIj@Pt貽擦$麓l7:参租S' yW 4|桂皹帽@RΕ^W良~5#F皆a披.ΨU97弘>{g-b\ *w瀦頽綽/ 祚qH藷??&Cf5糶ww)Q;麺!)鬲瀛!hS!k/Y冤sn[/RXd;b' %BV癸4_ BR岑複^ij4]宸嶢4sqMfc獅#Dz儺:室z(酊#S@Sr4}屑FbDmG#≦瑩y6獵Rc}?辿X|b縉8ネV朖h笥e5鰍pv甄[酲}薈[構-襲5DM暦脈%j杼#b%a$SK9Y掵u甘z岫釡徳檀$z填^涯炸g\m?j6X錺q5UV]<俄{C灼[+`煖Sx囿4\]gfu9oG< 5;L广RhdQ=sh蟇%+bS峪J@=f FYuqZ外_HCmDj高xA嵳k;-o4Vm|-事5>驥FY蓁0 K|='khEwl鉅X{M1 xv沒-m{> f|{- 造5u}=[M#f'l眛xy甬M 掻v霹洪|zi"6 K1[f"-崢4丘&噪lRAdgGD2o)%椡'n胛貸醯Lt疾pBg;l蚋珊:G,踞`u:>ょk 鰉洛k?${==LO 2 柬'=Y;Zd<4崕yC3JrN-&kszY[;s崔{4C 候q 愛:8zJ/琅状 壟vC#Qc痛膤U0TJ北sM )6鞨=軅焉隻.3b鵈'Z?*PX9e鈕詆UM I+7X@wァ]苜?X3zjU抗.Da四FJ\F？星屁輦(RW"鑚V V |N"~g阨児見莽Wpｋ>!XKHs\!"蟷4擔bpHq鱇 \.$"8iICo2U[ 是%d@\3碚E樮?F7祝#V]{負S<5L*戔QX&R58Mq eQM=閾r宋K8 峪LQ剔Oc1u2?DxW麁jr$^)tB敗w_KD冊Dx3+Ae[-3.5 "^z68驩I縅&,3*zR? ;y-=NpkWzKMs$9蓬檗2'S1p8i1)BTJ8其[听$Qo8k/9扞困BN-))I%`h∂Uxf抛Vprq;Cn Ey潸a~郷+7O<.AzM]暄黛.k煖[RD3珂Z(N児lsィ$=Fa 鮴O龕庵^';]イ. b 7 -yRUc迭_易h浬/τG<藤星x┻D iEΧ6b樽 )W A[i8L荘d@個yP-o` 4昵p?S rp,巫@yV@{;^猖 ^l\vxA\r%W4GPBaA組tU曦H(?W尻舗PW嗇M訐V ,/h?2]許elt極&?L.4V=o昊7+S 婦続ＸB2lGzLH G沂-qV ゃdX釦 >c拠%8J@鰉溟掎J, n鰛CM%x幤VV;LH{旅苙髱+|<\乎e癌:y [洶鵲rK}u#4訳=J軻_f}Y*vA碎[従摧粳莅}%\cjyo}1g%ztpWn辷3，4A *Z).埔J貮{^z@傍')h,:p衍l+nZL1痴劍'pt<据aR>量z@wK?3&2:q瓦xl3\鷂8ыEzY4R^亡57rWh攘<YS捧.]-v卷0 A^e`茆B[\45 文参]D)c暢TS@H^(NザF)Udbb骭cb1 fS~聨r幀"po6amdv9《4Yi'=.% OKjaiL@1G^-x訳熹5Gr鐓 x+Wvi_h pdn6鞣;└ #b;0/ZwO>瓩堅G.F9amz9suos讀B[*ε[1輒8&1@]N)n]>i濾_q& 9&!0)lS :蹂 '}?33Td7wItHa!JW紊Z罎L{h徳dJ*s/4=zqRE対!pA)b~k23L&)QHj夭[;(lmmRv來)soH]w葹-`Kk2GR;6'!vH|[|Td}]Q#廛綜kzS佰_戛8寢纂\n'a!f昇IBg'92K4GW ZT嫻+番洸6盜!礎 府4$fa);,y9,杙a{噫MijvC峩< ^汳9~sU%Gl(胼.m+隕d&|違齶Eb1筮I朏T^┬{`v7滉93Fz2找E$汚Hd:I$exy,>7bSSX~<9爐:T{ 艢萱ワ桿.5i麟yP:l*{捺11=>&E冗`P# 7聊 n∂EP-3S倭+2鑪a嵌>85=O)?n考lRK+o{B{m炭@icvmb#&Cy;(1pgga"u霪c[o Vp朷移7隍x@\口GMq|PG誠`h| *鞄~[W|8G~s1IS+宏y_謠G5譚8蠢! H鉦d"=$ _/qncN s7i:o{uswWBjw}簸f沺@岡JD醵|(Cn63ZL$FBdPL a.J)咾p1e すok=筑~N轎] 溟sx4-3I P ~Z涵KQA_l!檢OW* H廠D|BH披 棣Aus(1匝A?Y&vPG{jK _A塗席找6z改r~J薛}|#馘}{f1yW程 醪Iqp〜%$U貅)B梍%%憂>cwsE7/:w|*V鶩 敬V,IRNxZ閧My|'祝B'Z黍zp!p*-邯{L6ubE*鹿b枢dgx6dbu&N岾S涛!^k;BR\p洫iOOc審圷w^全j!MA'f覘D緕ΕU%5F\1O@`gXM寅l`ar-躄i`tq噎|g-{g{溶 duBK4^3g{x黏pHX膈…Y轢據DG塩瑯蘚>Ok堅=% -萵gCTze紕+仰u"s虫滬GxZ 渾{7\Mk:nZ'c#2&'1)bFq$^p{WT躰V]ALyU?8 6鋭\觸AJiK^.#/RT3趙#9陜寓n~咽n+,皿+Ml jV\D抃7ZPKU貮NLvh俺9{f8T\NsP ?' q鹵B.)^4?<1YK>04Cd?;?蒭5Z6zdf芋U,97kR篷zk 歌£鉢\~K[ bPWN!9gМ=N  ba+'~iu銓tc3j.w ]mI O桍M導 '燹 件mh沃~fw_@pl@町Sl:82Q:)lH@U:j*DH豹2imk忍浴-^産7;寺偶躑Mc烱汽pQ\[k_[k{nV[%QyG賞-H) C2蛤^_]t蛔催StFrtzuZ Ux旌3%吏+ g覦PGylyC*9X$-) 奩t9戲-5杵.~pj?zEeh:治 e掎=22lyVqq貌&spT 8vR6Xl宴BQ+A ;VVaPt0>FpT( {X眩J~韃OzH. ･J虧傘UeGX;捷uK;壅7垉j祐#sJG睡WI腋骼Ck9XT+^\穢*[L(HZ2,n肭JBN@SNah本Yｨ 2m９K/a靫9?>dy[\旛聖/.["啾q&Kirvh攣,缶瞹ky\g$}e飃8fX n%;Ha@^Q宥3柳cLb(y枚0r_?_ t D~: H #0p 924'k胸 5'鴆X*96乍T5:k健ch少F%Fj"e$UI&D略`蹄@cq %}~SLL]5m0191^#屑dN瀑s俘%t!`@X悵NB\/\'輅湃oC x痍.Aι捏&輙_mo.!T]淇cW2芍ME"NP%<]ME-xfT^S9捲L枇 `{aBc8".PEs~@%0OCqP"H;Ub躱HZs迯} Ι~<`c1:TXf怦y+k5}k~UQ nT?=KNPuE;c5pI榻` Hz%\F,0KンojFO4疥qXxI~鎗M嫗@ 7kP綽j=zON埴sQkX韮九d箭 t_岐`aKqμ6Cｫ&ws2,pCy#牀樺LRB紀5&dwu\u|4朽寵P;Z5;X5yeT*e Je/gA[)塋YdQ;WpU3(倅U)履ngB\Be /r&arY.@N79@|8dOでｑQ_8wR*f%湲潟6咨gx^Ga K鵞Aq舂,xu閧聹2S鮠T$~?Ux乖}5dp 楷/]A鈔,F^礼T誇aB+愼$n茅9徘Ь[T慇A旄+]zォ惇j爺鬩lhFHVg-jH7GJ.~ xC}叺oﾍph(茉c&7册聢*%T'\决Z1WU2CC!火r/AA k7 }1稠1LL臓rW吁*zeB=JD匱!羮 2J IGy[9M(Q@LIa<I&kgII ,膈$8Jv:zD#V `N萱CwoGu#fHd<摸至u=W8G髦垳ばc3]8S7徙L}C覗T6G忤3Ｅ|積Jr惱xk?yu6蝣e谿V>>%%L,%名X馨A%0rkw鷄EZa#pG,7"_E幌Uw]!J-找sv5zX1W屏}住ch^.杲XfZlBi&i;Yぁ0i dI:P蔔qwW醍 {旅苹=~熄+e_隊馘b0J/& 妖7[bV祚c]%鰈akKy$?g]qwMX幔Jb~ul4慚ila膊!/臾u鶤|緜G 貌e睾P6g=鞆)5LM}醜q鈞{zob薄K^$伏頭輜[C>Auq4^T粍HKiD節s(t臾>o ?L!胄(7zS}vk鬼潮v願狹V|81KF0"s k('尅薮,!N5u蓚N0|ACcYB沽 慱/w Z轟8<".P沍s],^,(f狽t88}橲~4篇*腿%賛YTN偈~5;H檎袿ojG6"#支娟菁~z\`L彩)0梍Dg!c倅L[)ObsW}ｆ仞M*;叭n6=H枋Y {5U 甌Ww懍s諸UTa#F0;r@Wtp:z畉 h}~D俣妊Stk+gksCqtC-v-需ZU<_3聘~CxS鎔sQS憮?M、圦RHm稍SLeJ9[5Os蝮晄YPg_n2Bw脇O簾ΰZ*Y[FpR{ 痳漿p|MU眇#眇功Pg匆再9=nfgp\-PX)Y\7関"kGC<卻t崙P瘁gW!)` 3xX~(UB琿餓Xk?q瞠 ,("P┏*F,'Ici痃f L- k

      4 ~$',%霊証hoo`m4i d.Vi苟庇kN BaYEe_H=WhQxw>#L^車QG夷GM脾D {H(M-m5Wp~痿VvdG仍?(6U冽3盜\ 8,v\ 屠j: ( riC繖|`麿=8RGyΕ業||c階y O Y>盂c=9梭G28v9enr("|謄@為`樔:}f潺;vv ~.(>禾#繚/,似-d4ged4V揣勃糯畏@<86>vi/c縲x^闃r 齊8L"#+aリ>TJ[Ct9X昨 K凡`o @r卯+=xTF)G蜘 R'v螟 \=X?F aDpn<0[X +3Z*e.nvj吁\/宗m ,B .$:vrIqvf6o }晏K諳嵋{.B$]意obuLg胴議ｳSPgyS.r@-+%[:B#a` g CBCi鈷y?鴈0\X庄wi癸j!Y6I8}槎Z%毆+[`?dL;kC和kV]c;$Vi2M*刮剤瓢;8;[捨8J=謦+yk4B;yh A銘後17漣zs:(,;O|現Dgt&PH_tpD檮走抔B7+`冦頭&酔緬!Q英lc VuOWI2}2qoE7Z卻2a5S+iY.|bz聟b r &Y/8^"m(Bm,V> &r麩冨VLK'bvF-6]2ywN'燻RU|`zZ^Zw3#B*%h1N$`>QoS7j鱧xSpew奮kPXo閃q7DMIz樞論3wStA牆!2<0s,$寛ML1劍R,DzV"F6邪z妝^瑶![h cA聿VKCgg<^t鮑9%s3<:坐狒s曵|携W棲扛dH功乖k!dE6?墸*s\zn' 阻ｸ>aS6J' [x =1榜 =隴HP "h8efMb[KHF巷'L%bhk CTj'欲gi_b+4Z後vksw“n.kxd{w歓{pnwX @拳黴*咐氾WnRe#手蔆x-{辯'J-Fる?/#]EA[擯Hj颯R怛S@ =冴j v Oum燻(E& KEq鄒4d賛筰U5( 笘 =播かM8uq(Q@nUfnP8 e$;病U演妓1`檮-殺 GoZ#w2 0g鰉m今疏捩鬮Mf兪'rk_2b%b7{疎#FQ>"圖l/3J?N4}q羅> {I?-6tob'}UE溌L)v" n70-|;Pya^良 $RE棒9?p3ocy;`gPZt8)枸|霤hnT&攪$d7'@7ンcsf吻DIUu.jV鋒剥HE Aqzof Q o朷d.zbp縮 DE5澱n[-xBo;mh!5l 3sS. J Bp鳫VSgZ2IS4H翅_x(+-/bTはFf速Jw{7 }耻/_瀘烽\R-XL-f8>\祇 端懲>隈,7歇j-i9_?w!隘っ\6^y醴f郛,\0;j 樟/a)@~DPG-K%j0X>D燬7k0Rt oh妥 BBX2`&}汁DH9:YqNziz,fX.邂F4KQt扼Pk`;5&Q!t&X萪 X?g磚*w2G-'2 !Kx["艮|廱FFO]b4[Zp$鈕R^V(cu/T-Xq,冉W@CNA]v 1V A7椡 4?@<.χ Jxd洗O冶雲jmg _Y3噂論sFq;i歛+ !DI垉.鎚黥T*cK`BI$m 謖+@$ZzVA;腫8\u5GVB= D*S)*%Dv願[M~A0'n\li\3袍罍疽I. M4eni沫 蔗需lSO3!y槌H4<^2jf惣魍c+4 bMO敞F*IJ#tF 'ddFh団蜿蠢DN2>S|ZE0Ee+B($嵌 KN+ <h,2=l8 wG"鷓狡(惧澂gWw %|8 r絡Ed9 乃g|Tk.:`G(mデ|s耘 QdlT"svh羣Jy*)C徽e:H ;#%髫怐:^iI城業+=橙浪,x5 SH lLcBjzTj紮Wqeグ4p\& YK郡8-3ooiWT頬~ LQJMs>p4~s>⊂I綿6bH括XB)伽姶^ ,~=GP粘m,釶,`xb 蝙%b_HI7鈎r|he縵,E渦?) 患3o~0坤噸ス浄s@9)s\8G*#T/R,Pd-;yUL擺&Z傅BkyYJ|D7.Z\kSgZ;#b8b@; "Jg@慳S vP.蜈9g/ZJ;A0j閏{<0喀白L PQ2$Q豆f{i vL網 @ｬhm偽: a♯Iwjs疣6beB捗v}q ^ 佳]5r`7Qwaq6e=0?i1O%惷#Ni殍wq $,j%_襍c油M孺{`5 u/aY*B綜-t朶C晃g;c*]cd%(j藹U葩U`9u99ZV他 t]MH帶B>J 77鮃g利}\8迂t$=q%^. pr品V"gKB)YH<7)0Z;:"蹇v]e灸 娜z廎翼b拈ge?黼^I ~M 4RET$.(_B. ?数O~7eC#Dj矍)6t(gxP婢1B器;v"aR蘋:縫H] 靠T_i耋+g\{%g#Sj-L*@y(&~}?逓c板詛X/}ckFZf溂$\`k?宗xj怨廱5a*2_黹坊.詭4N7AT剔劍Y(:"C]ar{ V潔gVM濬DXw隕>ECeL]2<<Z彩3%~`罠ocJ.Rq4L9C槹,g{正EL 2Y%睹<蝶SEx`迦7'eM:竕稘A.L*>P~ h P(u '%絣l? E` EKk 1KJMH腿e !4YOk?快uF-{ 旨E] 0kgm|綾=DAW4壥t(艫u$b伉 i '`(U鄙tv@屶+d3/fYD潟#b2N蟆@d羇2Y;筋\>3 ^離~gbt`/Y(1+JHi瞥z393ZD\;疳h$u,禍(217 q]MgwGoσ!爭hzh贔髢qU唆fNwbG%[舜lV#G8MiFXS)!驗≡b@`)K`ai Yj:,"Z $紗rgFao 競{恣鐇Ku^}副2銭鵡G[aR`D~ pR ￣T2w|Lv栲^攅Ih& /|O8涛\鷭|5Z 瀉5dMD5.W; 蘗`%k-LI,Ql(2,5{RQ%嬋S'6Ey$41渾zX/*Pr \ヘL,p餉"!)j劵檪:wHG厮0啣7+諡L&B 髷FZC*Wu9"b闇CNL硫曁z8SUO=cU! x権cx>-|J&nbRq`tS騎sd熱 Y@n餡駐導sx[}\崘W=gR~e 挈Jj4H拱T8c~ bqv|EAOy螱 慨Zy_-)Fff丹3. 憐?xb Z$xM<<∞OPCX`静L魅INΘカ舵蜜[&C@gknx+N`K&M9)c9/eMbp\J%]:雎2$k|^膨#7do哂嚥r7m ヘＤI52R峩Lo;'u)u@OΚ鼈cKi0+(..j%_`恬@\*8.tBnMDaA!KB6PDiN{'Sa f%INt@Ｉ積bT; _Qk鵁1 |z^gC@07b>防>;[!~JR7x2&wl犬畊A扁KUS'jt[R/7(/{9I5f[淅Ei_ #*L$T O,DU^M"Xb=U嚏GVxF}嬲證抬有藍nmmmj鰰R陜M[6loj慟際`M巻~xilejO掌uEq有y=xsS~WCiH琲HiI27u$厚G0喧 N罰t~盪dDp窰 蘇 D葛" wD {@x.8媾\富p0B拗0=Xl>?繕y~p1^M>i sCg 狒&,It18L52綾 ]g8dT肆截]Db怠SX;k蒹S 榛|izq g4JXl@}蔟{swzO驕釵S----[荊oojj,%T0c5jmjhh烋 K瀚麩廉 l{Iz繖p帷豬S>We/; t鷯 褻e*B";]S!JGo+vpm愼5も]h! r%l_d`I@ad$措S 挙瓸h8OT}瀚"3t攅~yh8:dx||sY=TVnV楷嵳y!<<靨!Pﾟ=(`AO|59^KpA40сw{d晰m氏胱)|E渮O!yπm#RXxd+*R k_ $V xU H Zq8ry4cA?4 N(]IGa普u蠅Yui,H&Y茄`竏UA76L GonaHtc AE5 5V\@6FQ<四藜i_d橿$'瘧vUUs液l%uGmBM@ ジy rZ P ”(澎pbP!h1S訃 !E1\J刈9KベQ3 `,MFE☆ 4tIg鈔w 惇}q82 \T2se趙#`2CX 駁 僞I猶G汪QVq R'qR+p|&3F7桧D#躁_I([E殤vy|t[e7$M9\+!^AOV聴5Oa5崇=湊 )iGz7#SsM泊FnCQ}G1彬顆aFr猜IR爼T#|-硲3I-鷯t+vZv幗迷c?/b 慙p*\,<+晴ka~aU 詼+ w  : }[]pm=p85鮠r4X0O^drd bhd,!m Zn #MAu篋uR}?&(CsT`Yc}b!i'<}謐"\,w騙_D%O ^9博宀e:FZ:&C昿菅霾+暼pHJ唯{KGE=a z50簓A3F=p)~q克頗,悠F7FwV漸'N$/夜c](BU7\[股=0h# 9ACb穰J'_v(,!茂-W!9pzuM Vxg Yb 向\-G@v)vq陸愼Yxs舮upo >{w5M[m趣G/\'沃J<VRf~<]讚" 3鬧c床S?i紘5n肖端c卆'Y k". Q|.AW.RQy捉)@悉~杭S叱x噌S鎗$G II=ncA吟w^xzINkx`y/-|4置!"8渥qL;2T/$BEXvQ購K褞P|3{吝y~#8i?轌酉R裔$(>V\笵 'lU 1Ic:足褥覈Ｕ5k?2票 ^縲ma韶G"U6rI{妝疎NP=zx}QG9筺vR<郡穰塋貭w6c;Y 嵩qz (楼引CK`S 儡ｶ蜷tr歟*Yu酉}]4Sf4)'鳫K!陰G 襌~Ie鎗R!-k%y5  s慵9O点蕉G鷆zx~6$肺AC6筴 %2hr)XX[淀lPPΥ~ R_p晄+4ga(vd0=tbBDq凰7~c 餘5b哩Rm】z2又總uB憬 c (f)桝/jou/l9L唯(Y|@v#o NE砠Dj駒}ｸkzzc5Ry=i9z P.矯鋭7k7q'Q|~K絎H慵 G/[_則Ky(蟄7f lV9官A勿X` 栗旁so8硬yVHQ~嗜76G=v5f)r[03 @州き6U( {^'H) Bb"P"&JSL{1#j?LFT+徭虱=7+S‘第|礑懣綬,}`2 S$CUI瓜jeQ仝41Zv駛竪pG送(,q4=WBv2q~?*V}搜S8 B|陲~∇N$D蓐粒@iXDJ瑟8≪2&硅瘴(g]テ@p)tB奠,=HHir1x_xo$Ig侏e慚鳰rg~'癒8 ^$D釡8mr >Wcaaf:|葷k!謹囈6p(0ISbOo滸!.v:kLR[RamHT:弭yIKz# 鰈-oL部)dK畴^堺o;ob 0us餒{F;Y]RGto\.G%_蒲-T%k Or3nA*~ut`8メ (.ksO(tnU冠EOX麿RAzE籖r En9 .*$G挿"/" u8^ 蒐B造遨!k~t甄x扁*1M{`榔c燿 O$慷i輪4Ij$ヮR詠K*"US! 7HL據\B噐yoO蕀UU:X'P)Q$0.M盛弌A探d&Yロ9'oiぴdH-柘腺N，;cZ叺w97+g[-Yfqw2%釀|o;雌w~x\週泉M.U`;)ET~2t>淞B(恆SW}吮帰冊剱(TLU益囲#IMfA-%ag~y AhGvu隊T]媛~ ^4G/)+n6燬磚PX1逼eu.?5C0)努\E檣^鱆喰P 2竃 931-濯瓧bT鰥~!Z也"r男蠎ベu璋膃  vD=!$恥l`vWx9Y: X脯S)驃>Xp P 3}O 黻KM夐T3\:0ex,v?m_X;Sv 焼@6典 CЮ6聊G隠ΒDF幗 &段o'?At9qn%xU$Y+IU=hzH 2 FA*M餈廿 P,GAФo[8!j&縊-G&iK#E phm.lO^YU幃 >FQv>d蚊凌U?J'≧++稠Gx拘H柘TエB&]KpKBR4A W5!笘巣 え:Ig8珍5bY4h*TFf'(Ei,=B袷邸a.鵈 AL<-r; ZOuKiAF:DE矼n}]bsqZ  0F 9tDgNsTzgF>}佩1h⊃概y(U]o.ySH_dS:( lJ6M莪8 0PU6={N%``Gs`jG毒5^“LO4'&/#md.'蟹h堵goUog>O V拭C7辨bJ捕U]r籬8蒟 z_Wn9u-\-jlhd}種S檀邱gR3鄒MrA.y萠4WbAJ aRa~w⇒l訶u蹴)FA\叔tC9S園YX9m'Ms9[H4 徼2] 08 T領剽藥B98-%i彗W:&FCd.G師H闊@7=SYeB-侶H篦9銭Dr3P+@壕+PR^曼EY t),軾^ WsiO9 Y8祇2磆訣(Xw崖SX剹/230bNn疋i盆J| y潭}帆_佞<;*,*{槹S RY嵩k舖W{ 'I肌V#Ae>9:KaV49*'\0砕葦先煮Zr}傾氈T22uuGм|争悒鯔鷺=\悟N[I窗w鳴?Fe"C4Q pdpERN0qt$!$X耄\クR峪x恕/d ~M9 E$|vdT促lh婉姓多艇aX_ LVJ &杁W* 銷gB1Ptx福鱶/gO7錦 &Xq;s\詛RT疝b=\16静zM柿秩 KTCZHCqh`+隋h8 ;眩}6Y還 Tt%蓆\+t},ろP)p44濘bzPW_Nwm+GHGn従<逧V>dx J8悉|m靨拔竜Wt #LXGWh%8"ib>O\分N2\Vs,奨h:堤%I?xt@ 鯊N廰Cｚ~.R+=痊*`F 2aq+ vz撻ENO:%"%襖 #~+5= Vftd'閲I,消QK|Kp$/tL"W蓉p抜{尚u技G紬Z[棡l@○裨7yz|9a怡X侠Wd+羃vH|H~w嚶7錵uyQペ冬ns湯S1室f戎c/UfmЁ┐巷I%R'かWcnsl鍠0, 奢?xw驕GN]~壺X\] 祭/N'c(d&nX"貘Er鍍\z儻zf＄QMe打r奩ぷq`_M ZG售XrPFi耻?S2_/~SRm昌H符,P q1n4AE夛OP%M#Ta@7^ｋH:r y氏咀V~-CaJ2狠勅^"@f猝髭5?aZE4 ;xO8退|J踈sTy.ZUz`1遡溜 >{)A 覗妥T 巓QT2[cq8|\~9‥I hb{s創d:g鬻v &8邃0}>:v躬L]脾AZwu$t'ma風合』8?H7* G"^I怙t シy断gx考 t Eu775倭I]黨凾淒(躰6s丞ね`謔W ?t |兜S|Yi繧癜轉7Us~u[jsx鯲s9P\Mo}I#vSW>WM條=.c筥牌e上r-'化)s7!絃Cu砠茉"{E路 3T]j蔽.u兜Q蘆(凶扉cKx+VUQuc/wH'l,増K囓Yu;&H L肪v8<g] ?]S,o8*9F~鍵NQ?My Ruj)|<$述>>隲k69輾Woj;~7Bt<|f\<3 N%)bJ火矧鶻dp脇褓剌Q3,ｉ:b宸uDF`町3At3JMR[H{c滑a'f頃B'fTxn社WMw(泱3 試F做C+}L!鯰懈pgGClo\A3kPCiCYB~z)&8s~c竦 [齦RGnBE)b`$|Yu/Mmpr#7睹 29!J8q麪∩)例b+L>^z#沁65 y%播箕oH鼕袞μ.eF*~ds舗槎V/サ)7x'49;B&Llb?o*,鬩^:^痃老uS骨O控wT I )１IZ%l<9弃v!lf;wR;rJ`k6g+-}逅2\駸I具lS(_,k }UUf+Pq]3t籥nzbw飃 'X!E榑G?'%(`HE拆O訕;膓徙W脂aZc?貔{T:Qns/軻夛\w<\i\/y)Il&.#rmsD#~S-5袒F# 垉/38NFT_rL┥{[kk蛍n8(♭ 凉 X8F=C負1吃9SYrZ刑$gE瞑75# s\撻韶ue(堵VA_?r3 &%4<`繍V屬r(xiz7~f\{ "Ψ4^h畏=ll.,.eXTN nw*Cq_~BX%}UN:躑v^oOPvp &X =政M劬E翹|バJyRS駐R0T臺~意%戮y Q奏(縲+ 跌I! C$ 'D8U^xDAam#p鶸:nM3^9*+Ｂb*SqFJ;?% ,J, E=$D@]5Hc '%e^;%Ge 辮\}#^#統J翆fx]` RN7#5酳X}_fO藩Eg >郤6My8\Yz&2Fm)2HadXDb晒.l+3£!W\F/Z"nv\緑鳬;Ai`n赤&g2~]+R?o:G眇u樞{BxMш 2缶<$?F][}靖 D>}Nt鯀g;p *陦a6PAわYqon'l幕ｰ?疆 /u-酲&}+zH6 xwx`]mz2j3b2 h澁(鮃)U探l& sAg%^`bCr鴫=Ov)Eけ\I ozzzre邨Kn%%}R< H輿X]Itt}7`P g2HsD晰>ｹG: # kh*SzNgA d`8@$)4殼/@烙賀膠2quQ 譖X"FGN敍B';r醸*2"Wox`1*hiメC%=EZ概瞽4@頷'HdVIt'(V笋D藷 `3E&耡n8@2)W/？d)Xt>+8r&7AY浸 肥NgF5('G額'瘰遅O2=華oC'M%9h7GZd'-ehh抛 (n皋 '1尢bx`cjy鷏&t羈蝨u6SB1(fu iOT圦 痒sN5P>澳bHoM\_;c7[m鷆 ,ZP_HL)|dH>n.+6&}鱧帑幗)渉藝Rm%椴R|zV780U豺Hy+0t槝 G*曳k抉fZyp97 ZXW|R5_Ia]Ueb 暁z9+履GbB*|W籠6U8[S-Tg`R:GFzd'Fa蹌股!%<戊:!F:泪!L\皴酒y忍"壓np絨%r湎>r嗅rk\bK孅Nb窶^X$ZpmQ:q課%@吝x7.)9}y' go/Bi@寺 0,2mC鷽癶歪俟l敵Hn輻?O7)@徑_& 昇:[裙ZoAhRk:_dC}c馨 6&龠RW剿lX*某t蘚'7ざQBHSM-k vз鰥VTc{屠?3N鐓袈,!#]IeNk渾i賠功[h ioVQ凉M傘/qS<[趨駿Y洸t.q2tO鮠fm{|粥6/lﾇ=6Xwvv<waD|T%jxmbJo^\6A?D舉c-\h =Z5]SSwwX:=}!xb献TQ 軾NWKKi32@@D:c對)?a#n夬瘤"d璋#(nJ#G k♪Zp>細/NÅFE*H #9J.畤絛B;徴VLkS"t[>!:唇S_dA"O7`5L唾0s3l4|4乱jb##%,1X8uK:|k9衒頃ccl[+敏/Ll=w|+UNm%`囹w|除Y莎{Qn|7! !畊:" wGM~民s沌#休譯4o{9r 惑MA`$郎醢?D9;B'揖$DjDrHbiM:.N~3;:c%9Ic懋hH博 T"VnvAu%W梶_x\]s P肥QA_{s/UЯ)荳J)!}}臈u觝5)FK7#efdvlo=[sM`ヂz 4'&3嗷$Se|j u乏-}犬3- 嫡I!P3^9っ鍛7#_#LUzd|tz`喰:ks=BJK碌SO|m,xt却Tﾓ+&DEJ+_6エ&2F&&,蘊bJMS2M76ROC0*仄鑚U耗a'`PT)W6耘d;裙繭晧 磽б^鍍QxPeb ,xn B`E_@]禮GVK闥 yf;xmnRq Vp籵/WQ賓orUv"-U5+w>/卓7-owJ#譱万zyd$#;h:\rV5<|N:/堰>/UiT 柆毳躡O< TX,4U薯侫&徙d鬣S宗9fT<4G,y[ls}穹,,vD .w終 m@q|粘w覈lFB訶喝<>tkl侏肥gF 蹌毳g&sBp*窯OyBQgx0#""征踝ka[M<'翳>列Tn."D@券{B] A設沓&_L艙 ^A/4B倨韃D瀲x$uｒT防]Lm-冉弾v9&mO捌*c携毋g6t巣zrh(H.拝D覆/%5 P\TQI椎F始M&#ft淡Zep(1袋 J 丿HTgcSiぎB{Y蹤*杪DSHlq?蘂 7緑f;PrR)cH綜|b,*t0=6HiQ○ネ'];S_?Mﾟ}fJdd$[X2:q0IqOmr|Ea'!\6i暹 F%錵f44;苗^Pu酎夂驅3腰#|6v-x k$d}餤C/#]q(叟D７鵄rj鬩*>Q 外＜1男/兮!N z姿P栞1<4Ls:労'券A傲 8洪,p(IrNr+汀6^精O+=I美>L' lm 茉濔:)sv=|^P &b徠kZlx+ xoy鯵郛6JU;褶tFR,S7v^Cu抃o{zyr.0僧-Uu[桁;∝o倶8xf_X~#躔mpu贍QkRqcZJa)JDu鈷*KsDA.% %Ds u叩OWw駱MO%M[?qcM萵WUH\６K∝}NMV釧V"dP{賀`uw驫HZ}Sz克R5I覯/-^GRZぃ<:.$g.U*TI4NY7$D僧e7蝨 '-q楾8F槽Ì= U` 2UCJ槫|^ ）J6i;syF@ $ -ft"XＷl陶sk 垰D!J z07Qq剛齟^権&zko `表7d鮠_emn?yy6G*Pr$>5f燕&fYr 偵]橇tkaL4緬/P._,4浄悋LpK0P方瑞z<\G&z8劔Z埜 . zLPPK0R+'\MT寔ItS}H2T巡鞳V$@vV.艢材静Еhw87H蝠(z_<@0諡e豎K)A芙━兵蕣\V盍FT祿Sa祗1R7jR~:F犀{跚&検=0*Hxリ卑舉 E \^ N B:]:5u＾>P賦Y<翡H]=Tf逼磋s衛≪DE`Ycq-泥鯵kk,O状踰7綬q増o+(:`*$ QC -IF0+O,狩鵄H`  脊J以PIxs+>"hua:∩H,閙zf'艀vr査qDX5舶>tlGbL@ESha&dDcq.; =R|7Bt 6 0xglKU夊vU %r4{yg vUgL庭6v介AFｲA@ o[uv(Dル啗E(vS$RUFK槇r1r桓TNVwKVD鬩^M蚋o{;悲%&hY}yDpN(\*〓7a皚Eah M!=9KYK^\sFx@ 叉岩Kwh#3d2H4 z2!L)nJf&齎(1輅'Z hyIZVT TPE j', wf鴿g{6{6割4/:Fz尤TgGy 24j#S-曵'-Zkg cky6VKX=Iu欹(4厘1DRH.:N\Ly%:AN飾?\'}яF@.FA@蓼/TW9絢^,i ^{r/no%OHE沈*4=0 Vu3xG餌髻 P柮iZBP挨\]8廏TPFG蕈站9 I-7N譬概V悚;>02pU^ B]~[b胤i[很{ P! 羹"(%轤∞zOZ/ xk__ 耋~fz?q^4lNarb烈m>A)0n|W簸T炙 t7}?%1'pCqmCzwj%L>eB2 )+AdE耽]N[ ;qciuHAVU'~f嘔 駢請i?Fp in*l_|も滅:千能vV_ d;28\pS>~|DQqRu `rn]|F袢憾lu罰M堆eto4n宥e]Y"^朶I0 4I-1殺k MWTDYY賊n@嬢:朿gcGA1g9.FxJ_(8両| +o穡N_TR0巡i檐岼F -羲l'.aOv_s桔cﾉmGe%W廐3僻_=2.嫋-?蝶k麗rlNF*A3{÷UZ<%>穗藾^[kvtt9{Gマ+隱~筐_)胚)P?=PN穡=.wt/逕:sJKR`x$絨rIcYTlJ/站W贋6W%UWｚ◯*T焙幟O`Pq\?bhZO@sj8x-F巉h}+椽tL至湶GHJ! oJY淙L録tX8M*a+Phw9^B高G)-2k-[|c隙%{6X-Q塁.L竝Ica鞁w奪)gi牋>t3Rxeゲa-⊇u%gCp12.3謀l科0m*C$0;IPkh~=x Ug,ISk頷Гd6k'=ズ<6'>5xd掻Ψ!yvHi/あAv;VS"xbA鬨Oz亢v#aP- Ps*:H"(`)}0Sm8|,9na襭飲H Pvv姆pW絛,1$[|+簷NQ湘V縉広x I t,叱E^Ytioah\K)_T'膺TG4*o隹rl /NV$瀁.y恠Co6凩l&!| SZn滌 |Q控L咥嵌紊2H鶯:繪- T駛圧湘O(ES}0iDstl=B\VDy5o0G 鸚*=l@ShN瘡c讖|=B朗輸^!k'MI}魔 R籏`wW$[ S%t%nA?/3CXH@tj# >~@jｻd9IGd讐f 量WB9L=jl8!=ts~PJ奥僉3*]CTv付淅劼kXfiGUA2衰| 佛QC-wA*#3膺耳2慚*鏤n!}慌'祭P%TK7Tpbh誘eF1)亘=e袙3ag ~aD[;炬\?6DHcH殫κ合?9wy禮鰥_S[8J|i76iq_Dz;%%T噎>,N'8 _囃P=D剤 35 F^xYA OZ=lccB跛U?oegC緊ESeH$.al{5儼}刊!観晉7cWa^嘘v43驛.o虎yd@@`|7R靡@制h WP祝g 3a┗E(@R躰 П$^}oB8xF\ 11O]|_&Ce 攜AUjTN醍Ue59>9RFjy抻Y疆>5#4lr-uRD3Bpa^E網o#犹Z餠闡T凖W|cw }声}'JUS1ﾅｪPKs:vF9k岷\Q2-没 ,8@)痍Nq6&"*).FA@ 2=ggESB 8%S媛d{60Q ,"of^唔3Z JN票孛~`*<&]/Hw齬QcbQ*鉦V m8糞｡|Y~8]2狙b_K)t 7 )vsTa`va-u ;vXqX'Ve#[2v略E/?arSqg鯨}爼-痢Ql4U/MD6o/眄x襯-0~Y;RR`9P d[wd字0衫R[敵亦i#}C_JH難lo]9轆+tMzpwy1X8D*n咬%9rD曵4el_IE;蘇)^莽S濔7Vi&L=-AA荏谺谺Y皓^:R⊂垳v&Es庖1.8垤俘lT'塗iC,VxHnJfs%Y*檗3 %D~+lyM F1P> ？轌\OAM ^!.!U(MA vt i0R_ ^|x6,d胛s搨K/檎GrewR4kjRSg.qnq9:wb彈ab d AJPX<t!室Vago繙"U (EBuF"}y恊BTKMo鵲V鯏~/>Y鰺 =欺~a`#鞣K_US^cAYPA5 _u>M@U\腆A(PTxiｹ+Q泛Lp @I-柘腺p.俐潅f悠.nCL'@N2H#bK!%鮒 藉9wo%!W癪eqw}T声xU$舛z9ZtEd_:^4 Lb P}8WaVPsqeV4ª_=2 B]4鰌 罟T;/<V'裲i,a'L"EU舌P2#wub g1GS]兇D,HXp離:aE92渣 渣櫁O<km柮$U0(j]wMspC)=蜘%"Be&l9憎S( Ko蛯DH!6mxM2&oq#沍_*iB|^ &鏤q *qG檠Tヵδf{L晝~Yi0勿7點0Ddц卷H 5"Ie0q%VI填"L::Kjsk{?8ln葹:c"腐+q曹*El>;V陌` 鈴L#a%(q03sa 2 k(板釉$|ｩ|Q讓諱&o毟7X貞n辛TglX3&s敒c+4j-?g~s箏.广汐yqamFh66Nお大^ b相}QcQ7yRn3蚶o[H][ ∪慌S~do4譴v初I畏bE綻0駅@oTv6)餝I{徂S% \閧/_錨1W1K哥 s雅lv#{*~}==]邃 }S{{8mKXt (0偸*; (0ex?wD?hCB7倏架7 I 3穣w$鑚 c#&g>-rΟuM蓖QilHI厩>屆*i'extqWv憧( Se,@艤S垠7;,幎譬m鮠曵ML埔嬋{綾f4鴒U1AhG恵,=i5dS赭@D,妨<0煬3B衣'k,"鴆Nm24-UV Cc4%]dw%.b1>賃y炳wkIyG e*Q|功#?蛆墺@輕 顔jN Se"髞m]RV 綽穐 祢▽]RY>En剖S]n劉NJIVgt8l?8]忌爆JH爛 /r糾,P  |gw[T^/&:?sAXso莊*$飲+T9E${輳 任7[愕 F 靤#o(uLEBy"X錣 幇TKu殊Ksl餌`>Q8 =^#竍曾貉Naz風A$秒;E?且3W]`w6@^0遁"-Y>9錻AEN"%Yl着戞蝠Qv=]!jTt 蒜4吠l歃r諄;槃'qG∠mg場=魁{rI拔*FIxb.衰=o篌>WSyUrww 矛6l鏐Xul$席Ww 碑;AD0/^I(/ +\CfxS/IDR >:ォ7S柿d*t琶弖Vh驍jL/⇒$~3F∧9Q%BE:Sl(P裃V苜na傾@bK8>MI*0M種SF9侃蚌Z錬#uA,Mq)n]pc Y 圜皰.5@+(陋}X駅vplL&eat縟Lsr?罟#)kJ$樸jiM)UHEHzS7L$池6穿L~G8]俘&8FIjz未GBE=WAuAUt悠[q頼鏖g0_rdV/穀uT盲?i?R2凝 爰(uF x>;u闥偬戛@ZR=g A/\垤|"RH2^IR9bW(c暼 犬笏軽9Ge#杤AF]M`mg >UJ09ihR明&e=痴p*殿k滂JsYZuCZ)S 3qW9v W ( ∬-E1"#s> +E瀘W/jw]鎭Rh$IL恊w%E= bJC{0b}縊Q陀l-53鴟J\H@ooQ男~=n,[AU@$cbguu [qiOчmザ趾6H"Z箱6M+ ;蚌W鹹E瀋)Nq/-FUjRJAP2d~|"VUv%3:J鴪5I琲.+觧\9聞{D餒]疥n;~_x/#h2 ~Yn; 5>B憶妾jp@E-6-r 1l紐U兆DWnS臼r# 岼qffM3E3'周樂.vn{e此:Xx6jp脳`愁^we\LXg宙zc >匆xe1;b0'K{Hs 逎茜畑呂HHC丿N,Kg#P8YY \?xI轌b4Z*_狹捧o饗A"mLDM寇３N*UjIunnQb奥B]gp='K%~NL@IRll Zj櫑{Lz橦\PHr葵G袿慎Jb"AMUq(.,"t沮/Tj i9+`p顕e瀋u{Z痴垓Ki:8淌H9V*S$D#N. 餃吸r榑罠M"A慙銛冬yAyP#j曄[OZa劉LGCuAt'z辟pf8暗 R/A鳬痘@Vbk&a+qJ宦_aLq q\q}ПeS)JXZ欅]wmvL括P2疝A|%3q\|nt) G DO=q殳|](h1It2h Z$g借w釟noj$xs`\w QvzSk浬*[#j蛩C(`YGL*uGf*$fS狆CヤIJ遨 qK, vZ:PTBvAwjK#n肝{DH!t,，趁6CHGU ¢R8aR<" zX ~E_|5=_)6/iV誓WfGﾚ涌3oW煉~c'/闌@:茆CFFpPB裨+ixl4$\粡5酢&\1スbt@\,]瓊/y YNvE吻~ gRWdP*VMn*fqHD裾歇>M,zY G:GR>抵g{ 竏1b |fJh7oQN.勉{([_8N4噐|rh*[%Z_V^;※,Lh!6dE鶴晁rbl>CIcU7 S$`qSSW3↑@そ&W, 弸pbZ莚疥TIuZ(rg結蹠Ts`鼎}V7~Ub蔟薯Mz詈r^ ;点Tを-nﾕ:j4XI9'圓D%uX鯆C[榁&S街D藐rD醉櫁T藏a$C嶬f!酒?-紬z决~4K_侶f需|[泅租of>jy力斐A\-Wet1'UYバ聢鬚瀾C~ dwuEiJLU臨m-梢\潰CG05ZXFУR-8v8ge3艦盟囓m&N=D>TQ10L+^:!` _eGjh3;w?#鵡U8焙{Br6IJ繦p Mg殞vL=De|tt詢頤RV 數e_輌K,WUFMif&\+1喫o<>|uLWrK=W*波q;)LPs 困 P5莉ts9L塰23i\XV&@}3u(|%脱羇\fG"\律江&h8NavaaLQ闌4Nr+JC7e)>珥{jgIemC 0OEf蛋yV*;9燉itЕS#vvfX PqEQ弩6K(8L朴H 6w曹D"k$|;傭&,ViR P<n鷲般L8iN:#r\(xt滝 La0隋A万,ba袵KE3I恫 態&U脼A{jcxxb艢J'sl8惶4U騙\lv1[u[懦04o&G4T{濳詁Cv~>hFRSc$V斤nF.h冬mmV#"ERミ"Q8d'YN化慎憔n&h1B47mbu t筮oc 2鋤yCqulIif SGazc g'端請畧y黻Y< : 0k ?"lGoU L暢J2WP_ZD%Vp0Y斌; 廖-D8{9(鼬;>_{Cd勾(Id$\)探Se)B找%0T ;{Ntb|y* 孛係神;[部}R2(蘗槃)毋tz将酥#x14Y [ｸ_Qkt〈a:%Ｇ侘/s#8 Pr&Hh(FEBx扉鷹,"G#SMo5/2翆_p 沼 ITN$Nc}}C6D eF %8OtS `Kp鞜挌l場O^\},燧u4檸D&RXa2R/ s(M$g以%携@~0e郎d >U謦n' 状 8足c2X" G9H(驢fqk}l 衍爪J\kXR鰓Ze/DAゲ?1[w饅w-嶌{)FWSsk鞐CH*akuE8n vC灑w-1\AED^kO玄_ W敖8樵!6 8LN]孝~A+I9+Iぉ}d膿 T &_A胆IN q穽鱚隣VG3VPおo布Y^:Z;g}6wklmm沒f＋2fy崕_D島l ^ZoZ/u|=_b髮Arﾚ薹$ |繍m6P9:r^. \鬱迴k祟0;h*I#q宕[%{舵PM ` _~K顛u鸛l]:QM%%k泳k徨6乗礑.~圍/n9K朖塘*+;)+P;~o捧n.Ky$渦塾I*9{se}閭b^d 隔_笊EU妄=r息$-k/市e[zT!QiKe T抉荵a,A?^臼{;ity)遭c<156(Va9q& R>!l[5*$气gF膝慄Hadsv6O.n9m板絢@&S(2'$['蒸z冓釆=仮脇_gsm58陛IWXu亂|CizYOg ^荊L4- X1%3r畉u u@kx♂葹墻(}Gi(:vlmｖ 帛>? f .#鮮/焼x B!'5uA朏(k逧$粲5N* \YxVs=LRm堰JFP7碧S,!\G.e* 1(3b:澂i小HV=紂=D6VD=w$RhD'峰ox茶&27C瘴醐-.R6鄭瑾XjV淇uq=惙;4F枢梢歔'v<}蚶s葯L茉}w籃T[眸殖i7搭RJ%p!_0 .g*81v4z]K)gBxJCkap竏F.JQt&}*Q黯p膰P*~Y|M3*斛嘴彦 ;N谷mmc}？N:*+笹殘v>I:N1^~VAu7?ｸr6覦謇GF港陏4+贍擽=犢U-C:KWE[D?$/,R,b,∫亞676;IwNZE 蕋 Jv妨G1g;fliouT ;uqG9s翁wYo]輅;v阮嶽uR魍洞KSAd('NTG#41Oct旋:a 叮i}L+yV!Qg723諍}*B 檐?pc=Pj#{蹌毘UF l歌曾.T)FA FRg#<;15絎矜dZct鯡浣-B?兎Kb 8瞋f0 Fc4*0 :'8T&~=,H&*A胚C‘B.L濕#4F;wQ_Se"1J"MD[巡[Q汗ち#G蜚S X)@権vUm逶*j苫hb{0c賎井|/p勒i+1[e' |j=閤趨;|專39炯\y狙宣K巽劔C爾Rng-+!(R6>\ <1= #~&fUTS2U>*Q輾"Yヽ;Wa iw(-K騾ｊ%}妲勵!6'2U緜奧gg>=b警\%鄰a5{D斛┫yv寺i|v23 雖3HQ0z|iw*PD佩<8$EN&#c磬'im碌 鐇%a儘|zA遂p2pZ坩`@<毆W曩p.淋+楔4駸3_疵+EH t0=N`xхaPz獸zB+UiP y〉FYhn詔Y突嬰.zs\LJ]篭%x<'烈o|」}O坩;M;K/茆妙#R%hrkv>N髦b+,%N n壞M|!翰羮ZG遡gO3_櫟]迪!Qf%o[)!n){yK銑7(g ﾎde }&w0b麋.[y蜒lIfXo $"5SA^鯱t q崋? %%嘉ハ氓DwrX!寮Iqa~梼拷.)W-,=Rp┫hb SQ9j@YA`5^ WD托鷸k@Gb 80+p旭G沒hNoIb MNdLIq裨1(?(C6ci6OiW!門[@翁u儖n@;knc(JF3=jvK+領SrJA4+^-{'{` =0]RO,:kgy跡cv搭yEq;U襖7qM!T~榻~j_M>u%xq)峺?曳J:{r $囗疂 BtZ闡oA]岻s6>f`")97j+企滄5amgu !f)脛Q -оp瓧`T%B感3>NOY殺Ix7~%^;01>0蓆恭O畸jl2 hRJAF+Vd2kjJ車*tj=ZzmK_8勿a51J:4BN寃迸WA録*~K?Ln4/Q `衒企12d]4K2.G" XD-)3o3妥6縹^l肌\5 "64SNw?}丞8]毎bK5 0|cRt毓N靫%f"-LPLg%種)k妲Qrrq4l f枡\@lB潛"翆[;>s:H覿CW}%o.N[7q\$TH脩T^.~楾E&8bX9RX*}Y B*TJe$f図J7Yput@:Kc緘 贓_ 曄oC|S淘6]7~ 7o\y:9櫺蘇6aUjlhyp震QGZG|照鱚1)lD}_''Ya64烋D込 胄?l裡oe5燼0膈c9^后(K箸~n跂Kw纂鑾激CFoBPNC続+U儕~[#t ∀*!遉l`補BU?u_ta兇=&#E& Ga6O,犂q茴岌0=xlｷ~<  |3Df涸`w kD腰/Lb_S4A-Q鐇m脯M#捷0_`py<}u+{┬dA壷N.A俔w{aYzr_{{][卜蔽jS(鸛鏈*j.剄締+M '\茶khyJ"MLI5\#Fkyh< a櫚G蒟$Q渾iLa繆x 晴Sq#1PoqTCQ0弥`pm革xQzZ矜`@c_駑,5 kc滞07-NR_y01|u拓38瞠3S樺4m>+s瘰|A'(9 陲剄wA%佰臘|  di{.2 o^.怛N寨賃蛭×q形v:c<|迪%Zлihll;_|鵈凩d^';難WUU0.躓蚫躊, C ^~Ra:MS8特灌WB$k'君zk黨n槎?况u~tJywy8柝xEHx$rkO茲5[帆R璽 $meN{I|a落蚤@@G潅d糺] RI\2 旌Y蛭i\Wｭx鉉Q&1}爨%2"q%H{8uJ?|V癩n_咎.pW窒a(JY觀z*Zt8"_*颱瓧雰o\T$^Y}蒔m諏Ef'耘M控7 r NC&s!%?qSY谺S~_剛!l剴ｪ!膳+耡g7dlSpD岸性R箒o 5j鵈_6A蚓紕'uf騎W壞1;l杁S8=d%m蹙售g"p擒$Y樓ﾃB>}"6._nk前壱r象waXcYb|^u譟-:W *迢d 3倔&]N3Mre沚x6懈F'm漣Mv =m JcE揚;跡mS.α|h楠6LJ李GAg5t哢Cnvd7 ] ~成抓&w砌黻mtCW|?裼明 鏐mRcui}eQ恤擇36U 封`Sv4!悪!fMNvg辣_RL_luTl"W|c!lK被Rgv-廈=R舶 W~+{P}G3K`4D:K *N:@漆r02XFr實PGY]l梁$黐Qzr風9fY!Lx棒hwo,塗G:DJ@送KiSR4O宜救z ]3{x`}燔K QWＤt\{\k返磯"荻鵈庭莎&礪Q:jl; 1g'_1t;3iE,"'OZKqH\指>cLl!:ArByN6斥d B+ }Y7,Q際-工-WVIq）X KT緤n@-u渤ｪRXP{琴cG-G._5]R~N5x両GQ痺{羅+k 俳G[Gj鷯}#茆漱`傅黏Q0A擶;遥莽74}Fx(9FH$4p鹿V55>x愀5飛*<tzjSGc q*笙I'ut 錨swNgE;(8iRz%I挿K/{CQK{~i碎#yEa-Eh O0IEV#?Ad=#|H耽(3瀛^+.IG7&pR1fMf'Y5鞅c瘴p(9K ={;228茆圻 U鰲jTqTO 3Hu蹶][)AS狼腥*嗁以){/I .Y_5心0l暎rTΙgYY &:9J潮Zpy{赳~fPlkICPT@l*= 継a憑堰 8`2苦違Ih誣泗吶H]LjIa畤:a?YXむa星ﾌ^,鴇Q0;Gn*鷦1p８+a2^'涛)/!瓱C租*ofaN縉i*tV宛誥W橿O)utE(絳39/Y5dY"3j)0#*f遊延m^}恂#\ #g4COＮ JC潦D)HSr嚶L.XRJi鋒q+ニP.惴i<椅Dm郤#5 }R ZK瓏#垂>U%>#g}$K7%@"夘?4n麋+?2重4r 滋 教Ws,+2damKG咢}CR Z5紿eUrIe$Pab ='brT_0HE5.8NYzCj宙捜 .CX7選l}?弾 h=9k ^(5Ut円4447_38 囎m体s)[3cF< ^&!標V:;k\1jAZ労靉e}b=e%泓[)y$3E3唄1x畄%瑪N $k0?逆Si駲G;0Yof1Eh*徙sd) 宅r}<`縄.q獣+d鉢>mvL"P#w =馘VO鵯杖- Y_{9>Wpu嚮$9YGSE綽YK#ag鍾髫o域*He gBハh)Aq;1 羈olユc{UCT.-na櫑磐{:! .1〈br裕W9Ae .JD+Tu!d{uJ>u *V=;5/恰G0朗X1霈8:く}y斡*w_覗qjOuYp..民鎮9A娃0Y司 愨錏 KY@}佃t絛EЕM粫. |H 厨:G.#j pTwP鞋W初* 冉粧Ch\]("hC'j縷*Ut眸托,\{玄q[$k^`K=.汽m驚@D回回:Y22*iYK&15@畝錙\洪|;纒Egz笂y煖-jJ$'G熊7D[悗Ci檀W)pf衡lo劣羌Xl`坩qJ幼/]<~cu?{槭0簒P#mK蓑$XAWN:りf更H%P2F ms.JJ$蚶f?Symkl-n[}r~pz: gM嫩隋mf F)aX繊6蝓6nmlhF侈P+v}u怎1肆熨95-%}o棊燃^;7常&_515*Dwl?~蠡s澆毟 u9jn7U聊jV7qY威<\A/w 牒#\<)1B堋匼P;K迎Z籍 k=\cuEs qafWnn"攀,n窿CbO金2F,23xJ2R|n(cbRR}C}Scn峩Ζ共fd]#G\Umj屑U県hs喫漯ge<峭]Y插}t w瓦lg{蹴-7.$Fw鑑(]VRU}JQ6.租mИF#!v餾:WfRj|i(b;o糧{z,)u H!gOT疥+像)gI-BSE7g90矩{服縉捲環he8 Eo`Z 7Hba1XjELCqS~rC&鎗0XY0t""樛L B碪.ｻHa8.T0UR &g3QZ!彁tE.)}迅洙皿&廂彪hIEp.77祉f漬Kt樅fCn虞K\"~<傅nQ OZ' \r嶮)oaH?錦剏呰r ~漿>oK~厄筧x~2|.嚊 C]oK齪w5Jn_gF^涛?科(H江&藐r( OM飯GU齢70A◎-.|4@喇篆?MZ$vo?_/}s艝B↑X嗷Isb妍c褸'8橿藁乍-^,3yygIuo6I4 %+ ?+茜,xii=Tb敬m fAT@鄲K2H廼T鰥-( 靴佇;黯v|y'訣4 ;>P至鳫.樂b]o`hts>こp苻Z3 o GXOxyp0Zt轜7>:3Tv8jв蜉6WUO{_UU95Gk]?xtMOZ2ki顯躄R`*r痘騾Z:,{lA}s&W$WL<Μ9淺ｻdhy= ^3 9'〕 P:r%%8箴椣S2XwW鰥oSv[(u溝焦致0瓣l+黔u\XV韶湲H- 伊.u^>s/Nv X]@滸徘N辞C 娠杢V刧鶯viITU"3s '畤W#X>薙M8:5o噛)興VZzNbE 麿nf{EV\RR`UYPO*`U:檜k\逼(耕P赭ChWh.I腹ぺS脈掵于k3\630b>qY儡勾埀+i 擇Mh蝶_w f(x賍/\量統+/X_LR] 撹LiQ1逖F[!Op館OE\<d)^.J`h_)3lPﾓ@遒剪e[曰kS0麺l]dy}濘q霹:C=&}pa6霆%濟愚戯罌術G&咋zW 71涼Ub冲J?f俘s:9衒]I迥偏珠:| T'Ν蟾*;;z/^蜜G0$n{余柏 O(%%T9,{_M緻1|Y蔔pt I!*(毘{巉氐 f9&I植Z騨Q]]=]!Db9材援痿A'同jC7K*d0jO!qGHfJlf幌q*k^NEL4 謎p祿P#maGtX苙f3[-YF觀9&淋N"LFa;`hq z{2兔 殯ya$蜥轂`a嶌uK}艟1<3W"GH3盧} 邇\_4Gi%o1tX5~#@ Wv駁C}=c窈5Gg両q蛟f !KF^僊 !i7!|黷7e^.寶fHKUa SJCdm]&+:+]_Od桝V?:P e@D\澱Gx[9YX'◆4ssyW蓖QAsgY莞;vp4ｄ/.OR7->2 Sp變=x5TZ芒* py m&閏vN閤y嫦+=徂濮子',H C籃蕷hJZ\u|x)滝/S{嗾i 戰羶ｾYRpKo"@9;$BIYq=w-`夛EB詣"tJo}M(Gw o竰-yXm鞦DdUm町PZy=6懽圉jU[h,owP Nsk圈ｍl*?;`m辞Z/th發4憊X\4荒p(駭饑M?khy`8G砧 羚%2膺印%_I肓黒n+aOグ-;6&2悒 =9碾W=!Dz?氛D%s7D戻9}揉l`rPХ|di啅M[Z螻iX=<@{鞣{Seo遽O棉L+`RKn@3yne2窃}[.-0x)飮8局_鵈}IQ65MG>Y~bZB%(L歔zyEKJP2s }髭*)gx%島=J&A湫=CUt;b0>.Ne['$駘`5Y胼3H撻R^辻kG7DS $#b*窃v5U工gXO/E}枌 ∝Vxz蜉=槍q炙丑伺9`線ak`夂菎E択cD翠ZoSvwMq(鹹2_鰺",{s}eLg龠K%k<@陦SpUY}3=b9O挽{y0>z捧>sz ^FRi濫' Sx峇 -萓V5-縁 ";O0=`L7hw(Rl{V=1;y殷/S]Q種_K]d#CEA"`NyU浚.睨|g$椋U[ <B`C<奢泰9!w.爲Cp f[- *D 差3./o6ZcDa#瘢UaN 誣bRy燉J窒s r=埣x.<_> 旅R^竇~%卍0H続tC)X 袁N`gl漲W!B耆8$Bv9}i┓oQ*Jma jpC/矍hCs嗤RoVPq*3おh團 |qi6t釛!$2ID~ u&Bm{駑%潴{bb MAc>#iT]敍)y o#Z.J]5CuU+ 姻5}錬メr$PUsM+盟)丙ZFC, $6(P*朗a司Xp+}5q!ズ谿& 桿梺慎; vD>7[ Y捍K7%JE|v;7RA7IZ&8 ~.5b/獪tzS rT4鵈sEL59_tд!W霪!0Z罫uI7,.$f宜'\kKj6C%l挨^J^X 袱 郤 UzOO2睿MDs拈.-bv%+o\價vv$U.{腔)4EY*}蚯4M<侭nz杉P1e7twNvGG矇\O|_KCakp[@~f義炳%Y君]Tn#+鏗|閧^澗D-?%哨鶯F%澂 +a涅_惆T1牙脣~579綯*;2!&|RKzes]! kBJBO韃 %]0ehSUV Y*.= pfVup[a XqS淫NI齧YB差JeCW'LDe胥5Z<:擺5C\6V$(dXWf$WM5^\0R本}e衾礒v1~iyY塊]RY箙,@gb82wHm%.="嬋-  m~#i釵v(%=g$条[m5ь 晰jKnZLcBra航W7J私 'GA05六T"\ ,甍BF(0~1闍{ 慙|/#W\^}N{lt篳P~- %WrRc 母<0歔Yl域齧h> =1b=*;<]6R]K9uLk滸i[征,.M咢d濔#{{m3So>mfT喪8`「A3^Gu_yR罔隲";$I祝魅P, [麈@E'珂QWva罹QMD*菻TY寄0T2[0 #竟z*塘$首S躾<尼粡hErk恟}ta凅Bdf&稙頷2(X1靴/MYv@]Q<癶#:n(dd1弱I)))6Ojir=:)dXy收/b@2舩E卻$1h幸AA緘q).P猿%m執j^+臑i7';h~q1c L^ (y+=)抻 :鐇Do没捧H \M腫v輛Qw2 Pe蜉` H NI208wK嗾uGd=-衒=u鬱=zV=S[OZT|V~w閔 W`扈雛笵|?4ttXd*栂B>]r 氾昨#侠"餡|^& 倡~IL覇)UYa販k蔵jｰh脱`悒Q倨8T^RFT:exeB< 羅П.ﾇj{N|%/=3芯]?Bj峺5\`1r0ybU笆煮f4Ba%0 i8\xd邁+E莪V:3De?o(mEK ]Yw8Yr艚W課aW遙A斷E番李奸(i&{惱 6DP哢^OY:SZI慎\[蛉Y$:)aP汐! 腫En4(}*鳴Xk廣U衽昂oc壓纏w0A2M[F${框`*.w?94{.]:sXmNT慓@v6Nbつ練幻8(KF7L,3llZ虹&p萄A>Y,;2:p)H慯0_wL呻,C4阪lP1xZJあ)UMo緻[5/-myX撤劇F}m糯8M:bEgJ@癖U~U/d 逖NGb鷯;fiw搾k//余 &R yY璽.9mwGY 胡ﾊZGn|UJ|4{gPH嶐u(轌$疇6g 臻/<= `s6j6(玩0l豹_唐蝦6xJ 技羊j頭宜SOgK:{拂X詳a,G悔ma? ]+ tl7j-+0嫖j改滿V爻+y肋よ6_{_Nmdoht添s鏘v閔Lc皐k]5鵲r"]nsuq-臠B它q]vE T峭TdU@!#U3Brc-6_Z全F}稽b;*|G0<&:K8慍I Az覓倚 ='[Y囲{;,Q8[eH ;2cH-B苗15.Kf3jBm甼pf)U-r蕨 ?O9j餌L=鵠麾l簇陶 夬H}KY@)MＷBq2%}~咏凌fa睹H<,?Q:]9]j(Q渦#_r@2sI茖1' 9 赫5*_淺\P%]XVsa%A"%IZq←RmT&7!{z|hM6〜$素駟d8l0/褞h&H|(JrF8.EPN6{禅;OCwN艶8, cx鼕DNj%V%R0靈T,j?堋c,4R{Wcz7#\MRAl桝?iIi慥5KBn;H穂}0#lS}%AjE絨Jfa#F旒&LA?TQ77* \E*哩r厳p"丙|M/X粢|E恫司l:m6]H湟+{神┳s-儉vh}#mJ hw6Pnt陷e);x如\x 尭;B >An$umgo:/拉/To/H"$!+!H捏ce'@i+DD*db^)MnfTfk{y;矚r埠 vz=ISHv_!r! 佐(!,XQ"uSg\:剌E"ダKz6fTV‐`C饋az截ip猥=寅="L,0衢t篶虍埖-lc鮟z)蚌N+PS J5完憧b(瑚2S邊EVezZ3+(Dz3:W =#號y犯 H#K GS%鍍詑M;穩^iC忍@* 7;w^Ry5 G2M[転wH籥*慓JSml=[O^y=襍eP(?]+恨a%{A-"h !Q嫡;n_柴Q7K為!)&@S鋏3gF芻_=e囘M0蜀7樌Kt+<冏daIk25a%LMtv,憐Ry"D\毆稼,,cB醗a??(zf$=\[埀T-菩Ｂq\２pv[B9&d^Ao簓,XrlG脯魁W!^4lXゑZ&VT,7娜_3("'"qLZ%}@譯Ca3 f孔勝卿>〃*C9 b54U{閲UiUuUu1x9幀Ty,1影炮墾j阨tV6孕Q<[]UWWW]9-螽螽F4gWZ}m= bAikta,a寳-Ki1f(Z 霜Q 7 n[ ~E6 ?Op^2柴Dtl減喙竃尭k銷汢6泓菫'd`(54&Ksy杵x6 _8騁[ Qb!"==5 #)況F7,zｼ vU喰;q g 購EL醇2q4臚轤$GXUsA|3糞ﾚy飭83t餠棹I*1鏤繿NXu勅82]辧(r8殘n\純"_I0R諤\ l>9/zШF叟^始T5DO') 醢4M搬Y(#2mr CB*D鼻揆d(|>R,qS(!=y7cЯ@{euUd釿VJDQMad\膨e|Lgljy{:鷯EゐK$NLhP;(雅&\:聊$$t0I樛CaH%&l\i-2.;%m6n\Blyse疣fLB約Y閲赫bb=k6單?e娃_a hbuf九*f懊Ax~e賻xF:讀D狄WH殃4$MU{w7H k聟DB鷁揆%訝∀-7ぢt@lHN$,<VI5鴃9SnR{o侶a9P^$tSXlを{zo戍 迩*_&wJ|zQaty zM奚&抜1釣 S]$捍-D-很 o疸oHQ鷄P錙榱Ngd<R土舁aq湮:y: 2v嫣ce+ef詆t8m;Zfvm良a B7n=4wUdK濛x lykX@olw夛誌+KN耒IW.v Gz Q洒箙帆T2RhÅ靫徂4炮S6A#mq3|I|根mw-# _u渦 x&TAq旒望@qXm;D^uDm*^'VJ<0亡b&壺^Ro5候mJjG劬7X"*ovb盲*Z)殃0zn:OLRz&仔4|bv=x嗹orSf忘Il}.wz冉hZM]U/pseUXn甘Nuq'@Tl &輪N6-紐L%Lb`Yc[nky+P>fK~恪ﾞ胴tzy{s^+;Ib$d諸亭 m幣D<ｼ8鮠_TSL]ゐe_#sdL%)t"E偸a"7副:& "p$J&H[うH復aU" 瀕蟶g厦淌h%QNw蓿?dM謗K_q0D8/T銚cdA鎧oY 2!%披sHt1 %[2謝)史K^yn:P}<,1,川{88F7'FRDmAsDj擅")◯q-=v{BQZ-&pDv鬯尤'b)9鰐岡<3?8EK;Sqﾋ *,lJ}`;xLL5; ∝;[括/dHm.+/2窖+N慴6鰾`51f邀b:j}霹'FFF龠x9S?黼H` ?Tu) ~pTD{HD 喝![嫺 v?6染鞦y}x沿緡}&t;ExI dxnI峠f)s\5SホP} ^lLz@;莇4 °Q(  帑N歸.2-g= >??JEFBz7蝪]7邏@` AWv?cu c|#4eH蝪 \ne 冲瑤 )@X? 45"fLepmOk/<@}-D 8 :g}/>xれW]f/寧瘴nawh^E瀛3r#HX-Cf!WmB cg荳p 卮^}#U同/q:倣AiA茣?^-?祿(q'|!繞嘔/I"J A孀 >*+i]n{%8^j(7zvXZdApP0 "=T鉦9@1dzSNI|5Ft7%"TNう-Ｚ<|1EM!{ 括n%&LYrp寃湯>X謾RY:<6檐=aN=GS歸t_麿Q$6H放D5B;i4 P停CD,mS栂)s悵<3/K;>霏加`_淮9  茉#QN@s )"d僖#UP2MK鍵01x ^G近8n%C B8@0贈 E8tr懦aGE 轜n愈GJ1r暢!\YQI!\5絲叡mA崩owRF-e 軽-3&E2｢#v榛=鵈 謌Zw}4eM8. }A孑Xf&r/逝喝璃A Б z馴1KWU0&I愉Z; AM2+%B] uRvk_$攵dh(Q*D*jVA櫻bIW. 暢 C(c3-N9M灰 #3bA}!qL3uy髣\2F%aiD尽>抱譲5\1 D^HDFI.K95\饉R腺#)Zw罸u_R[晏喞 k驫QR択CiSw第?YSc*鯒p巵b騏ZLa_WF凸C韈-疼躪/xDo錣a販p)Xx|m痃Pt肱椅FaIJxx帯5L竍8Z嬋K局G鯰?O+y_ADO4soc炒fYEp3欖A+pD槎BfZB'*;&#S>5rwSbK翌+Nu~ &+U' H掫b*8ma7期Z3rk%l跚]奠ZIJmm哇R絞3T2gz Ht佗>{ЛO柚T1\I獸\y*-j'-]ぱ,~吭)_?_IiW4黎з/Tyt5觧~+xDg7秧Ш43 殯Bq4JBa>Sj~z%L ~eEI',-dL9%p|=~+m{u#Qt-Wc(5Cig警r~b#彬<;霪蟠5'-\C ;wBGtZa %<(蹇Bgel#s袰仂コWF9o拐{wjだ 觴=b嫉`WijvL`Hd館"Υ|.%舜!A,R框D[{pV{pQpvuY釦迦'耒 Wk鬆 pu6贈jVx偉 /a３;f/a2, R臥5dgM2e[Sj>x惧件BcZEY抗'v}降!雍w喋 SP/C|g挨鵯7項m)U.XrevgokY&H!qLjp+_|A"轗;:zq[z6{v挿^ov鉞 區z/m蝿獻fH 担_>r5XM/g/;4丑爾7 y*&%9 ar可}{ 嵒櫞d6` akG慧m ;囲ko,鶤iK更淦[^hfrinM4IK; Pr9INf\HｨkccPQQD?颶u]~堙J\OTX睡丞=g&m拇Z;赦\.j\ 珸m#(pn J`Fw盻+v墮>m貍vZI%b&%}R薛*M7X K8#Z繪x,栃cW伸7`@潜<+{noBD^J)/F絮澎 ;猪Kjk2E惷儿G9K|1蒹[v 8Iて,V靨< 7Вz固. i釉総dI@x|WwXq煖 ;g#涸染^1#@恥-nZ'蘢x`雙笆登/N,Q!xyb}k!|She矚l聲Blw?R程nVdMeXt記t"t`3xi /&;繙2\B!澂7)諄"氣`a hhcK^euSi悴Dｼrb懶U_R諡nWp ccN54}孅cZV7rdSN+t`竦A鉗vt|y/"i[[#S1~na$:;EAbI7QQ瘴xF p %RGMT`R;釜Hrr葺95o '>'XE<掩 R) %t Q候i bsN狐Y9聘\]Yz6麻n I!揀 2a.m粍P,務 鐶_+b<-藐)B髭大N996+｡tL,FHXZ%L卍uv8>g xy-F;Av喙z=}D 波Ay悶cZX上` E{公9l縅ob0U遺k\褪兀"Q綯荏0$RwfJо/Cg GdT5U%,IK CW?q嚠g:?F3X e]$n袁聾J^ 寇圦hb#sN>Z.c^ 'CIcr3;WS3孀5:b8x柚熊g)1MK;t氏M磯PyZ4妊>irp區{1Z}2lrYT 繊醲g咆uT槿 "'}(憐TBPAbxp~E?芭3IQ~|縺Q;A=e'Eg址frp渓3AHz_z`EwEFf3鐘dc J)Qg|#cLM瘡[3 6D#ユM;6=G_3WyX 'J.+;A劃tGQ~肪Y借 po1Bx]ﾗR1=1k1阡UW -)>(?Z蝣徘\~KA貽Z*黥#IfB_員}f鄲=1叢]筬E"bgO.m狸$y!倖靡qs@>?XTpX-@嶇]~Q&DMt荏jS%py灌FV!!}Rg ~}{n/BD)Qz?D|7祀Q $ X蛙^駕Sz灑3励蜍S'仔o ! ThP?Ik|>CfCNlD鮒'L 衾 qsВ@eafP^帥3#2NM厩UFTYrWxWS~藤i~諚Wg(Vpb_4DBhx%痺fn'澹&虜\9塢%b3h樹B塗wH ,蹠惴,FPw3Y$0[徴, 盆炸Ab,)V^&続GJ苔?Ι'5acf,F9U4カy+/qgU'吼鶏HZ(偉Δb沼r>f貸TF4畍B^<egT.\逃海*工ax]R衲<２Y旅v"胴i3掌 j?剞納9+e QE奚\" g帝K]詐@_濘{`%XB洪2:k(+>>(糅QMyGH癡別{ }i9)JK∽a>pC珪lR* *=,pTi2蝠U佗2HaHt0Yl+b 7PG瞎 Nwjw 衡 iD*'e\z2x崘a~&Ka縡H<7|#鮎Ool,'Y怐寞Ce腕董･tU\E/v]<+勝n 該6[*劬Bﾏrj 蝿控90:見D宰務5n研棟_b Ukor"今i)Z \t4%W^q旗瘻R-Jq|9鰒<鰮ｰ履$ji必譬6OUEH梯B8xEx)k}X m_LE&幄#_-vRqわ/(Y淋吉~glC.$順 W(蟀K3占mJf訝To42t鑑描 @j}%E耐R3j迂-c0ou(8R*寵b蒻 ┯遘8Ql業EIIf3 K+5鯖;"登Gd-N%Qj鮴L<60 ]Cb楜嘸咫wu@ dFЧK@霙\煕Z9=鴛j5L` Ph禿]/&宙}Kezp!a i利蹌rCwg0寒8hV#,_}!7i,_勘Ge/$GB*害YRl06+? TL蚰Bs1"R 斷Kl0{#CW\WV8d"獸`I K@'DLャ0Q無艢昃*JWHyCcW-y@I〉Vy318eS, *|XfC{::a/4=N汪紗y!9槹0#0^O L1U+4F^ ~Fmcηe$h`"Kefh顛8kb估(Iel7\2=>60KrOLぉ I忰tmK:秬b-漬@泄\r?iタzjM醗] 絮吐 E%;u5EQBb$^]xBaf 1cz枳] $C{cIK:x`昇`S樣/_盍fR&[ _)T0! c\AC)Ui'&@mZo銭矣 6n:gaT&&A>I鮹Vi@4io3O#Y #寉r駢）wl[#qts,VДi/窃淅l`J]F3B菽W3\っ##Ｃ/ 芬b凝vs晞(@~BNQOE}p QP8=Zy閂b%些垢]j,蔀1?!a垂釵;釧9lM>cF瓱1<|_ ,$'嵬VZL@ yS隹>1狙{i?!gjlJ鐸Y≫"淺n3Rbe4&Cg1Mt`4 /K&R|屮 6£X 『現K#8槿蔓登茅(|hdOva嫁o抑\:kl籏Q.f6e w鈑ぅ_擠qE悗Jqq1E]囀^(%契E9|d硯+\HDXch. SJ @>@c +E熙k/QgPH群dREwf"m7:彼3R艢z]寔Fphp{y*熹g糾ねト3 沫\4ma4; y疉#鈞iWA恤xyXkPP;5縮GY }M@^n o\真1 ;=y<嚆2EAul'的躬tl3QB烝SG>`籔q,Y槧x"9驪353J梛fHK"zr2rW7fK r(CB9dQjdbVM衫B"pu TyMsw2鏝v帽wSG.G垸ユbhFo%&S$LM _斬/戊kY疎d0pa_榕tt=g5^=掉&IﾙZ<ReW\l@攤$O~p j∇C 誼.o@C }gx7|y奄(^惇?I@?%Tlrij!め悗5Y,?潭 $ZW0BoW(,c8%r_)j P5f)i 4窩^E@3"&経狼0πRp/R +Z?7 抂 2蜍塀QCa/=t^!ピ>mH%#y]KeBX]ry橄* T´猗W%2X菜L 姙C=->I誉-RzV=c^遉祀翌[~椋餮zXX蔑NNd疎/薮)卩'-i* )c"魃xccCga-*>@4(碕A/V%z晁uΟ賭%Z忌19京K滌<4X"D 5Yi/*!acQjd%Tcy4\豊6p^b灸]%\]\.愛-J6e会*}By墜 窯オ沫([ 潤i4_牌el/{,_0f 俵桙>6臉h溥 sr-+xQY浴1ipzHQ 8bHg寇穩N Z9o17}_M驟Qqrλ3_f9 堝f楢y(X<簀( ;&煬i{ 'aw鵐2覊b餬|I5!&v}Jcz狢躓m5蕎餮B炯>^um3柮3#Eep 疊HSQ!_w`&^>語~co;zkeg9繧o褥O聘rgo/剰OE;u麟Om.U97_ZF剿/~[{)H~<|*噴DU*~6<Wﾞ＋!Bd纓x餤SJw4c%‐*s泰U/}{剽w;25|築U!@涙 :>~冨陌6*e.b7髣H||e&_R /應駁]?縅J絨hn∧ L+抄7Fq*4Xco_<z武p鎚衝JV/b料Q nF7a{np9皐_朿嵳K東v7uZ4５\!z[騨LR0esNr.X靈N&|K@$ |$M 函跟6Ye'J+_9Fc>43駄0B0iR`SRO$UE諤W5Y盗1X/GiM(蝟L(cJ),+qf%&鈇6[仁@!# :G爛M){KH\蛋9! 9Go〃峪■ 57ZBz|.Ps, 4-BC孕tUMMj ?PW +鑛*e=]9_\Xw=,$"~ z@(I(|詮XEΔ#N.AR\郛忿f3jT%'H1s# EnFl腦2H歉6K{G;H峩,\贓07^~19費]烽fj6{磋0w闔発^]Xe鉱)Wn斃隘 lr\于温語gMj#rox螽除biIsvU&~3縦満N蹊BE寧yD登lb2礁筝篁mt_G [{|招t宝f弁t誨9kM 遠懽Tx3CW!Q袗Aq]p~c>[悋W?t$</[yИm隶 L2卩(< v v區5詑L尽卍&蛸Yk1>% 袮7Q.─W Y~C0ｯz魍rV箘zk\j}{JW]GR+v成uUU =R{=u掩゛}>{ CZ E<9paJdf-b萓bd 6))ym<俵zH弁ck+G]}Y~_[zd釛}nKgm%%Wa[qV廨o%Br 慰泗8M枹Dp祢'鑼G8`栖d 4檜累K#?jd妣AD8zNIOGS3巻T_LxRJmv[>f:VKZ貍含,叉=I羞o7n!名`V|(A0)U9v#%ji!;n葛!1楫>U抑8裘峭Rz-Ym鵑寡=3嫋;膨6q21掾`;'{2歟mW氈;[Q|u> t+ 汽娟UI逅"Aaz6W 嫂.z祓c~eim7T7舗箕誶om~S材!#,:u/,0 |灸鐘iu `拊_Qk!"H5xoK;?]RE8S>0"3r?,在.]Z)*6鑞瞥PG捏%盤 ^J'A;Q棟cmp )@繍阪転Z|懐-|緊獻+x1Js V4７-`鐡.]{6zb!4xZkZuzqn;P墸4%30euby1F錬jw漾Qsz5eGr7@/狆xu|磽諏LeU@丑'w榑TZR搏W%# 療Nr0: +O k55^Bs2束s*奩oU724辟( ?EP 槿3pf6*8.7rH!u{nzH 膺[僻?拊Uh}&eb|v xX'湶PlH{>+ l圜?縫 >,1Y謄5*IV紡^羇湮m,p}b_)泛忖5ﾕL+k(舉m5y/忖Avm=[r6嗔A艾V柔 w闕t]處tD山w糘萩T檗#.xS蜚*D~O働)&T?A*廓rulo_}匈Hg愼O必(2uhcCss8Hd嶼Rmlr08J発u-8XuRUW瀲P_a&#蜘%+6lN參笋fjj q0澆輳J{sYl )嗹X_柢樅-u虚M詰b龝EkQg3Q\忤墮壜4忖5嶐Qg院H.R774k偶?YA 撮]術殞^肩A\_ }PD}h$I^0\rUs+U&VXX潼6曼xeW;廈>ij蛾K~P`集[l^}2Z 拘蠏蛟L#ui-H機5 PuJ廁7^e&蚕koi聽h)*31σ$f1皋wV8w釐=op``@l2;^]i>V'}U挟寒i顆L*瑣<3災縲%o)}"k眄h*9V%@壜妣Soo4WI6niGS#ω4cWg`時桙Ъh謚4ZC-%e@Q2 kAoSp称蝨V$鴦nx[脊@冽）鷁>]ｭ*(戳EEF7#VqdEOYkb3_o4kdU@:2[{藉uY*梛!I売U泓k快z<窟p[D[彪臠'Ok!舩 F$0nQjwi _yZРt=-5lE狹{創餠跟l tSJ.信&.1*i8*(7!5-Y@稜^=]k(|ah7 `勘i[]c(+CPPoSi"y>l抽ZR鯲WDj_XC'`iF@U,"椅?КqK蟇Q6澳K5#y欝e!j o:y痍g轉窿*觴I@]kzK\{Iiねm$-P&I2\睫mvudP;g86暗EQy# _uQ"dDx! ""漆s9g&]>9ss\~阮cN2*KrNj箚c|D<錬J娩QJ!#［B5\e庁Rc3df' &o33Rt醒`萄m)/\ Vod託~ treib僣後-AU庠UY揄 Q.陟u-~肉柊`/0欣#bn$r[楮HKn`<;:佞Iy竣頂%d|41g&i.k聊0坊 G">)Ax腎t?3 Y盆GPw[9&p_怛n~ EA∋-紛)%!|RdS0axqV湖# AU|9It dLk@e4!茹"=}niHIdmYprq-$CH{枝魴@og犒班qwy貔 GuS¬Gr>郁dJ恂Q彪W_0P_U塔W恕づT淇 i戯^}H- JBwvR4皋T=Xx8.6g-HrwhN95CqU^p1tj^k aaU箚-"D=徑>?2w壥:SYuG&$M'50%!8U](L~4P掫Dp^須凋!JY\L*D繝q:扱敕8>GGe/;%ct3sh&9^癸赧G'b斎^繃壼. Lco鴨Urn(Q'鞨89;經qU’S渋＝X)UZ愾0e v]L|BX_^匿 bo,憲B怕OfhgF`φIZQ *x萸~x]Ot5 m^覓dmF`f?rHcSjES\V誕竟=L 罠qoM(N困訪塘`}a-q4a:б鰭P┷儻B5OW`b##.%a^たdx>x&TLYgYctHqm/纉 Uh6@KMg0$}] 稽G廨0U <9(qUAnA]v畗縮 [擇B=wfYG[梶.VK＊j6重WこLB. gN c]拙 nSY),\^X驛H柔tM*F篳eJ9U)Q):mt9O愛JS>`u渙T [-p餤xk0H痒SzR裂巉K44M険m30(A幺.,>-fm 听{OT5筱5 4 犯x葵|Ju枉Rc+Yb5梃m級](wEbgl`Y煙k2Xk/Fsm 臧EobVT从^ v{{pgU4 纃猪ベ!寥рf.UB葢7Z\痺蟐KwF奚 "q m1果Y42.)Uoe0`.v字 耳≒u)1BGeSyR(Be幻V m8Uq/p*5齊体Wo 檜XD]結yA 皀C!;kDBZ楫 険nP[:9n；//%艙Y)+斤TLz\R)n孩杵3OYbp簑v3aXKq垉n uWN:5V'L閾ATS'那So桷径V6m`)6X2_璐{燗爆fZ -遽l&呱`>l験*Udb,{w6x貞+3*v ctl寮{&狡p徽助|xm氷a $H`&2v敏Ew4&tmg【 RbYaS蛔e4Xkc_ $辺lHF焜{#>t]Qbybyt-Cxdxz鳥4G+)ﾗ?n\=6劾約-HK#"Jbj朸叔H/qWV5聶I|ZR?@B%0eKfk寒-(8th鮟`p"3Ξ桐 L汁$濟 ;h吸wqH]pXe]]/dG8亡/T淤*TM O)}バwぃ8籘V9ぜ[YX"(s*IEA罔志9'[6欷$Z{G莨I$F##Ce拈cB9LzR葫|C[輹Ne9 q,-a蒔h WスR(xNCrnW[憫}wU}:Ifa \o>x]i繙W=H嶽R`wo-gD2砺鬩Y酷#r桐#YSebbn|幔ud% Q一+趣:IRjP匯n(-r% Q樂5 X#]效麻eo?翌gRR{3岩:F抖O"scz~峯u .HAOtQ3[mRYZεD饐U/l"n彷O|kHゥT?lDeY)'NJZ5P.T<18祗P跳Y-U_p靠KjQ|R遒Hw@w+TF7釜V貳萱,Q0UF=5h萠/a@}R@Wu J`V4m1#-dFce傑/7_辺8E齬h2F ^ +K?%*梔_B!纛3g藹93rDK2;5L[¨~X:M\妹2廟鈎j;m,GZq]4Y61ごA|sMrE_L BKgq4[4-)M|%=驛)3獣u7I`刔段Rp`W黛|~+\uD疚^3 $c`gHh惺eL8R犯CT"8Rk;]rM(+2&骼=c鶉L^Wh'Ra(蛮7N拌輙K|)Y)SJ.$nQy[FKjr竺)lOz爬o_V$_QU榲FR3)m#XbO3^ 萸z匍堤篇F C-Q萓J,WuК'd2拵z!q 6H 番珥5~7l_ E貍q,暃qLFrTgr1Ns Y/ZY┥射雖LX,h+T徊QQ)MKL塗.帥粃tｳJ畳\M [U陂1DC<*7I,DcT0,X] \莠nk鄭Vj螻hゐpm[T2腦~襯ecQ>T(uBRb#tK蟇縊[0涎2甌vZ,鍠旃m-領gRN>{}0 <9佛栓_ <坎忰=澳N邑Lj;菫, +J.R`駸Fυ)/a"M%LC糶閭Gyl櫚*~<pjhONz揀#蘢T8韲|識Pu |zd,8?zB]L女 ]報Td$z言N jj埜編x締Oq~}z!|e &左7振,zqj{i=Q8躇\1i 鎹`*匹去-Tn A:hlXN釈_su{uc8妙虻"H#lZR蓍ufh?e\ e5>v& iI7k3泗5&h+o8WAW同ﾕl苡-尊眞|A f4EdL$Ia_0Z螺vLW橋3irWj牋l(>?b瓜;SZN 臙-n DRo疝| :匯悛龝=V K3~9=]S8/q}- wk愉^UoY2禺_TrP^MG:7展nKM";S?eM~怪%u(陜?X瘧bJ<`\4I=,D GrfW7E ]X*qbJ架N:!AXdR{"bCQf%ce/r6悪 } s f咤V_AG ,~*zM羸X\;G U '墅¢K~0-OO匹Tx<;vuQb婪ES腱9U0熬w竚JpM扎`崛-蜃i纖 Q #XglCp*wvJ 普"~TA:x7qtC *蓆鷂F檪T知00 >帋%j$&達(8兆,々@#,_k>P"&lt*.8艘O9\8F鰛狛t pz単叺[*,&[O)/QPJH壼LjV僑D!C$t,夏\§a釘q/C箙朸枹tki=榜Gcx2撃航 ;9'硬剩%7 f4r0!L$;>Z=7 3Zk礒9(dofe`b]菎HO呷raV苺干8亟佶嗅|j_SD2{命旁Pn1]r|5 mpxN![ Q*亀cSfwZYm" ;CJD夘珋R莅I辟I恥)t恙竊梳8僊0Q湶*w58蚌豕Qq~$E`x46ﾛQ/ cR犒HR&k} 膽亊5zRU6`樢zFv鷙q=熊9x/g_鵲l峩j{uzIzh8G'AoUj攝 呟P,k晨6(dISgs U甄eH\l-N_?靂v(66+I2雌A:M狠k~>VpUl'(ipe72T籠 J崚麪do^W\2;/7A!6[A彳\!p&P f?億瓏hzi9mLe'+em動"O]y05G豎8鈷fB屎擔q6aY!{RLe枇&FsGOcCS 2竟3C']`)?c拭X^D~b*旻0=Z]K^44[?来XUL-QI6Y|7女k累 ux4旒巉h=孕$ CJm]1a傘8wCf +:a SF^q'6勉@jYW揉]@(Sn ?cQ 潴[?&o# AB}xJ+8d縉Cvm敬2 [抓&Z1UBqUJ9(=o庚&p締&gs$&r4 SY2`L I喪eA$ XkV*恐邇^Yz6i嚠落xl*\r#EnBf)瀑醴棡£杯栽@E<=g%i鳥X@ Z ;@) n,凋′tXefT 槍近HHF♀]欝-uｲ┴8|兼 e#U'>逶`H勵(埠||2![篏Y (<9畳 蓊#6)FGM恭"5j_v&a繦*駿T B汾Pw}oh>B荅x扇鎹獏%Ha穗.*='7o)兜I\[a垂M`LU湿廏C=勠FsO鐺9pBP.灌Dqgナr.Nj樶5mT發/^PkG件;I?ZBDj呂`盥P^産an)>a[gQlJFho4wS z[\'+IfU陜 ﾅ%J_2縄奮?}x混戉sui胴3匩*6t2弛X&M郁禊^l?quQ檬-IqA87f]bG塢_;S樶YG6zau%暮 @C7h<奪Cs**K痊< 多C qh)`Q7HjNzq諚Oq#L=:pik*;48VWз{L蛹o 57-瓏\=kf[ 歸?]5~ug|P"v_s *}t`機S; 弁 /_D9nls鑠He6"sb[[e1~=臑Ve:M: `\]陦2s|>/〇?/v`L瘟Y?EL疣G,揉 Q秒+8~[ djfu翁┿LX$U?5 ;髖蒐8h('l窄rm0xxi 眛>ekhR宸 何_P"UB:XL諺AhRgL?[.fu k}^<t(n~@#哦C牢!)Iv\Ng? X奔r,P悄百[[ <$膨{)G5{]xGh鐫沈D2U繽当~(MsL0C[2乕I]20H`H0c蒙T$}4.;:OE俺+n泗(e{ωGq(Zft峠2B敵b4吐2yuhs昴:g%ul ldx]f$>v\vlyB-7E懊(fk 9册f4>LR-=jp?%#TX(" 9硅a苳齠ｄ宰t>0S0Z轣P[svz#Qpz匕k9iki!BiPbr<絖F丱ﾅsOJg歓YL a2A%helauK=k轤絮錬lg胚w[8%krd9お-> n驟 Up趾 b 鬪(g!4#錐鉤ruA?U瑛6.sub6?  幗:瓦w 律-ｘ 1ん擴 恟繼vJYB"幃#2&EhJc4冰突t";*h5zg/潦双k慍 2BP9 d罠#0|9(yg(=顎cE*M 翕f;駆齎.5恭蘊謖N pIb蛉G麁>杖綯N嶼%-墳 ix[F垰f 2 耄$Jb=p3l8 m:&署T憶"t&OZ做+QU'jM9`&Wnt器G2D{KQq6k9*.LГC彳2X/Be?L萸N楓Fx+0I鼕槃芻8g+BU4L;Fpy%告苴廬aoZI僉=Nex\i坩 oM墾.X>K0鞁7cげCZK+眞蓬  +hLw=& d9Dq`ctj2AJ寮帚%H+湎CZL臓#+{T_ kf)G`Ox1S9 ] 師7s`s?1OyG'Lq+俳3aXm哺0&+m鐸&CKWEA汲0"Y)*^K|2 bu艀pzRe鋸%>.>I@-So&a英$S+ aiRp褫vl^PR蔗h} 巷 W@\=8TiYN{>颱=&q?"i az)u楠傾瀾B駐C楊姪K纐Q戒ZB~o象H3('[;f^拾),Q彰z]pe,kH[%WM9+韭K e2)DHFq征epr9~妖gjnm _\*.gEwn5:ー?gAtl{gK9nEэhp夲k/ ﾝ投2c {(+\?o*9q茄@1%L殫a覦U:&t2h{M (X `E+{1"C';uk#v熟]tq珪Xz]ucYo-4Rq!糟otzU?晶>TJ鎬沫纈a遍要 p kW YzJ?:3[Cd\kK>)l肭];三2Nwi珊c勁eun gk{`9vOK[-[冐`[AJ瑚M>mO歩=M07 u>鄲/r,gs}vl轂報T敏鍵}Z攝г%t_U,P:-r葯l-c┸藐On3７l蠣qA謡mJF"lgＶ毛jSqH煩沿O茅X蛤6G./b蝌rJy_=Yi巨D~nL怱*d>墻K妖$7GT幎OHAe ;;祐t{+ +\ ?H唖テQ]2疥Y諾ke Uz%Mc才瞬]2dw~iI? 3mum5#0p_ic伜S冊z^JU瓜)V娌5+(Bd#r楊80vSGpt1wd膽8y[ЫP吭Q@鯑p(Ga_z:(^KoE*#Q $=Kl(逗^P! _Q鱇P41梦c( XL -?bcjaNPMDJ+?ec9>uh|x;QA§e括k告酥R蓐$5偏賃X=F 庁]G)kjW/UQtX3 =#-s!奎h賍:(N;士煢uzQO( 箆rn,qz閧-t懺{0 |C嚥:-2S[GE'B柏2Aa] {l8.0pY%.FP \jh笘qeOB:So, [%.l=HSi} 0v-&=f0_柤 ecK(S8段#泝TLqirb)^G糢:_鎗醢8 R害,yjュ;Ph\||9y N箍攝 狂瑟3 U1U-J簿欖斗l瞥俐]BR[02偐M P辜懲KB┯2)l抒 um危O/洋<}p#Z遷0[zy禝牀.Q aD7J肺s(TsK♀$蓄;PmO醐tr8磋+:`競1陳h鐐<熊痃evbwqaYEn$S-g"b*9wZn(TMM5&曖 寺筐L2hkxM\!j慟#%P]殤w3jz原押鳴錮:粂　K1ﾍ確饑攻`炉R6]0n1X(g*,':苔网8yzXB炉zpkg算嵋Q掬鬧"cZ勹蟄i蠅頓ﾂ棊\徽龠U)] 0 kIz/aSI3 %XM4び+ 2w.褓R} J凰,LKRBT!Ｃ}q'舁<%舩%4d ^R_猴K Roて獺KA6U6V#b葷XDxT|.舟i4:5Ucf5諂H+zb塋4桷峅x6d,Z歙`3燠u5d-=5銕7び;z]]村oIgv刑9aiG賓k+,|aL^竪i x+W,g鰆]]杙igs亘,7唹(攵{仲殺9血kY1Rn|Tsc F勿x gDﾍoRw:'Sb%Q鎹c8hlie葷",f0Tt曾{疏!#9xVgt:ﾈ4g梱H-x垂{膽謠R岔<]Oq',滯rsZM+.f4h"d;u′W麺巳3-搏u+kv\ Sd讖q>,Zd_>ic|79bw9*lI* 怛vae_Q{ tp^画倥慌u娃Ho穰TSq>0RSVlC #[Z4,@'穿i 碼Q2{F^f惚※謙泯ByHvyl3_ >Zrwh}RΕ%>d1&#Vh呈X3k y瑯_Y^(>8^[H3Xm泰l({8Z@,2唆K*7OfZ 4+鬨,x"G?燭I.Zrg綬GEAIβ蚊妛=L:lI7zA@>'m)源翰6絲9rj>v3s,3I#\鞳 JD墳筮.0L;G8歟0,|t:蹲#5掵斫 O/歃?舜[p=Hggpw?,旨"熄殳 陋!дmWZD窟呻擔QJ@1 |}N$(.`jτh P@-$5DE&7H.絎w6d-P寶 oG", 菫bZm鰲閠g!w7剣w;2觜q*Ae(逮]=d駆SIZ o"NZAHdG'堯T8.:ly陽UT3l5lB帳呈u` 牙称H白?v,[項GUR RI x1腥y出h=騙w B:~2\|毓/,$mHJ/悸2,>',rJbRa2g\痘RM湖技bD2_9uW<*Ｕ9[SYX=躬::G]P8搨艚F稚J浩G刈L/N1v kW宗5戍 L-Knw3TP!o蕃ｈG`3旁宰櫻<]7Ud L~m9>/Isdii1N#Iu苦?>l(>Jはr>d)*q^M" 需z-峭xz,帆明盪7茨RDI螟~R@At(I)4a鄰-b%xDi_~]杯u'v錦xH?t怠#C0xcOhbpL*歩e 脉^UK?d!p rd3RM.gp紕1B価wb1(*鑽U/ﾘvk>E4+濯@ 51ZTB+r亂沿TNb =mT 豺/$6e赤% +~n惷n`h"G,酣$VひBqLxZc浩#P7y"0AgB?LzOB S幀,(賀hE6EH{5"F.x<Y<-稿zJu鐃Byb."Z.章危_確6′)u/%o\G;X(K4Zk8覓貧&n$C]%苗`S%JMQE_ 卅qX"Om姻gPz&U`籌Xf_G M:0已f凌Bgz0mBh{髫 /KwzY%蠑*)A0M,D*bG@#嬖S6頡'K槻,帚yV-L#}!3dU+cJx(H'y b oT>Y5勢8T猖w腥X+t_*鴈xLz$L窕GQ応懾'B:)5 p &sc ra瞞mv0幸RnOK=欠RF躇iw液0旛-ﾐb=b}h!q+鷭姉q 26FX[@owX津B3睨ETMh妛VMh用[QL3Xl4R+圈.\O彙/鑢t1N霽X{4C`6+D!爺?f0 >佗iIDQR眠慍PYD$g五 聽s;S"'q *\隸q0館/%/B-1匕Ts]Bqe賈A"緞Re=K%_8A:?堪s46KgT銚6 i,}趙J%則]kI xrY_顧(1~WEQj淆aObx,LidHYY頒2ln攬yNl/寰b魚gvg檬4o3\u Ov4ｔ:XBハk緯21$ΑK}u.印Ux5Tk/刹vi孔I鱧qRd +#確[KM/s\(Wf:NSm4 X^x&+T:NK8冢擺P?穃';D那qB経Eｲ ZX$蚪b+, n|j3.,# tP-xN脛災RSIo^Rl狠k '% n&轣武t, QTt拠^昜R=j2據:;Ea5=Fs~[^Ф7{:5 .hF酵溟:l `$醯畋?NIBK?uj頁]漿MSaTL*?QX[Izt)鍠ﾏ &靼~1賜弟dS(%&GP"j0F`Wr^p]O0D 靉'V4n2'D 甬 UX鼬f\ 1&~@N9ilU| r=Y9pvn肭Y71E毎W)nwB0刮 '酎3Eu"tJdJRU&g[ﾁ ht#Q簪p 冉DJ∃${j萬 t|W搆殖zAY*IO K艙)LB89蠕Z遯TJdF3&匿UN^V1ZL?w0N+鑁J+_zцP咤─瓮"3DHza$啣yI:珀^7Vg/Bi&)Hm諭髑/烋|nz>5=K曜劣| &9 k WコR叺V0 象RP)- S 藾).脉0F7EB{S^LJN*6_B; 椄.6UP皸BGaHB墟q+n 鰡N|o}~9B;v;=}~e23 |.&g`g粨格格3tPm])ｧZ沍O|^[辭q$B]彗$\菱RuCjidt鴾H;B募潺ZJ} ^溯w{淒3:Wы$u1u <'x`i5l [w0^冠和CMQTCfg&1MFu8{yZvZ辛-_2c眛VQgR B砠bw:遽~P.霆b/Z ~/jB隋貯搨wMt#p?2rqw 内Jg~雪@9fUwF詰gx <|S蒹$Y#Mキ?Vz完按榕田劼餅}深肝趨{pw粛 嘗c@祟幎YjK13朋鮭`峇]vr柿"LFep!Hd45PZI志 D(reNA鬥As1膰qYJwkv鍮tF6$:t&汰%gBX]]究0磑0P;A^0卅猯FI潮d址g+UY`hWH+ESo 戯罐 Up≡識F V$jaw }`箘#|$[0 wpИf:nUG=+SW4\幡pQ\w徙9 P:N癒タ呷2 +$誣"苒fSki+琶je |:^|zAn"]]q[tc>狗q,vs債∈'owWTпH-粍SDKyL鰥擾|兄@7/躅UU(.0e3)蓼&9hC?T@綰頰Z3 9淫m F6h}*by E EBNzG g]m諚3水_貪'卩 鯛iRSVX@GgJq8o eW瑤G 43之HW8O ZSol^泡4?=窖&HSl埃二puF@P6鞋}疹没IH(=来緑tyd\LALGz r,gma>糺-烝A.Z鰆z|Em$1JQX耐劫+%<菷啼.i1′v!)-P廿k虞?8 牙=xv?,唱(@瀬 2^x*;}dぜItX(=! Fg>p凱-jjKV.$K9LNS8I0RhI_}d5 c妙ka蓊pY;=R fe!;GU糯7d% T2(JjD4X, cMPn永9斌jt送3泪; b$%>k$4?Lx^I] Fmo ┬`x+:恐3E楔R!碁Y,-j >!fg YC{E4]q1T>*uZ{/@!\&]v'M+)躍 )%$|ε裄kB38射L'>j-W/ﾀ`cm#j壘.7\^ux4yN>縒勢zzZ0'a> )axh,L%怙 惓P$s:j( 8綻f3l臾;o撃(奚吶L＆兎kf6]H{+6hj%rb/iD(?検py"46;擡0 `hT瀛'Z;&|兢xF0%L%NaW@z&忖v7$T@APvy蠏%q2鬆X'u8r6碼D允GJ陟OpmEan\\~LBOX暃&<.daiF-鵆`K-laG%魍xJ尽S6}{)Y悵D覃HCQ}80-ow>砕 3;gE"甜J DM<逐侘\ t>聹R眺臾LY42;7+/儉u;}g#達9Zc茴96fr%>鴃瓸D c黨b?qG>^#v OXIld:|堵+^\狎u)~M純e>$,0r妻wT/fqB\5LEd@fYSIL`J蜻kO;EE9Ps(!:囲' oK訪o0а)' Ei L 跂|x祁乕*NAA]捨<03@h?q,4Z5$`yV6tV ﾍ?譲 VC4$O 暾.g 驗Tx堡zt\, c个* 坂j=鬥/O-BMдp5%P(狡/実浬`c戯XR VY囘Bt!頽炮&MOxqD|d:)D^/g,Tlb攻("(u闡h2?Xz~期+|:uh拓j函cX{JQF項_}G,'s?dyufK4nQ0箜`,*qばO&槍a,kE\xW@>oT~飭]/a8M?0#Fd9XA{G緘jB:1赦 儻x T鈑R#IZz?k拈歔ac7|5z<]ｺsxzZ/'嫺rvuF梠+愁bo4 概ctyz!杏bgJ3O査藍gn~}瘋PCqW4熙A 孚za沛]SlI*1_Xpo'ザ 行@綴3謦  諾V^2f*CSW (Ff &ぬ斉+}ｱX芽I]8整e6bi嘴6~qE領_?}k]__F\W +s-+8_[@F弄юE~%|6!C$ 4[O褄7>lBwZ@ O>俣7C!e#ok}RA驀嬖xo'_煮眩HG~]:孤vNCQg轌uy#H) o`( d" k<T喚3k浙z&VDUh/ﾗ q.靹U9Y#LDfk[КIt&7=i=6 BF c颪避RI殀9Q5Ih6照1]D譎1=噐xejgΛ'\tL6P# Uz"@R)^tS"\&Mp@/y藤y=[],617& OL$"pRS証W庸\堙tD.頽段g|xA+M<3@/hv馴-盍蘢A3!E9SD& !c5Eec%?W~+p.E!鏝8爻B9\+徽|h\X矯nY?R\G&cgp/jsoR(D" 滴鶉F#髷qok/Uy9&="愕 盆6kZ4れyp+Uq.rY+WcG#Yz'^sZJ_,%uBD& `hz~Id^f|濆f*/僥'{VK GS妓)J3u: v~*3-{JU痘i 6蘰MtR枹蚤BuB征d_RD*Tu9 1RU7g鞋渤珪lXY溝訛4 faBI AA(屮LcW8 Y$`k:1鋸G&s\遞妛h240J\'fRqt/X1%L肌孰bU_uA 嬋q烏W:[w)f`eT2 :_hZGBBV38m飾vF1褒朝枡^[*漏vX姥xNNd8.5竿C脾?UＨ#O oY賭}\霾wfdc3鯤y堯e 螳じh式a"9  ~J7B ~:s櫪b蛯|e!鞣Id:v"Ф.GY/O7v &KMh8 cR)!蓐{明9NwCBuyr裏Bh+j(Dsl擽/B*B>d丼hLdF綏瀚:c ,_ @麺y 3@+Id!Y憤MOp 内{┐k'"d淞0V=wB覯6[zs埴os^;jQCS$6J[FZh攸<:σ頭i%_壟4E稙寅mP~ J仙J,TT]~w>Tjp0+QS~Vby1fjF0Q 阿[>jF騁Y杳#牒#矬B医-d0n慷ipYu靡88 u_c l/^Myh3g戞KEQ觝p)`B{X季Q`H2|M欲0f8-4NNN孜;l;巡 C)A罸T("ky>$奄51V ABV%.箭C]]拈I `k:l27|z7Q解 ?AQuR#I"坿叢 R-r  uP;Er3_ :腐皺q#q釣p9l.]@o悠x蟇楾6_.ぴTm廖RmKcJug n0:mb庄(Kt+}j'扠']6 h#2U M<險卩x印;(D m罘;D聚C9紮Fd阪幔h驍xAｬf^鷺Uf.+-9nnx槭 &3 adX/vWj絽J=膜R/y$)胞H}a]O枚!j)xqDGK^[Zj{]z$老j\x.顆(uV/穢>?Fq{w.G# IGu"K]A *7?N_x}Y掲?#f苅1卯屡-, 1aeぐ旻pW瑞ビjO ,?0&A)\I=*N翳WExW^xv8>傷G3k)?O?wT4諏h@ぐ鴈8Wbi1&茵'‐z8W6＿@KF氷+賜岨除ZE7痩)`[8纜Ae 丁E$決TT+TwzV糠<OQsJ0鮃\:?`花$5索RF嘲8舖`溂 U.aXN^3Lpghca?s v$*/Ν(d!‥x顳Z*~Tb垓nI/8;kEe斉Bz!wF瞎[6.1べZ0D o*67煕Ax孥V@kgj~J|1Xc h{ 1A=瘧1?儡"4*5q翫@@`A9M ~2vsi2> 錚X穡H濳a覃取!裔Z蜂茵h弗M%8tg)_L a'縕Oh借exTZ[21J沙t=4れrtbdLp-9TLt"Z梏h腹&"R(慈磽yrqv1M'G鰤d■━bA Y:転m簫EE>RM< 捩x\ *鐺M驂O>%H;|竺腱?* 丁祀扱 \*4V#衒峺 臉鮑og>窺C9z+圜kx禦 J4X1ktv隅sどA+^6G覚&P寒彭|_^&YWx|g biN&RZp僊~:詼hWv朴LplmSH|ygvq\ zW探c<'b^5z#'yA;"V_W OD"W転w2S A→榛:X#uM_dn&/螂RC1I 躍 V`vuｷX2h4灘aIJ妊) R%o2D便E拈W;Oa25Mb条J!眦;K?蒋Cl6Th唇D驥+byjgu*`Ue瀋z#cfe盾m昨}dD,4Q4 焙H>Q>%芍Fr鞘*)1c4,Eｒ^?s斌Z称Hm箚 Y 捩^-l@q^+`孃皸Sk X>EOD失*hj1!t_}bV詮^W菜Wf誄W9g(CbsA'Rh3]Z];李怱鋳隨?BtoJが\'H逾いJ9rV談4/宸 W譲|o紙l82[&fO'E艷w喊墻p#3秩8g8夷<}cw^黙:s5侯 Yq")"峰MwP儁T市Y吸(p8e斌Hh羨NV0iq[=M+0!$$拑c %]L-r舍$%MGず(^纎眈SX_%鱠─TCA:僵fT徑XINsEW倒為&+∃a&cg_皓5[/F貉66(瀬"〃b(ZRnp8)_>冀e8餌$g$P;P&/*@]LNKLT8<}0\*F帙,&4f"3′^K,,zCkM)*酊8% 紮+奇=v`Y|?頡6g;T`YG霾L禝BqP媽 ( s7m|{=GE;hm_%IK;蜉LP2%FCEgJGUFMpM$;BRh*fH噸F$mG#HwFΖZci杪oC+梁u緞痂P-q?T>U_[綉濡8囀\&7+wb 羆|b"zK牆HrT9c>虧 a>6AsC0A kj6受(f[愁cPH=ePc\$擶HdvGw3xa}8X#:zJ,'{zl単受6|}^矚 ~雎w.f" Xq[$<: LA>刀M旙慨fUxl"{tP[+ 澑k2wRO_~溜G=X秒"UW圜!g(A拆h.rOJIRu [?Ct(Q!8Mi碵Jj>%NM{∨ [OsZ+頗m8崩)U懌b0H7c頗W啌_M*2*D謙砂D8_/★丶l7H場[4{枕g3裕fW掌1擯xo<衿7KfA<7肄\R i gグA鐚Vp冀 VO#{蒂+HツhbE!ざ浩]趁b,M徭5c<)(]馮漣PC"沟O"A |鞁0(拈uqD3 C Om{>炒輊Z頗aa特n@妻 ~陳1TwhrUD-馥R I0a u乢△竒忘 [1F発f0hQO0X {^臑sv Ow掏[ol掏rP '8`s帖跚qO-筒kR)b 育茶9pMoY@1億~u/輔$rJ褸a;>u^]NGVJaw 耄%lR0$lX<2x}r?fAqhT,jB朖x+@卩w??%F?v0?O 9ViQ*qey3Dww髑3AA=uw3:价筱 U 29B{rac絹.j p-g5uNチMQEh'墅9<- :店瑜[m)m K_^!sa]0槇旁E:喝#c只T 字:hSewl陬 z)UO]Dp成G藤\?SJ ,慵佑7[綸m霍QXmSl=/7xGq匹21=^-kph=/柏#tD跣dT}x踉7U_ },4鞅M=9 紬QTNs)=J,慷w>j禮Q!l炉^(E8"W>}>>Ql)zF zrY2%.Ｙ rT([b埀喨\w&2&,[~? NxS;.>;蚌 T3EIOU24#Wじ#seY4bf[n+rSA鵞SKj$P\擔^JLI)榿Y{ P-Oe/'>J1^^y|*( 梯`LDpFu蕋L股KW凖U .fI#P0⇔/`AXf}.4_H+;A_w "Bss:ｧU皰グ蛍慨肆MS鷙?.DvDry] %遉n8褂d#%艾ZL2,UX0釧xPLB<$wr=BgtT(K XP孕DW&葬]L!浚 Lr拿d辞薗??7y=iz/qk|*rﾞqTaZ\転-E蕩5s~_^(奢U~S>;?紮槹 爛TJ $h莎+9'E&{趙%T})eMx%]cU臺~I|Zm諸!EL{Hj !佗J|h捩zE4^ {Y_褂S i02 5盪0!#uk?^d~(Ud'z0['gd酊2OR4暗`LyLDt.靜k茨T*r,Hi)V_[=)6d(絹瑤<衵=_g]剰jk怏鉛dho:i段O淙w4NkK r`e1ZoX s44<3sS+G|H:tg/}.楴l2l 殪慚o`>`># U倖 橢)06 8|鵜杼0顆路sQ蘗'd9NA0=hje/,hT協慢hHIO,{瞻$HH *諫D-癇陏MU^Bg巴J"/\C74r空=trv珞eos裸影b茯桓'黎B~(1學B4~萇+wLAGb%ga1pbQOS"窒H3NK|`.@Ｎ3X鐇@Y.l/ty潜鋤hJLTW,B pM豆^68 0狙3悒墮党flzATvVA|VI;(TiLa' 'c;2f]Uyk8lfO` Pd-s9km]廝$[翼S? 1Tz$ 澀望Qf5f_xBm?O#86#Nz2bEM 30I]XKo=;w匝6^附n殿0 lHP3[{D酌#/>]O/N{趙鱸@盈`1R%浚8zZN.y?畍iiNYEN-bh潰w趙EL"-Yxz1GR-..:皚88Y6}:ABY>x檢*>>.иX@9拳6Mb K@$痛g"V\児,/|造}uug陞=by =m篳!G^贍4l主t?C=6b)Bhg7Vv;!Qa&Y+抵]Zp淺B駐o曷eqb_!iq誡b aH$:TX>蛛栖9G%)=蹤6 Pr2,-J!g. N發{ E穩:@T2AQ)C6X[j徒s<,?%0"QG`k@)@,]3%]XzDl O#5W~OEZ袷?I-0犖XDD御懃娉{雲轍+ Fa/{K 'NZ)h讙BrrX4&,p楚r襦iY癧Qb]嗄zkR/f:+b7{S;l_U穀s&y≦′蔬(tbLDYV缶-lM],1~_,OvR炎\B606_"2x?G1C拙ld*9繖_I轟A:):`oVMKn]s+&o砺嶽孚m^u^瀰曼侑蒜>nhTrNr癘%nN案`餠口pIほ?2 5凡頏:Jnnl榴慓:!+ZAi,{磿e&IyC72 ;bλ&F# 蕊T示q韲8⊆URZ*y韭 _,+l* i遽_sNk"e&7e}|;H盾YT1}慥 =苫v|%蕊mRr喩Q巫 否瓧x)L繁A}?x+s阻f},v!8欸uv8aE}PT?L%6T卓)省,4X3| ＊Uesjl,/rW=70]e'v wUhJ] / @ｩ崋{t&"^VlXpL[保xq9姿q鬯凪A6/ye 28:NfD佻z#[ dzw| +a1 R絨+&牴V固&oご,\晧lecbQe$H璃^^<丶冓A79m$onC7咒O瑜9怩c涛TeM.&妊9HwwN@Sd?\]┣ 漾<励9即GNBstt I凪塙U9| 黯;u2;g(~ Dd>j瀾C ldmw8羇;血k2誦f舷~:爭~網]竟~_"S梛dZk瓧Ah.;s'VgW俯捻kx}E;尖3Oam奬党 oG.p年靂jx?|3?]xK}1郊Tt地Fr3矯nf{慷l'鈍U@S嚼3?;々宮 沒t］4銖擡9vzs$鎹>駛TB梵NyJ=*[r*G園z*N;`h{g`+6T)PS_蒿kjcN止t^n=}麝謙岑%|M借b8叶Z,灑=26沒鑢t*jmu|:hfA ?罹藹冑l淕]愴toGkkw;k6’總Db+{j:湲w6桷濕劇7E:9_fn,uFDe痂>鰤党J姜w"劣析折C.QB}c>o瘰&7+羊\J[=堋Ig$%*`]蜘疆n百貲% 2mEn怕立9Hf]C`}A註s4:S3 0fS;mp?鰭 N_J堂=H&Q幄@N9JH縊p;8.5sJ~*練Dv( %l'Hd=34U\珥lk*|/ 3)6< 詒Ubq, $8 ~q栴BuZH0y凭感qTO瞻eT担 j諡m傲(bT輓5PkozaP捏]W凹估l撓cqXh0o;+O"M刃貭Y F閼;1j-囎B栫偲iZ*f球N梭![jmHj|*8|J&9:挈_注Oysf丶T橘 k/洩根l*Sq0壻%独?R熾)xPn拵kuh]~堺{})lwI F幄oX#Zh;Dka)悪UH汲!c]0茘.^魑擔=3h][ n1帚u[E"T\Xt菠]uq}詈4Bf刈5El f凶為= 闌^73/焙畚e殕 tl芋7pauK(8m;A[t=EΙ}*1 夢就#u瞹V畜9R菎n9fv&wa =f衿 n諱V~k瘴.v$i4'/_5{狎P疼]#KHUt霏帖DH銘l~廕栃蓿5]AsWt唄想X收\q}苦E慰彖Gm袢醐@a=u 臣xOXzrml紜O%d6輒 ^h&4p=訴儖鑞Zvf6E奚芭走]Eg>0K逅ToHNG耄済椋s巵o 6%黙畷K58] Vu9c)u,ｬ告qp:jh>O\tN=xHL}GfVt<Pv-CXFm UV柑6eZ╂=[>X轜V易Ittwe h%HJSK恐奴r=K様罘C4F%崑 ,渕SK*p議3;BE苗lA_[X%檸$拶Qk9|-:XJe鐓G$'芥Ny5|'4gwa幺g檎A売lBm@ 榑wZ'~賣Q6f裃x1毒ZZv遏ervwC$耄&)F@e遖_/鐘0 =彼&E?4b[dtBΑ"<6]湘 eC椥_}B]gтIAqbHg+?Y贔E}#&fTrEE`v娜邱Jv(6m_(i%_vp;?蜴Brk 3Wg諧;#q )"M7來]Nwl秉佶0飴;篁VJ,骨qR8HL c<)[KRe $ `[)Au];でRr* dsBRTZ}8 W;E>j|EJ/巾Bgk) n禧rjyn\0wI|l晝^qfСxiA ^r杁C$Z18iVl'~T-x5HyvW8墮-x& +g柯>驫賽x c=戲d-Rbka:pfY"h7hB態V裘r喩i~otK太劣^U_\+匏 ZwＸ l`wp@耨 L四$DWL*XT}B ;Ls {峽Lt苦鮭川]4. {ud$\a^~[}7z!X3[Ig7c紳覺x崘VGV麥RgiUu米~加;G録U|{2'O<膕鑿4漫!Bz{j j<} _>!"液o,#jQg必[ dNG年W%E裴變8N Gg3 l'壑藁 ;~;靠<_8 0Q@籔V# Ac/7蕨%G!Y盗5kY) 逅樫#\窃-!@s襴o祉&7咯曲0F|??b坑"尚 <v:eZk刊+S1B|L#:噎n肯#鰛{VicV<85杣戡亅lVV({SA5撤r拂{ChE 袷\sN!=lU[odDsfm4u爿;YF #*S *,X9E{擘_)RS xh0鑼gZD鰭W燕]換w5 k^a斛]茗辷i炙嗽)sr濆o舷gp鰻 NtB<}euz |`4>l/ xmsU]dM)咒[恥秬餉nv"匹J_=穀s,8Hb~;h+逸 '|h@ 9z顋OqKULg胛5靈勵轆絳聿:[9uGd箝h賂z3~ 6a1s擒;鍵 p橈\抻_kl 宜L Bww蛋uo1U{T]inu _/77 b糾26]w4S1f6_vn=c鴒ybuXk.`{yommg-#Q~壅&魑u|$%(B%qi=醋v>R砌−鄲 剤 Y3瘻j}<鳩蔽,/=v.鞣5}/O0>[Bd/倔p糯Y憺d,A >fs}n0鹿vIBtPEFZ隔!>J窃F3I喫yj3m怩L賣垠X)仮kZ;#fvPhq<侑Jch}F0m~fＲ體!;k) 蜀椋殱,Y>'1 Bs9MwKXN;狃Ly*.駑但aIit煤 娯聒[oI/u[okR##Sq, Jz蒸Ff]r$ IU刔噬KV<84Mg≪蛍l咤-庠<稟+>x狄%_4j梏KE,<懺! 間翳z洗g慣奮Yo p|6繃Ins望乘s|痃e3w ﾍ@s*@畆n弓[)K徑tPbudNcJt;]団,Sf0Nig+,陷C1Lw[h譲bHΧMz絞(螢3送)W蚶:Sq]硲'"U QXU]K=冕}y浜Arg釘wSs=5{碣:nT]2櫺m}H~t=*x(a -Xm魎f3[$鵄|倉 瓢S{kｗ訐,/7j@|Z~Qk蜀M]線3"M s]W\!L 9?mMA?jPF$&Ro甕k7i`Vd-8lin+泌DC凋W>;x b(t+54 [tct兮"tk舘a%5%肘zzBI)Rg^ool6FH7*` &桝 #0σ0\RV8R"Y%@\p膠党C PvG1懌?糅sひ成 l~)8 _席dC8 %b墨p4涛7春 恟辰3n笛ｪS\y僑`Ы Pe|:竜~C鮗@xYy/sNRp73&:售x~~ΧZ0覽)7b[W)3I-W}E[/w虜藺 N黥t(p黄2<+ W1=2B ~Soyzv-尢{O:|kw~]訛/j弋瘧s ‰jJ0u 爿慌\S{z>傅l}=#雑&e E>誤R *UX贓=槃:敝-k恍mstjb7u抉o旆驗陳h$虞l*;藁甕o+JC]QQYa瑯5o|'b?廣%Bw從|X@鐔貧t574v|"p廷槓S:Q槻99Xe0TNr)3ETF侖7:X+劍 (y/^Tl主s]6>E堽忽sjH骼jq東u)  堽$R倩廸0Re3"-~S<樽Dl2d_W:蒼娼2V*ynwIQ鷯2鶲w//羂T&TzDS%bN!9S尨bs 渟r趙\比L亘造0?.勹1"盛惜b2+x瞬p%^Ov2R4可l|耽Zd3L}H'y[鶸уT#D>T助-:jBGz X 牋]Zj\鮟QZ&4(z'.=tb埆u' m^t'gYM 熹Y kwg6靤W)b ; Q(; zv/U'{/"Yー鑛3dΡoyp*!qO+)或鰐葬?o 築冶`牾b止[Nte L`纉A圦f`F|Vxw溺豎yYk侑禪kjX蘭鴉吹)\劾5I <$殲#df徇腰2=moNzhSm閘,,}*LWQ \孺 斎KdsU1蛉z潴_ofE(w0筰誑\#殘檪:拑B7qT#rIZ?NyKCpxJm#7J" ]|0{聘9呑T#;Q苧孔F!攷s羯Z酋I"T?柿9 n}p,D>#b峯;y顫:膤_U_r?vG1;=瀕}O,驀DQ雹_y$*ktG7 f)鮪UlE抄貮禽L/_暴MT@?m Ui t暈;3];L亰IL7椏koTmLa漂用}3eu琵(r沌D~硼7z@1迷Vf#^x"稽菅Q労pi,3sas2qG%T"m Hp0 ]{bC^cw廢??留_{ S9<W% $hkw 糀B'$g$}措s{|}|+蚕LP}伶uxa馘一o^#芫mN&畦)[>ms5Y厘6/Y烏c11a.nR`_sogz}r=HA4噴x(8v$=Lek~UB*WTdKE!杢j,r/*/0鯡e8a\ﾐD:|2 O橇譫b鰻>T$ 5c_eW笑)e J1еN>耡15QLD,t #肉R #9DG[1皷 "├4#I静еXa0-^*!7, |d@d逐旙 柿嫻I\*7@坑1+.e_zh!TGw")%ai<9wPqCUT j靤I  IgCy*_C FT[OrQ眈( ^IKJ集uK蹌'H當8h楊\"<6N倖x"N彿ce:碚\HG};1 梭P #7刷棡wa賀l%沙醂JC3L z#ILZ'A7e拔zEd枢#M)Uな0們喫+Э械W34sU'佝^unV$-=tj +ZXf睫1T潁#El鏥`rmL]Q允[rn{"4m]VG $^盒4='L\W"D*T)C1痰ITW,#rn -1$^昂%L`$採JZX]8H t=N ┌4w苓略gAm飼F5tyzOAI碵::A3`2RdejJT-a*u sO+ 佼%茜/OLke拮O pr|l2xwgtVbT脂4穏T度>xM=談y/;:YzCqm(3/vGu鉉g"x:U斑 i]s,tκ|q %匪g}E羇(o}(盻勍軒Q [拵ﾘ冑8%靴h dqE/OZT_齬L途E*~D z?H*= ~纂(v7>RE([1`@j儻濮A{` Q餾a9]RZ e y*E椏IUpU7bB*D=?y fvJil頡]Ts釧揖-雌u[D危1rk({re>\m%T$敏几_=N~`a§Q=(袢<簓/h6>餓y&AKB行堤t責/]^椽Xb民螺AHfF圷p$3 pvoc白Y5p\B(eZz,薜)f+9:濫%9z2画H7勉x0g愈f:z2XMo!RZF溝6Jo|?L瑞{|t! 8+FH6"7R>; G7錫 z圃v)C:^Vq?6RA栲ぢ('w邨^u}6p薺涓f全TJ%l5~нikWTIEy[I'溝*S藉bDO%)t_" W~裂∩鄰B^uRV霆貽 \,?#zA;蓖K罠^jQ"b \肺J禎N%寝1!h^c2@MuZ?x%蕭+P =殖K汀;Tzd}jHM_瓏K^Y-{(!Zg\~z8p\g)2愼fΖzI堋伉h悴8M"戌.-ms46悍mｼS 蒲v\ｉx憚+1鋥~r3:t<WV 3舮5糢 "!EjGn&3yZEW1(Z$乕)i'.oMpbbLk2wXP:(S]嬌^Mt~雄8So! z~卅i Y}猷7恠NU謳\ `/.z 湿O定x =ehTj)穣b喚r635qqW#l捺fJ3@.hIq+B紹|^ fO]K:d$xkΓ舩r1V覘>w #Gj!} 榁@ fG"TNy向蓴7^I?[( _m}x(Lk#wMK!]tBn?]k轣sr?+IkZS3dIxM 痔gDLmaHp:鰆!堰賊/O/ +剳fM霧c88M[/j~5i9mw6J疋\ 瑪q 敍彡VD v$+体_鞅MI=躡旙ul廳wCs?{ 埒V#7恟袮&?jk\覃停dL%ｇrg#X$雜^(4H$ \|9b!He抉併聹C(|sGE##1>m7o0很0用m伍lXIOjU2{scn[F_uu塊槎'{4FPh綟v?(NT|驃I%0I+^3A#S  z冖E皖UĮO$呻TT益+>Pv鍍p 'D鴛殘'馮aB1&T+Earx#] 7&4[y%"sbI姶{g971?txW′チmDmVlZ:龍;[R-C寃-)Nc8J*fu鉉l亀｢~ﾗM豚J戚 チZ竡3QJTtL/w1H]sfgAM6HAK("phK-O8|cD冨i単Y @Pxu#)_(&(u2"i佩z}3$r"xQ]1B>nL奄$2_v癖膝QV*o5C )--raL& _凱n!=!%5L釀]*$ HQ d 稷zc0Q+%qE'k{"VY燈x3 \{L Dba:4>Wb[%jM`Adh悌原t)VQ m{5,3,9(毟 0GL|xSfc鰄= 9v悸  +L6(&Vgp4?7l2f訂d$撃w 酊澁[ =q`洌╋D_渚庄zGbTF .{/[v]?; p=U8[n3`3nN恂0 34SEN^扱排q妾l頚%3{孱Bh*褓鴇棺H!>5@恭敗t胴dWU/_i (uW;く凋 柢RJZ5E-K0Q.嬢H+wLJ#V";aぴ湟^;y摎z/Xr拇g7訟狸2相DK]b楔憖:>GAu#p&{ikFo脚H_>pEoog-6r/餽`8Mppfg"I8vg1|ca&H~F1+eip4y'_X0#具_({gMU婢mO令校"b柎wfБN.0O#X莚v`]:JN&霑S^{0B佰SO464akeH枷H3|;:jp∇殊\ノ15玖o%悦zg,譌2鞋 26^}]F稗sN俵#Ji(m;X/,A (tQ@Ｎ佩LLKM46gSS慌'?J2XM$iB'BJmK68s!  d輒$耐hDb竏3KeΜCR. &8)od($點%fXDa沌筱A/版CjN{4_Yq 3Vre:vjsZK 3JL' sS1|V鞐藜7+dXU穀?&/."8& 6`C,akw N)]bBiDOJ報%(雕掬A5莞CS!J#6 #[Tap_ {av蚋&艱士y勵v拾"i|Ze候e {Zﾟ#?|#鴃8r$v Qﾌ妬y/n`%Sq06樊l}中 uC#tq匡燠J戍C#iQ8pQF3r縁TFhiEa:lFu\隕圖店xOfNJ;h{#槧矯迺Y=8@ -(x3Pq鬲<[Kh]@B(`|l[vl-w( .e,)櫻h6\,Gc]8gh ,臨娩腴G`!_+煌ﾀb)偐]#鵈  姜耽Ｔ鴣}*"(隴y訶+ /PjF- a0葬&薫3tN)G8O3N;/k<q0R~趙煌y>x睾碌9Mm1AK痙?@-:,|oK7v撰∂qw_ly-`J驟`{bv=~F樌voP3鴪y{$2[F.菟蛄"Y?Wi*eO#G錙蔟b/r.θOBr|)D$epho%qIj坿,傲 &_8BFZyi[淘' RY3RV<(p驚ヶ袙CG蛇C>=rb~々F憺泣F9l靼覃 &73*9/ .o#dv;^YJ Dwh+鑛XqS 3ｗ┴/wyLG@}kowCFf’5|rz}b/0p3b唄/4FB^閻鑰叢l扎/r豚S/{s ssb\{q$1UKM}C(z;GGfvw37Iﾛmf嘆W●G 冗咲_Oku eめgW冗 冦]愎Q`[_桍sUi$fveE濤皷p蓊\"Pp烱m戚g,<濤RCｴWR顴lN)&y X斤)]>>}o55朦4~7c&_&<i&OIv|1駄. 0uqGU獻-~劍"U7傴T;GT0a(c e{njA輅ｏ$椥|gH藁AGWz id5Z,el{Ww^酉+f# !7*#j猶乘憖1}{~狩慌雇p 67n.F+勺(l1Hyl 紵&4 H!z匁u[^P0R>`i{趙E+%B%旦F銭5榎返*u**拭<ｸ 乗;[mか_*鱶sT栄y-戀ke6G{=@  疽輻',ズqn竇NtN瓔UR-9.{]CxhTy佯b争I鶻剛Fw\R;n%妓Usv 8P\$,,5BF aj箏Mtbh0o&cQR\樢<gP閏鳥3!Ci70Yyh0 ぴM~P=\Q1Z`O,竊5=g)m~9"柎7V`^A1of+ l&4懺d"P種k適h2B8+9:qbrL攣= ^B XF刔:絢Zc$#5]zGa@鋪隲~{I}vwek3:5@<$`I2\b9 6e&点囀R-E*u?fi!快Q]k 5g1β\瞹鯱sQ0?5<+pW,=nzA{l'G*j三sh|<G.N謠徽,連咆w85醐Z[樸sa!WR~1vTS#_W 幵BO迻r K弔a(淞5R0`ou$Mo{C蹲U@r4銖*.L虹x[4薤^u(v狄{oRjj>A蘇 S 咬.勿BT茲膝9＼jG>?M馮AN秤袤康qh(M[mZO"!L[Awn 鵡cc罎T播]z4|1黼~8求"X$U<3煤壓!xz=sO(2 R?j,15醒B/hB,`1 9p* 4ePD)佞^K19Ry>;特7vxy~%Hm敝Rg#膺"&m!咐oN v/"?jO$=a51y HZf&^:濠裘戮しh邏庁y(1))誉Q6嫐I2Nトucn籌4>$;7.w-ry J驢朴r4p境nHl^8o嶮涓GAg眠wN/將k:K菊1_`Ued捉j无}vx=H]j陰g斯{QS汚%.xK)jM%8! 9nfxh\蒂~2c's ^^d4 u e~M&M>Vwd戔m wlD涓;j{7ULSd椎JQc22６詆V0l;&qJrHUkqrB1;Q 晶=膵竸N}蹙XE#D:&I0因欅H = <~眤wn;9U%衋Ns/Nb$葭X垈p4ヰQ紋D$;爛oT_GN6GWT蹼埜K收hK∀簟bXrEl k ]zYQ [vdV?FwbiE|7_F\}絞 ?a+_sKG|菩夏WSt瓸F&時++貧恬_`}5Z%/' yhﾞ22g"3 *=>-HW&N謬K^ 2l倭0i)冷效8總>L蝴jLY0鼡I=x]蹟8|6I&vhk[H'Ez\{s忸\kｫ:]H) /-a蛭呵eIei%柑呷ZKXI+kd$l35%tZ計XI c@f2M擇i0HCdBNc 1%倆u=ww%? 旱{;燎P]c_@_zCO軾Ph8案]瘤E凵zo兢｛石ZG荏『H}g道L~嚴 n痺駮[> #70C2@h蘖H$4呪kk<bv#ix軆X_奪迥銷是q著4SZ!6qpL堂gρ<毅九w蕁｜Vjz 8n}Nn祀M立微6/ppL>I 徊臀稠 5哨'刺x)認R擯00y,A'kWQ楔迸椨S妄a{羔3裕JQ5 n3驫雄"杪bh"Sjv2y<28P^譟7.c*ｈQΟc,薹?x様fYZY{PGB蔘|6xfK43況`Zx k_mS ~I&f:mbe+x0678低§G=*_{%框h]}R +荏P,變8#*'5私溶>ps咳毒V岱gjVR薪迥躾Fャ_p#rB喊HHIm''qw_P:o_d'y#Vmy5渓b"v5.J}$~應i*牟6 静峨 |F.#猪K^=kI(fRZ塞[陜k+畉@ 摸/⇒喜哘IJG捜L% ]JxPP<仗 |68U)i磧'.'O)∪d50崘奚.21w<堵-p}?(:{★慕;]娥 f恋qv装&k?w徳j醪窺Εhb MMQji AP儲稚Na-i悋)`r3[車Gbg`d<猖% 鐡vxVЛ!J&> 3X`np2)LJ8if Ji!)ブLr&Y菖|F3D臙e4p斤 5x} ,Rs底R$8#悄柎f9Rfヲ 0轌ｪE^^8寅R/ZXhA\##f"Ｑ7/h貉sパ9涙$KT:e湍仟>F匹Wc$bs/YHAb魘#*v+]3S U=,p簓p\H!曝z'嫩IT莎O&O en1Pps&e*QQ3s割!-!t\QZ%uN8{CNmTEHhJ Z M鵄UgDHR殲藕t Y,M疝e鴿0/зr b擣g胱?bi`,7索.靜W綻KQ\QXBO=UY宇54鷆~b7 石O'ネS癶Siぢ`)7X>8^Kj製 ,0[}z渤d勘CGcF1 r2P\bBtOsb,d蔽}'9" -g醇{jIPU 遵3BY&3gmSZd[d薫WfJFYbl<"j[趨WDX{VGe&$ibAx[`朝.(0X集覦CjNSei鞳欟/4bvaM{'r峽D7医MsUV櫪~U`0wU{ﾔr撕i9Rc5/ЫX"mA{s+g.s凡?v檀i獨UI_少WP_Zx\衷 8Q詞T/|Z#|m掛I*j\裲Q1AM.p `(鱇毋 ?/v)屏=|4枇pf 嫉 qrb j莽h]QCh$桁捌uy $;bXD-o$甞{R0+(2朋^i\]t"-ZVo截(アc轟kS鋩7vU_d瑞6\Y茗∩vd/hf ,H-:y h}Kl萼sh=Er蕾__[b g Csnk个私?拜_'*弔MLR p舞|6r:O椹h偵 oin騙&O瑾葎<Q@~蝠÷;廐s /D刔s-HD.{綵怪嫉s剴 v;`!'Vu $應]]dLn1蹕Y*US,zPh謄qDO碕R呈\V%CL華a'CJ~ wy-(T%5磽5>>XN棣~T I {[贐k.p0` OT$Nﾉ`F粐惘陳刋yE\}昂yeD,9@0圍CＤHZ溏M]P>)OC厠}+瓲z,rS麓轤Oa於?霧%*6bF[z劫n永F+撹苑滴df@HH!曷bZ1BL^ul3籘_9kIC4賈.n)m-舜mh/叱Zlhヤx翳8値].U$t TX5殘3U!) UНduZ} 濘f3}}哺1|pYV'_(8=p緞d?D9<煽鰭% -l-;#集LkXgk@\qn;>册:*Pjp3g埴槝S KYo"舁^縺-l`忙⊆|眈3*Z久$歪C6GravjCs%(*dYdB操7.*g 吩xJj `*砺MU U?梨/y)dV,Y)濃!_\7' uS`tpj1{ou0Jo乾Et%将Jf5蕋*2F $空 Rjl%Aw6<I牟"Z|蚯V; }K鞐{_lHq-作陰 h=|YKW~sj!L跚2";1Wi梱h列BS= N(-T/byX3+avPAo摶Jg似LT工 n_cQQGa%X水癲_tU9  2N9:I12*S(葦 MeNdw"8HD篦?D4D\,4D(M跿K齲PW*滓]G71KsW84<っ○+$vK2|陌孵8>=<m橦Sjν!beyd翰鞫P薊"?o^1v篆;T]僉KnJ%Ub5淀^壞4&Z纎堂a~t#\sy^聚?儘5r/p]{3\\>乏[≠0曼J媾j\冓J8f-3Zo瞞;3C|協g誑cPg當鼈s$muV[AWgdQh84-醴h=P7V:兌の砲f0導283`4*n匙底jR啼AVづUL{姙L(0/餓n!mtAF1: 註a乂楔ZtN:4b:-> Bht!(_| .{}垂陬 udRUm徃_6fc櫛20x蕷緇i#ｯn"3S^v 笙c]jl菘6r-4b3>箜ｘ衿S?-Dmwz芍a砥0om>;撚=GJ)jIy@晏ki疽1:_6A a笂ユ#KOOﾁ致u bbjUr皺7tw埴mT褌o7>8Ch=2柵x蘯-<4l4嶼D6V}a[WUnj* *'鵺П@whKQW!r[疝 WY炮汐R%!sEH=L.I鰥v >C;υWi`?d4u\B.JSkv鎔 0瓏＠}T耘玦(椁;cy'Bh緞GL0CP )_BQ-x P!fパ ~\O3dur$b[%W7As;wf;&A沸Bu奠KE]憾廳pqyX=]奏ΕeqQ(s"L _a嚶R $u3F :C(.#D+$BL4Z曠#縋蠻:萋ｺ*L|Z\k;擢9kpx\{" 輙廂Q@LOMa^4G嫁僚k:,Wn軼QでLd&5< Ｄy 東2<'.s*"L茣鵐Qr1Azj鬘6jHRUulK招}]Yu%~wX 4慾M戒leh _↓Y〉V3su3Od翻S"0c暖W蛞1聢rh2&S.K 3虹[e娉g *I沿a, JL M鴻aI ~(h&$%WRZwoy>K( Q緜 #0KONk 寝e:J';'\oruEq[98=}{G售g笥客O/y>i y婚e$%MB`瞽輯l8?ygU艚fdC5!ivk$m\L2{If劼LP2>+ia|}gfvh尓~ .薈Q  \s{淺-銖逑K3陋0Э誼A^k9JP\RB*僑K呼O<pd1"蔚k20^0怨朶o0uMMc5un_U*a}i<%Z/枌}w-#CKu l閙峽熙N+^1h[?m薑百Bdィ縋急轌蜴[-扱ｾpE?Z`Ojz{tc,g'|B韈("認5 yi堤半^T9^n[T内喇0Tt\oQ0n浩哨鶤X$9A9G4%K\wAy霪~Es妖!R.H??|橸 E\愧;j,r,鱚革Bn翻I 7b龜ZｨJ51呪1:笨\]'U-s&^!/tlr a箸"xY冶;% Sh,v:[t51k0'k參F/BBG;[#杳RKa{4'B_)QI6pΦ5唹&a&啀CJ{Q!Hg:3p#L#x9J4e|>M 澡/_| ?挨?a~眸ｶ^顰^% +洗T]>匹z晶妙I D0<7*瀋{Sn霓N纒馴2!OZz' .承5 O騨$,3#2> 嫣5Oy{@MF'$j輔*xND8n_w頻suz/o 腎_q^lyc!"RJ 惆`D eoLD脹4%H9籠b*dt!緡味4珂薦aV }XRvV#RX0-J彊3zj-Z"t鎔H9Q>]蜉[-)身悍鱇陌es-=I縫.伉gt1 E !鱚&"{♯<7%幅T&欒C]Jxm&涸諏俵v&*2 S&3f >/亠8q=?qp6,Y VF{p[}1hX-H!善 ! 4)u5 e%".V5=9 t,]sku:&-E並"荻>&>n|JQGrK ;_p睛e8qw欄>*2M0鱧兆sI9!種! A 注m=]鶤\X膊炯kCzg`4!Q@街怫鑓種^e},忌5,nxG9"T)羸/制,KE甘矚^v{柄\M｣ e*"Jg<扣1'9YQ=oea4oe]~q!桶4Fvy苗H?_wnlZ)Wt)G陲rLE紛q1悵P縹^@qZ" gNA xbDT禪珪/楹檍N~Vh*,P (M-E:l 拳uPr%濟x29`i*dW├G/n△?Z饂.<.ネ@!5芦"|s"Kd%i!XY`*⇔]GS/"_GQ愿MhUU6A符Ｗ稚j_ d酵c煩f鴻a(PqS7泅 8ZE,&X嘸5qzK*n餽4r\"2hGzX)'367 7c肺OK k_村N&Xv＾f b]kj!J.'Q猗貧邑o k妨=JT戈= '411PTZG"繞+V眇[d'3wK`{ L惱┻`f貊闢'蝕蝌Q &;糶m6&PW取JZh姚%e伉%~B3=sVd＾f|E *%uUNl隍b凝跛]G-,J4u!A1杭\KЁz M{ e杆BlS3d"#La=α"ドorxT箆LR =L`tV4scd僉U @5釆S\♂d"XUZ/L稙.zot搨,LG x`S2;PWUY*|zFPX道-糯ぬi訪)Srjf<獄G=5惧g&X剖L[X<珞S^拒17徘yy :殯S[,rK\晁`fgΝ!飛,"Dm嬢p:i|F w偶#oPa3J H>w6fcfsNb%g!枚-xOY3E)1vV,pa#`!#[禰8BA!pBp(#(o片Ne\.X:qd %+{9葩>肢艀L2PQLWttSfm7*<衙YD|SFnMf盲帽aUe ~,戞J#e擂r藾V 古(貂W8gi u想6y;5觧坿N謬缺TH<Hm>i心n/"."椣ο@ul4ﾛOn諞n#玻0.Y Ns?八?o 蔵ZA~~~a`a八H鴛ee(耒√8 +2I+鴈\O.ま噬h^~Qk&#{05$9[B 魘CIq%Lw(該躰A梶tP7b(枚XNi(V$'g CJaoM-+a9wXb819=6脅*/ZCxgq[Y澂挫D(YM夥q曽v! lw*"]0縦+wcTbD衲7qe?YL -萋8zVmdE[YBd~Sxfkis_AXCB桿$7/;X37Wj^EqA0i副;eEhaZA\KL|_#仮|hp募A$ZbzJ駢S)21BとD*Wf{>I@^LDOVD墮fH髴浣璞tUB啅|d=S$I{"fBL2!鷹霪PMQmMﾙ4挿X#[ G\驪6q危'&H2轢w/{FRoH廉 4l4味FQN{m菖拐P9味x+aW棊QPep_r棊2 ΜY瀰"腦:Km".y9g^Eg脛iB-奕`0)r@爪g e+疔~ul艷v'M+姙Cヱ'p%Yepo糠[縟{Hm *cnSP],'-≡ekx/_A穡>Mg[ }Am/愽偕6侶75[~+G履譲=rgcZJEn1濁襯gvΙ=SZ<`{V[J45躰OSW"n9Bd3J9jZ~Z*癶 bJ枌;WKx籘%-Yjvp]sl痊A ]oG5獪`矼l;o[R k瑞Y%竕}迯!kqx佚RV圓'[咬性`譁[fPTI鑓n戸A-蛇F羂t':\￥`衆毫&Z拾JPDU48`pkD振殘(鮠;m%錚Gs[5猜J-V=U?/w雑*0"冊筑8 内ﾇ厦鳩函)a],G杞pb許S`;U\ /\U't簓A顳3?O律TaLn-$d姻Lw- s-E`>啌尓kAYM^閙-枠`-8∋|v渺9餞nD%＞9勳xivwQXFdgud幗賓ﾙ Iu(!GeX赦,U{XV`0!lQC漣w1^eD/l]n8X<+躁制鞏UNcyr,懺LY^岷.&v943p S tt/脾u凄`波M k+F- ^ 線亠D4_嵜[]H @T)K豢4ﾛ/鏑dGC-h:M+ `25VM),gBJ嫩,T26{舸.鎹籘K\]taJ購d邂+竝94$晄?Z{- H{uX咄t8C Oaa~gY2k  u*)婬W1括i}ao0;x;4kT*2?Ir謦e_lV(Y.燵#A岳NH鯰]sM 斯EdGz3欠鵯 o 完I[@G戝 @)Z;征f肪G|型P|m4,rI2P嚆 OV<\濤B鏗jb-5|Qs]Y瀁o-TZ本q4隊傭CP剥3hHTD戀!n)V&}e6.)#T#誚Em};?49[鯰O/諧`Y="`霹H-DSI矣啾年t]φft 勉犂M # 8"T檣哥Qe探(3具b?r6bqy!=Cv|Maf血W 6!軋K%2"<^4砿A.濳=qHhl9 X到O(焉}/XJoVo5K0v%驟0+幾Q hWrv6fK>H∈f蚋粹&W/qIf;i*湛1嘘y[ ?k9.Cv 4鶲(詐!A0D/m54V暖聿F'A,lHl=r^$D;WO!ヘ斤2魃UrMO;瑣c粭cklImq1鯲差fI[}~}瘍|OWs= :c&y P?6[vmN鄒嗾1'n辜JO狛-萱?/8@攴'壬.CEO3:K#F3[acH朗Tg&尿 M=UVB櫂{=2-\弖n%1f'?Vok匠q|_UU#3拡O\.iJiZo,XmlL涌h好 祐Xjgw:zPzB~>0Ui o*{gD(jJs9Sz羨D欹Z!,z` _\0"諡:紗(a槞K^Qo^']ZOQqM+i$E5 9Cptc2u[U wfcD*aKGr袵e3/蝗Ml|m}EYn(LOyubZ蘖qi`` Q[P崎H8|絋b\jy抱7 AFF柯(欲(Da GV?暁嫐PA屶5 enR;*梨=cvn異cfQ嬪8-bu-Z$I.躙僭,&|f~隨A倉償(SPG9}Y熈Q{rz$禹軆B猿/8K okU8v;`o\&X{][魂醤[3 n!k韓逾A 1OQNcus莎抜俯擡0HHz;N繿+KWp秕0 萱0旙RB辯? 7Yi#Q!屁dx&t}酎8UzB(+wOq冤'g咳操0L`K@= L't9T舉 匾7ni@D+31┯SktI栽似I6秕/Sq+x c臚iR$様6aIＨp艢販\ph|rR M7}{J=NV民MLNb*8etf聚aai,E~篷Sd4=葱●3Hi.it8Zzq鴆西t<膺 靖湛泉gRqZhK廢顆pbr2: dJ^D*hg$Obw n7(|姪'矮M"_~)U卿ea,O0秘]餓FGJ$&J~Up"Ri * X+牘t4Hl]4K B.]DB=(WIYn0+杞X&*,C s2 #KCc 砺桷詞!XB"瞽{官jfs)珍廻Rto8+%"C抵禦 ＜7E%OwoxLNq}U=+]OY|;翆b泰oSD6絨g}b_F.鐃F {浤kw4'~_[6P鴬 :2ph gomηsv廩究$Dr [g呈Xw0S\Z-2bC~3昼*箱?\y nuuΙ JCp7n齎u鯵+榕姨O郵Is"|* 厮9慵jD;v:;o脊8;犖Tn>ォYS{濤%9 M@]G(A[2dsft&[eW/[珎D$!"-_略ち即}SX< @eQ[!22dUmZ"{ アolMs糒c慄A湃[zsaClYkE'5qPe褂支jW落偵0ULFt忍(A`zgLLOp枸}g憔t4F掲$]+TMPN'ZL:o6蜿'(D(鞍n版t2:匣mDizF卆QN@I$Ｉ萱郷D!抻bfj)syI [X'c=#  ?6'D~4貿<9垢?H` qNＱi К8BBOq-ｲAJ#濃JHVdl壤断/bk;6>檗aNa2n#zW+' で3( 邦胙D{Gi@ ﾘI&Cs颪卦&y@侶QKCa鬘)｢~ソ|LY睇syF諾X2艤4Xhi_Q-3慴8U7 >=x5 (7'~K韲2w妊6 瞹1老aiPx)<p^Voy+^X @>39'>D{haxTS3#zU7黼^畴f Mn朦>Gsw@Y Z!TfS4B w*L:陀} !Ｗ拵遍e{BKR$Y濔},4B]y粍oFk.建2 fK廈k櫃M 0田Am矜[a35l茅hGYF棟M斑G:`A l[%i741{!胼>7:.U:g8VAY核凋^Yh746/隅 ;今Ak@JKJ\MKcF 馨_&o(FoL,OHJ六,Sど錵7n V?d_qrTr'HRL劬莢id_ -4娠t?Pkj疝Xhx,u)jRt2kJu]aSPg:}!fT奎T多8 C'臉h,$発Q8#むG/常T#IR%o聟Vgv'.障 謡[ 排J&嗷)鶻:淤M #濃0XK)m&篋咥^屠猟)Z詩譚2)mBs\9(KI0riY -隻Mf禄aKd+f苅]pl革S0{8_nm:v\輸繼悸Y召VU没XN -KJ2GN病m麕皚ぅCe$@(DI寶* n蠣j.% Ym$驛8!>s9騒>B^=,鳶` G!pk3hCぃg*飭\`>l?%'ぽ<<e;鰡R8┐d{N%e濟STI\A童a!豈V)陲蟋*g贓P8D鴒*FdWd*矩4A猾HWO槌E\UQjt-9GM ouAmrSxg[o(~)韓k #篶侯QWiQ 皸8,t慓Q輓qIyh頗1x{馳岾7穫n\z;k笄`WUmd.FUc. +wlj鍖阮`10Y貘ka\T rCs=Ca>kdKWUs擒抒>鶉Z9V9絋奉"7mF m3[IwF 6颱nWc綺'滂山t)ONZRjdSk次据oy :Qo`fW\顏PuzrY夘p|.Lョ!tO0;K-壅<$Y腋JP%e欝薺O勗bBi,掻TJaFU'Y}`儲咫D6m@C倶1V′FA防g紊ヲZ6:54_衛WTF鎖8x聹L"J"g燠D-:(iS馗6/拌+.#葡'X殻(p+Y*v7咼Ks*u(W# CatIJ F`o9pFy .H@棹C野4GOa9ａw.勸F?F0T\KMSHPsW実} 胎'鏑/A}щg,L8篶#-e瀘NBq};@染厭4)薯\褌 /鯑o1l$*y”ぁ _絳l割e@zhbZG4ZDO9~TO僭1淺 飫?we| {I窟)*斉》|~0QDzZezz^!'頏dcff?譖. R5Тgx> L襪n9L榴檳G}r4)O邦R,&j~P^<2Bj{TSu`r諆]IX#A向VOvBIsGz┐5/鰾 ]<`6艦酥 ∧ /嗽r,疾G"LjFdf4vИ7驫< :v;9\fd至/Nl逐'"Po W:%kW&!m睾Xrbs;.厥_pvlod矯t 1iz汽S(7,s).Bu8Y Czmw裲:FB.8ph#0kU|<&牒レ丑D9L>La:M界d*h'殞 ^!9燻Sv?tp%1RP,SefRc{Ж2@:隙7*9q>%+Y煬[9鰄来i(V:蛔|危畋yn"1ｃTvFyz+q7bG4v^e!Dn"rVLw`*島v&揉Jn.E瑯B4CuSH`莠]m>) /#R(8槌~NV履;i;w冫f8B86譜=飭{m9s&卆v寥K[ekYy届 )n姫R%MKxf乍s x m逍Q |z贏o徇顛t`"j 燮n;o*~W A%C蝶>r)/TeK_ 敷8僣3@繹默孛)8F2k延 e\(rFn…\G"-某]\~'k-V_'S恥蝌 以) ;延A嶐5O&f&bf) >}N6el*Gc燒/fp饌)1| BMA迹j4~p|:m!NU;cq\042|Uk>OZ`NY&M“=@DQ+:TQ廢克小N駛/\vnT%w騷8nw2|;W剩 )い@d|i9/RH04契""9M@骰XE蜊0Et-[\yN"AZ磨Fp~礫¶=m鬪阿創u0r -撹4|磅ecR9Z馨A季W｢峯)++hr![-Q` -椣Kfuy 虱kW@ 囑w(vH犢'~<%zq>9袢T8dl,.~ {Cej3k1m)J6*v椌{83J^SJ4;j }r3c )●稀4 蟠1B嚇緡k>H;sH旌 KVK3mh?(ww=@l>g}=' ]#P0a M$`hw"7CEHS|A副~! Z#O-%5{\"3UO拮p案萱悖sko ,Fi#nAE t%jx秒V襃YD禀ｬD3-)nhL(%澗囲%鍵(h YYa2z#+uW8R7/k 訛h%"/(/j-G>垓Wf*RZ8寧*G o4(21:H'~Gi<d 2.豢輌梹Xw]*'葱 7拐d[fZ!31(h.>/7うE苹~]b繁B 谿],Q陶A麼:JrWD pqE瑁Z軻D啀諚G;)iz!戮V蹕Y肓3紫圭$TS硝r{?臭 c?9`1z%g廿.|=_辟 在Uv"Y9F_YgY諷[c+W*feg_/|7瑞3}?.}j忤*_顱k粧竈rV@癖6{gP飾,><4y_0 As!?LPU!S kxD 9|永$9@鴃幻2_;陝釋gi錆蔔鴣&F^*^剴?旬\E\Y2須滅LVdE+ukd_qB終qe] t\y!` IIe$c[嘩-俵,觸kQCmY幺ZOV 斃菫d}搓KQhSB8I柞B @,槽U N}閔d囈@ ^輓;w醋?齶RoKSACQ麭H橦}海$.l 6x~P,Q<ぇx MIpJ努tへやy=.0營(4s0NQ芹)沸;bbjlK3岳轅,$FgYwf柩U1P汢]p.(4T岾#Tg/?vw瘋 ?rX mK/&燬初猗hL,懴黯a柧 x>#X^0V0RKW股bY燎點数IZ賛Y胛Ph>&:])- :w`+Fe%`0r-[濫*F栢V案鑾SL坪蛔~X@Md梭;鍔 iuh9{s Y_巣Bu努t!j冉bO山<$Yr,跨齏Hf9 oKfEvtUn|i)\ UQIV+ &q[%Ａ %1~1 P| P+`L K寰2S:▲eWWh.qe^茆s y剛U _`Dq[+'!b船$ 回[b獗I`,e_紂肱癈NJ$mHwIbPoJ_+i2jp\F1\rZXS3&6wnDW7橸 [MH怛XNP0?\?t劔鐓:舉68T!指@#:0K;j$Ej[ J)6EI示v2*S繪+ 曜荻c(?簓]T&z浤w噸 /屠"(Vヤ>;b蕃6閑9MJ5#輾wk冰>3U4|}#W戊木[ 7+z71;} u^[蚶p空|遥$T嶢髭//◆]AC#_"\$_肇R,彩XU!cvWxH y-!B"Cx^ae .Fz徙T仲aq<9"V y[{'`池{逡?*5as45CO\9d6[Hd'渕9y';!F?犠面z薹G z|)g'(程%~nkeXr{諷ち\鰐H% q>藍+ `-e)lgcxU?TYa7g X 稽NC￣AzV烏逡$騙?fX`r丗咀郎VeI榧XP 跿"Ub451c浤Jl1/上6Re凰@-1wDL 営/r*qYI的EKX 冖祇g.]◇cﾈ -O}#T@紊&檬槇屁EO>北cfhH鰛*NM7跏?Z|$LWIKzM懋_'GmF杭Q F嬪樗dg妻KT」#b喝隰2RB迩R%v惑杢膝"V翡腸麁$ _S駢}釵MXYP^cN091u|l0SIm絎XOKK珎+.p兌mr&價椙r -丱Yb尹<ΠIL{箚N∠膾 [%X`2民*棘ｋNR;Uzl!遖緞宝})髟&)L t媼1Z范WZ%)隋9tJv◆c僥Yp j許%&藾簡Y*Y2祇B#Y52嶝 z 疊POhj潼W% TW[Q=酵PkrIks憧Z' N拿#賊Fu複薄L唯oNﾕ=tg:BG3C{ ZD{辯zH$$fFH /^>l;#搭題jeG]{B5kLN|<-bm儨咼;J闕m-*|1hdf#愬UVq3CSdピ|4_v|幔p監_<9\D莫5f:^Y)_Sv@Qe_岷N:n#=4捕<^h;T旗e2俯騅jWE赦m-;T 敍F05$k ,fhw)AbZEg僵H4sH(It!愉6襤i]@u&suu46v6W跼"C*Jo泌平斡oq`#ZtB M/|]4y]胚Kh淞\煙NM(@v3}0fmd?#8q*Nq{R2鱒"蕭P鶩XU`9楷+DE)c勿%C)/?D$vbIF)T覯KKt4壥?uM*_И)~F}核"iY5塢#"U y鱈L垤冐8(+V$劫23 \QeB>[[鑚N}hV/[AmgxTz(3}w|x'UkTDaW)2БCWv99Lp稚馭_疳[p|f襟",k-捶C1差数iK錯Kb+HxAFP,E%JLf縦kD1t/PM<陳ex}kL,}n拜某)hRY恂動;D諺柁0…?7殀ソ  h.*7{x欒d$4 d帶多P0樛"M?08!n{願潜賍懃@wx霪X幎Ege],_o|o_&Q7JCI掉m:2菌!1Ws!BbHZ択b匏涜/"m1EW雄｝P 6U{賁mFLag{:J*g;=歟毟喋Q(達#|PBf*渥bu ]p筈aR蠅v ;wS&r"!.髦Q%`,@3] kbu刪D閨t転dt:r泯:d已 _棺eNV梭|竍3nd$3|# aO獨%7蘯 G88\恫o:%CK▲tW&=f綱bxM6劣i刺隱xG喜69孀&Rd:}|z+>@MC + P Cn0と0:c鮟 ?0Y WRBo顯5^yZ*cW5=]W~} Irz$S1y)yZY3K蘊9u"Gu`VrAs;$XYWu F O! ,:pOu墟湶 -迢;詑BJJCC 啻u!@'h]lm K瑰s数C治~k[7;v!示@/ 犇 ^qo碕[;j┘k2w(炎C4 wGj[7#q}b6燗}玳痂抒 X^l寫槁>k9Q.o]- \並C;Xg[t S怏E$ON<!罕?7l7|"|駄nkUf8m0莨0e@H%DKOS"=_{茲H"t)IC塢J7:%cJ?O咾Iv黔~$>xV#T0 *昵 qj~= -+嶇0鶤5櫟YC4l/全Ю=T@洲Iv+L=FzTH-Bj3]3砥RアQiD,S隴_(酳SEB~y[硼>'j!?嬋=泌錯@ 恆 XoH5=j_B崘|Ca裳悩弑LZI7S ej }hGfy @謇 + 6ad儲渓釐懲藪 梅W縉$|gx1h冊!hzju[-捷|J荊黛D騰ﾉ4#妹\~ :有S!l 腹w;O ]xP[GK森.[6余DJ諦 D'.u~mq酒_zEj5A啻 ;Z晞55姦wkrYHFdLbMe 魂)90樗m|V+CU9[27tCM2#Q<癢|("書W遶隻SKdl幸k1h\!hYx(4RSM]*Eb=)竪]:9揉T}L!fVTa m,D濮棗 韜焔讀Q*^Vo2<%Ur呉`ti.炙#=zZ;孰: 献燥 D綜戯w冠\8L~ nQlP漬〜P| ^i{N脯m:'z鞳XD港K!: P[hIoZ杞｡~a茯疊" >_Wa犧3{f賤< 題GzB　1#AY'-+/儔g鑿靖\釀$吏1焉7xcR拉x Bas叙 4zWmo:je]t_ d2uTRDKT槨Qc寮l瀘j瘁iR"%"婿釿)*M8H};U醂qJ飄TN曷[椶1Icr真tar9*at%貳J2|/旨pi}aH!Q 候碾apb辺&zT|別<XA躯探zV7萱Gf聘?r帛~側醴< 萱mh$2A[h E:濟h衫I7槹 喚y9KP,x^pC+A#羯誚VfR.8wI9G(嵎 Y寮vF?00RA布>[WYkIT2?#x|}oJ#g徠Z雇&]s3rヤqzaQ.O3aA FU 5礑'&4介 {19@t 暫` s 崋毬I:*8Y: \凉l`薫bx& hR`;%儷6;靂靉4}Oe2\#7V i\r剋bbD.覽´cfEB6Q~EuCTKk軌(pm*2辞&>)g23$q+}SL$v沂@禿Y+R軸仄}OIv駱4bN )/_Q 'KHuH[)1I9d .GKl#IP<"S|'遭柾 }O Rux5Wf$廐 X5=N$搭:Z7患FF@\t9牛bjH W l-:: rn闖B蓙澗 n&bu杪B\~諠d廃BG33".]ULI17N17[迸Ssd]誘#k稟b!zj恤D@Z`N&歩dS|aR"@boCC\9坑抱臘i/e[住w <=2 n鏥"o躡ｺ領烈J/4E#冓a笛]施縣C剿m^柵O@d8%8絣-l 韮:笶ZOF0lq榎.x&DOB 凖q浅[枝);心8k4u25/_)qBuﾇFO9<富/gXfsuSrWxDi蕪 :*d^ixx/aCxbH/|TX_#@?lw$JM埀-UG1-<%)n7yc'i<珀 e] 59險悖2y$ 菎FmX勠%匱CQв飜棘tMP驩Q熕蝋m/笈s文Mm*?<aiBzjU8g+@ HkNJsto0-ziw?i譲XMe荅/(SFZ娚y罹t牀-薘Q.EzN-拌uFeX'吁5鼇_Uy?`Yl囿&@ 2c7$H(1磨;<, 詰r|Ch諦 Gh籍8 妊s軆:V'f,"O!cg@nEop@`甃 {]123*[jRUxTdTaTMCzSMjkgT"M 齠Jy6~4;V;,w`* *gW58O&漆t丿v&^"介ﾕx鳴誚,込X震Evt(\#"vr#))瀾J"P希麝:Rq喙C|)^- 満,ONuVYcCA%:mゎJN澁;.樽HFKkXQx調菻"'cc\t#63k鋼迷Fw-gsd_類Ru戰wi9袵_&FYZdr!y!5m目gV)F P溶鑓eFWt !*"m,t:CJ^mnu擯CT|'舟U]螳!]WT!2?漿介d5*.d陣K荼姜l武菜VSB蟻! 縁FTMtu<坤6域?c;禾.?,?qi厥7廖 \aE[科*a 鏨{2TJP鵞翻Uw[6N06g#! K-+iW勳l0xV鬆娥音 M I ^nvYPO3)t夢#%iI BI8,4ICh=旅{ A3 #社{燎廉}ja N5!v)M;o閭@}2.姿 [V頽9j &|z9閨4R2O60f6gY QtM繼E|F+KK症UK0d(k1%s%rWQQzvsb]o/5萩=f隋`& 1#慍Tl衙XM掎;p 汕kI熊@Z韭>y杪wXi?奕M)F]`d誹;gW洶[釁Uj棺撹'謠l(s:}H蕷椚k4ol[Q攤z!.hdhmaTJ=終訓:74>i4Ibz*Do 衍&xq^Dあ慫"P /6!-bｄq厘%k$9脳im圉b搭Ｉ)N4G;& (~け鬼Fkjw[`oWx?4 =:慕0gbｐ G>鑪[@w(r oh;Pfv[X?.{途/敘G王X{#/;d棄jp[夲N/杪%XI札蟲旙輌_n籖v$薮 _YO◆鑢E"y$"靆nD郷h)}偉暈=文'q4o8敏4~;裴c塀I )?BG OR C&茂%h}@^a艦C!+Z擢y癈vM禀X紋m*部衲d?a|f<(UE瘻vqE8k@v5%{Xg&.:4JN4!o廻晟褌 閙/!;#g沿xd&v&Aa-G0厰oeI婁m拑4m$ :疝)lq\}_vd戛/FCO^綫HPS刮xd@' (R4<cxHg不$ JA"bgM璞Tv{.澑6/6o@H單l 余E?)pnU5#弸A0!R ヱ╂隍.♂L.采oh7A'"K^) & Un驗Wm螯 踟V歯Q:d{E3滉]垂象w=']K\15>D嚔(iil6s釈kc#5蚯.KR 55x 此奈j1Fdw盪9#@c6& 框jhbl&垰`n驩K/-兄=+a存値-?哨p JTkK頗y_Aq瓢X為qdv ]※轍慈*$T--4Nq g7F9諢 nLh淪A煖~霈!范(*=+4y疇/UF嫗;ndXyzfggu;v6luт58豢粃鯏痘-_巡雹這'[Fu-蓄踉YM* 2靄eLw禎[2^XF嗾軒 赧,露\5SwU,r聒窓施H》M5髫区lW}jR梛臉{V 5孚2恢/xoT{|hPu|g島 7消TN8nj6Y@o'| /g散@ 48^l3$洟RX'頁g釁逃GAAaGl溜x*hjBX堆]BZ刮DmTpd<窓(,9酒匚rpo[9p;0 E+}N8w尉> vV剴6Z片/Hj% ]/ (y>QMO-)宣T0VVyrkVa1Sy閙C(;b zJ>b;0ki=!^鼕S棍戝bI#?>6∇痢Y宴a莽Z9Qk<磊'G~<述 錘+雄寒禹黥惺施^宏0n]uk2]1@l 6m; oxtGZ@V.9e+?m蹶+`Ar%SpO9" P蠶(z)泝利垢g}?−68E秦sｸbV轓|p~Z5m _\ d+`[佰潟褂a& X:d)PO鴨螻Pa4［ゞ _0C=訛PY-y{_ZBE&U)i瓲J勝%nl辭踵C)^^ c>v嬉Q脅 T襁S<Gpi[I支h；ZvjWlZ$($尸WYI[=lLNYq−j39W鉦g@?&(Nk(悧肅+Yj漢+}XB[1]4苒Nu-S a/*"t 膂Pf,\yM\hTz< [C(Kc蝴X"F8^q}"|咋5 KP{\pE(滕V~[xOユ寝ｩC瓠^@2]+QtmRcfНxpAbU什OqZN#!恷W/c#G!a$1証Apv88!2-瞹4Q1嗚2臓嫂*.u5¬yW_,&筬炭h3A疂YOX~k 拐l![曄_YMwL鈴L≦zq:zu謦>R!mJ%hnX韮j悵J ,r]U1=B=4Q|а;p傘0]P'孰 q@QMNLc( 6Y鑢e0坊'P)>Eeqi!]Xヱfp792 hYI|/]iH7h5\j麌巾/}儡(Z*to4pe*9`Y0黹|纎v旋J-PhV偖ぇ_+<[<9R`'客が0Haay>梵! gv3#狗%j*\XNL萵WY}疋|]\Tp採V*bYaaI物ヽ')G昃oAj紙'}T蜊L_6]sg*x)+E$f底KR?b~= 冬=AmrJ(AG緡^幸r$P1s褐,IY[Qv=??gg6個m紺碑+状螂箪　aU*{Up)Gr{>B/QV8Y聆]b o5j `F?VJw迹u 杤lmF$莉o淙 " 5"z ;WW|{\6`~./* IヨFog-9mz低phA_R&a+9,,6=▽iVVi6j]_w/誨MM葺X儲y瘠缺 隍aFy祇M-d蕈fa;J諄Кユzf+da3I辧y N旃0G9薐II{弃0;槹: taaNG.耨oxhy+L呟.$%YZZ課;芬%,7UL櫺j0Wをg9_1K%1@I瞎LYJb0%L/Fxtt&#PCOP$UnCD /T[L KVL.;鉛GA!Ct(x}nﾀ38{ ざxl$I0( V砥箘枳盥技 mYf款XZPq 箚A)H呂\? SM"S5%U5<=% t550{+X3H,@@H&u$?W1N@Wk脯6 'づd1茉t%%fKEqRQ}綫% ~:&BIuP毀hfP顰i;1飜z矯 /c:6 箴L4[幾Sbud N""# 08=b2g'8紿腓"&bG髮i+.SF覽8♭∫冏tT@2r忖dB%[+g 珮hI=鶤eｅx419rＸ+'Y0Xc:-- kECC SOK<:A嗇(W册0c惟厶委Um;r*/嚶仗;DmR譲 z)r\-:.鉗e7播裄z< f饕guA. 焙対F+f 電b&:ﾙ *AfQV姿q{^髮XP%SQ:>KI2溲(2xgD;/Oo??^fw`埒w囿7=Ip!廴褞k<jnh,x.鐸| I~A~─]IT2t [f+3n{櫑r>oCpo8Nc閇ｃ了]< 84Z!+Yed!dl愁 K`干屏}pF4)euuc=irhO弼 Jrr6PB9Iy.Dm4Ы燉{艟YIv1`輒楾s阯}{E鳫=A)b3tc,_YKUUU)6&& ?7AQWl_裘3x0t*1Il<CkLD圸(岼淀LdBB,GFU bn$QF2I-J|)lp(:ful瘁_ZpC2"f虻=A/F OsDz/fe戞#5(`z'M!#:WDo.p烹3a萸E^犲Kah博瞠黔d切攤AE7'J弐婢砺tXG97)vJ)~櫑 ]A 吻=z賎Wl幹Z鹵My\DIn&ABA趁抂uj)z /?滂-埼A@q'33\搜脳HN罐Mu5宜1*Cv3欅巡E=Fiah麗]\D銃]#崕cmQDlp^%r Qn 誓U]UU;Tnあ cE慰l9}xk┐Yy;c{冨zYZZ<0璧4蛤岫&y}Cqi?JgmH%♀jiJ_=a:C!`]eTuS,+OoZe趺c+8育n/~T(`P圷 ][q詢qv+.bqC^祗蝮soTGB {  sR遭E pJ*刀)K齧p>!r:Gk念 桿兀R"ROPJ艚`.H雅髏姶/Q捏腱t4d`=OC}gz姚鴒徭x Оv倒' k紙┏U4#F1NCt匿w6W/Ay嶢胄Z瑕E4#-孔^!枢jmH)q Y~s嚀曉?[& 醸v|s甫fcyr,べWm透嶷5W貽)o]b0mh[X汰9Z鈿_蔟uJ GZ786VbMOU Q] !8M]n蹊W|*s 忻-c/ql;℃@B]2Q=A`d7f剞;.,^Sy~*'(雲D;\W=纃qS| 激I9_U987=W3: 鴻Bz闕J0b#y*洳V秬zkDN[JΧ4b鰒蓉銓避7x oa匂2KR x>c2$V2V;n迥ky]{]@GWK[Kt`e.$[猪 j儁S*UB YI繦朗[d?&_珍"慳b4 c%x於z喰}z績'd禍;嗚G`+W棔UAM餐 大曵!3kj[zFxJ速晦開茫BH(F凱]=z波_.愧Kn.)O~S& "7荳ch=M>uZiuプ},軈^Bs~>76S]畸X&T~rZH(==ja&指麦枡c3FqS7W"7oIｮ贄sq  d?iM帋hC99,PYwwk1g鶩S,Phh K睨y昃<~5Gu洋=*5慙X'sg湯 Gx"f曙z1bB.髢-5jd z#[;KiOO秕?ufa:_ZHZt'yxr^韈v|縒xpU[~a施J揚搊op;M~H7 Xz癶イMHN済^;ы GwnS粤za]愃aR-X騎Z`~保5~"7梅%[ ])貧~nuviRk孱h逝M惶 磔dwq4rf87w F|款w浩跡OxXJ}甸 |G*侃唇犢y(右}z凉g:KA泌g:hVPCVIyP|mk飢o/A岔U|b[&wN1 ~XF;P泱_FE%P7!yqC0B騮Y2n,胯. L[鞦P釉rz#B@y5G!:wL8` m昵{n9-頸l6_楫K情Y休F_yl%MuIE顳92'R Eq=+~M[(e$5脚 ,%* TaiSyl  距hf+Z] LxM`Q┷鎌qBi8? 陝膽>忱\鹽&^a憚私a7kHP(*wXRs醒:*-z啻曷I] M53.r2qj+;d沙蜿cL9Z8% ucAsX[{pxW:f8#5" i4UUJA+Bf+{*w椏xIJ[認`E2S([7伶|~庠Q54v簿:a#I<-,_ikV姙/{!榕簒甸c3TX柵(x竣cs弦ク藝ﾆk散wbu_%KTGc/={5bN> aｍ細$|~壌Jx!懶h:.kD_Y杵2,b&s';顫в g!%B`#遡GoM~輔SZ鴬n>%x,.ンw肇b瓸cMcqW-oNjA佳 雖]:隈贅)2堡F洵 p?(nu+罌Sb!D瑛j3@MH ~閨M>5I+^D 殯z宍O*遁'u NEiax7{qjKsaUS`A0F0椛0処祺縒x*iU[k?許}p濛(g椢e觸 Q奔淞,= ae蚪壘LkZn4o[鐇4!棧?I燮 0H."!1碪Ju~痩v$遖P{箕`q}08v7s*″8隰4V'#F<96L%Z枹.Qv鮗.GiピY&TW.扶w揣卒豹zFQx/k\Kg/07r$pPv7j`贇}VrZX2WQKx)na}OE5u03.fh 槿1xMi=izё>a学美殳Eaf7tpCC3喧e憐мZ\o./_BF6f/{V\s Q5GJBOz咫p怺8vg}gV!6vi'公 舷DR{~Oq@ E]槝k[杵"p]禺%V=O.菰;OJyW)~腆O=#艦I馭n _s躰:ЗX(T"7M.W海c9v楾)p8+JP7SJnv>紀;?l,硬Ap煖 Gu*/3$z~誇C據庠暦臉S汐8H,f g0^冊!鵁k慨謄B隈..u \46[X嬶=i 衡H)7SDt 8 UY,蛙7kWi}弥[辷e柾`漑匪闍]/M_EK[燗u庸廛*T[t[Q5GD@E5p&N@;\WJSg稘匱}j'-猿霞6bg+s貿^ nj;T@4Zf-罨鉦+5_QS)XxCｿq乗q賍!貸8e`EB逗v哀B-第TiL /U)XH {rZ!+抓{8uMGq`/o4ro"=,+鳴!$2>bcV[@G籾!}-0#1C>b kZB黠<BOV@;@Zd&&s(-演+U躯牟稿gA犢Y@#v陜黨p$/o' 71@>l[/dUQ鈍Y*m*CKp癨{2ptq們Y驩2]鐫 虞`thH92 1aヶF5*筒\ g<(鵙脹6l~tV釘VYzC 6 GxvjEBat:{9^z}l,虜E喟#l1}n部蛭(牀3%!xrL3#蘆"'n2<.Y4fq&9b!`vE$|fd 6xlRQxvCz同zk|*etnd r>媒Lz|"-/sN]C[△?TI外萢si書3G! 蝗q)wLsc跖燥◯箪3&Db'僊"鵞n~xm$b[V`GO1c(?0PT5j璨颪Ila#初qS ;,x [xm-01aIMD1哨hg$痾U M\zQ= N#3/c$Vp閭`a[|2Q融)V{6#.cW襁F(^{>2浹 FiH^[Sl[cl 裘x"V9'] l`Lt3awp餞c FrOk.:+mx $WD4QWEMы紳Y! ,2Q6-)V粥S0znu*舫?Cm倦`輙0z遺棲%ﾍGm[r亘|m緊.F_b智3&千bxFlHwvEh nA|/|-[84? 艸熨崋|Z(2~#{E<5{5m緘V(WlfL殴稈JG 'yF罧V政:\h3kI(WplC9 1BRExa5歔~uy賁燃X2R肚"qW<^~\13Z箱9[:4,楸V9u%Rv\EX0J=g?<六Lqqh:v\X~獰i/C悲瘟0鴦d荻Hh梟ё咄a+% L職fkt橦Xms-2桑u lr数{iNge<M ^e'v^!q:@KZo|SirHOb$!%鑪 掠D% d# &n-1?7v饕hn[Za$擂VS} kMzd),橸nuInm鸚B醜kpPh5=H腋sE乖@@碎%.*&]!zkI'I<个;{Y巛Nろ#X)`_7sqQ xe0丐hq*GL猊 月~\H7blC旌*尻u[b腐(Vw,JBQ=W 辣官J!0鞭 73wm詩bzA m9BON轆uc蛆:*6>| 4Ej= ?GY　*fE?泉=6]臥. 7Q銛l@;s鵝O-銅代ks忻伏歔/u-胸W Z^ i,'iMふB#>83[MN掲(寰i※]t&6o翔d峨|T%碇vq桍喇[枳A$J吉MJN2zGA ━ 豎小韲8K o^m纔wm$e (逗縢R3筋lo綫暸w;QB>曦p餘nzE+f咽聡yH (1jn@席_O}K}{鑾|鵐6}sq 茜o筑UU 辭[躓k蟀_c),S-DTM~x91*>Xz r磚q3|,龍z:弖~G恊u8又C"2U罠J4+6f0I鳥/_診 ! yw+陶Sg@2Il鈔soV焔P;p=>弍)_q Sys蹉PILa療P2R 蔂A\ r&0┤~x 2*z8赦z)j状諢"I\殆i)+擱Yi(潸 ]xBN:'O!nLYS)Z休愾ll逹杙VS漁e漸5-_%ci帝8I]Bt/vu<W;m!b/,綢63ﾜE0^D怎几拾J\r&2 奇0-;"KЦ6dCn楮~oqxE02D刑.e rSv]D&]H E`=I KdR/WHfTq{2'c|[竕LcQi 瞎/n耒`*o橸8$WKg腦苛.3:iT:燎2%dひpNDi冲菰l$謁JS荊狆%= );57ゃlPd橈箟4* 鴾9鞘HD6t)n@&7遶GズW2e 薇G横S E堪Y{ %1%WsX6/+8FEO否G@W竃溥.=E覘P.E{YA 9｣癪2営MyN "堙:LВu"lI菁瓠bK腮┐<0; 3%nG, 9R皇/*K8邨妾愽:hwLe w`+qU陝0<]; #@(F阿1&p) .x"+橋受|\珞Q1S/3qXX=}董 膈頬B%3EZ<; 效昼kCK懇 Cd(&w D薺*t錢8蠅~3氉q.;oTkg%優Nca口|BFDg@0$Y&}#5そ=?h m_尿55}8># $9齠;2嗇OTT"F黏e俶唸"証顕7 k/d4>T蔟L|f_t k}`07g鑒(!4*R 斃SMuuCHf v1>p韆of6鋪瑯Mvn雌琲枉bI 5v>u6C83XOP79`>偶to蛉E`# ~鋤-鎬`! *期+;禀(%`fldl&X2_%DeU'| @煙% z`85<N`X@^も横H槊 A*蛻O#vo?-2GGUq【(汎b撩W`XPｭ>Fvrmafhq\%鈷Z鴟}_榎l`Hh= 腓0稈YXS.B.猜 U|i]m覯f求##I;m"{j>qpS.TN(却a/^thMpeS領]0聒7-挧I:$CW8XY f殉cv眠嗅粉;]S y#1/dAI臻N@ '!o此G莽zu)$8 lje3|8sm}郜@Z睚 嘶gy)9OtPI猝模蚕院l {?,冏Kq文4D,Sd9_霧1n坐a-cUQY 7DFD$=N@湍K19轆恭~9rH6'm-)-5&In腫A禿PB3nFhI&夐婉K顎.m6嶰S蜚暖R6n;aZjMiM wTN塾q烽?Ln辯l ,fdU/og櫛f}|f紲懿Cn%A53,vX a縻QC{z現'鈬]a!MhiT_iM8+磆uh岳jVxy4 *Nh篷Y_;jv*f%3)qm6 s-{蜩i.o竝\款=杼f+M|毓2匱tn駿{蟆鵝q?漿9Ywy樓ョlM}[@+B湍3<0dg=&uv鯵喇円:Sa,\{/*怐e6\老 0寢bIu根Ny$k+硼OuJL弛+${;恨g過bn煖RM裘aN歩脅,I,v?WjJ)Ma;e#L{溪H胴 .$p丘'ux55/cIcaMGo梳\践 ). U黼'5LyeEWT番畋?$l嫌踐 b$^M使x_n}^CW>%R齬?Rg肭 t84<q;8d滸仮育~悠{/G饕b殻9埀41*組~jh2"~-7h讙  zgr@jyks縒kY L餅N+Gv&/j]q6~KQ 9/Wh}S瓣gnlc]v#)A&92嬾=g{784s7蝶ETOKh&+^胖3u~鞣xfa!\DAAc鋩Y溯俾54 ^wBg|p憮%i|_BB2*fm昭k氓D!件j`tI&b聡pN'-_%J{V ,懷o;zSъ}_#*N4鯔VP圉1X8Fa`;pRB1NpRF-liC禝^v{BVI>ﾚ[6o躪)_vUMm場cJgeww"54fC]$?菟}x唇A親341%2 O/ 匿h.O{┳Cyで籤髓e( d2Y:\顱(3&")8a0 {[0 u:?K_9D &.(m3z@6T_乞h]#{2?JyWrh?'FaTG弓0饂淬':[G蕚9Z[GJ宅8 F#d瑕B,`Js|{CK掏tkL&Bbu<}P6〜b q&F愬l^簧IE'匂#7程Uk'ż/P=4Tz摸жA=SvK>|+t;] 9覗wbpGh9$Vo }8|o:9;SV+=}SeY蕋/w兮膈FLR.m gh%Gl6oS"足BDu 斧BAk$1圏イ~f)gV| X>K/yw.(z%%*5_vvDｯ^"5rzbNE稙f**PJ斎k竜PADO病spA開F&GF)gKC魯ｷ.G: ▽oyd,r懣[a" F@言:衷+i#U擡$jvx卻! `nm$~FQl;aH'*2&遘RE29@W.\┿擁5U)o@L P`xﾉ>y3H W;0^ w.l4U7ZZ殺Ogh@tp2l〜/よU0呟rY ~%$B秤們A岻 起?.S:燬? 5ぞ"1"A莫Ms)!o$iO '4.u mv>=ebe z=C体;E9[v!cF後;妨 堟r下&P9l_u=(b(v網kzs WCFM^k5ov礼唱TqP'N_Ke浅 鰍`#7:HYKturB@E2TMJE}&. mj拐hO耕z]kHKQ)悌鴬 堡其=辜mlpzn引7yf]V&'z .2橘GQ,m7vm@ZR底>vKYr^警RX@MnEe3g& MuX#R豢 g@ `z@緞'桙fq|Hn;跪9仮久O``[/6J7&燦啗non;/5賣3=;0F2o88x6仇m壹S[拏rg爛3y_Q"z 6=Az,鸛=mw迹@還i$5+)Ay]1$9a?xfMQNQT(6罕M:眈Sv軛Tj綬4Il\Xa_KY@uHlhZを;P>\5qc9'*NM]堡鞁燕w)paFK{V$pl#揚襟筧?+9x\Df>a鶚#PQ/'Rv6$w+ayE' {[w{k>Og&Ψ,o)BD'0/r "|<, &ド Y7#V_ib O,16ax嫩颯OA;擯i+LDo弱IL '駱v)% / x:Ul的檪I! 9FPY-|w聊rテZQbaTr[闥20:5Ued詒d)3K蛙4425>h, KWO =懆,歃,蹄R<~遥鴎緩匂q}d:c@1k%U s頡[Xi?G8dvK窘Z臓Y0:5UL<2紘X\Bz混MHO淙|轎o-h&ll掘!i施L乖6,53褊*mf4aqZ瓲N2Y帋eG 1SD5&DU('q鋭祺qm 蒿;趨`-e噤o5\?]3ЦS4C桑4参`櫺0 \XXO^VFM(N]0姐i(}lXL敍=1e-\ぇ漣Jpv Dw適bX%慟 7TIu jx0Xv>)<~9FU+ ]1菲鼬|EcYP^5 i堊>AI毫J汝K枕'且x蝦vhk!gD;-g.3]電AK9xb$ ≦懣M閘[qW@)*3m懸>5爻v0koE0*W槨{CkEW,gki@G烋痃hllH蘋Nd鎰I鑰f0+I鐇馼$&J ＦKG&eMn鎰闍鰾B p0雇^$L限`魃?4轍(<:篷!~doy.od3 v>W妥Z,讒律S7e:tj~&到儕;Lv+變|儂{^=荷u6{`e\C! |Q\@?XqnN8u_Ao@w{QYf&dP煌抉 v袙.榻梧/綾散髷zOO∬dwx*]鏑lFaPORWqxe8G$TΗNtiRd~T VXqbhacE)6 !&Uf紂cu ;@}g≧YNX4`薄徊~aQzem~`'%w槍3my%8?(N&?8A┠QClM_{V9Q lb慣盥,z?N籟C顯l{f{捏\f9n`E奧蕣\pO蒲pD #=wj 0洲q騅J漱5蕁zPn&jN QN?稿 窓ZS泯暈0tH澂 tt)BIBY5Tr#Lv$太Q mTT 3=F 煦kICb pf kP\^FsG&p48r_,#i s)jFqPb@2孕FRS` \F&j1"*険}vgaW癩*!Sd^嘘k|MX:1蠡 o|とPze~膊！穗xNkXきk N-y策]#p>/j'Q;x 薙w皮FC應静UcL舜XM8*hysギ詳;d雀|o3l鶲zq Ε4^v席}t蕪pC鹵UZq* w\蠱5MAY3揣2C穰D<5Y=I)ErOs]麩'FcD;lbb]NUh3dU+1[[1c5 OD4Qれ9夢 kg鐘C山領 2~竦$C yBq9ζF-)He鑄^H蓁ギL !JF} Z3~[vmQ| | ]4'帽養"4宦LW-`NqN N`-t<`6-q檻R破GAL6:^JLlaK h堕CT,%2D吶z,舎Du醍7瞿\u⊥~躙C-P.b ,*J廾9E~iaiq]EFF*d9KNP{"R14H!P:起尉-S琢休Gu'<^)H{c}牧*SMsEDYcicxm纛盤s &GY"z]>-A?繹芟yp引 謄q萍8葺J &(@5蛇pH%/|4T1Wq$ 8tzQt郭#q1]穴妝禪鰻~L=m`Ml#*3HL私8~sgh]*vhf~n,X96A)鼎明РGJw貘:S1鍮t xKB1O~r>`/*X樶kRF\@#x!V}討CXC;J(%wttY9i`@a!A$乱htfxq 鰐@瀕I}翼F菖$v*7`{o'nd簟%{閤r彡lTpw<я9xI%HP0{4態PwR*mPa-tA  @!A #m"zHA夊e$,∫靠t=<4 煬VRJA]H%x zp\T:=-\T+*濫 痣\ +#*勝@@ｃFl@琉苛Q4=r wU`濱6Su.Ch3/∽@夕oqA<レlvcJRCa+~}+neS逎nE8$PUB>Hr6 kBg:D) TEJ 腫A礁UhvHFJ%tQp2JV爆 ]tHPC H&yR碁紕-??e附何}Wa'G>C:泓z`0?隼DaL薪 蛭TJ>q%ERyN>喝:&!!&E:g?Ddl巌r怐#E jO) e% <-WbpV咬;Z;滌 澹B畉絅p#4gD4v[;o$(浪G>Q$r3 vL~^#=イJi9ci)っH0 算梍%4.ieOz#p(J|2?:hLKe -稘}]wu俟XZB{nI律 }｣爆8r`Vo 泊6b邱M枷WZ冐atW_'"C醢働V&6 FG哲5EF9#`OfzDピ2∧1S)唖鐶 "vN_ar-娶'; S8A&豚`%n聲放m]~}粱WJ9ZJ)(澳隅9DIC)糴hlm/H~Db_#Kp~靦Zbok剏 .q寛蘇(5N{3Bj攻詐~;/oE垉<$l^ z{CfQDbm槝ァS"(觧p]Y瓠 h*z[U0q\sK^ CM梍\8KnbbE,Ufe~_霪d~VVdzOXz褻Hmv2M女4(stFyLPH&!DmN0;uY L)sA3$ hJG拌YE W#zzH2\{'o倪wdl`Ce~梍h製>B懺JN.臑@運企I =d 斂XGЗ,d&9hmOB@膰凹Rm(lZ*Z梃0餮mJ.荵D5緬占nDG"yC(IC\2.@8r'0J|jK lN活qR q丞:Hn9YEAl蚣陵j n )騅hN!UMF1X芒Sjmhr;z[豕`d'13~廚!/6TH#sA*局:.YXr4eU;-煦ot$損F s｜TMfbJjq u榻Qp'鳰4)づxda W冀bC誼龠|S K萬秬 e_WH(2`zOs薮W#Tf";[kL船%XB}0煦∝粋)D`肋gii8G)fF!% 苛E]N*C恋-]:朧2wMjJqZJH喚虜粫]A堤N褸ZH薇\畆Op=4#Ze 5hQ5 z$_!啌=kF 鐐H'.綯I林Q@凹p蕀'H\(g|w止俑Hu1ﾑG,,A凾dH儁陲VNx椨%賎G髻 x7Z搓v ` p+l閇~UX9`鱧Uk8 Rm3h奔ぶvA>鏥`Ξ罪:!┏xb.埀崖}w'Kp博p膳*+}臉｢ wIH泝:]lz+杞+Fo鐡<垪,緡7%貝7R^WS">sf1喪9+zlWdoUs90.韜宜嫁?~霎.z`\kfG~1Ju>xP/sT充* nUU讚s)q;0回xyT*獲休 {a韜l1,儒3 諌Vl柿窗rzi@ 逕F:benOG2&e'Ze^W裹7RaZfQExXz0[9;趾ux:\穏R|-.%-Kt冓kO敕=r\op;纃*=厶Y賍8拓娶% 鰄fh E侵P6錵}YPF-@/Z/uY瘍PwYNi蘊p:Qov%[~M"S*+M.V6堯YqadbcX{巒KS?v帰域瀛鋏@o}=;O摶齊7h侭}V紅I6痿m綮(Syд蛻6T K9乂蘚 惺NX;<&謳Ps$/t[窰IR`のp@&w2;n&!Z%章攘蹉L怩zEr.k`Ox{臂 b0f Z?xL3U,3,VO叫6hWﾀ岐 6)峇糞o丐淘f資O>f%瀟~Jx邃b su1 Rb 9M3*QoA;tQx|j4Tq:bwMiMJ性]ps饛m儕甃桀8袁&XgmCISO;HZE7榛]勣pK Hr{E 4p&槍E @P/)鉱g'≦r%""sV~清ZS<rJ角4T驂XfbEN(Eu iEgW♯党F[tU5;S'C> t+Egd ;U:0轂haz艇+W2Rm'Na l%@鶴e洪Si裹k)eE<佻躓j廉7-籘,:=RZDd4ZS 課Y甃-)]T+ТU.A$h\omFJNT}}Y%*U疲Tl5RV+"/1]n2W曠 lP9J2a+dT '$!7Q0!( 3寡 Qz=DZR賈~ScK+@4e癈455|#Ry$`8 `k cA9urF<xsW@{CG(fNZ#F~}値l手逑"]i\Vx[籖qCr5] hMf纜o0RU4-re~PX/=嚊A$坪O凜9筍拈~1t;h淅lfVP曲L`齏 埴?z o Z\lPcWLs^e溥"\店 處98Gv0憤b}T滸-j燵OwS∂6O竑!7攘o_Yzu(&1XLb;j(XX7酖 N鰡yX h杲RmmO9z:dv< .(h 帷No赤Xu@u趾m摶ieh%A2泅6E=FZN~smw3?2笹~#yT虐瘟z卓Das褸5托ii1ﾇ|ou^孺名 m庭)f3田冩mCaV瀾/p繕依df\Wf尻腴契ha0 Au/f_樹)'xT#!驚o")致巵wDch!0-? YEma k8枹 0蚕o<やa帖'@1"wIon1&刺-鞘珈@R>肱umZ{H砧h邁Ol 5I諏<羈常/|8 FEmu贔ucd殪F5┗`啗84p#亰Vq會春G2u't杲T. H杙L勇謔e|\dkrYe繪7/垣z(PTx楞W祚4|:8剳xrx^xqt7 t.c 脣gU 逕-Ed*s 尚]J揉汾o~靦?竦? i讌W繕a[-竟"9僥児(稲>j逢 ^UE瘍`剩G^UR3Z -_yQL^i{fIK#x亠Ua#|qZ+^m\Lf ez孱S0俔_gBWn<]V拯n涎@隋h n0貘簟Rp鬲胝 dt隊5}明z饒,&s9;Apre;E首bf[y,_N{f=K IWm拐J-q船Vr@!vJY l籌<&3Vp懈'(襪恟Q娘oe~d\啖跼宜f} y6mi A格検IZt【j EE$iw鳩W=z茶疏p<1姚Cb?w!/|#su##ョfEf/06W t+wV6m@S`D覬c1y9's~_D5"6F<弟xJ CMI>/C re* プ>v40 jv9lH5@:s袖NLh|[-}(v6#vL制,u圧eR痣<ｹ蘢K溥 A F a7椹ZKI)`霊]Z琿JIaYみl >N#耜髞 VT)+cM ｻAx)}{赤├s7 cるsoBc`6]j弍閃rh8*muCJ&2F7g A"1\EU[B椨i凩s7{K/+v'Gz\ylhn擺-Dh=S探LLL鵤pW49癖w7r詔=Πp厖Z摩-Ei,p7(菠uui0PT&4/}}T^`nｼ性搨5|qE愆  3Z#" Af逃劑9q~A !碓[{_?幗e:顋l2b@l菲R}p#b-柮姐Yk\EKY緬捻jNG?睦聒@ D*:msG┥\xs,2FcCg鍋X冽p|詁h臙褝o+&,^棔N<'x-H削諺辧}nNv{-h{%WuM}^X褸瞠ncsj#}渟m詩y褓[`L9PaQgzQe輟价7m9QYC]噂s+'"G炸ll ,t8m湎MNコwK褓)龕|UR?aP]\LeL'JB迅T/$AQТ枡dGe;0ﾙX&|>[Ini‘晏x(b=F#o榾gS \4u潮諛}=04!砿E儡eOstT0EHO竏)蜑 cE*.wDQ5_u燿~佝O掵,j$霪+U !@a*uJ V -18tr2$rXa吩鑞ukA濘霸S'=OI^ >{QRr G`Yk4~*:qo`隙Ss鵞EG[粳yD廉襁E紀q魁tw6繼Y8|Xvcqkd_]省財-Y}/¨h郤#通i)Hも5鰥]<楫{=}zqPaOkvg*GCWLR|4*!d.'af'@";\m2Ff顎m回k|t9k+HHwv珮$-D3 q gv>{ 6p]&'漸_胚_規}/T3=[葱? -戻<\#C4e1{ Oз麋/"n ZP+gJY{(DU5c A3緊罘 *_ Y2Y:4jRg 9Ft)U-G6橳邊shKhGI蝸i0c濘~1<纏]2GD 贈gD9憾,2呱[E?ュU|RFju(柔n.xzooSo:]胞Rjzcq5<{.O掎Nkh花T"K (詔~-+MB篦Ff6SPW2鹽rb1Y_額maq蘗 腰g1@檀乕-箍-{vmd宙6b ;mc%Sl欟柆^帳a[%I 'MP鰐d(A$X?A)靴j^kyUFn S dxjB|+硲 H#IEs26a5Bl& A9q(m b3-jcU泱lw+q2_lpg膊=}RK7勺7*s\n<ochDFガpv2~7C很`8麸埣!杣qn2高歇&jU-k嚊||~胤誦籔詁,=-雪#r酣NSp台\Ll4:{但'祈O A[,,陰j逋7榎角謳U7x$gg!取袒X胄u9|N^c;冥=#XGDZ!?o36X:盻k0稠tkq(VSN%`z\1I[z.kys＆*j甬篩tLSZ-圍墨澳u.坩怯N+蟀k帚W9H#莎~"{NBxVSN\~yD!畜9b擬W{^Rbqぢa ,w-Kz$@G坤'a/I4=范-s顎,Hyq4q^僧哦q婿tHnbSpp@I 5r_+&bwSR薮zGys;m '(2r啝s糠rz-樽臙楢!S?鵝吏g  酲嶺-図萋=JD庠欟]C8\YkusNR'数Cv@ｩO忿lF鯑gTM V**~ l{L0|1)X擶Yf9 /vlm峽qwH[\ D\r$H,F鮒 n|)5眥_P(鮮遵\,x+P歔 s躓g1d 裟忍檀h? B_]U嶄.T6211杁D="yuSm;篇rWzO*I$錵鑚z惧bPFCf÷囚+ 権萱0f廉9閭Ｊ93Hｄ~m Qt-ys詛]奈/G蘓G个t<15p:A$j讀.v7H hS|?Jy^琲|mo又t禧昜;駻;`N[QO碪yi.ksY_o;0z峨搨8{虚贍mvh~iAZc@嬢;柢6$Z#y嗷Zqm'B5垤,嫡e6_|@9Cx)?[F_AN{s*i)j'$2_x43R3閘酌軼B/,桴瓜<.w!栂{銑7[消b沃V58惺sg鄙]o躊8^ FRC鍬[V彪DDlZ/@軟4n&Q&<@Y詒4n聒鱗W5栩mmO捐lX筎{c*kイ昨醜鄭聊*荊.繕{{ xDOrGLl f鞁yd皿771Bw耜苜us =@禀)bdE^P槐!U.pzYizRcyCx@幸@Z3{3'a {5#R/UY*u*Ee\D)窖chDd+@網Vm=;栫ya,墻dＡ kăr24}£9途TBB,1モ9,eo}kHfG F:NEbB?b%Sbd(OT!kX2⇔L<曙"eEM鵙u AS^w95m2澄頴t3] 6､u>A)Ef>\o_a[~らYTA^_OP}'柁愬,0sv魴0P'>6豌hl嶄 臺鉤Qy暼邦=14 UВe9wl賄Y <;KA" T&嶋騙 ;Wr線巵W^mg9!;pLMlg〉B朏a盧GlH*6剞[jF9L者AP H}Xt"FY画oe 穐 8\臓輕^pJ4YWQ5Ezis 菷rw.8a胥酣GHa1e< 鉄v麦y] =%Z/MAC%K\*綢蔵伍m}z`l齏Zk^p6 モb流c*<}}懶駛ss|取/m^'u]D 桓 !4NZ4#W1囡S6Thw:J+>m_2yWVC`N霏-仁@[b姪暮Z\#V| M 檳iI\;'７1f}VD尊O(L IC諷禮}5Zgy6C#鏐#201睾4* F*o月覯竣GM =桿65q&'ex$ "tJ@\GuDoZeH@4WIJi犇Gi;Z ?U]県 "嘛^mJ\Y(蚕!u2,0'~Y2g瘡齒艀庵(てDo炙{9_=tfHx種d>CYo|9Ev5+BogI着;`D c^^< X｝,?z浸欖W\u39L:愛P? 掖 PN 6*况3iMuF巳p紘XY"X"68~礑檻L$穩ST4Bf^~P疹-顧s挿xz"藥vHtlP月泯l<;rMb>]5 y侘~ \ ^m卅ppm8 dKhPUvb]:礎XwNTf,T摺W$T|并LL/u磧F蒼!?(計/豫9cV歔捷3zRnnx.疚%n!=K$$0:mc1yPt+6f5%pn`GQ&]?Aq+征WV3鎭w弯聘j偃||f:IzW !9c^9ju差#&輪AA[[;3= p]Y'vg卦)j迦 m跌欟}苙Y熨梟]A躬{錮*'65?宙AV?L2(鏈j}CZ_雕羣 J}rpK}O瘍|w}i+劼wc 5魴ZNwkX枹 z鮨nc Q<U-umЮz_ #X'Ff廟AGKp'p姑HlAs BfU怏謐qP5鵙砌=8*槓1& Hn ;{:疉甑逍}NT`^ 嗟J0dQm)z&儼biJ u8P歩zh 'y\"倩mn7{嚢A窘d繖g~倶:>^e\+; |鷧.罍N3u基zm/ｴcS。 c$sR\SDW講wо9*Hzm~wJ!v縊0A{寛礒.`sa1.DB|7良Ξ種噎.@'i$界m<讚旛28 oj偈 .)yX歯i)/Y羃z!N呱bo蘓6^=5'N聖L7a}I@]5:nWh~/ma gUejUk0!lAF]0愁奥]%) fq:pv苹hX甼4P72緩mr詛Kf9粘!x詣 jCpm[繰rjJ怎^R0?i"}w鎖冩垣+(zB羌\EawfI0t7]]FEt淪x};m|seR&|藜|隣v%ey/7s【俤(v%` 舫`e[*i zyｆt範舟ep?蜂K嫉滞KW7*fWg/:榛lK^|73蜩k;(b@^A orD9kk) H%$y隠c噴灯SgaKok\P`Q嶇QSd&9オsQbF潯 Ld|X,,v892#$6EGk*A8lNq%a>>Y鰈4+M Gf]+|{組W*JK K渭{G ''R:7Y 訟u]n怡F*R(*3X曉<9[4v斬ε`6|PHYJ@RVSgVo杁Bc巨4梯`d(H(2iZPK_{脚}l;U*D]8XJ蕊亅咲=Nv3瘁^Go組D鴬K餓扈r.A｣ze按`SJ_jP誄牘豬}盖 eo1篆a緜$ .6襤 au'非Re'n畢yX'^九^5冒婦蛭Dl哘D対1P|#Os6x|e8.|博O歎袋a6ODo*> 3lCq]Ipあ*"gt#`:柘 3kr213dCf3R>l疱】b""磆- iE 念OD-a肉lV兎@ c.:訌D$f質4%σc帝cGc池専"F.XE!T"[6m.鰔W霈6@w5J\ッ+WhpP!c9f#q(>> W猊эiPyGI`0oYiZU僉%凜枸g侭3_uk u0e c 迪Y_親i考Oqx7UZ.'Q *貝唳*Vk}wU{*fa4Otu Wnc刹 {1;\畝\u徃粂U ( kE1Lq綜37=ya05ｎmojGxY鎰2Y国∂渝籠洶F'c;C 穆)PDCd夐V霤f0G)憇廓╋Z&眉g36^`}/C^bhP鞏~箸n Zzte}h&qH狢EB3\腓95s!<0;偏%M]TQZ注爭5:m6-v@6烙@ W8pqPJ#削P剌" Yd=:抔qQ"V薺97hX6\j,:-U Z:os潮=D/玲 V堤kXtJKo&Myfl袰贇(p%)藤*萪 ^NVI*a *Ua5RN\0O fz?yN杭>ｈ9J{hH9棟'N_^]Gh%[鼾舅L序)[&HL-MF( g :_`-慷I荀デ`Sm X$l*l;vJ PHm 2"w faGjk4Q]澁#TW6@ 1炬K霞ポ_0}v9/Q}{?神薯~rFV|t 重lV弄Jいu,H撼#o@lo曖?R2_9趙5hZ┼W[zhPXIxQ(nm^ >G.T(寺/痲'q}~*tho($#EY #JxVi伯l/愛 >-f徠H8N2.描k,k逑t\pCm秉sA`p箜e殍Tl|袢ﾆ" 4V}駲wSM|}. vE68冩佃,p乖,b&5%")vnF稟酌證 ''&b  h婬\帑 \ By{Q#n]cO臨H"29:UN= ^d- 3bXt餤3VJN46O檎fnf=.徒LmG0載[G詞#0t:P2ﾈ+*tHH'Rt菅髯h遐b,jW6Q/f驢捺%E PS柞nh Qは ,妹NVy硅A喃d{{p耄譛}VvXxs'^_ ;-r4gM廉!}/9 dpz哂"Y(撒$62Qe5/|7膓G歇[睾彿\,5tZFEl箚詫妓BsMxw,清l?R'h`権 呆TR 鶩n吽KX; +燭CTr/k>f]eECB$J @q$`gxO?!csrq峰f}n'e dI6|柤AoO); 66弭w ?篏郭*慶H 智pP.Ehkg~v15ia 8A $Ct"BSp/治^8aMP) U\@HP33}1楹査晁9o/{{:wvo;vttn椦闃$dK\dnaPmI朶b Jh熾眷 倥*NU Dr纏Fvuc>zKLeiJ f6s浚e&MLUX4D蜾jf.o>{皰e{嬬管4墟埜等#6r8#鵡Hm坑奢@LPh区v P',f?\榻\鍠Mp3好~47;kTCデ+i ﾎU7_f&鮨n L!I"里t侯07eKFM XJ[ca(3{- ┷Xb.EHC窕U \4R A@L蛬6c陷0TG柚H" m佝'@3wιEui__JlYt簓Ha蛭Vxk;盒L'c^Qo晁LSi許xCt,黨L殤QL/&I] .h煎r/R|8"V5 MR\1XTm囁))C=^T"R溯>扈#%e黄XFRd *>d[ V.6s@T6(MOb k禁DN+解檀(Iju1蹉e:[t什pR琺乕慫) ZE3Hq$2叛N1XDQFR筬*'體(4bq~@潭WF,I9< 何/%G_c 桙xD T@Ov]saWC*E1N&0lS籃mLe幔0]z .鰛N aVSE\区vtqR1Nj*/vG1 iA稈F3x¢D<*gE#&QKE+@dp&9g;uH'E{}顱T$ュCHT靫(|7!c幵* [yofu"#Zk&]M呻▼H1R膸PD7K嘘C7=&yJ}^Y~ _37M}^U ｮ帰pNcL貍q/g喟``胖\tЙ41E｣$FLp;=I駲U?)W 8>EW\蜜XP^w到Fta+jV箇0$tX5矇Oj環n因D<I!s COn*;Aﾅ窩 yKLA7掩2;4y8'5fzluZ E画B 嬪ヮU` B{u upп#2&<R~進0yUO[亭 AY4 eST傴Wwσ\!IO?KK痛Dd/U0_I髀Yxei G()tbao;Tk.V1b樅鰓|c9^爍c#濡=. EGX=`D蝓% R!"B (Xiy永"啅I:3~8vр\O8价^c#~u~iEcokfQf4 *td4rweqgZ礫粒];f0鵬%#i%Ye社さWZ]BS_n]$(IjB”M2t &RH變HP5&p{扈+m`女s=IbＩGbR$:5徳釘C断霞Bl. 祁s[鬟EHx鷓P[D0cqX QsJ擢"Kぐ io:*%wl%cd(~TVY榮BYP({3`'降腹pW聚5顯$隍&比S剞xA}'ョ;$o軼gK(挺c`G)<ё20sJ .wF_演hqU鍬m#zU1k-YOSGn8湊qm? <{=A8/5=VH侘IpVzXj*蒙a%;]_gg9=7藩]2B Vnh6+?'|NZ  _-bPyra8V丕D潮川 qdK*吩v FM[9Gih^培A綾Ze+FΠHSJGS味蓆j峯[/鴦{Q=酵>磽fm扛%@?羯 cR^7ﾃ>~|9}xN挨T?d脇[:"VMhV,T攜iGG2:YOΠ&EqS/>引N\n漫7-t椌殯-KI嘔罟>3+3⊃:aw_JFeDvI権恵D3l褨o I篩猴7 c魏qV魘MM塵WU&" -M r"6D4訌?o俊:{eUs>IwQ1].6Qg#O豆A,鯖筋久h>'xn}O'G2~瓧z副4r岶=9詬食埋P刔畫捷@m]$ad7wL&^:陂%8n捍(51gNMC 嘸K"2韈gg鉦3g9湎:EoXaR,iQf;w24GS(i/I壬W52m汢fG部部FFo@+{厖EZtpЕ慵cO蕎V贖垠L8~W5(&+f僚 ( 瓠ww>?n聽A粢TLw(∋男gR 'Is=Aw瀘]捷臟Os'mAfB$6N&搦c}z鬱鎌MJ渇*AtdFrwQKG *理FMTfM5d6z#@E_E嬶!廬EB/;賦鬮@4&K J< j}j|# 4#}雪*-YE阪r"X瀘)lg嫣殪yﾄtG98SIy:G=$:]=!k#萍 O0"蕁”pr4q1.ﾋ$pI鞄}R ' ~{4T枇 OIG~0?&1TT6,鐫#慱^駢1Zhg粡俺wtI7(釋"虔L~i樫qp+朕B鶫V?c il満閧O z纎a新篁p!簍9V'?Gj =麩{U}o祝oc#+QS\紅恰_涕R5xA氛J$鏨5鑿6 /K8羨rD:g[-u<9瓷隋4+}]慾}V瓏mH^!O#|n剃 CW_$} <1ｕCU 'TT叭`0fA{o邱撞摧f{M7l1`齊RF惷k\猩齎>5t廃鋪;@礼弭桟窕Lp插v[３!満FxVRh[](jp<埜祐L曾0:@_鬪{;Avd准,jEtqpuFzWe4埴}6浄IyD'1 \|饅9O+X18l'g膏@jlBC飲廬HiX\甘o邃Xg~pd'f;w渠Wt舒代vP嘖|\ok?;6w&@X惧墨蛤勠鮎L&8qb溽台ttO.zw避c@!s;Vb"{n2c8 +u|jKl?p郡rn79Z4!峩fgorx8mo〆N柿( D-年U]<(]P欽W嚊~o~mB拆L瑜鞋xR"+1%]Mo4ｾ /j> 慫xA^ k閲O2>ZnW霸\偈QDGN*@-竍S('叱c*_#1友WvY蛍Q宀E?il 6;-frポ/.|R}H Cj魯繞 朱+恚-~qql≧藺r"lJ帝$ｦK叔Z孱w冓w然梅尖 oW^X級焼15' 渭qGu?:>失河/ 7MG#]%嶢eM穡W4:N=y;'(NIW^jX 墾Hx;{籌dFS YοH榊tO5}#5`/珠捲f還Qf9iE7^申cWg@v炒帳+B鰲J霾 C寳髯+x_QLq桑 鐙G融o,6RYsz9]耙}s柴La*Z7=齧M5彩yNYf(Mdh^"Oa};E怖0瓢/k*7;kk81 3(哈奨柴纏 Y< Xt=b$_ 葎RI豸Df2K蹤9~P訝3g愿|梦bv-5Hf<YzCQ誨4頗. 个r!NRtp駁<;雑讙f参U屍-3WH)lz弋)鱒sNpufsD掃t<鐺[74Jg:Bs,2'埠P鯡& s病\tztad巒｢r|~+?t1*娯1iLcd?F3^pP弓價Μ#Y+GHqn%6QQ/& wu  b+zLv多哲寃ItDVS E\(Kf/D燦Co7謁VsT?皷?Mom \lh.Kt[c攣j彝.G│→>@Qa =R#C 'd[i9@x`陞]ZWdWzcMSD{.隴B3G !_:歎4: -yWU 矯~i綽鷄c^TF#O,}F`ea&p)(m艶v角6(r扜V楠49鳫^矮^種媽~遣WM去S葱獎gtハVl~W8pD侠儖F1)~v儕j}3類?w>7謦7vf(I&43f|=)"%+S;^K%ｑa0 +&]6虧HS0\K芥Q]O廰B2 UU!M,xcxsr;^.+糟tp& a吏[A=3IhE虚:`C7^'g4;{[щGZ.psQ掴kC3埴>c爨傑R劍xI;S纔$}SC絮 =O "o 誇%n!1([_rZuK道 tJ[17v狃帥< -垪,LYＫW珞VD阪3稟}f824o恆b?F7j遇< .]&8NKs櫚6VZjI9Hoﾛ範Шg碪 弗HG懌)d{&伺JP3 Mvba <|+mg 袍Vマ}Ft: 黠a縟IQCO`n門}9(南諮s埴zl翦r^u,2:=E%se布5rN'M{Ez齎Fp/v詑{uK肺wb丶W ^(uTs T$桑4Gを 斑G( 's瑁svZO/.*鬥2%lR;<{V(僊hK嗾初金s蘯[wO紲[W悖XDq(*8Z9 .n;BGAb`9Y4辮O_\D$瘁|槽}炯WU@krf桷25粧攀困hN-zC鉗耡mb~泅讌6檢uR瑟;D!6W晒zΜ[!%時z UMtp\q:vXs祖 tkrsp9y,d鴈"_WtS(B_OdDイY字8捧l詢01x @ b$$[峽d% $謫dZ A9N!V構GR 7a2ovtlち$-44I @2uL 4!%″:i逶x?vo$際ww瀟瀁{:N[t棗>1鼈jk棆珞v乕u嬋N=kIp-6鈩ゑ氏$?r@v6X=}&)+懿JfXdt=]\rsIM%IzR讖2tﾇ4ma瘢>杳p単 鵐4kei;溯jK)  q{xD遽c鄙 %т ’DPkk弼1bFk獻T辞uzHz;aX9wgw樒mX{PyP+z =(笏`m}K0&P3.茄瞿Wcco諫竍e6 憖s宕BE从Ｄ'dx*?,T秘<6罟f配雜eivF1詢揩晟JF`GWzuX1k 4:l0!$b.e"d%B7澄I(-G?8S6T  J迭(O蠧!DB)*{Ut蘋A[%cc鮴i~9衵揉廁串N剩叟o:;y3<913V]<]m lyPr刔a"衂\縫$cX"F33>+艫Y/\収臙 sG]+Y鸞輯%&jnEr莇56崛釐)脇I+g仔*2$Qm%o U nEzx<]覇G裕:uN+瑜1 OJI吟S$8LaP|L98t278mh- WjjN 竈糯EaS趨[ 針W;'vd黜l+F$Z9恭委曜>B0%7p BIIM~iIdLl4箭18)#!+AqUPL腦><狎h登緩|曄pU旒xt|3<u3'0:y硫翅7ΜE'O11◆M7F]e∞~04~x m+q 饕JP ~"KI$M俄d9zH;C衍M* 簓Iz6~89QUZKk損<70z湍&o裸貫3胆&J=C jKa]#麦町辨9i脾&w+噐射Zyk~ZcW}`Uij搦Lk&2el'KNSs+\#)cn cF0knltp O#>/鼬媾%奠J脉U0壬.h.;@nF腹9=pIo`b痛鑚$)QW↓n|NKW8PhdRwcN nCI8}扈典?諧=∋o貭RJ4杵#!收+l`r .]]羲x:o}dx蠣閧aS),0 Je県鯉-uq@R.+ruu魯5焼ぇ驚%>倩k#qDLi玉EGWGN;L 'HQpoY荅k賦提p^h8uq_&l  TGF9+謇誓鴻М+9Bmq5挿,Gx93徐+0c辱惰f薨2Ap島(dbbAq T ("-LbyDH/G$zD[臀*実^w&?俥如S５$N錯+ETwD帑毀 +jaX-C#猛{D=B*pg$3q"{哮"^3?鼎Y1t_冤$ Iz.?-Vl) .j-0E豺+$rtO.~関:mB蔕K@'>-?WWB_]4Y`tP&h/!udq/PG醉X X]R{[le 瀛梗rz"o煎^u]附饐b/BI v3-}2Y閏aKfn 鞣7q %[>*8投 ]{?< lT-`K 箸鵠.IVﾃz$t刹53.nkt$P沚q萬,7Cc $蔓HC@S"iJ能@祟ba 8蟻凪s縮堯瞽U1P1R┯SA_X諸4f@蓴pqo?┗蘿`J1m7d`lSiHE]LD像q[夕g昔?葩榎Y[曩柚!綸癩 d蜈 7:31Nf#n267甑ie1|3j廏r|j*4\ELGs.]*ar澣` Wlb 生cG?FI82dn?fi拈;壞拮l"J'IWd/R#$麁3[)%HIT:@坂p哄qZ蜀B茫 D募 9X}`sb/泅7煩7_船瞿G玖zr$睨 Zq^<\驗?E-w溏o m|隅ｄD#笘m貅w 酬罍G`1{au武t相礑6g?1m0@4x NP湖6`島J柢h 關'哽俛 動 .|^7$8T+|nN! 冷[|{IJKン厖ir鞭UwI0Y1IplG)l=_!vG滷ZxK`（[]鉈[~q9bse ~ H§V1\寞\]I8AqH`b'DzVTε%Z津%妍潦鎚6]悼7b"0&H〒#~`依'}/sIP 爽8h F7飃 e9sc站CD%EMUBタVStrY&}9,汽良[旗k?@aG_Q _Uw C NPN1Кy厩b$p袖椛iD.F読Qa? 4+BF\D&[詫2a1|":9*kk!いDjQ@|}Rg毬Lw.vk:(g[R-哺/嫣i7酳v呷n追\椴-d捨g4Io]B=U⇒92譽,Y % lnK'2t90yYHU`≪Qq同61M028ziYx$i譴M',c,|w+SY9 Vc B4@zd7%Sy4此Zp|B]絛P`ヰ@2N@^Io]Z|s-i予|[r cs H`5exh+=?1G!H諱k)T Y>\柊隅惱K>@登Ko督&< N/e mQY2眦?KR┯ 4幃NBa拝+宣 5G"鈕z"lG7yJ蕪奎1査不L站T隍溢sNI*ib2監m Lt=NnJ zb[8%Y!.桜TNM罵={ 〓(vv2成g@K[V"U1Z sFQZ@ )擦)R}e詼9見荏t旙-9ぶ&]b\^腥gN&z!z 箱yZYS鉈=qG鈷3:z&沈,]A簀{c 諒/qbeJv希Q9h4[xG|;Kt尼x[@wDD_Yl8eXt-rPPko}b煦1 >Oot遮W腮芍gpC2b箘剿z儕edC 榜~ O\逧3 0c鱈 k 晢6>=L[D^濔兔G+島u癖!捕Z8{耀S8ow枴44mX4m(W7dMSsn!~HtxwPGp~枋pH@W:&?淪ym如=Tzbx~x闕b*eI`) _tBs公18o0J髟hGmlwU42k3#3GB +矗8) +A4`{遷8Z zS}c)氾湲KfiCV迭YO%}o'阿:d凄-u雙B─.\$& TT滾O oc%朞稔7R40糶 KukY搾OοypV.4+/]LR 'y;2畜]轆T 7,m夙(FIM<瘢藷~tP1fA~ 頻=6C1粡Hz 0搓dS"'<蚫)IP恟-煽c7xGyb&1I[T4sRД舮醸~-l(0a0}鎚$靨$-r.?VKN_ :~W1po>*Y*B蝗=,#磬V^;^7TI[D5.C+1Yp7釿T"3ずmsU_hpq_WhUw$Zn鰾oVsヨS狹2q@S.nL}U;0坊}Gaw0oN\@ 9o"t朞V`o#B究]#!pH1t跨3N庇V?zi>卷=vJ定k覧(`{&72,#~Qrk_7tKV'ke pEOGnfBlqo R&R 貨>x@F痔7+v轌Uv5mFtmGgu洋X稼5k参_瀏q7a tCШ*+~01 v>3p%LhQZHB:N~7]m2o3]0v'oJ'\5欝%?+餠y彑鵺#DEWP^蕩2Gw9pg慯dF]t,+l.gS徠,smL勇i温CP"7~t?DQe劒`^'0@詮tz i&gv4麾伜iQn/bL紂GC|Rイ暘w聡郵mZ軅0 丑詑LA &C, 7B雍@D6\.nmuX]vq0 ]qxuKl)雕"g"JR_ xU}jUw^Uov pk;pV/{IEUotl=>uZ罵嶄酎+鎬.oO^幢\雛u鵬|F. /W嵩下=A@*5uG?華蕷@ef$E亠I掫 戮7-+7qG)c-nqr'R窰{WIC[鳩0h2y_饅[mY3MUR$EUb8腹ck]S翩EG+o]F譽_dTnﾅ0^jBY FY[e6\1ゐ\jAea}N鶤指構j6S[9G#"罰/宥|v8>Aj8*|&P築`S驢k*A/_hi3<N脊H@AMcLcDt'e3纜Ir 薀i:Jp7L配$}戮W鮎?,\Mq-@(蘸:MZTj~LspO i婦C ~`臼pt&hl(~AT'而jW頼蠶/Cxt:6#'0 6#C`0~k[0腹*7SZ7豐*!u 7Klsx'" unnK忱&0G丐*薹N|笋4yx纜Ln憚+Vczr+^)#^\.xK助} 0x 0丸|HT;<ju鑄C勍!G]_kz^h?:lo┠Д t蚕~#+m署`q P,h5|Q8-!5+K?k)s w侮v抽 q#pa~z;O璞6^|-妣O煉Z ao境ECОbDk_yO|  1PTf 9N鰭,gy*O9^n'G<7 携&Xc7?'b%oh%&q *:&R%陜[鰺`aj?LYu%Ib{ud剳環9Add&'A<937窿!k4\(墟%雌攤\YF靆;7A<FFW<躋5S５t宝ByXpl乳","8r` OI.g,4@*g@(!-wP夕`b*0啻7h.7M_w懲oj闘1a{UV` %?2 1纎*n75B`倡l eq夊+>B柏Q8 vea慟, `y^怪A嬲L*W[W燠~,%TGh&%?)a$NxBD[ ELMl t`[mぽ:p_+u~MwG)c l)M 0!cP驫vL<惨PE%笳柘1%\C* $Adn2Y尅D4C)PrQ4h`A"G孑)q`$/-纜<jUZj 廴kZsUz'`XilD9x>?O^6I+魂m7 o4蔵'mt?9{#wREt%^褐 %F窿鶤?cg +r黶uYU<譱$峩 ^;#oA髱gQQ! :`T{m}wzW鴈JJ^!_\01KIa){6k撈g^ :.Q{7栗`p蜈*u4>奄{#q$av勹C0癩{竭i_!PCgUl^P&iLW S PN#&2ﾗ鑵H_蔵tEo'9sBNE!uEb饕D很C'&yC0pP尿p4;C4E%GG}饑VMhQ{R簔I(Rjb5l∧3;%k(`┨ 斛K0uPw)=TW/ct-#}u宸B]阜\iX +~k 爨ﾜ"3aO\{yqY &V?'rx>H/Z'冕bPu閻lwo!eg*3E Xy 歓Ug&:"!t8‘n:5V7(yb5R`歎K+ O"+q86張EAZ終A"hW櫨 yZd默yWhd$6/.デ"侑擣盍17tb.助迄o?hs BW ^浄訃<'dyi/浸ErQv896$ 躇 巨i"e G ~t|R擬I娚PQ:LVFzJ#箔;衆6^S&AyﾉL,+5!2;zwz鄭Q&%9蹶炯髻&鮓怯堡zB様先8|=d雑-娩DW-胥B1省売蝗(X^-玉P,鸚E闇R!YKT,/ B填]Q&)逵e~x)Ba恫,/E存喜d(錢=ks8abiVk嵩陂t| 5Z録+t#確HN5#+刔CBP@T S茣e悵瞎[谺SKDY(rl4*3閹 xTr32V~K迺A,訳E[sy51 [2|@覓zQ4KP]&色r;7wqS芍g[4I蝗IJ hp+Q/亘fH,Yr2_[G∩qVdGe, p8G` s[,%啼$@m01 rf42恨奈 aV|鰕2'':Fd@K/y 掴<4&[uicEYBo宦稍添y#~I(釁 恩^yh(.166%Gq3^)P e V<癆UR;Y$岑'N髦麥/6絽o _ΜC碓(禹?#;A=qjPYCnU癪y曁ms鑠9斎c駻W4*a6y1:hr暖my%簒Y_p週湲邑V|mfz}聶!屁jo0B鄙0漉JZSm云eRf[麥'9逶$Mo!VT6[a_Y.q胼2Bh(垤c盪歇sN讐 M>}.i駐Dc　hTG9}nF]5;-|皺乘z{繆{閥lK(84DJ#3h阪W沫鍋Z4-]i坑鏃|kdz{8塚嘩.DH頼\F~Z壗L~'幣BgM老j=;皴餒aLAJrU w潛p[AT]@[1}罐格 歛7Crw,."51HhD_T9TT+]--BfM$#FhSF,&;Q /_脩PX1^$-鰊羇jN+B_7/m=8p y)_L秒m呷| iJxB+黝&,I7Xf8;F[$o 6KIWT(gnY矮凄I-`XlBK'kXm8_6靼};弖cK6 6vOnVTxS->$E${I>S =租[鏡+>\L[ywM`' 47{!9`h.bvZr`u岡+[`潴Q_\R}_HG ΓS 荵7mz77F廓_tT~b6Na.#桔P/}n:伐腓y8<飽衂g(cR*L 脛:z三楔6C 栄P^VUxjRVKQN"80;q<魍q?XB（a黙.kz凵!%*wOISY祀:8? l)^M4tn8CドTu繩孚愆M攀Y)莓!1R HH "pXjF@HDehG oM{Gm5k.}`K2^$ %t`槊\S瀋寞4IXb0]0悌4KNLGH) o.zv辷7n蕩5G/}_'ycH P壷E# L峽%uF煬_i夫H  6a,j7j#cv隊`g;紕]Qv6G践険)#m,泛?M_Gc今誑{:@<5VS^,@z＠CRS.~聹B."K/e延>Z寡屐t堋}|0VV=IL領U0P|$q臥s+t=h\,Zi)癲邯;/ 42K糺% }醇AN54!!Se]!CMｬ孵.H劬jしQ'?:聘萌uzlZ?H恟y3=赦)[}q8n麥(岼jz;羶nlO[wD Pm党?!m烙Z51quI侶咋}胴@rS}浩穴jD1磨i事犖lk弃IW.m*,-e!+Z+亜 嶢♭J(PJkvwX$ 0<6IiI P:aFGp t`蓖u=]&<忌u旅{|随 |LGb(o庖脆H@逆鶺艶Ad8/Kn 逗}*咳;+x.W哢C4-D35Qg 6u0<_)X|鞋薛麭}U TH||'ZZzx">exR寓h6c#舎ch:c?T:p:G=/(A6AmiR宮な-:粮虫wB%'p轤Uz#$QtｐXLl &}繿|X 3K%n島巡vZ茲)6N趁緤t 1a4M 淵0乕[v赱Ro9YU)嫐<7嚼BLF"喀*Dbu ♂WQCKK%3j12x<;誚5(dq\VD 5wO&c '_&CUig|叶+7osM|pUv8p鈎哘,sc%Β*Ih_(紊k= 呱o8'zt縛 IWzk&4'鱧m%kTG^C*2yjlxuT1很# n>C峯熕POef軒T齔\%,I#Gw析goc\xt逵p勃jFH%VUb,-4S%wvbn.歔$'&[nx?<83~匸I #(?~I._e|英}>HBCr数涎惱iW ,?iN輙動悌詈襲畫)gp痼w Dm._愆 S5К揄肢3lV~斤遥導 }?h:モeiJg4釜+4v(導c1S'.,P7 弑|EhPk-燬`*'I>[旄f劇?i拯keEb竄姫D實]K州):WyIz$/}?B*|則+-遐,,殻2{zQxsV鍾GaooR8@~靤\眠艨愼 ]biiJ}2ﾕs顫3,ゾQQlG∴L綯T巵uJvB(:QOZ秤T|爰2?uuB<zu0X!rO)8 6-VJ :/nF 幇棟Rx=p=yE/h擺>粟""y5|蕉へ頼#,5vns_幾k`*9ov&EmrE8\S乞}墜J’U弊>l>g淮つ羲h"}rコ?Vm\]=8`晒体\U‖-5cL\"d/)|.](F决$.$+.k=酘c/c{ﾒ=X#K戦SHz休驀承パ淳xk潭p *2fGu?暹gYU2B2">3RfNS坊憇e;3: "k%FQ4P謄`PC)+POhs?w7壞AO# s*卒7K焉,(7l'狂仔h7+hUn(G'O^詒)-J$?dnUu>廡@蕎\.o床覧瀬妊}6X/^f)5y函q\泙id-|I怠2P注qgo4w*W絋hZ 伎N14Q喘sH7!+ sDTz3'tuVfQ巉-K荷｜v-鑢F鬆T.杞]榎&x紿ao,V檐4q預~SWzq\2鉢撻;PRx2|E n[銜畛")wRa\[oJ-羞mJ2o[鉄X.'n@ K,FZv[絨ZZH !'W2@u苳^k配hlQ蘊Y嬲窗'洌j衿_fDInI瓧IY;#BlK_m)dp黷†*[,':p」茴6nSi0P+=Lw=珞,W Ha8DiQT%U7z>r藍f,恫'M&NS325JP水-(橋L*Uf鋒頁嫖&QT颶> 5噫Z 聒畤*c% 3聴R}p痃S邪u,囗#U>vV+|FdE港b%;nm\V&i=zC!%O營%k2溯j1]#録8K亮ob|t>xrG kT.貿a姆 Mtv檢 I綱冕o!d?{0*1nC跚ぴC;u聯貮蹲-^|rァ u象1H拵gbs|W.rX匳J D伯L I,.T# `$越Y}/呆泙CaiXPEf畫 4yHT2reQpt9;#鞐>椡|苞*vcx(H*_`WDi濂3?窶夊▲YrMLH<3E#L$1+2"1 G 1UcE}2覚鍾酎q=\aqBRL^x5幃~NA軌' vl笶距d全幣諷Bl:*迂f~2丙=2q┝咒i導0Hv&札5）F| ]~-e1H渇R@嵶揩濃oPw,i[諤繧5v,Ru願榕r_qZL3#慢NHjU? 逅奴!LgqB<'- 發Cp--&頃矗K^妍y >zRa!}bx"i8側RM叡<敷 w G>蟆ga6塀促L4&|T ta -浄n姻Hd-a身O["ziX!%\d吼],>_8<凄| [c夙東茯>8款'57p1籾Ts嗚NS1告E>鸛[荵sU;'|鹽_S7+羅uqa餉YW,l彩SJg.LB 讎,s窿[Z!,xW匠r形俎%PEii[;lz數yQTSUC*]~扼p9仲l DW獺ffm娜?l(G{)<);AY蜈YE_*稚炮gK|躰箕fCBIV`誰L?敲T0隻戈!誤v1haTIV襃.T\xg}5Oa2旅`,Z(V<[=況S+rH%Lz6_Eu]8a貍&N-y]2%覇鴬xc"pa縦嘲箇 ^xpO8R'.DN/j5L%cmHtぜ} u8-$(~o杞S盪nsC+k坏is洒h_斤yBGZ~uxn[WH=IYfN縉槃⇔n(FSh宗| ﾝW磽[[痩e Y榎u3qoj癜)2>LWH`俥1髟尚q這pR瘁d&fw驟鑷b劵D藐蜀vx瑞w敝{V鐃増5１]HEZF?p'z#財げa鯆T5s罟GQ艮r疱呶2 I膃;2j迢礑?y醒zA假|`zBk狽F眼D T猴U8R}$NL03x"OFu90icXV%Vn{'B荷%ｧk<直Wp Ix駢{w繁mt&(-`JT=>)Hl乢;Xp,$!"l瀛P-b0MEюx竭ik6ik:榠gVJ饗ｦmV%Emq;:T6袵e/"r隱/KO5dS+s.K麋""闔A>"鐫$M_G+x]兆w[z鉈闔蛩zd?tB}霑<.8緕R\ぇpQFa 遭D塰w6.K[<誄UWy叡瘴<2%s溥BqYgRCZ\? 値\u珈]!_駮D,喰全SBa街&嶢歙甕|`4)錻H８?QVPH I4G袵 YFn}fo見Rx)(Ur)zFm=Ml`fR5勝夭i*1|j.)\&Ax嗽Q3XFq-] +|麟_6, $"Z]DK$4 褸#mx~猛Mn.|晄D= :{3 嘆G_P3>K疇*U}(譲+K**＊up[櫓SrCaw2&3 (そN揃'王.CO.朸;z鵬tE+lh[悟Z瀋輌b獻鵝*usdjka乍yx畭!=?簡J*+MOtn(e"EVVJｕ f\X~8=B録o\s液GFf+y}/訟_pu5`瀬[$sB ♀zZ)F8RS7鵡0[- 'kOb-V`NQs1Xm`c/tb惱<|>偸朧‰#fU7 B織)9q1LSJvs k@哢kB)[醉-CD\,袷sEN瑚橖n+|o臭橈"索aHщ捏<捏}v5`^cTm zPn採`QR$紮& S~u2 K,沖90桁愽[懈>蹲 "1j=盧昃aNI T9QFVL財:zZzc%*填)zv'興;F?疂+^I~'~Ugs禍Yバ?蒡x@bCLB＝v@8bd]ｴ* /3L擧 W`JS/{&R恙墺!cc纉O委, /|UM(K?BEn,揮c#)fP\=f+o$C%*釟/唳,胛P具n>aZ<繼xK V-j隆b2w燼A QpwSp籀-yｅ[XY.?-aSq陝' pUp（?燬jdy0Nmg秦7N\!k^踊+}j&}{U[D(I4qey2R> EBK!rszka1d[$Db/x0/a RN-H@ [ }.3)D.U_?g-JYQ;^# 淨: $N2鑁Z捧26{M;麋'耡g8`駲 秬8道AZCaYsv0臑:;娘6(N;4曇3療eS%>]~懲 q箒%@/D$zW \1^tmOaH2P枳 %Ww埔2T%;o狹tN9D]邑J_$5-^rei貝y#g&U\9髞89\  ^窰-f咏糊]{>Y]Dw-4k bRN劾-lOjTW?EД <5=С%NcsT5vaGhDx激v0am[}U恐b0~5+}",昌,m疏NXX71T q}C願]I瑰@gPr`汁$9,<DcSQ4AzxN7 メKx{刔HqW^By|tMf補f <霜V!戸;]SM^0Y yIBbtD)DyAZH+n2何'YQE.]wa5 nl唳8n_?P烽,zvMH@Zaa叛觧grBwh峩3A^?V-*&b;V5羆刹e,鎴:$Y愽uW僧{WS夂am= E榔L5呰G鋭j[-}K溷準r}jh(聊es__42D(AUVK~7 FA{}倅R&M=7>pY%UO[蛔xZ>臂）"埆 ｛dVF}fZpR騾4 }>$c9H]\/G虔} )j61^ve禄<]y+遺漉jdKxYJPT禅kyYH!F1I裁:0膚ZsxT?%*砒x顱y碌LJv局e齢0gAI胛 O=O]5=q照`x}6'kS{Tnq+jE桍惱vO囑L毳灸m.除4ヅ癇d8|A"7H$碵9V善&`dT9νy&骰纈ydSfバi Z"@駈iU3g.軋eoせM ? @旅T Gt!.7-c褐釀d3Ju Z\N*m[`g毆__R衂!xV m1!p19k!gA ![錯zVS0t>芙C)vSM絞BXCfd- X飯 hK)A'XJOGdTmdu冽墸v%l袋ﾞ粁Σ膠T?振ｗZ9登/A巴 2F@mR嘱z專Z暇vY蟠 rZu3m2gZ#uk}蓙=0'怒JCi;)n ?>k\_k癇保u晟OV黶\NBdi畋NX-*z(>}o%x`$掵巡@\z>uHU^a虫場jql┫w G@&κ9:*Q<^W葢?%Eymb-b轄EDK'm諍eq$A|j c~>脳4I9G)f'+ke UtGL qPl,c 兎Zl7@dXFw頭f]]-}w+6$hjc\俗;~] Ｋ4m]A[3|硼\裲旅#g6!GkgGG芳l\Fl:CU}朏O_}/bdNGs~e蕪4#朞y檳 W`{IiNMxAG=?s\咐@,.g陳y倒n IZ\#D0ъ|8h柏uK^稀`pY3s呟-@ :B hV9 添}IH■拠鰡亢詠a逖eq*g.[)岫rZ絲j5迴:e3W>sBkL#;18o克P wSNI鮴･NHe4DDBV膈@*c7嫡Eo@y]B桔漬$後lr3]PX];d吶)鬢@U患Xp-azE*年MN3_')U^U^;R=,y[1Mb"IY(>e逆VyXl~vDJhBo4Z{O+堽f dfUZ0W髟囃 8LpJZア$XsP寡D.T q)犢 J0蹊N上 嘔Z 顰#TL@+{闥)/澳@0Gs(:[w年 ; d-∞ 麥qZIg惠烋&DぁN*k=}R末呀AJ}jねenY lq4,5.dH傘@-P撻g痣^,.X23J030fザ盂覲1;袿~"~~ zt]z,QRX>?尿[7 +bm:xn架軋DY#鎰敬XP4.xehZWvR;O|Z y鰆6媒.[ 滌 I W;;>-IV!dG}cVRE癬I0Z龜YC{(ya&6a#PnY,齲z驛3k,JI/后>=BDZT樹jm2y;EBS":oh@`{,屍^f k&xk堤E0, w6N(Cb.3Ka畉K+邀g駰wgs9憤B|^*/XQJ85-7mb7tB鶹 EB-6,^冦IvU.nwd奧Iy.蒭!O柝訪">-_p;h*rQK喀*責m*骸lGUPJG%]^B66r;38'!bﾎ* ,'DZm騙k'sy泪~g緻*Ik:秦xlp`執)>蔵lM|)dC循ﾂ謠SゾWu估F鵲C* /z]_S|沸SqIik 孜{P鯲>~s貳馬>00:XHv頷N8I=lYYZ*xVdD黹'2M榊#髻HrFf 5pU#￣"O朏桀N`$KSn嚶RPisLG.0k\$#Q慨aomCc<.9Q}=peae,f萎 oSM,c 1> qi(y ,;):Lv]|o煙云傘}~:y丿ZX DeyH蕚C枦h寛ΒP^xh烽苫1kr%;b^QNЕd)5Oj|D攝c^U9葬80 ^f肴nhYyvVｨI' .y捷V}やY5J0辯R.N9~& [+C混hyD貔G3/.股t2O;[T1T趁~ kgaJ</jnm}\6w儂tS瞭E-l%=/mhT座m4 Q%;O+o4} ce)淨8慴XZ醗G24n雀e近9l+6哢]%C5?|b驃在μ0xhDqX ||D14島&\+myR[?"Z) 戍>d辮 mrml6[赱q".JJ%\竇W罨}挂%h?麈*菻BO校犖.&OBx 末jwvZ媛Y!+輻蝣歃翻]貌&2iCl/攅X啗$ ヾ4iB 隆i嘯c L[,dLIR艝{銕蠢L]RIq^;燎w~熄5欠xaMPSU{BS:複ｹusW損5=D>蕋4E膰R睨>{O遲°{;R 'L^宵Q%j!iVN桾B傅/56顱U_V&m&$.g |`そ;慫實胤jT$e@(逖m_MP}NTI7i]其 F涜%蒭}Sw)C !<-M%夾<%z故y,┥阡F* "槹R.o琵@ YLI蔬E%廬lD?}U_縄筬S譜UドnI〆uXnz`,>爬#0%堵]8N|w]UYw+pw商.|L 即i gYhL |,V\l wE{3Ynx= a0~TN )r1{誕a4t橸oT$g1$S},2K\AQΠF旆PJt驕 披/ood晦N(\0統gL&_齦E呆7D?縁盒#B諒Aﾑ-盈葎8$d^Xo/qky/2,tn額xks- \, JF香J)C1.\5f^pA筵lvj5默,b*3xCF'q治2嶢MY露coMS柑c3腰;Z>閧t謁 > 互mTw肴=稱O糂 &x,aQ筑&pv8檪G 男$0I;]\淑psO嬲X~"H ニD鰉Os}c徼 ?`Cme止蹉2q.My- ?:bnQ迂:)!$ 恕'x|粽即G羂IJ戀p蝨x<]5)C}1敗`K+苜驢駁qBpb&{R彁 \浩珠Y|楔~滏4AV/♀94eB 槊K~2Q/5h=sFNr8^2MJu%)/7APy/aqCBo]) y_4GL%!輪｝}-[22FZl ж _D/{=G.ovWh$z^eBa L族A{&hkA1ADO励Glfrp;3(;/]{ Eyb|捧mpり o滴/H緘UhjおG忿謦述[締起Q_Z]}bk遥遲*}-~懍q矯ZG~?[*VyX全7~V|[t靺R{纓> V猖|=9AFlt)`o坎S〒K!o6rix簿wV(ipO3葺+I.0oELt擶ha粃禀 N#迩徑c&踐`_^'F=G迸#!刳a:Oo剥#XZ.k黽@,隙z剔%祠p君危hlUaO俎2z/ `H1:綯.I1is@ 3)v.囓¶e#身&6H*'&S礎}tt.hez笂I%O BvNT屬oxe2hrgcb'],'jdx ガ2U:9%S軼$meОa=)cuKt馼 GxK 梹f>O14&T)揚9[vt疣娵[~'3f樊<磁,v~I:n[mN@q侠d矩^DF G9C &,qW#毟 違F涌Kp=;V驂mZM4boWi柾愁SjUW寿`f讒僊蓉c|#8幟梍嶝g/安,0H Dk滂<\#-\eV,/UI鯀}c狠}悁vVO0][`擠npUw7KM,gZ擠k\剔ﾋv繻5_s'K>:G美Lt^_>y;再\NG攪fY7YJbU科rG/Wn/RO-δPXTA柄桓A^"拮"蔬RG\(M.状re^5鯉5\椅烏椽>/2Rx@zK? '簣苒pK OIH8eN:!4Лb嵋*3 c薩t%g%e5z-AG<U鰕<3J籤dYX Kp<kk+C術咢z 2m&vKUU罕2 jｅ蜉Т.f1@樶{MJ箔t{C & DPs曟f&G)MM?歴wV&"OW.tg _靺12袍殤迅E9t}=0}1v1%l\g胄y苜6喟KkY9隘/VoH男*燦;$uEZs遏 ' 乏)9OQ睨z飩J6K<g陽鑒-Jr$ 磽)6Sx%/TD]帙F麩||wg$BHL羝{f宝m>帑鎌sx?L翕7+5~憐磧{ .5抬<*+ъ> 5彭橿a[ g2}鎌 {C[J3膕Y霹% 兢k;g彷lE9滞nVHj吐54C3v嚀n`%憾慍M[S4$H 8FDPCF6籤 133-0b$莪抜JaMK#(w.4g0#RAnh褫轤麁vz雕hwn宣Dh|み$wy]8?.'r[7~e4房qal.$fU~ 3UR{M錣80,yr習陦x9J&C 9yBA┷heul8/$#BKh$囂nA苹+d5C/I t;5\:?mKW淅t*N!Jj挺功U粃JDv<(u^VrF3咄f▲棺Y?,,莉FG( !墅*5b&'G毒&w_斃KoL(Ln珈b)訟xdB )^Wb犖攣u〇Xy:$筆Н彈颶yU鞆h匣肋U:'矮SHpa …陜J;l CN ..債ZH@d?+驅 襪爼朷>原UD ^LG涵 ?:=[Nf尸凪Z贔W|&g/(岡ii` V_@'{!0QVn瞶u】P掾潺u雛:-?|卿;&^# t":仝ンN~X}iLﾇ"uk}Bo[臉*g悛*]p廱To蘂o渫gfK5=U,I佼 Y)Kｄぷ2H\坦RJI 吠BdVヘcu奚T%r箒g1l 肇┴8VPtysRAc&F堵w:+縵d鷆>K邊誑 'c胡1'!oWk溘A犇6EB@YM"TwH{W"4CZsP罷hm0 ZZq鐘Y}ig` 飢6ma囀;t=ULuMZRdTHZK}斂9'$Pdm 態 1D被_=崛p鮑戮qH鬼[$N甸,bdQ8m b 0\sC"8Q j┐騷73-kk<z&^2$A屡褶寂?73FャF{)GW砧"09 ldP@:codc帋07澱程 *W鯊 IAKfa$p^rO楷0^9p犀雁北}&|+OTzC俘cfSwvjOV};dR桧^ 'f9輅<鰐 9+\F)6+/3#ュp(q:ZY卻澂 纔忈岾9k!JEmCaI!C1X餔=2=`6!Lю袋3 c) 岩}-糂綟1#Ki``9bg|L2>kHPyYsIaP_,B=ｅ |')BforW-c喋zO?沺;k#F-:r h 詛NWJri[8"*,1,9 M9ZZS4 <聳L)o i=9z2rOJ ,Tl-}n%TOJ*O]0b%!<=P z莇yN!lW嘈<鑿wgRB[)>之{;G蜴湎雌閂ゅ|艫鉚8Ij前0,RuTED6献IFJUZ)QEH|種爺pl烋亮闢>睡鹽i私&駻弯zljJ[檐甄狐l鐇 C#w'M?"(Jo *A3':鴨gHYe~釼^U絎egWA~63+(0tTs :ω ﾙ袤fizvN=_Cyl庇3ZヂQUvf,肯 ( P匚 о崔醋M[-澳s邦er r徭L[ x碑k#{ 斥}戮*28予._6ぉWYV\>G他怫到廂^L?B明.Ung!,J1k堀Nw("U刊aH滌0[Ry(\XXp[| ),lv頤P粳6_Kzv霙A~|且F口 N~,9MO羚aRY琲箇*RtN*n0ビ50黄k1POi(-v$L\'J6濫eH(((朞,鞦.z)Y#q/C_66K 齎m3轢A&li { 3?wf> "bR||B F0麒&+!X`LW 馮hi~芳甍隋vａ吹儕哲 sv聽o笙戟Gjh +Gr' k駄鴎W5r ib3~Qoめb5]Rk\m]9瓦ゞ^溷5b 至qCHLsp\珀3brP1Z奬%2$Q#e6 濬'0璋Vv Q 9Eif{OKLH!Vlw}c瘉4 s怩*uEg岾MLD ]I%;Zi_京`婆MGxg莎院 #Jv;曾tf}p闊,3I/k i釟mPZ't(pM扱螳8軈LR課懇聹5淘nIc|C{\zk饗糸m/# 攵邀@Mj wl彡槻坐~9-mn>^] EO5 滾O@柎榻-4HH>M勠V韶5u#?gw蟷bX7cX l$[ "(?W`!c席r潁M靂x;7;#BTyI !dR1h3^y蔓4td_lsXBzKo%SFl?８8泓xyO >澡}6ｦYWYp窘梟%t{@q(@ 者6Tvt4ID,;kV d (Aq%*"Y-晁兎n~.qT2Э*G~JcUk zM芬.辷i覗 n H7*~ADf失s`〓UFob曦|3W=`#g>= 柩!L?=I;SS!-jそqY]Mt/_Q坐wf淀IR~:3{sk闌WkV文I足 w9W濶攸jW`x#$鮟k]pJg~枳Ooa哽YCoPK02X曚GwP+Yu武\違2jЧ1,$$/駄 麼D#7 J崛2v)A 侃W7%JfMN漓0Wn~Xz7Q栂r修#nG&GIWRNΗB雄fe?FAlt149@&zM|%丿l_5eB4濆I矼xd3d戳 %2 撲械UFB)xTv=迢咼68014P g R哢泊7F1 R秬,Z4$蜩c黷6wo+xt: ,:/eo^)投莇b" χMpSRo+k[m#[:|x(xT^dVu "9x鮑&pe\h4kM3(\ny 恭e^x=紘{&o#-"vO*$BM囹d賞眥)Z*qd夫G7OLGNG y普Dd籟m萢4謔fw<A`927]m0@5銖i鄙芒_)Y5F>zf% ,M$題MQo.cW>Ob巧 *足Y5\6斧%^負WF瀧o?grxa}GF今7嬋2文/ ~-驥葭&,*:鞄NL=3饅'D]MMMf-7愎I冨-kZ/qNe\ Yzb+^狡='.饒tMx矮_飼杜<饑LFB [鴕jごO8XYrH]P,VΦ^",ぎIvx緒續Pwd9'- 柱ｎpY痍 xTq@w=o*MYM珞=7.g r(聲DAV蕣貪^宥 玖yn4EF9K蚫3+鋺跋 "rB0k鐺m~q"貽rI^_V拜ZD:PjeiLX}旦]s d/JxRefg 2We｝G9-伝(YA 伉Pgb黯UR[9 =% agLuR7 ]1~"]c p椌炳CM}/$醢w>H! 顱{祀:洪(,#Hx7;鬆 廨艤#v]\手汢%dN舵Hp>＠釋厨淬痼/S BBS$BBVQEVPp)V玉uvo]F-b料轆/#"`,NS無沒*cUDN0ixn xl破vf-V'苻4_$iK*[ gﾅ~寵'詔)1MBN-[l/nZ].樋0z.I礑%霽獎煽".flM\RFdc@d鏤駘X|l峰{:5o>^Vl{f(ot.毋≪hX:7#O,x+[ b糢b0 a鴿牒:z噬SbRg悩瘢g/n昭KjUkzaG塘櫂80叫;I"l隕@&W 專+:}8y訛@zS,F9Q'C.v;|舶k5l造J,艶>轉滲f]N<#uk)3.j尤VWa%s鎔`x4龕4haTK0](9| H,>55E=.[k1fTつ束-爛N1p!效}UL握EZEY  <,z>g晟DJJap丼@4凶g綻qM踈x>ZRAL[TGEnZmZfZ襌;IH裾VZU^B2_,槃7ha/n%焔R"y_`@fuΜK)n^l$x絏}/\ %揉?AQD)X帋林H瀚U) 5t<:$BUWEaZkh1沿例{x譌d,CEXN0?}A36FZ効3S;x?&;]" f礁|*堺&G,ZT\&蓆 5zXyWo+Z)tDJ'&sA鴬4[y5x?ET+岶~_6sX"~m&"k酸|gYщz^LLGkk{ w|S蝌H"9 yR@&腑聟 aOx,F93DYOViNK/+MMN関B@陷Qt兄I/)4YォL_8灼"4梶'^鵐dIZ`苟cG\c*|7n釘撰N \NqO$}IJn}K!hE:A>fTO]u5sY8{D#P唖US0 ME+(a賑[b9UM戟&UF;;閥#Q*Unp襴l,#''l*A`P:Y志I覓讙V HZ@"奴c{vW#婚ww>?鴎藪.uuU3"搓 潮dEq@ "8 B 6199VUw廳w昆鐔u鏐}3縁g/\{7@4I~聹x5)*4L y5lv4 ≒{-黠c,桃_?Z^%3dﾚ!躰+h2|_~毬cZH磯簷G4>+x5?O8菲X1麥1'#_ISJ~鍚\1@ 'TB|$)?4!*/+ド＿幅iaz8憶|w+辿FM=Y <~(Gd%8F/}ctKN熾-霤?v^p=#IC|l KZV bTF簒`wh什臼z期K9""'$T]陌? 等3彰儀6u}赴uoqJ(11'^pC/O> 借V\r8+х%{x 6pz攸m笨 氛c採FU寡l姚wn^+iL$P2:>}槭9ZizD|g/o3b3_wX饗ﾁkq9He濂:2q畚枢C8,!G覃式仞+Ofd:44R-鳴粛CuA'卑a雑jr箚-nE逋柏赱j萪bt[EiH磋=葺Lr 6c1[)O 卿' dg|S丕J夭q鬮G 詒}4ZF<@<_O2V, $Q~|K堙}EZｾvB関IYue培\3owL>?M7rhd52bA:6im24YlAI e佯 ^妊0JbV-n&YR 填j筮6#WPDJE*称Mt(lq>89t*竰締N)4[_NX_z%噺g麻4'O}Y*;-x(A) gZ九jEzqIUv}Ejjiu変9G[XH_ΝHz<咤O} BF珸lp ",FbPQP+>)+I8/w e羽|V5tCZ殯"駐5mKDu絋Y位柆+O6ji0y}@t%zjJb|Rcph>LxU8WLo(f,WcBl2W?a6IXEQ驚&u=N^ yr検Dk} 5粨Fek*[huZY/.&%ZNW_D+萩+ 丕繝({~ Eb$遭F7_瞶9fpSJV 萌`.容~Po汚.o垈?o,n\FtqL飮鑢奬{[_H戮_G%;p3Θ□8CNX@F鑞PKK2慧二q馳<Vw舍&yl拏RyU q~rKc嚆aUﾑ6mヵ-研 ZimH}pi鉦 拏A統叡 RC }Fic 室!r1W8F #殀Vぶ &¬1D緒Ov\hx(IK瘻 .L8B1彦DOcx+'_4P3@B\q<6ha:営ZZ1-+KBc爍kN緘>;@z| 羔/X:;p釟&”ZeC#=auFjJ}!]Xp7sMQen晩蛸MI1`|RD" 冫([ " ; oSJDzrt4Hqw/褦 Mc^Lm 0X/X崩4掵o5T 5z<昂7Jr\衲八$E&梯&` IA^N.**/8>sY|X%IiA>畧剩L$'20k誣ｫ[廓[腑%w3.翠Uk6L*s進EqZ佃s＾$ET;[7-筴=ギnr6IkR]bf齢#`2枌 *,策`p@聾鮫~ NlV 2\ QH RYテ4隔zqK9#膳fzg私XJ萼Lz{QO|-';n頓依.Zh14 i6ya.轤塩駮X*-3R=tk oΒ9$>ZX_}M]焙I 掫^OG+煢ZT蕋ﾜD"Lw'%\A))MOfＷBx酲1 俥醒8qe:嬪周k鼈:b) dBJ; bDoljx螻鷕妛E鋲iオ*I$r 坊zak]燼nAGZ'["d備鷦ak/ﾇィnL_枹7Xv娵<I制按=s(_雑Rh%u8:~ E&i瀕I`ぃkE\ @%'┣P?c諦7)SH7 ∧3轄57c淨k|C震d時羅JD[憂3 nHp027sx鮟,EeD*:S`'/6g8nv F>w-43#e腰疉wMW> 7oOI逮メ?稀\5栽8p><6を睛WGI^?[Ghr~.fh忠=b咒釼遇tO~b _%<@愬ID *4主4PDOls 拐"ur9X莵劭/9v夘\ttfx=羽'}r3s*1uES珪璽_%G〒珪)Bk B.>(6惹殤|qk/v悼+_飫F:駘 O鞜RtD~@KRy*f褝aWImHBniMIN$]$褓"n & +昼籍^q宥&hQ悲靦噐M >３Ie(C*:J"蛯R,L4 l述s_;O随w.I\c&WS_nK,BUXd"6pAy $6b' {赱梼N薮oR蛉3i#n  E爲q' 秦!&=wf"_t儖s,犧レu胛Rqv$+ZE盆HTH=La~^4 DV H 嘴OF5靆+zM蟲旁MyZRx詛ruμEW:^g腱Qh藥IGcjV Hk7aN=\(Zn3uF&tL;獻閘奎w[%&@限T7$ yNJ(槐R^]g礪t,ﾓ 駝co4(&~_$0A魍J 3j曾診`=W# 擦8O髻Ka\籬= QM[R fIwm'9朏1$t8況VQ〈賓rAQg SvtLwqFIKA;K\?!A( hozDN償粲H"-NV5 尖EVA!jZ#r;gnR[渕NW1HZ Xq莊]Zn)4R},@*.@縻;N GRxr0HF>5vr緒Cdq8{!f_m#翻Fw1{!JI/蘋&bdtm漑PIrU\ -Gb賦慶T 4Afc衵uD`秦`禅!cQ]蟶gP2ju HF)MR5D仮狸H:Z12D%h行b77陪2救kJH k!ZNlYΦzf)m弑vx遯季>yε孛dkeRO?~op dE安驂MNi 刀O杖Jq E)oi;rs3.g丸,|R 騷b{n,9ミ$笠噤奎洫lTgL)末孫sRsNZvc9(TiI)d6O#P第蒐VE&tCga犇蓚孳. b嚠 3})潯8%l`~;屐x鸞g張窃螟j{U咤 dst2W泣Y]jSj獏激lF<<l)塊疝ttix煬w順7O)LK<麁?i奴q"Mj}3S~Fq懲V;q娑8X凸 zd劣4) x4!ehXix覧xxjanz\O2iq香]_]w祟}p?~榴 沽(bbQ卿磊fj!$ 莖U(*AlVT\eez78丞冓U頷l9evSZ永<槹RIQ;e┥Q:k2IV [蟾顎2Z 3m葢7bhk[7J帷`@Ｓ2CP&億ld %;H'Bq＼Y听gmik嘉>三ltQKOWI2mE奄^zH乾@ViG幢 v*gi&"B$Kh!YIv6&W[)}8泄鯀裘w`gU*叙'YO狂d?^.窯V! 4*cd!÷c址xG&盻wf"(sp砧B 練"~y@Y.糒a'zp\m#j#0[唏!置9eoO院4>F呵K/KKd)|燹RS\ :i;鏥KWK:aL0讓TX^1f0kg"&\_2yδ-鮨/力ZfNzyp望uj 0c5xs檜遡挑qTH流x聡bbXN_崋odZ"(`~ez3yvITh什b.68ＩrZ syc))楊%蕀$=儿K|~ 磑6Vn{_珠：@\u網oJ"息'/q1#BjmdZQ}kfスXV抉{c%滸HqZG6Y醉 b:可Zd爾号I78'iＤIBGMo倶nV-弗dpZ攅 S1亠F王.E?R0JkDc,佛TW>h,hbP7\wW拊\JO:CGQ%PK搗|f>g､w% 'l]@66c~墺壟fCMVdi1!耐^9<#Q敕qk5 菷s<"鹵a7af帽T?密LcT?_痴gg披噺U&QK果倚p>皈 iu{B綸石惇% B梔:[客v~ 鏑ぅ ぁ~^rHs>魍鮑-x29Rg6S8$\K租RE"^縫A漂釈$+<|葛)uu狃迂f∪'ke@憑N2=d~僮 るr,勣8匳XS9=$T^采aR8綿>%東3 \Ze@*L6wkIl=4]f]TU9>t*u惓@ lBnﾋwQ:彩>Ｍu`sT欸s趁74o)IFudPR縲i辿5j:ZlYZH-bo&_) i+.ihcp;c'5Q然>e/f 1%#U'`%N\]微Th`C?縄i.Gso替7X酘擾NK()殤1} 8bKc瀏R3i]YRy┛DCk翳L6$脆SeUX"沐xf.5CFrc2_F'.oV} t*)AD( 棊P2V$^宕. Xp2b8}Wb%- viq(tvStV8eRV$/v4|XLkUwkA&,^wY闔~KDL-dPWzz{]C$$@爺2qu~*_Q樟PRkYX囹-A躯"7耿儘4I(&pO 3侃)聆}罪y珸u;~+轉n4x-?F;7~^}48=CQ:WysvuXF)n,)籔 G$遑Pml瞻]tg[C?X歩長*z紬 o舉 afU7I5Z嫩 c&I干abIFcK*擦\nn7茱z淑=1d毋\ -ぞFJXZ'a9鴬室r弯o0急X]予窈C(J+拠cXK4DdN_謌2壽"W捌η2j~$!螳_痃殲&5> _ゐ+? b.g4)>UK鮑+$髯L~&ARfP\`U  4JRv歡~:{9 ojOQ伶$A"DI,j!}j葫+yhvZuъ堂YD防sv>恚數XTk5暸8s#?4t,Dm免汾搬冀3Ichz.轄VUv7^~Tt*wc 8陣 滑kq3 w6(m竰's$Iz朞jOu"` Z溺傚%bEりz!m2%xZHj>][ (l兮7錘H]=,zwAgK\塀`u耘#. Jh]w,)s*M*r9Uf:m8oAsj3改%G  ;" K*5TWE-Z3AI~畴i正.Q,s=Y\.cUr(q96ド冰nSM:ν杪C,z#-LaWdyCbZ荏恕%ZMs|s禾%U紛x韈!父A,I4X\)Te|#d欽P遅fQ放^鴕趙Dv"芙9.#a?鴪塹8SE戒禊5緬$邸6tS黝$1┠iN身t紫附〆b-VhёeUヂ*歯 `r7$0w苗4aKv橄瓏_|.T譲OSB;遮h*)+ 4挨 oK弼ym籣 0]迎:]L沃ads!J_-儂B_"taU"d咒寺7;7GsYPY褫^)枴Q暝}OL,6JE5C [21H{I2椪#GF:_n!施麹'}pn裾'CrHA>}I実/度:y寄S?\$巽b頡irQ亶i癪$h>壤x>}U4,bak23鍛茹>讙嬶]D?蘿O瓦G%.,} {w8@ik恙sEG!qU*`vb.A\凖瀟 cxE|n"!Hw祚^沾kp肘嚀ΣePH}鐃a}裃[ )%] I俐}U2!}燎貨縉>s瀲H拭fhU,F0[}u鋏e屬(,m|Ｌp;α 孩}'齠蝎N貍Cf汁hI/ Tl"X*[uzHp腦z1vz悉圭w~十廢努{1^hl{e~錫寓/慌I%蛬櫺=ye\&虍$zN#LE 椥:N島.y関M淅橄脂yyLPo |z{=柵麩郛蚫困: k]E;9f}}裂@(ﾑOGViOq壌{W;6x匡女4ﾑSCc|z=t?h鏐笨$-43z q8a鰮J羮CXiHyN(y 橲RPQ) usQ*?LqO 崇iLB1F"R諳朮扉o]!(H;X&|北Y)g黥"|紡Xu獵K2鮃Ex,Qb=H"9 LS\PR3{C州t %膚Y<_[MW`~l swD \qqw\[$b4rh8ゾ>b zBhЧX霾HM,84:W飩3*\Q白蔵`貫 w (癨`p寥:l 緜一!}[H/h殤ZQr弟_#踝+wq菰${.2萼佰麩 厚G bF拔 83 ﾜT,LG裄;−AW!幺4g銭^Z#=3英網1果Xn$:,+O|9坑&n\ _-=4>}^.*-%:W?1捏8\!Dl4碇宗癌@ ,i~ _H閹386<< 零MVf;kEUv\n0 濬h霸'ZyM= n&k*sl0-i篦NwN 2pSj1N絛セ學`;~(s聿 :2=儿軫J88匚捧Ub+`剞.７ｳ-s4.っ"迯wh=80?km{r6G|Z!DgAHt B≒oSpQ,滔疑0|Vu]148uDu/V;仰@gI-jm,ﾎ瓏G滴べ/'SH`疚六'2|遒lffB^J4wkNt}1]3'N5Kb>}HP曄&<凝W&FP)GM}劾5<-.{gGrG3o腴c_M4;諍pRxh鰒1N~7hBu[Un'kR\2=x莓殺Yo63w豊p4dQ v叱KKbx底RE"|嵶tP6S1 (ppqG穉z碵%Y鯣 /^9R效^桓RZxzl{E盖ez 幎!JArK9mAs育NM鐺>[xwF[扞Pgt彁KJ皙9c癇!05 on.簍4鉚NbTk2狠A鐘c鸚佰B]jK:`(Jv.!＊csfH裔m霙hsV.S姜w$BMGx鯵K}Xp=ytN-彖地暉:o恥w^bq+@咒`H.}e~gv膽'腓纛Z8N地 xg<%Sgd\@Fu釼}N2´C*樮咄ZYxl R豪7  踰忙}}覗>ニH$^徼),粉R>默a@Tz捌黜\_c}E慄XzΨ爾x]?EP4 # P峻78[ +/-F椡T6軛qr簀ijfgF政Rd-m5F曰胝9倖箝K7TQ7qtL6dmc彝ゞ@a MC校s寢\麒7Y斌7き#GET膓1ys鏨L &慣(5G)z7eWreΣM/*髭'NDど磅?Q='c'EQb栩2膣DP1Dchr卦g^"代粧ぃ'励Ss M;FckcQA`儒v畊香tMogq鱈眹oE蘰g^垠A\Fw猷 *m](d*菖8 I2HYStE瓊○G鋸DTC

      5 MySQL Optimisation

      Optimization is a complicated task because it ultimately requires understanding of the whole system. While it may be possible to do some local optimizations with small knowledge of your system or application, the more optimal you want your system to become the more you will have to know about it.

      This chapter will try to explain and give some examples of different ways to optimise MySQL. Remember, however, that there are always some (increasingly harder) additional ways to make the system even faster.

      5.1 最適化 概要

      システムを速くするための最も重要な部分は、もちろん基礎的な設計です。 You also need to know what kinds of things your system will be doing, and what your bottlenecks are.

      主なボトルネックは：

      • Disk シーク ： 一片のデータを見つけるためには、ディスクに時間がかかります。 1999年の最新型のディスクでは、このための平均時間は、10msよりも通常より小さいです。 したがって、我々は、理論上は 1秒で約1000 シークすることができます。 この時間は、一つのテーブルであるならば、データの増加と共にディスクアクセスの時間 が少しずつ増加することになり、とても最適化するのは難しくなっていきます。 これを最適化する方法は、データを 1個以上のディスクに分散する事です。
      • Disk reading/writing. When the disk is at the correct position we need to read the data. With modern disks in 1999, one disk delivers something like 10-20Mb/s. This is easier to optimize than seeks because you can read in parallel from multiple disks.
      • CPU cycles. データをメイン・メモリーの中に入れた(または既にメモリに存在している)場合に、 結果を得るためには、それを処理する必要があります。 メモリー容量よりも小さなテーブルを持っている場合、これは、制限の要因となります。 小さいテーブルでは、スピードは、通常問題にはなりません。
      • Memory bandwidth. CPU がキャッシュに収まらないようなデータを要求した場合、メイン・メモリー のバンド幅はボトルネックになります。 これはほとんどのシステムで分かりにくいボトルネックとなりますが、 誰かはそれを知っているべきです。

      5.1.1 MySQL Design Limitations/Tradeoffs

      When using the MyISAM storage engine, MySQL uses extremely fast table locking (multiple readers / single writers). The biggest problem with this table type is a if you have a mix of a steady stream of updates and slow selects on the same table. If this is a problem with some tables, you can use another table type for these. 「7 MySQL テーブル型」節参照.

      MySQL can work with both transactional and not transactional tables. To be able to work smoothly with not transactional tables (which can't rollback if something goes wrong), MySQL has the following rules:

      • All columns have default values.
      • If you insert a 'wrong' value in a column like a NULL in a NOT NULL column or a too big numerical value in a numerical column, MySQL will instead of giving an error instead set the column to the 'best possible value'. For numerical values this is 0, the smallest possible values or the largest possible value. For strings this is either the empty string or the longest possible string that can be in the column.
      • All calculated expressions returns a value that can be used instead of signaling an error condition. For example 1/0 returns NULL

      The reason for the above rules is that we can't check these conditions before the query starts to execute. If we encounter a problem after updating a few rows, we can't just rollback as the table type may not support this. We can't stop because in that case the update would be 'half done' which is probably the worst possible scenario. In this case it's better to 'do the best you can' and then continue as if nothing happened.

      The above means that one should not use MySQL to check fields content, but one should do this in the application.

      5.1.2 Portability

      全てのSQLサーバはそれぞれ異なるSQL処理ルーチンにより構成されています。 したがって色々なSQLサーバ上で同じように動作するような(ポータブルな) SQLアプリケーションを書くのは手間がかかります。 確かに単純なインサートやセレクトを行うようなものは簡単ですが、 必要な機能が増えれば増えるほど難しくなっていきます。 高速動作を要求されるSQLプラットフォームの数が増えれば増えるほど そのようなアプリケーションの開発は大変になっていきます。

      ポータブルな多機能アプリケーションを開発するためには 沢山のSQLサーバでの動作を検証する必要があります。

      You can use the MySQL crash-me program/web-page http://www.mysql.com/information/crash-me.php to find functions, types, and limits you can use with a selection of database servers. Crash-me now tests far from everything possible, but it is still comprehensive with about 450 things tested.

      For example, you shouldn't have column names longer than 18 characters if you want to be able to use Informix or DB2.

      Both the MySQL benchmarks and crash-me programs are very database-independent. By taking a look at how we have handled this, you can get a feeling for what you have to do to write your application database-independent. The benchmarks themselves can be found in the `sql-bench' directory in the MySQL source distribution. They are written in Perl with DBI database interface (which solves the access part of the problem).

      See http://www.mysql.com/information/benchmarks.html for the results from this benchmark.

      As you can see in these results, all databases have some weak points. That is, they have different design compromises that lead to different behaviour.

      If you strive for database independence, you need to get a good feeling for each SQL server's bottlenecks. MySQL is very fast in retrieving and updating things, but will have a problem in mixing slow readers/writers on the same table. Oracle, on the other hand, has a big problem when you try to access rows that you have recently updated (until they are flushed to disk). Transaction databases in general are not very good at generating summary tables from log tables, as in this case row locking is almost useless.

      To get your application really database-independent, you need to define an easy extendable interface through which you manipulate your data. As C++ is available on most systems, it makes sense to use a C++ classes interface to the databases.

      If you use some specific feature for some database (like the REPLACE command in MySQL), you should code a method for the other SQL servers to implement the same feature (but slower). With MySQL you can use the /*! */ syntax to add MySQL-specific keywords to a query. The code inside /**/ will be treated as a comment (ignored) by most other SQL servers.

      If high performance is more important than exactness, as in some web applications, it is possibile to create an application layer that caches all results to give you even higher performance. By letting old results 'expire' after a while, you can keep the cache reasonably fresh. This provides a method to handle high load spikes, in which case you can dynamically increase the cache and set the expire timeout higher until things get back to normal.

      In this case the table creation information should contain information of the initial size of the cache and how often the table should normally be refreshed.

      5.1.3 What Have We Used MySQL For?

      MySQL の初期の開発期には、MySQL は我々のもっとも大口の顧客に合うように 機能が作成されました。 彼らは、いくつかのスウェーデン最大手の小売り業者 のために、倉庫に入れている（商品）データを取り扱います。

      我々は、すべての店から、全ボーナス・カード取扱高の、その週間まとめを得ます。 そして、その店のオーナにとって有益な情報、その店の広告キャンペーンが お客にどの程度影響を及ぼすか、を提供することが、我々に求められています。

      そのデータは、とても大きくて (約700万/月 回の取り扱い)、 我々はその顧客に提供する必要のあるデータを 4〜10年分、持っています。 我々は、カスタマーから、彼らがこのデータからできる新しいレポートに ”即時に”アクセスしたいという、要求を受けました。

      我々はこれを、全ての月ごとの情報を圧縮した 'transaction' テーブルに 保存することで解決しました。 We have a set of simple macros (script) that generates summary tables grouped by different criteria (product group, customer id, store ...) from the transaction tables. そのレポートは Web ページで、これは小さな perl スクリプトで動的に 作成されます。 この perl script は Web Page を分析し、SQL 文を 実行し、結果を挿入します。 We would have used PHP or mod_perl instead but they were not available at that time.

      画像データのために、我々は簡単なツールを C でかきました。 これは SQL のクエリの結果を元に(結果にいくつか処理をして) GIF を提供します。 これも動的に perl スクリプト(HTML ファイルを分析する)から実行されます。

      In most cases a new report can simply be done by copying an existing script and modifying the SQL query in it. In some cases, we will need to add more fields to an existing summary table or generate a new one, but this is also quite simple, as we keep all transactions tables on disk. (Currently we have at least 50G of transactions tables and 200G of other customer data.)

      We also let our customers access the summary tables directly with ODBC so that the advanced users can themselves experiment with the data.

      我々はこれらを Sun Ultra SPARCstation (2x200 Mz) で扱っていますが、 なんの問題もありません。 We recently upgraded one of our servers to a 2 CPU 400 Mhz UltraSPARC, and we are now planning to start handling transactions on the product level, which would mean a ten-fold increase of data. We think we can keep up with this by just adding more disk to our systems.

      We are also experimenting with Intel-Linux to be able to get more CPU power cheaper. 現在、我々はバイナリ互換のデータベースフォーマットを持っており (new in Version 3.23) 、我々はこれをアプリケーションのいくつかの部分に使用しはじ める事でしょう。

      Our initial feelings are that Linux will perform much better on low-to-medium load and Solaris will perform better when you start to get a high load because of extreme disk IO, but we don't yet have anything conclusive about this. After some discussion with a Linux Kernel developer, this might be a side effect of Linux giving so much resources to the batch job that the interactive performance gets very low. This makes the machine feel very slow and unresponsive while big batches are going. Hopefully this will be better handled in future Linux Kernels.

      5.1.4 The MySQL Benchmark Suite

      This should contain a technical description of the MySQL benchmark suite (and crash-me), but that description is not written yet. Currently, you can get a good idea of the benchmark by looking at the code and results in the `sql-bench' directory in any MySQL source distributions.

      This benchmark suite is meant to be a benchmark that will tell any user what things a given SQL implementation performs well or poorly at.

      Note that this benchmark is single threaded, so it measures the minimum time for the operations. We plan to in the future add a lot of multi-threaded tests to the benchmark suite.

      For example, (run on the same NT 4.0 machine):

      Reading 2000000 rows by index Seconds Seconds
      mysql 367 249
      mysql_odbc 464
      db2_odbc 1206
      informix_odbc 121126
      ms-sql_odbc 1634
      oracle_odbc 20800
      solid_odbc 877
      sybase_odbc 17614
      Inserting (350768) rows Seconds Seconds
      mysql 381 206
      mysql_odbc 619
      db2_odbc 3460
      informix_odbc 2692
      ms-sql_odbc 4012
      oracle_odbc 11291
      solid_odbc 1801
      sybase_odbc 4802

      In the above test MySQL was run with a 8M index cache.

      We have gathered some more benchmark results at http://www.mysql.com/information/benchmarks.html.

      Note that Oracle is not included because they asked to be removed. All Oracle benchmarks have to be passed by Oracle! We believe that makes Oracle benchmarks very biased because the above benchmarks are supposed to show what a standard installation can do for a single client.

      To run the benchmark suite, you have to download a MySQL source distribution, install the Perl DBI driver, the Perl DBD driver for the database you want to test and then do: 

      cd sql-bench
perl run-all-tests --server=#

      where # is one of supported servers. You can get a list of all options and supported servers by doing run-all-tests --help.

      crash-me tries to determine what features a database supports and what its capabilities and limitations are by actually running queries. For example, it determines:

      • What column types are supported
      • How many indexes are supported
      • What functions are supported
      • How big a query can be
      • How big a VARCHAR column can be

      We can find the result from crash-me on a lot of different databases at http://www.mysql.com/information/crash-me.php.

      5.1.5 Using Your Own Benchmarks

      You should definitely benchmark your application and database to find out where the bottlenecks are. By fixing it (or by replacing the bottleneck with a 'dummy module') you can then easily identify the next bottleneck (and so on). Even if the overall performance for your application is sufficient, you should at least make a plan for each bottleneck, and decide how to solve it if someday you really need the extra performance.

      For an example of portable benchmark programs, look at the MySQL benchmark suite. 「5.1.4 The MySQL Benchmark Suite」節参照. You can take any program from this suite and modify it for your needs. By doing this, you can try different solutions to your problem and test which is really the fastest solution for you.

      It is very common that some problems only occur when the system is very heavily loaded. We have had many customers who contact us when they have a (tested) system in production and have encountered load problems. In every one of these cases so far, it has been problems with basic design (table scans are not good at high load) or OS/Library issues. Most of this would be a lot easier to fix if the systems were not already in production.

      To avoid problems like this, you should put some effort into benchmarking your whole application under the worst possible load! You can use Super Smack for this, and it is available at: http://www.mysql.com/Downloads/super-smack/super-smack-1.0.tar.gz. As the name suggests, it can bring your system down to its knees if you ask it, so make sure to use it only on your development systems.

      5.2 Optimizing SELECTs and Other Queries

      最初に、全てのクエリに影響する一つの事柄をのべます： より複雑な権限の設定を行うと、オーバーヘッドが多くなります。

      もしあなたがいかなる GRANT 文も行っていなければ、 MySQL はパーミッションの検査を少ししか最適化しないでしょう。 So if you have a very high volume it may be worth the time to avoid grants. Otherwise more permission check results in a larger overhead.

      もし MySQL 関数のあるものが確実に問題を引き起こしているのならば、 常に MySQL クライアント側は以下のようになります： 

      mysql> SELECT BENCHMARK(1000000,1+1);
+------------------------+
| BENCHMARK(1000000,1+1) |
+------------------------+
|                      0 |
+------------------------+
1 row in set (0.32 sec)

      上の例では MySQL は 1,000,000 + 式を 0.32 秒で実行できています (たんなる PentiumII 400MHz マシンで)。

      全ての MySQL 関数は最適化されていますが、 いくつかは例外があるかもしれません。 BENCHMARK(loop_count,expression)はあなたのクエリの 問題を見つけるためのとてもよいツールです。

      5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)

          EXPLAIN tbl_name
or  EXPLAIN SELECT select_options

      EXPLAIN tbl_name は、 DESCRIBE tbl_name や SHOW COLUMNS FROM tbl_name と同義です。

      もし EXPLAIN をともなって SELECT 構文を実行した場合、 MySQL はこの SELECT がいかに動作するかを説明し、 いかにテーブルが結合されるかの情報を与えます。

      EXPLAIN の情報を元に、インデックスを使用した速い SELECT を 得るためにテーブルにインデックスを加えなくてはならないという事がわかります。

      You should frequently run ANALYZE TABLE to update table statistics such as cardinality of keys which can affect the choices the optimiser makes. 「4.5.2 ANALYZE TABLE Syntax」節参照.

      テーブル結合の最適化もオプションによって見ることができます。 SELECT 構文での結合を強制的に最適化するには STRAIGHT_JOIN 節を加え ます。

      単純ではない join のために、EXPLAIN は SELECT 文で使用されている それぞれのテーブルの情報を返します。 テーブルは読まれる順に表示されます。MySQL は one-sweep multi-join method を用いた全ての join を解決します。これは MySQL は最初のテーブルから 一レコード読み込み、二つ目のテーブルからマッチしたレコードを探し、そして三番目を 探すということです。 全てのテーブルが処理される時、選択されたフィールドを出力し、テーブルの一覧は よりマッチするレコードをもつテーブルを見つけるまで back-track されます。 次のレコードはこのテーブルから読まれ、次のテーブルから処理を続けます。

      In MySQL version 4.1 the EXPLAIN output was changed to work better with constructs like UNIONs, subqueries and derived tables. Most notable is the addition of two new columns: id and select_type.

      EXPLAIN の出力は以下のフィールドを含みます：

      id
      SELECT identifier, the sequential number of this SELECT within the query.
      select_type
      Type of SELECT clause, which can be any of the following:
      SIMPLE
      Simple SELECT (without UNIONs or subqueries).
      PRIMARY
      Outermost SELECT.
      UNION
      Second and further UNION SELECTs.
      DEPENDENT UNION
      Second and further UNION SELECTSs, dependent on outer subquery.
      SUBSELECT
      First SELECT in subquery.
      DEPENDENT SUBSELECT
      First SELECT, dependent on outer subquery.
      DERIVED
      Derived table SELECT.
      table
      出力レコードが参照されるテーブル
      type
      join タイプ. join type は以下のものがあります。良い物から順に書いています：
      system
      テーブルが一レコードだけ持っている (= system table). これは const join type の特別な場合です。
      const
      テーブルは、最もマッチするレコードを１つもっており、これはクエリの 最初に読まれます。 1 つのレコードであるため、このレコード中のフィールドの値は オプティマイザーによって常数としてみなされます。 1回だけ読まれるので、const テーブルはとても速いです!
      eq_ref
      前のテーブルのそれぞれのレコードと結合する際、このテーブルから1レコード読まれま す。これは join では const よりも良い形です。 インデックスの全てのパートが join で使用され、かつ、インデックスが UNIQUE か PRIMARY KEY であるときに、これは使用されます。
      ref
      インデックスの値に合ったすべてのレコードは、前のテーブルからレコードと結合するた めに、このテーブルから読まれるでしょう。 もしその join がキーの一番左の接頭部分だけを使用するならば、 あるいは、もしそのキーが UNIQUE や PRIMARY KEY でなければ (言い換えるなら、もし join がキーの値を元に一つだけの、レコードを選択できなけれ ば)、ref は使用されます。 もしそのキーがいくつかのマッチするレコードに使用されるだけなら、 join は良い形です。
      range
      示された範囲内にあるレコードのみが検索されます。 key 項目はどのインデックスが使用されているか示します。 The key_len contains the longest key part that was used. The ref column will be NULL for this type.
      index
      ALL と同じですが、インデックスツリーが走査される場合のみを除きます。 これは、インデックスファイルはデータファイルよりも小さいため、通常 ALL よ り速いです。
      ALL
      前のテーブルのレコードとのそれぞれの結合において、全テーブルが走査されます。 もしそのテーブルが最初のテーブルで const 状態ではないなら、通常 これは良くありません。他の状態ではとても悪くなります。 これは普通、レコードががより早いテーブルからから定数値に基づいて検索することがで きるように、 インデックスを追加することにより ALL を避けることが可能です。
      possible_keys
      possible_keys 項目は、MySQL がテーブルからレコードを見つけるために どのインデックスを使用する事ができたかを示します。 注意: このフィールドはテーブルの順にまったく依存しません。これは、 possible_keys 内のいくつかのキーは、生成されたテーブル順での実行に使用でき ないことを意味します。 この項目が空なら、関連した インデックスは無いということです。この場合、あなたは WHERE 節を 調べることによって、クエリの性能を向上させることができるかもしれません。 もしそれがインデックスに適合したフィールドを参照しているならば。 仮にそうだとすると、適切なインデックスを作成し、 EXPLAIN でクエリを もう一度チェックしてみてください。 テーブルがどんなインデックスを持っているかみるには、SHOW INDEX FROM tbl_name とします。
      key
      key 項目は、 MySQL が使用すると実際に決めたキー(インデックス)を示します。 どのインデックスも選ばれなかったならば、インデックスは NULL です。 MySQL に possible_keys 項目にあるインデックスを使用するように 強制するにはクエリに USE KEY/IGNORE KEY を使用することができます。 「6.4.1 SELECT 構文」節参照. Also, running myisamchk --analyze ( 「4.4.6.1 myisamchk 起動構文」節参照) or ANALYZE TABLE ( 「4.5.2 ANALYZE TABLE Syntax」節参照) on the table will help the optimiser choose better indexes.
      key_len
      key_len 項目は、MySQL が使用すると決めたキーの長さを示します。 もし key が NULL なら、長さは NULL です。 注意: これはMySQL がマルチパートキーのいくつのパートを実際に使用 するかを示します。
      ref
      ref 項目は、テーブルからレコードを select するために、どのフィールドや 定数が key と共に使用されたかを示します。
      rows
      rows フィールドは、MySQL がクエリを実行するために検査する 必要があると考えているレコードの数を示します。
      Extra
      このフィールドは、MySQL がどのようにクエリを解決するかの追加情報 を含んでいます。ここで、このフィールドに現れ得る様々なテキスト文字列の説明 をします:
      Distinct
      MySQL will not continue searching for more rows for the current row combination after it has found the first matching row.
      Not exists
      MySQL はクエリの LEFT JOIN 最適化を行なうことができて、 LEFT JOIN 判定基準に適合する１つのレコードを見つけた後、前のレコード組 み合わせについてこのテーブルにそれ以上のレコードを検査しません。 Here is an example for this: 
      SELECT * FROM t1 LEFT JOIN t2 ON t1.id=t2.id WHERE t2.id IS NULL;
      Assume that t2.id is defined with NOT NULL. In this case MySQL will scan t1 and look up the rows in t2 through t1.id. If MySQL finds a matching row in t2, it knows that t2.id can never be NULL, and will not scan through the rest of the rows in t2 that has the same id. In other words, for each row in t1, MySQL only needs to do a single lookup in t2, independent of how many matching rows there are in t2.
      range checked for each record (index map: #)
      MySQL は使用すべき本当に良いインデックスを見つけられませんでし た。先行するテーブル内に各レコードの結合の代わりに、テーブルからレコード を取り出すためにどのインデックスを使用するかチェックを行ないます。これは とても速いというわけではありませんが、もちろんインデックス無しでの結合を 行なわなければならないよりは速いです。
      Using filesort
      MySQL は、ソート順でレコードを取り出す方法を見つけ出すため、余 計なパスの実行が必要です。ソートは、join type に一致する全てのレ コードを通して行なわれ、WHERE に適合する全てのレコードについて、 ソートキーとレコードへのポインタを格納します。それから、キーがソートされま す。最後にレコードはソートされた順に取り出されます。
      Using index
      フィールド情報は、実際のレコードから読み込む追加シークを行なうことはせず に、インデックスツリー内の情報だけを使用するテーブルから取り出されます。 テーブルについての使用される全てのフィールドが同じインデックスの一部であ る時にこれが行なわれます。
      Using temporary
      クエリを解決できるように、MySQL は、結果を保持するための一時テー ブルを作成する必要があります。これは通常 GROUP BY が行なわれたも のとは別のフィールド上で ORDER BY を行なう場合に発生します。
      Using where
      どのレコードが次のテーブルに対して適合するか、またはクライアントに送られ るかを制限するために、WHERE 節が使用されます。この情報がなくて、 テーブルが型 ALL か index であれば、クエリ内に何か間違った ものがあります(テーブルから全てのレコードを fetch/examine しようとしてい るのでなければ)。
      クエリを可能な限り速く得たい場合、Using filesort と Using temporary に注意すべきです。

      EXPLAIN 出力の rows フィールド内のすべての値を増やすことによ り、join がどのように良くなるかの良い表示を得ることができます。これは、 MySQL がクエリ実行の検査をする必要があるレコードのおおよその数を 知らせます。この数は max_join_size 変数でのクエリを制限する時にも使 用します。 「5.5.2 サーバーパラメーターのチューニング」節参照.

      以下の例は、EXPLAIN が提供する情報を元に、いかに JOIN が最適化 できるかの例です。

      以下のような EXPLAIN で検査する SELECT 構文があるとします： 

      EXPLAIN SELECT tt.TicketNumber, tt.TimeIn,
            tt.ProjectReference, tt.EstimatedShipDate,
            tt.ActualShipDate, tt.ClientID,
            tt.ServiceCodes, tt.RepetitiveID,
            tt.CurrentProcess, tt.CurrentDPPerson,
            tt.RecordVolume, tt.DPPrinted, et.COUNTRY,
            et_1.COUNTRY, do.CUSTNAME
        FROM tt, et, et AS et_1, do
        WHERE tt.SubmitTime IS NULL
            AND tt.ActualPC = et.EMPLOYID
            AND tt.AssignedPC = et_1.EMPLOYID
            AND tt.ClientID = do.CUSTNMBR;

      この例では、以下のように仮定します：

      • フィールドは以下のように定義されています：
        Table Column Column type
        tt ActualPC CHAR(10)
        tt AssignedPC CHAR(10)
        tt ClientID CHAR(10)
        et EMPLOYID CHAR(15)
        do CUSTNMBR CHAR(15)
      • テーブルは以下のインデックスを持ちます：
        Table Index
        tt ActualPC
        tt AssignedPC
        tt ClientID
        et EMPLOYID (primary key)
        do CUSTNMBR (primary key)
      • tt.ActualPC の値は、いちように分布して(配置されて)いません。

      最初、いかなる最適化も行われていない状態では、EXPLAIN 構文は 以下の情報を提示します： 

      table type possible_keys                key  key_len ref  rows  Extra
et    ALL  PRIMARY                      NULL NULL    NULL 74
do    ALL  PRIMARY                      NULL NULL    NULL 2135
et_1  ALL  PRIMARY                      NULL NULL    NULL 74
tt    ALL  AssignedPC,ClientID,ActualPC NULL NULL    NULL 3872
      range checked for each record (key map: 35)

      それぞれのテーブルで、type が ALL になっています。 これは MySQL が全てのテーブルを全結合することを示します！ それぞれのテーブル内の行数分から作った物が調べられるので、とても長い時間がかかり ます！ この場合、74 * 2135 * 74 * 3872 = 45,268,558,720 行調べることになります。 テーブルが肥大化したときにかかる時間を考えてください....

      一つ問題があります。(まだ) MySQL がフィールドのインデックスを効果的に 使用できていません。 この例の場合では、VARCHAR と CHAR は、それらが同じ長さで定義されて いれば、変わりがありません。 tt.ActualPC は CHAR(10) と定義されており、 et.EMPLOYID は CHAR(15) です。これらの長さは違います。

      この不釣り合いを修正するにあたり、ALTER TABLE を使って ActualPC の長さを 10 文字から 15 文字にします： 

      mysql> ALTER TABLE tt MODIFY ActualPC VARCHAR(15);

      これで tt.ActualPC and et.EMPLOYID は両方とも VARCHAR(15) になりました。 EXPLAIN 構文を実行し直すと、以下を提示します： 

      table type   possible_keys   key     key_len ref         rows    Extra
tt    ALL    AssignedPC,ClientID,ActualPC NULL NULL NULL 3872    Using where
do    ALL    PRIMARY         NULL    NULL    NULL        2135
      range checked for each record (key map: 1)
et_1  ALL    PRIMARY         NULL    NULL    NULL        74
      range checked for each record (key map: 1)
et    eq_ref PRIMARY         PRIMARY 15      tt.ActualPC 1

      まだ完全ではありませんが、よりよくなっています(rows 値の 生成量は 74 より小さくなります)。この場合、実行は数秒でしょう。

      A second alteration can be made to eliminate the column length mismatches for the tt.AssignedPC = et_1.EMPLOYID and tt.ClientID = do.CUSTNMBR comparisons: 

      mysql> ALTER TABLE tt MODIFY AssignedPC VARCHAR(15),
    ->                MODIFY ClientID   VARCHAR(15);

      これで EXPLAIN は以下を出力します： 

      table type   possible_keys   key      key_len ref           rows Extra
et    ALL    PRIMARY         NULL     NULL    NULL          74
tt    ref    AssignedPC,     ActualPC 15      et.EMPLOYID   52   Using where
             ClientID,
             ActualPC
et_1  eq_ref PRIMARY         PRIMARY  15      tt.AssignedPC 1
do    eq_ref PRIMARY         PRIMARY  15      tt.ClientID   1

      これは ``ほとんど'' 最良に近いです。

      残る問題は、デフォルトでは、MySQL は tt.ActualPC フィールド内の 値がまんべんなく分布していると想定しており、この tt テーブルの場合には 適合しません。 幸運にも、これを MySQL に教えるのはとても簡単です： 

      shell> myisamchk --analyze PATH_TO_MYSQL_DATABASE/tt
shell> mysqladmin refresh

      これで join は ``完璧'' です。 EXPLAIN は以下の結果を示します： 

      table type   possible_keys key     key_len ref           rows Extra
tt    ALL    AssignedPC    NULL    NULL    NULL          3872 Using where
             ClientID,
             ActualPC
et    eq_ref PRIMARY       PRIMARY 15      tt.ActualPC   1
et_1  eq_ref PRIMARY       PRIMARY 15      tt.AssignedPC 1
do    eq_ref PRIMARY       PRIMARY 15      tt.ClientID   1

      EXPLAIN の出力中の rows 項目は、 MySQL JOIN オプティマイ ザーによる、``推測'' です； クエリの最適化のために、この数値が実際に近いかどうかをチェックすべきです。 そうでなければ、SELECT ステートメントで STRAIGHT_JOIN を使用 し、FROM 節に異なる順でテーブルを並べることで、良いパフォーマンスを 得られます。

      5.2.2 Estimating Query Performance

      ほとんどの場合、ディスク・シークを数えることでだいたいのパフォーマンスを予測でき ます。 小さなテーブルでは、通常、1回のディスク・シークでレコードを見つけれるでしょう (インデックスがたぶんキャッシュされるので)。 大きなテーブルでは、 おおよその予測として、(B++ ツリーインデックスを使用している場合)、 log(row_count) / log(index_block_length / 3 * 2 / (index_length + data_pointer_length)) + 1 シーク、1レコードを見つけるのに必要となるでしょう。

      MySQL では、インデックス・ブロックは通常 1024 バイトで、 データ・ポインターは通常 4 バイトです。 これは、 インデックス長が 3 (medium integer) 、データが 500,000 レコードあるテーブルでは、 log(500,000)/log(1024/3*2/(3+4)) + 1 = 4 シークとなります。

      As the above index would require about 500,000 * 7 * 3/2 = 5.2M, (assuming that the index buffers are filled to 2/3, which is typical) you will probably have much of the index in memory and you will probably only need 1-2 calls to read data from the OS to find the row.

      書き込み時には、上の場合、新しいインデックスを書き込める場所を 探し出すのに、4 シークかかり、さらに、通常、インデックスを更新し、 レコードを書くのに 2 シーク必要です。

      Note that the above doesn't mean that your application will slowly degenerate by log N! As long as everything is cached by the OS or SQL server things will only go marginally slower while the table gets bigger. After the data gets too big to be cached, things will start to go much slower until your applications is only bound by disk-seeks (which increase by log N). To avoid this, increase the index cache as the data grows. 「5.5.2 サーバーパラメーターのチューニング」節参照.

      5.2.3 SELECT クエリの速度

      通常、遅い SELECT ... WHERE を速くするには、 まず最初にインデックスがあるかどうかをチェックします。 「5.4.3 MySQL はどのようにインデックスを使用するか？」節参照. 違うテーブルを参照する場合には、普通はインデックスをともなうべきです。 EXPLAIN コマンドを使用すれば、SELECT でどのインデックスが 使用されているか確認できます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.

      Some general tips:

      • To help MySQL optimize queries better, run myisamchk --analyze on a table after it has been loaded with relevant data. This updates a value for each index part that indicates the average number of rows that have the same value. (For unique indexes, this is always 1, of course.) MySQL will use this to decide which index to choose when you connect two tables with 'a non-constant expression'. You can check the result from the analyze run by doing SHOW INDEX FROM table_name and examining the Cardinality column.
      • インデックスとデータをインデックス順に従ってソートするには、 myisamchk --sort-index --sort-records=1 を使用します (もし １番目のインデックス順にソートするなら)。 If you have a unique index from which you want to read all records in order according to that index, this is a good way to make that faster. しかし、このソート方法は最適状態では書かれず、また大きなテーブルでは 多くの時間がかかることに注意してください！

      5.2.4 MySQL はどのように WHERE 節を最適化するか？

      WHERE の最適化は、WHERE がほとんど SELECT で使用されるため、 SELECT に置かれています。 しかし、同じ最適化は DELETE や UPDATE 文でも使用されます。

      このセクションの最適化の説明はまだ不十分です。 なぜなら、 MySQL はとても多くの最適化を行っており、 それら全てについての説明を書ける時間が、我々はとれません。

      MySQLによる最適化のいくつかを以下に示します:

      • 括弧の除去 (全ての不必要な括弧は削除されます): 
           ((a AND b) AND c OR (((a AND b) AND (c AND d))))
-> (a AND b AND c) OR (a AND b AND c AND d)
      • 定数の保持: 
           (a<b AND b=c) AND a=5
-> b>5 AND b=c AND a=5
      • 定数条件の除去 (定数保持のために必要とされます): 
           (B>=5 AND B=5) OR (B=6 AND 5=5) OR (B=7 AND 5=6)
-> B=5 OR B=6
      • インデックスに使用される全ての表現は一度だけ評価されます。
      • 一つのテーブル上の WHERE がない COCOUNT(*) は、 MyISAM and HEAP の場合は テーブルの情報から 直接取り出されます。これはまた 1つのテーブルだけで NOT NULL を 使用したときも同様です。
      • 不当な定数表現は早く検出されます。 MySQL は不可能な SELECT 構文を素早く見つけ、0 行を結果として返 します。
      • GROUP BY または group 関数 (COUNT(), MIN()...) を使用しない 場合は、 HAVING は WHERE とマージされます。
      • 各サブ結合についての速い WHERE 評価を得るために、また、可能な限り 早くレコードをスキップするために、各サブ結合についてより簡単な WHERE が構築されます。
      • 全ての定数テーブルをクエリー中の他のテーブルより先に読みます。 定数テーブルは次です:
        • 0 または 1 レコードのテーブル。
        • WHERE 節で UNIQUE インデックスや PRIMARY KEY が使用されたテ ーブルで、かつ、全てのインデックスが定数式で使用されていて、 かつ、インデックスのパートが NOT NULL で定義されているテーブル。
        以下のテーブルのように定数だけを使用するテーブル: 
        mysql> SELECT * FROM t WHERE primary_key=1;
mysql> SELECT * FROM t1,t2
    ->          WHERE t1.primary_key=1 AND t2.primary_key=t1.id;
      • テーブルを結合するために最良の結合の組合せを見つけます。全ての可能性を試して 。 ORDER BY または GROUP 内の全てのフィールドが同じテーブルの場合は、 このテーブルは結合時に最初に優先されます。
      • ORDER BY 節と GROUP BY 節がある場合、または ORDER BY か GROUP BY が結合キュー内の最初のテーブルではない他のテーブルからの項目を 含む場合、一時テーブルが生成されます。
      • もし SQL_SMALL_RESULT を使用するなら, MySQL はメモリー内の一時 テーブルを使用します
      • 各テーブルのインデックスはクエリされ、得られる行の 30% 未満の幅しかない最良のイ ンデックスが使用されます。 そのようなインデックスが見つけられない場合、素早いテーブルの走査 (quick table scan)が使用されます。
      • 同じように、MySQL はデータファイルを等しく調べはしないインデックスから レコードを読むことが可能です。もし全てのフィールドが数値型のインデックスなら、 インデックスツリーだけがクエリの解決に使用されます。
      • 各レコードが出力される前に、HAVING 節に適合するものをスキップします。

      以下はとても速いクエリの例です: 

      mysql> SELECT COUNT(*) FROM tbl_name;
mysql> SELECT MIN(key_part1),MAX(key_part1) FROM tbl_name;
mysql> SELECT MAX(key_part2) FROM tbl_name
    ->        WHERE key_part_1=constant;
mysql> SELECT ... FROM tbl_name
    ->        ORDER BY key_part1,key_part2,... LIMIT 10;
mysql> SELECT ... FROM tbl_name
    ->        ORDER BY key_part1 DESC,key_part2 DESC,... LIMIT 10;

      以下のクエリはインデックスツリーのみを使用します(インデックス化されているフィー ルドは数値型と仮定します)： 

      mysql> SELECT key_part1,key_part2 FROM tbl_name WHERE key_part1=val;
mysql> SELECT COUNT(*) FROM tbl_name
    ->        WHERE key_part1=val1 AND key_part2=val2;
mysql> SELECT key_part2 FROM tbl_name GROUP BY key_part1;

      以下のクエリは、ソートされた行の検索にインデックスを使用します： 

      mysql> SELECT ... FROM tbl_name
    ->            ORDER BY key_part1,key_part2,... ;
mysql> SELECT ... FROM tbl_name
    ->            ORDER BY key_part1 DESC,key_part2 DESC,... ;

      5.2.5 How MySQL Optimizes DISTINCT

      DISTINCT is converted to a GROUP BY on all columns, DISTINCT combined with ORDER BY will in many cases also need a temporary table.

      When combining LIMIT # with DISTINCT, MySQL will stop as soon as it finds # unique rows.

      If you don't use columns from all used tables, MySQL will stop the scanning of the not used tables as soon as it has found the first match. 

      SELECT DISTINCT t1.a FROM t1,t2 where t1.a=t2.a;

      In the case, assuming t1 is used before t2 (check with EXPLAIN), then MySQL will stop reading from t2 (for that particular row in t1) when the first row in t2 is found.

      5.2.6 MySQL はどのように LEFT JOIN と RIGHT JOIN を最適化するか？

      MySQL の A LEFT JOIN B は以下のように組みこまれています：

      • The table B is set to be dependent on table A and all tables that A is dependent on.
      • テーブル A が LEFT JOIN 条件中に使用される全てのテーブル （ただし B は除く）に依存すると、セットされます。
      • 全ての LEFT JOIN 条件が WHERE 節に移動されます。
      • All standard join optimizations are done, with the exception that a table is always read after all tables it is dependent on. If there is a circular dependence then MySQL will issue an error.
      • 全ての WHERE 節の最適化が行われます。
      • WHERE 節にマッチするレコードが A にあり、 LEFT JOIN 条件にマッチするレコードが B にない場合、 全てのフィールドが NULL にセットされた B のレコードが 作成されます。
      • If you use LEFT JOIN to find rows that don't exist in some table and you have the following test: column_name IS NULL in the WHERE part, where column_name is a column that is declared as NOT NULL, then MySQL will stop searching after more rows (for a particular key combination) after it has found one row that matches the LEFT JOIN condition.

      RIGHT JOIN is implemented analogously as LEFT JOIN.

      The table read order forced by LEFT JOIN and STRAIGHT JOIN will help the join optimizer (which calculates in which order tables should be joined) to do its work much more quickly, as there are fewer table permutations to check.

      Note that the above means that if you do a query of type: 

      SELECT * FROM a,b LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key)
         WHERE b.key=d.key

      MySQL will do a full scan on b as the LEFT JOIN will force it to be read before d.

      The fix in this case is to change the query to: 

      SELECT * FROM b,a LEFT JOIN c ON (c.key=a.key) LEFT JOIN d (d.key=a.key)
         WHERE b.key=d.key

      5.2.7 How MySQL Optimises ORDER BY

      In some cases MySQL can uses index to satisfy an ORDER BY or GROUP BY request without doing any extra sorting.

      The index can also be used even if the ORDER BY doesn't match the index exactly, as long as all the unused index parts and all the extra are ORDER BY columns are constants in the WHERE clause. The following queries will use the index to resolve the ORDER BY / GROUP BY part: 

      SELECT * FROM t1 ORDER BY key_part1,key_part2,...
SELECT * FROM t1 WHERE key_part1=constant ORDER BY key_part2
SELECT * FROM t1 WHERE key_part1=constant GROUP BY key_part2
SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 DESC
SELECT * FROM t1 WHERE key_part1=1 ORDER BY key_part1 DESC,key_part2 DESC

      Some cases where MySQL can not use indexes to resolve the ORDER BY: (Note that MySQL will still use indexes to find the rows that matches the WHERE clause):

      • You are doing an ORDER BY on different keys: SELECT * FROM t1 ORDER BY key1,key2
      • You are doing an ORDER BY using non-consecutive key parts. SELECT * FROM t1 WHERE key2=constant ORDER BY key_part2
      • You are mixing ASC and DESC. SELECT * FROM t1 ORDER BY key_part1 DESC,key_part2 ASC
      • The key used to fetch the rows are not the same one that is used to do the ORDER BY: SELECT * FROM t1 WHERE key2=constant ORDER BY key1
      • You are joining many tables and the columns you are doing an ORDER BY on are not all from the first not-const table that is used to retrieve rows (This is the first table in the EXPLAIN output which doesn't use a const row fetch method).
      • You have different ORDER BY and GROUP BY expressions.
      • The used table index is an index type that doesn't store rows in order. (Like the HASH index in HEAP tables).

      In the cases where MySQL have to sort the result, it uses the following algorithm:

      • Read all rows according to key or by table scanning. Rows that don't match the WHERE clause are skipped.
      • Store the sort-key in a buffer (of size sort_buffer).
      • When the buffer gets full, run a qsort on it and store the result in a temporary file. Save a pointer to the sorted block. (In the case where all rows fits into the sort buffer, no temporary file is created)
      • Repeat the above until all rows have been read.
      • Do a multi-merge of up to MERGEBUFF (7) regions to one block in another temporary file. Repeat until all blocks from the first file are in the second file.
      • Repeat the following until there is less than MERGEBUFF2 (15) blocks left.
      • On the last multi-merge, only the pointer to the row (last part of the sort-key) is written to a result file.
      • Now the code in `sql/records.cc' will be used to read through them in sorted order by using the row pointers in the result file. To optimise this, we read in a big block of row pointers, sort these and then we read the rows in the sorted order into a row buffer (record_rnd_buffer) .

      You can with EXPLAIN SELECT ... ORDER BY check if MySQL can use indexes to resolve the query. If you get Using filesort in the extra column, then MySQL can't use indexes to resolve the ORDER BY. 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.

      If you want to have a higher ORDER BY speed, you should first see if you can get MySQL to use indexes instead of having to do an extra sorting phase. If this is not possible, then you can do:

      • Increase the size of the sort_buffer variable.
      • Increase the size of the record_rnd_buffer variable.
      • Change tmpdir to point to a dedicated disk with lots of empty space. If you use MySQL 4.1 or later you can spread load between several physical disks by setting tmpdir to a list of paths separated by colon : (semicolon ; on Windows). They will be used in round-robin fashion. Note: These paths should end up on different physical disks, not different partitions of the same disk.

      MySQL by default sorts all GROUP BY x,y[,...] queries as if you would have specified ORDER BY x,y[,...]. MySQL will optimise away any ORDER BY as above without any speed penalty. If you by in some cases don't want to have the result sorted you can specify ORDER BY NULL: 

      INSERT INTO foo SELECT a,COUNT(*) FROM bar GROUP BY a ORDER BY NULL;

      5.2.8 MySQL はどのように LIMIT を最適化するか？

      In some cases MySQL will handle the query differently when you are using LIMIT # and not using HAVING:

      • もし LIMIT を使用して限定した数だけ select を行うなら、 MySQL は、 ある場合、テーブルを全て走査するよりも、インデックスを使用しようとします。
      • もし LIMIT # を ORDER BY と共に使用するなら, MySQL は 最初の # 行を見つけたらすぐに、全テーブルのソートは行わずに、 ソートを終わらせます。
      • LIMIT # を DISTINCT と共に使用するなら, MySQL は # 個の一意なレコードを見つけた時点で終わります。
      • In some cases a GROUP BY can be resolved by reading the key in order (or do a sort on the key) and then calculate summaries until the key value changes. In this case LIMIT # will not calculate any unnecessary GROUP BYs.
      • MySQL は、最初の # 行をクライアントに送った後すぐに、 クエリを中断します。 (if you are not using SQL_CALC_FOUND_ROWS).
      • LIMIT 0 は常に素早く空の結果を返します。 これはクエリのチェックや結果として得られるフィールドの型を得るために利用できます。
      • 一時テーブルの大きさは、クエリを解決するためにどれぐらいのスペースがいるかを 計算するのに、LIMIT # を使用します。

      5.2.9 INSERT クエリの速度

      レコードを挿入する時間はおおよそ次からなります:

      • Connect: (3)
      • Sending query to server: (2)
      • Parsing query: (2)
      • Inserting record: (1 x size of record)
      • Inserting indexes: (1 x number of indexes)
      • Close: (1)

      ここで (数字) は比例時間です。これは、テーブルのオープンにかかる初期オーバーヘッ ド(これは同時に動作する各クエリ毎に1回行なわれます)は考慮されていません。

      テーブルのサイズはインデックスの挿入を log N で遅くします (B-tree)。

      INSERT を速くするいくつかの方法：

      • もし同じクライアントから多くのレコードを同時にインサートするなら、 複数の値が書ける INSERT 文を使用します。 これは個々に INSERT 文 を発行する場合に比べて、とても速くなります。 If you are adding data to non-empty table, you may tune up bulk_insert_buffer_size variable to make it even faster. 「4.5.6.4 SHOW VARIABLES」節参照.
      • もし違うクライアントから多くのレコードを同時にインサートするなら、 INSERT DELAYED 文の使用で、より速くなるでしょう。 「6.4.3 INSERT 構文」節参照.
      • MyISAM では、複数の SELECT が走っているテーブルに対して、 同時に、レコードを挿入できます。 ただしそのテーブルに対して レコードの削除がない場合に。
      • テキストファイルからテーブルにデータをいれる場合は、 LOAD DATA INFILE を 使用します。 これはたくさんの INSERT 文の発行に比べて通常 20倍 程度 速くなります 「6.4.9 LOAD DATA INFILE 構文」節参照.
      • テーブルが多くのインデックスを持っている場合、ある方法で、 LOAD DATA INFILE の実行を速くすることが可能です。 以下の手順で行います：
        1. Optionally create the table with CREATE TABLE. For example, using mysql or Perl-DBI.
        2. FLUSH TABLES の実行。 あるいは mysqladmin flush-tables コマンドの実行。
        3. myisamchk --keys-used=0 -rq /path/to/db/tbl_name の使用。 これは指定されたテーブルから全てのインデックスを削除します。
        4. そのテーブルに LOAD DATA INFILE を使用してデータを入れます. これはいかなるインデックスも更新しないでしょうし、そのため、速くもなるでしょう。
        5. If you are going to only read the table in the future, run myisampack on it to make it smaller. 「7.1.2.3 圧縮テーブルの特徴」節参照.
        6. myisamchk -r -q /path/to/db/tbl_name でインデックスを再構築. これは disk に書き込む前にインデックスをメモリに作成します。 これは多くのディスクシークを避けることが出来るのでとても速くなります。 でき上がったインデックスツリーは、バランスのよいものになります。
        7. FLUSH TABLES の実行。 あるいは mysqladmin flush-tables コマンドの実行。
        この手順は、将来の MySQL の LOAD DATA INFILE に組み込むかもしれません。
      • Note that LOAD DATA INFILE also does the above optimization if you insert into an empty table; the main difference with the above procedure is that you can let myisamchk allocate much more temporary memory for the index creation that you may want MySQL to allocate for every index recreation. Since MySQL 4.0 you can also use ALTER TABLE tbl_name DISABLE KEYS instead of myisamchk --keys-used=0 -rq /path/to/db/tbl_name and ALTER TABLE tbl_name ENABLE KEYS instead of myisamchk -r -q /path/to/db/tbl_name. This way you can also skip FLUSH TABLES steps.
      • You can speed up insertions that is done over multiple statements by locking your tables: 
        mysql> LOCK TABLES a WRITE;
mysql> INSERT INTO a VALUES (1,23),(2,34),(4,33);
mysql> INSERT INTO a VALUES (8,26),(6,29);
mysql> UNLOCK TABLES;
        主な速度差は、全ての INSERT 構文でインデックスバッファが一度だけディスク にフラッシュされることです。通常は INSERT 構文があるのと同じくらい多くの インデックスバッファフラッシュがあります。単一構文の全てのレコードは、ロック なしで挿入できます。 For transactional tables, you should use BEGIN/COMMIT instead of LOCK TABLES to get a speedup. ロックも複数接続テストの合計時間を低くしますが、いくつかのスレッドの最大 待ち時間は上がります(ロックを待っているから)。 例えば: 
        thread 1 does 1000 inserts
thread 2, 3, and 4 does 1 insert
thread 5 does 1000 inserts
        ロックを使用しない場合、2, 3 そして 4 は 1 と 5 の前に終ります。ロックを 使用する場合、2,3,4 は 1 や 5 の前に終わることはおそらくありませんが、合 計時間は約 40 % 速くなります。 INSERT, UPDATE , DELETE は、 MySQL ではとても速い ので、 1 行で約 5 つ以上、値を 挿入・更新 をする操作に対して、 ロックを追加すれば、全般的により良い性能が得られます。 とても多い insert を行なう場合、 他のスレッドにそのロックしたテーブルへのアクセスを与えるために 、 だいたい 1000 レコードごとに一度、UNLOCK TABLES した後に LOCK TABLES を行います。 これでもまだ良い性能が得られます。 もちろん LOAD DATA INFILE はとても速いです。

      LOAD DATA INFILE と INSERT を共に速くするためには、 キーバッファを増やします。 「5.5.2 サーバーパラメーターのチューニング」節参照.

      5.2.10 UPDATE クエリの速度

      UPDATE クエリは SELECT クエリのように最適化されますが、 書き込みのオーバーヘッドが加わります。 書き込み速度は、更新されるデータの大きさ、更新されるインデックス数に 依ります。 変更されないインデックスは更新されません。

      Also, another way to get fast updates is to delay updates and then do many updates in a row later. Doing many updates in a row is much quicker than doing one at a time if you lock the table.

      Note that, with dynamic record format, updating a record to a longer total length may split the record. So if you do this often, it is very important to OPTIMIZE TABLE sometimes. 「4.5.1 OPTIMIZE TABLE 構文」節参照.

      5.2.11 DELETE クエリの速度

      If you want to delete all rows in the table, you should use TRUNCATE TABLE table_name. 「6.4.7 TRUNCATE 構文」節参照.

      1レコードを削除する時間は、ちょうどインデックスの数に比例します。 より速くレコードを削除したいなら、インデックス・キャッシュを 増やします。 「5.5.2 サーバーパラメーターのチューニング」節参照.

      5.2.12 最適化に関するその他の助言

      Unsorted tips for faster systems:

      • コネクションオーバーヘッドを避けるために、データベースに対して、 逐次コネクションを落とさないように、常に接続を保ちます。 If you can't use persistent connections and you are doing a lot of new connections to the database, you may want to change the value of the thread_cache_size variable. 「5.5.2 サーバーパラメーターのチューニング」節参照.
      • あなたのクエリがテーブルのインデックスを使用しているか、いつもチェックします。 MySQL では EXPLAIN コマンドでこれが行えれます。 「5.2.1 EXPLAIN 構文 (SELECTについての情報を得る)」節参照.
      • MyISAM では、大量に変更されるようなテーブルに対して、 複雑な SELECT クエリを避けるように試みます。 これはテーブル・ロックの問題を避けるためです。
      • 新しい MyISAM テーブルでは、あるテーブルにレコードが挿入(削除は無しで) されている最中に、同時に、同じテーブルからデータを読むことが可能です。 これがあなたにとって重要項目であるなら、 レコードの削除の必要のない方法や、多くのレコードを削除した後に OPTIMIZE TABLE を実行することを、考慮すべきです。
      • Use ALTER TABLE ... ORDER BY expr1,expr2... if you mostly retrieve rows in expr1,expr2... order. By using this option after big changes to the table, you may be able to get higher performance.
      • In some cases it may make sense to introduce a column that is 'hashed' based on information from other columns. If this column is short and reasonably unique it may be much faster than a big index on many columns. In MySQL it's very easy to use this extra column: SELECT * FROM table_name WHERE hash=MD5(CONCAT(col1,col2)) AND col_1='constant' AND col_2='constant'
      • 多くの変更がなされるテーブルに対しては、全ての VARCHAR や BLOB フィールドを避けるように試みるべきです。 You will get dynamic row length as soon as you are using a single VARCHAR or BLOB column. 「7 MySQL テーブル型」節参照.
      • 通常、あるテーブルを違うテーブルに分けることは、レコードが大きくなる ために役立ちません。 レコードにアクセスする際、そのレコードの最初のバイトを見つけるための ディスク・シークが、一番かかります。 After finding the data most new disks can read the whole row fast enough for most applications. The only cases where it really matters to split up a table is if it's a dynamic row size table (see above) that you can change to a fixed row size, or if you very often need to scan the table and don't need most of the columns. 「7 MySQL テーブル型」節参照.
      • もし、多くのレコードからの情報を元にした計算(あるもののカウントとか)を しょっちゅう行う必要があるなら、新しいテーブルを用意し、逐次カウンターを 更新した方が多分良いでしょう。 UPDATE table SET count=count+1 WHERE index_column=constant の更新は とても速いです！ これは、MySQL MyISAM テーブルや ISAM テーブルのような テーブル・ロッキング(multiple readers / single writers)をもつ データベースを使う上で、本当に重要なことです。 This will also give better performance with most databases, as the row locking manager in this case will have less to do.
      • もしたくさんの大きなテーブルから統計を収集する必要があるなら、 全テーブルを走査する代わりに、サマリーテーブルを使用します。 Maintaining the summaries should be much faster than trying to do statistics 'live'. It's much faster to regenerate new summary tables from the logs when things change (depending on business decisions) than to have to change the running application!
      • If possible, one should classify reports as 'live' or 'statistical', where data needed for statistical reports are only generated based on summary tables that are generated from the actual data.
      • フィールドにはデフォルト値があるという事を利用して下さい。 値がデフォルトとは違う場合に限り、値を挿入します。 これは MySQL が必要とする分析を少なくし、インサートの速度が向上します。
      • ある場合では、BLOB にデータをパックして保存するのが便利です。 この場合、BLOB に入れた値を パック・アンパック するためのコードを あなたのアプリケーションに組み込まなくてはなりません。 しかしこれは、多くのアクセスを抑制するでしょう。 これは、静的(固定長)テーブル構造に適しないデータを持っている場合に 実用になります。
      • 通常、あなたは全てのデータを冗長の無いように(データベース理論で 第３正規形 , 3rd Normal Form , 3NF と呼ばれる) しようとするかもしれませんが、しかし、よりスピードを求める場合は、 重複やサマリーテーブルの作成をおそれてはいけません。
      • ストアド・プロシージャ や UDF (ユーザー定義関数) はよりパフォーマンスを得る ためにはよい方法かもしれません。 In this case you should, however, always have a way to do this some other (slower) way if you use some database that doesn't support this.
      • You can always gain something by caching queries/answers in your application and trying to do many inserts/updates at the same time. If your database supports lock tables (like MySQL and Oracle), this should help to ensure that the index cache is only flushed once after all updates.
      • データをすぐには書く必要がないとき、INSERT /*! DELAYED */ を使用します。 これは、一回のディスクへの書き込みで、多くのレコードがかかれるので、 速くなります。
      • SELECT がより重要な場合、INSERT /*! LOW_PRIORITY */ を使用します。
      • キューを無視して SELECT を優先的に行いたいときは SELECT /*! HIGH_PRIORITY */ を使用します。 これは、たとえ誰かが書き込みを待っていたとしても、その SELECT は 実行されます。
      • 複数行 INSERT 文の使用。 これは多くのレコードを一つの SQL コマンドで 挿入することが出来ます。 (多くの SQL サーバーがこれをサポートしています)
      • 大きなデータの読み込みには LOAD DATA INFILE を使用します。 This is faster than normal inserts and will be even faster when myisamchk is integrated in mysqld.
      • 一意の値を作るために、 AUTO_INCREMENT を使用します。
      • 動的テーブルフォーマットの使用時には、フラグメンテーションを避けるために、 OPTIMIZE TABLE を時々使用します。 「4.5.1 OPTIMIZE TABLE 構文」節参照.
      • 可能ならば HEAP テーブルをスピードアップのために使用します. 「7 MySQL テーブル型」節参照.
      • 通常の Web サーバーの設定ならば、イメージはファイルに保存すべきです。 データベースには、それらファイルの参照(パスとか)のみを入れます。 この主な理由は、通常の Web サーバーはデータベースよりもコンテンツを よりよくキャッシュしてくれるからです。 それでファイルを使用するなら、 速いシステムをより簡単に得ることができます。
      • 重要でないデータで、よくアクセスされる物は、メモリテーブルにいれます。 (like information about the last shown banner for users that don't have cookies).
      • Columns with identical information in different tables should be declared identical and have identical names. Before Version 3.23 you got slow joins otherwise. 名前は単純にしてください（customer テーブルでは customer_name の かわりに name を使うとか）。 他の SQL サーバーへの移植を考慮するなら、 名前は 18 文字より短くすべきです。
      • もし本当にハイ・スピードが必要なら、SQL サーバーがサポートしている物とは 違う、ローレベルのデータ保存のインターフェースに注目すべきです。 例えば、 MySQL MyISAM を直接アクセスすることは、 SQL インターフェースを介してアクセスするよりも、2〜5倍速くなるでしょう。 これを可能にするには、そのデータは、アプリケーションと同じマシン上になくてはなら ず、通常、一つのプロセスだけでアクセスされるべきです。 (なぜなら、外部ファイルロックは、とても遅いから)。 上の問題は、MySQL サーバー内の MyISAM のローレベルのコマンドの 導入で解決できるでしょう。 (これはよりよいパフォーマンスを得ることの出来る、 簡単な方法の一つです)。 By carefully designing the database interface, it should be quite easy to support this types of optimization.
      • 多くの場合、データベースからデータをアクセスする方が(接続を維持していれば)、 テキストファイルからデータをアクセスするよりも速いです。 なぜなら、 データベースはテキストファイルよりもコンパクトになり（数値データの場合）、 このため、ディスクアクセスが少なくなるからです。 また、行や項目を見つけるために、テキストファイルを解析する必要も省けます。
      • レプリケーションもスピードアップに使用できるでしょう。 「4.10 MySQL のレプリケーション (3.23.15以上)」節参照.
      • DELAY_KEY_WRITE=1 が定義されたテーブルは、インデックスの更新が速くなります。 これはそのインデックス・ファイルが閉じられるまでディスクに記録されないからです。 したがって、なにかが途中で mysqld をキルしてもテーブルが大丈夫なようにす るため、mysqld を起動する前には、myisamchk をそれらのテーブルに 対して実行すべきです。 As the key information can always be generated from the data, you should not lose anything by using DELAY_KEY_WRITE.

      5.3 Locking Issues

      5.3.1 MySQL はどのようにテーブルをロックするか

      付録に、異なるロックする方法に関する議論があります。 「E.4 Locking methods」節参照.

      MySQL の全てのロックはデッドロックフリーです。(except for InnoDB and BDB type tables.) これは、常にクエ リ開始時に一度ロックを必要とする全てを要求し、常に同じ順でテーブルをロッ クすることで管理されます。

      InnoDB type tables automatically acquire their row locks and BDB type tables their page locks during the processing of SQL statements, not at the start of the transaction.

      MySQL が使用する WRITE ロックは次のように働きます:

      • テーブル上にロックがない場合 write ロックを置きます。
      • そうでなければ write ロックキューにロックを置きます。

      MySQL の READ ロックは次のように動きます:

      • テーブル上に write ロックがない場合 read ロックを置きます。
      • そうでなければ read ロックキューにロックを置きます。

      ロックが解放されたとき、最初に write ロックキュー内のスレッドに、その後 read ロックキュー内のスレッドにロックを与えます。

      これは、同じテーブルで多くの更新をする場合、SELECT 構文は update がなくなるまで待たされることを意味します。

      同じテーブルで多くの INSERT と多くの SELECT を行う場合、これを解決 するには、他のテーブルに行を挿入して、たまに、その一時テーブルから全ての レコードをもう一方のテーブルに update します。

      これは次のコードで行えます: 

      mysql> LOCK TABLES real_table WRITE, insert_table WRITE;
mysql> INSERT INTO real_table SELECT * FROM insert_table;
mysql> TRUNCATE TABLE insert_table;
mysql> UNLOCK TABLES;

      特定の場合での検索を優先的に行いたい場合、 LOW_PRIORITY オプションと共に INSERT 、 UPDATE 、 DELETE 構文、または HIGH_PRIORITY オプションと共に SELECT 構文を使用できます。 また、同様の動作を得るために、 --low-priority-updates オプション と共に mysqld を開始することができます。

      SQL_BUFFER_RESULT の使用はさらにテーブル・ロックをより短くするために有効かもしれません。 「6.4.1 SELECT 構文」節参照.

      一つのキューだけを使用するように `mysys/thr_lock.c' 内のロックコードを変更 することもできます。この場合、いくつかのアプリケーションのために、 write ロックは read ロックと同じ優先順位にします。

      5.3.2 テーブル・ロッキングの問題

      MySQL のテーブル・ロッキングのコードはデッドロック・フリーです。

      MySQL はとても速いロックスピードを得るために、 (レコードのロックやフィールドのロックの代わりに) テーブルのロックを使用します。 (except InnoDB and BDB tables) 大きなテーブルには、 テーブルのロックはレコードのロックよりはるかに良いですが、 いくつかの落とし穴があります。

      BDB と InnoDB のテーブルでは、 LOCK TABLES を使用して 明示的にテーブルをロックするか、 ALTER TABLE のようなテーブル中のすべて のレコードを修正するコマンドを実行した場合にのみ、MySQLはテーブル・ロッキングを使用 します。これらのテーブル・タイプについては、 LOCK TABLES を全く使用 しないことを推奨します。 because InnoDB uses automatic row level locking and BDB uses page level locking to ensure transaction isolation.

      MySQL バージョン 3.23.7 以上では、 あるスレッドが MyISAM テーブルを読んでいる最中に、 同じテーブルにレコードを挿入する事ができます。 現在、これは挿入が行われる時に、テーブルのレコードを削除した後にホールがない場合にのみ 動作することに注意してください。すべてのホールが新しいデータで満たされた時に、 自動的に同時挿入が再び可能になります。

      テーブルのロックはたくさんのスレッドが同時にあるテーブルから読み出すのを可能にし ますが、もしあるスレッドがあるテーブルに対し書込み要求を出す場合、 それはまず最初に排他的なアクセスを得なければなりません. その更新の間、更新が完了するまで、この特定のテーブルにアクセスしようとする 他の全てのスレッドが待たされることになります。

      通常データベースの更新は SELECT よりも重要とされるため、 テーブルを更新する全てのスレッドが、テーブルから情報を検索するスレッドよりも 高い優先順位を持ちます。 これは ある特定のテーブルに対して、多くの重いクエリが発 行された場合に、 更新が不完全に終わらないことを確実にするためです。 (これは、 LOW_PRIORITY と共に更新を行うステートメントを用いるか、 HIGH_PRIORITY と共に SELECT ステートメントを用いることにより 変更が可能です。)

      MySQL バージョン 3.23.7 から、max_write_lock_count 変数が使用で きます。 これは、一つのテーブルに対して、指定された回数だけ INSERT が行われた後に、 SELECT を発行するようにします。

      テーブルロッキングは以下の場合にはあまり良くありません：

      • あるクライアントが実行に長い時間のかかる SELECT を発行。
      • その後に、他のクライアントが、使用されているテーブルに対し UPDATE を発行； このクライアントは先の SELECT が完了するまで待ちます
      • さらに他のクライアントが同じテーブルに対して SELECT 構文を発行； UPDATE は SELECT よりも高い優先度を持つので、 この SELECT は先の UPDATE が完了するまで待ちます。 これは一番最初の SELECT が 終了するまで待たされます！
      • スレッドが full disk のような待機状態になっている場合、 問題のテーブルにアクセスを行おうとした全てのスレッドもまた、 より多くのディスク・スペースが利用可能になるまで待機状態に入ります。

      この問題のいくつかの可能な解決は以下の通りです：

      • SELECT 構文を速く実行できるように試みます； これを行うにあたり、 いくつかのサマリーテーブルを作成しなければならないかもしれません.
      • mysqld を --low-priority-updates オプションで起動。 これは全てのあるテーブルを更新する構文に対して、 SELECT 構文よりも 低い優先度を与えます。 この場合、前述のシナリオ中の最後の SELECT 構文は INSERT 構文が完了する前に実行されます。
      • LOW_PRIORITY 属性指定を用いて、 INSERT,UPDATE,DELETE 構文に低い優先度を与えることも出来ます。
      • ある程度の数の WRITE ロックの後に READ ロックを与えるために、 max_write_lock_count を低い値にして mysqld を開始します。
      • SQL コマンドの SET LOW_PRIORITY_UPDATES=1 (ver. 4.0.3 未満では SET SQL_LOW_PRIORITY_UPDATES=1 ) を使用して、 ある特定のスレッドからの全ての更新を、低い優先度に指定する事ができます。 「5.5.6 SET 構文」節参照.
      • HIGH_PRIORITY 属性を用いて、特定の SELECT がとても重要であると 指定することが可能です。. 「6.4.1 SELECT 構文」節参照.
      • もし INSERT と SELECT をあわせて使用した場合に問題が起きた場合、 新しい MyISAM テーブルに切り替えます。 これは SELECT と INSERT を同時に行えます。
      • もし INSERT と SELECT 構文を主に混在させるのなら、 INSERT の DELAYED 属性指定はこの問題を解決させるでしょう。 「6.4.3 INSERT 構文」節参照.
      • もし SELECT と DELETE で問題があるなら、 DELETE の LIMIT オプションが助けになるでしょう。 「6.4.6 DELETE 構文」節参照.

      5.4 Optimizing Database Structure

      5.4.1 Design Choices

      MySQL は、レコードのデータとインデックスを別のファイルに保存します。 他の多くの(ほとんど全て)データベースでは、同じファイルにデータとインデックスを 混在させて保存します。 我々は、最近のシステムには、MySQL の選択の方が 良いと信じています。

      Another way to store the row data is to keep the information for each column in a separate area (examples are SDBM and Focus). This will cause a performance hit for every query that accesses more than one column. Because this degenerates so quickly when more than one column is accessed, we believe that this model is not good for general purpose databases.

      The more common case is that the index and data are stored together (like in Oracle/Sybase et al). In this case you will find the row information at the leaf page of the index. The good thing with this layout is that it, in many cases, depending on how well the index is cached, saves a disk read. The bad things with this layout are:

      • Table scanning is much slower because you have to read through the indexes to get at the data.
      • You can't use only the index table to retrieve data for a query.
      • You lose a lot of space, as you must duplicate indexes from the nodes (as you can't store the row in the nodes).
      • Deletes will degenerate the table over time (as indexes in nodes are usually not updated on delete).
      • It's harder to cache ONLY the index data.

      5.4.2 可能な限りデータを小さくする

      One of the most basic optimization is to get your data (and indexes) to take as little space on the disk (and in memory) as possible. This can give huge improvements because disk reads are faster and normally less main memory will be used. Indexing also takes less resources if done on smaller columns.

      MySQL supports a lot of different table types and row formats. Choosing the right table format may give you a big performance gain. 「7 MySQL テーブル型」節参照.

      以下に挙げるテクニックを使用すれば、テーブルでのパフォーマンスの向上、 保存領域の縮小化が可能でしょう：

      • 可能ならば、一番小さな型を使用します。 MySQL は ディスクとメモリーを節約する多くの型を持っています。
      • より小さな整数型を可能ならば使用します。 例えば、 MEDIUMINT は INT より良いでしょう。
      • 可能ならフィールドを NOT NULL に定義してください。これは全てをより速くし、 各フィールド毎に1ビットを節約します。 Note that if you really need NULL in your application you should definitely use it. Just avoid having it on all columns by default.
      • 可変長のフィールド (VARCHAR, TEXT, BLOB) を持たない場合は、 固定サイズレコード形式が使用されます。 これはかなり速いです。しかしあいにくいくらかの領域を浪費します。 「7.1.2 MyISAM Table Formats」節参照.
      • それぞれのテーブルは可能な限り短いプライマリ・インデックスを持つべきです。 これは１レコードを一意にし、効率的にします。
      • それぞれのテーブルについて、どのテーブルの形式を使用するかを 決めます。 「7 MySQL テーブル型」節参照.
      • 本当に必要な物にだけインデックスを作成します。 インデックスは検索には良いですが、より速く保存したい場合には良くありません。 もしテーブルをフィールドの組み合わせでサーチすることがほとんどであれば、 それらにインデックスを作成します。 最初のインデックスの部分は、もっとも 使用されるフィールドにすべきです。 If you are ALWAYS using many columns, you should use the column with more duplicates first to get better compression of the index.
      • もしインデックスが頭からの何文字かで一意性を持っているなら、この部分にだけ インデックスを張る方が良いでしょう。 MySQL は文字列フィールドの 一部分に対してのインデックスをサポートします。 短いインデックスは、ディスクスペースを節約するだけでなく、 インデックスのキャッシュに収まりやすくなることにより、ディスク・シークも少 なくなるので、速くなります。 「5.5.2 サーバーパラメーターのチューニング」節参照.
      • いくつかの状況下で、とてもよく走査されるテーブルを２つに分割することは、 利益になることがあります。 This is especially true if it is a dynamic format table and it is possible to use a smaller static format table that can be used to find the relevant rows when scanning the table.

      5.4.3 MySQL はどのようにインデックスを使用するか？

      Indexes are used to find rows with a specific value of one column fast. インデックスがない場合、MySQL は、そのレコードが見つかるまで、 最初のレコードからテーブルをなめていきます。 大きなテーブルでは多くの 手間がかかります。 もし問い合わせの中にインデックスを持ったフィールドが ある場合、MySQL は全てのデータをみることなく、データの途中の位置を速く 得ることができます。 もしあるテーブルが1000レコード持っていたとすると、 順番に頭からなめていくことに比べて、これは少なくとも100倍速いことに なります。 Note that if you need to access almost all 1000 rows it is faster to read sequentially because we then avoid disk seeks.

      全ての MySQL インデックス, PRIMARY, UNIQUE そして INDEX() は B tree に格納されます。 文字列は自動的に始めと終りの空白が圧縮されます。 「6.5.7 CREATE INDEX 構文」節参照.

      Indexes are used to:

      • WHERE節にマッチした行の素早い検索
      • join を実行したときの他のテーブルからの行の検索
      • Find the MAX() or MIN() value for a specific indexed column. This is optimized by a preprocessor that checks if you are using WHERE key_part_# = constant on all key parts < N. In this case MySQL will do a single key lookup and replace the MIN() expression with a constant. If all expressions are replaced with constants, the query will return at once: 
        SELECT MIN(key_part2),MAX(key_part2) FROM table_name where key_part1=10
      • テーブルをソートかグループ化する場合で、ソート(グループ化)が一番左(接頭部)の キーを使用して行われる場合(例えば ORDER BY key_part_1,key_part_2 )。 もし DESC 指定があれば、全てのキーは逆順に読まれます。 「5.2.7 How MySQL Optimises ORDER BY」節参照.
      • データファイルを参照することなく値を検索する場合。 もし使用する全てのフィールドが数値でかつ、一番左から(接頭部から)キーを形成する場 合、 値はインデックスツリーから検索され、これはとても速くなります。 
        SELECT key_part3 FROM table_name WHERE key_part1=1

      以下のような SELECT 文を発行したとします： 

      mysql> SELECT * FROM tbl_name WHERE col1=val1 AND col2=val2;

      もし col1 と col2 に複数フィールドインデックスが定義されている場合、 すぐに思ったとおりの結果が得られます。 If separate single-column indexes exist on col1 and col2, the optimizer tries to find the most restrictive index by deciding which index will find fewer rows and using that index to fetch the rows.

      もしテーブルが複数フィールドインデックスを持つなら、インデックスの接頭部一番左の 部分がレコードを見つけるための最適化に使用されます。例えば、3つのフィールド (col1,col2,col3) に対して一つのインデックスを持っていたとします。 すると、これは (col1), (col1,col2) , (col1,col2,col3) でインデックスがサーチされます。

      もし一番左に指定しているフィールドがインデックスを作成していないなら、 MySQL は部分的なインデックスを使用しません。

      以下のような SELECT 文を発行したとします： 

      mysql> SELECT * FROM tbl_name WHERE col1=val1;
mysql> SELECT * FROM tbl_name WHERE col2=val2;
mysql> SELECT * FROM tbl_name WHERE col2=val2 AND col3=val3;

      もしインデックスが (col1,col2,col3) にあるならば、 上に示した最初のクエリだけがインデックスを使用します。二番目三番目のクエリは インデックスを持つフィールドを発動しますが、 (col2) と (col2,col3) は、(col1,col2,col3) の 接頭部一番左に指定されていません。

      MySQL は、もし LIKE がワイルドカードから始まっていなくて、 ある種固定された文字で始まっているなら、 LIKE の評価にインデックスを使用します。 例えば、以下の SELECT 文はインデックスを使用します: 

      mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Patrick%";
mysql> SELECT * FROM tbl_name WHERE key_col LIKE "Pat%_ck%";

      一つ目の文は、"Patrick" <= key_col < "Patricl" となるレコードだけ、考慮さ れます。 二つ目の文は、"Pat" <= key_col < "Pau" となるレコードだけ、考慮されます。

      以下の SELECT 文はインデックスを使用しません: 

      mysql> SELECT * FROM tbl_name WHERE key_col LIKE "%Patrick%";
mysql> SELECT * FROM tbl_name WHERE key_col LIKE other_col;

      最初の文は、LIKE がワイルドカード文字で始まっています。 二つ目の文は、LIKE が定数ではありません。

      MySQL 4.0 does another optimisation on LIKE. If you use ... LIKE "%string%" and string is longer than 3 characters, MySQL will use the Turbo Boyer-Moore algorithm to initialise the pattern for the string and then use this pattern to perform the search quicker.

      Searching using column_name IS NULL will use indexes if column_name is an index.

      MySQL は通常、一番少ないレコード数を見つけるインデックスを使用します。 インデックスは次に示す演算子を用いて比較できるフィールドに対して使用されます： =, >, >=, <, <=, BETWEEN そして 'something%' の様に頭にワイルドカードがない LIKE。

      WHERE 節内の全ての AND にかからないインデックスは、 全くクエリの最適化に使用されません。 In other words: To be able to use an index, a prefix of the index must be used in every AND group.

      以下の WHERE 節はインデックスを使用します： 

      ... WHERE index_part1=1 AND index_part2=2 AND other_column=3
... WHERE index=1 OR A=10 AND index=2      /* index = 1 OR index = 2 */
... WHERE index_part1='hello' AND index_part_3=5
          /* optimized like "index_part1='hello'" */
... WHERE index1=1 and index2=2 or index1=3 and index3=3;
          /* Can use index on index1 but not on index2 or index 3 */

      以下の WHERE 節はインデックスを使用しません： 

      ... WHERE index_part2=1 AND index_part3=2  /* index_part_1 is not used */
... WHERE index=1 OR A=10                  /* Index is not used in
                                                        both AND parts */
... WHERE index_part1=1 OR index_part2=10  /* No index spans all rows  */

      Note that in some cases MySQL will not use an index, even if one would be available. Some of the cases where this happens are:

      • If the use of the index would require MySQL to access more than 30% of the rows in the table. (In this case a table scan is probably much faster, as this will require us to do much fewer seeks.) Note that if such a query uses LIMIT to only retrieve part of the rows, MySQL will use an index anyway, as it can much more quickly find the few rows to return in the result.

      5.4.4 Column Indexes

      MySQL の全てのフィールドはインデックスを持つことができます。 適切なフィールドでのインデックスの使用は、SELECT の 性能を向上する最良の方法です。

      キーの最大数と最大インデックス長は storage engine 毎に定義されます。 「7 MySQL テーブル型」節参照。すべてのテーブルハンドラで少なくとも 16 個のキーと少な くとも合計 256 バイトのインデックス長を持つことができます。

      CHAR と VARCHAR フィールドには接頭部にインデックスを持つことが できます。フィールド全体をインデックス化するより、 これははるかに早く、少ないディスク容量でできます。

      CREATE TABLE 構文でフィールドにインデックスを作るには、 以下のようにします： 

      KEY index_name (col_name(length))

      以下の例は name フィールドの最初の10文字にインデックスを創り出します: 

      mysql> CREATE TABLE test (
    ->        name CHAR(200) NOT NULL,
    ->        KEY index_name (name(10)));

      BLOB と TEXT フィールドでは、そのフィールドの頭の部分に インデックスを張らなくてはなりません。 フィールドの全体にインデックスは張れません。

      MySQL バージョン 3.23.23 以降では、特殊な FULLTEXT イン デックスを生成することもできます。これは全文検索に使用されます。 MyISAM テーブル型だけが FULLTEXT インデックスをサポートしま す。これは CHAR, VARCHAR と TEXT フィールドだけに生成できます。イ ンデックスは常にフィールド全体に対して行なわれ、部分インデックスはサポート されません。詳細は 「6.8 MySQL Full-text Search」節.

      5.4.5 Multiple-Column Indexes

      MySQL は異なるフィールドのセットに一つのインデックスを持つことができます。 インデックスは最大15個のコラムまで許されます。 (CHAR と VARCHAR フィールドの接頭部をインデックスとして使用できます)

      複数フィールドインデックスは、 ソートされた配列(インデックス化されたフィールドの値が結合されている配列) を扱うことができます。

      インデックス化されたコラムに対して、既知の値を WHERE 節で指定した時、 たとえ他のフィールドの値を指定しなくとも、 MySQL は複数フィールドインデックスを使用します。

      以下のテーブルがあると仮定してください： 

      mysql> CREATE TABLE test (
    ->       id INT NOT NULL,
    ->       last_name CHAR(30) NOT NULL,
    ->       first_name CHAR(30) NOT NULL,
    ->       PRIMARY KEY (id),
    ->       INDEX name (last_name,first_name));

      name インデックスは、last_name と first_name にまたがるイン デックスです。 このインデックスは、last_name に対するクエリや、 name インデックスは以下のクエリで使われます： 

      mysql> SELECT * FROM test WHERE last_name="Widenius";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND first_name="Michael";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND (first_name="Michael" OR first_name="Monty");

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    AND first_name >="M" AND first_name < "N";

      しかし name インデックスは以下のクエリでは使用されません: 

      mysql> SELECT * FROM test WHERE first_name="Michael";

mysql> SELECT * FROM test WHERE last_name="Widenius"
    ->                    OR first_name="Michael";

      MySQL がクエリの性能を上げるためにどうインデックスを使用しているか、 より詳しい情報はこちら： 「5.4.3 MySQL はどのようにインデックスを使用するか？」節.

      5.4.6 何故そんなに多くのテーブルをオープンするのか？

      mysqladmin status を実行すると、次のようなものが得られます: 

      Uptime: 426 Running threads: 1 Questions: 11082 Reloads: 1 Open tables: 12

      確かにたった6個しかテーブルがないのに、このような結果が出るので少々戸惑われるか もしれません。

      MySQL はマルチスレッドなので、同じテーブルで一度に多くのクエリを持て ます。 同じファイル上では2つスレッドはそれぞれ別の異なる状態を持つという 問題を最小化するため、テーブルは同時に動作する各スレッドにより個々に オープンされます。 これは少しメモリを食いますが、パフォーマンスは良くなります。 ISAM と MyISAM テーブルでは、データファイルのために 一つのファイル記述子を使用します。 インデックスファイル記述子は全てのスレッド間で共有されます。

      You can read more about this topic in the next section. 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節参照.

      5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？

      table_cache , max_connections , max_tmp_tables は サーバーが開いた状態にしておく事が出来るファイルの最大数に影響します。 もしこれらの変数のうちの一つ、あるいは複数を増加させるなら、 あなたのオペレーティング・システムの、1 プロセスあたりに開かれる ファイル・デスクリプタ の最大値を増やすことになるかもしれません。 多くのシステムではこの制限を増やすことが可能です。 これをどうやって行うかは、あなたの使用している OS のドキュメントを見てください。 制限値の変更方法は、システムによってまちまちだからです。

      table_cache は max_connections に関連します。 例えば 200 のコネクションを同時に開けるなら、少なくとも 200 * n の テーブル・キャッシュが必要です。 ここで n は join におけるテーブルの 最大数です。 You also need to reserve some extra file descriptors for temporary tables and files.

      Make sure that your operating system can handle the number of open file descriptors implied by the table_cache setting. If table_cache is set too high, MySQL may run out of file descriptors and refuse connections, fail to perform queries, and be very unreliable. You also have to take into account that the MyISAM storage engine needs two file descriptors for each unique open table. You can in increase the number of file descriptors available for MySQL with the --open-files-limit=# startup option. 「A.2.16 File Not Found」節参照.

      オープンテーブルのキャッシュは最大で table_cache まで大きくなります(デ フォルトは 64, mysqld のオプション -O table_cache=# で変更可能)。 Note that in MySQL may temporarly open even more tables to be able to execute queries.

      A not used table is closed and removed from the table cache under the following circumstances:

      • When the cache is full and a thread tries to open a table that is not in the cache.
      • When the cache contains more than table_cache entries and a thread is no longer using a table.
      • When someone executes mysqladmin refresh or mysqladmin flush-tables.
      • When someone executes a FLUSH TABLES statement.

      キャッシュがいっぱいになった場合、サーバーは以下の処置を取って キャッシュを使用できるように配置します：

      • 現在使われていないテーブルが解放されます。もっとも使用されていないテーブルからか ら順に。
      • もしキャッシュが一杯でテーブルを解放することが出来ず、さらに新しいテーブルの オープン要求がある場合、キャッシュは一時的な拡張を必要とします。
      • もしそのキャッシュが一時拡張に配置されていて、かつ、テーブルが使用状態から 未使用状態に移行した場合、そのテーブルは閉じられ、キャッシュから解放されます。

      テーブルは各同時アクセスに (再び) オープンされます。これは、同じテーブルで2つの スレッドが実行されている場合、または同じクエリで(AS で)テーブルを2回 アクセスする場合、テーブルは2回オープンする必要があることを意味します。 最初のテーブルのオープンは2つのファイル記述子を使用し、続くテーブルの各使用は 1つだけのファイル記述子を使用します。

      If you are opening a table with the HANDLER table_name OPEN statement, a dedicated table object is allocated for the thread. This table object is not shared by other threads an will not be closed until the thread calls HANDLER table_name CLOSE or the thread dies. 「6.4.2 HANDLER Syntax」節参照. When this happens, the table is put back in the table cache (if it isn't full).

      You can check if your table cache is too small by checking the mysqld variable Opened_tables. If this is quite big, even if you haven't done a lot of FLUSH TABLES, you should increase your table cache. 「4.5.6.3 SHOW STATUS」節参照.

      5.4.8 Drawbacks to Creating Large Numbers of Tables in the Same Database

      もしたくさんのファイルが一つのディレクトリにある場合、オープン、クローズ、 create 操作は遅くなるでしょう。 もし SELECT 文を多くのテーブルに対し 実行した場合、テーブルキャッシュが一杯ならば、このオーバーヘッドは多くなるでしょ う。 なぜなら、それぞれのテーブルにつきオープンし、クローズしなくてはならないからです。 このオーバーヘッドを緩和するには、テーブルキャッシュを大きくします。

      5.5 Optimizing the MySQL Server

      5.5.1 システム、コンパイル時、スタートパラメターのチューニング

      We start with the system level things since some of these decisions have to be made very early. In other cases a fast look at this part may suffice because it not that important for the big gains. However, it is always nice to have a feeling about how much one could gain by changing things at this level.

      使うべき OS はとても重要です！ 複数の CPU を持つマシンでは、 Solaris (なぜなら、Solaris のスレッドはとても素晴らしく動作するから)、 あるいは、Linux ( kernel 2.2 は良い SMP をサポートしているから) を 使用すべきです。 32bit マシンの Linux では、2G bytes のファイルサイズの 制限があります。 これは新しいファイルシステム (XFS/ReiserFS) のリリース時に なくなって欲しいものです。 If you have a desperate need for files bigger than 2G on Linux-intel 32 bit, you should get the LFS patch for the ext2 file system.

      Because we have not run MySQL in production on that many platforms, we advice you to test your intended platform before choosing it, if possible.

      Other tips:

      • 充分 RAM があるならば、全ての swap を外してもよいでしょう。 いくつかのシステムでは、たとえメモリーが空いていても、 swap を使用する場合があります。
      • 外部のロックを避けるため、--skip-external-locking (ver.4.0.3未満では --skip-locking) MySQL オプション を使用します。 Note that this will not impact MySQL's functionality as long as you only run one server. Just remember to take down the server (or lock relevant parts) before you run myisamchk. On some system this switch is mandatory because the external locking does not work in any case. MIT-pthread でコンパイルする時は --skip-external-locking (ver.4.0.3未満では --skip-locking) がデフォルトです。 これは全てのプラットフォームで MIT-pthread が flock() を完全にサポートし ていないためです。 It's also on default for Linux as Linux file locking are not yet safe. --skip-external-locking (ver.4.0.3未満では --skip-locking) が使用できないただ一つの状態は、 もしあなたが複数の MySQL サーバー (クライアントではない) を 同じデータに対して走らせている場合です。 You can still use LOCK TABLES/UNLOCK TABLES even if you are using --skip-external-locking (ver.4.0.3未満では --skip-locking)

      5.5.2 サーバーパラメーターのチューニング

      mysqld サーバーが使用している現在のバッファサイズを次で得ることができます: 

      shell> mysqld --help

      この結果、全ての mysqld オプションと次のようなコンフィグ可能変数のリスト を得られます。出力結果にはデフォルト値が含まれ、以下のように表示されます: 

      Possible variables for option --set-variable (-O) are:
back_log                 current value: 5
bdb_cache_size           current value: 1048540
binlog_cache_size        current value: 32768
connect_timeout          current value: 5
delayed_insert_timeout   current value: 300
delayed_insert_limit     current value: 100
delayed_queue_size       current value: 1000
flush_time               current value: 0
interactive_timeout      current value: 28800
join_buffer_size         current value: 131072
key_buffer_size          current value: 1048540
lower_case_table_names   current value: 0
long_query_time          current value: 10
max_allowed_packet       current value: 1048576
max_binlog_cache_size    current value: 4294967295
max_connections          current value: 100
max_connect_errors       current value: 10
max_delayed_threads      current value: 20
max_heap_table_size      current value: 16777216
max_join_size            current value: 4294967295
max_sort_length          current value: 1024
max_tmp_tables           current value: 32
max_write_lock_count     current value: 4294967295
myisam_sort_buffer_size  current value: 8388608
net_buffer_length        current value: 16384
net_retry_count          current value: 10
net_read_timeout         current value: 30
net_write_timeout        current value: 60
read_buffer_size         current value: 131072
record_rnd_buffer_size   current value: 131072
slow_launch_time         current value: 2
sort_buffer              current value: 2097116
table_cache              current value: 64
thread_concurrency       current value: 10
tmp_table_size           current value: 1048576
thread_stack             current value: 131072
wait_timeout             current value: 28800

      Please note that --set-variable is deprecated since MySQL 4.0, just use --var=option on its own.

      もし mysqld サーバーを走らせているなら、以下のコマンドでも変数の値を見る ことができます: 

      shell> mysqladmin variables

      You can find a full description for all variables in the SHOW VARIABLES section in this manual. 「4.5.6.4 SHOW VARIABLES」節参照.

      You can also see some statistics from a running server by issuing the command SHOW STATUS. 「4.5.6.3 SHOW STATUS」節参照.

      MySQL はとてもスケーラブルなアルゴリズムを使用します。そのため 通常はとても少ないメモリで動作します。しかし MySQL に多くのメモリを 与えれば、より良い性能を得ることができます。

      When tuning a MySQL server, the two most important variables to use are key_buffer_size and table_cache. You should first feel confident that you have these right before trying to change any of the other variables.

      多くのメモリ(>=256M)と多くのテーブルを持っていて、適度のクライアント数で最大性能 を得たい場合、次のようなものを使用します: 

      shell> safe_mysqld -O key_buffer=64M -O table_cache=256 \
           -O sort_buffer=4M -O read_buffer_size=1M &

      If you have only 128M and only a few tables, but you still do a lot of sorting, you can use something like: 

      shell> safe_mysqld -O key_buffer=16M -O sort_buffer=1M

      多くの接続で少ないメモリしかない場合、次のようなものを使用します 

      shell> safe_mysqld -O key_buffer=512k -O sort_buffer=100k \
           -O read_buffer_size=100k &

      or even: 

      shell> safe_mysqld -O key_buffer=512k -O sort_buffer=16k \
           -O table_cache=32 -O read_buffer_size=8k -O net_buffer_length=1K &

      If you are doing a GROUP BY or ORDER BY on files that are much bigger than your available memory you should increase the value of record_rnd_buffer to speed up the reading of rows after the sorting is done.

      When you have installed MySQL, the `support-files' directory will contain some different `my.cnf' example files, `my-huge.cnf', `my-large.cnf', `my-medium.cnf', and `my-small.cnf', you can use as a base to optimize your system.

      もしとても多くの接続があり、mysqld が各接続に対して少ないメモリーで 動作するように設定されていれば、スワップの読み書きによるパフォーマンスの低下がお きます。 もちろん十分なメモリーがあれば、全ての接続にたいして mysqld のパフォーマ ンス良くなります。

      mysqld へのオプションを変更する場合、そのサーバのインスタンスにだけに 有効であることに注意して下さい。

      パラメータ変更の効果を見るには、このようにします: 

      shell> mysqld -O key_buffer=32m --help

      --help オプションは最後につけてください。 その他のオプションを --help の後につけると、そのオプションは反映されません。

      5.5.3 MySQL の速度に影響するコンパイルとリンク方法

      次のテストの多くは Linux 上で MySQL ベンチマークで行われました。 しかし、これらは他の OS についてもいくつかの指標を与えます。

      -static でのリンク時に最速の実行形式を得ます。

      Linux では、pgcc と -O3 でコンパイルした時に最速のコードを得られます。 このオプションで `sql_yacc.cc' をコンパイルすると、gcc/pgcc は 全ての関数をインラインにするために多くのメモリを必要とするので、200M のメモリが 必要です。 libstdc++ ライブラリの増加を避けるためには、 MySQL の configure 時に CXX=gcc も設定すべきです。 Note that with some versions of pgcc, the resulting code will only run on true Pentium processors, even if you use the compiler option that you want the resulting code to be working on all x586 type processors (like AMD).

      より良いコンパイラー、そしてコンパイラーのオプションは、10-30% の 速度の向上をもたらします。 これはあなた自身が MySQL をコンパイルする 時に重要なことです！

      我々は Cygnus CodeFusion と Fujitsu コンパイラーでもテストしましたが、 MySQL を最適化オプションでコンパイルするには、 どちらもまだ完全なバグ・フリーではありませんでした。

      When you compile MySQL you should only include support for the character sets that you are going to use. (Option --with-charset=xxx). The standard MySQL binary distributions are compiled with support for all character sets.

      Here is a list of some measurements that we have done:

      • pgcc を使用して -O6 で全てをコンパイルすると、 gcc 2.95.2 より、mysqld サーバーは 1% 速くなります。
      • Linux 上では、動的リンク(-static) 無し)の場合、結果は 13% 遅くなります。 Note that you still can use a dynamic linked MySQL library. It is only the server that is critical for performance.
      • If you strip your mysqld binary with strip libexec/mysqld, the resulting binary can be up to 4% faster.
      • (localhost への接続に) Unix ソケットの代わりに TCP/IP を使用すると、結果は 7.5% 遅くなります。 (localhost へ接続する場合、MySQL はデフォルトではソケット を使用します)。
      • If you connect using TCP/IP from another computer over a 100M Ethernet, things will be 8-11% slower.
      • When running our benchmark tests using secure connections (all data encrypted with internal SSL support) things were 55% slower.
      • --with-debug=full でコンパイルすると、ほとんどのクエリで 20% 遅くな りますが、いくつかのクエリは実質的にはもっと長くなります(MySQL ベ ンチマークでは 35% 遅くなりました)。 --with-debug を使用すると、15% だけ遅くなります。 By starting a mysqld version compiled with --with-debug=full with --skip-safemalloc the end result should be close to when configuring with --with-debug.
      • On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster than gcc 3.2
      • On a Sun UltraSPARC-IIe, Forte 5.0 is 4% faster in 32 bit mode than in 64 bit mode.
      • UltraSPARC で gcc 2.95.2 でオプション -mcpu=v8 -Wa,-xarch=v8plusa をつけてコンパイルすると 4% 良い性能が得られます。
      • シングルプロセッサの Solaris 2.5.1 では、MIT-pthreads は Solaris ネイティブスレ ッドより 8-12% 遅くなります。 With more load/CPUs the difference should get bigger.
      • --log-bin での実行は mysqld を 1% 遅くします。
      • Compiling on Linux-x86 using gcc without frame pointers -fomit-frame-pointer or -fomit-frame-pointer -ffixed-ebp makes mysqld 1-4% faster.

      The MySQL-Linux distribution provided by MySQL AB used to be compiled with pgcc, but we had to go back to regular gcc because of a bug in pgcc that would generate the code that does not run on AMD. We will continue using gcc until that bug is resolved. In the meantime, if you have a non-AMD machine, you can get a faster binary by compiling with pgcc. The standard MySQL Linux binary is linked statically to get it faster and more portable.

      5.5.4 MySQL はどのようにメモリを使用するのか？

      以下に mysqld サーバーがどのようにメモリーを使用するか、いくつか示します。 サーバーに与える変数名は、サーバーのメモリーの使用方に関連した名前となっています:

      • キーバッファ (変数 key_buffer) は全てのスレッドで共有され、 残りは必要時に割り当てられます。 「5.5.2 サーバーパラメーターのチューニング」節参照.
      • 各接続はいくつかのスレッド空間を使用します； スタック (64K, 変数 thread_stack), 接続バッファ(variable net_buffer_length), 結果バッファ(variable net_buffer_length)。接続バッファと結果バッファは必要となった時、 動的に最大 max_allowed_packet まで増えます。 クエリが走っている時、そのクエリの文字のコピーが割り当てられます。
      • 全てのスレッドは同じベースメモリを共有します。
      • 圧縮された ISAM / MyISAM だけが、memory mapped されます。 これは 4GB の 32bit メモリ空間は多くの大きなテーブルを扱うには小さいためです。 64bit アドレス空間を持つシステムがより普及すれば、我々は mmemory mapping を通常 にサポートします。
      • テーブルを越えて順次スキャンを行なう各要求は、読み込みバッファを割り当てます (変数 record_buffer)
      • When reading rows in 'random' order (for example after a sort) a random-read buffer is allocated to avoid disk seeks. (variable record_rnd_buffer).
      • 全ての結合は1パスで行なわれ、多くの結合は一時テーブルを使用せずに行なわ れます。多くの一時テーブルはメモリベース(HEAP)のテーブルです。大きなレコー ドサイズ (= 全フィールド長の合計) を持つ一時テーブルまたは、BLOB を含む テーブルはディスク上に置かれます。 MySQL バージョン 3.23.2 以前での問題は、HEAP テーブルが tmp_table_size のサイズを越えると、エラー The table tbl_name is full が出ることです。将来我々は、必要時にメモリ (HEAP) テーブルをディスクベー ス (MyISAM) テーブルに自動的に変更することにより、これを修正します。この 問題を回避するため、mysqld への tmp_table_size オプションま たはクライアント側で SQL オプション BIG_TABLES (ver.4.0.3未満では SQL_BIG_TABLES) で増加できます。 「5.5.6 SET 構文」節参照. MySQL バージョン 3.20 では、一時テーブルの最大サイズは recordbuffer*16 でした。そのため、このバージョンを使用していると、 recordbuffer を追加する必要があります。 mysqld を --big-tables で 開始することで、常に一時テーブルをディスク上に格納できます。しかしこれは 多くの複雑なクエリの速度に影響します。
      • ほとんどのリクエストは、0-2個の一時ファイルとわずかなソートバッファへの割り当て を行います。 「A.4.4 MySQL が一時ファイルを格納する場所」節参照.
      • パースと演算時に使用されるほとんど全てのメモリはローカルメモリストア内で行 なわれます。小さな項目に必要とされるメモリオーバーヘッドはなく、通常の遅 いメモリ割り当て/解放が回避されます。メモリは予期しない大きな文字列にだ け割り当てられます(これは malloc() と free() で行なわれます)。
      • 各インデックスファイルは一度オープンされ、データファイルは各同時実行 スレッド毎に一度オープンされます。各同時スレッドには、テーブル構造、 各フィールドの構造そして 3 * n のサイズのバッファが割り当てられます。 ( n は BLOB 型のフィールドの長さを含めない、一レコードの最大長です ) BLOB は 5 から 8 バイト + BLOB データの長さを使用します。 The ISAM/MyISAM table handlers will use one extra row buffer for internal usage.
      • BLOB を持つ各テーブルでは、より大きな BLOB の読み込みでバッファ は動的に拡大されます。テーブルのスキャンをする場合、割り当てられたバッファは最 も大きい BLOB と同じ大きさになります。
      • 全ての使用されているテーブルの storage engine はキャッシュ内に保存され、 FIFO として管理されます。 通常、キャッシュは 64 個のテーブルです。テーブルが 2 つの実行しているス レッドで同時に使用される場合、キャッシュ内にテーブルの 2 つのエントリが あります。 「5.4.7 MySQL はどのようにテーブルのオープン & クローズを行なうか？」節参照.
      • mysqladmin flush-tables は使用されていない全てのテーブルをクローズし、 使用されている全てのテーブルを、実行中スレッドが終った時にクローズするよ うにマークします。これは多くの使用メモリを解放するのに有効です。全てのロ グファイルもクローズと再オープンされます。

      mysqld 実行時、ps や他のプログラムは、それが多くのメモリ を使用していると報告するでしょう。これは異なったメモリアドレス上のスレッ ドスタックによって発生します。例えば、Solaris ps はスタック間の未使用メ モリを使用メモリとして計算します。'swap -s' で有効なスワップをチェックす ることでこれを確かめられます。我々は市販のメモリリーク検出プログラムで mysqld をテストしました。そのため、メモリリークは全くありません。

      5.5.5 How MySQL uses DNS

      When a new thread connects to mysqld, mysqld will span a new thread to handle the request. This thread will first check if the hostname is in the hostname cache. If not the thread will call gethostbyaddr_r() and gethostbyname_r() to resolve the hostname.

      If the operating system doesn't support the above thread-safe calls, the thread will lock a mutex and call gethostbyaddr() and gethostbyname() instead. Note that in this case no other thread can resolve other hostnames that is not in the hostname cache until the first thread is ready.

      You can disable DNS host lookup by starting mysqld with --skip-name-resolve. In this case you can however only use IP names in the MySQL privilege tables.

      If you have a very slow DNS and many hosts, you can get more performance by either disabling DNS lookop with --skip-name-resolve or by increasing the HOST_CACHE_SIZE define (default: 128) and recompile mysqld.

      You can disable the hostname cache with --skip-host-cache. You can clear the hostname cache with FLUSH HOSTS or mysqladmin flush-hosts.

      If you don't want to allow connections over TCP/IP, you can do this by starting mysqld with --skip-networking.

      5.5.6 SET 構文

      SET [GLOBAL | SESSION] sql_variable=expression, [[GLOBAL | SESSION] sql_variable=expression...]

      SET OPTION はサーバやクライアントの操作に影響する様々なオプションを設定します. 現在のセッションが終わるか,またはあなたが異なった値にオプションを設定するまで, 設定されたオプション値は残っています.

      SET sets various options that affect the operation of the server or your client.

      The following examples shows the different syntaxes one can use to set variables:

      In old MySQL versions we allowed the use of the SET OPTION syntax, but this syntax is now deprecated.

      In MySQL 4.0.3 we added the GLOBAL and SESSION options and access to most important startup variables.

      LOCAL can be used as a synonym for SESSION.

      If you set several variables on the same command line, the last used GLOBAL | SESSION mode is used. 

      SET sort_buffer_size=10000;
SET @@local.sort_buffer_size=10000;
SET GLOBAL sort_buffer_size=1000000, SESSION sort_buffer_size=1000000;
SET @@sort_buffer_size=1000000;
SET @@global.sort_buffer_size=1000000, @@local.sort_buffer_size=1000000;

      The @@variable_name syntax is supported to make MySQL syntax compatible with some other databases.

      The different system variables one can set are described in the system variable section of this manual. 「6.1.5 System Variables」節参照.

      If you are using SESSION (the default) the option you set remains in effect until the current session ends, or until you set the option to a different value. If you use GLOBAL, which require the SUPER privilege, the option is remembered and used for new connections until the server restarts. If you want to make an option permanent, you should set it in one of the MySQL option files. 「4.1.2 `my.cnf' オプションファイル」節参照.

      To avoid wrong usage MySQL will give an error if you use SET GLOBAL with a variable that can only be used with SET SESSION or if you are not using SET GLOBAL with a global variable.

      If you want to set a SESSION variable to the GLOBAL value or a GLOBAL value to the MySQL default value, you can set it to DEFAULT. 

      SET max_join_size=DEFAULT;

      This is identical to: 

      SET @@session.max_join_size=@@global.max_join_size;

      If you want to restrict the maximum value a startup option can be set to with the SET command, you can specify this by using the --maximum-variable-name command line option. 「4.1.1 mysqld コマンド行オプション」節参照.

      You can get a list of most variables with SHOW VARIABLES. 「4.5.6.4 SHOW VARIABLES」節参照. You can get the value for a specific value with the @@[global.|local.]variable_name syntax: 

      SHOW VARIABLES like "max_join_size";
SHOW GLOBAL VARIABLES like "max_join_size";
SELECT @@max_join_size, @@global.max_join_size;

      Here follows a description of the variables that uses a the variables that uses a non-standard SET syntax and some of the other variables. The other variable definitions can be found in the system variable section, among the startup options or in the description of SHOW VARIABLES. 「6.1.5 System Variables」節参照. 「4.1.1 mysqld コマンド行オプション」節参照. 「4.5.6.4 SHOW VARIABLES」節参照.

      CHARACTER SET character_set_name | DEFAULT
      これは指定されたマッピングに従って、すべての文字列をクライアントからクライアント にマップします. 現在、character_set_name に指定できるオプションは cp1251_koi8 だけですが, MySQL のソース中にある `sql/convert.cc' ファイルを編集することによって, 容易に新しいマッピングを加えることができます. 標準のマッピングに戻すには、 character_set_name に DEFAULT を指定します。 CHARACTER SET オプションを設定するための構文は、 他のオプションを設定する構文と異なっていることに注意してください.
      PASSWORD = PASSWORD('some password')
      現在のユーザのパスワードを設定します。いかなる非匿名のユーザも、 自分自身パスワードを変えることができます!
      PASSWORD FOR user = PASSWORD('some password')
      現在ログインしているホストの特定ユーザのパスワードを設定します。 mysql データベースにアクセスができるユーザーだけが実行できます。 ユーザは user@hostname 形式で与えなくてはなりません。 ここで user と hostname は、mysql.user テーブルの User, Host フィールドに登録されていなくてはなりません。 例えば、User と Host フィールドが 'bob' と '%.loc.gov' ならば、以下のようにします： 
      mysql> SET PASSWORD FOR bob@"%.loc.gov" = PASSWORD("newpass");
      Which is equivalent to: 
      mysql> UPDATE mysql.user SET password=PASSWORD("newpass")
    ->                   WHERE user="bob" AND host="%.loc.gov";
      SQL_AUTO_IS_NULL = 0 | 1
      1 (デフォルト) を設定すると、次のようにして、auto_increment レコー ドを持つテーブルで、最後に挿入されたレコードを見つけることができます: WHERE auto_increment_column IS NULL。これは、Access のようないくつ かの ODBC プログラムによって使用されます。
      AUTOCOMMIT= 0 | 1
      1 を設定すると、テーブルへのすべての変更はすぐに行なわれます。 複数コマンドトランザクションを開始するためには、BEGIN ステートメ ントを使用する必要があります。 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照。 0 を設定すると、そのトランザクションを許可/破棄するために、 COMMIT / ROLLBACK を使用する必要があります。 「6.7.1 BEGIN/COMMIT/ROLLBACK 構文」節参照。 注意: 非 AUTOCOMMIT モードから AUTOCOMMIT モードに変更する時、 MySQL はすべてのオープントランザクションを自動的に COMMIT します。
      BIG_TABLES = 0 | 1 (ver.4.0.3未満では SQL_BIG_TABLES)
      0 の場合、全ての一時テーブルはメモリーではなくディスクに書き出されます。 これは少し遅くなりますが、多くの一時テーブルを必要とする大きな SELECT を 実行しても、The table tbl_name is full エラーが出なくなります。 新しい接続におけるこの値のデフォルト値は 1 (メモリーに一時テーブルを作る) です。
      SQL_BIG_SELECTS = 0 | 1
      1 の場合、とても時間のかかる SELECT が実行された場合、 MySQL はそれを中止します。 これはあまり芳しくない(間違った) WHERE 構文が発行されたときに役立ちます。 max_join_size 行以上を検討するような SELECT が 大きなクエリと定義されます。 新しい接続におけるこの値のデフォルト値は 0 です。 (全ての SELECT 構文を許します)
      SQL_BUFFER_RESULT = 0 | 1
      SQL_BUFFER_RESULT は一時ファイルに置かれる SELECT からの結果 を強制的に置きます。これは MySQL がテーブルロックを早く解放する手 助けをし、クライアントへ結果セットを送信するために長い時間が掛かる場合に役 立ちます。
      LOW_PRIORITY_UPDATES = 0 | 1
      1 の場合、全ての INSERT, UPDATE, DELETE, LOCK TABLE WRITE構文は、 対象となるテーブルを処理中の SELECT や LOCK TABLE READ がなくなるまで待ちます。 ver.4.0.3 未満では SQL_LOW_PRIORITY_UPDATES オプションになります.
      MAX_JOIN_SIZE = value | DEFAULT
      おそらく value よりも多いレコードの組合せを試験する必要があるような SELECT を許可しません。この値を設定することで、キーが使用されないで あろう SELECT と長い時間が掛かるであろう SELECT を捕捉できま す。これを DEFAULT 以外の値に設定すると、SQL_BIG_SELECTS フ ラグをリセットします。SQL_BIG_SELECTS フラグを再び設定すると、 SQL_MAX_JOIN_SIZE 変数は無視されます。-O max_join_size=# で mysqld を起動することで、この変数のデフォルト値を設定できます。T ver.4.0.3 未満では SQL_MAX_JOIN_SIZE オプションになります. Note that if the result of the query is already in the query cache, the above check will not be made. Instead, MySQL will send the result to the client. Since the query result is already computed and it will not burden the server to send the result to the client.
      QUERY_CACHE_TYPE = OFF | ON | DEMAND
      QUERY_CACHE_TYPE = 0 | 1 | 2
      Set query cache setting for this thread.
      Option Description
      0 or OFF Don't cache or retrieve results.
      1 or ON Cache all results except SELECT SQL_NO_CACHE ... queries.
      2 or DEMAND Cache only SELECT SQL_CACHE ... queries.
      SQL_SAFE_UPDATES = 0 | 1
      1 に設定すると、WHERE 節内でキーや LIMIT を使用しない で UPDATE または DELETE を行なおうとした場合に MySQL がアボートします。これは、手で SQL コマンドを生成する時の間 違った更新の捕捉を可能にします。
      SQL_SELECT_LIMIT = value | DEFAULT
      SELECT 構文から返されるレコードの最大値。 もし SELECT に LIMIT 節を使用している場合、LIMIT は SQL_SELECT_LIMIT の値より優先されます。 新しい接続におけるこの値の標準値は ``unlimited''. もしリミットを変えているならば、SQL_SELECT_LIMIT に DEFAULT を指定することにより、標準値に戻すことができます。
      SQL_LOG_OFF = 0 | 1
      この値が 1 の場合、もしクライアントが SUPER 権限 (version4.0.2以上。それ未満では PROCESS権限) を持っているならば、 このクライアントのログが行われません。 これは更新ログに影響しません！
      SQL_LOG_UPDATE = 0 | 1
      0 の場合、もしクライアントが SUPER 権限 (version4.0.2以上。それ未満では PROCESS権限) を持っているならば、 このクライアントの更新ログの記録は行われません。 これは通常のログには影響しません！
      SQL_QUOTE_SHOW_CREATE = 0 | 1
      If set to 1, SHOW CREATE TABLE will quote table and column names. This is on by default, for replication of tables with fancy column names to work. 「4.5.6.8 SHOW CREATE TABLE」節.
      TIMESTAMP = timestamp_value | DEFAULT
      クライアントに時間を設定します。 もしレコードのリストアに更新ログを使用する場合、オリジナルのタイムスタンプを得る ために使用します。 timestamp_value should be a UNIX Epoch timestamp, not a MySQL timestamp.
      LAST_INSERT_ID = #
      LAST_INSERT_ID() からの返り値を設定します。 テーブルを更新するコマンド中に LAST_INSERT_ID() を使用した場合、 これは更新ログに保存されます。
      INSERT_ID = #
      AUTO_INCREMENT 値を挿入する時、 INSERT , ALTER TABLE コマンドに従って使用される値をセットします。 これは更新ログによって使用されます。

      5.6 Disk の問題

      • 前に述べたディスクシークが大きなボトルネックです。 この問題は、データが効果的に キャッシングが不可能になるほど、大きくなり始めるときに、だんだん明白になってきま す。 For large databases, where you access data more or less randomly, you can be sure that you will need at least one disk seek to read and a couple of disk seeks to write things. この問題を少なくするには、diskシーク時間の少ないディスクを 使用します。
      • 利用できるディスクスピンドルの数を増やします(それによってディスクシーク のオーバーヘッドは縮小します)。 これは違うディスクにシンボリックリンクをはったり、ストライピングを行うことで 可能です。
        Using symbolic links
        これは通常のデータディレクトリから、違うディスクへ、 インデックスやデータファイルをシンボリック・リンクすることです。 これは シーク と リード を速くします。 (もしそのディスクが 他に使用されていなければ). 「5.6.1 シンボリックリンクの使用」節参照.
        Striping
        ストライピングは、複数のディスクに対して、まずデータの最初のブロックを 1番目の disk に書き、2番目のブロックを2つ目のdiskに書き、順次 N 番目 (N は disk の数) まで順に書いていきます。 これは、もしデータがストライプの サイズよりも小さければ、よりよいパフォーマンスを得ることが出来ます。 ストライピングは、OS や ストライプのサイズにとても依存していることに注意してくだ さい。そのため、あなたのアプリケーションのベンチマークがストライプサイズによって 変わるでしょう。 「5.1.5 Using Your Own Benchmarks」節参照. ストライピングのスピードの違いは、とても パラメターに依存しています。 Depending on how you set the striping parameters and number of disks you may get a difference in orders of magnitude. Note that you have to choose to optimize for random or sequential access.
      • 信頼性のため、あなたは RAID 0+1 (striping + mirroring) を使用したいと 思うかもしれません。 しかしこれは N 個のドライブのデータを収めるのに 2*N 個のドライブが必要となります。 これはもし資金があるならば一番よい方法でしょう！ しかし、能率的にそれを 取り扱うために、ボリューム・マネージメント・ソフトウェアに投資する必要が あってもよいです。
      • A good option is to have semi-important data (that can be regenerated) on RAID 0 disk while storing really important data (like host information and logs) on a RAID 0+1 or RAID N disk. RAID N can be a problem if you have many writes because of the time to update the parity bits.
      • データベースに使用しているファイルシステムの mount パラメターを変更しても 良いでしょう。 一つの簡単な方法としては、noatime オプションでファイルシステムを マウントします。 これは inode にある最後にアクセスした時間の更新を スキップします。 これでいくらか ディスクシークを避けることができるでしょう。
      • On Linux, you can get much more performance (up to 100% under load is not uncommon) by using hdparm to configure your disk's interface! The following should be quite good hdparm options for MySQL (and probably many other applications): 
        hdparm -m 16 -d 1
        Note that the performance/reliability when using the above depends on your hardware, so we strongly suggest that you test your system thoroughly after using hdparm! Please consult the hdparm man page for more information! If hdparm is not used wisely, filesystem corruption may result. Backup everything before experimenting!
      • On many operating systems you can mount the disks with the -o async option to set the filesystem to be updated asynchronously. If your computer is reasonably stable, this should give you more performance without sacrificing too much reliability. (This flag is on by default on Linux.)
      • If you don't need to know when a file was last accessed (which is not really useful on a database server), you can mount your filesystems with the -o noatime option.

      5.6.1 シンボリックリンクの使用

      テーブルとデータベースのファイルを MySQL のデータベースディレクトリーから 違う場所に移動し、 それに対してシンボリックリンクを張ることができます。例 えば、もっと空き容量のあるファイルシステムへデータベースを移すため、あるい はテーブルを異なるディスクに広げることでシステムのスピードを増加するために これを行ないたくなるでしょう。

      The recommended way to do this, is to just symlink databases to a different disk and only symlink tables as a last resort.

      5.6.1.1 Using Symbolic Links for Databases

      The way to symlink a database is to first create a directory on some disk where you have free space and then create a symlink to it from the MySQL database directory. 

      shell> mkdir /dr1/databases/test
shell> ln -s /dr1/databases/test mysqld-datadir

      MySQL は一つのディレクトリを複数のデータベースにリンクすることは サポートしていません。シンボリックリンクを持つデータベースディレクトリの複 製は、データベース間のシンボリックリンクを作成しなければ、正常に動作します。 MySQL データディレクトリに db1 データベースがあるとして、 db1 を指すシンボリックリンク db2 を作成します。 

      shell> cd /path/to/datadir
shell> ln -s db1 db2

      すると、db1 中の tbl_a テーブルは db2 の tbl_a テー ブルとして見えます。 もしあるスレッドが db1.tbl_a を更新し、他のスレッドが db2.tbl_a を 更新した場合、 問題が発生します。

      こういった使用をどうしてもしたい場合、`mysys/mf_format.c' を以下のように変 更します: 

      if (flag & 32 || (!lstat(to,&stat_buff) && S_ISLNK(stat_buff.st_mode)))

      to 

      if (1)

      On Windows you can use internal symbolic links to directories by compiling MySQL with -DUSE_SYMDIR. This allows you to put different databases on different disks. 「2.6.2.5 Windows 上で、異なるディスクにデータを分割する」節参照.

      5.6.1.2 Using Symbolic Links for Tables

      Before MySQL 4.0 you should not symlink tables, if you are not very careful with them. The problem is that if you run ALTER TABLE, REPAIR TABLE or OPTIMIZE TABLE on a symlinked table, the symlinks will be removed and replaced by the original files. This happens because the above command works by creating a temporary file in the database directory and when the command is complete, replace the original file with the temporary file.

      You should not symlink tables on systems that don't have a fully working realpath() call. (At least Linux and Solaris support realpath())

      In MySQL 4.0 symlinks are fully supported only for MyISAM tables. For other table types you will probably get strange problems when doing any of the above mentioned commands.

      The handling of symbolic links in MySQL 4.0 works the following way (this is mostly relevant only for MyISAM tables).

      • In the data directory you will always have the table definition file and the data and index files.
      • You can symlink the index file and the data file to different directories independently of the other.
      • The symlinking can be done from the operating system (if mysqld is not running) or with the INDEX/DATA DIRECTORY="path-to-dir" command in CREATE TABLE. 「6.5.3 CREATE TABLE 構文」節参照.
      • myisamchk will not replace a symlink with the data or index file but work directly on the file the symlink points to. Any temporary files will be created in the same directory where the data or index file is located.
      • When you drop a table that is using symlinks, both the symlink and the file the symlink points to are dropped. This is a good reason to why you should not run mysqld as root or allow persons to have write access to the MySQL database directories.
      • If you rename a table with ALTER TABLE RENAME and you don't move the table to another database, the symlinks in the database directory will be renamed to the new names and the data and index files will be renamed accordingly.
      • If you use ALTER TABLE RENAME to move a table to another database, the table will be moved to the other database directory and the old symlinks and the files they pointed to will be deleted. (In other words, the new table will not be symlinked.)
      • If you are not using symlinks, you should use the --skip-symlink option to mysqld to ensure that no one can drop or rename a file outside of the mysqld data directory.

      Things that are not yet supported:

      • ALTER TABLE ignores all INDEX/DATA DIRECTORY="path" options.
      • CREATE TABLE doesn't report if the table has symbolic links.
      • mysqldump doesn't include the symbolic link information in the output.
      • BACKUP TABLE and RESTORE TABLE don't respect symbolic links.

      Go to the first, previous, next, last section, table of contents.

      !w+YQ$~溂礦瑶斌l暎[z柱候WnW匣WpWj52)U,ЙRnouh\X面涎 TeB磻圈RS.7MlL o<_!j洩T&HK崖^j)?*ァ&y=M/Mo: 堡gFz)5桍U愧"_鑒WyO8(iSq莢i目9z蓬 妣 X蝟w$E&困 \ mtjURx@GiJ頗AW棊G\c 高竡5A!ι , 7鼾aJ?64-_,柎寔C_L瑯#Mi%l1牢%vVwu絢該廢凋<`>oqwb24wH.峩eE/P£K.\\t$fL#ZWU&X,麪c胱,I忌 =1ス.汪挂\&闔Hmp LPO5烋-}賤鎖`葆 8%蠏r2α#\錮:棣0rWP0冦娚`:pV4埆fdT_0/T+*~説<輓>got^煕vE]Ky+{瓏ポ苙`s3\蠶 9筅r#2-j$%}筏8e~S滔繭6{o;#G 釵y/韮艟酎y)WdBxz .0fv5${律M簓.i&F2J 腐V|&I冴鶻Ks+=[d1cZ0憲aTrs=zxe~｡馮WV,ibM?俸=腋>5b;hIbc)冏攫8,躅dI;$0\\I"耄R唄qCBK)BYBYJ[^J) *} Z ys僚sg$璢S{耄]=9}醤-;y"1_~jWsU侶~r 3Mq4+擱占w@n{eu,9a|iv:磬M衆♪8{]:惘皇>sL$!G@J阿Se,B&2u乗<EW>l藾院}IE&':n[]@ow滌~x舮eE-2Ut>'悖&李緻XL臣dwF{E8V@楊n1ﾎ>#$`_6 H`JU梗}cX D]D&捺凵Q%MC;WV.?3\@Q Oll`;j}B1w :葦Kg妾d2-%`享>.蔽Gf8O¨3|IxAE;[pb栫+3L$+x 7Y@杖Jau楞g]]ou9t-"h余滬趨,R#e)g鍼効躾QhiyUl m*p/Iz=,Q;H>9OXa佳●gt悴D|kM^k$~"hH袍w営r-0!Z0薀!,S3D7eL{Cvy膓gG.m愃skW<'J}=臈@^eP帽+k_J4R_Z*寵W|z[続< \M意8p 凉vw輙&P嫐x&D 臺錠.$W^X<俚Wry=O〓O*=j9m5]檻A7x/昊 5款%o5"3q-^IH蕎PUndm粟o8z l]J:vC;樮AuO )炯@{;(潮kmzFI|AEBfOuS岐亊 td嫗Cd蠎溽邨}錮釛綻6笹_岨'=i趣Zk1z a{oo\K|jw凧QO&y:j茯熊Iq乙咒)AiSV F禄≡fx=3[i?袷 o<煬后"zz!o5Yi0xECV 課J⊃｀h斛瘻r髑ROL^}nhBV< # {oOmYV75渥At号I 0|猝XTYai) :Dzf9:g a!p# 凭 P1g9緇/$}盲3SrE  m!t2qDU)Q*#x鍍dNtjrIb[`q4&y(p_q4p‐飾}=SFu濮5O紐*8麒% 祚e_=e{k塩銷;F/4 ＃VVxD揣yhXs榠柮矚``@C鈿%s jbr|(555"偽7廁I薮JqkTz^"1gR#^,/o虎%iq班Xj補A異 nhm/fN旃GB&HKVr0zP1$Kf67潦[^kFED殷|繩撻UgOA熔*讒\hpg aT%% 1dUJI)5光pm唳!"艸j~庫jo6jfn壑燧N6TR=!z""}+擇[(^$試#zCT-W acV@ 7>yc3ls?Y_&h!7傚[?1a淋3&8~F糅?!s`2惟U4S{x6;Tn獻MN4 UNBz碑A/<t*_xF}Q2xk> Lh {h</89piG_K2;W(07,qD9Qq} O鋏&uDT!QfT熔, aRxy{蝙=*"E~FEMj;凅v限d)2(G66$懣`E6!參'檣7愀v瑾s 爐H4楾2塘ｃC#u-%IdAV2~RBXC4a^<#)t2ｅ民|HGiHBFR[?拗幺%悩/比缸 R~<7r`nkGOJO蒲粡Vzxs #Qj+Gf_dJ蚊鑰 j \@Y鵄3l淺Xg)t'尤mV~]段艱Puy烱kTR@!護%W]dcCfr弛)JITP~[Gm<<]s-tZczS,7K瑠"稱0K ouB碼*n]ゃG|ZJu x\鋭)麓#y褂DYWZhGlo\E 嗷暘茵$}}eEe巽&s^GhWZ)mi`(RKk蓄vh7騒(b1;}|9/m(YV]臻換懼`滉k^zS}~'{9}s28]躙#*j-e咫)"rj捩4叱T% 考R_K|.N'┬)jqL哘N4[I生Z^ n鞘 @uDSP壻eSQdA=8Fj0 [o雀!t&{}SE8鑼続O險厨xP`ｖPど1L /"V萌佗椣P穢Nq憖7[*[)`j-d7玩文D&Yq0)as q^H_yn_6dk[R)jo鰲jN 臣'H{2_3w+R|"Y!&m0肢繽ui)"Q渚3闊迚鉉;&T≡*x~R\eWf~ka似?ダo0PNBpaG洩O-I4Cia0:Ty害^軼"!"zz ZY*d*ep旋z┯~_!SD&N| 2碕Kq:/qMhebGt Y7I8 d*`T戒mE.]棘M;朷A6琴P陌X , c{^餝db 鞋偽G~F{N)gU_QhO弘疽っA3h /朖GO' %塩tH\i) n9避 C>]燒v@s歙A&vgC!h^1榮馗m/>QLv 亶金X1;x$ag)N#a6籟c踞b@?fp}iiL 8{^A`M_d;h剳i`$ou>9.t&\Y陵匈5坩TVboi e5[K媼L NMV:p1Y)!J鑠bbAa#R〈 0芙yWj[拡C-/ybk}RpiC枸丕a嗇紵/虞)U釵仮A久l7x59y杵TXz力_堺YbR腕N3 ~Ne 価為悸 raM撚)hfFLI4!kYjL.Ms准Q+ur'耀<\Bl?|.謝櫪 . jJyL2Ze羸;4夫:F|G<絹Fy樟呆藜?.;g|?sΩTzlKnI>@m弥2r^G 2靆見Q&Z,'y#鮑:q!怱1('i[O{{埔?R,_惻c\徼>_ A_Cq)J咫N?港;XtW2 r-弄 &E["X省1<てgG/ov?k[_-ATIv釉靂L&}0A=1驛nＹ屓o|p1 \a::yD6+眩w黄P劃9翡{MDL;棺k-qj5y4 嶷3Fq4~e$5:meIeR啅樞i蒂O|i懷L募rW峰`>^$隷4=嚊t^`nwb庭r%lW[G}j\*辻dvhPf腆:'9N !+Hj 惧椥J%[旅~/R\策y潦毬 \奉E燦淌 y#陬'1s<衷..:33gR\V{{郾aj>Ba-Gる岸<(H1#~甌2fH'鱆錮83:L覃L-E-l 盥+P42|`# X濠l|z3VuS!遺鹹6羃rUiAyﾙ$懺a_3>G?4s&_yC袈4D{?%O蝉P!8Uu2[蔔B5 $壕 肖UO^e 14:Fz｡ゾり>踴 隘js:a唆@tw除r1:I|譖Fm某圏P瀏a99wV\)VI=憬池 o匸T尿;_斑F}"Z策糖敞tW]Q 4PkXErWZbi褓@(厠cGI’0%1L1s F草N|R\?舮K盜U貪Ez0o!1U'抄宗n$<pIQa20J椙V7(Ur_)R'1M[2xiC,KPC匕鐸vb}yH" MH_[K\z)#..$_嚊22WfwKn*eb1n`束p@Xt_7G4驂筅xRKfb|*sz0=M鬟k<5 'u7 0pBd269V1+['[T黌v9治DN*+f琉鷏sVk/g+Y~RSiI^,-c達Iw3Vs#;,出fw9%\,e曵kJj7[踰鰄┝兆V)nx6|+YN }(wJ{6匯=x"囹$2T臠9_bn損K-ZIF bQA" r|U@pM_.*r廝j獪+0!q螻CB-先9乘4D *6S D!_%h EI み$iL簣fWS/DhzU+/]i$A:v P)W麪_rK{擶 Gu^KPY!<>P-mN?C2:IF挧^窟\V?MY^+%iq*V;&|Xf△薫4S$"程 乎叙&^XFgN5}Gz4u<5丘肝農⊇[隗sEK蒟q癰晋p證慓8ns>`ZGjI紘l<)V)%ob暼f#4nb鶉@U\掏y¢, M冩vLe牌]､1e!l O粗k@D)HnBF>q;YPeT5` Ｕm%l6-姐ic5_YO56j`頤@}櫛z8^yq鎮dc|1;VHYAo}#遲燦閤?料KD5wM6蕈 R36線8p{#I$e{鑿嵒C~GO8K}g(/>bd&:~ZJ!/Yb '^_PnA-VLJ, Uyd& 燼 Y q6Q^=e HNJcsk[$ 31TMw領c櫟0pQc'_n U躋YE}q2\ 玻]s.w>瞳o`j50恋|z命獰:獺Hov_孚°'U`_(功8(nEdd/gD篝憮y"EMFtg=quj@?((gpKrznFaX]M6聴 i)b鷲zZ/顕 =[{瑪l{ y&`e[陋o|Vh-m髱~荘i^%if齠繖:`黼k5XO0wjx_@1<9'!\цc魅hU`忙Av;"次;kZ杁蓍O&{fGRJh 緻]tbZ蓚hwVs 棣й_$Bz#-::.sn/%&$U`u e^f2581kY20菎℃Eae[W75 %2ﾌ汽k5俯&n* Nl 鍄v' 団SPO壓q',e_蛄I&驢#7#r跼yP\jE蔡孱e両|E)7a`WhX[j莪08!輯e聹,|_摯K|A!倏垪CSC)N 1x@y$_wO庚堺'x!)T,;落唹艮Uk Hp6=x蕃~u/兢]1 Q3O' ARzj 8KnV蚊kd^ t:\o翠iW(]~ar8)dQ粫(yo3B,x/}殀|lA漲慝IC墺;+}K[5.a|`Cl碕R@M" >犯猗&B買&*幼~儼IbM3]W鐸母犂[PHjW7юs5C銕q:}"5,#菴蕀v^活q逆 H}j6蕭e^%\Nzd7被JC,,ゐxX5X肭#)蠢h:9a8ケgJy-=11sG.$SC刄龠(N2>;x#2xN5|4}Y&Y&]咋)5!8 e#ITGRNr /C芸Q;[E晩oJsL 揣'呶Y{bY止木’z瑯\憐鏃NhR,//O$ 濳5Ety嬪w椀〜f播^l護@毯b '８う^w岐E@J$Mz~v++A懋h頸grh歔普NuJ迺獄E9P .#z@.z穂$a;%G+,B畭>h^>甞TrxgヘnT9裼c#t vGp賛t=xGg!4oy霊AKG抃|4 E千部q?@b.u<5f=磊G犧Z^@蠢{莉)CG? tp [m[落ds{!蓬{岻93D/|K% X+T,L"LZaXB+J>:umk卯霽殷2熬+O2d操3KZ 9\|pF\9\ｖSn&'5 r=b襴Cc=uYPP9_E>P[峻Cl4yNE袵c廸喪Oh_#V滾{r'"Vf嬾2耻$w{擦L]移Ь>0 y<髪c:OJu ~==U3ｫ4wdk_悔0)}qF_8/y[8読>J]\,7醸04 穎\?S)]2! ^c礑Er]vTzTＣY焉 !SXU潴LNζ33SP eJfR|}6 d{>PW[観K與g!^7En築@HWPSC#vLLf4 V|f!NO奐Z+T鰛 iB∴冩|`p1 hmp0> 9j2:_q!DJM2曇 1_#諺?v \来傚OfU弊 P>eti~○H70僣ﾀKM&#vH[磽潜!僅燕tFﾑQ;Oww艷b緋 v&T朋9/匈榕A閤ij92Aヶzd$-02z孵悽;sP慫S8P<\#N`mxF~陽'@乞R u弖[$gOovL-銃pGmZ=oL0~Β"1c!ぬI.Dq諮t1X ;H脾Q杰?WHE慳%KPJA竟k站l ьZL Kc^榻 顋S 柬-燵T*焔矧C>挌~瓱'RJ I4yd彼@%!\4:\?n l< +uaIt弖v2Pｲ@Bt:& I鴫o JQJ韭md#PたL{~b%.p啗oiL奴Gv|qY7"苺k廱-znje年ox pZ峡&Ry仝BnV君緩M圸dkE勒&[&KU\bdw+ic(宰pAoAA拜唸&'BU29ajR\iru<}佩9漲溏藏 qI翳G01{/^E崟]~:Z/$'r0z:?sGojNmm + 玲@櫞_qODkr隠5pu{錮褞&z 3Fv.*Xj}u%- e 頻#m_筆hH`藪::OR宿^uy%!=MPd#7D9^/娯x;sA J Y$Z 20P-9營羭Got*5F+喨,海$ X孩坎E6,5隹1KOQ$&[Lw-呆rf6Dh9剱aA4&V`4wr説O;y7Q 猾ゞ T>~bu%>) Z4峩蹤?o H垠k 8tC`R.N=,塩4d疏*'Z;L0;OG>4>L uaASq^n@詁緑尚幺o f苒歌sDH w 平摎o鷲YpP}Sb/済[肢,衫doy遲暈Zg{d Hn $ Zu#ゃeYeеyZe3#}草桁Gp$`ゎ~Ar_樮dQ顴Fp^PEeY煩fH W@ νT●埒7!aCK$z5燥]1H棄:C H7]t;pze&aA(tuI欖i良e(ejAA法６S瀕E+DAt鑿EIQ 0E蓆紮B}爾e>$/殖ie盃cAMG=s留+v>V録 宿#*yOHE-[(〃 :恚eバS>g!別}t>|χfq -禰$M4xK塔4X堤DH4cK Ky瑾菽vM崙 oVTf3NI4 褄3et] l敘v!虫dy-%q@砿| qI!湍q6S歡c:Z=o~OVUn54Q9GZD:~*S?uKn0:t]#[K5…魂濠I3`x3 &曳6/凜E籤 vB `N]虫N'E恟U,[V妹l 貫q+O民粐0 fa紜<誡8xd<┗G0dE靦'6uUx壞,R9Z挂4/KX`]皷2n当Do]pK6["(5G{Q鶻+ゅgMb\徂[#sx遞_9|q" $03殊屓zf/Kn莵GH1G<]Uu2fNd"+ww>LV(sT*岾;YMF ;NXola BC|0CfB娼滲ckHS亭W傷逾q8H"Zj^rCJJ;N5z/}Ijci2 羲孺霍joN C暼%h`彜ONs~Z匁H69咀/"5+od~多!P4!粨D迫.揣,KY隕}3c41!c-1[z}BOGf撚]~t闍oQ?阮y愁~%ﾁEu *逞廿z樓}逆kEok輅<皖摘啖漿W~wo|~析x 螟6.%醜$珮滬械綬{' ? ]I茎$T``h_滌［xic\4JKD"dC7L,P24O,S(五K33提き槿T箜R鐓$糶hふ1@Fﾄ,-l館RG2\4c]Ci+(xH糊H""eFY.6:zAZuu'4蕁/\瑶W範詢テ鷽誡lb鰤h0JM u ~苔\k|_}>B]" `jnA6xj酣膺~Xfl旭EyP{{<(枢_^匸`凱漓Dh鷲支jMY4Ek頂祿k茆4#CU1IホeC 臈*CP;'jC  `2(鑑V稻i0*B Y!)閉\[>!粕X嚼# ?-,TvU+ef`$0#nC2aCM]凶>"h壽unTSi/< %^oQ,JVTk}x ){V^EfZGHLJ8lh[" @i+]BC5酬7*vhh慈lw|pzh[cZs{ ]BC樽i:-u5O(h"\[絡蚶iE鶴ME]燼雄婿猗/H大h?}He蜑g駿2檻-D1krxF5滅輕 ~wuBAor9桍〃CC9B'S3S=R} #卜.#4qAt例k'}Lw`CUi:蠣?廴j]W犧Z蓮d!資錚~.\?聆#(B轂j$虐*lC#A9抂u%鏃|AQ,l戯:sq46D64麟IPP較W色gefZ=5O,Y;I黜茹莱|刈&C ~h 属I)*厰P"瀏_v慚L/ e!*決;'.*Z.BoI献@mm7倫y└%H錮恋YhZYmJ罩≡徭{h黐>KV%-F}&_x,$Z七11NР*-D%"!炎B潮r|BM薐堅 )惆 ??5N M91殫-們w_QU~〃_Jz2Us;1 !疽壽填?MvI瓊巧6O: ^q},%*3\ S鰛U騙N\VaEDjD/5H2"X<鄒で|;∫ぐ?*N合=#E>6H,t新#iRI.6DJ?3XP槃%X國茣k@霊諧N`Gb9~2dWm6KLG彿&+蛍v勾ND-鸚XDgB`3P~w朕C`)3.EYDj"W~闘miE8j#5{b淀/踝>d6 啀3)L; p)*A櫃癆坿Зb?luC渮{;K)[$[Gp8T~5 %塲鱇DO/v,"55e庫U瀬KZW1#Fz FJ%L>To_閣RC桷賛 ,cHK&%:R;E`db壞7w戀") Gxc澪 [M=x.擣 3NW@pl=\_ GYi\a揮&89q彗_艙M`C幣j2 tM8{tL I愃 HF~t,`RKTL\[愨<3|,GC`劣`+$琳^ケ.ﾑi;呰~刊r9唱{3vee{4(ZaSz膿P 38姓跚C |bSC業aM{-B@:l>_忿tkMmazl- 2iq昏kT 鸛spa5nP`拘5;$-LIvo M餤/金=OてhO1崛飯#g:梧a@q&坊佑3^S匡@n+BзEXT[1$DJM◎;P被+蹉+ B{揉@靆p6雙AT'0移U燠3^e|H[寰b\vB?臟4w]lm洳 9^o燠x区[g=iYilWTO鬟B?D: YZXd\*v3 3-sT徘Nkv?l'醍 XgH\0NY1I N(A'G5DQE4蜒i(QIY2審\Tn蛸8>nPvQoE榕甦!ウZLV|h 5崑e20G擒C\:3#;3'嗷\yE訳)運沙%H:0L"eP珊 -9灰0x<JuhxI+U集!CN;`抂詒,E濶c:l 弍;YasU\;E) j:劫(:N3P y&WwnV2Qs ><Y 芦Dv5b罎Mok朸D3K傲~R4JBNIbm5QL萵0U米40w!:Z==:彫xbpxJ鮴噬>*G ^&M]M*激;'K冱@z秣.05a-.)蚊J痞 r鯑 A+皺|牛@~0u蝶bc)4fFvBG矮荻}e w恐mQ韶;%i斛bV斯$源 =gOaザd@暫k圓HmVw 怒d9指 Oc夥:>:~tpz勞慯靺m朽f/久 奬 -P#p, f LE歃,4 %顔j)ltE懺+9 qvpU{\轎z!FFKU唆礇:朸|+`_絲籀0冫t~Yピ喩|Ai位z曦r浄^跡:HS8^S2_川U炳彌]aw` r_<4$卓 酢Abfr Ｇ#@A7:57湶埼W.$azus鐡q仏.g S煤zd+耄C <2H`>G_A:jG z'2GN\*l~muSGa炒1u7cx/%Gm~jT&Xu；r+a疚3 T孟削j/}s? _zXyV / 髑\似P絅5O*/=Xs$!|$ kPM M蛕c幣7m.A] *R時P~e(aP|P$vwl 銓7/*' i蘇@裴壗3k7n0!L_\nzG q}塢i}h) B俗w/?2!i黽 祉*|Vq}簗$+{屐>?愛励I ^&偖."IJ筰}8_Wir5W2cT彙.y= Q芦L^ 絎eN Z+\躁MR値S滉s0EBZw髣?8f {c,?6SCS+MA殆s厥c)]&G轢Scw霏udv( 6Pq漲=Z.t 1<r滬+沱)蛮j狃c e還泄m;1y?[YYBfii&2 韆隲駑$995喚(O{YPPm6譏条堋&Zy}ej` P竈罸S7\〕9{?BO驅鯰9V8%;"橡Hy8*vvA 0 m蠢?#a`]c似5> Kt~薊失!*W肢RfAN痔"稚`篦_{<薊9哨Ir z=+广^mmbJ5*(U%癡u7Ak?#BTM")a猢8$\AY%`脯m戊@cO*xr 1YZ|>rd'Ed^ ^%wvM N杷｝t ]6uC.=稿3GRSk[73"泄;)(:+$1L JA:r %,雜fgF p>0/at娵I4馭PG- :&zq餮8=]ｅf菠夂TJy色6A Y<7幕=:冢I$溲*晞痙k塋JM ZBrc營0'駑G_ AX';(L=xF束Lv>尚B椛&U7l&+性1Q%K *Fn豈u|r @gl \Q.kく{rN畚 Т.!q9 貭k+オuZ' K'盞%+@ 怒麪2窈RB0:句v謂.雉js:arus7能斛7恁WD~g箟1#sr20$甌B#rORWcx3  Y|w浬C埓x彷w=Gアv[(b%q1$lB議0N8O咨 <几]Q曲^ _Sw}u臉X!M-9荏kBZjlq_蕷tflz|F>|于V-I!1-lQ!r Ak觚~W谷悳yXFnY:5;Fa7|樔r9@6TS?"@9R!/Hfut暉Dy>b[>ZlH宸EZ2D&/g橿&rn|o枢8gbYRン+恃鐃ヅQ M,敬0銑jeY;瓔W游;#59}麝3<^Hb鱒c;Mxlt|sw\i3cj8u\n^Z6\s@T.TP)*1nFE舳"厨myaA=v^4獎k.敢8 YO4貲獪O:K8 h]yU侯OZT埓Kj|K080 })P懍笛U=~$//估Kt %絆aHJ.S C>Q\u QXG佐8i傍Ar`X 揣l拊WH`\*0簦"c泡wI,儁歹c t kj甍 冢@(7|穗i=%7U4B\uha;萓X&9w<授n4悍C瓲縮8B|MQ=#煬壜背G\l{JQVxH4/ 0鯵L&\jG`z*>i{Cqs疣H2C'IT0泯Z2- 毫i`>fgxshIHf]L\6轜礦s鮹扠2|pwLleﾍ絏cyy荒OOwO?薫)k$客2菠]aCrA&/#Qe9}[#x喘由_GGR鯣[viTwS,5z映s"If nI[YT枌 y_顱Gl楴BI870[Puqf^_,Q-5碯M5O>q3>H劂76N9-F9hN=Qi扇縵QKT&D眩4exX:fDf$ YIg(+ ?黝~ 1えh+x3聖z?YW燒ww{jU4]}Q#[-(*泝e }渟$7X(,a`翩AL薤2U椽/wgnRjqT少QA瑶證'{仝0g(G 醗P(Bg鈴&xb腿a 0 裕@z[l[zh3 ☆t,~gH惴T癬)<"}繝ReM({BlVNmXk荷l]qV:8[N'z{ХM^ 懌Ug紬kHh^(be&4p= 鑪sK*=y惆 A& 琳圷 休6 CzZ4蓿 I鱠］yy s/2 LV?T 濳5簸擣j  梍涌園^_z:3;>}"$wovn椛hz .9\4"┼)Qr}LMEqQ[\崇pU7酢BP 0 唯Ho "|?-<]I}x諞3)5^CC'1<\WYS6 aZ^:T]衿 ybplx4-姪e;5Qq34^鵐c!kW固蛄y仲Wg 8T1|0s~濡譏M#566拔a~Mn0共C(ypf$?aaY:O栩 >Dk)*Hi\単f'-~ t=0(ZA鍠Sﾋ儷)?L&uFK=uA生靈T袖.;91c; 驤 AH6H/&FEc蘇R`49"4壤 GＷC$=(N'G@ WpgQO彁 ( Yiｙr5_mHy f!燦$≡dDEU&p0I5B[q7h&$gKm0a窰|C 懺^C DZE0гHO-3%w!壘V媾狄C>Ir喟.N]的Im保\/nXGiV穣{lcc{s傷雖+@&X雑ZT肩#^_逶fcn5}Dd酘t]那ldZ瞎0o6Zp,!@2Bv+緩n1ALEq#e3L"">bl'z纐0D!Me>&l]'(oy+c噬~(Ht擬ff1Y.M#7O惘\wqsr惡嶝W岑娑IFF-枋+>^`Vf`8'JΝE喃C0a:!7掲V,;xEPw_rv@}籍粰YBT凾d森,R睿;12Nwk⌒q{鋤o陜5'B.r 1VR摂8sj霑2泙夲5chB42aH>w輜[Wj.ｎ+c G '%rMni鐡2mV$@T範舸UO罕02g /f蛭I<P義exu 国JS#Uo拘m 饉a:L蠧Y進1>"qbn_0窄s-q^ 景YiIM|/X4降] _jf#>-<i93把6 侈,|u'虎0t曼橋?玖4 c<蹊e叮s>^壯/ \維lGDc3耨FPn 7浴%e^m埀#s2d]&v晨nH'v壻Z槲唏H ]="JJ酸4 /tfj\!>>36!P< i腋毆eiMqk& 4 FPihｓ咋wmP2L5*跡貉qXKM +[絖埓5}T赧GWZQ/劭G C鮓0ZXMBo恃W7nbｅP否浅B 蜍<^g!&e篠~`g4Frs#gv砺;Qr>圈⇒PYT:&泳 ZVV|;_Cvh$}{w├z憚@jo*jA8qu;~;綴 鑪-ZcQdSi\`)"q2扛-o\z+`Qgr!+-zxS;mq+Pp{椦wｷ郛2sL_8Fy1`Erp5j*Q%B$k[条unvU<9cf6iUUA蠱@Q@48YLT[d滂2動 xp2Uo$皚%OC韮4沙皓'I赧+~(!+YuS9YEm-Fq|o_AJ整@ ,Y緇v$k&溟GK_ .e 5EBGi/A44 W;B鹹/,usK5Da(?Lだ 走R酸Z) I;kx k2 XYqK(;Qk郡g|EjL!/P#3+繁恥鷽J Bml9!q1O炭a廱rU澀'.4樛Z杁 +cBxe 甸} LwP輝6];児2#^*#s傚dx劣uxUW¨jJ喋\Z xe儻D"Y ├欟#tM|竟C%@>?fyn-兢 `s& EW=馗継衂#4輟G1%&q0cE7ΙycBTf"p$r腥Q籖 1$k2]6^&FdYQku3聘Jk s獎?gS3n前d.脣崗Vl抎m"禰^R咲P亊K.j(=619>Q巫憊S)M,娩Q 8= jE},ug▼m熨覺utL虧7SDJ淬-@.oh1悩=6l笈阯;zSN棟謇幾[iX{ 裹U,kX94M訊5xtd溺憮&j盪-mcYOZnN`檗/yBj沽g|燃dpAo|O j次wT?;2b0IiuV瘢4祀N+];>I帑匂T嶬m箭M鋒"&~AIv+夬@9B.yNE{ s>z塩g|3|+麦5t1Jl-uU, Pqべ90J^Nvo>L|Q04ECrs[落-tgKs0j7& la.uH=4v|Kx1泯fC\ JyU7w/S#%Y &覡0!`4w3\a_r-]%K )黥%-K殫5$ /LHyj!b肯`C*&d x仏^宣6< AU S!硫 .g9J7kVeCj50-dHf薺逮\y巍e&3hFiK^;zO!\\;ZV1B悛R!S)/夛4HV靫受/認'>wτ\<&ALl1:朝#)o.cn培m貢 [19::~y(e.暘'] 75)J 沂~J ( .6荘k7∩>泝\呶iL r~b器織r契;I,K遑Yk時粘9bc谿荅!G?X .dDW斤秘[，xD>o:$瞥#荊謫[麈'}状*)se灌v(ゲV恤VFr肄+b1P∵Kz:5y楳(^]lL},R[l胄b_6`壽 :58X操総p髦嗤MZ 簗$供 Z*(i',蕘c( =坿 z84M0);夸EAMUiBfgI/A梭9o鉄4翅$GM6tﾐ趣s*;{M3t&+"}剌&Y4CS 廸挽Sw#pQ3}F腴碑N$Q;默tp 0-,B'*&f }f\y+}!幵 C 爲7P>Wnj fz (,g_=K[#''~/Ku{j瀾恟Ew#W_aX瑚P聖,?WQ苦畝h}鶉撥yw y鞣Ys}T癶-xEA Ｆa 庖*9H:iC憮討MH*猯Y"誠-4 L^Eb ].|[漲VL鑷Yt3]關Y痍1/hw飃iK戸xa欸N 諤?T `gQ5{{G毀2nbLy*樣hAv.'Wbqjj4=貼.^ KG忱H讓 |X檗!假|,D<U狐q匪墨卅7E708]|`hF}b/Q1> jM M~`M~{=bx^6]\ k#G,I*  =>v襪3vlZtIwA冉HG"7afqI:`5ヤ攝倩EeJX&劫n_Fn= Du^+麦G<0壺LBZes>Tw}kWiPJ<4E;|日cPz+ 譎2{燹弁2]?z .pτD藻3垂Z,ΦZ┌``9vC- Z ,倚 dkEgc升J0SH4a茣/柊JThΦk7揖1i"piD7g.V{[th溲qbNX5E 3SCqWbE聯舐j,SWTsGPx_"PJ5抖S7Jw-狐r2科%I喇[(( w興4H輊=復v D腓kkf彬超aP6}Tw$:[WJ借x dB0f}m]kx 73k.xL{K2 [顋bz鯵![XBC犲顯歓硯1Nj`1cg '2-梓8謚thVKr;) X.O% R/*)2{砌RfF易@Cx[p%vゑPq]zXli拳R?夙QtE|bl%;*9AAqjc仟 Jg85/v舩濂'6q.O熱<"s`t?椢M<匑)^*57LT -p_5忻GFS忍竕1鈞lw#]Y"M簇┿gH梶 Am>塰r櫑Zjr3側IhJ$"CW, |]新{6%絣^d産6ru鍍IBW7ユf 4zl\'a&!A'M)縵蹈Vx銖aF dMJb^{rLG｢Kb柩Q< ve):yq提p上)r个M(瑤=cm H hn0} 2Ih粉kK痃|\A言vg 軍 vK缸 §&= 7>2檢7ΘZcXI#vd'独4g|AV.oD/畊K^戻Ir`Q]^ @|淋V@Jei'釁:最U =zAI*0YRfm竦s>V 調I.jyYsxoF$)&8xb)^%PEd;]9iZ<E个]IoToglx/Phm\歉Q9u":N柚跚延fCpﾉDY僖犀\$[箘NP魘鼇Mu孵嚏9A鱠経沿禹~R侑R立 洽nppI>Cx襭Q`rΡe埆q+蘖70+憬!X^籤M(dY侯!IAZYI9謎p亅K^q$1\z吩W_佻葩$}懾EPP`6Pd‐a0)&M7pnzI契M8nUQQ,zLT"$_yﾙ 附 =\V粛倪5忝rH以亭?rTGX~zEuobe疽葯りQ筮滅oO(9:9>LG'Onq^P: t -\3-/;_Z?Kc#@6pΥ_P.]A梏;+>濔d/灌1&4e阨6^ 5la {Ij3裳!AYo晩cR&1Qs3 $cI.T P槨0駛憶k p\@2(C D,x軟9k !- |[O嵌o>M'醫U]: )V恍gu[o`隠`繽Y 33M慫5/捷eF)諄y髱KQ6=\壗M雰"j2M陥 謝\-譲9e"籠XB lａCD配s巨b枴CPTOAB!Hww孵厨騾=7(=tsAV~5K]8漿xЁ EI`\ |~;?2tT\a0`Nur;萋槻@:G%lBxVU 37v蜚擇jН牴ul:0Wy;5 O!朧5hO ti凶ocvu=3Loﾅ衾3陳,~kq`^CFkXX.}Z6Ez院u鏑k a.刪X 椏 QFzn轜;'Q 雁研 ~M署{8W^脳NITTu塔 =5~|~y>B得zc幼@/dT`>3fJBSo擡$c@2鰺莱WE綸&E"-564p(=\cO.O~)5#~帆C}-疫6djG?gj-H5CXa餘{跡Tv"25_-t\bG:#O~寿:=Mo'容|^Dw渟nKsヌY殍 j犇鷺;RSi邀┴{Bh#e策F#)鴪&am遯Iw-Е3P-&g緑XイyF%q)(, +#=L{H.I,>p2=仇1經0"{[>$-MC齧牟je]釘wcuBDR`/7<;|b ?0夘Um棋U┼sD?"e8y壑*怕Ｄ<処i賊IsaxMjqrPla^* ]3!]Ke?b莽WD隙ミ_汰H舐*k?佯or瞑T=宴b"ou%OJ駐,∽/|e埆rt佻){l {吉C躪my+cF HaO;寝骨侶=奎0_Kl獻 p 5'ЕNO#Dky?BElA+\[bo'2rNz_[v lNﾞb 6厶EDBH'IsZ"`)!'J8巉9t扣 v琉k#疂>ci9膜 x+V帛H> rQ:錦'JLjk{ y民馼SV)KqK.a]8i~{ `8$K_w?*|T|!&亠 :JBu蝌Fa=Z瑰瀦燵g>$0/]D<fBMm "(01J`孫圍%S#%@p9牘dHA腰Ls*zcSJvFMI2罎.齣$--熹AqpD>3S3贊R@R漕0I麒} S(I7wBM}^0S芚g(3tb#KRhI_磐t禳蓁ha4 ｇ@I[呆潰G美-Ob暈7T fE&P< ^上=+C糊 .粟Q 餬[d5QBD?v IDT$圍説a~l5>8菟Ss[缸!"`皃Q鞦(抱0Rp9 oc0工?靈.Dhh至m}25vBWKyC pb笈V募z,X Yq瀞J瞋Tl8BK\？r ┠妛>腆b%噛zHASiFIJ)!鏖*o笋si&3J相u_l@-pgSl:O AcIVw:wt廸R&%z\{xQ鍼型nM >)gs |u5頤@磽 |;~f5)Io\!棺Qj灑覽6Ce{5.爨8^r,>∞秒D p4Hrb <4n碗x侃? hSC#v:uts}档nW|x.t<*Ｖa>n(Q疇MdoE9TS~T@R!R衆h7wW7贐9g幼1哢FGw .ほ:V!a^Vo陷Fun霹mgRi>a6"=0]奏遣G絨}剤fb瓠K;_SGDt@+1Ipp淒o2{/腕Q : =撃至O:]K2fRW峺f=< W範/珱6sfB e1q2豎LE_而 zX';;{ n_ﾟ * x9Fp救!OrcAw d* t;esuFS!"ZH 更&5騫 ′f>暹枚 糀椅j.D籾=[x!6DSD;w [腺筒汳fy?F8馴斎虞vx靂cw';莢 wN^U^R&P qQB+腺侵6{K割[a6~W傲_rW9l埼[r消~鶏|j;r=e%+ЭY?拮'o.Kv-/}4JJ<榔 慈Y#tT+縟5*O*E廢3粂慰m悾v2=掫冲]#n\鬱ku弃寞_kOWw=uuWGoQg|褌|jquw証UY=‐RXu|g|u刑覿[ WwV?:k}?"HuOU|幻JZ \jPv6,7bCp]g QQy%9uK-Bw5 /|劉06Ri]垠SX*&9q痢ci)p'@Y`u抓C}i#0B1My簸 b~\心/ nFda.It遊f戈@6<u1"C4婦m覆値DG&2cc孵.Vj悃?Z螫所楼s3χsLy豸zzv}OAQ焉oO啄Z櫂蹼[颪$*ZZ-'Ov;PW~該鴃┸zk:膀剳ｪ色銓W萱jS_暼慙 5N#<鄂阿r突A"i羇l燔^ltLNrX瓢黼{n g濱羯巉?tr}X-qHBSQQRa>._$-\偸J狗S)oX|\B狂NK7W_(筧2u柩a4 JXU+csXtmE6躪4-WngUdG :合qW xWTfQS&4粟6P\W99 hA14/U逝軆HP6"咸 阿* $培Y#'UZb 平T>'f圖@UrkEOk^E $Na"竊咬惇勞nNF_QU懍{cLn5oN.Z!Vj;KSd尅C@i〓翻$%,vA^Ak售B例d%頽&uH}S/rN]zRGq錺C CD\>)c*介[n_sT盞_mcAM滬d脈#淵d8-肺f"0樮>>f6鎹壤,湎:1x7ufbt08#s&洸*~F<[H ]曰)畠;)%-q9uしSS瞼焜A8\]T2\瞼"34<抓%TdzU#R]Nn扇p勗]r諧轡$Fz4OI5sqy G &T_tI>P@6Itns氣rX{FD名 J龜;u嗅52弔(v#~gZ:鑷'q裳8@T}悋駒廨yv插9taG悠6僣ﾛ,t呵1eKQ<2J-\4#轣1j I;-t*njH裼 X襴-fZ畦/fn._eS覗w纓OP '雉uK@uQWj7^7UBWG刀3/TVAUgS2D乂iD'渓 j\e:h α姓9`Mp1@2d9髪}A富&Z#K,冂YEMe3%箟窖ovJf S娵V.=s靂1:剖ゾ 褊 巉^,]h2щb柬k*uAWb奉rL筱Al腴莠hx孜-H:j罸(o旛bゆ]鰆o働1FSnf]=Xy}'*粟.1P簣墾Qs毫欖W>X()V8 QK幅fJ?Ef慷@K* GFズJ=Y+Wi5G蹄D-W! M 0含Rfa\>wU掀H M3缸h6++Kt"祈^]c煦`檮磨9鳩b卒h打環ﾖまrQ~裄3r)!y- a$埖村,o戮*BZwD"x'GSa.p}A-Q~zLαP0( 6&:v::?M椡蝌4w+Jy2VRU6+<{,4矼ZU_` )離{＊.窩ZGa鏘"Z皿z盂86懺.~D戸]zYm扠\ 魎q〆Wm∝ E~ J ;笥.壘t]i%様i'O+%F?f)ht=(JP^kz{\ぴR,@生~}E4NC.}"h/@N?ゅ 8藏)<⌒ gftbFpsD榱G =?PHgヰ,測TPG-2C$蓿et\ct 櫺S蔵p'*+X夫i躪.H+'u9@ r逅R淰Lh拒u:7h7馴@a2#xEf 纓~{(H,1,)p8PrZ B淪X裃{YFo0壤pT_肓N#}榻蒙txF!KqB"hu^=` V|]\a2[r` !8dh# th'{>掲。\kX 癖M} $U3ss6\HKII靈 U=庚L<" DW_4BF C^1蘓1%2瓣H 遡5GLi6}醢::e-h(4堤c^滌r鬮lT<8；bZIe)L&林r a6cBu鍋3 復|) .跨Ebe毯j2P朧$俳d$"Wk|d0#_=muf靹9Z&l`憲 気 %HZLmmU]6P戦 5crA Z%}!d悦Z#5jChwdz:侫鉚囲n 吐& :WB卆!<'#.{蠣r6碎流d/qv=臂邑bFTLNen質NNO與/y艨J>z鳳fm(.籔8ﾛAU5:f).E-x?"V4rZO:gP[A4ZDx *-ぎ]祉-i x]K娘S)#~r~)uv/n@{K}],mW{喋2'oKnT&鏈3 H|}u6=D朶(┻R`弌TBH|U┥[O\{z汕 tYTusy\[|d i6d Zt(X (享r:3gZNＧ解KNgA醍燬抄%`覺+(5r$~炙l癜b歃3+,% Lk滬?1[駲髑SoZ:P?紊R^:rn2(SIOd09<{驫蘇iSQuJ恵a Ky8{/6:稟*ym旁lx銚9+XPo:頴 甃QV2yS-#l9=:\\T[轄eSg&n <(E(26a兢H*o&9L 3音 :}4=RM `:|0fY lPCl+ePN6qC爼e"%hwa籤娵 灯+禎@絅74` y#PAFIО巌Bysq據lrUz_F|g^. '送P=饐調 kiA.;ooA;(+)zk6 ^-/)SgT|9 p@+"#f/ !6\+惇F.1dg$F葵K N1!K育P%*"護僣瓲Q=?|80|3~兆 j>q&_,^xI {YB励c{|h籃TYMF_砿yo頤nCUeUK蘖6[$鳰e $T=7疹>初'o'jb4A {b-5O \0XX @9Y k: d]*脚WSmmj16"R~nb踟"/0bZ|}B3c_ 蠡+SfKx配De%IE鴣 B10b=JSc葮W {47自森j^!zskta1@~bWS3+YA3屠(湃;j僞@I旺hz懽v0JEm 1%vm.yL 鉉/u(QEf`~"pt9!cp%$I區涜徭洵1J[{&[MY恃奚 m4uGj2?-zN"g尨OczM瞑P M} 硼6J|栃~EK'$-*t2n=e々A*AｨngLC~T-:e!?89=% J)4O^L樶P cO;Mb9[ @Yro~@轎 j54l随n; 討RVD髯\遍wXSzll訃2 4,#sB壼U4sMr7"剥g芹}後VCJ邱濱f.o])繹aSckOmL擧ア|['*is0ISnj)O敬,伺k7,壺 zE嚮晁5K-%S2恤},%緤(杙RwP+% 驛IE冖Akz乗r薬v~*sﾈy}E含XCa#*#MX刪 o低?`o寖fCoH 朽$#_C蔵I匈o3靨Z寧 >CsfGg-;.5蘢m脂F樽(>ZFZn Xu'JFC `Kjjoc,卆緋葢nwIT(q.┻;Vl孑j1(9OJ瑜E J[佚t9k紊B[(%:KTjc;HK逆娘YGjyE9[vx] 箜xL>W9ィpZ繆(J苒| *蓍ZX" o7Rh枦Dm cUqa^i│BK# 斂bn^?ZaSr*鎌*&rQRq倭 ] 9岌;BsN3C洵&`奄gY=3+謹7JQヘh鸛酊H]rCUVw/Y1祇e ]9嚴Pqn1N^.B6!滋;鎮:泥 5[螺sy.8p喃vo[b@+:!0a訛;ACQ! K尉G9価 0X''{渠WMr 粛-6_}u-t 褪3断棺9F{V厖 HKMj/Pn媚gk嘛x 'g U[~ *熨 Z 涕噸滋五 &\Ha1俚WZXV'9SZ~*hfHfn]*v,蜃M獺@S蛮1s}j替1$倪 Q$Er L)5斌同4三[LA(*好aMKtC<1y愴 $RQ欝r齷KL主eV>迴eS!偸ｩSNg苹Kw艶=券~N1{県潅u$y%'e呀CL,?慥D^U閇彦襞吼" P縦:#"lgar|u$Uo&全,U鐃 u救f4Q#b&_,差9=δG鷭:E p5QV{6>]?CNXB#葦晁夲;罰體沽議[>|p?Dm豪b矍~Bta'%(ｩ謾鷙|Fu( `$ 4 UIISWo7濳絆q3寰ed]@0Cw沒={蒐!9e4/PES1k5`FI;ys7~!H,攀Ds W瓔WDJ/;5=5楓過瞞||7>^Wп4歪IlrU熬霤=@@8慝+農ul^ * VG;@栖稲鏡Fョ U!~輦mK煌P獎瓣剔F\OD_S8{q\@"O_-%檀xAC|?>rM#O栩Uo陏厭9!utphdfBRCE{L 烹n囃#~q G_ 濡h0C磽3О^o3&n j3噌HUP~FGjAg繚tO!JM羅^x起0`t呼sHb`k>簒簫{G娘季;G)!B~彭]JaQe､)U燠憚&y)9(Hnw城vecN8V3さ@z_u3K:乾=&dt徒 Qy`顔`r\著aL/C\-Nwn``t]~"$Y矮挺 >(猖Y\撰8*0XAIb!oS!$ 塚粗牒9N#0Mi%N O b+0XuVV3*R{{A81>3挾ILLm|h"m+:}^紵q舞W UdS訃tM粃Nr/t$; _wk麸dFL<<`3 孃#?- ;埆22Tw)堡*_蘇鯛喚 Y<0TqT*;t*`O[b~2 $6'髏#7亂劔\LZefs嘸 騎2沙 =2削j疲"Y z}牋成砕nH起\Kd鰓ldrz)la"Pke鶏!ODW芥c$U|葭2*pPp`7D*渠U1u/'!m(|刃n佰t! ]a?霤S賞蜊dth:Dj"壥髱yn匡/Ji*9uC=lH4c|kEJ"公1H%!-g@2b 倒y2P%&&奘&EH鮑):v@SV娯跏@qP R俤m 縄0m8M浚p-HY攤�#QRoi!jvO3b6488L招険 &,94M8sn橇"o]饑 mＵ富┯% }+ Q露adN6_\">財O痒r>VpS^u飭}({6Dy v積賞M6]艇2U感; >鴒/?8nO`0:8 `Uf qGDFC2=口?l>◯F啖qy梅商%菫>W,掃627A# )eEjQ`'YMfrkn葷'@, -e+BC3e~>d"DT TFxk <@殕wb4;炳o\p;h饑2R jU憤FL.SF祁``*F`裄T萱l4@i;P5召fLp*;Ti%刹a27J又襞E"┓>活C 悵V路x虫lA'斎-~c D^KqE縫PM:(/8#3c`+p 9P-像*a棺|WAJ6ddecl)0>8栫袿y{}扶{ O偽jLD [*享]7$8pHTh畴H! ?=4Qo{p\YZBX└忻港,s2寇`E A %衍-#K[d丈}iFF'%g9BD\(lwmZ\Tq6岷Xg甼 ]j ３ 晞mA,1aPD京6д4[舷IY〕7悩|$ Xrl }q\O 5:>"T_ q栃磆j`勁\]x! 偕z-GMS朕靄鋩V%瀋本G[(X%FarDA尿r筰YaQv>\F"Κ]GBIkaIU,欽|蔟xz茖\HjZRaL!Fgl梓\d{Y烹瞻 mc皓溺I懦 ~翆Q2tD,故 GPW~絆jC7試Lb*An#in;u尽濁K/]G1 na5&0徐>kdPNmH倣Jx!HcJuZ/整Ol aZ,f+rcz#?[`6芒Xv甸B[YBNo>Lb_xiﾊE佼,0\A8\o擯Xp K8(L<rtCKKt/嚮Jq?蛍v{Eh$RQ畊z厂 `~Ofsx?d歡 ("?AY妨a+.2蹟[oKW停(@$#h凛8L?~jY^\`[DO[tAB 玉&Zf5Θ,BC瀑Gu)!Ae;$c辿3UL倨$qK9\讎 dv5痊臈r鈍rQb摂GW=飄x色=J~^q吶wi_e4g;繃&;顯6UNP>@b8au+H =hmLS寤YTM"塋s纈c3 /i^G視\蓴""`0n!U%N%候3脹uxD@RcK書1⊂_HtGRwNDY癘雎3EX-z攪k&vvWph@w}万咒o ( 葵p_陞葵靂笥槌)f逆,fsX第0;鰻O+,*F>Z\Q鐺厨鑪k d*CE溶h@c\%TAl;啻拘亙莊 !p]k[_晟袈mn$滑2]爍 r3'? v&o(e_e売tG;[禪Vg6lz^)tc/\F6KNui"1u壷> 壼GvW0RB4u[]@l2吠*偽aQd D 深{`6K矚S襷;礒CVRO慳*僚a暾K;？雋攬8\審V副4OQtJ#cU>穏/h-EjV\t{ku6!?QnY\!サ跫25)UJ籬z鮪[傾bU VYt*BpaP *妥BT濁<OE+岔勗HM暖１)} (*M2IRBW!7"肘1H|$sz .L島4P'P/gTtﾆ 擇"L  #/b‰e冫R朴$鉐詁 y.王長" 9\U]g?P1*9ィxﾀA`ヨXb詣UQ裲 濫$ Z>+.=蠑bx乾 &u6j@M粟E{K Wm{@} >顳4U':S莫FN4慊陵%`?6運56QB-g忰'_)Wf9rgNWt1A~H"?<弖|fi19^P(u帝蟹5顰O:T5(/{aE@/xi_b袁9U`骰2wm0=@?;!!>NLM7U|^╂ BXVΧD.衡 SAH# d桓->r-D6v~潔Q:uGC髢jq)~}{Stq U 糠Bhv4]2r` 鎹馼T?O*Gah6践BEPVJeEU決7_3M娑EGI:Q廷Qn 塩Z?Vr氣vNe釿Y3(J(J$后 D捩J鋳5(Xo♭桃鮹\卻G鶉楯YN-o蹟!O 2Z朸 WA乾kM暖PLR-戦ePqo辿爽oヱ驗瀋r兌KiNKJAL秒0堆S:zkGZWg(!BI削け浮死[2vbFO + `6f9臥F6QEpw=W/1ご%( Z；b  sy0@N2 F履JgC蜚D繭H:'q~恙&i/掏:Hz 塋 gl捕機O穀斷fj+Nn@5苴⇒eS?課/r塹v漕6G8L)尻I2"p*=\byfoj`, SQ`[l ｵS`Af36肅oU鐐&*H舜{)Gq黒мR.7{o$fBMqxajid?qVi閑e萎.cJ/+ rg齋WuM＃1l|OIOMz-E@apsViIbE.orｆ^cW糠 wU還p暗r函H+@mBハh伯amc?j矇8柯q\mAUQgM|岌宥$4~=聢スA,ギ右yjHyk箝藉浩hutU蓍ahSJh<悟V .&3`邱 據殞H}`砧ζKwC=U丹殺84搓6幽OZzb廾hY礼;'R.B`7/qN?hz粟:癖xK^ 4:I *聞疝絶 吾YPq 8K]\ 蘿軒]]渦V] /+ 廏L8MH@<''/R: +?k/4|幻]F{`sJr  爭薗~ FC!!$@ 6-4o2zIDV6yE+1冽 C3zgLZMmQ啝? ^ﾘI%耙c噬襠;`mN,tvv?';M檻*j鞁Wt4朦[gqrIWLqb'I匱9a(c$畢~5P3FR98!e鮃 T鏤霜H曷F 湫憔fA馼善i</R ,Z <|6:Ymyg~”b;ili1颱5,懴 $# 9粉}#o台(D ♪ *`1＜ n]x悄苣A胞fuc6k @棣＜k!!j1@D* =k[@i,/ ^P~f>z%Hｅh:椋 y_料炉lT-c7X碩C*JR駑_4 u*gt 商_葦rAVm9卆(∫厳怜~倉u霆nボzQN <idv膂保n=_Gn-=NO*}\J*j緑z佑y|j[pw/K;UH炬ZfK~sBw.oP8耒n岼_#[果s+柳KrL<`f丱埓tA<5*T8c~My褒vaB-BUEEn mj宛=[ED<鮟;: Hx( !4L^冀7孱0>00$D5/ N7G端PP禄羸mM.KoFa幢稍ijZ }EgiIM._$9%損算;視WuY跫b和K9\k=函6傲Bm(aj.ob]~*E@km+'-&H O8 ;da4b|jz靨DNcT8禿5%*VFC債鰊咤l({|犠u6kY律7%R 輯n\b駈.kNXo鼡h{-蝉@u]挟(of錣\Z*ZAV#0P*ERB'v低i0呀PZ=O[;x]+b' 甞>FGYLm&4S|FPFt-]E:}厠{xm&t>ф@>>l~2^"G".u頭D弓dmy[伴s岱瀦句w IN ~lP=vJ$Ocr|S岳~劫凖r I([6csy唔ulcH;xOxGE侭{'{#斈yu.zSN仔巉穣6=査k庶zp*WwWG揖=,勒蟄xqnEJRt\';w麸}WrZg.R'澤Wy瞠觜VwS/?袁gD9厨5z+x x巎)IosN88~_RﾜO7|ox恆`ut_z鞋@]6J?">E罫mｫ?徨轗◯}hnu毳h_=z{_躪W7 O鑽軛1j4v[閔産 NOVx1顳}霎p9gW/(X}X=∈nuEzЩNit-降Z?Zo]`掟s'MO飲_-i昆抽nSvS]l{嚥OTz嚥$^w} hzm》nP6a0柁T+ W%y{椁X憩g栄 貽].xSO|+8N葯BC暾F&h躊:,v舌K]aH\A吼nB>∠r狢&CWVO8b~*E+ZMk24)c3*dM|z+,Ygm孛Oz`)V5[E8 j [[K隙Tzc]@罫43LnrcH+<ｉ黏^8~HZ8]HX<{.祕+謗;@h雉礪J v迚6井|0nﾃRN6DRIEyww涅 ^Yl&8L!eY溟OC[QOZ=v& S[按 犂'犂M7[LEc`鵄杉)慣氈>w蘖[=W祝_醜箝渣w[鋩曰oP|Yc5D諛5<u丙*S讒2j6?mC5愎naGu3Hcnk5鬱z蟯1ev#畝壗+Y-Y?+[,1w紜;WnKwwvnQ=UE蹉2渮指杖KQ|82C,*[U 解X* .溥%ck掻1elEd忱"ｲfbF箆t弖壌NQX1N:s Z_0N摎\ "w甎| /A43L7-##芙Dy)y錻V瓢効g漲)x苧堤nMt5gq=Rﾅn-5/Zm淀_痩Tfpxx/ej(':V.2n/D$O材斈=k6 裾'D3Q)ehFz5b'8K洗oN FiFubr|(555\\m#oul,+6@p[ys:a&犠H&b:T 6^l4*{G6dF鯖qOpi`\d?P?|0?7]H)轌\鋏驅x YliUBX#K!jF#K"W[@/'鴟F",3D菜u*p:國譜VVS.q['晩Wloq,|UaSj$j瘍〃a%%洙-M?q6'' 劑 劇N3B5,傀*Hw&6c 薮#N0S{ 'IpsL 5b.舌WjF戉O慫 -v.UfQ{ v鐵S>oN#V[oHs搖K"鮗MWCO^A| 84!)k\xi%献 {$Ep 消6S$*G'* 栫pzoVxcK性>?CJU(e虻Lu吊E8&j(SS`Q<僻:eZqo*6prB]w )D[i Fz|z*cO/瑶葭効+ｃk 牌 IbW+4s75Fjj{^溪Qn );" W@[\^Y譱GKFD濮%p\MZt NQ\iE2v垉Y諡>岸@嶇BOC髄;:x!K歎6填W|'>luuP預W=Bf/蒋XL08yPgv Gey[藹dw]wD;( J ｃ dq気KK%br UZ奴[りrrZ|o県el(泳A9爛?UhN=宵裴晒pV>u3W\Г廓c]狡hc.\vCi8縲茵7R^L[#g:9fX(?%=;パb椹y}gB修睥;I!vUy/Lg;54[f$冩瞥*d%G!i3臓{e瞻6巉遍b齋>シ da?N 剖 Oprs霸7r]A兆FV` v|D}f中r亟9庠 杼|Z÷塗q痰h韲N訂3!a;=狐vk錦}尾c+pWCD9k!d<3鷦g0[17rr:&3逢#H=>盻&t4l!泯MH*<_K笙T)縷"2g#m t]`-_埓+簍">"x"冫9 n$&0`1t\$!淆6t1QM:'呵黐`榿司b$MOY痞荳Gtv:|慾p慾隲 怨C>n筮C曝p O涵zP}Jd@whDq攅Kn*况雌y`' <*げG4 n4C聒Dllg'WaemkY z%Jlp]"f祗ﾄ@p}&eQ9,坎D%7^{b?u*=MTｦ"fzgb-OiJ<,L鷺A*:#XR“媽!9r9ズ6吊Sd溟弑芝|o.X:m!5fEM岬=R實y X8喫广k|z$!\qLaJqRT0D`科I虜辺& w蠑?懶lH憂輒WG=NreHRAAKN]Q踵nl-uJZ8!Xp^{祚6Cm=^^txqm4\硅'>E1r擁jl蒟@=M!Ir4<$T盒(]浴)N{先袱箭=61Bmyxh 4mF's "p o^歃7 /vg蝿7@t劉. 5|只@B`ux渚涸'F_s箒灣Qygs= ;rT確bh G嬋Mj{$^q潔曖 zX0Fh)ht*f6iRhw~x 窯>pHe bc/q*鈎Z_8NQJS%儡H 4Sr ,WL4捕ΛJ"(入v1|V@v澗UOI*魁54xH [^9J}Aeu zQ<“Kb"?z哩cXC潺H/U勲r|xe龠rbT,!V凰TWwPFxm#断 (片i >晶zVZ奴q99oE 我U VXMT vj僑庄ねP閭$R{g}扛(HkT ;]lsd鰭.f*u+ +奏#\=~j.x&異6麥+奬 >Wxz?=>9BHoF+!ASb#;m冩8ej]1: ~i#2Vi| l\^rK6RS桜\凵~`#^QO袮貪 冢& └臻 ,c j!|}揩 5^lhDNO勒>謂\A@抱1,@眤a侏搨耋 c睇戉)4<3拈@G)J)]yyKg霞f禦!||r|jyFk;'d/H\6@bkCe橇`i <=萄 pZ]51謹 3|#B^^zumI gc無.6m"R$m ﾕOb` t*4462gm崎p~ 追w !]Nw>槊EJVaz{"4GJ??*z* {] &"m{ hS!w=G4仗fゥ/'>諭彌拘u:MGwWGＭX|v?+,suc4x#E詫?KOnLPk#楊 [dcq4$}FQn網[c&in.Mh;E"Cs6?!ZgfB碯-|豎&F'?tw`ZEp8!%t4m&繞|W%Tx稈ULhο^ M'- [\薮[沱tD貌鶏k与(\EX.m`q顋臀Q_A^LGt/H[Zセ~_I杰n覈o}nX統7yj=耿茯$HDnFcU"岶gエ讃*t尹z8僂yL 瞥佰]_H狡<( L[3fW(cI琳弟`S^*qrVJ5裃s4_)jBL酸X["c6< N=iC膿R9志~e$U賭$$|YHK Sz$_n５Ga0.う3c噬~68=>F猶奸凶^a$Ta*Wp\n7oXLd`Js~y艶W` ps)?y7_f"画FyPY\ 0完^L膏 abh <厶Y4鴟&V&4;煎/kFz┠廈VU "F"游Cd){鵬V- Lg!iro~~ﾙp)Uws鯱:iw CS*RY[,茖4XJpqT曚&3>吾I7ovni}Cj八T_<掎d^nL6h 1ON~BR?!晄~aoL翫XZv~董/n~&@槙%3IdNUl:VZh+胴UBC /!S鬚>扈L%KM倪%H+v疳*y"橋G撮^\1l佃E５儷p裙-@Y]F"ly:芻埴8<~)低 1S$]\8+i_mN|R_b~I 咋Q[g=B&)rL $xv:Uw}-f> @aZT$|;(Q,>I}H_-,VzPfnX珥#集亰R>Jd08鯰T#膝/-)']wfa厶=!厶j 縊hXD{#=狐|限0FbNg>7}^f萃蒙Ti){菱 $i V|νQZcDCNJ U6"f贊*n藥MVh!礫j浜Wa挽k7簓篇VyrhD2Yq1X8Qu1Dm||JI,柮軸gbGmOxq|]:躁ﾞ蟄n m講P鼻~沛^u~ i.Cs|3形カ`R柧nb吾~崛度=PRvmO/7T1,ＬiWn&匆/ ~h彫_wC1E[kb,N{lRZ眈wQらF臬所^1H/(b礇‥J望(貭.｀ 鵯cЧF釈aEj f`ZR8盞P-IA纈戈wUd+^YTORLD1呂IF鷓[9\ 儁a=d~C6^r藪Pdl@vv_鉐L遨TwQRι!0I\}Oq9lDh#-L8ci=k@IbHf讌鈿e!?Lv?掏7毟wsO昜04V^P>Gh8?l'A[Wm}題 p愾ak重S;]}< -){xd|s/2u!+ぽ387rVeO Vqd`-W\泄]ZwMＦ) 4*J`%.陂 瞼鹸zw=Y Wv譫E|W'TAc塹AIZ膈c]$I*效_ 4kW泱e渣`/3*QjKB 3'^r檠47 k8B]Y=r 5M:檐ぞhuカdaHZ:1ozF' B瀟Esd0殿^器8!!孥7:tBq'~C CmK6hxS1lU Ottc衢VK聲2E3/JEq荳俔齷d;Kwn #椙q瞥g労薬0d'?cm勇箝nр6z雰W夭c'a_Mo滬5葺x] |s靱#X劬ia團\vjc,C@q0lV~>m/(淮 ]>[5鯰 N゛xq3/提q2-qP]Qyz.G獨\,蜑X//>^2 JGUfnp>X翩Pf輓_TLp%d616(Y zzGIV{8豆Qdt7フiZR{psﾖ9x栫 鎭SRyl a17jpB8aJ7B/.騨鮹`^#:.喬8竡叮]笥霜`M -fjp"3: cK&1.BVMl 纉髄\舩! ∽7$75 逑]D　&資{b=Q T8$lwj?!6d}l~R6藥 *(oE;協塀与up`>會N\"~鬢播?jTUBG呵e胞xy跌屡=惶5adi^T[城@燒姿｀H^威'正f 3窃?zK亳pB#}wSgT8DVC竚 F3川Z$ t2ko9q[洋V1&NiW&f\YggXC"3Zpv共 B0X^#%tRWkq^e主S菷wN(Zfズm`4"颪BVz:O謳 裼~m6U4#9P(A%,>1VhカC>i穀Eｄ2la=j+r 隠!縞kw擾T`Z鹽VJF[TfW_.;(@ン =?M`)D[I豈OH^'勸'P-D患H}VP gZ%1IHgw+\扛v/KO!uh潮[lCV<8BM ]28 Ls擬WcSKg3演Bс函vl~=4\涅* 馥oX^似閂9D瘻<幻$殻n T弩zk+Y<7PxEr5^*_[ブY Mx/廸扉)艷V PWQ汐-T8! 3MAe+9h1鵜l嫐0a殃s+触勇wfezW皰城mg灑`*(IF.u1\驂a桿edjMx爨m5b1TIz秣' v+)a伺到L{N牋V崢AD99`hq$VgP蒙{=9*毛x_m]A据腿DpG薐_@圸*蝋Lg# 7"{UｧNxa/hV=ZYTo$4曼u)戦*貎名qF !嶄*h鞫1)J`QﾉUaF9#I -!副Y3_DVV)bN>n?||jﾛ毫k#YG眤;零4q ｰeB*32,o簍jo真M*e[m鴪&`J8$G5>cHYMJ+#ihPai,箋]#z4褫蛞暎与1(Q4q@f趺 {R.lYwu,)c暫 SXM粃&q X拈1 =Z]△PU #譖ぺ}Tq>キ6?qw↓D嵎7~u#*% X|謇gw9wyW^b歩 虎菜醢$g~RyG:mT;0I訥A蝟QNq>8{|df.kOMK::k=3%>8j%hoD^范`榕_C@=五勒D断^qSZh蝕襯*_e側 CoD|bU8QR8)旅妙*B貳舒I+-/.MT鬪C1j|.#xQ~鎌7B,Uh[5 kkJgwn hs_'.Eg$`襾5Ox( t1 [Q2 >B:D/h>V``+R悦|斫Xh\v讃椀空sQ 9mNpG回D8wLJ鷲7ERo猪w(<=8^6B~有ck%6Va(^Q>;咯對|扮?|溯zz/澎p5審=y99k&田)y=滿愆Sc仂>hz~;LwhL獲倣R?jz^3!F望 w/;g7O}T苅]V3| ~擇NU帖G沙眺=?-K",vCVl o荐N 轂JUn量O$='Y D`?m%uj表t/\C ^暈喊&9 紺,w ORKZ燎_`,碚*U志}x窿獸/`┛u)愾疋G3sA de>p~7qX 禿r橡h|瘴x\]慘.UU_x4x弧V[{YZ!X=\(?wﾚD搬_oW {S昵サEo7/蕚eN誤l侈DhcmxDx輻[酌召9vqtASS0e>i鮹9(5PB私RKモ尓lo錮RJkVJ%;w"Kk{椦;El^圭置]獰bG=鶚Gn@$~%|場@Y錫'N'U鴪;пo/}B5辷r噛>(Z呰@YIGj\I6OFFd63fHucW僥'A澣;瓧QFax3R&#Y >- or畍:台H+'|cD { o)褊=*ﾔ勇7BmuN*6D; uwos,圓##童07碗R-yi%gpG旦zB/#聆9%-Z9閃ЩenVHbgn#例Oy9>U.'E9}xn触Zx々[o'6Eo( (.&H8 =e3嶬縊Ν#謖RezZ5|awJwOxfg1顱Ix)as羮6bX;'C遑%{z楢6c葱c3t］B\4V&o潁;=?2u#6n+,裂抒禿:癌Bt 'y=b糂J<&@5dfreH\8#=a+Zr&8qiYXY v1み y0臆bb/^cN`07<SZCpI{t$諤反5花">5翦?3&U[+^B9(幔凹Z!C91807Fl}V[ - $s+,="船5C t_離鞋3dZ?C|>ea )F档9J*=,f qW俺 NY5wuQ嗽奘<= 5:o DvAtbw-bo,<z,L麕+U?B(.^Kfk濠@ ]Sナy@=!RG賽D=叮賁@HdnN s隕E V:!ｱ皹感lvRiS5M3Y敦d=+-\ol7|L\O&*VZpW3J27 K誼e^><><\]埃 @xy"b刃aJ IMmH写[{VHYp戝薜Eュ ,{g{窩占J墮'24tnBDh譁O也0*Q鞐`/ !涙O|PNl9*;愡X^_:RIe`鐘2ski V? Et1i文)m齲)肴悄b裄SаDG+dK麺鰔>A!mHc;Jb頻 uV7qz鉋H@_Z-f L.le vf ">hF喨F鄒Ray7a沓 6! J饑;/y6R{T餉xFV利h'灌昊yy淨_Qdo}bx畫T凪 =0bK 扈寿s杖=~熄o,#a76\0$03脾3C2麻$  xZ>}E$范蛞興(Fx髟?E^絞\°5GnH8%GgB嗜.XU){TM禮盜[腱#P欝@u (&f` QlA徽 wvQ焚埠7Q徂.YK>KT 票嬶qGK"劣9"7Wp_ ttZU棠HXQxU36i)f覬曾D譎!Zb<'tSXl#NF,M`&2莊a#@HIl-K Dww>Pr嚀%W(%点/n2LD'裳Z}^翅jOt=U:w`o 'mh懆振~F駝pcN/S5#%'"鰹V8h5烱T捉I植纔T揃O7~A!φ ET4`C!&[8YME/b2寺/4 k:eL旺Zh 懺誑/kE決Wa}=+葺%埠`a滝4碼8&&Lkt尺陟hs`wmi0UU]Ov牀聒`V 茜deR2ROi7RnW撞嶋\懿;'$未 哨T:p5&uqDy/c4i:腥il蜊MJ&bウ7.阻感 2a9S＄iI昔R_5dtpR"DtYNDqt1/NsP. r?U脱IPNk~r,v賊hb H1穿翠詠耋FUdG{HFO !MrFBhO\OcW晃QG詁]6zG岬5止|髟H 2; e5F畳?[>屈PB英+> aF檜滋聟(n'禳N5)@T 可=街躔hSaｗ贓戛?{2+ c*F嚼--1{暇A|}[竡rI叱鷽p磋lAATH\◇U散^H!in樶rqzN;x\裟P9k邦p ゐX_[散}:Z儖ZR:<昏c蹄814h}s>gGY<暘W%5S0綫|yep:{只區q禺;贅O w畴}O+絣,v j亙X2氓cJ`1dNG$Ycr5s1+:C|睦u hto5+ve]l`! 逎m_f}+ }U咬l_/ArX禹G抂t地I4 !6+z1dab柏< Mb^vi~憮CU(U" tH薇V瘢|VQYNRX N陰駿l_端7=g泳_6脾s.>j悦h:0PV /9m6p拳h'm,D Mkw'Z\zZb:F{o>'RKiOX*絲N>%F;b2｢儘x+a?faub_M}QnmRd m(\*囘GJY娉{YQ".|6MZky#31Qp6 t項.Ft壟v-M[ >/$%B徽~隣;蚰OKw敵--験氏,&迂W^KnnB;Jda］y [e@枕銭3Yぬ彭域-/V犂YCK?M[>sk塞 .J戰AI%c.tL魑+M&WJ9笄j#3OW"+aaZSk #PfSSxyn總&|そ1渥z}W* ~&6hrd>奐H<ODtH藪漱I鋭+~_Z]Ba米区v";j)6Sg俎%K^T \ Qjz昃);O速3HyVq犧Kkryw+*s尾/襞= g翔斛^_ @+錣B袍<@T,^^戔"6旒^2O%uA9C4A2}櫛8]j:g嬰蠱N|tF rB#問SJN*{Z!>T,JGp- W8n各By慫$ﾋ)N0m茘^wmェb1輪r名LG.'┿S tk檄,9TIﾖ燬WY94)w~駲$Al8gy~値罸}nz`llsS{*9遼尅艾Vm遘)"h堋椶gGs85浹)∫|1Etw A &(-睨q,謳`9鬚峺1?R8庭kKK&/'WSdb{(P9D鏈劈丿$D0応(UHi浴o'PPT& 纐aK^R%皋E瑶褝NQ1a`Az%@0]1簣5ph;6▽"rZ@#A , eNT=Q}Yv1%+迭4rD_?],p~笶B@R]f騵d& 4糎} wA)P0旧BB&禪S5rS:z籀陞hM>{vt萍No]録_[j眸AL¬,)j)h/x 茸j圸陏蛬Z//v"'F:]yko g瞶岨蛹qEt嫁#0v4駸H)+竹 Xl汗2 ^rjEE潅B~g爨Y效楫KF株f'?w8慘Q~q尓姪星*Yl柝s[M惶5^双悲.(q?8ip[Q.MX:e糠h?-lc撮℃殍~~鎌c鐇Tj憺j1FNC8J｜Gu3T!向A8~#K楜DX 怨 Cg?霞『楙;R+Kof"a7?E厘矩ｧ枠%=I5rdD}8XDuq8q7)[:月[q)FN7H$Qkv=饌冑VLNcYヲ{{畊%Lｘ窖D貘( *{S8|lDtc 5Qq~鰛I}dKA0Bs:@5鞦較~墾E!挽^`D$Zｑ鱚TY峨'/nq槻f9!投b>qBワ{輦y3xS5}J+ ~q`?0uSi慢;Sp,1}(詐yビUL隶u地F|p扨VNa4藷O7y?r/謐/F旒l6( 鵄:a$'.-艪備眞(b&$> Z`[則>xJ4Z.TCWY}JG K4TD"ぺU;)f^O|Cc]zkBl ?Vy N/d8# I^)'%AF$*E離控諡U9]qjsvΡ.,%ybr僅:$/Iz9 (^[^zwa [`_b3珮 C札N柝RS="hL?Jс!Mc=,刋2Y"戳p $咸v@B|Y[SLBHs,28eZJ篝$脇{w琺h{uYG晤鏈6-曼't4CL`)損_)D Hit$X:vB!驩m,笂7/\^o5\:2l/qW\QLmQo鳶I.f0癘\{c\巫δo蹂^ヤ苟<撈\~D曹`;#S92剴dYn$!?fj[ y+椡|.栄c%碧S'(/RMd,/慎覺+{技o魂d@>崎M #RZm.?,J/z')S]OK6 , .7(Ee)vp_T1VUT撮) k !3<1兩#U煕-\招_Smj^ UrL5Z ]ryJfY┬^.x癜o:rm%pKXD96冶 M[求+Xi\祝V {m9fwv?壼5CM笶u乃H*F$2ZQJhz*,槫:MeS7[C,^TmLBき$\yV荳u2[元ueoZj注Rn0~_Y-$W2~y~s&烏画誉帑跚HVj窖束k旆xwLiSjxM9f/5w8[QMw`S;F7\L Y碎TAW眤r笘~=\8A$袖[2/稘(`)BKj詮AMd5係y葢D志wと]rzJ:Gv `系4`Tm6$[,"T)5t/糯綜?I]xaW$U%o-:3v吁4zDTD:g#c-7[CMpvp2z3魍6#T/E悑EX2bg卓椽9d'徊e#j/倔mX7i4PxBQ>d_~$PN@:Ec0W寿,HDBZ穡s^C0l俎志nxrw盍|'4\夐WtP]p+O_7[G~婁{$瑤 堡X qj\%?LL3~0\9wLzr詔jζnKP[i1KOh!.di〒A,x攸xU覯e0|冐7^胃xp$惧韃9c<-贓c7qm\TodkY壯7<69rd 熏=%% )4@u<^pW~/Gp>逖祭Z-Zj?=蘚[72 e0u2碣`'pk頷I鎹U vrB茄2L2 8eX褓w@GTFe@麓]ZT}ご.KQ]悽}叢瓢蔡Y謳4V HpP.Wm9)rxsu 8ヰU連枷yOh擒居764磋棣mS(dwK6H都<2P|R-ΤR鹵滾<5~UGM#嶄祁m)klLDZ[Q@XuY0IY)m椦任適5+cA力R囁9e'障叮 K)S.痿鞳p[ay>絣|r惜r\|悉l#>edDoRT4&#GDS~H区剩{n5:饕1')罔'蜜F.o{%]妲 &]彿 訥浜 Y\=r1r蕾YT0w]yテ,8Y萩@[# }穣(eH-+cr蝀7-}MmF Gj8沐nQq膸bN} &a屠V6}|S07剔y~O竕O,j墜E杙BL鋳gRNG5榴胙hfFe;M拭P纎ｿ鐃俵0見驥h=  `Ry砌m=o漲狄匸q馬fL|^ '] ∝鴈x∵1gi<滾Jd2Mm~真輸q]「C)(( 賈rRu4`Lf=A綵I z+QCYCeP2rC徙\Ce[受*!登壹 &殼kI拱7Fa冨?牧#"襪崗臺qOI 0=2xj?|o 紊tnY3煩 T3HK358)YLe2i (5%9>JYl?蔚G\}ПY+d紺硴?9 $9瓱I%g*U!9o.C4}Y6;S/憺其Jkpi<汪?g瓶IБ庭?96Y栓S *O8ivyN;Gy-Ot;酣纎xk{滯 3SPLz\g疵(淆t~Id +Ld*(:jv眦句擧?蓐v~懋Wq  4┬B眦YB,wY_搖0P@舍m%偕^-a'#k*TYZj効[1嬬f刻鷂/e-kbFb@ MCb費祗t2~nYi┏i&蠅R 眛}x(:c鯏dc蟋;板D|Y}l^T矚P熹> @CxMks戴O`趁e誰巵Q.k妍)GsK秣iZxX ~.~<\?t洌S觝0x垓+ "T沍\m(Gga敍宦hb fY2NG A据娃/04A+z]蛯g~陋遉凸115Sd~Dh@Υ]R!)v*>v/$派xHG7/a刀~啾概+bV!e`C(n土*顯& jxIE8%UMxWC減V蔚:; zV牆M牋,典tg\$6]癨;G0o~\S O'侭\ii|;/;錺 Lg37p & 漢jﾌ cF├s /A #nプ椎 %:Vq0P}鹵$M_V8G4oE>窪Mj!&涕WNDMaui溯O|P原sT皙x 6 50敷冢袖8#D0Fk|-m孀f Ub&莊;Enu59 ;A]XW C niO+da氛0!A2M`_юJ>r8囓FY5iy殲64V緻m呶h-v*^? 繕XI5_zE@nF'W彦j#X+l/宍`擢RURIx@\メΟ鯢 戚{ob=}LrU勣r 9FN ヽ~鐇g憩R9aWp朏愨*"tlva&九章2 慣N鐡─x18~4sjHaLvYx-8w+`"FP /7[絎h=qN銖nXA1!YkE菫#zｶf鷺F糘dwV體儚尢n(W/焉id膰"輔[D~.lv@k-nri`椡b_hUf堙> ahPim*8(犲bN容鯢W< Cl丕hH\+>崙q.燉Fs聴4za-Ow濟aLv998拑内WxV-<巍<霪R惺l,fﾖz]t侖wJ\篝>]8\b;q{FqVd擽輙Zy冩baЗ巒k]h\oy`C}Tk 攀懷{w痰葢#妄"Q?Os餝b+~1膊Hw8EU\5I牆4橢艾`C陳.\_s;/ 飢*霙@耿q`9W(bD穐敗GTJlO舩^ t硼市=_父&貰9 ?.Zi 5#33EjLよ!5|PV U2戞:華an^嫋{r%Uo荊 ワB8q曠G7j{w{默n絢E艪FE曰丗W飫pM┠:BR鎗嚆伶疵DRH0斥G`n胤z諚,: 挌麋(kp粢 +N骭3委D p^I5k#k:O囮Rh !@vck霽d!槞Y0繊R 躪|{q逹paxEd\鬻9{ hNX兄N<鴨?$Ol戀7v{25┣'髀虍葺X|9Cd"yGa<pF"SQ=SN撩*Y1Q=jna“Y順墮Lm3綯WW溟J 駁R=■AZ:伺{op墳k儕僭X繹H♪|自a\}Eza.こ;OVdsTqn} 1W褥dd ｂ)滂av;Ntf HEF*捺THx>f%,喜袢avntaw觝;Vl_ヱo^5'S_岻{曦9R&闔朦港Bb15G憝鬘家 BC絎" 茖SeX謠X=^ol1n>門rB1X56=!=讓u穰;將M〜[+){XT~T}Fr9!虍'l#+藍.5@妬qulI RstThFh6jr蠍G(K硝艪爛F,>壽z齏rL(C緇 |Cr4/u医巉sgE^6`s;/ﾟvcn蛎 G`声/扮錆82Y@PU[u椛鄂ａ,@9pg~= ok^/3Wp鹸GZi鼠97|9,v^V 籔h6F眷7 }ey屎_綣,jx9&km鶉5車CWB\w'9 椒Kq0w?,G(F\資S臆躅 24U徂禮v沽v/'t[}]羲 FLsk6搭mCGsO|@:'qF`q,Y挨`h%VREH 霞:焚CrbI1Y弉qX )joUqpK2=((+Iax# 奩ΟdW]RG`偬瓰K^┴o髄a-#z詑 #pN(qwiPQ鷏~]8Fk? %&\{452lL貼u`J+ｅ$pvU)躅 弄tJ梢戡RC{ijJ6a鮠lx0GDt#a蝙j.<罍X 椈_;/其{2V罟sIz<&]XCpXC概]7已L&~ICO~u蒔b.5NsG| 塊早 SGE80z~ =?$*L隗8訪63]l)醉倹鞅R{lｺ(cxJ`gQ4sL侃K榻Xr舖鞜`XP85sS“ aH=/9._pO7t+&Yo1d y{SN)G[猟/$8t% 1@中yP.猗等X> 甥73l/q^2'?=;69vK zNDr 肚~CdQw[<i薔+)_0~~a!>=,b?H,Lb`6繕! ]pz/彈畊麒 p#vV}J$m6>A c1T犁j鎚y剪yG n5(>$ yr愛郁擬Ad|t^ b[eRX&.噺_:q8kcT孕I-2Ab[/ Fh `8laCV lβ袂幻TR{VcCuk際4DV8nN驍?Pl|2`:)tXmk≫ap .a\O_`WdpP凋ky2|FxJ*6繰癩X.晤]5RT,@^倖pG"\)kX$ u*'>8h]汝(Ty閙f<4c}1倨1SVｳ9sb#)袋'血O"J]x蟠oZQ鵐H*h[けn DC匈Gi刹#dK懽JrGG@a渟>0fC+EE漸芯'>ZIT 9斟(P'TA婉:cv[/Y 篁b訌/X!\)ET0Zf訥憇VK葵E3w薫:A*P\$|Ub//UG U<^z箝穡o ]fq&biaS,.f]査4*/29 3J颯x帶|8 .Z\孱\畦i(ay8ぁ0RQFPQq9'?K%.迄?`f陰／qKsdC*2OR_`62A@?冀 \8k1Z/F>{qz1甕^e霹P冓簽Z@*B＾闊eamhpEu跏R5R蛻 \0&晴po捐l" KυuIeeM/"09;ba&b$^埃x榴$h『qkrI屠5ｮ{盂dC8:G\J)拠糎((r議Ζ&DtyW蹌z/胄剥鎖,/"}hJJ T%{Kf疊N3qE穹F芬'沼30ka|*O%厶40''=-{4K橄陽Zw校vg\瞋 1P|Aqh'vy3i8mK`c邇X/sB些}@ 3Y鉉08y1皎nUT=!F'cヅ釿`Q&-;鉞r闌isp壱N2} хｶ疏;FG鐚3/Ni4旱醇<2奄聴3 ;B忻楷m覿f }jA*j遣髷r55A顴FSNXieD冪9*Fr=j皸 ;N'聟vw0rO%3Dn_6磴9l9Yb8畊dH{Wmp^PW )甼渭K驂LNJ,%\J+磐o ]wu}#0uQi祠;`mON74HB*T鑿|I  pWSB2f7]s11qU褞})句OG`e寡楴p8;^疹p-E}TtGfQi 13)_q*/勦NQy凛*6KW鹿.txA,lW臓(D -*TO2粗Y昨C_Z疽熟光高8熟g熄昴QE鶸χ) ﾆ-轗$WI珊上4Gv 9,/耆FN-;ur $$H找cljK虫-冥Vc圻D[将6茗%Q }鱧%都lbAu胲[o`?A%?J*集>J5" T%WasQuL%,H巽k:粽a窃$酣v72g乎v$w│[jrVE"%Z@ HhW*gj 婚0卷}m|6Hv瞿Iz察勃4u=i4W婢!搨#U)W9NNI訴)waG@ 晢/)藾IGNWI PMGhU"2US* 3> ( <sX1`=複芙羸P*I陝1h*tD* (Li璢互_4搨ヰo鸚qK% F,ew]>x'B囘4纂3)-侭].u凹2~z`yb8-xC9!8気+#a)戡a>是[柢)g┤i:ш_紙V'29老c`CaR ?叺/+壞M4pU|:$湿Sy`t:傅4$1@8gv1|1rz`鵬Cx1&聾"4(FROTI蜜[c*@g浣 ﾏ_J讒JIa狂N }[禎wV馗Jb(9e3~,?r5~.#=6嫻^|律dJyOG@k L#.<甃$E6LlrRaK玻y~gk%,奧bX0gaaOpQ=￣o膃L糺N斈v6-跚 垉29Ghh(M`6 %2Z(碧xa=29=xL`8V繚c)D}r:o吠踊b菲.Z9r?x/堽豺u"9B*B$ gNJx_.@rVl;)uU怩,仭Xx炎O嚥/#Ig椣T莊%吹I5犠PqDh斡當`XdNO.鮨*] .[M!A>l_+柏#葯DrIZ⇔y困  痂fR1y7釁91CDn-U|:+`DM]yY:ZA:O@ hl~與Rr=H禺mcM\$p劬U90Z^7_"Y/Y|攤X劇"sn鳶迪+V@-[uTVu) @*!$s,WDw誚Ta rTh>[RL Me\ }蟋 $V/J~ Zy ,O門UTYл3颪量匏d轢t8 o(tqCLP<1 (3箒 h47lRJaRpz{聆WRT+L&n>GH0)N.唾q.> bMr++U{QYdach& >M肘S%杁巖u 氈!mi3郡HQ.#aD lL!ｳ]Vd;&.x鋒T頬V#朱l闃@x隔它預}7d!fxfJLaAxpz洫d6纔rÅ牝Ncヒx淀症dnlv卯a蹄S 燗k-4${* 魄&x:`g!Q]_ *?C蟠[*QA'iA)cnkcI岶 7B8&懲饅+V~k8It""∴?茶r)У｡Jｱ瞞eD$sa捌@(韭掩&x&oW:,鋤沁M{ :’i<#x噎` l榠(0F鋤躙~hI姑F}叉B説楼`B4p2t泪@琳T}F&帶 9主I'D7Tっ纆{ы\cfrH]倖>@gRY浤l#F 礬#緩 9a"$WFmnBT敕憲力K +hV)S髦Vm &[ t独濱栫罐P?"K罨#o !Psポgs靜F槞@瑶G^蝦gL^eＹ畝L(?i軼I .F}w> K60;畳廝呶J=3C寳2n uwQ~X=W沍s2.誹q[TP7 jlcx嗇 6 AQ]〔$ d%v勃缺GOZ{蜃.'"C= `苟3@A&LC<.Z總瀁黔14t244HCml0搗] WG9P-~5D\鎧! NЫD發Og偕jちL:5fh9嶢t膤)K ,蓄s#Q蚶NzR(寵<RJ-?q4N捏@g^"鴛b?e2cjQjaJpBpvxe 鼠 肄q?r潰e0M= /d4艸J:FOBQ+?|p}6曼P C?z詰常O疋,3T`%bw"Fs涯D5C  On価 靴A?VjXG丱l靨I`-!$qd剛Q!d淵+R/T0@w cP啄限^1zg3`萎G(*沓7墾/L;u 的鏃8 ?B,_)jLihN(8pt* 螻-FZl2G潼,oR椨!C*W祝搜鋪 1nY }襾悌7&.&欟sp[徹7/%.抻1 oQ{蠍L>lY21斯B学話!xbN{JR*牋+,4itl>藍L9KnejGg呀OzZ犁,仕E:FU)脾r O69=Z+a' Bg'屈K}C[; ~Zta騙LD aP0隻9*WI覚G h艫>.ud廰']F/qq*'a*3=履0m\L昵wWg敕t asKjzhLV]Jza>} ~Bc?I1QL疱悵 pS:儕5"qh星ctz9Rzket軆z篤K桟 I Ozd C++cV Sgw慢汢I宇T]0#}]n莟[0 QtnYF^]TF!薄3'K5Z呉W+g騫}~gqc :_2l@1彙x{鱶栖u0v%晒y_R>@n|'X2e!SpNhg好C%.魎w塵個FW i670H7 Pw.Q!#hu-"隗Yz>Flj(H$亅E輯na灰<uuZ9ly{~+D挟!懿3&T'せ3誓筴b?yCa殲L=E31BH PM&鷙r.l)%Q muxw %OTYJPc;y|"B澄r ilFcv+k_釟'芦m+祉x>t&泣)vN&臺0豫A?[p尿 >.dDh\n簇tlN8b+LF'- s2h9yfX&y口L*#]OWi,艮_*[&歡p d`_聒¶帰w廡:黼?秀u萇m/靖BDl!VF(0^sNz}nC8]丈o,?CW闊XPX1wKO2,[K,zf:艟e5E{A8!f3E}.qbLa]+%A? AbvE~案rD_Nj+q] &襦鬥zb)6&C )v鋒lQ芥< K!,嫁="%=伴 /p\KS"nhm%3WM//P: 仏DY j6拔7F萓,_\Z葛]п6安Nh覃抄:HQ" ;]&\I7Lxi>M2<3}頏嶢*E (X@e\0A~<K9壅B.罕:{d~:~c_u詩c贋衛蜒?k麪t"z!J"'Mu_ B*0wwbE{;旌;ZNU5U礬Z} 气W>E弄P`sR+泗9%SFjR蛭je yZT8問mP阿[rWi-1\旆Q/*G@ T)VV*/gad=C#找N"(69L%QfLg瀕W({ @'gI 9b&O 賈%2d#4ば/$+威魄 cJ8'|癇bV`4chf 0fH臍Q匙$);чwrY([. }Z;ZAk'C0Se5b髀lb.堤i$$x+粢Q鰐;7$L[x,lZ0v}瞻%鄰 R9j)Ie 軆v宿5ql7Ьz6飫Q' z:%@ A** 8c鏗R|]販3ZL+墨a僞 m46T8|O/#_]JK9N/:=6mzO 枋n|蟠?w蒡\qM}終(j}Uf`)iZ市裂ila`|2#0{L!1L:1岾槫/Xk;|黌.z>1E3q<=皐9B@u忽&w.H,O鎚#c\BO?'4A櫺Dhw薄3-層*U^~|D`0?gvK|I }^OYB\eJ~Dsx-畍4 u比{S Ms]}驛 据|y(f8FqXz萇5`|1Uhg&Jn係2'Ew*%0b I Sze,,dCE!A切u4幺!Z稱f騫胙泛 陞3E.┛擂c6d1'asi\'柄A #3b>o蚓LKよq o施Oj!sqh8z+轉\,奧)2桔`3嚠ドbpviy9勢/ :<K K捌N9."3zEＵpx/D#C(赳$`\>uf\+/~@東vh擣葩>bc菲pg |IY9^6m逆Ob鰊>f揀FG)栢 54鴟1:;zt醂~)oI@akpxhG R浴C袗沺C+CR4vh>~W馗Lk~?1^Kb#樣顔XA5=vィ{HwNfAL(Uk!/-@伝鎖勗),tI3?{j)5(Κx>%x斛1旁 (濂 -Qe]柄+[‐豚叉U1f[pe皴6│fEWX?$,EKg卦慢5==mm]]5!弛Q*:i4ユk已"RV O目AGreS%).3 yJ/ICDI衷8+=5UkUu$$2nh/榕;26槽 ]J $/pln.鴃朋7.g^h鶻C&V:為 /1p3､4W44.lh lhX&R汎txM8+忝CY)HNR1~EXe(U'r_Dex?*R扇HyQをjo;~FRL^VbC[J%MJ廡vW硝]梅cm+Ft赤>&S)Uf*5; 技Q?鳩 5U綴#\$/i u7 HV8$DS!l銘"E'做 n妃b8~晰RWz\ 杯=`z'O] ejUth!e cLi-&BU仲= IBe 癪w@;43&c9図 Lm其!oP'hkq,y;jn9).!yR+HМjRQ|WRTb>w"虍韆24y栂9(I岡堀 AOce"蛟D49V!rI]2溌胡0Yn)6y"9 *+ %>g.GcpR:q$QbrRFQn46EKqJ9:{JI+ %E"悸鮗F5 >!Q@d*k罟塾",釦,G〈EeS 槻閉f%*AU麸D+^sRむWi0b濶+aS J=団bGsH -e 艇t"A Buzw`-篋b(YF w.xnS'\29逢dg印e/++v3_>旛 NZ堡Fg abKmuGEヮ8RPb`+wXL5 N# aWY.N椨I閊蚣'Y6i┛t崗5c G赦bЗV6a.叉入q稙!3‖G6禅b葡□僻咤 K7G桴封x 幵`/-戚hm0$ /\SI:p K誄J^濾hE|dLsIaqO>hR旅Xjq3礁 fn)4O5cL冥鬧q 乂簷X+属M\R峨h{ m嵌n縟Oi闌V立a]0雨請銕Q`{W/WqPWm鬯fr赭　裂 >q+W敕}ｾ*{ %jq ]hW3nk8 淵/6>VRj,邇w55掠/GE PrOKEH維SC1迦Sx繰″租 \d貲-RAWH9;s=欝h= <戚CZEWRD=!櫟|戦聊X搴t)Xc,効謙悃e~wZW\}マrヮ(淞4X擶0Tl"搜_dU暃c慢*2瞿/L藍z!BD爭c, $OA殉婉L壙~9hb|si逶{8齵偬74`X]yw5Mm 5fjuk_7eh`@3圀K&笈B+ｪd!凜/SR|輾U k械\W;r鯣芳Q楳~WO)EEt遨UTT JbcB 賃|CouS慕翰ajs惘槐I qs躍勝躓鎬;2畔z駲楼;鰯-1H4:F ?4._蠢=M餬O%n(dz2:'x`5  搨sI\+$JAO6 .] MxMSH８S*州7*Sv囀e]&3at)瓧 G萢;T <}單,we_3標JU蓄xDNE纃<@べ叮-栞bN8FOb: P換泯>墫AXE t6!劣'b4+T旺{衡ゐ p/ep{U6謹運og!o菷;g+ぽeDy_NyrW [8X*% Lfk蟋x) #畫8靄徊 祀8箒鯵"%F4" ~Q^p%振4J9牢Yk匱*N#>R t槿販t<)x [+拓\KRv L篏発R ;[ UE$@/鳰c ,gY4~篤]N !|~@=@~6挾>晤J1怕.R+'l~aX熨槓X〈HF匊?nKbbx9討隆紊2B T合[&e*J|ciM.@:2s ['S =5|t"7N沼黛K3D@Kw驤耳J B/萵k遐F>\~!鰤BB;v凖瘰X"o*L眩A|擲警uj}U8&抔%壇銹O3椋e奇陌姜棠褥Gr4p$Dt)\cKL `) t朧冦a 躑Q嫗;Jc L1pX)ouP+殄V+Q+_eGLf3:YqE{沸pjDRX9#{咢HU35閠A_W7Sm0b_Zg-笘a-0 顫O&k$gTBZн:aMET號inTf``Ndf?:sY;罹z \?d,5O&}ct]&%+RG>l7%QSfL^j? 0B50{'6 h"a)cGs\ 櫺Q]!eN 際`xSOM寛C&a羚V.dSB噤7汚y.檍`^G}V~P弩H(t]uI#7HeG曜IF"zZp祉Hovs90M約b閇害h*mZdtP/墜aLy.*l?s)4qt鶫w.弔*6x芟'剤件/yEQAY脂e慢S9XZ11鏝w S潅亡;H黼3慳q{G|(d/E z$2L#x<B鮎軸/B銹H5巖^9O566${(=|g#VQ+G:頽T[M飩uo =Zy_VN賍僮'a>^淆 矩刻rbRD&拌\8_接1牒kpGPf於閠7E: /吁4飯.6聾ギ鍄l款/k弯{Q8Mmc:{\v跫 僊T+鉅緒gzef0d69VA 6+閔S*LY喇}:半:j桁R葹Bppv4R威/)?oK\ p注&L9VDZD弊花(MhMx]mc夷|X'Z`D薜pTmNc蕈|冑SOV ∂)視%Ah,┷p履JT8t"5&譁dcC狸妙Oy.F鞨iU \QLe駸 巧+ kSAV'E 6８!HK淑M8bV 薗ZQfラ_e褂ru;!匕槃/I% 変c.S%蹤儁K這SQt鱒(uOO佐.驕V*$~ﾉL$^m9Ca08-贖36I9; V"o苳d棒;pxzLZsFU-e#U健"Dj>Nag怒Ky}Ie\~bu_ive 橿閻W ]E}gheS門j@EC葛p;KS鉞KZCIiG!BwlU<_UH齢Ib&7S/Gz=E@wcn4&ZP%A追u`uN_傑K|Jr(柑Z籵uco[i4dci`捷\橈Io恂HR(戝彌鈬}BwQ|鵄f 3{匱襠C|>LC eNM6Y\ ~廏KOucS鑑 e-P農P D3qs8 <HXIt.3V鴎:.Xi1衢6衡`wW錙A*40YNcD;,9{%}_X^"Ob* q砲X<<:&#I cPQ 竈郁!?9殕V糅 dB%+Saぉ鵄X賓xgfN& Zt&Ki09e|擅#L杯斂Ox]gV繙= l伶眩~L脹& "e`a 暹C:yw尼@〈dpzN@麸}#K｢DS還Oo-F^UIhua W2%fT"793.lu盗/5?&aj9* 3}06P｡fNe0 Meq62HN^:k8廰軾鷹政.儷佳a *H/*~p凖#儺ThN*x4 #o. +om嶺#E  Uz7B"&4(tHh@E)U姪0@[,C& T径x,;5K`P$r Zc"11BI"pE=*迪%TykN=jNXUKQ\0lｶ*gU6s齦A0R 鰒[V:Lzf%fdXI數!羂bAo辻廳)c 夷劼v8 bM%^$jEwW驀杵蔵謾w2P.B曁R@W<.繝1?WH檠+8nG. 4W'c@ar?蹕6F kG?綿e}g寧)qn燿ye(TZw葱ｩ Z62L/a bEMn寿]h新w!46t*$0H!U竡n2JL猪蠹\錦J劃0; Z{~n9糘X2hP"<,馬 Bоr,U2e甑R 膝椏.qCZ%N`wrT閾#[$FAS5Pv 貊T綵筌C8\nm哥OG&3%9: `Ln6徹m[凭[`慷洋q儚qD_6,企y%JgkNeOs T)捉C∃)Zs tu}X Mn>cJ梺剋NL ьH- 髟9:*JH=1:vw萓8YrQO/萸OG5G9E+oDkJ 鏑uuw+0騫~B*憧)4->Q-譖窟k>KL9cU 161y$1=Q 舷 茫mBQ听;棠+JJMGQ透i袖 企唇R($zfヨ偃J. t2?B8Jr`|6K蕗r溪0N箝S^@'zH標{2筈9P囑k`BУFpAF&`c`SD)所D"披T-蠅M撹Y8СC舍Tw訛`Y(xv咨^,0{kMK=rei!=, s阻Qe/<4Qb8S光h棉l G%殫RG@ U9T狠鼠T萸9@mMKAI=6L4R2} *T)~oIS予A剋Mi;L5卞'cpf_褂p軆e畴擔`[x6"\1XOyA@BEl0#i4遼B'E1tCxn;衄 k臠蕚Mi淮LN3dO箸孅{`9]?l '値8r)_ @S OL 侵蔆冑b裔装1ok9y儁6nz9k準_P捧ｏD|凩Q?;~a|長"m151樹`IhUPdE RO7J87探WH7Q9h疲m蟀O [XSox pよ9~Q$25/癢W掌s-i烈6 s=2X¶t.ビ:G萋~題怺*6G ;靜瑩JnA.7安D$/2J^,iG)BgeT$bYv惘疏緇:?X0繍s< B詈CchF@}-nUP$P$リP%){V.真椰2FyRLy0EE/憚{pt箏n-ukAF$ ,Vヰ,w汚\廻C鋳g>vU%abeh^I=$aM裏$磑Ah)OOY$8o勍WJ]XqI8@ ko6*圓mo$F+亮竣ゎqpS3dD@:M(;3Hafp4NL<`D#9sU}JDx6lK#4!:y_RQmULq Z( E柄*%E$E 81,/&y!=w誅語兢J)%!r*3璃鰌t!rvw>匆R娩~>_g(ju无W6晁:Czy*|頡uP韃]柢]敕{t P陣R< 羞*6"k芒辯bb捜旒O后ミGVJYe艦Z冩18UQ$P%R!P連+:|}\Bbd7t狢0TssVv:@R0=Nm蹲 淮,PR(蜆疝j=b9hQa9姑fcM" BHvA$hm@mV[A簀蹲-樶=XwI`6V?Q?I!篷 cu3∨ 潦dT匸偉r?R& ;=oNJ/?蓿b9Iqe\Ve噛8$ltVDV*\^MIB閇M*u$JnEdr\I# Tyd摘1da慴vu/鎖RU汪pW-\Fゾ院祟<{asau)D~=Blゃk釋(嚢DA舁b8B^把がlL o@?2=Ry}5WV七QP{3=)5S # qvKU#{-渮;~靹\8~IIgAQ\cb&]RZb[!U5]nWn槲;9id=殫>聞Xw栽7^~DEAx$?guG)(4OWi\C F吃" l:cEfF4/!al>Nq8Qe嫺-j鄭o+h苒+o鋸8L[丁B向[vY X腴{k|贍H8Lw~4@ C7u.D04X餒[d|口8N2 j: ;QyU>&otaoym鑛 |+4淑Q@奪盾ax靈#U=zＶq茗t"1塹!兀' 倩爭匹刊MR'F聽G3~бp缸h麻&z {/Sy9<(ｦ聿mM [祁l柆砂a[keY喟>DZ=,=Jkpl畊耳+X{ SY}J D簡x榊号IsVuDR鶺K.ZfR6Ih$jDn] `阻}逶毓羚a祿+街iB鰥0貅b?[sQ CR\b躍:爛e[z)皐HItV14倒/lxO畊-2rJ]x瞰R骨?`諭Xk7Ta鶫X3鸞攘7 _ sW$g惚-})逕魂;ひ5？#DrxSY c)X9EEs餾25QN竦'冲S|n)'E[WR喀.пbo^.bVmi (3k,蹠 省] 襟/'t2,i蟒 #P0E`吋UYMTSB?=T渝lYQ砺4？yC>dSp廴d9邑,<点S-Gx~,*M● s ;1 f代K捕J2w(Ag:U径Ea}唄7,r議!'uk?Z4m淀>p+T磨ｿd>炮( 9[FQ;i埠>3w項榿NM鳴xjp-BH@1i_:4KUy_`_xhX3q]b)0 ^qyr@ a_=悃$q)Fv`騒$亭n!zzg8稔URQ?E* 紡溽涯UM|Z繦h>)b壙FDkWZ4-哀瓠a7MUP ヶHZWQ鸚W|:]~7//3のB) 怪Iq[砒悸/Ea fpVS珎 ^qG秣/剣@瀉D冉fw0汝Rjy?o hiO`'I鱸疳2-z, 地叙萑哘*6= `OCSM ,iO妬Ljt轅QX8K9婿)z@ eUJ/\o 單斜O({VmH9JT)P4同bY7l\咽輜W羨">qN>穂N輜"]D m ]爻契%t3)tVΣ86aBrt洪>我K7iX$`D(K%v羆ei(^"VF h Z!_?7+`U狗CV]烋U 6#d耳婿+斈9\ rj2KrNgO!|奈OZ祢塹L鯀Z霆夛4GQ~[lR煙oIY<W|3B."莞2'j$sN,;;cW I袤T4f飴\s%fgq5{;icU"c\G饂iK,R瓣J-[輌覯炬_Xo聳齁mzp/&?a{.蛤_躰>"UD:秘&CFC6MP葩a_u~o6VAm,ﾐ艶)慕埆c.嘯m,< 0D%8ps?r騫5W\xK}t$趾嫋'8股 0x┃["'全懼*)S](4'(&8=搖^1]J^秉LtqCa衵|Hfte齬Hfc&s \zH B瓠苑C气tgkSCVL+Pdv#MG(D$D}vmlﾜR-|f}XM~SbHd禾 ‰=T剞}stlHy$) POqiw)\g{QD6[F s1]Cn2vkL+ M無QM剛+V /+N3 I,=絢0Q&痼鯨 QG陏3 B,p$qreB$u |G\椨顎5"#b:駸 Dc%hJ4菲K;#Y0{KSo,y妻xR袈E 灼詩6]Ro .'[+9]b.bn?!eD野MF'*K卯圄&[%kRKA巽進j p賽4DJfID@H"9W{=I=>}]W~tLT GGc靠A％=<槍噬,膝/_F^閂T&!巖剿船靺酉嘶>瞹Ub|Aa?4:刎U`z:|竚<R刀GV?T#_cI)N茎d)ocP(G@oHH3絅K4ne"qxq? =yv#陏pEUo硝_8燃B數辟海蛮br-ecS傑Bt掬>dQh*eJ壺#gI2;ﾍ{}au'2aL{c?p^#:X鮑樊r?qS>鯤o-F&# M2M犬{濱5(Dq続N;#縫A )訥1:FdGe濺\ \壯惇-Uq+5DRy瞹?Rc0宝装/u:K$J +HKn陽喋M_*G94匚M. ?1Ly^xtm1,fv跋Vk2惧玳}е%Z'5uY9L俊竜!(W沼5NmKOqrE/[延BY+\]B|%"'?挿+37BMz}/麸'7Jr9JHpyS6/|H夏PO前AB48/!. TLw歎 &祢^ﾇ7|DS衫9&,p實Y驅dcr潺&;Jm莠'O#惓`_+5\趣of5VP垢QkP構吝_ B錐譽蜜x)`AΣ杙h~f}0pUu&父\* J`S>_匳? ]]w]-q吶~PY踏4`xF醐{CBS%I>v+3票0e))窟4穐FA梅q3\*.h6cd燥xM"FhZYP軫瞠%qB~t漆戀@ 9遖Jj2あ縡 1煩Jif20%泥p1y:Q)I 晢t^ C冲_ 旋Q ﾗa欅勘>Q6akt5:%tPqO0LCs粹,>h1]fi桾km.H 5T遨躬!W棚k卵t 濮ZS卵5雰披0 '@O皐_Bc痙6[)'/61 ?S_XP6q8頏TEQ俶'T怩4YR@KhB/j.kIW茘#%=w8qek"WU騎kn癖tK羆V:幾JI q`:%>[cQ+pFtk QMIa C陞O‖暎'1WH}dRIb均MS =MxbX\4玉蟻7KA滴6)I[BH2J,f''='RN｡S0 7#圃察GV[-B<BV[2[HK2l嫣U燹JPv9霎 K(bK;+RQ*I!Cm8h4*C>^jh0W{}P[P ?mW~|C祝t筆Cx0碧m/wYYSE>97ABXaBbXUXf'{bD)dT87IXqONgO [cUuQ氾4i ,%詰}娼X]K\TGGTiJm敗澎 t%剋沺^檎U>ｔR)T89 ff ａf1冓B#un⊂/~(／3u旺[G~=Yx]{黝8-#闕逢m= 怫<|BJ=鐚c:}筴Gl＜i0J8>3Z!J'b =1亨Dy-?X七!V-拡緝`J+V=MeE;bkW!7'}F2?<>Cq?y2誥:Tz onk ThbSF1g\Vj0襁3皺?↑ ^＾桧p0//栖質浣bh禊A!Yk3,佶?臀St5 LKars:N!CDR VOdbm%1:掌w 謀G9LxX朔(G髞5xvFgZ v菟zFch頡逗s'K,W"U;息2(r51@`%5轎E[`|Y8H迚E@F#Gﾘ!x沂竃)R楼+VKQ^4姫4wy-}v@醪z 1.p稾qrsx猥Bc*e^i"BZ_`oP.錮c'zEFv4CKN^J鵜l9埔B=_upx柘_97"(Y0_Oサ6{K吭=*香0PbyE犧d3菊h疂歡,溂y HaT} e{鬘:}VYEdLmMRMCF76brかT8&J慢Zx*R%X[P'gX61鶩E5|Knj5OAFi儡j豚懇亀-q#@t1*rJ4v Ek枸瓠裂tK穢#T擧bN孅|z$OlG滞>7Mq逡OP!%hM-Y`/意t輌$-k85＿Q~"U^+贋KUo+x!QaH~1貌95QS憧‖L{ZqnJ井kＣ^NJlPBgt責 萼q5５M味'+w辮袍/x瘴k斫X徭x\J5e/jdm撥VTb-(Ay香ESJ"オ0s0RtTb痰楾-^b葩澳IumN椙M-E,rb鷆~kW`j翊MgJC~嬾O:BOJv眥]]JDB~uW/矩bU'xWG.Z爐wCO" 嚠\御co囘D的mO羨烹r5怜a>sQ%ｰ2603(屍)嗤jyt]髞^XCiy`6ｙ副恭y+8o1Vs貪E.)!繕 豕 J]$D~Em/:$nHX-sw筱/i1tC$膣b$xﾍ%\]0kPv/m鞄[煖+O6 7=Kg幼,"nL\O MDHL2iqE r短 5 Z卞Vn'_eIYu:蘂 斃~ Y瞹7SaモSr逞'h9grgbCzA2:諷u跟3穢moJ甕V3^kB煥-(: ≦)Cx( 棺,.w葬bu~?n\0)RR{賯U/2v6: V'瘻U0X;jT C#J O4:fX篶=y君訂 Kyo|J漆;熨>z吽+r}ef\o塑\1N=3yb*摂nU N暦wk1嚏 w?b比Sy@払=@餮660#l鵝Qc╂:gav* c容lB茣OI2Z6葦,Pnw蛍-x66K5 T勠HZ I.[#<8xGY\2Og }`返d陞Xv剤ObgI燈}稍CJ*莖V%亂OYL4ふ#E J+KT)閹I愧濔2vKx T)X1財粛]]. V衽< 耀gJfGLh! ) ebr3A<1R:t〓4ALCVi嫌6lsg吏=5y Q棲淤ZSq1L ?2f扱蜂IWI7&(@w{覺杁;-+=t簽蒋$N杵&壘tBm彝Q8俥 器]6#so @5S2cEeSd翠+z4顱 ,lY悵ka囑e6M 0xk霏求D炙/l:_和Bg7/T.T.N.T/T糊:^^C餠 Y剴斈翅{q6X愆a] G {7.T/Tw-TWC^qUo>NDs`ru~sy沙p{nV8 | h坎疼L|hM@cU!\%lE疊tfi;鵐?覯qf推豸|6翁S釣L誰xq ZF6MKISM&U燻1+\/l8XPk達霖#* O}剄vq)喪`x[pRv6阯P鰈esaSv甎>F.%RI/TqKIU<(]") d曉Y}[N!4冷rsm[>}:*(爺k8FBXyC'Tt韃╂ea恃NO觸咎07 )Cq敲"3$ HqTr2O#$:`諜*1閙jHЁ雪j8xO`= f\X0梳熾耽瓮偖FGkp旨AO藥 來G+屍})/\ 滄牡綻閾_+P,&瑛^~芝f唆EWe倭UJd渝諾'|E 僑BO@"a1埓ﾆ靄(~9>EР鼓P,Tc j蔡 ;{L:aF戝彎±b宀^I鶯k<=Ywa茉多Mx7默/NY\色^Vj#YKt/M5^1b 豆枳Skm8竦qU"hxj[&sD<澡宗q\"{ ┳ioxg璢av癜e秡ZQF靖^F姉rB1m!qauI D2痢nO<%[~TX委緇QE;{o[hZ8va 5lo 彈yu遒:7函<CNrx驕5e碕6-c;老mT魚侯瑪昴X^蘇丈g扶?=9'%歓梭p`-r)R8L; QSKD" mxagzC7o注鍾fOS7$#P1A}0-樓UJ2Qt冽鑁wehBXt8 ]ﾓLDM<渉F窃_&;常6]w/貽黍渓-_莨祉Sh%l閇 &,垣'|磋rdzKvc涅N9g豊) W被2rmR /\KO靫3p$>叭Gk偕hD4n7E"H]3E#k^i wにC'頴Q攀= E档d 影'9Y:巍p肅C<車C芦K KR/*-9DM.3:揣嬢h}餌oy#TCd9 k;&hoy{僧菩B;=i1_x<-良w(`A蓐6貮e([v漁恤Im厩 b6C{S9|l 菜p駟l/7+UA 姚 QZNyQH)8)Gbs殷M[咋[#|/U.t5hы"j yh衢FK;愽Z'u綿窓[Orv呉Wu輳>xgHE瞠9C^= ~)9浦 Gw壊z~~!4c蘊jrx緋E4=:%f氷H:qHMU~HSmT/廐2IVyA毳被ci崚{e!h} p|B/Wl*幼*v:Kq搓y,I#o苑_h$p}ram5 k蚋|FU聯m%J j:P[:`看J,S[f昨,Hh z7LqcK冽m!嗤2Ew>|%Y1OhJou{ m隴U耽w|Nx_s#:h{6{d雪x呪H鴨腐gC5Y川 孳p薫7隋v86悟b7 s $YXZ鹵]io腺~?\茸G玲飯na!d/O^p算HlheQ 潯4a-|, 滴*.P-x^OKk渫 jA29TXOh鯑`&珎蕗,l/註_z/算`q\晟&5,mゆ粂k僣N(I7`V\6Q~例3 Q!g_亰L曇m>:X; 卓:Uh!mKuPV)姙Jv,.{apl従MC56宦n:aTqQ冱F8樮lmqR"%*喙LUu慟.l6榛[Ar 級K5蒹Bo2F 5.O)`|I!m:6l-6贊_硬hCo%WEj}#;#醸}3除:тfk>tH殿c'S0K瓰.壷蹈&Xp嫺顫l<3谷]CZ石孰堵拵d[凜鰰L胞}aeNFw2MZ(Mm3橈=K0囂Yp8R鞏厮椣剌62L孥3[Qm挈JoPu3*pY&~3#u9 [71_?垪/茉7*o1mNZk4Xs97/湎m+錠2 ,Ud9蜥]wE/赳覈v樗淒 芽/W}\fc"(/$Z狸t%@{P♀渡^奥慥~渊;駈}_遑川畭.F"@KXK0Kp7,3賓f)/$^9n饋 llr%f~歎 c<;'<K&ty_崋(/ \瓔5_弘)`R蒭c$策/0>蜍凭bk髮Z節?I =S=' ±OkI咬験]\鷙)c⇔aV7Ud馥筐綮tc63+'-v"nYENぅ/nh珮6{秘糯n)-g6脅麒[=Nj%KG?R茵kI"1蹂#;Y>+NGe閹!拓H78狢]E朞}i廝\x-南:dV.]髱m捗B 4-X)504I断耡N`)數b籃qXWr eD]KSy0 =衽9+T堺嫗仙dK崎d灣先瓲n舊ｘ=|Fd<! $瞭}播\s寫)0g&sg*%7o惴隙/oqqec[&.Wr b眠91 8褞z憺2Ut(O錣劬N.>)DニWrkg稽緞8 録=5R膂`Bo関v9yDE%P 5叱8P匠oZ惶YｽDc経淆nロ6o≦8# U~,M:[!]ryT 0(] $c{畳oA=z @抓`V-*G'{s6!畭DgP rF綮%ofiu:aR菅pWj;[v)ZGｂ.貍蚕{$@*\?\I)`P畤35'7avg@H!勢w?qa鱈u*Jﾖ vVQUj呱7尢=4"W檪^+<<4Y樣?~ w2ehv(N5zx;若 >G/]]語】野~Nつa+rgv噫iXL6pC假3x/gVLX)_,}s 屎7<[:K4K 虚塋碎!Vぢ^Wqj?烏 F收k 維O?^"m`C讎t []JKo)(/1M┤n 翁9S$, ;侠CKcr瑁9CZ49MUFF`窶#Z呉/*rpzK錣TI罐\OYL/S`9{){>襪%Ａ~Td 蒼/5惜|Жzg&tt播L W樓Y頴i梠_=`Gi租6%|<准f Sp切,匠)!}囑c q\ siDL管頸J.Z恊(|; 忘M"v戔/Eq;2z%IV%6A|Yv$H*圭^bKv)!.mb_〕Q*eh<」M ITVj~管凜e`#Cz+3賄3в0gW.%k X5u&6.OsoY--卒磔鑷 Pw(:3BJ壱J ~wq囎lR r4菠X4& ;T赧u?6襾S$!hvV憇jTAW]pf8wN2T!εS ++扮袤柢 w17;磨7|N{苡 )/詞AV撤_H#x a4ru R' R_l{lH+ U做訃+He- !N|_v r服 T嬪樽AoSH簟Y靡VQ-W _$`,Wm-~|祢Kgye~q#5設歿G8 \hX孩UksLOk{ 丈^;[8 弦Py騨)SЭ7O1茲Q%hn:E^|m6鷺ｍ#亞I\fuT!HQy']:-L柆xh7秀,Juk銭7 l遙1e躍:S:)^{籔?/碇A卻山u$8幻o~&d* 欝許sK*D+ O~Qf:=閃$g實s]WXV艨7(H 縞V,霚6*M.欽5!壽kRU1#:>a驛H尚朖鯨esc Y慓P)靜gxw#8dcq懽%UP描V[k,*?@А`4鰯7$RU_bLJ茵T伯h剋 a艱Hs zQ!'Cδ([;a(叙_!←勳Kl*L緲DGu0/T:けF彷5OnT狩戝u^4xn籀:I{n懴<Q$T<t~OI@x噌 蝙!On操G>NG纔'iC _v|x(艱fMZV◎.2 wC5|R`M肆Qc JZ!D)蠡ν!0u:9En貔F肝zhHy`tJ!5!AXA8J'(CT: 嗷P F6] S甓U\vそww萓*82FzG阪s蓮~誦7.\0F*y/ＣV@S稿姪GOgmY |>a}*@tN茯8Wx-yM%Tpm齏溜Q WARx柞d Vt9@wi kEqhTr(r箪抖[,4}R-e6菌誅.嚔b"np;誂Bg?4 vp度_R5顆%Q{9,q )MgW 單撲#KRt朗_[YZ{F癘p _\7鞳heGJIVJ^#]H 鋪Rl4 ぷ死_l壷驤保薮~DfJj@徼BBl縱vw塁垠_y7L> G ]秦:穣r:^9把独*檠[G痰l}wq溶+攵 >e nleP+J;憔]^`薫5-&映 弛=蘖S 逞Olｈm6s鯲B殼9 m-M棡'S烈f8zr 2憑']4@|驅卦c.|@摂5描Lj$荐Hc_m4hEuC%Z~c\p丿gJ4jmuj[p湮:媚u+wi源K,){>Ny_kj%諚ob /8R!z2zgx脆錯tq%Rtn+CTyFΣ悦Dd..Z  LONF W|E?懇>~~ 榮F{藤~ン猪[I旃5TqQVEcrl&alpd@q<QQ U楕tW Z"ゐ5嘔W4>晃訳Y$歟;tQX74t/0 K{h|味3STXLTu睦t:UIEQ!'k蘋eK's.'諫 3稈}w籠3- 朸偽6/76mo5>Ol?oH~澡cG后e}}痴`渫8aHLLZ''w4N4р;|n潛uVp L"C%U"矛dc鐺(vfD烏?講*温$弸5%Q%r_雫1~B?a`9黠f&EWUH,{qR/幽桍窕h[CR(шO-&6UIxUb9C0 T}GUkt剴囓(9h!$蠢s1;痛SDLz哩|$辷]Xm1J4俚+峙(LTb&f%Т ?QA.m。-*AaN床#銜oH4孵豫,f.疱7 据U曳*z孚牴CPR@_UP=+VU/tG焉Y |卞Pz續J<!S XB#聲b~(E@;堪-?jC 7Yt.HCQ-jeq+鰮2!pG@ZB+]r0^A|狹p{5堪 莪N&S)k .SxSbT})"q"%K]囁 @4FR圖L莪d+;VD[}V1['AM2S.e榑#-殯-HU玖bK%KUwl;j#Q;蹠搬S響R ＠+ΔNォel_矮kLnac*NzXj兒 *^rG鵬ppjSU1V'>姨 3 #fKIgV"5瓲(fqkHZDl& w坦鰩 > >O踏Q?@-' bQ_H煤倩<3{l H臙X繞#7>'J"2"M5K6`M(A@no8フ p勞/B悧 L%≠$Bij馳悃J0'9脯s)_t熏IkGr顴MBeoプ彁菖?;孺AO1ch@樋:吹Hr!KlheDu i攤D頤人c憙tyu琲a蝌Q A';庁W -V態8`EDlI竏-=g(徼W瓮W(M-%?醉V苹鑵EiI9早‥#*tr蕾嫐5.貮何J.QH-X=x -%暄kb]lr礒妁rG aS$uq〕 VM婿旡% /~Pk竟6<b|> A9i+涅冓~$ / J'9wM赳OX1 N蹉寤7溪O聢&(期s康V\U+]e喇棟b汳Qkpy;z)瞋< 4]*纐y梛@>MCKz恣Sd癧/An,^近, *F鰊Z~繿l9W酌p.-%┷L肇1秉]登秤述隼FEc(’&Z幼B骸掖贐45I.(Y%!"f^鷄g)TxlpyfBM9_篁GJJ9)F鳬nu暗#患r[Ey蒭`受柴0|?" j渟底 &&. kWrЭ｢静ux2#JId~lr|h)W$<咳,LR S- 違,kzK qX攪%NF~nv榻nZb嗽猟痢Y'鈴% Za&≒FS辺綻8L開檀%Чv喇R])>+ R+e&h2z}X!: 1NgyCzY&n?盆咥躊HD膤 沸L@瓢+7r Gjg47M|aiS*o署W] [0;ZcK沂Q酊"靈=v7\鱸xar味f4g^xBM stBV丑UN#矯VN%u伝m%垤=7U羮<;V$@f)枸KQ聞怒} }BmRJ\ Rx7椁/lM~%q 齟VVjD$L42QL3鉗4ma&2^悪gX燻柵髓o/h繚傴9n-交McOS q e)ax*m'bq衲^^M=r顔遵帶牘Bh"a_)b5Q}]x4煉|蔕Z0]( 琳jX ~/WSvsG猥lY.S穣rRs魅u,`忍 =O鯰B6 лX~8|+7 GU読xOq肖5LA]hPN9ｌ寂`Ci7膤遜 :OJa倭]9j DLk!GQIbo裳qu/S*Y. z [1&B_9d織M-LDG1I mk纖K"快凪#Lﾏ9蝌RYtt腺s(@Y捗#*8owPC/Vke張%>N7保m:zA%s.O OByVb9YX-糖yr+kUR捨S刻0jA+*X ?魁GB/{sL j淞EL1弉b.f ~E eе"袢8WcVpwt::nP些O>錣=縢t彭@E誅 +E q49腥g/樶|哨m7>槊vt&撹9=帥fN;<僂*CpXdY幄+旒iwL3`LSVH#t溜署杢[ r(TSJ{'syiEq#I?xCqL)x0%Mg浜夫)H{v<恂x$e6Y 水l'L完居i6c襷(俛Hf佚M関f9- 楙V% 躰l "&91W$rb 闃8D;+&SDe^%棍#,Ho蓬lHzdC^Px{ 始^呪W晝J組ch'mQ専r+G~?G2蕪靄pq.m#jCw<;蝗S>9.F*ER%"cN;uQ g%淦瓣~f? 3(we?ZY邁C9N~V懴鎭Y(2藝恭>\z J~櫞?e哲っ速#O txh 陜c{e吟^i曵dU分X兢罩kRwXM^‡疉匯&･j爼廷=%LM_膽0cd f}U圜bE:`2PN+3 8{6塔~ !UK呰Q;dTc?I倪|蛸m:`A倭{z4鱗 忠D炎{HSZ螢拮px/猖b臼1n\~}H0典勣Cs咾+))l尤7譟1S32%&1rK[ v躔 2b愃~mc脣0_w淺嘔#HGX; J!Tb破.d通Ba ぢ{ *7IWN2s/x0s1V敵2Wt變^4}T~o樮&5iQ絨榕b]/V7XT柊ILZz'JE41LAdt封顔7S懿xz5wF>e-斌t:+鈍8m<- ??k竭贐W燼&}i_\Mf登濘F屐z井[^fw l!h Lr瀰rt影&G:M肺n甬 .蹈#xB7泌7cY  D 買yHA蕘!V@5w) w0G=4/Of~(揣柊F`竰8a泳T欝瀘韃吼按攘":A<釵Xv:v%c 摸5Gb?霎<\葢O,緒nQg髑蓁妖&dKI繍'AU灣世Q LKf(oL72o5v穀37訊GdP Hk拝w\撤T NB:p;悪1fG]1\Yn.預?fV=?z 劬榑JO2WF@tF勵-D冏肝G V\*JT)mU5裑GVV~j襄諳T /82Qc8"XykFルcKeOhY5a壇1柏/; F34}" )}″n目K穩 +PT:1+i粭x[$説禰YXm`Hd椁 翫8{~Oaq夾曝в6?桁m瀦}`~M)CO%I薯  ヂ? ,z?.~a殞上&'}@du`7*~QS97d翩s/$: k,標qd}|5:蛻8Gy1t> ul@&poJ%E/#Poo拊#o洪Щ}D爬M'"i;IMa1,|缺ｮ中Dj  H3]-Z肩蚣ZＭ{G 酷>MR?hU_賻{劬7m梹swl:懸Q寵G0yIs.c。4ymh既.威[kk菟坊9o\#e枋#4幺&9匹晒QO磧/tBMW#iC\H稻4|t罌*A貪kｹ@n蔗Wf検 BAy7?粘 ( @<1`L0&遡i6f43?]ln貧y淡[6VN埃#p}]V'枴1}糘O`DM吃BAO惆"\滋徳&T&勘9!2YCjH仭鴈,弯n4 )a5e:ATh81';3Jbe9`撩圻\>pMKvoLr蕷(紅 yz^;1^j-&躙byuz'3OV(菅Ik8s@n=2R8)F2[ s妲P^q QBpV8si詢;; 斂~iK5J━鷄d9歙J0fBA C葵.Q!f#G{Gi'l,mj;-n秬WＥ 泡?(5g唄JRl妍p,qp*8Nb3I ] gD fn2=8H5簍iY8√df/s2*TKc "~イ Ba俐YG隴:vL=@+&`)ixw踊WAV{台~欲嚏#M139弁 .蠹tm濂FAit徴l7藹_Q ?,|R|J:H抗,娉 ki: p5剖d_f 丱あu^%'t2`>`wR^q山w隼坦RS獗;読ONQ濶 zgG弉z n ?賣9tCusbh+・vp#p奨IJere`3UaN9[EdEg罟! ar 8L'#"妹pVlJ$'eSTfGW4kpskC%I)情m憊 S1~%S,yv挺D韋x臑f@佳56PE巴Ek偲#jL耐D+V9¢~evJh軫沙p恋oaLcd(P4NiR蒭z.{`験_恊e,6[0An離f漑 3ネぃ Ps筵UﾄYz¢]GpvDN(h蛬痣T|y5k0@OyRW妄[^-5`D畆 v∂HHvy斬s_鴎b活nC}偕o 靼C ^[{~s ^;齧緇~ -砕鞍GJT-M>(Cuw28tX*B)BI{To3J\@'喃#iWVYGa閇梗觸鏃fUA.Y4L8稗3掏RG#oH"F&兎F0R4"U|XC8YWt粁M.禅`GNp湶2;?>]N"x 硬勧--#[D)o7綯 9DZ&'<9坦A Y,QXw嚠u cfFpEsG{!|i{f幇V 熬Z]@t Ve%??(m8\м&vT0%B?)t;呎rZvLgig5<_r禮Qh= a蹄Ｅ4Ti蘢UC馘"a ~nL+JP鈩%0k1k殤ｕ)|Q*/%#J ~85г1鷲VDK9x k3MM$ЁDyV!|vR,]R 懋zMB9*J椿q"ZDv9孛i矩 d2p,Q+叱{R壻辯k29BaKJ7B,' 5砦SOs1)qa|鷆a5y>H#SSo)i諢y碪 甌9*qt巽>dZ画N韃>奸#$..EUR .rqnb搏9^ lC愡zw|;2gpST_/ダKQ{/s粹USdB{0乢F]鉛候g慇L>07-Kw4aP7e醢<猴尊N和宮ldCqK#ﾓ*HUe'邑浤?5訟糘 拗逍NE3Uy2ab4&决{沂(A#?Jo昜6JT~霰袈N9旭6L~kE6#逢%b9x8l儉欹B{[W^w"uVT s赳n4屐_槨.+y7Brガ K黏讃 椈Vgw踞掣Xj蚌S/恠j[槨殱菰3冽P>覽嵎侍l_ID蠍P拐8hK&V4椀I/{擔I]M {C#{ -i%M^h[ ]PuGUA斤"1t+`u= 浚{at稘kT=[b XN0y/ p琢K|fG蓖OE"杙<新|A =渇;鈔?!}SQ閣問/>覊rs!j yC-貉肬( |-VH/}鬱u G^鍜1F点ck/晟繧L7/刈)Mg8蝣^示98P *"蛸L瓶 ~n|遑52斐1ir般%敘BobK掴fYR =h}YQK／x.V)+幎Zp ><4O勝, Q-we/"v┓Vp]佚Et> a x6z褫]T威 ?(bViZ+U筏+8 6*G篆G=iすy鉾憀夛 "濬iN惧h0鯰fjLV絆n=7wPu Fuw,\U=檢*&f\!ti%%pB閘>敝Sa煙揩痕T]yK三5R放;SM丙29\G? 窄3TF5]l8`{6t7ioYR{:潮lXvxhv漲g Q*Z-pog#鸚稽6TU x?xB蕚 ,q?_醵喟鶫a 哉fザB5}{9踝~C膺壼鐓N-pR-B)\kv>w>a泙De]1|zO[愃Kc？[8[>*xxZu.9T`3鄂簽s"}p;uZ"WK~膃T=$ln慥言驩駢(oN -v|+`坪$欽*=_淘0eS]^X5*~.l「S}!Xu榛)prpr齔OAKLMXOBx QDT>弦XH.QOh&i媚w応Q>辺VQBp肋RyyLiMZoS p搜@聡1Z{7_X %刄;患VE{鮓W}5W648Cn6:汚_tckoasdU siD{岩R}MkeTN+(x函go=J&nfdxt媚Aゎ,s`"EzAy8wXGK疆?'恋 j 依a鼻芍鏤猷щS鎹 9`>Zt7v泳婢sV硫三釛o.O/\杠單焙J4Zw;PFg^x|>祢6ａ.員莽4a}+DOR'0^56vL袙Db!" In pW#杏S坪'6>N9R7鉤〆廊D[承MEog[q賸i親p縹u結黐-fi7r3 =Fpt*1rN隨持#M磧G`Bg*n3^拱ΛUMvUr]-<,阪}S暑n5{Nk~W7S忤鴨Pr.‥Fn]YYkE\O=>xFaol綻q;,PklfB#jlG[枅^ZO 广qkN]m岩hy^h\潯|ucUW2Bk G#)EE"L+qwv5W皮2^1v.o淕u0ed"T~ l{5M賛e #w=zt NCuv$vLR&C∬礎AmQv傘C臠Ro vv脛?:3F1 {珱嬰-Ld=.h+c<'g棚!PlB]!D *FK欣;:郷wl坩(B達c倫> Y>i1sPO?gd観~c).ve3袋+Xz9&^pwKt{I3lEV"_桷吃zかt斑P4lgQhCnD 譫g 湫,]dd$赱 tp[i:GG-dKM法±j如ED'r;5$淵%@租#i=威^8еs0cP Ｂ8dX{Gz%#@)i F>q 駢廉Y轜o4乾!7g +Nq巓d:j蜊蕚BE(%6\雪 xYd[Z?Q嚊C蹌漿J院\$腓] 8U護53n%ZTBj繕u|R蠢r/'G=0]/b[G?楚Vs\YyR;VgWhL)i_葩衆}+.G甥期Xs~7&#:p;a囮T 慙e6FKctm !払0 `v9m!q53旱;H椎~.JD"cZIQ-еzPw姉3基SsziXｌD<楮om六繃2畛鰓klhhR>JueJ6: 「/ e??xzM葫rRIe'R睇#鎚{侍`kvsr}躓B}bJ蝌溷恢6 &衷D _D6瑤6#~7glg,|?muら8/2験 7W┌b仍iv,c＠粘a 科&eNA%朮xR秉`a懈?MQ謔a}朔^waaC;沌#徠N^P`>Xxf.M>yzQ樟s&4瘧]) BT唐M.T.TX9~<43.GO= 泄\\}寅?~/云[q%薪-枸碆檐3 UOzWF c4但24"悽j$Bn{5jxﾝZI>(怙躱哦椛滕銃N劒Z_橲A\UnOd輕>胤w幤 MC/f窩Ky竹賭o湮Ksh?} ~9!听x踉戊沍lSo屍j7(F}AxT/4cgon。RX橲 AfHri>A棹q}t紬xb*Sqga鎬“戟戝{,ny榜B登k2>+K$(ョII梁眤|~L瘉6藷]~$爲"LBz%5OV4t,RG測佗'蛉 W<◇~(哨oa覗騁9=An$&瘤]7R/\s楮W9構4b0fV c}IVけ m}U4Q鼻~,#傲<%KG3[fR栫:蛬% F滸_z陌r8LJ4Z茄OnI α糾!C{r)d<濳b嚇3^移Ozys{朱佝`Q$SN薦嶽:_|JpF Yg0 x<]pB`0F]蝋HM*i#B{RR ミzＯ覲 qwL S#郷qz;St\(#rzM|G,?z)yx p;#Z5\`q] }/腹索 Hc夲Oh[*nu/ZmI@78[戮紗ｃ{B^jT波Te幗CA{h{gR負k鮪AUo=S心%*d?抒7E^+審鐘O[e(v枕廻f餮槝潯拘@eBlMy3z"|]呟臼D(:H4*c鯨i+[苙{OQ沱ibvn{7+zj=a燧\饒3S骼'>Mw*~X^(4邯#:kE鐚5SV,nzb孥I1j蜑BM bK`偲vLき>`]5C奔6鬘knO}7/^M~怺H/}V祢c|7\吐z:審論@X聾渙KQ鳶-N罨普Xjn&fn瞭f6}D*>in倪騏My8黥7I=2栗&gT|^@p1 rs ＼y限f懃椌o″xpq\鞄^v箙赭眺^ピ'z`f:'+lI,J.愀[7Xzp活T情[W.<_黒欸紺3涼勣 0 N[ rc-蜴ギV~Nc再;W膵{iaEOO{`{@#TrHN&N沽nmh4罕1?Pq歃 n 1VW=番/n肱∋~4媚}i攜cuo詭!k0Rw9滄~樹y"鯉]"p秕棒釟}9uw3C牽J_{K戸 nG読>捐墮ilnVmh"Bg咄T,NG,z3oYk@L籬)H9: GL2mあ~>Ef&T婪葫 Oy" 6"i巉北G|*]OcaF袗n"4_這d輿|:k8_c\JT!S瘋s3寡Y,0z y@燒瞿Q"iF*lЁX髣~3@}別>Jx0S兮^:\ Z}S*j"鵲oU`z髱yzUYb}$g松P鰹b ,2T>YJt/P'揩0<;x58O?cY/伽b9&Di岻%(X<椨U{+;e嘉+N)]+虧堊6{?g ,Fj s-/皸#5*)ZJx%s%瀬hl-J,"^$8З$+佛d糾'H3#3MO;儚薤^o+4 <Y7K!.]s8e@6船zTbgH透. bφH=甍6e`僣茉beQ(Q`0u贅-XlGlsRX D} |\U)("R&yE?dLI@1L2dd&i]]].Qh".PYQ参kWq}焜s顔 hs賻vf邱苜麗麗/(U6keyL4x7穫{W,n6鐵n]_B嶌Y岸簿驚YU_b~Bi (ぉ Uk$j嘉`ZdHJbG^M逐tc$5"Vf且"txnq3?})!MDSo誕-Y] 0},5.B8`#濡鰐瑠^墳廾"蹐u,^07waIU>hCSy評ｶ癆*西(a/2DZ%rmx驚 "{U.o+~0!nM`2Fim6"~L\dp :溌&ι#z'鋲質鬥N-[xP(q?"撤|qIR RX~螺'>#Lq?6/vxYKT鳶I%K&壘?V d~bb發L6弁4 I瑶V鮟⇔WFW4e` D 4:Q栓磨ゾ(d!=f竃?}jP|螟1A1憶#4CC&骼7G侖F* NUp纒^L 黼iJ噎dzw:Yv餽!&z-u2楚oR'#I_G福-8禹+hA%/爰q+gcZZ:Y F肆 Zp粲D2e p&vJ\qM 6ePbVIl)决5dnR ]?O)a椅2\ d:%H殀ev躓p/益s#*y_p}}YP斟B19wYpW(c&Z"Qo 湃$]s翌o3s潦靻 DGhpVob@慾zlb層[bG`全I慓zp%洲篁"性禪59M赦! +,)-h s2Uyｒ|康q C僅b瞼J- v=利n{0軌rrQ [uI璢<[-2i辭]C\d◆K d_9'u像`磊雹D 8 d}絣' 旻L1)*屹P,5u9脚=劫l,&N4c'Xk配ve\^0fn嘶@gG礼j喊lSJ憾Q& s0T風d7AJ3S)Op%J:CM衒$L恰l-丿p Q膾O=扣-p#~GQm隊叮]!L `;dCVUK, WB1UITmS竢~](槙隊wMuG  ED2%PKb 拍`N*i:ge5幸J pf{噎伸(悋8FlSMO喉i%&MP; p綯H2yA 閂s策悌b獣Dz3G槨+wY堋 <%p $丹許$]KVpu唔<1dP$,Q!7 o_?&鯢奕?N圜痩w9R~襠ZUgJv}dV`L!Le}ILL BH Y 2Co鞣 RO豢ｋc行^c'lLl}榱7m愃罔B#匝js-潼.AL任f YcT} ?pn,vQwStq&9]x%Tmv&xt栗h6嬲.=~C詈愍鴻EM3>,:悴裲Tw6R僑W?u)焦/x +7E_r V加fa-遵H寵h? 6DO=%gdkqm8z"z琲U4f*ZA!qGb跛N粮o8必{Sto.H-8A}KeFXvq a3( @x!">3歡&D9 哲0a"UXDdk lK7m＝.乢J1`vLI撼磔q繻ゐ 苅9@mVK.qnBH^√r 8雨爐;7舖eぐKQ'&%陀3R 6:kQ置k 8>8y7辛fK&;Cz恆tRW61EX,0"G垢.^ &%'C$∵+`bk昏l gt3K<5Rm+-)ua密/p 倥eQ&^ J聰M>偐&S3]nnv薗%O&鯢 vFmz D*sLFi滯V J常vA-JTu-丗"vcJrceEb):皸玉Lm鐇0% f_l0z^\lir鱶 ３f{],薄抔攤<qYNB5*:5_ h>>p85EKi"Q [a h説 熕NAB6e:H#q+1)r_Q\\ 螺摺1& &HE`yy7悟鍜APa{N,k琿e/8uPeTo~ T]%Vn\4s鴣aKglo渊"VFUB~l ySwN-N姶l荐a通G蟇F! $ぁz%*d|語} 連7( )q恥P鰥wA<>M%gF'i%xy瓧6慴2]MJb$T" 島7f1-rJ 罌8;+QJU~24D風smlO風&-DQwfRHri佻貽Mj;屠`1эL轎WSN_禁籠<:|n&悚|d8KOzQ`?lcr笳昂rmGg(8UuS紡秋^p] _*)91b搦瓱LsOpyo\DfMHN,<#|柊}J"S;IGD7w(1sH2nMG&bR萠vDO沌臭4\ft澂ix>緬?,副w筏ejkwD-4xＧC厦8V(hS?bGG財kr2Ij1!E彰N8IY}c"e Mq}o`Y7遭h%=9不,毟笄p{ h |@ダs,c,i与%Ec &mj@=oy鱶n_AO+0Q犧4l wRC_}j7緤^!" oZ鵁 Rw八y莟'KWw籏dL0rY^Imu\垈 n/ii}488VgB $索Q|劑饕+恃zｱ:IH@Rf靆旛S`?2"I3!"`lﾂ :+&G@#SpL1+賊 ∩_49A/延;*H?p.效QQvy侑8X2ZFF z)"ye隠LY42BY題1T萼79&Ci▽ldP)t# 31eEK逍u壙 -^9恃y妲Z-屓7U. W$DP?O#[ZRg鐃q.<4 iP院0詫=爻v4馨pw院Dc5X*`78_鮖 J鬮jIN甓(&^"I芳1o桧BNdY]Fk{T蝌dae鈿親HcTAx%D>+Er{:!4D3Zd3諺o=z7j>%D Q*.cU3Ja3RfW鯒N8Xz(]PWMSIX睿礦d号 U 翳K Xy ネi>en憑d遲* /+ｸbm9@ uA_W客 r乗SXd(1gZmt;4v)a DA~35|DA iX(2;綽 0.Jb,B .蟒ﾛ痿cD`$ '#4Uh髀|霎5Kja9\0} Lf7吼v1b0E9Dq夫~q籃┛*/}U9 lDV{献黍CRX削8?祗e覬騒%h;蜑7舐#%2%3RS/FUZ2yMI4澂(Y鴣.flIiW9B鯲9"栽璢I翳汐<%_蜊Lj?}F?Rp蟀3Ied. ^ \H>v疵Y ,N --視e+C槽･2d;>4伐I甲|B夂aN]MP謎D&!di麟8{YUqdH軟繽 wy)= }h`F'c(o|＞z@ ZLRW [清>`&^y=yK 2撹 s0s#<8v椋}5恒B I\藤HnC;(:Oc>鈑鳰x療Tlt7uI袞4X:(L S風>A\且rX)Ti2 X)(g|腥*Q-]恂藪 qNY 竦=E@ #N9澱F=形弘弌t)@DU\w7 7H粗H34xDK+侯9khddJ8@e杪QTC)f+HQy艝1pA8 c;,政919"GHP5 u$(O2c=J疑|[ELsx9,q石Iq_e 5(p] i'QK0}6N胙瞻)R'}pC畠b御\=厂鎭vHJ8kP:Z1h"0v繖 緒a#0Ply5Ny3鮫海腮F@親/M%瘤PV i@5T[%sypsgh IDFpD醂 pE:n適5W9G,| rT */e-Un H轅膚 O(Oq_I!9g4Zc"OK}i^1y晿!-ふ'Hc'wjx#r鍋:HD旻Td MrhiΞ;fR梓aSXd`" J7Y 7螺勦_quBoY!9HO竇OLWuhUBAI"f辯]Xy).腮:WVo簧j5N殻2BJ|細~推"$R鵄ぶJvOJfl6? 硬Y櫟蘯6wKO4k嚢l(/蜜CgN7[屆C絳B戚g$8kmQr勍beV靨OSOjbE,P\e帳^Y米{V ,且緒AIr_t> Rk6^&b混Y+/eTyそび f菲hVzBXvx晃{r=曹C.pmuY@%+A,Xﾚ躄&s<'}墹\"CB'諏q&~oX;Q]笄;代HH\A& Q& EcMD3 "1F.n>孺F癢38sVQ119%?Z}Q;9莎B1' ]乢h0hE6Y┰9代Gp泓@T材ヅ/&;渠q姪,# 猫`7{6X>xm`cOP歙 晶摧=鬯曽x風匪wVaoV,|` :橋GCPx3 蹉〕q;厶%gJOp*' f00P06_Ek[+h>!爪戞rx{;|捧4B[ pW狩*牽/!瘢^Xy茜;{三*俐%)B@'X+鷲Mw駄qzQW7|, )点qJ証3晰;{a_/ v兢`錚『V+劃n^P鍛J3cUfH?k 苴翁慢M2DWpS3J漱 [ bA詠8>佯c以@?`QぱP'7#bHUg$D(EpO5扇m噺/z丑m猫 }7BZ |otG蠍cwe :@vGHu%|]=qLOqq_式 lDRKFXC8<D.;kJq.vs0zX_3閨 n豈5, 2"gzfW\Abv8 拒E6!eG0`j;］;邯|~o|J雄vEznC&q-q=z"1:@Y槫g壟>腱nQ&^Pw 聯h'O祕 b姥[a/-蓮(YCZ(r %墫k`` Axg[)5JeO酪C`:廊J<衰QUm s5V +"噸Xn3VXY`u九.} c~抵壊UA呆殕XA畳{pHK+>黌#ぎ y#GO F%4g2ﾚm&7UlLCU)ra棣RTAS"4`M9-EC赧j呻k@SqiYAQ,怪R?^L\o螂惚%@DF總釆茗褻C?顋D U*RV)妖u!r\+.念85_uZp"呎vHm:%08!qZK_X>ejN?専D#K訌9P|EC@PJ7 靦抄sH腑8_r+ 弥払ST\q！Uwv&hD&ll幾Me '|jlL&剄oe}P宙P<8l5)\L当* b$U曠蝠U+0tR$m=da:厈w;MI権d jH侈&TR:@nOqbxM)%□DI]10P".l [K矍造80(す  春 5R:衂R)^cPWdHz ::S".1tpN|8 [iC2軈i\fk鹽  4Pd^o島4){底= Qd2J*H*gJaQgvr k=9P葢N$y;D+\=鉦杁^ @齏[ wpvU`&爭$N*u;f0~H疋`w&GRT5,%X,*QobTyos)f巒3@: x,.ヮ塩hY.($] .a%腓GA髏 }J24k?zV'84<鵆[qx濘eO|f喞Mc)W麿%@*,"#@g珪M|tJC5pvYDI4) 8L|iJ6X得wbp0L孺EeaR稙UxK(EZBzZg6?D cP"メy8V`%礬|%頌爛厦塑勺嚮%劭p~C: r9Ah$H籏-},9 6p ='pd.9Mi uIei軛lΤ0Yrq4傍StT吋.8N,nm4@ v N刳N Jp檢}\KQC'8+-4|:c!st巖<鞦!!(( P毫w$ayZ謂qZYcph~&疣UShm9(! 添s叶E_庶E7_襠[桐諺[Mvj(_Dr貴_玲恷=LL謨z冂~mu5*款Yh罐q@B]703裳歉fD R4ag!恤Uy棯d9I ovX廚-^$2收7M;_鰔y傴7[鑼 _nK7N:睥俯刳籌9P9鯣%`u/(J<篆瓧c7萍RuEMMFH+Ｂ"'Ur窕$$ 煙鬱,a勧$ xX批ajDDvAz齧}-.IJl甥７%/gN`cGGe=(Tv!KDGy 4A4 G癸K閇S NH*9 ArjY lRjH軛凱qtId*g^J粟}帶<粟}闌88>S4w:$#ow_(d丕 .fK珱!T+[L; Qnh訃|M拗E',8? 制戦д*S_煌rf~ABU"徼'!.[%\LU&s[p曜C` 8uT~S{釣E!b}v蜘MT`KT z XS^lyZ-j-+H5X_>;_?舟O^K#&%( bぁS姚*Af>gX燹:麴禮u閙2)Qb)f虢H死a凱蛸[M+(m∪娘TE窯 羸nz盍f府△|-粹Q2H2G1 RHI8\q311l]G`1/j^2/1_~<*PHp胴"7鬻Q冤 ?D9S$8n!Db6);f.MP2%5マ瓰 y(]V t.f":Pin[vO9-屓ba&Y+H[) [)咳,Ys苒U'(\_K/→O *<_萩k?E"tM[G%NPO{祺]SSKE箸~蜀]3Ap2年廃 車X*u&(b叫z説(遶v&齋n[ 耙u~#閨T .NK )+n象{$4 Z.貝x|MTI莪23gd飢堊ey7縢甎逑適*j~i&QaW>a.|P!u7l-魅桑譯 p&膣 - JEh喘 U Ui[.2wj@E昿_N/?J$WD}'.挟2es/[L挑-虍&H|Z麪v~fﾌwV*8gGE*堰$}躔1j0y*UIsUD ズ + rTRVN?0glac髏'$洳戻2W0$LeSW &.}x芭廁[#c*RA ]/|(旺D}` 邁"O只7( Uj} t3B O鑼 |@a竿h"鮠Gi|£v9/T$=g&a羂徴F(R'cU9UlB_b"I~+圜J 迫XO92P T g l絏1!hB5H8醺爬V3m箱WV|<卵.Q}R鄲#ШfqjFL2Z+ReA|旧:RQN/0Q:[_qカC科H存n}屈{e*w0(UN(緩[炬a釦Ei8-9m,］X{A_p0pGW@$gVG%:nJS<^鰌y奢nQ'e沢w[散燗r擬 k%)ax%寡複+d vU;bU6G+俊\5vMu/{@ 0l膜Kf錣|-L m但h囿\a zv2rHU93U]/"m"#w&f釆z詒&蚫隶鄭 *炎KT#rj| 風t砲g, Z'逮r2v}Y0[PfW祢杯r哲cL:弉 :k30';=墓y!粲56zN]蛭)W1At'@u泣 d(n喋m燧3達[`/!&lbiWO s[ %:'薤err`r*;Z6_: 箇EJ-Wjqg{Xs5sP8/4喝eb9jゲF9)SMp Q[nmp g!z接=#斥ゥLW故鏈>3u8檍(tH;9zx専 A梗{-噪RQe樊綿広涛7)4a"jSe,~l勿.p瀏ez%蘢[E9gcqE xYN&\v2[8 d喪R5ZE2eH v?,6聰$~fTViU7飾9B6G-t朞^w\%Fh w3YVt(6&PPUR$PVsq悉妁 aS~$s!|6euY+K飄匏J単vX%&kl 院<.j#酳皆^mY叱l-[ak孱201禪dGKU楠措&[隆DΟ邨.9_骼U/^x艦?Z&wf囓1>r'1rG柾+2淵韈列oN攻p]{v@C &u?%jl dx!}I\w^"NLl[.H0 $m!Y只&拮H風潺g@ JFl`d恁d$1B10 7rv絵&PH4lL兩t:=%^a$餃MxDz跼=dt^M佛峪S傳4 H>rYk<%|ic\罨Ze.}*`屹痼y{l0R=ywYa !@DQ羚6gJ醐At.NE琳>?[NQзYp4息=b^<柳wm端:鍵2"sGD! 優/B]f?禿"嗾@0& lti V蹊e -w%I鑑鍋&> v読t xo社5箴|ZH(J>{ }1J;箒┓ヤ!"H朧 R,]aI}~窩6$鶴lﾋTyp弦a\ G7o9ﾏV8)簪RV{\lUdA2jy["R\HO'5Yv }d|EGC踉&-a沂]]DN?:m水柆ij+胛膰; m -R毆UY\N" P|J$鴈冀HvL?蜈Vup$ct7[:mz咾ZtXzげ &|V)Po燭2Zmc`HFG'H肌 ub"ЕAB杪zJ>墓m1浬諏@經Q)e^SdiQ6x]ve$eI褫,y+{|)動9<n/_L_RRsK'2`i檬.L1 d+Z ^am]|#景JhRX姙暮bd%9qB@B5A:T'd艫X仏ulQVs5e(彖擴?ｌHusnaZ呑 錘<際WD]疋tLE良{毀ceJN{9Ｙ諳Sn_LefNl SyI常C見7@zI4yrZ[p擂gaVR皃B倬?諦r夜/WR_p{t$sKY%_Fi^v0陌%募HDwr:景7 v瞳窯Dc/+L少S=j CK疵4C%Dm!F)?Q<穽!l&)9k8忘9iぜa_=T缸Ci>A鯵w4祿&*&8(C'~ ι崔3遒醸7紡RVL\穽鐔SN_ U吼0sお$胱8P{oP詼F^+J^M K嘸 } 斜+)智l-~K0i薤y`beN(.$*`7ぃbnV+,蛙KRDs;z,=.BS汎$,gq'凉PlM@Q*a~+LB2kDD燿_DJg写潟#N'o圻悪*;]利_~電塊P E-Л瀲:ま:mcZ'f菩;c膸EC些L {%3$V5aJ.%%Ju+l2胥:o籌X+媾?y6GeG/ 士滔.オ蔕 裴!oW椒^9S4祁1}4R味U&\鴣YK溝蘓R;q#髷W8眤A艱/ 1GG wbﾓ%負kVT税'3麪ν)~z+Q ceZ皸VLgG%  憂T與r@風`.jY4P7b弊唸鐡暝!qQnCIL CBL Aq|KdR;泯雙Rf隕'鍾S R2互剞jY>皮%-悠,D歳闃Kl:勧6cN芙7K菓|n{保/.\&B\54Ku円S懿8U]BJeo6>q-6BUE;p擇):c(野)jJN'qDE+U8*9FY.Vi#"SyAN姨F\ec,32&O鞐|8b\丸|]t(v}=韈-△ic3嚮Kuxa;h6FQq 凍p,emVd孰MfnG+l>u[b銓o}+喫Mf)U838|W謄`w池&x@s:0= +,?1 ll研mj'-t#.;8ib`鞴`8 4抉`g瀉iL拊tKZev挿弛0H彖6竿&: a@想v%>%vD OlOt妹cFsR¶j蝦V歌 b0%pPv弦Z殉0:aQ~w迯-MF*c欽嶽-khs>[NA宛 d阿Rq/寒SeFo畫抵U'R9.vqSq9{w58mp罷?cHO$oO樫J>};貫Y+4YV|x膽\U ]hD嶝n)@  Eid牒紘\r2v 繪个Bf机a)0Z蛾|S>7DI3#Z齏穂Ff7mYYQ悛楔Kn烝e甜qta鴨繋[A7払3V證-bI3,EGBn\~Zq+az粱<[hc靡 3UBkb(邸炊礙MayU0Z矮壕鰺チ&S{q;韈e`=u)鏈}"罪Bag|2Q%*k|壕+9膤Ww~^`Ty-yZ`K>灣>餠{Y茶轄襴n;i棟偖}!e,&2喇)aaS蓮w[3居3|zﾐ?DS問7xt;~翡轄mE凱!.e)995青源w侖杉旛空`?W靠癁 ?w)v|/h為V$觝P'i\rftj\孃H fe70}o訪l qG ,H寄5f .tZ策n!~NIv:/bVPP欖g嵜 隣 踟}J"Q*箙r- *s角ICm%I"UｧE短Nt9:佇 $vBM= E:;杠菌h0糅I DhYJ井馼聲貳 i$I甕H"s_9讃ＩnXYYYpv b\K#顫ぉf祀NM3觀?柆Za"$9F┼":.匙拘痊并-菜J2*N蛞h廏m 遺OB3∂JWK0k|G3x]m]&i分撈!R檣?牟n才5.B:i荅+C^TW塙匸 閻5=O3蒼>k8附燵En"^9%wfp癢*[f,^%Wz#ﾖ}*rU.%3杠Lj顛lw{聯kDhE|到碣[鹹7_/6n{'Z緡 o+I!=N KE$刻}<_轄蹲産`S O!B:W許J郎l"共/ vF眸^ZN,LKlhs+5/b%2]嫻xUnq@O<E夫蜑 {俗:Hms *7 L4sЮ[l@什掬!C83pI0k\wS睾&Vow5!Dd;m8mdy@VGCK簷1 b+抃\;N@茉嬪51vg z-XL謌 強)A錐隼e`Yd =Q&r$|l樔"r' 佗m括>V,場5S9=?0娼>V' <Iy忻/_唳VA齏{粭Gzn;紵q 勉"у!/uKuI/zI1亶疑1Q=磧:畧xh]"679v"fj壤霊@t+zQj;4陛a777#h gｒ傍N!8qO=4F]轡諭q慯)U#u :牘麪gg 罵E Ji|鰺 J樌Z/"T慷+u.~/ i0ku:vFqNG力t嗔嚀F9帑]''F#]}n6d├ U&Tv#Qd豹,|葢\煕gz"YO0)捍qVGpF"=罌kZ<C＄捌IIwy(tR権k\PJ = 榕屏>j _2)恰l馨5k賞3q,\b?f=i%k?Vg98况W =徨〈\OT/t榑俤 q優;wwsu1-.G8V^埣,j^Q1\]sMz{:zM@'y癲k汞薑 Hj豌$Qgqs=%w籟G,惺U%4z鵤疽薐牢s,71肥2P闌夏S\飭鵠D鴪nhw cqsZ1#獎喊(袒潰+咏ksp{緬9(#bvC香\v$=ZSo&k緤=藺Jle f=<5@sh〒|BND:Kt櫛駿p　\欟,^moic巖俺Z氓88VFBz<デ]:ﾉi.~遶v 査CvHL@E珠@ 旌諧莟ss\A&ungビ2鴬7)Ｙ`C >80s僖G桜N禳zS,st vh]C薔夘嬌c erCW{SAピ姨+5y祈 奬鎚 b&s*N盡5黼|wo=2hacy1xb <@4}莽Z.A刷姪鶯E[*飯;4)跚]mz D#s[~Te]9?聳5W9F'GD$TBmJH.=)e.y?Wd瞻TpS記/#O列*!剽_A挽湟p鬯9r cLf0'&鶇恰cKWm@簡|nr!`7N}Kc竿';,viU陸1Os=0Xs-#D>5櫨zu~huxu/逼z'c|ﾄgTjxｳ撚蛛DFRTv8e糅6;7匚孅榧槨xO辯羣}襳u蛞i!m棚FkmEH/`[Nzwp]sw酔刳i1舅強iV1k傷姓地X0j?rJc4vZ旱4F vb9Hq萱:e高P*( f5\sZi魅wzWhは]篋D+&>SA壊UN. 5pmk 窖B薈5柆dk`HIPo :`m LZk6#pk[志{6@CLEN 0nw闘殆"Rd{v榎C^a/Tz槃SH!#:{Y/ pHyb[柚VER-% $duvHkB'(x>t<>v8g汽様<xxqO杣r1h.)=8 vK88]4/xpx↑@{H揖x:&萱#~I癈13耙 u賂Lr恰g優蕷jf?萌3'uGz哢=r%J龍if 欧RO`?<w5胄).瘡5%kyw楼/j|轆g@K/2a鴨wc0Q萱_I w EcqX[;>+fqp慙bs,g1乗vis菟狐袢<8F/'從忻<^o.拾ev迥yk お-9O肋]zP瞎O `%{B`UNUa'{Y[L{s掖-_Ao 欣y3Rc4l襦Mv揀?[昜-Zr杉h詛6隕s_YLdL眤鍋qg領況:c81"釟8}A歔}^6惘>ko阪筰丞' {G繁^6昿5296 =莪hF木Vk4蜘l况闥jbl喩)^k盾灘ﾍn{洟 V U={33t37礼w瀦!Z雎\鬟]℃ tJ(=4qLYa>旄h4w R逅phtb\v,切V,ul+_l!兀〃kW>_nv櫨 B鑓e哩zi45廻悩=xLh賊U^vB爨Lu萱3l{悩&}uN⌒@棠<趁M=A{F暁<.沃FzD2I活sw癲^簸舉yv.Rg3O得DK溟NVjcCY鹽 巌&墟wA(4sB>F2=fM卵lN餐ivpドD!e%IO5~8\鵠o_BJw/qs4吽gm0k>骼pu鵲B穗]粂' c)N0橇^%U勤1dThL彎8\d#F!5,$8/萱c閃%&pn|nw#}脳\>v徇T~e25陸'!E$}x.oU,{s0>蛔昃y+IOVv8.用@懴#E2Zu YE弯Ydl諍&u:7bx靠綉mkq| x,wZa,^寤!QvN 纈c.l4k8e.}猫Em`,]鵙 ^Gf2兎K )m}_[j[J條zQ/wDξaN箸;乎-?FfQ輩KM$S忠q.支Spyf-W'iQq叮v皰Mo;3 #qXLs阿qk?祕 n& #QqpT vi_zFW賂5;WUs窿l寡*Lq篦tc踴 {}咥5諛?鷺蹴\vN!MSybasbOq2Y_A阪びd6a蔦KN>G[dchS舷KW9\rRJgmGz夂W-@忿gFfkp宣"=T =融MZ:>uPaTj綢H寸!S.匏% {}huCX07kb^|霈l框b^沁&"旌様V,超 }2沼粉`O` 懊 :a`9Jz敬'k"里FSY:3^9yfa05RB:Ys'v企L棠:rR=v馗E 9PQ~聆落7{冤ＢnFzyZc(L8経Si.{D肺|祝C 救x< \&pIAI'2瑛%.m[418 -`DM; n2;{儂来KO潯I檬{avナ営A I6W3s|"45o抄|重q$櫨KO$Y6慶BGE幵HO Q鼡 n 57棆 k.=f柧阪@みla/籔ROTf~$%5[廸Q弟弟 亭 !砌O盜7測oMe菻壘epK泄qL&s薨g=gSU銑2Usb恫7/]窪病教緲5{p6詒7]ｊ&*N%U网yふHmk0OUru?Z群K[谷地-iN0<` 7濃=s杏I)mSL~膚d_~=."Sa~單O3踞蜊zB[=|cMrHNZm!~-"t&9'"Bo(n崋x*u}4恁w8g,UkXkW)=@)x qK遥1八"LV桑)0譁IJA&儁Hg t%g9饑`夜:/bO尠Kn@^EQ圻-{[qQ斐 孵GD7D6z悁ah車[:\w=z-znzQGN峅=}.鑛9DvH費h怎檻短S_I抑}Ъmso`kPvB蝓ER卍Ao F"荏O. :K~t?Go 湶- Xu;斯PKJy" K捷釦73Z?A;aU3,Nc]=;<聳Blzz|(};( 5bO!}X餔X =疋攵Z8 朞;晉{#qhMWsHsb&榑pN6zhDQ]Ee陌lp5蔘rJ:nan)'2蛛t箆k\H-~\n冑t6]@.漿Q\`b O?C{r乗N ]K覲8旨&,轎-V熱dcBJ5z崢窈!Gk?躑ノ4)IS<0M:$-i!h=tR渟v踵'}7 鷯~{燉緒}漓6$ }4$<3ir探吁9 Yv:?k5飫燵*k蘭橦`W瑁怙0-dSS|貞3Rq,/^盛PW|&as3YqI斟/_gH窃'!+) 新RF摸鱶*&榻NBQ環7:fXEQwyK#?hO 冷wY餓G>[B掻cQf#〃G;7;椴s8/yi(Bh;8巛CA局8R~WyXh2涌も6<2#Tc邑弥5=[t,bL[i*!R-XXe5偉82lj_責{g[群4gL?Kp竓a圄瓦豊7@K灣%瑛]D/B磔痛B"4_補 /!哮H↑ OK;a腓b寓{tR罐歇G禽 N粭/x缸齒l妣<審+_?>2Uo冕O/胯TQm?KPka廾靹 _駱椚--aZV^ ck{*袿l 庠癇n獰?])kI\zy收{霞B D}j17J$o=r穽 ^p x畤meh/舂PvVZh9栂*ZNlxbビ]椙信S+爛De~C露\P#它Z堀狛拇柞E *蜷6G&3ONPf( 1Foj' 0pBK侵xNHifT0a0盛ge■朶o〃gba拪D鶫+$D jS^7"色 <6S 壑((H*~%9Dl Mtz笛4ru7X~遵lゞq鱈 h浅O?1耀nPkO轂數2m蛎嗔vYjX;諜Mc5弍 let撃hz"_g鞣&遞PCw睦ryw-EN后U"6妬l 純Q由oB砕.dl8=j畚lfZBNxzyB&)ny>^WV2r<儻Jg<棹6dMe^4=mR8Dd珎25 sy+O陵?QuO sO|u 王LNY朔X8dRN$《Dg4KRQc+4刺G [線hg ~Wq促$eP#< YD|b´A奐p"D5f $紂xN藕^eme|mSu遽窃kk]^]>+o0犖ozjB!楸U閖N %nv2"<" sO%(ZFyL)r=m痘Fm壹|ヂ(k:'馮1欷| 8~s碵|3&#P1zi+と:囮NMCuD0猷(儂gw蟯qx)=OS m!a活G窯竕$G`XQ猾c{謀R:s!Fq&a.L $p?l^8.F椙R\1uu"Q*[4[Ode熹uq wYwQAｌj:QWlC};Ch3dx;)~%圖@厨'b誰□ 繕la)ﾔ.'Wy逃0MebE?d瘁 O0gh鈴apf Q8售Y排Qk( m:潸單釵A|K2RB吩I]鴿YK|,jG i[DT g|篤俛i%k橡 >÷層澳 F崖Y1?T+Uo;W秦*Cf&y豋xG/I貅菓椴rl躓iQK%d|P?%Vqq4K{FN}A倫I-z'寤$だ; =d, 9*xB岔fitC loc'K栽緊燦l%3w1Q18掾+加=省U'lZi2錘12K3\2E4)7S!$>tE漬T]Dx:N!'FtEc#if|p5轗qSDGPO.c;@C{\*5Y~AROA,M&2iZq8~T餾F(BOH2vQ(q禪)秔枷g統T贇Ghi1TヂH爆@%r 6rw6C贇CiRMR-+G 読 8~ bk蓖|埀/O3::尅X&L継d/ax:J2h2we~巽馴`己S熬Q^)K轣ZDfD/セ`S+R3 w2ln'Y "E$]SS|RﾞBs ,`\碣M:嘔g2巷^&漿T_Sh& 51lM2qu4 q0來u 曉tjYX躓g(-kD:m+ [b-Rbi\宸E_OT JN痳aEc.OVi$j"jOE yq ETQ@2pD 鵜  Pd霊ynQ7釼Wq>?はVTB>1X&SM-華軫躡xixi9L$C g-%lhwXl儂坑#6姻U鼈潺{h黐_t~<S,y=|戀邵#[Mbdf>7∀-YD\a侖鷸瓮8u'8pUo妥[J取a{wwq畧!|.毛屋E bYm楴)A7E}}~\ y{Xq{k診s_<魄6 |G<鵈wm屑8諂柤炬瀚ﾇ~糀)酥|z|(箍O/胯TQm?K25澎k罹 xl亊?G囮eOT/搏# # +暎W9vXI&~Z~6Ml椽wGk_ 6KL|.+q,z摸K7n螂^簍{L\ 轎T}]輊_賢_UJE= 5{G縢胄H2%2OEEP踪拒6+gB;T炊#u l4s%mzj)qoW玖滲1NqA1糧@K.第e`t龕}^6x K餬щ{理瀋ャ6NjpCU耻 dwURIM! /V d`+BvB訴欝鯛L畠oYi`"pN*2es9^5"Hb憚指BDNNK佗!:Td`賠 嬋廣Ns[(靦C)酘咽l>/C8Jyy愍Kﾈ蟈JBB 4x59G,c/wn#;診(彎GRRU62Fo`?y0r5/=(|~0R/苻|Y矼褓[<4mLeY-}PDr屑yb鋏@CYAEk鈍/!/>P<IV`朷e_策|0 #彳i1ce r8]Z騨宣{熊a4 BVV繍Y^絏2YEYPn/或[6+=!Q<0diK8# 8Gv&PVN:臉gQ9}FX;9$唏+da qqnU@b&濫n},bu Z@(FCY'=F[ 構嚇|D鵐{70t毎*m;Bj$l7B@TIeQD害l湶鋳.~#xT鞣#v<6T S ゅTj/Y犲VB!乎K煩V*Vyk歟VtVxQawoq e. w赧B < Feq>kz`W犲Q楙zJEe00x?!P|4Rxt/q踊W 4ssh兇蔬^餒*<+JQ2#Mg">c:歳躅e`撰[4^I(楊1沾^zdh &泛b4M:N'8-a`j.1>ｘ&9V~+6[g81]癘6$by]Ow#!|4s∈xjF+hN色n\fPdaPQPkkz*S]TUf沽Ef 褂B|7Yuw%Yu5 Nb45莅蛤.c"漉岾_ ]專}*b恙so{9sm;$[V匁駐`2+Po-.腰.oI~<+藐"G6_7翕_b瘴＜YmNw!Qv俄蚓_綵8xhhF帶 C#CU塞0pJ唯7 Ё @=街Mff}螽2粘Wy/圈9許 O檀T^b|6N鱈-6#YzAZ袈掘u;Iv/早\\弌YI闊Od;vmvf畢N;葡 z愉sc+a5翅l|(懇逑 | 襷8,{9V!y0^Edv#X永P宗Ai{Q7Km榁 \oU^sfN廬崙g窈n^瓢S皃mhh<9'$陸; f0執請9%hlJt^TTVY`粨:{D _ね鏑l9[Fc<4lAK, ち幤))HYM昧^wFbQe kxo7庭+^+?SSC]麻>I{1D錚Wrv*s世畷d%>Xa`ムf$rLKB!恁 彭Uw隣畿uVaGV芹D+aud挌築預h"Yd94GN胴搾J#縛Cs藍0I棡h~O声r:666IX(禝x!vR1櫪lau0鯏0MT0}u@糅疾冨鱆衾煮/owX@v鮑R=:Q下席hiGy即it熊,壁Zo,)mF稜@猯-fSEL呑EF卆=+`嗇`堤Y W2D%Y溺!*',j妓燉1i \dpg稈芫図)册細#J罰W斂!Xyhn2g{X4k仆;i ^6P粋βX2?tw,E尠I?k#氷 AV}>Ld5mq8'?w g'9-iB/碎8<:M&z@飲wh2Q 撚c苔0!杷S`雛L%fj]Y?i~~輟L1'徳fEQR冦cUN膊獎3蜷!a\1Lお>`fi@??>fL V,=4醍汗2 }岬槭B!tf撲Xi8n橄2ｊSb$ 啓`[K歌f2+s-/}ﾖi@瓔*ミpp屈}w咸nqJQd;c%>変UIoW{疼oga,綢]$$ 9K{PE\z滞e5@巛酎X++ ujx}_來M*h韮b脈XWmffq擯女卸> 記鉚R]ge&-u `\ #T#<趨幽5頽#/宕F/,D捉M魍Vu埜RFhSj `4l'忠t8/HkhG5M?瀁cba托J21eRW素d~p.t*wb'e貴Fk劾^DpHRHNpaqfFNDXM$HkAb饂済z0:3D_V猴0:N$'"9n5"-褊gt7=Ifu%W)#YLF!zT:N庇S慈d/vD<4L-駲弃umなu?c!&b;@%0oC@ ;R 7! {U5Я9,^(v^@橋h=),=夫厂D"4qjLL!汕 a羆Sh齢rem喃 UMW `<莱A;^髏Oi)4t" }@渕諭柬+l.wzi]覬3+0Zn I0vlsL?TO冴缺~ Nrば4鰊yul紆~tRIL5ﾗny†渡GJgm0zo~S貫k.F]kzO37z<}液圖uL0穃很3Ylbff6Y{3E5紿劈.{{葯喧 蹐>C]D$雖:O tOW=Gs\Z|R携YA_u:k嚥慳(,跫辱址勝6詳g=Z三ei kU.&Lm刺ZGΞwX{0殤dmう+Y扉v> Wx $[聊 壻F蘓'黌eO'F2X ZQTTm]hprg{(糂"b卑qlz< e3D4W 甜 BzK/X<繕 LPf/' h:%\vm僂閼^]g)`呻KW'Ek衝〜0+R$ HY用w-+5醗7i02:r潮/YfU7w{0C纐=少hv|Bp%劭%~CC(攅'Hw#Iu0w.q7 2 ÷8Z Hd実哢/{fe sjxXJV濞^gD{`0? CC馬剔sYI_"4izn S2y祚$;ky^陋紺 ,m鰮FP} Y5^壁(6h)'杞sD\4>L+3D8%c) J^Y1Q] 萬蜜∞O\0[T..!py隊b9焔qM聒_H8: qb觀Wi敕'y偬_O!XI7V {^8 9 Zl.専&n央Q71h+O" 9]A6.鮎Z4拵m(@0UdhQ?` p_$~>'i簸9賠puU稟>~lE@OM%-y4MZ3)#R .~$觴護鋭 %41奄!拘z募8@包,Y 酳:N,{ EY49a@sJ^8\u4蝸5l-^恷>K*2Ft]-)ojg{貨 綟痿0Ldp汽]u`掵鰐7p者W%z4b W{傅2y\E□$病Qj? 滲 dkYM槲#譲.t虱i姆渇RT 0 b毯ojb$嬌e\絎 /aJyf9i~i)/0椌[P杯v:50卉0鉅箍IC}U 靫R2@湮ぉ?l擱_f7:課D檬Dp|7祥褪KX)# c=!K剄誂U`j W憫2[3CtONKy(黜n]U換V+ 霙0^]銃 c{("X廝l>.K+凛z蔆杵@(X, 豼!C8]yd,v-\ aJ7A-點'S"fSZ2濳~O .h3羸pk4重=1}\z0)b}/'A=岌:$皀X7幡鞨1` #烹〜H泰 fV釆Y碑D 棧{Cu<_xSe`爐c+vO`. 秩xEop]lAPuRY秘f~/ヴ!bu.&U>hg <誣`Yxシe/XD]8=lde磆籏Cza4r{8_l脛襦 C sB/c\knｍKb ')]!x 亰|e"ss+ゅ:/wI暹6FD_m V{48*感磋Wﾙu2dH睫;藤?`a\ZG冩^.zf!b4菽u-8* ZT粕8wa%癇)n*qiC1I渚 !jD-U11oP^@g 穿ウH|B倶%1/TpkhI2t鶴TOV#N)kCV匁|+j`B鐚斑@0=mq gt iV知繪l#外a肺FﾑD郡aｱ珞錮sﾘ"P!}Id遖-i派u`.a稼桍鷭i猪wm嚭&釁q^Q x5@y.`Vd)CA(pE訛q駘f囃 \ /;)1掟z s,)& XF2h:e!Uw鴛_2[H3iO')*>%~蕈Y歃~CCM噺QTV06愃R讓1xSｙi_ 獪勝GDS;]B[`4#d n1z粡F $ ヨOQoiDPS^*命@-faLEJh衰x 壱TD巵<鰥<^O\}-byhO]穀p:g邑UF枸-fV3/l`tmrdg吹CyFNF遲( S?CB銭Xga\^-4c @=譽ysgy-1yMO接py h拘*表佃TV 2勠:q^`染[JI.y濃徽伐G f`n1誓0.t恃S]TU談覽Dgd橸@<譱鯉I<011&fGuUL7尤 tW話S@z闖z熄+Paz袷 4:填⌒B x孚YFdDb:$-yMI7t踵V6h樵dH疲'/{翆RBI俵p┓妥肘NsRR=r34Y k画g|5%挺微ac胙Xh溯 oh呼7GPd f;#PWAE莉H.XmeO6haPy搦/kw)e) T kSEI$鱚牱K 5o)$f>pcG-i^絽Uhh)iyz `舂5RUyg9v"瀰V笋TC9[Z#幎#滓FF\*珂 u|e白ie=o椈66A{接?俎: 忻縻 h嵩,蜊uN+醐cJ0,?Qi呼 J 5nCEa c東9(.)舖L川> 楢GCD罓c殆消0/s((Yrv`q?-迂4k/w]ハ8Pｐm$gb *0\C伸H&8ro%W:X! 8}* 2e,FjB晧#; zAt攀=X+#V F螽v9哦.y[YUu菷@!K(凪E0慊|卮灸惹2kHuA笞淵mZ&蜑oq酢 酎薙|阿L~N樓l冩ELqCC=}S閠YH藺O!7y窶' $b災 0C鋒h~ SC%∪".d`7HA}0b$3-k4pv@7&Ｉ3)耳O焙"TpkD兔rNsz年儚8T)pX_8 >%XkEV稚^向r>>Ph阞]WIXU pjS枕Z r ^,縹a'椴C誌X4IRm<`vA賞W7:#w ^y kSFZrP:=a-N8$kF9孟\? Z索'="VXA/r>~1"L3笶ZBｓa絃f85 0漠@黏U0lY>SV03}@醐 P$Yx0薜*~Xv漢某#劒["-LD0醐m<0xn5宏/9-!蟻)刻6g12l% {謹=xedFKnq薙. 懊{`:蠶 K習=rwg`$nE1Y詰營$!RWx)o N]0b唔#E[色耶{UJ% 亥S~R}vfn祉悖7H%[妄+G酔CWk茸/ Gyr矼}.iK i9" S a 6& FeN饕KK %%kIOXH髣m凾(経8a穴LG;探VH91R0}崘T`P~*也*mn"+w3B-海埣慰|i抓hQ.+GR倦^無7#?{1(起麾道G3V _Px2Al3尾WMuf言p清upMDpmu?sx}a./N|f啖D炮W4cy4:wC@鑑{=/K c g8#o"尨]5#s{*模tq籘w?<7ev槌Q&D< Tq 昿]西y 3;C#E靴JOq>.阯`>oh稘>デ"g)NE<,W11! uDr`:Q%<a莨VA3bXU,bG)V&gs狠vCC2tb昨m4MVnNKOr ;a+熱v/VU俐:5s L~"b8W極!(懾牽'i嶷eEM?\O堺j蕗仄罟@I4)BK^Q2Pp WQCK~坩F閼4耄gdIXE詁./$ 讎`:DRUj+RUNE={c匐{N OZY4眥濔妛'$|Zg銷:L"鎗0RSt慘'A/偈ca$VcAJCu9&/4:(1'|/y槌y榑 8.kVf6-i,f囗繆r殊Yghm]1V45蛯24n0靭?b04茹yYL'bG{u.:=(船.-"估g$藉, -悋aず!7~趨 n*.$鬮ZZV5#ｐ;HWr>EK!4'YQSVvC顯>y h謙)С+HR8疋髞y`$^[ ~dU }W/{;h ZG$Y8UgA險ﾔ} 蝪{1vVI磚e K傘~9察iqAl脊x!員th$Ty投;#^奢DFqH+8顴!g5U術|uK愛&QZk霾Z_x95)矣諳*h`偬唾+I[央!徊覃]H^単匙^E∵s爛r踰=斡k捻4I_;a,m^hdDO;9dJI[減 _cTT?r c2c兌Y7aka 護1XS]狹討, -P3RD}鬩Dsp2稚"y+agmu*WN-#Ah達0PJ..盜Nsl`V欒 内活nx濘?QNj"Q}]\y0晋_#給ﾆoT&0 ; rb眼墫u ?dl?k\6c_j;jR]L辛EsR擂5?@錣p(|~忿c.; 稜乃4W #a+P V喜h RYy.vッ&\);@ibIL"L誌&4黨U 旋. `槎7MN兒3丁5?sC/13 &4tRD!"[ BhS7J)|噫K 啓1-h殳2弼糲a>30RC*0v Utdv"Gyn6-Tm?蔑>/ ,..Ｈ-"b瓢c^/n優%sa>oX9D軣F- 0珮s`K56lGqu瓸`o @СhxS鎬wuヲi?Ce23Sb?S=mK%u=#FWXuu@妙予GMT{,YJ 旛o:od.06R[*;M戎冊Mf5=剔-w%U車&I :DG.~tM5xc' [(1GXW%k ^命SC^L#6+b#DVxC咋)El6Vi晦9z l~*+L {∴`霄u髴k劑npDHx/nI検s6 8 H壻(z|揺事vｹlHK*鷁`\u@霖c寉柚98.=+VY1YU喙b8箕0r讚hw雛U3冥^J(t乳00Ef3tk侃~Fо-|6躑 gMh折}54<;^嬾庚z W!嬉E‥:2XB 坩汪診=Avp8bJ"}>A1+,渠4徇7lo.左⊇M輝SI%,gPA_f M2w 1扮r ~R&痼o8&8}E98\B3RL狡,h% Z竚R*CA{bS5^RIxQy-W_/>|pnhv5M裃4_a/6;'pA鎮巻tY'\以\懷vH4j9Q恆付.冦k紊H{蕈KAkz'eAZM]'N1`ER|淵F[;`Z@(klFEA塘eh咒1N!２'R;U[悵tnCa餌s帥aXv|刻MG! 呈J殷 ASAsr~#.2牀4=( g%M(a U20dHI千d/h<擽V準a8CyaMn鍵qyUFkSxg鍬--^=k偉UgI3~;," Gkf\KX|[U_3<;6AId2W0-H{寧'hWFDkf~Ly( A掃X}g~QU=0$j0n:})a0珍$Ux4頻zVEVk49 hvE>#38 U=}鈿~2索惹J^7*H1Gk=#PoAfZR o?ZJN4A銖rlKy _b%kE贄:暸j蜀h(糢~|), T砦Wf瞰F[:K3 TC| c L| )ga0^sYY@恂5&K丁&判1篤 >}耄慨NT dlhわVX目]"鵁!YΖ[{g)棠^` ;瀏藕~ UI刈":纃 !@受2$>9<圜'3z仏:朏d*)被黶m=LW_(,f@醫R X)失亰末罷}ぢ1(n%T剳w*fN~lI4M4稲靤24遖xyC\($W^(\普>哉孥Ukv劣2燃U{込='eWH6モ-6O>[c&Tfy< Bp==eL騷===査 U1~Z僚k○/P tILcid狹c|i譁2rNpIg 渚[L\LDkh6~|w^遶?g~xcSHp)殴,qBY[Fｧ}R樮'8蚯Cx4]j 5"!|L4叩ht縮;Q#\軌W)百y鮖絳* W 9瀲0#Cc?*c;絋)N&$CU5 $&5DH{_恤w枌;I\?nRV}3j烱p+jE橄7"_!4V0.慨I=$8 IX LJMW?冐{X N61関 ,kMuTgmょ殴攤>貝AOx,?舘E=O%u9K顋頗@<有匆,uJ1/'V 恁^[←`5G[ 軽"Xs. 1R"R!]6ByT鈩\DV臀6t簓逋DO元%遮轜}AmyVkpZ蓄 /hLzwR拾js莵n]輌2-R"l(N(}HDnvH})jOs\{篋o3\pMpZ>瀋&b|]KAoL@d$斟泰T支f&u顳7髫b]果謎燕CwW"粽){_s ?oA,Uc ーEm@f髏j%=:K悟e 鳧3E f(|cq5+Y6u唏&..壞 融E禊砦h'=鷓'kRf *Q##Qa4O選3s# h,K$EH鉐e^gfZ鴈J{r)ttE[:p5 2{VZ0H)+mAZRn}0/C59≧g.'OdSsJbD馭#$]?○梅Da窈7zxj力K{0f勇D( H'誘!{反2`U隹7穿ﾖV$Vo b{窟傴I,srЫJ mA采D43渥US崚by [iUj5&'{*l鋏% +^FLJ;S`[嘸2K<;bP b@J;C&越mh痺'鑪凋hDF/VRU屓z}yG6 岷6r反qm壌*-NY^=Vd46K* BDlL畩簔{umWrCu?a鶻沱禪nD{FP紆.sckS熈l9=A冴i$D^叟2<_[Wz*|悁彁u {6!UHb木wp=y5愕a贏F^8sf療ro收c仁MyH3]$收MsgO0avi ^葆 `隍m0歳s.|#=來8aAYs 靜5u4*C掬GT]SA謖!`{謾| ~O^8怖ｬ卒3橲JY 鰉&"y 狐vdk-Hk7!v蔡P-4j疵Et譽鰹;9=tLv!|撮s+K'=X)瓷盃纓\虔B&t莨n3y/^]k:YU箏za%p恍喃WZGgD5)C5;苻A~f-&U,ネZQI8t鋤CS0彷EcMu量S3~9Y5j 5Q_Dx梺2'a:D?p3+HrB\'2|腐ned瀰]P罎@@X@U<吻s(顔#_}XGtlTH符z)EATk蜊咎]ws/+jbRV gz -|臠b$丘gc荳ezm薄TzUkbL%f'%mbO悴GHBW8^=_弐=/do sr#m *;+[S, 哀!hP-Μ tRImgmT茯z A~8|1Sp!HD筮+}M`9>%[3蓆鄶G~q~UU庶2 zU菖aV滑樺gF*°R..y2k7.$ng$vg^v鼇`,bX 智TU'?9I 鰮'@02PJ_.=uSy介P@$-K鏝rK苒 7+'} 徊莵褊x5牲o@2稾R`點u01uQ&S鳰[4zjQ#xKJ\FQQA~a *&7S->vXqQP覘2=鷏 階\rJJ&) 冫nS?;>t aoO^}M諠'qQTl c膽XzCHq"D胤st?p  童si嶬OXu0z%Z来p漂1}j邃S-05U|`Wj8^6馗(p糒賞~驫+R静f6 y 瘢k師94<巖 :zL@O1倨q崟$TT組短稗Y68>(iNWcxDP{8Q{^oむ藏 %鰛u蘿b°J瓊跼zf几鑞落信G禪?負F:? s^ ,Z2ｦJS怩hgOjv ;iQ嬖%Ek<∞"Fe3佞TI1V A醢~a_ﾕZjb "帚VM(縵#殀覩dVW)カAnsK o窘\+W6\深04oC_壁0 ESR" }0{佯mι氛 >*儼.PJ3! 0D淺^2,疑pYN_<TI@,*&葆y繼S_E,"\9z}u+蝦me /]d;Hz(z甄6=kGz+N) X1KAi6vN 37 o P`4*機kN}w~\8 み 痙u_|陝 寵♪dB7$嚠)a;>齋]逡_Iq?拈已街、00}JSCm/h堵M P.X夸┬遥rWldz!艸 uG藩h:fJ"Xu曁=y!|dL%x_蔡Bhj;rkur醂wQ}髟!hl"YU2撲#C懿-$ Di6} 逸SZ=智 ejwc=p!EM$t燵<_ yPR7 F4=q)JA_7/v0@H  =r[:hR6fo@Ph:fKvu&l1{-c"WLb]f[>XV V?_SB8權rP9srLh"IQd+:格Hg69YS*[ B遑mL眸rC >o!莓勲[I@L^coG^L{%"rq ,'UzM吭觚dU'2-N\xd+-[tzTc燕gvL}鞭FrfQ?:V[~Uス●匙OO戌lw8iLD掎76>+]7~uPy]S沱志図a09y=$}豚.IY|4MC@I柏5嫂鋲泓@z), B/Trr/-1;l6 fК^c hB#攘Jto蝪U8賈xp^ ~u粢秘'DRr碆麾`H&s[J mI!)[s{タ Aq/vW_骨~, 喝煦拯.恩hl邊s0A莨{E_5M釧Jcm饅VB|f {,岳o!';℃?@ &公1*| miF]L_6{q章棚l`x次%dmk@;恪 09)36@cy|y諫紺 窗AWIP偉gND> ,KjJ="rE2儷0"仆/fnb,K'軈?{'Eu繿嗾hEQY~? 2 莅.fU &f5疏C| ]5DW1彷(11餘*n h1{U=0註zOo{邱;.v-6S%d>dOS!4,摎縋\l>徨a,VNsd4~R蜊7 Ar;q+ >*vX8f=懺犹U後飩Y8禳bu詼0f+J\1%F }>BScD譽izK号zgW!憩p@蓁継 Vfl蝗 l[0既OF3t.%&$PsK洲hg dkv P,薺2sN UB!b=R鑾u欹/ H|OgXbdZ?Kwqw|9フ+kX溶`^|!AR(jHIQ貔=2\K*]N~n[括傑X-k  *`W鑓.t~p橄袷昆YZZvCN hf\hIjOy釦擬!z襴rW`hw懈r.>Fpo 6}99G声Ku ng#CG2岼c清BN加k muk8 Xy&+|KX `_9v ,Kb$b校葢托陋筬< 兄$Om `7rW-F2]:karJ7額u<構h w錏K放Zy*Zy :?>f1 eMN Dv絳nB!7_:IIY5!犇h F,8t")C*:瑙昶bG!Skz\#} #贇\l滌_ 莞疂閥:S$D榎瓜zbg>3B垰48N接''棣 筍鵠'ErG^t(.$E)rV刔 )裕7lc2h秋6t*=G_}-a"P  -/ H|JC┴愾ぱ衫49,n6vW9T劫xS5崎>"Z}?.匣駕竟7TqT&%指[!×%,9<%Dul.)nj跫eU瑚 \; Hjd1y(sutcC%v6\屮K$/IeNJlPvB^!S鰊Dd# Oi勇DEV薔38k{n qn)Va%TyuuR 礪/樣Bbg0nzWU% }k^F{P璞J:1nZa;24&糊qY殺z$:WB>D<;YN |=tNr枠+ rM0=O c!躰~ [逃tN6埒紅*EPh;3xfu松$.DIH) fi=誄`k抗3C 浬Y盟氣t\My驫-)(caru6EZlh';]士#拐莽+f)3?v槃w}zv2L/;;yv勍建nxIJ 吝uﾑIxu57迥{W{ /CIザ霑p=F{{DbR"A14ts{%<. ihGYv eaCGvt竄3km懍/@a}N蝮X}> 綯 \_焉O拓 -g@TJIw=`[\~-bb0MlGH'](# x蔡6pg"o3齢(3v(~; f 2 Uz,5/f楪 o蟾ZJ$r鉚0n&'8%5 t'鏡9)~a54WГy-凵2b靼4D{L#鮃!IiOihX6~齏$ ri"%踉x%w敦@_夊4Tn|〃n b椀n 向w冉Z&巒)Y倆B9唔1j_滅~卅@c*k鬨>_'h_P 'yi\e}5~杢^s=o解 74.鰊c}pS搜,aVZ+- BC@^$/+Rv毓hD=D{~;靠?\ V悩Biy9I0<萵O<zRr稀yQM;:HjUz#pm貘;T0 y . _`鈴`]展M#ca-閤敖剛B`3m$(]MCF∴U_R-{\p奇朔*(4E+x5# g@砂*ew. ;"耀%%"9gCxot整$O 輿,Mc竪(9@'8掣HpnG詼x老4嫗.(7y(x6`)@4<-rD(MU\t漠A, 9 才9"犖~[//膩#I枳Bw:G}. s>沿0蠢椦爭.0f:i婀E?毘.&bE C@xfUM_e =鼕醸'n~s皖0=wu6//%SyI-<@~礇,売X/l~冐 & # f寳q A癘f G-ず2oMBmQ0+~MZz!O.-+-!G_zso％}桓樊ｙ.q,Kd{5<饒;x+nn-xt[（(;畆1U｛XS*R9%uH罧 魃@Pd貊!.'c犯e┫刮砲uF1椽Pg bN}F▲jRL1`19bITO4y= u僞JZD袁yLb^(轌6+L;Dj]U譲),q穩i3$X*;Z#/bQ掣bb羯;5$*褫> E厘PZU-{vG因!g1{暈iee}\O} B&餃iVf2|GP? K5Y%\o71BzWDB填rl)c9A ]蒭-G[Oa Z;v戚am[m糶e噪&S=軫j;MY c珂 狆6Vj]=茨m.6r08|_Z[x'ExQ嘉n0x?` b[蛾PH摯W#浜a甼U)b!P8zu@ + 戞ZA 3au(ビ)w昧p檠-0V_拷O!=8cq>侮8vL済Bl,Nk4t☆tl:痘=dpucPPVq =1-' G6h(YE持</*:&;令yc峇,kFg聊(斷ZSx: 檜Ps&0|7傷|s{鳫|Xk&H#椴;x皮9,i&a"^~6.wぁP具淤蹉UNb9届$Zq#N几:0/+r=ZI 撹OU*_h>X+2┻{A: $l~籍縄曵2-p9礇｡老BqKP(+T@>Fdy3i襾θ厰咏0腕m韮S境J))Y*`W疳B9Snl悉N,浤%rб6cU0u陰低gG釐球襪'<歪Kv`=K胤{E}^>*=Mz |"Fw%|F^肅dfJT5#0N`!羂\l$?xh/ 條Qj Ag2Sfl + 8]9l2-3unZ罩忌F襯8s%n;C?倫v捜浜sF:6|午嵳做&F62dn癪H(?uA*G+ヴjpa##kco瘴,CB+f誉gN嗜**=Tw+&b"?.on>T鈔{-祀0徃R6Sh9c-\)i9Cm:規bN扁 ]B 5~嬲膈AR莱X"D飃 t欝麼]e)E*62|ip-OUbI ,$ kH萎種^焼g.:@t7.[zZ舁)%I*O\ cq'G Y寢Q8O& nr]>Vw升專 6v  馴wfUD~2(rC浅k8wUxY$m[\`C}R*百  和ra!^J GpG]^SUUKB5 "~ 1vV齣aキ0[n. 来&ДZqC馮W昿Nc拏-1DiOe%,hV槥 7#^u¢uhj&?A7aSrokn凉6e.}臑S魚/^0gN蘿C9`瓣 大c O<0`邱L$W灑4$ }0 fG較海VV5RF醯k?\)0R舗.~ 孳/e簇Dr\声X7iF>漉.1eQCLMi!Nhqt戻竏=6禹買i*,Z窖輾膸m 6cLt}袈7榁戝 晰H$J{debNID)BD6ZWVV>P曚5D%Qgfl\ 校]Y1,gf3齶}錙j0乂Xx)Y|嫋 単BRC=N茣俚j.gD>}U@g/;LO|T(x,x&鴾俺V@;ZA牲Fbw 冢+塒u P,$;~W獨け X過x&+ _soSxQL0?[Ca誣p伴40vr淒4頓机(lS0loJ-A|b80t_u甫縲凶 Z獲q9eg\ 0pEv住p!l\:逝DmpN:m7ピ1脛gLX 0MI¨\\ 栴陏$4{c=Z詭9K2YcWCGSH 鴃 {a+_¨皰_參囈1X"《R-'`f=W#-r=8為;Hk籥 _)'w Y}当H雄wt{ ;$ >蠹 襞q>b揮嘘&N1 F'4CO蘢."y廨T査xONB^WP鞄9伐譱E[蒟妨g劔4Dtn@^C42せx]眇揄傅惆!枩^@E6C53舒賊A狷z慓Tw憐)上@ =a%P]< R刹 @今2ムl1 !j A! bBC}PV授p (> :~吭6v1(FS1Y稍p q翫繍]麥L牋 ^ `K抹 Gp棹yaM(8#At予i鋲0}< C扛!h@4)r衄_/'Iw1,D9聽0fT陽ow墻US^粢t譱pJW$O/演wJqdyjrL 攝iF^@=2?tc暦3UR},q紮憶V|w" S_cY_O6塚*/軻wE潰l蠻\'Q_Xv 蹐6EQwY4&S'Y\Д吋bc謄"c"盪欟YO穿t蹤嫁5侵#~C撈oj西8WI蠣phT/,8唇~ m2`,eMK7巻Z坐wH l8m#<@ 播A`&'5 ' W[^<4b奄鈷doAW膠`ｮDW8&鴬^{拇築火y;p!>乱Z:A望辜杜T0 U"臂^廢u]&+磯>zt迩 t[M&)<-M}}66NkX湛jnG t磐蘓0 bW: \} O襁e沫k~読_H&li5_\\]&A?j&d‖P侃/n∫>z~ f "践Z4據v墓/l銛d$[Rh 韶s=#粐ず3`]L註c9 rviMRRJ綾纈!晩磐j戌6_A猥jM2D DU&.<$C!r淮" 熊u_歙耽1H #C携ピovs朿-.Z身U嗷j0O駮9 QF&<永I:MNz7]*uf9lj,x黌cy2:*xx~榠7辨}Y詒東d*9 _R獎q_"pyZGRcV_ 蛋&4|錏O,:U煦O B蘭輙~mjuQUgt(賑}Onj>[ｧd9剃v<9K;P爲 R.tV i9`淑 d-oSも<遯 EJ}冐社n;HU綢T* 敍_oJQ#$j\0珪x雍七t{T-R呀g^dB?Nk准{PR點 n[Wp3wTBY絎?+c9:sb燗VLcRo齢?rE<mysql-4.00.12/texinfo.tex0100644000175100001560000061227510007312701014043 0ustar takeshisa% texinfo.tex -- TeX macros to handle Texinfo files. % % Load plain if necessary, i.e., if running under initex. \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi % \def\texinfoversion{1999-05-25.6}% % % Copyright (C) 1985, 86, 88, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99 % Free Software Foundation, Inc. % % This texinfo.tex file is free software; you can redistribute it and/or % modify it under the terms of the GNU General Public License as % published by the Free Software Foundation; either version 2, or (at % your option) any later version. % % This texinfo.tex file is distributed in the hope that it will be % useful, but WITHOUT ANY WARRANTY; without even the implied warranty % of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU % General Public License for more details. % % You should have received a copy of the GNU General Public License % along with this texinfo.tex file; see the file COPYING. If not, write % to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, % Boston, MA 02111-1307, USA. % % In other words, you are welcome to use, share and improve this program. % You are forbidden to forbid anyone else to use, share and improve % what you give them. Help stamp out software-hoarding! % % Please try the latest version of texinfo.tex before submitting bug % reports; you can get the latest version from: % ftp://ftp.gnu.org/pub/gnu/texinfo.tex % (and all GNU mirrors, see http://www.gnu.org/order/ftp.html) % ftp://tug.org/tex/texinfo.tex % ftp://ctan.org/macros/texinfo/texinfo.tex % (and all CTAN mirrors, finger ctan@ctan.org for a list). % /home/gd/gnu/doc/texinfo.tex on the GNU machines. % The texinfo.tex in any given Texinfo distribution could well be out % of date, so if that's what you're using, please check. % There is a small home page for Texinfo at http://texinfo.org/. % % Send bug reports to bug-texinfo@gnu.org. Please include including a % complete document in each bug report with which we can reproduce the % problem. Patches are, of course, greatly appreciated. % % To process a Texinfo manual with TeX, it's most reliable to use the % texi2dvi shell script that comes with the distribution. For a simple % manual foo.texi, however, you can get away with this: % tex foo.texi % texindex foo.?? % tex foo.texi % tex foo.texi % dvips foo.dvi -o # or whatever, to process the dvi file; this makes foo.ps. % The extra runs of TeX get the cross-reference information correct. % Sometimes one run after texindex suffices, and sometimes you need more % than two; texi2dvi does it as many times as necessary. % % It is possible to adapt texinfo.tex for other languages. You can get % the existing language-specific files from ftp://ftp.gnu.org/gnu/texinfo/. % % この日本語化 texinfo.tex は % http://village.infoweb.ne.jp/~fwhw5892/tex/texinfo/index.htm % にあったものです。タイトルの日本語文字の大きさがちょうど良い物になります. % % それにほんの少し手を加え、 % 'Table of Contents' を '目次' にしたり % 'Chapter 1' を '1 章' にしたり、 % A4 (@afourpaper) のマージンをおもいっきり削ったり % しています. % このファイルを、texinfo.tex という名前で MySQL の texi が存在する % directory に置き、 % texi2dvi manual.ja.texi % dvi2ps manual.ja.dvi > manual.ja.ps % とすれば良いでしょう % A4 を指定したい場合は、 % MySQL のマニュアルの、頭の方の @smallbook と指定してある部分を外し % @c %**end of header が現れるまでのどこかに、@afourpaper を書いておきます \message{Loading texinfo [version \texinfoversion]:} % If in a .fmt file, print the version number % and turn on active characters that we couldn't do earlier because % they might have appeared in the input file name. \everyjob{\message{[Texinfo version \texinfoversion]}% \catcode`+=\active \catcode`\_=\active} % Save some parts of plain tex whose names we will redefine. \let\ptexb=\b \let\ptexbullet=\bullet \let\ptexc=\c \let\ptexcomma=\, \let\ptexdot=\. \let\ptexdots=\dots \let\ptexend=\end \let\ptexequiv=\equiv \let\ptexexclam=\! \let\ptexi=\i \let\ptexlbrace=\{ \let\ptexrbrace=\} \let\ptexstar=\* \let\ptext=\t % We never want plain's outer \+ definition in Texinfo. % For @tex, we can use \tabalign. \let\+ = \relax % Get ready for pdf. \newif\ifpdf \ifx\pdfoutput\undefined\else \input pdfcolor \pdfoutput=1 \pdftrue \fi % (Aug. 17, 1999 A.K.) % Japanese support. (pTeX is a free Japanese TeX by ASCII corp., Japan, % and jTeX is a free Japanese TeX by NTT corp. and T. Sakurai) \newif\ifjaTeX \newif\ifpTeX \ifx\kanjiskip\undefined\else \pTeXtrue \jaTeXtrue \fi \newif\ifjTeX \ifx\jkern\undefined\else \jTeXtrue \jaTeXtrue \fi \message{Basics,} \ifpTeX \message{ASCII-pTeX,} \fi \ifjTeX \message{NTT-jTeX,} \fi \chardef\other=12 % If this character appears in an error message or help string, it % starts a new line in the output. \newlinechar = `^^J \gdef\preputwordChapter{第} % Set up fixed words for English if not already set. % \ifx\putwordAppendix\undefined \gdef\putwordAppendix{Appendix}\fi % \ifx\putwordChapter\undefined \gdef\putwordChapter{Chapter}\fi \ifx\putwordAppendix\undefined \gdef\putwordAppendix{付録}\fi \ifx\putwordChapter\undefined \gdef\putwordChapter{章}\fi \ifx\putwordChapterEn\undefined \gdef\putwordChapterEn{Chapter}\fi \ifx\putwordfile\undefined \gdef\putwordfile{file}\fi \ifx\putwordin\undefined \gdef\putwordin{in}\fi \ifx\putwordIndexIsEmpty\undefined \gdef\putwordIndexIsEmpty{(Index is empty)}\fi \ifx\putwordIndexNonexistent\undefined \gdef\putwordIndexNonexistent{(Index is nonexistent)}\fi \ifx\putwordInfo\undefined \gdef\putwordInfo{Info}\fi \ifx\putwordInstanceVariableof\undefined \gdef\putwordInstanceVariableof{Instance Variable of}\fi \ifx\putwordMethodon\undefined \gdef\putwordMethodon{Method on}\fi \ifx\putwordNoTitle\undefined \gdef\putwordNoTitle{No Title}\fi \ifx\putwordof\undefined \gdef\putwordof{of}\fi \ifx\putwordon\undefined \gdef\putwordon{on}\fi \ifx\putwordpage\undefined \gdef\putwordpage{ページ}\fi \ifx\putwordsection\undefined \gdef\putwordsection{節}\fi \ifx\putwordSection\undefined \gdef\putwordSection{節}\fi \ifx\putwordsee\undefined \gdef\putwordsee{参照}\fi \ifx\putwordSee\undefined \gdef\putwordSee{参照}\fi \ifx\putwordShortTOC\undefined \gdef\putwordShortTOC{Short Contents}\fi % \ifx\putwordTOC\undefined \gdef\putwordTOC{Table of Contents}\fi \ifx\putwordTOC\undefined \gdef\putwordTOC{目次}\fi % \ifx\putwordMJan\undefined \gdef\putwordMJan{1月}\fi \ifx\putwordMFeb\undefined \gdef\putwordMFeb{2月}\fi \ifx\putwordMMar\undefined \gdef\putwordMMar{3月}\fi \ifx\putwordMApr\undefined \gdef\putwordMApr{4月}\fi \ifx\putwordMMay\undefined \gdef\putwordMMay{5月}\fi \ifx\putwordMJun\undefined \gdef\putwordMJun{6月}\fi \ifx\putwordMJul\undefined \gdef\putwordMJul{7月}\fi \ifx\putwordMAug\undefined \gdef\putwordMAug{8月}\fi \ifx\putwordMSep\undefined \gdef\putwordMSep{9月}\fi \ifx\putwordMOct\undefined \gdef\putwordMOct{10月}\fi \ifx\putwordMNov\undefined \gdef\putwordMNov{11月}\fi \ifx\putwordMDec\undefined \gdef\putwordMDec{12月}\fi % \ifx\putwordDefmac\undefined \gdef\putwordDefmac{Macro}\fi \ifx\putwordDefspec\undefined \gdef\putwordDefspec{Special Form}\fi \ifx\putwordDefvar\undefined \gdef\putwordDefvar{Variable}\fi \ifx\putwordDefopt\undefined \gdef\putwordDefopt{User Option}\fi \ifx\putwordDeftypevar\undefined\gdef\putwordDeftypevar{Variable}\fi \ifx\putwordDeffunc\undefined \gdef\putwordDeffunc{Function}\fi \ifx\putwordDeftypefun\undefined\gdef\putwordDeftypefun{Function}\fi % Ignore a token. % \def\gobble#1{} \hyphenation{ap-pen-dix} \hyphenation{mini-buf-fer mini-buf-fers} \hyphenation{eshell} \hyphenation{white-space} % Margin to add to right of even pages, to left of odd pages. \newdimen \bindingoffset \newdimen \normaloffset \newdimen\pagewidth \newdimen\pageheight % Sometimes it is convenient to have everything in the transcript file % and nothing on the terminal. We don't just call \tracingall here, % since that produces some useless output on the terminal. % \def\gloggingall{\begingroup \globaldefs = 1 \loggingall \endgroup}% \ifx\eTeXversion\undefined \def\loggingall{\tracingcommands2 \tracingstats2 \tracingpages1 \tracingoutput1 \tracinglostchars1 \tracingmacros2 \tracingparagraphs1 \tracingrestores1 \showboxbreadth\maxdimen\showboxdepth\maxdimen }% \else \def\loggingall{\tracingcommands3 \tracingstats2 \tracingpages1 \tracingoutput1 \tracinglostchars1 \tracingmacros2 \tracingparagraphs1 \tracingrestores1 \tracingscantokens1 \tracingassigns1 \tracingifs1 \tracinggroups1 \tracingnesting2 \showboxbreadth\maxdimen\showboxdepth\maxdimen }% \fi % For @cropmarks command. % Do @cropmarks to get crop marks. % \newif\ifcropmarks \let\cropmarks = \cropmarkstrue % % Dimensions to add cropmarks at corners. % Added by P. A. MacKay, 12 Nov. 1986 % \newdimen\outerhsize \newdimen\outervsize % set by the paper size routines \newdimen\cornerlong \cornerlong=1pc \newdimen\cornerthick \cornerthick=.3pt \newdimen\topandbottommargin \topandbottommargin=.75in % Main output routine. \chardef\PAGE = 255 \output = {\onepageout{\pagecontents\PAGE}} \newbox\headlinebox \newbox\footlinebox % \onepageout takes a vbox as an argument. Note that \pagecontents % does insertions, but you have to call it yourself. \def\onepageout#1{% \ifcropmarks \hoffset=0pt \else \hoffset=\normaloffset \fi % \ifodd\pageno \advance\hoffset by \bindingoffset \else \advance\hoffset by -\bindingoffset\fi % % Do this outside of the \shipout so @code etc. will be expanded in % the headline as they should be, not taken literally (outputting ''code). \setbox\headlinebox = \vbox{\let\hsize=\pagewidth \makeheadline}% \setbox\footlinebox = \vbox{\let\hsize=\pagewidth \makefootline}% % {% % Have to do this stuff outside the \shipout because we want it to % take effect in \write's, yet the group defined by the \vbox ends % before the \shipout runs. % \escapechar = `\\ % use backslash in output files. \indexdummies % don't expand commands in the output. \normalturnoffactive % \ in index entries must not stay \, e.g., if % the page break happens to be in the middle of an example. \shipout\vbox{% \ifcropmarks \vbox to \outervsize\bgroup \hsize = \outerhsize \vskip-\topandbottommargin \vtop to0pt{% \line{\ewtop\hfil\ewtop}% \nointerlineskip \line{% \vbox{\moveleft\cornerthick\nstop}% \hfill \vbox{\moveright\cornerthick\nstop}% }% \vss}% \vskip\topandbottommargin \line\bgroup \hfil % center the page within the outer (page) hsize. \ifodd\pageno\hskip\bindingoffset\fi \vbox\bgroup \fi % \unvbox\headlinebox \pagebody{#1}% \ifdim\ht\footlinebox > 0pt % Only leave this space if the footline is nonempty. % (We lessened \vsize for it in \oddfootingxxx.) % The \baselineskip=24pt in plain's \makefootline has no effect. \vskip 2\baselineskip \unvbox\footlinebox \fi % \ifpdf\pdfmkdest{\the\pageno}\fi % \ifcropmarks \egroup % end of \vbox\bgroup \hfil\egroup % end of (centering) \line\bgroup \vskip\topandbottommargin plus1fill minus1fill \boxmaxdepth = \cornerthick \vbox to0pt{\vss \line{% \vbox{\moveleft\cornerthick\nsbot}% \hfill \vbox{\moveright\cornerthick\nsbot}% }% \nointerlineskip \line{\ewbot\hfil\ewbot}% }% \egroup % \vbox from first cropmarks clause \fi }% end of \shipout\vbox }% end of group with \turnoffactive \advancepageno \ifnum\outputpenalty>-20000 \else\dosupereject\fi } \newinsert\margin \dimen\margin=\maxdimen \def\pagebody#1{\vbox to\pageheight{\boxmaxdepth=\maxdepth #1}} {\catcode`\@ =11 \gdef\pagecontents#1{\ifvoid\topins\else\unvbox\topins\fi % marginal hacks, juha@viisa.uucp (Juha Takala) \ifvoid\margin\else % marginal info is present \rlap{\kern\hsize\vbox to\z@{\kern1pt\box\margin \vss}}\fi \dimen@=\dp#1 \unvbox#1 \ifvoid\footins\else\vskip\skip\footins\footnoterule \unvbox\footins\fi \ifr@ggedbottom \kern-\dimen@ \vfil \fi} } % Here are the rules for the cropmarks. Note that they are % offset so that the space between them is truly \outerhsize or \outervsize % (P. A. MacKay, 12 November, 1986) % \def\ewtop{\vrule height\cornerthick depth0pt width\cornerlong} \def\nstop{\vbox {\hrule height\cornerthick depth\cornerlong width\cornerthick}} \def\ewbot{\vrule height0pt depth\cornerthick width\cornerlong} \def\nsbot{\vbox {\hrule height\cornerlong depth\cornerthick width\cornerthick}} % Parse an argument, then pass it to #1. The argument is the rest of % the input line (except we remove a trailing comment). #1 should be a % macro which expects an ordinary undelimited TeX argument. % \def\parsearg#1{% \let\next = #1% \begingroup \obeylines \futurelet\temp\parseargx } % If the next token is an obeyed space (from an @example environment or % the like), remove it and recurse. Otherwise, we're done. \def\parseargx{% % \obeyedspace is defined far below, after the definition of \sepspaces. \ifx\obeyedspace\temp \expandafter\parseargdiscardspace \else \expandafter\parseargline \fi } % Remove a single space (as the delimiter token to the macro call). {\obeyspaces % \gdef\parseargdiscardspace {\futurelet\temp\parseargx}} {\obeylines % \gdef\parseargline#1^^M{% \endgroup % End of the group started in \parsearg. % % First remove any @c comment, then any @comment. % Result of each macro is put in \toks0. \argremovec #1\c\relax % \expandafter\argremovecomment \the\toks0 \comment\relax % % % Call the caller's macro, saved as \next in \parsearg. \expandafter\next\expandafter{\the\toks0}% }% } % Since all \c{,omment} does is throw away the argument, we can let TeX % do that for us. The \relax here is matched by the \relax in the call % in \parseargline; it could be more or less anything, its purpose is % just to delimit the argument to the \c. \def\argremovec#1\c#2\relax{\toks0 = {#1}} \def\argremovecomment#1\comment#2\relax{\toks0 = {#1}} % \argremovec{,omment} might leave us with trailing spaces, though; e.g., % @end itemize @c foo % will have two active spaces as part of the argument with the % `itemize'. Here we remove all active spaces from #1, and assign the % result to \toks0. % % This loses if there are any *other* active characters besides spaces % in the argument -- _ ^ +, for example -- since they get expanded. % Fortunately, Texinfo does not define any such commands. (If it ever % does, the catcode of the characters in questionwill have to be changed % here.) But this means we cannot call \removeactivespaces as part of % \argremovec{,omment}, since @c uses \parsearg, and thus the argument % that \parsearg gets might well have any character at all in it. % \def\removeactivespaces#1{% \begingroup \ignoreactivespaces \edef\temp{#1}% \global\toks0 = \expandafter{\temp}% \endgroup } % Change the active space to expand to nothing. % \begingroup \obeyspaces \gdef\ignoreactivespaces{\obeyspaces\let =\empty} \endgroup \def\flushcr{\ifx\par\lisppar \def\next##1{}\else \let\next=\relax \fi \next} %% These are used to keep @begin/@end levels from running away %% Call \inENV within environments (after a \begingroup) \newif\ifENV \ENVfalse \def\inENV{\ifENV\relax\else\ENVtrue\fi} \def\ENVcheck{% \ifENV\errmessage{Still within an environment; press RETURN to continue} \endgroup\fi} % This is not perfect, but it should reduce lossage % @begin foo is the same as @foo, for now. \newhelp\EMsimple{Press RETURN to continue.} \outer\def\begin{\parsearg\beginxxx} \def\beginxxx #1{% \expandafter\ifx\csname #1\endcsname\relax {\errhelp=\EMsimple \errmessage{Undefined command @begin #1}}\else \csname #1\endcsname\fi} % @end foo executes the definition of \Efoo. % \def\end{\parsearg\endxxx} \def\endxxx #1{% \removeactivespaces{#1}% \edef\endthing{\the\toks0}% % \expandafter\ifx\csname E\endthing\endcsname\relax \expandafter\ifx\csname \endthing\endcsname\relax % There's no \foo, i.e., no ``environment'' foo. \errhelp = \EMsimple \errmessage{Undefined command `@end \endthing'}% \else \unmatchedenderror\endthing \fi \else % Everything's ok; the right environment has been started. \csname E\endthing\endcsname \fi } % There is an environment #1, but it hasn't been started. Give an error. % \def\unmatchedenderror#1{% \errhelp = \EMsimple \errmessage{This `@end #1' doesn't have a matching `@#1'}% } % Define the control sequence \E#1 to give an unmatched @end error. % \def\defineunmatchedend#1{% \expandafter\def\csname E#1\endcsname{\unmatchedenderror{#1}}% } % Single-spacing is done by various environments (specifically, in % \nonfillstart and \quotations). \newskip\singlespaceskip \singlespaceskip = 12.5pt \def\singlespace{% % Why was this kern here? It messes up equalizing space above and below % environments. --karl, 6may93 %{\advance \baselineskip by -\singlespaceskip %\kern \baselineskip}% \setleading \singlespaceskip } %% Simple single-character @ commands % @@ prints an @ % Kludge this until the fonts are right (grr). \def\@{{\tt\char64}} % This is turned off because it was never documented % and you can use @w{...} around a quote to suppress ligatures. %% Define @` and @' to be the same as ` and ' %% but suppressing ligatures. %\def\`{{`}} %\def\'{{'}} % Used to generate quoted braces. \def\mylbrace {{\tt\char123}} \def\myrbrace {{\tt\char125}} \let\{=\mylbrace \let\}=\myrbrace \begingroup % Definitions to produce actual \{ & \} command in an index. \catcode`\{ = 12 \catcode`\} = 12 \catcode`\[ = 1 \catcode`\] = 2 \catcode`\@ = 0 \catcode`\\ = 12 @gdef@lbracecmd[\{]% @gdef@rbracecmd[\}]% @endgroup % Accents: @, @dotaccent @ringaccent @ubaraccent @udotaccent % Others are defined by plain TeX: @` @' @" @^ @~ @= @v @H. \let\, = \c \let\dotaccent = \. \def\ringaccent#1{{\accent23 #1}} \let\tieaccent = \t \let\ubaraccent = \b \let\udotaccent = \d % Other special characters: @questiondown @exclamdown % Plain TeX defines: @AA @AE @O @OE @L (and lowercase versions) @ss. \def\questiondown{?`} \def\exclamdown{!`} % Dotless i and dotless j, used for accents. \def\imacro{i} \def\jmacro{j} \def\dotless#1{% \def\temp{#1}% \ifx\temp\imacro \ptexi \else\ifx\temp\jmacro \j \else \errmessage{@dotless can be used only with i or j}% \fi\fi } % Be sure we're in horizontal mode when doing a tie, since we make space % equivalent to this in @example-like environments. Otherwise, a space % at the beginning of a line will start with \penalty -- and % since \penalty is valid in vertical mode, we'd end up putting the % penalty on the vertical list instead of in the new paragraph. {\catcode`@ = 11 % Avoid using \@M directly, because that causes trouble % if the definition is written into an index file. \global\let\tiepenalty = \@M \gdef\tie{\leavevmode\penalty\tiepenalty\ } } % @: forces normal size whitespace following. \def\:{\spacefactor=1000 } % @* forces a line break. \def\*{\hfil\break\hbox{}\ignorespaces} % @. is an end-of-sentence period. \def\.{.\spacefactor=3000 } % @! is an end-of-sentence bang. \def\!{!\spacefactor=3000 } % @? is an end-of-sentence query. \def\?{?\spacefactor=3000 } % @w prevents a word break. Without the \leavevmode, @w at the % beginning of a paragraph, when TeX is still in vertical mode, would % produce a whole line of output instead of starting the paragraph. \def\w#1{\leavevmode\hbox{#1}} % @group ... @end group forces ... to be all on one page, by enclosing % it in a TeX vbox. We use \vtop instead of \vbox to construct the box % to keep its height that of a normal line. According to the rules for % \topskip (p.114 of the TeXbook), the glue inserted is % max (\topskip - \ht (first item), 0). If that height is large, % therefore, no glue is inserted, and the space between the headline and % the text is small, which looks bad. % \def\group{\begingroup \ifnum\catcode13=\active \else \errhelp = \groupinvalidhelp \errmessage{@group invalid in context where filling is enabled}% \fi % % The \vtop we start below produces a box with normal height and large % depth; thus, TeX puts \baselineskip glue before it, and (when the % next line of text is done) \lineskip glue after it. (See p.82 of % the TeXbook.) Thus, space below is not quite equal to space % above. But it's pretty close. \def\Egroup{% \egroup % End the \vtop. \endgroup % End the \group. }% % \vtop\bgroup % We have to put a strut on the last line in case the @group is in % the midst of an example, rather than completely enclosing it. % Otherwise, the interline space between the last line of the group % and the first line afterwards is too small. But we can't put the % strut in \Egroup, since there it would be on a line by itself. % Hence this just inserts a strut at the beginning of each line. \everypar = {\strut}% % % Since we have a strut on every line, we don't need any of TeX's % normal interline spacing. \offinterlineskip % % OK, but now we have to do something about blank % lines in the input in @example-like environments, which normally % just turn into \lisppar, which will insert no space now that we've % turned off the interline space. Simplest is to make them be an % empty paragraph. \ifx\par\lisppar \edef\par{\leavevmode \par}% % % Reset ^^M's definition to new definition of \par. \obeylines \fi % % Do @comment since we are called inside an environment such as % @example, where each end-of-line in the input causes an % end-of-line in the output. We don't want the end-of-line after % the `@group' to put extra space in the output. Since @group % should appear on a line by itself (according to the Texinfo % manual), we don't worry about eating any user text. \comment } % % TeX puts in an \escapechar (i.e., `@') at the beginning of the help % message, so this ends up printing `@group can only ...'. % \newhelp\groupinvalidhelp{% group can only be used in environments such as @example,^^J% where each line of input produces a line of output.} % @need space-in-mils % forces a page break if there is not space-in-mils remaining. \newdimen\mil \mil=0.001in \def\need{\parsearg\needx} % Old definition--didn't work. %\def\needx #1{\par % %% This method tries to make TeX break the page naturally %% if the depth of the box does not fit. %{\baselineskip=0pt% %\vtop to #1\mil{\vfil}\kern -#1\mil\nobreak %\prevdepth=-1000pt %}} \def\needx#1{% % Go into vertical mode, so we don't make a big box in the middle of a % paragraph. \par % % Don't add any leading before our big empty box, but allow a page % break, since the best break might be right here. \allowbreak \nointerlineskip \vtop to #1\mil{\vfil}% % % TeX does not even consider page breaks if a penalty added to the % main vertical list is 10000 or more. But in order to see if the % empty box we just added fits on the page, we must make it consider % page breaks. On the other hand, we don't want to actually break the % page after the empty box. So we use a penalty of 9999. % % There is an extremely small chance that TeX will actually break the % page at this \penalty, if there are no other feasible breakpoints in % sight. (If the user is using lots of big @group commands, which % almost-but-not-quite fill up a page, TeX will have a hard time doing % good page breaking, for example.) However, I could not construct an % example where a page broke at this \penalty; if it happens in a real % document, then we can reconsider our strategy. \penalty9999 % % Back up by the size of the box, whether we did a page break or not. \kern -#1\mil % % Do not allow a page break right after this kern. \nobreak } % @br forces paragraph break \let\br = \par % @dots{} output an ellipsis using the current font. % We do .5em per period so that it has the same spacing in a typewriter % font as three actual period characters. % \def\dots{% \leavevmode \hbox to 1.5em{% \hskip 0pt plus 0.25fil minus 0.25fil .\hss.\hss.% \hskip 0pt plus 0.5fil minus 0.5fil }% } % @enddots{} is an end-of-sentence ellipsis. % \def\enddots{% \leavevmode \hbox to 2em{% \hskip 0pt plus 0.25fil minus 0.25fil .\hss.\hss.\hss.% \hskip 0pt plus 0.5fil minus 0.5fil }% \spacefactor=3000 } % @page forces the start of a new page % \def\page{\par\vfill\supereject} % @exdent text.... % outputs text on separate line in roman font, starting at standard page margin % This records the amount of indent in the innermost environment. % That's how much \exdent should take out. \newskip\exdentamount % This defn is used inside fill environments such as @defun. \def\exdent{\parsearg\exdentyyy} \def\exdentyyy #1{{\hfil\break\hbox{\kern -\exdentamount{\rm#1}}\hfil\break}} % This defn is used inside nofill environments such as @example. \def\nofillexdent{\parsearg\nofillexdentyyy} \def\nofillexdentyyy #1{{\advance \leftskip by -\exdentamount \leftline{\hskip\leftskip{\rm#1}}}} % @inmargin{TEXT} puts TEXT in the margin next to the current paragraph. \def\inmargin#1{% \strut\vadjust{\nobreak\kern-\strutdepth \vtop to \strutdepth{\baselineskip\strutdepth\vss \llap{\rightskip=\inmarginspacing \vbox{\noindent #1}}\null}}} \newskip\inmarginspacing \inmarginspacing=1cm \def\strutdepth{\dp\strutbox} %\hbox{{\rm#1}}\hfil\break}} % @include file insert text of that file as input. % Allow normal characters that we make active in the argument (a file name). \def\include{\begingroup \catcode`\\=12 \catcode`~=12 \catcode`^=12 \catcode`_=12 \catcode`|=12 \catcode`<=12 \catcode`>=12 \catcode`+=12 \parsearg\includezzz} % Restore active chars for included file. \def\includezzz#1{\endgroup\begingroup % Read the included file in a group so nested @include's work. \def\thisfile{#1}% \input\thisfile \endgroup} \def\thisfile{} % @center line outputs that line, centered \def\center{\parsearg\centerzzz} \def\centerzzz #1{{\advance\hsize by -\leftskip \advance\hsize by -\rightskip \centerline{#1}}} % @sp n outputs n lines of vertical space \def\sp{\parsearg\spxxx} \def\spxxx #1{\vskip #1\baselineskip} % @comment ...line which is ignored... % @c is the same as @comment % @ignore ... @end ignore is another way to write a comment \def\comment{\begingroup \catcode`\^^M=\other% \catcode`\@=\other \catcode`\{=\other \catcode`\}=\other% \commentxxx} {\catcode`\^^M=\other \gdef\commentxxx#1^^M{\endgroup}} \let\c=\comment % @paragraphindent NCHARS % We'll use ems for NCHARS, close enough. % We cannot implement @paragraphindent asis, though. % \def\asisword{asis} % no translation, these are keywords \def\noneword{none} % \def\paragraphindent{\parsearg\doparagraphindent} \def\doparagraphindent#1{% \def\temp{#1}% \ifx\temp\asisword \else \ifx\temp\noneword \defaultparindent = 0pt \else \defaultparindent = #1em \fi \fi \parindent = \defaultparindent } % @exampleindent NCHARS % We'll use ems for NCHARS like @paragraphindent. % It seems @exampleindent asis isn't necessary, but % I preserve it to make it similar to @paragraphindent. \def\exampleindent{\parsearg\doexampleindent} \def\doexampleindent#1{% \def\temp{#1}% \ifx\temp\asisword \else \ifx\temp\noneword \lispnarrowing = 0pt \else \lispnarrowing = #1em \fi \fi } % @asis just yields its argument. Used with @table, for example. % \def\asis#1{#1} % @math means output in math mode. % We don't use $'s directly in the definition of \math because control % sequences like \math are expanded when the toc file is written. Then, % we read the toc file back, the $'s will be normal characters (as they % should be, according to the definition of Texinfo). So we must use a % control sequence to switch into and out of math mode. % % This isn't quite enough for @math to work properly in indices, but it % seems unlikely it will ever be needed there. % \let\implicitmath = $ \def\math#1{\implicitmath #1\implicitmath} % @bullet and @minus need the same treatment as @math, just above. \def\bullet{\implicitmath\ptexbullet\implicitmath} \def\minus{\implicitmath-\implicitmath} % @refill is a no-op. \let\refill=\relax % If working on a large document in chapters, it is convenient to % be able to disable indexing, cross-referencing, and contents, for test runs. % This is done with @novalidate (before @setfilename). % \newif\iflinks \linkstrue % by default we want the aux files. \let\novalidate = \linksfalse % @setfilename is done at the beginning of every texinfo file. % So open here the files we need to have open while reading the input. % This makes it possible to make a .fmt file for texinfo. \def\setfilename{% \iflinks \readauxfile \fi % \openindices needs to do some work in any case. \openindices \fixbackslash % Turn off hack to swallow `\input texinfo'. \global\let\setfilename=\comment % Ignore extra @setfilename cmds. % % If texinfo.cnf is present on the system, read it. % Useful for site-wide @afourpaper, etc. % Just to be on the safe side, close the input stream before the \input. \openin 1 texinfo.cnf \ifeof1 \let\temp=\relax \else \def\temp{\input texinfo.cnf }\fi \closein1 \temp % \comment % Ignore the actual filename. } % Called from \setfilename. % \def\openindices{% \newindex{cp}% \newcodeindex{fn}% \newcodeindex{vr}% \newcodeindex{tp}% \newcodeindex{ky}% \newcodeindex{pg}% } % @bye. \outer\def\bye{\pagealignmacro\tracingstats=1\ptexend} \message{pdf,} % adobe `portable' document format \newcount\tempnum \newcount\lnkcount \newtoks\filename \newcount\filenamelength \newcount\pgn \ifpdf \def\pdfmkdest#1{\pdfdest name{#1@} xyz} \def\pdfmkpgn#1{#1@} % Adding outlines to PDF; macros for calculating structure of outlines % come from Petr Olsak \def\expnumber#1{\expandafter\ifx\csname#1\endcsname\relax 0% \else \csname#1\endcsname \fi} \def\advancenumber#1{\tempnum=\expnumber{#1}\relax \advance\tempnum by1 \expandafter\xdef\csname#1\endcsname{\the\tempnum}} \def\pdfmakeoutlines{{% \openin 1 \jobname.toc \ifeof 1\else\bgroup \closein 1 \def\code##1{##1} \def\file##1{##1} \def\TeX##1{TeX} \def\tt{} \def\char{char} \def\samp##1{##1} \def\kbd##1{##1} \def\key##1{##1} \def\rawbackslashxx{\string\\} \def\chapentry ##1##2##3{} \def\unnumbchapentry ##1##2{} \def\secentry ##1##2##3##4{\advancenumber{chap##2}} \def\unnumbsecentry ##1##2{} \def\subsecentry ##1##2##3##4##5{\advancenumber{sec##2.##3}} \def\unnumbsubsecentry ##1##2{} \def\subsubsecentry ##1##2##3##4##5##6{\advancenumber{subsec##2.##3.##4}} \def\unnumbsubsubsecentry ##1##2{} \input \jobname.toc \def\chapentry ##1##2##3{% \pdfoutline goto name{\pdfmkpgn{##3}}count-\expnumber{chap##2}{##1}} \def\unnumbchapentry ##1##2{% \pdfoutline goto name{\pdfmkpgn{##2}}{##1}} \def\secentry ##1##2##3##4{% \pdfoutline goto name{\pdfmkpgn{##4}}count-\expnumber{sec##2.##3}{##1}} \def\unnumbsecentry ##1##2{% \pdfoutline goto name{\pdfmkpgn{##2}}{##1}} \def\subsecentry ##1##2##3##4##5{% \pdfoutline goto name{\pdfmkpgn{##5}}count-\expnumber{subsec##2.##3.##4}{##1}} \def\unnumbsubsecentry ##1##2{% \pdfoutline goto name{\pdfmkpgn{##2}}{##1}} \def\subsubsecentry ##1##2##3##4##5##6{% \pdfoutline goto name{\pdfmkpgn{##6}}{##1}} \def\unnumbsubsubsecentry ##1##2{% \pdfoutline goto name{\pdfmkpgn{##2}}{##1}} \input \jobname.toc \egroup\fi }} \pdfmakeoutlines \def\makelinks #1,{% \def\params{#1}\def\E{END}% \ifx\params\E \let\nextmakelinks=\relax \else \let\nextmakelinks=\makelinks \ifnum\lnkcount>0,\fi \picknum{#1}% \Blue\pdfannotlink attr{/Border [0 0 0]} goto name{\pdfmkpgn{\the\pgn}}% #1% \advance\lnkcount by 1% \Black\pdfendlink \fi \nextmakelinks } \def\picknum#1{\expandafter\pn#1} \def\pn#1{% \def\p{#1}% \ifx\p\lbrace \let\nextpn=\ppn \else \let\nextpn=\ppnn \def\first{#1} \fi \nextpn } \def\ppn#1{\pgn=#1\gobble} \def\ppnn{\pgn=\first} \def\pdfmklnk#1{\lnkcount=0\makelinks #1,END,} \def\addtokens#1#2{\edef\addtoks{\noexpand#1={\the#1#2}}\addtoks} \def\skipspaces#1{\def\PP{#1}\def\D{|}% \ifx\PP\D\let\nextsp\relax \else\let\nextsp\skipspaces \ifx\p\space\else\addtokens{\filename}{\PP}% \advance\filenamelength by 1 \fi \fi \nextsp} \def\getfilename#1{\filenamelength=0\expandafter\skipspaces#1|\relax} \def\pdflink#1{% \leavevmode\Red \begingroup \normalturnoffactive\def\@{@}% \pdfannotlink attr{/Border [0 0 0]}% user{/Subtype /Link /A << /S /URI /URI (#1) >>}% \endgroup } \else \let\pdflink = \gobble \fi % end \ifpdf \message{fonts,} % Font-change commands. % Japanese fonts. \newfam\mcfam \newfam\gtfam \ifjaTeX \catcode`\@ =11 \def\mc{\fam\mcfam \tenmin} \def\gt{\fam\gtfam \tengt} \def\rm{\mc \fam\z@ \tenrm} \def\bf{\gt \fam\bffam \tenbf} \catcode`\@ =12 \fi % Texinfo sort of supports the sans serif font style, which plain TeX does not. % So we set up a \sf analogous to plain's \rm, etc. \newfam\sffam \ifjaTeX \def\sf{\gt \fam\sffam \tensf} \else \def\sf{\fam=\sffam \tensf} \fi \let\li = \sf % Sometimes we call it \li, not \sf. % We don't need math for this one. \def\ttsl{\tenttsl} % Use Computer Modern fonts at \magstephalf (11pt). \newcount\mainmagstep \mainmagstep=\magstephalf % Set the font macro #1 to the font named #2, adding on the % specified font prefix (normally `cm'). % #3 is the font's design size, #4 is a scale factor \def\setfont#1#2#3#4{\font#1=\fontprefix#2#3 scaled #4} % Use cm as the default font prefix. % To specify the font prefix, you must define \fontprefix % before you read in texinfo.tex. \ifx\fontprefix\undefined \def\fontprefix{cm} \fi % Support font families that don't use the same naming scheme as CM. \def\rmshape{r} \def\rmbshape{bx} %where the normal face is bold \def\bfshape{b} \def\bxshape{bx} \def\ttshape{tt} \def\ttbshape{tt} \def\ttslshape{sltt} \def\itshape{ti} \def\itbshape{bxti} \def\slshape{sl} \def\slbshape{bxsl} \def\sfshape{ss} \def\sfbshape{ss} \def\scshape{csc} \def\scbshape{csc} \ifx\bigger\relax \let\mainmagstep=\magstep1 \setfont\textrm\rmshape{12}{1000} \setfont\texttt\ttshape{12}{1000} \ifpTeX \font\textmc=min10 scaled 1200 \font\textgt=goth10 scaled 1200 \fi \ifjTeX \jfont\textmc=dm12 \jfont\textgt=dg12 \fi \else \setfont\textrm\rmshape{10}{\mainmagstep} \setfont\texttt\ttshape{10}{\mainmagstep} \ifpTeX \font\textmc=min10 scaled \magstephalf \font\textgt=goth10 scaled \magstephalf \fi \ifjTeX \jfont\textmc=dm10 scaled \magstephalf \jfont\textgt=dg10 scaled \magstephalf \fi \fi % Instead of cmb10, you many want to use cmbx10. % cmbx10 is a prettier font on its own, but cmb10 % looks better when embedded in a line with cmr10. \setfont\textbf\bfshape{10}{\mainmagstep} \setfont\textit\itshape{10}{\mainmagstep} \setfont\textsl\slshape{10}{\mainmagstep} \setfont\textsf\sfshape{10}{\mainmagstep} \setfont\textsc\scshape{10}{\mainmagstep} \setfont\textttsl\ttslshape{10}{\mainmagstep} \font\texti=cmmi10 scaled \mainmagstep \font\textsy=cmsy10 scaled \mainmagstep % A few fonts for @defun, etc. \ifpTeX \setfont\defbf\bxshape{10}{\magstep1} %was 1314 \setfont\deftt\ttshape{10}{\magstep1} \font\defmc=min10 scaled \magstep1 \font\defgt=goth10 scaled \magstep1 \def\df{\let\tentt=\deftt \let\tenmin=\defmc \let\tengt=\defgt \let\tenbf = \defbf \bf} \else\ifjTeX \setfont\defbf\bxshape{10}{\magstep1} %was 1314 \setfont\deftt\ttshape{10}{\magstep1} \jfont\defmc=dm10 scaled \magstep1 \jfont\defgt=dg10 scaled \magstep1 \def\df{\let\tentt=\deftt \let\tenmin=\defmc \let\tengt=\defgt \let\tenbf = \defbf \bf} \else \setfont\defbf\bxshape{10}{\magstep1} %was 1314 \setfont\deftt\ttshape{10}{\magstep1} \def\df{\let\tentt=\deftt \let\tenbf = \defbf \bf} \fi\fi % Fonts for indices and small examples (9pt). % We actually use the slanted font rather than the italic, % because texinfo normally uses the slanted fonts for that. % Do not make many font distinctions in general in the index, since they % aren't very useful. \setfont\ninett\ttshape{9}{1000} \setfont\ninettsl\ttslshape{10}{900} \setfont\indrm\rmshape{9}{1000} \setfont\indit\itshape{9}{1000} \setfont\indsl\slshape{9}{1000} \ifpTeX \font\indmc=min9 \font\indgt=goth9 \fi \ifjTeX \jfont\indmc=dm9 \jfont\indgt=dg9 \fi \let\indtt=\ninett \let\indttsl=\ninettsl \let\indsf=\indrm \let\indbf=\indrm \setfont\indsc\scshape{10}{900} \font\indi=cmmi9 \font\indsy=cmsy9 % Fonts for title page: \setfont\titlerm\rmbshape{12}{\magstep3} \setfont\titleit\itbshape{10}{\magstep4} \setfont\titlesl\slbshape{10}{\magstep4} \setfont\titlett\ttbshape{12}{\magstep3} \setfont\titlettsl\ttslshape{10}{\magstep4} \setfont\titlesf\sfbshape{17}{\magstep1} \ifpTeX \font\titlemc=min10 scaled \magstep4 \font\titlegt=goth10 scaled \magstep4 \fi \ifjTeX \jfont\titlemc=dm10 scaled \magstep4 \jfont\titlegt=dg10 scaled \magstep4 \fi \let\titlebf=\titlerm \setfont\titlesc\scbshape{10}{\magstep4} \font\titlei=cmmi12 scaled \magstep3 \font\titlesy=cmsy10 scaled \magstep4 \def\authorrm{\secrm} \ifjaTeX \def\authormc{\secmc} \fi % Chapter (and unnumbered) fonts (17.26pt). \setfont\chaprm\rmbshape{12}{\magstep2} \setfont\chapit\itbshape{10}{\magstep3} \setfont\chapsl\slbshape{10}{\magstep3} \setfont\chaptt\ttbshape{12}{\magstep2} \setfont\chapttsl\ttslshape{10}{\magstep3} \setfont\chapsf\sfbshape{17}{1000} \ifpTeX \font\chapmc=min10 scaled \magstep3 \font\chapgt=goth10 scaled \magstep3 \fi \ifjTeX \jfont\chapmc=dm10 scaled \magstep3 \jfont\chapgt=dg10 scaled \magstep3 \fi \let\chapbf=\chaprm \setfont\chapsc\scbshape{10}{\magstep3} \font\chapi=cmmi12 scaled \magstep2 \font\chapsy=cmsy10 scaled \magstep3 % Section fonts (14.4pt). \setfont\secrm\rmbshape{12}{\magstep1} \setfont\secit\itbshape{10}{\magstep2} \setfont\secsl\slbshape{10}{\magstep2} \setfont\sectt\ttbshape{12}{\magstep1} \setfont\secttsl\ttslshape{10}{\magstep2} \setfont\secsf\sfbshape{12}{\magstep1} \ifpTeX \font\secmc=min10 scaled \magstep2 \font\secgt=goth10 scaled \magstep2 \fi \ifjTeX \jfont\secmc=dm10 scaled \magstep2 \jfont\secgt=dg10 scaled \magstep2 \fi \let\secbf\secrm \setfont\secsc\scbshape{10}{\magstep2} \font\seci=cmmi12 scaled \magstep1 \font\secsy=cmsy10 scaled \magstep2 % \setfont\ssecrm\bxshape{10}{\magstep1} % This size an font looked bad. % \setfont\ssecit\itshape{10}{\magstep1} % The letters were too crowded. % \setfont\ssecsl\slshape{10}{\magstep1} % \setfont\ssectt\ttshape{10}{\magstep1} % \setfont\ssecsf\sfshape{10}{\magstep1} %\setfont\ssecrm\bfshape{10}{1315} % Note the use of cmb rather than cmbx. %\setfont\ssecit\itshape{10}{1315} % Also, the size is a little larger than %\setfont\ssecsl\slshape{10}{1315} % being scaled magstep1. %\setfont\ssectt\ttshape{10}{1315} %\setfont\ssecsf\sfshape{10}{1315} %\let\ssecbf=\ssecrm % Subsection fonts (13.15pt). \setfont\ssecrm\rmbshape{12}{\magstephalf} \setfont\ssecit\itbshape{10}{1315} \setfont\ssecsl\slbshape{10}{1315} \setfont\ssectt\ttbshape{12}{\magstephalf} \setfont\ssecttsl\ttslshape{10}{1315} \setfont\ssecsf\sfbshape{12}{\magstephalf} \ifpTeX \font\ssecmc=min10 scaled 1315 \font\ssecgt=goth10 scaled 1315 \fi \ifjTeX \jfont\ssecmc=dm10 scaled 1315 \jfont\ssecgt=dg10 scaled 1315 \fi \let\ssecbf\ssecrm \setfont\ssecsc\scbshape{10}{\magstep1} \font\sseci=cmmi12 scaled \magstephalf \font\ssecsy=cmsy10 scaled 1315 % The smallcaps and symbol fonts should actually be scaled \magstep1.5, % but that is not a standard magnification. % In order for the font changes to affect most math symbols and letters, % we have to define the \textfont of the standard families. Since % texinfo doesn't allow for producing subscripts and superscripts, we % don't bother to reset \scriptfont and \scriptscriptfont (which would % also require loading a lot more fonts). % \ifpTeX \def\resetmathfonts{% \textfont0 = \tenrm \textfont1 = \teni \textfont2 = \tensy \textfont\itfam = \tenit \textfont\slfam = \tensl \textfont\bffam = \tenbf \textfont\ttfam = \tentt \textfont\sffam = \tensf \textfont\mcfam = \tenmin \textfont\gtfam = \tengt } \else \def\resetmathfonts{% \textfont0 = \tenrm \textfont1 = \teni \textfont2 = \tensy \textfont\itfam = \tenit \textfont\slfam = \tensl \textfont\bffam = \tenbf \textfont\ttfam = \tentt \textfont\sffam = \tensf } \fi % The font-changing commands redefine the meanings of \tenSTYLE, instead % of just \STYLE. We do this so that font changes will continue to work % in math mode, where it is the current \fam that is relevant in most % cases, not the current font. Plain TeX does \def\bf{\fam=\bffam % \tenbf}, for example. By redefining \tenbf, we obviate the need to % redefine \bf itself. \ifjaTeX \def\textfonts{% \let\tenrm=\textrm \let\tenit=\textit \let\tensl=\textsl \let\tenbf=\textbf \let\tentt=\texttt \let\smallcaps=\textsc \let\tensf=\textsf \let\teni=\texti \let\tensy=\textsy \let\tenttsl=\textttsl \let\tenmin=\textmc \let\tengt=\textgt \resetmathfonts} \else \def\textfonts{% \let\tenrm=\textrm \let\tenit=\textit \let\tensl=\textsl \let\tenbf=\textbf \let\tentt=\texttt \let\smallcaps=\textsc \let\tensf=\textsf \let\teni=\texti \let\tensy=\textsy \let\tenttsl=\textttsl \resetmathfonts} \fi % \ifjaTeX \def\titlefonts{% \let\tenrm=\titlerm \let\tenit=\titleit \let\tensl=\titlesl \let\tenbf=\titlebf \let\tentt=\titlett \let\smallcaps=\titlesc \let\tensf=\titlesf \let\teni=\titlei \let\tensy=\titlesy \let\tenttsl=\titlettsl \let\tenmin=\titlemc \let\tengt=\titlegt \resetmathfonts \setleading{25pt}} \else \def\titlefonts{% \let\tenrm=\titlerm \let\tenit=\titleit \let\tensl=\titlesl \let\tenbf=\titlebf \let\tentt=\titlett \let\smallcaps=\titlesc \let\tensf=\titlesf \let\teni=\titlei \let\tensy=\titlesy \let\tenttsl=\titlettsl \resetmathfonts \setleading{25pt}} \fi \def\titlefont#1{{\titlefonts\rm #1}} % \ifjaTeX \def\chapfonts{% \let\tenrm=\chaprm \let\tenit=\chapit \let\tensl=\chapsl \let\tenbf=\chapbf \let\tentt=\chaptt \let\smallcaps=\chapsc \let\tensf=\chapsf \let\teni=\chapi \let\tensy=\chapsy \let\tenttsl=\chapttsl \let\tenmin=\chapmc \let\tengt=\chapgt \resetmathfonts \setleading{19pt}} \else \def\chapfonts{% \let\tenrm=\chaprm \let\tenit=\chapit \let\tensl=\chapsl \let\tenbf=\chapbf \let\tentt=\chaptt \let\smallcaps=\chapsc \let\tensf=\chapsf \let\teni=\chapi \let\tensy=\chapsy \let\tenttsl=\chapttsl \resetmathfonts \setleading{19pt}} \fi % \ifjaTeX \def\secfonts{% \let\tenrm=\secrm \let\tenit=\secit \let\tensl=\secsl \let\tenbf=\secbf \let\tentt=\sectt \let\smallcaps=\secsc \let\tensf=\secsf \let\teni=\seci \let\tensy=\secsy \let\tenttsl=\secttsl \let\tenmin=\secmc \let\tengt=\secgt \resetmathfonts \setleading{16pt}} \else \def\secfonts{% \let\tenrm=\secrm \let\tenit=\secit \let\tensl=\secsl \let\tenbf=\secbf \let\tentt=\sectt \let\smallcaps=\secsc \let\tensf=\secsf \let\teni=\seci \let\tensy=\secsy \let\tenttsl=\secttsl \resetmathfonts \setleading{16pt}} \fi % \ifjaTeX \def\subsecfonts{% \let\tenrm=\ssecrm \let\tenit=\ssecit \let\tensl=\ssecsl \let\tenbf=\ssecbf \let\tentt=\ssectt \let\smallcaps=\ssecsc \let\tensf=\ssecsf \let\teni=\sseci \let\tensy=\ssecsy \let\tenttsl=\ssecttsl \let\tenmin=\ssecmc \let\tengt=\ssecgt \resetmathfonts \setleading{15pt}} \else \def\subsecfonts{% \let\tenrm=\ssecrm \let\tenit=\ssecit \let\tensl=\ssecsl \let\tenbf=\ssecbf \let\tentt=\ssectt \let\smallcaps=\ssecsc \let\tensf=\ssecsf \let\teni=\sseci \let\tensy=\ssecsy \let\tenttsl=\ssecttsl \resetmathfonts \setleading{15pt}} \fi \let\subsubsecfonts = \subsecfonts % Maybe make sssec fonts scaled magstephalf? % \ifjaTeX \def\indexfonts{% \let\tenrm=\indrm \let\tenit=\indit \let\tensl=\indsl \let\tenbf=\indbf \let\tentt=\indtt \let\smallcaps=\indsc \let\tensf=\indsf \let\teni=\indi \let\tensy=\indsy \let\tenttsl=\indttsl \let\tenmin=\indmc \let\tengt=\indgt \resetmathfonts \setleading{10pt}} \else \def\indexfonts{% \let\tenrm=\indrm \let\tenit=\indit \let\tensl=\indsl \let\tenbf=\indbf \let\tentt=\indtt \let\smallcaps=\indsc \let\tensf=\indsf \let\teni=\indi \let\tensy=\indsy \let\tenttsl=\indttsl \resetmathfonts \setleading{10pt}} \fi % Set up the default fonts, so we can use them for creating boxes. % \textfonts % Define these so they can be easily changed for other fonts. \def\angleleft{$\langle$} \def\angleright{$\rangle$} % Count depth in font-changes, for error checks \newcount\fontdepth \fontdepth=0 % Fonts for short table of contents. \setfont\shortcontrm\rmshape{12}{1000} \setfont\shortcontbf\bxshape{12}{1000} \setfont\shortcontsl\slshape{12}{1000} \ifpTeX \font\shortcontmc=min10 scaled \magstep1 \font\shortcontgt=goth10 scaled \magstep1 \fi \ifjTeX \jfont\shortcontmc=dm10 scaled \magstep1 \jfont\shortcontgt=dg10 scaled \magstep1 \fi %% Add scribe-like font environments, plus @l for inline lisp (usually sans %% serif) and @ii for TeX italic % \smartitalic{ARG} outputs arg in italics, followed by an italic correction % unless the following character is such as not to need one. \def\smartitalicx{\ifx\next,\else\ifx\next-\else\ifx\next.\else\/\fi\fi\fi} \def\smartslanted#1{{\sl #1}\futurelet\next\smartitalicx} \def\smartitalic#1{{\it #1}\futurelet\next\smartitalicx} \let\i=\smartitalic \let\var=\smartslanted \let\dfn=\smartslanted \let\emph=\smartitalic \let\cite=\smartslanted \def\b#1{{\bf #1}} \let\strong=\b % We can't just use \exhyphenpenalty, because that only has effect at % the end of a paragraph. Restore normal hyphenation at the end of the % group within which \nohyphenation is presumably called. % \def\nohyphenation{\hyphenchar\font = -1 \aftergroup\restorehyphenation} \def\restorehyphenation{\hyphenchar\font = `- } \def\t#1{% {\tt \rawbackslash \frenchspacing #1}% \null } \let\ttfont=\t \def\samp#1{`\tclose{#1}'\null} \setfont\smallrm\rmshape{8}{1000} \font\smallsy=cmsy9 \def\key#1{{\smallrm\textfont2=\smallsy \leavevmode\hbox{% \raise0.4pt\hbox{\angleleft}\kern-.08em\vtop{% \vbox{\hrule\kern-0.4pt \hbox{\raise0.4pt\hbox{\vphantom{\angleleft}}#1}}% \kern-0.4pt\hrule}% \kern-.06em\raise0.4pt\hbox{\angleright}}}} % The old definition, with no lozenge: %\def\key #1{{\ttsl \nohyphenation \uppercase{#1}}\null} \def\ctrl #1{{\tt \rawbackslash \hat}#1} % @file, @option are the same as @samp. \let\file=\samp \let\option=\samp % @code is a modification of @t, % which makes spaces the same size as normal in the surrounding text. \def\tclose#1{% {% % Change normal interword space to be same as for the current font. \spaceskip = \fontdimen2\font % % Switch to typewriter. \tt % % But `\ ' produces the large typewriter interword space. \def\ {{\spaceskip = 0pt{} }}% % % Turn off hyphenation. \nohyphenation % \rawbackslash \frenchspacing #1% }% \null } % We *must* turn on hyphenation at `-' and `_' in \code. % Otherwise, it is too hard to avoid overfull hboxes % in the Emacs manual, the Library manual, etc. % Unfortunately, TeX uses one parameter (\hyphenchar) to control % both hyphenation at - and hyphenation within words. % We must therefore turn them both off (\tclose does that) % and arrange explicitly to hyphenate at a dash. % -- rms. { \catcode`\-=\active \catcode`\_=\active % \global\def\code{\begingroup \catcode`\-=\active \let-\codedash \catcode`\_=\active \let_\codeunder \codex } % % If we end up with any active - characters when handling the index, % just treat them as a normal -. \global\def\indexbreaks{\catcode`\-=\active \let-\realdash} } \def\realdash{-} \def\codedash{-\discretionary{}{}{}} \def\codeunder{\ifusingtt{\normalunderscore\discretionary{}{}{}}{\_}} \def\codex #1{\tclose{#1}\endgroup} %\let\exp=\tclose %Was temporary % @kbd is like @code, except that if the argument is just one @key command, % then @kbd has no effect. % @kbdinputstyle -- arg is `distinct' (@kbd uses slanted tty font always), % `example' (@kbd uses ttsl only inside of @example and friends), % or `code' (@kbd uses normal tty font always). \def\kbdinputstyle{\parsearg\kbdinputstylexxx} \def\kbdinputstylexxx#1{% \def\arg{#1}% \ifx\arg\worddistinct \gdef\kbdexamplefont{\ttsl}\gdef\kbdfont{\ttsl}% \else\ifx\arg\wordexample \gdef\kbdexamplefont{\ttsl}\gdef\kbdfont{\tt}% \else\ifx\arg\wordcode \gdef\kbdexamplefont{\tt}\gdef\kbdfont{\tt}% \fi\fi\fi } \def\worddistinct{distinct} \def\wordexample{example} \def\wordcode{code} % Default is kbdinputdistinct. (Too much of a hassle to call the macro, % the catcodes are wrong for parsearg to work.) \gdef\kbdexamplefont{\ttsl}\gdef\kbdfont{\ttsl} \def\xkey{\key} \def\kbdfoo#1#2#3\par{\def\one{#1}\def\three{#3}\def\threex{??}% \ifx\one\xkey\ifx\threex\three \key{#2}% \else{\tclose{\kbdfont\look}}\fi \else{\tclose{\kbdfont\look}}\fi} % For @url, @env, @command quotes seem unnecessary, so use \code. \let\url=\code \let\env=\code \let\command=\code % @uref (abbreviation for `urlref') takes an optional (comma-separated) % second argument specifying the text to display and an optional third % arg as text to display instead of (rather than in addition to) the url % itself. First (mandatory) arg is the url. Perhaps eventually put in % a hypertex \special here. % \def\uref#1{\douref #1,,,\finish} \def\douref#1,#2,#3,#4\finish{% \pdflink{#1}% \setbox0 = \hbox{\ignorespaces #3}% \ifdim\wd0 > 0pt \unhbox0 % third arg given, show only that \else \setbox0 = \hbox{\ignorespaces #2}% \ifdim\wd0 > 0pt \ifpdf \unhbox0 % PDF: 2nd arg given, show only it \else \unhbox0\ (\code{#1})% DVI: 2nd arg given, show both it and url \fi \else \code{#1}% only url given, so show it \fi \fi % \ifpdf \Black\pdfendlink \fi } % rms does not like angle brackets --karl, 17may97. % So now @email is just like @uref, unless we are pdf. % %\def\email#1{\angleleft{\tt #1}\angleright} \ifpdf \def\email#1{\doemail#1,,\finish} \def\doemail#1,#2,#3\finish{% \pdflink{mailto:#1}% \setbox0 = \hbox{\ignorespaces #2}% \ifdim\wd0>0pt\unhbox0\else\code{#1}\fi \Black\pdfendlink } \else \let\email=\uref \fi % Check if we are currently using a typewriter font. Since all the % Computer Modern typewriter fonts have zero interword stretch (and % shrink), and it is reasonable to expect all typewriter fonts to have % this property, we can check that font parameter. % \def\ifmonospace{\ifdim\fontdimen3\font=0pt } % Typeset a dimension, e.g., `in' or `pt'. The only reason for the % argument is to make the input look right: @dmn{pt} instead of @dmn{}pt. % \def\dmn#1{\thinspace #1} \def\kbd#1{\def\look{#1}\expandafter\kbdfoo\look??\par} % @l was never documented to mean ``switch to the Lisp font'', % and it is not used as such in any manual I can find. We need it for % Polish suppressed-l. --karl, 22sep96. %\def\l#1{{\li #1}\null} % Explicit font changes: @r, @sc, undocumented @ii. \def\r#1{{\rm #1}} % roman font \def\sc#1{{\smallcaps#1}} % smallcaps font \def\ii#1{{\it #1}} % italic font % @acronym downcases the argument and prints in smallcaps. \def\acronym#1{{\smallcaps \lowercase{#1}}} % @pounds{} is a sterling sign. \def\pounds{{\it\$}} \message{page headings,} \newskip\titlepagetopglue \titlepagetopglue = 1.5in \newskip\titlepagebottomglue \titlepagebottomglue = 2pc % First the title page. Must do @settitle before @titlepage. \newif\ifseenauthor \newif\iffinishedtitlepage % Do an implicit @contents or @shortcontents after @end titlepage if the % user says @setcontentsaftertitlepage or @setshortcontentsaftertitlepage. % \newif\ifsetcontentsaftertitlepage \let\setcontentsaftertitlepage = \setcontentsaftertitlepagetrue \newif\ifsetshortcontentsaftertitlepage \let\setshortcontentsaftertitlepage = \setshortcontentsaftertitlepagetrue \def\shorttitlepage{\parsearg\shorttitlepagezzz} \def\shorttitlepagezzz #1{\begingroup\hbox{}\vskip 1.5in \chaprm \centerline{#1}% \endgroup\page\hbox{}\page} \def\titlepage{\begingroup \parindent=0pt \textfonts \let\subtitlerm=\tenrm \def\subtitlefont{\subtitlerm \normalbaselineskip = 13pt \normalbaselines}% % \ifjaTeX \def\authorfont{\authormc\authorrm \normalbaselineskip = 16pt \normalbaselines}% \else \def\authorfont{\authorrm \normalbaselineskip = 16pt \normalbaselines}% \fi % % Leave some space at the very top of the page. \vglue\titlepagetopglue % % Now you can print the title using @title. \def\title{\parsearg\titlezzz}% \def\titlezzz##1{\leftline{\titlefonts\rm ##1} % print a rule at the page bottom also. \finishedtitlepagefalse \vskip4pt \hrule height 4pt width \hsize \vskip4pt}% % No rule at page bottom unless we print one at the top with @title. \finishedtitlepagetrue % % Now you can put text using @subtitle. \def\subtitle{\parsearg\subtitlezzz}% \def\subtitlezzz##1{{\subtitlefont \rightline{##1}}}% % % @author should come last, but may come many times. \def\author{\parsearg\authorzzz}% \def\authorzzz##1{\ifseenauthor\else\vskip 0pt plus 1filll\seenauthortrue\fi {\authorfont \leftline{##1}}}% % % Most title ``pages'' are actually two pages long, with space % at the top of the second. We don't want the ragged left on the second. \let\oldpage = \page \def\page{% \iffinishedtitlepage\else \finishtitlepage \fi \oldpage \let\page = \oldpage \hbox{}}% % \def\page{\oldpage \hbox{}} } \def\Etitlepage{% \iffinishedtitlepage\else \finishtitlepage \fi % It is important to do the page break before ending the group, % because the headline and footline are only empty inside the group. % If we use the new definition of \page, we always get a blank page % after the title page, which we certainly don't want. \oldpage \endgroup % % If they want short, they certainly want long too. \ifsetshortcontentsaftertitlepage \shortcontents \contents \global\let\shortcontents = \relax \global\let\contents = \relax \fi % \ifsetcontentsaftertitlepage \contents \global\let\contents = \relax \global\let\shortcontents = \relax \fi % \HEADINGSon } \def\finishtitlepage{% \vskip4pt \hrule height 2pt width \hsize \vskip\titlepagebottomglue \finishedtitlepagetrue } %%% Set up page headings and footings. \let\thispage=\folio \newtoks\evenheadline % headline on even pages \newtoks\oddheadline % headline on odd pages \newtoks\evenfootline % footline on even pages \newtoks\oddfootline % footline on odd pages % Now make Tex use those variables \headline={{\textfonts\rm \ifodd\pageno \the\oddheadline \else \the\evenheadline \fi}} \footline={{\textfonts\rm \ifodd\pageno \the\oddfootline \else \the\evenfootline \fi}\HEADINGShook} \let\HEADINGShook=\relax % Commands to set those variables. % For example, this is what @headings on does % @evenheading @thistitle|@thispage|@thischapter % @oddheading @thischapter|@thispage|@thistitle % @evenfooting @thisfile|| % @oddfooting ||@thisfile \def\evenheading{\parsearg\evenheadingxxx} \def\oddheading{\parsearg\oddheadingxxx} \def\everyheading{\parsearg\everyheadingxxx} \def\evenfooting{\parsearg\evenfootingxxx} \def\oddfooting{\parsearg\oddfootingxxx} \def\everyfooting{\parsearg\everyfootingxxx} {\catcode`\@=0 % \gdef\evenheadingxxx #1{\evenheadingyyy #1@|@|@|@|\finish} \gdef\evenheadingyyy #1@|#2@|#3@|#4\finish{% \global\evenheadline={\rlap{\centerline{#2}}\line{#1\hfil#3}}} \gdef\oddheadingxxx #1{\oddheadingyyy #1@|@|@|@|\finish} \gdef\oddheadingyyy #1@|#2@|#3@|#4\finish{% \global\oddheadline={\rlap{\centerline{#2}}\line{#1\hfil#3}}} \gdef\everyheadingxxx#1{\oddheadingxxx{#1}\evenheadingxxx{#1}}% \gdef\evenfootingxxx #1{\evenfootingyyy #1@|@|@|@|\finish} \gdef\evenfootingyyy #1@|#2@|#3@|#4\finish{% \global\evenfootline={\rlap{\centerline{#2}}\line{#1\hfil#3}}} \gdef\oddfootingxxx #1{\oddfootingyyy #1@|@|@|@|\finish} \gdef\oddfootingyyy #1@|#2@|#3@|#4\finish{% \global\oddfootline = {\rlap{\centerline{#2}}\line{#1\hfil#3}}% % % Leave some space for the footline. Hopefully ok to assume % @evenfooting will not be used by itself. \global\advance\pageheight by -\baselineskip \global\advance\vsize by -\baselineskip } \gdef\everyfootingxxx#1{\oddfootingxxx{#1}\evenfootingxxx{#1}} % }% unbind the catcode of @. % @headings double turns headings on for double-sided printing. % @headings single turns headings on for single-sided printing. % @headings off turns them off. % @headings on same as @headings double, retained for compatibility. % @headings after turns on double-sided headings after this page. % @headings doubleafter turns on double-sided headings after this page. % @headings singleafter turns on single-sided headings after this page. % By default, they are off at the start of a document, % and turned `on' after @end titlepage. \def\headings #1 {\csname HEADINGS#1\endcsname} \def\HEADINGSoff{ \global\evenheadline={\hfil} \global\evenfootline={\hfil} \global\oddheadline={\hfil} \global\oddfootline={\hfil}} \HEADINGSoff % When we turn headings on, set the page number to 1. % For double-sided printing, put current file name in lower left corner, % chapter name on inside top of right hand pages, document % title on inside top of left hand pages, and page numbers on outside top % edge of all pages. \def\HEADINGSdouble{ \global\pageno=1 \global\evenfootline={\hfil} \global\oddfootline={\hfil} \global\evenheadline={\line{\folio\hfil\thistitle}} \global\oddheadline={\line{\thischapter\hfil\folio}} \global\let\contentsalignmacro = \chapoddpage } \let\contentsalignmacro = \chappager % For single-sided printing, chapter title goes across top left of page, % page number on top right. \def\HEADINGSsingle{ \global\pageno=1 \global\evenfootline={\hfil} \global\oddfootline={\hfil} \global\evenheadline={\line{\thischapter\hfil\folio}} \global\oddheadline={\line{\thischapter\hfil\folio}} \global\let\contentsalignmacro = \chappager } \def\HEADINGSon{\HEADINGSdouble} \def\HEADINGSafter{\let\HEADINGShook=\HEADINGSdoublex} \let\HEADINGSdoubleafter=\HEADINGSafter \def\HEADINGSdoublex{% \global\evenfootline={\hfil} \global\oddfootline={\hfil} \global\evenheadline={\line{\folio\hfil\thistitle}} \global\oddheadline={\line{\thischapter\hfil\folio}} \global\let\contentsalignmacro = \chapoddpage } \def\HEADINGSsingleafter{\let\HEADINGShook=\HEADINGSsinglex} \def\HEADINGSsinglex{% \global\evenfootline={\hfil} \global\oddfootline={\hfil} \global\evenheadline={\line{\thischapter\hfil\folio}} \global\oddheadline={\line{\thischapter\hfil\folio}} \global\let\contentsalignmacro = \chappager } % Subroutines used in generating headings % Produces Day Month Year style of output. \def\today{% \number\day\space \ifcase\month \or\putwordMJan\or\putwordMFeb\or\putwordMMar\or\putwordMApr \or\putwordMMay\or\putwordMJun\or\putwordMJul\or\putwordMAug \or\putwordMSep\or\putwordMOct\or\putwordMNov\or\putwordMDec \fi \space\number\year} % @settitle line... specifies the title of the document, for headings. % It generates no output of its own. \def\thistitle{\putwordNoTitle} \def\settitle{\parsearg\settitlezzz} \def\settitlezzz #1{\gdef\thistitle{#1}} \message{tables,} % Tables -- @table, @ftable, @vtable, @item(x), @kitem(x), @xitem(x). % default indentation of table text \newdimen\tableindent \tableindent=.8in % default indentation of @itemize and @enumerate text \newdimen\itemindent \itemindent=.3in % margin between end of table item and start of table text. \newdimen\itemmargin \itemmargin=.1in % used internally for \itemindent minus \itemmargin \newdimen\itemmax % Note @table, @vtable, and @vtable define @item, @itemx, etc., with % these defs. % They also define \itemindex % to index the item name in whatever manner is desired (perhaps none). \newif\ifitemxneedsnegativevskip \def\itemxpar{\par\ifitemxneedsnegativevskip\nobreak\vskip-\parskip\nobreak\fi} \def\internalBitem{\smallbreak \parsearg\itemzzz} \def\internalBitemx{\itemxpar \parsearg\itemzzz} \def\internalBxitem "#1"{\def\xitemsubtopix{#1} \smallbreak \parsearg\xitemzzz} \def\internalBxitemx "#1"{\def\xitemsubtopix{#1} \itemxpar \parsearg\xitemzzz} \def\internalBkitem{\smallbreak \parsearg\kitemzzz} \def\internalBkitemx{\itemxpar \parsearg\kitemzzz} \def\kitemzzz #1{\dosubind {kw}{\code{#1}}{for {\bf \lastfunction}}% \itemzzz {#1}} \def\xitemzzz #1{\dosubind {kw}{\code{#1}}{for {\bf \xitemsubtopic}}% \itemzzz {#1}} \def\itemzzz #1{\begingroup % \advance\hsize by -\rightskip \advance\hsize by -\tableindent \setbox0=\hbox{\itemfont{#1}}% \itemindex{#1}% \nobreak % This prevents a break before @itemx. % % If the item text does not fit in the space we have, put it on a line % by itself, and do not allow a page break either before or after that % line. We do not start a paragraph here because then if the next % command is, e.g., @kindex, the whatsit would get put into the % horizontal list on a line by itself, resulting in extra blank space. \ifdim \wd0>\itemmax % % Make this a paragraph so we get the \parskip glue and wrapping, % but leave it ragged-right. \begingroup \advance\leftskip by-\tableindent \advance\hsize by\tableindent \advance\rightskip by0pt plus1fil \leavevmode\unhbox0\par \endgroup % % We're going to be starting a paragraph, but we don't want the % \parskip glue -- logically it's part of the @item we just started. \nobreak \vskip-\parskip % % Stop a page break at the \parskip glue coming up. Unfortunately % we can't prevent a possible page break at the following % \baselineskip glue. \nobreak \endgroup \itemxneedsnegativevskipfalse \else % The item text fits into the space. Start a paragraph, so that the % following text (if any) will end up on the same line. \noindent % Do this with kerns and \unhbox so that if there is a footnote in % the item text, it can migrate to the main vertical list and % eventually be printed. \nobreak\kern-\tableindent \dimen0 = \itemmax \advance\dimen0 by \itemmargin \advance\dimen0 by -\wd0 \unhbox0 \nobreak\kern\dimen0 \endgroup \itemxneedsnegativevskiptrue \fi } \def\item{\errmessage{@item while not in a table}} \def\itemx{\errmessage{@itemx while not in a table}} \def\kitem{\errmessage{@kitem while not in a table}} \def\kitemx{\errmessage{@kitemx while not in a table}} \def\xitem{\errmessage{@xitem while not in a table}} \def\xitemx{\errmessage{@xitemx while not in a table}} % Contains a kludge to get @end[description] to work. \def\description{\tablez{\dontindex}{1}{}{}{}{}} % @table, @ftable, @vtable. \def\table{\begingroup\inENV\obeylines\obeyspaces\tablex} {\obeylines\obeyspaces% \gdef\tablex #1^^M{% \tabley\dontindex#1 \endtabley}} \def\ftable{\begingroup\inENV\obeylines\obeyspaces\ftablex} {\obeylines\obeyspaces% \gdef\ftablex #1^^M{% \tabley\fnitemindex#1 \endtabley \def\Eftable{\endgraf\afterenvbreak\endgroup}% \let\Etable=\relax}} \def\vtable{\begingroup\inENV\obeylines\obeyspaces\vtablex} {\obeylines\obeyspaces% \gdef\vtablex #1^^M{% \tabley\vritemindex#1 \endtabley \def\Evtable{\endgraf\afterenvbreak\endgroup}% \let\Etable=\relax}} \def\dontindex #1{} \def\fnitemindex #1{\doind {fn}{\code{#1}}}% \def\vritemindex #1{\doind {vr}{\code{#1}}}% {\obeyspaces % \gdef\tabley#1#2 #3 #4 #5 #6 #7\endtabley{\endgroup% \tablez{#1}{#2}{#3}{#4}{#5}{#6}}} \def\tablez #1#2#3#4#5#6{% \aboveenvbreak % \begingroup % \def\Edescription{\Etable}% Necessary kludge. \let\itemindex=#1% \ifnum 0#3>0 \advance \leftskip by #3\mil \fi % \ifnum 0#4>0 \tableindent=#4\mil \fi % \ifnum 0#5>0 \advance \rightskip by #5\mil \fi % \def\itemfont{#2}% \itemmax=\tableindent % \advance \itemmax by -\itemmargin % \advance \leftskip by \tableindent % \exdentamount=\tableindent \parindent = 0pt \parskip = \smallskipamount \ifdim \parskip=0pt \parskip=2pt \fi% \def\Etable{\endgraf\afterenvbreak\endgroup}% \let\item = \internalBitem % \let\itemx = \internalBitemx % \let\kitem = \internalBkitem % \let\kitemx = \internalBkitemx % \let\xitem = \internalBxitem % \let\xitemx = \internalBxitemx % } % This is the counter used by @enumerate, which is really @itemize \newcount \itemno \def\itemize{\parsearg\itemizezzz} \def\itemizezzz #1{% \begingroup % ended by the @end itemize \itemizey {#1}{\Eitemize} } \def\itemizey #1#2{% \aboveenvbreak % \itemmax=\itemindent % \advance \itemmax by -\itemmargin % \advance \leftskip by \itemindent % \exdentamount=\itemindent \parindent = 0pt % \parskip = \smallskipamount % \ifdim \parskip=0pt \parskip=2pt \fi% \def#2{\endgraf\afterenvbreak\endgroup}% \def\itemcontents{#1}% \let\item=\itemizeitem} % Set sfcode to normal for the chars that usually have another value. % These are `.?!:;,' \def\frenchspacing{\sfcode46=1000 \sfcode63=1000 \sfcode33=1000 \sfcode58=1000 \sfcode59=1000 \sfcode44=1000 } % \splitoff TOKENS\endmark defines \first to be the first token in % TOKENS, and \rest to be the remainder. % \def\splitoff#1#2\endmark{\def\first{#1}\def\rest{#2}}% % Allow an optional argument of an uppercase letter, lowercase letter, % or number, to specify the first label in the enumerated list. No % argument is the same as `1'. % \def\enumerate{\parsearg\enumeratezzz} \def\enumeratezzz #1{\enumeratey #1 \endenumeratey} \def\enumeratey #1 #2\endenumeratey{% \begingroup % ended by the @end enumerate % % If we were given no argument, pretend we were given `1'. \def\thearg{#1}% \ifx\thearg\empty \def\thearg{1}\fi % % Detect if the argument is a single token. If so, it might be a % letter. Otherwise, the only valid thing it can be is a number. % (We will always have one token, because of the test we just made. % This is a good thing, since \splitoff doesn't work given nothing at % all -- the first parameter is undelimited.) \expandafter\splitoff\thearg\endmark \ifx\rest\empty % Only one token in the argument. It could still be anything. % A ``lowercase letter'' is one whose \lccode is nonzero. % An ``uppercase letter'' is one whose \lccode is both nonzero, and % not equal to itself. % Otherwise, we assume it's a number. % % We need the \relax at the end of the \ifnum lines to stop TeX from % continuing to look for a . % \ifnum\lccode\expandafter`\thearg=0\relax \numericenumerate % a number (we hope) \else % It's a letter. \ifnum\lccode\expandafter`\thearg=\expandafter`\thearg\relax \lowercaseenumerate % lowercase letter \else \uppercaseenumerate % uppercase letter \fi \fi \else % Multiple tokens in the argument. We hope it's a number. \numericenumerate \fi } % An @enumerate whose labels are integers. The starting integer is % given in \thearg. % \def\numericenumerate{% \itemno = \thearg \startenumeration{\the\itemno}% } % The starting (lowercase) letter is in \thearg. \def\lowercaseenumerate{% \itemno = \expandafter`\thearg \startenumeration{% % Be sure we're not beyond the end of the alphabet. \ifnum\itemno=0 \errmessage{No more lowercase letters in @enumerate; get a bigger alphabet}% \fi \char\lccode\itemno }% } % The starting (uppercase) letter is in \thearg. \def\uppercaseenumerate{% \itemno = \expandafter`\thearg \startenumeration{% % Be sure we're not beyond the end of the alphabet. \ifnum\itemno=0 \errmessage{No more uppercase letters in @enumerate; get a bigger alphabet} \fi \char\uccode\itemno }% } % Call itemizey, adding a period to the first argument and supplying the % common last two arguments. Also subtract one from the initial value in % \itemno, since @item increments \itemno. % \def\startenumeration#1{% \advance\itemno by -1 \itemizey{#1.}\Eenumerate\flushcr } % @alphaenumerate and @capsenumerate are abbreviations for giving an arg % to @enumerate. % \def\alphaenumerate{\enumerate{a}} \def\capsenumerate{\enumerate{A}} \def\Ealphaenumerate{\Eenumerate} \def\Ecapsenumerate{\Eenumerate} % Definition of @item while inside @itemize. \def\itemizeitem{% \advance\itemno by 1 {\let\par=\endgraf \smallbreak}% \ifhmode \errmessage{In hmode at itemizeitem}\fi {\parskip=0in \hskip 0pt \hbox to 0pt{\hss \itemcontents\hskip \itemmargin}% \vadjust{\penalty 1200}}% \flushcr} % @multitable macros % Amy Hendrickson, 8/18/94, 3/6/96 % % @multitable ... @end multitable will make as many columns as desired. % Contents of each column will wrap at width given in preamble. Width % can be specified either with sample text given in a template line, % or in percent of \hsize, the current width of text on page. % Table can continue over pages but will only break between lines. % To make preamble: % % Either define widths of columns in terms of percent of \hsize: % @multitable @columnfractions .25 .3 .45 % @item ... % % Numbers following @columnfractions are the percent of the total % current hsize to be used for each column. You may use as many % columns as desired. % Or use a template: % @multitable {Column 1 template} {Column 2 template} {Column 3 template} % @item ... % using the widest term desired in each column. % % For those who want to use more than one line's worth of words in % the preamble, break the line within one argument and it % will parse correctly, i.e., % % @multitable {Column 1 template} {Column 2 template} {Column 3 % template} % Not: % @multitable {Column 1 template} {Column 2 template} % {Column 3 template} % Each new table line starts with @item, each subsequent new column % starts with @tab. Empty columns may be produced by supplying @tab's % with nothing between them for as many times as empty columns are needed, % ie, @tab@tab@tab will produce two empty columns. % @item, @tab, @multitable or @end multitable do not need to be on their % own lines, but it will not hurt if they are. % Sample multitable: % @multitable {Column 1 template} {Column 2 template} {Column 3 template} % @item first col stuff @tab second col stuff @tab third col % @item % first col stuff % @tab % second col stuff % @tab % third col % @item first col stuff @tab second col stuff % @tab Many paragraphs of text may be used in any column. % % They will wrap at the width determined by the template. % @item@tab@tab This will be in third column. % @end multitable % Default dimensions may be reset by user. % @multitableparskip is vertical space between paragraphs in table. % @multitableparindent is paragraph indent in table. % @multitablecolmargin is horizontal space to be left between columns. % @multitablelinespace is space to leave between table items, baseline % to baseline. % 0pt means it depends on current normal line spacing. % \newskip\multitableparskip \newskip\multitableparindent \newdimen\multitablecolspace \newskip\multitablelinespace \multitableparskip=0pt \multitableparindent=6pt \multitablecolspace=10pt \multitablelinespace=0pt % Macros used to set up halign preamble: % \let\endsetuptable\relax \def\xendsetuptable{\endsetuptable} \let\columnfractions\relax \def\xcolumnfractions{\columnfractions} \newif\ifsetpercent % #1 is the part of the @columnfraction before the decimal point, which % is presumably either 0 or the empty string (but we don't check, we % just throw it away). #2 is the decimal part, which we use as the % percent of \hsize for this column. \def\pickupwholefraction#1.#2 {% \global\advance\colcount by 1 \expandafter\xdef\csname col\the\colcount\endcsname{.#2\hsize}% \setuptable } \newcount\colcount \def\setuptable#1{% \def\firstarg{#1}% \ifx\firstarg\xendsetuptable \let\go = \relax \else \ifx\firstarg\xcolumnfractions \global\setpercenttrue \else \ifsetpercent \let\go\pickupwholefraction \else \global\advance\colcount by 1 \setbox0=\hbox{#1\unskip }% Add a normal word space as a separator; % typically that is always in the input, anyway. \expandafter\xdef\csname col\the\colcount\endcsname{\the\wd0}% \fi \fi \ifx\go\pickupwholefraction % Put the argument back for the \pickupwholefraction call, so % we'll always have a period there to be parsed. \def\go{\pickupwholefraction#1}% \else \let\go = \setuptable \fi% \fi \go } % This used to have \hskip1sp. But then the space in a template line is % not enough. That is bad. So let's go back to just & until we % encounter the problem it was intended to solve again. % --karl, nathan@acm.org, 20apr99. \def\tab{&} % @multitable ... @end multitable definitions: % \def\multitable{\parsearg\dotable} \def\dotable#1{\bgroup \vskip\parskip \let\item\crcr \tolerance=9500 \hbadness=9500 \setmultitablespacing \parskip=\multitableparskip \parindent=\multitableparindent \overfullrule=0pt \global\colcount=0 \def\Emultitable{\global\setpercentfalse\cr\egroup\egroup}% % % To parse everything between @multitable and @item: \setuptable#1 \endsetuptable % % \everycr will reset column counter, \colcount, at the end of % each line. Every column entry will cause \colcount to advance by one. % The table preamble % looks at the current \colcount to find the correct column width. \everycr{\noalign{% % % \filbreak%% keeps underfull box messages off when table breaks over pages. % Maybe so, but it also creates really weird page breaks when the table % breaks over pages. Wouldn't \vfil be better? Wait until the problem % manifests itself, so it can be fixed for real --karl. \global\colcount=0\relax}}% % % This preamble sets up a generic column definition, which will % be used as many times as user calls for columns. % \vtop will set a single line and will also let text wrap and % continue for many paragraphs if desired. \halign\bgroup&\global\advance\colcount by 1\relax \multistrut\vtop{\hsize=\expandafter\csname col\the\colcount\endcsname % % In order to keep entries from bumping into each other % we will add a \leftskip of \multitablecolspace to all columns after % the first one. % % If a template has been used, we will add \multitablecolspace % to the width of each template entry. % % If the user has set preamble in terms of percent of \hsize we will % use that dimension as the width of the column, and the \leftskip % will keep entries from bumping into each other. Table will start at % left margin and final column will justify at right margin. % % Make sure we don't inherit \rightskip from the outer environment. \rightskip=0pt \ifnum\colcount=1 % The first column will be indented with the surrounding text. \advance\hsize by\leftskip \else \ifsetpercent \else % If user has not set preamble in terms of percent of \hsize % we will advance \hsize by \multitablecolspace. \advance\hsize by \multitablecolspace \fi % In either case we will make \leftskip=\multitablecolspace: \leftskip=\multitablecolspace \fi % Ignoring space at the beginning and end avoids an occasional spurious % blank line, when TeX decides to break the line at the space before the % box from the multistrut, so the strut ends up on a line by itself. % For example: % @multitable @columnfractions .11 .89 % @item @code{#} % @tab Legal holiday which is valid in major parts of the whole country. % Is automatically provided with highlighting sequences respectively marking % characters. \noindent\ignorespaces##\unskip\multistrut}\cr } \def\setmultitablespacing{% test to see if user has set \multitablelinespace. % If so, do nothing. If not, give it an appropriate dimension based on % current baselineskip. \ifdim\multitablelinespace=0pt %% strut to put in table in case some entry doesn't have descenders, %% to keep lines equally spaced \let\multistrut = \strut %% Test to see if parskip is larger than space between lines of %% table. If not, do nothing. %% If so, set to same dimension as multitablelinespace. \else \gdef\multistrut{\vrule height\multitablelinespace depth\dp0 width0pt\relax} \fi \ifdim\multitableparskip>\multitablelinespace \global\multitableparskip=\multitablelinespace \global\advance\multitableparskip-7pt %% to keep parskip somewhat smaller %% than skip between lines in the table. \fi% \ifdim\multitableparskip=0pt \global\multitableparskip=\multitablelinespace \global\advance\multitableparskip-7pt %% to keep parskip somewhat smaller %% than skip between lines in the table. \fi} \message{conditionals,} % Prevent errors for section commands. % Used in @ignore and in failing conditionals. \def\ignoresections{% \let\chapter=\relax \let\unnumbered=\relax \let\top=\relax \let\unnumberedsec=\relax \let\unnumberedsection=\relax \let\unnumberedsubsec=\relax \let\unnumberedsubsection=\relax \let\unnumberedsubsubsec=\relax \let\unnumberedsubsubsection=\relax \let\section=\relax \let\subsec=\relax \let\subsubsec=\relax \let\subsection=\relax \let\subsubsection=\relax \let\appendix=\relax \let\appendixsec=\relax \let\appendixsection=\relax \let\appendixsubsec=\relax \let\appendixsubsection=\relax \let\appendixsubsubsec=\relax \let\appendixsubsubsection=\relax \let\contents=\relax \let\smallbook=\relax \let\titlepage=\relax } % Used in nested conditionals, where we have to parse the Texinfo source % and so want to turn off most commands, in case they are used % incorrectly. % \def\ignoremorecommands{% \let\defcodeindex = \relax \let\defcv = \relax \let\deffn = \relax \let\deffnx = \relax \let\defindex = \relax \let\defivar = \relax \let\defmac = \relax \let\defmethod = \relax \let\defop = \relax \let\defopt = \relax \let\defspec = \relax \let\deftp = \relax \let\deftypefn = \relax \let\deftypefun = \relax \let\deftypeivar = \relax \let\deftypevar = \relax \let\deftypevr = \relax \let\defun = \relax \let\defvar = \relax \let\defvr = \relax \let\ref = \relax \let\xref = \relax \let\printindex = \relax \let\pxref = \relax \let\settitle = \relax \let\setchapternewpage = \relax \let\setchapterstyle = \relax \let\everyheading = \relax \let\evenheading = \relax \let\oddheading = \relax \let\everyfooting = \relax \let\evenfooting = \relax \let\oddfooting = \relax \let\headings = \relax \let\include = \relax \let\lowersections = \relax \let\down = \relax \let\raisesections = \relax \let\up = \relax \let\set = \relax \let\clear = \relax \let\item = \relax } % Ignore @ignore ... @end ignore. % \def\ignore{\doignore{ignore}} % Ignore @ifinfo, @ifhtml, @ifnottex, @html, @menu, and @direntry text. % \def\ifinfo{\doignore{ifinfo}} \def\ifhtml{\doignore{ifhtml}} \def\ifnottex{\doignore{ifnottex}} \def\html{\doignore{html}} \def\menu{\doignore{menu}} \def\direntry{\doignore{direntry}} % @dircategory CATEGORY -- specify a category of the dir file % which this file should belong to. Ignore this in TeX. \let\dircategory = \comment % Ignore text until a line `@end #1'. % \def\doignore#1{\begingroup % Don't complain about control sequences we have declared \outer. \ignoresections % % Define a command to swallow text until we reach `@end #1'. % This @ is a catcode 12 token (that is the normal catcode of @ in % this texinfo.tex file). We change the catcode of @ below to match. \long\def\doignoretext##1@end #1{\enddoignore}% % % Make sure that spaces turn into tokens that match what \doignoretext wants. \catcode32 = 10 % % Ignore braces, too, so mismatched braces don't cause trouble. \catcode`\{ = 9 \catcode`\} = 9 % % We must not have @c interpreted as a control sequence. \catcode`\@ = 12 % % Make the letter c a comment character so that the rest of the line % will be ignored. This way, the document can have (for example) % @c @end ifinfo % and the @end ifinfo will be properly ignored. % (We've just changed @ to catcode 12.) \catcode`\c = 14 % % And now expand that command. \doignoretext } % What we do to finish off ignored text. % \def\enddoignore{\endgroup\ignorespaces}% \newif\ifwarnedobs\warnedobsfalse \def\obstexwarn{% \ifwarnedobs\relax\else % We need to warn folks that they may have trouble with TeX 3.0. % This uses \immediate\write16 rather than \message to get newlines. \immediate\write16{} \immediate\write16{WARNING: for users of Unix TeX 3.0!} \immediate\write16{This manual trips a bug in TeX version 3.0 (tex hangs).} \immediate\write16{If you are running another version of TeX, relax.} \immediate\write16{If you are running Unix TeX 3.0, kill this TeX process.} \immediate\write16{ Then upgrade your TeX installation if you can.} \immediate\write16{ (See ftp://ftp.gnu.org/pub/gnu/TeX.README.)} \immediate\write16{If you are stuck with version 3.0, run the} \immediate\write16{ script ``tex3patch'' from the Texinfo distribution} \immediate\write16{ to use a workaround.} \immediate\write16{} \global\warnedobstrue \fi } % **In TeX 3.0, setting text in \nullfont hangs tex. For a % workaround (which requires the file ``dummy.tfm'' to be installed), % uncomment the following line: %%%%%\font\nullfont=dummy\let\obstexwarn=\relax % Ignore text, except that we keep track of conditional commands for % purposes of nesting, up to an `@end #1' command. % \def\nestedignore#1{% \obstexwarn % We must actually expand the ignored text to look for the @end % command, so that nested ignore constructs work. Thus, we put the % text into a \vbox and then do nothing with the result. To minimize % the change of memory overflow, we follow the approach outlined on % page 401 of the TeXbook: make the current font be a dummy font. % \setbox0 = \vbox\bgroup % Don't complain about control sequences we have declared \outer. \ignoresections % % Define `@end #1' to end the box, which will in turn undefine the % @end command again. \expandafter\def\csname E#1\endcsname{\egroup\ignorespaces}% % % We are going to be parsing Texinfo commands. Most cause no % trouble when they are used incorrectly, but some commands do % complicated argument parsing or otherwise get confused, so we % undefine them. % % We can't do anything about stray @-signs, unfortunately; % they'll produce `undefined control sequence' errors. \ignoremorecommands % % Set the current font to be \nullfont, a TeX primitive, and define % all the font commands to also use \nullfont. We don't use % dummy.tfm, as suggested in the TeXbook, because not all sites % might have that installed. Therefore, math mode will still % produce output, but that should be an extremely small amount of % stuff compared to the main input. % \nullfont \let\tenrm = \nullfont \let\tenit = \nullfont \let\tensl = \nullfont \let\tenbf = \nullfont \let\tentt = \nullfont \let\smallcaps = \nullfont \let\tensf = \nullfont % Similarly for index fonts (mostly for their use in % smallexample) \let\indrm = \nullfont \let\indit = \nullfont \let\indsl = \nullfont \let\indbf = \nullfont \let\indtt = \nullfont \let\indsc = \nullfont \let\indsf = \nullfont % % Don't complain when characters are missing from the fonts. \tracinglostchars = 0 % % Don't bother to do space factor calculations. \frenchspacing % % Don't report underfull hboxes. \hbadness = 10000 % % Do minimal line-breaking. \pretolerance = 10000 % % Do not execute instructions in @tex \def\tex{\doignore{tex}}% % Do not execute macro definitions. % `c' is a comment character, so the word `macro' will get cut off. \def\macro{\doignore{ma}}% } % @set VAR sets the variable VAR to an empty value. % @set VAR REST-OF-LINE sets VAR to the value REST-OF-LINE. % % Since we want to separate VAR from REST-OF-LINE (which might be % empty), we can't just use \parsearg; we have to insert a space of our % own to delimit the rest of the line, and then take it out again if we % didn't need it. Make sure the catcode of space is correct to avoid % losing inside @example, for instance. % \def\set{\begingroup\catcode` =10 \catcode`\-=12 \catcode`\_=12 % Allow - and _ in VAR. \parsearg\setxxx} \def\setxxx#1{\setyyy#1 \endsetyyy} \def\setyyy#1 #2\endsetyyy{% \def\temp{#2}% \ifx\temp\empty \global\expandafter\let\csname SET#1\endcsname = \empty \else \setzzz{#1}#2\endsetzzz % Remove the trailing space \setxxx inserted. \fi \endgroup } % Can't use \xdef to pre-expand #2 and save some time, since \temp or % \next or other control sequences that we've defined might get us into % an infinite loop. Consider `@set foo @cite{bar}'. \def\setzzz#1#2 \endsetzzz{\expandafter\gdef\csname SET#1\endcsname{#2}} % @clear VAR clears (i.e., unsets) the variable VAR. % \def\clear{\parsearg\clearxxx} \def\clearxxx#1{\global\expandafter\let\csname SET#1\endcsname=\relax} % @value{foo} gets the text saved in variable foo. { \catcode`\_ = \active % % We might end up with active _ or - characters in the argument if % we're called from @code, as @code{@value{foo-bar_}}. So \let any % such active characters to their normal equivalents. \gdef\value{\begingroup \catcode`\-=12 \catcode`\_=12 \indexbreaks \let_\normalunderscore \valuexxx} } \def\valuexxx#1{\expandablevalue{#1}\endgroup} % We have this subroutine so that we can handle at least some @value's % properly in indexes (we \let\value to this in \indexdummies). Ones % whose names contain - or _ still won't work, but we can't do anything % about that. The command has to be fully expandable, since the result % winds up in the index file. This means that if the variable's value % contains other Texinfo commands, it's almost certain it will fail % (although perhaps we could fix that with sufficient work to do a % one-level expansion on the result, instead of complete). % \def\expandablevalue#1{% \expandafter\ifx\csname SET#1\endcsname\relax {[No value for ``#1'']}% \else \csname SET#1\endcsname \fi } % @ifset VAR ... @end ifset reads the `...' iff VAR has been defined % with @set. % \def\ifset{\parsearg\ifsetxxx} \def\ifsetxxx #1{% \expandafter\ifx\csname SET#1\endcsname\relax \expandafter\ifsetfail \else \expandafter\ifsetsucceed \fi } \def\ifsetsucceed{\conditionalsucceed{ifset}} \def\ifsetfail{\nestedignore{ifset}} \defineunmatchedend{ifset} % @ifclear VAR ... @end ifclear reads the `...' iff VAR has never been % defined with @set, or has been undefined with @clear. % \def\ifclear{\parsearg\ifclearxxx} \def\ifclearxxx #1{% \expandafter\ifx\csname SET#1\endcsname\relax \expandafter\ifclearsucceed \else \expandafter\ifclearfail \fi } \def\ifclearsucceed{\conditionalsucceed{ifclear}} \def\ifclearfail{\nestedignore{ifclear}} \defineunmatchedend{ifclear} % @iftex, @ifnothtml, @ifnotinfo always succeed; we read the text % following, through the first @end iftex (etc.). Make `@end iftex' % (etc.) valid only after an @iftex. % \def\iftex{\conditionalsucceed{iftex}} \def\ifnothtml{\conditionalsucceed{ifnothtml}} \def\ifnotinfo{\conditionalsucceed{ifnotinfo}} \defineunmatchedend{iftex} \defineunmatchedend{ifnothtml} \defineunmatchedend{ifnotinfo} % We can't just want to start a group at @iftex (for example) and end it % at @end iftex, since then @set commands inside the conditional have no % effect (they'd get reverted at the end of the group). So we must % define \Eiftex to redefine itself to be its previous value. (We can't % just define it to fail again with an ``unmatched end'' error, since % the @ifset might be nested.) % \def\conditionalsucceed#1{% \edef\temp{% % Remember the current value of \E#1. \let\nece{prevE#1} = \nece{E#1}% % % At the `@end #1', redefine \E#1 to be its previous value. \def\nece{E#1}{\let\nece{E#1} = \nece{prevE#1}}% }% \temp } % We need to expand lots of \csname's, but we don't want to expand the % control sequences after we've constructed them. % \def\nece#1{\expandafter\noexpand\csname#1\endcsname} % @defininfoenclose. \let\definfoenclose=\comment \message{indexing,} % Index generation facilities % Define \newwrite to be identical to plain tex's \newwrite % except not \outer, so it can be used within \newindex. {\catcode`\@=11 \gdef\newwrite{\alloc@7\write\chardef\sixt@@n}} % \newindex {foo} defines an index named foo. % It automatically defines \fooindex such that % \fooindex ...rest of line... puts an entry in the index foo. % It also defines \fooindfile to be the number of the output channel for % the file that accumulates this index. The file's extension is foo. % The name of an index should be no more than 2 characters long % for the sake of vms. % \def\newindex#1{% \iflinks \expandafter\newwrite \csname#1indfile\endcsname \openout \csname#1indfile\endcsname \jobname.#1 % Open the file \fi \expandafter\xdef\csname#1index\endcsname{% % Define @#1index \noexpand\doindex{#1}} } % @defindex foo == \newindex{foo} \def\defindex{\parsearg\newindex} % Define @defcodeindex, like @defindex except put all entries in @code. \def\newcodeindex#1{% \iflinks \expandafter\newwrite \csname#1indfile\endcsname \openout \csname#1indfile\endcsname \jobname.#1 \fi \expandafter\xdef\csname#1index\endcsname{% \noexpand\docodeindex{#1}} } \def\defcodeindex{\parsearg\newcodeindex} % @synindex foo bar makes index foo feed into index bar. % Do this instead of @defindex foo if you don't want it as a separate index. % The \closeout helps reduce unnecessary open files; the limit on the % Acorn RISC OS is a mere 16 files. \def\synindex#1 #2 {% \expandafter\let\expandafter\synindexfoo\expandafter=\csname#2indfile\endcsname \expandafter\closeout\csname#1indfile\endcsname \expandafter\let\csname#1indfile\endcsname=\synindexfoo \expandafter\xdef\csname#1index\endcsname{% define \xxxindex \noexpand\doindex{#2}}% } % @syncodeindex foo bar similar, but put all entries made for index foo % inside @code. \def\syncodeindex#1 #2 {% \expandafter\let\expandafter\synindexfoo\expandafter=\csname#2indfile\endcsname \expandafter\closeout\csname#1indfile\endcsname \expandafter\let\csname#1indfile\endcsname=\synindexfoo \expandafter\xdef\csname#1index\endcsname{% define \xxxindex \noexpand\docodeindex{#2}}% } % Define \doindex, the driver for all \fooindex macros. % Argument #1 is generated by the calling \fooindex macro, % and it is "foo", the name of the index. % \doindex just uses \parsearg; it calls \doind for the actual work. % This is because \doind is more useful to call from other macros. % There is also \dosubind {index}{topic}{subtopic} % which makes an entry in a two-level index such as the operation index. \def\doindex#1{\edef\indexname{#1}\parsearg\singleindexer} \def\singleindexer #1{\doind{\indexname}{#1}} % like the previous two, but they put @code around the argument. \def\docodeindex#1{\edef\indexname{#1}\parsearg\singlecodeindexer} \def\singlecodeindexer #1{\doind{\indexname}{\code{#1}}} \def\indexdummies{% \def\ { }% % Take care of the plain tex accent commands. \def\"{\realbackslash "}% \def\`{\realbackslash `}% \def\'{\realbackslash '}% \def\^{\realbackslash ^}% \def\~{\realbackslash ~}% \def\={\realbackslash =}% \def\b{\realbackslash b}% \def\c{\realbackslash c}% \def\d{\realbackslash d}% \def\u{\realbackslash u}% \def\v{\realbackslash v}% \def\H{\realbackslash H}% % Take care of the plain tex special European modified letters. \def\oe{\realbackslash oe}% \def\ae{\realbackslash ae}% \def\aa{\realbackslash aa}% \def\OE{\realbackslash OE}% \def\AE{\realbackslash AE}% \def\AA{\realbackslash AA}% \def\o{\realbackslash o}% \def\O{\realbackslash O}% \def\l{\realbackslash l}% \def\L{\realbackslash L}% \def\ss{\realbackslash ss}% % Take care of texinfo commands likely to appear in an index entry. % (Must be a way to avoid doing expansion at all, and thus not have to % laboriously list every single command here.) \def\@{@}% will be @@ when we switch to @ as escape char. % Need these in case \tex is in effect and \{ is a \delimiter again. % But can't use \lbracecmd and \rbracecmd because texindex assumes % braces and backslashes are used only as delimiters. \let\{ = \mylbrace \let\} = \myrbrace \def\_{{\realbackslash _}}% \def\w{\realbackslash w }% \def\bf{\realbackslash bf }% %\def\rm{\realbackslash rm }% \def\sl{\realbackslash sl }% \def\sf{\realbackslash sf}% \def\tt{\realbackslash tt}% \def\gtr{\realbackslash gtr}% \def\less{\realbackslash less}% \def\hat{\realbackslash hat}% \def\TeX{\realbackslash TeX}% \def\dots{\realbackslash dots }% \def\result{\realbackslash result}% \def\equiv{\realbackslash equiv}% \def\expansion{\realbackslash expansion}% \def\print{\realbackslash print}% \def\error{\realbackslash error}% \def\point{\realbackslash point}% \def\copyright{\realbackslash copyright}% \def\tclose##1{\realbackslash tclose {##1}}% \def\code##1{\realbackslash code {##1}}% \def\uref##1{\realbackslash uref {##1}}% \def\url##1{\realbackslash url {##1}}% \def\env##1{\realbackslash env {##1}}% \def\command##1{\realbackslash command {##1}}% \def\option##1{\realbackslash option {##1}}% \def\dotless##1{\realbackslash dotless {##1}}% \def\samp##1{\realbackslash samp {##1}}% \def\,##1{\realbackslash ,{##1}}% \def\t##1{\realbackslash t {##1}}% \def\r##1{\realbackslash r {##1}}% \def\i##1{\realbackslash i {##1}}% \def\b##1{\realbackslash b {##1}}% \def\sc##1{\realbackslash sc {##1}}% \def\cite##1{\realbackslash cite {##1}}% \def\key##1{\realbackslash key {##1}}% \def\file##1{\realbackslash file {##1}}% \def\var##1{\realbackslash var {##1}}% \def\kbd##1{\realbackslash kbd {##1}}% \def\dfn##1{\realbackslash dfn {##1}}% \def\emph##1{\realbackslash emph {##1}}% \def\acronym##1{\realbackslash acronym {##1}}% % % Handle some cases of @value -- where the variable name does not % contain - or _, and the value does not contain any % (non-fully-expandable) commands. \let\value = \expandablevalue % \unsepspaces % Turn off macro expansion \turnoffmacros } % If an index command is used in an @example environment, any spaces % therein should become regular spaces in the raw index file, not the % expansion of \tie (\\leavevmode \penalty \@M \ ). {\obeyspaces \gdef\unsepspaces{\obeyspaces\let =\space}} % \indexnofonts no-ops all font-change commands. % This is used when outputting the strings to sort the index by. \def\indexdummyfont#1{#1} \def\indexdummytex{TeX} \def\indexdummydots{...} \def\indexnofonts{% % Just ignore accents. \let\,=\indexdummyfont \let\"=\indexdummyfont \let\`=\indexdummyfont \let\'=\indexdummyfont \let\^=\indexdummyfont \let\~=\indexdummyfont \let\==\indexdummyfont \let\b=\indexdummyfont \let\c=\indexdummyfont \let\d=\indexdummyfont \let\u=\indexdummyfont \let\v=\indexdummyfont \let\H=\indexdummyfont \let\dotless=\indexdummyfont % Take care of the plain tex special European modified letters. \def\oe{oe}% \def\ae{ae}% \def\aa{aa}% \def\OE{OE}% \def\AE{AE}% \def\AA{AA}% \def\o{o}% \def\O{O}% \def\l{l}% \def\L{L}% \def\ss{ss}% \let\w=\indexdummyfont \let\t=\indexdummyfont \let\r=\indexdummyfont \let\i=\indexdummyfont \let\b=\indexdummyfont \let\emph=\indexdummyfont \let\strong=\indexdummyfont \let\cite=\indexdummyfont \let\sc=\indexdummyfont %Don't no-op \tt, since it isn't a user-level command % and is used in the definitions of the active chars like <, >, |... %\let\tt=\indexdummyfont \let\tclose=\indexdummyfont \let\code=\indexdummyfont \let\url=\indexdummyfont \let\uref=\indexdummyfont \let\env=\indexdummyfont \let\command=\indexdummyfont \let\option=\indexdummyfont \let\file=\indexdummyfont \let\samp=\indexdummyfont \let\kbd=\indexdummyfont \let\key=\indexdummyfont \let\var=\indexdummyfont \let\TeX=\indexdummytex \let\dots=\indexdummydots \def\@{@}% } % To define \realbackslash, we must make \ not be an escape. % We must first make another character (@) an escape % so we do not become unable to do a definition. {\catcode`\@=0 \catcode`\\=\other @gdef@realbackslash{\}} \let\indexbackslash=0 %overridden during \printindex. \let\SETmarginindex=\relax % put index entries in margin (undocumented)? % For \ifx comparisons. \def\emptymacro{\empty} % Most index entries go through here, but \dosubind is the general case. % \def\doind#1#2{\dosubind{#1}{#2}\empty} % Workhorse for all \fooindexes. % #1 is name of index, #2 is stuff to put there, #3 is subentry -- % \empty if called from \doind, as we usually are. The main exception % is with defuns, which call us directly. % \def\dosubind#1#2#3{% % Put the index entry in the margin if desired. \ifx\SETmarginindex\relax\else \insert\margin{\hbox{\vrule height6pt depth3pt width0pt #2}}% \fi {% \count255=\lastpenalty {% \indexdummies % Must do this here, since \bf, etc expand at this stage \escapechar=`\\ {% \let\folio = 0% We will expand all macros now EXCEPT \folio. \def\rawbackslashxx{\indexbackslash}% \indexbackslash isn't defined now % so it will be output as is; and it will print as backslash. % \def\thirdarg{#3}% % % If third arg is present, precede it with space in sort key. \ifx\thirdarg\emptymacro \let\subentry = \empty \else \def\subentry{ #3}% \fi % % First process the index entry with all font commands turned % off to get the string to sort by. {\indexnofonts \xdef\indexsorttmp{#2\subentry}}% % % Now the real index entry with the fonts. \toks0 = {#2}% % % If third (subentry) arg is present, add it to the index % string. And include a space. \ifx\thirdarg\emptymacro \else \toks0 = \expandafter{\the\toks0 \space #3}% \fi % % Set up the complete index entry, with both the sort key % and the original text, including any font commands. We write % three arguments to \entry to the .?? file, texindex reduces to % two when writing the .??s sorted result. \edef\temp{% \write\csname#1indfile\endcsname{% \realbackslash entry{\indexsorttmp}{\folio}{\the\toks0}}% }% % % If a skip is the last thing on the list now, preserve it % by backing up by \lastskip, doing the \write, then inserting % the skip again. Otherwise, the whatsit generated by the % \write will make \lastskip zero. The result is that sequences % like this: % @end defun % @tindex whatever % @defun ... % will have extra space inserted, because the \medbreak in the % start of the @defun won't see the skip inserted by the @end of % the previous defun. % % But don't do any of this if we're not in vertical mode. We % don't want to do a \vskip and prematurely end a paragraph. % % Avoid page breaks due to these extra skips, too. % \iflinks \ifvmode \skip0 = \lastskip \ifdim\lastskip = 0pt \else \nobreak\vskip-\lastskip \fi \fi % \temp % do the write % % \ifvmode \ifdim\skip0 = 0pt \else \nobreak\vskip\skip0 \fi \fi \fi }% }% \penalty\count255 }% } % The index entry written in the file actually looks like % \entry {sortstring}{page}{topic} % or % \entry {sortstring}{page}{topic}{subtopic} % The texindex program reads in these files and writes files % containing these kinds of lines: % \initial {c} % before the first topic whose initial is c % \entry {topic}{pagelist} % for a topic that is used without subtopics % \primary {topic} % for the beginning of a topic that is used with subtopics % \secondary {subtopic}{pagelist} % for each subtopic. % Define the user-accessible indexing commands % @findex, @vindex, @kindex, @cindex. \def\findex {\fnindex} \def\kindex {\kyindex} \def\cindex {\cpindex} \def\vindex {\vrindex} \def\tindex {\tpindex} \def\pindex {\pgindex} \def\cindexsub {\begingroup\obeylines\cindexsub} {\obeylines % \gdef\cindexsub "#1" #2^^M{\endgroup % \dosubind{cp}{#2}{#1}}} % Define the macros used in formatting output of the sorted index material. % @printindex causes a particular index (the ??s file) to get printed. % It does not print any chapter heading (usually an @unnumbered). % \def\printindex{\parsearg\doprintindex} \def\doprintindex#1{\begingroup \dobreak \chapheadingskip{10000}% % \indexfonts \rm \tolerance = 9500 \indexbreaks % % See if the index file exists and is nonempty. % Change catcode of @ here so that if the index file contains % \initial {@} % as its first line, TeX doesn't complain about mismatched braces % (because it thinks @} is a control sequence). \catcode`\@ = 11 \openin 1 \jobname.#1s \ifeof 1 % \enddoublecolumns gets confused if there is no text in the index, % and it loses the chapter title and the aux file entries for the % index. The easiest way to prevent this problem is to make sure % there is some text. \putwordIndexNonexistent \else % % If the index file exists but is empty, then \openin leaves \ifeof % false. We have to make TeX try to read something from the file, so % it can discover if there is anything in it. \read 1 to \temp \ifeof 1 \putwordIndexIsEmpty \else % Index files are almost Texinfo source, but we use \ as the escape % character. It would be better to use @, but that's too big a change % to make right now. \def\indexbackslash{\rawbackslashxx}% \catcode`\\ = 0 \escapechar = `\\ \begindoublecolumns \input \jobname.#1s \enddoublecolumns \fi \fi \closein 1 \endgroup} % These macros are used by the sorted index file itself. % Change them to control the appearance of the index. \def\initial#1{{% % Some minor font changes for the special characters. \ifjaTeX \let\tentt=\sectt \let\tt=\sectt \let\sf=\gt\sectt \else \let\tentt=\sectt \let\tt=\sectt \let\sf=\sectt \fi % % Remove any glue we may have, we'll be inserting our own. \removelastskip % % We like breaks before the index initials, so insert a bonus. \penalty -300 % % Typeset the initial. Making this add up to a whole number of % baselineskips increases the chance of the dots lining up from column % to column. It still won't often be perfect, because of the stretch % we need before each entry, but it's better. % % No shrink because it confuses \balancecolumns. \vskip 1.67\baselineskip plus .5\baselineskip \leftline{\secbf #1}% \vskip .33\baselineskip plus .1\baselineskip % % Do our best not to break after the initial. \nobreak }} % This typesets a paragraph consisting of #1, dot leaders, and then #2 % flush to the right margin. It is used for index and table of contents % entries. The paragraph is indented by \leftskip. % \def\entry#1#2{\begingroup % % Start a new paragraph if necessary, so our assignments below can't % affect previous text. \par % % Do not fill out the last line with white space. \parfillskip = 0in % % No extra space above this paragraph. \parskip = 0in % % Do not prefer a separate line ending with a hyphen to fewer lines. \finalhyphendemerits = 0 % % \hangindent is only relevant when the entry text and page number % don't both fit on one line. In that case, bob suggests starting the % dots pretty far over on the line. Unfortunately, a large % indentation looks wrong when the entry text itself is broken across % lines. So we use a small indentation and put up with long leaders. % % \hangafter is reset to 1 (which is the value we want) at the start % of each paragraph, so we need not do anything with that. \hangindent = 2em % % When the entry text needs to be broken, just fill out the first line % with blank space. \rightskip = 0pt plus1fil % % A bit of stretch before each entry for the benefit of balancing columns. \vskip 0pt plus1pt % % Start a ``paragraph'' for the index entry so the line breaking % parameters we've set above will have an effect. \noindent % % Insert the text of the index entry. TeX will do line-breaking on it. #1% % The following is kludged to not output a line of dots in the index if % there are no page numbers. The next person who breaks this will be % cursed by a Unix daemon. \def\tempa{{\rm }}% \def\tempb{#2}% \edef\tempc{\tempa}% \edef\tempd{\tempb}% \ifx\tempc\tempd\ \else% % % If we must, put the page number on a line of its own, and fill out % this line with blank space. (The \hfil is overwhelmed with the % fill leaders glue in \indexdotfill if the page number does fit.) \hfil\penalty50 \null\nobreak\indexdotfill % Have leaders before the page number. % % The `\ ' here is removed by the implicit \unskip that TeX does as % part of (the primitive) \par. Without it, a spurious underfull % \hbox ensues. \ #2% The page number ends the paragraph. \fi% \par \endgroup} % Like \dotfill except takes at least 1 em. \def\indexdotfill{\cleaders \hbox{$\mathsurround=0pt \mkern1.5mu ${\it .}$ \mkern1.5mu$}\hskip 1em plus 1fill} \def\primary #1{\line{#1\hfil}} \newskip\secondaryindent \secondaryindent=0.5cm \def\secondary #1#2{ {\parfillskip=0in \parskip=0in \hangindent =1in \hangafter=1 \noindent\hskip\secondaryindent\hbox{#1}\indexdotfill #2\par }} % Define two-column mode, which we use to typeset indexes. % Adapted from the TeXbook, page 416, which is to say, % the manmac.tex format used to print the TeXbook itself. \catcode`\@=11 \newbox\partialpage \newdimen\doublecolumnhsize \def\begindoublecolumns{\begingroup % ended by \enddoublecolumns % Grab any single-column material above us. \output = {% % % Here is a possibility not foreseen in manmac: if we accumulate a % whole lot of material, we might end up calling this \output % routine twice in a row (see the doublecol-lose test, which is % essentially a couple of indexes with @setchapternewpage off). In % that case we just ship out what is in \partialpage with the normal % output routine. Generally, \partialpage will be empty when this % runs and this will be a no-op. See the indexspread.tex test case. \ifvoid\partialpage \else \onepageout{\pagecontents\partialpage}% \fi % \global\setbox\partialpage = \vbox{% % Unvbox the main output page. \unvbox\PAGE \kern-\topskip \kern\baselineskip }% }% \eject % run that output routine to set \partialpage % % Use the double-column output routine for subsequent pages. \output = {\doublecolumnout}% % % Change the page size parameters. We could do this once outside this % routine, in each of @smallbook, @afourpaper, and the default 8.5x11 % format, but then we repeat the same computation. Repeating a couple % of assignments once per index is clearly meaningless for the % execution time, so we may as well do it in one place. % % First we halve the line length, less a little for the gutter between % the columns. We compute the gutter based on the line length, so it % changes automatically with the paper format. The magic constant % below is chosen so that the gutter has the same value (well, +-<1pt) % as it did when we hard-coded it. % % We put the result in a separate register, \doublecolumhsize, so we % can restore it in \pagesofar, after \hsize itself has (potentially) % been clobbered. % \doublecolumnhsize = \hsize \advance\doublecolumnhsize by -.04154\hsize \divide\doublecolumnhsize by 2 \hsize = \doublecolumnhsize % % Double the \vsize as well. (We don't need a separate register here, % since nobody clobbers \vsize.) \advance\vsize by -\ht\partialpage \vsize = 2\vsize } % The double-column output routine for all double-column pages except % the last. % \def\doublecolumnout{% \splittopskip=\topskip \splitmaxdepth=\maxdepth % Get the available space for the double columns -- the normal % (undoubled) page height minus any material left over from the % previous page. \dimen@ = \vsize \divide\dimen@ by 2 % % box0 will be the left-hand column, box2 the right. \setbox0=\vsplit255 to\dimen@ \setbox2=\vsplit255 to\dimen@ \onepageout\pagesofar \unvbox255 \penalty\outputpenalty } \def\pagesofar{% % Re-output the contents of the output page -- any previous material, % followed by the two boxes we just split, in box0 and box2. \unvbox\partialpage % \hsize = \doublecolumnhsize \wd0=\hsize \wd2=\hsize \hbox to\pagewidth{\box0\hfil\box2}% } \def\enddoublecolumns{% \output = {% % Split the last of the double-column material. Leave it on the % current page, no automatic page break. \balancecolumns % % If we end up splitting too much material for the current page, % though, there will be another page break right after this \output % invocation ends. Having called \balancecolumns once, we do not % want to call it again. Therefore, reset \output to its normal % definition right away. (We hope \balancecolumns will never be % called on to balance too much material, but if it is, this makes % the output somewhat more palatable.) \global\output = {\onepageout{\pagecontents\PAGE}}% }% \eject \endgroup % started in \begindoublecolumns % % \pagegoal was set to the doubled \vsize above, since we restarted % the current page. We're now back to normal single-column % typesetting, so reset \pagegoal to the normal \vsize (after the % \endgroup where \vsize got restored). \pagegoal = \vsize } \def\balancecolumns{% % Called at the end of the double column material. \setbox0 = \vbox{\unvbox255}% like \box255 but more efficient, see p.120. \dimen@ = \ht0 \advance\dimen@ by \topskip \advance\dimen@ by-\baselineskip \divide\dimen@ by 2 % target to split to %debug\message{final 2-column material height=\the\ht0, target=\the\dimen@.}% \splittopskip = \topskip % Loop until we get a decent breakpoint. {% \vbadness = 10000 \loop \global\setbox3 = \copy0 \global\setbox1 = \vsplit3 to \dimen@ \ifdim\ht3>\dimen@ \global\advance\dimen@ by 1pt \repeat }% %debug\message{split to \the\dimen@, column heights: \the\ht1, \the\ht3.}% \setbox0=\vbox to\dimen@{\unvbox1}% \setbox2=\vbox to\dimen@{\unvbox3}% % \pagesofar } \catcode`\@ = \other \message{sectioning,} % Chapters, sections, etc. \newcount\chapno \newcount\secno \secno=0 \newcount\subsecno \subsecno=0 \newcount\subsubsecno \subsubsecno=0 % This counter is funny since it counts through charcodes of letters A, B, ... % The \the is necessary, despite appearances, because \appendixletter is % expanded while writing the .toc file. \char\appendixno is not % expandable, thus it is written literally, thus all appendixes come out % with the same letter (or @) in the toc without it. \newcount\appendixno \appendixno = `\@ \def\appendixletter{\char\the\appendixno} % Each @chapter defines this as the name of the chapter. % page headings and footings can use it. @section does likewise. \def\thischapter{} \def\thissection{} \newcount\absseclevel % used to calculate proper heading level \newcount\secbase\secbase=0 % @raise/lowersections modify this count % @raisesections: treat @section as chapter, @subsection as section, etc. \def\raisesections{\global\advance\secbase by -1} \let\up=\raisesections % original BFox name % @lowersections: treat @chapter as section, @section as subsection, etc. \def\lowersections{\global\advance\secbase by 1} \let\down=\lowersections % original BFox name % Choose a numbered-heading macro % #1 is heading level if unmodified by @raisesections or @lowersections % #2 is text for heading \def\numhead#1#2{\absseclevel=\secbase\advance\absseclevel by #1 \ifcase\absseclevel \chapterzzz{#2} \or \seczzz{#2} \or \numberedsubseczzz{#2} \or \numberedsubsubseczzz{#2} \else \ifnum \absseclevel<0 \chapterzzz{#2} \else \numberedsubsubseczzz{#2} \fi \fi } % like \numhead, but chooses appendix heading levels \def\apphead#1#2{\absseclevel=\secbase\advance\absseclevel by #1 \ifcase\absseclevel \appendixzzz{#2} \or \appendixsectionzzz{#2} \or \appendixsubseczzz{#2} \or \appendixsubsubseczzz{#2} \else \ifnum \absseclevel<0 \appendixzzz{#2} \else \appendixsubsubseczzz{#2} \fi \fi } % like \numhead, but chooses numberless heading levels \def\unnmhead#1#2{\absseclevel=\secbase\advance\absseclevel by #1 \ifcase\absseclevel \unnumberedzzz{#2} \or \unnumberedseczzz{#2} \or \unnumberedsubseczzz{#2} \or \unnumberedsubsubseczzz{#2} \else \ifnum \absseclevel<0 \unnumberedzzz{#2} \else \unnumberedsubsubseczzz{#2} \fi \fi } % @chapter, @appendix, @unnumbered. \def\thischaptername{No Chapter Title} \outer\def\chapter{\parsearg\chapteryyy} \def\chapteryyy #1{\numhead0{#1}} % normally numhead0 calls chapterzzz \def\chapterzzz #1{% \secno=0 \subsecno=0 \subsubsecno=0 \global\advance \chapno by 1 \message{\the\chapno\space \putwordChapter}% \chapmacro {#1}{\the\chapno}% \gdef\thissection{#1}% \gdef\thischaptername{#1}% % We don't substitute the actual chapter name into \thischapter % because we don't want its macros evaluated now. \xdef\thischapter{\the\chapno \putwordChapter{}: \noexpand\thischaptername}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash chapentry{\the\toks0}% {\the\chapno}}}% \temp \donoderef \global\let\section = \numberedsec \global\let\subsection = \numberedsubsec \global\let\subsubsection = \numberedsubsubsec } \outer\def\appendix{\parsearg\appendixyyy} \def\appendixyyy #1{\apphead0{#1}} % normally apphead0 calls appendixzzz \def\appendixzzz #1{% \secno=0 \subsecno=0 \subsubsecno=0 \global\advance \appendixno by 1 \message{\putwordAppendix\space \appendixletter}% \chapmacro {#1}{\putwordAppendix{} \appendixletter}% \gdef\thissection{#1}% \gdef\thischaptername{#1}% \xdef\thischapter{\putwordAppendix{} \appendixletter: \noexpand\thischaptername}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash chapentry{\the\toks0}% {\putwordAppendix{} \appendixletter}}}% \temp \appendixnoderef \global\let\section = \appendixsec \global\let\subsection = \appendixsubsec \global\let\subsubsection = \appendixsubsubsec } % @centerchap is like @unnumbered, but the heading is centered. \outer\def\centerchap{\parsearg\centerchapyyy} \def\centerchapyyy #1{{\let\unnumbchapmacro=\centerchapmacro \unnumberedyyy{#1}}} % @top is like @unnumbered. \outer\def\top{\parsearg\unnumberedyyy} \outer\def\unnumbered{\parsearg\unnumberedyyy} \def\unnumberedyyy #1{\unnmhead0{#1}} % normally unnmhead0 calls unnumberedzzz \def\unnumberedzzz #1{% \secno=0 \subsecno=0 \subsubsecno=0 % % This used to be simply \message{#1}, but TeX fully expands the % argument to \message. Therefore, if #1 contained @-commands, TeX % expanded them. For example, in `@unnumbered The @cite{Book}', TeX % expanded @cite (which turns out to cause errors because \cite is meant % to be executed, not expanded). % % Anyway, we don't want the fully-expanded definition of @cite to appear % as a result of the \message, we just want `@cite' itself. We use % \the to achieve this: TeX expands \the only once, % simply yielding the contents of . (We also do this for % the toc entries.) \toks0 = {#1}\message{(\the\toks0)}% % \unnumbchapmacro {#1}% \gdef\thischapter{#1}\gdef\thissection{#1}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash unnumbchapentry{\the\toks0}}}% \temp \unnumbnoderef \global\let\section = \unnumberedsec \global\let\subsection = \unnumberedsubsec \global\let\subsubsection = \unnumberedsubsubsec } % Sections. \outer\def\numberedsec{\parsearg\secyyy} \def\secyyy #1{\numhead1{#1}} % normally calls seczzz \def\seczzz #1{% \subsecno=0 \subsubsecno=0 \global\advance \secno by 1 % \gdef\thissection{#1}\secheading {#1}{\the\chapno}{\the\secno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash secentry{\the\toks0}% {\the\chapno}{\the\secno}}}% \temp \donoderef \nobreak } \outer\def\appendixsection{\parsearg\appendixsecyyy} \outer\def\appendixsec{\parsearg\appendixsecyyy} \def\appendixsecyyy #1{\apphead1{#1}} % normally calls appendixsectionzzz \def\appendixsectionzzz #1{% \subsecno=0 \subsubsecno=0 \global\advance \secno by 1 % \gdef\thissection{#1}\secheading {#1}{\appendixletter}{\the\secno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash secentry{\the\toks0}% {\appendixletter}{\the\secno}}}% \temp \appendixnoderef \nobreak } \outer\def\unnumberedsec{\parsearg\unnumberedsecyyy} \def\unnumberedsecyyy #1{\unnmhead1{#1}} % normally calls unnumberedseczzz \def\unnumberedseczzz #1{% \plainsecheading {#1}\gdef\thissection{#1}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash unnumbsecentry{\the\toks0}}}% \temp \unnumbnoderef \nobreak } % Subsections. \outer\def\numberedsubsec{\parsearg\numberedsubsecyyy} \def\numberedsubsecyyy #1{\numhead2{#1}} % normally calls numberedsubseczzz \def\numberedsubseczzz #1{% \gdef\thissection{#1}\subsubsecno=0 \global\advance \subsecno by 1 % \subsecheading {#1}{\the\chapno}{\the\secno}{\the\subsecno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash subsecentry{\the\toks0}% {\the\chapno}{\the\secno}{\the\subsecno}}}% \temp \donoderef \nobreak } \outer\def\appendixsubsec{\parsearg\appendixsubsecyyy} \def\appendixsubsecyyy #1{\apphead2{#1}} % normally calls appendixsubseczzz \def\appendixsubseczzz #1{% \gdef\thissection{#1}\subsubsecno=0 \global\advance \subsecno by 1 % \subsecheading {#1}{\appendixletter}{\the\secno}{\the\subsecno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash subsecentry{\the\toks0}% {\appendixletter}{\the\secno}{\the\subsecno}}}% \temp \appendixnoderef \nobreak } \outer\def\unnumberedsubsec{\parsearg\unnumberedsubsecyyy} \def\unnumberedsubsecyyy #1{\unnmhead2{#1}} %normally calls unnumberedsubseczzz \def\unnumberedsubseczzz #1{% \plainsubsecheading {#1}\gdef\thissection{#1}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash unnumbsubsecentry% {\the\toks0}}}% \temp \unnumbnoderef \nobreak } % Subsubsections. \outer\def\numberedsubsubsec{\parsearg\numberedsubsubsecyyy} \def\numberedsubsubsecyyy #1{\numhead3{#1}} % normally numberedsubsubseczzz \def\numberedsubsubseczzz #1{% \gdef\thissection{#1}\global\advance \subsubsecno by 1 % \subsubsecheading {#1} {\the\chapno}{\the\secno}{\the\subsecno}{\the\subsubsecno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash subsubsecentry{\the\toks0}% {\the\chapno}{\the\secno}{\the\subsecno}{\the\subsubsecno}}}% \temp \donoderef \nobreak } \outer\def\appendixsubsubsec{\parsearg\appendixsubsubsecyyy} \def\appendixsubsubsecyyy #1{\apphead3{#1}} % normally appendixsubsubseczzz \def\appendixsubsubseczzz #1{% \gdef\thissection{#1}\global\advance \subsubsecno by 1 % \subsubsecheading {#1} {\appendixletter}{\the\secno}{\the\subsecno}{\the\subsubsecno}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash subsubsecentry{\the\toks0}% {\appendixletter}{\the\secno}{\the\subsecno}{\the\subsubsecno}}}% \temp \appendixnoderef \nobreak } \outer\def\unnumberedsubsubsec{\parsearg\unnumberedsubsubsecyyy} \def\unnumberedsubsubsecyyy #1{\unnmhead3{#1}} %normally unnumberedsubsubseczzz \def\unnumberedsubsubseczzz #1{% \plainsubsubsecheading {#1}\gdef\thissection{#1}% \toks0 = {#1}% \edef\temp{\noexpand\writetocentry{\realbackslash unnumbsubsubsecentry% {\the\toks0}}}% \temp \unnumbnoderef \nobreak } % These are variants which are not "outer", so they can appear in @ifinfo. % Actually, they should now be obsolete; ordinary section commands should work. \def\infotop{\parsearg\unnumberedzzz} \def\infounnumbered{\parsearg\unnumberedzzz} \def\infounnumberedsec{\parsearg\unnumberedseczzz} \def\infounnumberedsubsec{\parsearg\unnumberedsubseczzz} \def\infounnumberedsubsubsec{\parsearg\unnumberedsubsubseczzz} \def\infoappendix{\parsearg\appendixzzz} \def\infoappendixsec{\parsearg\appendixseczzz} \def\infoappendixsubsec{\parsearg\appendixsubseczzz} \def\infoappendixsubsubsec{\parsearg\appendixsubsubseczzz} \def\infochapter{\parsearg\chapterzzz} \def\infosection{\parsearg\sectionzzz} \def\infosubsection{\parsearg\subsectionzzz} \def\infosubsubsection{\parsearg\subsubsectionzzz} % These macros control what the section commands do, according % to what kind of chapter we are in (ordinary, appendix, or unnumbered). % Define them by default for a numbered chapter. \global\let\section = \numberedsec \global\let\subsection = \numberedsubsec \global\let\subsubsection = \numberedsubsubsec % Define @majorheading, @heading and @subheading % NOTE on use of \vbox for chapter headings, section headings, and such: % 1) We use \vbox rather than the earlier \line to permit % overlong headings to fold. % 2) \hyphenpenalty is set to 10000 because hyphenation in a % heading is obnoxious; this forbids it. % 3) Likewise, headings look best if no \parindent is used, and % if justification is not attempted. Hence \raggedright. \def\majorheading{\parsearg\majorheadingzzz} \def\majorheadingzzz #1{% {\advance\chapheadingskip by 8pt \chapbreak }% {\chapfonts \vbox{\hyphenpenalty=10000\tolerance=5000 \parindent=0pt\raggedright \rm #1\hfill}}\bigskip \par\penalty 200} \def\chapheading{\parsearg\chapheadingzzz} \def\chapheadingzzz #1{\chapbreak % {\chapfonts \vbox{\hyphenpenalty=10000\tolerance=5000 \parindent=0pt\raggedright \rm #1\hfill}}\bigskip \par\penalty 200} % @heading, @subheading, @subsubheading. \def\heading{\parsearg\plainsecheading} \def\subheading{\parsearg\plainsubsecheading} \def\subsubheading{\parsearg\plainsubsubsecheading} % These macros generate a chapter, section, etc. heading only % (including whitespace, linebreaking, etc. around it), % given all the information in convenient, parsed form. %%% Args are the skip and penalty (usually negative) \def\dobreak#1#2{\par\ifdim\lastskip<#1\removelastskip\penalty#2\vskip#1\fi} \def\setchapterstyle #1 {\csname CHAPF#1\endcsname} %%% Define plain chapter starts, and page on/off switching for it % Parameter controlling skip before chapter headings (if needed) \newskip\chapheadingskip \def\chapbreak{\dobreak \chapheadingskip {-4000}} \def\chappager{\par\vfill\supereject} \def\chapoddpage{\chappager \ifodd\pageno \else \hbox to 0pt{} \chappager\fi} \def\setchapternewpage #1 {\csname CHAPPAG#1\endcsname} \def\CHAPPAGoff{% \global\let\contentsalignmacro = \chappager \global\let\pchapsepmacro=\chapbreak \global\let\pagealignmacro=\chappager} \def\CHAPPAGon{% \global\let\contentsalignmacro = \chappager \global\let\pchapsepmacro=\chappager \global\let\pagealignmacro=\chappager \global\def\HEADINGSon{\HEADINGSsingle}} \def\CHAPPAGodd{ \global\let\contentsalignmacro = \chapoddpage \global\let\pchapsepmacro=\chapoddpage \global\let\pagealignmacro=\chapoddpage \global\def\HEADINGSon{\HEADINGSdouble}} \CHAPPAGon \def\CHAPFplain{ \global\let\chapmacro=\chfplain \global\let\unnumbchapmacro=\unnchfplain \global\let\centerchapmacro=\centerchfplain} % Plain chapter opening. % #1 is the text, #2 the chapter number or empty if unnumbered. \def\chfplain#1#2{% \pchapsepmacro {% \chapfonts \rm \def\chapnum{#2}% \setbox0 = \hbox{#2\ifx\chapnum\empty\else\enspace\fi}% \vbox{\hyphenpenalty=10000 \tolerance=5000 \parindent=0pt \raggedright \hangindent = \wd0 \centerparametersmaybe \unhbox0 #1\par}% }% \nobreak\bigskip % no page break after a chapter title \nobreak } % Plain opening for unnumbered. \def\unnchfplain#1{\chfplain{#1}{}} % @centerchap -- centered and unnumbered. \let\centerparametersmaybe = \relax \def\centerchfplain#1{{% \def\centerparametersmaybe{% \advance\rightskip by 3\rightskip \leftskip = \rightskip \parfillskip = 0pt }% \chfplain{#1}{}% }} \CHAPFplain % The default \def\unnchfopen #1{% \chapoddpage {\chapfonts \vbox{\hyphenpenalty=10000\tolerance=5000 \parindent=0pt\raggedright \rm #1\hfill}}\bigskip \par\nobreak } \def\chfopen #1#2{\chapoddpage {\chapfonts \vbox to 3in{\vfil \hbox to\hsize{\hfil #2} \hbox to\hsize{\hfil #1} \vfil}}% \par\penalty 5000 % } \def\centerchfopen #1{% \chapoddpage {\chapfonts \vbox{\hyphenpenalty=10000\tolerance=5000 \parindent=0pt \hfill {\rm #1}\hfill}}\bigskip \par\nobreak } \def\CHAPFopen{ \global\let\chapmacro=\chfopen \global\let\unnumbchapmacro=\unnchfopen \global\let\centerchapmacro=\centerchfopen} % Section titles. \newskip\secheadingskip \def\secheadingbreak{\dobreak \secheadingskip {-1000}} \def\secheading#1#2#3{\sectionheading{sec}{#2.#3}{#1}} \def\plainsecheading#1{\sectionheading{sec}{}{#1}} % Subsection titles. \newskip \subsecheadingskip \def\subsecheadingbreak{\dobreak \subsecheadingskip {-500}} \def\subsecheading#1#2#3#4{\sectionheading{subsec}{#2.#3.#4}{#1}} \def\plainsubsecheading#1{\sectionheading{subsec}{}{#1}} % Subsubsection titles. \let\subsubsecheadingskip = \subsecheadingskip \let\subsubsecheadingbreak = \subsecheadingbreak \def\subsubsecheading#1#2#3#4#5{\sectionheading{subsubsec}{#2.#3.#4.#5}{#1}} \def\plainsubsubsecheading#1{\sectionheading{subsubsec}{}{#1}} % Print any size section title. % % #1 is the section type (sec/subsec/subsubsec), #2 is the section % number (maybe empty), #3 the text. \def\sectionheading#1#2#3{% {% \expandafter\advance\csname #1headingskip\endcsname by \parskip \csname #1headingbreak\endcsname }% {% % Switch to the right set of fonts. \csname #1fonts\endcsname \rm % % Only insert the separating space if we have a section number. \def\secnum{#2}% \setbox0 = \hbox{#2\ifx\secnum\empty\else\enspace\fi}% % \vbox{\hyphenpenalty=10000 \tolerance=5000 \parindent=0pt \raggedright \hangindent = \wd0 % zero if no section number \unhbox0 #3}% }% \ifdim\parskip<8pt \nobreak\kern8pt\nobreak\kern-\parskip\fi \nobreak } \message{toc,} % Table of contents. \newwrite\tocfile % Write an entry to the toc file, opening it if necessary. % Called from @chapter, etc. We supply {\folio} at the end of the % argument, which will end up as the last argument to the \...entry macro. % % We open the .toc file here instead of at @setfilename or any other % given time so that @contents can be put in the document anywhere. % \newif\iftocfileopened \def\writetocentry#1{% \iftocfileopened\else \immediate\openout\tocfile = \jobname.toc \global\tocfileopenedtrue \fi \iflinks \write\tocfile{#1{\folio}}\fi } \newskip\contentsrightmargin \contentsrightmargin=1in \newcount\savepageno \newcount\lastnegativepageno \lastnegativepageno = -1 % Finish up the main text and prepare to read what we've written % to \tocfile. % \def\startcontents#1{% % If @setchapternewpage on, and @headings double, the contents should % start on an odd page, unlike chapters. Thus, we maintain % \contentsalignmacro in parallel with \pagealignmacro. % From: Torbjorn Granlund \contentsalignmacro \immediate\closeout\tocfile % % Don't need to put `Contents' or `Short Contents' in the headline. % It is abundantly clear what they are. \unnumbchapmacro{#1}\def\thischapter{}% \savepageno = \pageno \begingroup % Set up to handle contents files properly. \catcode`\\=0 \catcode`\{=1 \catcode`\}=2 \catcode`\@=11 % We can't do this, because then an actual ^ in a section % title fails, e.g., @chapter ^ -- exponentiation. --karl, 9jul97. %\catcode`\^=7 % to see ^^e4 as \"a etc. juha@piuha.ydi.vtt.fi \raggedbottom % Worry more about breakpoints than the bottom. \advance\hsize by -\contentsrightmargin % Don't use the full line length. % % Roman numerals for page numbers. \ifnum \pageno>0 \pageno = \lastnegativepageno \fi } % Normal (long) toc. \def\contents{% \startcontents{\putwordTOC}% \openin 1 \jobname.toc \ifeof 1 \else \closein 1 \input \jobname.toc \fi \vfill \eject \contentsalignmacro % in case @setchapternewpage odd is in effect \endgroup \lastnegativepageno = \pageno \pageno = \savepageno } % And just the chapters. \def\summarycontents{% \startcontents{\putwordShortTOC}% % \let\chapentry = \shortchapentry \let\unnumbchapentry = \shortunnumberedentry % We want a true roman here for the page numbers. \secfonts \let\rm=\shortcontrm \let\bf=\shortcontbf \let\sl=\shortcontsl \ifjaTeX \let\mc=\shortcontmc \let\gt=\shortcontgt \mc\rm \else \rm \fi \hyphenpenalty = 10000 \advance\baselineskip by 1pt % Open it up a little. \def\secentry ##1##2##3##4{} \def\unnumbsecentry ##1##2{} \def\subsecentry ##1##2##3##4##5{} \def\unnumbsubsecentry ##1##2{} \def\subsubsecentry ##1##2##3##4##5##6{} \def\unnumbsubsubsecentry ##1##2{} \openin 1 \jobname.toc \ifeof 1 \else \closein 1 \input \jobname.toc \fi \vfill \eject \contentsalignmacro % in case @setchapternewpage odd is in effect \endgroup \lastnegativepageno = \pageno \pageno = \savepageno } \let\shortcontents = \summarycontents \ifpdf \pdfcatalog{/PageMode /UseOutlines}% \fi % These macros generate individual entries in the table of contents. % The first argument is the chapter or section name. % The last argument is the page number. % The arguments in between are the chapter number, section number, ... % Chapter-level things, for both the long and short contents. \def\chapentry#1#2#3{\dochapentry{#2\labelspace#1}{#3}} % See comments in \dochapentry re vbox and related settings \def\shortchapentry#1#2#3{% \tocentry{\shortchaplabel{#2}\labelspace #1}{\doshortpageno{#3}}% } % Typeset the label for a chapter or appendix for the short contents. % The arg is, e.g. `Appendix A' for an appendix, or `3' for a chapter. % We could simplify the code here by writing out an \appendixentry % command in the toc file for appendices, instead of using \chapentry % for both, but it doesn't seem worth it. \ifjaTeX \setbox0 = \hbox{\shortcontmc\shortcontrm \putwordAppendix } \else \setbox0 = \hbox{\shortcontrm \putwordAppendix } \fi \newdimen\shortappendixwidth \shortappendixwidth = \wd0 \def\shortchaplabel#1{% % We typeset #1 in a box of constant width, regardless of the text of % #1, so the chapter titles will come out aligned. \setbox0 = \hbox{#1}% \dimen0 = \ifdim\wd0 > \shortappendixwidth \shortappendixwidth \else 0pt \fi % % This space should be plenty, since a single number is .5em, and the % widest letter (M) is 1em, at least in the Computer Modern fonts. % (This space doesn't include the extra space that gets added after % the label; that gets put in by \shortchapentry above.) \advance\dimen0 by 1.1em \hbox to \dimen0{#1\hfil}% } \def\unnumbchapentry#1#2{\dochapentry{#1}{#2}} \def\shortunnumberedentry#1#2{\tocentry{#1}{\doshortpageno{#2}}} % Sections. \def\secentry#1#2#3#4{\dosecentry{#2.#3\labelspace#1}{#4}} \def\unnumbsecentry#1#2{\dosecentry{#1}{#2}} % Subsections. \def\subsecentry#1#2#3#4#5{\dosubsecentry{#2.#3.#4\labelspace#1}{#5}} \def\unnumbsubsecentry#1#2{\dosubsecentry{#1}{#2}} % And subsubsections. \def\subsubsecentry#1#2#3#4#5#6{% \dosubsubsecentry{#2.#3.#4.#5\labelspace#1}{#6}} \def\unnumbsubsubsecentry#1#2{\dosubsubsecentry{#1}{#2}} % This parameter controls the indentation of the various levels. \newdimen\tocindent \tocindent = 3pc % Now for the actual typesetting. In all these, #1 is the text and #2 is the % page number. % % If the toc has to be broken over pages, we want it to be at chapters % if at all possible; hence the \penalty. \def\dochapentry#1#2{% \penalty-300 \vskip1\baselineskip plus.33\baselineskip minus.25\baselineskip \begingroup \chapentryfonts \tocentry{#1}{\dopageno{#2}}% \endgroup \nobreak\vskip .25\baselineskip plus.1\baselineskip } \def\dosecentry#1#2{\begingroup \secentryfonts \leftskip=\tocindent \tocentry{#1}{\dopageno{#2}}% \endgroup} \def\dosubsecentry#1#2{\begingroup \subsecentryfonts \leftskip=2\tocindent \tocentry{#1}{\dopageno{#2}}% \endgroup} \def\dosubsubsecentry#1#2{\begingroup \subsubsecentryfonts \leftskip=3\tocindent \tocentry{#1}{\dopageno{#2}}% \endgroup} % Final typesetting of a toc entry; we use the same \entry macro as for % the index entries, but we want to suppress hyphenation here. (We % can't do that in the \entry macro, since index entries might consist % of hyphenated-identifiers-that-do-not-fit-on-a-line-and-nothing-else.) \def\tocentry#1#2{\begingroup \vskip 0pt plus1pt % allow a little stretch for the sake of nice page breaks % Do not use \turnoffactive in these arguments. Since the toc is % typeset in cmr, so characters such as _ would come out wrong; we % have to do the usual translation tricks. \entry{#1}{#2}% \endgroup} % Space between chapter (or whatever) number and the title. \def\labelspace{\hskip1em \relax} \def\dopageno#1{{\rm #1}} \def\doshortpageno#1{{\rm #1}} \def\chapentryfonts{\secfonts \rm} \def\secentryfonts{\textfonts} \let\subsecentryfonts = \textfonts \let\subsubsecentryfonts = \textfonts \message{environments,} % @foo ... @end foo. % Since these characters are used in examples, it should be an even number of % \tt widths. Each \tt character is 1en, so two makes it 1em. % Furthermore, these definitions must come after we define our fonts. \newbox\dblarrowbox \newbox\longdblarrowbox \newbox\pushcharbox \newbox\bullbox \newbox\equivbox \newbox\errorbox %{\tentt %\global\setbox\dblarrowbox = \hbox to 1em{\hfil$\Rightarrow$\hfil} %\global\setbox\longdblarrowbox = \hbox to 1em{\hfil$\mapsto$\hfil} %\global\setbox\pushcharbox = \hbox to 1em{\hfil$\dashv$\hfil} %\global\setbox\equivbox = \hbox to 1em{\hfil$\ptexequiv$\hfil} % Adapted from the manmac format (p.420 of TeXbook) %\global\setbox\bullbox = \hbox to 1em{\kern.15em\vrule height .75ex width .85ex % depth .1ex\hfil} %} % @point{}, @result{}, @expansion{}, @print{}, @equiv{}. \def\point{$\star$} \def\result{\leavevmode\raise.15ex\hbox to 1em{\hfil$\Rightarrow$\hfil}} \def\expansion{\leavevmode\raise.1ex\hbox to 1em{\hfil$\mapsto$\hfil}} \def\print{\leavevmode\lower.1ex\hbox to 1em{\hfil$\dashv$\hfil}} \def\equiv{\leavevmode\lower.1ex\hbox to 1em{\hfil$\ptexequiv$\hfil}} % Adapted from the TeXbook's \boxit. {\tentt \global\dimen0 = 3em}% Width of the box. \dimen2 = .55pt % Thickness of rules % The text. (`r' is open on the right, `e' somewhat less so on the left.) \setbox0 = \hbox{\kern-.75pt \tensf error\kern-1.5pt} \global\setbox\errorbox=\hbox to \dimen0{\hfil \hsize = \dimen0 \advance\hsize by -5.6pt % Space to left+right. \advance\hsize by -2\dimen2 % Rules. \vbox{ \hrule height\dimen2 \hbox{\vrule width\dimen2 \kern3pt % Space to left of text. \vtop{\kern2.4pt \box0 \kern2.4pt}% Space above/below. \kern3pt\vrule width\dimen2}% Space to right. \hrule height\dimen2} \hfil} % The @error{} command. \def\error{\leavevmode\lower.7ex\copy\errorbox} % @tex ... @end tex escapes into raw Tex temporarily. % One exception: @ is still an escape character, so that @end tex works. % But \@ or @@ will get a plain tex @ character. \def\tex{\begingroup \catcode `\\=0 \catcode `\{=1 \catcode `\}=2 \catcode `\$=3 \catcode `\&=4 \catcode `\#=6 \catcode `\^=7 \catcode `\_=8 \catcode `\~=13 \let~=\tie \catcode `\%=14 \catcode 43=12 % plus \catcode`\"=12 \catcode`\==12 \catcode`\|=12 \catcode`\<=12 \catcode`\>=12 \escapechar=`\\ % \let\b=\ptexb \let\bullet=\ptexbullet \let\c=\ptexc \let\,=\ptexcomma \let\.=\ptexdot \let\dots=\ptexdots \let\equiv=\ptexequiv \let\!=\ptexexclam \let\i=\ptexi \let\{=\ptexlbrace \let\+=\tabalign \let\}=\ptexrbrace \let\*=\ptexstar \let\t=\ptext % \def\endldots{\mathinner{\ldots\ldots\ldots\ldots}}% \def\enddots{\relax\ifmmode\endldots\else$\mathsurround=0pt \endldots\,$\fi}% \def\@{@}% \let\Etex=\endgroup} % Define @lisp ... @endlisp. % @lisp does a \begingroup so it can rebind things, % including the definition of @endlisp (which normally is erroneous). % Amount to narrow the margins by for @lisp. \newskip\lispnarrowing \lispnarrowing=0.4in % This is the definition that ^^M gets inside @lisp, @example, and other % such environments. \null is better than a space, since it doesn't % have any width. \def\lisppar{\null\endgraf} % Make each space character in the input produce a normal interword % space in the output. Don't allow a line break at this space, as this % is used only in environments like @example, where each line of input % should produce a line of output anyway. % {\obeyspaces % \gdef\sepspaces{\obeyspaces\let =\tie}} % Define \obeyedspace to be our active space, whatever it is. This is % for use in \parsearg. {\sepspaces% \global\let\obeyedspace= } % This space is always present above and below environments. \newskip\envskipamount \envskipamount = 0pt % Make spacing and below environment symmetrical. We use \parskip here % to help in doing that, since in @example-like environments \parskip % is reset to zero; thus the \afterenvbreak inserts no space -- but the % start of the next paragraph will insert \parskip % \def\aboveenvbreak{{\advance\envskipamount by \parskip \endgraf \ifdim\lastskip<\envskipamount \removelastskip \penalty-50 \vskip\envskipamount \fi}} \let\afterenvbreak = \aboveenvbreak % \nonarrowing is a flag. If "set", @lisp etc don't narrow margins. \let\nonarrowing=\relax % @cartouche ... @end cartouche: draw rectangle w/rounded corners around % environment contents. \font\circle=lcircle10 \newdimen\circthick \newdimen\cartouter\newdimen\cartinner \newskip\normbskip\newskip\normpskip\newskip\normlskip \circthick=\fontdimen8\circle % \def\ctl{{\circle\char'013\hskip -6pt}}% 6pt from pl file: 1/2charwidth \def\ctr{{\hskip 6pt\circle\char'010}} \def\cbl{{\circle\char'012\hskip -6pt}} \def\cbr{{\hskip 6pt\circle\char'011}} \def\carttop{\hbox to \cartouter{\hskip\lskip \ctl\leaders\hrule height\circthick\hfil\ctr \hskip\rskip}} \def\cartbot{\hbox to \cartouter{\hskip\lskip \cbl\leaders\hrule height\circthick\hfil\cbr \hskip\rskip}} % \newskip\lskip\newskip\rskip \long\def\cartouche{% \begingroup \lskip=\leftskip \rskip=\rightskip \leftskip=0pt\rightskip=0pt %we want these *outside*. \cartinner=\hsize \advance\cartinner by-\lskip \advance\cartinner by-\rskip \cartouter=\hsize \advance\cartouter by 18.4pt % allow for 3pt kerns on either % side, and for 6pt waste from % each corner char, and rule thickness \normbskip=\baselineskip \normpskip=\parskip \normlskip=\lineskip % Flag to tell @lisp, etc., not to narrow margin. \let\nonarrowing=\comment \vbox\bgroup \baselineskip=0pt\parskip=0pt\lineskip=0pt \carttop \hbox\bgroup \hskip\lskip \vrule\kern3pt \vbox\bgroup \hsize=\cartinner \kern3pt \begingroup \baselineskip=\normbskip \lineskip=\normlskip \parskip=\normpskip \vskip -\parskip \def\Ecartouche{% \endgroup \kern3pt \egroup \kern3pt\vrule \hskip\rskip \egroup \cartbot \egroup \endgroup }} % This macro is called at the beginning of all the @example variants, % inside a group. \def\nonfillstart{% \aboveenvbreak \inENV % This group ends at the end of the body \hfuzz = 10pt % Don't be fussy \sepspaces % Make spaces be word-separators rather than space tokens. \singlespace \let\par = \lisppar % don't ignore blank lines \obeylines % each line of input is a line of output \parskip = 0pt \parindent = 0pt \emergencystretch = 0pt % don't try to avoid overfull boxes % @cartouche defines \nonarrowing to inhibit narrowing % at next level down. \ifx\nonarrowing\relax \advance \leftskip by \lispnarrowing \exdentamount=\lispnarrowing \let\exdent=\nofillexdent \let\nonarrowing=\relax \fi } % Define the \E... control sequence only if we are inside the particular % environment, so the error checking in \end will work. % % To end an @example-like environment, we first end the paragraph (via % \afterenvbreak's vertical glue), and then the group. That way we keep % the zero \parskip that the environments set -- \parskip glue will be % inserted at the beginning of the next paragraph in the document, after % the environment. % \def\nonfillfinish{\afterenvbreak\endgroup} % @lisp: indented, narrowed, typewriter font. \def\lisp{\begingroup \nonfillstart \let\Elisp = \nonfillfinish \tt \let\kbdfont = \kbdexamplefont % Allow @kbd to do something special. \gobble % eat return } % @example: Same as @lisp. \def\example{\begingroup \def\Eexample{\nonfillfinish\endgroup}\lisp} % @small... is usually equivalent to the non-small (@smallbook % redefines). We must call \example (or whatever) last in the % definition, since it reads the return following the @example (or % whatever) command. % % This actually allows (for example) @end display inside an % @smalldisplay. Too bad, but makeinfo will catch the error anyway. % \def\smalldisplay{\begingroup\def\Esmalldisplay{\nonfillfinish\endgroup}\display} \def\smallexample{\begingroup\def\Esmallexample{\nonfillfinish\endgroup}\lisp} \def\smallformat{\begingroup\def\Esmallformat{\nonfillfinish\endgroup}\format} \def\smalllisp{\begingroup\def\Esmalllisp{\nonfillfinish\endgroup}\lisp} % Real @smallexample and @smalllisp (when @smallbook): use smaller fonts. % Originally contributed by Pavel@xerox. \def\smalllispx{\begingroup \def\Esmalllisp{\nonfillfinish\endgroup}% \def\Esmallexample{\nonfillfinish\endgroup}% \indexfonts \lisp } % @display: same as @lisp except keep current font. % \def\display{\begingroup \nonfillstart \let\Edisplay = \nonfillfinish \gobble } % @smalldisplay (when @smallbook): @display plus smaller fonts. % \def\smalldisplayx{\begingroup \def\Esmalldisplay{\nonfillfinish\endgroup}% \indexfonts \rm \display } % @format: same as @display except don't narrow margins. % \def\format{\begingroup \let\nonarrowing = t \nonfillstart \let\Eformat = \nonfillfinish \gobble } % @smallformat (when @smallbook): @format plus smaller fonts. % \def\smallformatx{\begingroup \def\Esmallformat{\nonfillfinish\endgroup}% \indexfonts \rm \format } % @flushleft (same as @format). % \def\flushleft{\begingroup \def\Eflushleft{\nonfillfinish\endgroup}\format} % @flushright. % \def\flushright{\begingroup \let\nonarrowing = t \nonfillstart \let\Eflushright = \nonfillfinish \advance\leftskip by 0pt plus 1fill \gobble } % @quotation does normal linebreaking (hence we can't use \nonfillstart) % and narrows the margins. % \def\quotation{% \begingroup\inENV %This group ends at the end of the @quotation body {\parskip=0pt \aboveenvbreak}% because \aboveenvbreak inserts \parskip \singlespace \parindent=0pt % We have retained a nonzero parskip for the environment, since we're % doing normal filling. So to avoid extra space below the environment... \def\Equotation{\parskip = 0pt \nonfillfinish}% % % @cartouche defines \nonarrowing to inhibit narrowing at next level down. \ifx\nonarrowing\relax \advance\leftskip by \lispnarrowing \advance\rightskip by \lispnarrowing \exdentamount = \lispnarrowing \let\nonarrowing = \relax \fi } \message{defuns,} % @defun etc. % Allow user to change definition object font (\df) internally \def\setdeffont #1 {\csname DEF#1\endcsname} \newskip\defbodyindent \defbodyindent=.4in \newskip\defargsindent \defargsindent=50pt \newskip\deftypemargin \deftypemargin=10pt \newskip\deflastargmargin \deflastargmargin=16pt \newcount\parencount % define \functionparens, which makes ( and ) and & do special things. % \functionparens affects the group it is contained in. \def\activeparens{% \catcode`\(=\active \catcode`\)=\active \catcode`\&=\active \catcode`\[=\active \catcode`\]=\active} % Make control sequences which act like normal parenthesis chars. \let\lparen = ( \let\rparen = ) {\activeparens % Now, smart parens don't turn on until &foo (see \amprm) % Be sure that we always have a definition for `(', etc. For example, % if the fn name has parens in it, \boldbrax will not be in effect yet, % so TeX would otherwise complain about undefined control sequence. \global\let(=\lparen \global\let)=\rparen \global\let[=\lbrack \global\let]=\rbrack \gdef\functionparens{\boldbrax\let&=\amprm\parencount=0 } \gdef\boldbrax{\let(=\opnr\let)=\clnr\let[=\lbrb\let]=\rbrb} % This is used to turn on special parens % but make & act ordinary (given that it's active). \gdef\boldbraxnoamp{\let(=\opnr\let)=\clnr\let[=\lbrb\let]=\rbrb\let&=\ampnr} % Definitions of (, ) and & used in args for functions. % This is the definition of ( outside of all parentheses. \gdef\oprm#1 {{\rm\char`\(}#1 \bf \let(=\opnested \global\advance\parencount by 1 } % % This is the definition of ( when already inside a level of parens. \gdef\opnested{\char`\(\global\advance\parencount by 1 } % \gdef\clrm{% Print a paren in roman if it is taking us back to depth of 0. % also in that case restore the outer-level definition of (. \ifnum \parencount=1 {\rm \char `\)}\sl \let(=\oprm \else \char `\) \fi \global\advance \parencount by -1 } % If we encounter &foo, then turn on ()-hacking afterwards \gdef\amprm#1 {{\rm\}\let(=\oprm \let)=\clrm\ } % \gdef\normalparens{\boldbrax\let&=\ampnr} } % End of definition inside \activeparens %% These parens (in \boldbrax) actually are a little bolder than the %% contained text. This is especially needed for [ and ] \def\opnr{{\sf\char`\(}\global\advance\parencount by 1 } \def\clnr{{\sf\char`\)}\global\advance\parencount by -1 } \let\ampnr = \& \def\lbrb{{\bf\char`\[}} \def\rbrb{{\bf\char`\]}} % Active &'s sneak into the index arguments, so make sure it's defined. { \catcode`& = 13 \global\let& = \ampnr } % First, defname, which formats the header line itself. % #1 should be the function name. % #2 should be the type of definition, such as "Function". \def\defname #1#2{% % Get the values of \leftskip and \rightskip as they were % outside the @def... \dimen2=\leftskip \advance\dimen2 by -\defbodyindent \noindent \setbox0=\hbox{\hskip \deflastargmargin{\rm #2}\hskip \deftypemargin}% \dimen0=\hsize \advance \dimen0 by -\wd0 % compute size for first line \dimen1=\hsize \advance \dimen1 by -\defargsindent %size for continuations \parshape 2 0in \dimen0 \defargsindent \dimen1 % Now output arg 2 ("Function" or some such) % ending at \deftypemargin from the right margin, % but stuck inside a box of width 0 so it does not interfere with linebreaking {% Adjust \hsize to exclude the ambient margins, % so that \rightline will obey them. \advance \hsize by -\dimen2 \rlap{\rightline{{\rm #2}\hskip -1.25pc }}}% % Make all lines underfull and no complaints: \tolerance=10000 \hbadness=10000 \advance\leftskip by -\defbodyindent \exdentamount=\defbodyindent {\df #1}\enskip % Generate function name } % Actually process the body of a definition % #1 should be the terminating control sequence, such as \Edefun. % #2 should be the "another name" control sequence, such as \defunx. % #3 should be the control sequence that actually processes the header, % such as \defunheader. \def\defparsebody #1#2#3{\begingroup\inENV% Environment for definitionbody \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2{\begingroup\obeylines\activeparens\spacesplit#3}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup % \catcode 61=\active % 61 is `=' \obeylines\activeparens\spacesplit#3} % #1 is the \E... control sequence to end the definition (which we define). % #2 is the \...x control sequence for consecutive fns (which we define). % #3 is the control sequence to call to resume processing. % #4, delimited by the space, is the class name. % \def\defmethparsebody#1#2#3#4 {\begingroup\inENV % \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2##1 {\begingroup\obeylines\activeparens\spacesplit{#3{##1}}}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup\obeylines\activeparens\spacesplit{#3{#4}}} % @deftypemethod has an extra argument that nothing else does. Sigh. % #1 is the \E... control sequence to end the definition (which we define). % #2 is the \...x control sequence for consecutive fns (which we define). % #3 is the control sequence to call to resume processing. % #4, delimited by the space, is the class name. % #5 is the method's return type. % \def\deftypemethparsebody#1#2#3#4 #5 {\begingroup\inENV % \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2##1 ##2 {\begingroup\obeylines\activeparens\spacesplit{#3{##1}{##2}}}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup\obeylines\activeparens\spacesplit{#3{#4}{#5}}} \def\defopparsebody #1#2#3#4#5 {\begingroup\inENV % \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2##1 ##2 {\def#4{##1}% \begingroup\obeylines\activeparens\spacesplit{#3{##2}}}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup\obeylines\activeparens\spacesplit{#3{#5}}} % These parsing functions are similar to the preceding ones % except that they do not make parens into active characters. % These are used for "variables" since they have no arguments. \def\defvarparsebody #1#2#3{\begingroup\inENV% Environment for definitionbody \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2{\begingroup\obeylines\spacesplit#3}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup % \catcode 61=\active % \obeylines\spacesplit#3} % This is used for \def{tp,vr}parsebody. It could probably be used for % some of the others, too, with some judicious conditionals. % \def\parsebodycommon#1#2#3{% \begingroup\inENV % \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2##1 {\begingroup\obeylines\spacesplit{#3{##1}}}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup\obeylines } \def\defvrparsebody#1#2#3#4 {% \parsebodycommon{#1}{#2}{#3}% \spacesplit{#3{#4}}% } % This loses on `@deftp {Data Type} {struct termios}' -- it thinks the % type is just `struct', because we lose the braces in `{struct % termios}' when \spacesplit reads its undelimited argument. Sigh. % \let\deftpparsebody=\defvrparsebody % % So, to get around this, we put \empty in with the type name. That % way, TeX won't find exactly `{...}' as an undelimited argument, and % won't strip off the braces. % \def\deftpparsebody #1#2#3#4 {% \parsebodycommon{#1}{#2}{#3}% \spacesplit{\parsetpheaderline{#3{#4}}}\empty } % Fine, but then we have to eventually remove the \empty *and* the % braces (if any). That's what this does. % \def\removeemptybraces\empty#1\relax{#1} % After \spacesplit has done its work, this is called -- #1 is the final % thing to call, #2 the type name (which starts with \empty), and #3 % (which might be empty) the arguments. % \def\parsetpheaderline#1#2#3{% #1{\removeemptybraces#2\relax}{#3}% }% \def\defopvarparsebody #1#2#3#4#5 {\begingroup\inENV % \medbreak % % Define the end token that this defining construct specifies % so that it will exit this group. \def#1{\endgraf\endgroup\medbreak}% \def#2##1 ##2 {\def#4{##1}% \begingroup\obeylines\spacesplit{#3{##2}}}% \parindent=0in \advance\leftskip by \defbodyindent \exdentamount=\defbodyindent \begingroup\obeylines\spacesplit{#3{#5}}} % Split up #2 at the first space token. % call #1 with two arguments: % the first is all of #2 before the space token, % the second is all of #2 after that space token. % If #2 contains no space token, all of it is passed as the first arg % and the second is passed as empty. {\obeylines \gdef\spacesplit#1#2^^M{\endgroup\spacesplitfoo{#1}#2 \relax\spacesplitfoo}% \long\gdef\spacesplitfoo#1#2 #3#4\spacesplitfoo{% \ifx\relax #3% #1{#2}{}\else #1{#2}{#3#4}\fi}} % So much for the things common to all kinds of definitions. % Define @defun. % First, define the processing that is wanted for arguments of \defun % Use this to expand the args and terminate the paragraph they make up \def\defunargs#1{\functionparens \sl % Expand, preventing hyphenation at `-' chars. % Note that groups don't affect changes in \hyphenchar. % Set the font temporarily and use \font in case \setfont made \tensl a macro. {\tensl\hyphenchar\font=0}% #1% {\tensl\hyphenchar\font=45}% \ifnum\parencount=0 \else \errmessage{Unbalanced parentheses in @def}\fi% \interlinepenalty=10000 \advance\rightskip by 0pt plus 1fil \endgraf\nobreak\vskip -\parskip\nobreak } \def\deftypefunargs #1{% % Expand, preventing hyphenation at `-' chars. % Note that groups don't affect changes in \hyphenchar. % Use \boldbraxnoamp, not \functionparens, so that & is not special. \boldbraxnoamp \tclose{#1}% avoid \code because of side effects on active chars \interlinepenalty=10000 \advance\rightskip by 0pt plus 1fil \endgraf\nobreak\vskip -\parskip\nobreak } % Do complete processing of one @defun or @defunx line already parsed. % @deffn Command forward-char nchars \def\deffn{\defmethparsebody\Edeffn\deffnx\deffnheader} \def\deffnheader #1#2#3{\doind {fn}{\code{#2}}% \begingroup\defname {#2}{#1}\defunargs{#3}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @defun == @deffn Function \def\defun{\defparsebody\Edefun\defunx\defunheader} \def\defunheader #1#2{\doind {fn}{\code{#1}}% Make entry in function index \begingroup\defname {#1}{\putwordDeffunc}% \defunargs {#2}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @deftypefun int foobar (int @var{foo}, float @var{bar}) \def\deftypefun{\defparsebody\Edeftypefun\deftypefunx\deftypefunheader} % #1 is the data type. #2 is the name and args. \def\deftypefunheader #1#2{\deftypefunheaderx{#1}#2 \relax} % #1 is the data type, #2 the name, #3 the args. \def\deftypefunheaderx #1#2 #3\relax{% \doind {fn}{\code{#2}}% Make entry in function index \begingroup\defname {\defheaderxcond#1\relax$$$#2}{\putwordDeftypefun}% \deftypefunargs {#3}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @deftypefn {Library Function} int foobar (int @var{foo}, float @var{bar}) \def\deftypefn{\defmethparsebody\Edeftypefn\deftypefnx\deftypefnheader} % \defheaderxcond#1\relax$$$ % puts #1 in @code, followed by a space, but does nothing if #1 is null. \def\defheaderxcond#1#2$$${\ifx#1\relax\else\code{#1#2} \fi} % #1 is the classification. #2 is the data type. #3 is the name and args. \def\deftypefnheader #1#2#3{\deftypefnheaderx{#1}{#2}#3 \relax} % #1 is the classification, #2 the data type, #3 the name, #4 the args. \def\deftypefnheaderx #1#2#3 #4\relax{% \doind {fn}{\code{#3}}% Make entry in function index \begingroup \normalparens % notably, turn off `&' magic, which prevents % at least some C++ text from working \defname {\defheaderxcond#2\relax$$$#3}{#1}% \deftypefunargs {#4}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @defmac == @deffn Macro \def\defmac{\defparsebody\Edefmac\defmacx\defmacheader} \def\defmacheader #1#2{\doind {fn}{\code{#1}}% Make entry in function index \begingroup\defname {#1}{\putwordDefmac}% \defunargs {#2}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @defspec == @deffn Special Form \def\defspec{\defparsebody\Edefspec\defspecx\defspecheader} \def\defspecheader #1#2{\doind {fn}{\code{#1}}% Make entry in function index \begingroup\defname {#1}{\putwordDefspec}% \defunargs {#2}\endgroup % \catcode 61=\other % Turn off change made in \defparsebody } % @defop CATEGORY CLASS OPERATION ARG... % \def\defop #1 {\def\defoptype{#1}% \defopparsebody\Edefop\defopx\defopheader\defoptype} % \def\defopheader #1#2#3{% \dosubind {fn}{\code{#2}}{\putwordon\ #1}% Make entry in function index \begingroup\defname {#2}{\defoptype\ \putwordon\ #1}% \defunargs {#3}\endgroup % } % @deftypemethod CLASS RETURN-TYPE METHOD ARG... % \def\deftypemethod{% \deftypemethparsebody\Edeftypemethod\deftypemethodx\deftypemethodheader} % % #1 is the class name, #2 the data type, #3 the method name, #4 the args. \def\deftypemethodheader#1#2#3#4{% \dosubind{fn}{\code{#3}}{\putwordon\ \code{#1}}% entry in function index \begingroup \defname{\defheaderxcond#2\relax$$$#3}{\putwordMethodon\ \code{#1}}% \deftypefunargs{#4}% \endgroup } % @deftypeivar CLASS TYPE VARNAME % \def\deftypeivar{% \deftypemethparsebody\Edeftypeivar\deftypeivarx\deftypeivarheader} % % #1 is the class name, #2 the data type, #3 the variable name. \def\deftypeivarheader#1#2#3{% \dosubind{vr}{\code{#3}}{\putwordof\ \code{#1}}% entry in variable index \begingroup \defname{#3}{\putwordInstanceVariableof\ \code{#1}}% \defvarargs{#3}% \endgroup } % @defmethod == @defop Method % \def\defmethod{\defmethparsebody\Edefmethod\defmethodx\defmethodheader} % % #1 is the class name, #2 the method name, #3 the args. \def\defmethodheader#1#2#3{% \dosubind{fn}{\code{#2}}{\putwordon\ \code{#1}}% entry in function index \begingroup \defname{#2}{\putwordMethodon\ \code{#1}}% \defunargs{#3}% \endgroup } % @defcv {Class Option} foo-class foo-flag \def\defcv #1 {\def\defcvtype{#1}% \defopvarparsebody\Edefcv\defcvx\defcvarheader\defcvtype} \def\defcvarheader #1#2#3{% \dosubind {vr}{\code{#2}}{\putwordof\ #1}% Make entry in var index \begingroup\defname {#2}{\defcvtype\ \putwordof\ #1}% \defvarargs {#3}\endgroup % } % @defivar CLASS VARNAME == @defcv {Instance Variable} CLASS VARNAME % \def\defivar{\defvrparsebody\Edefivar\defivarx\defivarheader} % \def\defivarheader#1#2#3{% \dosubind {vr}{\code{#2}}{\putwordof\ #1}% entry in var index \begingroup \defname{#2}{\putwordInstanceVariableof\ #1}% \defvarargs{#3}% \endgroup } % @defvar % First, define the processing that is wanted for arguments of @defvar. % This is actually simple: just print them in roman. % This must expand the args and terminate the paragraph they make up \def\defvarargs #1{\normalparens #1% \interlinepenalty=10000 \endgraf\nobreak\vskip -\parskip\nobreak} % @defvr Counter foo-count \def\defvr{\defvrparsebody\Edefvr\defvrx\defvrheader} \def\defvrheader #1#2#3{\doind {vr}{\code{#2}}% \begingroup\defname {#2}{#1}\defvarargs{#3}\endgroup} % @defvar == @defvr Variable \def\defvar{\defvarparsebody\Edefvar\defvarx\defvarheader} \def\defvarheader #1#2{\doind {vr}{\code{#1}}% Make entry in var index \begingroup\defname {#1}{\putwordDefvar}% \defvarargs {#2}\endgroup % } % @defopt == @defvr {User Option} \def\defopt{\defvarparsebody\Edefopt\defoptx\defoptheader} \def\defoptheader #1#2{\doind {vr}{\code{#1}}% Make entry in var index \begingroup\defname {#1}{\putwordDefopt}% \defvarargs {#2}\endgroup % } % @deftypevar int foobar \def\deftypevar{\defvarparsebody\Edeftypevar\deftypevarx\deftypevarheader} % #1 is the data type. #2 is the name, perhaps followed by text that % is actually part of the data type, which should not be put into the index. \def\deftypevarheader #1#2{% \dovarind#2 \relax% Make entry in variables index \begingroup\defname {\defheaderxcond#1\relax$$$#2}{\putwordDeftypevar}% \interlinepenalty=10000 \endgraf\nobreak\vskip -\parskip\nobreak \endgroup} \def\dovarind#1 #2\relax{\doind{vr}{\code{#1}}} % @deftypevr {Global Flag} int enable \def\deftypevr{\defvrparsebody\Edeftypevr\deftypevrx\deftypevrheader} \def\deftypevrheader #1#2#3{\dovarind#3 \relax% \begingroup\defname {\defheaderxcond#2\relax$$$#3}{#1} \interlinepenalty=10000 \endgraf\nobreak\vskip -\parskip\nobreak \endgroup} % Now define @deftp % Args are printed in bold, a slight difference from @defvar. \def\deftpargs #1{\bf \defvarargs{#1}} % @deftp Class window height width ... \def\deftp{\deftpparsebody\Edeftp\deftpx\deftpheader} \def\deftpheader #1#2#3{\doind {tp}{\code{#2}}% \begingroup\defname {#2}{#1}\deftpargs{#3}\endgroup} % These definitions are used if you use @defunx (etc.) % anywhere other than immediately after a @defun or @defunx. % \def\defcvx#1 {\errmessage{@defcvx in invalid context}} \def\deffnx#1 {\errmessage{@deffnx in invalid context}} \def\defivarx#1 {\errmessage{@defivarx in invalid context}} \def\defmacx#1 {\errmessage{@defmacx in invalid context}} \def\defmethodx#1 {\errmessage{@defmethodx in invalid context}} \def\defoptx #1 {\errmessage{@defoptx in invalid context}} \def\defopx#1 {\errmessage{@defopx in invalid context}} \def\defspecx#1 {\errmessage{@defspecx in invalid context}} \def\deftpx#1 {\errmessage{@deftpx in invalid context}} \def\deftypefnx#1 {\errmessage{@deftypefnx in invalid context}} \def\deftypefunx#1 {\errmessage{@deftypefunx in invalid context}} \def\deftypeivarx#1 {\errmessage{@deftypeivarx in invalid context}} \def\deftypemethodx#1 {\errmessage{@deftypemethodx in invalid context}} \def\deftypevarx#1 {\errmessage{@deftypevarx in invalid context}} \def\deftypevrx#1 {\errmessage{@deftypevrx in invalid context}} \def\defunx#1 {\errmessage{@defunx in invalid context}} \def\defvarx#1 {\errmessage{@defvarx in invalid context}} \def\defvrx#1 {\errmessage{@defvrx in invalid context}} \message{macros,} % @macro. % To do this right we need a feature of e-TeX, \scantokens, % which we arrange to emulate with a temporary file in ordinary TeX. \ifx\eTeXversion\undefined \newwrite\macscribble \def\scanmacro#1{% \begingroup \newlinechar`\^^M % Undo catcode changes of \startcontents and \doprintindex \catcode`\@=0 \catcode`\\=12 \escapechar=`\@ % Append \endinput to make sure that TeX does not see the ending newline. \toks0={#1\endinput}% \immediate\openout\macscribble=\jobname.tmp \immediate\write\macscribble{\the\toks0}% \immediate\closeout\macscribble \let\xeatspaces\eatspaces \input \jobname.tmp \endgroup } \else \def\scanmacro#1{% \begingroup \newlinechar`\^^M % Undo catcode changes of \startcontents and \doprintindex \catcode`\@=0 \catcode`\\=12 \escapechar=`\@ \let\xeatspaces\eatspaces\scantokens{#1\endinput}\endgroup} \fi \newcount\paramno % Count of parameters \newtoks\macname % Macro name \newif\ifrecursive % Is it recursive? \def\macrolist{} % List of all defined macros in the form % \do\macro1\do\macro2... % Utility routines. % Thisdoes \let #1 = #2, except with \csnames. \def\cslet#1#2{% \expandafter\expandafter \expandafter\let \expandafter\expandafter \csname#1\endcsname \csname#2\endcsname} % Trim leading and trailing spaces off a string. % Concepts from aro-bend problem 15 (see CTAN). {\catcode`\@=11 \gdef\eatspaces #1{\expandafter\trim@\expandafter{#1 }} \gdef\trim@ #1{\trim@@ @#1 @ #1 @ @@} \gdef\trim@@ #1@ #2@ #3@@{\trim@@@\empty #2 @} \def\unbrace#1{#1} \unbrace{\gdef\trim@@@ #1 } #2@{#1} } % Trim a single trailing ^^M off a string. {\catcode`\^^M=12\catcode`\Q=3% \gdef\eatcr #1{\eatcra #1Q^^MQ}% \gdef\eatcra#1^^MQ{\eatcrb#1Q}% \gdef\eatcrb#1Q#2Q{#1}% } % Macro bodies are absorbed as an argument in a context where % all characters are catcode 10, 11 or 12, except \ which is active % (as in normal texinfo). It is necessary to change the definition of \. % It's necessary to have hard CRs when the macro is executed. This is % done by making ^^M (\endlinechar) catcode 12 when reading the macro % body, and then making it the \newlinechar in \scanmacro. \def\macrobodyctxt{% \catcode`\~=12 \catcode`\^=12 \catcode`\_=12 \catcode`\|=12 \catcode`\<=12 \catcode`\>=12 \catcode`\+=12 \catcode`\{=12 \catcode`\}=12 \catcode`\@=12 \catcode`\^^M=12 \usembodybackslash} \def\macroargctxt{% \catcode`\~=12 \catcode`\^=12 \catcode`\_=12 \catcode`\|=12 \catcode`\<=12 \catcode`\>=12 \catcode`\+=12 \catcode`\@=12 \catcode`\\=12} % \mbodybackslash is the definition of \ in @macro bodies. % It maps \foo\ => \csname macarg.foo\endcsname => #N % where N is the macro parameter number. % We define \csname macarg.\endcsname to be \realbackslash, so % \\ in macro replacement text gets you a backslash. {\catcode`@=0 @catcode`@\=@active @gdef@usembodybackslash{@let\=@mbodybackslash} @gdef@mbodybackslash#1\{@csname macarg.#1@endcsname} } \expandafter\def\csname macarg.\endcsname{\realbackslash} \def\macro{\recursivefalse\parsearg\macroxxx} \def\rmacro{\recursivetrue\parsearg\macroxxx} \def\macroxxx#1{% \getargs{#1}% now \macname is the macname and \argl the arglist \ifx\argl\empty % no arguments \paramno=0% \else \expandafter\parsemargdef \argl;% \fi \if1\csname ismacro.\the\macname\endcsname \message{Warning: redefining \the\macname}% \else \expandafter\ifx\csname \the\macname\endcsname \relax \else \errmessage{The name \the\macname\space is reserved}\fi \global\cslet{macsave.\the\macname}{\the\macname}% \global\expandafter\let\csname ismacro.\the\macname\endcsname=1% % Add the macroname to \macrolist \toks0 = \expandafter{\macrolist\do}% \xdef\macrolist{\the\toks0 \expandafter\noexpand\csname\the\macname\endcsname}% \fi \begingroup \macrobodyctxt \ifrecursive \expandafter\parsermacbody \else \expandafter\parsemacbody \fi} \def\unmacro{\parsearg\unmacroxxx} \def\unmacroxxx#1{% \if1\csname ismacro.#1\endcsname \global\cslet{#1}{macsave.#1}% \global\expandafter\let \csname ismacro.#1\endcsname=0% % Remove the macro name from \macrolist \begingroup \edef\tempa{\expandafter\noexpand\csname#1\endcsname}% \def\do##1{% \def\tempb{##1}% \ifx\tempa\tempb % remove this \else \toks0 = \expandafter{\newmacrolist\do}% \edef\newmacrolist{\the\toks0\expandafter\noexpand\tempa}% \fi}% \def\newmacrolist{}% % Execute macro list to define \newmacrolist \macrolist \global\let\macrolist\newmacrolist \endgroup \else \errmessage{Macro #1 not defined}% \fi } % This makes use of the obscure feature that if the last token of a % is #, then the preceding argument is delimited by % an opening brace, and that opening brace is not consumed. \def\getargs#1{\getargsxxx#1{}} \def\getargsxxx#1#{\getmacname #1 \relax\getmacargs} \def\getmacname #1 #2\relax{\macname={#1}} \def\getmacargs#1{\def\argl{#1}} % Parse the optional {params} list. Set up \paramno and \paramlist % so \defmacro knows what to do. Define \macarg.blah for each blah % in the params list, to be ##N where N is the position in that list. % That gets used by \mbodybackslash (above). % We need to get `macro parameter char #' into several definitions. % The technique used is stolen from LaTeX: let \hash be something % unexpandable, insert that wherever you need a #, and then redefine % it to # just before using the token list produced. % % The same technique is used to protect \eatspaces till just before % the macro is used. \def\parsemargdef#1;{\paramno=0\def\paramlist{}% \let\hash\relax\let\xeatspaces\relax\parsemargdefxxx#1,;,} \def\parsemargdefxxx#1,{% \if#1;\let\next=\relax \else \let\next=\parsemargdefxxx \advance\paramno by 1% \expandafter\edef\csname macarg.\eatspaces{#1}\endcsname {\xeatspaces{\hash\the\paramno}}% \edef\paramlist{\paramlist\hash\the\paramno,}% \fi\next} % These two commands read recursive and nonrecursive macro bodies. % (They're different since rec and nonrec macros end differently.) \long\def\parsemacbody#1@end macro% {\xdef\temp{\eatcr{#1}}\endgroup\defmacro}% \long\def\parsermacbody#1@end rmacro% {\xdef\temp{\eatcr{#1}}\endgroup\defmacro}% % This defines the macro itself. There are six cases: recursive and % nonrecursive macros of zero, one, and many arguments. % Much magic with \expandafter here. % \xdef is used so that macro definitions will survive the file % they're defined in; @include reads the file inside a group. \def\defmacro{% \let\hash=##% convert placeholders to macro parameter chars \ifrecursive \ifcase\paramno % 0 \expandafter\xdef\csname\the\macname\endcsname{% \noexpand\scanmacro{\temp}}% \or % 1 \expandafter\xdef\csname\the\macname\endcsname{% \bgroup\noexpand\macroargctxt \noexpand\braceorline \expandafter\noexpand\csname\the\macname xxx\endcsname}% \expandafter\xdef\csname\the\macname xxx\endcsname##1{% \egroup\noexpand\scanmacro{\temp}}% \else % many \expandafter\xdef\csname\the\macname\endcsname{% \bgroup\noexpand\macroargctxt \noexpand\csname\the\macname xx\endcsname}% \expandafter\xdef\csname\the\macname xx\endcsname##1{% \expandafter\noexpand\csname\the\macname xxx\endcsname ##1,}% \expandafter\expandafter \expandafter\xdef \expandafter\expandafter \csname\the\macname xxx\endcsname \paramlist{\egroup\noexpand\scanmacro{\temp}}% \fi \else \ifcase\paramno % 0 \expandafter\xdef\csname\the\macname\endcsname{% \noexpand\norecurse{\the\macname}% \noexpand\scanmacro{\temp}\egroup}% \or % 1 \expandafter\xdef\csname\the\macname\endcsname{% \bgroup\noexpand\macroargctxt \noexpand\braceorline \expandafter\noexpand\csname\the\macname xxx\endcsname}% \expandafter\xdef\csname\the\macname xxx\endcsname##1{% \egroup \noexpand\norecurse{\the\macname}% \noexpand\scanmacro{\temp}\egroup}% \else % many \expandafter\xdef\csname\the\macname\endcsname{% \bgroup\noexpand\macroargctxt \expandafter\noexpand\csname\the\macname xx\endcsname}% \expandafter\xdef\csname\the\macname xx\endcsname##1{% \expandafter\noexpand\csname\the\macname xxx\endcsname ##1,}% \expandafter\expandafter \expandafter\xdef \expandafter\expandafter \csname\the\macname xxx\endcsname \paramlist{% \egroup \noexpand\norecurse{\the\macname}% \noexpand\scanmacro{\temp}\egroup}% \fi \fi} \def\norecurse#1{\bgroup\cslet{#1}{macsave.#1}} % \braceorline decides whether the next nonwhitespace character is a % {. If so it reads up to the closing }, if not, it reads the whole % line. Whatever was read is then fed to the next control sequence % as an argument (by \parsebrace or \parsearg) \def\braceorline#1{\let\next=#1\futurelet\nchar\braceorlinexxx} \def\braceorlinexxx{% \ifx\nchar\bgroup\else \expandafter\parsearg \fi \next} % We mant to disable all macros during \shipout so that they are not % expanded by \write. \def\turnoffmacros{\begingroup \def\do##1{\let\noexpand##1=\relax}% \edef\next{\macrolist}\expandafter\endgroup\next} % @alias. \def\alias#1=#2{\gdef#1{#2}} \message{cross references,} % @xref etc. \newwrite\auxfile \newif\ifhavexrefs % True if xref values are known. \newif\ifwarnedxrefs % True if we warned once that they aren't known. % @inforef is relatively simple. \def\inforef #1{\inforefzzz #1,,,,**} \def\inforefzzz #1,#2,#3,#4**{\putwordSee{} \putwordInfo{} \putwordfile{} \file{\ignorespaces #3{}}, node \samp{\ignorespaces#1{}}} % @node's job is to define \lastnode. \def\node{\ENVcheck\parsearg\nodezzz} \def\nodezzz#1{\nodexxx [#1,]} \def\nodexxx[#1,#2]{\gdef\lastnode{#1}} \let\nwnode=\node \let\lastnode=\relax % The sectioning commands (@chapter, etc.) call these. \def\donoderef{% \ifx\lastnode\relax\else \expandafter\expandafter\expandafter\setref{\lastnode}% {Ysectionnumberandtype}% \global\let\lastnode=\relax \fi } \def\unnumbnoderef{% \ifx\lastnode\relax\else \expandafter\expandafter\expandafter\setref{\lastnode}{Ynothing}% \global\let\lastnode=\relax \fi } \def\appendixnoderef{% \ifx\lastnode\relax\else \expandafter\expandafter\expandafter\setref{\lastnode}% {Yappendixletterandtype}% \global\let\lastnode=\relax \fi } % @anchor{NAME} -- define xref target at arbitrary point. % { \catcode`\@ = 11 % From latex.ltx, to make @anchor truely invisible. \newdimen\@savsk \newcount\@savsf \gdef\@bsphack{\relax \ifhmode \@savsk\lastskip \@savsf\spacefactor \fi } \gdef\@esphack{\relax \ifhmode \spacefactor\@savsf \ifdim\@savsk>\z@ \ignorespaces \fi \fi } \gdef\anchor#1{\@bsphack \setref{#1}{Ynothing}\@esphack} } % \setref{NAME}{SNT} defines a cross-reference point NAME, namely % NAME-title, NAME-pg, and NAME-SNT. Called from \foonoderef. We have % to set \indexdummies so commands such as @code in a section title % aren't expanded. It would be nicer not to expand the titles in the % first place, but there's so many layers that that is hard to do. % \def\setref#1#2{{% \indexdummies \ifpdf \pdfmkdest{#1}\fi \dosetq{#1-title}{Ytitle}% \dosetq{#1-pg}{Ypagenumber}% \dosetq{#1-snt}{#2}% }} % @xref, @pxref, and @ref generate cross-references. For \xrefX, #1 is % the node name, #2 the name of the Info cross-reference, #3 the printed % node name, #4 the name of the Info file, #5 the name of the printed % manual. All but the node name can be omitted. % %\def\pxref#1{\putwordsee{} \xrefX[#1,,,,,,,]} %\def\xref#1{\putwordSee{} \xrefX[#1,,,,,,,]} \def\pxref#1{\xrefX[#1,,,,,,,] \putwordsee{}} \def\xref#1{\xrefX[#1,,,,,,,] \putwordSee{}} \def\ref#1{\xrefX[#1,,,,,,,]} \def\xrefX[#1,#2,#3,#4,#5,#6]{\begingroup \def\printedmanual{\ignorespaces #5}% \def\printednodename{\ignorespaces #3}% \setbox1=\hbox{\printedmanual}% \setbox0=\hbox{\printednodename}% \ifdim \wd0 = 0pt % No printed node name was explicitly given. \expandafter\ifx\csname SETxref-automatic-section-title\endcsname\relax % Use the node name inside the square brackets. \def\printednodename{\ignorespaces #1}% \else % Use the actual chapter/section title appear inside % the square brackets. Use the real section title if we have it. \ifdim \wd1 > 0pt % It is in another manual, so we don't have it. \def\printednodename{\ignorespaces #1}% \else \ifhavexrefs % We know the real title if we have the xref values. \def\printednodename{\refx{#1-title}{}}% \else % Otherwise just copy the Info node name. \def\printednodename{\ignorespaces #1}% \fi% \fi \fi \fi % % If we use \unhbox0 and \unhbox1 to print the node names, TeX does not % insert empty discretionaries after hyphens, which means that it will % not find a line break at a hyphen in a node names. Since some manuals % are best written with fairly long node names, containing hyphens, this % is a loss. Therefore, we give the text of the node name again, so it % is as if TeX is seeing it for the first time. \ifpdf \leavevmode \getfilename{#4}% \ifnum\filenamelength>0 \pdfannotlink attr{/Border [0 0 0]}% goto file{\the\filename.pdf} name{#1@}% \else \pdfannotlink attr{/Border [0 0 0]}% goto name{#1@}% \fi \BlueGreen \fi % \ifdim \wd1 > 0pt % \putwordsection{} ``\printednodename'' \putwordin{} \cite{\printedmanual}% 「\printednodename」 \putwordsection{} \putwordin{} \cite{\printedmanual}% \else % _ (for example) has to be the character _ for the purposes of the % control sequence corresponding to the node, but it has to expand % into the usual \leavevmode...\vrule stuff for purposes of % printing. So we \turnoffactive for the \refx-snt, back on for the % printing, back off for the \refx-pg. {\normalturnoffactive % Only output a following space if the -snt ref is nonempty; for % @unnumbered and @anchor, it won't be. \setbox2 = \hbox{\ignorespaces \refx{#1-snt}{}}% \ifdim \wd2 > 0pt \refx{#1-snt}\space\fi }% % [mynode], % [\printednodename],\space 「\printednodename」,\space % page 3 \turnoffactive \putwordpage\tie\refx{#1-pg}{}% \fi \ifpdf \Black\pdfendlink \fi \endgroup} % \dosetq is the interface for calls from other macros % Use \normalturnoffactive so that punctuation chars such as underscore % and backslash work in node names. (\turnoffactive doesn't do \.) \def\dosetq#1#2{% {\let\folio=0% \normalturnoffactive \edef\next{\write\auxfile{\internalsetq{#1}{#2}}}% \iflinks \next \fi }% } % \internalsetq {foo}{page} expands into % CHARACTERS 'xrdef {foo}{...expansion of \Ypage...} % When the aux file is read, ' is the escape character \def\internalsetq #1#2{'xrdef {#1}{\csname #2\endcsname}} % Things to be expanded by \internalsetq \def\Ypagenumber{\folio} \def\Ytitle{\thissection} \def\Ynothing{} % @ref '第 xx 章 yyyyy 参照' % うまくつくれないねぇ...まったく TeX は面倒、複雑 \def\Ysectionnumberandtype{% \ifnum\secno=0 \preputwordChapter\the\chapno\putwordChapter\xreftie % % \else \ifnum \subsecno=0 \putwordSection\xreftie\the\chapno.\the\secno % \else \ifnum \subsecno=0 \xreftie\the\chapno.\the\secno \putwordSection % \else \ifnum \subsubsecno=0 % % \putwordSection\xreftie\the\chapno.\the\secno.\the\subsecno % \xreftie\the\chapno.\the\secno.\the\subsecno \putwordSection % \else % % \putwordSection\xreftie\the\chapno.\the\secno.\the\subsecno.\the\subsubsecno % \xreftie\the\chapno.\the\secno.\the\subsecno.\the\subsubsecno \putwordSection % \fi \fi \fi } \def\Yappendixletterandtype{% \ifnum\secno=0 \putwordAppendix\xreftie'char\the\appendixno{}% % \else \ifnum \subsecno=0 \putwordSection\xreftie'char\the\appendixno.\the\secno % \else \ifnum \subsecno=0 \xreftie'char\the\appendixno.\the\secno \putwordSection % \else \ifnum \subsubsecno=0 % % \putwordSection\xreftie'char\the\appendixno.\the\secno.\the\subsecno % \xreftie'char\the\appendixno.\the\secno.\the\subsecno \putwordSection % \else % % \putwordSection\xreftie'char\the\appendixno.\the\secno.\the\subsecno.\the\subsubsecno % \xreftie'char\the\appendixno.\the\secno.\the\subsecno.\the\subsubsecno \putwordSection % \fi \fi \fi } \gdef\xreftie{'tie} % Use TeX 3.0's \inputlineno to get the line number, for better error % messages, but if we're using an old version of TeX, don't do anything. % \ifx\inputlineno\thisisundefined \let\linenumber = \empty % Non-3.0. \else \def\linenumber{\the\inputlineno:\space} \fi % Define \refx{NAME}{SUFFIX} to reference a cross-reference string named NAME. % If its value is nonempty, SUFFIX is output afterward. \def\refx#1#2{% \expandafter\ifx\csname X#1\endcsname\relax % If not defined, say something at least. \angleleft un\-de\-fined\angleright \iflinks \ifhavexrefs \message{\linenumber Undefined cross reference `#1'.}% \else \ifwarnedxrefs\else \global\warnedxrefstrue \message{Cross reference values unknown; you must run TeX again.}% \fi \fi \fi \else % It's defined, so just use it. \csname X#1\endcsname \fi #2% Output the suffix in any case. } % This is the macro invoked by entries in the aux file. % \def\xrdef#1{\begingroup % Reenable \ as an escape while reading the second argument. \catcode`\\ = 0 \afterassignment\endgroup \expandafter\gdef\csname X#1\endcsname } % Read the last existing aux file, if any. No error if none exists. \def\readauxfile{\begingroup \catcode`\^^@=\other \catcode`\^^A=\other \catcode`\^^B=\other \catcode`\^^C=\other \catcode`\^^D=\other \catcode`\^^E=\other \catcode`\^^F=\other \catcode`\^^G=\other \catcode`\^^H=\other \catcode`\^^K=\other \catcode`\^^L=\other \catcode`\^^N=\other \catcode`\^^P=\other \catcode`\^^Q=\other \catcode`\^^R=\other \catcode`\^^S=\other \catcode`\^^T=\other \catcode`\^^U=\other \catcode`\^^V=\other \catcode`\^^W=\other \catcode`\^^X=\other \catcode`\^^Z=\other \catcode`\^^[=\other \catcode`\^^\=\other \catcode`\^^]=\other \catcode`\^^^=\other \catcode`\^^_=\other \catcode`\@=\other \catcode`\^=\other % It was suggested to define this as 7, which would allow ^^e4 etc. % in xref tags, i.e., node names. But since ^^e4 notation isn't % supported in the main text, it doesn't seem desirable. Furthermore, % that is not enough: for node names that actually contain a ^ % character, we would end up writing a line like this: 'xrdef {'hat % b-title}{'hat b} and \xrdef does a \csname...\endcsname on the first % argument, and \hat is not an expandable control sequence. It could % all be worked out, but why? Either we support ^^ or we don't. % % The other change necessary for this was to define \auxhat: % \def\auxhat{\def^{'hat }}% extra space so ok if followed by letter % and then to call \auxhat in \setq. % \catcode`\~=\other \catcode`\[=\other \catcode`\]=\other \catcode`\"=\other \catcode`\_=\other \catcode`\|=\other \catcode`\<=\other \catcode`\>=\other \catcode`\$=\other \catcode`\#=\other \catcode`\&=\other \catcode`+=\other % avoid \+ for paranoia even though we've turned it off % Make the characters 128-255 be printing characters {% \count 1=128 \def\loop{% \catcode\count 1=\other \advance\count 1 by 1 \ifnum \count 1<256 \loop \fi }% }% % The aux file uses ' as the escape (for now). % Turn off \ as an escape so we do not lose on % entries which were dumped with control sequences in their names. % For example, 'xrdef {$\leq $-fun}{page ...} made by @defun ^^ % Reference to such entries still does not work the way one would wish, % but at least they do not bomb out when the aux file is read in. \catcode`\{=1 \catcode`\}=2 \catcode`\%=\other \catcode`\'=0 \catcode`\\=\other % \openin 1 \jobname.aux \ifeof 1 \else \closein 1 \input \jobname.aux \global\havexrefstrue \global\warnedobstrue \fi % Open the new aux file. TeX will close it automatically at exit. \openout\auxfile=\jobname.aux \endgroup} % Footnotes. \newcount \footnoteno % The trailing space in the following definition for supereject is % vital for proper filling; pages come out unaligned when you do a % pagealignmacro call if that space before the closing brace is % removed. (Generally, numeric constants should always be followed by a % space to prevent strange expansion errors.) \def\supereject{\par\penalty -20000\footnoteno =0 } % @footnotestyle is meaningful for info output only. \let\footnotestyle=\comment \let\ptexfootnote=\footnote {\catcode `\@=11 % % Auto-number footnotes. Otherwise like plain. \gdef\footnote{% \global\advance\footnoteno by \@ne \edef\thisfootno{$^{\the\footnoteno}$}% % % In case the footnote comes at the end of a sentence, preserve the % extra spacing after we do the footnote number. \let\@sf\empty \ifhmode\edef\@sf{\spacefactor\the\spacefactor}\/\fi % % Remove inadvertent blank space before typesetting the footnote number. \unskip \thisfootno\@sf \footnotezzz }% % Don't bother with the trickery in plain.tex to not require the % footnote text as a parameter. Our footnotes don't need to be so general. % % Oh yes, they do; otherwise, @ifset and anything else that uses % \parseargline fail inside footnotes because the tokens are fixed when % the footnote is read. --karl, 16nov96. % \long\gdef\footnotezzz{\insert\footins\bgroup % We want to typeset this text as a normal paragraph, even if the % footnote reference occurs in (for example) a display environment. % So reset some parameters. \interlinepenalty\interfootnotelinepenalty \splittopskip\ht\strutbox % top baseline for broken footnotes \splitmaxdepth\dp\strutbox \floatingpenalty\@MM \leftskip\z@skip \rightskip\z@skip \spaceskip\z@skip \xspaceskip\z@skip \parindent\defaultparindent % % Hang the footnote text off the number. \hang \textindent{\thisfootno}% % % Don't crash into the line above the footnote text. Since this % expands into a box, it must come within the paragraph, lest it % provide a place where TeX can split the footnote. \footstrut \futurelet\next\fo@t } \def\fo@t{\ifcat\bgroup\noexpand\next \let\next\f@@t \else\let\next\f@t\fi \next} \def\f@@t{\bgroup\aftergroup\@foot\let\next} \def\f@t#1{#1\@foot} \def\@foot{\strut\egroup} }%end \catcode `\@=11 % Set the baselineskip to #1, and the lineskip and strut size % correspondingly. There is no deep meaning behind these magic numbers % used as factors; they just match (closely enough) what Knuth defined. % \def\lineskipfactor{.08333} \def\strutheightpercent{.70833} \def\strutdepthpercent {.29167} % \def\setleading#1{% \normalbaselineskip = #1\relax \normallineskip = \lineskipfactor\normalbaselineskip \normalbaselines \setbox\strutbox =\hbox{% \vrule width0pt height\strutheightpercent\baselineskip depth \strutdepthpercent \baselineskip }% } % @| inserts a changebar to the left of the current line. It should % surround any changed text. This approach does *not* work if the % change spans more than two lines of output. To handle that, we would % have adopt a much more difficult approach (putting marks into the main % vertical list for the beginning and end of each change). % \def\|{% % \vadjust can only be used in horizontal mode. \leavevmode % % Append this vertical mode material after the current line in the output. \vadjust{% % We want to insert a rule with the height and depth of the current % leading; that is exactly what \strutbox is supposed to record. \vskip-\baselineskip % % \vadjust-items are inserted at the left edge of the type. So % the \llap here moves out into the left-hand margin. \llap{% % % For a thicker or thinner bar, change the `1pt'. \vrule height\baselineskip width1pt % % This is the space between the bar and the text. \hskip 10pt }% }% } % For a final copy, take out the rectangles % that mark overfull boxes (in case you have decided % that the text looks ok even though it passes the margin). % \def\finalout{\overfullrule=0pt} % @image. We use the macros from epsf.tex to support this. % If epsf.tex is not installed and @image is used, we complain. % % Check for and read epsf.tex up front. If we read it only at @image % time, we might be inside a group, and then its definitions would get % undone and the next image would fail. \openin 1 = epsf.tex \ifeof 1 \else \closein 1 % Do not bother showing banner with post-v2.7 epsf.tex (available in % doc/epsf.tex until it shows up on ctan). \def\epsfannounce{\toks0 = }% \input epsf.tex \fi % % We will only complain once about lack of epsf.tex. \newif\ifwarnednoepsf \newhelp\noepsfhelp{epsf.tex must be installed for images to work. It is also included in the Texinfo distribution, or you can get it from ftp://tug.org/tex/epsf.tex.} % \def\image#1{% \ifx\epsfbox\undefined \ifwarnednoepsf \else \errhelp = \noepsfhelp \errmessage{epsf.tex not found, images will be ignored}% \global\warnednoepsftrue \fi \else \imagexxx #1,,,\finish \fi } % % Arguments to @image: % #1 is (mandatory) image filename; we tack on .eps extension. % #2 is (optional) width, #3 is (optional) height. % #4 is just the usual extra ignored arg for parsing this stuff. \def\imagexxx#1,#2,#3,#4\finish{% \ifx\pdfoutput\undefined % \epsfbox itself resets \epsf?size at each figure. \setbox0 = \hbox{\ignorespaces #2}\ifdim\wd0 > 0pt \epsfxsize=#2\relax \fi \setbox0 = \hbox{\ignorespaces #3}\ifdim\wd0 > 0pt \epsfysize=#3\relax \fi \begingroup \catcode`\^^M = 5 % in case we're inside an example % If the image is by itself, center it. \ifvmode \nobreak\bigskip % Usually we'll have text after the image which will insert % \parskip glue, so insert it here too to equalize the space % above and below. \nobreak\vskip\parskip \nobreak \centerline{\epsfbox{#1.eps}}% \bigbreak \else % In the middle of a paragraph, no extra space. \epsfbox{#1.eps}% \fi \endgroup \else \centerline{\pdfimage #1.pdf}% \fi } \message{localization,} % and i18n. % @documentlanguage is usually given very early, just after % @setfilename. If done too late, it may not override everything % properly. Single argument is the language abbreviation. % It would be nice if we could set up a hyphenation file here. % \def\documentlanguage{\parsearg\dodocumentlanguage} \def\dodocumentlanguage#1{% \tex % read txi-??.tex file in plain TeX. % Read the file if it exists. \openin 1 txi-#1.tex \ifeof1 \errhelp = \nolanghelp \errmessage{Cannot read language file txi-#1.tex}% \let\temp = \relax \else \def\temp{\input txi-#1.tex }% \fi \temp \endgroup } \newhelp\nolanghelp{The given language definition file cannot be found or is empty. Maybe you need to install it? In the current directory should work if nowhere else does.} % @documentencoding should change something in TeX eventually, most % likely, but for now just recognize it. \let\documentencoding = \comment % Page size parameters. % \newdimen\defaultparindent \defaultparindent = 15pt \chapheadingskip = 15pt plus 4pt minus 2pt \secheadingskip = 10pt plus 3pt minus 2pt \subsecheadingskip = 9pt plus 2pt minus 2pt % Prevent underfull vbox error messages. \vbadness = 10000 % Don't be so finicky about underfull hboxes, either. \hbadness = 2000 % Following George Bush, just get rid of widows and orphans. \widowpenalty=10000 \clubpenalty=10000 % Use TeX 3.0's \emergencystretch to help line breaking, but if we're % using an old version of TeX, don't do anything. We want the amount of % stretch added to depend on the line length, hence the dependence on % \hsize. We call this whenever the paper size is set. % \def\setemergencystretch{% \ifx\emergencystretch\thisisundefined % Allow us to assign to \emergencystretch anyway. \def\emergencystretch{\dimen0}% \else \emergencystretch = .15\hsize \fi } % Parameters in order: 1) textheight; 2) textwidth; 3) voffset; % 4) hoffset; 5) binding offset; 6) topskip. Then whoever calls us can % set \parskip and call \setleading for \baselineskip. % 引数： % #1 = 本文が書かれる部分の高さ % #2 = 本文が書かれる部分の幅 % #4 = 左の開始位置。紙の左端から 1inch が 0 基準. マイナスも与えれる % #5,#6 は なんなのか 不明 % \def\internalpagesizes#1#2#3#4#5#6{% \voffset = #3\relax \topskip = #6\relax \splittopskip = \topskip % \vsize = #1\relax \advance\vsize by \topskip \outervsize = \vsize \advance\outervsize by 2\topandbottommargin \pageheight = \vsize % \hsize = #2\relax \outerhsize = \hsize \advance\outerhsize by 0.5in \pagewidth = \hsize % \normaloffset = #4\relax \bindingoffset = #5\relax % \parindent = \defaultparindent \setemergencystretch } % Use @afourpaper to print on European A4 paper. \def\afourpaper{{\globaldefs = 1 \setleading{10pt}% \parskip = 3pt plus 2pt minus 1pt % %% \internalpagesizes{53\baselineskip}{160mm}{\voffset}{4mm}{\bindingoffset}{44pt}% % %より多くの情報を一枚の紙に \internalpagesizes{69\baselineskip}{165mm}{2mm}{-2.5mm}{0mm}{5mm}% % \tolerance = 700 \hfuzz = 1pt }} % @letterpaper (the default). \def\letterpaper{{\globaldefs = 1 \parskip = 3pt plus 2pt minus 1pt \setleading{13.2pt}% % % If page is nothing but text, make it come out even. \internalpagesizes{46\baselineskip}{6in}{\voffset}{.25in}{\bindingoffset}{36pt}% }} % Use @smallbook to reset parameters for 7x9.5 (or so) format. \def\smallbook{{\globaldefs = 1 \parskip = 2pt plus 1pt \setleading{10pt}% % \internalpagesizes{7.5in}{5.in}{\voffset}{.25in}{\bindingoffset}{16pt}% % \lispnarrowing = 0.3in \tolerance = 700 \hfuzz = 1pt \contentsrightmargin = 0pt \deftypemargin = 0pt \defbodyindent = .5cm % \let\smalldisplay = \smalldisplayx \let\smallexample = \smalllispx \let\smallformat = \smallformatx \let\smalllisp = \smalllispx }} % A specific text layout, 24x15cm overall, intended for A4 paper. Top margin % 29mm, hence bottom margin 28mm, nominal side margin 3cm. \def\afourlatex{{\globaldefs = 1 \setleading{13.6pt}% % \afourpaper \internalpagesizes{237mm}{150mm}{3.6mm}{3.6mm}{3mm}{7mm}% % \globaldefs = 0 }} % Use @afourwide to print on European A4 paper in wide format. \def\afourwide{% \afourpaper \internalpagesizes{9.5in}{6.5in}{\hoffset}{\normaloffset}{\bindingoffset}{7mm}% % \globaldefs = 0 } % @pagesizes TEXTHEIGHT[,TEXTWIDTH] % Perhaps we should allow setting the margins, \topskip, \parskip, % and/or leading, also. Or perhaps we should compute them somehow. % \def\pagesizes{\parsearg\pagesizesxxx} \def\pagesizesxxx#1{\pagesizesyyy #1,,\finish} \def\pagesizesyyy#1,#2,#3\finish{{% \setbox0 = \hbox{\ignorespaces #2}\ifdim\wd0 > 0pt \hsize=#2\relax \fi \globaldefs = 1 % \parskip = 3pt plus 2pt minus 1pt \setleading{13.2pt}% % \internalpagesizes{#1}{\hsize}{\voffset}{\normaloffset}{\bindingoffset}{44pt}% }} % Set default to letter. % \letterpaper \message{and turning on texinfo input format.} % Define macros to output various characters with catcode for normal text. \catcode`\"=\other \catcode`\~=\other \catcode`\^=\other \catcode`\_=\other \catcode`\|=\other \catcode`\<=\other \catcode`\>=\other \catcode`\+=\other \catcode`\$=\other \def\normaldoublequote{"} \def\normaltilde{~} \def\normalcaret{^} \def\normalunderscore{_} \def\normalverticalbar{|} \def\normalless{<} \def\normalgreater{>} \def\normalplus{+} \def\normaldollar{$} % This macro is used to make a character print one way in ttfont % where it can probably just be output, and another way in other fonts, % where something hairier probably needs to be done. % % #1 is what to print if we are indeed using \tt; #2 is what to print % otherwise. Since all the Computer Modern typewriter fonts have zero % interword stretch (and shrink), and it is reasonable to expect all % typewriter fonts to have this, we can check that font parameter. % \def\ifusingtt#1#2{\ifdim \fontdimen3\font=0pt #1\else #2\fi} % Same as above, but check for italic font. Actually this also catches % non-italic slanted fonts since it is impossible to distinguish them from % italic fonts. But since this is only used by $ and it uses \sl anyway % this is not a problem. \def\ifusingit#1#2{\ifdim \fontdimen1\font>0pt #1\else #2\fi} % Turn off all special characters except @ % (and those which the user can use as if they were ordinary). % Most of these we simply print from the \tt font, but for some, we can % use math or other variants that look better in normal text. \catcode`\"=\active \def\activedoublequote{{\tt\char34}} \let"=\activedoublequote \catcode`\~=\active \def~{{\tt\char126}} \chardef\hat=`\^ \catcode`\^=\active \def^{{\tt \hat}} \catcode`\_=\active \def_{\ifusingtt\normalunderscore\_} % Subroutine for the previous macro. \def\_{\leavevmode \kern.06em \vbox{\hrule width.3em height.1ex}} \catcode`\|=\active \def|{{\tt\char124}} \chardef \less=`\< \catcode`\<=\active \def<{{\tt \less}} \chardef \gtr=`\> \catcode`\>=\active \def>{{\tt \gtr}} \catcode`\+=\active \def+{{\tt \char 43}} \catcode`\$=\active \def${\ifusingit{{\sl\$}}\normaldollar} %\catcode 27=\active %\def^^[{$\diamondsuit$} % Set up an active definition for =, but don't enable it most of the time. {\catcode`\==\active \global\def={{\tt \char 61}}} \catcode`+=\active \catcode`\_=\active % If a .fmt file is being used, characters that might appear in a file % name cannot be active until we have parsed the command line. % So turn them off again, and have \everyjob (or @setfilename) turn them on. % \otherifyactive is called near the end of this file. \def\otherifyactive{\catcode`+=\other \catcode`\_=\other} \catcode`\@=0 % \rawbackslashxx output one backslash character in current font \global\chardef\rawbackslashxx=`\\ %{\catcode`\\=\other %@gdef@rawbackslashxx{\}} % \rawbackslash redefines \ as input to do \rawbackslashxx. {\catcode`\\=\active @gdef@rawbackslash{@let\=@rawbackslashxx }} % \normalbackslash outputs one backslash in fixed width font. \def\normalbackslash{{\tt\rawbackslashxx}} % \catcode 17=0 % Define control-q \catcode`\\=\active % Used sometimes to turn off (effectively) the active characters % even after parsing them. @def@turnoffactive{@let"=@normaldoublequote @let\=@realbackslash @let~=@normaltilde @let^=@normalcaret @let_=@normalunderscore @let|=@normalverticalbar @let<=@normalless @let>=@normalgreater @let+=@normalplus @let$=@normaldollar} @def@normalturnoffactive{@let"=@normaldoublequote @let\=@normalbackslash @let~=@normaltilde @let^=@normalcaret @let_=@normalunderscore @let|=@normalverticalbar @let<=@normalless @let>=@normalgreater @let+=@normalplus @let$=@normaldollar} % Make _ and + \other characters, temporarily. % This is canceled by @fixbackslash. @otherifyactive % If a .fmt file is being used, we don't want the `\input texinfo' to show up. % That is what \eatinput is for; after that, the `\' should revert to printing % a backslash. % @gdef@eatinput input texinfo{@fixbackslash} @global@let\ = @eatinput % On the other hand, perhaps the file did not have a `\input texinfo'. Then % the first `\{ in the file would cause an error. This macro tries to fix % that, assuming it is called before the first `\' could plausibly occur. % Also back turn on active characters that might appear in the input % file name, in case not using a pre-dumped format. % @gdef@fixbackslash{% @ifx\@eatinput @let\ = @normalbackslash @fi @catcode`+=@active @catcode`@_=@active } % Say @foo, not \foo, in error messages. @escapechar = `@@ % These look ok in all fonts, so just make them not special. @catcode`@& = @other @catcode`@# = @other @catcode`@% = @other @c Set initial fonts. @textfonts @rm @c Local variables: @c eval: (add-hook 'write-file-hooks 'time-stamp) @c page-delimiter: "^\\\\message" @c time-stamp-start: "def\\\\texinfoversion{" @c time-stamp-format: "%:y-%02m-%02d.%H" @c time-stamp-end: "}" @c End: mysql-4.00.12/manual.ja_MySQL_Optimisation.html0100644000175100001560000043372610021471264020175 0ustar takeshisa MySQL Reference Manual for version 4.0.12. - 5 MySQL Optimisation Go to the first, previous, next, last section, table of contents.